Professional Documents
Culture Documents
1] Modified 12-MAY-2009 Type WHITE PAPER Status PUBLISHED In this Document Abstract Document History R12 Payment Process Request - Functional and Technical Information Overview Submitting a Single Payment Process Request Document Selection Payables Build Payments - Payments Format Payments - Payments Confirm Payments - Payables
Applies to:
Oracle Payables - Version: 12.0.0 to 12.1 Information in this document applies to any platform.
Abstract
This whitepaper provides an overview of the Payment Process Request (PPR) processing in Payments in R12. It will cover technical details of PPR processing and the different tables involved during the process.
Document History
Author : Lakshmi Nilacantan Create Date 01-MAR-2009 Update Date 07-MAY-2009
Overview
Under Funds disbursement page, users can submit Payment Process Requests (PPR) to generate payments. There is an option to submit a single Payment Process Request or schedule Payment Process Requests. There are four steps in the processing of a PPR. a) Document selection b) Build Payments c) Format Payments d) Confirm Payments Document selection and Confirm Payments are handled by Payables (AP) code while Build Payments and Format payments are handled by Payments (IBY) code.
At the end of this step, the valid statuses are a) Invoices Pending Review or b) Cancelled - No Invoices Selected or c) Other statuses from missing information such as Missing Exchange rates If PPR status is Cancelled-No Invoices Selected, there are no valid actions available. For others, the actions available are a) Terminate the PPR or b) Modify / proceed to submit the PPR and start the build process.
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 Profile Assignment: Code: IBY_ASSIGN_PUB If the payment process request has the internal bank account and payment profile assigned to it, the same is assigned to all the documents in the PPR. If a default internal bank account and PPP were not provided when submitting the PPR, Oracle Payments attempts to default the values. If it cannot find a default value for all the documents, the PPR is set to INFORMATION REQUIRED status. The display status of the PPR is Information Required - Pending Action User should complete the missing information and Run Payment Process to continue. b) Document Validation Code: IBY_VALIDATIONSETS_PUB During this step, Oracle Payments validates all the documents using Payment Method based validations and then payment format based validations.. b.1 - If all the documents pass validation, all the documents are set to a status of VALIDATED and the request status is set to Documents Validated. b.2 If there are any validation failures, Oracle Payments uses the system option used while submitting the PPR to determine the next action. The DOCUMENT_REJECTION_LEVEL_CODE of the PPR can have the following values which determine how the document processing will continue when there is a validation failure REQUEST - Reject all documents in this PPR DOCUMENT - Reject only the document in error PAYEE - Reject all the documents related to the supplier NONE - Stop the request for review b.2.1 REQUEST The status of the payment process request is updated to Failed Document Validation. Oracle Payments calls the calling application and AP releases the rejected documents so they can be paid through another Payment process request. b.2.2 DOCUMENT Oracle Payments rejects all documents that failed validation. Oracle Payments then calls the calling application and AP releases the rejected documents so they can be paid through another Payment process request. The rest of the documents are set to VALIDATED status and the ppr is set to Documents Validated status.
b.2.3 PAYEE Oracle Payments rejects all documents for the supplier that had one or more documents that failed validation. Oracle Payments calls the calling application and AP releases the rejected documents so they can be paid through another Payment process request. The rest of the documents are set to VALIDATED status and the ppr is set to Documents Validated status. c) Create Payments Code: IBY_PAYGROUP_PUB The validated documents are then grouped into proposed payments based on the grouping rules, both user defined and hard coded. Example: If exclusive_payment_flag = Y on a document, its paid on a separate payment. It then numbers the payments (internal identifier not the check numbering) and validates the created payments. Records are inserted into IBY_PAYMENTS_ALL that holds the payment information for the selected documents. The build program then updates the IBY_DOCS_PAYABLE_ALL table with the payment_id and formatting_payment_id values that corresponding to the payment that pays the document. IBY_PAYMENTS_ALL links through payment_service_request_id. Key Columns: 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 The PAYMENT_REJECTION_LEVEL_CODE can have the following values which determine how the payment processing will continue when there is a validation failure REQUEST Reject all payments in the request PAYMENT Reject only those payments in error NONE Stop the request for review Request Entire PPR is rejected. Oracle Payments raises a business event that calls AP to release the documents. The status of the payment process request and proposed payments is updated to REJECTED. Payment Payments that failed validation are rejected and AP releases the documents that belong to the payment that failed validation. The other payments are accepted. The accepted payments get a status of CREATED. None Payments that failed Validation are set to Failed Validation and allows for user intervention. Status of the PPR is set to PENDING REVIEW If in the PPR setup, Stop Process for Review After Creation of Proposed Payments is enabled,
the PPR status is set to Pending Proposed Payment Review. This status prevents further processing until user takes action. If this option to stop for review is not enabled, the status of the PPR is set to Payments Created. In this status, payment instruction can be created for the PPR.
Copyright 2008 Oracle. All rights reserved. Oracle is a registered trademark of Oracle. Various product and service names referenced herein may be trademarks of Oracle. All other product and service names mentioned may be trademarks of their respective owners. Disclaimer: This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle does not warrant that this document is error-free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the prior written permission of Oracle.
Related Products Oracle E-Business Suite > Financial Management > Procure to Pay > Oracle Payables
Back to top