Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CA-DMS (Application Component) Document Management System⤷
CV (Package) Application Development: R/3 Document Management
Basic Data
| Data Element | ACL |
| Short Description | ACL Flag |
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 | ACLFLAG | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ACL FLAG |
| Medium | 10 | ACL FLAG |
| Long | 10 | ACL FLAG |
| Heading | 1 | A |
Documentation
Definition
Displays or hides the Authorizations tab in transactions CV01N (Create Document), CV02N (Change Document) and CV03N (Display Document).
Use
Dependencies
Example
Supplementary Documentation - ACLAS 4023
Use
This field contains the schedule class relevant for the time-specific reservation of a resource. This is generally the schedule class set for the business event in infotype 1022 (Schedule).
When a new relationship is added, if the field contains the value from infotype 1022 appended to the business event, you should not change this value if possible. If you change the value, it could mean that the reservation of the resource would be different from that of the business event schedule. You should only change the schedule if you explicitly wish to have a different reservation. Otherwise, a change can lead to undesired multiple bookings of related resources by other business events.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 604 |
