General purpose | 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. | ||||
|---|---|---|---|---|---|
Sending transaction (?) | 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.
| ||||
Object assignment (?) | Object SERVICECALLSTATUS must be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company |
| Note | ||||
|---|---|---|---|---|
SERVICECALL_STATUS object:
These new classes must be set by the Setup report – customers who would like to use new solution fully, would need to change the configuration manually by themselves otherwise connector will keep running in the ‘old way’. Old version of /PACG/ECM_SCSTD transaction is maintained in /PACG/ECM_SCSTD2 - ‘Status of Service Call (Obsolete)’. Is remained as a ‘backup’ transaction and moved to /PACG/ECM_OBSOLETE package. |
...
| Note |
|---|
The activity status update will not occur when an identical status is also maintained in /PACG/ECM_SCREQ at the same time. |
| Status | ||
|---|---|---|
|
|
| Status | ||
|---|---|---|
|
...
Customizing options
Status
...
...
Customizing options
Status (together with StatProf) | System status / User Status of service orders to be mapped with FSM service call status.
| ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Priority | 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. | ||||||||||||||||||||
Serv. call status | SAP→FSM: Enter a service call status (-1, 0, 1), which should which should be set in FSM for service calls whose orders have a given SAP status (field 'Status')'Status')
The following Service Call statuses are predefined:
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 | ||||||||||||||||||||
Description |
 There’s It’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)  | ||||||||||||||||||||
Activity generation | 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:
| ||||||||||||||||||||
Allow reopening | When enabled, allow for reopening activities after reverting this system /status (user status). For instance , - if user system status E0002 I0045 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 I0046 is retrieved as the currently most important one, the related activities will become open again (see the field 'Allow reopening’ for E0002I0045, which allowed for the reopening).  
If technical completion was performed on a service Service order but then reverted, the related activities will be reopened. (In other words, reopen an activity after cancelling service order Service Order technical completion.)
ExampleTechnically complete a service order in transaction IW32. The related activity becomes closed.  Cancel the technical completion of the order. If the ‘ReopenAfterTECO’ ‘AllowReop’ field is checked for the status currently set for the service order (e.g. I0002 - ‘Released’), the closed activity will reopen.   
|
Example
#1
...
#2
First, the connector will try to find all matching system statuses in the service order in /PACG/ECM_SCSTD -Status of Service Call. In the below example, we have REL, PCNF, NMAT, PRC and SETC.
...
The settings in /PACG/ECM_SCSTD- Status of Service Call only has REL.
...
It will search for matching statuses first. If more than one system statuses are found, then it will select from priority 1 to xxx to find the highest priority where the correct cloud status will be sent.
...