cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

How to manage Multiple Regulatory content data updates

ashish25bp
Participant
0 Likes
550

Dear Experts

Request your suggestions and comments on the following scenario.

EHS regulatory content data updates have not been done for past 2.5 years for some reason. The last SERC update was done was 1505 (1st release of 2015). Now the requirement has come to update all the SERC updates till now.

I have several questions on this:

  1. How many updates were missed during this lapse of time (Last was 2015 Ist version- 1505), where can I get the exact list?
  2. I dont see any option on market place to get the archived SERC updates for past period to check the delta changes, How can I get that.
  3. Most Important .....Do I really need to update all the versions before I load the latest 1711 SERC update. Is that a prerequisite?
  4. If so, what should be the ideal approach to do this whole activity? Is it possible to update all at a time in Dev, then all in QC & last all in Prod OR Each SERC updates, one after another, should be done sequentially in DEV, QC & PROD.
  5. Any major challenges for the above scenario?

Thanks

View Entire Topic
Mark-Pfister
Active Contributor
0 Likes

Hi Ashish,

How many updates were missed during this lapse of time (Last was 2015 Ist version- 1505), where can I get the exact list?

AFAIK there is no official list available - but you could ask SAP. Here a list I kept for myself:

  • 1711
  • 1708
  • 1705
  • 1702
  • 1611
  • 1605
  • 1608
  • 1602
  • 2015-2
  • 2015-1
I dont see any option on market place to get the archived SERC updates for past period to check the delta changes, How can I get that.

Here's the text from their latest slides: "SAP EHS Regulatory Content is available through SAP Service Market Place  Scheduled delivery date: November 22 nd , 2017 .  Please note: On Service Market Place the names of the latest published packages will end with “1711”.  Generally, you will find only the latest version on Service Market Place. Please always download it even your are not intended to install it. Some information are always required for later updates. Please note: Delivery of previous release via SAP Standard Support is not allowed."

If so, what should be the ideal approach to do this whole activity? Is it possible to update all at a time in Dev, then all in QC & last all in Prod OR Each SERC updates, one after another, should be done sequentially in DEV, QC & PROD.

You can do all updates in one system e.g DEV - test it there and then move to the next system, test there etc...

Any major challenges for the above scenario?

Since you don't have the content releases in-between you are missing on lot of related information. For example which OSS notes you need to install and other manual tasks you would have needed to do. It is very hard to compile the delta of what has changed for the business without these version.

Best

Mark