Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBSE (Package) FI-SL sets
Basic Data
| Data Element | SETWRITECD |
| Short Description | Indicator: Writing 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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 9 | Chng.docs |
| Medium | 19 | Writ. change docus |
| Long | 33 | Indicator: Writing chnge documnts |
| Heading | 0 |
Documentation
Definition
The indicator determines whether change documents are written for particular Controlling master data groups.
This way all changes to a group with regard to its structure (items) and its name are logged. Here the date of the change and the person who made the change are recorded. You can then use the change documents to view the history of the group.
Since writing change documents increases the amount of work involved in changing groups and the fact that the change documents can accept a large amount of data, we recommend that changes are only documented for certain categories.
Before you switch on logging for particular categories, you should try to estimate the volume of change documents to be expected based on how often you make changes and the size of the changed groups. Each change in the hierarchy structure (adding a group or a value, deleting a group or a value) results in a change document being written.
In particular no change documents should be written for order groups since these groups are often very large and change relatively frequently due to automatic generation.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |
