Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SCM-BAS (Application Component) SCM Basis⤷
CIF (Package) Core Interface
Basic Data
| Data Element | CIFIMAXCHK |
| Short Description | Consistency Check W/O Generation |
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 Only |
| Medium | 15 | Check Only |
| Long | 24 | Check Without Generation |
| Heading | 34 | Consistency Check W/O Generation |
Documentation
Use
If you set this indicator, the system checks the data consistency between the tables of the integration model (CIF_IMOD) and the runtime version (CIF_IMAX). A consistency check only makes sense if the RCIFIMAX report has already run with the Generation indicator in the relevant system and client.
We recommend you schedule the report regularly in the background with the Consistency Check indicator.
Any data inconsistencies discovered can be rectified by a new generation.
For more information, see the report documentation under Help -> Extended Help. To do this, access the report by calling up transaction SA38.
Dependencies
Note that the selection options object types and logical target systems are taken into account in the consistency check. If you have not made any entries for this, the system check all entries in the CIF_IMOD and CIF_IMAX tables for consistency.
You may not activate any integration models during the consistency check.
History
| Last changed by/on | SAP | 20030325 |
| SAP Release Created in |
