This chapter covers the following topics:
You must complete these setup tasks in Oracle iReceivables. Use the checklist in this section to complete the appropriate setup steps.
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 Receivables Release 12.
Set up Oracle Bill Presentment Architecture Release 12.
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:
| Step Number | Step Description |
|---|---|
| 1 | Define iReceivables Internal Users. See: Define iReceivables Internal Users. |
| 2 | Define iReceivables External Users and Customer Access. See: Define iReceivables External Users and Customer Access. |
| 3 | Define Receipt Class and Receipt Method. See: Set Up Receipt Class and Receipt Method. |
Related Topics
Setting Up, Oracle Receivables Implementation Guide
Setting Up Oracle Workflow, Oracle Workflow Administrator's Guide
Configuring Oracle Payments, Oracle Payments Implementation Guide
Understanding Oracle Payments, Oracle Payments User's Guide
Viewing Online Bills, Oracle Bill Presentment Architecture User Guide
Oracle User Management, Oracle E-Business Suite Security Guide
Define your internal users for iReceivables. Internal users are the personnel in your company, such as collectors and salespersons, who have access to iReceivables customer information. Internal users have access to the full customer search capability to display customer information.
Note: You must have access to the system administrator responsibility to perform this setup step.
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:
Select the System Administrator responsibility.
Navigate to the Users window.
Query or enter the users in your company that you want to have access to iReceivables.
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.
Open the Direct Responsibilities tabbed region for this user.
In the Responsibility field, enter iReceivables 2.0 Internal.
Note: For internal users performing implementation setup for iReceivables, add iReceivables Setup responsibility.
In the From and To fields, enter the effective dates for this user.
Save your work.
Repeat steps 4 to 8 for each internal 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
Run the Customer text data creation and indexing concurrent program to index the customer information in your applications database. The first time that you run this concurrent program, it builds the indexes in your database. Depending on the volume of your customer data, the first run may take a fairly long time to complete.
Additional Information: This index search is available only for internal users.
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 concurrent program act upon updates only, and therefore should take much less time to complete.
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.
To build the customer indexes in your applications database:
Select the Receivables Manager responsibility.
Navigate to the Submit Request window.
In the Name field, choose Customer text data creation and indexing from the list of values.
In the Build Compact Index? field, enter:
No to index all customer information.
Yes to index customer and customer site information only.
Choose the Schedule button.
In the Schedule window, choose Once.
To schedule a regular update of your customer indexes:
Select the Receivables Manager responsibility.
Navigate to the Submit Request window again.
In the Name field, choose Customer text data creation and indexing from the list of values.
Choose the Schedule button.
In the Schedule window, choose Periodically.
In the Start At and End At fields, set the date and time for this program run.
In the Re-run Every field, enter 1 Day.
Related Topics
Request Submission, Oracle E-Business Suite User's Guide
Define your external users and their level of customer access to iReceivables. You can provide external users with access to their own bill-to site only, to multiple customers or customer sites, or both, by assigning users the customer contact role Self Service User. An external user has access to the search criteria Customer Names and Transaction Numbers to display account information for each applicable customer and customer site. There are two types of external users:
For business-to-business external users, use the Contact: Roles region of the Customers - Standard window to assign iReceivables external users to customers and customer sites with the customer contact role Self Service User.
For business-to-consumer external users, use the Customers - Standard window header region to enter users with the customer type Person.
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.
Additional Information: External users can only add attachments and view existing attachments. They cannot modify attachments.
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.
Important: When an external user has access to multiple customers, it is mandatory to enable a default currency using the profile option, OIR: Default currency code.
By default, users with the iReceivables Account Management responsibility have access to the Manage Customer Account Access link, for use with the iReceivables Self Registration feature. If you do not plan to use Self Registration, then please remove this function from the iReceivables Account Management responsibility using function security. See: Define Function Security.
To define iReceivables external user for Business-to-Consumer Setup, with access to one site or multiple customer sites, for a single customer:
Select the Receivables Manager responsibility.
Navigate to the Customers - Standard window.
Select Customer Type as Person.
Query or enter the customer name.
Navigate to the Addresses tabbed region and choose the customer address.
Open the Contacts: Roles tabbed region.
Enter the name of the external user and the user's contact information.
In the Description field, enter the role Self Service User.
Save the work.
To assign this user to a second site of the same customer, repeat steps 5 and 6.
From the Customer Standard form, query a customer, open the Account, open one of the Sites. Add a Contact by using the Communications tab.
Assign the role Self Service User to this contact.
Save the work.
To assign this user to additional sites of the same customer, repeat steps 10 to 13.
Select the System Administrator responsibility.
Navigate to the Users window.
Enter the User Name and Password of the external user.
In the Customer Name field, choose any version of the external user's name defined in step 7 from the list of values.
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.
Open the Direct Responsibilities tabbed region.
In the Responsibility field, enter iReceivables Account Management.
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:
HZ: Enable Party Search = YES HZ: Duplicate Allowed = No HZ: Enable Duplicate Prevention at Party Creation = Person or Organization HZ: Match Rule for Contact Duplicate Prevention = SAMPLE: SEARCH HZ: Match Rule for Organization Duplicate Prevention = SAMPLE: SEARCH HZ: Match Rule for Person Duplicate Prevention = SAMPLE: SEARCH
Contact Duplication Prevention, Oracle Receivables User Guide
To define iReceivables external user for Business-to-Business Setup, with access to multiple customer sites, for multiple customers:
Select the Receivables Manager responsibility.
Navigate to the Customers - Standard window.
Select Customer Type as Organization.
Query or enter the first customer to assign to an external user.
Open the Contacts: Roles tabbed region.
Enter the name of the external user and the user's contact information.
In the Description field, enter the role Self Service User.
Save the work.
Query the next customer in the Customer Name or Number field.
Open the Contacts: Roles tabbed region.
In the Last field, choose the external user name entered in step 6 from the list of values.
In the Description field, enter the role Self Service User.
Repeat steps 9 to 12 for all customers to be assigned to this external user.
Save the work.
Select the System Administrator responsibility.
Navigate to the Users window.
Enter the User Name and Password of the external user.
In the Customer Name field, choose any version of the external user's name defined in step 6 from the list of values.
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.
Open the Direct Responsibilities tabbed region.
In the Responsibility field, enter iReceivables Account Management.
In the From and To fields, enter the effective dates for this user.
To define an iReceivables external user for Business-to-Consumer Setup:
Select the Receivables Manager responsibility.
Navigate to the Customers - Standard window.
Query or enter the customer name.
Assign the user the Customer Type Person and enter the necessary Person party details.
Save the work.
Select the System Administrator responsibility.
Navigate to the Users window.
Enter the User Name and Password of the external user.
In the Customer Name field, choose any version of the external user's name defined in step 4 from the list of values.
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.
Open the Direct Responsibilities tabbed region.
In the Responsibility field, enter iReceivables Account Management.
In the From and To fields, enter the effective dates for this user.
The profile option OIR: Minimum Characters for Search can be used to restrict character search for external users. For example, if the value is set to three, minimum three characters are required to search for a customer. Value can be set as null for blind search.
Additional Information: This profile option does not hold for Credit Requests.
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 iReceivables Self Registration feature lets users register for iReceivables Account Management (application) access to their customer account data. On the Self Registration pages, an external user is given three attempts to answer a challenge/response question correctly. These questions are setup using Rules by the administrator. If all three attempts are unsuccessful, the user is only able to re-register according to the Self Registration profile option settings that are specified.
For more information on setting up Rules and Profile Options, see: Set Up Rules, Profile Options, and System Parameters.
If registration is successful, iReceivables creates a user account, assigns the user the customer contact role Self Service User, and forwards the information necessary to access customer account data.
Note: After successful registration, this new customer contact is not available to the iReceivables customer search engine until the next running of the Customer text data creation and indexing concurrent program. See: Index the Customer Database for more information.
The self registration process can be performed using the following processes. Users can set up any of these methods as per preference.
Selecting the Register Here link created on the main portal page with or without SSO.
Accessing SelfRegistration.jsp page. See Bookmark the Self Registration Page
Accessing the OIR Self Service Portal page, http://machinename:portnumber/OA_HTML/IrecVisitor.jsp\. Add the iReceivables Self Service responsibility to the pre-seeded Guest User for this. For more information on setting up the Self Service portal, see: Set Up for Self Service Portal.
For additional access, select the Manage Customer Account Access link, when the user logs in to the iReceivables Account Management responsibility.
Note: By default, users with either the iReceivables Account Management responsibility or any responsibility that includes the iReceivables Account Management menu have access to the Manage Customer Account Access link. If responsibilities have been defined with menus other than the iReceivables Account Management menu and want to provide users with access to the Self Registration feature, then add the Manage Customer Account Access function to the menus attached to these custom responsibilities. Users can add or remove association to an account using the Request Additional Customer Access or Remove Access options from the Manage Customer Account Access page.
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.
Perform the following steps to enable self registration:
To set up iReceivables Self Registration:
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.
In Oracle E-Business Suite, select the System Administrator responsibility.
Assign the iReceivables Registration responsibility to the pre-seeded guest user account specified by the Guest User Password profile option with the following steps:
Under System Administrator, navigate to the Profile and select System. The Profile System Values window opens.
In the Profile field, enter the user account and make note of the value (value format: user/password).
Navigate to the Users window.
In the User Name field, query the value of the same user account.
Navigate to the Responsibilities tabbed region.
Add the iReceivables Registration and iReceivables Account Management responsibilities.
Assign an e-mail address to the Contact Us global icon.
Enter the email address of the Self Registration administrator (or other qualified user responsible for answering inquiries from external users about Self Registration).
Navigate to the Form Functions window.
Query the function ARI Self Registration Contact Us.
Choose the Web HTML tab.
Enter the Self-Registration administrator's email address in the HTML Call field, using the format: mailto:<userid>@<domain>.com.
Note: User may need to restart the web server for the update to take effect.
Switch to the Applications Developer responsibility.
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.
ARI_REG_APPLICATION_LOGIN_URL - Enter the login URL to access iReceivables applications.
Additional Information: Passwords created are case sensitive or case insensitive depending on the EBS Profile Option, SIGNON_PASSWORD_CASE. If this is set to NULL or Insensitive, the passwords in OID will be in lowercase irrespective of how it was entered. If set to Sensitive, passwords will be same as when entered.
The Self Registration URL can be bookmarked using the URL http://<machinename>:<port>/OA_HTML/SelfRegistration.jsp. The pre-seeded guest user should have iReceivables Account Management responsibility assigned.
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.
Redirect Self Registration Page:
The profile option, OIR: Self Registration Redirect URL, redirects external users who cancel the registration process coming through the bookmarkable Self Registration page, to the URL specified in the profile. If this profile value is set, the user is redirected to the URL specified. If not set, then the user is redirected to the URL specified in profile value APPS_SERVLET_AGENT, to which AppsLocalLogin.jsp is appended. For example, http://<machinename>:<port>/OA_HTML/AppsLocalLogin.jsp
Set the Registration Hold profile options, OIR: Registration Hold Domain and OIR: Registration Hold Duration, to manage user re-registration.
OIR: Registration Hold Domain: If a user is unsuccessful in completing the self registration process, iReceivables prevents this user from attempting to re-register. Use this profile option to determine whether iReceivables prevents this user only or all users belonging to the same customer account from attempting to re-register.
OIR: Registration Hold Duration: This profile option works in conjunction with the OIR: Registration Hold Domain profile option. Use this profile option to set the number of days that iReceivables prevents a user or all users belonging to the same customer account from attempting to re-register.
Related Topics
User Profiles and Profile Options in Oracle Application Object Library, Oracle E-Business Suite Setup Guide
Form Functions Window, Oracle E-Business Suite Security Guide
Message Dictionary, Oracle E-Business Suite Developer's Guide
Defining Workflow Process Components, Oracle Workflow Developer's Guide
Managing Business Events, Oracle Workflow Developer's Guide
Customer verification questions are used to verify access at the account level during self registration. The questions are set through the Customer Verification Question rule under iReceivables Setup. For information on setting up rules, see: Set Up Rules.
Users can create rules specific for a customer. Select the verification type from the Rules List. The following options are available:
Set a question and its answer. During self registration, the user is challenged with this question, and is allowed to proceed further only if the exact answer is provided.
Dynamic Customer Verification Question provides the flexibility to define questions at the Customer Verification rule. When the user tries to Self Register for a customer account, it challenges the user. The answer should be provided is based on the customer the user is trying to register to. Maximum of three questions can be set at Customer Account level.
The option Dynamic Customer Verification Question is used to set the rule for Customer Verification Question, which has 15 parameters, with three sets of five parameters each. If first set is filled, then the user has to answer one question during Self Registration. If two sets are filled, the user has to answer two questions and if three sets are filled, then user has to answer all three questions. All the questions have to answer correctly for proceeding to the next step in the Self Registration train. The following parameters are available:
Question: Question to be asked to the user during self registration.
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.
Important: Customer related information can be found in Receivables Manager, Customer Standard form.
HZ_CUST_ACCOUNTS Join Column: The column from HZ_CUST_ACCOUNTS table to be joined with Answer Table Join Column to get a unique record.
Tables can be added to or deleted from the Answer Table.
Navigate to Application Developer Responsibility, then to Flexfield, Descriptive, then Values. Enter Application as Receivables.
Enter Title as iReceivables Customer Verification Question and click Find.
Enter the table name in the Value field. Enter the table description. Select Enabled.
Important: The table added should be able to be joined with HZ_CUST_ACCOUNTS table to get a unique record.
The table added should be present in AR schema and its reference in APPS schema.
To remove a table, deselect the Enabled check box and set To Date prior to current date.
Site verification questions are used to verify access at the site level for the user during self registration. The questions are set through the Site Verification Question rule under iReceivables Setup. For information on setting up rules, see: Set Up Rules.
Users can create rules specific to their site. Select the site verification type from the Rules List. The following options are available:
Dynamic Site Verification Question provides the flexibility to define questions at the Site Verification rule. When the user tries to Self Register for a customer bill to site or all locations, it challenges the user. The answer should be provided based on the customer bill to or the oldest bill to site information (for all locations) the user is trying to register to. Maximum of three questions can be set for Site Verification.
The option Dynamic Site Verification Question is used to set the rule for Site Verification Question, which has 15 parameters, with three sets of five parameters each. If first set is filled, then the user has to answer one question during Self Registration. If two sets are filled, the user has to answer two questions and if three sets are filled, then user has to answer all three questions. All the questions have to answer correctly for proceeding to the next step in the Self Registration train. The following parameters are available:
Question: Question to be asked to the user during self registration.
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.
Important: Customer bill to site related information can be found in Receivables Manager, Customer Standard form.
HZ_PARTY_SITES Join Column: The column from HZ_PARTY_SITES table to be joined with Answer Table Join Column to get a unique record.
Tables can be added to or deleted from the Answer Table.
Navigate to Application Developer Responsibility, then to Flexfield, Descriptive, then Values. Enter Application as Receivables.
Enter Title as iReceivables Site Verification Question and click Find.
Enter the table name in the Value field. Enter the table description. Select Enabled.
Important: The table added should be able to be joined with HZ_PARTY_SITES table to get a unique record.
The table added should be present in AR schema and its reference in APPS schema.
To remove a table, deselect the Enabled check box and set To Date prior to current date.
Select Yes, No, or null. If Yes is selected, the challenge question is based on a previous invoice. If No or null is selected, the site verification step is skipped.
Select Yes, No, or null. If Yes is selected, the challenge question is based on a previous payment. If No or null is selected, the site verification step is skipped.
Select Yes, No, or null. If Yes is selected, the challenge question is based on a previous invoice and payment. If No or null is selected, the site verification step is skipped.
Set a question and its answer. During self registration, the user is challenged with this question, and is allowed to proceed further only if the exact answer is provided.
Self Service Portal page can be used as a landing page for external users for both Registration and Login. This page can be used in both Single Sign On (SSO) and non-SSO environments.
Assign iReceivables Self Service and iReceivables Account Management responsibility to the guest user.
(Optional) Assign an iReceivables External User Responsibility Key value to the profile iReceivables Self Service Responsibility. This is required only if the customer uses self service registration using iReceivables in an SSO environment.
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.
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.
The iReceivables Self Service Portal page can be accessed in two ways. The following URLs direct to the same page. The page can be customized for external users.
Using the IrecVisitor.jsp URL http://<machinename>:<port>/OA_HTML/IrecVisitor.jsp
Using the function URL http://<machinename>:<port>/OA_HTML/OA.jsp?OAFunc=OIR_SELF_SERVICE_HOME_PAGE.
If Single Sign on (SSO) is enabled, then in the portal page, the Login Here button is shown in Already registered on our Site region. iReceivables checks the profile Applications SSO Type set with value SSWA w/SSO or Portal w/SSO for SSO.
When SSO is enabled, clicking Register Now takes the user to the Profile User Creation page. Once the registration process is completed, the user is redirected to the Portal page. Click Login Here to login to iReceivables. Based on the responsibilities assigned to the user, the following scenarios can happen:
User does not have valid iReceivables External User responsibility:
iReceivables checks if any responsibility assigned to the user has access to the iReceivables External Access function. If not, then the user is redirected the Partial Registration page.
Note: This usually happens to first time users without iReceivables External User responsibility.
Click Continue. This assigns the iReceivables External User responsibility as specified in the profile iReceivables Self Service Responsibility. If this value is not set, then it assigns standard iReceivables Account Management responsibility and redirects the user to the Self Registration process train. User has to complete the registration process and get access to a customer account.
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.
If SSO is not enabled, then the email and Password fields are shown in Already registered on our Site section of the portal page. Click Register Now to navigate to the iReceivables Self Registration page. Complete the registration process to get access to the customer account and iReceivables External user responsibility. After registration, fill the email and Password fields to log in. The user is redirected to the responsibility navigator page, to select the responsibility and function to access iReceivables.
Grouping of Accounts enables external users to group their accounts or sites. My All Locations link is available when the user has access to more than one site for an account, but not to all the bill to sites. Click this to get a summary of the account view for the account across all the sites the user has access to.
This feature is enabled using the profile option OIR: Account Grouping. Set it to one of the following values as required:
No Grouping: Account grouping is not enabled.
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.
The list of available currencies in the Account Summary page and the Account Details page is based either on the profile amounts or on the amounts enabled in the credit profile. These profiles can be specified at the customer level and customer site level. If there are transactions for a customer in currencies which not defined in the customer profile, these are also shown in iReceivables Account Summary and Account Details page.
Use the Customers window to define credit profiles and profile amounts for iReceivables customers and customer bill-to sites.
To define currencies for a customer:
Select the Receivables Manager responsibility.
Navigate to the Customer Summary or the Customers window.
Query the customer.
Open the Account Profile tabbed region.
Enter a Profile Class.
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.
Open the Profile Amounts tabbed region.
In the Curr column, set the currency or currencies that this customer uses.
Additional Information: iReceivables Currency drop-down list shows the currencies defined in AR Customer profile and the currencies in which the customer has made transactions.
Related Topics
Defining Customer Profile Classes, Oracle Receivables Implementation Guide
Assigning Profile Classes to Customers, Accounts, or Addresses, Oracle Receivables Implementation Guide
If using the Pay Invoice function, define at least one receipt class and receipt method for each iReceivables payment instrument:
Credit card payments using Payments
Bank account transfers using Payments
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 for more information.
For bank account transfers and credit card payments, run the Receivables remittance program to capture funds.
For credit card payments, define a receipt class and receipt method to enable credit card payment authorization and capture of funds using a two-step remittance method. In a two-step remittance method, iReceivables only authorizes the credit card charge. The Receivables remittance program has to be run to capture funds.
A user can make a “one-time payment” of open invoices with a credit card. iReceivables processes the transaction using the credit card but does not save the credit card information.
One step credit card payments are setup as Automatic and the profile option OIR: Save Payment Instrument Information is set to No.
Note: If the OIR: Save Payment Instrument Information profile option is set to No, iReceivables can only accept payment by new credit card option. Bank account transfer cannot be used to process payments.
Additional Information: If the OIR: Save Payment Instrument Information profile option is set to Yes, then the option, Save credit card for later use, is shown under the New Credit Card region in Advance Payment page. When this option is selected, the credit card details are saved for future use. This option is selected by default.
The profile option OIR: Verify Credit Card Details controls the Credit Card Security Code and Billing Address options shown in the iReceivables Payment UI. When making a payment, the security code or billing address, or both are passed to the payment gateway based on the profile option.
Important: The fields displayed using this profile option are mandatory for successful payment using credit card.
The following options are available:
Credit Card Address only: The card Billing Address fields are displayed in the iReceivables Payment UI.
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 Payment UI.
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.
Oracle Payments manages external processing of credit card payments and ACH bank account transfers. The banks and currencies supported by Payment are determined by the Payment servlets.
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.
Note: iReceivables does not support cross-currency payments. Though a user can still pay invoices with a credit card or bank account that has a different currency from that of the invoice, the receipt created in iReceivables will have the same currency as the invoice.
To define a receipt class and receipt method for iReceivables:
Select the Receivables Manager responsibility.
Navigate to the Receipt Classes window under Setup.
Enter a Name for this receipt class. For example, enter a name that identifies this receipt class for iReceivables.
Leave the Notes Receivable and Require Confirmation check boxes deselected.
Enter a Creation Method of Automatic to process receipts by credit card or bank account transfer using Payments.
Enter a Remittance Method of Standard, Factoring, or Standard and Factoring, according to business practices, for credit card payments and bank account transfer payments. Receipts are created as Confirmed and require remittance.
Enter Standard, if refunds against credit card payments have to be allowed.
Enter a Clearance Method of Directly, By Automatic Clearing, or By Matching, according to business practices.
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.
Enter a name in the Printed Name field. For example, iReceivables Credit Card.
Leave the Debit Memos Inherit Receipt Numbers check box deselected.
Leave the Receipts Inherit Transaction Numbers check box deselected.
iReceivables uses document sequences to number credit card or bank account transfer receipts.
Enter the number of receipts rule according to the business practices. This field is not used by iReceivables.
Enter receipt maturity date rule according to the business practices. This field is not used by iReceivables.
Enter the automatic print program according to the business practices.
Enter the lead days according to the business practices.
In the Payment Method field, enter:
Credit Card for credit card payments.
Bank Account Transferfor bank account transfer payments.
Enter the range of Effective Dates for this payment method.
Choose the Bank Accounts button to assign a remittance bank to this payment method.
If this payment method is for bank account transfers using Payments, provide a valid bank number for the bank associated with the account being linked to.
Note: Because iReceivables does not support cross-currency payments, ensure that the bank account assigned to the default credit card and bank account transfer payment methods are in the same currency as the customer invoices.
Save the work.
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 for more information.
For bank account transfer, perform this additional step:
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.
When an Invoice is completed in AR, an email notification can be sent to users of Self Service User role. Perform the following steps to enable this subscription:
Login as system administrator and navigate to Workflow Administrator Web Applications responsibility.
Select Business Events and search for oracle.apps.ar.transaction.Invoice.complete.
Click the Subscription link to check the subscriptions for the event
For the ARI_UTILITIES.invoke_invoice_email_notwf function, click the Update link and change Status to Enabled. Click Next and Apply.
Additional Information: This subscription is disabled by default.
Related Topics
Understanding Oracle Payments, Oracle Payments User's Guide
About Remittances, Oracle Receivables User Guide
Integration with Other Oracle E-Business Suite, Oracle Payments Implementation Guide
Receipt Methods, Oracle Receivables Implementation Guide
Oracle Receivables Profile Options, Oracle Receivables Implementation Guide
Assign the iReceivables receipt methods defined in Define Receipt Class and Receipt Method to the Receivables System Options window, Customers - Standard window, Customer Addresses window, and the profile options OIR: Credit Card Payment Method and OIR: Bank Account Payment Method according to business practices. The system searches for the Receipt Method first in the profile options mentioned above, next the bill to sites, then at the account level, and finally the system options.
Use the Receivables System Options window to assign a default iReceivables receipt method for credit card payments and bank account transfers. Use the Customers - Standard window and the Customer Addresses window to assign iReceivables receipt methods to specific customers and specific customer bill-to sites.
Receipt method assignments take precedence in the order:
Profile options mentioned above
Bill-to sites
Account level
Receivables system options
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.
Associated Payment Type is Credit Card.
There is an associated remittance bank account that accepts receipts in the payment currency.
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:
Select the Receivables Manager responsibility select Setup, then System.
Navigate to the Receivables System Options window.
Open the Miscellaneous tabbed region.
Enter an iReceivables credit card payment method in the Credit Card Payment Method field.
Enter an iReceivables bank account transfer payment method in the Bank Account Payment Method field.
Navigate to the Customers - Standard window.
Query or enter the first customer.
Navigate to the Payment Details tabbed region to assign iReceivables receipt methods to this customer. Mark only one receipt method of each type as Primary.
In the Addresses tabbed region, choose the customer address.
Navigate to the Payment Details tabbed region to assign iReceivables receipt methods to this customer bill-to site.
Save the work.
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
To display the Pay button in the Account Details page for external users, you must define a payment method in Receivables System Options. For this, perform steps 1 to 5 from the previous section, To assign iReceivables receipt methods.
Set up document sequences to assign sequence numbers to iReceivables credit card receipts and bank account transfer receipts.
Note: System Administrator responsibility access is required to perform this setup step.
To set up document sequencing for iReceivables receipts:
Select the System Administrator responsibility.
Navigate to the System Profile Values window.
Set the Sequential Numbering profile option to Always Used or Partially Used.
Save the work.
Navigate to the Document Sequences window.
In the Name field, enter a document sequence name that identifies this sequence for iReceivables receipts, such as iReceivables Credit Card Receipts.
In the Application field, enter Oracle Receivables.
In the From and To fields, enter the effective dates for this document sequence.
In the Type field, enter Automatic or Gapless.
Complete the fields for this document sequence.
Save the work.
Navigate to the Sequence Assignments window.
In the Application field, enter Oracle Receivables.
In the Category field, enter the document category created by the corresponding iReceivables payment method defined in Oracle Payments and Supported Currencies.
In the Method field, enter Automatic.
Open the Assignment tabbed region.
Enter the Start and End Dates for this sequence assignment.
In the Sequence field, enter the name of the document sequence defined in step 6.
Save the work.
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
Users can apply service charges to payments that customers make using the Pay Invoice function in iReceivables. iReceivables records a service charge as an adjustment to the invoice.
The setup tasks for applying service charges for a new user to iReceivables are:
Set the Service Charge Enabled and Service Charge Activity ID rules for an operating unit or customer.
Set the Service Charge Enabled rule default value to Yes to enable service charges.
See: Set Up Rules.
The setup tasks for applying service charges are:
Define a Receivables activity and document sequencing for service charges.
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.
Enter the service charge calculation in the ARI_SERVICE_CHARGE_PKG.compute_service_charge function for bank account payments.
To define service charges on invoice payments using iReceivables:
Select the Receivables Manager responsibility.
Navigate to the Receivables Activities window.
Enter a Name and Description for the activity.
Enter Adjustment in the Type field.
Complete the Receivables Activities window according to business requirements.
Save the work.
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.
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).
Select the System Administrator responsibility.
Navigate to the System Profile Values window.
Set the Sequential Numbering profile option to Always Used or Partially Used.
Save the work.
Navigate to the Document Sequences window.
In the Name field, enter a document sequence name that identifies this sequence for iReceivables service charges.
In the Application field, enter Oracle Receivables.
In the From and To fields, enter the effective dates for this document sequence.
In the Type field, enter Automatic or Gapless.
Complete the fields for this document sequence.
Save the work.
Navigate to the Sequence Assignments window.
In the Application field, enter Oracle Receivables.
In the Category field, enter the document category created by the Receivables activity defined above.
In the Method field, enter Automatic.
Open the Assignment tabbed region.
Enter the Start and End Dates for this sequence assignment.
In the Sequence field, enter the name of the document sequence defined in step 14.
Save the work.
Set these profile options for service charges:
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.
Set the OIR: Enable Service Charge profile option to Yes.
Set the ARI_SERVICE_CHARGE_PKG.compute_service_charge function to calculate the appropriate service charge. The default calculation is .05% for bank account payments. For credit cards, different values can be setup. It is 0.05% by default.
The ARI_SERVICE_CHARGE_PKG.compute_service_charge function is defined as:
SELECT ATTRIBUTE1 INTO L_SERVICE_CHRG_PRCNT from ar_lookups where lookup_type = upper(L_LOOKUP_TYPE) AND lookup_code = upper(P_LOOKUP_CODE) AND ENABLED_FLAG='Y' AND sysdate between start_date_active AND nvl(end_date_active,sysdate);
Important: In this function, ATTRIBUTE1 is hardcoded and cannot be changed.
The lookup AR_CREDIT_CARD_SURCHARGE defines the Credit Card Types and the Service Charges for each type. To set this up, perform the following steps:
Enable DFF Common Lookups with the following steps:
Navigate to Application Developer responsibility, and select Flexfield, then Descriptive, then Segments.
Search for Type with value Common Lookups.
Deselect Freeze Flexfield Definition option.
Select the Global Data Elements row and click Segments.
Enter the following values:
Name: Credit Card Surcharge Window Prompt: Credit Card Surcharge Column: Value for credit card surcharge
Save and compile.
Select the Freeze Flexfield Definition option.
Navigate to Receivables Manager responsibility. Select Setup, then System. Under QuickCodes, select Receivables.
Search for the lookup AR_CREDIT_CARD_SURCHARGE. Under DFF , enter the Credit Card Surcharge value for each credit card type. This value gets reflected while calculating the Service Charge when a Credit Card Type is selected during payment.
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
Users can configure iReceivables to consider the discount grace days for a customer or customer site when calculating and displaying discount amounts for transactions.
The setup tasks for setting the discount grace days for users new to iReceivables are:
Set the Discount Grace Days rule for an operating unit and/or customer
See: Set Up Rules.
The setup tasks for setting the discount grace days are:
Use the OIR: Enable Discount Grace Days profile option to enable or disable the consideration of the grace period. When the grace period is enabled:
Last Date column in the Discount Alerts table on the Home Page includes the grace days allowed for the discount.
Discount amount displayed on the Payment page considers the grace days allowed for the discount.
All payments made through iReceivables consider the grace days when calculating payment on transactions.
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.
Note: When the OIR: Enable Discount Grace Days profile option is set to No, iReceivables does not consider grace days when calculating discounts, even if grace days are defined for the customer or customer site.
Related Topics
Oracle Receivables Profile Options, Oracle Receivables Implementation Guide
Use the OIR: Bank Directory Source profile option to help manage bank account transfer payments for iReceivables. The source for the bank directory can be the CE_BANK_BRANCHES_V view or a local table AR_BANK_DIRECTORY, containing the bank branch information, downloaded from the Federal Reserve Financial Services web site.
Note: If OIR: Save Payment Instrument Information profile option is set to No, iReceivables can only accept payment by credit card using a one-step remittance method. The ACH bank account transfer to process payments cannot be used. See: Define Receipt Class and Payment Method for more information.
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 routing number is checked against the local table, AR_BANK_DIRECTORY, containing the bank branch information. If this routing number is available in the local table, iReceivables still considers the information as valid and proceeds with the payment. Along with the payment, iReceivables uploads the routing number, bank and branch information into the system. To upload the ACH bank branch information to a local table, see: Download and Upload the E-Payment ACH Directory to a Local Table.
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.
If the OIR: Bank Directory profile option is set to Local, a copy of the E-Payment ACH directory must be present in the local table, AR_BANK_DIRECTORY. Retrieving the directory involves two steps:
Download the E-Payment ACH directory from the Federal Reserve Financial Services web site.
Use SQL*Loader to upload the directory to the AR_BANK_DIRECTORY table.
Note: System Administrator responsibility access is required to perform this task.
To upload the E-Payment ACH directory to the local table:
Open the web browser.
Navigate to the Federal Reserve Financial Services web site.
Navigate to the E-Payments Routing Directory page and follow the instructions given to download the directories.
Save the file in a local file that the Receivables system can access.
In Oracle E-Business Suite, select the System Administrator responsibility.
Navigate to the Request Group window.
In the Group field, query Receivables All.
Add Import Bank Directory to the Requests.
Switch the responsibility from System Administrator to Receivables Manager.
Navigate to the Submit Request window.
In the Name field, choose Import Bank Directory from the list of values.
In the Parameters window, enter in the Data File field the path to the local file saved in step 5.
Press the OK button.
Press the Schedule button.
In the Schedule window, choose Once.
Press the OK button.
Press the Submit button to submit the request.
Note: ORACLE PROVIDES THE E-PAYMENT ROUTING DIRECTORY ON AN “AS IS” BASIS. ORACLE EXPRESSLY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. ORACLE MAKES NO WARRANTY THAT: (i) THE E-PAYMENT ROUTING DIRECTORY WILL BE AVAILABLE UNINTERRUPTED, ON A TIMELY BASIS, SECURE, OR ERROR-FREE, AND (ii) THE RESULTS THAT MAY BE OBTAINED FROM THE USE OF THE SERVICE WILL BE ACCURATE OR RELIABLE. IN NO EVENT SHALL ORACLE BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR DATA USE, INCURRED BY YOU OR ANY THIRD PARTY IN CONNECTION WITH THE E-PAYMENT ROUTING DIRECTORY, WHETHER IN AN ACTION IN CONTRACT OR TORT, EVEN IF ORACLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ORACLE'S ENTIRE LIABILITY FOR DAMAGES IN RESPECT OF THE E-PAYMENT ROUTING DIRECTORY SHALL IN NO EVENT EXCEED TEN THOUSAND DOLLARS (U.S. $10,000).
Related Topics
Oracle Receivables Profile Options, Oracle Receivables Implementation Guide
The concurrent program Import AR_BANK_DIRECTORY Table data to HZ_PARTIES imports AR_BANK_DIRECTORY table data to TCA tables like HZ_PARTIES.
This CP takes one input parameter, Import New Banks Information Only. If set as N, then the CP imports all the new bank information from AR_BANK_DIRECTORY table to TCA tables and also updates the existing information in the TCA Tables.
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).
Use function security to limit access to iReceivables functionality for selected users. Define a new responsibility based upon iReceivables 2.0 Internal or iReceivables Account Management with the limited access that is desired and assign this new responsibility to the internal users or to external users.
Use function security in these situations:
Remove the Pay or Dispute function. By default iReceivables users have access to both the Pay Invoice function and Dispute Invoice function. The Pay Invoice function lets a user make online payments. The Dispute Invoice function allows a user to dispute all or part of an invoice and submit a credit memo request.
To define function security for an iReceivables user:
Select the System Administrator responsibility.
Select Security, then Responsibility. Click Define. The Responsibilities window opens.
In the Responsibility Name field, enter a new responsibility name.
In the Application field, enter Oracle Receivables.
In the Responsibility Key field, enter the new responsibility name defined above.
In the Available From region, choose the Oracle Self Service Web Applications radio button.
In the Data Group Name field, enter Standard.
In the Data Group Application field, enter Oracle Receivables.
In the Menu field, choose iReceivables 2.0 Internal from the list of values for internal users or iReceivables Account Management for external users.
Open the Menu Exclusions tabbed region.
In the Type field, enter Function.
In the Name fields, enter:
Pay Invoices to exclude the Pay Invoice function.
ARW_BTN_DISPUTE to exclude the Dispute Invoice function.
Save the work.
Under System Administrator, select Security, then Users. Select Define. The Users window opens.
Query or enter the first user.
Open the Responsibilities tabbed region.
In the Responsibility field, enter the new responsibility defined above.
In the From and To fields, enter the effective dates for this user.
Save the work.
Repeat steps 15 to 19 for each user to be assigned this responsibility.
Related Topics
Responsibilities Window, Oracle E-Business Suite Security Guide
Use the Setup Checklist page to set up profile options, rules and system parameters for different functions of iReceivables.
User must have access to the iReceivables Setup responsibility to perform this setup step.
Important: In iReceivables Release 12, the rules set precedence over profile options. First the rules are checked for values and then the profile options are checked.
The Setup Checklist page gives access to the following setups:
Profiles: Profile options can be set or updated easily from this page.
Registration History: Self Registration details can be viewed and modified from this page.
Rules: Rules offer a high degree of flexibility in customizing the application behavior similar to e-mail rules. Rules can be set up and updated from this page.
System Parameters: Various system options can be set from this page.
To set up profile options:
Click Go To Task to view profiles.
Select the profile option and click Go to display its properties.
Click Update to change the profile option details.
To set up rules:
Click Go To Task from the setup checklist page to view rules.
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.
Site Verification Question rule, which is used as the verification question shown to the user in Verify Access page during self registration.
Service Charge Enabled rule, which is used to enable the iReceivables Service Charge feature.
Service Charge Activity ID rule, which is used to set the Receivables Activity identifier for the service charge transaction created while paying through iReceivables.
Multi Print Limit rule, which is used to set the maximum number of invoices for immediate printing from iReceivables.
Last Used Payment Instrument rule, which is used to configure iReceivables to remember previously used payment instruments.
Future Dated Payments rule, which is used to set the maximum limit (in days) for future dated ACH payments through iReceivables.
Discount Grace Days rule, which is used to set the grace days to determine if discount are eligible for payments through iReceivables.
Contact Information rule, which is used to configure contact information for iReceivables pages.
Aging Buckets rule, which is used to configure display of aging buckets on the home page.
To set up system parameters:
Click Go To Task to view system parameters.
Select the organization for which the system parameter has to be set.
Set the following parameters:
Credit Card Receipt Method
Bank Account Payment Method
Service Charge Activity
Click Update to change the system parameters details.
Use the Setup Checklist page to view the Payment Audit History and Registration History details of users.
This feature allows to track all payments received and processed through iReceivables by internal and external users. You can review successful and failed payment attempts.
To view payment audit history:
Using iReceivables Setup responsibility, navigate to the Setup Checklist page.
Click Go To Task on the Payment Audit History row to view the Payment Audit History Details page.
Enter the required fields and click Go.
Additional Information: With blind search, the Date filter is defaulted and the search returns all registration performed in the last seven days.
The following details are available:
Payment Status (Successful/Failed).
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.
Customer Name and Customer Number.
List of Invoices and Debit Memos paid. You can also view the Deposits paid.
Registration history data can be managed through this page. Customers can also review Pending and Previously completed registration requests. The data is stored in the ARI_REG_VERIFICATIONS table.
To view and update registration history:
Using iReceivables Setup responsibility, navigate to the Setup Checklist page.
Click Go To Task on the Registration History row to view the Registration History Details page.
Enter the required fields and click Go.
Additional Information: With blind search, the Date filter is defaulted and the search returns all registration performed in the last seven days.
Click Update to update the registration.
Registration Type: Can be used to distinguish between new user and existing user.
Status: Gives the status of registration.
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.
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.
Use the Lookups window to review and update Receivables lookup types for use with iReceivables. The lookup types are:
CREDIT_MEMO_REASON
ARI_CUSTOMER_SEARCH_TYPE
ARI_INVOICE_SECTION
AR_IREC_CREDIT_CARD_TYPES
ARI_ACCOUNT_DETAILS_TYPE
ARI_ACCT_STATUS
ARI_CUSTOMER_HEADER_LABEL
For the lookup types CREDIT_MEMO_REASON and ARI_INVOICE_SECTION, review and update both seeded and user-defined lookup codes. For the lookup type AR_IREC_CREDIT_CARD_TYPES, update the seeded credit card types to be accepted for iReceivables payments.
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 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 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
Customer Name: Displays the Customer Name
Customer Number: Displays the Customer Number
Customer Site Name: Displays the Location of the Site
Customer Site User ID - Displays the Site User Id
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 lookup. If order of options has to be changed, for example, Customer Number before Customer name, then set the Tag lower for Customer Number than Customer Name.
Select the Receivables Manager responsibility.
Navigate to the Oracle Receivables Lookups window.
In the Type field, query the lookup type.
In the User Name field, enter the user name for the applicable lookup codes.
In the Application field, enter Oracle Receivables. The system displays the lookup codes.
To disable a lookup code, enter a date in the Effective Dates To field or deselect the Enabled box.
For ARI_CUSTOMER_SEARCH_TYPE and CREDIT_MEMO_REASON, enter Y in the Tag field to make a code available to external users or N to make the code available to internal users only. Replace any null values in the Tag field with Y or N.
Enter any new lookup codes for ARI_CUSTOMER_SEARCH_TYPE and CREDIT_MEMO_REASON.
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
Users can set the aging information for iReceivables to view transactions across various age buckets. Customers can view aging buckets for their accounts in the Account Summary page. By clicking on an aging bucket balance number, the user can drill down to the Account Details page to review all the debit items in the aging bucket, including invoices, chargebacks, guarantees, deposits, debit memos, and credit memos. The Search list for transaction status in the Account Details page includes each of the active aging buckets as search criteria.
The setup tasks for applying aging buckets if user is new to iReceivables are:
Set the Aging Bucket rule for an operating unit and/or customer
See: Set Up Rules.
The setup tasks for applying aging buckets are:
Set the OIR: Aging Buckets profile option to display aging information for iReceivables users.
Users can set this profile option at the site, responsibility, and user levels, according to the business practice. Users can display the standard aging buckets that Oracle Receivables provides, or the custom buckets that is defined in the Receivables Aging Buckets window. If all fields are left blank, then iReceivables does not display aging buckets.
To set the aging buckets profile option:
Select the System Administrator responsibility.
Navigate to the System Profile Values window.
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
iReceivables integrates with Bill Presentment Architecture (BPA) to customize the content and format of billing data that customers view online. BPA lets users retrieve billing data from multiple data sources and template-based configuration of online bills, including content selection, layout design, drill-down and grouping capability, and billing template assignment. With BPA, the information on the bill is not limited to information contained within Oracle Receivables. By separating bill presentment from transaction accounting, Oracle BPA lets users configure and print invoices according to their company needs.
Perform the following setup steps to display and print invoices using the Bill Presentment Architecture in Oracle iReceivables:
OIR: Bill Presentment Architecture Enabled profile option - Set the OIR: Bill Presentment Architecture Enabled profile option to display and print invoices in BPA format. This profile option can be set at the site, application, responsibility, and user levels, according to business practices.
If all fields are left blank, then iReceivables displays invoices in the standard iReceivables format.
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.
ARI_PRINT_PROGRAM_NAME - BPA Print concurrent program.
Note: System Administrator responsibility access is required to perform this setup step.
For steps on setting up profile options, see: Set Up Profiles, Registration History, Rules, and System Parameters.
Related Topics
Overview of Bill Presentment Architecture, Oracle Bill Presentment Architecture User's Guide.
Print Management, Oracle Bill Presentment Architecture User's Guide.
The profile option OIR: Bill Presentment Architecture Enabled can be used to select the print program used to print invoices. If the profile value is set to No, then iReceivables uses the AR Print program, Invoice Print Selected Invoices, to print the invoices. If the value is set to Yes or not set with any value, then iReceivables uses the BPA Print Program to print the invoices.
The display of account information can be modified in the iReceivables Account Details and Transaction pages (including Invoice, Debit Memo, Deposit, and Payments) using Oracle E-Business Suite Personalization Framework. See: Oracle Application Framework Personalization Guide. By modifying the display of account information in the Account Details and Transactions pages, the regions and fields that external customers and one-time users have access to can be controlled.
In addition to displaying the customer's latest account activity, the Account Details page can also display transaction descriptive flexfields and the context field values defined for them, if these flexfields are enabled in the Receivables Transactions window. The flexfields are the Invoice Transaction flexfield and the Transaction Information flexfield. iReceivables stores flexfield information in the ARI_ACCOUNT_INVOICE table. Use the Descriptive Flexfield Segments window to enter context field values for the transaction flexfields.
The Invoice, Debit Memo, and Deposit pages can also display invoice line-level descriptive flexfields and the context field values defined for them, if these flexfields are enabled in the Receivables Transactions window. The flexfields are the Invoice Line Information flexfield and the Line Transaction flexfield. iReceivables stores flexfield information in the ARI_INVOICE_LINES table. Use the Descriptive Flexfield Segments window to enter context field values for the invoice line-level flexfields.
The Payments page can also display the Receipt Information flexfield and the context field values defined for the flexfield in the Payment Row region. iReceivables can also display the Transaction Information and Invoice Transaction flexfields in the Payment Activities tables for the Account Details, Invoice, and Payment pages.
Administrator-level personalization changes can be made while logged in to iReceivables. Administrator-Level (Admin-level) personalizations apply to Function, Localization, Site, Organization, and Responsibility levels.
Some restrictions may apply to personalization changes due to the controller class. A controller class is the code that controls how a page is rendered and how events are handled on the page. The restrictions are:
Users cannot create new controller classes or modify existing controller classes. Any modifications to controller classes are not supported.
In some cases, the controller class for a given page may override the personalization settings.
To make Admin-level personalization changes to the Account Details page:
Set the Personalize Self-Service Defn profile option to Yes.
Log in to iReceivables and navigate to the Account Details page for the customer.
Click the available personalization link. These personalization links vary according to the search, but always appear in the Search region of the Account Details page, after the search results table.
To make Admin-level personalization changes to the Invoice page:
Set the Personalize Self-Service Defn profile option to Yes.
Log in to iReceivables and navigate to the Invoice page for the customer.
To display transaction header-level flexfields on the Invoice page, click the personalization link Personalize Invoice Terms Table. To display transaction line-level flexfields in the Invoice page, click the Personalize Invoice Lines Table personalization link.
To make Admin-level personalization changes to the Payments page:
Set the Personalize Self-Service Defn profile option to Yes.
Log in to iReceivables and navigate to the Payments page for the customer.
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 hooks can be enabled for Payment, Dispute, and Print options from the Account Details page and the Transaction details page. If the user wants custom conditions to be passed before making payments, dispute, or print, these custom procedures can be set up.
The profile options used are OIR: Custom Validate Payment, OIR: Custom Validate Dispute, and OIR: Custom Validate Print. Set the Custom PackageName.Procedure name (which contains the business logic whether to allow Payment, Dispute, or Print) as the profile value for the above profiles.
If the custom procedures are in the package ARI_DEF_CUSTOM_HOOKS_PVT and the procedures for validating Payment is VALIDATE_PAYMENT, Dispute is VALIDATE_DISPUTE and Print is VALIDATE_PRINT, then set the values of the profiles as follows at the appropriate level:
OIR: Custom Validate Payment: ARI_DEF_CUSTOM_HOOKS_PVT.VALIDATE_PAYMENT
OIR: Custom Validate Payment: ARI_DEF_CUSTOM_HOOKS_PVT.VALIDATE_DISPUTE
OIR: Custom Validate Print: ARI_DEF_CUSTOM_HOOKS_PVT. VALIDATE_PRINT
The profile values can be set at either Site Level/Application Level/Responsibility Level/User Level. If they are not set, then by default the validations are returned as Success. For information on how to set up profile options, see: Set Up Profiles, Registration History, Rules, and System Parameters.
Important: The seeded package ARI_DEF_HOOKS_PVT returns validations as success. This package can be used as a reference. Do not modify this package. Define the custom package as required.
Custom procedures should follow their pre-defined signatures and should have six parameters. These parameter values are passed from the iReceivables application to the custom procedures.
Additional Information: The signature is the same for payments, dispute and print, except for the procedure name.
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.
Find ways to integrate iReceivables into your business processes. Some examples of integrating iReceivables into your business include:
Make sure your printed Collections and Receivables documents reference the URL that customers use to access your iReceivables web site.
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.