You are on page 1of 7

Interface Monitoring

Standard Operating Procedure


GAME_SOP_MAN.XX.XX.XX Interface Monitoring (Primavera)

Date: 13 Aug 2013 Version: 1.1

GAME SOP MAN.XX.XX.XX.XX Interface monitoring (Track)

Table of Contents
1. Interface Monitoring - Primavera ......................................................................................................... 4 1.1 Context Information........................................................................................................................ 4 2 Monitoring / Error Handling CAP Side .............................................................................................. 4 2.1 Primavera ...................................................................................................................................... 4

Last saved: 2/19/2014 9:01:00 PM

2/7

GAME SOP MAN.XX.XX.XX.XX Interface monitoring (Track)

Amendment history for document


Revision No 1.1 Revision Date 13 Aug 2013 Author(s) Kumar Loganathan Comments/Major Changes Initial Document

Last saved: 2/19/2014 9:01:00 PM

3/7

GAME SOP MAN.XX.XX.XX.XX Interface monitoring (Track)

1. Interface Monitoring - Primavera


1.1 Context Information
The GAME IT landscape comprises several 'Connected Applications' interfaced with GSAP. The daily batch run will have to be monitored to ensure that errors reported will get solved. The GAME design for Interface Monitoring (MAN.XX.XX.XX.XX) SOP describes how to monitor and handle the errors in the Game Interfaces batch jobs. The target readers are the nominated Super users at sites who need the GAME070 role to perform these activities. It should be noticed that the actions described here are very technical and hence it is not expected that they are performed by users on the 'process' side (Inspectors for IDMS, Instrumentation staff for INTOOLS, Reliability engineers for RCM etc...). If an error is detected by the 'GAME070' super User, he will contact the relevant Process person if necessary.

2 Monitoring / Error Handling CAP Side


2.1 Primavera
2.1.1 Overview
Primavera P3e is the scheduling tool for both ME & TA processes together with a bidirectional interface. The diagram below shows the hardware design of PrimaVera, Impress and SAP.

Last saved: 2/19/2014 9:01:00 PM

4/7

GAME SOP MAN.XX.XX.XX.XX Interface monitoring (Track)

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

GAME SOP MAN.XX.XX.XX.XX Interface monitoring (Track)

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).

2.1.2 Handling Impress Synchronization Failure


Log on to Impress application and select the workspace. o Go to Synchronization tab

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.

Last saved: 2/19/2014 9:01:00 PM

6/7

GAME SOP MAN.XX.XX.XX.XX Interface monitoring (Track)

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.

Primavera_Impress_ Error List.xlsx

Last saved: 2/19/2014 9:01:00 PM

7/7

You might also like