Page Comparison

System status / User Status of service orders to be mapped with FSM service call status.

Within the service order, several system statuses may be active, the priority defines the importance. Service call statuses are read in the descending order.

Only applicable for sending of the correct service order and activity statuses from SAP backend to FSM.

SAP→FSM: Enter a service call status (-1, 0, 1), which should be set in FSM for service calls whose orders have a given SAP status (field 'Status')

FSM→SAP: Service calls from FSM with this status will result in setting an SAP status from field ‘Status’ to the corresponding Service Order

It’s recommend to use status ‘0' for released service calls (ready and should be planned), ‘-1’ for closed/technically completed and ‘1’ for deleted/cancelled. After sending the service call statuses and their descriptions (field 'Description’) to FSM (using the dedicated sending transaction), make sure to map them also in General settings for Planning and Dispatching:

See also: https://help.sap.com/docs/SAP_FIELD_SERVICE_MANAGEMENT/fsm_plan_dispatch/service-call-statuses.html?q=service%20call%20status, https://help.sap.com/docs/SAP_FIELD_SERVICE_MANAGEMENT/fsm_plan_dispatch/plan-dispatch-settings.html#service-call-mappings

There’s not possible to change the description of Service Call Statuses. Maintenance view allows only for translating entries.

If using a language other than English, user can define a translation of the status description. (check https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952620)

Default values for ‘Activity generation’ field are set based on entered ‘Service Call status’ – during new entry creation if Service Call status equals ‘0’ then ‘Activity generation’ is set to ‘A - Active', in remaining cases of Service Call status being either ‘1' or '-1’ - value of ‘Activity generation’ is set to ‘C - Outstanding’. 

FSM Activity generation rules:

• Active – activities will be automatically generated for orders with a given status,

• No active – activities will not be created or updated for orders with a given status,

• Outstanding – used to close or cancel all activities of a given order after order status change (see an example: Prerequisite - enable field ‘Finalize confirmations after checkout’ in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

• 2094727169/PACG+ECM_VSCTD+

• -+Service+Call+types+

• definition#Finalize-confirmations-after-checkout and disable ‘Confirmations always final’ in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

• 2094727169/PACG+ECM_VSCTD+

• -+Service+Call+types+

• definition#Confirmations-always-final .

When enabled, allow for reopening activities after reverting this system/user status. For instance, if user status E0002 is set to an order, its activities will be automatically closed (see the values in fields ‘Act status’ and ‘Activity gen.' for E0002). When the status is deactivated for the order and system status I0002 is retrieved as the currently most important one, the related activities will become open again (see the field 'Allow reopening’ for E0002, which allowed for the reopening).

If technical completion was performed on a service order but then reverted, the related activities will be reopened. (In other words, reopen an activity after cancelling service order technical completion.)

Example

Technically complete a service order in transaction IW32. The related activity becomes closed.

Cancel the technical completion of the order. If the ‘ReopenAfterTECO’ field is checked for the status currently set for the service order (e.g. I0002 - ‘Released’), the closed activity will reopen.