Release Procedure for Pricing Conditions

September 17, 2017 | Author: Anupa Wijesinghe | Category: Simulation, Software, Technology, Computing, Computing And Information Technology
Share Embed Donate


Short Description

Download Release Procedure for Pricing Conditions...

Description

Contents Introduction .................................................................................................................................................. 2 Release status and Processing Status ....................................................................................................... 2 Convert old condition record (without release status) to have the release status .................................. 7 System Demo ................................................................................................................................................ 9 Block the condition record ...................................................................................................................... 10 Release the condition record .................................................................................................................. 11

Introduction Like in purchase order release strategy or sales order release strategy (Commonly known as "Status Profile" in SAP. Click here to view details), you can have a release procedure for your pricing conditions. This will allows you, for example, to create condition records purely for planning purposes, which are later taken into consideration after a pricing release. For this release procedure, you can use the functionality together with "Processing" and "Release" Statuses. Processing statuses are freely definable. But release statuses are pre-defined by SAP and therefore, you can only assign your processing statuses to those release statuses. Please note, these release statues for condition tables are only available from release 4.6 A. But it is possible to convert existing condition records to the new format with the release status.

Release status and Processing Status Release statuses are pre-defined by SAP. You can only assign your processing statuses to those release statues in the customizing under below IMG node; IMG Path:

Processing statuses can be assigned to condition records during condition maintenance (VK11, VK12). Assigned processing status will determine the release status of that condition record. During sales order pricing, condition records which the release status 'released' will be taken in to consideration for pricing. SAP has pre-defined below 4 release statuses. 1. Released - Can be used for SD pricing 2. Blocked - System will ignore these conditions during SD pricing

3. Released for pricing simulation - Conditions which has this release status can be used during "Net Price List report - (Program: SDNETPR0 in SE38)

4. Released for planning and pricing simulation - This means planning in CO-PA and price simulation During execution if system found several condition records with different release statues, then following priority will take place.  



Pricing - Only the release status = "Released" Simulation 1. First check for the release status = " Released for pricing simulation" 2. then check for the release status = " Released for planning and pricing simulation" 3. Then check for the release status = "Released" Planning 1. First check for the release status = " Released for planning and pricing simulation" 2. Then check for the release status = "Released"

Action Required: Define your own Processing status and assign those to a release status under above IMG path.

During new condition table creation, you can see the flag to activate the release status processing for condition tables. IMG Path:

->

If you have flagged the above field, you can use the release status functionality during condition record maintenance in the transaction VK11. When you assign such condition table to the access sequence, you can see the release status and processing status comes in the "Fields" level

In the standard SAP system (Before 4.6A), the table delivered are not with the release status and processing status. For example see table 004 - Material.

Same can be seen in the access sequence as well. (Under "Fields" level for that table) Eg:

Therefore with 4.6 A, SAP has delivered new set of tables and access sequences. New condition tables    

A304 - Material with release status (Instead of SAP table A004) A305 - Customer/material with release status (Instead of SAP table A005) A306 - Price list category/currency/material with release status (Instead of SAP table A006) A307 - Customer with Release Status (Instead of SAP table A007)

Eg:

New access Sequence    

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

Eg: Assignment of new access sequence to condition types 

The access sequence PR02 has been assigned to the condition types PR01 and PRRP.

Eg:

Convert old condition record (without release status) to have the release status 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. SAP has provided the report "SD_MOVE_A004_TO_A304" as an example report, which can be convert condition records with table 004 for table 304. To convert other tables, you can copy this report and enter the source and target table in the source text. When you run for this report, it deletes all of the old records and creates new ones with the status "Released". You can run this report based on the "Condition type"

The documentation will give you more information on this report and how changes can be made.

System Demo My condition type "ZAW0" has the condition table "969" with the release status. This condition type is assigned to the Access sequence "ZAW0". I have created a condition master record in VK11 as follows.

The "Processing Status" can be set using the button option

in this screen.

When you press this button, you can see only the "Processing Status" field is editable. "Release status" is not editable as it is determined based on the value you specify under "Processing Status" field.

Block the condition record When I select the "Processing Status" as "A", system automatically set the "Release status" as "A" (Blocked).

This is based on the customizing maintained for "Processing Status".

Now let's create a sales order with this price condition and see how "Condition Analysis" functionality shows this. Below can be seen in there;

As you can see above, if the correct "Processing Status" is set, system will not allow such conditions to be used in sales order pricing.

Release the condition record Now when the review is done, you can release the condition record, by selecting the relevant "Processing Status" Transaction: VK12  

Go to your condition record and select the button Set the "Processing Status" as "R" (Approved)



Now you should be able to see the "Release status" as "Released"



Now let's create another sales order and see whether this condition comes.

Condition automatically comes to the sales order

Now when you go in to details of the condition through "Analysis" option, you should be able to see below.

Author: Anupa Wijesinghe E-Mail: [email protected] / [email protected] Website: www.learnsaptips.com View my profile in LinkedIn Follow me on Twitter

Disclaimer This article is done based on my research and readings, unless otherwise stated. The views expressed are my own and not of anyone else. Author accepts no liability for the content of the articles in this website or for the consequences of any actions taken on the basis of the information provided. Using this information is at the users own discretion and responsibility.

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF