SAP S/4HANa for Product Compliance Data Migration approach: Raw Materials - Bulk vs Packaged

[Paulo_Pinto]

Hello dear community, I need your insights and advice regarding this subject.

My customer is a group of Chemical Companies with several roles along the supply chain. The current scenario regarding purchased materials products is as follows:

1. Some materials/products are purchased in "true" bulk/unpackaged form. 

1.1. Of these, some of these are sold in the exact same "category" in which they were purchased, that is bulk/unpackaged. 

1.2. Of these, some are also sold and/or in different packages (of course these are different SAP materials/products, which are "produced").

1.3. Of these, some are exclusively sold in different smaller packages (again, of course these are different SAP materials/products, which are "produced"). 

1.4. Of these, some are used in the production of other materials (chiefly mixtures, some "articles (plastics) but there is also some production of new substances)

2. Some materials/products are purchased in packaged form, IBC's and other - without a clear "true" bulk/unpackaged material to refer to. This is my main worry.

2.1. Of these, some are also sold and/or in different packages (of course these are different SAP materials/products, which are "produced").

2.2. Of these, some are exclusively sold in different smaller packages (again, of course these are different SAP materials/products, which are "produced"). 

2.3. Of these, some are used in the production of other materials (chiefly mixtures, some "articles (plastics) but there is also some production of new substances)

Now my doubts are related to which is the best - or most advisable - way to migrate the raw material data in order to assure the most seamless go live as possible, especially regarding the materials/products purchased in "packages" without a clear or "true" bulk/unpackaged material.

(I'm trying to be clear about the scenarios, please ask for clarifications if needed).

Thank you in advance!

Paulo Sérgio Pinto

[Mark-Pfister]

Hello @Paulo_Pinto,

I understand that you want to use the new "S/4HANA for product compliance" solution.

As you indicated that you are migrating - please don't mind me asking what functionality of the new solution you want to use.
Please be aware that SDS Authoring, Labeling, and Substance Volume Tracking are not yet possible with the new solution.
However Dangerous Goods processes and product marketability checks are already working.

The good news is, that you can use the classic functionality until 2037 under S/4HANA - as long as you stay on release S/4HANA 2029.

Best

Mark

[Paulo_Pinto]

Hello @Mark-Pfister 

I'm implementing the S/4HANA for product compliance solution, on-prem, version 2023. Customer bought this product, along with EHS (new), and does not want to use the classic solution. 

I started with the Product Marketability and Chemical Compliance functionalities, which include SVT, that I understand is working in this version (?); that will be my next step in my approach, after I migrate/upload the master data needed to run the "pure" PMCC functionalities - as you can imagine this is an interesting challenge.

After this I will be implementing Dangerous Goods Management and only after I'll tackle SDS and Labelling, as my customer is least interested in these functionalities (for now). SDS Management I think it's fully operational, and from what I've been reading, SDS Authoring is also operational, although it might not be as mature as other non-SAP solutions the customer is using (and will require a substancial effort regarding master data). Labeling is operational as from 2023 versions, but it uses a third-party organization (with additional costs, for what I understand). 

Off course I might be misguided; in that case I'll appreciate some guidance towards the real state of affairs regarding SAP S/4HANA for PC.

Thank you for your remarks (they have me thinking about learning the classic solution as well!)

[christoph_bergemann]

Hello Paulo

I am sorry. Some of your assumptions are according to my understanding wrong

In SAP S/4 HANA 2023 SVT exists but can not really be used. Check the "Roadmap" explorer to get more insight here

The same is true for "DG" and to certain par of "SDS" as well

For SDS: you can use the tool (best knowledge !) to dipatch the SDS but you can not create a SDS. The "Label" generation will be done any how using a "Partner Solution".

As well: to get more insight for DG and SDS part: please check the roadmap.

On top: this blog might be of interest:

https://community.sap.com/t5/product-lifecycle-management-blogs-by-members/new-sap-ehs-management-fo...

and

https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/sap-quot-ehs-quot-product...

With best wishes

C.B