Dear ​@mvanrooijen, 

thank you for your question. The SAP LeanIX predefined Meta Model does not consider a relation between Data Object and Business Context (Process) see here.

What is the concrete need to introduce these relationships within SAP LeanIX? Our recommended best practice for modelling process dependencies is to use a dedicate process management solution (e.g. SAP Siganvio)

Possible solutions to visualize this would be:

1. You can model it form a application perspective. You can have Application A which supports Process A transferring a data object via Interface A to Application B which is supporting process B. Then you can create an interface that transfers the data object from Application B (related process to Application A or another Application C (which is related to Process A). This then can be visualised in a diagram with respective “drill down” and “show dependency” filters.
2. You create a 1:1 relation but model sub-processes (possible process steps) and respectively show the transfer of the same Data Object by separating the relation. 

Please let me know if you have any further questions! 

KR, Luca

LeanIX does not know the architecture element “business object”. I’ve circumvented this by introducing a “Flow” relation between business contexts and in diagrams linking a data factsheet with a subtype “Business Object” to that relationship.

In this specific usecase:
We have a team that delivers ideas to the architects. Those Ideas get turned into requirements. The requirements are then reviewed, refined and scored (MoSCoW) by the first team in collaboration with the department who delivered the idea, and then is sent back to the architecture department who uses it to draft an architecture vision that is presented to the solution architect as well as project portfolio management team.

I do not wat to deliver a detailed work instruction, nor specific process steps mapped to individual actors or roles. I do need to show the target operating model related to specific business objects and business contexts.

It is not related to applications, it is about governance, specific deliverables that get refined and then redistributed, sometimes back into the originating process.

Hope that helps.
.

 

Please stop marking this as the best answer.

Please note my reply from 3 days ago. 

Hi ​@mvanrooijen thank for the background.

I would suggest to use the initiative fact sheet here, potentially with the subtype “idea”.

You can then use SAP LeanIX automations to orchestrate the collaboration and assignment to different teams, in combination with surveys to enhance the data gathering and to-dos for team assignments.

The results can be captured in the respective fact sheet including all criteria and also decisions.

I hope this is what you are looking for, happy to get your feedback!

KR, Luca