Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MGW (Package) Application development R/3 material master Retail
Basic Data
| Data Element | NO_CHNG_DOC |
| Short Description | Do Not Write Change Documents |
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 | NO_CHANGE_DOC | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | No ChgDocs |
| Medium | 15 | No change docs |
| Long | 20 | No change documents |
| Heading | 4 | NoCD |
Documentation
Definition
Use
Determines whether change documents, and thus ALE change pointers, are written during data transfer. It is not possible to set this indicator when distributing data by ALE, where change documents and possibly also ALE change pointers are always written.
- Indicator set
No change documents are written for the created or changed data records. Since the ALE change pointers are written via the change document interface, no change pointers are written as a result, even if the writing of change pointers is activated for message type ARTMAS in Customizing for Distribution (ALE) in the activity Activate Change Pointers According to Message Type.
- Indicator not set
Change documents and possibly also ALE change pointers are written for the created or changed data records.
Procedure
Examples
Dependencies
In data transfer, where it may be necessary to transfer very large quantities of data from a legacy system, setting this indicator can reduce the runtime because writing change documents can be a significant time factor.
History
| Last changed by/on | SAP | 19990421 |
| SAP Release Created in |
