CV.

040 CONVERSION DATA MAPPING

Item Conversion

Author: Creation Date: Last Updated: Document Ref: Version:

M Nishit Feb 20, 2013 Feb 20, 2013 N/A 1.0

Approvals: <Approver 1> <Approver 2> Chuck Vrchota

CV.040 Conversion Data Mapping

Document Control
Change Record
4

Date 20-Feb13

Author M Nishit

Versio n 1.0

Change Reference No Previous Document

Reviewers

Name Chuck Vrchota Vicki Bentz Bill Pick

Position Cretex IT Lead Cretex Mfg Lead Fujitsu Project Manager

Distribution

Copy No. 1 2 3 4

Name Cretex Core team

Location

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 Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

3 of 8

CV.040 Conversion Data Mapping

Contents

Document Control.......................................................................................ii Introduction................................................................................................1 Purpose.................................................................................................1 Pre-Requisites.......................................................................................1 Assumptions..........................................................................................1 Scope and Application...........................................................................1 Audience...............................................................................................1 Application Business Object Reference Information...................................2 Conversion Rules and Mapping Items......................................................3 Extract File Layout......................................................................................6 Data Clean-up.............................................................................................7 Data Normalization.....................................................................................8 Open and Closed Issues for this Deliverable...............................................9 Open Issues...........................................................................................9 Closed Issues.........................................................................................9

Bom Header Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

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 Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

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 Items Item revisions ItemCategories Customer Items

Man/ Prog Prog Prog Prog Prog

Owned By Apps Apps Apps Apps

Open Interface

Production Table Name(s) Mtl_system_items_b Mtl_item_revisions Mtl_item_categories Mtl_customer_items

Foreign Key Table Name(s)

Mtl_system_items_interface Mtl_item_revisions_interface Mtl_Item_categories_interfac e Mtl_ci_interface

Bom Header Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

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 Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

3 of 8

Target Application: Oracle Applications Business Object : Items Prepared by: <To be Filled By Technical Team >

Syste m TCM/P K TCM/P K TCM/P K TCM/P K TCM TCM TCM/P K TCM/P K TCM/P K TCM/P K TCM/P K TCM TCM PK PK PK PK PK PK PK PK PK PK PK PK PK PK PK PK

Combined Fields COMPANY_NAME ERP_SYSTEM Item Number Description Alt Key Internal Item Rev Unit of Measure (Stock) U/M Weight Length Width Height Purch/Mfg Order Policy GL Account Planner# Buyer ID Planning Type Classification Backflush Leadtime Fence Stockable Item Flag Order Point # of Days Minimum Qty Maximum Qty Multiples Of UOM (Issue) UOM (Rec)

Oracle Field

Comments RMS, Juno, etc Profit Key, TCM, etc

ITEM_NUMBER DESCRIPTION ATTRIBUTE1 MIR.REVISION_LABEL PRIMARY_UNIT_OF_MEASUR E UNIT_WEIGHT UNIT_LENGHT UNIT_WIDTH UNIT_HEIGHT PLANNING_MAKE_BUY_COD E LOT_CONTROL_CODE COST_OF_SALES_ACCOUNT PLANNER_CODE BUYER_ID Inventory Planning/MRP Planning User Item Types WIP_SUPPLY_TYPE CUMULATIVE_TOTAL_LEAD_ TIME PLANNING_TIME__FENCE_D AYS STOCK_ENABLED_FLAG

Based on Planning Pre-Requisites

Planning Attributes Planning Attributes MIN_MINMAX_QUANTITY MAX_MINMAX_QUANTITY FIXED_LOT_MULTIPLIER UNIT_OF_ISSUE Defined in UOMs
Conversion Rules and Mapping Items Company Confidential - For internal use only 3 of 8

Bom Header Conversion

PK PK PK PK PK PK PK TCM/P K

Carton Cubic Feet Material Labor Burden

MAT SUP BY/SAMP REQ PASSIVATION FORMULA Cyro Deburr. Program Customer Item Rev.

UNIT_VOLUME MATERIAL_COST MATERIAL_SUB_ELEM MATERIAL_OH_RATE ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 MIR.ATTRIBUTE1

MIR Mtl_Item_revisions, others Mtl_items_interface.

Bom Header Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

3 of 8

Extract File Layout

N/A

Datafile

Field Name

Datatype

Position: From

Position: To

Oracle Table

Oracle Column

Bom Header Conversion

Conversion Rules and Mapping Items Company Confidential - For internal use only

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 Conversion

Company Confidential - For internal use only

Conversion Rules and Mapping Items

3 of 8

Data Normalization

TO BE FILLED BY TECHNICAL TEAM

Bom Header Conversion

Company Confidential - For internal use only

Conversion Rules and Mapping Items

3 of 8

Open and Closed Issues for this Deliverable

Open Issues

ID TCM.1 TCM.2 TCM.3 TCM.4 TCM.5 TCM.6

Issue We need a default GL Account for items. Need a UOM for Item Weight Oracle Revision Number is 3 digits. Internal Rev is having very long data fields. This does not look right and may need correction Item Conv. Factor for Ft. to Lbs for certain items needed Planning Data needs to be provided for enabling items for planning

Resolution Default from org parameters Leave it null. Weight not used. Data cleaning required. In process.

Responsibility Target Dt Mark/manoj Chuck Chuck Chuck Anir/Nishit Chuck

Impact Dt

TCM.7 TCM.8 TCM.9 TCM.10

To be provided. If value is null then defaults will be: General Planning = Not Planned. MRP/MPS Planning Lot enabled flag should be provided for lot enabled items Could be provided as a separate table data and if some items should be made serial controlled then we which will have to be incorporated before need to do that import. We would have lot and serial columns in that table itemwise. WIPsupply type (Pull, Push, etc) should be provided Push. OSP item information should be provided Talk to Kristin. Order and Invoicable flags should be provided Enabled Cust/Internal Orderable, Invoicable Need the items to be categorized as FG,SA,RM Purchased=RM, else = FG/SA.

Anir/Nishit Chuck Anir/Nishit Chuck

Closed Issues

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

Bom Header Conversion

Company Confidential - For internal use only

Conversion Rules and Mapping Items

3 of 8

ID

Issue

Resolution

Responsibility

Target Date

Impact Date

Bom Header Conversion

Company Confidential - For internal use only

Conversion Rules and Mapping Items

3 of 8