SAP S/4HANA on-premise PI Adaptor for Click Field Service Edge. Version 1.0. Documentation

Transcription

1 SAP S/4HANA on-premise PI Adaptor for Click Field Service Edge Version 1.0 Documentation

2 The software with this guide is furnished under a license agreement and may be used only according to the terms of that agreement. Copyright Notice Copyright ClickSoftware, Inc. All rights reserved. Trademark Click Field Service Edge is a trademark of ClickSoftware; SAP is trademarks of SAP AG No part of this publication may be copied without the express written permission of ClickSoftware, Inc. Contact Information Contact information is available from the ClickSoftware web site: For support services, mail to support@clicksoftware.com or see For general information, mail to sales@clicksoftware.com Publication Notice This guide has been carefully compiled. The information in this guide does not constitute a warranty of performance. Furthermore, ClickSoftware reserves the right to revise this publication and make changes from time to time in the content thereof, without obligation to notify any person of such revisions or changes. ClickSoftware assumes no liability for losses incurred as a result of out-of-date or incorrect information in this guide. Version Document Version Date Changes This version contains the documentation for an integration of SAP S/4HANA PI Adapter WSOPT 216_700 with Click Field Service Edge

3 SAP S/4HANA Adaptor for the Field Service Edge i Contents Contents... i Overview... 8 Handling Engineers Field Service Edge S/4HANA Mapping between FSE and S/4HANA Load Engineers/Employees from S/4HANA to FSE Relevant Persons Settings HCM Integration Download of Engineers Update of Engineer data using SAP HCM workflow events Replication of Skills and Qualifications Replication of Engineer Types (Jobs) Handling Calendars Field Service Edge S/4HANA Base Calendar Base Calendars in Time Management Transfer of Base Calendar from S/4HANA to FSE Transferring Base Calendar Mapping between FSE and S/4HANA Engineer Calendar Engineer Calendar in S/4HANA Transfer of Engineer Calendar from S/4HANA to FSE Transferring Engineer Calendar Mapping between FSE and S/4HANA Handling Engineer Availabilities Field Service Edge S/4HANA Transfer of Employee Absences or Attendances to FSE Transfer of Employee Non-Availabilities to S/4HANA Special Integration Scenarios Transfer of Non-Availability Types (Attendance / Absence Types) Entitlement procedure in S/4HANA and FSE for Absences and Attendances Mapping between FSE and S/4HANA Handling S/4HANA Service and Maintenance Orders Field Service Edge S/4HANA... 45

4 SAP S/4HANA Adaptor for the Field Service Edge ii Mapping between FSE and S/4HANA Relevant Order Operations Partner UTC-Conversion Transfer of Order Operations to FSE Transfer of Order Operations using Business Transaction Events Appointment Booking for Orders S/4HANA Standard Customizing Settings for External Scheduling Using Appointment Booking for Orders Assignment Information Mapping between FSE and S/4HANA Status Update Mapping between FSE and S/4HANA Handling Time Confirmations from Edge Mobility Field Service Edge S/4HANA Processing Time Confirmation Data in S/4HANA Mapping between FSE and S/4HANA Handling Parts Field Service Edge S/4HANA Replication of Inventory Data to FSE Processing Material Consumption Data in S/4HANA Mapping between FSE and S/4HANA Handling Assets Field Service Edge S/4HANA Transfer of Assets to FSE Customizing for Hierarchies and History of an Asset Mapping between FSE and S/4HANA Handling Technical History Field Service Edge S/4HANA Replication of the Technical History Mapping between FSE and S/4HANA Handling Measurements Field Service Edge S/4HANA Replication of the Measurement to FSE Processing inbound Measurement Documents in S/4HANA Mapping between FSE and S/4HANA... 76

5 SAP S/4HANA Adaptor for the Field Service Edge iii Handling Back Reporting Field Service Edge S/4HANA Replication of code catalogs to FSE Transfer of notifications to FSE Processing of the back report in S/4HANA Mapping between FSE and S/4HANA Technical Interface Description Installation of S/4HANA PI Adaptor Prerequisites Prerequisites for ClickSoftware Field Service Edge Prerequisites for S/4HANA Prerequisites for SAP NetWeaver PI Installation Steps Installation in S/4HANA Installation in SAP NetWeaver PI Installing the WSOPT Add-On Preparing the installation Starting the installation Preparing the System Landscape Directory Technical Systems in SLD Business Systems in SLD Configuration of SAP NetWeaver PI Integration Importing PI Design Objects into ESR Configuring the runtime environment in the Integration Directory Assigning Business Systems from the SLD Communication Channels for S/4HANA Business Systems Communication Channels for FSE Business System Configuring the integration Communication settings in S/4HANA RFC destination settings in S/4HANA Main PI RFC destination(s) Logical qrfc destination(s) Authorization for qrfc user Communication settings HCM Communication settings PM Communication settings in Field Service Edge Enabling integration with external systems Enabling Object events Configuration of outgoing messages Message Grouping and Filtering Object references for messaging Message error handling Customizing tables Authorization concept Backup procedure Changes to previous releases Update from previous adaptor patch release Upgrade from previous adaptor major release Troubleshooting

6 SAP S/4HANA Adaptor for the Field Service Edge iv Application log in S/4HANA Outgoing message processing in S/4HANA Outgoing message processing in Field Service Edge PI Runtime Workbench Resolving known pitfalls Appendix Operation and message mappings Configuration Scenario Mappings

7 SAP S/4HANA Adaptor for the Field Service Edge v List of Figures Figure 1: Overview of ERP_EngineerIntegration Figure 2: Transaction /WSOPT/C_ARBPL Figure 3: Transaction /WSOPT/HR_CUST Figure 4: Transaction /WSOPT/C_ENG_PI Figure 5: Result of transaction /WSOPT/C_ENG_PI Figure 6: Event-Infotype Operation (Customer) Overview Figure 7: Event-Infotype Operation (Customer) New entry Figure 8: Event-Infotype Operation (Customer) Overview (qualification update) Figure 9: SAP Refresh Qualifications in transaction /WSOPT/QUALIFICATION.. 19 Figure 10: FSE Dictionary table Skill displayed in Legacy Administration Tool Figure 11: SAP Change Qualifications Catalogue in transaction OOQA Figure 12: SAP Job of specific employee in transaction PPOSE Figure 13: FSE Dictionary EngineerType from the replicated SAP HCM Job displayed in Legacy Administration Tool Figure 14: S/4HANA Refresh jobs in transaction /WSOPT/JOBS Figure 15: Time_type to Status mapping in BCAL_INS_Request and BCAL_UPD_Request Figure 16: Customizing of Work Schedule Rule at HR Time Management Figure 17: Customizing of Period Work Schedule at Personnel Time Management 24 Figure 18: Customizing of Daily Work Schedule NORM Figure 19: Customizing of Daily Work Schedule GLZ Figure 20: Transaction /WSOPT/C_BCAL_PI Figure 21: Work Schedule Rule of a HR person Figure 22: HCM Master Data HCM infotype 0007 Planned working time Figure 23: HCM Master Data HCM infotype 2004 Availability Figure 24: HCM Master Data HCM infotype 2004 Availability Figure 25: Transaction /WSOPT/C_NA_PI Figure 26: Download result of Non-Availabilities Figure 27: SAP transaction SWEHR3 Workflow Linkage for Absences / Attendances Figure 28: Transaction /WSOPT/ATTABS_TYPE Figure 29: Transaction /WSOPT/ATTABS_TYPE (Output list of absence/attendance types) Figure 30: SAP Used absence type in transaction PA30 (example Object 0270 Industrial accident) Figure 31: Legacy Administrative Tool Filled dictionary NonAvailabilityType Figure 32: Transaction /WSOPT/HR_CUST to activate /WSOPT/HR_CUST- NA_STATUS Figure 33: Legacy Administrative Tool / Object Assignment Update of Non- Availability received from HCM External Comment populated Figure 34: HCM Corresponding Absence created in locked status in HCM Figure 35: Overview of ERP_OrderExIntegration Figure 36: Transaction /WSOPT/C_OPRST Figure 37: Transaction /WSOPT/PM_CUST Figure 38: Order selection screen of transaction /WSOPT/C_ORDERS Figure 39: Order list of transaction /WSOPT/C_ORDERS Figure 40: Download result of transaction /WSOPT/C_ORDERS Figure 41: Customer Products Figure 42: P&S BTE: Customer Enhancements Figure 43: IMG Navigation path to settings for External Scheduling Figure 44: Activate external scheduling for selected order types Figure 45: Settings for External Scheduling of Order Communication settings Figure 46: Set External Scheduling Parameters Figure 47: Set External Scheduling Parameter 1 example settings Figure 48: Appointment booking time slots for an order... 57

8 SAP S/4HANA Adaptor for the Field Service Edge vi Figure 49: Change order Appointment start and finish stored in operation date fields Figure 50: Assignment Object in FSE Figure 51: Time confirmation object in S/4HANA Figure 52: Assignment of engineers to storage locations Figure 53: Storage location data of a part in S/4HANA Figure 54: Assignment of components in an S/4HANA order operation Figure 55: Goods issue for two parts Figure 56: Download of material and inventory Figure 57: Example of the Implementation of SAP enhancement MCB Figure 58: Implementation of include ZXMCBU Figure 59: Configuration table /WSOPT/ASSET_CUS Figure 60: Measurement Point in S/4HANA ( transaction IK02) Figure 61: Measurement document in S/4HANA (transaction IK11) Figure 62: S/4HANA Notification (item tab) Figure 63: Catalog Selection for a catalog profile Figure 64: Assignment of catalog types to a notification type Figure 65: Download of code catalogs Figure 66: Architecture of S/4HANA PI Adapter for Field Service Edge Figure 67: Technical System listing in SLD Figure 68: Business System Wizard Figure 69: Overview of the created Business Systems in the SLD Figure 70: Overview of the imported PI Design Objects Figure 71: Assigning Business Systems from the SLD in the Integration Builder Figure 72: Creating the Sender communication channel Figure 73: Creating a receiver communication channel Figure 74: Creation of an Integrated Configuration Figure 75: Integrated Configuration Inbound Processing Figure 76: Integrated Configuration Receivers Figure 77: Integrated Configuration Receiver Interfaces Figure 78: Integrated Configuration Outbound Processing Figure 79: Model Configurator wizard for assigning Business systems and Communication channels Figure 80: Settings for Generation of Configuration Objects Figure 81: Definition of CLICK_QRFC in transaction SM Figure 82: Successful Connection Test of CLICK_QRFC Figure 83: Communication settings HCM transaction /WSOPT/HR_DEST Figure 84: Communication settings PM transaction /WSOPT/PM_DEST Figure 85: Destination settings in the Legacy Administration Tool Figure 86: Message destinations in Legacy Administration Tool Figure 87: Outgoing message configuration in the Legacy Administration Tool Figure 88: Outgoing messages in the Legacy Administration Tool Figure 89: Role Maintenance (transaction PFCG) Figure 90: User menu for role /WSOPT/WSO Figure 91: qrfc Monitor suggested selection for relevant entries Figure 92: qrfc Monitor List of hanging outbound queue entries Figure 93: qrfc Monitor Detailed queue monitor Figure 94: qrfc Monitor Detailed view for queue entries Figure 95: qrfc Monitor Detailed view for queue entries with the Activating Queue button Figure 96: qrfc Monitor Detailed view for queue entries with the Lock Queue and Lock Queue immediately button Figure 97: qrfc Monitor Lock Queue Popup Figure 98: qrfc Monitor Detailed view for queue entries with the Unlock Queue and Unlock without activating button Figure 99: qrfc Monitor Unlock Queue Popup Figure 100: PI Runtime Workbench Message Monitoring

9 SAP S/4HANA Adaptor for the Field Service Edge vii Figure 101: Message mappings in PI, part Figure 102: Message mappings in PI, part Figure 103: Message Mappings in PI, part Figure 104: Message Mappings in PI, part

10 C H A P T E R 1 Overview Ch 1 Overview 8 This document contains the description for the SAP S/4HANA on-premise adaptor interface for the Click Field Service Edge integrated via SAP Process Integration (SAP NetWeaver PI) functionality. The relevant releases are SAP S/4HANA on-premise 1610 and Field Service Edge (FSE). Required version of SAP NetWeaver PI is 7.5. The Field Service Edge and S/4HANA have different data models and describe similar entities in different ways. In each of the following chapters you can find a discussion of the different models. Possibilities to match these models according to your needs and the necessary customizing settings for Field Service Edge are described in the final section. There are five different roles involved in installing and activating this interface: IT Network Administrator: Since the interface transfers data between different systems in the network and the internet, this role needs to make sure that those systems can be accessed by each other. There is an overview in the first part of chapter 12 of the architecture and the protocols involved that will be useful for this role. The SAP certificate C_TADM5x SAP Certified Technology Associate System Administration or similar is recommended. SAP Application Expert for Plant Maintenance (PM): This document is mainly for this role. Relevant are chapters 5 to 11 and 13. The SAP certificate C_TPLM30 SAP Certified Application Associate - Enterprise Asset Management or similar is recommended. SAP Application Expert for Human Capital Management (HCM): This document is mainly for this role. Relevant are chapters 2 to 4 and 13. The SAP certificate C_THR12 SAP Certified Application Associate - SAP HCM or similar is recommended. SAP Basis Administrator: This role is responsible for creating destinations and assigning authorizations in the SAP backend system. Chapter 12 describes everything this role needs to do. The SAP certificate C_TADM5x SAP Certified Technology Associate System Administration or similar is recommended. SAP PI Administrator: All changes in SAP PI are handles by this role. Relevant chapters are 12 and 13. The SAP certificate C_PO - SAP Certified Technology Associate - Process Orchestration or similar is recommended. FSE Professional Service Expert: All changes in Field Service Edge are handles by this role. Relevant chapters are 12 and 13. The chapters 2, 3 and 4 describe the integration between Field Service Edge and SAP HCM as it is part of the S/4HANA integration. It describes how engineer data including the engineer availability can be replicated from S/4HANA to Field Service Edge. Chapter 2 explains and discusses different ways to describe your engineers and their attributes like organizational structure and skills. At the end of the section you can find the data transfer from S/4HANA to Field Service Edge and how to set up this download to Field Service Edge. Chapter 3 gives an overview of calendars in Field Service Edge and SAP HCM. In this chapter you will find which calendars will be transferred from HCM module to Field Service Edge.

11 Ch 1 Overview 9 Chapter 4 describes possibilities to maintain the availability of the engineers. It explains how to maintain this information inside S/4HANA and Field Service Edge. Three ways of maintenance of availability are possible: inside SAP HCM only, inside Field Service Edge only or a mixed mode where the general shifts and vacations are maintained inside SAP HCM but changes on a short notice can be maintained inside Field Service Edge (like an absence of an engineer on a short notice). Appointment booking can be part of S/4HANA call logging by using a service order planning process. Chapter 5 describes how to set up this function optimized for your service organization. The customizing section of this chapter explains how to match the attributes of Field Service Edge tasks and order data. Appointment booking requires a two way interface, which enables the data to be transferred in both directions: S/4HANA can request an appointment offering from Field Service Edge. New tasks (order operations in S/4HANA terminology) are transferred to Field Service Edge according to these appointments. Edge Scheduling is then responsible for scheduling the task. An update of the S/4HANA order based on status changes and assignments might be required depending on your business process. Possible scenarios are discussed in Chapter 5. In the chapters 6 11 the integration mainly for supporting the Edge Mobility integration is described. Time confirmations are discussed in chapter 6. Inventory data and material consumption are discussed in chapter 7. Chapter 8 describes the replication of assets from S/4HANA to the Field Service Edge. In addition history information can be made available to those assets as described in chapter 9. The replication of the measurement points is discussed in chapter 10 including the replication of measurement reading from the Field Service Edge to S/4HANA. Last but not least technical back reporting data can be exchanged between the two systems as described in chapter 11. On the SAP side notification is the object that hosts this data. Chapter 12 gives some general information about the S/4HANA Field Service Edge communication interface from a technical point of view. It helps the system administrator to set up the interface and explains how the system is monitored. Chapter 13 offers a troubleshooting guide, which is presented as a collection of frequent problems and their solution steps. Naming scheme Depending on the configuration context and the related software producer multiple names for the different parts of the delivery will be used throughout this whole documentation. The used naming is as follows: SAP S/4HANA PI Adaptor for Click Field Service Edge 1.0 refers to the whole adaptor product, which consists of the SAP ERP Adaptor for Service Optimization and the SAP CRM Adaptor for ClickSchedule. SAP CRM Adaptor for ClickSchedule is not used in the context of the S/4HANA Field Service Edge integration, but it is only used in the context of the pure on-premise deployment as part of the on-premise product SAP Workforce Scheduling and Optimization by ClickSoftware 2.3. Restrictions The integration of Field Service Edge into a multi-client environment is not supported by the out-of-the-box functionality. The usage of the interface in a multi-client scenario with only one Field Service Edge system is limited because Field Service Edge doesn't support a setup of multiple clients

12 Ch 1 Overview 10 in the same way as S/4HANA does. But a scenario with multiple SAP S/4HANA clients and the same number of Field Service Edge systems is supported. The settings for external scheduling in S/4HANA are only required if the appointment booking process according to the SAP standard scheduling process is needed. Customizing settings of previous releases are kept during the upgrade. It s necessary to manually adjust settings in Customer-Exits and Business-Add-Ins to the new functionality. SAP CRM Adaptor for ClickSchedule is not supported in the context of the SAP S/4HANA on-premise Field Service Edge integration. SAP S/4HANA PI Adaptor for Click Field Service Edge 1.0 is partly based of the compatibility packages for SAP S/4HANA on-premise. Please refer to SAP support note and subsequent information there.

13 Ch 2 Handling Engineers 11 C H A P T E R 2 Handling Engineers Field Service Edge S/4HANA This chapter describes how to maintain engineers and employees in SAP S/4HANA and how to map them to the structures in Field Service Edge. A suggested standard mapping can be found in the ERP_EngineerIntegration process integration scenario which is part of the Adaptor definitions for SAP NetWeaver PI. The resources inside Field Service Edge are named engineers. In the standard Field Service Edge these resources can have a number of important properties. Possible property values are maintained in the Schema Editor. In addition, other properties relevant for scheduling can be defined during the Field Service Edge implementation process. All properties can be used for defining rules and objectives for the scheduling process. These settings are only part of the Field Service Edge implementation process. S/4HANA supports multiple ways of maintaining the resources that can be dispatched. A prerequisite for the integration of Field Service Edge is that one work center represents a group of engineers that is equivalent to a district in Field Service Edge. Engineers are represented by HR master records. Each engineer is linked to exactly one work center at a time by one of the different ways supported by SAP HCM to link persons to work centers. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERP_EngineerIntegration. The scenario is just a suggestion and might be changed according to specific project requirements. All attributes for persons in SAP HCM are time dependent and can be maintained already for a point of time in the future. E.g. an address change can be entered in SAP before it becomes effective or a certain qualification expires on a certain date. In SO engineer/employee attributes are static, so the engineer/employee has a certain address (qualifications/skills are an exception, which is time dependent). For the integration this limits the possibilities of real-time updates between SAP and SO. The address change is typically updated in SO when it becomes effective and not when it is entered in SAP, so that the values in SO represent a snap-shot of the setting in SAP for a certain day. Nevertheless all updates in SAP can trigger an update in SO immediately after the change is entered in SAP. This works fine as long all changes in SAP become effective at the point in time when they are entered. In parallel the report used for the Download of Engineers (page 16) can be scheduled as job in SAP to ensure a daily update of the snapshot in SO with the valid data for this day. In this way e.g. all engineer skills are removed in SO when they expire on the SAP side. The mapping provided in the OOTB integration is also referencing time phased skills in FSE.

14 Ch 2 Handling Engineers 12 Figure 1: Overview of ERP_EngineerIntegration The mapping provided for SAP NetWeaver PI is described in detail in the table below: Field Service Edge S/4HANA Remarks Name First name and Last name Derived from SAP infotype 0001 ID Personnel No This is the SAP key. So this mapping must not be changed Region Plant Assumption is that each engineer is assigned to one relevant work center in SAP. The plant of this work center is mapped to the region ExternalRefID SAPID Unique key for the engineer. ExternalRefID must be set as object reference in FSE. The SAPID is created by concatenating the HR Prefix with the Personnel No as described on page 105. District Work Center Assumption is that each engineer is assigned to one relevant work center in SAP. Address Calendar Permanent resident Address Engineer SAPID Assumption is that the engineer/employee is starting his work from this address (SAP Infotype 0006). The content is dependent on the address type in /WSOPT/HR_CUST. Following infotype 0006 fields are mapped to engineer address fields in FSE: PSTL to Postcode, ORT01 to City, STRAS to Street, LAND1 to CountryID (mapping table in PI to derive the country name in FSE) Assumption is that for each engineer a calendar is defined. The SAPID of the engineer is also used as key for the

15 Ch 2 Handling Engineers 13 Engineer Type Job type short + object ID calendar. This setting is required for the standard calendar integration. In SAP a person can be assigned to a certain job indirectly via his position. The existence and content is dependent on the evaluation path in /WSOPT/HR_CUST. Travel Speed --- No similar functionality is available in SAP standard Active --- True for all engineers who belong to a FSE relevant work center, otherwise false. In addition to above criteria an engineer becomes active false if his Employment Status becomes different than 3 (table field P0000-STAT2). Internal --- True for all employees belonging to employee group 1, otherwise false Skills TimePhasedSkills Qualification name + object ID Qualification name + object ID Qualifications are derived from SAP infotype These are the same qualifications you can assign to a requirements profile in the order. In the standard mapping the qualification ID is used. The proficiency ID is used as the level in FSE. FSE supports only numeric values. See above plus StartTime + FinishTime Tools --- No similar functionality is available in SAP standard to assign tools to engineers that the engineer has for a longer term. Efficiency --- No similar functionality is available in SAP standard The update of engineers/employees in SO is triggered by the default implementation of enhancement spot /WSOPT/HR_ENGINEER. It's possible to replace this logic with a different implementation according to specific project needs by implementing BAdI /WSOPT/HR_ENGINEER.

16 Ch 2 Handling Engineers 14 Load Engineers/Employees from S/4HANA to FSE Relevant Persons There are the following possibilities to download (or update) engineer/employee data to FSE: Using a report for the initial download or as a scheduled job in batch. Activating a HR Workflow linkage for specific infotypes in SAP HCM. When transferring engineer data to FSE the adapter doesn t check if the engineer region or engineer district already exists in the FSE scheme. It is assumed that the values for region and district will be added with the SOAP message creating or updating engineer data in FSE. After an engineer was created by CreateResource message the adapter updates the parent child relationship of the corresponding district in FSE. An engineer can be marked relevant for FSE depending on his work center category, plant and the person responsible for the work center. Use the transaction /WSOPT/C_ARBPL to define FSE relevant work centers. All engineers who belong to these relevant work centers are replicated to FSE. Settings HCM Integration Figure 2: Transaction /WSOPT/C_ARBPL This relevance check is supported by the default implementation of enhancement spot /WSOPT/HR_ENGINEER. It's possible to replace this logic with a different implementation according to specific project needs by implementing the BAdI /WSOPT/HR_ENGINEER_RELEVANT. You can define which subtype of infotype 0006 is used as the engineer address relevant for FSE. The evaluation path defines the access to SAP HCM Organization Management. You can set up if and how position, job and organizational units are read in SAP. You can use a SAP standard evaluation path or you can define your own path in the SAP standard configuration. If you don't define a path, the integration to SAP HCM

17 Ch 2 Handling Engineers 15 Organization Management is inactive. Organizational Units are available in PI structures but OOTB not mapped to build the navigation tree in FSE. The evaluation path is used to derive the FSE Engineer Type from the Job in HCM and to list all organizational units which are above a person in the organizational structure. The setting can be maintained in transaction OOAW. The flag Read Com. Data enables or disables the usage of infotype 0105 (engineer telephone, , fax and others) in the integration. You can differentiate between scenarios in your organizational plan by using the plan version of the organizational tree. For more information on creating plan versions, see the SAP Implementation Guide (use transaction SPRO, then select SAP REFERENCE IMG) under Personnel Management Global Settings in Personnel Management Plan Version Maintenance. If the No Calendar flag is set, infotypes 0007 and 2004 will be excluded from the integration and no calendars will be passed to FSE. The flag Activate NA Status provides Non-Availability Status logic for the integration of Non-Availabilities. In this case the SAP NA information Locked / Unlocked is converted to the corresponding Non-Availability Status in FSE. Use the transaction /WSOPT/HR_CUST to change these settings. All other settings available in transaction /WSOPT/HR_CUST are not relevant for the integration into FSE. Figure 3: Transaction /WSOPT/HR_CUST Note: The evaluation path ZCLICK is not part of the delivery. Please enter the evaluation path from your local settings or leave it empty, if not necessary.

18 Download of Engineers Ch 2 Handling Engineers 16 The initial download of engineers and employees is implemented as a special ABAP/4 report that allows a flexible selection of the relevant engineers/employees. The report is named /WSOPT/C_DOWNLOAD_ENG_PI. It can be found in the ABAP Editor, transaction SE38. The report is also directly accessible with transaction /WSOPT/C_ENG_PI. It is strongly recommended to use report variants for defining this selection. The report can run online or as a background task. It is also possible to use SAP s job scheduling mechanism to run the download on a regular basis. To specify relevant engineers/employees it is mandatory to define at least one of the following parameters: The plant or an interval of plants The work center or an interval of work centers Person responsible Personnel number(s) Optional to the work center it is possible to define the person responsible or an interval of this parameter, if your individual engineers/employees are defined as work centers or people inside your SAP system. The report and its parameters are shown in Figure 4. Figure 4: Transaction /WSOPT/C_ENG_PI Figure 5: Result of transaction /WSOPT/C_ENG_PI After a new engineer was created by CreateResource message the ExecuteMultipleOperations message is passed to FSE in order to update the parent child relationship. With the same message the time zone of District is set to Greenwich

19 Ch 2 Handling Engineers 17 Standard Time. If the District time zone is different to Greenwich Standard Time the XLS based mapping has to be adjusted accordingly. This report also creates a Base Calendar if the Engineer Calendar of the engineer to be updated is referencing a not yet downloaded Base Calendar. Such created Base Calendars consist of weekly time intervals as maintained in the Period Work Schedule of the Planned Working Time. Holidays included in the Holiday Calendar will be transferred if the Holiday takes place on the day of execution. Update of Engineer data using SAP HCM workflow events The trigger for the real time update of HR data is the workflow event. Use the program Event-Infotype Operation (Customer) (transaction SWEHR3) to maintain the relevant workflow for HR object person. Figure 6: Event-Infotype Operation (Customer) Overview Push the button New entries and make the following entries: Object Type = always P (Person) for workflow events of persons Infotype (Infotype which shall trigger the engineer update procedure) Update operation (INS = insert, UPD = update and DEL = delete) Object Type (object which supports the update operation, e.g. BUS1065 means the employee object, ADDRESSEMP means address of an employee). Function module = /WSOPT/C_ENGINEER_UPDATE (this function module is called when an update of engineer/employee data shall be made in FSE)

20 Ch 2 Handling Engineers 18 Figure 7: Event-Infotype Operation (Customer) New entry It is recommended to maintain the workflow linkage for following infotypes: Infotype 0001 = Organizational Assignment Infotype 0002 = Personal Data Infotype 0006 = Addresses Infotype 0007 = Planned working time Infotype 0105 = Communication Only if the workflow linkage is maintained for a certain infotype, a change on this infotype of an engineer/employee will trigger the data update in FSE. For example, when you change the home address of an engineer/employee (infotype 0006) then an update message is sent in real time to notify FSE about the changes. Immediate updates of resource qualifications to FSE can be triggered by function module /WSOPT/C_ENGINEER_UPDATE2. When maintaining qualifications for a person via infotype 0024 (Qualification) the SAP system creates just a link to the qualification. Therefore the workflow linkage has to be created for the object Q (Qualifications) instead of P (Person). The workflow linkage for immediate qualification update has to be maintained for Object Type Q, infotype 1001 (Relationship), Subtype B032 (is fulfilled by), Update Operation INS, UPD and DEL, Activity PDSP (PD: Changes to HR Develop. Subprofile). Object type BUS7030 (Dev. Subprofile) and function module /WSOPT/C_ENGINEER_UPDATE2. Figure 8: Event-Infotype Operation (Customer) Overview (qualification update)

21 Ch 2 Handling Engineers 19 Replication of Skills and Qualifications Skills can be replicated to FSE with the report /WSOPT/DOWNLOAD_QUALIFICATION. In this case the dictionary table Skill is populated with the content of the qualification catalogue defined in SAP HCM. It s possible to define a specific root object in the configuration of the S/4HANA PI Adaptor to replicate only skills of a certain part of the hierarchy to FSE. It s as well possible to define which fields become the property name in FSE. In the standard delivery the skill name will be concatenated with name and ID e.g. French Language ( ). These setting influences as well the replication of the time phased engineer skills (infotype 0024). Skills can be updated or added. The deletion of existing skills is not supported. The replication of skills can be triggered by starting the replication report in S/4HANA manually with the transaction /WSOPT/QUALIFICATION. You can enter a qualification key to identify the root object (e.g ) as root object for the skills of the hierarchy Language Skills). Figure 9: SAP Refresh Qualifications in transaction /WSOPT/QUALIFICATION Figure 10: FSE Dictionary table Skill displayed in Legacy Administration Tool You get the catalog with the qualification keys by using the transaction OOQA and choosing View Key on. There's also an input help available. If you leave the field blank all the catalog entries will be refreshed. Figure 11: SAP Change Qualifications Catalogue in transaction OOQA If you want to replicate skills from two or more certain parts of the hierarchy you have to run the report for each root object. The report can also run on a regular basis as a batch job.

22 Ch 2 Handling Engineers 20 Replication of Engineer Types (Jobs) For the integration of SAP HCM and FSE the engineer type is mapped to the job to which the engineer/employee is linked via the assignment to a certain position. In SAP you get the job of a certain resource by using the transaction PPOSE. Figure 12: SAP Job of specific employee in transaction PPOSE The corresponding dictionary table in FSE is Engineer Type. Figure 13: FSE Dictionary EngineerType from the replicated SAP HCM Job displayed in Legacy Administration Tool The dictionary table Engineer Type can be populated by the report /WSOPT/DOWNLOAD_JOBS that allows sending a selection of jobs to the FSE. OOTB the name of the engineer type is concatenated from the name in the replication language and the SAP external key, e.g. Skilled worker ( ). Engineer types can be updated or added. The deletion of existing employee types is not supported. The replication of the employee types can be triggered by starting the replication report in SAP manually. Use the transaction /WSOPT/JOBS to change these settings. It s as well possible to run the report on a regular basis as a batch job. To specify relevant jobs you can define at least one of the following parameters: The SAP Object ID or an interval The SAP Object abbreviation or an interval The SAP Object name or an interval An input help is available for each parameter. Figure 14: S/4HANA Refresh jobs in transaction /WSOPT/JOBS

23 Ch 3 Handling Calendars 21 C H A P T E R 3 Handling Calendars Field Service Edge S/4HANA Base Calendar In Field Service Edge calendars can be defined on various levels. You can define standard weeks; maintain holidays and the calendar on a day-by-day basis per engineer. An engineer can have working time, non-working time and optional time. In SAP HCM you can define a calendar in different ways, depending on the point of view from the work center or from the HR time. Similar to the definition in Edge Scheduling the calendar can be specified for a standard week, for holidays and at the daily level. The S/4HANA Adaptor for Field Service Edge supports SAP HCM standard calendars defined in Personnel Time Management in the SAP system. The SAP S/4HANA PI Adaptor for Click Field Service Edge supports two different types of calendars: Base calendar defined for a group of engineers Engineer calendar defined for one engineer This type of calendar will include the holiday calendar of the Personnel Area and the Period Work Schedule. The holiday calendar is used to define the yearly non-working days in the Edge Scheduling calendar. The Period Work Schedule is used to define the weekly working intervals of an Edge Scheduling calendar. The calendar will just cover a Period work schedule for one week shifts. A Period work schedule, which extends over several weeks, e.g. a 3-week rotating shift containing three different shifts, is not supported. SAP S/4HANA PI Adaptor for Click Field Service Edge supports following structures, which contain the base calendar properties: BASECAL BASECALWEEK BASECALYEAR The structure BASECAL contains following properties of the base calendar: CALENDAR (Name of the base calendar) START (Date of a present day) FINISH (Date of a present day plus one year) The identifier of the field: BASECAL-CALENDAR is a combination of four fields. This combination determines the name of a base calendar in Edge Scheduling:

24 Ch 3 Handling Calendars 22 Employee Subgroup Grouping for Work Schedules Holiday Calendar ID Personnel Subarea Grouping for Work Schedules Work Schedule Rule The structure BASECALWEEK includes the time intervals for each day of the week from daily work schedule. This structure supports following properties: CALENDAR (Name of calendar) WEEKDAY (Day of the week) TPROG (Key of Daily work schedule, e.g. NORM, GLZ, ) TIME_TYPE (Type of time of the time interval) BEGIN_TIME (Begin of time interval) END_TIME (End of time interval) The TIME_TYPE is an interface specific structure field which represents a special time interval. The purpose of this structure field is to predefine flexible time intervals. For example, the time interval CO1 shall be working time and the time interval BNO shall be optional working time in the corresponding Edge Scheduling base calendar. PFI and PFL are mutually exclusive. The meaning of TIME_TYPE is as follows: PFI PFL NOR TIME_TYPE Description Planned working time minus fix time Planned working time minus flex time Normal working time CO1 Core time 1 CO2 Core time 2 BNO ANO UND BC1 AC1 BTC Meaning of time_type Before Normal working time After Normal working time Undefined (no time settings for this day of the week) After Core Time 1 begin and before normal time begin After normal time end until core time 2 end Time between core time 1 end and core time 2 end In the standard mapping the following combinations are assigned. In Edge Scheduling calendars there are four statuses for a certain time interval: Working Non-Working Optional Undefined

25 Ch 3 Handling Calendars 23 Figure 15: Time_type to Status mapping in BCAL_INS_Request and BCAL_UPD_Request The structure BASECALYEAR includes the intervals for holidays. This structure supports following properties: CALENDAR (Name of calendar) START (Date of a present-day) FINISH (Date of a present-day plus one year) TXT_LONG (Long text description of holiday calendar) Base Calendars in Time Management In SAP HCM standard customizing you can define your base calendar properties. In the SAP Implementation Guide (use transaction SPRO, then select SAP REFERENCE IMG) under Time Management Work Schedules Work Schedule Rules and Work Schedules Set Work Schedule Rules and Work Schedules you can define Work Schedule Rule which will represent the base calendar for FSE. The combination of the first four fields is the identifier of a base calendar: Employee subgroup grouping for Work Schedules e.g. 1 Holiday Calendar ID e.g. 08 Personnel subarea grouping e.g. 01 and Work schedule rule e.g. GLZ. The name of this base calendar would be 10801GLZ.

26 Ch 3 Handling Calendars 24 Figure 16: Customizing of Work Schedule Rule at HR Time Management The Period Work Schedule defines the sequence of Daily Work Schedule on any workday. The columns 01 till 07 represent the week days Monday till Sunday. On each of these workdays you can assign a Daily Work Schedule which defines the working hours of the employee. Period work schedules are defined in the SAP Implementation Guide (use transaction SPRO, then select SAP REFERENCE IMG) under Time Management Work Schedules Period Work Schedules Define Period Work Schedules and select an entry. Figure 17: Customizing of Period Work Schedule at Personnel Time Management In the Daily Work Schedule you can define the daily working hours for each workday. In SAP daily work schedules are defined in the SAP Implementation Guide (use transaction SPRO, then select SAP REFERENCE IMG) under Time Management Work Schedules Daily Work Schedules Define Daily Work Schedules and select an entry and then select menu Goto Details.

27 Ch 3 Handling Calendars 25 Figure 18: Customizing of Daily Work Schedule NORM SAP S/4HANA PI Adaptor for Click Field Service Edge supports the download of Fixed working hours and Flextime. The content of the structure BASECALWEEK will be different for Fixed working hours and Flextime. The following table displays the content of BASECALWEEK when using fixed working hours: CALENDAR WEEK- DAY TPROG TIME TYPE BEGIN TIME END TIME 10801NORM Monday NORM PFI 08:00:00 16:30: NORM Tuesday NORM PFI 08:00:00 16:30:00

28 Ch 3 Handling Calendars NORM Saturday UND 10801NORM Sunday UND Content of basecalweek when using Fixed working hours The next screen displays possible Flextimes of the daily work schedule GLZ. Figure 19: Customizing of Daily Work Schedule GLZ The following table shows the content of the structure BASECALWEEK of the daily work schedule GLZ with Flextime : CALENDAR WEEKDAY TPROG TIME_TYPE BEGIN_TIME END_TIME 10801GLZ Monday GLZ PFL 08:00:00 18:00: GLZ Monday GLZ NOR 08:30:00 17:30: GLZ Monday GLZ CO1 09:00:00 11:30: GLZ Monday GLZ CO2 14:00:00 16:00: GLZ Monday GLZ BNO 08:00:00 08:30: GLZ Monday GLZ ANO 17:30:00 18:00:00

29 Ch 3 Handling Calendars GLZ Monday GLZ BC1 08:30:00 09:00: GLZ Monday GLZ AC2 16:00:00 17:30: GLZ Monday GLZ BTC 11:30:00 14:00: GLZ Tuesday GLZ PFL GLZ Saturday UND 10801GLZ Sunday UND Content of BASECALWEEK when using Flextime Transfer of Base Calendar from S/4HANA to FSE The download of base calendar is implemented as a special ABAP/4 report. The report /WSOPT/C_DOWNLOAD_BASECAL_PI offers a number of selections to download the calendars to FSE (alternatively, you can use transaction /WSOPT/C_BCAL_PI which provides the same functionality). Before executing the download, a query for the existence of the calendar is sent to FSE to avoid creating the same calendar twice. You can specify the following parameters for the calendar download: The Employee Subgroup Grouping for Work Schedules Holiday Calendar ID Personnel Subarea Grouping for Work Schedules Work Schedule Rule Begin date of calendar you want to download End date of calendar you want to download As described in chapter 2 Handling Engineers base calendars will also be created when the engineer download report is executed and the base calendar of an engineer calendar doesn t exist in FSE. In such case the base calendar will only consist of weekly time intervals as defined in the work schedule rule in SAP HR time management. Yearly time intervals cannot be selected in SAP HR time management by the engineer download report because the Begin and End dates cannot be set in that report. The Begin and End date of the selection screen are used to derive the holidays of the Holiday calendar of the work schedule rule. These holidays are created as yearly time intervals with status non-working in the base calendar. The default value of both date fields is set to the current date. Figure 20: Transaction /WSOPT/C_BCAL_PI

30 Ch 3 Handling Calendars 28 Transferring Base Calendar Due to the fact that two different calendar types are needed, two different messages Create and Update must be provided in PI. An additional Get message will look for the existence of a calendar in FSE. When a base calendar does not exist in FSE a Create message is sent to create the base calendar in FSE. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERP_BaseCalenderIntegration. The scenario is just a suggestion and might be changed according to specific project requirements. Field Service Edge Name YearlyInterval WeeklyInterval S/4HANA Combination of the four fields: Employee Subgroup Grouping for Work Schedules Holiday Calendar ID Personnel Subarea Grouping for Work Schedules Work Schedule Rule Non Working time derived from the Holiday Calendar Working and optional working time of the first week from the selected time interval. The status of the weekly time interval is set based on the Time Type, e.g. BNO, NOR. Engineer Calendar In SAP HCM module you can assign the Work Schedule Rule to a HR person. This assignment will be done using the HR infotype 0007 Planned working time. You can use each Work Schedule Rule which is valid for the employee subgroup and personnel area of a certain personnel master. This assignment determines which base calendar is valid for a certain HR person. Use program Maintain HR Master Data (transaction PA30) for the changes.

31 Ch 3 Handling Calendars 29 Figure 21: Work Schedule Rule of a HR person Figure 22 shows the assignment of a Work Schedule Rule in the infotype 0007 (Planned working time) of a HR person. Figure 22: HCM Master Data HCM infotype 0007 Planned working time In addition, each engineer will have his own calendar in Field Scheduling, which will refer to the base calendar. His individual optional working days, which are maintained in SAP HR module as an infotype 2004 (Availability), are used to define his individual yearly optional working days in his Field Scheduling calendar. S/4HANA Adaptor for Field Service Edge supports following structures, which contain individual engineer calendar properties: ENGICAL

32 Ch 3 Handling Calendars 30 ENGICALYEAR The structure ENGICAL contains the properties of the calendars: CALENDAR (Personnel number of the engineer) START (Date of a present day) FINISH (Date of a present day plus one year) BASECALENDAR (Name of the base calendar) The structure ENGICALYEAR contains the properties of the individual calendars: CALENDAR (Personnel number of the engineer) START (Date of a current day) FINISH (Date of a current day plus one year) SUBTY (Subtype of infotype 2004) Engineer Calendar in S/4HANA The calendar of an engineer is determined by the Planned working time which is shared by a number of engineers and his individual working time which is maintained as infotype 2004 (Availability) in his HR master data. The provided default PI mapping uses subtype 01 as optional work time and subtype 02 as non-working hours. Figure 23: HCM Master Data HCM infotype 2004 Availability

33 Ch 3 Handling Calendars 31 Figure 24: HCM Master Data HCM infotype 2004 Availability SAP S/4HANA PI Adaptor for Click Field Service Edge supports the availability of individual times maintained as a fixed time or from a Daily work schedule. Transfer of Engineer Calendar from S/4HANA to FSE The transfer of engineer calendars to FSE is implemented as part of the engineer update logic. Each time a relevant engineer record is created or modified the related engineer calendar record is created as well. The engineer calendar is only updated if the infotype triggering the workflow begins with 2. If the flag No Calendar is set in the HCM configuration (transaction /WSOPT/HR_CUST) the engineer calendars are not transferred to FSE. A more specialized update logic may be implemented in the customer environment using Business Add-Ins or SAP HCM workflow events. Transferring Engineer Calendar A GET message is used to query FSE if the specified calendar already exists. The creation logic will ensure that an existing calendar will be updated and not created twice. When an engineer calendar does not exist yet in FSE, a Create message is sent to create the engineer calendar in FSE. When a record of infotype 2004 (Availability) is added for a certain engineer an Update message is sent to Field Scheduling to update the specified engineer calendar. Existing time intervals will be overwritten and new time intervals will be added when updating the engineer calendar. When an engineer becomes not relevant for FSE (e.g. he loses the allocation to a FSE relevant work center), then an Update message is sent to remove the link of the

34 Ch 3 Handling Calendars 32 engineer calendar from the engineer data. In that case, an additional Delete message is send to FSE which triggers a deletion of the engineer calendar. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERP_EngineerCalendarIntegration. The scenario is just a suggestion and might be changed according to specific project requirements. Field Service Edge S/4HANA Remarks Name Engineer SAPID See pages 12 and 105. BaseCalendar Name of base calendar as derived from engineer infotype See description of base calendar above. YearlyInterval Start-Finish of infotype 2004 Time intervals are created in status Optional Work or Non Work.

35 Ch 4 Handling Engineer Availabilities 33 C H A P T E R 4 Handling Engineer Availabilities Field Service Edge In Field Service Edge you can create non-availability assignments. In FSE terminology, a non-availability is a designated time when an employee is not available to be scheduled. The properties of a non-availability assignment which are relevant for the SAP HCM integration are: Engineer (ExternalRefID of the engineer/employee) Start date and time (Start date and time of the non-availability) Finish date and time (End date and time of the non-availability) NonAvailabilityType (Description and ID of the subtype of an absence or attendance) NonAvailabilityStatus (Tentative, Declined, Accepted) ExternalComment (Error description raised when creating an absence or attendance record in SAP HCM) Key (FSE object key) Note: For the Field Service Edge, the assignment properties NonAvailabilityStatus and ExternalComment need to be created as UDPs using the Schema Editor. S/4HANA The availability of an employee can be maintained via the standard infotype 2001 Absence and infotype 2002 Attendance in HCM. The absence/attendance types with specified start and end time of an absence/attendance are the corresponding data for creating a non-availability assignment in FSE. There are rules defined in HCM for processing absences and attendances. For instance, quota days must be defined for certain absence or attendance types, such as leave day or trainings. If a resource doesn t have enough quota days left for an absence or attendance, the record can only be created as a locked absence or attendance. The manager responsible is able to increase the quota days and unlock the corresponding absence or attendance. During a payroll period for a personal area some infotypes are not allowed to be changed or created for the duration of this period and for the month before this period. Only future absences or attendances can be created as unlocked records. Absences or attendances for the locked period and month before that period can only be created as locked absences or attendances. After the payroll run, all locked absences can be unlocked. When changing an absence or attendance in HCM, the system deletes the existing record and creates a new one with the new start and finish interval and allocates a new document number to the new record. The document number is the unique identifier of

36 Ch 4 Handling Engineer Availabilities 34 an absence or attendance (it is mapped to the assignment property ExternalRefID as its identifier). Changes of absence or attendance types are not supported in HCM, instead the old absence or attendance needs to be deleted and a new absence or attendance with the new absence or attendance type has to be created. Absences and attendances are split automatically in HCM when the intervals of the absence or attendance are overlapping. For instance the resource is on leave for 10 days (starting on 7 th of January 2013 and ending on 18 th of January 2013) and becomes sick during the first week of his vacation. The sickness starts on 9 th January and ends on 15 th January. In such case HCM splits the leave absence in two record parts: The first leave absence will start on 7 th of January and ends on 8 th of January. The second leave absence will start on 16 th of January and ends on 18 th of January. It is not allowed to end a leave on a non-working day according to the planned working time of the HCM resource calendar. Such an absence cannot be created as unlocked or locked absence in HCM. Note: The adaptor doesn t manipulate assignment UDPs and therefore if they are maintained in FSE they won t be deleted or changed by the adaptor. Following structure is used for getting information about engineer availabilities: ATTABS (ATTendances / ABSences of an engineer/employee) The structure ATTABS contains absence or attendance data of engineers/employees. The properties of absences and attendances are: START (Start date and time of an absence) FINISH (End date and time of an absence) TIMEZONE (FSE time zone) NAME_LIST (Name of the engineer/employee) EMPLOYEENUMBER (Personnel number of the engineer/employee) DOCUMENTNUMBER (Document number for time data) RECTYPE (Subtype number) RECTYPE_TEXT (Subtype name) SAPID (Unique identifier of the assigned resource) LOCKINDICATOR (Lock Indicator for HR Master Data Record) NA_STATUS (NonAvailability Status) NA_COMMENT (Error Description raised in HCM) O_KEY (FSE Key) Transfer of Employee Absences or Attendances to FSE The SAP S/4HANA PI Adaptor for Click Field Service Edge supports two options for transferring SAP absences or attendances to FSE. The first option is implemented as

37 Ch 4 Handling Engineer Availabilities 35 the ABAP/4 report /WSOPT/C_NON_AVAILIBILITY_PI. The second option is for transferring absences and attendances using the SAP HCM workflow. The report /WSOPT/C_NON_AVAILIBILITY_PI offers a number of selections to download the non-availabilities to SO. It is recommended to define report variants for this selection. This report can run online or as a background task. You can specify the following parameters for the attendance / absence download: The plant or an interval of plants The work center or an interval of work centers The person responsible of a work center or an interval of persons responsible The personnel number of an employee or an interval of personnel numbers The attendance / absence type or an interval of attendance / absence types Begin date of the time interval for the selection of attendances / absences you want to download End date of the time interval for the selection of attendances / absences you want to download The transaction /WSOPT/C_NA_PI can also be used to execute the report to download engineer absences. Make required entries and execute this transaction. Figure 25: Transaction /WSOPT/C_NA_PI Figure 26: Download result of Non-Availabilities The report will only create a non-availability if the resource exists in FSE and if the nonavailability doesn t exist in FSE. If there are non-availabilities with the ExternalRefID in FSE which don t exist in SAP HCM, they will get deleted. Non-availabilities without an ExternalRefID will be ignored. Customers who don t want to transfer non-availabilities

38 Ch 4 Handling Engineer Availabilities 36 created in FSE to SAP HCM can also use the download report to update or create nonavailabilities from SAP HCM absences or attendances. The second possibility to transfer non-availability data to FSE is to use the SAP HCM workflow linkage. You can activate the workflow linkage with the transaction SWEHR3, as described in section Update of Engineer data using SAP HCM workflow events on page 17 and shown in Figure 6. The infotype 2001 Absence and infotype 2002 Attendance are supported. The function module, which has to be executed when the specified infotype is maintained for an engineer/employee is /WSOPT/C_ATTABS_UPDATE. To enable processing of locked and unlocked absences and attendances, please define the following Update Operations in workflow linkage: APC, APP, DEL, INS, REQ, RQC and UPD. Figure 27: SAP transaction SWEHR3 Workflow Linkage for Absences / Attendances Transfer of Employee Non-Availabilities to S/4HANA It is also possible to maintain non-availabilities directly in Field Scheduling and to transfer their data to SAP HCM. If the UDP Status was configured in the Schema Editor for Business Object Assignment the non-availability can be created in FSE with status Tentative and with a non-availability type existing in HCM. After the corresponding absence or attendance was processed in HCM, the status will be changed by the adaptor either to Declined or to Accepted. If for any reason the absence or attendance could not be processed in HCM, the status will remain Tentative in FSE. The status Accepted will be set if the absence or attendance could be created in unlocked status in HCM. If the absence or attendance could not be processed as unlocked but it was processed as locked, because of missing quota days or any other reason, the status in FSE will be set to Declined. In addition to the status, an External Comment will be passed to FSE to indicate the reason for the locked record. If for any reason the absence or attendance could not be processed at all (even not as a locked record), the status will remain Tentative in FSE. The External Comment property will be populated with the error raised while the adaptor tried to process the absence or attendance. The errors raised during creation of an absence in HCM are equal to those which are raised when a dialog user creates an absence or attendance in HCM. In HCM, the start and end time of an absence or attendance is dependent on the nonavailability type. For instance the non-availability type Illness with certificate (0200) can only be created for full days. For that reason, a non-availability of type Illness with certificate (0200) created in FSE with a start time 08:00 AM and finish time 04:00 PM will be created as a full-day absence in HCM. The update from HCM will change the start and finish time in FSE after the absence was created in HCM.

39 Ch 4 Handling Engineer Availabilities 37 The adaptor doesn t support following changes to non-availabilities in FSE: the resource of an existing non-availability, the non-availability type or Non-availability status from Tentative to Declined or to Accepted. Status changes will only be triggered by the absence or attendance processing in HCM. Note: Only non-availabilities with a non-availability type existing in SAP HCM can be processed in HCM. The adaptor doesn t support a request for leave instead it creates an absence or attendance using the non-availability data sent by FSE. In HCM, there is no infotype available to store such request for leave in HCM. Special Integration Scenarios In order to ensure consistency between SAP and SO, it is not allowed to delete a nonavailability in FSE which was not yet updated from SAP. The non-availability is updated in FSE as soon as the status changes from Tentative to Accepted or Declined and the ExternalRefID is set. If the corresponding absence or attendance record could not be created in HCM, the non-availability record in SO will remain in status Tentative without populated ExternalRefID but with an External Comment indicating why the absence or attendance could not be created (error messages raised during creation process in HCM). The following is an explanation of what will happen in the integration when the nonavailability was deleted before its update from HCM: Action in FSE 1. Create non-availability in FSE. 2. Delete the nonavailability in FSE before it was updated with ExternalRefID and status from HCM. Result A NonAvailabilityCreate message is sent from SO to PI/HCM. Absence is created in HCM and an UpdateAssignment message is triggered to SO. FSE doesn t trigger a delete message to SAP, which is correct. Assignment Update and Delete messages should only be passed for nonavailabilities with an ExternalRefID. The UpdateAssignment message from HCM will fail (triggered as a result of absence create event step 1 message contains the FSE key of the assignment) because the non-availability was already deleted. The response from FSE is: The specified Assignment object was not found in database. This error response raises an error in the SAP queue. The private queue of the person is in status sysfail which avoids a restart of the queue and further updates related to this person. To resolve this issue, the private queue of the resource has to be deleted in S/4HANA in order to process further updates for the resource. The following table describes how or when an absence split is triggered in HCM.

40 Ch 4 Handling Engineer Availabilities 38 Action in FSE 1. Create a leave non-availability in FSE (06 th to 17 th June). 2. The non-availability is updated with ExternalRefID and status. 3. Create a sickness nonavailability in FSE (14 th to 15 th June). 4. The adaptor creates two new leave non-availability with a new ExternalRefID, start and finish and creates a third leave non-availability with the corresponding start and finish dates. The adaptor updates the sickness non-availability with ExternalRefID and status. Result A NonAvailabilityCreate message is sent from FSE to S/4HANA. The absence is created in HCM and an UpdateAssignment message is triggered to FSE. In HCM, SAP splits the leave absence into two absences: th to 13 th June th to 17 th June Both absences will get a new identifier in HCM (ExternalRefID). A third absence for sickness is created in HCM. In the Edge Scheduling Gantt the original leave non-availability and three new nonavailabilities are displayed. In order to keep both system (S74HANA and FSE) in synch the download report for absences has to be executed. The report will delete the original created long leave and will keep the tree absences on the gantt. If you delete the sickness non-availability in FSE before it was updated with the ExternalRefID, you will have three queue entries for this person in SAP queue. One will have the status sysfail. The sysfail queue has to be deleted and the other queues have to be activated in order to update the non-availability in FSE. The result will be zero to two split leave non-availabilities (in fact two leave non-availabilities with a gap in-between). Note: Once the non-availability was created in FSE the user has to wait until the nonavailability was updated from HCM in order to keep both systems in synch. The adaptor gets the same error or warning messages like a dialog user while processing incoming messages from FSE. Those error or warning messages are passed to the nonavailability in FSE and stored in the External Comment field. It is recommended to test the behavior of processing absences or attendances in HCM before triggering the process from FSE. In such case the user will be aware of any warnings and errors. Transfer of Non-Availability Types (Attendance / Absence Types) In SAP HCM each form of attendance (infotype 2002) and absence (infotype 2001) is represented by an attendance/absence type, which describes the attendance or absence in more detail. The ABAP/4 report /WSOPT/DOWNLOAD_ATTABS_TYPE allows replicating the SO dictionary values of non-availability types based on the SAP configuration. The report can be also triggered in SAP manually by using the transaction /WSOPT/ATTABS_TYPE. You can specify the following parameters for the attendance / absence download:

41 Ch 4 Handling Engineer Availabilities 39 Personnel Subarea Grouping for Work Schedules Language Key The attendance / absence type or an interval of attendance / absence types An input help is available. It s also possible to run the report on a regular basis as a batch job. For more information on maintaining personnel subarea grouping for absence and attendance types, see the SAP Implementation Guide (use transaction SPRO, then select SAP REFERENCE IMG) under Time Management Work Schedules Personal Subarea Groupings Group Personnel Subareas for the Work Schedule. Figure 28: Transaction /WSOPT/ATTABS_TYPE Figure 29: Transaction /WSOPT/ATTABS_TYPE (Output list of absence/attendance types) OOTB box the naming for attendance / absence types is concatenated from the text of the absence or attendance type in the replication language and the SAP external key (sub type of the absence or attendance), e.g. Industrial accident (0270).

42 Ch 4 Handling Engineer Availabilities 40 Figure 30: SAP Used absence type in transaction PA30 (example Object 0270 Industrial accident) When creating non-availabilities in FSE, the user will only use NonAvailablityTypes which ere replicated from HCM to FSE. In other case the absence or attendance cannot be processed in HCM. Figure 31 shows an example with highlighted NonAvailabilityType Industrial accident (0270). Figure 31: Legacy Administrative Tool Filled dictionary NonAvailabilityType The items of the dictionary table NonAvailabilityType in FSE can be updated or added. The deletion of existing non-availability types is not supported.

43 Ch 4 Handling Engineer Availabilities 41 Entitlement procedure in S/4HANA and FSE for Absences and Attendances Absences or attendances that require an entitlement in HCM are processed as locked absences or attendances by the PI adaptor. It is recommended to configure a workflow procedure in HCM for approval of locked absence and attendance records. The non-availability status property is used to indicate whether an absence or attendance could be processed in HCM. A second assignment property called ExternalComment is used to store the error description in case the absence or attendance could not be created as an unlocked absence or attendance in HCM. The error description is raised during the creation procedure in HCM and passed to FSE. It is also possible that an error is raised while processing a locked absence or attendance in HCM. For instance this error could be raised by a configuration or by technical reasons and cannot be influenced by the adaptor. In order to use this functionality in FSE the UDPs NonAvailabilityStatus has to be created for the assignment object. The UDP for the Business Object Assignment has to be created in the Schema Editor of FSE. The property ExternalComment already exists in the OOTB FSE database. By using the Generic Status Flow feature in FSE a default status can be forced on new non-availabilities. Following configuration steps have to be performed in FSE: 1. In FSE Schema Editor: add the dictionary called NonAvailabilityStatus. 2. For the object Assignment: add a new UDP called NonAvailabilityStatus which references to the newly created dictionary NonAvailabilityStatus. 3. In Legacy Administrative Tool add three instances for the new NonAvailabilityStatus dictionary: Tentative, Accepted and Declined. 4. Using the Generic Status Flow feature, configure the default value for the new Assignment property to be Tentative. In HCM an absence or attendance can be created in locked or unlocked status. Absences or attendances which are created in locked status will go through the entitlement procedure and have to be approved to become status unlocked. In order to support the status transfer from FSE to SAP HCM and vice versa the Activate NA Status flag needs to be activated in transaction /WSOPT/HR_CUST. Figure 32: Transaction /WSOPT/HR_CUST to activate /WSOPT/HR_CUST-NA_STATUS

44 Ch 4 Handling Engineer Availabilities 42 The last prerequisite for the entitlement procedure to be supported is to set up the field mapping as described in the next section Mapping between SO and ERP. When creating a non-availability in FSE the default status Tentative will be allocated to it. In HCM the adaptor processes the incoming absence or attendance in the following sequence: 1. A new absence or attendance will be created in unlocked status. 2. When the absence or attendance was processed successfully in HCM, the adaptor updates the non-availability in FSE with the status Accepted It also updates the property ExternalRefID which is the identifier of an absence or attendance in HCM and the start and finish date and times. The time interval will be updated as well in FSE because some absence and attendance types are defined a full-day absences or attendances and cannot be created to start at 08:00 am and end at 4 pm. Therefore it is required to update the time according to the absence or attendance in HCM. 3. If for any reason the creation fails in HCM, the adaptor creates the absence or attendance as a locked record. The status on the non-availability in FSE will be set to Declined and the External Comment property will be updated with the error message received while creating unlocked absence or attendance in the first step. Figure 33: Legacy Administrative Tool / Object Assignment Update of Non-Availability received from HCM External Comment populated

45 Ch 4 Handling Engineer Availabilities 43 Figure 34: HCM Corresponding Absence created in locked status in HCM In addition, the Adaptor supports the creation of Non-availabilities in status Declined or Accepted in FSE. If you create a non-availability in status Declined a locked Absence or Attendance will be created in HCM. If you create a non-availability in status Accepted the same steps will be performed by the Adaptor as described in case of Tentative non-availabilities. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERP_NonAvailabilityIntegration. The scenario is just a suggestion and might be changed according to specific project requirements. Field Service Edge Engineer ExternalRefID S/4HANA Engineer SAPID Start Start date and time of Infotype record 2001 or 2002 Finish End date and time of Infotype record 2001 or 2002 NonAvailabilityType ExternalComment NonAvailability ExternalRefID NonAvailabilityStatus RECTYPE_TEXT and RECTYPE in brackets NA_COMMENT If the creation of Absence or Attendance failed in status unlock otherwise empty. Property is mapped, but disabled OOTB. The mapping node needs to be enabled in the ESR to activate the processing of this node. Attabs Document Number NA_STATUS: mapped, but disabled OOTB. The mapping node needs to be enabled in the ESR to activate the processing of this node. Note: Before activating the mapping in ESR you need to activate the Stets feature in S/4HANA using Transaction /WSOPT/HR_CUST.

46 Ch 4 Handling Engineer Availabilities 44 The overview below shows the mapping that is provided in the scenario ERP_InboundNonAvailabilityIntegration. Field Service Edge Engineer ExternalRefID Engineer ID ExternalRefID NonAvailabilityStatus NonAvailabilityType Assignment Key ExternalComment S/4HANA Engineer SAPID Employeenumber Attabs Document Number NA_STATUS: mapped, but not active in PI RECTYPE I_KEY NA_COMMENT: mapped, but not active in PI

47 Ch 5 Handling S/4HANA Service and Maintenance Orders 45 C H A P T E R 5 Handling S/4HANA Service and Maintenance Orders Field Service Edge S/4HANA Tasks are the central object for scheduling in Edge Scheduling and Edge Mobility. The corresponding object to a task is a PM or CS order operation. Important fields from a FSE perspective are maintained in SAP in the order header other fields are maintained on the operation level. Tools and material are assigned to the operation. SAP S/4HANA PI Adaptor for Click Field Service Edge supports processing of service and maintenance orders. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERP_OrderExIntegration. The scenario is just one option and might be changed according to specific project requirements. Figure 35: Overview of ERP_OrderExIntegration The mapping provided for SAP NetWeaver PI is described in detail in the table below:

48 Ch 5 Handling S/4HANA Service and Maintenance Orders 46 Field Service Edge S/4HANA Remarks CallID Order Number The order number is used to make the assignment information available in SAP. Changes here cause further issues for the display of assignments. Number Operation + Sub Operation Number Both numbers from SAP are concatenated, e.g. operation 0010 becomes number in FSE, Sub Operation 0010 of operation 0010 becomes In FSE the leading zeros are truncated, so that the stored number becomes Please don't change this mapping. It's also used to make the assignment information available in SAP. Changes here will cause further issues for the display of assignments ExternalRefID SAPID Unique key for task created from the PM Prefix + internal order number + internal operation number. ExternalRefID must be set as object reference in FSE. This SAPID does not have a type flag. Details of the format are described on page 105. Priority Priority In FSE you must use a value between Assumption is that no other values in SAP are allowed. Status Task User Status The status flow in FSE is an extremely important part of the overall configuration. The OOTB system statuses in SAP were not designed to describe the typically sophisticated status flow defined in FSE. Therefore the assumption is that a user status flow in SAP is configured to map with the status flow in FSE. In SAP the status is a four char field. The status of a removed operation will be updated to DELETED in FSE. This mapping can be changed in SAP NetWeaver PI. In the FSE you can schedule a purge agent to remove them automatically. Beside of this a task list filter can be set which will cover the DELETED tasks. Calendar --- No mapping for a customer specific calendar is provided out of the box

49 Ch 5 Handling S/4HANA Service and Maintenance Orders 47 Field Service Edge S/4HANA Remarks Task Type Order Type The order type in SAP describes the type of the work in a good way. However a limitation is that after the order is created the type can't be changed anymore. Alternative implementations are e.g. to use the maintenance activity type. This field on the header level of the order can be changed in case the type of the work is different then entered at the first time. Another alternative can be to look for a SAP field on operation and not on order header level if different operations of the same order consist of different task types (as defined in the FSE implementation). E.g. the operation control key or the standard text key could then be a possible field for the mapping. Duration Duration SAP makes a difference between the amount of work and the duration. A work of two hours that is performed by a crew of two engineers in parallel requires a duration of one hour. Time dependencies Relationships In SAP Start to Start, Start to Finish, Finish to Start and Finish to Finish Relationships are supported. Engineer dependencies SAP does not have the concept to define non exact dependencies (at least, between, at most). The standard mapping assumes always exact dependencies. Time Dependencies between tasks in FSE are only created when relationships are defined in SAP. --- SAP does not have a comparable concept. No mapping is provided out of the box Critical --- There is no special concept in SAP to define a task as critical. However this value might be derived e.g. from the priority or task type. Early start Basic Start Start as defined in SAP on the order header. Late Start --- No similar field available in SAP. Due Date Basic Finish Finish as defined in SAP on the order header.

50 Ch 5 Handling S/4HANA Service and Maintenance Orders 48 Field Service Edge S/4HANA Remarks Open Date Created On Created on date and time in SAP. Contact Date --- A possible mapping depends on the mobile solution in place. When Edge Mobility is in use there is no need to derive this field from SAP. Confirmation Date --- A possible mapping depends on the mobile solution in place. When Edge Mobility is in use there is no need to derive this field from SAP. Appointment Start Earliest scheduled start Appointment Finish Latest scheduled start Customer Name of configured partner The field is available only if the appointment was pulled from FSE (SAP operations status DSEX). The field is available only if the appointment was pulled from FSE (SAP operations status DSEX). The mapping assumes that you have configured a partner role. Region Plant Plant of the work center of the SAP order operation. District Work center Work center of the SAP order operation. Address Address Address data is determined in SAP with the following sequence: 1. Order address 2. Object address 3. Customer address The first address in this sequence is the address that is transferred to FSE as the task address. Contract Type --- There are a number of options for a project specific solution. The type of a contract in the way this information might be relevant for FSE can be defined in SAP in several different ways. So no standard mapping can be provided. Contact Name Name1 The mapping assumes that you have configured a partner role for the customer contact. Contact Phone Tel_number1 The mapping assumes that you have configured a partner role for the customer contact.

51 Ch 5 Handling S/4HANA Service and Maintenance Orders 49 Field Service Edge S/4HANA Remarks CountryID Country SAP typically uses the international identifiers like DE for Germany or GB for Great Britain whereas FSE uses the country names. Therefore there is a mapping between the two types defined in PI. Not all countries are mapped. In case further countries are needed in a specific scenario they have to be added. Preferred Engineer Partner The mapping assumes that you have configured a partner role for the preferred engineers. Required Engineer Partner The mapping assumes that you have configured a partner role for the required engineers. Number of Required Engineers Required Crew size Number of Capacities --- The value is mapped to the constant 1. The number of required capacities for the operation. IsCrewTask --- The PI Adaptor assumes that a crew is required if number of capacities in SAP is > 1 and sets this field to True. Default is False. Required Skills 1 Requirements In SAP it's possible to link a requirement profile to the order operation. All qualifications included in the requirement profile assigned to the operation at the basic start date are sent to FSE. In the standard mapping the qualification ID is used. The proficiency ID is used as the level in FSE. FSE supports only numeric values. Required Skills In SAP there is out of the box no logic to differentiate between required skills 1 and 2. All requirements are mapped to Required Skill1. No mapping is provided OOTB for Required Skills 2. Required Tools Name Engineer Operation Category Number Parts and If the tool in FSE is a resource, which can be used to assign tasks to it, an order operation in SAP should be created to define this need. Longitude --- Assumption is that the longitude of the task is determined in FSE based on the address information.

52 Ch 5 Handling S/4HANA Service and Maintenance Orders 50 Field Service Edge S/4HANA Remarks Latitude --- Assumption is that the latitude of the task is determined in FSE based on the address information. ReturnSchedulingError --- Mapped to constant value false. Relevant Order Operations All timestamps are sent to FSE without seconds. In the following you will find some more detailed information for the table above. It's possible to specify the relevance of order operations for FSE in dependency of its criteria, which consist of order type, plant and control key. Use the transaction /WSOPT/C_OPRST to define FSE relevant order operations. Partner UTC-Conversion Figure 36: Transaction /WSOPT/C_OPRST Note: The order and operation properties must match all three properties of the criteria to be marked as relevant for transfer to FSE. Consider to configure orders/operations of mixed type as well, if they are required. In addition the adaptor transfers only order operations of released orders. Order operations of an order in system status CRTD Created are not considered as relevant for FSE. In SAP it is possible to maintain different partner functions and to assign different partners to them on the order header level. This can be used to define the customer contact, the preferred and the required engineer for FSE. Figure 37 shows the definition of such contacts with the transaction /WSOPT/PM_CUST. The referenced partner functions are defined with transaction VOP2. SAP's assumption for time zone support for orders is that all order related time information is stored in the system time of the SAP server. A time conversion is supported by S/4HANA. The PI Adaptor can convert all order related time information into UTC. This time zone conversion is only done when the check box UTC in the settings as shown in Figure 37 is checked.

53 Ch 5 Handling S/4HANA Service and Maintenance Orders 51 Figure 37: Transaction /WSOPT/PM_CUST Transfer of Order Operations to FSE The initial download for order operations is implemented as a special ABAP/4 report. The report /WSOPT/C_ORDER_DOWNLOAD offers a standard selection screen for selecting FSE relevant orders. When you execute the transaction /WSOPT/C_ORDERS for the order download a selection screen will appear. Figure 38: Order selection screen of transaction /WSOPT/C_ORDERS Fill required entries and execute this transaction. From the list of orders you can choose which of them should be sent to FSE.

54 Ch 5 Handling S/4HANA Service and Maintenance Orders 52 Figure 39: Order list of transaction /WSOPT/C_ORDERS When chosen orders do not yet exist in FSE they will be created in FSE, otherwise they will be updated. Figure 40: Download result of transaction /WSOPT/C_ORDERS Transfer of Order Operations using Business Transaction Events Alternatively to the initial transfer of orders to FSE using the report introduced above, an on-change transfer of order operations triggered via Business Transaction Events (BTEs) is possible. The implementation of this mechanism needs the registration of the following BTE function modules for the selected events. Event PM is triggered each time an order is created (transaction IW31) or modified (transaction IW32). Event PM is triggered each time an order confirmation is saved through transaction IW41 or a mobile client. Follow the customizing steps using the events and modules shown in the following table. Event Event triggered at BTE function module PM Update of Order /WSOPT/C_ORDER_UPDATE_BTE PM Update of Confirmation /WSOPT/C_CONFI_UPDATE_BTE If you need additional asset information on the FSE server it s possible to configure another function module to include asset and notification details in the replication process. In chapter 8, Handling Assets, you can find further details. Configuration steps: 1. Define product Define a Product to which the function modules can be assigned: Use transaction FIBF and select menu Settings Products...of a customer.

55 Ch 5 Handling S/4HANA Service and Maintenance Orders 53 Figure 41: Customer Products Note: Mark the product as active, otherwise the function modules assigned to this product are not triggered. 2. Register P/S modules Register function modules for the events according to your requirements: Use transaction FIBF and select menu Settings P/S Modules...of a customer. Figure 42: P&S BTE: Customer Enhancements Appointment Booking for Orders S/4HANA Standard Customizing Settings for External Scheduling For external scheduling the SAP system offers a CS-SDL interface to perform interactive scheduling for service orders. S/4HANA customizing settings are required if you want to use appointment booking. Customizing settings must be done in the SAP Implementation Guide under: Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Orders Scheduling External Scheduling.

56 Ch 5 Handling S/4HANA Service and Maintenance Orders 54 Figure 43: IMG Navigation path to settings for External Scheduling Following settings must be performed: 1. Activating external scheduling per service order type After executing customizing transaction Define for Each Order Type the system offers a list of existing orders. Select that order type you want to schedule using an external scheduling system and mark it with an X. Figure 44: Activate external scheduling for selected order types 2. Configuring communication The SAP S/4HANA PI Adaptor for Click Field Service Edge offers special function modules, which define interface parameters. Following remote function modules are supported:

57 Ch 5 Handling S/4HANA Service and Maintenance Orders 55 Function module /WSOPT/C_ORDER_SCHED_APPOINT /WSOPT/C_SCHED_DIALOG Description Allows selecting a suitable date from proposed dates delivered by FSE. Allows using a dialog for appointment booking, where suitable appointments can be selected. The SAP system offers predefined values, which specify the time when a particular remote function module should be called. The predefined values are: A: During scheduling proposal D: For scheduling in dialog with an external system The settings are only required if appointment booking in SAP is needed. Figure 45: Settings for External Scheduling of Order Communication settings Note: Please do not use the RFC destination NONE for external scheduling. For more details about usage of NONE RFC destinations please refer to the SAP note Set external Scheduling Parameters The standard interface for external scheduling (CS_SDL interface) provides a definition of scheduling parameters. There are three different types of parameters which can be used for external scheduling. You can use them for example to define FSE profiles and FSE policies and make that information available in SAP order processing. Execute the action link of Set external Scheduling Parameters in the IMG. The pop-up dialog will ask you to choose between three parameter types. The usage of each parameter set is shown in the table below.

58 Ch 5 Handling S/4HANA Service and Maintenance Orders 56 Figure 46: Set External Scheduling Parameters Open each of the scheduling parameter options with a double click on one of the parameters or use the button Choose. In every dialog you can define a key and a description of the parameter. If no parameters are defined, the adaptor will use the value 'DEF' for profile and policy. The parameters are limited to have a format of 4 upper case only letters. The profile and policy keys must be defined in FSE accordingly if the SAP customizing settings are in use. External Scheduling Parameter Field in Appointment Booking Window Usage in FSE Task Key of parameter1 Profile Appointment booking profile Key of parameter2 Policy Schedule policy Key of parameter3 Not used Not used An exemplary definition of the appointment booking profiles is shown in Figure 47. Figure 47: Set External Scheduling Parameter 1 example settings In the example above following Appointment Booking Profiles have to be configured in Legacy Administration Tool: AM AMPM DEF PM

59 Ch 5 Handling S/4HANA Service and Maintenance Orders 57 Note: Enabling of external scheduling together with automatic scheduling may lead to unexpected results in the default configuration. In this configuration the creation or modification of an assignment in Edge Scheduling will trigger the external scheduling dialog in SAP in a background task, which leads to short dump. A customer-specific solution must be implemented if both functionalities are to be used. Using Appointment Booking for Orders When creating (transaction IW31) or changing (transaction IW32) an order, the dispatcher selects the scheduling icon in the top of the order screen. An appearing popup window (Figure 48) will offer available appointment slots queried from Edge Scheduling, where the dispatcher may select one of them before saving the service order finally. Figure 48: Appointment booking time slots for an order The selected appointment will be stored in the operation date fields. For FSE only the early start and late start of the order are relevant for the appointment. Early and late finish is derived by adding the duration to the start date and time. Figure 49: Change order Appointment start and finish stored in operation date fields

60 Ch 5 Handling S/4HANA Service and Maintenance Orders 58 Assignment Information Depending on the integration scenario it might be required to make the engineer assignments available in S/4HANA. This information may be passed to S/4HANA every time an assignment is created or modified in Edge Scheduling and the SAP order is updated based on the assignment details. The integration scenario ERP_InboundAssignmentIntegration supports the update of the constraints of the SAP order operation by updating the time restriction and the employee of the order operation with the actual data of the assignment. The function module /WSOPT/C_ORDER_ASSIGNMENT_UPD is called from SAP NetWeaver PI to update the order operation with this data. It's not possible to store assignments to more than one engineer (crews or teams) as this is not supported by the order implementation by SAP. Assumption is that the engineer ID is a valid personnel number in SAP. Note: Please be aware that the number of assignment updates triggered, especially by the background optimizer, can reach very high volumes and may impact your overall performance. Please consider sending only a carefully selected set of assignments to S/4HANA. Mapping between FSE and S/4HANA The overview below shows the mappings that are provided in the scenarios. The scenarios are just a suggestion and might be changed according to specific project requirements. The field mappings are referencing fields, which were already introduced in the context of orders and engineers. For completeness the relevant fields as used in the scenario ERP_InboundAssignmentIntegration are shown below: Field Service Edge S/4HANA Remarks Engineer ID Personnel No. References the engineer properties as created during Engineer Name Engineer First and engineer upload. Last Name Engineer ExternalRefID Engineer SAPID Assignment Key Assignment Key Generated by FSE. Task CallID Order number. References the order and operation properties as created Task Number Operation + Order during task upload. sub operation number. Task Status Start, Finish Status name Restrictions: StartPoint and End --- Update Type Mapped to one of I, D or U depending on action Insert, Delete or Update. The integration scenario ERP_AssignmentIntegration implements the query of available assignments in FSE from S/4HANA. By default this integration scenario is not used and is provided only to ease customer specific customizations.

61 Ch 5 Handling S/4HANA Service and Maintenance Orders 59 Field Service Edge S/4HANA Remarks CallID (LowBound Value and HighBound Value) Assignment ExternalRefID Order No. Order No. Used to query the assignments by CallID. Not used in standard SAP. Assignment Key --- Generated by FSE. Not used in standard SAP. Start, Finish Engineer ExternalRefID Start, End Personnel No. Comment Comments Not used in standard SAP. Assignment Location Location Not used in standard SAP. Status Optional: Status Not used in standard SAP. Get Assignments --- Notifies FSE to attach the Assignment information in query result. Set to true per default. Status Update The order update process handles the task status update in SAP order operations by FSE tasks. Updates can potentially be triggered for configured task statuses in FSE and should become visible in SAP. The integration for status updates from FSE to SAP is delivered in the scenario ERP_InboundOrderIntegration. Assumption is that a user status scheme for order operations is configured in SAP. The scenario assumes that the 4-character status name in SAP is in line with the status name in FSE. Note: Usually only one System (either S/4HANA or FSE) should be able to set a certain status. So a task group should trigger the sending of status updates in FSE only for status changes that are really caused by a status change in FSE and not by a status change caused by a task update message coming in from S/4HANA. Please be aware that the number of status changes triggered, especially by the background optimizer, can reach very high volumes and may impact your overall performance. Please consider synchronizing only status changes that are really needed in S/4HANA. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERP_InboundOrderIntegration. The scenario is just a suggestion and might be changed according to specific project requirements. Field Service Edge Task Status Name Task CallID Task ExternalRefID S/4HANA 4-character name of operation user status. SAP Order number SAPID

62 Ch 6 Handling Time Confirmations from Edge Mobility 60 C H A P T E R 6 Handling Time Confirmations from Edge Mobility Field Service Edge A time confirmation in Edge Mobility is processed as an update to the two objects assignment and task. The time confirmation includes the actual assignment start and finish, the engineer identifier and the task status. After creating a time confirmation in Edge Mobility and passing it to FSE the corresponding assignment and task objects are updated. The assignment start and finish properties may be changed as well as the task status to indicate the completion of the task. In order to trigger only one message to SAP including both changes (assignment and task update) a task status indicating a time confirmation was set is needed. A change to this status is used as a trigger to pass the time confirmation from Edge Mobility to S/4HANA. S/4HANA Figure 50: Assignment Object in FSE The corresponding S/4HANA object to an Edge Mobility time confirmation is a Time Confirmation of an order operation in S/4HANA.

63 Ch 6 Handling Time Confirmations from Edge Mobility 61 Figure 51: Time confirmation object in S/4HANA Processing Time Confirmation Data in S/4HANA The integration scenario ERPMobile supports the creation of a time confirmation with the actual data of the assignment. The function module /WSOPT/C_PI_TIMECONF_INS is called from SAP NetWeaver PI, which will use the BAdI /WSOPT/TIMECONFIRMATION to create the queue entry with function module /WSOPT/C_TIMECONF_CREATE_I. This module will transform the data from FSE into S/4HANA time confirmation data and it will create the time confirmation if necessary. Mapping between FSE and S/4HANA The overview below shows the mapping that is provided in the scenario ERPMobile. The scenario is just one option and might be changed according to specific project requirements. The mapping provided for SAP NetWeaver PI is described in detail in the table below: Field Service Edge S/4HANA (Time Confirmation Field) Remarks Task ExternalRefID Order Number Operation Unique key of the task. Details of the format are described on page 105. Order number and operation number are derived from the SAPID of the task. Not used in FSE Confirmation The confirmation number is automatically set by SAP. Not available in FSE Confirmation Counter The confirmation counter is calculated based on the number of engineers including the list of assigned engineers sent by FSE. If the message contains two assigned engineers (two engineer SAPIDs) then two time confirmations will be created. The time confirmation for the first SAPID will have the counter equal 1 and the second time

64 Ch 6 Handling Time Confirmations from Edge Mobility 62 Field Service Edge S/4HANA (Time Confirmation Field) Remarks confirmation for the second SAPID will have a counter equal 2. Not used from FSE Work Center If the District property of the engineer is not empty and contains a valid value, the Work Center will be set to the District. Otherwise the Work center of the engineer as set in SAP is used. Not used from FSE Plant Plant of the engineer work center. Engineer ExternalRefID Personnel number ExternalRefID is a unique key for the engineer, which references the engineer property as created during engineer upload. It is used to derive a valid personnel number in SAP. Not used in FSE Wage Type Wage Type is not used by the standard adaptor. Not used in FSE Actual Work Actual Work is calculated based on the assignment start date/time and assignment finish date/time properties. The unit is set to minutes. Not used in FSE Activity Type Activity Type is taken from the corresponding operation Not used in FSE Posting date Posting date is automatically set by SAP. Not used in FSE Final Confirmation Final confirmation flag is activated for the time confirmation of the last SAPID of the assignment message. Not used in FSE No Remaining work No Remaining work flag is automatically set by SAP, because remaining work is initial. Not used in FSE Acctg. Indicator Accounting Indicator is not used by the standard adaptor. Not used in FSE Clear open Res. Clear open Reservation flag is not used by the standard adaptor. Not used in FSE Remaining Work Remaining Work flag is not used by the standard adaptor. Assignment Start Assignment Finish Work Starts on Date Work Starts on Time Work Ends on Date Work Ends on Time The assignment date and time property is used to set the Work Starts on date and time in the time confirmation object. The assignment date and time property is used to set the Work Ends on date and time in the time confirmation object. Not used in FSE Actual Duration Actual Duration is calculated based on the assignment start date/time and

65 Ch 6 Handling Time Confirmations from Edge Mobility 63 Field Service Edge S/4HANA (Time Confirmation Field) Remarks assignment finish date/time properties. The unit is set to minutes. Not used in FSE Forecast End Forecast End date and time are not used by the standard adaptor. Not used in FSE Reason Reason Code is not used by the standard adaptor. Not used in FSE Confirmation text Confirmation text (40 chars) is not used by the standard adaptor. Not used in FSE Long text exists Long text exists flag is not used by the standard adaptor.

66 Ch 7 Handling Parts 64 C H A P T E R 7 Handling Parts Field Service Edge S/4HANA Part objects are stored in the dictionary tables PartsType, PartsStock, PartsInStock and PartsUsed in the FSE database. PartsType defines the parts. PartsStock defines a stock that can contain different PartsTypes. PartsInStock is the definition of the parts that are stocked in a certain PartsStock. PartsUsed is a database table linked to a task that defines parts reservation and later on parts consumption in FSE. In S/4HANA parts are described by the material master. Parts can be stocked in different ways. One option is to define storage locations in SAP for each SAP Plant (mapped in the FSE S/4HANA integration as region). Assumption is that the stock of each engineer is identified as a certain storage location. To define the linkage between an engineer and his parts as identified by the storage location a special configuration table is provided by the adaptor in S/4HANA. Figure 52: Assignment of engineers to storage locations

67 Ch 7 Handling Parts 65 Figure 53: Storage location data of a part in S/4HANA For each storage location and each material the unrestricted available quantity is defined as shown in Figure 53. In S/4HANA the required components can be assigned to each S/4HANA order operation. This may be stock components, which the engineer carries (e.g. in his van) and other components which are send to the customer beforehand from a central warehouse or are even produced or bought for a specific service job.

68 Ch 7 Handling Parts 66 Figure 54: Assignment of components in an S/4HANA order operation After a part was used in S/4HANA a goods issue is posted. This can be done with or without a reference to a reservation. If no reservation number is passed from Field Service Edge, the reservation will be determined in S/4HANA if there is one for the issued part. If no reservation was made beforehand the goods issue is posted without a reference to a reservation. Figure 55: Goods issue for two parts A goods issue in S/4HANA refers only to the order header and not to the order operation. Replication of Inventory Data to FSE Report /WSOPT/DOWNLOAD_MATERIAL, which is also available as transaction /WSOPT/C_MATERIAL, can be used to trigger the initial download of all parts

69 Ch 7 Handling Parts 67 belonging to selected storage locations as defined in the configuration table mentioned before. PartsType, PartsStock and PartsInStock are updated by this download. Figure 56: Download of material and inventory The on-going update of the engineer stock can be triggered by using SAP enhancement MCB This enhancement can be activated via transaction CMOD. Figure 57: Example of the Implementation of SAP enhancement MCB10001 Include /WSOPT/ZXMCBU01 is provided to be included in the enhancement function module EXIT_SAPLMCB1_001. Figure 58: Implementation of include ZXMCBU01 With each change of the unrestricted stock an update of the resource is triggered. All messages regarding the update process are stored in the application log for object /WSOPT/. The messages related to parts are stored under sub object MATERIAL. The planning is available in the current integration scenario as described in chapter 5, Handling S/4HANA Service and Maintenance Orders. Out of the box there is currently no update to PartsUsed when orders are send to FSE. For enhancing the mapping the structure /WSOPT/C_PI_COMPONENT in the order operation should be mapped to the PartsUsed structure in FSE.

70 Ch 7 Handling Parts 68 The assignment of the engineer to the PartsStock can be currently done manually in FSE by adding PartsStock to the engineer form. As an alternative the structure /WSOPT/C_PI_ENGINEER can be extended with the additional fields. The extension makes it necessary to populate the fields in the provided enhancement spot and to map the fields properly in PI. Processing Material Consumption Data in S/4HANA The integration scenario ERPMobile supports the creation of goods issues with the actual data of PartUsed. The function module /WSOPT/C_PI_MATCON_INS is called from SAP NetWeaver PI, which will use the BAdI /WSOPT/MATERIALCON to create the queue entry with function module /WSOPT/C_MATCON_CREATE_I. This module will transform the data from FSE into S/4HANA goods issue and it will create the goods issue if necessary. Mapping between FSE and S/4HANA The report /WSOPT/DOWNLOAD_MATERIAL creates entries in FSE dictionary table PartType. The dictionary table PartsStock defines the locations where parts are stocked. The PartsStock can be assigned to an engineer. In database table PartsInStock is defined which PartsTypes are stocked in which quantity and in which PartsStock. A record in PartsUsed can be either already created when an order operation is replicated to FSE or when the engineer enters the parts consumption in Edge Mobility. Field Service Edge S/4HANA Remarks ExternalRefID Material SAPID SAP unique key for a material created from concatenation of S/4HANA SAPID prefix + M + material number. ExternalRefID must be set as object reference in FSE. Name Quantity Unit Description Material Number Base Unit of measure Material Description In parallel the inventory is stored in FSE table PartsInStock. Field Service Edge S/4HANA Remarks ExternalRefID Material SAPID Unique key for a material. PartType Description Quantity Unit Material Number Material Description Base Unit of measure PartsStock Plant and storage location Quantity Unrestricted Stock of the storage location The two four digit fields in SAP are concatenated into one field

71 Ch 7 Handling Parts 69 PartsUsed hold the parts planned and/or used for a specific task in FSE. Field Service Edge S/4HANA Remarks ExternalRefID Material SAPID Unique key for a material PartType Description Material Number Material Description QuantityPlanned Requirement quantity The requirement quantity is defined in SAP on the component allocation screen of the SAP S/4HANA order Reservation Number QuantityUsed Reservation, Reservation item nr. Issued Quantity In SAP both fields are concatenated. Quantity Unit Base Unit of measure If left empty in the SAP update the Base Unit of measure is assumed Dictionary table PartsStock is populated automatically with all selected storage locations. Field Service Edge S/4HANA Remarks Name Plant and storage location The two four digit fields in SAP are concatenated into one field

72 Ch 8 Handling Assets 70 C H A P T E R 8 Handling Assets Field Service Edge S/4HANA All technical objects in Field Service Edge are described as assets. Tasks can point to a list of assets to describe the objects that should be maintained during this task. In S/4HANA assets are described by the Functional Locations and pieces of equipment. The business object Functional Location is an organizational unit that structures the maintenance objects of a company according to functional, process-related or spatial criteria. A functional location represents the place at which a maintenance task is to be performed. The business object Equipment is an individual physical object that is to be maintained independently. It can be installed in a technical system or part of a technical system. A functional location can have a superior functional location. Equipment items can be part of a superior equipment items or can be installed at a functional location. In this way a hierarchy of these objects can be defined. Transfer of Assets to FSE Since assets are linked to orders, they are transferred together with measurement points, notifications and orders respectively including the technical history. To enable the transfer of assets, the function module /WSOPT/C_ORDER_UPDATE_BTE, which handles the transfer for basic orders and was described in section Transfer of Order Operations using Business Transaction Events of chapter 5, has to be replaced with the function module /WSOPT/C_ASSET_UPDATE_BTE, which transfers orders including measurement points, assets, notifications and orders respectively their technical history. Since equipment is always part of a functional location, it will be preferred over its functional location for the transfer. Customizing for Hierarchies and History of an Asset In configuration table /WSOPT/ASSET_CUS it s possible to define if object hierarchies of functional locations and/or pieces of equipment are transferred or not. If the object hierarchy flag is enabled, the asset tree referenced by the order header and the notification header are transferred together with their successors. In addition to the hierarchy flag the number of days in the past, for which notifications and orders are replicated as part of the object history can be specified. To disable the replication, set the number of days to an empty value (SPACE).

73 Ch 8 Handling Assets 71 Figure 59: Configuration table /WSOPT/ASSET_CUS Note: These settings can lead to very large number of objects, which are transferred for a single task, in case an object with a large hierarchy is the reference of a certain order. So please ensure that according to your business process the data volume remains acceptable. Mapping between FSE and S/4HANA Field Service Edge S/4HANA Remarks AssetName AssetID OperationalStatus NextMaintenanceDate Short text Equipment or Functional Location Number Not mapped Not mapped ExternalRefID Asset SAPID S/4HANA unique key for an asset created from concatenation of PM SAPID prefix, type flag and item number. Type flags: E for equipments; F for functional locations. ExternalRefID must be set as object reference in FSE. Technical Identifier Technical identification number Category AssetType Region District Construction Type Address Object Type E for Equipment; F for Functional Location Planning Plant Maintenance Work Center Construction Type Object Address AssetList List of Functional Locations/Equipment that have the actual object as the superior object Only for equipments Multi-Value used for Asset Hierarchy AssetIDs of Functional Locations or Equipments When passing the order (order operations) to FSE the adaptor collects all functional locations or

74 Ch 8 Handling Assets 72 Field Service Edge S/4HANA Remarks equipments to FSE which are installed underneath of the order reference object. It doesn t collect superior functional locations or equipments. It ignores the functional location if an equipment is also referenced. History MeasurementPoints Link to the objects of the technical history (see Chapter 9) List of the Measurement points (see Chapter 10) Multi-Value Multi-Value

75 Ch 9 Handling Technical History 73 C H A P T E R 9 Handling Technical History Field Service Edge S/4HANA In the Field Service Edge the table Technical History is provided to store the history information for assets. The history of each technical object in S/4HANA can consist of many elements (notifications, installation history, meter and counter readings, orders etc.). The basic structure /WSOPT/ASSET_HISTORY which will already record order details of historic orders is delivered by the Add-On. It s possible to enhance this structure according to specific project needs. The history can refer to functional locations and/or pieces of equipment. As assets can be linked to orders respectively notifications and notifications are always related to an order, the history entry for an order is preferred if both (order history and notification history) are present. Replication of the Technical History The replication of historic information is triggered by the update of assets (see Transfer of Assets to FSE in chapter 8). In a configuration table of the adapter the volume of the history can be restricted by the time horizon. If the horizon is defined with 0 days no history is replicated. In configuration table /WSOPT/ASSET_CUS you define for how many days in the past notifications and orders should be replicated as part of the object history. To disable the replication, use 0 for the number of days. Depending on the asset object (Equipment or Functional Location) the Technical History is updated using FunclocUpdate.xsl or EquipmentUpdate.xsl as part of Edge Mobility Archive. Only those notifications or service orders are considered as historical objects which were completed. Orders or notifications in status Released or Open are not considered as historical objects. The days set in the configuration table are compared with the creation date of the order or notification. For instance, if you define 10 days in the past for orders and notifications then only completed orders and completed notifications will be considered as historical documents which were created within last 10 days.

76 Ch 9 Handling Technical History 74 Mapping between FSE and S/4HANA Field Service Edge S/4HANA Remarks ExternalRefID Asset history SAPID S/4HANA unique key for an asset created from concatenation of PM SAPID prefix, type flag and item number. Type flags: O for orders, N for notifications. ExternalRefID must be set as object reference in FSE. ReferenceDate Description Reference Date of Order or Notification Short Text of Order or Notification

77 Ch 10 Handling Measurements 75 C H A P T E R 10 Handling Measurements Field Service Edge S/4HANA In Field Service Edge the table MeasurementPoint is provided to store the measurement points. Readings with reference to a measurement point are stored in the table MeasurementDocument. Measurement points and counters are made available per technical object. Trigger to update the related counters and measurement points is the replication of the functional location or piece of equipment itself. The definition of the measurement points is part of S/4HANA Plant Maintenance functionality. The IS-U specific functionality for readings and measurements is not part of the integration. Figure 60: Measurement Point in S/4HANA ( transaction IK02) A measurement document can be created for a measurement point. If the measurement point is a counter the new reading has to be equal to or higher than the last reading. If the counter counts backwards the reading has to be equal or lower.

78 Ch 10 Handling Measurements 76 Figure 61: Measurement document in S/4HANA (transaction IK11) Replication of the Measurement to FSE The replication of historic information into FSE is triggered by the update of assets (see chapter 8, Handling Assets). Processing inbound Measurement Documents in S/4HANA The integration scenario ERP_InboundIntegration supports the creation of measurement documents in S/4HANA. If enabled for the TaskUpdate, the function module /WSOPT/C_PI_MEASDOC_INS is called from SAP NetWeaver PI, which uses the BAdI /WSOPT/MEASUREMENTDOCUMENT to create the queue entry with function /WSOPT/C_MEASDOC_CREATE_I. This module transforms the data from FSE and creates the measurement document in S/4HANA. Assumption is that all meter readings are transferred in the default unit of the measurement point. Mapping between FSE and S/4HANA Measurement Points are replicated from S/4HANA to FSE. Please see the following tables for the mapping between fields in FSE and in S/4HANA. Filed Service Edge S/4HANA Remarks ExternalRefID Measurement Point SAPID S/4HANA unique key for a measurement point SAPID prefix + P + measurement point number. ExternalRefID must be set as object reference in FSE.

79 Ch 10 Handling Measurements 77 MeasurementPointType Description Unit Characteristic Description Unit Expected Low Value Last reading Only when measurement point is a normal counter Expected High Value Last reading Only when measurement point is a counter counting backwards Measurement Document Measurement Position Not mapped Position Measurement Point Types are created on the fly when measurement points are replicated to FSE. Field Service Edge S/4HANA Remarks Name Characteristic Measurement Documents are replicated from FSE to S/4HANA Field Service Edge S/4HANA Remarks Reading Reading -- Reading_Timestamp -- Unit -- Short Text

80 Ch 11 Handling Back Reporting 78 C H A P T E R 11 Handling Back Reporting Field Service Edge S/4HANA In FSE the object BackReporting is defined to capture the technical back reporting entered in Edge Mobility. A BackReporting is created when in S/4HANA an order operation relevant for FSE is replicated and a notification is directly or via the object list linked to this order. The technical details of the engineer s back report can be stored in S/4HANA in notifications. Each notification may consist of multiple object part items, causes, tasks and activities. To log the details of the back report new notification items can be added to a notification. For each item multiple damage causes can be added. Activities describe the technical activities performed by the engineer. Notification tasks can be used to trigger follow up work. Figure 62: S/4HANA Notification (item tab) Each aspect can consist of a textual description and a two-tier hierarchy structure to describe the entry. The structure consists of a code group and a code. Depending on the catalog profile the notification is assigned to only certain code groups are valid for the notification. Depending on the catalog type the catalog is used for the description of a cause, a task or their activities in the assembly or damage description of the item.

81 Ch 11 Handling Back Reporting 79 Figure 63: Catalog Selection for a catalog profile The catalog profile is determined at creation time of the notification in S/4HANA, which uses a special search sequence to find the correct catalog profile: 1. Piece of equipment 2. Construction type of piece of equipment 3. Functional Location 4. Construction Type of functional location 5. Notification type For each notification type in S/4HANA the catalog types used can be specified and grouped by their purpose. Figure 64: Assignment of catalog types to a notification type Replication of code catalogs to FSE Report /WSOPT/C_DOWNLOAD_CATALOGUE, which is also available as transaction /WSOPT/C_CATALOG, can be used to trigger the download of all catalogs into FSE, which are created as dictionary entries.

82 Ch 11 Handling Back Reporting 80 The Report creates the entries in the dictionary tables BackReportingType, CatalogProfile and the selected code catalog tables. Out of the box the FSE database is only delivered with the dictionary structures for the code catalogs CodingGroup and CodingCode. It s possible to add further dictionaries with the same structure to make the additional catalogs available in the FSE database. The report assumes the following dictionary names: ActivityGroup, ActivityCode CauseGroup, CauseCode DamageGroup, DamageCode ObjectPartGroup, ObjectPartCode TaskGroup, TaskCode All group catalogs share the same structure and properties: Field Name Type Information Key Key Key of this object Revision Long Internal revision number Name String Length: 64 Description String Length: 1024 ParentCatalogProfile Key To object CatalogProfile All code catalogs share the same base fields (Key, Revision, Name and Description), which are defined equivalently to the fields for group catalogs, and an additional key to the parent structure, which is as follows: Dictionary Field Name Type Information ActivityCode ParentActivityGroup Key To object ActivityGroup CauseCode ParentCauseGroup Key To object CauseGroup DamageCode ParentDamageGroup Key To object DamageGroup ObjectPartCode ParentObjectPartGroup Key To object ObjectPartGroup TaskCode ParentTaskGroup Key To object TaskGroup The report offers switches to enable these additional dictionaries during transfer. The report does not check for the existence of the underlying tables in the FSE database, so they should only be enabled after the equivalent data structures were created on the FSE server.

83 Ch 11 Handling Back Reporting 81 Figure 65: Download of code catalogs Transfer of notifications to FSE Notifications can be replicated to FSE using the integration scenario as described in chapter 8, Transfer of Assets to FSE. Notifications are handled together with other objects by /WSOPT/C_ASSET_UPDATE_BTE and include notification header data as listed in the table Notification download on page 82. If further details of the notification are required to support the back reporting process these details can be added using the enhancement spot /WSOPT/NOTIFICATION provided for this scenario. Processing of the back report in S/4HANA The integration scenario ERPMobile supports the creation of new notification items, causes, activities and tasks in SAP based on the technical back reporting in Edge Mobility. The function module /WSOPT/C_PI_NOTIF_UPD_IN is called from SAP NetWeaver PI, which will use the BAdI interface of /WSOPT/NOTIFICATION to create the queue entry with function module /WSOPT/C_NOTIF_UPDATE_I. This module will transform the data from FSE into an update for the related notification. The data structures of the FSE table BackReporting have to be enhanced according to the actual project needs and must be mapped in PI to the data structures of /WSOPT/C_PI_NOTIF_UPD_IN. Mapping between FSE and S/4HANA S/4HANA notifications are send as updates to Back Reporting in FSE. The update of a back report in Edge Mobility can be used to create new notification items, causes, activities or tasks in S/4HANA. When the scenario for the replication is activated as described in chapter 8, notifications are replicated from S/4HANA to FSE as part of this scenario. The update of the related S/4HANA order is the trigger for creating or updating a BackReporting entry in FSE. Trigger for the update of a S/4HANA notification is the change of the related task to a certain status in FSE.

84 Ch 11 Handling Back Reporting 82 Notification update Field Service Edge BackReporting S/4HANA Notifications Remarks ExternalRefID Notification SAPID S/4HANA unique key for a notification created from concatenation of SAPID prefix + N + notification number. ExternalRefID must be set as object reference in FSE. Number Short Text Long Text Notification number Short Text of the notification Long text of the notification Optional. Short Text of the notification. The text length is limited to 1024 characters. Priority Notification Priority It s assumed that this is a numeric value. In S/4HANA it s technically possible to define non-numeric keys for the priority as well. ExternalRefIDAsset Asset SAPID Unique key of an asset. BackReportingType CatalogProfile Notification Type Catalog Profile CodingGroup Coding Group Name to CodingGroup, ParentCatalogProfile to CatalogProfile. CodingCode Coding Code Name to CodingCode, CodingGroup to CodingGroup. BackReporting update S/4HANA Notifications Notification SAPID Order ID Operation ID Suboperation ID AUFPL APLZL Remarks Unique key as defined during the download. Order Number Operation/Activity Number Order Number Routing number of operations in the order General counter for order

85 Ch 11 Handling Back Reporting 83 Notification No Structure /WSOPT/NOTITEM Structure /WSOPT/NOTACTVI Structure /WSOPT/NOTCAUSI Structure /WSOPT/NOTTASKI Optional. Notification Item Notification Activity Notification Cause Notification Task Note: As no default mapping for the update of notifications by a change of a BackReport in FSE is provided, the table above shows only a shortened overview of the implemented interface. Please see the structure listings in the Appendix in the developer guide for a complete overview.

86 Ch 12 Technical Interface Description 84 C H A P T E R 12 Technical Interface Description The architecture of the SAP S/4HANA PI Adaptor for Click Field Service Edge is based on a backend Add-on in S/4HANA, a middleware message mapping and a configuration of the Field Service Edge System. This chapter will explain the used communication methods and the installation of the mentioned parts. Figure 66: Architecture of S/4HANA PI Adapter for Field Service Edge The communication between the S/4HANA system and the Field Service Edge system is integrated through the SAP NetWeaver PI infrastructure, which maps between the different message formats. This PI component acts as a middleware to enable the communication between S/4HANA and Field Service Edge. The chosen communication method for the communication between S/4HANA and SAP PI is RFC. The chosen communication method between SAP PI and Field Service Edge is via Web Services (HTTPS / SOAP). Installation of S/4HANA PI Adaptor Prerequisites The S/4HANA PI Adaptor for Field Service Edge is divided into different parts, which have to be installed in different ways and on different servers. This section describes the interface parts of the adaptor, which are installed and configured in the SAP components. Additional notes about the Adaptor will be published in SAP note Prerequisites for ClickSoftware Field Service Edge There are no specific prerequisites for Field Service Edge. The FSE application is running in the cloud and will be continuously updated and maintained.

87 Installation Steps Ch 12 Technical Interface Description 85 Prerequisites for S/4HANA The initial supported SAP S/4HANA on-premise release is Please check the SAP Support Portal (Product Availability Matrix) for notes regarding support of further releases. Prerequisites for SAP NetWeaver PI The supported SAP NetWeaver PI release is SAP NetWeaver PI 7.5. The SLD CR Content containing the necessary product versions and software component versions will be available once this product version is certified by SAP. Please open a support ticket at your software vendor, in case this is not available yet. To enable HTTPS connection in PI, look into the 'SAP Process Integration Security Guide' under 'Network and Transport Layer Security => HTTP and SSL'. The following table lists the components of S/4HANA PI Adaptor for Field Service Edge and the way how they should be implemented. Installation in S/4HANA S/4HANA PI Adaptor for Field Service Edge Component WSOPT Add-On package Implementation/Configuration Way Installation or upgrade with transaction SAINT Interface specific customizing Customizing of interface specific customizing tables (FSE relevant order types and control keys) Activating of interface specific customer exits and BAdIs, BTEs and workflows Customizing of RFC and qrfc Activating of user exits for order saving and HCM implementations Configuration of the communication Installation in SAP NetWeaver PI PI Tool System Landscape Directory (SLD) Enterprise Service Repository (ESR) Implementation steps Registration of Technical Systems and manual creation of Business Systems Import XI Content with Design Objects via file system into PI Enterprise Service Repository Integration Directory (ID) Create Configuration Objects (communication channels, Integrated Configurations or Integration Scenario objects) Installing the WSOPT Add-On The ABAP code with the enhancements to S/4HANA is delivered as an installable Add- On package for the software component WSOPT. The version of the software

88 Ch 12 Technical Interface Description 86 component is 216_700. The S/4HANA FSE integration requires a minimum support package level 9. Preparing the installation The Add-on and its support packages are provided as SAPCAR archives (SAR file extension). The main archive includes the installation package as well as the upgrade package. Transfer the SAR-files to a local directory on your front end. Log on to your S/4HANA system in client 000 as a user with SAP_ALL authorization. Do not use the SAP* or DDIC users. Upload the installation package and all support packages to the EPS inbox on the S/4HANA system by calling transaction SAINT, and select the menu: Installation Packages Load packages From the front end. Starting the installation During the installation of the Add-on and its support packages a password will be requested for each package needing special attention. Please consult SAP note if these passwords were not provided to you or consult your sales representative before continuing with this step. Call transaction SAINT and select the Start button. This lists all the installable Add-Ons. If this is the first time that the Add-On is to be installed select the WSOPT installation package, otherwise select the upgrade package. After the selection click the button Continue. If all prerequisites for importing the Add-On are met, the system displays the corresponding queue. The queue comprises the installation or upgrade package and should also include all Support Packages. To begin the installation, click the button Continue. After a successful installation the queue has to be confirmed. For more information regarding the installation, call transaction SAINT and click the information button in the application toolbar. Even more details about the installation procedure are documented in the SAP online help. Preparing the System Landscape Directory During the configuration of the integration in SAP NetWeaver PI Integration Directory, the involved communication parties are referenced by their installed software components. These software components are part of the product definitions in the CR Content for the System Landscape Directory (SLD), which must be updated to its latest version. For general recommendations and procedures in the administration and operation of the System Landscape Directory, please consult the online resource at SAP, especially the guide User Manual Configuring, Working with and Administering System Landscape Directory. The following subsection documents the minimal procedure to register the installed instance of the S/4HANA system together with the Add-On in the PI SLD. In cases where multiple SLDs are in use, a cascading setup may be chosen according to the before mentioned SLD documentation resources. Technical Systems in SLD The systems involved in each integration scenario are represented as two technical systems in the SLD one technical system for the S/4HANA and one for the Field Service Edge server.

89 Ch 12 Technical Interface Description 87 To register the SAP system in the PI SLD, logon to the SAP system with a sufficiently authorized user and run the transaction RZ70. Enter at minimum the hostname and gateway port of the PI system in the SLD Bridge configuration. Optionally a background job can be scheduled at a regular interval to collect the updated system data and retransmit it to the SLD. Start the data collection and job scheduling from the menu. Collected data and system information should be transmitted to the SLD now. After a successful registration the SID of the chosen system should be listed in the technical systems section of the SLD. The Add-On is registered as an instance of the software component SER.OPT.SUT CS-ERPADAPT216_700 and technical name WSOPT. Additionally to the automatic registration a link to the according software product must be created. In the detailed view of the technical system activate the button Add New Product and select the product SAP WS&O BY CLICKSOFTWARE The installed software component should be already enabled. Save the selection. Figure 67: Technical System listing in SLD Business Systems in SLD Create two Business Systems in the SLD one for S/4HANA (e.g. BS_ERP60) and one for the Field Service Edge system (e.g. BS_CS8ERP). Instead of the suggested names any other name, optionally following a mandated naming-scheme, can be used too. Click on New Business System and follow the steps of the wizard as shown in Figure 68 by using the following configurations: S/4HANA Business system Type of technical system: AS ABAP Technical system: choose your S/4HANA system Technical client: choose your main S/4HANA client Business system name: e.g. BS_ERP60 Installed products: needs SAP WS&O BY CLICKSOFTWARE Business system role: Application System

90 Ch 12 Technical Interface Description 88 Field Service Edge Business system for S/4HANA Type of technical system: Third Party/Other Technical system: choose instance FieldServiceEdgeServer of your system Business system name: e.g. BS_CS8ERP Installed products: needs SAP WS&O BY CLICKSOFTWARE Installed software: CLICK S.O. SERVER Business system role: Application System Figure 68: Business System Wizard The next screen shows an overview of all created Business systems. Figure 69: Overview of the created Business Systems in the SLD Configuration of SAP NetWeaver PI Integration This section describes the steps necessary for the initial configuration of the integration scenarios. The configuration consists of several steps as specified in the following order: importing the PI design objects into the repository, linking the business systems to the related technical systems, creating the communication channels from and to the PI system and finally the generating the configuration models. Importing PI Design Objects into ESR The PI Design Objects are delivered as separate files with the file suffix.tpz the S/4HANA integration and general Field Service Edge definitions. The files contain the predefined design objects used during the configuration process. All provided Field

91 Ch 12 Technical Interface Description 89 Service Edge objects and the SAP design objects used for your environment are needed. To import the file(s) open the Enterprise Services Builder as found in the NetWeaver Process Integration Tools on the PI system and select from the menu: Tools Import Design Objects to load the objects from the local client or from the server. After a successful import the following software products with their versioned software components will be available in the Design Objects List of the Enterprise Service Builder: CLICK S.O. SERVER SER.OPT.SUT CS-ERP ADAPT216_700 Once imported no more configuration steps has to be done in the Enterprise Services Builder until the message mappings has to be changed or extended. Note: The view of the imported and available objects may vary depending on the applied view filter. Figure 70: Overview of the imported PI Design Objects Configuring the runtime environment in the Integration Directory The following steps are done in the Integration Directory as found in the NetWeaver Process Integration Tools on the PI system. Assigning Business Systems from the SLD At first you need to assign your Business Systems to Components. In the navigation area (Object View), choose Communication Component Without Party Business System. Right-click on Business System Assign Business System and follow the upcoming wizard to assign the two new Business Systems BS_CS8ERP and BS_ERP60 from the SLD. Note: In order to reflect any changes done in the SLD it is necessary to Clear the SLD Data Cache in the Integration Builder.

92 Ch 12 Technical Interface Description 90 Figure 71: Assigning Business Systems from the SLD in the Integration Builder For further information please take a look at SAP NetWeaver PI documentation. Communication Channels for S/4HANA Business Systems The communication with the S/4HANA Business Systems is done using communications channels of type RFC adapter. For each S/4HANA Business System create one sender and one receiver communication channel as described in this section. RFC adapter type channels are generic and can transfer various messages. The exact message to be transferred is determined by the message mappings. For the S/4HANA integration, select the Communication Channel node in BS_ERP60 and choose New from the context menu. Enter your system specific values with mandatory settings entered. Figure 72 shows an example configuration screen. Adapter Type Application Server (Gateway) Application Server Server (Gateway) Program ID Unicode flag Maximum Connections RFC Metadata Repository Parameter RFC Sender S/4HANA server or PI server Sapgw<instanceNo> Free choice, eg ERP_RFCSender Enabled Enter a value matching your setting for number of qrfc work processes on ERP Maintain all mandatory fields to enable access to RFC Metadata Repository on the S/4HANA system.

93 Ch 12 Technical Interface Description 91 Figure 72: Creating the Sender communication channel Note: The communication channel setup dialog sets the parameter Party by default to *, which must be changed to an empty string for RFC type adapters. Please consult SAP note for further details. For sending changes to the S/4HANA system (Business System is receiver), create a Receiver RFC communication channel. Beforehand a communication user must be created in the integration client of the S/4HANA system. Enter the logon data for this user in the RFC Client Parameter area and your other system specific values in the communication channel settings. Communication Channels for FSE Business System The communication between the S/4HANA Business Systems and the Field Service Edge Business System is using SOAP adapter type communications channels either receiver or sender type. Depending on the Business Systems taking part in the integration different sets of channels have to be configured. As SOAP channels can t be defined in a generic way, each channel definition is specific to one SOAP action. The predefined SOAP channels are the complete set of actions supported by the adapters and must not be changed for customer specific enhancements. For the communication with the S/4HANA Business System create a communication channel for each web service at the corresponding Field Service Edge Business System (i.e. BS_CS8ERP) as described in this section. Note: The names of the communication channels are just a suggestion and may be adopted according to local requirements. Replace the variable <HOST> in the Target URL with the actual hostname of the IIS web server instance of the Field Service Edge Server and the variable <PORT> with the service communication port number, e.g. clickhost.example.com:8443. In cases where the default port 443 is used the suffix :<PORT> (colon and port number) can be omitted. For easier configuration and to reduce potential error sources templates are provided with the ESR Content and can be applied from the Communication Channel Editor.

94 Ch 12 Technical Interface Description 92 You can derive the required hostname of the IIS web server instance of the Field Service Edge Server from the dialog login URL of the Field Service Edge Server according to this description from the Field Service Edge Wiki: If your dialog login URL is then the <HOST> for your configuration URL for calling the webservice from SAP PI is Field Service Edge receiver side communication channels: Web service CreateCalendar Communication Channel: Target URL: SOAP Action: Web service CreateNonAvailability Communication Channel: Target URL: SOAP Action: Web service CreateResource Communication Channel: Target URL: SOAP Action: Web service GetResource Communication Channel: Target URL: SOAP Action: Web service GetResources Communication Channel: Target URL: SOAP Action: Web service GetResourceSchedule Communication Channel: Target URL: SOAP Action: SOAPReceiver_CreateCalendar rviceoptimizationservice.svc/basichttpint rvice/createcalendar SOAPReceiver_CreateNonAvailability rviceoptimizationservice.svc/basichttpint rvice/createnonavailability SOAPReceiver_CreateResource rviceoptimizationservice.svc/basichttpint rvice/createresource SOAPReceiver_GetResource erviceoptimizationservice.svc/basichttpint ervice/getresource SOAPReceiver_GetResources erviceoptimizationservice.svc/basichttpint ervice/getresources SOAPReceiver_GetResourceSchedule heduleservice.svc/basichttpint ResourceSchedule

95 Ch 12 Technical Interface Description 93 Web service GetCalendar Communication Channel: Target URL: SOAP Action: Web service GetAssignment Communication Channel: Target URL: SOAP Action: Web service GetAppointments Communication Channel: Target URL: SOAP Action: Web service GetTasks Communication Channel: Target URL: SOAP Action: Web service ProcessTaskEx Communication Channel: Target URL: SOAP Action: Web service ProcessTask Communication Channel: Target URL: SOAP Action: Web service UpdateAssignment Communication Channel: Target URL: SOAP Action: SOAPReceiver_GetCalendar rviceoptimizationservice.svc/basichttpint rvice/getcalendar SOAPReceiver_GetAssignment heduleservice.svc/basichttpint ssignment SOAPReceiver_GetAppointments heduleservice.svc/basichttpint ppointments SOAPReceiver_GetAssignment heduleservice.svc/basichttpint asks SOAPReceiver_ProcessTaskEx heduleservice.svc/basichttpint esstaskex SOAPReceiver_ProcessTask heduleservice.svc/basichttpint esstask SOAPReceiver_UpdateAssignment heduleservice.svc/basichttpint ateassignment

96 Ch 12 Technical Interface Description 94 Web service UpdateCalendar Communication Channel: Target URL: SOAP Action: Web service UpdateResource Communication Channel: Target URL: SOAP Action: Web service ExecuteMultipleOperations Communication Channel: Target URL: SOAP Action: Web service DeleteCalendar Communication Channel: Target URL: SOAP Action: Web service DeleteAssignment Communication Channel: Target URL: SOAP Action: Web service DeleteResource Communication Channel: Target URL: SOAP Action: Web service ExecuteOperation Communication Channel: Target URL: SOAP Action: SOAPReceiver_UpdateCalendar rviceoptimizationservice.svc/basichttpint rvice/updatecalendar SOAPReceiver_UpdateResource rviceoptimizationservice.svc/basichttpint rvice/updateresource SOAPReceiver_ExecuteMultipleOperations rviceoptimizationservice.svc/basichttpint rvice/executemultipleoperations SOAPReceiver_DeleteCalendar rviceoptimizationservice.svc/basichttpint rvice/deletecalendar SOAPReceiver_DeleteAssignment heduleservice.svc/basichttpint eassignment SOAPReceiver_DeleteResource rviceoptimizationservice.svc/basichttpint rvice/deleteresource SOAPReceiver_ExecuteOperation rviceoptimization.svc/basichttpint rvice/executeoperation

97 Ch 12 Technical Interface Description 95 The following screen in Figure 73 shows an example configuration for the receiver communication channel SOAPReceiver_CreateCalender. The other communication channels need to be created manually in the same way. Figure 73: Creating a receiver communication channel Note: If user authentication is used for the communication channels, only Basic Authentication can be chosen in the IIS on the server where Field Service Edge is installed ( Sites Default Web Site SO IntegrationServices). By default Windows Authentication is configured by the Field Service Edge installer. This configuration has to be changed and Field Service Edge has to be restarted. If no authentication is used for the communication channels, the authentication for the integration services has to be changed to Anonymous Authentication. The Field Service Edge sender side communication channels are: Communication Channel: Communication Channel: Communication Channel: Communication Channel: Communication Channel: Communication Channel: Communication Channel: SOAPSender_AssignmentCreate SOAPSender_AssignmentUpdate SOAPSender_AssignmentDelete SOAPSender_TaskUpdate SOAPSender_NonAvailabilityCreate SOAPSender_NonAvailabilityUpdate SOAPSender_NonAvailabilityDelete The only mandatory setting for the sender side communication channels is Exactly once for the Quality of Service. Configuring the integration SAP PI offers two ways of setting up the processing of the process integrations Configuration Scenarios and Integrated Configuration. Please consult the technical documentation of SAP PI for details about the differences between the configuration types and for instructions on how to setup the first type. For best performance of the

98 Ch 12 Technical Interface Description 96 provided SAP PI Adaptor for the Field Service Edge, it is recommended to use the functionality of Integrated Configurations. For each of the following outgoing interfaces please create an Integrated Configuration as described in detail below. /WSOPT/C_PI_BCAL_GET /WSOPT/C_PI_BCAL_INS /WSOPT/C_PI_BCAL_UPD /WSOPT/C_PI_ECAL_DEL /WSOPT/C_PI_ECAL_GET /WSOPT/C_PI_ECAL_INS /WSOPT/C_PI_ECAL_UPD /WSOPT/C_PI_ENG_DEL /WSOPT/C_PI_ENG_GET /WSOPT/C_PI_ENG_GET1 /WSOPT/C_PI_ENG_INS /WSOPT/C_PI_ENG_UPD /WSOPT/C_PI_ENGREL_UPD /WSOPT/C_PI_NA_DEL /WSOPT/C_PI_NA_INS /WSOPT/C_PI_NA_UPD /WSOPT/C_PI_NA_GET /WSOPT/C_PI_NA_BY_SOKEY_DEL /WSOPT/C_PI_NA_ERROR_UPD /WSOPT/C_PI_NOTIF_UPD_OUT /WSOPT/C_PI_SCHED_APPOINT /WSOPT/C_PI_DICTIONARY_UPD /WSOPT/C_PI_ORDER_UPD In case the Edge Mobility integration with transfer of one or all of assets, measurements and parts is to be used, the following interfaces have to be configured in the same way: /WSOPT/C_PI_EQUIPMENT_UPD /WSOPT/C_PI_FUNCLOC_UPD /WSOPT/C_PI_MATSTOCK_UPD /WSOPT/C_PI_MEASPOINT_UPD In the Integration Builder, select Integrated Configuration from Menu Object New. Enter the S/4HANA Business System as Communication Component and select the interface you want to configure:

99 Ch 12 Technical Interface Description 97 Figure 74: Creation of an Integrated Configuration In the following steps settings have to be done on each of the configuration tabs: Inbound Processing, Receiver, Receiver Interfaces and Outbound Processing. On the tab Inbound Processing, select the communication channel ERP_RFCSender : Figure 75: Integrated Configuration Inbound Processing On the tab Receiver select the Business System of the FSE instance (e.g. BS_CS8ERP ) as communication component:

100 Ch 12 Technical Interface Description 98 Figure 76: Integrated Configuration Receivers On the tab Receiver Interfaces use the search help for the operation mapping and select the mapping that was found: Figure 77: Integrated Configuration Receiver Interfaces On the tab Outbound Processing select the communication channel that corresponds to the (destination) Name of the selected Operation Mapping:

101 Ch 12 Technical Interface Description 99 Figure 78: Integrated Configuration Outbound Processing After that, save and activate your configuration. The inbound messages coming from the Field Service edge Server are configured as an Integrated Configuration as well. Please follow the procedure as outlined before for the following SOAP Sender interfaces: AssignmentCreate AssignmentUpdate AssignmentDelete NonAvailabilityCreate NonAvailabilityUpdate NonAvailabilityDelete For all these interfaces, the configuration is as follows: Section Field Sender communication component Inbound Processing communication channel Receiver communication component Receiver Interfaces Operation Mapping Outbound Processing communication channel Configuration Value Business System of the FSE instance (e.g. BS_CS8ERP ) SOAPSender_<InterfaceName> (e.g. SOAPSender_AssignmentCreate ) Business System of the S/4HANA instance correlated to the sender (e.g. BS_ERP60 ) <InterfaceName>_To_<WSOPT_Function> (e.g. AssignmentCreate_To_WSOPT_C_PI_ASSIGN MENT_UPDATE ) Receiver channel of the S/4HANA Business System (e.g. ERP_RFCReceiver )

102 Ch 12 Technical Interface Description 100 Using a Process Integration Scenario for TaskUpdate Finally, the TaskUpdate integration needs to be configured separately as it is dependent on the transferred properties. In the basic setup, where only the S/4HANA order operation shall be updated, please follow the instructions above to configure an Integrated Configuration using the service interface /WSOPT/C_PI_OPR_STATUS_UPD. In an Edge Mobility integration scenario, where material data, measurements or time confirmations (all of them or a subset) has to be updated as well, the Integrated Configuration cannot be used. In that case the TaskUpdate message from Field Service Edge will be split up and mapped into multiple outgoing messages. Note: The TaskUpdate integration is delivered in the two scenarios ERP_InboundOrderIntegration and ERP_InboundMobileIntegration, which offer different variants for reference to customer modifications one with the basic update of order data and one with the full Edge Mobility integration. Modifications might be needed for different subsets or configurations. Please configure the integration as follows: In the Menu, navigate to Tools Apply Model from ES Repository. Select type Process Integration Scenario and the model ERP_InboundOrderIntegration or ERP_InboundMobileIntegration to configure from ESR. Click Continue and Finish to import the scenario. In the wizard where you configure the scenario, click the button Assign component... to assign the systems to the components. Choose the Business systems for FSE and the S/4HANA System. Please see the tables in section Configuration Scenario Mappings on page 130 for a complete listing using the suggested names from this documentation. Note: Because of restrictions in the PI modeling both communication partners are labeled with the same software product name. To ease the distinction between S/4HANA and FSE systems, the action names were formatted differently: capital letters only for the S/4HANA system (e.g. ORD_UPD), mixed case letters for the FSE system (e.g. Process_Task).

103 Ch 12 Technical Interface Description 101 Figure 79: Model Configurator wizard for assigning Business systems and Communication channels Click on the Button Configure connections. For each action pair, select a matching communication channel as defined previously. For the FSE communication component (sender) a matching communication channel must be selected from the list, e.g. choose SOAPSender_TaskUpdate communication channel for the TaskUpdate action. For the S/4HANA system communication component the corresponding RFC Receiver channel should be proposed correctly. Note: Please make sure that all the fields for the communication channels and communication components are carefully fulfilled. The indicator bar on the right side of the following screen does not check if all fields are configured. If you forget them, then mandatory agreements and determinations will not be generated and the Integration scenario will not work correctly. Afterwards, click on the Buttons Activate all connections and Generate all connections for integration server communication. Save the settings and push the Generate button. In the following dialog, proceed as follows:

104 Ch 12 Technical Interface Description 102 Figure 80: Settings for Generation of Configuration Objects Choose Start to start the generation process. Finally activate your standard change list. In case your TaskUpdate message does not include the necessary information for update of material consumption, measurement documents and backreporting for some updates and you want to prevent processing of those updates in the S/4HANA backend, please add conditions to the generated Interface Determination for TaskUpdate. A basic set of conditions, which can be used as reference is: TaskUpdate_To_WSOPT_C_PI_MATCON_INS: Xpath: /TaskUpdate/Task/PartsUsed/Value exists TaskUpdate_To_WSOPT_C_PI_MEASDOC_INS Xpath: /TaskUpdate/Task/Assets/Value/MeasurementPoints/Value/Meas urementdocument exists TaskUpdate_To_WSOPT_C_PI_TIMECONF_INS Xpath: /TaskUpdate/Assignment/Finish exists Communication settings in S/4HANA This section describes the necessary settings on the S/4HANA system for the communication with the PI system. The configuration consists of creating RFC destinations and publishing them in the customizing settings of the Add-On. RFC destination settings in S/4HANA For the communication between S/4HANA and SAP PI a main RFC destination is needed. Additionally each request is placed in a queued RFC for easier error and retransmission handling as well as debugging.

105 Ch 12 Technical Interface Description 103 Main PI RFC destination(s) Create at least one RFC destination (transaction SM59) on the S/4HANA system for communication between S/4HANA and SAP NetWeaver PI. This destinations needs to be entered in the WSOPT customizing tables /WSOPT/HR_DEST and /WSOPT/PM_DEST in the steps later on. The default scenario in this guide uses only one destination common to both parts. Required entries are: Connection type: TCP/IP (type T) Activation type: Registered server program Program ID: Program ID of the RFC Sender communication channel as specified in SAP PI Integration Builder, e.g. ERP_RFCSender Gateway host: hostname of the selected gateway system Gateway service: port number or name of the selected gateway system Finally save and test your RFC destination. The test will succeed if the registration of the corresponding PI communication channel on the gateway succeeded. For further information regarding the configuration and usage of the PI RFC-Adapter please consult the FAQ in SAP note and the SAP NetWeaver PI documentation. Logical qrfc destination(s) The logical qrfc destination(s) should be defined for the background processing of the S/4HANA PI Adaptor for FSE in order to avoid qrfc problems as described in SAP note It is recommended to define the logical qrfc destination as a default qrfc destination for the SAP S/4HANA PI Adaptor and use this qrfc in the communication settings for HCM and PM. Different destinations may be used for HCM and PM integration. Execute transaction SM59 and click on the symbol Create to create a logical qrfc destination. The system shows a screen where the logical destination settings can be defined. Required entries are: Name of your logical destination in the qrfc destination field (e.g. CLICK_QRFC ) Reference entry must be NONE destination Connection type must be L as reference entry (refers to another destination) Description of your qrfc destination Logon data all logon data must be maintained (language, client, user, password) Note: The replication of dictionaries from S/4HANA to FSE is language dependent. Complete texts can only be replicated in one language. This language is dependent on the SAP logon language of the user, under which the RFC call is to be executed.

106 Ch 12 Technical Interface Description 104 Figure 81: Definition of CLICK_QRFC in transaction SM59 If all required settings are maintained you can test your qrfc destination. Push the button Test connection for testing your qrfc destination. Figure 82: Successful Connection Test of CLICK_QRFC Authorization for qrfc user The S/4HANA PI Adaptor for Field Service Edge requires a specific communication user who has the following authorizations: Login into S/4HANA from an external application (when assignment or task XML messages are being sent from FSE to S/4HANA). Therefore, this communication user needs the authorization object S_RFCACL to be assigned to him. Processing of queue entries in background task. The source of queue entries can vary by customer s needs. For instance, if you want to use the HCM interface then HCM authorizations for the specific infotypes are also required. If you want to schedule order operations then you need the authorization for order processing. If you want to schedule notification tasks/actions then you need authorizations for notification processing. Because of the customer specific implementations, we are not able to deliver a standard role or user profile for the interface user. It is recommended to check which authorizations are required using a trace log for the communication user.

107 Communication settings HCM Ch 12 Technical Interface Description 105 You have to specify which destination is used as the destination to send the outgoing HCM related messages to the qrfc-queue. In the second entry, you define the destination of your PI server to process the messages. If you check the box for the application log information and error messages are stored in the SAP standard message log. The specified SAPID prefix is concatenated with the numeric engineer ID in the engineer SAPID (ExternalRefID in FSE Schema) and with the engineer calendar ID in the engineer calendar SAPID field. You can define different prefixes for different instances of your S/4HANA environment to distinguish them in Field Service Edge. Use the transaction /WSOPT/HR_DEST to define the communication data. The transaction is not relevant for customizing transports to allow different configurations in the development and test environment as in the production environment. Communication settings PM Figure 83: Communication settings HCM transaction /WSOPT/HR_DEST Note: The values shown in Figure 83 are examples only, e.g. the prefix WSC001 follows a format of <SAP System ID> and <SAP Client>. Please use a valid prefix for your environment. You have to specify which destination is used as the destination to send the outgoing PM related messages to the qrfc-queue. In the second entry, you define the destination of your PI server to process the messages. If you check the box for the application log information and error messages are stored in the SAP standard message log. The SAPID prefix is concatenated with a 1-character type flag and the object specific ID and used as a unique key in the communication with Field Service Edge (mapped to ExternalRefID in FSE Schema). You can define different prefixes for different instances of your S/4HANA environment to distinguish them in Field Service Edge. The prefixes for HCM and PM do not have to be the same. Use the transaction /WSOPT/PM_DEST to define the communication data. The transaction is not relevant for customizing transports to allow different configurations in the development and test environment as in the production environment. It's possible that HCM and PM data share the same RFC connections.

108 Ch 12 Technical Interface Description 106 Figure 84: Communication settings PM transaction /WSOPT/PM_DEST Note: The values shown in Figure 84 are examples only, e.g. the prefix WSC001 follows a format of <SAP System ID> and <SAP Client>. Please use a valid prefix for your environment. Communication settings in Field Service Edge Enabling integration with external systems The Integration of Field Service Edge with external systems is not configured by default in the Installation of FSE. Therefore two additional steps are needed to setup the integration with the S/4HANA PI Adaptor enabling of events on the multiple objects for triggering outgoing messages and enabling additional Web Services. Enabling Object events In Legacy Administration Tool, please navigate to Central Settings Parameters Events Product Events. Select Sub Category W6BFAssignment and add a new Element Event with a new attribute Active and a new attribute Type. Active is set to True, Type is set to this value: W6IntEvents.W6IntAssignment, W6IntEvents Repeat the same procedure for Sub Category W6BFTask. Active is set to True, Type is set to this value: W6IntEvents.W6IntTask, W6IntEvents Configuration of outgoing messages In order to send assignment updates and task updates to S/4HANA, four outgoing messages need to be created, which are described in the following part. Before continuing with this step, please make sure that the object properties in the FSE Schema Editor have an ExternalRefID property, which has to be the object reference for these objects. It is mandatory to have an index on each of these properties. Please validate in the Schema Editor if the business objects Assignment, Engineer and Task have and index on the property ExternalRefID. Please consult the Service Edge - Technical Documentation for additional instructions. If this prerequisite is met please proceed in the Legacy Administration Tool as follows:

109 Ch 12 Technical Interface Description Setting destinations: Navigate to Central Settings Integration & Services Outgoing Destinations and open the Destinations node. For each of the sender channels as created in the steps in section Communication Channels for FSE Business System, create a destination setting with the parameters as shown in the following Figure 85. Use an URL-address in the extended format as recommended by SAP Note ty=<senderparty>&senderservice=<senderservice>&interface=<interf ACE>&receiverParty=<RECEIVERPARTY>&receiverService=<RECEIVERSERVI CE>&interfaceNamespace=<IFNAMESPACE> or the still valid short format: <BUSINESS_SYSTEM>:<CHANNEL> where <PI_HOST> has to be replaced by the hostname of the server running SAP NetWeaver PI, <PORTNUMBER> has to be replaced with the http port of the SAP NetWeaver PI instance (usually 50000), <BUSINESS_SYSTEM> has to be replaced by the referenced business system in the integration builder, where the channel is defined, e.g. BS_CS8ERP, and <CHANNEL> has to be replaced with the channel to be used. In the S/4HANA integration the channels, as defined in this example, would be: Integration level Basic Integration with FSE Back-Integration of Non-Availabilities Channels used in destinations SOAPSender_AssignmentCreate SOAPSender_AssignmentDelete SOAPSender_AssignmentUpdate SOAPSender_TaskUpdate SOAPSender_NonAvailabilityCreate SOAPSender_NonAvailabilityDelete SOAPSender_NonAvailabilityUpdate The four messages listed in the basic integration section are the minimal backintegration from the FSE server to S/4HANA. In an extended setup additional events may be used, which in turn may trigger other messages. SOAPSender_TaskUpdate plays a special role, as it must be adopted to the local needs and possibly extended with additional fields if used together with Assets, Parts or Measurements in an Edge Mobility integration. Even more extended integrations involve the sending of Non- Availabilities from FSE to S/4HANA. Please read the according chapters as well as the developer guide regarding further details. Note: The correct naming and the availability of a PI communication channel can be checked by opening the URL of a PI helper tool in the browser. In a correct setup the tool will show selected configuration parameters for the channel. The URL format is: Channel&channel=:<BUSINESS_SYSTEM>:<CHANNEL>

110 Ch 12 Technical Interface Description 108 Figure 85: Destination settings in the Legacy Administration Tool Figure 86: Message destinations in Legacy Administration Tool 2. Setting outgoing messages: After defining the destinations in the Integration Manager the outgoing messages can be defined. Messages are triggered by events on the related object. The objects used in this integration are Assignment and Task. This events need to be configured manually as shown in the previous section. Use the following scheme to define the messages (e.g. AssignmentCreate for object Assignment): Message name <object>create Event OnAdd

111 Ch 12 Technical Interface Description 109 <object>update <object>delete OnUpdate OnDelete Note: The names used for the outgoing messages do influence the message names used during the communication and must NOT be changed. The chosen names are defined in the messages mappings in the Enterprise Services Builder. The following steps are dependent of the grade of integration. Not all of the described messages need to be implemented. Navigate to Central Settings Integration & Services Outgoing Outgoing messages. Create the following messages for the Assignment object and link them to the destinations created in the step before. Set the properties for the messages as follows: For AssignmentCreate, AssignmentUpdate and AssignmentDelete: Assignment: Start, Finish, Key Assignment Task: CallID, Number, ExternalRefID Assignment Task Status: Name Assignment Engineers Engineer: ID, Name, ExternalRefID In addition define a translator for each of the outgoing Assignment messages. Use Type XSL(Text) and copy the translator script into the Value :

112 Ch 12 Technical Interface Description 110 Figure 87: Outgoing message configuration in the Legacy Administration Tool Use the following translator script for Assignment messages: <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl=" xmlns:ns0=" xmlns:xs=" exclude-result-prefixes="ns0 xs"> <xsl:output method="xml" encoding="utf-8" indent="yes"/> <!-- copy all items --> <xsl:template </xsl:template> <xsl:copy> </xsl:copy> <xsl:apply-templates <!--fix engineer format from SE to V8 --> <xsl:template match="assignment/engineers/value">

113 Ch 12 Technical Interface Description 111 <Value Key="0"> <Engineer> <xsl:copy-of select="./id"/> <xsl:copy-of select="./externalrefid"/> <xsl:copy-of select="./name"/> </Engineer> </Value> </xsl:template> </xsl:stylesheet> In case the back-integration of Non-Availabilities from FSE to S/4HANA is to be used, create the corresponding messages for the Assignment object and link them to the destinations created in the step before. Set the properties for the messages as follows: For NonAvailabilityCreate, NonAvailabilityDelete and NonAvailabilityUpdate: Assignment: ExternalRefID, Finish, Key, Start Assignment Engineers Engineer: ExternalRefID, ID Assignment NonAvailabilityStatus: Name Assignment NonAvailabilityType: Name A translator for each of the outgoing Non-Availability messages is also required. Use Type XSL(Text) and copy the translator script into the Value of each Non-Availability message. Use the following translator script for Non-Availability messages: <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl=" xmlns:ns0=" xmlns:xs=" exclude-result-prefixes="ns0 xs"> <xsl:output method="xml" encoding="utf-8" indent="yes"/> <!-- copy all items --> <xsl:template <xsl:copy> </xsl:copy> <xsl:apply-templates

114 ERP TaskUpdate MATCON MEASDOC TIMECONF Ch 12 Technical Interface Description 112 </xsl:template> <!--fix engineer format from SE to V8 --> <xsl:template match="assignment/engineers/value"> <Value Key="0"> <Engineer> <xsl:copy-of select="./id"/> <xsl:copy-of select="./externalrefid"/> </Engineer> </Value> </xsl:template> </xsl:stylesheet> Note: The property NonAvailabilityStatus has to be created as an UDP in FSE according to the description in Entitlement procedure in S/4HANA and FSE for Absences and Attendances on page 41. The property will be only processed in S/4HANA, if not empty. The property is as well disabled on field level in target message in SAP PI message mapping (ESR) WSOPT_C_PI_NA_INS_Req_To_CreateNonAvailability_req and has to be enabled in local copy to become active. The definition of fields for message TaskUpdate is used by multiple integration scenarios. In the Out-of-the-box integration all the fields as listed below are expected. In case only configured and used fields have to be transferred, the message definition must be changed and re-imported into the External Message definition for Software Component CLICK S.O. SERVER in Enterprise Service Builder. Please see the table below for the exact usage of fields by the supported mappings: Assignment: Finish Assignment: Key Assignment: Start Engineer: ExternalRefID Engineer: ID Task Assets MeasurementPoints: ExternalRefID Task Assets MeasurementPoints MeasurementDocument: ExternalRefID Task Assets MeasurementPoints MeasurementDocument: Reading X X X X X X X

115 Ch 12 Technical Interface Description 113 Task Assets MeasurementPoints: Unit X Task: CallID X X X Task District: Name X Task: ExternalRefID X X X Task: Number X Task PartsUsed: ExternalRefID X Task PartsUsed: QuantityUsed X Task Region: Name X Task Status: Name X Figure 88 shows an overview of all defined messages in the Outgoing Messages configuration in FSE. Figure 88: Outgoing messages in the Legacy Administration Tool For further information regarding the configuration and usage (especially authorization issues) of the PI SOAP-Adapter please consult the FAQ in SAP note and the SAP NetWeaver PI documentation. Message Grouping and Filtering To minimize the amount of messages send to the PI system and to restrict the messages to relevant ones, it is recommended to use filter criteria in the message definition. For a minimal setup it is necessary to create the following groups: Name Object Attributes NonAvailabilitiesToDelete Assignment ExternalRefID differs NonAvailabilitiesToCreate Assignment NonAvailabilityType.Name differs AND ExternalRefID equals TaskAssignments Assignment NonAvailabilityType equals (none) Using the groups configured above it is necessary to choose them in on the filter tab in the message definition. Please use the settings as shown in the following table.

116 Ch 12 Technical Interface Description 114 Message Group Value AssignmentCreate after TaskAssignments AssignmentDelete before TaskAssignments AssignmentUpdate after TaskAssignments before TaskAssignments NonAvailabilityCreate after NonAvailabilitiesToCreate NonAvailabilityDelete before NonAvailabilitiesToDelete NonAvailabilityUpdate after NonAvailabilitiesToDelete before NonAvailabilitiesToDelete NonAvailabilitiesToDelete: This group will avoid sending NonAvailability messages (Delete or Update) from FSE which don t have an ExternalRefID. Absences without an ExternalRefID will raise errors in the SAP queue and no further updates could be processed for the person. NonAvailabilitiesToCreate: This group is required to avoid a loop between S/4HANA and FSE. TaskAssignments: This group differentiates between NAs and task assignments. We need all changes performed for task assignments. Object references for messaging The messaging API of Field Service Edge can refer to objects that are defined in the database by properties that uniquely identify it. This identifiers can be the default ones or user-defined. The S/4HANA PI Adaptor for Field Service Edge is relying on special identifiers to uniquely relate objects in FSE and in S/4HANA. Although most needed object references are already provided by the default installation, it may be necessary to re-adjust the object references to the S/4HANA PI Adaptor expectations. This might be especially the case in upgrade projects. The object references can be viewed and modified in Legacy Administration Tool in Central Settings Integration & Services SXP Object Reference. Additionally to setting the object reference in the Administration tool it is also necessary to provide a database index on the properties used as identifier. Please use the FSE Schema Editor to make modifications to the database scheme. The complete set of object references and indexes is listed below. Object Reference Index Asset ExternalRefID Asset ExternalRefID Assignment ExternalRefID Assignment ExternalRefID BackReporting ExternalRefID BackReporting ExternalRefID

117 Ch 12 Technical Interface Description 115 Calendar Name Calendar Name District Name District Name Engineer ExternalRefID Engineer ExternalRefID MeasurementDocume nt ExternalRefID MeasurementDocument ExternalRefI D MeasurementPoint ExternalRefID MeasurementPoint ExternalRefID PartsInStock ExternalRefID PartsInStock ExternalRefID PartsStock Name PartsStock Name PartUsed ExternalRefID PartUsed ExternalRefID Region Name Region Name Task ExternalRefID Task ExternalRefID TechnicalHistory ExternalRefID TechnicalHistory ExternalRefID Message error handling By default the Integration Manager of FSE handles HTTP status error codes with internal status code 2, which means the message is discarded. This might lead to inconsistent data between S/4HANA Backend and the FSE Server. In order to prevent such situations it is recommended to configure the handling of selected HTTP status error codes as internal status 3, which marks the messages for resending and blocks the outgoing queue until the error situation is resolved. This makes it necessary to monitor the outgoing message queue on the FSE Server. Please use the Legacy Administration Tool and navigate to Central Settings Integration & Services Parameters Advanced and set the attribute HttpErrorCodesToResend to: 401,403,404,500,501,503 Customizing tables This chapter provides a list of customizing tables included in the SAP S/4HANA PI Adaptor for Click Field Service Edge. Regarding authorization access all customizing tables are assigned to authorization group PMC (PM: Application table). The column mandatory indicates if the maintenance of the table is obligatory. Table Name Description mandatory /WSOPT/HR_CUST Settings HR integration Yes /WSOPT/PM_CUST Settings PM integration Yes

118 Ch 12 Technical Interface Description 116 /WSOPT/C_ARBPL Relevant Work Centers Yes /WSOPT/C_OPRST Relevant Control Key Yes /WSOPT/ASSET_CUS Asset Transfer Settings No /WSOPT/STORLOC Engineer Storage Locations No Note: Unless the mandatory tables are configured the S/4HANA PI Adaptor for Field Service Edge will not forward any message to the Field Service Edge server. Authorization concept The Adaptor only provides transactions designed for system administration and configuration. However there is functionality for appointment booking and displaying of assigned engineers. These functions can be accessed if the user has the right authorization to access the standard transaction (e.g. PA30, IW31 etc.). All customizing tables are assigned to authorization group PMC (PM: Application table). This means any user who is entitled for the standard customizing of S/4HANA Plant Maintenance can work on the standard customizing for the adaptor as well. Installing SAP user menu shortcuts The SAP S/4HANA PI Adaptor for Click Field Service Edge contains a number of specific transaction codes which are necessary for customizing and using the interface. Those transaction codes are summarized in the role /WSOPT/WSO, which can be uploaded from a local file into your S/4HANA system. You can upload this role using the transaction code PFCG. Figure 89: Role Maintenance (transaction PFCG) Go through the menu Role Upload and choose the role in a selected folder. After upload you can change this role and assign it to SAP users.

119 Ch 12 Technical Interface Description 117 Backup procedure Figure 90: User menu for role /WSOPT/WSO On the user tab page you can assign the user names, which shall be able to use the specific adaptor transactions in the S/4HANA system. There are no specific backup procedures required for the WSOPT Add-On. All customizing tables of the Add-On will be stored in the S/4HANA database. Therefore the tables will be included in the implemented backup and restore procedure. Changes to previous releases The installation of the Add-On WSOPT as part of S/4HANA PI Adaptor for Field Service Edge will not uninstall the software components of the two previous WSCCLICK major releases. Because adaptor releases of version series 2.1.x are fully based on the SAP NetWeaver PI platform, settings have to be applied according to the instructions provided above. Update from previous adaptor patch release Updates from previous adaptor patches (i.e. from WSOPT 216_700 service pack 01 to service pack 03) may contain changes to the integrations which may require additional modifications in the customer implementation. To work properly the updated XI content with design objects is required along with the WSOPT service pack. Essential changes to the delivered objects are documented in the release notes. The XI content, the updated documentation and the release notes can be downloaded from SAP Service Marketplace or the ClickSoftware Download Portal.

120 Ch 12 Technical Interface Description 118 Upgrade from previous adaptor major release An upgrade is supported starting with WSOPT release 215_700 support package 02. The upgrade files are included in the installation package and are offered in the transaction SAINT. To process with the upgrade select the upgrade package of WSOPT instead of the installation package. Upgrades from a previous SAP PI based integration may need some migration steps, which will be outlined below. Additional changes may be documented in the Release Notes to each Service Pack delivery. New Design Object names follow the SAP naming schemes more closely. Please see Importing PI Design Objects on page 88 for more details. SAPID was implemented in Field Service Edge DB scheme as ExternalRefID, modifications to customer mappings may be necessary. Integrated Configurations are used by default in PI Integration Builder. Migration from previous Process Integration Scenarios is recommended. Names of Process Integration Scenarios were shortened for better readability and to follow the new naming recommendations. The TaskUpdate message definition in the S/4HANA integration was changed to asynchronous messaging and enhanced to support Edge Mobility resources like assets, materials, measurements and time confirmations. Changes are only necessary for enabling the new functionality. Inbound Assignment messages in S/4HANA integration are now handled asynchronously in PI. No changes needed for existing installations. The mapping of S/4HANA qualifications to skills was changed. The skill name is now concatenated from the qualification description and the SAP qualification ID in brackets. The language of the description is determined by the language of the SAP qrfc user used for the replication. This change was provided for the mapping of engineers and the mapping of tasks. In addition time phased skills are mapped as well including the start and date entered in S/4HANA. A download of all orders and engineers might be necessary to update the associations. Afterwards the old skills can be removed. The S/4HANA subtype of Absences/Attendances is now mapped to the Non-Availability type in Field Service Edge. The description and the subtype in brackets are concatenated. The old mapping to the comment field was removed. In new /WSOPT/MOBILE coding changes were done to the SAPID field: The maximal field length was extended from 32 to 64. A new format of Prefix + 1-char type flag + (internal) ID number was introduced. The high value of date field in S/4HANA will now be converted from SAP default to a more reasonable in the RFC interface. TimePhasedSkills are supported.

121 Ch 13 Troubleshooting 119 C H A P T E R 13 Troubleshooting Application log in S/4HANA In the S/4HANA integration it's possible to switch on the SAP application log for the PI adaptor in transaction /WSOPT/HR_DEST and /WSOPT/PM_DEST. All logs can be viewed with SAP standard transaction SLG1. The name of the main object is /WSOPT/. If enabled, the application log shows information about the transfer relevance of orders and engineer related information. The log can help in analyzing problems or unexpected behaviour of the selected entities during transfer to Field Service Edge. Outgoing message processing in S/4HANA For each interaction with the FSE server (like for updates of orders, notifications, engineer data or calendar data) an entry is created in the outbound queue. Each entry contains a function module, which is processed in a background task. The queue entry will be deleted automatically after the object was processed successfully. The entry stays in the queue if errors occur. Possible situations which result in such undeleted queues could be for instance: Field Service Edge server is not available Background processing fails (e.g. order could not be saved into the database because of missing sales data) S/4HANA: debugging is activated for the user of the logical qrfc destination The standard mapping has been changed in a wrong way (e.g. mandatory tags are not mapped anymore) You can check the contents of the outbound queues in the qrfc Monitor, which can be accessed with the transaction code SMQ1. Figure 91: qrfc Monitor suggested selection for relevant entries On the initial screen you can restrict the entries to be displayed by specifying: The client, in which the entries were generated

122 Ch 13 Troubleshooting 120 Name of the queue (use * for all queue names) In S/4HANA the system generates a name using the prefix CS_SDL, which is concatenated with the order or notification number, the calendar name or the HCM personnel number. Queue destination (use * for all queue destinations) In S/4HANA the destination is defined in standard customizing for external scheduling. Display waiting queues only On the next screen the system will display a list with queued outbound messages. In case you don t find any queue entries, check the configuration of the scheduling according to the configuration guide. You will find the required settings in section Communication settings in S/4HANA of chapter 12. The example in Figure 92 is showing the contents of the queues on an ERP system, where the user-specified logical qrfc destination is used by the interface when processing Order or HCM data. The outbound queue monitor displays following information about the waiting queue entries: Cl.: SAP client number Queue name: queue name, generated by the interface using the prefix CS_SDL_, followed by order number / notification number or personnel number according to the processed object Destination: name of the logical destination of the LUW Entries: number of LUWs per queue entry Figure 92: qrfc Monitor List of hanging outbound queue entries An LUW is a Logical Unit of Work, which is an inseparable sequence of database operations that must be executed either in its entirety or not at all. After selecting a queue entry for detailed view the displayed information changes to an extended, where in addition to the first screen the system displays more columns: Status: Status of the queue entry, e.g. SYSFAIL, WAITUPDATE and other

123 Ch 13 Troubleshooting 121 Date 1 /Time 1: Date/time when the first LUW was written into the queue NxtDate/NxtTim: Date/time when the last LUW was written into the queue Wait for queue: Shows the name of this queue which has to be processed before the current queue could be started = current queue has to wait until the depending queue has been processed Figure 93: qrfc Monitor Detailed queue monitor Global actions are placed as symbol above the queue. Actions to block, delete or activate the queue are available. By activating a queue the corresponding function module will be processed again. After a manual refresh of the overview screen the queue entry will be not listed anymore in case the reprocessing was successful. Selecting the Queue Name in the list by double-click, will show the detailed view for all entries saved in the queue. This detailed view shows additional information as shown in Figure 94 and described by the following fields: User: Name of the user who has started the qrfc Function module: Function module which was executed when the queue was generated Date/Time: Time when the LUW was written into the queue Status: Status text of the LUW; it is not equal with the queue status TID: Transaction identifier for the LUW Host: Name of the application server the LUW will be executed in Tran: Transaction which was active when the LUW was created Program: Program which produced the LUW Rpts: Repeats that are planned; if no changes have been made the default repeat settings will be used 30 attempts, one each 15 minutes Figure 94: qrfc Monitor Detailed view for queue entries Selecting the Status field of the detailed queue monitor (Figure 93) by double-click will show more details about the error. The following statuses are possible for a queue entry: SYSFAIL: An error occurred when processing the first LUW of the queue CPICERR: During processing of the first LUW a communication or network problem appeared. The LUW will be automatically executed a second time WAITUPDA: Queue is waiting to be completely saved into the database READY: A temporary status which indicates that the queue is waiting to be processed RUNNING: A temporary status which indicates that the first LUW of this queue is currently processed

124 Ch 13 Troubleshooting 122 RETRY: If there have been communication problems between FSE and SAP then the queue will be restarted automatically The overview truncates the error descriptions. The complete error description can be found in the response message sent by the FSE. You can find the initial request as well as the response in the Runtime Workbench in SAP NetWeaver PI. It s possible to restart a specific queue entry in the detailed queue monitor with F6-key or the Activate Queue button. Figure 95: qrfc Monitor Detailed view for queue entries with the Activating Queue button To lock one or more queue entries it's necessary to go to the status screen and press either the Lock Queue (F7) or the Lock Queue immediately button (F8). Figure 96: qrfc Monitor Detailed view for queue entries with the Lock Queue and Lock Queue immediately button In the following popup the queue name and the destination that should be locked can be entered. If the queue name is unknown the asterisk sign (*) can be used as wildcard character. The destination should be known. This will change the status of the queue entry to STOP. The Lock Immediately functionality will lock all queues even those in status RUNNING! Usually this action is not used. Figure 97: qrfc Monitor Lock Queue Popup To unlock one or more queue entries it's necessary to go to the status screen and press either the Unlock Queue (F5) or the Unlock without activating button (Shift+F4). Figure 98: qrfc Monitor Detailed view for queue entries with the Unlock Queue and Unlock without activating button In the following popup the queue name and the destination that should be unlocked can be entered. Wildcards are possible, but the Unlock functionality only works if the names of the two fields are exactly the same as in the lock entry. The Unlock functionality will also activate the queue entries.

125 Ch 13 Troubleshooting 123 Figure 99: qrfc Monitor Unlock Queue Popup Outgoing message processing in Field Service Edge On the FSE Server all the outgoing messages are processed by the Integration Manager, which is configured using the Legacy Administration Tool. In case messages, which are expected to be send from Field Service Edge to S/4HANA, are suspected to be missing, please check that the event for Field Service Edge is registered properly so that the event is triggered in case e.g. a task is changed in FSE, the outgoing destinations are configured properly so that the message can be sent to SAP NetWeaver PI successfully, at least one integration manager agent is activated for processing of the outgoing messages. For further details on how to perform this step, please consult the Service Edge - Technical Documentation. You will find further hints how to check the configuration of the outgoing messages queues. Have as well a look at chapter 12 of this manual to check the configuration. PI Runtime Workbench In case the communication between S/4HANA and the FSE server is not working properly the first step is typically to look into SAP NetWeaver PI. In Message Monitoring in the Runtime Workbench the message flow between the two systems is shown. Select Adaptor Engine Database and look into the messages for the time interval to inspect. Each successful communication will have two (when using Integrated Configuration on the Adapter Engine) or four (when using Integration Engine) entries: Request from S/4HANA to PI with the RFC field names (optional) Converted data in the format of the SO web service Reply from FSE to PI in web service format (optional) Converted reply in RFC format.

126 Ch 13 Troubleshooting 124 Figure 100: PI Runtime Workbench Message Monitoring Please analyze the details of the processing and the payload to understand what has happened. If messages expected from correlating actions are not listed in the overview, please examine the configuration and the local logs on both sides to find more information. The following chapter might help in resolving common mistakes. Note: The description of the PI monitoring functionalities and their usage is far too complex to be described here. Only a basic introduction and first steps are provided here. Some common errors and their solutions are described in the SAP Developer Network. Resolving known pitfalls Problem 1: Direct input of transaction code (e.g. /WSOPT/HR_CUST) in SAPGui does not work. SAPGui status line shows: This function is not possible. Solution 1: You may need to put a /n in front of the transaction code e.g. /n/wsopt/hr_cust Problem 2: No data is transferred to FSE with batch update reports. Solution 2: Trace down the root cause for the issue by following the next steps: Step description check application log (SLG1) for relevance information check outbound qrfc Monitor (SMQ1) for stucked entries and error messages check the Centralized Log on the FSE system check SXMB_MONI or Message Monitor/Runtime Workbench on the PI system for message processing errors