Versions Compared

Old Version 2

changes.mady.by.user proaxia

Saved on

compared with

New Version Current

changes.mady.by.user proaxia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When the option ‘CATS’ is selected as the Person Reservation source in transaction /PACG/ECM_CPERR - Person reservation - general setting, 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

...

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

Info

Status
title(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

Status
title(S4)PACG 200 SP11
and already used the functionality of Person Reservation based on CATS entries (Automatic transfer of Person Reservations created based on CATS entries as person reservations), please follow the steps described here: Migration of keys for CATS-based Person Reservations

...