October 2000 to January 2001
Designed and built several interfaces using IDOCs ALE scenarios
and TCP for a supply chain project at this large transportation
company in the South East.
Modules: SD, FI, PS.
Tools: ABAP tools, IDOC, ALE, ALE Scenario, BAPI, EDI,
MQSeries and MQSI middleware, Ascendent documentation, Data Dictionary.
Other: MVS interface, NT interface, Unix scripting, FTP.
ABAP analyst/programmer for a number of
interfacing projects in a major implementation of Supply Chain
Management. Designed, built and implemented several projects using
IDOC, ALE Scenarios and BAPIs in conjunction with MQSI and MQ-Series
middleware and direct interfaces utilizing TCP/IP services. These
included:
SD interface from
legacy MVS/ES9000 to SAP system utilizing MQ-Series, IDOC and
SD BAPIs to enter sales orders in the SAP order chain for
Surplus and Accommodation Sales from parts inventory. Standard
order entry ALE scenarios were used
B2B interface to
external vendor for employee deduction accounting. The FI data
originated from EDI and manual invoices sent from vendors which
are paid via employee deduction. An ABAP program creates IDOCs
which are queued to the middleware and then via TCP/IP to the
vendor which processes the payroll (Win NT 4.0 system).
Inbound interface
from MVS, involving the creation of JCL on the MVS legacy system,
TCP/IP transmission of data to the SAP host Unix system (HP9000-
HP/UX) and the creation of Unix scripts to initiate an ABAP program
which creates an inbound IDOC which is subsequently, via ALE,
processed by a function module. The system processes labor hours
which are allocated to SAP PS (Project Systems) WBS (Work Breakdown
Structures) and internal orders for ultimate FI/CO expense and
asset accounting.
As the customer is in a Federal overseen business, all work was performed to exacting standards of quality and documentation. Duties on this project included knowledge transfer.