SAP-GIS-EDI Integration

From the Trenches

The Challenge

Confirm that an outbound Idoc has been received by GIS and create a link between the Idoc and the GIS BP that processed it.

The Solution

A GIS BP called from the central Idoc processing BP maps the outbound Idoc’s control segment and a status code of 12 to a STATUS Idoc. An XPath query pulls the BP ID from Process Data into a message variable in the STATUS Idoc, which is then sent to SAP through the SAPSuite Adapter. The outbound Idoc is updated to status 12 and the BP number posted in the Status Record.

Consulting Services

Strategic Vision: Software systems design, architecture and documentation including evaluation and selection of technology and vendors
SAP and EDI Project Planning and development approach and methodologies
EDI and legacy interface business process discovery and documentation and requirements gathering for custom development
Interface process and data analysis including a wide variety of standard X12 transactions, Idocs, RFCs and custom file formats
SAP XI interface development, configuration, testing and documentation
Sandard SAP Idoc interface determination and configuration and custom Idoc development, including coding of custom Idoc processing functions
Custom ABAP development including data conversion using LSMW or custom batch input programs, ALV and ALV Grid Reports, user exits, transactions, SAPScript and anything else required to do the job
Gentran Integration Server BP Development for a wide variety of standard and custom EDI interfaces, including mapping in GIS and Contivo Analyst, set up of partners, envelopes and configuration of adapters including FTP, File, HTTP SOAP, SAP RFC, SAP File-based RFC and SAP BAPI.
Mentoring, Training and Knowledge Transfer