SAP Environmental Compliance 3.0

Transcription

1 Implementation Guide Document Version: 9.3 December 2017

2 Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> EXAMPLE Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions

3 Document History Caution This guide is regularly updated. Before you start the implementation, make sure that you have the latest version of this document that is available on SAP Help Portal at Version Change 1.00 (January 22th, 2009) Initial Creation 2.00 (February 27th, 2009) Fixes ITSAM and Validation 2.10 (Match 19th, 2009) Patch 2: Update user groups (optional) in Migration Steps 2.20 (March 27th, 2009) Patch 2: UWL configuration fix 2.30 (April 29th, 2009) Patch 3: BW/BI configuration fix 2.40 (June 03rd, 2009) Patch 3: Rename the Deployment files of Patch 2 and (June 25th, 2009) Support Package 1: Enhance description of the scheduled jobs, BW configuration and update configuration of archiving 2.60 (July 02nd, 2009) SP1 Patch 1: New chapter Personalizing EC View Elements 2.70 (October 29th, 2009) SP1 Patch 1: New chapter Importing ERP Transport for EHS Integration 3.00 (January 08th, 2010) SP2 Patch 1: BW Documentation has been revised 3.10 (January 26th, 2010) SP2 Patch 2: Update units handling in EC Web Services, and fix the SAP Note to SapTrans 3.20 (February 03th, 2010) SP2 Patch 3: Set up scheduled jobs is mentioned in the post installation steps 3.30 (March 02nd, 2010) SP2 Patch 5: update Support Packages and Patch Implementation chapter Support Packages and Patch Implementation and the UWL Configuration note (April 26th, 2010) SP3: Update chapter Using KM Integration in EC 3.50 (July 1st, 2010) SP4: New chapters Configuring Object-Based Navigation and 7.4 Migration of EC Installations 3.51 (July 15th, 2010) SP4 PL1: new trouble shoot chapters There Is No iview Available for SAP_ECC and Personalization of EC Pages Does Not Work 3.60 (August 25th, 2010) SP5: Change the SAP NetWeaver CE 7.1 requirement from SP7 to SP (October 04th, 2010) SP6: New migration process from EC20 SP15 to EC30 SP6 for chapter 7.4 Migration of EC Installations Document History 2017 SAP SE or an SAP affiliate company. All rights reserved. 3

4 Version Change 4.1 (December 02nd, 2010) SP7: New trouble shooting chapters 4.2 (February 16th, 2011) SP8: Description of EHS integration parameters and Web Service return codes. MII 12.1 reference. 4.3 (March 30th, 2011) SP9: 4.4 (August 4th, 2011) SP10: New measurement Web Service domeasurementimport-extended New chapter Regulatory Content Integration Three new background jobs for using regulatory content BI Installation Guide adapted BI Content updated BI Content chapter updated Support NW CE 7.30 SP2 EC Export / Import tool New Media DVD (See Media List) 4.5 (January 30th, 2012) SP11: Import EC User Groups installation step is mandatory 4.6 (February 3rd, 2012) SP11 Patch 2: Installation step order number has been changed #1 Import User Groups #2 Import init / delta data 5.0 (May 3rd, 2012) EC 3.0 SP12 (Feature Pack 2): Refactor the whole document New chapter 8 Enterprise Energy Management New EHS integration program for ECC (October 1st, 2012) EC 3.0 SP13 PL0 and PL1: SAP EEM BI content activation guide Russian 2TP-Reporting 5.2 (November 22th, 2012) EC 3.0 SP13 SP3: Update chapter 6.12 Data Export and Data Import 5.3 (January 17th, 2013) EC 3.0 SP13 SP6: Migration of Permissions from EC 2.0 to EC 3.0 How to get the WSDL file and the Web Service URL MII 12.2 Actions 5.4 (February 08th, 2013) EC 3.0 SP14: Adobe Document Services set up for NW 7.20 NW 7.30 NW (May 10th, 2013) EC 3.0 SP14 PL2: Trouble shoot for the EC Export Import tool EC Export Import tool: fix of wrong URLs SAP SE or an SAP affiliate company. All rights reserved. Document History

5 Version Change 5.6 (July 29th, 2013) EC 3.0 SP15: Integration into SAP Portfolio and Project Management Export of LOV data 5.7 (September 20th, 2013) EC 3.0 SP15 Patch 2: New parameter in Web Service EnergyAnalyticsExport getassetallocations 5.8 (November 20th, 2013) EC 3.0 SP15 Patch 10 Patch 12: New reference page for trouble shooting RFC connections New Delivery Strategy Note New trouble shooting topic for permission issues EC runs now on NW 7.40 (non HANA) 5.9 (January 8th, 2014) EC 3.0 SP15 Patch 13: 6.0 (March 19th, 2014) EC 3.0 SP16 Patch 0: URL of EC ( Step by Step Documentation Note Import Export Tool: new rules for importing configuration data Import Export Tool: trouble shoot Consumption, emission and measurement Web Service with User Defined Fields New doconsumptioncalcflagsetting operation the EC_ConsumptionImport Web Service Renaming of one Web Service 7.0 (July 14th, 2014) EC 3.0 SP17 Patch 0: Changing authorization for the Energy Analytics Web Services New SAP Notes to create customer extractor and customer Regulatory Content Provider New chapter Develop own RCP Provider Installing the Environmental Compliance MII 14.0 Actions Remove xmii 11.5 from the guide. 8.0 (February 2015) EC 30 SP18 Patch 0: 8.1 (September 2015) EC 30 SP19 Patch 0: New chapter Web Service Status Information of Emissions, Consumptions, and Measurements Setup of Extension Point (SAP Knowledge Management) use HTTPS Url Import Transactional Data with UDFs Set up the notification in the SAP NetWeaver Administration Document History 2017 SAP SE or an SAP affiliate company. All rights reserved. 5

6 Version Change 9.0 (March 2016) EC 30 SP20 Patch 0: 9.1 (November 2016) EC 30 SP21 Patch 0: Rename 0FUNC_LOC to 0FUNCT_LOC in chapter Activation of BW Content (New Installation) Add 0ALTITUDE in chapter Activation of BW Content (New Installation) Run the data migration "EC User, Roles and Group Migration" in chapter Assigning Users Run the data migration "Delta Data Migration" in chapter Uploading Initial EC Delivery Content New configuration steps in chapter Setting up Configurations SAP EC Runs on SAP NetWeaver 7.50 Update chapter How to Get WSDL File and Web Service URLs Update the chapter Export Content Data Remove chapter: Integration into SAP Portfolio and Project Management support 9.2 (May 2017) EC 30 SP22: Update chapter Three Tier Authentication Concept 9.3 (December 2017) EC 30 SP23: Add new data protection and privacy function SAP SE or an SAP affiliate company. All rights reserved. Document History

7 Table of Contents 1 Getting Started Purpose Planning Information Related Information Further Useful Links Important SAP Notes Overview Software Units of EC System Landscape Installation Information Planning Naming Conventions Preparation Hardware Requirements Software Requirements Installation Quick Overview Installing SAP NetWeaver Deploying the EC Application Importing EC User Groups Uploading Initial EC Delivery Content Setting up Configurations Post-Installation Restarting the System Assigning Users Setting Up Adobe Document Service Settings Setting Up Federal Portal Using EP WorkProtect Mode Setting Up System Types Setting Up Deployable Application Properties Configuring the Universal Work List Installing BI Content Checking Internet Graphics Service (IGS) Settings Personalizing EC View Elements Importing ERP Transport for EHS Integration Setting Up Scheduled Periodic Tasks Configuring Object-Based Navigation Security Information Application Security Role and Authorization Concept Table of Contents 2017 SAP SE or an SAP affiliate company. All rights reserved. 7

8 5.1.2 Three Tier Authentication Concept Network and Communication Security Data Protection Introduction Glossary User Consent Read Access Logging Information Report Deletion of Personal Data Change Log Monitoring Tools Alert Monitoring with CCMS CCMS Monitoring Installation and Setup Component Specific Monitoring Detailed Monitoring and Tools for Problem and Performance Analysis Trace and Log Files Interface Monitors Data Growth and Data Archiving Basic Configuration Archiving Write Archives Delete Archives Monitor Archives Search Archives Management Tools Start and Stop Tools Software Configuration Backup and Restore Application Copy Periodic Tasks Load Balancing User Management Technical Interfaces Web Services Interfaces to SAP EHS Management as Part of SAP ERP Interfaces into SAP MII Knowledge Management Integration Customer Development (Extension Point) Regulatory Content Integration High Availability Software Change Management Transport and Change Management Development Requests and Development Release Management Release Implementation Support Packages and Patch Implementation Troubleshooting Imported Initial or Delta Data Does Not Appear in EC Logged-In User Has No Permission for an EC Object Report Generation Does Not Work SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

9 Notification Does Not Work EC Object Is Locked Web Services Does Not Import All Data Graphics Rendering (IGS) Problem Java Scheduler Jobs Do Not Work There Is No iview Available for SAP_ECC Personalization of EC Pages Does Not Work Processing of Java Scheduler Jobs Takes Too Long System Copy Mode Remains in EC after Running Export or Import EHS Integration Data Transfer Errors Errors in EC Import / Export Tool SAP EC Permission Problems Support Desk Management Remote Support Setup Remote Debugging Problem Message Handover BI / BW Content Introduction EC Extraction Layer BI InfoProviders Data Export and Data Import Export Content Data Import Content Data Import Data with SAPTrans (Obsolete as of EC 3.0 SP10) Migration of SAP EC Introduction Prerequisites Detailed Migration Steps Migration of EC Installations Import Default User Groups Import Database Content Import Delta Data Content of EC Run the Data Migrations SAP BI Content Migration Enterprise Portal Content Migration Migration of Permissions from EC 2.0 to EC Enterprise Energy Management EEM Introduction EEM Installation Description EEM as Part of EC 3.0 SP EEM System Setup / Installation EEM Database Data Import Application Authorization EEM BI Content EEM BI Content Activation Guide Business Process Description Maintenance of Master Maintenance of Transactional Data Table of Contents 2017 SAP SE or an SAP affiliate company. All rights reserved. 9

10 8.5.3 Calculation of Emission Data Energy Costs Generic Facility Related Key Figures Units and Dimensions Data Extraction into Business Warehouse Setup of the Extraction Process Extraction of Master Data Extraction of Transactional Data BI Data Model BI Reporting Enterprise Energy Management BI Content BI Content Description Russian 2TP-Reporting TP-Reporting as Part of SP13 PL Reporting System Setup / Installation Reporting Database Data Import TP-Reporting System Configuration Classifiers & List of Values Facility Type Hierarchy Facility Type Properties Media List SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

11 1 Getting Started 1.1 Purpose This guide includes all relevant information for the technical implementation of SAP Environmental Compliance 3.0 as well as information about configuration, upgrade, and data migration. In addition, it contains information how to operate the system and security information. Note We strongly recommend that you use the most recent version of this document, which you can find on the SAP Help Portal at Getting Started 2017 SAP SE or an SAP affiliate company. All rights reserved. 11

12 2 Planning Information 2.1 Related Information For more information about implementation topics not covered in this guide, see the following content on the SAP Support Portal: Content Sizing of SAP Applications with the Quick Sizer tool Sizing of SAP Environmental Compliance Platform Availability Matrix (Technical Releases) - released platforms and technology-related topics, such as maintenance strategies and language support Information about Support Package Stacks, latest software versions and patch level requirements Location on SAP Service Marketplace g.quick-sizer.html (Search the SAP Application: "SAP ENVIRONMENTAL COMPL. 3.0") Further Useful Links The following table lists where you can find more information on the SAP Support Portal: Content Information about creating product error Incidents SAP Notes search SAP Software Distribution Center (software download and ordering of software) SAP Early Knowledge Transfer role-specific Learning Maps Location on SAP Service Marketplace SAP SE or an SAP affiliate company. All rights reserved. Planning Information

13 2.3 Important SAP Notes You have to read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find on the SAP Support Portal at SAP Note Number Title Central Note Release Notes EC Date and Time Handling SAP EC 3.0 adjustment of XSLT Templates for EC Reporting BI Additional Documentation for Environmental Compliance MII 12.0 Actions for Environmental Compliance Using Units in EC 3.0 Web Services Object Based Navigation in Env. Compliance 3.0 SP2 PL EC 3.0 Installation Note: Import EC User Groups SAP MII 12.1 Actions for Environmental Compliance EC 3.0 example BI Content for higher BI_CONT releases Using EC 3.0 export import tool Slow performance of EC 3.0 transactional data web services UME Principal Update is not reflected in UME Cache EC 3.0 Enterprise Energy Management initial data content Feature Release Notes for SAP EC 3.0 SP15 (Feature Pack 3) Software delivery strategy of Environmental Compliance Installation of EC BI Content TDAGECB 331 on SAP NW 7.31 and SAP NW Developing own regulatory content provider in SAP EC Developing own BI extractors in SAP Environmental Compliance Poor performance when EC transactional data read Archiving SAP Environmental Compliance data Installing SPx the first time Composite SAP Note for BI topics in SAP EC Error during saving - no reply within 10s Migration from SAP xem 2.0 to SAP EC 3.0 Planning Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 13

14 Composite SAP Note for calculation topics in SAP Environmental Compliance Loss of authorizations after the import of patch or Support Package Error during saving - no reply within 10s SAP SE or an SAP affiliate company. All rights reserved. Planning Information

15 3 Overview (EC) helps reduce operational and financial risks, optimizes operating efficiencies, and improves shareholder value by ensuring that auditable, standardized, and transparent environmental processes for compliance and risk assessment are incorporated into daily business operations. The solution is highly integrated and can be deployed globally across an enterprise servicing various jurisdictions both at the plant and corporate level. The solution supports business processes for all three environmental domains of air, waste water, and waste compliance and additionally supports enterprise energy management initiatives. Business processes to support compliance with permits for air and waste water regulations can be seamlessly deployed across different business units ensuring timely generation of government reports. The Green House Gas (GHG) business process for monitoring emissions, credits accounting, and reduction initiatives can also be supported with this solution ensuring compliance with local and global regulations and thereby reducing the risk for operational and financial risk. 3.1 Software Units of EC SAP EC is delivered in several software components (SC), which have to be deployed on your SAP NetWeaver CE JAVA Web application server and installed on a SAP BI system. The following components are initially delivered with SAP EC 3.0: Application Component Name of the SC File (Example) Software Component Version EC Central Services TDAGECSSERV300SP15P_1 ECS_SERVICES 3.0 SP 15 Patch 1 EC Central Modules TDAGECSMOD300SP15P_1 ECS_MODULES 3.0 SP15 Patch 1 EC Application Modules TDAGXEMMOD300SP15P_1 XEM_MODULES 3.0 SP15 Patch 1 EC Reporting Content TDAGREPCONT300SP15P_1 XEM_REP_CONTENT 3.0 SP 15 PL1 EC Portal Content TDAGECSPC300SP15P_1 ECS_PC 3.0 Patch 1 EC BI Content SAPK-300COINTDAGECB TDAGECB 3.0 The SC BI Content requires a SAP BI 7.0 SP17 or higher installation. The EC 3.0 SCs require SAP NetWeaver CE 7.1 SP8 or higher Java Server. Since EC 3.0 SP6, the EC also runs on SAP NetWeaver CE 7.2 SP3. Since EC 3.0 SP9, the EC also runs on SAP NetWeaver CE 7.3 SP2. Since EC 3.0 SP15, the EC also runs on SAP NetWeaver CE 7.4 SP2. (Non Hana DB) Since EC 3.0 SP21, the EC also runs on SAP NetWeaver CE 7.5 SP4. (Non Hana DB) The PL00 label means that the Support Package is in Patch Level 0 Overview 2017 SAP SE or an SAP affiliate company. All rights reserved. 15

16 3.2 System Landscape The SAP EC 3.0 application consists of five main software components the core packages (running on SAP NetWeaver CE) and the SAP Enterprise Portal. Optionally, the following components can be used or accessed via interfaces: SAP Business Warehouse 7.0 SP17 or higher (running SAP Web Application Server) SAP R/3 (4.6C or higher) Master Data (Material, Substance, and so on) with RFC/BAPI (on project base) The architecture follows the concepts of SAP Enterprise Services Architecture. Client Web Browser UWL EC Portal Content NW Java EC Portal Functions Transactional Data Interface Web Services UWL Connector EC User Interfaces Custom User Interfaces UI Layer Web Dynpro Java EC Application Logic Custom Application Logic Application Layer SAP NW CE 7.1 EC Persistency Services EC BI Extraction Services EC RFC Interfaces Persistency & Interface Layer RFC RFC JDBC (OPEN SQL) BAPI BAPI BW Integrated Systems NW Database EC BI Content EAM, EHS(PS, IH), MM ABAP is hosted on a SAP NetWeaver Composition Environment 7.1. The EC Portal functionality can be either integrated into a SAP Enterprise Portal using the Federated Portal Network (FPN) or used as a standalone solution. The Portal functionality offers EC Portal Content and access to the Unified Worklist that is enhanced by EC Tasks and EC Exceptions. EC 3.0 contains three different software layers the UI layer, the application layer, and the Persistency & Interface layer. The UI layer provides EC user interfaces, the integration of custom user interfaces, UWL connectors to access the EC specific UWL tasks/exceptions, and transactional interfaces to consume or supply data from/to EC 3.0. The EC user interfaces are decoupled from the business logic via a well-defined interface to support the reuse of the business logic for customer-specific user interfaces SAP SE or an SAP affiliate company. All rights reserved. Overview

17 The application layer represents the business logic of EC 3.0, which can be enhanced by customer-specific extensions to offer additional functionality in EC 3.0. The Persistency & Interface layer represents the persistency storage functionality for all EC business objects that are stored in a NetWeaver database. In addition, BI Extraction Services and RFC interfaces offer access to BI content and integrated systems. Caution We strongly recommend that you use a minimal system landscape for test and demo purposes only. For performance, scalability, high availability, and security reasons, do not use a minimal system landscape as your production landscape. Overview 2017 SAP SE or an SAP affiliate company. All rights reserved. 17

18 4 Installation Information 4.1 Planning (EC) can be migrated only from EC 2.0 SP16. If you are working with EC 2.0 older than SP16, then you first must update to EC 2.0 SP16. For information about the update process, see chapter 7 Migration of SAP EC. Careful planning is a prerequisite for the successful installation of the system Naming Conventions In this documentation, the following naming conventions are used: Variable <SID> <INSTNO> <EC-DIR> <INSTDRIVE> <host> <port> Description SAP system ID in uppercase letters SAP system Instance number The Environmental Compliance delivery directory. The directory where the SAP system is installed: On Windows systems, you can find the <INSTDRIVE> by entering following in the Explorer: \\<host>\sapmnt On Unix systems, you can find the <INSTDRIVE> for default under /usr/sap/ Web server name TCP port number on which the server is listening for HTTP requests. Default value is usually Process Flow 1. You print out the relevant checklist. o To install, see chapter 4.3 Installation. o To upgrade, see chapter 7 Migration of SAP EC. 2. You print out the relevant documentation. o SAP Notes in chapter 2.3 Important SAP Notes o Functional Documentation for SAP Environmental Compliance on the SAP Help Portal at SAP SE or an SAP affiliate company. All rights reserved. Installation Information

19 3. You follow the installation sequence exactly as shown in the tables. o If a step is required for your installation, you follow the link for that step to the corresponding section. o You perform the procedure described there. o After you complete the installation step, mark the corresponding entry in the printed table with! to log the progress of your installation. o You proceed with the next step listed in the table of the installation quick overview. 4.2 Preparation Before starting the installation, the following items must be taken into consideration: Hardware Requirements The following table lists the hardware requirements of SAP EC, which are primarily dependent on the requirements of the SAP J2EE Engine. The host machine for the SAP NetWeaver Web Application Server (EC target platform) must meet the following requirements: Requirement Type Hardware Requirements Recommendation Software Requirements Requirement Disk Space: 5 GB RAM: 1 GB CPU: 2 GHz For optimal performance, we recommend a multi-processor machine with each CPU having not less than 2 GHz A multi-processor (dual or quad) system is recommended for optimal performance, where each CPU should have not less than 2 GHz clock speed. The J2EE engine performs best with 2GB of RAM or more available to it. The memory should be distributed between the dispatcher (>512MB) and the server nodes (>1024MB). Make sure that all allocated memory is available physically. Take the operating system s own memory requirements into account. Operating System: See the SAP Product Availability Matrix ( SAP JVM delivered with NetWeaver Java stack The client workstations must meet the following requirements: Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 19

20 Requirement Type Hardware Requirements Requirement CPU: 1 GHz RAM: 512 MB Monitor resolution 1024 x 768 or higher Software Requirements Requirement Type Requirement Basic Requirements SAP NetWeaver CE 7.1 SP8 or higher Required usage type For NW 7.10 / 7.11 required usage is Composite Applications For NW 7.20 required usage is Composite Environment Platform For NW 7.30 / 7.31 required usage is Composition Platform For NW 7.40 required usage is Composition Platform (NW 7.40 with a non HANA Database!) For NW 7.50 SP04 required usage is Composition Platform (NW 7.50 with a non HANA Database!) Microsoft Internet Explorer 6 or higher Firefox 2.0 or higher Optional Software Components SAP NetWeaver 7.0 Enterprise Portal 7.0 SP10 and higher Adobe Document Services 7.0 SP10 or higher Supporting System Corporate User Persistence (LDAP) Environmental Compliance 3.0 can be downloaded from the SAP Support Portal. For more information, see chapter Release Implementation and Support Packages and Patch Implementation or the SAP Product Availability Matrix (PAM) for EC. 4.3 Installation Quick Overview! Action Install SAP NetWeaver CE 7.1 SP8 or higher Deploy the Environmental Compliance application to the SAP NetWeaver Server SAP SE or an SAP affiliate company. All rights reserved. Installation Information

21 Import Environmental Compliance User Groups Upload the initial Environmental Compliance data to the target database Set up Configuration Installing SAP NetWeaver Use Use the NetWeaver Java stack to install the latest SAP NetWeaver CE 7.1 or a later release such as NW 7.11 or NW 7.20 or NW 7.30 or NW 7.31 or NW 7.40 or NW Prerequisites Ensure that the operating system is installed properly and the current user has administrator permissions. Procedure For more information about installing SAP NetWeaver (J2EE Engine), go to Deploying the EC Application Use The EC application is delivered in different software components (see chapter 3.1 Software Units of EC). All the software components have to be deployed with JSPM tool or SUM on the SAP NetWeaver Web Application Server. For more information about JSPM, go to the SAP Help at: Prerequisites Ensure that the SAP NetWeaver CE (J2EE Engine) is properly installed and all services are running. You can control this by using the SAP Management Console. Procedure! Action Navigate to the Environmental Compliance 3.0 installation directory Copy all software components (SCs) (see chapter 3.1 Software Units of EC) files: from <EC-DIR>\Deployment\ into the directory <INSTDRIVE>\sapmnt\trans\EPS\in Start the SAP Software Delivery Tool (JSPM) by executing <INSTDRIVE>\sap\<SID>\JC<INSTNO>\j2ee\JSPM\go.bat on Windows systems or <INSTDRIVE>\sap\<SID>\JC<INSTNO>\j2ee\JSPM\go on Unix systems Log in with the SAP NetWeaver CE administrator password Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 21

22 Select the package type: New Software Component Choose the Next button to proceed to the next steps The SAP Software Delivery tool shows the software components - Deploy the following files: - TDAGECSSERV30000P_1 - TDAGECSMOD30000P_1 - TDAGXEMMOD30000P_1 - TDAGXEMREPCONT30000P_1 - TDAGECSPC30000P_1 NOTE: The name of the files in the further patches has been changed. - ECSSERV300SP15P_x - ECSMOD300SP15P_x - XEMMOD300SP15P_x - REPCONT300SP15P_x - ECSPC300SP15P_x Choose the Next button to go to the next steps and start the deployment After successful deployment, you can exit from SAP Software Delivery tool Note When is installed for the very first time, download and install the latest Patch of the latest available Support Package. There is no need to deploy the SAP Environmental Compliance 3.0 SP0 Patch 0 the first time Importing EC User Groups Use Environmental Compliance 3.0 is delivered with predefined User Management Engine (UME) User Groups and the EC standard roles, which enables you to start using the Environmental Compliance application quickly. This installation step is MANDATORY. The user groups file and the related user roles are attached, see SAP Note Prerequisites Ensure that Environmental Compliance is deployed on the SAP NetWeaver Application Server. Procedure! Action Log in to the user administration ( with an administrator user SAP SE or an SAP affiliate company. All rights reserved. Installation Information

23 Navigate to the import tab Open roles text file which match with your Netweaver Release and EC Version number Select the Overwrite Existing Data Import the user roles Open groups text file DO NOT select the Overwrite Existing Data Import the user groups Note For information about importing data in the UME, see the SAP Help at: t.htm Uploading Initial EC Delivery Content Use SAP Environmental Compliance requires the availability of initial data content. The content is uploaded with the EC import tool. For more information, see SAP Note: or chapter 6.12 Data Export and Data Import. Prerequisites Ensure that is deployed on the SAP NetWeaver Application Server, the server is running, and the user roles and user groups has been imported. The EC administration user needs to be assigned to the EC Group: UMEGROUP_Environmental Compliance Admin. Procedure! Action Extract the ZIP File (attached to the latest Support Package SAP Note) with the import content data on the server in an empty folder. Set up grant full permission for user SAPService<SID> on the selected migration folder. Start the Import tool Content Import in EC Tools Menu or run the URL: The EC 3.0 user needs Environmental Compliance Admin permissions. The application needs the Permission Action EC_ExportImportData. Select the folder on the server. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 23

24 Start the import of data During the import process, the EC 3.0 system is in system copy mode. That means all database operations in EC 3.0 are stopped. After the import process the system reset the copy mode. If the reset of the copy mode does not work as expected, click the link Navigate to Reset Copy View and reset manually the copy mode. Note If the message appears Some tables already contain data. Do you want to start import and replace them with the import data? : During the import process, the system overwrites the data that is defined in the exporting XML file and already exists in the system. In case of initial or delta data, only data in a special range is overwritten. The customer data is not overwritten Run the data migration "Delta Data Migration" in SAP EC Administration menu Setting up Configurations Use The notification in works by sending . In this case, you need to set up the configuration in the SAP NetWeaver environment. Prerequisites Ensure that Environmental Compliance is deployed on the SAP NetWeaver Server. Procedure New Steps:! Action Go to the SAP NetWeaver Administrator ( Navigate to Configuration Infrastructure Java System Properties In the Java System Properties Overview change to the Tab Services Search the property Java Mail Client Set up by clicking the button Modify the following properties: mail.from mail.smtp.host mail.smtp.password Save the changes SAP SE or an SAP affiliate company. All rights reserved. Installation Information

25 The configuration needs a further step in the EC Configuration Templates. For more information about the EC Templates, see the topic Notification of the Functional Documentation for EC at The notification functionality can be tested in the EC Administration System Checks. 4.4 Post-Installation You have to carry out the following post-installation steps:! Action Restart System User Assignment Set up Adobe Document Service settings Setup Federal Portal when using EP 7.0 Work Protect Mode Unified Work List (UWL) configuration Set up EC Properties Set up Deployable Application properties BI / BW Installation Content Guide Check the Internet Graphics Service (IGS) settings Personalize EC View elements Import ERP Transport for EHS Integration Set up the scheduled periodic tasks Object Based Navigation Restarting the System Use After finishing the installation steps, the SAP NetWeaver Web Application Servers have to be restarted. Prerequisites You have completed all installation steps. Procedure There are two different ways to restart the system. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 25

26 The first way is to restart the whole cluster. This step is needed when you make changes in the Config Tool ( notification settings).! Action Log in directly to the OS of the SAP NetWeaver Web Application Server. Start the SAP Management Console. Select the upper node of your SAP NetWeaver Web Application Server and select with the right Mouse click Restart button. After entering the Administrator user and password the SAP NetWeaver Web. Application Server is restarted. The second way is to restart only the SAP NetWeaver Server Instances after you deploy EC deployable files. This method is quicker.! Action Log in to the NWA ( with an administrator user Restart every Server Process of each instance Enter the Administrator password in the pop-up window Assigning Users Use The user assignment is a basic step to set up the different users for the different Environmental Compliance processes. Prerequisites You have completed all installation steps. Procedure For assigning users in SAP NetWeaver CE, see the SAP Help: Note We recommend assigning the role pcd:portal_content/every_user/general/eu_role for the EC Users to activate the Personalize Menu for Work Protect mode settings. For more information about pcd:portal_content/every_user/general/eu_role, see the SAP Help Portal at tm SAP SE or an SAP affiliate company. All rights reserved. Installation Information

27 In the next step, we recommend assigning the EC users or user groups to the EC groups (imported in the chapter Importing EC User Groups). For more information about EC groups and roles, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal at The permission recommendation for the EC Administrator user is the following: Do not use any EC Roles assignment Add the following USER Groups to the EC user: o UMEGROUP_Compliance Analyst o UMEGROUP_Environmental Analyst o UMEGROUP_Environmental Compliance Admin These thee User Groups have the full permissions of the EC application. You can access the EC application by running following URL: The EC application appears in the Tab Environmental Performance Run the data migration "EC User, Roles and Group Migration" in SAP EC Administration menu. To finish this setup step Setting Up Adobe Document Service Settings Use The Adobe Document Service is needed for creating reports and queries. SAP NetWeaver CE is delivered with Adobe Document Service. Prerequisites You have completed all installation steps. Procedure For set up Adobe Document Service see the one of the following documentations: Netweaver Netweaver Netweaver Netweaver Netweaver 7.31 (Java stack) Netweaver 7.4 (Java stack) Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 27

28 Netweaver 7.5 (Java stack) Setting Up Federal Portal Using EP 7.0 Use The federated portal network capabilities of SAP NetWeaver enable you to share content between distributed portal installations, both SAP and non-sap; thus, providing a single portal access point per user to portal information, services, and applications distributed on portals throughout the entire organizational network. Prerequisites If you use SAP Enterprise Portal on 7.0 or 7.01, you have completed all installation steps. Procedure See chapter Enterprise Portal Content Migration or directly on the SAP Help Portal at WorkProtect Mode Use The WorkProtect mode in EC enables the Enterprise Portal to recognize when the current user wants to change to another Environmental Compliance tab strip and the current Environmental Compliance detail view has unsaved changes. Prerequisites You have completed all installation steps. Procedure For more information about the WorkProtect mode of the SAP Enterprise Portal, see the SAP Help Portal at Note We recommend assigning the role pcd:portal_content/every_user/general/eu_role for all EC Users to activate the Personalize Menu for Work Protect mode settings. For more information about pcd:portal_content/every_user/general/eu_role see the SAP Help Portal at tm In the portal personalization, select for WorkProtect Mode the option "Choose action in popup on unsaved data" SAP SE or an SAP affiliate company. All rights reserved. Installation Information

29 End User Behavior in EC Views When you open an EC View, enter data in an input field, and navigate away immediately, then the application and the portal do not recognize your changes. You are in an Internet Browser and the Web Dynpro has no internal event to catch this change. The correct behavior is to enter the data in the input field and to press ENTER or the TAB key. After that the system shows that you have unsaved changes. Caution The WorkProtect functionality is not implemented in the EC Configuration, EC Maintenance, EC Tools or EC Administration. The reason is that the Configuration area is only accessed by special admin users Setting Up System Types Use The system type should be set up the first time EC 3.0 is installed or updated. The system type is a property of EC Properties. You can find a detailed description of the EC properties in the Description column of the EC properties. Navigate to the EC Properties, go to Configuration Basic Settings EC Properties. Prerequisites You have completed all installation steps. Procedure Navigate to the EC properties. For EC properties access, you need an EC Admin user. You need at least a user (EC Environmental Compliance Admin) that has the user group UMEGROUP_Environmental Compliance Admin. The EC application is delivered in EC 3.0 with the property system.landscape.type value: P. P means productive system. The next table shows an overview of the possible values of the property system.landscape.type : Value D Q P Description Development: All Transport of Configuration options are available. See also chapter Transport and Change Management Quality: Here the data is imported from D, tested and if everything is ok, then moved to P. The Transport of Configuration functionality is not available. Productive System: The Transport of Configuration function is not available. You should adapt this property for every different EC System in your system landscape. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 29

30 4.4.7 Setting Up Deployable Application Properties Use The settings in SAP NetWeaver configuration Tool (Config Tool) set up which deployable applications should be start automatically. Prerequisites You have completed all installation steps. Procedure! Action Go to the SAP NetWeaver Configuration tool \usr\sap\<instance>\j00\j2ee\configtool Run the configtool file See also In the Menu View, change to Expert Mode. Select the Hierarchy element under the cluster-data node. On the right detail screen, navigate to the Filters Tab. Add a new property: Actions: Start Component: application Vendor Mask: technidata.de Component Name Mask: * Add a new property: Actions: Start Component: application Vendor Mask: sap.com Component Name Mask: *energyanalytics*: * Add a new property: Actions: Start Component: application Vendor Mask: sap.com Component Name Mask: *impexp* Add a new property Actions: Start Component: application Vendor Mask: sap.com Component Name Mask: *dataimport* After that, you must restart the whole cluster SAP SE or an SAP affiliate company. All rights reserved. Installation Information

31 4.4.8 Configuring the Universal Work List Use The universal work list (UWL) enables a central and unified access to all work items regardless of their specific type. Therefore, users that have to work with multiple systems do not have to log on to several systems to supervise and process their work items. For this reason, the Tasks and Exceptions of SAP Environmental Compliance are also integrated into the UWL. Procedure Set up the SAP Environmental Compliance specific UWL Connectors according to the following table: System Alias Connector Type Delta Pull Channel Refresh Period (in Seconds) EC Alerts ECAlertProviderConnector 60 EC Tasks ECTaskProviderConnector 60 For more information about registering the provider systems, see the SAP Help Portal: Note o In the SAP Universal Worklist, you cannot set up substitute users for Alerts and Tasks. This setup is only possible in the EC Dashboard for Tasks and Alerts (EC Exceptions) and in the EC Tools My Profile Administration Substitute for Tasks and Alerts (EC Exceptions) o We recommend assigning the Role pcd:portal_content/every_user/general/eu_role for the EC Users to activate the Home tab in the portal application. The home tab contains the Universal Worklist. For more information about pcd:portal_content/every_user/general/eu_role see the SAP Help Portal at et.htm Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 31

32 4.4.9 Installing BI Content Use The delivered BI component contains BI objects needed for the extraction of master data, text data, and transactional data from EC to the BI system. The BW transport consists of the following: 1. InfoCubes 2. ODS-Objects 3. InfoSources 4. InfoPackages 5. ProcessChains 6. InfoObjects All DataSources for InfoCubes do support the delta load of transactional data. The naming conventions for the BW content follow the following rules: DataSources: /TDAG/EM_X, e.g. /TDAG/EM_1 InfoSource: /TDAG/EM_X, e.g. /TDAG/EM_1 ODS-object: /TDAG/EM_DSXX, e.g. /TDAG/EM_DS01 InfoCube: /TDAG/EM_CXX, e.g. /TDAG/EM_C01 [Where X is a chosen identification]. However, the EC content cannot be seen as a standard solution for all business cases. The delivered BW content is a suggestion to the customer, how to make the EC data available for reporting in the SAP Business Warehouse. Prerequisites For the installation of the EC BI content, you must have the most recent service pack for your Business Warehouse installed. Note that support can only be provided if you have the appropriate service packs for your BI release installed (see table below for details). The list below contains the minimum SP Levels for each component that should be available prior to the installation of the EC BI Content. SAP Business Warehouse Version SAP_BW: 700 BI_CONT: 703 Recommended Service Pack Level SP17, SAPKW70017 SP5, SAPKIBIIP5 SAP_BASIS: SAP SE or an SAP affiliate company. All rights reserved. Installation Information

33 Procedure and Preparation Activation The following SAP standard BW objects are used by EC BW content. They need to be activated in the BW system: 0CALYEAR 0CALDAY 0CALMONTH 0CALQUARTER 0UNIT 0CHNGID 0CURRENCY 0DATE 0DATEFROM 0DATETO 0TIME 0HIER_NODE 0HIENM 0HIER_HIEID 0HIER_VERS 0EQUIPMENT 0FUNCT_LOC 0PRECISID 0SRCID 0COUNTRY 0REGION 0RECORDMODE 0RECORDTP 0REQUID 0MATERIAL Activate these BW objects with transactionrsor with option Only necessary objects. Note If these InfoObjects have been activated successfully but cannot be found in transactionrsa1, see SAP Note Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 33

34 Installation The SAP EC 3.0 BI-Content is delivered as an Add-On Package that can be installed via the Add-On Installation Tool (Transaction SAINT). Prior to the installation via Add-On Installation Tool, move the File containing the EC BI Content SAPK-300COINTDAGECB.SAR to the appropriate /usr/sap/trans/ inbox. The password for the installation is in SAP Note You can unpack the SAPK-300COINTDAGECB.SAR file with the SAPCAR tool with the command /SAPCAR.EXE -xvf SAPK-300COINTDAGECB.SAR. Note The packed SAR file contains the following folder structure: /EPS/in/. The SAR file contains a file named XBA _ PAT. The latest SAPCAR can be downloaded from the SAP Support Portal Namespaces The required Namespaces are automatically installed after successful installation of the EC BI-Content via the Add-On Installation Tool (Transaction SAINT). The provided namespaces for TDAG-BW objects are: /TDAG/ - Namespace for TechniData objects /B123/ - Namespace for generated TechniData objects After the import and activation of the namespaces, you can verify the namespaces in transactionrsnspace. The table shows the declared entries in the BW partner namespaces. Namespace Gen Namespace BW Application System type Active /TDAG/ /B123/ BW PAR X In addition to creating the namespaces (either manually or via the transport mentioned above), you must specify the two new namespaces as modifiable in transactionse03. This is necessary, due to the fact, that all delivered BW objects in these namespaces have to be activated and this is only possible if the namespaces are specified as modifiable in the customer system. To do this carry out the following steps: 1. Call transactionse03 2. Select Set System Change options 3. Locate the namespaces /B123/ and /TDAG/ and set them to modifiable SAP SE or an SAP affiliate company. All rights reserved. Installation Information

35 Packages The required packages are automatically installed after installation of the EC BI-Content via the Add-On Installation Tool (transactionsaint). After the import and installation of the packages necessary for EC, verify the packages in transactionse80. Select in the drop-down menu the entry packages. The following packages should be successfully configured: /TDAG/CO /TDAG/EM Maintain Source System EC For the extraction of data from EC to the SAP BI, a new source system needs to be created. This has to be done manually because source systems cannot be transported in the SAP BI. To assign the source system EC to BI, use TA RSA1 and create a new source system: 1. Type: External system (Data and Metadata Transfer using Staging BAPI) 2. Connection type TCP/IP 3. Enter description and program ID: EC. 4. Make sure to enter the correct type and release of the source system. Logical System Name Source System Name Type and Release XEM XEM XEM020 Note Use the Type XEM020 also in EC 3.0 Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 35

36 If an error message appears and states that the BW user does not exist in table RSADMIN, see the SAP Note Note o Check if the source system of the BI self-def d is activated. o To verify if the source system is created correctly, call TA WE20 and check if the Partner Profile Partner Type Logical System is created with EC and check under tab Classification the Partn.status = A (Active, partner profile can be used). If this is not the case, visit TA RSA1 and select source systems. Click on the EC source system and select the option Restore. When the source system is restored, call transaction WE20 again and check if the partner profile is active and created correctly. o If the source system is already present, due to a former EC BW content installation, it is mandatory to perform a source system restore. Go to transaction RSA1, select the source system, and there choose the EC data source. Right-click the EC source system and choose restore from the menu. After restoring, activate the source system. After activating the source system. We recommend that you replicate and reactivate the logical system. The logical system is also located in the source systems. Right-click the source system logical system and select replicate from the menu User for Extraction and Test The remote user in SAP Business Warehouse is generally called ALEREMOTE. The remote user in BW must have the correct authorizations for extraction data. Assign the profiles S_BI-WHM_RFC and S_BI_WX_RFC to the remote user. Note To test the RFC connection from the BW system to the EC system, the RFC connection must be configured in EC. For more information see the chapters System Settings and EC RFC Setup. To verify if the source system and the remote user are configured correctly, follow the steps pointed out below: 1. Refer to the chapters System Settings and EC RFC Setup to start the RFC Server. 2. Check connection on BW-side with TA RSA1 > Source systems, select xem, context menu, select test. 3. Verify that the correct system has registered at the BW system. Use transactionsm59 -> TCP/IP Connections and select xem. 1. Click Test Connection to see if a connection has been established. 2. Select in the menu bar System Information -> Target System and make sure that the system you are connected to is the correct host. Note We recommend restoring the source system. This is done in the administrator workbench by selecting TA RSA1 > Source systems, select xem, context menu, select restore option. The BW system recreates all generated programs for this source system. After restoring, activate the source SAP SE or an SAP affiliate company. All rights reserved. Installation Information

37 Activation of BW Content (New Installation) After the completion of all actions described in chapter Procedure and Preparation, all BI-Content objects required for SAP EC are automatically installed. After the installation, the BI Content objects need to be activated, which is described in this part of the guide Activation of EC BW content The activation of BW Object is done in transactionrsor under BI Content. The BW Object for EC has to be activated in the following sequence: 1. Activate Info Object by Info Areas 2. Activate Info Providers by Info Areas 3. Process Chains by Object Types For the activation, you need to adjust the settings prior to the selection of the content Activation of Info Object by Info Areas You have the following select options: Grouping: Only necessary objects Source System assignment: xem Collection Mode: Collect automatically Select the InfoObject Catalogs in left menu and click on Select Objects. Transfer the following InfoObject catalogs into the activation dialog: /TDAG/CO_CHA01 PM/EM: Characteristics /TDAG/CO_KYF01 PM/EM: Key Figures /TDAG/EM_CHA01 EM: Characteristics /TDAG/EM_KYF01 EM: Key Figures Note We recommend removing the SAP standard objects before activating. For all SAP standard objects, select in mouse context menu the option Do not install any below. The following list provides a short summary (use the search option to find the items): Search for Object 0ALTITUDE and select Do not install any below. Search for Object 0EQUIPMENT and select Do not install any below. Search for Object 0FUNCT_LOC and select Do not install any below. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 37

38 Search for Object 0MATERIAL and select Do not install any below. Search for Object 0PRECISID and select Do not install any below. Search for Object 0SRCID and select Do not install any below. Search for Object 0COUNTRY and select Do not install any below. Select install Install. This starts the activation of the selected objects. Check the status of the background task in SM Activation of InfoProviders by Info Areas The activation of InfoCubes needs to have a different grouping option. Grouping -> In Dataflow Before Source System assignment -> xem Collection Mode -> Collect automatically The In Dataflow Before option includes all objects below the InfoCube (ODS objects, InfoSources, InfoObjects etc). The following InfoCubes have to be activated: /TDAG/EM_C01 Emissions /TDAG/EM_C01A Emissions Scenarios /TDAG/EM_C01B Emissions by material classifiers /TDAG/EM_C01C Emissions by material groups /TDAG/EM_C02 Consumptions /TDAG/EM_C02A Consumption Scenarios /TDAG/EM_C02B Consumptions by material classifiers /TDAG/EM_C02C Consumptions by material groups /TDAG/EM_C04 Tasks /TDAG/EM_C05 Measurements /TDAG/EM_C05B Measurements by material classifiers /TDAG/EM_C05C Measurements by material groups /TDAG/EM_C06 Exceptions /TDAG/EM_C07 Limit Reports To activate the content, procced as follows: 1. Select item InfoProviders in the navigation pane of RSOR. 2. Drag the InfoCubes starting with /TDAG/EM to the right pane. 3. Mark all entries in right pane using the select all button SAP SE or an SAP affiliate company. All rights reserved. Installation Information

39 Note We recommend removing the SAP standard objects before activating. For all SAP standard objects, select in context menu the option Do not install any below. The following list provides a short summary (use the search option to find the items): Search for Object 0EQUIPMENT and select Do not install any below. Search for Object 0FUNC_LOC and select Do not install any below. Search for Object 0MATERIAL and select Do not install any below. Search for Object 0PRECISID and select Do not install any below. Search for Object 0SRCID and select Do not install any below. Search for Object 0COUNTRY and select Do not install any below. Select install Install. This starts the activation of the selected objects. Check the status of the background task in SM Activation of Process Chains by Object Types The following table shows all xem process chains: Process Chain EM Master data and transactional data (Delta) EM Master data and transactional data (Init) EM Consumption scenarios (Delta) EM Consumption scenarios (Init) EM Consumptions (Delta) EM Consumptions (Init) EM Delete all transaction EM Emission scenarios (Delta) EM Emission scenarios (Init) EM Emissions (Delta) EM Emissions (Init) EM Exception Attribute Delta EM Exception Attribute Init EM Exception UDF Delta EM Exception UDF Init Description Loads all data calling the other process chains) Loads all data calling the other process chains Data loading for InfoCube Data loading for InfoCube Data loading for InfoCube Data loading for InfoCube Deletes all transactional data in the InfoCubes and ODS Data loading for InfoCube Data loading for InfoCube Data loading for InfoCube Data loading for InfoCube Master data loading Master data loading Master data loading Master data loading Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 39

40 EM Exceptions (Delta) EM Exceptions (Init) EM Facility Attribute EM Facility Hierarchy Nodes EM Facility Hierarchy Default EM Facility Hierarchy Legal Entity EM Facility Hierarchy Location EM Facility Hierarchy Organizational Unit EM Facility Hierarchy Regional EM Facility Identifier and Classifier EM Facility UDF EM Master data and hierarchies EM Measurements (Delta) EM Measurements (Init) EM Tasks (Delta) EM Tasks (Init) EM Tasks Attribute (Init) EM Tasks Attributes (Delta) EM Tasks UDF (Delta) EM Tasks UDF (Init) EM Text data EM Text data (optional) EM Master data and hierarchies (optional) EM Emissions by material classifiers (Init) EM Emissions by material classifiers (Delta) EM Emissions by material groups (Init) EM Emissions by material groups (Delta) EM Consumptions by material classifiers (Init) EM Consumptions by material classifiers (Delta) EM Consumptions by material groups (Init) EM Consumptions by material groups (Delta) Data loading for InfoCube Data loading for InfoCube Master data loading Facility Hierarchy Nodes Default Hierarchy structure of the facility Legal hierarchy structure Location hierarchy structure Organization hierarchy structure Regional hierarchy structure Master data loading Master data loading Data load of all master data and hierarchies. Data loading for InfoCube Data loading for InfoCube Data loading for InfoCube Data loading for InfoCube Master data loading Master data loading Master data loading Master data loading Load all texts of the InfoObjects Loads all texts of InfoObjects which require configuration (hierarchies, UDF, ) Loads the master data and hierarchies of InfoObjects that need a configuration (UDF, Flex hierarchies) Emission data by material classifiers Emission data by material classifiers Emission data by material groups Emission data by material groups Consumptions by material classifiers Consumptions by material classifiers Consumptions by material groups Consumptions by material groups SAP SE or an SAP affiliate company. All rights reserved. Installation Information

41 EM Measurements by material groups (Init) EM Measurements by material groups (Delta) EM Measurements by material classifier (Init) EM Measurements by material classifier (Delta) EM Parameter Attribute EM Material Parameter Value EM Facility Parameter Value EM Limits Attribute EM Limit Report (Init) EM Limit Report (Delta) Measurements by material groups Measurements by material groups Measurements by material classifier Measurements by material classifier Parameter master data Material Parameter Value Facility Parameter Value Limit master data Limit Reports Limit Reports Select these options for installing: Grouping -> Only necessary objects Source System assignment -> xem Collection Mode -> Collect automatically Activate all process chains. Caution Do not install process chains starting with /TDAG/EEM_ if you do not use SAP Enterprise Energy Management. To activate the content, proceed as follows: 1. Select Item Object Types in the navigation pane of RSOR 2. Select Process Chains and select Objects 3. Sort the data in the popup by object name and select all items starting with /TDAG/ and transfer this selection 4. Mark all entries in right pane using the select all button 5. Select Install 6. This starts the activation of the selected objects 7. Check the status of the background task in SM37 Note Before loading data from EC, make sure that the InfoPackages are set to the correct update mode. Note that this setting of the InfoPackage is not always transported correctly. The update mode in the InfoPackage must match the InfoPackage s name, for example, /TDAG/EM_1_INIT must have update mode: Initialization of delta transfer. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 41

42 Checking Internet Graphics Service (IGS) Settings Use The Internet Graphics Service (IGS) enables you to create charts and graphics in EC Reporting. Prerequisites All installation steps must be finished. Procedure Check if the IGS installation runs on your system. Log in with the SAP NetWeaver Admin user at the following URL: Navigate to the Admin Menu Settings Web Dynpro Framework. In the Web Dynpro Properties Detail view, you can check if the IGS Server is connected. If the IGS is not connected, you have to go to NWA and set up the IGS URL as follows: 1. Log in to NWA with the SAP NetWeaver Admin user 2. Filter the application tc~wd~dispwda in the module list. 3. Select the module webdynpro/resources/sap.com/tc~wd~dispwda. 4. On the Tab Web Dynpro Properties in the Web Module Details, select the row Default. 5. In the dialog table below Full Details, you can now set up the IGSUrl. Note that this Service URL can also be on an external System Personalizing EC View Elements Use The Renaming Tool in EC 2.0 provides a function that enables the EC admin user to rename headers and labels of views and to hide elements of views. In EC 3.0, this function is replaced by the portal framework personalization function. Prerequisites You have completed all installation steps. Procedure For the complete description of how to personalize your Web Dynpro views based on roles, see the SAP Help Portal at The EC Portal content is located at Portal Content Content Provided by SAP Specialist Environmental Compliance 3.0 Pages SAP SE or an SAP affiliate company. All rights reserved. Installation Information

43 Importing ERP Transport for EHS Integration Use EHS Integration enables you to synchronize the Specifications in SAP EHS Management as part of SAP ERP (EHS) with Materials in Environmental Compliance. Prerequisites You have completed all installation steps. Procedure EHS Integration is an EPR program that enables you to synchronize the EHS Specifications with EC Materials. For this case an ERP Transport has to be imported in the ERP System. For importing an ERP (R3) transport, contact the ERP Administrator. For more information about how to use the EHS Integration, see the chapter Interfaces to SAP EHS Management as Part of SAP ERP Setting Up Scheduled Periodic Tasks Use The NWA Java Scheduler enables you to setup background tasks (jobs) such as limit checks or emissions. Prerequisites You have completed all installation steps. Procedure See the chapter Scheduled Periodic Tasks Configuring Object-Based Navigation Use Object-Based Navigation (OBN) allows you to open new windows in EC (for example, tasks from EC Dashboard) with the full WorkProtect mode and personalization features. OBN is already configured for EC standard delivered roles; however, further configuration is necessary for user-defined user portal roles. Prerequisites You have completed all installation steps. In addition, all new roles and worksets have to be defined and created on the EC portal system. Procedure EC Object-Based Navigation (OBN) pages are defined in the portal content area at Portal Content Content Provided by SAP specialist Environmental Compliance 3.0 pages obnpages. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 43

44 The following table shows all OBN Portal pages, where they are used (Portal Business Objects and their operations), and which EC Standard roles use these pages. OBN Page Name + (Description) Business Object Operation Used in EC standard roles Authority Permit Open Authority Compliance Analyst EHS Manager Energy Manager Environmental Analyst Read All BatchProcess Batch Process Open Recipe Environmental Analyst Read All Citation Permit Open Citation Compliance Analyst EHS Manager Energy Manager Environmental Analyst Read All Compliance Management Facility Open Compliance Management Compliance Analyst EHS Manager Energy Manager Environmental Analyst Read All Consumption Based Calculation Calculation Open Calculation View EHS Manager Energy Manager Environmental Analyst Read All Emission Accounting Emission Accounting Open Emission Accounting Emission Management Facility Open Emission Management Energy Manager Environmental Analyst Read All Energy Manager Environmental Analyst Read All Exception Detail (UI called from EC Dashboard or from Facility Details, Tasks, etc...) Exception Open Exception Compliance Analyst Corporate Program Manager EHS Manager Energy Manager Environmental Analyst Read All Site Manager Site Technician UWL Manager SAP SE or an SAP affiliate company. All rights reserved. Installation Information

45 Facility Detail Facility Open Facility Energy Manager Environmental Analyst Facility Compliance Operator Facility Compliance Responsible Read All IO Calculation Calculation Open IO Calculation EHS Manager Energy Manager Environmental Analyst Read All Limit Detail Permit Open Limit Compliance Analyst EHS Manager Energy Manager Environmental Analyst Read All Material Detail Material Open Material Energy Manager Environmental Analyst Read All New Calculation Calculation Open Calculation View Energy Manager Environmental Analyst Parameter Detail Parameter Open Parameter Compliance Analyst Energy Manager Environmental Analyst Read All Permit Permit Open Permit Compliance Analyst EHS Manager Energy Manager Environmental Analyst Facility Compliance Analyst Read All Recipe Step Template Batch Process Open Recipe Step Environmental Analyst Read All Report Reporting Open Report Query Compliance Analyst EHS Manager Energy Manager Environmental Analyst Environmental Compliance Admin Facility Compliance Responsible Read All Requirement Permit Open Requirement Compliance Analyst EHS Manager Energy Manager Environmental Analyst Facility Compliance Analyst Read All Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 45

46 Requirement Set Permit Open Requirement Set Compliance Analyst EHS Manager Energy Manager Environmental Analyst Facility Compliance Analyst Read All Task Editor (Opened from Notification See also SAP Note ) Task Open Task Instance with Access (Permissions) Compliance Analyst EHS Manager Energy Manager Environmental Analyst Facility Compliance Analyst Read All Site Manager UWL Manager Task Management - Status Editor (Opened from EC Dashboard) Task Open Task Instance Compliance Analyst Compliance Manager Corporate Program Manager EHS Manager Energy Manager Environmental Analyst Environmental Compliance Admin Facility Compliance Analyst Facility Compliance Operator Facility Compliance Responsible Read All Site Manager Site Technician UWL Manager Task Template Task Open Task Template Compliance Analyst EHS Manager Energy Manager Environmental Analyst Facility Compliance Analyst Read All Permit Manager Obsolete! Obsolete! When you are using custom portal roles, then you have to follow the following configuration steps to ensure that the OBN works correctly: SAP SE or an SAP affiliate company. All rights reserved. Installation Information

47 1. Add the OBN pages you need manually to your custom portal role as DELTA LINK and set the visibility setting to FALSE of every OBN page within the portal role (The OBN Pages have to be invisible in the role) 2. Add your portal role to the Business Objects as target selection (based on the OBN Pages in the table from previous pages) 3. Select in the Portal Business Object the newly added Role, search the related OBN Page and add the page as target to the Business Object Operation (see the correct operation for every Portal page in the table above). Save the changes Portal Business Object. Note The newly created roles and portal business object assignment changes can be transported between the different EC system landscapes via portal import / export function ( In the transport package, you have to add your portal roles, worksets, etc. then the EC standard roles, worksets, etc., and the EC Portal business objects. Installation Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 47

48 5 Security Information This chapter provides an overview of the security-relevant information that applies to SAP Environmental Compliance. 5.1 Application Security This chapter is intended to provide you with an overview of the security aspects and recommendations that apply to the application SAP Environment Compliance. It describes the configuration of the authentication of the application SAP Environmental Compliance (SAP EC) Role and Authorization Concept To limit access to an application, different security mechanisms are needed. SAP Environment Compliance has these mechanisms to ensure access for selected users only. EC uses the authorization concept provided by the SAP NetWeaver AS Java. Therefore, the recommendations and guidelines for authorizations as described in the SAP NetWeaver AS Security Guide Java also apply to the SAP Environment Compliance. SAP EC is a role-based application. This concept enables the administrator to define detailed access to the objects regarding the user s responsibilities in the company. For more information about NetWeaver Security Guides for the Operating System and Database Platforms for CE, see SAP Help Portal at Three Tier Authentication Concept Rights and permissions are needed to limit access to an application. The EC application works with rights and permissions. Every user must have rights to be able to read and to manipulate data in the EC application. The permission queries are executed in every module separately. The EC application is divided into three different authentication types: User Management Engine (UME) actions Portal roles EC Object-Based Authorizations (OBP) SAP SE or an SAP affiliate company. All rights reserved. Security Information

49 The following figure shows the interrelationship between the different permission types: Every EC user needs portal role permission. The portal role ensures the access to the defined user interface module. The role self has a link to the UME actions for basic access to the different EC Views. Every portal role has its own UME Group, which should be assigned to the EC Users. In addition, the Object-Based permissions are also assigned the UME Groups. The object based permissions controls the access to the special object with the different access types like VIEW, CHANGE, CREATE, DETELE, etc. EC is delivered with 14 different user groups, which are predefined for different EC Work processes and these user groups are already linked to the SAP EC standard portal roles and SAP EC standard object based permission profiles. For more information about the SAP EC standard roles, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under User Management Engine (UME) Actions The EC application is delivered with a lot of permission actions that define access to the different EC modules. Access actions enable you to access to the EC Module; however, there are further object-based authorizations that you need to have further permissions in the Module. The other permissions (Not Access) have full permissions for the related configuration objects. In the UME User administration view, you can find an overview of all EC Actions:! Action Log in to the user administration ( with an SAP NetWeaver administrator user Select Action as search criteria type and enter EC_* as search text The search result shows all available EC Actions Security Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 49

50 In the initial status, these actions are assigned to the delivered EC Portal Roles. These actions can be used in user-defined UME roles or EP Roles User Management Engine (UME) Groups The EC application is delivered with UME user groups. These sample groups should be assigned to the EC endusers. In the UME User administration view, you can find an overview of all EC user groups:! Action Log in to the user administration ( with an SAP NetWeaver administrator user Select Group as search criteria type and enter UMEGROUP_* as search text The search result shows all available EC User Groups Enterprise Portal Roles The portal permission is granted by roles. A security role represents an abstract logical group of users that is defined for specific application components. The table below gives an overview of the defined portal standard roles delivered with the application: Role Corporate Program Manager Compliance Manager EHS Manager Compliance Analyst Environmental Analyst Site Manager Site Technician Environmental Compliance Admin Facility Compliance Operator Activities KPIs for Company and EC Dashboard KPIs for Site and Dashboard View KPIs for Site, EC Dashboard, EC Compliance Management (Compliance, Permit, Task, Reporting, Exception) View KPIs for Site, EC Dashboard, EC Compliance Management, EC Master Data (Facilities, Materials) View KPIs for Site, EC Dashboard, EC Compliance Management, EC Emissions Management, EC Master Data View KPIs for Site, EC Dashboard EC Dashboard Access to the main Configuration, Administration, Maintenance and Tools menu Special EC User, refer to the Functional Guide SAP SE or an SAP affiliate company. All rights reserved. Security Information

51 Facility Compliance Analyst Facility Compliance Responsible Energy Manager Read All UWL Manager Special EC User, refer to the Functional Guide Special EC User, refer to the Functional Guide Special EC User, refer to the Functional Guide Role has read permission for all EC Modules except the configuration Special User to use the EC UWL actions and the EC Dashboard features. The delivered portal permissions contain the UME action permissions. For more information about roles, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under EC Object-Based Authorizations Object-Based Authorizations (OBP) provide a fine granular authorization and access control concept that is based on the different Business Objects (BO) of Environmental Compliance. For BOs, customers can define authorizations that fulfill specific criteria. These authorizations are grantable to a specific user, group, or role. For example, change permission for all Facilities that have the classifier Stuttgart assigned can be granted to the users of the group Data Entry Users Stuttgart. For more information about object-based authorizations, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under Network and Communication Security Your network infrastructure is extremely important for protecting your system. Your network needs to support communication for your business needs without allowing unauthorized access. A well-defined network topology can eliminate many security threats that exploit software flaws (at both the operating system level and application level) or network attacks such as eavesdropping. If users cannot log on to your application or database servers at the operating system or database layer, there is no way for intruders to compromise the machines and gain access to the database or files of your backend system. Additionally, if users are not able to connect to the server LAN (local area network), they cannot exploit well-known bugs and security holes in network services on the server machines. The network topology for SAP Environmental Compliance is based on the topology used by the SAP NetWeaver platform. Therefore, the security guidelines and recommendations described in the SAP NetWeaver Security Guide also apply to SAP Environmental Compliance. Details that apply specifically to SAP EHS Regulatory Documentation OnDemand are described in the following topics: Security Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 51

52 For more information about communication channel security, see on SAP Help Portal at Security Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guide for Usage Type AS SAP NetWeaver Application Server Java Security Guide Network Security Communication Channel Security. 5.2 Data Protection Introduction Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with general data privacy acts, it is necessary to consider compliance with industry-specific legislation in different countries. SAP provides specific features and functions to support compliance with the relevant legal requirements and data privacy. SAP does not give any advice on whether these features and functions are the best method to support company, industry, regional or country-specific requirements. Furthermore, this information does not give any advice or recommendations with regard to additional features that would be required in a particular environment; decisions related to data protection must be made on a case-by-case basis and under consideration of the given system landscape and the applicable legal requirements. Note In the majority of cases, compliance with data privacy laws is not a product feature. SAP software supports data privacy by providing security features and specific data-protection-relevant functions such as functions for simplified blocking and deletion of personal data. SAP does not provide legal advice in any form. The definitions and other terms used in this guide are not taken from any given legal source Glossary Term Definition Blocking Business purpose A method of restricting access to data for which the primary business purpose has ended. A legal, contractual, or in other form justified reason for the processing of personal data. The assumption is that any purpose has an end that is usually already defined when the purpose starts SAP SE or an SAP affiliate company. All rights reserved. Security Information

53 Term Definition Consent Deletion End of purpose (EoP) Personal data Purpose Residence period Retention period Sensitive personal data The action of the data subject confirming that the usage of his or her personal data shall be allowed for a given purpose. A consent functionality allows the storage of a consent record in relation to a specific purpose and shows if a data subject has granted, withdrawn, or denied consent. The irreversible destruction of personal data. A method of identifying the point in time for a data set when the processing of personal data is no longer required for the primary business purpose. After the EoP has been reached, the data is blocked and can only be accessed by users with special authorization (for example, tax auditors). Any information relating to an identified or identifiable natural person ("data subject"). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person. A legal, contractual, or in other form justified reason for the processing of personal data. The assumption is that any purpose has an end that is usually already defined when the purpose starts. The period of time between the end of business and the end of purpose (EoP) for a data set during which the data remains in the database and can be used in case of subsequent processes related to the original purpose. At the end of the longest configured residence period, the data is blocked or deleted. The residence period is part of the overall retention period. The period of time between the end of the last business activity involving a specific object (for example, a business partner) and the deletion of the corresponding data, subject to applicable laws. The retention period is a combination of the residence period and the blocking period. A category of personal data that usually includes the following type of information: Special categories of personal data, such as data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data, data concerning health or sex life or sexual orientation, or personal data concerning bank and credit accounts. Personal data subject to professional secrecy Personal data subject to professional secrecy Personal data concerning insurances and bank or credit card accounts Security Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 53

54 Term Definition Where-used check (WUC) A process designed to ensure data integrity in the case of potential blocking of business partner data. An application's where-used check (WUC) determines if there is any dependent data for a certain business partner in the database. If dependent data exists, this means the data is still required for business activities. Therefore, the blocking of business partners referenced in the data is prevented User Consent Due to the data protection and privacy regulations, data subjects (natural persons such as customers, contact, or account) need to give consent to processing their personal data. As part of the contract between SAP and the customer, the user of SAP Environmental Compliance consents to the collection and use of information as described in the contract. The user of SAP Environmental Compliance can insert personal data of data subjects in the application. Since there is no contract between SAP and these data subjects about processing their personal data, it is the user's responsibility to ask for consent to process their personal data Read Access Logging Since handling of data that are categorized as sensitive by law, by external company policy, or by internal company policy is critical, all successful and unsuccessful attempts to access this data needs to be logged. Currently no sensitive personal data is used and stored within SAP Environmental Compliance. Therefore, read access logging is not required. However, the application logs changes in specific fields. For more information, see chapter Change Log Information Report Applications that store personal data need to provide functions to report or display personal data about a data subject (natural persons such as customers, contact, or account). In SAP Environmental Compliance, a user with authorization to use the Reporting function can create reports to view all task templates and exceptions that contain a specific address. The data sources Task Template E- Mail Address and Exception Address can be used to generate reporting variants and Excel or PDF reports. Note that these reports contain personal data. You need to configure the authorization concept to be compliant with data protection regulations. To import the data sources into the SAP Environmental Compliance system, start data migration Delta Data Migration under Administration - > Data Migration SAP SE or an SAP affiliate company. All rights reserved. Security Information

55 In addition, an administrator with the SAP Environmental Compliance Admin role can use the contact management to search for a user to view the user`s personal data. The administrator can inform a user about which personal data is stored for the user in SAP Environmental Compliance Deletion of Personal Data When handling personal data, it is necessary to comply with general data protection regulation and industryspecific legislation in different countries. A typical requirement in certain countries and regulations is that personal data shall no longer be handled after the specified, explicit, and legitimate purpose for the processing of personal data has ended. Data that reached their end of purpose (EoP) must be deleted if no other retention periods are defined in legislation, for example, retention periods for occupational health documents. If there are legal requirements to retain personal data after the end of purpose, this data needs to be blocked. Blocked data is retained in the database due to the legally defined retention periods and can be displayed only by persons with special authorizations. SAP Environmental Compliance provide the functions described in the following sections to support you to comply with general data protection regulation Anonymizing Data in Task Templates In the user data for a task template under Compliance Management -> Task Management, the address of an interested person can be added as additional information. This address will be anonymized by the background jobsap_environmental_compliance-task maskjob. For templates in status Deactivated, the report replaces the address with asterisks (*) in the corresponding database field if the retention period specified in the field Retention_of_ _Address is reached. The additional information field is also used in SAP Environmental Compliance reporting in data sources of type SQL or in business objects. If you generate a report after the address is anonymized, the report contains the anonymized data. Note that data in change documents is not changed. You have to delete change documents manually from the database tablesem_change_doc andem_cdoc_trans after the purpose of processing this data has ended. For more information about deleting change documents, see SAP Note Anonymizing Data in Exceptions In the communication for exceptions under Compliance Management -> Exception Management, an address can be added as authority contact. This address will be anonymized by the background job SAP_Environmental_Compliance-Exception MaskJob. For exceptions in status Completed, the report replaces the address with asterisks (*) in the corresponding database field if the retention period specified in the field Retention_of_ _Address is reached. Security Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 55

56 Note that data in change documents is not changed. You have to delete change documents manually from the database tablesem_change_doc andem_cdoc_trans after the purpose of processing this data has ended. For more information about deleting change documents, see SAP Note Removing Addresses in Alert Logs In the configuration of alert logs under Configuration -> Compliance Management -> Alert Logs Configuration, the address for the notification recipient is displayed. Since it is not needed to display the address, you can remove this field from the alert log configuration by starting the data migration Delete Addresses in Alert Log Configuration under Administration -> Data Migration Deleting Personal Data of External Contacts In SAP Environmental Compliance, you can enter data of external contacts, which no user in the user administration. You can assign this contact information to facilities, permits, and authorities. If you have entered personal data of external contact persons into the SAP Environmental Compliance system, you are responsible to be compliant with applicable data protection and privacy laws and to delete the data after the purpose of processing this data has ended. To delete the data of external contacts, proceed as follows: 4. Go to Tools -> Contact Management and search for the contact you want to delete. Note that you need the SAP Environmental Compliance Admin role to use the contact management tool. 5. In the search results list, you can view if the contact is assigned to a facility, permit, or authority. If a contact is assigned, delete first the assignment manually by navigating to the assigned objects and delete the assignment there. 6. If all assignments have been removed, you can delete the contact in the search results list. After you deleted the contact data in the contact management, run the jobsap_environmental_compliance- PhysicallyDeletionDataJob to destroy the data by deleting it from the database Deleting Personal Data in Facilities and Authority In SAP Environmental Compliance, you can enter address information for facilities and authority. In the address data, you can add an address. This address should be used only for general data (for example admin@authority.com) and should not contain any personal data. If you have entered personal data for facilities and authority into the SAP Environmental Compliance system, you are responsible to comply with applicable data protection and privacy laws and to delete the data after the purpose of processing this data has ended SAP SE or an SAP affiliate company. All rights reserved. Security Information

57 5.2.7 Change Log Personal data may be subject to changes. If these changes are logged, it is possible to check which employee made which change and when. SAP Environmental Compliance writes change documents for changes in specific fields. For more information, see section Change Documents in the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under Security Information 2017 SAP SE or an SAP affiliate company. All rights reserved. 57

58 6 6.1 Monitoring Tools Within the management of SAP technology, monitoring is an essential task. A section has therefore been devoted solely to this subject. You can find more information about the underlying technology in the SAP NetWeaver Administrator s Guide -> Technical Operations Manual on the SAP Help Portal at Alert Monitoring with CCMS Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure and recommendations needed to set up your alert monitoring to recognize critical situations for SAP Environmental Compliance as quickly as possible. You can use the Log-file Monitoring monitors to search any log files for the occurrence of text patterns of your choice. This is done using a CCMS agent that takes the required information about which text pattern it should search for in which files from one or more configuration files. For detailed information about monitoring, see the SAP Help Portal at CCMS Monitoring Installation and Setup If you want to monitor SAP NetWeaver Composition Environment (CE) centrally, you must use a central monitoring system with release SAP NetWeaver 7.0. For information about how to set up the CCMS agent, see SAP Help Portal at under SAP NetWeaver SAP NetWeaver CE SAP NetWeaver Composition Environment Library. Use the search pattern technidata.ec. To monitor the general availability of all components of SAP Environmental Compliance in a CCMS System, create a GRMG Lite scenario for each component (see chapter Component Specific Monitoring). For detailed information about GRMG Lite, see For more information about monitoring SAP NetWeaver, see To enable the auto-alert mechanism of CCMS, see SAP Note SAP SE or an SAP affiliate company. All rights reserved.

59 6.1.3 Component Specific Monitoring To monitor the general availability of all components, the SAP Environmental Compliance in a CCMS System creates a GRMG Lite scenario for the following URLs: EC Central Services (TDAG_ECS_SERVICES) EC Central Modules (TDAG_ECS_MODULES) T EC Application Modules (TDAG_XEM_MODULES) ent EC Reporting Content (TDAG_XEM_REP_CONTENT) Detailed Monitoring and Tools for Problem and Performance Analysis The technology of SAP Environmental Compliance is based on SAP NetWeaver 2004s Application Server. For information about technical problem analysis (such as with a database, the operating system, or workload analysis), see the Solution Operation Guide for Web Application Server. For more information about monitoring the SAP Web Application Server, SAP Enterprise Portal and SAP NetWeaver in general, see the Operation Guides for SAP NetWeaver 7.0 (2004) at For more information about network load and memory size, see the EC Sizing Guide at Trace and Log Files Trace files and log files are essential for analyzing problems. SAP Environmental Compliance uses the standard SAP NetWeaver logging infrastructure and, therefore, SAP NetWeaver Administrator. For detailed information about error messages saved in the log files, go to Problem Management Logs and Traces Log Viewer (Quicklink Alias: /nwa/logs). For detailed information about monitoring and displaying log files, see the following URL: SAP SE or an SAP affiliate company. All rights reserved. 59

60 Note We recommend that you check the log files periodically. Important the following log and trace files for SAP Environmental Compliance: Component TDAG_ECS_SERVICES TDAG_ECS_MODULES TDAG_XEM_MODULES TDAG_XEM_REP_CONTENT Content Trace Messages of Central Services Trace Messages of Central Modules Trace Messages of Application Modules Trace Messages of Reporting Content The components TDAG_ECS_SERVICES, TDAG_ECS_MODULES, TDAG_XEM_MODULES and TDAG_XEM_REP_CONTENT of SAP Environmental Compliance trace to the following locations, dependent on the application area and the technical home of the source class: de.technidata com.technidata By default, all trace locations are configured for severity level ERROR. Refer to SAP standard documentation for detailed instructions on how to control the level of trace messages for specific trace locations. The logging level is controlled by SAP NetWeaver. To view the log files, use the standard SAP NetWeaver logging utilities. In addition, to the system categories, the logs for SAP Environmental Compliance are written to the application specific base category /Applications/TDAG. The subcategories, dependent on the application area, are: The following log categories are available for component TDAG_ECS_SERVICES: EC Archive Service Basic Objects ECS Basic Service TimeStamp Calculation Service Cross-Reference Service DataMigration Deprecated Objects Document management service Notifications Service Scheduler Detector Scheduler Manager Hierarchy Service Identification service SAP SE or an SAP affiliate company. All rights reserved.

61 IGSWrapper ImportExport Service Inspection framework Integrated Systems Logging Viewer LOV Multilingual Deprecated Service Multilingual Service Parameters Permission Service Persistency Change Doc Transfer RFC Service Startup EC Properties UDF Service Unit and Dimension Service User Service UserExit Service User Profile Service UserReassignment User Substitution Service The following log categories are available for component TDAG_ECS_MODULES ECS Facility Builder ECS Facility Builder UserExit Menu Frame Reporting The following log categories are available for component TDAG_XEM_MODULES Accounting EC Archive Modules Batch Calculation Batch Process Calculation Scheduler Calculation Mgmt Module Contacts Service Data Entry Variances Module Data Release EEM-Package FacCompl Helper Validity Profile 2017 SAP SE or an SAP affiliate company. All rights reserved. 61

62 XEM Facility Builder Calculations IntegrationManager Integrated Tags Management Integrated Tags Management MaterialManagement MultiValueSelector PermitManagement Limit Scheduler Status Network Service Task- and Exception Management Service Checklist Task Poll EAM Task Synchronization Task Status Job Exception Custom Task Type UserExit Data Import The following log category is available for component TDAG_XEM_REP_CONTENT EC Reporting Content: Facility Emissions Datasource By default, these log categories are configured for severity level INFO Interface Monitors Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP. Interface Detailed Description Technology used RFC Monitor The RFC Monitor gives an overview about the communication between the EC 3.0 and the ERP system. The RFC Monitor works when a RFC Connection is set up in EC. To access the RFC Monitor: Log in to the portal ( with a user that is assigned to the User Group UMEGROUP_Environmental Compliance Admin. Navigate to Plant Compliance Administration RFC Server Monitor By selecting the Logging Message Type in the drop-down box, the system displays the current Log entries. RFC SAP SE or an SAP affiliate company. All rights reserved.

63 Web Services Scheduled Jobs Archiving Monitor For more information about web services logging & tracing see the SAP Help Portal at 9b1b2341d8e a1553f7/frameset.htm Log in to the NWA ( with SAP NetWeaver CE admin user. For more information about the java scheduler, see the SAP Help Portal at ee10b3e a11466f/frameset.htm Log in to the NWA ( with SAP NetWeaver CE admin user. See chapter 6.3 Data Growth and Data ArchivingError! Reference source not found.. Web Service Java Scheduler Java Scheduler and Archiving Cockpit 6.3 Data Growth and Data Archiving This chapter describes how to archive transactional data within. In addition, it describes the searching of archived data of the different business objects. Working with Environmental Compliance (EC) over a long period of time creates a lot of transactional data in database tables. This could lead to performance problems in the reporting process when database tables contain huge amount of entries (> 1 million). For this case, the transactional database tables of Environmental Compliance can use a final archiving method of the life data. The EC Admin should be aware that the archived data cannot be returned into the EC database tables after they were archived. There are two ways to archive the SAP EC Data 1. Using a shadow database table and copy a range of data from EC standard tables. Refer to SAP Note for further details (Recommended Way to archive the SAP EC Data) 2. Using SAP NetWeaver Archiving Tool. The following chapters describe the SAP NetWeaver Archiving Tool. SAP NetWeaver Archiving Tool The archiving process in SAP NetWeaver Archiving Tool is implemented using XML-based archiving, which is part of the JAVA NetWeaver CE landscape. The following Environmental Compliance business objects are supported for archiving: 1. Consumptions 2. Measurements 3. Emissions 4. Exceptions 5. Task Instances 6. Change Documents 2017 SAP SE or an SAP affiliate company. All rights reserved. 63

64 Note The following prerequisites must be satisfied before it is possible to run the archiving process with SAP NetWeaver archiving tool: o is set up correctly. o Archiving Store is set up for every archive set object Basic Configuration The whole archiving process documentation is located on the SAP Help Portal at The home path synchronization assigns the archiving stores with the archiving sets: The following EC archiving sets have to be synchronized in Synchronize Home Paths menu, with defined archiving stores: /<SYSID>/sap_ec_archiving_changedocs/ /<SYSID>/sap_ec_archiving_consumptions/ /<SYSID>/sap_ec_archiving_emissions/ /<SYSID>/sap_ec_archiving_exceptions/ /<SYSID>/sap_ec_archiving_measurements/ /<SYSID>/sap_ec_archiving_tasks/ For more information about assigning an archiving store to a set see the SAP Help Portal (Administration of the XML Data Archiving Service) at Archiving The archiving process contains the steps that are needed for the archiving of EC transactional data. The archiving process can only be done by a SAP NetWeaver WEB Application Administrator user because the archive store views are not part of Environmental Compliance. The archiving store is part of the NetWeaver Administration Service (NWA), which can be reached with the URL In the Menu XML Data Archiving Service Administration (XML DAS Administration), you can set up the basic configuration and in the menu Java Archiving Cockpit you can start the write and delete archive process Before you can start with the archiving process, you need to create path extensions of the different archiving sets: 1. Navigate to the Java Archiving Cockpit and select the Hierarchy Tab. 2. Select one of the EC archiving sets (Example: sap_ec_archiving_emissions). 3. Create collections (the name of the collection is the path extension). 4. Navigate to the XML DAS Administration and select the tab Archive Hierarchy & Store Assignment SAP SE or an SAP affiliate company. All rights reserved.

65 5. Select your collections and assign them to an Archive Store (on the right side in the Archive Path Properties view). 6. Now the Path extension can be used in the Archiving View and in the EC Archive Search Write Archives In the Write view, the user can centrally schedule the write sessions for any archiving set that supports this function. During a write session, data is written from the database to a collection in the form of resources the first phase of an archiving session. After the write phase, the archiving session appears with the status incomplete in the archive hierarchy. The second phase of an archiving session is the delete phase, which is described in chapter Delete Archives. The Write view is built up in three different areas: 1. Selection Criteria: Every EC Archive Set has own selection criteria s (See next chapters). 2. Schedule Settings: The Schedule settings are similar for every EC Archiving Set and have following properties. o Start now: Start date for the archiving process o Start at Date / Time: Definition for set up a scheduled archiving run o Start Delete Phase Automatically: This enables running the archiving and deletes process in one step. For more information see the SAP Help 3. Technical Settings: The technical settings are similar for every EC Archiving Set and have the following properties: o XML Parsing: check if the created XML is well-formed. o Simulation: this flag should be used for testing, e.g. how many rows a run have o Path Extension: displays the Archiving path extension of a collection, which can be set up in the Java Archiving Cockpit hierarchy o Comment: Comment of the archiving run For more information about writing archives see the SAP Help Portal (for Java Archiving Cockpit at SAP SE or an SAP affiliate company. All rights reserved. 65

66 Archiving Measurements with sap_ec_archiving_measurements The archive set sap_ec_archiving_measurements archives measurement values of facilities for a given date period. The entire search result is archived. The facility ID and the date period are required input fields. The following search criteria for archiving are available: Field Name (* required) Facility ID * Include Subordinate Hierarchy Elements Show Data from* To * Include Scenarios Purge logical deleted data before archiving Description Enter the Facility technical ID. The Facility technical ID can be read in the Facility detail view selecting the Technical Information pop-up. Flag: All measurements of the subordinate facilities are also archived. Defines the period start of the measurement data, e.g. 1st January Defines the period end of the measurement data, e.g. 31st December Flag: All measurements within scenarios are also archived. Flag: Before the archiving process begins, the system deletes physically all logical deleted measurements in the database Archiving Emissions with sap_ec_archiving_emissions The archive set sap_ec_archiving_emissions archives emission values of facilities for a given date period. In addition, the archiving process archives the related calculation logs. The entire search result is archived. The facility ID and the date period are required input fields: The following search criteria for archiving are available: Field Name (* required) Facility ID * Include Subordinate Hierarchy Elements Description Enter the facility technical ID. The facility technical ID can be read in the facility detail view selecting the technical information pop-up. Flag: All emissions of the subordinate facilities are also archived. Show Data from* Defines the period begin of the emissions data, e.g. 1st January To * Include Scenarios Purge logical deleted data before archiving Defines the period end of the emissions data, e.g. 31st December Flag: All emissions within scenarios are archived. Flag: Before the archiving process begins, the system deletes physically all logical deleted emissions in the database SAP SE or an SAP affiliate company. All rights reserved.

67 Archiving Consumptions with sap_ec_archiving_consumptions The archive set sap_ec_archiving_consumptions archives consumption values of facilities for a given date period. In addition, the archiving process archives the related consumption parameter values and the calculation logs. The entire search result is archived. The facility ID and the date period are required input fields. The following search criteria for archiving are available: Field Name (* required) Facility ID * Include Subordinate Hierarchy Elements Description Enter the Facility technical ID. The Facility technical ID can be read in the Facility detail view selecting the Technical Information pop-up. Flag: All consumptions of the subordinate facilities are also archived. Show Data from* Defines the period start of the consumptions data, e.g. 1st January 2008 To * Defines the period end of the consumptions data, e.g. 31st December 2008 Include Scenarios Purge logical deleted data before archiving Archive consumption parameters and calculations Flag: All consumptions within scenarios are archived. Flag: Before the archiving process begins, the system deletes physically all logical deleted consumptions in the database. When this flag is set, then the archiving process will also archive the related Parameters and emission calculations. Note that this parameter shall be not used for EEM data Archiving Tasks with sap_ec_archiving_tasks The archive set sap_ec_archiving_tasks archives task instance values of a date period. In addition, the archiving process archives the related task properties. The following table shows which related data is archived together with the task depending on the task type: Name Calculation Logs Task Users Cross-table Facilities Cross-table Requirements Cross Table Documents EAM User Defined Fields data Check List Description All task types All task types All task types All task types All task types EAM Task All task types Checklist task 2017 SAP SE or an SAP affiliate company. All rights reserved. 67

68 Batch Production series Emissions Consumptions Measurement Batch Task Emission Task Consumption Task Measurement Task Note For more information about the different EC Task types, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under The entire search result is archived. The date From and the date To input fields are required search criteria. The following search criteria for archiving are available: Field Name (* required) Facility ID Include Subordinate Hierarchy Elements From (Due Date): * To (Due Date): * Purge logical deleted data before archiving Completion Status Type Description Enter the Facility technical ID. The Facility technical ID can be read in the Facility detail view selecting the Technical Information popup Flag: All Task Instances of the subordinate facilities are also archived. Defines the period start of the Task Instance Due Date, e.g. 1st January 2008 Defines the period end of the Task Instance Due Date, e.g. 31st December 2008 Flag: Before the archiving process starts, the system deletes physically all logical deleted task instances in the EC database. Task Status: New, In Process, Completed, Canceled, To Approve. You can use the following LOV keys as search criteria: TSK_STAT_NEW TSK_STAT_PROCESS TSK_STAT_TO_APPROVE TSK_STAT_COMPLETED TSK_STAT_CANCELED Type of Task: Standard, Measurement Task, TSK_TYPE_DEFAULT TSK_TYPE_CONSUMPTION TSK_TYPE_MEASURING TSK_TYPE_EMISSION TSK_TYPE_EAM TSK_TYPE_EAM_ORDER Standard Task Consumption Task Measurement Task Emission Task EAM Notification Task EAM Order Task SAP SE or an SAP affiliate company. All rights reserved.

69 TSK_TYPE_PRODUCTION_SERIES TSK_TYPE_CHECKLISTXEM Production Series Task Standard Checklist Task Archiving Exceptions with sap_ec_archiving_exceptions The archive set sap_ec_archiving_exceptions archives exception values of a given date period. In addition, the archiving process archives the related EC exception properties. The following table shows which related data is archived together with the exception: Name Calculation Logs Exception Assignees Cross-table Facilities Cross-table Requirements Cross table Documents Cross-table Citations Identifiers User Defined Fields data Communication The date From and date To input fields are required search criteria. The entire search result is archived. The following search criteria for archiving are available: Field Name(*required) Facility ID Include Subordinate Hierarchy Elements Description Enter the Facility technical ID. The Facility technical ID can be read in the Facility detail view selecting the Technical Information pop-up Flag: All EC exceptions of the subordinate facilities are archived. Start Date * Defines the period begin of the exception data, e.g. 1st January 2008 (based on the EC Exception begin date) To * Defines the period end of the exception data, e.g. 31st December 2008 (based on the EC Exception begin date) 2017 SAP SE or an SAP affiliate company. All rights reserved. 69

70 Status Status such as New, In Process, Completed. Following integer values could be used as search criteria: 0 New 1 In Process 2 Completed Archiving Change Cocuments with sap_ec_archiving_changedocs The archive set sap_ec_archiving_changedocs archives change document values of a date period. The date From and date To input fields are required as search criteria. The following search criteria for archiving are available: Field Name (*required) From * To * Description Defines the period begin of the change document data, e.g. 1st January 2008 Defines the period end of the change document data, e.g.: 31st December Delete Archives In the Delete view, you can centrally schedule the delete sessions for any archiving set that supports this function. During a delete session, the data that was previously written from the database to a collection in the form of resources during the write phase, is now deleted from the database the second step of an archiving session. After the delete phase, the archiving session appears with the status completed in the archive hierarchy. The deleting process is not needed when the option Start delete Phase Automatically in the schedule settings of the Write Archive View is selected. Note For more information about deleting archives see the Java Archiving Cockpit documentation on the SAP Help Portal at SAP SE or an SAP affiliate company. All rights reserved.

71 6.3.5 Monitor Archives The archive monitor displays an overview table with all archive runs. In the detail log pop-up, the admin user sees all actions that were done in the selected archive set. The following picture describes the possible states of an archiving set: State Running Scheduled Description The archiving is still running. The archive is planned for a later date. Failed The archiving process is failed check the Log details (Log column in Archiving Monitor) for more information. Incomplete The archiving process is incomplete check the Log details (Log column in Archiving Monitor) for more information SAP SE or an SAP affiliate company. All rights reserved. 71

72 Completed The archiving process is completed. The write and delete process has been completed successfully. For more information about deleting archives see the Java Archiving Cockpit documentation on the SAP Help Portal at Search Archives Depending on the archive set type, the user can search archived data. The search hit list is displayed in EC system in the affected modules. The following chapters describe where the user can search archived data based on the archiving set. The following different search dialogs are available: Emissions, Consumptions, and Measurements Tasks Exceptions Change Documents Emissions, Consumptions, and Measurements The search dialog for emissions, consumptions, and measurements is in the Emissions Management module Authentication and Access Searching archived transactional data of type Emissions, Consumptions, and Measurements can be done by users that have the following permissions: UME Access Permission for Emission Manager UME ArchiveSearch Permission for Emission Manager Portal permission for Emission Manager Note Environmental Compliance 3.0 is not delivered with permissions for searching archived emissions, consumptions, and measurements. The EC Admin has to create new role and assigned the upper named actions and permissions. The EC user needs the UME Action "EC_EmissionManagerArchiveSearch" SAP SE or an SAP affiliate company. All rights reserved.

73 Search Criteria Archived consumptions, measurements, and emissions can be searched and displayed in the Archived Transactional Data (known as Data Diagnostics) in the EC component Emission Manager with facility, path extension and period (From/To) search criteria as required fields. Note The archived data cannot be changed Tasks The search dialog for task instances is in the Task Management module Authentication and Access Searching archived transactional data of type Task Instances can be done by users that have the following permissions: UME Access Permission for Task Manager UME ArchiveSearch Permission for Task Manager Portal permission for Compliance Manager Note Environmental Compliance 3.0 is not delivered with permissions for searching archived task instances. The EC Admin has to create new roles and assign the actions and permissions named above. The EC user needs the UME Action EC_TaskArchiveSearch" Search Criteria Archived tasks can be searched in the Task Manager Activity with the following search criteria: Name (* required field) Type Priority Due Date* Completion Status Description Type such as Standard Task, Consumption Task High, Low, etc. Due date of the task Status of the Task; New, Completed, etc SAP SE or an SAP affiliate company. All rights reserved. 73

74 Parent Template Path Extension* Task Template (ID) The Path of the Archiving Store The archived tasks result list is displayed in the tasks hit list. Note The archived tasks details cannot be changed Exceptions The search dialog for exceptions is in the Exception Manager module Authentication and Access Searching archived transactional data of type Exception can be done by users that have the following permissions: UME Access Permission for Exception Manager UME ArchiveSearch Permission for Exception Manager Portal permission for Compliance Manager Note Environmental Compliance 3.0 is not delivered with permissions for searching archived task instances. The EC Admin has to create new role and assign the actions and permissions named above. The EC user needs the UME Action EC_ExceptionManagerArchiveSearch" Search Criteria Archived exceptions can be searched in the Exception Manager activity with the following search criteria: Name (* required field) Type Assessment Status Start Date* Path Extension* Description LOV: Type such as Fire, Oil Spill, etc. Special type such as Deviation Status such as New, Completed Start Date period The path of the Archiving Store SAP SE or an SAP affiliate company. All rights reserved.

75 The archived exceptions result list is displayed in the exception hit list. Note The archived exception details cannot be changed Change Documents The search dialog for change documents is located in the Maintenance module Authentication and Access Searching archived transactional data of type Change Documents can be done by users that have following permissions: UME Menu Permission for ArchivedChangeDocument Portal permission for Environmental Compliance Admin Note The EC user needs the UME Action EC_ChangeDocumentArchives" Search Criteria Archived change documents can be searched in the Maintenance Archived Change Document with following search criteria: Name (* Required) Domain Date/Time of Change From* Date/Time of Change To* User Path Extension* Description List of available Modules: Facility, Exception, etc. Time Frame From Time Frame To User name in the system fields The Path of the Archiving Store The archived change documents are displayed in the change document hit-list SAP SE or an SAP affiliate company. All rights reserved. 75

76 6.4 Management Tools SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively manage all SAP components and complete all tasks related to technical administration and operation. You can find more information about underlying technology in the Technical Operations Manual of SAP NetWeaver CE on the SAP Help Portal at Start and Stop Tools The following start and stop sequences and tools are available: Software Component Detailed Description SAP NetWeaver CE Server Note: For more information see the SAP Help d6e a114a6b/frameset.htm RFC Server For more information, see the chapter Interfaces to SAP EHS Management as Part of SAP ERP Software Configuration This chapter explains which components or scenarios used by this application are configurable and which tools are available for adjusting Application Configuration The EC application configuration enables you to set up and administrate EC relevant data. The EC configuration is represented by the following menu structures, which are in the Portal menu: Configuration Administration Maintenance Tools This menu structure is available in the EC Portal for users with admin permissions (User within the user group UMEGROUP_Environmental Compliance Admin ) SAP SE or an SAP affiliate company. All rights reserved.

77 For more information, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under Technical Configuration The technical configuration enables you to set up basic SAP NetWeaver CE settings with the Configuration tool (Config Tool). More information about SAP NetWeaver CE Config Tool refer to the SAP Help Portal at The following component configuration tools are available: Component Configuration Tool Detailed Description Config Tool Set up Configuration Refer to the chapter Setting up Configuration for more information Config Tool Check the Internet Graphics Service (IGS) settings Refer to the chapter Checking Internet Graphics Service (IGS) Settings for more information Backup and Restore All application data is stored in a database system that is linked to the SAP NW CE. The application data includes the configuration data of EC 3.0. To backup and restore your SAP NetWeaver CE system, use the backup and restore mechanisms of the database that you use. To configure Archiving of Log and Trace files, see the SAP Help Portal at For more information about the administration of SAP NetWeaver CE, see the Administration Guide of SAP NetWeaver CE on the SAP Help Portal at Application Copy For more information about the homogeneous and heterogeneous system copy for SAP systems based on SAP NetWeaver CE, see 2b10-a795-d25997cf SAP SE or an SAP affiliate company. All rights reserved. 77

78 6.4.5 Periodic Tasks Scheduled Periodic Tasks The Java Scheduler provides all necessary EC scheduled jobs. Log in to the NWA ( with an administrator user. The following Java periodic tasks are available: Program Name/Task SAP_Environmental_Compliance- CalculationSchedulerJob SAP_Environmental_Compliance- LimitCheckJob SAP_Environmental_Compliance- ExceptionGenerationJob SAP_Environmental_Compliance- TaskSchedulerForEAMObjectsJob SAP_Environmental_Compliance- ChecklistTaskSchedulerJob SAP_Environmental_Compliance- BatchProcessCalculationJob SAP_Environmental_Compliance- AlertDetectorJob Recommended Frequency (Cron) 0 30 * * *? Every Hour at 30 Minutes 0 40 * * *? Every Hour at 40 Minutes 0 0 * * *? Every Hour 0 15 * * *? Every Hour at 15 Minutes 0 10 * * *? Every Hour at 10 Minutes 0 5 * * *? Every Hour at 5 Minutes 0 0/10 * * *? Every Ten Minutes Detailed Description The Calculation scheduler job calculates all consumptions that have not been calculated yet. The Limit Check scheduler job checks all newly created or changed consumptions, emissions and measurements. The system scans all new overdue tasks and creates an exception for all tasks that are flagged with the setting Exception when overdue for a specified exception type. The EAM notification background job scans all open EC EAM Tasks. The open EAM Tasks are compared to the corresponding ERP PM Notifications. If one of the PM notifications status is different than the EC EAM Task Status, then the system synchronizes the Status of the EC EAM Tasks This job checks SMTP mailbox if with attached checklist is available. If with checklist is there, checklistfile is opened, values are extracted and imported to EC as checklist values This job calculates batch emissions based on production runs or production series. The Alert Detector job scans for outstanding s and generates the from the template SAP SE or an SAP affiliate company. All rights reserved.

79 SAP_Environmental_Compliance- AlertManagerJob SAP_Environmental_Compliance- ChangeDocumentJob SAP_Environmental_Compliance- AutomaticReportGenerationJob SAP_Environmental_Compliance- RCP-Check_for_Notification SAP_Environmental_Compliance- RCP-Check_for_Update SAP_Environmental_Compliance- RCP-SynchronizeData SAP_Environmental_Compliance- AlertLogsJob 0 5/10 * * *? Every Ten Minutes 0 50 * * *? Every Hour at 50 Minutes Once a day when the Server has minimal workload Once a week Once a week Once a week Every Hour The Alert Manager sends the generated s with the Alert Detector job to the target users The Change Document job copies the newly created change document entries from a buffer table into the final change document database table. The Automatic Report Generation job scans all released report generation variants that have a valid due date and generates reports based on the given restrictions System checks for citation notifications from the assigned content providers System checks for citation updates from the assigned content providers System synchronizes citation data with content providers. If the Alert Log Configuration in the EC Configuration Compliance Management menu is activated, then the EC application sends alle EC Warnings and Error Log to EC user(s) Note The scheduled jobs should not be run at the same time to load off the application Required Manual Periodic Tasks The following manual tasks are available: Task Tools supporting this task Recommen ded Frequency Detailed Description Check Log files Log Viewer Weekly The EC Administrator should check the EC logs for the following problems: Calculation errors Grave error in the EC persistency Database Overflow Database Management tools Weekly The administrator should check if the EC database content and logs do not grow faster than the database settings allow SAP SE or an SAP affiliate company. All rights reserved. 79

80 EC System Checks EC System Checks Once, after installation The EC system checks should be checked after installing the EC application. For more information, see the chapter Report Generation Does Not Work Load Balancing For more information about load balancing, see the following documentations: Chapter SAP Load Balancing Protocol Specification at Chapter SAP Web Dispatcher at m User Management For detailed information about user management engine (UME), see the documentation for NetWeaver CE at User Management Engine (UME) can use a Lightweight Directory Access Protocol (LDAP) directory, database, or the ABAP user management of a SAP NetWeaver Application Server as a data source. Therefore, in most cases, no user data synchronization is necessary. For more information, see the SAP Help Portal at Technical Interfaces Web Services EC Web Services This chapter describes how to manage EC transactional data such as exceptions, emissions, measurements and consumptions imported from external systems via Web Services. The EC transactional data interfaces are used to integrate different data sources for the above-mentioned objects. These data sources are mainly external data historian systems, LIMS, or FEMS systems that collect, store and aggregate data. These data items are important for the different emission calculations carried out in EC. The Facility Integration in Master Data Management enables the user to create and manage mapping objects for importing exceptions via Web Services. It enables the user to create and manage mapping objects for importing emissions, measurements and consumptions via Web Services. The creation of the external object IDs takes place in the EC Configuration Integration Integrated Systems SAP SE or an SAP affiliate company. All rights reserved.

81 Mapping External Object IDs to EC Objects Mapping external object IDs to the corresponding objects or object combinations in EC provides the link between the data historian and EC. This link is crucial for mapping the various data sources managed in the external systems to the EC facility levels and the corresponding materials. The system works by mapping data objects known by data historians or other external systems (e.g. Tag IDs) to the corresponding exception, consumption, emission, and measurement entries for a certain material and facility within EC. The external Tag ID for a certain measurement value is mapped to the corresponding Facility/Material combination in EC. Since multiple external data sources may be importing data into EC, it is necessary to track when and from where an imported measurement, consumption, emission, or exception value has come from. To do this, an external system ID, for each system that provides data to EC is identified. This system ID is stored together with each exception, measurement, emission and consumption value that was imported. The external tag ID together with the external system ID is used to identify the correct position for the value in the EC facility hierarchy and the corresponding material for each facility. The dialog to maintain the system IDs is located in the administration part of EC. In the EC menu, use the following path: Configuration fi Integration fi Integrated Systems. Activity for creating System Integration Create a new system integration Description To create a new connection, navigate to Configuration Integrated Systems. Press the Create button and enter the External System ID and the External System Name for your new integrated system. Optional, enter an External System URL. Save your entries. The following sections of this document describe the transactional data interfaces functionality in more detail: Integration user interface Mapping of master data Mapping of consumption data Mapping of measurement data Mapping of emission data Description of the Web Service interface Note You can create the same system tag and system ID combination on several facilities. The Web Service will generate several entries in different facilities SAP SE or an SAP affiliate company. All rights reserved. 81

82 Integration User Interface The integration user interface (popup window) is accessible on the facility detail to define integration objects of the facility. This interface has four tabs for the object mapping: Master Data (Exception), Consumption, Measurement, and Emission. Tab Master Data (Access Only via Master Data Management) The Master Data tab is used to define the exception mapping between an external system and EC. For the mapping, two IDs are required; one for mapping the system (Exception Sys ID), and one for mapping the object (Exception Tag ID). Activity for Mapping Exceptions Mapping Exceptions Description Prerequisite: You have defined an Integrated System To map Exceptions, proceed as follows: 1. Choose the Master Data tab In the Integration view 2. Press the Create button In the Integration view of the dialog box. A new line opens where you can enter the mapping information. 3. Enter the Reference Type for system mapping, open the dropdown box and select the Exception Sys ID in the Ref Type column. The values you can choose in the Ref Type column cannot be customized. 4. Enter the external reference (it must be the same spelling like the External System ID has, which you have entered for the external system definition) in the External Ref field to identify the external system. 5. The External Reference column has no function in case you choose the Exception Sys ID item from the dropdown list. 6. In the Description field, enter a description for the system mapping. 7. To delete the system mapping, press the Delete button in the Del. column. 8. Enter the Reference Type for object mapping, open the dropdown box and select the Exception Tag ID in the Ref Type column. The values you can choose in the Ref Type column cannot be customized. 9. Enter the external reference (Exception Tag ID) in the External Ref field to identify the external object (data record). 10. The External Reference column has no function in case you choose the Exception Tag ID item from the dropdown list above. 11. In the Description field, enter a description for the object mapping. This field has no further functionality. 12. To delete the object mapping, press the Delete button in the Del. column. 13. Press the OK button to accept your mapping or changes. 14. Press the Save button in the facility detail to save the changed data SAP SE or an SAP affiliate company. All rights reserved.

83 The assignee is one of the following persons: If a Facility Responsible function has been assigned to the facility, Web Service uses this responsible person as exception assignee. The assignee of the exception is the facility responsible. If the facility has no responsible user, then the exception has the LOV administrator (SYS_ADMIN_USER) user as assignee. Note You can create the same system tag and system ID combination on several facilities. The Web Service will generate one exception with several facility assignments. In addition, all facility responsible users are assigned to the newly created exception and this exception will appear on the related user dashboard. Tab Consumption (Access Only via Emissions Management) The Consumption tab is used to define the consumption mapping between an external system and EC. Every consumption mapping needs at least one material definition. To assign materials to the facility, use the Material tab in the Facility Detail view. The Integration window for consumptions displays three areas representing the consumption mapping, the involved single consumption parameter, and the involved consumption parameter sets. The values for single consumption parameters and parameter sets come from different data points in the external system. Activity for Mapping of Consumptions Mapping Consumptions Description Prerequisites: You have defined an integrated system. You have assigned materials to the facility. To map consumptions, proceed as follows: 1. In the Integration view, choose the Consumptions tab. 2. In the Integration view of the dialog box, press the Create button. A new line opens (in the top pane) where you can enter the mapping information. 3. Select a material from the dropdown menu in the Material column. The materials unit is filled in by the system. The materials dimension is fixed, but you can change the unit if required. Only assigned materials (see Materials tab) appears in this dropdown box. 4. Select a method from the dropdown menu in the Method column. Possible values are: Calculated, Measured, and Estimated (the values can be customized). The method property is optional and is supplied by the external application or can be predetermined in the mapping screen as well. 5. Select the external system from the dropdown list in the External System column. 6. Enter the external tag ID in the External Tag ID column. 7. The Overwrite column enables you to overwrite consumptions if the system detects the same consumption in the system SAP SE or an SAP affiliate company. All rights reserved. 83

84 8. Press the Create Params. button to assign all used parameters in equations, which are assigned on the Materials tab for the consumption material in Details view. The Consumptions Parameter Sets pane is editable; at a minimum, one parameter set must be used in an assigned equation. In this case, you can use the Create button in this pane to assign more parameter sets. 9. To delete the consumption mapping, press the Delete button 10. Press the OK button to accept your entries. 11. Press the Save button in the facility detail to save the changed data. Note You can create the same system tag and system ID combination on several facilities. The Web Service generates several consumption entries in different facilities. The consumption parameter does not support this functionality because they are dependent on the imported consumption data. Tab Measurement (Access Only via Emissions Management) The Measurement tab is used to define the measurement mapping between an external system and EC. Activity for Mapping of Measurements Mapping Measurements Description Prerequisites: You have defined an integrated system. To map measurements, proceed as follows: 1. In the Integrations view, choose the Measurements tab. 2. Press Create button. A new line opens where you can enter the mapping information. 3. Enter a material in the Material column. The material is a required field. To select a material, press the Magnifying Glass button. A Material Search dialog box opens. The materials unit is filled in by the system. To change the material s dimension or unit, press the Magnifying Glass button. A Unit Search dialog box opens. 4. Select a measurement type from the dropdown menu in the Measurement Type column. Possible values are: Concentration, Mass, Temperature, and Volume (the values can be customized). The measurement type is a mandatory field. 5. Select the external system from the dropdown list in the External Sys column. 6. The Overwrite column enables you to overwrite consumptions if the system detects the same measurement in the system 7. Enter the external tag ID in the External Tag ID column. 8. To delete the measurement mapping, press the Delete button in the Del. column. 9. Press the OK button to accept your entries. 10. Press the Save button in the facility details to save the changed data SAP SE or an SAP affiliate company. All rights reserved.

85 Tab Emission (Access only via Emissions Management) The Emission tab is used to define the emission mapping between an external system and EC. Activity for Mapping of Emissions Mapping Emissions Description Prerequisites: You have defined an Integrated System To map emissions, proceed as follows: 1. Choose the Emissions tab. 2. Press Create button. A new line opens where you can enter the mapping information. 3. Select a consumption material from the dropdown menu in the Consump. Material column. Only assigned materials (see Materials tab) appear in this dropdown box. 4. Enter a material in the Emission Material column. The material is required. To select a material, press the Magnifying Glass button. A Material Search dialog box opens. The materials unit is given by the system. To change material s dimension or unit, press the Magnifying Glass button in the Sel. column. A Unit Search dialog box opens. 5. Select the external system from the dropdown list in the External Sys. column. 6. The Overwrite column enables you to overwrite consumptions if the system detects the same emission in the system 7. Enter the external tag ID in the External Tag ID column. 8. Select a calculation frequency from the dropdown menu in the Calculation Frequency column (optional). Possible values are: Blank, Annually, Daily, Weekly, Monthly, and Hourly (the values can be customized). 9. Select a rollup type from the dropdown menu in the Rollup Type column (optional). Possible values are: Blank, Actual Emissions, Exceptional Emissions, Forecasted Emissions, and Potential to Emit (PTE) (the values can be customized). 10. Select an emission-to from the dropdown menu in the Emission To column (optional). Possible values are: Blank, Air, Land, and Water (the values can be customized). 11. To delete the emission mapping, press the Delete button in the Del. column. 12. Press the OK button to accept your entries. 13. Press the Save button in the facility detail to save the changed data SAP SE or an SAP affiliate company. All rights reserved. 85

86 Overwrite Available Values EC supports the functionality to overwrite available consumptions, consumption parameters, measurements and emissions (This functionality does not exist for exceptions). In the facility integration popup, the user can define if the defined tag can be overwritten. If the "Overwrite" option is not selected and the system detects a similar object (same External System ID and External Tag ID) during the import process, then the Web Service returns an error value. If the "Overwrite" option is selected and the system detects a similar object during the import process, then the value is overwritten, the status of the object is changed and the previous value of the object is saved to the database field "Status info". This enables you to report on the status field and status info field to see which values have been imported and which values have been overwritten. Status Information The following statuses are supported for measurements, consumptions, consumption parameters, and emissions: Status 0 = new value Status 1 = imported value Status 2 = overwritten value during the import process Status info has the prev. value Note The overwrite mechanism is not available for exceptions. The EC System creates a new EC exception every time Calendar Date Handling (Deprecated Web Services) Consumptions and Emissions In the past, the start time and end time of consumptions and emissions were imported with a fixed time value. The Start time was always 12:00:00 am and End time was 11:59:59 pm. Now the start date and end date is set from the import Web Service date interface. We also recommend using the standard time format (from 12:00:00 am to 11:59:59 pm) for importing consumptions and emissions. The time zone information (+00:00) determines how the time is imported into EC. Example The following example shows how to define a date time for consumptions and emissions. Date From (UTC): T00:00: :00 Date From (USA Pacific Time): T:08: :00 Date To (UTC): T23:59: :00 Date To (USA Pacific Time): T07:59: : SAP SE or an SAP affiliate company. All rights reserved.

87 Measurements The date and time of the measurement is set from the imported date (interface) value. The measured date supports also the time zone information. Example Date To (UTC): T14:15: :00 Exceptions The exception importer provides two methods to trigger exceptions in EC. Method triggerexception This method has no date and time interface. The date and time is set with the current import date and time. The method uses the time zone information of the used EC Server. Method triggerexceptionextended This method has three different date interfaces. All thee date interfaces support the follow format with time zone information Example: Date To (UTC) T14:15: :00 For more information about EC Data Handling, see SAP Note Date Handling with Time Zone Settings The standard deprecated EC Web services (see chapter Overview of EC Web Services) for importing transactional data into EC are using the time zone of the Web Service user to determine the date and time values that were provided by an external system. This is very confusing to the external system and it is not possible to use the same user for different locations. With the EC 3.0 Web Services, you can directly provide the date and time utilizing the facility time zone to determine the corresponding timestamp. Import Production Run The supplied date and time information is written to the production run record as is. Since production runs are assigned to batch recipes and cannot be uniquely mapped to a facility, the timestamp database value has to be interpreted in the server s default time zone. Two new methods are provided: doproductionrunimportlocaltime doproductionrunimportslocaltime 2017 SAP SE or an SAP affiliate company. All rights reserved. 87

88 The parameters are identical to their existing counterparts except that pstartdate is replaced by: pstartdatestring: The start date as string in the format yyyy-mm-dd pstarttimestring: The start time as string in the format hh:mm:ss Import Production Series The supplied date and time information is written to the production series record as is. Since production series are assigned to batch recipes and cannot be uniquely mapped to a facility, the timestamp database value has to be interpreted in the server s default time zone. Two new methods are provided: doprodseriesimportlocaltime doprodseriesimportslocaltime The parameters are identical to their existing counterparts except that pstartdate and penddate are replaced by: pstartdatestring: The start date as string in the format yyyy-mm-dd pstarttimestring: The start time as string in the format hh:mm:ss penddatestring: The end date as string in the format yyyy-mm-dd pendtimestring: The end time as string in the format hh:mm:ss Import Consumption The supplied date and time information is written to the consumption record as is. The timestamp information is interpreted by using the time zone that is assigned at the facility this consumption belongs to. If the facility does not have a time zone assigned, the server s default time zone is used. Two new methods are provided: doconsumptionimportlocaltime doconsumptionsimportlocaltime The parameters are identical to their existing counterparts except that pdatetimefrom and pdatetimeto is replaced by: pstartdatestring: The start date as string in the format yyyy-mm-dd pstarttimestring: The start time as string in the format hh:mm:ss penddatestring: The end date as string in the format yyyy-mm-dd pendtimestring: The end time as string in the format hh:mm:ss Import Emission The supplied date and time information is written to the emission record as is. The timestamp information is interpreted by using the time zone that is assigned at the facility this emission belongs to. If the facility does not have a time zone assigned, the server s default time zone is used. The Web Service xem_emissionimport shall provide methods for importing data using date and time strings SAP SE or an SAP affiliate company. All rights reserved.

89 Two new methods are provided: doemissionimport doemissionsimport The parameters are identical to their existing counterparts except that pdatefrom and pdateto is replaced by: pstartdatestring: The start date as string in the format yyyy-mm-dd pstarttimestring: The start time as string in the format hh:mm:ss penddatestring: The end date as string in the format yyyy-mm-dd pendtimestring: The end time as string in the format hh:mm:ss Import Measurement The supplied date and time information is written to the measurement record as is. The timestamp information is interpreted by using the time zone that is assigned at the facility this measurement belongs to. If the facility does not have a time zone assigned, the server s default time zone is used. Two new methods are provided: domeasurementimport domeasurementimports The parameters are identical to their existing counterparts, except that pdate is replaced by: pdatestring: The start date as string in the format yyyy-mm-dd ptimestring: The start time as string in the format hh:mm:ss Trigger Exception The supplied date and time information is written to the newly created EC exception record as is. The timestamp information is interpreted by using the time zone that is assigned at the facility. If the facility does not have a time zone assigned, the server s default time zone is used. One new method is provided: triggerexceptionextendedlocaltime The parameters are identical to their existing counterparts except that pdateidentified, pdatestarted and pdateended are replaced by: pidentifieddatestring: The start date as string in the format yyyy-mm-dd pidentifiedtimestring: The start time as string in the format hh:mm:ss pstartdatestring: The start date as string in the format yyyy-mm-dd pstarttimestring: The start time as string in the format hh:mm:ss penddatestring: The end date as string in the format yyyy-mm-dd pendtimestring: The end time as string in the format hh:mm:ss 2017 SAP SE or an SAP affiliate company. All rights reserved. 89

90 Overview of EC Web Services Every transactional Web Service exists twice in the EC System. The reason for this is that EC 3.0 has completely new Web Service s that are based on the new EJB 3.0 and supports new methods with enhanced time zone settings. For more information about time zone settings, see the chapter Date Handling with Time Zone Settings. The old Web Services from EC 2.0 are needed for customers that have web clients based on the EC 2.0 WSDL files. The Web Services can be reviewed in the SAP Web Service Navigator. ( To access the Web Service Navigator, the user needs NetWeaver administration permissions. To run the EC Web Services, the user also needs EC permissions. Web Service: EC Consumption Data Import For the consumption data import, the Web Service is called EC_ConsumptionImport and xem_consumptionimport EC_ConsumptionImport Operation Name checkconnection doconsumptioncalcflagsett ing doconsumptionimport doconsumptionimport LocalTime doconsumptionimportudf doconsumptionsimport doconsumptionsimportloca ltime doconsumptionsimportudf getconsumptionperiod geterrorcodes Description Return a string if the connection works Update the calculation Flag of Comption values for a given time period Run one consumption import Run one consumption import with local date time settings: refer to chapter Date Handling with Time Zone Settings. Run one consumption import with local date time settings and user defined fields Run one or more consumption import Run one or more consumption import with local date time settings: refer to chapter Date Handling with Time Zone Settings. Run one or more consumption import with local date time settings and user defined fields Determine correct Facility/Material combination based on given Ext. System ID and Ext. System Tag ID Return List of valid Error and Warning codes: code = 0 code =- 2 code =- 1 Finished successfully Error: Not imported - incomplete consumption Error: cannot read integration information SAP SE or an SAP affiliate company. All rights reserved.

91 code =- 3 code =1 code =- 4 code =- 9 code =- 10 code =- 5 code =- 7 code =- 11 code =- 12 code =- 20 code =- 21 code = -23 code = -24 code = -25 code = -26 code = -27 code = -28 code = -29 code = -30 Error - no detailed information (check the EC Log Viewer) Warning - No facility found for the system ID and Tag Id Error - Wrong Unit. Cannot resolve imported Unit 'External ID' Error - Wrong Unit. The Mapping Unit has different Dimension like the parameter Unit Error - Missing Measurement Value Type. Enter Measurement Value Type in the facility integration Error: Not imported - incomplete consumption single parameter Error: Not imported - incomplete consumption parameter set Error: The imported consumption is overlapped with another consumption in the system Error: The imported consumption could not be stored, due to this consumption is already in the EC system. If you want to overwrite consumption, change the integration setting 'overwrite' and do the import again Error: The current user has no permission Error: It is not allowed to import data in inactive facilities. EC Property facility.inactive.forbid.import.data is true Error: Time period of consumption not equal to time period of consumption material Error: Start time of the consumption is not valid Error: Wrong or invalid UDF assignment Id given Error: Wrong UDF material assignment Error: Given UDF value does not match UDF type Error: Given UDF unit does not match to the dimension of the UDF Physics Value Error: Given UDF currency does not exist Error: UDF picklist key is missing or wrong 2017 SAP SE or an SAP affiliate company. All rights reserved. 91

92 getparamsupportedunits getsupportedunits Return List of defined Units of a dimension for consumption parameter, which is defined in the parameter management (SAP R/3 External IDs) For more information, see the SAP Note Return List of defined Units of a dimension for consumption, which is defined in the facility material assignment (SAP R/3 External IDs) For more information, see the SAP Note xem_consumptionimport Operation Name checkconnection doconsumptionimport doconsumptionsimport getconsumptionperiod geterrorcodes getparamsupportedunits getsupportedunits Description Return a string if the connection works Run one consumption import Run one or more consumption import Determine correct Facility/Material combination based on given Ext. System ID and Ext. System Tag ID Return List of valid Error and Warning codes: See Error codes in the Web Service EC_ConsumptionImport Return List of defined Units of a dimension for consumption parameter, which is defined in the parameter management (SAP R/3 External IDs) For more information, see the SAP Note Return List of defined Units of a dimension for consumption, which is defined in the facility material assignment (SAP R/3 External IDs) For more information, see the SAP Note The operations doconsumptionimport, doconsumptionimportlocaltime, doconsumptionsimport, and doconsumptionsimportlocaltime have the following optional Interfaces: Interface pamountunit (String)) pdescription (String) ptier (String) psimpleconsumptionparams (consumptionparam[]) pconsumptionparamets (consumptionparam[]) Description If the unit is empty(null), then the system takes the unit from the facility consumption integration definition Set to null, if not used Set to null, if not used. Set to null, if not used. Set to null, if not used SAP SE or an SAP affiliate company. All rights reserved.

93 Note The consumption Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the Action EC_EmissionManagerWebService. Example of a Web Service with User Defined Fields (UDF). All other UDF web services have the similar build up. Web- Service Operation Input parameter doconsumptionimportudf Type Name/ Value Meaning String psystemid mandatory String psystemtagid mandatory Date pdatetimefrom Start Date and Time of the Consumption - optional, if set, pdatetimeto has to be set as well and pstartdatestring, pstarttimestring, penddatestring and pendtimestring are not read Date pdatetimeto mandatory, if pdatetimefrom is given (not null) String pstartdatestring Start Date of the Consumption - mandatory, if pdatetimefrom is not given or is null String pstarttimestring Start Time of the Consumption - mandatory, if pdatetimefrom is not given or is null String penddatestring End Date of the Consumption - mandatory, if pdatetimeto is not given or is null String pendtimestring End Time of the Consumption SAP SE or an SAP affiliate company. All rights reserved. 93

94 mandatory, if pdatetimeto is not given or is null double pamount Amount of the Consumption String pamountunit Not mandatory if empty then the unit from the integration is used. For more information see the SAP Note String ptier Not mandatory if empty then the method/tier from the integration is used int puncertainty Not mandatory (0-100) ConsumptionParameter[] psimpleconsumptionparams Consumption Parameter ConsumptionParameter[] pconsumptionparameterset Consumption Parameter String pdescription Not mandatory int ppercentgood Not mandatory (0-100), this information is saved in the uncertainty field of the consumption. UdfKeyValue[] ptransudfvalues[] Array with trans UDF values - optional udfxareaid long Technical Id of the UDF assignment. This is the ID of the Element within the Area. Technically Name: ID of TD_UDF_X_AREA value String value to set unitid long for UDF elements of type Physics Value, the Technical Id of the Unit optional, if not set then the unit of the UDF element definition is used SAP SE or an SAP affiliate company. All rights reserved.

95 currencyicocode long for UDF elements of type Currency the ICO Code of the currency optional, if not set then the currency of the UDF element definition is used Return value Integer ErrorCode = 0 Everything ok. ErrorCode <> 0 Error or Warning See result of the method geterrorcodes Web- Service Operation Input parameter doconsumptioncalcflagsetting Type Name/ Value Meaning String psystemid mandatory String psystemtagid mandatory Date pdatetimefrom Start Date and Time of the Consumption - optional, if set, pdatetimeto has to be set as well and pstartdatestring, pstarttimestring, penddatestring and pendtimestring are not read Date pdatetimeto mandatory, if pdatetimefrom is given (not null) String pstartdatestring Start Date of the Consumption - mandatory, if pdatetimefrom is not given or is null String pstarttimestring Start Time of the Consumption - mandatory, if pdatetimefrom is not given or is null String penddatestring End Date of the Consumption - mandatory, if pdatetimeto is not given or is null 2017 SAP SE or an SAP affiliate company. All rights reserved. 95

96 String pendtimestring End Time of the Consumption - mandatory, if pdatetimeto is not given or is null Boolean pcalcflag mandatory - Set the calculation flag true = Set all the flags false = Disable all the flags Boolean pmodifylockedbytask mandatory if also Consumption should be maintained which are currently locked by tasks Return value Integer 0 ok, calc flag of at least one Consumptions was set 2 Warning - No values found to modify for the given system Id, Tag Id and time range 3 Warning - No values have to be modified for the given system Id, Tag Id and time range Web Service: EC Emission Data Import For the emission import, the Web Service is called EC_EmissionImport and xem_emissionimport. It provides the following operations: EC_EmissionImport Operation Name checkconnection doemissionimport doemissionimportlocaltime doemissionimportudf doemissionsimport doemissionsimportlocaltime doemissionsimportudf geterrorcodes Description Return a string if the connection works Run one emission import Run one emission import with local date time settings: refer to chapter Date Handling with Time Zone Settings. Run one emission import with local date time settings and user defined fields Run one or more emissions import Run one or more emissions import with local date time settings: refer to chapter Date Handling with Time Zone Settings. Run one or more emissions import with local date time settings and user defined fields Return List of valid Error and Warning codes: code = 0 Finished successfully SAP SE or an SAP affiliate company. All rights reserved.

97 code =-2 code =-1 code =-3 code =1 code =-5 code =-7 code =-11 code =-12 code =-20 code =-21 code = -23 code = -24 Error: Not imported - incomplete consumption Error: cannot read integration information Error - no detailed information (check the EC Log Viewer) Warning - No facility found for the system ID and Tag Id Error: Not imported - incomplete consumption single parameter Error: Not imported - incomplete consumption parameter set Error: The imported consumption is overlapped with another consumption in the system Error: The imported consumption could not be stored, due to this consumption is already in the EC system. If you want to overwrite consumption, change the integration setting 'overwrite' and do the import again Error: The current user has no permission Error: It is not allowed to import data in inactive facilities. EC Property facility.inactive.forbid.import.data is true Error: Time period of consumption not equal to time period of consumption material Error: Start time of the consumption is not valid getsupportedunits Return List of defined Units (External Ids) of Emission For more information see the SAP Note xem_emissionimport Operation Name checkconnection doemissionimport doemissionsimport geterrorcodes getsupportedunits Description Return a string if the connection works Run one emission import Run one or more emissions import Return List of valid Error and Warning codes: Return List of defined Units (External IDs) of Emission For more information see the SAP Note The following operations doemissionimport, doemissionimportlocaltime, doemissionsimport and doemissionsimportlocaltime have the following optional interfaces: 2017 SAP SE or an SAP affiliate company. All rights reserved. 97

98 Interface punit (String) pdescription (String) puncertainty (int) ppercentgood (int) Description If the unit is empty(null), then the system takes the unit from the facility emission integration definition. For more information see the SAP Note Set to null, if not used Set to null, if not used. Set to null, if not used. If percentage good is provided, calculate Uncer-tainty as 100% - ppercentgood. If both are supplied, Uncertainty is used. Note The EC Emission Data Import Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_EmissionManagerWebService. Web Service: EC Exception Data Import Operations To allow an external system to generate and show alerts on the operator's console that are based on limit deviations, the external system must be able to query the limit information for a certain facility. To allow this, a Web Service called EC_ExceptionTrigger is created, which provides the following operations: Operation Name checkconnection triggerexception triggerexceptionextended triggerexceptionextendedl ocaltime geterrorcodes Description Return a string if the connection works Create a new Exception in EC System Create a new Exception in EC System, with extended Interface Create a new Exception in EC System, with extended Interface with local date time settings: refer to chapter Date Handling with Time Zone Settings. Return List of valid Error and Warning codes: code = 0 code =-2 code =-1 code = -3 code =1 code =-20 Finished successfully Not imported - incomplete exception Error: cannot read Integration Information Error - no detailed information, see Log entries Error - No Facility found for the System ID and Tag Id Error - User has no permission getexceptiontypes getudfbyexceptiontype Return List of defined exception types of EC See Detailed description below SAP SE or an SAP affiliate company. All rights reserved.

99 The following operations triggerexceptionextended and triggerexceptionextendedlocaltime have the following optional Interfaces: Interface Description pdateended (java.util.date) pprobablecause (String) pcorrectiveaction (String) pudfkeyvalue[] (KeyValue) Array Of UDF Key, Value and Type More information #1: The assignee of the exception is the facility responsible. If the facility has no responsible user, then the exception has the LOV administrator (SYS_ADMIN_USER) user as assignee. More information #2: Operation getudfbyexceptiontype Interface : o pexceptiontype (String) Exception Type (required) Return value: o (XML String) Functionality: o This method delivers for a given exception types all available UDF information. The return value is created in a XML String and has the follow format: <![CDATA[ <data> <tabs> <tab name = "FELIX_Data"> <!-- tab no=0 --> <rows> <row rowno="0"> <entryname name="my_date" assign_id=" " element_id=" " datatype="7"/> <entrydata></entrydata> <addentrydata></addentrydata> </row> <row rowno="1"> <entryname name="my_string" assign_id=" " element_id=" " 2017 SAP SE or an SAP affiliate company. All rights reserved. 99

100 </row> </tab> </tabs> <dropdowndata> </dropdowndata> </data>]]> datatype="1"/> <entrydata></entrydata> <addentrydata></addentrydata> The XML file gives an overview about the requested Exception type. The assign ID and data type are needed in the method triggerexceptionextended for the UDF optional parameter pudfkeyvalue. Note The EC Exception Data Import Operations Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the Action EC_ExceptionWebService. Web Service: EC Measurement Data Import For the measurement data import, the Web Service is called EC_MeasurementImport and xem_measurementimport provides the following operations: EC_MeasurementImport Operation Name checkconnection domeasurementimport domeasurementimport- Extended domeasurementimportlo caltime domeasurementimport- LocalTimeExtended domeasurementimportud f domeasurementsimport Description Return a string if the connection works Run one Measurement import Run one Measurement import with a new property pvaluetype. The value type has to be a list of value (LOV) key such as EM_VALUE_TYPE_CONC (Concentration). All LOV keys can be read from the EC Configuration Basic Settings List of Value Hierarchy Facilities Measurement Value Types Run one Measurement import with local date time settings: refer to chapter Date Handling with Time Zone Settings. Run one Measurement import with local date time settings: refer to chapter Date Handling with Time Zone Settings and the new property pvaluetype. Run one Measurement import with local date time settings and user defined fields Run one or more Measurements import SAP SE or an SAP affiliate company. All rights reserved.

101 domeasurementsimporte xtended: domeasurementsimportl ocaltime domeasurementsimportl ocaltimeextended domeasurementsimportu df domeasurementsimportu dfcomment geterrorcodes Run one or more Measurements import and the new property pvaluetype. Run one or more Measurements import with local date time settings, see to chapter Date Handling with Time Zone Settings. Run one or more Measurements import with local date time settings: refer to chapter Date Handling with Time Zone Settings and the new property pvaluetype. Run one or more Measurements import with local date time settings and user defined fields Run one or more Measurements import with local date time settings and user defined fields and Comment field Return List of valid Error and Warning codes: code = 0 code =-2 code =-1 code = -3 code =1 code =-4 code =-9 code =-10 code = -12 code =-20 code =-21 Finished successfully Error: Not imported - incomplete Measurement Error: cannot read integration information Error - no detailed information (check the EC Log Viewer) Warning - No facility found for the system ID and Tag ID Error: - Wrong Unit. Cannot resolve imported Unit R3Id Error - Wrong Unit. The Mapping Unit has different Dimension like the parameter Unit Error - Missing Measurement Value Type. Enter Measurement Value Type in the facility integration Error: The imported measurements could not be stored, due to this measurement already exists in the EC system. If you want to overwrite measurements, change the integration setting 'overwrite' and do the import again Error: The current user has no permission Error: It is not allowed to import data in inactive facilities. EC Property facility.inactive.forbid.import.data is true getmeasurementvaluety pes getsupportedunits Return a list of all available Value Types IDs (List of Value IDs). These IDs can be used directly as import parameter in the measurement web services. Return List of defined Units (External IDs) of Measurement For more information, see the note SAP SE or an SAP affiliate company. All rights reserved. 101

102 xem_measurementimport Operation Name checkconnection domeasurementimport domeasurementsimport geterrorcodes getsupportedunits Description Return a string if the connection works Run one Measurement import Run one or more Measurements import Return List of valid Error and Warning codes Return List of defined Units (External IDs) of Measurement For more information, see the SAP Note The following operations domeasurementimport, domeasurementimportlocaltime, domeasurementsimport and domeasurementsimportlocaltime have following optional Interfaces: Interface punit (String) pdescription (String) Description If the unit is empty(null), then the system takes the unit from the facility emission integration definition. For more information see the SAP Note Set to null, if not used Note The EC Measurement Data Import Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or which has the action EC_EmissionManagerWebService Web Service: EC External Systems Information This Web Service is used to get the EC settings for external systems. The Web Service is called xem_externalsystems and offers the following operations: Operation Name checkconnection getalltags getconsumptionparametertags getconsumptiontags Description Return a string if the connection works Return all External Systems Tags that are defined for the passed system. (Tags for Consumptions, Consumption Parameters, Emissions and Measurements) Return all External Systems Tags that are defined for Consumption Parameter Integration for the passed system. If the paddconstagprefix parameter is set to TRUE the consumption tag is added as prefix See also further info below Return all External Systems Tags that are defined for Consumption Integration for the passed system SAP SE or an SAP affiliate company. All rights reserved.

103 getemissiontags getmeasurementtags Return all External Systems Tags that are defined for Emission Integration for the passed system Return all External Systems Tags that are defined for Measurement Integration for the passed system getconsumptionparametertags has following optional Interfaces: Interface psystemid (String) paddconstagprefix (Boolean) Description Unique identifier for external system. Set this parameter to NULL to get tags for all systems If this parameter is set to TRUE the return value also contains the name of the consumption tag that is related to the parameter separated by the character ~. E.g.: CONS_TAG~PARAM1_TAG CONS_TAG~PARAM2_TAG The return value is Ext. System Tag IDs (String []) Note The EC External Systems Information Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_EmissionManagerWebService. Web Service: EC Production Series Data Import Operations For the Batch Process Production Series import, the Web Service is called EC_ProductionSeriesImport and provides the following operations: Operation Name checkconnection doprodseriesimport doprodseriesimportlocaltime doprodseriesimports doprodseriesimportslocaltime geterrorcodes Description Return a string if the connection works Run one Production Series import Run one Production Series import with local date time settings: refer to chapter Date Handling with Time Zone Settings. Run one or more Production Series import Run one or more Production Series import with local date time settings. See chapter Date Handling with Time Zone Settings. Return List of valid Error and Warning codes code = 0 code =-2 Finished successfully Error: Not imported - incomplete Production Series data 2017 SAP SE or an SAP affiliate company. All rights reserved. 103

104 code =-14 code = -16 code =-3 code =-19 Error: cannot find relevant Recipe Error: cannot save Production Series data Error: cannot read Recipe data Error: incorrect value for Prod. Runs Note The EC Production Series Data Import Operations Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_BatchProcessWebService. Web Service: EC Production Run Data Import Operations For the Batch Process Production Run import, the Web Service is called EC_ProductionRunImport and provides the following operations: Operation Name checkconnection doproductionrunimport doproductionrunimportlocaltime doproductionrunimports doproductionrunimportslocaltime geterrorcodes Description Return a string if the connection works Run one Production Run import Run one Production Run import with local date time settings. See chapter Date Handling with Time Zone Settings. Run one or more Production Run import Run one or more Production Run import with local date time settings. See chapter Date Handling with Time Zone Settings. Return List of valid Error and Warning codes: code = 0 code =-2 code =-14 code =-15 code = -3 code =-17 code =-18 code =-4 Finished successfully Error: Not imported - incomplete consumption Error: cannot find relevant Recipe Error: cannot save Production Run data Error: cannot read Recipe data Error: wrong Material specified Error: wrong Step number specified Error: wrong Unit specified. The Unit should be of 'Mass' Dimension SAP SE or an SAP affiliate company. All rights reserved.

105 Note The EC Production Run Data Import Operations Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_BatchProcessWebService. Web Service: Facility Compliance The Web Service EmFacCompFacCreate is used to create facilities by their facility type. A facility type consists of one or more Hazards. A hazard consists of one or more properties. A property holds one or more User-Defined Fields (UDF) elements. The Web Service is used from outside of the Environmental Compliance to generate new facility objects. The newly created object appears then in the Facility Hierarchy beneath the External Created Facility node. The Web Service EMFacCompFacCreate provides the following operations (WSO): WSO checkconnection The following table displays required input values and the return values of the Web Service operation. Web-Service Operation checkconnection Input parameter Type Name/ Value Meaning - - (there are no parameter necessary) Return value Integer ErrorCode = 0 everything ok ErrorCode = 1 connection error, connection is active but currently the system is not available WSO getfacilitytypes This operator reads out all possible facility types defined inside Environment compliance. The following table displays required input values and the return values of the Web Service operation. Web-Service Operation getfacilitytypes Input parameter Type Name/ Value Meaning String(2) Language Language code, in which language the name of facility type returns. If no language code is set the system use EN per default. Possible values are: EN, DE Return value Integer ErrorCode = 0 everything ok ErrorCode = 1 ErrorCode = 2 connection error, connection is active but currently the system is not available Database error 2017 SAP SE or an SAP affiliate company. All rights reserved. 105

106 ErrorCode = 4 ErrorCode = 16 Required language is not available No data! No facility types defined in system Array Returns an array. Every element of the list exists of two values. If the array contains no value an error occurs or there is no facility type defined. Type Array Element Meaning Long FaciTypeId ID of facility type String(255) FaciTypeName Name of facility type WSO getvalidityareas This operator reads out all validity areas. The following table displays required input values and the return values of the Web Service operation. Web-Service Operation getvalidityareas Input parameter Type Name/ Value Meaning String(2) Language Language code, in which language the name of facility type returns. If no language code is set the system use EN per default. Possible values are: EN, DE Return value Integer ErrorCode = 0 Everything ok. ErrorCode = 1 ErrorCode = 2 ErrorCode = 4 Connection error, connection is active but currently the system is not available. Database error. Required language not available. Array Returns an array. Every element of the list exists of two values. If the array contains no value, an error occurs or there is no facility type defined. Type Array Element Meaning String(127) ID ID of validity area. String(255) Name Name of validity area. WSO createfacilitybytype This operator creates the facility by type. The following table displays required input values and the return values of the Web Service operation SAP SE or an SAP affiliate company. All rights reserved.

107 Web-Service Operation createfacilitybytype Input parameter Type Name/ Value Meaning String(2) Language Language code for the facility name (optional). String(255) Name Name of new facility. If no language code is set, the system uses the standard language EN per default. String(255) RefType The object type which refers to the ERP system. String(255) RefId ID of object which refers to the ERP system Long FacTypeId ID of the facility type of which the facility should base on. String(127) ValAreaId ID of the validity area. String(255) FolderName (optional) The folder name beneath the folder External Created Facility where the facility is stored. Return value Int ErrorCode = 0 Everything ok. ErrorCode = 1 ErrorCode = 2 ErrorCode = 4 ErrorCode = 16 ErrorCode = 32 ErrorCode = 64 Connection error, connection is active but currently the system is not available. Database error Required language is not available. A wrong parameter is handed over. Error during creating facility. A facility with the handed over RefType and RefId still exist in system. Error occurs while processing. The error occurs during facility creation. Comment If no language code is set, the system uses the standard language EN per default for the name, which is delivered first. This means, if only one name is specified, e.g. in German, then the system uses this name also for the English translation. This Web Service can also be used creating facilities of type Facility within the facility hierarchy when you are using standard EC. (Not Facility Compliance.) The following parameters are required: 1. Facility Name 2. Facility Compliance Type ID needs having value 0 3. Folder Name (Parent folder of the new created facility) 2017 SAP SE or an SAP affiliate company. All rights reserved. 107

108 After running the Web Service, the EC application creates the new facility Facility Name in the hierarchy of the folder Folder Name. It is important that the name of the folder is unique in the facility hierarchy Note that the empty parameters shall have empty string values instead of being NULL! WSO createfacilitiesbytype This operator creates more than one facility by type. The following table displays required input values and the return values of the Web Service operation. Web-Service Operation createfacilitiesbytype Input parameter Type Name/ Value Meaning Array An array that contains all input parameter to create the facilities. Every record set of the array contains the following parameters: Type Array Element Meaning String(2) Language Language code for the facility name (optional). String(255 ) String(255 ) String(255 ) Name RefType RefId Name of new facility. If no language code is set the system will use the standard language EN per default for the handed over name. The object type that refers to the ERP system. ID of object that refers to the ERP system Long FacTypeId ID of the facility type of that the facility should base on. String(127 ) String(255 ) ValAreaId FolderName ID of the validity area. (optional) The folder name beneath the folder External Created Facility where the facility is stored. Comment If no language code is set the system uses the standard language EN per default for the name, which is delivered first. This means, if only one name is specified, e.g. in German, then the system uses this name also for the English translation. Return value Type Name/ Value Meaning Int ErrorCode = 0 Everything ok SAP SE or an SAP affiliate company. All rights reserved.

109 ErrorCode = 1 ErrorCode = 64 Connection error, connection is active but currently the system is not available. Error occurs while processing. The error occurs at least during one facility creation. The system returns an array that contains the errors for every failed facility creation. Array The array contains a declaration of facility and the error that occurs during facility creation. Type Array Element Meaning String (255) Name Name of the erroneous facility String (255) RefType RefType of the erroneous facility String (255) RefId RefId of the erroneous facility Int ErrorCode = 2 ErrorCode = 4 ErrorCode = 16 ErrorCode = 32 ErrorCode = 64 Database error Required language not available Wrong parameter was handed over Error during creating facility. A facility with the handed over RefType and RefId still exist in system Error occurs while processing. The error occurs during facility creation WSO geterrorcodes This operator reads out the errors. The following table displays required input values and the return values of the Web Service operation. WebService Operation Input parameter Type Name/ Value Meaning String(2) Language Language code, in which language a possible error should be reported. If no language code is set, the system uses EN per default. If the error message is not available in the requested language code, the system uses also the default language English (Optional). Return value List Error Codes A list contains all error codes SAP SE or an SAP affiliate company. All rights reserved. 109

110 Integer ErrorCode = 0 Everything ok. ErrorCode = -1 Unexpected error. Remark None Note The Facility Compliance Web Services need UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_FacilityComplianceWebService. Web Service: EC Facility Search The Web Service EmFacilityService provides the following operations: findfacility: Finds facilities for given input parameters. checkconnection: Checks the connection and returns a string with status information (successful or not successful). geterrorcodes: Returns all existing error codes of the facility Web Service. getfacilitydetails: Gets details of a facility. The following tables give an overview of the input and output parameters of the existing operations: WSO findfacility Web Service Operation findfacility Input parameter Type Parameter name Description String typeidentifier The identifier of the facility type as String (optional) String categoryidentifier The identifier of the facility category as String (optional) String name Name of the facility (optional) String language Language of the facility name (optional) Date keydate The validity date of the facility. Valid date has to be between start date and end date of the facility (validity period). List objectids List containing all objects IDs which should be retrieved. For synchronization possible to check, if facilities are still existing. boolean includedeleted defines whether already deleted facilities should be considered also Integer maxresults number of maximum results to be returned as result (optional) SAP SE or an SAP affiliate company. All rights reserved.

111 Output parameter EmFacility[] Facility Array of found facilities. May be empty. Type Name Description String facilityname Name of the facility Date validfrom Begin of the validity period Date validto End of the validity period EmLOVBo facilitytype Referenced type of the facility EmLOVBo facilitycategory Referenced category of the facility boolean deleted Flag, whether the facility is already deleted or not Long objectid The object ID of the facility. Long esid Technical ID of the facility. boolean moreresultsexisting Flag, whether more results are existing or not EmWebService Error error Error occurred during processing. May be empty (NULL), if no error occurred. Type Name Description int Code Numeric error code. String Description Description of the error in English. WSO checkconnection Web Service Operation checkconnection Input parameter Type Parameter name Description - - No parameters needed. Output parameter String connection String containing information, if a connection could be established or not. (Successful, not successful, ) 2017 SAP SE or an SAP affiliate company. All rights reserved. 111

112 WSO geterrorcodes Web Service Operation geterrorcodes Input parameter Type Parameter name Description - - No parameters needed. Output parameter EmWebServic eerror Code Description 1 Web Service request not processed; server error during execution. Details: 2 Web Service request not processed; user has no authorization: Contact your system administrator for further details. 3 Web Service request not processed; language is invalid: Input language = 4 Web Service request not processed; number of max results is invalid: MaxResults = 5 Web Service request not processed; LOV does not exist: LOV identifier = 6 Web Service request not processed; Requested facility does not exist: Facility identifier = 7 Web Service request not processed; Requested facility already deleted: Facility identifier = WSO getfacilitydetails Web Service Operation getfacilitydetails Input parameter Type Parameter name Description long esid The unique identifier of the ESource (primary key). Mandatory field. String language Language of the facility name (optional) Output parameter EmFacilityDet ails facilitydetails The facility details. May be NULL, if no details could be found or an error occurred. Type Name Description EmLOVBo costcenter Referenced Cost Center as LOV Double equityshare The equity share of the facility SAP SE or an SAP affiliate company. All rights reserved.

113 EmFacilityAddress facilityaddress The address of the facility EmLOVBo facilitycategory Referenced category of the facility as LOV EmLOVBo facilitystatus Referenced status of the facility as LOV EmLOVBo facilitytype Referenced type of the facility as LOV String hierarchypath The hierarchy of the parent-/childrelationship starting with the root, e.g. Carrier / Plant / Facility boolean inactive Flag, whether the facility is inactive or not Date validfrom Begin of the validity period Date validto End of the validity period EmWebServic eerror error Error occurred during processing. May be empty (NULL), if no error occurred. Type Name Description int Code Numeric error code. String Description Description of the error in English. Note The EC Facility Search Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_FacilityWebService. Web Service: EC LOV The Web Service EmLOVService gets list of values (LOV). It provides the following operations: getchildlistofvalues: Gets LOVs for the given input parameters. checkconnection: Checks the connection and returns a string with status information (successful or not successful). geterrorcodes: Returns all existing error codes of the LOV Web Service. Following tables give an overview of the input and output parameters of the existing operations: 2017 SAP SE or an SAP affiliate company. All rights reserved. 113

114 WSO getchildlistofvalues Web Service Operation getchildlistofvalues Input parameter Type Parameter name Description String lovidentifier The identifier of the facility type as String (optional), if null, the root node of the list of values is used as identifier String language The identifier of the facility category as String (optional) Output parameter EmLOVBo[] EmLOVBo Array of LOVs. May be empty. Type Name Description String lovidentifier The LOV identifier as String. String language Language of the LOV value. String value The LOV name (value). EmWebService Error error Error occurred during processing. May be empty (NULL), if no error occurred. Type Name Description int Code Numeric error code. String Description Description of the error in English. WSO checkconnection Web Service Operation checkconnection Input parameter Type Parameter name Description - - No parameters needed. Output parameter String connection String containing information, if a connection could be established or not. (Successful, not successful, ) WSO geterrorcodes Web Service Operation geterrorcodes SAP SE or an SAP affiliate company. All rights reserved.

115 Input parameter Type Parameter name Description - - No parameters needed. Output parameter EmWebService Error Code Description 1 Web Service request not processed; server error during execution. Details: 2 Web Service request not processed; user has no authorization: Contact your system administrator for further details. 3 Web Service request not processed; language is invalid: Input language = 5 Web Service request not processed; LOV does not exist: LOV identifier = Note The LOV Web Service needs UME permission. You need a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin or that has the action EC_LOVWebService. Web Service: Energy Data Export The Web Service EnergyAnalyticsExport provides the following operations: getmeasurementpoints: Exports all facilities with the type Automated, Manual, and Virtual Measurement Points that have assigned a material with type MM_TYPE_ENEGY. getmaterials: Exports all materials with a certain type, such as energy, producartion, or emission. getunits: Exports all units but currencies. getassets: Exports all facilities. getassetallocations: Exports the assignment of Measurement Points to facilities. getflexhierarchies: Exports flexible, alternative hierarchies of facilities. getflexhierarchyallocations: Exports the assignment of facilities to hierarchy nodes. getfacilitykeyfiguresudf: Exports for all facilities all user defined fields (UDF) with the mapping EA_MAPPINGS. getconsumptions: Exports consumption materials with a certain type, such as energy, producartion, or emission.. getemissions: Exports emissions from consumption materials of type MM_TYPE_ENERGY. Following table gives an overview of the input and output parameters of the existing operations: 2017 SAP SE or an SAP affiliate company. All rights reserved. 115

116 WSO getmeasurementpoints Web Service Operation getmeasurementpoints Input parameter Type Parameter name Description String language Language in which the languagedependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. Output parameter String MP_INT_ID Facility ID within the valid validity period (FAC_ID) String MP_ID Facility ID within all validity periods (OBJID) Date MP_FROM Start date of the validity period (VAL_BEGIN) Date MP_TO End date of the validity period (VAL_END) String MP_TYPE Facility type (ES_TYPE NAME) String MP_RES_ID ID of the assigned material (MAT_ID) String MP_NAME Facility name (FAC_ID NAME) String MP_SRC_ID Integrated system for the Web Service (EXT_SYS_ID) String MP_TAG_ID Integration Tag (EXT_TAG_ID) Integer DELETED Logical deletion flag. (SYS_DELETED) String TIME_PERIODICITY Time period for data entry (TIME_PERIODE CODE) UdfData[] UDF List of UDF that have the name EA_MAPPING. Type Name Description String UDF_ID Equals EA_MAPPING String UDF_VALUE String name of the value String UDF_UNIT If available, unit / currency of the value WSO getmaterials Web Service Operation getmaterials Input parameter Type Parameter name Description SAP SE or an SAP affiliate company. All rights reserved.

117 String language Language in which the language-dependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. String materialtype Material type to be exported (for example, MM_TYPE_ENERGYor MM_TYPE_PRODUCT Output parameter String MAT_ID Material ID (MAT_ID) String MAT_NAME Material name (MAT_ID NAME) String MAT_TYPE Material type (MAT_TYPE) String MAT_NORM_UNIT _ID Basic unit of the material (BASE_UNIT) Integer DELETED Logical deletion flag. (SYS_DELETED) TypeValueData[ ] IDENTIFIER List of material identifiers. Type Name Description String ID Unique identifier ID (IDENT_TYPE) String TYPE Identifier type (IDENT_TYPE TEXT) String VALUE Identifier value (IDENT_VALUE) TypeValueData[ ] CLASSIFIER List of material classifiers. Type Name Description String ID Unique classifier ID (CLASS_TYPE) String TYPE Classifier type (CLASS_TYPE TEXT) String VALUE Classifier value (CLASS_VALUE) 2017 SAP SE or an SAP affiliate company. All rights reserved. 117

118 WSO getunits Web Service Operation getunits Input parameter Type Parameter name Description String language Language in which the language-dependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. Output parameter String UNIT_ID Unit ID (CODE) String UNIT_NAME Unit name (CODE TEXT) Integer DELETED Logical deletion flag. (SYS_DELETED) WSO getassets Web Service Operation getassets Input parameter Type Parameter name Description String language Language in which the languagedependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. Output parameter String ASSET_INT_ID Facility ID within the current validity period (FAC_ID) String ASSET_ID Facility ID within all validity periods (OBJID) Date ASSET_FROM Start date of the validity period (VAL_BEGIN) Date ASSET_TO End date of the validity period (VAL_END) String ASSET_P_ID Parent facility ID (PARENT_OBJID FAC_ID) String ASSET_INT_IDPTH - String ASSET_INT_IDL - String ASSET_NAME Facility name (FAC_ID NAME) String ASSET_TYPE Facility type (ES_TYPE NAME) Integer INACTIVE Logical inactive flag. (INACTIVE) Integer DELETED Logical deletion flag. (SYS_DELETED) SAP SE or an SAP affiliate company. All rights reserved.

119 UdfData[] UDF List of UDF that have the name EA_MAPPING. Type Name Description String UDF_ID Equals EA_MAPPING String UDF_VALUE String name of the value String UDF_UNIT If available, unit / currency of the value WSO getassetallocations Web Service Operation getassetallocations Input parameter Type Parameter name Description String language Not in use; but necessary for DSXI to call the Web Service Output parameter Date KEYFIGUREDATE Start date of the allocation (VAL_BEGIN) String MP_INT_ID Measurement Point ID (FAC_ID) Date VALID_TO Facility Validity Date date String MP_ASSET_ALLOCATION Allocation in percent (EQUITITY) String ASSET_INT_D Facility ID (FAC_ID) Integer DELETED Logical deletion flag. (SYS_DELETED) WSO getflexhierarchies Web Service Operation getflexhierarchies Input parameter Type Parameter name Description String language Language in which the languagedependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. String hierarchyname Hierarchy name Output parameter String INTERNAL_ID ID of a hierarchy node (HN_ID) String ID ID of a hierarchy master node (MASTER_ID) 2017 SAP SE or an SAP affiliate company. All rights reserved. 119

120 Date VALID_FROM Start date of the validity period (VAL_BEGIN) Date VALID_TO End date of the validity period (VAL_END) String INTENAL_PARENT_ID ID of a hierarchy parent node (PARENT) String NAME Name of a hierarchy node (ID NAME) Integer DELETED Logical deletion flag. (SYS_DELETED) WSO getflexhierarchyallocations Web Service Operation getflexhierarchyallocations Input parameter Type Parameter name Description String hierarchyname Hierarchy name Output parameter Date KEYFIGUREDATE Start date of the allocation (VAL_BEGIN) String FACILITY_INTERNAL_ID Facility ID (FAC_ID) String ALLOCATION Allocation in percent (EQUITITY) String HIERARCHINODE_ID ID of a hierarchy node (HN_ID) Integer DELETED Logical deletion flag. (SYS_DELETED) WSO getfacilitykeyfiguresudf Web Service Operation getfacilitykeyfiguresudf Input parameter Type Parameter name Description String udfmapping Value of EA_MAPPINGS. (e.g. ASSETAREA) Output parameter Date KEYFIGUREDATE Start date of the allocation (VAL_BEGIN) String FACILITY_ID Facility ID to which the UDF is assigned (FAC_ID) String UDF_VALUE Value of the UDF (xxx_value) String UDF_UNIT If available, currency / unit of the UDF (PHY_UNIT_ID CODE / CUR_CURRENCY_ID ISOCD) Integer DELETED Logical deletion flag. (SYS_DELETED) SAP SE or an SAP affiliate company. All rights reserved.

121 WSO getconsumptions Web Service Operation getconsumptions Input parameter Type Parameter name Description String language Language in which the languagedependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. String materialtype Material type that should be exported, such as MM_TYPE_ENERGY, MM_TYPE_PRODUCT, and so on...). Output parameter Date KEYFIGUREDATE End date of the consumption (END_DATE, END_TIME) String MP_INT_ID Measurement point ID(FAC_ID) String MAT_ID Consumption material ID (MAT_ID) String MATUNIT_ID Unit ID (CODE) String AMOUNT Amount of the consumption material (CON_AMOUNT) String USAGE Usage text (QUALITY TEXT) String TIME_PERIODICITY Time period of the consumption, such as daily, weekly, and so on (TIME_PERIODE CODE) String TIER Name of the tier (TIER TEXT) String TIER_LEVEL Name of the tier level (TIER_LEVEL TEXT) String COMMENT Comment (COMMENT) String DELETED Logical deletion flag. (SYS_DELETED) UdfData[] UDF List of UDF that have the name EA_MAPPING. Type Name Description String UDF_ID Equals EA_MAPPING String UDF_VALUE String name of the value String UDF_UNIT If available, unit / currency of the value 2017 SAP SE or an SAP affiliate company. All rights reserved. 121

122 WSO getemissions Web Service Operation getemissions Input parameter Type Parameter name Description String language Language in which the languagedependent texts are exported. Language abbreviations must have two characters such as en for English or de for German. Default setting is en. boolean converttosiunit Indicates, whether the exported values should be converted to SI units. If a conversion should take place (converttosiunit=true) the following values will be converted before exporting: - EMISSION_VALUE_CONTROLLED, - EMISSION_VALUE_UNCONTROLLED - UNIT Output parameter Date KEYFIGUREDATE End date of the consumption (END_DATE, END_TIME) String MP_INT_ID Measurement point ID(FAC_ID) String String EMISSION_VALUE_C ONTROLLED EMISSION_VALUE_U NCONTROLLED Amount of emission (controlled) (EM_AMOUNT_CONTR) Amount of emission (uncontrolled) (EM_AMOUNT) String ET_ID Emission ID (EMISSION) String RES_ID Material ID (MAT_ID) String ROLLUP_TYPE Emission type (language-dependent, en as default) (ROLLUP_TYPE TEXT) String TIME_PERIODICITY Time period of the emission, such as daily, weekly, and so on (TIME_PERIODE CODE) String DELETED Logical deletion flag. (SYS_DELETED) String UNIT Unit of the emission amount (ISO CODE) String USAGE Material usage (language-dependent, en as default) (QUALITY TEXT) String TIER Name of the tier (TIER TEXT) String TIER_LEVEL Name of the tier level (TIER_LEVEL TEXT) String DIMENSION Dimension of the unit (SAP R/3 ID) (DIMENSION) SAP SE or an SAP affiliate company. All rights reserved.

123 String COMMENT Comment (COMMENT) UdfData[] UDF List of UDF that have the name EA_MAPPING. Type Name Description String UDF_ID Equals EA_MAPPING String UDF_VALUE String name of the value String UDF_UNIT If available, unit / currency of the value Note The Energy Data Export Web Service needs UME permission. You need a user that has the action EC_EnergyAnalyticsWebService. Web Service: Energy Analytics Delta Info To set the date of the last export of a data type, the Web Service Energy Analytics Delta Info is called. It provides the operation setdeltainfo that sets the last requested date to the request date. If the data have been exported successfully, the system sets the success date to the request date. Web Service Operation setdeltainfo Input paramete r Type Parameter name Description String objectname AssetAllocation, Facility Keyfigure UDF Date requestdate Date of the delta export request. ( T 18:32: :00) Integer success Indicates, whether the update has been successfully (1 = true, 0 = false) Possible ObjectName parameters are the following: Parameter ASSET_ALLOCATION FLEXIBLE_HIERARCHY_ALLOCATION ORGANIZATION KEYFIGURE_FACILITY_UDF ASSETHEADCOUNT KEYFIGURE_FACILITY_UDF ASSETAREA KEYFIGURE_CONSUMPTION MM_TYPE_ENERGY KEYFIGURE_EMISSION Description Asset Allocation Hierarchy Organizational Unit Occupancy in Facilities Area in Facilities Consumptions of Material Type Energy Emissions 2017 SAP SE or an SAP affiliate company. All rights reserved. 123

124 Note The Energy Analytics Delta Info Web Service needs UME permission. You need a user that has the action EC_EnergyAnalyticsWebService How to Get WSDL File and Web Service URLs The WSDL file and the URL for the Web Services could be downloaded from the SOA Management administration in the SAP NetWeaver Administration tool: For more information about the different NW versions, see the following documentations on the SAP Help Portal: SAP NetWeaver CE Navigate to the Web Services Administration URL: SAP NetWeaver CE 7.1 EHP1 m Navigate to the Single Service Administration URL: SAP NetWeaver Composition Environment m Navigate to the Single Service Administration URL: SAP NetWeaver Navigate to the Single Service Administration URL: SAP NetWeaver 7.3 Including Enhancement Package 1 m Navigate to the Single Service Administration URL: SAP NetWeaver Navigate to the Single Service Administration URL: SAP NetWeaver Navigate to the Single Service Administration URL: SAP SE or an SAP affiliate company. All rights reserved.

125 Web Service Status Information of Emissions, Consumptions, and Measurements The database tables from emissions, consumptions and measurements contain 2 columns with additional information about the status of the imported data. Database Table Column Description EM_EMISSION_RES STATUS Value: 0; The data is not imported with the EC web service. Value: 1; The data has been imported initial with the EC web service Value: 2; The data has been overwritten with the EC web service. The status info has the original value which has been overwritten EM_EMISSION_RES STATUS_INFO When the status is 2, then this column has the information about the original value and unit which has been overwritten: Example: 45t EM_ES_DATA STATUS Value: 0; The data is not imported with the EC web service Value: 1; The data has been imported initial with the EC web service Value: 2; The data has been overwritten with the EC web service. The status info has the original value and unit which has been overwritten EM_ES_DATA STATUS_INFO When the status is 2, then this column has the information about the original value which has been overwritten: Example: 45t EM_ES_MEASURE STATUS Value: 0; The data is not imported with the EC web service Value: 1; The data has been imported initial with the EC web service Value: 2; The data has been overwritten with the EC web service. The status info has the original value and unit which has been overwritten EM_ES_MEASURE STATUS_INFO When the status is 2, then this column has the information about the original value which has been overwritten: Example: 45t The status information is not displayed in the EC Views. This information can be only reported in a SQL DataSource using the columns in a SQL Select Statement SAP SE or an SAP affiliate company. All rights reserved. 125

126 6.4.9 Interfaces to SAP EHS Management as Part of SAP ERP This chapter describes the handling of Integration of SAP EHS Management as part of SAP ERP (EHS) within EC. It explains the integration installation process in detail. SAP EC supports various integration points. For example, EC supports EHS integration points so that: EHS specification data and EC material parameters can be linked EHS properties and EC material property values can be linked EHS specification identifiers and EC material identifiers can be linked EHS specification classifiers and EC material classifiers can be linked EHS specification compositions and EC material parameters can be linked A scheduled job in ERP determines changed substances and updates the EC properties Additionally, the integration from EHS to EC contains material identifiers from EHS specifications, material classifiers from EHS phrases and material parameter sets from specification compositions. The data transfer runs always from EHS to EC. The EHS system is the master system. Requirements Environmental Compliance 3.0 supports only ERP Systems Version 470 and higher with Unicode. Lower systems are not supported. Installation EC-EHS integration uses SAP RFC calls. The EC system registers itself at the connected ERO system. Once this registration is established, ERP can call functions on the EC system and both system can communicate with each other vie RPC calls. Prerequisites The following prerequisites must be satisfied before EC-EHS integration can be established: EC 3.0 is installed EC ERP Transports are loaded or SAP ECC 6.0 is installed At this time (EC 3.0 SP12) following EOR releases supports the EC-EHS integration ERP 6.0 EHP6 EE6 ERP 6.0 EHP5 EE5 ERP 6.0 EHP4 E4E ERP 6.0 EHP3 E36 ERP 6.0 EHP2 EAE ERP 6.0 P7E ERP EHS is installed and configured correctly. ERP RFC Setup A RFC ERP destination entry must be maintained (in ERP transaction SM59 TCP/IP Connections) in the ERP system before RFC registration can occur. The RFC destination must have a destination type T with an activation type Register SAP SE or an SAP affiliate company. All rights reserved.

127 Note o The program-id could be for example EC30. o The RCF destination differs between Unicode systems and Non-Unicode systems. The Unicode systems should have the flag Unicode in the tab MDMP & Unicode or Unicode. EC RFC Setup The RFC setup on SAP NetWeaver Web application side has to be done first in the NetWeaver Administration (NWA) and in the second step on the EC side. To set up the RFC connection, proceed as follows: 1. Log into the NWA ( In this View, you have to set up 2 connections to the ERP System. Two connections are required due to the bidirectional communication: 1. Set up first connection. Enter the ERP System name as destination (Example ERP ) Set up the destination details. Under tab Specific Data, activate the checkbox Pooled Connection Mode. For more information, see SAP Help Portal at After finishing the destination setup, you can test the connection by pinging the ERP destination system. 2. Set up a second connection to ERP. Enter the ERP System name plus PROVIDER as destination name. (Example ERP_PROVIDER ) Enter the same destination setup properties like step 1). 2. After finishing the destination setup, the next step is to set up the JCO RFC Provider. 1. Navigate to Configuration Integration RFC Configuration. 2. Enter the program ID (for example: EC30 ). 3. In the next step, enter the RFC Destination Name like "ERP Name + Provider" (example: ERP_PROVIDER ) For more information, see SAP Help Portal at t.htm 3. After you set up the JCO RFC Provider, you can start the server in this view. On the EC side, you have to assign the different modules to the destinations. 1. Log in to the portal ( with a user that is assigned to the User Group UMEGROUP_Environmental Compliance Admin. 2. Navigate to Configuration Integration RFC Configuration. 3. Now you assign the Material Reference and Substance Reference to the newly created destination. 4. When you navigate to Master Data Management Materials and you select a material, you can search for ERP specifications and ERP materials on the Integration Tab SAP SE or an SAP affiliate company. All rights reserved. 127

128 Troubleshooting RFC Connection errors. Refer to the SAP Help Portal to troubleshoot RFC connection errors: NetWeaver Check Technical Connection If the EC and the ERP parts are set up properly, the RFC connection can be checked in transaction SM59 TCP IP connections Data Update Job As of EC 3.0 SP12, the EHS integration supports both EHS EC programs. The old /TDAG/XEMSYNCSUB program is delivered with a special transport and was part of the EC 2.0 and EC 3.0. As of EC 3.0 SP12, this ERP transport is now part of the EHS standard delivery and has changed the name. The following table shows the old and the new programs which are supported in EC. Old Program Name New Program Name Key Word TDAG/XEMSYNCSUB ENHE_R_SYNCSUB Match up specification data TDAG/XEMSYNCUNIT ENHE_R_SYNCUNIT Match up dimensions and units The documentation uses the old program names however the new program name supports the same functionality. As of SP12, EC operates with the both program names. At this time (EC 3.0 SP12) both application have the similar coding. The only one difference is that the old code is no more supported in the EC maintenance and the new program has a better error and exception handling. To have the system update data on a nightly basis, schedule the program /TDAG/XEMSYNCSUB (new ENHE_R_SYNCSUB) as a daily job. If all default parameters apply, transactions SM36 and SM37 can be used to define the daily job. If not, a selection variant for /TDAG/XEMSYNCSUB (new ENHE_R_SYNCSUB) can be used. The selection fields are: Current Date (old. Key Date) The latest changes that is transferred. Default is today. Inclueded Days (old: DeltaDay) Added days to key date, to enable a Multiple Days update period. Defaulted to 1. Rating The rating and validity area to be considered while reading data. Defaulted to /REG_WORLD. RFC Destination The RFC destination used. (required) Language Language used. (required) Specification Type The specification type restricts the read of the specifications that are assigned to selected specification type. (optional) Update Values and Identifiers This updates EC material values and material identifiers from EHS specification identifiers. Update Classifiers This updates EC material classifiers from EHS specification phrases Update Compositions This updates EC material parameter sets from EHS specification compositions. Update/Delete Compositions This updates EC material parameter sets from EHS specification compositions. This deletes the manually created parameter sets in EC of the linked materials SAP SE or an SAP affiliate company. All rights reserved.

129 After executing the, the report displays all results pushed from EC and potential errors Transfer Capabilities of Characteristics from EHS The Integration of EHS Characteristics links EHS Characteristics with EC Material Single Parameters. There are two types that support automatic data transfers from EHS to EC the parameter link and the material link. These two links are described below. Parameter Link To have a material parameter in EC automatically updated from ERP3 EHS, the parameter must be linked to a substance property. The link can be specified in the parameter definition screen in Emissions Management Parameters. The EHS substance property and an EC value characteristic name must be defined. Ensure that the EHS property value and the EC parameter have the same unit dimension. Additional Information The parameter property set indicates whether the transferred value is a single parameter or a parameter set. Sequence numbers and materials are transferred from EHS to EC differently for single parameters and parameter set. The sequence number (order number) for single materials in EC are always 0. When a set of values from EHS are linked with a single parameter, then only the first values (sequence 1) are transferred to EC and the sequence is changed to 0 (order number). Note The EHS Characteristics can be saved as ranges. Example: Density Temperature <25 C. The greater and lower operator are not transferred to EC. The example value is transferred to EC as 25 C. Material Link The second link that supports an automatic data load from EHS to EC has to be set up in the material view. An EC material can either link to either an EHS material or an EHS substance. Select the correct integration type and enter either a material number or substance ID. To test, call the transaction /TDAG/XEMSYNCSUB (new ENHE_R_SYNCSUB) to load recently changed data. Note Only value properties can be loaded. The Usage and Activity flag must be maintained correctly, or the program must be called without usage (Rating field and Validity Area field are empty) and all changes is transferred. Only substances updated since the key date + the Delta days are transferred. The material has to be reloaded to see the effect of the data load SAP SE or an SAP affiliate company. All rights reserved. 129

130 Note EC has materials with several parameters. Some of the parameters are linked (integrated) with EHS values and some not. The material parameters that are linked to EHS are considered for the data transfer from EHS. Parameters that are not integrated (linked) are not touched (deleted or modified) by the EHS integration and can be used for calculations as well. Automatic Unit Conversion during transfer process If the maintained unit in EC is the same as the property unit in EHS, the value in EHS is not converted when transferred to EC. If the units are different, the property unit is converted and the maintained unit is transferred to EC. If the user enters a property value in EHS without a unit, the program will transfer the unit value to EC. This unit is dimensionless. Source Information for Values If a specification value has source information, this is transferred automatically with the EHS value to EC material single parameter or material parameter set. In EC, the source information is saved in the parameter comment column. The source information is concatenated with the source and the source note (Above example: Clean Air Act (CAA) Section 109 NPSAQS - Test). If a parameter already has source information (EC Comment), the value is overwritten Material Groups A special property in ERP EHS can be used to link to material groups. The name of this property can be set in the EC Properties: Application:XemPutValues Value:com.technidata.em.r3.mat_grp_propertyalue If this is not maintained, a default value of ZNC_EHS_1013_076 is used. This EHS substance property must consist of characteristics; the characteristics can only take the fixed string values X or. Each of these characteristics represents a material group at EC and should be named accordingly. The link between the characteristic name and the material group in EC is done in the ListOfValues management in EC; this is where the material groups are maintained. For each parameter group, the field code is used to take the characteristic. If the material characteristic is extracted to BW, the code field is used to take both the BW info object name and the R/3 characteristic. In this case, both have to be separated by a ;, for example BW InfoObj;EH&S Characteristic SAP SE or an SAP affiliate company. All rights reserved.

131 Transfer Capabilities for EC Material Classifiers from EHS With the SAP Program /TDAG/XEMSYNCSUB (new ENHE_R_SYNCSUB), you can transfer EHS Phrases from EHS to EC List of Values (LOVs). Some EC settings must be maintained in this feature before the data is transferred automatically from EHS to EC. EC LOVs linking to EHS Phrases The List of Values (LOV) that are used for material classifiers should be linked to EHS Phrases. The linking of EC LOVs is defined in the code field of the List of Value details. The material classifier LOV has a hierarchical design. The upper level in the tree shows the classifier type and the second level (child) shows the classifier value. The Type LOV CODE field should contain the valuation type German: Bewertungsart and characteristic German: Merkmal of the R/3. The valuation type and characteristic should be separated with a semicolon (;) Optional: In addition, it is possible to define the usage of the EHS in the EC. After the characteristic, the rating and validity can be put into the LOV code definition separated with a semicolon (;) Example o Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE Description: The usage is read by the application. o Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;;US Description: The usage rating:, Validity Area: US is used for this classifier. The usage in the application is ignored. o Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;;* Description: The usage Rating:, All Validity Areas is used for this classifier. The usage in the application is ignored. o Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;*;DE Description: The usage: Rating: all, Validity Area: Germany is used for this classifier. The usage in the application is ignored. o Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;*;* Description: All rating and validity areas is read for this classifier. The usage in the application is ignored. The * is a wildcard for all ratings and all validity areas. The value LOV should contain the value of the phrase like EHS-N The LOVs are now linked with the EHS phrases. When a phrase of the type is changed in EHS and the application /TDAG/XEMSYNCSUB (new ENHE_R_SYNCSUB) is started, the facts (LOV) are automatically inserted in the material classifier. The properties that contain the Classifiers in EHS need to be maintained with the correct usage (rating and validity area) to be transferred to EC correctly SAP SE or an SAP affiliate company. All rights reserved. 131

132 Note If all sort sequences of a valuation type in EHS is deleted, this deletion cannot be transferred to EC; the values have to be deleted manually in EC. Example EHS Specification Classifier Water Pollutions Value Assignment: TSCA Value Assignment: ELINCS EC LOV CODE settings SAP_EHS_1023_009;SAP_EHS_1023_009_BASE TSCA ELINCS Water pollution is the EC LOV material type and the value assignment is the EC LOV material value. BADI Implementation as Customer Exit for Material Classifiers A new BAdI interface has been implemented to enable you to change the return EHS classifiers data before it is sent from EHS to the Environmental Compliance system. The BAdI/TDAG/EC_MAT_CL_INTE (new BADI_ENHE_MAT_CLA) is only used to transfer material classifiers to Environmental Compliance. The BAdI offers the methodread_and_write_mat_classifier which has the following two parameters: I_MATERIAL_CLASSIFIER (importing parameter) E_MATERIAL_CLASSIFIER (exporting parameter) The importing parameter table (I_MATERIAL_CLASSIFIER) contains the classifier data that should be transferred to Environmental Compliance. You can read the settings from this table and put the changed values into the export table E_MATERIAL_CLASSIFIER. This information is transferred to Environmental Compliance. The following information is transferred to Environmental Compliance: LOV_TYPE CHAR30 CHAR 30 0 EC List of Value - Type Classifier LOV_VALUE CHAR30 CHAR 30 0 EC List of Value Value of Classifier SUB_ID ESESUBID CHAR 12 0 Specification ID ESTCAT ESEESTCAT CHAR 30 0 Value Assignment Type ATNAM ATNAM CHAR 30 0 Characteristic name RATING ESEVACLID CHAR 10 0 Rating VAL_AREA ESERVLID CHAR 10 0 Validity Area ATWRT ATWRT CHAR 30 0 Characteristic value SAP SE or an SAP affiliate company. All rights reserved.

133 Transfer Capabilities for EHS Compositions to EC Material Parameter Sets This feature automatically copies composition values from changed EHS specifications to EC. In EC, these composition values and materials appear as material parameter set. Some settings must be maintained in EC before the data is transferred automatically from EHS to EC. Link Parameters and Material with R3 System The used parameters and materials must be linked to the EHS composition valuation type. A parameter that is linked to an EHS composition has to be defined as a material parameter set in EC. In addition, the integration drop-down SAP EHS composition has to be selected and the value of the row has to be an EHS composition valuation type German: Bewertungsart such as SAP_EHS_1012_002 (Exact Composition Based on Compounds). The information about the EHS valuation type can be read when you press F1 and the select the composition in the EHS Specification Property Tree. At least one EC material must be linked to the specification that contains the compositions and a second material must be linked to the specification that is the composition. This integration works only with EHS specifications (not with R3 Materials). After the parameters and materials in EC are integrated the SAP EHS application /TDAG/XEMSYNCSUB must be started. Example Integration of EHS Compositions to EC The EHS Specification IS_EC_TEST is linked with an EC Material IS_Test. The EHS Specification IS_EC_TEST2, which is a component of IS_EC_TEST is also linked with an EC Material Composition Material EHS. The EHS Specification ISTEST001 is not linked with EC Material and it is ignored during the integration process. After running the program XEMSYNCSUB, the system displays the following message: Handle Compositions EH&S Spec.: IS_EC_TEST - Param set 'Nitrozellulose Composition' of the EC Material 'IS_Test' has been updated for material'composition Material EHS' EH&S Spec.: IS_EC_TEST - No EC Materials for composition substance 'ISTEST001' found! Note o If the EHS composition value is null or empty, then the system transfers the value 0 to EC as in the above example. The upper and lower limits of the EHS compositions are not transferred to EC. o The EHS Characteristics can be saved in EHS as ranges with a greater or lower characteristic. <25 C. The greater and lower operators are not transferred to EC. The example value is transferred to EC as 25 C SAP SE or an SAP affiliate company. All rights reserved. 133

134 Update / Delete Compositions As of EC 2.0 SP10 Patch 5, the integration of compositions has two different functions: Update Compositions: The system reads the changed compositions from EHS and sends them to EC. When the linked EC Material has no compositions (Material Parameter Sets), the system inserts the compositions. When EC has the same compositions, they are updated. When EC has different compositions (manual created) than the compositions from EHS, the system ignores the compositions in EC System. Update/Delete Compositions: This mode is the same as the mode described above, but the different compositions from EHS and EC are deleted on the EC system. After running the SYNCSUB program, the EC system has the same compositions as the EHS system. Manually created compositions in EC are deleted Transfer Capabilities for EHS Identifiers to EC This feature automatically copies identifiers changed in EHS specifications to corresponding identifiers in EC Materials. Some settings must be maintained in EC before the data is transferred automatically from EHS to EC. Configuration of LOVs The next step requires the creation of some identifier types for the material. The LOV identifier should have the concatenated name of the R3 Ident Type and Ident Art. (Example: NUM-CAS) The material identifier is in the Configuration List of value Materials Material Identifier. The EC material needs a link (integration) to the EHS specification. EC is delivered with predefined LOVs for material identifiers. NUM-CAS CAS Number NAM-PROD Material Name NUM-PROD Material Number If one of these identifiers is set, the affected input fields (NAM PROD Material name) then the field is disabled and automatically overwritten by the identifier. Note The material identifiers that are linked to EHS are considered for the data transfer from EHS. Material identifiers that are not integrated (linked) are not touched (deleted or modified) by the EHS integration SAP SE or an SAP affiliate company. All rights reserved.

135 Transfer Capabilities for Units from ERP to EC The ERP transaction CUNI allows the user to enter one or a range of specific units or dimensions. These units and dimensions can be transferred to EC with the program /TDAG/XEMSYNCUNIT (new ENHE_R_SYNCUNIT). The user should test the transport to see if the unit/dimension already exists in the EC system. Some setting must be maintained in EC before the data is transferred automatically from ERP to EC. Start ERP Program to Transfer Units/Dimensions The program /TDAG/XEMSYNCUNIT (new ENHE_R_SYNCUNIT) enables the user to select units and dimensions and to select a language. This language is saved in the EC unit/dimension text. The default language in EC is English. This language is automatically set. If you select a language other than English, EC saves both languages for unit and dimension. The selection fields are the following: Unit Selection of one or more units Dimension Selection of one or more dimension RFC Destination Destination value for the RFC Call default EC Language Language of the unit text and dimension text in EC Test Mode The test mode enables the user to see if the selected units/dimensions already exist in the EC system. When this flag is selected then the system will not transfer any data. We recommend resetting the buffer after unit and dimension information has been transferred from ERP to EC Interfaces into SAP MII This chapter describes the MII actions for. For installing MII, see the following SAP Notes: For installing the EC MII 12.0 and 12.1 actions, see SAP Note and SAP Note For installing the EC MII 12.2 actions, see SAP Note For installing the EC MII 14.0 actions, see SAP Note Environmental Compliance MII Actions SAP Environmental Compliance delivers several actions that call the EC Web Services. The following actions are available in Environmental Compliance: Consumption Action: uses Web Service xem_consumptionimport Web Service method: doconsumptionsimport Emission Action: uses Web Service xem_emissionimport Web Service method: doemissionsimport Exception Action: uses Web Service xem_exceptiontrigger Web Service method: triggerexception 2017 SAP SE or an SAP affiliate company. All rights reserved. 135

136 Exception Extended Action: uses Web Service xem_exceptiontrigger Web Service method: triggerexceptionextended Measurement Action: uses Web Service xem_measurementimport Web Service method: domeasurementsimport Batch Process Production Run Action: uses Web Service xem_productionrunimport Web Service method: doproductionrunimports Batch Process Production Series Actions: uses Web Service xem_productionseriesimport Web Service method: doprodseriesimports Transactions The SAP Note with the MII Interface from SAP Environmental Compliance delivers also several sample transactions. The following sample transactions are delivered: ConsumptionSampleAction.trx import Consumptions EmissionSampleAction.trx import Emissions MeasurementSampleAction.trx import Measurements ExceptionSampleAction.trx import Exceptions ExceptionExtendedSampleAction.trx import Extended Exceptions with Date information ProductionRunSampleAction.trx import Batch Process Production Run ProductionSeriesSampleAction.trx import Batch Process Production Series All sample transactions read the data from an XML file Description of the MII Sequences (Example: Measurement) Sequence 1 XML Loader The XML Loader is responsible for loading the data from an XML file to the EC action. Instead of the XML Loader, you can use other actions to supply data for the Environmental Compliance Web Services. Configuration: The XML Loader needs one configuration the path of the XML file that contains the delivery data. When the path is set, the system automatically defines the XPath Expression for the repeater (Sequence 3). Check the path in the Repeater action SAP SE or an SAP affiliate company. All rights reserved.

137 D:\...\Transactions\consumptions.xml Sequence 2 Measurement Container The measurement container is the cache for the used data in the Measurement node. This container sends the data for the import to the main measurement action (Seq. 6) Every measurement that is read in the repeater is buffered in the container. Configuration: This action does not need any configuration. Sequence 3 Repeater The repeater is an action which loops over all XML tags and sends every single record to the Sequence 4 (measurement node). Configuration: The repeater has the XPath configuration that is automatically generated when a valid XML File is defined for the XML Loader (See Seq. 1) Sequence 4 Measurements Node The measurements node contains a single measurement record, which came from the repeater. This information is sent to the container SAP SE or an SAP affiliate company. All rights reserved. 137

138 Configuration: 1. The Measurements node has a link to the Measurement container: Measurement Document 2. Select the Measurement Node Properties Configure Object 3. The input field time zone is required. The other input fields, including Description, System ID, Tag ID, Value, Unit and Date, are default values for the imported measurement. When the system detects incoming values from the XML (this sample) it ignores the default values. Sequence 5 Tracer of Measurements Node The tracer is a Log printer that shows the data flow of a configured action. Configuration: In the link editor of the tracer, you can link some properties of the measurement nodes to the tracer message. The flow data is shown in the Log popup after running the transaction SAP SE or an SAP affiliate company. All rights reserved.

139 Sequence 6 Measurements Action This action collects all the information from the measurement container, creates the SOAP XML Envelope, and sends it to the Environmental Compliance Web Service Configuration: In the measurement action, the target system should be configured. The input fields username, password, EC server and EC port are required. The trace option enables you to see in the result SOAP envelope in the log window after running the transaction. The measurements action has a link to the measurement container: measurement document. In addition, there is another setting required. The input XML that is sending should be linked with the container action. After successful configuration, the connection settings you can start importing data. Run the sample by choosing Transaction Execute. The execution popup describes all steps and shows you the result of the import. [INFO ]: Success: 1 return code: 0 Status Code: 200 Error Msg: The import is successful if the return code is Time Zones The time zone information saves the time information of the imported date into Environmental Compliance accurately. Caution MII actions works with old EC Web Services Set the time zone of the zone where the imported data is used and read. It is important to set the right time zone because while reading the time information in the Environmental Compliance application, the system converts the time information into the time zone of the logged in user. The time information is saved in the database always in the UTC (Old GMT (Greenwich Mean Time)). Users in different time zones see different time information in Environmental Compliance SAP SE or an SAP affiliate company. All rights reserved. 139

140 The following are some samples of time zone settings: Time Zone Description Countries / Towns +00:00 UTC WET West European Time Great Britain +01:00 UTC+1 CET Central European Time Germany, France, Spain, etc. +02:00 UTC+2 EET East European Time Bulgaria, South Africa, etc. -03:00 UTC-3 Argentina, Brazil (Part) -05:00 UTC-5 EST Eastern Standard Time Canada (Part), USA (Delaware, Massachusetts, etc.) -06:00 UTC-6 CST Central Standard Time Canada (Part), Mexico (Part), USA (Alabama, Texas, etc.) -07:00 UTC-7 MST Mountain Standard Time Canada (Part), Mexico (Part), USA (Arizona, Texas, Utah, etc.) -08:00 UTC-8 PST Pacific Standard Time Canada (Part), Mexico (Part), USA (California, Nevada. Etc.) Note the following: Daylights saving time needs to be considered when importing values. For example, a value in eastern standard time (winter) should be imported with the time zone -05:00 and in eastern daylight time (summer) with the time zone -04:00 to account for it. We recommend importing data with the same time zone that the server is running in. We recommend using the following dates to import daily consumptions: o From Date: T00:00: :00 (Germany Daylights saving time) o To Date: T23:59: :00 (Germany Daylights saving time) For more information about date and time handling, see SAP Note: Unicode MII supports Unicode data with the char-set UTF-8 encoding. All Environmental Compliance properties can use Unicode characters for the import process to EC from MII Knowledge Management Integration For simple document management requirements, EC has a simple, built-in document management function, which can be used without any other document management installation. For more complex document management tasks, however, integration into a more complex document management system like SAP Knowledge Management is required SAP SE or an SAP affiliate company. All rights reserved.

141 Set Up Connection to SAP Knowledge Management System Prerequisites A SAP Knowledge Management System application is installed correctly. Procedure To configure a connection to the SAP Knowledge Management system, proceed as follows: 1. Set up of KM Web Service Proxies in SAP NetWeaver Administrator The KM Web Service Proxies are configured in SAP NetWeaver Administrator. Go to the WS/SS Administration URL:NW Search by Proxy Definition Name Single Service Administration: Service Definitions for NW 7.11 and higher releases got to Customer Proxies. 2. Index Management Web Service 1. Search for the Proxy Definition IndexManagementWSVi_Document and navigate to Configuration > Logical Ports. 2. Create a new logical port: Name: Config1Port_Document Web Service End Point URL (URL of KM Server): 3. In case you are using HTTPS use the following URL: 4. Navigate to Security and set up the authentication to access the Web Service (e.g. Authentication BASIC, Username/Password). 5. Save the configuration. 3. Repository Framework Web Service 1. Search for the proxy definition RepositoryFrameworkWSVi_Document and navigate to Configuration > Logical Ports. 2. Create a new logical port: Name: Config1Port_Document Web Service End Point URL (URL of KM Server): 3. In case you are using HTTPS use the following URL: cy 4. Navigate to Security and set up the authentication to access the Web Service (e.g. Authentication BASIC, Username/Password). 5. Save the configuration SAP SE or an SAP affiliate company. All rights reserved. 141

142 Setup of Extension Point (SAP Knowledge Management) To set up extension points, proceed as follows: 1. Log in to the portal ( with a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin. 2. Navigate to Configuration Basic Settings Extension Point. 3. Expand the DMS Plug-in and click the Easy Connect button. 4. Select the Activate checkbox. 5. After that, define the properties as described in the next section. Then save your changes. For properties, you have to define the search path within KM, a maximum number of results, a timeout period, and associations between the user-defined fields and the related KM properties. Use the following syntax to define these values: Search Path (considers any indexed document that is located in the defined folder or any of its subfolders regardless of the index): o path=<path1>;<path2> for example: path=/documents/public Documents/;/documents/Links/ Alternatively, you can use the search index (considers any document in the specified indices regardless of the folder it is located): o index=<index1>;<index> Maximum number of retrieved documents per search: o maxcount=<maximum results> for example: maxcount=300 Access timeout of Web Service requests (optional / default value is 60000): o [timeout=<timeout in ms>] for example: timeout=30000 Associations between user-defined fields (UDFs) and related KM properties: o udf_<udf-field>={namespace}propertyname for example: udf_name={ udf_description={ You can find a list of all available KM properties of a KM document if you go to System Administration System Configuration Knowledge Management Content Management Global Services Property Metadata Properties The related namespaces can be found in under System Administration System Configuration Knowledge Management Content Management Global Services Property Metadata Namespaces If you defined custom properties, a possible association would be: for example: udf_mycustomprop={ To enable the full text-search, you have to define the following association: o udf_<udf-field>=kmfulltext SAP SE or an SAP affiliate company. All rights reserved.

143 Example 1 index=all maxcount=300 udf_fulltext=kmfulltext udf_name={ udf_description={ upload_path=/documents Example 2 index=all maxcount=300 udf_fulltext=kmfulltext udf_date={ udf_name={ udf_picklist={ upload_path=/documents Setup of User-Defined Fields for Search View For the KM search dialog, you have to define the user-defined search fields in the configuration section of EC as follows: 1. Create a new UDF Area of type DMS-Search. 2. Create and assign at least one element to the area. For example: Label: Name / Type: Text For example: Label: Description / Type: Text Setup of Full-Text Search To set up the full text search, proceed as follows: 1. Select the UDF Area DMS-Search. 2. Create and assign the following element: Label: Fulltext / Type: Text field 2017 SAP SE or an SAP affiliate company. All rights reserved. 143

144 Using KM Integration in EC To link a KM document to an EC object, you can search for the KM document by the user-defined search criteria. To link a KM document, proceed as follows: 1. Select the button Add from DMS in any document table in EC. 2. A search screen appears, which allows you to define search criteria based on the previously defined UDFs. By clicking the Search button, you can search for the KM documents. The different search criteria are combined logically with the AND operator. A document is returned if all specified search criteria are equal to the document properties. The user-defined fields are compared to the KM properties as described in the following section: o Text-Field: Compares equal if both values are exactly equal. Note that this criterion is ignored when the content of the text field is empty. o Integer-Field: Compares equal if both values are exactly equal. Note that this criterion is ignored when the content of the text field is 0. o Boolean-Field: Compares equal if both values are set to true. Note that the criterion is ignored when the checkbox is deselected. o Date-/Time Field: Compares equal if both values contain the same date regardless of the timestamp. Note that this criterion is ignored when the content of the date-time field is empty. o Picklist-Field: Compares equal if both values contain the same picklist value. Note that this criterion is ignored when the content of the picklist field is empty. 3. You can link the returned documents to EC by selecting the OK button on the search result screen. The KM document name, the description and the URL is added to the link in EC Customer Development (Extension Point) Several modules of SAP Environmental Compliance can be enhanced with multiple customer-specific extensions. SAP Environmental Compliance provides several extension points where those extension points can be integrated into the product. Those extensions are developed by customers based on predefined interfaces and are delivered in separate software components (in custom Java Name Space). Customer development should be done in the SAP NWDI Landscape, which supports the deployment on a setup system landscape (DEV TEST PROD). Therefore, the NWDI provides settings to set up version management for customer software components. Conflict resolution is not necessary because the interfaces of the extension point remain stable. If the interfaces of the extension points are changed, then SAP Notes describe the relevant versions and changes. For more information about extension points, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal at SAP SE or an SAP affiliate company. All rights reserved.

145 Regulatory Content Integration The main purpose of the Regulatory Content Provider (RCP) integration into SAP Environmental Compliance (EC) is to link EC citations to citations provided by an external content provider. Regulatory texts can be automatically received from the provider using this linkage. If a citation is changed on the provider side, you could inform specific users of SAP EC about those modifications by assigning them to citation update tasks. Configure Regulatory Content Provider Set the profile ID for the current system. Every SAP EC system, such as QA, production, test, must be assigned to a unique profile ID. Link EC Citation Create a new EC citation in Permit Management in EC, or open an existing EC citation that is not yet linked to a provider. Search on the provider s portal for the appropriate citation. Enter the citation ID that is returned by the search in the appropriate EC citation input field. Retrieve the regulatory text and save the data. Receiving Updates Set up a task to receive notifications for integrated EC citations. There are two different background jobs that trigger the synchronization of the linkage and the retrieval of notifications or updates automatically. New regulatory texts are automatically transferred to the EC citation text. Check the retrieved updates Configuring the BNA Web Service and JAVA Proxy Prerequisites You have installed SAP Environmental Compliance and you have imported the EC 3.0 SP9 init or delta content. Procedure Set Up Java Proxy SAP EC cannot communicate directly to the Web Services of an external content provider from the Java Web Application framework. Therefore, a Java proxy is required. To configure a Java proxy, perform the following steps: Navigate to the NetWeaver Administrator under and log in with an administrator user. NW 7.10: Go to SOA Management and navigate to System Global Settings NW 7.11: Go to SOA Management and navigate to SOA Middleware Global Settings: HTTP Proxy Set up a new HTTP proxy and specify the following values: o Host: <Your host> o Port: <Your port> 2017 SAP SE or an SAP affiliate company. All rights reserved. 145

146 Save the proxy settings. Set Up Web Service To access the Web Services provided by the external regulatory content provider BNA valid, credential information must be maintained. To maintain this information: Enter NetWeaver Administrator as described under Set Up Java Proxy above. Navigate to: NW 7.10: SOA Management Business Administration Web Services Administration. NW 7.11: SOA Management Application and Scenario Communication Single Service Administration: Consumer Proxies Search by proxy definition name and search by name: *cite*. In the results, select CiteProfileSoap. Open the tab Configuration and choose the CiteProfileSoap in the logical port list. On the Security tab below Authentication, select HTTP Authentication and click User ID/Password (Basic). Enter the user ID and password (account has to be requested from BNA). Save the setting Configure the BNA Provider Prerequisites The BNA Web Service and Java proxy are configured successfully. Procedure The provider configuration can be found below: Configuration Integration Regulatory Content Providers Provider Setting Property BNA Profile note BNA Profile Start Publish Date Description The property BNA profile note is an optional property that can be used for additional information regarding the set profile. The BNA profile start-publish-date is used to define the start date for the notifications to be retrieved. You can define this date to avoid retrieving all existing notification updates. If there are already retrieved updates on the system, the next start date is set to the day when the last update ran. In this way, it is possible to adjust this date during the tests. Therefore, to receive updates for a longer period, just set this date to Example Value e.g. Productive Profile or QA Profile Current date e.g SAP SE or an SAP affiliate company. All rights reserved.

147 Search Citation URL Search engine for citations on provider s side. BNA Profile ID BNA Citation Text Length Link to display BNA Citation Profile ID provided by BNA Max length of the received citation texts 9216 Link to access citations on provider s side; fname=%cit_id%&linktype=reg&pdm=dib Develop own RCP Provider Prerequisites EC 30 SP09 at least must be installed Procedure Refer to the SAP Note It described how to develop an own Provide in the EC application. 6.5 High Availability This chapter describes which components in your system landscape could fail. The following components should be monitored to ensure a clear process run of EC 3.0: Component ERP EHS SAP Knowledge Management (KM) ADS ADS SMTP SAP Web Dispatcher Detailed Description EHS Integration does not work Linked Documents cannot be accessed and documents cannot be linked SAP EC PDF generation does not work SAP EC Check List Task does not work Notification does not work EC Application does not work To find out how to make the SAP Web Dispatcher a high availability solution, see Architecture of the SAP Web Dispatcher. ce a114084/frameset.htm 2017 SAP SE or an SAP affiliate company. All rights reserved. 147

148 6.6 Software Change Management Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams. The goal of Software Change Management is to establish consistent, solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products Transport and Change Management EC configuration supports a transport mechanism for transferring configuration data between different EC systems (between development and test system) The data is transport via EC Export-Import tool. For more information, see chapter 6.12 Data Export and Data Import. The EC application generates an XML file that defines the database table and the row which should be transported. At the end of the process, EC generates this XML file, which has to be used in the EC Export-Import tool. The EC Export-Import tool exports the data from one system and imports the data to a new system. Note EC Export Import tool always overwrites data on the target database system (if data exists in the used ID range) Define an Activity The transport is saved into an activity. To create an activity, proceed as follows: 1. Log in to the portal ( with a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin. 2. Navigate to the maintenance view My Transport Activities at Maintenance My Transport Activities. 3. In this view, the current logged-in user can create activities. The status of the activity is Open. This activity can now be used in the second step for transport data SAP SE or an SAP affiliate company. All rights reserved.

149 Transport Data The following configuration views support the transport function: Units and Dimensions User-Defined Fields List of Values Templates Flexible Hierarchies Facility Types Parameters Extension Point Configurations Object-Based Permission Profiles Example The following procedure is an example of how to use the transport function: 1. Create a new activity in My Transport Activities. 2. Go to Configuration Basic Settings List of Values (LOV) 3. Search with the identifier SYS_ADMIN_USER. 4. Select the LOV. 5. Click the Transport Icon Select for Transport. 6. Select the newly created activity from step Go to Maintenance My Transport Activities. 8. Release your activity. 9. Go to Maintenance Manage Transport Activities. 10. Search for your released activity. 11. Download the XML file. 12. Start the EC Export-Import tool ent 13. Use the XML file in the option Export by XML definition file. Note After transporting data, the admin user has to reset the buffers; otherwise, the new inserted data does not appear in the imported application. To do so, jog in to EC portal ( with a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin and navigate to the Reset Buffer View in Tools Reset Buffer SAP SE or an SAP affiliate company. All rights reserved. 149

150 6.6.2 Development Requests and Development Release Management Development requests help to continuously improve SAP solutions. As SAP Environmental Compliance is an SAP product, the standard roll-in process for development requests applies Release Implementation The release CD rom can be downloaded from SAP Support Portal at In SAP Software Distribution Center, select the Access downloads link and of Installations & Upgrades and search forsap ENVIRONMENTAL COMPL Every release has a unique SAP Note. For EC 3.0, all relevant release notes are described in the SAP Note Support Packages and Patch Implementation The latest EC Support Packages and Patches (only deployable files) can be downloaded from the SAP Support Portal at In SAP Software Distribution Center, select the Access downloads link and of Support Packages & Patches and search forenv.compl. The Support Packages & Patches delivery contains the different EC software components separately: ENV.COMPL. APPL. MODULES 3.0 ENV.COMPL. CENTR. MODULES 3.0 ENV.COMPL. CENTR. SERVICES 3.0 ENV.COMPL. PORTAL CONTENT 3.0 ENV.COMPL. REP. MODULES 3.0 When you update your system, you have to download and deploy the patch or support package of all EC software components for the required SP or Patch level. Every support package and patch has a unique SAP Note. All support packages and patch notes are listed in SAP Note Update Patches and Support Packages Strategy The release of EC 3.0 is delivered as a CD image. This image contains all relevant data for beginning to work with EC 3.0. After the delivery of the initial EC 3.0 release, we deliver patches when needed in appropriate intervals (this depends on the amount of errors). A support package is a collection of several patches. When managing patches and support packages, note the following: SAP SE or an SAP affiliate company. All rights reserved.

151 Download and install always the main release of EC 3.0. The release contains all EC 3.0 files. The central Release Note (SAP Note ) describes which patch notes are available for the current release. Navigate to ALL patch notes. The notes describe the update steps. Follow the description of the patch notes and always download all attachments of the patch notes. Note The deployment files do not have to be deployed for every patch. For example, if you update from EC 3.0 Patch 2 to EC 2.0 Patch 5, then you can deploy directly the Patch 5 SCA files. This exception exits ONLY for SCA files of the main application. For the other objects (non-java) like R3 Transports or BI Content, you have to update (check the installation steps in the corresponding note) every single patch in to your system (for this example: Patch 3, Patch 4 and Patch 5). 6.7 Troubleshooting Imported Initial or Delta Data Does Not Appear in EC Problem After importing data into EC via Export-Import Tool, the imported configuration data does not appear in the target system. Solution 1. After importing data, the admin user has to reset the buffer. To do so, log in to EC portal ( with a user that is assigned to the user group UMEGROUP_Environmental Compliance Admin and navigate to the Reset Buffer View at Tools Reset Buffer. 2. Check the EC Export-Import tool import.log file on the server folder Logged-In User Has No Permission for an EC Object Problem Logged-in user has no permission for an EC Object. The user has no access to the EC module. Solution The admin responsible user opens the User Authorization Analysis in Configuration Object Based Authorization. For more information about object-based authorization, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under SAP SE or an SAP affiliate company. All rights reserved. 151

152 6.7.3 Report Generation Does Not Work Problem When you try to generate a PDF report in the EC Reporting modules, you get an error message from the system. Solution You should check if the PDF generation works. Use the EC System Checks. For more information, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under If the report generation system check fails, see the SAP Help Portal for more information at Notification Does Not Work Problem Limit checks failed or EC Tasks are overdue; however, no notification is sent to the responsible users. Solution First, check if the sends function works. Use the EC System Check. For more information, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under Check if the background jobs are running correctly. For more information, see chapter Periodic Tasks EC Object Is Locked Problem You try to access an EC Object and the system shows an error that the EC Object is locked by yourself or another EC User. It can happen that the current session in Microsoft Internet Explorer is exceeded and the locked status remains. Solution Log in to the NWA ( with an administrator user The following locking objects are set by Environmental Compliance: SAP SE or an SAP affiliate company. All rights reserved.

153 Object Name EC_MATERIAL EC_ACCOUNTING EC_TASK EC_TASK_INSTANCE EC_EQUATION EC_IO_CALCULATION EC_CONSUMPTION_BASED_CALC EC_FACILITY EC_FACILITY_COMPLIANCE EC_FACILITY_TYPE EC_EXCEPTION EC_AUTHORITY EC_PERMIT EC_REQUIREMENT EC_LIMIT EC_CITATION EC_PROPERTY EC_EMISSION_MANAGER EC_COMPLIANCE_MANAGER EC_BATCH_PROCESS_RECIEPE EC_BATCH_PRODUCTION_RUN EC_BATCH_PRODUCTION_SERIES EC_Buffer Thread AutoGenVariantReportJob Description Material in Master Data Emissions Accounting Task Templates in Compliance Management Task Instances from EC Dashboard, Compliance Management Status Analyzer or from History tab of Task Templates Equations in Calculation Manager within the Emissions Management Input Output Calculations in Calculation Manager within the Emissions Management Consumption Based Calculations in Calculation Manager within the Emissions Management Facility in Master Data Facility in Facility Compliance Facility Type configuration in Facility Compliance EC Exceptions Compliance Management Authority in Compliance Management Permit and Requirement Set in Compliance Management Requirement in Compliance Management Limit checks in Compliance Management Citations in Compliance Management Properties Facility Type Configuration in Facility Compliance Facility in Emission Manager Facility in Compliance Management Batch Processes Batch Processes Batch Processes Background Job Change document Background Job Automatically Generation of Reports The Admin should only unlock EC objects that are described in the above table SAP SE or an SAP affiliate company. All rights reserved. 153

154 6.7.6 Web Services Does Not Import All Data Problem During the import process, the connection between the Web Service Client and EC 3.0 Server can be broken. Only a part of the data has been imported in the EC System. Solution When the connection between client and server is broken the Web Service process can be started one more time. The data that is already imported is overwritten (depending on the Integration settings) and the other data is imported into EC Graphics Rendering (IGS) Problem Problem When you try to create graphics and charts (IGS) in EC Reporting, the EC application does not display any charts. Solution You should check if the IGS is working. Use the EC System Checks. For more information, see the Administration description in the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under If the IGS System check fails, see the SAP Help Portal for more information at Java Scheduler Jobs Do Not Work Problem In the JAVA Scheduler, some jobs could remain in the status Starting. Solution 1. Check if the Config Tool Settings from chapter Setting Up Deployable Application Properties is set up correctly. 2. If the settings are correct, then you need to check if the EC scheduler services are running. To do so, go to the NWA ( as NetWeaver Admin user and select in the left menu Java EE Applications. Filter the applications with the name cron. Check if the applications ecs~cronjobs~service~eappl and xem~cronjobs~service~eappl are started. If they are not started, start them manually. After that, the EC 3.0 Scheduled Jobs should be completed SAP SE or an SAP affiliate company. All rights reserved.

155 6.7.9 There Is No iview Available for SAP_ECC By opening a task or an exception from the EC Dashboard, the system could show the following error message: There is no iview available for system SAP_ECC_EnvironmentalHealthSafety object TaskBo. When this error comes, then the current user has no permission to access the Object-Based Navigation View. See chapter Configuring Object-Based Navigation Error! Reference source not found.to add the missing portal pages to your own created EC roles. Note If a new role is added to an EC System, then this role also has to be added to the EC Portal Business Object with the affected operations Personalization of EC Pages Does Not Work The SAP Note describes the personalization of EC Pages in EC 3.0. After a page is personalized, some users might not see the personalization changes (e.g. hidden buttons). Possible Cause: The administration user that makes the personalization changes in portal content might not have the role (additional) from the user that accesses the Business Objects in the EC Application. To ensure that the personalization works for all users in an EC System, we recommend adding all EC Roles to the Admin user that sets up the personalization Processing of Java Scheduler Jobs Takes Too Long Problem The processing of Java Scheduler Jobs takes a long time. Solution The different EC Java Scheduler Jobs could run at the same time. This could lead to performance problems, if, for example, the Limit Scheduler, Calculation Scheduler and Change Document Transfer jobs run at the same time. You have to set up the jobs with different start times to avoid performance bottlenecks due to overlapped jobs SAP SE or an SAP affiliate company. All rights reserved. 155

156 System Copy Mode Remains in EC after Running Export or Import Problem If the EC 3.0 system is still in system copy mode when the import is finished in an incorrect manner or the Web Application timed out, run the Reset System Copy application to enable the EC 3.0 system again. Solution Reset the system copy mode in the following URL: EHS Integration Data Transfer Errors Problem In the EC EHS Integration, the data is transferred via RFC from an ERP system to EC application. In some cases, the data is not transferred correctly. Solution In the ERP system, the connection settings could be set up incorrectly. 1. Go to transaction SM59 2. Select the used TCP/IP connection 3. Go to the tab MDMP & Unicode or Unicode 4. Set up the communication type to Unicode 5. Save the TCP/IP connection settings Errors in EC Import / Export Tool Problem During the export or import process the application shows the following error messages: Import failed unknown protocol: c Export failed unknown protocol: c Solution The used folder has special characters like ö or ä or $. Remove the special characters and try again to import or export the data SAP SE or an SAP affiliate company. All rights reserved.

157 SAP EC Permission Problems Problem The user does not have permission to access the main EC modules. Solution 1. The permission problems could come during the update/deployment of the EC application.in some cases the deployment of the EC application could delete the user permission actions within the user roles. In this case (re)import the user roles from SAP Note Please refer also to SAP Note for further information about the SAP NetWeaver fix. 2. The assigned roles / groups are missing or they are wrong. The recommendation for the EC Admin user is: o Do not use any EC Roles assignment o Add the following USER Groups to the user: o UMEGROUP_Compliance Analyst o UMEGROUP_Environmental Analyst o UMEGROUP_Environmental Compliance Admin 6.8 Support Desk Management Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure. For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently. The following topics are covered: Remote Support: see chapter 6.9 Remote Support Setup. Component hierarchy relevant for this application: XAP-EM. For more information, see chapter 6.10 Problem Message Handover. 6.9 Remote Support Setup EC SAP Support needs to be able to work remotely for highest efficiency and availability. Therefore, all required support tools must be remotely accessible for SAP Support. It is possible to open a connection via Support Message your system landscape. Therefore, the EC SAP support team needs a HTTP Connection. For more information, see the following SAP Note: For SAP Router Configuration for Support Access, see SAP Note For PC Anywhere, see SAP Note For HTTP Access, see SAP Note SAP SE or an SAP affiliate company. All rights reserved. 157

158 6.9.1 Remote Debugging The following figure shows how remote debugging works in SAP NetWeaver landscape. The graphic above shows the necessary steps for enabling and working with remote debugging. The customer configures the java debug service on the SAP service marketplace (the customer creates the connection data). The customer switches on the debug mode on the java engine. The connection data is replicated to the CSS system. The developer who wants to debug remotely calls the transaction STFK and downloads the connection data that is stored in the file '..sapdebugdata_v2.txt' on the developer s file system. Also with the help of the STFK, the developer opens the connection. As a prerequisite, the customer has opened the connection in the SAP service marketplace. If the connection is open, the developer can use the ping wizard of the IDE to see whether the connection works. The developer creates a debug master project, which in turn, uses the connection data from the developer's file system to retrieve system and version information from the customer. The debug master project serves as a container for the connection data and the sources, which should be debugged SAP SE or an SAP affiliate company. All rights reserved.

159 The developer synchronizes the sources into the debug master project. If available, the system asks the developer whether to download the sources from the debug source server or from the customer directly. After the sources are retrieved, the debugging session can start. For more information, see the SAP Help Portal at or see SAP Note Problem Message Handover The SAP component for sending problem messages for errors is XAP-EM. When you set up a message, include the following information, which is necessary to reproduce the error: Support package and patch of the EC version where the problem occurs OS of the Web application server and the version of the Web application server: You can read this information from the System Information: ( from the tab Component info. Provide an Excel Export of the Software Components. Target database 6.11 BI / BW Content Introduction This chapter gives an overview of the SAP Business Warehouse (BW) content of the SAP Environmental compliance product and how the SAP Business Warehouse component works together with the SAP Environmental Compliance application. This document describes all relevant facts concerning the business warehouse component, such as: The data transfer process between the SAP EC application and SAP Business Warehouse. The responsible component is called extraction layer or extraction framework. The design and the usage of the Business Warehouse content Setup and configuration of the BW content The different items are discussed in the next chapters and subchapters. The document refers to the SAP Business Warehouse release 3.5. The SAP Note described step by step the configuration of EC and BI for some EC sample objects SAP SE or an SAP affiliate company. All rights reserved. 159

160 Technical Composition The SAP Environmental Compliance application is implemented with SAP NetWeaver Web Dynpro and needs a database in order to store all the data. In addition, the application provides an extraction layer which extracts data out of the database. In addition, this layer provides functions for transferring the database base into the Business Warehouse. For more details about the extraction layer functionality, see chapter EC Extraction Layer. The following figure provides a graphical review of the technical composition of SAP Environmental Compliance and the interaction between the components application, database, and Business Warehouse: SAP EC (application) Extraction Layer SAP EC BW Database Note that the extraction layer of the application has bi-directional (read and write) access regarding the database but it can only transfer data from the application (database) into the Business Warehouse. It is not possible to import data from the Business Warehouse into the application (database). The use of the Business Warehouse component of the product is optional. The product can be used without implementing the Business Warehouse part. The Business Warehouse part just serves as a reporting method for SAP Environmental Compliance data SAP SE or an SAP affiliate company. All rights reserved.

161 SAP EC BW Content The Business Warehouse content of SAP Environment Compliance consists of three BW transports: Namespace transport: The TechniData-specific Business Warehouse namespace. The namespace is necessary for the installation of the Business content. Packages The BW Packages or development classes. All Business content objects are assigned to certain packages. SAP Environmental Compliance BW content This transport contains all BW objects which build the business content of the product. For details about the installation of the business content, see chapter Installing BI Content. The business content is delivered and enhanced with every service pack of the product. In case of errors, a correction transport is created and delivered as patch. The business content consists of the following: InfoAreas and components InfoObjects and their InfoObject catalogs InfoSources InfoCubes and ODS Process Chains InfoSets and MultiProviders Note that the business content does not contain any queries for BW reporting EC Extraction Layer The extraction layer is a java-based framework that uses JDBC to communicate with the database. The extraction layer extracts (reads) and writes data into the database. With regard to the Business Warehouse the extraction framework is responsible for the interaction with the Business Warehouse as well as the transfer of database data into the Business Warehouse System Settings This chapter describes the different steps for establishing the connection between the EC application and the Business Warehouse. Within this chapter, we assume that the SAP Environmental Compliance application and the Business content have been successfully installed. To establish a connection between the application and the Business Warehouse, the steps described in the following chapters have to be carried out SAP SE or an SAP affiliate company. All rights reserved. 161

162 EC RFC Setup The RFC setup on SAP NetWeaver Web application side has to be done first in the NetWeaver Administration (NWA) and then on the EC side. To set up the RFC destination in the NWA, proceed as follows: 1. Log into the NWA ( as SAP NetWeaver Admin and navigate to the destinations. 2. In this view, you have to set up the BW RFC connection to the ERP System. Enter the ERP System name as destination (Example BW ) To set up the destination details, see m After finishing the destination setup, you can test the connection by pinging the ERP destination system. 3. Navigate in NWA to Configuration Management Infrastructure JCO RFC Provider and enter as Program ID XEM. This ID is comparable with the old EC 2.0 property bw.extractor.progid ; however, in EC 3.0 this property is not needed anymore. 4. In the next step, enter the RFC Destination Name you have specified in step 2. (Example: BW ) For more information, see m 5. After you set up the JCO RFC Provider, you can start the server in this view. On the EC application side, you have to assign the different modules to the destinations: 1. Log in to EC portal ( with a user that is assigned to the User Group UMEGROUP_Environmental Compliance Admin. 2. Navigate to EC Plant Compliance Configuration Integration RFC Configuration. 3. Now you assign the BW System JCo Destination reference to the newly created destination. 4. In SAP BW, the configuration of the program ID is done within the source system maintenance in transaction SM59. Got to TCP/IP connections XEM. Here you can check the connection between EC and BW. Now the connection between EC and BW is done. Note The RCF destination differs between Unicode systems and Non-Unicode Systems. The Unicode systems should have the flag Unicode in the tab MDMP & Unicode or Unicode : SAP SE or an SAP affiliate company. All rights reserved.

163 Basic Functionality As mentioned above, the extraction layer is a Java-based framework, which is included in the SAP Environmental Compliance application. The extraction of data into the BW requires a successful connection between the application and the BW as well as an active extraction server. The extraction layer performs the following operations: Data extraction from the database Data conversion of database data into BW compliant data structures BW request processing. A BW request is launched by executing an InfoPackage. This request is analyzed and processed. Data transfer into the BW The connection between the application and the BW is based on RFC. The extraction layer uses the RFC enabled BAPIs for the interaction and the data transfer with the BW. With the use of the SAP Java Connector (JCO), you can call the RFC BAPIs in Java. The extraction layer is only able to handle certain BW requests. A BW request is launched by starting an InfoPackage, which itself belongs to an InfoSource. Therefore, we can say that the extraction framework is only able to process the data transfer for certain InfoSources. The manageable InfoSources are stored in a central registry in the extraction framework. There are several extractor classes that are responsible for the data extraction of these InfoSources. The registry stores the InfoSources and their corresponding extractor classes, such as the facility extractor class is responsible for the data extraction of facility master data and facility text data BI InfoProviders This chapter describes the Business Warehouse content for SAP Environmental Compliance from a process view. It shows all InfoProviders such as InfoCubes and ODS as well as master data bearing InfoObjects and InfoObjects with hierarchies. In addition, the Business Warehouse data flow of these objects is explained to provide an overview of the functionality of the business content. The description of the process chains will finalize the explanations Parameter Values as Master Data Attributes In SAP Environmental Compliance, you can maintain multiple parameters per facility. There is no limit for the number of parameters for one facility. To support different customer installations of SAP Environmental Compliance, the BW model has to retain this flexibility. The following documentation explains the parameter value mechanism for the facility. For the different Parameter Value Master Data Attributes Container (e.g. Material), adapt the explanation to your needs. Because of this, the parameters with their respective values are extracted as master data attributes of the InfoObject /TDAG/PVFACILI. Each parameter value is stored as one master data record of this InfoObject SAP SE or an SAP affiliate company. All rights reserved. 163

164 Since each value of InfoObject /TDAG/PVFACILI has to uniquely identify one master data record these values are created as a combination of up to three components: Facility ID Parameter ID Material ID in case of parameter sets These components are concatenated separated by a slash ( / ). For facility parameters, the first component is the facility ID. For material parameters, the first component is the material ID. Parameter sets can have multiple values, one value per emission material. For parameter sets, the ID of the emission material is used as the third component of the key value in the master data table Example 1 /TDAG/PVFACILI - Facility - Parameter Value / / / / / /0 These are the generated key values of three master data records for the InfoObject /TDAG/PVFACILI. They belong to three different parameters of the facility with ID The IDs of the three parameters are , , and respectively. These are not parameter sets; therefore, the third component of the key values is 0. Example 2 /TDAG/PVFACILI - Facility - Parameter Value / / / / / / These key values belong to one parameter set of the facility with ID The ID of the parameter set is The third component of the key values shows the ID of the emission material for which the corresponding value of the parameter set is valid SAP SE or an SAP affiliate company. All rights reserved.

165 Displaying Parameter Values on Reports The following options exist in order to display the parameter values on reports: One parameter per row, for example, multiple rows per facility Multiple parameters per row, for example, one row per facility One Parameter per Row This is the easiest option for having one parameter per row; however, rows are multiplied this may cause problems in the reporting. The solution can be achieved by the following way: 1. Create an InfoSet for the InfoCube (i.e. Emission Cube /TDAG/EM_C01) you want to report for. 2. Add the Parameter Value Master Container (/TDAG/PVFACILI). 3. Connect the facility (TDAG/FACILITY) with the Referencing Object ID (/TDAG/PVREFID) of the Parameter Value Master container. As a result, the InfoSet contains the following records: Facility Parameter Value Object ID Parameter Overview Parameter Value Parameter Value Unit ,00E+01 KW ,00E+01 KW ,00E+01 KW ,00E+01 KW ,40E+02 TO ,40E+02 TO ,40E+02 TO ,40E+02 TO ,00E+01 TO ,00E+01 TO ,00E+01 TO ,00E+01 TO Multiple Parameters per Row The described master data table contains one parameter per record. That means, when a facility has multiple parameters, these parameters are distributed over multiple master data records. To print these parameters in one row on the report, it is necessary to combine these multiple master data rows into one. This can be achieved in the following way: 1. Create a new InfoObject for each parameter that should be displayed on the report and add these new InfoObjects to a DSO. 2. Implement a transformation routine in the transformation that populates the DSO. The transformation routine reads the required parameters from the master data table of InfoObject /TDAG/PVFACILI and copies them into the DSO SAP SE or an SAP affiliate company. All rights reserved. 165

166 The transformation routine can identify the master data records to copy via the following master data attributes of /TDAG/PVFACILI: /TDAG/PVREFID - Parameter Value - Referencing Object ID /TDAG/PARAM - Parameter Overview /TDAG/PVMATID - Parameter Value - Material ID The master data attribute /TDAG/PVREFID contains the ID of the facility (or the material) to which the parameter belongs in SAP Environmental Compliance. The master data attribute /TDAG/PARAM contains the parameter ID. The master data attribute /TDAG/PVMATID contains the ID of the emission material to which a parameter value belongs in case of a parameter set. Alternatively, the master data records can be identified via their respective key value. In that case, the transformation routine has to create the key values as concatenated values in the same way as described above. This has the advantage that the primary key index of the master data table is used to select the records. Example The InfoObject /TDAG/PVFACILI has the following master data records: /TDAG/PVFACILI /TDAG/PVREFID /TDAG/PARAM /TDAG/PVVALUE / / / / / / / / / / / / The DSO contains the facility InfoObject /TDAG/FACILITY and the emission values in /TDAG/EMIVALUE. The parameter values should be copied into the new InfoObjects in the following way: o Parameter InfoObject ZPVAL1 o Parameter InfoObject ZPVAL2 o Parameter InfoObject ZPVAL3 So the DSO contains the following InfoObjects: /TDAG/FACILITY ZPVAL1 ZPVAL2 ZPVAL3 /TDAG/EMIVALUE For each record that is transferred to the DSO, the transformation routine determines the facility ID and reads the corresponding master data records from the master data table of InfoObject /TDAG/FACILITY. The parameter IDs in these records are used to identify the correct parameter value for each of the InfoObjects ZPVAL1 through ZPVAL3. So the transformation routine reads the parameter values from the identified master data records and copies them to the respective InfoObject in the DSO record SAP SE or an SAP affiliate company. All rights reserved.

167 As a result of the transformation the DSO contains the following records: /TDAG/FACILITY ZPVAL1 ZPVAL2 ZPVAL3 /TDAG/EMIVALUE Calculation Parameter for Emissions For emissions, you can also extract the calculation parameter that the emission was calculated with. You use the Extraction Mapping for Calculation Variable dialog under the menu configuration item integration to configure the mapping between SAP Environmental Compliance calculation variables and map them with the created Business Warehouse Info Objects. To do so, the following parameters are required: Variable Name: The name of the calculation parameter this can be a variable defined inside the script or a referenced Parameter from the Input Interface in the user interface. Also parameter sets are supported. Mapping for Value in BI: This is the technical Info Object the value of the parameter shall be extracted to. Note: To have the unit of the calculation value there must be also an Info Object with the same name as the value and a postfix of U. Mapping for Uncertainty in BI: This refers to the Info Object for the uncertainty (always in percent) of the parameter. Example The Extraction Mapping for Calculation Variable table looks like this: Variable Name BW Value Field BW Uncertainty Field EF EFACTOR EFACTOR_UNC EnContent ENERGY_CONT EFactor EFACTOR EFACTOR_UNC Then the referring BI Objects has to be named this way: Value in BI Value Unit in BI Uncertainty in BI (always in %) EFACTOR EFACTORU EFACTOR_UNC ENERGY_CONT ENEGRGY_CONTU EFACTOR EFACTORU EFACTOR_UNC If the setup is done, the relevant BI Objects have to be added to the Emission InfoSource (/TDAG/EM_1) and its transfer rule to get filled with the next data load. Once the InfoSource has been adapted, the ODS Emission (/TDAG/EM_DS01) can be setup in the way that the parameters can be stored there. Finally, the InfoCube (/TDAG/EM_C01) needs to be adapted by adding these parameter objects them for. With this setup, every 2017 SAP SE or an SAP affiliate company. All rights reserved. 167

168 emission value that was calculated with one of the variable names defined in the Extraction Mapping for Calculation Variable dialog is filled with the according value, unit and uncertainty, if configured. Note If you want to report these calculation variables for emissions created prior to SAP Environmental Compliance 3.0 SP9, you have to recalculate all affected consumptions. After a successful recalculation, the database contains the required information and the calculation parameter can be extracted to the Business Warehouse with an Init Load of the Emission InfoSource (/TDAG/EM_1) Master Data Bearing InfoObjects The business content of SAP Environmental Compliance provides several master data InfoObjects. There are two different kinds of master data: fixed and configurable. The fixed master data includes the InfoObjects Facility, Material, Task and Exception. The configurable master data includes the InfoObjects UDF, Identifier and Classifier. For detailed information about configurable master data InfoObjects, see chapter Expandable Parts of SAP EC and SAP EC BW Content. The following tables provide an overview of the different InfoObjects, their usage, and their properties. Container Principle Because of the number of characters of an InfoObject in BW is limited to 4076, all the information that refers to the same object (for example the facility) cannot be stored in one single InfoObject. For this reason, further InfoObjects called containers are used. There are two containers which refer to the InfoObject /TDAG/FACILITY: the container /TDAG/FACIC for classifiers and identifiers and the container /TDAG/FACUDF for UDFs. The InfoObject /TDAG/FACILITY and the container InfoObjects are identified by the same technical key the facility ID. Therefore, the different master data records can be linked together. For every container InfoObject, a template InfoObject is implemented. You have two ways of using this InfoObject. First, you can use the already existing template InfoObject. Note that with new updates of the SAP BI Content, you have to merge the BI content; otherwise, the custom changes are overwritten by SAP standard changes. Second, you can use a copy of the existing template InfoObject. In this case, it is important that the BI content (InfoSource, Update Rules, and InfoProvider) that is affected by this change, has to be adapted to the new InfoObject (see data flow in chapter Expandable Parts of SAP EC and SAP EC BW Content). Container in Details The facility container InfoObjects /TDAG/FACILITY, /TDAG/FACIC, /TDAG/FACMATCL and /TDAG/FACUDF are described in the following table: Facility Master Data InfoObject Usage /TDAG/FACILITY This InfoObject stores the master data of facilities. It also stores deleted facilities, these master data records are marked with the attribute /TDAG/DELETED so that the record can be identified whether it refers to a deleted facility or not, e.g. when performing master data reporting this option is quite helpful SAP SE or an SAP affiliate company. All rights reserved.

169 Attributes Properties Data flow Database table Facility type, Fac. responsible, source category, unit, division, region, country, legal entity, legal structure, work area, location, equity share, facility status, cost center, facility active, data record status, geo coding information, equipment and functional location Time dependent Hierarchies and texts Geo coding enabled Export data source Full load EM_ESOURCE InfoObject Usage /TDAG/FACIC This container InfoObject stores identifiers and classifiers of the facility. It is a template and can be copied for use. For information on configuration of identifiers and classifiers in the EC system for BW, see chapter Facility / Material Identifier and Classifier and Material Groups. Within the Facility Detail you can assign identifier and classifiers. Attributes Properties Data flow Remarks Time dependent Template Full load See chapter Facility / Material Identifier and Classifier and Material Groups for the correct usage of facility identifiers and classifiers. InfoObject Usage /TDAG/FACMATCL This container InfoObject stores consumption material classifiers. For information on the configuration of identifiers and classifiers in the EC system for BW, see chapter Facility / Material Identifier and Classifier and Material Groups. Within the Facility Detail you can assign identifier and classifiers. Attributes Properties Data flow Remarks Time dependent Template Full load See chapter Facility / Material Identifier and Classifier and Material Groups for the correct usage of facility identifiers and classifiers SAP SE or an SAP affiliate company. All rights reserved. 169

170 InfoObject Usage Attributes Properties Data flow Remarks /TDAG/FACUDF This container InfoObject can store facility UDF information. It can be used as a template for the storage of facility UDF data and should be copied or adapted for use. For information on configuration of UDF data fields (also the LOV items configuration) in the EC system, see chapter User-Defined Fields for Master Data in BW. Area identifier Time dependent Template Full load See chapter User-Defined Fields for Master Data in BW for the correct usage of UDF in the BW. Task Master Data InfoObject Usage Attributes Properties Data flow Database table Remarks /TDAG/TASK This InfoObject stores the master data of task instances. In the application, open the task manager in order to maintain or create task instances of task templates. Task instances can also be found within the history tab of a task template; there you can see all instances which belong to the template. Task name, task category, task sub category, priority, status, due date, end date, task status in percent, time status, task template, BW record status Time dependent Texts Delta load EM_TSK_INSTANCE Delta loading of master data In addition, the task master data InfoObject /TDAG/TASK has a container InfoObject for task UDFs, the container /TDAG/TASKUDF. The InfoObject /TDAG/TASK as well as the container InfoObject /TDAG/TASKUDF are identified by the same technical key, the task ID. Therefore, the different master data records can be linked together. The container InfoObject /TDAG/TASKUDF is also a template InfoObject. Either use this template for the UDFs or copy it for use. For pros and cons of these options, see the Container Principle in the facility InfoObject description. The task container InfoObject /TDAG/TASKUDF is described in the following table: SAP SE or an SAP affiliate company. All rights reserved.

171 InfoObject Usage Attributes Properties Data flow Database table Remarks /TDAG/TASKUDF This container InfoObject stores UDF information of tasks. The InfoObject functions as a template for new UDF task InfoObjects and can be copied for use. For information about how to configure the UDF data fields in the EPM System for BW, see chapter User-Defined Fields for Master Data in BW. After successful configuration, the UDF fields can be accessed within the maintenance of a task. Area identifier Template Delta load TD_UDF* For more information, see chapter User-Defined Fields for Master Data in BW. Material Master Data InfoObject Usage Attributes Properties Data flow Database table /TDAG/MATERIAL This InfoObject stores the material master data. Within the material manager of the application, it is possible to maintain or create materials. The material data is transferred as master data into the BW. Material type, CAS number, material number, material parameter 1 2, R3 Reference material, BW data record status Texts Full load EM_MATERIAL The material master data InfoObject /TDAG/MATERIAL has a container InfoObject for material identifiers and classifiers, the container /TDAG/MATIC and a container InfoObject for material groups, the container /TDAG/MATGRPS. They are identified by the same technical key the material ID. Therefore, the different master data records can be linked together. The container InfoObjects /TDAG/MATIC and /TDAG/MATGRPS are also template InfoObjects. Either use this template or copy it for use. For pros and cons of these options, see the Container Principle in the facility InfoObject description SAP SE or an SAP affiliate company. All rights reserved. 171

172 The material container InfoObjects /TDAG/MATIC and /TDAG/MATGRPS are described in the following table: InfoObject Usage /TDAG/MATIC This container InfoObject stores material identifier and classifiers. The assignment of material identifiers and classifiers is done within the material manager of the application. For information about the configuration of identifiers and classifiers in the EC system, see chapter Facility / Material Identifier and Classifier and Material Groups. Attributes Properties Data flow Database table Remarks Template Full load EM_MAT_IDENT EM_MAT_CLASS For more information, see chapter Facility / Material Identifier and Classifier and Material Groups. InfoObject Usage Attributes Properties Data flow Database table Remarks /TDAG/MATGRPS This container InfoObject stores material groups. The assignment of material groups is done within the material manager of the application. The material groups are configured as LOV items. For information on the configuration of groups in the EC system, see chapter Facility / Material Identifier and Classifier and Material Groups. Material, Material group Template Full load EM_FACT (Material groups) EM_MAT_X_GRP(Assignment material to material group) For more information, see chapter Facility / Material Identifier and Classifier and Material Groups. Exceptions InfoObject Usage Attributes Properties Data flow /TDAG/EXCEPT This InfoObject stores the exception master data. Access the exception log of the application to maintain or create exceptions. The information from there is transferred to the BW. Type, assessment, assignee 1-5, state, report date and time, initiator, date from, date to, time from, time to, exception cause, correction action, notes Texts Delta load SAP SE or an SAP affiliate company. All rights reserved.

173 Database table Remarks EM_EXCEPTION Delta load of master data The exception master data InfoObject /TDAG/EXCEPT has a container InfoObject for exception UDFs, the container /TDAG/EXCPTUDF. They are identified by the same technical key, the exception ID. Therefore, the different master data records can be linked together. The container InfoObject /TDAG/ EXCPTUDF is also a template InfoObject. Either use this template for the UDFs or copy it for use. For pros and cons of these options, see the Container Principle in the facility InfoObject description. The exception container InfoObject /TDAG/EXCPTUDF is described in the following table: InfoObject Usage Attributes Properties Data flow Database table Remarks /TDAG/EXCPTUDF This container InfoObject stores UDF information of exceptions. The InfoObject functions as a template for new UDF exception InfoObjects and can be copied for use. For information on configuration of UDF data fields in the EC system, see chapter User-Defined Fields for Master Data in BW. After a successful configuration, the UDF fields can be accessed within the maintenance of an exception. Area identifier Template Delta load TD_UDF* For more information, see chapter User-Defined Fields for Master Data in BW. Limit Master Data InfoObject Usage Attributes /TDAG/LIMIT This container stores the Limit master data. It stores the definition of limits that could trigger Limit Reports (EM_C07) All Limit master data attributes Properties Data flow Database table Full Load EM_REQ_LIMIT Remarks 2017 SAP SE or an SAP affiliate company. All rights reserved. 173

174 Parameter Overview InfoObject Usage Attributes /TDAG/PARAM This container stores the parameter definition data. It contains what type a parameter is defined as, the default unit and the default value if maintained in the EC Source System. Parameter master data Properties Data flow Database table Full Load EM_PARAM Remarks Facility Parameter Values InfoObject Usage Attributes /TDAG/PVFACILI This container holds all Facility parameter values. The facility parameter values Properties Data flow Database table Remarks Full Load EM_PARAM_VALUES See Principle of Parameter Value Definition in the beginning of this chapter for usage details. Material Parameter Values InfoObject Usage Attributes /TDAG/PVMATERI This container holds all Material parameter values The material parameter values Properties Data flow Database table Remarks Full Load EM_PARAM_VALUES See Principle of Parameter Value Definition in the beginning of this chapter for usage details SAP SE or an SAP affiliate company. All rights reserved.

175 InfoObjects with Hierarchies In SAP Environmental Compliance, Only the InfoObject /TDAG/FACILITY has hierarchies. There are two types of hierarchies implemented: Facility Hierarchy: The facility hierarchy consists of facility elements and folders. For reporting, this hierarchy can be used as a method to aggregate data from a lower level of the hierarchy to a higher level. This is only possible if the query is using the hierarchy display for the InfoObject /TDAG/FACILITY. If this hierarchy is used, the hierarchy levels are not available as master data and so they cannot be used for filtering on hierarchy level. Furthermore, the levels have no connection between each other without the facility. External Hierarchy: For the external hierarchy or flex-hierarchy, every layer of the hierarchy has to be configured in a separate InfoObject. These InfoObjects have to be attributes of the facility InfoObject /TDAG/FACILITY and are extracted as master data. In this case, the hierarchies cannot only be used for displaying, but also for filter characteristics. For more information on hierarchies, see chapter Master Data Bearing InfoObjects InfoObjects with Texts Texts for InfoObjects are treated differently per configurable InfoObject. For detailed information on the texts of the InfoObjects, see Expandable Parts of SAP EC and SAP EC BW Content and the respective subchapters InfoProviders by Functional Areas In every subchapter, the usage of the InfoProviders, the involved master data bearing InfoObjects, the key definitions of the ODS, adaptation and extension possibilities, are described according to the functional area to which the InfoProviders belong. Functional areas include emissions data and consumptions data. Through the characterization of InfoProviders into functional areas, the user gets an exact summary of all available InfoProviders and their usage Common Properties of All InfoProviders For the reporting of SAP Environmental Compliance data, the business content offers several InfoCubes, two MultiProviders, and two InfoSets. In addition, you can perform master data reporting on the master data bearing InfoObjects as well. The data flow of all InfoCubes is always the same each InfoCube has its own ODS which supports delta loading of transactional data. Within the ODS, the master data lookup is performed in case attributes become historically true SAP SE or an SAP affiliate company. All rights reserved. 175

176 The following figure shows the dataflow of the Consumptions InfoCube in the Business Warehouse: In addition, the InfoProviders cannot be freely extended with new InfoObjects because the extraction layer is only able to handle the transfer structure of the existing InfoSources. Nevertheless, the BW user has some options regarding the adaptation of the InfoProviders. He can add container InfoObjects to all InfoCubes that contain their related parent InfoObject. For example, the Task InfoCube stores the InfoObject /TDAG/TASK and because of that, it is possible to add the container UDF TASK InfoObjects to this InfoCube. The same principle exists for the InfoObjects for the facility, the exception, and the material (see chapter Parameter Values as Master Data Attributes). Reporting of BW data on a daily, weekly, monthly or yearly basis is possible. The transactional data records of the SAP Environmental Compliance application are based on daily records. Therefore, the smallest time frame for the reporting refers to daily values SAP SE or an SAP affiliate company. All rights reserved.

177 Emission Data The following tables list all InfoProviders that store emissions data: InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EM_C01 Emissions Stores all emissions data except the emissions data that refers to facilities that are assigned to a scenario. Emissions data can be maintained within the emissions section of the Facility Builder, where you have access to the emissions data. In addition, you can assign a facility to a scenario; in this case, the facility serves for planning and forecasting and not for storage of real emissions data. Emissions data always refers to a facility. /TDAG/MATERIAL The emission material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/EMIVALUE Emissions value (uncontrolled) /TDAG/EMIVALC Emissions value (controlled) /TDAG/EQUITY Equity share /TDAG/EQS_EMIV Equity Share Emissions value (uncont.) /TDAG/EQS_EMIC Equity Share Emissions value (cont.) Standard data flow over ODS, delta data loading Emissions value ID Custom UDF InfoObjects and Identifier / Classifier InfoObjects and Calculation Variables can be added. Only emissions data of facilities that are not assigned to a scenario are stored in this InfoCube. EM_EMISSION_RES EM_ESOURCE InfoProvider Usage Master data InfoObjects /TDAG/EM_C01A Emissions Scenarios Stores all emissions scenarios data except the emissions data that refers to facilities that are not assigned to a scenario. /TDAG/MATERIAL The emission material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material () /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) 2017 SAP SE or an SAP affiliate company. All rights reserved. 177

178 Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EMIVALUE Emissions value (uncontrolled) /TDAG/EMIVALC Emissions value (controlled) /TDAG/EQUITY Equity share /TDAG/EQS_EMIV Equity Share Emissions value (uncont.) /TDAG/EQS_EMIC Equity Share Emissions value (cont.) Standard data flow over ODS, delta data loading Emissions value ID Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only emissions data of facilities that are assigned to a scenario are stored in this InfoCube. EM_EMISSION_RES EM_ESOURCE InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks /TDAG/EM_C01B Emissions by material classifiers Stores all emissions data except the emissions data which refers to facilities that are assigned to a scenario. In addition, the emissions data records are multiplied according to the number of material classifiers of a material. This has also impacts on the key definitions of the ODS. For further details, see chapter User-Defined Fields for Master Data in BW. /TDAG/MATERIAL The emission material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material () /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/EMIVALUE Emissions value (uncontrolled) /TDAG/EMIVALC Emissions value (controlled) /TDAG/EQUITY Equity share /TDAG/EQS_EMIV Equity Share Emissions value (uncont.) /TDAG/EQS_EMIC Equity Share Emissions value (cont.) Standard data flow over ODS, delta data loading Emissions value id Material classifier type Material classifier Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only emissions data of facilities that are not assigned to a scenario are stored in this InfoCube. Because the emission values are multiplied according to the number of material classifiers of a material, it is not possible to build an overall result over all SAP SE or an SAP affiliate company. All rights reserved.

179 emission records. See chapter User-Defined Fields for Master Data in BW. There you can find a screenshot of a sample query. Database EM_EMISSION_RES EM_ESOURCE InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EM_C01C Emissions by material groups Stores all emissions data despite the emissions data which refers to facilities that are assigned to a scenario. In addition, the emissions data records are multiplied according to the number of material groups of a material. This has also impacts on the key definitions of the ODS. For further details, see chapter User- Defined Fields for Master Data in BW. /TDAG/MATERIAL The emission material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material () /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/EMIVALUE Emissions value (uncontrolled) /TDAG/EMIVALC Emissions value (controlled) /TDAG/EQUITY Equity share /TDAG/EQS_EMIV Equity Share Emissions value (uncont.) /TDAG/EQS_EMIC Equity Share Emissions value (cont.) Standard data flow over ODS, delta data loading Emissions value ID Material group Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only emissions data of facilities that are not assigned to a scenario are stored in this InfoCube. Because the emission values are multiplied according to the number of material groups of a material, it is not possible to build an overall result over all emission records. See chapter User-Defined Fields for Master Data in BW. There you can find a screenshot of a sample query topic. EM_EMISSION_RES EM_ESOURCE 2017 SAP SE or an SAP affiliate company. All rights reserved. 179

180 Consumption Data InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EM_C02 Consumptions Stores all consumption data despite the consumptions data which refers to facilities that are assigned to a scenario. Consumptions data can be maintained within the consumptions section of the Facility Builder, there you have access to the consumptions data. In addition, you can assign a facility to a scenario; in this case, the facility serves for planning and forecasting and not for storage of real consumptions data. Consumption data always refers to a facility. /TDAG/MATERIAL The consumption material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/CONVALUE Consumptions value /TDAG/EQUITY Equity share /TDAG/EQS_CONV Equity Share consumptions value /TDAG/CPAR1 Consumptions parameter value 1 /TDAG/CPAR1 Consumptions parameter value 2 Standard data flow over ODS, delta data loading Consumptions value ID Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only consumptions data of facilities that are not assigned to a scenario are stored in this InfoCube. EM_ES_DATA EM_ESOURCE InfoProvider Usage Master data InfoObjects Key figures /TDAG/EM_C02A Consumptions Scenario Stores all consumptions scenario data despite the consumptions data which refers to facilities that are not assigned to a scenario. /TDAG/MATERIAL The consumption material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/CONVALUE Consumptions value /TDAG/EQUITY Equity share SAP SE or an SAP affiliate company. All rights reserved.

181 /TDAG/EQS_CONV Equity Share consumptions value /TDAG/CPAR1 Consumptions parameter value 1 /TDAG/CPAR1 Consumptions parameter value 2 Data flow ODS key definitions Expandable Remarks Database Standard data flow over ODS, delta data loading Consumptions value ID Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only Consumptions data of facilities that are assigned to a scenario are stored in this InfoCube. EM_ES_DATA EM_ESOURCE InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks /TDAG/EM_C02B Consumptions by material classifiers Stores all consumptions data despite the consumptions data which refers to facilities that are assigned to a scenario. In addition, the consumptions data records are multiplied according to the number of material classifiers of a material. This has also impacts on the key definitions of the ODS. For further details, see the document Configurable LOV items. /TDAG/MATERIAL The consumption material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/CONVALUE Consumptions value /TDAG/EQUITY Equity share /TDAG/EQS_CONV Equity Share consumptions value /TDAG/CPAR1 Consumptions parameter value 1 /TDAG/CPAR1 Consumptions parameter value 2 Standard data flow over ODS, delta data loading Consumptions value ID Material classifier type Material classifier Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only consumption data of facilities that are not assigned to a scenario are stored in this InfoCube. Because the consumption values are multiplied according to the number of material classifiers of a material, it is not possible to build an overall result over all consumption records. See the document Configurable LOV items. There you can find a screenshot of a sample query SAP SE or an SAP affiliate company. All rights reserved. 181

182 Database EM_ES_DATA EM_ESOURCE InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EM_C02C Consumptions by material groups Stores all consumption data despite the consumptions data which refers to facilities that are assigned to a scenario. In addition, the consumptions data records are multiplied according to the number of material groups of a material. This also has impacts on the key definitions of the ODS. For further details, see the document Configurable LOV items. /TDAG/MATERIAL The consumption material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/CONVALUE Consumptions value /TDAG/EQUITY Equity share /TDAG/EQS_CONV Equity Share consumptions value /TDAG/CPAR1 Consumptions parameter value 1 /TDAG/CPAR1 Consumptions parameter value 2 Standard data flow over ODS, delta data loading Consumptions value ID Material group Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Only consumptions data of facilities that are not assigned to a scenario are stored in this InfoCube. Because the consumption values are multiplied according to the number of material groups of a material, it is not possible to build an overall result over all consumption records. See the document Configurable LOV items. There you can find a screenshot of a sample query. EM_ES_DATA EM_ESOURCE SAP SE or an SAP affiliate company. All rights reserved.

183 Tasks InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EM_C04 Tasks Stores all tasks data. This InfoCube stores the task instances according to the ODS key definitions. For reporting, a task counter is available as key figure. Within task management, you can maintain the task instances. The data of these task instances is transferred to the BW as well as a task counter, which counts the number of tasks, e.g. the number of tasks of type consumptions tasks. /TDAG/TASK Task master data /TDAG/TASKUDF TASK UDF data (sample) /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/TASKCNT The task counter /TDAG/REQCNT The number of requirements Standard data flow over ODS, delta data loading /TDAG/TASK /TDAG/FACILITY /TDAG/REQUIRE /TDAG/TASKOWN /TDAG/TASKRESP Custom TASK and Facility UDF InfoObjects can be added. Task instances are stored in the Task InfoCube. EM_TSK_INSTANCE Measurements InfoProvider Usage Master data InfoObjects Key figures /TDAG/EM_C05 Measurements Stores all measurements data. You get access to the measurement data through the use of the Emission Management. There you find a separate section called measurements. /TDAG/MATERIAL The measurement material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/MVALUE Measurement value 2017 SAP SE or an SAP affiliate company. All rights reserved. 183

184 Data flow ODS key definitions Expandable Standard data flow over ODS, delta data loading Measurement value ID Custom facility and material UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Remarks Database EM_ES_MEASURE EM_ESOURCE InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/EM_C05B Measurements by material classifiers Stores all measurements data. Note that the measurement data records are multiplied according to the number of material classifiers of a material. This also affects the key definitions of the ODS. For further details, see the document Configurable LOV items. /TDAG/MATERIAL The measurement material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/MVALUE Measurement value Standard data flow over ODS, delta data loading Measurement value ID Material classifier type Material classifier value Custom Facility and material UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Because the measurement values are multiplied according to the number of material classifiers of a material, it is not possible to build an overall result over all measurement records. See the document Configurable LOV items. There you can find a screenshot of a sample query. EM_ES_MEASURE EM_ESOURCE InfoProvider Usage /TDAG/EM_C05C Measurements by material groups Stores all measurements data. Note that the measurement data records are multiplied according to the number of material groups of a material. This has also impacts on the key definitions of the ODS. For further details, see the document Configurable LOV items SAP SE or an SAP affiliate company. All rights reserved.

185 Master data InfoObjects Key figures Data flow ODS key definitions Expandable Remarks Database /TDAG/MATERIAL The measurement material /TDAG/MATIC Material identifier and classifier /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/MVALUE Measurement value Standard data flow over ODS, delta data loading Measurement value ID Material classifier type Material classifier value Custom Facility and material UDF InfoObjects and Identifier / Classifier InfoObjects can be added. Because the measurement values are multiplied according to the number of material groups of a material, it is not possible to build an overall result over all measurement records. See the document Configurable LOV items. There you can find a screenshot of a sample query. EM_ES_MEASURE EM_ESOURCE Exceptions InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions /TDAG/EM_C06 Exceptions Stores all exceptions data. This InfoCube stores the exceptions according to the ODS key definitions. For reporting, an exception counter is available as key figure. Within the Exception Log of the application, you get access to the exception data. The transactional exception data includes an exception counter in order to perform count operations on exception data, e.g. all exceptions of type fire. /TDAG/EXCEPT Exception master data /TDAG/EXCPTUDF Exception UDF data (sample) /TDAG/FACILITY The facility that emits the material /TDAG/FACIC Facility identifier and classifier /TDAG/FACUDF Facility UDF data (sample) /TDAG/EXCNT The task counter /TDAG/REQCNT The number of requirements Standard data flow over ODS, delta data loading /TDAG/EXCEPT /TDAG/FACILITY 2017 SAP SE or an SAP affiliate company. All rights reserved. 185

186 /TDAG/REQUIRE Expandable Remarks Database Custom Exception and Facility UDF InfoObjects can be added. Up to five exception assignees are stored in the BW. EM_EXCEPTION InfoProvider Usage Master data InfoObjects Key figures Data flow ODS key definitions /TDAG/EM_C07 Limits Reports Stores all Limit Reports that were created after EC3.0 SP9. This InfoCube stores all limit reports that were created by the limit scheduler after EC3.0 SP9 was implemented in the source system. With the Permit Application, you can also check these limits in the EC System. /TDAG/LIMIT The limit master data that this limit report was triggered from /TDAG/LMRCOUNT - The number of limit reports /TDAG/LMRCHKVA The value that was checked /TDAG/LMRTHRVA The threshold value /TDAG/LMRRPTUA The threshold upper amount /TDAG/LMRRPTLA The threshold lower amount Standard data flow over ODS, delta data loading /TDAG/LMRID Limit Report ID (from EC) Expandable Remarks Database EM_LIMIT_REPORT MultiProvider for Emissions and Consumptions There are two MultiProviders for the comparison of emissions data and consumptions data. There is one for comparing the emission and consumptions values of facilities that are not assigned to a scenario and the other one is for the comparison of emission and consumption data of facilities with scenarios only. Note that the Business Warehouse performs a union of the data records of the emissions and the consumptions InfoCubes and not a join InfoSets for Master Data Reporting As introduced in chapter Parameter Values as Master Data Attributes, the facility master data and the material master data are spread over different InfoObjects. The facility master data is stored in the InfoObjects: SAP SE or an SAP affiliate company. All rights reserved.

187 /TDAG/FACILITY /TDAG/FACUDF ( + additional custom UDF InfoObjects) /TDAG/FACIC ( + additional custom InfoObjects) The material master data is stored in the InfoObjects: /TDAG/MATERIAL /TDAG/MATIC ( + additional custom InfoObjects) /TDAG/MATGRPS The InfoSets combine the separated master data InfoObjects so that master data reporting is possible over the complete master data, if required. Note that InfoSets technically perform a left-outer join of data. The two InfoSets use the facility or the material ID for the linkage between the different master data bearing InfoObjects. In addition, the InfoObjects /TDAG/FCLASSES, /TDAG/MCLASSES and /TDAG/MATGRPS are also part of their InfoSets. The linkage of these InfoObjects is also done through the use of the facility or the material ID Process Chains The SAP Environmental Compliance business content also contains process chains for the scheduling of the data loading into the Business Warehouse. The composition of the process chains is the following: Separate process chains for loading master data and transactional data, e.g. the facility master data load has an own process chain as well as the loading of task master data. For every InfoCube, there is a delta and an init process chain. All master data is loaded with the process chain master data and hierarchies. All texts are loaded with the process chain EM Texts. There are two meta chains that execute all other process chains. These two chains ensure that the master data is loaded before the transactional data is loaded. In addition, the data load stops in case there is an error loading the master data. Through this, it is ensured that the quality of the transactional data records is correct when they are loaded into the BW. Remove unneeded process chains from these meta chains to avoid problems for the all meta chains Expandable Parts of SAP EC and SAP EC BW Content There are two different approaches for extending the extraction functionality. Depending on the requirements it needs to be determined if the business case can be customized using the configuration or needs a custom extractor (development). Configuration One of the concepts is the usage of user-defined fields for facility, task or exception data. Another one is the usage of facility / material identifier and classifiers as well as material groups. The third configurable part is the hierarchies. The concepts are explained in the following subchapters. Development (JAVA) It is possible to develop custom java-based BW extractors that can transfer data from the database into the Business Warehouse SAP SE or an SAP affiliate company. All rights reserved. 187

188 In addition, there are some generic concepts regarding the extraction of EC data into the Business Warehouse User-Defined Fields for Master Data in BW Since each customer is unique and with specific requirements, it is absolutely necessary to enable the EC system to be more freely configurable. The user-defined fields (UDF) offer a lot of flexibility in customizing the EC content in regard to facilities, tasks, exceptions and emission accounting. Note that the UDF values only extend the characterization of the existing InfoObjects Facility, Task and Exception, other InfoObjects might follow later. In the following text, EC content always refers to facility, task and exception. With the use of UDFs, customers can adapt the EC content to their needs and wishes by modeling their own UDF InfoObjects to store additional data. The configuration performed in the EC application must refer to the appropriate InfoObject and BW fields that have been designed before. In addition, with EC, you can use UDF fields for non-bw relevant topics. It is possible to create UDFs for the Document Management Search Plug-ins. This means that besides the domains facility, task, exception and emission accounting there might be other available domains. This document only focuses on the BW-relevant facts in regard to facilities, tasks and exceptions. These UDF fields are not extracted to BW. The different chapters explain in detail all the important facts concerning the use of UDFs in the Business Warehouse of EC. Configuration of UDF in EC SAP Environmental Compliance distinguishes between two essential facts, the configuration of the UDF data fields (configuration of the EC: Configuration User Defined Fields Assignments) and the configuration of the List of Values (LoV). UDF Configuration The configuration of the UDF data fields means the interaction between the extractors and the corresponding UDF InfoObjects. There are extractors for master data and for delta enabled data, they are identified through the suffix _M indicating that the data is of type Master data and _D for delta data. For a correct configuration, we have to set the InfoSource followed by the extractor suffix in the EC application field BW InfoSource. We also have to set the BW Name with the name of the InfoObject. LoV Configuration In order to extract the textual information, the InfoObjects of type UDF Picklist have to be configured under the EC menu entry List of Values. There the customer must set the BW Data Source and the corresponding BW fieldname of the InfoObjects of type UDF Picklist to enable the interaction between the extractors and the Business Warehouse. These extractors are identified through the suffix _T indicating that the data is of type Text. Note A new configuration requires a restart of registered extractors SAP SE or an SAP affiliate company. All rights reserved.

189 InfoObjects for UDF Functionality As previously mentioned, the UDF container InfoObjects extend the characterization of the existing InfoObjects /TDAG/FACILITY, /TDAG/TASK and /TDAG/EXCEPT. SAP provides several template InfoObjects to which customers must refer in order to create their own InfoObjects. The InfoObject /TDAG/UDF_AREA is a mandatory attribute for creating new UDF InfoObjects. The following figure provides a summary of all template InfoObjects that can be used as attributes (data types): Template InfoObject /TDAG/UDFBOOL /TDAG/UDFINT /TDAG/UDFDOUBL /TDAG/UDFTEXT /TDAG/UDFDATE /TDAG/UDFPICKL /TDAG/UDFCURR /TDAG/UDFCURRC /TDAG/UDFPHYS /TDAG/UDFPHYSU /TDAG/UDF_AREA (mandatory) Description UDF InfoObject specifying the Boolean data type in BW. UDF InfoObject specifying the Integer data type in BW. UDF InfoObject specifying the Double / Float data type in BW. UDF InfoObject specifying the String data type in BW. UDF InfoObject specifying the data format UDF InfoObject specifying the Picklist data type in BW. Configured as List of Value. UDF InfoObject specifying the currency in BW. UDF Unit for currency. UDF InfoObject specifying the data type for physical values in BW. UDF Unit for physical values. Identifies the UDF Area and is used by Facility, Task and Exception The following figure lists three container InfoObjects for /TDAG/FACILITY, /TDAG/TASK, /TDAG/EXCEPT and /TDAG/UDFEMACC. These containers must have the InfoObjects /TDAG/UDF_AREA and at least one of the data types explained in the figure above as attributes. Sample /TDAG/FACUDF /TDAG/TASKUDF /TDAG/EXCPTUDF Description Describes the UDF values for a facility. Consists of: /TDAG/UDF_AREA (mandatory) Describes the UDF values for a task. Consists of: /TDAG/UDF_AREA (mandatory) Describes the UDF values for an exception. Consists of: /TDAG/UDF_AREA (mandatory) 2017 SAP SE or an SAP affiliate company. All rights reserved. 189

190 /TDAG/UDFEMACC Describes the UDF values for an emission account. Consists of: /TDAG/UDF_AREA (mandatory) The container InfoObjects /TDAG/FACUDF, /TDAG/TASKUDF, /TDAG/EXCPTUDF and /TDAG/UDFEMACC shouldn t be changed. They can be used as a template for creating new UDF InfoObjects. If the objects are changed, the BW content installation is more complicated (merging the BW content is required). Therefore, we recommend creating a new custom UDF InfoObject using one of the three sample InfoObjects as a template. Hints and Definitions The modeling in SAP BW should always be performed top to down. This means from the InfoCube to the ODS to the DataSource and so on. When master data is extracted without using a process chain, it has to be activated manually. The customer development must be carried out in customer namespace. The commonly used prefix for the new InfoObjects is Z_ before a describing name. An example for a new InfoObject would be Z_FACUDF (UDF of Facility). Requirements The InfoObject /TDAG/INCGTID is the reference InfoObject of the UDF InfoObject /TDAG/UDFBOOL and stores the multilingual texts of the Boolean values (Yes / No). Make sure that the InfoObject /TDAG/INCGTID stores all necessary texts. The text maintenance has to be performed manually because there is no text data source configured. Maintain the texts of the Boolean values as follows: 1D Ja 1E Yes 2D Nein 2E No Business Warehouse Modeling This chapter describes how to extend the Business Warehouse in order to store the UDF data for facilities, tasks or exceptions. The UDF values (UDF InfoObjects and their attributes) are recorded in the InfoCubes; therefore, it is necessary to add the new InfoObjects to the InfoCubes and update the transfer and update rules so that the UDF data can be stored correctly. The next several subchapters give a precise overview of all necessary steps that have to be performed to create new UDFs in the Business Warehouse. An example follows the explanations. In the following, UDF InfoObjects always refers to the InfoObjects that describe a facility, a task or an exception more detailed; whereas, UDF type InfoObjects are the attributes, e.g. /TDAG/UDFTEXT SAP SE or an SAP affiliate company. All rights reserved.

191 InfoObject Modeling In order to store the data in the BW, we have to model the appropriate InfoObjects that will hold the UDF data. The InfoObjects as mentioned above (UDF data types) have to be used as attributes to create custom UDF InfoObjects for facility, task or exception. The modeling of the InfoObjects consists of two essential facts. First, we have to create the UDF InfoObjects consisting of several attributes that we have described before. Second, we have to design the attributes we want to use in our UDF InfoObjects. Therefore, we take the delivered UDF type InfoObjects. The UDF type InfoObjects are delivered for every UDF type, e.g. /TDAG/UDFDOUBL for double / float values. If customers need more than one InfoObject of the same UDF type, they have to create new InfoObjects in the customer namespace, e.g. create an InfoObject Z_MYUDF. If customers intend to use several physical values or currencies, they have to create the corresponding units separately. Otherwise, all physical values or currencies would have the same unit. Don t forget to set the attributes of UDF InfoObject for Facilities as navigational and time-dependent. For tasks and exception, only the navigation has to be enabled. Note o We strongly recommend creating new UDF type InfoObjects either with reference to the existing UDF type InfoObjects, e.g. Z_UDFBOOL as a reference to the InfoObject /TDAG/UDFBOOL or as a template. Through this, it ensured that new InfoObjects inherit the settings from the existing ones. o The UDF key figures /TDAG/UDFPHYS and /TDAG/UDFCURR have units (/TDAG/UDFPHYSU and /TDAG/UDFCURRC). Customers who want to create more UDF key figures of these types also have to create new units. When creating new key figures using the existing ones as a template, the units are automatically overtaken. These units have to be changed; otherwise, it is not possible to store different units for the key figures. New UDF key figures and their corresponding units are created according to the following naming convention: the technical name of the key figure uses at most 7 chars, the corresponding unit has the identical technical name either followed by a U for units of physical values or a C for units of currencies. The technical naming before the suffix U or C has to be identical; otherwise, the extractors cannot match the values and the units, e.g. /TDAG/UDFCURR and /TDAG/UDFCURRC. o It is not possible to add referenced key figures as attributes to an InfoObject. It is mandatory to create new UDF key figures using existing UDF key figures as a template. InfoCube / ODS Modeling We have to add our newly created UDF InfoObjects to the appropriate InfoCubes and to the ODS according to the following convention: Add all newly created Facility UDF InfoObjects to every Cube / ODS where the InfoObject /TDAG/FACILITY is already stored. Add all newly created Task UDF InfoObjects only to the Task Cube / ODS. Add all newly created Except UDF InfoObjects only to the Exception Cube / ODS. This process has impacts on the corresponding update and transfer rules; therefore, they haven t been updated yet SAP SE or an SAP affiliate company. All rights reserved. 191

192 InfoSource / DataSource / InfoPackage When adding the UDF InfoObjects to the InfoCubes / ODS, the corresponding update rules and InfoSources have to be changed. Therefore, change the InfoSource of the ODS first, so that the update rules can be adapted and reactivated correctly. Note that the transfer rules of the InfoSource have to map the new UDF InfoObjects to their depending parent InfoObjects, e.g. map /TDAG/FACUDF to /TDAG/FACILITY. Never change the data source / transfer rules. In order to get / store all the UDF data, the customer has to create a separate InfoSource for the extraction of the UDF data (e.g. the master data of UDF Facility). The InfoSource is automatically created; therefore, the InfoObject is marked as a data target. For tasks (exception is delta capable in the next Release), it is mandatory to create flexible update rules; therefore, they have to be delta capable. For facilities and exceptions, we create an InfoSource with direct update of master data. Add the EC data source to all newly created InfoSources and define the InfoPackages. Note o It is mandatory that the fieldname of the data source / transfer structure is set to the value DomainID for all the UDF InfoObjects, e.g. in the InfoSource of the InfoObject /TDAG/FACUDF the data source / transfer structure field of /TDAG/FACUDF is set to the value DomainID. The standard value has to be changed. o For the UDF key figures /TDAG/UDFCURR and /TDAG/UDFPHYS, there is no need to change the fieldname in regard to the previously mentioned fact ( DomainID ). The extractors notify the corresponding units according to the naming. o For Picklist, we need a separate InfoSource that loads the texts. Add the EC data source to the InfoSource and create a new InfoPackage for the texts and add this package to the EC text metachains. The delivered InfoSources and InfoPackages can be taken as a template. Process Chains The defined InfoPackages have to be added to the corresponding process chains so that the data is correctly transported from the data source into the Cubes. For Task, we have to create two new process chains - one for init and one for the delta InfoPackage with load the data for the UDF Task attributes. For Facility and Exception, we have to create for each one a new process chain to collect the data for the attributes. Note that Facility, Task or Exception, in this case, means the UDF-related InfoObjects. The new process chain for Task is added to the process chain of the Task Cube. Through this, it is ensured that the Task attributes (not the UDF data) are collected first followed by the UDF data. Afterwards, the InfoPackage of the Task cube is called to load the data into the ODS and in the Cube. The following figure provides a graphical summary: This process is identical for UDF Facility and UDF Exception SAP SE or an SAP affiliate company. All rights reserved.

193 The process chains that are responsible for the master data loading of the other InfoObjects FACUDF and EXCPTUDF is added to the corresponding chains. The Facility UDF chains are added to the master data and hierarchies chain. The Exception UDF chains are added to the Exceptions Init and Delta chain. Note that if customers have several UDF InfoObjects (Facility, Task and Exception), they first have to create a separate process chain for each UDF InfoObject; therefore, these InfoObjects have their own InfoPackages. Second, they have to add these new process chains to the chains of the corresponding cubes. The extension of the existing UDF chains is not required due to the content installation procedures. The following tables give a short summary of the InfoPackages and their process chains: InfoPackage TASKUDF (Delta) TASKUDF (Init) EXCPTUDF (Delta) EXCPTUDF (Init) FACUDF (FULL) EMACCUDF (FULL) Process chain New process chain for collecting the UDF Task master data. New process chain for collecting the UDF Task master data. New process chain for collecting the UDF Exception master data. New process chain for collecting the UDF Exception master data. New process chain for collecting the UDF Facility master data. New process chain for collecting the UDF Emission Accounting master data. Process chain Process chain Chain of TASKUDF (Delta) Chain of TASKUDF (Init) Chain of EXCPTUDF (Delta) Chain of EXCPTUDF (Init) Chain of FACUDF (Full) Chain of EMACCUDF (Full) EM Tasks (Delta) EM Tasks (Init) EM Exceptions (Delta) EM Exceptions (Init) EM Master data and hierarchies EM Emission Accounting UDF Interaction between EC and BW As mentioned in the introduction, data can only be stored in the Business Warehouse if the BW content was modeled beforehand. In order to fill the UDF data fields through the use of EC, we have to configure the BW in the configuration of the EC, e.g. name of BW Source and BW field. Note that the whole process also includes interactions with the database and the extractors. Through the configuration, the EC gets access to the BW and data can be loaded into the ODS and Cubes of the Business Warehouse SAP SE or an SAP affiliate company. All rights reserved. 193

194 The following figure shows a graphical summary of this scenario (simplified): Example The customer wants to create an UDF InfoObject to specify the facility in more detail. The customer wants to create an UDF InfoObject with several attributes. The following steps have to be performed: 1. Create a new InfoObject and use the appropriate InfoObjects (/TDAG/FACUDF, /TDAG/EXCPTUDF and /TDAG/TASKUDF) as a template. Do not take the template and change / add the new attributes. Customers can design the attributes of the InfoObject to their needs, but they should keep all the other settings from the template. 2. Attributes: If the customer intends to use several attributes of the same type, he has to create new InfoObjects as references or templates of the existing ones, e.g. /TDAG/UDFBOOL is the existing UDF type InfoObject that has to be used as draft. Therefore, the customer creates a new Z_* InfoObject and uses the /TDAG/UDFBOOL InfoObject as a reference or as a template. Set the attributes as navigational attributes and as time dependent (only for Facility UDF). 3. Add the UDF InfoObject to the InfoCubes and to the ODS. Take the existing UDF InfoObjects like /TDAG/FACUDF, /TDAG/TASKUDF or /TDAG/EXCPT UDF, which are already added to the corresponding InfoCubes / ODS for orientation. Note that the facility is stored in every InfoCube / ODS so it is necessary to store new UDF InfoObjects that describe the UDF values of a facility in every InfoCube / ODS as well. Add the UDF InfoObjects for Task and Exception only to their corresponding InfoCubes / ODS. When changing the InfoCubes, the corresponding update rules also have to be changed as well as the corresponding InfoSources of the InfoCubes. It is absolutely necessary that the new UDF InfoObjects are mapped to their depending parent InfoObjects when changing the transfer rules of the InfoCubes, e.g. /TDAG/FACUDF is mapped to /TDAG/FACILITY and we will not add /TDAG/FACUDF to the data source so that we are able to map /TDAG/FACUDF to /TDAG/FACUDF. Therefore, we create separate InfoSources that collect all the UDF data and not only the ID. See the next step for details. Through this, it is ensured that the facility stores all the data that belongs to the facility. 4. Create an InfoSource for every UDF InfoObject and assign the EC data source so that data loading from the extractors can be enabled. Note that for Task we need flexible update rules (Tasks are delta capable). Create the InfoPackages for the data source and make sure that, for task, delta update is chosen as update mode. For facility and exception, we use full update as update mode. 5. Create update rules in the InfoProvider for the master data of a task, for facility and exception we do not have to create separate update rules. Make sure that the UDF InfoObjects are available as data targets in the InfoProvider view. If not, check the settings of the InfoObject. It has to be marked as data target. 6. Don t forget to set the data source / transfer structure field of the UDF InfoObjects to the value DomainID, e.g. /TDAG/FACUDF has to be mapped to the field value DomainID and not to the field value /B123/S_FACUDF as set per default SAP SE or an SAP affiliate company. All rights reserved.

195 7. Finally, we have to add our new InfoPackages to the corresponding process chains. For the data extraction of the UDF InfoObjects we have to create new process chains. The process chains have to be added either to the Master Data and Hierarchies chain (UDF for Facility and UDF for exception) or to the Master Data and Transactional Data chains (UDF for Task, delta and init). We recommend using the delivered Objects (InfoObjects, InfoPackages) as templates when creating new BW UDF content. Otherwise, correct functionality cannot be ensured. EC Configuration and Settings This chapter explains in detail the complete workflow of the EC in regard to the BW configuration and the data extraction into the Business Warehouse. Set up the InfoSource Our goal is to set up the UDF Values in EC by configuring the correct InfoSource. The EC UDF Configuration is located under the Configuration Menu, there we select from the left side menu the User-Defined Fields entry. The following screen appears, which is divided in the Areas region and the Assigned Elements region: First, you have to set up the BW Info Source fields (green rectangle) in the Area region. There you have to enter the Info Source name of the BW Info Object that contains the UDF Values itself (i.e. the /TDAG/FACUDF ). It is important to know that you have to enter the type of the extractor in this case as well. There are two different extraction methods for the UDF Values: Delta Extractor ( D ) Master Data Extractor ( M ) You have to add the correct extractor type at the end of the InfoSource separated by an underscore. For example, the correct configuration for /TDAG/FACUDF is: /TDAG/FACUDF_M 2017 SAP SE or an SAP affiliate company. All rights reserved. 195

196 If you are not sure what kind of extractor the single info sources have, refer to the following table: InfoSource /TDAG/FACUDF (UDF Facility) /TDAG/EXCPTUDF (UDF Exception) /TDAG/TASKUDF (UDF Tasks) Extractor Type Full Master Data (_M) Delta Master Data (_D) Delta Master Data (_D) Note o If you are changing or adding a BW InfoSource, you always have to restart your Extraction Server. Otherwise, the changes won t affect the running system. o If you want to configure a new UDF domain, there might be different domains from facility, exception and task, available, such as the Document Management Search. Setting Up the UDF Values Now we have to map the existing (or newly created) UDF Values from the EC to the BW System. Therefore, we have to create a UDF Area. Here you have to enter the BW Keys of the BW Transfer structure to the according UDF Element that was created in EC. Note The transfer structure in the BW also contains a generated namespace, e.g. /B123/S_UDF_AREA. It is mandatory to ignore this namespace when setting the BW Name (red marked rectangle). Example You may use the /TDAG/S_UDFINT value in BW for mapping the EC Integer UDF Value no. oil spills SAP SE or an SAP affiliate company. All rights reserved.

197 Therefore, you have to assign this EC UDF Value to an area that has a valid BW InfoSource. Now map the /TDAG/S_UDFINT by entering the BW Name S_UDFINT in the no. oil spills UDF Value. Based on the configured domain, the UDF input fields are shown on the appropriate tab within the task manager, the exception log, or the facility builder. There, the user can fill the previously configured UDF fields with data. List of Values To extract the textual information, the InfoObjects of type UDF Picklist have to be configured under the EC menu entry List of Values as well. There, the customer must set the BW Data Source and the corresponding BW fieldname of the InfoObjects of type UDF Picklist to enable the interaction between the extractors and the Business Warehouse. These extractors are identified by the suffix _T indicating that the data is of type Text. Remarks Notes for the Business Warehouse This chapter briefly explains the most important facts to be considered during the Business Warehouse modeling. When creating new InfoObjects, either use references (for new UDF type InfoObjects, only for characteristics) or templates (for new UDF InfoObjects and the UDF key figures). Through this, the correct settings of the InfoObject are inherited. Don t forget to enable navigation for all attributes. Only set the attributes of /TDAG/FACUDF as time-dependent. If necessary, change the data target of the InfoObject, e.g. from package /TDAG/CO to Z_MYTEST. When trying to create new UDF key figures with references, these InfoObjects cannot be used as attributes in other InfoObjects. We have to use the template method instead when creating new UDF key figures. Always use existing objects (InfoObjects, InfoSources, InfoPackages...) as samples for creating new objects. It is mandatory to change the field name in the InfoSources of the UDF InfoObjects Facility, Tasks and Exceptions to the value DomainID. The following figure shows a sample of a data source: 2017 SAP SE or an SAP affiliate company. All rights reserved. 197

198 Note The extractors can only determine the ID for UDF Facility, UDF Task and UDF Exception if the fieldname is set to the value DomainID (highlighted in light orange in the figure above). For the UDF key figures with units, the extractors notify the corresponding unit according to the identical technical naming followed by the suffix U for the unit of physical values or a C for the unit of currencies. For example, /TDAG/UDFPHYS is the value and /TDAG/UDFPHYSU is the corresponding unit as you can see at the bottom of the figure above (highlighted in dark orange). There is a limit of 4076 chars for all attributes. This means that an InfoObject can have at most 67 attributes of type char 60. If there is the need to store more attributes, it is necessary to create an additional InfoObject for storing the UDF data. Changes to the cubes have impacts on the update rules of the cube and on the multi cubes. Both objects have to be activated separately. To transfer the data into the cubes, do the following: 1. Add the InfoObjects to the cube. 2. Add the data source EC to the InfoSource of the UDF InfoObject. Create corresponding InfoObjects. 3. Change the InfoSource of the cubes. Map the UDF InfoObject to the corresponding existing InfoObject in the transfer rules. For example, /TDAG/FACUDF is mapped to /TDAG/FACILITY. 4. Add new InfoPackages to the process chains and change exiting process chains, if necessary. Change the data field of the data source / transfer rules in the InfoSource of every UDF InfoObject. To ensure the extractor functions correctly, it is mandatory to set the value to DomainID. We have UDF InfoObjects with several attributes that have been created as references. If changes are applied to the parent InfoObjects, for example through a new patch, the corresponding InfoSources of these objects have to be manually activated and checked for the correct data type and length SAP SE or an SAP affiliate company. All rights reserved.

199 Notes for EC Configuration The EC configuration enables the interaction between EC and the Business Warehouse. The most important facts are listed below: 1. To link the EC with the BW, you must to configure the BW Source and its field names. The data source / transfer structure fieldnames of the delivered UDF type InfoObjects, such as /TDAG/UDFTEXT, have the naming /B123/S_<technical name of InfoObject without /TDAG/ namespace>, for example /B123/S_UDFTEXT. Customer InfoObjects, such as Z_MYUDF, have fieldnames starting with /BIC/ followed by the complete technical name of the InfoObject, for example /BIC/Z_MYUDF. The configuration of EC must use the fieldnames without the identifier /B123/ and /BIC/. In this case, the configuration must point to S_UDFTEXT and to Z_MYUDF in order to store the data in the BW. 2. List of Values (UDF Picklist) has to be configured separately. 3. After changing the configuration, it is necessary to restart registered extractors Setting Up UDFs for Transactional Data in BW To create your own info objects for User-Defined Fields, follow the description in chapter User-Defined Fields for Master Data in BW. Instead of adding these new created info objects to the delivered info objects as attribute, you have to add them to the InfoSource of the according InfoCubes: UDF Domain Consumption Emission Measurements Emission Accounting Transactions InfoCube in BW /TDAG/EM_2 /TDAG/EM_1 /TDAG/EM_5 /TDAG/EM_8 Note The InfoCubes in the list above are the only InfoCubes that supports transactional UDF: Following InfoCube do not support transactional UDF: /TDAG/EM_1A, /TDAG/EM_1B, /TDAG/EM_1C, /TDAG/EM_2A, /TDAG/EM_2B, /TDAG/EM_2C, /TDAG/EM_C5B, /TDAG/EM_C5C. After the InfoSources of this InfoCubes were extended, the dataflow up to the InfoCube (Transfer Rules, ODS and so on) needs to be adapted to transfer get the UDF into the according InfoCube and allow reporting on them SAP SE or an SAP affiliate company. All rights reserved. 199

200 Setting Up UDFs for Transactional Data in EC To setup the extraction of transactional data, such as consumptions, emissions, measurements, and emission accounting transactions, open the Assignments for Transactional Data dialog in Configuration User-Defined Fields. In difference to the master data extraction, there is no need to setup BW InfoSource: The InfoSource added at the additional user-defined fields is predefined. Note If you delete an assignment on the SAP Environmental Compliance side, you also have to remove this assignment on the BW side Facility / Material Identifier and Classifier and Material Groups Material / Facility identifiers are used for more detailed characterization and identification. This means that identifiers offer additional information of a material or a facility. Identifiers are not used for data arrangement in transactional data sets. In contrast, material groups and material / consumption material / facility classifiers can be used for both scenarios. They can be used for data arrangements of transactional data sets as well as for additional information (identification) of a material or a facility. Note that material and facility identifiers and classifiers cannot be mixed. Material identifiers and classifiers can only be assigned to material; whereas, facility identifiers and classifiers can only be assigned to a facility. Material identifiers and classifiers and facility identifiers and classifiers are always separated and do not belong together. The data extraction of facility / material classifiers and material groups to the BW does also work without configuring the BW settings within the LOV dialog. Identifiers cannot be extracted to the BW without a BW configuration. As additional identifying information, classifiers and groups also require a BW configuration within the LOV dialog. With the BW configuration, the classifiers and groups are only extracted into the BW for data arrangement purpose. More details will follow in the next chapters. Important Note: If a system can have multiple classifier values for the same classifier type then you have to maintain a unique BW Field Name in the LOV definition for each classifier value. This is possible with SAP Environmental Compliance 3.0 SP10 and all higher releases. The BW Field Name stands for the object name that the classifier has in BW. With this solution, you have to add the custom info objects in the container that represents the InfoSource name of the classifier type. To configure in BW, proceed as follows: 1. Create an Info Object as a container for the classifier in BW With Master Data. 2. Create an Info Object for the classifier type you want to extract to BW (use reference characteristics /TDAG/CL_TYPE for facility classifier or /TDAG/MCLATY for material classifier). 3. Create Info Objects for each classifier value you want to transfer into BW (use as reference characteristics /TDAG/CLASSIF for facility classifiers or /TDAG/MCLASS for material classifiers). 4. Add the Info Object for the classifier type and the classifier values to the container created in step #1 as an attribute SAP SE or an SAP affiliate company. All rights reserved.

201 To configure in SAP EC, proceed as follows: 1. Maintain the BW Configuration List of Value (LOV) classifier type. The BW Data Source normally represents the container object created in step #1 and the BW Field Name stands for the classifier type created in step #2. 2. For each classifier value, fill in its BW Field name. These are the technical IDs of the Info Objects created in step #3. BW Modeling Custom BW modeling should always be performed in the customer namespace, e.g. Z. Do not apply the delivered InfoObjects from TDAG because this may cause problems when updating the EC BW content to a higher version. In the BW, there is a limit concerning the number of attributes an InfoObject can store. If it is insufficient to store the identifiers, classifiers, and groups in one InfoObject, you can create new container InfoObjects. Use the delivered Template InfoObjects for the creation of custom Identifier / classifier and group InfoObjects as a sample. For the list of template InfoObjects, see the following table Delivered BW InfoObjects The identifiers and classifiers of the material and the facility are stored in separate container InfoObjects /TDAG/MATIC (material identifiers, classifiers, and material groups) and /TDAG/FACIC (facility identifiers and classifiers). As a consequence, it is necessary that the Material InfoObject and the Material Identifier and Classifier InfoObject are linked together. The same requirement exists for the facility. The following list shows all delivered BW InfoObjects that are involved: InfoObject /TDAG/FACILITY /TDAG/FACIC /TDAG/FCLASSES /TDAG/FACMATCL /TDAG/CL_TYPE /TDAG/CLASSIF /TDAG/IDTY /TDAG/IDENT Description Stores the master data of the facility Stores the identifiers and classifiers of a facility Stores all assigned facility classifiers of all facilities Stores all assigned consumption material (facility material classifiers) Template InfoObject for storing a facility classifier. Custom classifier type InfoObjects must be created in the BW with reference to this InfoObject. This InfoObject stores all texts of all classifier types. Template InfoObject for storing a facility classifier value. Custom classifier value InfoObjects must be created in the BW with reference to this InfoObject. This InfoObject stores all texts of all classifier values. Template InfoObject for storing a facility identifier type. Custom identifier type InfoObjects must be created in the BW with reference to this InfoObject. This InfoObject stores all texts of all identifier types. Template InfoObject for storing an identifier value. Can be taken as sample for creating new InfoObject in the BW. Does not store any texts SAP SE or an SAP affiliate company. All rights reserved. 201

202 /TDAG/MATERIAL /TDAG/MATIC /TDAG/MATGRPS /TDAG/MCLASSES /TDAG/MCLATY /TDAG/MCLASS /TDAG/MIDTY /TDAG/MIDENT Stores the master data of the material and up to SP10 also the identifiers and classifiers. Stores the identifiers and classifiers of a material Stores all assigned material groups of all materials. Stores all assigned material classifiers of all materials. Template InfoObject for storing a material classifier type. Custom classifier type InfoObjects must be created in the BW with reference to this InfoObject. This InfoObject stores all texts of all classifier types. Template InfoObject for storing a material classifier value. Custom classifier value InfoObjects must be created in the BW with reference to this InfoObject. This InfoObject stores all texts of all classifier values. Template InfoObject for storing a material identifier type. Custom identifier type InfoObjects must be created in the BW with reference to this InfoObject. This InfoObject stores all texts of all identifier types. Template InfoObject for storing a material identifier value. This InfoObject can be taken as sample to create new custom InfoObjects. Does not store any texts. Note The bold marked items store master data. Details about master data reporting on material and facility master data are described later in this document. The linkage between the master data bearing InfoObjects is also explained there Configuration of LOV Items Within the EC application, configuration of the LOV items is done under Configuration. There the user has to maintain and specify custom LOV items. Within the EC Master Data Facility Builder and / or Material Management, you can assign the configured LOV items to a facility or a material. As already mentioned within the introduction, you can now extract as many identifiers and classifiers into the BW as required. The following subchapters describe all necessary aspects that have to be considered for successful LOV maintenance and LOV BW configuration. Material and Facility Identifiers The following graphic shows List of Values dialog in EC: SAP SE or an SAP affiliate company. All rights reserved.

203 Within the LOV dialog, identifier types can be configured. Such an identifier type has to be assigned within the facility builder or material management. There, the user is able to maintain a value for the identifier type. In addition, it is also possible to assign the same identifier type multiple times to the same material or facility. For BW extraction, note the following: In general, it is possible to skip the BW configuration if there is no need to extract the identifiers into the BW. The EC application does not force the user to perform a BW configuration. BW configuration must be complete. It is not possible to perform an incomplete BW configuration. The BW InfoSource name has to be configured with suffix _M. The InfoSource must belong to a master data bearing InfoObject in the BW that has as key either the facility or the material ID. The technical name of the master data bearing InfoObject and the InfoSource must be identical. The BW fieldname must refer to the corresponding data field of the transfer structure of the specified InfoSource and it must be unique concerning the InfoSource. This InfoObject must be an attribute of the master data InfoObject to which the InfoSource belongs. With regard to the screenshot, the corresponding BW modeling is the following: The master data InfoObject is called /TDAG/MATIC and contains the InfoObject /TDAG/NUMCAS as attribute. The BW InfoSource has the same name as the technical name of the master data bearing InfoObject /TDAG/MATIC. The transfer structure field for the attribute /TDAG/NUMCAS is S_NUMCAS. Material and facility identifiers can only be created as direct children of the LOV material and facility root nodes. It is not possible to create a different tree structure. The InfoObject for storing the identifier value must have the same technical naming as the identifier type InfoObject + a suffix V. This convention ensures that the identifier type and its values belong together. If the same identifier type is assigned to the same material or facility multiple times, the corresponding identifier value is concatenated and comma-separated until the size of 60 chars is reached. The rest is cut off SAP SE or an SAP affiliate company. All rights reserved. 203

204 Note that it is possible to store the identifiers in different container InfoObjects such as Z_MATIC. This might be necessary if the BW limit of attributes for an InfoObject is reached: The consequence of this scenario is that the identifier CAS-Number is extracted into the InfoObject /TDAG/MATIC. The identifier NAM-PROD is extracted into the InfoObject Z_MATIC. As prerequisites, the InfoObjects /TDAG/MATIC and Z_MATIC must have appropriate attributes. To get both master data records together, both InfoObjects have the same data record key - the material ID. Therefore, it is possible to combine the different master data records within all transactional data records that contain the material ID (the material InfoObject). This scenario is the same for the facility. The transfer structure already contains a data field for the material ID. The customer has to apply the transfer rules of the InfoSource by mapping the InfoObjects /TDAG/MATIC and Z_MATIC to the transfer structure field /TDAG/MATERIAL. Within the update rules, it is also possible to do a master data look up for the attributes of the InfoObjects /TDAG/MATIC and Z_MATIC, if necessary. The next figure shows a transfer structure sample: Note that there is no limit in the number of custom master data InfoObjects for storing material or facility identifiers SAP SE or an SAP affiliate company. All rights reserved.

205 Sample BW Record The following is an example of a BW record of the InfoObject /TDAG/MATIC, /TDAG/FACIC or any other custom InfoObjects that store the configured LOV items as additional information: MATERIAL ID NUM-CAS (Identifier) NUM_PROD (Identifier) MATGRP1 (Mat. Group) CLASS1 (Classifier type) CLASS1V (Classifier value) (Diesel) (petrol) Fossil fuels GHG Value for GHG Fossil fuels GHG Value for GHG This means that the relation of multiple identifiers and classifiers result in new columns and not in new records. In this scenario, the relation of multiple identifiers and classifiers for a single material or facility is solved by storing the identifiers and classifiers or groups in columns. This enables information to be stored on the basis of the material or the facility. In addition, the BW developer is able to add such a master data bearing InfoObject to every InfoCube that already stores the material or the facility because the master data InfoObjects are identified by the material ID or the facility ID. The only thing that has to be done here is the adaptation of the update rules, the adaptation of the ODS, and the InfoCube. For more details, see the following figure. Material, Consumption Material, and Facility Identifiers The concept for the classifiers is slightly different with regard to the identifiers. Within the LOV dialog, the classifier types and the corresponding classifier values have to be maintained. For a graphical summary of this scenario, see the following screenshot: 2017 SAP SE or an SAP affiliate company. All rights reserved. 205

206 As you can see in the screenshot, the classifier type enables you to maintain the BW settings. It is not possible to perform the BW configuration on the classifier values. For a correct use of classifiers, note the following: BW configuration must be complete or empty. Every classifier type has its own BW configuration. The BW fieldname of an InfoSource must be unique; otherwise, the information is overwritten. Classifier values must be children of a classifier type. The classifier type U.S. EPA has three possible classifier values: EPA AIR, EPCRA and Federal Insecticide. The InfoSource name in the BW has to be the same as the configured one without the suffix _M. The configured BW InfoSource (Z_MIDENT_M) belongs to a master data bearing InfoObject (Z_MIDENT) that contains the InfoObject (Z_CLASS3). The transfer structure field of the InfoSource is called (Z_CLASS3). As for the identifiers here, the same concept for the extraction of multiple classifier values for the same classifier type exists (only as additional information). The corresponding classifier values are concatenated and commaseparated up to 60 chars. The InfoObject for storing the classifier values must have the same technical name as the classifier type InfoObject + a suffix V. Note We recommend creating custom InfoObjects for identifiers, classifiers, and groups in the customer namespace, for example Z. Delivered BW Content Note Material / Facility classifiers are also stored in the InfoObject /TDAG/MCLASSES and /TDAG/FCLASSES. These two InfoObjects have the following composition: ID of the classifier record (/TDAG/MCLASSES, /TDAG/FCLASSES) Material (or facility ID) (/TDAG/MATERIAL, /TDAG/FACILITY) Classifier type ID (/TDAG/MCLATY, /TDAG/CL_TYPE) Classifier value (/TDAG/MCLASS, /TDAG/CLASSIF) Date from (time dependency of the facility) Date to (time dependency of the facility) These InfoObjects store all assigned classifiers of all materials / facilities (not as additional information). It is possible that, within such a master data record, the same material or the facility occurs several times. This is the case when a facility or a material has multiple assignments of the same classifier type SAP SE or an SAP affiliate company. All rights reserved.

207 Note It is not possible to create a custom InfoObject for storing the classifiers with regard to the previously mentioned concept. The following table shows some example BW records of these master data bearing InfoObjects: Record-ID Material ID Classifier Type ID Classifier Value U.S. EPA EPA AIR U.S. EPA EPCRA U.S. EPA Federal U.S. EPA EPA AIR With regard to the table for the material and facility identifiers above, the difference is that new classifier types and values will create a new record and not new columns. But this also means that it is not possible to use this information directly for the extension of the material and facility master data because the keys for these InfoObjects are different. The feature of customizing the update rules of the InfoCubes does not work here. Material Groups The concept for the material groups is similar to that for the classifiers. Material groups have to be maintained within the LOV dialog of the EC application. There, the user has to specify the material groups. The assignment of the material groups is done in the material management. The following two screenshots depict the LOV configuration and the material group assignment within the EC application: Note the following: The BW configuration must be complete or empty. Every material group must have its own BW configuration. The BW fieldname must be unique for the specified InfoSource; otherwise, the information is overwritten SAP SE or an SAP affiliate company. All rights reserved. 207

208 It is only possible to create material groups as children of the LOV root node for material groups, here named as Material Gruppen. No other constellations or tree structures are possible (supported). The InfoSource name in the BW has to be the same as the configured one without the suffix _M. The configured InfoSource /TDAG/MATIC_M belongs to the master data bearing InfoObject /TDAG/MATIC, which stores the material group 1 in the attribute /TDAG/MATGRP1. The transfer structure field of the InfoSource is S_MATGRP1. It is possible to store the material groups in different master data bearing InfoObjects like Z_MATIC. This might be necessary in case the BW limit of InfoObject attributes is reached. Delivered BW Content With regard to the classifiers here, the assigned material groups are also stored in a separate master data bearing InfoObject. The InfoObject is called /TDAG/MATGRPS and has the following composition: Record ID (/TDAG/MATGRPS) Material ID (/TDAG/MATERIAL) Material group ID (/TDAG/MATGRP) This InfoObject cannot be configured. The complete master data is stored within this InfoObject. Summary / Conclusion The application enables you to create unlimited numbers of material / facility identifiers and classifiers and material groups. These data objects are stored in two different ways in the BW: Identifiers, classifiers, and material groups are stored on basis of the material. Each identifier, classifier or material group is stored in a column. New identifiers, classifiers or groups result in new columns and not in new records. The advantage of this is that the data can be used as additional information for the facility or the material because the master data records do have the same key (material ID or facility ID). The disadvantage is that, with this solution, the material groups and the material / facility classifiers cannot be used for data arrangements SAP SE or an SAP affiliate company. All rights reserved.

209 Every classifier and material group assignment results in a new record. The same material or facility ID can occur several times in the different data records. The key for this master data records is different than the key for the material or facility master data. Therefore, the data records cannot be easily linked as in the point before; therefore, additional InfoCubes are required. The data extraction for this is not configurable. EC Content Delivery The EC content delivery provides the following objects: /TDAG/MATIC: Master data bearing InfoObject for storing the identifiers, classifiers, and groups of a material. This object contains the attributes /TDAG/NUMCAS, /TDAG/NUMCASV, /TDAG/NUMPROD, /TDAG/NUMPRODV, /TDAG/NAMPROD, /TDAG/NAMPRODV and /TDAG/MATGRP1. The LOV configuration of these identifiers is delivered as well. To test the data extraction, create a material and assign the LOV items to the newly created material. /TDAG/FACIC: Master data bearing InfoObject for storing identifiers and classifiers of the facility. This object contains the attributes /TDAG/FACNUM and /TDAG/FACNUMV. The LOV configuration of the identifier is delivered as well. To test the data extraction, create a facility and assign the LOV item to the newly created material. Note We recommend creating custom InfoObjects for identifiers, classifiers, and groups in the customer namespace, for example, Z. InfoCubes For the different InfoCubes, you can do the following: Add the InfoObject /TDAG/MATIC and all other custom InfoObjects (all master data bearing InfoObjects that store additional information) to all InfoCubes that already store the InfoObject /TDAG/MATERIAL. The delivered InfoCubes already contain the InfoObject /TDAG/MATIC so far the material InfoObject /TDAG/MATERIAL is part of it. Add the InfoObject /TDAG/FACIC and all custom InfoObjects (all master data bearing InfoObjects that store additional information) to all InfoCubes that already store the InfoObject /TDAG/FACILITY. The delivered InfoCubes already contain the InfoObject /TDAG/FACIC so far the facility InfoObject /TDAG/FACILITY is part of it. Use the newly delivered InfoCubes (see chapter ) if you want to report emission, consumption, and measurement data grouped by material classifiers or material groups. Process Chains The process chains must ensure that the master data is extracted first before the transactional data of the InfoCubes is extracted; otherwise, the master data lookup within the update rules of the ODS will fail. The master data of the identifier and classifier InfoObjects is added to a unique chain. Within the master data and hierarchies process chain, these process chains are called. Custom InfoPackages need to be added to the process chains as well SAP SE or an SAP affiliate company. All rights reserved. 209

210 Texts of the InfoObject Both InfoObjects have texts. The facility and the material texts are multilingual. The extraction of the facility texts uses the EC generic extractor. The consequence is that the data source / transfer structure of the InfoSource has to be manually applied. Instead of the Facility InfoObject default name (B123/S_FACILITY), the value OBJECTID has to be entered in the transfer structure field name of the facility InfoObject. For details about this scenario, see the following screenshot (orange marked): Master Data Reporting Because the complete master data of a facility or a material is split onto different InfoObjects, it is necessary that the data is linked together for reporting. Master data reporting makes more sense if the complete master data is available and not only a part of it. For example, you want to create a query for the determination of the classifier type for every material type. The information about the classifier data is stored in the InfoObject /TDAG/MCLASSES and the material type information is stored in the InfoObject /TDAG/MATERIAL. How do you get (join) the master data together? Material Master Data Reporting To enable master data reporting on the complete material master data, an InfoSet is introduced in EC 2.0 SP10 that joins all material dependent master data records that are split onto different InfoObjects. The InfoSet is called /TDAG/EM_IS01 (InfoSet Material) and contains the InfoObjects /TDAG/MATERIAL, /TDAG/MATIC, /TDAG/MCLASSES and /TDAG/MATGRPS by default. Customers that have a custom master data InfoObject for storing the identifiers, classifiers, and material groups should create their own InfoSet based on the delivered one and add the custom InfoObjects to the new InfoSet additionally. We recommend that you create a custom InfoSet and not change the delivered one. Note that it is only necessary to create an InfoSet if there is a need to do master data reporting on material data or facility data combined with identifier, classifier and material group master data. If you only want to do master data reporting on the facility master data or the material master data, it is not necessary to use the InfoSet. An InfoSet in the BW is only a special kind of data view. It is neither a data target nor can it be used for data forwarding SAP SE or an SAP affiliate company. All rights reserved.

211 Facility Master Data Reporting The same principle as for the material master data reporting is valid for the facility master data reporting. Note that in contrast to the material master data, the facility master data has the following differences: Facility master data is time-dependent There are no groups, only classifiers and identifiers The InfoSet for the facility master data is called /TDAG/EM_IS02 (InfoSet Facility) and joins the master data of the InfoObjects /TDAG/FACILITY, /TDAG/FACIC and /TDAG/FCLASSES as well as the master data of every custom facility InfoObject that stores the identifiers and classifiers. The UDF InfoObjects of the Facility can also be added to the InfoSet for master data reporting BW InfoCubes and ODS This chapter describes all relevant facts concerning the data arrangement functions of material classifiers and material groups. Currently, data arrangement by facility classifiers is not supported. The following screenshot shows a sample BW report for emissions by material classifiers: The problem of this report is that it is not possible to get an overall result concerning the emission values because a material can be assigned to multiple classifiers. Look at the screenshot and search for the material Sulfur dioxide. You will see that this material occurs several times in the report. Note If you want to create a report similar to this, it is mandatory to use the classifier or material group InfoObject in the query. Otherwise, the emission values are summed up and the result will be incorrect SAP SE or an SAP affiliate company. All rights reserved. 211

212 Hierarchies Reports and queries sometimes need to display data related to the whole company and the company structure. Because companies have different company structures, there is the need to customize hierarchies. In correlation to the structure of the hierarchy, the BW configuration needs to be considered. Configuration of Hierarchy Level in EC The configuration of the hierarchies in EC is done under: Configuration Master Data Management Hierarchies. Each of the hierarchy definitions includes a separate BW configuration. The BW configuration comprises three important points: BW Source: This name implies which InfoObject is the container for the external hierarchy. This name must stick to BW naming conventions. For example, /TDAG/FACILITY has to be entered in this field for a hierarchy for InfoObject /TDAG/FACILITY. BW Hierarchy: This name is requested by Business Warehouse, for example REG_HIERARCHY. BW Mapping Level: The mapping level describes the structure of the hierarchy, for example REG_HIERARCHY, which consists of the following levels: REGION COUNTRY LOCATION. If the hierarchy type is Business Warehouse relevant, then it is necessary to map each level of the hierarchy to a particular BW InfoObject. The amount of hierarchy levels is restricted to 5. InfoObjects for Hierarchy Levels As previously mentioned, the main function of hierarchies is to visualize the company structure in hierarchies. When assigning a facility to a hierarchy level, note that the BW configuration must be appropriate. For example, if you assign a facility to hierarchy level 3 but hierarchy level 2 has no BW configuration; EC cannot extract data of the facilities to the SAP BW. See the following figure: For the extraction of the hierarchy level in EC, an InfoObject must be created which is an attribute of the characteristic /TDAG/FACILITY. If the hierarchy level is defined with a new custom InfoObject, EC extracts the textual data and hierarchy information to the BW system. Another option is to use the InfoObject 0HIER_NODE. But if this InfoObject is used, there are no attributes in InfoObject /TDAG/FACILITY that can be used for filtering. Notes and Definitions In the following, facility always refers to the InfoObject /TDAG/FACILITY. The modeling in SAP BW should always be performed top to down. This means from the InfoCube to the ODS to the DataSource and so on. Customer development must be carried out in customer namespace. The commonly used prefix for the new InfoObjects is Z_ before a describing name, for example Z_BUSLINE (Business Line) SAP SE or an SAP affiliate company. All rights reserved.

213 EC Configuration This chapter describes the necessary steps to correctly configure a flex hierarchy that you have built in the facility builder so that it is extracted into the Business Warehouse. The whole process consists of the following steps: 1. Creation of a flex hierarchy and configuration of BW Properties (only necessary if the technical name of the facility hierarchy should be changed) 2. Hierarchy assignment 3. BW modeling Creation and Configuration The configuration and the creation of the flex hierarchies are done under Configuration Master Data Management Hierarchies within the EC application. For a valid configuration, perform the following steps: 1. Open Configuration in the EC application and select Hierarchies 2. Select Create Hierarchy or choose an existing hierarchy 3. Create your hierarchy (below the hierarchies' tray) 4. In the hierarchy details tray, select BW Properties (see screenshot) for configuration. The BW Mapping level defines the relationship between your hierarchy (created in Step3) and the corresponding BW InfoObjects. Note that there can be at most 5 hierarchy levels. Hierarchy Assignments After configuring the hierarchy, you have to assign the hierarchy to your facility structure. To do so, open the Facility Builder and assign the hierarchy structure to your facility structure. Select any facility and assign the corresponding hierarchy level to it. The hierarchy assignment is done on the hierarchies tab of a facility in Master Data Management. BW modeling For the BW modeling, see the next chapter SAP SE or an SAP affiliate company. All rights reserved. 213

214 BW Modeling Creating an InfoObject for New Hierarchy levels When creating the new hierarchy InfoObjects, we recommend that you use an existing InfoObject as a template. The most common one is the InfoObject Division (/TDAG/DIVISION). As mentioned before, the textual data of the hierarchy level is extracted to EC too. For this, the new InfoObject must be defined for the extraction of text. This is done by checking the With Text checkbox in the new InfoObject. The BW system creates a new InfoSource for the new hierarchy level InfoObject. For the extraction of text data, a new DataSource must be created. The DataSource must be of type Text and assigned to the SourceSystem EC. By default, the BW system maps the fields of the DataSource to the corresponding InfoObjects that makes further adjustments unnecessary. The next step is to create a new InfoPackage for requesting the data from EC and add the new InfoPackage to the ProcessChain: EC: Text data full load (/TDAG/EM_IO_TEXT). Modification of the InfoObject Facility The newly created InfoObject has to be added to the InfoObject Facility. The first step is to add the new InfoObject as an attribute. The attribute must be set as Time Dependent and optionally as Navigational Attribute. The next step is to add the new hierarchy InfoObjects as External Characteristics in Hierarchies in the Hierarchies Tab of the InfoObject Facility. After adding the objects, save and activate the InfoObject. In addition, the new hierarchy level InfoObjects need to be added to the DataSource by adding the InfoObject to the Transfer Structure. When the InfoObject is added to the transfer structure, the BW system automatically adds to the name of the InfoObject a generated Namespace (/BIC/) as prefix. The InfoObject may look like this /BIC/Z_BUSLINE. This prefix needs to be removed in order to perform a correct extraction of data (Z_BUSLINE). When creating a new hierarchy for the new InfoObjects, a new InfoPackage below the DataSource EC needs to be created. The InfoPackage must be assigned to the hierarchy DataSource (/TDAG/FACILITY_HIER_xEM020). The next step is to create a new hierarchy structure in Tab Hierarchy Selection of the new InfoPackage. The name of the hierarchy selection has to be the same as the one configured in EC because this name is requested by the BW during extraction. Historical Truth Hierarchies are part of the master data in the BW system. Since hierarchies can change, it might be necessary to make hierarchies historically true. It is insufficient to use the attributes of the InfoObject Facility since they contain only current master data and might have been changed over time. To meet this demand, the new hierarchy level InfoObjects must be included as characteristics in the corresponding InfoCubes. When adding the new InfoObject, we recommend that you create a new dimension for the new hierarchy layers. The next step is to add the new InfoObjects to the ODS Objects as well, where they should be added as DataField and not as a KeyField of the ODS Object. The mapping of the InfoObjects in the Update Rules from the ODS Object to the Cube are directly mapped; whereas, the Update Rules from the InfoSource to the ODS Object must perform a master data lookup. The corresponding information is read from the Facility InfoObject. This is configured in the master data details where the option Master Data Attrib. Of - Update Method must be selected. As time dependency, the end date must be selected from the InfoObject DS timeframe end (/TDAG/DS_TFEND) SAP SE or an SAP affiliate company. All rights reserved.

215 6.12 Data Export and Data Import As of EC 3.0 SP10, the EC application provides a new tool which enables the export and import of EC database tables without using SAPTrans tool. The tool enables importing and exporting mass data (all EC database tables) and the EC initial data content Export Content Data The EC export content data provides three options for exporting data from the current EC system: Export all data (system copy) exports all data of SAP Environmental Compliance. Use this export for a system copy. Export configuration data exports almost all configuration data. In detail, following configuration is exported (refer to SAP Note ): o EC Units and Dimensions o EC Facility Types o List of Values o Hierarchies o Object Based Permissions o User Defined Fields o Extension Points o Currencies o Status NetWork o User Profile o Customer Database Tables o Number Ranges o Account Types o Data Release Definition o Extension Mapping o Regulatory Content Providers o Permit Configuration o Alert Log Configuration o Data Entry Variances o Scripting o Notifications Configuration o Limit Check Configuration Export by XML definition file exports specific data using a user-defined XML file. Note that you perform this export at your own risk. Export for SAP EC Maintenance exports data when an export is requested by SAP Environmental Technical Support Team. Do not import this data in one of your systems SAP SE or an SAP affiliate company. All rights reserved. 215

216 EXPORT BY GENERIC DEFINITION FILE exports specific data updated since a specific date and a number range. (Refer to SAP Note for details) Example XML file for exporting EC configuration data: <?xml version="1.0"?> <selections> // Number Ranges <table name="td_content"/> //Dimensions and units <table name="em_dimension"/> <table name="em_dimension_text"/> <table name="em_unit"/> <table name="em_unit_text"/> <table name="em_fact" primarykey="iid"/> <table name="em_fact_ml_text"/> <table name="em_fact_text" primarykey="iid"/> <table name="em_fact_x_fact" primarykey="iid"/> <table name="td_ha_text"/> <table name="td_hierarchy_attr"/> <table name="td_hierarchy_node"/> <table name="td_hierarchy_type"/> <table name="td_hn_text"/> <table name="td_hn_x_ha"/> <table name="td_hn_x_hn"/> <table name="td_ht_text"/> <table name="td_ht_validity"/> <table name="td_udf_area"/> <table name="td_udf_area_text"/> <table name="td_udf_element"/> <table name="td_udf_elem_text"/> <table name="td_udf_x_area"/> <table name="td_user_exit" primarykey="iid"/> <table name="td_obp_action"/> <table name="td_obp_auth"/> <table name="td_obp_principal"/> <table name="td_obp_profile"/> <table name="td_obp_restr"/> SAP SE or an SAP affiliate company. All rights reserved.

217 <table name="em_es_types"/> <table name="em_es_type_caps"/> // Currencies <table name="er_currency"/> <table name="er_currency_text"/> // Status NetWork <table name="td_permission"/> <table name="td_perm_attr_def"/> <table name="td_perm_attr_value"/> <table name="td_perm_x_permattr"/> <table name="td_statnet_x_pattr"/> <table name="td_status"/> <table name="td_statusnetwork"/> <table name="td_status_change"/> <table name="td_status_t"/> // User Profile <table name="td_user_profile"> <where text="user_id='system_default_profile'"/> </table> // Customer Database Tables <table name="em_white_list"/> // Account Types <table name="em_acc_acctype"/> <table name="em_acc_period"/> // Data Release Definition <table name="em_drel_definition"/> <table name="em_drel_def_x_fac"/> <table name="em_drel_def_x_mat"/> // Extension Mapping <table name="em_calcvar_bwconf"/> // Regulatory Content Providers <table name="td_rcp_config"/> // Permit Configuration <table name="em_permit_icon"/> // Alert Log Configuration <table name="em_alert_logs"/> // Data Entry Variances <table name="em_entry_var"/> // Scripting <table name="em_ts_script"/> <table name="em_ts_script_log"/> 2017 SAP SE or an SAP affiliate company. All rights reserved. 217

218 // Notifications Configuration <table name="td_ _tpl"/> <table name="td_ _tpl_xml"/> // Limit Check Configuration <table name="td_xml_tpl"/> <table name="td_xslt_tpl"/> </selections> Note When you want or export all EC/BW properties, use the following tag in the XML definition file: <table name="td_properties"> <where text="name<>'admin.migration.systemcopy'"/> </table> The propertyadmin.migration.systemcopy is generated during the export/import process and control the system copy mode. This property is excluded in the upper tag. To export EC content data, proceed as following: 1. Create an empty folder on the NW server. Set up grant full permission for user SAPService<SID> on the folder. 2. Start the Export tool. Since EC 30 SP15 you can start the tool in the EC tools menu Content Export. or use the direct URL: Note The application is not part of the EC portal content and the EC 3.0 user needs Environmental Compliance admin permissions. The application needs the permission action EC_ExportImportData. 3. Select the folder on the Import content UI. 4. Select an export option. o Export all data (system copy) o Export configuration data o Export for SAP EC Maintenance o Export by XML definition file For this option, you need to select an XML definition file 5. Start the export of data. During the export process, the EC 3.0 system is in system copy mode. That means all persistency operations in EC 3.0 are stopped. 6. After the export, the Reset System Copy Mode popup appears. You have to reset the copy mode. After this reset, the EC persistency operations are available again SAP SE or an SAP affiliate company. All rights reserved.

219 Supported Database Tables At this time, the Content Export / Content Import supports only EC standard database tables (standard database tables are delivered with the EC software component). When using customer database tables (from EC projects), you have to add the customer database in the EC configuration tool Customer Database Tables. This tool enables you to specify further database tables for using the Content Export / Content Import Import Content Data To import EC content data, proceed as following: 1. Copy the exported files to an empty folder on the NW server. Set up full permissions for user SAPService<SID> on the selected folder. 2. Start the Content Export / Content Import tool Since EC 30 SP15 you can start the tool in the EC tools menu Content Import. or use the direct URL: Note: The application is not part of the EC portal content and the EC 3.0 user needs Environmental Compliance admin permissions. The application needs the permission action EC_ExportImportData. 3. Select the folder on the import content screen. 4. Start the import of data. During the import, the EC 3.0 system is in system copy mode. That means all persistency operations in EC 3.0 are stopped. 5. After the import, the Reset System Copy Mode popup appears. You have to reset the copy mode. After this reset, the EC persistency operations are available again. 6. After the import runs, reset the EC Buffer in the EC Tools menu. (Very Important step!) The import process always checks the files that are imported with the current version of EC. This check ensures that the EC user does not import data from a newer EC system into an older EC system. The following tables show the check of the imported data: 2017 SAP SE or an SAP affiliate company. All rights reserved. 219

220 Export EC 2.0 in current EC 3.0 SP EC30 earlier SP in current EC 3.0 SP EC 3.0 similar SP in current EC 3.0 SP EC 3.0 future SP current EC 3.0 SP EC Initial data Not allowed Not allowed Allowed Not allowed EC delta data Not allowed Allowed Allowed Not allowed All database tables Allowed Allowed Allowed Not allowed Configuration data Not allowed Allowed. Only on system with Productive EC property Allowed. Only on system with Productive EC property Not allowed Data exported via XML definition file Allowed with Warning: Import at your own risk Allowed Allowed Allowed with Warning: Import at your own risk Note In case that the message appears Some tables already contain data. Do you want to start import and replace them with the import data? : During the import process the system overwrites the data that is specified in the exporting XML file and already exists in the system. In case of initial or delta data, only data in a special range is overwritten. Customer data is not overwritten. Caution This following build up in a self-defined XML file is technically not possible: <table name="em_esource"> <where text="id > AND ID < " /> </table> <table name="em_esource"> <where text="id > AND ID < " /> </table> The same database table shall not be defined in the XML file twice or more times. Use the following build up to avoid problems in the importing process: <table name="em_esource"> <where text="(id > AND ID < ) OR (ID > AND ID < )" /> </table> The brackets are very important, because of the build of the SQL select statement to detect the data. Another possibility is to create for every EM_ESOURCE table an own select.xml file SAP SE or an SAP affiliate company. All rights reserved.

221 6.13 Import Data with SAPTrans (Obsolete as of EC 3.0 SP10) This chapter describes how to import the EC data with the obsolete EC tool SAPTrans. Use the tool for importing historical delta data of EC with earlier versions than EC 3.0 SP10. SAP Environmental Compliance requires the availability of initial data content. The content is uploaded with the SAPTrans tool (see SAP Note: and ). Ensure that the EC 3.0 is deployed on the SAP NetWeaver CE system. To import data with SAPTrans, proceed as follows: Action On the EC installation directory, navigate to folder: <EC-DIR>\saptrans_EC30_init. Copy the all content of this folder to a local hard disk drive, for example \saptrans_init\ 1. Copy the corresponding JDBC Driver JARs, which depends on the EC target database into the folder \saptrans_init\ o The driver JARS are database-dependent and are required to be copied into the SAPTrans directory: The following list contains the driver JARs for the different database types: o MAXDB: sapdbc.jar o SQL-Server: sqljdbc.jar For information about where you can download the latest MS SQL Server JDBC driver, see SAP Note o Oracle: ojdbc14.jar With Oracle 11g or higher, use the JDBC driver from the SAPTrans package. o DB2: db2jcc.jar, db2jcc_license_cisuz.jar and db2jcc_license_cu.jar o For a default installation, these driver classes can be found in the following directories: Windows systems o MAXDB: localdrive\sapdb\programs\runtime\jar o SQL-Server: Refer to the SAP Note o Oracle: localdrive\oracle\<sid>\<oracle_version>\jdbc\lib o DB2: localdrive\db2\db2<sid>\sqllib\java Unix systems o MAXDB: /sapdb/programs/runtime/jar o SQL-Server: Refer to the SAP Note o Oracle: oracle/<sid>/<oracle_version>/jdbc/lib o DB2: /db2/db2<sid>/sqllib/java 2. Open a command line interface and change the current working directory folder \saptrans_init\ o Enter the following command: java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m -jar 2017 SAP SE or an SAP affiliate company. All rights reserved. 221

222 SAPtrans.jar import logfile=import.log datafile=init.dat connectstring=<jdbc Driver>;<JDBC Url>;<User>;<Password> with parameters: o JDBC Driver: Full qualified class name of the JDBC Driver to connect the EC target Database. o MAXDB: com.sap.dbtech.jdbc.driversapdb o MS SQL-Server com.microsoft.sqlserver.jdbc.sqlserverdriver o Oracle: oracle.jdbc.driver.oracledriver o DB2: com.ibm.db2.jcc.db2driver o JDBC Url: Connect URL for the JDBC Driver. The JDBC URL is database-dependent o MAXDB: jdbc:sapdb://<host>/<instanceid> o MS SQL-Server: jdbc:sqlserver://<host>:<port> o Oracle: jdbc:oracle:thin:@<host>:<port>:<sid> o DB2: jdbc:db2://<host>:<port>/<sid> o User: Database user to connect with. o Password: Database user password. o Example command for import into SQL Server: java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring= com.microsoft.sqlserver.jdbc.sqlserverdriver; jdbc:sqlserver://vma03:1433;sapc11db;password o Example command for import into DB2 Server java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m -jar SAPtrans.jar import logfile=import.log datafile=init.dat "connectstring= com.ibm.db2.jcc.db2driver;jdbc:db2://vma03: 5912/C11;SAPC11;password" o Example command for import into Oracle Server java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring= oracle.jdbc.driver.oracledriver; jdbc:oracle:thin:@vma03:1527:sr3;sapsr3db;password o Example command for import into MAXDB Server java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m -jar SAPtrans.jar import logfile=import.log datafile=init.dat connectstring= com.sap.dbtech.jdbc.driversapdb;jdbc:sapdb: //vma03/c11;sapc11db;password o Choose Enter and execute the command. For more information about the state of the initial data load, see file import.log. o The timezone function is detailed described in the SAP Note: Note The parameter -Xmx1024m means that JAVA allocates 1 GB Memory RAM. Note that the client system where SAPTrans runs needs at least 1GB free Memory RAM SAP SE or an SAP affiliate company. All rights reserved.

223 7 Migration of SAP EC This chapter describes the upgrade and migration steps of an existing SAP Environmental Compliance 2.0 system to. 7.1 Introduction SAP Environmental Compliance 2.0 is released based on either NetWeaver 2004 or NetWeaver 7.0. The SAP Environmental Compliance 3.0 is based on SAP s NetWeaver java platform NetWeaver CE (7.10, 7.11, 7.20 or 7.30 or newer). Since you usually have to setup a landscape for Environmental Compliance that consists of a development, a test/qa, and a productive environment, the migration steps described in this document have to be carried out for all these environments. Generally, the development environment should be migrated first, followed by the QA environment and then finally the production servers. We recommend testing your business functions on your QA environment before upgrading the productive servers. 7.2 Prerequisites EC 2.0 Support Package Your existing SAP EC installations have to be upgraded to the latest EC 2.0 Support Package SP13 in order to ensure that the database tables are prepared for the upgrade to EC 3.0. For information on the upgrade to EC 2.0 SP13, see the corresponding SAP Note Server Platforms Server platforms (hardware/operating system and database platform) for the new EC 3.0 installations are compliant with NetWeaver CE 7.1 SP8 or higher and SAP Environmental Compliance requirements. See the Product Availability Matrix (PAM) on for a complete list of supported operating systems and database platforms for NetWeaver CE and. If you find that your existing server platform that hosts SAP Environmental Compliance 2.0 does not meet the requirements for the version 3.0 and the new NetWeaver CE Platform, you can carry out the same Migration; however, the installation of NetWeaver CE and EC 3.0 has to be done on a new server platform. Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 223

224 7.3 Detailed Migration Steps In order to successfully migrate a complete EC installation, the following sections contain the detailed description of the steps that you have to carry out. Since Environmental Compliance also contains components that are installed on a SAP BI system and on an Enterprise Portal System, the migration steps for these two parts are described separately. Note that the migration steps for the SAP BI content, as well as for the portal content, only need be top carried out if you are already using these 2 options in your existing EC installation. 7.4 Migration of EC Installations The following steps need to be carried out when migrating an EC 2.0 SP15 (or later EC20 release) installation to SP6 (or later EC30 release - we recommend always using the latest EC30 Support Package. An overview of all EC30 is provided in the SAP Note ): We recommend that you use a new system for the EC 3.0 installation to maintain a valid backup system. Export Database Content Inform all users of the EC 2.0 system that it is not available for the time of migration. Deactivate all background jobs. Stop running BW extractions related to the EC 2.0 system. Deactivate data access from all ERP systems to EC 2.0 data via an RFC connection. Caution Do not use any EC Web Service, Background jobs, or BI extractions during migration. To migrate all content of the database tables that are part of EC, use the export application of the EC 2.0 EC 3.0 Migration Tool (This URL exists only in EC 2.0). Note o The application is not part of the EC Portal Content and the EC 2.0 user needs Environmental Compliance admin permissions. The application needs the permission action ContentMigrationTool. o Replace <host>:<port> with your server name and the port the WAS is running. Provide a migration folder on the EC 2.0 server with sufficient storage capacity for the migration data. Select the migration folder in the EC 2.0 EC 3.0 Migration Tool and start the export. Note Depending on the amount of data, exporting the data can take an extended period. During the export, the EC 2.0 system is in system copy mode. That means all persistency operations in Environmental Compliance are stopped SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

225 Note o Troubleshooting: If the EC 2.0 system is still in system copy mode when the export is finished in an incorrect manner, run the Reset System Copy application to enable the EC 2.0 system again: Copy o The application is not part of the EC Portal Content and the EC 2.0 user needs Environmental Compliance admin permissions. The application needs the permission action ContentMigrationTool. o The export runs in background. When you are shut down the client, the export still running in background. You can check the export.log file in the export folder to Install New NetWeaver CE 7.1 SP8 or Higher Instance Since this migration assumes that the existing server platform supports the requirements for SAP NetWeaver CE, you can install the new NetWeaver platform using the normal installation procedure as described in the installation documentation. For the corresponding installation documentation, see the following article Note If your existing server platform does not meet the requirements for NetWeaver CE and SAP Environmental Performance 3.0, you have to install NetWeaver CE on a new server platform. All subsequent steps have to then be carried out on the newly installed server. Deploy Environmental Compliance 3.0 SP6 or Later Support Packages/Patches After NetWeaver CE is successfully installed, you can start the deployment of SAP Environmental Compliance 3.0. For the detailed installation process, see chapter Deploying the EC Application. For more information about the installation, see SAP Note and all related SP and Patch notes. Migrate Users To move the existing users, roles, and groups that have been setup on your EC 2.0 installation to the new EC 3.0 system, you can use the export and import function available in the user management of NetWeaver. For detailed information, go to help.sap.com: For NetWeaver 2004: For NetWeaver 7.0 (2004s): When using the import and export function, usually the passwords of the users you are exporting are not written to the export file. To change this, you can set the following UME property: ume.admin.password.migration=true Note that this setting has to be made on the NetWeaver system where you export the users as well as on the NetWeaver system where the users are imported. For detailed information about how to set the UME property, go to help.sap.com: Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 225

226 For NetWeaver 2004: For NetWeaver 7.0 (2004s): For NetWeaver CE 7.1: m Note This setting should be reverted tofalse on the source as well as the target system after the migration of the users is finished Import Default User Groups EC 3.0 is delivered with several sample user groups, which are assigned to the portal roles and EC object-based permissions. For more information about EC 3.0 user groups, refer to the SAP Note Note o If you are using federated portal network, then the Groups has to be imported always on the Producer side. o If the message appears Some tables already contain data. Do you want to start import and replace them with the import data? : During the import process the EC application overwrites the data that is defined in the exporting XML file and already exists in the system. In case of initial or delta data, only data in a special range is overwritten. The customer data is not overwritten. o EC 3.0 does not support making changes in the UME role file as it was possible in EC 2.0. All customer changes from EC 2.0 Role.xml file have to be migrated manually in the EC 3.0 object-based permissions. For more information, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal under SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

227 7.4.2 Import Database Content To migration all content of the database tables that are part of EC, use the Import application of the EC 2.0 EC 3.0 Migration Tool. (This URL exists only in EC 3.0) Note o The application is not part of the EC portal content and the EC 3.0 user needs Environmental Compliance admin permissions. The application needs the permission action ContentMigrationTool. This action is part of the standard role ec_environmental_compliance_admin or group UMEGROUP_Environmental Compliance Admin o Grant full permission for user SAPService<SID> on the selected migration folder. Select the migration folder that contains the exported data of the EC 2.0 system in the EC 3.0 Migration Tool and start the import. Note o Depending on the amount of data, importing the data can take an extended period. o In dependency of the used database, we recommend that you deactivate redo logging or set the system to bulk-logging mode of the database for the time of the import. Reactive the redo logging or set the system mode to full when the import is finished. o If an out-of-memory exception occurs during export, we recommend that you increase the JVM heap size. For detailed information, see: eset.htm o If the EC system already contains data, an initialization is necessary to enable a successful import. The initialization operation can take an extended period of time regarding the existing data. During the import, the new EC 3.0 system is in system copy mode. That means all persistency operations in EC 3.0 are stopped. Note o Troubleshooting: If the EC 3.0 system is still in system copy mode when the import is finished in an incorrect manner or the Web Application timed out, run the Reset System Copy application to enable the EC 3.0 system again: Copy. o The application is not part of the EC Portal Content and the EC 3.0 user needs Environmental Compliance Admin permissions. Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 227

228 7.4.3 Import Delta Data Content of EC 3.0 To import the delta data of EC 3.0, use the EC Export Import tool. The current installation SAP Note contains a step by step update process description. As of EC 3.0 SP13, a special SAP Note provides an EC 2.0 EC 3.0 Delta. (See SAP Note and chapter Uploading Initial EC Delivery Content Run the Data Migrations To ensure that changes to the database structure of SAP EC 3.0 in comparison to 2.0 are applied to the now imported data, you have to run the corresponding data migrations. Logon with an administrator user to Environmental Compliance; navigate to EC Administration Data Migrations and run the listed data migrations. This ensures that the data is converted to the new database structures if required. Run all data migrations that are described in the SAP Note Furthermore, run also the data migrations described in the SAP Note of the current EC 3.0 Support Package or Patch Level. Action Log in to the EC portal ( with an user that is assigned to the User Group UMEGROUP_Environmental Compliance Admin. Navigate to Administration Data Migration Run the EC 3.0 available data migrations. After every run, check the logs of the data migration modules. Remove the Now Obsolete NetWeaver Instance (Optional) Using the uninstall functionality of the SAPInst, you can remove the remaining NetWeaver 2004 or NetWeaver 7.0 installation that was used for EC 2.0. We recommend doing this after you test your key functions on the newly migrated EC 3.0 installation. If you install on a new server platform, these steps become obsolete. The old server that hosted EC 2.0 can be reused or decommissioned SAP BI Content Migration The most important points for every release of EC are the Business Warehouse system requirements. The level of the support packages for the SAP Business Warehouse can differ with every release of EC SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

229 Updating EC BW Content The update of the BW content is different to the first-time activation. However, the activation of BW content can be tricky in some cases. This chapter describes techniques and strategies for upgrading the EC BW content Preliminaries For the update of your BW content, you should have completed the preliminary steps described in chapter Procedure and Preparation. However, it is strongly recommended that you verify that the steps described are successfully accomplished. Another important point is to make sure that your BW system has the appropriate service pack level installed. This level may be different for every version of EC BW content. Note Before upgrading your EC BW Content make sure the transactional data of all InfoCubes and ODS objects are deleted Techniques and Knowledge Generally, the update of the BW content can be tricky in some cases. Depending on the changes made from the previous BW content to the newly delivered. If the changes made to the BW content contain deletions of InfoObjects that are still referenced in other Objects, in the activation can be complicated. However, if no objects have been removed, the activation and installation is straight forward. There are usually two activation strategies that need to be considered when activating the EC BW content: Customized standard content Standard content If you are updating your EC BW content the most important option for the activation is the MATCH or COPY(x) option. This option defines whether the active BW content is merged with the delivered BW content. This mode is also called update mode. This is of importance when customer specific enhancements are made to the EC content (e.g. customizing of the facility hierarchy). If you deselect this option, the delivered version of the content will overwrite your changes. However, sometimes it might be necessary to deselect this option. This is the case if the upgrade BW content that contains incompatible changes to previous versions e.g. InfoObjects have been removed from /TDAG/FACLITY. Then, to install the content, deselecting this option will overwrite the Standard content. This is necessary because deletions cannot be transported, so the delivered version of the content needs to replace the active version of the content. In general, the BW activation system suggests which objects to update and which objects to overwrite. However, this might not be appropriate in all cases. Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 229

230 Note o Before starting the BW content installation, make sure that you have selected the source system EC and the self system. The collection mode should be set to collect automatically. o If you have trouble installing the InfoPackages of the EC BW InfoSources, try restoring the EC source system and importing the EC BW content transport again General Remarks This subchapter lists key facts that should be considered for the EC BW upgrade. The different remarks do not depend on a specific EC service pack; they are valid for all EC BW releases. The different points are requirements that have to be performed manually before starting the content activation Notes for content activation Select the source system EC and the Self system when activating the InfoObjects in your BW system. Follow the instruction of the content installation as mentioned in this document. Removal of obsolete attributes of InfoObjects: Consider all referenced InfoObjects (EC standard InfoObjects or custom InfoObjects). Especially if referenced InfoObjects are used in InfoCubes. After changing the InfoObject e.g. removing of attributes, the corresponding Update rules of the involved InfoCubes or InfoObjects need to be reactivated. If not, the merge process while activating new BW content will fail. This may occur during the installation of the InfoCubes resulting in an error message that refers to the earlier removed attributes. Custom InfoCubes that use standard EC BW Objects For example, this means that besides the standard InfoCube, there is also an additional copy of this InfoCube in our BW system. The copy also uses the same InfoSource for data loading. If there are major changes as described in the previous point, you also have to reactivate the update rule of the InfoCube copy. Otherwise, it is not possible to install / activate the new BW content using the option merge. In addition, there are problems with data loading and it is not possible to view the details of the InfoSource. After installing / activating a part of the new BW content, e.g. the InfoCubes, check if the activation was successful. Call transaction rsa1 and review the InfoCubes in the InfoProvider view. After successfully installing the process chains, we recommend that you manually activate the process chains again. Call transaction RSPC for activating the process chains. Note that there several process chains that include other process chains. Standalone process chains need to be activated first We recommend that you check if the complete BW upgrade was successful. Are all BW objects (InfoObjects, InfoCubes, update rules ) active in the BW system? Do the InfoSources contain any generated Z - InfoPackages? If this is the case, remove these InfoPackages manually. Always read the installation remarks for the different releases carefully. If there is an update that skips several service packs, e.g. from SP7 directly to SP9, you must observe the installation remarks of the missed service packs. If the EC BW content is installed for the first time, the installation remarks can be skipped - except the installation order SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

231 Ignore Errors In some BW releases, errors might occur during the activation of the content for the InfoObjects /TDAG/IDENT and /TDAG/MIDENT, which indicate that the data source is missing. These errors can be ignored because, for these InfoObjects, no master data/ extraction is performed. These InfoObjects are used as attributes Upgrade from EC 2.0 SP13 BI Content Within EC 3.0, there is one important change regarding the BI content design. With EC 3.0 BI Content, the facility and material identifier and classifiers have been adapted. In the past, EC provided two ways of configuring the BW extraction of these identifier and classifier. The first used the BW Properties and the second one used the LOV dialog. Because EC 3.0 only supports the identifier and classifier concept, which uses the LOV configuration, it was necessary to adapt the BW content. Therefore, the following changes have been applied: Removal of the facility classifiers and identifiers from the InfoObject /TDAG/FACIC Removal of the material identifiers and classifiers from the InfoObject /TDAG/MATIC Adaption of the InfoSources /TDAG/FACIC and /TDAG/MATIC Removal of the navigational attributes in all EC InfoCubes Deletion of the facility and material classifier and identifier InfoObjects (they have been marked as obsolete, the template InfoObjects will remain) The following remarks help you to adopt the EC 3.0 BI Content: Note that if you do have customer specific enhancements in your EC BI content, it is necessary to perform the changes manually. If you do not have customer specific enhancements, you can copy the BI content during the installation. Herewith, the BI content is replaced by the EC 3.0 BI Content. If you use the old facility / material identifier and classifier concept, which use the BW Properties configuration dialog, you have to implement the new concept, which uses the LOV dialog. See the SAP Note for details. Note If your current EC 2.0 SP13 BI Content is based on a SAP BI 6.20 or SAP BI 6.40 note that an automatic upgrade to the EC 3.0 BI Content together with the Upgrade to SAP BI 7.00 via an integrated Upgrade Package is not supported. Upgrade your BI system to BI 7.00 separately and then follow the instructions above to then upgrade the EC BI content to version Enterprise Portal Content Migration SAP Environmental Compliance 2.0 came with separate portal content to be installed on an Enterprise Portal system. This content could be installed on a portal installation that was hosted on the same server as the EC installation or on a separate server that hosted the Enterprise Portal installation. Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 231

232 With, which is now hosted on a SAP NetWeaver CE 7.1, the integration into a SAP Enterprise Portal is done using Federated Portal Network (FPN) technologies instead of deploying separate Enterprise Portal content for EC. The following graphic shows the relationship: In regards to the migration to Environmental Compliance 3.0, this means, that you can continue using your existing Enterprise Portal Installation based on NetWeaver 7.0 to integrate the PCD objects of SAP Environmental Compliance 3.0 into your Portal For a detailed description of how to setup the connection between NetWeaver CE 7.1 and Enterprise Portal on NetWeaver 7.0, see and The result of exposing the PCD objects via the FPN technologies is that you can integrate the worksets and pages that come with EC 3.0 into your own roles or worksets or just assign the standard roles of EC 3.0 to your users. There are different options how you have installed SAP Environmental Compliance 2.0 and the Enterprise Portal: EC 2.0 and the Enterprise Portal are installed on the same server platform. If you currently host SAP Environmental Compliance 2.0 and Enterprise Portal 7.0 on the same NetWeaver 7.0 or NetWeaver 2004 installation, you have 2 options depending if you are using the Enterprise Portal for other applications: o Option 1: The Enterprise Portal is only used for Environmental Compliance. In this case, you can migrate to EC 3.0 on NetWeaver CE 7.1 as described in the chapter 7.4 Migration of EC Installations. With the deployment of EC 3.0, all new roles, worksets, and pages are available and can be assign to users or used to create custom roles and worksets directly in the portal configuration of NetWeaver CE 7.1. o Option 2: The Enterprise Portal is used for other applications as well. In this case, we recommend separating the Enterprise Portal and the Environmental Compliance onto two different servers, whereas the existing Enterprise Portal Installation (that now also hosts Environmental Compliance 2.0) can be reused SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

233 EC 2.0 and the Enterprise Portal are installed on separate server platforms. In this case, you can stay with your existing Enterprise Portal installation and consume the new PCD objects coming from the new Environmental Compliance 3.0 Installation via the FPN technologies. The existing server hosting Environmental Compliance 2.0 can be migrated with either scenario 1 or 2 as described in the chapter 7.4 Migration of EC Installations Migration of Permissions from EC 2.0 to EC 3.0 The permission in EC 2.0 was built in the Role.XML file. The EC 3.0 permissions are building up in three places: Portal Pages: Portal Content Role File (internally): Can be assigned in the user management to the roles. Object Based Permission: Part of the EC application The customer XML data from EC 2.0 role file needs to be mapped into the EC 3.0 pages, role file and object based permission profiles. The EC 3.0 Rolefile content cannot be changed. This file contains only ACCESS Actions which allows the ACCESS to the different modules of EC 3.0. Following actions are available in EC 3.0: EC 30 Action Similar EC 20 Action Description EC 30 Relevant EC_UnitsRead UnitsRead Allows to read units and dimensions. Needs the Portal Pages Units & Dimensions and Currencies EC_UnitsChange UnitsChange Allows to manage units and dimensions. Needs the Portal Pages Units & Dimensions and Currencies EC_ExtractionServerMonitor Tools.ExtractionServerMonitor Needs the Portal Page RFC Server Monitor EC_BWDeltaInfo Tools.BWDeltaInfo Needs the Portal Page BW Delta Info EC_DataMigration Tools.DataMigration Needs the Portal Page Data Migration EC_LogViewer Tools.LogViewer Needs the Portal Page EC Log Viewer EC_ResetBuffer Tools.ResetBuffer Needs the Portal Page Reset Buffer EC_GlobalUserReassignment Tools.GlobalUserReassignment Needs the Portal Page Global User Reassignment Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 233

234 EC_ChangeDocumentAdmin Tools.ChangeDocument Needs the Portal Page Change Documents EC_XMLTransferWorkbench Tools.XMLTransferWorkbench Needs the Portal Page XML Transfer Workbench EC_MyUserProfile Tools.UserProfile Needs the Portal Page My Profile EC_ContactsManagement Tools.ContactsManagement Needs the Portal Page Contact Management EC_IntegratedTags Tools.IntegratedTags Needs the Portal Page Integrated Tags Management EC_Hierarchies Configuration.Hierarchies Needs the Portal Page Hierarchy EC_ListOfValues Configuration.ListOfValues Needs the Portal Page List of Values EC_ Notification Configuration. Notification Allows to manage the Notifications and Diagnostics. Needs the Portal Page Notification EC_DefaultUserProfile Configuration.DefaultUserProfile Needs the Portal Page Default User Profile EC_BWProperties Configuration.BWProperties Needs the Portal Page BW Properties and EC Properties EC_RFCDestination Tools.RfcServer Configuration.RFCDestination Needs the Portal Page RFC Configuration EC_IntegratedSystems Configuration.IntegratedSystems Needs the Portal Page Integrated Systems EC_FacilityTypeCapabilitiesConfig Configuration.FacilityTypeConfig Needs the Portal Page Facility Configuration EC_UserDefinedFields Configuration.UserDefinedFields Needs the Portal Pages Assignments for Master Data, Assignments for Transactional Data and Elements EC_UserExits Configuration.UserExits Needs the Portal Page Extension Points EC_DataEntryVariances Configuration.DataEntryVariances Needs the Portal Page Data Entry Variances EC_Scripting Tools.Scripting Needs the Portal Page Scripting SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

235 EC_DocumentManagement Tools.DocumentManagement Allows to manage the document management. Needs the Portal Page Document Management EC_EmissionsAccountingConfig EC_BatchProcessStepTemplate Configuration.EmissionsAccountingCon fig Configuration.BatchProcessStepTempl ate Allows to manage the emissions accounting configuration. Needs the Portal Page Emissions Account Types Allows to manage the batch process step templates. Needs the Portal Page Batch Process Step Templates EC_IntegrationManager Tools.IntegrationManager Allows to use the integration manager. Needs the Portal Page Integration Management EC_IntegrationManagerAdmin Tools.IntegrationManagerAdmin Allows to administrate the integration manager settings Needs the Portal Page Integration Management EC_SystemChecks Tools.SystemChecks Needs the Portal Page in the role System Checks EC_StatusNetwork Configuration.StatusNetwork Needs the Portal Page Status Network Configuration EC_DataRelease Configuration.DataRelease Needs the Portal Page Data Release Definition EC_MyTranportConfiguration NO EC 20 Action Needs the Portal Page My Transport Activities EC_TranportConfigManager NO EC 20 Action Needs the Portal Page Manage Transport Activities EC_GlobalAuthorizations Tools.GlobalAuthorizations Needs the Portal Page Object- Based Authorization EC_ChangeDocumentArchives NO EC 20 Action Needs the Portal Page Change Document Archives EC_RFCServerMonitor Tools.ExtractionServerMonitor Needs the Portal Page RFC Server Monitor EC_TableLookupWebService NO EC 20 Action ContentMigration ContentMigration Similar with the action EC_ExportImportData Can be accessed only via URL Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 235

236 EC_RegulationContentProvider NO EC 20 Action Needs the Portal Page Regulatory Content Providers EC_ExtractionMappingConfig NO EC 20 Action Needs the Portal Page Extraction Mapping for Calculation Variables EC_ExportImportData NO EC 20 Action Can be accessed only via URL Portal Page Data Import Log EC_LimitCheckSummaryTemplate s NO EC 20 Action Needs the Portal Page Limit Check Summary Templates EC_CustomerDatabaseTables NO EC 20 Action Needs the Portal Page Customer Database Tables EC_PermitConfiguration NO EC 20 Action Needs the Portal Page Permit Configuration EC_EmissionsAccountingAccess EmissionsAccountingBase Portal Page Emissions Accounting EC_ExceptionManagerAccess NO EC 20 Action Portal Page Exception Management EC_ExceptionManagerArchiveSea rch NO EC 20 Action Portal Page Exception Management EC_CalculationAccess NO EC 20 Action Portal Page Calculation Management EC_BatchProcessAccess NO EC 20 Action Portal Page Batch Processes EC_PermitAccess NO EC 20 Action Portal Page Permit Management EC_MaterialAccess NO EC 20 Action Portal Page Materials EC_TaskAccess NO EC 20 Action Portal Page Task Management EC_TaskArchiveSearch NO EC 20 Action Portal Page Task Management EC_ReportAccess ReportBasic Portal Page Reporting EC_FacilityAccess NO EC 20 Action Portal Page Facilities EC_FacilityComplianceAccess NO EC 20 Action Portal Page Facility Compliance Management EC_EmissionManagerAccess NO EC 20 Action Portal Page Emissions Management and Energy Manager EC_ComplianceManagementAcce ss NO EC 20 Action Portal Page Compliance Management SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

237 EC_FacilityScenarioManager NO EC 20 Action Additional action to access the scenarios in facilities EC_EmissionManagerArchiveSear ch EC_FacilityTypeConfigurationAcce ss NO EC 20 Action NO EC 20 Action Additional action to access the facility archives Portal Page Facility Type Configuration EC_ParameterAccess NO EC 20 Action Portal Page Parameters EC_ExceptionWebService NO EC 20 Action Web Service action EC_BatchProcessWebService NO EC 20 Action Web Service action EC_FacilityComplianceWebServic e NO EC 20 Action Web Service action EC_EmissionManagerWebService NO EC 20 Action Web Service action EC_CitationMonitoringAccess NO EC 20 Action Portal Page Obsoleted actions from EC 2.0: PermitPLSEnabled PermitEMEnabled FacilityPLSEnabled FacilityEMEnabled FacilityShowAllTabs ReportFacilityComplianceEnabled TaskPLSEnabled Configuration.CronService use the NetWeaver Administration Configuration.RenamingTool use the Portal Personalization settings ReportAdmin Use Object Based Permissions + EC_ReportAccess DocumentAssignment DocumentReader DocumentManager DocumentAdministrator ChangeDocumentUse ListOfValuesChange Admin Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 237

238 EC 20 actions that were not used in the upper table: EC 20 Action Mapping in EC 30 FacilityPLSDataRead EC 30 Object-based Permission action within the profile FacilityPLSManager FacilityPLSAdmin PermitPLSDataRead PermitPLSManager PermitPLSAdmin TaskRead TaskReadAndCreate TaskWriteAndCreate TaskManageAll MaterialRead MaterialManager PermitRead PermitManageAll ParameterRead ParameterManager EquationBuilderRead EquationBuilderManager FacilityManageAll FacilityCarriers FacilityCostCenter7400 FacilityReadNode and601 FacilityDataManage FacilityReadAll FacilityScenarioManager FacilityManager FacilityAdministrator ExceptionCreate ExceptionLogRead ExceptionLogManage EmissionsAccountingAdmin EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile OBSOLETE AS OF xem 2.0 SP5 OBSOLETE AS OF xem 2.0 SP5 OBSOLETE AS OF xem 2.0 SP5 OBSOLETE AS OF xem 2.0 SP5 OBSOLETE AS OF xem 2.0 SP5 EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

239 BatchProcessManage BatchProcessRead ManageAll EC 30 Object-based Permission action within the profile EC 30 Object-based Permission action within the profile Similar with the following delivered User Groups UMEGROUP_Compliance Analyst UMEGROUP_Environmental Analyst UMEGROUP_Environmental Compliance Admin All actions, which begin with Frame.NAME (e.g. Frame.CalculationManager, etc.) and MenuPermissions (e.g. Tools.SystemChecks, etc.) cannot be mapped with EC 30 actions. These frame actions represent the following portal pages: EC 20 Action Mapping in EC 30 Frame.EmissionsAccounting Portal Page: Emissions Accounting Portal Page: Batch Processes Frame.BWReports Frame.ExceptionLog Frame.Reporting Frame.Tools Frame.Configuration Frame.AllXEM Frame.PLS Frame.CalculationManager Frame.MaterialManager Frame.TaskManagement Frame.PermitManager Frame.FacilityBuilder Frame.DashBoard Portal Page: BI Reports Portal Page: Exception Management Portal Page: Reporting Obsolete: the single Pages needs to be added manually in the Portal Role Obsolete: the single Pages needs to be added manually in the Portal Role Obsolete: the single Pages needs to be added manually in the Portal Role Obsolete: the single Pages needs to be added manually in the Portal Role. Facility Type Configuration Portal Page: Calculation Management Portal Page: Materials Portal Page: Task Editor + Task Management Portal Page: Permit Management See description below. Portal Page: Dashboard The xem RoleFile Frames are mapped in EC 30 in the Portal Content Pages: See Path in the SAP NetWeaver EC Portal Content: Portal Content Content Provided by SAP specialist Environmental Compliance 3.0 pages Migration of SAP EC 2017 SAP SE or an SAP affiliate company. All rights reserved. 239

240 The Frame.FacilityBuilder has in EC 3.0 four different Portal Pages: Emissions Management Facilities Facility Compliance Management Compliance Management The EC 3.0 Portal Page Energy Manager is similar to the Emissions Management with some label changes SAP SE or an SAP affiliate company. All rights reserved. Migration of SAP EC

241 8 Enterprise Energy Management EEM Introduction This document describes all facts concerning Enterprise Energy Management (EEM). The different chapters explain the topics installation, configuration, business process, application usage as well as reporting and the BI content. Note that EEM bases on SAP Environmental Compliance (SAP EC). Therefore, EEM uses several parts of SAP EC in order to meet the requirements of the EEM business process. For more information about the EEM integration into SAP EC, see chapter 8.3 EEM as Part of EC 3.0 SP11. Furthermore it is assumed that customers are familiar with the SAP Environmental Compliance application and at least do have a basic knowledge regarding the usage of the application and the SAP EC business processes. The EEM solution package contains the following items: Application content: An extractor is delivered which extracts data from the SAP EC database and afterwards transfers the data into the Business Warehouse. Configuration: SAP EC is customized into an EEM application by renaming application views and containing EC parameters and user defined field elements. BI Content: EEM specific Business Warehouse content to store EEM master and transactional data in the Business Warehouse. BI Reports: Several web applications will be delivered as well to support the analysis of EEM data with SAP BI. More information on these topics will be explained in upcoming chapters. In addition, this document will provide information on how to setup and install Enterprise Energy Management. 8.2 EEM Installation Description This chapter describes all relevant facts concerning the installation of the Enterprise Energy Management solution. Within the different sub chapters the topics Application installation, database content and BI content are explained. 8.3 EEM as Part of EC 3.0 SP11 Enterprise Energy Management bases on. This means that SAP EC will be customized to a specific version to form the EEM application. Furthermore, it is possible to use SAP EC and EEM together in the same environment. In this case, only some parts of the EEM customizing are applied to SAP EC system so that the users are still able to work with the SAP EC application as they are used to. In general, EEM will use existing functionalities and application views of the SAP EC application. EEM does not have any own application dialogs. Only a new extractor has been added which manages the data extraction of EEM specific data into the Business Warehouse. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 241

242 Through configuration and customization, the SAP EC application will be applied to the EEM application. The configuration and customization information is provided as database content and thus has to be imported into the database. For more information, see chapter EEM Database Data Import. In the field of SAP Environmental Compliance products, energies and emissions are materials and therefore their definition has to be done in the material management section. Furthermore production, energy and emission data always refer to a facility, e.g. a production line. This means that the maintenance of data is always done per facility and with regard to the SAP EC application the facility builder is the central instrument for the maintenance of transactional data. The extraction process of data has been changed as of EC 3.0 SP11 PL0. For more information, see SAP Note As of EC 3.0 SP11, EEM extraction supports only the extraction of consumption and emission values which are on hourly basis or 15 minutes basis. All other periods will not be extracted and the values which are not extracted to BI will be logged in the EC Log Viewer for further analysis. We recommend checking the EC Logs after EEM data have been transferred to BI. The period settings can be made in the EEM Configuration Integration BW Properties bw.eem.timeframe. Examples o Values supported for extraction (15 minutes data extraction example): o An hourly product amount of 40 QLI from 12:00:00 AM to 12:59:59 AM is split into four data records in BI.Four values of 10 QLI (12:00:00 AM - 12:14:59 AM, 12:15:00 AM - 12:29:59 AM, 12:30:00 AM - 12:44:59 AM, 12:45 AM - 12:59:59 AM). o Values supported for extraction (1 hour data extraction example): o A daily energy value from 12:00:00 AM to 11:59:59 PM is split into 24 records in BI. o A monthly energy value from 1st Jan :00:00 AM to 31st Jan :59:59 PM is split into 744 records in BI. The amount will be divided to 744. o Values not supported for extraction: o 17 minutes value from 12:00:00 AM to 12:16:59 AM o 3 hours on not fully hour base 12:12:00 AM to 3:11:59 AM If you have some special periods for the EEM extraction, which are not supported in the current EC version, create a customer message on SAP Component XAP-EM for the EC Maintenance Team to analyze your special time period requests. The following list provides a list of EEM corrections in EC 3.0.: Note number Description EEM Extractor extracts deleted records in initial load EEM delta data extraction process extracts on daily basis EEM extractor fails while extraction process is running Energy manager role has no access to parameters view Enterprise Energy Management does not extract 15 min values SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

243 Enterprise Energy Management delta extractor is very slow EC 3.0 Enterprise Energy Management initial data content EEM delta extractor does not return enough energy data to BI 8.4 EEM System Setup / Installation Since Enterprise Energy Management is part of the product delivery of the user has to perform the same steps of the SAP EC installation in order to get the EEM application running on the SAP NetWeaver platform. Therefore, it is recommended to use the installation steps of SAP EC. The installation sequence of the complete EEM application is the following (it is assumed that the system landscape is correctly setup and all requisites regarding the installation of the Enterprise Energy Management are fulfilled): 1. Deployment of the application files. Deploy all SAP EC 3.0 files as mentioned in the documentation. 2. Import of SAP EC database content. Import the Initial database content if this is your first version of SAP Environmental Compliance that you install in your system. Otherwise import the Delta database content. 3. Import of EEM Configuration database content. (Refer to SAP Note ) 4. Import of EEM Master Data database content. (Refer to SAP Note ) 5. Installation of SAP EC and EEM BI Content EEM Database Data Import The configuration and customization information of EEM is provided as database content. Note that the import of database content has to be performed after the installation of the EC application. This content consists of the following items: Configuration information, e.g. material types product and energy, currencies (Configuration data) Master data: Energy costs parameter set (Master data) The database content has to be imported with EC Import Export Tool into the database. Note that each item is a separate import file / folder. Herewith it is possible to import only some parts of the configuration / customization. The import of the configuration data and the master data are requisites for the usage of the EEM solution. Note The database import files can be downloaded from the SAP Note Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 243

244 8.4.2 Application Authorization Enterprise Energy Management will use the same authorization concept as SAP Environmental Compliance does. For detailed information, see chapter Enterprise Portal Roles. EEM also provide the custom role Energy Manager that contains the definition of the EEM specific user authorizations. Note The Business Warehouse part of Enterprise Energy Management will not provide any BW authorizations. The setup of BW roles and authorizations has to be performed by the customer itself EEM BI Content The BI content of EC 3.0 SP12 contains the whole EEM Info sources and packages. For more information about BI Content of EC 3.0 SP12, see SAP Note EEM BI Content Activation Guide This chapter describes the required steps to activate the BI example content of SAP Enterprise Energy Management (EEM). Prerequisites A SAP Enterprise Energy Management 3.0 system is configured as source system. The BI example content has been installed and activated. The EEM content is installed on the system via SAINT or SPAM. A user with a sufficient permission for activation of BI content is available Activation Steps To activate the SAP Energy Enterprise Management content, proceed as follows: 1. Enter the BI content activation Transaction (/RSOR). 2. Set Grouping to: "Only necessary Objects". 3. Choose "InfoObjects by InfoAreas" 4. Move the following InfoObjects catalogs below the info area "Enterprise Energy Management" to the activation area using the drag and drop function: o EEM Characteristics (/TDAG/EEM_CH01) o EEM Key Figures (/TDAG/EEM_KF01) Install the BI content to the source system "XEM" by clicking the Install button and choose "install". 5. Re-enter the BI content activation transaction (/RSOR). 6. Set Grouping to: "In dataflow before" SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

245 7. Choose "InfoProviders by InfoAreas" 8. Move the InfoProvider EEM All data (/TDAG/EEM_C00) below the info areas "Enterprise Energy Management" to the activation area by using the drag and drop function. 9. Install the BI content to the source system "XEM" by click the Install button and choose "install". 10. Re-enter BI content activation transaction (/RSOR). 11. Set Grouping back to: "only necessary objects". 12. Choose "Object Types" and expand "Process Chain" 13. Double click on "Select Objects". A popup window occurs. Sort the listed objects by the "Object Name" column. 14. Mark the following objects (all starting with "/TDAG/EEM") and choose "Transfer Selections": o /TDAG/EEM_ALL_DELTA o /TDAG/EEM_ALL_INIT o /TDAG/EEM_FACIC o /TDAG/EEM_MD_ALL o /TDAG/EEM_TEXTS o /TDAG/EEM_UDF 15. Install the BI content to the source system "XEM". 16. Re-enter BI content activation transaction (/RSOR). 17. Set Grouping to: "only necessary objects". 18. Choose "Object Types" and expand "Query Elements" and "Query" 19. Double click on "Select Objects". A popup window occur. 20. Select all query objects below "EEM All data" which starts with "EEM" and transfer those object by choosing "Transfer" 21. The following object have to be added (technical names): o EEM_CO2_EMISSION_DATA_EN o EEM_ENERGY_PER_PRODUCT_UNIT_EN o EEM_HOURLY_DATA_EN o EEM_WEEKLY_PE_DATA_PER_FAC_EN o EEM_NRGY_PER_WEEK_PER_FACAREA o EEM_ENERGY_COSTS_PER_FAC_EN o EEM_ENERGY_COSTS_PER_PROD_EN o EEM_WEEKLY_ENERGY_DATA_EN o EEM_WEEKLY_PE_DATA_PER_EQTYPE o EEM_WEEKLY_PRODUCTION_DATA_EN o EEM_ENERGY_COSTS_PER_FACILIT 22. Install the BI content to the source system "XEM". Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 245

246 8.5 Business Process Description This chapter explains the Enterprise Energy Management functionalities from a business process view. Enterprise Energy Management version 1.0 shall help customers to gather, maintain and report production, energy and emission data. The gathering and the maintenance of data is based on the facility structure of the company. The visualization and the reporting of data are performed with the use of SAP Business Warehouse. This means that the gathered or maintained data is transferred into the Business Warehouse. In the context of production, energy and emission data the topic Calculation of KPIs plays an important role. With the use of SAP BW / BI as reporting basis these requirements can be met. Furthermore, the EEM application will offer the functionality to define custom facility related key figures. This feature allows the creation of further facility related KPIs with regard to the production, energy and emission data. As an example, the key figure facility area size is delivered which stores the facility area in square meters. Within the reports this key figure can be used for the calculation of KPIs, e.g. the amount of consumed energy per square meter. The main reporting target is to increase the production efficiency to decrease the energy consumptions and as a consequence also the emissions data. The use of SAP Business Warehouse as reporting platform provides access to powerful reporting tools like the BEx Query Designer and the Web Application Designer Maintenance of Master This subchapter explains the most relevant facts regarding the maintenance and the use of master data in the EEM application. Within EEM there exist several master data objects, like Material or Facility. Prior to the maintenance of transactional data it is necessary to maintain the master data because the master data objects are part of the transactional data. As already mentioned products, energies and emissions are materials and therefore their master data is store in the same database table and in the same InfoObject in the BW. The master data is transferred to the Business Warehouse with the use of the extraction layer of SAP Environmental Compliance. Have a look at the most relevant master data objects of the EEM application: Facility Product Energy Emission Facility classifiers Facility user defined fields (UDF) The master data of these objects is maintained in the facility builder and the material management of the EEM application Maintenance of Transactional Data Transactional data in the field of EEM means production, energy and emission data records which dispose of date and time stamp and a key figure which represents the amount of manufactured product, of consumed energy and or ejected emission data. Within the EEM application the facility builder provides access to the production, energy SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

247 and emission data records. In general, there are several possibilities how to maintain production, energy and emissions data in the EEM application: Manually maintenance of data: Manual maintenance of data is done in the facility builder section of the EEM application. There the user selects a facility for which he wants to capture production, energy and / or emission data. In the facility builder, the user has to perform the following steps in order to create transactional EEM data: The detail view Production materials must contain all products and energies that are involved in the production process at this facility. Note that this is also necessary in case transactional data shall be imported through the Web Service interface or with the use of data entry tasks. Note that the materials which can be assigned here have to be maintained in the material management before. After assigning the production materials the transactional data can be maintained. Production data and energy consumptions are maintained in the detail view Production data whereas emissions data is maintained in the detail view Emissions. Furthermore, the details views Production data and Emissions can also be used in order to visualize the data that is currently stored in the system. It is possible to select a certain time frame e.g. the last month in order to restrict the amount of data records that shall be displayed. Import of data using Web Service interface EEM offers the possibility to import production, energy and emission data with the use of Web Service technology. This means that EEM offers an interface with which transactional data can be imported into the system. The requisites of the data import are that the production, energy and emission materials are assigned to a facility. Furthermore, it is necessary to setup the Web Service connection in order to enable the import of data. The setup of the Web Service interface is done under Configuration Integrated Systems. Within the Integration of the Facility Builder the mapping between the Web Service data fields and the production, energy and emission records is defined. For more details about the usage of Web Services in EEM, see chapter Overview of EC Web Services. Data entry tasks The third possibility to maintain transactional data are the so-called data entry tasks. Data entry task are similar to manual maintenance of transactional EEM data. The use of data entry tasks offers the possibility to manage and schedule the data entries for all involved users. EEM allows the delivery of data entry task per E- Mail so that users can be notified and requested to enter data. Consider the following facts: o A data entry task refers to at least one facility. It is possible to create a data entry task for all facilities or per facility. o The date information of the data entry task refers to the date setting of the task itself. In case it is a weekly task the records will also have a weekly validity (duration). o It is not possible to specify the time information. The smallest date / time interval is daily. Recommendation We recommend that you consider the following guidelines for data maintenance: o Data always has to be maintained for a single facility. Data combinations from different facilities e.g. production data from facility A and energy data from facility B are not supported with EEM. o Production, energy and emission data must always dispose of a time frame, e.g. 12 AM to 12 PM. o The timestamp for a complete day can be maintained as 12 AM 11:59:59 PM the same day or as 12 AM 12 AM the following day. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 247

248 o Production and energy data do not have a physical dependency; the link between products and energies is drawn using the facility, date and time information. It is recommended that production and energy data records dispose of identical time periods so that they can be easily linked together. Nevertheless, the EEM solution does supported different time constellations. For more information, see chapter 8.6 Data Extraction into Business Warehouse. Since production and energy data records are linked using their facility, date and time information these attributes needn t be changed. A change of these attributes requires an initial data extraction into the BW. Only emissions data which refers to energy consumption will be extracted to the BW. To maintain emissions data related to energy consumption it is necessary to define a calculation script which calculates the emission information according to the amount of consumed energy. Herewith it is ensured that the emissions refer to energy. It is also possible to maintain manual emission data but it is recommended to calculate emission data out of energy consumption. Only materials that are marked as product or energy will be considered for BW extraction. Note that the EEM application allows the maintenance of production data with materials that are not marked as product and energy. Emission materials do not have to be marked explicitly with a certain material type as products or energies have to be Calculation of Emission Data As already mentioned the consummation of energy during production leads to the emission of substances. In regard to the functionality of Enterprise Energy Management it is recommended to calculate emission data out of the energy consumptions. This means that with the use of a certain mathematical calculation routine the amount of consumed energy is directly transformed into an emission of one or multiple substances. The EEM solution therefore uses the so called Consumption-based Calculation. For details about the use of consumption-based calculations, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal at Within the Calculation Manager the user defines the consumption-based calculations, e.g. for each emission a single calculation. The calculation of emission data out of energy data requires the handling of the input and output units for instance, the energy data unit is kwh whereas the emission target unit is kg. Here it must be assured that the calculation returns the appropriate target unit. The assignment of the consumption-based calculation is done in the Production materials view of the Facility Detail in SAP EC in the Consumption material view. Note that it is possible to assign multiple calculations to energy. Furthermore, it is necessary to explicitly mark a consumption based calculation in order to use it. As you can see in the figure there is a calculation assigned and active for the energy Electricity. By the way this calculation is available for all energies and all products but it is only assigned (activated) for the energy Electricity. In order to assign or activate a consumption-based calculation it is necessary to mark the Assign Checkbox. By default, this checkbox is not marked. The calculation of the emission data is executed in the Emissions section of the facility detail. Pressing the (Re) Calculation Button in this view opens a popup window in which the selection of the energies has to be performed. Note that the execution of consumption-based calculations for multiple energies may take several minutes. The execution of a Re-Calculation requires an additional step before the calculation can be execute. In order to enable the re-calculation, it is necessary to open the data diagnostics view of the facility detail SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

249 This figure currently shows the data diagnostics entry view of the facility Maschine A1. As you can see there is no data visible in the bottom table view of the Consumption Values. To show the emissions data, it is necessary to apply the filter settings. Therefore, the energy which emissions data shall be re-calculated has to be selected as consumption material; here the material Electricity has been selected. Afterwards apply the maximum row count if applicable (default value is 200) and press the button Show result in order to visualize the consumption data. In the result table the calculation state of the energy consumption record(s) will be changed to Has to be calculated. This is done by marking the energy consumption records as to be calculated. Either press the button Select all to be calc. or select the checkbox of an energy record in the column Has to be calc. Afterwards the emission can be re-calculated. Note that the re-calculation can also be executed from this dialog Energy Costs With EEM it is possible to maintain and report energy costs. The energy costs maintenance is divided into two different steps: Within the parameter section of the facility builder the user has to maintain the energy cost coefficients. Therefore, he must assign the facility parameter set energy cost coefficients to his facility. Afterwards he must choose the energies for which the energy cost coefficients shall be maintained. Note that the energy cost coefficient always refers to the SI Unit of the energy. It is not possible to bind the energy cost coefficient to a different unit. The energy cost coefficient parameter set is part of the delivery of EEM. It is mandatory to use this parameter set to maintain energy costs. User specific parameter sets will not work. Note that in this dialog only the coefficients are maintained. It is also possible to specify the energy cost coefficient factor with a scientific number format, e.g. 2E-8. The application will automatically set the decimal value of the cost coefficient after saving. The currencies are maintained in the facility detail. Furthermore, the maintenance of the energy cost coefficients has to be performed for every facility and the facility parameter sets also offers the possibility to define validity periods of the energy cost coefficients. This means that the energy cost coefficients can be bound to certain validity period. Note that this solution basically enables the user to maintain daily cost coefficients. Unfortunately, daily energy cost coefficients will probably lead to performance issues regarding the data extraction into the BW. Furthermore, with this dialog a daily maintenance of data is not manageable. Therefore, it is recommended to maintain energy cost coefficients on a monthly basis. The maintenance of the energy cost currency is done in the User Defined Fields section of the facility builder. There the user can choose the appropriate currency for his facility. Note that the available currencies dependent on the values from the LOV dialog. To create new currencies, the user has to open the Currency section in the LOV dialog. The currency section is located under Module independent UDF Pick list Values Currencies Alternatively. Use the LOV search and look for ENERGY_COST_UNITS. Create new LOV items in this section, you can take Euro as an example. Note that the CODE field must contain the international currency code, e.g. EUR for EURO and USD for US Dollar. After configuring new currencies, it is necessary to reset the buffer. This is done under Tools Reset Buffer. Afterwards the newly created currencies are available within the User Defined Fields area of the facility builder. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 249

250 8.5.5 Generic Facility Related Key Figures Enterprise Energy Management 1.0 provides the functionality to define customer specific key figures which can be included in the EEM transactional data. Herewith the user gets more flexibility in reporting and in creating KPIs. To create further facility related key figures the user has to carry out the following steps: 1. Definition of the key figure as UDF element. This is done in the LOV section of the Configuration 2. Assignment of the newly created UDF element to the EEM UDF object. 3. Configuration of the BW Settings in the EEM application under Configuration User Defined Fields Assignment. 4. Implementation of the key figure in the BW. 5. Extension of the EEM Facility UDF InfoObject in the BW, application of the corresponding InfoSource 6. Application of the ODS and the InfoCube in order to include the newly created key figure in the EEM transactional data. The delivery of EEM 1.0 includes the facility key figure Facility area (size). Technically this key figure is realized as a User Defined Field (UDF) of the facility. The maintenance of the key figure is done in the UDF section of the facility builder. Consider the aggregation settings of these key figures and set except aggregation for these key figures if necessary. For more details about the usage of UDF and BW, see chapter User-Defined Fields for Master Data in BW Units and Dimensions With regard to production, energy and emission data units and dimension play an important role. In general, a dimension contains several units, e.g. the dimension Energy contains the units J and KWH. Within a dimension the units do have mathematical dependencies, this means that a value can be converted from one unit into another one, e.g. 1 KWH = J. Note that the automatic conversion of units from different dimensions is not possible! Within the EEM the maintenance of the dimensions and its units is done under Configuration Units & Dimensions. Note the following information: Each dimension contains a unit which is defined as the SI unit (base unit). The SI Unit of the dimension shouldn t be changed. As mentioned in the chapter Energy Costs the energy cost coefficients refer to the SI Unit of the energy. In case the SI Unit is changed it is necessary to run an initial data extraction into BW. With EEM it is possible to define a reporting unit for each dimension. This means that all transactional data will be transformed using the reporting unit as target unit. This offers the possibility to maintain data with different units and to report on data which disposes of the same unit. The definition of the reporting unit is done under Configuration Units & Dimensions in the EEM application. Note that the setting of the reporting unit is not mandatory. Nevertheless, it is recommended to define a reporting unit in order to provide a common basis for data analysis and reporting SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

251 8.6 Data Extraction into Business Warehouse This chapter explains the most relevant information concerning the extraction of EEM data into the Business Warehouse. The Business Warehouse is used for data storage and reporting basis. In order to transfer data from the EEM application into the Business Warehouse the extraction framework of SAP Environmental compliance will be used. Furthermore, an EEM specific extractor has been implemented which is responsible for the extraction of data out of the SAP EC database and the transfer of data into the Business Warehouse. The extraction of data is divided into two areas: The extraction of master data (Master data, texts and hierarchies) The extraction of transactional data The following chapters describe the setup and configuration of the extraction process, the extraction of master data and the extraction of transactional data Setup of the Extraction Process The extraction framework uses RFC for the communication with the Business Warehouse. Therefore, the Business Warehouse system and the connection information have to be maintained under Configuration Connectable R3 of the EEM application. Have a look at the next screenshot for details: Note that the specified user must dispose of the BW RFC roles. For more details, refer to the BW Content Installation Guide that describes all relevant facts concerning the configuration and setup of the Business Warehouse part of the application. After a successful setup of the BW connection it is necessary to start / activate the extraction server so that the BW request can be processed. The management of the extraction server is located under Tools Extraction Server Monitor. If the extraction server is not running it will not be possible to load any data to the Business Warehouse. Note that the extraction server has to be started manually. Thus, in case the Web Application Server is restarted (e.g. due to system maintenance) it is necessary to restart the extraction server manually again. Remember to restart the server in case of system reboot because this can lead to problems in case the BW data loads are scheduled using process chains Extraction of Master Data The Business Warehouse content of Enterprise Energy Management deals with the following master data objects: /TDAG/FACILITY This InfoObject stores information of the facilities which are maintained in the EEM application. Beside master data this InfoObject does also support multilingual texts and hierarchies. Within the EEM application the user can define his own hierarchy structures, e.g. a regional hierarchy of his facilities. /TDAG/MATERIAL This InfoObject stores master data and texts of all materials that are maintained in the EEM application. As already mentioned products, energies and emissions are also materials and their master data and texts are Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 251

252 stored in the InfoObject /TDAG/MATERIAL as well. To differ between products, energies and emissions the following InfoObjects have been introduced: o /TDAG/PRODUCT o /TDAG/ENERGY o /TDAG/EMISSION These InfoObjects have been created with reference to the InfoObject /TDAG/MATERIAL and therefore the master data and the texts are inherited. /TDAG/EEMFACIC This InfoObject stores the facility classifiers and identifiers. Within EEM the facility classifiers are used to specify the equipment type of a facility. In addition, there is a BI report which shows product and energy data related to equipment type. It is possible to extend this InfoObject and to add new facility classifiers. /TDAG/EEMUDF This InfoObject stores the master data of the facility UDF attributes, e.g. the generic facility related key figure Facility Area size. The user here also has the possibility to create customer specific UDF attributes or key figures. For each of these InfoObjects an InfoSource exists which handles the data extraction from the database into the Business Warehouse. The scheduling of the extraction of master data, texts and hierarchies is realized in an own process chain. This chain is included in the init and delta meta chain which loads the transactional EEM data Extraction of Transactional Data The extraction of transactional data is managed by process chains; one chain is responsible for the initial data load the other one performs the delta data loads. There is one InfoCube in the BW which stores the transactional data. This means that production, energy and emission data is stored in the same InfoCube. Due to the fact that the relation between products and energies and emissions is drawn upon their facility, date and time information there are many different time / date constellations between products and energies / emissions possible. Note that it is recommended to maintain production, energy and emissions data always with the same date and time periods. Consider the following points: Within the BW Properties (Configuration BW Properties) the user has to specify the time interval size. According to the time interval size the extraction layer will split the product and energy and emission records. The time interval size has to be specified in seconds, e.g for an extraction of hourly values. The extraction layer only accepts the values 900 and It is recommended to use smaller time frames than the different product, energy and emission records do have. The extractor will first analyze the different time interval constellations between product and energy records. This means that according to the maintained time information of the different records the extractor will build suitable time intervals SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

253 Example Production data is available per day. This means we have records from 00:00:00 AM to 11:59:59 PM. Energy consumptions are available every 8 hours. The resulting time intervals are 00:00:00 8:00:00 AM, 8:00:00AM 4:00:00 PM and 4:00:00 PM 11:59:59 PM. After the calculation of the time intervals from the different product and energy records the time intervals according to the configuration in the BW properties will be calculated. The time information of product, energy and emission records will always refer to full hour in the BW. This means that in case there is data maintained in the EEM application which does not match full hour the extraction layer will perform a transformation of the record to full hour. There will be 2 time intervals for each product, energy and emission record in the BW in case the data is not maintained with full hour information. Example Product record from 4:30:00 AM 6:20:00 AM 4:00:00 AM 6:00:00 AM and 6:00:00 AM 7:00:00 AM The extraction of data is always performed day by day. This means that the all available data records are analyzed day by day. Afterwards the split of data according to the time intervals and the time interval configuration is performed. In case there is weekly data available in the EEM application the extractor will split the weekly data into daily data. In case there are several products at the same facility and at the same date and time it is necessary to do a distribution of the consumed energies. Here the assumption is made that the higher the product amount the higher the energy consumption is. Thus, the extraction layer distributes the energy consumptions according to the product quantities. Note that in practice the amount of consumed energies during production depends on several factors like the production process, the product size, If there is production data and no energy consumptions available at the same facility, date and time than the extractor will transfer energy as NOT SPECIFIED to the BW. The same procedure will be performed in case there is energy data and no production data available at the same facility, a certain date and time. In case there are production, energy and / or emission data records with time intervals smaller than one hour then the extraction layer will transform this records into full hour matching records. Energy and emission data do always have the same date and time intervals because the emission data is calculated according to the energy consumptions and as a consequence the time information of the energy record is inherited. Within EEM the user has the possibility to define reporting units and SI units for each dimension. A reporting unit is the one which is extracted to the BW. This means that the extraction layer performs a transformation of the data in case the product / energy data records are maintained with a different unit as the reporting unit. It is up to the user to specify the way units have to be managed in EEM. Since product, energies and emissions are linked together during the data extraction it can happen that only product energy and no emission data is available. If this is the case the emission part of such a record is set to the emission 999 with value 0. This value is set in the update rules of the InfoCube. Customers can adapt this InfoSource and can set their own values to show up. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 253

254 8.6.4 BI Data Model This chapter gives a brief overview of the BI data model of Enterprise Energy Management 1.0. The data model shall serve for a better understanding and orientation in the field of EEM reporting. For a detailed description of the Enterprise Energy Management BI content refer to the documentation SAP_Enterprise_Energy_Management_BI_Documentation.doc. Have a look at the next table which contains all objects that are part of the transactional data model of the EEM InfoCube: BI Object Description Key fields Facility Product Energy Emission Date from Date to Time from Time to Method of Production Method of Energy Scenario ID The facility to which the production, energy and emission data refers to. Master data access possible. The product information. Master data access possible. The energy information. Master data access possible. The emission information. Master data access possible. Start date of the production, energy or emission record. End date of the production, energy or emission record. Start time End time Calculation Method (List of Value) Calculation Method (List of Value) Facility Scenario ID Additional characteristics Facility identifier and classifier Classifiers and identifiers of the facility. Possibility to customize the EEM application according to user specific requirements. Time characteristics 0Calday 0Calweek 0Calmonth 0Calyear Calendar day Calendar week Calendar month Calendar year Key figures Product quantity Energy quantity Emission value Energy cost Facility area The amount of manufactured product. The amount of consumed energy. The emission value due to the energy consumption. The cost of the consumed energy. The size of the facility area, e.g m² SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

255 Note that the BW objects Facility, Product, Energy and Emission are master data Info Objects and therefore the master data is also accessible within the BI reporting. As already mentioned these BI objects define the transactional data record as it is stored in the EEM InfoCube in the BW. The data model of transactional data of a single facility is the following: Energy EMISSION PRODUCT Energy EMISSION Energy EMISSION As you can see in the figure, the production of a certain product refers to 1:n energies. The consummation of energy can lead to several emissions. As a consequence this means that the amount of manufactured product is multiplied according to the number of consumed energies and ejected emissions. This constellation has to be kept in mind when reporting on EEM data. Technically this scenario is solved with the use of except aggregation in the BW. But note that the except aggregation only works in case the manufactured product always uses the same energies (that for the manufactured product always the same energies are maintained) and that the energies always eject the same emissions. Otherwise the data model will become incomplete and the aggregation of data gets faulty BI Reporting With EEM 1.0 a couple of BI reports are delivered. Furthermore, each Query is published in a web application and these web applications can be easily included in the EEM application. The BI reports shall serve as a first introduction into EEM BI reporting. In addition, these reports only meet a certain part of customer requirement regarding business reporting. It is up to the customers to define their own specific reports to meet their requirements. In the following some basic properties and each of the delivered reports will be explained. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 255

256 Common Properties / Remarks The delivered BI reports all focus on the reporting of transactional EEM data. The usage of each report will be explained in the next chapters. Due to the fact that product, energies and emissions are stored in the same InfoCube (as a consequence also their key figures) it is important to consider their aggregation properties: For each energy there can be 1:n emissions (as a consequence there are several data records with the same energy amount). This means that in case there is more than 1 emission, the aggregation of the energy amount is disabled. This scenario is also valid for the production quantity because here it can be the case that there are several energies which each can have several emissions. Here the aggregation of the production amount must be suppressed in case there is more than one energy emission record. With regard to the aggregation of the key figures there is another fact which needs to be considered: Assuming that we have one product which is manufactured with 3 energies within a monthly period (the emissions can be excluded but the principle would also be valid). The data records are maintained every 2 hours. If there are gaps in the maintenance cycle, e.g. at a certain day and time there are only 2 of the 3 energies maintained between 00:00:00 and 2:00:00 than the aggregation will not work because the third energy is missing. EEM 1.0 is currently not able to manage this situation during extraction. In this case, it is mandatory that the third energy is maintained with value 0 in the EEM application. Each web application offers a navigation panel with which the user is able to filter the report data. Have a look at the following screenshot which gives a graphical review: With the use of a navigation panel it is possible to filter or re arrange the data layout of the web application. Note that the navigation panel affects all items of the query, e.g. a table and a chart. The item structure contains all key figures that are part of the report. By filtering on structure, it is possible to exclude certain key figures from the report. The reporting periods of all web application basically refer to calendar weeks. As mentioned above the extraction of data into the BW uses a configurable time interval size which supports time intervals from 1 hour up to daily data. This means that the smallest available time interval can be 1 hour. When changing this interval, it is necessary to do an initial data load. SAP BW / SAP BI is not able to display the time 00:00:00. In this case the query displays # instead. Consider this as a fact and not as a bug of the extraction layer. There is a workaround in order to solve this problem: Within the update rules of the ODS or the InfoCube it would be possible to implement a routine which sets 00:00:00 to 00:00:01 so that the query will show time information instead of #. But then it must be clear that 00:00:01 means 00:00: SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

257 Integration of BI Reports into EEM Application With Enterprise Energy Management, it is possible to access BI reports directly from the application. Note that it is helpful to enable Single Sign On (SSO) between the EEM application and the BI system which contains the EEM BI content. The EEM solution automatically performs the integration of the BI reports into the external reports section of the reporting area of EEM. Due to the fact, the BI reports refer to the customer BW system it is necessary to apply URL links, otherwise the report cannot be opened using the EEM application. The URL links are configured like It is necessary to replace the URL link with the appropriate BW server connection information. Customer-specific BI reports can also be included in the external report section Weekly Production Data This report shows production data of all facilities over calendar week. Furthermore, the web application graphically visualizes the production data. Have a look at the web application screenshot for details: The chart on the right top visualizes the production data of all products at all facilities per calendar week. This means that the product quantities at the different facilities are aggregated. A data row point in the chart matches the result of the calendar week. Note that an aggregation of the product quantities is not possible if the product quantities do have different units. In case there are different units it is necessary to filter only those products which have the same units. The filtering can be done by using the navigation panel. The char on the bottom right in Error! Reference source not found. shows production data over time per facility. Note that the aggregation of the product quantities does not work in case there are products with different units. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 257

258 If there are products with different units, it is necessary to filter the data in the web application so that aggregation is possible. Consider the fact that regarding production efficiency, it is better to compare those facilities that manufacture the same products Weekly Production and Energy Data This report shows product data and energy consumptions of all facilities over calendar weeks. Have a look at the next figure for details: As you can see in the graphic the energies Gas, Electricity and Steam are displayed. These key figures are restricted key figures of the query / web application which filter those energy quantities which refer to a certain energy. Note that such a restricted key figure uses the energy keys for identification. The problem is that in every EEM system this identification information can vary and thus the restricted key figure will not work. Therefore, it is necessary to apply this query / web application in the customer system in order to ensure the correct functionality. In addition, it is necessary to define further restricted key figures for each energy. EEM 1.0 delivers the query / web application as shown in Error! Reference source not found.. This web application does show production and energy data on an hourly basis by not using restricted key figures. This report can be adapted to realize a weekly display of product and energy data. With regard to the display of data in the two charts it can be determined that the visualization of the product quantity is not that good. The reason for this is that the scaling between product and energy quantity does severely vary. Here are some hints how to solve this issue: Definition of a suitable reporting unit in EEM so that the scaling between product and energy quantities does not vary too strongly SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

259 Change the display options of web applications. There it is possible to define a logarithmic scaling of the chart. Choose an appropriate logarithmic basis for the display of data. Introduce a second value axis for the chart and assign the product quantity and the energy quantities to different axis Weekly Energy Consumptions This report shows energy consumptions of all facility per energy and per calendar week. See the next graphic for details: Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 259

260 Energy Consumption per Product Unit, Facility, and per Week This report shows production data, its energy consumptions and the portion of energy per product unit. Herewith the user gets an overview of the amount of consumed energy product unit. This key figure will also help in determining the production efficiency of facilities, such as the higher the energy consumption per product the less efficient is the facility. The key figure Energy per product unit is a calculated key figure of the query / web application. Note that this key figure directly uses the energy and the product key figure. Different to the restricted key figure a calculated key figure does not need to be adapted. This report will calculate the energy consumptions per product unit, it is also possible to define calculated key figure which refer to a certain amount of products, for example, the energy consumption per 1000 product units SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

261 Hourly Production and Energy Data This report reflects the way data is stored in the BW. In addition this report shows the smallest available time information of the product and energy records. Have a look at the following figure: Note that SAP BW / SAP BI are not able to display the time information 00:00:00. In this case SAP BW / SAP BI display # instead. In case the time intervals are always the same it might also be interesting in displaying the time information in reports that use date periods greater than calendar day. Use this report in case it is necessary to report EEM data on basis of hours. Furthermore, the use of time information (assuming that there is data with time periods smaller than a single day available) offers to chance to compare production time periods with regard to production efficiency. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 261

262 Weekly Energy Costs This report gives a review of the energy costs of all consumed energies per facility and per calendar week. See the next screenshot for details: As you can see in the screenshot, the data is also visualized as a line chart. Within the query / web application the two key figures Energy quantity and energy costs are set to summation when their result is calculated. Note that in case there are different energy units or even different currencies the summation will not work. In this case, it is necessary to perform a transformation of the units. For more information about the calculation of the energy costs, see the chapter Energy Costs SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

263 Total Energy Costs This report calculates the energy costs per product unit. In addition, this report shows the amounts of manufactured products, the related energy costs per calendar week, per facility and per product. Have a look at the following screenshot for details: It can be stated that the result area of the Energy costs per product unit is empty. This is a property setting or the query. Consider the following facts for this query: The energy cost key figure displays the costs of all energies that are involved during the production of a product at a certain facility. The calculation of the energy costs is done per energy. Energies do have different energy cost coefficients and thus there is no linear distribution between the different energies regarding their costs. The energy cost coefficients of the same energy may vary between different facilities due to the fact that the energy costs depend on local energy providers. Because of the facts from 2, 3 and 4 the result calculation of the energy costs per product unit will lead to an incorrect result. In case there is the requirement to get this information, it is necessary to add energy into the slice of the query. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 263

264 Energy Consumptions per Facility Area This report calculates the amount of consumed energy per facility area size. Herewith it is possible to get detailed information about the dependency of energy consumption with regard to the size of the facility at which the energy has been consumed. As you can see in the figure the summation of facility area is suppressed or rather set to maximum. In the context of the facility area the summation does not make much sense. Note that if energies do have different units the summation of the key figure energy per facility area will not be executed. In this case, it is necessary to define unit conversions in order to enable summation. The summation of data over different facilities is also suppressed by this report because of the fact that this report focuses on the data of each facility SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

265 CO2 Emission Data per Product and Energy With EEM it is possible to maintain and report on emission data that refers to consumed energies. Have a look at the next screenshot in order to get a graphical review of this report: This query filters from all available emissions only the CO2 data. The user does have the possibility to create a similar report which shows all emission data of all energies. As you can see in the graphic only the facility Maschine A1 does contain emissions data the other facility does not have emissions data yet. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 265

266 Product and Energy Data per Equipment Type The equipment type is a special classifier of a facility which enables the possibility to perform analysis of equipment / facilities which do have the same type (classifier). Note that the equipment type is just a single example for a facility classifier. With EEM it is possible to define any classifiers as there is a need to. See the next figure for details: SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

267 8.7 Enterprise Energy Management BI Content As already mentioned the EEM solution package contains BI content which has to be imported and activated in a SAP Business Warehouse system. The EEM BI Content basis on SAP Environmental Compliance BI content this means that SAP EC and EEM do have common BW content objects e.g. the InfoObjects /TDAG/FACILITY and /TDAG/MATERIAL. For details about the BW system configuration and setup, see chapter 6.11 BI / BW Content. This document describes all relevant facts about how to install SAP EC BI content (EEM uses the same procedure) into SAP Business Warehouse. Note that it is mandatory to install the SAP EC BI content first. Otherwise the EEM BI content cannot be installed correctly. A detailed description about how to install and activate the EEM BI content will follow later in this chapter. Have a look at the following list for details about the EEM specific BI content: InfoArea: Enterprise Energy Management InfoObjects: characteristics, key figures and units InfoSources: InfoSource for loading transactional EEM data, InfoSource for loading EEM facility classifiers and one InfoSource for loading EEM facility UDF data ODS: Delta Management of transactional EEM data InfoCube: Stores production, energy and emission data ProcessChains: Scheduling of EEM data loads Queries and web applications for EEM BI Reporting BI Content Description As energy cost soar and the importance of businesses Going Green increases being able to plan and control, energy usage becomes a more strategic issue than ever before. Most companies do not have the detailed information concerning energy usage and cost that are required for both energy usage & energy cost reduction programs. Conserving and optimizing the use of resources is imperative in today s operating environment. By having such detailed information plans can be created & executed upon that will support the corporate & social goals of energy reduction. This solution will bring for the first time a fully integrated picture of enterprise energy management data with the business processes. The gathering of near real time energy consumption and their connection to business (or financial) data further enables taking activities concerning energy usage reduction and cost reduction. This solution will enable and support companies in their endeavors to reduce the cost & usage of energy in their business. This solution will allow the marrying of data collected via equipment and sensors on the shop floor and in buildings, to the data in the ERP system. Part of energy management includes the support of green initiatives. This includes items such as calculating CO2 emissions, and calculating the carbon foot print of the company and its products. With this in mind, integrating the energy management composite application into an application that monitors Environmental Compliance becomes a value-added process. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 267

268 InfoArea The InfoArea contains all BI content objects from the Enterprise Energy Management BI solution part Web Templates Weekly Production Data Template EEM_WT_WEEKLY_PRODUCTION_DATA displays the amount of manufactured product (s) per calendar week and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, facility and calendar week. Furthermore, the report data is visualized in a chart Weekly Production and Energy Data Template EEM_WT_WEEKLY_PROD_ENER_DATA displays the amount of manufactured product (s) and consumed energies per calendar week and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility and calendar week. Furthermore, the report data is visualized in a chart Weekly Energy Consumptions Template EEM_WT_WEEKLY_NRGY_DATA_EN displays the amount of consumed energy per calendar week and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among energy, facility and calendar week. Note that the aggregation of energies does not work in case there are different energies with different units Energy per Product Unit and per Week Template EEM_WT_NRGY_PER_PRODUNIT displays the amount of consumed energy per product unit, per calendar week and per facility. In addition, the product quantity and the energy quantity are displayed as well. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility and calendar week SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

269 Hourly Production and Energy Data Template EEM_WT_HOURLY_PE_DATA_EN displays the amount of manufactured product(s) and consumed energies per calendar week, hour (time from time to) and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility, time from, time to and calendar week Weekly Energy Costs per Facility Template EEM_WT_WEEKLY_ENERGY_COSTS displays the energy costs of the consumed energies per calendar week and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility and calendar week Total Energy Costs and Energy Costs per Product Template EEM_WT_NRGY_COSTS_PER_PROD_EN displays the production amount, the total energy costs per product and the energy costs per product unit. These key figures are shown per calendar week and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility and calendar week Energy Consumptions per Facility Area Template EEM_WT_NRGY_PER_WEEK_PER_FAREA displays the amount of consumed energy per facility area, per calendar week and per facility. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility and calendar week (CO2) Emission Data per Product and Energy Template EEM_WT_WEEKLY_CO2_EMISS_DATA displays the amount of emitted CO2 per manufactured product, per consumed energy, per calendar week and per facility. In addition, the product quantity and the energy quantity are displayed as well. The template provides a navigation panel with which the user can control the report data. He has the possibility to filter among product, energy, facility and calendar week. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 269

270 Product and Energy Data per Equipment Type Template EEM_WT_DATA_PER_EQUIP_TYPE displays the amount of manufactured product and consumed energy per calendar week and per equipment type. The template provides a navigation panel with which the user can control the report data. The user has the possibility to filter among product, energy, equipment type, and calendar week Queries Weekly Production Data per Facility Query EEM_WEEKLY_PRODUCTION_DATA_EN displays the amount of manufactured products per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation to calculate the correct product quantity in case of multiple products Product and Energy Data per Week and per Facility Query EEM_WEEKLY_PE_DATA_PER_FAC_EN displays the amounts of manufactured products and its energy consumptions per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. The query uses restricted key figures for every energy. By default, the restricted key figures, Gas, Steam and Electricity are delivered SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

271 Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Electricity ELECTRICITYAMOUNT Restricted key figure on energy electricity Gas GAS_AMOUNT Restricted key figure on energy gas Steam STEAM_AMOUNT Restricted key figure on energy steam Weekly Energy Consumptions Query EEM_WEEKLY_ENERGY_DATA_EN displays the amount of consumed energies per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Energy /TDAG/ENERGY - Columns Name Technical Name Value Restriction / Calculation: Energy quantity /TDAG/NRGYVAL - Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 271

272 Energy per Product Unit, Facility, and per Week Query EEM_ENERGY_PER_PRODUCT_UNIT_EN displays the amount of consumed energy per product unit, per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. The key figure energy per product unit is a calculated key figure. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Energy /TDAG/ENERGY - Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Energy quantity /TDAG/NRGYVAL - Energy per product unit NRGY_PER_PUNIT Calculated key figure (energy quantity / product quantity) Hourly Production and Energy Data Query EEM_HOURLY_DATA_EN displays the amount of manufactured products and consumed energies per calendar day, time (time from time to) and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Energy /TDAG/ENERGY Time from /TDAG/TIMEFRO Start time Time to /TDAG/TIMETO End time SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

273 Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Energy quantity /TDAG/NRGYVAL Weekly Energy Costs per Facility Query EEM_ENERGY_COSTS_PER_FAC _EN displays the total energy costs per consumed energy per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. The key figure total energy costs is a calculated key figure. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Energy /TDAG/ENERGY - Columns Name Technical Name Value Restriction / Calculation: Energy quantity /TDAG/NRGYVAL - Energy costs /TDAG/NRGYCOST Energy Costs per Product Unit Query EEM_ENERGY_COSTS_PER_PROD_EN displays the energy costs per product unit per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 273

274 Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Energy costs /TDAG/NRGYCOST - Energy costs per product unit NRGYCOSTS_PUNIT Calculated key figure Energy Consumptions per Facility Area Query EEM_NRGY_PER_WEEK_PER_FACAREA displays the amounts of consumed energies per facility area per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Energy /TDAG/ENERGY - Columns Name Technical Name Value Restriction / Calculation: Energy quantity /TDAG/NRGYVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Facility area /TDAG/FACAREA - Energy per facility area NRGY_FACAREA Calculated key figure SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

275 CO2 Emission Data per Product and Energy Query EEM_CO2_EMISSION_DATA_EN displays the CO2 emissions amount per product, per energy, per calendar week and per facility. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Energy /TDAG/ENERGY - Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Energy quantity /TDAG/NRGYVAL - Emission quantity /TDAG/EMISVAL Product and Energy Data per Equipment Type Query EEM_WEEKLY_PE_DATA_PER_EQTYPE displays the product and energy quantities per equipment type and per calendar week. The query is used in the corresponding web template. The query does not use any variables, filtering is enabled on facility and calendar week. Rows Name Technical Name Value Restriction / Calculation: Facility /TDAG/FACILITY - Calendar week 0CALWEEK - Product /TDAG/PRODUCT - Energy /TDAG/ENERGY - Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 275

276 Columns Name Technical Name Value Restriction / Calculation: Product quantity /TDAG/PRODVAL This key figure uses except aggregation in order to calculate the correct product quantity in case of multiple products. Energy quantity /TDAG/NRGYVAL EEM InfoCubes InfoCube </TDAG/EEM_C00stores the complete EEM transactional data. It contains the products, the energies and the emissions which refer to Enterprise energy management. All reports are based on this InfoCube DataStore Objects EEM All Data DataStore object</tdag/eem_ds0 is connected to the InfoSource which is responsible for the data extraction of EEM data. The data store object manages the delta data loading. Furthermore, the master data lookup is performed in the update rules of the ODS, e.g. the UDF currency. The following delta update is supported for this DataStore object: Delta update: New Status for changed records Data Source: xem EEM InfoSources EEM Products + Energies + Emissions InfoSource /TDAG/EEM_ALL manages the data loading of Enterprise Energy Management. The Enterprise Management data is extracted from the SAP EC database with the use of specific extractor. The data extracted with the use of the InfoSource is forwarded into an ODS. The InfoSource supports delta data load SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

277 Key Figures Product Quantity Key figure /TDAG/PRODVAL stores the production quantity. Aggregation: Exception Aggregation: Calculation: Restriction: Summation Last value, /TDAG/ENERGY No No Energy Quantity Key figure /TDAG/NRGYVAL stores the energy quantity. Aggregation: Exception Aggregation: Calculation: Restriction: Summation Last value, /TDAG/EMISSION No No Energy Costs Key figure /TDAG/NRGYCOST stores the energy costs. Aggregation: Exception Aggregation: Calculation: Restriction: Summation Last value, /TDAG/EMISSION No No Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 277

278 Emission Value Key figure /TDAG/EMISVAL stores the emission value. Aggregation: Exception Aggregation: Calculation: Restriction: Summation Summation No No Facility area Key figure /TDAG/FACAREA stores the facility area size value. Aggregation: Exception Aggregation: Calculation: Restriction: Summation Summation No No Template for Characteristics Facility InfoObject /TDAG/FACILITY stores the master data of a facility. The facility InfoObject can store (external) hierarchies. These hierarchies can be customized by the user Material InfoObject /TDAG/MATERIAL stores the master data of a material. Products, energies and emissions are also materials. These InfoObjects are derived from the material one and therefore they can also access the master data table of the material SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

279 Product InfoObject/TDAG/PRODUCT stores the master data of a product Energy InfoObject /TDAG/Energy stores the master data of energy Emission InfoObject /TDAG/EMISSION stores the master data of an emission Time From InfoObject /TDAG/TIMEFRO stores the time from information Time To InfoObject /TDAG/TIMETO stores the time to information Date From InfoObject /TDAG/DATFROM stores the date from information Date To InfoObject /TDAG/DATTO stores the date to information. Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 279

280 EEM Facility Classifier InfoObject /TDAG/EEMFACIC stores the facility classifiers as master data. The InfoObject key is the same as the one for the InfoObject /TDAG/FACILITY EEM Facility UDF InfoObject /TDAG/EEMUDF stores the UDF master data of the facilities used in EEM. The solution delivery only contains the UDF element facility area. The user can extend this UDF InfoObject Equipment Type InfoObject /TDAG/EQTYPE stores the facility classifier equipment type. This InfoObject is an attribute of the InfoObject /TDAG/EEMFACIC Process Chains EEM Load All Data Init Process chain /TDAG/EEM_ALL_INIT does the complete load of EEM data. Beside the transactional data also the master data is loaded with this process chain. It is up to the user to define the schedule options EEM Load All Data Delta Process chain /TDAG/EEM_ALL_DELTA does the complete load of EEM data. Beside the transactional data also the master data is loaded with this process chain. It is up to the user to define the schedule options EEM Load All Master Data Process chain /TDAG/EEM_MD_ALL does the complete load of EEM master data and texts. This chain will be part of the init and the delta chain because master data has to be loaded before the transactional data is loaded SAP SE or an SAP affiliate company. All rights reserved. Enterprise Energy Management

281 Further Information For more information about BI Content documentation, see in the BI Content documentation for SAP NetWeaver on the SAP Help Portal at Enterprise Energy Management 2017 SAP SE or an SAP affiliate company. All rights reserved. 281

282 9 Russian 2TP-Reporting In Russia, there are four environmental reports, called 2-TP reports (Air, Air urgent, Waste, and Water) which companies have to deliver to authorities. Air, Waste, and Water are annual reports; Air urgent is a mid-year report. Russian companies have to deliver these reports for each of their detached subdivision. Such a detached subdivision is a Russian specialty defined by legal as well as by territorial aspects. This chapter includes all relevant information for the technical implementation of the Russian 2TP reporting within SP13 PL1 and all later releases. Note These reports are example reports and these can be only generated in the Russian language (ru_ru) TP-Reporting as Part of SAP Environmental Compliance 3.0 SP13 PL1 The 2TP-Reporting enhancement bases on. This means that SAP EC will be customized to a specific version in order to fulfill the requirements to create 2TP Reports. The creation of 2TP Reports are triggered in SAP EC. Therefore, SAP EC has to be installed first. For the creation of the reports the enhancement takes emissions and/or consumptions into account depending on what exactly is required for the specific report. In general, 2TP-Reporting will use existing functionalities of SAP EC regarding the generation of conform 2TP Reports. The 2TP-Reporting enhancement does not have any own application dialogs. Through configuration and customization, the SAP EC application will be applied to the 2TP-reporting add-on. The configuration and customization information is provided as database content and thus has to be imported into the database. For more details, see chapter 2TP-Reporting Database Data Import. SAP Environmental Compliance is the single point of truth regarding 2TP reporting meaning that all relevant emissions and consumptions have to be stored in its database Reporting System Setup / Installation Due to the fact that 2TP-Reporting is part of the product delivery of the user has to perform the same steps of the SAP EC installation in order to get the 2TP-Reporting add-on running on the SAP NetWeaver platform. Therefore it is recommended to use the installation steps of SAP EC. The installation sequence of the complete 2TP-Reporting enhancement is the following (it is assumed that the system landscape is correctly): SAP SE or an SAP affiliate company. All rights reserved. Russian 2TP-Reporting

283 1. Deployment of the application files. Deploy all SAP EC 3.0 SP13 PL1 (and all later releases) files as mentioned in the documentation. The 2TP reports are part of the EC standard delivery and it is shipped in the SCA file REPCONT300SP13P_1. 2. Import of SAP EC database content. Import the Initial database content if this is your first version of SAP Environmental Compliance that you install in your system. Otherwise import the delta database content. 3. Import of 2TP-Reporting required database content. (Refer to SAP Note ) Reporting Database Data Import The configuration and customization information of 2TP-Reporting is provided as database content. Note that the import of database content has to be performed after the installation of the EC application. This content consists of the following items: Configuration information, e.g. Data Sources, Report Variants, (Configuration data) Master data: o UDF Elements o UDF Areas o UDF Picklists o Task Category o Material Types o Material Groups o Materials o Facility/Material Identifier o Facility/Material Classifier o Unit o Contact Types o Permit Types o Exception Types o Roll-Up Types o Emission to The database content has to be imported with EC Import Export Tool into the database. The import of the configuration data and the master data are requisites for the usage of the 2TP-Reporting enhancement. Note The database import files can be downloaded from the SAP Note Russian 2TP-Reporting 2017 SAP SE or an SAP affiliate company. All rights reserved. 283

284 9.2 2TP-Reporting System Configuration Classifiers & List of Values Some of the values that classify facilities, materials and so on are customer specific. Therefore, these values are not part of the 2TP-Reporting content package but have to be created manually. Prerequisite to start creating these values is that the content package was imported successfully. For the following classifiers and picklists, values have to be created: Facility Classifiers: o OKVED (RUS_OKVED) o OKATO (RUS_OKATO) o Water Body Type (RUS_WATER_BODY_TYPE) Material Classifier: o Waste Type (RUS_MAT_WASTE_TYPE) UDF Picklists: o Decreasing Action Group (RUS_UDF_PICK_AG) o Decreasing Action Status (RUS_UDF_PICK_AS) o Water Quality of Disposal (RUS_WATER_QUALITY_DISPOSAL) o Water Quality of Supplier (RUS_WATER_QUALITY_SUPPLIER) o Water Quality of Withdrawal (RUS_WATER_QUALITY_WITHDRAWAL) o OKATO (RUS_OKATO_CODE) o Water Use Type (RUS_WATER_USE_TYPE) o Water Quality Category (RUS_WATER_QUALITY) Values for these classifiers and picklists can be created performing the steps listed below: 1. Go to Configuration in SAP Environmental Compliance 2. Select List of Values (Basic Settings List of Values) 3. Search for a classifier or picklist noted above by using the identifier (text in the brackets) 4. Select the node which matches your search criterion and press afterwards the Create button 5. Enter at least an identifier, a code and a display name in Russian or English language 6. Save the entry by pressing the Save button Facility Type Hierarchy For the 2TP-Reporting two special facility types are required (Detached Subdivision and Water Body). Since they are not part of the SAP EC initial content the Facility Type Hierarchy has to be defined manually. The facility type hierarchy can be defined in the Configurations of SAP EC (Configuration Master Data Management Facility Configuration Facility Type Hierarchy) SAP SE or an SAP affiliate company. All rights reserved. Russian 2TP-Reporting

285 To configure that a certain facility type is allowed beneath a detached subdivision or water body the facility type has to be selected. Afterwards it is possible to mark the parent types of the selected facilities. In this example a plant can be populated beneath a carrier or a detached subdivision. After finishing the facility type hierarchy, the changes have to be saved Facility Type Properties Furthermore, the UDF Tab has to be activated manually in the Facility Configuration The facility type properties can be defined in the Configurations of SAP EC (Configuration Master Data Management Facility Configuration Facility Type Properties). Select Carrier/Company in the drop down and select the flag User-Defined Fields in the column Facility Builder. After finishing the facility type properties, the changes have to be saved. Now all installation and configuration steps have been finished. The functional part of this reporting is located in the EC Functional Documentation. For further information, see the Functional Documentation for SAP Environmental Compliance on the SAP Help Portal at Russian 2TP-Reporting 2017 SAP SE or an SAP affiliate company. All rights reserved. 285

286 10 Media List The following table provides information detailing on which data carrier you can find which software: Installable Software Unit Media Name The CD Material Number on SAP MP is SP9 PL2 on NW 7.30 The CD Material Number on SAP MP is SAP SE or an SAP affiliate company. All rights reserved. Media List

287

288 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see for additional trademark information and notices. Material Number