Hi All,
In Retraction we have changed the mapping in UPBR_RULE transaction of Sender structure UPB_SND_COPS. Then later on transported the transfer rules along with sender structure UPB_SND_COPS in the Quality System.
Then we run the retraction in Quality system it is giving the following dump. Whereas the same is running properly in development.
Could you please suggest what else needs to be generated/activated in Quality.
-
Runtime Errors LOAD_PROGRAM_NOT_FOUND
Exception CX_SY_PROGRAM_NOT_FOUND
Date and Time 14.02.2008 11:36:30
Short text
Program "D22LGY3T92WZV9W4WOGFU10PS " not found.
What happened?
There are several possibilities:
Error in the ABAP Application Program
The current ABAP program "SAPLUPBR_TOOLBOX_DATA_MAPPING" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
or
Error in the SAP kernel.
The current ABAP "SAPLUPBR_TOOLBOX_DATA_MAPPING" program had to be terminated
because the
ABAP processor detected an internal system error.
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
caught in
procedure "UPBR_DATA_PACKAGE_MAP" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely "D22LGY3T92WZV9W4WOGFU10PS ".
However, program "D22LGY3T92WZV9W4WOGFU10PS " does not exist in the library.
Possible reasons:
a) Wrong program name specified in an external PERFORM or
SUBMIT or, when defining a new transaction, a new
dialog module or a new function module.
b) Transport error
How to correct the error
Check the last transports to the R/3 System.
Are changes currently being made to the program
"SAPLUPBR_TOOLBOX_DATA_MAPPING"?
Has the correct program been entered in table TSTC for Transaction "ZPSRETRACT
"?
-
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:
"LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"
"SAPLUPBR_TOOLBOX_DATA_MAPPING" or "LUPBR_TOOLBOX_DATA_MAPPINGU02"
"UPBR_DATA_PACKAGE_MAP"
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.
The exception must either be prevented, caught within proedure
"UPBR_DATA_PACKAGE_MAP" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
-
Thanks and Regards,
Saritha