Define iReceivables Internal Users

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.

Define iReceivables External Users and Customer Access

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, or 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.

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, you then use the Users window to assign the external users the responsibility iReceivables Account Management 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.

Note: You cannot assign an external user to a customer site that belongs to a different organization ID.

Customer Access and Indexing the Customer Database

The Customer text data creation and indexing concurrent program indexes the customer information in your database. The program provides the parameter Build Compact Index? the first time that you run the program to perform either full indexing or compact indexing. The compact indexing option omits customer contact information from the build.

Because the customer contact name is one of the search criteria iReceivables internal users have available to search for customers, you must ensure that you build your customer index with the Build Compact Index? parameter set to No. See: Index the Customer Database for more information.

Defining iReceivables External Users

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: Set Up for Self Registration.

To define an iReceivables external user for Business-to-Business Setup, with access to one site only or to multiple customer sites for a single customer:

Select the Receivables Manager responsibility.

Navigate to the Customers - Standard window.

Query or enter the first customer that you want.

Navigate to the Addresses tabbed region and choose the customer address that you want.

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 your work.

To assign this user to a second site of the same customer, first repeat steps 4 and 5.

In the Number field, choose the external user name that you entered in step 6 from the list of values.

In the Description field, enter the role Self Service User.

Save your work.

To assign this user to additional sites of the same customer, repeat steps 9 to 12.

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 that you defined in step 6 from the list of values.

If you are 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-Business Setup, with access to multiple customer sites for multiple customers:

Select the Receivables Manager responsibility.

Navigate to the Customers - Standard window.

Query or enter the first customer that you want 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 your work.

Query the next customer that you want in the Customer Name or Number field.

Open the Contacts: Roles tabbed region.

In the Last field, choose the external user name that you entered in step 5 from the list of values.

In the Description field, enter the role Self Service User.

Repeat steps 8 to 11 for all customers that you want to assign to this external user.

Save your 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 that you defined in step 6 from the list of values.

If you are 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 that you want.

Assign the user the Customer Type Person and enter the necessary Person party details.

Save your 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 that you defined in step 4 from the list of values.

If you are 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.

Index the Customer Database

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 the Customer text data creation and indexing concurrent program, the program builds the indexes in your database. Therefore, depending on the volume of your customer data, the first run may take a fairly long time to complete.

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 Currencies for Customers and Customer Bill To Sites

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. You can specify these profiles at the customer level and customer site level. If a currency code does not exist in either of these two profiles at the customer or any customer site level, then iReceivables cannot display the customer's transactions in that currency.

Use the Customers window to define credit profiles and profile amounts for your 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 that you want.

Open the Profile: Transaction 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.

Define Receipt Class and Payment Method

If you are using the Pay Invoice function, define at least one receipt class and payment method for each iReceivables payment instrument that you intend to use:

Bank account transfers using Receivables direct debit.

Credit card payments using Payments.

ACH bank account transfers using Payments.

If you use Receivables direct debit, you can process bank account transfer payments globally. If you use payment methods via Payments, then payment processing is restricted according to the Payments servlets.

A user can pay all open invoices in one payment transaction. You can also let the user 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 payment method specified at the customer level. For payments of multiple invoices across multiple bill-to sites, you must provide specific settings to use the payment methods that you assign to customers and customer sites. See: Assign iReceivables Payment Methods for more information.

If you already use Oracle Receivables direct debit to mark invoices for automatic direct debit processing, you can let your customers pay their invoices by direct debit. Create a payment method for standard Receivables direct debit with a manual creation method. If you set this payment method as the default bank account transfer payment method, then Receivables can process your customer bank account transfer payments via direct debit.

For bank account transfers, both direct debit and ACH transfer, you must run the Receivables remittance program to capture funds.

For credit card payments, define a receipt class and payment method to enable credit card payment authorization and capture of funds using either a one-step remittance method or a two-step remittance method. In a one-step remittance method, iReceivables authorizes and captures the funds in the same process. In a two-step remittance method, iReceivables only authorizes the credit card charge. You must run the Receivables remittance program to capture funds.

Credit Card One-Time Payment

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.

If you intend to use the credit card one-time payment feature, you must:

Define a receipt class and payment method that uses a one-step remittance method.

Note: If you set the OIR: Save Payment Instrument Information profile option to No, iReceivables can only accept payment by credit card using a one-step remittance method. You cannot use the ACH bank account transfer to process payments.

Additional Credit Card Verification

Use the Payments Setup Administrator responsibility under Oracle Payments to set up the credit card verification details. See: Setting Up System Security Options, Oracle Payments Implementation Guide.

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 and Supported Currencies

Note: Please consult Oracle Payment User's Guide for the current list of Payments servlets and the currencies they support.

For credit card processing, you can use the Payments integration with Verisign, which supports transactions in US dollars (USD) and Canadian dollars (CAD) only. You 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, you can use the Payments integration with Chase Merchant Services, which supports transactions in US dollars (USD) only.

If your company uses the Verisign payment system, you 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 your company uses a payment system other than Verisign, you can set up a single payment method for multiple bank accounts with multiple currencies, if your 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 payment method for iReceivables:

Select the Receivables Manager responsibility.

Navigate to the Receipt Classes window.

Enter a Name for this receipt class. You may want to enter a name that identifies this receipt class for iReceivables.

Leave the Notes Receivable and Require Confirmation boxes unchecked.

Enter a Creation Method of:

Manual to process receipts using the standard Receivables direct debit.

No Remittance for one-step credit card payments, including one-time payments. Receipts are created as Cleared and do not require remittance.

Standard, Factoring, or Standard and Factoring, according to your business practice, for two-step credit card payments and bank account transfer payments. Receipts are created as Confirmed and require remittance.

Enter Standard, if you plan to allow refunds against credit card payments.

Enter a Clearance Method of Directly, By Automatic Clearing, or By Matching, according to your business practice.

Enter a Payment Method Name. You may want to enter a name that identifies the type of payment, such as iReceivables direct debit, iReceivables 2-step credit card, or iReceivables ACH.

Enter a name in the Printed Name field. For example, iReceivables Credit Card.

Leave the Debit Memos Inherit Receipt Numbers box unchecked.

If you are defining a direct debit payment method, go to step 18.

Enter the number of receipts rule according to your business practice. This field is not used by iReceivables.

Enter receipt maturity date rule according to your business practice. This field is not used by iReceivables.

If you entered a payment type of Credit Card, enter your Merchant ID number. This number is usually provided by your bank or credit card issuer. Your credit card vendor requires this number to process credit card transactions.

The Merchant ID that you provide here is the same as the Payee Identifier that you entered when you created the payee in the Payments Administration user interface. You can view the Payee Identifier in the Payments Payee Details window.

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 ACH bank account transfers using Payments, you must provide a valid bank number for the bank associated with the account that you are linking to.

Note: Because iReceivables does not support cross-currency payments, you must ensure that the bank account assigned to your default credit card and bank account transfer payment methods are in the same currency as your customer invoices.

Save your work.

Assign the iReceivables payment methods that you defined to the Receivables System Options window, Customers - Standard window, and Customer Addresses window according to your business practice. See: Assign iReceivables Payment Methods for more information.

For ACH 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 your business practices. Setting a maximum future payment date, for example, prevents users from entering exaggerated future payment dates.

By default, iReceivables reads the profile option setting for all customers and customer sites. If necessary, modify the ARI_CONFIG. get_max_future_payment_date function according to your business requirements to set this function at the customer level and customer site ID level.

Assign iReceivables Payment Methods

Assign the iReceivables payment methods that you defined in Oracle Payments and Supported Currencies to the Receivables System Options window, Customers - Standard window, and Customer Addresses window according to your business practice.

Use the Receivables System Options window to assign a default iReceivables payment method for credit card payments and bank account transfers. Use the Customers - Standard window and the Customer Addresses window to assign iReceivables payment methods to specific customers and specific customer bill-to sites.

Payment method assignments take precedence in the order:

Customer bill-to site

Customer

Receivables System Options

Mark one payment method of each type as Primary at the customer and customer site level. If at the customer site level there are two or more payment methods of the same type, the payment method marked as primary is taken as the payment method for transactions billed to this site. If no payment 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 payment methods defined at the customer and customer site level if the payment 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 payment 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.

Define Function Security

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 you want and assign this new responsibility to your internal users or to external customers or customer sites.

You can 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.

Navigate to the Responsibilities window.

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 that you 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 your work.

Navigate to the Users window.

Query or enter the first user that you want.

Open the Responsibilities tabbed region.

In the Responsibility field, enter the new responsibility that you defined above.

In the From and To fields, enter the effective dates for this user.

Save your work.

Repeat steps 15 to 19 for each user that you want to assign this responsibility.

Set Up Rules, Profile Options, and System Parameters

Use the setup checklist page to set up profile options, rules and system parameters for different functions of iReceivables.

You 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:

Rules: Rules offer a high degree of flexibility in customizing the application behavior similar to e-mail rules. You can set the rules from this page.

Profiles: Profile options can be set or updated easily from this page.

System Parameters: Various system options can be set from this page.

Set Up Rules

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, you can 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, you can set the rule 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 Info rule, which is used to configure contact information for iReceivables pages.

Aging Buckets rule, which is used to configure display of aging buckets on home page.

Set Up Profile Options

To set up profile options:

Click Go To Task to view profiles.

The following profile options can be set:

OIR: Active Contacts Display Limits

OIR: Aging Buckets

OIR: Multi Print Limit

OIR: Enable Discount Grace Days

OIR: Enable Service Charge

OIR: Maximum Future Payment Days Allowed

OIR: Payment Approver Status

OIR: Save Payment Instrument Information

OIR: Service Charge Activity ID

Select the profile option and click Go to display its properties.

Click Update to change the profile option details.

Set Up System Parameters

To set up system parameters:

Click Go To Task to view system parameters.

Select the organization for which you want to set the system parameter.

You can set for the following parameters:

Credit Card Receipt Method

Bank Account Payment Method

Service Charge Activity

Click Update to change the system parameters details.

Set Up for Self Registration

The iReceivables Self Registration feature lets your customers register for iReceivables Account Management (application) access to their customer account data. To register, a customer clicks a link that you create on your portal page to access the Self Registration pages. On the Self Registration pages, an external user is given three attempts to answer a challenge/response question correctly (this is a transactional question pertaining to the applicable customer account). If all three attempts are unsuccessful, the user is only able to re-register according to the Self Registration profile option settings that you specify.

If registration is successful, iReceivables creates a user account, assigns the user the customer contact role Self Service User, and forwards the customer 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.

A user can register for additional accounts using either the:

Register link that you create on the main portal page

or

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 you have defined your own responsibilities 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 your custom responsibilities. Users can add or remove themselves from the responsibility using the Request Additional Customer Access or Remove Access options from the Manage Customer Account Access page.

Prerequisites

Before you can complete set up of iReceivables for Self Registration, you must:

Associate the MO: Security profile option you have already created to the Guest User.

In the Security profile option, enter all the organizations that contain customer account data for which your 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:

Set up iReceivables Self Registration for external users.

Set the Local Login Mask Site Level to 48 at site level in the System Profiles Values window.

Set Up for Anonymous User Login

The iReceivables Anonymous User Login feature lets your customers access customer account data without owning or registering for a user account. You can use this feature, for example, for bill collections to let users access account data to view and pay open invoices.

External users access their account data using the Anonymous Login page. The Anonymous Login page prompts the user for an account number, and then redirects to the iReceivables page of your choice. The available pages for redirect are the Customer Search page, the Account Home page, the Account Details page, or an Anonymous Login Error page.

The Anonymous Login feature is contained in the jsp file AnonymousLogin.jsp. Use this jsp file to validate the guest user, create a session and redirect to the iReceivables page that you want, and customize the number of parameters passed to the API. By default, the information entered by the user in the Account Number field on the Anonymous Login page is passed to the API.

Modify the file AnonymousLogin.jsp, located in the OA_HTML directory, if you have migrated from Release 11i.

Caution: The iReceivables 2.0 Anonymous Internal responsibility by default has access to all the application features available to the registered user. Please carefully enable or disable the features accessible to the anonymous user.

To successfully access the anonymous login pages, modify these .htm files. If you want to support multiple languages, you can 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]/

where: [country code] - Uppercase ISO 3166 2-letter code

In Oracle E-Business Suite, select the System Administrator responsibility.

If necessary, use function security to limit user access to functionality in the iReceivables Account Management responsibility. See: Define Function Security for more information.

Assign the iReceivables anonymous login responsibility that you defined in step 3 to the pre-seeded guest user account specified by the Guest User Password profile option.

Navigate to the System Profile Values window.

In the Profile field, enter Guest User Password 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 Guest User Password account.

Navigate to the Responsibilities tabbed region.

Add the iReceivables anonymous loginresponsibility that you defined above.

Modify the SQL code in AnonymousLogin.jsp.

Add any parameters that you need as name-value pairs to the HashMap structure hParams, according to this example:

HashMap hParams = new HashMap();
hParams.put("Ircustomerid",sCustId);

In this example, 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.

This table outlines the page-level semantics, and mandatory and optional parameters, for each iReceivables page.

Values for <type> are from the lookup ARI_ACCOUNT_DETAILS_TYPE. Values for <status> are from the lookup ARI_ACCT_STATUS. If you are using aging buckets, then you can also use aging status codes. The format for the aging status code is: OIR_AGING_ +<days from> + <days to>

Note: You must have a corresponding aging bucket defined for <days from> and<days to>.

Set Up for Applying On-Account Credits

Set up iReceivables to let your customers apply their on-account credits to open debit transactions, including invoices, debit memos, and deposits. Customers can:

Select one or more on-account credit memos or unapplied payments and apply them to multiple invoices and other debit transactions.

Shortpay one or more invoices and other debit transactions and apply on-account credit memos, on-account payments, or unapplied payment to the remaining balance.

Along with the profile option settings, you can set the service charge profile at the customer and customer site level by configuring the appropriate parameters in the ARI_CONFIG package.

Enter the service charge calculation in the ARI_SERVICE_CHARGE_PKG.compute_service_charge function.

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 your business requirements.

Save your work.

Remain in the Receivables Activities window with the new activity that you just created. From the Help menu, choose Diagnostics > Examine.

The Examine window appears.

In the Field field, enter RECEIVABLES_TRX_ID. Make note of the value in the Value field. You will enter this value 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 your 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 your 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 that you 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 that you defined in step 14.

Save your 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 you defined for service charges.

Set the OIR: Enable Service Charge profile option to Yes.

By default, iReceivables reads the profile option settings for all customers and customer sites. If necessary, modify the ARI_CONFIG.get_service_charge_activity_id function and ARI_CONFIG.is_service_charge_enabled function according to your business requirements to set these functions at the customer level and customer site ID level.

Set the ARI_SERVICE_CHARGE_PKG.compute_service_charge function to calculate the appropriate service charge. The default calculation is .05% on every transaction in the payment list.

Setup Tasks Using Profile Options

The setup tasks for setting the discount grace days for iReceivables Release 11i and earlier releases, 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 that you want.

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.

Review and Update Receivables Lookups

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

For the lookup types CREDIT_MEMO_REASON and ARI_INVOICE_SECTION, review and update both your seeded and user-defined lookup codes. For the lookup type AR_IREC_CREDIT_CARD_TYPES, update the seeded credit card types that you plan to accept for iReceivables payments.

Note: You cannot modify the seeded lookups for the lookup types CREDIT_MEMO_REASON and AR_IREC_CREDIT_CARD_TYPES. You 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 you want to appear on the Search By poplist on the Customer Search page. If you plan to extend the customer search, define lookup codes for your new customer search attributes. The custom transaction search attributes that you define 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 you want to appear on the Status and Transaction Type poplists on the Account Details page. If you plan to extend the transaction search, define lookup codes for your new transaction search attributes. The custom transaction search attributes that you define are queried by the procedure search_custom_trx() in the file ARICNFGB.pls. See: Extending the iReceivables Search for more information.

To update Receivables lookups for use with iReceivables:

Select the Receivables Manager responsibility.

Navigate to the Oracle Receivables Lookups window.

In the Type field, query the lookup type that you want.

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 uncheck 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 that you want.

Related Topics

Lookup Types, Oracle E-Business Suite Developer's Guide

Defining Receivables Lookups, Oracle Receivables Implementation Guide

Set the Aging Information

You can set the aging information for iReceivables users to view their transactions across various age buckets. Your 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, and debit memos. The Search list for transaction status in the Account Details page includes each of the active aging buckets as search criteria.

Setup Tasks Using Rules

The setup tasks for applying service charges if you are new to iReceivables are:

Setup Tasks Using Profile Options

You can set this profile option at the site, responsibility, and user levels, according to your business practice. You can display the standard aging buckets that Oracle Receivables provides, or you can display the custom buckets that you define in the Receivables Aging Buckets window. If you leave all fields 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 aging buckets that you want.

Set the Profile Option for ACH Bank Account Transfer Payments

Use the OIR: Bank Directory Source profile option to help manage bank account transfer payments for iReceivables via Payments and the ACH network. Setting this profile option lets iReceivables derive the name of the bank or financial institution from the routing number that the customer enters to pay an invoice using an ACH bank account transfer. You use the AR: Bank Directory Source profile option to acquire access to the E-Payment routing directory on the Federal Reserve Financial Services web site (http://www.fedwiredirectory.frb.org). When a customer pays an invoice by ACH bank account transfer with a routing number that is not assigned to a bank in the AP_BANK_BRANCHES table, the routing number is checked against the E-Payment routing directory. iReceivables derives the bank or financial institution name from the E-Payment routing directory using the routing number that the customer entered.

Note: If you set the OIR: Save Payment Instrument Information profile option to No, iReceivables can only accept payment by credit card using a one-step remittance method. You cannot use the ACH bank account transfer to process payments. See: Define Receipt Class and Payment Method for more information.

Set the OIR: Bank Directory Source profile option to Local to access the E-Payment routing directory from a local file that you download from the Federal Reserve Financial Services web site. When the customer enters a routing number that is not assigned to a bank in the AP_BANK_BRANCHES table, iReceivables attempts to derive the bank name using the local table. If the bank name for this routing number is not in the table, iReceivables uses the routing number as the bank name.

Save the file in a local file that your 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 that you saved in step 4.

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: You can access the Federal Reserve System's terms of use, which apply to the E-Payment Routing Directory, at http://www.frbservices.org/index.cfm.

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

Modify the Display of Account Information

You can modify the display of account information 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, you can control the regions and fields that your external customers and one-time users have access to.

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 that you define for them, if you enable these flexfields 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 that you define for them, if you enable these flexfields 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 that you define 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.

You make Administrator-level personalization changes while logged in to iReceivables. Administrator-Level (Admin-level) personalizations apply to Function, Localization, Site, Organization, and Responsibility levels.

Controller Class Restrictions

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:

You 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 your 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 that you want.

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 that you want.