Process C1-PEPL2 - Upload Payments (Step 2)

The batch process C1-PEPL2 refers to the second of three background processes that load the contents of the payment event upload staging records into the various payment tables.

The responsibility of the C1-PEPL2 process is to create payment events, payment tenders and payments and transition the corresponding staging records from Pending to Complete.

The following diagram and the section below describe at a high level the processing phases of the C1-PEPL2 background process.

The C1-PEPL2 batch process is the second of three background processes that load the contents of the payment event upload staging records into the various payment tables. It creates payment events, payment tenders, and payments. It then transitions the corresponding staging records from Pending to Complete.

Each distinct group of pending staging records associated with the same external source ID, external transmit ID, accounting date, and pay event process ID is processed as follows:

  • A payment event is created for the group and stamped on each of its records.
  • A payment tender is created for each distinct set of staging records having the same tender account, tender type and other tender information fields, except for the tender amount.
  • The Create Payment algorithm is then called for each distinct group of staging records having the same tender account, distribution rule and rule value providing it with the total amount for the group.
  • The staging record is moved to the complete state.
  • If any error occurs a designated staging record for the payment event group (one is picked at random) is set to Error and a To Do entry is created and linked to it to capture the error message that applies for the whole group. Other records in the group remain incomplete .
Note:

Group Error. This technique allows for an easier recovery from an error that affects all staging records for a single payment event. Capturing the error only on a single designated record requires only this record to be set back to pending once the issue is corrected. It is important to note that the whole set of records is not processes if at least one of the records in the group is in Error status.

  • If no error occurred, a To Do cleanup processing takes place to complete To Do entries previously raised for the designated staging record.
Fastpath:

Refer to To Do Entries Instead of Exceptions for more information on how To Do entries are used to capture processing errors.

Note:

This process is designed to support execution in parallel threads based upon the payment event process ID field.