Product Compliance in SAP S/4HANA Cloud, Public Edition 2302
In the processes needed for transporting and selling your products in many different countries/regions, we have specific fields, or document generation services that put texts in documents. A phrase is used in SAP S/4HANA Cloud, public edition for product compliance as a value for this type of specific field. To reduce the time and effort needed in keeping your company-owned phrases up to date, we enable with this new release better phrase maintenance through data synchronization. See in this blog how we continue our journey to increase key differentiators full of exciting innovations, enhancements, and features supporting your intelligent enterprise in the product compliance area.
To name just a few highlights:
- Compliance Data Foundation: Embedded regulatory content update
- Compliance Data Foundation: Ability to keep company-owned phrases in sync
- Product Marketability: Integration of supplier checks in purchase-information records and purchase scheduling agreements
- Product Marketability: Enablement of substance volume tracking for a compliance requirement
- Product Marketability: Evaluate bonded warehouse configuration during substance volume tracking
- Dangerous Goods Management: Dangerous goods tanks and bulk containers filling process
- Dangerous Goods Management: View regulatory data app
- Safety Data Sheet Management: Handling of multiple addresses and ability to print translations for multiple product names
- SAP Fiori Update
- … and more.
In case you do not need all the information below and just briefly want to get an overview of the release highlights, please watch this video with the top two key innovations:
Release video: SAP S/4HANA Cloud, public edition 2302 for Product Compliance: Top 2 key innovations.
In this blog post, I will walk you through the selected key highlights for product compliance of the SAP S/4HANA Cloud, public edition 2302 release.
Compliance Data Foundation: Regulatory Content Update
Companies are facing complex and specific regulations in the market. With the ability to validate regulatory compliance early in the product development cycle, you avoid the risk of having to rework formulations containing banned or restricted substances or, worse, recall products if they do not meet regulatory obligations. or customers’ requirements.
SAP delivers new and updated compliance requirements for Product Marketability, Safety Data Sheet Management, and Dangerous Goods Management, which you can use in your product compliance processes. You can view all SAP-delivered compliance requirements using the Manage Compliance Requirements app. To use the compliance requirements in your product compliance processes, you must activate the ones that are relevant to your own business and deactivate the ones that are not relevant using the Activate Compliance Requirements app. After activating a compliance requirement, you want to use, you must assign it to at least one compliance purpose using the Manage Compliance Purposes app.
Demo 1: Ensure proper and up-to-date product declarations with integrated regulatory content.
With the update and enhancement of the integrated regulatory content, you stay compliant with your product portfolio using the most recent regulatory updates. With the SAP S/4HANA Cloud, public edition 2302 release, SAP provides the following new and updated compliance requirements in the following solution areas:
In total 213 compliance requirements (Substance list check pattern) are available now
With SAP S/4HANA Cloud, public edition 2302 delivered:
- 42 updates of existing compliance requirement versions (SLC)
- 32 new compliance requirement versions (SLC)
- 6 new compliance requirements
Substance List Check
- GB REACH Annex 17 Status (Jul 2021)
- GB REACH Annex 14 Status (Jul 2021)
- GB PIC Status (Jan 2021)
Substance Volume Tracking:
- EU REACH Registration Status (Jan 2021)
- TR KKDIK Registration Status (Jun 2017)
- GB REACH Registration Status (Jul 2021)
Dangerous Goods Management
20 new or updated compliance requirements versions or lists with this release. In total 14 compliance requirements are available now
With SAP S/4HANA, public edition 2302 the following new data is included in the compliance requirement versions:
- CFR 49 as of July 26th 2022
- NZS 2021
The following new lists are included in the compliance requirement versions NCh382 2021, NOM-002-SCT/2011, NZS 2012, and SANS 2012:
- Organic Peroxides List
- Self-Reactive Substances List
The content is used when you classify unpackaged dangerous goods according to one of these dangerous goods regulations. When you select an organic peroxide or a self-reactive substance that is included in this content as the technical name, the system uses the name from the respective list. For this kind of substance, you can’t change the technical name but can display more information in the Select Technical Names dialog.
Safety Data Sheet Management
With this new release, we delivered:
35 updates of existing compliance requirement versions for embedded safety data sheet management
5 new compliance requirements for support of the data model:
- MY GHS Classification (Feb 2020)
- AL Components with OELs (Jan 2019)
- MY GHS Labeling (Feb 2020)
- CN GHS Classification (Oct 2013)
- CN GHS Labeling (Oct 2013)
2 new compliance requirements for occupational exposure limits:
- Albania Occupational Exposure Limits-Carcinogen, Mutagen (Aug 2014)
- Albania Indicative Occupational Exposure Limits (Aug 2014)
10 new compliance requirements for occupational exposure limits
Picture 1: Enable customers to rely on embedded regulatory content including phrases, graphics, and listed substances.
For more information about the SAP Content in Product Compliance, see the Foundation for Product Compliance in the Product Assistance for Product Compliance.
Synchronize Company-Owned Phrases
The idea of Phrase Management is to provide standardized texts, called phrases, to consumers. These consumers could be, for example, applications that provide value help for specific fields, or document generation services that put texts in documents. A phrase is used in SAP S/4HANA Cloud for product compliance as a value for specific fields, such as in the compliance requirement World First Aid Measures or simply, Colors. Phrases contain standardized text strings that are provided in different languages. These phrases are used for processes and documents needed for transporting and selling your products in many different countries/regions. Phrases are provided as SAP content for complying with regional, national, and international regulations. The Manage Phrase-Enabled Fields app, allows you to find phrases used in other SAP S/4HANA Cloud for product compliance apps as well as create your own phrases, optionally based on provided content.
With this new release, you can synchronize company-owned phrases to reduce the time and effort needed in keeping your phrases up to date. Additionally, it doesn’t matter which of the synced phrases you change, all others in the group are automatically updated. This improved management of phrases helps to avoid multiplied data maintenance for similar phrases. The company-owned phrase information can be used for output on documents like safety data sheets, labels, and reports.
Demo 2: Enables better phrase maintenance through data synchronization.
For more information about phrase management in Product Compliance, see Manage Phrase-Enabled Fields in the Product Assistance for Product Compliance.
Integration of Supplier Checks in Purchase-Information Records and Purchase Scheduling Agreements
In Product Compliance, you can assess suppliers for a product and set a status to indicate if a supplier is approved or blocked for this product. This information is used in a check that considers the status of the supplier assessment for compliance-relevant products during the creation of a purchase scheduling agreement. A new field on the item level and a new field on the header level indicate the status of the check.
If a product has been marked as relevant for compliance in the product master, the system checks the supplier assessment as a purchase scheduling agreement is created or edited. Depending on the outcome of this check, the system issues warnings.
If the status of the item is set to Blocked – By Supplier, the purchaser gets a message to block the item manually to prevent further processing of the item. For an item in status Blocked – Decision Pending, a compliance request is created for the product stewardship specialist to check the assessment of the supplier. If the compliance result of the assessment is positive, the document is unblocked.
With this new release, a supplier check is now integrated
- into purchase scheduling agreements
- into purchase info records
Picture 2: Improved supplier check for purchase scheduling agreements and blocking of items in case of supplier noncompliance.
For more information about the supplier check in Product Compliance, see Supplier Check in Purchasing Documents in the Product Assistance for Product Compliance.
For more information about the supplier check in Product Compliance, see Supplier Check in Purchase Info Records in the Product Assistance for Product Compliance
Enablement of Substance Volume Tracking for a Compliance Requirement
In many countries, regulations state that, above a certain quantity of chemicals and other hazardous substances, you must register with the authorities the maximum quantities of these substances that you plan to purchase, import, produce, sell, or export within a certain period. Substance volume tracking helps you to comply with the relevant regulations by recording the quantities of substances needing to be tracked that you purchase, import, produce, sell, or export. By comparing the recorded quantities with the limit values, the system can warn you in good time before a limit value is exceeded; if a limit value is exceeded, the system can also block the respective business process. This means you can ensure that you stay below the quantity limits.
With this new release, you can start the substance volume tracking process per individual compliance requirements and business processes in the Enable Substance Volume Tracking – for a Compliance Requirement app. By using this app, you can perform initial tracking from the beginning of the current tracking period. In addition, you can pause the tracking process in cases where the system workload requires this, and you can re-enable it again without losing data.
You can use this new SAP Fiori app Enable Substance Volume Tracking – for a Compliance Requirement to do the following:
- Enable or disable the SVT process for specific compliance requirements and business processes.
- Perform initial tracking from the beginning of the tracking period.
- Clear tracking data.
Picture 3: Ensure initial substance volume tracking for a compliance requirement.
For more information, see Substance Volume Tracking in the Product Assistance for Product Compliance.
Evaluate Bonded Warehouse Configuration during Substance Volume Tracking
A bonded warehouse is, for example, a secure warehouse in which goods are stored until customs duty is paid or the goods are cleared for export.
With this new release, you can flag a storage location or plant as a bonded warehouse for standard purchasing or standard sales business scenarios in the Manage Bonded Warehouses app. You can also define a period for which the bonded warehouse will be active.
Substances that are purchased or sold within the Compliance Requirement validity area and that are stored in a bonded warehouse for the active period of the bonded warehouse will be excluded from substance volume tracking.
With this new SAP Fiori app Manage Bonded Warehouses, you can create, edit and delete bonded warehouse entries for substance volume tracking. The entries can be valid for a specific period.
The key features are:
- Search for active bonded warehouses.
- View or edit bonded warehouse status.
- Create new entries.
- Export search results to a spreadsheet format (.XLSX)
Picture 4: Ensure accurate tracking of substance volumes in process scenarios involving bonded warehouses.
Support of Dangerous Goods Transported in Tanks and Bulk Containers
The process of classifying dangerous goods that are transported in tanks or in bulk containers is different from the process of classifying already packed dangerous goods. For packed dangerous goods, you need, for example, information about the packaging, such as the code and quantity of the dangerous goods package and information about the inner package. This information is not needed for tanks and bulk containers. In addition, when you transport dangerous goods in packages, the shipping quantity per package is fixed and defined by the size of the package. When transporting dangerous goods in tanks or in bulk containers, the amount of the product that is filled in the tank or bulk container can differ from shipment to shipment.
With this new release, the handling of dangerous goods transported in tanks and in bulk containers is supported. This feature supports the classifying and shipping of dangerous goods in tanks and bulk containers as follows:
- The new Tank or Bulk Container flag is introduced in the Specify Descriptions of Dangerous Goods Packages configuration activity. This flag indicates that the packaging is a tank or a bulk container. If you select a packaging for which this flag is set, the system displays only the description of the dangerous goods package in the Edit Packaging Details dialog. The code and quantity information of the dangerous goods package and data for an inner package is no longer displayed.
- The following new placeholders are delivered:
- These placeholders are resolved with the amount of the product that is filled in the tank or bulk container as entered on documents within the value chain, such as sales orders, delivery notes, and freight orders. The placeholders are used for the enclosure variants UN Portable Tank, Regulation-Specific Tank, and UN Bulk Container.
- The description templates are adapted to use the new placeholders when you select an enclosure variant for tanks and bulk containers.
Demo 3: Enhance basic dangerous goods compliance with a new filling process for dangerous goods for tanks and bulk containers.
Effects on Configuration
The Specify Descriptions of Dangerous Goods Packages activity is changed as follows:
- The new Tank or Bulk Container flag is added that indicates if the packaging is a tank or a bulk container.
- The descriptions in the plural for tanks are replaced with the descriptions in the singular because the shipment of multiple tanks is not supported.
- An entry for a bulk container is added in the singular for all descriptions.
In the Specify Descriptions of Dangerous Goods Packages activity, the configuration expert can view the new data. To do so, use the search function to open the following activity in your configuration environment: Specify Descriptions of Dangerous Goods Packages.
For more information about configuration settings, see Configuration Environment of SAP S/4HANA Cloud.
You can find more information about classifying dangerous goods in the Product Assistance for Product Compliance. See Assessing Dangerous Goods.
View Regulatory Data for Dangerous Goods
You, as a dangerous goods specialist, want to get an overview of the dangerous goods data for a specific regulation or a specific UN number. This overview of the available regulatory data can help you in the process of classifying your product. In addition, to a certain extent, it can replace your research in the printed versions of the dangerous goods regulations.
In the classification process, you can access the View Regulatory Data – Dangerous Goods app from the apps that you use to classify an unpackaged or packaged product according to a specific dangerous goods regulation. You can use the View Regulatory Data link to navigate to the View Regulatory Data – Dangerous Goods app, where you can view the delivered data for your selected regulation and UN number.
If you want to get an overview of the delivered dangerous goods data, or if you want to look for data for a specific regulation or a specific UN number independent of the product classification process, you can access the View Regulatory Data – Dangerous Goods app form the SAP Fiori Launchpad.
With this new SAP Fiori app, you can view regulatory data that is delivered with the compliance requirements that represent a dangerous good regulation. You can view details about the basic classification and enclosure-specific data. For organic peroxides and for self-reactive substances, you can view more information, such as the name as it is used on the corresponding dangerous goods lists.
If you open the app in two separate browser windows, you can easily compare data from different regulations.
If you access the app from the SAP Fiori launchpad you can use this app to:
- Search for regulatory data using various filters such as the regulation, the UN number, and the packing group.
- Select a regulatory data set to view the delivered regulatory details for the selected UN number and dangerous goods regulation.
If you access the app from the View Regulatory Data link in the apps in which you classify a product according to a dangerous goods regulation, you can use this app to:
- View the delivered regulatory details for the UN number and dangerous goods regulation for which you are classifying your product.
- Adapt the filters to view more regulatory data sets, such as for different regulations or for different UN numbers.
- Select a regulatory data set to view the delivered regulatory details for the selected UN number and dangerous goods regulation.
Demo 4: New SAP Fiori app to view all available regulatory data for a UN-number for each dangerous goods regulation.
For more information about how to check the delivered data for a compliance requirement, see Manage Compliance Requirements – Dangerous Goods.
Business Partner Multi-Address Support
In SAP S/4HANA, the Business Partner (BP) is the leading object to maintain Customer and Supplier data. The Business Partner data model enables you to maintain multiple, time-dependent addresses for each Business Partner master record and to assign these addresses to address usages.
But until SAP S/4HANA Cloud, public edition 2202, the Order-to-Cash documents can only use the customer’s standard address, and you need to maintain multiple BPs just because your customer has asked you to deliver your goods to different addresses.
SAP S/4HANA Cloud, public edition 2202 is now able to consume multiple addresses of a Business Partner that has a customer role. With this multiple address handling, you can increase the flexibility and efficiency with which the system handles business partner (BP) addresses in apps and documents (for example, sales orders, outbound deliveries, and billing documents) across sales, shipping, and some other parts of the system (for example, settlement management).
When you have activated the additional system capabilities in your configuration environment, sales and shipping apps can model and process the relationships between BPs (for example, companies) and their addresses in a way that more closely reflects the real-world legal and physical realities. Apps and documents across sales and shipping can then consume N addresses of the same BP master record that are assigned to one customer master record.
This new release enables the support of multiple addresses assigned to a business partner in processes for safety data sheet shipments.
Safety data sheet processes consider multi-address assignments if the feature Multiple Address Handling in SD Documents Using SAP Business Partner is activated for Quote-2-Cash processes.
This applies to the following safety data sheet processes:
Safety Data Sheet Shipment
- The Compliance Information – For Products app (F3226) provides a value help to select the address if you have selected a customer that has multiple addresses assigned when you send a safety data sheet manually.
- The selected address of the ship-to party of delivery is considered in the shipment request for safety data sheets.
- In the Monitor Shipments – Safety Data Sheets app (F4309) you can view the selected address of the safety data sheet recipient.
Maintenance of the Sender Address for the Safety Data Sheet
- The Manage Contact Data – Safety Data Sheets app (F4521) provides a value help to select the sender address if you have selected a business partner that has multiple addresses assigned.
International Address Version
- With this feature international address versions (IAV) are considered when printing addresses on the safety data sheet and on the cover sheet.
Final Safety Data Sheet Generation
- This feature supports the printing of the product name in English and in Chinese in section 1 on a Chinese safety data sheet if the product name is available in these languages in the product master.
Picture 5: Use of business partner data model and master records to provide multiple addresses with time-dependent validities.
For more information about activating the Multiple Address Handling in SD Documents Using SAP Business Partner feature, see the prerequisites in Multiple Address Handling in SD Documents Using SAP Business Partner.
For more information about the support of international address versions (IAV), see International Address Versions.
For more information about the apps related to this feature, see the product assistance for Product Compliance:
- Compliance Information – For Products (F3226)
- Monitor Shipments – Safety Data Sheets (F4309)
- Manage Contact Data – Safety Data Sheets (F4521)
Replacement of Technical Names with Generic Names
For specific UN numbers, such as 1993 (FLAMMABLE LIQUID, N.O.S.) and 1760 (CORROSIVE LIQUID, N.O.S), the proper shipping name has to be supplemented with the technical names of the substances that most predominantly contribute to the hazard of the dangerous goods.
When you classify unpackaged dangerous goods in the Classify Dangerous Good – Unpackaged Product apps, you can select a substance as a technical name. The system uses the technical name of the substance for the description of the dangerous goods. If the substance has no technical name, the system uses its company-specific specific company-specific name or the name of the assigned listed substance.
If you want to mask or disguise the chemical identity of a substance used as a technical name in the description of the dangerous goods, you can use this BAdI. This BAdI is called during the determination of the technical names for the dangerous goods’ basic description. With this BAdI, you can use the generic name that you’ve entered for this substance in the Manage Substances Compliance app to replace the technical name.
In the example implementation, the BAdI replaces the name of a substance used as a technical name with the generic name of the substance that you have entered for this substance in the Manage Substances Compliance app if the data entered in the Manage Confidential Business Information app meets the following conditions:
- The legal area of confidential business information is (World).
- The flag Use Generic Name is selected.
With this feature, the Business Add-In (BAdI) Replacement of Technical Names with Generic Names (BADI_EHDGM_DGDSCR_TECH_NAM) is delivered for key user extensibility. It replaces a technical name in the description of the dangerous goods with the generic name of a substance that you want to keep confidential.
Effects on Existing Data
If you implement the example implementation of this BAdI, the names of all substances that are entered as technical names in the dangerous goods classification are replaced with the generic names, provided that they are entered for the substance in the Manage Substances Compliance app and the conditions for the confidential business information are met.
You can find more information about technical names, generic names, and confidential business information in the Product Assistance for Product Compliance:
SAP Fiori Update
Horizon is making its way into further cloud products and S/4HANA Cloud 2302 brings along many UX improvements (auto-generated spaces and pages, reducing administration efforts here to almost zero, plus some cool new enhancements to the new My Home page, collaboration, and user assistance). This post shows many examples, and also explains our entry point strategy based on SAP Build Work Zone, SAP Start, and SAP Mobile Start, as well as some mobile UX and UI technology updates.
For more information, see the following blog post from Thomas Reiss
Watch the Replays of Our SAP S/4HANA Cloud, Public Edition 2302 Early Release Series!
We’ve hosted a series of compelling live sessions from the heart of the SAP S/4HANA Engineering organization. Missed the live sessions? Watch our replays on demand!
Among the replays, you can find a 45-minute replay, a presentation, and demos for product compliance as part of the SAP S/4HANA Cloud, public edition 2302 release as well as 19 other sessions on diverse topics like manufacturing, finance, two-tier ERP, SAP User Experience, developer extensibility, and many more. For more information on the SAP S/4HANA Cloud, Public Edition Early Release Series, and how to sign up for it, see this link.
Thanks for reading this blog post. Stay tuned!
- ‘Highlights of the SAP S/4HANA Cloud, Public Edition 2302 Release’ blog post here
- SAP S/4HANA Cloud, public edition release info here
- The Link Collection for Product Compliance here
- Latest SAP S/4HANA Cloud, public edition release blog posts here and previous release highlights here
- Product videos on our SAP S/4HANA Cloud, Public Edition, and SAP S/4HANA YouTube playlist
- SAP S/4HANA PSCC Digital Enablement Wheel here
- Early Release Webinar Series here
- Inside SAP S/4HANA Podcast here
- openSAP Microlearnings for SAP S/4HANA here
- Best practices for SAP S/4HANA Cloud, public edition here
- SAP S/4HANA Cloud, Public Edition Community: here
- Feature Scope Description here
- What’s New here
- Help Portal Product Page here