Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Current »

General purpose

Specify how skills and tags transferred to FSM should be determined in SAP, as well as their properties.

Sending transaction (?)

/PACG/ECM_TRIG_TAG - Tag send, /PACG/ECM_TRIG_SKILL - Skill send

(S4)PACG 200 SP09 You can navigate to the sending transaction using the button Send to FSM, placed on the toolbar.

Before transferring Skill objects to FSM, please make sure to transfer Tags first. Tags (e.g. English language, driving licence) are connected to employees by SKILL objects and to activities by REQUIREMENT objects. Learn more about requirement objects: /PACG/ECM_TRIG_REQ – Requirement, Skill/Tag Assignment

Object assignment (?)

Object TAG and SKILL must be added to /PACG/ECM_NOAS - No Object Assignment for a given company

Customizing options

Skill source

Specify which source should be used for determination of skills relevant for technicians in a given company. These skills would then be sent automatically whenever an Employee’s master data is sent to FSM or a new qualification is added to the SAP system. You can also send them manually via transaction /PACG/ECM_TRIG_SKILL - Skill send.

(S4)PACG 200 SP11 Click on the ‘arrow’ button to enter the skill sources relevant for a given company and order them based on priority ('1' indicating the highest). If a skill cannot be determined for a given technician from the source with priority 1, it will be searched for in the source with priority 2.

To provide backwards compatibility (upgrade from (S4)PACG 200 SP10 to (S4)PACG 200 SP11), the setup program performs a one-time migration - for all companies for which a skill source was already entered, an entry with priority '1' will be created in the customizing above.

The following skill sources are available:

  • Infotype 0024 - use the qualifications assigned to a technician via infotype Qualifications (e.g. in transaction PA30).

Before skills of this type are sent, make sure that the relevant Tags (qualifications) had been sent. This can be done with transaction /PACG/ECM_TRIG_TAG - Tag send. In the hereby described transaction, the ’Tag source' field should be set to ‘Infotype 0024’.

  • Individual development plant - use the qualifications assigned to a technician via development plan (e.g. in transaction PPDPIM). Such qualifications are stored in table HRP1001.

Before skills of this type are sent, make sure that the relevant Tags (qualifications) had been sent. This can be done with transaction /PACG/ECM_TRIG_TAG - Tag send. In the hereby described transaction, the ’Tag source' field should be set to ‘Individual development qualifications’.

  • (S4)PACG 200 SP11 Work center - use the qualifications assigned to the technician’s work center (e.g. in transaction IR02). Such qualifications are stored in table HRP1001.

In SAP ECC/S4, qualifications can be assigned to work centers. This would indicate that all employees belonging to a given work center share common skills. The effort of maintaining skills per each employee individually is significantly reduced. This skill source determination option takes advantage of this approach. If more than one work center is assigned, the qualifications from all work centers will be used.

Creation/deletion of a work center qualification in transaction IR02 triggers automatic transfer of new skills/deletion requests - changes in SAP ECC/S4 are automatically reflected in FSM.

Before skills of this type are sent, make sure that the relevant Tags (qualifications) had been sent. This can be done with transaction /PACG/ECM_TRIG_TAG - Tag send. In the hereby described transaction, the ’Tag source' field should be set to ‘Individual development qualifications’.

  • (S4)PACG 200 SP11 BAdI - skill determination conducted based on customer-specific implementation (BAdI definition /PACG/ECM_GET_SKILLS). With a developer’s help, you can have full impact on how skills are determined.

Before skills of this type are sent, make sure that the relevant Tags (qualifications) had been sent. This can be done with transaction /PACG/ECM_TRIG_TAG - Tag send.

(S4)PACG 200 SP10 Skip skills with ‘valid to’ in the past

Do not transfer skills whose ‘valid to’ date is in the past, compared to the system date.

Tag source

Determine the source of Tags (representing qualifications). The following sources apply:

  • Infotype 0024 (table T574A/B)

  • Individual development qualifications (table HRP1000)

Tags must be sent to FSM before Skill transfer. You can do it with transaction /PACG/ECM_TRIG_TAG - Tag send.

Tag name source

Source of Tag’s (qualification) name for FSM. Depending on the value in field ‘Tag source’, the following options apply:

Tag source ‘Infotype 0024’:

  • ID - qualification number (see Qualification below)

  • Object Abbreviation - N/A

  • Object Name - N/A

  • Qualification text - (see Qualification Text below)

Tag source ‘Individual development qualifications':

  • ID - qualification ID (see Object ID below)

  • Object Abbreviation (see Object abbreviation below)

  • Object Name (see Object name below)

  • Qualification text - N/A

Tag descr.

Source of Tag’s (qualification) description for FSM. Depending on the value in option ‘Tag source’, the rules described for ‘Tag name source’ (see above) apply.

Send Req Act

Send requirements with activity. Learn more: /PACG/ECM_TRIG_REQ – Requirement

Short skill key

Use short keys, stored in table /PACG/ECM_SKILL, as skill ID sent to SAP FSM.

To save skill attachments as DMS, it is required to have this setting enabled. As a result, object link for /PACG/ECMQ and the short skill key will be created in a DMS document.


  • No labels