What is the effect of release Status in condition table and what if i deactive it.
The text may be useful .....
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).
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 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:
only for the release status released
first released for simulation
then released for planning and simulation
then released for planning and simulation
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:
approved department X
approved department Y
approved department Z
Customer Specific Adaptation
For defining your own processing logics for the processing status, you can use Business Transaction Event 00503303 Maintain Conditions: Transfers. If you want to, you can define the sequence of the processing status, which must be kept to when defining condition records (transaction VK12).
Working with the 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 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.
There are new condition tables and access sequences for using the processing and release status in the standard system.
New Condition Tables for Release 4.6A:
A304 Material (SAP table A004)
A305 Customer/Material (SAP table A005)
A306 Price list type/Currency/Material (SAP table A006)
A307 Customer (SAP table A007, but without the column)
New Access Sequences for Release 4.6A:
PR02 Price with release status (SAP access sequence PR00) with the tables A305, A306 and A304
K304 Material with release status (SAP access sequence K004) with the table A304
K305 Customer/Material (SAP access sequence K005) with the table A305
K307 Customer (SAP access sequence K007) with the table A307
Assignment of access sequences to the previous condition types from 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, KP02 and KP03.
As the release and processing status are only available for the new condition tables, you have the option of converting all condition records without the release indicator into new condition records with a release indicator.
The report SD_MOVE_A004_TO_A304 is available as an example report for condition tables (for other tables you can copy the report and enter the source and target table in the source text). The run for this report deletes all of the old records and creates new ones with the status released.
When starting the report you can restrict the conversion for specific condition types.
Checks are also carried out during the start report. Checks are made, for example, to see whether the old and new condition tables can only be differentiated in the release status and whether they are assigned to the same access sequence.