As a result of changes related to the new organization structures, a new users’ maintenance was developed. The previous maintenance /PACG/ECM_USRADR - E4C Users with Addresses is still available but shouldn’t be used in FSM Cloud Connector instances upgraded to Service Pack 3 (and higher).
Creating or changing a Person entry in this transaction triggers automatic Person creation/update in FSM. Manual execution of the dedicated sending transactions for USER/EMPLOYEE is not necessary.
Only administration users can be created in SAP FSM. All other users should be created in SAP only.
Employees not added to this transaction can still, under certain circumstances, be transferred to FSM, without creating an account-level user (consuming licence). Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515/PACG+ECM+CPROP+-+General+Properties+of+FSM+Cloud+Connector#(s4)pacg-200-sp11-Per-w%2Fo-FSMUser
The new maintenance is based on a cluster view /PACG/ECM_VUSER. The cluster structure is following:
Users’ definition
Users Company assignment
Organization Level allocation
Addresses source for Users
Users assignment to Teams
Please refer to the section below to find the details corresponding to each cluster level:
Users’ definition - Within the top level the generic user settings can be defined
(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.
User | Enter SAP User to define its details. Either a username or a personnel number should be entered, but never both. Learn more about how to link a personnel number to SAP user: Preparation of user in SAP |
Display User | If SAP User is entered, then the button Display User appears, which leads to User Maintenance (SU01 transaction) and allows more user details to be viewed. |
PersNo | Enter Personnel Number to define its details. Either a username or a personnel number should be entered, but never both. If a personnel number is entered and a user linked to this number is retrieved (from PA30, based on infotype: 105, subtype: 001), the username will be automatically filled, and the personnel number field will be cleared. |
Display PersNo | If Personnel Number is entered, then the button Display PersNo appears, which leads to Maintain HR Master Data (PA30 transaction) and allows more personnel number details to be viewed. |
FSM User Id | Specify FSM User Id. Once FSM User Id is entered, saved and sent to FSM, it is non-updateable and cannot be changed later on in the cloud. This field is read-only, in case when when user was previously created in the FSM in the cloud. |
Perm ID | Assign a permission group |
FSM Usr ac | Specify whether the FSM User is active. This setting is available in the FSM admin panel where user can be activated or deactivated.  The setting is not relevant, when maintained as default.  |
Created On /Time / Created by | Read only fields automatically updated after the creation of a new entry |
Changed On /Time / Changed by | Read only fields automatically updated after the change of an existing entry |
Users Company assignment - Within this configuration, a user defined in the level above can be assigned to a company
Company ID | Enter the company ID to assign the user/personnel number. A single user can be assigned to multiple companies in the organization and in each assignment user can have different roles and settings. |
|---|---|
Subcontractor | Indicate whether a user is acting as an external supplier or the personnel number refers to an external technician. |
Plannable | Indicate whether a user is plannable in the FSM resource planner. |
Not active | Indicate whether the FSM master data record corresponding to technician/person is inactive. This is related to the entry in the FSM Master Data in the People section, where one can set the active employee flag to true or false  |
(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. Hard delete can be done in separately transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1957691394. |
(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:  Since in the previous service packs this property would always be set to ‘true’, in order to keep backwards compatibility the setup program marks all existing FSM users as ‘login enabled’ (during the first post-upgrade execution). The flag must be enabled for an FSM user to be created in FSM (on account level). When a user is first added to the user maintenance with this flag disabled, it won’t be created as an account-level FSM user. |
User crowd type | Specify the user crowd type; available options are non crowd, owner, admin, partner technician. |
Organization Level allocation - Within this configuration a user can be assigned to a specific organization level within a company
Learn more about organization structures: Organization
Org level | Define the organization level within the company to be assigned to the user. A single user can be assigned to multiple org levels and in each assignment user can have different roles |
|---|---|
FSM Role | Specify the FSM Role Name for the user within the specified organization level. Available roles - Manager or Member are provided and maintained by default while running set up connector program. Available roles are non-updatable. |
Created on / Time/ Created by | Read only fields automatically updated after the creation of a new entry |
Changed on / Time of change/ Changed by | Read only fields automatically updated after the change of an existing entry |
Addresses source for users - Within this configuration the address can be defined for a specific person. For each user, the default address can be sent to cloud, depending on the settings maintained in /PACG/ECM_USERG – User – General Settings in the "No address" checkbox.
If address for a given technician should be determined using the rules common for the entire company (https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953288), do not maintain any entry. This sub-node serves the purpose of maintaining address determination exceptions, unique rules for a given technician which differ from the /PACG/ECM_DEFADR customizing.
Address Type | Specify the types of address available within FSM (Work, Home, Other) |
|---|---|
DfA (Default Address) | Indicate the default address to be sent to the cloud (subject to user general settings). When defining this configuration, it is important to set exactly one address as default. |
STy. (Subtype) | Subtypes are subdivisions of infotypes. The various subtypes of an infotype can be assigned different time constraints, and a separate data history can be maintained for each user or personnel. 
|
AddrSource | Specify technician’s address source. INFOTYPE 0006 ADDRESSES / OLD LABEL NONEUse the address from infotype 0006 as technician’s address. PERSONNEL AREA ADDRESSThe address will be taken from the personnel area for the currently processed employee/user. SHIP-TO ADDRESSBy default, determine technician’s home address based on its business partner’s ship-to address. Linkage between a technician and its business partner should be configured in transaction /PACG/ECM_WRHKU - E4C warehouse - Customer Consignat. If more than one business partner is assigned to a technician, one entry should be checked as 'Def. Ship-to Partner'. The address is determined during transfer of an employee with transaction /PACG/ECM_EMPL - Employee. If no customer-user relationship is found in /PACG/ECM_WRHKU, a log is displayed and no address is sent. Determine a technician’s home address, territory and region based on its business partner’s ship-to address.  
Linkage between a technician and its business partner should be configured in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137655 . If more than one business partner is assigned to a technician, one entry should be checked as 'Def. Ship-to Partner' and serve the purpose of address source. 
The address is determined during transfer of an employee with transaction /PACG/ECM_EMPL - Employee. The territory object key can be found in an idoc of type /PACG/ECM_ITYPE_USER, segment /PACG/ECM_IS_GROUPDATA. 
The region object key can be found in the same idoc, segment /PACG/ECM_IS_REGIONDATA. 
Apart from an idoc of type /PACG/ECM_ITYPE_USER, an idoc of type /PACG/ECM_ITYPE_ADDRESS is generated. The customer’s ship-to address can be found in segment /PACG/ECM_IS_ADR. 
It is possible that the technician’s business partner has multiple SH partners defined. If one of the SH partners is marked as Default, then the address of that SH will be used. If more than one SH partners will be found and none of them will be default, no address data will be sent. 
|
Users’ assignment to Teams - Read only view which provides the information of all teams to which user is assigned
Team GUID | Read only field providing the GUID information about the team to which the user is assigned |
|---|---|
Team Name | Read only field providing the name of the team to which the user is assigned |
After applying changes and pressing the SAVE button all created/updated/deleted records from Users' definition and Users Company assignment level should be sent to FSM. In the transaction version delivered in Add on 2105 and above, employee (personnel number) record linked to the user is sent and updated as well.
Please be aware that in the transaction version delivered in SAP Add on 2105 and above, deleting the users results in soft deletion. The deleted users will be removed from FSM but this action will be reversible by re-uploading the user. In such a case the user will be assigned with a previous ID and its history in FSM will be preserved.
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.
Skills
Employee’s skills are transferred automatically during Employee transfer (after technician customizing update and saving). No additional customizing is required to enable it. The result is identical compared to executing transaction /PACG/ECM_TRIG_SKILL -Skill send for a specific company and personnel number.
To avoid sending of Skill objects more than once (if certain Skills were already sent earlier), enable hash handling for message type /PACG/ECM_SKILL in transaction /PACG/ECM_CLSASSIG - FSM Connector's Outgoing Messages Configuration.