1. Srinivas Ganta Email : gsabap@yahoo.co.in
SAP ABAP Consultant Mobile : +91 9243715999
Professional Summary:
• SAP ABAP consultant with 9.5 years of experience with Strong Implementation and
Support experience in ABAP programming.
Academic Profile:
• Bachelor of Engineering B.E from University of Madras.
Professional Experience:
• Currently Working for IBM, India pvt ltd as a SAP ABAP Senior Consultant since Nov
2011 to till date.
• Worked for Capgemini, India as a SAP ABAP Consultant since December 2005 to
Oct 2011.
Expertise in ABAP/4
• Strong Working experience of SAP R/3 applications FI & CO, MM, SD, PP, PM,
PS and Asset Accounting.
• Strong Working experience on FICO module With FI consultants on Customizing,
Substitutions, Validations, Payment Run and Business Transaction Events.
• Strong Working experience on ALE/IDOC’s.
• Strong Working experience on User Exits, Customer Exit, BADI's and
Enhancement Framework.
• Strong Working experience in BDC and LSMW.
• Strong Working experience on Data Dictionary Objects (Tables, Structures,
Search Helps, Views, Data Elements and Domains)
• Strong Working experience on SAP Query's.
COMPANY: IBM INDIA PVT LTD
Project Details: (12/2013 to Till Date)
Client Name: GESTAMP
GESTAMP is an Auto Part Supplier to major manufactures like, Audi, Renault, Volkswagen. It is
Group with 70-80 companies, all are working in SAP. Presence in Spain, Portugal, France, UK,
Poland, Hungary, Russia, China, USA, India with 26-28 plants.7 year Extension to AMS and
Enhancement Support Contract.
1

2. Roles and Responsibilities:
• Payment program (F110) will send Idoc using program RFFOEDI1 .This program is going
to create EDI outbound message PAYEXT which base type is PEXR2002. Retrieved the data
from VBKD and passed to the same to IDOC by using the exit EXIT_SAPLIEDP_001.
• Filling the Accounting clerk details in the payment advice note by Implicit enhancement
option in the standard program RFF0M100.
• The new field Alternative account number in company code added in the output of
FBL3N Transaction.
• The new fields country key, supply contrt2, tax amount in local currency, tax amount
document currency, Tax base amount in local currency, tax base amount in document
currency. Added in the output of FBL5N Transaction.
• Created a BADI implementation in order to trigger the event MKPF-CREATED using the
FM SWE_EVENT_CREATE for the standard Transaction MB04.
• Involved in ALE for Logical Systems, Distribution Model, Message Types and Partner
Profile to transfer Vendor Master Details by using Messages type ‘CREMAS’.
• Involved in ALE for Logical Systems, Distribution Model, Message Types and Partner
Profile to transfer Material Master Details by using Messages type ‘MATMAS’.
Project Details: (12/2011 to 11/2013)
Client Name: Wal-Mart Americas
Wal-Mart Stores Inc. is a worldwide household name in mass merchandising. The home
office is located at 702 South-west 8th Street Bentonville. Wal-Mart Stores Inc. is principally
engaged in the operation of mass merchandising stores located worldwide.
It is a support project, where we support different GEOs like, North America, Japan, Latin
America, China and Mexico .IBM India is responsible for functional support of any tickets
received through Remedy. Team is located in Argentina, US, China, Mexico and India. Scope
includes managed application support for SAP instance of FPMO in the UK, NA, Japan,
Argentina, Mexico, China and Central America.
Roles and Responsibilities:
● Working closely with functional team on several Modules.
● Debugging on the issues related customised programs and bug fixes for objects.
● Corrections /additions in existing reports/forms and other enhancements.
● Handled the tickets, resolving the issues on day to day basis on priority.
2

3. COMPANY : CAPGEMINI
Projects Details:
Project #1
Client: PHILIPS (08/2008 to 10/2011)
Philips Consumer Lifestyle and Philips Lighting Projects:
About the project: Philips is organized in a number of sectors: Philips Consumer Lifestyle,
Philips Lighting .These project consists of application support and change management.
As a member of the SAP Technical Team, I have been working on: Output management,
Classical/Interactive Reports, Extensively on ALE/IDOC’s, User-exits, Bapi, job abends,
handling Change Requests, Trouble Tickets as well.
Project #2
Client: ABB Implementation (05/2007 to 08/2008)
About the project: The ABB group is created from two companies, Swedish Asia and the Swiss
corporation Brown Boveri. The merger took place in 1988, with the aim that the new
company would be more competitive on the world market. This goal has also been
achieved and ABB is now number one in the world in many industrial fields.
Current project is a part of ABB OsA (One simple ABB) Program in which Denmark
implementation is under current scope. The objective was to remove the legacy
systems XAL and Mapics and integrate them in RasU environment. The current SAP R/3
4.6C implementation is considered as the toughest implementation after ABB power
systems. Technical work was mainly for user exits, Idoc’s, LSMW, migration programs,
reports, SAP scripts, SD pricing /output requirements, formulas etc. This project is the
most enhanced implementation and in future ABB will use it as role model for inheriting
the enhancements for other ABB subsystems.
Responsibilities:
• WINEDI INTERFACE: WINEDI is an application for printing labels for marking
goods sent by different forwarding agents. When a Delivery Note is created in RaSU a file
should be created that can be read by WINEDI. When WINEDI has printed the label, a file is
sent back to RaSU with, among other things, a unique number that can be used for example
to track an item on the internet. This number updates the shipment in RaSU.
• OUTBOUND File from RaSU to WINEDI: Technically the interface is an Idoc sent
to Business Connector where the Idoc is mapped to a WINEDI file and sent by FTP to the
WINEDI server.
• PRICE CATALOG BDC:
• MATERIAL CASE :
3

4. Fetch the data from presentation file and split the fields as per the given file format. For
mapping of the fields please see attached excel file. After reading data from file loop for
each material and check the existence entry in the material master table (MARA).
If execution method is Prod. Mode then using the inputted material type, inputted file data
and hardcode reference material, create a new material using BDC call transaction method
through transaction code MM01.
• INFO RECORDS CREATE / UPDATE:
Fetch the data from the inputted file path. Fill the internal table as per the provided
mapping excel sheet. Make a selection on EINE table with key Purchasing organization and
plant as per selection screen, Info record category as ‘0’.
For all the info records found to verify the existence of the Info records against table EINA.
Please use Material number and vendor from the inputted file for EINA selection.
Check if Info record does not exist then use T-code ME11 to create the new Info record if
info record already exists then use T-code Me12 to update the existing info record with new
data from the inputted file. Please consider that right now always Info category will be
STANDARD only.
• User exits:
SD User Exits
• MV45AFZZ,
1) Error for EDI-order when order qty less than min qty.doc
To check the order quantity, If not ok an error message should be issued, which will
prevent the order from being saved and block the Idoc.
2) Profit centre determination
If profit centre can't be determined from the table, the profit centre should be taken
from material master. This means that the following code in the exit MV45AFZZ needs
to be replaced and profit centre should be taken from material master instead of
issuing an error message:
3) Check if billing block is valid in combination with order reason in contract.doc
When standard contract is accepted by customer the billing block should be set to
Released, but for project contracts it should be removed. The system should be check
that the user doesn’t set wrong block.
• MV50AFZ1
1) User Exit for Packing Items
VL02N - For Outbound del exit. The exit fired at the time of saving of outbound delivery.
• WM User Exits
1) MWMTO007 Put away Strategy User Exit
Storage Bin will not be determined automatically and will be entered manually at the
TO creation screen.
Functional modules: EXIT_SAPML03T_002
Transaction used to test the exit LT03.
4

5. 2) PPCO0005 St.Location User Exit
User exit that determines Issue St.Location for Production Order components. That
code will first check if the Plant in the component reservation is 0504 and St.Location is
0902.If that is the case the St.Location will be changed to 0504 and coded accordingly.
Functional modules: EXIT_SAPLCOSD_001
Transaction code used to test the exit CO01.
 Created a new data element ZZPRODH12 (Character field with length 10). Also
create domain for the new data elements. Integrate the field name in the
communication structure KOMP using the INCLUDE ZKOMPAZ and allocate the
field to it. Activate the structure. In sales order processing the user exit is found
in member. Fill the TKOMP field with PRODH1 + PRODH2 (which is the first 10
characters of VBAP-PRODH
Project #3
Client: OUTOKUMPU (07/2006 to 04/2007)
Capacity Search Interface
• Capacity Search interface, it would enable the users to search the plans maintained in
the SCS system, from SAP. Interface will bring the plans from SCS system and plans are then
displayed to user. User can then drill down to a specific plan. Each plan is divided into weeks
and weeks can be divided into further customer wise plans. The user has an option to
Create new reservations Edit or Delete existing reservations.
• All changes are validated in SAP system and then sent to SCS with interface. SAP’s BAPI
functionality is used to read and send the plans and reservations.
• Editable ALV Grids are used in order to display and edit the customer reservations.
Send Orders Interface
• Outokumpu has several systems, apart from SAP. Interfaces have been developed for
communication across these systems. TIBCO is the middleware which is used for these data
communications.
• Order Acknowledgement needs to be sent to TIBCO on Order Acceptance. I was
involved in the creation of the IDoc and message type. A new function module was created
to capture the Sales Order details and the IDoc was sent to TIBCO using Output types.
Project #5
Capacity Cushion (Project of Capgemini –Netherlands) (04/2006 to 07/2006)
Client: DHL, Netherlands (Spare Parts Management System for Philips)
 Achieved client (DHL) appreciation letter along with Reward (75 EURO’s) from
Capgemini – Netherlands when I was in Netherlands.
5

6. • Involved in ALE for Logical Systems, Distribution Model, Message Types and Partner
Profile to transfer Vendor Master Details by using Messages type ‘CREMAS’.
• Developed a BDC program to extract the data from legacy system to R/3 system for the
Transaction ME01 using CALL TRANSACTION method.
• Developed a project to transfer Vender Master Data using LSMW technique. This
includes Batch Recording technique.( Uploading IBAN Code through program in to Sap
Transaction XK01)
• Developed a project to transfer Standard Purchase Order data using Legacy System
Migration Workbench (LSMW) technique. This includes Direct Input technique.
• Developed a project to transfer Accounts payable & Accounts Receivables data using
Legacy System Migration Workbench (LSMW) technique. This includes Direct Input
technique.
• Performance grading and testing of programs and reports under ABAP/4 Using SAP R/3
Components such as SQL trace, runtime analysis and extended syntax check.
Project #6
Client: Philips – Speed., Netherlands (Semi conductors Manufacturing Industry)
System: SAP R/3, ABAP/4 and WINDOWS NT. (12/05 to 04/06)
Role: ABAP/4 Consultant
Modules: Implemented are SD, MM and FI/CO.
Responsibilities:
• Designed & coded a BDC program for sales order that update records in the sales order
screen.
• Developed a BDC program for transferring Vendor Master Data (MK01) using CALL
TRANSACTION method
• Developed a project to transfer Customer Master Data using LSMW technique. This
includes Batch Recording technique.
• Developed BDC program for Material Master for following views - plant, storage
Location, Warehouse management, Sales organization data, Financing, Inventory
Information record, source list.
• Developed a project to transfer Material Master Data using Legacy System Migration
Workbench (LSMW) technique. This includes Direct Input technique.
• Developed BDC program using Call Transaction for Customer Master, it will update
records in Customer Master or create new customer depending on the source data file of
external system.
• Developed BDC Program to extract the data from legacy system to R/3 system for
Vendor Master Data using Session Method. (XK01)
6

7. • Involved in ALE for Logical Systems, Distribution Model, Message Types and Partner
Profile to transfer Vendor Master Details by using Messages type ‘CREMAS’.
• Developed a BDC program to extract the data from legacy system to R/3 system for the
Transaction ME01 using CALL TRANSACTION method.
• Developed a project to transfer Vender Master Data using LSMW technique. This
includes Batch Recording technique.( Uploading IBAN Code through program in to Sap
Transaction XK01)
• Developed a project to transfer Standard Purchase Order data using Legacy System
Migration Workbench (LSMW) technique. This includes Direct Input technique.
• Developed a project to transfer Accounts payable & Accounts Receivables data using
Legacy System Migration Workbench (LSMW) technique. This includes Direct Input
technique.
• Performance grading and testing of programs and reports under ABAP/4 Using SAP R/3
Components such as SQL trace, runtime analysis and extended syntax check.
Project #6
Client: Philips – Speed., Netherlands (Semi conductors Manufacturing Industry)
System: SAP R/3, ABAP/4 and WINDOWS NT. (12/05 to 04/06)
Role: ABAP/4 Consultant
Modules: Implemented are SD, MM and FI/CO.
Responsibilities:
• Designed & coded a BDC program for sales order that update records in the sales order
screen.
• Developed a BDC program for transferring Vendor Master Data (MK01) using CALL
TRANSACTION method
• Developed a project to transfer Customer Master Data using LSMW technique. This
includes Batch Recording technique.
• Developed BDC program for Material Master for following views - plant, storage
Location, Warehouse management, Sales organization data, Financing, Inventory
Information record, source list.
• Developed a project to transfer Material Master Data using Legacy System Migration
Workbench (LSMW) technique. This includes Direct Input technique.
• Developed BDC program using Call Transaction for Customer Master, it will update
records in Customer Master or create new customer depending on the source data file of
external system.
• Developed BDC Program to extract the data from legacy system to R/3 system for
Vendor Master Data using Session Method. (XK01)
6