Sei sulla pagina 1di 15

Release 12 Receivables External Bank Account Uptake

Technical
Last revised: January 29, 2007
See Change Record

How to Use this Document


The Technical TOI communicates technical information about new or changed functionality introduced in the specified release of the Oracle E-Business Suite. It does not cover any changes
introduced in family packs, mini-packs or standalone patches released since 11.5.10. To find out about these changes, consult the appropriate About Documents listed below.
This Technical TOI document contains the following technical information about Oracle Receivables, External Bank Account Uptake, Release 12.
1. New and Changed Components
2. Implementation Considerations
3. Performance & Sizing: Considerations and Optimizations
4. Minimum Technical Requirements
5. Diagnostics
6. Technical Architecture Considerations
7. Change Record
About Document Links
See About Oracle Receivables in Financials Family Pack G, OracleMetaLink Note 290394.1.
Other Document Links
Oracle Receivables Implementation Guide
Oracle Receivables User Guide
Oracle Receivables Reference Guide
Note that the Oracle Applications Online Documentation CD is available on OracleMetaLink. It contains the most current Documentation Library.
Oracle Electronic Technical Reference Manual (eTRM) located on OracleMetaLink

Oracle Integration Repository located on OracleMetaLink

1. New and Changed Components


This section identifies some of the components that were introduced or changed for Oracle Receivables, External Bank Account Uptake in Release 12. The components detailed in this section
may have significant impact to existing customizations and/or extensions currently implemented on the system. Please carefully review and understand the implications of these changes in
these areas. For additional information refer to the Oracle Electronic Technical Reference Manuals ( eTRM) or the Oracle Integration Repositorylocated on OracleMetaLink. Please note that both
the eTRM and the Integration Repository represent cumulative, not delta, product information.
1.1 User Interfaces
1.2 Reports and XML Publisher
1.3 Interfaces and Configuration
1.4 Tables and Views

1.1 User Interfaces


1. New User Interfaces
1. New Forms
2. New HTML Pages
2. Changed User Interfaces
1. Changed Forms
2. Changed HTML Pages
3. Obsoleted User Interfaces
1. Obsoleted Forms
2. Obsoleted HTML Pages
1.1.1 New User Interfaces
1.1.1.1 New Forms
None
1.1.1.2 New HTML Pages
None

1.1.2 Changed User Interfaces


1.1.2.1 Changed Forms

Form Name

Function Name

Brief Description of Change

ARXSUDRC.fmb Receipt Classes


The Automatic tab in the Receipt Method has been delineated into two regions: 1) Receipts Processing and 2) Funds Transfer Processing.
The Receipts Processing region primarily addresses the grouping of invoices for Automatic Receipts processing. The Funds Transfer
Processing region addresses the interaction between Receivables and Payments.
Values in this region include Payment Method (the Payment Type field on the Automatic tab has been replaced by Payment Method) and
the Funds Transfer Error Handling button (the Credit Card Error Handling button and the form which it opens have been renamed to
"Funds Transfer Error Handling").
In the Bills Receivable tab, the display-only Payment Method field has been added and will have the value of "Bills Receivable".
In the Receipt Classes form -> Bank Accounts button -> Formats tab, the Remittance Transmission and Factoring Transmission fields have
been removed. The formatting files associated with these fields will handled by Payments in R12.
ARXTWMAI.fmb Transactions

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.

1.1.2.2 Changed HTML Pages

HTML Page Name

Function Name Brief Description of Change

ARCCERRORHANDLINGPG.xm Credit Card


l
Error Handling

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.

1.1.3 Obsoleted User Interfaces


1.1.3.1 Obsoleted Forms
None
1.1.3.2 Obsoleted HTML Pages
None

1.2 Reports and XML Publisher


1. Reports
1. New Reports
2. Changed Reports
3. Obsoleted Reports
2. XML Publisher
1. New XML Publisher Components

2. Changed XML Publisher Components


3. Obsoleted XML Publisher Components
1.2.1 Reports
1.2.1.1 New Reports

Report Name

Function Name

Automatic Receipts Creation Program (API)

Automatic Receipts

Automatic Remittances Creation Program (API)

Automatic Remittance

1.2.1.2 Changed Reports

Report Name

Function Name

Brief Description of Change

ARBRFMTF.rdf

French Bills Receivable Format

Made changes as per the new External Bank Account data model

ARBRFMTI.rdf

Italian Bills Receivable Format

Made changes as per the new External Bank Account data model

ARBRFMTS.rdf

Spanish Bills Receivable Format

Made changes as per the new External Bank Account data model

ARXTDR.rdf

Transaction Detail Report

Made changes as per the new External Bank Account data model

ARXAPRRM.rdf

Receipt Remittance Report

Made changes as per the new External Bank Account data model

RAXCUSLR.rdf

Customer Listing Detail Report

Made changes as per the new External Bank Account data model

1.2.1.3 Obsoleted Reports


None

1.2.2 XML Publisher


1.2.2.1.1 New XML Publisher Components
None
1.2.2.1.2 Changed XML Publisher Components
None

1.2.2.1.3 Obsoleted XML Publisher Components


None

1.3 Interfaces and Configuration


1. Workflows
1. New Workflows
2. Changed Workflows
3. Obsoleted Workflows
2. Public APIs
1. New Public APIs
2. Changed Public APIs
3. Obsoleted/Deprecated Public APIs
3. Programs
1. New Programs
2. Changed Programs
3. Obsoleted Programs
4. SQL Loader Files
1. New SQL Loader Files
2. Changed SQL Loader Files
3. Obsoleted SQL Loader Files
5. Flexfields
1. New Flexfields
2. Changed Flexfields

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

1.3.2 Public APIs


For additional information, refer to the Oracle Integration Repository located on OracleMetaLink. Please note that the Integration Repository represents cumulative, not delta, product
information.
1.3.2.1 New Public APIs
None
1.3.2.2 Changed Public APIs

Public API Name

Feature Area Brief Description of Change

ar_invoice_api_pub.create_invoice

Invoice API

ar_invoice_api_pub.create_single_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.2.3 Obsoleted/Deprecated Public APIs


None

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

Brief Description of Change

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

Automatic Invoice creation

It has been modified, per the new Payments data model for external bank accounts and creation of the Payment Transaction extension
details.

1.3.3.3 Obsoleted Programs


None

1.3.4 SQL Loader Files


1.3.4.1 New SQL Loader Files
None
1.3.4.2 Changed SQL Loader Files
None
1.3.4.3 Obsoleted SQL Loader Files
None

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

1.3.6 Profile Options


1.3.6.1 New Profile Options
None
1.3.6.2 Changed Profile Options
None
1.3.6.3 Obsoleted Profile Options
None

1.4 Tables and Views


For additional table and view information, refer to the Oracle Electronic Technical Reference Manuals ( eTRM) located on OracleMetaLink. Please note that the eTRM contains cumulative, not
delta, product information.
1. Tables
1. New Tables
2. Changed Tables
3. Obsoleted Tables
2. Views
1. New Views
2. Changed Views
3. Obsoleted Views
3. Synonyms with Policies
1. New Synonyms with Policies
2. Changed Synonyms with Policies

3. Obsoleted Synonyms with Policies


1.4.1 Tables
1.4.1.1 New Tables
None
1.4.1.2 Changed Tables

Table Name

Feature Area

Brief Description of Change

AR_CASH_RECEIPTS_ALL

Receipt Header

Added Payment extension identifier and obsoleted payment_server_order_num, approval_code,


address_verification_code.

AR_RECEIPT_METHODS

Receipt Method
Setup

Added Payment Channel Code and obsoleted


payment_type_code, merchant_ref, merchant_id, auto_print_program_id, auto_trans_program_id.

RA_CUSTOMER_TRX_ALL

Transaction Header Added Payment extension identifier and Payment Attributes,


and obsoleted payment_server_order_num, approval_code, address_verification_code.

RA_CUSTOMER_TRX_LINES_ALL Transactions Lines Added Payment extension identifier.


RA_INTERFACE_LINES_ALL

Auto Invoice

Added Payment extension identifier and Payment Attributes, and obsoleted payment_server_order_num, approval_code,
address_verification_code.

1.4.1.3 Obsoleted Tables


None

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

1.4.2.2 Changed Views


Feature Area
View Name

Brief Description of Change

AR_AUTOMATIC_RECEIPTS_FORMAT_V Automatic Receipts

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

Added Payment extension identifier to view

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.

AR_BOE_REMIT_RECEIPTS_NONCBR_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.

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

Bills Receivable Assignments

Modified the view to accommodate the data model changes related to payment uptake project

AR_BR_MAIN_REMIT_BATCH_V

Bills Receivable Remittance

Modified the view to accommodate the data model changes related to payment uptake project

AR_CASH_RECEIPTS_V

Receipt

Added Payment extension identifier and payment channel identifier to view

AR_CUSTOMER_BILLS_TRX_V

Bills Receivable

Added Payment extension identifier and payment channel identifier to view

AR_REMITTED_RECEIPTS_FORMAT_V

Receipt Remittance Formatting

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

Transactions Credit Memo

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

1.4.2.3 Obsoleted Views


None

1.4.3 Synonyms with Policies


1.4.3.1 New Synonyms with Policies
None
1.4.3.2 Changed Synonyms with Policies

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.

3. Performance & Sizing: Considerations and Optimizations


None

4. Minimum Technical Requirements


The minimum technical requirements for Oracle Receivables are included in the Release 12 Rapid Install.

5. Diagnostics
None

6. Technical Architecture Considerations


In Release 11i, external (i.e., customer) banks were created on the Banks form (Setup > Receipts > Banks), which was owned by Oracle Payables. In Release 12, Oracle Payments stores external
banks.
Therefore, all customer bank details in Receivables, such as the bank information in the Customer set of HTML pages, now point to the bank tables located in Payments.
Oracle Receivables users create external banks using the form that has been designed by Payments. This new user interface in Payments is based on UI page components that are in OA
Framework.
All manual transactions created in Receivables will get written into the new transaction payment extension table in Payments. A record within the transaction payment extension table is
composed of payment method, payment instrument, and payment attributes.
Oracle Payments will be the new centralized payment processing solution for credit cards. Consolidating the data model will ease the introduction of new credit card features, such as data
encryption and supporting new attributes, as well as the creation of credit card transactions and receipts. In prior releases, credit card functionality was available in Receivables, and key credit
card information was passed from iPayment to Receivables, such as Payment Server ID and Approval Code. The new model requires calling products to store an ID, which is a unique internal
credit card identifier, to retrieve credit card information rather than having to store all the credit card data, such as Payment Server ID and Approval Code, in Receivables tables.
As part of the new credit card process, Oracle Payments requires that all transactions that will result in an electronic capture of funds undergo an authorization step before they can be settled.
The content of the authorization process varies based on the instrument type. For credit card payments, real-time communication is invoked with third party payment networks to authorize and
reserve funds. For bank account transfers, bank account validation takes place.
Oracle Payments will also be the centralized solution for authorization. Therefore, the transaction authorization information is stored in Payments, and Receivables should not store transaction
authorization in its tables. Receivables will be responsible for accepting valid authorizations from upstream products, and Receivables will not perform duplicate authorization on upstream
products.
To process manual receipts, the Remittances form will work the same way it did in Release 11i; Receivables will not contact Payments. Therefore, Receivables will continue storing remittance
receipt formats. However, for processing automatic receipts, there will be a new system process. After submitting a batch from either the Create Remittance Batch or Maintain Remittance Batch
form, Payments will handle the processing.

7. Change Record

Date

Description of Change

January 24, 2007

Published document.