USer status in order

Hi,
In the order CO02 :
My customer need when selecting the user status Z0001 and save, the system re-edit automaticaly the production order and also the order confirmation from the customer order attached to my production order.
How can we do this?
Thanks for your help.

Hi
I think using user status only this will not possible, you need to check the enhancements. Becuse production order user status only control the function of the production order.
Thanks
S.Murali

Similar Messages

User status for order confirmation

Dear Expert
My requirement is when system status for maintenance order is CNF and authorize person agreed with all data in confirmation, he will set user status and then only I can complete my order (Teco).
Till now I created one user status OCAP (operation conf aprroved. ) and I allowded TECO only at this status. when system will have any other user status TECO is forrbiden. and it is working fine.
but now if my order is not CNF and person approves order(select OCAP) system allow to do TECO.
How I can stop this?
I mean if order status is not CNF even person select any user status system should not allow for TECO. If both condition are correct then only system will allow for TECo.
Please suggest
Regards,
Prasad

solved.
it is only works for operation
and not order header

Assigning user status to order type

Hi All,
There is an query. Can I assign 2 user statuses to an order type?
regards,
Mohit Goyal

Hi Mohit,
A user status is activated by the user and can be created as an addition to the existing system status. You can define and
activate any number of user statuses. To define a user status, you need to have created a status profile, which is created per order type in Customizing
Hope clear to you.
Regards,
R.Brahmankar

No default USER STATUS in order with radio buttons

Hi friends,
We want to have 4 user status in PM order with radio buttons so that
user can choose only one at a time.But by default after creating order
No user status should be defaulted.Only it should display when user
selects one.
I have tried in SPRO but for radio buttons it selects one as default
automatically.
Is there any alternative.
With Regards
AMehra

Hi Pete,
I know this is standard only.But client's requirement is like this.
All the four status are like that we can choose only one
like PASS FAIL.
Now these two can not be set together.
thnx
Edited by: aachal on Jan 31, 2011 9:29 AM
Edited by: aachal on Jan 31, 2011 9:30 AM

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

Item User Status - Sales Order

1- The cancellation item is created with reference to an existing line item on Sales Order. How is done?
2- I would like to see the original item have its status for both delivery and billing changed to completed and have its overall status completed as long as a PO is created. I don't know how to do that...
Can you help???
Thankss

Hi Miquel,
For that T.code we have user exits and badi. I am providing all the userexits and badi plz gothrough that.
Transaction Code - VA02                     Change Sales Order
Enhancement/ Business Add-in            Description
Enhancement
V60F0001                                SD Billing plan (customer enhancement) dif
V46H0001                                SD Customer functions for resource-related
V45W0001                                SD Service Management: Forward Contract Da
V45S0004                                Effectivity type in sales order
V45S0003                                MRP-relevance for incomplete configuration
V45S0001                                Update sales document from configuration
V45P0001                                SD customer function for cross-company cod
V45L0001                                SD component supplier processing (customer
V45E0002                                Data transfer in procurement elements (PRr
V45E0001                                Update the purchase order from the sales o
V45A0004                                Copy packing proposal
V45A0003                                Collector for customer function modulpool
V45A0002                                Predefine sold-to party in sales document
V45A0001                                Determine alternative materials for produc
SDTRM001                                Reschedule schedule lines without a new AT
Business Add-in
BADI_SD_SCH_GETWAGFZ                    Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001                        SD Customer functions for resource-related
No.of Exits:         15
No.of BADis:          2
Which one is suitable plz check it out and put breakpoint after providing the logic .
Rewrds some points.
Rgds,
P.Nag

Activation of User status for Prod. order

Hi,
I have created a status profile with a status as a user status for production order. Now the thing is how to activate this user status for a specific transaction.
the requirement is after settlement the user status should get activated for production order.
Regards
Amit Parkhi

Hi Amit,
As told by Ajay , after assigning Status Profile in OPJH you can assign User Status to production order as below:
Pls. go through the following procedure for activating the User Status :
Activating User Statuses
Use
You can activate a user status at order header and at operation level.
Procedure
Order Header Level
Go to the order header.
Choose .
Choose Edit ® Direct entry.
The system displays a dialog box in which you can select the permitted user statuses.
Position the cursor on the required user status and choose Choose .
Operation Level
Go to the operation overview.
Select the operation in question.
Choose .
Choose Edit ® Direct entry.
The system displays a dialog box in which you can select the permitted user statuses.
Position the cursor on the required user status and choose Choose .
Pls. follow the above procedure as per rquirement and set user status accodingly.
Pls. revert if any doubt and reward if useful.
Regards,
Tejas
Edited by: Tejas Pujara on Jun 23, 2008 8:10 AM
Edited by: Tejas Pujara on Jun 23, 2008 8:11 AM

PM order user status authorization

Hi Experts,
How can i give authorization to user status of PM Order ?
I want to give authorization for different activites as below.
for example i only want authorization for 01 and 04. Is this possible?
01 ACLD
02 BASL
03 MABE
04 ISBE
05 MIBE
thanks.

Hi,
In addition to Narasimhan & Wendy told, follow these steps
Activities
1. create authorization keys in BS52
2. Create User Statuses & assign to Maintenance Order Object types in OIBS
3. Assign the authorization key to one or more user statuses in your status profile.
4. Assign these User Statuses to Order Types in OIOG
5. Define corresponding authorizations and include them in the relevant authorization profiles.
6. Assign these Authorisation Profiles to the User groups in SU01 under Profiles sub screen.
Regards,
Maheswaran.

Use of user status and business actions

Hi all,
I'm new at status profiles, user status and business actions.
Currently we are using status profiles and user status for orders - but business actions aren't assigned to the user status. In a project I should evaluate whether we can use those business actions.
After reading a lot of documentations there is still one question left. What are the business-actions for and how can I use them?
Let's say I've a status profile with following user status with according business actions:
- status: new;   business action: to progress
- status: in progress;   business action: to confirm
- status: confirmed;   business action: decline or close
- status: closed;   business action: close
What happens when a user sets the status of an order to "confirmed"? Will be done additional checks for my order? - If yes: Wich checks will be done and exists there an API to effect these checks or to implement additional checks?
Regards,
Christian

Christian;
If you´re wanting to speak about Status Profile in OP. You can execute whole theses steps in T-code BS02, when in this IMG:
1. Enter a Status Profile.
2. Assign the status profile to an Object Type.
3. Define the User Status.
4. Assign Business Transactions to user statuses.
5. Translate the status profile and user statuses.
You can also to use this function to simulate the status development for a particular object.
To do this, select a status profile and branch to the screen "Allowed Object Types". Then place the cursor on one of the object types.
Using the function Extras -> Status simulation, you can simulate the status changes that could be caused by performing various business transactions, or by changing the staus manually, during the lifetime of the object concerned.
You can also branch directly from simulation to status maintenance for the object concerned, to display information on which transactions are allowed or disallowed in the current situation.
The log function records all the changes you simulate and allows you to navigate freely to see what effects these are having.
Status profile info
Using the function Extras -> Status profile info, you can display a list of all the entries you have made for a particular status profile. The list is structured as follows:
The first block contains the permitted object types.
The second block contains the user statuses.
The third block contains the following information for each user status:
which transactions it allows
which transactions it allows with a warning
which transactions it disallows.
I hope help to you
Regards
Luciano Nobrega

Item user status at plant level

Hi All
I have configured certain User Status which are assigned to Item category. Item category is used in all the plants but user status is applicable for only few plants. So User status will also appear in those plants where it is not applicable.
In Cost object Sales orders I have the option of selecting the User status manually in Status tab by clicking in 'Object Status' button. But in the items which are not cost object 'Object Status' button does not appear. So I have to assign to Item category in Customizing which will then always be defaulted even though it is not required in ceratin plants.
Regards,

Hi,
I dont think it is possible .
A suggestion not sure if it works .
Assign user status profile operation wise and then have some development to check the operation status and
then update production order status with same user status you mentioned in operation.
FM: STATUS_CHANGE_EXTERN will help you to change the user status of order.
Regards,
Vishal

User status at operation level

Hi,
I have created one user status profile and attached in order type. In this profile I have included Operation and Order header as an "Allowed object type"
My problem is when I am changing user status at order level , it is not getting changed automatically at operation level.
Pls suggest me the solution.
Thanks

Hi,
I dont think it is possible .
A suggestion not sure if it works .
Assign user status profile operation wise and then have some development to check the operation status and
then update production order status with same user status you mentioned in operation.
FM: STATUS_CHANGE_EXTERN will help you to change the user status of order.
Regards,
Vishal

Any Pointers to set user status in iw31 and iw32

Hi all,
I am working on an enhancement where I need to set the user status for an order every time a new order is created(iw31) or an existing order is changed(iw32) and a material in that is flagged as a retirement unit material.
Is there any function module to do that?

Hello Anu
I would like to point to the BAPI documentation where a useful BAdI (<b>IBAPI_ALM_ORD_MODIFY</b>) is mentioned:
FU BAPI_ALM_ORDER_MAINTAIN
Short Text
     Process Maintenance-/Service Order
Functionality
     This Business Application Programming Interface (BAPI) is used for
     changing maintenance- or service orders and their lower-level objects.
     The following objects of an order can be processed (for restrictions,
     see the note at the end of the documentation):
     o   Order header
     o   Partner
     o   User status
     o   Order operations
     o   Relationships
     o   Components
     o   Long texts for order header, operations, and components
   Function
     Calling up this BAPI once allows you to perform all the operations. For
     this the system supplies the function module with a method table
     containing the methods to be performed. The entries in the method table
     refer to data records in the optionally filled-out data tables. All the
     methods from the method table are performed. Alternatively, just lower-
     level objects from existing orders can be changed.
     You can process the transferred data with the Business Add-In (BAdI)
     IBAPI_ALM_ORD_MODIFY to, for example, merge data from the external
     system with data from the R/3 system. The BAdI is called up as soon as
     the transferred data is converted into the internal format. The tests
     then take place after this.
   Construction of Method Table
     o   REFNUMBER   Reference number for linking object methods - attributes
         The reference number is the line of the database which contains the
         corresponding data. The data table is determined by the object type.
     o   OBJECTTYPE Object category
         The object category specifies which object from the order should be
         processed. The key words listed here are not language-dependent and
         must be transferred exactly as they are. The following objects
         exist:
         -   HEADER      Order header
         -   PARTNER     Partner data
         -   USERSTATUS User status
         -   OPERATION   Operation data
         -   RELATION        Relationships
         -   COMPONENT   Components
         -   TEXT            Long texts
         -   (empty)     ,General BAPI functions (save)
     o   METHOD      Methods
         The methods with which the data should be processed. The following
         functions exist:
         -   CREATE          Create objects
         -   CHANGE          Change objects
         -   DELETE          Delete objects
         -   RELEASE         Release
         -   TECHNICALCOMPLETE   Technically complete
         -   ATPCHECK            Availability check
         -   CALCULATE       Calculate
         -   SCHEDULE            Schedule
         -   DELELTEDSEX     Delete the status for external scheduling at
             operation level
         -   SAVE                Save all data
         -   DIALOG          Call-up dialog. See explanation below.
         -   TRACE       Write trace file in the specified file to the
             frontend
     o   OBJECTKEY       SAP external object key
         This key is for assigning the lower-level objects correctly to the
         corresponding objects, as there is always just one key in the data
         table. The key must have the following structure:
         -   1-12        Order number
             When creating orders with internal number assignment, a
             reference number beginning with % must be entered here. The
             BAPI then returns this number and the number actually assigned.
         -   13-16       Operation number
         -   17-20       Sub-operation number
         For relationships, the key is structured as follows:
         -   1-12    ,Order number from
         -   13-16   Operation number from
         -   17-28   Order number to
         -   29-32   Operation number to
     The following methods are permissible for the individual objects:
     o   HEADER:
         CREATE, CHANGE, RELEASE, TECHNICALCOMPLETE, ATPCHECK, CALCUALTE,
         SCHEDULE
     o   OPERATION
         CREATE, CHANGE, DELETE, DELETEDSEX
     o   PARTNER, RELATION, COMPONENT, USERSTATUS, TEXT:
         CREATE, CHANGE, DELETE
     o   (empty):
         SAVE, DIALOG, TRACE
   Data tables and update tables
     The objects have one or more data tables. For some objects you can
     specify which of the fields specified in the structure should be
     changed. For this you must set the field in the corresponding table to X
     as in the data table. If no update-table is transferred, then only
     those fields are set that have a value that is not initial. This
     simplifies the transfer data. However, this means it is not possible to
     delete fields. If an update structure should only be specified for some
     data records, the table with the update fields must nonetheless have the
     same amount of lines as the data table. The empty lines are then
     treated as if no update structure was transferred. The objects
     "Partner", "User Status", and "Text" have no update tables. The whole
     data record is always copied here.
   References
     The objects use the field REFNUMBER from the method table to refer to
     the lines in the data table. Counting always begins with 1. In doing
     this, REFNUMBER also refers to the update table. However, in the method
     table there is a second reference to higher-level objects for
     lower-levels objects. The field OBJECTKEY must be filled with order
     number, operation number, and sub-operation number, as specified above.
     If lower-level objects of a newly-created order should be changed, then
     you must enter a temporary order number that must begin with %. Several
     orders can be numbered serially, for example, with %00000000001,
     %00000000002 ... .
     The following objects have special treatment for REFNUMBER:
     o   Partner
     o   Texts
     Partners have an order number in the data table. During processing of
     the method table, all those entries in the data table are processed
     which have an order number that is the same as that in the line to which
     the method refers. Thus, through just one entry in the method table,
     several partners can be changed.
     Texts are composed of two tables. The first table (IT_TEXT) is made up
     of the header data of the text. Here you must specify the object and the
     first and last line of the text table (respectively inclusive, counting
     from 1). Through this, a line segment is specified in the text line
     table (IT_TEXT_LINES).
   Peculiarities in processing
     The BAPI processes the transferred methods in a particular sequence,
     which must not correspond to the sequence in the methods table.
     o   Write trace file
     o   Change user status time period 1
     o   Delete objects (dependent first)
     o   Create new objects
     o   Change existing or newly-created objects
     o   Change user status time period 2
     o   Status change of order
     o   Save data
     The methods are performed such that lower-level objects can also be
     assigned to newly-created objects. For example, first the operations are
     created, and then the components. Long texts can also be created for the
     objects.
     Components have an exceptional position. Components are created through
     the assignment to an operation, that is, using the "key" order/
     operation (item number). However, as this is not the unique component
     key, you can only access the components to change them, delete them, or
     add long texts by using the reservation number/-item, which is only
     given after saving. This means that, for example, you cannot create a
     long text when you create the component.
     User status changes can take place at two different time points. Time
     point 1 is before the object changes, time point 2 is after the object
     changes and before the status change of the system. These time points
     should be defined in the transfer table in the field CHANGE_EVENT. The
     field documentation contains the possible values.
     The external scheduling is offered by the BAPI as a special function.
     THe BAPI can set the date field directly at the operation level, and
     select the operation with the status DSEX "Date set by external system".
     This status prevents any further scheduling of the operation, it keeps
     the transferred dates. For this, set the category 'X' in the restriction
     categories. When reading the operation, this category is also returned,
     independent of the category of restriction set in the dialog. To delete
     the status, you can call up the method DELETEDSEX for the object
     operation. The external scheduling cannot be influenced in the dialog.
     All changes to the scheduling restrictions in the dialog are saved as
     normal, but are not relevant for the scheduling as long as the status
     DSEX is active.
     Every time the BAPI is called up, a SAVE or DIALOG method must be
     transferred. Normally, calling up a BAPI is seen as a transaction. All
     data that is changed in the BAPI should be saved to the database
     immediately. The BAPI checks whether a SAVE method exists, otherwise it
     terminates processing. A test run of the BAPI is composed of a normal
     call-up using the SAVE method and a subsequent
     BAPI_TRANSACTION_ROLLBACK. To call up the BAPI without the SAVE method,
     for example, to realize dialog transactions, the BAPI can be called up
     with the DIALOG method. This switches off the check for the SAVE method.
     The processor must then ensure that later either a SAVE method or a
     BAPI_TRANSACTION_ROLLBACK is called up.
     A BAPI_TRANSACTION_COMMIT without SAVE method terminates processing in
     the update to ensure that no inconsistent data is written to the
     database. The processor who called up the BAPI does not receive any
     confirmation for the termination of the update in the target system.
     This logic is necessary as the order data was flagged for updating with
     BAPI_TRANSACTION_COMMIT through the SAVE method. However, the status
     information was already flagged for updating when the BAPI was called
     up. A BAPI_TRANSACTION_COMMIT without SAVE method then just saves the
     status information and would generate inconsistent orders, if the
     updating was not terminated.
   Customer Enhancement
     The BAdI IBAPI_ALM_ORD_MODIFY can be used to change the transferred
     data. The BAdI is called up after the conversion of the transfer
     structure into the structures used internally. Additional data can be
     transferred using the table EXTENSION_IN. Only then is the data checked.
Example
     The following examples should clarify the use.
   Creating an order
     OBJECTKEY should be filled with a temporary key. The BAPI returns this
     key together with the assigned order number in the return table
     ET_NUMBERS . The order number in the HEADER table should also be filled
     with the number. For external number assignment, the external number
     should be specified. The update structure can be transferred if
     necessary.
     Methods table
     REFNUMBER   OBJECTTYPE METHOD      OBJECTKEY
     1           HEADER      CREATE      %00000000001
     IT_HEADER
     ORDERID     ORDER_TYPE PLANPLANT   ...
     %00000000001    PM01    1000        ...
   Creating an order with operation and long text
     Methods table
     REFNUMBER   OBJECTTYPE METHOD      OBJECTKEY
     1           HEADER      CREATE      %00000000001
     1           OPERATION   CREATE      %00000000001
     1           TEXT        CREATE      %000000000010010
     IT_HEADER
     ORDERID     ORDER_TYPE PLANPLANT   ...
     %00000000001    PM01    1000        ...
     IT_OPERATION
     ACTIVITY    SUB_ACTIVITY    CONTROL_KEY WRK_CNTR    ...
     10                      PM01        MECHANIC    ...
     IT_TEXT
     ACTIVITY    ...         TEXTSTART   TEXTEND
     10          ...         1           2
     IT_TEXT_LINES
     TDFORMAT    TDLINE
      *          Longtext for operation 10, line 1
      *          Line 2 of the long text
Notes
   Using the BAPI to process the order data cannot support all the functions
   of the transaction. This applies in particular for the following
   functions:
     Order header data
     o   The object list cannot be processed.
     o   Refurbishment orders are not supported.
     o   The estimated costs cannot be processed - only the estimated overall
         costs of the order.
     o   Notification data cannot be processed with the order BAPI. Even if
         the settings in Customizing are such that the orders and
         notifications can be maintained on one screen, no notification is
         created for the order.
     o   Permits cannot be processed.
     o   The order addresses cannot be processed.
     o   Individual partner addresses cannot be maintained.
     o   The settlement rule cannot be maintained.
     Order functions
     o   Printing the papers is not possible.
     o   Locking and unlocking the order is not possible.
     o   Accepting and rejecting quotations is not possible.
     o   Business completion is not possible.
     o   Flagging for deletion is not possible.
     o   The log cannot be displayed.
     o   User default values are not used.
     o   The field selection is not checked.
     o   The Customer Exits/BAdIs are not executed completely.
     o   Joint ventures are not supported.
     o   Funds Management is not supported.
     o   Investment orders are not supported.
     o   No integration of service products with task lists possible.
     o   No integration of configurable service products possible.
     o   Assignment of sales document items with service products in
         accordance with the aforementioned conditions.
     Operation data
     o   A change of the control key in the operation is not possible, if
         this leads to a change of the processing type (internal-/external
         processing)
     o   User status change not possible.
     o   Production resources and tools cannot be processed.
     o   Service lines cannot be processed.
     o   Task list integration is not supported.
     o   Linking operations with object list is not supported.
     Component data
     o   User status change not possible.
     o   BOM data cannot be processed.
     o   The delivery address cannot be processed.
Further information
     See also the documentation for the individual transfer tables.
Parameters
     IT_METHODS
     IT_HEADER
     IT_HEADER_UP
     IT_HEADER_SRV
     IT_HEADER_SRV_UP
     IT_USERSTATUS
     IT_PARTNER
     IT_PARTNER_UP
     IT_OPERATION
     IT_OPERATION_UP
     IT_RELATION
     IT_RELATION_UP
     IT_COMPONENT
     IT_COMPONENT_UP
     IT_TEXT
     IT_TEXT_LINES
     EXTENSION_IN
     RETURN
     ET_NUMBERS
Exceptions
Function Group
     IBAPI_ALM_ORDER
Regards
Uwe

To update user status of an operation in Plant maintenance

Hi
I ma trying to update the user status of an operation of an order using function module status_update but it is not working properly. Although the same function module is working fine for updation of user status of order. Can somebody please tell me some other function module to update the user status of operations?
Thanx in Advance.
Richa.

Hi Richa,
I have the same requirement like which you had. updating the operation user status in work order.
How did you attend this requirement. Please let me know your solution.
Thanks in advance.

Activate a user status when confirm with Reason for Variance

Dear SAPper,
I have a requirement to set a user status block order for good movement and confirmation
when user confirm the order with reason for variance Z999 (machine broke down)
In the order header, I have attach status profile ZBLOCK contain 2 user status
a. UNR = Unrest ---> initial user status
b. LCK = lock for good movement and confirmation
In the reason for variance Z999 (machine broke) i have attach to status profile ZBLOCK user status LCK
But when i tried confirm worh reason for variance Z999, why the order not updated to LCK for its status?
Did i miss something?
Kindly help?
Best regards,
Freddy Ha
Edited by: Freddy Halim on Dec 4, 2008 8:49 AM

solved.
it is only works for operation
and not order header

User Status replication to ECC

Dear Frnds ,
   I am Facing a Problem in updating the User status from ECC to CRM and CRM to ECC ( Delta Load) . When we are creating the order in CRM, this order is replicated to ECC and initial user status has updated in ECC.
   When ever user status is updated in ECC or CRM, the changes are not updated.
Where as when we checked the bdocs, this status is appearing in BDOC, where as same is not updated in Order.
   Kindly let us know, is there any specific settings or developmenets need to be done to replicate the user status in order from ECC <-> CRM.
   Thanks all for your help.
Regards,
Pola

Hi,
User status dont get replicated automatically.
You'll need to implement a BADI CRM_DATAEXCHG_BADI and method CRM_DATAEXCH_R3D_MBDOC_FILL for R3 to CRM.
For CRM to R3 CRM_DATAEXCH_AFTER_MBDOC_FILL.
Kindly reward with points in case helpful
Sharif

USer status in order

Similar Messages

Maybe you are looking for