Release Strategy in MM PO document

Hi,
Could you please any one can clear my doubt in Release Procedure for P.O/PR. I can configure release procedure two level based on value.
Now my doubt is where these two different users going to get their authority. Is it through Parameter ID using T.code SU01. If so What is the parameter ID (FGB, FGE, FGR, BFC, FAB) and Value I need to maintain for this user.
Kind Regards,
Sankar.K

Sankar,
For PO releases, the release codes are assined to users in role maintenance (PFCG). So, one user can perform release by using code, which assigned to his role.
regards
sairam akundi

Similar Messages

Release Strategy in purchase order document type

Hi Gurus..
I'm tring to tweak the single RS in the system.
I've set the charcteristic using table CEKKO field BSART, restriction 032, I've set two document types as the Characteristic Value (ZLOG - ZADM). Then I´ve set the class with this characteristic, Created Release Groups & linked to class , Created Release Codes, Release Indicator, and Set up strategies
.. but It doesn´t pick any release strategy.
The funny thing is if I delete the document types values entered in CL20N it works for all doc typs, but if I set the docs types that it should take to pick the RS it doesn't work at all...
Please advice..

I´m not such a abapper but I guess there is not values taken to ekko, does it ring a bell?
                                        BUKRS
                                        BSTYP
                                        BSART
                                        BSAKZ
                                        LIFNR
                                        SPRAS
                                        EKORG
                                        EKGRP
                                        WAERS
                                        BEDAT                                             00000000
                                        LLIEF
                                        KUNNR
                                        RESWK
                                        LBLIF
                                        INCO1
                                        KTWRT                                             0.00
                                        LIFRE
                                        WERKS
                                        MATKL
                                        LTSNR
                                        USRC1
                                        USRC2
                                        USRN1                                             0000000000
                                        USRN2                                             0000000000
                                        GNETW                                             0.00
                                        SUBMI
                                        MEMORY
                                        KONNR
                                        REVNO
                                        PDUMMY
                                        KDATB                                             00000000
                                        KDATE                                             00000000
                                        EBELN

Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

Hi Friends,
I have a issue to fix. The issue is releated to PR.
There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
I have to retrigger the release strategy for all the affected PR's.
The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
Regards,
Manjunath K

Hi,
Refer the discussion to triggers release again on release code addition/change in release strategy.
release code is changed on PR release strategy - old PR can´t be approved
Regards,
Biju K

How to configure release strategy in case of document parking ?

Hi experts,
I have a requirement wherein i have to create a workflow with four level approval when a document is parked before it can be posted.
The approval is by company code,reacon code and the amount .For example for a particular reason code for particular amount one person has to approve,if the amount is greater then 2 people have to approve, so on.
Is it possible to configure such a release strategy in SPRO ?
Kindly help,
thanks in advance,
regards
Ashwin

If it are FI Invoice you're talking about, it's possible.
Do you have access to the best practices of Public sector management ? There's an example on how to implement an FI workflow.
If not, check workflows on the object FIPP

PR overall release strategy (with shared PR document types)

We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know, this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

Hi ,
The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
The Plant can be taken as one of the characteristic.
The view CEBAN gives all the related views.
check the below LInk for Futher information on the same.
http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
hope so it helps
Regards
Anjanna.

Release strategy:ME53N : Older PR documents shows, modified PR rel.strategy

Hi Friends
We have updated the sequence of release codes for certain PR release strategies. But when we moved the changes production, i observe that all the older PR documents (Which were released last year and completed) also shows the updated release strategy in transaction ME52N/ME53N.
Can someone pls some explain? Is this normal?
SAP doesnt store the release strategy and its sequence of release codes, which were determined at the time of document creation?
Thanks for your help...Raj

Hi,
There is no change in the older documents.
The documents are older by few years.
I have checked few documents randomly, the tcode ME53N shows only the updated release strategy.
I did some investigation today on this.
i think system will not keep the release strategy pertaining to document creation.
It will just store Release Group and Release strategy in the Purchase Requisition tables (like EBAN).
And when ever we try to display the document it will go and read the release strategy sequence from relevant tables.
Hope someone helps to validate if my investigation is correct.
Good day..

Add release strategy in the PO document type

Dear all,
I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type.
Thanks
Pauline

Pauline,
I would suggest you to please post this query in ERP MM forum to get it answered asap.
Regards,
Faisal

Release strategy behavior for purchase documents

Hi all,
I'm working at a company that recentily has implanted SAP. We noticed last week that the approved documents, like PR, PO, RFQ etc.. can be modified by the users and that documents doesn't modify its approval status, I mean, they remains approved.
I'd like to know if is there any standard way to configure the SAP to not allow any modification in an approved document, or if an approved document has been modified, it resets its approval status to pending approval again.
Thanks in advanced,
Rodrigo

Rodrigo wrote:
> I'd like to know if is there any standard way to configure the SAP to not allow any modification in an approved document,
For this, Use OLME -> Purchasing -> Purchase Order -> Release Procedure for Purchase Order --> Define Release Procedure for Purchase Orders -> Release Indicator chose the last level for Changeability as "1 Cannot be changed"
Rodrigo wrote:
> if an approved document has been modified, it resets its approval status to pending approval again.
For this, Use OLME -> Purchasing -> Purchase Order -> Release Procedure for Purchase Order --> Define Release Procedure for Purchase Orders -> Release Indicator chose the last level for Changeability as "4 Changeable, new release in case of new strat. or val. change"

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

Why PO is automatically assigned with release strategy?

I created a PO with PO document type NB and NB is not assigned with any release strategy.
But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO. Why?
And only when the PO is in held status, there is no release strategy assigned to NB PO.
Is the normal ERP behavior?
I only assigned a release strategy to PO document type DB, which means dummy document type.

Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

Release Strategy in PO for direct materials not driven by MRP

We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
Request you to let me know how I can make this work.
I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
Thanks and Regards
Murali

Hi Murali,
Standard SAP provides PO release strategy at header level only and not at item level.
So you can create a new PO document type and allow use of only this document type for manual PO creation.
Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
Hope this will fulfill your requirements.
-Ravi

No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

Release Strategy @ Company Code Level

Hi Guys:
We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
with Characteristics as Company Code ,PO Document Type and PO Value?
Thanks
Sweth

Hi
For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
The characteristics for release strategy for external purchasing documents are
Plant                - WERKS
Pur.group        - EKGRP
Pur.org            -EKORG
Acc.assignment category-KNTTP
Document value-GNETW
Document type-BSART
The table is CEKKO
Thanks

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...

Wrong Release strategy in purchase order

Hi,
I have a specific purchase order with wrong release strategy.
I had been creating others documents with the same total value and the release strategy work correctly.
The release strategy configuration are right.
How I can correct the release strategy in a specific document?
Thanks.
Best Regards.

Hi,
The release strtegy is basically conssitss of Different type of characters.
What characters you are highlighting plays in release strategy.
First you comapre the characters you mentioned in two purchase orders,
eg: p.org, Pur Grp, Value,------
o to bith release strategies and compre the things or characters you mentioned Release strategy and found wher you missed to get the required Strategy.
SPRO>>MM>>Purchase order>>Release Procedure for Purchase Orders>>Define Release Procedure for Purchase Orders>>Click on release strategies
Select your release strategy and go to Classification , here you chck the parameters in both release strategies and compare with your purchase orders.
Regards,
Andra.

Release Strategy in MM PO document

Similar Messages

Maybe you are looking for