EXPERIENCE SUMMARY:

• SAP Technical consultant with 6 years of experience.
• Experience working in ECC 6.0 and CRM 7.0.
• Knowledge in SAP CRM - Sales, CRM - Service and SAP SD module.
• Worked extensively in the development activities of CRM, SD and MM modules.
• Project experience includes ABAP/4 developments for reports, customer enhancements, business add-ins, smart forms in SD, MM modules.
• Expertise in developing all the major components of RICEF from design to support phases.
• Worked on different Cross Application technologies like RFC, ALE, and EDI etc.
• Experience working on data migrations and transfers using BDC and LSMW.
• Worked on many CRM WEB UI enhancements including screen configurations, BOL programming.
• Worked extensively on the CRM component workbench tool BSP WD CMPWB.
• Worked extensively on different enhancements - Transaction variants, Customer exits, User exits.
• Developed Menu interfaces for various screens & interactive lists.
• Modification of standard layout sets using Smart forms.
• Exposure to CRM - Sales and CRM - Service customizations.
• Worked on Performance tuning using tools - Runtime Analysis (SE30), Extended Code Check (SLIN), Code Inspector (SCI) & SQL Trace (ST05).
• Was single POC for all the priority 1 incidents. Met both response and resolution SLAs for all the assigned tickets.
• Good coordinating skills with functional consultants.
• Excellent analytical and problem solving skills.
• A motivated team player with excellent inter-personal skills.

TECHNICAL SKILLS:

Data Dictionary: Tables, Structures, Views, Search Helps etc.

Function Library: Development of function modules and remote function calls.

Reporting: Classic lists, Interactive reporting, ALV reporting (using Function modules and Object Oriented programming).

Enhancements: User exits, BADI, Customer Exits.

Cross Applications: ALE, EDI & RFC.

Tools: Menu painter, Screen Painter, Debugging tools.BOL and GENIL Programming.

WORK EXPERIENCE:

Confidential

Environment: SAP ECC 6.0, SAP CRM 7.0

Responsibilities:

• Dispute management issues:
• Populate processor value in the dispute management screen - The processor value was to be fetched from the T001S based on the accounting clerk. Worked using BADI to check if processor value is initial and then populate the extracted processor value.
• Base line date population - In the transaction F-30, baseline date was not being populated correctly.
• Travel and Expenses Portal issues -
• Threshold amount for cash receipts and mileage - The business needed a check on the trip amount and the mileage amount that can be allowed on an expense report. Used function exits, BADI and Web Dynpro components to access and edit the code.
• Rejection report for expense reports - The Trip rejection report had an issue of the status not getting changed but the associated workflow getting cancelled. This issue is throwing the trip into a non-re-usable status. Edited the program which rejects the expense report in order to cancel the workflow id only if the trip status has been successfully changed.
• Adobe form - fax number issue - A particular international expense report adobe form cover sheet encountered a problem with the fax number not appearing. The adobe form had JavaScript encrypted to populate the fax number. Changed the JavaScript to fix the bug.
• Change request on PEXR2001 EDI 820 document - A particular vendor for Confidential required be paid via ACH (Automated clearing house). This required including a 16 digit credit card account number into either one of the exiting segments or into a new segment. Explained the client the feasibilities with both the approaches and convinced them to go about using the existing IDOC instead of extending the IDOC.
• CRM Issues:
• Filter products from the final search list - The requirement was to avoid products belonging to certain categories not be displayed in the search list. Wrote code in the event handler method of the button in the component workbench.
• Search help restriction - The transaction type in sales order search had to be narrowed down to few specific fields. The component ERP S had to be enhanced and the DDLB of the search field had to be restricted with the desired fields.
• One order customer address update - The business needed a pop up to enter customer address appear when a one order customer is entered in the order create screen on the WEB UI. For this inbound and outbound plugs were used to navigate between the order create screen and the BP HEAD component. Also worked with the Navigation Links.
• CRM WEB UI and run time error analysis - A particular button which lets the user write notes for a product in the TPM view was not being reflected in the production system. Figured out the respective Web Dynpro component, view, and the context which had the bug and fixed the issue. In another case, the business was encountering a dump when a particular web based application was run. Analyzed the dump and informed the business of relevant OSS notes.

Confidential

Environment: SAP ECC 6.0, SAP CRM 7.0

Responsibilities:

• This is an implementation project where my contribution involves the technical development activities in areas of CRM sales & service, Logistics, Customer Service, SD, MM and FI.
• Analyzing the Functional Inputs.
• Responsible for object development from Technical design phase through unit testing.
• Automate VDH1N Transaction ( SD ):
• Developed a program to automate the VDH1N transaction.
• The program uploads 3 hierarchies NSD, DSD & Sales management hierarchies into ECC, by letting the user choose the type of hierarchy and the appropriate file the customers can be found in hierarchy in the KNVH table.
• Enhanced an inbound EDI 856 advanced shipping notice IDOC to validate the incoming data. As the middleware was configured with the DESADV IDOC to let in shipping notifications, used enhancement point to perform the validations on data. Enhancement point was chosen as the data as DESADV01 is an obsolete IDOC type and SAP did not provide any user exits for the function module IDOC INPUT DESADV.

Confidential

Environment: SAP ECC 6.0

Responsibilities:

• Analyzing the Functional Inputs.
• Object development and review of the development requests assigned.
• Modified and adjusted the different DDIC objects.
• Prepared technical designs and unit test documents for many RICEFWs
• Coded and created unit test plans for the objects developed.
• IDOC:
• Extended IDOC to accommodate for few extra fields required by the EDI data mapping team. Whenever an outbound Sales order was sent to a Vendor, a field to accommodate any previous sales order corresponding to the same product had to be mentioned. For this extended the ORDERS05 IDOC and wrote the code to populate the respective data into these segments.
• A particular vendor requested that the new PO number be mapped to the old PO if any with the same data and also requested that this data be sent via DESADV01 IDOC after going through certain validations. Instead of changing the standard function module, developed a Wrapper function module to accommodate these changes and configure this to a custom process code.
• BADI:
• Certain BADIs in the production system had many implementations and had no filters set which was causing a performance issue for a particular program. Understood the requirement behind each implementation and set up filter values for each of the implementations and also modified the calling programs by passing the necessary FLT VAL.
• Smart forms:
• Developed smart forms on pre-printed stationary.
• The client had a standard template for their billing documents and the requirement was to include the address and invoice details for each of the customer.
• Used FORM PAINTER to adjust windows according to the template and wrote code to populate the required data in these spaces.

Confidential

Environment: SAP R/3 ECC 6.0

Responsibilities:

• Job monitoring.
• Peer Review of ABAP programs.
• Performance Tuning of ABAP programs.
• Writing technical designs and unit test documents for RICEFWs.
• Enhancements:
• SD - While Creating Sales order, the customer number should get populated automatically in VA01 used the Enhancement V45A0002 and modified the exit EXIT SAPMV45A 002.
• SD - While returning the goods the delivery quantity should not be greater than return order quantity, if this occurs system should throw an error message in V101N transaction. For this used the function exit EXIT SAPLV50P 001 in the eenhancement V50PSTAT to validate for this condition and produce the error message.
• SD - Scheduled background Jobs and respective variants for many programs which were to frequently run.
• A particular RFC which was being called between ECC and CRM for sample order creation had an issue. To resolve this created a new destination in SM59 transaction code with the name DIALOG and established a connection between this new destination and the CRM system. Debugged the RFC by passing this new destination and fixed the issue after understanding the data flow between both the systems.
• Configured VOFM routines to delete certain output types in the output screen of sales order.
• BDC programming:
• Uploaded asset master data using BDC programming.
• Created a BDC recording on the transaction AS01 for the fields in the files and used the option program to prepare the BDC table, modified this program to do the same operation for all the data in the files.

Confidential

Environment: SAP R/3 6.0

Responsibilities:

• Developed an interactive ALV report to display sales order data in the primary or the main screen. By clicking on the output screen the Sales order change screen is called along with the sales order number auto population.
• Developed an ALV report for displaying details of all the purchase orders of a vendor
• Developed an interactive ALV report to display customer details in the primary screen and its sales order details in the detail screen.
• Worked on logo and barcode upload and adjustments on the forms. For the barcode the client had a requirement to create a new barcode pattern, so followed the instructions given by the client to create the barcode pattern and then used it in the smart form.
• A particular form was to be printed in 3 copies ( Bank, Customer, Store). Used copies window and based on the copy count separate three different copies were printed.
• The requirement was to add 3 fields in additional data B tab of the item. The three fields were exported from APO when a check availability is done is sales order. Code was written both in ECC and APO to import and export the fields. Used CIF debugging to find out the BAPI which was responsible for the
• Uploaded material master data using BDC programming. Created a BDC recording on the transaction MM01 for the fields in the files and used the option program to prepare the BDC table, modified this program to do the same operation for all the data in the files.
• Used direct input method in LSMW to upload the customer master data. In the direct input method object attributes specified the program name and uploaded the file and executed the program as per the steps prompted by the migration workbench.
• Developed Transaction variants and the respective variant transactions for MM01, VA01 etc., which were assigned to the corresponding authorized users.

Confidential

Environment: SAP R/3 ECC 6.0

Responsibilities:

• Interacted with the functional team to resolve the issues in the given objects.
• Developed a report that gives critical material classification information to the user for quick access. Attached this report to a transaction code through which the report can be run.
• Developed material master details report.
• Developed a BDC program for Sales order that updated records in the sales order screen using VA01 and VA02 transactions
• Set up the partner profiles and process code for a particular message type.
• Worked on table maintenance generator and did field level validations by creating a module against the desired field.
• Worked on events in TABLE MAINTENANCE GENERATOR - A particular table had date and time fields and the requirement was to pass the current date and time as soon as the user presses enter on the view. Code was written under the On-press enter event.
• Prepared deliverable cover sheets and unit test documents for many RICEFWs.