Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-GTF-BS (Application Component) Business Application Support⤷
CNV_BASIS (Package) Conversion: Basis functions
Basic Data
| Data Element | CNV_FUNC |
| Short Description | Name of the used routine |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CNV_FUNC | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Routine |
| Medium | 15 | Routine |
| Long | 20 | Routine name |
| Heading | 30 | Rout. |
Supplementary Documentation - CNV_FUNC 0155
Description
Priority routine is a routine whose task is to determine which of the 2 conflicting rows should remain in the database.
The above mentioned conflict occurs when the converted row is updated or inserted into the table and the row with exactly the same values of all key fields already exists in this table. This can only happen if one or more key fields are converted (the original key, which did not cause duplicate key entries was changed). Although, in general, there can be more than 2 conflicting entries, technically the conflict always occurs between exactly 2 entries - the one that is in the database and the one that is currently being processed (one entry is processed at a time).
If for the table the priority duplicate handling method is specified then the priority routine should be defined. A set of predefined priority routines should be delivered with conversion packages. They should also contain a short documentation explaining how they work. If no appropriate routine exists the custom one can be written.
Example
Supplementary Documentation - CNV_FUNC 0159
Description
Conversion routine implements the actual conversion of a table field. In most cases it uses previously defined mapping table to convert the old value to a new value (often also using organizational derivation to determine which organizational unit the currently coverted row belongs to). The conversion routine returns the (potentially) changed value which is then updated in the database.
The conversion packages always come with predefined set of conversion routines already assigned to the types of the fields (domains, data elements). However, if no conversion routine is available the custom routine can be created.
Example
Supplementary Documentation - CNV_FUNC 0161
Description
Custom aggregate routine aggregates the values a the given filed for all rows having the same key in case of duplicate key entries during the update / insert into database table. It always receives the values of the field for the currently updated row and for the row that is in the database. The simplest examples of aggregate function are predefined and can always be used:
- Sum
- Minimum
- Maximum
If none of these meets your requirements the custom routine can be written.
Example
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in |
