Error relate to PO Release Strategy

[Former Member]

Hi expert,

I have a problem relate to PO release strategy. I try some of suggestions but nothing work. I hope you guy can help me to fix it.

I have finished configuring PO Release Strategy and Release Group is ZT with 2 release code (01, 02).

After that i created some of other release groups and delete the first release group ZT (include release strategy). But whenever when i go to ME29N, ZT always appear in release group with it's release strategy even i already deleted it.

Thanks for your help

[Former Member · Accepted solution]

Please check T16FG table if the release group still exist there. If yes , then some inconsistency is there is the system.

Regards

SayanPal

[Former Member · Accepted solution]

I did something like your suggestion. Go to data browse, put the "table" , f8 and nothing display. That mean this release group does not exist anymore.

[Yateesh_h]

To check for inconsistency in your system, create a new PO and check if that triggers the release strategy, it shouldnt. For the old POs that already have ZT release strategy triggered, go to ME22N and make changes in the PO and "Check", this time the release strategy shouldnt trigger.

Hope this helps.

[Former Member]

Yes. Like you said. I make a new PO and this time the release strategy did not trigger.

So is it inconsistency? What should we do now?

[BijayKumarBarik]

Hi,

As created and then deleted the first release group ZT with other release strategies.

Now just cross check following:

1.Did new release group assigned to your release class.

2.All release codes which you are going to use are assigned to new release group.

3.The new release group is assigned to all release strategies.

4.All release strategies have properly designed, release codes are in sequence in order to release, all release VALUEu2019s are properly assigned in u201Cclassificationu201D segment and see that u201CRelease simulationu201D segment all release codes are there which are designed with each individual release strategy.

NOTE: Just cross check all release VALUEu2019s in CL24N/CL20N with individual release strategy with release group with release class.

Regards,

Biju K

[Former Member]

Hi,

What procedure did you follow while deleting the release group ? The process for release group deletion should be as mentioned below.

1. First delete the classification data for the release strategies you want to delete

2. Delete release strategies ( from detail view in SPRO )

3. Then delete release codes ( including description in different languages - translation )

5. Lastly delete release groups ( including description in different languages - translation )

If you dont follow the above process inconsistency might be there.

After deletion if you want to create new release groups follow the steps in reverse reverse order.

1. Create Release group ( including description in different languages - translation ) Check table - T16FG

2. Create Release Codes ( including description in different languages - translation ) - Check table - T16FC/T16FD

3. Create Release Strategies ( ( including description in different languages - translation ) - Check table - T16FS/T16FT

- Assign codes to Release Strategies

4. Maintain classification values - Tocode CL20N

Please let me know ifyou need any further help.

Regards

Sayan

Edited by: Sayan Pal on Dec 8, 2011 3:28 AM

[Former Member]

Procedure to delete, yes i did like your.

But there is a little bit difference with you when i create a new release strategy.

I did not go to step 4 - Maintain classification value. The reason is i dont wanna limit range of release. I dont want release trigger effective just only the value i put in. what I want is release trigger effective whatever value i put in 'Plant' field (ans the field table from Characteristic)

[Former Member]

Hi,

Please go to the PO ( which is picking up ZT ) and modify the quantity ( ME22N) and do a check and save. See if ZT is picked up or not. I believe it will not pick up ZT anymore since new PO is not picking up ZT. The reason may be you had created this PO before deletion of the release group. Hence ZT is still there.

Regards

Sayan

[former_member329706]

Hi,

I guess there is inconsistency of release group, thats why the old release group is displaying even i it is deleted.

Before deleting the release group you should first delete the release strategies and then release group.

So better try to re-define the old release group ZT and then check if any release staregy exists for that Release group if so try to delet first the release staretgy and later release group.

Check OSS note 365604

[ajitkumar]

reease strategies once firmed up in PO will remain. try to change the po value ar any other release char vaue so that a new strategy has to be triggered

[Former Member]

Hi expert,
> 
> I have a problem relate to PO release strategy. I try some of suggestions but nothing work. I hope you guy can help me to fix it.
> 
> 
> I have finished configuring PO Release Strategy and  Release Group is ZT with 2 release code (01, 02). 
> 
> After that i created some of other release groups and delete the first release group ZT (include release strategy). But whenever when i go to ME29N, ZT always appear in release group with it's release strategy even i already deleted it.
> 
> Thanks for your help

hI,

PLEASE remove the zt release group from release strategy and save then try to assign .

come from down deletion and save all the release strategy.

Thanking you.

[Former Member]

Actually, i dont want to use release group ZT anymore, so i deleted it. But i wonder why it still display when i go to ME29N.