on 07-19-2014 8:41 AM
Hi,
MIGO transaction Giving dumpwhen we are trying to check or post more than 9 materials. Its working fine till for 9 materials check or post. but when we are trying more that its giving dump Exception condition "CUST_EXIT_AUSP3" triggered
Below are the dump details.
Error analysis
A RAISE statement in program "SAPLCLFM" has raised exception condition
"CUST_EXIT_AUSP3".
Since the exception was not caught by a program higher up in the call
hierarchy, processing was terminated.
Short text for exception condition:
You can find detailed documentation about the exception condition in
transaction SE37 (Function Library). You can find the name of the
function module called from the display of active calls.
How to correct the error :
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:
"RAISE_EXCEPTION"
"SAPLCLFM" bzw. LCLFMF65
"MERGE_ALLKSSK_ALLAUSP"
or
"SAPLCLFM" CUST_EXIT_AUSP3
or
"SAPLMIGO " "CUST_EXIT_AUSP3"
If you cannot solve the problem yourself, please send the following
information to SAP:
1. This description of the problem (short dump)
To do this, choose System -> List -> Save -> Local File (unconverted)
on the screen you are in now.
2. A suitable 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).
Isn't the portion "How to correct the error :" has given the possible solution ?
As this is standard program, If you can't solve by using SAP note then please raise an OSS note to SAP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's not the name of exit, it's the name of the exception. If you check the subroutine where the exception is thrown, the descrition is:
*----------------------------------------------------------------------*
* FORM MERGE_ALLKSSK_ALLAUSP
*----------------------------------------------------------------------*
* Merge allocation and valuation tables from user exit (L_*)
* with corresponding tables in standard program (G_*).
*----------------------------------------------------------------------*
If this was my system I would put a break-point inside the perform, and debug.
* take over user changes into allkssk, allausp
perform merge_allkssk_allausp
tables allkssk
lt_allkssk
allausp
lt_allausp.
It tried looking at the code for the name of the exit, but it's a dynamic function call, so you can only see the name in runtime.
EDIT: The actual code where the exception is thrown is:
if l_allausp-atcod na '123456789'.
raise cust_exit_ausp3.
endif.
Hi Experts,
Can any body help me , this is urgent please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.