
The increasing importance of sustainability reporting is a major trend in the business world, and regulations like IFRS S2 (International Financial Reporting Standard S2) on climate-related disclosures are a key driving force.
Navigating the complex and evolving regulatory landscape and identifying the right tools and processes can be a challenging task for organizations, highlighting the need for clear guidance and effective solutions.
This blog aims to show how to leverage the power of SAP Green Ledger and SAP Group Reporting for comprehensive sustainability reporting. This includes connecting the Data Mapping apps to SAP Green Ledger, mapping SAP Green Ledger data to the SAP S/4HANA Group Reporting table ACDOCU and importing greenhouse gas emissions data to streamline compliance with regulations like IFRS S2.
SAP Green Ledger is an innovative solution designed to bring the rigor and precision of financial accounting to environmental data. It allows companies to capture granular environmental data at a transactional level, providing a comprehensive and auditable view of their environmental impact.
SAP Group Reporting is SAP’s strategic solution for consolidated financial reporting. It is designed to help organizations efficiently and accurately consolidate financial and environmental data from multiple entities into a single, unified view. This is essential for meeting legal and regulatory requirements, as well as for providing management with a comprehensive overview of the group's financial and environmental performance.
SAP Group Reporting Data Collection provides a suite of apps within SAP Group Reporting designed to streamline the process of gathering and preparing data for consolidated reporting. Among these, the Data Mapping apps bridge the gap between diverse data sources, such as SAP Green Ledger, and the standardized structure required by SAP Group Reporting.
To connect the Data Mapping apps to SAP Green Ledger as a data source, an OData version 4 destination is created in the SAP BTP Cockpit, the central web-based administration interface for the SAP Business Technology Platform (BTP). This destination then serves as the source instance in a Data Mapping definition, enabling data extraction, transformation, and loading (ETL) from SAP Green Ledger into SAP Group Reporting.
Investors are increasingly incorporating environmental, social, and governance (ESG) factors into their investment decisions. They want to understand how companies are managing sustainability risks and opportunities, as these can significantly impact long-term financial performance.
Regulators around the world are introducing mandatory sustainability reporting requirements. IFRS S2 is a prime example, setting a global baseline for climate-related disclosures, but other regulations are also pushing companies to provide more detailed sustainability information. Important international frameworks include the Global Reporting Initiative (GRI) which provides a comprehensive framework for broader sustainability reporting beyond just climate and the Sustainability Accounting Standards Board (SASB) which offers industry-specific standards focused on financially material sustainability information.
To learn more about IFRS S2 (Climate-related Disclosures), go to the ISSB website.
In addition to these international standards, regional and national regulations are also emerging, such as the EU's Corporate Sustainability Reporting Directive (CSRD), which mandates more detailed sustainability information for many companies operating within the EU. This complex landscape requires companies to be adaptable and informed about the various requirements they may face.
Sustainability issues, such as climate change, can pose significant risks to businesses. By reporting on these risks, companies can better manage them and mitigate their potential impact. Sustainability can also create new opportunities for businesses, such as developing innovative green products and services. Reporting on these opportunities can help companies attract investment and drive growth.
Meeting the requirements of IFRS S2 and other regulations demands accurate, reliable, and auditable data. Estimates and fragmented data sources are no longer sufficient. Companies need robust systems and processes to collect, manage, and report on their environmental performance with the same rigor as financial data.
By prioritizing data quality and implementing appropriate systems, organizations can confidently meet regulatory requirements, enhance stakeholder trust, and gain valuable insights into their sustainability performance. This is where SAP Green Ledger becomes invaluable, providing the necessary foundation for accurate and auditable environmental data.
SAP Green Ledger empowers companies to move beyond basic sustainability reporting and gain a deeper understanding of their environmental footprint. This granular data can then be used to drive more sustainable business practices, improve resource efficiency, and meet stakeholder expectations for transparency and accountability.
Here are some key aspects of SAP Green Ledger:
To learn more about SAP Green Ledger, go to the SAP Green Ledger product documentation page.
SAP Group Reporting provides a robust and comprehensive solution for consolidated financial and environmental reporting. Its tight integration with SAP S/4HANA, real-time capabilities, and comprehensive functionality make it a powerful tool for organizations looking to streamline their consolidation process and gain valuable insights into their financial and environmental performance.
Here are some key aspects of SAP Group Reporting:
To learn more about SAP Group Reporting, go to the go to the SAP Group Reporting product documentation page.
The Data Mapping apps within SAP Group Reporting Data Collection simplify the often-complex task of integrating data from disparate sources, ensuring that the necessary information is accurately and efficiently transferred into the SAP S/4HANA Group Reporting table ACDOCU for consolidation.
Here are some key aspects of the SAP Group Reporting Data Collection Data Mapping apps:
To learn more about SAP Group Reporting Data Collection, go to the SAP Group Reporting Data Collection product documentation page.
SAP Green Ledger integrates environmental data into core business processes, primarily within SAP S/4HANA. Connecting to this data involves exposing data from those systems via OData (Open Data Protocol).
OData is an open standard for creating and consuming data APIs (Application Programming Interfaces). It simplifies the way applications interact with data by providing a uniform way to request and manipulate data over the web. OData is like a common language for data exchange.
OData is widely used in SAP systems and is a key technology for data integration within the SAP ecosystem and beyond. It is especially relevant in scenarios like this one, where you need to connect data from an SAP system (containing SAP Green Ledger data) to other applications or services in the SAP Business Technology Platform (BTP).
SAP Group Reporting Data Collection supports OData versions 2 and 4, with the SAP Green Ledger scenario using version 4.
To learn more about the Open Data Protocol standard, go to the OData website. https://www.odata.org
SAP Business Technology Platform (BTP) is SAP's unified, enterprise-grade platform for innovation and integration in the cloud. It is designed to help businesses become intelligent, sustainable enterprises by providing a comprehensive set of services and tools for developing, extending, and integrating business applications.
To make SAP Green Ledger data available for use in other applications and services within BTP, we leverage OData services. Here is a general outline of the process:
1. Exposing SAP Green Ledger Data as an OData Service in the Source System:
This configuration step takes place directly in your SAP Green Ledger system where the data resides.
2. Creating a Destination in SAP BTP Cockpit:
Once the OData service is exposed in the source system, you need to create a destination in BTP to establish the connection.
Figure 1: GHG destination configuration in the SAP BTP Cockpit
To learn more about how to configure destinations for OData custom connections as source instances for Data Mapping, go to the SAP Group Reporting Data Collection Administration Guide.
3. Using the SAP Green Ledger Destination in Data Mapping apps:
With the destination configured, you can now use it in various BTP services, like the Data Mapping apps to extract, transform (Define Data Mapping app) and load (Run Data Mapping app) the SAP Green Ledger data into the SAP S/4HANA Group Reporting table ACDOCU.
In your Data Mapping definition, when defining the source system, select the source type OData Custom Connection, select the SAP Green Ledger destination you created in the SAP BTP Cockpit, e.g. “GHG”, as a source instance. The Data Mapping apps will use the destination's configuration to connect to the OData service and retrieve the SAP Green Ledger data.
Figure 2: Data Mapping source definition
After selecting a source type and instance, you are connected to the data source, e.g. SAP Green Ledger. You can then apply source filters to narrow down the data range for extraction, such as greenhouse gas categories in tons for a given company, fiscal year and fiscal period.
Figure 3: Data Mapping source filters
The final mandatory step in creating a valid Data Mapping definition is the upload of a mapping file. This file, in Microsoft Excel format (.xlsx), specifies the mapping rules governing the transformation of input (in this case SAP Green Ledger) dimensions to output (SAP S/4HANA Group Reporting table ACDOCU) dimensions.
For your convenience, a pre-built template mapping file is available in SAP Note 3524284. This template streamlines the process of importing greenhouse gas emission data from SAP Green Ledger into the SAP S/4HANA Group Reporting table ACDOCU using SAP GRDC Data Mapping apps. While you can create your own mapping files from scratch, the template can save you time and ensure a smooth import process.
Figure 4: Data Mapping file metadata
The Metadata tab lists the available input (I) and output (O) fields for the data mapping. The input fields originate from SAP Green Ledger and are accessed via the OData API. The output fields correspond to the fields in the SAP S/4HANA Group Reporting table ACDOCU.
The other tabs are used to define how these input and output fields are mapped to each other.
Within the mapping file, you can transform the extracted data using filters, functions, and formulas (using a syntax similar to Java).
Figure 5: Data Mapping file measures
Mapping is essential when the input dimension values, e.g. SAP Green Ledger accounts, do not match the output dimension values, e.g. SAP S/4HANA Group Reporting financial statement items.
Figure 6: Data Mapping file accounts
If the values are the same, you can map them directly without any transformation.
Figure 7: Data Mapping file GHG dimensions
After uploading your mapping file into the Data Mapping definition, the system validates it for errors. Only valid mapping definitions can be selected in and run as Data Mapping jobs.
Figure 8: Data Mapping file upload and validation
Now that you have defined the data mapping, which governs the extraction and transformation of data, you can create a Data Mapping job to generate the mapped data and import it into the SAP S/4HANA Group Reporting table ACDOCU. This process involves several key steps:
1. Creating and Running the Data Mapping Job:
Figure 9: Data Mapping job creation
Figure 10: Data Mapping job run
2. The Data Mapping Process in Action:
When the job runs, the following actions occur:
Figure 11: Data Mapping job statuses
3. Monitoring and Logging:
The Data Mapping job run generates two essential logs:
Figure 12: Data Mapping import log
4. Optional Traceability Log:
For more detailed analysis and troubleshooting, you can optionally generate a traceability log. This log provides a comprehensive view of the data flow, including:
Figure 13: Data Mapping traceability log
5. Verifying the Data in the ACDOCU Table:
After the job completes successfully, you can verify that the data has been correctly written into the ACDOCU table in SAP S/4HANA. You can use standard SAP S/4HANA reporting tools or queries to view the imported data.
Example:
After running the “Green Ledger GHG to ACDOCU” Data Mapping job, you can review the import log to ensure all greenhouse gas emission data for the specified company, fiscal year, and period has been successfully loaded into the ACDOCU table. You can then verify the data using transaction SE16H to directly view the table entries.
Figure 14: Greenhouse gas emission data in ACDOCU table
Once the SAP Green Ledger data, such as greenhouse gas emissions, has been successfully written into the ACDOCU table, you can unlock a range of powerful capabilities within SAP Group Reporting and beyond. Here are some key actions you can take:
1. Consolidated Reporting and Analysis:
2. Enhanced Compliance and Transparency:
3. Strategic Decision-Making:
By successfully importing SAP Green Ledger data into the ACDOCU table using SAP Group Reporting Data Collection Data Mapping apps, organizations gain a solid foundation for comprehensive and compliant sustainability reporting. This integration empowers them to analyze their environmental impact alongside financial performance, meet regulatory requirements like IFRS S2, communicate transparently with stakeholders, and make informed decisions to drive a more sustainable future. This seamless data flow not only simplifies reporting but also unlocks valuable insights for strategic sustainability management.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |