EHS100 - EN - Col17 SAP S4HANA EHS - Environment Management
EHS100 - EN - Col17 SAP S4HANA EHS - Environment Management
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 17
Course Duration: 2 Day(s)
Material Number: 50158620
SAP Copyrights, Trademarks and
Disclaimers
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see https://www.sap.com/corporate/en/legal/copyright.html for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or
inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any
reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to
various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
Demonstration
Procedure
Warning or Caution
Hint
Facilitated Discussion
65 Lesson: Getting familiar with the required Master Data for the
Environment Management process
TARGET AUDIENCE
This course is intended for the following audiences:
● Application Consultant
● Technology Consultant
● Business Analyst
● Business Process Architect
● Business Process Owner/Team Lead/Power User
● Solution Architect
● User
Lesson 1
Getting an overview of EHS 3
Lesson 2
Getting familiar with the Environment Management module 23
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Get an overview of EHS
EHS Overview
Overview
The sustainability, health and well-being related to the Corporate Sustainability Report
focuses and directs SAP's purpose. SAP seeks to help the world run more efficiently and
improve people's lives. This is the guiding principle to our business strategy - in particular, our
sustainability, health, and corporate social responsibility (CSR) portfolio. We believe social,
environmental, and economic activities and performance are interrelated - one impacts the
other. Our efforts focus on creating a sustainable future for SAP, our customers, and society.
For us, it is crucial to be a responsible business that intelligently strives to balance people, the
planet, and profit.
SAP acts as both an enabler and an exemplar to create positive economic, social, and
environmental impacts within planetary boundaries. As an enabler, SAP provides products
and services that meet the purpose and sustainability challenges and opportunities of our
customers. Furthermore, as an exemplar, SAP is leading by example in our own sustainable
business operations and practices.
For further information about SAP Purpose and Sustainability, use the following link:
https://www.sap.com/corporate/en/company/sustainability-csr.html
Design Philosophy
The design philosophy of SAP in the area of EHS means that it is to be able to connect these
groups of field operations, EHS practitioners and the corporate level.
SAP supports these groups within the customers organizations by providing tools and
processes that are highly integrated and the information is accessible in real time from
bottom to top and the reverse.
Solution Portfolio
The following figure outlines the solution portfolio.
This component helps you reduce the cost of risk management by supporting and automating
administrative tasks and processes, which increases the efficiency of the people responsible
for health and safety management as well as the reliability and cost-efficiency of
implementing controls.
The SAP EHS Management for SAP S/4HANA, occupational health application supports
general employee occupational healthcare in your enterprise, as well as the planning and
execution of special health surveillance protocols.
Special surveillance is required for those persons who may be exposed to certain influences
of a chemical, physical, or biological nature at their workplace, or who perform activities that
pose a health hazard. Health surveillance protocols can also include vaccinations or - as in the
United States - random drug tests.
Note:
The Occupational Health application is delivered as a Repeatable Customer
Solution (RCS) on S/4HANA.
Note:
The Audit Management application is a core component of the SAP S/4HANA
Enterprise license. It is a solution that can be used in the context of EHS processes
(for example, Safety Audits).
This includes two aspects, such as Permit to Work and Work Clearance Management.
The Permit to Work process is a critical and mandatory process for an asset-intensive
industry such as Oil and Gas, Utilities, Chemicals, and so forth. The process ensures the
safety of maintenance workers while performing tasks in a hazardous environment.
In the SAP S/4HANA world, this topic falls under Asset Management - Environment Health
and Safety. Work permit management functions are available in the Order, Order and
Notification List, and Job List applications.
With Incident Management, the value drivers fall into the following areas:
● A record of actual incident data that supports customers in achieving their main goal,
which is the reduction of incident rates.
● A proactive safety culture that closely tracks, analyzes, and learns from the (theoretically)
larger number of unsafe conditions and near misses that occur within an operation. It uses
that insight to act with the goal of reducing the chances of major incidents.
Environment management value drivers are to ensure the company's compliance with
environmental regulations as well as minimize emissions.
Companies need support to monitor, implement, and report changes and this is how
Management of Change drives customers to reduce any risk as a result of the required
changes.
Maintenance safety has priority over all other goals drives to better control of work and tools
that support the prevention of safety violations.
Incident Management
The objective of the EHS Incident Management solution is to provide you with a centralized
solution that tracks all types of incidents and drives a consistent process for incident entry,
investigation, and corrective actions.
Occupational Health
The objective of the EHS Occupational health solution is to provide you with a repository to
track the occupational health history of employees and drive a risk-based Occupational
Health process with integration back to central HR data.
Audit Management
The objective of Audit Management is to provide you with a solution for comprehensive
auditing activities across multiple business domains and processes.
Note:
The Audit Management application is a core component of the SAP S/4HANA
Enterprise license and is not included within SAP EHS.
Management of Change
The objective of the Management of Change solution is to provide you with a system to
execute and monitor change effectively within an organization so that it does not lead to
unknown or uncontrolled operational risk.
SAP Analytics Cloud and SAP Digital Boardroom provide (holistically) the bigger picture to
the corporate team. Whereas the EHS practitioner is more interested in more detailed
reporting capabilities and that is where the analytical path framework and smart business
dashboards can enable him/her in building in own dimensions the EHS analysis.
● It enables organizations to assess and reduce their carbon footprint, increase resource
productivity through circular processes, and run safer, sustainable business processes.
● It provides industry-specific insights that combine operational and financial data across
value chains, embedded in core business processes.
Figure 18: The Value Proposition of the SAP EHS Solution Suite
The modular but unified platform provided by SAP enables the EHS function within an
enterprise to be more aware, reduce risk, drive intelligent processes, and be at the forefront
of digital transformation instead of being left behind on a non-integrated island.
Figure 19: The Journey towards Business Value with SAP EHS
The next step is bringing the EHS processes into context. The context could be personnel
data, but also other enterprise information merging it with data that is already available. That
definitely enriches the value that EHS can bring to the company.
Additionally, the next step is not just looking at the EHS data and embedding it in the data
from other sources but having a deep dive into the processes. Having safety and
environmental aspects already being part of the ongoing day-to-day operations and
contributing to them is the key.
The next step is generating all this data and learning from it using the people on the ground as
a data source, using sensors as an information source to understand what is taking place - be
it understanding, doing simulations, modeling, predicting what can happen, and even going
into what-ifs and simulations.
Consequently, if any type of parameter in the safety operations change, how could that affect
the final performance?
The final target is creating this awareness of having an embedded application, which supports
the companies in learning continuously, getting automated insights, analyzing it, and feeding
it back into the processes.
Three themes are vital here:
● Establishing situational awareness for the workforce
● Having autonomy of the system, and of the processes, where possible
● Having EHS as a kind of ubiquitous dimension in all kinds of the operations, and the
processes, in the company
Stakeholder Benefits
The following figure outlines Corporate, EHS Practitioner, and Operations.
Process
● Handoffs and triggers that occur in your real-life business processes can be driven by the
system with no drops in communication or responsibility
● Process improvement is not only enabled by the system, but the system becomes a
source of new ideas and innovation
Data
● Provides context not matched by point solutions
● Data entry at all levels is quicker and less error-prone
● Processes run on a consistent source of truth
● EHS department does not need to deal with maintaining enterprise data
Reporting
● Consistent user-interfaces across multiple parts of SAP
● No need to maintain separate interfaces to other reporting tools
● Leverage central SAP ERP hierarchies as a source of truth like Plant, Functional Locations,
Cost Centers, and Org Structure to enable both roll-up and drill-down reporting in real-
time
● Consistent security paradigm between process data and reporting logic
● Gain additional insight with the ability to pull data from disparate processes within the SAP
landscape
Key Takeaways
SAP supports your EHS management system, so you can take a holistic approach to manage
safe operations. The end-to-end process provides support for key business processes that
create an effective safety culture by engaging all employees in safety and by providing risk-
based safety information. With the proactive approach of identifying and controlling risks, you
can reduce the likelihood and severity of incidents. Visibility into risks top floor to the shop
floor will reduce risk and enable continuous improvement in safety performance.
LESSON SUMMARY
You should now be able to:
● Get an overview of EHS
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Get an overview of the regulatory and permit compliance process
● Get an overview of the emission management process
High-level Process
The high-level process of environment management contains of three main steps - prepare,
execute, and manage. Each of the steps can be repeated as many times required depending
on the business use case.
Regulatory and compliance management has a very linear process. The environment
manager is being supported in the creation of a compliance requirement repository. The
compliance requirements can be either manually created or optionally they can be retrieved
as regulatory content from a third-party solution. The Environment Management solution
comes with a built-in option for integration to SAP content provider partner RegScan and
their RegScan One solution. Other integrations with content providers - for example, ENHESA
can be easily built.
After the compliance requirements have been created or imported from the third-party
solution of a content provider, they can be assigned to specific locations.
The environment manager can schedule compliance tasks directly from the compliance
requirements, trigger the execution of the tasks, monitor using the task calendar view and
perform the required analysis.
Division ABC and its subordinate locations Tank Area, Ethanol Storage Tank R2-BB4, Ethanol
Storage Tank R5-BB7, and Ethanol Storage Tank R6-BB9 will be used in the process
walkthrough as an example.
Regulatory Content
Applicable requirements based on regulations can be imported from external content
providers. Automatic updates to requirements are also made available when applicable
regulations change. To enable this action, you can use the app, Import Compliance
Requirement - Content Provider. The sources can be providers of regulatory content, such as
RegScan.
The interface for compliance content providers enables you do the following:
● View the content provider regulations with their corresponding Compliance Requirement
records
● Track pending versus completed updates
● Import multiple Compliance Requirements at once
● Access the content provider web page with each change explanation
● Choose whether to apply all the updates together or execute record by record
your industrial processes, the compliance requirement business object helps you organize
detailed information, which is critical to the environment.
The Manage Compliance Requirements - Regulations, Permits, Policies app supports the
environmental manager's ability to view a list of available compliance requirements in
environmental management. Various filters can be used to search for specific compliance
requirements and maintain their data.
Additionally, this app can be used to navigate to other apps where you can create new
compliance requirements of policy, regulation, or permit type. The created compliance
requirements can be used in further business processes, such as Emission Inventory or
Waste Management, to ensure environmental compliance.
In this example, the environmental manager creates a new permit to meet compliance
requirements. Other main activities can also accomplish the following:
● Adjust the settings in this app to optimize business processes
● Add as many permits as necessary to fulfill the requirements and manage compliance over
time
The environmental manager can add the required paragraphs to describe the specific
requirements related to the permit.
Environment managers can view the Task Calendar view of their team. Tasks can be filtered
based on Location, Status, and Type. Managers can reassign the tasks by dragging and
dropping it between individual users. Managers can change start/end date by stretching or
shrinking the tasks. Daily/Monthly views are available for the monitoring team using
Compliance Tasks.
Figure 46: Regulatory and Permit Compliance - Task Monitor and Analysis
Environmental Data Explorer app supports you in browsing through transactional data
records from all compliance scenario activities in the system. You can view the data through
the location hierarchy and filter it by applying various criteria such as data type, status, year,
month, and so on. You can export the data and use it for further reporting.
The Task Calendar app supports you in planning tasks for your team in a calendar view. You
can have an overview of existing task instances in a time schedule. Based on the overall
schedule, status, and workload of the team members you can adjust the plan by reassigning
and rescheduling the tasks between assignees.
Compliance Analysis app supports you in getting an overview of tasks grouped by status,
location, and compliance requirement type. You can add several analysis steps, one after
another, to filter and analyze compliance task execution. This helps you to gain further
insights, quickly identify pain points, and evaluate the data you need for information and
reporting purposes.
High-level Process
The high-level process of environment management contains of three main steps - prepare,
execute, and manage. Each of the steps can be repeated as many times required depending
on the business use case.
8. Reporting:
● Perform further deviation reporting
● Export records of collected, calculated, sampled, and aggregated data to plain
spreadsheets
● Export records of collected, calculated, or sampled data to pre-defined file-based reports
Power Plan Boston and its subordinate locations, Power Unit B1 and Power Unit B2, will be
used in the process walkthrough as an example.
These documents consist of conditions and requirements, and they are organized into a given
order (such as chapters, subchapters, parts, subparts, paragraphs) relevant for various
industries or businesses.
The environmental manager, on the SAP Fiori launchpad, opens the Manage Compliance
Requirements - Regulations, Permits, Policies app.
Depending on the requirement purpose, the environmental manager can create one of the
following:
● Regulation
● Permit
● Policy
The process walkthrough focuses on the creation of a compliance requirement type, Policy.
The environmental manager navigates to the Contents tab and maintains the following:
● Environment Limits
● Regulatory Lists
● Equations
The compliance requirement has been released and can be used to set company goals for
compliance of greenhouse gas emissions with applicable environmental limits.
The next step in the process is as follows: the environmental manager starts planning the
emissions by creating and setting up the activities in the required compliance scenarios.
Create Compliance Scenario for Power Unit B1 - Role: Environmental Manager 1/3
After the environmental manager has created and released the compliance requirement
of type, Policy, the environmental manager creates a compliance scenario for one of the
company's production units to set that unit as applicable for its requirements about
greenhouse emissions reporting.
Figure 71: Create Compliance Scenario for Power Unit B1 - Role: Environmental Manager 1/3
Create Compliance Scenario for Power Unit B1 - Role: Environmental Manager 2/3
The environmental manager opens the Manage Compliance Scenario app and chooses the
option to create a compliance scenario.
Figure 72: Create Compliance Scenario for Power Unit B1 - Role: Environmental Manager 2/3
Create Compliance Scenario for Power Unit B1 - Role: Environmental Manager 3/3
A compliance scenario has been created for one of the company's production units and can
be used to set that unit as applicable for compliance requirements about greenhouse
emissions reporting.
Figure 73: Create Compliance Scenario for Power Unit B1 - Role: Environmental Manager 3/3
In order to comply with the requirements, the user can setup the necessary activities - data
collections, calculations, sampling, and location-based aggregations.
Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager
1/6
The environmental manager sets up compliance activities within the created scenario, such
as data collections, samplings, and some calculations.
Figure 74: Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager 1/6
The planned activities help the environmental manager to ensure the compliance of the
company's production unit with the applicable requirements about greenhouse emissions.
The figure above provides a visual illustration of these activities.
Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager
2/6
The environmental manager navigates to the Compliance Scenario: Greenhouse Gas
Monitoring B1 (demo) at Power Unit B1 screen and adds a data collection definition.
Figure 75: Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager 2/6
Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager
3/6
The environmental manager adds a sampling compliance activity. A specific sampling method
has been created and released. Further on, it can be used in the sampling definition.
Figure 76: Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager 3/6
Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager
4/6
The environmental manager defines the calculations in the compliance scenario.
Figure 77: Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager 4/6
Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager
5/6
The environmental manager defines a location-based aggregation in the compliance scenario.
Figure 78: Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager 5/6
Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager
6/6
Compliance activities have been added to the scenario to help ensure the compliance of the
company's production unit with applicable requirements about greenhouse emissions.
Figure 79: Set Up Compliance Scenario Activities for Power Unit B1 - Role: Environmental Manager 6/6
Figure 80: Copy Compliance Scenario to Power Unit B2 - Role: Environmental Manager 1/2
The environmental manager performs the copy and adjusts the specific details for Power Unit
B2.
Figure 81: Copy Compliance Scenario to Power Unit B2 - Role: Environmental Manager 2/2
Create Compliance Scenario for Power Plant Boston - Role: Environmental Manager
A compliance scenario has to be created for Power Plant Boston to set up the applicability of
the plant to the compliance requirement about greenhouse emissions.
Figure 82: Create Compliance Scenario for Power Plant Boston - Role: Environmental Manager
Set Up Compliance Scenario Activities for Power Plant Boston - Role: Environmental
Manager 1/3
Compliance scenario activities, such as calculations and aggregations, have to be set up
for Power Plant Boston. These activities can be used to check emissions data from all power
plants in the company and verify that the set company targets can be met.
Figure 83: Set Up Compliance Scenario Activities for Power Plant Boston - Role: Environmental Manager 1/3
Set Up Compliance Scenario Activities for Power Plant Boston - Role: Environmental
Manager 2/3
The environmental manager adds a new calculation and defines the details such as required
expression and data source for the calculation variable.
Figure 84: Set Up Compliance Scenario Activities for Power Plant Boston - Role: Environmental Manager 2/3
Set Up Compliance Scenario Activities for Power Plant Boston - Role: Environmental
Manager 3/3
Compliance scenario activities, such as calculations and aggregations, have been set up
for Power Plant Boston. These activities can be used to check emissions data from all power
plants in the company and verify that the set company targets can be met.
Figure 85: Set Up Compliance Scenario Activities for Power Plant Boston - Role: Environmental Manager 3/3
Activate Compliance Scenarios for Power Plant Boston and Sublocations - Role:
Environmental Manager
The compliance scenarios for Power Plant Boston and its sublocations have been activated in
one go. The planned compliance activities in them can start and be monitored on a plant level.
Figure 86: Activate Compliance Scenarios for Power Plant Boston and Sublocations - Role: Environmental
Manager
The next step in the process is as follows: the environmental manager with the help of the
production operator or technician records the missing data.
Figure 88: Record Environmental Data for Power Unit B1 - Role: Environmental Manager
The environmental manager enters the final results in the compliance scenario under the
sampling overview.
Record Environmental Data for Power Unit B1 - Role: Production Operator - EHS Info
The production operator or technician maintains the missing data using the My Data
Collections app.
Figure 89: Record Environmental Data for Power Unit B1 - Role: Production Operator - EHS Info
Figure 90: Record Environmental Data for Power Unit B1 - Role: Environmental Manager
Following the same approach, the emissions data for Power Unit B2 can be entered in the
system to reflect monthly data collections and samplings, part of the company's operations.
The next step in the process is as follows: calculation and aggregation based on collected and
aggregated data as well on as the input from the regulatory lists assigned to the compliance
requirement.
For our example, the data will be aggregated into the scenario for the location Power Plant
Boston.
Figure 93: Monitor Data and Data Issues - Role: Environmental Manager
The next step in the process is as follows: the environmental manager starts monitoring the
data on a plant level and performs checks against company goals about compliance with
applicable environmental limits.
Monitor Environmental Data for Power Plant Boston - Role: Environmental Manager 1/3
Emissions data for Power Plant Boston has been monitored and checked against company
goals about compliance with applicable environmental limits. The environmental manager
opens the compliance scenario created for location Power Plant Boston and under the
defined calculation navigates to the Monitor Calculated Data app.
Figure 94: Monitor Environmental Data for Power Plant Boston - Role: Environmental Manager 1/3
Monitor Environmental Data for Power Plant Boston - Role: Environmental Manager 2/3
The environmental manager opens the compliance scenario created for the Power Plant
Boston location and under the defined location aggregation navigates to the Monitor Data
app.
Figure 95: Monitor Environmental Data for Power Plant Boston - Role: Environmental Manager 2/3
Monitor Environmental Data for Power Plant Boston - Role: Environmental Manager 3/3
The environmental manager identified that two of the amounts go above the upper
environmental limit. A deviation has to be created for each value above the limit.
Figure 96: Monitor Environmental Data for Power Plant Boston - Role: Environmental Manager 3/3
Figure 97: Record Deviation and Start Investigation - Role: Environmental Manager
The next step in the process is as follows: the environmental manager concludes that there
are deviations from the environmental limits and deviation records have to be created to
further investigate the causes.
Figure 98: Create a Deviation for Power Plant Boston - Role: Environmental Manager
Figure 99: A Deviation for Power Plant Boston - Role: Environmental Manager
Objective
● Reduce your environmental impact with comprehensive emissions management
Capabilities
● Manage emissions of greenhouse gas (GHG) as well as other air or water emissions to
fulfill legal requirements
● Calculate and aggregate emissions while fostering proactive data transparency and
monitoring
● Detect and communicate deviations, including investigations and tracking follow-up
activities
Benefit
● Reduce risk of environmental non-compliance and penalties
● Ensure license to operate
● Improved calculation accuracy and transparency
LESSON SUMMARY
You should now be able to:
● Get an overview of the regulatory and permit compliance process
● Get an overview of the emission management process
Lesson 1
Getting familiar with the required Master Data for the Environment Management process 65
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Specify location details
● Manage listed substances
● Manage chemical/physical properties
● Manage sampling method
● Update location details
● Create sampling method
● Create chemical/physical properties
The logistic and organizational master data displayed above is introduced in Environment
Management to support the process of compliance management.
In the following unit, you will get familiar with the usage of the location and location structure
and how essential they are for the emissions management process.
Location Definition
The emissions management process requires certain master data to be created. In
Environment Management, locations are used to define the emission sources, which will be
used later in the process of calculating the emissions. You can define master data, such as the
plant or company code, to which that location belongs. You can also specify the location's
address and geographic coordinates to identify its precise position. You can use the precise
position to visualize a location on a map that can be integrated into the system.
In this process, a location structure must be created in the system. Without a single location,
the process cannot be triggered.
To use the location in the emissions management process, the environmental manager needs
to maintain the following information about the location:
● Persons Responsible
● Environmental Details
The assignment of the Environmental Manager is required to enable the managing of all
compliance activities in the compliance scenario.
The assignment of the Production Operator or Environmental Technician is required to be
able to receive all notifications of data collection.
A location classifier is a textual object that is used to categorize locations and can be assigned
to compliance requirements to specify their applicability.
Depending on the use case, in Environment Management, the environmental manager can
either create their own classifiers or use the standard classifiers delivered as sample content
by SAP. The following business catalog SAP_EHS_BC_ENV_MNG_LOCCL_PC is assigned to
any of the business roles. When a location or a compliance requirement is classified by adding
a classifier to it, the system displays in a suggested value list all available classifiers that
match the entry.
If the location classifiers match with the compliance requirement classifiers, the system
displays a green sign indicating that the location has a compliance scenario for the defined
company goals and the type of operations running at the location.
The environmental manager adds a property to the location with the following input data
points:
● Property (selected from the list of existing ones)
● Value
● Unit
● Comment
The environmental manager can choose a data source type Location Data with a data source
the location property.
Listed Substances
Ability to Create Master Data
The environmental manager has been provided with the ability to create master data to
support the emissions management process. These master data objects are essential for
carrying out the process.
The logistic and organizational master data displayed above is introduced in Environment
Management to support the process of compliance management.
In the following unit, you will get familiar with the listed substances and their usage.
Listed Substances
The listed substance object represents a substance in the way that it is defined in a legal or
industry-specific regulation.
It can also be a virtual substance such as the carbon dioxide equivalent which is used in
regulations to relate and aggregate the different greenhouse gas emissions to a single
emissions value.
In environment management, the environmental manager can use listed substances to define
environmental data sets in the compliance scenario like data collection, calculation results,
aggregation, and sampling data. Listed substances can be used when the composition data of
a material (product) is required.
The object can be maintained in the Manage Listed Substances app.
The environmental manager can create new listed substances from the Manage Listed
Substances app. SAP delivers an extensive catalog of pre-build listed substances as part of
the standard product that can also be used.
The sequence number that can be specified controls the order of appearance of the provided
synonym or translation entry. The numbering order must be unique for each language.
Usage of Listed Substances
Listed Substances are widely used within the emissions management process. The
environmental manager using listed substances can create and manage the following:
● Regulatory lists
● Environmental limits
● Equations
● Data collections
● Sampling definitions
● Location-based aggregations
● Calculations
● Material data
Chemical/Physical Properties
Ability to Create Master Data
The environmental manager has been provided with the ability to create master data to
support the emissions management process. These master data objects are essential for
carrying out the process.
The logistic and organizational master data displayed in the figure above is introduced in
Environment Management to support the process of compliance management.
In the following unit, you will get familiar with the chemical/physical properties and their
usage.
Chemical/Physical Properties
For the purposes of environment management, additional chemical/physical properties that
are not directly related to specific chemicals can be created. These are chemical/physical
properties that can be properties of the equipment or environment where you wish to carry
out environmentally-related activities, such as data collections or calculations.
They are all user-specified measurable properties (for example, system temperature, tank
volume, or valve count of a production unit).
With the Manage Chemical/Physical Properties app, you can create new chemical/physical
properties.
Sampling Method
Ability to Create Master Data
The environmental manager has been provided with the ability to create master data to
support the emissions management process. These master data objects are essential for
carrying out the process.
The logistic and organizational master data displayed above is introduced in Environment
Management to support the process of compliance management.
In the following unit, you will get familiar with the sampling methods and their usage.
Sampling Method
To ensure consistent sampling activities, the environmental manager can prepare sampling
methods and distribute uniform instructions for them. Later, when compliance scenarios are
created, the sampling methods can be used as a basis for sampling activities at different
locations or pieces of equipment at your company.
With the Sampling Method app, the environmental manager can view and edit all existing
sampling methods in the environmental management system. The app can be used as a
starting point to create a new sampling method, which will be used in the sampling activities.
Initially when the Sampling Method app is opened, the environmental manager can view the
following:
● Recent - Under this tab, a list of the recently opened sampling methods is displayed.
● Search - Under this tab, a search for a sampling method can be performed by using the
name and/or the status.
To create a new sampling method, the environmental manager chooses the Create Sampling
Method option. The following details are required for the creation of a sampling method:
● Name
● Type of Sampling Method - the standard list provides the following types: Composition
(Predefined Analytes), Composition Analysis, Contaminants Analysis
● Sampled Subject - a sampled subject can be either a listed substance or a material. The
fields becomes visible only in the cases of samping method of a Composition (Predefined
Analytes) type.
LESSON SUMMARY
You should now be able to:
● Specify location details
● Manage listed substances
● Manage chemical/physical properties
● Manage sampling method
● Update location details
● Create sampling method
● Create chemical/physical properties
Lesson 1
Understanding the Compliance Requirements in the System 83
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create compliance requirements
● Create environmental limits
● Create regulatory lists
● Create equations
● Create compliance requirement
Compliance Requirements
Company Compliance Obligation and Responsible Role
To be environmentally compliant, a given location (or a piece of equipment) must adhere to
certain requirements. These may be parts of the documents (regulations or permits) issued
by global environmental agencies or policies that are issued by the companies.
These documents consist of conditions and requirements, and they are organized into a given
order (such as chapters, subchapters, parts, subparts, paragraphs) relevant for various
industries or businesses.
The creation of compliance requirements that represents the legal catalog is the main
responsibility of the environmental manager.
The compliance requirement is a main instrument for the environmental manager to ensure
and control the environmental compliance at a location or equipment in accordance with the
corresponding regulations, permits, or policies.
The set of requirements (conditions) has to be prepared with relevance to the industry for the
company.
The environment management component enables you to create an object known as
a Compliance Requirement and use the issued regulations, permits, or policies as a basis for
this object.
The compliance requirement facilitates the creation of industry-relevant excerpts of the
larger environmental documents.
The app provides the possibility to manage the existing requirements for the company as well
as the creation of new ones.
Using the Import Compliance Requirement - Spreadsheet app, the environmental manager
can browse data files from the file system and import these files into the environmental
management system. When a file for import is specified, the app loads it and examines the
compliance requirements stored in it. Then, the app runs data consistency checks and
outlines the potential import-related issues that may occur in the system. After the potential
issues are resolved, the app imports and stores the compliance requirements in the system.
The following details are valid for the three types of compliance requirements:
● ID - an optional field which allows the Environmental Manager to organize the compliance
requirements using a numeric system
● Compliance Requirement Name - title for the compliance requirement
● Issuing Organization - the name of the organization that issues the compliance
requirement
Note:
If you do not specify any country/region of validity, the compliance requirement is
considered valid in all countries/regions.
Under the Contents section, the structure of the paragraphs can be created.
The compliance requirement details section is filled in after the initial creation. The structure
of a paragraph always starts with a leading level, which is basically the compliance
requirement name.
The task of the environmental manager is to extract the compliance requirements from the
official legal source and maintain them in the system as paragraph(s). The Contents table
displays the structure of the paragraphs and a count of the environmental limits, regulatory
lists, equations, and tasks related to each paragraph.
As a next step in the process, the environmental manager can start building the contents for
the compliance requirement in the system as illustrated on the image above.
Basic Information
Each compliance requirement paragraph is created in the system with the following structure:
● Basic Information
● Documents
● Environment Limits
● Regulatory Lists
● Equations
● Tasks
Documents
Under the Documents tab, all documents that are relevant to the compliance requirement can
be attached.
This tab can be used as a central repository of regulatory documentation and can be used as
a reference in the emissions management process.
The compliance requirement Title 40: Protection of Environment; Mandatory Greenhouse Gas
Reporting by the United States Environmental Protection Agency (EPA) is one of the
examples.
The content delivery is in the form of values delivered into existing data structures like
regulatory list values from Regulatory Lists and Emissions Factors.
The topic will be covered in detail in Unit 9 of this course.
Environmental Limits
Define Environmental Limits
Environmental limits are used to define compliance checks on the environmental data
(collected, calculated, sampled, or aggregated) within your compliance requirement
paragraphs.
The Where Used list also enables you to navigate directly to the activities and scenarios that
use the limit. In addition, environmental limits can be deleted when it is ensured that they are
not used in any compliance scenario activities.
Note:
If the limits are used, they must be either unassigned from the corresponding
activities, or even deleted from the activities, before the limits can be deleted.
The example in the figure, Usage of Environmental Limits, illustrates the usage of the
environmental limit for a calculation activity defined in a compliance scenario.
Regulatory Lists
Define Regulatory Lists
Regulatory lists are used to define the values of a given chemical property within a list of
specified substances. A regulatory list contains reference information that can be extracted
from the environmental documents (regulations, permits, or policies).
The regulatory lists conform to the lifecycle of the compliance requirement. That is, when the
requirement is released, the regulatory list is also released for active usage.
The standard system is delivered with the following regulatory list types:
● Boiling Point
● Carbon Content
● Emission Factor
● Global Warming Potential
● High Heating Value
● Liquid Density
● Low Heating Value
● Molecular Weight
● Vapor Pressure Equation Constant
● Vapor Pressure
To be able to create a new regulatory list, the environmental manager has to maintain the
following details:
● Name
● Official Name (more detailed description)
● Chemical/Physical Property - specifies the chemical/physical property for which the
regulatory list is created; the app does not allow changes on any predefined chemical/
physical properties
● Listed Substance/Pollutant
regulatory list and the data source will be based on the regulatory list types (for example,
Emission Factor) and the predefined value (0,0016 kg/MMBtu). This is shown in the example
in the figure above.
Equations
Define Equations
When the environmental manager prepares industry-relevant compliance requirements at the
company, the regulatory equations that must be used for the calculation of the environmental
data (for example, calculation of produced emissions) have to be identified. These equations
can be either identified in the regulations, permits, policies, or, depending on the business
case, created by the environmental manager in the compliance requirements.
The equations can be reused multiple times and the environmental manager can ensure that
the same methodology of calculation is being applied. An important aspect is that they also
allow multiple expressions one after another with multiple final results.
The equations control the mechanism of identification and calculation of environmentally-
relevant data at the company and later, the reporting of this data to the respective authority
or the supervisory organization.
To define equations, the environmental manager can specify the following types of results:
● Final
The final results represent the final values persisted as individual data sets that are the
product of the calculations. The final results can be used for direct reporting to the authorities
and/or for follow-up calculations. Depending on the use case, final results can be used also in
other expressions of the same equation (similarly to the intermediate results).
● Intermediate
The intermediate results represent transitional values that are used (for example, as input
variables) in other expressions of the same equation. The intermediate results cannot be used
for direct reporting of data to the authorities. Instead, the environmental manager can specify
various expressions with intermediate results that can be reused in the same equation for
calculating environmental data. This way, the expressions with intermediate results facilitate
the definition of larger, error-prone equations. Using expressions with intermediate results in
the equation allows handling of more complex methodologies which require a lot of sequential
steps (for example, tank equations).
The mathematical expression of an equation consists of numbers (constants), mathematical
functions, operators, and input variables that are used in the calculations.
The intermediate or final results (output variables) can be reused as input variables within the
expressions of the equation. However, to avoid recursive references between expressions,
there are sequence dependencies and restrictions that are implemented in the Check
Consistency functionality. Furthermore, to ensure the correctness of the entered dimensions,
you can use the Check Dimensions functionality.
The equations conform to the lifecycle of the compliance requirement. When the requirement
is released, the equation is also released for active usage.
The environmental manager only defines the equations as a basis for future calculations. The
environmental manager can check the usage of the equation across the calculation activities
and the corresponding compliance scenarios. The Where Used list also enables the
environmental manager to navigate directly to the activities and scenarios that use the
equation.
Note:
In addition, equations can be deleted but first it must be ensured that they are not
used in any calculation activities.
Usage of Equations
After an equation is created and released, it can be used actively. The environmental manager
can use the equations and perform calculations of environmentally-relevant data.
The following figure provides you with an example of the usage of the equation in a
compliance scenario in the system.
LESSON SUMMARY
You should now be able to:
● Create compliance requirements
● Create environmental limits
● Create regulatory lists
● Create equations
● Create compliance requirement
Lesson 1
Creating and Managing a Compliance Scenario in the system 99
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create and setup the data collection process
● Create and setup sampling
● Create and setup calculations
● Create and setup location-aggregations
● Create compliance scenario for power unit B1
● Set up compliance scenario activities for power unit B1
● Copy compliance scenario to power unit B2
● Create compliance scenario for Power Plant Boston
● Set up compliance scenario activities for Power Plant Boston
● Activate compliance scenarios for Power Plant Boston and its sublocations
● Record environmental data for power unit B1
● Record environmental data for power unit B2
The data collection process is a main step in the emissions management process. In the
compliance scenario, a standard activity can be used to do the following:
● Add
● Schedule
● Monitor the collection of environmentally-related data at your location (or equipment)
It contains all the necessary information (such as the subject, the unit of measurement, and
the data period) that is needed to carry out the collection of environmentally-related data.
Later on, the collected data is used in the emissions calculation activities.
and data collection ID); the data collection name is a free text heading that is specified by the
user and serves for the identification of the data collection across the applications. Note that
the data collection name is optional and if you do not provide an entry, the application
automatically sets the title of the collected data as a data collection name.
A data period has to be entered. The data period is the time period that is used to characterize
the collected data in terms of usage or validity.
The environmental manager must enter the subject (a chemical substance, mixture, listed
substance, or chemical/physical property) for which data collection will be scheduled.
A unit of measurement of the subject must be also specified.
Optionally, specify the method that you want to use for data collection: Manual or Automatic.
Important to know is that when you create hourly data collection activities, the input method
can only be automatic.
In case data from another system has to be used in the emissions calculation process, an
external source must be specified. An external source tag is mandatory for data collection
activities with automatic input method.
As a result, a new data collection is created in the compliance scenario.
You can change or update the details of an existing data collection definition. You can update
the list of persons responsible for carrying out the data collection or the due period. However,
to prevent changes to definitions that are in productive usage within the compliance
scenarios, the system restricts the editing of active data collection definitions. To edit the
data collection definition, the status of the compliance scenario revision must be Inactive.
It checks for missing or not yet scheduled data records in all active data collection definitions.
A key element is the processing of the due date for a specific data collection definition. The
background job automatically defines the day on which the next data collection value should
be entered. This is based on the scheduling information specified in the data collection
definition (start date and due period) and the data period.
The data period of the data collection, and the input method of the data, are inter-dependent.
If the check of the background job detects missing data for daily, monthly, or yearly data
period, the system recognizes that the collection for those data records, is manual. For the
hourly data collection periodicity, the system identifies that the data is imported
automatically by an import interface. It responds by sending a notification with the missing
data records to the assigned environmental manager.
In unit 11, you will be able to see where the background job is defined in the customizing.
Under the data collection details, the following details can be changed:
● Name
● Input Method - In the Details section, choose the Manual or Automatic input method,
depending on the way you want environmental data to be collected.
Manual: An environmental technician will receive a notification by the system, which contains
information about the data that must be collected.
Automatic: The system is configured to receive the data automatically using a data import
interface. Persons responsible are not assigned or involved. The system uses a technical
name SAP_WFRT for the role, which is assigned to specify that the data collection is
automatic.
● Allow Overwrite
● Automatic Approval
● Schedule
The assignment of environmental technicians for a Location can be edited in the Persons
Responsible for Location section in the location master data details.
By default, each value is expected by the system and not marked as Missing within the span
of the data period of the corresponding data collection activity.
For example, data collection activities of data period Daily are expected to receive data all
through the day, data collections of data period, Monthly - throughout the entire month, and
data collections of data period, Yearly - during the course of the year.
The Due Date (calculated by the system from Due Within) that was entered controls for how
long the value should be expected in the system after the expiry of the data period. After the
expiration of that due date, the concrete record is marked as Missing, and the environmental
technician is notified of the overdue data collection value by email. If the value is still not
supplied a day after the notification has been received, a separate notification for the overdue
data collection value is also sent to the environmental manager.
The start date in the Schedule section cannot be changed.
Note:
You cannot change the start date in the Schedule section.
The start date denotes the Valid From date of the compliance scenario revision. When you
activate the scenario and the data collection activities, the system allows you to choose
whether you want to use the start date or the date of activation as a beginning for the data
collection.
After the environmental manager plans the activities and activates the data collection in the
compliance scenarios, the collection of the environmentally-related data can start.
As long as the persons responsible for the data collection are correctly assigned and the users
have the required authorizations, the system triggers the e-mail notification. The
environmental technicians or operators who are assigned to collect the data receive their
tasks by e-mail after the activation of the compliance scenario.
Filters
The system provides predefined views for all, pending data collections and for data with no
schedule. Additionally, the result table indicates with a red color the number of pending
records and corresponding collection schedule (for example, yearly, quarterly).
The system displays a header for the data which must be collected. Important improvement
here is the indication of the location path and the indicator for the average collected values
based on the previous 20 records.
There certain prerequisites that have be set up, which are as follows:
● You have to set up the master data for locations and chemicals.
● You have to configure the automatic data collection import interface to work in integration
with MII, so that data can be transferred from an external source into the environment
management system.
● The background job for data collection checks is scheduled in Customizing.
Using the Monitor Data - Environment Management app, the environmental manager can
browse for data files from the file system and import these files into the data collection
definition that is currently open for monitoring.
When a file for import is specified, the app loads it and examines the data records stored in it.
Then, the app runs data consistency checks and outlines the potential import related issues
that may occur in the system.
After the potential issues are resolved, the app imports and stores the environmental data in
the system.
Finally, the data-related checks (such as environmental limits) are run.
When the Monitor Data - Environment Management app opens, the system displays a
graphical representation of all values (data records).
Optionally, using the additional search criteria, you can filter out data records based on time
period, status, issue type, or presence of deviation incidents, and preliminary results for
calculated data.
Select a value to display further details of it, such as issue type, status, date, value, history of
changes in case the value was replaced or a link to a deviation incident created for the value.
When you select more than one value, the app displays the details of the last one selected.
In the results list (either graphical or table view), you can take action in case there is an
unusual value that requires immediate attention. To do this, you can select a record, and then,
carry out one of the following activities:
● Approve the data record - You can accept the value (collected or calculated) and provide a
short description in the Comment field to explain your decision.
If you approve an empty data record regardless of whether it was not yet collected or it was
not collected on purpose, the record is considered unavailable and causes data issue of the
type, Data Not Available.
When you are using monitoring apps, you cannot approve sampled data records. Sampled
data is approved and finalized only in the Sampling Overview section of the compliance
scenario. Therefore, you have to do the following:
● Replace the value of the data record - You can replace an incorrect or missing value and
provide a short description in the Comment field to explain your decision.
● Invalidate the data record - If you consider the value of a data record incorrect and you do
not want to use it further, you can invalidate the record.
● Create a deviation incident for the record - You can create a deviation incident for a
selected data record (collected or calculated data) and investigate the reason for it as part
of another process.
● Import additional data records by using a spreadsheet data file
The environment management system enables the environmental manager to import data
from spreadsheet files.
A sampling method is an object that contains information about the details of the sampling
procedure of a given material or a listed substance and the expected results (analytes).
The creation of a new sampling method can be done either directly upon adding the sampling
activity in the compliance scenario or by using the Sampling Method - Environment
Management app.
Sampling Activities
The sampling definition enables the environmental manager to set up and organize sampling
collection activities to ensure environmental compliance of industrial processes. The
sampling definition can be accessed and edited in the compliance scenario.
Using the sampling definition, the environmental manager can do the following:
Adding analytes and expected sampling results to the sampling can be done manually.
Alternatively, choosing the Autofill Components from Chemical, which can be used to
automatically populate the analytes based on the sampled subject, sampling method, or a
combination of both. After the confirmation of the dialog box, the sampling activity is added to
the compliance scenario.
At a glance, the environmental manager can view the sampling definition and the composition
of analytes.
If required, environmental limits can be assigned based on the compliance requirement setup.
The system will check the incoming sampling data against the limits and indicate if warning or
exceedance levels have been reached.
Additional analytes can be added to an already initiated sampling in the same app.
Sampling Activities
The Sampling Overview screen provides the environmental manager with a means for
handling and overview of the different sampling processes by status.
Plan Sampling
The planning of the sampling can be triggered from the Sampling Overview page.
The environmental manager can schedule sampling dates and process sampled data in
organized sampling processes. The handling of all sampling activities and process steps is
done within the compliance scenario. The planning of the sampling is completed as soon as
the sampling dates are defined, and the dialog box is confirmed.
The sampling process can be performed also retrospectively by selecting sampling dates in
the past. This allows the environmental manager to keep record of all performed activities
even if they were done ad-hoc.
In this case, the Planned Samples section will display all future sampling dates that the
sampling process will be triggered on.
Sampling Results
Upon submission of sampling results, the system can perform the follow-up limit checks and
calculations.
When the results have been submitted, the system carries out follow-up limit checks and
calculations on the data.
The limit checks are applied only to the final data.
The additional aggregation functions support experts to finalize the sampling result faster,
especially for activities where multiple physical sample results need to be handled.
If required, the sampling can be invalidated.
Complete Sampling
If the values are submitted, the sampled data is saved and the samples for the respective date
are moved to the Completed Samples section where the results are displayed. The invalidated
samples are displayed on the Sampling Overview page. In addition, the system makes the
finalized sampling results available as input for calculation activities.
Calculations
Calculating Environmentally-Related Data
The environmental manager can use the activities in the compliance scenario to manage the
calculations of emissions at the location (or equipment). The calculations can be based on the
provided equations in the compliance requirement and the data from regulatory lists,
collected environmentally-related data, or other calculations (chained calculations are
allowed).
The automatic mode of calculation is controlled by a background job that runs in the back-end
system when given events occur like when input data for a given period is available in the
system.
A calculation activity consists of the following major components:
● A calculation setup that carries the basic information and details of the calculation, such as
name, description, calculation mode, and link to the specified equation (if applicable).
● A calculation result that represents a container for the environmentally-relevant data sets
produced by the calculation. Each calculation result carries information about the subject
of calculation (a material, listed substance, or chemical/physical property), its unit, and its
data period.
A calculation expression is the mathematical formula that you use for the calculation of
environmentally-relevant data. It has input variables of environmental data, such as collected
or sampled values that are recorded in the system, the results of other calculations,
regulatory lists, or locally defined fixed values.
Add Calculation
The rolling calculation results are supported by an aggregation function with the following
parameters:
● SUM (input; periods)
● AVG (input; periods)
● MIN (input; periods)
● MAX (input; periods)
Calculation Setup
The Calculation Setup section can be further edited by the environment manager.
● Automatic for Complete Data Only - The system performs the calculation automatically at
the end of the calculation period only if complete set of input data is available.
● Manual - The system does not perform the calculation automatically.
Define Expression
The environmental manager enters the expression manually.
These are valid operations and functions that the environmental manager has used in the
expression definition.
All aggregation functions work with numbers, variables, functions, and other calculations.
The following principles apply in the use of aggregation function parameters:
● Variables (VAR_A, VAR_B, and so on) accept variable data sets from sources such as data
collections, calculations, and location aggregations.
● N accepts constant data source with positive integer value. Default value is N=1.
● FROM and TO accept data with a valid date format.
Input Variables
To complete the setup of the calculation, the environmental manager has to complete the
definition of the variables.
The input variables of the expression are the placeholders for the real environmental data that
should be used in the calculation.
The data source type (Calculated Data, Collected Data, Location Aggregated Data, Fixed
Value, Regulatory List, Sampled Data, Date, Location Data) and the data source have to be
defined.
The environmental limits can be assigned. This triggers automatic system checks when the
calculation is being performed.
Add Calculation
After adding the calculation activity, the system informs the environmental manager that the
data sources for the calculation have not been defined. The calculation has to be further set
up through the Calculation Setup Details page.
Calculation Setup
The calculation name and description can be further refined and updated.
If the result title is not defined in the equation, the functions Set Title and/or Set Period should
be used to finalize the definition.
Equation Details
The details of the equation are not editable.
The equation name is presented as a link that can be used by the environmental manager.
The subject and the unit of measurement are already populated by the system from the
equation.
Set Title
A data period is the time period that is used to characterize the calculated data in terms of
use or validity.
Results
The result type has been defined.
Input Variables
The environmental manager has to complete the definition of the variables. The input
variables of the expression are the placeholders for the real environmental data that should
be used in the calculation. The data source type can be calculated, collected, location-based
aggregated, sampled data or location data, fixed value or regulatory list. The solution allows a
chain of calculations and aggregations one after the other to support more complex
scenarios.
For example, on an equipment level the user can have a conversion from fuel to emissions,
then on a plant level there could be an aggregation per emissions and then another
calculation to convert the emissions to equivalent (for further information, refer to the
process walkthrough).
The environmental limits can be assigned to each calculation result. This triggers automatic
system checks when the calculation is performed.
When the environmental manager finishes the editing of the calculation setup and before
he/she activates it (by activating the compliance scenario), a check can be performed to
verify how the calculation works either using real data that is available in the system, or by
providing own data values.
There are two ways to start the manual calculation. It can be done either from the compliance
scenario by selecting the activity or from the calculation activity setup details.
The results of the manual calculation override and replace the results of the previous
calculation, regardless of whether it was manual or automatic.
Test Calculation
In the Calculation Setup Details page, the environmental manager is enabled to perform a test
calculation.
Monitor Calculate
Accessing the Monitor Data - Environment Management app through the compliance
scenario, the environmental manager can monitor the calculated data against the
environmental limit and identify any potential issues with it.
Location-aggregations
Aggregating Environmentally-Related Data
The Location Aggregation activity allows the environmental manager to acquire aggregated
values of the environmental data for the purposes of environmental assessments and
reporting to authorities.
The activity of data aggregation is created and managed in the system based on the
company's location structure. Location-based aggregations use as input data collections,
sampled data, and calculated data from compliance scenarios. Aggregation results depend
on the recorded environmental data which was approved and on the chosen mathematical
function which governs the running of the aggregation itself.
Location-based aggregations can be performed manually or scheduled to run automatically.
The automatic aggregations are triggered when the status of the matching data gets updated.
When defining the location-based aggregation, the environmental manager specifies which
mathematical function will be used for the aggregation activity.
The following aggregation functions are available:
● Arithmetic Sum (SUM)
● Arithmetic Average (AVG)
● Maximum Value (MAX)
● Minimum Value (MIN)
● Count of Elements (COUNT)
The Result Data Definition section of the dialog box requires the following aggregation
parameters:
● Data Period - defines the periodicity for the data sets to be aggregated. It can be set to
Hourly, Daily, Monthly, Quarterly, or Half-Yearly, Yearly. It acts as a filter for the Matching
Data list.
● Subject - identifies the type of material data, listed substance, or chemical/physical
property, for which the system aggregates data. If a listed substance group is selected in
the subject, the matching data finds all data sets for the listed substances part of the same
group.
● Unit - used to specify the unit of measurement for the selected subject.
You specify the mathematical function that you want to be used for your aggregation activity.
The following aggregation functions are available:
● Arithmetic Sum (SUM)
● Arithmetic Average (AVG)
● Maximum Value (MAX)
● Minimum Value (MIN)
● Count of Elements (COUNT)
The aggregated data and the function can no longer be changed. The name and the
description of the aggregation are editable.
The Aggregation Mode determines the condition according to which an automatic
aggregation will or will not be performed. The following aggregation modes are available for
selection:
● Automatic - The system calculates automatically as soon as possible. If the period is not
over or the input data is incomplete, the calculation result is marked as preliminary.
● Automatic for Complete Data Only - The system calculates automatically at the end of
the calculation period only if the complete set of input data is available.
● Manual - The system does not calculate automatically.
The Matching Data section displays all the data sets that match all conditions defined during
the setup of the location aggregation - the subject, the data period, the unit of measurement.
They are assigned within the location structure underneath the current location. For example,
if the location-based aggregation is on a plant level, the system will display the data sets for
this location.
The environmental manager can select the data records that will be aggregated, choose Yes
from the drop-down list and execute Set Classifier for the marked data records so that they
are included in the aggregation. The data records that should not be included in the
aggregation must be set to No.
The environmental manager can select the data records, choose No from the drop-down list
and execute Set Classifier for the marked data records.
To start the procedure, the environmental manager chooses Aggregate Manually. The
aggregation wizard opens.
Under the Reason section, a mandatory explanation has to be entered in the Description field.
A data period can be filtered and the data included in the aggregation data for that period -
displayed.
In the final step, the environmental manager can review all data included in the aggregation.
The overview table displays the following information:
● Period
● Value
● Unit
● Status
● Value Not Available
● Preliminary Result - the flag indicates that not all data was available at the time when the
aggregation was processed. In the displayed example for the month of January, not all
data was gathered.
LESSON SUMMARY
You should now be able to:
● Create and setup the data collection process
● Create and setup sampling
● Create and setup calculations
● Create and setup location-aggregations
● Create compliance scenario for power unit B1
● Set up compliance scenario activities for power unit B1
● Copy compliance scenario to power unit B2
● Create compliance scenario for Power Plant Boston
● Set up compliance scenario activities for Power Plant Boston
● Activate compliance scenarios for Power Plant Boston and its sublocations
● Record environmental data for power unit B1
● Record environmental data for power unit B2
Lesson 1
Getting familiar with Environmental Data Monitoring tools 147
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Monitor data issues
● Examine emissions forecast
● Check environmental data with the Environmental Data Explorer
● Check environmental data with the Environmental Data Monitor
● Monitor environmental data for Power Plant Boston
Figure 227: Monitor Environmental Data with the Data Issues apps 1/4
In this way, the monitors allow the environmental manager to quickly identify potential issues
with the environmentally-related data, so that he or she can take preventive or corrective
measures in time. The issue monitoring apps display issues related to data that was either
collected or calculated only in the locations of the responsibility of the environmental
manager.
Figure 228: Monitor Environmental Data with the Data Issues apps 2/4
The app supports the environmental manager so that they can monitor the following:
● Limit Exceedances: The environmentally-related data was checked against the values of an
environmental limit (threshold) and the data exceeds either the upper or the lower limit
value.
● Warnings: The environmental data was checked against the values of an environmental
limit and the data has surpassed the warning value but not the limit value.
● Missing Data: Indicates that the environmentally-related data has not yet been collected or
calculated.
● Data Not Available: The environmental data does not contain any specific value, but only a
comment.
Figure 229: Monitor Environmental Data with the Data Issues apps 3/4
When specific data issues are being monitored, the app displays additional information, such
as location and value details, violated environmental limits, and a link for monitoring the other
data records that are part of the same activity.
Figure 230: Monitor Environmental Data with the Data Issues apps 4/4
In the results list, the environmental manager can select a record, and then, carry out one of
the following activities:
● Approve – The collected or calculated value can be accepted, and a short description in the
Comment field, to explain the decision can be entered. If an empty data record is being
approved regardless of whether it was not yet collected or it was not collected on purpose,
the record is considered unavailable and causes a data issue of the type, Data Not
Available.
● Replace – A replacement of an incorrect or missing value can be done, and a short
description in the Comment field, is required to explain the decision.
● Invalidate - If the value of a data record is incorrect, and if it will not be used further, the
record can be invalidated.
● Create Deviation Incident - A deviation incident for a selected data record (collected or
calculated data) can be created and investigation for the reason for it can be performed as
part of the incident management process.
Emissions Forecasting
Forecast with Monitor Data app
A Forecast button is enabled on all tabs in the Monitor Data - Environment Management app.
By default, the button is inactive.
The environmental manager needs to select the respective data for the activity from the list. It
is only then that the button becomes active and forecasting can be performed.
Emission Forecast
Forecast Concept
The environmental manager can forecast emission data based on historical emission data
with the help of predictive learning algorithms and statistical methods. Additionally, a
comparison of the forecasted emission data against the environmental limits can be
performed. By getting early indications of future deviations or noncompliance, the
environmental manager can plan proactively to avoid potentially unwanted events.
Emissions are forecasted based on historical emissions data with the help of predictive
learning algorithms and statistical methods. The forecasted emissions can be compared to
the environmental limits. This is a very powerful way of getting an early indication of future
deviations or noncompliance.
Forecasting Methods
The emissions forecasting functionality is enabled to use predictive and custom-developed
algorithms. The standard delivery of the app comes with two forecast methods:
● Double Exponential Smoothing method
The Double Exponential Smoothing model is suitable to model time series with the trend but
without seasonality. In the model, there are two kinds of smoothed quantities: smoothed
signal and smoothed trend.
It is part of the SAP HANA Predictive Analysis Library (PAL). SAP PAL defines functions that
can be called from within SQLScript procedures to perform analytical algorithms.
SAP PAL includes classic and universal predictive analysis algorithms in ten data-mining
categories, time series algorithms being the ones applicable for emissions forecasting.
The Latest Delta Extrapolation method is a statistical method that takes the difference of the
last two values and extrapolates it linearly for the forecast period.
Figure 236: Monitor Environmental Data with the Environmental Data Explorer App 1/4
The Environmental Data Explorer app provides the possibility to monitor and browse all
transactional data in the system. The app enables the environmental manager to view the
data (collected, calculated, sampled, or aggregated) associated with its location in the
hierarchy.
After a location at which the monitoring of the data should occur is selected, the app enables
the environmental manager to additionally filter out data based on various criteria, such as
issue type, data status, calendar date, data type, data title, location, and preliminary results.
Besides the monitoring aspect of the Environmental Data Explorer app, the app enables the
environmental manager to analyze, slice and dice the data, and then, export it in spreadsheet
for further use.
Monitor Environmental Data with the Environmental Data Explorer App 2/4
As a starting point, the relevant location has to be selected. By default, the app displays the
My Location of the environmental manager.
Figure 237: Monitor Environmental Data with the Environmental Data Explorer App 2/4
If required, the monitoring and the analysis can be performed for another location. The Show
All Locations option displays the whole location structure.
Monitor Environmental Data with the Environmental Data Explorer App 3/4
With the help of the available filters, the result can be further refined.
Figure 238: Monitor Environmental Data with the Environmental Data Explorer App 3/4
Monitor Environmental Data with the Environmental Data Explorer App 4/4
The result of the data refinement is displayed in the Items table.
Figure 239: Monitor Environmental Data with the Environmental Data Explorer App 4/4
To produce internal or external reports that are necessary to fulfill legal, regulatory, or
internal reporting requirements, the environmental manager has to export the
environmentally-related data for later use as the basis of these reports.
Furthermore, the app enables you to export the environmental data to a file on the file system
either to a plain spreadsheet, or to a predefined file-based report. For more information, see
unit 8.
In this case, the Monitor Data - Environmental Management app is opened to support the
monitoring of the environmental data.
Figure 241: Monitor Environmental Data with Monitor Data app 1/4
The app enables the environmental manager to perform the following functions:
● Review environmental data records for a specific data collection, calculation, aggregation,
or sampling activity
● Overview the data graphically
● Filter data records by different criteria
● Process data by approving, replacing, or invalidating data records
● Process data exceedances of environmental limits through deviation incidents
● Import environmental data using spreadsheet files from the file system
● Export data records to file-based reports
Figure 242: Monitor Environmental Data with Monitor Data app 2/4
Figure 243: Monitor Environmental Data with Monitor Data app 3/4
Figure 244: Monitor Environmental Data with Monitor Data app 4/4
Moreover, there is a possibility to use further search criteria to get the best possible view on
the records.
The red dotted line indicates the Upper Limit, which is assigned to the environmental record.
As soon as the line is crossed the environmental manager can create a deviation.
The yellow dotted line indicates the Upper Limit warning. As soon as the record crosses the
environmental manager will get a notification from the system.
LESSON SUMMARY
You should now be able to:
● Monitor data issues
● Examine emissions forecast
● Check environmental data with the Environmental Data Explorer
● Check environmental data with the Environmental Data Monitor
● Monitor environmental data for Power Plant Boston
Lesson 1
Getting familiar with the Task Management process 161
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create and manage tasks from compliance requirement
● Create and manage tasks from compliance scenario
● Create a task from a compliance requirement
● Monitor tasks
Similar to other objects in Environment, Health, and Safety, the task definitions that you
create have a specific lifecycle that is controlled by their status at a given moment. The
following statuses are valid for the task:
New
● This is the initial status of a task definition. It is set when the task is created and saved.
Note that you can only delete task definition with the status New.
In Process
● When you schedule and save the task, the system creates an instance of the task for
processing and sets the status of the task definition to In Process.
Closed
● When all of the task process instances are closed, the task status is also set to Closed and
the task is considered carried out and complete.
Task Types
An assignee is the party that actually carries out the task. The assignee receives a work item
of the task in his or her inbox. He or she can accept, reject, or forward the task to another
assignee.
● Owner
An owner is the party that is responsible for monitoring the execution of a task. The owner is
notified of a task, only if the assignee discards the task, or, if it is a task with approval, if the
approver does not approve the task.
An approver is the person who checks if the task was carried out correctly by the assignee.
When a task is implemented, the approver automatically receives an approval work item in his
or her inbox.
● Start Date and Due Date
● Priority
In the Attachments section, attach any relevant document or link, for example, if you want to
add background information as a reference to the created task. Note that the attached
document exists only in the task definition and it is not visible in the task instance (or the
implementer work item) once the task process is started.
In addition, there is a possibility to design the task as recurrent.
As part of the standard workflow of the environmentally-related task, the specified owner,
assignee, or approver, receives a work item (a reference to a task instance) in their inbox.
Then, they process the work item as appropriate and after all work items are processed and
done, the task instance is set to Completed.
Task Lifecycle
The task status provides information about the current state of a task instance. The following
task statuses are available:
Scheduled
● Specifies a task instance that is planned but its workflow is not generated, and the task
instance is not yet in the user's inbox.
Due
● Specifies a task instance that has reached its start date and is visible in the user's inbox.
Overdue
● Specifies a task instance that has not been performed by its due date.
Completed
● Specifies a task instance that has been confirmed as finished.
Canceled
● Specifies a task instance that is no longer needed, and has been made inactive.
Error
● Specifies a technical error in the task instance definition or the workflow.
Implementing Tasks
There are numerous options related to implementing tasks.
The responsible person can complete or reject the task by selecting the corresponding
button.
Completed
● When the corresponding approver approves the task, the workflow finishes and the task
instance is closed.
Reject
● When the corresponding approver does not approve the implementation of a task, the
workflow goes on and it invokes the step of the process where the due date or the
implementer can be changed. In this case, the task is sent to the inbox of the person
responsible and he or she can reassign it to another processor or change its due date.
In case the task is rejected, the task owner has to handle the rejection.
Open Task
You can handle an open task in a number of ways.
Handle the rejection of the task implementation by selecting the corresponding radio button.
Re-send
● When you resend a task, the workflow goes to the previous process step. This means that
the task is sent back to the inbox of the assignee of the task instance for further processing
and execution.
Cancel
● When you cancel the implementation of a task, the workflow is removed from the inbox.
The Cancel option allows the owner of the task to cancel the task implementation directly
from the My Inbox app without entering the Display Task Instance app.
● Create Deviation
This option allows the responsible person to create deviation. If the deviation is created from
the Task Instance app, the task process will be displayed as triggering task in the Deviation
tab.
● Change Assignee
If a change of the assignee is required, the owner can choose Change Assignee. With the
support of a value help, the new person can be selected. The person needs to be a business
user in order to appear in the list. Changing the assignee is an operation on a task process
level.
● Change Due Date
If a change of the due date is required, the owner can choose Change Due Date. With the
support of a value help type calendar view, the new date can be selected. The Due Date can
not be in the past. Changing the due date is an operation on a task process level.
Resend and Cancel are also available on selection of the current step of the task.
Approving Tasks
The environmental manager can approve or reject implementation of the task by selecting the
corresponding button.
Approved
● When the implemented task is approved, the workflow goes to the next process step. This
means that either the task is sent to the inbox of the approver (if an approver is specified in
the task definition), or the task instance is closed (in case an approval step is not planned).
Rejected
● When the environmental manager rejects the implementation of a task, the workflow goes
on to the Handle Rejection process step. This means that the task is sent to the inbox of
the person responsible and they can reassign it to another processor or change its due
date.
Tasks Approved
When the implementation of the task is completed and approved, the status of the task is
updated in the compliance requirement.
Monitoring and Processing Compliance Requirement Tasks through the Monitor Tasks
app
The various monitoring applications in the environment management component enable you
to monitor the environmentally-relevant data that is available in the system. Depending on the
monitoring use case that you wish to accomplish, you can use the application that is most
useful for the case.
Figure 256: Monitoring and Processing Compliance Requirement Tasks through the Monitor Tasks app
The Monitor Tasks app enables you to find and monitor environmentally-relevant tasks that
are created in the compliance requirements. Using the app, you can filter out tasks based on
various criteria, such as start, due, or completion dates, priority, origin type, current
processor or owner, and location. In addition, in the app you can navigate to the task instance
from the monitor where you can view detailed information.
Depending on the use case that you wish to accomplish, you can process a task from the
result list in any of the following ways:
● Perform task-related activities (process a task)
You can navigate to the task instance from the list of tasks, to view its details. On the Task
Instance screen you can either cancel a task, or open a task definition for editing.
Furthermore, you can provide comments to the task, view related objects, and add
attachments relevant for the task.
When you open the task definition for editing, you can change its title, description, assignee,
owner, priority, and recurrence, add attachments, or delete the task.
● Receiving e-mail notifications for tasks
On saving a changed or newly created task definition, the system sends push notifications to
the assignee of the task.
Environmental managers use tasks to organize and plan all actions associated to the overall
compliance scenario or any aspect of the compliance scenario, such as, applicable locations
(pieces of equipment), assigned compliance requirements, or any checks related to the
scenario activities. To start a task processing, environmental managers first create objects
known as task definitions. These objects encapsulate the information needed for the
execution of the task, such as priority, scheduling and recurrence, responsibilities, and
additional pieces of information, for example, attachments or links.
Task Definition Lifecycle
● New
This is the initial status of a task definition. It is set when the task is created and saved. Note
that you can only delete task definition with the status, New.
● In Process
When you schedule and save the task, the system creates an instance of the task for
processing and sets the status of the task definition to In Process.
● Closed
When all of the task process instances are closed, the task status is also set to Closed and the
task is considered carried out and complete.
Task Types
The following figure provides you with an example of choosing a task type.
An assignee is the party that actually carries out the task. The assignee receives a work item
of the task in his or her inbox. He or she can accept, reject, or forward the task to another
assignee.
● Owner
An owner is the party that is responsible for monitoring the execution of a task. The owner is
notified of a task, only if the assignee discards the task, or, if it is a task with approval, if the
approver does not approve the task.
● Approver (if a task with approval was selected)
An approver is the person who checks if the task was carried out correctly by the assignee.
When a task is implemented, the approver automatically receives an approval work item in his
or her inbox.
● Start Date and Due Date
● Priority
In the Attachments section, attach any relevant document or link, for example, if you want to
add background information as a reference to the created task. Note that the attached
document exists only in the task definition and it is not visible in the task instance (or the
implementer work item) once the task process is started.
The task processing and monitoring process is the same as in the previous chapter.
LESSON SUMMARY
You should now be able to:
● Create and manage tasks from compliance requirement
● Create and manage tasks from compliance scenario
● Create a task from a compliance requirement
● Monitor tasks
Lesson 1
Understanding how to Manage Deviations 177
UNIT OBJECTIVES
● Create deviations
● Carry out investigations
● Take corrective measures
● Report deviations
● Creating a deviation for Power Plant Boston
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create deviations
● Carry out investigations
● Take corrective measures
● Report deviations
● Creating a deviation for Power Plant Boston
Deviations
Incident Deviation Process
Deviations in the emissions management process are used to handle cases of violation of
environmental requirements.
Let us start with creating a deviation from the Monitor Data app.
The environmental manager can monitor the environmental data and check it against the
assigned environmental limit. If any exceedances have been noticed, an incident of the
deviation type can be created from the Monitor Data - Environment Management app by
selecting the records directly from the graphic or from the table view and using the Create
Deviation Incident button.
If required, a deviation can be created from the Create Deviation Incident option.
During the review and completion process, the information that is entered is already available
for the deviation and can be validated or changed, if necessary.
The access to the entire deviation record can be restricted using the Restricted Access radio
button. If restricted access is chosen, the deviation record is only displayed to users who are
allowed to access confidential information. The access to confidential information is
controlled by the access level settings of the EHS Incident authorization object.
Tab Deviation
Under the Deviation tab, the environmental manager can specify compliance requirements
that relate to the entire deviation.
If the deviation has been created from the compliance requirement, the following occurs:
● The relevant compliance requirement is pre-filled based on the data and the environmental
limit.
● The Deviation Data subtab shows the relevant environmental data, which is a subject for
the created deviation.
The source of the deviation or the tasks that triggered the deviation can be added.
If a task has been identified as the root cause for the deviation, the Triggering Tasks subtab
will display it. New tasks can be added using the Add option.
Create Deviation
The created deviation incident can be further edited using the Manage Deviation Incidents
app.
The created deviation automatically shows the respective task set as a triggering task, and
the relevant task information is automatically populated.
To create the deviation, the environmental manager maintains certain fields. By default, the
start date, time zone, and follow up issue category are mandatory fields.
Investigations
Investigation Process
You do an investigation to determine the causes that led to an deviation incident. Depending
on legal or organization-specific requirements, an investigation can include different
investigation steps, for example, a root cause analysis or lessons learned.
Corrective Measures
Take Corrective and Preventive Measures
The Tasks tab of a deviation allows the environmental manager to define and process
corrective and preventive measures, such as the following:
● Tasks
● Tasks with Approval
● Maintenance Notifications
The Tasks are handled like the Task that were presented in the previous unit.
Deviations Reporting
Deviation Reporting
As an environmental manager, you can use this procedure to review and complete deviation
records that have been created for inconsistent environmentally-related data.
If you go to the Search Deviation Incidents tab. You can already see that the Incident Group
Deviation is predefined.
Filter Options
The environmental manager can adjust the filters by selecting Adapt Filters. In the following
figure, you can see the possible filter options. By selecting the checkboxes, you can add the
filters to the filter bar.
Note:
Exports using profile will be treated in the next unit.
LESSON SUMMARY
You should now be able to:
● Create deviations
● Carry out investigations
● Take corrective measures
● Report deviations
● Creating a deviation for Power Plant Boston
Lesson 1
Understanding how to Export Environmental Data 191
UNIT OBJECTIVES
● Export to Spreadsheet
● Export data using profile
● Export environmental data for Power Plant Boston
● Export data using profile
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Export to Spreadsheet
● Export data using profile
● Export environmental data for Power Plant Boston
● Export data using profile
Export to Spreadsheet
Export Data with Monitor Data app
To produce internal or external reports that are necessary to fulfill legal, regulatory, or
internal reporting requirements, at first, you have to export the environmentally-related data
that you use later on as the basis of these reports. In environment management, you can
prepare and export data for the purpose of reviewing, storing, or reporting environmentally-
relevant information for your company.
To generate and export the recorded, calculated, or aggregated data, the following types of
files are supported in Environment Management:
● To Spreadsheet
You can generate a spreadsheet of the data that is displayed by the corresponding monitoring
applications. The spreadsheet contains environmental data of more than one data type, for
example, a log of all data records of collected, calculated, sampled, or aggregated data that
were recorded in the environment management system over the year.
● To File-Based Report
You can export environmental data of specific data type to a predefined file formats that are
available as templates in the system. The predefined templates can control the structure of
the exported data, the needed attributes, and layout. Later on, you can use these file-based
reports as a basis for your reporting to authorities, for example, to the Environmental
Protection Agency (EPA) in the United States.
Later on, these file-based reports can be used as the basis for reporting to authorities, for
example, to the Environmental Protection Agency (EPA) in the United States.
LESSON SUMMARY
You should now be able to:
● Export to Spreadsheet
● Export data using profile
● Export environmental data for Power Plant Boston
● Export data using profile
Lesson 1
Understanding of the standard delivered example content 197
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Get an overview of example content
● Create customer-specific content
● Integrating with external content providers
● Copy function of compliance requirement
For more information, please refer to the official SAP Note 2404012 - Content for EHS as part
of SAP S/4HANA and SAP S/4HANA Cloud.
Content for Air Emissions and GHG Management Industries cover the following industries:
● Oil and Gas
● Utilities
● Chemicals
● Mining
Note:
The content that was provided by SAP cannot be modified. In this case, copying
the content is necessary, if the environmental manager decides to modify the
example content.
When you retrieve the regulations, the application loads them and determines whether these
regulations are new to the system, or were already imported as compliance requirements.
Then, depending on the presence of these regulations in the Environment Management
system, you can either create new compliance requirements or modify the existing
requirements with the latest updates. After the relevant activity is determined, the application
stores the latest compliance requirements in the system.
The diagram in the figure above outlines the integration and import of compliance
requirements at the system of compliance from the regulatory content provider system.
Establish Secure Communication
● Import Certificates
The content provider system issues its certificate and provides trusted communication via
this certificate. Therefore, to establish trusted relations and machine-to-machine
communication, this certificate must be imported and configured on the system of
compliance. As a result, the entire further communication is encrypted and signed by this
certificate.
● Web Services
Normally, the regulatory content provider system exposes its content using Web services.
This enables the content for consumption by a wide range of remote systems, such as the
Environment Management system. To provide access to these services, the content provider
publishes their corresponding WSDL documents and allows remote and secure access to
these documents for the consumer systems. When secure communication between the
systems is established, the WSDL document can be pulled on the system of compliance and a
Web service consumer can be created out of it.
● Web Service Consumer
To consume a given Web service that is exposed by a remote system, such as the regulatory
content provider, a corresponding Web service consumer has to be created and configured
for it on the client system. A Web service consumer comprises the following entities:
● Consumer proxy
The first step of the creation of a Web service consumer is the generation of a Web service
proxy, and then, the creation of a client application. The client application uses the proxy to
call and consume the Web service.
● Logical port
To access and consume a particular Web service definition, the consumer proxy must be
configured with a corresponding logical port. The logical port contains a reference to the Web
service and has the runtime configuration settings, such as a user name and password, with
which it can access and consume the service endpoint. You can think of a logical port as the
destination to which the Web service consumer with particular runtime settings sends a call
to access a particular service endpoint. For the same consumer proxy, you can create more
than one logical port, each having different runtime settings and pointing to the Web service.
In this way, you can configure the same consumer proxy to call the Web service definition
using different authorization or communication settings.
Import Regulations (Compliance Requirements)
When the communication channel between the content provider and the Environment
Management system is established, you can request information about the regulations that
are available for import from the provider. When you retrieve the information, the provider
system performs internal checks on whether the existing regulations were already initialized
and sent to the consumer. If they are loaded for the first time, the regulations are marked as
initialized. On a subsequent retrieve, the provider does not send them a new one, the provider
sends the changed (updated) information. The provider system prepares an XML file with the
required information about new or updated regulations and sends it to the client system.
● EHS Customizing Conversions
When information is received in the client system, business logic is invoked that parses the
XML file and performs some conversions (specified in EHS Customizing) to harmonize the
received content with the content that can be handled by environment management. When all
information is synchronized, the available regulations are displayed in the client application.
As a next step, you can select which regulations you want to import as compliance
requirements.
● Create Compliance Requirements
The import of regulations from the external content provider system is a process of automatic
creation of compliance requirements that are based on the regulatory information prepared
and sent by the provider system. To import compliance requirements from the content
provider, the corresponding regulations must be selected and the functionality for the
creation of requirements must be invoked. The application pre-fills the required information
from the regulation entry and allows the users to enter their alternative information for the
newly created (imported) compliance requirements.
LESSON SUMMARY
You should now be able to:
● Get an overview of example content
Lesson 1
Learning standard roles and authorisation objects 205
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Get familiar standard front-end and back-end system roles
● Get familiar with standard authorization objects
● Understand the specifics of system user setup
The environmental manager role is assigned to employees who are responsible for ensuring
the organization is compliant with environmental regulations and standards. The
environmental manager is responsible for assessing environmental aspects and impacts,
implementing risk treatment programs for environmental risks, monitoring environmental
performance, conducting control inspections, and investigating any incident that involves
releases into the environment.
To ensure compliance with environmental regulations and standards, the environmental
manager communicates with employees and performs training courses with regard to
potential environmental impacts. This person takes part in the chemical approval process to
ensure that a new chemical that is introduced in the company is checked from an
environmental point of view.
The production operator role is assigned to employees in production departments who
perform tasks, assigned by the environmental manager, to ensure compliance with
environmental regulations and laws. The production operator ensures that the equipment is
maintained in good and safe working condition. He identifies and reports unsafe operations to
the environmental manager. In addition, the production operator evaluates equipment
performance and recommends improvements.
Frontend Roles
Important: All roles are provided without any authorizations assigned to them. You must
assign authorizations using the authorization objects in the backend system.
The environmental manager role is assigned to employees who are responsible for ensuring
the organization is compliant with environmental regulations and standards. The
environmental manager is responsible for assessing environmental aspects and impacts,
implementing risk treatment programs for environmental risks, monitoring environmental
performance, conducting control inspections, and investigating any incident that involves
releases into the environment.
To ensure compliance with environmental regulations and standards, the environmental
manager communicates with employees and performs training courses with regards to
potential environmental impacts. This person takes part in the chemical approval process to
ensure that a new chemical that is introduced in the company is checked from an
environmental point of view.
The Production Operator role is assigned to employees in production departments who
perform tasks, assigned by the environmental manager, to ensure compliance with
environmental regulations and laws. The production operator ensures that the equipment is
maintained in good and safe working conditions. He identifies and reports unsafe operations
to the environmental manager. In addition, the production operator evaluates equipment
performance and recommends improvements.
Note that, when you want to delete activities and compliance scenarios, the system first
checks whether there is recorded environmental data in the compliance scenario activities,
and then performs the authorization check. This means that the system allows users who are
not configured with activity 06 (Delete) to delete empty compliance scenario activities and
empty compliance scenarios.
● Activity 76 (Enter) controls the access of the environmental technician to pending data
collections.
This activity must be enabled of technician. Otherwise, they cannot enter environmental data
into the system and hence process pending data collections.
● The non-mandatory
fields LOCTYPE, LOCSTATUS, LOCAUTHGRP, LOCPLANT , LOCCOST, LOCCOMP, LOCB
USAREA, LOCCOUNTRY , and LOCREGION are used to specify the compliance scenario
depending on the additional details of its location. For each role that uses
the EHENV_SCEN authorization object you can define the following in the authorization
data:
● If the user is authorized to manage compliance scenarios that are assigned to locations
with specific details only, specify the concrete values in the corresponding fields of the
authorization object.
● If the user is authorized to manage compliance scenarios that are assigned to locations
with any details, specify an asterisk (*) in the corresponding fields of the authorization
object.
● If the user is authorized to manage compliance scenarios that are assigned to
locations without any details, specify an empty string ('') in the corresponding fields of the
authorization object.
Note that you are not allowed to specify an empty string for the non-mandatory
field LOCAUTHGRP. Therefore, if the user is authorized to manage compliance scenarios that
are assigned to locations without set LOCAUTHGRP, specify a new authorization object
separately and any entries in that field.
For the Business User in SAP S/4HANA the person, work center, and communication-related
data are derived from the related Business Partner with relation 1:1. This data for person, work
center, communication and company is persistent and derived from the
corresponding Business Partner and no longer redundant in the User Management. The goal
is to have a fully integrated lifecycle among the physical person with the corresponding user
information.
In SAP S/4HANA, the Business Partner is the leading object for the natural person and single
entry point to maintain Business Partner, Customer, and Supplier (formerly known as
Vendor) master data. This is to ensure ease of maintenance of the above master data and to
achieve harmonization between them.
Following this once central business user, the Business Partner in SAP S/4HANA is the
natural person which contains and persist the person, work center and communication
related data. The employee data can be retrieved from the following:
● SAP Success Factors
● SAP Human Capital Management
● Third-party System
In environment management, it is required that the main players in the process such as
Environmental Manager and Production Operator to have a business user in the system.
For further information about the installation and configuration of the app, please refer to the
official documentation in the SAP Fiori Apps Reference Library.
Important attribute is the business user, as user name you have to maintain the system user.
For further information about the installation and configuration of the app, refer to the official
documentation in the SAP Fiori Apps Reference Library.
LESSON SUMMARY
You should now be able to:
● Get familiar standard front-end and back-end system roles
● Get familiar with standard authorization objects
● Understand the specifics of system user setup
Lesson 1
Specifying different Configuration Objects 213
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Specify general configuration objects
● Specify process configuration
● Specify master data configuration
● Specify compliance requirement configuration
● Specify file-based reporting configuration
● Configure integration scenarios
● Configure business add-ins
Figure 307: General Configuration - Specify Allowed ABAP Function Modules in User-Defined Calculations
The input parameters for the function include a custom-defined backend function, followed
by a maximum of 5 input parameters. In the standard system, this function works with
variable structures or numbers. The output is always a variable structure.
Example: The function EHFND_IF_GREATER_THAN works with four arguments - INPUT_1,
INPUT_2, INPUT_3 and INPUT_4. If the value of the first argument is greater than that of the
second, the result is the value of the third argument, else - the result is the value of the fourth
argument. Each of the four input parameters can be a hardcoded number or a variable. You
can assign labels to the variables to help your process, for example, CHECK_VALUE,
LIMIT_VALUE, RESULT_TRUE or RESULT_FALSE.
Specify Roles
In this Customizing activity, you can define the roles that can be assigned to people
responsible for data collection (Environmental Technician), or people responsible for
scheduling data collection and managing other compliance scenario activities (Environmental
Manager). The standard system is delivered with examples in the following figure.
Note that the data entries for the data period, hourly, are collected automatically in the
system. For this reason, notifications for missing hourly data collections are not sent to
technicians. Otherwise, if any of the data entries are overdue, the notification is sent to the
environmental manager who is responsible.
To trigger the collection of daily, monthly, or yearly environmental data, we recommend that
you schedule the background job to run on at least a daily basis (for example, at midnight).
You can also schedule the job to run at shorter intervals, but as a prerequisite, prepare report
variants with the corresponding input parameters. If your business case features many
locations that span different time zones, we recommend that you schedule the background
job to run at shorter intervals (for example, every 2 hours). If you wish to trigger the automatic
collection of hourly data, schedule the report to run hourly.
This job processes amounts in chunks of 200. After a chunk is processed, the data is saved to
the database as a means of backup of the current state of the job.
To prevent the job from running too long and blocking the running of other jobs, there is a set
maximum processing time. When the set maximum processing time of 1hr is reached, the job
is stopped automatically, even if it is not complete.
determines whether it complies with the conditions required to run, and triggers the
calculations. This program is scheduled to run at defined time intervals, or on specific events
like value changes.
The recommended setup is to configure a periodical activation of the program for manually
recorded and automatically imported data, both on the event SAP_EHFND_AMOUNT_CNG
using the system client number as a parameter. To do this, you can create a variant
containing the following settings:
● Job activation period 59 minutes
● No test mode
● No tracing
● No continuous activation
● All types of calculation operations
In addition, the program enables you to carry out automatic calculations depending on the
nature of the input data. To improve the system performance, you can schedule separate
processing of automatic calculation operations either based on manually recorded data or
automatically imported data. To do this, you need to create separate variants of the program
and specify for processing the corresponding calculation operations.
whether they comply with the conditions required to run. The calculation is started only for
non-periodic input data sets, that do not have a triggering event specified to start calculating.
This program is scheduled to run at defined time intervals. The system calculates data
upfront, taking into account all input recorded until the next scheduled run.
● No continuous activation
● All types of calculation operations
In addition, the program enables you to carry out automatic aggregations depending on the
nature of the input data. To improve the system performance, you can schedule separate
processing of automatic aggregation operations either based on manually recorded data or
automatically imported data. To do this, you need to create separate variants of the program
and specify for processing the corresponding calculation operations.
Intervals must be defined for all Environment Management specific number range objects
shown on this slide. In addition, many objects from the EHS Foundation and Incident
Management are used and need to be defined to be able to create records in Environment
Management. Those are listed in the activity documentation.
The standard system is delivered with examples. You can identify the process definitions for
environment management by the technical key of the purpose (ENV_*).
When you want to sample, for example, chemicals, such as formaldehyde, carbon monoxide
or diesel fuel, you need a special detector tube attached to a sampling head and a pump with
an appropriate flow rate. When you want to measure noise, for example, you only need a
dosimeter.
When you select a sampling method type in the application, only these fields are displayed on
the screen that you have specified in the Customizing activity.
An environmental manager, for example, responsible for scheduling data collections. Persons
with this role can schedule the collection of measurement data from devices within the
industrial plant.
That is, if a given location does not contain assigned persons responsible for specific roles,
the system allows automatic assignment of such persons responsible from the superordinate
locations of the location hierarchy. By specifying roles in this activity, you enable the
inheritance and assignment of persons responsible that occupy these roles.
The configuration of this activity has an effect on all locations across the overall location
hierarchy.
The standard system is delivered with examples. The following roles are enabled for
inheritance across the location hierarchy by default in the standard system:
● Environmental Technician
● Environmental Manager
In this Customizing activity, you can enable or disable the integration for locations with the
Plant Maintenance (PM) component.
You can use the PM integration to import locations from PM and also to link existing locations
to PM technical objects.
Figure 321: Master Data Configuration - Schedule Jobs for Location Sync
This ensures that the location data is up-to-date, for example, in search screens, analytical
reports, and so on. If you do not use the report, or the system has not run the scheduled
report yet, you can open a location's master data to synchronize that location's data with PM.
Schedule the job to run as a background job once a day. If the PM data rarely changes, you
can schedule the background job to run less frequently.
Note:
The background job queries all integrated technical objects for changes. The
number of integrated objects can create additional load for the Environment,
Health, and Safety and PM systems and affect performance.
When you assign a position to a location, the position ID is stored in the location. The system
uses a function module to read the current organizational structure and evaluate it along the
configured evaluation path. The system returns the corresponding objects for the ID, such as
business partners and employees, at runtime.
Requirements
● You have integrated the system with the PA-OS system and the organizational structure is
available locally in the Environment, Health, and Safety system.
● You have entered evaluation paths in Customizing for PA-OS under Personnel
Management → Organizational Management → Basic Settings → Maintain Evaluation
Paths.
You can assign authorization groups to locations. The authorization groups are used in the
authorization checks for the location. Following this process, you can restrict access to
certain locations to specific users.
There are no separate authorization groups for the location structure. All actions performed
inside the location structure ascribe to the authorizations for the location.
Specify Forms
In this Customizing activity, you can specify the different forms of chemicals.
Specify Colors
In this Customizing activity, you can specify the colors of chemicals.
Specify Odors
In this Customizing activity, you can define odors of chemicals. You can select from the odors
specified here when you edit chemical data in the application.
To define a new limit type, you have to also adapt the coding of the Business Add-In used for
the execution of environmental limit checks.
By default, the standard system is delivered with the following limit types that can be used
and defined in the compliance requirement paragraphs:
● Upper Limit
Specifies a limit (threshold) that is used to ensure values of collected or calculated data that
are less than the specified threshold. In this case, the environmental limit will cause
exceedance if the value of the collected or calculated data is greater than the entered upper
limit value. If the value of the collected or calculated data is between the upper warning value
and the upper limit value, the environmental limit will only cause a warning.
● Lower Limit
Specifies a limit that is used to ensure values of collected or calculated data that are greater
than the specified threshold. In this case, the environmental limit will cause exceedance if the
value of the collected or calculated data is less than the entered lower limit value. If the value
of the collected or calculated data is between the lower warning value and the lower limit
value, the environmental limit will only cause a warning.
● Range
Specifies a range that is used to ensure values of collected or calculated data that are within
the span of the specified thresholds. In this case, the environmental limit will cause
exceedance if the value of the collected or calculated data is not within that range. If the value
of the collected or calculated data is within the range but close to the specified thresholds, the
environmental limit will only cause a warning.
If you want to define customer specific regulatory lists and use these lists in the compliance
requirement, you also have to enhance the following entities:
● Enhance the business object EHFND_COMPL_REQUIREMENT, by adding a sub-node for
the new regulatory list to the node, REGULATORY_LIST.
● EHFND_UI_REQ_CONT_REGLIST_TAB component configuration that represents the
regulatory list in the compliance requirement.
If you want to define customer specific regulatory lists and use these lists as data sources
(input data) for calculations, you have to additionally enhance the functionality of the
standard delivery.
You can define a limit for email attachment size and the lifetime of reports for download in
days for background generation of file-based reports.
You can set the Template flag for each file format. This flag indicates that the file format
supports template files.
Note:
You can use the Customizing activity Specify Export Profiles to upload a template
file.
For each specified file format, a BAdI implementation has to be available in the Customizing
activity BAdI: Generate Export Files.
The business object nodes selected for a data selection specify a tree-like hierarchy. You have
to select one lead business object whose topmost node, the ROOT node, represents the root
of the hierarchy.
Based on the ROOT node of the lead business object, you can select associations with child
nodes. For these child nodes, you can select associations with further child nodes. This first
selected child node will become the parent node of further associated child nodes. This way,
you can build up a node hierarchy.
For each associated node, you can select the fields from which you want to export data. The
data extracted from these fields are combined in one data selection.
Note:
To get a denormalized table in the generated report, only one node on each node
level is allowed to have a 1:n child node.
The data source types specified for data selection determine the source type of the
environmental data that you want to include in the file-based report.
You can assign more than one data selection in one export profile. The assigned data
selections specify the data to be extracted for the report.
In addition to the lead business object and the data selection, you have to specify the file
format of the resulting file. If the file format XLSX (Microsoft Excel 2007/2010) is used, the
export profile can contain an Excel template file that is used for the export. After the file
upload, the name of the uploaded file is displayed as the file name. This file name can be
changed later.
Furthermore, you can enter a threshold for background exporting to configure whether a
report is processed in the foreground or in the background.
Note:
The EHFND_EXPP authorization object can be used to specify which user should
be able to generate file-based reports based on the configured export profile.
Integration Scenarios
Integration Scenarios
You can use this component to integrate Environment Management with other components.
This enables you to access data in other components from within the Environment
Management applications and transfer data from Environment Management to other
components. In addition to simplifying work with the applications, integration also ensures
consistency by reusing existing data in different components. If you use integrated data
Business Add-Ins
The standard Business Add-Ins are specified in the Customizing relevant for the environment
management component.
The method does not contain default implementation and allows you to implement your own
business logic that handles the additional environmental limit checks. The method includes
the following import parameters:
Import Parameters
Changing Parameters
● RESULT - Validation Result Type
● MESSAGES - Message Text and Severity
This BAdI definition uses the IF_BADI_EHFND_REQ_ENV_LIMIT_EX interface and has the
following implementations:
● BADI_EHFND_REQ_ENV_LIMIT_EX
● BADI_EHFND_REQ_ENV_LIMIT_EX_LO
● BADI_EHFND_REQ_ENV_LIMIT_EX_UP
The method contains default implementation and allows you to implement your own business
logic that handles the additional import of compliance requirements. The method includes the
following import and export parameters:
Import Parameters
● IR_T_REQUIREMENTS
Export Parameters
● ET_MESSAGES
● EV_SUCCESSFUL_IMPORT
This BAdI definition uses the IF_BADI_EHFND_REQ_IMPORT interface and has the following
implementation:
● BADI_EHFND_REQ_IMPORT
The method contains default implementation and allows you to implement your own business
logic that handles the additional parsing of compliance requirements. The method includes
the following import and change parameters:
Import Parameters
● IV_FILE_CONTENT
Change Parameters
● CR_T_PARSED_REQUIREMENTS
● CT_MESSAGES
This BAdI definition uses the IF_BADI_EHFND_REQ_PARSING interface and has the following
implementation:
● BADI_EHFND_REQ_PARSING_XLSX
The method contains default implementation and allows you to implement your own business
logic that handles the import of regulations from external content providers, the parsing of
these regulations in the environmental management system, and the creation of compliance
requirements out of the regulations data.
The method includes the following import and changes parameters:
Import Parameters
● IV_XML_CONTENT
Change Parameters
● CT_RESULT_MESSAGES
● CV_SUCCESSFUL_IMPORT
● FINALIZE
The method contains default implementation and allows you to implement your own business
logic that handles the information sent to the content provider system with regard to the
finalization of compliance requirements at the system of compliance. The method includes
the following change parameters:
Change Parameters
● CT_RESULT_MESSAGES
● CV_SUCCESS
This BAdI definition uses the IF_BADI_EHFND_REQ_EXT_IMPORT interface and has the
following implementation:
● BADI_EHFND_REQ_EXT_IMP_RN
The BAdI is intended for multiple uses and is not filter-dependent. This BAdI is active in the
standard system and uses the following method:
● IMPORT_AMOUNTS
The method does not contain a default implementation and allows you to implement your own
business logic that handles automatic data collection. The method includes the following
parameters:
Import Parameter
● IT_AMOUNTS - Automatic Data Collection Import Table Type
Export Parameter
● ET_MESSAGES - Table with BAPI Return Information
This BAdI definition uses the IF_EHENV_ADC_IMPORT interface and has the following
implementation BADI_EHENV_ADC_IMPORT.
Figure 343: Business Add-Ins for Automatic Data Import using Files
The method contains a default implementation and additionally allows you to implement your
own business logic that handles the import of data. The method includes the following
parameters:
Import Parameter
● IV_MDEF_ROOT_KEY - Root instance key of the data collection definition
● IV_FILE_CONTENT - Binary representation of the imported file content
● IMPORT_ADC_AMOUNTS
The method contains a default implementation and allows you to implement your own
business logic that handles the information returned by the data import. The method includes
the following parameters:
Export Parameter
● EV_RESPONSE - Return messages of the import procedure in JSON format
This BAdI definition uses the IF_EHENV_ADC_IMPORT_XLSX interface and has the following
implementation BADI_EHENV_ADC_IMPORT_XLSX.
Figure 344: Business Add-Ins for Data Checks and Calculations 1/2
Figure 345: Business Add-Ins for Data Checks and Calculations 2/2
The method contains a default implementation. It allows you to implement your own business
logic that handles the check of environmental data and prepares that data for calculation. The
method includes the following import and changes parameters:
Import Parameters
● IT_KEYS - Table with amount root keys
Change Parameters
● CT_MESSAGES - List of system messages in T100 format
This BAdI definition uses the IF_EHFND_AMOUNTS_CHECK interface and has the following
implementations:
● BADI_EHENV_AMOUNTS_CHECK
This BAdI is used in the environment management component of Environment, Health, and
Safety. You can use this BAdI to enhance the standard functionality when you execute a
forecast of environmental emissions.
The BAdI is intended for multiple uses and is filter-dependent. For more information about the
standard settings (filters, single or multiple uses), see the Enhancement Spot Element
Definitions tab in the BAdI Builder (transaction SE18).
This BAdI is active in the standard system and uses the IF_EHENV_EMISSION_FORECAST
interface. This interface contains a GET DATA method that uses the following parameters:
Importing Parameters
● IT_SOURCE_UUID: Identifying parameter that ensures correct data selection.
● IV_USAGEPERIOD: Data period (hourly, daily, monthly, and so on) for past and future data.
● IV_SUBJ_COMP_KEY_REF: Subject reference key for a component (optional).
● IV_SUBJ_COMP_TYPE: Subject type for a component (optional).
● IV_PAST_FROM, IV_PAST_TO: Date range for narrowing down the data selection of past
data.
● IV_FUTURE_FROM, IV_FUTURE_FROM: Date range for narrowing down the data selection
of future data.
Exporting Parameters
● ET_FUTURE_RESULTS: Predicted data, calculated for forecast purposes.
● ET_PAST_RESULTS: Collected data for past periods.
Returning Parameters
● RT_MESSAGES: Error, warning, and success messages during the GET DATA method
execution.
As of 1909 FPS01, this BAdI is delivered with 2 examples BAdI implementations (Latest Delta
Extrapolation and Double Exponential Smoothing implementation). You can use them to
create your own BAdI implementations.
LESSON SUMMARY
You should now be able to:
● Specify general configuration objects
● Specify process configuration
● Specify master data configuration
● Specify compliance requirement configuration
● Specify file-based reporting configuration
● Configure integration scenarios
● Configure business add-ins
Lesson 1
Understanding the Current Availability of the Solution on SAP Cloud 247
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Get an overview of the Cloud Solution/Innovations
Innovations Overview
With Environment Management in SAP S/4HANA Cloud 2111, SAP delivers new features for
the emissions management process.
The following innovations can be highlighted:
● The use of data classifiers in sampling activities and location aggregations
● The use of new Manage Environmental Reports - Environment Management app to
support Corporate Carbon Footprint
● Changes to an IAM object
Figure 348: Use of Data Classifiers in Sampling Activities and Location Aggregations 1/2
Setting a data classifier to the data records received from these activities can help to easily
filter through data records and keep them apart.
The data classifiers can be used to support the processes of monitoring, reviewing, and
reporting emission information.
Figure 349: Use of Data Classifiers in Sampling Activities and Location Aggregations 2/2
The example (in the figure above) shows aggregated data that can be used to classify the
result of the total carbon dioxide equivalent for scope 3 - the use of solid products, but also in
the calculation of the total amount of scope 3 emissions.
It provides a framework for creating summary reports that can serve as guidance regarding
how you create environmental summary reports. These reports can be used to fulfill legal and
internal reporting requirements. Customers can create environmental reports and get a
summary of the available environmental data in the system.
In addition to reports containing current environmental data, customers can also make up a
snapshot of projected environmental data based on the setup of compliance activities for a
future period.
The app provides currently only an example template for managing greenhouse gas reports to
support the creation of a Corporate Carbon Footprint.
The Manage Environmental Reports - Environment Management app supports you in the
following activities:
● View a list of existing environmental reports in the system
● Shortlist reports by applying various filter criteria
● Create reports using a predefined template
● Delete generated reports
● Download report files
The environmental reports can be created using a predefined template. Customers can
prepare and generate greenhouse gas report files for the following:
● Emissions of carbon dioxide, methane, dinitrogen oxide, and carbon dioxide equivalents
● Yearly emission data sets in unit kilograms (kg)
Based on the greenhouse gas report form, the report file can be generated based on the
selected criteria (location type first and second level).
This requires a check to the business roles and the business catalogs assigned to them. It
should be ensured that the restrictions, included in the business catalogs, are set correctly to
allow the users to use their business apps as needed.
Figure 354: Changes to Identity and Access Management (IAM) Objects (1/2)
Summary
You should now be able to outline the new features for the emissions management process
that can support the creation of the Corporate Carbon footprint in Environment Management
in SAP S/4HANA Cloud 2111.
LESSON SUMMARY
You should now be able to:
● Get an overview of the Cloud Solution/Innovations