Hi all,
Today we received an interesting question on version management of the SDS documents in EH&S.
Our client has a large number of generation variants.
When some data is modified in the substance, it is likely that not all relevant SDS documents will be regenerated at the same time.
let's assume the following order of events
* populate substance Z with data
* generate SDS for generation variant A (and release it - v1.0)
* do a major update (1) of data on substance Z
* generate SDS for generation varant A (and release it - v2.0) => changes should be marked
* generate SDS for generation variant B (and release it - v1.0) => as it is the first release, no changes should be marked
for as far as I know, this is pretty much standard
Now, continuing this logic....
* do a major update (2) of substance Z (mark changes from previous release as no longer relevant)
* generate SDS for generation variant B (and release it - v2.0) => new changes (update 2) should be marked
* do a major update (3) of substance Z
* generate SDS for generation variant A (and release it - v3.0) => old changes (update 1) should no longer be marked, recent changes (2 and 3) should be marked
* generate SDS for generation variant B (and release it - v3.0) => old changes (update 2) should no longer be marked, recent changes (update 3) should be marked
I have the impression the SAP logic is not soffisticated enough to handle such requirements.
did any of you meet a similar requirement (and if so, were you able to solve it?)?
Looking forward to any suggestions on how to tackle this requirement
Kind regards,
Luk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.