Consignment Vendor Invoice Amount Adjustment

Dear All,
Normally in SAP, The vendor invoices for consignment in purchasing is posted from MRKO. There is no invoice posting from MIRO.
In MRKO, after entering the selection details, we choose SETTLE for processing type, then we run it and vendor invoice is posted.
So I wonder how can our client make some adjustments for very small differences in the price ? Because normally there may be some differences like 0,50 EUR because of the roundings. So how will these difference amounts will be posted ?
Thx in advance

Hi,
MR11 shows the amount for GI/IR account if there is any.. But in consignment case.. you put the price to inforecord, then withdrawals occur. According to these withdrawals you settle the vendor invoice. But the price is already captured from the inforecord.  When you settle it, SAP assumes the price as the inforecord price. That is ok. But because of the roundings (because it is only two digit after comma) the real vendor invoice may be different like 0,50 eur (for example you posted 300 EUR, but real invoice is 300,50 EUR)
This happens very frequently for our customer. So MR11 is useless for that case. There shall be some other trx to make these differences to be posted. So how will the 0,50 EUR posted ? This 0,50 eur will not appear in MR11

Similar Messages

  • Vendor Invoice amount allowing any higher value

    Hi
    1. While I do a vendor invoice for a PO, the document balance field (DIFFERENZ) is showing in Green light even before I input the amount in the Amount field.(WRBTR)
    2. And also, if the total invoice amount is USD 1000.00, the amount field is allowing any higher amount. How do i control that ?
    Thanks
    Maruthi Ram

    Hi,
    U can Block Invoice for Higher Limit as well as lower Limit.
    Go to SPRO -->  MM --> Logistic Invoice --> Invoice Block
    Here Go to Company Code and PP - Price Variance and maintain Upper and lower Limit.
    Hope Help U !
    Regards,
    Pardeep Malik

  • FV60 Vendor Invoice Amount Split Tab Field

    Greetings! Our users do not have authorization to access to FB60 - how can we open the fields (OTA and NAME OF OTA PAYEE) in the Amount Split Tab using FV60 - Park Vendor Invoice? Thank you in advance

    Hi:
            In the amount split tab of FV60 there will be a Yellow and blue button on the right corner named as configuration. Just click on it and go to Administrator and there you will see OTA and name of OTA payee . Please see if this has been set as invisible there. If they have not been set as invisible and still you can not see them in FV60 Amount split then the only way to fetch these fields in FV60 is through SHD0...For that please proceed as under
    Go to SHD0...Enter FV60  in Transaction code and ZFV60 in transaction variant.Press create button on the left top corner and enter co code and press enter again when next screen appears, it will take you to the main screen of FV60.. Enter vendor , invoice date,amount , GL account and and its amount and then keep on press entering and giving name to screen where it is required unless a FV60 main screen appears again...Now go to amount split tab and keep on pressing enter unless amount split tab screen appears, data already entered in main screen will be seen by you there , press enter two times times you will see a screen 0090 carrying these OTA fields there you will have to just un check the invisible tick from them and then exit and save with a proper name for screen variant. Give ABAP package name and exit. Upon exit in SDH0 standard variant tab assign and activate this ZFV60 variant and now you will be able to see them.
    Hope it resolves your issue.
    Regards

  • Vendor Invoice amount

    Hello Experts,
    I am working on designing of check. We print check on the first half of A4 size page and in the second half of the page we print invoice amount and net amount of each invoice along with few other fields. Can someone tell me what table fields should I use for invoice amount, discount and net amount for printing.
    The amount that we print on the check is the sum of all the net amounts of all invoices of that vendor.
    Any help in this regard is rewarded and highly appreciated.
    Thanks,
    Sriram

    Hi Sriram,
    You get all the data relevant to the settled amount in a payment run in the table REGUH (Settlement data from payment program).  This table contains the document number of the payment document, no. of items paid and the cash discount details as well relatint to a particular payment run.  Most of the fields which you require are found in this table.
    If you want some other information which you dont find in REGUH table, I am sure that you will find the same in the table REGUP (Processed items from payment program).
    Hope this answer helps you.  Please reward points if helpful.
    Regards,
    Sreekanth....

  • Vendor Invoice w/ different exchange rate on taxable amount and tax amount

    Hi Experts,
    I have an issue with regarding the Vendor Invoice with Foreign Currency. Normally we use JPY as our base currency and system exchange rate for out Vendor Invoices. But there was an audit issue pointing out that the Original Vendor Invoice is not tallied with the SAP Invoice as the tax amount is not the same. The problem is the Original Invoice has the Vendor Exchange Rate and it is not the same with the system rate that we use. Auditor tells us that we should use the Vendor Exchange Rate for Tax Amount and use the System Exchange Rate for the Taxable Amount. Is this possible? Can we use 2 Exchange Rates in a single Invoice Document one for the taxable amount and one for the tax amount? How can we possibly do this? Or any workaround?
    Thanks a lot for the information!

    I think its a bit misleading...The requirement is to post an Invoice with a base taxable amount of  Exchange Rate A and a tax amount of Exchange Rate B. The Base Currency is JPY and the System Currency is SGD. So the Report S_ALR_87012357 should see the amount in SGD there. The Issue is caused by the different exchange rate on the tax amount submitted by the Vendor Invoice.
    Example: Vendor Invoice Amount: 926,413.00 JPY, then we created PO to Invoice with Base Currency JPYalso amounted 926,413.00 JPY. However, in the Vendor Invoice Amount, the Tax Chargeable is 923.00 SGD (based on their exchange rate 65.66 JPY per SGD). But our Exchange Rate (System Rate) is 63.49 JPY per SGD. How can we reflect the Tax Amount as 65.66 JPY but still the correct SGD amount is based on the Vendor Original Invoice Exchange Rate 65.66 and not the System Exchange Rate, 63.49 in the same Invoice Creation (MIRO)?

  • In F110 -Customer as a Vendor  invoice clear and make payment

    Dear all ,
    Can we make payment through in F110.
    WE maintain Customer as a vendor and Vendor as customer,While running automatic program system
    showing error massage"No pymt possible because items with a debit bal"
    But over all amount is credit ,But only customer invoice showing like this.
    Could you tel me that ,Is there any setting    ,Wt setting we have to configured .How to solve this issue
    Thanks in advance
    Regards
    Girish.

    Dear all,
    Kindly suggest me how to do this.
    we have maintained customer as a vendor in different company code
    one company code xxxx here we maintained as a customer ,In this
    customer master data we maintained vendor no and clearing with vendor we have selected.
    In next company code yyyy here we maintained vendor as customer ,here we maintained customer no and selected clearing with vendor.and payment method .
    In xxxx company code customer as a vendor balance is 1000.
    In another company code yyyy here vendor as customer balance is 15000,
    paying company code is yyyy.
    while running F110 system asking paying company code and sending companycode,we are entering two times.first time yyyy and second time xxxx.
    that time showing error"No pymt possible because items with a debit balance"
    Then we edit proposal its working fine ,But its not clear against vendor
    invoice
    system taking full vendor invoice amount(15000) as a out going payment
    and 1000 is incoming payment.
    But we want pay only difference amount of the invoice.
    For this what we need to do in the system please guide
    thanks in advance
    Thanks and Regards
    Girish

  • Vendor Invoice info

    Hi  All,
    I am looking for FM/tables  that gives some info about
    Company,
    Internal Order,
    Vendor,
    Invoice Amount,
    Invoice Date,
    Tax Amount,
    Tax Jurisdiction,
    G/L Account Affected.
    Could you please help me with this.
    Thanks in advance,
    Raja Chandra Rangineni

    Hi,
    You should get details from Tables BSIK , BSAK,BSIP
    LFA1 General section
    LFAS VAT registration numbers general section
    LFB1 Company code
    LFB5 Dunning data
    LFBK Bank details
    LFC1 Transaction figures
    LFC3 Special G/L transaction figures
    LFM1 Record purchasing organization data
    Logical databases: KDF
    Regrds
    Hiren K.Chitalia

  • 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

  • Tables for vendor invoice no, date, amount, tds, deduction

    Hi experts, i m new to implementation. i m now doing report for vendor payment voucher.
    as per per the payment voucher no and date, in item data i want the tables stores the vendor invoice no, date, po no after MIGO & MIRO,  bill amount, tds, deduction (debit note, advance etc).
    regards
    thanks in advance.

    hi,
    LFA1
    LFAS
    LFAT.
        These tables is not useful for now for Report of Vendor payment voucher.
    In header data, i want pament voucher no, date, vendor no, name(i got in table-field REGUP-VBLNR, regup-bldat, regup-lifnr &  lfa1-name1)  .
    now i want in item data vendor invoice no, date, GR no, date, invoice amount, tds amt, deduction amt (separately like advance amt, debit note etc).
    till now i found invoice no,  inv amt (table-field BSIK-BELNR, BSIK-DMBTR).
    Now i need GR no,  GR date, tds amt, deduction details amt.
    Plz send with table-field names, and how to relate with above.
    regards,
    debendra

  • (very urgent)Difference of amount in vendor account and vendor invoice.

    Dear all,
    we are facing a issue related with vendor account actually MIRO post for the amount is showing difference compare with vendor invoice,
    please consider this scenario:-
    we are having vendor bill/invoice for Rs 1110/-
    but in SAP amount is showing 1105/- showing a Rs 5/- difference
    we found that this difference is showing becuse of we are maintaing material on single quantity whareas we got the price from vendor on BOX or bulk qty when we are deviding this price with the quantity the price will come on 4 decimals again here also we are maintaing two decimals. 
    from this we come to conclusion that this problem will occure again and again
    so it is advaisable to create a LOSS DUE TO AMOUNT ROUNDIG OFF account and posting these differnce to this gl to clear the open item that is showing in vendor master.
    Here please suggest me how to resolve this issue
    a)for the current scenario we are having many MIRO which we sre posted having the difference of only RS 1,2,3,4,5,
    this difference will come between this range only so please suggest me to resolve thisa issue
    SU

    Hi,
    if you go to SM30, view V_169L, you can configure what is considered as a "small difference". Small differences are then automatically posted, see account configuration in OBYC.
    However, I think this is designed if the vendor really invoices you a little bit too more or less. But in your case, this is not the problem. The problem is, as you have realized, that the price unit is set to small (actually, to 1 PC). The proper solution is not to post the differences away, but to stop this incorrect calculation. Small diffs should only be posted if there really were some small diffs!
    Example: agreed price with vendor is  1,001 RS per piece. As you keep your RS currency with two decimals, the price in SAP would be 1,00 RS.
    If the invoice is about 1000 pc, then the correct price is 1001,00 RS. This is what you see on the invoice and this is also correct. However, within SAP, you will see an expected value of 1000,00 RS only, so you have a difference of 1,00 RS.
    You do not need to touch the material master to fix this. Only thing you need to maintain is the PO line, where you have entered the price as 1,00 (rounded!!!) RS by 1 pc.  This must be changed like this: 1001,00 RS by 1000 pc. Then it will work fine.
    Hope that helps, points welcome
    Csaba

  • Cheque Payment PLD - AP Invoice no., Date, Vendor Ref. AP Invoice Amount

    hi all,
    I am trying to modify the Cheques for Payment PLD to include row details for each AP Invoice, included in the payment(these details are available in Outgoing Payments PLD)
    Details needed are:
        Invoice Date      AP Invoice No     Vendor Invoice Ref.                 AP Invoice Amount
    1
    2
    3
    etc
    These details are not available in the in standard "Cheques For Payment (system)" PLD.
    Would any one have a sample PLD suitable to use for this issue.
    Kind Regards
    Eric Walker

    Update,
    We tried copying the cheque PLD from the US Demo database and its worked.
    I now  have row data that includes, date, AP Invoice, AP Invoice Vendor Invoice number, AP invoice amount.
    So I don't how this can be, the US PLD also used variables. When I try to use the US variable No. I get an error indicating they are invalid, in my local system PLD.
    Still like to know how to do this with our system PLD or how a  variable can be added in our system.
    Kind Rgards,
    eric

  • Recommendations, samples, etc for creating a "Vendor Invoice" Content Type.

    I am developing a "Vendor Invoice Approval" application in SharePoint 2013. My development platform is "Visual Studio 2013". This will be an "Intranet only" application running only on our internal SharePoint
    2013 Farm.
    I am planning on using a "Document Library" to store all of the Invoices. I believe the "correct" approach (or one of many, probably, lol) would be to create a "Content Type" called "Vendor Invoice". The "content
    type" would then need to have the following functionality:
    Custom Columns. Some columns would be "required", some would be "optional".
    Vendor Name - Chosen from a “Vendors” list (a SharePoint "custom" list that contains "Vendor Name" and "People Responsible" (which will be a "People" type column and allow multiple choices/people from
    a SharePoint Group called "Vendor Invoice Person Responsible"). The user may also enter a new Vendor Name.
    Person Responsible - Limited to the users in the “Vendor Invoice Person Responsible” SharePoint Group. Will allow the selection of 1 or more "people" from that Group. (When a Vendor Name is "chosen" (above), this field
    should be populated with the values from the "People Responsible" record for that Vendor. The user can then ONLY choose between those users or choose them all. Optionally, I may just store a single Person in the "Vendors" list and use that
    to populate this field with a "default" value, but then allow the user to pick ANY user from the "Vendor Invoice Person Responsible" SharePoint Group).
    Invoice Number (Will probably renamed the “Title” column.)
    Invoice Date
    Invoice Amount
    PO Number (When entered, look it up in our ERP system and populate as many fields as possible, such as the Vendor Name, Account Number and Plant.)
    Status - Most likely this field will only be adjusted via "workflows". Choices are:
    “Created” – The initial Status when an Invoice is created (BEFORE any “Issue” or “Approved”).
    "Pending Issue" - An "Issue" needs to be resolved. (See "Issue" below.)
    “Issue Resolved” – The current “Issue” has been resolved. The next status could be “Pending Issue” (if there is another Issue to resolve) or “Approved”.
    “Approved” – All Issues have been resolved.
    “Issue Check” – The Invoice was “Approved” and a check may now be issued to the Vendor.
    “Completed” – The Invoice has been “Approved” and the vendor has been issued a check.
    Issue - Chosen from an “Invoice Issues” list (a SharePoint "custom" list that contains "Issue" and the name of a "WorkFlow" to execute on the "Invoice" in order to resolve that particular "Issue").
    When an Issue is chosen, this will trigger a "Workflow" (or more than one?? probably only one...) to start.
    Account Number
    Plant (Choices: 1-New York, 2-Los Angeles,99-Headquarters)
    Invoice Notes
    Template/Forms (Insert/Update)/Development/Event Receivers/Display Template/"UI". This is the part that I am unsure of and where "Visual Studio" will be used. (I have quite a bit of experience developing "SharePoint
    Solutions". I am not interested in using the new "App Model". I have read about it, studied it, setup a local "App Store", etc, but for this particular application, I am going to stick with the "old" Solution based model.
    I am more familiar with it and "believe" it will give me the most "power" and "flexibility". As I said.... I am unsure how to "categorize" the following "needs", so I am just going to lump the rest of the "features"
    I need into the list below and ask for any feedback and/or help. :)
    Adding Invoices - Ideally, the "drag and drop" feature will (can) be utilized by the user to add the new Invoices (I can force them to only add one Invoice at a time). If this is just "too much trouble", I
    could require the user to only add them using the "Upload Document" control. Or, I could develop the UI  (or just the Insert/Update UI) using traditional "ASP .Net" controls and insert/update the data using the Server
    Object Model or the Client Object Model (CSOM).
    Preview Invoices - There are several times I would like to show the Invoice (pdf) as a "preview" (when the Invoice is being Added or Edited, when the user is "Approving" or "Denying"
    on Invoice via a "WorkFlow", or when an Invoice is "hovered" over in a Document Library View). Basically, anytime the Invoice needs to be acted on by a user, I would like to show the PDF in a "preview" window and
    I don't mean just open it in a separate Tab or Window. I mean use something like an "IFrame" in a certain area of the page (depending on what the page is doing: Inserting/Editing/Viewing/etc) to show that preview.  (For the "hover
    preview", I believe I can use the same skills I learned when modifying how the "Enterprise Search Center" works with PDFs. Basically, it involved adding a new Display Template for the Search Item and referencing that template
    in a new "Search Result Type". The new Display Template created an "IFrame" and populated it using our Office Web App Server via "WOPI". Anyway, I believe I can simply do the same thing in a Document Library View and most
    likely in whatever "form" or "page" is responsible for the Insert/Edit. I suppose I am just looking for someone to tell me if this is "doable" (and as "easy" as I think it might be), what the "best"
    way to accomplish it would be, or if it is a bad idea, etc. etc.)
    "Auto Populate" the columns. When a new Invoice is added, I would like to use the (Enterprise) Search functionality (OCR and "graphic matching") to somehow populate as many of the columns (metadata) as possible.
    This might involve looking for some particular "text" or graphic(s) (like a company logo?) to determine the Vendor. Then, once the Vendor is determined, I might be able to figure out other items, such as the "Invoice Number" and "PO".
    Usually our Vendor Invoices don't change very often. This would only serve as "default" values, so it wouldn't have to be 100% correct. Anything I can do to save the user time or make it easier to enter new Invoices will go along way towards
    acceptance of this application. (Currently, they use an Excel Spreadsheet, along with email. So, from their point of view, the existing "system", "works" and is very "easy" to use,  etc....)
    More uses for the "Search Index Results". It would also be "nice" if we could setup some "weighted rules" on a "per Vendor" basis to help determine who the "responsible user" is. (For instance,
    we may get Invoices from a single Vendor that could possibly go to 1 of several "responsible users". In order to determine the correct user, I would like to setup some "rules" for each vendor to give "weighted" values to
    certain "keywords". For instance, if the word "Computer" appears on the invoice, that might be worth "100 points" towards the "IT Manager". So, when the user is selecting the person responsible for this particular invoice,
    I could order the list they are choosing from by the "total points" (as calculated from the "weighted rules") which would put the "Person" who is most "likely" the "Person Responsible" at
    the top of the list, followed by the second most likely, and so on. I don't think this be that "hard" to do. I would simply need to store "keywords" and "values" and have access to the "Search Index Results" for the
    document (Invoice) the user is currently adding.
    **Another "option" I have for developing this application is to basically develop it using a traditional "ASP .Net" framework and controls (which I definitely have more experience with, but as I mentioned, I also
    have quite a bit (4-5 years) of SharePoint development experience) and just using the "out of the box" features of SharePoint (and Custom Lists, Document Libraries, SharePoint Security Groups, WorkFlows), etc. What I am trying to describe is that
    I would develop the "UI" (add/change/delete) using traditional "ASP .Net" controls and just use SharePoint for my "Data Source". (I DO need to AT LEAST use SharePoint as the "Data Source". This is for reasons that
    I don't want to get into here and just bog down the discussion. I certainly realize this application could easily be a "traditional" "ASP .Net" application using "SQL" for the Data Source. So that part really isn't what I am looking
    for "advise" on.)
    Any help/advice/samples would be very MUCH appreciated!
    Shayne

    You should generate the XSD form the DTD files. Also you should list values unless necessary. XMLSpy is good tool I use.
    You can send the XML schema file to me if you can't register it to XML DB. I will help you take a look.

  • Residual payment should not allow more than Vendor Invoice

    Hi,
    Eg: Vendor has booked invoice 5000 INR, when user make payment through F-53 or F-58 through "Residual" payment user can pay more than invoice 5002 INR and below accounting entry is posting.
    Bank Cr 5002 INR
            To  Vendor Dr 5000 INR (Invoice amount)
            To  Vendor Dr 02    INR  Excess than invoice 
    Business requirement is system should not allow pay more than invoice amount. How to control suggestion would be appreciated.
    I have done below settings for your understanding here system configuration.
    1. OBA3: Under "Permitted Payment difference" zero for Gain , Loss , Amount, Percent & Adjust Discount By  However "Permitted Payment Differences for Automatic write-Off(Function code AD)" zero.
    2. OBA4: Cash discount per line item: Zero and Under "Permitted Payment difference" Revenues, Expense, Percent & Cash discount  put Zero.
    Regards,
    Babu.

    Hi Prashant,
    I have restricted many fields to use through screen variant now user can not pay more than Invoice amount except through Residual payment process.
    Client side management strongly says that they want to use Partial and Residual payment process options but user should not allow pay more than invoice amount.
    If any solution please guide me.
    Regards,
    Babu.

  • Transaction MRHR and MIRO - Vendor Invoice

    Good morning,
         we have completed the upgrade to 4.7 SAP version (from 4.6c) two weeks ago.
    To register the vendor invoice  for simple “Withholding tax” in 4.6c we used MRHR,
    But in 4.7 this transaction is no longer usable and we are obliged to use MIRO.
    The question is : can we use the simple  “Withholding tax” or  we must to use the extended one ?
    Then, what is necessary to do (in customizing and not) to be able to register the incoming vendor invoices for “Withholding tax” ?
    Thanks a lot in advance.
    Best regards.
    Massimo

    HI Freddy,
    Create a PO with material having price indicator as Moving avg price (V). In the PO select a feight condition and enter the freigh amount. Also enter freight vendor if known.
    Make sure for the freight condition accruals is ticked and the vendor in GR is 2 under control data 2 in tcode M/06. This enables change in the freight vendor while making GR by opening e new tab called Freight at items level.
    Since the material has price indicator V both the price and the freight goes to material accounts only.
    Also if the freight amount is not known exactly enter an app value while creating PO.  Before making the GRN since u receive the bill from forwarder u will know the freight amount for a particular PO and adjust the PO accordingly and do GRN.
    Also if possible advice the material vendor to send a copy of the invoice to the forwarder and the forwarder can send the material and freight bill together to u. Although this change in the business process is difficult discover the ways of achieving it if posssible.
    Also if the frieght amount is not known exactly even after u receive goods enter an app close value in PO,do GRN and then create a subsequent debit or credit for the remaining freight amount once u get the exact freight bill. By this way the remaining amount will go to the material if price indicator is V.
    Thx
    Raja

  • Tables for vendor invoice and payment

    Hi Gurus.
    I want to know from which tables i can get the information for folllowing points.
    1.       Vendor Invoices  - Complete (Header and Item)
    2.       Vendor Payments Details – Detail about payment method (check, wire, etc)
    Please tell me tje table names.

    There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
    |Table Name               |Table Description                                           |
    |/BEV3/CHKOMPAZVV         |Append Structure CH -> CO PA                                |
    |/CWM/ACCIT               |Append Structure for Enhancement of Structure ACCIT in CWM  |
    |/CWM/KOMP                |Catch Weight Management Enhancement                         |
    |/DSD/TAXJURCD            |Ship From Tax Jurisdiction Code: for Header Prc Comm Str    |
    |/SAPNEA/J_SC_LFA1        |Subcontractor Information                                   |
    |/SAPNEA/J_SC_LFB1        |Subcontracting Management                                   |
    |/SAPPSPRO/A_FI2_LONGNUM  |IBU-PS:  Append structure for structure NONBSEG             |
    |/SAPPSPRO/A_LONGNUMBER   |additional fields for SPIIN number                          |
    |/SAPPSPRO/EADD           |Purchasing Document Header: Additional Data                 |
    |/SAPPSPRO/EADD_DATA      |Purchasing Document Header: Data Part Additional Information|
    |/VSO/R_KNA1_A            |Append to KNA1 for Vehicle Space Optimization               |
    |/VSO/R_KNA1_I            |Additional Data for Vehicle Space Optimization for KNA1     |
    |AACCHD_FMFG              |US federal fields                                           |
    |AACCHD_PSO               |IS-PS: ACCHD Append Structure for Payment Requests          |
    |AACCIT_GM                |Append for Grants Management                                |
    |AACCIT_PSO               |IS-PS: ACCIT Append Structure for Payment Requests          |
    |AACCIT_SSP               |Append for Payment Statistical Sampling Process             |
    |AACCIT_USFG              |Append structure for US federal government                  |
    |AAUSZ_CLR_USFG           |Clearing information for US Fed (Tresury Confirmation)      |
    |ABKPF_PSO                |IS-PS: BKPF Append Structure for Payment Requests           |
    |ABKPF_UMB                |IS-PS: Append Structure for Transfer Transaction FMITPO     |
    |ABSID_PSO                |IS-PS: Data appendix of open items customers                |
    |ABSIK_PSO                |IS-PS: Data appendix of open items vendors                  |
    |ABSIS_PSO                |Local Authorities                                           |
    |ABUZ                     |Help Structure for Line Items to be Generated Automatically |
    |ACCCR                    |Accounting Interface: Currency Information                  |
    |ACCCR_FKEY               |Key: Acctg Currency Data for Line Item Including Currency   |
    |ACCCR_KEY                |Key: Accounting Currency Data for Line Item                 |
    |ACCFI                    |Interface to Accounting: Financial Acctg One-Time Accts     |
    |ACCHD                    |Interface to Accounting: Header Information                 |
    |ACCHD_KEY                |Key: FI/CO Document Header                                  |
    |ACCIT                    |Accounting Interface: Item Information                      |
    |ACCIT_EXTENSION          |ACC Document: Additional Item Information                   |
    |ACCIT_JV                 |Joint Venture Accounting                                    |
    |ACCIT_KEY                |Key: FI/CO Line Item                                        |
    |ACCIT_WT                 |Withholding tax information for FI Interface                |
    |ACCRDF                   |Fields for Posting Small Differences: Preparation           |
    |ACC_DOCUMENT             |Accounting document                                         |
    |ACC_KONTEXT              |Context Info for FI Single Screen Transactions FB50 and FB60|
    |ACERRLOG                 |Return Parameter                                            |
    |ACGL_HEAD                |Fields for Document Header Entry Screen                     |
    |ACGL_ITEM                |Structure for Table Control: G/L Account Entry              |
    |ACSCR                    |Communication Structure for Field Modification SAPLFDCB     |
    |ACSPLT                   |Carrier for Split Information re: Current Account Line Items|
    |ACSPLT_WTNEW             |Proportion of New Withholding Tax                           |
    |ACSPLT_WTOLD             |Proportion of Old Withholding Tax                           |
    |ADDR1_SEL                |Address selection parameter                                 |
    |AEBPP_KNBK               |Additional Fields Bank Data Biller Direct                   |
    |AEBPP_LFBK               |Additional Fields Bank Data Biller Direct                   |
    |AFMIOI                   |Append for new fields ECC50/ERP                             |
    |AFMIOI_USFG              | SD order needs quantity                                    |
    |AFMISPS                  |Additional Fields for Table FMISPS                          |
    |AFM_ACCIT_EXTENSION      |Extension for FM Payment Update                             |
    |AFM_FAGL_GLT0_ACCIT_EXT  |Extension FM Account Assignments                            |
    |AFM_FI_BKPF_SUBST        |Append to Structure BKPF_SUBST                              |
    |AFM_FMFCTF               |Append for Fund Center substrings                           |
    |AFM_FMFINCODE            |Append for Fund substrings                                  |
    |AIFM01D                  |Append for IFM01D                                           |
    |AKNA1_FMFG               |US Federal Government Customer Master Data Additional Fields|
    |AKNA1_PSO                |Local Authority Additional Fields                           |
    |AKNB1_PSO                |IS-PS: Customer Master Record, Additional Data (Co.Code)    |
    |AKNBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALFA1_FMFG               |US Federal Government Vendor Master Data Additional Fields  |
    |ALFA1_PSO                |Local Authority Additional Fields (Address)                 |
    |ALFB1_FMFG               |PS fields for company code-specific master data field       |
    |ALFB1_PSO                |IS-PS: Data Appendix Vendor Master Record (Company Code)    |
    |ALFBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALVDYNP                  |ALV dialog screen fields                                    |
    |ALV_S_FCAT               |Field Catalog (for LVC and for KKBLO)                       |
    |ALV_S_FILT               |Filter Criteria (for LVC and for KKBLO)                     |
    |ALV_S_GRPL               |Group Levels (for LVC and for KKBLO)                        |
    |ALV_S_LAYO               |Layout (for LVC and for KKBLO)                              |
    |ALV_S_PCTL               |Structure for Checking Print in ALV                         |
    |ALV_S_PRNT               |Print settings (for LVC and KKBLO)                          |
    |ALV_S_QINF               |Structure for Quickinfos of Exceptions                      |
    |ALV_S_SGRP               |Field Groups (for LVC and for KKBLO)                        |
    |ALV_S_SORT               |Sort Criteria (for LVC and for KKBLO)                       |
    |ANBZ                     |Help structure for asset line item                          |
    |ANLZACCOUNT              |Additional Account Assignment Objects in Asset Accounting   |
    |ANLZACCOUNT_FKBER        |Account Assignment Objects: ANLZACCOUNT with Function Added |
    |ARC_PARAMS               |ImageLink structure                                         |
    |AT003_XBLNR2             |Append structure for US federal government                  |
    |AUSZ1                    |Clearing Table 1                                            |
    |AUSZ2                    |Clearing Table 2                                            |
    |AUSZ_CLR                 |Assign Clearing Item to Cleared Items                       |
    |AUSZ_CLR_ASGMT           |Assgt of Clrg Items - Cleared Items with Acct Assignment    |
    |AUSZ_INFO                |Open item data for clearing transactions                    |
    |AVBKPF_FMFG              |US federal                                                  |
    |AVBKPF_PSO               |IS-PS: Append Structure VBKPF for Payment Requests          |
    |AVBSEGDPSO               |IS-PS: Append Structure VBSEGD for Payment Requests         |
    |AVBSEGKPSO               |IS-PS: Append Structure VBSEGK for Payment Requests         |
    |AVIK                     |Payment Advice Header                                       |
    |AVIP                     |Payment Advice Line Item                                    |
    |BALHDR                   |Application log: log header                                 |
    |BALMT                    |Application Log: Structure for a formatted message          |
    |BAL_S_CLBK               |Application Log: Return routine definition                  |
    |BAL_S_CONT               |Application Log: Context                                    |
    |BAL_S_MSG                |Application Log: Message Data                               |
    |BAL_S_PAR                |Application Log: Parameter Name and Value                   |
    |BAL_S_PARM               |Application log: Parameters                                 |
    |BAPIASCONT               |Business Document Service: File Content ASCII               |
    |BAPIBDS01                |Business Document Service: Reference Structure for BAPIs    |
    |BAPICOMFIL               |BDS: Command File for Transport Entries                     |
    |BAPICOMPO2               |SBDS: Enhanced Component Information                        |
    |BAPICOMPO3               |SBDS: Enhanced Component Information                        |
    |BAPICOMPON               |Business Document Service: Component Table                  |
    |BAPICONNEC               |BDS: Structure for BDS Links                                |
    |BAPICONTEN               |Business Document Service: File Content                     |
    |BAPIDPROPT               |BDS: Structure for Properties                               |
    |BAPIFILES                |Business Document Services: Transfer Table for File Names   |
    |BAPIPROPER               |BDS: Structure for Properties                               |
    |BAPIPROPTL               |BDS: Structure for KPRO Properties                          |
    |BAPIQUERY                |BDS Structure for Query Table                               |
    |BAPIRELAT                |Business Document Service: Relations                        |
    |BAPIRET1                 |Return Parameter                                            |
    |BAPIRETURN               |Return Parameter                                            |
    |BAPISIGNAT               |Business Document Service: Signature Table                  |
    |BAPISRELAT               |Business Document Service: Relationship Table with Signature|
    |BAPIURI                  |Business Document Service: URI Table                        |
    |BDCMSGCOLL               |Collecting messages in the SAP System                       |
    |BDCRUN                   |Batch input: Runtime analysis                               |
    |BDIDOCSTAT               |ALE IDoc status (subset of all IDoc status fields)          |
    |BDI_SER                  |Serialization objects for one/several IDocs                 |
    |BDN_FKT                  |Business Document Navigator: Functions to be Excluded       |
    |BDWFAP_PAR               |Parameters for application function module - IDoc inbound   |
    |BDWFRETVAR               |Assignment of IDoc or document no. to method parameter      |
    |BDWF_PARAM               |Parameters for workflow methods for IDoc inbound processing |
    |BKDF                     |Document Header Supplement for Recurring Entry              |
    |BKDF_SUBST               |Process Interfaces: Substitutable fields during posting     |
    |BKORM                    |Accounting Correspondence Requests                          |
    |BKP1                     |Document Header Supplement for Update                       |
    |BKPF                     |Accounting Document Header                                  |
    |BKPFBU_ALV               |Document Overview: Display Document Headers in ALV Grid Ctrl|
    |BKPF_CARD                |Credit Card: Append for BKPF                                |
    |BKPF_LINE                |Item Category for XBKPF_TAB                                 |
    |BKPF_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BKPF_USFED               |Append structure for US federal government                  |
    |BLNTAB                   |Document Number Table for Financial Accounting              |
    |BNKA                     |Bank master record                                          |
    |BNKAAPP                  |Appendix to Table BNKA                                      |
    |BNKT                     |Conversion of temporary to internal bank keys               |
    |BOOLE                    |Boolean variable                                            |
    |BSEC                     |One-Time Account Data Document Segment                      |
    |BSEC_LINE                |Item Category for XBSEC_TAB                                 |
    |BSED                     |Bill of Exchange Fields Document Segment                    |
    |BSEE                     |Changeable Fields in the Line Item                          |
    |BSEG                     |Accounting Document Segment                                 |
    |BSEGL                    |Document Segment: Fields Derived for Line Layout Variant    |
    |BSEGS                    |G/L Item Transfer Structure for Single Screen Transactions  |
    |BSEGT                    |Transfer Table for the Tax Postings to be Generated         |
    |BSEGZ                    |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
    |BSEG_ALV                 |Document Overview: Document Item Display in ALV Grid Control|
    |BSEG_LINE                |Item Category for XBSEG_TAB                                 |
    |BSEG_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BSET                     |Tax Data Document Segment                                   |
    |BSEU                     |Line Item Additional Information (Update)                   |
    |BSEZ                     |Line Item Additional Information (Online)                   |
    |BSEZ_LINE                |Line Item Category for XBSEZ_TAB                            |
    |BSID                     |Accounting: Secondary Index for Customers                   |
    |BSIK                     |Accounting: Secondary Index for Vendors                     |
    |BSIP                     |Index for Vendor Validation of Double Documents             |
    |BSIS                     |Accounting: Secondary Index for G/L Accounts                |
    |BSIX                     |Index table for customer bills of exchange used             |
    |BTXKDF                   |Fields for Exch.Rate Difference Posting for Taxes           |
    |BVOR                     |Intercompany posting procedures                             |
    |CACS_A_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_A_CUST_COND         |Commissions: Customer Fields Condition Technique            |
    |CACS_A_FIELDSPRICING     |Append for Condition Technique Fields from Commission System|
    |CACS_S_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_S_CUST_COND         |Condition Attributes                                        |
    |CACS_S_FIELDSPRICING     |Comm.: All Condition Technique-Relevant Commission Fields   |
    |CACS_S_FSINS             |Customer Fields for Condition Technique of Insurances       |
    |CCDATA                   |Payment cards: Database fields relevant to both SD and FI   |
    |CFW_LINK                 |CFW: Link Info of a Container                               |
    |CI_COBL                  |Extension                                                   |
    |CKI_ACCIT_ML             |Transfer from MM to ML in accit-structure                   |
    |CNTLSTRLIS               |Control stream list                                         |
    |COBK                     |CO Object: Document Header                                  |
    |COBK_ONLY                |Non-key fields only in COBK (INCLUDE structure)             |
    |COBL                     |Coding Block                                                |
    |COBLF                    |Coding block: Tax table structure                           |
    |COBL_COKZ                |Assignment types for CO account assignments                 |
    |COBL_DB_INCLUDE          |Include with Additional Account Assignments for DB Tables   |
    |COBL_EX                  |Coding Block for External Applications (Not CO/FI)          |
    |COBL_FI                  |Fields from COBL that Must not Be Overwritten in FI         |
    |COBL_FM                  |Additional Fields for FM                                    |
    |D010SINF                 |Generated Table for View D010SINF                           |
    |D020S                    |System table D020S (screen sources)                         |
    |D020T                    |Screen Short Description                                    |
    |DBSEG                    |Dialog Supplementation BSEG (Taxes)                         |
    |DD02L                    |SAP Tables                                                  |
    |DD03P                    |Structure                                                   |
    |DD03V                    |Table fields view                                           |
    |DD07V                    |Generated Table for View DD07V                              |
    |DD23L                    |Matchcode ID                                                |
    |DD32P                    |Interface structure for search help parameters              |
    |DDSHDEFLT                |Description of a default value for search help fields       |
    |DDSHDESCR                |Interface: elementary search helps of a search help         |
    |DDSHFPROP                |Characteristics of search help parameters                   |
    |DDSHIFACE                |Interface description of a F4 help method                   |
    |DDSHRETVAL               |Interface Structure Search Help <-> Help System             |
    |DDSHSELOPT               |Selection options for value selection with search help      |
    |DDSUX030L                |Nametab Header, Database Structure DDNTT                    |
    |DDSUX031L                |Nametab Structure, Database Structure DDNTF                 |
    |DDTYPES                  |Table of all Dictionary types and classes                   |
    |DFIES                    |DD Interface: Table Fields for DDIF_FIELDINFO_GET           |
    |DISVARIANT               |Layout (External Use)                                       |
    |DOKHL                    |Documentation: Headers                                      |
    |DPPROPS                  |General property structure for data provider                |
    |DTC_S_LAYO               |Structure for Design of Double Table Control                |
    |DTC_S_TC                 |Structure for table controls in the double table dialog box |
    |DTC_S_TS                 |Tab Title Structure                                         |
    |DYNPREAD                 |Fields of the current screen (with values)                  |
    |E071                     |Change & Transport System: Object Entries of Requests/Tasks |
    |E071K                    |Change & Transport System: Key Entries of Requests/Tasks    |
    |EAPS_20                  |Field Enhancements for EA-PS 2.0                            |
    |EDIDC                    |Control record (IDoc)                                       |
    |EDIDS                    |Status Record (IDoc)                                        |
    |EDIFCT                   |IDoc: Assignment of FM to log. message and IDoc type        |
    |EDIMESSAGE               |Transfer Structure with all Sy Fields for T100              |
    |EDI_DS                   |Status record for interface to EDI subsystem                |
    |EDI_HELP                 |Help Structure for Reference Fields in EDI Function Groups  |
    |EK05A                    |Communication Area Purchasing - Financial Accounting        |
    |ESKN                     |Account Assignment in Service Package                       |
    |EUDB                     |Development Environment Objects                             |
    |EUOBJ                    |Workbench: Development Objects                              |
    |EXCLTAB_LINE             |Lines of EXCLTAB with OK Code to be Deactivated             |
    |EXISTING_DOC             |Original Document                                           |
    |F05ACTRL                 |Control Fields for SAPMF05A and Subprograms                 |
    |FAGLBSEGL_S              |Additional Sender Flds from General Ledger for Doc. Overview|
    |FAGL_GLT0_ACCIT_EXT      |Line Information for Document Splitting                     |
    |FAGL_MIG_S_BUKRS_LEDGER  |Combination of Company Code and Assigned Ledgers            |
    |FAGL_SPLIT_FLD_S         |Characteristics Permitted for Split                         |
    |FAGL_S_APPLICATION       |Application and Subapplication                              |
    |FAGL_S_BALDIM            |G/L Characteristics of Document Split in New General Ledger |
    |FAGL_S_BUKRS             |Structure with Company Code                                 |
    |FAGL_S_BUKRS_EXT         |Structure: Company Codes --> Ledgers                        |
    |FAGL_S_CURTYPES          |Currency Types of a Ledger                                  |
    |FAGL_S_MIG_001           |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S           |
    |FAGL_S_MIG_MGPLN_EXT     |Structure: Extended Migration Plan Information              |
    |FAGL_S_T8G40_BS          |Split Fields with Characteristic "Balance Sheet"            |
    |FCRD_VBKPF               |Credit Card: Include for Appends for BKPF, VBKPF            |
    |FCRD_VBSEG               |Include for Appends for VBSE*                               |
    |FDM_AR_CASE_ATTR_1       |FSCM DM:                                                    |
    |FDM_AR_LINE_ITEM         |FSCM: DM                                                    |
    |FDM_AR_RFPOS             |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
    |FELD                     |Screen Painter fields (internal)                            |
    |FICCO                    |Adjustment Values for External Document Items               |
    |FICCT                    |Totals Information for Interclient Posting                  |
    |FICTX                    |Tax Information for ICT                                     |
    |FIELDINFO                |Field attributes for a specific field                       |
    |FIN1_PARAM               |OBNG: Trans. structure for official doc. numbering (global) |
    |FIN1_PARAM_FI            |OBNG: FI parameters                                         |
    |FIN1_PARAM_MM            |OBNG: MM Parameters                                         |
    |FIPEX_STRUC              |Subfields Commitment Item                                   |
    |FIPOEXT                  |Help structure for line items to be generated automatically |
    |FIREVDOC                 |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS     |
    |FISTL_STRUC              |Substructure Fund Center                                    |
    |FM01                     |Financial Management Areas                                  |
    |FMBLSTRING_COMPONENTS    |Component of the BL String                                  |
    |FMCI                     |Commitment items master data                                |
    |FMDY                     |FIFM: Screen Fields                                         |
    |FMFCTR                   |Funds Center Master Record                                  |
    |FMFG_ACCIT_EXTENSION     |Extention for all fields that have to be transfered into BL |
    |FMFINCODE                |FIFM: Financing code                                        |
    |FMFPO                    |FIFM: Commitment Item                                       |
    |FMHRBA_NEG_DOC_TYPES     |HR Integration: Doc. Types for Negative Funds Commitments   |
    |FMHRBA_SETTINGS          |Integration with HR: Settings                               |
    |FMHRBA_VAD_SETTINGS      |HR Integration: Generate Value Adjustment Docs for Changes  |
    |FMICCN                   |FM: Append Structure for FMIOI (CCN Fields)                 |
    |FMIDATA                  |Common Data for Funds Management Actual Data                |
    |FMIDATAFI                |Clean FI Data for Funds Management Actual Data              |
    |FMIDATAOI                |Clean Open Item Data for Funds Management Actual Data       |
    |FMIFIIT                  |FI Line Item Table in Funds Management                      |
    |FMIKEY                   |Common Key for Funds Management Actual Data                 |
    |FMIKEYFI                 |FI - Key for Funds Management Actual Data                   |
    |FMIKEYOI                 |Common Key for Funds Management Actual Data                 |
    |FMIOI                    |Commitment Documents Funds Management                       |
    |FMIOIKEY                 |Key for Table FMIOI                                         |
    |FMIOI_USFG               | SD order needs quantity                                    |
    |FMIREF                   |Ref. Funds Management Actual Data to Preceding Document     |
    |FMISPS                   |General Parameters for Funds Management                     |
    |FMIT                     |Totals Table for Funds Management                           |
    |FMMRESERV                |Include for the Reduction of Funds Reservations (FM)        |
    |FMRFC                    |Function Modules and their RFC Destinations                 |
    |FMSP_SPLIT_FIELDS        |PSM Fields used in multiple account splitting               |
    |FMT001                   |Additional Customizing for Funds Management                 |
    |FMUP00T                  |Update Profiles                                             |
    |FMUP01                   |Update Control with Value Type Dependency                   |
    |FMUP_INV_KEY             |Extension for FM Update: FI Key of Invoice                  |
    |FMUP_PAY_KEY             |Extension for FM Update: FI Key of Payment                  |
    |FS006                    |Fields for Optical Archiving                                |
    |FTCHECK                  |Foreign Trade: Import Simulation - Ctrl Fields for Pricing  |
    |FTEXTS                   |Communication Structure for Additional Components           |
    |FTGENERAL                |Foreign Trade: General Fields Item                          |
    |FUND_STRUC               |Substructure Fonds                                          |
    |FVD_TZB0A                |Append to TZBOA: Loans Fields                               |
    |GLACCOUNT_CCODE          |G/L Account Master Record: Company Code                     |
    |GLACCOUNT_CCODE_DATA     |G/L Account Master Record: Company Code - Data              |
    |GLACCOUNT_CCODE_INFO     |G/L Account Master Record: Company Code - Information       |
    |GLACCOUNT_CCODE_KEY      |G/L Account Master Record: Company Code - Key               |
    |GLX_ORG_INFO             |Organizational Assignment                                   |
    |GMBSEGZ                  |Grants Management Add-on                                    |
    |GXXLT_H                  |XXL interface: horizontal features                          |
    |GXXLT_O                  |XXL_interface: texts for online display                     |
    |GXXLT_S                  |XXL interface: structure of the semantics table             |
    |GXXLT_V                  |XXL interface: vertical features                            |
    |HELPVAL                  |Restrict Value Range - Transfer Table                       |
    |HELP_INFO                |Transfer Values for the Help Processor                      |
    |HELP_VALUE               |Structure or Function Module HELP_VALUE_GET_FOR_TABLE       |
    |HHM_COBL                 |Include for COBL from FM                                    |
    |IADDR_PSO                |Local Authority Additional Fields (Address)                 |
    |IBKPF_PSO                |IS-PS: Include Structure BKPF Payment Request Doc.Header    |
    |ICDIND                   |Structures for generating change document update programs   |
    |ICON                     |Icons table                                                 |
    |ICONS                    |Icons                                                       |
    |ICURR                    |Interface for Currency Translation                  

Maybe you are looking for

  • UWL: No automatic refresh after completing workitem in iView

    Hi, our system is EP 6 SP2 P4 HF 7 with CM HF 6. We have configured a workitem launched by an individual iview - this works fine. For execution of this workitem we call SAP_WAPI_CREATE_EVENT and save values in simple_container. After this SWW_WI_ADMI

  • Can i uninstall the pre-installed final cut express?

    There is the deal that when you buy a new mac you save a lot on final cut express. The only problem is it comes pre-installed. Could i uninstall it where i could use it on a different computer?

  • E-Recruitment configuration

    Hi Can anybody share e-recruitment configuration documents? Thanks inadvance.. Regards Vijay

  • Running  a webApplication using struts

    Hi forum, I am using struts & in index.jsp I have used following lines of code <code> <html:form action="Lookup" name="lookupForm" type="Project.LookupForm" > <table width="45%" border="0"> <tr><td>Symbol:</td> <td><html:text property="symbol" /></td

  • Java Add-in WAS 6.40 on MSSQL Server

    Hi, I am trying to install the Java Add-in (WAS 6.40) on Windows 200 Server after successfully installing the ABAP system. I am getting an error during the "start SAP J2EE engine" phase of the installation.  The message goes: ERROR 2005-03-15 19:01:5