This is the transaction for manual sending of person reservation (only for infotype 2001 or 2002) by personnel number (PA30) from SAP ERP backend to FSM Cloud. This is usually not needed to be used unless it is not automatically sent.
...
| Info |
|---|
Updates here do not update / create any CATS entry. |
...
Exclusivity status is transferred as the value of the 'Exclusive' field held in idocs Transaction /PACG/ECM_TRIG_PRERV serves the purpose of sending person reservations from SAP to the cloud. The only obligatory field is Company ID.
...
| Status | ||
|---|---|---|
|
| Expand | ||
|---|---|---|
| ||
|
| Expand | ||
|---|---|---|
| ||
|
Usually there’s no need to use it since data entered in PA30 as Absences are sent automatically with idocs of type /PACG/ECM_ITYPE_PERSRESERV.
...
The reservation can be found on the Planning and Dispatching board as a striped field.
...
The sending report is called /PACG/ECM_TRIG_PERSRESERV. It transfers relevant reservations from the PA2001 table, based on the selection criteria. It can be noticed that all the entries of this table contain a personnel number.
...
| Info |
|---|
New idocs of type /PACG/ECM_ITYPE_PERSRESERV are generated only if a person reservation is sent with the deletion flag and then resent again. If a reservation already exists, logs inform that no new objects were created. |
Setting the delete flag.
...
An idoc of type /PACG/ECM_ITYPE_PERSRESERV has been generated (with deletion flag) and the reservation disappears from FSM.
...
Resending without the deletion flag.
...
An idoc of type /PACG/ECM_ITYPE_PERSRESERV .
...
has been generated.
...
The reservation can be found again.
...
| Info |
|---|
Learn more about person reservation: Person reservation |