Sunteți pe pagina 1din 47

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8

Operation Guide

Guide SAP ® Applications by PROLOGA 4.8 Operation Guide © PROLOGA GmbH SAP ® Applications by
Guide SAP ® Applications by PROLOGA 4.8 Operation Guide © PROLOGA GmbH SAP ® Applications by
Guide SAP ® Applications by PROLOGA 4.8 Operation Guide © PROLOGA GmbH SAP ® Applications by

SAP ® Applications by PROLOGA 4.8 Operation Guide

© Copyright 2011 PROLOGA GmbH 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 PROLOGA GmbH contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1® and Motif® are registered trademarks of Open Group.

Citrix®, the Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and and other names of Citrix products are registered trademards of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP®, R/3®, mySAP™, mySAP.com®, SAP® xApps, SAP® xApp™, SAP NetWeaver™, 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 in several other countries all over the world.

PROLOGA GmbH is a registered trademark of PROLOGA GmbH in Germany. All other product and service names mentioned are the trademarks of their respective companies.

Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice.

These materials are provided by PROLOGA GmbH for informational purposes only, without representation or warranty of any kind, and PROLOGA GmbH shall not be liable for errors or omissions with respect to the materials.

The only warranties for PROLOGA GmbH 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 ® Applications by PROLOGA 4.8 Operation Guide

Table of Contents

1

Getting Started

6

1.1

About this Guide

6

1.2

Global Definitions

6

1.3

Important SAP Notes

7

1.4

History of Changes

7

1.5

Support Packages

8

2

Configuration and Customization

9

2.1

SAP ® Legal Requirements by PROLOGA

9

2.2

SAP ® Dispatching and Planning Longterm Planning by PROLOGA

9

2.3

SAP ® Dispatching and Planning Operational Planning by PROLOGA

9

2.4

SAP ® Mobile Order Management by PROLOGA

9

2.5

SAP ® Smart Meter Rollout for Utilities by PROLOGA

10

3

Technical System Landscape High Level Overview

11

4

Monitoring

13

4.1

Alert Monitoring Concept

13

4.2

Performance Analysis

15

4.2.1

Starting SQL trace analysis

16

4.2.2

Example: How to analyze Operational Planning

16

4.3

Logging and Tracing Concept

20

4.3.1

Application Logging

20

4.3.2

System Logging and Tracing

21

4.3.2.1

Trace Functions

21

4.3.2.2

System Log

21

5

Management of SAP ® Applications by PROLOGA 4.8

23

5.1

Starting and Stopping

23

5.2

Backup and Restore

23

5.3

System Copy

23

5.4

Periodic Task

23

5.5

User Management

23

5.5.1

Role Concept

29

5.5.1.1

/WATP/PROLOGA_CUSTOMIZING (for consultants, administrators)

30

5.5.1.2

/WATP/WASTE_LEGAL_REQ_WITH_PRO (for commercial clerks)

31

5.5.1.3

/WATP/WASTE_LEGAL_REQ_NOPROFIL

32

5.5.1.4

/WATP/ONBOARD_COMPUTER (for commercial clerks)

32

5.5.1.5

/WATP/ROUTEPLANNING (for commercial clerks)

32

5.5.1.6

/WATP/SAMMELROLLE_MITPROFIL (commercial clerk)

33

5.5.1.7

/WATP/SAMMELROLLE_OHNEPROFIL (mainly for "powerful" users)

33

5.5.1.8

/WATP/USERS_OWN_DATA (commercial clerk)

34

5.5.2

Authorization Objects

34

5.5.2.1

Example: Waste Approval Management

35

5.5.3

Archiving

36

5.5.3.1

Principles of PROLOGA‟s Archiving

36

5.5.3.2

Principles of PROLOGA‟s Deletion Process

38

5.6

Logging of Security Relevant Events

39

5.7

Communication Channels and Communication Security

39

5.8

Security Statements/Guidelines for Included 3rd Party Applications

39

5.9

Security Statements/Guidelines

40

6

High Availability

42

7

Appendix

44

7.1

Customizing Tables

44

7.2

Authorization Objects delivered with the Add-on

47

SAP ® Applications by PROLOGA 4.8 Operation Guide

Table of Figures

Figure 1: High level overview waste and recycling industry

11

Figure 2: High level scenario with other SAP ® standard modules

11

Figure 3: feasible solution of a system landscape for the PROLOGA Add-on

12

Figure 4: feasible solution of a system landscape for the PROLOGA Add-on by using Google Maps

12

Figure 5: Applying the SAP ® monitor template for the operating system

13

Figure 6: CPU monitoring

14

Figure 7: CPU analysis of a typical test system of PCSS

14

Figure 8: Fundamentals of ABAP ® monitoring

15

Figure 9: Activate system trace

16

Figure 10: Date and planner group selection dialog

16

Figure 11: Main screen of operational planning

16

Figure 12: Tree with expanded nodes

17

Figure 13: Deactivating SQL trace

17

Figure 14: Display trace

18

Figure 15: Assigning filter for displaying trace

18

Figure 16: Example of a trace

19

Figure 17: Detailed execution plan

19

Figure 18: User management screen (transaction SU01)

24

Figure 19: User management screen (transaction SU01)

25

Figure 20: Role assignment (transaction SU01)

25

Figure 21: Additional information about user management in SAP ® help portal

26

Figure 22: Additional information about identity management in SAP ® help portal

26

Figure 23: Additional information about authorization concepts in SAP ® help portal

27

Figure 24: Different role selection

28

Figure 25: Additional information about locking/unlocking users

29

Figure 26: Role

/WATP/PROLOGA_CUSTOMIZING

30

Figure 27: Role /WATP/WASTE_LEGAL_REQ_WITH_PRO

31

Figure 28: Role /WATP/ONBOARD_COMPUTER

32

Figure 29: Role /WATP/ROUTEPLANNING

33

Figure 30: Select authorization object

35

Figure 31: Display authorization objects

35

Figure 32: Change authorization objects

36

Figure 33: Overview PROLOGA Archiving

37

Figure 34: Example of archiving frame

37

Figure 35: Object hierarchy of /watp/base_admin

38

Figure 36: Display log

38

Figure 37: Logging of security relevant objects

39

Figure 38: Security statements 1

40

Figure 39: Transaction SE80 I

40

Figure 40: Transaction SE80 II

41

Figure 41: Source SAP ® Library; TOM Netweaver

42

Figure 42: Source SAP ® Library; TOM NW; SAP Notes

43

Figure 43: Customizing and configuration data I

44

Figure 44: Customizing and configuration data II

45

Figure 45: Customizing and configuration data III

46

Figure 46: Authorization Objects delivered with the Add-on

47

 

Table Overview

Table

1: Important SAP Notes

7

Table 2: Most important changes in prior PROLOGA Add-ons

8

Table 3: Logging objects of PROLOGA Add-on

20

SAP ® Applications by PROLOGA 4.8 Operation Guide

Glossary

Attention Applications by PROLOGA 4.8 – Operation Guide Glossary Note © PROLOGA GmbH SAP ® Applications by

Note by PROLOGA 4.8 – Operation Guide Glossary Attention © PROLOGA GmbH SAP ® Applications by PROLOGA

SAP ® Applications by PROLOGA 4.8 Operation Guide

1 Getting Started

by PROLOGA 4.8 – Operation Guide 1 Getting Started This guide does not replace the daily

This guide does not replace the daily operations hand book that we recommend customers create for their specific production operations.

1.1 About this Guide

Designing, implementing, and running your SAP ® Applications by PROLOGA will give you the opportunity to increase the performance of your business processes in the best way and to fulfill the demands of your local government at treating the waste materials.

This guide provides a starting point for managing your mySAP solutions and maintaining and running them optimally. It contains specific information on various tasks and lists the tools that you can use to implement them. This guide also provides references to the documentation required for these tasks, so you will sometimes also need to consult other guides such as the Master Guide, the Customizing and Configuration Documentation of:

SAP ® Legal Requirements by PROLOGA , ® Legal Requirements by PROLOGA,

SAP ® Dispatching & Planning - Longterm Planning by PROLOGA , ® Dispatching & Planning - Longterm Planning by PROLOGA,

SAP ® Smart Meter Rollout for Utilities by PROLOGA , ® Smart Meter Rollout for Utilities by PROLOGA,

SAP ® Dispatching & Planning - Operational Planning by PROLOGA and ® Dispatching & Planning - Operational Planning by PROLOGA and

SAP ® Mobile Order Management by PROLOGA and Implementation of SAP ® Applications by PROLOGA (PCSS). ® Mobile Order Management by PROLOGA and Implementation of SAP ® Applications by PROLOGA (PCSS).

Target Groups:

Technical ConsultantsSAP ® Applications by PROLOGA (PCSS). Target Groups: System Administrators Solution Consultants Business Process

System Administratorsby PROLOGA (PCSS). Target Groups: Technical Consultants Solution Consultants Business Process Owners Support

Solution ConsultantsTarget Groups: Technical Consultants System Administrators Business Process Owners Support Specialists The PROLOGA

Business Process OwnersConsultants System Administrators Solution Consultants Support Specialists The PROLOGA Add-on is technically fully

Support SpecialistsAdministrators Solution Consultants Business Process Owners The PROLOGA Add-on is technically fully integrated into the

The PROLOGA Add-on is technically fully integrated into the SAP ® ERP system and does not require any special technical configuration (e.g. in the server profiles or on database level)

1.2 Global Definitions

server profiles or on database level) 1.2 Global Definitions It„s recommended to read:

It„s recommended to read:

Terms_and_Definitions_of_SAP_Applications_by_PROLOGA_4.8.pdf.

This document gives an overview of all important terms and definitions of the Add-on.

Knowledge of business processes (e.g. waste and recycling industry) and maintenance of SAP ® solutions is required.

SAP ® Applications by PROLOGA 4.8 Operation Guide

1.3 Important SAP Notes

by PROLOGA 4.8 – Operation Guide 1.3 Important SAP Notes Check regularly which SAP ® Notes

Check regularly which SAP ® Notes are available for the Solution Operation Guide.

SAP Note Number

Title

1375005

Composite note SAP ® Applications by PROLOGA 4.8

1375003

How to get a licence key for PROLOGA add on

1375009

Prerequisites for installing AddOn V4.8

Table 1: Important SAP Notes

1.4 History of Changes

V4.8 Table 1: Important SAP Notes 1.4 History of Changes Make sure you use the current

Make sure you use the current version of the Solution Operation Guide. The current version of the Solution Operation Guide can be found on the SAP Service Marketplace at http://service.sap.com.

The following table provides an overview of the most important changes in prior versions.

Version

Important Changes

1.0

First version of the SAP ® Applications by PROLOGA Solution Operation Guide

2.0

SAP ® Legal Requirements by PROLOGA

Catalogue exchange provides an interface to exchange local and customer-made waste (material) catalogues. The direct usage of approval in service frequency is a simplification in the service frequency maintenance process. Instead to create a note template the customer can enter the approval number. The functionality for archiving of waste notes is prepared.

SAP ® Route and District Management for Waste and Recycling by PROLOGA

The new release provides new functionalities for dispatching different types of orders. This capability supports the customer in implementing processes for a variety of different business scenarios. Managing different order types (waste disposal orders, deliveries and customer service orders) under the same planning interface is enabled. Planned resources are checked against availability (SAP-HR and SAP-PM integration). The short term planning provides an overview about a planning time line, the service location of the orders and details regarding single orders. Third party products, such as map material by PTV or a Geographical Information System may be integrated to the software through interfaces.

SAP ® Mobile Order Management by PROLOGA

The new release provides broader opportunities to manage the fleet regarding administration client front-end software at the vehicles, like remote software updates and maintenance of releases. It provides new features for system administrators to install a new release or to roll-out the software for a business unit. The technology on which the software is based on has got new features to scale the communication (sending and receiving orders and messages) and to confirm executed orders.

Support for SAP ® EhP2

With release 2.0 functional changes of SAP ® Waste and Recycling delivered in SAP ® EhP2 are fully supported.

3.0

The Add-on contains specific waste and recycling functions even generic functions for operational

© PROLOGA GmbH SAP ® Applications by PROLOGA 4.8

Page 7 of 47 Operation Guide

SAP ® Applications by PROLOGA 4.8 Operation Guide

planning and mobile order management.

Therefore the Add-on was renamed to SAP ® Applications by PROLOGA.

The component SAP ® Route and District Management for Waste and Recycling by PROLOGA

This component was splitted in Release 4.8 in three separate components:

1.

SAP ® Dispatching & Planning - Longterm Planning by PROLOGA contains the longterm planning

especially for the waste and recycling industry

2.

SAP ® Dispatching & Planning - Operational Planning by PROLOGA contains generic functions even

special functions for the waste and recycling market.

3.

SAP ® Smart Meter Rollout for Utilities by PROLOGA based on the existing longterm planning and

was enhanced for the special one time process smart meter rollout.

Table 2: Most important changes in prior PROLOGA Add-ons

1.5 Support Packages

changes in prior PROLOGA Add-ons 1.5 Support Packages Make sure that you only use official releases

Make sure that you only use official releases of the PROLOGA Add-on. The PROLOGA Add-on follows the SAP ® strategy regarding support packages.

Please

at:

contact

the

PROLOGA

administration

for

available

versions

SAP ® Applications by PROLOGA 4.8 Operation Guide

2 Configuration and Customization

Before you can use SAP ® Applications by PROLOGA you have to customize and configure the acquired components.

you have to customize and configure the acquired components. The PROLOGA Add-on includes enhancements of the

The PROLOGA Add-on includes enhancements of the existing SAP ® industry solution SAP ® Waste and Recycling. Before you start customizing this Add-on you have to customize the standard business processes of SAP ® Waste and Recycling as described in the appropriate documentation (transaction SPRO)

2.1 SAP ® Legal Requirements by PROLOGA

The customization/configuration of this component is described in:

SAP_Legal_Requirements_by_PROLOGA_Configuration_Guide_4.8.pdf.

After finishing the customizing you can start using the component by managing your waste manifests as described in the user manual.

2.2 SAP ® Dispatching and Planning Longterm Planning by PROLOGA

Customization/configuration of this component is described in:

SAP_Dispatching_&_Planning_Longterm_Planning_by_PROLOGA_Configuration_Guide_4.8.pdf.

We recommend using a digital map component to tap the full potential of this component and maximize efficiency. An SAP ® certified digital map solution is available from PTV AG. There exist the additional opportunity to link to other maps like GIS systems via WMS and WFS, Google Maps and bing. See also document SAP_MapConfig_by_PROLOGA_Configuration_Guide_4.8.pdf.

2.3 SAP ® Dispatching and Planning Operational Planning by PROLOGA

Customization/configuration of this component is described in:

SAP_Dispatching_&_Planning_Operational_Planning_by_PROLOGA_Configuration_Guide_4.8.pdf.

We recommend using a digital map component to tap the full potential of this component and maximize efficiency. An SAP ® certified digital map solution is available from PTV AG. There exist the additional opportunity to link to other maps like GIS systems via WMS and WFS, Google Maps and bing. See also document SAP_MapConfig_by_PROLOGA_Configuration_Guide_4.8.pdf.

2.4 SAP ® Mobile Order Management by PROLOGA

Customization/configuration of this component is described in:

SAP_Mobile_Order_Management_by_PROLOGA_Configuration_Guide_4.8.pdf.

The customizing is splitted in several parts and includes basic customizing of SAP ® standard objects (like technical object types) and component specific customizing. The customizing of the module is to be implemented with the transaction /WATP/BC_CONFIG.

Prerequisite for applying the SAP ® Mobile Order Management by PROLOGA application is the implementation of the SAP ® Dispatching and Planning - Operational Planning by PROLOGA application.

SAP ® Applications by PROLOGA 4.8 Operation Guide

2.5 SAP ® Smart Meter Rollout for Utilities by PROLOGA

Configuration of this component is described in:

SAP_Smart_Meter_Rollout_for_Utilities_by_PROLOGA_Configuration_Guide_4.8.pdf.

The user manual of the component can be found in document:

SAP_Smart_Meter_Rollout_for_Utilities_by_PROLOGA_User_Manual_4.8.pdf.

We recommend using a digital map component to tap the full potential of this component and maximize efficiency. An SAP ® certified digital map solution is available from PTV AG. There exist the additional opportunity to link to other maps like GIS systems via WMS and WFS, Google Maps and bing. See also document SAP_MapConfig_by_PROLOGA_Configuration_Guide_4.8.pdf.

SAP ® Applications by PROLOGA 4.8 Operation Guide

3 Technical System Landscape High Level Overview

As mentioned above the PROLOGA Add-on is fully integrated in the SAP ® system. The modules are connected to the BADI‟s published by SAP ® . The following picture is a high level overview dedicated to the waste and recycling industry:

SAP ECC 6.04 ABAP SAP Applications by PROLOGA SAP Dispatching & SAP Dispatching & SAP
SAP ECC 6.04
ABAP
SAP Applications by PROLOGA
SAP Dispatching &
SAP Dispatching &
SAP Mobile Order
SAP Legal
Planning -
Planning -
Management
Requirements
Longterm
operational planning
application
application
Planning
Facility
Treatment and
Dispatching and
Order Management
Order Management
management/
disposal
route planning
weighing system
SAP Waste And Recycling

Figure 1: High level overview waste and recycling industry

The component for the smart meter rollout is especially dedicated to a mass roll out of technical devices. The picture below provides an overview about the high level scenario combined with the other modules for the process.

SAP ECC 6.04 ABAP SAP Applications by PROLOGA SAP Dispatching & SAP Mobile Order SAP
SAP ECC 6.04
ABAP
SAP Applications by PROLOGA
SAP Dispatching &
SAP Mobile Order
SAP Smart Meter
Planning -
Management
Rollout for Utilities
operational planning
application
Sales and
Material
Order Management
Plant maintenance
ISU
distribution
Management
SAP standard modules

Figure 2: High level scenario with other SAP ® standard modules

SAP ® Applications by PROLOGA 4.8 Operation Guide

The following picture illustrates the system landscape as it is described in the technical product fact sheets of PCSS. The picture is an example for the use of PTV.

Another option is the use of a GIS (as ESRI or openGIS) system which provides maps and functions as WMS or WFS. In this case the external SAP Netweaver is needless.

or WFS. In this case the external SAP Netweaver is needless. SAP ERP 6.0 with EhP4
SAP ERP 6.0 with EhP4 Optimized route and dist. plan.
SAP ERP 6.0 with EhP4
Optimized route and dist. plan.
SAP ERP 6.0 with EhP4 Optimized route and dist. plan. Road map server computer with Windows
Road map server computer with Windows Server2003 SAP Kernel 7.01 patchlevel 110 UNIX or Linux

Road map server computer with

Windows Server2003

SAP Kernel 7.01 patchlevel 110

UNIX or Linux cannot be used for this purpose

SAP_BASIS 7.01 SP 7

SAP_APPL 6.04 SP 7

PTV

( xMap Serve)r

SAP IGS

( Internet Graphics Serve)r

PTV

PTV

( xLocate Serve)r

( xRoute Serve)r

PTV

( Roadmap materia)l

xLocate Serve)r ( xRoute Serve)r PTV ( Roadmap materia)l RFC link to SAP gateway IS- UT

RFC link to

SAP gateway

IS- UT 6.04 SP 7

SPAM/SAINT 7.01 SP 40

Legal requirements

Mobile order management

SAP database

The IGS communicates via RFC with the gateway of the ERP

6. 0 system.

The road map data can then be displayed in the

ERP system,

and geocoding and routing can be performed

based on the PTV map da.ta Instead of PTV eServer,sthe

newer PTV xServers can be use(d at least in the near

future).

Figure 3: feasible solution of a system landscape for the PROLOGA Add-on

Map Web Service provided by Google

or Microsoft

Add-on Map Web Service provided by Google or Microsoft SAP ERP 6.0 with EhP4 SAP Kernel

SAP ERP 6.0 with EhP4

SAP Kernel 7.01 patchlevel 110

SAP_BASIS 7.01 SP 7

SAP_APPL 6.04 SP 7

 

IS- UT 6.04 SP 7

SPAM/SAINT 7.01 SP 40

Legal requirements Mobile order management

Legal requirements

Mobile order management

RFC link to

SAP gateway

 

SAP database

© PROLOGA GmbH SAP ® Applications by PROLOGA 4.8
© PROLOGA GmbH SAP ® Applications by PROLOGA 4.8
© PROLOGA GmbH SAP ® Applications by PROLOGA 4.8

© PROLOGA GmbH SAP ® Applications by PROLOGA 4.8

RFC link to SAP gateway   SAP database © PROLOGA GmbH SAP ® Applications by PROLOGA
Optimized route and dist. plan.
Optimized route and dist. plan.

Figure 4: feasible solution of a system landscape for the PROLOGA Add-on by using Google Maps

The choice of the map service depends usually on the customer preferences or already existing GIS solutions.

Page 12 of 47 Operation Guide

SAP ® Applications by PROLOGA 4.8 Operation Guide

4 Monitoring

4.1 Alert Monitoring Concept

The CCMS is fully integrated in the SAP ® solution. Administrators and developers can monitor the complete solution within the SAP ® Alert Monitor (transaction RZ20).

As the PROLOGA Add-on is technically fully integrated in the SAP ® ERP system, there are no additional resources such as memory caches, queues etc. deployed. Therefore, the PROLOGA Add-on does not require any special CCMS monitoring. Instead the already existing standard CCMS monitoring tools can be used.

You can monitor the system by using the SAP ® standard templates for system monitoring.

the SAP ® standard templates for system monitoring. Figure 5: Applying the SAP ® monitor template

Figure 5: Applying the SAP ® monitor template for the operating system

You can execute the different methods as described in the SAP ® standard dialog.

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 6: CPU monitoring The following screenshot

Figure 6: CPU monitoring

The following screenshot illustrates the result of the CPU analysis as described above.

the result of the CPU analysis as described above. Figure 7: CPU analysis of a typical

Figure 7: CPU analysis of a typical test system of PCSS

Figure 7: CPU analysis of a typical test system of PCSS In addition to the available

In addition to the available SAP ® monitoring templates administrators may build their individual monitor templates.

For further information on alert monitoring go to:

© PROLOGA GmbH SAP ® Applications by PROLOGA 4.8

Page 14 of 47 Operation Guide

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 8: Fundamentals of ABAP ® monitoring

Figure 8: Fundamentals of ABAP ® monitoring

4.2 Performance Analysis

As the PROLOGA Add-on was developed with SAP ® development tools and in compliance with the SAP ® development standards, you can use the transactions provided by SAP ® for performance analysis.

provided by SAP ® for performance analysis. Please use the standard SAP ® SQL trace functionality

Please use the standard SAP ® SQL trace functionality for analyzing the SQL statements which are used in a PROLOGA transaction.

The standard SAP ® SQL trace functionality (transaction ST05) can be applied for analyzing the SQL statements used by PROLOGA transactions. This is useful for performance analyses aiming at optimizing the efficiency of the PROLOGA transactions.

SAP ® Applications by PROLOGA 4.8 Operation Guide

4.2.1 Starting SQL trace analysis

Start transaction ST05 and set marker in SQL trace check box.

transaction ST05 and set marker in SQL trace check box. Figure 9: Activate system trace After

Figure 9: Activate system trace

After the SQL trace is switched on (Activate Trace), you can execute the transaction you want to investigate in a second session.

4.2.2 Example: How to analyze Operational Planning

1. Start the transaction /WATP/TP01 in a second session (select transaction from tree or enter

/N/WATP/TP01).

(select transaction from tree or enter /N/WATP/TP01 ). Figure 10: Date and planner group selection dialog

Figure 10: Date and planner group selection dialog

2. Click on the green check mark.

group selection dialog 2. Click on the green check mark. Figure 11: Main screen of operational

Figure 11: Main screen of operational planning

SAP ® Applications by PROLOGA 4.8 Operation Guide

3. Expand a node in the tree on the left.

Operation Guide 3. Expand a node in the tree on the left. Figure 12: Tree with

Figure 12: Tree with expanded nodes

4. Switch back to your first session and deactivate the SQL trace.

back to your first session and deactivate the SQL trace. Figure 13: Deactivating SQL trace ©

Figure 13: Deactivating SQL trace

SAP ® Applications by PROLOGA 4.8 Operation Guide

5. Click on Display Trace to show the SQL trace.

Guide 5. Click on Display Trace to show the SQL trace. Figure 14: Display trace Figure

Figure 14: Display trace

Trace to show the SQL trace. Figure 14: Display trace Figure 15: Assigning filter for displaying

Figure 15: Assigning filter for displaying trace

SAP ® Applications by PROLOGA 4.8 Operation Guide

6. Click on the green check mark. The usual SQL trace display appears, showing how SAP ® standard tables and PROLOGAs /WATP/ tables are accessed by SQL statements.

and PROLOGAs /WATP/ tables are accessed by SQL statements. Figure 16: Example of a trace 7.

Figure 16: Example of a trace

7. For further investigations and detailed analysis you can call the Execution Plan for an SQL statement.

you can call the Execution Plan for an SQL statement. Figure 17: Detailed execution plan ©

Figure 17: Detailed execution plan

SAP ® Applications by PROLOGA 4.8 Operation Guide

4.3 Logging and Tracing Concept

SAP ® systems keep a variety of logs for system administration, monitoring, problem solving, and auditing purposes. Audits and logs are important for monitoring the security of your system and to track events in case of problems.

Due to the fact that the PROLOGA Add-on is fully integrated in the SAP ® environment you can use standard SAP ® functionality to log and trace the behavior of the Add-on and the entire system.

4.3.1 Application Logging

Application logging records the progress of the execution of an application so that you are able to reconstruct the processing if required. While the system log records system events (information about program and transaction terminations, database errors, etc), you can use the application log to record application specific event and problem messages relating to objects. Use the transaction SLG0 to configure the application log. With the transaction SLG1 to you can display and analyze the application log.

The application log is a table structure consisting of several tables. Application related entries are written to these tables using SAP ® function modules.

The where-used list provides information on who accessed the function modules (call report RSFKT100; function group: SLG0).

The following logging objects are included in the PROLOGA Add-on.

Object

Subobject

Description

/WATP/DEFAULT

 

General logging object for the whole Add-on

 

/WATP/DEFAULT

Default message log

 

/WATP/ADMTASK

Administration

 

/WATP/ARCHIVE

Archiving

 

/WATP/UPGRADEADJUST

Upgrade processes

/WATP/ARB

 

Logging object for SAP ® Legal Requirements by PROLOGA

 

/WATP/DEFAULT

Default message log

/WATP/BC

 

Logging object for SAP ® Mobile Order Management by PROLOGA

 

/WATP/DEFAULT

Default message log

 

/WATP/ADMIN

Administration

 

/WATP/ARCHIVE

Archiving

 

/WATP/CONFIRM

Confirmation

 

/WATP/IMPEXP

Im-/Export

/WATP/CS_CIC

 

Logging object for Cluster Builder

 

/WATP/CS_CIC

CIC processes

/WATP/TP

 

Logging object for SAP Dispatching and Planning

 

/WATP/DEFAULT

Default message log

Table 3: Logging objects of PROLOGA Add-on

Further information about application logging and auditing can be found here:

SAP ® Applications by PROLOGA 4.8 Operation Guide

4.3.2

System Logging and Tracing

4.3.2.1

Trace Functions

Trace functions allow you to trace the steps of various operations in your SAP ® system. It enables you to monitor the system and to isolate problems that occur.

You can use trace functions to monitor the following operations in your system:

SQL database accessesto monitor the following operations in your system: For more information, refer to the SQL trace

For more information, refer to the SQL trace documentation in the BC - ABAP Workbench: Tools guide.

ABAP programsntent.htm For more information, refer to the ABAP runtime

For more information, refer to the ABAP runtime documentation in the BC - ABAP Workbench:

Tools guide.

Internal operations in the SAP ® system and authorization check ® system and authorization check

Apply transaction ST01 (see also System Trace).

Traces generated by SAP ® processes (developer traces). ® processes (developer traces).

These are the files that are written by the individual SAP ® system processes. The trace files contain detailed technical information to be consulted when problems arise in your system. For more information see also Developer Traces. Use transaction ST11 to display the trace files.

 

4.3.2.2

System Log

You can use the system log to identify and correct errors occurring in your system and its environment. System log can be started with transaction SM21.

Working with the System Log:

Configuring and Running the System Log:

SAP ® Applications by PROLOGA 4.8 Operation Guide

5 Management of SAP ® Applications by PROLOGA 4.8

5.1 Starting and Stopping

There is no need to start or stop the PROLOGA Add-on. After you have installed (as described in SAP ® _Applications_by_PROLOGA_Installation_Guide_4.8.pdf), configurated (as described in the single configuration guides of SAP ® Applications by PROLOGA) and customized (as described in the single customizing guides of SAP ® Applications by PROLOGA) the Add-on, it is ready for usage.

5.2 Backup and Restore

All tables of the PROLOGA Add-on are part of the SAP ® ERP database. There is no additional database schema required. As all programs and transactions are part of the SAP ® ERP system, backup and restore instructions of SAP ® apply.

system, backup and restore instructions of SAP ® apply. For further information go to:

For further information go to:

5.3 System Copy

Since the PROLOGA Add-on is fully integrated in SAP ® system you do not have to perform additional steps for creating a system copy. Follow the instructions of how to create a system copy described in the SAP ® manual.

5.4 Periodic Task

The PROLOGA Add-on does not require any periodic task to run properly. Therefore, you do not have to schedule any jobs or tasks.

5.5 User Management

The PROLOGA Add-on follows the requirements and recommendations of SAP ® for user management, authorization and role concepts. The Add-on itself does not need additional users or user groups. The Add-on contains a pre-defined set of roles for common business scenarios which can easily be adapted to your specific needs.

The SAP ® standard transactions SU01, SU10, PFCG, CUA and SUIM can be used for managing user rights, roles, realization of authentication concept etc.

Below you will find some examples and information about user and role management.

SAP ® Applications by PROLOGA 4.8 Operation Guide

1. Transaction SU01

by PROLOGA 4.8 – Operation Guide 1. Transaction SU01 Figure 18: User management screen (transaction SU01

Figure 18: User management screen (transaction SU01)

SAP ® Applications by PROLOGA 4.8 Operation Guide

2. Creation of initial or new password

Creating initial passwords or changing passwords follows the SAP® standard rules.

or changing passwords follows the SAP® standard rules. Figure 19: User management screen (transaction SU01 )

Figure 19: User management screen (transaction SU01)

3. Role definition

The declaration of roles is recommended as it is described in the SAP ® guidelines. The following illustration displays the definition of different system roles.

displays the definition of different system roles. Figure 20: Role assignment (transaction SU01 ) The roles

Figure 20: Role assignment (transaction SU01)

The roles are defined for different user types (administrator, non-administrative users ->work flow user). By means of the SAP ® standard transactions mentioned above the roles will be defined especially for the business needs of the user. The role ROUTE_PLANNING marked in the illustration above is particularly designed for order management and order dispatching. It contains all user rights necessary to fulfill the requirements of the business process the dispatcher is responsible for.

You will find additional helpful information about user management at the SAP ® help portal.

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 21: Additional information about user management

Figure 21: Additional information about user management in SAP ® help portal

The identity management of the PROLOGA Add-on follows the SAP ® standard rules. The following transactions of the Identity Management of the Application Server ABAP are relevant: SU01, SU10, PFCG, CUA, SUIM.

m

m Figure 22: Additional information about identity management

Figure 22: Additional information about identity management in SAP ® help portal

It is recommended to apply the SAP ® Authorization Concept.

For more information go to:

m

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 23: Additional information about authorization

Figure 23: Additional information about authorization concepts in SAP ® help portal

SAP ® Applications by PROLOGA 4.8 Operation Guide

4. Different role selection

4.8 – Operation Guide 4. Different role selection Figure 24: Different role selection In case of

Figure 24: Different role selection

In case of emergency refer to the SAP ® recommendations for activating an emergency user for the SAP ® Application Server ABAP and the SAP ® troubleshooting guide.

See also SAP ® instructions on how to unlock a user:

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 25: Additional information about locking/unlocking

Figure 25: Additional information about locking/unlocking users

5.5.1 Role Concept

Generally, the commercial clerk role referred to in the following chapters may also be assigned to consultants and developers, in particular for testing of relevant transactions. The designation “commercial clerk” is only to express that the role was predominantly conceived for commercial clerks and therefore - which is essential authorization is not issued for system administration, the ABAP workbench or customizing.

The authorization concept described in the following distinguishes between a „standard“ end user (= commercial clerk) on the one hand and a „system design“ oriented user (consultants, developers or system administrators) on the other hand. The basic idea is that the commercial clerk may not interfere with the basic system configuration of a productive system (including the largest part of the customizing).

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide With the PROLOGA Add-on 4.8, several roles

With the PROLOGA Add-on 4.8, several roles for various areas of the waste & recycling industry are delivered. These roles have names starting with /WATP/. When the PROLOGA Add-on is installed using transaction SAINT, the /WATP/ roles are imported fully correctly only into client 000 but not into the other clients. This is normal system behavior.

We recommend the following course of action for the system administrator in order to make the delivered roles fully usable also in other clients:

1. Go into client 000 and check in the profile generator (transaction PFCG) whether all authorization profiles for the /WATP/ roles are correctly generated. This is usually the case in client 000. (If a profile is for some exceptional reason not generated in client 000, then generate it manually.)

2. Put all /WATP/ roles into a customizing transport request in client 000.

3. Release this transport request in client 000.

4. Import the transport request into the client(s) in which you are really working.

5. Check in the profile generator (transaction PFCG) in your working clients whether all authorization profiles for the /WATP/ roles are correctly generated. This should be the case if the import ran successfully.

6. Assign the relevant /WATP/ roles with the correctly generated authorization profiles to the relevant users.

Then all /WATP/ roles should work correctly as desired in all relevant clients.

5.5.1.1 /WATP/PROLOGA_CUSTOMIZING (for consultants, administrators)

Brief description: allows complete customizing in the /WATP/ namespace

This role provides the authorizations for customizing activities in the relevant PROLOGA configuration transactions in the /WATP/ namespace. Authorizations for SAP ® standard transactions are not provided. This role was mainly designed for consultants and persons being responsible for customizing tasks and can also be assigned to developers, if required. Due to security reasons this role should not be assigned to end-users on the commercial clerk level.

The menu tree of this role is structured as follows:

level. The menu tree of this role is structured as follows: Figure 26: Role /WATP/PROLOGA_CUSTOMIZING ©

Figure 26: Role /WATP/PROLOGA_CUSTOMIZING

SAP ® Applications by PROLOGA 4.8 Operation Guide

5.5.1.2 /WATP/WASTE_LEGAL_REQ_WITH_PRO (for commercial clerks)

Brief description: Legal requirements SAP ® standard and PROLOGA transactions

This role is mainly designed for commercial clerks and provides extensive authorizations for PROLOGA transactions in the component SAP ® Legal Requirements by PROLOGA and also for some SAP ® standard transactions relating to this field. However, rather than being used on its own this role is most useful in combination with other roles (within SAP ® Waste & Recycling), e.g. in combination with the role /WATP/WASTE_MITPROFIL (see below).

The menu of the /WATP/WASTE_LEGAL_REQ_WITH_PRO role is structured as follows:

role is structured as follows: Figure 27: Role /WATP/WASTE_LEGAL_REQ_WITH_PRO The

Figure 27: Role /WATP/WASTE_LEGAL_REQ_WITH_PRO

The possibilities to navigate from directly permitted transactions to other transactions are limited in order to keep authorizations linked to this role concentrated on the waste legislation related field. Example:

Material master data can be displayed but not changed. Additional rights provided by other roles are required in order to manage (including creating and deleting) material data.

As said earlier, this role provides no authorizations regarding system administration or ABAP development. Moreover, an end-user cannot execute any SAP ® software transport functions (such as in SE09, STMS etc.) with this role. Customizing rights are very restricted. The same applies for authorizations in the area of spool request management and background processing. Those rights are restricted in order to prevent authorizations from being unnecessarily assigned several times to the same user. If a user is to be provided with enhanced authorizations in these fields, those rights have to be assigned through other roles.

SAP ® Applications by PROLOGA 4.8 Operation Guide

5.5.1.3 /WATP/WASTE_LEGAL_REQ_NOPROFIL

Brief description: Legal Requirements SAP ® standard and PROLOGA transactions

The menu of this role is identical to the menu of the role /WATP/WASTE_LEGAL_REQ_WITH_PRO described in the previous paragraph. The only distinction is that the role /WATP/WASTE_LEGAL_REQ_WITH_PRO provides the rights required for the transactions listed in the menu (i.e. an authorization profile has been assigned) whereas the role /WATP/WASTE_LEGAL_REQ_NOPROFIL provides neither rights nor an authorization profile. Therefore, this role provides merely a menu tree listing waste legislation related transactions.

In order not to blow up user master data unnecessarily by assigning authorizations twice, the role /WATP/WASTE_LEGAL_REQ_NOPROFIL is particularly suitable for users that have already other roles assigned which provide them with extensive rights. Example: Users with an assigned role that has been derived and only slightly modified from the SAP_ALL profile. In this case, only the menu tree for SAP ® Legal Requirements has to be assigned to the user by means of the role /WATP/WASTE_LEGAL_REQ_NOPROFIL. In this example, the required authorizations are already part of the slightly modified SAP_ALL profile that was granted to the user.

5.5.1.4 /WATP/ONBOARD_COMPUTER (for commercial clerks)

Brief description: Transactions for SAP ® Mobile Order Management

This role provides a menu tree for SAP ® Mobile Order Management by PROLOGA transactions and the respective authorizations. However, this role should only be seen as a supplement to other roles in the process of mobile workforce management, i.e. this role by itself is hardly sufficient for productive work. Rather, it should be combined with suitable other roles such as /WATP/ROUTEPLANNING.

with suitable other roles such as /WATP/ROUTEPLANNING . Figure 28: Role /WATP/ONBOARD_COMPUTER 5.5.1.5

Figure 28: Role /WATP/ONBOARD_COMPUTER

5.5.1.5 /WATP/ROUTEPLANNING (for commercial clerks)

Brief description: Route planning and related management of waste disposal orders

This role was designed for commercial clerks working in the field of route planning. This role enables the user, among other things, to display the road map material in transactions such as /WATP/TP01. Moreover, the user may execute activities associated with the route planning when maintaining waste disposal orders that are assigned to routes and vehicles. Here, the user may view the detailed data of the relevant waste disposal order or assign a waste disposal order to another vehicle.

The menu tree of this relatively "small" role is structured as follows:

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 29: Role /WATP/ROUTEPLANNING 5.5.1.6

Figure 29: Role /WATP/ROUTEPLANNING

5.5.1.6 /WATP/SAMMELROLLE_MITPROFIL (commercial clerk)

Brief description: composite role of several waste & recycling and BC roles

This composite role was designed for commercial clerks who are responsible for various tasks in the field of waste and recycling and who are to be enabled to deal with route planning and mobile order management (BC, on-board computing) as well.

This composite role comprises the following single roles including the respective authorizations (and the associated authorization profiles):

/WATP/WASTE_LEGAL_REQ_WITH_PROauthorizations (and the associated authorization profiles): /WATP/WASTE_FEES_WITH_PROFILE /WATP/MANAGE_CUSTOMERS

/WATP/WASTE_FEES_WITH_PROFILEauthorization profiles): /WATP/WASTE_LEGAL_REQ_WITH_PRO /WATP/MANAGE_CUSTOMERS /WATP/ONBOARD_COMPUTER

/WATP/MANAGE_CUSTOMERS/WATP/WASTE_LEGAL_REQ_WITH_PRO /WATP/WASTE_FEES_WITH_PROFILE /WATP/ONBOARD_COMPUTER /WATP/ROUTEPLANNING The role

/WATP/ONBOARD_COMPUTER/WATP/WASTE_FEES_WITH_PROFILE /WATP/MANAGE_CUSTOMERS /WATP/ROUTEPLANNING The role PROLOGA_SAMMELROLLE_MITPROFIL

/WATP/ROUTEPLANNING/WATP/MANAGE_CUSTOMERS /WATP/ONBOARD_COMPUTER The role PROLOGA_SAMMELROLLE_MITPROFIL provides extensive

The role PROLOGA_SAMMELROLLE_MITPROFIL provides extensive rights in the daily waste and recycling business and allows for necessary activities in adjacent areas such as sales. However, this role does not cover the entire area of waste and recycling but mainly focuses on the PROLOGA transactions and those SAP ® standard transactions which are relatively closely associated with them. This role also provides the required authorizations to work with the SAP ® Dispatching and Planning by PROLOGA application including the road map material.

This role does not provide authorizations to customize essential system settings. As regards system administration, ABAP development or transport management, this role does not provide any rights as it was designed for end-users.

5.5.1.7 /WATP/SAMMELROLLE_OHNEPROFIL (mainly for "powerful" users)

Brief description: composite role of several waste & recycling and BC roles

This composite role includes the following single roles:

/WATP/WASTE_LEGAL_REQ_NOPROFIL (a role without authorization profile) (a role without authorization profile)

/WATP/WASTE_FEES_NOPROFILE (a role without authorization profile) (a role without authorization profile)

/WATP/MANAGE_CUSTOMERS (a role with a "small" authorization profile) (a role with a "small" authorization profile)

/WATP/ONBOARD_COMPUTER (a role with a "small" authorization profile) (a role with a "small" authorization profile)

/WATP/ROUTEPLANNING (a role with a "small" authorization profile) (a role with a "small" authorization profile)

SAP ® Applications by PROLOGA 4.8 Operation Guide

The purpose of this composite role is to provide users who have already been assigned quite extensive rights through other roles with an additional menu tree for several important parts of SAP ® Waste and Recycling. This menu tree focuses on the PROLOGA transactions but also includes several SAP ® standard transactions which are relatively closely related to the PROLOGA transactions.

This composite role mainly provides a menu tree; however, it also contains a few authorizations. In particular, the authorizations required to work with the SAP ® Dispatching and Planning application including the map material are provided by this role. This role is chiefly interesting for developers and consultants who have already been assigned extensive authorizations through, e.g., a slightly reduced SAP_ALL profile and who just need this role to access its menu tree. In this way, the user context is not unnecessarily enlarged with doubly assigned authorizations.

5.5.1.8 /WATP/USERS_OWN_DATA (commercial clerk)

Brief description: user data: address, spool jobs, jobs

This very "small" role enables the user to:

display and change own address data and default values in transaction SU3 SU3

manage own spool and print jobs in transaction SP02 SP02

manage own background processing in transaction SM37 SM37

display own authorizations with transaction SU56 and define missing authorizations with transaction SU53 ; the transactions SU53 and SU56 were SU56 and define missing authorizations with transaction SU53; the transactions SU53 and SU56 were not included in the menu on purpose in order not to call the user‟s attention to it. However, these transactions might be very helpful when analyzing authorization problems.

Neither spool jobs nor background processing jobs of other users can be managed with this role.

5.5.2 Authorization Objects

Authorization objects enable you to define complex authorizations by grouping up to 10 authorization fields in an AND relationship to check whether a user is allowed to perform a certain action. To pass an authorization test for an object, the user must satisfy the authorization check for each field in the object. Therefore, it is essential to provide users and user groups with correct user rights.

The development follows the SAP ® guidelines for creating authorization objects. The classes and objects of the PROLOGA Add-on 4.8 were evaluated considering whether the existence of an authorization is mandatory from a process perspective.

Having determined the objects a user is requiring rights for, those rights can be allocated.

SAP ® Applications by PROLOGA 4.8 Operation Guide

5.5.2.1 Example: Waste Approval Management

Technical name for SAP Legal Requirements
Technical
name
for
SAP
Legal
Requirements

Figure 30: Select authorization object

Legal Requirements Figure 30: Select authorization object Figure 31: Display authorization objects © PROLOGA GmbH SAP

Figure 31: Display authorization objects

SAP ® Applications by PROLOGA 4.8 Operation Guide

The data element of the field ISU_ACTIVT is E_MODE. The picture below illustrates the elementary type

of E_ACTIVITY. The authorization rights displayed under the Value Range tab can be allocated.

displayed under the Value Range tab can be allocated. Figure 32: Change authorization objects A complete

Figure 32: Change authorization objects

A complete list of all authorization objects delivered with the PROLOGA Add-on is attached as appendix

7.2 - Authorization Objects delivered with the Add-on.

User rights supported by the PROLOGA Add-on are similar to the authorization field ISU_ACTIVT: display (value 1), change (value 2), create (value 3), delete (value 4), check (value 7) and execute (value 8). The following values are not supported: empty (no processing), 5 (change history) and 9 (display in list).

5.5.3 Archiving

Objective of any archiving integration is the reduction of the data volume on a database in order to improve efficiency of the database. PROLOGA follows the SAP ® recommendations to export the data in files. An import of data is not supported in general. In case that an import of data is required, contact SAP ® or your implementation partner directly.

PROLOGA has a predefined archiving frame. This object is a container consisting of one more archiving steps to complete a whole archiving process. The process runs in a defined order and is defined for a client of an SAP ® system (see next chapter).

5.5.3.1 Principles of PROLOGA’s Archiving

Archiving provided by PROLOGA follows a hierarchical strategy. You can archive an object only if the superior object of the SAP ® standard has been archived before.

SAP ® Applications by PROLOGA 4.8 Operation Guide

class Data Model

material

«column»

*PK

MANDT: MANDT(3)

*PK

MATNR: CHAR(18)

MTART: CHAR(4)

MATKL: CHAR(9)

«PK»

+

PK_Material(MANDT, CHAR)

Waste material
Waste
material

0

 

material

description

 

«column»

*PK

MANDT: MANDT(3)

*pfK

MATNR: CHAR(18)

*

*PK

SPRAS: LANG(1)

 

MAKTX: CHAR(40)

MAKTG: CHAR(40)

 

«FK»

+

FK_MATNR(CHAR)

«PK»

+

PK_Materialtexte(MANDT, CHAR, LA

  «FK» + FK_MATNR(CHAR) «PK» + PK_Materialtexte(MANDT, CHAR, LA 1 Container type NG)

1

Container type
Container type

NG)

Figure 33: Overview PROLOGA Archiving

The superior object of the waste material is the SAP ® standard object material. PROLOGA provides a business object for this SAP ® standard object which includes a functionality to check in the background if related objects exist. In this case an error message is created and archiving is not executed.

It depends on the customizing which objects relations have to be checked.

Definition of selection. Flag - check whether this object is still in use. Archiving frame
Definition
of
selection.
Flag
- check
whether this
object is still
in use.
Archiving
frame
is
defined
for

Figure 34: Example of archiving frame

SAP ® Applications by PROLOGA 4.8 Operation Guide

In the example above the material can be deleted when the flag (Field: LOEVM) for deletion is set. The material will not be deleted if it has already been used in an invoice.

5.5.3.2 Principles of PROLOGA’s Deletion Process

The same method that is used to archiving data is applied for deleting data (if this functionality is enabled).

The following picture illustrates the hierarchy of existing objects in PROLOGA‟s transaction

task

/WATP/BASE_ADMIN.

The

archiving

frame

EX_CUST_FRAME

(grey

box)

references

the

EX_CUST_FRAME (white box).

The task is referenced by the archiving frame as shown below. Frame, that has to
The
task
is
referenced
by
the
archiving
frame
as
shown below.
Frame, that has to
be deleted. The
frame references the
taks
EX_CUST_FRAME.

Figure 35: Object hierarchy of /watp/base_admin

If anyone tries to delete task EX_CUST_FRAME (white box) the following error message appears and the program prevents archiving or deleting of the object.

the program prevents archiving or deleting of the object. Figure 36: Display log © PROLOGA GmbH

Figure 36: Display log

SAP ® Applications by PROLOGA 4.8 Operation Guide

5.6 Logging of Security Relevant Events

– Operation Guide 5.6 Logging of Security Relevant Events It is recommended to use the transaction

It is recommended to use the transaction RZ20 of SAP ® ECC 6.0 to monitor security relevant alerts.

of SAP ® ECC 6.0 to monitor security relevant alerts. Figure 37: Logging of security relevant

Figure 37: Logging of security relevant objects

See also chapter Fehler! Verweisquelle konnte nicht gefunden werden

The PROLOGA Add-on does not provide a security configuration. There is no security concept required in addition to the SAP ® standard concept.

You will find additional information on the SAP ® Security concept at:

5.7 Communication Channels and Communication Security

The PROLOGA Add-on applies the SAP ® interface (IF_GIS_VIEW) in order to retrieve map data from the MapServer (for instance map&guide by PTV AG). The interface is provided by SAP ® and is implemented class CL_GIS_VIEW_IGS.

There is no additional encryption method required as all servers are connected to the local network.

5.8 Security Statements/Guidelines for Included 3rd Party Applications

There are no 3 rd party applications included in the product.

SAP ® Applications by PROLOGA 4.8 Operation Guide

5.9 Security Statements/Guidelines

The add-on provides the capability to administrate and adapt the functionality. The relevant transactions are /WATP/BASE_OBJCONFIG, /WATP/ARB_CONFIG and /WATP/MAP_CONFIG. Take care that users have no rights on this transactions in a productive environment as you would administrate functions as SE16 and SE80.

You can use these transactions in the development systems for adapting functions. The changes will be transferred to Q and P system by using SAP transport.

Example:

After calling transaction /WATP/BASE_OBJCONFIG you can navigate by double.klick on a methode name to the code editor.

Double- klick
Double-
klick

Figure 38: Security statements 1

Navigation to transaction SE80.

38: Security statements 1 Navigation to transaction SE80 . Figure 39: Transaction SE80 I © PROLOGA

Figure 39: Transaction SE80 I

SAP ® Applications by PROLOGA 4.8 Operation Guide

At changing into edit mode a developer key is requested by SAP.

changing into edit mode a developer key is requested by SAP. Figure 40: Transaction SE80 II

Figure 40: Transaction SE80 II

SAP ® Applications by PROLOGA 4.8 Operation Guide

6 High Availability

The PROLOGA Add-on is is fully integrated in the SAP ® system landscape.

Availability of the PROLOGA Add-on component SAP ® Legal Requirements by PROLOGA directly linked to the availability of the SAP ® Waste and Recycling solution. Therefore both solutions have to be considered if a higher solution availability is required.

For further information about availability considerations go to:

m

m Figure 41: Source SAP ® Library; TOM Netweaver Note the

Figure 41: Source SAP ® Library; TOM Netweaver

m Figure 41: Source SAP ® Library; TOM Netweaver Note the general checklist of SAP ®

Note the general checklist of SAP ® .

SAP ® Applications by PROLOGA 4.8 Operation Guide

SAP ® Applications by PROLOGA 4.8 – Operation Guide Figure 42: Source SAP ® Library; TOM

Figure 42: Source SAP ® Library; TOM NW; SAP Notes

SAP ® Applications by PROLOGA 4.8 Operation Guide

7 Appendix

7.1 Customizing Tables

Below is a list of all tables containing customization and configuration data of the PROLOGA Add-on.

Tablename Description zusätzliche Daten zum Signal Aktivität /WATP/TTBCACTVTY futher data for signal activity
Tablename
Description
zusätzliche Daten zum Signal Aktivität
/WATP/TTBCACTVTY
futher data for signal activity
zusätzliche Daten zum Signal Bemerkungen
/WATP/TTBCCMMNT
futher data for signal remarks
allgemeine BC-Konfiguration
/WATP/TTBCCONFIG
Configuration for BC Suite
zusätzliche Daten zum Signal Ausnahmen
/WATP/TTBCEXCEPT
futher data for signal exceptions
zusätzliche Daten zum Signal für Füllstandswerte
/WATP/TTBCFILLLV
futher data for signal fuel values
Tablekey-Provider
/WATP/TTBCKEYPRO
Tablekey-Provider
Texttabelle zu Tablekey-Provider
/WATP/TTBCKEYPRT
Tablekey-Provider text
Konfiguration der Stammdatengenerierung
/WATP/TTBCMDGEN
Configuration master data generation
Zuordnung der Objektyp-Tablekey-Provider
/WATP/TTBCOBJTKP
Tablekey-Provider assigning object type
zusätzliche Konfigurationsdaten zum Objekttyp
/WATP/TTBCOBJTYP
futher data for object type
Texttabelle für Erweiterung der Objekttypen
/WATP/TTBCOBJTYT
futher data for object type text
Rückmeldetypen
/WATP/TTBCRES
Result types
Rückmeldetypzuordnung
/WATP/TTBCRESA
Result types assignings
Rückmeldefelder
/WATP/TTBCRESF
Result fields
Rückmeldefeldertexte
/WATP/TTBCRESFT
Result fields text
Rückmeldetypentexte
/WATP/TTBCREST
Result types text
Transferparameter
/WATP/TTEXPPARM
Transfer parameter
Texttabelle zu Transferparametern
/WATP/TTEXPPARMT
Transfer parameter text
zusätzliche Eigenschaften an einer Transfertypklasse
/WATP/TTEXPPROPS
futher data for transfer type class
/WATP/TTEXPTSSIG
Transfer types assigning transfer state and signa Transfertyp Transferstatus-Signal-Zuordnung
Transfertypen
/WATP/TTEXPTYPE
Transfer types
Texttabelle zu Transfertypen
/WATP/TTEXPTYPET
Transfer types text
XSLT-Programme für Transfertypen
/WATP/TTEXPXML
XSLT programs
Signaltypgruppen
/WATP/TTSIGTYPGR
Signal type group
Texttabelle zu Signaltypgruppen
/WATP/TTSIGTYPGT
Signal type group text
Texttabelle zur Kapazitätsart
/WATP/TCAPAKINDT
Capacity kind text
FOP for Application (Text)
/WATP/TTFOP4APPL
Front Office Process for application text
FOP for Application
/WATP/TTFOP4APPT
Front Office Process for application
benötigte Stops zwischen 2 Routenpunkten
/WATP/TTPST4RPS
needed stops between route points
Einstellungen der KapaPlanung
/WATP/TTTPCPCNFG
Capacity planning properties
HR Infotypes read in OPTP
/WATP/TTTPHRINFO
HR Infotypes read in OPTP
Einstellungen der Op. TP
/WATP/TTTPOPCNFG
Operational route planning properties
Einstellungen der Revierplanung
/WATP/TTTPRPCNFG
route district planning properties
Druckeinstellungen des Nutzers
/WATP/TPRTUSER
Print options per user
Optionen f. nutzerspezifische Druckformulareinstellungen
/WATP/TPRTUSERO
Print options per user
Druckformular
/WATP/TTPRTFRM
Print form
Druckformularoptionen
/WATP/TTPRTFRMO
Print
form options
Druckformularparameter
/WATP/TTPRTFRMP
Print
form parameters
Druckformular Zuordnung SubFormulare
/WATP/TTPRTFRMS
Print form assigning sub print forms
Druckformulargruppe
/WATP/TTPRTGRP
Print
form group
weitere Customizing Einstellungen zur Fahrzeugart
/WATP/TTFLEETCAT
Fleet cat further properties
Abgrenzungen gespeichert
/WATP/TRANGE
Selection
Abgrenzung Texte
/WATP/TRANGET
Selection text
Abgrenzungswerte
/WATP/TRANGEV
Selection values
Anwendungen
/WATP/TTAPPL
Application
Anwendungsgruppe
/WATP/TTAPPLGRP
Application group
Anwendungsbereich
/WATP/TTAPPLSCR
Application screen
Texte zur Tabelle der Anwendungen
/WATP/TTAPPLT
Application text
Implementierung/Ausprägung APPL
/WATP/TTIMPL
Implementation
Implementation BO Feld Modifikation
/WATP/TTIMPLBFM
Implementation field modifications
Implementation BO Erweiterung
/WATP/TTIMPLBOA
Implementation business object extensions
Implementation Buchungen
/WATP/TTIMPLBOK
Implementation functions
Implementation Datenberechtigung
/WATP/TTIMPLDTA
Implementation data authority
Implementationsfelder
/WATP/TTIMPLFLD
Implementation fields
Implementationsgruppe
/WATP/TTIMPLGRP
Implementation group
Implementation aktiv in Mandant
/WATP/TTIMPLMAN
Implementation client
Implementation Nummernkreisinterval
/WATP/TTIMPLNR
Implementation number range
Implementation Vorgangsberechtigung
/WATP/TTIMPLPRA
Implementation process authority
Implementation Druckformulare
/WATP/TTIMPLPRT
Implementation print forms
Implementation Abgrenzungsdefinitionszuordnung zu Anwendung
/WATP/TTIMPLRNG
Implementation selections
Implementation Reportmapping
/WATP/TTIMPLRPT
Implementation report mapping
Implementation Subscreen
/WATP/TTIMPLSCR
Implementation screens
Implementation Subscreen Texte
/WATP/TTIMPLSCRT
Implementation screen texts
Planner HTML - Charttypen
/WATP/TTPLANHTMC
HTML planner chart types
Konfiguration für PLANNER_HTML
/WATP/TTPLANHTML
HTML planner configuration

Figure 43: Customizing and configuration data I

SAP ® Applications by PROLOGA 4.8 Operation Guide

Tablename Description Mandanten Tabelle /WATP/TADMARFRM Archiving frame client Customizingeinstellungen für den
Tablename
Description
Mandanten Tabelle
/WATP/TADMARFRM
Archiving frame client
Customizingeinstellungen für den Admin
/WATP/TADMCSTM
Administration properties
MesspunktSammlung
/WATP/TADMMEASA
Measurement collection
MesspunktSammlung
/WATP/TADMMEASC
Measurement collection
Kumulierte Messwerte
/WATP/TADMMEASK
Measurement cumulated values
Mandantenabhängige Einstellung für Messungen
/WATP/TADMMEASM
Measurement client
letzte Laufende Nummer zu jeder Messung
/WATP/TADMMEASN
Measurement numbering
konkrete Messung mit Werten
/WATP/TADMMEASP
Measurement values
Admin Task
/WATP/TADMTSK
Task
"Nicht"-Transportrelation für Aufgaben (/WATP/TADMTSK)
/WATP/TADMTSKO
Task
Admin Task Parameter
/WATP/TADMTSKP
Task parameters
Teilaufgaben
/WATP/TADMTSKS
Task partials
Admin Task Text
/WATP/TADMTSKT
Task text
Archivierungsrahmen
/WATP/TTADMARFR
Archiving frame
Archivierungsrahmen Objekttypen
/WATP/TTADMARFRO
Archiving frame object types
Archivierungsrahmen Abgrenzungen
/WATP/TTADMARFRR
Archiving frame selection
Archivierungsrahmen Texte
/WATP/TTADMARFRT
Archiving frame text
Messpunkt
/WATP/TTADMMEAS
Measurement
Messpunkt Texte
/WATP/TTADMMEAST
Measurement text
Texttabelle für /WATP/TTADMTSKTP
/WATP/TTADMTKTPT
Task template text
Admin Taskkind
/WATP/TTADMTSKK
Task kind
Admin Taskkind Text
/WATP/TTADMTSKKT
Task kind text
Admin Task Template
/WATP/TTADMTSKT
Task template
Administration Task Template Parameter
/WATP/TTADMTSKTP
Task template parameters
Admin Task Template Text
/WATP/TTADMTSKTT
Task template text
Upgrade Adjustment
/WATP/TTADMUADJ
Upgrade Adjustment
Upgrade Adjustment Property
/WATP/TTADMUADJP
Upgrade Adjustment Property
AbgrenzungsDefinition
/WATP/TTRANGEDF
Definition of selection
AbgrenzungsDefinition Schlüssel
/WATP/TTRANGEDFK
Definition of selection keys
AbgrenzungsDefinition Struktur
/WATP/TTRANGEDFS
Definition of selection structures
AbgrenzungsDefinition Text
/WATP/TTRANGEDFT
Definition of selection text
AbgrenzungsDefinition Struktur Text
/WATP/TTRANGEDFX
Definition of selection structure text
Abgrenzungsdefinitionsgruppe
/WATP/TTRANGEDG
Group of definition of selection
AbgrenzungsdefinitionsgruppeTexte
/WATP/TTRANGEDGT
Group of definition of selection text
ADR Vorschriften
/WATP/TTADRRLE
ADR regulation
ADR Vorschriften / Detail
/WATP/TTADRRLED
ADR regulation detail
Texttabelle zur Tabelle /WATP/TTADRRLED
/WATP/TTADRRLEDT
ADR regulation detail text
Texttabelle zur Tabelle /WATP/TTADRRLE
/WATP/TTADRRLET
ADR regulation text
Verpackungsarten
/WATP/TTARB_PAT
Packaging type
Physikalische Eigenschaften
/WATP/TTARB_PHP
Physical properties
Behandlungsverfahren
/WATP/TTARB_TMM
Treatment procedures
Transportweg
/WATP/TTARB_WOT
Type of transport
Konfigurationstabelle für ARB
/WATP/TTARBCNFG
ARB configuration
Zusätze zur politischen Region
/WATP/TTARBPOLRG
Additional information on political region
Service types for automatic document post. from Servicetypen für automat. Scheinverbuchung aus Rückmeldung
/WATP/TTARBSFAB
ZEDAL Konfiguration
/WATP/TTARBZDLCF
ZEDAL configuration
Scheinarten
/WATP/TTCERTTYP
Disposal Document Types
Texttabelle zur Tabelle /WATP/TTCERTTYP
/WATP/TTCERTTYPT
Disposal
Document Types text
AVV Sammelkategorien
/WATP/TTCOLLCAT
EWC collective categories
Texttabelle zur Tabelle /WATP/TTCOLLCAT
/WATP/TTCOLLCATT
EWC collective categories text
Überwachungslevel
/WATP/TTCTRLLVL
Monitoring level
Texttabelle zur Tabelle /WATP/TTCTRLLVL
/WATP/TTCTRLLVLT
Monitoring level text
Wertevorrat für Deklarationsanalyse
/WATP/TTDECLV
Declaration analysis parameter
Texttabelle zur Tabelle /WATP/TTDECLV
/WATP/TTDECLVT
Declaration analysis parameter text
Nachweisarten
/WATP/TTPRFTYP
Waste approval
types
Texttabelle zur Tabelle /WATP/TTPRFTYP
/WATP/TTPRFTYPT
Waste approval
types text
verwendbare Scheinarten für Nachweisart
/WATP/TTPRTCERT
Disposal Document Types for

Figure 44: Customizing and configuration data II

SAP ® Applications by PROLOGA 4.8 Operation Guide

Tablename Description verwendbare Nachweisart für Überwachungslevel /WATP/TTPRTCTRL Disposal Document Types for
Tablename
Description
verwendbare Nachweisart für Überwachungslevel
/WATP/TTPRTCTRL
Disposal Document Types for monitoring level
Partnerarten
/WATP/TTPTNRTYP
Partner types
Texttabelle zur Tabelle /WATP/TTPTNRTYP
/WATP/TTPTNRTYPT
Partner types text
Entsorgungsverfahren
/WATP/TTWSTMODE
Waste disposal procedure
Texttabelle zur Tabelle /WATP/TTWSTMODE
/WATP/TTWSTMODET
Waste disposal procedure text
Texte sprachabhängig ohne Mandant
/WATP/TTSPRATXTG
Client independent text
Profiles for PROLOGA business partner compon Profil für die PROLOGA Geschäftspartnerkomponente des CIC
/WATP/TTCICBPSD
/WATP/TTCSCABADR
PROLOGA characteristic for addresses, customi Customizing für Adressmerkmal
PROLOGA cic clusterbuilder, configuration node CIC Cluster Builder: Konfiguration der einzelnen Knotentypen
/WATP/TTCSCICL
/WATP/TTCSCICLGO
Profiles for PROLOGA logo component of cic, cu Profi für PROLOGA Logokomponente für Slot 2
/WATP/TTCSRELCON
Container types for during day process, customiz Relevante für UB
/WATP/TTVBAPEWAO
Field assign for service object from contract and Zuordnung Kontrakt <-> Servicerhythmus
Konfiguration Auftragserzeugung
/WATP/TTORDALLCO
Configuration order creation
Split-Kriterien für Auftragserzeugung
/WATP/TTORDALLSP
Split criterias for order creation
Aufgabenzuordnung zu einer IMP/EXP-Config
/WATP/TIECONFTSK
Import export configuration assigning task
Import Export Konfiguration
/WATP/TTIECONF
Import export configuration
Import Export Konfiguration Datenanbieter Parameter
/WATP/TTIECONFD
Import export configuration parameter
Import Export Transformer
/WATP/TTIECONFTF
Import export transformer
Import Export Transformer Parameter
/WATP/TTIECONFTP
Import export transformer parameter
Einstellungen für Kartenfunktionen
/WATP/TTMAPCNFG
Map configuration
Kartenkonfigurationen
/WATP/TTMAPCNFGS
Map configuration
Account Limit
/WATP/TTACCLMT
Account limit
Account Limit Current
/WATP/TTACCLMTC
Account limit current
Account Limit Keys
/WATP/TTACCLMTK
Account limit keys
Account Limit Texttabelle
/WATP/TTACCLMTT
Account limit text
Objekttypgruppen
/WATP/TTOBJGRP
Object type group
Modul (Klammer für OBJGRP, IMPLGRP, APPLGRP, PRTGRP, usw.)
/WATP/TTOBJMOD
Module
Objektmodul Paket Zuordnung
/WATP/TTOBJMODP
Module packages
Modulversionen
/WATP/TTOBJMODV
Module versions
Nummernkreiseinstellungen
/WATP/TTOBJNRNG
Number key properties
Nummernkreiseinstellungen
/WATP/TTOBJNRNGM
Number key properties client
Objekttypvorgangsposition
/WATP/TTOBJPRCP
Object type process position
Objekttypvorgänge
/WATP/TTOBJPROC
Object type process
Texte zu Objekttypvorgängen
/WATP/TTOBJPROCT
Object type process text
Objektstatus
/WATP/TTOBJSTAT
Object status
Objektstatus Mandantenabhängige Feldmodifikationen
/WATP/TTOBJSTATF
Object status field modifications
Objektstatus Mandantspezifisch
/WATP/TTOBJSTATM
Object status client
Texte zu Objekttypstatus
/WATP/TTOBJSTATT
Object status text
Transaktion Konfiguration für /WATP/CL_TRANSACTION
/WATP/TTOBJTRA
Transaction configuration
Transaktion Konfiguration für /WATP/CL_TRANSACTION
/WATP/TTOBJTRAM
Transaction configuration client
Transaktionskonfigurationsparameter
/WATP/TTOBJTRAMP
Transaction configuration parameter client
Transaktionskonfigurationsparameter
/WATP/TTOBJTRAP
Transaction configuration parameter
Transaktion Texte
/WATP/TTOBJTRAT
Transaction configuration text
Objekttypen
/WATP/TTOBJTYPE
Object type
Archivierungsobjekte als Detail eines Objtypes
/WATP/TTOBJTYPEA
Object type archiving
Objekttypezusätze
/WATP/TTOBJTYPED
Object type extensions
Objekttypen
/WATP/TTOBJTYPEM
Object type client
Texte zu Objekttypen
/WATP/TTOBJTYPET
Object type text
OBU Profile
/WATP/TBCOBUPRF
OBU Profile
OBU Profile Blob
/WATP/TBCOBUPRFB
OBU Profile data
OBU Profile Konfiguartion
/WATP/TBCOBUPRFC
OBU Profile configuration
OBU Profile Datei
/WATP/TBCOBUPRFF
OBU Profile file
OBU Profile Softwareupdate
/WATP/TBCOBUPRFS
OBU Profile software update
OBU Profile Text
/WATP/TBCOBUPRFT
OBU Profile text
OBU Profile Fahrzeuge
/WATP/TBCOBUPRFV
OBU Profile vehicle
OBU Software
/WATP/TBCOBUSW
OBU Software
OBU Software Daten
/WATP/TBCOBUSWD
OBU Software data
Signaltypen
/WATP/TT001
Types of signal
Texttabelle zu Signaltypen
/WATP/TT001T
Types of signal text
Signale
/WATP/TT002
Signal
Texttabelle zu Signalen
/WATP/TT002T
Signal text
Übertragungsstatus
/WATP/TT003
Transferstate
Texttabelle zu Übertragungsstatus
/WATP/TT003T
Transferstate text
zusätzliche Daten zu den Leistungsarten
/WATP/TT005
futher data for service type
Dokumentenkategorien
/WATP/TT007
Document categories
Texttabelle für Dokumentenkategorien
/WATP/TT007T
Document categories text
Dokumentdefinitionen
/WATP/TT008
Document definition
Texttabelle für Dokumente
/WATP/TT008T
Document text
Imp/Exp-Prozessoren
/WATP/TTBC_IEPRO
Import Export processors

Figure 45: Customizing and configuration data III

SAP ® Applications by PROLOGA 4.8 Operation Guide

7.2 Authorization Objects delivered with the Add-on

package

PROLOGA class of business object

short descritption of business object

technical name

localization

/WATP/ARB

/WATP/CL_BO_ARBNW

waste approval

/WATP/ARNW

 

/WATP/ARB

/WATP/CL_BO_DECLANLS

declaration analysis

/WATP/ARDL

 

/WATP/ARB

/WATP/CL_BO_NGSAS

NGS modul - German legislation

/WATP/ARNG

German

/WATP/BC_EEWA

/WATP/CL_BO_CONTHSTRY

BC/EEWA container movements

/WATP/BCNM

 

/WATP/MAP

/WATP/CL_BO_GEOMOBJ

geocoding

/WATP/GIS

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCACTIVITYHSTRY

BC-Suite event history

/WATP/BCAH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCCOMMENTHSTRY

BC-Suite history of remarks

/WATP/BCCH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCCSTORDRESULT

BC-Suite additional confirmation information by orderer

/WATP/BCCR

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCEVACUATION

BC-Suite emptying

/WATP/BCEA

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCEXCEPTIONHSTRY

BC-Suite history of exeption messages

/WATP/BCEH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCMSGTMPL

BC-Suite message profiles

/WATP/BCMT

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCOBUPROFILE

BC-Suite technical OBU profile

/WATP/BCOR

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCOBUSOFTWARE

BC-Suite OBU Software for data processing

/WATP/BCSW

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCOPHSTRY

BC-Suite employment history

/WATP/BCOH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCSERSTATEHSTRY

BC-Suite history of service status

/WATP/BCSH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCSERVICERESULT

BC-Suite confirmation data made by orderer

/WATP/BCSR

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCSTAFFTIMERECORD

BC-Suite time registration by vehicle crew

/WATP/BCST

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCSWUORDER

BC-Suite update order of softwarerelease on OBU

/WATP/BCSO

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCSWUORDPOS

BC-Suite items for update order of softwarerelease on OBU

/WATP/BCSP

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCSYSREQRESULT

BC-Suite result on request for system data

/WATP/BCSQ

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCTOURRESULT

BC-Suite confirmation data of route

/WATP/BCTR

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_BCWEIGHBILL

BC-Suite weighing note

/WATP/BCWB

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_CYCLTMPL

BC-Suite pattern to send position data from vehicle to office

/WATP/BCCT

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_DOCHSTRY

BC-Suite history of documents

/WATP/BCDH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_MSGHSTRY

BC-Suite history of messages

/WATP/BCMH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_ORDRHSTRY

BC-Suite order history

/WATP/BCTH

 

/WATP/ON-BOARD-COMPUTER

/WATP/CL_BO_ORPSHSTRY

BC-Suite history of orders

/WATP/BCCI

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_PLANAREA

planning area

/WATP/TPPA

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_PLANPROFILE

planning profile

/WATP/TPPF

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_PLANSET

planning scenario

/WATP/TPPS

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_PLNGRP

planner group

/WATP/TPPG

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_PLNGRPEAP

order items of a planner group

/WATP/TPPG

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_PLNGRPEAR

orders of a planner group

/WATP/TPPG

 
   

configuration shortterm planning time line, size of row at

   

/WATP/ORDER_PROCESSING

/WATP/CL_BO_TPCPCNFG

displaying

/WATP/TPCC

/WATP/ORDER_PROCESSING

/WATP/CL_BO_TPOPCNFG

configuration shortterm planning planning tree

/WATP/TPCO

 

/WATP/ORDER_PROCESSING

/WATP/CL_BO_TPRPCNFG

configuration of user-tailored planning area

/WATP/TPCR

 

Figure 46: Authorization Objects delivered with the Add-on