SAP Edge Services

SAP Edge Services Business Essential Functions Service - Configuration Guide Version 3.0 FP01

BUSINESS ESSENTIAL FUNCTIONS SERVICE - CONFIGURATION GUIDE Public

2

Table of Contents 1 ABOUT THIS DOCUMENT ........................................................................................................................... 5 1.1 Glossary ......................................................................................................................................... 5

2 SOLUTION OVERVIEW ................................................................................................................................. 9 2.1 Edge Synchronization ................................................................................................................................ 9 2.2 Prerequisites ....................................................................................................................................... 10 2.3 Implementation and Configuration – Basic Settings ............................................................................ 12 2.3.1 SAP SQL Anywhere Database................................................................................................................ 12 2.4 Setting Up MobiLink Server .................................................................................................................... 13 2.4.1 Generating MobiLink System Objects ..................................................................................................... 13 2.4.2 Synchronizing MobiLink Step-by-Step .................................................................................................... 13

3 SAP ERP CONFIGURATION ...................................................................................................................... 18 3.1 Project Administration ............................................................................................................................. 18

4 SET-UP REQUIREMENTS .......................................................................................................................... 18

5 SAP ADD-ON CONFIGURATION ............................................................................................................... 18 5.1 Overview ....................................................................................................................................... 18

6 GENERAL CONFIGURATION ..................................................................................................................... 18 6.1 SAP Work Manager .................................................................................................................................. 18 6.1.1 Activate BCSET (SCPR20) ..................................................................................................................... 18 6.1.2 Create PMBATCH user in SAP ERP ...................................................................................................... 20 6.1.3 Create PMBATCH user for Agentry and SAP ERP................................................................................. 20 6.1.4 Configure Agentry System Technical setting .......................................................................................... 22 6.2 Configuration Tables ............................................................................................................................... 23

7 CONFIGURATION FOR SYNC JOBS ........................................................................................................ 24 7.1 Configure Background RFC Queue ........................................................................................................ 24 7.1.1 Assign the SAP ERP instance to an RFC Server Group ........................................................................ 24 7.1.2 Create an RFC (Logical) Destination ...................................................................................................... 25 7.1.3 Create an RFC Inbound Destination ....................................................................................................... 28 7.1.4 Create Supervisor Destination Define EBEF_LOCAL as a supervisor destination. ............................... 31

8 PLANT SPECIFIC CONFIGURATION OVERVIEW .................................................................................... 32 8.1 Equipment Classification set-up............................................................................................................. 43

9 WORK ORDER CONFIGURATION ............................................................................................................. 46 9.1 Create PM Order type ZM01 .................................................................................................................... 46 9.2 Assign Order type ZM01 to EBEF MTCE Plants .................................................................................... 48 9.3 Create External Number Range – Add to Group ................................................................................... 49 9.4 Maintain User Status Profile .................................................................................................................... 52 9.5 Create Control Keys EXT2 and ZINT ...................................................................................................... 54 9.6 Maintain Default Control Key Order Type ZM01 .................................................................................... 56 9.7 Create Activity Type for ZM01 Orders .................................................................................................... 58 9.8 Assign Maintenance Activity Types to Order Type ZM01 .................................................................... 59 9.9 Maintain Default Activity Type for Order Type ZM01 ............................................................................ 60 9.10 Configure Automatic Notification Creation During Work Order Creation ........................................ 61 9.11 Define Control Parameters for Completion Confirmations ................................................................ 62

10 PURCHASE REQUISITION SPECIFIC CONFIGURATION...................................................................... 65 10.1 Enhance CI_EBANDB and CI_EBANDBX Structures ......................................................................... 65


3

10.2 Add Components to Structure CI_EBANDBX ..................................................................................... 69 10.2.1 APPEND STRUCTURE CI_EBANDBX to table EBAN ......................................................................... 71 10.3 Implement BADI /EBEF/BADI_MM_PREQ_NUM_LC ........................................................................... 71 10.4 Change Purchase Requisition Order Type .......................................................................................... 78 10.5 Change Purchase Group ....................................................................................................................... 79

11 CONFIGURATION OF FILE TRANSFER ................................................................................................. 81 11.1 Configure Attachment File Transfer Settings ...................................................................................... 81 11.1.1 Configure Reports Management Settings ............................................................................................. 85 11.1.2 Create the Subdirectories on the SAP ERP server ............................................................................... 86 11.1.3 Define the directories in SAP ERP ........................................................................................................ 87

12 CONFIGURATION OF WEB DYNPRO SERVICE .................................................................................... 87

13 RUN INITIAL LOAD ................................................................................................................................... 89 13.1.1 Data Tables - Initial Load ...................................................................................................................... 89 13.1.2 Complex Tables – Initial Load ............................................................................................................... 95 13.1.3 Object Tables – Initial Load ................................................................................................................. 102

14 SET VARIANTS USED FOR BACKGROUND JOBS ............................................................................. 108 14.1 Variant DT ..................................................................................................................................... 108 14.2 Variant CT ..................................................................................................................................... 110 14.3 Variant OBJ ..................................................................................................................................... 111 14.4 Variant Standard ................................................................................................................................... 113 14.5 Variant /EBEF/HOURLY ....................................................................................................................... 115 14.6 Variant /EBEF/DAILY ............................................................................................................................ 117 14.7 Variant /EBEF/MONTHLY ..................................................................................................................... 120 14.8 Variant /EBEF/YEARLY ........................................................................................................................ 121 14.9 Variant /EBEF/ONDEMAND ................................................................................................................. 121 14.10 Variant UPLOADATTACH .................................................................................................................. 122 14.11 Variant DWNATTACH_EBEF ............................................................................................................. 123 14.12 Variant GET_MDKE ............................................................................................................................ 124

15 DOCUMENTATION OF BACKGROUND JOBS ..................................................................................... 125 15.1 /EBEF/GET_DT – Get Data Tables (3.1.2.1) ........................................................................................ 126 15.2 /EBEF/GET_CT - Get Complex Tables ................................................................................................ 131 15.3 /EBEF/GET_OBJ - Get Object Tables ................................................................................................. 133 15.4 /EBEF/TRN - Process Uploaded Transactions .................................................................................. 135 15.5 /EBEF/HOURLY_REPORTS ................................................................................................................. 137 15.5.1 /EBEF/DAILY_REPORTS ................................................................................................................... 138 15.6 /EBEF/MONTHLY_REPORTS............................................................................................................... 138 15.7 /EBEF/YEARLY_REPORTS .................................................................................................................. 138 15.8 /EBEF/ONDEMAND_REPORTS ........................................................................................................... 138 15.9 /EBEF/ATTACHMENTS_UP ................................................................................................................. 138 15.10 /EBEF/ATTACHMENTS_DOWN ......................................................................................................... 139 15.11 /EBEF/GET_MDKE .............................................................................................................................. 139 15.12 Schedule parameters for maintenance orders ................................................................................ 139

16 SECURITY INFORMATION ..................................................................................................................... 141 16.1 Authorization Concept ......................................................................................................................... 142 16.1.1 Roles ..................................................................................................................................... 142 16.1.2 Mapping Remote Location Users with Roles ...................................................................................... 143 16.2 Data Privacy and Protection ................................................................................................................ 146 16.3 Security-Relevant Logging and Tracing ............................................................................................ 146


4

16.4 LDAP Setup ..................................................................................................................................... 146

17 APPLYING SQL PATCHES TO THE DATABASE ................................................................................. 148

18 MULTI-LANGUAGE SUPPORT .............................................................................................................. 153

APPENDIX A: SCANNING ATTACHMENTS FOR MALWARE ................................................................... 154

APPENDIX B: RESTARTING THE DATABASE SERVER AND MOBILINK CLIENT ON LINUX .............. 155

APPENDIX C: DATA PRIVACY AND PROTECTION CONFIGURATION ................................................... 158

APPENDIX D: AIN CLOUD INTEGRATION AT THE EDGE SERVICES (ES) CORE ................................. 162 Setup the Cloud integrator ........................................................................................................................... 163 Configuration at the Edge ............................................................................................................................ 164

APPENDIX E: UI DEPLOYMENT FROM THE DIGITAL CORE ................................................................... 166 Setup at the Digital Core ............................................................................................................................... 166 Loading Library for synchronization ........................................................................................................... 167 Setup at the Edge .......................................................................................................................................... 167


5

ABOUT THIS DOCUMENT

This configuration guide provides a central starting point for the technical implementation and configuration of the Business Essential Functions Service in the solution. It describes all activities necessary for implementation and configuration of components that perform integration with, In the case of using SAP EDGE SERVICES, cloud edition

- the SAP ERP or SAP S/4HANA system In the case of using SAP EDGE SERVICES, on premise edition

- the SAP ERP system only This is not an installation document. Refer to the appropriate installation notes for instructions about installing the underlying components. This document is intended for the following target audiences:

• Consultants

• Partners

• Customers Glossary

Term Abbreviation Definition

Agentry The installation components SMERP 620_700 and SMFND 620_700 are the Agentry SAP Framework ERP Add-On and Integration Foundation.

Bill of Material BOM A list of parts grouped together for one piece of equipment, configured in SAP ERP.

Complex Table CT Master data staging table; data in these tables is common to all edge or remote locations.

Component The raw material, part, or subassembly that goes into a higher-level assembly. Example: A part is entered as a component.

Plant (Plant Data) A Plant in SAP ECC is an operating area or branch within a company. In this solution, Plant Data is synchronized to and from the Edge.

Equipment Master Master data that describes an individual piece of equipment.

Goods Issue GI A withdrawal from warehouse stock, such as in the issue of materials to a work order.

Goods Receipt GR An addition to warehouse stock, such as goods received from external vendors or from in-plant production.


6

Hypertext Markup Language

HTML HTML is the language your browser understands. It's a standardized system for tagging text files to achieve font, color, graphic, and hyperlink effects on World Wide Web pages.

Inter-Plant Transfer The transfer of materials from one plant or remote location to another and the resulting goods movement.

Lightweight Directory Access Protocol

LDAP A software protocol for enabling anyone to locate organizations, individuals, and other resources such as files and devices in a network.

Local Area Network

LAN Computer network that interconnects computers within a limited area.

Material Goods that are manufactured or purchased, such as a part used for repair. They are identified by their unique Material Number.

Material Document Evidence of one or more material movements, providing information for downstream applications. For example, a record of an issuing of goods(materials) from a stock location to a work order.

Measuring Point Measuring points in the SAP System describe the physical and/or logical locations at which a condition is described, (for example, the coolant temperature in a nuclear power station after the coolant has left the pressure vessel, or the number of revolutions at a rotor shaft of a wind-driven power plant).

MobiLink MobiLink is a component of SAP SQL Anywhere that allows reliable and efficient two-way synchronization of data.

Maintenance Notification

Describe malfunctions or exceptional technical situations at an object in the area of maintenance processing, request the maintenance department to perform a necessary task, and document the work that has been performed.

Operation A task that instructs the user doing the work order. Example: Inspect exhaust system.

Physical Inventory PI Counting material at a specific point in time. The counted quantity of a material for each storage location is contained in a physical inventory document.


7

Plant Maintenance PM The measures taken to keep a facility operating efficiently. Also, the module of SAP ERP that manages these measures.

Purchase Order PO A request from a buyer to a seller to deliver a specified quantity of material, or perform a specified service, at a specified price within a specified time.

Purchase Requisition

PR A document which defines the needs for a good or service and contains details of the purchase to be made.

SAP SQL Anywhere

A proprietary relational database management system (RDBMS) product from SAP. It includes the MobiLink client and web server.

SAP Work Manager

SMERP SMFND

The components SMERP and SMFND are the ABAP add-ons from SAP Work Manager that are used in this solution.

Service Entry Sheet

SES An invoice for services provided by a third party. Example: Purchase service such as sanding or welding.

Stock Goods or materials in inventory.

Work Order WO The entity containing the work to be done for maintenance and repair of equipment.

Important SAP Notes

Recommendation

Read the SAP Notes below before you start implementing the software. The SAP Notes contain the latest information about the installation as well as corrections to the installation information. Also make sure that you have the most current version of each SAP Note, which is available on SAP Support Portal at http://support.sap.com/notes.

SAP Note Number

Title Description

2516741 Release strategy for the ABAP add-on EBEF 300

In the case of Customers using either SAP EDGE SERVICES, cloud edition or on premise edition, there is the option of integrating with only SAP ERP 6.0 back end system. This note applies in such a case.

http://support.sap.com/notes


8

2567806 Release strategy for the ABAP add-on S4EF 300

In the case of Customers using SAP EDGE SERVICES, cloud edition, there is the option of integrating with S/4HANA back end system. This note applies in such a case.

2531316 Release strategy for non-ABAP components of the Product “SAP EDGE SERVICES 3.0”

In the case of Customers using SAP EDGE SERVICES, on premise edition, this note gives overview of the downloadable non-ABAP components

2486514 Vendor fetch BAPI does not populate the deleted list.

You're fetching the list of vendors via the function module /SMERP/MM_CTVENDOR_GET or /SYCLO/MM_CTVENDOR_GET, the return table ET_EXCHANGE_ACTION_DELETED is empty when a vendor has been deleted, marked for deletion, blocked from posting, or blocked from purhcasing in the backend.


9

SOLUTION OVERVIEW

Business Essential Functions Service provides uninterrupted SAP functionality anywhere, anytime. It is always available, and provides LAN-based speed whether it's connected or disconnected to the SAP ERP. Now, the distributed locations of a company can run 24x7 at the edge, and are continuously synchronized, regardless of connectivity method. Business Essential Functions Service consists of the following components:

• SAP ERP integration

• Synchronization server

• Edge database and edge web server The architecture consists of a database server running on the edge (remote site) as a distributed data store (remote database). Through staging tables in a central consolidated database, functionality is extended in the areas of:

• Plant Maintenance

• Inventory Management

• Materials Management ABAP programs execute in regularly scheduled jobs to populate the exchange or staging tables. The data in the staging tables in SAP ERP is synchronized with data in the edge databases, using the synchronization server. Applications at the edge location can use web services that interact with data in the edge database. Edge Synchronization Synchronization is initiated by the edge database server. Changes are uploaded to the synchronization server through the network layer. Conflicts that result from the upload are resolved at the central SAP ERP database. Changes in SAP ERP data are then downloaded to the edge database server. The synchronization server can operate in a single or multi-tiered distributed architecture. The synchronization server uses internal system tables to keep track of the synchronization progress of users. This information is kept both at the edge database and the consolidated SAP ERP database. The synchronization client keeps track of the transaction log progress and the last successful synchronization timestamp to ensure that the next synchronization of a user is in step. During upload processing, the synchronization server ensures all or nothing updates at the consolidated database. In other words, the synchronization server rolls back all transactions for the current upload if anything fails during the upload process. During the download, the synchronization client operates in the same fashion to ensure all or nothing updates at the edge. The synchronization client guarantees transaction integrity by synchronizing only committed transactions. The synchronization client picks up committed transactions by scanning the transaction log. If solution data is not properly scoped under database transactions, then the synchronization can leave the consolidated database in an inconsistent state.


10

System and Application Landscape

Recommendation

For performance, scalability, high availability, and security reasons, we strongly recommend that a minimal system landscape be used as the productive landscape. For more information about creating productive system landscapes, see SAP Service Marketplace at https://service.sap.com. The system landscape consists of local PCs connecting to the SAP SQL Anywhere 17.0 database server that resides on a LAN at the remote location. The SAP SQL Anywhere 17.0 server also functions as a web server and has a MobiLink connector agent.

Landscape Components

The following form the basis of Business Essential Functions Service:

• SAP ERP

The MobiLink synchronization server uploads the data from the edge database and places the data in the transaction tables of the EBEF staging tables.

The synchronization framework processes the uploaded transactions from the transaction tables, then updates SAP ERP data, subsequently updating the object tables, via the delta BAPI wrappers.

• Headquarters

The technical user (for example, mlsyncuser) must have full access rights to the SAP\RIGS folder to

read and write attachments and reports.

• Network

TCP port 5555 must be open between the application server and the MobiLink server.

Prerequisites The software prerequisites for using Business Essential Functions Service include:

Software Version

SAP ERP 6.0 EHP7 or above

SAP Work Manager components SMERP 620_700, plus support packages; SMFND 620_700, plus support packages

SQL Anywhere with MobiLink client (part of EDGE DB 3.0 download for the product)

On Windows: 17.0.8.4003 or above On Linux: 17.0.8.4003 or above

MobiLink server (part of SYNC SERVER 3.0 download for the product)

On Windows: 17.0.8.4003 or above On Linux: 17.0.8.4003 or above

One of the following database options is also required:

Database Option Version

Microsoft SQL Server Server 2008 or above

https://service.sap.com/


11

Oracle Database 11g or above (also requires Oracle JDK 1.6 or above)

HANA 1.95 or above (also requires HANA Client and HANA Real-Time Replication)


12

Implementation and Configuration – Basic Settings This configuration guide contains the information necessary to configure the SAP system to meet customer requirements. The SAP ERP configuration is done in the implementation guide (IMG; transaction SPRO). It

covers all steps of the implementation process as well as the SAP standard (factory) customizing settings and the system configuration activities. The customizing activities and their documentation are structured from a functional perspective. Installation:

• Install SAP add-ons (SMFND and SMERP) on SAP ERP, and activate permissions. Please refer to SAP Note 2516741 for more information. - SMFND:

o Initial - K-620AGINSMFND.SAR

o All service packs o Files can be found on the SAP EDGE SERVICES OP (SUPPORT PACKAGES AND

PATCHES) downloads page at SMFND 620_700 SUPPORT PACKAGES

- SMERP

o Initial - K-620AGISMERP.SAR


PATCHES) downloads page at SMERP 620_700 SUPPORT PACKAGES

- EBEF300 o Initial - K-300AGINEBEF.SAR


PATCHES) downloads page

• Install MobiLink software (SAP SQL Anywhere 17.0) on the ML synchronization server. Files can be found on the SAP EDGE SERVICES OP (SUPPORT PACKAGES AND PATCHES) downloads page in the SYNC SERVER folder. - If installed on Windows machineQ

o Select the appropriate platform from the dropdown menu and download the .zip file o Run .msi file that is in the .zip file to install MobiLink Server, SQL Anywhere and tools

- If Installed on Linux machine o Select the appropriate platform from the dropdown menu and download the .zip file o Extract to target directory to install MobiLink Server, SQL Anywhere and tools

• Install MobiLink server scripts and configuration on the ML synchronization server. Files can be found on the SAP EDGE SERVICES OP (SUPPORT PACKAGES AND PATCHES) downloads page in the EDGE BUSESSENTIAL SYNC folder by selecting the appropriate database type from the dropdown.

SAP SQL Anywhere Database The SAP SQL Anywhere database is also known as the MobiLink client database. There are a number of technical components in the SAP SQL Anywhere relational database:

• The schema that extends from the staging tables of SAP ERP via MobiLink synchronization. It holds the data to be used by the client application.

• The relational database, which is running as a Windows service

• SAP SQL Anywhere 17.0.8 is configured and run as a standard database connectivity and HTTP service, which acts as a web server


13

• Install SAP SQL Anywhere 17.0.8 on the client system. Files can be found on the SAP EDGE SERVICES OP (SUPPORT PACKAGES AND PATCHES) downloads page in the EDGE DB folder. Make sure to select the appropriate platform for the target system from the dropdown.

Relational database objects used:

• Stored procedures that extend the data as retrieval API

• Stored procedures that accept data and store the data into the relational database

• Web Service to extend the stored procedures

• Events to process background actions such as file transfers

• Synchronization running as a service For more information about SAP SQL Anywhere 17.0.8 and MobiLink synchronization, see: http://dcx.sap.com/index.html#sqla170/en/html/36323b3ab0c2475bb6ccb140c411aa8a.html Many installation and configuration possibilities are supported, and we strongly recommend that you perform a proper analysis of the best options before beginning your installation. Setting Up MobiLink Server Generating MobiLink System Objects The MobiLink system objects are provided with your SAP SQL Anywhere installation in the folder <SQL

Anywhere installation>\MobiLink\Setup. The files syncxxx.sql are required for the SAP ERP database

to set up MobiLink.

Relation Database Management System (RDBMS) used as SAP ERP database (consolidated database)

File in setup folder

Microsoft SQL Server Syncmss.sql

Oracle Syncora.sql

HANA Synchana.sql

MobiLink synchronization uses:

• Synchronization scripts, which are called by synchronization events.

• Synchronization stored procedures, which are invoked by synchronization scripts to process the uploads and downloads between remote sites and SAP ERP.

• File share mounted by MobiLink synchronization, which handles uploading and downloading non-relational objects such as reports and attachments. The file share is also used as a deployment database file transfer.

Synchronizing MobiLink Step-by-Step

Prerequisites

• Install Java JDK 1.6 or higher

• Install Apache ANT 1.9 or higher

• Downloaded ML synchronization scripts (See install section above)

Setting up HANA (RDSync, HANA only)

http://dcx.sap.com/index.html#sqla170/en/html/36323b3ab0c2475bb6ccb140c411aa8a.html


14

Set up the ODBC (Open Database Connectivity) connection for RDSync:

o install the HANA client o set the ODBC data source using HDBODBC version 1.00.09.00 or higher from HANA client.

Establish proper credentials for the SAP ERP database to be used by RDSync.

Create user ML_SYSTEM. Any user with USER ADMIN privileges can create the ML_SYSTEM user. o ML_SYSTEM must have the SELECT, UPDATE, INSERT, DELETE privileges for all the objects

within the namespace /EBEF/*.

Move the contents of the ml_hana folder (downloaded above) to a temporary folder. Don’t nest the folder too

deep. For example, your folder structure may look like the following, where : o C:\SAAP_ML_HANA-<version>\mobilink_hana (this filepath will be represented below by

$ML_FOLDER$) Configure the build script to point to the SAP ERP database. Change the consolidated host/port/uid/pwd in the build.xml file to point at the SAP ERP server.

- cons.host (localhost) - cons.port - cons.uid = ML_SYSTEM - cons.pwd = <ML_SYSTEM password> Note: Replace all "a0a" with your SAP ERP system ID, such as "PRD".

Setting up MobiLink Server (MSSQL Server only)

MobiLink server software (SAP SQL Anywhere 17.0) is installed (downloaded above). Set up the ODBC (Open Database Connectivity) connection for MobiLink:

o set the ODBC data source using MSSQL Native client (install the MSSQL client first). Establish proper credentials for the SAP ERP database to be used by MobiLink.

a) Create a schema from the MobiLink system. This is where the MobiLink system object resides: - CREATE SCHEMA ML_SYSTEM

b) Create a technical user to start MobiLink. o CREATE LOGIN <technical user> WITH PASSWORD ='<password>', DEFAULT_DATABASE =

<database instance> o CREATE USER <technical user> FOR LOGIN <technical user> o EXEC sp_addrolemember 'db_owner', ‘<technical user>' o GRANT VIEW SERVER STATE TO <technical user> o ALTER USER <technical user> WITH DEFAULT_SCHEMA = ML_SYSTEM

Move the contents of the ml_mssql folder (downloaded above) to a temporary folder. Don’t nest the folder

too deep. For example, your folder structure may look like the following: o C:\SAAP_ML_MSSQL-<version>\mobilink_mssql (this filepath will be represented below by


- cons.host - cons.port - cons.uid = <technical user>


15

- cons.pwd = <technical user password>

Setting up MobiLink Server (Oracle)

MobiLink server software (SAP SQL Anywhere 17.0) is installed (downloaded above). Set up the ODBC (Open Database Connectivity) connection for MobiLink:

o set the ODBC data source using the SQL Anywhere Oracle driver (install the Oracle Admin client first).

Establish proper credentials for the SAP ERP database to be used by MobiLink.

1. Create two technical users to serve as schema (ML_SYSTEM as acts as a technical user that starts MobiLink).

o ML_SYSTEM - schema contains all the MobiLink system objects that come with the standard MobiLink product

o ML_R1 - schema contains all the MobiLink synchronization logics that are related to this solution 2. Assign proper privileges to the technical users: o GRANT SELECT ON V_$TRANSACTION TO ML_SYSTEM; o GRANT SELECT ON V_$SESSION TO ML_SYSTEM; o GRANT SELECT ON GV_$TRANSACTION TO ML_SYSTEM (for Oracle grid computing); o GRANT SELECT ON GV_$SESSION TO ML_SYSTEM (for Oracle grid computing); o GRANT SELECT ON V_$TRANSACTION TO ML_R1; o GRANT SELECT ON V_$SESSION TO ML_R1; o GRANT SELECT ON GV_$TRANSACTION TO ML_R1 (for Oracle grid computing); o GRANT SELECT ON GV_$SESSION TO ML_R1 (for Oracle grid computing); o GRANT RESOURCE TO ML_SYSTEM; o GRANT CREATE VIEW TO ML_SYSTEM; o GRANT CREATE SYNONYM TO ML_SYSTEM; o GRANT RESOURCE TO ML_R1; o GRANT CREATE VIEW TO ML_R1; o GRANT CREATE SYNONYM TO ML_R1

3. Grant all /EBEF/ table objects (individually) to ML_SYSTEM and ML_R1 the SQL script in the zip $ML_FOLDER$\cons\sql\grant\application_table_grant.sql.

Move then contents of the ml_oracle folder (downloaded above) to a temporary folder. Don’t nest the folder

too deep. For example, your folder structure may look like the following: o C:\SAAP_ML_ORACLE-<version>\mobilink_oracle (this filepath will be represented below by


- cons.host - cons.port - cons.ml.uid = ML_SYSTEM - cons.ml.pwd = <ML_SYSTEM password> - cons.ml.sync.uid = ML_SYSTEM - cons.ml.sync.pwd = <ML_SYSTEM password> - cons.ml.code.uid = ML_R1 - cons.ml.code.pwd = <ML_R1 password> Note: You can obtain the host and port number for the system ID from the tnsnames.ora file on the

MobiLink server.


16

Setting up MobiLink Server (all databases)

Install MobiLink system tables in the SAP ERP database using the ML_SYSTEM user.

o Use Apache Ant to run the target install_consolidated_ml. It is in the same folder as the

build.xml file.

Set up a file share to be used by the MobiLink server for file upload and download. This file share is used by MobiLink to transfer files between the client and MobiLink, and between MobiLink and SAP ERP. The file share is also used by SAP ERP for files and reports to be synchronized to the remote site.

o Create the file share as part of the ABAP setup. o Create the necessary file shares on the share drive. The file share defined on the SAP ERP server

must be mounted as a share by MobiLink server, and must be at least two levels deep, for example, C:\MobiLink_fileshare. The attachment folder must be created in C:\MobiLink_fileshare. MobiLink must mount C:\MobiLink_fileshare\XXX as its upload and download folder. A read/write permission should be extended to the MobiLink service. o For the attachment folders (ATTS_BUS2007, ATTS_BUS2012, ATTS_BUS2091,

ATTS_BUS2105) o For the report folder o For the template database folder

Create the MobiLink Server service by modifying and running the ExampleCreateMLService.bat file, which

is located in $ML_FOLDER$\cons\bin. Make sure you have the correct DSN (data source name),

synchronization user ID, password, port, MobiLink installation folder, and so on. The port number should be the port that the MobiLink server is listening on (usually 5555). The file share in the service should reflect the mounted share above. To start the MobiLink service, add command dbsvc -u DEPML to the command file.

Modify the Edge Configuration Settings file.

a) Extract the SQL.zip from the business_essential_service_backend.zip folder downloaded

above, into a temporary folder. For example, the folder may look like the following: a. C:\EDGE BUSESSENTIAL SQL-3.0.0\sqlanywhere. (this filepath will be represented below

by $SQL_FOLDER$)

S/4HANA specific instruction modification.

a) In the case where S/4HANA integration is being used in the implementation, make the following modification:

a. Rename the publication.sql file in the sql\common folder to publication_old.sql.

b. Rename publication_s4.sql to publication.sql.

Generate MobiLink synchronization logic.

a) Generate the reference database o Run ant schema –DsyncUser=ref from the command line under the directory path

$SQL_FOLDER$.

b) Configure SyncObjectGenerator file under folder $ML_FOLDER$.

o Under the folder $ML_FOLDER$util\SyncObjectGenerator modify build.xml:

- Modify the target “generate” to change the –C switch for the SAP client number, for example: - <arg value="-C" /> - <arg value="200" /> - Modify the –S switch to specify the schema for the SAP ERP tables, for example:


17

- <arg value="-S" /> - <arg value="SAPERP" />

c) Generate synchronization logic by running ANT from the command line in $ML_FOLDER$\util\SyncObjectGenerator (this runs the default target).

Install MobiLink support tables by running the following under directory $ML_FOLDER$:

o ANT install_sync_support_schema Install synchronization logic under directory $ML_FOLDER$:

o ANT build_sync_logic Generate a template database:

1. Set up a template user mapping in the SYNC_USER_MAPPING table in the consolidated or SAP ERP

database. o Connect to the database and add the following SQL:

- INSERT INTO SYNC_USER_MAPPING VALUES; o Add SSL certificates to the $SQL_FOLDER$/certificate folder

- Certificates must be in pem format - If a signed production certificate is not available, a self-signed certificate can be generated with

the createcert utility (refer to the SQL Anywhere 17 documentation for more about createcert) o Within $SQL_FOLDER$, modify the following variables in the file build.properties

- Location of the MobiLink server, for example: - ml.host=<my_mobilink_server_host> - ml.port =<mobilink_port_setup_previously> - Location of the file share to store the transfer file, for example: - ml.ftr_share=/myfileshare/SAP/RIGS - Filename, and passkey of SSL certificate for HTTPS requests to the edge database - rem.db.cert.file=<certificate_filename> - rem.db.cert.pass=<certificate_passkey> - Database encryption key - rem.db.encryption.key=<encryption_key>

Generate a template database to be downloaded to the folder RIG_XXXX for each RIG under the folder $SQL_FOLDER$ by doing the following:

o Generate an empty remote database. o Make sure the following is correct: rem.db.rootDir=${ml.ftr_share}

- ANT –DsyncUser=RIG_XXXX where XXXX is the plant number (specifically SAP ERP field WERKS)

o Populate the remote database by performing an initial sync: - Go to the $SQL_FOLDER$\bin folder and modify the scheduled_template_sync.cmd

(scheduled_template_sync_linux.cmd for deploying to linux machines) command file to

point to the proper plant template database. For example, if the plant number is 0101: - REM template 0101 - dbmlsync -c "dsn=DEP_RCS_rem_RIG_0101;uid=saap;pwd=sql123" -x -qc -os 4M -o "c:\MobiLink\logs\dbmlsync_log_RIG_0101" - dbstop -c "dsn=DEP_RCS_rem_RIG_0101;uid=saap;pwd=sql123" - In the same file change the ml_ftr_share property to point to the proper fileshare location, the line should look like the following: - SET ml_ftr_share=\\server555.sap.corp\MobiLink_Fileshare\DEP\RIG_0101\ - In the same file set the rem_host_name to the host name of the remote site and set rem_root_dir to the file path of the root directory being used - Run the batch and pass in the sync user as the only argument to the batch script - e.g. scheduled_template_sync.cmd 0101


18

SAP ERP CONFIGURATION

Project Administration This solution implementation can either be documented in a separate project or embedded in an existing implementation project. The language must be English. Documents to be uploaded into SAP Solution Manager must use a common readable format (PDF is recommended). SET-UP REQUIREMENTS

There are a few things that need to be in-place to complete the backend configuration - Install SMFND and SMERP components on the SAP ERP system - The user making the changes must have the following SAP ERP authorizations (to create users in

Agentry):

Authorization Object Field Value

S_ICF ICF_FIELD SERVICE

S_ICF ICF_VALUE SYCLOADM

S_TCODE TCD /EBEF/*

S_TCODE TCD /SYCLO/*

SAP ADD-ON CONFIGURATION

Overview The implementation requires some customer-specific configuration in SAP ERP. Install SMFND and SMERP components on the SAP ERP system. Two components from SAP Work Manager and SAP Inventory Manager are utilized. There are configuration tables that are specific to the solution: /EBEF/CONF_SYNC, /EBEF/CONF_SYNCP,

/EBEF/CONF_SYNCM, /EBEF/LOCALUSER, /EBEF/S_ROLES and /EBEF/A_DEF. Maintain these tables using

transaction SM30.

You must also configure the file transfer that occurs for attachments, both to and from remote sites. Finally, define background jobs to control the synchronization process using transaction SM36.

GENERAL CONFIGURATION

SAP Work Manager Activate BCSET (SCPR20) Activate the specific Work Manager Component. This is the component that all the following changes will be made on.

1. Go to SCPR20

2. Enter /EBEF/WORK_MANAGER_53 into the BCSET field


19

3. Click the ‘Activate BC Set’ icon to activate the BCSET

4. Copy Variable field values (click ‘Copy Values’) (if pop-up appears)

5. Click ‘Execute’ on the next pop-up (to overwrite data)


20

6. A message should appear saying ‘Activation Successfully completed’

Create PMBATCH user in SAP ERP Create users in SAP ERP via transaction SU01. Create user PMBATCH as a communication user who has

authorization to execute batch jobs. Make sure to create users with roles according to their responsibilities so that business transactions submitted by each user are processed correctly in the batch jobs. For example, users who submit edits to work orders should have roles that allow them to edit work orders for the appropriate plant and work order types.

1. Go to transaction SU01

2. Enter the user PMBATCH and click the ‘Create’ icon 3. Assign permissions to the PMBATCH user so that they can execute batch jobs

Create PMBATCH user for Agentry and SAP ERP For data synchronization to operate, create the PMBATCH user in the Agentry system for both the SAP Work Manager and SAP Inventory Manager solutions. Use the transaction /SYCLO/ADMIN.

The following SAP ERP authorizations are required to create users in Agentry:

Authorization Object Field Value

S_ICF ICF_FIELD SERVICE

S_ICF ICF_VALUE SYCLOADM

S_TCODE TCD /EBEF/*

S_TCODE TCD /SYCLO/*

The first user you need to set up in Agentry is the batch user PMBATCH, which runs batch jobs in SAP ERP.

2.

1. Go to /n/syclo/admin and login


21

2. In the System Administration & Monitoring Portal select Administration → User Management and click ‘Create’

3. Fill in details for PMBATCH, work manager user and Save

Mobile Application: User Name:

Middleware License No: Device User ID:

EBEF Work Manager 5.3.0 PMBATCH SAP_WORK_MANAGER_53 PMBATCH

4. Create another user – PMBATCH for Inventory manager and Save

Mobile Application: User Name:

Middleware License No: Device User ID:

EBEF Inventory Manager 3.2.0 PMBATCH SAP_INVENTORY_MANAGER_32 PMBATCH


22

Configure Agentry System Technical setting Next, maintain the technical settings in the Agentry configuration panel.

1. Go to transaction /n/syclo/configpanel

2. In Agentry SAP Framework Configuration, go to Technical Settings. 3. The Technical Settings Detail screen should already be populated; if it is not, click Add, then

save the screen with the information that appears in the fields. 4. Click ‘Change’, edit the fields and click ‘Save’

5. A confirmation of the save appears:


23

Configuration Tables There are a number of configuration tables. Some tables have existing entries; others require customer-specific modifications. Access these tables through transaction SM30 or through a customer-specific

transaction. - Maintain remote plant synchronization master (/EBEF/CONF_SYNC) - this table should already be set up

with all the valid settings for the solution. If you do need to modify it, or view its entries, use transaction /EBEF/CONF_SYNC.

- Maintain remote plant synchronization - BAPI Wrapper Parameters (/EBEF/CONF_SYNCP) - this table

should already be set up with all the valid settings for the solution. If you do need to modify it, or view its entries, use transaction /EBEF/CONF_SYNC.

- Maintain remote plant synchronization of parameter mapping (/EBEF/CONF_SYNCM) - you should need

to modify this table only for a few default values, as specified in this document. Do not modify any other values, as they are the valid settings for the solution. To view the entries, use transaction /EBEF/CONF_SYNCM.

- Maintain roles and security (/EBEF/S_ROLES) - this table specifies the system functionality that can be

performed by each customer-defined role or work center. (Note work centers for the client functionality are not the same as SAP ERP work centers). Typically, a role will perform only portions of a business process. For example, an electrician role or work center may not have the ability to create work orders and add components. A specific implementation can utilize this table to govern access to certain features in a user interface. Maintain the table using transaction /EBEF/ROLES.

- Maintain Remote Site Users (/EBEF/LOCALUSER) - this table has a link between front-end user names

and back-end user names. It also has a link to the role assigned to the user (see table /EBEF/S_ROLES). Maintain the table using transaction /EBEF/LOCALUSER.

- Maintain Directory for Attachment File Transfer (/EBEF/A_DEF) - this table includes the directory and

subdirectory locations for the folder used to transfer attachments between SAP ERP and remote sites. Maintain the table using transaction /EBEF/DEF.

- Maintain Syclo GUID (/syclo/mdw00) for back-end batch user (such as PMBATCH) - this table provides

a GUID for each back-end user, which is used for remote site users (/EBEF/LOCALUSER). The GUID

is required for some transactions, such as approvals, to run correctly. In addition, before you set up batch jobs, you must also generate a valid GUID for the batch user ID PMBATCH. Maintain this table using transaction /syclo/admin and selecting User Management.


24

CONFIGURATION FOR SYNC JOBS

For synchronization jobs to execute properly, you must configure the following components Configure Background RFC Queue Assign the SAP ERP instance to an RFC Server Group

1. Go to transaction rz12

2. Assign the SAP ERP instance to a new RFC Server group

i. Click the ‘Create’ icon to create a new RFC Server Group

ii. Select the server group and enter a name for the Instance. Then click ‘Copy’ to add

the instance to the list 1. The logon group can be named based on company preferences. 2. The instance name is typically the concatenation of the server name, system

ID, and instance number (for example, USCHI3100_PRD_00).


25

iii. The instance should be added to the list. Make sure the status indicator is green:

iv. Take note of the logon group for the ‘Create RFC Inbound Destination’ step

3. Assign the SAP ERP instance to a server group

Create an RFC (Logical) Destination Create an RFC destination to connect from the ABAP system to the external system

4. Go to transaction SM59 to define a logical destination

5. Select ‘Logical Connections’. If EBEF_LOCAL is not created click the ‘Create’ icon

6. Enter details and ‘Save’


26


27

7. Select ‘EBEF_LOCAL’ and click the ‘Edit’ icon (pencil). Select the ‘Logon & Security’ tab

8. Define the logon info for the logical destination, then click ‘Save’.


28

9. Navigate to the ‘Special Options’ tab and set the transfer protocol to ‘Classic with bgRFC’

10. Save the logical destination info.

Create an RFC Inbound Destination You must create the background RFC inbound destination in each system to run the synchronization batch job.

11. Go to transaction SBGRFCCONF


29

12. Select the ‘Define Inbound Destination’ tab and click the ‘Create’ icon

13. Enter in applicable details:

a. Define the Inb. Dest. Name as /EBEF/SYNC_INB_TRANS

b. Define the Logon/server group as the RFC server group created in transaction RZ12

c. In the Add Queue Prefix field enter /EBEF/SYNC, then click Add (to add the prefix)


30


31

d. Click Save on the popup. /EBEF/SYNC_INB_TRANS will be added to the list.

14. Save the bgRFC Configuration.

Create Supervisor Destination Define EBEF_LOCAL as a supervisor destination.

1. Go to transaction SBGRFCCONF to define a supervisor destination

2. Select the Define Supervisor Dest tab


32

3. Click the Create icon and set the Destination to the appropriate RFC connection. Enter in the PMBATCH user and password.

4. Click ‘Save’ to save the supervisor destination

PLANT SPECIFIC CONFIGURATION OVERVIEW

Groups work by maintenance plant, which must also be the same Plant ID as the materials management plant and the maintenance planning plant. An edge site is considered a single plant. The functional locations and equipment used at the edge site must be linked or extended to the edge plant. Define filters for the respective plant and order types that will be used We recommend that you consider filters for Equipment and Functional Location as well as the Planning Plant (Planning Plant instructions are below). Note: Make sure that the data filters do not exclude plants of interest. For example, if you are implementing maintenance for plant 1000, ensure the data filters are set to include data for maintenance plant 1000. You can learn about defining filters in the SAP Work Manager documentation. The solution does not currently use parameters, so you can set to inactive any filters using parameters.


33

1. Go to transaction /n/syclo/configpanel

2. Select ‘Mobile Data Object Configuration’ 3. Expand ‘CT – Complex Table’

4. Double Click /EBEF/SWM53_PM_PLANNING_PLANT to select it from the CT List

5. Go to the ‘Data Filter’ Tab and expand the ‘GET_PLANNING_PLANT’ section in ‘Defined Filters’


34

6. Click the PLANNING_PLANT filter and click the ‘Change’ icon at the top of the page to edit

7. Click the ‘Create’ icon to add a new rule (for planning plant) to the list. If there are already rules listed, ensure they are for the plants being used.

8. Change the following fields: DOF Rule Type: Static Value in Range Format Sign: Inclusive Option: = Low Value: <Plant Used> (in this case 1000)


35

High Value: only use if plants are in sequential order. If being used, enter the highest plant number here. Click ‘Create’ to add the plant to the list:


36

9. If the plants used are not sequential, each individual plant must be added to the list. To add another plant to the list, click ‘Create’

10. Enter the applicable details:

DOF Rule Type: Static Value in Range Format Sign: Inclusive Option: = Low Value: <Plant Used> (in this case 1000) High Value: only use if plants are in sequential order. If being used, enter the highest plant number here.


37

11. Repeat steps 9-10 for all plants that need to be added.


38

12. Once all plants are added, click ‘Save’ to save your changes.

13. Select /EBEF/SWM53_PLANNING_PLANT_ORD_TYPE from the CT list

14. Go to the ‘Data Filter’ table, expand the ‘Defined Filters’ section and open the PLANNING_PLANT


39

15. Click ‘Change’ to edit the data object.

16. ‘Create’ icon to add a new rule (for planning plant) to the list. If there are already rules listed, ensure

they are for the plants being used.

17. Change the following fields: DOF Rule Type: Static Value in Range Format Sign: Inclusive Option: = Low Value: <Plant Used> (in this case 1000) High Value: only use if plants are in sequential order. If being used, enter the highest plant number here. Click ‘Create’ to add the plant to the list:


40


41

18. If the plants used are not sequential, each individual plant must be added to the list. To add another plant to the list, click ‘Create’

19. Enter the applicable details:

DOF Rule Type: Static Value in Range Format Sign: Inclusive Option: = Low Value: <Plant Used> (in this case 1000) High Value: only use if plants are in sequential order. If being used, enter the highest plant number here.


42

20. Repeat steps 18-19 for all plants that need to be added.


43

21. Once all plants are added, click ‘Save’ to save your changes.

22. Click Save. Use the Same customizing/transport request as before (if prompted). Equipment Classification set-up If Equipment classification is not used (or synchronized), set the Equipment Classification details so it is not included in data updates.

23. Go to tcode /n/syclo/configpanel

24. Select Mobile Data object Configuration


44

25. From the Data Object Navigation Tree, select ‘DO-Standard Data Object’

26. Select /EBEF/SWM53_CLASSIFICATION_GENERIC


45

27. In the details, select the Data filter tab, and select ‘Filter-CLASSTYPE’ from the ‘Defined Filters’ section

28. Click the ‘Change’ button at the top of the screen to edit the filter

29. Edit the filter rules and Save changes.

DOF Rule Type: Static Value in Range Format Sign: Inclusive Option: = Low Value: ZZZ (this excludes all data for the initial and delta loads) Active Flag: <selected>


46

WORK ORDER CONFIGURATION

The solution must be able to create work orders that are external to SAP ERP, and upload and integrate them with plant maintenance. This requires a custom work order type that uses external numbering. The work orders are generally either for maintenance or for external services. There are also requirements for user status profile. The following list is an overview of the steps to be completed; you must complete the first two items first.

- Create Plant Maintenance (PM) order type ZM01 (copy of PM01) - Assign order type ZM01 to maintenance plants - Create and assign external numbering - Maintain user status profile - Create control keys EXT2 (copy of PM03) and ZINT (copy of PM01) - Maintain default control key for order type ZM01 - Create activity type for EBEF orders - Assign maintenance activity types to order type ZM01 - Maintain default activity type for order type ZM01 - Define control parameters for completion confirmations for order type ZM01

The setup for work orders is done primarily by customizing the ECC application (transaction SPRO). You may

also need to enter or change some Agentry parameters. Create PM Order type ZM01 Create order type ZM01 (a duplicate of PM01 order type). The ZM01 work order type is the order type used for work orders created on the remote site.

1. Go to SPRO (or transaction OIOA to skip steps 2 & 3)


47

2. Click ‘SAP Reference IMG’ 3. In the tree, navigate to Plant Maintenance and Customer service -> Maintenance and Service

Processing -> Maintenance and Service Orders -> Functions and Settings for Order types -> Configure Order Types

4. On the ‘Configure Order Types’ screen, select the PM01 item and click the ‘Copy As’ icon

5. Change the Order type to ‘ZM01’ and edit the description


48

6. Save Changes. (you may need a new transport request for this) ZM01 item will now display in the list.

Assign Order type ZM01 to EBEF MTCE Plants Assign the order type ZM01 to the Plants that are being configured so that work orders created on the remote site can have order type ZM01.

1. Go to SPRO (or transaction OIOD to skip step 2)


Processing -> Maintenance and Service Orders -> Functions and Settings for Order types -> Assign Order Types to Maintenance Plants

4. If ZM01 has not already been assigned to configured plants, click to ‘Create New Entries’ 5. Enter the Planning Plant and Order type you want to add to it, then Save


49

New Record will be added to the list (with the order type assigned to the plant)

Create External Number Range – Add to Group Create an external number range of globally unique numbers that will be used for work orders created at the remote site. Assign order type ZM01 to that number range (and any other order types that are used for WO Create on the remote site). All work orders at the remote sites are created using this external number range.

1. Go to SPRO (or transaction OION to skip step 2)


Processing -> Maintenance and Service Orders -> Functions and Settings for Order types -> Configure Number Ranges

4. If there is no group for external numbering, Create one (for example, External A – ZZZZZZZZZZZZ) a. Click the ‘Maintain Groups icon

b. Click the ‘Create’ icon to create a new group


50

c. Enter a group title and a number range, then save. The Number range must be an available

range of globally unique numbers.

d. New number range will be added to the list and you can add order types to it

5. Assign order type ZM01 to the group you created with the corresponding number range you assigned (in the example, the group that supports numbers between VZZZZ0000001 and VZZZZ999999)

a. Go to t-code OION

b. Click ‘GoTo’, then ‘Groups’ then ‘Maintain’

c. The order type should display in the ‘Non-Assigned Elements’ section d. Select the desired order type (ZM01) and click the ‘Element/Group’ button in order to assign it

to a specified number range


51

e. Select the appropriate number range and click the ‘Copy’ icon

f. The order type should now appear in the number range group you assigned it to


52

g. Save your changes

Maintain User Status Profile Maintain a user status profile that specifies a list of valid user statuses, then assign that user status profile to relevant order types that are used for work orders (in this case PM01 and ZM01)

1. Go to SPRO (or transaction OIBS to skip step 2,3)


Processing -> Maintenance and Service Orders -> General Data -> User Status for Orders -> Define Status Profile

4. Create a user status profile, for example EBEF_WO, that starts as a copy of the one used for order type

PM01. This sets the status options for work order create. a. Copy the EBEF_WO Status profile and rename, OR if it doesn’t exist,

b. Click the ‘Create’ icon c. Fill in the details for the status profile and click ‘Continue’

d. The EBEF_WO entry will be added to the status profile list:


53

e. Double click the entry, enter the following status details and Save

5. Assign this new user status to both PM01 and ZM01 order types

a. Go to SPRO (or transaction OIOG to skip step 2,3)

b. Click ‘SAP Reference IMG’ c. In the tree, navigate to Plant Maintenance and Customer service -> Maintenance and Service

Processing -> Maintenance and Service Orders -> General Data -> User Status for Orders -> Define Status Profile, then select ‘Assign User Statuses to Order Types’ from the options displayed and click ‘Choose’

d. Add EBEF_WO as the Status profile (‘Stat.Prof.’) for PM01 and ZM01 Order Types, and Save.


54

Create Control Keys EXT2 and ZINT Create control keys EXT2 (external) and ZINT (Internal) that can be used to specify external and internal work orders respectively. Any additional control keys used can also be specified here.

1. Go to SPRO


Processing -> Maintenance and Service Orders -> Functions and Settings for Order Types -> Control Key -> Maintain Control Keys

4. Select the control key PM01 from the menu bar and click the ‘Copy As’ icon. If there is no pre-existing PM01 control keys, click the ‘New Entries’ button to create a new control key


55

5. Enter in the following data for control key ZINT, and Save. ZINT Control Key entry will be added to the list.

6. Select the control key PM03 from the menu bar and click the ‘Copy As’ icon. If there is no pre-

existing PM03 control keys, click the ‘New Entries’ button to create a new control key

7. Enter in the following data for control key EXT2, and Save. EXT2 Control Key entry will be added to

the list.


56

Maintain Default Control Key Order Type ZM01 Set the default control key for work orders with order type ZM01. In this case, we are setting it to ZINT.

1. Go to SPRO (or t-code OIO6 to skip steps 2&3)


Processing -> Maintenance and Service Orders -> Functions and Settings for Order Types -> Control Key -> Maintain Default Values for Control Keys for Order Types

4. For each combination of Planning Plant and Order Type ZM01 assign control key ZINT and save: a. Double click the entry for the Planning Plant/Order Type ZM01


57

b. Make sure the form is in editable mode, enter the control key ‘ZINT’ and click ‘Save’

c. Do this for all combinations of Planning Plant and Order Type ZM01


58

Create Activity Type for ZM01 Orders Create Activity types to be used for ZM01 Orders. Activity types specify the type of activity a work order is being created for (for example: Regular Maintenance, Inspection, etc.).

1. Go to SPRO


Processing -> Maintenance and Service Orders -> Functions and Settings for Order Types -> Maintenance Activity Type -> Define Maintenance Activity Types

4. Click the ‘New Entries’ to add a ‘Maintenance Order’ activity type 5. Enter the Maintenance Order activity type details and click ‘Save’


59

6. The Maintenance order that was created will be added to the list

Assign Maintenance Activity Types to Order Type ZM01 The desired maintenance activity types to be used at the remote site must now be assigned to order type ZM01 (and any additional order types that are used for work order creation at the remote).

1. Go to SPRO (or t-code OIO5 to skip steps 2&3))


Processing -> Maintenance and Service Orders -> Functions and Settings for Order Types -> Maintenance Activity Type -> Assign Valid Maintenance Activity Types to Maintenance Order Types

4. To assign a maintenance activity type, click the ‘New Entries’ button


60

5. Enter in the order type & the maintenance activity types being assigned to that order type

6. Click ‘Save’ to save the new entries 7. Activity types that have been assigned are added to the list

Maintain Default Activity Type for Order Type ZM01 Assign the default activity type (created in ‘Create Activity Type for ZM01 Orders’) to be used for each order type and save the assignment. Set the default activity type for all order types that are used in work order creation (see below for example using ZM01).

1. Go to SPRO (or go to transaction OIO4 to skip steps 2 &3)


Processing -> Maintenance and Service Orders -> Functions and Settings for Order Types -> Maintenance Activity Type -> Default Values for Maintenance Activity Type for Each Order Type

4. Click the ‘New Entries’ button. 5. Enter in the Order Type and Maintenance Activity type you want to assign to it. Add multiple line

items as desired. Click ‘Save’ to complete the assignment.


61

6. The activity type is now assigned to the specified order type:

Configure Automatic Notification Creation During Work Order Creation For the solution, a notification must be created automatically during work order creation. The details of the notification being created can be specified using SPRO.

1. Go to transaction SPRO and click ‘SAP Reference IMG’

2. Navigate to Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Maintenance and Service Orders -> Functions and settings for Order Types -> Define Notification and Order Integration


62

3. Click the ‘New Entries’ button to add in a new order type entry

4. Add a new entry for ZM01 work order type that will be used by the solution for new work orders

created at the edge location. Assign the appropriate notification type to the order (In this case we used M1 – Maintenance Order). Select the ‘Notification’ and ‘Long Text’ checkboxes for each order type

5. Save the entries

Define Control Parameters for Completion Confirmations Maintain Control parameters for completion confirmations for maintenance and service orders. You must configure the parameters for each plant and order type combination

1. Go to transaction SPRO (or transaction OIOR to skip steps 2 & 3)

2. Click ‘SAP Reference IMG’ 3. Navigate to Plant Maintenance and Customer Service -> Maintenance and Service Processing ->

Completion Confirmations -> Define Control Parameters for Completion Confirmations 4. A list of Plants and Order Types are displayed. Users can click a line item and view the

confirmation parameters


63

5. Click the ‘New Entries’ button to add a confirmation parameter to the list


64

6. Enter the Plant and Order Type and click ‘Save’ to add the item to the list


65

7. Ensure entries are created for order type ZM01 and any other work order type that will be used by the solution.

PURCHASE REQUISITION SPECIFIC CONFIGURATION

Enhance CI_EBANDB and CI_EBANDBX Structures Since this is an offline solution and the user can create purchase requisitions at a remote site while disconnected, the request to create a requisition made by the solution interface must assign a temporary unique requisition number. When the requisition created on a remote site synchronizes with SAP ERP, a permanent purchase requisition number is generated by SAP ERP. To maintain the association between the local requisition number created at the remote site and the SAP ERP requisition number, enhance structures CI_EBANDB and CI_EBANDBX with the zzpr_no_local field. The field zzfreight_mode is also added to the

structures to support the use of freight modes at the remote site. 1. Go to se11


66

2. Enter table name ‘EBAN’ and click ‘Display’

3. Double click the data element ‘CI_EBANDB’

4. Pop-up appears asking if you want to create the structure. Click ‘Yes’ 5. Enter the following details and click ‘Save’


67

6. Specify package $TMP and save

7. Click the ‘Activate’ icon to activate the structure:


68

The activation log is displayed


69

8. Go back to the EBAN table and note that the ZPR_NO_LOCAL and ZFREIGHT_MODE1 items you added

to CI_EBANDB are displayed:

Add Components to Structure CI_EBANDBX

1. Go to se11

2. Enter ‘CI_EBANDBX’ under ‘Data Types’ and click ‘Create’


70

3. Select ‘Create Structure’ 4. Enter in the following details and save:

5. Assign package $TMP

6. Click the ‘Activate’ icon to activate the structure. The Activation Log will be displayed


71

APPEND STRUCTURE CI_EBANDBX to table EBAN

Implement BADI /EBEF/BADI_MM_PREQ_NUM_LC To pass the local assigned requisition number and freight mode from the solution interface to the newly added fields in CI_EBAN, implement the BAdI /EBEF/BADI_MM_PREQ_NUM_LC in your system and follow the

sample implementation class /EBEF/CL_BADI_IMPL_SAMPLE.

1. Go to se18

2. Enter BAdI /EBEF/BADI_MM_PREQ_NUM_LC and click ‘Display’

3. On the screen displayed click the ‘Create BADI Implementation’ icon


72

4. On the screen that appears, enter the Enhancement Implementation name ‘ZBADI_MM_PREQ_NUM_LC_IMPL’, a short description and click ‘Continue’

5. Assign package $TMP and save

6. On the ‘Create BAdI Implementation’ screen enter the following details and click ‘Continue’:

7. Choose to ‘Copy Sample Class’ of /EBEF/CL_BADI_IMPL_SAMPLE


73

8. Assign package $TMP and Save:


74

9. The Enhancement Implementation screen will now display:

10. Click the ‘Activate’ icon to activate the enhancement implementation

11. Select all objects to activate and click ‘Continue’ UNCOMMENT CODE IN COPIED CLASS Once the implementation class is copied, uncomment the code to pass the local assigned requisition number and freight mode from the solution interface to the newly added fields in CI_EBAN.


75

12. Go to the ‘Technical Details’ tab and double click the ‘Changed Object’ for the class:

13. On the Methods tab, select the first line item and click the ‘Source Code’ button:

14. Once the code displays, click the ‘Edit’ icon:


76

15. Uncomment out the code and ensure the fields from the sample class match the newly added fields in CI_EBAN (ZPR_NO_LOCAL for example). Save the changes.

16. Return to the previous page, select the 2nd method and click the ‘Code’ icon:


77

17. Uncomment out the code and ensure the fields from the sample class match the newly added fields in CI_EBAN. Save the changes.

18. Save the code changes. 19. Return to the previous page, select the 3rd method and click the ‘Code’ icon 20. Uncomment out the code and ensure the fields from the sample class match the newly added

fields in CI_EBAN. Save the changes


78

21. Click the ‘Activate’ icon to activate all the methods

22. Select the Methods that were edited and click the ‘Continue’ icon

Change Purchase Requisition Order Type The default requisition order type in table /EBEF/CONF_SYNCM is NB. This forces all purchase requisitions to be

created as type NB.

If you do not want purchase requisitions to be created as requisition type NB (standard procurement), you

can configure it as follows: 1. Go to SPRO

2. Click the ‘SAP Reference IMG’ button 3. Navigate to IoT Edge Processing -> Dynamic Edge Processing -> Backend Configuration ->

Synchronization Parameter -> Maintain Synchronization Parameter Mapping 4. Find entries with Synch Key : PRCRT and PRUPD, and parameter field ‘PR_TYPE’.


79

5. Double click the items to view the details:

6. Mapped field is defaulted to NB (standard procurement). Change this to a valid purchase

requisition order type (if desired) and Save. Do not change any other value.

Change Purchase Group The default requisition purchase group in table /EBEF/CONF_SYNCM is 001, which forces all purchase

requisitions created in purchasing group to be 001.

If you do not want to have 001 as the purchasing group, you can configure it as follows:


80

1. Go to SPRO

2. Click the ‘SAP Reference IMG’ button 3. Navigate to IoT Edge Processing -> Dynamic Edge Processing -> Backend Configuration ->

Synchronization Parameter -> Maintain Synchronization Parameter Mapping 4. Find entries with Synch Key : PRCRT and PRUPD, and parameter field ‘PUR_GROUP’

5. Double click the items to view the details 6. Change the ‘mapped field’ if desired to a valid purchasing group type. Save the changes. Do not

change any other value.


81

CONFIGURATION OF FILE TRANSFER

The solution requires a file folder on the underlying server (UNIX/Linux/Windows) for passing attachments files between SAP ERP and remote sites. You may need to request this from your system administrator if one doesn't already exist. The folder must be accessible from SAP ERP and from the MobiLink server. This section shows the setup for SAP ERP. File transfer setup for MobiLink can be found in Setting Up MobiLink Server. Note: The directory name should be at the same folder level as the ATTS files. Configure Attachment File Transfer Settings Use the table /EBEF/A_DEF to maintain the directory for attachment file transfers. This table identifies the

directory and subdirectory locations for the folder used to transfer attachments between SAP ERP and remote sites. Maintain the table using transaction /EBEF/DEF. To complete this task, complete the following

steps: Type SM30 into the transaction dropdown.

Type /ebef/a_def into the Table/View lookup, and click Display.

Make sure the configuration table has entries for each of the following business objects that use attachments, by switching to change mode icon and adding New Entries for the following objects:

o BUS2007 - Work Order attachments

o BUS2012 - Purchase Order attachments

o BUS2091 - Service Entry attachments

o BUS2105 - Purchase Requisition attachments

CLASSTYPE BO

CLASSNAME BUS2007

DIRPATH <the directory path from AL11>


82

SUBDIR Concatenate any subdirectory assigned with the business object, for example, RIGS/ATTS_BUS2007

RIGDEP 'N' (this is important - if 'Y', the program will look for another subdirectory)

CHANGED_TS Leave this blank - it will be used by programs

Note: You can set the directory path, however, the subdirectory for attachments folders must always match ATTS_<classname>, or the subdirectory won’t be recognized.

1. Click the ‘New Entries’ button to add a line

2. Add in a class for one of the sub-folders of the file directory and Save.


83

3. Now add in an entry for each of the remaining sub-directories:


84

4. Return to the se16 screen and view the ‘Table Contents’ for /EBEF/A_DEF

5. The added line items should be displayed


85

Configure Reports Management Settings Configuring reports management settings requires two tasks. First, configure intervals for the number range object /EBEF/REPO for use of the reports, then maintain a file share folder.

Configure Intervals for number range object /EBEF/REPO

The configuration of intervals for the number range object /EBEF/REPO is required for use of the reports. You

must create intervals in each system for this number range object using the transaction SNRO: 1. Go to transaction SNRO

2. Enter object /EBEF/REPO

3. Click the ‘Interval Editing’ button

4. Click the ‘Change Intervals’ button to edit the interval

5. Add a line item (by clicking the ‘Insert Line’ icon) and enter the number range from 0000000001 to

1000000000, then Save.

Maintain a File share folder

Create a file share folder for each remote site so that the relevant reports can be accessible on each remote. 6. Enter /n/ebef/manage_reps into the transaction dropdown.


86

7. Enter the remote sites you want to maintain a reporting schedule for

8. Create a folder for each remote site (for example, RPT_1000) so each has its own file share.

Create the Subdirectories on the SAP ERP server Create subdirectories in the shared file folder in order to facilitate the use of attachments on the Remote site. Attachments added (at the remote site or from ERP) are put into the folder of the relevant business object and accessible to all users of the system.

1. From the windows Explorer, access the share folder on the SAP ERP server 2. Create a subfolder for each business object that will use attachments. To do this, combine ‘ATTS_’

with the business object class name, for example, ATTS_BUS2007. Subdirectories: (ATTS_BUS2007, ATTS_BUS2012, ATTS_BUS2091, ATTS_BUS2105) The folder structure will display as follows:


87

Define the directories in SAP ERP Define the shared directory in ERP to facilitate the sharing of reports and attachments to/from ERP.

1. Go to transaction AL11

2. Click the ‘Configure User Directories’ icon:

3. Selected file-share directory

4. Save the new directory.

6.

Enter

CONFIGURATION OF WEB DYNPRO SERVICE

This solution uses Web Dynpro to launch your application. Make sure the Web Dynpro service is enabled in each system using the transaction SICF. After configuration, you should have a service called ebef under

your Web Dynpro runtime service as shown below (make sure you also activate the SYCLO service)


88

1. Go to transaction SICF

2. Click the ‘Execute’ icon on the search screen

3. Navigate to Default_host -> Sap -> bc -> webdynpro -> ebef in the file tree:

**note if ebef and TRANMON are deactivated


89

4. If deactivated, select the ‘ebef’ item. Click the ‘Service/Host’ from the menu and click ‘Activate’

5. Do the same for the ‘TRANMON’ item if applicable RUN INITIAL LOAD

Before scheduling the background (delta) jobs, you need to run the initial load for the following tables: /EBEF/GET_DT - Get Data Tables

/EBEF/GET_CT - Get Complex Tables

/EBEF/GET_OBJ - Get Object Tables

/EBEF/ATTACHMENTS_DOWN - Download Attachments from SAP ERP Business Objects to Remote

Sites

Once the initial loads are complete, schedule your regular background jobs as per Set Variants used for background jobs and Documentation of background jobs. The Initial load and the delta background jobs essentially run the same program (for CT, DT and OBJ tables), but the Initial Load must first run successfully to store a timestamp in the database. Any subsequent runs (background delta jobs) will leverage that timestamp to see if anything has changed and apply those changes. If the Initial load has not been completed before running the background jobs, the background jobs will basically be running an initial load again (on a scheduled basis) and will error. Data Tables - Initial Load Because the initial load is only run once, we do not need to define variants for the data loads.

1. Go to SE38

2. Enter program /EBEF/P_GET_RIG and click ‘Execute’


90

3. On the screen that is displayed, click ‘1) DT Fetch’

4. From the top menu, select ‘Program’ then ‘Execute in Background’


91

5. Click Continue on the ‘Background Print Parameters’ screen

6. Select an Immediate Start Time and click ‘Save’


92

7. A notification will appear saying that the background job was scheduled

8. To check the job results, go to sm37 9. Search for job name /EBEF/P_GET, and click ‘Execute’

10. The job details (and status) will be displayed. 11. Select the job and click ‘Job log’


93

12. The Job log will show each table executed and the corresponding data quantities:


94

You can also view the data loaded directly in transaction code se16 by display the data in /EBEF/D_DATALL:


95

Complex Tables – Initial Load 13. Return to se38 to run the initial load for the complex tables.


The Initial load run a SINGLE at a time. You must highlight the plant you want to Execute.


96

15. To rerun the initial load you can you P_GET and select reset:

16. On the screen that is displayed, click ‘Fill Complex Tables’ and scroll further down the screen to fill

out the ‘Complex Table Options’


97

17. Select ‘Reset – All Data Deleted’ in the Complex table Options. Select all the tables listed in the reset option, and click the Icon beside the ‘Plant’ field to specify the plants you want to execute it for.

18. In the Plant Selection pop-up, enter the plants you want to run the complex initial load for. Then

click the ‘Copy’ icon to select them


98

Note: after the values have been copied, only the first one from the list will be displayed in the Plant field:



99




100


23. To check the job results, go to sm37

24. Search for job name /EBEF/P_GET, and click ‘Execute’


101

25. The job details (and status) will be displayed. If the job is still running, it’s status will display as ‘Active’

26. Select the job and click ‘Job log’


102

27. The Job log will show each table executed and the corresponding data quantities. If the job is still running (status = Active), the log will show what has been executed up until the current point.

28. Wait until the job has finished before scheduling the run of the next initial load. This could take a

significant period of time depending on how much data is being loaded.

Object Tables – Initial Load 29. Return to se38 to run the initial load for the object tables.



103

Select ‘3) Obj Tables’ You can also use ‘Reset’ feature to rerun the Object Tables

31. On the screen that is displayed, click ‘Fill Object Tables’ and scroll further down the screen to fill out the ‘Object Table Options’

32. Select ‘Reset – All Data Deleted’ in the Object Table Options. Select all the fetch options listed in the reset option, and click the plant selection Icon beside the ‘Plant’ field to specify the plants you


104

want to execute it for.

33. In the Plant Selection pop-up, enter the plants you want to run the object table initial load for. Then

click the ‘Copy’ icon to select them

Note: after the values have been copied, only the first one from the list will be displayed in the


105

Plant field:




106


NOTE: If the previous Initial load has not finished you can select ‘After Job’ and run it after the previous job had finished.


38. To check the job results, go to sm37


107

39. Search for job name /EBEF/P_GET, and click ‘Execute’

40. The job details (and status) will be displayed. If the job is still running, it’s status will display as

‘Active’

41. Select the most recent job and click ‘Job log’


108

42. The Job log will show each table executed and the corresponding data quantities. If the job is still

running (Status = Active), the log will show what has been executed up until the current point.

43. Wait until all initial load jobs have finished before moving onto the next configuration steps.

This could take a significant period of time depending on how much data is being loaded. SET VARIANTS USED FOR BACKGROUND JOBS

Variants must be set up before documenting the background jobs in order to specify what each background job will run. Variant DT

(used for job /EBEF/GET_DT)

A. Go to se38

Job Step Description Program Value

ABAP Program Name Variant Client-Specific

Get delta updates for data tables

ABAP /EBEF/P_GET DT_EBEF Yes


109

B. Enter program /EBEF/P_GET and click ‘Execute’

C. Ensure ‘Fill Data Tables’ is selected and select ‘Standard’ under Data Table Options

D. Click ‘Save’ to save the selected options as a variant

E. Enter the following details and click ‘Save’ to save the Variant

Variant Name: DT_EBEF


110

Description: Data tables background run

Variant CT (used for job /EBEF/GET_CT)

A. Go to se38


C. Ensure ‘Fill Complex Tables’ is selected and select ‘Standard’ under Complex Table Options

Job Step Description Program Value ABAP Program Name Variant Client-Specific

Get delta updates for complex tables

ABAP /EBEF/P_GET CT_EBEF Yes


111



Variant Name: CT_EBEF

Description: Complex tables background run

Variant OBJ (used for job /EBEF/GET_OBJ)


112

A. Go to se38


C. Ensure ‘Fill Object Tables’ is selected and select ‘Standard’ under Object Table Options (with all

Fetch options selected as well)


Get delta updates for object tables

ABAP /EBEF/P_GET OBJ_EBEF Yes


113



Variant Name: OBJ_EBEF

Description: Object tables background run

Variant Standard (used for job /EBEF/TRN)


Process all transactions uploaded from remote sites

ABAP /EBEF/P_TRN STANDARD_EBEF Yes

Variant Standard should be created with your entries based on the RFC connections and users created for your installation.

1. Go to se38

2. Enter program /EBEF/P_TRN and click ‘Execute’


114

3. On the screen that displays, click the ‘Save’ icon to Save the details as a variant

4. Enter in the variant details and Save.

Variant Name: STANDARD_EBEF


115

Description: Background scheduled job

Variant /EBEF/HOURLY

(used for job /EBEF/HOURLY_REPORTS)

A. Go to se38

B. Enter program /EBEF/P_JOB_START and click ‘Execute’


Run hourly reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/HOURLY Yes


116

C. On the screen that displays, enter the following details and Save:

AL11 Directory to download Rep: <Directory created during the File Transfer Set-up section>

Sub-directory for report files: <Subdirectory created during the file transfer set-up section>

Use Plant Sub-directories: Y Run Schedule: H Prefix for reporting Jobs: /EBEF/RPT_ Max number of parallel jobs: 5

Use the multi-select option for the ‘Rig’ field to add the desired plants (in this case, 1000 & 3000)

D. Enter in the variant details and Save.

Variant Name: /EBEF/HOURLY


117

Description: Hourly Run of Mobile Reports

Variant /EBEF/DAILY

(for job /EBEF/DAILY_REPORTS)


Run daily reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/DAILY Yes

A. Go to se38

B. Enter program /EBEF/P_JOB_START and click ‘Execute’


118

C. On the screen that displays, enter the following details and Save:

AL11 Directory to download Rep: <Directory created during the File Transfer Set-up section>

Sub-directory for report files: <Subdirectory created during the file transfer set-up section>

Use Plant Sub-directories: Y Run Schedule: D Prefix for reporting Jobs: Max number of parallel jobs: 5

Use the multi-select option for the ‘Rig’ field to add the desired plants (in this case, 1000 & 3000)


119


Variant Name: /EBEF/DAILY

Description: Daily Run of Mobile Reports


120

Variant /EBEF/MONTHLY

(for job /EBEF/MONTHLY_REPORTS)

Perform the exact same steps as in /EBEF/HOURLY and /EBEF/DAILY except that in the /EBEF/P_JOB_START page the Run Schedule should be set to ‘M’ (Monthly)

Save the Variant Details as follows:


Run monthly reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/MONTHLY Yes


121

Variant /EBEF/YEARLY

(for job /EBEF/YEARLY_REPORTS)

Perform the exact same steps as in /EBEF/HOURLY and /EBEF/DAILY except that in the /EBEF/P_JOB_START

page the Run Schedule should be set to ‘Y’ (Yearly)


Variant /EBEF/ONDEMAND

Job Name: /EBEF/ONDEMAND_REPORTS Scheduler: Run on request


Run yearly reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/YEARLY Yes


122


Run on-demand reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/ONDEMAND Yes

Perform the exact same steps as in /EBEF/HOURLY and /EBEF/DAILY except that in the /EBEF/P_JOB_START

page the Run Schedule should be set to ‘A’ (On Demand Reports)


Variant UPLOADATTACH

(for job /EBEF/ATTACHMENTS_UP)


Attach documents uploaded from remote sites to SAP ERP business objects

ABAP /EBEF/P_ATTACHMENT_MANAGE

UPATTACH_EBEF Yes


123

A. Go to se38

B. Enter program /EBEF/P_ATTACHMENT_MANAGE and click ‘Execute’

C. On the screen that displays, select ‘Test Upload’ and click the Save icon to Save as a Variant


Variant Name: UPATTACH_EBEF

Description: Upload attachments from unix

Variant DWNATTACH_EBEF

(for job /EBEF/ATTACHMENTS_DOWN)


Download attachments from ECC business objects to remote sites

ABAP /EBEF/P_ATTACHMENT_MANAGE

DWNATTACH_EBEF Yes

A. Go to se38

B. Enter program /EBEF/P_ATTACHMENT_MANAGE and click ‘Execute’


124

C. On the screen that displays, select ‘Test Download’ and click the Save icon to Save as a Variant


Variant Name: DWNATTACH_EBEF

Description: Download attachments from unix

Variant GET_MDKE

(for job /EBEF/GET_MDKE)


Download stock wanted list to remote sites

ABAP /EBEF/P_GET_MDKE GET_MDKE_EBEF Yes

A. Go to se38

B. Enter program /EBEF/P_GET_MDKE and click ‘Execute’


125

C. On the screen that displays, click the Save icon to Save as a Variant


Variant Name: GET_MDKE_EBEF

Description: Standard bkgrnd Stock Wanted

DOCUMENTATION OF BACKGROUND JOBS

The following background jobs are used in the solution. They are defined using transaction SM36. Before you

run any batch jobs, make sure that all of the background jobs have been defined and scheduled to run at the appropriate intervals. The scheduled background job ensures that changes in ERP are applied to the staging tables (for synchronization to the remote site), and new changes in the staging tables (from the remote site) are applied into ERP. The Initial load and the delta background jobs essentially run the same program (for CT, DT and OBJ tables), but the Initial Load must first run successfully to store a timestamp for the tables in the database. Any subsequent runs (background delta jobs) will leverage that timestamp to see if anything has changed and apply those changes. If the Initial load has not been completed before running the background jobs, the background jobs will basically be running an initial load again (on a scheduled basis) and will error.


126

/EBEF/GET_DT – Get Data Tables (3.1.2.1) Job Name: /EBEF/GET_DT

Scheduler: Run every 1 minute

1. Go to SM36

2. Enter job name /EBEF/GET_DT and click the ‘Step’ icon

3. Fill in the appropriate details as shown below (make sure that ‘abap program’ is selected). Use

user PMBATCH. Click Save



Get delta updates for data tables

ABAP /EBEF/P_GET DT_EBEF Yes


127

4. Program will display on screen:

5. Click the back arrow to go back to the ‘Define Background Job’ screen


128

6. Click ‘Start Condition’ to specify the start conditions

7. Select ‘Immediate’ for the start time and then click the ‘Periodic Job’ checkbox


129

8. Click the ‘Period Values’ button and select the ‘Other Period’ option (as we want to run this job

every minute).

9. Enter a 1 minute period and click ‘Save’

10. Click ‘Save’ on the ‘Period Values’ pop-up and on the ‘Start Time’ pop-up.

11. Once the Step has been created and the start time/period specified, you can save the

Background job


130

12. Go to SM37

13. Enter in the job name /EBEF/GET_DT and click ‘Execute’. The job details should now be

displayed


131

14. Return to sm36

15. Create background jobs for all tables (specifying them using the process outlined above for

/EBEF/GET_DT but using the details below):

/EBEF/GET_CT - Get Complex Tables Job Name: /EBEF/GET_CT

Scheduler: Run every 1 minute Variant CT_EBEF is created in above steps



Get delta updates for complex tables

ABAP /EBEF/P_GET CT_EBEF Yes


132

Click “Save” icon

Back one screen and hit “Start condition

Click “Immediate” and check “Periodic Job”, followed by clicking “Period values”:


133

To setup every minute, click “Other period”, set 1 minute then “Save” icon, and follow all the “Save” icon until

/EBEF/GET_OBJ - Get Object Tables Job Name: /EBEF/GET_OBJ

Scheduler: Run every 1 minute Variant OBJ_EBEF is created in above steps



Get delta updates for object tables

ABAP /EBEF/P_GET OBJ_EBEF Yes


134



135

To setup every minute, click “Other period”, set 1 minute then “Save” icon, and follow all the “Save” icon

/EBEF/TRN - Process Uploaded Transactions Job Name: /EBEF/TRN




Process all transactions uploaded from remote sites

ABAP /EBEF/P_TRN STANDARD_EBEF Yes

Variant STANDARD_EBEF is created in above steps


136



137

To setup every minute, click “Other period”, set 1 minute then “Save” icon, and follow all the “Save” icon

/EBEF/HOURLY_REPORTS Run Hourly Reports in Background and Send to Remote Sites Job Name: /EBEF/HOURLY_REPORTS

Scheduler: Run once every hour



Run hourly reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/HOURLY Yes


138

/EBEF/DAILY_REPORTS Run Daily Reports in Background and Send to Remote Sites Job Name: /EBEF/DAILY_REPORTS

Scheduler: Run once each day



Run daily reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/DAILY Yes

/EBEF/MONTHLY_REPORTS Run Monthly Reports in Background and Send to Remote Sites Job Name: /EBEF/MONTHLY_REPORTS

Scheduler: Run once each month



Run monthly reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/MONTHLY Yes

/EBEF/YEARLY_REPORTS Run Yearly Reports in Background and Send to Remote Sites Job Name: /EBEF/YEARLY_REPORTS

Scheduler: Run once each year



Run yearly reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/YEARLY Yes

/EBEF/ONDEMAND_REPORTS Run On-Demand Reports in Background and Send to Remote Sites Job Name: /EBEF/ONDEMAND_REPORTS

Scheduler: Run on request



Run on-demand reports in background and send to remote sites

ABAP /EBEF/P_JOB_START /EBEF/ONDEMAN

D Yes

/EBEF/ATTACHMENTS_UP Attach Documents Uploaded from Remote Sites Job Name: /EBEF/ATTACHMENTS_UP




Attach documents uploaded from remote sites to SAP ERP business objects

ABAP /EBEF/P_ATTACHMENT_M

ANAGE

UPATTACH_EBEF Yes


139

/EBEF/ATTACHMENTS_DOWN Download Attachments from ECC Business Objects to Remote Sites Job Name: /EBEF/ATTACHMENTS_DOWN




Download attachments from ECC business objects to remote sites

ABAP /EBEF/P_ATTACHMENT_M

ANAGE

DWNATTACH_EBEF Yes

/EBEF/GET_MDKE Download Stock Wanted List to Remote Sites Job Name: /EBEF/GET_MDKE

Scheduler: Run daily. The assumption is that the Inventory Manager or person responsible for re-ordering inventory performs this job every day, so the scheduling of the report should be daily. If the person responsible for re-ordering inventory performs this on a less or more frequent basis, then the schedule cadence can be adjusted accordingly. For example, if the re-ordering takes place once a week, then the report can run on a weekly schedule. The assumption is that this re-ordering data is required in the implementation of the solution. If it is not used, then the schedule should not be set for the job.



Download stock wanted list to remote sites

ABAP /EBEF/P_GET_MDKE GET_MDKE_EBEF Yes

Schedule parameters for maintenance orders

1. To prevent this error when creating work orders:

2. Go to transaction OPU7


140

3. Click ‘New Entries’ to add in scheduling parameters for specific order types:

4. Enter the following details, and click ‘Save’ to add the new entry.

Plant: <enter appropriate plant> Order Type: <enter appropriate order type> Prodn Superv: * Adjust Dates: ‘Do not adjust basic dates, dep. Reqmts to operation dates’ Scheduling Type: Forwards


141

Automatic Scheduling: <selected>

5. Add new entries for all applicable plant/order combinations

SECURITY INFORMATION

This Add-On dependency is SAP ERP 6.0 (EHP 7 and above) Plant Maintenance and Materials Management modules. Therefore, guides for these modules also apply to this solution. For more information about specific security-related topics, see the following resources on SAP Service Marketplace, SAP Support Portal, or SCN:

Topic Quicklink

Security http://service.sap.com/security http://scn.sap.com/community/security

Platforms http://service.sap.com/platforms

Infrastructure http://service.sap.com/securityguide → Infrastructure Security

SAP NetWeaver http://scn.sap.com/community/netweaver

http://service.sap.com/security

http://scn.sap.com/community/security

http://service.sap.com/platforms

http://service.sap.com/securityguide

http://scn.sap.com/community/netweaver


142

For a complete list of available SAP Security Guides, see SAP Service Marketplace at http://service.sap.com/securityguide. Authorization Concept There are two types of authorizations for this solution: Edge, and SAP ERP. Edge roles or work centers control the functionality accessible by users of the edge user interface. When users at the remote location submit work to synchronize in SAP ERP, standard SAP ERP authorization checks are used during the batch job.

Note

All edge users submitting work to be posted in SAP ERP need authorization to the S_RFC Object for all RFC function calls.

Roles The following table lists the functions that can be assigned to edge roles for use in the solution.

Role Description

APPROVAL Purchase Requisition Approval

BOM_EDIT Bill of Material Edit

GITRANSF Goods Issue and Transfer

GIWRKORD Goods Issue for Work Order

INVTMNGR Inventory Manager

MATEDIT Material Edit

MEASPNTS Measurement Points

POGR Purchase Order and Goods Receipt

PREDIT Purchase Requisition Edit

REPORTIN Inventory Report

SERVENTS Service Entry Sheet

STATREDY Status Change to Ready

STATTECO Status Change to TECO

STOCKWNT Stock Wanted

WORKMNGR Work Manager

MATDOCRV Material Document Receive

http://service.sap.com/securityguides


143

PIEDIT Physical Inventory Edit

PIPSTDIF Physical Inventory

Mapping Remote Location Users with Roles Local Users

In the SAP GUI, go to /n/ebef/roles and enter the following roles data:

1) Select New Entries.

2) Enter the main work center (for example, SOMC, OIM, MS, CRAFT) representing front-end roles. 3) Select functions to be performed by this role/work center. See Role/Function Assignments. 4) Enter a timestamp value in the following format:

o Approximately 5 minutes in the future, so that when you save the record, it will be picked up for synchronization.

o The format is YYYYMMDDHHMMSS (for example, 20160801134255 – which corresponds to August 1, 2016 at 1:42:55 PM)

o Select the Save icon on the top menu bar. 5) Repeat steps 1-4 for the remaining roles/functions.


144

Role/Function Assignments

Corresponding Function Dropdown Values

Function Value

Permission Granted Permission Code

Approvals Control access to approvals data APPROVAL

Bill of Material edit Control access for editing BOM items from equipment BOM

BOM_EDIT

Goods Issue and Transfer

Control access to transfer out goods from a specified remote plant destined for another remote plant

GITRANSF

Goods Issue for Work Order

Control access for the issuing of materials to work orders

GIWRKORD

Inventory Manager Control access to viewing Inventory and Materials management capabilities

INVTMNGR

Material edit Control access to editing materials MAEDIT

Material Documents Reverse

Control access to perform material document reversals

MATDOCRV

Physical Inventory Edit

Control access for creating Physical Inventory Documents and performing counts of materials in inventory

PIEDIT

Physical Inventory Control access to post differences for a Physical Inventory Document count

PIPSTDIF


145

Purchase Order and Goods Receipt

Control access for retrieving goods for a Purchase Order

POGR

Purchase Requisition Edit

Control access to edit of Purchase Requisitions

PREDIT

Inventory Report Control access to reporting data REPORTIN

Service Entry Sheet

Control access to service entry sheet data SERVENTS

Status change to REDY

Ability to change user status of a work order to REDY

STATREDY

Status change to TECO

Ability to change user status of a work order to TECO

STATTECO

Stock Wanted Control access to Stock Wanted data for creating Purchase Requisitions

STOCKWNT

Work Manager Control access to the Maintenance capabilities

WORKMNGR

Local User Setup

1) In the SAP GUI, go to transaction /n/ebef/localuser:

2) Select New Entries.

3) Add the plant user. o Example: SOMC 0102

4) Add the plant (remote site #) in the next column. o Example: 0102

5) Press tab, then enter the back-end SAP ERP user name that has been set up for the SOMC 0102 user. 6) Add the main workctr (that is, SOMC, OIM, MS, CRAFT, and so on; the ones set up in the Roles table

above). 7) Set the active user flag to True.


146

8) Set the create time stamp value using YYYYMMDDHHMMSS format, then click Save on the top menu. 9) Repeat steps 1-8 for the remaining users at the remote location.

Data Privacy and Protection This solution provides General Data Protection Regulation (GDPR) compliance features. Security-Relevant Logging and Tracing Security-related logging uses standard logging for all actions in SAP ERP. This logging relates to the back-end user ID that is linked to the edge user ID in table /EBEF/LOCALUSER. Edge security logging is handled

through an LDAP server. LDAP Setup LDAP (Lightweight Directory Access Protocol) is an open and vendor-neutral, industry-standard application protocol for querying and modifying items in directory services. In this solution, LDAP verifies the credentials of a user at the edge site. There are three parts to authentication of credentials:

• Edge site authentication

• Synchronization transport

• SAP ERP transaction processing authorization Remote site authentication is processed via LDAP. Synchronization transport happens via the technical RDBMS user for the staging area (MobiLink user) within the SAP ERP database. Finally, processing of the transaction into SAP ERP occurs via the SAP ERP user.


147

At the remote site, the edge server/application authenticates against LDAP protocol. If Active Directory is being used (such as Windows environment), Active Directory needs to be exposed as LDAP protocol. To set up LDAP, complete the following steps: 1) Set up the back-end system (see Local User Setup). 2) Set up the edge configuration. We will be using only the search and compare feature of LDAP; we must

first set up the following items in the remote server database (SYNC_OPTIONS): o LDAP URL – a client starts an LDAP session by connecting to an LDAP server (DSA). This is

exposed as an URI with the default port as 389. o LDAP DOMAIN COMPONENT – a tree view organization in which the user can be located as a

DOMAIN COMPONENT (DC). Multiple tree views can be shown; the more concise the tree view, the quicker the lookup for pass or failure

o LDAP AUTHENTICATION TYPE – simple is currently the only authentication type that has been tested within the solution. Other methods may require unsupported LDAP attributes. Do not change the “simple” setting.

o LDAP MATCH ATTRIBUTE – attribute that forms a distinguished name (DN). LDAP uses a unique DN to look up the directory. The uniqueness is constructed with this attribute as its DC. For example: if the matching attribute is UID and the domain component is “OU=people,DC=employee,DC=SAPGLOBAL,DC=com; “ looking up john.smith in LDAP would be the following “UID=john.smith,OU=people,DC=employee,DC=SAPGLOBAL,DC=com;”


148

APPLYING SQL PATCHES TO THE DATABASE

Because the Business Essential Functions Service contains SQL components, applying a patch differs from applying SAP notes for ABAP. 1) Find the SQL patches, which are usually delivered through the SAP Support Portal Software Download

Center.

2) Download any applicable patches to a temporary folder. 3) Unzip the patches and copy them to your remote server where you installed your SQL database as

described in Remote SQL Anywhere 17.0 Database Server Setup Step-by-Step.

4) Go to the destination in the new SQL folder where you copied the patch and edit the setlocalenv.cmd

file.


149

5) Change the highlighted sections below to match the local settings.


150

6) Open the update.cmd file and modify the highlighted section of the file to match the remote site (0425 is

used in this example), DC (xxxx), user, and LDAP server.

7) Fix the path (in the same update.cmd) and copy the java folder into the bin directory.


151

8) Disable the SAAP service in Web Services.

9) Once all setenvlocal.cmd and update.cmd files are modified, run the update.cmd in a command line.

10) Monitor the screen to make sure no errors are reported. You should see the following results:


152

11) Reenable SAAP Web Services.


153

MULTI-LANGUAGE SUPPORT

The solution currently supports only English language. This means that you can only configure back-end processing for English, and data is retrieved in that language. All back-end batch jobs must run in English.


154

APPENDIX A: SCANNING ATTACHMENTS FOR MALWARE

This section only applies if the remote system’s antivirus software does not watch the file system to scan files as they are saved. The DEP SQL Anywhere database can execute a command line script to instruct the antivirus software to check an attachment file for malicious content. Without any configuration, the default behavior is to rely on existing antivirus software and take no action against new attachments. In this situation the value of rem_saap_scanner_script in setlocalenv.cmd should be empty. If a script does need to be used to scan attachments, the value of rem_saap_scanner_script should be the path to the script. The script should be based on (or a modified version of) the sample at $SQL_FOLDER$\sqlanywhere\scanner\script.cmd. Of note is line 12, which is the actual command to run the scanner against the new attachment file. This will vary based on the antivirus software installed. Depending on how your antivirus software handles success or failure, line 15 may also need to be modified. A successful scan on a clean file should output a value of 0. Any other value will be seen as either an error or malicious content. Some antivirus software will simply return an error code if a malicious file is detected, others may have different behavior. Refer to your antivirus software’s documentation for information about scanning a target file from the command line, and how it provides return codes upon execution.


155

APPENDIX B: RESTARTING THE DATABASE SERVER AND MOBILINK CLIENT ON LINUX

It is recommended to configure all processes to run as background processes that are autostarted when the Linux instance boots up. There are multiple ways of accomplishing this in Linux. This documentation will focus on using Systemd Linux services. Systemd is the new standard for Linux that is being adopted by most major Linux distributions. It allows configuring restarting processes if they fail, easy definition of dependencies between services, easier configuration. This section is not meant as an in-depth tutorial on Systemd but covers creating systemd services for this solution, deploying and configuring them for auto-start. Please refer to systemd documentation for details on specific parameters and how systemd works in general. Systemd services are defined by creating "unit" files in /lib/systemd/system directory. On some Linux

distributions such as Suse Enterprise Linux 12, /lib/systemd directory does not exist. In this case use

/etc/systemd/system directory. When both directories ie. /lib/systemd/system and

/etc/systemd/system are present use /lib/systemd/system directory. The unit files specify how to start or

stop services, any dependencies, what action to take if the process fails and if this service will be auto-started during Linux bootup at what point in the bootup process it should be started. Once the unit file is in the required location, you will need to execute the following command to get systemd to pick-up the new service definition. You will need to rerun this command any time you edit any unit file.

systemctl daemon-reload

Below are standard system commands to start and stop services

Command Description

systemctl status <servicename> Display the current status of the service

systemctl start <servicename> Start the service manually

systemctl stop <servicename> Stop the service manually

systemctl enable <servicename> Configure the service to auto-start on Linux bootup

systemctl disable <servicename> Configure the service to no-longer auto-start on Linux bootup

For each service systemctl start <servicename> and systemctl enable <servicename> need to be

run. Before starting the services the currently running database server and synchronization process may need to be stopped manually. Below is an example unit file for SQL Anywhere used by Business Essential Functions Service. It should be called ebef.service and placed in /lib/systemd/system. The paths to SQL Anywhere 17 may need to be

changed if it was installed elsewhere.

[Unit]

Description=EBEF

[Service]

Type=simple

ExecStart=/bin/bash -c 'source /opt/sqlanywhere17/bin64/sa_config.sh && dbsrv17

@/home/SAP/SAAP/ebef_db_start.conf'


156

ExecStop=/bin/bash -c 'source /opt/sqlanywhere17/bin64/sa_config.sh && dbstop

@/home/SAP/SAAP/ebef_db_stop.conf && sleep 5'

Restart=always

RestartSec=15

[Install]

WantedBy=multi-user.target

Below are the configuration files relavent to starting the database server and should match the name specified in the unit file above. ebef_db_start.conf specifies the parameters needed to start the database

server and ebef_db_stop.conf specifies the parameters needed to stop the database server.

Example ebef_db_start.conf configuration file:

-n SAAPDB_RCS_SERVERNAME_1000

/home/SAP/SAAP/db/1000/DEP.db

-n

SAAP_RCS_rem_1000

-o

/home/SAP/SAAP/db/logs/eng_log_1000

-on

4M

-x

shmem

-x

tcpip(port=5657)

-xs

http(port=8080;dbn=DEP_RCS_rem_1000;MaxRequestSize=10M;log=/home/SAP/SAAP/db/logs/web_log

_1000.txt)

-gd

ALL

Example ebef_db_stop.conf configuration file:

-y

-c

"dsn=DEP_RCS_rem_1000"

Below is an example unit file for Mobilink used by the solution . It should be called ebef_sync.service

and placed in /lib/systemd/system directory.

[Unit]

Description=sync

BindsTo= ebef.service

After= ebef.service

[Service]

Type=simple

ExecStart=/bin/bash -c 'source /opt/sqlanywhere17/bin64/sa_config.sh && dbmlsync

@/home/SAP/SAAP/mlsync.conf'

ExecStop=/bin/bash -c 'pkill -P $MAINPID && sleep 10'

Restart=always

RestartSec=30

[Install]

WantedBy=multi-user.target


157

The "After" parameter specifies that this service should be started after the "ebef" service has started. The "BindsTo" service specifies that if the "ebef_sqlany" service stops then the streaminglite service should also

be stopped. This "After" and "BindsTo" parameters specific service dependency. All the commands specified for ebef.service will also apply to this service.

Below is an example configuration file for starting the MobiLink client and should match the name specified in the unit file above in this example mlsync.conf.

-c

"dsn=DEP_RCS_rem_0293"

-os

4M

-o

/home/SAP/SAAP/db/logs/DEP_RCS_dbmlsync_0293

-e

"sch=EVERY:00:02"

-x

4M

-sc


158

APPENDIX C: DATA PRIVACY AND PROTECTION CONFIGURATION

This configuration is required to implement the data privacy and protection features in the solution.

Configure Retention Period for Data Privacy and Protection Processing

This configuration is required to maintain retention periods (no. of days)

• for read-only O-tables and master data tables, and

• for edge transaction T-tables.

Setting retention periods is required for use of this feature. The rention periods have the following significance: MasterRetenDays – this sets the number of days in the past from today’s date, for which data that is identified as personal data, should be left in the data records (i.e. younger than today’s date minus the retention period), and is considered active data. Active data meaning that it is data for which this personal information (e.g. Username) is desired to still be available through the APIs used to access the data. The date that is used as a reference date, from which to identify if the record is within or outside of the retention period, is the date and time stamp on the record, which represents the last refresh of the record. Any record that is outside of the retention period (i.e. older than today’s date minus the retention period) will have an “*” (i.e. asterix) anonymizing the personal data, if existing. This is refered to as masking the data. Customer needs to decide how far in the past to retain personal data stored in the solution, and therefore set the retention period accordingly. TransRetentionDays – this sets the number of days in the past from today’s date, for which Transaction records, that may contain personal data, should be left in the system for reference. Transaction records are used in the solution and then remain in the solution, as transaction logging information, for troubleshooting issues related to past transactions from the edge. Any records that are older than today’s date minus the retention period, will be deleted in the system. Customer needs to decide how far in the past they wish to keep these transaction records, in order to investigate past transaction processing from the edge. Note: this feature does not affect data that resides in either the SAP ERP or SAP S/4HANA system, but only data that is extended through this solution. To maintain retention periods:

1. Open transaction code /N/EBEF/GEN_CONF to maintain the following entries for the retention days for

the Read-only/O-tables and T-tables:


159

Syclo Data Table Key General Configuration Value

MasterRetenDays <Retention days for Read-only/O-tables>

TransRetenDays <Retention days for T-tables>

2. Enter desired retention periods. Be aware that setting retention days to a certain value and executing the masking, and then changing the value to a larger number, will not return the original personal data that was masked to its unmasked state.

For example: If MasterRetenDays is set to 40.

- Personal data that is in records that are older than 40 days will have personal data masked. If MasterRetenDays is then set to 70, on the same date.

- Personal data this is in records that are between 40 and 70 days old will still be masked, because the masking was done when the MasterRetenDays was set to 40.

3. Execute program /EBEF/P_GET. On the selection screen, Uncheck ‘Fill Complex Tables’ and ‘Fill

Object Tables’ check boxes. Only ‘Fill Data tables’ checkbox should be checked from Table Options. Also, select the radio button ‘Standard’ from the Data Table Options:


160

4. Click execute to update the maintained retention days in table /EBEF/D_DATALL. Example screen shot

of the table entries is as below. These retention period values will be used by the scheduled jobs (/EBEF/PERS_TRN and /EBEF/PERS_MST)to maintain the masking and deletion activity on a daily

basis.

5. Repeat steps 1 through 4, if the retention period values need to change.


161

/EBEF/PERS_TRN – Delete transaction record

Job Name: /EBEF/PERS_TRN


/EBEF/PERS_MST – Mask user’s personal information for master data/read-only data

Job Name: /EBEF/PERS_MST


Job Step Description Program Type


Delete transaction record ABAP /EBEF/P_DPP_USER_DTL TRANSACTION Yes

Job Step Description Program Type


Mask user’s personal information for master data/read-only data

ABAP /EBEF/P_DPP_USER_DTL MASTER Yes


162

APPENDIX D: AIN CLOUD INTEGRATION AT THE EDGE SERVICES (ES) CORE

For customers that have subscribed to the SAP Asset Intelligence Network (AIN), there is the option of integrating to AIN, so that supported data objects can be made available at the Edge (See Business Essential Functions Service – Developer Guide, Business Essential Functions Service – API Guide, at help.sap.com, for details). Below, are the configuration instructions for the integration to customer specific AIN subscription.

AIN

(Asset Core)

SAP Edge Services (ES)

RR

ES Persistence

ES

Synchronization

Server

ES Core

Get Equip

Model

Get Equip

Model Attribute

(Threshold etc)

Get Class

Template

Get Customer

Equipment

ES Cloud Integration

ES Edge

Equipment

SensorEquipment

SensorEquipment

Sensor

RR

RR

The setup of Asset Core integration consists of setting up:

• Setup of cloud integrator to AIN and configuring the cloud integrator

• Enabling Asset Core synchronization at the Edge by configuring the frequency of synchronization


163

Setup the Cloud integrator There are three pieces in the Cloud integration Framework:

• Cloud Integrator (Java application)

• The persistence staging for synchronization and configuration data

• The synchronization engine The following are steps to setup the cloud integrator with the configuration settings:

1. Download the cloud integration software to the MobiLink server (com.sap.dep.ml_sqla).

2. Create the folder where AIN’s persistence store will reside. For example, if you want the persistence store is in d:\DEP_FILES\SJ4_AIN

3. Modify build.properties file to ensure the above directory is used (root.db.dir) in the AIN directory: Change the “cons.db.dir=${basedir}/db/${project}” to the appropriate directory. The above example would be: “cons.db.dir= D:\DEP_FILES\SJ4_AIN /db/${project}”

4. Modify build.properties file to ensure the asset core end-point is correct. The following are the Asset Core properties required:

Properties Description

ml.port Default 6850

option.asset_core_url AIN end-point data provider

option.proxy_host Specify the host name or IP address of the proxy server. Default as “proxy”

option.proxy_port Specify the port number of the proxy server. Default 8080

option.asset_core_sync_freq_minutes Specify the frequency of the synchronization. Default 5 minutes

option.system_id System ID associated to the AIN instance

option.client_number Client number associated to the AIN instance

For example:

option.asset_core_url=https://ain_my_asset_core.hana.ondemand.com

option.proxy_host=proxy


164

option.proxy_port=8080 option.asset_core_sync_freq_minutes=5 option.system_id=QI3 option.client_number=002

5. Run the build to setup the AIN by running the default target: ant

6. Set up the Asset Core technical user by running the following command: dbisql -nogui -onerror exit -c <connection_string> CALL sp_setup_technical_user(<user_id>, <password>) For example: dbisql -nogui -onerror exit -c dsn=ASSET_CORE;uid=dep;pwd=sql123 CALL sp_setup_technical_user('user1', 'password1')

Configuration at the Edge At the edge, after the deployment of BEF to the edge (as described in this document), the Asset Core synchronization service is available but not enabled. To enable the synchronization you must modify the service to be Automatic and start the service.


165


166

APPENDIX E: UI DEPLOYMENT FROM THE EDGE SERVICES (ES) CORE

HTTPS Data

Provider

ES

Synchronization

Service

BEF

Persistence

HTTPS Data

Consumers

Edge LocationES Busincess

Essential

Functions

R

Edge

Extender

UI Deployment

Persistence

UI Loader

R

R

AIN

External Cloud

Applications

ES CORE

The set up of the UI deployment consist of :

• Setting up the synchronization server in the digital core with the persistence for UI distributation

• Loading the UI required at the digital core

• Enabling the synchronization at the edge to bring down the UI elements

Setup at the Digital Core The set up of UI Deployment setup at the edge consist of the following:

1. Download the cloud integration software to the MobiLink server (com.sap.dep.ml_sqla).

2. Go to the directory ui_deployment and adjust the properties appropriately in build.properties. Currently the default synchronization server port is 6890 (ml.port).

3. Run the default ant target: ant


167

Loading Library for synchronization Setup at the Edge At the edge, after the deployment of BEF to the edge (as described in this document), the WEB UI synchronization service is available but not enabled. To enable the synchronization you must modify the service to be Automaic and start the service.

www.sap.com

© 2018 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

SAP Edge Services

Documents

Transcript of SAP Edge Services