Process C1-PEPL1 - Upload Payments (Step 1)

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

The responsibility of this process is to transition the status of the staging records from Incomplete to Pending. The status of a staging record must remain Incomplete until:

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

C1-PEPL1 Background Process

Phase 1 - Create Tender Control

Note:

This step cannot be bounded by thread range but must execute across the entire population of staging details. Therefore this step in the process is designed so that all parallel threads attempt to execute it at the same time but only one thread succeeds to avoid creating duplicate tender controls.

This step creates all tender controls required by the upload records as follows:

Group Error. This technique allows for an easier recovery from a setup error that may affect a large volume of records in a single transmission. Capturing the error only on a single designated record requires only this record to be set back to Incomplete once the setup issue is corrected. It is important to note that the transmission group is not processes if at least one of the records in the group is in Error status.

Fastpath:

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

Phase 2 - Determine Tender Account

After all tender controls have been created the second step attempts to transition all incomplete records to the pending state.

Each incomplete staging record is processed as follows:

Fastpath:

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

Note:

This step is designed to support execution in parallel threads based upon the sequence number portion of the staging table prime key.