Three-Step PUPL Processing

The Payment Upload (PUPL) batch faces significant performance issues when the number of payment segments are huge for a single payment event or payment. To handle this performance issue, the system provides an alternative three-step approach wherein you need to execute the following batches in the specified sequence:

1. PUPL - The following new parameters are added in the PUPL batch:

   • Three Step Batch Processing (Y/N) - Used to indicate whether you want to use three-step approach for uploading payment records from the staging area. The valid values are Y and N. If you do not specify the value for this parameter or set the parameter value to N, you need to just execute the PUPL batch in the traditional manner.

     However, if you set the parameter value to Y, you need to execute the PUPL, PUPLDF, and PUPLCMPL batches in the specified sequence. In the three-step approach, the PUPL batch creates the deposit control, tender controls, payment events, tenders, and payments in the staging area using the payment records from the pre-staging area.

     The status of the payment is set to Step in Process. In addition, the payment distribution algorithm is triggered and the payment distribution records are created in the CI_​PAY_​DIST_​TEMP table.

   • Division - Used when you want to create payments for accounts belonging to a particular division.

   • Bulk Insert Count - Used to indicate the number of records that you want to insert at once in the CI_​PAY_​DIST_​TEMP table.

   For more information about the batch, refer to Oracle Revenue Management and Billing Batch Guide.

2. PUPLDF - This batch considers the payment distribution records from the CI_​PAY_​DIST_​TEMP table and accordingly creates the payment segments. In addition, it creates the financial transaction for each payment segment and sets its status to Frozen. If any of the payment segment returns an error, the system will not hold the creation of other payment segments in the payment. For more information about the batch, refer to Oracle Revenue Management and Billing Batch Guide.

3. PUPLCMPL - This batch changes the status of the payment to Frozen or Error depending on whether its payment segments and financial transactions are successfully created in the system. If all payments in a payment event are successfully created, the status of the corresponding deposit control, tender control, payment tender, and payment staging records is set to Complete. If any error occurs while creating payment event for a payment record, the status of the deposit control, tender control, payment tender, and payment staging records is changed to Error. In addition, the status of the payment record in the pre-staging area is changed to Error in Staging. For more information about the batch, refer to Oracle Revenue Management and Billing Batch Guide.

Related Topics

Parent Topic: The Big Picture of Payments