Store Person Reservations as CATS entries

(S4)PACG 200 SP11

When the option ‘CATS’ is selected as the Person Reservation source in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/75464839, reservations created in FSM will be reflected as CATS entries. The solution supports creation, update and deletion of reservations. See also (and perform prerequisites steps): https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/edit-v2/831848449

Integration scope

Creation

Person Reservations are saved as CATS entries with the time slot and attendance/absence type reflecting the properties from FSM. Remarks are stored as CATS short text. Full-day Person Reservations result in full-day CATS entries.

Person Reservations longer than a day result in creation of a few CATS entries, separate for each day (while FSM Person Reservation can span across a few days, CATS entries can be created only for one). These CATS entries are linked to each other in a dedicated table (/PACG/ECM_APRES), thanks to which update/deletion of a reservation in FSM will affect all the related CATS entries in SAP.

Make sure that a given Attendance/Absence Type used as a Person Reservation type allows posting of entries shorter than a day, if such will be posted in FSM. See the view V_T554S, field ‘Minimum duration’. Otherwise the posting will fail.

In certain cases, e.g. based on work schedule / planned working time customizing, SAP ECC/S4 may automatically adjust the time slot of a CATS entry (e.g. shorten it). As a consequence, the Person Reservation in FSM would be adjusted to the time slot saved in the backend. This automatic adjustment is out of FSM Cloud Connector’s control and relies purely on standard HR customizing, FSM Cloud Connector however ensures that the data created in SAP ECC/S4 is reflected in FSM.

Update

Update of a Person Reservation in FSM results in cancellation of all the related CATS entries in SAP and creation of new ones.

Deletion

Deletion of a Person Reservation in FSM results in cancellation of all the related CATS entries in SAP.

(S4) PACG 200 SP11 If a multi-day Person Reservation was created in FSM (i.e. resulted in creation of at least two CATS entries), and one of the related CATS entries was deleted in SAP ECC/S4, the entire Person Reservation would be deleted from FSM and then re-created, based on the remaining data. This would result in splitting the Person Reservation - a separate reservation would be created for each day.

For instance, a three-day-long reservation is created in FSM. It results in three CATS entries. The first one is deleted in SAP. The entire reservation is removed and then two new reservations are sent to FSM, representing the two remaining days.

Similar behavior applies to update of CATS related to multi-day reservations created from FSM - reservations will be split.

Key migration

Implementation of this solution required adjustment and simplification of the object keys generated for CATS-based reservations. If you upgraded to (S4)PACG 200 SP11 and already used the functionality of Person Reservation based on CATS entries (https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/831848449), please follow the steps described here:

Technical table

The table used to store data of multi-day reservations can be periodically cleared using the dedicated deletion report: .