This is transaction is to be executed manually if needed. This is for sending of personnel number transaction serves the purpose of sending employees as personnel numbers (PA30) from SAP to FSM. When triggering program /PACG/ECM_TRIG_EMPLOYEE_MASTER, the determination of addresses with the 'PERN' type is called.
...
| Info |
|---|
It is required to enter a company ID before executing the program. If not, an error message is displayed at the bottom of the screen ('Fill in all required entry fields'). |
After execution, idocs of type /PACG/ECM_ITYPE_USER (and /PACG/ECM_ITYPE_ADDRESS) are generated.
Send calendar assignment | Send a calendar assignment object during transfer of an employee (if relevant). Learn more about the calendar integration feature: Calendar integration | ||||
|---|---|---|---|---|---|
| Allow transfer of employees (personnel numbers) who are not supposed to be FSM users (i.e. are not added in /PACG/ECM_MAINT_USER - FSM users). Such employees are sent only as employee records, visible in FSM master data. No account-level user is created for them (therefore licence is not consumed). To limit accidental transfer of too many objects, the field is visible only if the option 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 is enabled. When both are activated, employees not added as FSM-relevant users will also be transferred to FSM. Learn more. |
Employee Adress determination
Configuration occurs on two levels.
The general level concerns the settings of the given E4C Company. In this configuration, we determine the general principle of sending addresses. Please note that only one type of address should be marked as 'default'.
The configuration can be found under the transaction '/PACG/ECM_DEFADR' or using the standard user menu '/PACG/EC'
...
The addresses from this configuration are read only when user-specific configuration is missing.
User-specific level. Within this configuration, you can define specific addresses for a specific person. When defining this configuration, it is also important to remember exactly one 'default' address. Once we define the most specific settings for specific users, it is a good practice to set all three types of addresses (Home / Work / Other).
...
This will avoid inconsistencies between the general configuration and the specific one for the user. (i.e. two addresses will be marked as 'default').
The configuration can be found under the transaction '/PACG/ECM_USRADR' or using the standard user menu '/PACG/EC'
...
Technical documentation
The logic for addresses was implemented in the following classes:
/PACG/ECM_CL_S_SEL_EMPLOYEE Employee selection class
/PACG/ECM_CL_S_SEL_USER User selection class
Process
After setting the configuration, when sending people to the FSM cloud system should send 3 Idocs with the appropriate addresses.
Below is a sample test.
...
FSM database result:
...
As long as there is an entry of "HOME/WORK/OTHER" in transaction /PACG/ECM_DEFADR or /PACG/ECM_USRADR, then the addresses from PA30 infotype 0005 will be sent.
In another case, if the employment is not "3 Active", then transaction_type = D will always be sent as this is checked internally. The employment field here is in PA0000-STAT2.
To locate the responsible outbound idoc creation class for a message type, look for the message type in "/PACG/ECM_CLSASSIG - E4C Outgoing Messages Configuration".
...
Skills
Employee’s skills are transferred automatically during Employee transfer. 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.