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_SUM |
| Short Description | Method of duplicate table keys handling |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CNV_SUM | |
| 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 | Totl |
| Medium | 15 | Totaling |
| Long | 20 | Total/double recs. |
| Heading | 5 | Totl |
Documentation
Definition
The processing type indicates the action that occurs if duplicate entries occur during the update of table rows during the conversion.
Use
There are the following processing types:
<space> (No special processing is applied)
Depending on the scenario, if entries that have duplicate keys occur, the conversion program can either dump or end with an error. This setting should only be used if no key fields are converted. If key fields are converted, and you are sure that no duplicates can occur, use value 'I' (No duplicate handling necessary).
S (Sum all CURR and QUAN fields)
The values of the non-key fields from all rows that contain the same key are summed up. This applies only to fields of type QUAN (quantity) and CURR (currency). For other field types, the value that remains in the database depends on the order of the processed rows.
A (Ignore duplicate entries)
You use this processing type if it is not important which entry remains in the database. The value that remains in the database depends on the order of the processed rows.
G (Aggregate Function)
You can use this processing type to specify an aggregate function for numeric non-key fields. You specify the aggregate function at field level; this means that you can use a different aggregate function for each field. There are three pre-defined aggregate functions , H (maximum) L (minimum), S (sum), you can also specify a custom one (F).
P (Custom Priority Routine)
The duplicate entries will be handled according to the defined priority routine. The routine must decide for each conflicting pair of rows which of the rows should be written to the database (a conflicting pair consists of the currently updated / inserted row, and the row that is already in the database).
I (No duplicate processing necessary)
Either no key fields are changed in a table, or it was explicitly checked that no duplicate entries can occur after the conversion. If duplicate entries do occur, depending on the scenario, either the conversion program returns an error message, or the program terminates.
Supplementary Documentation - CNV_SUM 0001
Use
P (Custom Priority Routine)
The duplicate entries will be handled according to the defined priority routine. The routine must decide for each conflicting pair of rows which of the rows should be written to the database (a conflicting pair consists of the currently updated / inserted row, and the row that is already in the database).
Dependencies
Example
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in |
