Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

steps to upload vendor invoice(tcode fb60) in bdc

Former Member
0 Kudos

hi, iam srinivas can any one plz send me the steps to upload veneor invoice tcode is (fb60).i dont want the code but i want the steps to create .

thanks and regards.

Srinivas.

1 REPLY 1

Former Member
0 Kudos

refer this site.

FI_AP_FBR2_Post_With_Reference (FBR2)

Business Process Description Overview

Use this procedure to copy a previously posted non-PO invoice document that uses many of the same values.

This may help reduce data entry time if used correctly. For example, the library invoice vouchers that have the same vendor but many invoices on them might be a good example of when to use this transaction code.

Trigger

Perform this procedure when there is an invoice that needs to have data entered where most of the fields are the same as a prior invoice document already entered in the system.

Prerequisites

· Security Role: AP_DIR_INV_ENTRY

· An FB60 invoice has already been data entered.

Menu Path

None

Transaction Code

FBR2

Tips and Tricks

· If you would like to save this transaction under your "Favorites" folder, right-click on the "Favorites" folder, select "Insert Transaction" and type in this t-code when the box appears.

· You may use the transaction code: search_sap_menu to search for a transaction codes menu path.

Procedure

Enter Vendor Invoice: Company Code PUR

Typically the FBR2 - Post With Reference transaction is accessed from the Financial transaction code that you just used. For Accounts Payable, typically we would use the FB60 transaction code to enter invoices that are not PO-related. After you have entered an invoice, you can now post a second invoice. Feel free to post an invoice in DEV to the Vendor ID number: 31. Choose today's date as the Invoice Date. Enter a Vendor Invoice in the Reference Field. Enter $1000 as the Amount. Enter a Text that you want to show on the remittance advice to the vendor. Choose your own GL Account and Cost Center. Enter 21010000 as the Fund. Make sure to also enter $1000 in the Amount in doc. curr. field.

Please be aware that the FB60 screenshot above is using the ZPurdue Variant so unless you are also using that same variant the order of your columns may differ.

Refer to FB60 documentation for more information regarding entering a non-PO related invoice.

After an invoice has been entered, you may proceed to step 1. If you prefer not to enter an FB60 invoice then after you open FB60, immediately do step 1, but enter "1900001354" in the Document Number field.

1. Select Goto Post with reference Shift+F9 to go to the FBR2 transaction.

Post Document: Header Data

The document number you just entered in FB60 should now display. If you did not first enter your own FB60 invoice, please enter 1900001354 in the Document Number field. Make sure Company Code is PUR and Fiscal Year is 2007.

If you did enter your own FB60 invoice to reference to, please be aware that the data entry fields will have different content in the screen shots than what you are seeing on your screen.

2. Click or the "Enter" key to proceed.

Post Document: Header Data

Because we want to avoid paying the same invoice twice, we must change the reference field to another Vendor Invoice text.

3. As required, complete/review the following fields:

Field Name

R/O/C

Description

Reference

R

Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.

Example: VENDORINVOICE#2

Your reference number should be different than the one above. Otherwise, the system will think you are entering a duplicate invoice. Please change your text slightly.

Post Document: Header Data

4. Click or the "Enter" key to proceed.

Post Document Display Overview

You are now viewing the document overview screen.

5. Double-click to open that line item.

Post Document Correct Vendor item

When you open the Vendor line item, you may change the Text field here to change what appears on the remittance advice.

6. As required, complete/review the following fields:

Field Name

R/O/C

Description

Text

O

Description field for an entry.

Example: prints on remittance advice - for second invoice

Post Document Correct Vendor item

7. Click to return to the document overview screen.

Post Document Display Overview

The document overview screen.

8. Click to post this second invoice which has the same fields as the original except a different vendor invoice number and a different remittance advice text.

Information

Pending upon your user settings, you may not get this pop up box, but just a message in the bottom left hand corner of the screen.

9. Click to close the box.

Enter Vendor Invoice: Company Code PUR

Because you used the menu (Goto Post with reference) from FB60 to access the FBR2 transaction code, you are then returned to the FB60 transaction after you have posted the invoice.

10. Another way to access FBR2 is to just type the t-code in the field at the top of the screen. As required, complete/review the following fields:

Field Name

R/O/C

Description

Transaction Code

R

A unique four-character (in most cases) identification assigned to each SAP transaction based on its purpose.

Example: /nfbr2

11. Click or the "Enter" key to proceed.

Post Document: Header Data

The FBR2 transaction code opens with the last document number entered as the default.

12. Click or the "Enter" key to proceed.

Post Document: Header Data

This time we will change the vendor number

13. Change the Reference field. As required, complete/review the following fields:

Field Name

R/O/C

Description

Reference

R

Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.

Example: VENDORINVOICE

Your reference number should be different than the one above. Otherwise, the system will think you are entering a duplicate invoice. Please change your text slightly.

Post Document: Header Data

14. As required, complete/review the following fields:

Field Name

R/O/C

Description

Account

R

Unique identification number. SAP uses several kinds of accounts. SAP's general ledger accounts are similar to standard in most accounting systems. SAP also uses sub-ledger accounts for customers (accounts receivable), vendors (accounts payable), and assets (asset accounts). These sub-ledger accounts roll-up to a general ledger account.

Example: 5000129

Vendor 5000129 in DEV has withholding tax applied to it in the vendor master.

Post Document: Header Data

15. Click or the "Enter" key to proceed.

Post Document Add Vendor item

If the vendor invoice date was a date in the past, the due date for pay immediately will be in the past. You may get the above informational message to alert you of the date. If you do, just hit the "Enter" key to acknowledge it.

Enter Withholding Tax Information

Because this vendor has withholding tax information in its vendor master, you will receive this popup up box.

16. Click to accept it.

Refer to the Tax Department for more information regarding withholding tax.

Post Document Display Overview

You should now see the document overview screen. If you do not, then click on .

17. Double-click OR click to open it.

Post Document Correct Vendor item

18. As required, complete/review the following fields:

Field Name

R/O/C

Description

Text

O

Description field for an entry.

Example: change remittance advice text

Post Document Correct Vendor item

19. Click to view that Vendor's Withholding tax information again.

Enter Withholding Tax Information

If for some reason, for this invoice the vendor should not have any withholdings, you would enter a 0.00 in both the W/Tax Base and W/Tax Amt fields.

When using the FBR2 to change withholding tax amounts, you need to be very careful if using this new invoice as the "reference" invoice for the next one. For example, if you put 0.00 in both W/Tax Base and W/Tax Amt fields then if this is the reference invoice, those 0.00 amounts will automatically be applied to the next; however, you won't see the 0.00 displayed. The 0.00 will be assumed.

20. Click to close the box.

Post Document Correct Vendor item

21. Click to post the invoice.

Post Document: Header Data

Your new document number will display in the bottom left hand corner. Pending upon your user settings, you may also get a pop up box to acknowledge.

You have posted another invoice, but this time you changed the vendor ID used, the vendor invoice, and the text on the remittance advice.

Notice that the "Document Number" field now defaults to the newly posted invoice number.

Because you entered FBR2 in the transaction code field to access this screen, when you post an invoice you are returned to the beginning of the FBR2 screen. Remember, when you accessed it from the menu line of FB60? If you access it that way, you are then returned to FB60 after the Post with Reference document is posted.

22. Because you are returned to the start of FBR2 again, you may just click or the "Enter" key to proceed.

Post Document: Header Data

Now you are at the start of entering a new invoice again.

23. Click to return to the main menu without finishing the process of entering another invoice.

24. You have completed this transaction.

Result

You have posted two documents by using a reference document. This reduced the data entry required since it defaults the fields from the reference document.

Comments

Be very careful using this transaction if you change withholding tax amounts.

To see the results/calculations of discounts and withholdings, you must run F110, the Payment Program.

http://www.purdue.edu/onepurduehelp/content/fi_ap_fbr2_post_with_reference/wi/html/index.htm

Message was edited by:

Karthikeyan Pandurangan

Message was edited by:

Karthikeyan Pandurangan