SAP Environmental Compliance 30 en Implementation Guide

Implementation Implementation Implementation Implementation GuideGuideGuideGuide

SAPSAPSAPSAP Environmental Environmental Environmental Environmental

Compliance Compliance Compliance Compliance

Using SAPUsing SAPUsing SAPUsing SAP®®®® Environmental Environmental Environmental Environmental

Compliance 3.0Compliance 3.0Compliance 3.0Compliance 3.0

Target Audience

� System administrators

� Technology consultants

Document Version 2.00 – February 27, 2009

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,

OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,

Power Architecture, POWER6+, POWER6, POWER5+, POWER5,

POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System

Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,

OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,

WebSphere, Netfinity, Tivoli and Informix are trademarks or

registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:

service.sap.com/instguidesservice.sap.com/instguidesservice.sap.com/instguidesservice.sap.com/instguides

SAP AGSAP AGSAP AGSAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.comwww.sap.comwww.sap.comwww.sap.com

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide <Solution>

4 Feb 2009

History of Changes

The Master Guide is regularly updated in SAP Service Marketplace at service.sap.com/instguides.

Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace immediately before starting the installation.

The following table provides an overview of the most important changes that were made in the latest versions.

Master Guide Version Important Changes

1.00 (January 22th, 2009) Initial Creation (FA)

2.00 (February 03th-

27th,

2009) Fixes ITSAM and Validation(FA)

1 Getting Started

History of Changes

Feb 2009 5

Contents

History of Changes ................................................................................ 4

1 Getting Started .............................................................................. 8

1.1 About this Document ....................................................................... 8

1.2 Related Information ......................................................................... 9

1.2.1 Planning Information .......................................................................... 9

1.2.2 Further Useful Links ........................................................................... 9

1.3 Important SAP Notes ..................................................................... 10

2 Environmental Compliance Overview ....................................... 10

2.1 Software Units of EC ...................................................................... 11

2.2 System Landscape ......................................................................... 11

3 Installation of SAP EC 3.0 ........................................................... 13

3.1 Planning .......................................................................................... 13

3.1.1 Naming Conventions ........................................................................ 13

3.2 Preparation ..................................................................................... 14

3.2.1 Hardware Requirements ................................................................... 14

3.2.2 Software Requirements .................................................................... 15

3.3 Installation ...................................................................................... 15

3.3.1 Quick overview .................................................................................. 15

3.3.2 Install SAP Netweaver CE 7.1 ........................................................... 15

3.3.3 Deploy the EC application ................................................................ 16

3.3.4 Upload the initial EC data ................................................................. 16

3.3.5 Import EC User Groups .................................................................... 19

3.3.6 Set up Email Configuration .............................................................. 19

3.4 Post-Installation ............................................................................. 20

3.4.1 Quick overview .................................................................................. 20

3.4.2 Restart System .................................................................................. 20

3.4.3 User Assignment ............................................................................... 21

3.4.4 Set up Adobe Document Service Settings ...................................... 21

3.4.5 Work Protect Mode ............................................................................ 22

3.4.6 Unified Work List (UWL) configuration ........................................... 22

3.4.7 Set up System Type .......................................................................... 23

3.4.8 Set up Deployable Application properties ...................................... 23

3.4.9 BI Installation Content Guide ........................................................... 24

3.4.10 Check the Internet Graphics Service (IGS) settings ..................... 33

4 Operation of SAP EC 3.0 ............................................................. 34

4.1 Monitoring of SAP Environmental Compliance .......................... 34

4.1.1 Alert Monitoring with CCMS ............................................................. 34

1 Getting Started

History of Changes

6 Feb 2009

4.1.2 CCMS Monitoring Installation and Setup ........................................ 34

4.1.3 Component specific Monitoring ....................................................... 35

4.2 Detailed Monitoring and Tools for Problem and Performance Analysis ................................................................................................ 35

4.2.1 Trace and Log Files ........................................................................... 35

4.2.2 Interface Monitors ............................................................................. 38

4.3 Data Growth and Data Archiving .................................................. 38

4.3.1 Overview ............................................................................................ 38

4.3.2 Prerequisites...................................................................................... 39

4.3.3 Archiving process ............................................................................. 39

4.3.4 Basic Configuration .......................................................................... 39

4.3.5 Write Archives ................................................................................... 40

4.3.5 Delete Archives ................................................................................. 45

4.3.6 Monitor Archives ............................................................................... 46

4.3.6 Search archives ................................................................................. 47

4.4 Management of SAP EC ................................................................ 50

4.4.1 Starting and Stopping ....................................................................... 50

4.4.2 Software Configuration ..................................................................... 50

4.4.3 Backup and Restore .......................................................................... 51

4.4.4 Application Copy ............................................................................... 51

4.4.5 Periodic Tasks ................................................................................... 51

4.4.6 Load Balancing .................................................................................. 53

4.4.7 User Management ............................................................................. 53

4.4.8 Technical Interfaces .......................................................................... 54

4.5 High Availability ............................................................................. 93

4.6 Software Change Management ..................................................... 94

4.6.1 Transport and Change Management ............................................... 94

4.6.2 Development Requests and Development Release Management . 95

4.6.3 Release Implementation ................................................................... 96

4.6.4 Support Packages and Patch Implementation................................ 96

4.7 Troubleshooting ............................................................................. 96

4.7.1 Imported data does not appear in EC .............................................. 96

4.7.2 Logged in user has no permission for an EC Object ..................... 97

4.7.3 Report Generation does not work .................................................... 97

4.7.4 Email notification does not work ..................................................... 97

4.7.5 EC object is locked ........................................................................... 97

4.7.6 Web Services does not import all data ............................................ 98

4.7.7 Graphics Rendering (IGS) Problem ................................................. 99

4.7.8 Java Scheduler Jobs do not work ................................................... 99

4.8 Application Security .................................................................... 100

4.8.1 Three Tier Authentication Concept ................................................ 100

1 Getting Started

History of Changes

Feb 2009 7

4.9 Support Desk Management ......................................................... 102

4.10 Remote Support Setup .............................................................. 103

4.11 Problem Message Handover ..................................................... 104

4.12 BI / BW Content .......................................................................... 104

4.12.1 Introduction ................................................................................... 104

4.12.2 Extraction Layer of SAP Environmental compliance ................. 106

4.12.3 Environmental compliance BI InfoProviders .............................. 108

5 Migration of SAP EC ................................................................. 127

5.1 Introduction .................................................................................. 127

5.2 Prerequisites ................................................................................ 127

5.3 Detailed Migration Steps ............................................................. 127

5.4 Migration of EC Installations ....................................................... 128

5.4.1 SAP BI Content Migration ............................................................... 130

5.4.2 Enterprise Portal Content Migration .............................................. 133

6 Media List .................................................................................. 135

1 Getting Started

1.1 About this Document

8 Feb 2009

1 Getting Started

1.1 About this Document

Purpose

This guide includes all relevant information for the technical implementation of SAP Environmental Compliance 3.0.

The Master Guide consists of the following main sections:

• System Landscape

• Installation

• Configuration

• Operation

• Upgrade

You can find the most current information about the technical implementation of SAP Environmental Compliance 3.0 on SAP Service Marketplace at http://service.sap.com/instguides.

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

1 Getting Started

1.2 Related Information

Feb 2009 9

1.2 Related Information

1.2.1 Planning Information For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade guides

http://service.sap.com/instguides

SAP Business Maps - information about applications and business scenarios

http://service.sap.com/businessmap

s

Sizing, calculation of hardware requirements - such as CPU, disk and memory resource - with the Quick Sizer tool

http://service.sap.com/quicksizer

Released platforms and technology-related topics such as maintenance strategies and language support

http://service.sap.com/platforms

To access the Platform Availability Matrix directly, enter service.sap.com/pam.

Network security http://service.sap.com/securitygui

de

High Availability http://service.sap.com/ha

Performance http://service.sap.com/performance

Information about Support Package Stacks, latest software versions and patch level requirements

http://service.sap.com/sp-stacks

Information about Unicode technology http://service.sap.com/unicode@sap

1.2.2 Further Useful Links The following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Information about creating error messages http://service.sap.com/messages

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (software download and ordering of software)

http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learning Maps

http://service.sap.com/rkt

2 Environmental Compliance Overview

1.3 Important SAP Notes

10 Feb 2009

1.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 SAP Service Marketplace at service.sap.com/notes.

SAP Note Number

Title

1139005 SAP Environmental Compliance 3.0 Central Note

1277367 SAP Environmental Compliance 3.0 Release Notes

1067441 EC Date and Time Handling

1297451 Export / Import Environmental Compliance 3.0 Data

1010913 SAPTrans Tool for importing EC Data

1177820 SAP EC 2.0 SP13 Central Note

1297538 SAP EC 3.0 adjustment of XSLT Templates for EC Reporting

1303115 BI Additional Documentation for Environmental Compliance 3.0

2 Environmental Compliance Overview SAP Environmental Compliance 3.0 (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, wastewater and waste compliance and additionally supports enterprise energy management initiatives. Business processes to support compliance with permits for air and wastewater regulations can be seamlessly deployed across different business units ensuring timely generation of government reports. 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.


2.1 Software Units of EC

Feb 2009 11

2.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 or installed on a SAP BI system.

Following components are initially delivered with SAP EC 3.0

Application Component

Name of the SC File Software Component Version

EC Central Services

TDAGECSSERV30000P_1 TDAG_ECS_SERVICES 3.0 Patch 1

EC Central Modules

TDAGECSMOD30000P_1 TDAG_ECS_MODULES 3.0 Patch 1

EC Application Modules

TDAGXEMMOD30000P_1 TDAG_XEM_MODULES 3.0 Patch 1

EC Reporting Content

TDAGXEMREPCONT30000P_1 TDAG_XEM_REP_CONTENT 3.0 Patch 1

EC Portal Content TDAGECSPC30000P_1 TDAG_ECS_PC 3.0 Patch 1

EC BI Content (Optional)

SAPK-300COINTDAGECB TDAGECB 3.0

The SC “Bi Content” requires a SAP BI 7.0 SP17 or higher installation.

The other SCs requires a SAP Netweaver CE 7.1 Java Server installation

The PL00 label means that the Support Package is in Patch Level 0.

2.2 System Landscape

The SAP EC 3.0 Application consists of five main software components: Refer to previous chapter . The Core Packages (running under 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)


2.2 System Landscape

12 Feb 2009

The baseline for the architecture is TechniData AG’s architecture EC-E³ in order to support integration of the application into the Business Compliance Suite of TechniData AG. The architecture EC-E³ follows the ideas of SAP Enterprise Services Architecture.

ECApplication Logic

ECPersistency Services

RFC

Persistency & Interface Layer

UI Layer

Custom User

Interfaces

UWLConnector

ECUser Interfaces

BW

ECBI Extraction Services

TransactionalData Interface

Web Services

Integrated Systems

EAM, EHS(PS, IH), MM

Custom Application

Logic

UWL EC Portal Content NW Java EC Portal Functions

BAPI BAPI

EC BI Content

ECRFC Interfaces

RFC

NW Database

JDBC (OPEN SQL)

ABAP

Application Layer SAP NW CE 7.1

Web Dynpro Java

Environmental Compliance 3.0 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 the 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.

The Application Layer represents the Business Logic of EC 3.0, that can be enhanced by custom specific extensions to offer additional functionality in EC 3.0.

The Persistency & Interface Layer represents the persistency storage functionality for all EC business objects which are stored in a Netweaver Database. Furthermore BI Extraction Services and RFC Interfaces offer access to BI Content and Integrated Systems.

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.

Client Web Browser

3 Installation of SAP EC 3.0

Feb 2009 13


3.1 Planning EC 3.0 can be migrated only from EC 2.0 SP13. If you are working with EC 2.0 older than SP13 then you have first to update to EC 2.0 SP13. For further information about EC 2.0 SP13 please refer to the SAP Note 1177820

For the update process please refer to the chapter 5 Migration of SAP EC

For further information about the proceeding to installation the SAP Netweaver CE 7.1, refer to http://service.sap.com/instguides.

Careful planning is a prerequisite for the successful installation of the system.

3.1.1 Naming Conventions In this documentation, the following naming conventions are used:

Variable Description

<SID> SAP system ID in uppercase letters

<INSTNO> SAP system Instance number

<EC-DIR> The Environmental Compliance delivery directory.

<INSTDRIVE> 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/…

<host> Web server name

<port> TCP port number on which the server is listening for HTTP requests

Process Flow

1. You print out the relevant checklist:

- To install, see chapter 3.3 Installation

- To upgrade, see chapter 5 Upgrade of SAP EC

2. You print out the relevant documentation:

- SAP Installation notes � See Chapter 1.3 Important SAP Notes

- SAP_Environmental_Compliance_30_en_Functional_Documentation

3. You follow the installation sequence exactly as shown in the tables.

− If a step is required for your installation, you follow the link for that step to the corresponding section.

− You perform the procedure described there.

− After you have successfully completed the installation step, please mark the corresponding entry in the printed table with ! to log the progress of your installation.

− You proceed with the next step listed in the table.


14 Feb 2009

3.2 Preparation Before starting the installation the following items have to be taken into consideration:

3.2.1 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 Requirement

Hardware Requirements

• 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

Recommendation 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.

Software Requirements

• Operating System: Please refer to the SAP Product Availability Matrix (https://service.sap.com/pam)

• SAP JVM which is delivered with NetWeaver Java stack

The client workstations must meet the following requirements:

Requirement Type Requirement

Hardware Requirements

• CPU: 1 GHz

• RAM: 512 MB

• Monitor Resolution 1024 x 768 or higher


Feb 2009 15

3.2.2 Software Requirements Requirement Type Requirement

Basic Requirements • SAP NetWeaver CE 7.1 SP7 or higher

• 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)

The Environmental Compliance 3.0 can be downloaded from SAP Market Place. For further information please refer to the chapter 4.6.3 Release Implementation and 4.6.4 Support Packages and Patch Implementation.

3.3 Installation

3.3.1 Quick overview !!!! Action

Install SAP Netweaver CE 7.1 SP7 or higher

Deploy the Environmental Compliance application to the SAP Netweaver CE 7.1

Upload the initial Environmental Compliance data to the target database

Import Environmental Compliance User Groups

Set up Email Configuration

3.3.2 Install SAP Netweaver CE 7.1

Use

Use the NetWeaver Java stack to install the latest SAP Netweaver CE 7.1

Prerequisites

Ensure that the Operation System is installed properly and the current user has administrator permissions.

Procedure

For further information about installing SAP Netweaver (J2EE Engine), go to http://service.sap.com/instguides


16 Feb 2009

3.3.3 Deploy the EC application

Use

The EC application is delivered in different Software components (See chapter 2.1 Software Units of Environmental Compliance). All the software components have to be deployed with JSPM tool on the SAP NetWeaver Web Application Server.

For further information about JSPM refer to the SAP Help on the following page: http://help.sap.com/saphelp_nwce10/helpdata/en/87/4797422930c56ae10000000a155106/frameset.htm

Prerequisites

Ensure that the SAP Netweaver CE 7.1 (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 2.1 Software Units of Environmental Compliance) 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 SAP Netweaver CE administrator password

Select the Package Type: � New Software Component

Choose the Next button to switch 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

Choose the Next button to switch to the next Steps and start the deployment

After successful deployment you can exit from SAP Software Delivery Tool

3.3.4 Upload the initial EC data

Use

Environmental Compliance requires the availability of initial data content. The content will be uploading with the SAPTrans tool (See OSS note: 1010913 and 1063294)


Feb 2009 17

Prerequisites

Ensure that the Environmental Compliance 3.0 is deployed on the SAP Netweaver CE system.

Procedure

!!!! Action

On the EC Installation directory navigate to folder:

<EC-DIR>\saptrans_EC30_init. Copy the whole content of this folder to a local hard

disc drive, for example …\saptrans_init\

Copy the corresponding JDBC Driver JARs, which depends on the EC target database into the folder \saptrans_init\

• The driver JARS are Data Base dependent and are required to be copied into the SAPTrans directory: The following list contains the driver JARs for the different Data base Types.

� MAXDB: sapdbc.jar

� SQL-Server: sqljdbc.jar

Refer to the SAP Note 1109274. Here you find information where you can download the latest MS SQL Server JDBC driver

� Oracle: ojdbc14.jar

� DB2: db2jcc.jar, db2jcc_license_cisuz.jar and db2jcc_license_cu.jar

• For a default installation these driver classes can be found in the following directories: Windows systems - MAXDB: localdrive\sapdb\programs\runtime\jar - SQL-Server: Refer to the SAP Note 1109274

- Oracle: localdrive\oracle\<SID>\<oracle_version>\jdbc\lib - DB2: localdrive\db2\db2<sid>\sqllib\java Unix systems - MAXDB: /sapdb/programs/runtime/jar - SQL-Server: Refer to the SAP Note 1109274 - Oracle: oracle/<SID>/<oracle_version>/jdbc/lib

- DB2: /db2/db2<sid>/sqllib/java

Open a command line interface and change the current working directory folder …\saptrans_init\

• Enter the following command: java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m

-jar SAPtrans.jar import logfile=import.log

datafile=init.dat “connectstring=<JDBC Driver>;<JDBC

Url>;<User>;<Password>”

with parameters:

• JDBC Driver: full qualified class name of the JDBC Driver to connect the EC target Database.

�MAXDB: com.sap.dbtech.jdbc.DriverSapDB

�MS SQL-Server com.microsoft.sqlserver.jdbc.SQLServerDriver


18 Feb 2009

�Oracle: oracle.jdbc.driver.OracleDriver

�DB2: com.ibm.db2.jcc.DB2Driver

• JDBC Url: the connect Url for the JDBC Driver. The JDBC URL is database dependant

�MAXDB: jdbc:sapdb://<host>/<instanceid>

�MS SQL-Server: jdbc:sqlserver://<host>:<port>

�Oracle: jdbc:oracle:thin:@<host>:<port>:<sid>

�DB2: jdbc:db2://<host>:<port>/<SID>

User: the database user to connect with.

Password: the database user password.

• Example command for import into SQL Server: java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m


datafile=init.dat “connectstring=

com.microsoft.sqlserver.jdbc.SQLServerDriver;

jdbc:sqlserver://vma03:1433;SAPC11DB;password”

• Example command for import into DB2 Server java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m


datafile=init.dat "connectstring=

com.ibm.db2.jcc.DB2Driver;jdbc:db2://vma03:

5912/C11;SAPC11;password"

• Example command for import into Oracle Server java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m


datafile=init.dat connectstring=

oracle.jdbc.driver.OracleDriver;

jdbc:oracle:thin:@vma03:1527:C11;SAPC11DB;password

• Example command for import into MAXDB Server java -Duser.timezone=UTC-0:00 -Djava.ext.dirs=. -Xmx1024m


datafile=init.dat “connectstring=

com.sap.dbtech.jdbc.DriverSapDB;jdbc:sapdb:

//vma03/C11;SAPC11DB;password”

• Choose Enter and execute the command. For more information about the state of the initial data load see file import.log.

The “timezone” functionality is detailed described in the SAP OSS Note: 1063294

NOTE: The parameter -Xmx1024m means that JAVA allocates 1 GB Memory

RAM. Be aware that the client system where SAPTrans runs needs at least 1GB free Memory RAM

The initial data load process is now completed


Feb 2009 19

3.3.5 Import EC User Groups

Use

Environmental Compliance 3.0 is delivered with predefined User Management Engine (UME) User groups, which enables a fast start with the Environmental Compliance application. This installation step is optional. You can set up also own User groups..

You find the User Groups in the directory “<INSTDRIVE>/User Groups”

Prerequisites

Ensure that Environmental Compliance is deployed on the SAP Netweaver CE

Procedure

!!!! Action

Log in to the user administration (http://<host>:<port>/useradmin) with an administrator user

Navigate to the Import Tab

Search the file Groups.txt from your Installation directory “<INSTDRIVE>/User

Groups”

Import the user groups

After finishing these steps you have to set up a password for all EC imported users. Note: You have to change the password after you log in the fist time.

Importing data in the UME please refer to the SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/70/9be23d44d48e5be10000000a114084/frameset.htm

3.3.6 Set up Email Configuration

Use

The notification in Environmental Compliance 3.0 works with Email sending. For this case you need to set up the Email Configuration in the SAP Netweaver CE 7.1 environment.

Prerequisites

Ensure that Environmental Compliance is deployed on the SAP Netweaver CE.

Procedure

!!!! Action

Go to the SAP Netweaver CE Config Tool (For further information refer to SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm )

In Config Tool navigate to: Cluster-data � Template_<Name> � Services � javamail

If you have several Instances the data from the template will be transferred automatically to the instances.

In the detail view of javamail node you can set up the mail pop3 settings, smtp settings and the administrator email address (mail.from)

After you saved your changes you have to restart the whole cluster (Refer to the


20 Feb 2009

chapter 3.4.2 Restart System)

The email configuration needs a further step in the EC Configuration Email Templates. For further information about the EC Email Templates please refer to the SAP EC Functional Guide “Email Notification”.

3.4 Post-Installation

3.4.1 Quick overview !!!! 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

3.4.2 Restart System

Use

After finishing the installation steps the SAP NetWeaver Web Application Server(s) has to be restarted

Prerequisites

All installation steps have to be finished.

Procedure

There are two different ways to restart the system.

The first way is to restart the whole cluster. This step is needed when you make changes in the Config Tool (Email notification settings)

Procedure:

!!!! Action

Log in directly on 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


Feb 2009 21

Application Server will restarted.

The second way is to restart only the SAP NetWeaver Server Instance(s) after you deployed EC deployable files. This way does not take so long time.

Procedure:

!!!! Action

Log in to the NWA (http://<host:port>/nwa/start-stop) with an administrator user

Restart every Server Process of each Instance

Enter the Administrator password in the popup window.

3.4.3 User Assignment

Use

The user assignment is a basic step to set up the different users for the different Environmental Compliance processes.

Prerequisites


Procedure

For assigning Users in SAP Netweaver CE please refer to the SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/59/bf2287b3cb5e48af94f99929ad15b9/frameset.htm

We recommend assign 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 further information about “pcd:portal_content/every_user/general/eu_role” please refer to the SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/46/a1be96f7bf407db6ac78e343b8cef1/frameset.htm

For further information about the EC Groups and Roles please refer to the SAP_Environmental_Compliance_30_en_Functional_Documentation

3.4.4 Set 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


Procedure

For set up Adobe Document Service please refer to the SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/45/bf03b55b9847f2e10000000a114a6b/frameset.htm


22 Feb 2009

3.4.5 Work Protect Mode

Use

The Work Protect 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


Procedure

For further information about the Enterprise Portal Work Protect Mode please refer to the SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/45/762f7bf0020dece10000000a11466f/frameset.htm

Further information you find on the following Help page: http://help.sap.com/saphelp_nw70/helpdata/en/43/2236fc0b413fe1e10000000a11466f/frameset.htm

We recommend to assign 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 further information about “pcd:portal_content/every_user/general/eu_role” please refer to the SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/46/a1be96f7bf407db6ac78e343b8cef1/frameset.htm

3.4.6 Unified Work List (UWL) configuration

Use

The Unified Work List enables a central and unified access to all work items regardless of their specific type. Therefore users which have to work with multiple systems have not 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.

Prerequisites


Procedure

Please 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 further information about registering the provider systems please refer to the SAP Help:

http://help.sap.com/saphelp_nw04/helpdata/en/92/a88931f2dd4631b9e8d530697d89c9/frameset.htm


Feb 2009 23

3.4.7 Set up System Type

Use

The System Type should be set up the first time of the installing or updating the EC 3.0. The System type is a property of EC Properties. A detailed description about the EC Properties you can find in the Description Column of the EC properties.

Navigate to the EC Properties: Plant Compliance � Configuration � Basic Settings � EC Properties.

Prerequisites


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) which 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 about the possible Values of the Property “system.landscape.type”:

Value Description

D Development: means all Transport of Configuration options are available. See also Chapter 4.6.1 Transport and Change Management

Q 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.

P (default) Productive System: The Transport of Configuration functionality is not available.

You should adapt this property for every different EC System in your Landscape.

3.4.8 Set up Deployable Application properties

Use

The settings in SAP Netweaver configuration Tool (Config Tool) set up which deployable applications should be start automatically.

Prerequisites


Procedure

!!!! Action

Go to the SAP NetWeaver Configuration tool http://help.sap.com/saphelp_nwce10/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm

In the Menu „View“ change to Expert Mode

Select the Hierarchy element under the cluster-data node


24 Feb 2009

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: *

Click on the Set button and save the settings

After that you have to restart the whole cluster

3.4.9 BI Installation Content Guide

3.4.9.1 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:

• InfoCubes

• ODS-Objects

• InfoSources

• InfoPackages

• ProcessChains

• 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.


Feb 2009 25

3.4.9.2 Prerequisites For the installation of the EC BI content it is absolutely necessary to have the most recent service pack for your Business Warehouse installed.

Please keep in mind that support can only be provided, if you do 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

Recommended Service Pack Level

SAP_BW: 700 SP17, SAPKW70017

BI_CONT: 703 SP5, SAPKIBIIP5

SAP_BASIS: 700

3.4.9.3 Procedure and Preparation

Activation

Some 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


26 Feb 2009

• 0SRCID

• 0COUNTRY

• 0REGION

• 0RECORDMODE

• 0RECORDTP

• 0REQUID

• 0MATERIAL

Activate these BW objects with TA RSOR with option “Only necessary objects”.

If these InfoObjects have been activated successfully but cannot be found in TA RSA1, consider SAP note 573421.

3.4.9.3.1 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 please move the File containing the EC BI Content SAPK-300COINTDAGECB.SAR to the appropriate “…/usr/sap/trans/” inbox.

The Password for the Installation is put in the SAP Note 1139005

The SAPK-300COINTDAGECB.SAR file can be unpack with the SAPCAR tool with the command “…/SAPCAR.EXE -xvf SAPK-300COINTDAGECB.SAR”

The packed SAR file contains the following folder structure: “…/EPS/in/” The SAR file contains a file named “XBA0020145770_0000004.PAT”

The latest SAPCAR can be downloaded from the SAP Market Place

3.4.9.3.2 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 TA RSNSPACE. 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) it is necessary to flag the two new namespaces as modifiable in TA SE03. 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 marked as modifiable in the customer system. To do this carry out the following steps:


Feb 2009 27

1. Call TA SE03

2. Select “Set System Change options”

3. Locate the namespaces /B123/ and /TDAG/ and set them to “modifiable”

3.4.9.3.3 Packages

The required Packages are automatically installed after successful installation of the EC BI-Content via the Add-On Installation Tool (Transaction SAINT)

After the import and installation of the packages necessary for EC verify the packages in TA SE80. Select in the drop down menu the entry Packages. The following packages should be successfully configured:

• /TDAG/CO

• /TDAG/EM

3.4.9.3.4 Maintain source system XEM

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, since source systems cannot be transported in the SAP BI.

In order 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: xEM.

4. Make sure to enter the correct type and release of the source system.

The program ID of the xEM source system has to be identical to the program ID customized at EC Configuration �� Integration �� BW Properties (property bw.extractor.progid).

Logical System Name Source System Name Type and Release

xEM xEM XEM020

If an error message appears, that the BW user does not exist in table RSADMIN, please refer to the SAP note 410952

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. If this is not the case, visit TA RSA1 and select Source Systems. Left click on the EC Source System and select the option Restore. When the restoring of the Source System is done, call TA WE20 again and check if the Partner Profile is active and created correctly.

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 Source Systems and there choose the EC data source. Right click on the EC source system and choose restore from the menu. Don’t forget to activate the source system after restoring. After activating the source system it is recommended to replicate and reactivate the logical system. The logical system is also located in the source systems. Right click on the source system “logical system” and select replicate from the menu.


28 Feb 2009

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 profile S_BI-WHM_RFC to the remote user.

To test the RFC connection from the BW system to the EC system, the RFC connection must be configured in EC. For further information please refer to the chapter 4.12.2.1 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 chapter 4.12.2.1 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 TA SM59 > TCP/IP Connections and select xEM.

a. Click on Test Connection to see if a connection has been established.

b. Select in the menu bar System Information > Target System and make sure that the system you are connected to is the correct host.

It is recommended to restore the source system! This will be done in the administrator workbench by selecting TA RSA1 > Source systems, select xEM, context menu, select restore option. The BW system will recreate all generated programs for this SourceSystem. Don’t forget to activate the source system after restoring!

3.4.9.4 Activation of BW content (New Installation) After the completion of all actions described in Chapter 3.4.9.3 Procedure and Preparation, all BI-Content objects required for SAP EC are automatically installed.

After the successful 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 Transaction RSOR under Business Content. The BW Object for xEM has to be activated in the following sequence:

1. Activate Info Object Catalogs

2. Activate Info Providers

3. Activate Process Chains

For the activation you need to adjust the settings prior to the selection of the content.


Feb 2009 29

Activation of Info Object Catalogs

Select options:

• Grouping > Only necessary objects

• Source System assignment > xEM

• Collection Mode > Collect automatically

Select the InfoObject Catalogues in left menu and click on Select Objects. Transfer the following InfoObject Catalogues 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

It’s recommended to remove the SAP standard objects before activating.

For all SAP standard object select in context menu the option “Do not install any below”. Have a look at the following list which gives a short review (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 SM37

Activation of InfoCubes

The activation of InfoCubes needs to have a different grouping option.

• Grouping > In Dataflow Before



The “In Dataflow Before” option includes all objects “below” the InfoCube (ODS objects, InfoSources, InfoObjects etc).

The InfoCubes to be activated are:


30 Feb 2009

• /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

Please follow the following procedure to activate the content:

• Select item InfoProviders in the navigation pane of RSOR.

• Drag the InfoCubes starting with /TDAG/EM to the right pane.

• Mark all entries in right pane using the “select all” button

It’s recommended to remove the SAP standard objects before activating.

For all SAP standard object select in context menu the option “Do not install any below”. Have a look at the following list which gives a short review (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”



Activation of Process Chains

The following table shows all xEM process chains:

Process Chain Description


Feb 2009 31

-> EM Master data and transactional data (Delta)

Loads all data calling the other process chains)

-> EM Master data and transactional data (Init)

Loads all data calling the other process chains

EM Consumption scenarios (Delta) Data loading for InfoCube

EM Consumption scenarios (Init) Data loading for InfoCube

EM Consumptions (Delta) Data loading for InfoCube

EM Consumptions (Init) Data loading for InfoCube

EM Delete all transaction Deletes all transactional data in the InfoCubes and ODS.

EM Emission scenarios (Delta) Data loading for InfoCube

EM Emission scenarios (Init) Data loading for InfoCube

EM Emissions (Delta) Data loading for InfoCube

EM Emissions (Init) Data loading for InfoCube

EM Exception Attribute Delta Master data loading

EM Exception Attribute Init Master data loading

EM Exception UDF Delta Master data loading

EM Exception UDF Init Master data loading

EM Exceptions (Delta) Data loading for InfoCube

EM Exceptions (Init) Data loading for InfoCube

EM Facility Attribute Master data loading

EM Facility Hierarchy Nodes Facility Hierarchy Nodes

EM Facility Hierarchy Default Default Hierarchy structure of the facility

EM Facility Hierarchy Legal Entity Legal hierarchy structure

EM Facility Hierarchy Location Location hierarchy structure

EM Facility Hierarchy Organizational Unit Organization hierarchy structure

EM Facility Hierarchy Regional Regional hierarchy structure

EM Facility Identifier and Classifier Master data loading

EM Facility UDF Master data loading

EM Master data and hierarchies Data load of all master data and hierarchies.

EM Measurements (Delta) Data loading for InfoCube

EM Measurements (Init) Data loading for InfoCube

EM Tasks (Delta) Data loading for InfoCube


32 Feb 2009

EM Tasks (Init) Data loading for InfoCube

EM Tasks Attribute (Init) Master data loading

EM Tasks Attributes (Delta) Master data loading

EM Tasks UDF (Delta) Master data loading

EM Tasks UDF (Init) Master data loading

EM Text data Load all texts of the InfoObjects

EM Text data (optional) Loads all texts of InfoObjects which require configuration (hierarchies, UDF, …)

EM Master data and hierarchies (optional) Loads the master data and hierarchies of InfoObjects that need a configuration (UDF, Flex hierarchies)

EM Emissions by material classifiers (Init) Emission data by material classifiers

EM Emissions by material classifiers (Delta) Emission data by material classifiers

EM Emissions by material groups (Init) Emission data by material groups

EM Emissions by material groups (Delta) Emission data by material groups

EM Consumptions by material classifiers (Init) Consumptions by material classifiers

EM Consumptions by material classifiers (Delta) Consumptions by material classifiers

EM Consumptions by material groups (Init) Consumptions by material groups

EM Consumptions by material groups (Delta) Consumptions by material groups

EM Measurements by material groups (Init) Measurements by material groups

EM Measurements by material groups (Delta) Measurements by material groups

EM Measurements by material classifier (Init) Measurements by material classifier

EM Measurements by material classifier (Delta) Measurements by material classifier

Select these options for installing:

• Grouping > Only necessary objects



Activate all process chains.

Please follow the following procedure to activate the content:

• Select Item Object Types in the navigation pane of RSOR

• Select Process Chains and select Objects

• Sort the data in the popup by object name and select all items starting with /TDAG/EM and transfer this selection

• Mark all entries in right pane using the “select all” button


Feb 2009 33

• Select “Install”



Before loading data from EC, make sure that the InfoPackages are set to the correct update mode. Be aware that this setting of the InfoPackage is not always transported correctly. The update mode in the InfoPackage must match the InfoPackage’s name, e.g. /TDAG/EM_1_INIT must have update mode: Initialization of delta transfer.

3.4.10 Check the Internet Graphics Service (IGS) settings

Use

The Internet Graphics Service (IGS) enables to create charts and Graphics in EC Reporting.

Prerequisites


Procedure

Check if the IGS installation runs on your system. Log in with the SAP Netweaver Admin user into the following URL: http://<Server>:<Port>/webdynpro/dispatcher/sap.com/tc~wd~tools~console/WebDynproConsole

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 successfully.

If the IGS is not connected, you have to go to NWA and set up the IGS Url:

Log in to NWA with the SAP Netweaver Admin user http://<Server>:<Port>/nwa/app-modules

Filter the application “tc~wd~dispwda” in the Module List.

Select the Module “webdynpro/resources/sap.com/tc~wd~dispwda”

Select in the Tab Web Dynpro Properties in the “Web Module Details” the row “Default”

In the Dialog Table below “Full Details” you can now set up the IGSUrl.

Note, this Service URL can also be on an external System.

4 Operation of SAP EC 3.0

34 Feb 2009


4.1 Monitoring of SAP Environmental Compliance

Within the management of SAP Technology, monitoring is an essential task. A section has therefore been devoted solely to this subject.

You can find more information about the underlying technology in the SAP Netweaver Administrator’s Guide - Technical Operations Manual in the SAP Library under SAP Netweaver Library.

4.1.1 Alert Monitoring 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 please refer to the SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htm

4.1.2 CCMS Monitoring Installation and Setup If you want to monitor SAP NetWeaver Composition Environment 7.1 (CE) centrally, you must use a central monitoring system with release SAP NetWeaver 7.0.

See SAP Help for information on how to set up the CCMS agent: http://help.sap.com

� SAP Netweaver � SAP Netweaver CE � SAP NetWeaver Composition Environment Library

http://help.sap.com/saphelp_nw70/helpdata/en/7c/d9ba3b3bf00152e10000000a114084/frameset.htm

The following search pattern can be used:

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 4.1.3 Component specific Monitoring).

For detailed information about GRMG Lite see the following URL http://help.sap.com/saphelp_nw70/helpdata/en/6d/6fe040852f712ae10000000a155106/frameset.htm

For more information about monitoring SAP NetWeaver, see the following URL http://help.sap.com/saphelp_nw70/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htm

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


Feb 2009 35

4.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)

http://<host>:<port>/webdynpro/dispatcher/technidata.de/ecs~syscheck~main~wd/SystemChecksApp

EC Central Modules (TDAG_ECS_MODULES)

http://<host>:<port>/webdynpro/dispatcher/technidata.de/ecs~facility~exposed~wd/FacilitySelectorTEST

EC Application Modules (TDAG_XEM_MODULES)

http://<host>:<port>/webdynpro/dispatcher/technidata.de/xem~matmgmt~main~wd/MaterialManagement

EC Reporting Content (TDAG_XEM_REP_CONTENT)

http://<host>:<port>/webdynpro/dispatcher/technidata.de/xem~repcont~main~wd/RepContHeartbeat

4.2 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), refer to 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) under the following URL service.sap.com/instguides � SAP NetWeaver � SAP NetWeaver 7.0 (2004)

� Operations

4.2.1 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. Go to the URL according the following pattern http://<host>:<port>/nwa � Problem Management � Logs and Traces � Log Viewer (Quicklink Alias: /nwa/logs) to find detailed information about error messages saved in the log files.

For detailed information about Monitoring and Displaying Log Files see the following URL: http://help.sap.com/saphelp_nwce10/helpdata/en/ac/e9d8a51c732e42bd0e7de54b9ff4e2/frameset.htm

We recommend that you check the log files from time to time.

Important Log and Trace files for SAP Environmental Compliance

Component Content


36 Feb 2009

TDAG_ECS_SERVICES Trace Messages of Central Services

TDAG_ECS_MODULES Trace Messages of Central Modules

TDAG_XEM_MODULES Trace Messages of Application Modules

TDAG_XEM_REP_CONTENT 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. Additionally 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: Log Categories of Component TDAG_ECS_SERVICES EC Archive Service Basic Objects ECS Basic Service TimeStamp Calculation Service Cross-Reference Service DataMigration Deprecated Objects Document management service Email Notifications Service Email Scheduler Detector Email Scheduler Manager Hierarchy Service Identification service IGSWrapper ImportExport Service Inspection framework Integrated Systems Logging Viewer LOV Multilingual Deprecated Service Multilingual Service Parameters Permission Service Persistency Change Doc Transfer RenamingTool RFC Service Startup EC Properties UDF Service Unit and Dimension Service User Service UserExit Service


Feb 2009 37

User Profile Service UserReassignment User Substitution Service Log Categories of Component TDAG_ECS_MODULES ECS Facility Builder ECS Facility Builder UserExit Menu Frame Reporting Log Categories of 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 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 EMail Poll EAM Task Synchronization Task Status Job Exception Custom Task Type UserExit Log Categories of Component TDAG_XEM_REP_CONTENT EC Reporting Content: Facility Emissions Datasource

By default, these log categories are configured for severity level INFO.


38 Feb 2009

4.2.2 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. For further information please refer to the Chapter 4.4.2.15 RFC Configuration

You can reach the RFC Monitor in the following Navigation:

Log in to the portal (http://<host:port>/irj) with an user which 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

Web Services For further information about Web Services Logging & Tracing please refer to the SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/46/b7349b1b2341d8e10000000a1553f7/frameset.htm

Log in to the NWA (http://<host:port>/nwa/ws-logs) with SAP Netweaver CE admin user.

Web Service

Scheduled Jobs For further information about Java Scheduler please refer to the SAP Help

http://help.sap.com/saphelp_nwce10/helpdata/en/44/03d66015ee10b3e10000000a11466f/frameset.htm

Log in to the NWA (http://<host:port>/nwa/scheduler) with SAP Netweaver CE admin user.

Java Scheduler

Archiving Monitor

See chapter 4.3 Data Growth and Data Archiving Java Scheduler and Archiving Cockpit

4.3 Data Growth and Data Archiving

4.3.1 Overview This chapter describes how to archive Transactional Data within Environmental Compliance 3.0. Further more it describes the searching of archived data of the different business objects.

Working with the Environmental Compliance (EC) creates during its lifetime a lot of Transactional Data in data base tables. This could lead to performance problems in the reporting process when data base table(s) contain huge amount of entries (> 1mio). For this


Feb 2009 39

case the transactional data base tables of Environmental Compliance have the possibility for a final archiving method of the life data.

The EC Admin should be aware that the archived data can not be returned into the EC Data base tables after they were archived.

The archiving process is realized with the XML Based Archiving which is part of the JAVA Netweaver 7.1 CE landscape.

Following Environmental Compliance Business Objects are supported for archiving:

1. Consumptions

2. Measurements

3. Emissions

4. Exceptions

5. Task Instances

6. Change documents

4.3.2 Prerequisites The following prerequisites must be satisfied before it is possible to run the Archiving process.

� SAP Environmental Compliance 3.0 must be set up correctly

� Set up Archiving Store for every Archive Set object

4.3.3 Archiving process

The archiving process contains the steps which are needed for the Archiving of EC Transactional data.

The archiving process can only be done by a SAP NetWeaver WEB Application Administrator user, due to 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:

http://<server>:<port>/nwa/archcockpit

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

4.3.4 Basic Configuration Before starting the action of configure the Archiving Store you need to set up an user.

For further information about creating users for Archiving please refer to the SAP Help (Creating Users and Assigning Roles): http://help.sap.com/saphelp_nwce10/helpdata/en/43/68fac39a363d33e10000000a11466f/frameset.htm

4.3.4.1 Archive Store

The Archive Store defines the location and type of the XML Based Archiving.

The Archiving Store enables to define new archive stores, change, delete or test existing archive store.


40 Feb 2009

For further information about the Archiving Store please refer to the SAP Help (Administration of the XML Data Archiving Service): http://help.sap.com/saphelp_nwce10/helpdata/en/d3/f61140d72dc442e10000000a1550b0/frameset.htm

4.3.4.2 Assign Archiving Set to available Archiving Store

EC 3.0 delivers several archiving sets which represents the EC business objects. Every Archiving Set and its path extension can be assigned to ONE available Archiving Store. For further information about assigning an Archiving Store to a Set please refer to the SAP Help (Administration of the XML Data Archiving Service): http://help.sap.com/saphelp_nwce10/helpdata/en/d3/f61140d72dc442e10000000a1550b0/frameset.htm

EC 3.0 has the following Archiving Sets:

1. sap_ec_archiving_measurements

2. sap_ec_archiving_emissions

3. sap_ec_archiving_consumptions

4. sap_ec_archiving_changedocs

5. sap_ec_archiving_tasks

6. sap_ec_archiving_exceptions

4.3.5 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 4.3.5 Delete Archives

The Write view is build 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 - Start now: Date for start the archiving process - Start at Date / Time: Definition for set up a scheduled archiving run - Start Delete Phase Automatically: This flag enables running the archiving and delete process in one step. For further information please refer to the SAP Help

3. Technical Settings The Technical Settings are similar for every EC Archiving Set and have the following properties: - XML Parsing: check if the created XML is well formed - Simulation: this flag should be used for testing, e.g. how many rows a run have - Path Extension: displays the Archiving path extension of a collection, which can be set up in the Java Archiving Cockpit hierarchy. - Comment: Comment of the archiving run


Feb 2009 41

For further information about writing archives please refer to the SAP Help (Java Archiving Cockpit): http://help.sap.com/saphelp_nwce10/helpdata/en/d3/f61140d72dc442e10000000a1550b0/frameset.htm

4.3.5.1 sap_ec_archiving_measurements

The Archive Set “sap_ec_archiving_measurements” archives measurement values of facilities for a given date period. The whole search result will be archived!

The Facility Id and the date period are required input fields.

Search criteria’s for archiving:

Field Name (* required) Description

Facility ID * Enter the Facility technical ID. The Facility technical ID can be read in the Facility detail view selecting the Technical Information pop-up

Include Subordinate Facilities

Flag: All measurements of the subordinate facilities will be archived too

From * Defines the period begin of the measurement data: e.g.: 1st

January 2008

To * Defines the period end of the measurement data: e.g.: 31st

December 2008

Include Scenarios Flag: All measurements within scenarios will be archived too

Purge logical deleted data before archiving

Flag: Before the archiving process begin, the system will delete physically all logical deleted measurements in the data base

4.3.5.2 sap_ec_archiving_emissions

The Archive Set “sap_ec_archiving_emissions” archives emission values of facilities for a given date period. Further more the archiving process archives the related the calculation logs. The whole search result will be archived!

The Facility Id and the date period are required input fields:





Flag: All emissions of the subordinate facilities will be archived too

From * Defines the period begin of the emissions data: e.g.: 1st January

2008

To * Defines the period end of the emissions data: e.g.: 31st

December 2008


42 Feb 2009

Include Scenarios Flag: All emissions within scenarios will be archived too


Flag: Before the archiving process begin, the system will delete physically all logical deleted emissions in the data base

4.3.5.3 sap_ec_archiving_consumptions

The Archive Set “sap_ec_archiving_consumptions” archives consumption values of facilities for a given date period. Further more the archiving process archives the related consumption parameter values and the calculation logs. The whole search result will be archived!

The Facility Id and the date period are required input fields:





Flag: All consumptions of the subordinate facilities will be archived too

From * Defines the period begin 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 Flag: All consumptions within scenarios will be archived too


Flag: Before the archiving process begin, the system will delete physically all logical deleted consumptions in the data base

4.3.5.4 sap_ec_archiving_tasks

The Archive Set “sap_ec_archiving_tasks” archives task instance values of a date period. Further more the archiving process archives the related task properties. Following table shows which related data is archived together with the task depending on the task type:

Name Description

Calculation Logs All task types

Task Users All task types

Cross-table Facilities All task types

Cross-table Requirements All task types

Cross Table Documents All task types

EAM EAM Task

User Defined Fields data All task types

Check List Checklist task


Feb 2009 43

Batch Production series Batch Task

Emissions Emission Task

Consumptions Consumption Task

Measurement Measurement Task

For further information about the different EC Task types please refer to the SAP_Environmental_Compliance_30_en_Functional_Documentation

The whole search result will be archived!

The date “From” and date “To” input fields are required search criteria’s.



Facility ID 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 Task Instances of the subordinate facilities will be archived too

From (Due Date):* Defines the period begin of the Task Instance Due Date e.g: 1st

January 2008

To (Due Date):* Defines the period end of the Task Instance Due Date: e.g: 31st

December 2008


Flag: Before the archiving process begin, the system will delete physically all logical deleted task instances in the EC data base

Task Status 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

Task Type Type of Task: Standard, Measurement Task,

TSK_TYPE_DEFAULT Standard Task

TSK_TYPE_CONSUMPTION Consumption Task

TSK_TYPE_MEASURING Measurement Task

TSK_TYPE_EMISSION Emission Task

TSK_TYPE_EAM EAM Notification Task

TSK_TYPE_EAM_ORDER EAM Order Task

TSK_TYPE_PRODUCTION_SERIES Production Series Task

TSK_TYPE_CHECKLISTXEM Standard Checklist Task


44 Feb 2009

4.3.5.5 sap_ec_archiving_exceptions

The Archive Set “sap_ec_archiving_exceptions” archives exception values of a given date period. Further more the archiving process archives the related EC exception properties. 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’s.

The whole search result will be archived!


Field Name(*required) Description

Facility ID 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 will be archived too

From * 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

Exception Status Status like New, In Process, Completed. Following integer values could be used as search criteria:

0 Status New

1 Status In Process

2 Status Completed


Feb 2009 45

4.3.5.6 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:


Field Name (*required) Description

From * Defines the period begin of the change document data: e.g: 1st

January 2008

To * Defines the period end of the change document data: e.g: 31st

December 2008

4.3.5 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 flag “Start delete Phase Automatically” in the schedule settings of the Write Archive View is set.

For further information about deleting archives please refer to the SAP Help (Java Archiving Cockpit): http://help.sap.com/saphelp_nwce10/helpdata/en/d3/f61140d72dc442e10000000a1550b0/frameset.htm


46 Feb 2009

4.3.6 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 which were done in the selected Archive Set.

The following picture describes the possible states of an Archiving Set:

State Description

Running The archiving is still running.

Scheduled The archive is planned for a later date

Failed The archiving process is failed � check the Log details (Log column in Archiving Monitor) for further information.

Incomplete The archiving process is incomplete � check the Log details (Log column in Archiving Monitor) for further information.

Completed The archiving process is completed. The write and delete process has been completed successfully.

For further information about monitoring archives please refer to the SAP Help (Java Archiving Cockpit): http://help.sap.com/saphelp_nwce10/helpdata/en/d3/f61140d72dc442e10000000a1550b0/frameset.htm


Feb 2009 47

4.3.6 Search archives Depended of the Archive Set type the user has the possibility to 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:

Following different search dialogs are available:

� Emissions, Consumptions and Measurements

� Task Instances

� Exceptions

� Change Documents

4.3.6.1 Emissions, Consumptions and Measurements The Search dialog for Emissions, Consumptions and Measurements is located in the Emission Manager module.

Authentication and Access

Searching archived transactional data of type Emissions, Consumptions and Measurements can be done by users which has the following permissions

� UME Access Permission for Emission Manager

� UME ArchiveSearch Permission for Emission Manager

� Portal permission for Emission Manager

Environmental Compliance 3.0 will not be 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"

Search Criteria’s

Consumptions, Measurements and Emissions 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’s as required fields:

The archived data can not be changed.

4.3.6.2 Task Instances The Search dialog for Task Instances is in the Task Manager module.


Searching archived transactional data of type Task Instances can be done by users which have the following permissions


48 Feb 2009

� UME Access Permission for Task Manager

� UME ArchiveSearch Permission for Task Manager

� Portal permission for Compliance Manager

Environmental Compliance 3.0 will not be delivered with permissions for searching Archived Task Instances. The EC Admin has to create new Role and assigned the upper named actions and permissions.

The EC user needs the UME Action “EC_TaskArchiveSearch"

Search Criteria’s

Archived Tasks can be searched in the Task Manager Activity with following search criteria’s:

Name (* required field)

Description

Type Type like “Standard Task”, “Consumption Task”, etc

Priority High, Low, etc.

Due Date Due date of the task

Completion Status Status of the Task; New, Completed, etc.

Parent Task Template Task Template (ID)

Path Extension* The Path of the Archiving Store

The archived Tasks result list is displayed in the Tasks Hit-list.

The archived Tasks details can not be changed

4.3.6.3 Exceptions The Search dialog for Exceptions is in the Exception Manager module.


Searching archived transactional data of type Exception can be done by users which have following permissions

� UME Access Permission for Exception Manager

� UME ArchiveSearch Permission for Exception Manager

� Portal permission for Compliance Manager

Environmental Compliance 3.0 will not be delivered with permissions for searching Archived Task Instances. The EC Admin has to create new Role and assigned the upper named actions and permissions.

The EC user needs the UME Action “EC_ExceptionManagerArchiveSearch"

Search Criteria’s

Archived Exceptions can be searched in the Exception Manager Activity with following search criteria’s:

Name (* required field) Description


Feb 2009 49

Type LOV: Type like Fire, Oil Splil, etc.

Assessment Special type like “Deviation”

Status Status like New, Completed

Start Date* Start Date period


The archived Exceptions result list is displayed in the Exception Hit-list.

The archived Exception details can not be changed

4.3.6.4 Change Documents The Search dialog for Change Documents is located in the Maintenance module.


Searching archived transactional data of type Change Documents can be done by users which has following permissions

� UME Menu Permission for ArchivedChangeDocument

� Portal permission for Environmental Compliance Admin

The EC user needs the UME Action “EC_ChangeDocumentArchives"

Search Criteria’s

Archived Change Documents can be searched in the Maintenance � Archived Change Document with following search criteria’s:

Name (* Required) Description

Domain List of available Modules: Facility, Exception, etc.

From Date* Time Frame “From”

To Date* Time Frame “To”

User User name in the system fields


The archived change documents are displayed in the change document hit-list


50 Feb 2009

4.4 Management of SAP EC SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively to 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 in the SAP Library under SAP NetWeaver CE 7.1.

4.4.1 Starting and Stopping Start and Stop Sequences and Tools

Software Component Detailed Description

SAP Netweaver CE Server

For further information please refer to the SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/44/9a894484d360d6e10000000a114a6b/frameset.htm

RFC Server For further information please refer to the chapter 4.4.8.2 Interfaces into SAP EH&S

4.4.2 Software Configuration This chapter explains which components or scenarios used by this application are configurable and which tools are available for adjusting.

We differ between two types of configuration:

� Application Configuration

� Technical Configuration

4.4.2.1 Application Configuration The EC Application Configuration enables 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 will be available in the EC Portal for Users with Admin Permissions (User within the User Group “UMEGROUP_Environmental Compliance Admin”)

These four menus are detailed described in the SAP_Environmental_Compliance_30_en_Functional_Documentation


Feb 2009 51

4.4.2.2 Technical Configuration The technical configuration enables to set up basic SAP Netweaver CE settings with the Configuration tool (Config Tool)

Further information about SAP Netweaver CE Config Tool refer to SAP Help http://help.sap.com/saphelp_nwce10/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm )

Component configuration tools

Component Configuration Tool(s) Detailed Description

Config Tool Set up Email Configuration Refer to the chapter 3.3.6 Set up Email Configuration for further information

Config Tool Check the Internet Graphics Service (IGS) settings

Refer to the chapter 3.4.10 Check the Internet Graphics Service (IGS) settings for further information

4.4.3 Backup and Restore All application data is stored in a Data Base system which is linked to the SAP NW CE 7.1. The application data includes also the configuration data of EC 3.0.

To configure Archiving of Log and Trace files please refer to the SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/45/66d4eb8f9d6102e10000000a1553f6/frameset.htm

For further information please refer to the SAP Help ”Administration of SAP NetWeaver CE”: http://help.sap.com/saphelp_nwce10/helpdata/en/45/49c5f692cf4d35e10000000a114a6b/frameset.htm

4.4.4 Application Copy Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Netweaver CE 7.1 please refer to the following documentation:

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/508e36c5-5914-2b10-a795-d25997cf3270

4.4.5 Periodic Tasks

4.4.5.1 Scheduled Periodic Tasks The JAVA scheduler provide all necessary EC scheduled Jobs.

Log in to the NWA (http://<host:port>/nwa/Scheduler) with an administrator user.

Following JAVA periodic tasks are available

Scheduled periodic tasks for Environmental Compliance:

Program Name/Task Recommended Frequency (Cron)

Detailed Description

SAP_Environmental_Compliance-CalculationSchedulerJob

0 30 * * * ? Every Hour at 30 Minutes

The Calculation scheduler job calculates all consumptions which have not been calculated


52 Feb 2009

yet.

SAP_Environmental_Compliance-LimitCheckJob


The Limit check scheduler job checks all new created or changed consumptions, emissions and measurements.

SAP_Environmental_Compliance-ExceptionGenerationJob

0 0 * * * ? Every Hour

The Exception generation job scans new created Exceptions. If there are Task with the Type “Occurrences of the task are generated on occurrence of an exception” then the Job generates the affected tasks.

SAP_Environmental_Compliance-TaskSchedulerForEAMObjectsJob


The EAM notification background job, scans all open EC EAM Tasks. The open EAM Tasks will be compared with the corresponding ERP PM Notifications. If one of the PM notifications status is different than the EC EAM Task Status, then the system will synchronize the Status of the EC EAM Tasks

SAP_Environmental_Compliance-ChecklistTaskSchedulerJob


Job checks SMTP mailbox if email with attached checklist is available.

If email with checklist is there, checklistfile will be opened, values will be extracted and imported to EC as Checklist values

SAP_Environmental_Compliance-BatchProcessCalculationJob


This Job calculates Batch Emissions based on production runs or production series.

SAP_Environmental_Compliance-AlertDetectorJob

0 0/10 * * * ? Every Ten Minutes

The Alert Detector job scans for outstanding emails and generates the email from the template

SAP_Environmental_Compliance-AlertManagerJob

0 5/10 * * * ? Every Ten Minutes

The Alert Manager sends the generated Emails with the Alert Detector job to the target users

SAP_Environmental_Compliance-ChangeDocumentJob


The Change Document copies the new created Change Document entries from a Buffer table into the final Change Document Data base table.

SAP_Environmental_Compliance-AutomaticReportGenerationJob

Once a Day when the Server has minimal workload

The Automatic Report Generation Job scans all released Report Generation Variants which have a valid Due Date and generates Reports based on the given Restrictions


Feb 2009 53

The scheduled Jobs should avoid to be run at the same time to load off the application

4.4.5.2 Required Manual Periodic Tasks Manual tasks for Environmental Compliance

Task Tool(s) supporting this task

Recommended Frequency

Detailed Description

Check Log files

Log Viewer Weekly The EC Administrator should check the EC logs due to of following problems: �Calculation errors �Grave error in the EC Persistency

Data base Overflow

Data Base Management tools

Weekly The Administrator should check if the EC Data base content and logs do not grow faster than the Data Base settings allow this.

EC System Checks

EC System Checks Once, after installation

The EC System checks should be checked after installing the EC Application. For further information please refer to the chapter: 4.7.3 Report Generation does not work

4.4.6 Load Balancing The Load Balancing is described in the SAP Help:

Refer to the chapter “SAP Load Balancing Protocol Specification” http://help.sap.com/saphelp_nwce10/helpdata/en/94/384b8e308b934f8b51cf2b5fb762b5/frameset.htm

Refer to the chapter “SAP Web Dispatcher” http://help.sap.com/saphelp_nwce10/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm

4.4.7 User Management For detailed information about user management engine (UME) please refer to the SAP Help for Netweaver 7.1 CE

http://help.sap.com/saphelp_nwce10/helpdata/en/cc/2e2d0b2b6e474dab2fcf3b11c2f052/frameset.htm

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 further information please refer to the SAP Help.

http://help.sap.com/saphelp_nwce10/helpdata/en/3b/0c38b2a3d04e90bacce336f0835119/frameset.htm


54 Feb 2009

4.4.8 Technical Interfaces

4.4.8.1 Web Services (Transactional Data) This chapter describes how to manage transactional data imported for Exceptions, Emissions, Measurements and Consumptions into EC. 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 Builder enables the user to create and manage mapping objects for importing Exceptions, Emissions, Measurements and Consumptions via Web Services. The mapping of external object IDs to EC object IDs takes place in the Configuration. These Web Services are relevant for the following EC components:

1. Mapping of external Object IDs to EC Objects

2. Definition of Exception Creation Web Services

3. Definition of Emission Import Web Services

4. Definition of the Measurement Import Web Services

5. Definition of the Consumption Import Web Services

4.4.8.1.1 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 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 → Infrastructure → Integrated Systems

Activity for creating System Integration

Description

Create a new system integration

To create a new system integration:

1. Navigate to Integrated Systems task in the EC Configuration. Click the link to open the Integrated Systems popup window.


Feb 2009 55

2. In the Integrated Systems view of the popup 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. Press the Save button.

The following sections of this document describe the Transactional Data Interfaces functionality in more detail:

� Facility type configuration.

� 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.

It is possible to create the same System Tag and System ID combination on several facilities. This will occur that the web service generates several entries in different facilities

4.4.8.1.2 The Integration User Interface

The integration user interface is accessible on the facility detail to define integration objects of the facility. This interface has four tabs for the object mapping like: Master Data (Exception), Consumption, Measurement, and Emission.

Tab Master Data

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

Description

Mapping Exceptions

To map Exceptions:

Prerequisite: you must have already defined an Integrated System.

In the Integration view:

1. Choose the Master Data tab.

2. In the Integration view of the dialog box presses the Create button. A new line opens where you can enter the mapping information.

3. First: To 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 next E. column (Lookup external systems) has no function in


56 Feb 2009

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 D. column.

8. Second: To 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 next E. column (Lookup external systems) 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 D. 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.

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, than the exception has the LOV administrator (SYS_ADMIN_USER)

user as assignee.

It is possible to create the same System Tag and System ID combination on several facilities. This will occur that the web service generates one exception with several facility assignments. Further more all facility responsible users will be assigning to the new created exception and this exception will appear on the affected user dashboard.

Tab Consumption

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

Description


Feb 2009 57

Mapping Consumptions

To map consumptions:

Prerequisites: you must have already defined an Integrated System. You must have already assigned materials to the facility.

1. In the Integration view, choose the Consumptions tab.

2. In the Integration view of the dialog box presses 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 Sys. Column.

6. Enter the external Tag Id in the External Tag ID column.

7. The “Overwrite” column enables to overwrite consumptions if the system detects the same consumption in the system

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 in the D. column.

10. Press the OK button to accept your entries.


It is possible to create the same System Tag and System ID combination on several facilities. This will occur that the web service generates several consumption entries in different facilities. The consumption parameter do not support this functionality, due to they are dependent on the imported consumption data.

Tab Measurement

The Measurement tab is used to define the measurement mapping between an external system and EC.

Activity for Mapping of Measurements

Description


58 Feb 2009

Mapping Measurements

To map measurements:

Prerequisites: you must have already defined an Integrated System.

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 to the right of the Material column that corresponds to the material you want to enter. 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 in the D. column. 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 to overwrite consumptions if the system detects the same measurement in the system


8. To delete the measurement mapping, press the Delete button in the D. column.




Feb 2009 59

Tab Emission

The Emission tab is used to define the emission mapping between an external system and EC.

Activity for Mapping of Emissions

Description

Mapping Emissions To map emissions:

Prerequisites: you must have already defined an Integrated System.

1. Choose the Emissions tab.

2. Presses Create button. A new line opens where you can enter the mapping information.

3. Material for consumption: select a consumption material from the dropdown menu in the Consum. Material column. Only assigned materials (see Materials tab) appears in this dropdown box.

4. Material for emission: enter a material in the Emission Material column. The material is required. To select a material, press the Magnifying glass button to the right of the Material column that corresponds to the material you want to enter. 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 U. 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 to overwrite consumptions if the system detects the same emission in the system


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 D. column.




60 Feb 2009

4.4.8.1.3 Overwrite available values

EC supports the functionality to overwrite available consumptions, consumption parameters, measurements and emissions. In the facility integration definition the user has the possibility to define if the defined tag allows to be overwritten.

If the "Overwrite" flag is not set and the system detects a similar object during the import process, than the web service returns an error value.

If the "Overwrite" flag is set and the system detects a similar object during the import process, than the value will be overwritten, the status of the object will be changed and the previous value of the object will be saved into the data base field "Status info". This enables to report on the status field and status info field to see which values has been imported and which values has been overwritten.

Follow status 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

The overwrite mechanism is not available for exceptions. The EC System created every time a new EC Exception.

4.4.8.1.4 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. It will be further recommended to use 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) decides how the time will be imported into EC.

The following example shows how to define a date time for consumptions and emissions.

Date From (UTC) 2007-03-01T00:00:00.000+00:00

Date From (USA Pacific Time) 2007-03-01T:08:00.000-08:00

Date To (UTC) 2007-03-01T23:59:59.000+00:00

Date To (USA Pacific Time) 2007-03-02T07:59:59.000-08:00

Measurements

The date and time of the measurement will be set from the imported date (interface) value.

The measured date supports also the time zone information

Example:


Feb 2009 61

Date To (UTC) 2007-03-01T14:15:55.000+00: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 will be 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 supports the follow format with time zone information

Example:

Date To (UTC) 2007-03-01T14:15:55.000+00:00

For further information about EC Data Handling please refer to SAP OSS Note: 1067441

4.4.8.1.5 Date Handling with Time Zone Settings

The standard deprecated 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.

The EC 3.0 Web services offer a possibility to directly provide the date and time and 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 can not 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

The parameters are identical to their existing counterparts except that “pStartDate” will be 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 can not be uniquely mapped to a facility, the timestamp database value has to be interpreted in the server’s default time zone.


- doProdSeriesImportLocalTime

- doProdSeriesImportsLocalTime


62 Feb 2009

The parameters are identical to their existing counterparts except that “pStartDate” and “pEndDate” will be replaced by:



- 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 which 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 will be used.


- doConsumptionImportLocalTime

- doConsumptionsImportLocalTime

The parameters are identical to their existing counterparts except that “pDateTimeFrom” and “pDateTimeTo” will be replaced by:





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 which 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 will be used.

The webservice “xEM_EmissionImport” shall provide methods for importing data using date and time strings.

Description :

Two new methods will be provided:

- doEmissionImport

- doEmissionsImport

The parameters are identical to their existing counterparts except that “pDateFrom” and “pDateTo” will be replaced by:






Feb 2009 63

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 which 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 will be used


- doMeasurementImport

- doMeasurementImports

The parameters are identical to their existing counterparts except that “pDate” and will be 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 new created EC Exception record as is.

The timestamp information is interpreted by using the time zone which is assigned at the facility. If the facility does not have a time zone assigned, the server’s default time zone will be used.

One new method is provided:

- triggerExceptionExtendedLocalTime

The parameters are identical to their existing counterparts except that “pDateIdentified”, “pDateStarted” and “pDateEnded” will be 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





4.4.8.1.6 Overview over all EC 3.0 Web services

Every Transactional Web Services exists twice in the EC System. The reason for this is that the EC 3.0 has completely new Web Services which are based on the new EJB 3.0 and supports new Methods with enhanced Time Zone settings, refer also to the chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

The old web services from EC 2.0 SP13 are needed for customers which has already Web clients based on the EC 2.0 SP13 WSDL files. These Web Services are deprecated for new EC 3.0 Customers. See also the column deprecated in the following Table:

Technical Name of the Web service WSDL compatibility

Depre- cated

technidata.de/xem~facility~internal~eappl_com.technidata.em.imp. cnsptnimp_xEM_ConsumptionImportVi

EC 2.0 SP13 Consumption

X


64 Feb 2009

Web Service

technidata.de/xem~facility~ws~eappl_technidata.de~xem~facility~ws~ ejb_EJB_ConsumptionImport

EC 3.0 Consumption Web Service

technidata.de/xem~facility~internal~eappl_com.technidata.em.imp. emssnimp_xEM_EmissionImportVi

EC 2.0 SP13 Emission Web Service

X

technidata.de/xem~facility~ws~eappl_technidata.de~xem~facility~ws ~ejb_EJB_EmissionImport

EC 3.0 Emission Web Service

technidata.de/xem~facility~internal~eappl_com.technidata.em.webservice. msrmtimp_xEM_MeasurementImportVi

EC 2.0 SP13 Measurement Web Service

X

technidata.de/xem~facility~ws~eappl_technidata.de~xem~facility~ws ~ejb_EJB_MeasurementImport

EC 3.0 Measurement Web Service

technidata.de/xem~batcalc~module~eappl_com.technidata.em.imp. prrunimp_xEM_ProductionRunImportVi

EC 2.0 SP13 Production Run Web Service

X

technidata.de/xem~batcalc~ws~eappl_technidata.de~xem~batcalc~ws ~ejb_EJB_ProductionRunImport

EC 3.0 Production Run Web Service

technidata.de/xem~batcalc~module~eappl_com.technidata.em.imp. prseriesimp_xEM_ProductionSeriesImportVi

EC 2.0 SP13 Production Series Web Service

X

technidata.de/xem~batcalc~ws~eappl_technidata.de~xem~batcalc~ws~ ejb_EJB_ProductionSeriesImport

EC 3.0 Production Series Web Service

technidata.de/xem~taskexc~internal~eappl_com.technidata.em.imp. exptntrig_xEM_ExceptionTriggerVi

EC 2.0 SP13 Exceptions Web Service

X

technidata.de/xem~taskexc~ws~eappl_technidata.de~xem~taskexc~ws~ ejb_EJB_ExceptionTrigger

EC 3.0 Exceptions Web Service

technidata.de/xem~facility~internal~eappl_com.technidata.em.ws. facsetdetail_EmFacilitySetDetailVi

EC 2.0 SP13 Set Facility Detail

technidata.de/xem~facility~internal~eappl_com.technidata.em. ws_EmFacilityGetDetailVi

EC 2.0 SP13 Get Facility Detail

technidata.de/xem~facility~internal~eappl_com.technidata.em. ws_EmFacilityGetF4Vi

EC 2.0 SP13 Set Facility F4

technidata.de/xem~facility~internal~eappl_com.technidata.em. EC 2.0 SP13


Feb 2009 65

ws_EmFacilityGetListVi Set Facility List

technidata.de/xem~facility~internal~eappl_com.technidata.em. ws_EmSDPChecklistImporterVi

EC 2.0 SP13 SDP Checklist

technidata.de/xem~facility~internal~eappl_de.technidata.xem.facility. webserv.faccomp.facilitycreate_EmFacCompFacilityCreateVi

EC 2.0 SP13 Create Facility

technidata.de/xem~facility~internal~eappl_com.technidata. util_xEM_ExternalSystemsVi

EC 2.0 SP13 External Systems

4.4.8.1.7 EC Consumption Data Import

For the consumption data import, the Web Service is called EC_ConsumptionImport and offers the following operations:

Operation Name Description

checkConnection Return a string if the connection works

doConsumptionImport Run one consumption import

doConsumptionImportLocalTime Run one consumption import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

doConsumptionsImport Run one or more consumption import

doConsumptionsImportLocalTime Run one or more consumption import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

getConsumptionPeriod Determine correct Facility/Material combination based on given Ext. System ID and Ext. System Tag ID

getErrorCodes Return List of valid Error and Warning codes

getParamSupportedUnits Return List of defined Units of a dimension for consumption parameter, which is defined in the parameter management(SAP R/3 Ext IDs)

getSupportedUnits Return List of defined Units of a dimension for consumption, which is defined in the facility material assignment(SAP R/3 Ext IDs)

The following operations doConsumptionImport, doConsumptionImportLocalTime, doConsumptionsImport and doConsumptionsImportLocalTime have following optional Interfaces:

� optional: pAmountUnit (String) If the unit is empty(null), then the system takes the unit from the facility consumption integration definition

� optional: pDescription (String) Set to null, if not used

� optional: pTier (String) Set to null, if not used.


66 Feb 2009

� optional: pSimpleConsumptionParams (consumptionParam[])

Set to null, if not used.

� optional: pConsumptionParamets (consumptionParam[])

Set to null, if not used.

The Consumption Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_EmissionManagerWebService”.

4.4.8.1.8 EC Emission Data Import

For the emission import, the Web Service is called EC_EmissionImport and offers the following operations:



doEmissionImport Run one emission import

doEmissionImportLocalTime Run one emission import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

doEmissionsImport Run one or more emissions import

doEmissionsImportLocalTime Run one or more emissions import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.


getSupportedUnits Return List of defined Units of Emission

The following operations doEmissionImport, doEmissionImportLocalTime, doEmissionsImport and doEmissionsImportLocalTime have following optional Interfaces

� optional: pUnit (String) If the unit is empty(null), then the system takes the unit from the facility emission integration definition

� optional: pDescription (String) Set to null, if not used

� optional: pUncertainty (int) Set to null, if not used.

� optional: pPercentGood (int) Set to null, if not used. If percentage good is provided, calculate Uncer-tainty as 100% - pPercentGood. If both is sup-plied, Uncertainty will be used.

The Emission Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_EmissionManagerWebService”.


Feb 2009 67

4.4.8.1.9 EC Exception Data Import Operations

To allow an external system to generate and show alerts on the operators console that are based on limit deviations, the external system must have a possibility to query the limit information for a certain facility. To allow this, a Web Service called EC_ExceptionTrigger is created, which offers the following operations:



triggerException Create a new Exception in EC System

triggerExceptionExtended Create a new Exception in EC System, with extended Interface

triggerExceptionExtendedLocalTime Create a new Exception in EC System, with extended Interface with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.


getExceptionTypes Return List of defined exception types of EC

getUDFbyExceptionType See Detailed description below

The following operations triggerExceptionExtended and triggerExceptionExtendedLocalTime have following optional Interfaces:

� pDateEnded (java.util.Date) � pProbableCause (String) � pCorrectiveAction (String) � pUDFKeyValue[] (KeyValue) Array Of UDF Key, Value and Type

Further information #1: The assignee of the exception is the facility responsible. If the facility has no responsible user, than the exception has the LOV administrator (SYS_ADMIN_USER) user as assignee

Further information #2: Operation getUDFbyExceptionType

� Interface :

� pExceptionType (String) Exception Type (required)

o Return value: � (XML String)

o Functionality: � This method delivers for a given exception types all available UDF

information. The return value is build up in a XML String and has the follow format: <![CDATA[

<data>

<tabs>

<tab name = "FELIX_Data">



<rows>

<row rowno="0">

<entryname name="MY_DATE"

assign_id="1000002"

element_id="1000003"

datatype="7"/>


68 Feb 2009

<entrydata></entrydata>

<addentrydata></addentrydata>

</row>

<row rowno="1">

<entryname name="MY_STRING"

assign_id="1000003"

element_id="1000004"

datatype="1"/>

<entrydata></entrydata>

<addentrydata></addentrydata>

</row>

</tab>

</tabs>

<dropdowndata>

</dropdowndata>

</data>]]>

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.

The Exception Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_ExceptionWebService”.

4.4.8.1.10 EC Measurement Data Import

For the measurement data import, the Web Service is called EC_MeasurementImport and offers the following operations:



doMeasurementImport Run one Measurement import

doMeasurementImportLocalTime Run one Measurement import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

doMeasurementsImport Run one or more Measurements import

doMeasurementsImportLocalTime Run one or more Measurements import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.


getSupportedUnits Return List of defined Units of Measure

The following operations doMeasurementImport, doMeasurementImportLocalTime, doMeasurementsImport and doMeasurementsImportLocalTime have following optional Interfaces:

� pUnit (String) If the unit is empty(null), then the system takes the unit from the


Feb 2009 69

facility measurement integration definition

� pDescription (String) Description of imported measurement

The Measurement Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_EmissionManagerWebService”.

4.4.8.1.11 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:



getAllTags Return all External Systems Tags that are defined for the passed system. (Tags for Consumptions, Consumption Parameters, Emissions and Measurements)

getConsumptionParameterTags 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

getConsumptionTags Return all External Systems Tags that are defined for ConsumptionIntegration for the passed system

getEmissionTags Return all External Systems Tags that are defined for Emission Integration for the passed system

getMeasurementTags Return all External Systems Tags that are defined for Measurement Integration for the passed system

Further information :

Operation getConsumptionParameterTags

o Interface :

� pSystemId (String) Unique identifier for external system. Set this parameter to NULL to get tags for all systems.

� pAddConsTagPrefix (Boolean) If this parameter is set to TRUE the return value will contain also 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

� Return value: � Ext. System Tag IDs (String [])


70 Feb 2009

The External Systems Tags Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_EmissionManagerWebService”.

4.4.8.1.12 EC Production Series Data Import Operations

For the Batch Process Production Series import, the Web Service is called EC_ProductionSeriesImport and offers the following operations:



doProdSeriesImport Run one Production Series import

doProdSeriesImportLocalTime Run one Production Series import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

doProdSeriesImports Run one or more Production Series import

doProdSeriesImportsLocalTime Run one or more Production Series import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.


The Production Series Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_BatchProcessWebService”.

4.4.8.1.13 EC Production Run Data Import Operations

For the Batch Process Production Run import, the Web Service is called EC_ProductionRunImport and offers the following operations:



doProductionRunImport Run one Production Run import

doProductionRunImportLocalTime Run one Production Run import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.

doProductionRunImports Run one or more Production Run import

doProductionRunImportsLocalTime Run one or more Production Run import with local date time settings: refer to chapter 4.4.8.1.5 Date Handling with Time Zone Settings.


The Production Run Web Service needs UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_BatchProcessWebService”.


Feb 2009 71

4.4.8.1.14 Web Services for 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) element(s). The Web Service is used from outside of the Environmental Compliance to generate new facility objects. The new created object appears then in the Facility Builder of EC beneath the External Created Facility node.

The Web Service EMFacCompFacCreate offers the following operations (WSO):

The Facility Compliance Web Services need UME permission. You need a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” or which has the Action “EC_FacilityComplianceWebService”.

WSO checkConnection

The following table displays required input value(s) and the return value(s) 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 value(s) and the return value(s) of the web service operation.


getFacilityTypes

Input parameter Typ 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 connection error, connection is active but currently the system is not available


72 Feb 2009

ErrorCode = 2 Data base error

ErrorCode = 4 Required language is not available

ErrorCode = 16 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 value(s) and the return value(s) of the web service operation.


getValidityAreas


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 Connection error, connection is active but currently the system is not available.

ErrorCode = 2 Data base error.

ErrorCode = 4 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.


Feb 2009 73

WSO createFacilityByType

This operator creates the facility by type. The following table displays required input value(s) and the return value(s) of the web service operation.


createFacilityByType

Input parameter Typ 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 will use 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 will be set down.

Return value Int ErrorCode = 0 Everything ok.


ErrorCode = 2 Data base error

ErrorCode = 4 Required language is not available.

ErrorCode = 16 A wrong parameter is handed over.

ErrorCode = 32 Error during creating facility. A facility with the handed over RefType and RefId still exist in system.

ErrorCode = 64 Error occurs while processing. The error occurs during facility creation.

Comment If no language code is set the system will use the standard language EN per default for the name, which will be delivered first. This means, if only one name is handed over, e. g. in German then the system will use this name also for the English translation.

WSO createFacilitiesByType

This operator creates more then one facility by type. The following table displays required input value(s) and the return value(s) of the web service operation.


74 Feb 2009

Web-Service Operation createFacilitiesByType


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) Name 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.

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 will be set down.

Comment If no language code is set the system will use the standard language EN per default for the name, which will be delivered first. This means, if only one name is handed over, e. g. in German then the system will use this name also for the English translation.

Return value Type Name/ Value Meaning

Int ErrorCode = 0 Everything ok.


ErrorCode = 64 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 accurse during facility creation.

Type Array Element

Meaning

String (255) Name Name of the erroneous facility.

String (255) RefType RefType of the erroneous


Feb 2009 75

facility.

String (255) RefId RefId of the erroneous facility.

Int ErrorCode = 2 Data base error.

ErrorCode = 4 Required language not available.

ErrorCode = 16 Wrong parameter was handed over.

ErrorCode = 32 Error during creating facility. A facility with the handed over RefType and RefId still exist in system.

ErrorCode = 64 Error occurs while processing. The error occurs during facility creation.

WSO getErrorCodes

This operator reads out the errors. The following table displays required input value(s) and the return value(s) of the web service operation.

WebService Operation


String(2) Language Language code, in which language a possible error should be reported. If no language code is set the system use EN per default. If the error massage not available in the requested language code the system will use also the default language English (Optional).

Return value Liste Error Codes A list contains all error codes.

Integer ErrorCode = 0 Everything ok.

ErrorCode = -1 Unexpected error.

Remark None


76 Feb 2009

4.4.8.2 Interfaces into SAP EH&S This chapter describes the handling of EH&S Integration within EC. It explains the integration installation process in detail looks.

SAP EC supports various integration points. For example, EC supports EH&S integration points so that:

• EH&S Specification data and EC Material parameters can be linked.

• EH&S Properties and EC Material Property values can be linked.

• EH&S Specification identifiers and EC Material Identifiers can be linked

• EH&S Specification Classifiers and EC Material Classifiers can be linked

• EH&S Specification Compositions and EC Material parameters can be linked.

• A scheduled job in R/3 determines changed Substances and updates the EC Properties.

Additionally, the integration from EH&S to EC contains material identifiers from EH&S specifications, material classifiers from EH&S phrases and material parameter sets from specification compositions.

The data transfer runs always from EH&S to EC. The EH&S System is the master system.

Requirements

Environmental Compliance 3.0 supports only R/3 Systems Version 470 and higher with Unicode. Lower systems are not supported.

Installation

EC-EH&S integration uses SAP RFC calls. The EC system registers at the R/3 system. Once this registration is established, R/3 can call functions on the EC System

Prerequisites

The following prerequisites must be satisfied before EC-EH&S integration can be established:

� EC 3.0 installed

� EC R/3 Transports loaded

� ERP EH&S installed & configured

The R/3 Transports which are delivered with EC Support Package contains ABAP Functions in the Namespace “/TDAG/” which helps to integrate EC with EH&S.

ERP RFC Setup

A RFC ERP Destination entry must be maintained (in ERP Transaction SM59 � TCP/IP Connections) in the R/3 system before RFC registration can occur.

The RFC Destination must have a destination type T with an activation type Register.

The Program-ID could be “EC30”.

The RCF destination differs between Unicode systems and Non Unicode Systems. The Unicode systems should have the flag “Unicode” in the Setting “Character Width in

Target System” on the Tab Strip “Special Options”


Feb 2009 77

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 EC side.

Log into the NWA (http://<host>:<port>/nwa/destinations)

In this View you have to set up 2 connections to the ERP System.

The two connections are required due to of the bidirectional communication

a. Set up first connection. Enter the ERP System name as destination (Example “ERP”) Set up the destination details. See SAP HELP http://help.sap.com/saphelp_nwce10/helpdata/en/07/0d27932264284b883dab13ce1008a6/frameset.htm After finishing the destination setup you can test the connection pinging the ERP destination system.

b. 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 like step a). Enter the same destination setup properties like step a).

After finishing the Destination setup the next step is to set up the JCO RFC Provider

Navigate to Configuration Management --> Infrastructure --> JCO RFC Provider

In this view create a JCO RFC Destination

Enter Program ID (Example: “EC30”)

Enter in the next Step the RFC Destination Name like the step 2 destination "ERP Name + Provider" (Example: “ERP PROVIDER”)

For further information please refer to SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/44/3bd73865524903e10000000a1553f7/frameset.htm

After you set up successfully the JCO RFC Destination, you can start the server in this view.

On EC Side you have to assign the different Modules to the Destinations.

Log in to the portal (http://<host:port>/irj) with a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin”.

Navigate to Plant compliance --> Configuration --> Integration --> RFC Configuration

Now you assign the Material Reference and Substance Reference to the new created "Destination in the Step a)".

When you navigate to the Master Data --> Materials and you select a material, you can now search for ERP specifications and ERP Materials on the Integration Tab.

Check technical connection

If the EC and the R/3 parts are set up properly, the RFC destination can be checked in transaction SM59. The result should look like this:

Data Update Job

To have the system update data on a nightly basis, schedule the program /TDAG/XEMSYNCSUB 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 can be used.


78 Feb 2009

To test execute the program via transaction /TDAG/XEMSYNCSUB.

The selection fields are:

� Key Date – The latest changes that will be transferred. Default is “today”

� DeltaDay – Added days to key date, to enable a “Multiple Days” update period. Defaulted to 1

� Rating/ValArea - The rating and validity area to be considered while reading data. Defaulted to PUBLIC/REG_WORLD

� RfcDest – The RFC-Destination used.

� UpdateVa (Update Values and Identifiers) – This flag activates the functionality to update EC material values and material identifiers from EH&S specification identifiers.

� UpdateCa (Update Classifiers) - This flag activates the functionality to update EC material classifiers from EH&S specification phrases

� UpdateCo (Update Compositions) - This flag activates the functionality to update EC material parameter sets from EH&S specification compositions.

� UpdateCo2 (Update/Delete Compositions) - This flag activates the functionality to update EC material parameter sets from EH&S specification compositions. The flag delete the manual created parameter sets in EC of the linked materials.

After executing the program /TDAG/XEMSYNCSUB, the report will display all results pushed to EC and potential errors.

4.4.8.3.1 Transfer capabilities of Characteristics from EH&S

The Integration of EHS Characteristics links EHS Characteristics with EC Material Single Parameters.

There are two types that support automatic data transfers from EH&S 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 R/3 EH&S the parameter must be “linked” to a substance property. The link can be made in the parameter definition screen in the EC Configuration � Emissions Management � Parameters

The EH&S substance property and an EC value characteristic name must be defined. Ensure that the EH&S property value and the EC parameter have the same unit dimension.

Additional Information

The parameter property Set indicates whether or not the transferred value will be a single parameter or a parameter set.

Sequence numbers and materials are transferred from EH&S 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 EH&S are linked with a single parameter, then only the first values (sequence 1) will be transferred to EC and the sequence will be changed to 0 (order number).

: The EH&S Characteristics can be saved as ranges. Example: Density Temperature <25°C. The greater and lower operator will not be transferred to EC. The example value will be transferred to EC as 25°C.


Feb 2009 79

Material Link

The second link that supports an automatic data load from EH&S to EC has to be set up in the material view. An EC material can either link to either an EH&S material or an EH&S substance.

Select the correct integration type and enter either a material number or substance id.

To test call the transaction /TDAG/XEMSYNCSUB to load recently changed data.

Please be aware that:

� Only value properties can be loaded

� The Usage and Activity Flag must be maintained correctly or

� /TDAG/XEMSYNCSUB must be called without usage (Rating field and Validity Area field are empty) and all changes will be transferred

� Only substances updated since the “key date” + the “Delta days” will be transferred

� The material has to be reloaded to see the effect of the data load.

EC has materials with several parameters. Some of the parameters are linked (integrated) with EH&S values and some not. The material parameters, which are linked to EH&S, will be considered for the data transfer from EH&S. Parameters that are not integrated (linked) will not be touched (deleted or modified) by the EH&S integration and could be used for calculations as well.

Implicit unit conversion during transfer

If the maintained unit in EC is the same as the property unit in EH&S, the value in EH&S will not be converted when transferred to EC.

If the units are different, the property unit will be converted and the maintained unit will be transferred to EC.

If the user enters a property value in EH&S without a unit, the program will transfer the unit val to EC. This unit is dimensionless.

Source Information for values

If a specification value has a source information, this will be transferred automatically with the EH&S value to EC material single parameter or/and 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 (Upper example: Clean Air Act (CAA) Section 109 NPSAQS - Test)

If a parameter already has source information (EC Comment) the value will be overwritten.

4.4.8.3.2 Material Groups

A special property in R/3 EH&S can be used to link to material groups. The name of this property can be set in the EC Properties, in

Application: XemPutValues

Value: com.technidata.em.r3.mat_grp_propertyalue


80 Feb 2009

If this is not maintained, a default value of ZNC_EHS_1013_076 will be taken.

This EH&S 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 will be 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.

In case the material characteristic will be extracted to BW, the code field will be used to take both the BW info object name and the R/3 characteristic. In this case both have to be separated by a “;”, e.g. BW InfoObj;EH&S Characteristic.

4.4.8.3.3 Transfer capabilities for EC Material classifiers from EH&S

With the SAP Program /TDAG/XEMSYNCSUB it is possible to transfer EH&S Phrases from R/3 System to EC List of Values (LOVs). Some EC settings must be maintained in this feature before the data will be transferred automatically from EH&S to EC.

EC LOVs linking to EH&S Phrases

The List of Values (LOV) that are used for material classifiers should be linked to EH&S Phrases.

The linking of EC LOVs will be defined in the code field of the Fact Details.

The material classifier LOV has a hierarchal build up. The upper level in the tree shows the classifier type of 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: Further more it is possible to define the usage of the EHS in the EC. After the characteristic the rating and validity are could be put into the LOV Code definition separated with a semicolon (;)

Examples:

Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE Description: The usage will be read from the application (See Picture 4)

Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;PUBLIC;US Description: The usage rating: PUBLIC, Validity Area: US will be used for this classifier. The usage in the application will be ignored

Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;PUBLIC;* Description: The usage Rating: PUBLIC, All Validity Areas will be used for this classifier. The usage in the application will be ignored


Feb 2009 81

Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;*;DE Description: The usage: Rating: all, Validity Area: Germany will be used for this classifier. The usage in the application will be ignored

Type LOV Code field: SAP_EHS_1023_032; SAP_EHS_1023_032_BASE;*;* Description: All rating and validity areas will be read for this classifier. The usage in the application will be ignored

The “*” is a wildcard for all ratings and all validity areas.

The Value LOV should contains the value of the phrase like CED-N15.00309080

The LOVs are now linked with the EHS Phrases. When a phrase of the type is changed in EHS and the application /TDAG/XEMSYNCSUB is started, the facts (LOV) will be automatically be inserted in the material classifier.

The properties that contain the Classifiers in EH&S need to be maintained with the correct usage (rating and validity area) to be transferred to EC correctly.

If all sort sequences of a valuation type in EH&S is deleted, this deletion cannot be transferred to EC; the values have to be deleted manually in EC.

BADI implementation as customer exit for Material Classifiers

In Environmental Compliance SP12 a new BAdi interface has been implemented to enable to change the return EH&S classifiers data before it is send from R/3 EHS to Environmental Compliance System. The BAdi will be only used for transfer Material Classifiers to Environmental Compliance. Name of the BAdi: /TDAG/EC_MAT_CL_INTE The BAdi offers one Method READ_AND_WRITE_MAT_CLASSIFIER which has two parameters

- I_MATERIAL_CLASSIFIER (importing parameter)

- E_MATERIAL_CLASSIFIER (exporting parameter)

The importing parameter table (I_MATERIAL_CLASSIFIER ) contains the classifier data which 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 will be transferred to Environmental Compliance. Following information is transferred to Environmental Compliance:

Transferred Data

The following structure (fields) will be send to Environmental Compliance System: 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


82 Feb 2009

4.4.8.3.4 Transfer capabilities for EH&S Compositions to EC Material Parameter Sets

This feature copies automatically composition values from changed EH&S specifications to EC. In EC these composition values and materials will appear as material parameter set. Some settings must be maintained in EC before the data will be transferred automatically from EH&S to EC.

Link Parameters and Material with R3 System

The used parameters and materials must be linked to EHS Composition valuation type.

A parameter which will be linked to an EH&S composition has to be defined as a material parameter set in EC.

Furthermore, the integration drop down SAP EH&S Composition has to be selected and the value of the row has to be an EH&S composition valuation type German: Bewertungsart

like SAP_EHS_1012_002 (Exact composition based on compounds)

The information about the EH&S valuation type can be read when you press F1 and the mouse cursor select the composition in the EH&S “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 EH&S specifications (not with R3 Materials).

After the parameters and materials in EC are integrated the SAP EH&S application /TDAG/XEMSYNCSUB must be started.

Example Integration of EH&S Compositions to EC

The EHS Specification IS_EC_TEST is linked with a EC Material “IS_Test”

The EHS Specification IS_EC_TEST2, which is a component of IS_EC_TEST is also linked with a EC Material “Composition Material EHS”

The EHS Specification ISTEST001 is not linked with EC Material and it will be ignored during the integration process

After running the program XEMSYNCSUB the system shows follow message:

Programm /TDAG/XEMSYNCSUB

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!


Feb 2009 83

If the EHS Composition Value is null or empty, then the system will transfer the value 0 to EC like the upper example. The upper and lower limits of the EH&S compositions will not be transferred to EC.

The EH&S Characteristics can be saved in EH&S as ranges with a greater or lower characteristic. <25°C. The greater and lower operator will not be transferred to EC. The example value will be transferred to EC as 25°C.

Update/Delete Compositions

Since EC 2.0 SP10 Patch 5 the integration of compositions has two different functionalities:

1. Update Compositions: The system reads the changed compositions from EH&S 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 will be updated. When EC has different compositions (manual created) like the compositions from EH&S, the system will ignore the compositions in EC System.

2. Update and Delete Compositions. This mode is the same like the upper described mode, but the different compositions from EHS and EC will be deleted on the EC system. After running the SYNCSUB Program the EC System has the same compositions like the EH&S system. Manually created compositions in EC will be deleted.

4.4.8.3.5 Transfer capabilities for EH&S Identifiers to EC

This feature automatically copies identifiers changed in EH&S specifications to corresponding identifiers in EC Materials.

Some settings must be maintained in EC before the data will be transferred automatically from EH&S 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 List of value materials � material identifier

The EC material needs a link (integration) to the EHS specification.

EC is delivered with pre defined 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 will be disabled and automatically overwritten by the identifier.

The material identifiers, which are linked to EH&S, will be considered for the data transfer from EH&S. Material identifiers which are not integrated (linked) will not be touched (deleted or modified) by the EH&S integration.


84 Feb 2009

4.4.8.3.6 Transfer capabilities for Units from R/3 to EC

The R/3 transaction CUNI in R/3 allows the user to enter one specific, or a range of specific units or dimensions. These units and dimensions can be transferred to EC with the program /TDAG/XEMSYNCUNIT. 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 will be transferred automatically from EH&S to EC.

Start R/3 program to transfer units/dimensions

The program /TDAG/XEMSYNCUNIT enable the user to select Units and Dimensions and to select a language. This language will be saved in the EC unit/dimension text. The default language in EC is English. This language will be automatically set. If you select a language other than English, EC will save both languages for unit and dimension.

The selection fields are:

� 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


Feb 2009 85

4.4.8.3 Interfaces into SAP MII This chaoter describes how to configure MII 11.5 for Environmental Compliance and the first steps running the web service client for SAP Environmental Compliance.

This document describes only the Installation of Environmental Compliance Actions for xMII 11.5

Installing the Environmental Compliance Actions

In order to install the custom action block the following files need to be copied into various directories of the xMII server.

File Name Directory

xEM_xMII_Interface.jar <Drive Letter>:\ServletExec AS\se-<LHCMS or

xMII>\webapps\default\Lighthamer\WEB-INF\lib

xEM_xMII_Interface.jar <Drive Letter>:\ServletExec AS\se-<LHCMS or

xMII>\webapps\default\Lighthamer\CMSLogicEditor

SAPxEMActions.xml <Drive Letter>:\Lighthammer\Xacute\Components

Delivered sample transactions (trx) files

<Drive Letter>:\Lighthammer\Xacute\Transactions

Delivered sample xml files for the XML Loader samples

<Drive Letter>:\Lighthammer\Xacute\Transactions

Once these files are copied to the appropriate directories the following actions need to be performed

1. The Servlet Exec/xMII or Servlet Exec/LHCMS service needs to be stopped

2. The Java Web Start Cache needs to be cleared

a. C:\Documents and Settings\<UserName>\ApplicationData\Sun\Java\Deployment\

cache

b. C:\Documents and Settings\<UserName>\ ApplicationData\Sun\Java\Deployment\javaws\cache

3. The JNLP files in the following directory need to be deleted

a. <Drive Letter>:\ServletExec AS\se-<LHCMS or xMII>\webapps\default\Lighthamer\CMSLogicEditor

4. The Servlet Exec/xMII or Servlet Exec/LHCMS service needs to be started

Your new Environmental Compliance XMII Custom Action is now ready for use, log into the xMII System and open up the Business Logic Editor to verify that the Environmental Compliance actions were successfully installed.

Environmental Compliance xMII Actions

Environmental Compliance delivers several Actions which calls Environmental Compliance Web-services.


86 Feb 2009

Following actions are available in Environmental Compliance

1. Consumption Action: � uses web service xEM_ConsumptionImport web service (depracated) method: doConsumptionsImport

2. Emission Action: � uses web service xEM_EmissionImport web service (depracated) method: doEmissionsImport

3. Exception Action: � uses web service xEM_ExceptionTrigger web service (depracated) method: triggerException

4. Exception Extended Action: � uses web service xEM_ExceptionTrigger web service (depracated) method: triggerExceptionExtended

5. Measurement Action: � uses web service xEM_MeasurementImport web service (depracated) method: doMeasurementsImport

6. Batch Process Production Run Action: � uses web service xEM_ProductionRunImport web service (depracated) method: doProductionRunImports

7. Batch Process Production Series Actions: � uses web service xEM_ProductionSeriesImport web service (depracated) method: doProdSeriesImports

Transactions

Environmental Compliance will be delivered with several sample transactions.

The following sample transactions are delivered with Environmental Compliance:

- 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 XML file.

Running a sample measurement transaction

This chapter describes how to configure xMII Logical Editor running the measurements sample.

Start xMII:

http://<Server>:<Port>/Lighthammer/Menu.jsp

Start the Logic Editor in the xMII Menu “Business Logic Services”

The Environmental Compliance Actions are in the Window “SAP xEM” within the xMII Logic Editor.

Load delivered Environmental Compliance transaction sample in menu: Files � Open � “MeasurementSampleAction“

The system displays the sample: See picture below


Feb 2009 87

Before running the sample the target system should be configured.

Permission check: The imported data via EC web services will be checked based on the Facility Reference. For further information please refer to the Chapter 4.8 Application Security

Description of the sequences

Sequence 1 – XML Loader

The XML Loader is responsible for loading the measurement data. 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 which content 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.

D:\Lighthammer\Xacute\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, which is read in the repeater, will be 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 it sends every single record to the Sequence 4 (Measurement Node).

Configuration:


88 Feb 2009

The Repeater has the XPath configuration which will be 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 will be send to the container.

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 like Description, System ID, Tag ID, Value, Unit and Date are default values for the imported measurement. When the system detect incoming values from the XML (this sample) it will ignore the default values.

Sequence 5 – Tracer of Measurements Node

The tracer is a Log printer which shows the data flow of a configured action.

Configuration:

In the link editor of the tracer it is possible to link some properties of the measurement nodes to the tracer message. The flow data will be shown in the Log popup after running the transaction.


Feb 2009 89

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 flag will enable 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

Further more there is another setting required. The input XML which will be sending should be linked with the container action.

After successfully configuration the connection settings you can start importing data.

Run the sample clicking on the Menu 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 was successfully when the Return Code is 0.

Time zone

The time zone information saves the time information of the imported date into Environmental Compliance accurately.

Set the time zone of the zone where the imported data will be used and read. It is important to set the right time zone because while reading the time information in Environmental


90 Feb 2009

Compliance Application the system converts the time information into the time zone of the logged in user. The time information is saved in the data base always in the UTC (Old GMT (Greenwich Mean Time)). Users in different time zones will see different time information in Environmental Compliance.

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 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.)

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.

It is recommended to import data with the same time zone that the server is running in.

It is recommended to use the following dates to import daily consumptions From Date: 2007-053T00:00:00.000+02:00 (Germany Daylights saving time) To Date: 2007-053T23:59:59.999+02:00 (Germany Daylights saving time)

For further information please refer to SAP Note: 1067441

Unicode

xMII supports Unicode data with the char-set UTF-8 encoding. All Environmental Compliance properties can be used Unicode characters for the import process to Environmental Compliance from xMII.

4.4.8.4 Knowledge Management Integration

Overview For simple document management requirements EC has a simple, built in document management 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. After installing the KM integration package for EC the user will be able to search for KM documents inside of EC and to link this documents to the EC objects.


Feb 2009 91

4.4.8.4.1 System Set Up

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 URL according the following pattern http://<host>:<port>/nwa/WSAdmin Indexmanagement Web Service

Search for the Proxy Definition “IndexManagementWSVi_Document” and navigate to Configuration > Logical Ports:

Set up the WS Endpoint URL:

http://<hostname>:<port>/IndexManagementWS/Config1?style=document

Navigate to Security and set up the authentication to access the Web Service (e.g. Authentication “BASIC”, Username/Password).

Repository Framework Web Service

Search for the Proxy Definition “RepositoryFrameworkWSVi_Document” and navigate to Configuration > Logical Ports:

Set up the WS Endpoint URL:

http://<hostname>:<port>/RepositoryFrameworkWS/Config1?style=document

Navigate to Security and set up the authentication to access the Web Service (e.g. Authentication “BASIC”, Username/Password).

4.4.8.4.2 Set up of User Exit (SAP Knowledge Management (KM))

Log in to the portal (http://<host:port>/irj) with a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin”

Navigate to Plant Compliance � Configuration � Basic Settings � User Exit.

Select the DMS Plugin and Click on the Easy Connect Button

Select the Activate Check box.

After that Set up the properties how described in the next section, after that save your changes:

As 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.

Please 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):

� path=<path1>;<path2>

e.g. 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):

� index=<index1>;<index>

Maximum number of retrieved documents per search:


92 Feb 2009

� maxcount=<maximum results> e.g. maxcount=300

Access timeout of web service requests (Optional / Default Value is 60000):

� [timeout=<timeout in ms>] e.g. timeout=30000

Associations between User Defined Fields (UDFs) and related KM properties:

� udf_<UDF-Field>={namespace}propertyName e.g. udf_Name={http://sapportals.com/xmlns/cm}displayname udf_Description={http://sapportals.com/xmlns/cm}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: System Administration >…> Property Metadata > Namespaces

If you defined custom properties a possible association would be:

� e.g. udf_MyCustomProp={http://sapportals.com/xmlns/cm/custom}MyCustomProp

To enable the fulltext-search you have to define the following association:

� udf_<UDF-Field>=kmfulltext

Example:

index=all

maxcount=300

udf_Fulltext=kmfulltext

udf_Date={http://sapportals.com/xmlns/cm}custom_date

udf_Name={http://sapportals.com/xmlns/cm}displayname

udf_Picklist={http://sapportals.com/xmlns/cm}custom_picklist

upload_path=/documents

4.4.8.4.3 Set up 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:

� Create a new UDF Area of type DMS-Search.

� Create and assign at least one element to the area. e.g. Label: Name / Type: Text e.g. Label: Description / Type: Text

4.4.8.4.4 Set up of full-text search:

� Select the UDF Area DMS-Search.

� Create and assign the following element: Label: Fulltext / Type: Text field

4.4.8.4.5 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.


Feb 2009 93

Link a KM document

1) Select the button Add from DMS at any document table in EC.

2) A search screen will pop up 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 filled search criteria are equal to the document properties. The User Defined Fields are compared to the KM properties as described in the following section:

� Text-Field: Compares equal if both values are exactly equal. Please, pay attention that this criterion is ignored when the content of the text field is empty.

� Integer-Field: Compares equal if both values are exactly equal. Please, pay attention that this criterion is ignored when the content of the text field is “0”.

� Boolean-Field: Compares equal if both values are set to true. Please, pay attention that the criterion is ignored when the checkbox is deselected.

� Date-/Time Field: Compares equal if both values contain the same date regardless of the timestamp. Please, pay attention that this criterion is ignored when the content of the date-time field is empty.

� Picklist-Field: Compares equal if both values contain the same picklist value. Please, pay attention 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 will be added to the link in EC.

4.4.8.5 Customer Development (User Exit) Several modules of SAP Environmental Compliance can be enhanced with multiple custom specific extensions. SAP Environmental Compliance provides several extension points where those user exits can be integrated into the product

Those extensions are developed by Customers based on predefined Interfaces and are delivered in separate Software Components (in own Java Name Space).

The customer development should be done in the SAP NWDI Landscape which supports the deployment on a set up system landscape (DEV � TEST � PROD). Therefore the NWDI provide settings to set up Version Management for Customer Software Components.

Conflict resolution is not necessary, due to the Interfaces of the User Exit remains stable. If the Interfaces of the User Exits will be changed, then SAP OSS Notes will describe the relevant versions and changes.

For further information about User Exits please refer to SAP_Environmental_Compliance_30_en_Functional_Documentation.

4.5 High Availability This chapter describes which components in your System landscape could failure.

Following Components should be monitors to engage a clear process run of EC 3.0

Components with single point of failure

Component Detailed Description


94 Feb 2009

ERP – EHS EHS Integration does not work

SAP Knowledge Management (KM)

Linked Documents can not be accessed and documents can not be linked

ADS SAP EC PDF generation does not work

ADS SAP EC Check List Task does not work

SMTP Email Notification does not work

SAP Web Dispatcher

EC Application does not work

To find out how to make the SAP Web Dispatcher a high availability solution refers to “Architecture of the SAP Web Dispatcher”. http://help.sap.com/saphelp_nwce10/helpdata/en/73/8c3c3d3a4b8c4ce10000000a114084/frameset.htm

4.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.

4.6.1 Transport and Change Management The EC Configuration supports a transport mechanism for transferring configuration data between different EC Systems (between Development and Test system)

The data will be transport via SAPTrans tool. How the Saptrans tool works is described in the chapter 3.3.5 and in the SAP OSS Note: 1010913 and 1063294

The EC application generates an XML files which defines Data base table and the Row which should be transport. At the end of the process EC generates this XML File which has to be used in the SAPTrans Tool. The Saptrans exports the data in one system and imports the data in a new System

Saptrans always overwrite data on the target data base system (if data exist in the used ID Range)

Define an Activity

The transport will be saved into an Activity.

Log in to the portal (http://<host:port>/irj) with an user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin

Navigate to the Maintenance View “My Transport Activities”. Plant Compliance � Maintenance � My Transport Activities.

In this view the current logged in user can create new Activities. The Status of the Activity is now open. This activity can now be used in the second step for transport data


Feb 2009 95

Transport Data

Following Configuration views supports the transport functionality

� Units and Dimensions

� User Defined Fields

� List of Values

� E-mail Templates

� Flexible Hierarchies

� Facility Types

� Parameters

� User Exit Configurations

� Object Based Permission Profiles

Based on an example the transport functionality will be described:

1. Create a new Activity in My Transport Activities

2. Go to the EC Configuration List of Values (LOV)

3. Search the LOV with identifier “SYS_ADMIN_USER”

4. Select the LOV

5. Click on the Transport Icon “Mark for Transport”

6. Select the new created Activity from Step 1

7. Go to EC Maintenance � My Transport Activities

8. Release your Activity

9. Go to EC Maintenance � Manage Transport Activities

10. Search your Release Activity

11. Now you can download the XML File

12. Copy the saptrans folder of the initial data on you local system rename your XML file to select.xml and replace the xml file in the saptrans folder

13. The further steps working with saptrans and generation an export command Please refer to the SAP Note 1063294

After transporting Data via SAPTrans the admin user has to reset the Buffers otherwise the new inserted data will not appear in the imported application � Log in to EC portal (http://<host:port>/irj) with an user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin” and Navigate to the Reset Buffer View � Plant Compliance � Tools � Reset Buffer

4.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. If you consider filing a development request, we recommend that you follow the


96 Feb 2009

procedure published on the SAP Service Marketplace under http://service.sap.com/rollin.

4.6.3 Release Implementation The Release CD Rom can be downloaded from SAP Service Marketplace (http://service.sap.com/swdc).

In SAP Software Distribution Center select the Download link and the link "Installations and Upgrades"

Select the link "Search for Installations and Upgrades" and enter the search term: “Environmental”

Every Release has an own SAP Note. For EC 3.0 all relevant Release Notes are described in the OSS Note 1277367.

4.6.4 Support Packages and Patch Implementation The latest EC Support Packages and Patches (Only deployable files) can be downloaded from SAP Service Marketplace (http://service.sap.com/swdc).

In SAP Software Distribution Center select the Download link and the link "Support Packages and Patches"

Select the link "Search for Support Packages and Patches" and enter the search term: “Environmental”.

Every Support Package and Patches has an own SAP Notes. All Support Packs and Patch Notes are listed in the Central Release SAP Note.

4.7 Troubleshooting

4.7.1 Imported data does not appear in EC

Problem

After importing data into EC via Saptrans the imported configuration data does not appear in the target system

Solution

After importing data via Saptrans the admin user has to reset the buffer.

For further information about Reset buffer please refer to the Tools description in SAP_Environmental_Compliance_30_en_Functional_Documentation


Feb 2009 97

4.7.2 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 shall call the Authorization Diagnostics in the Object Based Authorization. For further information about Object Based Authorization please refer to the SAP_Environmental_Compliance_30_en_Functional_Documentation.

4.7.3 Report Generation does not work

Problem

When you tries to generate a PDF report in the EC Reporting modules and you get an Error message from the System

Solution

You should check if the PDF generation work. Use the EC System Checks. For further information please refer to the Administration description in SAP_Environmental_Compliance_30_en_Functional_Documentation.

If the Report Generation System check fails please refer to the SAP Page which will provide further information: http://help.sap.com/saphelp_nwce10/helpdata/en/44/badbb34d65673be10000000a1553f6/frameset.htm

4.7.4 Email notification does not work

Problem

Limit checks failed or EC Tasks are overdue however no Email notification is send to the responsible users.

Solution

First you should check if the Email sending functionality works. Use the EC System Check. For further information please refer to the SAP_Environmental_Compliance_30_en_Functional_Documentation

This chapter will help to resolve the problem.

4.7.5 EC object is locked

Problem

You try to access to an EC Object and the system show an error that the EC Object is locked by yourself or another EC User.


98 Feb 2009

Sometimes it could happen that the current session in the Internet Explorer exceeded and the locking status remains.

Solution

Log in to the NWA (http://<host:port>/nwa/locks) with an administrator user

Following locking objects are set by Environmental Compliance:

Object Name Description

EC_MATERIAL Material in Master Data

EC_ACCOUNTING Emission Accounting

EC_TASK Task Templates in Compliance Management

EC_EQUATION Equations in Calculation Manager within the Emissions Management

EC_IO_CALCULATION Input Output Calculations in Calculation Manager within the Emissions Management

EC_CONSUMPTION_BASED_CALC Consumption Based Calculations in Calculation Manager within the Emissions Management

EC_FACILITY Facility in Master Data

EC_FACILITY_COMPLIANCE Facility in Facility Compliance

EC_FACILITY_TYPE Facility Type configuration in Facility Compliance

EC_EXCEPTION EC Exceptions Compliance Management

EC_AUTHORITY Authority in Compliance Management

EC_PERMIT Permit and Requirement Set in Compliance Management

EC_REQUIREMENT Requirement in Compliance Management

EC_LIMIT Limit checks in Compliance Management

EC_CITATION Citations in Compliance Management

EC_PROPERTY Properties Facility Type Configuration in Facility Compliance

EC_EMISSION_MANAGER Facility in Emission Manager

EC_COMPLIANCE_MANAGER Facility in Compliance Management

EC_BATCH_PROCESS_RECIEPE Batch Processes

EC_BATCH_PRODUCTION_RUN Batch Processes

EC_BATCH_PRODUCTION_SERIES Batch Processes

EC_Buffer Thread Background Job Change document

The Admin should only unlock EC objects which are described in the upper table.

4.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


Feb 2009 99

Solution

When the connection between client and server is broken the web service process can be started one more time. The data which is already imported will be overwritten (Dependent of the Integration settings) and the other data will be imported into EC.

4.7.7 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 work. Use the EC System Checks. For further information please refer to the Administration description in SAP_Environmental_Compliance_30_en_Functional_Documentation.

If the IGS System check fails please refer to the SAP Page which will provide further information: http://help.sap.com/saphelp_nwce10/helpdata/en/45/f15ed044c741b2e10000000a11466f/frameset.htm

4.7.8 Java Scheduler Jobs do not work

Problem

In the JAVA Scheduler some Jobs could remain in the Status “Starting”.

Solution

Check if the Config Tool Settings from chapter “3.4.8 Set up Deployable Application properties” is set up correctly.

If the settings are correct, then you need to check if the EC scheduler services are running.

Go to the NWA (http://<system>:<port>/nwa/start-stop) 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. When they are not started please start them manually.

After that the EC 3.0 Scheduled Jobs should be completed.


100 Feb 2009

4.8 Application Security To reduce the access to an application, different security mechanisms are needed. EC has these mechanisms to ensure access for selected users only

Purpose

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).

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 further information about NetWeaver Security Guides for the Operating System and Database Platforms for CE please refer to SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/45/a22c6471cc2735e10000000a155369/frameset.htm

4.8.1 Three Tier Authentication Concept

Purpose

Rights and permissions are needed to limit access to an application. The application EC 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 will be executed in every module separately. The application EC is divided into three different authentication types.

� EC User Management Engine (UME) actions � Enterprise Portal roles � EC Object Based Authorizations (OBP)

The next picture shows the interrelationship between the different permission types:


Feb 2009 101

Every EC user needs a Portal Role permission. The portal role has a link to the UME actions for access to the different EC Views and EC Configuration. Every portal role has its own UME Group which should be assigned to the EC Users. Further more the detailed Object Based permissions are assigned also the UME Groups. EC is delivered with 14 different User Groups which are predefined for different EC Work processes.

4.8.1.1 EC User Management Engine (UME) Actions

The EC application is delivered with a lot of Permission Actions which defines the access to the different EC modules.

We differ between Access Permissions for EC Modules and Menu Permissions for EC Administration, EC Maintenance, EC Configuration and EC Tools Application.

The Access Actions enables to access to the EC Module, however there are further Object Based Authorizations needed to have further permissions in the Module. The Other permissions (Not Access) have full permissions for the affected Configuration Objects.

An overview about all EC Action you can find in the UME User administration view:

!!!! Action

Log in to the user administration (http://<host>:<port>/useradmin) 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

In the initial status these Actions are assigned to the 14 delivered EC Portal Roles. Of course this actions can be used in self defined UME roles or EP Roles.

4.8.1.2 EC User Management Engine (UME) Groups

The EC application is delivered with 14 UME User Groups. These Groups should be assigned

to the EC End-users

An overview about all EC User Groups you can find in the UME User administration view:

!!!! Action

Log in to the user administration (http://<host>:<port>/useradmin) 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

4.8.1.3 Enterprise Portal (EP) 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 Activities

Corporate Program Manager KPIs for Company and EC Dashboard

Compliance Manager KPIs for Site and Dashboard


102 Feb 2009

EHS Manager View KPIs for Site, EC Dashboard, EC Compliance Management (Compliance, Permit, Task, Reporting, Exception)

Compliance Analyst View KPIs for Site, EC Dashboard, EC Compliance Management, EC Master Data (Facilities, Materials)

Environmental Analyst View KPIs for Site, EC Dashboard, EC Compliance Management, EC Emissions Management, EC Master Data

Site Manager View KPIs for Site, EC Dashboard

Site Technician EC Dashboard

Environmental Compliance Admin Access to the main Configuration, Administration, Maintenance and Tools menu

Facility Compliance Operator Special EC User, refer to the Functional Guide

Facility Compliance Analyst Special EC User, refer to the Functional Guide

Facility Compliance Responsible Special EC User, refer to the Functional Guide

Energy Manager Special EC User, refer to the Functional Guide

Read All Role with all EC Modules except the configuration

The delivered portal permissions contain the EC UME permissions. An EC user should be assigned to an EC portal role, and the user has automatically the described UME permissions.

Further information about roles please refer to the EC SAP_Environmental_Compliance_30_en_Functional_Documentation

4.8.1.4 EC Object Based Authorizations Object Based Authorizations (OBP) provides a fine-granular authorization and access control concept that is based on the different Business Objects (BO) of Environmental Compliance.

Customers can define authorizations for BOs, which fulfill specific criteria. These authorizations are grantable to a specific user, a group or a role. For example change permission for all Facilities, which have the classifier “Stuttgart” assigned can be granted to the users of the group “Data Entry Users Stuttgart”.

Further information about Object Based Authorizations please refer to the EC SAP_Environmental_Compliance_30_en_Functional_Documentation

4.9 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 4.9 Remote Support Setup

• Component hierarchy relevant for this application: XAP-EM, See chapter 4.10 Problem Message Handover


Feb 2009 103

4.10 Remote Support Setup The 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 OSS Message your system landscape. Therefore the EC SAP support team needs a HTTP Connection…

For further information please refer to the following SAP Note:

SAP Router Configuration for OSS Access

PC Anywhere

HTTP Access

30289

100740

592085

4.10.1 Remote debugging This picture shows how the Remote Debugging works in SAP NetWeaver landscape

The graphic above shows the necessary steps for enabling and working with remote debugging.

1. The customer configures the java debug service on the SAP service marketplace (he creates the connection data).

2. The customer switches on the debug mode on his java engine.

3. The connection data is replicated to the CSS system.

4. The developer who wants to debug remotely calls the transaction STFK and downloads the connection data which is stored in file '..sapdebugdata_v2.txt' on his or her file system


104 Feb 2009

5. Also with the help of the STFK the developer opens the connection. Prerequisite at this point of time is that the customer has opened his connection in the SAP service marketplace.

6. If the connection is open the developer can use the ping wizard of the IDE to see whether it works.

7. 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 been debugged.

8. The developer synchronizes the sources into the debug master project. If available he will be asked if he wants to download them from the debug source server or from the customer directly. After the sources have been retrieved, the debugging session can start.

For further information please refer to the SAP Help. http://help.sap.com/saphelp_nwce10/helpdata/en/46/c2a1e4e4cc0e5ce10000000a1553f7/frameset.htm or Refer to the SAP Note 545519

4.11 Problem Message Handover The SAP Component for sending problem messages is finding Errors is XAP-EM.

When you set up a message please report also following information which are necessary to reproduce the error.

• The Support Package and Patch of the EC Version where the problem happens

• The OS of the Web application server, and the version of the Web application server.

• The Target Data base.

4.12 BI / BW Content

4.12.1 Introduction This chapter gives an overview of the Business Warehouse content of the SAP Environmental compliance product and how the Business Warehouse component works together with the SAP Environmental Compliance application. This document describes all relevant facts concerning the business warehouse component such as:

a. The data transfer process between the SAP EC application and the Business Warehouse. The responsible component is called extraction layer or extraction framework

b. The design and the usage of the Business Warehouse content

c. Setup and configuration of the BW content

The different items will be discussed in the next chapters and subchapters. The document refers to the SAP Business Warehouse release 3.5.

4.12.1.1 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. Further more this layer


Feb 2009 105

provides functionalities to transfer the database base into the Business Warehouse. For more details about the extraction layer functionality please refers to chapter 4.12.2 Extraction Layer of SAP Environmental compliance.

Have a look at the following drawing which gives a graphical review of the technical composition of SAP Environmental Compliance and the interaction between the components application, database and Business Warehouse:

Please not 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 reporting possibility of SAP Environmental compliance data.

4.12.1.2 SAP EC BW content The Business Warehouse content of SAP Environment Compliance consists of three BW transports:

1. Namespace transport The TechniData specific Business Warehouse namespace. The namespace is a requisite for the installation of the Business content.

2. Packages The BW Packages or development classes, all Business content objects are assigned to certain packages.

3. SAP Environmental Compliance BW content. This transport contains all BW objects which build the business content of the product.

SAP EC (application)

Extraction Layer

Database

SAP EC BW


106 Feb 2009

For details about the installation of the business content please refer to chapter 3.4.9 BI Installation Content Guide

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:

d. InfoAreas and components

e. InfoObjects and their InfoObject catalogues

f. InfoSources

g. InfoCubes and ODS

h. Process Chains

i. InfoSets and MultiProviders

Please note that the business content does not contain any queries for BW reporting.

4.12.2 Extraction Layer of SAP Environmental compliance The extraction layer is a java based framework which uses JDBC in order 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.

4.12.2.1 System settings This chapter describes the different steps to establish 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. In order to establish a connection between the application and the Business Warehouse the following steps have to be carried out:

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 EC side.

Log into the NWA (http://<host>:<port>/nwa/destinations) as SAP NetWeaver

Admin and Navigate to the Destinations:

In this View you have to set up the BW RFC connection to the ERP System.

a. Set up connection. Enter the ERP System name as destination (Example “BW”) Set up the destination details. See SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/07/0d27932264284b883dab13ce1008a6/frameset.htm After finishing the destination setup you can test the connection pinging the ERP destination system.

b. Set up a second connection to ERP. Enter the ERP System name plus PROVIDER as destination name. (Example “BW PROVIDER”) Enter the same destination setup like step a). Enter the same destination setup properties like step a).


Feb 2009 107

After finishing the Destination setup the next step is to set up the JCO RFC Provider

Navigate in NWA to Configuration Management � Infrastructure � JCO RFC Provider

In this view create a JCO RFC Destination

Enter as Program ID “XEM”

Enter in the next Step the RFC Destination Name like the step 2 destination "ERP Name + Provider" (Example: “BW PROVIDER”)

For further information please refer to SAP Help: http://help.sap.com/saphelp_nwce10/helpdata/en/44/3bd73865524903e10000000a1553f7/frameset.htm

� After you set up successfully the JCO RFC Destination, you can start the server in this view.

On EC application Side you have to assign the different Modules to the Destinations.

Log in to EC portal (http://<host:port>/irj) with a user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin”.

Navigate to EC Plant Compliance --> Configuration --> Integration --> RFC Configuration

Now you assign the “BW System JCo Destination” Reference to the new created "Destination in the Step a)".

Next it is necessary to activate the RFC connection between the application and the Business Warehouse. Therefore we have to configure the BW Property “bw.extractor.progid” (EC Plant Compliance � Configuration � Integration � BW Properties) in order to link the application and the Business Warehouse by using the same program identifier.

In the SAP BW the configuration of the program id is done within the source system maintenance, transaction SM59 � TCP/IP connections � XEM.

4.12.2.2 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:

c. data extraction from the database

d. data conversion of database data into BW compliant data structures

e. BW request processing. A BW request is launch by the execution of an InfoPackage. This request will be analyzed and processed.

f. 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) it is possible to 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.


108 Feb 2009

There are several extractor classes which are responsible for the data extraction of these InfoSources. The registry stores the InfoSources and their corresponding extractor classes, e.g. the facility extractor class is responsible for the data extraction of facility master data and facility text data.

4.12.2.3 Extension of the extraction framework It is possible to register custom Java extractors within the extractor framework. A custom extractor needs to be registered to the extraction framework so that the extractor can be used for the data extraction into the BW. The extractor must perform the basic functionalities of an extractor. Please refer to the chapter 4.12.2.2 Basic functionality for more details. The registration of custom extractors is done through the deployment of a software component (SC) which contains the custom extractor (s). After finishing the deployment the SC is started. During the start-up of the SC the registration routine is executed which registers the custom extractor (s) at the extractor registry. After a (re) start of the extraction server the custom extractors are available and ready to extract data from the application into the Business Warehouse.

The software component which is deployed onto the web application server (SAP Netweaver CE 7.1) consists of the following items:

g. an EJB module

o Which contains the custom java extractor classes (1-n) possible

o Contains an Startup Initializer which performs the registration of the custom java extractors within the java extraction framework registry

h. An enterprise application

o Contains the EJB module

o To deploy the custom extractor onto the SAP Netweaver CE

Due to the fact that the development of custom extractors requires deep knowledge of the database table structures and the persistency layer it is nearly impossible for customers to develop their own extractors. The development of custom extractors should be done by TechniData in terms of a project solution. The development will be driven according to the business requirements of the customers.

A custom extractor can extract all database data, it can perform data operations on the data and it transforms the data into a BW compliant structure. Finally the extractor transfers the data into the BW.

4.12.3 Environmental compliance BI InfoProviders This chapter describes the SAP Environmental Compliance Business Warehouse content from a process view. It shows all InfoProviders such as InfoCubes and ODS as well as master data bearing InfoObjects and InfoObjects with hierarchies. Further more the Business Warehouse data flow of these objects will be explained in order to get an overview of the functionality of the business content. The description of the process chains will finalize the explanations.


Feb 2009 109

4.12.3.1 Master data bearing InfoObjects The business content of SAP Environmental Compliance provides several master data InfoObjects. Please have a look at the following tables to get an overview of the different InfoObjects, their usage and their properties.

Facility master data

InfoObject /TDAG/FACILITY

Usage 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.

Attributes 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

Properties Time dependant

Hierarchies and texts

Geo coding enabled

Export data source

Data flow Full load

Database table EM_ESOURCE

Beside the facility master data InfoObject /TDAG/Facility there are three more InfoObjects which also store data which refers to the facility: the InfoObject /TDAG/FACHN stores the hierarchy attributes, the InfoObject /TDAG/FACIC stores the facility identifiers and classifiers and the InfoObject /TDAG/FACUDF can store the user defined field information of facilities. All facility InfoObjects are identified by the same key value, the facility id, therefore the different master data records can be easily linked together. In the following these InfoObjects are described:

InfoObject /TDAG/FACHN

Usage This InfoObject stores the hierarchy attributes of the facilities.

Attributes Identifier, Geo Coding Country and Geo Coding Region


Data flow Full load

Database table EM_ESOURCE

Figure 1 - Facility Hierarchy Attributes InfoObject

InfoObject /TDAG/FACIC

Usage This InfoObject stores identifiers and classifiers of the facility. Deals as a sample for storing identifiers and classifiers of the facility.

Within the Facility Builder you can assign identifier and classifiers. The maintenance of the identifiers and classifiers is done under


110 Feb 2009

Configuration � List of Values

Attributes Facility identifier 1 – 7, identifier type 1 – 7, classifier 1-7, classifier type 1 – 7.


Sample

Data flow Full load

Database table EM_ES_CLASSIFICAT

EM_ES_IDENTIFICAT

Remarks Please consider the documentation “Extraction of configurable LOV items” for the correct usage of facility identifiers and classifiers.

Figure 2 - Facility identifier and classifier InfoObject

InfoObject /TDAG/FACUDF

Usage This InfoObject can store facility UDF information. It deals as a sample for the storage of facility UDF data. The UDF data fields have to be configured under Configuration � User defined Fields. After a successful configuration the UDF fields can be accessed within the facility builder.

Attributes Area identifier


Template

Data flow Full load

Database table TD_UDF*

Remarks Please consider the documentation “User Defined Fields in BW” for the correct usage of UDF in the BW.

Figure 3 - Facility UDF InfoObject

Task master data

InfoObject /TDAG/TASK

Usage 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.

Attributes Task name, task category, task sub category, priority, status, due date, end date, task status in percent, time status, task template, BW record status


Texts


Feb 2009 111

Data flow Delta load

Database table EM_TSK_INSTANCE

Remarks Delta loading of master data

Figure 4 - Task master data InfoObject

InfoObject /TDAG/TASKUDF

Usage This InfoObject stores UDF information of tasks. The InfoObject deals as a sample for new UDF task InfoObjects.

The UDF data fields have to be configured under Configuration � User defined Fields. After a successful configuration the UDF fields can be accessed within the maintenance of a task.

Attributes Area identifier.

Properties Template



Remarks Please consider the document User Defined Fields in BW for further details.

Figure 5 - Task UDF InfoObject

Material master data

InfoObject /TDAG/MATERIAL

Usage 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.

Attributes Material type, CAS number, material number, material parameter 1 – 2, R3 Reference material, BW data record status

Properties Texts

Data flow Full load

Database table EM_MATERIAL

Figure 6 - Material master data InfoObject

InfoObject /TDAG/MATIC

Usage This InfoObject stores material identifier and classifiers. The assignment of material identifiers and classifiers as well as material groups is done within the material manager of the application. The maintenance of identifiers, classifiers or groups is done under EC Configuration � List of Values.

Attributes Material identifier and identifier type 1 – 7, classifier and classifier type 1


112 Feb 2009

– 7

Properties Sample

Data flow Full

Database table EM_MAT_IDENT

EM_MAT_CLASS

Remarks Please consider the document Configurable LOV items in the BW for further details.

Figure 7 - Material identifier/classifier InfoObject

Exceptions

InfoObject /TDAG/EXCEPT

Usage This InfoObject stores the exception master data. Access the Exception Log of the application in order to maintain or create exceptions. The information from there is transferred to the BW.

Attributes Type, assessment, assignee 1- 5, state, report date and time, initiator, date from, date to, time from , time to, exception cause, correction action, notes

Properties Texts


Database table EM_EXCEPTION

Remarks Delta load of master data

Figure 8 - Exception master data InfoObject

InfoObject /TDAG/EXCPTUDF

Usage This InfoObject stores UDF information of exceptions. The InfoObject deals as a sample for new UDF exception InfoObjects.

The UDF data fields have to be configured under EC Configuration � User defined Fields. After a successful configuration the UDF fields can be accessed within the maintenance of an exception.

Attributes Area identifier.

Properties Sample



Remarks Please consider the document User Defined Fields in BW for further details.

Figure 9 - Exception UDF InfoObject


Feb 2009 113

4.12.3.2 InfoObjects with hierarchies Only the InfoObject /TDAG/FACILITY does have hierarchies. For the correct usage and customization of facility hierarchies in the BW please refer to the hierarchies in the BW guide which explains in detail all necessary information.

First the hierarchies have to be configured under EC Configuration � Flex hierarchies. In addition the user also has to maintain the BW configuration of these hierarchies. After the successful hierarchy configuration the hierarchies have to be assigned to the corresponding facilities within the facility builder. Afterwards the hierarchy can be extracted into the BW.

4.12.3.3 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 are emissions data, consumptions data for example. Through the characterization of InfoProviders into functional areas the user gets an exact review 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 it is possible to 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 historical true.

Have a look at the following figure which shows the dataflow of the Consumptions InfoCube in the Business Warehouse.


114 Feb 2009

Figure 10 - Dataflow at InfoCube Consumptions

Further more the InfoProviders cannot be freely extended with new InfoObjects due to the fact that the extraction layer is only able to handle the transfer structure of the existing InfoSources. For further information about the customizing of the extraction layer please refer to chapter 0.

Nevertheless the BW user has some options regarding the adaptation of the InfoProviders. He can add UDF InfoObjects to all InfoCubes which contain their related parent InfoObject, e.g. the Task InfoCube stores the InfoObject /TDAG/TASK and because of that it is possible to add UDF TASK InfoObjects to this InfoCube. The same principle exists for the Facility and the Exception UDF InfoObjects.

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 we can say that the smallest time frame for the reporting refers to daily values.

Update rules

InfoCube

InfoSource

PSA

xEM Source System

Datasource


Feb 2009 115

Emission data

The following Tables list all InfoProviders which store emissions data.

InfoProvider /TDAG/EM_C01 – Emissions

Usage Stores all emissions data despite the emissions data which refers to facilities that are assigned to a scenario. Emissions data can be maintained within the emissions section of the Facilitybuilder, there 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. Emission data always refers to a facility.

Master data InfoObjects

/TDAG/MATERIAL – The emission material

/TDAG/MATIC – Material identifier and classifier

/TDAG/FACILITY – The facility which emits the material

/TDAG/FACIC – Facility identifier and classifier

/TDAG/FACUDF – Facility UDF data (sample)

/TDAG/FACHN – Facility hierarchy attributes

Key figures /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.)

Data flow Standard data flow over ODS, delta data loading

ODS key definitions

Emissions value id

Expandable Custom UDF InfoObjects and Identifier / Classifier InfoObjects can be added.

Remarks Only Emissions data of facilities which are not assigned to a scenario are stored in this InfoCube!

Database EM_EMISSION_RES

EM_ESOURCE

Figure 11 - Emissions InfoCube

InfoProvider /TDAG/EM_C01A – Emissions Scenarios

Usage Stores all emissions scenarios data despite the emissions data which refers to facilities that are not assigned to a scenario.




/TDAG/FACILITY – The facility which emits the material ()


116 Feb 2009










ODS key definitions

Emissions value id


Remarks Only emissions data of facilities which are assigned to a scenario are stored in this InfoCube!


EM_ESOURCE

Figure 12 - Emissions Scenario InfoCube

InfoProvider /TDAG/EM_C01B – Emissions by material classifiers

Usage 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 classifiers of a material. This has also impacts on the key definitions of the ODS. For further details please refer to the document “Configurable LOV items”.














ODS key definitions

Emissions value id

Material classifier type


Feb 2009 117

Material classifier


Remarks Only emissions data of facilities which are not assigned to a scenario are stored in this InfoCube!

Due to the fact that 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 emission records. Please have a look at the document “Configurable LOV items” there you can find a screenshot of a sample query.


EM_ESOURCE

Figure 13 - Emissions by material classifiers

InfoProvider /TDAG/EM_C01C – Emissions by material groups

Usage 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 please refer to the document “Configurable LOV items”.














ODS key definitions

Emissions value id Material group


Remarks Only emissions data of facilities which are not assigned to a scenario are stored in this InfoCube!

Due to the fact that 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. Please have a look at the document “Configurable LOV items” there you can find a screenshot of a sample query


118 Feb 2009

topic.


EM_ESOURCE

Figure 14 - Emissions by material groups

Consumption data

InfoProvider /TDAG/EM_C02 – Consumptions

Usage Stores all consumptions 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 Facilitybuilder, 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






Key figures /TDAG/CONVALUE – Consumptions value


/TDAG/EQS_CONV – Equity Share consumptions value

/TDAG/CPAR1 – Consumptions parameter value 1



ODS key definitions

Consumptions value id


Remarks Only Consumptions data of facilities which are not assigned to a scenario are stored in this InfoCube!

Database EM_ES_DATA

EM_ESOURCE

Figure 15 - Consumptions InfoCube

InfoProvider /TDAG/EM_C02A – Consumptions Scenario

Usage Stores all consumptions scenario data despite the consumptions data which refers to facilities that are not assigned to a scenario.


Feb 2009 119














ODS key definitions



Remarks Only Consumptions data of facilities which are assigned to a scenario are stored in this InfoCube!

Database EM_ES_DATA

EM_ESOURCE

Figure 16 - Consumptions scenarios InfoCube

InfoProvider /TDAG/EM_C02B – Consumptions by material classifiers

Usage 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 please refer to the document “Configurable LOV items”.














120 Feb 2009


ODS key definitions



Material classifier


Remarks Only Consumptions data of facilities which are not assigned to a scenario are stored in this InfoCube!

Due to the fact that 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. Please have a look at the document “Configurable LOV items” there you can find a screenshot of a sample query.

Database EM_ES_DATA

EM_ESOURCE

Figure 17 - Consumptions by material classifiers

InfoProvider /TDAG/EM_C02C – Consumptions by material groups

Usage 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 groups of a material. This has also impacts on the key definitions of the ODS. For further details please refer to the document “Configurable LOV items”.














ODS key definitions


Material group


Remarks Only Consumptions data of facilities which are not assigned to a scenario


Feb 2009 121

are stored in this InfoCube!

Due to the fact that 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. Please have a look at the document “Configurable LOV items” there you can find a screenshot of a sample query.

Database EM_ES_DATA

EM_ESOURCE

Figure 18 - Consumptions by material groups

Tasks

InfoProvider /TDAG/EM_C04 – Tasks

Usage Stores all tasks data. This InfoCube stores the task instances according to the ODS key definitions. For the reporting a task counter is available as key figure. Within the task manager 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)





Key figures /TDAG/TASKCNT – The task counter

/TDAG/REQCNT – The number of requirements


ODS key definitions

/TDAG/TASK

/TDAG/FACILITY

/TDAG/REQUIRE

/TDAG/TASKOWN

/TDAG/TASKRESP

Expandable Custom TASK and Facility UDF InfoObjects can be added.

Remarks Task instances are stored in the Task InfoCube.

Database EM_TSK_INSTANCE

Figure 19 - TASK InfoCube

Exceptions

InfoProvider /TDAG/EM_C06 – Exceptions

Usage Stores all exceptions data. This InfoCube stores the exceptions according


122 Feb 2009

to the ODS key definitions. For the 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)





Key figures /TDAG/EXCNT – The task counter

/TDAG/REQCNT – The number of requirements


ODS key definitions

/TDAG/EXCEPT

/TDAG/FACILITY

/TDAG/REQUIRE

Expandable Custom Exception and Facility UDF InfoObjects can be added.

Remarks Up to five exception assignees are stored in the BW.

Database EM_EXCEPTION

Figure 20 - Exception InfoCube

Measurements

InfoProvider /TDAG/EM_C05 – Measurements

Usage 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






Key figures /TDAG/MVALUE – Measurement value


ODS key definitions

Measurement value id

Expandable Custom Facility and material UDF InfoObjects and Identifier / Classifier InfoObjects can be added.

Remarks


Feb 2009 123

Database EM_ES_MEASURE

EM_ESOURCE

Figure 21 - Measurement InfoCube

InfoProvider /TDAG/EM_C05B – Measurements by material classifiers

Usage Stores all measurements data. Please note that the measurement 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 please refer to the document “Configurable LOV items”.










ODS key definitions



Material classifier value


Remarks Due to the fact that 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. Please have a look at the document “Configurable LOV items” there you can find a screenshot of a sample query.


EM_ESOURCE

Figure 22 - Measurements by material classifiers InfoCube

InfoProvider /TDAG/EM_C05C – Measurements by material groups

Usage Stores all measurements data. Please 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 please refer to the document “Configurable LOV items”.







124 Feb 2009





ODS key definitions



Material classifier value


Remarks Due to the fact that 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. Please have a look at the document “Configurable LOV items” there you can find a screenshot of a sample query.


EM_ESOURCE

Figure 23 - Measurements by material groups

MultiProvider for emissions and consumptions

There exist two MultiProviders for the comparison of emissions data and consumptions data. One for comparing the emission and consumptions values of facilities which are not assigned to a scenario and the other one for the comparison of emission and consumption data of facilities with scenarios only. Please 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 4.12.3.1 Master data bearing InfoObjects the facility master data and the material master data is spread over different InfoObjects. The facility master data is stored in the InfoObjects:

i. /TDAG/FACILITY

j. /TDAG/FACUDF ( + additional custom UDF InfoObjects)

k. /TDAG/FACHN

l. /TDAG/FACIC ( + additional custom InfoObjects)

and the material master data is stored in the InfoObjects:

m. /TDAG/MATERIAL

n. /TDAG/MATIC ( + additional custom InfoObjects)

The InfoSets combine the separated master data InfoObjects so that master data reporting is possible over the “complete” master data if required. Please note that InfoSets technically


Feb 2009 125

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:

o. 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

p. all master data will be loaded with the process chain “master data and hierarchies”

q. all texts are loaded with the process chain “EM Texts”

r. There a two Meta chains which 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.

Expandable parts of SAP EC and SAP EC BW content

It is possible to develop custom java based BW extractors which can transfer data from the database into the Business Warehouse. Further more there are some generic concepts regarding the extraction of xEM data into the Business Warehouse.

One of the concepts is the usage of User Defined Fields for Facility, Task or Exception data. The other one is the usage of Facility / Material identifier and classifiers as well as material groups. The two concepts will be explained in separate subchapters. When using these two concepts it is not necessary to implement custom java extractors. The concepts base on configuration information.

Another point is the interface for the deployment and usage of custom java extractors. Please refer to chapter 4.12.2.3 Extension of the extraction framework in order to get more information regarding the development of custom extractors.

User Defined Fields in BW

Please have a look at the documentation “User Defined Fields in the BW” to get all relevant information about how to use UDF together with the BW,

UDFs can be created for Facilities, Tasks and Exceptions. The user first has to configure the structure of the UDF; this means he has to specify the attributes and the name of the structure. Finally the user must assign the UDF structure to the appropriate Facility, Task or Exception type (or domain). The configuration is done under Configuration � User Defined Fields in the EC Application. Please keep in mind that you have to configure the BW counter parts of the attributes as well within the configuration dialog. In addition you also have to design the BW InfoObjects and InfoSource so that the data can be extracted into the Business Warehouse. For details please read the documentation “User Defined Fields in the BW”.


126 Feb 2009

Facility / Material identifier and classifier

Please have a look at the documentation “Configurable LOV items” for details about how to use identifier and classifiers together with the BW.

Under EC Plant Compliance � Configuration � List of Values within the application the user can configure the facility / material identifier and classifier. Here he also has to perform the BW configuration. Afterwards he can assign the facility identifiers and classifiers to any facility. The material identifiers and classifiers can be assigned to any material. If the BW configuration of the identifiers and classifiers is correct and the BW data targets have been successfully build the data will be transferred to the BW. All relevant facts concerning the usage of identifiers and classifiers together with the BW are available in the documentation.

5 Migration of SAP EC

Feb 2009 127

5 Migration of SAP EC This chapter describes the upgrade and migration steps of an existing SAP Environmental Compliance 2.0 System to SAP Environmental Compliance 3.0.

5.1 Introduction SAP Environmental Compliance 2.0 is released on basis of either Netweaver 2004 or Netweaver 7.0. The SAP Environmental Compliance 3.0 is based on SAPs new Netweaver Java Platform Netweaver 7.1 CE.

Since usually you have setup a landscape for Environmental Compliance that consist of a Development, a Test/QA and a Productive environment the migration steps described in this document has to be carried out for all these environments.

Generally, the development environment should be migrated first, followed by the QA environment and the finally the production server(s). We recommend testing your business functions on your QA environment before upgrading the productive server(s).

5.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. Please see the corresponding OSS-Note 1177820 for information on the upgrade to EC 2.0 SP13.

• Server Platforms

Server Platforms (Hardware/Operating System and Database platform) for the new EC 3.0 installations is compliant to Netweaver CE 7.1 SP7 and SAP Environmental Compliance requirements. Please refer to the Product Availability Matrix (PAM) on http://service.sap.com/PAM for a complete list of supported Operating systems and Database platforms for Netweaver 7.1 CE and SAP Environmental Compliance 3.0.

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 7.1 CE Platform, you can carry out the same Migration except that the installation of Netweaver CE 7.1 and EC 3.0 has to be done on a new server platform.

5.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 an on an Enterprise Portal System, the migration steps for these two parts are described separately.

Please note, that the migration steps for the SAP BI Content as well as for the Portal Content need only top be carried out if you already are using these 2 options in your existing EC installation.


128 Feb 2009

5.4 Migration of EC Installations The following steps need to be carried out in Order to migrate an EC 2.0 installation to SAP Environmental Compliance 3.0:

• Execute complete database backup (Optional but recommended)

Since the database content of your existing EC installation will be removed after the successful upgrade it is advisable to create a full database backup of the existing installation prior to the following upgrade steps.

• Shutdown existing Netweaver Instance

To ensure, that the system is not used (and therefore data is changed) during the export of the database content, all server instances of your EC installation should be stopped using the SAP Management Console or the corresponding command line tools.

• Export database contents

To export all content of the database tables that are part of EC please use the SAPTrans tool. The OSS Note 1010913 describes where and how to obtain the latest version of the SAPTrans tool.

In the next step you have to adapt the select.xml file in the Saptrans directory. This file defines the data base tables for the exporting process.

For a detailed description on how to execute the export of the complete EC 2.0 SP13 database content (EC20_SP13_to_EC30.zip from SAP Note 1297451), please refer to OSS Note 1297451. After completion of the export, SAPTrans will have created a file called <name>.dat that contains the complete data.

Depending on the amount of data, exporting the data can take an extended period. As a recommendation, you can run this export over night.

• Install new Netweaver CE 7.1 SP7 Instance

Since this migration assumes, that the existing server platform does support the requirements for SAP Netweaver CE 7.1 you can normally install the new Netweaver platform using the normal installation procedure as described in the installation documentation. Please see the following article https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/e0c6b746-61de-2910-e2a0-9991016c17a7 for the corresponding installation documentation.

In case your existing Server Platform does not meet the requirements for Netweaver CE 7.1 and SAP Environmental Performance 3.0 you have to install Netweaver CE 7.1 on a new server platform. All subsequent steps have then to be carried out on the newly installed server.

• Deploy Environmental Compliance 3.0

After Netweaver CE 7.1 was successfully installed you can now start the deployment of SAP Environmental Compliance 3.0. The installation detailed process is described in the corresponding Installation documentation that can be found under the chapter


Feb 2009 129

3.3.3 Deploy the EC application. Please also refer to Note 1139005 for more information on the installation.

• Migrate users

In order 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 functionality available in the user management of Netweaver. Detailed information on this functionality can be found on help.sap.com:

For Netweaver 2004: http://help.sap.com/saphelp_nw04/helpdata/en/52/96f03eae11e16be10000000a114084/frameset.htm

For Netweaver 7.0 (2004s): http://help.sap.com/saphelp_nw04s/helpdata/en/52/96f03eae11e16be10000000a114084/frameset.htm

When using the import and export functionality usually the passwords of the users you are exporting are not written to the export file. To change this behavior you can set the following UME property. ume.admin.password.migration=true

Be aware that this setting has to be done on the Netweaver system where you export the users as well as on the Netweaver system, where the users are imported. Detailed information on how to set the UME property can be found on help.sap.com:

For Netweaver 2004:

http://help.sap.com/saphelp_nw04/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/frameset.htm

For Netweaver 7.0 (2004s): http://help.sap.com/saphelp_nw04s/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/frameset.htm

For Netweaver CE 7.1:

http://help.sap.com/saphelp_nwce10/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/frameset.htm

Please note, that this setting should be reverted back on the source as well as the target system to false after the migration of the users is finished.

• Import Database Contents

To import the data that has been previously exported from the EC 2.0 system you again will use the SAPTrans tool. The same notes as for the exports step apply here as well for detailed information

Depending on the amount of data, importing the data can take an extended period. As a recommendation, you can run this export over night.

• Import Delta Data Content

To import the delta data of EC 3.0 use the SAPTrans tool shipped in the folder <EC-DIR>\saptrans_EC_30_delta. The same notes as for the exports step

apply here as well for detailed information.

Please refer also to the Chapter 3.3.4 Upload the initial EC data.

Use in the Saptrans command call “delta.dat” instead of “init.dat”!


130 Feb 2009

• Run Data Migrations

In order 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. Please logon with an administrator user to Environmental Compliance, navigate to EC � Administration � Data Migrations and run the listed data migrations. This will ensure, that the data is converted to the new data base structures if required. Run all Data Migrations which are described in the SAP OSS Note 1139005

Action

Log in to the EC portal (http://<host:port>/irj) with an user which is assigned to the User Group “UMEGROUP_Environmental Compliance Admin”

Navigate to Plant Compliance � Administration � Data Migration

Run the EC 3.0 available data migrations

After every run check the Logs of the Data migration modules

• (Optional) Remove the now obsolete Netweaver Instance

Using the uninstall functionality of the SAPInst you can now remove the remaining Netweaver 2004 or Netweaver 7.0 installation that was used for EC 2.0. We recommend to do this after you tested your main functionalities on the newly migrated EC 3.0 installation.

If you installed on a new Server platform this steps becomes obsolete. The old server that hosted EC 2.0 can just be reused or decommissioned.

5.4.1 SAP BI Content Migration The most important point 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.

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 3.4.9.3 Procedure and Preparation. However it is strongly recommended to verify, that the steps described are successfully accomplished.

Another important point is to make sure that your BW system does have the appropriate service pack level installed. This level may be different for every version of EC BW content.

Before upgrading your EC BW Content make sure the transactional data of all InfoCubes and ODS objects are deleted.


Feb 2009 131

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 this case 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 xEM BW content

• Customized standard content

• Standard content

If you are updating your xEM BW content the most important option for the activation is the “MATCH or COPY(x)” option. This flag controls if the active BW content should be 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 xEM content (e.g. customizing of the facility hierarchy). If you uncheck this option the delivered version of the content will overwrite your changes made!

However, sometimes it might be necessary to uncheck this option. This is the case if the upgrade BW content that contains incompatible changes to previous versions e.g. InfoObjects have been removed out of /TDAG/FACLITY. Then in order to install the content to uncheck this option will overwrite the Standard content. This is necessary since deletions can not be transported, so the delivered version of the content needs to replace the active version of the content.

In general the BW activation system will suggest you which objects to update and which objects to overwrite. However this might not be appropriate in all cases.

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”.

If you have trouble installing the InfoPackages of the EC BW InfoSources try to restore the EC source system and to import the EC BW content transport again.

General remarks

This subchapter will list up key facts which should be considered for the xEM BW upgrade. The different remarks do no depend on a specific xEM service pack they are valid for all xEM BW releases. The different points are requisites which have to be performed manually before starting the content activation

• Hints for the 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


132 Feb 2009

InfoCubes or InfoObjects need to be reactivated. If not the merge process while activating new BW content will fail. This might happen during the installation of the InfoCubes showing an error message which refers to the earlier removed attributes.

• Custom InfoCubes which use standard EC BW Objects

For example, this means that beside the standard InfoCube there is also an additional “copy” of this InfoCube in our BW system. The copy also uses the same InfoSource for the data loading. If there are major changes as described in the previous point you will 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 will be problems with the data loading and it is even 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 it is recommended to manually activate the process chains again. Call transaction RSPC for activating the process chains. Note that there several Process chains which include other process chains. Standalone Process chains need to be activated first

• It is recommended to check if the complete BW upgrade was successful. Do all BW objects (InfoObjects, InfoCubes, update rules …) are active in the BW system? Do the InfoSources contain any generated Z… - InfoPackages? If this is the case please remove these InfoPackages manually.

• Please always read the installation remarks for the different releases carefully. If there is an update which skips several service packs e.g. from SP7 directly to SP9 it is absolutely necessary to take care of the installation remarks of the missed service packs. If the xEM BW content will be installed for the first time the installation remarks can be totally skipped beside the installation order.

Ignore errors

In some BW releases, errors might occur during the activation of the content for the InfoObjects /TDAG/IDENT and /TDAG/MIDENT telling that the data source is missing. These errors can be ignored, because for these InfoObjects no master data/ extraction will be 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 offered two possibilities on how to configure the BW extraction of these identifier and classifier, the first one was using the BW Properties and the second one uses the LOV dialog. Due to the fact that 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:

1. Removal of the facility classifiers and identifiers from the InfoObject /TDAG/FACIC

2. Removal of the material identifiers and classifiers from the InfoObject /TDAG/MATIC

3. Adaption of the InfoSources /TDAG/FACIC and /TDAG/MATIC

4. Removal of the navigational attributes in all EC InfoCubes

5. Deletion of the facility and material classifier and identifier InfoObjects (they have been marked as obsolete, the template InfoObjects will remain!)


Feb 2009 133

Have a look at the following remarks which will help you to adopt the EC 3.0 BI Content:

1. Please note that in case you do have customer specific enhancements in your EC BI content it is necessary to perform the changes manually.

2. If you do not have customer specific enhancements you can copy the BI content during the installation. Herewith the BI content will be replaced by the EC 3.0 BI Content

3. If you use the old facility / material identifier and classifier concept which uses the BW Properties configuration dialog you will have to implement the new concept which uses the LOV dialog. Please have a look at the SAP NOTE 1303115 for details.

If your current EC 2.0 SP13 BI Content is based on a SAP BI 6.20 or SAP BI 6.40 please 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. Please upgrade your BI system to BI 7.00 separately and then follow the instructions above to then upgrade the EC BI content to version 3.0

5.4.2 Enterprise Portal Content Migration SAP Environmental Compliance 2.0 did come 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 host the Enterprise Portal installation.

With SAP Environmental Compliance 3.0 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 picture shows the relationship between:

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


134 Feb 2009

For a detailed description of how to setup the connection between Netweaver CE 7.1 and Enterprise Portal on Netweaver 7.0 please see http://help.sap.com/saphelp_nwce10/helpdata/en/3e/878ce2eba747e2b065cfb5d4496483/frameset.htm

The result of exposing the SAP Environmental Compliance 3.0 PCD objects via the FPN technologies you will be able to 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.

SAP Environmental Compliance 2.0 and 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:

Option 1: Enterprise Portal is only used for Environmental Compliance

In this case, you can just migrate to EC 3.0 on Netweaver CE 7.1 as described in the Chapter “5.4 Migration of EC Installations”. With the deployment of EC 3.0 all new roles worksets, pages will be available and can be used to assign to users or to build own roles and worksets directly in the portal configuration of Netweaver CE 7.1.

Option 2: 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 Environmental Compliance 2.0 and 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 van be Migrated with either Scenario 1 or 2 as described in the Chapter “5.4 Migration of EC Installations”

6 Media List

Feb 2009 135

6 Media List The following table provides you with the information, on which data carrier you can find which software.

Installable Software Unit Media Name

SAP Environmental Compliance 3.0 The CD Material Number on SAP MP is: 51036467

Date post:	21-Oct-2015
Category:	Documents
Upload:	paruchuriin
View:	81 times
Download:	2 times