Hierarchy
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 | ISM_QUASI |
| Short Description | IS-M: Define System Contracts |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ISM_QUASI | |
| Data Type | CHAR | Character String |
| 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 | Syst.Cntrt |
| Medium | 15 | System Contract |
| Long | 20 | System Contract |
| Heading | 4 | Syst |
Documentation
Definition
If this field has an initial value, the sales area does not contain any system contracts.
The validity period for a system contract is defined using the rules that were available in Release 4.62 and earlier realeases if this field contains the value 'X'.
If this field contains one of the other letters as the value, the system determines the validity of a system contract using the following rules:
- In addition to service date S for the billing dataset for which the system contract is created, an earliest possible start B = 01.01.0000 and latest possible end E = 31.12.9999 are also defined.
- System contract paralllel to standard contract
This step is performed for the letters BDFHLNP.
If the holder of the system contract has a standard contract in whose validity S falls, the system sets B and E to the start or end of the validity period for this standard contract. It also copies additional attributes from the standard contract into the system contract (as was the case in 4.62).
- System contract ends before the standard contract
This step is performed for the letters CDGHKLOP.
The system moves E to a day before the start of the validity period for each standard contract for the system contract holder that starts later than S, unless E is already earlier than the start of the validity period. If letters KLOP are involved, this step is only performed for standard contracts that have the same booking unit (in the first requirement element in the leading requirement) as the system contract.
- System contract starts after the standard contract
This step is performed for the letters EFGHMNOP. The system moves B to a day after the end of the validity period for each standard contract for the system contract holder that ends before S unless B is already later than the end of the validity period. If letters MNOP are involved, this step is only performed for standard contracts that have the same booking unit (in the first requirement element in the leading requirement) as the system contract.
- If both B and E are further away than the standard validity period of S the system contract starts with S and is valid for the length of the standard validity period.
- If S is closer to B than E, the system contract starts with B and is valid for the length of the standard validity period.
- In all other cases the system contract ends with E and starts on the same day as the standard validity period.
- If the standard validity period has been defined for the sales area, the system only creates a system contract if its validity falls between B and E. If no standard validity period has been defined for the sales area, the system uses a period of 12 months in steps 5 to 7 and then restricts the validity period from B to E if necessary, (which may mean it is shorter than 12 months).
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 463 |
