Professional Documents
Culture Documents
www.ivruksha.com
Page 1
Greetings Fellow Professionals, Welcome you all to another presentation on Oracle Financials, this time have taken up a feature from Oracle Payables which is Payment Process Request or widely known as PPR. The reason to touch upon this particular feature is that there is very less information available in the documentations provided by oracle, and there is a greater struggle, trial and error method involved in finding out the intended behaviour of the feature. It is not that oracle has not provided the documentation , but as we all know to understand one complete flow of an feature one needs to open up multiple user guides, implementation guides, reference guides, etc to get that information, I have tried to compile those information that are relevant to payment process request from various such oracle related documentations. Even though I have not mastered this feature, I would like to share what I have understood till date on this feature to fellow professionals, as it could be of some help and reference. I do not want this to sound like a formal whitepaper, therefore taken a liberty of write the same in a manner that would be comfortable for the readers, have adopted an organised approach till the end of the document. Having said all this, I am sure this document is not 100% complete, there are greater things which I have not explored, and it is purely an attempt to share in areas where I have stumbled upon. The document contains only conceptual understanding of the feature, the detailed demonstration with step by step screen shots have already been uploaded in the website (www.ivruksha.com). Take your time in going through the presentation and please point out mistakes that are available in the document, so that one can have better and correct understanding of this feature and no one gets misguided. Please fire your feedback to the Author and the Site Administrator at ivruksha@gmail.com
www.ivruksha.com
Page 2
Generic Overview
Introduction Oracle Payments Is it a new Module? Oracle Payables Vs Oracle Payments Procure to Pay Cycle Types of Payment Mode of Payment Why oracle payables does not provide Cash mode of payment? Methods of Payment 6 6 6 7 7 7 8 8
Functional Overview
What is a payment process request? What is the need of Payments in batches or Payment Process Request? Payment Batches in Release 12 How can one make Multiple payments or payments in batches? Payment process request is controlled by Payables or Payments module? How Payment processes Request in Release 12 differ from Payment Batches in Release 11? What are the different selection criteria available in Payment Process Request for selecting invoices eligible for payment? When an invoice is eligible to be picked up by Payment Process Request? Benefits of Payment Process Request Disadvantages of Payment Process Request Prerequisites for making Payment Process Request New enhancements in Payment process request not available in earlier versions Different statuses of Payment Process Request Different Statuses of Payment Instruction Process flow of Payment Batches in Release 11 Process flow of Payment Batches in Release 12 Payment Models supported by Oracle Payments 10 10 10 10 10 11 12 13 13 15 16 16 16 17 17 17 17
18
Technical Overview
Has the payment architecture undergone any changes in Release 12 Table Names involved in Payment Process Request Payments Integration with XML Publisher
www.ivruksha.com
Page 3
www.ivruksha.com
Page 4
GENERIC OVERVIEW
www.ivruksha.com
Page 5
www.ivruksha.com
Page 6
www.ivruksha.com
Page 7
Did oracle consider about the option of company making a credit purchase and later followed by a payment after a week in CASH? This is a very genuine transaction; however no direct functionality is available to satisfy the same.
There are other logical explanations as well; the most common one is, it is not the Best Business Practice to be adopted, as control on physical cash and cash related documentations is subject to human intervention and manipulation. Methods of Payment There are three different types of payments available to the user when they make a single payment using Payment Workbench, they are Manual, Quick and Refund. Refund is actually a negative payment, whereas manual and quick payments are normal payments. There are few differences between Manual payment and quick payments, which is not being discussed here.
www.ivruksha.com
Page 8
FUNCTIONAL OVERVIEW
www.ivruksha.com
Page 9
www.ivruksha.com
Page 10
How Payment process Request in Release 12 differ from Payment Batches in Release 11? Invoice Selection
Release 11 Invoice selection must be the made as per the payment requirements and other attributes Release 12 Invoice selection is not dependant on the how the payment is going to be made at later
stage, it selects all invoices which are eligible for payment, the grouping of selected invoices are taken care at later stage, and payment instructions are printed accordingly. Look and Feel
Release 11 No field for Payment Process Profile Release 12 New field for Payment process profile exists.
Centralised Payment System
Release 11 Payment batches can be created only for invoices from Oracle payables module Release 12 Payment process request can pick up eligible transactions from other related modules and
also from different operating units which was not possible in earlier releases. Transmission of Payment Instruction File
Release 11 It involves customization with the assistance from any third party software Release 12 Formatting and Transmission is carried out by the Oracle Payments module itself.
Check Printing
Release 11 Owned by Oracle Payables Module Release 12 Owned by Oracle Payments Module
And many more....
www.ivruksha.com
Page 11
When an invoice is eligible to be picked up by Payment Process Request? An invoice which is complete in all respects are eligible for payment, below are the conditions which are to be satisfied in order for an invoice to be available for selection in the Payment process request: Invoices that are approved (Force Approval or Approved through Invoice workflow) Invoices that are validated (Need not be Accounted) Invoices which are due for payment as per the payment terms Invoices, which have outstanding balances. (not fully paid invoices) All holds placed in the invoices are released (Manually or Automatically)
Benefits of Payment Process Requests Payment process request is provides us with many benefits. It is really worthwhile to spend some time in few of those benefits as we will speak about this more and more in further discussions to come. Full Audit Trail - It acts as a one point stop for administering all payments. Also there is a greater visibility in the payments, as one can very clearly observe the status of pending payments and payment completed via payment dashboard. The complete process can very easily be crossverified with final results. Centralized Payment System - Oracle payments act as a centralized payment system, where all payments are carried out through Payment Process Requests. We need to understand what is centralized. The following payments can now be made very easily via payment manager, www.ivruksha.com Page 13
Flexible Validation Model - Apart from pre-defined validations available in the system by default, users can have their own validations. The main purpose of this flexible validation model is that to avoid errors at the very beginning of the process, rather than waiting till the last step and starting over again from the beginning. So that all errors are corrected at the earliest and providing no bottle necks at the end. Payment Process Request Templates - Users can create a template with all the relevant parameters, which they will be providing in Payment Process Request at run time. This template can be referenced next time when the user creates a pay run, all parameters gets defaulted to the Payment process request, and user just has to hit the submit button. Based on the invoice selection criteria one can create templates as required. It saves time spent on creating Payment Process Requests by the users. Below is the Screenshot of the Payment Process Request Template
Payments Dashboard - Payments dashboard provides a complete overview on the status of the payment process requests that are in place on a particular day and the actions to be taken on them if required. This snapshot enables the user to monitor pending actions that are to be completed. Also the dashboard provides with links for users to navigate to the pages directly without any need to remember navigations.
www.ivruksha.com
Page 14
Schedule Payment Process Request - Payment process Requests can be scheduled like any other concurrent program from the Payment Manager dashboard. The only prerequisite for scheduling the Payment Process Request is that one need to have a template defined for it, upon submission of the request, system creates a Payment Process Request with an auto generated name preceded by the template name. Request will be run as scheduled, users can prefer a notification to be sent to them, while scheduling the request or they can monitor the request from the monitor requests link on the dashboard. Below is the Screenshot of the Scheduling Payment Process Request
www.ivruksha.com
Page 15
Bank Account must be created for Payment Payment document must be created for the Bank Account Payment Process Profile must be defined Payment exchange rate must be defined in case of multi currency payments. Payment Method must be decided Payment instructions for printing should be defined. Invoices eligible for payment must be available
And the most important prerequisite is to be on the latest Patch set. As we all know Release 12 is a product with less number of new functionalities and more number of bugs, one has to be on the latest patch set always, so that the functionality can work in an intended way without any technical hiccups. Brief information on the available patches and known issues are given at the later stage as a ready reference. New enhancements in Payment process Request not available in earlier versions? The major enhancement which I have personally felt is due to Multi Org Access Control (MOAC) feature. In release 11, one can make payments to invoices belonging to single operating unit only, whereas in release 12, one is given with the choice of selecting invoices from more than one operating unit and more than one legal entity. The above is possible by having a security profile with more than one operating unit attached to the responsibility. Apart from above, this feature has retained all functionalities from earlier versions. Different statuses of a Payment Process Request Payment Process Request when executed updates the status which is being performed currently, so that user is aware of the progress of the payments and updated if manual intervention is required in between. Below are the few status names which Payment process request uses while performing the payment operations: New This is the initial status of the PPR, which means no processing has began. Selecting Scheduled Payments This status indicates that PPR is currently engaged in looking for eligible invoices for payment. Invoices Selected This status indicates that PPR has selected invoices that are due for payment or as per the invoice selection criteria. Assembling payments This status indicates that PPR is currently engaged in generating payments for the selected invoices. Page 16
www.ivruksha.com
Different statuses of Payment Instruction Printed This status indicates that payment instruction has been printed Submitted for printing This status indicates that payment instruction has been submitted for printing Created Ready for Printing This status indicates that payment instructions are generated and available for printing Formatted Ready for Printing This status indicates that payment instructions are formatted and available for printing. Formatted Ready for transmission This status indicates that payment instructions are formatted and ready for transmission. Process Flow of Payment Batches in Release 11 Invoice Selection = > It selects invoices based on how it needs to be paid along with other criterias. Build Payments = > From the above selection similar invoices are grouped together for payment. Format Payments = > Payments are formatted as per the grouping done at the build stage. Print Documents = > Print the payment document after formatting Confirm Payment Batch = > Confirm the payment batch to complete the payment batch process. Process Flow of payment process Request in Release 12 Invoice Selection = > It selects invoices that are available in payables eligible for payment Build Payments = > from the list of invoices selected from the previous step, the invoices are grouped in to payments based on the various criterias. Build Payment Instruction = > Built payments are further grouped in to Payment instructions. Format Payment Instruction = > the above grouped payment instructions are later converted in to well formatted files through XML data extract. Transmission of payments = >Transmission of electronic payment files or printing checks are done. Payment Models supported by Oracle payments Completely Decentralized Invoices belonging to different operating units are kept separate through invoice selection, build payments and format payments stages. Shared Service Centre Invoices belonging to different operating units are kept together. Payment Factory Invoices belonging to different operating units are kept separate through invoice selection and build process, however they are clubbed during the format or payment instructions creation stage.
www.ivruksha.com
Page 17
www.ivruksha.com
Page 18
Refer to the below section in this document: What are the different selection criteria available in Payment Process Request for selecting invoices eligible for payment? TAB: PAYMENT ATTRIBUTES
Payment Date This will be the date on which payments will be made. This date will also appear on the payment document and Payment instruction also.
www.ivruksha.com
Page 19
A starting voucher number that the system uses to incrementally number the resulting payments. If you enter 1, then 1 is used as a starting number each time this template is used. If you use voucher numbers, number you assign
to a payment document to uniquely identify it. If you use automatic sequential numbering, Payables assigns a voucher number and you cannot update it.
www.ivruksha.com
Page 20
In case of user type exchange rate, the user submitting the payment process request has to provide the rate which the system has to take in to account for other automatic computations. There may be multiple currency payments being made, hence conversion rates between each of those foreign currencies and functional currencies have to be provided for a successful completion of payment process request. Following are details you are required to provide: Payment Currency, Ledger Currency and Rate TAB: PROCESSING
Maximize Credits If this check box is selected in the Process Automation subtab, then during invoice selection, if there is any credit for a payee after interest and payment withholding calculations, the system groups all scheduled payments for the payee site together to be paid on one payment, based on grouping rules. If the sum is negative, the system reduces the credit amount to zero. Stop Process for Review after Scheduled Payment Selection If this check box is selected in the Process Automation subtab, the pay run pauses after invoices have been selected and the status of the payment process request updates to Invoices Pending Review. Clicking on the Start Action icon navigates you to the Payment Process Request: Selected Scheduled Payments page to review the invoices selected for scheduled payment, add or remove scheduled payments from the request, or change payment amounts. Calculate Payment Withholding and Interest during scheduled Payment Selection If this check box is selected in the Process Automation subtab, the following calculations occur: For each scheduled payment subject to interest, the system calculates the interest due. For those invoices subject to withholding, the system calculates withholding tax for invoices that belong to an operating unit where tax is withheld at payment time. Stop Process for review after creation of proposed payments If this check box is selected in the Process Automation subtab, the Build Payments program runs to group the invoices into payments and the pay run pauses after payments have been built. Clicking on the Start Action icon navigates you to the proposed payments in the Review Proposed Payments: Payment Process Request page of the Payment Process Requests tab.
Document
During the execution of the payment process request, if by any reason validations performed on the documents payable has negative results, then you instruct the system on what is to be done next, the available options are: Reject Only Documents with errors, Stop process for review, Reject all documents for payee when any document fails and Reject all documents in request
Payment
Similarly for payments system performs validations, and likewise on negative results one of the below instructions are to be selected for the system operation to proceed further. The available options are: Stop process for review, Reject all payments for payee when any payment fails, Reject only payment with errors and Reject all payments in request TAB: ADDITIONAL INFORMATION
These are DFF fields which do not have any predefined usage; it is for information / data capture purposes only. The DFF name is Invoice Selection (AP_INVOICE_SELECTION_CRITERIA) XML PUBLISHER TEMPLATE It is the layout designed in a well formatted file. The template will pick the relevant data upon execution. One can decide as to what the fields the layout must contain are and what must be hidden. It is like a seeded report with option to modify as per the requirement. Technical expertise is required to modify an XML publisher Template.
www.ivruksha.com
Page 22
PAYMENT FORMAT Oracle payment uses many different formats for various needs, of all the formats following are frequently used ones almost in every payment, they are: Format for Printed Checks Format for Electronic Funds Transfer Format for Remittance Advice XML publisher templates are available for every format, which can be modified as per the requirement. Payment Format Type Selection Screen
www.ivruksha.com
Page 23
PAYMENT PROCESS PROFILE A payment process profile, is a payment attribute assigned to documents payable, which specifies handling of the documents payable, payments and payment instructions by oracle payments. Payment process profiles include specifications for payment formatting and transmission. The selection of a payment process profile is driven by the payment method assigned to a document. Payments are built from documents payable that have the same payment process profile. Oracle Payments seeds a limited number of payment process profiles.
www.ivruksha.com
Page 24
www.ivruksha.com
Page 25
BANK, BANK BRANCH, BANK ACCOUNT AND PAYMENT DOCUMENT In order to make a payment, one must have a Bank Account. Even though it is ideal for any business to make a cash payment, the same is not available in oracle payments or cash management as straight fit. Hence one must setup Bank, Bank Branches and Bank Account. Also, Bank Account alone is not enough for making payment, one must setup check or wire sequence numbers by configuring Payment documents. OTHER TERMINOLOGIES OF SOME USE: Payer and Payee Payer The one who initiates the payment Payee The one who received the payment made by payer. When we use Receivables module we become the Payee when we use payables module, we become payer Pay run It is a process of selection of invoices for making payment. Payment Systems Payment system indicates the third party or the financial institution which will process the payment upon transmission. Ideal payment systems are Banks.
www.ivruksha.com
Page 26
TECHNICAL OVERVIEW
www.ivruksha.com
Page 27
The above changes are purely due to introduction of centralized accounting engine through Subledger Accounting and introduction of new Funds disbursement process in Oracle Payments. TABLES involved in Payment Process Request In order to complete a payment process request there are multiple stages involved in the process, at each stage there are certain tables that gets updated with the necessary data, flags, stamping etc... Let me share few such information on the same, which I have observed so far,
Creation of Payment Process Request through Payment Manager When Invoices are selected based on the selection criteria provided Of the Invoices got selected, if you are manually removing few invoices not want to be paid When payment is completed When Payment Instruction is completed
Oracle payments integration with Oracle XML Publisher XML publisher has replaced oracle reports. Unlike in earlier versions where assistance of technical consultant is required to modify the reports, one can make changes to seeded templates using e text editor with less technical assistance, however knowledge on basic XML publisher is required for the Functional Consultant. Payment Instructions are to be generated through XML Publisher templates in release 12.
www.ivruksha.com
Page 28
AUTHORS CORNER
www.ivruksha.com
Page 29
When one must approach Oracle Support for assistance and what are the prerequisites one must take care before approaching for assistance? When you have exercised all the above options and did a reasonable search on the Metalink with the error or error message, and still you are unable to fix the issue by yourself, it is time to reach Oracle support with all of the output / log files / screen shots you have obtained on the issue for faster resolution.
www.ivruksha.com
Page 30
Frequently Asked Questions Does the module ipayments is totally scrapped due to introduction of Oracle Payments module? Not exactly, the module ipayments does not exist in release 12 now, however the database details, table structures still exists, therefore one cannot say that ipayments is totally scrapped. Is there a direct relation between invoices and the payment process profile? No, there is no direct relationship. While creating invoices one is never asked to provide the details of the payment process profile in the Invoice workbench. Payment process profile detail is collected only at the stage of making payment. Having said there is no direct relationship between invoices and payment process profile, details mentioned in the invoices must match with the details mentioned in the Payment process profile at the time of payment, else it is not possible to complete the payment. Oracle payments are stated as Centralized Payment System, what are the other payments that it takes care of? Apart from making payments to invoices in payables, oracle payments module takes care of Bank Account Transfers (BAT) from Cash Management and receipts through credit cards from receivables. It also integrates with third party systems. However Payroll is excluded from the Centralized Payment system. Does payment process profile is required for all payments or is it optional? Payment process profile is mandatory for all payments. However it is not required for a refund transaction made in payment workbench since it is not a payment. www.ivruksha.com Page 31
How can one edit the existing XML templates using Microsoft Word? One needs to install an Add on software which is available for free download from metalink. This software is known as eText. Can one setup a payment format in a manner as per the client needs? There is a feature called validation in oracle payments which stipulates that every payment format must satisfy the seeded validations. These validations are performed so that the payment file is not rejected by the Payment systems. What is the difference between Build Payment process and Payment Instruction Process? There is not much difference between the two processes, both does the same function in separate ways. The function performed by them are Grouping of invoices. Build payment process groups the invoices for payment in certain way first, followed by the Payment instruction process which again regroups depending on how it is to be paid. Which process decides on how the invoices needs to be paid in the Payment Process Request? Invoice Selection process selects invoices based on due dates, Build process groups based on similarities on the selected invoices, whereas payment instruction process regroups invoices based on how the invoices needs to be paid. Is Bills payable available in payment method definition a new feature in release 12? No it is not a new feature; it has replaced Future Dated Payments used in Release 11. What is the difference between payment method defaulting rules and Usage rules under payment method definition? In Payment method defaulting rules, system performs the process of defaulting a payment method only. In Usage rules of payment method definition, system controls what values must be shown in the payment method LOV. Why at all we need Payment Process Profile, when the same is not used in the previous releases, and more than that it is a mandatory setup for making a payment, is there any logic behind?
www.ivruksha.com
Page 32
Thank you for your Time and Patience AND Congrats on making it to the last page
Please shoot your views, mainly criticisms and incorrect statements on the document, so that the same can be corrected at the earliest. Author & Site Administrator: ivruksha@gmail.com
www.ivruksha.com
Page 34