Purchase order release history table

Hi,
  I would like to know the table where we can have history of purchase order releases.
For example, If the purchase order created and released. Later purchase order release is cancelled. Again i will release the purchase order.
Even the the release history is not maintained in the table EKBE. I am not aware of the reason for not having the data in EKBE.
I would like know all the release history would be maintained . In the table EKKO, i can find only  latest release status.
Can you please throw light on this. Thanks.
Regards
Badari
Edited by: Badari Narayana1 on Nov 19, 2009 8:10 PM
Edited by: Badari Narayana1 on Nov 19, 2009 8:11 PM

If memory serves correctly, you have to use change documents for this.
Read the documentation for FM CHANGEDOCUMENT_READ . You will also find lots of information in the forum.
Rob
Edited by: Rob Burbank on Nov 19, 2009 2:22 PM

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.

  • Purchase order release table

    Hi,
    we have a purchase order release strategy defined in our company. I am trying to make a SAP query that will show the list of purchase orders that are hanging for approval. I am trying to find the table that hold the information of which purchase order is on whose approval screen.
    Please advise
    SAPXPT

    Hi,
    You can use EKKO and T16FS tables and write your own logic to create Z- report with the help of ABAPer.
    From EKKO table you will get following details for each PO
    FRGGR    Release group  
    FRGSX    Rel. Strategy
    FRGKE    Release ind.
    FRGZU    Release status
    Release ind - FRGKE will help to filter POs from EKKO table which are not release yet completely that is having blocked status or some other defined one except C.
    Get release level from T16Fs table by giving following inputs which you will get from EKKO table
    FRGGR    Release group  
    FRGSX    Rel. Strategy
    Yuo will received release number of relese codes in sequence as per the strategy.
    E.g. code 01, 02 and 02 for release strategy XX and Release group YY.
    Now you know for perticular PO what is release strategy and what are the levels of PO approval i.e. 2 level, 3 level or 8 levels.
    In EKKO table we have field  FRGZU -  Release status ,  this field will give you details at which level Po is release
    E.g. if this field has value XXX that means PO is release at 3rd level and pending for approval at 4th level and you can find the 4th level release code from T16FS table.
    If field value is blank that means pendingat 1st level.
    Regards,
    Shailesh Mackwan

  • Sales order changes history table

    hi.........
    i wann field for user name from sales order change history table. i hv tried CDHDR and CDPOS, but i cound't get the exact link in those tables.
    will u tel me any other table, so that i can get this field by passing sales order ?

    Hi subharao,
    Go though this program.
    REPORT zmm_rep_poh NO STANDARD PAGE HEADING LINE-SIZE 250 LINE-COUNT 65.
    TABLES: cdhdr,cdpos,ekko,ekpo.
    TYPE-POOLS : slis.
    DATA       : t_fieldalv     TYPE slis_t_fieldcat_alv.
    DATA       : import_variant LIKE disvariant.
    DATA       : xrepid         LIKE sy-repid.
    DATA       : layout         TYPE slis_layout_alv.
    DATA: BEGIN OF itab OCCURS 0,
            fname(40) ,
            objectid(10),
            changenr(10) ,
            value_new(10),
            value_old(10),
            unit_old(10),
            unit_new(10),
            cuky_old(10),
            cuky_new(10),
            key(5),
            username(10),
            udate LIKE cdhdr-udate,
            utime LIKE cdhdr-utime,
          END OF itab.
    DATA iebeln(15).
    DATA: BEGIN OF itab1 OCCURS 0,
            username(10),
            udate LIKE cdhdr-udate,
            changenr(10),
            utime LIKE cdhdr-utime,
          END OF itab1.
    DATA: BEGIN OF itab3 OCCURS 0.
            INCLUDE STRUCTURE itab.
    DATA: END OF itab3.
    DATA iekko LIKE ekko OCCURS 0 WITH HEADER LINE.
    *Select Option
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS : s_ebeln FOR ekpo-ebeln OBLIGATORY,
                     s_ekorg FOR ekko-ekorg NO INTERVALS DEFAULT '77IN',
                     s_bukrs FOR ekko-bukrs NO INTERVALS DEFAULT '77IN'.
    SELECTION-SCREEN END OF BLOCK b1.
    *INITIALIZATION.
    for alv field catalog definition.
      PERFORM initial_alv_fieldcat CHANGING t_fieldalv[].
    START-OF-SELECTION.
      SELECT * INTO iekko
      FROM ekko
      WHERE ebeln IN s_ebeln AND ekorg IN s_ekorg AND bukrs IN s_bukrs.
        APPEND iekko.
      ENDSELECT.
      LOOP AT iekko.
        SELECT username udate changenr utime
        INTO   (itab1-username,itab1-udate,
               itab1-changenr,itab1-utime)
        FROM  cdhdr
        WHERE objectid EQ iekko-ebeln.
          APPEND itab1.
        ENDSELECT.
      ENDLOOP.
      LOOP AT itab1.
        SELECT objectid changenr fname value_old value_new unit_old unit_new
               cuky_old cuky_new
        INTO  (itab-objectid, itab-changenr, itab-fname,
              itab-value_old,itab-value_new ,itab-unit_old, itab-unit_new,
              itab-cuky_old,itab-cuky_new)
        FROM  cdpos
        WHERE changenr = itab1-changenr.
          IF sy-subrc = 0.
            itab-username = itab1-username.
            itab-udate    = itab1-udate.
            itab-utime    = itab1-utime.
            APPEND itab.
          ENDIF.
        ENDSELECT.
      ENDLOOP.
    delete itab where fname eq 'KEY'.
      sort itab by fname.
    delete ADJACENT DUPLICATES FROM itab comparing all fields.
      LOOP AT itab.
        IF itab-fname = 'ZTERM'.
           itab-fname = 'Payment Terms'.
          MODIFY itab.
        ELSEIF itab-fname = 'AEDAT'.
               itab-fname = 'Date'.
          MODIFY itab.
        ELSEIF itab-fname = 'EFFWR'.
               itab-fname = 'Effective Value'.
          MODIFY itab.
        ELSEIF itab-fname = 'MENGE'.
               itab-fname = 'PO Quantity'.
          MODIFY itab.
        ELSEIF itab-fname = 'BRTWR'.
               itab-fname = 'Gross Order Value'.
          MODIFY itab.
        ELSEIF itab-fname = 'NETWR'.
               itab-fname = 'Net Order Value'.
          MODIFY itab.
        ELSEIF itab-fname = 'PROCSTAT'.
               itab-fname = 'Purchasing Doc processing state'.
          MODIFY itab.
        ELSEIF itab-fname = 'FRGSX'.
               itab-fname = 'Release Strategy'.
          MODIFY itab.
        ELSEIF itab-fname = 'FRGKE'.
               itab-fname = 'Release Ind. Pur. Doc'.
          MODIFY itab.
        ELSEIF itab-fname = 'ZBD1P'.
               itab-fname = 'Cash Discount Perc 1'.
          MODIFY itab.
        ELSEIF itab-fname = 'ZBD1T'.
               itab-fname = 'Cash Discount Days'.
          MODIFY itab.
        ELSEIF itab-fname = 'ZBD2T'.
               itab-fname = 'Cash Discount Days'.
          MODIFY itab.
              ELSEIF itab-fname = 'KEY'.
               itab-fname = 'Item Entered'.
          MODIFY itab.
        ENDIF.
      ENDLOOP.
      PERFORM alv_grid_display.
    *&      Form  alv_grid_display
          text
    -->  p1        text
    <--  p2        text
    FORM alv_grid_display .
      DATA  : gt_event  TYPE slis_t_event.
      DATA  : dbcnt TYPE i.
      DATA  : dbcntr(10) TYPE c.
      DATA  : title(100) TYPE c.
      CLEAR : dbcnt,dbcntr,title.
      DESCRIBE TABLE itab LINES dbcnt.
      dbcntr = dbcnt.
      CONCATENATE 'NO.OF ENTRIES : ' dbcntr INTO title SEPARATED BY space.
      sy-title = title.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          i_callback_program = sy-repid
          is_layout          = layout
          it_fieldcat        = t_fieldalv[]
          i_save             = 'A'
          i_grid_title       = 'Purchase Order Amendment Details'
        TABLES
          t_outtab           = itab
        EXCEPTIONS
          program_error      = 1
          OTHERS             = 2.
    ENDFORM.                    " alv_grid_display
    *&      Form  initial_alv_fieldcat
          text
         <--RT_FIELDCAT  text
    FORM initial_alv_fieldcat  CHANGING rt_fieldcat TYPE slis_t_fieldcat_alv.
      DATA       : ls_fieldcat TYPE slis_fieldcat_alv .
      DATA       : cntr TYPE i VALUE 1.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 1.
      ls_fieldcat-fieldname = 'USERNAME'.
      ls_fieldcat-seltext_l = 'UNAME'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 2.
      ls_fieldcat-fieldname = 'UDATE'.
      ls_fieldcat-seltext_l = 'UDATE'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 3.
      ls_fieldcat-fieldname = 'UTIME'.
      ls_fieldcat-seltext_l = 'UTIME'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 4.
      ls_fieldcat-fieldname = 'OBJECTID'.
      ls_fieldcat-seltext_l = 'PO Number'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 5.
      ls_fieldcat-fieldname = 'FNAME'.
      ls_fieldcat-seltext_l = 'Field Name'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 6.
      ls_fieldcat-fieldname = 'VALUE_OLD'.
      ls_fieldcat-seltext_l = 'Old Value'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 7.
      ls_fieldcat-fieldname = 'VALUE_NEW'.
      ls_fieldcat-seltext_l = 'New Value '.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 8.
      ls_fieldcat-fieldname = 'UNIT_OLD'.
      ls_fieldcat-seltext_l = 'Old Unit'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 9.
      ls_fieldcat-fieldname = 'UNIT_NEW'.
      ls_fieldcat-seltext_l = 'New Unit'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 10.
      ls_fieldcat-fieldname = 'CUKY_OLD'.
      ls_fieldcat-seltext_l = 'Old Cuky'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      CLEAR ls_fieldcat.
      cntr = cntr + 1.
      ls_fieldcat-col_pos   = 11.
      ls_fieldcat-fieldname = 'CUKY_NEW'.
      ls_fieldcat-seltext_l = 'New Cuky'.
      ls_fieldcat-do_sum    = 'X'.
      APPEND ls_fieldcat TO rt_fieldcat.
      layout-zebra = 'X'.
      layout-colwidth_optimize = 'X'.
    ENDFORM.                    " initial_alv_fieldcat
    *********Rewards some points.
    Rgds,
    P.Naganjana Reddy

  • Purchase Order Release Report

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

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

  • Purchase order release strategy report

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

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

  • Purchase Order release date

    Dear Experts
    Can anybody give me table & field of Purchase order release date .
    which we can see in Version tab of ME23n
    thanks
    Nayan Lad

    hi,
    please refer to the following thread:
    TAble for PO Release date
    i hope it helps.
    arjun

  • 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

  • TWO CURRENCIES IN ONE Purchase Orders Release Procedure.

    TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
    Please provide a solution if a release strategy is maintained for two currencies like USD and SGD for more clarification please Read the below Requirement.
    Requirement for Singapore:
    u2022          COMPANY Asia (Singapore) wants its own Purchase order release strategy is based on their local currency (SGD)
    u2022          Whereas COMPANY is using only USD as currency in Purchase order release strategy.
    u2022          Standard SAP works based on Character currency which is defining in Class of Purchase release strategy and converts with Local currency to compare with Character Currency.
    Required analysis:
    u2022          The value assigned in classification is based on Conversion from SGD to USD, Due to Exchange rate fluctuations the assigned value is differ by large amounts and hence system is either determining the higher release strategy or Lower release strategy
    u2022          But during Release Strategy Configuration the Net order Value is assigned as 3600 USD considering the Exchange as 1.388889.
    u2022          As per the exchange rate in the purchase order 1.3799 the system is calculation the PO Net order Value but the Strategy is Determined based on the value maintained according to exchange Rate 1.388889
    In the Purchase Order the system is 
    Ex:  Total Purchase Order Value is 4765.21 SGD and 3453.30 in USD
          For Level 1 the value limit is 5000 SGD if it exceeds 5000 SGD it has to go to his manager (Level 2) Exchange rate on 01.04.2008 is 1.3799.
    System Considerations:
    Possible Solution:
    1.        Create a new Class with Characteristic with Currency Value SGD System should determine the class based on the combination of Plant 6000 and Document Category F Purchase Order.
    2.        By using Enhancement spot with Function Module ME_RELEASE_STRATEGIE/ ME_RELEASE_STRATEGIE_EKKO
    Logic:
    1.        System will determine the class PUR_RELEASE from table T16FG if the system finds Plant as 6000 and Document Category as F Then replace PUR_RELEASE with New class as ZPUR _6000.
    2.        Maintain Z table for the combination of Plant and Class for future requirement
    Edited by: Mohammad Irfan on Jun 8, 2009 10:41 AM

    Hi Mohamed,
      You can create separate characteristics far all check points and assign those to class.
    Regards,
    Prasath

  • Problem in Purchase Order Release Workflow

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

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

  • Purchase order Release Stratergy-Error in Class CL01

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

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

  • Purchase order release workflow - urgent

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

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

  • Dead Line Monetering in Purchase Order Release Workflow

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

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

  • No of levels in purchase order release more than 8

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

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

  • Graphical view in Purchase order release strategy

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

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

Maybe you are looking for