William S. Kempt

**** ***** *****

Missouri City, Texas 77459

281-***-**** (home) / 832-***-**** (cell)

(acehuu@r.postjobfree.com)

PROFESSIONAL PROFILE

Twenty years of Information Systems experience specializing in developing and implementing business

applications, and supporting various technical components of an infrastructure. Functioned as a system

analyst, systems engineer, business analyst, and lead programmer analyst.

Over fourteen years of experience in SAP, providing services in SAP-EDI sub systems, Process

Integration and ABAP programming. Also over six years of Websphere Transformation Extender

development, including extensive mapping and systems design and deployment.

FUNCTIONAL SKILLS

Business Systems: Proficient in developing EDI solutions for SAP/ABAP with a strength in Sales and

Distribution module (SD) and also knowledgeable in SAP EDI/ABAP MM & FI

business solutions. Adept in Process Integration design, development and

implementation. Also experienced in ABAP/4 programming development, IDoc

extensions, data analysis and capable in the use of Websphere Transformation

Extender (formally Mercator) and UNIX scripting.

Operating Systems: UNIX (Solaris and AIX), Microsoft NT & MPE/XL

Software: Comprehensive knowledge in SAP-(EDI, ABAP and PI), Websphere

Transformation Extender, FORTRAN and C.

SAP Versions: SAP/R3 2.2D – ECC 6.0

Training: SAP/R3 courses instructed by SAP:

• CA210 SAP-EDI Interface

• CA910 Application Link Enabling (ALE)

• BC610 SAP Business Workflow (Programming Workshop)

• BIT400 SAP NetWeaver Process Integration

Education: Bachelor of Science in Computer Science

Texas Southern University

SKILLS HIGHLIGHTS

• SAP/EDI specialist with immense IDoc experience and ABAP coding changes (SD, MM, FI)

• SAP Process Integration design, development and implementation

• Process Integration design, configuration and data mapping (graphical and UDF)

• Adapters used in PI (RFC, FILE, HTTP, FTP, XI, IDOC, and Mail)

• ALE knowledgeable

• EDI specialist with ANSI X12 and EDIFACT experience

• Websphere Transformation Extender mapping specialist

• Involved in over 6 major corporate implementations

SAP PROFESSIONAL HIGHLIGHTS

NRG Energy (formally Reliant Energy) Oct 2013 – present

Houston, Tx

• Member of the EDI Team for NRG Energy. Joined team as a short term member while one of the

regular members was on maternity leave. Responsibilities included process documentation,

monitoring team mailbox for job errors and on call support. As a temporary member of the team my

primary role was to create documentation for incoming team members including spreadsheet creation

for all production jobs that defined all process parameters, timings and problem resolution. The

processes were for UNIX jobs and Websphere Transformation Extender map execution.

Baker Hughes Oct 2006 – Sep 2013

Houston, Tx

• Returned to Baker Hughes to retire the Websphere Transformation Extender (WTX) system

developed in 1998. Transitioned approximately 185 inbound and outbound interfaces to another ETL

tool and/or retired the interface. During the same timeframe BHI began using SAP Process

Integration (formally Exchange Integration) product for internal interfacing and became the lead and

sole Baker Hughes developer in PI. Assisted in the implementation of the following projects via

design assistance, installation and support. Brazil Nfe (Nota Fiscal Eletronica) Invoicing, Argentina

Invoicing and Maximo Asset Management. Conducted all ongoing maintenance and development.

Designed and developed a Mexico Nfe Invoicing process that was moved into production in Mar

2013. Used several different adapters including Mail, RFC, IDOC and HTTP.

• Detailed task/skills used at BHI:

o Currently working as SAP integration architect/developer for BHI using SAP PI (SAP PI

7.1 EHP 3).

o Design & develop several interfaces (CLM, Nfe Mexico) in PI including mapping

development with data from customer master data, vendor master data and invoices.

o Worked with user groups in insure all business needs were completed.

o Worked with an external vendor (Grupo) to design and deliver data.

o Reviewed and modified functional specs and technical specification documents as

needed.

o Worked with external consultants in the implementation of project: Nfe Argentina, Nfe

Brazil, MAXIMO and MDM.

o Design and created Data Types, Message Types, Service Interfaces, Operation Mapping,

and Message Mapping programs for each of these interfaces.

o Configured Communication Channel, Receiver Determinations, Sender, Receiver

Agreement & Defining Web Services for the interfaces developed in PI.

o Used RFC, FILE, HTTP, FTP, XI, IDOC, and Mail adapters in PI.

Timken Feb 2006 – Oct 2006

Canton, Oh

• Developed technical design documents for several EDI interfaces (inbound purchase orders,

outbound invoices, outbound shipment notifications and outbound invoices via DataStage to and

external data warehousing system). Created extensions for INVOIC02 and FIDCCP02 IDocs,

designed, developed all supporting ABAP code needed for the corresponding IDoc enhancements.

All interfaces were developed in SAP (5.0). Participated in testing (unit & functional acceptance) and

development walkthrough sessions with users, functional and technical team members as a means of

quality assurance. Also performed standard EDI partner configuration, logical system creation and

ALE Distribution Modeling (for the Data Warehouse Interface) for development and test

environments.

Honeywell Aug 2004 – Feb 2006

Phoenix, Az/Minneapolis, Mn/Albuquerque, Nm

• Designed, developed and implemented the inbound SPEC2K orders process for Honeywell

Aerospace GMS. Task consisted of ABAP enhancements to the existing SAP BADI delivered

SPEC2K processing to meet industry standards and Honeywell business practices. The BADI was

also enhanced to analyze inbound SPEC2K data to determine if the data should be processed in SAP

or sent to a Honeywell legacy system. The S1BOOKED & S1NVOICE (and any acknowledgements)

transactions were interrogated based on material (S1BOOKED) or invoice number (S1NVOICE),

tables MARD and VBRK respectively. If the material or invoice number were found in SAP the data

was sent to SAP, otherwise it would be processed by one of two legacy systems as determined by the

inbound iATA address. The Honeywell guidelines were for the SPEC2K process to handle all

SPEC2K transactions; this development did not include REPAIRS transactions. All S1BOOKED

acknowledgments were to be generated from SAP, even those orders that were not processed via

SAP. The standard inbound orders EDI functions are called by SAP after the BADI processing, using

standard delivered function module and BDC processing via the ORDERS05 IDoc type. Performed

additional enhancements to add data to the standard segments using ABAP code to meet Honeywell

business practices.

• DSES (Defense & Space Electronic Systems) – Responsible for the WAWF (Wide Area WorkFlow)

data transmissions between Honeywell and the Department of Defense. Developed training

documentation for users of Honeywell Wave II processing and performed data analysis, created

mapping documents and coordinated all other aspects as relates to WAWF processing.

Reliant Energy Mar 2003 – Aug 2004

Houston, Tx

• Member of the EDI Team for Reliant Retail Solutions. I was transitioned as the primary developer

and support of all of the Energy Supply interfaces (approximately 12). This role included daily support

of existing interfaces as well as design and development of modifications to existing interfaces. We

also developed reporting for 3 of the interfaces to enhance user visibility into data share between

systems. The primary systems involved were SAP, Siebel and Deal Capture. Also responsible for

educating and documenting the ES interfaces for my team.

• Became primary Batch Enrollment interfaces, which included extensive modifications to the

Mercator (DataStage) mapping for address parsing. This interface received a flat file from a Siebel

system and converted the data into IDocs, which were then loaded into SAP.

• Resumed role as primary developer of UNIX scripting.

• All data translation was done using Mercator (v6.5 and 6.7) in an AIX environment including use

of multiple Mercator (DataStage) adapters and IFD setup and deployment.

McDonald’s Restaurants of Canada Oct 2002 – Jan 2003

Toronto, CN/Chicago, Il

• Member of the Innovate development team working as part of McDonald’s worldwide

implementation of Oracle and Mercator (DataStage). The goal of the project is to standardize the

reporting of both individually owner and company owned restaurants. Canada was chosen as the

first site to undergo the standardization. The development team was responsible for the interpretation

of functional specifications documents and the creation of a corresponding technical specifications

document. The technical specifications were then used in the development of Mercator (DataStage)

maps. The maps were tested in 3 phases, individual testing, unit testing and user acceptance testing.

The architecture was based on MQSeries queues as the transport and storage area for data before

processing. The Mercator (DataStage) maps were designed to extract data from an interface specific

queue using Mercator (DataStage) adapters, perform validation and then transformation with a

database destination. All communication with other platforms was performed using Mercator

(DataStage) adapters. Any errors were reported to a central Global Error Handling function. The

platforms used were NT and Sun servers and the version of Mercator (DataStage) was 6.5 (211).

Rayonier Performance Fibers Sep 2002 - Oct 2002

Jesup, Ga

• Designed, coded and tested a delivery SAP (version 4.1) IDoc for Rayonier Performance Fibers.

The IDoc was part of an implementation with a 3rd party shipper RELY Systems and the documents

will be sent to RELY in batch mode. The IDoc extensions and supporting ABAP code were both

enhanced to include all the necessary fields for the two business partners. The system was designed

such that the changes to a delivery document are made as the NAST record is created. The NAST

records are then processed via a standard delivered SAP program and IDoc output was generated.

The project work was on schedule in the client defined three weeks.

Reliant Energy Mar 2001 – May 2002

Houston, Tx

• Member of the EDI Team for Reliant Retail Solutions (Unregulated). My duties consist of

translation and testing for the Outbound 820 to JP Morgan Chase, the outbound 820 for the TDSP's,

two internal Batch Enrollment interfaces and a variety of Team related support functions. All

translations were from x12 or flat file into IDoc or from IDoc (SAP 4.6) to x12. Also included was the

development of several Mercator (DataStage) maps regarding Texas Set Validation and the

generation of errors when validation failed. All data translation was done using Mercator (v5.0) in an

AIX environment including IFD setup/deployment and Commerce Manager. Also responsible for

design and development of several UNIX scripts used throughout the environment.

Accenture Consulting Feb 2001 - Mar 2001

Chicago, Il

• Worked in the Accenture Solutions Center as a member of the SAP/EDI team performing problem

resolution for Nortel in North Carolina. Nortel was experiencing problems in sales order output in

SAP 4.6 on two clients. There had been prior code ABAP modifications made to an output

requirements module that did not function properly on both machines. The first solution was to get

the configurations synchronized. The second solution was to make some minor modifications in the

output requirements module to have the output generated only when needed.

Motorola Corporation Sep 2000 - Feb 2001

Tempe, Az

• As a member of the EAI Team our primary directive is to control the interfaces for project Mercury.

The interfaces were of several types, including ALE/IDocs, BAPI’s and flat files. The SAP version

was 4.6. Also an existing data routing system that uses Mercator needed some enhancements and

monitoring. One of the major enhancements being performed is upgrading to the most recent version

of Mercator (5.0), increasing the stability of the system and improved error reporting. The system

uses an Oracle database to retrieve application map execution details and maintain application map

statuses.

• Another part of the assignment at Motorola is the IMS Bridge project. IMS is a legacy system that

needs to remain synchronized with SAP. The proposed design involves Mercator and an array of MQ

Series Queues. A single IMS transaction could encompass several messages, thus the messages

need to be prioritized and all must contain a transmission ID that is unique to one IMS transaction.

This information will be populated into the message ID of each message. Mercator will send a

message to IMS that represents a portion of an IMS transaction. IMS will then respond with the

success or failure of that message and the Mercator map will either continue to send the remaining

messages for that transaction or begin to process the next transaction.

Dell Computer Corporation Jun 2000 – Aug 2000

Austin, Tx

• Member of the Polaris Team. Assigned with the responsibility to develop a broker or routing

system for XML documents using Mercator. The broker system interrogates the XML header of each

document and distributes that document to a number of subscribers. The communication link

between each system is MQ Series or FTP. Mercator serves as a middleware piece to handle

communications with each subscriber. Also tasked with the responsibility of documenting all

developed processed and maintaining of a portion of the project plan. Finally responsible for the

mentorship of additional Dell employees that would maintain all developments.

Baker Hughes Incorporated Jul 1998 – May 2000

Houston, Tx

• Member of the Project Renaissance ADAPT team serving as a mentor to BHI employees with

little and no SAP experience. Also member of the Utilities Team, which designed and implemented a

File Dispatch System (FDS). The FDS was used for conversions and interfaces to transport data

between application systems using Mercator (DataStage). The Utilities Team was also assembled to

assist other ADAPT team members with any Mercator (DataStage) data mapping relating to any

conversions and interfaces. Finally as a member of the EDI Team we converted legacy EDI

transactions into SAP/R3 and developed new transactions for the BHI environment.

• BHI purchased Mercator (1.4.1) with the intent to use the product to translate data for interfaces and

conversions. As part of the Utilities Team we developed the File Dispatch System (FDS) that took full

advantage of Mercator and it’s Adapters. The FDS was used for inbound and outbound interfaces

and became the primary means of moving data. Mercator was hosted on an NT server and it moved

files between the UNIX and several AS/400’s.

• BHI also had existing EDI business relationships that needed to be migrated to SAP. We successfully

converted five outbound and two inbound transactions into SAP.

850 Purchase Order: Configured several trading partners for standard outbound

purchase orders.

810 Invoice: Outbound and inbound invoices were setup for over 20 trading

partners. The outbound included customizations to include the

condition type in the E1EDK01 segment for header taxes. Also

made a similar modification for E1EDP04 segment for line item

taxes. Finally, modified the pricing conditions in the E1EDP26

segment for several BHI specific prices. The Inbound approach

required a pre-processor to read an IDoc to verify GL Account

and Cost Center related data and also to actually build an IDoc

from a legacy format.

REMADV: Assisted in configuration of ACH payments for accounts payable

checks and ACH payments for HR Payroll both International and

Domestic. 820 Direct deposits payments for payroll both

International and domestic.

Status Records: BHI also required that status records get updated into SAP for all

EDI documents. Designed and coded an ABAP program to

process the inbound status records.

Purchase Cards: Inbound UDF (User Defined File) format read via a custom ABAP

developed preprocessor program and converted into an inbound

810 IDoc with message type INVOICE. Each line item on the

inbound invoice represented a summary of charges with an

individual purchase card. The inbound invoice was processed

into SAP using standard EDI functions.

Celanese Limited Nov 1997 – Jul 1998

Dallas, Tx

• Member of the ATLAS team with the responsibility of conversion of four legacy systems EDI

transactions into SAP R3. The role on the team consisted of the design, ABAP coding and

implementation of the transactions. Also responsible for the translation of IDOC data to a predefined

application file format using Mercator (DataStage). Task also included the development of error

processing procedures as well as documentation surrounding the transactions developed.

• Configured, modified and enhanced SAP EDI Subsystem and its delivered code to adhere to

specific business practices. Made extensive modifications to the standard delivered code via user

exits to provide additional data in order to maintain the current business applications. In addition to

the application enhancements IDOC extensions were also performed to support the new data. EDI

configuration has been done in the SD module and some in FI. Specific EDI transaction which were

developed/enhanced are as follows:

304 Shipping Instructions: Added capability to forward outbound sales order data to the

freight forwarders. Included IDOC extensions to handle special

reference data and hazardous materials information.

304 Shipping Confirmation: Inbound document changes to accept the confirmation from the

freight forwarder.

301 Booking Request: Code modifications to extract additional data to send to freight

forwarders.

301 Booking Confirmation: Changes to receive the booking confirmation from the freight

forwarders

Compaq Computer Corporation Aug 1994 – Nov 1997

Houston, Tx

SAP Project experience (Jun 1995 - Nov 1997)

• Began working on the data conversion team in June 1995. Responsible for the conversation of

sales orders from an ASK OMAR environment into SAP. The method chosen for the conversion was

EDI. Perform data gap analysis and directed and participated in program modifications to convert the

data. Joined the EDI team in June 1996 and began the task of implementing sales orders (ANSI 850)

and sales order responses (ANSI 855). Also served as a team lead responsible for five other analyst.

Involved in decision making for business process development of the 810, 860, 865, 856 and 870

transactions. Conducted weekly meeting with business group users and make frequent reports to

management. Made program modifications to maintain the current business practices for the

Canadian trading partners. Also made extensive modifications to upgrade the SAP/R3 functionality to

COMPTIA standards.

Contact this candidate