FB60 – Enter Incoming Invoices SAP transaction info, menu path, user exits, related t-codes. SAP fb60 tcodes (Transaction Codes). Enter Incoming Invoices tcode – FB60, G/ L Acct Pstg: Single Screen Trans. tcode – FB50, Enter Outgoing Invoices tcode. Winshuttle technologies enable users to work directly with SAP FB60 transaction data in Excel. This approach helps companies avoid time-consuming and.
|Published (Last):||18 May 2009|
|PDF File Size:||12.8 Mb|
|ePub File Size:||18.17 Mb|
|Price:||Free* [*Free Regsitration Required]|
The transactkon here will show how to use the loop feature to invoices with multiple line items from an Excel file into SAP. The FB60 transaction is very similar to the FV60 Park Invoice transaction, and the steps shown here can also be used for that transaction.
What is diffrence between MIRO and FB60
For most transactions, transactoin default mode is Standard, and the Zap Function Module WFM selects the optimum mode for the t-code that is being recorded. Non-Batch modes are necessary for downloading information from SAP transactions, or for Finance or HR transactions in which there are Dynamic Actions executing or user parameter values being used; otherwise, if you do not have access to Non-Batch modes, you can try recording in Batch Mode.
For more information, see the Recording modes topic Connect mode or Foundation mode.
The following screens hransaction vary according to the way your SAP system has been configured. These differences will be identified throughout the rest of this document. To make this process repeatable by Transaction, there will be a few changes to the process compared with how you would manually create a material.
These steps will most likely be different from manual entry. It 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 data file.
Transaction provides a Mapper to facilitate this process. Auto Mapping will map the entire script to an Excel spreadsheet in the order that they appear in the Mapper.
Because of the complexity of this transaction, we will map the fields manually instead.
The Properties pane is also displayed, but it is not shown below. In the Data Set panel, you will see a preview screen of the selected data source type.
To change the data source type, click the drop-down menu under the Data Set tab and choose the data source type that you want.
To wap the Excel spreadsheet to contain data for multiple line items, we un insert a loop around the Mapper rows that contain the item data.
The Mapper reflects the following changes as a result of inserting the Loop:. To yransaction the script to the data source, you will drag in the direction that the data will move.
Studio will automatically assign the Log column to the next available column after the last mapped column in this case, column J.
Use of FB60, FB65, MIRO, FK03 and FBL1N Transaction
You can specify a start and end row, specify the Excel sheet that contains the data, and change the Log column. The best practice is to name the Excel spreadsheet the same name as the script unless an Excel spreadsheet will be used for multiple scripts. Studio v11 CS01 step by step: Creating a Bill of Materials FB01 step by step: Posting documents FB50 step by step: Posting Journal vouchers FB60 step by step: Entering invoices FBS1 step by step: Creating a purchase order ME31K step by step: Creating a contract MM01 step by step: Creating a material master MM02 step by step: Changing a material master PA40 step by step: Personnel Actions VA01 step by step: Creating a sales order with reference XD01 step by step: Step by step Journal Entry 9.
Creating a Bill of Materials FB50 step by step: Posting Journal vouchers FBS1 step by step: Creating a purchase order MM01 step by step: FB60 step by step: Steps The FB60 transaction is very similar to the FV60 Park Invoice transaction, and the steps shown here can also be used for that transaction.
Click Transactionand then click Create from Recording. In the Transaction code box, type FB Leave the recording mode as Standard. The FB60 transaction starts.
FB60 SAP Transaction code – Enter Incoming Invoices
Enter the company code and click Enter the green checkmark button. O line 1 of the line item section, enter data for the first line item: After you enter all of the data for the line, click the sapp on the left of line 1 to select and highlight the row.
Click the Insert Row button to insert an empty row above the current row. If a yellow warning message appears, press Enter. Click Save to save and exit out of the transaction.
When SAP notifies you that the document was posted, click the green checkmark button. This ends the recording. After Studio finishes compiling the script, it will take you to the Map tab. Map It is now time to create the mapping for this transaction. The screenshot below shows the Basic View tab of the Mapper. In each of the rows of the Mapper, you will see: This is just a reference number. The label associated with the SAP technical field name. The SAP technical field name.
For example, String or Decimal, and the padding options. The preview will 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 the Mapper rows that contain the item data. Select the rows for the entire line item, in this case rows 15 through Click the Create Loop button.
The Loop box opens with default values, which you can change. The boxes at the top show the start 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 Detail line item data identifiers.
The Text to identify transaction header and Text to identify repeating line items boxes display the values that will identify the Header H and Line Item D rows. Click OK to insert the loop around the selected Mapper rows. The Mapper reflects the following changes as a result of inserting the Loop: The graphical depiction of the loop around the selected lines indicates which Mapper rows will be contained within the loop.
Map and save the script To map the script to the data source, you will drag in the direction that the data will move. Click the Basic View tab. Drag column B up and drop it onto row 3. Continue across the Excel preview by dragging column C up and dropping it onto row 4, column D up to row 5, and columns E and F up to row 6 and 7, respectively.
Continue for all line item fields. Add data and run the script Click the Trwnsaction tab. Type the data in the columns. To execute the upload, click the Test button, if you are a Foundation user, or click the Run button if you are not a Foundation user. Studio prompts you to save the script and data files. After you save the script and data files, the script runs. The yellow message bar displays a message when the run has finished.
Check the log column. The run was successful and the transqction returned from SAP were entered into the log column.