on 01-03-2015 2:07 PM
Check if the leave requests actually still exist in the system. Check this for example with PTARQ -> Display documents, etc. Also check that the leave request has not been already approved (status = APPROVED).
Just few ideas. I have seen different dumps for leave request approval, if there has been some kind of problem with the actual leave request itself (for example it has been deleted etc.). Normally the work item should disappear from UWL, but it some cases they stay there, but are impossible to process further.
Regards,
Karri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Experts,
Dump got cleared by changing the status entry in PTREQ_HEADER table as Error.
We are able to see the old request workflow status still in sent,we have changed into Error.
Regards
Vinodh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear experts
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_OBJECT_ERROR', was not
caught in
procedure "CREATE_TRANSIENT_OBJECT" "(METHOD)", 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:
The dynamically specified class " " at CREATE OBJECT neither exists as
local, nor as global class in the system, or is overshadowed by a local
data type of the same name.
We cleared all work item and completed the workflow manually.
We are created new leave request and same dump is getting in MSS user.
Regards
Vinodh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From ST22, pls provide us more details like the class that is not found, line number/code at which its crashing etc, may be past your dump screen shot or data.
Also do try as suggested by Sidh.
In case if its class not found and its not due to any data issue, then you can raise the OSS Msg to SAP, they will fix it .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Vinod,
Check following points
1. IT0105 & subtype 0001 is updated there should be user I'd.
2. Check Roles should be assigned properly (ESS roleone user and MSS role should be other user and and in the OM should be relationship should be proper)
3. Check PTARQ leave status , if there status is showing approved then check workflow with ABAPer.
Regard,
Santosh Shivane
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.