Error In MIGO Transaction

While creating MIGO transaction against a PO I am getting this error continously
PL Stock in transit exceeded by 12 PC : QS8X20 2100 2110 9000000010
I dont know what to do.??
can any one please tell me how to get rid of this error.

Hi
But after creating PO when i am checking ME2M for the particular material i cannot see the PO number generated at ME21N
I still unable to understand where the problem lies
See for a while forget about ME2M and check you PO in ME23N T-code you are getting your Po or not
IF not then while saving PO,system giving any message to you?
Regards
Kailas Ugale

Similar Messages

  • Error with MIGO transaction

    Dears,
    I receive this error while doing MIGO "Transaction type is a mandatory field". Please advise in which field i can put the transaction type.
    Thanks in advance,

    Hi,
    it is custom Message number. Please take Abaper help to understand when it is called in MIGO transaction.
    Regards,
    Srikanth P.

  • Runtime Error  in MIGO Transaction

    Hi all,
    I am getting error in MIGO i.e. TABLEVIEW_NOT_FOUND_IN_SCREEN. Short text: Table view "TV_GOITEM " does not exist in screen 8200. Error analysis: The screen 8200 of program "SAPLMIGO" specified in the CONTROLS declaration of the table view "TV_GOITEM " contains no description for this element.
    Thanks in Advance

    Hi,
    Please take assistants from SAP if ur client/company have serivces from SAP for the Product.
    They will suggest you to track this as the error is from Standard Program
    In case if you need to apply SAP OSS Notes related to the Issue/Error for the Trxn, they will guide you
    in the right direction.
    Thanks & Regards,

  • Reg. Error in MIGO transaction

    Hi friends,
    When I run standard transaction MIGO it is giving dump. Just after entering the Tcode it is giving dump. The following is the error we are getting.
    *Syntax error in program "SAPLVBDOCUBATCH_DM ".*
    Detail description:
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLMIGO" had to be terminated because it has          
    come across a statement that unfortunately cannot be executed.                                                                               
    The following syntax error occurred in program "SAPLVBDOCUBATCH_DM " in include  
      "LVBDOCUBATCH_DMU25 " in                                                        
    line 139:                                                                        
    "You can only use the COLLECT command in a table if all of its non-key "         
    "fields are numeric (type I, P, or F) . . . . . . . ."                           
    The include has been created and last changed by:                                
    Created by: "SAP "                                                               
    Last changed by: "SAP "                                                          
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLMIGO" had to be terminated because it has          
    come across a statement that unfortunately cannot be executed.                                                                               
    Please look into this and give me your suggestions, Thanks in advance.
    Regards,
    Chandu.

    Hi Venkat,
    My BASIS people solved the issue, they applied some patches to the system. Then it got set. You please check with your BASIS team.
    Regards,
    Chandu.

  • MIGO Transaction Error

    Dear All,
                 We are facing error in MIGO Transaction,after applying
    PATCHES In Development Server.
    The Particular Include-Program which is containing Data Variables after
    application of Notes was resetted.That Include program is not allowing
    to change also.It is giving following message.
    Carry out Modification Comparision for REPS LJ1IEXTOP First.No changes Possible.
        Please give suggestion accordingly.
    Thanks and Regards
       BalaNarasimman.M

    Hi BalaNarasimman,
    Normally after applying the patch try to do SPAU adjustment and retain the latest code (i,e If you have applied notes that is for latest package)..Else the OSS notes relevant to the package must be searched and it must be applied again. What is the error that you are getting..? What is the CIN package?
    Thank You.
    Regards,
    Uma

  • GETWA_NOT_ASSIGNED - Runtime Error in MIGO

    Dear All
    I am receiving GETWA_NOT_ASSIGNED - Runtime Error in MIGO transaction for a particular user only in production system. I am not able to narrow down is this transaction specific or user issue.  I searched the forum and not able to get reason.  If someone knows about ths kindly give me a hint.
    Regards,
    Venkat

    Hi,
    Please check if any User Exit BADI implemented and have a look into below thread
    Reg Dump in MIGO Transaction
    GETWA_NOT_ASSIGNED run time error_MIGO processing stock transport order
    Shiva

  • Error in FM RV_MESSAGE_UPDATE in MIGO transaction

    Hi,
    I am facing the the error in FM RV_MESSAGE_UPDATE for MIGO transaction as below:
    Report          SAPLMIGO
    Transaction     MIGO
    Error details   Class:     FPRUNX    
    Error Number:    102 - No job started
    Status : Update was terminated
    I have checked in SM13 transaction but I am not able to get the root cause for this error.
    Please advice.
    Ashish Dholi

    Maybe it's the ADSUSER issue, check this:
    http://scn.sap.com/message/8210637

  • Account determination error when i do MIGO transaction

    Hi All,
    When i post MIGO transaction I get this error.
    ACCOUNT DETERMINATION FOR ENTRY INT BSX--3000 NOT POSSIBLE.
    Can anybody help me to resolve this issue.
    Regards,
    Srivatsan

    Hi,
    Transaction Event Key "BSX" is used for inventory posting.At the time of MIGO Stock/Inventory Account is debited.
    Please check your material code. As per the error message the valuation class for your material code should be 3000. Maintain appropriate GL account for Valuation Class 3000 in BSX key.
    Use T Code OBYC to view all the transaction event keys. Scroll down to BSX which might be 11 th in the list, and double click on it. You will find a combination of Valuation modifier, Valuation class and GL Account. Please mantain appropriate GL code against valuation class 3000.
    If you are not confident enough you can take the help of your MM consultant.
    Regards,
    Swapnil

  • Account Determination error during Import MIGO transaction

    Dear ppl,
    Could any body help me in resolving this issue?
    While doing MIGO transaction for import PO, the following error message is surfacing.
    - Accoun determination forentry NML______N100______3000 not possible.
    Its not at all showing the accounting key. OBYC setting for all relevany accounting keys are correct. I have checked multiple times.
    - At the time of MIGO, commercial invoice no. against customs duties MIRO is being referred to, but this error is coming at the time of posting.
    Regards,

    Hi There,
    The majority of the times the error M8147 is raised, is due to a missing entry for one of the the following within table T030.                                                                               
    "Account determination for entry A B C D E not possible"                                                                               
    Please check in transaction OBYC and maintain an entry for the transaction key in question :
    A  Chart of Accts    : KTOPL                                            
    B  Transaction        : KTOSL                                              
    C  Val.Grpg Code    : BWMOD                                              
    D  Acct modif          : KOMOK                                             
    E  Valuation Class   : BKLAS    
    Best Regards,
    Elaine.

  • While doing MIGO transaction system showing error: Check table169P the entr

    Hi experts,
    while doing MIGO transaction system showing error: Check table169P the entry BP01 does not exit.
    pls do needful.
    Thanks&Regards
    sreenivas.p

    Hi,
    Please specify Whether you are doing Blocking of Invoices or what?
    As the T169P is A Parameters Invoice Verification, so you can check the values for T169P table in SE16 so that you will get Clear idea regarding  company code BP01 in which the stochastic block is active with Threshold value for stochastic block...
    Please check....
    For maintaining Entries please go to OMRG maintain Company code and Threshold value as per client requirement so that This will specifies the degree of probability that an invoice is stochastically blocked.
    Regards,
    Ninad Kshirsagar

  • Error in BED in MIGO transaction

    Hi Experts,
    The BED is getting populated for 1No. only. It is not getting multiplyed with the GR quantity.  We are using TAXINJ and
    please guide me how to resolve this.
    Thanks
    Ganesh

    Hi,
    Thanks for your quick reply, I have maintained tax code in PO, rate in FTXP & J1ID.  Is it required to maintain in FV11/13 for TAXINJ procedure?
    BED is coming to MIGO transaction for 1 quantity only. It is not getting muliplied by the GR quantity.
    Thanks
    Ganesh

  • ABAP DUMP While doing GI Through Zmovement type in MIGO Transaction

    Hi ,
    We have migrated from FM FBS to BCS from 12.01.2015.
    And we are using 101 profile with GR and IR update.
    We received blow ABAP Dump while doing the GI through MIGO Transaction.
    Can you please help on this.
    Dump detatils
    Category               ABAP Programming Error
    Runtime Errors         MESSAGE_TYPE_X
    ABAP Program           CL_BUAVC_ENTRY================CP
    Application Component  PSM-FM-BCS-AC
    Date and Time          13.01.2015 09:10:00
    Operating system..... "AIX 1 6, AIX 1 7"                                                      |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 0                                                                                    |
    |    EM...... 33518336                                                                             |
    |    Heap.... 0                                                                                    |
    |    Page.... 196608                                                                               |
    |    MM Used. 21989120                                                                             |
    |    MM Free. 3145840                                                                              |
    |User and Transaction                                                                              |
    |    Client.............. 256                                                                      |
    |    User................ "MM_BUX00_ZZ"                                                            |
    |    Language key........ "R"                                                                      |
    |    Transaction......... "MIGO_GI "                                                               |
    |    Transaction ID...... "54AEDD9E3EE60710E10080000A15C616"                                       |
    |                                                                                                  |
    |    EPP Whole Context ID.... "54B35F7088300910E10080000A15C616"                                   |
    |    EPP Connection ID....... 00000000000000000000000000000000                                     |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "CL_BUAVC_ENTRY================CP"                                       |
    |    Screen.............. "SAPLMIGO 0001"                                                          |
    |    Screen Line......... 18                                                                       |
    |    Debugger Active..... "none"                                                                   |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "CL_BUAVC_ENTRY================CP" -                 |
    |     in "POST".                                                                                   |
    |    The main program was "SAPLMIGO ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 82                                  |
    |    of the (Include) program "CL_BUAVC_ENTRY================CM00J".                               |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |   52|*--- method has provided some errors!):                                                     |
    |   53|                                                                                            |
    |   54|* Note 1499464:                                                                             |
    |   55|*      IF cl_abap_aab_utilities=>is_active( id = 'BUAVC_GROUP'                              |
    |   56|*       mode_assert_dump = 'X' ) = 'X'.                                                     |
    |   57|      MOVE 'X' TO l_flg_dump.                                                               |
    |   58|*      ENDIF.                                                                               |
    |   59|                                                                                            |
    |   60|*--- Check if the entry buffer of the AVC ledger contains data records                      |
    |   61|*--- from previous COLLECT events:                                                          |
    |   62|      IF ( l_f_avc_ledger-ref_ledger->entry_buffer_lines_count( ) > 0 ).                    |
    |   63|*--- Sorry, must dump:                                                                      |
    |   64|        ASSERT ID buavc_group                                                               |
    |   65|               FIELDS c_avc_text 'POSTING_NOT_ALLOWED'                                      |
    |   66|               CONDITION l_flg_dump <> 'X'.                                                 |
    |   67|        IF l_flg_dump = 'X'.                                                                |
    |   68|          MESSAGE x002(buavc) WITH c_avc_text space                                         |
    |   69|                                   'POSTING_NOT_ALLOWED' space.                             |
    |   70|        ENDIF.                                                                              |
    |   71|      ENDIF.                                                                                |
    |   72|    ENDIF.                                                                                  |
    |   73|*----------------------------------------------------------------------                     |
    |   74|* Note 1666556:                                                                             |
    |   75|    IF me->g_commit_before_post EQ 'X'.                                                     |
    |   76|*--- An unauthorized COMMIT WORK occurred before calling this POST                          |
    |   77|*--- method. This COMMIT WORK has refreshed the AVC entry buffer and                        |
    |   78|*--- would thus create a database inconsistency!                                            |
    |   79|      MOVE 'X' TO l_flg_dump.                                                               |
    |   80|      IF l_flg_dump = 'X'.                                                                  |
    |   81|*--- Sorry, must dump (see note 1666556):                                                   |
    |>>>>>|        MESSAGE x002(buavc) WITH c_avc_text space                                           |
    |   83|                                 'INVALID_COMMIT' space.                                    |
    |   84|      ENDIF.                                                                                |
    |   85|    ENDIF.                                                                                  |
    |   86|*----------------------------------------------------------------------                     |
    |   87|                                                                                            |
    |   88|                                                                                            |
    |   89|*--- Call the POST method of the corresponding ledger instance:                             |
    |   90|    CALL METHOD l_f_avc_ledger-ref_ledger->post                                             |
    |   91|      EXPORTING                                                                             |
    |   92|        i_ref_appl_log = me->g_ref_appl_log                                                 |
    |   93|        i_doc_ref      = i_doc_ref.                                                         |
    |   94|                                                                                            |
    |   95|  ENDLOOP.                                                                                  |
    |   96|                      
    Thanks Advance.
    SAM

    Hi Sam,
    Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
    Regards,
    Prakash.

  • Error in MIGO while GR reversal - Message no. M7021

    Hello MM Sapperu2019s,
    I got an error in MIGO as meniotned below,
    Deficit of Project stock unr. 2,00 PC : XXXXXXX 9093 1111 Q
    Up on checking from my side the issue I observed that while executing GR reversal for the PO in transaction MIGO user is getting the error as Deficit of Project stock unr. 21,00 PC : XXXXXXX 9093 1111 Q because there is no project stock available for the relevant material.This I have checked in MMBE transaction for the respective material, Project stock is missing.
    Now I need to know if I want to maintain the project stock for the respective WBS element in MMBE and proceed with reversal of GR in MIGO.Please let me know what action I need to take it to resolve this.
    PS: PO qty is 26 and IR made first for qty 1 and then GR made for qty 26.
    I have also referred the below link in SDN related to this query,
    GRN reverse problem
    Where it talks about the material issued document reversal which is relevant to me part from that other actions also required I feel.
    Cheers,
    Kumar.S

    KUMAR.S. wrote:
    Hello MM Sapperu2019s,
    > I got an error in MIGO as meniotned below,
    > Deficit of Project stock unr. 2,00 PC : XXXXXXX 9093 1111 Q
    > Up on checking from my side the issue I observed that while executing GR reversal for the PO in transaction MIGO user is getting the error as Deficit of Project stock unr. 21,00 PC : XXXXXXX 9093 1111 Q because there is no project stock available for the relevant material.This I have checked in MMBE transaction for the respective material, Project stock is missing.
    > Now I need to know if I want to maintain the project stock for the respective WBS element in MMBE and proceed with reversal of GR in MIGO.Please let me know what action I need to take it to resolve this.
    > PS: PO qty is 26 and IR made first for qty 1 and then GR made for qty 26.
    > I have also referred the below link in SDN related to this query,
    > GRN reverse problem
    > Where it talks about the material issued document reversal which is relevant to me part from that other actions also required I feel.
    > Cheers,
    > Kumar.S
    Hi,
    first u have to reverse the transfer posting (if it is applicable) are directly u can reverse the GI after that u can cancel gr.
    u can check  the stock in mmbe for every transaction's.
    may be it is helpful for u.
    Regrds
    Raj.

  • QM-Error during MIGO(movmnt type-322)

    I have done the UD stock moves to unrestricted.NowI am trying to revert material from unrestricted to quality in the same storage location by movement type 322 in MIGO transaction.
    I am getting this error' change the inspection stock of material in QM only'
    Pl. help.
    Thanks & Regards,
    Varun Kumar

    Hi,
    Reversing Stock Postings Locate the document in its SAP Library structure
    1. Choose Logistics ® Materials Management ® Inventory Management ® Goods Movement ® Goods receipt ® For purchase order ® PO number known.
    The initial screen for creating a goods receipt for a purchase order appears.
    2. In the field for the movement type, enter
    3. 102 (goods receipt for a purchase order into warehouse - reversal). In the field for the purchase order, enter the purchase order number for the original goods receipt.
    Note
    You can copy the purchase order number from the inspection lot.
    4. Choose Enter to display the selection screen for the purchase order items.
    5. Select the purchase order item for which you want to create the goods receipt and set the Stock type indicator to the stock to which the goods were originally posted with the usage decision (for example, F for unrestricted-use stock or S for blocked stock).
    6. Save the goods receipt and exit the Materials Management component.
    7. Choose Logistics ® Quality management ® Quality inspection ® Inspection lot ® Usage decision ® Change with history.
    The initial screen for changing a usage decision appears.
    8. Enter the number of the inspection lot for which you previously made the usage decision and choose Usage decision (UD).
    9. To cancel the inspection lot, choose Usage decision ® Functions ® Cancel lot in the usage decision screen.
    Also check the SAP note :  175842 for Transfer of Unres stk to QI stock.
    Hope this will help you.
    regards
    radhak mk

  • Reg Dump in MIGO Transaction

    Hi all,
    When I am executing MIGO transaction in Pre-Production I am getting error as 'GETWA_NOT_ASSIGNED'. IF I check thru ST22, showing message as 'Field symbol has not yet been assigned'. Could anybody please assist in this regard.Thanks in advance.
    Thanks & Regards.
    I. Reddy Prasad

    Hi
    Pls check the following notes
    Note 496258 - MIGO: ABAP runtime error GETWA_NOT_ASSIGNED
    Note 712454 - MB1B/MIGO aborts with GETWA_NOT_ASSIGNED
    Note 979013 MIGO: Programmabbruch GETWA_NOT_ASSIGNED in LMIGOKC2
    Note 379448 GETWA_NOT_ASSIGNED for return delivery with MIGO
    Note 965675 MIGO: Termination after setting OK flag for tied empties
    Pls take opinion from SAP / Basis before implementing the note
    Regards
    Madhan

Maybe you are looking for