FB60 - Vendor Invoice Creation Information to be extracted in BW

Hi Experts,
I have typical requirement where in I have to create a BW report. In the report the information are coming from FB60 transaction.
The fields in FB60 are pointing to a structure INVFO. I am not able to find out the base tables, after creating an entry in FB60, the entries goes inti which table?
I have to build a generic datasource to meet this requirement.
Please suggest me how to procee ahead.
Regards,

Considering if you already have all of your financial data ( fi documents) in BW, you can do a query on the ods which has this info at the document level and then filter on the document type if you want to have a list of just the vendor invoices.
The datasource used for transporting all of fi is 0FI_GL_4.
Hope that helps
Nandita

Similar Messages

Mandatory fields for creation of FB60(vendor invoice),and FK01(cost center)

Hi all,
can u plz send me the mandatory fields(along with discription) for creation of FB60(vendor invoice),and FK01(cost center).
thank u,
Srinivas Reddy.

The FK01 is the transaction used to create a Vendor.
The mandatory fields are:
a. NAME1: For Name
b. SORT1: For CUIT number.
c. SORT2: For alternative CUIT number.
d. CITY1: For city.
e. STCD1: Tax Number.
f. Others depending the case.
For FB60 (Vendor invoice) the mandatory fields are:
a. ACCNT: Number of Vendor Account.
b. BLDAT: Date.
c. XBLNR: Reference Number.
d. WRBTR: Invoice Amount.
e. HKONT: G/L Account Number.
f. WRBTR: Invoice Amount. The same as d but in the item.
g.MWSKZ: Tax Type. Depending the case.
h. KOSTL: Cost Center. Depending the case but is highly probable that the field were mandatory.
i. Others. Depending the case.
I have given to you the most probably fields that are mandatory for those transactions.
Your Sincerely
Leonardo Lopez
FI Consultant

Vendor Invoice creation through EDI (Transaction MIRO)

Dear All,
We want to implement Vendor Invoice creation thro EDI .(Transaction
MIRO)
We are not finding any suitable EDI Function Module in SAP which
would take care of more than 20 items and run a MIRO or any
equivalent transaction .
Can any one please advise if any Function module exists ? We need it for
Invoice creation with GR reference as well as without GR reference .
Thanks
Sanjay.

Thanks Naren,
I will come back after checking the fn module.
- Sanjay

FB60 vendor invoice

FB60 vendor invoice
Transaction : posting a vendor invoice and offsetting entry is a G/L expense account
When i enter equal amounts (invoice amount and g/l amount) i am getting an error saying balance not zero
But i varied the amount it is letting me post
ex 5300 as invoice amount and 5000 as g/l amount
Why is this so?
Points promised
Prashanth

Hi,
WHT has 2 types a. Accrual basis b. Payment Basis
Path: IMG FA-Fin GS WHT-Extended WHT
1.     Basic Settings
a.     Check WHT countries: Check ur country
b.     Calculation
i.     Withholding tax type Define WHT type for invoice posting: Give ur country, tax type, Base Amt Select Gross amount à Save
ii.     WHT Type Define WHT for payment posting Similar to 1bi
iii.     WHT Code - Country, WHT type, Base Amoutn: 100%, Post Indicator: 1: Std posting, Calculate: WHT Rate: Give ur tax rate. Similarly do for payment posting
c.     Define formula for calculating WHT-Give basic details and enter other details by double clicking Formula for calculating WHT. Do for both Accrual and payment
d.     Company code Assign WHT to cocode Do for both payment and accrual
e.     Activate Extended WHT
2.     Posting: Accoutns for WHT Define accouts for WHT Give chart of acct Select WHT code and Type. Give the type and code of both accrual n opayment
3.     IMG-Logistics General Tax on Goods movement India basic settings Maintain Cocd settings Give first month and save
4.     Attach the WHT to Vendor Master (FK02 change; FKO1 Create) Select WHT; Tax type: Either payment/accrual; Select Liable and save
5.     Try posting entry thru F-43 and enter the WHT. Document àSimulate
The above is the configuration for Extended WT
Regards,
Sridevi
<b>* Pls. assign points, if useful</b>

Posting Tax Amount in BAPI_ACC_DOCUMENT_POST (Tcode FB60 - Vendor Invoice)

Where do I need to populate the Tax amount in BAPI_ACC_DOCUMENT_POST inorder to create Vendor Invoice (Non PO) - FB60.
I have populated Tax information GL A/c, Condition key, Account key, Tax Code in u2018ACCOUNTTAXu2019 table and Tax amount $7 in 'CURRENCYAMOUNT' table but got below errors:
u2018Balance in transaction currencyu2019 - when we have $-107in Vendor line, $100 in GL line & $7 in Tax line. (It showing difference $7).
The tax amount must not be greater than the tax baseu2019 - When we have $-107 in Vendor line, $107 in GL line & $7 in Tax line.
Here is the code, please check and suggest me:
Header Details:
it_documentheader-obj_type   = u2018BKPFFu2019.
it_documentheader-doc_date   = u201811/08/2011u2019.
it_documentheader-pstng_date = u201811/08/2011u2019.
it_documentheader-comp_code = u20180001u2019.
it_documentheader-ref_doc_no = u2018TESTQ108u2019.
it_documentheader-doc_type   = u2018KRu2019.
it_documentheader-obj_key    = u2018$u2019.
it_documentheader-username   = sy-uname.
it_documentheader-bus_act    = u2018RFBUu2019.
it_documentheader-fisc_year = u20182011u2019.
Vendor Line u2013 Accounts Payable
lv_item_no = 1.
it_accountpayable-itemno_acc = u20181u2019.
it_accountpayable-vendor_no = u20187800988u2019.
it_accountpayable-comp_code = u20180001u2019.
it_accountpayable-pmnttrms   = u2018DUBPu2019.
it_accountpayable-tax_code   = u2018I1u2019.
it_accountpayable-taxjurcode = u2018000003749u2019.
it_accountpayable-item_text = u2018Test123u2019.
Populate currency amount for account payable data
it_currencyamount-itemno_acc = u20181u2019.
it_currencyamount-curr_type = '00'.
it_currencyamount-currency   = u2018USDu2019.
it_currencyamount-amt_doccur = -107.
it_currencyamount-amt_base = 100.
Append it_currencyamount.
G/L Account data
it_accountgl-acct_type = u2018Su2019.                         " GL
it_accountgl-itemno_acc = u20182u2019.
it_accountgl-gl_account = u2018623000u2019.
it_accountgl-item_text = u2018Test123u2019.
it_accountgl-costcenter = u20181099u2019.
it_accountgl-profit_ctr = u20181u2019.
it_accountgl-comp_code = u20180001u2019.
it_accountgl-tax_code   = u2018I1u2019.
it_accountgl-taxjurcode = u2018000003749u2019.
Append it_accountgl.
it_currencyamount-itemno_acc = u20182u2019.
it_currencyamount-curr_type = '00'.
it_currencyamount-currency   = u2018USDu2019.
it_currencyamount-amt_doccur = 100.
Append it_currencyamount.
Tax Line Details:
it_accounttax-itemno_acc = '3'.
it_accounttax-gl_account = '0000210000'.
it_accounttax-acct_key = 'NVV'.
it_accounttax-cond_key = 'XP1I'.
it_accounttax-tax_code   = 'I1'.
Append it_accounttax.
it_currencyamount-itemno_acc = '3'.
it_currencyamount-curr_type = '00'.
it_currencyamount-currency   = u2018USDu2019.
it_currencyamount-amt_doccur = 7.
it_currencyamount-amt_base = 100.
Append it_currencyamount.

Hi
See this [post|BAPI_ACC_DOCUMENT_POST and partial non deductible VAT;. It's related with Note 487064 - Direct posting to tax account with AC BAPIs.
I hope this helps you
Regards
Eduardo

Required BAPI for Vendor Invoice Creation

Hi,
The transaction code for creation a vendor invoice is FB60. Is there any BAPI to create VENDOR INVOICE.
Regards!
kannan

check...
<b>BAPI_ACC_INVOICE_RECEIPT_POST</b>

Vendor invoice creation using BAPI BAPI_ACC_DOCUMENT_POST

Hi,
I am trying to create vendor invoice(FB60) using BAPI_ACC_DOCUMENT_POST.
Could anyone please let me know what all mandatory fields we have to pass in vendor item and header to create this ?
Regards,
Anubhuti Pandey

Hi,
Please call the FM BAPI_ACC_DOCUMENT_POST and try with the following parameters:
Function module to post the accounting document
      CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
"      EXPORTING
          documentheader    = w_documentheader
"      TABLES
          accountgl               = i_accountgl
          accountreceivable = i_accountreceivable
          accountpayable     = i_accountpayable
          currencyamount    = i_currencyamount
          return                     = i_return
          contractitem           = i_contractitem.
The required fields in the header document:
    w_documentheader-bus_act
    w_documentheader-username    = sy-uname.                                             "Username
    w_documentheader-header_txt
    w_documentheader-comp_code
    w_documentheader-doc_date
    w_documentheader-pstng_date = sy-datum.
    w_documentheader-trans_date                                 " Transaction date value as per document date
    w_documentheader-fisc_year   = sy-datum(4).
    w_documentheader-doc_type
Pass the necessary information in the account GL and accounts payable.
I hope this helps you in some way.

Standard workflow for FB60 vendor invoice

Dear experts,
I am looking for a standard workflow for transaction FB60. Is that WS00400012(BO: BSEG)?
I just wonder if I could check the link between a transaction and business object.
In SWO1, BSEG is noted as "Accounting document line item". So i am not sure if it is for Vendor Invoice.

There are several standard workflows for vendor invoices. WS00400012 is for release of payment. If that is what you are looking for, it is fine. But go to the customizing to find more information about both the release for payment solution and the release for posting solution from SAP. Can't recall the customizing path now, but it is in Financial Accounting, I think the path is Accunts Receivable and Payable, then Business Transactions, and there you will at least find the Release for Payment part of it. The customizing screens are partly common, but the help available for the customizing nodes is most likely specific for each solution. I have never set up release for posting, so I don't know it.

Vendor Invoice creation

Hi Experts ,
I have to create a Vendor invoice for the open items to run the payment proposal and than run payment run,Could you please tell me the steps needed to create the vendor invoice , it's very urgent .
waiting for an early relpy ,
thanks in advance ,
Arun

Hi,
Please follow this documentation.
Creating vendor master:
http://help.sap.com/saphelp_erp2004/helpdata/en/41/37b8e7455b11d182b40000e829fbfe/frameset.htm
Entering AP transaction:
http://help.sap.com/saphelp_erp2004/helpdata/en/41/37b8e7455b11d182b40000e829fbfe/frameset.htm
regards,

Problem in vendor invoice creation through BAPI

I am trying to create vendor invoice using bapi_acc_document_post but what value have be passed to obj_key and obj_typ fields of header is not clear to me.
regards,
anu

Hi,
Don't pass any values to OBJ_TYPE,OBJ_KEY. Many threads are available in SDN regarding this BAPI.
Search SDN to get more details.
Regards
Vinod

Business Object for FB60 Vendor Invoice?

Hi all,
Which is the business object for tcode FB60?
Regards,
Arpita

Hi Arpita,
You should use SWO2 - BO explorer.
Regards,
Suwandi

Duplicate vendor Invoice check in FB60

Hi Experts,
I want to put the duplicate invoice check while posting the vendor invoice through FB60. I want the system to check the duplicate invoices in combination of the Vendor code and vendor invoice number ( we put the vendor invoice no. in the reference field of FB60 ). How to make this possible. I do not want to make the FI validation for the same. Can you please suggest how to go ahead with this.
Thanks,
BABA

Hi Shailesh,
phuu, ok, let's start from the beginning then.
Some theory first:
you need the validation because the standard check takes the doc.date ito consideration and this is not wanted. And you need the exit from the validation (! not a separate exit! not the original), locate the IF-statements where there is an ELSE option ending with function CUSTOMIZED_MESSAGE. It is up to you what to do here. In the original functoin module, the messages are issued here immediately. It can be an error or a warning, depending on the setting in table T100C. If my understanding is correct, you always want to see an error message, bt this should be done in the validation, not in the function module. So you should skip the customized_message function call and just issue the messages here as info message regardless of T100C settings. In this case, remove the function call customized_message (as many times as it occurs) and issue the message included directly as an information. Right after the message was issued, set E_RC to 4, infoming the validation that the check has failed. (Note that the customized_message function is only called if the check has failed, so no worry that you always get the message.
4. Define the exit for the validation
=========================
Go to your form pool Z_RGGBR000 (defined in V_T80D) and locate the statement APPEND EXITS. It should appear few times, locate the last occurence.
Right after that, enter the following:
exits-name = 'U901' .
exits-param = c_exit_param_none.
exits-title = text-901.
append exits.
This will define a new exit namd U901 for the validation routines. If in V_T80D, you already had a Z (or Y) report, check if the string U901 is used in that code already (check for the main program). If this is the case, instead of U901, use another name, it should begin with U followed by 3 digits. Also, you make sure the text symbol text-901 (or the 3 digits you are using) is existing, doubleclick it and enter a description like "Duplicate invoice check validation" or similar.
Well, the exit is published, we have to write the main code now.
go to the very end of your Z_RGGBR000 report and add a new form U901 like follows:
Duplicate invoice check validation
FORM U901 USING B_RESULT.
Vendor master flag
data: l_reprf like lfb1-reprf.
Result of function module
data: l_rc like sy-subrc.
Check vendor master first
select single reprf into l_reprf from lfb1 where bukrs = bkpf-bukrs and lifnr = bseg-lifnr.
Do not continue if flag is not set.
if L_REPRF is initial.
b_result = b_true.
endif.
check not L_reprf is initial.
Call modified function module
CALL FUNCTION 'Z.....your function'
    EXPORTING
      i_bukrs = bkpf-bukrs
      i_lifnr = bseg-lifnr
      i_waers = bkpf-waers
      i_bldat = bkpf-bldat
      i_xblnr = bkpf-xblnr
      i_wrbtr = bseg-wrbtr
      i_koart = bseg-koart
      i_reprf = L_reprf
      i_shkzg = bseg-shkzg
      i_xumsw = bseg-xumsw
      i_bstat = bkpf-bstat
      i_belnr = bseg-belnr
      i_gjahr = bkpf-gjahr
      i_blart = bkpf-blart
EXPORTING
      e_rc = L_RC.
Decide if validation message must be issued or not
if L_RC = 4.
b_result = b_false.
else.
b_result = b_true.
endif.
endform.
After this, activate the source code. Make sure you have defined the text-symbol 901 before!
5. Define the validation
=================
Go to OB28 now, and enter your company code(s) and the call-up point 002 (line item). If there is a validation defined already, you have to add a new step only, if not, you have to create the validation anew.
I assume there is no validation defined yet, so enter a name for the validation like FI_2 or similar. It should NOT be named DUPLIC or similar, i.e., you should not include the purpose in the validation name. This is because the validation is defined on company code / call-up point level and it may contain many steps for different purposes later. A generic name FI-2 or probably your company code followed by 2 (2 is the call-up point) is the best choice.
Before presing enter go to the last column Validatin active and enter 1 here.
Then press enter and you will get an error that the validation does not exist. No problem, go to menu path Environment --> Validation and let's create a new validation.
First, enter a description for your new validation in the right hand panel. Again, this should be a generic description, tell nothing about duplicate invoice checks here.
You may be asked here to assign a message class to the boolean class 009. You should enter here a Z message class where the validation message should be issued from. If no appropriate message class exits, open a new session go to SE91, enter a new message class Z... press create, enter a description. Then go to the Messages tab there, and create a new message with number 001 (NOT 000) and enter the message text there. E.g. Duplicate entry not allowed.
Coming back to the validation, if the message class was already assigned (this is the case if there was a validation defined earlier), you can create a new step. In case of a new validation, it will become the first step. But if there was already a validation in OB28 for your company code and call-up point 2, then it will be the last step. In the left hand panel, make sure the new (or existing) validation is selected and press the Create Step button (Ctrl-Shift-F5).
In the right hand panel, enter a description for your step. This is the point where you can enter Double invoice check or similar.
We have three parts here, a Prerequisite and a Check part, finally a message.
In the left hand panel, select the Prerequiste. This will activate that screen block in the right side. We have to make sure that our validation is called only for the relevant vendor line items, so press Ctrl-F3 to hange to expert mode ) and enter the following in the Prerequiste window in the right hand panel:
BSEG-LIFNR <> '' AND BSEG-XUMSW = 'X' AND BSEG-KOART = 'K' AND
BKPF-BSTAT = ''
Beware '' is a ' followed by another ' and not a single " !!
Then switch back to normal mode using Ctrl-F1 and check the small lamp below that should be green now. Also, you can see the field descriptions now. If the lamp is red, press Ctrl-F3 again, delete all and copy the above again. Do not bother with line breaks. Switch to Ctrl-F1 again until the lamp is green. OK, what we have told here was please call the validation only if we have a vendor number and if this is a sales relevant item (invoice or credit memo, but not a payment or similar, this is the standard logic as well), and the account type is vendor (K) and this is a normal document.
WHen you are done here and the lamp is green, then go to the left side again and select the Check part. Now you should be able to edit the Check screen lock in the right hand side again. Switch to expert mode and enter simply U901
This is the name of the form in your Z_RGGBR000 report. NO brackets, no spaces, only U901 here. Switch back to Ctrl-F1 and instead of U901, you should see the text of your form (text symbol 901 in report Z_RGGBR000).
Finally, click the Message part in the left side to be able to maintain the message in the right side. If you issued an error from the function module already, you can give here an information, or you can give it as an error if you like. The message number is one of the messages from your Z message class, you have to define the text in SE91 (see above).
When done, save the validation and you can test it immediately.
Here a brief summary what is happening:
OB28 setting defines that in your company code a validation like FI-2 or similar is active on line item level. Whenever a line item is abut to be created, the validation will be called.
However, the prerequisite of the validation is quite strict: only a limited number or vendor items will allow to continue, other line items (G/L, customer, not sales relevant vndor, etc.) will just skip the whole validation.
If the prerequsite was met, the Check part is carried out. Here we have the exit U901.
In the exit, first we check if the vendor is flagged for double invoie checks. If not, we quit and processing can be continued. B_TRUE means it is OK. If the vendor is flagged, we call the new Z function which is almost the same as the original one.
The Z function will check table BSIP, but it will skip the document date comparison. If the current invoice seems to be entered earlier (regardless of the doc.date), instead of the standard customized message (which can be E or W for instance), the very same standard message will be issued as an information. So the user will be informed about the previous document number but the processing won't be stopped. In addition, a return code will be set to 4, meaning check has failed.
Jumping back to the exit, if the return code is 4, we have to tell the validatin that the check has failed (B_RESULT = B_FALSE), otehrwise we can tell the validation that the check was OK (B_RESULT = B_TRUE).
Now we are back in the validation, and, depending on B_RESULT, we just continue processing (B_TRUE), or issue an error message from a Z message class (B_FALSE). As the main standard message was isued already from the Z function, the user should know at this stage what the matter is. Your Z message can be a bit generic one, no need to include the vendor number or the previously issued invoice, etc.
Hope that helps, points welcome
Csaba

Steps to upload vendor invoice(tcode fb60) in bdc

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.

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

Creation of Vendor Invoice - BADI to control "Payment Baseline Date field"

Hi ,
In SRM - Creation of Vendor Invoice or Credit memo -
In the process of creation of vendor invoice in Header Data - Payment Data tab there is a field "Payment Baseline Date" and I want to populate custom value to this field using BADI. But I could not find any BADI to do this.
Can any one please let me know if any idea what BADI I can use.
I tried DOC_CHANGE_BADI and this one does not have this field in the ET_HEADER.
Thanks in advance.
Venkat

Hi,
Any ideas please?
Thanks for ur time.

BAPI for Vendor Invoice and Credit memo - FB60

Hi
Iam using BAPI_ACC_DOCUMENT_POST for creating Vendor invoice and Credit memo ..Could you please tell me which fields to be populated on the below structures?
what will be the value i should use for BAPIACHE09-BUS_ACT...RFBU or RMRP?
ACCOUNTPAYABLE ( BAPIACAP09)
ACCOUNTGL(BAPIACGL09)
CURRENCYAMOUNT( BAPIACCR09)
Only the fields which needs to be populated on these structures when we do FB60 invoice and credit memo using bapi..
Thanks in advance
Govi

Hi,
Populate in Document_header : (User name, Comp code, Doc DAte, Doc type, Ref Doc No)
                   Account GL : ItemNo_Acc, GL Accuont, REf Key1, Refkey2, Refkey3, Account Type = 'A', Doc Type, Comp code
                                          Account_number, Cost_center
                   Account Payable: ItemNo_Acc, Vendor_No, Rey_key1, Ref_key2, Ref_key3
                  Currency Amount: Item No_Acc = 2, 1
                                                Curr = USD, USD
                   Amt_Doccur
At last use commit bapi.
Thanks,
Krishna

FB60 - Vendor Invoice Creation Information to be extracted in BW

Similar Messages

Maybe you are looking for