cancel
Showing results for 
Search instead for 
Did you mean: 

Release Not triggering in PR

Former Member
0 Kudos

Hi,

We are in a Roll Out project wherein we are sharing the same client & landscape.

Now the issue is as follows.

1) The parent company has a release strategy wherein they have defined document type, Account assignment, USRC1, Total Value of PR & tracking number as the characteristics.

2) Now the company which I have been assigned to work on requires only PR document type, USRC1 & Total Value of PR as the characteristics.

3) As per my knowledge we can use only a single class for a client.

Thus kindly suggest what can I do wherein the release is triggered even if I keep some characteristics as empty i.e. account assignment & tracking number.

Thanks

Accepted Solutions (0)

Answers (6)

Answers (6)

0 Kudos

Hi Jajati,

I think you need to delete the existing release strategy setup and than set up your new release strategy

For implementing/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. According to standard SAP, for every release object (1=PReq, 2=Purchase order) only one class may be used.

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.

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.
  3. Delete Release Strategy
  4. Delete Release indicator
  5. Delete Release codes
  6. Delete Release group
  7. Move this deletion TP in the respective Acceptance / Production system to clean up the existing release strategy.
  8. On completion of deleting Release Strategy, delete the Class using transaction CL02 in respectively acceptance/production system.
  9. Delete the Characteristic using CT04 transaction respectively in acceptance/production system.
  10. Execute the report in Customizing (transaction OMGQCK or OMGSCK) and ensure that the system does not display any red traffic lights.
  11. Move all the Transports related to New Release strategy Configuration in the acceptance/Production system as per required sequence.
  12. Assign the Release Group and Release Strategy to Class using CL20N/CL24N transaction in each system.

Reference Notes:

SAP Note 365604

Former Member
0 Kudos

Thanks for your responses issue has been resolved

0 Kudos

Please mark it as Answered.

Former Member
0 Kudos

Blank characteristics are usefull in some cases and not usefull in some.. so check this OSS notes and better test your release strategies with different options

SAP Note 493900 - FAQ: Release Strategy

If you want to use blank characteristic. you should maintain a value with ' ' in the characteristics.

for account assignment you dont enter any alien value, so its better you maintain all the values including standard. But for tracking number you may try with the blank value.

Former Member
0 Kudos

Hi,

We can use only two class one for itemwise release and another for overall release.

USRC1 is user defined field so check Enhancement M06B0005 in SMOD first. You may require some program modification for your another company.
You can not leave Charactristics value blank otherwise release strategy will not get determined.
If you do not want to use perticular field then enter value 00 to 99 ot AA to ZZ depending what kinf of field and value.

Ravindra

Yateesh_h
Active Participant
0 Kudos

Hi,

Please try putting all the values possible for the unwanted characteristics(Account Assignment and Tracking number) and BLANK in the Release strategy.

Since Account assignment is at the item level, if there are 2 different account assignments in the same PR, then BLANK will be used by the system, so include BLANK as one of the allowed values for the Account Assignment characteristic.

Hope this helps.

Former Member
0 Kudos

Hello Jajti,

You can use max 2 Class. create doc type for PR ant case u can use the same charstics and assign it in classification.

Regards

Avinash

Former Member
0 Kudos

you will have to maintain "blank" as the value for the characteristics not required in your rel. stgy.

Blank will be considered as always true and hence rel. stgy will be triggered as soon as the first match based on the required characteristics is found.

Regards,

Dakshesh