Why only one Class is allowed in Release Strategy?

[Former Member]

Why only one Class is allowed in Release Strategy? Why can't we maintain more than one Class with different Release Code?

[Prasoon · Accepted solution]

Hi,

During document processing, system will pass the values dynamically from the communication structure CEKKO to the characteristics of the class assigned in config. Now, the release strategy determination will happen based on release characteristc value in the document and release classification data maintained in CL24N, saved in AUSP table.

If there are multiple classes, system can not identify the characteristics to which the values to be passed and can not identify a unique release strategy from classification data, AUSP. So its standard design which allows only one release class for external purchasing documents, and two for PR (One for overall and one for item level release).

Also refer the "object search" documentation in the help doc:

https://help.sap.com/doc/saphelp_46c/4.6.C/en-US/d8/54c8ecaa83d311ae690060b03c9bbe/frameset.htm

Regards,

Prasoon