| Note | ||||
|---|---|---|---|---|
Due to significant enhancements in the area of CATS and Person Reservation integration, the object’s key for CATS-based reservations must have been redesigned. If you upgraded to
|
Personal reservations can be automatically transferred to SAP FSM after saving a CATS entry.
Prerequisites
Make sure that the following customizing is maintained:
...
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.
| Expand | ||
|---|---|---|
| ||
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.
| Info | ||||
|---|---|---|---|---|
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. |