SAP ABAP Data Element MUSS (Text is obligatory)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷
VZ0C (Package) Customizing R/3 RV central functions
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VZ0C (Package) Customizing R/3 RV central functions
Basic Data
| Data Element | MUSS |
| Short Description | Text is obligatory |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| 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 | Text oblig |
| Medium | 15 | Text obligatory |
| Long | 20 | Text obligatory |
| Heading | 16 | Text obligatory |
Documentation
Definition
If you set this field, then the text type selected is mandatory in the text determination procedure.
In the sales document, the absence of a text for a text type defined as mandatory in the text procedure is reported in the incompletion log and can prevent the creation of subsequent documents (delivery, billing document).
Mandatory texts can only be defined for sales documents.
A mandatory text also not be defined for immediate display at the time it is copied, because it is assumed that the text is empty during sales document creation.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
