Query : P.O. Release Strategy

Hi All,
I have a Question about P.O. Release strategy that:
How does the System differentiate the P.Os for Release approval when we create Pur. Requisitions?
I mean when we create Pur. Requi. with different Amt values(at header level), if the Amt is above the certain Level, then it will goes for P.O. Release Approval as a next step.
So, my Question is: How does it differentiate the P.O. which are for Reelase Approval and which are not for Release approval? Where does it differentiate between these two types of P.O.s after Pur. Requisition creation?
Pl. help me out.
I appreciate for your needful help.
Thanks,
Roopan.

Hi ,
Interestingly , the system check for necessary and sufficient conditions to subject PO or PR for processing through release process. Its done by comparing the values as applicable in release characterisics and release classification with the values in the document.
Once this selection is done , its processed through the release strategy thats applicable.
This logic is same for both PR and PO.
Hope this information helps.
Raghuramam

Similar Messages

Release strategy modification

Hi all,
I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document & 2. Purchasing Group .
Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
Please help! How can I achieve this...
Thanks,
Rajan U

Hi,
As needed, you created one more charterictics CEBAN - CFWRT and included it in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
1. <= 5000 INR
2. > 5000 INR
Craete release group as PO and create two release codes C1 & C2.
Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
Regards,
Biju K

Query on Release strategy and WFL?

Hi Friends
what is the diff bet Release Strategy and WFL
Regards
Emil

By WFL if you are referring to Workflow, then these two are not something you should look for differentiating. Worflow is tool provided by SAP to automate a series of business process activities based on business rules. In case release strategy it helps in automating the whole approval process.
Workflow is used to trigger e-mails to approvers once a purchasing document is subjected to release strategy. It can used to write the approval rules and in what scenario who is the approver, are there multiple approvers etc.

Report for release strategy

Hi,
Is there a report for PR/PO release strategy?
Thanks in advance!

Hey
In that case you must query the tables from release strategies, i suggest to you:
T16FS - to get release group, release strategy, and releases codes.
AUSP / KLART=032 - to get Cost Center or others characteristics.
More detailed information get from tables T16F... C/D/E/G/H/K/L/M/T/V and KSSK.
Cya
Jony

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

PR release strategy at header level

Dear Experts,
I have one query, I have configured a release strategy for purchase request and I have done all necessary settings. However by default the release strategy is getting applied at item level.
Could you please help why it is happening?
Thanks in advance.

Hi,
please activate overall release indicator for PR document type.
SPRO > Materials management> purchasing> purchase requisition> define document types. acitvate overall release indicator for your PR doc type.
Regards
Hari

Why we Maintain the data in Trxn # CL20N / CL24N for Release Strategy ?

Dear All Gurus,
Please resolve my Query , that during maintaining the Release strategy for a P.O , i used to create characteristics for defined values such as plant , currency , doc. type etc, then creating class and assigning these characterstics with this class created.
Now after this i had create Release Group , Release Code and Release Strategy and assigned the Rel. Code with the Rel . Str and in Classification tab i had manually mentioned all those created Characterstics in CT04 and finally saved this Process.
Till now i had not at all made any entry in Trxn # cl20n.
But when i had create a P.O with all the values as same as defined in characteristsc , the Rel Str got triggered succesfully.
My Question is that , what is the use of mainiating data in Trxn # CL20N & CL24N ?
Please clarify my doubt.
Many Thanx in advance.
Rgds
sap11
Edited by: Rajeev Chaturvedi on Jan 20, 2011 5:08 PM

it is just another way to maintain the same thing in the same tables. Classification notspecific to release strategies, materials and batches, vendors and customers can be classified too.
You can do this from withion those objects, or from the central classification menu using the classification transactions.
People here recommending this for production system after you have transported the strategy from developement to production. Becaues classification is master data and cannot be transported the usual way. And many here do not know how this can be done with ALE

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 in credit management

Dear All,
My client, wants to configure credit management in such way as
For some say Rs 20000/- debit, some X shd release the blocked delivery document
and for say rs Rs 50000/- debit, some X and Y shd release the blocked delivery document
I hope I am able to put my query in right perspective.
Kindly advice
Shailesh

Shailesh,
This one is very much possible.
You have to take help from your basis person for releasing these docs through vkm3, vkm4, vkm5.
With the help of BASIS you can restrict release strategy as per herarcy...
You will have to use some logic in Authorisation profile/Role with the help of BASIS..
AWARD PONIS IF U FINDS THIS AS USEFUL....
Regds
MM

BAPI_REQUISITION_DELETE (Clears Release Strategy)

Hi guys,
Hoping you can help with a query. I'm using BAPI_REQUISITION_DELETE to delete a line item off a Stock Transport Requisition. The bapi is clearing the following fields in Table EBAN:
- EBAN-FRGKZ (Release ind.)
- EBAN-FRGZU (Release status )
- EBAN-FRGST (Rel. strategy)
I don't want this to happen as deleting one item from the STR should not clear the release strategy.
Has anyone encountered this before? I can't see an option in the BADI to prevent this from happening.
Many Thanks,
Philip Johannesen

Hi Philip,
we have the same issue.
Which the OSS Note?
Thank you in advance.
Regards

Correction to PO release strategy

Dear All,
We have PO release strategy configured and working fine.
Now there are ammendments happend in the PO release strategy i.e. the value limits are changed also new levels are introduced which will be effectivef fro a particular date.
I want to make changes in the system such that the old strategy will be effective till the specidied date and from the cut off date new strategy will be effective.
Thanks in advance.
Regards
Yogesh Chaudhari

Dear Afshad,
Thanks for your reply.
I have one query.
We have PO version management active. i.e. released PO is changed system should trigger a version and release strategy is re-triggered.
Now If I am changing anything in the PO which is of older date ( i.e. before the new release strategy is active) what will happen to the release strategy.
Regards
Yogesh

Release strategy characteristics

Hello Experts,
I am looking to have a report / query where I can see the characteristics values for a specific Release strategy combination .
It should show Release Strategy , Group , Release code & their respective Chararcteristics .
I have tried table AUSP, CAWN , T16FS but this does make up the required report .
Regards,
Lawrei

Hi Lawrei,
It's not a problem to find a report combining the release group, the strategy and the corresponding values, since all reside in the classification system. CL6BN is one way; another report with the characteristics as columns is CL30N - search without assigning any values in the class that you use for release strategies. The resulting list is presented as an ALV report which gives you the options to add columns - here you can add all the characteristics in separate columns. Don't forget to click the pushbutton "Expand multiple values" if you have such characteristics.
Release codes assigned to strategies are stored in another table, T16FS. You can list it using SE16N, then download both to Excel and make a simple lookup using the release group/strategy combination.
BR
Raf

Release Groups at "Release strategy

Hi,
At "Release strategy with Classification " there are Release Groups.
But at "Release strategy without Classification " are not Groups availbale.
What is the reason for and for what are Release Groups existing ?
Regards
sas

hi,
The release group is the only element which makes a pool/connection/linkage between the class and the release strategy....This is specially applicable for the release strategy with classification...
And then further this group is assigned release codes based on which you release the documents...
You can see and check the above explaination here:
SPRO >> MM >> Purchasing >> PR >> release strategy >> Rel startegy with classification >> check for the "set up procedure with classification"
Hope it answers your query
Regards
Priyanka.P

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Query : P.O. Release Strategy

Similar Messages

Maybe you are looking for