Due to significant enhancements in the area of CATS and Person Reservation integration (for instance, support for storing single and multi-day reservations created in FSM; support for modifying/deleting them later in SAP ECC/S4), the object’s key for CATS-based reservations must have been redesigned. If you upgraded to (S4)PACG 200 SP11 and already used the functionality of Person Reservations based on CATS entries (Automatic transfer of CATS entries as person reservations), please execute the program /PACG/ECS_PRES_CATS_KEY_MIGR. This is necessary to avoid duplicates in FSM, in case already existing reservations were updated or deleted. Learn more: Migration of keys for CATS-based Person Reservations
Personal reservations can be automatically transferred to SAP FSM after saving a CATS entry.
Prerequisites
Make sure that the following customizing is maintained:
PR source set as ‘CATS’ in transaction /PACG/ECM_CPERR - Person reservation - general setting
Assignment of the PERSONRESERVATION object to a company in transaction /PACG/ECM_NOAS - No Object Assignment
Att./absence types maintained in transaction /PACG/ECM_T554S - Att./Abs. types for Person reservations
CATS statuses maintained in transaction /PACG/ECM_CPRCS - Person res. - CATS status action
Process
Creation
A CATS entry created with an FSM-relevant attendance/absence type will be sent to FSM as a Person Reservation.
Navigate to transaction CAT2 and create a new entry with an FSM-relevant Att./Absence type.
Save the transaction and notice that an outbound person reservation idoc is generated. All the CATS entries with relevant Att./absence types will be transferred to SAP FSM after saving and will be found on the Planning and Dispatching Board.
Deletion
Deletion of a CATS entry would result in deletion of an FSM Person Reservation.
(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.