Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-MD-RPC (Application Component) Retail Pricing⤷
WCV1 (Package) IS-R: Sales pricing (Customizing)
IMG Activity
| ID | W_VPK_BADI_0001 | BAdI: Condition Posting Control in Sales Pricing |
| Transaction Code | S_AL0_96000673 | (empty) |
| Created on | 20020115 | |
| Customizing Attributes | W_VPK_BADI | BAdI Attribute for Sales Pricing |
| Customizing Activity | W_VPK_BADI_0001 | BAdI: Condition Posting Control in Sales Pricing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SPC_POSTING_CONTROL |
Use
You can use this Business Add-In (BAdI) to change the control for data backup of conditions in sales price calculation for a pricing item, as defined in Customizing for pricing, to suit customer requirements. This allows you to directly influence which conditions are to be created when saving a pricing item in sales price calculation.
The BAdI also serves as a filter. In Customizing, you define which condition records (condition type, condition table) are to be created for which list fields in the pricing table. You can use the BAdI to suppress the update of single condition records or all condition records.
For the basic checks as to which condition records are to be created, you can access pricing item data (vendor, sales price, margins, competitor prices, and so on), which is copied to the method CALC_ITEM_POST_CHECK as import parameters (see example).
Requirements
Standard settings
The BAdI is not activated in the standard system. The condition records are updated in accordance with the aforementioned Customizing settings for control of data backup in pricing.
Activities
Example
In the example code for this BAdI, filtering of the update is demonstrated for the following cases:
A) No update if the newly calculated final price is the same as the current final price
The conditions of purchase change, so you carry out a price calculation to check the margin for an unchanged sales price. As you want to use the actual markup in subsequent price calculations, you have entered an update for the list field "AUFSG" for a condition type "ZAUF", for example. When saving the price calculation in question, a new condition record is to be created for the actual markup, but not for the sales price, as this has not changed. You can then use the BAdI to filter out the update for the sales price (list field "ENDPR").
B) No update of condition supplements
For information reasons, you update certain prices in a price calculation as additional information for the sales price; an example would be the planned final price with rounding. If both prices agree, the condition supplement is not updated as it is redundant information. In this case, you filter out the update of the condition supplement.
C) Suppression of the update
For legal reasons, it is not possible to save a sales price that is lower than the purchase price if you do not enter a suitable price change reason at the same time. If such a situation arises and no price change reason is entered for the pricing item, you can suppress the update of conditions completely. You will receive a message to this effect in the update log.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020116 |
| SAP Release Created in | 470 |
