SAP Shop Floor Dispatching and Monitoring Tool

Administrator's GuideSAP Shop Floor Dispatching and Monitoring Tool

Target Audience ■ System Administrators ■ Technology Consultants

CUSTOMERDocument version: 1.1 – 2013-05-15

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/

instguides.

The following table provides an overview of the most important document changes.

Version Date Description

1.1 2013-05-15 Updated version for SP01

2/34 CUSTOMER 2013-05-15

http://service.sap.com/instguides


Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 SAP Shop Floor Dispatching and Monitoring Tool Overview . . . . . . . . . . 7

2.1 Software Units of SAP Shop Floor Dispatching and Monitoring

Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.1 Minimal System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.2 Deployed Component Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 3 Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Overall Implementation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4 Operation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1 Monitoring of SAP Shop Floor Dispatching and Monitoring . . . . . . . . . . . . . . 13

4.1.1 Alert Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.2 Detailed Monitoring and Tools for Problem and Performance

Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.2.1 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.2.2 Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.2 Management of SAP Shop Floor Dispatching and Monitoring

Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.2.1 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.2.2 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2.3 Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2.4 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2.5 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.2.6 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.3 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3.1 Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3.2 Development Requests and Development Release Management . . . . . . . . . . . 17

4.3.3 Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . . 18

2013-05-15 CUSTOMER 3/34

Chapter 5 Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.2 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.3 Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.4 User Administration and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.4.1 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.4.2 User Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.4.3 Integration into Single Sign-On Environments . . . . . . . . . . . . . . . . . . . . . . . . 23

5.5 Network and Communication Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.5.1 Communication Chanel Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.5.2 Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.6 Data Storage Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.7 Other Security Relevant Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.8 Security Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4/34 CUSTOMER 2013-05-15

1 Getting Started

1.1 About this Document

Purpose

This Administrator's Guide is the central starting point for the technical implementation of SAP Shop

Floor Dispatching and Monitoring Tool. You can find cross-scenario implementation information as well as

scenario-specific information in this guide.

Use the Administrator’s Guide to get an overview of SAP Shop Floor Dispatching and Monitoring Tool, its

software units, and its scenarios from a technical perspective. The Administration Guide is a planning

tool that helps you to design your system landscape. It refers you to the required detailed

documentation.

The Administrator’s Guide is a single source of information to support the implementation and

operation of SAP Shop Floor Dispatching and Monitoring Tool.

The Master Guide consists of the following main sections:

■ Planning Information

The first two chapters of the Administrator’s Guide provide you with the most important

information regarding the implementation of SAP Shop Floor Dispatching and Monitoring Tool, including

an overview of the related planning information, its software units, the system landscape, and the

overall implementation sequence.

■ Installation Overview

This chapter gives you an overview of the installation components and the sequence in which they

are installed, as described in detail in the Installation Notes (1772981 and 1773352).

■ Operation Information

This chapter provides you with the information that you require to operate SAP Shop Floor Dispatching

and Monitoring Tool.

■ Security Information

This chapter provides you with the information that you require to operate SAP Shop Floor Dispatching

and Monitoring Tool securely.

Constraints

■ The business scenarios that are presented here serve as examples of how you can use SAP software

in your company. The business scenarios are only intended as models and do not necessarily run

the way they are described here in your customer-specific system landscape. Ensure to check your

requirements and systems to determine whether these scenarios can be used productively at your

1 Getting Started


2013-05-15 CUSTOMER 5/34

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1772981&_NLANG=en&_NVERS=0


site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems

to ensure they are complete and free of errors before going live.

■ This Master Guide primarily discusses the overall technical implementation of SAP Shop Floor

Dispatching and Monitoring Tool, rather than its subordinate components. This means that additional

software dependencies might exist without being mentioned explicitly in this document. You can

find more information on component-specific software dependencies in the corresponding

installation guides.

NOTE

You can find the most current information about the technical implementation of SAP Shop

Floor Dispatching and Monitoring Tool and the latest installation and configuration guides on SAP

Service Marketplace athttp://service.sap.com/instguides.

We strongly recommend that you use the documents available here. The guides are regularly

updated.

1 Getting Started


6/34 CUSTOMER 2013-05-15


2 SAP Shop Floor Dispatching and Monitoring Tool Overview

2.1 Software Units of SAP Shop Floor Dispatching and Monitoring Tool

The software units required for SAP Shop Floor Dispatching and Monitoring Tool are as follows:

■ SAP NetWeaver (7.0 - 7.31)

■ SAP ERP 6.0 (ECC 600 – ECC 606)

■ Shop Floor Dispatching and Monitoring Tool Add-on for ERP

■ Shop Floor Dispatching and Monitoring Tool Frontend Component

All components are mandatory.

2.2 System Landscape

The following section describes the various ways in which the system landscape for SAP Shop Floor

Dispatching and Monitoring Tool can be set up.

2.2.1 Minimal System Landscape

The following figure provides an overview of a minimal system landscape forSAP Shop Floor Dispatching

and Monitoring Tool.


2.1 Software Units of SAP Shop Floor Dispatching and Monitoring Tool

2013-05-15 CUSTOMER 7/34

Figure 1: Minimal System Landscape

2.2.2 Deployed Component Structure

This section describes the deployed component structure based on the lowest release (ECC 600) and

the highest release (ECC 606).

Figure 2: Deployed Component Structure (Lowest Release ECC 600)



8/34 CUSTOMER 2013-05-15

Figure 3: Deployed Component Structure (Highest Release ECC 606)



2013-05-15 CUSTOMER 9/34

This page is left blank for documents that are printed on both sides.

3 Installation Information

3.1 Overall Implementation Sequence

Purpose

The following table describes the overall installation sequence for SAP Shop Floor Dispatching and Monitoring

Tool. This table contains all available software units.

Note: For the latest component version and patch level requirements, see note 1772981 (server

components) and note 1773352 (client components). For all SP01 relevant information, see note

1779572.

Process

Implementation Sequence

StepAction[Required Documentation] Remarks/Subsequent Steps

1 SAP NetWeaver (7.0 – 7.31) Server component

2 SAP ERP 6.0 (ECC 600 – ECC 606) Server component

3 Shop Floor Dispatching and Monitoring Tool Add-on for ERP Server component

4 .NET Framework 4.0 Client component

5 Shop Floor Dispatching and Monitoring Tool Front-end Component Client component

3 Installation Information

3.1 Overall Implementation Sequence

2013-05-15 CUSTOMER 11/34




4 Operation Information

4.1 Monitoring of SAP Shop Floor Dispatching and Monitoring

Within the management of SAP Technology, monitoring is an essential task. A section has therefore

been devoted solely to this subject.

You can find more information about the underlying technology in the SAP Netweaver Administrator’s

Guide – Technical Operations Manual in the SAP Library under SAP Netweaver Library.

4.1.1 Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system

environment. SAP provides you with the infrastructure and recommendations needed to set up your

alert monitoring to recognize critical situations for SAP Shop Floor Dispatching and Monitoring Tool as quickly

as possible.

SAP Shop Floor Dispatching and Monitoring Tool does not offer specific data in the Computer Center

Management System (CCMS) for alert monitoring. Nevertheless general monitoring options can be

used.

In order to enable the auto-alert mechanism of CCMS, see SAP Note 617547.

4.1.2 Detailed Monitoring and Tools for Problem and Performance Analysis

4.1.2.1 Trace and Log Files

Trace files and log files are essential for analyzing problems.

Important Log and Trace files

Component Content File Path

Shop Floor Dispatching and Monitoring Frontend Component

Technical Exception Log

log.txt Frontend host:<UserDirectory>\AppData\Local\SAP\ShopFloorDispatcher\<Assemblynumber>

<UserDirectory>: This refers to the directory of the user data (e.g.: C:\Users\UserName)

< Assemblynumber > This refers to the build number of the application assembly (e.g.: 1.0.0.0)

The customer can display the log file using any text editor. Log files of front-end versions (build number)

no longer in use can be deleted.


4.1 Monitoring of SAP Shop Floor Dispatching and Monitoring

2013-05-15 CUSTOMER 13/34


4.1.2.2 Data Growth and Data Archiving Monitors

The SAP Shop Floor Dispatching and Monitoring Tool uses the standard tools for archiving and monitoring data

archiving available in SAP NetWeaver, and does not require an application-specific tool. For more

information, see the following sources:

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 3 SAP NetWeaver 7.0

Library (including Enhancement Package 3) English SAP NetWeaver Library SAP NetWeaver by Key Capability

Solution Life Cycle Management by Key Capability Data Archiving (CA-ARC)

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 3 SAP NetWeaver 7.0

Library (including Enhancement Package 3) English SAP NetWeaver Library SAP NetWeaver by Key Capability

Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS Data Archiving

Monitor

4.2 Management of SAP Shop Floor Dispatching and Monitoring Tool

SAP provides you with an infrastructure to help your technical support consultants and system

administrators effectively manage all SAP components and complete all tasks related to technical

administration and operation.

You can find more information about the underlying technology in the Technical Operations Manual

in the SAP Library under SAP NetWeaver.

4.2.1 Starting and Stopping

The Stop Sequence is in reverse order to the Start Sequence.

Start and Stop Sequences and Tools

Software Component Sequence Tool Detailed Description

SAP ERP 1 STARTSAP/ STOPSAP (Unix)Microsoft Management Console (Windows)

For more information, see the SAP NetWeaver Technical Operations Manual

General Administration TasksStarting and Stopping SAP

NetWeaver ABAP and Java.

SAP Shop Floor Dispatching and Monitoring Tool Add-On

2 STARTSAP/ STOPSAP (Unix)Microsoft Management Console (Windows)

For more information, see the SAP NetWeaver Technical Operations Manual

General Administration TasksStarting and Stopping SAP



14/34 CUSTOMER 2013-05-15

NetWeaver ABAP and Java .

For the list of components required for each scenario please refer to Chapter 2.

4.2.2 Software Configuration

This chapter explains which components or scenarios used by this application are configurable and

which tools are available for adjusting.

The Implementation Guide (IMG) is the standard SAP tool for component Customizing. To display

the Implementation Guide (IMG) on the SAP Easy Access screen choose Tools Customizing IMG

Execute Project (transaction SPRO) .

Customizing settings for SAP Shop Floor Dispatching and Monitoring can be found under Production

Shop Floor Control Dispatching and Monitoring Tool .

The appearance of the frontend component is configured via the frontend administration tool. For

details of the interaction between the frontend administration tool and the backend customizing

consult the application documentation under help.sap.com SAP Business Suite SAP ERP Add-Ons

Shop Floor Dispatching and Monitoring Tool .

4.2.3 Administration Tools

SAP Shop Floor Dispatching and Monitoring Tool is based on SAP NetWeaver. For more information, see the

Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com SAP NetWeaver

SAP NetWeaver 7.31 SAP NetWeaver Library Administrator’s Guide Technical Operations for SAP

NetWeaver .

4.2.4 Backup and Restore

For SAP Shop Floor Dispatching and Monitoring Tool, you can use the standard SAP tools and procedures for

systems based on SAP NetWeaver ABAP technology.

You need to back up your system landscape regularly to ensure that you can restore and recover it in

case of failure.

The backup and restore strategy for your system landscape should not only consider SAP systems but

should also be embedded in overall business requirements and incorporate your company’s entire

process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of

a data center through fire. It is most important in this context that you ensure that backup devices are

not lost together with normal data storage (separation of storage locations).



2013-05-15 CUSTOMER 15/34

■ The following table lists the components used by SAP Shop Floor Dispatching and Monitoring Tool and

how to back them up:

Component Data to be backed upBackup Method / Tool

Recommended Backup Frequency

Backup Sequence (if required)

SAP ERP (including SAP Shop Floor Dispatching and Monitoring Tool Add-on)

Database and log backup, application log backup (such as job logs in file system), data consistency with other systems must be considered ■ Backup of software, configuration, log files

See SAP ERP Application Operations Guide (see below).



The user settings of the frontend component are stored in the local user application data directory of

the windows operating system. It is recommended to backup this data within the windows backup.

4.2.5 Load Balancing

The SAP Shop Floor Dispatching and Monitoring Tool uses the standard functionality of SAP NetWeaver for

logon and load balancing. For more information on load balancing, see SAP Service Marketplace at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 3 -> System Administration

and Maintenance Information Technical Operation Guide General Administration Tasks High Availability Network

High Availability Web Server Networks and DMZs .

4.2.6 High Availability

SAP Shop Floor Dispatching and Monitoring Tool is part of SAP ERP, which means that all high

availability measures for SAP ERP also apply for SAP Shop Floor Dispatching and Monitoring Tool. In

particular, you can protect SAP Shop Floor Dispatching and Monitoring Tool from downtimes using

redundancy approaches such as installations on at least two different runtime environments or physical

machines. A load balancing or dispatching mechanism ensures that in case of a downtime of one

runtime or physical machine the remaining ones can handle all requests.

When a machine running SAP ERP crashes, users who are logged on to the SAP Shop Floor Dispatching

and Monitoring Tool user interface get error messages that the connection to SAP ERP has been lost.

For more information, see SAP Help Portal at http:// help.sap.com SAP NetWeaver SAP NetWeaver

7.0 including Enhancement Package 3 System Administration and Maintenance Information Technical Operation Guide

General Administration Tasks High Availability SAP NetWeaver AS ABAP: High Availability.



16/34 CUSTOMER 2013-05-15

http://help.sap.com

4.3 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and

testing procedures for complex software landscapes and multiple software development platforms.

These functions support your project teams, development teams, and application support teams.

The goal of Software Change Management is to establish consistent, solution-wide change management

that allows for specific maintenance procedures, global rollouts (including localizations), and open

integration with third-party products.

This section provides additional information about the most important software components.

The following topics are covered:

■ Transport and Change Management – Enables and secures the distribution of software changes

from the development environment to the quality assurance and production environment.

■ Development Request and Development Release Management – Enables customer-specific

maintenance procedures and open integration with third-party products.

■ Template Management – Enables and secures the rollout of global templates, including

localizations.

■ Quality Management and Test Management – Reduce the time, cost, and risk associated with

software changes.

■ Support Packages and SAP Notes Implementation – Provide standardized software distribution

and maintenance procedures.

■ Release and Upgrade Management – Reduces the time, cost, and risk associated with upgrades.

4.3.1 Transport and Change Management

The SAP Shop Floor Dispatching and Monitoring Tool ERP Add-on is client-enabled. For transport and change

management issues, the procedures of SAP NetWeaver apply. For more information, see SAP NetWeaver

documentation.

The SAP Shop Floor Dispatching and Monitoring Tool frontend component is installed locally using SAPsetup.

If you want to change the installation, you can rerun SAPsetup from Start Control Panel Add or Remove

Programs to add or remove the program.

4.3.2 Development Requests and Development Release Management

The standard procedures of SAP NetWeaver apply for the ERP Add-on of the SAP Shop Floor Dispatching

and Monitoring Tool. See the Technical Operations Manual for SAP NetWeaver on SAP Help Portal under

SAP NetWeaver.



2013-05-15 CUSTOMER 17/34

4.3.3 Support Packages and Patch Implementation

We recommend that you implement Support Package Stacks (SP Stacks), which are sets of support

packages and patches for the respective product version that must be used in the given combination.

The technology for applying support packages and patches will not change.

Read the corresponding Release and Information Notes (RIN) before you apply any support packages

or patches of the selected SP Stack. Use the Maintenance Optimizer (transaction DSWP) of the SAP

Solution Manager to select, download, and install the needed usages, or software components and

required support packages. For more information, see the following:

SAP Solution Manager documentation on SAP Help Portal at http:// help.sap.com/ SAP Solution

Manager Change Management Maintenance Optimizer

SAP Service Marketplace at http:// service.sap.com/ solman-mopz The documentation for

transaction SAINT (SAP Add-On Installation Tool) For more information about the implementation

of support packages as well as possible side effects, see http:// service.sap.com/ patches SAP Support

Packages in Detail

For more information about the tools necessary for implementing patches, see SAP NetWeaver

documentation.

The SAP Shop Floor Dispatching and Monitoring Tool front end component support packages, located on the

SAP Service Marketplace, are included in the complete product installation using SAPsetup. SAP Shop

Floor Dispatching and Monitoring Tool front end component support packages are cumulative and can be

installed over an existing installation as an upgrade.



18/34 CUSTOMER 2013-05-15

http://help.sap.com/

http://service.sap.com/solman-mopz

http://service.sap.com/patches

5 Security Information

5.1 Before You Start

The backend part of the SAP Shop Floor Dispatching and Monitoring Tool is built from the Production Order

Component in ERP and can be installed respectively used beginning with SAP ERP 6.0 and SAP

NEetWeaver 7.0 upward. Therefore, the corresponding Security Guides also apply to the Shop Floor

Dispatching and Monitoring Tool. Pay particular attention to the most relevant sections or specific

restrictions as indicated in the table below.

Fundamental Security Guides

Scenario, Application or Component Security Guide Most-Relevant Sections or Specific Restrictions

SAP NetWeaver http://service.sap.com/securityguide SAP NetWeaver SAP NetWeaver 7.0 (2004s)SAP NetWeaver 7.3 EhP1 Security Guide

SAP ERP 6.0 http:// service.sap.com/ securityguide SAP Business Suite Applications SAP ERP , for example, 6.0.

For a complete list of the available SAP Security Guides, see service.sap.com/securityguide on the

SAP Service Marketplace.

You can find a summary of the configuration steps for implementing security for the SAP Shop Floor

Dispatching and Monitoring Tool in the <Configuration Guide, Solution Manager>. See <provide link or

path>.

Additional Information

For more information about specific topics, see the Quick Links as shown in the table below.

Content Quick Link on the SAP Service Marketplace or SDN

Security sdn.sap.com/irj/sdn/security

Security Guides service.sap.com/securityguide

Related SAP Notes service.sap.com/notesservice.sap.com/securitynotes

Released platforms service.sap.com/pam

Network security service.sap.com/securityguide

SAP Solution Manager service.sap.com/solutionmanager

SAP NetWeaver sdn.sap.com/irj/sdn/netweaver


5.1 Before You Start

2013-05-15 CUSTOMER 19/34

http://service.sap.com/securityguide


5.2 Technical System Landscape

For more information about the technical system landscape, see the resources listed in the table below

and the System Landscape section above.

Topic Guide/ToolQuick Link to the SAP Service Marketplace or SDN

Technical description of the underlying components such as SAP NetWeaver

Master Guide service.sap.com/instguides

High availability High Availability for SAP Solutions

sdn.sap.com/irj/sdn/ha

Technical landscape design See applicable documents sdn.sap.com/irj/sdn/landscapedesign

Security See applicable documents sdn.sap.com/irj/sdn/security

5.3 Authorizations

The SAP Shop Floor Dispatching and Monitoring Tool uses the authorization concept provided by the SAP

NetWeaver AS ABAP. Therefore, the recommendations and guidelines for authorizations as described

in the SAP NetWeaver AS Security Guide ABAP also apply to the SAP Shop Floor Dispatching and Monitoring

Tool.

The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles.

For role maintenance, use the profile generator (transaction PFCG) on the AS ABAP and the User

Management Engine’s user administration console on the AS Java.

NOTE

For more information about how to create roles, see Role Maintenance [SAP Library]Standard

Roles

Standard Roles

There are no standard roles that are used by the SAP Shop Floor Dispatching and Monitoring Tool.

Standard Authorization Objects

The table below shows the security-relevant authorization objects that are used by the SAP Shop Floor

Dispatching and Monitoring Tool.

Standard Authorization Objects

Authorization Object Field Value Description

C_SFDM_DIS SFDMACT LOAD, SAVE Authorization for Shop Floor Dispatching and Monitoring


5.2 Technical System Landscape

20/34 CUSTOMER 2013-05-15

5.4 User Administration and Authentication

The SAP Shop Floor Dispatching and Monitoring Tool uses the user management and authentication

mechanisms provided with the SAP NetWeaver platform, in particular the SAP NetWeaver Application

Server ABAP. Therefore, the security recommendations and guidelines for user administration and

authentication as described in the SAP NetWeaver Application Server ABAP Security Guide [SAP Library]

also apply to the SAP Shop Floor Dispatching and Monitoring Tool.

In addition to these guidelines, we include information about user administration and authentication

that specifically applies to the SAP Shop Floor Dispatching and Monitoring Tool in the following topics:

■ User Management

This topic lists the tools to use for user management, the types of users required, and the standard

users that are delivered with the SAP Shop Floor Dispatching and Monitoring Tool.

■ User Data Synchronization

The SAP Shop Floor Dispatching and Monitoring Tool shares user data with other sources.. This topic

describes how the user data is synchronized with these other sources.

■ Integration into Single Sign-On Environments

This topic describes how the SAP Shop Floor Dispatching and Monitoring Tool supports Single Sign-On

mechanisms.

5.4.1 User Management

Use

User management for the SAP Shop Floor Dispatching and Monitoring Tool uses the mechanisms provided with

the SAP NetWeaver Application Server (ABAP), for example, tools, user types, and password policies. For

an overview of how these mechanisms apply for the SAP Shop Floor Dispatching and Monitoring Tool see the

sections below. In addition, we provide a list of the standard users required for operating the SAP Shop

Floor Dispatching and Monitoring Tool.

User Administration Tools

The table below shows the tools to use for user management and user administration with the SAP

SAP Shop Floor Dispatching and Monitoring Tool.

User Management Tools

Tool Detailed Description Prerequisites

User maintenance for ABAP-based systems (transaction SU01)

For more information about the authorization objects provided by the subcomponents of the SAP Shop Floor Dispatching and Monitoring Tool, see the relevant component in the section Authorizations.

N/a

Role maintenance with the profile generator for ABAP-based systems (PFCG)

For more information about the roles provided by the subcomponents of SAP Shop Floor Dispatching and Monitoring Tool, see the relevant component in the section Authorizations. For

N/a



2013-05-15 CUSTOMER 21/34

Tool Detailed Description Prerequisitesmore information, see User and Role Administration of Application Server ABAP

User Types

It is often necessary to specify different security policies for different types of users. For example, your

policy may specify that individual users who perform tasks interactively have to change their passwords

on a regular basis, but not those users under which background processing jobs run.

The user types that are required for the SAP Shop Floor Dispatching and Monitoring Tool include:

■ Individual users:

Dialog users are used for SAP GUI for Windows or RFC connections (which are used by the front-

end component to communicate with the back end)

■ Technical users:

● So far no service users are used for SAP Shop Floor Dispatching and Monitoring Tool

● So far no communication users are used for SAP Shop Floor Dispatching and Monitoring Tool

● So far, no background users are used for SAP Shop Floor Dispatching and Monitoring Tool

For more information on these user types, see User Types [SAP Library] in the SAP NetWeaver AS ABAP

Security Guide.

Standard Users

The table below shows the standard users that are necessary for operating the SAP Shop Floor Dispatching

and Monitoring Tool. No users are delivered with SAP Shop Floor Dispatching and Monitoring Tool. You need to

make sure that the users are available when you start to configure the application.

Standard Users

System User ID Type Password Description

System where SFDM is installed .

<User 1> Dialog user You specify the initial password during the installation.

The main SFDM user, needed for the SFDM functionality and other ERP-PP transactions.

NOTE

We recommend changing the user IDs and passwords for users that are automatically created

during installation.

5.4.2 User Data Synchronization

By synchronizing user data, you can reduce effort and expense in the user management of your system

landscape. Since SAP Shop Floor Dispatching and Monitoring Tool is based on SAP NetWeaver, you can use all

of the mechanisms for user synchronization in SAP NetWeaver here. For more information, see the

SAP NetWeaver Security Guide on SAP Service Marketplace at service.sap.com/securityguide

SAP NetWeaver .



22/34 CUSTOMER 2013-05-15

5.4.3 Integration into Single Sign-On Environments

The SAP Shop Floor Dispatching and Monitoring Tool supports the Single Sign-On (SSO) mechanisms provided

by SAP NetWeaver. Therefore, the security recommendations and guidelines for user administration

and authentication as described in the SAP NetWeaver Security Guide [SAP Library] also apply to the

SAP Shop Floor Dispatching and Monitoring Tool.

The most widely-used supported mechanisms are listed below.

■ Secure Network Communications (SNC)

SNC is available for user authentication and provides for an SSO environment when using the SAP

GUI for Windows or Remote Function Calls.

■ SAP logon tickets

The SAP Shop Floor Dispatching and Monitoring Tool back end component supports the use of logon tickets

for SSO when using a Web browser as the frontend client. In this case, users can be issued a logon

ticket after they have authenticated themselves with the initial SAP system. The ticket can then

be submitted to other systems (SAP or external systems) as an authentication token. The user does

not need to enter a user ID or password for authentication but can access the system directly after

the system has checked the logon ticket.

■ Client certificates

As an alternative to user authentication using a user ID and passwords, users using a Web browser

as a frontend client can also provide X.509 client certificates to use for authentication. In this case,

user authentication is performed on the Web server using the Secure Sockets Layer Protocol (SSL

Protocol) and no passwords have to be transferred. User authorizations are valid in accordance

with the authorization concept in the SAP system.

SAP logon tickets and client certificates are not supported by the current version of the front end

component.

For more information, about the available authentication mechanisms, see User Authentication and

Single Sign-On [SAP Library] in the SAP NetWeaver Library.

5.5 Network and Communication Security

Your network infrastructure is extremely important in protecting your system. Your network needs

to support the communication necessary for your business needs without allowing unauthorized

access. A well-defined network topology can eliminate many security threats based on software flaws

(at both the operating system and application level) or network attacks such as eavesdropping. If users

cannot log on to your application or database servers at the operating system or database layer, then

there is no way for intruders to compromise the machines and gain access to the backend system’s

database or files. Additionally, if users are not able to connect to the server LAN (local area network),

they cannot exploit well-known bugs and security holes in network services on the server machines.



2013-05-15 CUSTOMER 23/34

The network topology for the SAP Shop Floor Dispatching and Monitoring Tool is based on the topology used

by the SAP NetWeaver platform. Therefore, the security guidelines and recommendations described

in the SAP NetWeaver Security Guide also apply to the SAP Shop Floor Dispatching and Monitoring Tool. Details

that specifically apply to the SAP Shop Floor Dispatching and Monitoring Tool are described in the following

topics:

■ Communication Channel Security

This topic describes the communication paths and protocols used by the SAP Shop Floor Dispatching and

Monitoring Tool.

■ Network Security

This topic describes the recommended network topology for the SAP Shop Floor Dispatching and Monitoring

Tool. It shows the appropriate network segments for the various client and server components and

where to use firewalls for access protection. It also includes a list of the ports needed to operate the SAP

Shop Floor Dispatching and Monitoring Tool.

For more information, see the following sections in the SAP NetWeaver Security Guide:

■ Network and Communication Security [SAP Library]

■ Security Aspects for Connectivity and Interoperability [SAP Library]

5.5.1 Communication Chanel Security

The table below shows the communication channels used by the SAP Shop Floor Dispatching and Monitoring

Tool, the protocol used for the connection, and the type of data transferred.

Communication Path Protocol Used Type of Data TransferredData Requiring Special Protection

Frontend client using SAP GUI for Windows to application server

RFC, HTTP(S) Configuration data Passwords

Frontend client using SAP .NET Connector to application server

RFC All application data Passwords

DIAG and RFC connections can be protected using Secure Network Communications (SNC). HTTP

connections are protected using the Secure Sockets Layer (SSL) protocol.

For more information, see Transport Layer Security [SAP Library] in the SAP NetWeaver Security Guide.

5.5.2 Network Security

Your network infrastructure plays a key role in protecting your system. A well-defined network

topology can eliminate many security threats based on software flaws (at the operating system and

application level) or network attacks such as eavesdropping. We offer general recommendations to

protect your system landscape, based on SAP NetWeaver.

NOTE



24/34 CUSTOMER 2013-05-15

For information about network security for SAP NetWeaver, see the SAP NetWeaver Security Guide

on SAP Service Marketplace at http:// service.sap.com/ securityguide

A minimum security demand for your network infrastructure is the use of a firewall for all your services

that are provided over the Internet. A more secure variant is to protect your systems (or groups of

systems) by locating the system groups in different network segments. Each system group has a firewall

that protects it from unauthorized access. External security attacks can also come from the inside, if

the intruder has already taken control of one of your systems.

NOTE

For information about access control using firewalls, see the SAP NetWeaver Security Guide on SAP

Help Portal at http:// service.sap.com/ securityguide SAP NetWeaver SAP NetWeaver 7.0 EhP3

Security Guides (Online Version) SAP NetWeaver Security Guide Network and Communication Security Using

Firewall Systems for Access Control .

5.6 Data Storage Security

SAP Shop Floor Dispatching and Monitoring Tool does not use personalized data. Business and configuration

data is stored in the database of the SAP system. User-specific settings, such as layout settings, for the

front-end component are stored in the file system of the front-end client host.

5.7 Other Security Relevant Information

SAP Shop Floor Dispatching and Monitoring Tool uses active code – HTML and JavaScript – on the front-end

client to enable the information area of the text templates. If the security policy does not allow the use

of active code, the customer has to use/create text templates without JavaScript, which may result in

loss of functionality and flexibility

5.8 Security Logging and Tracing

The trace and log files of SAP Shop Floor Dispatching and Monitoring Tool use the standard mechanisms of SAP

NetWeaver. For more information, see the following sections in the SAP NetWeaver Security Guide at

service.sap.com/securityguide Auditing and Logging .

If there is no information about trace and log files in the sections for the individual components of SAP

Shop Floor Dispatching and Monitoring Tool, you can assume that no sensitive data is updated in these files.


5.6 Data Storage Security

2013-05-15 CUSTOMER 25/34



A Reference

A.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various

phases in the life cycle of SAP software.

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.

■ Target group:

● Relevant for all target groups

■ Current version:

● On SAP Help Portal at http://help.sap.com Glossary

● In the SAP system in transaction STERM

SAP Library is a collection of documentation for SAP software covering functions and processes.

■ Target group:

● Consultants

● System administrators

● Project teams for implementations or upgrades


● On SAP Help Portal at http://help.sap.com (also available as documentation DVD)

The security guide describes the settings for a medium security level and offers suggestions for raising

security levels. A collective security guide is available for SAP NetWeaver. This document contains

general guidelines and suggestions. SAP applications have a security guide of their own.

■ Target group:


● Technology consultants

● Solution consultants


● On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable

units for each business or IT scenario. It provides scenario-specific descriptions of preparation,

A Reference


2013-05-15 CUSTOMER 27/34

http://help.sap.com

http://help.sap.com


execution, and follow-up of an implementation. It also provides references to other documents, such

as installation guides, the technical infrastructure guide and SAP Notes.

■ Target group:


● Project teams for implementations


● On SAP Service Marketplace at http://service.sap.com/instguides

The installation guide describes the technical implementation of an installable unit, taking into

account the combinations of operating systems and databases. It does not describe any business-related

configuration.

■ Target group:





Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle

platform. One of its main functions is the configuration of business scenarios, business processes, and

implementable steps. It contains Customizing activities, transactions, and so on, as well as

documentation.

■ Target group:





● In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The

Customizing activities and their documentation are structured from a functional perspective. (In order

to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager,

which refers to the relevant Customizing activities in the individual SAP systems, is used.)

■ Target group:


● Project teams for implementations or upgrades


● In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP

NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers

A Reference


28/34 CUSTOMER 2013-05-15



users to the tools and documentation that are needed to carry out various tasks, such as monitoring,

backup/ restore, master data maintenance, transports, and tests.

■ Target group:




The application operations guide is used for operating an SAP application once all tasks in the

technical operations manual have been completed. It refers users to the tools and documentation that

are needed to carry out the various operations-related tasks.

■ Target group:






Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and processes of

an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of

an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.

■ Target group:


● Project teams for upgrades



The upgrade guide describes the technical upgrade of an installable unit, taking into account the

combinations of operating systems and databases. It does not describe any business-related

configuration.

■ Target group:





Release notes are documents that contain short descriptions of new features in a particular release or

changes to existing features since the previous release. Release notes about ABAP developments are the

technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide

(IMG).

■ Target group:

A Reference


2013-05-15 CUSTOMER 29/34





● Consultants



● On SAP Service Marketplace at http://service.sap.com/releasenotes

● In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

A Reference


30/34 CUSTOMER 2013-05-15

http://service.sap.com/releasenotes

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2013-05-15 CUSTOMER 31/34

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

DisclaimerPlease see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

32/34 CUSTOMER 2013-05-15

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

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


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

SAP Shop Floor Dispatching and Monitoring Tool

Documents

Transcript of SAP Shop Floor Dispatching and Monitoring Tool