Ansicht
Dokumentation

RPWI1000 - Integration with Logistics: Read Interface File and Generate Session

CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

New Procedure as of Release 4.0

As of Release 4.0, this report is replaced by the RPWI1100 report. The RPWI1000 report must be run one more time, however, in order for the data from the old interface table AFRUHR to be read.

If you are distributing for Release 4.0, you must begin this report absolutely before distributing your system.

Description

This report generates a batch input session to retrieve Logistics confirmations using the interface between Logistics and HR. The retrieved confirmations are stored in a session either as time tickets or as attendances. It is often necessart to treat confirmations from PM/PS as attendances, since a labor utilization rate is not necessarily calculated here.

The report supports four operation modes:

If Logistics and HR are run in different (distributed) systems, select the operation mode IDoc. The operation modes Online and Session are used if Logistics and HR are run in the same (central) system. The operation mode Statistics is used both in distributed and in central systems. It generates statistics on the confirmations that have been read. The data is not posted.

If you select the operation mode IDoc, the confirmations are transferred from the Logistics system to HR using ALE functionality. In this case, the report must be run in the Logistics system. For information on the required customizing settings, please see the ALE scenario Transfer Logistics confirmations to HR. A batch input session is then generated during inbound processing in the HR system. Time tickets are always posted in one block. Attendances are posted one by one.

If processing is carried out Online, the transaction for entering time tickets or attendances is processed in the foreground. This is for test purposes only. The data records are not posted or logged.

The operation mode Session generates a batch input session.

The value in the Number of data records field determines the maximum number of confirmations that should be processed in one block. An individual session or IDoc can contain more records, however, since all confirmations belonging to a personnel number are entered in the same session or IDoc. The value in the field must always be greater than 0. After a block of records has been processed, the database is updated. One IDoc or session is created for each block.

In the operation modes IDoc and Session, the report writes a log to the interface file which indicates whether the confirmations were successfully entered in an IDoc or session. Confirmations which have not been processed successfully are logged as containing errors. Once the errors have been eliminated, the confirmation can be retrieved again with the report. To do this, select the option Confirmations with errors.

The confirmations which have been entered successfully in a session can be read again by the report and entered in a new session. It is necessary to do this if an existing session has been lost due to a hardware error, for example. Select the Activate repeat run button. You can now specify when the interface file was last accessed (date and time).

Press the Deactivate repeat run key to retrieve new or incorrect confirmations.

Procedure

Notes

Batch input or IDoc for Incentive Wages: By default, a premium time ticket (time ticket type 01) is generated.

Batch input or IDoc for attendances: You can choose the attendance type the appropriate report parameter.

Choose the menu path Human resources --> Incentive wages --> Environment --> Logistics --> Reorganize to reorganize the interface file by deleting confirmations. In a distributed system, you must be in Logistics to do this.

The retrieval of confirmations is based on status monitoring, particularly of the fields "Status of first read access" and "Status of last read access." Before the interface file is read for the first time, both statuses are "Not yet accessed." When the file is read for the first time, the status is set either to "successful" or "unsuccessful" and is not changed. Each time the file is read (including the first time), the status of the last read access is set to either "successful" or "unsuccessful." The status is reset each time the file is read.

Each time the interface file is read, the system logs the date, time, and user name.

When the entry is created in the interface file (write access), the date, time, and user name are logged. The same information is logged on the first time the entry was successfully read.

Technical notes

You can generally add your own data to time tickets (e.g. a different time ticket type) before they are entered in the session. In order to do so, you must implement the enhancements to function exit EXIT_SAPLHRIW_001 in the SAP enhancement HRPINW01. For information on SAP enhancements, please see the online manual on transactions SMOD and CMOD.

Description

Requirements

Output

Example

Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 6443 Date: 20240520 Time: 143454     sap01-206 ( 139 ms )