AIM

MD.070 APPLICATION EXTENSION

TECHNICAL DESIGN
BAJAJ ELECTRICALS LIMITED.

Author : S S S Krishna.M

Creation Date : Mar 10, 2009

Last Updated :
Version : 1.0

Approvals:

Kunal Mitra

Ankur Singhal

Upal Mandal
MD.070 Application Extension Technical Design Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Document Control

Change Record
3

Date Author Version Change Reference

10-mar-2009 S S S Krishna.M Version 1.0 No Previous Document

Reviewers

Name Position

Kunal Mitra Technical Lead

Ankur Singhal Procurement Lead
Upal Mandal Finance Lead

Distribution

Copy No. Name Location

1
Library Master Project Library
2 BEL Project Manager BEL Project Site
3 Oracle Project Manager Oracle Project Site

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.

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: MD.070 Application Extension Technical Design (version 1.0)
Company Confidential - For internal use only
MD.070 Application Extension Technical Design Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Contents

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

Technical Overview..................................................................................................... 4

Concurrent Program Logic........................................................................................ 4

Table and View Usage...........................................................................................5
Program Logic (pseudo code)...............................................................................5
SQL Statements.................................................................................................... 6
Default Data Sources............................................................................................ 7
Validation Logic..................................................................................................... 7
Incompatibility....................................................................................................... 7
Performance Considerations.................................................................................7
Other Considerations............................................................................................8
Integration Issues........................................................................................................ 8
Changes Required................................................................................................8
Shared Components............................................................................................. 8
Alert conditions...................................................................................................... 8
Incompatibilities.................................................................................................... 9
Performance Issues..............................................................................................8
Database Design......................................................................................................... 8

Installation Requirements.......................................................................................... 11

Implementation Notes................................................................................................ 12
Design Summary................................................................................................. 12
Coding Summary................................................................................................ 12
Testing Summary................................................................................................ 12
Installation........................................................................................................... 12
Open and Closed Issues for this Deliverable.............................................................14
Open Issues........................................................................................................ 14
Closed Issues...................................................................................................... 14

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: MD.070 Application Extension Technical Design (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Technical Overview
This document defines the technical components required to implement Data Migration for
Onhand Upload. This Application Extension Technical Design document complements the
Application Extension Functional Design document for Data Migration for Onhand Upload and
you should consider the set to be the complete detailed design.

Concurrent Programs Logic

Data Migration for Onhand includes the following concurrent programs:

Program Name Purpose Responsibility

BEL SQL Loader For Onhand SQL Loader for Loading Bel Inventory Navigator
Upload Program Legacy Data to Staging Table

BEL OnHand Upload Program Program Used for moving On- Bel Inventory Navigator
hand data from Staging Table to
Interface Table

Process transaction interface Standard Concurrent Program Bel Inventory Navigator

for moving Onhand data from
Interface To Base Table.

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Table and View Usage

Table Name Select Insert Update Delete

MTL_MATERIAL_TRANSACTIONS X
MTL_PARAMETERS X
MTL_SYSTEM_ITEMS_B X
MTL_TRANSACTION_TYPES X
MTL_TXN_SOURCE_TYPES X
MTL_SECONDARY_INVENTORIES X

MTL_UNITS_OF_MEASURE X
MTL_ITEM_LOCATIONS X
ORG_ACCT_PERIODS_V X
GL_CODE_COMBINATIONS X
FND_CURRENCIES X
MTL_TRANSACTION_LOTS_INTERFACE X X
MTL_TRANSACTIONS_INTERFACE X X
MTL_ONHAND_QUANTITIES_DETAIL X

Program Logic (pseudo code) Onhand Upload.

STEP1: Prepare Data File in CSV (Comma Seperated Value) Format and save it in word format
(Note1 Please ensure the data is saved properly in Word format)
(Note2 Order of the Data column wise must match with the column order in the CTL file.For reference the control
file is attached below.)

Or
STEP1: Prepare Data File in CSV (Comma Seperated Value) Format.
(Note: Order Of the Data column wise must match with the column order in the CTL file.For reference the control
file is attached below.)

XX_BEL_INV_OHNAND_CTL.ctl

STEP2: Move the Data File to the CUSTOM application Server Path Below

PATH: /belebizappl/apps/apps_st/appl/xxbel/12.0.0/data/ <data filename>.csv

Or

PATH: /belebizappl/apps/apps_st/appl/xxbel/12.0.0/data/ <data filename>.txt

(Note: Above paths given refer to same location, only the data file format is changed)

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

STEP3: Run the following CUSTOM Concurrent Program for moving data to staging tables.
Concurrent Program name BEL SQL Loader For Onhand Upload Program.
Parameters:
1. Enter Path: Following are the Data file paths where the data is located in Server

PATH: /belebizappl/apps/apps_st/appl/xxbel/12.0.0/data/ <data filename>.csv

Or

PATH: /belebizappl/apps/apps_st/appl/xxbel/12.0.0/data/ <data filename>.txt

(Note: Above paths given refer to same location, only the data file format is changed)

Note: Please check the data inserted into the staging table column wise has been
populated properly.

STEP4: Run the following CUSTOM Concurrent Program for moving data to Interface tables
From staging tables
Concurrent Program name: BEL OnHand Upload Program

STEP5: Run the Standard Concurrent Program to move Onhand Data from Interface to Base Table.
Concurrent Program name: Process transaction interface

SQL Statements
Note: The Attachment below contains querry through which the Onhand Upload information loaded into the base table can be
querried.

on-hand_Querry.txt

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009
Default Data Sources
None

Validation Logic

1. Organization Validation to check Valid Organization from MTL_PARAMETERS table.

2. Item validation to check Valid Item from MTL_SYSTEM_ITEMS_B table.

3. Transaction Type validation to check valid Transaction Type from MTL_TRANSACTION_TYPES table.

4. Transaction Source Type validation to check valid Transaction Source Type from MTL_TXN_SOURCE_TYPES table.

5. Sub-Inventory validation to check valid Sub-Inventory from MTL_SECONDARY_INVENTORIES table.

6. Unit of Measure validation to check valid Unit of Measure from MTL_UNITS_OF_MEASURE table.

7. Debit account for onhand upload validation.In this initially natural account of given debit account is checked against
the natural account of transaction type,if it is matching then that code combination given is valid else the natural
account is replaced with the natural account of transaction type and then the code combination will be validated.If
code combination is not existing,it will be created using API namely “fnd_flex_ext.get_ccid” (Note: The
above API mentioned will create code combination id for the given code combinations if it does not exists else it will
return the existing code combination id.)

8. Lot Control validation to check whether item is lot controlled or not from MTL_SYSTEM_ITEMS_B table.

9. Locator validation to check valid locator.Initially the BU (Buisiness Unit) given in the locator must match with the BU
in which the onhand is loaded for that record.Then the locator will be validated from MTL_ITEM_LOCATIONS 
table,if it is not existing then it will be created using “inv_LOC_WMS_PUB.CREATE_LOCATOR” API.

10. Transaction date should be in the open periods of that organization given which is checked against
ORG_ACCT_PERIODS_V table.

11. Currency should be a valid currency which is checked against the FND_CURRENCIES table.

12. Please check the column PROCESS_FLAG in the staging table i.exxbel.XX_BEL_INV_MISCREP_STG_TABLE is
set to ‘N’ as the custom concurrent program considers these records as NEW records and processes them.

13. Please check the column ‘PROCESS_FLAG’ in the interface tables MTL_TRANSACTIONS_INTERFACE and
MTL_TRANSACTION_LOTS_INTERFACE is ‘1’, so that these records are identified as ‘NEW’ records by the standard
concurrent program and will be processed.

Incompatibility1
None

Performance Considerations
None

Other Considerations
None

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009
Integration Issues

Changes Required

Within Product
No changes required

Other Products
No changes required

Shared Components

Alert conditions
None

Incompatibilities
None

Performance Issues
None

Database Design
This section summarized new and changed database objects and data required to Data base Migration for Onhand upload.

Package

XX_BEL_INV_MISCREP_NEW_PKG
This Package is having one procedure “XX_BEL_INV_MISCREPT_PRO” and is registered with the Concurrent program
Namely “BEL OnHand Upload Program”.

PROCEDURE XX_BEL_INV_MISCREPT_PRO:
This procedure selects the Data from the staging Table like item, organization, currency, transaction date etc, validates them
and inserts the data into the interface tables.
The following are the validations done on the datain the staging tables

1 Organization Validation to check Valid Organization from MTL_PARAMETERS table.

2 Item validation to check Valid Item from MTL_SYSTEM_ITEMS_B table.

3 Transaction Type validation to check valid Transaction Type from MTL_TRANSACTION_TYPES table.

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009
4 Transaction Source Type validation to check valid Transaction Source Type from MTL_TXN_SOURCE_TYPES table.

5 Sub-Inventory validation to check valid Sub-Inventory from MTL_SECONDARY_INVENTORIES table.

6 Unit of Measure validation to check valid Unit of Measure from MTL_UNITS_OF_MEASURE table.

7 Debit account for onhand upload validation.In this initially natural account of given debit account is checked against
the natural account of transaction type,if it is matching then that code combination given is valid else the natural
account is replaced with the natural account of transaction type and then the code combination will be validated.If
code combination is not existing,it will be created using API namely “fnd_flex_ext.get_ccid” (Note: The
above API mentioned will create code combination id for the given code combinations if it does not exists else it will
return the existing code combination id.)

8 Lot Control validation to check whether item is lot controlled or not from MTL_SYSTEM_ITEMS_B table.

9 Locator validation to check valid locator.Initially the BU (Buisiness Unit) given in the locator must match with the BU
in which the onhand is loaded for that record.Then the locator will be validated from MTL_ITEM_LOCATIONS table,if
it is not existing then it will be created using “inv_LOC_WMS_PUB.CREATE_LOCATOR” API.

10 Transaction date should be in the open periods of that organization given which is checked against
ORG_ACCT_PERIODS_V table.

11 Currency should be a valid currency which is checked against the FND_CURRENCIES table.

12. Please check the column PROCESS_FLAG in the staging table i.exxbel.XX_BEL_INV_MISCREP_STG_TABLE is
set to ‘N’ as the custom concurrent program considers these records as NEW records and processes them.

13. Please check the column ‘PROCESS_FLAG’ in the interface tables MTL_TRANSACTIONS_INTERFACE and
MTL_TRANSACTION_LOTS_INTERFACE is ‘1’, so that these records are identified as ‘NEW’ records by the standard
concurrent program and will be processed.

Custom Table
For the Onhand upload custom program one custom table namely XXBEL.XX_BEL_INV_MISCREP_STG_TABLE

One more table is taken to capture errors for the particular record in XXBEL.XX_BEL_INV_MISCREP_STG_TABLE i.e.

XXBEL.XX_BEL_AP_SUP_INT_ERRORS

Custom Sequences

To identify the errors record wise one custom sequence is used.

The sequence is used as a join between the error table and onhand table i.e.
XXBEL.XX_BEL_INV_MISCREP_STG_TABLE so that error can be pointed out to the particular record.

XX_BEL_AP_SUP_INT_S.

New/Updated Seed Data

1. Transaction type “Onhand Upload” is created.

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Installation Requirements
Installation scripts must be prepared to perform the following actions in an automated way:

 Create new staging table.

 Create new packages, functions and procedures.
 Create concurrent program for procedure.
 Attach concurrent program to the request group.

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Implementation Notes
This document describes Data Migration for onhand upload and implemented at Bajaj Electricals Ltd.

Design Summary

Functional Design

Functional Design Approval

Technical Design
Krishna.M.S.S.S

Design Review

Final Acceptance

Coding Summary
Development was done on Windows Operating System, to work with Release 12.0.6 of Oracle Applications. All coding
follows the standards defined in the Build Standards document for BEL.

Program Files
The files required for this customization are as follows:

File Description Coded By

Onhand_upload_pkg.sql Package created for Onhand upload S S S Krishna.M

XX_BEL_AP_SUP_CTL.ctl Control file created for moving data in staging S S S Krishna.M

table

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Testing Summary

Installation
All modules are installed as if part of a separate product. A UNIX directory structure is created
under $APPL_TOP as shown in the following example:
$APPL_TOP
|
XXBEL
|
12.0.0
___________________________|___________________________________
| | | | | | | | |
Forms bin admin sql log out data reports mesg

The directories contain the components of the enhancement as shown below (directories not
listed are empty). All future customizations will also be stored in these directories.
Forms/
Bin/
Admin/
Sql/

Onhand_upload_pkg.sql
Mesg/
Reports/
Log/
Out/
Data/

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only
 Doc Ref: MD050 Data Migration_V1 0
March 10, 2009

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact

Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact

Date

Data Migration For Onhand Upload Technical Overview 1 of 13

File Ref: (version 1.0)
Company Confidential - For internal use only