Documente Academic
Documente Profesional
Documente Cultură
Objective:
A challenging assignment as Techno-Functional Consultant in SAP R/3 in line with my pervious
experience and skills in ERP.
Professional Summary:
• Total of 4.9 years IT Experience.
• Over 4 years of experience in SAP-Workflow Development.
• Hands on experience in ABAP/4.
• Worked in SAP Functional Modules SD, MM, ESS, and MSS.
• Experience in preparing Module Test Plans, Integration
• Test plans, user Documentation & User Training.
• Understands both business processes and technical development.
• Excellent communication and interpersonal skills.
Awards:
Received the best faculty for the quarter1 (Apr'08 to Jun'08) for my customer (Tyco Thermal
Controls - Mumbai) training in workflow.
Technical Skills:
ERP : SAP R/3 4.6 & 4.7c, CRM 5.0, ECC 5.0, ECC 6.0.
Functional Area : MM, SD, HR (payroll), ESS, MSS.
New Dimensional Products : Workflow
Operating Systems : MS-Dos, Windows'98, and Windows NT 4.0
Databases : MS-Access, Embedded SQL Server
Languages : C, C++, Keil C, COBOL
Internet/Web : HTML, DHTML, and Java Script
Educational Qualification:
B.E. (Electronics and Communication) from Bharathi Dasan University during 1999-2003.
Project Details:
5.
Organization : Mahindra Satyam
Designation : Sr. Software Engineer
Duration : May 2008 - Till Date
Project #2:
Client : Mazagon dock limited, India
Role : SAP Workflow Lead
Duration : Aug'08 - Till date
Responsibilities:
Release strategy Workflow (RFQ, PR/PO)
• When a Purchase Requisition/ Purchase Order or Request for Quotation is created in SAP,
the release strategy will be determined based upon the document type, purchase
organization, purchase group, storage location and net value of the purchase
requisition/Purchase Order or Request for Quotation.
• Based upon the release strategy maximum number of release code is defined.
• Custom table is created with initiator, Purchase Group, release strategy, release code, and
the approver as the fields.
• Based upon the initiator, Purchase Group, release strategy, release code, the approver is
identified with the help of the custom table.
• A workitem will be sent to the corresponding approver, for the release of the corresponding
business document.
• The approver can see the corresponding business document (PR/PO or PFQ) in the
workitem in display mode. After seeing the document the approver double clicks the workitem
and it takes him to the corresponding release transaction.
• Here the approver has not provided any user decision, and giving full freedom to make the
decision on the transaction code for the corresponding document.
• Once the approver, approves/rejects/block the corresponding document an email will be sent
to the initiator.
Project #1:
Role : SAP Workflow Competency Lead
Duration : May'08 - Jul'08
Responsibilities:
• Conducted three internal Classroom Workflow Trainings as per the BIT 600, BIT 601, and BIT
610.
• Provided hands on training to a customer (Tyco Thermal Controls-Mumbai).
• Conducted 2 internal V-Share Workflow Trainings.
4.
Organization : Wipro Info Tech, India
Duration : Apr'07 - Mar'08
Project #2:
Client : Wheels India Limited, India
Role : SAP Workflow Consultant
Duration : Jan'08 - Mar'08
Responsibilities:
Business Events (HR):
• When a Business event is created and scheduled, it will be intimated to all employees
through mail.
• Employee who is interested with the training can nominate himself for the specified training
using the business transactions.
• Once the employee nominates himself for the training, it goes for two levels of approval. First
level to his immediate manager, second level to the event manager.
• The immediate manager has three options for the requested nomination 1. Approve 2. Reject
• 3. Resend for reschedule.
• The nomination goes for event mangers approval once the immediate manager approves the
request. Based upon the number of nomination and number of seats the event manager can
approve the request or reject the request.
• If the event manager rejects the request, a pop-up window will open where he has to give the
reason for rejection. This information will be sent to the immediate manger and the employee
who has nominated himself for the event.
• If the immediate manger rejects the request the employee cannot schedule this training for
next 30 days.
• If the immediate manager resend's the request for reschedule the employee can reschedule
his training based upon the next available training scheduled.
• All the three levels of approvers will be having the following options for approval of the travel
plan 1. Approve 2. Reject. All three approver must provide their reason for approval or
rejection of the travel plan.
• If the employee has requested for an advance payment and if the travel plan is approved by
all the levels a notification will be send to the payment team for making the payment to the
employees account (the payment will be made after three working days from the date of
approval-manual process).
• Once the employee completes his travel, the employee has to submit the travel expense
report within three days time, else a reminder mail will be sent to the employee for each 48
hours time period.
• Based upon the travel expense report created by the employee it may goes to 1 or 2 or 3
levels of approval same as travel plan approval.
• Once the travel expense report is approved, the employee is requested to submit the bill to
the bills processing team manually and they process it for further payment to the employee or
payment receivables from the employee.
Project #1:
Client : AIRCEL Cellular Limited, India
Role : SAP Workflow Consultant
Duration : Apr'07 - Dec'07
Responsibilities:
Release Strategy (PR and PO (MM))
• When a Purchase Requisition/Purchase Order is created in SAP, the release strategy will be
determined based upon the document type, purchase organization, purchase group, storage
location and net value of the purchase requisition/Purchase Order.
• Based upon the release strategy maximum number of release code is defined.
• Custom table is created with initiator, purchase document type, release strategy, release
code, and the approver as the fields.
• Based upon the initiator, purchase document type, release strategy, release code the
approver is identified with the help of the custom table.
• The approver will have four decisions to perform 1. Release PR/PO 2. Reject PR/PO and 3.
Consult 4. Transfer.
• If the approver's decision is 'Release PR/PO' the purchase requisition/Purchase Order will be
released in background for the corresponding release code and an email notification would
be sent to the initiator.
• If the approver's decision is 'Reject PR/PO' the purchase requisition/Purchase Order will be
rejected in background for the corresponding release code and an email notification would be
sent to the initiator.
• If the approver decides to consult with some other user about the PR/PO the approver can go
for the decision 'Consult'. When the approver's decision is consult a pop-up window will be
opened where he can choose the user to whom he has to consult about the PR/PO, the
approver has the option of giving his comments on the pop-up which will be sent as an email
to the consulted person.
• The consulted person will have the option of 'Reply', when he decides to reply a pop-up
window will be opened where he can give his comments on the PR/PO and his comment
would be sent as an email to the consulted user, after seeing the mail the approver can make
any of four decision.
• If the approver decides to transfer the approval of PR/PO to some other user, the approver
can go for the decision 'Transfer'. When the approver's decision is Transfer then a pop-up
window will be opened where he can choose the user to whom he has to Transfer the
approval of PR/PO, the approver has the option of giving his comments on the pop-up which
would be sent as an email to the transferred person.
• The assigned person will have all the four options for the decision.
3.
Organization : ASAP InfoTech Systems Pvt Ltd, India
Duration : Sep'06 - Apr'07
Project #3:
Client : Adobe INC, US
Role : SAP Workflow Consultant
Duration : Jan'07 - Apr'07
Responsibilities:
Integration of JAVA Web-dynpro with SAP Workflow (SD, ESS, and MSS)
Severance Form. (Employee Termination Info (ESS):
• A Severance form will be initiated from the web-dynpro by an initiator using the personnel
number as the key. The initiator is one user from HR-OPS group.
• The initiator will be entering the personnel number and a RFC would be called to populate all
the value of the personnel number.
• Based upon the payroll area of the employee a notification will be sent to the HRM, HRM
Admin, Functional HRM, Field Controller, Functional Controller, Benefits (Group of users),
Payroll (Group of users), and HR-OPS (Group of users).
• Group of users are assigned to the work center, there are three work centers for three groups
of users.
• If any one user in that work center acts on the workitem it gets disappeared from others UWL.
• Based upon the number of hours the employee worked in organization his pay will be
calculated and the employee's last pay will be dispatched after 32 working days to his bank
account.
Responsibilities:
Travel Request Approval (ESS)
• Extended the Standard business object BUS2089 (Employee Trip) and added methods for
finding the approver based on the employee subgroup.
• Highest level of the employee subgroup is maintained in a ztable.
• Created a Method to find the appropriate lines from the Travel Request, which is created by
the employee.
• Created a condition step in the workflow template to find whether the first approver is the final
approval, this continues for further levels.
• After getting approval or rejection a notification is sent to the employee whether his approval
is approved or rejected.
• After getting approval a notification is sent to the 'Travel Admin', 'Accommodation Admin',
'Local Convince Admin' based on the detail provided by the employee in the travel request.
• Approval mail is sent to the 'Account Manager' if the employee applied for any 'Advance'.
• The mail, which is sent to the 'Account Manager', consists of Employee name, Employee
subgroup, Date, Advance Amount, and the Reason.
• A Notification mail is sent to the employee from the Approver inbox, if the approver needs any
additional information.
Project #1:
Client : GE Energy, US
Role : SAP CRM-Workflow Consultant
Duration : Sep'06 - Nov '06
Responsibilities:
Notification to Global Tech Support Manager:
• Extended the Standard business object BUS2000126 (Business Activity) and added a
method for sending notification to Global Tech Support Manager.
• OS Tech Support Case is created in the transaction CRMD_BUS2000126 with status.
• The workflow is triggered and a notification email is sent to the 'assigned to' person based on
the employee id.
• The mail which is sent to the 'assigned to' person consist of the case number and the
description of the case with the created date and created time.
• If the status of the activity is open for 4 hours, the notification email is sent along with the
number of hours the case is open with the case number in the subject to Global Tech Support
Manager.
• Email is sent to the Global Tech Support Manager with the case number, Employee id of the
assigned to person, and the description of the product id with the category id as the content
of the email.
• This process continues for every 24 hours till the status is open.
• The workflow gets terminated if the status of the business activity is other than open.
1.
Organization : Kaavian Systems Pvt. Ltd, India
Duration : Aug'04 - Sep'06
Project #5:
Client : Samsonite, Denver, US
Role : SAP Workflow Consultant
Duration : Mar'06 - Sep'06
Responsibilities:
Release Strategy (MM):
• Extended the Standard business object BUS2009 and added a method for approval and a
virtual attribute for showing the item.
• The workflow is triggered whenever the purchase requisition is created to get the approval
from superior.
• Extended the standard workflow (purchase requisition release) to meet the extension
requirements.
• Specified the deadline monitoring dates for optimized process.
• Purchase quantity, No. Of Purchases, Total Values, Average Purchase Cost, Consumption
during the period are used the approval.
• After the approval is given for the specified Purchase Requisition it has to create RFQ
automatically and that is send to the corresponding vendor through EDI.
R/3 Workflows:
• Triggered a workflow for purchase order quantity change.
• Extended the Business object and added a method for approval and a virtual attribute for
showing the item.
• Developed an approval workflow for scheduling agreement creation. To get the values of the
scheduling agreement, added a method by customizing the business object.
• Defined start conditions to trigger the workflows based on purchasing organization,
purchasing group.
• Used deadline monitoring to set deadlines for processing
• Defined Check function module to restrict the creation of workflow from specified
transactions.
Project #4:
Client : Wilton Industries, US
Role : Workflow Consultant
Duration : Aug'06- Jan'06
Responsibilities:
As a workflow consultant I was involved in designing, developing, implementing and testing
workflows by understanding the existing business process for SD and PM.
Project #3:
Client : WMH Tool Group, US
Role : SAP Workflow Consultant (SD).
Duration : Apr'05 - Jun'05
Responsibilities:
Request for Quotation Workflow:
• Triggered Workflow whenever RFQ is created.
• A notification containing the details of Vendor, Person Created the RFQ and purchase
document number is sent to the purchasing group manager for approval.
• The manager has been given an option to execute the work item or it can be escalated to
another same level of manager for approval.
• The approval status is sent to the creator of the RFQ for further proceedings.
Project #2:
Client : EDS Corporation (Budd, TX) - Indiana, Indianapolis
Role : SAP Technical Consultant (MM/SD/PS).
Duration : Dec'05 - Mar'05
Responsibilities:
• Developed BDC program to load the purchase order to SAP from external file using
background job schedule.
• Modified purchase order and Order Confirmation Form in SAPscript to the client requirement
• Created incomplete sales document report.
• Involved in Migration of Vendor Master and Customer Master Data from Legacy system to
SAP R/3 using LSMW with the aid of Direct Input Programs like RFBIKR00 for vendor master
and RFBIDE00 for customer master.
• Developed a report to list the sales documents those have been delivered on the requested
date of the customer
• Created Vendor Performance Report that lists Vendor Name, Materials Supplied, Planned &
Actual Delivery Times, Payments Terms and Prices
• Created report for Sales Orders due for delivery and Daily sales summary for a selected
sales organization
• Created report for listing the material that has the maximum returns at a particular plant
• Developed Purchase order listing between two given dates for a selected vendor
• Archiving done for the objects in SD and MM module
Project #1:
Client : Nissan Motors, TN
Role : SAP - ABAP Consultant (MM/SD).
Duration : Aug'04 - Nov'05
Responsibilities:
• Modified Standard SAPScript MEDRUCK for Purchase Orders and the corresponding print
program base on the company requirements. Output type is created with two options
Transmission medium: Printout and Mailing.
• Delivery note is created using the standard form RVDELNOTE and print program for the
packing list.
• Modified the standard Sales order SAPScript layout set RVORDER01 and the corresponding
print program RVADOR01 for adding company logo and layout style as per the company
requirements in sales order. Transmission medium with two options: Printout and Mailing.
• Used SAP Script to customize the Report Structure. Report for Customer service Level
statistics, which gives the performance of customer service based on creating deliveries on or
before the requested delivery date.
• Worked on the text file was passed to a BDC program in Material Master which assigns the
Purchasing group for respective material for that client from another text file Containing
details of purchasing group.
• Worked on SAP Scripts for Invoice Printing. Different Invoices were printed, based on Sales
Org and Distribution Channel
• Created a report that gives a summarized view of the costs, activities, planned and actual
postings, and balance of a cost center.
• Customized for Account Receivable reports development of the monthly Account Balance,
Sales and Customer Sales.