CV.040 CONVERSION DATA MAPPING

Item Conversion

Author: M Nishit

Creation Date: Feb 20, 2013

Last Updated: Feb 20, 2013

Document Ref: N/A

Version: 1.0

Approvals:

<Approver 1> Chuck Vrchota

<Approver 2>

CV.040 Conversion Data Mapping

Document Control

Change Record

4

Date Author Version

Change Reference

20-Feb-13

M Nishit 1.0 No Previous Document

Reviewers

Name Position

Chuck Vrchota Cretex IT LeadVicki Bentz Cretex Mfg LeadBill Pick Fujitsu Project Manager

Distribution

Copy No.

Name Location

1 Cretex Core team2 `34

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

CV.040 Conversion Data Mapping

Contents

Document Control..........................................................................................ii

Introduction....................................................................................................1

Purpose....................................................................................................1Pre-Requisites..........................................................................................1Assumptions.............................................................................................1Scope and Application.............................................................................1Audience..................................................................................................1

Application Business Object Reference Information....................................2

Conversion Rules and Mapping – Items........................................................3

Extract File Layout.........................................................................................5

Data Clean-up................................................................................................6

Data Normalization........................................................................................7

Open and Closed Issues for this Deliverable................................................8

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

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Introduction

Purpose

The Conversion Data Mapping document provides the field level mapping for the Item attributes required to convert the data from the Cretex Legacy System TCM and Profit Key to Oracle. This would include the following objects for conversion:

Items

Item Revisions

Item Categories

Customer Items

Pre-Requisites

The Units of Measures should be defined in the system if not already seeded through Oracle.

The Source data should be provided by Cretex in a flat file for loading to Oracle

The Customers should be defined before converting Customer Items.

Assumptions

The item attributes that cannot be provided by the source system would be assumed to be defaulted in Oracle. This situation can arise is the source system does not store the related data that Oracle requires. For example, if planning data is not provided during conversion the all the items would default to not planned and thatmay affect the Planning process in Oracle.

Hence every effort should be made to extract and provide data for improving the quality of conversion.

Scope and Application

All the item data provided by TCM and Profit Key for conversion would be in Scope.

Audience

This document is intended for the Cretex Core team and the Business leads.

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Application Business Object Reference Information

In each of the following sections, a table maps the business objects for Items, Item Revisions, Item Categories and Customer Items to the Oracle Application tables. The foreign key relationships between the Oracle Application tables are also indicated. Column (2) suggests whether the business object is a candidate for programmatic conversion. In column (4), the standard Oracle interface is documented if one exists for facilitating the conversion of a specific business object.

Business Object

Man/Prog

OwnedBy

Open Interface Production Table Name(s)

Foreign Key Table Name(s)

Items Prog Apps Mtl_system_items_interface Mtl_system_items_bItem revisions Prog Apps Mtl_item_revisions_interface Mtl_item_revisionsItemCategories Prog Apps Mtl_Item_categories_interfac

eMtl_item_categories

Customer Items

Prog Apps Mtl_ci_interface Mtl_customer_items

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Conversion Rules and Mapping – Items

Source System: TCM

Target System: Oracle 12

Pre-requisitits:

User-Item Types should be defined before conversion

Conversion Program Parameters:

To be filled in

Conversion Strategy:

Items would be segregated as Raw Material or Finished Goods.

If Make / Buy = Buy Purchased

Make FG.

Conversion Rules:

All

Below is a table mapping the source data elements to the target tables and columns? Please note that below mapping is showing only functional columns. All other columns which are required by oracle open interface to pocess data must be handeled within conversion code.

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Target Application: Oracle Applications

Business Object : Items

Prepared by: <To be Filled By Technical Team >

System Combined Fields Oracle Field CommentsTCM/PK COMPANY_NAME   RMS, Juno, etc

TCM/PK ERP_SYSTEM  Profit Key, TCM, etc

TCM/PK Item Number ITEM_NUMBER  TCM/PK Description DESCRIPTION  TCM Alt Key ATTRIBUTE1  TCM Internal Item Rev MIR.REVISION_LABEL  TCM/PK Unit of Measure (Stock) PRIMARY_UNIT_OF_MEASURE  TCM/PK U/M Weight UNIT_WEIGHT  TCM/PK Length UNIT_LENGHT  TCM/PK Width UNIT_WIDTH  TCM/PK Height UNIT_HEIGHT  TCM Purch/Mfg PLANNING_MAKE_BUY_CODE  TCM Order Policy LOT_CONTROL_CODE  PK GL Account COST_OF_SALES_ACCOUNT  PK Planner# PLANNER_CODE  PK Buyer ID BUYER_ID  PK Planning Type  Inventory Planning/MRP Planning Based on PlanningPK Classification User Item Types  Pre-RequisitesPK Backflush WIP_SUPPLY_TYPE  PK Leadtime CUMULATIVE_TOTAL_LEAD_TIME  PK Fence PLANNING_TIME__FENCE_DAYS  PK Stockable Item Flag STOCK_ENABLED_FLAG  PK Order Point   Planning AttributesPK # of Days   Planning AttributesPK Minimum Qty MIN_MINMAX_QUANTITY  PK Maximum Qty MAX_MINMAX_QUANTITY  PK Multiples Of FIXED_LOT_MULTIPLIER  PK UOM (Issue) UNIT_OF_ISSUE  PK UOM (Rec) Defined in UOMs  PK Carton Cubic Feet UNIT_VOLUME  PK Material MATERIAL_COST  PK Labor MATERIAL_SUB_ELEM  PK Burden MATERIAL_OH_RATE  PK MAT SUP BY/SAMP REQ ATTRIBUTE2  PK PASSIVATION FORMULA ATTRIBUTE3  PK Cyro Deburr. Program ATTRIBUTE4  TCM/PK Customer Item Rev. MIR.ATTRIBUTE1  

MIR – Mtl_Item_revisions, others – Mtl_items_interface.

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Extract File Layout

N/A

Datafile Field Name Datatype Position:From

Position:To

Oracle Table Oracle Column

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Data Clean-up

1) Item Revisions (in Desc2) Needs to be cleaned up.

2) Revision should be 3 char long.

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Data Normalization

TO BE FILLED BY TECHNICAL TEAM

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Dt

Impact Dt

TCM.1 We need a default GL Account for items. Default from org parameters Mark/manojTCM.2 Need a UOM for Item Weight Leave it null. Weight not used. ChuckTCM.3 Oracle Revision Number is 3 digits. Internal Rev is having

very long data fields. This does not look right and may need correction

Data cleaning required. In process. Chuck

TCM.4 Item Conv. Factor for Ft. to Lbs for certain items needed To be provided. ChuckTCM.5 Planning Data needs to be provided for enabling items for

planningIf value is null then defaults will be:General Planning = Not Planned. MRP/MPS Planning

Anir/Nishit

TCM.6 Lot enabled flag should be provided for lot enabled items and if some items should be made serial controlled then we need to do that

Could be provided as a separate table data which will have to be incorporated before import. We would have lot and serial columns in that table itemwise.

Chuck

TCM.7 WIPsupply type (Pull, Push, etc) should be provided Push. Anir/NishitTCM.8 OSP item information should be provided Talk to Kristin. ChuckTCM.9 Order and Invoicable flags should be provided Enabled Cust/Internal Orderable, Invoicable Anir/NishitTCM.10 Need the items to be categorized as FG,SA,RM Purchased=RM, else = FG/SA. Chuck

Closed Issues

ID Issue Resolution Responsibility Target Date

Impact Date

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8

ID Issue Resolution Responsibility Target Date

Impact Date

Bom Header ConversionCompany Confidential - For internal use only

Conversion Rules and Mapping – Items 3 of 8