topic Re: GETTING RUNTIME ERROR POSITNG GR-MIGO in Application Development and Automation Discussions

GETTING RUNTIME ERROR POSITNG GR-MIGO

Former Member — Fri, 08 Feb 2008 08:59:21 GMT

Dear All,

While Posting GR thru MIGO, we'r getting short fump while posting the transaction after check made.

Pls advise what happened exactly and how to fix this......

We'r getting this error/short dump only from today and wants to know whether its getting affected by any patches implemented by Basis consultant.

FYR

The below description displaying in Runtime error while posting GR-MIGO after check completed OK.

Short Text

Syntax error in program "SAPLFAGL_MIG_OPITEMS ".

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLGLIN" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLFAGL_MIG_OPITEMS " in

include "LFAGL_MIG_OPITEMSTOP " in

line 42:

"The type "FAGL_MIG_BELNR_DOCNR" is unknown."

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "BS1SUDHA "

Error in the ABAP Application Program

The current ABAP program "SAPLGLIN" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program SAPLFAGL_MIG_OPITEMS :

"The type "FAGL_MIG_BELNR_DOCNR" is unknown."

" "

Trigger Location of Runtime Error

Program SAPLGLIN

Include LGLINF90

Row 3,340

Module type (FORM)

Module Name SET_DOCNR

Source Code Extract

Line SourceCde

3310 MOVE BEL_TAB-REFACTIVITY TO BEL_ST-REFACTIV.

3311 MOVE-CORRESPONDING BEL_ST TO TAB_FAGLFLEXA .

3312 IF T881-GLFLEX = '1'.

3313 MOVE BEL_TAB-DOCNR_GLFLEX TO TAB_FAGLFLEXA-DOCNR.

3314 ENDIF.

3315 MODIFY TAB_FAGLFLEXA .

3316 ELSE.

3317 CLEAR BEL_TAB.

3318 LOOP AT BEL_TAB WHERE BUKRS = TAB_FAGLFLEXA_ADD-BUCHKREIS

3319 AND ACTIVITY = TAB_FAGLFLEXA-ACTIV

3320 AND DOCNRVORL = TAB_FAGLFLEXA-DOCNR.

3321 IF T881-GLFLEX = '1'.

3322 IF UF-INTERFACE = GC_AC_INTERFACE.

3323 CHECK BEL_TAB-RLDNR = TAB_FAGLFLEXA-RLDNR.

3324 ENDIF.

3325 CHECK NOT BEL_TAB-DOCNR_GLFLEX IS INITIAL.

3326 ELSE.

3327 CHECK NOT BEL_TAB-DOCNR IS INITIAL.

3328 ENDIF.

3329 MOVE-CORRESPONDING BEL_TAB TO BEL_ST.

3330 MOVE BEL_TAB-REFACTIVITY TO BEL_ST-REFACTIV.

3331 MOVE-CORRESPONDING BEL_ST TO TAB_FAGLFLEXA .

3332 IF T881-GLFLEX = '1'.

3333 MOVE BEL_TAB-DOCNR_GLFLEX TO TAB_FAGLFLEXA-DOCNR.

3334 ENDIF.

3335 MODIFY TAB_FAGLFLEXA .

3336 EXIT.

3337 ENDLOOP.

3338 ENDIF.

3339 IF NOT TAB_FAGLFLEXA_ADD-GLSIP IS INITIAL.

>>>> CALL FUNCTION 'FAGL_MIG_GET_DOCNR'

3341 EXPORTING

3342 iv_rldnr = TAB_FAGLFLEXA-rldnr

3343 iv_bukrs = TAB_FAGLFLEXA-rbukrs

3344 iv_gjahr = TAB_FAGLFLEXA-gjahr

3345 iv_belnr = TAB_FAGLFLEXA-belnr

3346 iv_buzei = TAB_FAGLFLEXA-buzei

3347 IMPORTING

3348 ev_docln = TAB_FAGLFLEXA-docln.

3349 MODIFY TAB_FAGLFLEXA .

3350 ENDIF.

3351 ENDLOOP.

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

Former Member — Fri, 08 Feb 2008 09:14:55 GMT

HI,

https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1086181&nlang=EN&smpsrv=https%3a%2f%2fwebsmp210%2esap-ag%2ede

regards

Nicole

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

Former Member — Fri, 08 Feb 2008 09:22:32 GMT

Hi NIchole,

Pls Post me ur reply clearly once again.

thanks & regards

sankar.

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

Former Member — Fri, 08 Feb 2008 09:25:56 GMT

HI Nichole,

its asking me login id and pw...I don't have authorisation or account in that, pls reply me where can able to do this by our Basis consultant or who exactly????

Pls advise.

regards

sankar.

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

Former Member — Fri, 08 Feb 2008 09:27:03 GMT

Hi,

the link is an OSS-Note. Please read this and take a look, if this note is the right one for you.

[https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1086181&nlang=EN&smpsrv=https%3a%2f%2fwebsmp210%2esap-ag%2ede]

I can send you this oss-note as mail, if you give me your mailadi.

Edited by: Nicole Lorenz on Feb 8, 2008 4:27 AM

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

RaymondGiuseppi — Fri, 08 Feb 2008 10:21:01 GMT

Give the static link to OSS note : [Note 1086181 - Subsequent implementation of document splitting|https://service.sap.com/sap/support/notes/1086181] like [https://service.sap.com/sap/support/notes/1086181|https://service.sap.com/sap/support/notes/1086181]

Regards

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

Former Member — Fri, 08 Feb 2008 10:38:29 GMT

Hi Raymond,

The SAP - 1086181 note not in active mode in our side presently....

So, Whr is the problem...in other areas...

Pls comment

regards

sankar.

Re: GETTING RUNTIME ERROR POSITNG GR-MIGO

RaymondGiuseppi — Fri, 08 Feb 2008 10:51:50 GMT

In your dump a structure/table is referenced but doesn't exist in the system where the dump appeared. This type is FAGL_MIG_BELNR_DOCNR.

"The type "FAGL_MIG_BELNR_DOCNR" is unknown."

The type is used in global data of a program, include LFAGL_MIG_OPITEMSTOP.

The type was created in [Note 1086181 - Subsequent implementation of document splitting|https://service.sap.com/sap/support/notes/1086181]

3. In the ABAP Dictionary (transaction SE11), create the structure FAGL_MIG_BELNR_DOCNR (package FAGL_MIG_CONVERSION):

This note is include in the following corrections

600 - P7DK094573
500 - P6DK115133
602 - EACK028314

It seems that this note was partially implemented or not fully transported.

In DEV system look for version of include LFAGL_MIG_OPITEMSTOP (SE38) and of structure FAGL_MIG_BELNR_DOCNR (SE11) if it exists to find the transport request, and the user who applyed the note or the correction package. (Look also at the attributes of the transport request for a note or package number)

As there are manual taks to perform before using SNOTE, it is possible that some objects were lost in transportation.

Regards