/PACG/ECM_SCSTD - Status of Service Call

Define ERP-equivalents (code and description) of standard FSM service calls statuses (Ready to plan, Technically complete, Cancelled).

Map service order system/user statuses (Status) with FSM service call statuses (Serv.call stat.). Specify how service order’s system status should affect the status of the related FSM activities (Act Status). The mapping is maintained in combination with priority, Status and description for the cloud.

Transfer status descriptions to FSM using https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38174866. It’s necessary for proper service call/activity display.

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

Object SERVICECALLSTATUS must be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company

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: ,

Enter a description for status code entered in field ‘Serv. call status’. This description will be displayed in service calls in FSM. If using a language other than English (check ), make sure to maintain status translations:

Activity status to be set during activity creation/update for activities of type assignment, based on the order’s status.

The available statuses originate from transaction (filled automatically by the setup program).

(S4)PACG 200 SP10 Activity cancellation

Status ‘6 CANCELLED’ represents activity cancellation, i.e. activity status ‘closed’ and execution stage ‘cancelled’. Use it to trigger cancellation of all order activities if a given system/user status is set to the order. Unliked closed activities, cancelled activities disappear from the Planning and Dispatching Board.

Prerequisites:

• make sure that the setup program was executed after service pack upgrade

• ensure that property ‘Activity generation’ in the hereby described transaction is set to ‘Outstanding’ for the status which should trigger activity cancellation.

Activity status set during activity creation for activities without technician

FSM Activity generation rules:

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

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

• Outstanding – used to close or cancel all activities of a given order after order status change (see an example: ). Prerequisite - enable field and disable .

(s4)pacg 200 sp10

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).

(S4)PACG 200 SP09 and older

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.