CTO4 - Cherectersticks -Net price and Doc type

CL02 - Class -Assign Charecterstics to class

1. I wolud suggest not to delete any OLD Strategy . You may face problem.Instead of
Delteting it just Block it (Cl20N
2. this stratgy to work remove the values for old rel strategy classification
charactistics so that the old rel . strategy will not pick and new strategy will
get attached.

3. Is this release strategy S2 is in use in production client and assigned to

Purchasing documents?

SAP Recommends that you must absolutely avoid changes to release strategy
customizing once the release strategy is in use.
https://answers.sap.com/questions/9702884/regdeleting-release-code-from-release-
strategy.html

If you have to introduce such a change you should do as follows:

1) Make sure all of the old PO's have been released.

2) Create a new release strategy with the copy function and extend the new release
strategy as required.

3) Don't delete the original release strategy

If the Release strategy S2 is not in use then Remove the Release code L2 from
Release strategy and in Release Prerequites make change accordingly.

4. Since you are trying to delete one level from the existing strategy, Pls assign
Release prerequisites once again, go to Release statues, change the release
indicator(B/R) accordingly and Save.

Please keep in mind that if already PO s exists for the said strategy ,this will
have retrospective effect and create inconsistency in table T16FV.
Alternatively you can de-activate current Release Strategy by removing theCL20N
assignment and create new Strategy.
https://answers.sap.com/questions/9702884/regdeleting-release-code-from-release-
strategy.html

5. Deletion of Existing Release Strategy in SAP ECC

Follow
RSS feed
Like
10 Likes 10,666 Views 1 Comment
Deletion of Existing Release Strategy in SAP ECC
For implementing/activating /modifying New Release strategy in SAP ECC systems we
need to make sure that we will not having any inconsistency while activating it and
need to delete any existing Release Strategies.

Issue:
If a Release Strategy already exists than in the table KLAH where the class entries
are maintained has primary key and the class which is having lower primary key will
get triggered. So in order to avoid the inconsistency Existing Release Strategy
has to be deleted. According to standard SAP, for every release object (1=PReq,
2=Purchase order) only one class may be used.

1.1 Steps to be followed for Release Strategy Deletion

1. Create the Replica of existing Release strategy as per the Acceptance/
Production in the development system for all the boxes where Release strategy is
present.

2. Create the deletion request in Development system for all the Release
strategy replicated in the previous step. Release strategy needs to be deleted in
the following sequence.

a. Delete Release Strategy

b. Delete Release indicator

c. Delete Release codes

d. Delete Release group

3. Move this deletion TP in the respective Acceptance / Production system to

clean up the existing release strategy.

1.2 Deletion of Class:

4. On completion of deleting Release Strategy, delete the Class using
transaction CL02 in respectively acceptance/production system.

1.3 Deletion of Characteristics:

5. Delete the Characteristic using CT04 transaction respectively in
acceptance/production system.

1.4 Report:
6. Execute the report in Customizing (transaction OMGQCK or OMGSCK) and
ensure that the system does not display any red traffic lights.

1.5 Configure New Release Strategy:

7. Move all the Transports related to New Release strategy Configuration in
the acceptance/Production system as per required sequence.

8. Assign the Release Group and Release Strategy to Class using CL20N/CL24N
transaction in each system.

Reference Notes:
SAP note:365604

6. Normally, we don't delete the Release strategy, we just deactivate the OLD
release strategy only. Goto that release strategy. All combination you have to
leave it blank. So next time it will not be triggered anymore.

try this it will solve your problem.

Hi

Goto Transaction CL24N , Check for the Relase Class all the Strategy's Present, if
you can find the RS Which you think is deleted , Deactivate the Same By removing
the Charcateristic values.

You can try to maintain this Table Directly VV_T16FS_2 -Release Strategies:
External Purchasing Documents using SM30

T16FS is the Main table where all the Relase Strategies are stored.

got SE16N & check if the deleted RS exits or not.

7. Probably you might have deleted a release strategy and recreated with same id
again.
You can check the sap note 365604 for procedure to delete release strategy and
recreating with out making any inconsistencies.

8. Please read question 6 of note 365604 about this issue

6. Changing the release strategy when the system is running:

We strongly recommend that you do NOT change an existing release strategy that is
in use or its individual elements (release code(s), release status and so on),
especially if documents already exist in the system that use this release strategy

Seems there is inconsistency in your system. Please see the information in the
attached note 365604 part 5 about the correct procedure to delete the release
strategy:

5. Deletion of release strategies:

The tables T16FK, T16FV, T16FS, T16FC and T16FG may contain entries from previous
Customizing settings (such as old release groups) which were deleted in Customizing
but not in 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:

The release strategiesThe release indicatorsThe release codesThe release groupThe

corresponding class (transaction CL02) if a new one was created for the new release
strategies.

Then use transaction SE16 to check whether the entries were deleted in the tables
named above. Execute the check report in Customizing (transaction OMGQCK or OMGSCK)
and ensure that a red traffic light is not displayed. Also refer to SAP Note
350703. You can use report RCCLZUOB to check the consistency as already mentioned
in point 2f.

Best regards,