Glenn Allen SAP specific accomplishments at Ford Motor Company

Interfaces Each interface uses the following XI objects: Integration Builder - data

types, message types, message interfaces, interface mappings, configuration scenarios; and SPROXY. Each interface has a class in XI which perform xml parsing, field mapping, and xml rendering. Each file contains a header record with a sequence number and a trailer record with record total. They use a custom Integration Framework common mapping class which validate the header and trailer records. Each interface records any errors or warnings and has the functionality to reprocess.

Build custom object to process Quantitative Tie In (QTI) between ECC and Legacy

(compare inventory quantity). This object required 2 outbound interfaces and an inbound

interface. This object is composed of 3 parts: 1) Transaction which invokes a selection

screen to choose plant(s) and parts for comparison which is saved in a z table. A

scheduled program selects the parts and quantity from MARD, formats the data as a file in a legacy 90 record format, and the file is ftp’ed to legacy. 2) Legacy ftp’s back a file with parts that have quantity differences in a legacy 46P record format. The data is stored in a z table which will be viewed by users via transaction using an editable alv grid. User can mark the quantity for adjustment and the program updates the z table accordingly. 3) A scheduled program selects these marked records, formats the data as a file in a legacy 46P record format, and the file is ftp’ed back to legacy to adjust their quantities accordingly. In production this is a multi-day process end to end.

Co-build custom object for the Actual Cost interface with a junior developer. This object

is an inbound interface. Legacy ftp’s a file with parts and costs that are loaded into the

planned price fields of the material master (costing 2 tab). Use the following bapi’s to

to process: BAPI_MATERIAL_EXISTENCECHECK, BAPI_MATERIAL_

SAVEREPLICA, BAPI_OBJCL_GETDETAIL, BAPI_OBJCL_CHANGE, BAPI_

MATVAL_PRICE_CHANGE.

Maintain custom object for Confirmation, Denials, and Cancellation Orders. This object is an outbound interface. During the processing of outbound deliveries in EWM various

events can happen such as delivery cancellation, machine denials, bin denials, pick denials, goods issue, assessment of freight charges. This information is stored in a file, formatted into a legacy record format, and ftp’ed to various legacy systems. The interface is scheduled on a daily basis and may be run on demand.

Build prototype to ftp outbound files to legacy system using functions FTP_CONNECT,

FTP_COMMAND, FTP_DISCONNECT. Determine the appropriate legacy commands to successfully ‘put’ the file.

Conversions Build conversion object for customer master business partners in CRM.

The object is also used as a daily interface so all of the XI setup referenced in the interface section applies. The object creates, changes, or archives customers. Use the following bapi’s in the object: BAPI_BUPA_CREATE_FROM_DATA, BAPI_BUPA_

ROLE_ADD_2, BAPI_BUPA_SPL0030_ADD, BAPI_BUPA_FRG0040_CREATE, BAPI_BUPA_FRG0020_ADD, BAPI_BUPA_CENTRAL_CHANGE, BAPI_BUPA_

ADDRESS_CHANGE, BAPI_BUPA_SPL0030_CHANGE, CRM_STATUS_CHANGE

_INTERN.

Enhancements Maintain Badi Implementation /SCWM/EX_ERP_GOODSMVT_

EXT, enhancement spot /SCWM/ES_ERP_GOODSMVT in EWM to determine the movement type based on the destination bin of the scrap stock. Build custom tables with table maintenance to store the reference of warehouse, storage bin and the desired movement type. Build function to return document flow, providing a link between it_ordim_c and ct_goodsmvt internal tables within the badi. Work closely with functional consultant testing the badi using transaction sppfp.

Prototype enhancement points for Source List Determination. The source list helps

determine the purchasing document and item for each inbound delivery. Create

enhancement points in program RM06W003.

Mentoring Mentor, train, and support junior team mates. Provide overview of SAP to

team members with no SAP experience.

Miscellaneous Perform various tasks such as investigating short dumps, researching OSS notes, etc. Reverse engineer ‘clearing house’ solution from EU programs and objects.