External Activity Types and Activity Subtypes

External Activity Types

Activity Types are transferred to SAP FSM as Enumeration objects of type ACTIVITY_TYPE.

A proper Enumeration value should be maintained in transaction /PACG/ECM_ENUMV - Enumeration value. The ‘Enum. Type’ field should be filled with ‘ACTIVITY_TYPE’.

Open

Enumeration objects should be transferred to SAP FSM with transaction /PACG/ECM_TRIG_ENUM – Enumeration. Make sure that ‘ACTIVITY_TYPE’ is entered in the ‘Enumeration Type’ field.

Open

The object is sent in an idoc of type /PACG/ECM_ITYPE_ENUMERATION.

It can then be found in SAP FSM Settings and Configuration, tab ‘Planning and Dispatching’ -> ‘Activity’.

The new Activity Type can be selected on the mobile app (displayed by description):

For automatic mapping of internal Activity Types with External Activity Types during Activity transfer, maintain entries in transaction /PACG/ECM_ACTMAE - Activity code mapping: 

During transfer of an E4C Activity to SAP FSM, it is no longer checked if an Activity Code is maintained in obsolete table /PACG/ECM_EXTAD (transaction /PACG/ECM_EXTACTDEF - External Activity Definitions).

Summary

External Activity Codes should be:

·       maintained in transaction /PACG/ECM_ENUMV - Enumeration value as ‘ACTIVITY_TYPE’

·       transferred to SAP FSM with transaction /PACG/ECM_TRIG_ENUM – Enumeration

·       mapped with an internal Activity Type in transaction /PACG/ECM_ACTMAE - Activity code mapping

Activity Subtypes

Maintain an entry in transaction /PACG/ECM_ACTMAE - Activity code mapping and tick it as ‘Is subtype’.

Transfer the Subtype with transaction /PACG/ECM_ACTSUBTYPE - Activity Subtype:

An idoc of type /PACG/ECM_ITYPE_ACTSUBTYPE will be generated. 

The new Subtype will be visible in Query API and e.g. on the mobile app.

The Subtype can be sent within outbound Activity idocs in field ‘SUBTYPE’ if a proper mapping is maintained in transaction /PACG/ECM_ACTMAE - Activity code mapping (see the first paragraph of this chapter).