COA Conversion Technical Guidelines

by Ramesh Padhiyar

Zensar 2008

www.zensar.com

Objective
Pre Conversion Activities
Mapping Application
Conversion Activities
Post Conversion Activities
Custom Objects Identification
Impact Analysis of Custom Objects
Issue Analysis of Impacted Objects.
Testing & Migration of Custom Objects

Zensar 2008

www.zensar.com

Pre Conversion Activities

Application Setup
Verify that the New responsibility created for the COA conversion process
Data Extract
GL - Trial Balance Detail and Summary (PTD & YTD)
AP - Accounts Payable Trial Balance
AR - Aging Report - 7 Bucket by Account
INV - Material Account Distribution Detail Report
FA - Drill Down Account Report
Data Collection sheets
Send data collection sheet of AP Expense report, Asset Categories, Book Controls, Mass
Retirements, Mass Transfer, PO Approval Groups, ...etc.
Database Object creation for COA Conversion
Send scripts of Tables, Indexes, Packages, Procedures to DBA for conversion
Delete setup and prepare control files
Delete book controls and organization setup
Get the GL_CODE_COMBINATIONS data into temp table

Zensar 2008

www.zensar.com

Mapping Application
Populate new mapping relation & values to temp tables
There are several relationship defined for old & new COA structure
CO = EcE, CO+AC = EcE, CO+AC+BL= EcE+BL, ...etc. most important thing is to
understand relationship and its priority.
Populate segments mapping values to temp table and update relation type.
Counter Generation
Run the mapping application script to generate counter
Why counter required & logic of counter
Verify the counter generation
Control files
Prepare control files of Flex Value, Parent Values, GLCC, CCID Mapping, Asset Category, Mass
Retirement, Mass Transfer, PO Control, GL Allocation, Cross Validation, FA Keywords & Customer
Channel and send to DBA to upload in tempo table.

Zensar 2008

www.zensar.com

Conversion Activity
Delete Setup and Others
Delete Summary Template, Cross Validation rules, Short hand alias & Budget Ranges .
Run Depreciation Rollback.
Delete Segment definition in Account Flexfield
Define new segment definition in Accounting Flexfield
Define Flexfield Qualifiers for Balancing, Natural Account, Cost Center & Intercompany.
Open segments and define default type, enable security...etc
Change the value set name used in FA_Location KFF
Run the set of concurrent programs
Concurrent programs to upload control files to temp tables.
Concurrent program to convert GL_CODE_COMBINATIONS table
Run the concurrent program to check retained earnings a/c in SOB
Run the concurrent program to update FA Locations KFF
Run the concurrent program to update the FA Distributions history & view log file.
If log file returns any new combinations, run again till no combinations are displayed.
(LAST 1 OR 2 SWAPING DO AFTER POST CONVERSION using mass transfer)
Identify missing values in Value Sets.

Zensar 2008

www.zensar.com

Post Conversion Activity

Upload data from control files to temp tables
Upload data from control files to temp tables for Asset Categories, Mass Retirement,
PO Control Groups, ...etc.
Run the set of concurrent programs
Run the concurrent programs Post Conversion Process to Update Counters in
Setups of each module.
Run the concurrent program to Enable Code Combinations in GLCC table.
Run FA Account Generator Process to identify the disabled combinations.
Run the following query to identify any assets have NULL CCIDs.
select gcc.segment1, gcc.segment2, gcc.segment3, da.*
from gl.gl_code_combinations gcc
, fa.fa_distribution_accounts da
where da.asset_cost_account_ccid = gcc.code_combination_id (+)
and da.BOOK_TYPE_CODE = 'EOA-CORPORATE'
and gcc.code_combination_id is null
If the query returns NULL CCIDs then run FA Account Generator Process
Run concurrent program to update GL Posting flag to Y, Customer Channel, Cross
Validation & FA Keywords.
Do some manual update (Functional Task) like Book Control, AR Auto Accounting,
Budget Ranges, AP Expense, AP Reporting Entity
Replace the counter from Intercompany account definition

Zensar 2008

www.zensar.com

Custom Objects Identification

Custom objects include all the bespoke programs or database objects
which are not standard to oracle application.
In COA restructuring we classify the Custom of Objects as:
A. Database Custom Objects.
B. Application Custom Objects.
Database Custom Objects: It includes all the Custom tables, stored
procedures, packages, functions, views and triggers from the custom
schema.
Application Custom Objects: It includes objects like Reports, Forms,
SQL, Concurrent Programs, Value Sets, Alerts, Profile options,
Flexfields.

Zensar 2008

www.zensar.com

Custom Objects Identification

Custom Objects

Database Custom Objects

Tables

SQL

Request Sets

Zensar 2008

Views

Reports

Application Custom Objects

Packages

Forms

Concurrent Programs

Procedures

Value Sets

Flex Fields

www.zensar.com

Functions

Triggers

Alerts

Profile Options

Impact Analysis of Custom Objects

OLD STRUCTURE

NEW STRUCTURE

No

Name

Type &
Length

No

Name

Type &
Length

Seg1

Company

C(4)

Seg1

Economic Entity

C(5)

Seg2

Account

C(4)

Seg2

Account

C(5)

Seg3

Function

C(3)

Seg3

Cost Center

C(4)

Seg4

Business Line

C(3)

Seg4

Business Line

C(3)

Seg5

Intercompany

C(4)

Seg5

Intercompany

C(5)

Seg6

Customer Type

C(3)

Seg6

Customer Channel

C(3)

Seg7

Group

C(6)

Seg7

Group

C(4)

Seg8

Project

C(4)

Seg8

Tracking

C(5)

Seg9

Future Use

C(6)

Seg9

Future Use

C(6)

Zensar 2008

www.zensar.com

Impact Analysis of Custom Objects

The above table shows the Old Accounting Flexfield and New Accounting
Flexfield structure.
All the Issue Analysis would be based on this structure only.
For Issue analysis we first have to identify that whether a file is impacted or
not.
Finalize a word or a string which is to be identified in a file.
For e.g. The words would be the name of the segment, Values set name,
gl_code_combinations etc.
Following are the key words to search in all the object
company, gl_code_combinations, Segment, comp, function, Account,
Business, Intercompany, project, dept, combination, acct, seg, values et
name, value set id,...etc.

Zensar 2008

www.zensar.com

Issue Analysis of Impacted Object

Once the impacted code is listed, issue analysis is to be done.
There are three type of impacted object such as
Fully Hard Coded
Partially Hard Coded
Dynamically Hard Coded

Zensar 2008

www.zensar.com

Issue Analysis of Impacted Object

For e.g. in the package we have the code:
CURSOR csr_get_accts(p_company_code IN VARCHAR2) IS
SELECT cc.code_combination_id,
cc.segment1||'.'||cc.segment2||'.'||cc.segment3||'.'||cc.segment4||'.'||cc.segment5||'.'||cc.segme
nt6||'.'||cc.segment7||'.'||cc.segment8||'.'||cc.segment9
FROM gl_code_combinations cc
WHERE segment1 = p_company_code
AND segment2 ='5206'
AND segment3 = '000'
AND segment4 = '000'
AND segment5 = '0000'
AND segment6 = '000'
AND segment7 = '000000'
AND segment8 = '0000'
AND segment9 = '000000'
AND chart_of_accounts_id = 101;

In this package there is a selection of segment1-9 and in the where clause the
values are Hard-coded. So this file is an impacted file and it is fully hard coded.

Zensar 2008

www.zensar.com

Issue Analysis of Impacted Object

Issue Analysis of TABLES:
Thoroughly check the table structure for its segment values.
For Eg:
In the custom table COCUST_IMP_WK_INTERCO a
INTERCOMPANY_CODE column is defined is defined having data type
and length VARCHAR2 (4), The length of the column defined here is of old
segment as the new segment have a length of (5 Bytes).
Other impacted type in table is data. Suppose one column of table
contains concatenated value of all the segments. In this case we need to
replace combination of segments with new value.

Zensar 2008

www.zensar.com

Issue Analysis of Impacted Object

Issue Analysis of Views
For the analysis of views just check whether the view is based on impacted
table or not and also check the script whether the string/word is used in
building up the View.
In similar way we can check and record the impacted code for Procedures,
Functions, Triggers, SQL.
Issue Analysis of Reports
For reports convert the .rdf file into .rex file as .rex file is a text file so it will
be easy for analysis.
Issue Analysis of Forms
Convert the Form .fmb file into .txt file, so it will be easy for analysis.

Zensar 2008

www.zensar.com

Issue Analysis of Impacted Object

Resolution of Impacted objects
Providing resolution is one tricky task depending upon the mapping of the
old accounting Flexfield structure with the new accounting Flexfield
structure.

If the mapping is one to one with the same number of segment the
resolution would be easy.
But if the mapping is one to many or vice versa it becomes tricky and a
proper understanding of Mapping along with the mapping values is must
before providing the resolution.
Don't delete any line from object. Comment existing line with standard
comment like - Commented by Zensar for COA on dd-Mon-yy
and new line with comment - Added by Zensar for COA on dd-Mon-yy

Zensar 2008

www.zensar.com

Testing & Migration of Custom Object

Test the object with 2 or 3 test scenario and prepare the migration script
for modified object
Prepare Migration script depend on object type like
Object type
Script type
--------------------------------------------------------Conc program definition
LDT file
.rdf, .sql or .ctl files
Shell script with move command
.fmb file
Shell script with compilation command
Package or procedure
sql file
Workflow
LDT file
Value set
LDT file

Zensar 2008

www.zensar.com

Thank You

Zensar 2008

www.zensar.com