SAP Sustainability Control Tower (SCT) & SAP Envir...

Sai_Santhosh1 · 3 weeks ago

Introduction:

The SAP Sustainability Control Tower (SCT) is a comprehensive solution that enables holistic steering and reporting of sustainability efforts. It applies the SAP Business Technology Platform and core applications, integrating with existing systems to provide unique and effective sustainability solutions.

SAP Environmental Health and Safety management (SAP EHS) has been a key contributor to record, monitor and forecast environmental and social concerns like emissions, people safety, Risk assessments, change management, chemical management, compliance etc.

SAP EHS got abundant information on emission level tracking details and work-related incident details which is now major contributor to SCT.

Let us take a detail look on Sustainability solution SCT and how SAP EHS is integrated with it.

Sustainability Control Tower:

SAP Sustainability Tower (SAP SCT) uses existing system data for the area of sustainability for the fulfilment of ESG reporting requirements and activity management.

Typical data from SAP S/4 HANA, SAP ERP and other SAP solutions which can be used for SAP Sustainability Control Tower:

Air emissions, water emissions, CO2 emissions (SAP EHSM, SAP PFM)
Waste (SAP EHSM, SAP REA, SAP RDP)
Energy (SAP EHS, SAP MM)
Accidents, Occupational Health (SAP EHSM)
Financial Data, such as sales and pricing (SAP SD)
Produced Quantities, Purchased Quantities (SAP PP/PP-PI, MM, Ariba, SAP Concur, SAP Fieldglass)
HR such as Headcount (SAP HCM, SuccessFactors)

The goal is to use this data mostly automated, i.e. to automate the data collection required for the ESG-reporting.

Benefits of SAP Sustainability Control Tower

Integrated solution for sustainability
Predefined reporting, KPIs and integration scenarios
Automated, up-to-date, and auditable ESG-KPIs
Identification of potentials to improve sustainability performance
Support of activity management
High transparency and efficiency
Holistic decision-making based on interrelationships of financial, operational and sustainability performance
No technical gaps between operational SAP and sustainability systems
Digitization of sustainability

SAP S/4HANA Integration:

This chapter covers the configuration process for data replication in SAP S/4HANA, with two available systems for connection:

SAP S/4HANA On-Premises
SAP S/4HANA Cloud

SAP S/4HANA On-Premise

Set up the SAP Cloud Connector, which allows secure communication between the on-premises system and the SAP BTP subaccount.

Once the SAP Cloud Connector is set up, you need to configure the HTTP Destination Service on SAP BTP.

SAP S/4HANA Cloud

Configure the HTTP destination service on SAP BTP to enable data replication between the SAP S/4HANA Cloud system and the SAP BTP subaccount.

When configuring data replication for SAP S/4HANA, whether it be on-premise or in the cloud, the key difference lies in the process for connecting the SAP S/4HANA system to the SAP BTP subaccount.

Set up the Cloud Connector: This serves as a link between applications running on the platform and on-premise systems.

Procedure: SAP ABAP

After installing and starting the Cloud Connector, log on to the administration UI and perform the required configuration to make your Cloud Connector operational.

This includes logging on to the Cloud Connector, setting up connection parameters and an HTTPS proxy, and establishing a connection to the platform.

As soon as the initial setup is complete, the tunnel to the cloud endpoint is open, but no requests are allowed to pass. Go to Cloud to On-Premises and perform the Access Control setup, to specify the back-end systems and resources that can be accessed by your cloud applications (SAP ABAP)

For a back-end system, specify properties such as the Backend Type, the Protocol, the Internal Host, and the Virtual Host.

Note: The Virtual Host is used as the URL property for the destination configuration in the SAP BTP cockpit.

If the Cloud Connector is installed in an environment that is operated by SAP, SAP provides a user that you can add as member in your SAP BTP subaccount and assign the required role.

SAP BTP SUB-ACCOUNT: (Administrator – Any user with access)

When logging in for the first time, the following screen is displayed every time you choose an option from the main menu that requires a configured subaccount.

User Administration:

Create Cloud connector administrator - To edit the password for the Administrator user, choose Configuration from the main menu, tab User Interface, section User Administration.

If the internal landscape is protected by a firewall that blocks any outgoing TCP traffic, must specify an HTTPS proxy that the Cloud Connector can use to connect to SAP BTP. Normally, one must use the same proxy settings as those being used by your standard Web browser.

The Cloud Connector needs this proxy for two operations:

Download the correct connection configuration corresponding to your subaccount ID in SAP BTP.
Establish the SSL tunnel connection from the Cloud Connector user to your SAP BTP subaccount.

The Cloud Connector:

Key points on subaccount connection:

For <Subaccount>, <Subaccount User> and <Password>, enter the values you obtained when you registered your subaccount on SAP BTP.

Note

For a subaccount in the Cloud Foundry environment, you must enter the subaccount ID as <Subaccount>, rather than its actual (technical) name. As <Subaccount User> you must provide your Login E-mail instead of a user ID. The user must be a member of the global account the subaccount belongs to.

You can also add a new subaccount user with the role Cloud Connector Admin in the SAP BTP cockpit and use the new user and password.

The Cloud Connector does not yet support SAP Universal ID. Please use your S-user or P-user credentials for the <subaccount user> and <password> fields instead.

Enter a suitable proxy host from your network and the port that is specified for this proxy. If your network requires an authentication for the proxy, enter a corresponding proxy user and password. You must specify a proxy server that supports SSL communication (a standard HTTP proxy does not suffice).

These settings strongly depend on your specific network setup. If you need more detailed information, please contact your local system administrator.

The Cloud Connector now starts a handshake with SAP BTP and attempts to establish a secure SSL tunnel to the server that hosts the subaccount in which your on-demand applications are running. However, no requests are yet allowed to pass from the cloud side to any of your internal back-end systems. To allow your on-demand applications to access specific internal back-end systems, proceed with the access configuration described in the next section.

If you want to change the description for your Cloud Connector, choose Configuration from the main menu, go to the Cloud tab, section Connector Info and edit the description.

Establish Connections to SAP BTP:

As soon as the initial setup is complete, the tunnel to the cloud endpoint is open, but no requests are allowed to pass until you have performed the Access Control setup.

To manually close (and reopen) the connection to SAP BTP, choose your subaccount from the main menu and select the Disconnect button (or the Connect button to reconnect to SAP BTP).

The green icon next to Region Host indicates that it is valid and can be reached.
If an HTTPS Proxy is configured, its availability is shown the same way. In the screenshot, the grey diamond icon next to HTTPS Proxy indicates that connectivity is possible without proxy configuration.

In case of a timeout or a connectivity issue, these icons are yellow (warning) or red (error), and a tooltip shows the cause of the problem. Initiated By refers to the user that has originally established the tunnel. During normal operations, this user is no longer needed. Instead, a certificate is used to open the connection to a subaccount.

Note

When connected, you can monitor the Cloud Connector also in the Connectivity section of the SAP BTP cockpit. There, you can track attributes like version, description and high availability set up. Every Cloud Connector configured for your subaccount automatically appears in the Connectivity section of the cockpit.

SAP EHS INTEGRATION:

Restrictions include:

Only data for the listed substance carbon dioxide equivalent in metric tons is imported.
Of the GHG data classifiers in SAP EHS Management, a subset is supported.
Only approved, non-preliminary data is imported.
The data must be assigned to locations of type Site or Plant. These locations must have a Plant ID. It is used as the identifier for the business location hierarchy of the imported data. Ensure to maintain your SAP Sustainability Control Tower business location hierarchy with the required plants.

Import data from SAP EHS Management

Integrate with the SAP EHS Management, environment management solution to import activity data for greenhouse gas (GHG) emissions into SAP Sustainability Control
Here is a list of things that can be done with SAP EHSM & SCT integration:
1) Import your recorded GHG emissions from the SAP EHS Management system.
2) Associate your activity data with GHG scopes and sub-categories based on pre-defined classifiers.
3) Assign emission data to business locations in SAP Sustainability Control Tower.
4) Analyse emission data in the View Emission Dashboard app
5) Set and track your emission goals in the SCT Ambitions app.

Import GHG emission data with the Import Data from SAP EHS Management app.

The import uses your SAP S/4HANA configuration for data replication to import calculation results, data collections, and location aggregations using CDS views. Data is imported only for the given time period. The replicated data is transformed and stored into the emissions DPI.

Prerequisites:

SAP EHS Management, environment management is active in the SAP S/4HANA or SAP S/4HANA Cloud system.
Connection to SAP S/4HANA or SAP S/4HANA Cloud.
You have the following role assigned to you: SUS_SCT_EHS_Data_Manager.

With this app, you can transfer your emission data from the activities that you have recorded in SAP EHS Management, environment management, to SAP Sustainability Control Tower to use it in the GHG recording for your company.

Specifically, once imported, you can use the associated emission data with the sustainability metrics for GHG emissions across SAP Sustainability Control Tower and, for example, view and analyze the emission data in the View Emission Dashboard app.

You can select if you want to import yearly, monthly, or quarterly data.

Before importing any data, ensure that the data is complete in SAP EHS Management. Review the data after importing it into SAP Sustainability Control Tower.

What Happens with My Data from SAP EHS Management, environment management?

When the emission data from SAP EHS Management is imported, SAP Sustainability Control Tower uses the following information stored in SAP EHS Management to read the data:

The standard classifiers you have defined in SAP EHS Management, for example the data classifier Scope 1.
User-defined classifiers you have created in SAP Sustainability Control Tower for your activity types, for example, Heating.

These classifiers are then mapped onto the categories available in SAP Sustainability Control Tower to enable further processing of the data.

Example

We have created the following information in SAP EHS Management and want to now use it in SAP Sustainability Control Tower for GHG recording:

Standard classifiers: Scope 1, S1 Stationary Combustion
User-defined classifiers: Heating
Activity: Heating Building 1
CO2e Amount: 2,000 t

This information would be mapped to SAP Sustainability Control Tower as follows:

SAP EHS Management, environment management			SAP Sustainability Control Tower
Activity	CO2e Amount	Classifiers	Activity Type	Scope	Scope Category	Source Category
Heating Building 1	2,000 t	Scope 1 (standard)	S1 Stationary Combustion (standard)	Heating (user-defined)	Heating	1	1.1 Stationary Combustion	Stationary Combustion

One source for issues is a missing standard classifier. For example, for the activity of heating, you have maintained the user-defined classifier Combustion, however no standard classifier exists. In this case, the data will not get imported to avoid incorrect data from getting validated and recorded.

Another source for issues are data conflicts. A data conflict might arise due to mismatches between the used classifiers. For example, for the activity of heating, the standard classifier Scope 1 and the user-defined classifier Truck Transport are maintained, leading to a scope conflict. You can review this data in the Import Data from SAP EHS Management. You have then two possible options to proceed:

Recommended: You can choose to first resolve conflicts in the data and postpone the publication. Once you have corrected the entries, you can re-import the data.
You can start the validation of the successfully imported data and publish it. You can then fix any data with issues and once the next data import runs and is successful, you can start the validation in CPE. You have two options:
- Update: Existing values are updated with new entries.
- Create: New entries are entered into the system and stored.

Procedure:

Open the Import Data from SAP EHS Management application from your SAP Fiori launchpad and wait for the connectivity check to complete.
Select a period for importing data from Import Data from SAP EHS Management.
Start the import. The import status is published in the top bar in percent.
Once the import has run, you have different options to proceed depending on the import status:
- If the import has been Finished successfully, select validate data. You will then be navigated to the CPE environment to validate and publish your data.
- If the import has been Finished with Issues, you have two options. You can choose to Review Issues first and re-import the data or you can choose to validate data that has been successful and resolve any data with issues later.
- If the import has Failed, a message will provide you with more details on how to resolve the issue.

Sustainability Control Catalogue:

Below are Master data managed by Sustainability Control Tower with respect to SAP EHSM:

Emissions
Injury – Injury type and Severity
People – Injured Person, Body part, Absence/Restriction

Sustainability metrics can be used for recording actuals and targets. This allows you to understand performance in achieving a set of strategic ambitions for a particular metric. There are more than 40 sustainability metrics in SAP Sustainability Control Tower, such as employee wages and benefits, net investments, and water consumption.

With the app Manage Metrics, you can:

Configure sustainability metrics.
Set sustainability metrics you'd like to be ambitions for your organization, such as reducing greenhouse gas emissions, work related incidents etc.
Upload data to sustainability metrics.

In the overview section, you can find information on:

The number of available metrics.
The number of metrics that have data uploaded to them.
The distribution of metrics according to the areas environmental, social, and corporate governance (ESG), and economic.
The number of metrics with set ambitions for your organization.

Prerequisites:

On using SAP S/4HANA Cloud or SAP S/4HANA to upload data in the Manage ESG Data app for sustainability metrics based on financial records, ensure to configure the source system as a destination in your SAP BTP subaccount and that you have uploaded the required master data to SAP Sustainability Control Tower.

Sustainability Control Tower: Sustainability Metrics for EHS:
Gross GHG Emissions – Scope 1
Gross GHG Emissions – Scope 2 Market/Location Based
Gross GHG Emissions – Scope 3 Market/Location Based
Incidents per millions of hours worked
Work Related Fatalities
Work Related Incidents

Procedure: Administrator (User with Access to SMC):

In Sustainability Metric Catalogue, Sustainability metrics are uploaded with respect to status (data provided/no data), Area (Social/ Governance/ Economic/Environmental) and Ambition (Ambition set/ No Ambition).

Incidents per millions of hours worked:

The value of this sustainability metric represents the number of work-related incidents per million hours worked. It includes health and safety process data on incidents that have happened to workers.

Maintaining strong standards of health, safety, and labor rights can improve employee productivity and operational efficiency and enhance employee well-being. Working proactively in these areas of business will help identify and mitigate potential risks and it is increasingly required by law. Mental health and emotional wellbeing, as components of overall worker health and safety, are becoming increasingly important in driving innovation and delivering goods and services that are reliant on human capital. Organizations that invest in non-occupational medical and healthcare services would demonstrate to their employees that they care for and look after them. This would result in a purposeful, resilient, and growth-oriented workforce.

Calculation Methodology

Incidents per million hours worked = INJURY_TOTAL / (HOURS_WORKED /1000000)

Injury count = INJURY_TOTAL

Total hours worked = HOURS_WORKED

DPI to be Used

DPI - Data is uploaded using CSV files (also referred to as 'flat files') through the appropriate Data Provider Interface (DPI). DPIs define the structure of the data to be uploaded, and act as an interface to the system, allowing you to upload your data.

The sustainability metric "incidents per million hours worked" uses the following DPI:

Injury - measure "Injured" (ID_MEASURE: INJ_INJURED_PERSON) is used
People - measure "Hours worked" (ID_MEASURE: PPL_HOURS_WORKED) is used

Dimensions Related to Actuals

The calculation of the sustainability metric "incidents per million hours worked" does not use any domain-specific dimension.

Targets

Like other sustainability metrics supporting standard organizational structures, the data for the sustainability metric "incidents per million hours worked" is uploaded directly as ratio per period - per the organizational unit targets. These targets can only be uploaded for a defined leading hierarchy.

Work Related Fatalities:

The value of this sustainability metric represents the number of work-related fatalities. It includes health and safety process data on incidents (fatalities) that have happened to workers.

The metric describes number of fatalities as a result of work-related injury and high-consequence work-related injuries (including fatalities only). Maintaining strong standards of health, safety, and labor rights can improve employee productivity and operational efficiency and enhance employee well-being. Working proactively in these areas of business will help identify and mitigate potential risks and it is increasingly required by law. Mental health and emotional wellbeing, as components of overall worker health and safety, are becoming increasingly important in driving innovation and delivering goods and services that are reliant on human capital. Organizations that invest in non-occupational medical and healthcare services would demonstrate to their employees that they care for and look after them. This would result in a purposeful, resilient, and growth-oriented workforce.

Calculation Methodology

Number of fatalities = This calculation limits the measure incidents count by dimension injury severity (ID_INJURY_SEVERITY), Values: Fatal (3) where incidents count = INJURY_COUNT

DPI to be Used

The sustainability metric "work-related fatalities" uses the following DPI: Injury - measure injured (ID_MEASURE: INJ_INJURED_PERSON)

Dimensions Related to Actuals

The calculation of the sustainability metric "work-related fatalities" uses the domain-specific dimension ID_INJURY_SEVERITY.

Work-Related Incidents:

The value of this sustainability metric represents the number of work-related incidents. It includes health and safety process data on incidents that have happened to workers.

Maintaining strong standards of health, safety, and labor rights can improve employee productivity and operational efficiency and enhance employee well-being. Working proactively in these areas of business will help identify and mitigate potential risks, and it is increasingly required by law. Mental health and emotional wellbeing, as components of overall worker health and safety, are becoming increasingly important in driving innovation and delivering goods and services that are reliant on human capital. Organizations that invest in non-occupational medical and healthcare services would demonstrate to their employees that they care for and look after them. This would result in a purposeful, resilient and growth-oriented workforce.

Calculation Methodology

Number of incidents = This calculation limits the measure incidents count by dimension injury severity (ID_INJURY_SEVERITY), Values: all (1, 2 and 3) where incidents count = INJURY_COUNT

DPI to be Used

The sustainability metric "work-related incidents" uses the following DPI: Injury - measure injured (ID_MEASURE: INJ_INJURED_PERSON)

Dimensions Related to Actuals

The calculation of the sustainability metric "work-related incidents" uses the domain-specific dimension ID_INJURY_SEVERITY.

Conclusion:

The journey towards sustainability is fraught with numerous challenges that organizations must navigate. To effectively manage and overcome these challenges, companies need robust tools and systems. One such essential tool is the SAP Sustainability Control Tower, a core component of SAP Cloud for Sustainable Enterprises solutions. With an effective integration to SAP EHS and other existing SAP submodules, SAP SCT is now a game changer.

Thank You!

Regards,

Sai Santhosh. B