Best Practice -

June 14, 2013

Copyright 2012 Tata Consultancy Services Limited

Title

Domain/ Service/ Technology /Geo: SAP BW-BI/ SAP/ INDIA Name of the Project/Support Fn : Name of the Author : Mohammed Mushtaq Date Created: February 8, 2013

Description

Project / Context

As part of our project, there was new implementation of Postpaid Revenue Reports to be displayed on SAKSHAM from transforming complete business data from various circles from a legacy system to SAP application . The project also entailed performing and displaying the PAN India data at very granular level such as Account level, Subscriber level, Circle level and at various products, business line item (that is, extracting legacy data from various source system and for different circles at a time) thus involved repeated process and heave maintenance on a periodic basis over a length of time.

Description
Purpose

Usually performing data migration for one entity involves a number of processes to be run one after the other like: Use a file transfer tool to move a data file to the appropriate path in the server. Use SQL Loader tool to load data into the staging table. Check log files for number of records loaded, rejected. Perform validation on staging table data and load data into interface table Check data errors. Run Oracle standard Open Interface Import program to load data into Oracle base tables. Check log files for errors and total number of loaded and rejected data.
4

How we did it
Process Adopted

<Step by Step description>

1. 2. 3. 4.

Highlights
xxxxxxxxxxx

Why this is a Best Practice

Before
<Give your reasons in quantifiable terms as much as possible.>

Benefits
<Numbers like additional dollars earned, cycle time reduced, error free work, productivity improved, customer delight etc. Who were the actual beneficiaries? employees, TCS, Customer etc) Is this benefit one time or recurring?>

How this may be adapted elsewhere

Replication
Contact Info

< your ideas on taking this forward to other units of TCS.>

Thank You