| Note |
|---|
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). |
| Info |
|---|
| Info |
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. |
| Info |
|---|
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 |
| Info |
|---|
Only administration users can be created in SAP FSM. All other users should be created in SAP only. |
| Info | ||||
|---|---|---|---|---|
|
The new maintenance is based on a cluster view /PACG/ECM_VUSER. The cluster structure is following:
...
User | Enter SAP User to define its details. Either a username or a personnel number should be entered, but never both.
| |||||
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 cloudThis 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. | |||||
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 |
...
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  | ||||||||
| Set a user as marked for (reversible) deletion. This field will also be activated if a person is soft-deleted via the offboarding program.
| ||||||||
| 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: 
| ||||||||
User crowd type | Specify the user crowd type; available options are non crowd, owner, admin, partner technician.
|
...
| Info |
|---|
If address for a given technician should be determined using the rules common for the entire company (https:/PACG/ECM_DEFADR - Company addresses/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 /
Use 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.
|
...
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.