R12 payment process request-function and technical information (Document ID 1537521.1)

In this document

Abstract

History

Details

Submit a single payment processing request

Payment document Selection-Accounts payable

Create payment-payment

Format payment-payment

Confirm payment-Accounts payable

References

Applies to: Oracle payables-version 12.0.0 to 12.1.0 [release 12.0 to 12.1]
Information in this document applies to any platform.
Abstract

This White Paper provides an overview of the payment process requests (PPR) that process payments in R12. This article includes the technical details of the PPR processing process and the tables involved in this process.

History

Gavin Zhang

Creation date: 15-Mar-2013

Updated on 15-Mar-2013

Details

Payment process request

Summary

On the Fund expenditure page, you can submit a payment process request (PPR) to generate a payment. You can choose to submit a single payment processing request or schedule a payment processing request.

There are four payment processing requests.
A) Payment document Selection
B) establish payment
C) format the payment
D) confirm payment

Payment document Selection and confirmation payment are handled by the account payable (AP) code, while the establishment payment and formatting payment are handled by the payment (iby) Code

Submit a single payment processing request

Required project-name of the payment processing request, payment deadline

Payment property sub-tag-payment date, Payment Exchange Rate type.
Payment processing configuration file and payment bank account are optional fields.

Under the processing sub-tag, options can be used to stop processing after the document is selected/paid, and how to create payment instructions.

Under the verification failure result subtab, select the option about how to handle the payment receipt and invoice verification failure that best meets the business requirements.
Click Submit to submit a payment processing request.

Payment document Selection-Accounts payable

Code: ap_autoselect_pkg

When a payment process request is submitted, a record is created in the ap_inv_selection_criteria_all table. The checkrun_name of the record is the same as the name of the payment process request.

When selecting an invoice, you do not need to specify the payment configuration file and the internal bank account that pays the payment. Users who submit the PPR do not need to know the information. These values can be provided in later payment management.

Select: 
Select an invoice Based on the expiration date, discount date, payment group, and other criteria provided when you submit the PPR. The selection process is executed by the caller.

The selected invoice is stored in the ap_selected_invoices_all table.

Unselected invoices are stored in the ap_unselected_invoices_all table.

Lock:
After payment documents are selected, these invoices are locked to prevent them from being selected by other checks. The checkrun_id of PPR is updated to ap_payment_schedules_all.checkrun_id of the selected Payment document.

Review: 
If the payment process request is set to "stop the review process after the planned payment is selected", the process is stopped for user review. The PPR status changes to "invoice pending review ".

If the "Stop review process after planning payment" option is not enabled, after the invoice is selected, the setup program will be automatically submitted.

If no invoice meets the selected criteria and no payment plan is selected, PPR will be automatically canceled and the status will change to "canceled-unselected invoice ".

If you need to review the selected payment plan, click submit after the user reviews the selected payment plan, and the AP calls the ibybuild program.

Verification status and activity
At the end of this step, the valid status is
A) The invoice is awaiting review or
B) cancel-unselected invoice or
C) other statuses that show missing information, such as missing exchange rates

If the PPR status is "cancel-unselected invoice", no valid action is taken.
For other States, actions that can be taken are
A) End the PPR or
B) Modify/continue submitting PPR and start the payment creation process.

Create payment-payment

Code: iby_disburse_submit_pub_pkg

The establishment of payment will insert a record in iby_pay_service_requests. In this record, call_app_pay_service_req_code = checkrun_name.

Primary Key: payment_sevice_request_id

Main column:
Call_ap_pay_service_req_code-> PPR name
Calling_app_id
Payment_service_request_status
Internal_bank_account_id
Maximum_payment_amount
Minimum_payment_amount
Document_rejection_level_code
Payment_rejection_level_code
Require_prop_pmts_review_flag
Create_pmt_instructions_flag

Note: The Status displayed by this PPR is generated by ibyvutlb. Pls.

The PPR status is displayed on the panel by using the get_psr_status function.

The values provided to payment_service_request_status mainly include:
Payment_service_request_status
------------------------------
Documents_validated
Information_required
Inserted
Payments_created
Pending_review
Terminated
Validation_failed

Create a payment program to store the payment information in the iby_docs_payable_all table, and connect to the payment service request table through the column payment_service_request_id.

Main column:
Payment_service_request_id
Calling_app_doc_ref_number-> invoice_number
Document_payable_id
Document_status
Payment_currency_code
Payment_amount
Document_amount
Exclusive_payment_flag
Payment_method_code
Payment_id
Formatting_payment_id
Ext_payee_id
Payee_party_id
Payment_profile_id
Internal_bank_account_id
Calling_app_doc_unique_ref2-> invoice_id
Calling_app_doc_unique_ref3-> payment number


A) internal bank account/payment process configuration file (PPP) allocation: 
Code: iby_assign_pub

If a payment process request has an internal bank account and a payment configuration file (PPP) is assigned ), all payment documents in the PPR are allocated with the same internal bank account and payment configuration file.

If no default internal bank account or PPP is found when submitting PPR, Oracle will look for the default value. If the default values of all payment documents cannot be found, PPR will be updated to the "required information" status. The information displayed by the PPR is "required information-waiting for action ".
The user should fill in the missing information and continue the payment process.

B) Payment document verification 
Code: iby_validationsets_pub

In this process, payment is verified using a verified payment method and a verified payment format.

B .1-if all documents pass verification, the status of all documents is updated to "verified", and the status of PPR is updated to "verified '.

B .2-If verification fails, Oracle payments uses the system configuration option used when submitting PPR to determine the next step.

When verification fails, PPR's document_rejection_level_code uses the following values to determine how to proceed with the Payment Document
Request-reject all payment documents for this PPR
Payment Receipt-only rejected wrong payment receipt
Recipient-decline all payment documents related to this supplier
None-stop the request for review

B .2.1-Request
The status of the payment process request is updated to "file Verification Failed ". Oracle payments calls the calling program, and the AP releases rejected documents so that other payment process requests can pay for these documents.

B .2.2-payment documents
Oracle payments rejects all documents that fail verification. Oracle payments calls the calling program, and the AP releases rejected documents so that other payment process requests can pay for these documents. The status of other documents is updated to "verified", and the PPR status is updated to "verified ".

B .2.3-payee
If one or more documents fail to be verified, Oracle payments rejects all payment documents from the supplier. Oracle payments calls the calling program, and the AP releases rejected documents so that other payment process requests can pay for these documents. The status of other documents is updated to "verified", and the PPR status is updated to "verified ".

C) create payment 
Code: iby_paygroup_pub

Verified payment documents are divided into suggested payment according to grouping rules. Grouping rules include user-defined and default system composition.

For example, if exclusive_payment_flag = Y, the payment receipt must be paid separately. Then, the document number (internal identification, not the check number) is verified and the created payment is verified.

Insert the iby_payments_all record to save the payment information of the selected Payment document.

The Payment Program will update the payment payment_id and formatting_payment_id values related to the payment for this document in the iby_docs_payable_all table.

Associate iby_payments_all with payment_service_request_id.

Main column:
Payment_service_request_id
Payment_id
Payment_method_code
Payment_status
Payments_complete_flag
Payment_amount,
Dicount_amount_taken
Internal_bank_account_id
Ext_payee_id
Payment_instruction_id
Payment_profile_id
Void_date

When verification fails, payment_rejection_level_code uses the following values to determine how the payment process continues.
Request-reject all payment documents for this PPR
Payment Receipt-only rejected wrong payment receipt
None-stop the request for review

Request-the entire PPR is rejected. Oracle payments submits a business event to call the AP to release these payment documents. The payment process Request status and suggested payment are updated to "REJECTED ".

Payment-payment for verification failure will be rejected. The AP releases the Payment Document for the payment that is not verified and accepts the payment that has passed the verification. The status of the accepted payment is updated to "created ".

None-the payment status for failed verification is updated to "Verification Failed" and user intervention is allowed. The PPR status is updated to "waiting for review"

If you enable the option "stop the process for review after creating a suggested payment" in the PPR settings, the PPR status changes to "Wait for the proposed payment review ". The PPR will be suspended to prevent further processing until the user takes action. If this option is not enabled, the PPR status changes to "payment already created ". In this status, you can create a payment instruction for this PPR.

Format payment-payment

Code: iby_payintsr_pub, iby_checknumber_pub

After submitting a PPR, you have two options:

Create_pmt_instructions_flag can be Y or N
Y-after the payment is created, the payment instruction is automatically generated.
N-the application waits for a standard request to submit the payment instruction.

Iby_payment_instructions_all stores the payment instruction information.

If PPR is set to automatic submission, payment_service_request_id is updated to iby_payment_instructions_all, and the program will specify a payment instruction for PPR. In this case, the payment instruction is associated with PPR through payment_service_request_id.

If the PPR is processing the settings under the sub-tag, the user submits a standard request to establish a payment instruction. After the request is indicated to be submitted, the payment instruction associates the selected payment with the PPR through the payment instruction. In this case, the Association is implemented through iby_payments_all.payment_instruction_id.

Main column in iby_payment_instructions_all
Payment_instruction_id
Payment_profile_id
Payment_instruction_status
Payments_complete_code
Payment_count
Print_instruction_immed_flag
Transmit_pai_immed_flag
Internal_bank_account_id
Payment_document_id
Payment_date
Payment_reason_code
Payment_currency_code

Format:
The following process occurs during formatting.

A) pay by no.-Check no.
B) create XML extraction information
C) Send the extracted information to XML Publisher
D) Oracle XML Publisher (BI Publisher) application format template
E) BI Publisher format and store output information
F) Oracle payments updates the payment instruction status and payment status. If successful, the status of the payment and payment instructions is "formatted ".

Print check:
A) In this step, the user can load the printed consumables to the printer and print the check.
B) Check whether check printing is successful. If it fails, print it again.

Confirm payment-Accounts payable

Code: ap_pmt_callout_pkg

Record the printing status of the check to confirm the payment. Oracle payments calls ap_pmt_callout_pkg.payment_completed to confirm the payment.

Perform the following steps:
A) Specify the serial number/value-file number.
B) update the corresponding data in the iby table to the ap_checks_all table.
Checkrun_name = PPR name in the iby table, checkrun_id = checkrun_id in the iby table.
C) Insert the data of the check to the ap_invoice_payments_all table.
D. Update ap_payment_schedules_all of the invoice to display the payment information and status.
E) release the payment documents paid by PPR by setting checkrun_id as null in the payment plan.
F) Update the ap_invoices_all table to display the payment status.
G) Delete the data in the ap_selected_invoices_all table.
H) Delete the data in the ap_unselected_invoices_all table.

R12 payment process request-function and technical information (Document ID 1537521.1)