CV040 Onhand Qty-V1.0

AIM
CV.040 CONVERSION DATA

MAPPING
FL Smidth
Onhand Inventory Conversion
Author: Anshul Kumar
Creation Date: July 13, 2012
Last Updated:
Document Ref: <Document Reference Num>
Version: 1.0
Approvals:
<Approver 1>
<Approver 2>
CV.040 Conversion Data Mapping Doc Ref: <Document Reference Num>
Error: Reference source not found
Document Control
Change Record
Date Author Versio Change Reference

n
13-Jul- Anshul Kumar Draft No Previous Document

2012 1a
09-Aug- Anshul Kumar 1.0 Modified based on the review comments.

2012
Reviewers
Name Position
Pablo S. Perez Solution Architect-SCM
Janne Stegemann Business Lead Back Office
Pia Bubandt Mortensen Business Lead- Valby
Jacqueline Hoefer Business Lead- Bethlehem
Michael Fisher Conversion Manager
Tom Jensen Project Manager
Rathakrishnan Jayabalan Assistant Manager.ESD Group for Enovia
Distribution
Onhand Inventory Conversion Approach 2227192
File Ref: 351028461 (v. 1.0 )

Copy Name Location

No.
1 Library Master Project Library
2 Project Manager
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.
File Ref: 351028461 (v. 1.0 )

Contents
Document Control.......................................................................................ii
Introduction................................................................................................ 4
Purpose.................................................................................................4
Background........................................................................................... 4
Scope and Assumption...............................................................................5

Scope.................................................................................................... 5
Assumption...........................................................................................5
Pre-requisite................................................................................................ 6
Approach..................................................................................................... 7
Financial Approach................................................................................7
Data Clean-up............................................................................................. 9
Validation.................................................................................................. 10
Reconciliation......................................................................................10
Interim Process:........................................................................................11
Interface Process Stages...........................................................................12
Technical Information Onhand Inventory................................................13

Interface parameter:...........................................................................16
Extract File Layout....................................................................................17
Open and Closed Issues for this Deliverable.............................................19

Open Issues......................................................................................... 19
Closed Issues.......................................................................................19
File Ref: 351028461 (v. 1.0 )

File Ref: 351028461 (v. 1.0 )

Introduction
Purpose
An important requirement is to load Quantity on hand data from existing systems into
Oracle applications. The Quantity on hand will be only required for those items have
available/unreserved quantity on hand.
The objective of this document is to describe the functional requirements for the
loading of Quantity on hand data from External systems into Oracle. The interface will
consist of a Comma Separated Variable (CSV) file templates being generated from
existing data and made available Oracle applications in an agreed directory. The file
will then be loaded Oracle through standard interfaces.
Background
The information in this document has been defined for conversion of onhand quantity
from Atlas & other various IT systems to R12.
File Ref: 351028461 (v. 1.0 )

Scope and Assumption
Scope
Costing method is Average costing and migrated stock will show
current average cost of item. It does not hold any historic cost.
Conversion team will provide the mapping file and cleansed on hand
data file mapped with Enovia item number to business. Business will
provide sign-off before data will be loaded into Oracle Production
environment.
Data migrated will be on the item conversion date, It will not migrate
with historic date.
If details like country of origin, supplier and stock aging need to find
out after migration, this would be outside oracle. Migrated on hand
data will not hold such details.
No Project specific inventory will be migrated.
Conversion team will provide the migrated on hand data from the
oracle system in spreadsheet with Enovia item number.
Simultaneously PDB number and Enovia item number mapping file
will be provided received from Enovia Team. Business will be
reconciling the data based on these 2 files.
This document will include various process related to on hand. Process

owner can provide more details, if require related to them.
Conversion will take place for the warehouse as per sheet available at
below link and approved by business:
http://fls-
teamsites/project/GlobalITProjectsPortal/StrategicProjects/CenterERP/R
2%20general%20cross-business/Data%20Conversion/Inventory
%20Dataconversion%20Planning%20Sheet%20UPDATES%20FROM
%20BETHLEHEM%2028-JUN-12.xlsx
Assumption
The data held in Oracle is defined as that data required by Oracle
Applications to support the approved system design as signed off by
File Ref: 351028461 (v. 1.0 )

FLSmidth users. Any additional data required by non-Oracle

supporting systems will be managed by other procedures and is
documented elsewhere and not the responsibility of this project or
document.
Pre-requisites in this document are defined and validated by

respective owner.
On hand data & other related details provided by the business is

validated and verified by respective business users.
Mapping of PDB number to new item number generated by enovia is

provided by Enovia team, which will flow to Oracle in terms of item
reference "Conversion".
Current inventory has only material cost of items.
Business user will reduce the inventory in the old warehouse system,
when they provide the on hand data during cut over period for
migration into oracle and same should also reflect in financial system
with conversion account.
File Ref: 351028461 (v. 1.0 )

Pre-requisite
The following pre-requisite required for this interface to run:
Enovia has pushed all the items in the oracle and assigned it to all the
inventory organizations.
All the required items have been made active and required attributes are
updated.
All required locators are defined for the asset subinventory with all
inventory structure. Details of warhouse structure is available at below
link:
http://fls-
teamsites/project/GlobalITProjectsPortal/StrategicProjects/CenterERP/R2%20g
eneral%20cross-business/Data%20Conversion/Inventory%20Dataconversion
%20Planning%20Sheet%20UPDATES%20FROM%20BETHLEHEM%2028-JUN-
12.xlsx
Data provided to load by business should be as per new UOM from Oracle.
Conversion team will provide the Item and UOM details in advance to
business to validate the data before it's provide to migrate.
Project data is loaded if project specific inventory is required to load.
Conversion account is setup.
File Ref: 351028461 (v. 1.0 )

Approach
The Transaction Open Interface API (mtl_transactions_interface) will be used to load

the inventory from data provided in Excel format from the legacy system. The
intermediate Excel file is suggested so that any site will be able to use this process
without requiring programming changes. Interface will use a Miscellaneous Receipt/
Issue to update the inventory balances for the items to be processed.
Developers to utilized designed file format as attached in this document.
The implementation site will collect the data in the Excel file template.
Developers will build a sql procedure to read the input file and write it to
the custom table.
Custom validation will be applied on the custom table before moving it

inventory interface.
The inventory transaction API is run to load data into the inventory tables.
Reference Oracle manual Manufacturing APIs and Open Interfaces

Manual, chapter 6 Oracle Inventory Open Interfaces and APIs
Reference Metalink article Sample WMS Open Interface Insert Scripts /

Examples how to Insert into Transaction Open Interface [ID 357535.1]
Request should process only one inventory organization record based on

the MFG: Organization_ID profile selected.
Source will be selected Miscellaneous Receipt if quantity is positive and

Miscellaneous Issue if quantity is negative.
Sysdate will be taken for transaction_date if not provided.
If Item number is not found in on hand date, find the item number using
cross reference "Conversion" based on the PDB number provided.
Conversion program should have the provision to only validate the data.
Validation is provided in the separate section.
File Ref: 351028461 (v. 1.0 )

Financial Approach
Business user will provide inventory valuation report for both kind of stock
((Stock migrating in oracle, Stock stays in source system).We would need
to get the sign-off from finance department that inventory valuation is
matching as per GL before we can start the on hand data migration.
Business will provide the report to finance department in below format:
PDB Total Reserved Available Qty/ Average

Number Quantity Qty/Qty to Quantity going unit Cost
remain in source to migrate in of item
system Oracle
Finance department will provide sign-off on the inventory valuation

matching with GL.
Business will remove the available inventory from source system, which
needs to migrate to Oracle. This transaction should create below
accounting transaction in GL.
Source_Inventory_A/C Cr
Conversion_A/C Dr
Once on hand data is migrated to Oracle, It will create below accounting

entry in GL.
Conversion_A/C Cr
Oracle_Inventory_A/C Dr
These processes will knock-off all the balance in conversion account and
through GL , it inventory valuation sitting in Oracle and non-oracle system
can be viewed.
File Ref: 351028461 (v. 1.0 )

Data Clean-up
Warehouse approach to prepare source system, before conversion data could be
extracted from source system:
All the Quantity will be adjusted in source system as per physical quantity.
All the cost will be adjusted in source system, before extracting data and
the changes will be reflecting in financial balance in source system.
Complete the scrapping process for all pending items.
Warehouse balance reflects correctly in financial system.
Below is a description of the data clean-up efforts required for the conversion of
on hand data:
Approved and Verified Mapping file will be provided by Enovia team,

which will contain the mapping of PDB number with new item numbers.
All the items which will be provided to migrate will be

unreserved/available stock, which is extra after fulfilling existing sales
orders.
Business will provide the total inventory valuation report including

committed & non-committed stock, to take sign-off from financial before
migration.
Business will provide the data in the agreed format as per template
attached in this document. This Sheet will have only unreserved stock
with the new UOM.
Conversion team will provide details to Spare Parts lead about missing
PDB numbers from Oracle & Mapping file, based on the data received.
This step may need to repeat and will also be carried out much before
cut-off to minimize the risk of finding such items during cut-off.
Required Item status will be changed to Active
On_hand to be migrated need to be reduced from source system and

accounting entry for such transaction will be with conversion account in
GL.
File Ref: 351028461 (v. 1.0 )

Cleansed on_hand data will be migrated to oracle by each warehouse

after validation is passed on it, using the conversion account as provided
by finance.
File Ref: 351028461 (v. 1.0 )

Validation
Following validation should be checked and data should not process, any violation
should be shown in the output file.
Item is valid for the warehouse, If PDB number is provided, corresponding

item number will be derived based on the item cross reference.
UOM is valid for corresponding item.
Item cost is non-negative.
Material, Material Overhead, OSP, Resource and overhead cost sum is

equivalent to Unit cost.
Subinventory is valid for Warehouse and item.
Locator is valid for warehouse, subinventory and item.
Project and task is valid if provided.
Reason code is valid.
Reconciliation
Mapping sheet and Extract will be provided from Oracle. Mapping sheet will contain
the mapping of PDB number with new item number. Extract file will keep the new item
number, Quantity, Warehouse, Subinventory, unit cost and locator information.
Business will reconcile the data based on the extract to provide the sign off.
File Ref: 351028461 (v. 1.0 )

Interim Process:
This process will be utilizing after R2 live and while business will be processing their
customer orders from their old system and from Oracle simultaneously. The method to
process order is not in scope of this document. In this section we are trying to brief the
process in non oracle system to fulfill customer order, while oracle is live and on hand
is divided between oracle and non oracle system.
There are following scenario possible after go live in Oracle, while fulfilling demand:
Sr. Scenario Process

No.
1 Fulfilling the Original Order will be processed in old system.

sales order Like its happening currently.
2 Sales order gets Cancel the Sales order in source system

cancelled and transfer the quantity to Oracle
3 Sales order quantity is Ship the required quantity from source

reduced by customer system and transfer rest quantity to
Oracle.
4 Sales order quantity is Check if sufficient quantity is available in

increased by customer source system. If not, a process will be
required to reduce the require quantity
from oracle and migrate same in source
system to fulfill the sales order.
File Ref: 351028461 (v. 1.0 )

Interface Process Stages

On Hand quantity conversion program should follow process stage mentioned
below:
1. Gather Quantity on hand details for those items have quantity on hand when cutoff.
2. Write details to interface file.
3. Pass completed file to the DATA directory. $MISC_DIR/INV/OH/in.
4. Import to Oracle apps.
i. Insert the data into a staging table
ii. Find Enovia item number for corresponding PDB number.
iii. Validate if the data is Ok then move to Oracle open interface
iv. Perform Oracle standard API to bring the quantity on hand data into Oracle master
table
5. If any errors are found move file to $MISC_DIR/INV/OH/out/error and resolve errors.
6. If the file is processed successfully move file to $MISC_DIR/INV/OH/out/processed.
File Ref: 351028461 (v. 1.0 )

Technical Information Onhand Inventory
Sample SQL for Loading Interface Table (From API documents)
Insert into mtl_transactions_interface(

transaction_uom,
transaction_date,
source_code,
source_line_id,
source_header_id,
process_flag ,
transaction_mode ,
lock_flag ,
locator_id ,
last_update_date ,
last_updated_by ,
creation_date ,
created_by ,
inventory_item_id ,
subinventory_code,
organization_id,
transaction_quantity ,
primary_quantity ,
transaction_type_id ,
dst_segment1,
dst_segment2,
dst_segment3,
dst_segment4,
dst_segment5,
transaction_interface_id)
VALUES (
'Ea', --transaction uom
SYSDATE, --transaction date
'Miscellaneous Receipt', --source code
99, --source line id
99, --source header id
1, --process flag
3 , --transaction mode
2 , --lock flag
1291 , --locator id
SYSDATE , --last update date
0, --last updated by
SYSDATE , --creation date
0, --created by
11821 , --inventory item id
'FGI',--From subinventory code
1884, --organization id
10, --transaction quantity
10, --Primary quantity
42, --transaction type id
File Ref: 351028461 (v. 1.0 )

'01', --segment1 account combination

999 transaction interface id
);
Supporting Information (From API documents)
Open Transaction Interface

Oracle Inventory provides an open interface for you to load transactions from external applications and
feeder systems. These transactions could include sales order shipment transactions from an Order
Management system other than Oracle Order Management, or they could be simple material issues,
receipts, or transfers loaded from data collection devices. The following transaction types are supported
by this interface:
Inventory issues and receipts (including user-defined transaction types)
Subinventory transfers
Direct interorganization transfers
Intransit shipments
WIP component issues and returns
WIP assembly completions and returns
Sales order shipments
Inventory average cost updates
LPN Pack
Unpack
Split Transactions
Inventory Lot Split/ Merge/ Translate Transactions
This interface is also used as an integration point with Oracle Order Management for shipment
transactions. Oracle Order Management's Inventory Interface program populates the interface tables with
transactions submitted through the Confirm
Shipments window.
You must write the load program that inserts a single row for each transaction into the
MTL_TRANSACTIONS_INTERFACE table. For material movement of items that are under lot or serial control,
you must also insert rows into MTL_TRANSACTION_LOTS_INTERFACE and
MTL_SERIAL_NUMBERS_INTERFACE respectively. If you insert WIP
assembly/completion transactions that complete or return job assemblies, you must also insert rows into
the CST_COMP_SNAP_ INTERFACE table if the organization referenced uses average costing. The system
uses this information to calculate completion cost.
File Ref: 351028461 (v. 1.0 )

There are two modes you can use to process your transactions through the interface. In the first
processing mode, you populate the interface table only. Then the Transaction Manager polls the interface
table asynchronously looking for transactions to process, groups the transaction rows, and launches a
Transaction Worker to process each group.
In the second processing mode, you insert the rows in the interface table and call a Transaction Worker
directly, passing the group identifier of the interfaced transactions as a parameter so that the worker can
recognize which subset of transactions to process.
File Ref: 351028461 (v. 1.0 )

Target Application: INV
Business Object : Onhand Inventory
Prepared by:
(1) (2) (3) (4) (5) (6) (7) (8) (9)
Ref. Target Application Target Application Target Not Source System Source System Source Default
# Table Table Column Column Null? File Name Field Name System Value
Dataty Field
pe Datatyp
e
1 mtl_transactions_interfa Transaction_interface_i Num Mtl_material_tr

ce d ansactions_s.ne
xtval
Transaction_header_id Num Transaction_int

erface_id
Source_code Var(30 Yes inv

)
Source_line_id Num Yes Transaction_int

erface_id
Source_header_id Num Yes Transaction_int

erface_id
Process_flag Num Yes 1
Transaction_mode Num Yes 3
Validation_required Num 1
Lock_flag Num 2
Last_update_Date Date Yes
Last_updated_by Num Yes
Created_by Num Yes
Creation_date Date Yes
Item_segment1 Var2 Enovia Item Number Exis

to th
Schedule_flag Num 2
Revision Var2
Organization_id Num Yes Warehouse Valid

cod
Transaction_qty Num Yes Quantity >0
Primary_qty Num Qty

cod
File Ref: 351028461 (v. 1.0 )

(1) (2) (3) (4) (5) (6) (7) (8) (9)
Dataty Field
pe Datatyp
e
Transaction_uom Var2 Yes UOM Valid
Transaction_date Date Yes Sys_date
Acct_period_id Num Der

cale
tran
Subinventory_code Var2 Subinventory Valid

cod
orga
LOCATOR_NAME Var2 Locator
Loc_segment1 Var2
Transaction_type_id Num Yes Trans Type =

Miscellaneous
receipt for
positive
quantity and
'Miscellaneous
Issue' for
Negative
quantity
Distribution_account_id Num GL c
ID
Project_id Num Project
Task_id Num Task
Source_lot_Num Var2 Che

con
if lo
item
Reason_id Num Reason_code
TRANSACTION_REFERE Var2 Comments

NCE
Attribute_category Var2
Attribute1 Var2
Attribute2 Var2
Attribute3 Var2
Attribute4 Var2
Attribute5 Var2
File Ref: 351028461 (v. 1.0 )

(1) (2) (3) (4) (5) (6) (7) (8) (9)
Dataty Field
pe Datatyp
e
Mtl_transactions_lots_int Transactions_interface_i Yes Transaction_int

erface d erface_id
product_code inv
Last_update_date Yes sysdate
Last_updated_by Yes User_id
Creation_date Yes sysdate
Created_by Yes User_id
Transaction_quantity Yes Quantity
Transaction_cost Unit Cost
Primary_quantity
Lot_Number Yes
Product_transaction_id Transaction_int
erface_id
Lot_expiry_date
Interface parameter:
Parameter Name Required ?
File Name Yes
Conversion Account Yes
Validate Only No
File Ref: 351028461 (v. 1.0 )

Extract File Layout

Below is a table documenting the extract file schema.
On-Hand
Template.xls
Required
Field Name or Optional Description
Inventory organization code in which the assembly

item exists. Value in template must match a 3
character inventory organization code as defined in
Warehouse Required the Oracle database.
PDB Number Required Atlas item number.
Item number must be already existing in the

organization specific, otherwise program will error out
ITEM_NUMBER Optional
UOM Required Unit of measure
Unresrved/Available quantity required to migrated in

QUANTITY Required Oracle.
SUBINVENTORY Required Valid subinventory for the warehouse.
Locator information for the item, Which contains

LOCATOR Required Area, Row, Rack & Bin details.
File Ref: 351028461 (v. 1.0 )

Valid Project for the organization. This is not

PROJECT Optional applicable for Denmark and Bethlehem.
Valid task for the Project provided. This is not

TASK Optional applicable for Denmark and Bethlehem.
Total item cost for the specific item, user to provide,

it is in functional currency which is DKK for Denmark
Unit Cost Required and US$ for Bethlehem.
Material cost
This is applicable to all the items, the value for

material cost must be lesser or equal to the item unit
cost
Material Cost Required
Material Overhead Cost
Currently FLSmidth is not using any material

Material Overhead Optional overhead
Outside Processing Cost
This is only applicable to semi-finished or finished

items which have outside processing operation in
their routing, the value for OSP cost must be less to
the item unit cost
OSP Optional
Resource Cost

items which have resource usage incurred in WIP,
the value for Resource cost must be less to the item
unit cost
Resource Optional
Overhead Optional Overhead Cost

items which have overhead usage incurred in WIP,
File Ref: 351028461 (v. 1.0 )

the value for Overhead cost must be less to the item

unit cost
REASON_CODE Optional Valid reason code
COMMENTS Optional Any comments need to provide for the transaction.
File Ref: 351028461 (v. 1.0 )

Open and Closed Issues for this Deliverable
Open Issues
ID Issue Resolution Responsibility Target Impact

Date Date
1 Lead time need to provide to add any Carsten TBD

item in Enovia and push same to Giesel/Rathakrishn
Oracle. an Jayabalan
2 Current on hand data with PDB number Pia Bubandt 04-Aug-2012

& UOM required to migrated need to Mortensen
provide by business, To make a pre-
check on missing items in Enovia
3 Locator Values need to decided and Pablo S. Perez TBD

setup in system.
4 Inventory Adjustment Process need to Pablo S. Perez TBD

setup after R2 go live to move the
inventory between Oracle and old
system as per interim process
requirement.
5 Spare parts lead to be announced Tom HJensen TBD
6 Country of Origin to migrate with on Pablo S. Perez TBD

hand data and should be able to
provide details from Oracle.
Closed Issues
ID Issue Resolution Responsibility Target Impact

Date Date
File Ref: 351028461 (v. 1.0 )

File Ref: 351028461 (v. 1.0 )

CV040 Onhand Qty-V1.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CV040 Onhand Qty-V1.0

Uploaded by

Copyright:

Available Formats

AIM

CV.040 CONVERSION DATA

Author: Anshul Kumar

Creation Date: July 13, 2012

Document Ref: <Document Reference Num>

Error: Reference source not found

Date Author Versio Change Reference

13-Jul- Anshul Kumar Draft No Previous Document

09-Aug- Anshul Kumar 1.0 Modified based on the review comments.

Pablo S. Perez Solution Architect-SCM

Janne Stegemann Business Lead Back Office

Pia Bubandt Mortensen Business Lead- Valby

Jacqueline Hoefer Business Lead- Bethlehem

Michael Fisher Conversion Manager

Tom Jensen Project Manager

Rathakrishnan Jayabalan Assistant Manager.ESD Group for Enovia

Onhand Inventory Conversion Approach 2227192

File Ref: 351028461 (v. 1.0 )

Error: Reference source not found

Copy Name Location

1 Library Master Project Library

Onhand Inventory Conversion Approach 2327193

File Ref: 351028461 (v. 1.0 )

Error: Reference source not found

Scope and Assumption...............................................................................5

Interface Process Stages...........................................................................12

Technical Information Onhand Inventory................................................13

Extract File Layout....................................................................................17

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

File Ref: 351028461 (v. 1.0 )

Error: Reference source not found

Onhand Inventory Conversion Approach 2527195

File Ref: 351028461 (v. 1.0 )

Onhand Inventory Conversion Approach 2627196

File Ref: 351028461 (v. 1.0 )

Scope and Assumption

No Project specific inventory will be migrated.

This document will include various process related to on hand. Process

Onhand Inventory Conversion Approach 2727197

File Ref: 351028461 (v. 1.0 )

FLSmidth users. Any additional data required by non-Oracle

Pre-requisites in this document are defined and validated by

On hand data & other related details provided by the business is

Mapping of PDB number to new item number generated by enovia is

Current inventory has only material cost of items.

Onhand Inventory Conversion Approach 2827198

File Ref: 351028461 (v. 1.0 )

Project data is loaded if project specific inventory is required to load.

Conversion account is setup.

Onhand Inventory Conversion Approach 2927199

File Ref: 351028461 (v. 1.0 )

The Transaction Open Interface API (mtl_transactions_interface) will be used to load

Developers to utilized designed file format as attached in this document.

Custom validation will be applied on the custom table before moving it

Reference Oracle manual Manufacturing APIs and Open Interfaces

Reference Metalink article Sample WMS Open Interface Insert Scripts /

Request should process only one inventory organization record based on

Source will be selected Miscellaneous Receipt if quantity is positive and

Sysdate will be taken for transaction_date if not provided.

Validation is provided in the separate section.

Onhand Inventory Conversion Approach 210271910

File Ref: 351028461 (v. 1.0 )