Transferring regions from SAP to FSM

Regions should be transferred from SAP to FSM (only this way) and can originate from one of three types of SAP objects:

Work centers
Planning groups
Address regions

To regions to FSM, use one of the following sending transactions:

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38174744

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38174753

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38174770

Prerequisites

‘Region’ object added in /PACG/ECM_NOAS - No Object Assignment.

The object region field must be other than ‘No object’ in transaction . This customizing also affects how regions will be automatically determined for all activities transferred to FSM.

The same region source should be set for technicians in transaction . Notice that planning group option isn’t available but can be added with a Z-implementation (e.g. work centers defined as planning groups).

The regions must be transferred to FSM with the relevant sending transactions before they’re used by persons/activities. Technicians/activities transferred to FSM after performing the steps above will have the region determined automatically.

Transfer example

Transfer of planning groups as regions is demonstrated below. The customizing for Company 8 in transaction /PACG/ECM_SC_GR - group object for service call is set as “Planning Group”. The objects are transferred to FSM with transaction .

The ID, code, name and description of a new region can be found in an outbound idoc of type /PACG/ECM_REGION. The new region is displayed in FSM under General settings > Service regions.

Activity regions

(S4) PACG 200 SP11 Region determination is also supported by notification task-based activities (see ). Please be aware that in case we overwrite the region on the FSM side, then during the notification save the region gets the default value and the FSM input is lost. It works in the same way for service order-based activities.

After activity creation in SAP, the region value will be derived based on data in the above customizing table:

After activity creation in FSM, the region value can be either taken from an incoming idoc (if region was entered in FSM) or if there was no value specified in FSM, the region value will be determined according to the above transaction and will be sent in outgoing idoc.