Вы находитесь на странице: 1из 19

Why is the UWQ blank or not Showing Correct Data? [ID 784274.

1] Modified 09-AUG-2011 In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details How the UWQ is Populated? Verify you setup Credit Management Verify your Collector: Type TROUBLESHOOTING Status PUBLISHED

How to Know What Nodes Should be Displayed? Other Setups to Check: Looking at the Data: NOTE: For Release 12.1.2 What about the Broken Promise and Work Item nodes?

Applies to:
Oracle Advanced Collections - Version: 11.5.10.2 to 12.1.1 - Release: 11.5.10 to 12.0 Information in this document applies to any platform. This Troubleshooting Guide is relevant to customers that have applied 5660900, 11i.IEX.H RUP4 or Release12. If you have not applied 5660900 or you are on 11i.IEX.H RUP3.1 and lower, this document will not help you. ***Checked for relevance on 7-May-2010***

Purpose
The purpose of this document is to provide you with a list of things to check when you find that the data in the UWQ for Collections is either missing or not correct.

Last Review Date


March 18, 2009

Instructions for the Reader


A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details How the UWQ is Populated?

The data that is displays in the UWQ comes from the IEX_DLN_UWQ_SUMMARY table. This table is populated by the IEX: Populate UWQ Summary Table concurrent process and below is the list of input to this process:

Credit summary data comes from the AR_TRX_BAL_SUMMARY table. TCA data comes from the HZ_PARTIES and HZ_CONTACT_POINTS tables. Delinquency information comes from the IEX_DELINQUENCIES_ALL and IEX_PROMISES tables. Strategy Work Item information comes from the IEX Strategy and Work Items tables.

Therefore, you should only run the IEX: Populate UWQ Summary Table concurrent process after you've confirmed the AR_TRX_BAL_SUMMARY table is populated, you've run the IEX: Scoring Engine Harness and the IEX: Strategy Management concurrent processes. Since the Credit summary data comes from the AR_TRX_BAL_SUMMARY table, you must make sure this table is populated correctly with AR data before proceeding with the IEX concurrent processes. The AR_TRX_BAL_SUMMARY table is initially populated by the Refresh AR Summary Table concurrent process and then as balances are created and paid in Receivables, Workflow Business Events are triggered to update the AR_TRX_BAL_SUMMARY table so that the data is up to date. If the data becomes out of date, chances are the business events are not being processed. You can quickly update the entire table by running the Refresh AR Summary Table. Troubleshooting the workflow business events can be done with the help of Note: 393204.1. To run Refresh AR Summary Table concurrent process: 1. Under System administrator set profile "AR: Allow Summary Table Refresh" = Yes at the Application level. 2. Profile may or may not be updateable at the application level. If not, login as application developer and change it's updateable value. 3. Run the Concurrent Process Refresh AR Transactions Summary Table. Once the AR_TRX_BAL_SUMMARY table is accurate, you can move forward with the IEX concurrent processes. You would run them in the following order: IEX: Scoring Engine Harness IEX: Strategy Management (if you are using strategies) IEX: Populate UWQ Summary Table At this point, the current data should appear in the UWQ.

Verify you setup Credit Management


-Using Credit Management SuperUser responsibility -Policy Management>System Options -Make sure that these settings are set including Exchange Rate -You can tell if they are set because when you first look at the screen, if you can select an

aging bucket, then it's not set. When the system options are set, you should not be able to select an aging bucket.

Verify your Collector:


Confirm that you have assigned a valid Collector to the Customer, Account or Bill To depending on how you have setup Collections. This Collector must have a Collections Role assigned. If the IEX: Work Queue Access profile is set to Restricted, only the customers owned by the Collector will see data in the Delinquency nodes. If you are looking at the Broken Promise and Strategy Work Items nodes, the profile IEX: Work Queue Access is not used, instead the collector must be assigned to these activities to see them in the UWQ.

How to Know What Nodes Should be Displayed?


The UWQ is based on your operational or strategy level. If you have your strategy level set to Customer, you will only have data in the Delinquent Customer node. If you have your strategy level set to Account, you will only have data in the Delinquent Account node. If you have your strategy level set to Bill To, you will only have data in the Delinquent Bill To node. You should confirm that you have the appropriate Nodes listed for your level. See Note 729255.1 for details on the profile options.

Other Setups to Check:


1. Make sure you have set the Exchange Rate in Credit Management see Note: 282798.1 2. Confirm your Collector assignment. You must have collectors assigned or setup properly, without collector assignments you will not have valid data in the IEX_DLN_UWQ_SUMMARY table to be displayed in the UWQ.

Looking at the Data:


1. Check the IEX_DLN_UWQ_SUMMARY and AR_TRX_BAL_SUMMARY table to see if data exists for your customer:
1> select cust_account_id from hz_cust_accounts where account_number = '&customer_number'; Using the cust_account_id, run the next SQL 2> Select cust_account_id, site_use_id, org_id, currency, op_invoices_value, op_invoices_count, last_payment_amount, last_payment_date from ar_trx_bal_summary where cust_account_id = &cust_account_id from above;

3> Select * from iex_dln_uwq_summary where cust_account_id = &cust_account_id from above;

If you have no data in these tables, then you need to look at the processes that populate the tables. Lack of data in these tables will give you a blank or zero count UWQ. 2. Confirm these accounts truly are past due/delinquent. Make sure that these accounts have rows in the IEX_DELINQUENCIES_ALL table.
select * from iex_delinquencies_all where cust_account_id = &custacctid;

If there are no delinquencies in the IEX_DELINQUENCIES_ALL table, then you need to check AR and make sure the customer has past due invoices that are not disputed. Make sure that you have profile IEX: Batch Size set to at least 100,000 so that it will process all past due invoices. If the customer has past due invoices that are not disputed then rerun the IEX: Scoring Engine Harness for seeded Scoring Engine #2 - Delinquency Status Determination, then run the appropriate scoring for your Strategy/Dunning Level.

NOTE: For Release 12.1.2


Patch 9596144 was released and now the update of the AR_TRX_BAL_SUMMARY table (step 1 above) is now a separate process. IEX: Update AR Transaction Summary Table concurrent process will now handle the update of the table outside of the IEX: Populate UWQ Summary Table concurrent process. The following processes should run in the following order: 1. IEX: Update AR Transaction Summary Table 2. IEX: Populate UWQ Summary Table

What about the Broken Promise and Work Item nodes?


These nodes are controlled by the collector logging into the application and not the IEX: Work Queue Access profile option. You must be the owner of the promise or work item to see the data in the UWQ. For the Work Item, you can review the iex_dln_uwq_summary.wkresource_id column for the work item and compare the value to the collector. For the Broken Promise, you can review the iex_dln_uwq_summary.collector_resource_id column to compare with your collector.

Advanced Collections

Current Issues: Recently, I've noticed an increase in the amount of Service Requests that we receive regarding data in the UWQ not being correct. I'm going to cover this topic again in this newsletter, because it's a bit tricky and I think that a refresher course might be needed. After the application of patch 5660900, 11i.IEX.H.RUP4 or R12 the UWQ will only show data in the nodes associated to the Strategy Level and in the IEX_DLN_UWQ_SUMMARY table. --If you have your strategy level set to Customer, then you will only have customer data in the Delinquent Customer node. --If you have your strategy level set to Account, then you will only have customer data in the Delinquent Account node. --If you have your strategy level set to Bill To, then you will only have customer data in the Delinquent Bill To node This change was made due to the performance of the UWQ and is described in depth in Note: 405933.1 Also, it is expected that you are running the Workflow Agent Listener to process business events to the AR_TRX_BAL_SUMMARY table so that it's kept up to date with AR. This table is input for the IEX: Populate UWQ Summary Table concurrent process. You will also want to be sure to run the IEX: Scoring Engine Harness and IEX: Strategy Management concurrent processes on a regular basis, prior to running IEX: Populate UWQ Summary Table. Lastly, IEX: Work Queue Access set to Restricted will only allow the Collector assigned to the Customer/Account/BillTo to see their data in the UWQ. The Delinquent Transactions node looks at live Collections data, not the data in the IEX_DLN_UWQ_SUMMARY table. The above information does not apply to the Delinquent Transactions node. When you first see that the data in the UWQ is incorrect, you need to look at the IEX_DLN_UWQ_SUMMARY table and make sure the data there is the same, if it's the same as the UWQ, then the problem is with the data, not the UWQ. If the data is different, then the problem is with the UWQ. If the data is the same, then you have to check the AR_TRX_BAL_SUMMARY table and confirm that you have accurate data there as well. If it's not accurate, then IEX_DLN_UWQ_SUMMARY will not be accurate and hence the UWQ will not be accurate. Note: 784274.1 steps you through the entire troubleshooting process and includes the select statements that you can use to look at the data in these tables. Lastly, the IEX: Work Queue Access profile option controls the data that is seen in the UWQ by your collectors. Note: 858772.1 will explain how this profile works in conjunction with the data.

http://download.oracle.com/docs/cd/E18727_01/doc.121/e13452/T387641T387647.htm#T387728

Oracle Advanced Collections Implementation Guide Release 12.1 Part Number E13452-04

Content s

Previou Next s

Verifying the Implementation


This chapter discusses how to verify that your implementation is successful. This chapter covers the following topics:

Use the Diagnostic Tests Implementation Verification Tasks for Mandatory Components Create Accounts Create Invoices Create Delinquencies Verify Delinquencies Dispute an Invoice Adjust an Invoice Record a Promise to Pay Process a Credit Card Payment Process a Bank EFT Payment Verify Payment Processing Verify the Collector's Actions Verify Collector's Work Queue Navigation Verify Interaction Tracking Implementation Verification Tasks for Optional Components Verifying Integration with Oracle Lease and Finance Management

Use the Diagnostic Tests


After completing the implementation steps, run the entire suite of diagnostic tests available for the CRM Foundation application using the System Administration responsibility. You can run the tests from the Basic tab or the Advanced tab. In the Basic tab, you can run the following tests:

RunAll UserTest AOLTests

PropertyManager UserProfile AKData Security Manager TerritoryManager DiagnosticsSecurity JTFSessions AOLSessions CachingFramework

In the Advanced tab, you can modify the parameters used in the test. Each test generates a report if a problem is encountered. The report identifies the problem and provides a suggested resolution to the problem. Related Topics Implementation Verification Tasks for Mandatory Components Implementation Verification Tasks for Optional Components

Implementation Verification Tasks for Mandatory Components


Perform the tasks in this section to verify the implementation of the mandatory components of Oracle Advanced Collections. Note: You must complete the prerequisites before performing the verification tasks. Prerequisites

Configure Collections Checklist, Questionnaire and tasks.

1. Dunning Letters 2. Follow Up Payment, Promise, Adjustment, and Dispute Templates 3. Send Copy of Invoice template 1. Select Components 2. Weight Components 1. 2. 3. 4. Select Dunning Plan level Select Aging Bucket for Dunning Plan Create Dunning Plan Select Dunning Letters

Create Scoring Components Create Scoring Engine

Determine if you will run Dunning Plans or Strategies. If running Dunning Plans:

Configure Oracle Receivables Credit Memo Workflow Configure Collector's Work Queue nodes If you run Strategies:

5. Determine send method for Letter Fulfillment 6. Determine callback requirements (Select Yes for testing)

1. Select data level 2. Create or use test Work Item Templates 3. Create or use test Strategy Templates

Tasks
The following list describes the Implementation Verification tasks for Mandatory Components in detail: 1. Create Accounts 2. Create Invoices 3. Create Delinquencies 4. Verify Delinquencies 5. Dispute an Invoice 6. Adjust an Invoice 7. Record a Promise to Pay 8. Process a Credit Card Payment 9. Process a Bank EFT Payment 10. Verify Payment Processing 11. Verify the Collector's Actions 12. Verify Collector's Work Queue Navigation 13. Verify Interaction Tracking

Create Accounts
Create some test accounts tied to existing customers. Guidelines You can also create accounts in Oracle Receivables using the Customer page. You should create several accounts so that you can verify individual account information is reflected accurately in the Collections Header as well as in the Aging tab and Delinquency table on the Profile tab. In order to test the Dunning and Fulfillment functions, enter your e-mail address as the Primary Bill To address. By doing this, once the Dunning Plan is executed, you will be able to verify that the appropriate dunning letter with the appropriate data is received.

Steps 1. Using the Collections Agent or Collections Manager responsibility, navigate to the eBusiness Center. 2. Search and select a customer. 3. Navigate to the Account tab. 4. Click New. 5. Enter account information. 6. Enter your e-mail address as the primary bill to address. 7. Save. Keep a note of the customer name and account number. 8. Repeat for two more accounts for that customer. Repeat steps to have multiple customers with multiple accounts. Add the customer names and account numbers to your note. Related Topics Implementation Verification Tasks for Mandatory Components

Create Invoices
Create invoices in Oracle Receivables complete with line items and amounts, and then make them due immediately or with 30/60/90 terms. Back date the creation dates so that the invoices will be flagged as delinquent when the concurrent program requests are submitted. Here is where you create the individual invoice lines, compute tax, and then complete the invoices. Then you are ready to request concurrent programs so that these invoices are aged and will become delinquencies. Steps 1. Using the Receivables, Vision Operations or comparable responsibility in a test or live environment, from the Navigator, open Transactions and choose Transactions. 2. Enter a free form invoice number. 3. Select Invoice type. 4. Select Invoice class. 5. For Terms select IMMEDIATE. This creates an immediate delinquency. 6. Enter Invoice Lines using the following steps for each line: a. Choose Line Items. The Line window appears.

b. c. d. e.

Enter item, description, quantity, and unit price. Close Lines window. Click Tax. Click Complete.

Tip: Make the line items on each invoice different and remember what the totals are so that you can verify amounts on the Collections Header and Profile tab. Related Topics Implementation Verification Tasks for Mandatory Components

Create Delinquencies
Steps 1. Using the Collections Administrator responsibility, choose Requests from the View menu. The Find Request window appears. 2. 3. 4. 5. Click Submit a New Request. Select Single Request. Click OK. Run the following concurrent programs for Dunning Plans in this order: o IEX: Promise Reconciliation o IEX: Scoring Engine Harness: request a Transaction Scoring Engine to score invoices and then to create delinquencies o A second IEX: Scoring Engine Harness: request a Party Scoring Engine and an Account Scoring Engine o IEX: Send Dunning for Delinquent Customers o IEX: Create Dunning and Broken Promise Call Backs Each concurrent program must complete before any subsequent concurrent program is submitted, to ensure the accuracy of the data and programs. 6. Run the following concurrent program to verify strategies: o IEX: Strategy Management Related Topics Implementation Verification Tasks for Mandatory Components

Verify Delinquencies
Verify if delinquencies were accurately created and if all the dependent processes occurred. Steps 1. Using the Collections Agent responsibility, go to Collector's Work Queue and see if the delinquent accounts are listed under the Delinquent Accounts node. 2. Verify that there are callback tasks in the Task node for the delinquent accounts. 3. Navigate to the Collections window. 4. Can you find all of your delinquencies in the Collections Header? Switch account views to verify delinquent amounts, number of invoices, and the collections score. 5. Select the Transactions tab and verify delinquencies are listed. Switch between Customer, Bill To, and Account views to see data in all views. 6. Select the Aging tab and verify aging information. Switch between Customer, Bill To, and Account views in the Collections Header. 7. Click the customer's name (Organization) in the Collections header. The eBusiness Center displays the customer information. 8. Select the Collections tab and make sure the information is the same as on the Profile tab. 9. Return to the Collections window and navigate to the History tab. 10. Select the Dunning History. You should see the dunning events that have occurred. These are the dunning letters that should have been e-mailed to you when the concurrent programs were run. 11. Check your e-mail. Did you receive a dunning e-mail for each delinquent account? The dunning letter should list all of the delinquent transactions for each account. 12. If you use strategies, go to Collector's Work Queue and verify that Strategy Work Items are displayed. 13. Select a work item to open the Strategies tab in Advanced Collections. 14. Verify that an Open Strategy is displayed in the parent table and one Open Work Item is displayed in the child table. 15. Select Work Item Details and review the work item. 16. Click Complete Work to complete the work item. Verify that a new Open Work Item appears. Related Topics

Implementation Verification Tasks for Mandatory Components

Dispute an Invoice
Verify that a collections agent can record a dispute for an invoice. Tip: Keep a record of your dispute for later verification. Steps 1. 2. 3. 4. 5. 6. 7. Using the Collections Agent responsibility, select the customer. In the Transactions tab, select an invoice. Click Transaction Details. Enter a dispute reason. Enter a dispute quantity or amount. Enter a note. Click Submit. Oracle Advanced Collections calls the Oracle Receivables Credit Memo Workflow. 8. Click Send Copy. A copy of the transaction is e-mailed to you. Related Topics Implementation Verification Tasks for Mandatory Components

Adjust an Invoice
Verify that a collections agent can adjust an invoice. Steps 1. 2. 3. 4. Using the Collections Agent responsibility, select the customer. In the Transactions tab, select an invoice. Click Adjustment Processing. Create a new row in the Adjustment Processing region and enter the required adjustment details: activity name, type, amount, date, line number, and note. 5. Click Adjustment. Oracle Advanced Collections reviews the approval limits defined in Oracle Receivables before processing the adjustment.

If you set up the appropriate profile options, then a copy of the adjustment is emailed to your customer. Related Topics Implementation Verification Tasks for Mandatory Components

Record a Promise to Pay


Steps 1. Select the customer. 2. In the Transactions tab, select an invoice. 3. Click Payment Processing. The Payment Processing window appears. 4. Enter a payment amount. 5. Enter three promise to pay lines, each with a different due date. Make one due date today's date. Enter three different amounts. 6. Enter a note. 7. Click Submit. Note: Alternatively, you can process a Mass Promise to verify broken promise functionality. Related Topics Implementation Verification Tasks for Mandatory Components

Process a Credit Card Payment


Oracle Payments processes the credit card information and applies the cash in Oracle Receivables. Prerequisites

Oracle Payments must be fully configured.

Steps 1. Select the customer. 2. In the Transactions tab, select an invoice. 3. Click Payment Processing.

The Payment Processing window appears. 4. Enter a payment amount. 5. Enter the bogus credit card number such as 4111111111111111 (4 followed by 15 1's). 6. Enter the amount to be charged against the credit card. Keep a note of the payment amount for later verification. 7. Enter a note for the payment. 8. Click Submit. Related Topics Implementation Verification Tasks for Mandatory Components

Process a Bank EFT Payment


The final type of payment processing is Bank Electronic Funds Transfer or EFT. Collectors use this type of money transfer to take payments immediately. Similar to credit card payment processing, Oracle Advanced Collections calls Oracle Payments to verify the bank information and to obtain the authorization for the funds transfer. Prerequisites

Oracle Payments must be fully configured.

Steps 1. Using the Collections Agent responsibility, select the customer. 2. In the Transactions tab, select an invoice. 3. Click Payment Processing. The Payment Processing window appears. 4. 5. 6. 7. Enter a payment amount. Enter bank numbers and amounts. Enter a note for the payment. Click Submit.

Related Topics Implementation Verification Tasks for Mandatory Components

Verify Payment Processing


At this time, you can verify if the payments and disputes that were attributed to the delinquencies were accurately processed by Oracle Advanced Collections and Oracle Payments, and ultimately posted within Oracle Receivables. Guidelines If all points do not verify, check the following:

Did the concurrent programs complete? Was transaction information updated? Was correspondence sent out, if applicable?

Steps 1. Using the Collections Agent responsibility, go to Collector's Work Queue and check the following: a. Are the counts of delinquent transactions by Account a smaller number now that some are paid? b. Is the broken Promise to Pay now represented in the Account Level Promise node? Check the count of the broken promises by Account. c. What is the status of the delinquency that is in Dispute? 2. Navigate to the Collections window and verify the following: a. Can you find these delinquencies in the Collections Header: switch account views, verify delinquent amounts and number of invoices. Have the cured delinquencies been removed? b. Move to the Profile tab and verify the delinquencies can be seen in the Delinquency View. Are all of the delinquencies there? c. Move to the Transactions tab. Switch between each account and see if the delinquent invoices are there. What is the status of the disputed invoices? 3. Click the customer's name (Organization) to navigate to eBusiness Center. Check the data on the Collections tab. 4. Check your e-mail. Did you receive an e-mail for each payment, promise, adjustment, or dispute processed with the appropriate payment, promise, adjustment, and dispute information included? Did you receive a copy of the invoice as per the request? Related Topics Implementation Verification Tasks for Mandatory Components

Verify the Collector's Actions

At this time, you can verify what the collectors have done and if all of their actions have been recorded in the various histories, if all notes have been saved, and if all payment processing transactions appear in reports. Guidelines If all points do not verify, check the following:

Did the concurrent programs complete? Are the reports running at all?

Steps 1. Using the Collections Agent responsibility, in the History tab of the Collections window, go to Payment history and verify your credit card and bank EFT payments, including your notes. Go to the Promise to Pay history and verify your recorded promises and related notes. 2. Go to the Dispute history and verify the details of the dispute and your notes. 3. From the Navigator, choose Reports. The Collections Reports page appears in a separate browser window. 4. Check the Reconciliation Report to see if the broken promise is noted. 5. Check the Collector Report to see if all payments, promises, and disputes are noted, if invoice information is accurate, and if accounts are noted. 6. Go to the Collections header and look for the information that is on the Collector Report. Switch account views and verify delinquent amounts and number of invoices. Have the cured delinquencies been removed? Related Topics Implementation Verification Tasks for Mandatory Components

Verify Collector's Work Queue Navigation


At this time, you can verify if the flows from Collector's Work Queue (UWQ) are mapped to the correct tab within Oracle Advanced Collections. You should check each flow to ensure the collector can efficiently navigate through the application. Guidelines

If the verification fails, review your selections in the Collections Questionnaire and Checklist. See: Display Collector's Work Queue Nodes. Steps 1. Using the Collections Agent responsibility, from the Navigator, choose Collector's Work Queue. The UWQ window opens. From UWQ Account Level Delinquency node select a delinquency and click Get Work. Does the Collections Transactions tab appear with the selected delinquent invoice highlighted and the appropriate data level set in the Collections Header? 2. From UWQ Account Level Promise node select a Broken Promise and click Get Work. Does the appropriate customer appear in Collections and the right Promise record appear on the History tab? 3. From UWQ customer level strategy work item node, select a work item and click Get Work. Does the appropriate strategy and work item appear on the Strategy tab? 4. From UWQ Task node, find a callback and click Get Work. Does the Collections Dunning History appear with selected dunning and invoice highlighted? Related Topics Implementation Verification Tasks for Mandatory Components

Verify Interaction Tracking


Interaction Tracking can be manual or automatic. Manual interaction tracking requires the collector to start and stop interactions using the traffic lights on the tool bar. The actions and action items columns are automatically filled in based on where the collector navigates within the application. Automatic interaction tracking begins as soon as a collector selects a record from Collector's Work Queue or queries a record (both are based on profiles).

Guidelines Other profile options affect how interaction history behaves. See: Set Up Oracle Additional Advanced Collections Profile Options for more information. Prerequisites

Set related interaction tracking profiles. See: Set Up Oracle Additional Advanced Collections Profile Options.

Steps 1. Using the Collections Agent responsibility, query and view a Customer in the Collections window. 2. Click the first traffic light to start the interaction. 3. Process a payment and make a note of the details of your transaction. 4. Click the second traffic light to verify actions and to end the interaction. 5. Navigate to the History tab and verify that Interaction History has this new interaction. 6. Change the profiles to automatically start the interaction. 7. In Collector's Work Queue, select a work item and click Get Work. 8. In the Collections window, note that the first traffic light is grey. 9. Process a payment and make a note of the details of your transaction. 10. Return to UWQ and select another record. 11. Navigate to the History tab and verify that the Interaction History has this new interaction. 12. To change to manual interaction tracking, change the IEX: Automatically Start Interactions profile option to No. 13. Query and view a Customer in the Collections window. Click the first traffic light to start the interaction. 14. Process a payment and make a note of the details of your transaction. 15. End the interaction. 16. Navigate to the History tab and verify that the Interaction History has this new interaction. Related Topics Implementation Verification Tasks for Mandatory Components

Implementation Verification Tasks for Optional Components

Verify the implementation of any optional components of Oracle Advanced Collections, if installed. Determine if your implementation includes any of the following optional components.

Oracle Marketing and its dependency, Oracle Discoverer Oracle Advanced Inbound Oracle Advanced Outbound

Be sure someone on your implementation team has expertise in the optional components you are implementing. Also make sure the components have been installed. Then refer to the Implementation or User Guides for each module for verification and validation steps related to each module. Related Topics Implementation Verification Tasks for Mandatory Components

Verifying Integration with Oracle Lease and Finance Management


After you have configured Oracle Advanced Collections to integrate with Oracle Lease and Finance Management, verify the following: Collections Header Confirm the following calculations and resulting data are specific to Oracle Lease and Finance Management:

Collectable transactions Delinquencies Days Sales Outstanding (DSO) Last payment due on last payment amount

Related Topics Implementation Verification Tasks for Optional Components Implementation Tasks for Mandatory Components