As soon as we run MIGO and MIRO tcode i am getting ABAP DUMP.. !

[former_member622718]

hi all,

when i run migo miro tcode i am getting abap dump directly!!

[former_member1716]

manoj16393,

Go to T-Code ST22 and understand what is the cause of short Dump, Help us with few details on that Dump without which it is very difficult for us to help.

You can also use your ABAPer to support this.

Regards!

[former_member622718]

hi satishkumarbalasubramanian,

in st22 we are getting this --->>

What Happended?

Error in the ABAP application program. The current ABAP program "SAPLMIGO" had to be terminated because it found a statement that could not be executed. In include "LDRVNFA1 ", in line 25 of program "SAPLDRVN ", the following syntax errors have occurred: In PERFORM or CALL FUNCTION "MONITOR_READ_MATK", the actual parameter "LS_OUTTAB-TEXT" is incompatible with the formal parameter "P_MAKTX". Author and last person to change the include are: Author SAP Last changed by "SAP "

What can I do?

The termination occurred in ABAP program or include "SAPLMIGO", in "RESET".

The main program was "SAPLMIGO". In the source code, the termination point is in line 69 of program or include "LMIGOKR1".

[Sandra_Rossi]

In the short dump, it's also explained what to do:

How to correct the error
    If the error occurs in one of your own ABAP programs or an SAP program
    that you have modified, try to correct the error yourself.
    If you cannot solve the problem yourself, please send the following
    information to SAP:


    1. The description of the problem (short dump)
    To do this, choose  System -> List -> Save -> Local File (unconverted)
    on the screen you are in now.


    2. The relevant system log
    To do this, call the system log in transaction SM21. Restrict the time
    interval to ten minutes before the short dump and five minutes after
    it. In the display, choose System -> List -> Save -> Local File
    (unconverted).


    3. If these are programs of your own, or modified SAP programs: The
    source text of the programs
    To do this, please choose
    "Other Utilties -> Upload/Download -> Download".


    4. Details regarding the conditions under which the error occurred or
    which actions and input caused the error.

[VeselinaPeykova]

Community members have no access to your system, which means:

1. The available information is limited to what the OP (in this case - you) provides;

2. Community members cannot perform troubleshooting on behalf of the OP. If the OP has performed troubleshooting, but does not share information about the troubleshooting steps and the outcome - this is essentially the same as not troubleshooting at all;

3. Community members cannot directly fix problems in the system of the OP - the developers, system administrators, functional consultants who have sufficient authorizations and can access the system can do this. In nearly all cases community members can only guide, which is only possible when there is sufficient and well-written explanation of the problem, the troubleshooting steps done so far, the outcome of the troubleshooting and research, version, recently implemented notes, recent upgrades, imported transport requests, etc.

4. If for some reason you cannot share enough information about the problem or if you are not able to troubleshoot it on your own - please reach out to a system administrator or a developer in your company.

[michael_piesche]

Not only check who recently changed the include where the dump occurred, but also The involved variables and called codings, e.g. the DDIC data element(s) and domain(s) of LS_OUTTAB-TEXT as well as the Perform or FM MONITOR_READ_MATK and the DDIC data element(s) and domain(s) of Parameter P_MAKTX.

Ask a developer to do this for you, in case you do not have enough ABAP knowledge.

Only if you can rule out any custom changes, you should open a support ticket with SAP. But also check if any SAP switches or add-ons have been recently activated that might cause this inconsistency. Currently I assume some sort of custom modification has been done.

[former_member1716]

manoj16393,

As it clearly suggests, there is problem with compatibility of the variable P_MAKTX with the FM it is being passed to.

Request you to take help of a local developer and take forward, reach out to the code line where it dumps and check if there are any customization done recently.

As rightly suggested by veselina.peykova it is very difficult for us to resolve with the information provided. You can reach to us in case if there is any progress and you feel our suggestion would help.

Regards!

[former_member622718]

hi veselina.peykova, satishkumarbalasubramanian..

Short Text Syntax error in program "SAPLDRVN ".

What happened?

Error in the ABAP application program.

The current ABAP program "SAPLMIGO" had to be terminated because it found a statement that could not be executed.

In include "LDRVNFA1 ", in line 25 of program "SAPLDRVN ", he following syntax errors have occurred: In PERFORM or CALL FUNCTION "MONITOR_READ_MATK", the actual parameter "LS_OUTTAB-TEXT" is incompatible with the formal parameter "P_MAKTX".

Author and last person to change the include are: Author SAP Last changed by "SAP "

[former_member622718]

hi veselina.peykova, satishkumarbalasubramanian..

these are SAP standard TCODES, internal members of out team and our services providers has not chanegd anything in these tcode source program when we have asked..

when saw in st22 its showing last changed by SAP..

Thanks Advanced