Professional Documents
Culture Documents
Page | 1
Table of Contents
1. Introduction 3
2. What is PPR (Payment Processing Request) Process and why we need that? 4
3. Create New Check Format 6
4. Create New Bank and Branch 10
5. Create New Bank Account 17
6. Create New Payment Method 33
7. Create Payment Process Profile 38
8. Create Supplier and Supplier Site 50
9. Update Payment Method in Supplier 55
10. Run PPR Process 60
Page | 2
1. Introduction
Section 1 – Introduction
This will cover the introduction and high level process of Payment Processing Request process.
2) What is PPR (Payment Processing Request) Process and why we need that?
Section 2 - Setups
This will cover all set ups required to run the PPR process.
Section 3 – Demo
This will cover demonstration of PPR process.
Page | 3
2. What is PPR (Payment Processing Request) Process and why we
need that?
Payment Processing Request process will allow to pay the multiple invoices same time. This is the
feature in R12. Earlier we used to have payment batches to pay the multiple invoices.
Unlike 11i payment batches, PPR process will allow us to select the multiple invoices for payment by
selection criteria and we can pause the invoice selection and payment.
Payment manager can review the invoices selected and he can add or remove those invoices from the
Payment Process. Payment manager can individually dismiss the payment if necessary, and restart the
payment build process.
1) Document Selection:
Invoices will be selected based on the due date, discount date, pay group and other criteria provided
while submitting the PPR. After selecting the documents, the invoices are locked to prevent
other check runs from selecting the same invoices.
If the PPR has been setup to ‘Stop Process for Review after Scheduled Payment Selection’, the process
stops for user review. Then the status of the PPR is set to ‘Invoices Pending Review’.
If the PPR has not been enabled to ‘Stop Process for Review after Scheduled Payment Selection’, then
at the end of the invoice selection, build program is submitted automatically.
If no invoices met the selection criteria and no payment schedules selected for payment, the PPR is
cancelled automatically and the status of PPR is set to ‘Cancelled – No Invoices Selected’.
2) Build Payments
A Payment Process Request is a group of documents payable that a source product submits to Oracle
Payments for payment service processing. Program ‘Build Programs’ will get submitted to
process the payments. This program will select the Invoice or similar document that needs to be
paid.
If the Payment Process Request has the internal bank account and Payment Process Profile (PPP)
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 –
Page | 4
Pending Action’. User should complete the missing information and run the Payment Process to
continue.
After this, Oracle Payments validates all the documents using Payment Method based validations and
then payment format based validations. If all the documents pass validation, all the documents
are set to a status of VALIDATED and PPR request status is set to ‘Documents Validated’. If
there is any validation failure occurs, then Payment Process Request is updated to ‘Failed
Document Validation’. After that, rejected documents will be released so that another PPR
process will process them.
Validated documents are grouped into proposed payments based on the grouping rules. Payments are
built after the grouping rules. If the PPR setup, ‘Stop Process for Review After Creation of
Proposed Payments’ is enabled, the PPR status will be 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’.
3) Format Payments
When a PPR is submitted, Create Payment Instruction Flag can be either Y or N
Y – Payment Instruction will be automatically created after payments are created.
N – Application waits for standard request submission for Payment Instruction.
After this, Users can load stationery into the printer and print checks at this stage.
4) Confirm Payments
This will record the Print Status of the checks to Confirm the payments.
Page | 5
3. Create New Check Format
Page | 6
Select Formats – Go To Task button.
Page | 7
Enter Format details as required.
Click on Format Code, Name, Data Extract and XML Publisher Template details.
Page | 8
Payment Check Format has been created.
Technical Information:
After creating new payment check formats, data will be inserted into following tables
1) IBY_FORMATS_B
2) IBY_FORMATS_TL
Sql Queries:
select *
from IBY_FORMATS_B
where FORMAT_CODE = 'XRX_PAY_CHK_STANDARD_CITI_1';
select *
from IBY_FORMATS_TL
where FORMAT_CODE = 'XRX_PAY_CHK_STANDARD_CITI_1'
and language = USERENV('LANG');
Page | 9
4. Create New Bank and Branch
Page | 10
Click on ‘Create’ button to create the new Bank.
Page | 11
Enter Country, Bank Name and Bank Number, then click on Save and Next.
A page would pop up for Bank Address. Click on Save and Next.
Page | 12
Then click on Finish button to complete the set up for creation of Bank.
Technical Queries:
After creating the bank, a new record has been inserted into hz_parties table.
Page | 13
iby_ext_banks_v
Click on Create Branch button create the branches for that bank.
Country and Bank Name would come automatically from Bank set up. Click on Continue.
Page | 14
Enter Branch Name and Branch Type.
Enter Branch Address details if any, then click on Save and Next.
Page | 15
Enter Branch Contact details if any, then click on Finish.
Technical Details:
After creating the new bank branch, a new record will be inserted into hz_parties table.
Page | 16
iby_ext_bank_branches_v
Bank Name ‘CITI BANK’ and Branch Name ‘NEW YORK’ has already been created.
Page | 17
Click on Create Button to create the new Bank Account.
select *
from CE_BANKS_V
where BANK_NAME = 'CITI BANK';
select *
from CE_BANK_BRANCHES_V
where BANK_NAME = 'CITI BANK';
Page | 18
Page | 19
Update the Country, Bank name and B
rach name. Then click on Continue.
Enter Bank Account owner which is Legal Entity name, and select Account Use.
Page | 20
Enter mandatory fields which are: Account Name, Account Number, Currency and Check whether
Multiple Currencies Allowed or not.
Page | 21
Enter Cash, Cash Clearing, Bank Charges and Bank Errors account details.
Also, enter Payables Controls details (Multiple Currency Payments, Allow Zero Payments, Maximum
Outlay and Maximum Payment), as displayed in the screenshot.
Rest of the fields in this page are either populated with default values or not mandatory.
Page | 22
Click on Save and Next.
Click on Add Organization Access button to give access this account to multiple operating units.
Page | 23
Then Payables Options and Receivables Options accounting information will be populated.
These values will be retrieved from Accounting Controls set up in the same page.
Click on Apply.
Do the same exercise for other 2 operating units in the same legal entity.
Page | 24
Click on Save and Next.
Page | 25
Bank Account has been created.
select *
from CE_BANK_ACCOUNTS
where BANK_ACCOUNT_NAME = 'XRX_US_OPERATIONS_ALL_USD';
Query to verify, to how many organizations, bank account has been assigned.
select *
from CE_BANK_ACCT_USES_ALL
where bank_account_id = 13001;
Page | 26
Click on Manage Payment Documents.
Page | 27
Enter Name, paper Stock Type, Format, First Available Document Number and Last Available
Document Number details. Click on Apply.
Page | 28
Page | 29
Now 5 Payment Methods have been created.
Page | 30
Page | 31
Update the Format in these Payment Documents.
Click on Update
Page | 32
Update the Format details.
Page | 33
Query to get Payment Document details:
select *
from CE_PAYMENT_DOCUMENTS
where PAYMENT_DOCUMENT_NAME = 'XRX-US-OPER-USD-1';
Page | 34
6. Create New Payment Method
After creating the Bank details, we need to create the Payment Method.
Page | 35
Click on Payment Methods - Go To Task button.
Page | 36
Enter Payment Method Code, Name and Description.
Page | 37
Click on Next.
Click on Finish.
Page | 38
Payment Method has been created.
1) IBY_PAYMENT_METHODS_TL
2) IBY_PAYMENT_METHODS_B
Sql Queries:
select *
from IBY_PAYMENT_METHODS_TL
where PAYMENT_METHOD_CODE = 'P-CARD'
and LANGUAGE = userenv('LANG');
select *
from IBY_PAYMENT_METHODS_B
where PAYMENT_METHOD_CODE = 'P-CARD';
Page | 39
7. Create Payment Process Profile
Create Payment Process Profile to process invoices payments based on the selection criteria we have
selected.
Page | 40
Click on Payment Process Profiles – Go To Task button.
Page | 41
A new page will be opened like this. Enter the required details.
Enter Payment Process Profile Code, Name, Description, Payment Instruction Format and Processing
Type details.
These Payment Process Profile header details will be inserted into following table.
1) IBY_PAYMENT_PROFILES
Page | 42
Page | 43
Sql Query
select *
from IBY_PAYMENT_PROFILES
Page | 44
Payment Method Name has been added to the profile.
Page | 45
Select Bank Account Name from the list and click on Select button.
Page | 46
Now select Currency information to be used for this profile.
Page | 47
IBY_APPLICABLE_PMT_PROFS
Sql Query:
select *
from IBY_APPLICABLE_PMT_PROFS
Check First Party Organization, First Party Legal Entity, Payment Currency and Payment Function
buttons.
Page | 48
Then click on Save and Add Details button.
Click on Apply.
Page | 49
Payment Process Profile has been created.
After creating the Payment profiles, data will be inserted into following tables.
1) IBY_SYS_PMT_PROFILES_TL
2) IBY_SYS_PMT_PROFILES_B
Sql Query:
select *
from IBY_SYS_PMT_PROFILES_TL
where SYSTEM_PROFILE_NAME = 'Standard Check Format USD CITI'
and language = userenv('LANG');
select *
from IBY_SYS_PMT_PROFILES_B
where SYSTEM_PROFILE_CODE = 'XRX_IBY_CHK_USD_CITI';
Page | 50
Update Payment Format in this Payment Profile.
Select Payment Instruction Format tab and update Payment Instruction Format.
Page | 51
Update the Payment Instruction Format and click on Apply.
Page | 52
8. Create Supplier and Supplier Site
Page | 53
Click on Create Supplier button.
Page | 54
SQL Query:
select *
from ap_suppliers
Click on Address Book and click on Create button to create the new supplier site.
Page | 55
Select Site and click on Apply.
Page | 56
SQL Query:
select *
from ap_supplier_sites_all
from ap_suppliers
Page | 57
9. Update Payment Method in Supplier
Navigation:
Page | 58
A new page will be opened like this.
Page | 59
Click on Payment Details.
Page | 60
Update the Payment Method default value to PAYMENT CARD and click on Save.
Page | 61
SQL Query to find the Payment Method of a supplier:
SELECT ieppm.ext_party_pmt_mthd_id,
sup.vendor_name,
assa.vendor_site_code,
ieppm.payment_method_code,
assa.org_id,
sup.vendor_id,
assa.vendor_site_id
ap_suppliers sup,
iby_external_payees_all iepa,
iby_ext_party_pmt_mthds ieppm
Page | 62
10. Run PPR Process
Create an Invoice
Create an Invoice using Invoice Batches and try to pay the invoice using the PPR process we have
created.
Navigation:
Page | 63
Sql query to get the Batch Name information is:
select *x
from AP_BATCHES_ALL
Page | 64
A form will be opened like this. Enter the required details.
Page | 65
Page | 66
Enter Supplier Name (Trading Partner), Supplier Num, Supplier Site, Invoice Date, Invoice Num and
Invoice Currency, Invoice Amount, Terms Date and Terms and Save it.
As per Xerox Customizations, update Document Location Number in zoom form on header level.
Page | 67
SQL Query to get the Invoice Header details:
select *
from AP_INVOICES_ALL
Page | 68
Enter Amount and Default Distribution Account and click Save.
select *
from AP_INVOICE_LINES_ALL
Page | 69
where INVOICE_ID = 17386177;
select *
from AP_INVOICE_DISTRIBUTIONS_ALL;
Page | 70
Click on Actions and select Force Approval, then select OK.
Page | 71
Status has changed to Needs Revalidation. Remove the Hold for this invoice.
Page | 72
select *
from AP_HOLDS_ALL
Page | 73
A new page like this will get opened.
Page | 74
Enter required details in this page.
Enter Payment Process Request Name, Pay From Date and Payment Method.
Page | 75
Click On Payment Attributes tab.
Enter Disbursement Bank Account, Payment Document, Payment Process Profile, Payment Exchange
Rate Type.
Here Process will be stopped after reviewing the Scheduled Payment Selection and after creation of
Proposed Payments.
Page | 76
Change the Document value from LOV, based on the requirement.
After updating all these details in the PPR Process, click on Submit.
Page | 77
Verify the status of the PPR process.
SELECT *
FROM AP_INV_SELECTION_CRITERIA_ALL
Page | 78
where checkrun_name = 'USD10112017154900';
Verify whether correct invoices got selected or not. We can remove the invoices from the list.
Page | 79
Payment request submitted. Click on Refresh Status to verify the latest status.
Page | 80
select *
from IBY_PAY_SERVICE_REQUESTS
select * -- PAYMENT_ID
from IBY_DOCS_PAYABLE_ALL
select *
from IBY_PAYMENTS_ALL
Page | 81
Status has changed to Pending Proposed Payment Review. Click on Start Action.
Page | 82
Verify the Invoice details and click on Go.
Page | 83
SQL Query to get Payment Format Instruction details:
select *
from IBY_PAY_INSTRUCTIONS_ALL
The output of Program ‘Format Payment Instructions’ is the output of the Check.
Page | 84
This gets printed on the check.
Status has changed to Formatting. Reference details are updated and status is Ready for Printing.
Page | 85
Enter Printer details and click in Print.
Sql Query to get XML Documents associated with a particular transaction generated:
Page | 86
SELECT *
FROM IBY_TRXN_DOCUMENTS
Page | 87
Verify the Supplier details and click on Record Print Status.
Click on Continue.
Page | 88
Now we are updating the status as Printed. This process can’t be reversed.
Page | 89
Payment has been Confirmed and status is updated to Printed.
Page | 90
select * from AP_CHECKS_ALL
select *
from AP_INVOICE_PAYMENTS_ALL
from AP_CHECKS_ALL
select *
from AP_PAYMENT_SCHEDULES_ALL
from AP_INVOICE_PAYMENTS_ALL
from AP_CHECKS_ALL
Page | 91
Payment Dash board will update this PPR process in the Completed section.
Page | 92
Payment has been completed using PAYMENT CARD and the date.
Page | 93