Manage Parties and Customer Accounts

Manage Parties and
Customer Accounts
Copyright 2007, Oracle. All rights reserved.
Objectives
After completing this module, you should be able to do
the following:
Define the features that let you enter and maintain
party and customer account information
Create profile classes and assign them to customer
accounts
Create and maintain party and customer account
information
Merge parties and customer accounts
Enable customer account relationships
Define TCA party paying relationships
View party and customer account information
Define setup options
1-2
Agenda
1-3
Describing Party Model and Features

Using Profile Classes
Entering Party Information
Merging Parties and Customer Accounts
Defining Customer Account Relationships
Defining TCA Party Paying Relationships
Reviewing Information
Defining Setup Options
Customer Overview
A customer is an organization or person with whom
you have a selling relationship. This selling
relationship can result from the purchase of products
and services or from the negotiation of terms and
conditions that provide the basis for future purchases.
For example, a division of Vision Distribution could
become one of your customers.
1-4
Party Model Overview
Receivables
Order Management
Customers set
of pages
Projects
Party Interface
tables
Party
Master
Party Model Tables
1-5
CRM
Party
merge
Party Model
PARTY
Bill to
Ship to
SITE
Bill to
Bill to
Ship to
Bill to, Ship to
Bill to, Ship to
Account
Site
Site
Account
Acct
Site
Acct
Account
Acct
Ship to
1-6
SITE
PARTY
SITE
PARTY
Division Of
Bill to, Ship to
Party Model and Relationships

Models inter- and intra-company relationships
Supports party-defined relationships
Phone Company *
Marla
(Customer)
Employee of
Business
World
Spouse of
John
(Customer)
Related to
Digital Image
Corporation
* Company implementing E-Business Suite

1-7
Managing Parties
Create customer
account profile
classes
Review party
information
1-8
Enter party
information
Assign profile
classes to customer
account
Eliminate duplicate
information
Create
relationships
Party Sites
Allow multiple organizations or parties to do business

at one location
Are global (not specific to operating units)
Allow you to perform address validation using
validation rules
Have flexible address formatting with seeded and
custom formats
1-9
Customer Accounts
Selected Party level attributes
PARTY
SITE
Ship to
SITE
Bill to
Ship to
Bill to, Ship to
Bill to, Ship to
Account
Site
Site
Account
Acct
Site
Account
Acct
Ship to
Acct
SITE
Division Of
Bill to
1 - 10
Bill to
PARTY
Name
Street address
Parent/subsidiary relationships
Industrial classifications
DUNS number (D&B)
External credit ratings
Taxpayer ID
PARTY
Bill to, Ship to
Selected Account
level attributes
Payment terms
Billing preferences
Shipping preferences
Internal credit rating
Integrating Party Information

Oracle
Order Management
Owned by
Oracle Receivables
Shared with
Oracle Projects
Trading
Community
Architecture
(TCA)
1 - 11
Oracle CRM suite
Agenda
1 - 12

Profile Classes
Poor Credit
Good Credit
Cash on Delivery
High Risk Credit Classification
Monthly Statements
Net 30
Semiannual Credit Review Cycle
Monthly Statements
Net 90
No Credit Check
Quarterly Statements
Excellent Credit
1 - 13
Profile Class Characteristics
1 - 14
Credit/
Collections
Invoices and
Statements
Credit check
Credit Analyst
and Collector
Payment
application
Dunning letters
Late Charges
Invoice line
and tax printing
Statement cycle
Billing cycle
Balance Forward
Bills
Payment
Promptness
Payment terms
Discounts
Grace days
Managing Customer Account Profiles
Poor Credit
Cash on Delivery
High Risk Credit Classification
Monthly Statements
Good Credit
Net 30
Semiannual Credit Review Cycle
Monthly Statements
Excellent Credit
1 - 15
Net 90
No Credit Check
Quarterly Statements
Setting Up a Late Charge Policy

in Profile Classes
Adjustment
Set the charge methods

Assign the type of charge
Enter calculation details
Late Charges
Debit Memo
Interest Invoice
1 - 16
Updating Profile Classes
There are three options after making a change to a

profile class:
Do not update existing profiles
Update all profiles
Update all non-customized profiles
Net 60
250,000 Credit Limit
Monthly Statements
Good Credit
1 - 17
Reviewing Profile Class Changes
All profiles
updated
Non-customized
profiles updated
Concurrent Program:
Customer Profile Copy
1 - 18
Agenda
1 - 19

Review Information
Data Quality Management Overview
The Data Quality Management (DQM) feature lets you:

Perform advanced searches for parties and
customer accounts with user-defined criteria
Prevent duplicate entries by determining if the
customer that you are creating or updating is a
potential duplicate of an existing customer
1 - 20
Data Quality Management (DQM)

DQM lets you:
Search your party information for possible
duplicates or matches to your input values
Apply threshold scores or filter conditions to
evaluate the results of a search
Identify existing duplicate entries in the TCA party
registry
Prevent the entry of duplicates into the TCA party
registry
1 - 21
How Does DQM Work?
TCA
Registry
Input Record
or Run a duplicate
identification
process
1 - 22
Cleanse &
Standardize
Staged
Schemas
Cleanse
data
Apply Match
Rule
Potential
Matches
Setting UP DQM
To set up DQM:
1. Define attributes and transformations
2. Generate the staged schema and interMedia indexes
3. Optionally define match rules
4. Compile all match rules
5. Synchronize the staged schema with the TCA registry
6. Set DQM related profile options
1 - 23
Entry Methods
Import from other systems
Customer
interface
Bulk
Import
Enter Party
information
TCA
Registry
Customers set
of pages
Enter a new customer directly from

the Sales Order window
1 - 24
Business Issues
CORP
corp
Corporation
Naming Conventions
Classifications for Pricing and

Reporting
Bill To
Ship To
Bill To
Ship To
Automatic or Manual
Numbering
Payment of Unrelated
Transactions
Bill To
Ship To
Ship To
Centralized or Decentralized Address Structures

1 - 25
Business Purposes
Each address can have multiple business purposes
Ship-to site
Ship-to site
Statements
Bill-to site
Marketing
Dunning
Legal
1 - 26
Multiple Sites and Business Purposes:

Centralized Example
ABC, Inc. is completely centralized, and its
headquarters handles all payment procedures
New York
Headquarters
Bill-to
Statements
Dunning
1 - 27
Paris
Ship-to
Marketing
Washington, D.C.
Ship-to
Chicago
Ship-to
Multiple Sites and Business Purposes:

Decentralized Example
XYZ, Inc. is completely decentralized, and each site
handles its own payment procedures
New York
Headquarters
Ship-to
Bill-to
Statements
Dunning
1 - 28
Paris
Ship-to
Bill-to
Statements
Dunning
Marketing
Washington, D.C.
Ship-to
Bill-to
Statements
Dunning
Chicago
Ship-to
Bill-to
Statements
Dunning
Importing Data Using Interface Tables
External
Databases
Temporary
Interface Tables
Oracle
Receivables
Customer Tables
Correct errors
with SQL*Plus
Customer Interface
Execution Report
1 - 29
Entering Data Using the Customers Set of Pages

Search Before
Creating
Customers or
Customer
Accounts
Match
Found
Create Customer
Create a New
Address
Y
Create Account
Customer
Add
Account
Customer
Details
Add
Account
Create Account Site
Create an Account
by Creating an
Account Site
Create an Account
Site Using an
Existing Address
Create a New
Address
Account Details
Add Account
site
Account
Account Overview
Business Purpose Details
Details
Account Site Account Site Details
Details
Account Site Overview
Business Purpose Details
Business Purpose
1 - 30
Account
Add Account
Site
Customer Overview
Create an Account
Using an Existing
Party Site
Create an Account
Site by Creating an
Address
Prevention of
Duplication and Invalid Address Creation
Receivables lets you prevent the creation of:
Duplicate Customers
Duplicate Addresses
Duplicate Contacts
Invalid Addresses
1 - 31
Dun & Bradstreet (D&B) Integration
Search the D&B database for information about

businesses, including proprietorships
Request investigations of businesses not in the
D&B database
Purchase standard data sets or a standard report
image
Request initial or updated data sets and reports
over the Internet:
Online for a single business
Batch process for multiple businesses
Compare D&B data and user-entered data

1 - 32
D&B Online
Query your database to determine if it already

contains D&B data for a party
Decide if the D&B data in your database is
sufficient and current
Query the D&B database to determine if data for
the requested business is available from D&B
Request investigation of business, if data is not
available from D&B database
Request download of data, if data is available from
D&B database
1 - 33
D&B Batch Loading

The batch process includes five steps:
D&B
Generate list
of parties
Transfer request
list to D&B
Run the Load D&B

Data program
1 - 34
Receive formatted
file from D&B
Run SQL*Loader
(D&B Import Adapter)
Agenda
1 - 35

Merge Parties or Customer Accounts
AT&T
American
Telephone
AT&T
Montreal
London
Merge parties or customer accounts to:

Eliminate incorrect data and duplicate information
Consolidate site data
Reflect party or customer account changes due to
business consolidation
1 - 36
Agenda
1 - 37

Customer Account Relationships
Parent
Parent
Reciprocal
Parent
Nonreciprocal
B
A
1 - 38
Child
Agenda
1 - 39

Oracle Trading Community Architecture
Oracle Trading Community Architecture (TCA)

Administration tab provides a single access to the setup
and administration functionality for various TCA features
1 - 40
TCA Registry
TCA is a model for maintaining complex information about

the parties and customers who belong to your commercial
community, including organizations, locations, and the
network of hierarchical relationships among them.
PARTIES
Person
1 - 41
Organization
Group
TCA Administration
Each subtab under the Administration tab contains specific

administration functionality
ADMINISTRATION
Data Quality
Management (DQM)
Relationships
Classifications
1 - 42
Source Systems
Security
Using Party Paying Relationships
You can create and manage relationships between

parties using Oracle Trading Community Architecture
Relationship Manager.
The party relationships that are used by Receivables
for various payment-related functions are called party
paying relationships.
1 - 43
Using Customer Account Relationships
Customer account relationships also provide this type of

access.
Customer account relationships, however, build only flat
hierarchies that can be difficult to maintain when multiple
parties are involved.
1 - 44
Using Party Paying and Customer Account

Relationships
Receivables considers both types of relationships
during the following activities:
Applying receipts, including:
Manual receipts, Mass Apply receipts, QuickCash
receipts, and Lockbox receipts
Applying invoices against commitments and bills

receivable
Adjusting or crediting transactions
Entering the paying customer for a transaction in
the Transactions workbench
Creating automatic receipts (via the paying
customer that you specified in the Transactions
workbench)
1 - 45
Creating Party Paying Relationships

The relationship type that you use to create a party
paying relationship must meet these two requirements:
The relationship type must be hierarchical, and the
subject and object parties must be of type
Organization
The relationship type must be assigned to one of
these relationship groups:
Pay Within
Pay Below
1 - 46
Pay Within Paying Relationships

If you assign one phrase of a relationship type to the
Pay Within relationship group, then relationships that
you create using that relationship type are Pay Within
This means that any party within the relationship can
pay for the accounts of any other party within the
relationship.
1 - 47
Party Paying Relationships Process Flow
ACME USA
ACME Worldwide
ACME England
Account
Account
Account
ACME West
INV
INV
Account
INV
1 - 48
Pay Below Paying Relationships

If you assign one phrase of a relationship type to the
Pay Below relationship group, then relationships that
you create using that relationship type are Pay Below
A Pay Below paying relationship is a parent-child
relationship, where each party can pay for its own
transactions, as well as the transactions of all parties
that are lower in the hierarchy (children, grandchildren,
and so on).
1 - 49
Relationship Types and

Relationship Groups
For party paying relationships, you should not assign the
same relationship type to both the Pay Within and Pay
Below relationship groups, because Receivables will
recognize only the Pay Within group.
1 - 50
Agenda
1 - 51

Review party and customer account data

online
Search party and customer account

information
Generate reports
1 - 52
Reports
Customer Listing Detail/Summary

Customer Profiles Report
Customer Relationships Listing
1 - 53
Agenda
1 - 54

Mandatory Customer Profile Setup Steps
The following setup steps are mandatory for

implementing customer profile classes:
Collectors
Payment Terms
1 - 55
Collectors
Collectors are used in:

Customer Profile Classes window
Customers set of pages
1 - 56
Payment Terms
Payment
Schedule
% of
Discount
Allowed
Credit Check
Check box
1 - 57
Optional Customer Profile Setup Steps
Some setup steps may be helpful to define prior to

implementing Customer Profile Classes:
Customer Profile Lookups
Statement Cycles
Balance Forward Billing Cycles
AutoCash Rule Sets
Grouping Rules
Credit Classifications
1 - 58
Setup Steps for Customers
The following setup steps are required for

implementing customers:
System Options
Profile Options
Profile Classes
1 - 59
System Options Related to Customers
Some key system options related to Customers:

Automatic Customer Numbering
Automatic Site Numbering
Create Reciprocal Customer
Grouping Rule Name
Allow Change to Printed Transactions
Allow Payment of Unrelated Transactions
1 - 60
Profile Options
Some key profile options related to Customers:

AR: Change Customer on Transaction
AR: Customers - Enter Alternate Fields
HZ: Display D&B button in Customer form
HZ: Enable DQM Party Search
Default Country
1 - 61
Optional Setup Steps for Customers
Some setup steps may be helpful to define prior to

implementing Customers:
Customer Lookups
Customer Bank Accounts
Receipt Methods
Customer Payment Details
Flexible Address Style
1 - 62
Flexible Address Formatting
19 Kew Gardens Road

Kew, Surrey
TW9 4RW
England
29 Long Road
Wheaton, IL
60187
1 - 63
Summary
In this module, you should have learned how to:
Define the features that let you enter and maintain
party and customer account information
Create profile classes and assign them to customer
accounts
Create and maintain party and customer account
information
Merge parties and customer accounts
Enable customer account relationships
Define TCA party paying relationships
View party and customer account information
Define setup options
1 - 64

Manage Parties and Customer Accounts

Uploaded by

Copyright:

Available Formats

Manage Parties and Customer Accounts

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manage Parties and Customer Accounts

Uploaded by

Copyright:

Available Formats

Manage Parties and

Copyright 2007, Oracle. All rights reserved.

Copyright 2007, Oracle. All rights reserved.

Describing Party Model and Features

Copyright 2007, Oracle. All rights reserved.

Copyright 2007, Oracle. All rights reserved.

Party Model Overview

Copyright 2007, Oracle. All rights reserved.

Bill to, Ship to

Bill to, Ship to

Bill to, Ship to

Copyright 2007, Oracle. All rights reserved.

Party Model and Relationships

* Company implementing E-Business Suite

Copyright 2007, Oracle. All rights reserved.

Allow multiple organizations or parties to do business

Copyright 2007, Oracle. All rights reserved.

Bill to, Ship to

Bill to, Ship to

Bill to, Ship to

Copyright 2007, Oracle. All rights reserved.

Integrating Party Information

Oracle CRM suite

Copyright 2007, Oracle. All rights reserved.

Describing Party Model and Features

Copyright 2007, Oracle. All rights reserved.

Copyright 2007, Oracle. All rights reserved.

Profile Class Characteristics

Copyright 2007, Oracle. All rights reserved.

Managing Customer Account Profiles

Copyright 2007, Oracle. All rights reserved.

Setting Up a Late Charge Policy

Set the charge methods

Copyright 2007, Oracle. All rights reserved.

Updating Profile Classes

There are three options after making a change to a

Copyright 2007, Oracle. All rights reserved.

Reviewing Profile Class Changes

Copyright 2007, Oracle. All rights reserved.

Describing Party Model and Features

Copyright 2007, Oracle. All rights reserved.

Data Quality Management Overview

The Data Quality Management (DQM) feature lets you:

Copyright 2007, Oracle. All rights reserved.

Data Quality Management (DQM)

Copyright 2007, Oracle. All rights reserved.

How Does DQM Work?

Copyright 2007, Oracle. All rights reserved.

Copyright 2007, Oracle. All rights reserved.

Enter a new customer directly from

Copyright 2007, Oracle. All rights reserved.

Classifications for Pricing and

Centralized or Decentralized Address Structures

Copyright 2007, Oracle. All rights reserved.

Each address can have multiple business purposes

Copyright 2007, Oracle. All rights reserved.

Multiple Sites and Business Purposes:

Copyright 2007, Oracle. All rights reserved.

Multiple Sites and Business Purposes: