Condition Tables

[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]

HeyVenkat,

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.

Reward points pls.

Regards,

Govind.

[bcrao]

hi,

refer this business transaction event00503303 maintain condition;

http://help.sap.com/erp2005_ehp_02/helpdata/en/a4/af9e78e69611d2ace10000e8a5bd28/frameset.htm

[bcrao]

hi,

if you select release status- then you can allow release procedure to be used in when condition table is created. This adds two fields in condition table automatically-

KFRST--release status as last 'key' field

KBSTAT--processing statusas (non-key field)

the release status is predefined-

released

blocked

released for price simulation(ex sales deal)

released for planing and price simulation(ex sales deal)

The release status set directly by defining a processing status in costomizing for pricing and assigning a release status to the processing status

[Former Member]

Hello Venkat,

When we create condition tables, we just define the structure as we put there all required fields. And by releasing it we make it we make them active to use.

[Former Member]

The release status controls in which scenarios the condition records are found.

If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.

I hope this will help..Jess