Business Requirement:
Sometime we need to use one condition table in an Access Sequence, but do not want to make all the fields of the condition table as mandatory fields while maintaining the condition record in VK11, as the Business wants to have some optional fields, which they may maintain or may not maintain.
Prerequisite:
User who knew the basic concept of Price Condition Technique for automatic determination of pricing in sales document.
Example:
Business wants to determine their Price on the basis of Sales Organization / Distribution Channel / Material / Region / Customer
But they do not want the Customer and Region as mandatory fields, since they want to maintain the common price for everyone, however in special cases, they want to give a different price to all the customer of a region, and a special price to one specific customer.
Method:
There are two methods in SAP:
Access Sequence | Step | Condition Table | Exclusive |
Zxyz | 10 | Sales Organisation / Distribution Channel / Material / Region / Customer | √ |
20 | Sales Organisation / Distribution Channel / Material / Region | √ | |
30 | Sales Organisation / Distribution Channel / Material | √ |
This is the most common method which we use normally.
Here I will try to explain the second method.
Configuration:
1. Create a Condition Table:
2. Create a new Access Sequence:
While creating the access sequence, maintain the “Atyp” as “A” for the Optional fields, and give a Priority to them.
When Atyp is maintained as “A” system consider these fields as Optional Field while maintaining the Price Master. Similarly when given the priority, system check the priority where ‘01’ is the highest and “99” has the lowest priority.
Now I would like to elaborate further on priority, with below example. Based on the above setting of access sequence, I can maintain master data in VK11 in following manner:
A. Sales Organization / Distribution Channel / Material
B. Sales Organization / Distribution Channel / Material / Region
C. Sales Organization / Distribution Channel / Material / Customer
D. Sales Organization / Distribution Channel / Material / Region / Customer
Now if the master data in VK11 is maintained for all the above four options considering all the field values are same (like same Sales Org., Dist. Channel., Material, Region, and Customer), then in SD document system will pick the data from Record ‘D’
However, if the master data is maintained for option ‘B’ and ‘C’, then system will pick the value from master data maintained for option ‘B’, since the priority for the field Region is '1' which is higher than the priority maintained for the field Customer.
3. Assign this access sequence to a condition type, then create a Pricing Procedure and determine the same as per the requirement.
4. Test the same by maintaining the price master data in VK11, as below:
System is showing Region and Mandatory field as optional, so you can maintain the record without any region or customer.
However for test purpose I will create two similar master data - one with Region and another with Customer, as below:
As you can see, from above data that I have created two records with two different rates, but the other field values are same. in one case it is customer based and in another it is region based.
Now create a Sales Order, as below, as per the logic, system should pick the rate of 100 INR as the priority of Region was higher than Customer, in Access Sequence.
5. Create Sales Order:
As you can see the system picks the rate of 100 INR, which was maintained at the Region Level, and it has higher priority.
Analysis also shows that system gets both the price but picks 100 INR due to higher priority and neglect the other.
Hope it clarifies this method of creating Price Condition Table and Access Sequence for automatic pricing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 |