/PACG/ECM_CPERR - Person reservation - general setting

Source of time zone:

• 1 Person’s work center address

• 2 Person’s plant address

Determination of person reservation source – use CATS or HR infotypes Absence/Attendance.

HR

Use HR infotype Attendance or Absence as FSM person reservation.

Example

Create a new absence in transaction PA30:

The absence’s type is maintained in transaction /PACG/ECM_T554S - FSM Absence and Attendance Types Definition as relevant for SAP FSM, company 8:

The person reservation is automatically transferred to SAP FSM, company 8 and can be found on the Planning and Dispatching Board:

CATS

For this functionality to work, proper mapping should be maintained in transaction /PACG/ECM_CPRCS.

Each CATS status can be mapped to an action. Not mapped statuses are treated the same as option ‘Do not send to FSM’.

If time start/time end data are missing in CATS, they can be statically set in transaction /PACG/ECM_T554S (whole day absence/attendance)

Learn more about person reservations in general: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/75464839/PACG+ECM+CPERR+-+Person+reservation+-+general+setting#PR-Source---example

Option determinate what kind of key is sent to FSM with Person reservation type.

Key is a combination of field MOABW (PSG) and AWART (A/AType) which they can be set up in /PACG/ECM_T554S. When checkbox is marked then key has always blank MOABW (00) regardless of the type of absence. This solution allows to avoid duplicate same absence types in FSM when company has multiple PSG and each of them have assigned the same A/AType. In example below company 1000 has assigned Attendance/Absence type Leave in two areas: PSG 1 and 2.

In that case checkbox should be enabled. Inside outgoing Idoc with Person Reservation Types (/PACG/ECM_ITYPE_PERSRESERVTYP) is new id that it doesn’t duplicate existing Absence/Attendance types on FSM side:

On cloud application are available Reservation types without any duplicates:

In incoming message with Person Reservation, type is determinated by technican data where MOAB is fetched from his Personal subarea (T001P). Finally the type is sent to SAP with the same result as id: