OUM

AN.100 APPLICATION FUNCTIONAL DESIGN

AN100_ORACLE_TO_MICROSTRATERG
Y INTERFACE CUSTOMERS
PPM_Proposal/Request#80649
Global Object (N)
Author: Ragav Manica
Creation Date: November 6, 2014
Last Updated: July 12, 2019
Document Ref:
Version: DRAFT 1AA

Approvals:

<Approver 1>

<Approver 2>
AN.100 Doc Ref
July 12, 2019

1 DOCUMENT CONTROL
1.1 Document Naming Convention

XXSW_ GLOBAL COUNTRY CODE

SWYY_ Non Global Country Code
AA_Application Code
DD_Object Description

1.2 Change Record

2

Date Author Version Change Reference

8/05/2014 Ragav Manica Draft 1a No Previous Document
11/10/2014 Sanjeev Arya Updated Updated as per the discussion with Microstratgy
team and business
4/20/2016`` Ankur Verma Updated
07/12/2019 Caue S. Pinheiro Updated Reviewed for EMEA Wave 2 Project
10/26/2020 Tino Piazzardi Updated Added 2 extrafields according to NT2P2 RICE –
9616

1.3 Reviewers

Name Position

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2iixxi18ii

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref
July 12, 2019

Contents

1 Document Control..................................................................................................... ii
1.1 Document Naming Convention....................................................................................ii
1.2 Change Record........................................................................................................... ii
1.3 Reviewers.................................................................................................................... ii

2 Introduction............................................................................................................... 1
2.1 Current Process and Defined......................................................................................1
2.2 Business Objectives/ Proposed Solution.....................................................................1
2.3 Major Features............................................................................................................ 1
2.4 Definitions................................................................................................................... 1
2.5 Scenarios/Process flow............................................................................................... 2
2.6 Examples.................................................................................................................... 2
2.7 Business Rules/ Dependencies...................................................................................2
2.8 Assumptions................................................................................................................ 8

3 User Interface Descriptions......................................................................................9

3.1 Surface Feature Descriptions......................................................................................9
3.2 User Interface Flow Descriptions................................................................................9

4 Data and Behavior Analysis...................................................................................10

4.1 Data Analysis............................................................................................................ 10
4.2 Behavior Analysis...................................................................................................... 10

5 Interface Analysis................................................................................................... 11

6 Test Plan.................................................................................................................. 12

7 Error Handling......................................................................................................... 13

8 Issue Log................................................................................................................. 14
8.1 Open Issues.............................................................................................................. 14
8.2 Closed Issues............................................................................................................ 14

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2iiixxi18iii

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

2 INTRODUCTION

2.1 Current Process and Defined

Current process is database views for Customer, Sales Rep, Products, Location and Receivable Invoice
are provided from OBIEE.
Data pulled from OBIEE views to Netezza / MicroStrategy database.
Latest data is feed from Oracle EBS to OBIEE periodically.

2.2 Business Objectives/ Proposed Solution

Daily extract Interface needs to be built from Oracle EBS to MicroStrategy.
 Interface Includes data related to
o Customer
o Sales Rep
o Products
o Locations
o Receivable Invoice
 Daily full refresh will be provided for Customer, Sales Rep, Products and Locations
 Rolling two months data for Receivable Invoice will be provided daily.
o Open Month Data for Invoices
o AR invoice Adjustments
o Previous period data and current period data (After period close ???)
 Data will be provided in text file with pipe || as delimiter.
 All field values will be provided in full length, Netezza / MicroStrategy team to handle the field
size.

2.3 Major Features

Provide Data File
Data file needs to be provided matching the data file format requested by MicroStrategy.

2.4 Definitions

2.5 Scenarios/Process flow

Step # 1

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2121181

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

Run Concurrent Request in Oracle EBS to create criteria based data collection for Customer, Sales Rep,
Products, Locations and Receivable Invoice.
Step # 2
Transfer the data file (.txt) from Oracle EBS to Netezza Server.
Step # 3
Netezza / MicroStrategy to pick up the file.

2.6 Examples

2.7 Business Rules/ Dependencies

2.7.1 BUSINESS RULES/ DEPENDENCIES – CUSTOMERS
Customer information will be provided from all sites. Customer header information will remain common
and site level information changes based on Site (country or Operating Unit).
Customer extract has information specific to all customers in EBS. There is one row for each customer
site found in EBS.
2.7.1.1 Mapping information (Columns in Yellow needs clarifications)

COLUMN COLUMN NAME DESC REQUIRED EBS Data Mapping

INDEX
1 CUSTOMER_KEY Combination of attributes to create NO  
unique values per table
2 SOURCE Source of data YES  Hard coded ORACLE
(please refer to standardized list) APAC or ORACLE
LATAM or ORACLE
EMEA
3 ACCOUNT_NUMBER Customer/Account Number YES  Customer account
number from Header.
Refer to screen shot.
4 ACCOUNT_NAME Customer Name YES  Customer name from
Header.
Refer to screen shot.
5 ADDRESS Customer address YES Site Address
 Refer to screen shot.
6 CITY Customer city YES From Site Address
Refer to screen shot.
7 STATE Customer state YES From Site Address
Refer to screen
shot.For EMEA this is
not mandatory
8 ZIP_POSTAL_CODE Customer zip YES From Site Address
Refer to screen shot.
9 COUNTRY Customer country YES From Site Address
(please refer to the chart of Refer to screen shot.
standardized country codes)

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2221182

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

10 Holding Group Account Number

11 Holding Group Desc Party Name

12 COMMERCIAL_REGION Country Grouping NO  

(e.g. Russia + Belarus)
13 LOCAL_CUST_CAT  This is the Trade sector code and NO  This is the Trade sector
will be used in UK/IRE Diversified code and will be used
Brand. in UK/IRE Diversified
Brand.
14 LOCAL_CUST_CAT_DET  This is the Trade sector name and NO   This is the Trade
AIL will be used in UK/IRE Diversified sector name and will be
Brand. used in UK/IRE
Diversified Brand.
15 CAC_CODE Please refer to standardized list YES   This code is
maintained in a
descriptive flex field on
the customer Header.
Refer to screen shot.
For UK PM CAC code
will come from Ship-To
Site for some
customers. It is
maintained on the AR
Receivable lookup. If
the CAC group is not in
the lookup then it will
be taken from the
customer
account(Refer the
screen shots)
16 CUSTOMER_GROUP   NO  

17 CUSTOMER_INVOICE Main location the customer is billed NO  

out of
18 SALES_REP Rep territory YES From Ship to if it is
NULL then Bill To
 Refer to screen shot.
19 GLOBAL_PARENT Please refer to standardized list NO  

20 CUSTOMER_TYPE CUSTOMER or INTER-COMPANY YES From Header

(This should be in all caps)  Refer to screen shot.
Actual value is I or E
21 COMPANY   NO  
22 ACCOUNT_BRANCH Customer Site ID YES Populate using
Customer site Id

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2321183

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

23 SALES_CHANNEL DL=Dealers NA=N/A YES From Customer

DR=Direct ` SW=SW Owned Header. 
Stores Refer to screen shot.
EX=Export
WD=Distributors
HC=Home Centers ZZ=No Sales
Channel
IN=IntraCompany
24 CUSTOMER_PRIORITY   NO  This will be the
Account class DFF at
customer Account level
ATTRIBUTE1
25 CUSTOMER_PRIORITY_   NO  Description for
DESC ATTRIBUTE1

26 CUSTOMER_STATUS A=Active, D=Dead, NT=Not Trading YES From Customer

Header 
EBS value is A or I.
Refer to screen shot.
27 FORECAST_GROUP  This is will be utilized by Diversified NO   This is will be utilized
Brand UK/IRE by Diversified Brand
UK/IRE
28 ACCOUNT_OPEN_DATE Date account was opened YES For LA: From Customer
Header , Customer
Establishment date.
Refer to screen shot.
For ASIA: Customer
Creation Date will be
used
For EMEA: Customer
Establishment date.
29 LAT Latitude NO  
30 LONG Longitude NO  
31 LOAD_DATE YYYY-MM-DD HH:MM:SS EST NO  
32 CUSTOMER_ALIAS The English translation of the NO  For LA : will be ‘0’
customer name (Zero)
33 BRANCH_INVOICE   NO  

34 LOCAL_PARENT ABC attribute NO  

35 LOCAL_CAT_3   NO  

36 LOCAL_CAT_3_DETAIL   NO  

37 LOCAL_CAT_4   NO  

38 LOCAL_CAT_4_DETAIL   NO  

39 VIP_ACCOUNT Y=Yes, N=No YES Hard coded to N

40 COUNTY Customer site county YES For Mexico : County

value comes from

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2421184

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

province and others

will County
41 MAJOR_CUST_CODE Major Customer Code YES Logic (same as BO logic)
will be different for
each country
If it is unavailable or
NULL the use Customer
account number
42 MAJOR_CUST_DESC Major Customer Description YES Logic (same as BO logic)
will be different for
each country
If it is unavailable or
NULL the use Customer
account Description
43 Address_type Address Type No Values are
Bill To
Ship To
Both

44 CAC_GROUP Customer CAC Group No   This code is

maintained in a
descriptive flex field on
the customer Header.
Refer to screen shot.
For UK PM CAC Group
will come from Ship-To
Site for some
customers. It is
maintained on the AR
Receivable lookup.If
the CAC group is not in
the lookup then it will
be taken from the
customer
account(Refer the
screen shots)
45 BRANCH_NAME Customer Name No Customer Name

46 DUN_NUMBER A unique nine-digit identification Yes A unique nine-digit

number for each physical location identification number
of the business. for each physical
location of the
business.
47 PRIMARY_BRANCH Y/N FLAG NO Identification if it is
customer primary
branch
48 LEGACY_ACCOUNT_NO customer account DFF - SW LEGACY Yes
ACCOUNT NUMBER

49 LEGACY_ACCOUNT_BR account site details DFF - SW Legacy Yes

ANCH Account Branch

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2521185

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

10/26/2020[TP]: Adding 48( LEGACY_ACCOUNT_NO) & 49 (LEGACY_ACCOUNT_BRANCH) according to

NT2P2 RICE – 9616 P&L by Sales Person Revenue Report.
Information must be taken from hz_cust_acct_sites_all.orig_system_reference:

Format is IW01-99656-01, where 99656 is the LEGACY_ACCOUNT_NO and 01 is the

LEGACY_ACCOUNT_BRANCH.
We will setup Site Original System Reference Format in Lookup Table
‘XXSW_AR_SITE_ORIG_SYS_REF_FMT’ with following information:

To access the format you have to find in fnd_lookup_values table the row with lookup_type equal to
Operating Unit Name (i.e. SWSE IW OU) and language= ‘US’ then you must get the following information:
1) Attribute1: Prefix, check hz_cust_acct_sites_all.orig_system_reference start with the test included in
this column

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2621186

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

2) Attribute2: Separator, this is the characters that separated fields in

hz_cust_acct_sites_all.orig_system_reference
3) Attribute3: Column Position of LEGACY_ACCOUNT_NO value (please not that the first position must
exclude the PREFIX, in example for Value IW01-99656-01, the character separator is ‘-‘, the prefix is
‘IW’, value of first column is ‘01’, Second column is ‘99656’; account is ‘99656’, so we have to put 2
in attribute3)
4) Attribute4: Column Position of LEGACY_ACCOUNT_BRANCH value (for Value IW01-99656-01 we put 3
to get the value ‘01’)

1.1.1.1 Mapping information (Columns in Yellow needs clarifications)

Field # 3: ACCOUNT_NUMBER

Field # 4: ACCOUNT_NAME

Account address comes from the Bill To

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2721187

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

Field # 9: Field # 5:
COUNTRY ADDRESS

Field # 6: CITY
Field # 7: STATE

Field # 8: ZIP-POSTAL-
CODE

Field # 26: CUSTOMER_STATUS

Field # 44: CAC-GROUP

Field # 15: CAC-
CODE

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2821188

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

Reference to sales person

Field 18: SALES_REP

Field 28: ACCOUNT_OPEN_DATE

Field 20: CUSTOMER_TYPE

Field 23: SALES_CHANNEL

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 2921189

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

Field 22: ACCOUNT_BRANCH

Field 44: SHIP_TO_COUNTRY Field 40: SHIP_TO_ADDRESS

Field 41: SHIP_TO_CITY

Field 42: SHIP_TO_STATE

Field 43: SHIP_TO_ZIP_POSTAL_CODE

UK PM wants the CAC assignment at SHIP-TO customer site level for some customers. So in order to achieve this
requirement a Receivable lookup is created which checks If the below Description(CAC GROUP-CAC CODE) exits per
screeshot in this Lookup table for that Account-Party site(Only for SHIP_TO) combinations then print the CAC GROUP
and CAC CODE from here in MSTR else take it from Account Level.
Please Note: This can be used for other Eurpean Countries if they do CAC assignments per site

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 210211810

Sherwin-Williams Confidential - For internal use only

 AN.100 Doc Ref

Account and party site

combination seperated by -

CAC Group and CAC Code

combination seperated by -

2.8 Assumptions

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 211211811

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

3 USER INTERFACE DESCRIPTIONS

The following defines the user interface data elements.

3.1 Surface Feature Descriptions



3.2 User Interface Flow Descriptions

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 212211812

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

4 DATA AND BEHAVIOR ANALYSIS

4.1 Data Analysis

Entity (Class) Attribute (Data Minimum Value Maximum Value Default Value Comments
Field)

4.2 Behavior Analysis

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 213211813

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

5 INTERFACE ANALYSIS

The <Use Case Package Name> is dependent on the following components and external systems.

Use Case External System Messages Frequency Interface Message Parameters

Name Name, Component Requirements (data exchanged)
Name, or Service
Name

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 214211814

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

6 TEST PLAN
 Create a new sellable item in Oracle
 Update an existing sellable item in Oracle

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 215211815

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

7 ERROR HANDLING


File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 216211816

Sherwin-Williams Confidential - For internal use only

AN.100 Doc Ref

8 ISSUE LOG

8.1 Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

8.2 Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

File Ref: 503617212.docx (v. DRAFT 1A ) Issue Log 217211817

Sherwin-Williams Confidential - For internal use only