Hierarchy
EA-GLTRADE (Software Component) SAP Enterprise Extension Global Trade⤷
LO-GT-TE (Application Component) Expenses⤷
WB2B_EXPENSE (Package) Trading Expense Handling
IMG Activity
| ID | W_WB2B_0G41 | Define Calculation Schema |
| Transaction Code | S_P0D_25000085 | (empty) |
| Created on | 20010226 | |
| Customizing Attributes | W_WB2B_DUMMY | Attribute Global Trade |
| Customizing Activity | W_WB2B_0G41 | Define Calculation Schema |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_WB2B_0G41 |
Use
You define the calculation schema for sales expenses, in this step. In the calculation schema, you define which condition types should be taken into account and in which sequence. During pricing, the SAP system automatically determines which calculation schema is valid for a business transaction and it takes the condition types contained in it into account one after the other.
You may find that you need to maintain two different calculation schemas for trading expenses:
- Calculation schema for expense processing with planned expenses
- Calculation schema for expense processing with unplanned expenses
In the schema for planned expenses, you could set the condition type for reading the base amount from a document as a statistical value (the expense value is calculated using this base value). You should also set an account key within this calculation schema.
In the schema for unplanned expenses, the system uses the ordinary SD calculation schema for calculating the expense value. This means that the condition class for the expense condition type should be Prices, not Discount or surcharge.
Requirements
Standard settings
Activities
- Determine the extent to which you can use the calculation schemas provided in the system.
- Create new calculation schemas by copying a similar existing one. You may delete or change condition types as necessary for your business scenario.
- Enter a key (6 characters) for the schema you wish to create and provide a description for it.
- For each schema, specify the condition types in the order of their usage, and maintain the relevant data.
Example
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VVC_T683_VA | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20020326 |
| SAP Release Created in | 46C |
