Release tab at release PO indicator

Hi Guys,
I'm wondering what is the purpose of release tab (tick / untick) at release PO indicator?
Thx in advance

Hi,
The release tab in purchasing documents shows if the document is subject to release strategy and needs to be approved before any follow on documents can be created (PO, goods receipt, invoice).  So it may be the case where ther is a 3 level hierarchy for the pucase document to be released. so for example manager 1, manager 2, manager 3.  If there is a green tick set for these release codes then the document has been approved by manager 1, manager 2 ,manager 3.
All release strategy setup is set in customising.  The release indicator can be set in customising for the release code. So for example in this case you can set it that until all the managers approve the document the document is blocked for further processing. When released by all release codes (manager 1, manager 2, manager 3) then the document can be set for release and follow on documents can be created.
Kind regards,
Lorraine

Similar Messages

  • MEPO822:Release tab is occuring in PR

    Hi Friends,
    I am not getting the release tab in PR at item level. I am getting the error MEPO822 while changing the PR in ME52N T-code.
    Please guide me for getting the release tab in PR.
    Krishan

    Hi,
    Please check your release strategy with below detail.
    Business Process: -
    Purchase requisition is creating PPA person than PPA head release this purchase requisition.
    Process of Release Strategy: -
    Procedure with Classification: -
    Edit Characteristics: -
    For implement release strategy for purchase requisition you have to create Characteristics u2013 CT04.
    For Example: -
    Suppose you want to create release strategy for purchase requisition document type wise. So you create characteristics for purchase requisition document type with CT04 u2013 document_type.
    Edit Classes: -
    After creation of characteristics, Create Class u2013 CL01 for release strategy of purchase requisition.
    For Example: -
    Create class for purchase requisition like: Release_PR
    Set Up Procedure with Classification: -
    In this node you can maintain following details.
    Release Group
    Release Codes
    Release Indicator
    Release Strategies
    Now we see above details in briefly
    Release Group: -
    You can maintain release group in this node. This permits the multiple usage of the same release strategy key
    For example: - Create 01 u2013 Release Group for purchase requisition release strategy and assign your class of release strategy.
    Release Codes: -
    You can maintain release code against release group with this node.
    For example: - Create release code 01 u2013 PPA Head against release group 01 u2013 release group.
    Release Indicator: -
    You can create release indicator with this node, like blocked, in process, Release.
    For example: - Create two indicators, Like X u2013 Blocked, 9 u2013 Release.
    Release Strategy: -
    After click on this node you can see four different step for release strategy of purchase requisition.
    Release prerequisites, Release status, Classification, Release simulation.
    First off all maintain your release code in Release code tab. Than done some bellow settings.
    Release prerequisites: -
    Click on release prerequisites tab, change your required changes and click on continue button.
    Release Status: -
    In this node you can set your path of release strategy.
    For example: - you want to create release strategy like when PPA head tick on release indicator at that time purchase requisition made release. So you can set it via release status.
    Classification: -
    In this node you have to enter value of characteristics.
    For example: - enter NB u2013 standard pr for document_type.
    Note: - Before enter value in Classification, You have to maintain value in characteristics u2013 CT04 in value tab.
    Release simulation: -
    Check release simulation for release strategy.
    After done this process, Create purchase requisition for document type NB u2013 Standard PR.
    At the time of check release strategy will be implemented in your purchase requisition.
    You can release it via ME54N. List of purchase requisition release with ME55.
    Regards,
    Mahesh R.

  • Release Tab in purchase order disappear after release using ME29n

    Hi there,
    We are busy testing support stacks (upgrading from ECC6 SAP_APPL SAPKH60305 to SAPKH60307)and we've come accross a strange problem.  When we create a normal purchase order (ME21n) the purchase order does pick up a release strategy.  Using the older ME28 transaction to release this purchase order, everything is fine.  We can use ME28 to release the purchase order, as well as unreleasing the purchase order, as often as we want (the same purchase order).  When we use transaction ME29n the release tab in the purchase order just simply disappears after saving.  In the purchase order header changes, the release change is visible, but the release tab is missing.  This purchase order is now not subject for release, and a goods receipt is possible without release.  I checked in table EKKO as well and the release fields in this table for this purchase order is empty.
    Has anybody had a similar experience?  Any advise would be greatly appreciated.
    Regards
    Christo Vermeulen

    Hi Christo Vermeulen,
    I have detected the same problem as reported by you. Did you solve it? Do you know how can I procedure to solve it?
    Thanks in advanced,
    Eder Nicoleti

  • How can i block PO adopt from PR with no release tab

    Dear Experts,
    I need to block PO creation ( by adoptation of PR) from PR which has no release tab active. Kindly help me how can i do this.
    From unreleased PR , PO can not be created and it is standard SAP function. But if PR has no release tab then PO can be created from that PR and no error or warning is there. But i need to block PO creaation from the PR which as no released tab active.
    Please help.
    Kind regards,
    Zusen

    Hi Zusen,
    Would not be good idea to place those PRs in release strategy? In this way PO(s) will not be created until PR(s) is released. Have a look at release strategy of PR under the path; IMG-Materials Management-Purchasing-Purchase Requisition-Release Procedure
    Otherwise you have to develop some coding. You can use BADI: ME_PROCESS_PO in order to control unreleased PR. If EBAN-FRGRL is NULL in PO then you can place an error message as you want.
    Kind regards

  • Broken PCI card release tab question

    Ordered and received the ATI 4870 video card upgrade from Apple and read the included instructions. In lifting up the plastic card release tab at the end of the PCI express slot to release the ATI 2600 video card the plastic tab broke off and fell down into the machine. I was able to remove the old card and install the new one without other problems. The new card seems to be working well.
    Should I be concerned about this broken release tab and the plastic piece which has fallen who knows where? I have Apple care on the Mac Pro and there is an Apple store in the area.

    Apple will probably not cover it since you broke it. There should be no problem using it without the plastic latch, but if you ship the Mac Pro, make sure the card is pushed all the way in before connecting power.

  • PO Release TAB not trigered in Purchase Order

    Dear all,
    We have created a Release strategy in our test system.Its works fine.But when we create the same in our clients development
    system the "Release Strategy "Tab is not triggered in Purchase order.We did the following steps while creation
    1) Created new characteristics and class and when we had assigned it to new user group system gives following error
        "Please check release classes (see long text) Message no. ME492".....
    2) So we used the existing class in clients system and assigned new required values in characteristics (Plant,Purch.Org,
       Company code,total net order value,Purch.Group).
    3) In classification tab we get all the required value and no problem to release strategy.In "CHECK RELEASE STRATEGIES"
         system shows green signal for Release code and release strategy..
    Kindly suggest were we went wrong????
    Regards
    Sachin

    Hi,
    You should use only release class for PO.Hope one release class assigned to release group(TR transported to dev-client) & now you created another  release class and want to assign to release group, so you are getting the error. Now create same release class  which assigned to release group & design release strategy and you will have release TAB in PO.
    Note:Better to keep one release class always for purchasing documents....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.
    Regards,
    Biju K

  • Release Tab getting deactivated when changing SRM GOA

    Hi,
    I have created GOA long back.I have also have release PO`s against that GOA. But now when I am trying to change any item level data like condtion or any other data and try to release it that time release tab gets gryed out.
    Does any one faced this issue in past...if so then please let me know the probable reason.
    Regards.

    Hi Navneet,
    The release button gets grayed out usually when the contract have some errors.
    It could be some problem related to your target value or target quantity. As per my understanding the target quanity/value at the header level always should be more than the release quantity at the line item level.
    Also please check the note numbers: 863656, 1082548
    which deals with similar issues.
    Please award points if the answer was usefull.
    Thanks & Best Regards
    Raj

  • EXIT_SAPLEBND_004 lets release tab disappear on PR

    Hi, Gurus,
    I created an enhancement project ZMM_005 throught CMOD,It was assigned with M06B0005.
    After activating it, I found that release tab disappeared from PR screen.
    (In my R/3 system, PR release was set into overall release.)
    After I entered PR number and release code on ME54, SAP gave the error message "Purchase requisition not subject to a release strategy".
    It's why?
    Please give me some suggestion.
    Edited by: Mic chen on Feb 15, 2010 9:20 AM

    Thanks very much.
    I found the solution(SAP Note 371667).
    Edited by: Mic chen on Feb 15, 2010 10:48 AM

  • Stack file is invalid: 'SEM-BW' (stack release 600 source release 602)

    Hi experts,
    I encountered the following error while patching my BCS SEM system using EHPi.
    Servere error(s) occured in phase PREP_EXTENSION/EHP_INCLUSION!
    Last error code set: Stack file is invalid: component 'SEM-BW' (stack release 600 < source release 602)
    The BCS SEM system is currently installed with SEM-BW 602. But the xml stack file generated by solution manager contains SEM-BW 600. From SMSY, under the Software Components tab, the release for software component SEM-BW is 602.
    Where does solution manager obtain the data when calculating the xml stack? How can I generate a xml stack with SEM-BW release 602?
    Thanks,
    Tzyy Ming

    Hi.
    When installing this system you have used an installation guide. If i were you i would try to configure the system described in the guide. SAP note 852447 talks about an IInstallation SEM-BW 600 on SAP NW 2004s AS ABAP;
    So why not try to configure this system as netweaver as abap in smsy and add the add-ons as relevant. But i am not completely sure - i am at home and can not look to our SolMan system.
    I do not think that the configured system should be the problem. You said, the smsy contains the correct data. Did you refresh the product data in your solution manager. That could be the reason why the queue ist not calculated correct ly.
    regards,
    Martin

  • Release code and Release group

    Hi All,
    where we find PR release roles with release code and release group combination. Is there any table to identify with this combination?
    Thanks in Advance
    Suresh

    Hi Suresh,
    Here is the list  of various tables in release procedure,
    Tables in Release strategy:
    T16FG - Release Groups
    T16FC - Release Codes
    T16FB - Release Indicator: Purchasing documents
    T161S - Release Indicator, Purchase Requisition
    T16FE - Description of Release Indicators: Purchasing Documents
    T16FS - Release Strategies
    T16FV - Release Prerequisites
    T16FK - Release StatusesTable: V_161S
    Vivek

  • Release Purchase Requisition - "Release strategy"

    Hi there,
    I am trying to release a purchase requisition. I looked in the table "EBAN" and i can see the entry or in other words, the requisition i created. In the Release indicator, Release status and Release strategy fields, these are empty. How do i add information to these fields which appear to have missing data?
    Speedy repsponse would be very much appreciated.
    Thanks
    Motolani Fatuga

    Hi Motolani
    spro>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release strategy
    Select release strategy> Go to details>classification
    here check what are the charactaristic and what are the values maintained for it
    Check this for all release strategy
    Mostly PR release strategy is based on Document type and PR Value
    Check whether UR PR fits in release strategy criteria
    Suppose Total value of requisition is maintained as 1000-2000
    If UR PR value is less than 1000 Then PR will not subject to release
    Vishal...

  • Find sap user id from release code and release group

    does anyone know any FM that can get sap user id from certain release code and release group?
    ex: if i input rel code 40, rel group N1 , then it should be sap user id A
    i would prefer FM rather than tables and tcode.

    Hello,
    Please find attached list of tables
    T16FB                          Release Indicator: Purchasing Document
    T16FC                          Release Codes
    T16FD                          Description of Release Codes
    T16FE                          Descriptions of Release Indicators: Purcha
    T16FG                          Release Groups
    T16FH                          Descriptions of Release Groups
    T16FK                          Release Statuses
    T16FL                          Release Indicators: Service Entry Sheet
    T16FM                          Descriptions of Release Indicators for Ser
    T16FS                          Release Strategies
    T16FT                          Descriptions of Release Strategies
    T16FV                          Release Prerequisites
    T16FW                          Assignment of Role to Release Code
    Thanks & Regards,
    Mihir Popat

  • BUS2012 releaser RELEASE - BAPI_PO_RELEASE, saving releaser

    Hi all,
    I know, this kind of topic was already processed a couple of times, however I did not find a suitable solution for our problem.
    Customer wants to be able to save (and report later) releasers of the PO. There is a new processed being implemented, which uses the (slightly modified) BUS2012 object and it's RELEASE method to release the step of the PO in the workflow. Now this calls BAPI BAPI_PO_RELEASE, but it's interface does not incorporate the RELEASER.
    We can't use change documents for this purpose, as, from workflow-orientated releases there will only be WF-BATCH users releasing everything. We would be able to find the place, where CDHEAD and CDPOS are filled, but however this could be not only one place and the added value would be very low, as customer wants a transparent reporting on who and when did which release. For this purpose we enhanced the EKKO table with 16 fields (combinations of uname + date), which will serve the purpose of saving releaser / date of release for every step.
    We can get the actual agent of the workflow, but I do not know how to pass him / her to the BAPI. Of course we can redefine the RELEASE method (and we also will have to), but whatever I put to a e.g. Z_BAPI_PO_RELEASE, will need to be accessed somewhere deeper (maybe in FM ME_REL_SET, maybe in  ME_PURCHASE_DOCUMENT_DATA_SAVE)...
    I believe this was already solved by somebody and we do have something like a best-practise to work with it. Can anybody guide me? Of course, the whole process should be ready to accept releases also from ME29N, should also be implemented for the cancellation of the release and for rejection. But this first step would be a good kick for me.
    Thanks in advance.

    I can give you one option:
    define a new 'release' method, still calling the BAPI_PO_RELEASE but define it as dialog not background
    place the task calling the new method directly after the decision task , transfer the WI_actual_agent of the decision task as the executing agent of the new task. 
    This way the BAPI_PO_RELEASE will be executed with the RELEASER user and not WF-BACTH.
    however, this solution has a few limitations:
    this will work only in SAP GUI
    the user will need to have authorizations to release the PO.
    But, I have created many reports simply reading the workflow logs, this is not more complected then the change documents logs. you can use function modules:
    SAP_WAPI_READ_CONTAINER
    SAP_WAPI_DECISION_READ
    SAP_WAPI_WORKITEMS_TO_OBJECT
    And the logs themselves can be much clearer to the user then the change documents release status has changed from XXX to XXXX logs.

  • Release date and release no of Scheduling Agreement

    Hi All,
    I have a problem with Scheduling agreement.
    I have created a scheduling agreement with long validity period.
    I maintained delivery schedules within that validity period.
    I have generated forecast schedules. then using ME84, creating a releases.
    the problem is occurs here.
    it was not updating the release no and release date for the schedule line.
    still it is showing a *yellow light* .
    where is the problem and why it was not updating.
    and can u please explain the process and significance of those lights.
    Thanks in Advance.
    Regards
    Kishore

    Verify the table T161M has the values
    kvewe = 'B'
    kappl = 'EL'
    druvo = 1
    kschl = LHPA
    as mentioned in the code.
    The solution is add in SPAD the

  • Release strategy for Release POs

    Hi Every one,
    We have a requirement.
    A contract is created and approved as per the regular strategy.
    The releases (POs) are created against it and sent directly to the vendor.
    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
    But the business wants the PO releases too to follow the release strategy.
    Can you please look in to this and let me what changes we need to make this happen.
    Regards
    Pavan

    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
    This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
    As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
    So that the Release Process is applicable to PO's created w.r.to Contract also..
    For ex: if you use the field purchase Doc category as a Character  in  the Release , it differentiates whether it is PO or Contract..
    So that you can define different Release Strategy for PO & Contract
    Or  if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
    then the release strategy applies to PO also..

Maybe you are looking for