SCM: Data conversion Supplier Mapping Specification Supplier Conversion Lean Specification

 

 

Data Conversion Mapping Specification

 

 

              Supply Chain Management Data Conversion (Supplier)

 

 

 

 

 

 

VJ Implementation

 

Author:                                  

Creation Date:                     

Last Updated:                      

Document Ref:                   

Version:                                 1.0

 

Note:Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents.  When you change any of these values, be careful not to accidentally delete the bookmark.  You can make bookmarks visible by selecting Tools->Options…View and checking the Bookmarks option in the Show region.

 

Document Control

Change Record

2

Date	Author	Version	Change Reference
24-Sep-23	Sai Kumar

 

 

Reviewers

Name	Position

 

Approvers

 

Name	Position

 

 Contents

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

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

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

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

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

Conversion Scope, Strategy And Assumptions.................................................. 4

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

MAPPING SPECIFICATIONS........................................................................... 5

Data Extract Component Logic...................................................................... 6

Data Extraction Rules................................................................................... 6

Upload Component Logic............................................................................. 7

Data Flow Assumptions/ Prerequisites............................................................ 7

Open and Closed Issues............................................................................... 8

Open Issues................................................................................................ 8

Closed Issues.............................................................................................. 8

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 an individual entity that is going to be converted to the Oracle Cloud applications.

Following Objects will be converted:

Supplier (Suppliers, Supplier Addresses, Supplier Sites, Supplier Site Assignments, Supplier Contacts, Supplier Bank Accounts)

Conversion Scope, Strategy And Assumptions

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

High Level Conversion Process Overview- Supplier

a.      The Data Migration of Oracle Supplier data will involve conversion of data from CLIENT’s old legacy system into CLIENT’s new Oracle Fusion.

b.      The data being migrated from CLIENT’s old system into new system will be transformed because the source and target data structures are different.

c.      The datafile provided will be used to build the import FBDI file templates with Metadata of cate Suppliers, Supplier Addresses, Supplier Sites, Supplier Site Assignments, Supplier Contacts, Supplier Bank Accounts.

 

Prerequisites

Following configurations are required in SaaS

·        Business Unit

·        Banks and Bank Branches

 

 Oracle Fusion Customer DFF

 

NAME	TABLE COLUMN	VALUE SET	GLOBAL

  

NAVISION TO FUSION DATA FIELD MAPPING

Data conversion process involves mapping of source and destination columns which is the critical part of entire conversion process. As discussed on Supplier (Suppliers, Supplier Addresses, Supplier Sites, Supplier Site Assignments, Supplier Contacts, Supplier Bank Accounts) conversion with Videojet IT, mapping of the columns will be provided along with data in standard FBDI templates. 

 

Mapping of the columns

Navison vs Supplier FBDI Mapping.xlsx

 

Sample suppliers tested in Dev2 for data provided. 

 

                     

 

 

Standard ESS Jobs used in Supplier Conversion:  

 

1.      Load Interface File for Import

2.      Import Suppliers

3.      Import Supplier Addresses

4.      Import Supplier Contacts

5.      Import Supplier Sites

6.      Import Supplier Site Assignments

7.      Import Supplier Bank Accounts

8.      Purge Interface Tables 

Fusion Navigations:  

Data Extract Component Logic

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

Bring  Supplier and related details from existing legacy system to New Fusion

 

To bring in Supplier Data into Oracle fusion we need pre-requisites of Business Unit setup in Oracle Fusion. These will be defined manually.

 

Pool: Only Include Active Supplier

 

Supplier will have multiple FBDI Information to be loaded as Metadata to process the records into Oracle Fusion. With Metadata of Suppliers, Supplier Addresses, Supplier Sites, Supplier Site Assignments, Supplier Contacts, Supplier Bank Accounts.

 

 

 

Data Extraction Rules

 

S.no	Business Rules
01.	Supplier always created with Business Classification as Spend Authorized
02.	Supplier for all the countries in scope will be extracted in the Data File.
03.

 

 

 

CONVERSION APPROACH 

 

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

·        Extract the data and populate it in Oracle FBDI Template.  

·        Validate the Data and manually change any data as required and generate .CSV and .ZIP file from template  

·        Goto Scheduled Processes in Fusion and First Run ‘Load Interface File for Import’ for all supplier Objects and upload the .zip file. After its Successful Completion run the supplier object specific Program to transfer the data from Interface Table to Base Table.  

·        Review output log for successfully migrated records and exceptions. Correct errors and reload errored records.   

·        If errored data is to be deleted from Interface table, run the job ‘Purge Interface Tables’  

·        Repeat the Process until all the records are imported successfully.  

·        Validate the data if all columns are correctly populated.  

 

 

 

Data Flow Assumptions/ Prerequisites

The development specifications for Supplier assume the following:

Key Assumptions are:

·        The data of Supplier for all supplier objects will be provided by the CLIENT extraction team directly into FBDI templates.

·        Oracle technical team will prepare the data in the required Oracle standard FBDI formats in CSV or ZIP extracts.

·        FBDI Metadata will be build based on Suppliers, Supplier Addresses, Supplier Sites, Supplier Site Assignments, Supplier Contacts, Supplier Bank Accounts.

·        All required setups/configurations have been completed before the program is run.

·        All system level profile options have been setup.

·        Business Unit is defined.

 

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	Banks and Branches	To finalize the approach and load the data
2
3.
4

 

Closed Issues

 

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