Sap Upload File With Jpy for Fb01

FB01 step by step: Posting documents

This document describes how you lot can apply Winshuttle Transaction to post documents in the SAP Business concern Suite from data in Microsoft Excel using the SAP transaction FB01.

The example here will show how to utilize the Transaction loop feature to upload documents with multiple-line entries from an Excel file into SAP.

Steps

Tape

1. Start Winshuttle Studio from the desktop shortcut or from the Windows Commencement carte du jour.
2. Click New.

   

3. Click Transaction, and and so click Create from Recording.

   

4. Choose the SAP system that you want to use, enter the appropriate user data, and and so click Log On to SAP.

   

   If you practice not see the SAP system that yous desire, click Advanced SAP Logon, click Add together System, provide the organization information, and click OK.

5. In the Transaction code box, type FB01.

   

6. Leave the recording mode as Standard. If you do not run across Standard, click Change, click Not-Batch Input Mode Without SAP Controls, and then click OK.

   Note: For most transactions, the default way is Standard, and the Winshuttle Function Module (WFM) selects the optimum way for the t-code that is being recorded.  If the WFM is non installed, Not-Batch Input Mode Without Controls will work for virtually transactions. Not-Batch modes are necessary for downloading information from SAP transactions, or for Finance or Hr transactions in which in that location are Dynamic Actions executing or user parameter values being used; otherwise, if you do not take access to Non-Batch modes, you tin can try recording in Batch Mode. The difference between Without SAP Controls and With SAP Controls is but a matter of what tools are on the transaction screens. For more data, see the Recording modes topic (Connect fashion or Foundation manner).

7. Click Showtime Recording.

   

   The FB01 transaction starts.

   Annotation: The post-obit screens may vary according to the way your SAP organization has been configured.

To brand this process repeatable by Transaction, there volition be a few changes to the procedure compared with how you would manually create a cloth. These differences will exist identified throughout the residue of this certificate.

8. Enter information into the header section of the screen. In this example:
   • Certificate Engagement
   • Document Type
   • Company Code
   • Currency Rate

   

9. Click Fast Data Entry.

   

10. In the Tx field on the elevation row, enter a space.

    

11. Under Other line items, enter the following:
    • PstKy
    • Account

    

    You can also enter a dissimilar company code.

    Of import: These steps will virtually likely exist unlike from manual entry.

12. Click Enter (the green checkmark push button).
13. Enter the Amount and any other relevant information.

    

14. Click Fast Data Entry again.

    

15. In the Tx field on the top row, enter a space.

    

16. Under Other line items, enter the post-obit:
    • PstKy
    • Account

    Of import: While recording this transaction, pay close attending to the running balances of the debit and credit entries. The transaction balance indicator must be dark-green at the end of the recording.

    

17. Click Enter (the green checkmark button).
18. Enter the Amount and whatever other relevant data.

    

19. Click Fast Data Entry again.
20. Click Salvage to save and exit out of the transaction.

    

21. When SAP notifies you that the document was posted, click the greenish checkmark push button. This ends the recording.

Subsequently Studio finishes compiling the script, it will accept you lot to the Map tab.

Map

Information technology is now time to create the mapping for this transaction. Mapping a script is just a matter of connecting SAP fields to fields in your information file. Transaction provides a Mapper to facilitate this process.

Machine Mapping will map the unabridged script to an Excel spreadsheet in the order that they announced in the Mapper. Because of the complexity of this transaction, we will map the fields manually instead.

The screenshot below shows the Bones View tab of the Mapper.

In each of the rows of the Mapper, y'all will encounter:

• Mapper row number: This is only a reference number.
• Enable flag: only enabled Mapper rows volition be executed by Transaction.
• Field Description: The label associated with the SAP technical field proper name.
• Field Name: The SAP technical field name.
• Field Type & Length: For example, String or Decimal, and the padding options.
• Mapping management: Stock-still Value, Excel to SAP, SAP to Excel (or, if mapping to Access: Access to SAP, SAP to Access).
• Value: Values assigned to the SAP field; either stock-still values or mapped locations in the associated data source.

Note: The Properties pane is too displayed, but it is non shown below.

In the Information Set panel, you will see a preview screen of the selected data source type.

To change the data source type, click the drop-downward menu nether the Information Prepare tab and choose the data source type that you want.

The preview volition change to reflect the choice. In this case, we will use Excel.

Add the loop

To allow the Excel spreadsheet to contain data for multiple line items, we will insert a Loop around Mapper rows containing the item data for Posting Key, Business relationship, Amount, and whatever other line item fields.

1. Click the Expert View tab.
2. Select the rows for the unabridged line detail, in this case rows eleven through 20.

   

3. Click the Create Loop push.

   

   The Loop box opens with default values, which yous can change.

   • The boxes at the top show the get-go and end rows of the loop in the Mapper (the highlighted rows).
   • The Loop identifier column box displays the column in the spreadsheet that will contain the Header and Item (line item data) identifiers.
   • The Text to identify Transaction Header and Text to identify repeating Line Items boxes display the values that volition identify the Header (H) and Line Particular (D) rows.

   >

4. Click OK to insert the loop around the selected Mapper rows.

   The Mapper reflects the post-obit changes as a effect of inserting the Loop:

   • The graphical depiction of the loop around the selected lines indicates which Mapper rows will be contained inside the loop.
   • The Loop ID Cavalcade has been identified in the Preview panel.
   • Row ii contains the first Header ID value and Row 3 contains the Line Item ID value.

   

Disable duplicate fields

Every bit you lot can see, the line item data for Posting Key, Business relationship, Amount, and any other line item fields repeat again on the next screen because in our recording we entered two line items.

We do not need these fields to exist enabled.

To disable the duplicate fields:

1. Select the rows by clicking the outset row in the selection and pressing Shift while you click the last row in the selection.
2. Right-click and select Disable from the menu.

   

The rows disappear from the Mapper.

Map and salvage the script

To map the script to the data source, y'all will drag in the direction that the data volition move. For this script, you are uploading information from Excel to SAP, and then you volition elevate from Excel to the Mapper.

1. Drag cavalcade B up and drop it onto row seven.
2. Continue across the Excel preview by dragging column C upwardly and dropping it onto row viii, column D up to row nine, and column E up to row 10, respectively. Continue for all the header and line item fields.

   >

Add data and run the script

1. Click the Run tab.

   

   Note: Transaction volition automatically assign the Log column to the side by side available cavalcade after the last mapped column (in this case, column J).

2. Type the data in the columns.

   

   You can specify a different first and end row, specify the Excel sheet that contains the data, and change the Log column.

3. To execute the upload, click the Examination button, if you lot are a Foundation user, or click the Run button if yous are not a Foundation user.

   Studio prompts you to salve the script and information files.

   

   The best do is to proper name the Excel spreadsheet the same name every bit the script unless an Excel spreadsheet volition be used for multiple scripts.

   After you salve the script and data files, the script runs.

   The yellow message bar displays a message when the run has finished.

   

4. Check the log cavalcade. The run was successful and the messages returned from SAP were entered into the log column.

   

baileyhicess1990.blogspot.com

Source: http://winshuttle-help.s3.amazonaws.com/step-by-step/en/studio/fb01-step-by-step_11.htm

Share this post