How come table based value assignment is showing number upto 27 only for any specific VAT  and not making entries for the rest values . If some class has more than 27 char , the system is cutting upto 27 and not populating the rest .

any suggestion ?

Hi Experts,

We have created so maný custom BO(busisnes objects) in BOPF in ECC and which are not specific to any Module like EHS or TM.We want to bring these BO to BW intead of their related tables for BW reporting purpose.

Could you please let us know if there is any way to extract these BO to BW?

Thanks in Advance,

Nageswar. 

Specification (CG02) Administration Data (at the specification header)

reports Whole Specification changed by and changed on.

Performance Assistant (Help) on Whole Specification Changed On reports:

---------------------------------------------------------

Date of Last Change to Specification As a Whole

Key date on which the specification was last changed.

Except for changes to the header data, the system takes all data that

relates to the specification into account, such as changes to:

Identifiers

Assignments of regulatory lists

Value assignments

Components

User-defined texts

Notes

The key date is specified when the specification workbench is started.

It

is not necessarily the same as the current date.

To determine the date of the last change to the specification in a

customer-defined program you can read out the specification time stamp

using function module EHSB_TMSTMB_READ_TIMESTAMPS, or you can follow

the

instructions in SAP note 874191.

The date of the last change to the specification is always set to the

key

date on which the specification was last processed. This is not always

the date of the last change to the specification (see SAP Note 874191).

--------------------------------------------

We are not able to 1) find SAP Note 874191 or function module

EHSB_TMSTMB_READ_TIMESTAMPS

SAP and T.A. Cook are delighted to announce the International SAP Conference on Environment, Health, and Safety Management on November 3-4, 2016, in The Hague, The Netherlands. This conference will be part of the larger International SAP Conference on Extended Supply Chain that brings together six co-located conferences:

• International SAP Conference on Supply Chain
• International SAP Conference for Manufacturing
• International SAP Conference on Product Lifecycle Management
• International SAP Conference on Portfolio and Project Management
• International SAP Conference on Environment, Health, and Safety
• International SAP Conference on Asset Management

Attendees have the opportunity to move freely across all six conferences, which will be packed with workshops, business focused customer case studies, keynotes, live demos, microforums and much more. Over two information-packed days, this conference will equip you with news on the latest innovation from SAP, as well as real-life customer case studies and expert industry insight. The unique agenda format allows you to meet with business leaders and learn from a diverse range of SAP customers, such as Akzo Nobel, Siegwerk Druckfarben, TaTa Steel and Reliance to name but a few.

Hi Experts,

In process foundation configuration while defining the process we maintain the PCO class to the Process Variants, this is linked to the corresponding PCBO, for Example: PCO Class CL_EHHSS_PCO_INC_ACTION_PM the corresponding PCBO reference is EHHSS_PROC_CTRL_INC_ACTION, you can see this in process definition check reports.

Where is this reference between the PCO Class and correcponding PCBO maintained?

Hi,

Had few questions around MSDS as part of EHS Module.

1. Wanted to know whether emailing MSDS is standard functionality or custom code in SAP?

2. Will this functionality be available in SAP S4 HANA as a standard functionality?

If there is any other insights on MSDS, it would be very helpful to understand standard functionality around MSDS.

Thank you.

Sanket

Hello All

Does RDS( Rapid Deployment Solution) have SAP EHSM?

Thanks

Dear EHS Community members,

I have a requirement. EHS system is already in place. SVT is currently used.  EHS has to integrate with SAP GTS

May I request you to give following clarifications

What stage volume tracking is happening , when I create a purchase order at that point of time whether tracking happens

If that tracking happens, whether it will get updated in table CCRCT_CO . Also, Is it possible to transfer volume tracked into GTS

in the case for depreciating volume from license

Scenario - Import

Create PO

License maintained in SAP GTS with quantity limit

Substance tracked for the material maintained in EHS side

The missing link here is, the volume tracked for that particular transaction how it will transfer to GTS side

I am not able to find this information, if that not happens, it means, Is it not possible to EHS relevant licenses for volume depreciation in GTS side

I checked in the forum, for one query answer like this... GTS will check only OK / Not OK means whether transaction can proceed if the following criteria satisfied

Registration completed with authorities

Tracking happened in GTS or not (can't see depreciation of quantity after transaction completed. )

Can anybody clarify my query related to volume depreciation? Version we are using 10.1

Hi,

How to use FM EHSB_TMSTMP_READ_TIMESTAMPS properly to get some "date/time etc."

Like to. Change whole specification data in admin data.

Thanks

Satya

Introduction

Because of thread : Property Tree Value Assignment may be it is time to discuss the EHS standard data model. Please check as well this very good document: Important compositions in EH&S and how they are used

Check as well: SAP EHS DISCUSSIONS !!!!: SAP EH&S Data Model - Use of Compositions

You will find many other threads asking question: what is a "PURE_SUB"/"LIST_SUB" etc. Please just use search options in SCN to find such threads. You will find helpful information of many kind. At the end of this document some references are collected discussing SAP EHS standard model (topics of many kind).

The standard data model of SAP EHS classic is described here: https://help.sap.com/saap/sap_bp/EHS_ERP605_Global/Documentation/EHSM_DATA_MODEL_605_EN.ppt

History/State of the Art

Based on the input of many chemical companies the SAP EHS standard data model was developped and will be improved in the future if there are e.g. legal needs to do so. E.g. one need in the last years was the REACh and the GHS regulations etc.

The SAP standard delivers the "STANDARD" property tree and the "OBSOLETE" property tree. These are the core once to discuss in this document.

On the top SAP delivers a number of identifiers etc. and other customizing stuff which can be used to start an EHS project. On the top SAP delivers as well "Content" (other companies do the same). This content include e.g.:

• Phrases

• Layouts to generate SDS/MSDS

• Rulesets (e.g. to support data generation for supporting the SDS/MSDS process)

• and other stuff (like regulatory content)

   

   

   

Therefore: any of these "content" pieces can be used only if the SAP EHS Standard Data model is used. If you deviate from that you will get problem in using these "on top" options.

Property Tree STANDARD

This tree combines the "Best practise" value assignment types/properties which are needed to support many of the subsequent EHS processes (e.g. SDS/MSDS/Label generation, DG topics, etc. etc.). This tree is represents the "full" scope of the SAP EHS standard data model regarding value assignment types/properties. It is very common to prepare special property trees which support the user better to maintain data related to SDS/MSDS etc.

Property Tree Obsolete

This tree combines "old properties" which are now "obsolete". Mainly either because regulations has changed or because of the fact that the use of the properties is limited etc.

Rating/Validity Areas

As well SAP delivers standard validity areas and ratings.

Identifiers

Same is true in context of identifiers (e.g. NUM, CAS and other stuff)

Other customizing

On the top SAP delivers standard set up for component type, specification types etc. etc.

Conclusion:

You should not delete SAP default customizing. If you are looking for to use SAP content you should not change the standard data model.

Options to extend EHS

You can add on top new "objects" with out any risk using customizing options which are used in SAP EHS-BD.

Examples are:

• substance authorization groups

• substance nature

• specification category/type (new categories should only be added if you have understood the EHS data model !)

• Rating

• Validity area

• Component type

• Property tree

• New value assignment types/classes
• etc.

Substance authorization group

The substance authorization group can be used mainly to "group" specifications. The set up is done mainly in such a way that authorization rights can be administered easily. E.g. if your company is organized by "branches" you can simply use terms as: "Food", "Feed", "Pharma", "Waste" etc.  Any specification belong to one branch can be created in the corresponding substance authorization group. The used terminology should follow to a creation extent the organisation of the company acting; you are completely free to here for set up.

Any specification must be set up in one authorization group.

Substance nature

The substance nature can describe on first glance the "chemistry" involved; it is used mainly as a search criteria but can be used different. Terms as: WASTE, SUB_POLY, SUB_NOPOLY etc. are quite common.

Specification header remark/note

You can maintain on specification level if needed one remark/note.  You can not maintain the information with a "language". This information can be used as well in inquiries in the system.

Identifiers

By SAP default: we have "Names" (NAM), "Numbers" (NUM) and "Formulars" (FRM) which can be used to describe the chemistry. The identifier can

• be longer than 132 characters
• can be language dependent (or not)
• can get a "check function " assigned (e.g. mostly used for numbers)
• can have no, one or more of one usages assigned
• can have no, one or more of one regulatory lists assigned
• one can maintain more than one identifer (e.g. you can have many "NAM, SYN")

Identifiers are one of the core data elements in EHS and are used at many locations in the system (e.g. via identification listings) and are used very often in context of  WWI development. They are used quite often for inquiries in the system.

Restriction

The restriction can be used to "enhance" the access concept in one authorization group. This functionality is used very rarely.

Status

You can use the Status  sure that one "data collection" is checked and released by a responsible person. You can implemenent lot of check. By default a status net is delivered by SAP. The functionality is not used often; but it is used more often than "Restrictions".

Reference

As EHS started only "Reference" was supported. By using "Reference" you can easily inherit data from one specification to another. It is very useful option to support the users in maintenance actions.

Inheritance

With higher EHS versions "Inheritance" was shipped and can be used. The functionality of "Inheritance" is broader than "reference" but the idea is the same. You maintain one data element and reuse this information very often. Using Inheritance you can inherit identifier information as well; this is not possible with "Reference". You can inherit the data very "flexible" by using "groups of properties" etc.  But you need more experience in using this and you must understand nearly perfect the idea of the "inheritance template" topic.

Material Assignment

With the material assignment you link EHS world to the Material world. Therefore this information is a critical one. With this link all the subsequent processes in EHS are "enabled" (e.g. DG, SVT, GLM, Report distribution etc. You can assign materials in EHS but you can use MM to assign specifications as well. You can use e.g. as well BOMBOS interface to link EHS to logistic processes.

Value Assignment Types/Properties

Component type

In properties of type "Composition" you need the "component type" for data maintenance. Even considering that under some conditions you need not to maintain this information, this information can be a "key" part in your maintenance. E.g. for "Trade Secret" topic you can define one or more component types which canbe used to suport the "Trade Secret" topic.

Exeption value

The "Exception value" is part of the composition. It is used rarely but can indicate additional information on a component.

UOM

The "UOM" is part as well of the "composition". Here we have two pieces. One describing the "principle" part (is e.g. composition of type "weight" or not) and the "core" part. In most cases value as "%", "%0" are used to describe the concentration of the component in the composition

Specification listing

Here you "only" list a number of components. This option makes sense e.g. if you would like to define: chemistry which should not get in touch with the "whole" product; or you canlist components which are generated if the product is burning etc.

Source

By assigning a "Source" you can make clear, which source you have used to derive the data (e.g. Literature and if so which..)

Assessment

Assessment is a "mandatory" field; but in real life does not have practical value (in most cases). E.g. you can "assess" that the data is "valid", "proofed" etc.

User defined text

This option is used quite often in daily maintenance. By defining "text types" you can add additional information which are "such specific" that you can not (or will not) generate a phrase. On top: with higher SAP releases you can use this option to linkto a DMS etc. document; e.g. you could link to a "test document" in which the real test results are shown (e.g. density, flashpoint etc.).

Usage

The defintion of the "Usage" is one of the core tasks in EHS classic data management. You can steer with Usage:

• Access topics
• and print out in WWI reports
• and DG management
• and SVT
• and....

Usage is a combination of "Rating" and "Validity area". To a validity area one or more countries can be assigned. This is crucail in most case for WWI reports.

Class/Characteristic based data

Most of the "value assignment types" (may be 70%) are set up in such a way that there is a SAP EHS class assigned with one or more characteristics. These properties and their use belongs to the "core" pieces in EHS. You can have characteristics which are "phrase" based, does have a "regulatory list" assignment, are of type "Numeric" with or without UOM assignment.

Discussions about EH&S Data model/Other soures of information

Small list of threads (mainly EHS data model oriented) of many kind

Please use search option in SCN to look for similar topics

OSS Notes

Attached is a short list of OSS notes with relevance to "STANDARD" property tree/and or topics wiht SAP classes/characteristics. Section will be extended if needed

• 1375848

• 874508

• 774006

• 955194

   

   

Hi,

I'd like to add an additional tab with dynamic image at CG02 as shown below. Anyone done this before?

Hi Experts ,

Has anyone used these program for generating worklist so far ? What things can we achieve using these two programmes ? Can we  use this to triggger worklist for regenerating sds based on the informations which are changed in specifications ?  It seems with the definition it provides but not sure whether anyone has really implemented this to do the updates in EhS and  define criteria to run rules again and re generate SDS to make it compliant as per updated regulations ?

Regards,

Krishna

Need some expert help on this .

any idea on this ?

Dear Experts,

In my clients production system the Standard Attributes are missing to assign the relevant phrase sets. everything is fine in Dev and Qualily Systems.

Please help with your Valuable suggestions.

In Quality System it is present.

In Production system it is missing .

If I open "Industrial Hygiene and Safety" in work area, I am getting the fallowing error saying " Internal Program error (SAPLCBIH_LB15_DIALOG  SAPLCBIH_WAOO_ERROR_C1AX_CLDLG_OPEN 0)

Please suggest me the solution.

Regards,

Sheena.

Dear all

in online help we have this chapter:

Test for Confirmed Substance Quantities - Product Safety (EHS-SAF) - SAP Library

Looking in the system and checking online help this seems to be true:

Values as stored are handled as: "It is deleted every three months or 90 days when data is transferred from substance volume tracking. It is subsequently no longer available."

Question: is the "90 days" value established via a customizing parameter and if so which one? If it is not customizing: as we need to implement in any case customer specific BADI implementation: in which part of code (method etc.) is the parameter defined?

According to analysis of BADi and documentation in SAP: to use this functionality one must activate  Business Function LOG_EHS_CI_2 (e.g.  EH&S Continuous Improvement - Logistics - SAP Library)

As this is a Business Funcfion there you can not go back (it is not reversal)

=> is there somebody outside there which uses sucessfully the "Test for Confirmed functionality"? Which challenges you have detected to implement it?

C.B.

In SVT purchasing scenario we are trying to update the monitoring tables for planned quantities(CCRCT_PUPL) and confirmed quantities(CCRCT_PU) respectively using program RREGCH_VT.

We are entering the below mentioned values in the selection screen.

• Regulatory list : REACH
• Scenario: PUR
• Radio button : Delta Run

We have found a badi badi_ehsrc_track_proc called inside FM: CBRC_PUR_DATA_FILLwhich updates the monitoring table. Also for the definition for the badi SAP has provided an example class: CL_EXM_IM_EHSRC_TRACK_PROC which we are referring for badi implementation.

Inside the class it refers to a method IF_EX_BADI_EHSRC_TRACK_PROC~DATA_FILL which actually updates the monitoring tables based on scenarios. The code written inside the method refers to a lot of check conditions which requires to be satisfied before the tables are updated with the values.

PROBLEM: 

Since we are running the report for PUR scenario the code checks whether the internal table X_PU_TAB or X_PU_DEL_TAB is not empty. But in our case no values are getting populated in either of the tables for normal purchase scenario.

We investigated on why the values are not getting populated in either of the tables. We found a FM: CBRC_PUR_MSEG_CO_FILL which is called inside the FM: CBRC_PUR_DATA_FILL.

But in debugging we were unable to find the root cause on why the condition tables were populated with no values. So we were unable to satisfy the check conditions inside the BADI implementation.

Kindly provide any pointers on this BADI implementation. Any sample code apart from that mentioned in the example classes would be really helpful.

Introduction

Currently state of the art in using EHS classic is SAP ERP Enhancement Package 8. Future state of the art will be version as delivered with SAP S/4 HANA. This document should talk about historic challenges and the future challenges as well.

Challenges in the past

If you check document SAP EHS Management for Beginners you will find some "historic" information how EHS has grown. For those who participated in this grow: they can really talk about "nice stories" how easy it was sometimes to jump from EHS version x to y (and later from SAP ERP version x to y). If you ask the IS managers in many companies they will give feedback as:

You would like install new Support Package ? Why ? And then you explain and then you do the job. But based on release change you will realize that sometimes this "simple"change was not easy as expected; you have had the need to do "afterwork" which was not planned. In some cases in good situation you realized the "issue" before Go Live to productive environment; sometimes 1 h after GoLive (TROUBLE....... ). So you have learned in lot in "updating/upgrading" EHS from one veriosn to the next (hopefully you have learned it; don't forget your "lessons learned)

Later story growed because of complexity. Then there was the need to start from e.g. EHS 2.7 to SAP Enterprise Version 4.7 (either in subversion 1.1 or 2.0). Once again: you have done your very best... but in many cases you have identified challenges in many areas. And depending on the fact at which point on time you "switched" to UNICODE in your system once again trouble was seen (sometimes). And as next step we have had SAP ERP 2004, then SAP ERP 2005...

Now things are changed once again. Now we have a "Business Function" "on board" which we can use (if needed). So this was more ar less a real major upgrade. And then the next challenges come up. With Enhancement Package 3 we have seen for the frist time some Business Function in EHS area. Now we have Enhancement Package 8 and the numbers of Business Function increased once again (but no new function in EHS).

Then in parallel SAP started new approach and delivered SAP EHSM (officially called: Component Extension for SAP EHS Management). A big new step for SAP (and the customers).

Reason is simply: if you check now the current version of EHSM then you need to decide: should I start with "new stuff" or should I use "old stuff". For those who are in the situation that you have not used old functionality: start with EHSM ! For those who use the old ones: think about to migrate ! and prepare your self.

Reason: be prepared for S/4 HANA

S/4 HANA

If you check discussion http://scn.sap.com/community/chemicals/blog/2016/07/06/strategy-update-on-product-safety-and-stewardship-solutions-from-sap

this seems to be clear:

from time to time SAP will deliver a new S/4 HANA version (currently one per year). Per version some of the old EHS functionality will be modernized and can be used then in full "HANA mode" (sorry for this new term). Roughly end of 2020 we can expect that most of the EHS classic is modernized and available completely in S/4 HANA. In the meantime you can use SAP EHS in "compatibility mode" if needed (and you are still using S/4 HANA).

So the challenges are here more or less the same as coming from may be SAP Enterprise 4.7 and switching to SAP ERP 2005; because of less of experience: we can not judge today how "easy" the transformation will be; but we can assume that per version challenges might be there (and as in the past: each variant of change might have its own challenges)

So be prepared, and prepare your self to get ideas about S/4 HANA installations (topic of e.g. hardware, software components to be used etc.).

As with old SAP version we have seen initiatives as "mySAP ERP" which "modernized" the GUIs..

With S/4 HANA once again new approach will be used: SAP FIORI. Here as well you should check: are you prepared ?

What will come next?

In most cases until 2020  you as consultant work in EHS on:

• handling changes in regulations (and per year we have many)
• SAP landscape optimization projects
• and other potential projects of many kind and changes as well of many kind to be implemented by whatever reason
  

At least before 2025 you should check (if needed): am I ready to move to S/4 HANA?

But in parallel you should check SAP communications to be ready if the challenge will come: the migration to S/4 HANA

Hi All,

I have a requirement to get the details of the properties of a specification like regulations,physical properties etc. in a report.

please help me to get the values of the properties.

For example, if you have the TSCA list in the regulation, i need to get the entries of that.

I tried with the FM C1F2_SUBSTANCES_READ_WITH_REF. But it is not working.

Appreciate your help.

Thanks,

Clara.

Dear all

based on SAP note 1040070:Restrictions in substance volume tracking

this restriction is stated:

Delivery schedules in purchasing

But no indication is given for the "Sales and distribution"  part.

Do you know about the "Sales&Distribution" part?

C.B.

Hi,

I need help on SVT EXP delivery scenario i was configured for delivery scenario and i have some doubts on related filed and tables.

I need to track delivered quantities to Europe (Finished product is not registered only Raw materials using registered need to track RM)

which field i can us for delivery scenario

Table       field

LIKP          ?

LIPS          ?

VBPA         ?

VBUP        ?

MKPF        ?

MSEG        ?

If 50 deliveries are created per how can i that this delivery is related to my tracking substance if answer from SVT flat from MM, they we can determine that in SALES ORDER level,

I maintain Z Specification composition in legal composition and A,B,C,D present in that and i maintain registered quantity legal entity and regulation in component level and i just assigned the material to Z specification.

My question to track shall i maintain compostion components as list_sub or pure_sub.

Next thing when i entered  CBRC20 given regulation as REACH and executed(witch out giving scenario) it is automatically showing the IMP scenario for Purchase and Purchase quantity is automatically updated ....now i need to change monitored values to EXP and delivery scenario which configuration i need to do for that or shall i maintain any environmental parameters for that.

please help why i'm getting IMP scenario in CBRC20 as default and how can i change that to EXP.

Thanks

Satya