ERP Connector Architecture
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The ERP Connector Solution Starter for Microsoft Office Project Server 2007 shows how to integrate Project Server with other enterprise resource planning applications, using mySAP™ ERP Human Capital Management solution and the SAP mySAP ERP Financials solution as examples. The ERP Connector relies on a file drop folder on the Project Server computer. A module in the mySAP ERP solution exports XML data to the drop folder. Project Server can also export data to mySAP ERP by saving an XML request in the drop folder.
To help maintain data security, an administrator must initiate actions on the sending system. Data from mySAP ERP is pushed through the Export Services component on the mySAP ERP solution; it is not pulled by the ERP Connector on the server running Project Server. The push architecture satisfies an important requirement for many businesses, that mySAP ERP maintains control of the data. One benefit of this architecture is that you can modify the solution starter implementation of the ERP Connector to integrate with any human resources application or finance application.
Figure 1 shows the high-level architecture of the ERP Connector. Project Server and mySAP ERP each generate XML files that contain data to be exchanged, and drop the files in the shared folder. The ERP Connector Service monitors the file drop folder and starts ERP Connector to process XML request files when mySAP ERP (or a test process) drops an XML file in the folder. As specified in the configuration files, the ERP Connector can log different levels of messages from each component into the system event log.
.gif "Note") Note |
|---|
When the ERP Connector exports actual reported hours from Project Server to mySAP ERP, it transforms the XML data to a comma-separated value (CSV) file. |
The ERP Connector consists of two main components:
Export Services are installed on the mySAP ERP solution.
The ERP Connector and ERP Connector Service are installed on the server running Project Server.
Figure 1. Architectue of the ERP Connector
.gif "General architecture of the ERP Connector")
Export Services on mySAP ERP
The Project 2007 SDK download provides the Export Services in the form of script files that a mySAP ERP analyst must customize before they are installed on the mySAP ERP solution.
Depending on the type of transaction, mySAP ERP triggers the corresponding Export Service module to produce the requested data and send an XML request file to the drop folder. When the Export Service drops a file in the folder, the ERP Connector Service on the Project Server computer starts ERP Connector.
The XML request files from mySAP ERP HCM have the following format:
<Request>
<ProcessHRDataSAP>
. .
</ProcessHRDataSAP>
</Request>
The XML request files from mySAP ERP Financials have the following format:
<Request>
<ProjectCreateSAP>
. . .
</ProjectCreateSAP>
</Request>
The ERP Connector reads the configuration files, and then sends the request data to the plug-in components. Each plug-in that is configured as available reads the request and accepts, ignores, or rejects it.
For exporting actuals from Project Server, an administrator or application on Project Server drops and XML file with the following format:
<Request>
<GetActualsSAP>
. .
</GetActualsSAP>
</Request>
The SAPFIPlugIn component accepts the request, gets the requested work actuals data from the Statusing Web service, and then saves the data to a CSV file in a special drop folder for the mySAP ERP Financials PS subsystem to process. The ERP Connector Solution Starter does not include an application to create a work actuals request. There is a test file for an actuals request in the Project 2007 SDK download.
You can configure the ERP Connector to ignore the request or save it in a folder for rejected requests if a required plug-in component is not available.
ERP Connector on Project Server
There are several components for ERP Connector installed on the Project Server computer.
Connector library. The Connector.dll library contains the common functionality required to integrate between an ERP system and Office Project Server. The Connector classes provide generic functions such as reading the configuration files, authenticating on Project Server, loading and managing plug-ins, creating and updating lookup tables and custom fields, and logging results. The ERP Connector can also detect and load suitable plug-ins to extend its functionality.
Connector command-line tool. The ConnectorTool.exe runs ERP Connector for initial setup and testing.
Connector Windows service. The ConnectorService.exe monitors the file drop folder and runs ERP Connector when an XML request is available.
Plug-in libraries. Plug-ins do the work to process data in an XML request and interact with the Resource, Project, and Statusing Web services of the Project Server Interface (PSI). The ERP Connector Solution Starter includes three plug-in libraries:
SapHRPlugIn handles requests for updating resource and organization data from the mySAP ERP HCM solution.
SapCOPlugIn handles requests for creating projects from the mySAP ERP Financials CO and PS subsystems.
SapFIPlugIn exports work actuals data for a specified time range to the mySAP ERP Financials FI subsystem.
Configuration files. There are XML configuration files for the ERP Connector Service, shared and user-level configuration files for the ERP Connector application, and user-level configuration files for each plug-in. For more information, see Configuring the ERP Connector.
For more information about the ERP Connector components, see Functional Specifications.
See Also
Concepts
ERP Connector Solution Starter for Project Server 2007