/PACG/ECM_TRIG_REQ – Requirement

Requirements are retrieved based on customer-specific BAdI implementation (definition /PACG/ECM_REQUIREMENT). Usually they would be sent automatically, manual transfer is not necessary (see the subchapter Prerequisites)

Transfer the requirements of service order operations to SAP FSM. The requirements will be displayed as skills of a related activity.

In SAP FSM a tag is a qualification per se (e.g. German language), a skill is a combination of a tag and a specific person and a requirement is a combination of a tag and an object (e.g. activity).

Requirement profiles

The operation requirements should be maintained in tab ‘Internal’, block ‘Qualifications’, and relate to a certain skill set (qualifications) needed to perform the operation.

Requirement profiles are maintained in SAP standard transaction PO17.

In the example BAdI implementation, priority '0' would make a Requirement mandatory in FSM and any other priority would make it optional. To adjust this logic, create your own BAdI implementation.

Idoc

Requirement objects are transferred with idocs of type /PACG/ECM_ITYPE_REQUIREMENT.

Requirements in SAP FSM

Transferred requirements will be displayed in SAP FSM as skills of a given activity.

Prerequisites

1. Make sure a relevant BAdI implementation exists and is active on your system.

2. Relevant tags (qualifications) should be transferred to SAP FSM beforehand with transaction /PACG/ECM_TRIG_TAG - Tag send. They might require additional customizing in transaction /PACG/ECM_SKTAG - General settings Skill/Tag.

3. If a requirement should be sent automatically with an activity, make sure to check the ‘SendReqAct’ field in transaction /PACG/ECM_SKTAG - General settings Skill/Tag.

4. Object assignment for ‘REQUIREMENT’ and ‘TAG’ should be maintained for each relevant company.

Transaction /PACG/ECM_EOAS - Object Assignment:

Transaction /PACG/ECM_NOAS - No Object Assignment: