Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KABR (Package) Appl. development: R/3 Cost Accounting order settlement
Basic Data
| Data Element | SR_STRAT |
| Short Description | Strategy for automatic generation of settlement rules |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SR_STRAT | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | SETTL_STRATEGY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Strategy |
| Medium | 15 | Strategy |
| Long | 20 | Strategy |
| Heading | 5 | Strat |
Documentation
Definition
This determines which receiver is assigned to the settlement rule that was generated by the system.
Use
If the system automatically creates the distribution rule, the strategy in the sender's strategy sequence specifies which receiver is contained in the settlement rule of the sender.
Supplementary Documentation - SR_STRAT 0001
Definition
Determines which receiver the system assigns to the automatically generated settlement rule.
Use
If the system creates the distribution rule, the strategy (in the strategy sequence of the sender) determines which receiver gets the sender's settlement rule.
- 01 No automatic generation / Manual maintenance
You use this strategy if a sender does not have a settlement rule that was created by the system, and you wish to maintain the settlement rule manually.
This strategy is useful for example, if you stored the strategies with receiver as a higher priority in the strategy sequence, but the system was unable to determine a receiver for them. By choosing the strategy that has the next priority down, you can prevent an error message being displayed.
Example:
An order has a strategy with the following assignments:
- Priority 1: Settlement to the responsible cost center
- Priority 2: No automatic generation / Manual maintenance
If you did not maintain the responsible cost center in the order, then the system does not generate anything. If the entry for priority 2 is missing, then no settlement rule can be generated, as there is no receiver data.
- 02 Settlement to a profitability segment
You use this strategy if the sender is to be settled to a profitability segment, whose characteristics are derived from the order master data.
- 03 Settlement to a requesting cost center
You use this strategy if an order is to be settled to its requesting cost center (screen field COAS-AKSTL).
- 04 Settlement to a responsible cost center
You use this strategy if an order is to be settled to its responsible cost center (screen field COAS-KOSTV).
- 05 Settlement to sales order
You use this strategy if an order is to be settled to its sales order (screen fields COAS-KDAUF und COAS-KDPOS).
- 06 Settlement to a WBS element
You use this strategy if an order is to be settled to its WBS element (screen fields COAS-PSPEL).
- 08 Copy the settlement rule from an assigned WBS element
You use this strategy if the order should contain the settlement rule from the WBS element assigned to the order (screen field COAS-PSPEL). This means that the settlement rule of the WBS element is copied.
History
| Last changed by/on | SAP | 20031111 |
| SAP Release Created in |
