on 07-23-2008 3:45 PM
Hi All,
I have scheduled the archiving job in PI 7.0 through sxmb_adm -> Schedule Archiving.
After scheduling I can see two jobs successfully released
1. ARV_BC_XMB_DEL - This job uses the program "RSXMB_DELETE_ARCHIVED_MESSAGES"
2. ARV_BC_XMB_WRP - This uses the program "RSXMB_ARCHIVE_MESSAGES"
The second job (which is archiving of xml messages) is running good but the First Job "ARV_BC_XMB_DEL" fails with a
"ABAP/4 processor: RAISE_EXCEPTION."
Both the jobs are running fine on DEV & QA systems.
But the first job fails on Pre-Prod & Prd (which are high available systems).
Any hints/help on why its failing with an exception on Pre-PRD & PRD ?
<removed by moderator>
Thanks
Sourav
Edited by: Mike Pokraka on Jul 24, 2008 12:52 PM
Thanks for the reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sourav,
did you check ST22 for detailled information?
Regards Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. This is what it says.
Short text
Exception condition "NO_DDIC_TYPE" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "CL_ABAP_TYPEDESCR=============CP" raised the
exception
condition "NO_DDIC_TYPE".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" " "
"CL_ABAP_TYPEDESCR=============CP" or "CL_ABAP_TYPEDESCR=============CM00C"
"GET_DDIC_HEADER"
or
"CL_ABAP_TYPEDESCR=============CP" "NO_DDIC_TYPE"
or
"RSXMB_DELETE_ARCHIVED_MESSAGES " "NO_DDIC_TYPE"
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.
Note 982407 - Qty object: RAISE_EXCEPTION with "NO_DDIC_TYPE" exception
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=982407
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.