SAP ABAP Data Element BCS_PERS (Type of Possible Personalization of a Document)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷ SBCOMS (Package) Business Communication Service
⤷ BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷ SBCOMS (Package) Business Communication Service
Basic Data
Data Element | BCS_PERS |
Short Description | Type of Possible Personalization of a Document |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BCSD_PERS | |
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 | Pers. Type |
Medium | 20 | Personalization Type |
Long | 0 | |
Heading | 0 |
Documentation
Definition
The personalization type specifies which type of data is used in the document:
- Recipient-specific variable replacement: In this case, recipient- specific data and data from the current application document can be used in the Smart Form.
- Object-specific variable replacement: In this case, only data from the current application document can be used in the Smart Form.
- No variable replacement: In this case, only fixed values (therefore, a fixed text) or system fields can be used in the Smart Form.
Use
The setting is used to optimize the runtime. If only a fixed text can be sent, less data is read and forwarded than if the address has to be formatted for each recipient, for example.
Dependencies
Example
History
Last changed by/on | SAP | 20020827 |
SAP Release Created in | 620 |