Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

RUNTIME ERROR IN MIGO TCODE FOR PARTICULAR PO

former_member185124
Participant
0 Kudos

HI FRIENDS,

I GOT A RUNTIME ERROR IN 'MIGO' TCODE ONLY FOR PARTICULAR PO NO: '  IN MESSAGE CLASS '00',398 MESSAGE NO,Variable 1.......... "RG register not same for material".

SO,PLEASE FIND THE ATTACHED FILE BELOW .

|    RG register not same for material                                                            |

|                                                                                                  |

|    Long text of error message:                                                                  |

|    Diagnosis                                                                                    |

|        Placeholder for batch input error text, this message is not output.                      |

|        RG register not same for material                                                        |

|    System Response                                                                              |

|    Procedure                                                                                    |

|                                                                                                  |

|    Technical information about the message:                                                      |

|    Message class....... 00                                                                      |

|    Number.............. 398                                                                      |

|    Variable 1.......... "RG register not same for material"                                      |

|    Variable 2.......... " "                                                                      |

|    Variable 3.......... " "                                                                      |

|    Variable 4.......... " "                                                                      |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|How to correct the error                                                                          |

|    Probably the only way to eliminate the error is to correct the program.                      |

|    -                                                                                            |

|                                                                                                  |

|    If the error occures in a non-modified SAP program, you may be able to                        |

|    find an interim solution in an SAP Note.                                                      |

|    If you have access to SAP Notes, carry out a search with the following                        |

|    keywords:                                                                                    |

|                                                                                                  |

|    "MESSAGE_TYPE_X" " "                                                                          |

|    "SAPLMBWL" or "LMBWLU21"                                                                      |

|    "MB_POST_GOODS_MOVEMENT"                                                                      |

|                                                                                                  |

|    If you cannot solve the problem yourself and want to send an error                            |

|    notification to SAP, include the following information:                                      |

|                                                                                                  |

|    1. The description of the current problem (short dump)                                        |

|                                                                                                  |

|      To save the description, choose "System->List->Save->Local File                            |

|    (Unconverted)".                                                                              |

|                                                                                                  |

|    2. Corresponding system log                                                                  |

|                                                                                                  |

|      Display the system log by calling transaction SM21.                                        |

|      Restrict the time interval to 10 minutes before and five minutes                          |

|    after the short dump. Then choose "System->List->Save->Local File                            |

|    (Unconverted)".                                                                              |

|                                                                                                  |

|    3. If the problem occurs in a problem of your own or a modified SAP                          |

|    program: The source code of the program                                                      |

|      In the editor, choose "Utilities->More                                                    |

|    Utilities->Upload/Download->Download".                                                        |

|                                                                                                  |

|    4. Details about the conditions under which the error occurred or which                      |

|    actions and input led to the error.                                                          |

|                                                                                                  |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|System environment                                                                                |

|    SAP Release..... 731                                                                          |

|    SAP Basis Level. 0012                                                                        |

|                                                                                                  |

|    Application server... "vjdpr1_svc"                                                            |

|    Network address...... "10.101.141.5"                                                          |

|    Operating system..... "AIX"                                                                  |

|    Release.............. "7.1"                                                                  |

|    Hardware type........ "00051663D600"                                                          |

|    Character length.... 8 Bits                                                                  |

|    Pointer length....... 64 Bits                                                                |

|    Work process number.. 14                                                                      |

|    Shortdump setting.... "full"                                                                  |

|                                                                                                  |

|    Database server... "vjdpr1"                                                                  |

|    Database type..... "ORACLE"                                                                  |

|    Database name..... "VJP"                                                                      |

|    Database user ID.. "SAPSR3"                                                                  |

|                                                                                                  |

|    Terminal.......... "Welcome-to-Suri-Wor"                                                      |

|                                                                                                  |

|    Char.set.... "en_US.ISO8859-1"                                                                |

|                                                                                                  |

|    SAP kernel....... 721                                                                        |

|    created (date)... "May 27 2014 03:46:44"                                                      |

|    create on........ "AIX 1 6 00CFADC14C00"                                                      |

|    Database version. "OCI_112, 11.2.0.4.0, V1, default"                                          |

|                                                                                                  |

|    Patch level. 300                                                                              |

|    Patch text.. " "                                                                              |

|                                                                                                  |

|    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              |

|    SAP database version. 721                                                                    |

|    Operating system..... "AIX 1 6, AIX 1 7"                                                      |

|                                                                                                  |

|    Memory consumption                                                                            |

|    Roll.... 0                                                                                    |

|    EM...... 25139136                                                                            |

|    Heap.... 0                                                                                    |

|    Page.... 172032                                                                              |

|    MM Used. 19731888                                                                            |

|    MM Free. 1213888                                                                              |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|User and Transaction                                                                              |

|    Client.............. 400                                                                      |

|    User................ 10208                                                                    |

|    Language key........ "E"                                                                      |

|    Transaction......... "MIGO "                                                                  |

|    Transaction ID...... "5499A1F84E4B12C0E10080000A658D07"                                      |

|                                                                                                  |

|    EPP Whole Context ID.... "5499A1944E4B12C0E10080000A658D07"                                  |

|    EPP Connection ID....... 00000000000000000000000000000000                                    |

|    EPP Caller Counter...... 0                                                                    |

|                                                                                                  |

|    Program............. "SAPLMBWL"                                                              |

|    Screen.............. "SAPLMIGO 0001"                                                          |

|    Screen Line......... 18                                                                      |

|    Debugger Active..... "none"                                                                  |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Information on where terminated                                                                  |

|    Termination occurred in the ABAP program "SAPLMBWL" - in                                      |

|    "MB_POST_GOODS_MOVEMENT".                                                                    |

|    The main program was "SAPLMIGO ".                                                            |

|                                                                                                  |

|    In the source code you have the termination point in line 83                                  |

|    of the (Include) program "LMBWLU21".                                                          |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Source Code Extract                                                                              |

----------------------------------------------------------------------------------------------------

|Line |SourceCde                                                                                  |

----------------------------------------------------------------------------------------------------

|  53|  ELSE.                                                    "1245374                        |

|  54|    l_mem_id = 'MKPF-XBLNR'.                                "1245374                        |

|  55|    FREE MEMORY ID l_mem_id.                                "1245374                        |

|  56|  ENDIF.                                                                                    |

|  57|  IF xmkpf-xabln IS INITIAL.                              "note 434093                    |

|  58|    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                  "note 434093                      |

|  59|  ENDIF.                                                  "note 434093                    |

|  60|                                                                                            |

|  61|* Ensure that mseg-xblnr_mkpf is filled when the goods movement is                          |

|  62|* posted directly in VL01N/VL31N.                                                          |

|  63|  IF NOT xblnr_sd IS INITIAL.                                  "1685136                    |

|  64|  DATA: ls_mseg_mkpf  LIKE xmseg.                            "1685136                    |

|  65|    ls_mseg_mkpf-xblnr_mkpf = xmkpf-xblnr.                    "1685136                    |

|  66|    MODIFY xmseg FROM ls_mseg_mkpf TRANSPORTING xblnr_mkpf    "1685136                    |

|  67|                  WHERE xblnr_mkpf NE xmkpf-xblnr.              "1685136                    |

|  68|  ENDIF.                                                      "1685136                    |

|  69|                                                                                            |

|  70|                                                                                            |

|  71|ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.                      |

|  72|                                                                                            |

|  73|ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.                            |

|  74|  CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'                                            |

|  75|    EXCEPTIONS                                                                              |

|  76|      error_message = 4.                                                                    |

|  77|*  As soon as we have started to put things into UPDATE TASK, we must                      |

|  78|*  ensure that errors definitely terminate the transaction.                                |

|  79|*  MESSAGE A is not sufficient because it can be catched from                              |

|  80|*  external callers which COMMIT WORK afterwards, resulting in                              |

|  81|*  incomplete updates. Read note 385830 for the full story.                                |

|  82|  IF NOT sy-subrc IS INITIAL.                                                              |

|>>>>>|    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH        "385830                        |

|  84|              sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.                                        |

|  85|*    MESSAGE A263.                                                                        |

|  86|  ENDIF.                                                                                    |

|  87|* Optische Archivierung                                                                    |

|  88|* Spaete Erfassung mit Barcode                                                              |

|  89|* Redesign of barcode handling -> note 780365                                              |

|  90|  PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr                                        |

|  91|                                        xmkpf-mjahr                                        |

|  92|                                        barcode.                                          |

|  93|                                                                                            |

|  94|  MOVE-CORRESPONDING xmkpf TO emkpf.                                                        |

|  95|  CALL FUNCTION 'MB_MOVEMENTS_REFRESH'                                                      |

|  96|    EXCEPTIONS                                                                              |

|  97|      error_message = 4.                                                                    |

|  98|  IF NOT sy-subrc IS INITIAL.                                                              |

|  99|    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH        "385830                        |

|  100|              sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.                                        |

|  101|*    MESSAGE A261.                                                                          |

|  102|  ENDIF.      

7 REPLIES 7

Former Member
0 Kudos

Hii Mahesh

is it excise related material? consult your sd consultant and check excise configuration

Regards

Gaurav

0 Kudos

Hi Gaurav,

Thank u for given reply,But it is Abap runtime error.It shows in the below error.Plz check the below post once then you can understand .

Runtime Error :

Category ABAP Programming Error

Runtime Errors MESSAGE_TYPE_X

ABAP Program SAPLMBWL

Application Component MM-IM

Date and Time 27.12.2014 13:08:54

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

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

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What can you do? |

|    Note down which actions and inputs caused the error.                                          |

| |

| |

|    To process the problem further, contact you SAP system                                        |

| administrator. |

|                                                                                                  |

|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |

|    at and manage termination messages, and you can also                                          |

|    keep them for a long time. |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Error analysis |

|    Short text of error message: |

|    RG register not same for material |

| |

|    Long text of error message:                                                                   |

|     Diagnosis |

|         Placeholder for batch input error text, this message is not output.                      |

|         RG register not same for material |

|     System Response |

|     Procedure                                                                                    |

| |

|    Technical information about the message: |

|    Message class....... 00 |

| Number.............. 398 |

|    Variable 1.......... "RG register not same for material"                                      |

|    Variable 2.......... " " |

|    Variable 3.......... " " |

|    Variable 4.......... " " |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|How to correct the error |

|    Probably the only way to eliminate the error is to correct the program.                       |

|    -                                                                                             |

| |

|    If the error occures in a non-modified SAP program, you may be able to                        |

|    find an interim solution in an SAP Note. |

|    If you have access to SAP Notes, carry out a search with the following                        |

|    keywords:                                                                                     |

| |

| "MESSAGE_TYPE_X" " " |

| "SAPLMBWL" or "LMBWLU21" |

| "MB_POST_GOODS_MOVEMENT" |

|                                                                                                  |

|    If you cannot solve the problem yourself and want to send an error                            |

|    notification to SAP, include the following information:                                       |

| |

|    1. The description of the current problem (short dump)                                        |

|                                                                                                  |

|       To save the description, choose "System->List->Save->Local File                            |

| (Unconverted)". |

| |

|    2. Corresponding system log |

| |

|       Display the system log by calling transaction SM21.                                        |

|       Restrict the time interval to 10 minutes before and five minutes                           |

|    after the short dump. Then choose "System->List->Save->Local File                             |

| (Unconverted)". |

| |

|    3. If the problem occurs in a problem of your own or a modified SAP                           |

|    program: The source code of the program |

|       In the editor, choose "Utilities->More |

| Utilities->Upload/Download->Download". |

| |

|    4. Details about the conditions under which the error occurred or which                       |

|    actions and input led to the error. |

|                                                                                                  |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|System environment |

|    SAP Release..... 731 |

|    SAP Basis Level. 0012 |

| |

|    Application server... "vjdpr1_svc"                                                            |

|    Network address...... "10.101.141.5" |

|    Operating system..... "AIX" |

| Release.............. "7.1"                                                                   |

|    Hardware type........ "00051663D600" |

|    Character length.... 8 Bits |

|    Pointer length....... 64 Bits |

|    Work process number.. 14 |

|    Shortdump setting.... "full"                                                                  |

| |

|    Database server... "vjdpr1" |

|    Database type..... "ORACLE" |

|    Database name..... "VJP" |

|    Database user ID.. "SAPSR3"                                                                   |

| |

| Terminal.......... "Welcome-to-Suri-Wor" |

| |

|    Char.set.... "en_US.ISO8859-1" |

| |

|    SAP kernel....... 721 |

|    created (date)... "May 27 2014 03:46:44" |

|    create on........ "AIX 1 6 00CFADC14C00" |

|    Database version. "OCI_112, 11.2.0.4.0, V1, default"                                          |

| |

|    Patch level. 300 |

|    Patch text.. " " |

|                                                                                                  |

| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |

|    SAP database version. 721                                                                     |

|    Operating system..... "AIX 1 6, AIX 1 7" |

| |

|    Memory consumption |

|    Roll.... 0 |

|    EM...... 25139136 |

|    Heap.... 0 |

|    Page.... 172032 |

|    MM Used. 19731888                                                                             |

|    MM Free. 1213888 |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client.............. 400                                                                      |

| User................ 10208 |

|    Language key........ "E" |

| Transaction......... "MIGO " |

|    Transaction ID...... "5499A1F84E4B12C0E10080000A658D07"                                       |

|                                                                                                  |

|    EPP Whole Context ID.... "5499A1944E4B12C0E10080000A658D07"                                   |

|    EPP Connection ID....... 00000000000000000000000000000000                                     |

|    EPP Caller Counter...... 0 |

| |

| Program............. "SAPLMBWL"                                                               |

| Screen.............. "SAPLMIGO 0001" |

|    Screen Line......... 18 |

|    Debugger Active..... "none" |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Information on where terminated |

|    Termination occurred in the ABAP program "SAPLMBWL" - in                                      |

|     "MB_POST_GOODS_MOVEMENT". |

|    The main program was "SAPLMIGO ". |

| |

|    In the source code you have the termination point in line 83                                  |

|    of the (Include) program "LMBWLU21". |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Source Code Extract                                                                               |

----------------------------------------------------------------------------------------------------

|Line |SourceCde |

----------------------------------------------------------------------------------------------------

|   53|  ELSE. "1245374 |

|   54|    l_mem_id = 'MKPF-XBLNR'.                                "1245374                        |

|   55|    FREE MEMORY ID l_mem_id. "1245374 |

|   56|  ENDIF. |

|   57|  IF xmkpf-xabln IS INITIAL.                               "note 434093                     |

|   58|    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093                       |

|   59|  ENDIF. "note 434093                     |

|   60| |

|   61|* Ensure that mseg-xblnr_mkpf is filled when the goods movement is                          |

|   62|* posted directly in VL01N/VL31N. |

|   63|  IF NOT xblnr_sd IS INITIAL. "1685136                    |

|   64|   DATA: ls_mseg_mkpf   LIKE xmseg.                             "1685136                    |

|   65|     ls_mseg_mkpf-xblnr_mkpf = xmkpf-xblnr. "1685136                    |

|   66|     MODIFY xmseg FROM ls_mseg_mkpf TRANSPORTING xblnr_mkpf "1685136                    |

|   67|                  WHERE xblnr_mkpf NE xmkpf-xblnr. "1685136                    |

|   68|   ENDIF. "1685136                    |

|   69| |

|   70| |

| 71|ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.                      |

|   72|                                                                                            |

| 73|ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.                             |

|   74|  CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'                                            |

|   75|    EXCEPTIONS |

|   76|      error_message = 4. |

|   77|*  As soon as we have started to put things into UPDATE TASK, we must |

|   78|*  ensure that errors definitely terminate the transaction. |

|   79|*  MESSAGE A is not sufficient because it can be catched from |

|   80|*  external callers which COMMIT WORK afterwards, resulting in                              |

|   81|*  incomplete updates. Read note 385830 for the full story. |

|   82|  IF NOT sy-subrc IS INITIAL.                                                               |

|>>>>>| MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH         "385830                         |

|   84|               sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.                                         |

|   85|*     MESSAGE A263. |

|   86|  ENDIF. |

|   87|* Optische Archivierung                                                                     |

|   88|* Spaete Erfassung mit Barcode |

|   89|* Redesign of barcode handling -> note 780365 |

|   90|  PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr                                        |

|   91| xmkpf-mjahr                                        |

|   92| barcode.                                           |

|   93| |

|   94|  MOVE-CORRESPONDING xmkpf TO emkpf. |

|   95|  CALL FUNCTION 'MB_MOVEMENTS_REFRESH' |

|   96|    EXCEPTIONS |

|   97|      error_message = 4. |

|   98|  IF NOT sy-subrc IS INITIAL. |

|   99|    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH         "385830                         |

|  100|               sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.                                         |

|  101|*    MESSAGE A261. |

|  102|  ENDIF. |

----------------------------------------------------------------------------------------------------

0 Kudos

Hi Mahesh,

though it is abap run time error...as sap always give error abap run time error as it is triggered through BAPI . please check material configuration of material used in this PO.

Regards

Gaurav

0 Kudos

I WILL CHECK AND REPLY BACK TO U .

THANK U,

MAHESH

0 Kudos

Hi Gaurav,

It is working in quality but problem in production system.

Former Member
0 Kudos

Hii Mahesh

Thats y i said pls check your config in both systems for the same material... specially excise related as RG register is under excise configuration.

0 Kudos

some current client settings must be missing, may be number ranges for Rg1,
compare SNRO and its objects in Production and Quality

SNM