Professional Documents
Culture Documents
Author : S S S Krishna.M
Approvals:
Kunal Mitra
Upal Mandal
Ankur Singhal
MD.070 Application Extension Technical Design Doc Ref: MD050 Data Migration_V1 0
March 10, 2009
Document Control
Change Record
3
Reviewers
Name Position
Distribution
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.
Contents
Document Control........................................................................................................ ii
Technical Overview..................................................................................................... 4
Installation Requirements.......................................................................................... 14
Implementation Notes................................................................................................ 15
Design Summary................................................................................................. 15
Coding Summary................................................................................................ 15
Testing Summary................................................................................................ 16
Installation........................................................................................................... 16
Open and Closed Issues for this Deliverable.............................................................17
Open Issues........................................................................................................ 17
Closed Issues...................................................................................................... 17
Technical Overview
This document defines the technical components required to implement Data Migration for
Supplier Master. This Application Extension Technical Design document complements the
Application Extension Functional Design document for Data Migration for Supplier Master and
you should consider the set to be the complete detailed design.
Data Migration for Supplier Master includes the following concurrent programs:
BEL SQL Loader For AP SQL Loader for Loading Bel Payables Navigator
Supplier Import Legacy Data to Staging Table
BEL Supplier and Site Upload Program Used for moving Bel Payables Navigator
Program Supplier and corresponding
Sites from Staging Table to
Interface Table
Supplier Open Interface Import Standard Concurrent Program Bel Payables Navigator
for moving Supplier from
Interface To Base Table.
Supplier Sites Open Interface Standard Concurrent Program Bel Payables Navigator
Import for moving Sites from Interface
To Base Table.
FND_CURRENCIES X
HR_LOCATIONS_ALL X
FND_LOOKUP_VALUES X
GL_CODE_COMBINATIONS X
FND_TERRITORIES X
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_AP_SUP_CTL.ctl
STEP2: Move the Data File to the CUSTOM application Server Path Below
Or
Or
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 Supplier and Site Upload Program
STEP5: Run the Standard Concurrent Program move Supplier Data from Interface to Base Table.
Concurrent Program name: Supplier Open Interface Import
Parameters:
1. Import Options : NEW
2. Batch Size : 1000
3. Print Exceptions Only : NO
4. Debug Switch : NO
5. Trace Switch : NO
STEP6: Run the Standard Concurrent Program move Supplier Sites Data from Interface to Base Table.
Concurrent Program name: Supplier Sites Open Interface Import
Parameters:
1. Import Options : NEW
2. Batch Size : 1000
3. Print Exceptions Only : NO
4. Debug Switch : NO
5. Trace Switch : NO
SQL Statements
Note: The Attachment below contains querry through which the supplier and the site information loaded into the base table
can be querried.
PROD_SUPPLIER_OUTPUT_QUERRY_01APR09.txt
Validation Logic
At Supplier Level
1. Payment Method Validation to check Valid Payment Method from IBY_PAYMENT_METHODS_TL table.
3. Supplier validation to check duplication of supplier in the interface table from AP_SUPPLIERS_INT table.
4. Supplier Type validation to check supplier type exists in PURCHASING LOOK UP created
“VENDOR TYPE” (NOTE: The vendor type must not be “EMPLOYEE”, as employee as supplier is not created using
this package.)
1. Duplication of Supplier Site combination is checked in Interface tables namely AP_SUPPLERS_INT and
AP_SUPPLIER_SITES_INT.
2. Duplication of Supplier Site combination is checked in Base tables namely AP_SUPPLERS and
AP_SUPPLIER_SITES_ALL.
4. Payment Term validation to check valid payment term and return term id from AP_TERMS_TL table.
5. Term Date Basis validation to check valid term date basis from FND_LOOKUP_VALUES table where
LOOKUP_TYPE is ‘TERMS DATE BASIS’.
6. Pay Date Basis validation to check valid Pay date basis from FND_LOOKUP_VALUES table where LOOKUP_TYPE
is ‘PAY DATE BASIS’.
7. Payment Method Validation to check Valid Payment Method from IBY_PAYMENT_METHODS_TL table.
9. Ship to Location validation to check valid ship to location and return the location_id from HR_LOCATIONS_ALL
table.
10. Bill to Location validation to check valid Bill to location and return the location_id from HR_LOCATIONS_ALL table.
11. Pay group validation to check valid pay group from FND_LOOKUP_VALUES table where LOOKUP_TYPE is ‘PAY
GROUP’.
12. Liability account validation to check the given code comination exists or not.if not then code combination to be
created using ‘fnd_flex_ext.get_ccid’ API.
13. Prepay account validation to check the given code comination exists or not.if not then code combination to be
created using ‘fnd_flex_ext.get_ccid’ API.
14. Future Dated account validation to check the given code comination exists or not.if not then code combination to be
created using ‘fnd_flex_ext.get_ccid’ API.
(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.)
15. Freight Term validation to check valid Freight Term from FND_LOOKUP_VALUES table where LOOKUP_TYPE is
‘FREIGHT TERMS’.
17. Please check the column PROCESS_FLAG in both the staging tables i.e.
XXBEL.XX_BEL_AP_SUPPLIER_DET_TBL and XXBEL.XX_BEL_AP_SUPPLIER_SITES_TBL are set to ‘N’ as the
custom concurrent program considers these records as NEW records and processes them.
18. Please check the column ‘STATUS’ in the interface tables AP_AUPPLIERS_INT AND AP_SUPPLIER_SITES_INT is
NULL,so that these records are identified as ‘NEW’ records by the standard concurrent program and will be
processed.
Incompatibility1
1. Supplier must be created initially and then only sites can be created for that supplier.
Performance Considerations
None
Other Considerations
None
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 Supplier Master.
Package
XX_BEL_AP_SUP_NEW_INT_PKG
This Package is having one procedure “XX_BEL_AP_SUP_INT_PRO” and is registered with the Concurrent program
Namely “BEL Supplier and Site Upload Program”.
PROCEDURE XX_BEL_AP_SUP_INT_PRO:
This procedure selects the Data from the staging Table like supplier name, supplier site, address, ship to, bill to etc, validates
them and inserts the data into the interface tables.
The following are the validations done on the datain the staging tables
At Supplier Level
1. Payment Method Validation to check Valid Payment Method from IBY_PAYMENT_METHODS_TL table.
3. Supplier validation to check duplication of supplier in the interface table from AP_SUPPLIERS_INT table.
4. Supplier Type validation to check supplier type exists in PURCHASING LOOK UP created
“VENDOR TYPE” (NOTE: The vendor type must not be “EMPLOYEE”, as employee as supplier is not created using
this package.)
1. Duplication of Supplier Site combination is checked in Interface tables namely AP_SUPPLERS_INT and
AP_SUPPLIER_SITES_INT.
2. Duplication of Supplier Site combination is checked in Base tables namely AP_SUPPLERS and
AP_SUPPLIER_SITES_ALL.
4. Payment Term validation to check valid payment term and return term id from AP_TERMS_TL table.
5. Term Date Basis validation to check valid term date basis from FND_LOOKUP_VALUES table where
LOOKUP_TYPE is ‘TERMS DATE BASIS’.
6. Pay Date Basis validation to check valid Pay date basis from FND_LOOKUP_VALUES table where LOOKUP_TYPE
is ‘PAY DATE BASIS’.
7. Payment Method Validation to check Valid Payment Method from IBY_PAYMENT_METHODS_TL table.
9. Ship to Location validation to check valid ship to location and return the location_id from HR_LOCATIONS_ALL
table.
10. Bill to Location validation to check valid Bill to location and return the location_id from HR_LOCATIONS_ALL table.
11. Pay group validation to check valid pay group from FND_LOOKUP_VALUES table where LOOKUP_TYPE is ‘PAY
GROUP’.
Data Migration For Supplier Master Technical Overview 7 of 16
File Ref: (version 1.0)
Company Confidential - For internal use only
Doc Ref: MD050 Data Migration_V1 0
March 10, 2009
12. Liability account validation to check the given code comination exists or not.if not then code combination to be
created using ‘fnd_flex_ext.get_ccid’ API.
13. Prepay account validation to check the given code comination exists or not.if not then code combination to be
created using ‘fnd_flex_ext.get_ccid’ API.
14. Future Dated account validation to check the given code comination exists or not.if not then code combination to be
created using ‘fnd_flex_ext.get_ccid’ API.
(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.)
15. Freight Term validation to check valid Freight Term from FND_LOOKUP_VALUES table where LOOKUP_TYPE is
‘FREIGHT TERMS’.
16. FOB validation to check valid FOB from FND_LOOKUP_VALUES table where LOOKUP_TYPE is ‘FOB’.
Custom Table
For the supplier and site upload custom program two custom tables are used as a supplier can have multiple sites, so to
implement one to many relationship multiples tables are considered i.e. one table for supplier details and the other for
supplier site details.
The 1st table contins supplier details and the 2nd table contains supplier site details.the link between these two tables is the
supplier name.
1. XXBEL.XX_BEL_AP_SUPPLIER_DET_TBL
2. XXBEL.XX_BEL_AP_SUPPLIER_SITES_TBL
One more table is taken to capture errors for the particular record both at the supplier and site table i.e.
XXBEL.XX_BEL_AP_SUP_INT_ERRORS
Custom Sequences
To identify the errors record wise two custom sequences are used.
The 1st sequence is used to as the join between the error table and the supplier table i.e.
XXBEL.XX_BEL_AP_SUPPLIER_DET_TBL so that error can be pointed out to the particular record.
The 2nd sequence is used as a join between the error table and supplier site table i.e.
XXBEL.XX_BEL_AP_SUPPLIER_SITES_TBL so that error can be pointed out to the particular record.
1. XX_BEL_AP_SUP_INT_S
2. XX_BEL_AP_SUP_SITES_INT_S.
CASHIER Cashier
COMPANY Company
EMPLOYEE Employee
INSURANCE Insurance
PARTNERSHIP Partnership
TRANSPORTER Transporter
TRUST Trust
VENDOR Supplier
Invoice Invoice
DUE Due
DISCOUNT Discount
DUE Due
002 Luminaires
003 EPBU
004 Appliances
005 Fans
006 Corporate
008 Perks
Allowed Allowed
Due Due
OPM OPM
Paid Paid
Prepaid Prepaid
RLWY RLWY
SHIP SHIP
TBD TBD
BUY Buyer
EX_GODOWN Ex.Godown
FACTORY Factory
SEL Seller
Installation Requirements
Installation scripts must be prepared to perform the following actions in an automated way:
Implementation Notes
This document describes Data Migration for Supplier Master and implemented at Bajaj Electricals Ltd.
Design Summary
Functional Design
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:
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/
BEL_Supplier_and_Sites_upload_custom_pkg.sql
Mesg/
Reports/
Log/
Out/
Data/
Open Issues
Closed Issues