PM order release

Dear all,
I know the concept of maintenance order release thro permit,
But the thing is I want the only component cost to be considered for this and I need 3levels of approval.Even when i change like add components or remove components from order it should take care.I think this is a development, To achive this what is the best possible way? can any one pls guide me.
Thanks and regards
NNR

Hi
If I have understood your problem corectly, then it should be possible to have multiple levels of approval through authorisation. As u know a maintenance order has various system stautses with creation, release, complete, lock and so on.
You can assign suitable role to an user having these objects as their authorisation. You can use the authorisation object I_VORG_ORD ( FOR ORDER) & I_VORG_MEL (FOR NOTIFICATIONS) AND ALLOW THE BUSINESS TRANSATIONS LIKE RELEASE. For release of maintenance order the business transaction is BFRE. An user who does not have this value in his role would not be able to release a maintenance order. Remove the appropriate values from user's roles and you can achieve multiple levels of approval. This a pretty standard feature in SAP. Talk to your basis guy for making the roles.
Reward points if found useful.
Regards
Alok Sengupta

Similar Messages

Purchase Order Release Report

Hi,
Is there a report that I can run that will give me the following information with regards to Purchase Orders released: PO number, Date Entered, Username, Release Code, Release Date and Released By?
Thank-you in advance.
Regards,
Tracy

Hi,
I think there is no such report as you have to develop the report through abap . With the useage of the tables i.e. EKKO,EKPO and few more you can have all this information..

Purchase order release strategy report

Dear Gurus,
We are using purchase order release strategy with classification.
We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
How to get it ?
Please provide ur help for the same
Rgds,
Saurabh

Hi,
Basically in EKKO table there is a field name FRGZU -
Release status based on that we can write a logic take the report.
for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
Just tell him the logic to ABAP person they will develop
Rehgards
Murugan J

Purchase Order released date field and table name

Hi,
Please tell me the Purchase Order released date field and table name.
Regards
Deepak

Hi,
Table : EKKO.
Fields : FRGKE,FRGZU.
You can get release date of PO from CDHDR table.
give object value as your po number and check.dont forget to give leading zeros.
The udate will be date field and transaction will be me29n for relaesed po.

Batch number coming automatically at the time of Process order release

Hi All,
I want the system generated batch number for header material to come automatically at the time of process order release.
At present ,the batch number is entered manualy dering process order creation.
Can anyone pls guide abt the settings required for the same

Dear,
Define the production scheduling profile CORY then
Auto Batch Creation = 2 On release.
Then assign this to your FG or SFG materials in work scheduling view in material msater MM02. Then create new order and check.
Now for automatic generation i have to set internal number asignment for batches.
Batch will create for movement type say 101 SPROLogistics - GeneralBatch mangment--Creation of New Batches --Define Batch Creation for Goods Movements. so it will have same logic in MM for 101 GR against PO will be internal number range but no effect in SD.
Regards,
R.Brahmankar
Edited by: R Brahmankar on Mar 12, 2010 12:40 PM

WMS : How to Process Sales Order Released before Turning on WMS

Hello Gurus,
How to process sales orders released before WMS enable flag is turned on in the new WMS enviournment in Oracle 11.5.10 ?

Helios,
Thanks for the document.
I m looking for how to perform Pick confirm transactions for already printed Pick slips before WMS enabled flag is turn on for the org.
One option is to close all the deliveries but if there is no on hand at that point the they will remain option.
Other option is to Back order those deliveries and re release them post wms enable flag is turned on... The only issue i see here is that if there are more new orders for one of the items and the orders are released then which orders will get allocated/reserved if there is limited on hand quantity to statisfy the SO need.
Let me know if you can think off some alternative solution.
Apprecite help !!
Thanks,
Sam

Problem in Purchase Order Release Workflow

Hello Experts,
I am working in a workflow for releasing PO.In this workflow I have created just one activity step type to release a purchase order.Here I have taken PO(BUS2012) object as input parameter.In the activity step type I am using a custom task(TS99900011).In this task I have used BUS2012 as Business Object and SINGLERELEASE as method.Here I have used 3 terminating events of BUS2012 object.They are Released, Reset and significantly changed. I have just copied the standard task (TS20000166).
Now my activity step has four outcomes.We can see them in Outcomes tab.
1.Purchase Order Released(Cgy:External Events)
2.Not Used(Cgy:External Events)
3.Purchase Order Changed Significantly(Cgy:External Events)
4.Processing obsolete(Cgy:Internal Events).
I have set agent assignment as user Manas.
Now, when I am testing the workflow with a valid PO number as input the work item goes to my inbox for release the PO as expected.There I can release or reject the PO.But while saving after releasing or rejecting the PO the work item still remains in Workspace Inbox.Any of the four outcomes is not appropriate for the activity.
Can anybody suggest any solution to overcome the situation.
Are the external events are really helpful in developing workflow activity?Please suggest.

Hi Manas,
There is one option, where you can stop the workitem and even entire workflow.
Use Fork for parllel processing
Have a Wait step with BUS2105-Significantlychanged event and outcome to the end of workflow.
Thanks,
Sudhir.

Purchase order Release Stratergy-Error in Class CL01

Purchase Order Release Stratergy:
In CL01(create class) i have created the class FRG_EKKO and saved.Then in CL02(change class) under Basic data-Administrative data we found Assignment field tick is not selected and that is not in changeable mode.
Because of that reason Error occured like Error in Class in SPRO release stratergy. Release is taking place in Development Server but not in Production server.
Regards,
Wilson Babu G

Hi
This indicator shows that objects are assigned to this class.
The indicator is set automatically by the system.
once you assign the class to any objects then this flag will come automatically.
Please check if you have assigned the characteristics to the Class in CL02
Please check if you have assigned the release strategy to the Class in CL24N
Thanks & Regards
Kishore

Purchase order release workflow - urgent

Hi friends
When iam creating purchase order it trigger the workflow WS20000075 for releasing purchase order in that purpose what can i do..
How can i set the Agents
How can i trigger the events - i think in that purpose using pftc we trigger the workflow.. so i need clear steps from beginning onwards..
my exact requirement
once i create purchase order, the workflow will be triggered..
after that the mail goes to the approver.. if he/she click that mail purchase order release statement want to be open.. after that he/she release purchase order it will goes to the next level..anyone give the step by step procedure..for that
Thanks
Gowrishankar

yes prabakar.. but iam confused..
You can get step by step workflow for PO using standard workflow
Release of Purchase Order :WS20000075
And for two levels of approvals you have to configure in SPRO the path is
Purchase Order:
SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
If you don't know about this configuration, you have to confirm with your MM consultant.
after finish this iam triggering events using pftc
in that pftc iam choosing business object bus 2012 for po release..
i think thats enuf..
After that it is possible to trigger workflow.. when iam create purchase order..
Thanks
Gowrishankar

Dead Line Monetering in Purchase Order Release Workflow

Hi Experts,
I have activated Standard Purchase Order Release workflow and it works fine now i have a requirement of Dead Line monetering for 2 days. In Standard Release Activity TS20000166 if i give 2 days in Latest End.
Will it work in such a way that if the first approvar does not take any action for 2 day then it automatically esculates to the next person in the release strategy.
Or should i use Modeled Deadline for esculation to next Level.
Regards,
Hari

Hi,
If you just have 2 days on the latest end tab, the workflow will only send a deadline notification to the current agent and WILL NOT escalate.
You have to use modelled deadline and in that branch route the workflow to the next approver based on your agent determination rules.
Satish

No of levels in purchase order release more than 8

Dear All,
We have a situation where some of our purchase orders need to be approved by more than 8 people.Can any one help me in telling-> whether we can create release strategies having more than 8 levels of approvals.If yes how to do it since I could see only max of 8 levels of approvals in the release strategy configuration for purchase order(release strategy with classification).
Regards,
Feroz Choudhury

Hello,
As mentioned by Uttkarsh, It is not possible to go beyond 8 levels in release strategy.
More than 8 levels of approval is not a best practice, if your requirement still demands this explore the options of using Workflow functionalities in ECC or if approval is complex suggest SRM where you can handle n-level approval.
Hope this helps.
Thanks
Ashu

Graphical view in Purchase order release strategy

Hi Experts,
I have added new position in existing Purchase order release strategy which is running properly.
I am facing the problem of visual display in header on tab release stratege for the PO which are already released by respective authority.
It is showing final release balance all though release indicator set to "1".
For e.g.
PO number 123 was released by 4 persons in past.
As per new modification release agencies are 5 nos.
for this PO release flag set to "1"
As 4 persons involved in PO release the graphical display shows 5 agencies for release but release tick infront of these show only 4.
My Problem is client wants correction in this graphical display.
Please help me on this.
Regards
Dhananjay

TELL THE SOLUTION DEAR ..SO ANOTHER WOULD GET HELP IN FUTURE.
REGRDS
MANOJ

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
   case of a purchase requisition and '4' or '6' in case of
   another purchasing document (purchase order, request for
   quotation, contract, scheduling agreement),
- the document is still subject to the previous release
   strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

Purchase order -- release strategy

Dear Friends,
I have a requirement for Purchase order Release.
The problem area is in purchase order ... there will be 2 Relase approvals
01 Mr. Abcd
02 Mr. Xyz
After level 1 approval and before level 2 approval ... i want to do some actions.. these actions are related to another product named savvion .
My question is can i stop the document to be edited by 02 ( Mr.Xyz ) untill i complete my process after 01( Mr.Abcd ) has finished his work.
This is to be done on top priority.
Please help me.
Cheers
Jitesh.

Hi,
Yes, We can stop the document to be edited by 02 until 01 has finished his work.
After 01 approved the document need to be correct, go to PO header menu release strategy TAB and 01 approved to be revoked (means double click on the tick mark, it will revoked).
Hope it is useful for you.
Regards,
K.Rajendran

RUNTIME Error - User Status for Order release

HI Friends,
Pls go thru the run-time error description,which i'm getting on Order release.Pls reply,.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          31.03.2008 13:16:08
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_250
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_250"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
"IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
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.
System environment
SAP-Release 700
Application server... "SILDEV"
Network address...... "192.168.255.70"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "SILDEV"
Database type..... "MSSQL"
Database name..... "DEV"
Database user ID.. "dev"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 3 2008 03:55:37"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 150
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 4889280
MM Free. 3487552
User and Transaction
Client.............. 250
User................ "PM5CHARL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."C0A8FF46013847F096C00004"
Outbound Queue Name.." "
Client.............. 250
User................ "PM5CHARL"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "NONE"
Source Server....... "SILDEV_DEV_00"
Source IP Address... "192.168.255.70"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" -
in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 10
of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
Source Code Extract
Line
SourceCde
1
METHOD if_swf_run_wim_utl_internal~get_system_user .
2
DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4
TRY.
5
IF me->m_int_state-system_user IS INITIAL.
6
me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7
ENDIF.
8
re_user = me->m_int_state-system_user.
9
CATCH cx_swf_run_wim INTO l_excp.
>>>>>
MESSAGE ID     l_excp->t100_msg-msgid
11
TYPE   'X'
12
NUMBER l_excp->t100_msg-msgno
13
WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14
l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15
ENDTRY.
16
17
ENDMETHOD.                    "
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
X
SY-MSGID
SWF_RUN
SY-MSGNO
617
SY-MSGV1
WORKFLOW_LOCAL_250
SY-MSGV2
RFC_READ_DESTINATION_TYPE
SY-MSGV3
DESTINATION_NOT_EXIST
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080331
SY-UZEIT
131608
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
26 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM088    10
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
25 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM00J     5
CL_SWF_UTL_MAIL=>GET_OWNER
24 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM002    37
CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
23 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0IE    38
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
22 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM021     7
CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
21 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM01V    12
CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
20 METHOD       CL_SWF_RUN_WIM_STATE_FLOW=====CP    CL_SWF_RUN_WIM_STATE_FLOW=====CM004     2
CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
19 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM09A    72
CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
18 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0H3    16
CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
17 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM04P     7
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
16 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM011    12
CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
15 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A    81
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
14 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R    93
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
13 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM008   144
CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
12 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM016    42
CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
11 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM002    33
CL_SWF_RUN_WORKFLOW_START=>EXECUTE
10 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU13                           135
SWW_WI_CREATE_VIA_EVENT_INTERN
9 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU11                            64
SWW_WI_CREATE_VIA_EVENT
8 FORM         SAPLSWW_SRV                         LSWW_SRVU11                             1
SWW_WI_CREATE_VIA_EVENT
7 FORM         SAPMSSY1                            SAPMSSY1                              271
XAB_RUN_DRIVER
6 FUNCTION     SAPLSXAB                            LSXABU01                                9
RFC_RUN_XAB_DRIVER
5 FUNCTION     SAPLERFC                            LERFCU01                              115
ARFC_EXECUTE
4 FUNCTION     SAPLERFC                            LERFCU02                              386
ARFC_DEST_SHIP
3 FORM         SAPLERFC                            LERFCU02                                1
ARFC_DEST_SHIP
2 FORM         SAPMSSY1                            SAPMSSY1                               85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.      26 Ty.          METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
RE_USER
222222222222
000000000000
000000000000
000000000000
L_EXCP
B0004000
90006000
SY-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
L_EXCP->T100_MSG-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
SWFCO_WIM_WI_FORWARD
SWW_WI_FORWARD
555554544554542222222222222222
377F79F6F271240000000000000000
000000000000000000000000000000
000000000000000000000000000000
SY-MSGNO
617
333
617
000
000
L_EXCP->T100_MSG+40(6)
617
333
617
000
000
SY-MSGV1
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+48(100)
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+148(100)
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+248(100)
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+348(100)
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No.      25 Ty.          METHOD
Name CL_SWF_UTL_MAIL=>GET_OWNER
RE_OWNER
%_DUMMY$$
2222
0000
0000
0000
ME->M_OWNER
%_VIASELSCR
0
4
ME
A0005000
E0001000
L_WORKITEM
60009000
3000C000
SY-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No.      24 Ty.          METHOD
Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
EX_SENT_TO_ALL
2
0
0
0
EX_MAIL_OBJECT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
A0005000
E0001000
OBJECT_HD_CHANGE-ACNAM
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222222222222222222222222222
377F79F4930C19F6F2FD19C0000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
OBJPARB
Table IT_758[1x570]
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
Table reference: 224
TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000
TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
TABH+ 40(16) = 042A0200600B000010000000C1248401
store        = 0xE06D6DEFF9060000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 224   (0xE0000000)
label        = 758   (0xF6020000)
fill         = 1     (0x01000000)
leng         = 570   (0x3A020000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000046
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x80095FEFF9060000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 540   (0x1C020000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
OBJECT_HD_CHANGE-OBJDES
Workflow 405090 set to status ERROR
56766667233333327672762776777245545222222222222222
7F2B6CF70405090035404F03414530522F2000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_FSREG_001
OBJCONT
Table IT_760[9x510]
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
Table reference: 225
TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000
TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
TABH+ 40(16) = 042A0200300B000010000000C1248401
store        = 0x106F6DEFF9060000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 225   (0xE1000000)
label        = 760   (0xF8020000)
fill         = 9     (0x09000000)
leng         = 510   (0xFE010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000045
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x402D5FEFF9060000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 541   (0x1D020000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
OWNER
222222222222
000000000000
000000000000
000000000000
SENDER
222222222222
000000000000
000000000000
000000000000
SY-SUBRC
0
0000
0000
SWFCO_MAIL_ERROR_NOTIFY
0002
3333
0002
0000
0000
OBJECT_HD_CHANGE
E          ERRORMESSAGEWorkflow 405090 set to status ERROR                00000000000000 F F S
4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_TYPE
RAW
545
217
000
000
SWFCO_OBJTYPE_BOR
BO
44
2F
00
00
No.      23 Ty.          METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
LT_AGENTS
Table IT_752[1x28]
\CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
Table reference: 207
TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000
TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
TABH+ 40(16) = 04180100E006000010000000C1248401
store        = 0x806B6DEFF9060000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 207   (0xCF000000)
label        = 752   (0xF0020000)
fill         = 1     (0x01000000)
leng         = 28    (0x1C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000022
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xA0696DEFF9060000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 537   (0x19020000)
refCount     = 1     (0x01000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 2     (0x02000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
SYST-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
WS20000014
55333333332222
73200000140000
00000000000000
00000000000000
SY-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
FUNCNAME
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222
377F79F4930C19F6F2FD19C0000000
000000000000000000000000000000
000000000000000000000000000000
SWFCO_WI_REMOTE
R
5
2
0
0
PARAMETER-NAME
WI_ID
54544
79F94
00000
00000
SWFCO_CALLBACK_AGENTS
CALLBACKAGENTS
54444444454444552222222222222222
F31CC213BF175E430000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
PARAMETER-VALUE
000000405090
333333333333
000000405090
000000000000
000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
000000405090
333333333333
000000405090
000000000000
000000000000
PARAMETER
807020C0
7080A050
00000000
00100010
LS_MAILOBJ
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
60009000
3000C000
SWFCO_WORKITEM_OBJECT
_WORKITEM
55454454422222222222222222222222
F7F2B945D00000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
No.      22 Ty.          METHOD
Name CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
SWFCO_WORKITEM_OBJECT
_WORKITEM
55454454422222222222222222222222
F7F2B945D00000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No.      21 Ty.          METHOD
Name CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
IM_STATE_ACTIONS
Table IT_279[30x152]
\CLASS=CL_SWF_RUN_WIM_STATE_FLOW\DATA=M_STATE_ACTIONS
Table reference: 112
TABH+ 0(20) = 90CE53EFF9060000B04D6BEFF906000000000000
TABH+ 20(20) = 70000000170100001E0000009800000090010000
TABH+ 40(16) = 049A01007004000010000000C9248001
store        = 0x90CE53EFF9060000
ext1         = 0xB04D6BEFF9060000
shmId        = 0     (0x00000000)
id           = 112   (0x70000000)
label        = 279   (0x17010000)
fill         = 30    (0x1E000000)
leng         = 152   (0x98000000)
loop         = 400   (0x90010000)
xtyp         = TYPE#000009
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xF0C453EFF9060000
pgHook       = 0xF0CE53EFF9060000
idxPtr       = 0x50E253EFF9060000
shmTabhSet   = 0x0000000000000000
id           = 207   (0xCF000000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 48    (0x30000000)
lineAlloc    = 48    (0x30000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x204C6BEFF9060000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
SWFCO_WI_NO_DEADLINE
0000
3333
0000
0000
0000
L_OBJ
A0005000
D0002000
ME
A0005000
D0002000
ME->IF_SWF_RUN_WIM_STATE~NEW_STATUS
ERROR
455452222222
522F20000000
000000000000
000000000000
<%_L003>
ERROR
455452222222
522F20000000
000000000000
000000000000
SY-REPID
CL_SWF_RUN_WIM_STATE==========CP
4455545554554455545433333333334522222222
3CF376F25EF79DF34145DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_L004>
F
4
6
0
0
<STATE_ACTION>
FERROR       01DYN_SEND_ERROR_REPAIR_MAIL
4455452222222334545544454554555454455444422222222222222222222222222222222222
6522F200000000149EF35E4F522F2F250192FD19C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
<%_L002>
<%_L002>-WI_STAT
SYST-REPID
CL_SWF_RUN_WIM_STATE==========CP
4455545554554455545433333333334522222222
3CF376F25EF79DF34145DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SWFCO_WI_STATUS_WILD_CARD
222222222222
A00000000000
000000000000
000000000000
<%_L002>-WI_TYPE
<STATE_ACTION>-METHOD
DYN_SEND_ERROR_REPAIR_MAIL
4545544454554555454455444422222222222222222222222222222222222
49EF35E4F522F2F250192FD19C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
0
0
LV_EXCP
F0000000
F0000000
No.      20 Ty.          METHOD
Name CL_SWF_RUN_WIM_STATE_FLOW=>

Hello,
Get help from your abaper on this.
Vinay

PM order release

Similar Messages

Maybe you are looking for