Using specification for GDSN attributes?

Question

We are planning to participate in Global Data Synchronization Network (GDSN).  For that additional master data must be defined and managed.
SAP does not provide standard solutions for this requirement.
We use EHSM for GLM and other functions.  We therefore have substances defined for materials.
We envision expanding the property tree to include GDSN related attributes which define the related material assigned.  Custom programs will be used to report the attributes as required.  The GDSN attributes are not required or related to GLM or other typical EHSM functions.
My question - would it be inappropriate or incorrect to use the specification database in this manner?  What would be the pro/con of this usage we need to be aware of?

Answer 1

Dear Richard
e.g. SAP EHS MANAGEMENT is used to push to others data from MSDS/SDS etc.
E.g. IMDS Customer and Supplier Collaboration - SAP Product and REACH Compliance - SAP Library
shows one example. In the area of REACH a lot fo more examples can ge listed. *** well there is a "IUCLIDE" interface etc.
A lot of regulations, industry bodies require exchange of data; e.g. check: Examples of Data sharing demands in SAP EHS Management using XML
So as long as the data is related to "EHS" (and does have some material significance) EHS is a good option to store the data and to use SAP EHS Management as the "source" for exchange the data wirth 3rd parties. A lot of IT solutions a possible. most common is the scenario SAPERP( with EHS) => SPA XI/PI => External software; other options arepossible as well.
What are the pros of using EHS?
a.) you can easily enhance EHS so that the data can be stored
b.) you can perform data loads in EHS (unsing IMport, OCC or Data Editor option)
c.) you can use EHS easily for inquiries on the data stored
d.) you can print the data in WWI reports
e.) you can share the data using options as mentioned above
The use of material classes is "limited" here
From my point of view:
You can store data in material classes
You can do uploads (using SAP standards but on the same level as with EHS)
You can exchange the data
You can proint the data using Smartform and other classic ABAP feature as well may be use Adobe integration
The "inquiry" to the data is possible as well but limited
In most cases: if you analyze data relevance for EHS > 90% of the data to be shared can be classified as "EHS" data.
At the end it is a company decision which solution you would like to use.
C.B.