Professional Documents
Culture Documents
Table of Contents
1. Interface Monitoring - Primavera ......................................................................................................... 4 1.1 Context Information........................................................................................................................ 4 2 Monitoring / Error Handling CAP Side .............................................................................................. 4 2.1 Primavera ...................................................................................................................................... 4
2/7
3/7
4/7
The primary objective is to ensure that planning is done right before carrying out scheduling and resource optimization. Unless planning in SAP is accurate then SAP cost plans and reports will not be meaningful. This set of interfaces is bi-directional and triggered on-demand. It includes the following functionalities:
MANI011 SAP to Primavera Interface Creation of a project out of SAP and into the target system Update of detailed work order operations from target system to SAP Update of planned hours, durations, work centers, dates and relationships from target system to SAP MANI014 Primavera to SAP Interface Update of progress from target system to SAP Update of user & system statuses from target system to SAP Update of any changed data from SAP to target system Update of master data (project & WBS basic data, resources, rates etc) from SAP to target system
Last saved: 2/19/2014 9:01:00 PM 5/7
Impress is the middleware which triggers the interface runs and synchronizes the work orders between SAP and Primavera. Batch jobs would be set up in Impress usually to run every day. Impress application log provides the status of the batch run and the details of messages (success, warning, error etc).
Select the line of interest from Previous Runs and click View Report. New window Update Log opens.
Select Error line and click on Details. Log opens in a new window.
The log would contain the error message as shown in example below.
6/7
Embedded document below lists the various failure, cause for it and possible fix. For the test environments, the fix recommending contacting help desk is not applicable.
7/7