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

Similar Messages

  • Purchase Order released date field and table name

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

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

  • Deliveries and contract release order ( LIKP ; LIPS tables)

    Hi,
    We have an extractor for SAP BW based on LIKP and LIPS tables.This extractor is fetching all the deliveries.
    What I want to know is , Do this tables have all the deliveries i.e deliveries against a sales order and also
    contract release order ( or call offs  or deliveries against sales order for customer with Contract).
    If yes, how can I seperate the deliveries for contract release orders, I mean based on which field?
    And also is there information on Total quantity of the Contract available from this tables?
    Thank you
    Regards
    mandha

    Hi Mandha
    Find field definition for following:
    VBELN : Delivery
    POSNR : Delivery Item
    LFART : Delivery Type
    PSTYV : Item Category
    LFIMG : Delivery Quantity
    KCMENG: Cumul Batch Quantity
    VGBEL : Reference Document
    VGPOS : Reference Item
    VGTYP : Sales Document Category
    ABRLI : Int Dlv Sched No.
    ABART : Release Type
    QUANT : Store Quantities
    You can use SE11 for definition of fields and table details.I hope this will help you.
    Regards
    Nagendra P Boggarapu

  • Purchase Order Release Strategy and SAP user RelationShip

    Hi,
    We are currently developing a work flow to streamline PO release in our company . What we want to achieve is that
    E.g
    A purchase order 100001 is creates and a release strategy s1 is applied to it which is a 3 level relase statrgy having release code c1,c2,c3 which are uniquely assigned to user/employee of the company and no 2 users'employee can have the same release code.
    Now when c1 release the purchase order a work item should be created to for the user/employee who is assigned the c2 code.
    Currently this workflow is not implemented in our company adn the relase stategy is handeled by authorization oobjects and when ever a po user relase the po he calls up the other persona next in relase strategy to notify him about the work he has to do .
    I am need to know can we develop a relationship b/w the release code and sap user or employee
    Regards
    Kamran ellahi

    Hi,
    We are currently developing a work flow to streamline PO release in our company . What we want to achieve is that
    E.g
    A purchase order 100001 is creates and a release strategy s1 is applied to it which is a 3 level relase statrgy having release code c1,c2,c3 which are uniquely assigned to user/employee of the company and no 2 users'employee can have the same release code.
    Now when c1 release the purchase order a work item should be created to for the user/employee who is assigned the c2 code.
    Currently this workflow is not implemented in our company adn the relase stategy is handeled by authorization oobjects and when ever a po user relase the po he calls up the other persona next in relase strategy to notify him about the work he has to do .
    I am need to know can we develop a relationship b/w the release code and sap user or employee
    Regards
    Kamran ellahi

  • Disabling selected Purchase Order field(s) after released/approved

    Hi Experts,
    I have a requirement to disable specific Purchase Order fields after released via ME29N.
    For example, in Purchase Requisition - I can "Release Indicator - Field Selection Key" to control Purchase Requisition screen layout. However, for Purchase Order - the configuration for "Release Indicator" consist only standard default "Chgable" options.
    Question:
    Is there a way to customize the Purchase Order "Release Indicator" for screen layout based on customer requirements other that using the default as mentioned above?
    Thank you.
    Steven

    Hi Padmasri,
    I understand your explanation on the standard SAP behavior.
    Nevertheless, I'm looking for some flexibility to meet customer requirement. Like in Purchase Requisition, there is option to further customize the screen layout by linking it to the "Release Indicator".
    Therefore, apart from the standard 6 options given by standard SAP, can we add/customize the options? For example, my customer may one to change a field in the Purchase Order even after released.
    Thank you.
    Steven

  • Guidelines, Form Fields and Tab Order

    I've been fighting a form for about two weeks now with Acrobat 9 Pro. I used guidelines to make sure I could get 2 buttons and a field aligned properly. I have 92 instances of this arrangement. When I reopened the file after I had worked on it for a couple of hours (precisely positioning the guidelines so that I could have consistent field sizes), the guides were gone. What happened. It has now happened three times. I ended up keeping the computer on for 5 days just because I didn't want to lose the guides.
    I'm having a similar problem with the selection for tab order. I have right clicked on the page on the left panel, chosen page properties and set tab order to unspecified. I then reorder the fields in the field panel and save the file. When I open the file again, the tab order is unchecked and the fields are not in the order I left them.
    Does anyone have any idea why I'm losing my sanity with this Acrobat form. I did it in Acrobat because I thought it would be easier than LiveCycle Designer.
    I am duplicating a print form. This means there are 92 places where I have a small button (visible but doesn't print) which executes a JavaScript when pressed to show another button (because it has an icon which will circle the date indicated in a field. I'm thinking I should have the small button on top, aligned on the bottom with the field for the date and the circle icon as the bottom button. How do I get all of these fields and buttons (a mere 276) to go in the right order and stay that way?
    Warren Bingham

    Warren wrote: "I'm having a similar problem with the selection for tab order. I have right clicked on the page on the left panel, chosen page properties and set tab order to unspecified. I then reorder the fields in the field panel and save the file. When I open the file again, the tab order is unchecked and the fields are not in the order I left them."
    In the left panel, in the Sort drop-down list, you have Tab Order selected, right? In the Tab Order drop-down list, is Order Tabs Manually selected?
    I am not able to get any menu by right-clicking on the page in the left panel. Can anyone tell me, is there another way to view the page properties while in Form Editing? I'm not finding it in any of the regular menus (menu bar) and I'd like to verify the setting Warren mentioned, for troubleshooting my own problems with tab order.
    EDIT -- Of course, as soon as I type it out, I discover the cause. I thought he meant the page in the Form Editing view, but no, I have to open the Pages view and right-click on each page. (Oddly, no options were selected at all. Usually a radio button set will default to the most popular option.) So -- sorry, never mind me.

  • Preview and print a printout in production order release

    Iu2019m using CO02 to release and save the production order. Currently u201Cbatch cardu201D printout is automatically printed in production order release. I want to change this to preview the printout before printout is send to the printer. Can someone tell me the configuration for this.

    Hi
    Pls refer this link
    layout adjustement in production order- suitable to printout sheet
    Print Preview of Production Order
    layout adjustement in production order- suitable to printout sheet
    Thanks
    S.Murali

  • Production and Service order Release Log updation

    Hi,
    Can any one help me how to update the release log of Production and service order.
    I have a requirements to add new custom logs to the production and service order release process.
    sudha

    As far as I know the standard behaviour is that the PR is created upon order save and not upon the status of the order or items changing to released.
    To get around this you can set user status and use status management to prevent the PR getting created or use the BADI CRM_SRV_FIND_LOG_SC to supress creation of the PR.
    Hope this helps.

  • Profit center field and internal order field in sales order

    Hello all,
    I am unable to find the settings for profit center field and internal order field in sales order account assignment tab screen. kindly let me know the path and configuration settings.
    Thanks in advance
    Regards
    srinivas

    Hi Srinivas
    If you want to assign the profit center then make sure that the Profit center is assigned in MMR->Sales orgn 1 view . 
    But to assign the Profit center in MMR also you need to configure the Profit center first for your Material in your company code with the help of FI/CO consultants and then assign then the profit center will flow from MMR to sales order  item data->account assignment tab
    Regards
    Srinath

  • Tracking Order release and Delivery Document

    Hi,
       I have the belwo scenario. Sales order is enter and released by User1 and delivery document is created by user2.
       The sales order can have multiple releases by User1, USER1A, USER1B. The same as for Delivery document USER 2, USER 2 A, USER 2B.
      Is there a way to link all these?
    Basically i am trying to link VBAP ( order Header ) CDHDR ( Change header table) and LIKP ( Delivery Header).. How can i recognize for 5 order releases 4 or 5 delivery is created and by which user?
    Your help would be highly appreciated.

    Hi Ashwini
    I would suggest you this.
    Create a Z table with SO Number, Line number, Status and user id.
    Create an output type and assing it to the sales order.
    In the program for the output type write a simple logic to update the Z table.
    Now you can link the sales order line item from VBAP, Ztable and LIKP.
    Please reward points if this helps.
    Thanks

  • Ordering of objects by more than one field and get counts

    i have an object visit (personid, city, street, place, date)
    A person could have visited a same place in the same strret in the same city several times on different dates.
    I have a visits 'Set' for a person and I have to get a count of visits he has done to a place..
    its basically select count(visits) group by city, street , place.
    I know to use interface comparator for a single field.. how to compare multiple fields and get counts??
    if you know abt where i can find information please let me know.
    Thanks.

    For multiple fields, your comparator compares the most significant field first. If they're unequal, it returns +/- accordingly. If they're equal, then it moves on to the next field. And so on, until, finally, if all the relevant fields are equal, then the objects are equal.
    Just like what you do when comparing, say, last names. If the first letters are unequal, you're done, else move onto the next letter, and so on..
    For the count, you wouldn't use a comparator, as that's for sorting. Exactly how you do it depends on the details of what you're storing and how, which you haven't provided.

  • Field material in purchase order Release ECC.6

    Hi, I see that in my system ECC.6 the field material in PO is hidden. How can I do to see material field?
    Thanks

    Hai Barbara...
    Can you be more specific on your question...
    Please provide exact requirement so that you get quick answers..
    Please mention the Field name or tech details of that field and where your are trying to see it.
    Thanks
    Arshad

  • Purchase order Release Stratergy-Error in Class CL01

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

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

  • 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

  • Purchase order release only at header level?

    Hello all,
    does anyone knows a method or workaround to allow implementation a release strategy based on the positions
    of a purchase order (like the posibilities in purchase requisition's customizing).
    I can't find anything that helps further, only a customer development seems to be the solution.
    The goal is, to route a workflow on position based cost center and account responsibilities.
    There is only a field for PO release status in the table EKKO, not in EKPO. For the PR, there is a correspondig
    field in the table EBAN.
    Thanks for incoming answers!
    Jens

    Hi Diego,
    sorry, my error! Thank you for your hint, but i can't find ad hoc the matching forum on sdn.
    Yes, i'm talking about MM, in detail the customizing of
    the purchasing process (procurement).
    Best
    Jens

Maybe you are looking for