PR Release strategy

[Former Member]

Hello All,

For our client, there are existing release strategies with Class "PR_Class1". Now I have created another class "PR_Class2" with different characteristics & assigned to same rel. strategies.

What precautions/ prerequisites I must follow for the existing unreleased PRs(release in process) & POs(in case of released PRs) before transporting to the production server. Pls guide me on the same.

Regards

Abhijit

[Former Member]

Hi Abhijit,

I suppose you created two different classes

one for For overall release

and the second one For item-wise release

One class will use characteristic with field Ceban-GFWRT for

the overall release. The other class to be used for the item release

will use characteristic with field Ceban-GSWRT.

You can only use one type of release for a specific document type.

To do this in configuration you must flag the document type (OMEB) to

be used for overall releases by clicking on the overall release flag.

After clicking on the flag then this document type will only look for

the overall release strategy. If the document type does not have the

overall release strategy indicator on then this document type will

only look at item release strategies. In the release strategy

configuration you can now set up the two classes to be used for the

release strategies. One will be for overall release and the other

will be used for the item release strategies. The system will use the

document type to determine whether the overall or the item release

should be used. Also you need two assign these to different release

groups.

You could have some inconsistencies in table T16FK, T16FV, T16FS and

T16FC as described in note 365604 item 5.

Creation or Deletion of

release strategy must follow in the sequence as below, if not it

will create inconsistency.

You can follow steps as below:

1. Create back the old release object:

( RELEASEGROUP - RELEASECODE - RELEASEINDICATOR -

RELEASESTRATEGIES - WORKFLOW)

2. Delete all release objects in OMGS first,

You have to do this "from bottom to the top". ( WORKFLOW -

RELEASESTRATEGIES - RELEASEINDICATOR - RELEASECODE - RELEASEGROUP ).

3. Delete all relevant characteristics in CT04 first, then delete the

relevant class in CL02.

When you delete a release strategy, the purchase orders which were

already assigned that release strategy can't recognize this change

unless you open the PO and make some change to it. Hence you get

"Release strategy inconsistent" for a PO which had the release strategy

that has now been deleted.

So the behaviour is absolutely normal.

Checking the release strategy is active or not.

A working strategy must have classification status '1' (active) in

Transaction CL24 or CL24N.If release strategies are deleted,

ensure that the strategy is also deleted in Transaction CL24N with

the deletion in Customizing.

BR

Nadia Orlandi

[Former Member]

Hi Nadia,

I have created another class for Overall release strategy(with different characteristics).There is no class for itemwise release startegy. I have assigned this new class(PR_CLASS2) with different characteristics to existing release strategies. Now theres only one class(PR_CLASS2) assigned to the release strategies.

Now in the system, there would be PRs whose approval is in process. If I transport my changes to the system, what would be the effect on the existing PRS(in process). Is there any precaution or pre-requisite that I need to follow?

Thanks

Abhijit

[murugan_mgl]

See when u create the second class, you should give the validity date from which is effective.The system will pick the 2 nd Rel startegy from the validity date given in CL02.Old PR will be subject to old rel strategy.

[Former Member]

Hi,

As per my knowledge we can use only one class in a client . If we change the release strategy , the document previously created will be triggered by new strategy when ever we go for changing the existing document.

Regards,

Deepak