Skip to main content

SD -Condition Exclusion group and its implication in Pricing


During a pricing Determination, if several valid Condition Records were available for a Condition type, We can define a Rule to determine a condition record to be considered a to be ignored

For example, we want a most favorable condition record among valid for a single condition type, then we define a Condition Exclusion and set Rules

Configuration of Condition Exclusion:

1. Condition Exclusion for a Group of Conditions:

Under this node we have several sub-nodes

1a.  Define Condition Exclusion Groups:
     
             


1b.    Assign Condition types to the exclusion Groups

                                 

1c.  Assign Condition Exclusion to the Pricing Procedure:  

                        



 In this Configuration, we have procedure which can have different impact o the selection
Let us see the explanation of each



Some of the comparison methods are as follows:
  • A   :  All conditions records in the first exclusion group are compared with each other and the condition with the best price is selected. All other conditions are deactivated.
let us Consider a example, 
We have two Discount Conditions such as K004 and K005 in 001 conditon exclusion Group

K004           -   40$
K005           -   45$

When we Set A, system will set K005 as Active in Sales order and ignore K004 ( will set it to Inactive)

  • B    :  All condition records for one condition type are compared with each other and the condition with the best price is selected. All other conditions are deactivated. This method can be used with condition type PR00.
We have two Condition Records for PR00 with Different access sequences
PR00   -  100$
PR00   -  200$

When we set B, system will set PR00 with 100 $ in the sales order.


  • C     :  The overall price of all condition records in the first exclusion group is compared with the overall price of all condition records in the second exclusion group. The group resulting in the best price is selected. The conditions of the other group are deactivated.
This is a comparison between two Condition Exclusion group and results in most best price to the customer
  • D    :  If a condition record is determined for the condition types of the first exclusion group, all the condition records for the second exclusion group are deactivated.
This will give best condition records among the Condition Exclusion groups and ignores other condition types

  • E     :  Method E is similar to method B, except that the worst (highest charge or lowest discount) price is selected.
This is similar to B, instead of Best a high charge is levied to the customer

  • FMethod F is similar to method C, except that the group with the worst overall price is selected. The conditions of the other group are deactivated.
This is similar to C, instead of Best a high charge is levied to the customer

  • L    : Method L is similar to method A, except that the worst (highest charge or lowest discount) price is selected.
This is similar to A, Instead of best a High charge is levied to the customer.



just understand the blog theoretically, we will discuss practically in other blog.

Youtube Link for demo:

https://www.youtube.com/watch?v=MamJuqKj900



Labels:

Comments

Post a Comment

Popular posts from this blog

SAP PM/CS / EAM : Refurbishment Process

Refurbishment A refurbishment order is a standard Maintenance Order type. In customizing for order, we first create an order type ( such as PM04) In the configuration we have to create a new order type in OIOA and activate this for Refurbishment process. Process flow: Business process steps 1. Damaged equipment/ spares if can be repaired will be done by the PM order of type PM04 2. Equipment/Spares needs repairing should have the item code if it is serialized item then with the serial number. 3. Item should have the valuation type for repair category too. 4. Create PR through refurbishment order for repair of the item with split valuation type of repair. Proper G/L codes and order for the repair indent should be provided in the indent 5. After approval of the requisition, the requisition and item should be send to the stores/Purchase section for further actions. 6. Stock will get updated after MIGO of the item 7. The activity type cost ...
2 comments
Read more

SAP SD/CS/PS /PM : System status and User Status a differentiation

In SAP, Master Data and Transaction data is controlled by system status.  But there are certain limitation where system status cannot be used, In such instances a User status can be used. We will see how a system status and User status functions in a particular transaction. Let's understand what is "SYSTEM STATUS" and  "USER STATUS" from system perspective. SYSTEM STATUS:-                                                       A system status is set by the system automatically upon executing a function. It                            Specifies that a particular function was carried out on an Object, be it a                            Transaction ( like Service Order) or a master Data ( serial Nu...
3 comments
Read more

S4HANA/ SD/PP/PS/CS---- Requirements Type and its determination in Sales Order

This Article focuses on Requirement Type and how it is determined in Sales Order. Also  the strategy of Requirement and its Usage Definition of Requirements Type:                Requirement Type Identifies different Requirements like Sales Order, Delivery Requirements,  individual Customer Requirements, Make To Order  or Assembly to Order. Requirements Type uses Planning strategy which has specific strategy for specific Process Requirements Type along with Requirements Class plays a Significant role in determining relevant Functions like, Costing, Settlement, Result analysis, Accounting Indicators,  Special Stock  Indicators, Valuation settings Determining the Requirements Type: To determine  Requirements Type at Sales Order, a sequence of Strategies are defined in Standard Let us check these Strategies 1.  At First, system will check the MATERIAL MASTER--> MRP  3 View-->Strategy...
2 comments
Read more