Professional Documents
Culture Documents
Technical
Last revised: January 29, 2007
See Change Record
Form Name
Function Name
Embedded the Oracle Payments components in the Transactions form to select the Instrument Details and Payments attributes based on the
associated payment method. The fields, which in Release 11i, held the customer bank, branch, account number, and expiration date have
been removed; these details will be entered from the Payments component.
ARXRWMAI.fmb Receipt
Embedded the Oracle Payments components in the Receipts form to select the Instrument Details and Payments attributes based on the
receipt method. The fields, which in Release 11i, held the customer bank, branch, account number, and expiration date have been removed;
these details will be entered from the Payments component.
Embedded the Oracle Payments components in the Receipts form to select the Instrument Details and Payments attributes based on the
receipt method. The fields, which in Release 11i, held the customer bank, branch, account number, and expiration date have been removed;
these details will be entered from the Payments component.
ARXRWRCT.fmb
RAXSUCTT.fmb
Define Transaction
Types
The Magnetic Format Code field has been removed from the Bills Receivable tab as Payments will handle magnetic formats in R12.
ARBRCBAT.fmb
Bills Receivable
Transaction Batches
The Customer Bank Name field has been removed from the Selection Criteria form as it will not be available for Bills Receivables invoices
in Release 12. The Transaction Type field has been added to this form because it is operating unit-specific.
ARBRMAIN.fmb
Bills Receivable
Transactions
The Bank Account tab has been modified to retrieve the Drawee's Instrument Details from Oracle Payments by calling the Payments API.
ARBRREMI.fmb
Bills Receivable
Remittances
From the Selection Criteria tab of the BR Remittance form, the Transmission Program and Drawee City fields have been removed.
ARXRWBOE.fmb
The Payment Methods field label has been changed to Receipt Methods in the Selection Criteria section. The Customer Bank tab name has
been renamed to "Payment Details", per the new Payments data model for external bank accounts.
The Credit Card Errors form has been redesigned to reflect the new Payments architecture and also to include Bank Account
Transfer errors.
1. The page header has been changed to "Correct Funds Transfer Errors". In the advanced search, the Credit Card Number
field label was changed to Instrument Number because this form now addresses bank account transfer instruments in
addition to credit cards.
2. A new column "Corrective Action" has been added. The values for this column are: Retry, Change Instrument, Reverse
Receipt, Clear Payment Information. This column replaces the Retry, Reauthorize Receipts, Reverse Receipts, and Clear
Payment Information buttons in Release 11i.
A Submit button will be added to the Results table. The user can click the Submit button to commit actions selected for
particular values that have been entered in the Corrective Action column and when a row is selected.
Report Name
Function Name
Automatic Receipts
Automatic Remittance
Report Name
Function Name
ARBRFMTF.rdf
Made changes as per the new External Bank Account data model
ARBRFMTI.rdf
Made changes as per the new External Bank Account data model
ARBRFMTS.rdf
Made changes as per the new External Bank Account data model
ARXTDR.rdf
Made changes as per the new External Bank Account data model
ARXAPRRM.rdf
Made changes as per the new External Bank Account data model
RAXCUSLR.rdf
Made changes as per the new External Bank Account data model
3. Obsoleted Flexfields
6. Profile Options
1. New Profile Options
2. Changed Profile Options
3. Obsoleted Profile Options
1.3.1 Workflows
1.3.1.1 New Workflows
None
1.3.1.2 Changed Workflows
None
1.3.1.2 Obsoleted Workflows
None
ar_invoice_api_pub.create_invoice
Invoice API
The create_invoice API has been enhanced to accept the Payment Extension-Entity ID as an input. The Payment ExtensionEntity ID is not mandatory. However, if the Receipt Class associated with the Receipt Method that is passed on the
transaction has a Creation Method equal to Automatic or Bills Receivable, then the Payment Extension-Entity ID is
mandatory.
The create_single_invoice API has been enhanced to accept the Payment Extension-Entity ID as an input. The Payment
Extension-Entity ID is not mandatory. However, if the Receipt Class associated with the Receipt Method that is passed on
the transaction has a Creation Method equal to Automatic or Bills Receivable, then the Payment Extension-Entity ID is
mandatory.
ar_deposit_api_pub.create_deposit
Deposit API
The Deposit API has been enhanced to accept the Payment Extension-Entity ID as an input. The Payment Extension-Entity
ID is not mandatory. However, if the Receipt Class associated with the Receipt Method that is passed on the transaction
has a Creation Method equal to Automatic or Bills Receivable, then the Payment Extension-Entity ID is mandatory.
ar_receipt_api_pub.create_cash
Receipt API
The Create_cash Receipt API will be enhanced to accept and copy the transaction payment-extension record from the
source document and link the copy to the newly created receipt.
ar_receipt_api_pub.create_and_apply
Receipt API
The Create_and_apply Receipt API will be enhanced to accept and copy the transaction payment-extension record from the
source document and link the copy to the newly created receipt.
ar_receipt_api_pub.create_misc
Receipt API
The Create_misc Receipt API will be enhanced to accept and copy the transaction payment-extension record from the
source document and link the copy to the newly created receipt.
ar_receipt_api_pub.Create_Apply_On_Ac
Receipt API
c
ar_prepayment_pub.create_prepayment
Prepayments
API
1.3.3 Programs
1.3.3.1 New Programs
None
1.3.3.2 Changed Programs
The Create_Apply_On_Acc Receipt API will be enhanced to accept and copy the transaction payment-extension record
from the source document and link the copy to the newly created receipt.
The Prepayment API will be enhanced to accept and copy the transaction payment-extension record from the source
document and link the copy to the newly created receipt.
Program
Name
Feature Area
Auto Receipts
Creation of Automatic
Receipts
It was been rewritten in pl/sql along with the changes, per the new Payments data model for external bank accounts.
Auto
remittance
Automatic Remittance
It was been rewritten in pl/sql along with the changes, per the new Payments data model for external bank accounts.
Lockbox
LockBox
It has been modified, per the new Payments data model for external bank accounts.
AutoInvoice
It has been modified, per the new Payments data model for external bank accounts and creation of the Payment Transaction extension
details.
1.3.5 Flexfields
1.3.5.1 New Flexfields
None
1.3.5.2. Changed Flexfields
None
1.3.5.3 Obsoleted Flexfields
None
Table Name
Feature Area
AR_CASH_RECEIPTS_ALL
Receipt Header
AR_RECEIPT_METHODS
Receipt Method
Setup
RA_CUSTOMER_TRX_ALL
Auto Invoice
Added Payment extension identifier and Payment Attributes, and obsoleted payment_server_order_num, approval_code,
address_verification_code.
1.4.2 Views
1.4.2.1 New Views
View Name
Feature Area
AR_DOCS_RECEIVABLES_V
Payment Settlement
AR_FUNDS_CAPTURE_ORDERS_V
Payment Settlement
ARBR_DOCS_RECEIVABLES_V
Payment Settlement
ARBR_DOCUMENT_LINES_V
Payment Settlement
ARBR_FUNDS_CAPTURE_ORDERS_V
Payment Settlement
Added Payment extension identifier & payment channel code to view. Also modified the view to
accommodate the data model changes related to payment uptake project.
AR_BOE_AUTO_RECEIPTS_V
Automatic Receipts
AR_BOE_REMIT_RECEIPTS_CBUNR_V
Receipt Remittance
Added Payment extension identifier & payment channel code to view. Also modified the view to
accommodate the data model changes related to payment uptake project.
Added Payment extension identifier & payment channel code to view. Also modified the view to
accommodate the data model changes related to payment uptake project.
AR_BOE_REMIT_RECEIPTS_V
Receipt Remittance
Modified the view to accommodate the data model changes related to payment uptake project
AR_BR_ASSIGNMENTS_V
Modified the view to accommodate the data model changes related to payment uptake project
AR_BR_MAIN_REMIT_BATCH_V
Modified the view to accommodate the data model changes related to payment uptake project
AR_CASH_RECEIPTS_V
Receipt
AR_CUSTOMER_BILLS_TRX_V
Bills Receivable
AR_REMITTED_RECEIPTS_FORMAT_V
Added Payment extension identifier & payment channel code to view. Also modified the view to
accommodate the data model changes related to payment uptake project.
RA_CUSTOMER_TRX_CM_V
Modified the view to accommodate the data model changes related to payment uptake project
Added Payment extension identifier and the payment channel identifier to view
RA_CUSTOMER_TRX_PART_CB_V
Transactions
Modified the view to accommodate the data model changes related to payment uptake project
Added Payment extension identifier and the payment channel identifier to view
RA_CUSTOMER_TRX_PARTIAL_V
Transaction
Modified the view to accommodate the data model changes related to payment uptake project
Added Payment extension identifier and the payment channel identifier to view
None
1.4.3.3 Obsoleted Synonyms with Policies
None
2. Implementation Considerations
This section identifies the new/changed setup steps that were introduced in Release 12 for the Oracle Receivables Payments Uptake. For detailed step-by-step implementation instructions,
please refer to the Oracle Receivables Implementation Guide, Oracle Receivables User Guide and Oracle Applications Upgrade Guide: Release 11i to Release 12.
1. New Setup Steps
2. Changed Setup Steps
2.1 New Setup Steps
The Merchant Reference ID is not associated with the Receipt Method in R12. Oracle Payments will identify the Merchant Reference ID from the operating unit. Users complete the setup for
each operating unit in Oracle Payments. Please refer to the Oracle Payments Technical TOI for further information.
2.2 Changed Setup Steps
1. Creation of External Bank
2. Receipt Classes and Receipt Methods
2.2.1 Creation of External Bank
External banks now must be created in Oracle Payments using their OA Framework user interface. The user interface can be invoked from the Payment Component associated in the Payment
Details region of the Transactions or Receipts workbenches. External banks can be created and associated with the customer account or site from the Customers set of HTML pages.
2.2.2 Receipt Classes and Receipt Methods
In the Receipt Classes setup form, when the Creation Method is Automatic, then the Remittance Method of No Remittance is NOT allowed. For Automatic Receipts, select the Payment
Method in the Funds Transfer Processing region on the Automatic tab. This addresses the interaction between Receivables and Payments.
5. Diagnostics
None
7. Change Record
Date
Description of Change
Published document.