Error in migo posting with respect to sch agreement

Hi
I created a purchse requisition and also a sch agreement with respect to it and maintained delivery scheduled.
PR item qty=10
sch delivery=2  4   4   i.e.equal to 10
but when i post GR with respect to this it gives error as follows
PU Ordered quantity exceeded by 2 KG
what can be possible reason.
Thnx

Hi,
Please check the SA - Schedule lines & also the Purchase document history to confirm the total order as well as GR quantity.
Also Please check the Purchase Order unit & Base unit of measure for the material.
Thanks & Regards,

Similar Messages

  • Account Determination error during MIGO Posting

    Dear All,
    Kindly help resolve error duirng MIGO posting  "ACCOUNT DETERMINATION FOR ENTRY GBB____ZOB TF01 not possible".  This is Message no. M8 147. 
    The error happens once the transaction is being saved.
    Hoping for your positive response.
    Thanks and regards,
    ching

    Hi,
    Goto OBYC Transaction.
    Select the Procedure as ' GBB" and enter the Chart of Accounts ( for Your Company code)
    Enter the Valuation modifier as assigned to others.
    Enter the General modifier as ZOB
    Enter the Valuation class  ( with respect ROH/SFG others)
    Enter the Debit/ Credit G/L account
    save then proceed your transaction MIGO.
    rgds
    Chidanand

  • BORGR 649 error message while posting with 105 mov type

    Hi Gurus,
    I faced a problem when I try to post with 105 mov type, when material doc is related to Inbound delivery.
    Explained better:
    I did a purchase order with inbound delivery confirmation.
    I carried out Good Receipt (related to Inb delievery) with mov type 103 (blocked stock from PO)
    When I try to post stock with 105 mov type, the following error appear:
    "Movement type 105 not allowed as it is not assigned to item category"
    Msg ID: BORGR
    Msg no: 649
    I already checked delivery item category configuration, movement types involved and transactions allowed for each mov types.
    Take care that the error mentioned doesn't occur if posting is related directly to purchase order, instead of inbound delivery..
    Thanks in advance
    Regards
    Ale

    Hi Sandra_PF
    in the inbound delivery the mov type is not 105, but 101 (correct, it's the default value for Inb delivery)
    With transaction MIGO I do 2 different operations (in 2 different moments):
    1°) Good Receipt referred to Inbound delivery (103 mov type - Blocked stock from PO)
    2°) Stock posting with 105 mov type, to transfer stock from Blocked to Unrestricted
    Here the system notice me that is not possible, because the mov type 105 is not assigned to the delivery inboud category.
    Please note that we did the same thing in another system with the same configuration, without any problems..
    Cheers,
    Ale

  • Error in MIGO posting Assets

    Hi  Friends ,
    Following error i am geting in MIGO posting for assets....please help
    Authorization missing for Company code 1000 Asset class IN4200
    Message no. AA048
    Diagnosis
    Authorization for Company code 1000 with Asset class IN4200 is missing.
    System Response
    You cannot create, change or post data in this object.
    Procedure
    If you want to create or change, use an object for which you have authorization. The display transaction will indicate your missing authorization in the initial request screen.
    If you need the authorization for this object, contact your Systems Specialist

    Hie Balegar.
    How did you resolve your error? My client is experiencing the same error AA048 but using t-code SU53 reports missing authorisations which are  maintained, have even went further to re-transport the role to no avail. Can you assist with possible solution.

  • WRX Error-For consumables posting with Acc Assignment K

    We are doing a GR for consumables posting with account assignment category K (Cost centre).  However, while trying to post the document, system issues a message that "Account determination for WRX cannot be determined". 
    Why this error is coming for consumables posting for a cost centre ?  Is it standard or am I missing any configuration ?

    Hi,
    When you are booking a Consumption to a Cost Center at the time of GR, the entry whihc is passed is
    Consupmtion A/c Dr
    GR/IR Account Cr.
    At the time of IR, the entry will be
    GR/IR Account Dr.
    Vendor A/c Cr.
    So you will have to do the settings for the WRX for GR/IR account in OBYC.
    Regards,
    Amit
    Edited by: amit kulkarni on Dec 2, 2009 5:19 PM

  • Error in MIGO posting against PO with account assignment category K

    Hi folks,
    I have craeted a P.O. Account assignment category K, while creating GR, I am getting following error message
    Account determination for entry SABB (chart of account) Z44 (Tra/event key) TE (act. grouping code) not possible
    Message no. M8147
    What could be the possibel cause.
    I have already did the G.R with same account assignment in the past.
    Regards

    Dear
    The system did not find an account for this transaction. This means that the account determination is not maintained in MM Customizing (Valuation). The key is made up of:
    Chart of account
    Transaction key (= Posting transaction)
    Valuation grouping code
    Account grouping code
    Valuation class
    System Response
    The system cannot update a G/L account for this transaction. You cannot post the transaction.
    Procedure
    Contact your system administrator.
    If you have the authorization, check the Account determination in Customizing forValuation.
    Regards

  • Run Time error in MIGO Posting

    Dear Friends,
    While Posting MIGO against a import PO system throws run time error for a particular plant. I have created 2 plants for the same company code. But first plant does not have any problem. Pl help me and let me know what may be the cause and its solution. No conditions maintained for the Vendor. After PO directly user creating MIGO.
    Regards,
    Ashok

    Pl find the Run Time error of Exception while posting. Before posting Document was OK while checking.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          11.01.2011 10:34:16
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
         Short text of error message:
         Operation QM14 not available for this lot
         Long text of error message:
          Diagnosis
              The desired operation does not fit the inspection lot (object
              type).
          System Response
              The operation is not permitted and can therefore not be carried
              out.
          Procedure
         Technical information about the message:
         Message class....... "QV"
         Number.............. 224
         Variable 1.......... "QM14"
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLMBWL
        Include                                 LMBWLU21
        Row                                     62
        Module type                             (FUNCTION)
        Module Name                             MB_POST_GOODS_MOVEMENT
    Source Code Extract
    Line  SourceCde
       32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
       33 *    every document is posted by MB_CREATE -> a new function module in
       34 *    MBWL for transferring the information, called by FI, meant to load
       35 *    the complete function group for all MBxx postings when this isn't
       36 *    required (Performance). Would be the better way to transport the
       37 *    information after switching off MBxx in later release.
       38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
       39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
       40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
       41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
       42    ELSE.                                                        "1245374
       43      l_mem_id = 'MKPF-XBLNR'.                                   "1245374
       44      FREE MEMORY ID l_mem_id.                                   "1245374
       45    ENDIF.
       46    IF xmkpf-xabln IS INITIAL.                               "note 434093
       47        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
       48    ENDIF.                                                   "note 434093
       49
       50 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
       CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
            EXCEPTIONS
              error_message = 4.
    As soon as we have started to put things into UPDATE TASK, w
    ensure that errors definitely terminate the transaction.
    MESSAGE A is not sufficient because it can be catched from
    external callers which COMMIT WORK afterwards, resulting in
    incomplete updates. Read note 385830 for the full story.
       IF NOT sy-subrc IS INITIAL.
          MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH
                     sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MESSAGE A263.
       ENDIF.
    Optische Archivierung
    Spaete Erfassung mit Barcode
    Redesign of barcode handling -> note 780365
      PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
                                             xmkpf-mjahr
                                             barcode.
      MOVE-CORRESPONDING xmkpf TO emkpf.
      CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
        EXCEPTIONS
          error_message = 4.
       MOVE-CORRESPONDING xmkpf TO emkpf.
       CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
            EXCEPTIONS
              error_message = 4.
       IF NOT sy-subrc IS INITIAL.
    Regards,
    Ashok

  • Duplicate GR Posting Control With Respect to MIGO Filed Delivery Note

    Hi Team,
    Is there any possiblity to check / control GR Posting with respect to the same PO and same delivery note reference.
    I have a PO 1000001 with line item 10 with qty 100. I did a MIGO with respect to this PO for 50 qty with delivery note ref DC-53.
    When i try to do MIGO with the same PO and same delivery note DC-53 for the balance 50 quantiy,
    System should intimate me as warning / error..
    How can we acheive this by standard  SAP.  If not possible by standard SAP wats the alternate.
    Vijay

    HI Vijay,
    It is possible to check warning / error message display of the MIGO bottom of the screen through ABAP delveloper with enhancement (Validation).
    After enhancement, MIGO posting is not allow to duplicate DC Ref.no. and also double entry of the same DC ref.no.
    Hope, it is useful for you.
    Regards,
    K.Rajendran.

  • MIRO error Posting with trans.type 159 not possible (No acquisition posted)

    Hi,
    I have the following probem while doing MIRO.  Would appreciate if someone could help.
    Error in Purchase invoice posting MIRO  :-
    The user has created a PO for asset in  FY2010 and has performed a MIGO in FY2010.
    Now in FY2011 the user tries to  invoice against the  above asset and wants to post it thru Trans MIRO.
    System gives an  error during MIRO  "Posting with trans.type 159 not possible (No acquisition posted)"  Message no AA 324
    Trans type 159 has trans type group 12 attached to it.
    MIGO can not be reversed  because it belongs to the closed FY.
    Please help

    Hi
    refer notes 1526247 and 1507808... Though it relates to Japan, but the issue is same
    Br, Ajay M

  • BAPI for MIGO with respect to Outbound delivery or Stk trfer pur order

    please let me know is there any standard BAPI for MIGO transaction with respect to Outbound delivery or Stock transfer purchase order

    try these...
    BAPI_OUTB_DELIVERY_CONFIRM_DEC
    BAPI_OUTB_DELIVERY_SAVEREPLICA
    BAPI_OUTB_DELIVERY_SPLIT_DEC

  • Data inconsistency: posting with restricted transaction type (FAA_POST047)

    Hi colleagues!
    I have the following error:
    Data inconsistency: posting with restricted transaction type
    Message no. FAA_POST047
    Diagnosis
    You are trying to post in company code 1000 with transaction type 130 in ledger group 0N. According to table TABWA, this transaction type is limited. Nonetheless, according to your entries, you want to post to area 11.
    System Response
    Using limited transaction types is obsolete and would lead to an inconsistent posting in this situation. The system rejects the posting.
    Procedure
    Use a transaction type that is not limited. And, if possible, choose the ledger group and/or depreciation area on the initial screen.
    According to specific accounting we shouldn't post to one of the depr. area, so most of the tr.types are restricted to post to all areas except this one.
    Because of this, posting from MM with acc.assignment 'A' is impossible - I have this error.
    Any ideas how to solve?
    Thanks in advance

    Hi Anton
    This looks like your transaction type -130 is limited to post only in ledger group-0N as per the transaction type configuration. Due to which system is unable to post all the ledgers and hence this lead to inconsistency.
    Please verify the transaction type 130- in configuration T code - OAYA and see if it is restricted by depreciation area (eventually allow to post only ledger group- 0N.
    Tcode - OAYA (Limit Transaction Types to Depreciation Areas)
    please verify and let us know the update. hope this helps
    Best Regards
    Jomon

  • ASSET TRANS-Posting with trans.type Z30 not possible(No acquisition posted)

    Hi Experts,
    Am creating a sub asset 001 for my_asset_1, via 'BAPI_FIXEDASSET_CREATE1'. Fine.
    Then, am trying to post the Asset transfer for my_asset/001 by using a BAPI of  'AMDP_BAPI_CALL_ON_TRANSACTION'.
    But, am getting the Error(via ABUMN am NOT geetting any ERROR)- <i><b>Posting with trans.type Z30 not possible (No acquisition posted)</b></i>
    Am passing paras, like,
    so, pls. clarify that,
    1 - Wht is the meaning of Error message am geeting?
    2 - How to fix it?
    thanq.
    Message was edited by:
            Srinivas
    Message was edited by:
            Srinivas

    closing, bcoz, did not get good answer

  • MIRO - Posting with trans.type 159 not possible (No acquisition posted)

    Hi all,
    I have a case where an asset PO was created with multiple account assignment in one line item.  For example, purchase 10 pc of printer with 10 asset numbers specified in the account assignment tab.  By standard SAP, the GR is non-valuated.
    The GR of the PO was done in the previous period.  Now, when the invoice is to be posted thru MIRO.  The system generate error message to me.  The error message is "Posting with trans.type 159 not possible (No acquisition posted)" and message number is AA324.
    The reason of this error is due to no acquisition date in the asset master.  GR is non-valuated hence, the acquisition date is not populated in the asset as well.  I believe this is quite a common problem.  Kindly advise any workaround solution.
    Thanks.
    Tom

    Hi
    refer notes 1526247 and 1507808... Though it relates to Japan, but the issue is same
    Br, Ajay M

  • Posting with trans.type 200 not possible (No acquisition posted

    When I am trying to retire an asset following error is throwing
    Posting with trans.type 200 not possible (No acquisition posted
    Please guide me accordingly
    naren

    Hi Narayana,
    I think you are using wrong transaction type for asset retirement.
    Ttype 210 is for Asset Retirement with revenue and 200 is for Retirement without revenue .
    Try using ttype 210 instead of 200.
    Hope this helps..
    Regards,
    Praisty
    Edited by: Praisty on Mar 25, 2009 10:24 AM
    Edited by: Praisty on Mar 25, 2009 10:26 AM

  • Posting with trans.type 200 not possible

    Dear Gurus,
    when I try to scrap the asset,  I am getting an error as below
    Posting with trans.type 200 not possible (No acquisition posted)
    Message no. AA324
    Diagnosis
    Transaction type 200 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
    Procedure
    Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
    Thanks in advance and Regards

    Tried all Transaction types. 
    Sometimes I get this error
    Retirement of old assets data not possible (No existing old assets data)
    Message no. AA416
    Diagnosis
    You have tried to post an retirement based on amount, using a transaction type which refers to old assets data (acquisitions from previous years).
    However, the sum of the APC at the start of the fiscal year and the transactions, related to the past, equals 0.
    Procedure
    Check the transaction type entered and the asset.
    When I tried for other company code it is working
    Compared the configurations of both the company codes.  Everything is same.
    We are using Group Assets.  Group Asset is a required field in Tax Depreciation Area.  I am giving that. 
    Is there anything else I need to check?
    Please help.
    Regards

Maybe you are looking for