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

[tejyadav]

Firstly Simulate the Release Strategies & Check it showing the Release properly from below Path SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Double Click Release Strategies > Open Strategies & Click on "Release Simulation" & Check,

Secondly check for any Error through Path SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Check Release Strategies > Check the "Red" Indicators if any

[Former Member]

Hi Tej,

Thanks for the process provided above 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 Eduaro.

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.

[JL23]

it should usually be enough to customize the release groups

Then you can access the data from T16FK and delete it prior to deletion of the groups.

[Former Member]

Hello Jurgen,

I have deleted all the additional entries from the table T16FK now (I did this directly from table level, through debugging & deleting additional entries one by one)

Now this table contains only the entries for the release groups, for which the configuration is existing in the system.

But even now, on creation of a new PO, the release strategy does not gets determined.

Please help.

[JL23]

I am strongly against any table modification using the debugger functionality,

(i still wonder why this is still possible in many production systems, and why people are doing this in developement systems as the such changes do not make it to the transports)

this is a violation of security measures

this expresses the unwill to follow SAP procedures

this creates usually follow on problems because people often underestimate the linkage of data in SAP (I see this even at my own collegues who have more than 30 years experience with SAP, about 90% of my maintenenance work is related to misdeveloped Z-programs and -exits and because of such table manipulations)

and it was not given as a recommendation to your question here.

The situation is completely unclear now. We do not know if your current problem is caused by an inconsistecy created by your table manipulations, or if it just caused by incomplete setup of the release strategy at all.

[Former Member]

Hello Jurgen,

I am completely in line with what you are telling.

I really regret, first of all for doing this manipulation myself & then secondly writing about the same on SCN.

Actually i tried all possible things for configuring the release strategy & the same was checked OK as well as tested fine in CL30N. Still it was not getting determined in ME21N.

So after getting the help from all of you & also referring the Note 365604, I found that definitely there is a mismatch in the actual configured release strategies & the entries in the database tables - T16FK, T16FV, T16FS, T16FC and T16FG.

But at the same time it was also made very clear in the Note by SAP that we need to build the missing Release Strategies again, save them & then have to delete them in the correct way so that the table entries get corrected.

I really regret what I have done & hope you forget me for this behaviour.

Also I was able to find resolve the issue.

I found a SAP Note 371667 "Release strategy fails when invoking a user-exit".

Using this note, I found that in our system, in the enhancement M06E0004, for the exit - EXIT_SAPLEBND_002, the include - ZXM06U22 was active, whereas no ABAP code was written in that include.

Hence the Release Strategy Tab was not coming at all in the PO created.

So after applying corrections in that include, as suggested by this Note, the release strategy tab started appearing in the PO & the release strategy defined got correctly determined.

Thanks a lot of all of your help & cooperation !

I again regret for using the debugger & would like to tell all our collegue SCN team members reading this thread, that use of this debugger is extremely dangerous & is not at all recommended by SAP at any cost or under any situation.

Try to follow all the steps as suggested in SAP notes for all your problems & definetely you will find the solution to your problems.

In other cases, you can go ahead & open an OSS with SAP, for them to analyse the issue, rather than touching the database tables, which may have very severe implications, which even a knowledgable person may not be able to anticipate.

Regards,

Zafar.