Supply Chain Management Data Conversion (Item Catalog & Category) Lean Specification

 

 

Data Conversion Mapping Specification

 

 

              Supply Chain Management Data Conversion

 (Item Catalog & Category)

 

 

 

 

 

Author:                                  

Creation Date:                     28^th August 2023

Last Updated:                      04^th September 2023

Document Ref:                   

Version:                                 0.1

 

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
04-Sept-23		0.2

 

 

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

NAVISION/EBS TO FUSION DATA FIELD MAPPING............................................ 5

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

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

Conversion Approach.................................................................................. 7

Fusion Navigation....................................................................................... 8

 

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

Open and Closed Issues............................................................................. 11

Open Issues.............................................................................................. 11

Closed Issues............................................................................................ 11

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:

Item Catalog & Category

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 Item Catalog & Category conversion.

High Level Conversion Process Overview- Item Catalog & Category

a.      The Data Migration of Oracle Item Catalog & Category 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 catalog & category details.

Prerequisites

Following configurations are required in SaaS.

 

S.no	Task Name	Status	Comments
01.	Catalogs needs to be defined	Completed

 

 

 

Navision/ebs 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 catalog & category conversion with Videojet IT and Business, mapping of the columns will be provided along with data in standard FBDI template.

 

 

Sample Data provided by Videojet Team in FBDI template

 

Data Extract Component Logic

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

Bring  Catalog, Category and related details from existing legacy system to New Fusion

 

To bring in category Data into Oracle fusion we need pre-requisites of Item catalog in Oracle Fusion. Catalogs will be defined manually or as part of separate conversions.

 

Category will have multiple FBDI Information to be loaded as Metadata to process the records into Oracle Fusion. With Metadata of catalog details and category details.

Data Extraction Rules

S.no	Business Rules
01.	As of now there are only four catalogs needs to be defined PRODFAMILY, PRODMODEL, PRODVIEW, VJ Procurement.
02.	If any category under PRODVIEW contains five segments like: EQUIPMENT.CIJ.1800.1800+.PRINTER than first two segments ‘EQUIPMENT.CIJ’ will be the category for PRODFAMILY and 1st, 2nd,4th segments which is ‘EQUIPMENT.CIJ.1880+’ will be the category for PRODMODEL.
03.	VJ Procurement will have only two categories Direct and Indirect.
04.	Any Item belongs to any of the catalog PRODFAMILY, PRODMODEL or PRODVIEW must be assigned to Direct category under VJ Procurement.

 

conversion approach

·        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.

·        Go to Scheduled Processes in Fusion and First Run ‘Load Interface File for Import’ for ‘Schedule Catalog Import Job’ and upload the .zip file. After its Successful Completion rerun the ‘Schedule Catalog Import Job’ 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.

Fusion Navigation

1.      Log in to Oracle Fusion Applications.

2.     2.  Click on username icon on the top right. See the highlighted part below:

1.      3. After clicking on username, click on Setup and Maintenance.

1.      4,. Click on Search from the right side.

5. Search ‘Manage Functional Area Catalogs’.

6. Click on ‘Manage Functional Area Catalogs’. Below is the screenshot from the Catalogs & Categories screen:

Data Flow Assumptions/ Prerequisites

The development specifications for Item Catalog & Category assume the following:

Key Assumptions are:

·        The data of Item Catalog & Category will be provided by the CLIENT extraction team directly into CSV Datafile.

·        Oracle technical team will prepare the data in the required Oracle standard FBDI formats.

·        FBDI Metadata will be build based on catalogs and category details.

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

·        All system level profile options have been setup.

·        Item Catalogs & Categories are imported.

 

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	Color code the mandatory fields	Highlighted the mandatory fields with green color.	Conversions Team
2	Check for standard report which will provide information related to items		Functional Team
3.
4

 

Closed Issues

 

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