SAP ABAP Data Element MDG_MDF_NO_CROSS_CHK_FL (Master Data: Do Not Cross-Check Field Definitions (Indic.))
Hierarchy
☛
MDG_FND (Software Component) MDG Foundation
⤷ CA-MDG-AF (Application Component) Application Framework
⤷ MDG_MDF0 (Package) Master Data
⤷ CA-MDG-AF (Application Component) Application Framework
⤷ MDG_MDF0 (Package) Master Data
Basic Data
Data Element | MDG_MDF_NO_CROSS_CHK_FL |
Short Description | Master Data: Do Not Cross-Check Field Definitions (Indic.) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MDG_MDF_FLG | |
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 | No X-Check |
Medium | 15 | No Cross-Check |
Long | 20 | No Cross-Checking |
Heading | 6 | No XCh |
Documentation
Definition
Determines that the system does not perform cross-area checking between InfoObject definitions in the local SAP BW system and those in other SAP BW systems.
This setting applies only if the current client uses several InfoObjects in multiple application areas and two or more different SAP BW systems (RFC destinations) are involved.
Use
Select this indicator only if the following conditions apply:
- You are sure that the InfoObject definitions are the same in all connected SAP BW systems and you do not want the system to perform this check every time you start the application.
- You want to avoid RFC communication with other SAP BW systems when you start the application because, for example, the users do not have authorization for the other RFC destination.
Warning: If this indicator is selected although InfoObject definitions are inconsistent, this may lead to repetitive calls to the data model synchronizer. To prevent this problem, it is imperative that you match the InfoObject definitions.
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |