AR: Customer Conversion 19 Sheets Lean Specification Document

 

Data Conversion Specification

 

 

CON-005–Customer Conversion

 

 

 

 

 

Cloud Implementation

 

Author:                                  

Creation Date:                     03/01/2023

Last Updated:                      03/01/2023

Document Ref:                    CON-005

Version:                                 1.0

Document Control

Change Record

2

Date	Author	Version	Change Reference
03/01/2023		1.0	Initial Draft

 

 

Reviewers

Name	Position

 

Approvers

 

Name	Position

Document Control...................................................................................... 2

Change Record........................................................................................... 2

Reviewers.................................................................................................. 2

Approvers.................................................................................................. 2

Introduction.............................................................................................. 4

Conversion Scope, Strategy, and Assumptions.................................................. 4

Prerequisites.............................................................................................. 4

MAPPING SPECIFICATIONS........................................................................... 6

Data Extract Component Logic...................................................................... 7

Data Extraction Rules................................................................................... 8

Data Reconciliation...................................................................................... 8

Upload Component Logic............................................................................. 9

Data Flow Assumptions/ Prerequisites............................................................ 9

Open and Closed Issues............................................................................. 10

Open Issues.............................................................................................. 10

Closed Issues............................................................................................ 10

Introduction

Note:A work product document should be produced for each of the business entities being converted.  You may want to use the Subject field to indicate the business entity.

The purpose of this document is to document and communicate the configurations, data mapping, interdependency, and component design specifications for the conversion of the Party that is going to be converted to the Oracle Cloud applications, where the Master Project (MP) Contract Client will be used as the source for “Party” information, which will then be linked to an existing Oracle Customer Account.

Following Objects will be converted:

Customer, Customer Accounts, Customer Sites, Customer Sites uses, Account Contacts, Account Relationships, and Account Site Contacts

Dev/SIT/UAT/Prod cut off, extract, and load criteria defined below

Conversion Scope, Strategy, and Assumptions

The Conversion Component Designs are used by the project team as the basis for the design and construction of the Customer conversion.

High-Level Conversion Process Overview- CON-005 – Customer Conversion

The Data Migration of Oracle CON-005 – Customer data will involve the conversion of data from the Oracle R12 EBS system into Oracle ERP Fusion.

a.                The data being migrated from Oracle R12 EBS into Oracle ERP Fusion will be transformed because the source and target data structures are different.

b.                There should be a linkage between the Client and the Billing customer. In the current system, the Master project has the client information in a custom field which will be converted as the Party in Oracle cloud. The project under the master project in the current system holds the billing customer which will become the customer account under the same party in the Oracle cloud.

Prerequisites

The following setups are defined in Oracle ERP Fusion Instance to upload the Customer

·        Manage Receivables Customer Profile Classes

·        Manage Trading Community Source System

·        Manage Administrator Profile Values for HZ_GENERATE_PARTY_NUMBER

·        Add values (STMT, DUN) in PARTY_SITE_USE_CODE and SITE_USE_CODE at “Manage Trading Community Location Lookups”

·        Create DFF for ECRM ID at Party Profile level (HZ_ORGANIZATION_PROFILES)

·        Create DFF at Party site level for Site Type (HZ_PARTY_SITES)

·        Manage Business Unit Set Assignment (Customer Account Address Sets: ENTERPRISE)

·        Master project data must have been extracted and made available for Customer Data Transformation (For Party – Customer relationships)

MAPPING SPECIFICATIONS

Please find attached Rapid Template for Mapping and FBDI Template for Conversion

Data Extract Component Logic

Note:Describe the component logic for the download component(s) used to convert the entity being converted.

Bring Customer, Accounts, Sites, site use, Account Contacts, and Account Site Contacts details from existing Oracle R12 ERP to Oracle ERP Fusion

 

Below are the extraction and upload criteria

 

Sprint	Extraction Criteria	Upload Criteria
Sprint 5	All the active Customers, Customer sites & Project Clients will be extracted based on the cut-off date from EBS	15% of Total customers will be loaded in Sprint 5
Sprint 6	All the active Customers, Customer sites & Project Clients will be extracted based on the cut-off date from EBS	An additional 35% will be loaded in Sprint 6
SIT	All the active Customers, Customer sites & Project Clients will be extracted based on the cut-off date from EBS	All the customers will be loaded as part of SIT
UAT	All the active Customers, Customer sites & Project Clients will be extracted based on the cut-off date from EBS	All the customers will be loaded as part of UAT
PROD	All the active Customers, Customer sites & Project Clients will be extracted based on the cut-off date from EBS	All the customers will be loaded as part of PROD cutover based on the cut-0ff date for Production GO LIVE.

 

For Sprint5, 6, and SIT Oracle EBS 12 development instance (DOA) is used to extract the Customer's data.

Data Extraction Rules

Data is extracted from the following table  

HZ_PARTIES
HZ_PARTY_SITES
HZ_CUST_ACCOUNTS
HZ_ORIG_SYS_REFERENCES
HZ_CUST_ACCT_SITES_ALL
HZ_CUST_SITE_USES_ALL
HZ_CUST_ACCT_RELATE_ALL
HZ_CUST_ACCOUNT_ROLES
HZ_ORG_CONTACT_ROLES
HZ_CONTACT_POINTS
AR_RECEIPT_METHODS
RA_CUST_RECEIPT_METHODS
AR_RECEIPT_METHOD_ACCOUNTS_ALL
HZ_CODE_ASSIGNMENTS
HZ_ORIG_SYSTEMS_B
HZ_ROLE_RESPONSIBILITY
HZ_RELATIONSHIPS
HZ_LOCATIONS
IBY_EXT_BANK_ACCOUNTS
IBY_EXTERNAL_PAYERS_ALL
HZ_PARTY_SITE_USES
HR_ORGANIZATION_UNITS
HZ_PERSON_LANGUAGE
HZ_CUST_PROFILE_CLASSES
AR_COLLECTORS
HZ_CUSTOMER_PROFILES_M
AR_AUTOCASH_HIERARCHIES
RA_TERMS_B
AR_STATEMENT_CYCLES
RA_GROUPING_RULES
HZ_CUST_PROF_CLASS_AMTS
IBY_ACCOUNT_OWNERS

Data will be extracted using the Rapid4Cloud tool for the mentioned dates and OU.

Data Reconciliation

Customer data reconciliation will be done with the help of the OTBI report.

 

Upload Component Logic

Data will be uploaded to Cloud using Standard FBDI (19 sheets) Process

Note:Describe the component logic for the upload component(s) used to convert the entity being converted.

 

 

 

Data Flow Assumptions/ Prerequisites

Prerequisites, extraction, and upload criteria are mentioned above.

Open and Closed Issues

 

Note:Add open issues that you identify while writing or reviewing this document to the open issues section.  As you resolve issues, move them to the closed issues section and keep the issue ID the same.  Include an explanation of the resolution.

When this work product is complete, any open issues should be transferred to the project- or process-level Issue Log (Manage focus area) and managed using a project level Issue Form (Manage focus area).  In addition, the open items should remain in the open issues section of this work product, but flagged in the resolution column as being transferred.

Open Issues

 

ID	Issue	Resolution	Responsibility	Target Date	Impact Date
1	OTBI report for Customer Master Data reconciliation
2
3.
4

 

Closed Issues

 

ID	Issue	Resolution	Responsibility	Target Date	Impact Date
1
2
3.
4