Query

[Former Member]

Hi all

Can u plz tel me d use of the field in the condition table i.e ( With Release status )

Thanks regards

Ritu

[Former Member]

Thank you sam and bhusan

Ritu

[Former Member]

Hi,

Condition table

u2022 Condition table is a combination of fields, which form key for a condition record.

u2022 Each condition table defines under access sequence.

u2022 All fields, which are to be used for creating a condition table, must be contained in the field catalogue. It is possible to add additional fields to this catalogue.

Release procedure

u2022 You can allow a release procedure to be used when a condition table is created by selecting the with release status checkbox. This adds the following fields to the condition table automatically.

 KFRST-Release status as last key field

 KBSTAT- Processing status as a field of the variable data part (non key field)

u2022 u201CThe release status is set indirectly by defining a processing status in customizing for pricing and assigning a release status to the processing statusu201D

u2022 Different statuses are

 Released

 Blocked

 Released for price simulation

 Released for planning and price simulation.

Thanks

Bhushan

Edited by: Bhushan S Dhake on Sep 25, 2008 12:14 PM

[Former Member]

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.