Ansicht
Dokumentation
_ISPSFM_H_MSGNR - Define Error Handling
General Material Data Vendor Master (General Section)This documentation is copyright by SAP AG.
In this step, you can determine how non-assignable payments can be processed further and updated correctly based on errors that occur.
The error handling enables you to generate batch input sessions that are processed automatically in the Background.
If you do not use error handling, batch input sessions are generated for the corresponding bank turnover that you must process manually in order to carry out the necessary adjustments or supplements for an update.
Certain problems may arise with the update, such as incomplete Customizing settings, unclear entries in the note to payee or an unclear account situation which can cause errors. Each error that occurs is represented by an error message in message class FMLGD.
In this step, you can define how the bank turnover should be processed further for these error messages. In addition to this, you can also outsort your own messages.
The error messages delivered in message class FMLGD are divided into the following areas:
- 0XX Technical error messages
- 1XX Customer down payments
- 2XX Vendor down payments
- 3XX G/L account debit posting
- 4XX G/L account credit posting
- 5XX Vendor down payment with general request
- 6XX Customer down payment with general request
- 7XX Customer bank credit memo
- 80X Clearing Sequence of Open Items
- 85X Turnover interpretation (credit memo)
- 87X Turnover interpretation (debit memo)
- 9XX Customer-specific errors
You must define at least one error message for each company code and transaction type for the processing of credit memos 001 and one error message for the processing of debit memos 002. Otherwise the turnover cannot be processed if errors occur.
In addition to this, you can use a general error message for each posting type (X00 basic setting) that you can define if you want to use error handling. It is advisable to define this basic setting, otherwise the system cannot carry out the posting automatically.
You can also trigger a specific error handling, depending on the request by defining further error messages for this posting type accordingly.
If an error is triggered for a posting type and no setting exists for this in the Customizing of error occurrences, the system checks whether a basic setting exists for the error handling of the posting type. If a basic setting does not exist either, the program carries out the posting in accordance with the settings for message 001 or 002.
The account assignment profile for the corresponding posting types must be created as well as folder variants.
-
You create an error message for processing credit memos 001 and one for processing debit memos 002 for each company code and transaction type.
Note that you are not allowed to make any entries for the posting rule, business transaction code, +/- sign and amount for these error messages. - Check which problems you want to define automatic error handling for and define the error messages accordingly.
For more information on the error messages delivered, see the long text on messages in message class FMLGD. You can also create your own messages here if you wish, in area 9XX.
Special handling is possible for error message 712. The message is issued if no open items exist for a payment, but the customer and company code can be determined from items already cleared. You can use this message to control that the payment occurs as a down payment on the company code and customer determined beforehand from the first cleared item.
The following setting is necessary for this:
- Posting type 01 (customer down payment)
This allows payments to be updated automatically without open items having been cleared.
- An account assignment profile for posting type 01 for which neither a customer or company code has been specified.
Note that an account assignment profile in which neither a customer or company code is specified can only be used for errors 712 and 713.
rdisp/max_wprun_time - Maximum work process run time PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 4812 Date: 20240523 Time: 182814 sap01-206 ( 78 ms )
