Versions Compared

Old Version 12

changes.mady.by.user proaxia

Saved on

compared with

New Version 13

changes.mady.by.user proaxia

Saved on

Key

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

...

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

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://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/360218625 .

FSM Usr ac

Activate/deactivate an FSM user on FSM account level.

FSM User Id

This field is editable only at creation of a user entry in SAP ECC/S4. After saving or for person created from FSM 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.

...