Message at MIGO transaction

Hi Gurus,
I am using a BADI MB_DOCUMENT_BADI implementation.
At the MB_DOCUMENT_BEFORE_UPDATE method, I am doing a call transaction at VT02N.
I need put one message at MIGO transaction, that shows when VT02N call transaction was not succesfull.
This badi doesn't have any returm messages parameters.
Does anyone knows how can I return those messages to MIGO?
I think that I can use EXPORT TO MEMORY, but I don't know where can I import and use.
Thank you all.

Done.

Similar Messages

How to Find Location of Error Message in MIGO Transaction

I keep getting an error in transaction MIGO: Create account N450010 for 08/07/2007 as a cost element in controlling area BFP1. According to the functional person the account has been created. Any other way to find out besides a "where-used" on the message class and number to find out where this message is coming from? The where used is not bringing me any results.....Thanks.

Hi
Probably the message is called dynamically, so u should try to check by debug when that message is raised.
U can set a break-point for the statament MESSAGE.
Max

Reg:Error message in MIGO Transaction

Hi All,
I added the new tab strip in MIGO Screen. now i need to make all the fields as mandatory. so using BADI (MB_MIGO_BADI) i gave the mandatory check ( if the Zfield = ' ', then error message) while clicking the check button before posting the material number. But it prevents to proceed further, simply it skips the transaction because of error message. and at the same time 'i should not use the information message'. my requirement is 'Error message should be populated after clicking the check button but it should allow to enter the mandatory fields after the error message'. i.e it should not skip the transaction after the error message.
Please help me.
Thanks & Regards
Vijay.R

Hi
Probably the message is called dynamically, so u should try to check by debug when that message is raised.
U can set a break-point for the statament MESSAGE.
Max

Re:In MIGO transaction is there any place where we can maintain the message

Hi All,
In MIGO transaction is there any place where we can maintain the message.
Thanks
siva

Hi,
you need to go to MB02 and double click on the line item say the quantity, then you get the messages icon, click here to maintain the messages.
Or you can automatically set this by MN21.
Thanks & Regards,
Kiran

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

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

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

Warning message in MIGO - Diference on Qty of entry/Qty in delivery note

Hello,
I want to set a warning (or even error) message when, in MIGO transaction, the quantity in the delivery note is higher than the quantity in unit of entry set up (both in the quantity screen).
A message regarding the difference between the quantity in unit of entry and the quantity order is standard and is already set.
How can I proceed?
Thank you,
Gonçalo.

Hi,
Thanks for the help, but I still can't manage to set the warning message. In fact I tried to set it on OMRM and in spro-mat management-purchasing-environment data-define messages. The only message I get in MIGO is M7021 (difference between the quantity order and the quantity in unit of entry (quantity details)... but I also want a message to occur in case of a difference in quantity of delivery note and qty in unit of entry.
I set as much messages as possible, do you know what's the message regarding this warning on table V_160M_
Thanks again,
Goncalo.

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

Bapi for migo transaction

i have created a bapi to upload data for MIGO transaction.. (GOODS RECEIPT-->PURCHASE ORDER)
i am getting the error " stock posting is not possible for this material "'.
when i create directly, it is posted.. while uploading through the program it shows the above error.
please suggest if anyone knows....
Thanks in advance,
Dhivya N.

*& Report ZR_MIGO_UPLOAD
*& package name : zabap
*& transport request number : MIDK901443
*& program to upload goods movement
REPORT ZR_MIGO_UPLOAD.
***DATA DECLARATION***
type-POOLs: icon.
TYPES: BEGIN OF TY_GR_PO,
        EBELN(10) TYPE c ,     "'PO NUMBEr
        EBELP(10) TYPE c,     "PO ITEM NUMBER
*       LGOBE TYPE LGOBE,     "STORAGE LOCATION DESCRIPTION
        LGORT(10) TYPE c,     "STORAGE LOCATION
        XFELD TYPE c,     "ITEM OK
        GERNR(10) TYPE c,     "SERIALNUMBER
        END OF TY_GR_PO.
DATA: TA_GR_PO TYPE TABLE OF TY_GR_PO,    "TABLE FOR GOODS RECEIPT PURCHASE ORDER
       WA_GR_PO TYPE TY_GR_PO.
DATA: BLDAT TYPE BLDAT,     "DOCUMENT DATE
        BUDAT TYPE BUDAT,     "POSTING DATE
        WEVER TYPE WEVER.     "VERSION FOR PRINTING GR SLIP
***BAPI DECLARATION***
DATA: BEGIN OF GM_HEAD OCCURS 0.                    "Material Document Header Data
         INCLUDE STRUCTURE BAPI2017_GM_HEAD_01.
DATA: END OF GM_HEAD.
DATA: BEGIN OF GM_CODE OCCURS 0.
         INCLUDE STRUCTURE BAPI2017_GM_CODE.          "Assign Code to Transaction for Goods Movement
DATA: END OF GM_CODE.
DATA: BEGIN OF GM_RET OCCURS 0.
         INCLUDE STRUCTURE BAPI2017_GM_HEAD_RET.       "Material Document Number/Material Document Year
DATA: END OF GM_RET.
DATA: BEGIN OF GM_ITEM OCCURS 0.
         INCLUDE STRUCTURE BAPI2017_GM_ITEM_CREATE.    "Material Document Items
DATA: END OF GM_ITEM.
DATA: BEGIN OF GM_SER OCCURS 0.
         INCLUDE STRUCTURE BAPI2017_GM_SERIALNUMBER.    "Serial Number
DATA: END OF GM_SER.
data: BEGIN OF ta_bapireturn OCCURS 0.
        INCLUDE STRUCTURE BAPIRET2.
data: END OF ta_bapireturn.
***declaration of excel file handling table***
FIELD-SYMBOLS: <fs> type any.    "field symbol for alsm_excel
DATA: TA_EXCEL TYPE TABLE OF ALSMEX_TABLINE, "table to contain excel sheet values
       WA_EXCEL TYPE ALSMEX_TABLINE.
***declaration of other parameters***
data:       V_brow type i VALUE    2,    "BEGIN OF ROW
             V_bcol type i value   1,     "BEGIN OF COL
             V_erow type i value 65536,   "END OF ROW
             V_ecol type i value 256.     "END OF COLUMN
DATA: V_sear type string,
        V_INDEX TYPE i,
        V_tabix type sy-tabix,     "current line.
        v_lines type i.          "total number of records
DATA: DATE TYPE DATS.
***SELECTION SCREEN***
***SELECTION SCREEN DESIGN***
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP 3.
PARAMETERS: zCODE(2) TYPE C MATCHCODE OBJECT H_T158G,
             zrefdoc type REFDOC,
             version type WEVER.
SELECTION-SCREEN skip 5.
PARAMETERS: p_file type ibipparms-path.
SELECTION-SCREEN SKIP 3.
SELECTION-SCREEN END OF BLOCK b1.
***SELECTION SCREEN VALUE REQUEST***
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
   CALL FUNCTION 'F4_FILENAME'                                    "f4 help for file name
     EXPORTING
       PROGRAM_NAME = SYST-CPROG
       DYNPRO_NUMBER = SYST-DYNNR
       FIELD_NAME    = 'P_FILE'
     IMPORTING
       FILE_NAME     = P_FILE.
***SELECTION SCREEN EVENT***
AT SELECTION-SCREEN.                                 "validation
   if p_file <> ''.
     V_sear = p_file.
     SEARCH V_sear for '.xls'.
     if sy-subrc <> 0.
       message 'please provide excel file. it is not valid' type 'E'.
     ENDIF.
   ENDIF.
INITIALIZATION.
*   DATE = '17.04.14'.
   GM_HEAD-PSTNG_DATE = SY-DATUM.
   GM_HEAD-DOC_DATE   = SY-DATUM.
   gm_head-pr_uname = sy-uname.
***START OF SELECTION***
START-OF-SELECTION.
   gm_head-REF_DOC_NO = zrefdoc.
   gm_head-VER_GR_GI_SLIP = version.
   GM_CODE-GM_CODE = zCODE.
   PERFORM EXCEL_UPLOAD.
   PERFORM EXCEL_CONVERSION.
   PERFORM NO_RECORDS.
END-OF-SELECTION.
   PERFORM BAPI_ASSIGNMENT.
   PERFORM BAPI_FM.
*&      Form EXCEL_UPLOAD
*       text
* --> p1        text
* <-- p2        text
FORM EXCEL_UPLOAD .
   CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
     EXPORTING
       FILENAME                = P_FILE
       I_BEGIN_COL             = V_BCOL
       I_BEGIN_ROW             = V_BROW
       I_END_COL               = V_ECOL
       I_END_ROW               = V_EROW
     TABLES
       INTERN                  = TA_EXCEL
     EXCEPTIONS
       INCONSISTENT_PARAMETERS = 1
       UPLOAD_OLE              = 2
       OTHERS                  = 3.
ENDFORM.                    " EXCEL_UPLOAD
*&      Form EXCEL_CONVERSION
*       text
* --> p1        text
* <-- p2        text
FORM EXCEL_CONVERSION .
   if ta_excel is NOT INITIAL.
     sort ta_excel by row col.
     clear wa_excel.
     clear wa_GR_PO.
     LOOP AT ta_excel INTO wa_excel.
       move wa_excel-col to v_index.
       ASSIGN COMPONENT v_index OF STRUCTURE wa_GR_PO to <fs>.
       if sy-subrc = 0.
         move wa_excel-value to <fs>.
       ENDIF.
       at END OF row.
         append wa_GR_PO to ta_GR_PO.
         clear wa_GR_PO.
       ENDAT.
     ENDLOOP.
   else.
     MESSAGE 'no data for conversion' type 'I'.
   ENDIF.
ENDFORM.                    " EXCEL_CONVERSION
*&      Form NO_RECORDS
*       text
* --> p1        text
* <-- p2        text
FORM NO_RECORDS .
   DESCRIBE TABLE ta_GR_PO LINES v_lines.
   if v_lines = 0.
     MESSAGE 'NO RECORDS TO UPLOAD' TYPE 'E'.
   ENDIF.
ENDFORM.                    " NO_RECORDS
*&      Form BAPI_ASSIGNMENT
*       text
* --> p1        text
* <-- p2        text
FORM BAPI_ASSIGNMENT .
   IF TA_GR_PO IS NOT INITIAL.
     LOOP AT TA_GR_PO INTO WA_GR_PO.
       gm_item-PO_NUMBER = wa_gr_po-ebeln.
       GM_ITEM-STGE_LOC = WA_GR_PO-LGORT.
       GM_ITEM-PO_ITEM = WA_GR_PO-EBELP.
       GM_ITEM-NO_MORE_GR = 'X'."WA_GR_PO-XFELD'.
*      GM_SER-SERIALNO = WA_GR_PO-GERNR.
       gm_item-NO_MORE_GR = 1.
       gm_item-ENTRY_QNT = 2.
       gm_item-MOVE_TYPE = 101.
*      gm_item-MVT_IND = 'B'.
       gm_item-plant = 'P001'.
       gm_item-move_stloc = 'FG01'.
*      GM_ITEM-SPEC_STOCK = 'K'.
       APPEND GM_ITEM.
       APPEND GM_SER.
     ENDLOOP.
    ELSE.
      MESSAGE 'DATA IS NOT UPLOADED' TYPE 'I'.
    ENDIF.
ENDFORM.                    " BAPI_ASSIGNMENT
*&      Form BAPI_FM
*       text
* --> p1        text
* <-- p2        text
FORM BAPI_FM .
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
   EXPORTING
     GOODSMVT_HEADER               = gm_head
     GOODSMVT_CODE                 = gm_code
*   TESTRUN                       = ' '
*   GOODSMVT_REF_EWM              =
IMPORTING
    GOODSMVT_HEADRET              = gm_ret
*   MATERIALDOCUMENT              =
*   MATDOCUMENTYEAR               =
   TABLES
     GOODSMVT_ITEM                 = gm_item
    GOODSMVT_SERIALNUMBER         = gm_ser
     RETURN                        = ta_bapireturn
*   GOODSMVT_SERV_PART_DATA       =
*   EXTENSIONIN                   =
if ta_bapireturn-type = 'S'.
     write:/ icon_green_light as icon,
             'success: Material document',gm_ret-mat_doc, 'is created for the GOODS RECEIPT- po number : ', wa_gr_po-ebeln,
           / 'reason:' , ta_bapireturn-message.
ELSEIF ta_bapireturn-type = 'E'.
     write:/ icon_red_light as icon,
             'error: Material document',gm_ret-mat_doc , 'is not created for the GOOD RECEIPT- po number : ', wa_gr_po-ebeln,
           / 'reason:' , ta_bapireturn-message.
ENDIF.
ENDFORM.                    " BAPI_FM

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.

Missing part message in MIGO

Hello,
we have activated the missing part message in MIGO using transaction OMBC.
All is working fine and we receive an notification in business workplace.
The problem is that only one person receives the mail and we want that all MRP controllers get an notification.
In transaction OMBC under "Mail user" we can only maintain one "Recipient Name".
But what is the meaning of "Recipient for mail to MRP controller"? Can we here use position to maintain all controolers in the organization model of the PD (PD-ORG)?
Thanks
Arnfried

Hi There
Specification of the mail recipient- System sends the missing part message to the material planner(MRP Controller) responsible for the material,, in order for this to happen , a user ID must be assigned to the material planner,,
Specification of missing part expediter- if no user ID is assigned to the responsible material planner, the message is sent to the central missing part expediter responsible for the plant. This person is defined per plant,,
So this is what happening in your place,, maintain the user ID to the MRP controller,, then it will work fine,,
Maintain the below settings--
SPRO-IMG-Materials Management-Consumption-Based Planning-Master Data-Define MRP Controllers-Double click on MRP controllers-Maintain the field Recipient Name (User ID) then system will trigger the mail to MRP controllers...
Hope it helps
Thanks
Senthil

Document date&Posting date Validation In MIGO Transaction

Hi,
I need to control document date should not be in future date comparing to posting date and should not be past date comparing to PO date in MIGO transaction.Pls suggest.
Regards
Mani

Dear Mani,
Goto Spro
Materials Management -> Inventory Management and Physical Inventory -> Define Attributes of System Messages
Goto Settings for System Messages and select
Version 00
Application area -- M7
Messages no -- 088 -- Document date lies in the future. (Check your entry)
Convert in Error Massage.
Regards,
PK

Message at MIGO transaction

Similar Messages

Maybe you are looking for