Ansicht
Dokumentation
Flexible Message Control ( RELNEBP_35_MSG_CONTROL )
rdisp/max_wprun_time - Maximum work process run time ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Short text
Flexible Message Control
Use
As of Release 3.5 of SAPMarkets Enterprise Buyer, message handling has been made more flexible. The aim is to allow customers to decide themselves:
- The message type which certain messages are to be assigned
- Whether certain messages are to be created at all
The goal is to facilitate business process, for example, to permit suppliers to create invoices even when they do not have all the necessary information at their disposal.
- Customizable messages
- You can influence the message type of the messages using Customizing activity Influence message control. You can even disable some messages completely so that they are no longer output on the user interface.
- If an E (error) message is set to a W (warning) message, the message is only forwarded to the user as a warning message. This error does not lead to an erroneous (incomplete) document. In this way, all actions that are possible for complete documents are also possible here. In the above example, such a shopping cart could be ordered.
- If a W message is set to E message, this causes the document to be deemed erroneous (incomplete). Here, no actions are possible that are only possible for complete documents. In this way, you can prevent a shopping cart from being ordered before such errors have been corrected.
- The number of customizable messages is predefined by SAP. The possible message types (including the option of switching off a message completely) are also predefined for each message individually.
- XML message control
- The Customizing activity Influence XML message control provides you with the opportunity to ignore certain errors (Eerrors) during XML import. The document itself remains erroneous (incomplete), but is handled like an error-free document and is forwarded to the approval workflow. The errors must have been corrected by the time a document is released by the last approver (at the latest) since only an error-free (complete) document can be released.
- Errors that are still to be ignored during import of the XML document have therefore to be corrected by the time that the document is released.
- SAP supplies a fixed number of controllable messages. In addition, you can add further messages.
- Warning: Note, however, that you only include those error messages that can actually be processed in the subsequent approval workflow. Proceeding in any other way will mean that you are never able to release certain documents
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
To change the message type or deactivate a customizable message, use the activity:
To specify that you want to ignore specific erroneous messages that arrive via XML, use the activity:
In a multiple company environment, company administrators access these transactions from their LaunchPad. They see only the information for their own company. See:
Further Information
Addresses (Business Address Services) PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 4271 Date: 20240520 Time: 224625 sap01-206 ( 72 ms )
