Page Comparison

This is an additional configuration screen allowing the ability to limit/exclude sending different kinds of service orders based on work center (either from service order header or from service order operation). 

The customizing is created as a cluster view.

On the first level the list of companies is displayed.

The next level is divided into 3 main parts where different types of service requests can be managed:

• Active service order types - for managing exclusion of general service orders

• Active network based service types - for managing exclusion of network based service orders

• Service call active type (service notification) - for managing exclusion of service notification based service orders

Each list displays active service call types, network order types or service notification types per company. The data in this level cannot be edited and is derived from set up /PACG/ECM_SCTD. The actual work center exclusion can be defined in the lowest configuration level (for each node). One can decide about the exclusion details such as the exclusion type: header or operation and the exclusion conditions (using standard options such as single value, greater than, less than, range etc.)

Please note that the work center value should be entered as work center ID. The best practise is to choose the work center by its name/plant assignment from the search help. Then the work center Id will be automatically displayed as below:

Active Service Order Types level - examples

The work center SERV02 identified by ID 10000006 is excluded on header level and all the work centers which IDs are greater than 10000007 (SERV05, SERV06) are excluded on operation level for company 1000, service order type SM01:

The below service order of type SM01 was created for company 1000 for main work center SERV02, which is excluded on the header level. In such situation nothing is sent to FSM.

The below service order of type SM01 was created for company 1000 for main work center SERV01, which is not excluded on the header level. In such a situation the service order is sent to FSM:

Additionally 4 operations were added:

• operation 0010 which was not excluded based on condition in customizing - sent

• operation 0020 which was excluded on header level but not on operation level - sent

• operation 0030 which was not excluded based on condition in customizing - sent

• operation 0040 which was excluded based on condition in customizing - not sent

Network based service orders level - example

The work center WR001 identified by ID 10000002 is excluded on operation level (only relevant level for network orders) for company 1000 and network order type PS02:

The below network order was created for company 100, type PS02 with two operations:

Operation 0010 was created for the work center SERV01 which was not excluded - such activity has been send to FSM after activity release

Operation 0020 was created for the work center WR001 which was excluded - this operation was blocked and has not been sent to the FSM after release

Service notification based service orders - example

The work center SERV01 identified by ID 10000178 is excluded on header level (only relevant level for service notification based orders) for company 1 and notification type Y2:

The below service notification based order of type Y2 was created for company 1 for work center SERV01 which is excluded on the header level. In such situation notification based service call has not been sent to FSM.

The below service notification based order of type Y2 was created for company 1 for work center SERV02 which is not excluded on the header level. In such situation notification based service call has been sent to FSM.