Stop Re-triggering of PR release strategies for closed PR's.

Hi,
Scenario is like, PR raised and converted it into PO and material has been received.
After Receipt of material, system is allowing to change the quantities by un-releasing the release strategies.
Once material receipt is completed, system should not allow to change in / revoke the release strategies.
Please suggest.
Thanks in advance.
njs

hi
plz check ur release indicator in spro >mm>pur>pr>rel>
here select the rel indicator and check the changability option in bottom it has to be 6
hope it help
regards
kunal

Similar Messages

Purchase Order Release Strategies for Changed Amount

Hi Gurus,
We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
Example: Configuration is PO total amount <$5K requires only L1 approval. PO total amount >$5K requires L1 and L2 approval. PO was created for $8K and was release using L1 and L2 approvals. Receipts were posted to PO in the amount of $7K. Now the buyer has added an additional line item for $1K. The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item). Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
Has anyone done this before? Any ideas??
Thanks,
Gabe

from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
The following user fields are available:
USRC1
USRC2
USRN1
USRN2
In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

T code to get the detail of release strategies for all purchas groups?

Hi,
Is there any T ode that i can run a report and get the current details of release strategies for all purchase groups exist at the moment?
if so pls let me know
or else how can i get that information?
highly appreciate all of your assistance in this regard?
thanks in advance
Regards
Sasika

from T16FS you can only get which strategy are present.
Which strategy you have can already be seen in the PO or requisition.
But you are looking for the person. this is not really easy, as this can be more than one person.
A strategy has the information what release code is needed.
And this release code is in a role which is then assigned to an approver.
So the only way would be to execute SUIM and then roles by authorization values.
there you enter the authorization object M_EINK_FRG (hit enter) then you have to enter the release group and release code.
Execute. SAP will list all roles that grand the authority to release order with this combination.
in this list you can click another button to see the users that are assigned to this role.

Release strategies for purchase requisitions

Hello,
I'm having trouble with profiles and roles for release strategies, this is the scenario:
-for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
Many thanks
Daniel

HI,
Not necessarily, you just need a different strategy for each different combination of release codes involved.
So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
Or however many different variations you have.
Steve B

Delete Release strategies for PO that has been delete

Hii SAP Expert,
I'm facing this problem whereby there are Purchase Order that have been inactive which mean the line item for the Purchase Order have been deleted. The concern is the release strategies still appear in ME29 for PO that have been deleted.
How do i remove this PO from the release strategies ?

Dear Nikamz,
Check to the PO item detail , if the delivery complete indicator and final invoice indicator is ticked, then the release strategy will remain in document although you already delete all the PO line items, try to untick the indicator and then unreset the delete indicator and delete the item again, see whether the release strategy still exist, also you may try to check notes : 527995(run report ZKSTAPO1 to update the STAPO field).
Regards,
w1n

Why release strategies for PO at header level only

We have release strategy for Purchase Requisitions and Purchasing documents like PO, Contract and SA.
In case of PREQ we have a choose for either item level release or header level release, whereas in case of PO, Contract and SA only header level release is possible.
My question is why SAP has provided only the header level Release Strategy for PO, Contract and SA? I wan to know the reason and logic behind this.

Hi,
For PR's, there is no header level data. Becuause vendor number is optional since it is internal document from the user dep. to pur org. That's why, vendor number fields is at item level in the source of supply screen. But this is optional field.
That's why, you can release PR line items one by one or all at a time.
If you are releasing all line items at a time, need header level release.
If you release line item by line item, need item level release.
But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
That's vendor number is at header level field and line item in the PO are related to the single vendor.
That's why u cann't release line item by item, i.e., item level release.
You can relase all the items in the PO or u can reject entire PO, not a single line item.
That's why, only header level release is possible for the PO/Contract/SA.
Regards
KRK

Release Strategies for PR with Characteristics Account assignment

Dear All,
Please let me know how to set rel.strategy for PR with Account assignment as a characteristics.
I tried with Account assignment and Document type as a characteristics but Rel.stst is not triggering.
Please help.
Thank you
regards
Amar

Hi,
I have created Charac A/c assigment with fied name KNTTP ,maintained the vaue as A and also assined to class. And other characteristics used are plant and docment type.
But REL STAT is not triggering.
Please suggest some input.
Thanks in advance
Amar

PR Release Strategies - Different characteristics

Hi All,
I want to set up PR release so that the strategy of some release groups is triggered by username/item value, and the strategy of other release groups are triggered by cost center/item value. I know there can be only one class per release category (item or overall), so I have all three characteristics in the class.
The class is Z_PR. The three characteristics are Z_GSWRT, Z_ERNAM, and Z_KOSTL. I've tried setting up release groups U1 and U2 for the usernames determination, and C1 and C2 for the cost center determination. So the release strategies for U1/U2 will have values for usernames, and the C1/C2 strategies will have values for cost centers. I tried leaving the cost center fields blank for U1/U2, and vice versa, but the strategies do not pick up in the PR.
Does anyone know if this is possible to achieve, and if so, what values should I put in the strategies?
Thanks,
J

your release strategy will not work becuase you have used three char in release and when you define the release strategy for username you are leaving the cost center blank
and when you define for cost center you are leaving the user name blank
now when you create the reqs for account assigned that time you populate cost center and your release have no blank value for user but in the PR there is a user name so it willnot work
same way for reg PR you are leaving cost center blank but there is no cost center for this PR
the bottome line is
even though you leave it the char value blank means system is looking for that filed with blank value and if you dont have that perticular field on the req than it will not work.
you have to think about some other solution for this kind of requirements.
Instead of cost center add the char as accoutn assignment category so for cosr center req will have A/C K and reg PR will have blank and it will work for both
but if you need for particular cost center based than it will not work
or else send us your complete bussiness requirements

Why can we only use 1 release class for overall Release of Purchase Req?

Hi,
After realizing that it would be beneficial to use more than one release class for overall release of Purchase Requisition with classification, in use with release groups for overall release, I now ask if someone knows why SAP has chosen to only allow 1 release class for overall release of Purchase Requisition?
In my scenario I would like Release group US, used for release strategies for US-plant to be able to use 1 release class with a specific set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_USD including a characteristic PR_TOTVAL_USD looking at CEBAN-GFWRT. The chosen currency for this characteristic would be USD.
I would then like to allow Release group FR, used for release strategies for FRANCE-plant to use another release class with another set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_EUR including a characteristic PR_TOTVAL_EUR looking at CEBAN-GFWRT. The chosen currency for this characteristic would be EUR.
In this way the release strategies for the respective release groups US and FR, could maintain their overall limit values in their respective release strategies in their own currencies.
1. Observe that I do not want to use the same Release class for both release groups for overall release, even though I know that this is currently the only allowed option, as far as I've understood.
2. Observe that I do not want to specify the two characteristics PR_TOTVAL_USD and PR_TOTVAL_EUR for overall value in the same release class, as this would lead to double maintenance for a large number of release strategies. Also consider the maintenance when new countries with new currencies want release strategies.
3. Observe that I only want to use overall release.
What I'm trying to avoid is having to continuously translate local business USD overall value limits to limits in the currency chosen for the overall value characteristic. If this for example is specified in DKK, this would lead to a need to adjust the overall value limits as soon as the exchange rate between USD and DKK changes in the system.
Please consider this simple example:
Local requirement is that USD purchase requisitions should be blocked when the USD value is above 1000 USD. However in my release strategy I would have to maintain a value of >5365 DDK, if DKK is chosen as the currency for overall characteristic.(e.g exchange rate 5,365).
Next month the currency exchange rate in the system between USD and DKK has changed, and therefore I would have to go into CL24N and maintain the value to reflect the new exchange rate between USD and DKK. Lets say it has gone up to 5,435. I would now have to maintain a value of > 5435 DKK in my release strategy to correctly reflect the local business requirement of 1000 USD.
So if anyone could please explain why SAP has taken the decision to make the Release class for overall release client specific that would be much appreciated and awarded accordingly. Also if you have any suggestion on how I could obtain the above scenario on maintaning overall value limits in different currencies than that would be awarded to.
BR Jakob F. Skott

You can give feed back to Apple from the iTunes drop-down menu in the iTunes menu bar..
You can also contact the iTS Customer Service from the links on this page - http://www.apple.com/support/itunes/store/
MJ

Are these requisition release strategies common?

All,
I’m designing new requisition release strategies for indirect requisitions at a chemical industry client. I’d like to know how often you have seen the following sorts of design before:
Existing design: Item-based release with workflow, with three dollar levels. At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic). Characteristics assign several cost centers to each approver. Strategies and codes are named for users, so we change configuration whenever someone changes jobs. The codes are linked to positions, which are attached to user IDs. Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic. A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase. I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
Thanks for your help!

Hi,
No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
For more refer a discussion:
PR release: place holder for Cost center and Material grp
NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
You can also go for other concept designing of your Requisition release strategies
Regards,
Biju K

Release strategy for Return PO

Hi,
Can we create Release strategy for Return PO's. ?
Regards
Sunil

Hi,
The process for return PO is:
Process:
- Create a return PO
- Create a outbound delivery
- Goods issue
Release Strategy can be created for All Document Types as Document Types being one of the determining factors for Release strategies. So under Classification data Characteristics which we maintain determine the release strategies for a Particular Purchasing documents. Actually it depends on your Business case that for what all documents you want to have a release strategy config.
regards,
Prashant Rathore.

Release Strategy for reservation created from PM and PS

Dear All,
How to configure the release strategy for reservation generated from PM and PS.
Regards,
Atanu

do you talk about release strategie for requisitions, or really reservations?

Release Strategies::::Urgent

Dear All,
I am creating release strategies for PR...
I have created a Release Group "01"
Release Code GM & PM
Release Strategy R1
but when i check the strategy...it gives error sayin...."Release Code for release group is inconsistent"
Cheers

Hi,
I think you have Release group--01
Release code combination is 01--GM
01--PM
Then you are creating the new Release strategy R1
here you are entering the Release group 01 and Release strategy R1
But in the release codes did you entering the same GM & PM or any other release codes.
Unless you maintain the combination of Release group & Release codes and if you are entering different Release codes in Release strategy system will not take and shows the inconsistencies.
Check the Release codes in R1 release strategy.
rgds
Chidanand

Release Strategy for Contract

Hello Experts
I am using release starategy for contract and using communication structure CEKKO in characteristics. I want to use other parameter such as material master number (MATNR) for characteristics. I see that CEKKO has component .INCLUDE (Communication Structure: PO release for User Exit). Does any one know how to use it in characteristics and if I use it can I design release strategy for particular materials?
Thanks
Ankit

this has been discussed multiple times on this forum - "Release strategy at item level for purchasing docs - PO/SA/Contract" not possible...
refer below threads
Why release strategies for PO at header level only
PO Release Strategy
Release strategy - item level
yogesh

Release Strategy for STO

Hello Experts,
We have a requirement to configure release procedure for STO scenario. Release procedure needs to be captured in STO PO's.
We have 6 plants - A,B,C,D,E,F, and each plant is having different approving authority individually.
When STO PO is created, it has to be approved by Issuing plant authority & receiving plant authority as well. The major concern here is for eg., approval authority for plant A can be a issuing authority at one instance & receiving authority at another instance.
How to configure release strategy for this.
We believe ,creating those many release strategies for all the combinations of plants will be a hectic task & still it'll multiply with the introduction of more number of plants.
Hence looking for a more simpler & feasible workaround/solution.
Regards
Mahesh.C.R

Hi,
you can use Supplying plant ( RESWK) and issuing plant (werks) both as characteristic and with these combination you can configue release strategy.
Or you can use User field format character for release strategy (USRC1)as per your requirement.
YB

Stop Re-triggering of PR release strategies for closed PR's.

Similar Messages

Maybe you are looking for