SAP ABAP Data Element MEREP_TYPCHK (Type Conflict Check)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_DATA (Package) Mobile: data replication
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_DATA (Package) Mobile: data replication
Basic Data
Data Element | MEREP_TYPCHK |
Short Description | Type Conflict Check |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MEREP_FLAG | |
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 Type |
Medium | 15 | Check the Types |
Long | 20 | Check the Types |
Heading | 1 | T |
Documentation
Definition
When this flag is set, the field values submitted from the mobile clients are verified against the field type definition of the meta data. If the field value is invalid, a message of type 'Error" is returned to the client.
Procedure
Make sure that this flag is set during development and testing. During production, however, deselect this flag to avoid performance loss.
Prior to shipment or production, the application program should ensure that such errors are prevented in the user input of the client application. In this case swtiching off the type check on the server helps to improve the synchronization performance.
Examples
Dependencies
History
Last changed by/on | SAP | 20070216 |
SAP Release Created in | 620 |