1. VINODH RAMADURAI
21/23, c1 B Block,
perungudi, chennai-96
9566246511
vinodhramadurai@gmail.com
TEAMLEAD, SENIOR SOFTWARE ENGINEER, ENGINEER TESTING
ROLE:
Requirement Gathering
Develop design
Spec and Coding in PL SQL
Unit testing
Functional Testing
Writing Test Cases
Log Defects
UAT testing
EDUCATION
Hindustan College of Engineering, UNIVERSITY OF Madras
Bachelor of Engineering (Mechanical)
Chennai, TN
1995-1999
First Class Graduate
EXPERIENCE
System Technologies Group
Team Lead
Chennai, TN
2009-2015
Ford is the customer
Communicate with customers to gather requirements
Develop 230 document
Develop logical flow diagram
Develop physical flow diagram
Create tables in oracle database
Develop program spec and oracle code
Develop Autosys code and shell script
Perform QC and UAT
2. Data Software Research company Chennai, TN
Software Engineer 2008-2009
Ford is the customer
Communicate with customers to gather requirements
Develop 230 document
Develop logical flow diagram
Develop physical flow diagram
Create tables in oracle database
Develop program spec and oracle code
Develop Autosys code and shell script
Perform QC and UAT
Project Name F@ST – MPA (Intercompany Accounting, Sales Journal)
Client FORD
Organization STG
Role Senior software engineer - Team Lead
Tools Used SQL, PL SQL, UNIX, Autosys
Duration 2.5 Years
SNURK:
Load data in db2 table to oracle using autosys, unix , pl sql.
PSC: Part Structure and cost
This module stores the part information, cost information and part structure (Bill of materials) in staging table.
The source of part is CMMS and ICS, WIPS send the Externally Purchased Price and Transfer Price. Every day
once the PSC gets switched the part price gets changes and loaded in the tables which is then used to Cost Parts.
PSC cost Actual vehicles.
APM:
TA:
APM is manufacturing parts for accounting. Plant receive parts, sell parts, reject parts on a source business date.
Transaction Accounting is a job that will process all the transactions like shipment, receipt, return receipt, return
shipment for that source business date , cost each part and generate the ledger amount based on the currency and
store in the costing tables. Using the process info, plant info, journal info the journal gets created which is then
sent to outbound systems like ICS, CCAPS, ERES.
EOP:
EOP is end of period accounting. Transaction happened on a month will increase or decrease the inventory.
Production run happens every month and re cost the inventory of a plant on an end of period date. Some other
run like pseudo and business run happens on on a need basis (may be twice in a week). Once the inventory
BOH, ICS, IIT, EIT gets costed the journal process gets triggered and journal gets created. The system is
designed in such a way that new journals for new account gets created automatically by adding new journal
groups, new accounts in the system.
3. Responsibilities:
SMW works, Enhancement, Project (Inter Company Accounting), SNURK project
Updating Program Specification
Updating Vision diagram
Fixing the changes mentioned in eTracker (pl sql, unix)
AUTOSYS job scheduling
Unix shell script to call driver procedures
Unit Test Cases, used Test Director to create test cases
Unit testing - Test all paths in the procedure
Project Name F@ST – FVA(System Maintenance Work)
Client FORD
Organization STG
Role Senior software engineer - Team Lead(current designation)
Tools Used SQL, PL SQL, UNIX, Autosys
Duration 2.5 Years
Project Description:
Costing actual vehicles and generate journal for it and sent to People Soft General Ledger. For each parts of the
vehicle the cost is pulled from PSC module.
Each Vehicle has Vehicle Events, Financial document, Financial element , vehicle order. These information
comes from external source and ETL tool is used to load into staging table. And the next module will use these
data and categorize into events, fin docs, fin element, vehicle order and store in each of the tables. The net
module will process all the vehicles one by one to create general ledger.
Module Handed: FE-B, Archival Retreival
Archived files stored in TSM the files purged if not needed in future. In case any of the vehicle detail needed
that file will not be purged and available which can be retrieved using the retrieval scripts.
Utility tables used to get the error log for a failed transaction.
Responsibilities
Updating Program Specification
Updating Visio diagram
Fixing the changes mentioned in eTracker (pl sql, unix). eTracker is nothing but a ticket.
4. AUTOSYS for job scheduling
Unix shell script to call driver procedures
Unit Test Cases
Unit testing - Test all paths in the procedure
Project Name F@ST – FVA
Client FORD
Organization DSRC
Role Senior software engineer
Tools Used SQL, PL SQL, UNIX, Autosys
Duration 1 year
Project Description:
Costing actual vehicles and generate journal for it and sent to People Soft General Ledger. For each parts of the
vehicle the cost is pulled from PSC module.
Each Vehicle has Vehicle Events, Financial document, Financial element , vehicle order. These information
comes from external source and ETL tool is used to load into staging table. And the next module will use these
data and categorize into events, fin docs, fin element, vehicle order and store in each of the tables. The net
module will process all the vehicles one by one to create general ledger.
Module Handed: FE-B, Archival Retreival
Archived files stored in TSM the files purged if not needed in future. In case any of the vehicle detail needed
that file will not be purged and available which can be retrieved using the retrieval scripts.
Utility tables used to get the error log for a failed transaction.
Responsibilities
Updating Program Specification
Updating Visio diagram
Fixing the changes mentioned in eTracker (pl sql, unix)
AUTOSYS job scheduling
Unix shell script to call driver procedures
Unit Test Cases
Unit testing - Test all paths in the procedure