ATP for Order Create vs Order Release

In SAP there is an option for different ATP checks when creating a production order and when releasing a production order.  I'm not sure I understand the behavior we are seeing in our system.  Could be I have a fundamental misunderstanding of the functionality.
In our configuration, ATP for production order create takes into consideration open purchase orders.  ATP for order release does not.  When I go into CO06/CO09 using the checking rule for order create, I see the commitments which include the open purchase order quantities.  When I go in using the checking rule for order release, my expectation is that the commitments for the purchase order quantities will not be there.  Nonetheless, those commitments appear.  I'm receiving missing parts when I'm trying to release a production order even though there is sufficient material not committed to released production orders.
I hope that makes sense.  Any guidance would be appreciated.

Yes.  We have a different checking rule in OPJK for production order create (YO) and one for production order release (YP).  YO includes purchase orders as a supply element in the check and YP does not.  Other than that, they are identical.
I am saying that when looking at CO09 with YP, I saw commitments based on purchase orders.
Purchase orders are a supply element.
MD04 - 18,606 on hand.  Order reservations for 1,512, 9,329, and 709 are for released orders.  The order reservations for 18,657 and 23,322 are for created orders.
CO09 - Checking Rule YO.  Because of purchase order for 45,000, all quantities are confirmed.
CO09 - Checking rule YP.  All quantities still confirmed. 

Similar Messages

  • 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

  • Order release approval

    Dear
    Just have the idea about below one. We need the maintenance order approval based on plan cost.
    For this we created Class type 032. The created class is assigned there. In class we referred the PMCO table and value is above one dollar.
    Now the thing is how to make this effect in order level. Even i cant assign to the equipments,functional location. Also there is no standard t Code is available for order release like PR.
    Thenna

    hi all,
    find the solution for planned cost,maintenance acitivity types,etc
    1.create ct04characteristicand maintain values 10k,20kof some range if your going to call permits on planning cost here in additional tab mention the structure CSEVPERMIT & any field names
    ILART-Maintenance activity type
    PKOSTEN for planning cost
    USER4 for estimated cost
    IKOSTEN for actual cost.
    2.Create permit class and put the charc in permit class and for class type 049 maintain classification status in IMG.[Cross application components--> classification system->classes---->maintain object types and object keys(here plz read the note and maintain status for class type 049).
    3.Create permits using IPMD and put category , order status and goto classification and maintain permit class and select particular charc value for that permit.
    By the above process respective permits assume that you have given based on planned cost of the orderget automatically assigned to the order,now you can maintain authorisation for the permit for issuing
    Hope this might have met you requirement.
    Plz try the same and let me know if you have any querries or no .If working give up points'''
    regards
    pushpa

  • Production order release Material Availability check

    Gurus,
    I have a production problem where the order can be released when the component for the order is in a restricted status.  This is not allowed by the batch search strategy.
    <u>Here's Problem Description:</u>
    When running on version 4.6C, I have a work order created. I release the work order successfully.  However there is a component that has an invalid material/batch according to the batch search strategy  The material availability check shows all components available. 
    However, I remove the batch and the batch can not be entered because it is not correct according to the batch search strategy.  I try and release and the material is added to the missing parts list.
    I change the component so that it can be used.  
    Put the batch number back in the order. 
    Save the order.  
    Change the component material/batch so that it is no longer valid.  
    The order will release and it shouldn't because the material/batch is not valid.
    <u>I've looked at the following transactions and master data:</u>
    OPL8 - Order Type - Dependent Parameters Overview for my plant and order type and the check batch box is checked.
    MM03 - Material Master MRP 2 view for the component to get the availability check
    OVZ2 - Availability check control
    OPJK - Order Control to get the checking rule for order release
    OPJJ - Availability check control details with availability check and the checking rule for order release - I did not see anything here that would influence the checking based on if the batch was entered or not.
    I did double check the batch search strategy for production order - COB3. Everything looks OK there.
    Does anyone have any other places to check? I must be missing something. I tried OSS - there weren't any notes that I could find.
    Thank you!
    Michelle

    Hi,
    Check in order control opjk for order type pp01
    Batch assignment /release material
    Release despite missing batches
    no release if batches are missing
    Regards,
    nandha

  • Availability of components at order release

    Hi pp guys,
    Can anybody tell me what setting is required so that user can come to know that all components are available in the prodn.order otherwise cancel the release of order
    Thanks in advance

    Hi,
    Use tcode OPJK,
    select your plant, order type and business process 2 (for order release).
    1.Remove tick mark in No availability check.
    2.Checking rule - Input your rule (std PP)
    3. Type of comp check - ATP check.
    4.Material release - 3- No release if parts are missing.
    With these setting, if missing parts found when releasing the order,system pop up the message & release rejected.
    Regards,
    Dharma

  • Function Modules for Order Settlement

    Hi,
    I need simulate the transaction KO88 for Order Settlement with a function module but without batch input. Please, somebody can tell me which function module I can use and give me a example?
    Also, I need another function module for order release...
    Thanks in advance,
    Regards,
    Irina

    Here`s the way to find out how its using ...
    GO to TR.SE93-> give "KO88" 0>  click display
    Double click program name and find "call fucntion" when list come up "serach "Settlement" . You`ll get idea.
    Hope this’ll give you idea!!
    <b>Pl... award the points.</b>
    Good luck
    Thanks
    Saquib Khan
    "Some are wise and some are otherwise"

  • Mandetory Order field and Order Release

    Dear Experts,
    We have made mandetory Problem(Damage) field [Table;VIQMFE, Field: FEGRP] in maintenance order.
    However system allows to Release the order even without no data available in the mandetory field.
    How could I prevent release the order ?
    Thannks in Advance.

    Use IWO10002 PM maintenance order: Customer check for order release and put abap code for checking the required field of  maintenance notification when releasing work order.
    Standard functionality doesn't check the mandatory fields of notifications when you are releasing work order unless the particular field is integrated part of both, notification and work order.
    Regards,
    Tehsin

  • Release strategy for PREQs created from PM work order

    Hi All,
    I have an issue with determining  release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
    We have activated release strategy for Purchase requisition based on the following characteristics:
    CEBAN_PLANT
    CEBAN_COST_CENTER_GROUP
    CEBAN_MANUAL
    Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding  cost center goups.
    In the user exit we have consider to cases:
    The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
    The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
    The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
    We have defined  for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
    Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
    Best Regards,
    Desislava

    Hi,
    For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
    Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
    Regards,
    Raj

  • Creating  workflow for purchase order release.

    Hi friends
    I want step by step detail about creation of workflow for purchase order release..
    After release purchase order it will goes to the two level of approval..
    after that the workflow should be completed...
    how can i develope the workflow for that scenario..
    Thanks
    Gowrishankar

    Hi Gowrishankar,
    You can get step by step workflow for PO using standard workflow
    <b>Release of Purchase Order :WS20000075</b>
    And for two levels of approvals you have to configure in SPRO the path is
    Purchase Order:
    SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
    If you don't know about this configuration, you have to confirm with your MM consultant.
    Thanks and Regards,
    Prabhakar Dharmala

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • IW31-Create Purchase Requisition automatically from PM order - Release 5.0

    Dear Experts,
    Currently we are working in the 4.6C Release but we are doing the migration for 5.0. In PM, in the 4.6C release when we
    create a PM Order in tcode IW31 we select a component and the system shows us the screen to inform the quantity and
    automatically the system shows us a  screen to Create Purchase Requisition where we can fill or select some fields.
    However, when we create a PM order in the  5.0 using the same tcode, the same material type, the system creates
    automatically the Purchase Requisition without to show us the screen to fill or select the fieds. I´ve checked the customizing
    comparing the systems but I couldn´t find something.
    I was wondering If you could help me with this issue?
    If my comments are not enough to understand me, please let me know...
    BR
    Valdevair

    Dear friend,
    Do check configuration node at
    plantmaintenance and custonmer service - maintenance and service processing -maintenance and service orders - functions and settings for order types - define change documents,collective pur.requisitionsindicator,operation no.interval
    here for your order type and plant  , check whether generation of PURCGHASE REQUISITION from maintenance order settings.
    there will be three options
    1) never
    2) from release
    3) immediatly.
    hipe this will help you.
    Regards,
    pardhu

  • "Create quotation for order" is not allowed (ORD 80000119 )

    Hi,
    After creation of service order I want to create quotation then  system gives error massage as below,
    "Create quotation for order" is not allowed (ORD 80000119 )
    Message no. BS002
    Diagnosis
    The transaction 'Create quotation for order' is not allowed for  ORD 80000119, because no status is set to permit it.
    System response
    You cannot carry out the transaction 'Create quotation for order'.
    Procedure
    You can carry out this transaction if you set a user status, which permits 'Create quotation for order'.
    Thanks & Regards
    kapil

    Kapil,
    Check the System status and user status of the order. Quotation can be created only before releasing the order (REL). or Any user status that may prevent creation of Quotation.
    Babu

  • Email Alert for Purchase Order Release

    Hi,
    When a PO is subject to release I would like an external email to be sent to the relevant user as per assignments in config.
    I have used standard workflow for PO release and this is working with no problems, alerts successfully going to the workflow inbox.
    But does anyone know the steps to configure the standard workflow so that an external email is sent?
    Thanks

    hi
    WORKFLOW FOR PO RELEASE PROCEDURE
    Steps involved are :
    1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
    2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
    3) Go to OOCU > here under MM, go to MM-PUR,
    4) Click on "activate event linking"
    5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
    and Save.
    6) Click on "Assign agents" and proceed all above steps.
    BUS2012 is the relevant business object and Releasestep created is the event for the same.
    7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
    Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
    regards
    KI

  • Unique serial number during production order release for FG materials

    Hi,
    Actually our client is asking for serial number generation for each FG material during its production order release.
    So that with this serial number he can track it in shop floor plus after dispatching to customer.
    Here the scenario is Make To Order, this serial number will also be considered by SD during dispatch.
    For serial number creation, I referred documents from SAP best practices(help.sap.com).
    After this, now I am able to create serial number for specific material automatically.
    Currently I am getting serial number with respect to material specific, i.e., serial number generating with respect to FG codes. Ex:- FG1 - 1, 2, 3, 4 and FG2 - 1, 2, 3, 4.
    But as per my client requirement, they want serial number without material specific, i.e., common serial number for all FG codes.
    Ex:- Sr No- 1-FG1, 2-FG1, 3-FG2, 4-FG1 - - - - according to production order releasing sequence.
    Plz inform if any settings are to be made.
    Thank you in advance.

    Hi Arman,
    I Had got solution for how to track which FG is linked to which SFG sr no, just go through the below link it also gives how to use COIB transaction.
    COIB transaction usage, how to track which FG is linked to which SFG sr no
    But still I had not got solution for
    how to assign common serial number for all FG codes automatically
    Ex:- Sr No- 1 -> FG1,
    2 -> FG1,
    3 -> FG2,
    4 -> FG1
    - - - - according to production order releasing sequence.
    Whether is it automatic serial number assignment is possible or not.
    Plz inform if any settings are to be made.
    Thank you in advance.

  • ATP for Internal orders

    Hi All,
    I'm a new Oracle user asking for your help. We are using the ATP for make-to-order items only in order to assign to the sales orders a scheduled ship date that consider the manufacturing LT set up in the "Cumulative Manufacturing" field in the org item. We receive two different types of orders- Sales orders and Internal Orders. It looks like the ATP works for the sales orders only. Could you advise if it is possible to set it up for internal orders as well?
    Many thanks

    Hi
    Thanks, but the internal sales orders will be sent to APO with a new Z ATP category. We want to know if this new Z ATP category can be used for example in the BOP also for back order processing.
    Also if there are inconsistencies, can inconsistent sales orders with the Z ATP category also be recognized in the Delta report, or do we need to make enhancements?
    I could not find a clear note which describes if you create a new ATP catagory for sales orders in APO which standard APO eports will work seamlessly with the new ATP categoy. And if the below reports should be enhanced (user exits, BADI etc) to make sure sales orders assigned to a custom ATP category will also be included in the comparisson between APO and R/3.
    Backorder processing: /SAPAPO/BOP
    Deltareport: /SAPAPO/CIF_DELTAREPORT3
    Correction report: /SAPAPO/SDRQCR21

Maybe you are looking for

  • Mail going as an attachment in Processchain

    Hi All, We have created a processchain which sends mail to the users after successful loading. BUt the problem is they are getting the mail as an attachment and the file format is ".RAW". Could anyone help for getting the mail in Txt format. Thanks i

  • Creating a QT Master for a Digital cinema Screening.

    Hello, I'm preparing a film for a Digital Cinema release. We shot it DVCPRO HD 1920x1080 25fps progressive and we are delivering a TIFF video file with the same specs. They will then be upresing that to a 1998 x 1020 DCP file. My concern is that the

  • Read spool - convert to PDF - FTP transfer

    Hi, How can I read a particular spool then convert it to PDF and transfer the PDF file to another system using FTP? Can anybody give me sample code or tutorial how to do this. thank you very much!!! james

  • Downgrade firmw

    Hi, I know the latest firmware for Zen micro is Creative Zen Micro Firmwarle ..0 but i need to downgrade the firmware to an older one. With this firmware i need to install Zen to be able to charge it using other Pcs USB port but with the old firmware

  • Blackberry Q5 wont read SD card

    Last week on Monday i had to turn my phone off due to an exam in school. Once the exam had finished i turned my phone back on and i looked on my pictures and the media files had dissappeared. So did my music files. I took my media card out and put it