SUMMARY

• He is a Senior SAP consultant with 21 years of SAP implementation experience, 3 ½ years big five experience (Accenture, formerly Andersen Consulting), and 20 years of systems implementation experience.
• He has 19+ years of ABAP experience, 17 years of SAP EDI experience, 10 years of SAP PI experience, and has worked with many other SAP technologies (ABAP, IDOCs, IDoc Archiving, ALE, EDI, HIPAA, Automotive 3.0, RFC, Workflow, Data Migration, BAPI, BDC, FI - AM, FI-AP, FI-AR, FI-GL, CO-PCA, CO-PA, CO-CCA, CO-ABC, HR, ESS/CATS, SD, MM, WM, PP, ASAP, GXS, GENTRAN, Harbinger, Mercator, etc.).
• He is also a certified FI/CO functional consultant with 8 months of FI configuration experience (FI-AR, FI-AP, FI-GL, FI-SL). Confidential has been an ASAP project manager, technical lead for a Europe wide implementation, a team lead several times.

PROFESSIONAL EXPERIENCE

Confidential

PI Developer (SAP PI 7.30)

Responsibilities:

• Because of Confidential ’s amazing growth, they always have several IT projects in process to keep up with the growth. While with UA, I was the PI developer on 7 projects. The following are the projects, a brief description of each, systems included, and number of PI interfaces for each project.
• All retail allocation for UA’s brand houses and factory outlets were being done manually. JustEnough software was implemented to automate the retail allocation process. There were 6 interfaces between SAP ECC, JustEnough, and EPICOR (POS & Retail).
• UA consolidated their B2B & Equipment room websites into a single website, UATeam.com. There were 11 interfaces between SAP ECC, UATeam website, and EEM (Transportation Management System).
• To support UA opening their first retail store in Europe, they extended their retail system (EPICOR) to include Europe. This required 2 new interfaces and modifications to 5 existing interfaces to accommodate different currencies, new stock requirement categories, etc.
• In order to offer their customers Endless aisle, save the sale, and ship from store functionality, UA implemented Omni Channel software. All web transactions, B2B transactions, and EDI transactions were re-route through Omni Channel, so Omni Channel could support the new functionality. There were 12 interfaces between UA.com, UATeam.com, GXS, Omni Channel, SAP ECC, and EEM (TMS).
• With the addition of several new stores in the EU, UA decide to extended the automated allocation process to the EU retail stores. This required modification of 3 interfaces between SAP ECC and JustEnough. This also required several SAP configuration changes.
• In the past, these countries have been served by 3rd party distributors. UA developed a website for each of these countries and opened a warehouse in each country to support the fulfillment of the web orders. There were 8 interfaces between SAP ECC, Business One, and 3PL (Geodis Wilson).
• Because of UA’s growth, their warehouses were usually at 110% capacity. Therefore, they were using trailer’s in the yard to store the overflow materials and tracking what was in each trailer manually. They added YardView software to automate this process, so they had better visibility of what materials were stored in the trailers in the yard. There were 9 interfaces between SAP ECC, YardView, and EEM (TMS).

Confidential

EDI Lead

Responsibilities:

• Project background - This project was an initial SAP implementation for Keurig and they were switching EDI translators to Seeburger Business Integration. I was responsible the conversion of the customer EDI, vendor EDI, and the EDI with their 3rd party logistic providers.
• EDI - I worked with the MM, SD, and FI analysts to gather EDI requirements, develop functional specs, developed technical specs (including mapping documents), gathered EDI production data for testing, and created a detailed parallel test plan. I managed a team of 4 EDI Seeburger developers that setup the Seeburger system, created EDI connections to VAN, mapped customer and vendor EDI transactions, integration tested, go-live, and supported post go-live. Keurig uses the EDI ANSI standards and the transactions included 810, 820, 850, 856, 875, and 880.
• PI (7.31 Single Stack) - PI was used for the EDI interfaces between Keurig and their warehouses (3PLs). All EDI transactions with the 3PLs were pass through interfaces in PI. I configured the all the EDI interfaces with the 3PLs in PI. Transactions included 214, 846, 856, 940, 944, 945.

Confidential

EDI Analyst

Responsibilities:

• Project background - Due to substantial success, Confidential had outgrown their collection of custom systems. The project was to integrate all of the functionality into SAP and sunset the outdated systems. TOMS had some customer EDI, but the bulk of their EDI was with their 3rd party manufacturer and logistic providers. I was in charge of the EDI interface with their 3rd party manufacturer & logistic providers.
• EDI - I gathered EDI requirements, developed functional specs, developed technical specs (including mapping documents), gathered EDI production data for testing, monitored EDI map development by GXS resources, created a detailed parallel testing plan, coordinated and unit tested all 6 EDI objects with 3 providers, supported 4 rounds of integration testing, developed go-live plan, developed detailed post go-live support plans, trained users for post go-live support, and implemented solution successfully. TOMS uses the EDI ANSI standards and the transactions included 832, 850, 856, 940, 944, and 945.

Confidential

EDI Lead

Responsibilities:

• Project background - Confidential partnered with IBM to implement SAP. This was Confidential first SAP implementation, so customer SAP experience was limited. Confidential has 19 different EDI objects, 450+ customers/vendors, and does ~$21 billion through their EDI system. This is an extremely large amount of volume for EDI. Before I arrived, a decision had been made to leave the EDI translator (GENTRAN) on the legacy mainframe system and use IBM’s WPS middleware to translate the outbound SAP IDocs to the existing legacy flat file format, and the inbound legacy flat files from GENTRAN to the SAP IDoc formats. This added a level of complexity to an already difficult process.
• EDI - Managed a team of 11 resources that gathered EDI requirements, developed functional specs, developed technical specs (including mapping documents), gathered EDI production data, monitored EDI map development in WPS, created a detailed parallel testing plan, unit test all 19 EDI objects, supported 6 rounds of integration testing, developed go-live plan, developed detailed post go-live support plans and escalation procedures, re-engineered the support ticket process and implemented a very complicated solution successfully. Confidential uses the EDI ANSI standards and the major transactions included 810, 820, 832, 850, 855, 856, and 862.