SAP ABAP Data Element NOSUCCESSMESS (Indicator: no success messages written in log)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷
IS-U-BI (Application Component) Contract Billing
⤷
EE20 (Package) IS-U: Billing
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | NOSUCCESSMESS |
| Short Description | Indicator: no success messages written in log |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KENNZX | |
| 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 | NoSuc.mes. |
| Medium | 15 | No succ. mess. |
| Long | 20 | No success messages |
| Heading | 1 | N |
Documentation
Definition
If this indicator is set, no success messages are written to the log. For example, if the message "Contract xyz was billed successfully" is output in the billing program, it is not transferred to the log. In this way, unnecessary entries in the log are avoided.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
