MD050 Customer Conversion Functional Design v2.5

AIM
MD.050 APPLICATION
EXTENSIONS FUNCTIONAL
DESIGN
RAI GmbH - OU Royal
Appliance International GmbH
HZ Customer Conversion
Author:
Graeme Gerber
Creation Date:
June 21, 2013
Last Updated:
June 21, 2013
Document Ref:
Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion
Version:
2.5
Approvals:
Ulrike Berger
Vertice Project Manager
Sharon Flynn
RAI Conversion Manager
Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion
MD.050 Application Extensions Functional Design

June 21, 2013
Document Control
Change Record
3
Date
Author
Versio
n
Change Reference
21-Jun-13
Graeme Gerber
Draft
1a
Draft1c
No Previous Document
2.5
(Final)
Update for posting to project library.

Close issues, document changes & check
spelling.
20-Aug12
5-Sep-12
10-Dec12
-Include Examples, Customer Creation Process

steps. This assumes one customer account per
unique billing ILN.
-Salesrep & Territory mapping.
Update issue list.
Include Technical Overview.
Reviewers
Name
Position
Roxana Macovschi
RAI Project Manager
Distribution
Copy
No.
Name
Location
1
2
3
4
Library Master
Project Library
Project Manager
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.
File Ref: 273560178.doc
Document Control
Company Confidential - For internal use only
iv

June 21, 2013
If you receive a hard copy of this document, please write your name on
the front cover, for document control purposes.
Document Control
iv

June 21, 2013
Contents
Document Control.......................................................................................ii
Topical Essay...............................................................................................1
Basic Business Needs............................................................................1
Major Features.......................................................................................1
Definitions............................................................................................. 1
User Procedures....................................................................................3
Examples...............................................................................................3
Business Rules......................................................................................7
Assumptions..........................................................................................7
Century Date Compliance.....................................................................8
When to Run the Program.....................................................................8
Launch Parameters................................................................................9
Log Output............................................................................................9
Restart Procedures..............................................................................10
Technical Overview...................................................................................11
Open and Closed Issues for this Deliverable.............................................12
Open Issues......................................................................................... 12
Closed Issues.......................................................................................12
Document Control
iv

June 21, 2013
Topical Essay
Customer Conversion allows you to transform extracted data into Oracles
Customer Standard (entity) using AR Customer Interface along with
Trading Community Architecture (TCA) Application Programme Interface
(API).
Customer Conversion contains:
VAX CSV SQL*Loader to Temp. Table concurrent program
VAX HZ Customer Conversion concurrent program
Basic Business Needs

Customer Conversion provides you with the features you need to satisfy
the following basic business needs. You will be able to address the
following:
Convert customer data in a given comma separated (CSV) format.
See Customer Data_final.xlsx below.
Major Features
Import customer data from a CSV spreadsheet.
Customer data may be imported into Oracle where a CSV file is provided
in the given format.
Oracles link to original system reference.
All converted Oracle SHIP_TO sites have a unique legacy customer
account number in the Oracle original system reference field.
All BILL_TO sites have a unique billing ILN, or a unique street address
reference from the original customer data. These bill-to sites are related
to the above ship-to both in the provided spreadsheet data & in Oracle.
Definitions
Parties, Customers & Customer Accounts
Copied from TCAAPI.pdf, Trading Community Architecture,
Customer Interface and TCA API in Oracle Receivables (11i)
TCA
Trading Community Architecture (TCA) is an architecture concept
designed to support complex trading communities. The goal of TCA is to
Document Control
iv

June 21, 2013
provide a shared data foundation for Oracle ERP, CRM, and eBusiness
applications.
RACUST
Customer Interface is a concurrent program that is responsible for the
import and update of AR customer information from open interface tables
to AR Customer tables.
HZ
Prefix used to distinguish 11i Customer Model objects using TCA such as
tables, views, and APIs from previous customer model objects such as
those used within R10.7, and R11.
PARTY
A party is an entity that can enter into a business relationship and can be
of two sub types; Person and Organization.
PERSON PARTY
A person party is a unique individual of interest to the owner of the
software.
ORGANIZATION PARTY
An organization party is a legal entity generally recognized by some
government authority.
RELATIONSHIP
Relationships in TCA allow for the linking of any two parties. When two
parties are connected via a party relationship a relationship type is
assigned which describes the relationship.
ACCOUNT
An account is the financial roll-up point to track the monitory portion of a
customers purchases and payments. This account stores details about a
customer relationship between a Party and your business. When a party
becomes a customer (through creation in the AR customer screen,
registering on iStore, creating a quote, placing an order etc), an account is
created and associated to the party to track the attributes of the customer
relationship. A Party may have one or more Accounts. Each account may
have only one owner, but any number of other parties may also be
associated to the account in roles other than owner.
ACCOUNT ROLE
The account role defines the relationship that a Party has in regard to
controlling or using an account.
ACCOUNT SITE
Document Control
iv

June 21, 2013
The account site is a Party Site that is used within the context of a
Customer Account.
ACCOUNT RELATIONSHIPS
Implies financial responsibility between owners of accounts.
CONTACT POINT
Contact points store electronic methods of communicating with an entity
(e.g., phone, fax number, email address, URL etc.). A contact points is
connected to a party or a party site, and there can be from one to many
contact points specified for a Party or Party Site.
LOCATION
The location record in TCA is point in geographical space, usually
described by an address.
PARTY SITE
The party site establishes the link between a Party and a Location.
PARTY SITE USAGE
Describes the usage of that Location (e.g., mailing address, billing
address, home address, etc.). A Party Site may have one to many uses
User Procedures
In order to import customer data into Oracle e-Business Suite, you must
perform the following steps:
Collect customer data in the example CSV format.
Transfer the data file to the server.
Run customer Receivables request VAX HZ Customer Conversion
Each of these steps is described in more detail below.
Upload data file to the server.
The file may be transferred via SCP or SFTP.
Run concurrent programme VAX HZ Customer Conversion
Navigation: RAI DE Receivables Super User View Requests Submit
new request VAX HZ Customer Conversion. Enter the file location &/or
customer name for process. If file location parameter is null then the
existing file is used. If customer name is null then all customers are
processed.
Document Control
iv

June 21, 2013
Examples
Customer Data_final.xlsx
Customer
Data_final_ILNs_v2_GG.xlsx
Pilot Customers - VAXDEV2, version 2.

Globus Fachmrkte
Document Control
iv

June 21, 2013
Globus Handelshof St. Wendel
Document Control
iv

June 21, 2013
Customer Creation Process

Background: In the spreadsheet we have a (non normalized) table of
customers with billing details matched to delivery details. In Oracle
these bill & deliver to details are considered as BILL_TO & SHIP_TO
sites.
In Oracle the following steps are programmed to create a customer:
1. Enter party or Billing Customer Name 1 (spreadsheet col. O).
2. Customer Account
Requires: Party Name, Account Description & Number.

Logic: Group by Billing Customer Name 1 (spreadsheet
col. O), ILN Billing Number (col. S), & Customer Number
(col. A).
Example Account: Globus Handelshof St. Wendel,
GmbH & Co.KG Betr. Wachau 4308597000004, &
18119.
Note:
Document Control
iv

June 21, 2013
There may be more than one Account per Party.
ILN Billing Number is unique for the grouping.
Billing Customer Name 2 (col. P) & Billing ILN are

combined to form Oracle Account Description in
the Customer Standard form.
Result: Account creation.
3. Physical Location
Requires: BILL_TO - Billing Street (col. Q), Post Code / Town (col.
R), & Land or country code (col. T).
Result: Location creation.
4. Party Site
Requires: Party & Location.
Result: Links Party & Location to form Party Site.
Note: many party sites may share one location.
5. Account Site
Requires: Customer Account & Party Site.
Result: Account Site.
6. Site Use (BILL_TO)
Requires: Account Site & Site Purpose or BILL_TO code. From

the customer data file we map Key Account (col. E) to Primary
Sales Rep.; Sales Territory maps to file Country of Address (col.
T segment1) & Region (col. G segment2).
Result: Assigns site purpose to Account Site & derives Territory

flexfield along with Primary SalesRep.
7. For each ship to Physical Location
Requires: SHIP_TO Delivery Address; Street, Post Code, Town.

No country is provided so billing address country is used for
now.
Note: There may be many ship or delivery addresses per bill to.
8. Party Site (as above).

9. Account Site (as above).
Document Control
iv

June 21, 2013
a. If ILN is duplicated then append dupl & account number then

reprocess.
10. Site Use (SHIP_TO).
Business Rules
File Processing
-
File column Customer Name 1 (col15) is grouped to form unique

Party Name.
Account & BILL_TO. Data file ILN-NumberBilling Adress maps to an

unique Oracle customer account with a primary bill to. If the ILNNumberBilling Adress is null then we use billing Street address.
E.g. ILN 4308596000005, note that only the 13 digit number
4308596000005 is used.
SHIP_TO sites. File Customer or column one maps to the unique

interface reference of Oracle ship to. E.g. D18121
The max of (data file) Street & Town address is used along with the
above grouping.
Ship to country equals assigned bill to country as no ship to country is

given.
Assumptions
This design assumes that the following statements are true:
The customer data file may be transferred to the server. For
examples we shall us the /usr/tmp directory folder.
When to Run the Program

VAX HZ Customer Conversion is run to optionally load the data file &
process customer conversion. The programme may also be run for one
customer.
Navigation: RAI DE Receivables Super User Menu: View Requests
Submit a new request.
Document Control
iv

June 21, 2013
Launch Parameters
Example parameters for the VAX HZ Customer Conversion concurrent
program:
-
Party Name: Globus Handelshof St. Wendel

o
If party name is null then all customers are processed.
File Location: /usr/tmp/Customer_Data.csv

o
If file location is null then the existing temporary table data is

used.
Log Output
The log output consists of:
**Starts**21-AUG-2012 09:14:45
**Ends**21-AUG-2012 09:14:47
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
***************************
Party Account Log
x_cust_account_id: 3054
x_account_number: D18130
x_party_id: 4048
x_party_number: 2027
Document Control
iv

June 21, 2013
x_profile_id: 4027
x_return_status: S
x_msg_count: 0
x_msg_data:
***************************
***************************
Create Location Log
x_location_id: 4185
x_return_status: S
x_msg_count: 0
x_msg_data:
***************************
***************************
Create Party Site Log
x_party_site_id: 7183
x_party_site_number: 3080
x_return_status: S
x_msg_count: 0
x_msg_data:
***************************
***************************
Create Account Site Log
x_cust_acct_site_id: 4285
x_return_status: S
x_msg_count: 0
x_msg_data:
***************************
***************************
Create Site Use Log
x_site_use_id: 4468
x_return_status: S
x_msg_count: 0
x_msg_data: 0
***************************
Restart Procedures
Restart procedures for VAX HZ Customer Conversion concurrent program
are as follows:
Reprocess the request the programme is intelligent in that it will
check for already created entities before creating new ones.
Document Control
iv

June 21, 2013
Technical Overview
Summary
Objects:
Concurrent programme VAX HZ Customer Conversion.
Package xxvax_hz_customer_conversion is called from the above

concurrent request.
Bridging table XXVAX_TEMP_TABLE is used to store the file data for

processing by the above package.
Generic SQL*Loader control file XXVAXCSV.ctl is used to load the above

bridging table.
Concurrent programme XXVAX CSV SQL*Loader to Temp. Table is a

generic request which simply loads a CSV file using the above control
file.
Install script install_XXVAX_HZ_CUST_CONV.sh is a shell script which

installs all the above objects on the server & configures the concurrent
request set up automatically.
Document Control
iv

June 21, 2013
Open and Closed Issues for this Deliverable

Open Issues
ID
Issue
Resolution
Responsibility
Target Date
Impact
Date
Impact
Date
Closed Issues
ID
Issue
Resolution
Responsibility
Target Date
2.
Q. Which name should

appear on customer
facing documentation?
E.g. Invoices, Orders, etc.
Globus Fachmrkte Bill
To ILN correction.
A. Party Name.
Ulrike, Sharon,
Graeme
20-Aug-12
Data cleanup.
Ulrike, Sharon,
Graeme
Ulrike, Sharon,
Graeme
3.
4.
5.
7.
9.
10.
Globus Handelshof St.

Wendel discuss search
functionality for sites.
No country exists for
delivery address use
billing address country.
Reprocessing logic
required.
Charcter set conversion
should be UTF-8
Salesreps in the file
should match the
-Create a customer account for

each unique BILL_TO ILN.
-Users may search on account
description for customer name2.
Is this correct?
Sharon.
Code reprocessing steps.
Graeme.
Save as UTF-8
11/9: Successfully tested in MIG.
Graeme
Change the file or change the

values in the system.
G, 18/9>> Complete
(MIG)
20-Aug-12
Document Control
iv

June 21, 2013
ID
Issue
Resolution
Responsibility
Target Date
Impact
Date
system.
11.
12.
14.
15.
1.
6.
8.
13.
16.
17.
G, 18/9> Complete
RAI Preisliste
Price lists should be

configured & the generic
price list name provided.
G, 18/9>>Complete
Sales territory - we
should capture each
distinct combination from
the file so that an id.
Exists in the system.
G, 18/9> Complete
Add Order Type of DE

German Order &
Warehouse of Neuss to
Order Management tab.
G, 18/9> Complete
AR System Options. Auto

site numbering needs to
be turned on & auto
customer numbering
turned off.
Using file COL15 or billing
Customer Name1 as
Oracles customer name
has the following issues:
-Null columns Oracle
customer name is
mandatory.
-Where speeling mistakes
exist then these will be
imported as such.
EDI & Customer Group
(Sage) attributes are
required in customer
extract data.
Payment Terms are
required.
Data cleanup.
18/9, GG>> Use customer
account number where customer
name is missing; & missing
street where no street address is
provided.
Update post conversion.
Business Marian/Nicole, Rec.

(In progress)
Data extract.
Sharon.
(In progress)
Graeme.
VAT numbers no API

exists. Check Oracles
seeded Customer
Interface programme for
VAT functionality.
Alternatively temps will
need to capture this.
21/9: Map delivery site
name2 to party site
alternate name
Factoring site DFF (Y/N)
Business
(In progress)
To clarify / to do.
Update post conversion.
Document Control
iv

MD050 Customer Conversion Functional Design v2.5

Uploaded by

Document Information

Original Description:

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

MD050 Customer Conversion Functional Design v2.5

Uploaded by

Copyright:

Available Formats

AIM

June 21, 2013

June 21, 2013

Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

Vertice Project Manager

RAI Conversion Manager

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Update for posting to project library.

-Include Examples, Customer Creation Process

RAI Project Manager

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Basic Business Needs

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Pilot Customers - VAXDEV2, version 2.

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Globus Handelshof St. Wendel

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Customer Creation Process

Requires: Party Name, Account Description & Number.

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

There may be more than one Account per Party.

ILN Billing Number is unique for the grouping.

Billing Customer Name 2 (col. P) & Billing ILN are

Result: Account creation.

Result: Location creation.

Requires: Party & Location.

Result: Links Party & Location to form Party Site.

Note: many party sites may share one location.

Requires: Customer Account & Party Site.

Result: Account Site.

6. Site Use (BILL_TO)

Requires: Account Site & Site Purpose or BILL_TO code. From

Result: Assigns site purpose to Account Site & derives Territory

7. For each ship to Physical Location

Requires: SHIP_TO Delivery Address; Street, Post Code, Town.

8. Party Site (as above).

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

a. If ILN is duplicated then append dupl & account number then

File column Customer Name 1 (col15) is grouped to form unique

Account & BILL_TO. Data file ILN-NumberBilling Adress maps to an

SHIP_TO sites. File Customer or column one maps to the unique

Ship to country equals assigned bill to country as no ship to country is

When to Run the Program

Doc Ref: Dropbox\PSM2\41_WS 1 - Data\20_MD 50 for data conversion

MD.050 Application Extensions Functional Design

Party Name: Globus Handelshof St. Wendel

If party name is null then all customers are processed.