Item Conversion Mapping Specification
Item Data Conversion
Author:
Creation Date: 29th August 2023
Last Updated: 30th August 2023
Document Ref:
Version: 0.1
Change Record
|
Date |
Author |
Version |
Change
Reference |
|
30-Aug-23 |
|
1.1 |
|
|
|
|
|
|
|
|
|
|
|
|
Name |
Position |
|
|
|
|
|
|
|
|
|
|
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 TEMPLATE Lookup Field MAPPING.................................... 5
MAPPING SPECIFICATIONS......................................................................... 11
Data Extract Component Logic.................................................................... 12
Data Extraction Rules...................................................................................................... 12
Upload Component Logic........................................................................... 13
Data Flow Assumptions/ Prerequisites......................................................................... 13
Open and Closed Issues.............................................................................. 14
Open Issues...................................................................................................................... 14
Closed Issues................................................................................................................... 14
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
Conversion Scope, Strategy And Assumptions
The Conversion Component FBDI template
is used by the Technical team
as the basis for the design and construction of the Item conversion.
High
Level Conversion Process Overview- Item
a.
The Data
Migration of Oracle Item 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 data
extract provided from legacy system will be used to build the FBDI templates
with Metadata of Item
Following
configurations are required in SaaS
|
S.no |
Task Name |
Status |
Comments |
|
01. |
Enterprise Design Setup |
Completed |
|
|
02. |
Item Class |
Completed |
|
|
03. |
UOM Setup |
Completed |
|
|
04. |
Item Templates and Item Type |
Completed |
|
|
05. |
Item Status |
Completed |
|
|
06. |
Item Lifecycle Phases |
Completed |
|
|
07. |
Item Catalog and Category Setup |
Open |
|
|
08. |
Item Attribute |
Open |
|
Field Name = Make or Buy
|
Value |
Description |
|
1 |
Make |
|
2 |
Buy |
Field Name = Reservable
|
Value |
Description |
|
1 |
create material
reservations for the item |
|
2 |
don't create material reservations
for the item |
Field Name = Structure Item Type
|
Value |
Description |
|
1 |
Model |
|
2 |
Option Class |
|
3 |
Planning |
|
4 |
Standard |
|
5 |
Product Family |
Field Name = Forecast Control
|
Value |
Description |
|
1 |
Consume Forecast |
|
2 |
Consume and Derive
Forecast |
|
3 |
None |
|
4 |
Consume then Explode |
|
5 |
Explode then Consume |
Field Name = Planning Method
|
Value |
Description |
|
10 |
Replenishment Planning |
|
3 |
MRP Planning |
|
4 |
MPS Planning |
|
6 |
Not Planned |
|
7 |
MRP and MPP Planning |
Field Name = Round Order
Quantities
|
Value |
Description |
|
1 |
round the quantity
on an internal requisition when converting between the unit of measure on the
requisition line and the item on the unit of issue |
|
2 |
don't resolve the unit of issue to an
integer. Setting this attribute to 2 might result in a fractional amount. |
Field Name = User Item Type
|
Value |
Description |
|
AA |
Asset Activity |
|
AG |
Asset Group |
|
AI |
ATO Item |
|
AOC |
ATO Option Class |
|
ATOFG |
ATO Model - Manufactured |
|
ATOP |
ATO Model - Purchased |
|
CMFG |
Contract Manufacturing Finished Goods |
|
CMSC |
Contract Manufacturing Service Component |
|
CONSULTING |
Contracts for Consulting |
|
CTO |
Configured Item |
|
EDU |
Contracts for Education |
|
EQ |
Equipment |
|
FG |
Finished Good |
|
FRT |
Freight |
|
I |
Inventory type |
|
K |
Kit |
|
KIT |
Contracts for Kit |
|
M |
Model |
|
MEDIA |
Contracts for media |
|
NRI |
Nonrecurring item |
|
NS |
Nonstock item |
|
OC |
Option Class |
|
OP |
Outside processing Item |
|
P |
Purchased Item |
|
PF |
Product family |
|
PH |
Phantom Item |
|
PL |
Planning |
|
POC |
PTO Option Class |
|
PTO |
PTO Model |
|
RB |
Rebuildable |
|
REF |
Reference Item |
|
RI |
Recurring item |
|
SA |
Subassembly |
|
SI |
Supply Item |
|
SW LIC |
Contracts for Software License |
|
TRAIN |
Contracts for Training |
Field Name = Pricing Unit of
Measure
|
Value |
Description |
|
P |
Primary |
|
S |
Secondary |
Field Name = WIP Supply Type
|
Value |
Description |
|
1 |
Push |
|
2 |
Assembly pull |
|
3 |
Operation pull |
|
4 |
Bulk |
|
5 |
Supplier |
Field Name = Inventory Planning Method
|
Value |
Description |
|
1 |
Reorder Point planning |
|
2 |
Min-max Planning |
|
6 |
Not Planned |
|
7 |
Supplier Managed |
Field Name = Replenishment Source Type
|
Value |
Description |
|
1 |
Inventory |
|
2 |
Supplier |
|
3 |
Subinventory |
Field Name = Sub inventory
Restrictions
|
Value |
Description |
|
1 |
then restrict the
transactions of the item from the sub inventory |
|
2 |
don't restrict the transactions of
the item from the sub inventory. The default value is true. |
Field Name = Restrict Locators
|
Value |
Description |
|
1 |
restrict the transactions
of the item from the locator |
|
2 |
then don't restrict the transactions of the
item from the locator. |
Field Name = Lot Expiration Control
|
Value |
Description |
|
1 |
No Control |
|
2 |
Shelf life days |
|
4 |
User-defined |
Field Name = Serial Number Control
|
Value |
Description |
|
1 |
No serial number control |
|
2 |
Predefined serial number |
|
5 |
Dynamic entry at inventory receipt |
|
6 |
Entry at sales order, transfer order or work
order issue |
|
7 |
Entry at inventory pick |
Field Name = Revision Control
|
Value |
Description |
|
1 |
the item isn't under revision control
and it includes inventory attributes. |
|
2 |
the item is under revision control
and it includes inventory attributes |
Field Name = Stock Locator Control
|
Value |
Description |
|
1 |
No control |
|
2 |
Previously specified |
|
3 |
Dynamic Entry |
Field Name = Lot Control
|
Value |
Description |
|
1 |
No Control |
|
2 |
Full Control |
Field Name = Reservable
|
Value |
Description |
|
1 |
create material
reservations for the item |
|
2 |
don't create material reservations for the
item. |
Field Name = Structure Item Type
|
Value |
Description |
|
1 |
Model |
|
2 |
Option
Class |
|
3 |
Planning |
|
4 |
Standard |
|
5 |
Product Family |
Field Name = Forecast Control
|
Value |
Description |
|
1 |
Consume Forecast |
|
2 |
Consume and Derive Forecast |
|
3 |
None |
|
4 |
Consume then Explode |
|
5 |
Explode then Consume |
Field Name = Demand Time Fence
|
Value |
Description |
|
1 |
Cumulative Total Lead Time |
|
2 |
Cumulative Manufacturing Lead Time |
|
3 |
Item Total Lead Time |
|
4 |
User Defined Time Fence |
Field Name = Planning Method
|
Value |
Description |
|
10 |
Replenishment Planning |
|
3 |
MRP Planning |
|
4 |
MPS Planning |
|
6 |
Not Planned |
|
7 |
MRP and MPP Planning |
Field Name = Planning Time Fence Code
|
Value |
|
Description |
|
1 |
|
Cumulative Total Lead Time |
|
2 |
|
Cumulative Manufacturing Lead Time |
|
3 |
|
Item Total Lead Time |
|
4 |
|
User Defined Time Fence |
Field Name = Round Order Quantities
|
Value |
Description |
|
1 |
round the quantity on an
internal requisition when converting between the unit of measure on the
requisition line and the item on the unit of issue |
|
2 |
then don't resolve the unit of issue to an
integer. Setting this attribute to 2 might result in a fractional amount. |
Field Name = RMA Inspection Required
|
Value |
Description |
|
1 |
then inspection is needed for items
returned by customers. The item then must be transferred to inventory
separately |
|
2 |
Inspection isn't needed for items returned
by customers. |
Field Name = Receipt Routing
|
Value |
Description |
|
1 |
Standard |
|
2 |
Inspection |
|
3 |
Direct |
Item Additional Attributes
|
GLOBAL |
|||
|
NAME |
TABLE
COLUMN |
VALUE
SET |
GLOBAL(Y/N) |
|
WIP
ACCOUNT CLASS |
ATTRIBUTE1 |
CUIN_ITM_WIP_ACCT_CLASS |
Y |
|
COUNTRY
OF ORIGIN |
ATTRIBUTE4 |
CUIN_ITM_COUNTRY_CODE |
Y |
|
END
OF LIFE DATE |
ATTRIBUTE_DATE1 |
AS_SRS_DATE. |
Y |
|
CONTEXT- 0333
VJ IT INV ORG (ORGANIZATION SPECIFIC) |
|||
|
COUNTRY
OF ORIGIN _2 |
ATTRIBUTE2 |
CUIN_ITM_COUNTRY_CODE |
N |
|
NRTL
ITEM |
ATTRIBUTE3 |
INV_SRS_YES_NO |
N |
|
MFG
INSTRUCTION |
ATTRIBUTE5 |
150 Character |
N |
|
HOT
PART |
ATTRIBUTE6 |
Yes_No |
N |
|
COMMENTS |
ATTRIBUTE7 |
240 Character |
N |
|
ECCN
NUMBER |
ATTRIBUTE8 |
ECCN _NUMBER |
N |
|
MEU NUMBER |
ATTRIBUTE9 |
MEU_NUMBER |
N |
|
TARIFF CODE |
ATTRIBUTE10 |
TARIFF_CODE |
N |
|
NET WEIGHT |
ATTRIBUTE11 |
NET_WEIGHT |
N |
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 Videojet Team in FBDI template
Fusion Navigations:
Item
screen: Product Management -> Product Information Management -> Manage
Items/Browse items
Run a ESS
job: Tools -> Scheduled Processes -> Schedule New Process
Standard ESS Jobs used in Item Conversion:
1.
Load Interface File for Import
2.
Item Import
3. Purge Interface Tables
Note:Describe the component logic for the download
component(s) used to convert the entity being converted.
Bring Item and related details from existing legacy system
to New Fusion
To bring
in Item Data into Oracle fusion we need pre-requisites of UOM Setups, Item
Status, Item Lifecycle Phases, into Oracle Fusion. These will be loaded as part
of separate conversions.
Pool: Only Include Active Item Data
Data Extraction Rules
|
S.no |
Business Rules |
|
01. |
All the Items currently available in Navision will
get converted and get associated to child org |
|
02. |
All the Items will get associated to Root Item Class
in Oracle Fusion (Any change to the same will be communicated by Business) |
|
04. |
There are 6 Item Statuses available for an Item and
association will happen based on the extraction. |
|
05. |
All the Additional Attribute associated with the
Item should be part of the Item Conversion. |
|
06. |
All the Item created should be Auto Approved |
|
07. |
While creating the
Item Technical Team to use Single “Created By” Name, this will help business
to reconcile if Item is created Manually or through Conversion. |
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 ‘Item Import’ and upload
the .zip file. After its Successful Completion rerun the Item Import 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
Item data assume the following:
Key Assumptions are:
·
The data
of Item data will be provided by the CLIENT extraction team
directly into FBDI template.
·
Oracle
technical team will generate the data in the required CSV and ZIP format.
·
FBDI template
will be build based on data extracts provided from Navision or EBS.
·
All
required setups/configurations have
been completed before the program is run.
ü
UOM Conversion
ü
Item Status
|
ID |
Issue |
Resolution |
Responsibility |
Target
Date |
Impact
Date |
|
1 |
Attribute values are missing Recheck attributes configured Context is inv org |
|
|
|
|
|
2 |
|
|
|
|
|
|
3. |
|
|
|
|
|
|
4 |
|
|
|
|
|
|
ID |
Issue |
Resolution |
Responsibility |
Target
Date |
Impact
Date |
|
1 |
Attribute values are missingRecheck attributes configured Context is inv org |
|
|
|
|
|
2 |
|
|
|
|
|
|
3. |
|
|
|
|
|
|
4 |
|
|
|
|
|
Comments
Post a Comment