SAP ABAP Data Element XST_RKUMU (IS-M: Type of cumulation for rolling discount)
Hierarchy
☛
IS-M (Software Component) SAP MEDIA
⤷
IS-M (Application Component) SAP Media
⤷
JAS (Package) Application development R/3 Publishing Advertising System***
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JAS (Package) Application development R/3 Publishing Advertising System***
Basic Data
| Data Element | XST_RKUMU |
| Short Description | IS-M: Type of cumulation for rolling discount |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XST_RKUMU | |
| Data Type | NUMC | Character string with only digits |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Dis.adj.II |
| Medium | 15 | Disc.adjust. II |
| Long | 40 | Disc.adjustmt: Earlier/all b.dtsts count |
| Heading | 0 |
Documentation
Definition
This indicator is used to determine which other billing datasets count towards determining a rolling discount for a billing dataset in a contract.
Example
If you stipulate that all billing datasets in the contract should count, by perfoming pricing again in the order, you can ensure that services which were performed earlier receive the current discount that is only actually produced by the addition of services that were performed later.
This setting should always be made for contracts without over-fulfillment.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
