122 Ireceivables Implementation Guide
122 Ireceivables Implementation Guide
Implementation Guide
Release 12.2
Part No. E48858-13
November 2021
Oracle iReceivables Implementation Guide, Release 12.2
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No
other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.
com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Preface
iii
History Details......................................................................................................................... 1-38
Set Up for Anonymous User Login......................................................................................... 1-40
Review and Update Receivables Lookups..............................................................................1-43
Set the Aging Information...................................................................................................... 1-45
Set Up for Bill Presentment Architecture............................................................................... 1-46
Print Invoices Using AR Print Program............................................................................. 1-47
Modify the Display of Account Information..........................................................................1-47
Custom Hooks for Payment, Dispute, and Print.................................................................... 1-49
Integrate iReceivables into Your Business Processes............................................................. 1-51
iv
A Features of Oracle iReceivables
Overview of Oracle iReceivables............................................................................................. A-1
Major Features........................................................................................................................... A-1
B Profile Options
Profile Options for Oracle iReceivables................................................................................... B-1
v
Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: [email protected]
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle iReceivables Implementation Guide.
This guide assumes you have a working knowledge of the following:
• The principles and customary practices of your business area.
If you have never used Oracle E-Business Suite, we suggest you attend one or more of
the Oracle E-Business Suite training classes available through Oracle University.
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Structure
1 Setting Up Oracle iReceivables
2 Oracle iReceivables Command Center Setup
ix
3 Setting Up for Credit Memo Request Workflow
4 Configuring Oracle iReceivables
A Features of Oracle iReceivables
B Profile Options
• PDF Documentation - See the Oracle E-Business Suite Documentation Library for
current PDF documentation for your product with each release.
• Release Notes - For information about changes in this release, including new
features, known issues, and other details, see the release notes for the relevant
product, available on My Oracle Support.
Related Guides
You should have the following related books on hand. Depending on the requirements
of your particular installation, you may also need additional manuals or guides.
Oracle E-Business Suite User's Guide:
This guide explains how to navigate, enter and query data, and run concurrent requests
using the user interface (UI) of Oracle E-Business Suite. It includes information on
setting preferences and customizing the UI. In addition, this guide describes
accessibility features and keyboard shortcuts for Oracle E-Business Suite.
Oracle Alert User's Guide:
This guide explains how to define periodic and event alerts to monitor the status of
your Oracle E-Business Suite data.
Oracle Application Framework Developer's Guide:
This guide contains the coding standards followed by the Oracle E-Business Suite
x
development staff to produce applications built with Oracle Application Framework.
This guide is available in PDF format on My Oracle Support and as online
documentation in JDeveloper 10g with Oracle Application Extension.
Oracle Application Framework Personalization Guide:
This guide covers the design-time and run-time aspects of personalizing applications
built with Oracle Application Framework.
Oracle Fusion Middleware Adapter for Oracle Applications User's Guide (Oracle
Application Server Adapter for Oracle Applications User's Guide):
This guide covers the use of Adapter for Oracle Applications in developing integrations
between Oracle E-Business Suite and trading partners.
Please note that the user's guide can be found in the following documentation libraries:
• As part of the Oracle Fusion Middleware and SOA Suite in 11g, Oracle Fusion
Middleware Adapter for Oracle Applications User's Guide is available in the Oracle
Fusion Middleware 11g Documentation Library.
• As part of the Oracle Application Server in 10g, Oracle Application Server Adapter for
Oracle Applications User's Guide is available in the Oracle Application Server 10g
Documentation Library.
xi
needed to implement the Oracle E-Business Suite user interface described in the Oracle
E-Business Suite User Interface Standards for Forms-Based Products. It provides information
to help you build your custom Oracle Forms Developer forms so that they integrate
with Oracle E-Business Suite. In addition, this guide has information for customizations
in features such as concurrent programs, flexfields, messages, and logging.
Oracle E-Business Suite Flexfields Guide:
This guide provides flexfields planning, setup, and reference information for the Oracle
E-Business Suite implementation team, as well as for users responsible for the ongoing
maintenance of Oracle E-Business Suite product data. This guide also provides
information on creating custom reports on flexfields data.
Oracle E-Business Suite Installation Guide: Using Rapid Install:
This book is intended for use by anyone who is responsible for installing or upgrading
Oracle E-Business Suite. It provides instructions for running Rapid Install either to carry
out a fresh installation of Oracle E-Business Suite Release 12.2, or as part of an upgrade
to Release 12.2.
Oracle E-Business Suite Maintenance Guide:
This guide contains information about the strategies, tasks, and troubleshooting
activities that can be used to help ensure an Oracle E-Business Suite system keeps
running smoothly, together with a comprehensive description of the relevant tools and
utilities. It also describes how to patch a system, with recommendations for optimizing
typical patching operations and reducing downtime.
Oracle E-Business Suite Security Guide:
This guide contains information on a comprehensive range of security-related topics,
including access control, user management, function security, data security, and
auditing. It also describes how Oracle E-Business Suite can be integrated into a single
sign-on environment
Oracle E-Business Suite Setup Guide:
This guide contains information on system configuration tasks that are carried out
either after installation or whenever there is a significant change to the system. The
activities described include defining concurrent programs and managers, enabling
Oracle Applications Manager features, and setting up printers and online help.
Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to 12.2:
This guide provides information for DBAs and Applications Specialists who are
responsible for upgrading Release 12.0 and 12.1 Oracle E-Business Suite system
(techstack and products) to Release 12.2 In addition to information about applying the
upgrade driver, it outlines pre-upgrade steps and post-upgrade steps, and provides
descriptions of product-specific functional changes and suggestions for verifying the
upgrade and reducing downtime.
Oracle E-Business Suite Supportability Guide:
This manual contains information on Oracle Diagnostics and the Logging Framework
xii
for system administrators and custom developers.
Oracle E-Business Suite User Interface Standards for Forms-Based Products:
This guide contains the user interface (UI) standards followed by the Oracle E-Business
Suite development staff. It describes the UI for the Oracle E-Business Suite products and
how to apply this UI to the design of an application built by using Oracle Forms.
Oracle E-Business Suite Integrated SOA Gateway User's Guide:
This guide describes the high level service enablement process, explaining how users
can browse and view the integration interface definitions and services residing in
Oracle Integration Repository.
Oracle E-Business Suite Integrated SOA Gateway Developer's Guide:
This guide describes how system integration developers can perform end-to-end service
integration activities. These include orchestrating discrete Web services into meaningful
end-to-end business processes using business process execution language (BPEL), and
deploying BPEL processes at run time.
This guide also explains how to invoke Web services using the Service Invocation
Framework. This includes defining Web service invocation metadata, invoking Web
services, and testing the Web service invocation.
Oracle E-Business Suite Integrated SOA Gateway Implementation Guide:
This guide explains how integration repository administrators can manage and
administer the Web service activities for integration interfaces including native
packaged integration interfaces, composite services (BPEL type), and custom
integration interfaces. It also describes how to invoke Web services from Oracle E-
Business Suite by employing the Oracle Workflow Business Event System, and how to
manage Web service security, configure logs, and monitor SOAP messages.
Oracle e-Commerce Gateway User's Guide:
This guide describes the functionality of Oracle e-Commerce Gateway and the
necessary setup steps in order for Oracle E-Business Suite to conduct business with
trading partners through Electronic Data Interchange (EDI). It also describes how to run
extract programs for outbound transactions, import programs for inbound transactions,
and the relevant reports.
Oracle e-Commerce Gateway Implementation Guide:
This guide describes implementation details, highlighting additional setup steps needed
for trading partners, code conversion, and Oracle E-Business Suite. It also provides
architecture guidelines for transaction interface files, troubleshooting information, and a
description of how to customize EDI transactions.
Oracle iSetup Developer's Guide:
This manual describes how to build, test, and deploy Oracle iSetup Framework
interfaces.
Oracle iSetup User's Guide:
xiii
This guide describes how to use Oracle iSetup to migrate data between different
instances of the Oracle E-Business Suite and generate reports. It also includes
configuration information, instance mapping, and seeded templates used for data
migration.
Oracle Report Manager User's Guide:
Oracle Report Manager is an online report distribution system that provides a secure
and centralized location to produce and manage point-in-time reports. Oracle Report
Manager users can be either report producers or report consumers. Use this guide for
information on setting up and using Oracle Report Manager.
Oracle Web Applications Desktop Integrator Implementation and Administration
Guide:
Oracle Web Applications Desktop Integrator brings Oracle E-Business Suite
functionality to a spreadsheet, where familiar data entry and modeling techniques can
be used to complete Oracle E-Business Suite tasks. You can create formatted
spreadsheets on your desktop that allow you to download, view, edit, and create Oracle
E-Business Suite data, which you can then upload. This guide describes how to
implement Oracle Web Applications Desktop Integrator and how to define mappings,
layouts, style sheets, and other setup options.
Oracle Workflow Client Installation Guide:
This guide describes how to install the Oracle Workflow Builder and Oracle XML
Gateway Message Designer client components for Oracle E-Business Suite.
Oracle Workflow Administrator's Guide:
This guide explains how to complete the setup steps necessary for any product that
includes workflow-enabled processes. It also describes how to manage workflow
processes and business events using Oracle Applications Manager, how to monitor the
progress of runtime workflow processes, and how to administer notifications sent to
workflow users.
Oracle Workflow API Reference:
This guide describes the APIs provided for developers and administrators to access
Oracle Workflow.
Oracle Workflow Developer's Guide:
This guide explains how to define new workflow business processes and customize
existing Oracle E-Business Suite-embedded workflow processes. It also describes how
to define and customize business events and event subscriptions.
Oracle Workflow User's Guide:
This guide describes how users can view and respond to workflow notifications and
monitor the progress of their workflow processes.
Oracle XML Gateway User's Guide:
This guide describes Oracle XML Gateway functionality and each component of the
xiv
Oracle XML Gateway architecture, including Message Designer, Oracle XML Gateway
Setup, Execution Engine, Message Queues, and Oracle Transport Agent. It also explains
how to use Collaboration History that records all business transactions and messages
exchanged with trading partners.
The integrations with Oracle Workflow Business Event System, and the Business-to-
Business transactions are also addressed in this guide.
Oracle XML Publisher Report Designer's Guide:
Oracle XML Publisher is a template-based reporting solution that merges XML data
with templates in RTF or PDF format to produce a variety of outputs to meet a variety
of business needs. Using Microsoft Word or Adobe Acrobat as the design tool, you can
create pixel-perfect reports from the Oracle E-Business Suite. Use this guide to design
your report layouts.
This guide is available through the Oracle E-Business Suite online help.
Oracle XML Publisher Administration and Developer's Guide:
Oracle XML Publisher is a template-based reporting solution that merges XML data
with templates in RTF or PDF format to produce a variety of outputs to meet a variety
of business needs. Outputs include: PDF, HTML, Excel, RTF, and eText (for EDI and
EFT transactions). Oracle XML Publisher can be used to generate reports based on
existing Oracle E-Business Suite report data, or you can use Oracle XML Publisher's
data extraction engine to build your own queries. Oracle XML Publisher also provides a
robust set of APIs to manage delivery of your reports via e-mail, fax, secure FTP,
printer, WebDav, and more. This guide describes how to set up and administer Oracle
XML Publisher as well as how to use the Application Programming Interface to build
custom solutions.
This guide is available through the Oracle E-Business Suite online help.
Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to
Release 12:
This guides provides detailed information about the functional impacts of upgrading
Oracle Financials and Oracle Procurement products from Release 11i to Release 12. This
guide supplements the Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to 12.2
.
Oracle Financials Concepts Guide:
This guide describes the fundamental concepts of Oracle Financials. The guide is
intended to introduce readers to the concepts used in the applications, and help them
compare their real world business, organization, and processes to those used in the
applications.
Oracle Financials Glossary:
The glossary includes definitions of common terms that are shared by all Oracle
Financials products. In some cases, there may be different definitions of the same term
for different Financials products. If you are unsure of the meaning of a term you see in
xv
an Oracle Financials guide, please refer to the glossary for clarification. You can find the
glossary in the online help or in the Oracle Financials Implementation Guide.
Oracle Financials Implementation Guide:
This guide provides information on how to implement the Oracle Financials E-Business
Suite. It guides you through setting up your organizations, including legal entities, and
their accounting, using the Accounting Setup Manager. It covers intercompany
accounting and sequencing of accounting entries, and it provides examples.
Oracle Payments Implementation Guide:
This guide describes how Oracle Payments, as the central payment engine for the
Oracle E-Business Suite, processes transactions, such as invoice payments from Oracle
Payables, bank account transfers from Oracle Cash Management, and settlements
against credit cards and bank accounts from Oracle Receivables. This guide also
describes how Oracle Payments is integrated with financial institutions and payment
systems for receipt and payment processing, known as funds capture and funds
disbursement, respectively. Additionally, the guide explains to the implementer how to
plan the implementation of Oracle Payments, how to configure it, set it up, test
transactions, and how use it with external payment systems.
Oracle Payments User's Guide:
This guide describes how Oracle Payments, as the central payment engine for the
Oracle E-Business Suite, processes transactions, such as invoice payments from Oracle
Payables, bank account transfers from Oracle Cash Management, and settlements
against credit cards and bank accounts from Oracle Receivables. This guide also
describes to the Payment Administrator how to monitor the funds capture and funds
disbursement processes, as well as how to remedy any errors that may arise.
Oracle Receivables Implementation Guide:
This guide provides you with information on how to implement Oracle Receivables.
Use this guide to understand the implementation steps required for application use,
including how to set up customers, transactions, receipts, accounting, tax, and
collections. This guide also includes a comprehensive list of profile options that you can
set to customize application behavior.
Oracle Receivables Reference Guide:
This guide provides you with detailed information about all public application
programming interfaces (APIs) that you can use to extend Oracle Receivables
functionality. This guide also describes the Oracle Receivables open interfaces, such as
AutoLockbox which lets you create and apply receipts and AutoInvoice which you can
use to import and validate transactions from other systems. Archiving and purging
Receivables data is also discussed in this guide.
Oracle Receivables User Guide:
This guide provides you with information on how to use Oracle Receivables. Use this
guide to learn how to create and maintain transactions and bills receivable, enter and
apply receipts, enter customer information, and manage revenue. This guide also
xvi
includes information about accounting in Receivables. Use the Standard Navigation
Paths appendix to find out how to access each Receivables window.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As
your instance is patched, the repository is automatically updated with content
appropriate for the precise revisions of interfaces in your environment.
xvii
1
Setting Up Oracle iReceivables
Note: You must have the URL for the Oracle E-Business Suite login.
Prerequisites:
Before setting up Oracle iReceivables, complete the following tasks:
• Set the MO: Default Operating Unit profile option to the default operating unit for
users with multiple units.
• Set the MO: Operating Unit profile option at the desired level (user, responsibility,
application, or site).
• Set the MO: Security profile option at the site level for all iReceivables
responsibilities.
• Set up Oracle Workflow Release 12, to use the Dispute Invoice function, or Self
Registration, or both.
• Set up Oracle Payments, to use the Pay Invoice function for credit cards or for bank
account transfers using the ACH network.
The following table lists the required setup steps for Oracle iReceivables:
3 Define Receipt Class and Receipt Method. See: Set Up Receipt Class and
Receipt Method, page 1-20.
Use the Users window to assign the responsibility iReceivables 2.0 Internal to each user
in your company that you want to have access to iReceivables. If you are using the
Multi Print feature, you must also enter the user's e-mail address.
To define iReceivables internal users:
1. Select the System Administrator responsibility.
3. Query or enter the users in your company that you want to have access to
iReceivables.
4. If you are using the Multi Print feature, enter the e-mail address of the first user in
the E-Mail field. The Multi Print feature sends an e-mail notification to this address
after the Receivables Invoice Print concurrent program finishes.
Related Topics
Printing Transactions, Oracle Receivables User Guide
Entering and Updating Customer Information, Oracle Receivables User Guide
ORACLE Users Window, Oracle E-Business Suite Maintenance Guide
The Customer text data creation and indexing concurrent program includes the parameter
'Build Compact Index?' to control the level of indexing when you first build your
customer index. Enter No to build the index with customer, customer site, customer
contact, and customer site contact information. Enter Yes to build the index with
customer and customer site information only, without contact information. The default
value is Yes. If you run the concurrent program without any parameter, the system will
default it to Yes and build the index without contact information.
Note: The index only includes customer contacts and customer site
contacts that have roles assigned to them, with one role marked as
primary.
Note: If you plan to assign external users the contact role Self Service
User for customers and customer sites, you must build your index with
the Build Compact Index? parameter set to No.
After you build customer indexes, schedule a regular run of the Customer text data
creation and indexing concurrent program, in accordance with your business practices, to
update the index with the changes to your customer data. A regular run of this program
ensures that all updates to your customer data are available to the iReceivables
customer search engine. Subsequent runs of the Customer text data creation and indexing
Note: Whenever you make changes to customer data, these changes are
not available to the iReceivables customer search engine until the next
time that the concurrent program runs and recreates the interMedia
index.
3. In the Name field, choose Customer text data creation and indexing from the list of
values.
3. In the Name field, choose Customer text data creation and indexing from the list of
values.
6. In the Start At and End At fields, set the date and time for this program run.
Related Topics
Request Submission, Oracle E-Business Suite User's Guide
For both types of external user, use the Users window to assign the iReceivables
Account Management responsibility and the corresponding customer contact or person.
If you are using the Multi Print feature, you must also enter the user's e-mail address.
External users can register themselves by logging through Register Here link or OIR
Self Service portal page using the Self Registration feature. See: Set Up for Self
Registration, page 1-10.
5. Navigate to the Addresses tabbed region and choose the customer address.
7. Enter the name of the external user and the user's contact information.
10. To assign this user to a second site of the same customer, repeat steps 5 and 6.
11. From the Customer Standard form, query a customer, open the Account, open one
of the Sites. Add a Contact by using the Communications tab.
14. To assign this user to additional sites of the same customer, repeat steps 10 to 13.
17. Enter the User Name and Password of the external user.
18. In the Customer Name field, choose any version of the external user's name defined
in step 7 from the list of values.
19. If using the Multi Print feature, enter the user's e-mail address in the E-Mail field.
The Multi Print feature sends an e-mail notification to this address after completion
of the Receivables Invoice Print concurrent program.
22. In the From and To fields, enter the effective dates for this user.
Do not create a new contact with the same name for each site. If the contact name or
address is a duplicate value, the application gives the option to select the contact from a
list. If this does not happen, check the following profile option settings:
6. Enter the name of the external user and the user's contact information.
11. In the Last field, choose the external user name entered in step 6 from the list of
values.
12. In the Description field, enter the role Self Service User.
13. Repeat steps 9 to 12 for all customers to be assigned to this external user.
17. Enter the User Name and Password of the external user.
18. In the Customer Name field, choose any version of the external user's name defined
in step 6 from the list of values.
22. In the From and To fields, enter the effective dates for this user.
4. Assign the user the Customer Type Person and enter the necessary Person party
details.
9. In the Customer Name field, choose any version of the external user's name defined
in step 4 from the list of values.
10. If using the Multi Print feature, enter the user's e-mail address in the E-Mail field.
The Multi Print feature sends an e-mail notification to this address after completion
of the Receivables Invoice Print concurrent program.
13. In the From and To fields, enter the effective dates for this user.
Related Topics
Printing Transactions, Oracle Receivables User Guide
Entering and Updating Customer Information, Oracle Receivables User Guide
Oracle Users Window, Oracle E-Business Suite Maintenance Guide
• Accessing SelfRegistration.jsp page. See Bookmark the Self Registration Page, page 1-
13
For additional access, select the Manage Customer Account Access link, when the user
logs in to the iReceivables Account Management responsibility.
Prerequisites
Before completing set up of iReceivables for Self Registration, perform the following
steps:
• Associate the MO: Security profile option that has been already created to the Guest
User.
In the Security profile option, enter all the organizations that contain customer
account data for which the external users should have access to.
• Set the ICX: Session Timeout profile option at a reasonable value to avoid session
timeout while a user completes the self-registration process.
Setup Tasks
To set up iReceivables Self Registration:
1. Set up Register Here link.
• Set the Local Login Mask Site Level to 48 at site level in the System Profiles
Values window.
• Set the UMX: Register Here Link - Default Registration Process value to
iReceivables Self Registration at server level in the System Profile Values window.
2. In the Profile field, enter the user account and make note of the value (value
format: user/password).
4. In the User Name field, query the value of the same user account.
Note: User may need to restart the web server for the update to
take effect.
6. Use the Message Dictionary to configure the FND confirmation messages that are
sent to users after successful registration.
The messages that should be configured contain this information:
• ARI_REG_APP_NAME - Enter the name of the iReceivables application that the
user has access to.
Note: If user is bookmarking the URL for Self Registration, then there is
no need to set the profiles Local Login Mask to 48 and UMX%Process to
iReceivables Self Registration.
Related Topics
User Profiles and Profile Options in Oracle Application Object Library, Oracle E-Business
Suite Setup Guide
• Answer Table: The list of table values, which has default tables as HZ_PARTIES,
HZ_CUST_ACCOUNTS. where the answer exists. Custom tables can also be added.
• Answer Column: If a value has been set in the Answer Table above, then the
columns in that table is populated in this drop down. The value in this column has
the answer which should be given by the user during Self Registration.
• Answer Table Join Column: The column from Answer Table to be joined with
HZ_CUST_ACCOUNTS table for getting a unique record.
Answer Table
Tables can be added to or deleted from the Answer Table.
1. Navigate to Application Developer Responsibility, then to Flexfield, Descriptive,
then Values. Enter Application as Receivables.
3. Enter the table name in the Value field. Enter the table description. Select Enabled.
To remove a table, deselect the Enabled check box and set To Date prior to current date.
• Answer Table: The list of table values, which has default tables as HZ_PARTIES,
HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, and
HZ_PARTY_SITES where the answer exists. Custom tables can also be added.
• Answer Column: If a value has been set in the Answer Table above, then the
columns in that table is populated in this drop down. The value in this column has
the answer which should be given by the user during Self Registration.
• Answer Table Join Column: The column from Answer Table to be joined with
HZ_PARTY_SITES table for getting a unique record.
Answer Table
Tables can be added to or deleted from the Answer Table.
1. Navigate to Application Developer Responsibility, then to Flexfield, Descriptive,
then Values. Enter Application as Receivables.
3. Enter the table name in the Value field. Enter the table description. Select Enabled.
To remove a table, deselect the Enabled check box and set To Date prior to current date.
Prerequisites
1. Assign iReceivables Self Service and iReceivables Account Management
responsibility to the guest user.
3. This step is required if the portal page has to be accessed outside the DMZ
environment. Modify the file $FND_TOP/admin/template/url_fw_conf_1013.tmp to
include the entry IrecVisitor.jsp under the line #Include URLs for product OIR
(iReceivables) like this: RewriteRule ^/OA_HTML/IrecVisitor\.jsp$ - [L].
Note: If the above entry is already included, then ignore this step.
4. For external user responsibility to work under a firewall, set the security-based
profile option Responsibility Trust level to External (3) for the responsibility
iReceivables Account Management.
• User has iReceivables External User responsibility, but does not have access to
any customer account:
The user is redirected to the registration process on logging in, where the user can
request access to the customer account.
• User has iReceivables External User responsibility and also access to customer
account:
The user is redirected to the iReceivables Customer Search screen on logging in.
• User has access to more than one iReceivables External User responsibility:
The user is redirected to the Responsibility navigator window. Select the required
responsibility and proceed further.
• Group Sites: Only grouping of sites for the customer account is enabled. On the
Customer Search page, My Locations link is available, which shows the transactions
and account summary for the sites the user has access to.
• Group Accounts and Sites: Grouping of customer accounts and grouping of sites
are enabled. On the Customer Search page, All My Accounts and Group My
Accounts buttons are available. On clicking All My Accounts button, the user is
navigated to the Account Summary page with a combined summarized view of all
the accounts and account sites the user has access to. There is an option to change
the account context to any customer account or back to all accounts.
• Always Group Accounts and Sites: Always groups customer accounts and sites.
On logging in the user is taken directly to the Account Summary page, with all
accounts selected, by-passing the Customer Search page.
Note: This feature is available only for External Users. Its not applicable
for Internal Users as they already have access to all the customer
accounts within the security profile or operating unit.
6. To assign a profile class to a customer site, open the Addresses tabbed region, select
the address, then choose Open. Repeat steps 4 and 5.
8. In the Curr column, set the currency or currencies that this customer uses.
Related Topics
Defining Customer Profile Classes, Oracle Receivables Implementation Guide
Assigning Profile Classes to Customers, Accounts, or Addresses, Oracle Receivables
Implementation Guide
Bank account transfer payments can be processed globally. If receipt methods are used
via Payments, then payment processing is restricted according to the Payments servlets.
A user can pay all open invoices in one payment transaction. The user can also make a
partial payment on the entire open invoice balance. If the user is paying multiple
invoices across multiple bill-to sites, Receivables creates the receipt using the primary
receipt method specified at the customer level. For payments of multiple invoices across
multiple bill-to sites, provide specific settings to use the receipt methods that are
assigned to customers and customer sites. See: Assign iReceivables Payment Methods,
page 1-25 for more information.
For bank account transfers and credit card payments, run the Receivables remittance
Important: The fields displayed using this profile option are mandatory
for successful payment using credit card.
• Credit Card Security Code only: The card Security Code field is displayed in the
iReceivables PaymentUI.
• Both: The card Security Code and Billing Address are displayed in the iReceivables
• None: The card Security Code and Billing Address fields are not displayed in the
iReceivables Payment UI.
Note: iReceivables uses the card security code for verification purposes
only and does not save the information but it saves the cardholder
billing address.
Note: Please consult Oracle Payment Implementation Guide for the current
list of Payments servlets and the currencies they support.
For credit card processing, users can use the Payments integration with Verisign, which
supports transactions in US dollars (USD) and Canadian dollars (CAD) only. They can
also use the Payments integration with Paymentech, which supports transactions in any
currencies supported by Visa and Master Card. For ACH bank account transfers, users
can use the Payments integration with Chase Merchant Services, which supports
transactions in US dollars (USD) only.
If their company uses the Verisign payment system, users cannot set up multiple bank
accounts with multiple currencies for one payment method. Set up a single payment
method for either USD or CAD, and assign a merchant ID and remittance bank that
supports the corresponding currency. If the company uses a payment system other than
Verisign, users can set up a single payment method for multiple bank accounts with
multiple currencies, if the payment system supports it.
4. Leave the Notes Receivable and Require Confirmation check boxes deselected.
8. Enter a Receipt Method name. For example, enter a name that identifies the type of
payment, such as iReceivables direct debit, iReceivables credit card, or iReceivables bank
transfer.
9. Enter a name in the Printed Name field. For example, iReceivables Credit Card.
10. Leave the Debit Memos Inherit Receipt Numbers check box deselected.
11. Leave the Receipts Inherit Transaction Numbers check box deselected.
12. Enter the number of receipts rule according to the business practices. This field is
not used by iReceivables.
13. Enter receipt maturity date rule according to the business practices. This field is not
used by iReceivables.
14. Enter the automatic print program according to the business practices.
17. Enter the range of Effective Dates for this payment method.
18. Choose the Bank Accounts button to assign a remittance bank to this payment
20. Assign the iReceivables receipt methods defined to the Receivables System Options
window, Customers - Standard window, and Customer Addresses window
according to you business practices. See: Assign iReceivables Payment Methods,
page 1-25 for more information.
Set the OIR: Maximum Future Payment Days Allowed profile option to the
maximum number of days that users can enter future-dated payments according to
business practices. Setting a maximum future payment date, for example, prevents
users from entering exaggerated future payment dates.
3. Click the Subscription link to check the subscriptions for the event
Related Topics
Understanding Oracle Payments, Oracle Payments User's Guide
About Remittances, Oracle Receivables User Guide
• Bill-to sites
• Account level
Important: For external users, you must set the system options to the
Pay button.
Mark one receipt method of each type as Primary at the customer and customer site
level. If at the customer site level there are two or more receipt methods of the same
type, the one marked as primary is taken as the receipt method for transactions billed to
this site. If no receipt method of the same type is marked as primary, then the payment
method at the customer level is taken as the payment method for transactions billed to
this site.
For credit card payments of multiple invoices across multiple bill-to sites, Receivables
only uses the primary receipt methods defined at the customer and customer site level
if the receipt methods are set up in this way:
• Associated receipt class has a Creation Method of Automatic.
For ACH payments of multiple invoices across multiple bill-to sites, Receivables uses
the primary receipt methods defined at the customer and customer site level as long as
the associated receipt class does not have a Remittance Method of No Remittance.
To assign iReceivables receipt methods:
1. Select the Receivables Manager responsibility select Setup, then System.
4. Enter an iReceivables credit card payment method in the Credit Card Payment
Method field.
5. Enter an iReceivables bank account transfer payment method in the Bank Account
Payment Method field.
10. Navigate to the Payment Details tabbed region to assign iReceivables receipt
methods to this customer bill-to site.
12. Repeat steps 7 to 11 for each customer and customer bill-to site.
Related Topics
Entering and Updating Customer Information, Oracle Receivables User Guide
Defining Receivables System Options, Oracle Receivables Implementation Guide
3. Set the Sequential Numbering profile option to Always Used or Partially Used.
6. In the Name field, enter a document sequence name that identifies this sequence for
iReceivables receipts, such as iReceivables Credit Card Receipts.
8. In the From and To fields, enter the effective dates for this document sequence.
14. In the Category field, enter the document category created by the corresponding
iReceivables payment method defined in Oracle Payments and Supported
Currencies, page 1-22.
17. Enter the Start and End Dates for this sequence assignment.
20. Repeat steps 5 to 19 for each document sequence to be defined for iReceivables.
Related Topics
Defining Document Sequences, Oracle E-Business Suite Setup Guide
• Set the OIR: Enable Service Charge and OIR: Service Charge Activity ID profile
options.
If migrating from Release 11i and before, the values set using the OIR: Service
Charge Activity ID and OIR: Enable Service Charge profile options are
automatically enabled in Release 12. See: Set Up Profiles, page 1-37.
7. Remain in the Receivables Activities window with the new activity that was just
created. From the Help menu, choose Diagnostics, select Examine. The Examine
window opens.
8. In the Field field, enter RECEIVABLES_TRX_ID. Make note of the value in the
Value field. This value has to be entered in the OIR: Service Charge Activity ID
profile option (see step 28, page 1-30).
11. Set the Sequential Numbering profile option to Always Used or Partially Used.
14. In the Name field, enter a document sequence name that identifies this sequence for
iReceivables service charges.
16. In the From and To fields, enter the effective dates for this document sequence.
22. In the Category field, enter the document category created by the Receivables
activity defined above.
25. Enter the Start and End Dates for this sequence assignment.
26. In the Sequence field, enter the name of the document sequence defined in step 14.
• Set the OIR: Service Charge Activity ID profile option to the value of
RECEIVABLES_TRX_ID for the new Receivables activity that was defined for
service charges.
Related Topics
Receivables Activities, Oracle Receivables Implementation Guide
Defining Document Sequences, Oracle E-Business Suite Setup Guide
Oracle Receivables Profile Options, Oracle Receivables Implementation Guide
• All payments made through iReceivables consider the grace days when
calculating payment on transactions.
2. The setup tasks for setting the grace period days for discounts are:
• If necessary, enter the grace days in the Discount Grace Days field in the Profile:
Transaction tabbed region of the Customers - Standard window or the
Customer Addresses window for the customers and customer sites.
• Set the OIR: Enable Discount Grace Days profile option to Yes. The default
value is No.
Related Topics
Oracle Receivables Profile Options, Oracle Receivables Implementation Guide
• Set the OIR: Bank Directory Source profile option to Local to access the bank branch
information (routing number) from a local table, AR_BANK_DIRECTORY, which is
downloaded from the Federal Reserve Financial Services web site.
When a customer pays an invoice by ACH bank account transfer with a routing
number that is not available in the system (CE_BANK_BRANCHES_V view), the
• Set the OIR: Bank Directory Source profile option to None to use the
CE_BANK_BRANCHES_V view as the bank directory source. If the routing
number is not present in the view, it will not be considered as a valid routing
number.
To set up the profile option, see: Set Up Profiles, Registration History, Rules, and
System Parameters, page 1-36.
3. Navigate to the E-Payments Routing Directory page and follow the instructions
given to download the directories.
4. Save the file in a local file that the Receivables system can access.
11. In the Name field, choose Import Bank Directory from the list of values.
12. In the Parameters window, enter in the Data File field the path to the local file saved
in step 5.
• If set as Y or no value, then the CP imports only new bank information from the
AR_BANK_DIRECTORY to TCA tables. It does not update the existing information.
• This CP has been added to the request group OIR Request Group All, which is
assigned to the iReceivables Internal User (ARI_INTERNAL).
5. In the Responsibility Key field, enter the new responsibility name defined above.
6. In the Available From region, choose the Oracle Self Service Web Applications radio
9. In the Menu field, choose iReceivables 2.0 Internal from the list of values for internal
users or iReceivables Account Management for external users.
14. Under System Administrator, select Security, then Users. Select Define. The Users
window opens.
17. In the Responsibility field, enter the new responsibility defined above.
18. In the From and To fields, enter the effective dates for this user.
Related Topics
Responsibilities Window, Oracle E-Business Suite Security Guide
• Registration History: Self Registration details can be viewed and modified from this
page.
• System Parameters: Various system options can be set from this page.
Set Up Profiles
To set up profile options:
1. Click Go To Task to view profiles.
Set Up Rules
To set up rules:
1. Click Go To Task from the setup checklist page to view rules.
2. Two types of rules can be setup from this page; Global Rules Setup and Operating
Unit Dependent Rules Setup.
• For Global Rules Setup, set the Customer Verification Question rule, which is
used as the verification question shown to the user in Validate Customer Access
page during self registration. Click Setup Rules to set the verification rule.
• For Operating Unit Dependent Rules Setup, rules can be set for the following
attributes. Select the organization and click Setup Rules to set any rule.
1. Site Verification Question rule, which is used as the verification question
shown to the user in Verify Access page during self registration.
4. Multi Print Limit rule, which is used to set the maximum number of
invoices for immediate printing from iReceivables.
6. Future Dated Payments rule, which is used to set the maximum limit (in
days) for future dated ACH payments through iReceivables.
7. Discount Grace Days rule, which is used to set the grace days to determine
if discount are eligible for payments through iReceivables.
2. Select the organization for which the system parameter has to be set.
Set the following parameters:
• Credit Card Receipt Method
History Details
Use the Setup Checklist page to view the Payment Audit History and Registration
History details of users.
2. Click Go To Task on the Payment Audit History row to view the Payment Audit
History Details page.
• Receipt Details, if payment was successful. Click the Receipt Number to view
the details.
• Credit card authorization details. Click the Receipt Number to view the details.
• List of Invoices and Debit Memos paid. You can also view the Deposits paid.
2. Click Go To Task on the Registration History row to view the Registration History
Details page.
• Update: Administrator can update the status. For example, if the external user
on self registration fails the challenge questions three times, the registration is
put on hold. The administrator can update this.
• The other fields are populated based on the customer chosen for registration.
Upon submission:
• Once the registration request is submitted, Administrator will not be able to modify
the Status of the Registration Request.
• UMX workflow is initiated for a new registration. Once the registration request is
submitted, workflow link is enabled and Update button is disabled.
Additional Access:
For requests for additional access, the workflow is initiated if the profile option, OIR:
Approval Required for Additional Account Access is set to a FND User Name or AME
is enabled (profile option, OIR: Use AME for Additional Access is set). If AME is
enabled then the former profile (OIR: Approval Required for Additional Account
Access) value is ignored. If both the profile values are set to NULL, then approval is not
required, and the additional account access is granted.
Click the workflow link available under Workflow Status column to view the workflow
details.
• Assign iReceivables 2.0 Anonymous Internal to the Guest User Password profile
option.
To successfully access the anonymous login pages, modify these .htm files. To
support multiple languages, copy these files, modify the alert in the logon_submit()
function and any other language dependent attributes, and place the modified files
in the appropriate directory structure. Place the modified static HTML pages in the
directory:
$OA_HTML/[country code]/
4. Assign the iReceivables anonymous login responsibility defined in step 3 to the pre-
seeded guest user account.
2. In the User Name field, query the value of the guest user account.
Here the code adds a parameter named IrcustomerId and its value sCustId to the
hash table. An illustration is provided in the file for Customer Site ID.
The following table outlines the page-level semantics, and mandatory and optional
parameters, for each iReceivables page.
Values for
<status> are
from the lookup
ARI_ACCT_STA
TUS. If aging
buckets are
used, then use
aging status
codes. The
format for the
aging status
code is:
OIR_AGING_
+<days from> +
<days to>
Note: A
correspondin
g aging
bucket must
be defined for
<days from>
and<days to>.
• ARI_CUSTOMER_SEARCH_TYPE
• ARI_INVOICE_SECTION
• ARI_ACCOUNT_DETAILS_TYPE
• ARI_ACCT_STATUS
• ARI_CUSTOMER_HEADER_LABEL
Note: Users cannot modify the seeded lookups for the lookup types
CREDIT_MEMO_REASON and AR_IREC_CREDIT_CARD_TYPES.
Users cannot add new lookup codes for the lookup types
ARI_INVOICE_SECTION and AR_IREC_CREDIT_CARD_TYPES.
For the lookup type ARI_CUSTOMER_SEARCH_TYPE, review and update the seeded
lookup codes that should appear on the Search By poplist on the Customer Search page.
For extended customer search, define lookup codes for the new customer search
attributes. Custom transaction search attributes that are defined are queried by the
procedure search_custom_customer() in the file ARICNFGB.pls. See: Extending the
iReceivables Search, page 4-6 for more information.
For the lookup types ARI_ACCOUNT_DETAILS_TYPE and ARI_ACCT_STATUS,
review and update the seeded lookup codes that should appear on the Status and
Transaction Type poplists on the Account Details page. For extended transaction search,
define lookup codes for the new transaction search attributes. Custom transaction
search attributes that are defined are queried by the procedure search_custom_trx() in
the file ARICNFGB.pls. See: Extending the iReceivables Search, page 4-6 for more
information.
The lookup type ARI_CUSTOMER_HEADER_LABEL is used to personalize header
information shown in iReceivables. The following options are available:
• Operating Unit Name: Displays the Operating Unit
By default all these values are enabled and comes in the above mentioned order. If the
Operating Unit has to be hidden, then disable Operating Unit Name option from the
4. In the User Name field, enter the user name for the applicable lookup codes.
5. In the Application field, enter Oracle Receivables. The system displays the lookup
codes.
6. To disable a lookup code, enter a date in the Effective Dates To field or deselect the
Enabled box.
Related Topics
Application Utilities Lookups and Oracle Application Object Library Lookups, Oracle E-
Business Suite Developer's Guide
Defining Receivables Lookups, Oracle Receivables Implementation Guide
3. Set the OIR: Aging Buckets profile option at the site, responsibility, or user level
to display the preferred aging buckets.
Related Topics
Oracle Receivables Profile Options, Oracle Receivables Implementation Guide
Aging Buckets and Interest Tiers, Oracle Receivables Implementation Guide
• OIR: Multi Print Limit profile option - Use the OIR: Multi Print Limit profile
option to set a limit to the number of invoices printed immediately using the BPA
Print program. If the user prints more invoices than the limit specified, then
iReceivables uses the BPA Print concurrent program to print the invoices.
• Generate BPA Stylesheets - Run the Generate Stylesheet for BPA Templates
concurrent program from BPA responsibility.
• Customize the print request messages - Users can customize the BPA print request
messages according to requirements. The messages are:
• ARI_IMMEDIATE_PRINT_PROG_NAME - BPA Immediate Print program.
For steps on setting up profile options, see: Set Up Profiles, Registration History, Rules,
and System Parameters, page 1-36.
Related Topics
Overview of Bill Presentment Architecture, Oracle Bill Presentment Architecture User's
Guide.
Print Management, Oracle Bill Presentment Architecture User's Guide.
• In some cases, the controller class for a given page may override the personalization
settings.
2. Log in to iReceivables and navigate to the Account Details page for the customer.
3. Click the available personalization link. These personalization links vary according
2. Log in to iReceivables and navigate to the Invoice page for the customer.
2. Log in to iReceivables and navigate to the Payments page for the customer.
3. To display receipt flexfields in the Payments page, click the personalization link
Personalize Payment Row. To display transaction line-level flexfields in the Payment
page, click the personalization link Personalize Application Table.
Related Topics
Planning and Defining Descriptive Flexfields, Oracle E-Business Suite Flexfields Guide
Creating Admin–Level Personalizations, OA Framework Personalization and Extensibility
Guide
Transaction Flexfields, Oracle Receivables User Guide
Custom procedure for allowing Payment should have the following signature:
procedure VALIDATE_PAYMENT(
p_cust_account_id IN NUMBER
,p_cust_site_use_id IN NUMBER
,p_session_id IN NUMBER
,p_payment_schedule_id IN NUMBER
,x_return_status OUT NOCOPY VARCHAR2
,x_msg_data OUT NOCOPY VARCHAR2);
For dispute and print, the signature is similar, with PAYMENT replaced with DISPUTE
and PRINT respectively. The procedure should return status as either S (Success) or E
(Error) and if it returns an Error, then the error message in x_msg_data procedure, is
shown in Account Details and Transaction List pages.
• Make sure your voice messages reference your iReceivables web site.
• Have your collectors mention your iReceivables web site when speaking with
customers.
• Advertise the iReceivables web site internally so that Sales, Collections, and
Customer Service personnel start to use the application regularly.
• Incremental Load: Loads only the data that has been modified since the
previous load for all dashboards. Schedule incremental load to run as often as
required to keep the ECC dashboards current.
• Metadata Load: Loads Descriptive Flexfield (DFF) metadata. If there are any
changes to the DFF definition, then you must run the program first with the
Metadata Load option and then the Full Load option so that the DFF changes
are reflected in the command center.
3. In the Languages field, enter one or more language codes for the output. For
multiple language codes, use the format AA,BB,NN. For example, enter US,AR,KO.
If the field is left blank, then the data will be loaded for the base language only
(usually US).
4. Select the log level that you want the program to report. The default value is Error.
8. Monitor data loading using the Data Load Tracking page of the ECC Developer
responsibility.
AR: Aging Buckets for ECC Use this site-level profile to set aging
templates for Receivables Command Center
components including the Transactions Aging
for Outstanding Receivables chart. Enter a
number to define the aging bucket
AR: History Range for ECC This site-level profile uses the Oracle
Receivables history range for the Payment
History dashboard. Enter the number of days
used for a specific date range.
2. Navigate to Setup, then Transactions. Select Approval Limits. The Approval Limits
window opens.
3. In the User Name field, enter the first approver for defining approval limits.
4. In the Document Type field, select Credit Memo from the LOV.
6. In the From Amount and To Amount fields, enter the minimum and maximum
approval amounts in this currency for this user.
7. If this approver is the primary approver for this range, check the Primary box.
Related Topics
Approval Limits, Oracle Receivables Implementation Guide
Note: If the invoices calculate tax, the credit memos assigned to them
must also calculate tax. For this, ensure that the invoice transaction type
and the credit memo transaction type both have the Tax Calculation
box checked. If necessary, set up a separate transaction type that does
not calculate tax for the On Account credit memos.
4. In the Credit Memo Type field, enter the credit memo type to use when crediting
items with this transaction type.
Related Topics
Transaction Types, Oracle Receivables Implementation Guide
3. In the Name field, enter a name that identifies this batch source as a credit memo
transaction batch source for iReceivables.
5. Check either the Automatic Transaction Numbering box or the Copy Document
Number to Transaction Number box.
Related Topics
Transaction Batch Sources, Oracle Receivables Implementation Guide
Related Topics
Setting Up the AME Credit Memo Request Workflow, Oracle Receivables User Guide
Setting Up Oracle Workflow, Oracle Workflow Administrator's Guide
Configuring iReceivables
iReceivables includes the configuration package ARI_CONFIG, written in PL/SQL. The
ARI_CONFIG configuration package can be used to modify attributes in iReceivables
without having to make changes to any other part of the code. ARI_CONFIG contains
in two files the variables and functions for this configurable component. The two files
are ARICNFGS.pls (package specification) and ARICNFGB.pls (package body).
The ARICNFGS.pls package specification contains variables referenced in the
ARICNFGB.pls package body. Functions and procedures in the package body are
referenced elsewhere in the iReceivables code.
Users can modify these components using the ARI_CONFIG configuration package:
• customer id
• encrypted customer id
• language
With these parameters, users can create dynamic content, such as marketing messages
and personalized account information.
For more information about the get_homepage_customization parameters, see the
documentation included in ARICNFGB.pls.
If the function returns Y for the RENDER flag, iReceivables displays the current data or
displays the messages "No Discounts" or "No Credit Requests" if there is no data. If the
procedure returns N for the RENDER flag, the region is not displayed.
Depending on the customer or on the business needs, users can also replace the default
messages with custom messages or information display.
3. In the Personalization Structure table, scroll down to attachment, and click the
Personalize button.
4. In the Personalization Properties table, set the value of Rendered property to true at
the Site, Organization, or Responsibility level.
5. Click Apply. The Attachments section is now available in the Accounts Summary
page.
• Personalize the Invoice Lines region of the Enter Dispute Details page and the
Review Credit Request page to display the invoice line flexfield.
• Personalize the Invoice Lines region of the Enter Dispute Details page to display a
Search region to search by invoice line attributes, when there is a large number of
invoice lines.
Note: The Enter Dispute Details page displays the default message
when no customized message is defined.
Setup Tasks
The setup tasks for personalizing the email information if new to iReceivables are:
• Enable Contact Information rule
• Create a new rule as required giving values for the following parameters:
• Customer
• Language String
• Page
• If the rule is not set, then the contact information is taken from WEB_HTML_CALL
attribute of the ARICONTACTUS function.
Related Topics
Form Functions Window, Oracle E-Business Suite Security Guide
These procedures are called by the client Java code whenever users initiate a search
using the additional custom search attributes.
To extend the iReceivables search:
• Use the Lookups window to define look up codes for custom transaction or
customer search attributes. See: Review and Update Receivables Lookups, page 1-
43.
• Use the Messages window to define error messages that refer to validations on the
input parameters.
Related Topics
Message Window, Oracle E-Business Suite Developer's Guide
• Do not insert returns. Inserting returns into HTML-based messages can cause a
fatal system error.
Before editing iReceivables messages, make a copy of the Message Dictionary runtime
message file and store it in a directory protected from upgrades. The Message
Dictionary runtime message file is located in the directory:
$AR_TOP/mesg/<language>
Related Topics
Implementing Message Dictionary, Oracle E-Business Suite Developer's Guide
2. Select the Account tab. The Template LOV lists all available templates.
3. Select the template to be customized from the LOV. Click Export. This launches the
report. Ensure that this is the correct report that needs to be customized. Note the
template name.
5. In the Name field, type the name of the template to be customized. Click Go.
7. The template file is available under the File Name section. Select the Download
option and save the template locally.
8. Open the downloaded template. The data fields in the template are grayed out.
Important: The first column will always have F prefixed to the text.
This indicates that from this point onwards, the data is to be
repeated for each row. Each row will end with a column name that
is suffixed with E. When new columns are added, ensure that the
first column is prefixed with F.
9. Select a data field, right click, and select Properties. Click the Add Help Text button.
This launches the Form Field Help Text window. The text box shows the data
source for this template. Note this down. See How to Identify Available View
Objects (VO) Attributes, page 4-9 to identify the attributes that can be used to this
template.
10. Save this template under a new name using the Save As option under File. Open
the saved file and make the required modifications to the template.
Example
Copy and paste an already grayed out field and modify its properties. Right-click
the field and select Properties. In the Text Form Field Options window, in the
Default Text field, provide the new attribute name. Select the Add Help Text
button. This launches the Form Field Help Text window. Modify the value in the
text box to the exact attribute required in the customized report. Please note that
this field is case-sensitive.
Be sure to start the first column with F as prefix and end the last column with E as
suffix. The attributes for these should be the same as the one given in the VO
attributes list, for the data to loop against a given header context. Save the final
template with the RTF file format.
11. Navigate to XML Publisher Administrator and select Templates. The Templates
Search page opens.
12. Click Create Template to upload the new customized template. Give the new
Template Name and Code. Under Applications, select the appropriate application,
for example, iReceivables. In the Data Definition, use the Search option and select
the correct data definition for the new template. Use the Browse button to select the
saved version of the new customized template. Select the Type as RTF. Click Apply.
After successful upload, the file can be found under Localized Templates on the
View Template page.
2. Expand the Business Component References Details section to see the View Objects
list.
3. Click AllDebTrxTableVO link. . It shows the attributes of the VO. These attribute can
be used in the Templates above, Custom Template without Data Template, page 4-7
.
2. Under the Statement Download section, the Template LOV lists the available
templates for statement downloads. Select the template to be customized from the
LOV. Click the Download button. This launches the report. Ensure that this is the
correct report that needs to be customized. Note the template name.
4. In the Name field, type the name of the template to be customized. Click Go.
5. From the search results, select the link for the template. This launches the View
Template page.
6. The template file is available under the File Name section. Select the Download
option and save the template locally.
7. Open the downloaded template. The data fields in the template are grayed out.
Important: The first column will always have F prefixed to the text.
This indicates that from this point onwards, the data is to be
repeated for each row. Each row will end with a column name that
is suffixed with E. When new columns are added, ensure that the
first column is prefixed with F.
8. Right- click a grayed out field and select Properties. In the properties window, click
the Add on Help Text button. The Form Field Help Text window opens. Note the
data source for the template.
9. In the application, navigate to Home and select the XML Publisher Administrator
responsibility. Under Home, select Data Definitions to open the Data Definitions
page.
10. In the Name field, enter the data definition noted from the template, for example,
iReceivables Customers Statement Data Definition, and click Go.
11. From the search results, select the correct data definition. The View page opens.
12. Select the Data Template file (xml file format) under Files to download and save the
data template.
13. Make the required changes to the data template to get the required values (through
queries) for the customized report. See Tags Present in the Data Template, page 4-
11 for some of the tags used in the data template.
14. Select the Update file button to upload the modified data template.
15. Now, open the previously saved template file (step 6). Select File, click Save As.
Give a new name and save the file.
16. Open the newly saved template and make the required modifications.
Copy and paste an already grayed out field and modify its properties. Right-click
the field and select Properties. In the Text Form Field Options window, in the
Default Text field, provide the new attribute name. Select the Add Help Text
button. This launches the Form Field Help Text window. Modify the value in the
text box to the exact attribute required in the customized report. Please note that
this field is case-sensitive.
18. Give a new Template Name and Code, as desired. Under Applications, select the
appropriate application, for example, iReceivables.
19. In the Data Definition field, search for and select the correct data definition, for
example, iReceivables Customers Statement Data Definition.
20. Under Template File section, click Browse. Select the customized template.
21. Select the Type as RTF from the LOV. Click Apply.
22. After successful upload, the file can be found under Localized Templates in the
View Template page.
23. Navigate to the Account Summary page for the customer. The Template LOV under
Statement Download will have the new customized template.
• properties: There are many properties which define the outcome of the data
template. Some of the properties used are:
• xml_tag_case: The value for this is as_are. This defines that the elements
mentioned in the dataStructure needs to be in the same case in the output of
this template. By default, if this property is not set, the element names are
converted to upper case.
• include_rowsettag: The value for this is either true or false. The default value is
true. This can be used if the sqlStatement might return multiple rows. When set
to true, the output xml includes a row set tag with the name LIST_<group name
mentioned>, for example, <LIST_Customers>. If this property is set to false this
tag is not included in the output.
• sqlStatement: This tag holds a single sql query, which can be either a select
statement or procedure call. This has an attribute name which is used in the group
tag in source attribute. The query may contain bind parameters. The bind
parameters are passed by iReceivables code. The parameters passed are created as
tags in the output xml.
• dataStructure: This tag holds one or more groups based on the number of
sqlStatement in the dataQuery tag.
• group: This tag contains the elements defined in the group. The group tag has two
attributes, name and source. The name attribute is used as the tag in the output xml
and source attribute is where the sqlStatement name is defined. A group is always
formed based on a source which is either a query or a procedure.
• element: The element tag defines the name of the element which is seen in the
output xml. The element tag has two attributes, name and value. The name attribute
gives the name which is displayed in the output xml and the value tag gives the
value from the query which is defined in the source of the group.
Purge Process
To purge the print records and user session details records from OIR tables, run the
following two concurrent programs.
Purge User Session Data:
System Administrator can run the concurrent program Purge
AR_IREC_PURGE_USER_ACCT_SITES Table to purge user session data from the
AR_IREC_USER_ACCT_SITES_ALL table.
• It is recommended to schedule this request to run daily.
• Input parameter is the purge date. If provided, all records up to the purge date are
deleted from the table. If it is not provided, then all records which are one day older
than the system date are deleted.
• This CP is present in the request group OIR Request Group All, which is assigned
to iReceivables Internal User (ARI_INTERNAL).
• The CP takes current date as the default parameter. If the date parameter is not
provided, the table is purged automatically, matching the
FND_CONCURRENT_REQUESTS dates.
• This CP is present in the request group OIR Request Group All, which is assigned
to iReceivables Internal User (ARI_INTERNAL).
Installment Number
To view the Installment Number of the transactions on the Account Details page,
perform the following steps:
1. Enable personalization.
2. Navigate to the Account Details page. Click the 'Personalize: This table displays the
results of …' link.
4. In the Personalization Properties table, select the Site value of Rendered as True.
Click Apply.
5. After the change has been saved, click the Return to Application link. Installment
Number of the transaction is now displayed on the Accounts Details page.
Diagnostics Reports
There are two diagnostics reports available for iReceivables, Ireceivables Internal report
and Ireceivables External report. These reports can be used for troubleshooting or for
viewing various parameters of the application instance. Perform the following steps to
execute the reports:
1. Select the Application Diagnostics responsibility from the Oracle E-Business Suite
home page and click Diagnose.
2. In the Diagnostic Tests page, click the Select Application button. Select Receivables
from the Search page.
Ireceivables Internal
Input parameters for this report are Responsibility Name and Operating Unit. The
report provides the following details:
• List of applied patches
• Rules
• CVV Encryption
• Lookups
• List of personalizations
• MO Org settings
Ireceivables External
Input parameters for this report are Responsibility Name and User Name. The report
provides the following details:
• List of applied patches
• Aging details
For more information on diagnosis, see Oracle Diagnostics Framework User's Guide.
Major Features
Major features of iReceivables include:
• User Interface
• Customer Search
• Online Aging
• Interactive Invoice
• Advanced Payment
• Dispute a Bill
• Multi Print
• Multi Pay
User Interface
The user interface enhances the user experience, providing a rich array of functionality
and high performance. For example, the configurable Account Summary home page
offers one-click access to most of the tasks to be performed in iReceivables. Hint
messages alert the user to special conditions or specific actions that must take place. In
addition, IT professionals can configure every iReceivables page to avoid burdening
users with unnecessary fields or information, thereby presenting only the most relevant
details to each user.
Customer Search
iReceivables provides internal users, such as sales representatives, collections agents
and upper management, a customer search engine based on the Oracle database full
text indexing. This technology allows an internal user to search for customer account
information by transaction number or by using any of these customer data elements:
customer name, customer number, tax registration number, contact name, contact
phone number, contact fax number, and customer location. A multi-record display of
search results allows drill-down to view account details for a customer or customer bill-
External users with access to multiple customers or multiple sites of a single customer
can search for account information by customer name or transaction number.
The search criteria can be customized according to business needs with the custom
customer search. Use this to add your own custom search-by attributes for your
iReceivables customers and customer sites. These custom attributes can then be used to
search for customer accounts in the Customer Search page.
Contact Us Link
In the Customer Search page, the Contact Us link picks the value from the following
settings:
• If the MO: Default Operating Unit is set for the Site, App, Resp, or User, then for
that Operating Unit if the Contact Information rule is set, it displays the value
specified in the rule in the Customer Search Page.
• If no rule is set, then it picks the WEB_HTML_CALL value from the function
ARICONTACTUS.
• Category, currency, and transaction status search to fine tune the inquiry.
• Advanced Search that lets users display transactions that match specific selection
criteria based on date range, due-date range, or amount range. For example, a
customer or employee can display all transactions for Superior Plumbing Co. with
outstanding amounts ranging from $100 to $10,000 and with due dates between 01-
JAN-1999 and 01-FEB-1999.
• Users can search transactions for a single organization or for multiple organizations
within a single search operation.
Users can also customize the search criteria according to business needs with the
custom transaction search:
• Use the custom transaction search to add your own custom search-by attributes for
iReceivables transactions. All customers can use these custom attributes to search
for transactions in the Account Details page. For example, a shipping company can
allow its users to search by bill of lading number, or a real estate company can
allow its users to search by property address.
Online Aging
The Online Aging feature allows iReceivables external users to view the same aging
information as collectors in the Receivables Collections workbench. If aging is enabled,
the aging buckets appear on the customer's home page alongside the customer's
account balance information. The Account Details page also supports searching by
aging status. For example, the user can search for all invoices that are "1-30 Days Past
Due". This functionality in the Account Details page lets the user drill down to the
transactions that make up an aging bucket total.
iReceivables can be configured to use any of the aging bucket styles defined in Oracle
Receivables at site, responsibility, and user levels.
Interactive Invoice
Oracle iReceivables displays invoices in a format that closely resembles a printed
invoice, with a real-time Balance Due. Users can display Receivables invoice-specific
and invoice line-specific flexfields in the Invoice page. Users can toggle between invoice
lines and invoice activities, including adjustments, payments, credits, charges and
disputes. Full drill-down capabilities point to related transactions such as payments and
credits.
• Use the Pay button to make a full or partial payment by credit card or bank account
transfer.
• Use the Dispute button to dispute a bill online. The dispute request automatically
triggers the Credit Memo Workflow process, routing the request for internal
approval.
• Use the Printable Page button to optimize the invoice presentation for printing on
paper.
Advanced Payment
iReceivables offers an Advanced Payment page to change the default payment method,
enter new credit card information, or make a partial payment. The Manage Payment
Methods button takes you to the Payment Details page, from where you can manage
credit cards and bank accounts at the Account level.
The Manage Payment Methods - Site button enables you to you to manage credit cards
and bank accounts at the Site level. If you navigate to the page by selecting All
Locations, then credit cards and bank accounts attached to the Primary Bill To is
Dispute a Bill
Customers can dispute all or part of an open invoice by choosing the Dispute button in
the Invoice page or Activities page. Choosing the Dispute button lets the customer enter
the following information about the dispute:
• Reason for the dispute.
• Any comments
Once the user submits the dispute, the system creates a credit memo request.
Users can control access to the Dispute Invoice function via function security. The
access to the Dispute Invoice function can be allowed or denied for both customers and
internal users. If customer access is denied to the Dispute Invoice function, internal
users, such as sales or customer service representatives, can still enter a dispute on the
customer's behalf.
• The existing dispute amount per each invoice can be seen in the transaction details
table.
• In the Dispute Review page, Dispute Amount per Invoice and Total Dispute
Amount can be seen.
• Once the dispute is submitted, all the successful disputes are shown in a table with
the transaction number and the dispute request number.
• Unsuccessful disputes are shown in another table with the transaction numbers and
the reason for failure.
• OIR: Allow Zero Payment Amount (When Dispute and Discount Amount >= Total
Remaining Amount)
Use this profile option to allow zero amount payments in iReceivables, when the
total of Dispute and Discount Amount is greater than, or equal to the Total
Remaining Amount.
• When set to Account and Bill To, if the user navigates at the Account level, then
credit cards and bank accounts attached from both the account and primary site
are displayed. If the user navigates at a site level, then credit cards and bank
accounts attached from that site and account level are displayed.