Condition Tables with Release status

[Former Member]

When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?

Thanks,

Venkat

[Former Member]

hi,

The release status for condition records in a sales deal enables you to limit the use of records that have already been created.

Release status has the following characteristics:

no entry: released

A: blocked

B: released for price simulation

C: released for price simulation and planning

The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.

Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.

When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.

A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.

The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.

If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.

The release status of conditions in an agreement can only be changed, if

the condition record has release status in the key

the agreement has the release status released

Otherwise the condition record always has the release status of the agreement.

The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.

If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.

The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.

source : Library.

regards

[Former Member]

You can use a release procedure, which allows you, for example, to create condition records purely for planning purposes, which are then only taken into consideration after a pricing release. For this release procedure, you can use the processing and release statuses. You are free to define and use a processing status, although the release status can not be maintained by you directly but results indirectly from your assignment to a processing status.

The release status and processing status are only available for the new condition tables (see standard system section). If you also want to use this status for condition records that already exist, you can convert this (see Conversion section).

Release Status

The release status is already set. You can only set a processing status using assignment and selection of 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 the report SDNETPR0)

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

If several condition records are found at the access with different release statuses, the following priorities apply:

Pricing:

only for the release status released

Simulation:

first released for simulation

then released for planning and simulation

then released

Planning:

then released for planning and simulation

then released

Processing status

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

Examples for processing status:

released

first draft

for approval

approved department X

approved department Y

approved department Z

approved management

[Former Member]

Condition tables are created for 3 types of scenarios:

-Planning

-Simulation

-Pricing

In case of the use of condition tables in pricing we check both the boxes

-with validity Period

-With release Status.

Regards

AK

Reward points if helpful