Skip to Content
avatar image
Former Member

Documenting Mappings

Hi all,

I have to go back to my previous question from early 2015 (, where I described the issue with the mapping of the source and target attributes in a PDM.

Now we have the case, that business is expecting to have a similar information, but on LDM level.

What we have to document is a logic like this:

1) we have a source entity Entity1 with the attributes:

  • Entity1.Attribute1
  • Entity1.Attribute2
  • Entity1.Attribute3
  • Entity1.Attribute4

2) a source entity Entity2, with:

  • Entity2.Attribute1
  • Entity2.Attribute99

3) we have a Entity3 with the attributes:

  • Entity3.TargetAttribute1
  • Entity3.TargetAttribute2

The mapping Entity3.Attribute1-> Entity1.TargetAttribute1is a direct 1:1 mapping, for the Entity3.TargetAttribute2, business has defined the the following logic:

when Entity1.Attribute2 = 0 or Entity1.Attribute2 is NULL

then 0

else when Entity1.Attribute2 = Entity1.Attribute3

then when Entity1.Attribute4 in (select Entity2.Attribute99 from Entity2 where Entity3.TargetAttribute1 = Entity1.Attribute1)

then 2
else 0
else 0

We can of course put this logic into a business rule, attach it to the attribute Entity1.Attribute4 or put it into the comment for the mapping... but... the it's only a text. It will not show p in the lineage and impact analysis.

Does anyone has an idea, how to implement such a requirement, so that it's somehow visible in the impact and lineage analysis?

DMM is to far away from business users I believe....



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers