New Release Strategy in case of PO amendment

[Former Member]

Dear All,

We have the release strategy at PO level on 3 parameters,

Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.

When ever users edit the PO, again system sets the release strategy as per above logic.

Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".

Can any one send me a user manual and steps for this.

Thanks in advance,.

Vikas

[Former Member · Accepted solution]

Hi,

You can set a control within Config. there is a parameter called as release indicator.

Follow this IMG path:

SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator

1 Cannot be changed

2 Changeable, no new determination of strategy

3 Changeable, new release in case of new strategy

4 Changeable, new release in case of new strat. or val. change

5 Changeable, new release if new strategy/outputted

6 Changeable, new rel. if new strat. or value change/outputted

Changeable, new release in case of new strategy

Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.

Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.

So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.

Hope this explanation was clear.

Prashant Rathore.

[Former Member · Accepted solution]

Thanks for your points.

YOu mean to say, version is nothiing to do with ??.But the question is how we can assign a new release strategy ??

Thanks in advance,

Vikas

[Former Member · Accepted solution]

In addition to that, release strategy is not getting trigeered based on the release indicator...

Release strategy is getting triggered based on the "characteristics" we maintain for for "Class"

Thanks,

Vikas

[former_member824495 · Accepted solution]

Hi,

Release strategy gets triggered as per your characteristics. Release indicator specifies whether you can make changes or not in PO once it is released.

Version management - When you make changes in print releavant field once it is outputted/printed, then version managemnet gets activated. You need to activate it at document type, document category & purchasing organization level.

Regards,

Piyush

[Former Member · Accepted solution]

Hi,

Here requirement is, we want to change the PO after release, and when ever PO gets edited either in Qty or in Prices and new release strategy should trigeer and this new strategy will not same what was trigeered earlier.

I hope , i am albe to explain our requirement.

Thanks,

Vikas

[former_member824495 · Accepted solution]

In release indicator, maintain changeable indicator '6' i.e. new release in case of any changes.

Hope it helps you.

Regards,

Piyush

[Former Member · Accepted solution]

Hi,

New Release Strategy triggers only when you make any changes to the Values like :

1.) value

2.) Quantity

3.) Characteristics (Like valuecan be one char, document type, purchasing group, Plant etc.)

So whatevery i mentioned earlier (regarding changeability)will help you to retrigger the release strategy, but if you make a considerable change in values like characteristics then NEW Release strategy will be triggered.

Changeability will only reset the release i.e. if PO is released it will reset the release.

Hope this clarifies.

[Former Member · Accepted solution]

Hi,

Now, the version tab is appearing in the PO but release strategy tab got disappeared.

Our requirement is as follows:-

Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"

now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases

Price-A can be equal to Price- B, Less than or greated than.

Thanks,

Vikas Rander.

[Former Member · Accepted solution]

Hi,

Check if you did not missed on maintaining characteristics correctly. Also check release prerequisited are correctly maintained. To check if release strategy is working fine--> check under release simulation.

There could be a possibility that you might be missing some step or you have not maintained the enteries correctly for Characteristics in CL24N.

Prashant Rathore.

[Former Member · Accepted solution]

All the things are working ok.

Any other suggestion.

Thanks in advance,

Vikas

[susheel_tiwari2]

Hello Vikas,

Outputted means print has been taken via ME9F Tcode and NAST table is updated.

in Cl20N, Version value should be given like '00000001' for version1,'00000002' for version 2 and like wise continue for all version.

Also ensure that there should be separate release strategy for each version and all field should be print/version relevant to traigger new version.

I have implemented same and it is working fine. so if you find any issue, please let me know

Thanks

Susheel

[Former Member]

This message was moderated.

[susheel_tiwari2]

Hi,

If Release Strategy is needed for every changes, this is only possible through Version Management as Release strategy is only triggered if either PO value is incremented or change value is falling in another ranges which must exist.

For version, actiavate all field which is required for version. Add Version field in CEKKO.

In CL20N, maintain the value for Version as it is done for CHAR. So version should be upto 8 character and is filled with leading zero.

Also Separate Release strategy will have to be maintained for each version and condition records will have to be maintained for each version.

Also new version will only trigger when message is outputted so once PO is released but not outputted and if users make any changes, no RS will trigger as no new version will be created.

So you will have to apply BADI ME_PROCESS_PO_CUST and code in check that if NAST status is not printed, no changes allowed.

hope this will resolve your issue....

[Former Member]

I wil check this BADI ...

Outputted means, talking the printout of the PO... Please correct me if am wrong.

Thanks,

Vikas

[Former Member]

Hello,

I think i am making mistake in filling the value in verison characteristics. Please advise how to put the data for versuon with leading zeros.

Quote

"In CL20N, maintain the value for Version as it is done for CHAR. So version should be upto 8 character and is filled with leading zero."

Unquote.

Thanks,

Vikas Rander.

[former_member210560]

Dear Vikas,

You need to fill in the leading zeros in your classification value if you use REVNO as classification

based on CHAR length.

Best Regards,

ian Wong Loke Foong