Ansicht
Dokumentation

PTRM_SE_PLAN_ARRANGMNT_DELTA - Report for TravelPlanning ArrangementEmployeeNotification - Delta

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.

Purpose

This report program is used to trigger the outbound proxy TravelPlanningArrangementEmployeeNotification_Out, which is used to send employee data out of the Travel Management system.

Integration

Prerequisites

For this program to execute, an initial setup must exist. You make this initial setup by running the report PTRM_SE_PLAN_ARRANGMNT_SETUP just once before you run this report for the first time.

To deactivate the setup, you run the report PTRM_SE_PLAN_ARRANGMNT_SETUP again by choosing the Deactivate Setup button.

Features

Selection

The selection screen is based on the logical database PNPCE. The selection screen allows you to select the employees, whose data you wish to send out of the Travel management system.

In the case of a CE scenario, if at least one work agreement of an employee matches the selection criteria, then all the work agreements of the employee are sent as a whole (all-or-none principle).

The report program also has 2 modes of operation:

1. Normal run
2. Error run

Standard Variants

Output

The output includes an application log, which is stored in the database with the following details:

• Log object: HR_PTRM_SE

• Log subobject: DISTRIBUTION

The application log contains the status for each employee as to whether processing was successful.

Activities

You can run the program in one of two modes:

• Normal

This is the normal destruction scenario in which the outbound proxy is called to distribute the data for only those employees who match the selection criteria and whose data has changed since the last run.

• Error run

In this mode, the outbound proxy is called for those employees who match the selection criteria and who had an error when its data was sent the last time - hence, the need for sending it again.

How does the report program work?

1. The logical database PNPCE retrieves all employee numbers that match the selection criteria.
2. The last date and time when data was sent for each employee that matches the selection criteria is read from a log table called PAD_SE_DELTA_LOG.
3. For each employee, the system checks whether the employee's data has changed since the last run.

• The PCL4 table is read for each employee to see if an entry exists in the table (an entry exists only if data was changed).

1. If an employee's data has changed, the system reads the data. If the data is successfully read, the system sends it through the outbound proxy.
2. The log of the employee data being sent is maintained in table PAD_SE_DELTA_LOG. This table contains the following information:

• Employee number, date of last successful run, time of last successful run, error status

• An error status set to 'X' indicates that an error occurred when an employee' s data was being read or sent.

• In the CE scenario, if only one work agreement contains an error, none of the work agreements of the employee are sent and all work agreements of the employee have the error status 'X' in the log table.

1. If the system discovers that no data of a particular employee has changed since the last run, the employee's data is not sent; however the log table PAD_SE_DELTA_LOG is updated with the date and time of the current run.

Example

General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4176 Date: 20240520 Time: 044604     sap01-206 ( 58 ms )