Item Structure Conversion Mapping Specification

 

 

Item Structure Conversion Mapping Specification

 

 

              Item Structure Data Conversion

 

 

 

 

 

 

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

 

 

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

Oracle FUSION ITEM STRUCTURE TEMPLATE Lookup Field MAPPING.................. 5

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

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

Data Extraction Rules................................................................................... 7

Upload Component Logic............................................................................. 8

Data Flow Assumptions/ Prerequisites............................................................ 8

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

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

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

 

Note:To update the table of contents, put the cursor anywhere in the table and press [F9].  To change the number of levels displayed, select the menu option Insert‑>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

 

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 Structure

Conversion Scope, Strategy And Assumptions

The Conversion Component Designs is used by the Technical team as the basis for the design and construction of the Item Structure conversion.

High Level Conversion Process Overview- Item Structure

a.      The Data Migration of Oracle Item Structure 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 templates with Metadata of Item Structure

 

Prerequisites

Following configurations are required in SaaS

 

S.no	Task Name	Status	Comments
01	UOM Setup	Completed
02	Item Status	Completed
03.	Item Lifecycle Phases	Completed
04.	Item Category Setup	Open

 

 

 

 

Oracle FUSION ITEM STRUCTURE TEMPLATE Lookup Field MAPPING

Field Name = Effectivity Control

Value	Description
1	Date
2	Model or Unit
3	Serial

 

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

Sample Data provided by client Team in FBDI template

Item Templates for structure and components

Run a ESS job: Tools -> Scheduled Processes -> Schedule New Process

 

Standard ESS Jobs used in Item Structure Conversion:

 

1.      Load Interface File for Import

2.      Item Import

 

Fusion Navigations:

Item screen: Product Management -> Product Information Management -> Manage Items/Browse items

Data Extract Component Logic

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

Bring  Item structure and related details from existing legacy system to New Fusion

 

To bring in Item structure Data into Oracle fusion we need pre-requisites of UOM Setups, Item Status, Item Lifecycle Phases, Item, Item Category, Item Structure Type into Oracle Fusion. These will be created as part of Configuration or sperate conversion (sperate conversion required for Item and Item Category).

 

Pool: Only Include Active Item Data

 

 

Data Extraction Rules

 

S.no	Business Rules
01.	Item Structure (BOM) will be created in Oracle Fusion having associated Component Item and also reference to Substitute Item.
02.	All the Item in the Item Structure including Component, Substitute, Reference Item will be in Approved status
03.	Deletion of Item in Item Structure will be done through Engineering Change Order (ECO).
04.	All the Parent and Child Item in the Item Structure extract to be attached to only Child Org
05.	Item Structure Name will be Primary for all the Parent Item
06.	All the BOMs (Item Structure) will be created in Child Organization (VIT) only. No Item Structure will be applicable in Master Organization.

 

Upload Component Logic

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

·        Get the data and Store it in Oracle Fusion Template.

·        After you finish preparing the data in the sheets, click the Generate CSV File button. The program generates both a CSV file and a ZIP file. 

·        Load the data using the Load Interface File for Import process:

1.      Log in to Oracle Fusion Applications.

2.      Navigate to Scheduled Processes.

3.       Select the Load Interface File for Import process.

4.      Select the process Item Import to load the CSV file to the interface tables.

5.       Review the results of the process.

·        Correct load errors:

1.       If the load of the CSV files fail on any row, the Load Interface File for Import process ends in error and the Load File to Interface child process ends in either warning or error. 

2.       All rows that were loaded from the CSV file are deleted, even those rows that loaded successfully. This lets you edit the problematic data in the spreadsheet and resubmit  without having to separate the successful rows from the rows that need modification.  

3.      Review the log and output files of the Load File to Interface child process for information about the data that caused the failure.

4.      Correct the data in the template you used as part of the steps outlined in Preparing the Table Data above.

5.      Repeat steps 1 and 2 of this section: Generate the CSV file and load the data using the Load Interface File for Import process.

6.      Repeat all of these steps until all data is loaded successfully.

 

 

 

 

 

Data Flow Assumptions/ Prerequisites

The development specifications for Item Structure data assume the following:

Key Assumptions are:

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

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

·        FBDI will be build based on single Item structure datafile provided.

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

ü  Structure Type

ü  Structure Name

ü  Association Structure Name with Structure Type

 

 

 

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
2
3.
4

 

Closed Issues

 

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