Purchase order history already inconsistent -- Quantity * * Value**

Hi experts,
Please note that I am trying to reverse a GR/IR account maintanence document.
But it throws the below error for a line item in the PO.
Purchase order history already inconsistent --> Quantity10,000- SET Value 3,96 AED
For this line item actually account maintanence was done on 30.10.09.And then
further GR has been done & IR also has been done.
Please advise in what circumstances system throw this error and how to reverse
the document now.
Regards,
Partha

Hi,
Please check if there exists any multiple order units exists for the PO and thier conversion while posting documents.
Regards,

Similar Messages

  • GR/IR Posting Error CKMLGRIR025 - Purchase Order History Inconsistent

    Hi Everyone.
    We currently have a posting in our GRIR for a Feright Condition Value against a Purchase Order which gets the above error when trying to post in MR11.
    The Diagnosis of the error reads:
    "The purchase order history contains differences between the goods receipt and invoice receipts/Account maintenance for the order item in the field Difference Quantitiy (= 43.804 TO) and Difference Value (= -342.77)
    The purchase order history for this tiem is inconsistent"
    When looking at this Freight Condition information in the Purchase Order I can not see why this item has resulted in this error in MR11.
    Has anyone else seen this error come through in their system, and do you have any ideas on how to fix this.
    Thanks
    Hayley

    We are experiencing the same issue with the GRIR Posting Error CKMLGRIR025 - puchase order history inconsistent.  The actual message that we receive is Puchase Order history already inconsistent -->Quantity 1.00 EA Value 0.65-USD.
    We reviewed SAP Note 708649 which also recommends using transaction MIRO with the corresponding default quantity and value o.  However, we are not able to enter an Invoice for the "default qty & value 0", as SAP gives me error message M8278 "You are not allowed to have zero lines" (just like Haley commented).  In reviewing this thread, I did not find the solution to the error message M8278 "You are not allowed to have zero lines" .  Could someone help me understand?
    Thank you!

  • Goods Receipt value in Purchase Order History

    Hi Experts,
    I raised a PO with Account Assignment category as "K" for 100 quantity with a value of 1000.
    GR non-valuated option is ticked in "Delivery" tab in line items.
    When posted a GR for 25 NUmbers the Purchase Order History is updated with "0,00" in Amount column.
    If this is because of GR Non-valuated option used then please let me know where the amount with correct value is stored in Database tables.
    Note: I have use only GR Non-valuated option.
    I want to know where the correct value of the stock received is stored.
    Regards,
    Nani.

    Hi
    By assigning K you will have 3 things in default unless uou change them manually. 1.  Goods receipt , 2. GR Non-valuated, Invoice receipt.
      When you do a GR then this account gets posted against the G/L you have assigned manually at PO or against the the acct. modifier VBR in OBYC, that is it is consumed directly. So you will not have any stock valuation like raw or other materials.
    Now when you carry out Invoice verification you get the postings regularised against the acct assignment object(K) and the vendor outstanding/GR/IR account.
    Once IV is done you can check the details of your posting.
    Regards

  • Pass values to OAF search page (View Purchase Order History)

    I need to call a OAF page from a PO Approval Notification. I need to call page View Purchase Order History (func:ICX_PO_REVISIONS).
    I am able to create the URL (using function FND_RUN_FUNCTION.get_run_function_url) and when I click on the link it opens the page fine, but it’s a page that contains simple search region and I need to populate the Operating Unit and PO Number fields (I can easily get from the PO) of the search fields, this will allow the user to just click the go button.
    Is it possible using the function FND_RUN_FUNCTION.get_run_function_url and passing parameters (field values) or setting the URL to JSP:/OA_HTML/OA.jsp?OAFunc=ICX_PO_REVISIONS&akRegionApplicationId=177&addBreadCrumb=Y&CorePO=Y and then passing the parameters?
    How would you achieve this if possible, call the page and populate the search field values? It does not seem to work, I have been able to pass paramaters to an OAF page that does not contain a simple search region to return results.
    Function paramaters:
    FND_RUN_FUNCTION.get_run_function_url (
    p_function_id => 3101,
    p_resp_appl_id => 201,
    p_resp_id => 50598, -- MS Purcahsing Superuser
    p_security_group_id => 0,
    p_parameters => 'PoNum=' || l_document_id || '&' || 'retainAM=Y' || '&' || 'addBreadCrumb=Y',
    p_override_agent => NULL,
    p_org_id => 101,
    p_lang_code => NULL,
    p_encryptParameters => FALSE);
    Thanks,
    Shaun

    What I found is there are 2 variables SiteName and SiteName1, if you use SiteName1 then it shows proper value as a site description. I replaced SiteName with SiteName1 and it works. This might help to all who are like me and trying Tutorial example.
    I am not sure how many may have tried OAF - Tutorial examples. They are really complicated and not easy and in most cases they are not coming out in first try but if you really try then it will give lot of understanding.

  • Quantity is not shown in the purchase order history of the Service PO

    Hi
    We have a service PO for which we made a service entry sheet and released the same. In the background GR with 101 movement type also done correctly. But when we refer the purchase order history, we found the SE Number and the GR number but the QUANTITY field shows empty. The amount field got updated. But none of the qty fields like Quantity, Delivery cost Quantity, Quantity in OPUn shows empty.
    Please let me what should be reason for this.
    Thanks
    Venkat.

    Hi, please try marking Srv-based inv.ver. in the purchising data of the vendor master.
    Rgards.

  • Purchase Order History Program - not working properly

    Dear friends
    i am developing purchase order history program in ALV,
    which shows the report of purchase order status
    i.e (fields as below).
    document no
    PO date
    line item
    material number
    material name
    purchase org
    plant
    purchase group
    orderd quantity
    ordered amount
    delivered quantity
    delivered amount
    to be delivered quantity
    to be delivered amount
    invoice quantity
    invoice amount
    to be invoiced quantity
    to be invoiced amount
    how to test from me23n
    open me23n
    enter PO number
    press status tab
    you can get some fields for verification..
    the problem is
    i can get all the details correctly except delivered amount and to be delivered amount
    it works fine in both ( material purchase order and service purchase order )
    sometimes i am getting incorrect values in service purchase order specifically in delivered amount and to be delivered amount
    why i am getting these incorrect values ??
    only couple of POs generate these things.
    i am getting these values from EKBE table and using proper filtration like movement type and etc...
    if anyone can resolve ... would be appreciable
    avirat.

    Hi,
    for getting proper Po History you need to select PO's details from EKKO table and
    Header details from CHANGEDOCUMENT_READ_HEADERS based on the details got from this FM pass
    to the FM CHANGEDOCUMENT_READ_POSITIONS and get proper details.
    This is the logic used by the standard program also to get the PO History.
    Hope this helps.
    Regards
    Bikas

  • How to Enable Delta for a Custom MM Purchase Order History ODS ???

    Hi all,
       We have a Customized MM Purchase Order History ODS with Full Update on Monthly basis. We want to enable the DELTA for this ODS and how can I proceed, PLEASE.
    Please find the Key Figures and Data Fields in the below:
    ODS Structure for PO History ODS:     
    Key Fields
    SAP R/3 Field Description             Technical Name
    Purchasing Document Number             EKBE-EBELN
    Purchasing Line Item Number             EKBE-EBELP
    Sequential number of account assignment     EKBE-ZEKKN
    Transaction/event type, purchase order history     EKBE-VGABE
    FI Fiscal Period     FISCPER (from BKPF-GJAHR + BKPF-MONAT) in the format YYYYPPPP
    Number of Material Document             EKBE-BELNR
    Item in Material Document             EKBE-BUZEI
    Data Fields
    SAP R/3 Field Description     Technical Name
    Company Code     EKKO-BUKRS
    Plant     EKPO-EWERK
    Account Number of the Vendor                   EKKO-LIFNR
    Currency Key (of PO)                           EKKO-WAERS
    Deletion indicator in purchasing document     EKPO-LOEKZ
    Purchasing Document Date                   EKKO-BEDAT
    Responsible salesperson at vendor's office    EKKO-VERKF
    Vendor's telephone number                   EKKO-TELF1
    Incoterms (part 1)                           EKKO-INCO1
    Incoterms (part 2)                           EKKO-INCO2
    Short text                                   EKPO-TXZ01
    Material Group                                   EKPO-MATKL
    Material Number used by Vendor                   EKPO-IDNLF
    Expected Delivery Date                           EKET-EINDT
    Order unit (UOM)                           EKPO-BSTME
    Delivery Completed Indicator                   EKPO-ELIKZ
    Account assignment category                   EKPO-KNTTP
    Business Area (from PO)                           EKKN-GSBER
    Name of requisitioner/requester                   EKPO-AFNAM
    Purchasing organization                           EKKO-EKORG
    Purchasing group                           EKKO-BKGRP
    G/L Account Number (from PO)                   EKKN-SAKTO
    Cost Center (from PO)                           EKKN-KOSTL
    Work Breakdown Structure Element (WBS Element)     EKKN-PS_PSP_PNR
    Payment Terms (from PO)                           EKKO-ZTERM
    PO History Category                            EKBE-BEWTP
    Movement Type                        EKBE-BWART, MSEG-BWART
    Debit/Credit Indicator                     EKBE-SHKZG
    Reference from Invoice                     RBKP-XBLNR
    Payment Terms (from Invoice)             RBKP-ZTERM
    Posting Date      RBKP-BUDAT for IR, MKPF-BLDAT for GR
    Document Date      RBKP-BLDAT for Invoice, MKPF-BLDAT for GR
    Baseline Date     RBKP-ZFBDT
    FI Document Number      BKPF-BELNR, found through BKPF-AWKEY (IR # or GR # + fiscal year) or MSEG-LFBNR
    FI Dcoument Year          BKPF-GJAHR
    FI Document Type          BKPF-BLART
    Fiscal Variant     Hardcoded: S4
    Payment Method (invoice header level)     RBKP-ZLSCH
    GL Account (from GR/IR document)     MSEG-SAKTO for GR, DRSEG-SAKNR for IR (DRSEG is a structure)
    Cost Cener (from GR/IR document)     MSEG-KOSTL for GR, DRSEG-KOSTL (DRSEG is a structure) for IR
    Business Area (from GR/IR document)     MSEG-PARGB; not sure on IR
    Local Currency                             BKPF-HWAE
    Local Currency 2                     BKPF-HWAE2
    Amount posted to GR/IR Clearing (LC)     EKBE-AREWR
    Amount posted to GR/IR Clearing (GC)     EKBE-AREWR converted to Group Currecny found through BKPF-KURS2 if BKPF-HWAE2 is USD
    Purchase order quantity                           EKPO-BSTMG
    Price Unit (for PO)                           EKPO-PEINH
    Net price in purchasing document (in document currency)                                           EKPO-BPREI
    Amount in local currency; amount in document currency     MSEG-DMBTR for material document, RSEG-WRBTR for invoice
    Amount in local currency; amount in document currency (GC)     MSEG-DMBTR for material document,
            RSEG-WRBTR for invoice converted to USD
    Quantity      MSEG-ERFMG for material document;
                    RSEG-MENGE for Invoice
    Delivery costs' share of item value     RSEG-BNKAN
    Delivery costs' share of item value (GC)RSEG-BNKAN converted to USD
    Tax Amount (accrued)             BSEG-PSWBT
    Freight Amount (accrued)     BSEG-PSWBT
    Discount Amount (invoice header level)     RBKP-WSKTO
    Thanks.

    Hi Venkat,
    If you are using a Custom DataSource/Extractor the main problem is that you are collecting data from a lot of tables, so it is really difficult to determine a field for the delta.
    If for you is important only a change at Key Fields Table (EKBE) you can set the Generic Delta only on a field of this table (Doc Number or Position Number - Date - Timestamp).
    But if you are interested in all changes you have to determine a single field for every tables...
    I think it is really difficult to find a delta in all these tables.
    Maybe you can think to use in BW an ODS without Reporting BEx flag to determine Delta, and then introduce delta records in a Cube.
    Ciao.
    Riccardo.

  • Purchase Order History SES not shown when not accepted

    We are working on 2 systems : one is ECC 6.0 and the other is 4.6.
    When i create a SES via ML81N and the SES is not released yet : on the 4.6 version, the SES is shown in the purchase order history, while in the ECC 6.0 version, the SES is not shown in the purchase order history. In ECC 6.0, the SES is shown inthe purchase order history tab after the SES has been accepted.
    Is this a setting in customizing or a difference in the 2 versions of SAP?

    Hi,
    no, it might be a coding error or an inconsistency issue.
    Please check the note
    442091 - Service entry sheet missing in purchase order hist
    In order to repair already existing inconsistencies, you can use report    
    RMESSRK2 (from Note 141870 or as of Release 4.6C in development class       
    ML_TOOLS). However, the report must be modified in the two positions        
    specified in the attachment.                                                                               
    If you can not find the report RMESSRK2 in transaction SE38                 
    in your system - or in transaction SE80 under the development class         
    ML_TOOLS, then please copy the program from the attached note               
    ML_TOOLS into your system and correct the coding according to               
    note 442091.       
    Regards,
    Edit

  • Batch specific unit of measure - Purchase order history correction

    I have maintained an alternate proportional unit for a material.  This alternate unit is used as the order price unit in the purchase order.  I have created a batch characteristic which is linked to this proportional unit of measure. I have also created a Master inspection characteristic which is linked to this batch characteristic.
    I want to correct the purchase order history using quality management by transaction code MWBQ.  However, when I perform transaction MWBQ, the inventory is reduced to zero and entire amount is posted to price difference account after correction. Hence, my inventory value becomes zero after MWBQ. I cannot maintain the proportional unit at standard price since this is a raw material.  Need a solution on how to post correction in purchase order history without actualy making the inventory zero and with moving average price.

    Thanks for caring!
    As for transaction MMBE it all looks fine. So basic definitions must be OK up to that point.
    I think the point is to set requirement for the amount of active ingredient.
    Do the batch determination for this.
    Do the goods issue in physcial quantity which is the base unit of measure.
    I did try now with KG in the BOM. I still get  double items in the process order. Now both in KG.
    One line is correclty copied.
    The incorrect line which is the same in both cases says 1 KG. which is the correct conversion from  0,01KAI.
    Regards,
    Tor

  • Problem with purchase order history

    Hi,
    i have the following problem
    I create a service purchase order for the quantity of 36000 and amount of 1350 (0.0375 per unit)
    Step 1:
    I entered a service entry sheet:
    quatity: 17800
    Value: 667.5
    The system create a 101 for the amount of 667.5. Then i reversed the entry service trough movement 102 and i deleted the service entry sheet.
    Step 2:
    I repeated the step 1 but  for the quantity of 17500 and the amount of 656.25.
    Step 3: Finally i entered a service entry sheet for the quantity of 9000 and the amount of 337.5 (9000*0.0375)
    An error ocurred on the purchase order history. The lerf (service entry sheet, appear for the total amount of the PO: 1350 and the WE 101 for the amount of the service entry sheet: 337.5 (9000*0.0375)
    I want to know why the system entered the service entry sheet for the total value (360000.0375) when i did it just for 337.5 (90000.0375)
    Thanks in advance for your help.
    Enzo.

    Thanks, but i dont understand what your are trying to explaim me
    The problem is when I enter a Service entry sheet trough ML81N the system should generate a 101 for the same value. It doesn´t happend.
    In purchase order, the service entry sheet is for the amount of the Lerf created but the 101 (should generate automatically) is for the total of the purchase order.
    I dont know why its happend
    Thanks in advance for your help
    Enzo

  • Purchase Order History as a Report?

    Hi,
    I would like to follow the amounts of purchase orders, relevant goods receipt amounts and so on as shown in purchase order history on PO. But I need it as a report which could be seen as ALV type, and easily exported to excel.
    Is there such a standart report that I could follow purchase order-goods receipt quantities?
    Thanks in advance
    Irem

    hi,
    use MC$G - Puchasing values
    And MC$I - Puchasing quantities
    Or use ME87 - Aggregate PO history
    Regards
    Priyanka.P
    Edited by: Priyanka Paltanwale on May 13, 2009 12:57 PM

  • Purchase order History

    Hi..
         Iam trying to display the Purchase order History using BAPI_PO_GETDETAIL function module... and my code is
    data : i_ekko type table of ekko,
           i_ekko_wa like line of i_ekko.
    parameters : p_vendor like ekko-lifnr,
                 p_po     like ekko-ebeln.
    select * from ekko into corresponding fields of table i_ekko where lifnr = p_vendor and ebeln = p_po.
    loop at i_ekko into i_ekko_wa.
    CALL FUNCTION 'BAPI_PO_GETDETAIL'
      EXPORTING
        PURCHASEORDER                    =  '4500017124'
       ITEMS                            = 'X'
    *   ACCOUNT_ASSIGNMENT               = ' '
    *   SCHEDULES                        = ' '
       HISTORY                          = 'X'
    *   ITEM_TEXTS                       = ' '
    *   HEADER_TEXTS                     = ' '
    *   SERVICES                         = ' '
    *   CONFIRMATIONS                    = ' '
    *   SERVICE_TEXTS                    = ' '
    *   EXTENSIONS                       = ' '
    * IMPORTING
    *   PO_HEADER                        =
    *   PO_ADDRESS                       =
    * TABLES
    *   PO_HEADER_TEXTS                  =
    *   PO_ITEMS                         =
    *   PO_ITEM_ACCOUNT_ASSIGNMENT       =
    *   PO_ITEM_SCHEDULES                =
    *   PO_ITEM_CONFIRMATIONS            =
    *   PO_ITEM_TEXTS                    =
    *   PO_ITEM_HISTORY                  =
    *   PO_ITEM_HISTORY_TOTALS           =
    *   PO_ITEM_LIMITS                   =
    *   PO_ITEM_CONTRACT_LIMITS          =
    *   PO_ITEM_SERVICES                 =
    *   PO_ITEM_SRV_ACCASS_VALUES        =
    *   RETURN                           =
    *   PO_SERVICES_TEXTS                =
    *   EXTENSIONOUT                     =
    endloop.
      Iam not getting the output ... It doesnt show errors..
    Regards,
    Abaper.

    where is the displaying PO code???
    check your code once again...
    look at this example...
    report  zbapi_1.
    data: begin of i_poitem occurs 0.
          include structure bapiekpo.
    data: end of i_poitem.
    parameters p_ebeln like ekko-ebeln default '4500012164'.
    call function 'BAPI_PO_GETDETAIL'
      exporting
        purchaseorder                    = p_ebeln
      ITEMS                            = 'X'
      ACCOUNT_ASSIGNMENT               = ' '
      SCHEDULES                        = ' '
      HISTORY                          = ' '
      ITEM_TEXTS                       = ' '
      HEADER_TEXTS                     = ' '
      SERVICES                         = ' '
      CONFIRMATIONS                    = ' '
      SERVICE_TEXTS                    = ' '
      EXTENSIONS                       = ' '
    IMPORTING
      PO_HEADER                        = PO_HEADER
      PO_ADDRESS                       = PO_ADDRESS
      tables
      PO_HEADER_TEXTS                  = PO_HEADER_TEXTS
        po_items                         = i_poitem.
      PO_ITEM_ACCOUNT_ASSIGNMENT       = PO_ITEM_ACCOUNT_ASSIGNMENT
      PO_ITEM_SCHEDULES                = PO_ITEM_SCHEDULES
      PO_ITEM_CONFIRMATIONS            = PO_ITEM_CONFIRMATIONS
      PO_ITEM_TEXTS                    = PO_ITEM_TEXTS
      PO_ITEM_HISTORY                  = PO_ITEM_HISTORY
      PO_ITEM_HISTORY_TOTALS           = PO_ITEM_HISTORY_TOTALS
      PO_ITEM_LIMITS                   =
      PO_ITEM_CONTRACT_LIMITS          =
      PO_ITEM_SERVICES                 =
      PO_ITEM_SRV_ACCASS_VALUES        =
      RETURN                           =
      PO_SERVICES_TEXTS                = .
      EXTENSIONOUT                     = EXTENSIONOUT
    loop at i_poitem.
    write :/ 'PONUMBER    = ' ,  i_poitem-po_number color col_heading,
           / 'ITEM = ' , i_poitem-po_item,
           / 'MATERIAL NAME = ' , i_poitem-material,
           / 'MATERIAL = ' , i_poitem-pur_mat,
           / 'CHANGED ON = ', i_poitem-changed_on,
           / 'SHORT TEXT = ' , i_poitem-short_text,
           / 'COMPANY CODE = ' , i_poitem-co_code,
           / 'PLANT = ' , i_poitem-plant,
           / 'MATERIAL GROUP = ' , i_poitem-mat_grp,
           / 'QUANTITY = ' , i_poitem-quantity left-justified,
           / 'UNIT = ' , i_poitem-unit,
           / 'NET PRICE = ' , i_poitem-net_price left-justified.
    uline.
    endloop.
    Edited by: Venkat Appikonda on Mar 7, 2009 11:57 AM

  • Purchase Order History Reference not filled

    Hello everyone,
    we are using BAPI_INCOMINGINVOICE_CREATE to create an invoice for an purchase order. It works just fine except that there no Reference filled in the Purchase Order History. We fill the number of the reference to the BAPI (headerdata-ref_doc_no) and the reference is visible on the created FI document as expected.
    However the customer insists, that it has to be visible in the field Reference of the Purchase Order History as well. I know, it is the XBLNR field of the table BSEG. I dug deep in the source codes to find out, where is the problem, but setting of this field seems to be very complicated. Someone told me, that the field is only filled when the GR-Based Invoice Verification is checked (which in our case is not).
    Can someone tell me the rules, when the field Reference gets filled? Or (if there is anything) how to customize the system, co make this field filled?

    Hi Oleg,
    thank you for your reaction.
    I am aware of that there is a field XBLNR in the BKPF table - and there we have the reference filled correctly (it is visible on the FI document as I mentoined). However in the BSEG table is the XBLNR as well and it is related to displaying Reference in the Purchase Order History (the bseg relates to an PO item) at least in our case. When I manually input in the BSEG-XBLNR a value (via SE16N for example), it displays afterwards in the required field when viewing the Purchase order.
    In the case GR-Based Invoice Verification procedure and the table MKPF - i believe, you are right there (so the Reference is filled), however this is unfortunatelly not our case.
    What I am trying to find out are the conditions, under which the XBLNR in BSEG is filled (I can tell you, what source codes I have been inspecting, but I got lost after I while, because there are literally thousands of lines of code:-(

  • Spro settings- Purchase order History

    Hi,
    In spro> MM> Purchasing-->Maintain Purchase Order History Categories.
    can somebody help me out how it works and the concept.
    I have maintained the entry there with Z- forwarding charges as long and short text.
    I donot understand where is the link in the system, how system will understand for what my entry Z is meant for.
    I tested the scenario but nothing happened in PO history with this my key. I have done MIGO and MIRO also. No update with my entry
    pl help how to make this functionality work, I feel this stand alone entry will not work, there must be some link with this entry or standard enteries some where which make the system to understand this?
    Edited by: Pallvi Dixit on May 7, 2008 5:18 PM

    In this step, you can maintain the purchase order history categories. You   
    can change the short and long texts for existing PO history categories.                                                                               
    The SAP System controls the display of the PO history using PO history      
    categories.                                                                               
    SAP recommendation                                                                               
    You should work with the standard SAP System supplied. In this case, you    
    need take no action.                                                                               
    Activities                                                                               
    Maintain the PO history category texts according to your requirements.                                                                               
    Notes on transport                                                                               
    You transport number range objects as follows:                                                                               
    Choose Interval -> Transport in the accounting document Number Range        
    screen.                                                                               
    All intervals for the selected number range object are deleted in the       
    target system first. After the import, only the intervals you export are    
    present. The number statuses are imported with their values at the time     
    of export.                                                                               
    Dependent tables are not transported or converted.

  • Purchase Order History not updated properly

    Hi All,
    The Purchase Order History is not updated correct.
    Scenario:
    The  Invoice is created ( MIRO) with Amount : 1001 USD but in PO History it displays 1000 USD.
    The Tolerance is 1 USD ...My Requirement is that it should display 1001 in PO History.
    Thanks and Regards
    Mahesh

    The Actual Bill Value is 1001 USD.

Maybe you are looking for