SAP® Applications by PROLOGA 4.

8 – Operation Guide

SAP® Applications by PROLOGA 4.8 Operation Guide

© PROLOGA GmbH SAP® Applications by PROLOGA 4.8

Operation Guide

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.

© PROLOGA GmbH SAP® Applications by PROLOGA 4.8

Operation Guide

SAP® Applications by PROLOGA 4.8 – Operation Guide

Table of Contents
1 1.1 1.2 1.3 1.4 1.5 2 2.1 2.2 2.3 2.4 2.5 3 4 4.1 4.2 4.2.1 4.2.2 4.3 4.3.1 4.3.2 4.3.2.1 4.3.2.2 5 5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.1.1 5.5.1.2 5.5.1.3 5.5.1.4 5.5.1.5 5.5.1.6 5.5.1.7 5.5.1.8 5.5.2 5.5.2.1 5.5.3 5.5.3.1 5.5.3.2 5.6 5.7 5.8 5.9 6 7 7.1 7.2 Getting Started ............................................................................................................... 6 About this Guide ................................................................................................................ 6 Global Definitions .............................................................................................................. 6 Important SAP Notes ......................................................................................................... 7 History of Changes ............................................................................................................ 7 Support Packages .............................................................................................................. 8 Configuration and Customization .................................................................................... 9 SAP® SAP® SAP® SAP® SAP® Legal Requirements by PROLOGA ................................................................................ 9 Dispatching and Planning – Longterm Planning by PROLOGA .......................................... 9 Dispatching and Planning – Operational Planning by PROLOGA ........................................ 9 Mobile Order Management by PROLOGA ....................................................................... 9 Smart Meter Rollout for Utilities by PROLOGA ............................................................. 10

Technical System Landscape – High Level Overview .................................................... 11 Monitoring .................................................................................................................... 13 Alert Monitoring Concept .................................................................................................. 13 Performance Analysis ....................................................................................................... 15 Starting SQL trace analysis ............................................................................................... 16 Example: How to analyze Operational Planning ................................................................... 16 Logging and Tracing Concept ............................................................................................ 20 Application Logging .......................................................................................................... 20 System Logging and Tracing ............................................................................................. 21 Trace Functions ............................................................................................................... 21 System Log..................................................................................................................... 21 Management of SAP® Applications by PROLOGA 4.8 ..................................................... 23 Starting and Stopping ...................................................................................................... 23 Backup and Restore ......................................................................................................... 23 System Copy .................................................................................................................. 23 Periodic Task................................................................................................................... 23 User Management............................................................................................................ 23 Role Concept................................................................................................................... 29 /WATP/PROLOGA_CUSTOMIZING (for consultants, administrators) ........................................ 30 /WATP/WASTE_LEGAL_REQ_WITH_PRO (for commercial clerks) ........................................... 31 /WATP/WASTE_LEGAL_REQ_NOPROFIL .............................................................................. 32 /WATP/ONBOARD_COMPUTER (for commercial clerks) ......................................................... 32 /WATP/ROUTEPLANNING (for commercial clerks) ................................................................. 32 /WATP/SAMMELROLLE_MITPROFIL (commercial clerk) ......................................................... 33 /WATP/SAMMELROLLE_OHNEPROFIL (mainly for "powerful" users) ........................................ 33 /WATP/USERS_OWN_DATA (commercial clerk) ................................................................... 34 Authorization Objects ....................................................................................................... 34 Example: Waste Approval Management .............................................................................. 35 Archiving ........................................................................................................................ 36 Principles of PROLOGA‟s Archiving ..................................................................................... 36 Principles of PROLOGA‟s Deletion Process ........................................................................... 38 Logging of Security Relevant Events .................................................................................. 39 Communication Channels and Communication Security ........................................................ 39 Security Statements/Guidelines for Included 3rd Party Applications ....................................... 39 Security Statements/Guidelines ......................................................................................... 40 High Availability ........................................................................................................... 42 Appendix ...................................................................................................................... 44 Customizing Tables .......................................................................................................... 44 Authorization Objects delivered with the Add-on .................................................................. 47

© PROLOGA GmbH SAP® Applications by PROLOGA 4.8

Page 3 of 47 Operation Guide

SAP® Applications by PROLOGA 4.8 – Operation Guide

Table of Figures
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1: High level overview – waste and recycling industry ........................................................... 11 2: High level scenario with other SAP® standard modules ...................................................... 11 3: feasible solution of a system landscape for the PROLOGA Add-on........................................ 12 4: feasible solution of a system landscape for the PROLOGA Add-on by using Google Maps ........ 12 5: Applying the SAP® monitor template for the operating system ............................................ 13 6: CPU monitoring ............................................................................................................ 14 7: CPU analysis of a typical test system of PCSS ................................................................... 14 8: Fundamentals of ABAP® monitoring................................................................................. 15 9: Activate system trace .................................................................................................... 16 10: Date and planner group selection dialog......................................................................... 16 11: Main screen of operational planning ............................................................................... 16 12: Tree with expanded nodes............................................................................................ 17 13: Deactivating SQL trace ................................................................................................ 17 14: Display trace .............................................................................................................. 18 15: Assigning filter for displaying trace ................................................................................ 18 16: Example of a trace ...................................................................................................... 19 17: Detailed execution plan ................................................................................................ 19 18: User management screen (transaction SU01) ................................................................. 24 19: User management screen (transaction SU01) ................................................................. 25 20: Role assignment (transaction SU01) .............................................................................. 25 21: Additional information about user management in SAP® help portal .................................. 26 22: Additional information about identity management in SAP® help portal .............................. 26 23: Additional information about authorization concepts in SAP® help portal ............................ 27 24: Different role selection ................................................................................................. 28 25: Additional information about locking/unlocking users ....................................................... 29 26: Role /WATP/PROLOGA_CUSTOMIZING ........................................................................... 30 27: Role /WATP/WASTE_LEGAL_REQ_WITH_PRO ................................................................. 31 28: Role /WATP/ONBOARD_COMPUTER ............................................................................... 32 29: Role /WATP/ROUTEPLANNING....................................................................................... 33 30: Select authorization object ........................................................................................... 35 31: Display authorization objects ........................................................................................ 35 32: Change authorization objects........................................................................................ 36 33: Overview PROLOGA Archiving ....................................................................................... 37 34: Example of archiving frame .......................................................................................... 37 35: Object hierarchy of /watp/base_admin .......................................................................... 38 36: Display log ................................................................................................................. 38 37: Logging of security relevant objects .............................................................................. 39 38: Security statements 1 .................................................................................................. 40 39: Transaction SE80 I ...................................................................................................... 40 40: Transaction SE80 II ..................................................................................................... 41 41: Source SAP® Library; TOM Netweaver ........................................................................... 42 42: Source SAP® Library; TOM NW; SAP Notes ..................................................................... 43 43: Customizing and configuration data I ............................................................................. 44 44: Customizing and configuration data II ........................................................................... 45 45: Customizing and configuration data III .......................................................................... 46 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

© PROLOGA GmbH SAP® Applications by PROLOGA 4.8

Page 4 of 47 Operation Guide

8 – Operation Guide Glossary Attention Note © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 Page 5 of 47 Operation Guide .SAP® Applications by PROLOGA 4.

g. © PROLOGA GmbH SAP® Applications by PROLOGA 4. SAP® Smart Meter Rollout for Utilities by PROLOGA.1 About this Guide Designing. This guide also provides references to the documentation required for these tasks.SAP® Applications by PROLOGA 4. SAP® Dispatching & Planning . SAP® Dispatching & Planning . 1.2 Global Definitions It„s recommended to read: Terms_and_Definitions_of_SAP_Applications_by_PROLOGA_4. This guide provides a starting point for managing your mySAP solutions and maintaining and running them optimally.Longterm Planning by PROLOGA.Operational Planning by PROLOGA and SAP® Mobile Order Management by PROLOGA and Implementation of SAP® Applications by PROLOGA (PCSS). in the server profiles or on database level) 1. This document gives an overview of all important terms and definitions of the Add-on.8.8 – Operation Guide 1 Getting Started This guide does not replace the daily operations hand book that we recommend customers create for their specific production operations. Target Groups: Technical Consultants System Administrators Solution Consultants Business Process Owners Support Specialists The PROLOGA Add-on is technically fully integrated into the SAP® ERP system and does not require any special technical configuration (e.8 Page 6 of 47 Operation Guide . 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. waste and recycling industry) and maintenance of SAP® solutions is required.g. the Customizing and Configuration Documentation of: SAP® Legal Requirements by PROLOGA.pdf. implementing. It contains specific information on various tasks and lists the tools that you can use to implement them. Knowledge of business processes (e. so you will sometimes also need to consult other guides such as the Master Guide.

Instead to create a note template the customer can enter the approval number.sap. The functionality for archiving of waste notes is prepared. Planned resources are checked against availability (SAP-HR and SAP-PM integration). SAP® Route and District Management for Waste and Recycling by PROLOGA The new release provides new functionalities for dispatching different types of orders. The direct usage of approval in service frequency is a simplification in the service frequency maintenance process.8 – Operation Guide 1. Third party products.8 Table 1: Important SAP Notes 1.3 Important SAP Notes Check regularly which SAP® Notes are available for the Solution Operation Guide.0 functional changes of SAP® Waste and Recycling delivered in SAP® EhP2 are fully supported.8 . such as map material by PTV or a Geographical Information System may be integrated to the software through interfaces. The short term planning provides an overview about a planning time line.0 Important Changes First version of the SAP® Applications by PROLOGA Solution Operation Guide SAP® Legal Requirements by PROLOGA Catalogue exchange provides an interface to exchange local and customer-made waste (material) catalogues.0 The Add-on contains specific waste and recycling functions even generic functions for operational Page 7 of 47 Operation Guide © PROLOGA GmbH SAP® Applications by PROLOGA 4. 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. Managing different order types (waste disposal orders. deliveries and customer service orders) under the same planning interface is enabled. 3. the service location of the orders and details regarding single orders. This capability supports the customer in implementing processes for a variety of different business scenarios. 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. It provides new features for system administrators to install a new release or to roll-out the software for a business unit.8 How to get a licence key for PROLOGA add on Prerequisites for installing AddOn V4.4 History of Changes Make sure you use the current version of the Solution Operation Guide. SAP Note Number 1375005 1375003 1375009 Title Composite note SAP® Applications by PROLOGA 4. like remote software updates and maintenance of releases. Support for SAP® EhP2 With release 2. The following table provides an overview of the most important changes in prior versions. Version 1.SAP® Applications by PROLOGA 4. The current version of the Solution Operation Guide can be found on the SAP Service Marketplace at http://service.0 2.com.

com PROLOGA administration for available versions at: © PROLOGA GmbH SAP® Applications by PROLOGA 4. SAP® Dispatching & Planning . Please contact the info@prologa. 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. The PROLOGA Add-on follows the SAP® strategy regarding support packages.SAP® Applications by PROLOGA 4. The component SAP® Route and District Management for Waste and Recycling by PROLOGA This component was splitted in Release 4. SAP® Dispatching & Planning .Operational Planning by PROLOGA contains generic functions even special functions for the waste and recycling market. Table 2: Most important changes in prior PROLOGA Add-ons 1.8 – Operation Guide planning and mobile order management.8 Page 8 of 47 Operation Guide .Longterm Planning by PROLOGA contains the longterm planning especially for the waste and recycling industry 2.5 Support Packages Make sure that you only use official releases of the PROLOGA Add-on. Therefore the Add-on was renamed to SAP® Applications by PROLOGA. 3.8 in three separate components: 1.

Operational Planning by PROLOGA application. See also document SAP_MapConfig_by_PROLOGA_Configuration_Guide_4.pdf. An SAP® certified digital map solution is available from PTV AG.8 Page 9 of 47 Operation Guide . The customizing of the module is to be implemented with the transaction /WATP/BC_CONFIG.SAP® Applications by PROLOGA 4. We recommend using a digital map component to tap the full potential of this component and maximize efficiency.1 SAP® Legal Requirements by PROLOGA The customization/configuration of this component is described in: SAP_Legal_Requirements_by_PROLOGA_Configuration_Guide_4.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. There exist the additional opportunity to link to other maps like GIS systems via WMS and WFS.8. The customizing is splitted in several parts and includes basic customizing of SAP ® standard objects (like technical object types) and component specific customizing. Google Maps and bing. 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.8.pdf.pdf. 2. 2.8. An SAP® certified digital map solution is available from PTV AG.pdf.8. After finishing the customizing you can start using the component by managing your waste manifests as described in the user manual.pdf.8 – Operation Guide 2 Configuration and Customization Before you can use SAP® Applications by PROLOGA you have to customize and configure the acquired components.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. 2.pdf. We recommend using a digital map component to tap the full potential of this component and maximize efficiency. Google Maps and bing. See also document SAP_MapConfig_by_PROLOGA_Configuration_Guide_4.8. Prerequisite for applying the SAP® Mobile Order Management by PROLOGA application is the implementation of the SAP® Dispatching and Planning .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. © PROLOGA GmbH SAP® Applications by PROLOGA 4. The PROLOGA Add-on includes enhancements of the existing SAP® industry solution SAP® Waste and Recycling. There exist the additional opportunity to link to other maps like GIS systems via WMS and WFS.

SAP® Applications by PROLOGA 4.8.8 – Operation Guide 2.pdf.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. © PROLOGA GmbH SAP® Applications by PROLOGA 4.pdf. The user manual of the component can be found in document: SAP_Smart_Meter_Rollout_for_Utilities_by_PROLOGA_User_Manual_4.8.8 Page 10 of 47 Operation Guide . See also document SAP_MapConfig_by_PROLOGA_Configuration_Guide_4.8. Google Maps and bing. An SAP® certified digital map solution is available from PTV AG. We recommend using a digital map component to tap the full potential of this component and maximize efficiency. There exist the additional opportunity to link to other maps like GIS systems via WMS and WFS.pdf.

The modules are connected to the BADI‟s published by SAP®.04 ABAP SAP Applications by PROLOGA SAP Mobile Order Management application SAP Dispatching & Planning operational planning SAP Dispatching & Planning Longterm Planning SAP Legal Requirements application Order Management Order Management Treatment and disposal Dispatching and route planning Facility management/ 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. SAP ECC 6.8 – Operation Guide 3 Technical System Landscape – High Level Overview As mentioned above the PROLOGA Add-on is fully integrated in the SAP® system.04 ABAP SAP Applications by PROLOGA SAP Mobile Order Management application SAP Dispatching & Planning operational planning SAP Smart Meter Rollout for Utilities Sales and Order Management distribution Plant maintenance Material Management ISU SAP standard modules Figure 2: High level scenario with other SAP® standard modules © PROLOGA GmbH SAP® Applications by PROLOGA 4.SAP® Applications by PROLOGA 4.8 Page 11 of 47 Operation Guide . The picture below provides an overview about the high level scenario combined with the other modules for the process. The following picture is a high level overview dedicated to the waste and recycling industry: SAP ECC 6.

Figure 3: feasible solution of a system landscape for the PROLOGA Add-on SAP ERP 6.0 with EhP4 Road map server computer with Windows Server2003 UNIX or Linux cannot be used for this purpose SAP Kernel 7.0 with EhP4 Map Web Service provided by Google or Microsoft SAP Kernel 7.8 Page 12 of 47 Operation Guide .01 patchlevel 110 SAP_BASIS 7. Another option is the use of a GIS (as ESRI or openGIS) system which provides maps and functions as WMS or WFS.04 SP 7 SPAM/SAINT 7.04 SP 7 SPAM/SAINT 7. plan.UT 6. Legal requirements RFC link to SAP gateway Mobile order management SAP database 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.SAP® Applications by PROLOGA 4. SAP ERP 6. and geocoding and routing can be performed based on the PTV map data Instead of PTV eServers the .01 patchlevel 110 SAP_BASIS 7.01 SP 40 Optimized route and dist.8 – Operation Guide The following picture illustrates the system landscape as it is described in the technical product fact sheets of PCSS. . plan.01 SP 7 SAP_APPL 6. Legal requirements RFC link to SAP gateway SAP IGS ( Internet Graphics Server ) Mobile order management PTV ( xMap Server ) PTV ( xLocate Server ) PTV ( xRoute Server ) SAP database PTV ( Roadmap material ) The IGS communicates via RFC with the gateway of the ERP 6.04 SP 7 IS.04 SP 7 IS. The road map data can then be displayed in the ERP system .UT 6. 0 system. © PROLOGA GmbH SAP® Applications by PROLOGA 4.01 SP 40 Optimized route and dist. newer PTV xServers can be used at least in the near ( future). The picture is an example for the use of PTV.01 SP 7 SAP_APPL 6. In this case the external SAP Netweaver is needless.

Instead the already existing standard CCMS monitoring tools can be used. As the PROLOGA Add-on is technically fully integrated in the SAP® ERP system. Therefore.8 Page 13 of 47 Operation Guide . © PROLOGA GmbH SAP® Applications by PROLOGA 4. there are no additional resources such as memory caches.8 – Operation Guide 4 Monitoring 4. queues etc. deployed.1 Alert Monitoring Concept The CCMS is fully integrated in the SAP® solution. the PROLOGA Add-on does not require any special CCMS monitoring.SAP® Applications by PROLOGA 4. Figure 5: Applying the SAP® monitor template for the operating system You can execute the different methods as described in the SAP® standard dialog. Administrators and developers can monitor the complete solution within the SAP® Alert Monitor (transaction RZ20). You can monitor the system by using the SAP® standard templates for system monitoring.

For further information on alert monitoring go to: http://help.htm © PROLOGA GmbH SAP® Applications by PROLOGA 4.com/saphelp_nw2004s/helpdata/en/8d/a20e4249fc5433e10000 000a155106/frameset.8 – Operation Guide Figure 6: CPU monitoring The following screenshot illustrates the result of the CPU analysis as described above.SAP® Applications by PROLOGA 4.8 Page 14 of 47 Operation Guide .sap. Figure 7: CPU analysis of a typical test system of PCSS In addition to the available SAP® monitoring templates administrators may build their individual monitor templates.

Please use the standard SAP® SQL trace functionality for analyzing the SQL statements which are used in a PROLOGA transaction. © PROLOGA GmbH SAP® Applications by PROLOGA 4.SAP® Applications by PROLOGA 4.8 Page 15 of 47 Operation Guide .8 – Operation Guide Figure 8: Fundamentals of ABAP® monitoring 4. 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. you can use the transactions provided by SAP® for performance analysis.2 Performance Analysis As the PROLOGA Add-on was developed with SAP® development tools and in compliance with the SAP® development standards.

1 Starting SQL trace analysis Start transaction ST05 and set marker in SQL trace check box. you can execute the transaction you want to investigate in a second session.8 Page 16 of 47 Operation Guide . Figure 10: Date and planner group selection dialog 2. 4.2. Figure 9: Activate system trace After the SQL trace is switched on (Activate Trace). Click on the green check mark. Figure 11: Main screen of operational planning © PROLOGA GmbH SAP® Applications by PROLOGA 4. Start the transaction /WATP/TP01 in a second session (select transaction from tree or enter /N/WATP/TP01).SAP® Applications by PROLOGA 4.8 – Operation Guide 4.2 Example: How to analyze Operational Planning 1.2.

Expand a node in the tree on the left. Switch back to your first session and deactivate the SQL trace. Figure 12: Tree with expanded nodes 4. Figure 13: Deactivating SQL trace © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 – Operation Guide 3.8 Page 17 of 47 Operation Guide .SAP® Applications by PROLOGA 4.

8 Page 18 of 47 Operation Guide . Figure 14: Display trace Figure 15: Assigning filter for displaying trace © PROLOGA GmbH SAP® Applications by PROLOGA 4.SAP® Applications by PROLOGA 4. Click on Display Trace to show the SQL trace.8 – Operation Guide 5.

Click on the green check mark. Figure 16: Example of a trace 7.8 – Operation Guide 6.SAP® Applications by PROLOGA 4. For further investigations and detailed analysis you can call the Execution Plan for an SQL statement. Figure 17: Detailed execution plan © PROLOGA GmbH SAP® Applications by PROLOGA 4. showing how SAP® standard tables and PROLOGAs /WATP/ tables are accessed by SQL statements. The usual SQL trace display appears.8 Page 19 of 47 Operation Guide .

and auditing purposes.3.com/erp2005_ehp_03/helpdata/EN/c7/69bcc9f36611d3a6510000e835363f/frameset. The application log is a table structure consisting of several tables. etc). While the system log records system events (information about program and transaction terminations. The following logging objects are included in the PROLOGA Add-on. Application related entries are written to these tables using SAP® function modules. With the transaction SLG1 to you can display and analyze the application log. 4. Object /WATP/DEFAULT /WATP/DEFAULT /WATP/ADMTASK /WATP/ARCHIVE /WATP/UPGRADEADJUST /WATP/ARB /WATP/DEFAULT /WATP/BC /WATP/DEFAULT /WATP/ADMIN /WATP/ARCHIVE /WATP/CONFIRM /WATP/IMPEXP /WATP/CS_CIC /WATP/CS_CIC /WATP/TP /WATP/DEFAULT Subobject Description General logging object for the whole Add-on Default message log Administration Archiving Upgrade processes Logging object for SAP® Legal Requirements by PROLOGA Default message log Logging object for SAP® Mobile Order Management by PROLOGA Default message log Administration Archiving Confirmation Im-/Export Logging object for Cluster Builder CIC processes Logging object for SAP Dispatching and Planning Default message log Table 3: Logging objects of PROLOGA Add-on Further information about application logging and auditing can be found here: http://help.htm © PROLOGA GmbH SAP® Applications by PROLOGA 4. 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. The where-used list provides information on who accessed the function modules (call report RSFKT100.3 Logging and Tracing Concept SAP® systems keep a variety of logs for system administration. Audits and logs are important for monitoring the security of your system and to track events in case of problems. you can use the application log to record application specific event and problem messages relating to objects.SAP® Applications by PROLOGA 4. database errors.8 – Operation Guide 4. Use the transaction SLG0 to configure the application log.sap. problem solving.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.8 Page 20 of 47 Operation Guide . function group: SLG0). monitoring.

sap.SAP® Applications by PROLOGA 4.com/erp2005_ehp_03/helpdata/EN/1f/8311ac4bc511d189750000e8322d00/con tent.sap. You can use trace functions to monitor the following operations in your system: SQL database accesses For more information.com/erp2005_ehp_03/helpdata/EN/1f/8311b94bc511d189750000e8322d00/con tent.htm Internal operations in the SAP® system and authorization check Apply transaction ST01 (see also System Trace).8 Page 21 of 47 Operation Guide . Use transaction ST11 to display the trace files. refer to the ABAP runtime documentation in the BC .2 System Log You can use the system log to identify and correct errors occurring in your system and its environment.3. http://help.2.sap.2. refer to the SQL trace documentation in the BC .sap.com/erp2005_ehp_03/helpdata/EN/1f/8311664bc511d189750000e8322d00/con tent. It enables you to monitor the system and to isolate problems that occur. For more information see also Developer Traces.3.ABAP Workbench: Tools guide.htm Configuring and Running the System Log: Specifying Log File Path Names http://help.htm Expert Mode http://help.com/erp2005_ehp_03/helpdata/EN/1f/83114c4bc511d189750000e8322d00/con tent. The trace files contain detailed technical information to be consulted when problems arise in your system.3. System log can be started with transaction SM21.ABAP Workbench: Tools guide.htm ABAP programs For more information.com/erp2005_ehp_03/helpdata/EN/d1/801847454211d189710000e8322d00/co ntent. http://help.sap. http://help.htm Reading a Log Report http://help.htm Traces generated by SAP® processes (developer traces).htm © PROLOGA GmbH SAP® Applications by PROLOGA 4. These are the files that are written by the individual SAP® system processes. Working with the System Log: Displaying a Log http://help.sap.com/erp2005_ehp_03/helpdata/EN/1f/83119f4bc511d189750000e8322d00/con tent.1 Trace Functions Trace functions allow you to trace the steps of various operations in your SAP ® system.sap.2 System Logging and Tracing 4.com/erp2005_ehp_03/helpdata/EN/d1/801847454211d189710000e8322d00/co ntent.com/erp2005_ehp_03/helpdata/EN/1f/8311924bc511d189750000e8322d00/con tent.8 – Operation Guide 4.htm 4.sap. http://help.

htm Starting the System Log Processes http://help.htm Debugging Central Log Processes http://help.sap.htm Terminating Processes http://help.com/erp2005_ehp_03/helpdata/EN/1f/8311d34bc511d189750000e8322d00/con tent.com/erp2005_ehp_03/helpdata/EN/1f/8311ed4bc511d189750000e8322d00/con tent.htm © PROLOGA GmbH SAP® Applications by PROLOGA 4.htm Troubleshooting Central Logging http://help.com/erp2005_ehp_03/helpdata/EN/1f/8311e04bc511d189750000e8322d00/con tent.com/erp2005_ehp_03/helpdata/EN/1f/8311c64bc511d189750000e8322d00/con tent.8 Page 22 of 47 Operation Guide .8 – Operation Guide Understanding Central Logging Concepts http://help.com/erp2005_ehp_03/helpdata/EN/1f/8312074bc511d189750000e8322d00/con tent.htm Setting Central Logging Parameters http://help.com/erp2005_ehp_03/helpdata/EN/1f/8312144bc511d189750000e8322d00/con tent.sap.sap.sap.sap.sap.com/erp2005_ehp_03/helpdata/EN/1f/8311fa4bc511d189750000e8322d00/con tent.sap.htm Controlling Log Switching http://help.SAP® Applications by PROLOGA 4.

SAP® Applications by PROLOGA 4. it is ready for usage.5 User Management The PROLOGA Add-on follows the requirements and recommendations of SAP® for user management. Below you will find some examples and information about user and role management. For further information go to: http://help.pdf). CUA and SUIM can be used for managing user rights. roles. 5. 5.4 Periodic Task The PROLOGA Add-on does not require any periodic task to run properly.8. realization of authentication concept etc. you do not have to schedule any jobs or tasks.sap. 5. © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 Page 23 of 47 Operation Guide . The Add-on itself does not need additional users or user groups. backup and restore instructions of SAP® apply.com/saphelp_nw2004s/helpdata/en/01/2bd13ffc9a4a21e100000 00a1550b0/frameset. As all programs and transactions are part of the SAP ® ERP system.1 Starting and Stopping There is no need to start or stop the PROLOGA Add-on.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. SU10.8 5. The Add-on contains a pre-defined set of roles for common business scenarios which can easily be adapted to your specific needs. PFCG. After you have installed (as described in SAP®_Applications_by_PROLOGA_Installation_Guide_4. Follow the instructions of how to create a system copy described in the SAP® manual. 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.2 Backup and Restore All tables of the PROLOGA Add-on are part of the SAP® ERP database.8 – Operation Guide 5 Management of SAP® Applications by PROLOGA 4. Therefore. authorization and role concepts.htm 5. The SAP® standard transactions SU01. There is no additional database schema required.

8 – Operation Guide 1. Transaction SU01 Figure 18: User management screen (transaction SU01) © PROLOGA GmbH SAP® Applications by PROLOGA 4.SAP® Applications by PROLOGA 4.8 Page 24 of 47 Operation Guide .

Figure 19: User management screen (transaction SU01) 3. Figure 20: Role assignment (transaction SU01) The roles are defined for different user types (administrator.8 Page 25 of 47 Operation Guide . http://help.SAP® Applications by PROLOGA 4.com/saphelp_nw2004s/helpdata/en/da/16115e9d70e64eaa3f9e199c3ffb80/frameset. The role ROUTE_PLANNING marked in the illustration above is particularly designed for order management and order dispatching.htm © PROLOGA GmbH SAP® Applications by PROLOGA 4.sap. non-administrative users ->work flow user). Role definition The declaration of roles is recommended as it is described in the SAP® guidelines. 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. By means of the SAP® standard transactions mentioned above the roles will be defined especially for the business needs of the user.8 – Operation Guide 2. Creation of initial or new password Creating initial passwords or changing passwords follows the SAP® standard rules. The following illustration displays the definition of different system roles.

The following transactions of the Identity Management of the Application Server ABAP are relevant: SU01. http://help. For more information go to: http://help.com/saphelp_nw2004s/helpdata/en/81/0e0f61b566dc44bbb4055b3ccd25be/frameset.sap. CUA.com/saphelp_nw2004s/helpdata/en/81/0e0f61b566dc44bbb4055b3ccd25be/frameset.ht m Figure 22: Additional information about identity management in SAP® help portal It is recommended to apply the SAP® Authorization Concept.sap.SAP® Applications by PROLOGA 4. PFCG.8 – Operation Guide Figure 21: Additional information about user management in SAP® help portal The identity management of the PROLOGA Add-on follows the SAP® standard rules.8 Page 26 of 47 Operation Guide .ht m © PROLOGA GmbH SAP® Applications by PROLOGA 4. SUIM. SU10.

8 – Operation Guide Figure 23: Additional information about authorization concepts in SAP® help portal © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 Page 27 of 47 Operation Guide .SAP® Applications by PROLOGA 4.

8 Page 28 of 47 Operation Guide .com/saphelp_nw70/helpdata/en/ee/10df3d0eb8af5ee10000000a114084/frameset.htm © PROLOGA GmbH SAP® Applications by PROLOGA 4.SAP® Applications by PROLOGA 4.sap. See also SAP® instructions on how to unlock a user: http://help. Different role selection 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.8 – Operation Guide 4.

the commercial clerk role referred to in the following chapters may also be assigned to consultants and developers.8 – Operation Guide Figure 25: Additional information about locking/unlocking users 5. in particular for testing of relevant transactions. 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). 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.5.8 Page 29 of 47 Operation Guide . © PROLOGA GmbH SAP® Applications by PROLOGA 4. developers or system administrators) on the other hand.1 Role Concept Generally.SAP® Applications by PROLOGA 4. 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.

4. Then all /WATP/ roles should work correctly as desired in all relevant clients. This should be the case if the import ran successfully. This is usually the case in client 000. if required. 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. 3.5. 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. Check in the profile generator (transaction PFCG) in your working clients whether all authorization profiles for the /WATP/ roles are correctly generated.) 2.8. then generate it manually.1. Import the transport request into the client(s) in which you are really working.8 Page 30 of 47 Operation Guide . Put all /WATP/ roles into a customizing transport request in client 000. 5. Release this transport request in client 000.8 – Operation Guide With the PROLOGA Add-on 4.SAP® Applications by PROLOGA 4. This role was mainly designed for consultants and persons being responsible for customizing tasks and can also be assigned to developers. These roles have names starting with /WATP/. The menu tree of this role is structured as follows: Figure 26: Role /WATP/PROLOGA_CUSTOMIZING © PROLOGA GmbH SAP® Applications by PROLOGA 4.1 /WATP/PROLOGA_CUSTOMIZING (for consultants. (If a profile is for some exceptional reason not generated in client 000. several roles for various areas of the waste & recycling industry are delivered. Due to security reasons this role should not be assigned to end-users on the commercial clerk level. This is normal system behavior. When the PROLOGA Add-on is installed using transaction SAINT. 5. Assign the relevant /WATP/ roles with the correctly generated authorization profiles to the relevant users. Authorizations for SAP® standard transactions are not provided. Go into client 000 and check in the profile generator (transaction PFCG) whether all authorization profiles for the /WATP/ roles are correctly generated. 6. the /WATP/ roles are imported fully correctly only into client 000 but not into the other clients.

8 – Operation Guide 5. © PROLOGA GmbH SAP® Applications by PROLOGA 4.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. Example: Material master data can be displayed but not changed. this role provides no authorizations regarding system administration or ABAP development. an end-user cannot execute any SAP® software transport functions (such as in SE09.g. those rights have to be assigned through other roles. e. Additional rights provided by other roles are required in order to manage (including creating and deleting) material data. rather than being used on its own this role is most useful in combination with other roles (within SAP® Waste & Recycling).) with this role. Those rights are restricted in order to prevent authorizations from being unnecessarily assigned several times to the same user. Moreover.1. The menu of the /WATP/WASTE_LEGAL_REQ_WITH_PRO role is structured as follows: 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.8 Page 31 of 47 Operation Guide . However. The same applies for authorizations in the area of spool request management and background processing. As said earlier. in combination with the role /WATP/WASTE_MITPROFIL (see below). STMS etc. If a user is to be provided with enhanced authorizations in these fields.SAP® Applications by PROLOGA 4. Customizing rights are very restricted.5.

1. among other things. Therefore. i.5. the required authorizations are already part of the slightly modified SAP_ALL profile that was granted to the user. Example: Users with an assigned role that has been derived and only slightly modified from the SAP_ALL profile.SAP® Applications by PROLOGA 4. In order not to blow up user master data unnecessarily by assigning authorizations twice.8 Page 32 of 47 Operation Guide . the user may view the detailed data of the relevant waste disposal order or assign a waste disposal order to another vehicle. this role provides merely a menu tree listing waste legislation related transactions. In this case. Rather. The menu tree of this relatively "small" role is structured as follows: © PROLOGA GmbH SAP® Applications by PROLOGA 4.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.5. it should be combined with suitable other roles such as /WATP/ROUTEPLANNING.8 – Operation Guide 5.1. to display the road map material in transactions such as /WATP/TP01. the user may execute activities associated with the route planning when maintaining waste disposal orders that are assigned to routes and vehicles.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. However.1. 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. 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.e. an authorization profile has been assigned) whereas the role /WATP/WASTE_LEGAL_REQ_NOPROFIL provides neither rights nor an authorization profile. this role should only be seen as a supplement to other roles in the process of mobile workforce management. This role enables the user. the role /WATP/WASTE_LEGAL_REQ_NOPROFIL is particularly suitable for users that have already other roles assigned which provide them with extensive rights. Moreover. In this example.e.5. Figure 28: Role /WATP/ONBOARD_COMPUTER 5. Here. 5.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. this role by itself is hardly sufficient for productive work.

1. on-board computing) as well.5. As regards system administration. 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 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 does not provide any rights as it was designed for end-users.5.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) /WATP/WASTE_FEES_NOPROFILE (a role without authorization profile) /WATP/MANAGE_CUSTOMERS (a role with a "small" authorization profile) /WATP/ONBOARD_COMPUTER (a role with a "small" authorization profile) /WATP/ROUTEPLANNING (a role with a "small" authorization profile) © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 Page 33 of 47 Operation Guide . However. This composite role comprises the following single roles including the respective authorizations (and the associated authorization profiles): /WATP/WASTE_LEGAL_REQ_WITH_PRO /WATP/WASTE_FEES_WITH_PROFILE /WATP/MANAGE_CUSTOMERS /WATP/ONBOARD_COMPUTER /WATP/ROUTEPLANNING 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.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.SAP® Applications by PROLOGA 4. 5.1. This role does not provide authorizations to customize essential system settings.8 – Operation Guide Figure 29: Role /WATP/ROUTEPLANNING 5. ABAP development or transport management.

spool jobs.SAP® Applications by PROLOGA 4.1. it is essential to provide users and user groups with correct user rights. e. the user must satisfy the authorization check for each field in the object. a slightly reduced SAP_ALL profile and who just need this role to access its menu tree. it also contains a few authorizations.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. 5.5. This menu tree focuses on the PROLOGA transactions but also includes several SAP ® standard transactions which are relatively closely related to the PROLOGA transactions. The development follows the SAP® guidelines for creating authorization objects. these transactions might be very helpful when analyzing authorization problems.. In this way.8 /WATP/USERS_OWN_DATA (commercial clerk) Brief description: user data: address. Neither spool jobs nor background processing jobs of other users can be managed with this role. Therefore. In particular. This composite role mainly provides a menu tree. To pass an authorization test for an object. 5.g.8 Page 34 of 47 Operation Guide .8 were evaluated considering whether the existence of an authorization is mandatory from a process perspective. However. those rights can be allocated. the user context is not unnecessarily enlarged with doubly assigned authorizations. the authorizations required to work with the SAP® Dispatching and Planning application including the map material are provided by this role. jobs This very "small" role enables the user to: display and change own address data and default values in transaction SU3 manage own spool and print jobs in transaction SP02 manage own background processing in transaction SM37 display own authorizations with transaction SU56 and define missing authorizations with transaction SU53.5. however. Having determined the objects a user is requiring rights for.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. the transactions SU53 and SU56 were not included in the menu on purpose in order not to call the user‟s attention to it. © PROLOGA GmbH SAP® Applications by PROLOGA 4. The classes and objects of the PROLOGA Add-on 4. This role is chiefly interesting for developers and consultants who have already been assigned extensive authorizations through.

8 – Operation Guide 5.8 Page 35 of 47 Operation Guide .2.1 Example: Waste Approval Management Technical name Requirements for SAP Legal Figure 30: Select authorization object Figure 31: Display authorization objects © PROLOGA GmbH SAP® Applications by PROLOGA 4.SAP® Applications by PROLOGA 4.5.

5. check (value 7) and execute (value 8).3. PROLOGA has a predefined archiving frame. PROLOGA follows the SAP® recommendations to export the data in files.5.1 Principles of PROLOGA’s Archiving Archiving provided by PROLOGA follows a hierarchical strategy. change (value 2).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 GmbH SAP® Applications by PROLOGA 4. The following values are not supported: empty (no processing).8 Page 36 of 47 Operation Guide . In case that an import of data is required. The authorization rights displayed under the Value Range tab can be allocated. contact SAP® or your implementation partner directly. 5 (change history) and 9 (display in list).Authorization Objects delivered with the Add-on. An import of data is not supported in general. delete (value 4). This object is a container consisting of one more archiving steps to complete a whole archiving process. User rights supported by the PROLOGA Add-on are similar to the authorization field ISU_ACTIVT: display (value 1).SAP® Applications by PROLOGA 4. 5.2 . Figure 32: Change authorization objects A complete list of all authorization objects delivered with the PROLOGA Add-on is attached as appendix 7. The process runs in a defined order and is defined for a client of an SAP® system (see next chapter). The picture below illustrates the elementary type of E_ACTIVITY.5. You can archive an object only if the superior object of the SAP® standard has been archived before.8 – Operation Guide The data element of the field ISU_ACTIVT is E_MODE. create (value 3).

of Flag . LANG) Waste material Container type Figure 33: Overview PROLOGA Archiving The superior object of the waste material is the SAP ® standard object material. Archiving frame is defined for SAP client Figure 34: Example of archiving frame © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 Page 37 of 47 Operation Guide . PROLOGA provides a business object for this SAP® standard object which includes a functionality to check in the background if related objects exist. Definition selection. In this case an error message is created and archiving is not executed.. CHAR) 1 «FK» + FK_MATNR(CHAR) «PK» + PK_Materialtexte(MANDT. CHAR.* *PK SPRAS: MAKTX: MAKTG: MANDT(3) CHAR(18) LANG(1) CHAR(40) CHAR(40) material «column» *PK MANDT: MANDT(3) *PK MATNR: CHAR(18) MTART: CHAR(4) MATKL: CHAR(9) «PK» + PK_Material(MANDT. It depends on the customizing which objects relations have to be checked.check whether this object is still in use.8 – Operation Guide class Data Model material description «column» *PK MANDT: *pfK MATNR: 0.SAP® Applications by PROLOGA 4.

Frame.5. The task is referenced by the archiving frame as shown below.8 Page 38 of 47 Operation Guide .8 – Operation Guide In the example above the material can be deleted when the flag (Field: LOEVM) for deletion is set.3. The following picture illustrates the hierarchy of existing objects in PROLOGA‟s transaction /WATP/BASE_ADMIN. The material will not be deleted if it has already been used in an invoice.SAP® Applications by PROLOGA 4. 5. 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 archiving frame EX_CUST_FRAME (grey box) references the task EX_CUST_FRAME (white box).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). Figure 36: Display log © PROLOGA GmbH SAP® Applications by PROLOGA 4. that has to be deleted.

5.8 Security Statements/Guidelines for Included 3rd Party Applications There are no 3rd party applications included in the product. The interface is provided by SAP ® and is implemented class CL_GIS_VIEW_IGS. The PROLOGA Add-on does not provide a security configuration.0 to monitor security relevant alerts.sap. © PROLOGA GmbH SAP® Applications by PROLOGA 4..6 Logging of Security Relevant Events It is recommended to use the transaction RZ20 of SAP® ECC 6.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).htm 5. There is no additional encryption method required as all servers are connected to the local network.com/saphelp_nw2004s/helpdata/en/da/16115e9d70e64eaa3f9e199c3ffb80/frameset. You will find additional information on the SAP® Security concept at: http://help. Figure 37: Logging of security relevant objects See also chapter Fehler! Verweisquelle konnte nicht gefunden werden.8 Page 39 of 47 Operation Guide .8 – Operation Guide 5.SAP® Applications by PROLOGA 4. There is no security concept required in addition to the SAP® standard concept.

8 Page 40 of 47 Operation Guide .SAP® Applications by PROLOGA 4. Figure 39: Transaction SE80 I © PROLOGA GmbH SAP® Applications by PROLOGA 4. 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. Doubleklick Figure 38: Security statements 1 Navigation to transaction SE80.9 Security Statements/Guidelines The add-on provides the capability to administrate and adapt the functionality. The changes will be transferred to Q and P system by using SAP transport. The relevant transactions are /WATP/BASE_OBJCONFIG. Example: After calling transaction /WATP/BASE_OBJCONFIG you can navigate by double. /WATP/ARB_CONFIG and /WATP/MAP_CONFIG.klick on a methode name to the code editor.8 – Operation Guide 5.

SAP® Applications by PROLOGA 4.8 – Operation Guide At changing into edit mode a developer key is requested by SAP. Figure 40: Transaction SE80 II © PROLOGA GmbH SAP® Applications by PROLOGA 4.8 Page 41 of 47 Operation Guide .

ht m Figure 41: Source SAP® Library.SAP® Applications by PROLOGA 4.com/saphelp_nw2004s/helpdata/en/08/57456b4ae611d1894f0000e829fbbd/frameset. © PROLOGA GmbH SAP® Applications by PROLOGA 4. TOM Netweaver Note the general checklist of SAP®. For further information about availability considerations go to: http://help.8 – Operation Guide 6 High Availability The PROLOGA Add-on is is fully integrated in the SAP® system landscape.8 Page 42 of 47 Operation Guide . Therefore both solutions have to be considered if a higher solution availability is required. Availability of the PROLOGA Add-on component SAP® Legal Requirements by PROLOGA directly linked to the availability of the SAP® Waste and Recycling solution.sap.

SAP® Applications by PROLOGA 4. TOM NW.8 – Operation Guide Figure 42: Source SAP® Library.8 Page 43 of 47 Operation Guide . SAP Notes © PROLOGA GmbH SAP® Applications by PROLOGA 4.

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

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

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

German legislation BC/EEWA container movements geocoding BC-Suite event history BC-Suite history of remarks BC-Suite additional confirmation information by orderer BC-Suite emptying BC-Suite history of exeption messages BC-Suite message profiles BC-Suite technical OBU profile BC-Suite OBU Software for data processing BC-Suite employment history BC-Suite history of service status BC-Suite confirmation data made by orderer BC-Suite time registration by vehicle crew BC-Suite update order of softwarerelease on OBU BC-Suite items for update order of softwarerelease on OBU BC-Suite result on request for system data BC-Suite confirmation data of route BC-Suite weighing note BC-Suite pattern to send position data from vehicle to office BC-Suite history of documents BC-Suite history of messages BC-Suite order history BC-Suite history of orders planning area planning profile planning scenario planner group order items of a planner group orders of a planner group configuration shortterm planning time line.SAP® Applications by PROLOGA 4.8 Page 47 of 47 Operation Guide .8 – Operation Guide 7.2 Authorization Objects delivered with the Add-on PROLOGA class of business object /WATP/CL_BO_ARBNW /WATP/CL_BO_DECLANLS /WATP/CL_BO_NGSAS /WATP/CL_BO_CONTHSTRY /WATP/CL_BO_GEOMOBJ /WATP/CL_BO_BCACTIVITYHSTRY /WATP/CL_BO_BCCOMMENTHSTRY /WATP/CL_BO_BCCSTORDRESULT /WATP/CL_BO_BCEVACUATION /WATP/CL_BO_BCEXCEPTIONHSTRY /WATP/CL_BO_BCMSGTMPL /WATP/CL_BO_BCOBUPROFILE /WATP/CL_BO_BCOBUSOFTWARE /WATP/CL_BO_BCOPHSTRY /WATP/CL_BO_BCSERSTATEHSTRY /WATP/CL_BO_BCSERVICERESULT /WATP/CL_BO_BCSTAFFTIMERECORD /WATP/CL_BO_BCSWUORDER /WATP/CL_BO_BCSWUORDPOS /WATP/CL_BO_BCSYSREQRESULT /WATP/CL_BO_BCTOURRESULT /WATP/CL_BO_BCWEIGHBILL /WATP/CL_BO_CYCLTMPL /WATP/CL_BO_DOCHSTRY /WATP/CL_BO_MSGHSTRY /WATP/CL_BO_ORDRHSTRY /WATP/CL_BO_ORPSHSTRY /WATP/CL_BO_PLANAREA /WATP/CL_BO_PLANPROFILE /WATP/CL_BO_PLANSET /WATP/CL_BO_PLNGRP /WATP/CL_BO_PLNGRPEAP /WATP/CL_BO_PLNGRPEAR /WATP/CL_BO_TPCPCNFG /WATP/CL_BO_TPOPCNFG /WATP/CL_BO_TPRPCNFG short descritption of business object waste approval declaration analysis NGS modul . size of row at displaying configuration shortterm planning planning tree configuration of user-tailored planning area technical name /WATP/ARNW /WATP/ARDL /WATP/ARNG /WATP/BCNM /WATP/GIS /WATP/BCAH /WATP/BCCH /WATP/BCCR /WATP/BCEA /WATP/BCEH /WATP/BCMT /WATP/BCOR /WATP/BCSW /WATP/BCOH /WATP/BCSH /WATP/BCSR /WATP/BCST /WATP/BCSO /WATP/BCSP /WATP/BCSQ /WATP/BCTR /WATP/BCWB /WATP/BCCT /WATP/BCDH /WATP/BCMH /WATP/BCTH /WATP/BCCI /WATP/TPPA /WATP/TPPF /WATP/TPPS /WATP/TPPG /WATP/TPPG /WATP/TPPG /WATP/TPCC /WATP/TPCO /WATP/TPCR localization package /WATP/ARB /WATP/ARB /WATP/ARB /WATP/BC_EEWA /WATP/MAP /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ON-BOARD-COMPUTER /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING /WATP/ORDER_PROCESSING German Figure 46: Authorization Objects delivered with the Add-on © PROLOGA GmbH SAP® Applications by PROLOGA 4.

Sign up to vote on this title
UsefulNot useful