Display PO Release group Approval Information-urgent

Hi All,
     In my report i have to display PO Release Date, PO Release group in various level,based on Approval From Release i have to display the PO Status(Released or not).In Our project we have 3 level of approval in PO Release group such as PO(Purchase officer),PM(purchase manager),GM(General Manager).So finally my output like this.....
Release Date ReleaseGroup  Status                              
                      PO PM GM      Pending
So guide me where can i get the fields for
PO Release Date,
Release Group and their approval status,status of PO

Hi Cristophe,
I checked the table BBP_WFLOCK and could not find any entry.
However in transactional RFC I could see an entry for this user XXXX and tried to delete this entry but I am not able to do so,below are the details observed in SM58
SWW_WI_EXECUTE_INTERNAL_RFC is the Function module.
WORKFLOW_LOCA is the target system.
Error in the module RSQL accessing the database is the status text.
Also I checked the FM BBP_PDH_WFL_CHECK_WF_BUSY but did not find any error.
One thing I would like to mention is that in BBP_PD the workflow status is completed for the PO but only in the web browser it is showing the status Awaiting Approval.
Again I tried to change the PO but again I received the same warning error "Document is still being processed in the background,try again later".
Regards,
Raj

Similar Messages

  • Release Group for T code FBV1

    Hi All,
    I have a problem. If vendor/customer, I have assigned release group approval path in vendor/customer master data. But for transaction in Tcode FBV1, I cannot assigned release group approval path in FS00 (GL Account Master Data). I want to ask, where I can assigned release approval path for GL Account which can make Approval Path for FBV1?
    Thanks,
    John

    Hi,
    The message has explained the problem.
    You cannot have two classes for the same document release and you are tryng to break this rule by adding another entry (the fact that you have give it a different release group does not make any difference this is still another class for the same document.)
    You should be able to do what you want without the need for a new release group or additional class, after all everyone else that uses SAP is using one class per document.
    Why diod you think that you needed another release group / class?
    Steve B

  • Class and release group and code in release strategy??

    hi experts ,
    Can some body explain me..
    I have created Characteristics and Class for for release strategy.
    But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
    I m using the same class what i have created for my company..
    So how to over come this issue
    Thanks

    Release Prerequisites
    Definition
    The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
    The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
    Release Indicator
    Definition
    When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
    When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
    What does the release indicator determine?
    Requisitions...
    External purchasing documents....
    Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
    Whether an RFQ or a PO may be created with reference to the item
    Whether the document may be changed by Purchasing after the start of the release procedure
    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
    Whether the purchasing document is released for transmission
    Alternative Release
    Definition
    Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
    Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
    The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
    An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
    Release w. Classification (PReqs./Ext. Pur. Docs.)
    Use
    The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
    The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
    Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
    If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
    Prerequisites
    The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
    If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
    How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
    This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
    Operation of Release Procedure w. Classification
    The characteristic values from a requisition or external purchasing document are passed on to the classification system.
    The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
    The persons responsible for the release codes process the document in the sequence defined in the release strategy.

  • Release Groups and code - PR and PO??

    Hii
    Some body explain me about the significance of release code and groups in PR and PO release strategy.??
    Thanks

    HI,
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users
    Check the link for more details
    http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM
    Regards
    KK

  • Release Procudure - Problem while creating Release Group:Reg-

    in release procedure char. were created and class also created and the char. were assigned to the class too.
    But when i am creating release group the below error was coming..
    Please check release classes (see long text)
    and if i am see long text the below is the error
    Please check release classes (see long text)
    Message no. ME492
    Diagnosis
    Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
    Procedure
    Assign the release groups that were created for overall release to one release class only. Assign the release groups that were not created for overall release to a different release class.
    Example:
    Rel. group Rel. obj. Overall rel.    Class       Description
    01 1 _   FRG_EBAN      Group 01
    02 1 _   FRG_EBAN      Group 02
    S1 1 X   FRG_GF_EBAN Group S1
    S2 1 X   FRG_GF_EBAN Group S2
    please see what can i do to solve the issue.
    Thanks and Regards,
    Rajesh.

    HI,
    It is not possible to have more than one class define in the release
    strategy but it is possible to define difference characterics within
    the same class.
    Please verify the following:
    1) As the long text of the message says, first check that one release
      class only is used within the release groups for overall release and
       the release groups without overall release in each case. However, in
       this instance several release classes have been used.
       This means you have to have one release class only for all the
       release groups for overall release.
       Assign the release groups that were not created for overall release
       to a different release class.
    Example:
    Rel. group,   Rel. obj.,   Overall rel.,  Class ,     Description
    01,,1,,_,    FRG_EBAN,      Group 01
    02,,1,,_,    FRG_EBAN,      Group 02
    S1,,1,,X,    FRG_GF_EBAN,   Group S1
    S2,,1,,X,    FRG_GF_EBAN,   Group S2
    2) If you have followed all the indications of the long text of the
       message and the error is still displayed, please try to create the
       new release group via the 'New Entries' button.
    3) If you tried to create the release group via this button and the
       error is still been displayed, please verify the implementation of
       note 125316 in you system.
    Best Regards,
    Arminda Jack

  • Purchase Order Release Strategy Approval

    HI All,
    I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
    Level one will have 1 approver
    Level two must have two approvers.
    The scene is:
    Level one will approve all purchase orders betwee 400 to 5000 euros.  1 approver only
    Level two will approve all purchase orders above 5000 euros.  2 approvers.
    The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
    Pur. group G70, Release Group GC and release strategy DF.
    I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
    CL20N is completed for both levels and works correctly for level one approval but not for level two
    Can any please help
    Leslie

    Hi,
    May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
    1. PO Order Type (ZPO_BSART),
    2. Company Code (ZPO_ BUKRS),
    3. Purchasing Organization (ZPO_EKORG),
    4.Plant (ZPO_WERKS)
    5. Purchasing Group (ZPO_ EKGRP) and
    6. Total net PO Value (ZPO_GNETW)
    Create one release class ZPO_CLASS & then add all above release characteristics
    And then design your release strategies as required.
    AND under release characteristic for PO Value (ZPO_GNETW) keep following values
    A. <= 400 EUR
    B. 400.01- 5000 EUR
    C. >5000 EUR
    As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
    NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
    In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
    Regards,
    Bijju K

  • CM21 - How to display only released orders in CM21

    Hi,
    I want to display only released orders in trasaction CM21. Currently it is displaying both created and released orders.
    could you please guide me how to proceed?
    BR/
    Laxmikant Lande

    Hi lax,
              By the way this problem is solved by assigning set for released order to the filter set in selection profile.
    That's great. Taking a cue from you i also tried that but could not find that appropriate set name/identification which i may assign to the filter set to get only the released orders by default in CM21. Can you share your experience?
              On CM21 Filter screen, there is no std field to control order status ...
    You're right. Actually what i meant was that in the filter screen you get the order number as an input field. If you press f4 you will have the different matchcodes available to choose the order. If you select the order information system as the input help you will arrive at the standard COOIS or COOISPI screen where you can choose the released orders by giving REL as the input in sys status. This will pick up all the released orders.
    Regards
    Sm.
    Edited by: Sm on Sep 2, 2010 12:27 PM

  • Release group does not appear in ME55 and

    Dear Experts,
    My query is related to defining a release group for purchase requisition in customizing activity "set up proceedur with classification" here it displays only one release group but in table T16FG it has three release groups and when we try to define in customizin it gives an error that an entry already exists.it this a system inconsistency in table T16FG?
    what is difference between release set up with and without classification? are release groups for PR and Po are different?
    I am new to MM and and will appreciate if get some besic documentation on release proceedure for PO and PR at mt personal email [email protected]
    Any help will be appreciate and rewarded.
    Thanks in Advance
    Anand

    release procedure with classification means u can relase a pr at item lvel as at header lelvel but in case of w/o classification bith type of release is not possible
    but point to note here is you can not release external purcahsing document (like po, rfq) at item level even though u create the strategy with classification
    yes in pr & po release groups are different

  • PO release by approving officer

    Dear All,
    Good Day!
    How can i config release strategy with 2 approving officer using authority matrix
    1. 1st approving officer release up to 500 thousand
    2. 2nd approving officer will also released po if more than 500 thousand
    Request to please explain step by step procedure of setup/config
    Thanks in advance
    Ermin D. Concepcion

    Hi,
    As I understand, U have 2 approving officers which in turn release two levels, so then  create release codes{A1 (1st approving officer) & A2 ( 2nd approving officer )}.
    Now create release characteristics(CT04) for PO VALUE with CEKKO with GNETW & keep with values <= 500,000 & >500,000. Add release characteristics for PO VALUE with other release characteristics ( PO document type, Plant, Pur.Org, Pur. Group) in a single PO Release Class(CL02).
    You should have release Group(PO) for PO & Create two Release strategies (T1 & T2). Now during designing release strategy, you can keep value <= 500,000 with A1 release code under T1 release strategy and keep value > 500,000 with A2 release code under T2 release strategy.
    Regards,
    Biju K

  • Problem in creating Release group for Release Procedure for PR

    Hi Experts,
    I could not able to create Release Group ( 01 & 02 ) for Release Procedure and assigning it with a Class
    ( Z_CLASS_PR ) in Set up Procedure with Classification.
    The following error is getting displayed.
    Please check release classes (see long text)..
    How to over come this problem.
    Thanks in advance.
    Regards,
    Nani

    Release group:
    You are only allowed to use one class for each release object (1=PReq, 2=Purchase order). When you use the overall release (as of Release 4.0A), you are only allowed to use one class for the overall release or individual release. If you use the overall release for purchase requisitions, you must mark this for the document type (transaction OMEB, flag for V_T161-GSFRG) and the release group (transaction OMGQ, flag for V_T16FG-FRGFG). In the overall release, the system only takes into account characteristics that are identical for all items. If, for example, item 10 of a purchase requisition contains material group 001 and item 20 contains material group 002, the material group is set to BLANK for the strategy determination.

  • How to Display PO Release Strategy in Enjoy Screen

    Dear all,
    I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
    However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
    In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
    Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
    Thanks a lot.

    Thanks 4 the reply Rahul.
    I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
    In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
    So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
    I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
    Thanks and appreciate if anyone could help.

  • Error while creating new release groups in PO release strategy

    Hi All
    I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
    But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
    Thanks for your support.
    Illan

    Dear,
    Please follow below mention path.
    *and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
    *- Follow below mention path.*
    *SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
    *Three steps involved in release process of purchase order.*
    **Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
    **Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
    *Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
    Now see each steps of Define release procedure of purchase order in briefly: -
    Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
    Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
    *Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
    Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
    Regards,
    Mahesh Wagh

  • PO Release Group Problem

    Hi All
    This problem regarding Purchase Order Release Strategy.
    I have deleted the existing Release group : 02 and created New Release Group: 11 for Purchase Order Release Procedure.
    I deleted Release Group 02 and Release strategy in sequence.
    But still when I'm using ME29N transaction, system using release Group 02 not New group 11.
    I verified all Release Group related tables.
    T161E,S,G,F,
    T16FG,FH,FT,FC,FD,FK,FB,FE
    But there are no entires for Release group: 02.
    when i look into EKKO table, purchase order linking automatically to release group 02.
    from which table system pulling this?
    How to solve this problem
    Please suggest
    Thanks
    SUNIL KUMAR

    If these all the POs were created before you delete the release group and created new than system will not take new release group
    you have to put it the old one back and release all the POs which has old release group than you delete the release group
    you can keep the new one so the new POs created based on the new release group
    in sm30 check this both table
    V_T16FG_2 and
    v_T16FG
    should be clear

  • Deletion of Release Group and Code in PO

    Dear Consultant,
    In Purchase order, we have created some release group and code, Unfortunately we deleted some groups Without deleting in Order wise.
    In table level the Release Group is there but in SPRO Release Strategy settings its not there..My consultant advised again you have to create same release group in Release strategy...
    If I create same Release Group which are lying in my T16FC Table..But system throwing this err "An entry already exists with the same key"
    Could you suggest me.
    Regards,
    PRIYA.

    Hi,
    Please go with below mention path: -
    SPRO >> Materials Management >> Purchase Order >> Release Procedure for Purchase Orders >> Define Release Procedure for Purchase Orders >> Release Groups.
    Here check release group is existing, if yes then remove them and click on save button.
    Then try to create new service group.
    Some times we delete release group and create new release group with same description without saving changes.Due to this this type of error is occur.
    Regards,

  • How can I allow the application to line through a field that has been locked after being digitally signed?  We have multiple sections on a form with some fields being proposed information and other in another section having the approved information. once

    How can I allow the application to line through a field that has been locked after being digitally signed?
    We have multiple sections on a form with some fields being proposed information and other in another section having the approved information. once the approved information is entered we line through the proposed field so the data entry clerk won't pick up the wrong information.  However we are receiving an error when attempting to enter data  in the field which we have this edit.  Error property: line through cannot be set because doing so would violate the document permission setting.  any idea how we can get around this issue?

    You can control which fields are locked down after signing by setting up a collection. Then those that are not locked can be changed after signing. If this is not possible, then the line outs must occur prior to signing.

Maybe you are looking for