Module Designs

MODULE DESIGNS

XXCLIENTXX Customer Care Workbench

Author: Anil Passi

Date: 21st February 2001

Document Ref: R&S/XXCLIENTXX/3000813/MD/035

Version: ISSUE 1

Note:

Document Control

Change Record1

Date Author Version Change Reference

30th Jan 01 Anil Passi Draft 1a No Previous Document14th Feb 01 Anil Passi Draft 1b Made changes after the firt review from Rob Debaes and

XXCLIENTXX Oracle Receivables end users.21st Feb 01 Anil Passi Issue 1 Ability to update data from Enquiry Workbench

Reviewers

Name Position

xxxPersonxxx Oracle Project ManagerXxxPersonxxx XXCLIENTXX Programme ManagerXxxPersonxxx XXCLIENTXX Business RepresentativeXxxPersonxxx XXCLIENTXX Business RepresentativeXxxPersonxxx Principal Consultant – Oracle

Distribution

Name Location

1 1 Library Master Project Library2 2 Project Manager3 3 4 4

Note:

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Contents

1 Overview..............................................................................................................................5

1.1 Introduction...............................................................................................................51.2 Related Documents..................................................................................................101.3 Assumptions..........................................................Error: Reference source not found1.4 Functional Overview...............................................................................................111.5 Application Set-up...................................................................................................111.6 Data Conversion......................................................................................................13

2 Module XXXARWKB – Customer Account Enquiry Workbench...................................14

2.1 Customer Account Enquiry Workbench..................................................................142.2 Customer Account Enquiry Form..................................................................142.3 Prerequisites.............................................................................................................152.4 Customer Zone........................................................................................................152.5 Turnover Zone.........................................................................................................19

3 Module XXXARSTM - Customer Statements...................................................................21

3.1 Customer Statements Window................................................................................213.2 Prerequisites.............................................................................................................213.3 Statements Zone......................................................................................................22

4 New Disputes Window ( Module XXXARSTM ).............................................................25

4.1 Create New Disputes...............................................................................................254.2 Prerequisites.............................................................................................................254.3 New Dispute Zone...................................................................................................25

5 Dispute History ( Module XXXARDSH )........................................................................27

5.1 Dispute History Window.........................................................................................275.2 Prerequisites.............................................................................................................275.3 Dispute History Zone...............................................................................................28

6 Customer Calls ( Module XXXARCCL)...........................................................................30

6.1 Customer Calls Window..........................................................................................306.2 Prerequisites.............................................................................................................306.3 Customer Calls Zone...............................................................................................31

7 Outline Test Plan................................................................................................................33

8 Technical Overview............................................................................................................35

8.1 General.....................................................................................................................358.2 Table XXX_DISPUTE_CREATION......................................................................358.3 Table XXX_DISPUTE_REFERENCES.................................................................368.4 Database Trigger XXX_DISPUTE_HISTORY_BRI.............................................368.5 View XXX_ar_open_items_v..........................................................................368.6 View XXX_ar_dispute_history_v..............................................................378.7 View XXX_ar_customer_calls_v................................................................378.8 View XXX_ra_customers_v............................................................................388.9 Package XXX_ar_customer_wb.......................................................................388.10 Configuration Items.................................................................................................398.11 Outline Installation Instructions..............................................................................40

9 Open and Closed Issues for this Deliverable......................................................................41

9.1 Open Issues..............................................................................................................419.2 Closed Issues...........................................................................................................41

10 Technical Review Comments.............................................................................................42

10.1 Draft 1A...................................................................................................................42

1 1 Overview

1.1 1.1 Introduction

This document describes modules identified in Reference 1, which together provide the following functionality:

XS001 Customer Account Enquiry

XP001 Calculate DSO

XP002 Calculate Account Balance

XP003 Calculate Turnover Last 12 Months

XP004 Calculate Turnover Previous 12 Months

XP005 Calculate Last Payment Date

XP006 Calculate Last Payment Amount

XP007 Create disputes for more than one open Receivables Items in one go.

XP008 View Closed Statements

XP009 Resolve Disputes

XP009 View Closed Disputes

XP010 Calculate Turnover for last 12 Months for each month of the year.

XP011 Calculate DSO for last 12 Months for each month of the year.

XP012 Calculate Turnover for previous 12 Months for each month of the year.

XP013 Calculate DSO for previoius 12 Months for each month of the year.

XZ001 Zoom to Standard Ageing screen

XZ002 Zoom to Custom “Customer Statements” screen

XZ003 Zoom to Custom “View Disputes” Screen

XZ004 Zoom to Custom “Customer Calls” Screen

XZ005 Ability To Create new disputes from Statements screen.

XZ006 Zoom to Std “Activities” screen from Custom “Customer Statements” screen

XZ007 Zoom to Custom “View Disputes” Screen from Custom “Customer Statements” screen

XZ008 Zoom to Oracle Receivables Customer Account Overview Screen from Workbench.

XZ009 Zoom to Oracle Receivables Customer Screen from Workbench.

XZ010 Zoom to Oracle Receivables Customer Calls Statements window from Custom Calls screen.

XZ011 Zoom to Oracle Receivables Customer Dunning letters window from Custom Calls screen.

XZ012 Zoom to Turnover/DSO window from Custom Workbench.

*

*

*

*

Module ID

Name Object Name Type and Description Where Documented

XS001 Customer Account Enquiry XXXARWKB

FORM

This screen may be queried for a customer/address to view the following information

Within this document.

Module ID


Credit Limit, Account Balance, Turnover Last 12 Months, Turnover Previous 12 Months, Payment Terms, Last Receipt Amount, Last Receipt Date, Contact Information, Risk Code

XP001 Calculate DSO XXXARWKB Workbench Screen :: To display DSO

Within this document

XP002 Calculate Account Balance XXXARWKB Workbench Screen :: To show the Account Balance for a customer invoice address in functional currency


XP003 Calculate Turnover Last 12 Months

XXXARWKB To show the Turnover in the functional currency Last 12 Months


XP004 Calculate Turnover Previous 12 Months

XXXARWKB To show the Turnover Previous 12 Months


XP005 Calculate Last Payment Date XXXARWKB Calculate Last Payment Date Within this document

XP006 Calculate Last Payment Amount

XXXARWKB Calculate Last Payment Amount


XP007 Create disputes for more than one open Receivables Items in one go.

XXXARSTM Create disputes for more than one open Receivables Items in on go.


XP008 View Closed Statements XXXARSTM Users should be able to view both closed and open statements for a given customer address


XP009 Resolve Disputes XXXARDSH Users should be able to resolve disputes from the disputes history screen


XP009 View Closed Disputes XXXARDSH Users should be able to view both open and closed disputes


XZ001 Zoom to Standard Ageing screen

ARXCWMAI Zoom to Standard Ageing screen from Customer Workbench


XZ002 Zoom to Custom “Customer Statements” screen

XXXARSTM Zoom to Custom “Customer Statements” screen from Customer Workbench


XZ003 Zoom to Custom “View Disputes” Screen

XXXARDSH Zoom to Custom “View Disputes” Screen from Customer Workbench


XZ004 Zoom to Custom “Customer XXXARCCL Zoom to Custom “Customer Within this

Module ID


Calls” Screen Calls” Screen document

XZ005 Ability To Create new disputes from Statements screen.

XXXARSTM Selection of various transactions for the creation of dispute


XZ006 Zoom to Std “Activities” screen from Custom “Customer Statements” screen

ARXCWMAI Zoom to standard Activities Screen


XZ007 Zoom to Custom “View Disputes” Screen from Custom “Customer Statements” screen

XXXARDSH Zoom to Custom “View Disputes” Screen from Custom “Customer Statements” screen


XP010 Calculate Turnover for last 12 Months for each month of the year.

XXXARWKB Calculate Turnover for last 12 Months for each month of the year.

Within This Document

XP011 Calculate DSO for last 12 Months for each month of the year.

XXXARWKB Calculate DSO for last 12 Months for each month of the year.


XP012 Calculate Turnover for previous 12 Months for each month of the year.

XXXARWKB Calculate Turnover for previous 12 Months for each month of the year.


XP013 Calculate DSO for previous 12 Months for each month of the year.

XXXARWKB Calculate DSO for previous 12 Months for each month of the year.


XZ008 Zoom to Oracle Receivables Customer Account Overview Screen from Workbench.

ARXCWMAI Zoom to Oracle Receivables Customer Account Overview Screen from Workbench.


XZ009 Zoom to Oracle Receivables Customer Screen from Workbench.

ARXCUDCI Zoom to Oracle Receivables Customer Screen from Workbench.


XZ010 * Zoom to Oracle Receivables Customer Calls Statements window from Custom Calls screen.

ARXCWMAI Zoom to Oracle Receivables Customer Calls Statements window from Custom Calls screen.


XZ011 * Zoom to Oracle Receivables Customer Dunning letters window from Custom Calls screen.

ARXCWMAI Zoom to Oracle Receivables Customer Dunning letters window from Custom Calls screen.


XZ012 Zoom to Turnover/DSO window from Custom Workbench.

XXXARWKB Zoom to Turnover/DSO window from Custom Workbench.


The following context diagram illustrates the way that modules are invoked and communicate with one another:

1.2 1.2 Related Documents

R&S/XXCLIENTXX/201225/PRP/006

Cash & Debt Management, a proposal document for Receivables extensions

1.3 1.3 Assumptions

This design assumes that the following statements are true:

The users need an ability to view Open Receivables Items across all the branches within a given operating unit.A user from one branch should have the ability to place on dispute an invoice, which belongs to some other branch within the same Operating Unit.

XXCLIENTXX to maintain the setup of Receivables System option for DSO calculation. This system option is known as “Days in Days Sales Outstanding Calculation”.

Users will not be able to update the disputes once they are created. But they will have an ability to resolve the dispute and re-create a new dispute for the given transaction.

XXCLIENTXX will be provided with a Descriptive Flex Field at customer address level for them to be able to maintain comments for customer addresses.

Customer calls once saved can not be updated except for their notes.

Customer Call topic notes will no longer be stored in Descriptive flexfields as were being done by XXCLIENTXX in Release10.7. The new custom screen will store these as standard receivables notes (in the standard tables)

Account balance displayed in the workbench will include the Receivables Items which are due in the future as well. This effectively means that a invoice with due date six months down the line will also be included in the account balance calculation.

It is assumed here that Turnover here means the sum of “Original Due Amount” for the customer in the given date range, with adjustment’s appplied. “Not Postable To GL” type Receivables transactions will be excluded from the calculations. The turnover value will be calculated in the functional currency.

The turnover amounts will be calculated for the calendar years and not for the financial year.

DSO (Days Sales Outstanding) will be calculated based on the Oracle Receivable’s definition of DSO.

* DSO will be calculated as :

*

*

Its assumed that the “Creation Date” in the Addresses Zone ( Menu : Help/About This Record) will be the date on which the customer address was originally created. It will be XXCLIENTXX’s responsibility to ensure that “Creation Date” is not the date on which customer info was migrated into the system. “Creation Date” will be displayed as the “Date Operational” in customer workbench screen.

Customer Calls will not be transaction specific.

Customer calls will created from Custom screen will always remain as Open Calls, since there is no requirement to be able to Close calls from the custom call screen.

Customer calls will be non-updateable, except for their notes. Customer Call Id will not be displayed in the Custom screen. It is XXCLIENTXX’s responsibility to ensure that any custom reports that use the four call topic descriptive segments in Release 10.7, use the text recorded in the Notes tables in Release 11.03.

Amount in dispute will be calculated as Sum of Disputed amount. For example if a invoice worth £100 is under dispute along with a credit memo worth £80 then amount in dispute will be £20 and not £180.

A Descriptive Flex Field segment named “Primary Contact” will be provided to identify primary contact for a customer address. Oracle will run a script at install time to update the latest of the contacts for each address as primary. XXCLIENTXX may toggle this Descriptive Flex Field to alter the primary contact for a customer address. In case more than one contact is primary then any one of these will be displayed in the Enquiry Workbench.

It will be XXCLIENTXX’s responsibility to maintain the Dispute Reason Codes for XXX look type “DISPUTE_REASON”. Oracle can load the Dispute Reasons provided XXCLIENTXX provides with a list of Valid Dispute Reasons.

It is assumed that it is acceptable for up to 4% of the notes recorded in the four DFF segments to lose the characters after the 240th position as a result of concatenating all four segments together. Descriptive Flex Field at customer call topics will still be usable for referencial purposes.

There will be no Query Find functionality implemented, instead the users will be able to Enter-Query and execute query for all the Queryable fields. It is assumed that queries will mostly be performed on Customer Name, Customer Number, Address String, Original Reference.

Last Receipt Amount and Last Receipt Date will include both Applied and UnApplied receipts.

The profile option “XXX Allow Update From AR Workbench” will allow/disallow the users, making updates from Receivables Workbench. If this profile is not set for a given user it will be assumed that the user is denied from updating Receivables Workbench.

Transactions in the Statements screen will be sorted by Transaction Date in ascending order.

*

1.4 1.4 Functional Overview

* The proposed solution is to Develop Custom Extensions to Oracle Receivables that is already implemented. This is to allow easy visualisation of a Customer’s Status, and the ability to drill down to a Customer’s Aged Debt, Statement, Calls and Disputes.

* This functionality will provide simple means of placing disputes and resolving disputes.The Aged screen used will be the standard Ageing screen of Oracle Receivables. It will be possible to view open/closed statements and disputes.

*

1.5 1.5 Application Set-up

Following Descriptive Flex Field Segments will be created

These Descriptive Flex Field will be created at install time

1. 1. In the Customer Address zone of the Define Customer screen a single segment descriptive flexfield will appear for the user to enter an optional free text comment.

2. 2. In the Contact zone of the Define Customer screen a single segment descriptive flexfield will appear for the user to enter an optional Yes/No flag to indicate if this is the primary contact for the address.

Entries will be added to Receivables Quick Code “CUSTOMER_RESPONSE_REASON”.These lookups will be created during install time. The following Customer Response QuickCodes will automatically be seeded. These were originally values used in the XXCLIENTXX Query Type segment of the Call Topics information descriptive flexfield in Release 10.7.

Ensure that field “Days in Days Sales Outstanding Calculation” in screen “Define System Options” is assigned appropriate value.

Assign values to XXX Lookup for Dispute Reason Codes, where look type is “DISPUTE_REASON”.

Create a profile option XXX_UPDATE_FROM_AR_WORKBENCH

Follow the steps indicated below to create this profile

Responsibiltiy :: Application Developer

Menu :: /Profile

Name => XXX_UPDATE_FROM_AR_WORKBENCH

Application => XXCLIENTXX Hire Module

User Profile Name => XXX Allow Update From AR Workbench

SQL Validation =>

SQL="SELECT meaning \"Allow Update\",

lookup_code

INTO :VISIBLE_OPTION_VALUE,

:PROFILE_OPTION_VALUE

FROM as_lookups

WHERE lookup_type = 'FLAG'

ORDER BY meaning"

COLUMN="\"Allow Update\"(*)"

User Access

Visible => Yes, Updateable=> No

System Administrator Access

Visible Updateable

Site Yes Yes

Lookup Code MeaningPRICE QUERY Price QueryO/N UNKNOWN Order Number UnknownPOD REQUIRED Signed POD RequiredDISPUTED OEA Disputed OeaDISPUTED CFD Disputed CfdTRANSPORT CHARGE QUERY Transport Charge QueryHIRE DATE QUERY On/Off Hire Date QueryINCORRECT ACCOUNT Incorrect Account Credit ReinvoiceEQUIPMENT OFF HIRED Equipment ReturnedWRONG EQUIPMENT Wrong Equipment SuppliedUNKNOWN DELIVERY ADDRESS Unknown Delivery AddressDUPLICATE INVOICE Duplicate Invoice

Application Yes Yes

Responsibility Yes Yes

User Yes Yes

1.6 1.6 Data Conversion

The descriptive FlexField “Call Topic Information” will be made redundant with the new functionality. Oracle will provide with a install script to migrate Notes1,Notes2, Notes3, Notes 4 to Standard Receivables Notes table ( ar_notes). Entries in Descriptive Flex Field Segment “Query Type” will be migrated to column “Reason Code” of Customer Call Topics table.

The data held in the four call topic descriptive flexfield segments will automatically be migrated as Customer Notes when this solution is installed. Only the first 240 characters of the four segments concatenated together will be migrated. The Query Type segment will be migrated to the Reason Code for the Customer Call Topic to which the Notes will belong.

2 2 Module XXXARWKB – Customer Account Enquiry Workbench

2.1 2.1 Customer Account Enquiry Workbench

This form will display all the desbt management information for the customers. Values will be displayed in the functional currency for the given responsibility.

Note:

2.2 2.2 Customer Account Enquiry Form

2.3 2.3 Prerequisites

Before you can use this form you must perform the following:

Maintain the comments for customer addresses in the address level Descriptive Flex Field.

* Menu :: /Customers/Standard

* Zone :: Customer Addresses Zone

Ensure that appropriate contact has been marked as primary contact for the customer address.

* Menu :: /Customers/Standard

* Zone :: Contacts Zone at Customer Addresses level

2.4 2.4 Customer Zone

2.4.1 2.4.1 Customer Number (Display Only, Query Allowed = Yes)

The Customer Number

2.4.2 2.4.2 Customer Name (Display Only, Query Allowed = Yes)

The Customer Name

2.4.3 2.4.3 Address (Display Only, Query Allowed = Yes)

The Customer Invoice Address

2.4.4 2.4.4 Original Reference (Display Only, Query Allowed = Yes)

Original reference for the customer address.

2.4.5 2.4.5 Send Statements (Query Allowed = Yes, Update = Yes)

The checkbox to indicate if stamtements are sent to this customer. This checkbox can be updated only if the profile “XXX Allow Update From AR Workbench” equals Yes.

2.4.6 2.4.6 Send Letters (Query Allowed = Yes, Update = Yes)

The checkbox to indicate if dunning letters are sent to this customer. This checkbox can be updated only if the profile “XXX Allow Update From AR Workbench” equals Yes.

2.4.7 2.4.7 Avg Days Late (Display Only, Query Allowed = Yes)

Average number of days for late payment.

2.4.8 2.4.8 Credit Limit (Display Only, Query Allowed = No)

The Customer Invoice Address Overall Credit Limit in the functional currency

2.4.9 2.4.9 Account Balance (Display Only, Query Allowed = No)

The Customer Invoice Address Account Balance in the functional currency. Account balance will also include open Receivables Items, which are due in future.

2.4.10 2.4.10 Contact Name (Display Only, Query Allowed = No)

Name of the contact for Customer Address. If no contact exists for customer address then contact info from the customer header will be shown if available.

2.4.11 2.4.11 Telephone (Display Only, Query Allowed = No)

Telephone Number of the contact for Customer Address. If no contact exists for customer address then contact info from the customer header will be shown if available.

2.4.12 2.4.12 Fax (Display Only, Query Allowed = No)

Fax Number of the contact for Customer Address. If no contact exists for customer address then contact info from the customer header will be shown if available.

2.4.13 2.4.13 Email (Display Only, Query Allowed = No)

Email Address of the contact for Customer Address. If no contact exists for customer address then contact info from the customer header will be shown if available.

2.4.14 2.4.14 Trading Status (Query Allowed = No, Update = Yes)

This will be the Account Status of Customer Address. This can be setup in APPS for customer addresses from Standard Customer entry screen. This field can be updated only if the profile “XXX Allow Update From AR Workbench” equals Yes.

2.4.15 2.4.15 Credit Controller (Display Only, Query Allowed = Yes)

This will be the Credit Controller for given customer address. This can be setup in APPS for customer addresses from Standard Customer entry screen.

2.4.16 2.4.16 Payment Terms (Display Only, Query Allowed = Yes)

Terms assigned to the invoice to address. If no payment terms assigned to the adddress then the payment terms at customer level will be shown.

2.4.17 2.4.17 Date Operational (Display Only, Query Allowed = Yes)

The date on which the customer address was created.

2.4.18 2.4.18 Risk Code (Display Only, Query Allowed = No)

This will be the risk code assigned to the customer profile.

2.4.19 2.4.19 Last Receipt Amount (Display Only, Query Allowed = No)

This is the latest receipt ( applied / unapplied ) amount against the customer address in the functional currency.

2.4.20 2.4.20 Last Receipt Date (Display Only, Query Allowed = No)

This is the latest receipt ( applied / unapplied ) date against the customer address in the functional currency.

2.4.21 2.4.21 DSO (Display Only, Query Allowed = No)

DSO displayed as number of days worth of outstanding balance against the customer address.

2.4.22 2.4.22 Comments (Display Only, Query Allowed = Yes)

This is the comment entered in the Comment segment of the Address Information descriptive flexfield.

2.4.23 2.4.23 Aged (Button)

Navigates to the Receivables Ageing screen.

2.4.24 2.4.24 Statement (Button)

Navigates to the Custom Statements Screen.

2.4.25 2.4.25 Turnover (Button)

Navigates to the Turnover/DSO window.

2.4.26 2.4.26 Account Overview (Button)

Navigates to the Standard Receivables Account Overview Screen.

2.4.27 2.4.27 Customer (Button)

Navigates to the Standard Receivables Customer Screen. This button will be enabled only if the profile “XXX Allow Update From AR Workbench” equals Yes.

2.4.28 2.4.28 Dispute History (Button)

Navigates to the Dispute History Screen.

2.5 2.5 Turnover Zone

2.5.1 2.5.1 Current Month Turnover (Display Only, Query Allowed = No)

Current month turnover for the customer address.

2.5.2 2.5.2 Current Month DSO (Display Only, Query Allowed = No)

Current month DSO for the customer address.

2.5.3 2.5.3 Mon-YYYY (Display Only, Query Allowed = No)

Month.

2.5.4 2.5.4 Turnover (Display Only, Query Allowed = No)

Turnover for Month.

2.5.5 2.5.5 DSO (Display Only, Query Allowed = No)

DSO for month.

2.5.6 2.5.6 Total Turnover Last Year (Display Only, Query Allowed = No)

Total Turnover for the last year.

2.5.7 2.5.7 Total Turnover PreviousYear (Display Only, Query Allowed = No)

Total Turnover for the previous year.

3 3 Module XXXARSTM - Customer StatementsThis screen will display all the open Receivables items for the given customer address. It will be possible to view the closed items as well by clicking on the button “View Closed Items”. Disputes can be created for various open items by selecting the checkbox.

3.1 3.1 Customer Statements Window


None

3.3 3.3 Statements Zone


Customer Number.


Customer Name.

3.3.3 3.3.3 Date (Display Only, Query Allowed = Yes)

Transaction Date.

3.3.4 3.3.4 Number (Display Only, Query Allowed = Yes)

Transaction Number.

3.3.5 3.3.5 PO (Display Only, Query Allowed = Yes)

Customer Purchase Order Number.

3.3.6 3.3.6 Class (Display Only, Query Allowed = Yes)

This is the transaction class of the transaction. These will be one of the following :: Guarantee, Invoice, Receipt, Chargeback, Credit Memo, Deposit, Debit Memo, Adjustment, Chargeback, Credit Memo, Deposit, Debit Memo, Guarantee, Invoice, Payment.

3.3.7 3.3.7 Due Date (Display Only, Query Allowed = Yes)

Due Date for the given transaction.

3.3.8 3.3.8 Original Amount (Display Only, Query Allowed = Yes)

Original Amount in the transaction currency.

3.3.9 3.3.9 Balance (Display Only, Query Allowed = Yes)

Current Balance in the transaction currency.

3.3.10 3.3.10 Comments (Display Only, Query Allowed = Yes)

Comments recorded against the receipts. For transactions other than receipts this field will be blank.

3.3.11 3.3.11 Type (Display Only, Query Allowed = Yes)

Transaction Type for the current transaction.

3.3.12 3.3.12 Currency (Display Only, Query Allowed = Yes)

Transaction Currency.

3.3.13 3.3.13 Cumulative Balance (Display Only, Query Allowed = No)

Cumulative balance calculated as the user scrolls across the records. This value will change as and when records are scrolled upwards or downwards.

3.3.14 3.3.14 Total Balance (Display Only, Query Allowed = No)

Total balance for the Customer Address in functional currency.

3.3.15 3.3.15 Create Dispute (Updateable, Query Allowed = No, Default=UnChecked,Optional)

To create dispute, check this checkbox for disputed transactions and click the “New Dispute” button. This checkbox will be disabled for transactions that are already under dispute and also for the transactions which have been closed. The colour of this field will be indicative of the dispute status for transaction. Green => Never Under Dispute, Blue => Closed Dispute Exists. Red => Currently Under Dispute.

3.3.16 3.3.16 Dispute Date (Display Only, Query Allowed = Yes)

The latest dispute date for the transaction.

3.3.1 3.3.1 View Closed Items (Button)

Closed items will be displayed when this button is clicked. The label of this button will toggle to “View Open Items” when its initially pressed.

3.3.2 3.3.2 Activities (Button)

Makes call to the standard Receivables Activities screen.

3.3.3 3.3.3 Details (Button)

Navigates to the standard account details Screen.

3.3.4 3.3.4 New Dispute (Button)

Navigates to the Custom “New Dispute” window, to create disputes for the selected transactions.

3.3.5 3.3.5 Dispute History (Button)

Navigates to the Custom “Dispute History” window, to view open and resolved disputes for customer address. This button should also be pressed when users intend to resolve disputes with a customer.

3.3.6 3.3.6 Call (Button)

Navigates to the Customer Calls screen.

4 4 New Disputes Window ( Module XXXARSTM )Use this functionality to create new disputes for customers.

4.1 4.1 Create New Disputes


At least one open transaction should be selected for disputes in Customer Statements window.

4.3 4.3 New Dispute Zone

4.3.1 4.3.1 Customer Number ( Display Only, Query Allowed = No)

Customer Number

4.3.2 4.3.2 Customer Name ( Display Only, Query Allowed = No)

Customer Name

4.3.3 4.3.3 Date ( Display Only, Query Allowed = No)

Dispute creation date.

4.3.4 4.3.4 Reference ( Display Only, Query Allowed = No)

Reference Number for the disputes being created.

4.3.5 4.3.5 Dispute Reason (Enterable, Required, Query Allowed = No)

Lists the valid dispute reasons from XXX Lookups “DISPUTE_REASON”

4.3.6 4.3.6 Note ( Enterable, Required, Query Allowed = No)

Note explaining the circumstances and other details of the dispute.

4.3.7 4.3.7 Confirm ( Button)

Confirms the operation and creates the disputes. After dispute creation users will be Prompted with a message “Do you wish to log a Call?”. Accordingly users will be navigated to Customer Calls Screen or the Customer Statements screen.

4.3.8 4.3.8 Cancel ( Button)

Cancels the operations and no new dispute is created.

5 5 Dispute History ( Module XXXARDSH )Use this screen to view the existing open disputes and resolved disputes against a customer address.

This screen also gives the ability to resolve the open disputes.

5.1 5.1 Dispute History Window


There should be existing disputes against the customer.

5.3 5.3 Dispute History Zone


Cusomer Number


Cusomer Name

5.3.3 5.3.3 Dispute Status (Display Only, Query Allowed = Yes)

Shows the dispute status, which is either Open or Resolved

5.3.4 5.3.4 Date (Display Only, Query Allowed = Yes)

Transaction Date for the transaction under dispute

5.3.5 5.3.5 Number (Display Only, Query Allowed = Yes)

Transaction Number, which was placed under dispute.

5.3.6 5.3.6 Remove From Dispute(Default,Checkbox,Conditional, Query Allowed = No)

Default value of this checkbox will be unchecked. Select the disputes to be resolved using this checkbox. This checkbox will be disabled for Resolved disputes.

5.3.7 5.3.7 Reason (Display Only, Query Allowed = Yes)

Reason for which transaction was placed under dispute.

5.3.8 5.3.8 Type (Display Only, Query Allowed = Yes)

Receivables transaction type.

5.3.9 5.3.9 Reference (Display Only, Query Allowed = Yes)

Dispute Reference Number.

5.3.10 5.3.10 Notes (Display Only, Query Allowed = Yes)

Dispute Notes.

5.3.11 5.3.11 View Closed Disputes (Button)

View Closed/Resolved Disputes for the customer address.

5.3.12 5.3.12 Confirm (Button)

Confirm the action to resolve selected disputes.

5.3.13 5.3.13 Dispute Total (Button)

Total open/closed dispute amount in the functional currency.

6 6 Customer Calls ( Module XXXARCCL)Use this screen to create customer calls. This screen will replace the 3 Std apps screen for logging customer calls.

6.1 6.1 Customer Calls Window


Customer Address should be setup in Receivables.

6.3 6.3 Customer Calls Zone


Customer Number


Customer Name

6.3.3 6.3.3 Collector (Enterable, Update=No,Mandatory=Yes, Default = Yes, Query Allowed = Yes)

This will be defaulted from the customer profiles. Select a valid Collector Name.

6.3.4 6.3.4 Date (Enterable, Update=No,Mandatory=Yes, Default = Yes, Query Allowed = Yes)

Date on which the Call is created.

6.3.5 6.3.5 Contact (Enterable, Update=No,Mandatory=Yes, Default = Yes, Query Allowed = Yes)

This will be defaulted to the Primary contact of the Customer address. Select a valid Contact Name.

6.3.6 6.3.6 Call Type (Enterable, Update=No,Mandatory=Yes, Default = No, Query Allowed = Yes)

The Call Type. Select a valid response reason as defined in Receivables QuickCode Screen. (Lookup Type = CUSTOMER_RESPONSE_REASON)

6.3.7 6.3.7 Text (Required, Default = No, Query Allowed = Yes)

Note for the current customer call.

6.3.8 6.3.8 Note (Required, Default = No, Query Allowed = Yes)

Multi Line Note, a mirror of the Text field.

6.3.9 6.3.9 Statements (Button)

Navigates to Customer Call Statements window.

6.3.10 6.3.10 Dunning Letters (Button)

Navigates to Customer Dunning Letters window.

6.3.11 6.3.11 Customer Enquiry (Button)

Closes the Customer Call screen and navigates back to Customer Enquiry Screen.

7 7 Outline Test PlanIn order to test this module, the following types of test should be run:

Type of Test Details e.g. data to be used

Check the account balance, DSO Create sales order, ship and run auto-invoice. Create RMA’s, receipt and run auto-invoice.Interface Receivables to GL.

Check Account Balance Create a receipt against a invoice.Check Account Balance Reverse the receipt applied to the invoiceCheck the account balance, DSO Create manual invoices and credit

memo’s, confirm the invoice.Test DSO Amount Apply A receipt to a outstanding invoice.

The DSO should reduce in proportion to the amount and “DSO Days”

Test DSO Amount Change the System SetUp “DSO Days”. The value of DSO must change in accordance.

Test the Contact information Toggle the primary flag of Descriptive Flex Field segment for Customer Contacts.

Test the Collector, Credit Limit for Customer Address

Change these setups at the customer level.

Test Risk Code and Trading Status Change the Setup for Risk Code and Trading Status in Customer Setup.

Test Last Receipt Date and Last Receipt Amount

Enter a Applied/UnApplied receipt against the customer address.

Test Dispute creation Create a disputes selecting more than one transaction.Navigate to the Dispute History Screen and examinefor the disputes listed. Run the following reportsDisputed Invoice Report XXCLIENTXX Disputed Invoice Report XXCLIENTXX Disputed Invoice Report - Grouped By Branch XXCLIENTXX Disputed Invoice Report - Grouped By Collector These should list the disputes created. Please note that in order to print the dispute reference, dispute reason and dispute notes, these reports will need o be customized.

Test Dispute Removal Navigate to the Dispute History Screen. Resolve the disputes by selecting the “Remove From Dispute” checkbox. Click on “View Closed Disputes”. The disputes resolved should be brought back in the screen.

Type of Test Details e.g. data to be used

Run the following reportsDisputed Invoice Report XXCLIENTXX Disputed Invoice Report XXCLIENTXX Disputed Invoice Report - Grouped By Branch XXCLIENTXX Disputed Invoice Report - Grouped By Collector These reports should list no longer list the disputes created in the prior test run.

Test “View Closed Items” functionality in Customer Statement screen

Close the invoice by applying receipts. This invoice should be listed in Customer Statements screen with “Status = Closed”

Test Customer Calls Create customer calls. Run the “Collector Call History” report.The calls created must be printed along with their notes.

8 8 Technical OverviewThis section contains technical notes to guide the person building the program e.g. tables to be accessed, templates and techniques to be used.

8.1 8.1 General

8.1.1 8.1.1 Design Methodology

Where possbile standard tables will be used in the design. This will reduce the programming effort and will allow XXCLIENTXX to use the standard APPS reports where possible.

We are replacing the 3 Customer Calls windows of standard Receivables APPS by a single Customer Calls screen. The idea is the populate the Receivables tables behind the scenes from this Custom screen. Hence following tables will be populated behind the scenes

AR_CALL_ACTIONS (ACTION_CODE will be defaulted to ‘ACTION’ )

AR_CUSTOMER_CALLS_ALL

AR_CUSTOMER_CALL_TOPICS_ALL

To create a log of dispute activity we will create two tables XXX_DISPUTE_REFERENCES and XXX_DISPUTE_CREATION. These tables will be non-multiorg, because standard APPS table ar_dispute_history is non-multiorg’ed as well.

AR_PAYMENT_SCHEDULES has a standard database trigger( ar_payment_schedules_bru ) which fires off when amount_in_dispute column is populated. In order to avoid modifying this trigger we will create a Custom database trigger i.e. XXX_dispute_history_bi on XXX_dispute_history.

8.2 8.2 Table XXX_DISPUTE_CREATION

This table will hold the reference to AR_DISPUTE_HISTORY and XXX_DISPUTE_REFERENCES.

COLUMN NAME DATA TYPEDISPUTE_CREATION_ID NUMBERDISPUTE_HISTORY_ID NUMBERDISPUTE_REFERENCE_ID NUMBERCREATED_BY NUMBERCREATION_DATE DATELAST_UPDATED_BY NUMBERLAST_UPDATE_DATE DATELAST_UPDATE_LOGIN NUMBER

8.3 8.3 Table XXX_DISPUTE_REFERENCES

This table will hold the reference to Notes, reasons and dispute reference number.

COLUMN NAME DATA TYPEDISPUTE_REFERENCE_ID NUMBERREASON_CODE VARCHAR2NOTE VARCHAR2REFERENCE VARCHAR2CREATED_BY NUMBERCREATION_DATE DATELAST_UPDATED_BY NUMBERLAST_UPDATE_DATE DATELAST_UPDATE_LOGIN NUMBER

8.4 8.4 Database Trigger XXX_DISPUTE_HISTORY_BRI

This trigger inserts record into XXX_dispute_creation

It fires before insert on ar_dispute_history

8.5 8.5 View XXX_ar_open_items_v

This view acts as a base table to “Customer Statements Screen” XXXARSTM

COLUMN NAME DATA TYPETRX_DATE DATETRX_NUMBER VARCHAR2CT_PURCHASE_ORDER VARCHAR2AL_CLASS_MEANING VARCHAR2DUE_DATE DATEAMOUNT_DUE_ORIGINAL NUMBERAMOUNT_DUE_REMAINING NUMBERAL_STATUS_MEANING VARCHAR2TYPE_NAME VARCHAR2CREATE_DISPUTE VARCHAR2DISPUTE_DATE DATEINVOICE_CURRENCY_CODE VARCHAR2RAC_CUSTOMER_NUMBER VARCHAR2RAC_CUSTOMER_NAME VARCHAR2CUSTOMER_SITE_USE_ID NUMBERCUSTOMER_ID NUMBER

8.6 8.6 View XXX_ar_dispute_history_v

This view acts as a base table to “Dispute History Screen” XXXARDSH

COLUMN NAME DATA TYPE

RAC_CUSTOMER_NUMBER VARCHAR2RAC_CUSTOMER_NAME VARCHAR2ROW_ID CHARAMOUNT_IN_DISPUTE NUMBERUNDER_DISPUTE_FLAG VARCHAR2DISPUTE_STATUS VARCHAR2TRX_DATE DATETRX_NUMBER VARCHAR2REASON_CODE_DSP VARCHAR2REASON_CODE VARCHAR2NOTES VARCHAR2TYPE_NAME VARCHAR2DISPUTE_REFERENCE VARCHAR2REMOVE_DISPUTE CHARCUSTOMER_SITE_USE_ID NUMBERCUSTOMER_ID NUMBERPAYMENT_SCHEDULE_ID NUMBER

8.7 8.7 View XXX_ar_customer_calls_v

This view acts as a base table to “Customer Calls Screen” XXXARCCL

COLUMN NAME DATA TYPEACO_NAME VARCHAR2CCT_CALL_DATE DATECCT_SITE_USE_ID NUMBERCONTACT_NAME VARCHAR2CUSTOMER_NAME VARCHAR2CUSTOMER_NUMBER VARCHAR2CUSTOMER_CALL_ID NUMBERLAST_UPDATED_BY NUMBERLAST_UPDATE_DATE DATELAST_UPDATE_LOGIN NUMBERCREATED_BY NUMBERCREATION_DATE DATE

CUSTOMER_ID NUMBERCOLLECTOR_ID NUMBERCALL_DATE DATESITE_USE_ID NUMBERREASON_CODE VARCHAR2CURRENCY_CODE VARCHAR2ORG_ID NUMBERROW_ID ROWIDCCT_CUSTOMER_CALL_TOPIC_ID NUMBERCCT_CUSTOMER_TRX_ID NUMBERANO_TEXT VARCHAR2CCT_COLLECTOR_ID NUMBER

8.8 8.8 View XXX_ra_customers_v

This view acts as a base table to “CustomerDebt Management Workbench” XXXARWKB

COLUMN NAME DATA TYPECUSTOMER_NAME VARCHAR2CUSTOMER_NUMBER VARCHAR2CUSTOMER_ID NUMBERADDRESS_ID NUMBERSITE_USE_ID NUMBERCOLLECTOR_ID NUMBERCONTACT_NAME VARCHAR2CONTACT_EMAIL VARCHAR2CONTACT_FAX VARCHAR2CONTACT_TELEPHONE VARCHAR2COLLECTOR_NAME VARCHAR2RISK_CODE VARCHAR2COMMENTS VARCHAR2DATE_OPERATIONAL DATEPAYMENT_TERMS VARCHAR2TRADING_STATUS VARCHAR2ADDRESS VARCHAR2

8.9 8.9 Package XXX_ar_customer_wb

This package provides bussiness functions for this Custom Receivables functionality. FUNCTION CHECK_DISPUTE_SELECTED RETURNS BOOLEAN Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_BILL_SITE_USE_ID NUMBER(38) IN P_REQUEST_ID NUMBER(38) IN* PROCEDURE CREATE_DISPUTES Argument Name Type In/Out Default?

------------------------------ ----------------------- ------ -------- P_BILL_SITE_USE_ID NUMBER(38) IN P_REQUEST_ID NUMBER(38) IN P_REASON_CODE VARCHAR2 IN P_NOTES VARCHAR2 IN FUNCTION GET_ACCOUNT_BALANCE RETURNS NUMBER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_BILL_SITE_USE_ID NUMBER(38) IN FUNCTION GET_ADDRESS_CREDIT_LIMIT RETURNS VARCHAR2 Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_BILL_SITE_USE_ID NUMBER(38) IN FUNCTION GET_CONTACT_NAME RETURNS VARCHAR2 Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_CUSTOMER_ID NUMBER(38) IN P_ADDRESS_ID NUMBER(38) IN PROCEDURE GET_CUSTOMER_NAME_TYPE Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_CUSTOMER_ID NUMBER(38) IN P_CUSTOMER_NAME VARCHAR2 OUT P_CUSTOMER_NUMBER VARCHAR2 OUT P_CUSTOMER_TYPE VARCHAR2 OUT FUNCTION GET_DISPUTED_AMOUNT RETURNS NUMBER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_BILL_SITE_USE_ID NUMBER(38) IN FUNCTION GET_EMAIL RETURNS VARCHAR2 FUNCTION GET_FAX RETURNS VARCHAR2 FUNCTION GET_LATEST_RECEIPT_AMOUNT RETURNS NUMBER Argument Name Type In/Out Default? ------------------------------ ----------------------- ------ -------- P_CUSTOMER_ID NUMBER(38) IN P_BILL_SITE_USE_ID NUMBER(38) IN FUNCTION GET_LATEST_RECEIPT_DATE RETURNS DATE FUNCTION GET_TELEPHONE RETURNS VARCHAR2

8.10 8.10 Configuration Items

This section lists all the Software Configuration Items that will be produced by this customisation. This list will also be replicated in the ‘Software Registry’ worksheet in the ‘MD050 Control’ spreadsheet.

Configuration Item Short Name

Program Name Installed Location Program Language

XXXAR000 Receivables Debt Management

- Pre-Installation$XXX_TOP/install/bin Unix Bourne Shell

XXXAR001 Receivables Debt Management – Database Storage Objects

$XXX_TOP/install/sql Oracle SQL*Plus

XXXAR002 Receivables Debt Management - Views, Grants and Synonyms to Universal Schema


XXXAR003 Receivables Debt Management – Package Specification For table Handlers


XXXAR013 Receivables Debt Management – Package Body For Table Handlers


XXXAR015 Receivables Debt Management - Seed Data and Data Conversion


XXXAR203 Receivables Debt Management Package Specifications


XXXAR233 Receivables Debt Management View Definitions


XXXAR253 Receivables Debt Management Package Body


XXXAR035 Debt Management – Descriptive Flexfields


XXXAR009 Debt Management - Post-Installation

$XXX_TOP/install/bin Unix Bourne Shell

XXXARWKB Receivables Customer Enquiry Workbench

$XXX_TOP/$APPLFRM Oracle Forms

XXXARCCL Customer Calls $XXX_TOP/$APPLFRM Oracle FormsXXXARDSH Dispute History $XXX_TOP/$APPLFRM Oracle FormsXXXARSTM Customer Statements $XXX_TOP/$APPLFRM Oracle Forms

8.11 8.11 Outline Installation Instructions

8.11.1 8.11.1 Manual Pre-Installation Steps

None.

8.11.2 8.11.2 Installation Steps

The following steps will be performed in the order specified.

1. 1. Copy Configuration Items listed above to the Installed Location specified above.

2. 2. Run the Function Group Install Program.

XAFBA000 XXX_TOP OR APPS <Apps PWD> XXX XXX <XXX PWD> OE OE <OE PWD> XXXTABS XXXINDS

3. 3. Verify the Installation.

9 9 Open and Closed Issues for this Deliverable

Note:

9.1 9.1 Open Issues

Module ID Issue Resolution Responsibility Target Date Impact Date

9.2 9.2 Closed Issues

Module ID

Issue Resolution Responsibility Target Date Impact Date

10 10 Technical Review Comments

10.1 10.1 Draft 1A

Outcome: please delete one of the following to indicate your choice

ACCEPTED (provided comments on this form are addressed)

NOT ACCEPTED (wish to re-review once all review comments have been actioned)

Page/

Ref

Comment Action (this section to be completed by Author to indicate action taken to address each review comment)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Module Designs

Documents

Transcript of Module Designs