Skip to main content
Solved

L1 Applications - "Leave Empty" BCs and Orgs

  • June 28, 2024
  • 1 reply
  • 98 views
S
Forum|alt.badge.img
  • Shane
  • Royalty For Loyalty
  • 16 replies

I’ve searched documentation but cannot find guidance on the value vs effort of relating L1 applications to business capabilities and organizations. If an L1’s child applications (L2) are mapped appropriately to Business Capabilities and Organizations, why map L1 at all? The effort to do so is very duplicative and my users don’t want to do it. My thought is to “Leave Empty” these relations on L1 applications as it is effort without much value. What are your opinions?

Example: An L1 application like “SAP ERP” and child applications like “SAP ERP CO”, etc.

Best answer by Justin Swift

@Shane I would tend to agree that in hierarchical application relationships, the lowest level of application is the best one to manage the detail of the actual capabilities enabled/supported by the application.

In fact, in the LeanIX guidelines on Modelling SAP ERP 6.0 they show a diagram that indicates maintaining the relationship at the lowest level too,

Hope this helps validate your thinking.

    1 reply

    Justin Swift
    Forum|alt.badge.img+1
    • Justin Swift
    • Veteran
    • 186 replies
    • Answer
    • July 2, 2024

    @Shane I would tend to agree that in hierarchical application relationships, the lowest level of application is the best one to manage the detail of the actual capabilities enabled/supported by the application.

    In fact, in the LeanIX guidelines on Modelling SAP ERP 6.0 they show a diagram that indicates maintaining the relationship at the lowest level too,

    Hope this helps validate your thinking.


    Terms & ConditionsCookie settingsAccessibility statement