This is a new version of the user maintenance transaction for FSM Cloud Connector instances upgraded to Service Pack 3 (and higher). Transaction /PACG/ECM_USRADR - E4C users with addresses became obsolete.
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://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.
This transaction is a simplified version of /PACG/ECM_MAINT_USER -E4C users with addresses
Maintain users relevant for transfer to SAP FSM.
The users which should to be transferred to SAP FSM must be defined either with SAP username (SAP user) or personnel number (employee), but never both. It is to be noted that only the combination of user + personnel (employee) OR personnel (employee) is a valid combination of data to be available to FSM.
(S4)PACG 200 SP07
Until add-on 200 SP07, if an SAP user was linked to an employee, only username would be displayed (and otherwise only personnel number). Now, both username and personnel number will be displayed simultaneously if both exist for a given FSM technician.
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. |
(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. |
(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 /PACG/ECM_MAINT_USER - FSM users. Afterwards or for person created from FSM/via other FSM Cloud Connector transactions the field is read-only. |
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.
Subcontractor
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.