Release Procedure for Conditions

Scope of Functions

You can use a release procedure for conditions that allows you, for example, to create condition records at first purely for planning purposes, and are only taken into consideration after they have been released in pricing. The processing and release statuses are available for this release procedure. You are free to use and define the processing status, whilst the release status can not be directly maintained by you, but results indirectly from assignment to a processing status.

The release status and the processing status are only available in the new condition tables (see the standard system section). If you want to use the status for condition records, you can convert these (see conversion section).

Release status

The release status is already specified. You can only set it indirectly by asssigning and selecting a processing status. The following statuses are currently defined:

• released

• blocked

• released for price simulation (this means the creation of a net price list using report SDNETPR0).

• released for planning (in CO-PA) and price simulation

If during access to the condition records, several are found with different release statuses, they should be dealt with in the following priority:

Pricing:

only released with release status

Simulation:

• firstly released for simulation

• then released for planning and simulation

• then released

Planning:

• firstly released for planning and simulation

• then released

Processing status

You are free to define the prcessing status. You can define your own processing status in Customizing for Pricing and assign a release status to this.

Examples for processing status:

• released

• first draft

• for approval

• approved department X

• approved department Y

• approved department Z

• approved management

Customer-specific adaptation

To define your own processing logic for the processing status, you can use the Business Transaction Event 00503303 Maintain conditions: Transfers. This enables you, for example, to determine the processing status, that must be used when maintaining condition records (Transaction VK12).

Working with agreements

The agreements have a maintainable release status and no processing status. If conditions are assigned to an agreement, the agreement passes the release status on to all of its conditions. The relevant processing status is also set.

INCLUDEPICTURE /SAPIrExtHelp/standard.asp?name=hinweis.gif \bmc \d If several processing statuses are assigned to a release status, the condition record receives the first (alphabetically) suitable entry as a processing status.

The processing status, that the conditions have received indirectly from an agreement via the release status, can only be changed for released agreements.

Standard system:

There are new condition tables and access sequences in the standard system for using the processing and release status :

New condition tables for Release 4.6A:

• A304 Material (SAP table A004)

• A305 Customer/Material (SAP table A005)

• A306 Price list category/currency/material (SAP table A006)

• A307 Customer (SAP table A007, but without the division)

new access sequences for release 4.6A:

• PR02 Price with release status (SAP access sequence PR00) with tables A305, A306 and A304

• K304 Material with release status (SAP access sequence K004) with table A304

• K305 Customer/Material (SAP access sequence K005) with table A305

• K307 Customer (SAP access sequence K007) with table A307

Assignment of new access sequences to the previous condition types as of Release 4.6A:

• The access sequence PR02 has been assigned to the condition types PR00, PR01 and PRRP

• The access sequence K304 has been assigned to the condition types K004 and PMIN.

• The access sequence K305 has been assigned to the condition types K005, KA00 and PR02.

• The access sequence K307 has been assigned the condition types K007, KP00, KP01, and KP02 und KP03.

Conversion

As the release and processing statuses are only available for the new condition tables, you have the option of converting old condition records without a release indicator into new condition records with a release indicator.

The report SD_MOVE_A004_TO_A304 can be used as an example report for the condition tables (For other tables you can copy the report and enter the source and destination table in the source text). The report run deletes the old records and creates new ones with the release status set as released.

When you set the report you can restrict conversion for specific condition types.

Checks are also carried out at the start of the report. These check, for example, that the old and new condition tables only differ in the release status and are assigned the same access sequence. You can find further information on the checks in the report documentation.

Effects on Customizing

You can find a processing status definition under Sales and distribution -> Basic functions -> Pricing.