Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-FIM-FCO (Application Component) Financial Conditions⤷
FICO (Package) Financial Conditions
Basic Data
| Data Element | FICO_IMERGENO |
| Short Description | Ordinal Number for Markup Conditions in Condition Merger |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FICO_IMERGENO | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | Sequence |
| Medium | 15 | Sequence |
| Long | 30 | Sequence for Markup Conditions |
| Heading | 5 | Seq. |
Documentation
Definition
Ordinal number for processing markup conditions that is evaluated during effective condition determination.
Use
Only internal processes supply and evaluate this field.
This field controls the evaluation sequence of multiple valid markup conditions during the determination of the effective conditions. The condition merger specifies this sequence when it merges two condition lists. It does so by taking into account the prioritization of the condition lists. Markups in the condition list that have a low priority receive a lower ordinal number than those with a higher priority. When the system determines the effective conditions, it uses markups with a lower priority (and thus a lower ordinal number) before it uses those with a higher priority.
The ordinal number is defined for basis conditions in the Ordinal Number for Processing Basis Conditions field.
Dependencies
Another task of the condition merger is to replace the shadowing of basis conditions and markup conditions with basis conditions whose priority is higher. Markup conditions that have been shadowed are not allowed to be used when the system determines the effective conditions (this is the same as with shadowed basis conditions). Providing the condition merger can recognize the shadowing, it deletes the shadowed conditions or reduces their validity period to ensure that there is no overlap between them. To be recognizable, these conditions are fully specified and do not have any generic attributes. Where conditions do have generic attributes, the condition merger cannot replace the shadowing until the target values of the contract to which the condition applies are known. This is not always the case when the condition merger merges two condition lists. However, the condition merger can use the ordinal number described here to prepare for a later replacement of the shadowing once this is recognizable. It ensures that processes occurring after the target values become available can recognize and replace the shadowing of markup conditions with basis conditions of a higher priority (the condition reader for cross-currency conditions and the condition filter for generic differentiations).
The ordinal number enables you to specify priorities for markups, for example, for the way in which they can be created based on the agreement on various levels in pricing.
Example
The following is an example from pricing, a complex application of financial conditions:
You are using a condition list (condition group), which contains a basis condition where the credit interest is in EUR, and an absolute markup condition of 1%. This condition list is defined in a product price list. In a business partner price agreement, you have defined a condition list (condition group) that contains a relative markup condition of 110% for the same condition (credit interest is in EUR). The pricing application calls the condition merger to merge the two condition lists, and establishes that the condition list defined in the product price list has a lower priority than that of the business partner price agreement.
The condition merger assigns ordinal number 0001 for the absolute markup condition from the product price list. It assigns the value 0002 for the relative markup condition from the business partner price agreement. The financial calculator analyzes this ordinal number and adds 1% (ordinal number 0001) to the basis condition before multiplying the result by 110%.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 730 |
