AIM

CV.040 CONVERSION DATA MAPPING Zensar technoligies Assets conversions

Author: Creation Date: Last Updated: Document Ref: Version:

<Pradeep.H> May 7, 1999 XXX 0, 0000 <Document Reference Number> DRAFT 1A

Approvals: <Approver 1> <Approver 2> Copy Number _____

H Versio n Draft 1a Change Reference No Previous Document Reviewers Name Position Distribution Copy No. 1 2 3 4 Name Library Master Vikas bahl Location Project Library Project Manager Note To Holders: If you receive an electronic copy of this document and print it out. for document control purposes.Document Control Change Record 4 Date 7-May-99 Author Pradeep. If you receive a hard copy of this document. please write your name on the front cover. for document control purposes. . please write your name on the equivalent of the cover page.

............................................................... Introduction................................................................................................................................ Data Clean-up........ Open and Closed Issues for this Deliverable.......................... Application Business Object Reference Information.................................................................................. Conversion Mapping .................................................................................................................. ......... Extract File Layout...................................................................................... Data Normalization.................. Purpose................................................. Open Issues..........................................................................Assets conversion from R11i to R12.....................................Contents Document Control.............................................................................................. Closed Issues.....................................................

Data Migration is the process of transfer of data from the current systems in use to the proposed Oracle eBiz R12. FA Data Migration Strategy . Data from the R11i systems will be converted to Oracle Applications Release12 data. The conversion team uses this document to communicate the strategy for successfully converting the legacy/existing Oracle 11i data to the new Oracle R12 environment. • • This Data Migration Strategy document will be distributed and communicated to • • • The Project Manager. approach. Other process leaders who are responsible for tasks that are prerequisites for conversion tasks. and requirements.Introduction Purpose The Purpose of this document is to arrive at a Data migration Strategy for G4 project. objectives. The Project Manager uses this document to understand how the conversion team plans to perform the conversion and how the conversion efforts may impact overall project. Currently Accounting Data is maintained in Oracle Apps R11i. or whose tasks are dependent on output from conversion tasks. Henceforth in this document the terms “Migration” and “Conversion” will be used. Conversion Team Members. who should sign off on the conversion requirement and strategy. The Data Migration Strategy will cover following aspects: • • • • • detailed data mapping from the R11i ( legacy system) to the R12 oracle assets for Fixed assets conversion file layout to be used for extraction of the data from the source system Cut off Date Type of data to be migrated Migration process in general • FA Migration strategy Use of Data Migration Strategy document • The primary use of this document is to record and communicate the data conversion scope.

This is usually the first day of the new accounting period. the Depreciation Reserve should be segregated as follows: Life-to-date Depreciation – Depreciation Reserve from the date of capitalisation till 31-MAR-2011 Year-to-date Depreciation – Depreciation Reserve from 01-APR-2011 till cut off date. The cut off date (-----------) Type of Data to be Migrated The data to be migrated can be classified into two categories • • • Master Data Transactional Data (All transactions as of cut off date in source system(even the fully depreciated/retire assets also) All capitalized / CIP assets as of the cut off date will be migrated in new system with details of accumulated depreciation. • • • • • • . All the capitalised Assets would be uploaded into Fixed Assets with the Capitalised and Post as the flag. to all the Assets lying in MassAdditions. so that there are no audit complications. or the period which has been closed in the source system. Conversion of assets retired before the cut off date will be Migrated to the R12. Web ADI will be used to upload asset details in Mass Addition table. On posting the system will assign New Asset Nos.The data migration strategy has been formulated keeping in mind the following data conversion • • • Capitalized assets CIP assets accumulated depreciation lines Cut Off Date The selection of the cut off data for migration of data will be based on following factors • • • Clear identification of transactions from the source system Audit-ability Continuity Cut off date should be close the date for which statutory audit has been completed. Mass addition functionality will be used for adding assets. All the Assets would be uploaded with the Current Gross Value of the Asset along with the Life-to-date Depreciation Reserve balance and the Year-to-date Depreciation Reserve Balance. For conversion purpose.

The foreign key relationships between the Oracle Application tables are also indicated. For future depreciation run. The table below lists the Module and the Master data that needs to be migrated • Application Business Object Reference Information In each of the following sections. the system will generate the Depreciation Reserve after taking into account uploaded Depreciation Reserve and post to GL. a table maps the business objects for G4 R12 to the Oracle Application tables. Business Object Setup Business FA calendar period Calendar Types FA Books FA INTERFACE Man/ Prog Owned By Open Interface Production Table Name(s) FA_CALENDAR_PERIODS FA_CALENDAE_TYPES FA_BOOKS FA_TRANSACTIONS_INTERF ACE Remarks Object M FA M M FA FA Transaction Entities FA P TRANSACTION S FA FA_INVOICE_TRANSACTION S . In column (4).• The System will not generate any accounting entry for Depreciation Reserve as the same is manually entered. Column (2) suggests whether the business object is a candidate for programmatic conversion. the standard Oracle interface is documented if one exists for facilitating the conversion of a specific business object.

data preparation.Conversion Mapping . data verification / cleanup and data migration. No.# (2) Target Application Table (3) Target Application Table Column (4) (5) (6) Source System File Name (7) Source System Field Name (8) Source System Field Datatyp e (9) Default Value Target Not Column Null? Datatyp e Migration Process in General Migrating data in a three step process . 1 2 3 Step Data Preparation (Extract) Data Validation / Cleanup Data Migration in R12 Business Business Responsibility Implementation Team Data Preparation . The following processing ID codes are used in the mapping spreadsheet: <Business Object Abbreviation>PR = Processing Rule <Business Object Abbreviation>TR = Translation Rule <Business Object Abbreviation>FR = Filter Rule <Business Object Abbreviation>FKR = Foreign Key Rule <Business Object Abbreviation>DR = Derivation Rule <Business Object Abbreviation>DV = Default Value Rule Target Application: <G4 r12> Business Object : <FA CONVERSIONS> Prepared by:Pradeep.<Business Object Name> Below is a table mapping the legacy data elements to the Oracle tables and columns.H (1) Ref.

Data Migration This step essentially involves uploading the data in Oracle R12 using interfaces. Data Cleanup It will be the responsibility of the Finance Team to cleanup the deta before they are uploaded in Oracle R12. and also to avoid migrating the deta that longer needs to reside in the system.Data preparation is essentially extracting the data required to be migrated from the source system in the formats provided. Extract File Layout Below attached document will be used for the data extraction from the oracle Release 11i Open and Closed Issues for this Deliverable . There are certain fields that are mandatory when uploading data in Oracle and these will have to be compulsorily filled in. This is necessary to avoid duplicate. API’s where available. In certain cases where interfaces / API’s are not available or the volume of data is less the data migration will be done manually.

Open Issues ID Issue Resolution Responsibility Target Date Impact Date Closed Issues ID Issue Resolution Responsibility Target Date Impact Date .

Sign up to vote on this title
UsefulNot useful