Clarifying License Cost Modeling: TCO Extension vs IT Component–Application Link Hi everyone,I'm working on cost modeling in LeanIX and I have a question regarding how to best represent license costs—especially in cases where a shared technology platform (e.g., SAP) supports multiple business applications.Context:SAP licenses are purchased centrally, but used across several applications (e.g., Finance, Procurement, HR). In LeanIX, I’ve already entered these costs on the IT Component–Application relation, since the licenses are tied to the SAP component. The Application TCO extension also allows me to enter license costs directly on the Application fact sheet, but this creates a duplication of cost data (TCO doesn’t use IT Component-Application relation costs)Questions:Should shared technical costs like licenses be entered in the TCO extension at the application level, or is it more appropriate to model them on the IT Component–Application link when the licenses are centrally managed and technically scoped? I know the TCO extension supports reporting costs per organ
