Name: Robert D. Guido
Phone: 804-814-6536 (primary) 804-550-1412 (secondary)
Email:
Education:
General Engineering
1975 – 1977
A.S. Applied Sciences - Data Processing
1979 – 1982
SAP Applications
Development - Training
BC010 - SAP Architecture
BC030 - Data Dictionary
BC060 - CPI-C and RFC Interfaces
BC170 - ABAP/4 Programming
BC180 - ABAP/4 Data Interfaces
BC190 - ABAP/4 Dialog-Orientated Batch
Reporting
BC220 - Screen Painter (Developing
Transactions)
1994 - 1995
SAP Applications
Development - Self Study
SAPScript Development
1999 – 2000
SAP Business Information
Warehouse -Training
TABW10 - SAP BW Configuration (2.1C)
TABW20 - SAP BW Extraction (2.1C)
TABW30 - SAP BW Presentation (2.1C)
2001 – 2001
Summary
·
22
years of IT experience with 12+ years of extensive experience in SAP R/3.
·
Worked
on several SAP projects: 2 Start-Up Implementations, 2 Upgrade Projects,
2 Joint Venture Projects and 3
Development Projects.
·
Experience
with the MM, PS, PP, PM, SD, and FI/CO SAP Modules.
·
Data
Migrations (including data conversion) for the MM, PM and SD SAP Modules.
·
Experience
working with the Legacy System Migration Workbench.
·
Developed
inbound/outbound interfaces to the MM, SD and FI SAP Modules.
·
SAP
interfaces developed for the Manugistics, Lawson and Cyborg systems.
·
Creating
dialog transactions using Screen and Menu Painters.
·
Complete
knowledge of the Data Dictionary.
·
SAP
modifications using User and Customer Exits.
·
Application
development using Function Modules / BAPI’s.
·
Dialog,
ALV Grid, SAP Script and Smart Forms reporting.
·
BW
Data Extraction and Infoset Queries.
·
Developed
technical utilities (ABAP Source Library Scan, SAP to Legacy system Data
Mapping, Unix Directory View).
·
Prepared
business analysis and technical design documents.
·
Created
technical application development standards.
·
Developed
documentation to provide guidelines for preparation of business application
specs.
·
Provided
informal training (ABAP/4, Data Dictionary) to client staff including mentoring
analysts.
Note
This resume summarizes 12+ years of SAP experience working
for 9 different companies. It reads like
a technical journal. The information is
indexed with an SAP Subsystem or Work Reference (left margin) so businesses of
different needs can scan through reading only the areas of interest.
Employment Record
Company: PepsiCo,
Dates: April 2006 – March 2007
Position: SAP
Developer/Consultant (SAP R/3 6.0)
FI
Migration Co-developed a conversion application to load
legacy financial data into the SAP Business Warehouse system. The legacy data converted consisted of financial
history, current year operating plans and current year period forecasts. The legacy data was
transformed using cost center, cost element and cost element group
cross-reference tables.
FI
Migration Co-developed a conversion application to
convert legacy G/L Account Balances into the SAP system. The conversion application processed legacy
year-end G/L balances as well as net activity for each period for the current
fiscal year. The legacy data was
transformed using G/L account, profit center, cost center, trading partner, and
tax code cross-reference tables.
Multiple legacy systems were processed by this conversion.
MM
Migration Developed a conversion application to
convert legacy Open Batches data into the SAP system. The conversion processes data from several
legacy systems. Key legacy data was
transformed using material and plant
cross-reference tables.
MM
Migration Developed a conversion application to
convert legacy Inventory Balances into the SAP system. The conversion application also processes
data from several legacy systems.
Multiple legacy to SAP cross-reference tables were used to translate
inventory data between the systems. Data
translations were required for material, plant storage location and inventory
movement types.
Data
Validation The concept behind Data Validation Reports is to be able to
run legacy data analysis reports, prior to executing a conversion, to determine
if potential data errors exist. Knowing
about legacy data errors before hand provides the opportunity to make
corrections which will limit SAP data load errors.
The legacy data was checked to insure that: 1)
all SAP required fields are present, 2) all
legacy data lookups to SAP cross-reference
tables will not fail, and 3) that all data load values will be accepted by the
SAP system without error. This is
accomplished by checking the data load values to SAP configuration tables.
Developed Data Valuation Reports for the
Customer, Open Batches and Inventory Balances conversions.
SD
Migration Developed a conversion application to
convert legacy Customer Contracts into the SAP-CRM system.
The contract
information was broken down into master agreements and subcontracts.
The master agreement contained all the contractual terms that were shared by
the contract owner and its relevant partners where as the subcontract contained
all the terms that differed from the master agreement.
SD
Migration Developed
a conversion application to convert legacy Service Provider and Customer Contract
Rate data into the SAP-CRM system. This conversion
required transformation rules (defaults, xref’s and logic) to restate the
legacy data into SAP system terms. The
legacy data also required data cleansing (record filtering) which involved
evaluating the pricing effective dates to eliminate inactive historical data.
Company: Northrop
Grumman,
Dates: March 2005 – January 2006
Position: SAP
Developer/Consultant (SAP R/3 4.6C)
Work assignments at Northrop Grumman required
the development of custom applications and the modification of existing
production programs within the Materials Management and Project Systems SAP
modules. Assignments required technical
skills in the areas of ALV Grid reporting (including data entry), Dialog
transactions, SAP Script and Smart Forms print documents.
MM,
PS
Reporting Application
Development ( Design Specifications )
1.
Developed an ALV Grid report (Material Planning Alteration) to
display engineering changes for Material Planning documents.
2.
Created a maintenance program to locate
and delete engineering changes that do not have a BOM Linkage.
3.
Developed an ALV Grid application to list BOM materials, allow
data selection / copy functionality (to the Material Continuation Sheet).
4.
Enhanced three ALV Grid data entry applications (Scope Module) to
include new screen fields and/or data validation routines.
5.
Enhanced two ALV Grid data entry applications (Bill of Materials)
to include new screen fields and/or data validation routines.
6.
Developed a Work Package print program (report data collection)
and Smartform (formatted report output).
Work Package data was collected from many SAP tables which included
Documents, Orders, Operations, BOM’s, Characteristics,
MM,
PS
Reporting Production
Support ( Trouble Tickets )
1.
Developed modifications to three user
dialog transactions which involved formatting data for new screen fields,
including data validation routines and adjusting the screen GUI Status to
provide new process functionalities.
2.
Created a utility program to correct
the BOM posting table.
3.
Modified an ALV Grid data entry application to protect grid cells
to prevent duplicate line entries from being created.
4.
Corrected a SAP Script program (Production Order Package Summary)
which had errors printing BOM text.
5.
Modified the BOM Alteration Report (ALV) to correctly display BOM
deletions.
6.
Modified the Engineering BOM Change program (ALV) to correctly
save EBOM item data.
7.
The EBOM change transaction was allowing multiple business users
to access the same data. The program was
modified to lock the BOM data by applying record locks (enqueue/dequeue) for
all BOM levels.
8.
BOM item text was not being handled properly when BOM components
were duplicated using the BOM Tree Drag & Drop functionality. The process was reworked to collect and apply
text information correctly.
9.
Performed several smartform modifications. This work included correcting page
heading/subheadings, adding new document print sections and providing scanner
barcodes next to key document information.
Company: ABB
TotalFlow,
Dates: December 2004 – March 2005
Position: SAP
Developer/Consultant (SAP R/3 4.6C)
The SAP system at ABB TotalFlow was upgraded
from 3.1G to 4.6C. Several programs
designed to load data into the SAP system did not function in the new
system. The following work was performed
to replace and/or correct these programs.
MM
Migration Developed a material master load
program using the SAP Direct Input process.
The program created materials for seven material groups, each having
different data requirements (data views).
Materials created were extended to plant and storage locations. The program also created material classifications
and assigned manufacturing plant information.
The developed program accessed EXCEL spreadsheet data, provided the option of viewing the formatted
data using a direct input utility and provided the option to simulate the material
load to validate the input data.
QM
Migration Modified the Create
Material Routings data load program to process data correctly on the CA01
(Create Standard Routings) transaction. The program establishes material routings for plant work centers.
MM
Migration Modified the Withdraw Materials
data load program to process data correctly on the MM02 (Change Material), MM06
(Delete Material Storage Location) and CS02 (Change Bill of Materials with
History) transactions.
PM
Migration Modified the Material BOM load program to process data
correctly on the CS01 (Create Bill of Materials) transaction. The program processed spreadsheet data using
SAP Batch Input.
SD
Reporting Developed a customer sales order report which provided
details pertaining to customer pricing.
Sales Document, Sales order and Price Condition tables were the primary
data sources for this report. The report
provided the ability to drilldown into related sales order and customer pricing
transactions.
MM
Migrations Developed a BDC data migration program
to extend Kanban materials (MM01) to sales office plants. Developed a BDC data
migration program to create Control Cycle records (PK01) for Kanban materials.
Company: Brookshire
Grocery Company,
Dates: July 2004 – August 2004
Position: SAP
Developer/Consultant (SAP R/3 4.7)
Interface
Utility Developed the technical design
for a Unix shell script needed to trigger SAP batch jobs to process inbound
interface data files. The Unix script
functioned as “Middleware” for all inbound interfaces. The technical design was presented to the
Basis team for approval. The design
document described all interface functionality such as waking up at specified
intervals to check for data, raising SAP events to kick off interface batch
jobs and writing interface activity to a log file (for process review /
debugging capabilities).
FI
Interface Developed an inbound SAP
interface to clear Account Payable checks.
The development of this interface required the following:
1-
Developed naming standards for data files, programs, batch jobs
and SAP Events.
2-
Created an ABAP program to process the inbound bank data file:
a-
Read the bank data from a Unix file directory.
b-
Process the bank data into batch input sessions (FCH6 - Change
Check Information).
c-
Use External Commands (from within the ABAP) to rename the input
Unix file to have a processed date/time stamp and to move the file to a data
archiving directory.
3-
Creating an SAP Batch Job to schedule the inbound interface.
4-
Setting up an SAP Event (used to trigger the interface batch job).
5-
Working with the Basis/Unix team to setup a Unix script needed to
trigger the SAP inbound interfaces. When
interface files are identified, the
script executes Unix program sapevt.exe (with parameters) to raise SAP events
to trigger corresponding interface batch jobs to run. Provided the sapevt.exe
parameters needed to raise the SAP Event for AP Clear Checks interface.
Interface
Utility Developed
9 programs to provide the ability to perform table maintenance. The tables were all user defined tables which
contained Legacy/SAP cross reference information. The work involved activating standard SAP
table maintenance, using the data dictionary to add new table fields, creating
field data elements, developing an ABAP program to capture record change
information (date, time, userid) to the user table and to create transaction
codes for each table maintenance process.
MM
Migration Worked with the LSMW application which
migrates vendor master data into the SAP system. The vendor master conversion used several of
the Legacy/SAP cross reference user tables described above (specifically
customer account, payment terms and cost center translations.). The LSMW application was tested to insure that
the conversion rules within the field mapping definitions continued to function
properly.
MM
Interface Developed an outbound interface to send vendor master
information to several mainframe legacy systems. The development of this interface required
the following:
1-
Creating an ABAP program to extract the vendor data from several
SAP tables.
2-
Translating field values (SAP to Legacy).
3-
Preparing the interface data to a legacy system data format.
4-
Writing the data out to a Unix interface directory.
5-
Creating a SAP Batch Job to schedule the outbound interface.
6-
Executing a Unix script (from within the SAP batch job) to FTP the
Unix outbound interface file to the mainframe system. This was accomplished by using the “External
Program” feature of the SAP Batch Job scheduler.
Company: Cooper
Cameron,
Dates: October
2003 – January 2004
Position: SAP
Developer/Consultant (SAP R/3 4.6C)
Cameron recently migrated from R/2 to R/3 which
made some of the company reporting unavailable.
The plants locations documented report requests (application
requirements) by referring to SAP transactions or reports and noting additional
data needs. Most of the report requests
were lacking the level of detail needed to develop the applications. Therefore, each “report sponsor” was
interviewed (remotely) to determine all the report requirements pertaining to
data collection (data selection options) and presentation (report output format). Technical information (such as data sources,
calculations and data processing) we’re not provided. This information was obtained by studying the
referred-to SAP transactions (or reports) while they were executed in debug
mode. This process of studying the SAP
applications also uncovered valuable subroutines (function modules) which were
incorporated in the developed report programs.
The report sponsors supported the application development process by
making themselves available (remotely) to answer questions, perform testing and
to provide application acceptance.
PP
Reporting Developed a report which provides information about
production orders that have material components in a backordered status
(inventory not available). For each
material component, the program calculates the available inventory by obtaining
the current on-hand inventory level and subtracting all material requirements
(order reservations, dependent requirements and customer orders). The collected material requirements data was
also used to support a popup window, displayed when a material component was selected
for additional information. The report
also has the functionality to jump to other SAP transactions to display
materials, inventory levels and production orders. This report is being used daily by production
planners to address production backorder issues.
PP
Reporting Developed
a forecast deviation report which allows planners to evaluate the sales
forecast of materials (or BOM’s) to customer bookings, or customer sales, or
plant production quantities. Additional
report information includes the calculation of the forecast deviation (shown as
a unit deviation and a percentage deviation).
PP
Reporting Developed a daily unit
scheduling report for production planners to balance the manufacturing
capacities of product assemblies (material components) by plant location. The report program collected capacity
requirements from production work orders as well as planning orders for the
plant.
LO
Reporting The company required a
process to perform ABC Analysis on component level materials only. The SAP transaction MC40 (Usage-Based ABC Analysis)
performs analysis on all materials not distinguishing materials from their
components. A new transaction (ZMC40)
was developed, which runs the SAP MC40 program modules with the ability to
exclude materials by MRP controller from the process.
PP
Reporting Developed a capacity load report which replaces a manual
spreadsheet application which plant locations updated weekly. The report information consisted of work
center capacity allocations and capacity requirements (from work orders and
planned orders). The capacity data was
retrieved from the SAP system using BAPI applications. The capacity data was
organized by work center into 12 weekly buckets. Subtotals by work center hierarchy were
included. The report also calculated the
percentage of the capacity load (all the order requirements) verses the
capacity allocation for each weekly period.
To allow production planners to have the ability to perform analysis
with the capacity load data, the report program was developed with the option
to output the report data directly into an Excel spreadsheet which the planners
could manipulate.
PP
Reporting Developed a program to perform a collective conversion of
planned orders. SAP transaction CO41
performs this function but the transaction does not display all the needed
information about the related order materials.
The report program performs the same data collection as transaction CO41
plus the retrieval of material velocity codes.
One or many of the planned orders displayed on the report can be selected
for conversion. The program calls SAP
transaction CO40 to process each selected planned order into a production
order. The production order number
created from the SAP transaction is captured and applied to the report to
provide a confirmation that the conversion was successful. The report also has the functionality to jump
to the material view, planned order view and production order view transactions
to obtain more detailed information.
PP
Reporting Developed a report to display planned orders (similar to
the SAP transaction MD16). The report
has more data selection options (plant, MRP controller, material and planned
order date) and displays additional information about the materials on the
orders. The report has the option to
export the collected data to Excel for spreadsheet analysis and
manipulation.
PP
Reporting Modified the existing shop load report (also referred to as
dispatch lists). The report program was
changed to allow selected work orders to be re-sequenced for production
planning. This was accomplished by
exporting report work order information to an Excel spreadsheet where the
sequence of the work orders could be changed by planners. When the sequencing of the work orders is
accomplished, the spreadsheet data is reapplied to the report changing the
sequence of the report data. The report
is being used by production planners to prioritize work orders at plant
locations.
SD
Reporting Developed a report to provide information
about the processing time between order entry and shipment confirmation
(delivery to the customer). This report
was titled the “Cycle Time Delivery Report”.
The report would allow order selection by plant, material, material
hierarchy, customer, MRP controller or sales office. In addition to displaying material, customer
and order information, the program calculated the number of calendar days and
work days between the order creation date and the date of when the order was
shipped to the customer. The SAP factory
calendar was used to determine the number of work days between the dates. The sales department is using this report to
measure customer delivery performance.
MM
Reporting Developed a report to display
information about material unplanned consumption. The SAP transaction MM03 (MRP1 Data) shows
this information for one material at a time.
The report allows many materials to be displayed by plant and MRP controller. The report program uses the fiscal
year/periods table (T009B) to determine the current reporting period and the
next 11 future periods. Material
unplanned consumption values are shown over a calculated 12 period range. The report has the
option to export the collected data to Excel for spreadsheet analysis and
manipulation.
Company: Solvay
Dates: April
2002 – March 2003
Position: SAP
Developer/Consultant (SAP R/3 4.6.D)
FI
Interface Developed an outbound interface
application to extract accounts receivable open items. The application created an output UNIX file
locally (data archiving with date/time stamp) which was then sent to a remote
IP address using several SAP function modules.
SD
Reporting The Solvay company had a
need to understand customer net pricing.
A report program was developed to collect customer, material, billing
and pricing data. The report allowed
customer pricing to be viewed by different customer levels (payer, soldto
shipto). The pricing data consisted of
sales price, rebates, commissions and computed net price which was organized by
material and shipping condition.
PS
Reporting Developed a Capital
Project Summary report for the FI team.
The program collected data from the Project, WBS Master, Project Info,
Project Applicant and Company Codes tables.
MM
Interface Created two inbound
interface applications which processed data from the British Petroleum
Company. One interface created material
reservations and the second created goods issues postings.
FI
Reporting Developed an application
which reported on the Accrual of Goods Receipts for Non Valuated Freight. The report collected data from the
Purchasing, Customer, Vendor, Account Assignment and Profitability tables. The report was developed with options to also
post journal entries to record an end-of-month accrual for freight costs
related to deliveries of split shipments.
MM
Data Extracts Created two data extract
programs to support the SAP Joint Venture project (Solvay
MM
Interface Developed an outbound interface
application to extract Inventory Onhand Balances. The application created an
output UNIX file locally which was then sent to a remote IP address using SAP
function modules.
FI
Reporting Developed a Tax Audit
Report which collected data from the Accounting, Vendor, Purchasing, WBS
Element and G/L Accounts Cleared Items tables.
The report allowed for the control of report data by means of many
select options. The report data was
organized by company code, fiscal year and Accounting Documents. The report detail included account open items
posted to expense accounts as well as account closed items. These account items were then linked to other
related tables to collect all the needed financial data to support the tax
audit.
BW
Data Extracts Developed applications to extract Material and Vendor Master data
from the Solvay production system. The
process to create the BW extracts included the following work:
1-
Extract the raw data per specifications.
2-
Review data with business analyst to remove redundant/bad
information.
3-
Data Modeling: Mapping the R/3 data into the BW Master table
formats.
4- Loading the BW Master
Data. (Infocubes)
BW
Queries Created Infoset Queries for the Material and Vendor
Master BW Infocubes. These Queries were
used as templates by the Solvay MM business community. Business analysts copied the template query
and made adjustments to create different views of the data. The initial queries that I provided was copied
by many business analysts, each template query copied 20+ times.
Company: Solvay
Dates: July
2001 – December 2001
Position: SAP
Developer/Consultant (SAP R/3 4.6.B)
SAP Joint Venture Project
(Solvay
MM
Migration Created a
data migration application to create purchase orders for the new joint venture
(JV) plant locations.
PM
Migration Created a
data migration to change plant maintenance equipment for new JV plants.
PM
Migration Created three data migrations to re-state plant maintenance task
lists (equipment, functional location and general task lists) for the JV plant
locations.
MM
Migration The technical staff at the Solvay company decided to load material
master records using the SAP Direct Input method. Due to the complexity of the data to be
loaded, the assigned Solvay analyst was having a lot of trouble getting the
migration process to work. I was
assigned to review the work that was done and to provide consulting
services. Within a couple of days, the
processing issues were resolved and the migration process was reviewed /
approved.
Interface
Utility Created
an SAP interface utility to provide information about processed interface data
files.
The
application was designed to process data files within a specified UNIX
interface directory. The files read from
the directory were used to locate/collect data from within the SAP system to
identify how the files were processed.
Information organized for the output report included data such as the UNIX
directory (file path), file name/description, the related program
name/description, variant name, batch job name/description, file create date
and the create userid.
Company: Phillips
Petroleum Co.,
Dates: July
2000 – May 2001
Position: SAP
Developer/Consultant (SAP R/3 4.6.C)
SAP Joint Venture Project (Phillips /
Chevron).
SD
Migration Developed
applications to load customer master data (contact person) into the SAP system
for the Chevron Joint Venture project.
Reporting Performed work for the Phillips SAP Reporting Team.
1-
Developed a new report for monitoring
freight drop shipments.
2-
Corrected several problems
in the Cost Center/Vendor Report.
3-
Reviewed 150+ programs to determine if
modifications were required to include the processing of the 4.6 history tables
MBEWH, MARDH, MCHBH MKOLH MSCAH MSKUH NARCH MSPRH MSSAH MSSQH.
4-
Performed a major enhancement to the
Cost Center Expense report.
SAP
Upgrade SAP 4.6D System Upgrade project.
1-
Developed a new program (ZPGMJOBS)
which validates the programs on batch job steps. This utility program reports
on batch jobs which have programs that no longer exist.
2-
Developed program (ZCPCFAX) to re-align
CPC European fax phone numbers.
3-
Developed program (ZPPCOFAX) to
re-align PPCO European and Australian fax phone numbers.
4-
Made changes to several SD Tax
programs. (TAXWARE)
5-
Made 4.6 modifications to utility
programs ZJOBDOWN and ZAPPER which are responsible for copying batch jobs
between SAP systems.
6-
Modified to the Z_IDOC_CREATE_ZSDHIST
function module to improve performance.
7-