For past many years we are used to the way SAP ECC EHS – Dangerous Goods Management functionality works for managing the Dangerous goods checks, document generation. The way it is used, whether creation of Specification Data using Work bench or Filling the Dangerous Goods Masters, setting up of Product release or even Dangerous Goods Documents. However, with the release of SAP S/4 HANA 1909 Product Compliance, there has been a major shift in the way the Dangerous Goods Management is performed in the system. In this blog I would like to give a short overview of SAP S/4 HANA 1909 Product Compliance – Dangerous Goods management functionality and how it supports the functionality which has been offered earlier with better user experience and streamlined process.

Source: http://www.pexels.com

Overview Scenario:

The basic business scenario of carrying out the Dangerous goods check remains the same as when a sales order is created system checks for transport permissibility by determining the DG data for departure and destination country. When an outbound delivery is created necessary dangerous goods documents are generated.

There is no relevant flag suggesting the Dangerous Goods Indicator profile, the DG checks, DG Documents relevancy needed to be handled explicitly in S/4 HANA. Its consultant’s involvement on how to handle. Dangerous Goods relevancy is further declared during Unpackaged DG information, stating the material is relevant for DG check, by doing that system excludes the materials which do not require DG checks

We used to notice different types of dangerous goods checks performed like triggering general dangerous goods checks for availability of dangerous goods master etc. Followed by the general checks’ other checks like Poisonous by Inhalation, Mixed Loading Checks or even product release was used to be performed. Need and provisioning of such checks in S/4 HANA 1909 Product Compliance – Dangerous Goods, is a consulting assignment which depends on individual consultants understanding of business needs and how it needs to be set up in the system like setting up of segregation groups. The available checks include system performing checks during sales (sales order, sales contract, sales quotation) and delivery process and generation of documents with Dangerous Goods Information as a predefined text format in documents such as sales order, Contract, delivery note.

Master Data differences:

In ECC – EHS, Dangerous Goods Management, the main master data consist of Dangerous Goods Master, which is an aggregation of data from more than 16 tables information. This data is generated from either configuration data or specification master data consisting of Transport classification and UN LISTED Substance information. In case of S/4 HANA Product Compliance, SAP Delivers the compliance requirement containing dangerous goods management with Dangerous Goods lists. When an Unpackaged Product – Dangerous Goods is classified the relevant DG, lists are selected for a UN Number. Basically, the main master data for Product Compliance consists of Compliance requirement and Compliance purpose. For generating the Dangerous Goods master, we used to run DG filling whereas in case of S/4 HANA scenario it would be creation of Unpackaged Dangerous Goods information using the Dangerous Goods Mgmt. content provided by SAP. The whole concept of UN Listed Substance, Real Substance, Pure Substance, and associated filling is avoided for DG classification and generation of DG Master

There are more than 16 regulations which needed to be managed and it very streamlined master data. Variations to DG which are specific to organizations or company specific needed to handled separately in declarations. Company Specific DG requirements can easily be cloned with existing Compliance requirements easily and adopted to suit to organizations 

End to End Dangerous Goods Mgmt. Process:

Overall process consists of marking the Product Master as relevant for Compliance relevance. Once compliance is assigned basic compliance status is managed by declaring various compliance requirements to the product master, followed by Unpackaged Dangerous Goods Management. Compliance checks are integrated into different sales and delivery document processing like sales order or sales contract. Based on Compliance relevancy and Dangerous Goods Relevancy necessary checks are implemented. If the regulation needs the sales to be blocked due to missing dangerous goods assessment or DG not allowed, it would be blocked by the system or allowed with restrictions if suggested. Based on the status of individual line items, system checks the information at the header level of the sales order.

We usually see Product Structure differs from organizations to organization and it needs central handling. It needs a careful validation of features and modification of functionality by customization to suit to business needs. Further the existing business process needs to be updated to have a proper handshake between SDS Authors and DG Classification, like when composition is updated or GHS Classification is updated. Even such communications are manual in current scenario or with company specific communications outside SAP.

Conclusion:

To conclude the Product Compliance based Dangerous Goods Management is highly streamlined, independent functionality which do not depend on classic way of working around Substance Database. It might seem a dual management for SDS, Label authoring and DG Classification. DG classification is a specialized job requiring DG Expert. When you look at the organizations work processes on how they do DG classifications, it it not a either/or approach which is followed. Further, we witness for many organizations Dangerous Goods Management is relevant, however those do not wish to implement Substance management or enabling skeleton Dangerous Goods data. The Apps provided with the module are highly user centric and have very less onboarding requirements. Various apps available like Analysing Dangerous Goods management offers an incredibly good insight around regulatory view and the status of dangerous goods information.

At the onset of implementing this module seems to conflict with existing ECC – Dangerous Goods Management and organizations might visualize sticking to ECC – EHS Module of Dangerous Goods Management, rather it should not be the case. It is not required to discount this application for the non-availability of full functionality of Product Compliance Module. Similarly for handling Dangerous Goods using model in EWM or Transport Management is not assessed, which needs further evaluation. It is again with consultants expertise in developing a plan to aligning the SAP ECC EHS module and S/4 HANA 1909 Product Marketability to come up with plan of segregating the functionality to offer a complimentary view of these functionality for organizations which do not have full EHS requirements and slowly moving into next generation system of managing Compliance in years to come.

Thanks
Jayakumar

Disclaimer: The thoughts expressed are based on literature available in Internet, for exact applicability / timing of using the approach, reach out to your SAP contact.

Leave a Reply

Close Menu
%d bloggers like this: