Versions Compared

Key

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

...

TZ source

Source of time zone:

  • 1 Person’s work center address

  • 2 Person’s plant address

PR Source

Specify how person reservations created in FSM should be stored in SAP ECC/S4, as well as how FSM reservations can be created from SAP ECC/S4.

The following options apply:

  • HR

    • FSM→SAP ECC/S4: Person reservations created in FSM will be stored as an Absence or Attendance HR infotype record for a given technician.

    • SAP ECC/S4→FSM: HR infotypes with the FSM-relevant attendance/absence type can result in generation of an FSM person reservations. Learn more: Person reservation sent from SAP HR Master Data

Expand
titleExample of a reservation created based on HR infotype

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:

BlPSGinKey

Status
colourBlue
title(S4)PACG 200 SP06

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:

...