Order release should be in IW32 only.
Is it possible to supress release of maintenance order in IW31.
How can we achieve this. We want release order only in IW32.
Regards,
VM
Dear VM,
You have not come up with complete requirement that why you need this.
As you must be knowing full cycle of Maintenace order.
1-Creation:Just creation of order (Job done by technician)
2-Planning:Release order(by Maintenace Manger)
3-Execution(Goods Movement)
4-Time Completion
5-Technical Completion
6-Settlment
So Actually release for such order is done in IW32 only in practical scenario. The person who is creating ordeer is not authorize to release. If he has authorization then he must be senoor person. I hope you have what i meaan to say.
Using user exit,BADI should be secondary.
Regards,
Kaushal Rai
Similar Messages
-
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,
HariHi,
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 -
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 -
Want to restrict the Purchase order release at lower level...
Dear Friends,
The Problem i am facing is that the release strategy defined in Purchase order is such that it will be released by four authorities,
& When 4th One, The Highest authority releases the order it should not get unreleased by lower level authorities.I want to configure this.
Partially it is completed, as if Tcode me29n is used for cancel release then it is restricted by Going into
SPRO-MM-Purchasing-Purchase Order-Release Procedure for Purchase Order- Define Release Procedure for Purchase Order
& suggesting it there.into Release Indicator
But still it can get unreleased by Tcode me28.
Kindly Suggest,
Gaurav ChopraHi,
This is the standard like release srtetegy will not have the restriction only the release do the release . He can also should de release the document.
this can't control.
SAM -
hello everybody.
marketing person prepares the sales order and he enters some discount in the pricing procedure. the requirement is that a higher level person will first check if the discounting and other terms & conditions have been maintained correctly. then he/she will release the sales order & the system should run the MRP.
is there any release provision available in SAP that will not allow the marketing person to create the sales order but the order will be saved by some other higher authority? The marketing person should not be able to save the sales order even if he/she tries to do.
please give me the solution step by step if it is a long procedure.hi,
In a condition record, you can define upper and lower limits to restrict manual changes in the sales document during pricing.
Procedure
To specify limits:
On the overview screen of the condition record, select the appropriate condition record and then choose Goto ® Details.The details screen for the condition record is displayed. Here you can maintain the Upper limit and Lower limit fields as required.
If, during manual processing, you exceed or drop below a defined limit, the system informs you with an error message.
" is there any release provision available in SAP that will not allow the marketing person to create the sales order but the order will be saved by some other higher authority ". not sure if i understood this perfectly. Anyway, dont give the marketing person access to VA01 t.code.
as an alternative, put a credit limit check for all the orders that it goes to a delivery block. let the sales order be saved. no issue. but put a user exit that unless the credit block is released by VKM3 no schedule line is permitted. And VKM3 release provision you give it only to higher level person.
hope it helps.
Thanks
Sadhu Kishore -
Sales order status to show as Complete only after PGI
Hello
I have one requirement. Now currently in sales order status of the order is showing complete once the item being delivered.
But our requirement is that, the status of the order should be shown complete only when PGI is done not after delivery.
I would like to know if any exit or any other program will help us in finding this solution
Thanks in advance
NaveenDear Naveen,
Sales order status depend on Item Category completion rule, please check on VOV7 for your sales order item category. In standard SAP, below rule can we define with item category:
Not relevant for completion
A
Item is completed with the first reference
B
Item is completed after full quantity has been referenced
C
Item is completed after the target qty is fully referenced
D
Item is referenced via contract release
E
Item is completed after full target value is referenced
Hope it will helpful for you.
Regards,
Shatrughan Singh -
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
NNRHi
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 -
TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
Please provide a solution if a release strategy is maintained for two currencies like USD and SGD for more clarification please Read the below Requirement.
Requirement for Singapore:
u2022 COMPANY Asia (Singapore) wants its own Purchase order release strategy is based on their local currency (SGD)
u2022 Whereas COMPANY is using only USD as currency in Purchase order release strategy.
u2022 Standard SAP works based on Character currency which is defining in Class of Purchase release strategy and converts with Local currency to compare with Character Currency.
Required analysis:
u2022 The value assigned in classification is based on Conversion from SGD to USD, Due to Exchange rate fluctuations the assigned value is differ by large amounts and hence system is either determining the higher release strategy or Lower release strategy
u2022 But during Release Strategy Configuration the Net order Value is assigned as 3600 USD considering the Exchange as 1.388889.
u2022 As per the exchange rate in the purchase order 1.3799 the system is calculation the PO Net order Value but the Strategy is Determined based on the value maintained according to exchange Rate 1.388889
In the Purchase Order the system is
Ex: Total Purchase Order Value is 4765.21 SGD and 3453.30 in USD
For Level 1 the value limit is 5000 SGD if it exceeds 5000 SGD it has to go to his manager (Level 2) Exchange rate on 01.04.2008 is 1.3799.
System Considerations:
Possible Solution:
1. Create a new Class with Characteristic with Currency Value SGD System should determine the class based on the combination of Plant 6000 and Document Category F Purchase Order.
2. By using Enhancement spot with Function Module ME_RELEASE_STRATEGIE/ ME_RELEASE_STRATEGIE_EKKO
Logic:
1. System will determine the class PUR_RELEASE from table T16FG if the system finds Plant as 6000 and Document Category as F Then replace PUR_RELEASE with New class as ZPUR _6000.
2. Maintain Z table for the combination of Plant and Class for future requirement
Edited by: Mohammad Irfan on Jun 8, 2009 10:41 AMHi Mohamed,
You can create separate characteristics far all check points and assign those to class.
Regards,
Prasath -
ESYU: Planner Workbench Release process가 다른 user로부터 planned orders를 release
Purpose
Materials Requirement Planning - Version: 11.5.9 to 12.1
Information in this document applies to any platform.
11.5.9 ~ R12 version:
두 명의 users가 MRP Planner Workbench에서 Release를 위해 records updating을 진행하는 경우, 두 명 중 한명만이 update 후 실제로 release를
submit 했으나 두 명 user의 모든 records가 release 되어 버린다.
User1은 자신의 Planned Orders 만을 release 할 수 있고, User2 또한 자신의 저장된 Planned Orders 만을 release 해야 한다.
STEPS:
1. User 1이 MRP Planned Workbench로 log
2. User 1은 특정 planner code를 위한 current planned order recommendations 을 찾는다.
3. User 2가 MRP Planned Workbench로 log
4. User 2가 특정 planner code를 위한 current planned order recommendations 을 찾는다.
5. User1은 All for Release를 선택
6. User2도 All for Release를 선택
7. User1은 checking process를 끝낸 후 저장
8. User2는 아직 checking process를 끝내지 못해 save를 아지 않은 상태로 남아 있다.
9. User1이 [Release] button을 선택
10. User1이 [Release] button을 선택시 User1과 User2에 의해 저장되거나 check 된 모든 planned order recommendations이 Work in Process와
Puchasing modules로 released 되어 버림
Cause
이 issue의 원인은 현재 MRP planning의 경우 expected functionality 이다.
MRP Workbench Release process는 모든 planner에 의해 check 되거나 저장된 모든 planned orders를 항상 release 한다.
Bug 891669 : Enhancement Request
PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
It is explained that this is current functionality in the following rejected Enhancement Request:
Bug 891669 : PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
Solution
Solution을 적용하기 위해 아래 steps을 실행:
1. 모든 planner에 의해 check 되거나 저장된 모든 planned orders가 [Release] button에 의해 항상 release 되는것은 현재 MRP Workbench
Release process에서는 correct functionality 이다.
2. ASCP Planning의 경우엔 Planner/User에 의해 Release process가 아래 option에 의해 처리 가능하다.
-- profile MSC:Released Only By User
-- Standard MRP에서는 이 option은 사용할 수 없고 고려되지 않는다.
Reference
Note 311053.1 -
SD Sales order release for MTO
Hi All,
I have a scenario regarding the sales order release.
The requirement is that, when i create a SO, it should be blocked automatically and never allow to create other subsequent document, unless its released in the SO.
I have completed doing the release procedure for SO.
Now my requirement is that, in MD04 the SO should'nt show any requirements, unlessSales order is released.
Thanks
Best Regards
PrabbathHI GSL,
Thanks for your reply.
May i know how to make the reason for rejection as a default while creating the SO.Since the User creates the SO and while the document is saved SO will be in blocked, due to status profile.
And only the authorized person can release the SO and deactivate the reason for rejection.
The user cannot choose reason for rejection.
Please let me know if there any solution.
Thanks
Best Regards
Prabbath -
Maintenance order release strategy
Dear All,
How can i design maintenance order release strategy by using authorization control.
Please help with path(Configuration with details process if possible).
ThanksSushant,
Please refer the authorization object: I_VORG_ORD which is having fields: AUFART - Order Type and BETRVORG - Business Transaction.
Using this authorization object you can decide whom to give the authorization to release the order.
You have to create a role in PFCG (please take help of BASIS team for the same) assign transaction IW31/ IW32/ IW38 and you will find this authorizaiton object where you have to assign the order type and allow only the business transaction which user is allowed and remove *.
Value BFRE in field BETRVORG is for release of order which you have to restrict to that user after which the user wont be able to release the order.
Please follow the above steps and do tell if you have any further clarification required.
Hope it helps.
Chin2. -
Hi,
I have the below requirement from my client for make to order,
System should allow to run MRP MD50 only after the sales order is released from authorized person.
Kindly suggest required confg.Hi
First of all sales document dont have released procedure. But you can achieve it by following config.
T-Code BS01
Maintain here your required Status Profile (you can copy PM and changed the Status according to you by double clicking it)
1. Not Released
2. Released
Then go to T-Code VOV8 and double click to your sales order type. In there in Transaction flow section "Status Profile" is there assign your status profile there.
Now with your authorized T-code VA02 system change the document status Released (with must be done by authorized person)
Elese you can give t-code VA02 authority to authorized person (Take the help of Basis Guy)
Now use BAPI or USEREXIT (with the help of PP consultant) and write the logic if sales order status is Released then system will allow to save Sales order planning (MD50)
Hope it will solve your issue
Regards
Shambhu Sarkar -
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 -
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 ChoudhuryHello,
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
DhananjayTELL THE SOLUTION DEAR ..SO ANOTHER WOULD GET HELP IN FUTURE.
REGRDS
MANOJ
Maybe you are looking for
-
Error message when opening iTunes and Mail
I'm running OS X 10.6.8 on a Mac Book. Since the recent 'hack' reports, I subsequently changed my Apple Password. Since then, when I open iTunes I get the error message: "You are signed in with a different Apple ID than previously used with podcsts.
-
Can't export/import in Photoshop CC, stuck on loading sign
I've finished an animation in Photoshop CC, but every time I try to import or export something in Photoshop it gets stuck on the spinning loading sign and I have to quit out of it with Task Manager. If anyone knows how to fix this, please leave a res
-
Dual Case Column names fail in select ORDER BY clause
This one is solved, but I thought someone might be able to explain why it happens. I'm a newbie, since I just downloaded Oracel XE last night, and am trying it out. I set up a trivial table with 4 text columns. As it happened, I used dual case for so
-
I just purchased the GB Creative Zen V. I will be traveling next week with no access to a computer to charge it. I?would like to use a digital uni'versal ac adapter to charge it while I'm away. I understand I can purchase a charger from Creative but
-
Iphoto won't open after laptop powered down (ran out of batteries)
I was transferring some photos from iphoto to facebook when my macbook pro ran out of charge. When I plugged it back on, iphoto would not open. Blank with spinning rainbow disc. I had to force quit several times. How do I back up my pics? Are they lo