No "valid from" date inherited to specifications

[Former Member]

Hello Team,

Please guide me in the below issue from client in EHS-SPCIFICATION

"We inherit data from a template specification to a target specification. When we change values in the template specification with a change state, the values in the target specification are changed as well, without taking care of the valid from date of the change state.

An example:
Template specification has a value YYY in value assignment XXX. This value is inherited to a target specification. The template specification value is changed with a change state with a valid from date of 2016-01-01.
The inherited value in the target specification is changed as well. But when we open the target specification with a valid from date of 07-01-2015, it shows the values that were changed in the template specification with a valid from date of 01-01-2016.

Step1: A newly specification created on 05-25-2016.:

Step2:1 inheritance maintained

Step3:The template specification inherits supplier address data to the specification.

Step4:A new change number is added with Valid from date 05-27-2016 . With this change number, the inheritance template is changed from 001000000648 to 001000000649

Issue: Wrong data inherited

When jumping back to the specifications creation date (05-25-2016), the inherited data in the value assignment is wrong as below. It shows the supplier values that were inherited on 05-27-2016. We expect to see the values that were inherited on 05-25-2016.

Thanks in advance,

Karthik

[christoph_bergemann]

Dear Karthik

a.)  please provide status of release of your SAP system

b.) please explain if you have activated business functions (some are having relation to "inheritance process")

c.) the one screen seesm to contain a "customer developped" enhancement. We can not judge here (screen named "Change numbers")

Honestly. You have chosen the "most complex" approach to maintain data in EHS which one can think about.

PLease check e.g.

Step 4 is not clear to me. I try it in "my words"

1.) you have a specification

2.) you add an inh. tample and target spec

Overall: I assume you did not overwrite value on target spec.

So looking on target spec using change number (key date !) in past: no data should be found. But there is data (but which is valid in future in comparison to "key date/chaneg number)

=> this seems to be not ok; therefore: Start OSS dialog

I would expect: if you use out put variangt "EXCEL; "Valuation" etc. wiht key dat in past for traget spec you will find "same" result (as in Cg02 maintenance mode)

Can you please do the following: can you use in hit list both specs (source and target) and execute the "change log" (starting from the date)? the change log can be viewed using menu entries (refer to SAP help). On the toP i recommend to execute this report (for sourc and target spec)

RSSCD110 (check online help: Creation of Change Documents for Specifications - Specification Management (EHS-BD-SPE) - SAP Librar...

Report is explained there; you need to analyze this on "table" level (including ESTRH, ESTVH, ESTVA etc.) and to check what the system has done; and what not.

C.B.

PS: YOU SHOULD NOT USE INHERITANCE IN COMBINATION WITH CHANGE NUMBER (YOU CAN DO BUT ON YOUR OWN RISK (not from technical point of videw (even we discuss here may be OSS correction) but according to my experience. for end user teh chaneg number is no easy ot understand and in combiantion with inheritance I would never ever try to do it...

The handling of change numbers as such is "complex"; but in combination with the "most complex" functionality as "inheritance" it can only be a disaster

PS: IT is important to know status of release etc. as there are some changes done by SAP here

[Former Member]

Respected,

Very much thanks for your guidence on the issue.

With your expertise advice, the issue is seems to be complex & sholud be table level analysis.So we are escalating the issue to SAP help desk.

With SAP comments, I will repost the solution whenever recieved.

Thanks & Regards,

Theja

[christoph_bergemann]

Hello

can you explain better your sentence:

"Step4:A new change number is added with Valid from date 05-27-2016 . With this change number, the inheritance template is changed from 001000000648 to 001000000649"

Here i have an issue in understanding the steps you have used but exactly this is the " trick" to look in more detail

You have a source spec, you have a target spec. Now you have set up an "interitance" using template 1 between source and taregt

These are my questions:

1.) did you "exchange" the inheritcante template using the change number?

2.) or did you just "enter" data on source spec using the change number?

As mentioned: you have generated a "customer view" on use of "change numbers"; but this can be misleading.

Using a change number you can maintain data for a spec; but you need not to do it as well. It is "not a good idea" to "display" if or if not a change number was applied; the reason is "simple". Even knowning that an change number was applied: nobody knows in whcih context you have used this change number

But I would like to ask you do execute a "parallel check" and provide feedback on reasult

PLease do the following

1.) generate two new specs (one you can call source and the oher you can call target)

2.) For "target": pleass use REAL_SUB as type and for source please use REAL_GRP

3.) Now assign the "REAL_GRP" using "reference" to the "REAL_SUB" (not inheritance !) (data flow REAL_GRP => REAL_SUB)

4.) maintain in the "REAL_GRP" some data as e.g. "color = yellow"; Nowon REAL_SUB level you should get the iinformaiton "yellow"

5.) look for a change number valid in the future

6.) select REAL_GRP using the change number. Change the collor to e.g. "red" using the change number

Now please look for effects on REAL_SUB: Use "current date" as key date,. Now it should show up "yellow". Then use key date as the date of change number used (e.g. tomorrow) and check the data on real_sub: Now you should see (with this key date) red

The reason is: I analzyed the ue of change numebrs in EHS long ago and I am not sure if it will work proeprly in "reference" situation. If the "Reference topic" is working, then we need to dig deeper for the "inheritance" topic

But to help you i need more details what you have done (maintenance scenario).  In inheritance you have the "on top" complexity that you have a "template" used to "inherit" the data

C.B.

[Former Member]

Dear C.B,

Actually I am an associate support for QM/PP. As this issue has been assigned on me , with lack of expertise, I have come to SCN help.

Whenever the client get back with the solution proposed ,I will re post .

Regards,

Karthik.

[christoph_bergemann]

Hello

can we assume that the problem is solved? If so: please close thread.

C.B.