Versions Compared

Old Version 11

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.

...

Info

Creating or changing a person entry in this transaction does not trigger automatic person creation/update in FSM. Manual execution of the dedicated sending transactions for USER and EMPLOYEE is necessary. Transactions https:/PACG/ECM_MAINT_USER - FSM users or /PACG/ECM_ALV_USERS - Mass User Maintenance /proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601665 or https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601806 support automatic idoc generation and are the recommended choice for user maintenance.

Info

This transaction is a simplified version of /PACG/ECM_MAINT_USER -E4C users with addresses

Maintain users relevant for transfer to SAP FSM.

...

Subcontractor

Indicates whether a user is acting as an external supplier / the personnel number here refers to an external technician.

Plannable

Indicates whether a user is plannable in the FSM resource planner

Not active

Make the master data record corresponding to technician/person inactive.

Image Removed

Deactivate an FSM user on company level. The person will be displayed as inactive in FSM Master Data.

Status
title(S4)PACG 200 SP09
Soft delete

Set a user as marked for (reversible) deletion. This field will also be activated if a person is soft-deleted via the offboarding program.

Status
title(S4)PACG 200 SP11
Loginable

Specify whether a user should be able to log into a given company. This setting has impact on the property ‘Login enabled’ in FSM master data:

Permission ID

Assign a permission group based on entries entered in transaction https:/PACG/ECM_VFSMPG - FSM Users' permission groups/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/360218625 .

FSM Usr ac

Image Removed

The setting is similar to field ‘Not active’. While the mentioned setting when set to true will make the master data record corresponding to technician/person inactive, the ‘FSM Usr ac’ field concerns User only.

Image Removed

Indicates whether a user is active on FSM account level. Editable only at user creation viahttps://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601665.

FSM User Id

This field is editable only at creation of a user entry in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601665. Afterwards or for person created from FSM/via other FSM Cloud Connector transactions the field is read-only.

Info

Note:

  • If the login is based on SAP username, the name must be linked to the master data in transaction PA30. PA30-> Maintain or change HR Master Data -> Infotyp: 0105 Subtype: 0001. Link user to the master record (see example below). This is only necessary if there is a need for specific posting to be done by a specific SAP user, else a personnel number will suffice.

  • If personnel records not created yet and ERPUSER is sent, then the first/last name from SU01 is used. Once personnel records created, then the first/last name will be replaced with the ones from PA30.

...


If a technician is set as "Subcontractor", and only has a personnel number assigned to it, both employee (/PACG/ECM_EMPL - Employee) and user (/PACG/ECM_USERMASTER - User) must be sent to FSM as the user (ERPUSER) is the one that allows the logon to the mobile FSM app.

...

Location

Idocs of type /PACG/ECM_ITYPE_USER can contain an additional segment - /PACG/ECM_IS_LOCATION. This segment will be created in object User or Employee if table /PACG/ECM_ALOC is filled with object type PERSON and appropriate ID or BAdI /PACG/ECM_LOCATION is implemented.

...