This appendix lists the profile options used for Oracle Advanced Collections.
This appendix covers the following topics:
During implementation, administrators use the collections checklist to set a value for most of the Oracle Advanced Collections system profile options. These profile options are set at the site level and specify how Advanced Collections controls access to and processes data. Other profile options can be set by individual users. These profiles can be changed later in the Setup module, if needed.
See: Setting User Profile Options, Oracle Applications System Administrator's Guide - Maintenance
See: Category and Profile Option Descriptions
Advanced Collections Categories
Advanced Collections Profile Options
This section describes profile options by category.
The tables in this section provide profile option information as follows:
The Default column displays the default profile option value in italics or No Default if none exists.
The User Access column indicates whether you can view or update the profile option.
The User, Responsibility, Application, and Site columns indicate at which levels the system administrator can update these profile options.
The key for this table is:
Update: You can update the profile option.
View Only: You can view the profile option but cannot change it.
No Access: You cannot view or change the profile option.
This category includes profile options that control display options for the Account nodes in the collector's work queue.
Note: These profile options are owned by Oracle Advanced Collections and are associated only with the Collector's Work Queue, even though they begin with the prefix IEU.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEU: Queue: Account View Delinquencies | No Default | Update | Update | Update | Update | Update |
IEU: Queue: Account View Promises | No Default | Update | Update | Update | Update | Update |
IEU: Queue: Account View Strategies | No Default | Update | Update | Update | Update | Update |
IEU: Queue Order: Account View Delinquencies | No Default | Update | Update | Update | Update | Update |
IEU: Queue Order: Account View Promises | No Default | Update | Update | Update | Update | Update |
IEU: Queue Order: Account View Strategies | No Default | Update | Update | Update | Update | Update |
Choose Yes to display delinquent accounts. Set to No to hide delinquent accounts.
Choose Yes to display accounts for which promises to pay have been broken.
Choose Yes to display strategy work items grouped by account.
Enter number 1, 2, or 3 to specify the order in which the delinquent account node appears in Collector’s Work Queue.
Enter number 1, 2, or 3 to specify the order in which the account broken promise node appears in the Collector’s Work Queue.
Enter number 1, 2, or 3 to specify the order in which the account strategy work item node appears in the Collector's Work Queue
This category includes profile options that control interactions.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Activity Enabled in Account | No Default | Update | Update | Update | Update | |
IEX: Activity Enabled in Adjustment | No Default | Update | Update | Update | Update | |
IEX: Activity Enabled in Delinquency | No Default | Update | Update | Update | Update | |
IEX: Activity Enabled in Dispute | No Default | Update | Update | Update | Update | |
IEX: Activity Enabled in Payment | No Default | View Only | Update | Update | Update | |
IEX: Activity Enabled in Promises | No Default | Update | Update | Update | Update | |
IEX: Activity Enabled in Strategy | No Default | View Only | Update | Update | Update |
Set to Yes to automatically record interaction activity when a collector accesses the Accounts tab and makes a modification. If set to No, then interaction activity must be recorded manually.
Set to Yes to automatically record interaction activity when an Adjustment is created. If set to No, then interaction activity must be recorded manually.
Set to Yes to automatically record interaction activity when a collector accesses the Lifecycle tab and makes a modification. If set to No, then interaction activity must be recorded manually.
Set to Yes to automatically record interaction activity when a Dispute is created. If set to No, then interaction activity must be recorded manually.
Set to Yes to automatically record interaction activity when a Payment is created. If set to No, interaction activity must be recorded manually.
Set to Yes to automatically record interaction activity when a Promise is created. If set to No, then interaction activity must be recorded manually.
Set to Yes to automatically record interaction activity when a collector accesses the Strategy tab and makes a modification. If set to No, then interaction activity must be recorded manually.
This category includes profile options that enable and disable specific business flows within the application.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Allow Changes to Customer Payment Data | Update | Update | Update | Update | ||
IEX: Enable Credit Card Payment | Yes | Update | Update | Update | Update | |
IEX: Enable Credit Hold | Update | Update | Update | Update | ||
IEX: Enable Electronic Funds Payment | Yes | Update | Update | Update | Update | |
IEX: Enable Promise to Pay | Yes | Update | Update | Update | Update | |
IEX: Enable Raising Customer Status Change Event | No | View Only | View Only | View Only | Update | |
IEX: Enable Receipt Reversal | Yes | Update | Update | Update | Update | |
IEX: Skip Default Strategy Assignment | No | Update | Update | Update | Update |
If Yes, then it allows collectors to add and update customer bank account and credit card information.
If Yes, then it enables the Credit Card tab in Processing Payments.
Specify the receipt method set in Oracle Receivables that corresponds to this remittance type.
If Yes, then it displays the Apply Credit Hold and Release Credit Hold option on the Actions menu.
If Yes, then it enables the Electronic Transfer tab in Processing Payments.
If Yes, then it enables the Promise to Pay tab in Processing Payments.
If Yes, it creates a business event to notify integrated applications of a change in delinquency status.
If Yes, then it allows a collector to process a Reversal. If No, then the Reversal button is grayed out.
If Yes, then it will skip the strategy assignment, if no strategy matches the criteria except the default one. If No, then it assigns the default strategy.
This category includes profile options that control the collection methods used by the application.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Contact Information Level | All | Update | Update | Update | Update | Update |
IEX: Enable Real Time Customer Assignment | N | Update | Update | Update | Update | Update |
IEX: Hash Area Size for TAP | No Default | Update | View Only | View Only | View Only | Update |
IEX: Number of Child Account Workers for TAP | 1 | Update | View Only | View Only | View Only | Update |
IEX: Percent Analyzed for TAP | 20 | Update | View Only | View Only | View Only | Update |
IEX: Sort Area Size for TAP | No Default | Update | View Only | View Only | View Only | Update |
IEX: Strategy Assignment Default Resource | No Default | Update | Update | Update | Update | Update |
IEX: Strategy Grace Period | No Default | Update | Update | Update | Update | Update |
IEX: Territory Minimum Number of Records for Parallel Processing | No Default | Update | View Only | View Only | View Only | Update |
IEX: Territory Number of Child Processes | 1 | Update | View Only | View Only | View Only | Update |
Set to All to display contacts from Account Level and Site Level Contacts for a Party and Collections, dunning contact for a party. Set to Account to display contacts from Account Level for a Party and Collections, dunning contact for a party. Set to Bill To to display contacts from Site Level for a Party and Collections, dunning contact for a party.
This profile option determines whether the Territory Access program assigns collectors to customers in batch mode or in real time. Batch mode is recommended. Set to Yes to run in real time. Set to No to assign territories in batch mode.
This profile option sets the hash area size used by the Territory Assignment program when assigning collectors to customers. It controls the amount of memory used by the program. If you do not set this profile option, the hash area size will be 10,000.
This profile option launches the child concurrent programs used by the Territory Assignment program. The minimum value is 1 and the maximum value is 10. If no value is set then the Territory Assignment program derives the number of parallel workers based on the number of records, up to a maximum of 10. If you set this profile option to more than 10, then the program will limit the number of child workers to 10.
Set this profile option one number higher than the desired number of parallel workers. For example, if you want 2 child account workers, enter 3.
The default value is 1.
This profile option sets the percentage of records analyzed when running the Territory Access program. You can enter values between 1 and 100.
The default value is 20.
This profile option sets the sort size area used by the Territory Assignment program. If you change the value for the profile, it only affects system performance when running the Territory Assignment program.
If you do not set this profile option, then the program will set the sort area size at 10,000.
The default value is 10,000.
The resource name (of a person) who will be assigned if no resources match the work item specifications.
Number of days to wait before executing strategies.
This profile option sets the minimum number of records that will cause Territory Assignment program to run in parallel processing mode. If less than the number specified, then program will run in a single mode.
The recommended setting is 100. You do not have to set this profile option unless you want to change system performance.
Default: 100.
This setting determines the minimum number of records for each parallel process run by the Territory Assignment program.
This category includes profile options that control how the application sends correspondence to customers.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Adjustment Fulfillment Template | Update | Update | Update | Update | ||
IEX: Consolidated Invoice Template | No Default | View Only | View Only | View Only | View Only | |
IEX: Default Fulfillment Subject | Message from Collections Department | Update | Update | Update | Update | |
IEX: Dispute Confirmation Letter | No Default | Update | Update | Update | Update | |
IEX: Fulfillment Printer | No Default | Update | Update | Update | Update | |
IEX: Fulfillment Send Method | No Default | Update | Update | Update | Update | |
IEX: Invoice Fulfillment Template | No Default | Update | Update | Update | Update | |
IEX: Pay Reversal Confirmation Letter | No Default | Update | Update | Update | Update | |
IEX: Payment Confirmation Letter | No Default | Update | Update | Update | Update | |
IEX: Promise to Pay Confirmation Letter | No Default | Update | Update | Update | Update | |
IEX: Send Correspondence Automatically | Automatic | Update | Update | Update | Update | |
IEX: SMTP From | No Default | Update | Update | Update | Update | |
IEX: Strategy Default Template | Customer Catch-all Collections Strategy | Update | Update | Update | Update | |
IEX: Strategy Fulfillment Resource | No Default | Update | Update | Update | Update | |
IEX: Strategy Unique Fulfillment | No Default | Update | Update | Update | Update | |
IEX: Use Customer Language for Dunning Letters | No | Update | Update | Update | Update |
Designates the correspondence template to use to send out adjustment confirmation correspondence.
If IEX: Strategy Unique Fulfillment is set to Yes, enter the name of the correspondence template to be used to send one dunning letter to a customer that consolidates all delinquencies for a day.
This profile option determines the text for the subject line of all correspondence e-mails sent out.
Select the correspondence template to be sent to customers as a confirmation when a dispute is recorded. For this to work, IEX: Send Correspondence Automatically must also be set to Yes.
Specify the printer name used by Oracle One-to-One Fulfillment for correspondence.
Note: Since you must now use Oracle XML Publisher for printing, this profile option is no longer used.
If IEX: Send Correspondence Automatically is set to Yes, then you can select E-mail, Fax, or Print to identify the default correspondence send method. If IEX: Send Correspondence Automatically is set to No, there is no default method and the collector selects the send method when sending correspondence.
Enter the template to be used to send a copy of the invoice from Transaction Details.
Select the correspondence template to be sent to customers as a confirmation when a payment reversal is recorded. For this to work, IEX: Send Correspondence Automatically must also be set to Yes.
Select the correspondence template to be sent to customers as a confirmation when a payment is recorded. For this to work, IEX: Send Correspondence Automatically must also be set to Yes.
Select the correspondence template to be sent to customers as a confirmation when a payment is recorded. For this to work, IEX: Send Correspondence Automatically must also be set to Yes.
Set to Automatic to send the dunning letter to the e-mail provided in the organization contacts. Set to Manual to open a popup window in which you can provide the e-mail address to which the dunning letter will be sent. Set to Disabled so that the dunning letter will never be sent.
The name that will appear on the "From" line for e-mails sent to customers.
Select the default strategy template to be assigned if no matching strategy exists when running Strategy Management.
The name that will appear on the "From" line for all e-mails and faxes sent to customers.
Used when running strategies at the delinquency level. This profile controls correspondence sent to customers. Set to Yes to send a single correspondence each day that consolidates all delinquency information. You must also enter the correspondence template name to be used in the IEX: Consolidated Invoice Template profile option.
Used for selecting the language for the dunning letter. Set to Yes to select the language defined for the site to which dunning letter is going to be sent in customer standard form.
This category includes profile options that control display options for viewing customer items in the work queue.
These profile options are owned by Oracle Advanced Collections and are associated only with the Collector's Work Queue, even though they begin with the prefix IEU.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEU: Queue: Customer View Delinquencies | No | Update | Update | Update | Update | |
IEU: Queue: Customer View Promises | No | Update | Update | Update | Update | |
IEU: Queue: Customer View Strategies | No | Update | Update | Update | Update | |
IEU: Queue Order: Customer View Delinquencies | Update | Update | Update | Update | ||
IEU: Queue Order: Customer View Promises | Update | Update | Update | Update | ||
IEU: Queue Order: Customer View Strategies | Update | Update | Update | Update |
Choose Yes to display delinquencies grouped by customer. Set to No to hide delinquent customers.
Choose Yes to display customers for which promises to pay have been broken.
Choose Yes to display strategy work items grouped by customer.
Enter number 1, 2, or 3 to specify the order in which the delinquent customer node appears in the Collector's Work Queue.
Enter number 1, 2, or 3 to specify the order in which the customer broken promises node appears in the Collector's Work Queue.
Enter number 1, 2, or 3 to specify the order in which the customer strategy work items node appears in the Collector's Work Queue.
This category includes profile options that control debugging operations within the application.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Debug Level | 20 | Update | Update | Update | Update | Update |
IEX: Disable iPayment Processing | No | Update | Update | Update | Update | Update |
IEX: On-Line Creditcard Payment | No Default | No Access | No Access | Update | Update | Update |
This profile option controls the level at which debugging information is collected. The default is 20. Generally, this setting should not be changed as the debug level affects system performance.
If you experience problems running the IEX: Strategy Management concurrent program, then set this profile option to 1 to enable SQL Trace. Use trace files to troubleshoot the problem.
Set to Yes to disable Oracle Payments processing in Oracle Lease and Finance Management implementations. Disable payment processing only for debugging purposes. This profile option does not affect processing payments for transactions in Oracle Advanced Collections.
Set this profile option to Yes if you want collectors to be able to authorize credit card payments online. Oracle Advanced Collections determines the validity of the credit card account through Oracle Payments and records the authorization code and payment server ID for the charge.
This category includes profile options that control display options for delinquency work queue items.
These profile options are owned by Oracle Advanced Collections and are associated only with the Collector's Work Queue, even though they begin with the prefix IEU.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEU: Queue: Delinquency View Delinquencies | No Default | Update | Update | Update | Update | |
IEU: Queue: Delinquency View Promises | No | Update | Update | Update | Update | |
IEU: Queue: Delinquency View Strategies | No | Update | Update | Update | Update | |
IEU: Queue Order: Delinquency View Delinquencies | No | Update | Update | Update | Update | |
IEU: Queue Order: Delinquency View Promises | No Default | Update | Update | Update | Update | |
IEU: Queue Order: Delinquency View Strategies | No Default | Update | Update | Update | Update |
Choose Yes to display delinquent transactions in the Collector's Work Queue. Set to No to hide delinquencies.
Choose Yes to display transactions for which promises to pay have been broken.
Choose Yes to include strategy work items grouped by transactions.
Enter number 1, 2, or 3 to specify the order in which the delinquent transaction node appears in the Collector's Work Queue.
Enter number 1, 2, or 3 to specify the order in which transaction broken promise node appears in the Collector's Work Queue.
Choose Yes to include work items for transactions in the Collector's Work Queue.
This category includes profile options that control integration with Oracle Lease and Finance Management.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Case Default Resource | No Default | Update | Update | Update | Update | |
IEX: CB Customer Notification Email From | No Default | Update | Update | Update | Update | |
IEX: CB Customer Notification Email Subject | No Default | Update | Update | Update | Update | |
IEX: CB Customer Notification Template | No Default | Update | Update | Update | Update | |
IEX: CB Notification Grace Days | No Default | View Only | Update | View Only | Update | |
IEX: Check Dunning Amount at Function Currency | Yes | Update | Update | Update | Update | |
IEX: EA Recall Grace Days | No Default | Update | Update | Update | Update | |
IEX: EA Score Diff For Recall | No Default | Update | Update | Update | Update | |
IEX: EA Score Engine ID | No Default | Update | Update | Update | Update | |
IEX: EA Transfer Days | No Default | Update | Update | Update | Update | |
IEX: EA Vendor Notification Email From | No Default | Update | Update | Update | Update | |
IEX: EA Vendor Notification Email Subject | No Default | Update | Update | Update | Update | |
IEX: EA Vendor Notification Template | No Default | Update | Update | Update | Update | |
IEX: Process Strategies by Operating Unit | No Default | Update | Update | Update | Update | |
IEX: Strategy Creation on Bankruptcy | No Default | Update | Update | Update | Update | |
IEX: Turn Off Collections Activity for Bankruptcy | Yes | View Only | Update | Update | Update |
Select the default resource to be assigned if no matching resource exists when assigning cases.
Sets the e-mail address displayed on the From line on the Intent to Report To Credit Bureau notice sent by e-mail to a customer.
The text displayed in the Subject line on the Intent to Report to Credit Bureau e-mail notice sent to a customer.
The name of the correspondence template used to inform the customer of the intent to report them to the credit bureau.
After the customer has been notified about intent to report to the credit bureau, this user profile specifies the number of days before a follow-up is initiated in order to make a decision to report the customer to the credit bureau.
Set to Yes for the current functionality to continue. If set to No, then Advanced Collections checks the minimum dunning invoice amount and minimum dunning amount at Currency level before processing the dunning letter. However the dunning letter will have all the invoices irrespective of limit.
After the elapse of the period for which the case has been transferred to an external agency and if there has been no significant positive change in the case score, the external agency will be informed about intent to recall and will be given a grace period to respond to this notification. This grace period is determined by the value in this user profile.
The score value used to determine eligibility to recall the case from the external agency after expiration of grace days. A concurrent API will compare the scores of a case after the expiration of the transfer period to determine eligibility for recall. If the positive difference in scores is less than the value in this user profile, then a case will be considered for recall and a notification will be sent to the concerned external agency.
The ID of the scoring engine, which is used to score cases for the transfer to external agency process.
The number of days for which a case is transferred to an external agency, after which it is considered for review if there is no significant positive change in the case score. If the review date is not specified in the Transfer to External Agency screen when a case is transferred to an external agency, this value is used to generate the review date.
The FROM EMAIL ID of the e-mail sent to the external agency by the concurrent notification API, to notify about intent to recall the case or a case recall.
Subject of the e-mail sent to the external agency by the concurrent notification API, to notify about intent to recall the case or a case recall.
Content ID of the notification template that is used to inform the external agency of the intent to recall a case, which has been assigned to them, or to inform the external agency about a case recall. It has to be populated with the content ID of the template after the template has been created in Fulfillment. This is used by the concurrent notification API to generate an e-mail, which is sent to the external agency to notify about intent to recall the case or a case recall.
Set to Yes to process strategies by Operating Unit.
Set to Yes to allow creation of strategies for bankruptcy.
If set to No then collections activities are continued. If set to Yes then everything is turned to bankruptcy status, new delinquencies are created for non-delinquent cases and then turned to bankruptcy, so all collections activities are stopped.
This category includes profile options that control operations in the application.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Allow Adjustments | Yes | Update | Update | Update | Update | |
IEX: Allow Disputes | Yes | Update | Update | Update | Update | |
IEX: Allow Promise Date Duplication Within Account | No | Update | Update | Update | Update | |
IEX: Batch Size | No Default | Update | Update | Update | Update | |
IEX: Collections Bucket | iCollections | View Only | Update | Update | Update | |
IEX: Collections Rate Type | Corporate | Update | Update | Update | Update | |
IEX: Callback Days for Broken Promise | No Default | Update | Update | Update | Update | |
IEX: Exclude Dispute Amount From Remaining Amount | No Default | Update | Update | Update | Update | |
IEX: iPayment Payee ID | No Default | Update | Update | Update | Update | |
IEX: Maximum Promise to Pay Range | No Default | Update | Update | Update | Update | |
IEX: Promise Grace Period | No Default | Update | Update | Update | Update | |
IEX: Strategy Disabled | No Default | Update | Update | Update | Update |
Set to Yes to let collectors view adjustment history and initiate adjustments.
Set to Yes to let collectors initiate disputes.
This profile option controls whether collectors can enter more than one promise to pay with the same promise due date for an account.
Set to Yes if an approval is required for promises. If so, a workflow is launched to obtain the approval.
Enter a number if you want to limit the number of objects to be scored at one time.
Determines the number of days after a broken promise is created that a promise callback is created.
The name of the aging bucket created in Oracle Receivables to be used as the default for the Collections Aging tab.
Enter the exchange rate type from Oracle Receivables to be used for Oracle Advanced Collections.
Set this profile option to Yes to exclude the disputed amount from the remaining transaction amount.
Set this profile option if you process payments for Oracle Lease and Finance Management. Select the payment payee ID configured for Oracle Advanced Collections when setting up Oracle Payments.
Name of the workflow launched for the promise approval. (None is seeded.)
Enter the maximum number of days from a payment due date that a promise to pay can be entered. Collectors will be able to enter a promise to pay if the due date for delinquency is not more than this number of days old.
Grace period after the promise is due before it is considered a broken promise.
Set to Yes to disable strategy functionality.
This category includes profile options that control the work queue display for the site.
These profile options are owned by Oracle Advanced Collections and are associated only with the Collector's Work Queue, even though they begin with the prefix IEU.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEU: Queue: Bill To View Delinquencies | Update | Update | Update | Update | ||
IEU: Queue: Bill To View Promises | Update | Update | Update | Update | ||
IEU: Queue: Bill To View Strategies | No | Update | Update | Update | Update | |
IEU: Queue Order: Bill To View Delinquencies | No | Update | Update | Update | Update | |
IEU: Queue Order: Bill To View Promises | No | Update | Update | Update | Update | |
IEU: Queue Order: Bill To View Strategies | Update | Update | Update | Update |
Set to Yes to display delinquencies grouped by bill-to location in Collector's Work Queue. Set to No to hide delinquent bill-to locations.
Set to Yes to display bill-to locations for which promises to pay have been broken.
Set to Yes to display strategy work items grouped by bill-to location.
Enter number 1, 2, or 3 to specify the order in which the delinquent bill-to node appears in the Collector's Work Queue.
Enter number 1, 2, or 3 to specify the order in which the bill-to broken promises node appears in the Collector's Work Queue.
Enter number 1, 2, or 3 to specify the order in which the bill-to strategy work items node appears in the Collector's Work Queue.
This category include profile options that control user interface preferences.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Automatically Populate Grids | Yes | Update | Update | Update | Update | Update |
IEX: Default Date Range Span | 90 | Update | Update | Update | Update | Update |
IEX: Default End Date Range Span | 0 | Update | Update | Update | Update | Update |
IEX: Default History Type | All | Update | Update | Update | Update | Update |
IEX: Default Payment Method | Credit Card | Update | Update | |||
IEX: Default Tab in Collections | Profile | Update | Update | Update | Update | Update |
IEX: Default Transaction Type | No Default | Update | Update | Update | Update | Update |
IEX: Default Universal Search Tab | No Default | Update | Update | Update | Update | Update |
IEX: Default Universal Search Type | No Default | Update | Update | Update | Update | Update |
IEX: Dunning Contact Selection Method | All | Update | Update | Update | Update | |
IEX: Launch Notes History | Grid | Update | Update | Update | Update | Update |
IEX: Maintain Status in Lifecycle Tab | Not Allowed | Update | Update | Update | Update | Update |
IEX: Metric Calculation Method | No Default | Update | Update | Update | Update | Update |
IEX: Minimum Number of Characters for Lookup | No Default | Update | Update | Update | Update | Update |
IEX: Service Hold of Delinquencies | No | Update | View Only | View Only | Update | Update |
IEX: Show Last Payment Due On Field | Yes | Update | Update | Update | Update | Update |
Set to Yes to automatically populate grids. Set to No to require the user to click Display to populate tables. To reduce performance issues relating to display of large amounts of data, set to No.
Enter the number of days of data to be included in a search or in information displayed as a default on the History and Transaction tabs. For example, if you want searches to return a four month range of data as a default, enter 120. You must also set the IEX: Default End Date Range Span profile option.
After you set the IEX: Default Date Range Span profile option, set this profile option to indicate when you want the default date range span to end. Enter a negative number to set the end date in the future. For example, if the default date range span is 120 days and you want to display data for 90 days previous to today's date and 30 days in the future, enter -30.
Set this profile option to determine the default history type displayed on the History tab.
Choose the type of payment tab to appear when the user opens the Process Payments window.
Choose the Collections window tab to appear when the user first opens the Collections window.
Enter the transaction type to be the default that is displayed on the Transactions tab of the Collections window.
Use this profile option to set the default tab that appears when using Universal Search.
Use this profile option to set the default search type selected when using Universal Search.
If set to All, all the contact roles are selecting while choosing the contact. If set to Dunning, then it selects only the dunning contact role while choosing the contact.
This profile option controls the format used to display notes. Set to Grid to display notes in an exportable, table format. Set to Text to display notes in a plain, readable text format.
This profile option controls whether the New Status button in the Lifecycle tab be displayed or not. By default, it is set to Not Allowed.
This profile option controls whether Oracle Advanced Collections calculates customer metrics in batch mode or in real time when you access the Profile tab.
Set this profile option to determine the minimum number of characters that a collector must type before seeing a list of values.
Set to Yes if you are using Oracle Lease and Finance Management. Setting No disables the Service Hold check box on the Lifecycle tab.
This profile option determines whether Oracle Advanced Collections displays information in the Last Payment Due On field on the Collections header. Setting this profile option to No improves system performance.
This category includes profile options that control the general display parameters in all the Collections work queues.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Enable Work Queue Statuses | No | Update | Update | Update | Update | |
IEX: Hide Bankruptcy in UWQ | Yes | Update | Update | Update | Update | |
IEX: Territory Access | No Default | View Only | Update | Update | Update | |
IEX: UWQ Default Complete Node Days | 30 | Update | Update | Update | Update | |
IEX: UWQ Default Pending Days | 10 | Update | Update | Update | Update | |
IEX: Work Queue Access | Full | Update | Update | Update | Update |
Set this profile option to display or hide the Active, Pending, and Complete subnodes in the Collector's Work Queue. If set to Yes, collectors can use the Actions menu to update the status of work items assigned to them.
Choose No to display bankruptcies tasks for collectors in Collector's Work Queue.
This profile option determines the level at which the Territory Assignment program runs. It can be set at the customer, account, or bill-to level. This setting assigns collectors at the desired level and is the same data level you do business with your customers. The default value is Customer.
You must rerun the IEX: Territory Assignment concurrent program, if you change the setting.
Enter the number of days a work item will stay in the Complete node before it is removed.
Enter the number of days a work item will stay in the Pending node before moving to the Active Node.
Note: If you set this profile option to null, work items will remain in the Pending node for 20 days.
Allows either Full or Restricted access to the Collector's Work Queue. Full access provides visibility to all customers. Restricted access provides visibility to only those customers assigned to the user by the Territory Assignment process.
This category includes profile options related to using Oracle XML Publisher to send correspondence.
Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
---|---|---|---|---|---|---|
IEX: Fax IPP Host | No Default | Update | Update | Update | Update | |
IEX: Fax IPP Port | No Default | Update | Update | Update | Update | |
IEX: Fax IPP Printer Name | No Default | Update | Update | Update | Update | |
IEX: IPP Printer Name | No Default | Update | Update | Update | Update | |
IEX: Print IPP Host | No Default | Update | Update | Update | Update | |
IEX: Print IPP Port | No Default | Update | Update | Update | Update | |
IEX: SMTP Host | No Default | Update | Update | Update | Update |
Note: IEX: Document Format for XML Publisher profile option is no longer used.
Set this profile option to identify the IPP host name for faxing.
Set this profile option to identify the IPP Port used for faxing correspondence generated by XML Publisher.
Set this profile option to identify the IPP printer name used for faxing correspondence generated by XML Publisher.
Specify the printer name for sending correspondence generated by Oracle XML Publisher. Begin the name with a slash (/) as in /printer1.
Specify the name of the print host used by Oracle XML Publisher for correspondence. Use the format printer host name + domain as in xdo.us.oracle.com. Do not include a protocol such as http://.
The name of the print port used by Oracle XML Publisher.
The name of the e-mail server.
The following table provides a list of profile options set when you answer questions in the Collections Questionnaire.
Section | Question | Sets |
---|---|---|
Operations | At what level does your organization do business with customers? | IEU: Queue: Account View Delinquencies IEU: Queue: Account View Promises IEU: Queue: Account View Strategies IEU: Queue: Customer View Delinquencies IEU: Queue: Customer View Promises IEU: Queue: Customer View Strategies IEU: Queue: Delinquency View Delinquencies IEU: Queue: Delinquency View Promises IEU: Queue: Delinquency View Strategies IEU: Queue: Bill-to View Delinquencies IEU: Queue: Bill-to View Promises IEU: Queue: Bill-to View Strategies |
Transactions | Do collections agents take payment from customers? | Displays Bank Transfer and Credit Card tabs in Payment Processing |
Transactions | Which payment methods do you accept? | IEX: Enable Credit Card Payment IEX: Enable Electronic Funds Payment |
Transactions | What other transaction activities do you allow? | IEX: Enable Receipt Reversal IEX: Allow Adjustments IEX: Allow Disputes |
Transactions | Do you take promises to pay from your customers? | IEX: Enable Promise to Pay |
Transactions | Which later stage delinquencies does your organization manage? | IEX: Default Bankruptcy Notice of Assignment IEX: Turn Off Collections Activity on Bankruptcy IEX: Turn Off Invoice on Bankruptcy IEX: Hide Bankruptcy in UWQ |
Collections Methods | Which collections methods does your organization use? | IEX: Strategy Disabled |
Collections Checklist: Operations Setup
The following table provides a list of profile options set when you answer questions in the Operations Setup section of the Collections Checklist.
Topic | Question | Sets |
---|---|---|
General Collections Information | What aging bucket should be automatically displayed? | IEX: Collections Bucket |
General Collections Information | Should collectors have access to all customers or only customers they work with? | IEX: Work Queue Access |
General Collections Information | At which level do you assign territories to collectors? | IEX: Territory Access Level |
General Collections Information | Select the exchange rate type for multi-currency transactions. | IEX: Collections Rate Type |
General Collections Information | Are collectors allowed to assign or release a customer credit hold? | IEX: Enable Credit Hold |
General Collections Information | Will collectors initiate service hold requests? | IEX: Service Hold of Delinquency |
General Collections Information | Which items do you want to track from customer interactions? | IEX: Activity Enabled in Accounts IEX: Activity Enabled in Adjustment IEX: Activity Enabled in Delinquency IEX: Activity Enabled in Dispute IEX: Activity Enabled in Payment IEX: Activity Enabled in Promises IEX: Activity Enabled in Strategy |
Display Preferences | Select the tab that will be displayed when a collector opens the Collections window. | IEX: Default Tab in Collections |
Display Preferences | Select the default history type for the History tab. | IEX: Default History Type |
Display Preferences | Select the Search tab to be displayed in the Search window. | IEX: Default Universal Search Tab |
Display Preferences | Which search type will be displayed in the Search window? | IEX: Default Universal Search Type |
Display Preferences | What is the minimum number of characters that an agent needs to type before seeing a list of values? | IEX: Minimum Number of Characters for Lookup |
Display Preferences | How many days of data do you want to display automatically on the History and Transaction tabs? | IEX: Default Date Range Span |
Display Preferences | How many days forward or back from today's date should the date range start? | IEX: Default End Date Range Span |
Display Preferences | Should data be displayed automatically for collectors? | IEX: Automatically Populate Grids |
Display Preferences | Should collectors see more than one operating unit in the Work Queue? | IEU: Desktop: UI: Show Quick Filter Panel |
Display Preferences | Select the default payment method tab to be displayed on the Payments window. | IEX: Default Payment Method |
Display Preferences | Do you want to calculate metrics in batch or real-time? | IEX: Metric Calculation Method |
Correspondence | Do you want to send correspondence automatically after each customer interaction? | IEX: Send Correspondence Automatically |
Correspondence | What should be the default send correspondence method? | IEX: Fulfillment Sent Method |
Correspondence | For each of the following select the letter template to be used. | IEX: Adjustment Fulfillment Template IEX: Consolidate Invoice Template IEX: Dispute Confirmation Letter IEX: Invoice Fulfillment Template IEX: Pay Reversal Confirmation Letter IEX: Payment Confirmation Letter IEX: Promise to Pay Confirmation Letter |
Correspondence | For each of the following, enter the XML Publisher setting. | IEX: Fax IPPHost IEX: Fax IPP Port IEX: Fax IPP Printer Name IEX: IPP Printer Name IEX: Print IPP Host IEX: Print IPP Port IEX: SMTP Host |
Correspondence | What 'From' address should appear in XML e-mail correspondence? | IEX: SMTP From |
Collections Checklist: Transaction Setup
The following table provides a list of profile options set when you answer questions in the Transactions Setup section of the Collections Checklist.
Topic | Question | Sets |
---|---|---|
Configure Transaction Processing | Select the default transaction type for the Transaction tab. | IEX: Default Transaction Type |
Configure Transaction Processing | Select the name of the vendor bank used to process electronic payments. | IEX: iPayment Payee ID |
Configure Transaction Processing | Can collectors update customer bank account and credit card information? | IEX: Allow Changes to Customer Payment Data |
Configure Transaction Processing | How many days after the promise payment due date will a promise be called broken? | IEX: Promise Grace Period |
Configure Transaction Processing | How many days from a payment due date can a promise to pay be made? | IEX: Maximum Promise to Pay Range |
Configure Transaction Processing | How many days after the promise is broken should a callback be scheduled? | IEX: Callback Days for Broken Promise |
Configure Transaction Processing | Can more than one promise to pay have the same promise due date? | IEX: Allow Promise Date Duplication with Account |
Collections Checklist: Collections Method Setup
The following table provides a list of profile options set when you answer questions in the Collections Method Setup section of the Collections Checklist.
Topic | Question | Sets |
---|---|---|
Define Strategy Defaults | Select a default strategy template. | IEX: Strategy Default Template |
Related Topics
Profile Options and Profile Categories Overview
Setting Up Oracle Advanced Collections
IEU: Desktop: UI: Show Quick Filter Panel: Set this profile option to Yes to be able to filter tasks by operating unit in the Collector's Work Queue. The default is Yes.
OS: Customer Access Privilege: This profile determines which customers a collector can view in eBusiness Center. Set to Full Access to view all customers; set to Sales Team/Territory Access to view only customers in a collector's territory; set to Prospecting and the collector can read but not write data. This can be set at all profile levels.
OTS: Interactions-Default Action: Users must perform at least one activity for the interaction to end. If the user doesn't perform any activity but ends the interaction anyway, then the application uses the default action set in this profile and the default action item from the OTS: Interaction Default Action Item profile option.
The default is Action with action ID = 1 (Item Added).
OTS: Interactions-Default Action Item: The application uses the default action item set in this profile together with the default action set in the OTS: Interaction Default Action profile option whenever the user does not perform an action required to wrap up an interaction.
The default is Action item with action ID = 1 (Account).
OTS: Interactions-Default Outcome: This profile determines the default value of the Outcome field in the wrap-up window.
This is also the value the application uses for outcomes of interactions that are ended automatically. The application uses this value if there is no outcome associated with the campaign schedule for this interaction. If there is a campaign associated with the interaction, then the application uses the outcome for that campaign schedule.
The default is Outcome with outcome ID = 1 (No Answer).
OTS: Interactions-Enable Auto Wrapup: When this profile is set to No, the wrap-up window appears automatically prompting users to enter the outcomes and reasons for the activity.
When this profile is set to Yes, the interaction ends automatically without the users seeing the wrap-up window.
OTS: Interactions-Enable Automatic Start: Set to Yes to record interactions after the interaction is started. Set to No to require agents to start and end interactions manually.
OTS: Interactions-Record Media Item ID: Interactions track different types of communications with customers including e-mails and phone calls placed through Oracle Inbound and Outbound Telephony applications. The record includes a unique identifier for the communication. This profile determines if that unique identifier is recorded or not. This identifier is never displayed for the user.
The default is Yes.
OTS: Interactions-Max Interactions Displayed: Determines how many interactions to display in the Overview tab.
OTS: Interactions-Start On Query: Set to Yes to start an interaction whenever the user displays a new record and to support automatic start of interactions.
Set to No to start the interaction only when the user updates or deletes information in a record.
The default is No.
OTS: Task Details-Query Tasks By: If set to Reference, Oracle Advanced Collections displays on the Task tab only tasks associated with the View By selected in the Collections header.
OTS: Telesales Interaction Enabled: If set to Yes, TeleSales records interactions after the interaction is started. A setting of No limits agents to starting and ending interactions manually.
The default is No.
Related Topics