cancel
Showing results for 
Search instead for 
Did you mean: 

Object Link between two specifications

former_member185558
Active Participant
0 Kudos

Hello ,

If I understand it right, if I use reference specification , referenced specification will get values from source specification for same value assignment type.

However we dont want that.

Is there any way I can bidirectionally link two specifications without any additional functionality (like object link).

Thanks in advance.

Niketan Maral

Accepted Solutions (0)

Answers (2)

Answers (2)

satya11719
Active Contributor
0 Kudos

Hi Niketan,

Bi direction means you want A to B and B to A .

No it is not all possible - and its meaning less why you want to that any business requirement.

Reference A->B

inheritance A->B->C

Inheritance - Specification Management (EHS-BD-SPE) - SAP Library

Reference - Specification Management (EHS-BD-SPE) - SAP Library

Thanks

Satya

former_member185558
Active Participant
0 Kudos

Ha ha ..meaningless is funny word. thanks for the answer by the way.:)

Niketan

christoph_bergemann
Active Contributor
0 Kudos

Dear Niketan

not sure if I understood your demand correct. Did you check "inheritance" option??

Currently i can not imagine  one case there you would like to inherit data block "A" from spec A to B and data block "B" from spec B to A

PLease explain your business case you are looking at

C.B.

former_member185558
Active Participant
0 Kudos

Hi Chris,

Thanks for the answer , we just want to link to specifications, for one specific business case.

I don't see need of disclosing more details for contractual purposes.

In general Spec A is to be linked to Spec B

and going to Spec A we need to know its linked it Spec B and vice a versa.

We can use classification may be or some other way (could be identifier)

more like DMS DIR object link to another DMS DIR

Thanks

christoph_bergemann
Active Contributor
0 Kudos

Dear Niketan

still no clue what you would like to get. Example:

You can create a LIST_SUB (e.g. NAM PROD water). THis LIST_SUB can be in many compositions of many REAL_SUB. So the "water" is linked to many other specs using "composition" relation.

But in EHS no "cyclce" is possible in compositions: That means A can contain B, But B can not contain A.

The "inheritance" option is once again a link; But the topic is "wording". You have always a "source" specification inheriting data to a target specification. So there are "link" clearly to each other but there is a data flow as well and this is only in one direction. And there is no useful tool available to do inquiries in EHS. All of the inquiries are deisigned as: If A is source and B is target you can look for. show many ans spec" related to "A"; but you can not do we other way around. Based on B you can not search for relation to "A".Same is true for reference

Referring to your example (use of identifier): You could define a identifier as "NAM SYN". If you have spec A then you can just link spec ID of B in NAM SYN and store it to A. And on B you do the same but maintain NAM, SYN with spec ID A

I have no clue about your business need. There was never the need to create such "relations" in EHS

But using identifiers you can do teh "search" and you will find result (in both directions)

C.B.

PS: no clue how you would like to achieve thsi with "Classification"; one other optione could be "using useer defined text" and maintain as with identifier; the clear con is: You can, in standard, not do an inquiry on content of userdefined text