SAP ABAP Data Element UMS_EXIST (Ind.: Check whether data already exists)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | UMS_EXIST |
| Short Description | Ind.: Check whether data already exists |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Check |
| Medium | 15 | Check rec.table |
| Long | 40 | Check whether data exists in rec. table |
| Heading | 5 | Check |
Documentation
Definition
This indicator defines whether the system checks to see whether data already exists in the receiver table before the actual conversion of the transaction data.
Use
If the indicator is set and data already exists in the receiver table, the system returns an appropriate error message.
Note
It is advisable to set the indicator with migration modes 1 and 2 because, with these migration modes, there should be no data in the receiver table which could be overwritten; otherwise the system cancels processing with a runtime error.
History
| Last changed by/on | SAP | 19940827 |
| SAP Release Created in | 470 |
