Show TOC

Process documentationEnrichment and Validation (FS-PE-EV)

 

This process enables the validation of the attributes of payment orders and payment items in Payment Engine based on different checks performed when payment processing starts. The system enriches the payment information as necessary. That is, information is added to the payment orders or payment items based on the Customizing settings defined for different checks and the determined service level agreement (SLA).

If information is missing or incorrect, Payment Engine can use an internal automatic repair function to make the correction or you can correct information manually depending on the settings defined for exception handling. For more information, see Exception Control (FS-PE-EH). If an error is so severe that this internal repair function cannot correct it, Payment Engine can call an external automatic repair function using an exception handling process.

Payment Engine checks every payment order and payment item it processes in terms of:

  • Formal accuracy

    For example, account format checks check whether an account is valid for a respective country.

  • Referential accuracy

    For example, the IBAN check checks whether a payment order has an IBAN and whether the IBAN is correct.

  • Material errors

    For example, amount limit checks check whether the amount of a payment transaction is exceeded for a special payment order type or payment order type group.

  • Consistency

    For example, the credit and debit check validates whether the amounts assigned to the ordering party items and the recipient items are consistent.

For more information about the levels of checking performed by Payment Engine, see Enrichment and Validation Check Set and Enrichment and Validation Checking.

Prerequisites

  • You have defined the checks run during enrichment and validation in Customizing for Payment Engine under:

    • Start of the navigation path Payment Order Next navigation step Payment Order Enrichment & Validation Next navigation step Maintain Enrichment & Validation Check Set Rule End of the navigation path

    • Start of the navigation path Payment Order Next navigation step Payment Order Enrichment & Validation Next navigation step Maintain Enrichment & Validation Sets for Order Types End of the navigation path

    • Start of the navigation path Payment Items Next navigation step Maintain Enrichment and Validation Set for Payment Items End of the navigation path

    • Start of the navigation path Payment Items Next navigation step Transaction Types and Transaction Type Groups End of the navigation path

  • You have managed service level agreements on the SAP Easy Access screen by choosing Start of the navigation path Payment Engine Next navigation step Master Data Next navigation step Service Level Agreements Next navigation step Manage Service Level Agreement End of the navigation path (transaction /PE1/SLA). For more information, see Service Level Agreement and Managing Service Level Agreements.

Process

  1. The system reads the payment orders that are pending processing in Payment Engine.

  2. The system determines the service level agreement (SLA) based on the default bank code number and the account number in the ordering party item of the payment order.

  3. The system enriches the payment order with the required information for the clearing area SLA and performs the necessary formal and material checks.

  4. The system checks whether a corresponding customer SLA or customer segment SLA exists.

    If a match is found, the system:

    1. Performs the necessary formal and material checks that are defined in the customer SLA or customer segment SLA.

    2. Enriches the payment order or payment item with the required information.

  5. The system determines the processing program.

    You can define that the system runs standards checks and special checks on payment orders and payment items in Customizing based on the payment order type and on the transaction types of the individual payment items.

  6. The system performs validation checks in the following sequence:

    1. Payment order checks

      The system checks the payment order based on the processing program that was determined in step 5.

      If the system detects any errors, it flags the payment order with an individual error and continues checking the payment order.

    2. Ordering party item checks

      • If the system successfully checks the payment order or if no errors were detected, the system checks the original unsplit ordering party item.

      • If the system detects any errors, it flags the ordering party item with an individual error and continues checking the ordering party item. It is therefore not possible to transfer the complete payment order to Exception Control based on the errors detected in the ordering party item.

    3. Recipient item checks

      • The system validates the recipient items of the payment order only if no severe errors have occurred in the process so far.

      • If the system detects any errors, it flags the recipient item with an individual error and continues checking the recipient item.

    4. Cross-item checks

      The system cross-validates all payment item types.

    Note Note

    The results of the validation checks are listed in the logs of the corresponding business objects:

    • The results of payment order checks and cross-item checks are listed in the log of the payment order.

    • The results of checks on ordering party items and recipient items are listed in the corresponding payment item logs.

    End of the note.

  7. The system transfers the ordering party items of successfully validated payment orders to Routing Control, provided that the execution date of a payment order is not in the future.

More Information

Payment Processing (FS-PE-POP)

Exception Control (FS-PE-EH)

Routing Control (FS-PE-RP)