Release Strategy not triggered in PO

[Former Member]

Hello,

I have configured the Release Strategy for PO in our client system with the characteristics of Company Code & Total Order Value

Reference for both characteristics is taken from CEKKO structure fields, BUKRS & GNETW.

When I create the PO and check or save it, the Release Strategy does not gets determined, instead of my PO having these 2 minimum fields filled in it.

To check the same, I verified the values appearing in CL24N, for each release strategy & also cross checked my release strategy in CL30N.

In CL30N, the my release strategy defined for the PO gets determined correctly.

But in ME21N, the PO does not gets the release strategy determined.

Request you to kindly help & provide solutions in such a case, where i have done all the basic settings & checks done as above.

Thanks for your help and time,

Zafar.

[former_member211279 · Accepted solution]

Also, in case you have deletedsome release strategy, it could lead in inconsistency.

Please, see the instructions of SAP Note 365404:

*****

In tables T16FK, T16FV, T16FS, T16FC and T16FG, there may be entries

from previous Customizing settings (for example, old release groups)

that were indeed deleted from Customizing, but not deleted from the

tables.

   This creates an inconsistency.

To eliminate the inconsistency, proceed as follows:

Make all the deleted release settings in Customizing again, save

them, and then delete them in the following sequence:

1. Delete the release strategies

2. Delete the release indicators

3. Delete the release codes

4. Delete the release group

5. Delete the class (Transaction CL02), if a new one was created for

the new release strategy.

Then use transaction SE16 to check whether the entries in the tables

mentioned above were deleted.

            Execute the report in Customizing (transaction OMGQCK or

OMGSCK) and ensure that the system does not display any red traffic

lights.

Hope it helps.

Thank you & Regards,

Eduardo Junior

[Former Member · Accepted solution]

Hi Eduardo,

Thanks for the details provided above along with the table names & process for checking the release strategies.

As per the same, i executed the report above and found inconsistency (error) in my release strategy for some release group & its strategies, which did not existed and seemed to be have deleted.

So i again created the release strategy & deleted it as per the sequence suggested by you.

Then again after executing the check, i got inconsistencies (warning) in some different release group & release codes, which did not existed, so i created that release group & codes & deleted the same.

So now when i executed the check again, no errors were found this time.

But when i created the PO, again no release strategy was determined.

So I started checking entries in the tables mentioned above & found out that from the above 5 tables, now 4 tables are showing existing values, whereas the table - T16FK - Release Statuses, is showing additional entries for more 11 release groups & its statuses, which does not exists.

So in this case, is the entire release strategy required to be configured again & deleted in the suggested sequence or can i directly remove the entries from the table.

Configuring entire release strategy with only information from one table (release group and release strategy found from T16FK) is difficult, as we are not knowing the release codes / pre-requisites to be maintained in these release strategies.

looking forward for your advise.

[amit_gupta44 · Accepted solution]

Please check whether version management is active or not. If it is active, then check whether the version check box is ticked or not.

Regards

Amit Gupta

[Former Member · Accepted solution]

Hi Amit,

Version Management is active at PR level.

But for PO, the version management is not active in the Plant, which we have configured.

Regards,

Zafar.

[mdsaidur_rahman · Accepted solution]

Dear Eduardo

Thanks for your details helpful answer. I had the similar problem and gone through as you mentioned. Now, in all 5 tables only the new data is available. Also, the "Check Release Strategy" is showing green signal. But still the release tab in header data in not coming while creating PR. Here mentionable that in "PR (ME51N) -> Status Tab -> Requisition Processing State -> 02 Active" is showing. As per I know, if the release strategy is activated then it will show as "03 In Release". Note that Version Management is not activated.

Could you please give a details from where this requisition process state key triggers?

Looking for your advice.

Regards,

Md. Saidur Rahman

[Former Member · Accepted solution]

Dear Eduardo,

Thanks for providing the details in brief.

My issue resolved by following your suggestion.

Regards

Abhishek