Escolar Documentos
Profissional Documentos
Cultura Documentos
CV.060 CONVERSION
TECHNICAL DESIGN
GM DC
Fixed Assets Conversion
Document Control
Change Record
23
Reviewers
Name Position
Distribution
1
Library Master Project Library
2 Project Manager
3
4
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...................................................................................................................2
Introduction..............................................................................................................................4
Conversion Program........................................................................................................4
Century Date Compliance...............................................................................................4
Conversion Assumptions.......................................................................................................6
Scope..........................................................................................................................................9
Approach.................................................................................................................................10
Conversion Tables..........................................................................................................11
Ordering of Tables..........................................................................................................11
Dependencies..................................................................................................................11
Design Rules...........................................................................................................................12
Program Logic........................................................................................................................15
Introduction
This document defines the technical design and specifications required for the
fixed assets data conversion to convert assets from GMDCs Legacy systems to
the Oracle E-Business Suite.
Taconic will provide all the valid assets data in the form of extract files, which
will be input to Oracle fixed assets conversion program.
Fixed Assets conversion will load the assets data, validate the data and then
create them in Oracle Fixed Assets.
Conversion Program
This Conversion Program Technical Design defines the key assumptions, rules,
and logic that are needed to create the conversion programs. The conversion
program code is not included in this document. The Develop Conversion
Programs (CV.080) task contains the actual code that is written and debugged to
perform the conversion. The conversion design document is intended to provide
the developer with the necessary information for writing accurate conversion
programs.
Conversion Assumptions
2. The fixed assets conversion program will be used for inserting the assets data
into base tables and not for updating the existing asset data.
3. The data file will be in the format specified in CV040 doc irrespective of the
data source.
4. There will be one pipe (|) delimited file for this conversion
7. All the required setups for this conversion will be completed before the
program is run.
9. No changes are done to the data files without prior notification to the
Caggemini technical team after they are transferred to the required directory
for upload.
10. The SQL*Loader will upload the records in the truncate mode, which means
all the previous records present in the staging table will be truncated, and the
staging table will be loaded with new records.
11. Bad, Discard and Log files are created in the $XXGMDC_TOP/bin directory.
Any file present in the $GMDC_TOP/bin with these names will be
overwritten with bad, log and discard file generated by the SQL*Loader.
12. All database objects like packages, procedure, functions, views, tables, etc
will be created in the XXGMDC schema.
13. The concurrent manager must be running in the applications before we can
run the Conversion program.
15. Depreciation Method and Life of every asset will be coming from Asset
Category Setup.
16. Depreciation methods, lives, prorate of existing legacy assets will not be
changed during the conversion.
17. The Asset Clearing Account will be providing by GMDC team. This is the
natural account for the Payables Code Combination. All other segments of
the combination will be derived from the asset Expense Account code
combination.
18. The Natural Account segment used by the seeded FA Account Generator
will be the assets cost account and depreciation reserve accounts based on
setup of the Asset Category. As part of standard functionality of Oracle
Assets, assets belonging to a particular Asset Category will be assigned the
default depreciation method and rate and life for that Category when posted
into Oracle Assets.
19. Extracted assets have been posted and reconciled to legacy General Ledger
balances. Detail and summary reports are available to support these
balances.
20. Each legacy asset will be converted with as one fixed asset unit (DEFAULT
VALUE = 1).
21. Asset currency code will default from the functional currency of the GL set
of book defined for the Asset book.
22. Asset tag numbers (if used) will be unique. Duplicate tag numberss record
will not load in the base table.
24. Cannot have LTD depr with zero cost. In the event of this error, the LTD
depreciation will be changed to be zero.
25. Assets in Oracle cannot be assigned to more than one category. The
conversion will process each category assignment as an individual asset.
26. Data cleansing will be performed by GMDC prior to submitting the data
extract.
The instance has been set up to accommodate the Oldest Asset Date
placed in services for GMDC.
The mapping is key elements has been identified and set up specifically
depreciations methods; asset locations, asset key and asset categories.
Scope
The following boundaries are specific to the conversion of the Fixed Assets
Conversion:
The scope of the conversion is to load data from the data files to the staging
tables, validate the data and then load the data into Interface tables.
The extract will contain the entire necessary Asset data elements required as
outlined in this design to successfully create an Asset in Oracle Assets.
Data cleansing will have been carried out on the source systems in time for the
conversion.
Where any derivation rules fail the validation step, the record will be erroring
out.
XXTA_FA_MASS_ADDITIONS_STG
None
None
None
Approach
The solution for this conversion requirement can be broken into two parts, the
loading of data into the temporary staging tables and the processing and
translation of that data before it is passed to interface to populate standard
Oracle base tables.
Data supplied in pipe delimited flat files (.cvs) and the format will be as defined
in the CV040.
The data files are loaded into the staging table using the host program that will
execute SQL LOADER. Once data file has been processed, any SQL Loader log
files, discard files, and bad files should be concatenated together and copied to
the appropriate directory and file where the user may review them. After each
run, the load program should accomplish any necessary cleanup.
The second step is the data validation program. This PL/SQL based program
should be able to select records from staging tables and process those records
before processing them using open interface. All incoming data file will be
written to a staging table by the load program. The validation program will select
these records and process them accordingly. The validation program will have
to maintain counts for total records processed, total records with errors, total
errors and total records with zero value. The program should also identify any
records with errors on the execution report.
The validation program should be run from within Oracle Applications. This
program will need an execution record, a defined concurrent program and be
attached to a request group.
Once the data in staging table is validated and valid data is inserted into
standard base table by using oracle oracle standard API.
Conversion Approach
Create one staging table.
XXTA_FA_MASS_ADDITIONS_STG
Asset data from the flat file will be inserted into the staging table using
the host program.
Once the staging table is populated the conversion package will perform
the necessary validations.
Validation is done for the records having process_flag equal to V as
VALIDATE or R as ERROR in the staging.
Records which are successfully processed will have the process_flag =
L as LOADED while error records will have the process_flag = R as
ERROR.
If any validation fails then the error is recorded in the error tables with
the appropriate error messages.
Every time the conversion program is run a summary report is created
that will tell the total count of records read, the number of records
processed and the number of records errored.
This process is continued until all the records are successfully processed
through standard API to create records in assets base tables.
Conversion Tables
The following tables are going to be populated in the Oracle application for the
conversion of Assets:
XXGMDC_FA_ADDITIONS_STG X X X X
XXGMDC_LOG_HEADERS X X
XXGMDC_LOG_LINES X X
FA_BOOK_CONTROLS X
FA_ADDITIONS_B X X
FA_CATEGORIES_B X
FA_ASSET_KEYWORDS X
FA_LOOKUPS_B X
FA_METHODS X
FA_FLAT_RATES X
FA_CONVENTION_TYPES X
FA_LOCATIONS X
GL_CODE_COMBINATIONS X
Ordering of Tables
Below is the order in which the tables need to be populated for the conversion of
Assets
XXGMDC_FA_ADDITIONS_STG
XXGMDC_LOG_HEADERS
XXGMDC_LOG_LINES
Dependencies
FA_CATEGORIES_B
FA_LOCATIONS
FA_ASSET_KEYWORDS
FA_BOOK_CONTROLS
FA_SYSTEM_CONTROLS
FA_METHODS
FA_CONVENTION_TYPES
FA_LOOKUPS_B
GL_CODE_COMBINATIONS
FA_FLAT_RATES
None
Parent/Child Dependencies
None
None
None
None
Design Rules
This section lists the processing rules, translation rules, derivation rules, foreign key rules that are
to be used in the conversion of assets:
Processing Rules
Program Logic
None.
This section describes the logic for the conversion table creation programs that
will be built to support the conversion of Assets.
ASSET_ID NUMBER,
ASSET_NUMBER
VARCHAR2(15),
TAG_NUMBER
VARCHAR2(15),
DESCRIPTION
VARCHAR2(80),
CATEGORIE_SEGMENT1 VARCHAR2(30),
CATEGORIE_SEGMENT2 VARCHAR2(30),
CATEGORIE_SEGMENT3 VARCHAR2(30)
DEFAULT 'FUT',
ATTRIBUTE_CATEGORY_CODE VARCHAR2(210),
ASSET_CATEGORY_ID NUMBER,
ASSET_KEY_SEGMENT1 VARCHAR2(30),
ASSET_KEY_SEGMENT2 VARCHAR2(30),
ASSET_KEY_SEGMENT3 VARCHAR2(30),
ASSET_KEY_SEGMENT4 VARCHAR2(30),
ASSET_KEY_CODE VARCHAR2(120),
LEASE_NUMBER
VARCHAR2 (150),
LESSOR
VARCHAR2 (150),
WARRANTY_NUMBER
VARCHAR2 (150),
BASIC_RATE NUMBER
NOT NULL,
ASSETS_COST NUMBER,
SALVAGE_VALUE NUMBER
DEFAULT 0,
SALVAGE_VALUE_TYPE_CODE VARCHAR2(3),
ORIGINAL_COST NUMBER
NOT NULL,
BEGINNING_NBV NUMBER,
YTD_DEPRN_COST NUMBER,
ACCUMULATED_COST NUMBER,
REVAL_RESERVE NUMBER,
REVAL_CEILING NUMBER,
DATE_PLACED_IN_SERVICE DATE
NOT NULL,
AMORTIZATION_START_DATE DATE,
SHORT_FISCAL_YEAR_FLAG DATE,
CONVERSION_DATE DATE,
ORIGINAL_DEPRN_START_DATE DATE,
LOCATION_CCID NUMBER,
EXPENSE_ACC_CCID NUMBER,
ATTRIBUTE11 NUMBER,
ATTRIBUTE12 NUMBER,
ATTRIBUTE13 NUMBER,
ATTRIBUTE14 NUMBER,
ATTRIBUTE15 NUMBER,
ATTRIBUTE16 NUMBER,
CREATED_BY NUMBER,
CREATION_DATE DATE ,
LAST_UPDATED_BY NUMBER,
LAST_UPDATE_DATE DATE,
LAST_UPDATE_LOGIN NUMBER,
REQUEST_ID NUMBER,
PROCESSING_ROW_ID NUMBER,
PROCESSING_MESSAGE VARCHAR2(360)
The following is the control file (CTL) script, which will upload the data from the flat file to
the staging table (XXTA_FA_MASS_ADDITIONS_STG):
LOAD DATA
TRUNCATE
INTO TABLE XXGMDC_FA_ADDITIONS_STG
FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
(
TAG_NUMBER CHAR
"TRIM (:TAG_NUMBER)"
, DESCRIPTION
CHAR "TRIM (:DESCRIPTION)"
, CATEGORIE_SEGMENT1
CHAR "TRIM (:CATEGORIE_SEGMENT1)"
, CATEGORIE_SEGMENT2
CHAR "TRIM (:CATEGORIE_SEGMENT2)"
, CATEGORIE_SEGMENT3
CHAR "TRIM (:CATEGORIE_SEGMENT3)"
, DFF_SEGMENT_MAKE
CHAR "TRIM (:DFF_SEGMENT_MAKE)"
, DFF_SEGMENT_REG_NO
CHAR "TRIM (:DFF_SEGMENT_REG_NO)"
, DFF_SEGMENT_YEAR_MFG
CHAR "TRIM (:DFF_SEGMENT_YEAR_MFG)"
, DFF_SEGMENT_ENG_NO
CHAR "TRIM (:DFF_SEGMENT_ENG_NO)"
, DFF_SEGMENT_CHASIS_NO
CHAR "TRIM (:DFF_SEGMENT_CHASIS_NO)"
, DFF_SEGMENT_CUBIC_CAP
CHAR "TRIM (:DFF_SEGMENT_CUBIC_CAP)"
, DFF_SEGMENT_SUM_INSURED
CHAR "TRIM (:DFF_SEGMENT_SUM_INSURED)"
, ASSET_KEY_CODE
CHAR "TRIM (:ASSET_KEY_CODE)"
, ASSET_TYPE
CHAR "TRIM (:ASSET_TYPE)"
, MANUFACTURER_NAME
CHAR "TRIM (:MANUFACTURER_NAME)"
, IN_USE_FLAG
CHAR "TRIM (:IN_USE_FLAG)"
, INVENTORIAL
CHAR "TRIM (:INVENTORIAL)"
, PROPERTY_TYPE_CODE
CHAR "TRIM (:PROPERTY_TYPE_CODE)"
, OWNED_LEASED
CHAR "TRIM (:OWNED_LEASED)"
, NEW_USED
CHAR "TRIM (:NEW_USED)"
, BOOK_TYPE_CODE
CHAR "TRIM (:BOOK_TYPE_CODE)"
, ORIGINAL_COST
CHAR "TRIM (:ORIGINAL_COST)"
, ACCUMULATED_COST
CHAR "TRIM (:ACCUMULATED_COST)"
, SALVAGE_VALUE_TYPE
CHAR "TRIM (:SALVAGE_VALUE_TYPE)"
, DATE_PLACED_IN_SERVICE
CHAR "TRIM (:DATE_PLACED_IN_SERVICE)"
, DEPRECIATE_METHOD_CODE
CHAR "TRIM (:DEPRECIATE_METHOD_CODE)"
, BASIC_RATE
CHAR "TRIM (:BASIC_RATE)"
, PRORATE_CONVENTION_CODE
CHAR "TRIM (:PRORATE_CONVENTION_CODE)"
, CURRENT_UNITS
CHAR "TRIM (:CURRENT_UNITS)"
, EXPENSE_ACC_CODE_COMB
CHAR "TRIM (:EXPENSE_ACC_CODE_COMB)"
, LOCATION_CODE_COMB
CHAR "TRIM (:LOCATION_CODE_COMB)"
, DEPRECIATE_FLAG
CONSTANT 'YES'
, PROCESSING_STATUS
CONSTANT 'N'
, created_by
"FND_GLOBAL.USER_ID"
, creation_date
"SYSDATE"
, last_updated_by
"FND_GLOBAL.USER_ID"
, last_update_date "SYSDATE"
)
2. Validation of data is done in the staging table. The Staging table is as follows:
XXGMDC_FA_ADDITIONS_STG
3.If a record fails during data validation then errors are inserted into the error table
(XXGMDC_LOG_HEADERS & XXGMDC_LOG_LINES) and for the errored out record the
process_flag column in the staging tables will be updated to R. Error reporting will take care of
incorrect dates format, missing mandatory fields etc.
4. After validations are complete, the procedure is called to load the valid data into Oracle base
table for record that has been successfully validated without any errors. Oracle standard open
API will be used to create records in Oracle base tables.
5. All the loaded data in staging tables will be marked as LOADED (process_flag = L) in the
staging tables. Records with process_flag=R will not be processed in the stanging tables.
N/A
Describes the program logic for the interface/validation program(s) used to convert the business
object.
The conversion of Assets is initiated through a main program, which will in turn call rest of the
programs depend on success.
XXGMDC FA Asset Number Conversion Program is the wrapper program, which will
call the XXGMDC_FA_ADDITIONS_PKG.MAIN pl/sql program.
This procedure reads records from the staging table and assigns the request_id
and processing_row_id value to the staging table.
SUBMIT_CHILD
This procedure divides the records by their batch sizes and calls the prodedure.
This procedure calls the fa_number_main procedure.
REPORT_RESULTS
This procedure displays the record statistics from staging table.
MAIN
1. If data file parameter is given, call load program XXGMDC FA Asset Number -
Load Data, otherwise go to next step.
VALIDATE_FA_NUMBER_RECORDS
Declare
Declare all local variables
CURSOR cur_get_stg_data IS
SELECT * FROM XXGMDC_FA_ADDITIONS_STG
WHERE process_flag in (parameter value);
BEGIN
Initialize the error flag.
CREATE_FA_NUMBER
This procedure will insert valid records into base table by oracle standard API.
Ln_record_count := 0;
Ln_record_count := ln_record_count + 1;
For each asset record, call API with values from necessary c_asset columns.
END LOOP
End Loop
This section describes the logic for the error handling procedure that will be built
to support the conversion of assets.
The following are the procedures that will be used in handling of errors.
INSERT_ERROR procedure is used to insert all the error messages in to the log
table.
In case of any setup validation error, assign retcode: = 2. This is done so that the
program completes in error.
The data in the staging table are not deleted so that error records can be
identified if required. The SQL*Loader will delete data from the staging table
before loading data to prevent storing of duplicate data in staging table.
Note: The program should complete all data & apps setup related validations (mentioned in
validation section) before giving a consolidated error report. Program should list all data/setup
errors before stopping rather than stopping when first validation /setup error occurs. In case of
system errors, program should give the error message and stop execution (ret code=2).
Conversion Programs
The following table lists each program created for the conversion of Assets:
Program Type Program Name Description/Purpose Program Develope Flat File:/File Name and Location (if any)
Location r
Program Modules
Common Routine
Value Sets
None
Executables
Application XXGMDC
Subroutine Name
Application XXGMDC
Subroutine Name
Concurrent Programs
Application XXGMDC
Priority
Request Type
Style
Parameters:
Validation
Program Logic: Page 28 of 32
CV.060 Doc Ref GMDC CV040 Fixed Assets Conversion.doc
A)ll
50 p_test_rec Y 15 Digit Y Test
Process eligible
ords Number Recor
candidate rows
ds
Application XXGMDC
Priority
Validation
Program Logic: Page 29 of 32
CV.060 Doc Ref GMDC CV040 Fixed Assets Conversion.doc
Request Type
Style
Parameters:
Se Parameter Description Enabl Value Set Re Enab Dis Disp Prom To
q ed q le p. . pt ken
Sec. Size
10 P_FILE_P Data file Y 120 Characters Y N Data
ATH_NA name with file
ME path name
with
path
Request Sets
None
Open Issues
Validation
Program Logic: Page 30 of 32
CV.060 Doc Ref GMDC CV040 Fixed Assets Conversion.doc
Closed Issues
Validation
Program Logic: Page 31 of 32
CV.060 Doc Ref GMDC CV040 Fixed Assets Conversion.doc
Validation
Program Logic: Page 32 of 32