The document discusses ERP integration between TRACK and SAP systems using BAPIs. It provides an overview of MCI's goals in developing the interface, which were to improve contract to go-live cycle times, provide an out-of-the-box solution compatible with TRACK, and provide single point of contact support. The implementation involves installing BAPIs in SAP environments to enable data exchange via get and post functions for various transactions like purchase orders and timesheets in a synchronous or asynchronous manner.

1. ERP Integration:
Now, More Than Ever
Stewart Graham
SAP Savants
1

2. TRACK / SAP Integration
• Introduction
– Stewart Graham – SAP Savants
• SAP since 1995
• Specialise in PM,MM,PS,CO and QM
• Consulting and bespke development
– Approached by George in 2009 to develop a standard interface
– Today we will :
• Review MCIs goals in the development of the interface
• Review a simplified implementation overview
• Overview of the architecture of the post BAPI SAP/TRACK
environment
• Provide a simple overview of the BAPIs
2

3. TRACK / SAP Integration
• MCI’s goals in the development of the interface where
– Improve the cycle time between contract signing and the actual TRACK
go live
– Out of the box solution that works the TRACK way
– No need for the client to write the inbound and outbound interfaces that
are needed on the SAP side
– Single point of contact for all technical questions – MCI supports both
sides of the interface
3

4. TRACK / SAP Integration
• Implementation Overview
– All of the necessary functionality is in the BAPIs.
– Delivered via an SAP transport to your SAP BASIS team
• Install in DEV and function test
• Move to QA for integration testing
• Move to PROD for go live
– No ABAP resources required
– No Architects, system analysts, PM / MM / PS functional consuktants
4

5. TRACK / SAP Integration
Post BAPI SAP environment
Track
BAPI Layer
Get PM
SAP/PM
Track API Get PS
API
Get MM SAP/PS
Post Timesheet
API
SAP/MM
API Cancel Timesheet
vN.N Client
Database Configuration
5

6. TRACK / SAP Integration
Post BAPI SAP environment
Track
BAPI Layer
Get PM
SAP/PM
XI (PI) / BizTalk
MiddleWare
Track API Get PS
API
Get MM SAP/PS
Post Timesheet
API
SAP/MM
API Cancel Timesheet
vN.N Client
Database Configuration
6

7. TRACK / SAP Integration
• Overview - Get BAPIs (PM / PS / MM / CO )
– Extract SAP transactional data on an agreed frequency
– Each has a selection criteria that can limit the scope of the data
• PM – Plant, Order Type, MAT, Ctrl Key …
• PS – Plant, Order Type, MRP Cntlr, Cntrl Key …
• MM – Plant, PO Type, P.Org, P.Grp,
• CO – Controlling Area, Hierarchy
– Multiple levels of data
• PM – Order->Op->Sub Op->Accnt Assign
• MM – PO Hdr->PO Item->Accnt Assign
• PS - NW Hdr, NW Item, Accnt Assign
7

8. TRACK / SAP Integration
• Overview - Post Timesheet BAPI
– Post Timesheet BAPI does many things :
• Prevalidation of the data
• Creates a Service Entry for the Timesheet
• Creates a Confirmation(s) for the Hrs
– Level of detail to be posted is decided during the design implementation phase
• Aggregate
– For the SES the timesheet lines are rolled into a single cost
– For the Confirmations the TS lines are aggregated by work center
• Detail
– The SES will have a line for each line on the timesheet
– A confirmation will be posted for each line on the timesheet
– BAPI triangulates the data
• Each service entry and confirmation is ‘stamped’ with the timesheet and the
timesheet line (if detail is chosen)
• Ensures that the records can be matched up when reporting and/or
reconciling
8

9. TRACK / SAP Integration
• Synchronous or ASynchronous
– Synchronous : TRACK will initiate the BAPI and wait until the
BAPI returns the results
– Asynchronous
• TRACK will initiate the BAPI and then leave
• Once the task is complete the SAP will, inturn, initiate TRACK and
provide the result
• In this case a token is used to identify which packet of information
is being processed
9