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. (S4)PACG 200 SP09 You can navigate to the sending transaction using the button Send to FSM, placed on the toolbar. |
Object assignment (?) | Object SERVICECALLSTATUS must be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company |
(S4)PACG 200 SP 14 To activate new Service Call configuration, the new selection and classes must be implemented.
/PACG/ECM_CL_S_IDOC_O_SCALLSTA2
/PACG/ECM_CL_S_SEL_SCALLSTATUS2
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.
(S4)PACG 200 SP 14 After entering the /PACG/ECM_SCSTD transaction, a selection screen will appear.
The selection of the ‘Service call type’ parameter is obligatory with ‘Service order’ as the default value. (based on /PACG/ECM_SCSTD-SC_TYPE)
The parameter for filtering 'Company ID' is not obligatory.
The activity status update will not occur when an identical status is also maintained in /PACG/ECM_SCREQ at the same time.
(S4)PACG 200 SP09 To manage statuses for deprecated sales activities, use https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1880129587
(S4)PACG 200 SP 14 On the top bar, the button ‘Statuses rel. for FSM’ navigates to the transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135798.
Customizing options
Status (together with StatProf) | System status / User Status of service orders to be mapped with FSM service call status. In case of network order-based activities, network activity statuses are retrieved, not network order header statuses. |
|---|---|
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 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 |
Description | (S4)PACG 200 SP 14 Status of Service Call Descriptions are maintained in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2312536081  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)  |
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:
Prerequisite - enable field https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136054/PACG+ECM+SCTD+Service+Call+types+definition+Overview+and+Detail#SA-Fin-Confirm and disable https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136054/PACG+ECM+SCTD+Service+Call+types+definition+Overview+and+Detail#No-zero-confirmation-(formerly-%E2%80%98No-final-conf.%E2%80%99). Make sure that for status TECO in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135798 option “Send deletion” is not set. Otherwise activities won’t be automatically closed. |
Allow reopening | 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).  The functionality implemented in (S4)PACG 200 SP09 AND OLDER has been extended. Now all the statuses able to close activities are supported, not only TECO. Before the change, the status REMAINING on an order (e.g. ‘released’) must have been marked with this flag, for the related activities to be reopened after TECO reversion. Now, the entry with status TECO (or any other status causing activity closing) should be marked with this flag. For customers upgrading from older Connector versions to (S4)PACG 200 SP10, the setup program checks if there are any entries having the option ‘Reopen after TECO’ enabled for a given company. If there is at least one such entry found, the report ensures that an entry for TECO (I0045) exists and has the option ‘Allow reopening’ activated (at the same time, this option is deactivated for other statuses). This functionality applies to service order and notification-based activities. (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.) This functionality applies to standard activities, created for service orders (project activities are not yet supported). This setting must be enabled also if an operation’s control key is changed to a not FSM-relevant one and then switched back to an FSM relevant key. This will cause the related activity to be reopened. Otherwise, it’ll remain closed. ExampleTechnically 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.   |
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.
Customizing options
Status OLD LABEL SysSt (together with StatProf) | System status / User Status of service orders to be mapped with FSM service call status. In case of network order-based activities, network activity statuses are retrieved, not network order header statuses. |
|---|---|
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 OLD LABEL Cloud status | 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 |
Description | 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, user can define a translation of the status description. (check https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952620) 
|
Activity Status | (S4)PACG 200 SP 14 In new version, ‘Act Status’ and ‘AcSt w/o T’ columns are obsoleted. 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 https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135519 (filled automatically by the setup program). When activity creation is allowed for a given order status and the activity has no technician assigned, it will always get status ‘DRAFT’, regardless of the activity status entered in this customizing.
(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:
 Technical remarks:
|
Activity Status without technician assignment / SHORT Act st w/o tech | Activity status set during activity creation for activities without technician (S4)PACG 200 SP08 If no value is entered, status '9' (Draft) is used. |
Activity generation OLD LABEL S.A. generation | FSM Activity generation rules:
Make sure that for status TECO in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135798 option “Send deletion” is not set. Otherwise activities won’t be automatically closed. |
(S4)PACG 200 SP10 Allow reopening(S4)PACG 200 SP09 AND OLDER ReopenAfterTECO | (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).  The functionality implemented in (S4)PACG 200 SP09 AND OLDER has been extended. Now all the statuses able to close activities are supported, not only TECO. Before the change, the status REMAINING on an order (e.g. ‘released’) must have been marked with this flag, for the related activities to be reopened after TECO reversion. Now, the entry with status TECO (or any other status causing activity closing) should be marked with this flag. For customers upgrading from older Connector versions to (S4)PACG 200 SP10, the setup program checks if there are any entries having the option ‘Reopen after TECO’ enabled for a given company. If there is at least one such entry found, the report ensures that an entry for TECO (I0045) exists and has the option ‘Allow reopening’ activated (at the same time, this option is deactivated for other statuses). This functionality applies to service order and notification-based activities.
(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.) This functionality applies to standard activities, created for service orders (project activities are not yet supported). This setting must be enabled also if an operation’s control key is changed to a not FSM-relevant one and then switched back to an FSM relevant key. This will cause the related activity to be reopened. Otherwise, it’ll remain closed. ExampleTechnically 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.   |