What is the importance of relase status in condition table?
- 5 Answers
- 15754 Views
- Cap Gemini, I also Faced
- E-Mail Answers
Answer Posted / ashok kumar sahoo
Hi,
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
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.
Standard System:
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.
Conversion
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. You can find further information on the checks in the report documentation.
Regards
Ashok
Future Career Solutions Pvt. Ltd.
| Is This Answer Correct ? | 1 Yes | 1 No |
Post New Answer View All Answers
Hi, I have advance payment scenario where customer want advance payment cannot be used against another sales order and against any credit limit. Let me put one example. Customer X is having credit limit of 1000 USD, if my client is received customized product order then he will take advance for this special order but customer X is already enjoying credit limit of 1000 USD. In this scenario my client wants advance payment received cannot use against any sales order and against any credit limit. If I will post advance payment in F-29 then customer credit exposure will decrease against credit limit in FD32 which will affect normal sales order credit limit. Here customer does not want to utilize advance payment against credit limit of customer which is use for normal sales order. Please suggest
What do you understand by intercompany customers and one-time customer?
Did you work on Transportation,what are the major settings for the transportation ?
Can any one explain how we will configure milestone billing , periodic billing and which scenario we will use?
In Third Party sale process, I am getting an error- in MIRO(Error No. M8889-A/c 893010 has been set as not relevant for Tax, but when I want to change the Account Assignment in ME21 it is taking only G/L A/C 893010 and refusing all other G/L A/C's by giving 2 errors. They are ME045-G/L A/c 39010 cannot be used(please correct)and ME038-No direct posting can be made to G/L A/C 34000. Experts please share your knowledge to solve this problem. Warm Regards.
what is the main purpose of maintaining the master data?
Explain credit management.
Change of sales document a sales document type of a sales order can be changed after getting saved. How do you do this?
how can you do consignment in inter company sales?
Tell me your Current client's organization structure in relation to SAP SD in your project? Draw / illustrate with a diagram.I have been asked this question in an recent interview. Please reply asap... Eagerly awaiting for your response? Thanks in advance.
List the system modules that are included in the financial application component?
What do you mean by order confirmation
Explain what is condition types?
Can a sales area belong to different company codes?
client wants to have sales of particular material area wise. How to write functional spec for this
