Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-SFC (Application Component) Production Orders⤷
COWB (Package) PP Workbench
Basic Data
| Data Element | COWB_MESSAGE_LEVEL |
| Short Description | Level of Message Type for Saving Log |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | COWB_MESSAGE_LEVEL | |
| 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 | Log |
| Medium | 15 | Save Log |
| Long | 20 | Save Log |
| Heading | 25 | Save Log |
Documentation
Definition
Specifies the lowest level of message which must occur for the system to save the log in the application log.
Use
After a mass processing function has been carried out, the application log specifies, for each order, whether the execution was successful, or if it was not, which problems occurred. The application log is saved to the database so that the user can look at it later.
To save memory, you can use this parameter to specify the lowest message type that must occur for an order for the system to save the log. The system then saves all the messages that have been generated for this order, even those of types that do not correspond to the setting in the parameter.
Dependencies
After a mass processing function has been carried out, all messages can always be viewed in the application log. The parameter only influences which messages are saved to the database so that you can call them up again later.
Example
History
| Last changed by/on | SAP | 20050705 |
| SAP Release Created in | 600 |
