Senior Integration Consultant

Haribabu Regula

adkxuo@r.postjobfree.com

Mobile: 309-***-****

Summary:

Senior SAP PI, PO, CPI, MuleSoft Integration Consultant with 16+ years of Professional Experience in Enterprise Application Integration and distributed application development. Experience in architecting, planning, managing, delivering, implementing, supporting, administering and monitoring in any of integration solutions.

Professional Summary:

Extensive experience of converting business or functional requirements into appropriate technical solutions.

Expertise in designing high quality software from the requirement specifications.

Practical Exposure of different versions PI 7.0, PI 7.1, PI 7.3, PO 7.4 and PO 7.5.

Hands on experience in PI Upgrade and Migration activities

Expertise in SAP CPI Developer tool and Payload traces and Message Monitoring and Tail logs, expert in Setting up Success factors Integrations using CPI connectivity concepts. CPI Key stores, Credentials deployment, XSD generation and Message Mapping.

Experience in System Integration with different systems like SAP, Salesforce, Ariba, Livelink, Exchange Servers, Active Directory, Hadoop, SuccessFactors, Primavera, DELEGO and HANA using SAP PI 7.3, PO tools.

Worked on CPI DS for integrating with SAP Integrated Business Planning for SCM.

Experience integrating S4 Hana, SuccessFactors, Fieldglass using CPI (Cloud Platform Integration).

Extensively used IDOC, RFC, SOAP, REST, FILE, JDBC, JMS, FTP, SFTP, Mail and HTTPs Adapters and ABAP Proxies for both inbound and outbound data processing.

Design and implementation of Java Adapter Modules for mail channel, SOAP Channels.

Extensively worked on Graphical, XSLT and Java mapping.

Upgraded and tested business critical interfaces from PI 7.11 to PO 7.5

Experienced in Business Process Management (ccBPM, SAP NW BPM) with its Architecture, Process design with editor, Step Types, Correlation, Containers, Process Patterns and Exception Handling.

Good expertise in SOA, designing Proxy to SOAP synchronous scenarios based on 7.3.

Experienced in using File System Transport and Transport using CMS and CTS+ for the transportation of PI content between various instances of PI like development to quality analysis to production.

Worked on camel and JBoss Fuse AMQ environment for asynchronous integrations.

Worked on Managed File Transfer tools like IBM’s GIS, IBM’s SFG and GoAnywhere.

Worked on Reverse Proxy setup for many interfaces, where requests are coming from outside of company’s network like from DELEGO system.

Expertise in the object-oriented programming, analysis and design using UML and in implementing Rational Unified Process using Rational Modeler.

Have designed and developed systems using technologies like Java, Servlets, JSP, JSF, Struts, EJB, JMS, spring, XML and Hibernate, PI and GIS.

Experience working with Developer IDE’S like Eclipse, WSAD, RAD and RSA, NetWeaver Developer Studio.

Proficient in Application Development with Web Technologies, Distributed Technologies and Client-Server architecture environment.

Excellent hands on experience with XML, SOAP, REST Webservices.

Well versed with design methodologies like UML and Design Patterns.

Proficient in writing complex Queries, Stored procedures and Triggers in PL/SQL, SQL.

Worked on Several Operating Systems UNIX, Window 95/98/2000/XP/NT, Linux and AIX.

Possess strong problem analyzing skills with ability to follow project standards.

Good team-management & leading skills, efficient performance in a team as well as independently.

Excellent ability to analyze problems at hand and find solutions

Development of Test cases, Unit Testing and Acceptance Testing of the entire process.

Excellent communication and interpersonal skills.

TECHNICAL SKILLS:

Elements

Particulars

Domain

Auto Insurance, Oil & Natural Gas

Programming Languages

Java, Camel, COBOL, C, C++

Operating Systems

MS-DOS, Unix, Windows, Linux, AIX

Databases

Oracle, MS-SQL Server 2008, MS-Access

Tools / DB / Packages / Framework / ERP Components

SAP PI 7.0,7.1,7.3, SAP PO, CPI, MuleSoft, Java, J2EE, JBOSS Fuse, GIS, SFG, GoAnywhere, Fabric8, Tomcat, Rational application developer, Oracle 12, SQL, Hadoop, GIT, CVS, Star team, Clear Case, Sub Version, Jenkins, Maven, Junit, Perl, Python, Groovy scripts

Education:

Osmania University, Hyderabad, Telangana, India. June 2003

Master of Computer Applications

Professional Experience:

Client: Phillips 66, Bartlesville, OK Nov 2012 to Oct 2018

Role: Senior Integration Analyst

Phillips 66 is a diversified energy manufacturing and logistics company with unique businesses in Refining, Midstream, Chemicals and Marketing and Specialties. During these 9 years, I was part of many integration projects with systems like ERP, Ariba, SuccessFactors, Livelink, Salesforce, Microsoft Exchange, DELEGO, IBP. Also worked PI to PO migration Project and CPI interfaces. I was part of on call rotation to support production issues.

Digital Transformation: Philllips66 started a project AdvantEdge66, to replace the on-premise SAP ERP with S4 Hana on AWS cloud. As part of this, all the integrations were implemented in SAP PO, CPI (Cloud Platform Integration) or MuleSoft. I was part of implementing few interfaces in SAP PO and few of the SuccessFactors, Concur and Fieldglass interfaces in CPI. Developed few custom developed interfaces in CPI instead of predefined content for sending data to SF Employee Central.

Production Support: Phillips66 Integration environment is very complex, as it was migrated with the same design from eGate tool which is java based. They have frameworks like Master data, Rack Inbound, Rack Outbound, Notification system, Control-m. They built a control-m framework so that, each pi interface can be scheduled and monitored by scheduling team and can call the on-call person if a job is running more than specified time. Notification system will read the adapter alerts from mailbox and sends notifications to business users and to developers. It has the capability to create incidents. All the interface details and respective business user, technical user details are maintained in an inbuilt java application called Metadata. We got good understanding of other frameworks like SAARP (SOX Application Access Review Process), MLB (Mapping Ledgers to BCS). Most of these existing frameworks are running with java maps, using modules. Epayables is one of the inbuilt frameworks for vendors to submit invoices electronically. PI accepts .txt, EDI 810 or 811, PIDX xml files as input along with attachments and sends to SAP using RFC. Since developers will not have access to test environment, there is an application called WebSubmit, which will allow user to trigger the job in test with out depending on Control-m team.

Migration of GIS proxy to MuleSoft API: Phillips66 was using Gentran Proxy tool to accept the requests from outside of their network and forwarding them to the integration tools like SAP PI, PO. We have replaced few of them into MuleSoft by exposing API’s.

SAP R3 integration with IBP using CPI DS: Worked on SAP IBP Implementation as CPI DS Analyst. I played a critical role in ensuring the connectivity between the Agent and the application in the cloud. As part of the effort I created scripts that you back-up data files on the agent and ensured we had ability to upload data in case of failure without running the jobs again on the SAP source systems. These jobs are scheduled on monthly basis, few of them on first day of every month and few on 15th of every month.

PI 7.3 to PO 7.5 Migration: Phillips 66 started the migration of dual stack PI 7.3 to single stack PO 7.5. As part of this project, we analyzed and designed the interfaces and worked on migrating to PO. After developing 30% of the interfaces, the project got scrapped, as the company decided to move to S4 Hana. During this effort, I have worked on migrating ccBPM’s to NWBPM and developed many IFlows in PO.

Ariba Integration: ARIBA, an SAP company is a cloud-based application widely used for procurement business of an enterprise. Phillips 66 uses ARIBA for the procurement business. The following are the high-level interfaces between ARIBA and ERP.

Procure to Order: All the integrations under P2O are completely real-time. The interfaces get triggered when a Purchase Order or a Purchase Requisition is created/changed/cancelled in ARIBA. Since, the requests are triggered from ARIBA P2O, they come thru the GIS secure proxy; If the AD authentication is successful, GIS forwards the call to SAP PI which in turns creates the Purchase Order in SAP.

Collaborative Finance (PO and Invoice automation through network): The interfaces developed are Advance ship Notice, Order Confirmation, Quote Message, Catalog Syndication, Goods Receipt, Invoice Status, Invoice Copy, Payment Remittance, Purchase order, Quote Request, Order Confirmation.

Office365 Migration: Phillips 66 moved all its Microsoft products to office 365 which is cloud based software as a service. Because of this, all the integration scenario’s which are using on premise exchange servers need to migrate to cloud exchange server. SAP PO mail adapter provides limited details like connecting to inbox and read emails. So, we used webservices provided by exchange server and these services give the flexibility of getting data specified in the parameter and, we can delete the mail only once all the tasks are done. For some mail adapters, the default modules were failing, when the mailbox owners upgrade to new version. So, developed a module, so that it will filter all the dynamic configuration attributes and send only needed by the interface.

JBoss Fuse AMQ: Phillips66 got JBoss Fuse AMQ as the enterprise broker and converted few of the existing PI interfaces into pub sub model. Work on few interfaces to change the design and use queues for communication. Developed few camel routes too in this environment.

Livelink Integration: Livelink is the document storage system for phillips66. We have multiple interfaces, where the documents need to move from Outlook mailbox to Livelink or move Agreement documents from Salesforce to Livelink or from SuccessFactors to Livelink, and HSE documents to Livelink. Earlier, we used LAPI (Livelink API) which are java based and once Livelink started supporting webservices, migrated them to PI. Livelink webservices need multiple calls to finish load a file. First step is getting authentication token, second step is getting context and then loading the content to Livelink using Upload content method. From PI, some calls are going from PI app server and another from PI DB server. So Livelink was authenticating by IP address, so we added a module to make sure authentication, context and upload happens from same server (IP).

SuccessFactors Integration: Multiple interfaces developed between SAP HR to SuccessFactors. Some of them are related to Learning management system and some are Talent management system. These include, open positions, Job applications, offer letters, Recruitments, Resumes, Candidate start date, contractors create in LMS.

Salesforce Integration: Phillips 66 got two instances of Salesforce. One for UK business and one for US Business. We didn’t use adapter available in the market, instead wrote java map to make connection and get the token id and then made connections to get store data to Salesforce or get data from Salesforce. Salesforce UK interfaces were developed long back and used bulk API. Because the bulk API can only be run in java 6 or higher (currently PI is only on java 5), we were not able to make this a simple straight through interface. It had to be split up into 2 steps. Step 1 is a PI interface that receives the data via the master data service and insert/update in a staging table. Step 2 is a java interface that selects the data from the staging tables, parses it using a SAX parser, formats it to fit the way Salesforce expects it and sends it to Salesforce.

Responsibilities:

As part of SAP PI/PO team, I am working on implementing new projects and supporting existing interfaces.

Got good knowledge on inbuilt frameworks like Master data, Rack Inbound, Notification system, Active directory, SAARP, Livelink, Epayables, Mobile payments, Feeops retail consignments, DELEGO.

Developed a module for Mail adapter, where it is filter other attributes from dynamic configuration and sends only needed by the interface.

Developed another module for SOAP channel in PI for making connection to Livelink using Livelink SOAP webservices.

Extensively used REST adapter to RESTFUL services.

Worked on CPI DS for integrating with SAP Integrated Business Planning for SCM.

Extensively used SOAP adapter to connect to many systems.

Worked on several Salesforce interfaces from ECC and non-SAP systems.

Providing Production support for the existing 700+ interfaces, which are live.

Extensively using ccBPM, Graphical mapping, Java and XSLT as part of interface development and enhancement.

For Managed file transfer, used IBM’s Sterling File Gateway, GoAnywhere tools.

For all the requests coming from outside of Phillips 66 network, used IBM’s reverse proxy technology for authentication.

Supporting legacy java jobs and trying to migrate them to either PO or MuleSoft.

Environment: PI 7.3, PO 7.5, CPI, MuleSoft, SAP ECC 6.0, Camel, JBOSS Fuse, GIS, SFG, CPI DS.

Client: ConocoPhillips, Bartlesville, OK Nov 11 to Oct 12

Role: Lead Java Developer

Project: Transition Enablement

ConocoPhillips is a multinational Energy corporation. I was contracted for the development of ongoing projects and for transition work for their ongoing split of the company into upstream (COP) and downstream (P66) operations.

It required separation of interfaces for both companies as per requirements. There were around 2500 interfaces enabled out of which 75 interfaces are in java and which run as standalone on AIX server or runs in apache tomcat server. I have completely owned the java interfaces and enabled some of the SAP PI 7.1 interfaces as well. I handled interfaces related to active directory, Live Link, Primavera, Sales Force, Exchange Mail server. I also enabled in house java web applications like Metadata, MLB, web submit etc. The PI interfaces enabled during this time are few Rack Inbound interface, SAARP, Notification System, Master data, STAR price orders.

Responsibilities:

Understand the flow of interfaces and identify the connections used in various places like tables, channels and java maps or classes.

Verify the user id’s used are provisioned in the downstream system.

Verify the user id permissions with corresponding system owner like Database Admin, Active Directory Owner and Mailbox Owner

Change the connections with new URLs and user ids in PI channels, staging DB’s or properties files in the downstream AIX servers.

Verified Network and proxy connections

Prepared Test cases in HP ALM Quality Center for the PI or java interfaces.

Test SAP PI or java interfaces with business users for user acceptance.

Resolved any issues in production.

Created Documentation for interfaces enabled.

Involved in on call production support 24/7 for all java and PI jobs.

Environment: SAP PI 7.1.1, SAP PI 7.3, SAP ECC 6.0, GIS, Java, J2EE, Tomcat.

Client: State Farm, Bloomington, IL Jan 2011 to Nov 2011

Role: Lead Java Developer

Project: Underwriter Decision Processing System

The State Farm Underwriters need an application which helps them to take decisions like “caution” or “non-renew” for the members based on their previous claim history in auto or home policies. The application is developed using EJB, spring, pure query and JSF. The decisions taken by the underwriters need to be converted into pdf's and send to members automatically. To achieve this requirement, Control-M job will trigger the batch job which will convert the eligible decisions into pdf format and stores in a shared file store. The print job reads these pdf's and prints the decision letter at appropriate regional office printers using Enterprise print architecture. The interactions between the batch service and Enterprise print service is in asynchronous mode.

Responsibilities:

Completely owned the print batch job of the project.

Used EJB and spring as the framework in designing the application.

Used Pure Query as the backend database layer and configured with DB2 for data retrieval.

Used JMS to interact with enterprise print Java runtime architecture.

Extensively used X-Stream to convert object to XML and XML to object, for generating the pdfs.

Written Junit test cases for testing the modules before delivering the code to clear case.

Involved in regression testing of the application using Selenium.

Used Hudson tool, to build the application and checking check style, and coverage problems.

Apart from developing batch job, I used to merge the code from one stream to other, as development happened in parallel. The merging of code is done in clear case tool.

Environment: Java, JSF, Spring, EJB, JMS, RAD (Rational Application Development).

Client: State Farm, Bloomington, IL Jan 2011 to Nov 2011

Role: Lead Java Developer

Project: Insurance Inquiry

This project replaces the existing VB version of the system with J2EE environment. The application helps the lenders like Banks or financial institutes to check whether the loan applicant is having insurance with State farm. For auto policies the search criteria are last 8 characters of VIN number and last name. For non-auto policies the search criteria are site address or mailing address and company name or last name. This application also helps to change the loan from one lender or financial institution to other. This application also gives the flexibility to indicate that lenders or lender agents will pay the premiums instead of customer.

Responsibilities:

Responsible for J2EE development part of the project.

Used Struts, EJB and spring and web services as the framework in designing the application.

Added Speed lookup DB2 tables for key information to avoid the IMS calls for every detail.

Taken care of writing JUnits, ant build and Hudson setup.

Project Development, System and Implementation testing environment setup with the help of environment team.

Environment: Java, JSF, Spring, EJB, JMS, RAD (Rational Application Development)

Client: USAA, San Antonia, TX Sept 2009 to May 2010

Role: Lead Java Developer

Project: Reduce Inbound Medical Mail (RIMM)

The main aim of this project is to route the physical mails to the vendor AIS (Concentra). Currently the physical mails are coming to USAA. Scanning and indexing of the mails is happening at EDM (electronic document management) of USAA itself. For auditing purposes USAA sends these scanned images to AIS. To minimize the maintenance cost, we are routing the physical mails itself to AIS. AIS will scan the documents, index them and sends the feed to USAA at regular intervals. These scanned images will be picked by batch jobs and stores into Documentum database and notification will be created to the MSR. MSR can request for rescan of the document if, the document is not proper.

Responsibilities:

Understand and analyze the client requirements from Requirements Specification Document and requirement sessions.

Design documents like class diagrams, sequence diagrams using RAD

Coding and reviewed with the client.

Set up the environment for DI (Developer integration), TI (Testers integration) and ST (System test) boxes.

Fixing the defects raised by testers and checking into StarTeam.

Environment: Java, EJB, JMS, RAD (Rational Application Development).

Client: USAA, San Antonia, TX Jan 2009 to August 2010

Role: Java Developer

Project: Enhanced Loss Report (ALR)

The main aim of this project is to enhance the capabilities of the member while reporting a loss. Some of the enhancements include getting context level help from virtual Vicky at different pages. Making the loss report screens dynamic based on the information provided during initial pages. Providing the ability to intimate member the list activities he needs to perform to process the loss (Customer Worklist). Ability to select appraisal assignment and rental assignment process.

Responsibilities:

Owned the component of showing the worklist “to-dos” to the member.

Working on the actions a member can do on the to-do.

Worked on the escalation process, when a to-do is not started by the member.

Setting up the environment for DI (Developer integration), TI (Testers integration) and ST (System test) boxes.

Environment: Java, JSP, Spring, EJB, JMS, RAD (Rational Application Development).

Client: USAA, San Antonia, TX May 2008 to December 2008

Role: Java Developer

Project: Tiger Team (To stabilize the production environment)

The previous projects like provide task list and enhanced assignment of tasks were based on the asynchronous transactions i.e. publish and subscribe model. The reason why they are asynchronous is tables and codes exist in three environments Java, CICS and IMS. Creation of loss is happening in CICS environment and the rules engine to create tasks (BAPM) is in Java. Opening of coverages happens in IMS. So, while creating the loss itself we need to create appropriate tasks. So, events will be published from CICS region and subscribed by BAPM and creates the tasks in work item DB (UDB). The events are becoming out of sequence, and some events are failed and waiting for reprocessing. Manual intervention is needed to again process these events. Because of this, the data in host tables, IMS tables and middle tier tables are becoming out of sync. Finding the reasons why those events are failing and fixing those defects is the main purpose of this team.

Responsibilities:

Understand and analyze the patterns when an event is failing.

Query data bases and check which records are out of sync.

Fixing the defects if exact problem is found.

Writing Perl scripts to make the tables sync manually so that it will not affect the users.

Setting up the environment for DI (Developer integration), TI (Testers integration) and ST (System test) boxes.

Environment: Java, JSF, Spring, EJB, JMS, RAD (Rational Application Development).

Client: USAA, San Antonia, TX Nov 2006 to April 2008

Role: Java Developer

Project: Workmanagement2 (PROVIDE TASK LIST)

The main aim of this project is to provide the list of tasks (Task is a piece of work) which needs to be worked by MSR (Member service representative) during the life cycle of that Auto Claim. While creating the loss report itself, these tasks will be created automatically for the representatives based on the information provided by the member. For automatically creating these tasks we used a rules engine which will validate the business rules applicable for each scenario. This task list specifies who is working on which task and its current status (NEW, WIP, Complete etc.).These tasks are grouped like a tree structure based on associated item information i.e. some tasks are related to items (Claimant vehicles, Insured vehicles, dwelling etc.) and some tasks are related to parties (owner, driver, witness, pedestrian etc.) and some related to loss.

Responsibilities:

Understand and analyze the client requirements from Requirements Specification Document and requirement sessions.

Mainly handled the claims Plan application, which will show all the work items created for that loss in a tree view structure.

Also worked on the actions of each work item, like changing the status of the work item or reassigning work item to different claim handler etc.

Coding and getting the design reviewed by the client.

Fixing the defects raised by testers and checking into start team.

Environment: Java, JSP, Spring, EJB, JMS, RAD (Rational Application Development).

Client: USAA, San Antonia, TX August 2005 to October 2006

Role: Java Developer

Project: Work management (Automate Initial Claims Assignment)

The purpose of this project is automatically assigning the loss to a proper claim handler based on the skills required for handling the loss (auto Claim), line of business, location of the loss. While assigning the loss to MSR, work load balancing needs to consider. Apart from assigning the loss, developed a work management infrastructure application for the MSR’s which specifies the to-do’s they need to work based on date. Also provided work management admin system, where we can specify the employees, their skills, availability and reports on their work.

Responsibilities:

Understanding the requirements from the RSM documents and checking with business for clarifications.

Part of developing worklist related application, where MSR can see his losses which he needs to work.

Came with infrastructure services, which will create work items, retrieve work items based on different criteria.

Used WebSphere work manager concept, which will spawn multiple threads to different databases and merge the results and display to user.

Environment: Java, JSP, EJB, JMS, RAD (Rational Application Development).

Client: USAA, San Antonia, TX August 2004 to July 2005

Role: Java Developer

Project: CLR-Payments and Recoveries Project

The main aim of this project is to replace the current payments and recoveries system with new web-based application. Currently Payments and recoveries are made using legacy transaction like CLPI, CLPY and CLCJ. Need to provide web enabled screens for posting the payments and recoveries.

Responsibilities:

The existing business services are in Mastercraft language which is like C++. This is a model-based language, which is used internally in the company.

Mostly developed the frontend screens for the project using in house PS framework which is like struts.

Environment: Java, JSF, Spring, EJB, JMS, RAD (Rational Application Development).

Contact this candidate