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>

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

  • 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

  • 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

  • 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.

  • 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

  • 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

  • Configuring double invoice check for vendor invoices posted through FB60

    Dear all
    Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
    for miro documents..we can use Tcode OMRDC
    Is there any such tcode which can be used for configuring fi invoices for double checking..
    regards
    Expertia

    Dear Expertia,
    In FI,when checking for duplicated invoices, the system compares the
    following :Vendor, currency, company code, gross amount of the invoice,
    reference document number and Invoice document date.
    SAP Note 305201 clarifies this in a more details; please read it.
    The following fields must be identical for Duplicate invoice check
         Company code                              (BUKRS)
         Vendor number                             (LIFNR)
         Currency                                  (WAERS)
         Reference number                          (XBLNR)
         Amount in document currency               (WRBTR)
         Document date                             (BLDAT)
    If the document is having any one of the above filed different then the
    system does not consider it as a duplicate invoice.
    Also It will check duplicate invoice check in vendor master data and
    in posting key is there check box selected for sales related
    The setting you making in OMRDC i.e Materials management->Logistics
    Invoice Verification->Incoming Invoice ->Set Check for Duplicate
    Invoices is only valid for MM and not  FI invoices posted via FB60/FB65
    You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
    in the relevant vendor master record (transaction FK03).
    Please also check, that message F5 117 has been set correctly in the
    IMG using this path:
    Financial Accounting -> Financial Accounting Global Settings ->
    Document -> Default Values for Document Processing -> Change Message
    Control for Document Control For Document Processing
    Finally & mainly, go to the relevant posting key is defined as sales
    related in transaction OB41. You have to flag this field if the
    duplicate invoice check should work.
    I hope this helps You.
    mauri

  • Default profit center when posting vendor invoices thru MIRO, FB60 and FB65

    Hi,
    My requirement is to default profit center at item level while posting vendor invoices using transactions MIRO, FB60 and FB65.
    can anyone please provide some inputs on this.
    Thanks for your help.
    Lucky

    Hi,you need to customize doc splitting.
    1.You need to clasify all accounts from future document in  Document Splitting-Classify G/L Accounts for Document Splitting(e.g. all accounts 2000) 03000-VENDOR.
    2.in IMG: Classify Document Types for Document Splitting    check for Document type  transaction and Variant (e.g. Doc=KR, Trans.=1010, Variant= 0001)
    3.In IMG:  Activate Document Splitting   check  assigned method(e.g. 000012)
    4. in IMG- Document Splitting-Extended Document Splitting-Define Document Splitting Rule
    For find your method and transaction(e.g. Method=00012, trans.=1010) and double click on Item categories(on left of the top of screen)
    There'd be record with category from first step (e.g. Cat.=0300), select one and double click on Base item cat. - there'd be Category 0300 and with check box Automatically split.
    I hope it'd be helpful

  • Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

    What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
    I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
    In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
    My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
    Thanks,
    Veeru.

    Hi,
    IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
    If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
    Msg: INVOIC
    Basic type: INVOIC02
    FM: IDOC_INPUT_INVOIC_FI
    Process code: INVF
    Thanks,
    Kumar

  • Enter Vendor Invoice - SAP T.Code FB60

    We have received an invoice from vendor for supplies and we do not have a purchase order for this invoice. We proceed to account through SAP T.Code FB60.
    The vendor should have charged sales tax but has not. While accounting the invoice we want to record accrual for self assessed use tax.
    The system calculates the tax but assumes the invoice value is inclusive of use tax. But we know that the price is exclusive of tax and hence we need to make an additional accrual for sales tax and debit the supplies expense account.
    Can this be done? Is this how other SAP run business record this transaction?

    I will give an example to make my query more clear.
    Vendor invoice 5000, Rate of tax 7% , Entry psoted by system:
    Dr Expenses for supplies a/c 4,672.90
    Dr Sales Tax Payable a/c         327.10
    Cr Vendor a/c                       5,000.00
    Entry required:
    Dr Expesnes for Supplies a/c 5350
    Cr Vendor a/c                       5000
    Cr Sales Tax Payable a/c        350

  • BDC FOR VENDOR INVOICE FB60

    Hi,
    I need to make a BDC to upload transaction data for Vendor invoice thru  fb60. Can someone help me with making this BDC. I have multiple invoice line items where G/L Accounts can be same for multiple line items.
    plz any help soon will be appreciated ...

    hi Raj,
    Here a Example:
    report ZTEST
    no standard page heading line-size 255.
    include bdcrecx1.
    start-of-selection.
    perform open_group.
    perform bdc_dynpro using 'SAPMF05A' '1100'.
    perform bdc_field using 'BDC_OKCODE'
    '=DUMMY'.
    perform bdc_field using 'RF05A-BUSCS'
    'R'.
    perform bdc_field using 'BDC_CURSOR'
    'INVFO-XMWST'.
    perform bdc_field using 'INVFO-ACCNT'
    '4711'. "LIFNR
    perform bdc_field using 'INVFO-BUDAT'
    '07.07.2006'.
    perform bdc_field using 'INVFO-WRBTR'
    '1000'.
    perform bdc_field using 'INVFO-WAERS'
    'EUR'.
    perform bdc_field using 'INVFO-XMWST'
    'X'.
    perform bdc_field using 'INVFO-MWSKZ'
    'V4'.
    perform bdc_dynpro using 'SAPMF05A' '1100'.
    perform bdc_field using 'BDC_OKCODE'
    '=BU'.
    perform bdc_field using 'RF05A-BUSCS'
    'R'.
    perform bdc_field using 'BDC_CURSOR'
    'INVFO-XBLNR'.
    perform bdc_field using 'INVFO-ACCNT'
    '4711'. "LIFNR
    perform bdc_field using 'INVFO-XBLNR'
    'test'.
    perform bdc_field using 'INVFO-WRBTR'
    '1.000,00'.
    perform bdc_field using 'INVFO-XMWST'
    'X'.
    perform bdc_field using 'INVFO-MWSKZ'
    'V4'.
    perform bdc_dynpro using 'SAPMF05A' '1100'.
    perform bdc_field using 'INVFO-BLDAT'
    '07062006'.
    perform bdc_field using 'INVFO-XBLNR'
    'TEST'.
    perform bdc_field using 'ACGL_ITEM-HKONT(01)'
    '467000'.
    perform bdc_field using 'ACGL_ITEM-WRBTR(01)'
    ' 1000'.
    perform bdc_field using 'ACGL_ITEM-KOSTL(01)'
    '1000'.
    perform bdc_transaction using 'FB60'.
    perform close_group.
    OR Also u can use the
    U can use the std batchinput RFBIBL00 (or a BAPI, like BAPI_ACC_DOCUMENT_POST ) instead of to write an own BDC program for FB60.
    FB60 is enjoy trx and it couldn't support the BDC for all its functionalities.
    For more infor abt the BDC
    http://www.sap-img.com/abap/learning-bdc-programming.htm
    Assing the points if helpfulll
    ranjit
    null
    null

  • Vendor Invoice - FB60

    Hi All
    this maybe a really basic Qs - but i am so stuck on it
    i am tryin to make the Reference field of FB60 transaction as mandatory - but am simply not able to find the place to do it
    for MIRO, its a Required Field, through the movement type, but am not sure how to make it Reqd for the normal FB60 transaction
    Thank u all
    Rukshana

    Hi Rukshana,
    It seems to be simple but it may lead to some complexities. The vendor invoice is created by crediting vendor using posting key 31. The simple way is to go and make the reference field mandatory in the field status of Posting key 31. Remember that the posting key is used at client level so wherever this is used the reference field will become mandatory.
    The alternative is to hit at the reconciliation account assigned to the vendor master and change the field status group reference field to mandatory. This is better.
    Hope this address your query.
    Regards
    Bharat

  • Vendor Invoice through FB60

    Hi Experts,
    I have very urgent requirement to Post Vendor Invoice Through
    FB60.
    Please suggest me BAPI for this ans suggest code to use that.

    hi,
    check this link.
    http://www.geocities.com/rmtiwari/main.html?http://www.geocities.com/rmtiwari/Resources/MySolutions/Dev/Codes/Report/Z_BAPI_INCOMINGINVOICE_CREATE.html

Maybe you are looking for