The following diagram shows the possible lifecycle of a payment event upload staging record.
Uploaded. A payment event staging record is initially created in uploaded state. The C1-PEPL0 process sets it to incomplete once it determines its tender account and distribution rule details.
Note that if your implementation chooses not to use the C1-PEPL0 process, payment event staging records should be created in incomplete state.Incomplete. The C1-PEPL1 process sets an incomplete record to pending once it links it to a tender control and determines its tender account, if not already populated by the C1-PEPL0 process.
Pending. The C1-PEPL2 process sets a pending record to complete once all processing logic is executed and a payment event is linked to it.
Complete. When processing of the staging record is complete the record is in the complete state. This is a final state.
Error. A payment event staging record may be set to Error from Incomplete or Pending states by the C1-PEPL1 and C1-PEPL2 processes respectively.
Audit. A payment event staging record may be set to Audit from the Uploaded state by the C1-PEPL0 process. This only occurs if the original staging record has been transformed into multiple staging records by one of the Determine Distribution Rule algorithms.
Refer to To Do Entries Instead of Exceptions for more information on how To Do entries are used to capture processing errors.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]