Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-DMS (Application Component) Document Management System⤷
CVDI (Package) DMS - Document Distribution
Basic Data
| Data Element | CVDIASSID |
| Short Description | Recipient list ID |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CVDIASSID | |
| Data Type | CHAR | Character String |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 20 | |
| Value Table |
Further Characteristics
| Search Help: Name | CVI | |
| Search Help: Parameters | ASS_ID | |
| Parameter ID | CI1 | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | RL |
| Medium | 15 | Recipient list |
| Long | 20 | Recipient list |
| Heading | 10 | Rec. list |
Documentation
Definition
List where recipients are assigned to one or more documents.
Use
Recipient lists determine:
- Which recipient receives a document when it is distributed
- How a recipient receives a document (for example, original application files as an e-mail attachment)
When documents are distributed, the recipients can be determined automatically from existing recipient lists.
Procedure
Examples
Dependencies
A recipient list can be defined as a standard recipient list. A standard recipient list comprises all documents in this recipient list. Each document can only ever have one standard recipient list.
You can restrict the use of a recipient list by entering a context. When you distribute documents, you enter a context, and only the recipient lists created for this context are read.
Example:
By entering a context you can define, for example, that different recipients are determined for the distribution of a new version than for distribution of a released version.
History
| Last changed by/on | SAP | 19980514 |
| SAP Release Created in |
