@prefix rdf: . @prefix rdfs: . @prefix xsd: . @prefix owl: . @prefix skos: . @prefix dcterms: . @prefix prov: . @prefix vann: . @prefix schema: . @prefix arch: . @prefix ap: . @prefix lmm: . @prefix : . ################################################################# # Model Declaration ################################################################# :LeanIXDocsExampleModel a arch:Model ; skos:prefLabel "SAP LeanIX Meta Model v4 — Documentation Example Landscape"@en ; dcterms:title "SAP LeanIX Meta Model v4 — Documentation Example Landscape"@en ; vann:preferredNamespaceUri "https://meta.linked.archi/examples/leanix-docs-example/" ; vann:preferredNamespacePrefix "lxdoc" ; arch:modelConformsToMetamodel ; dcterms:created "2026-08-16"^^xsd:date ; dcterms:modified "2026-08-16"^^xsd:date ; dcterms:creator "Kalin Maldzhanski"^^xsd:string ; dcterms:publisher "Linked.Archi"@en, ; owl:versionInfo "0.1.0"@en ; dcterms:description '''A small LeanIX workspace assembled from the examples SAP's own LeanIX documentation gives for each fact sheet type, wired together with all sixteen Meta Model v4 relationships and carrying the fact sheet attributes — status, completion, dated lifecycle phases, subscriptions and tags. Its purpose is to be validated, not admired: it is the data that exercises leanIX-shapes.ttl, which until now had nothing to fire on. It is deliberately small enough to read in one sitting. This is not an official SAP document, and SAP does not publish this landscape. What SAP publishes are the individual examples named below; assembling them into one connected workspace is this repository's doing.'''@en ; ## ─── Sources ─────────────────────────────────────────────── ## Every element name, every tag and every enumerated value below comes from ## one of these pages. Canonical URLs: the LeanIX documentation moved from ## docs-eam.leanix.net to the SAP Help Portal, and these are the targets its ## own 301s resolve to. dcterms:source , , , , , , , , , ; prov:wasDerivedFrom , , , , , , ; ## ─── What is sourced and what is illustrative ────────────── skos:editorialNote '''Read this before treating any value here as documented fact. Three tiers: **Sourced.** Fact sheet names are the examples SAP's documentation gives for each type, and each element below carries dcterms:source pointing at the page it came from — "SAP S/4HANA Finance" and "Salesforce Sales Cloud" for Application, "Customer Data Platform" for Platform, "Lead to Cash" for Value Stream, "PostgreSQL 15" and "Kubernetes cluster" for IT Component, and so on. The tag group "Application Hosting" with the values On-Prem, SaaS, PaaS and IaaS is the worked example on the IT component hosting page. The value sets — ACTIVE/ARCHIVED/BROKEN, RESPONSIBLE/ACCOUNTABLE/OBSERVER, and the five lifecycle phases plan/phaseIn/active/phaseOut/endOfLife — are fixed by the product and documented. The one lifecycle phase dated 2017-03-12 is verbatim from the GraphQL reference page's own response payload. **Illustrative.** Completion ratios, fact sheet identifiers, subscriber email addresses and every date except the one named above. The documentation gives no example values for these, so they are invented, and any reader treating them as SAP's would be wrong. They are here because the shapes constrain their datatypes and cardinality, and a fixture that omits them tests nothing. **Ours.** Which element relates to which. SAP documents that an Application supports a Business Capability; it does not say that "Salesforce Sales Cloud" supports "Customer Management". Every edge below is a plausible reading of the documented relationship types over the documented names, chosen to touch all sixteen relationships at least once.'''@en ; . ################################################################# # Strategy & Transformation # # Objective and Initiative examples: # https://help.sap.com/docs/leanix/ea/objective-modeling-guidelines # https://help.sap.com/docs/leanix/ea/initiative-modeling-guidelines ################################################################# :ReduceRunCost a lmm:Objective ; skos:prefLabel "Reduce IT run cost by 20% by 2027"@en ; skos:notation "lxdoc-obj-1" ; dcterms:type "Objective" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.75 ; . :ErpConsolidation a lmm:Initiative ; skos:prefLabel "ERP Consolidation Program 2026–2028"@en ; skos:notation "lxdoc-ini-1" ; dcterms:type "Initiative" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.6 ; ap:atLifecycleStage ap:PhaseIn ; lmm:hasLifecyclePhase :ErpConsolidationPlanPhase, :ErpConsolidationPhaseInPhase ; . ## The plan phase and its date are verbatim from the response payload on ## https://help.sap.com/docs/leanix/ea/reference/graphql-advanced, which shows ## lifecycle { asString phases { phase startDate } } returning ## phase "plan", startDate "2017-03-12". The phase token resolves to ap:Plan ## because ap:Plan carries a skos:closeMatch to the LeanIX lifecycle ## documentation anchor of the same name. :ErpConsolidationPlanPhase a lmm:LifecyclePhase ; ap:atLifecycleStage ap:Plan ; lmm:phaseStart "2017-03-12"^^xsd:date ; dcterms:source ; . :ErpConsolidationPhaseInPhase a lmm:LifecyclePhase ; ap:atLifecycleStage ap:PhaseIn ; lmm:phaseStart "2026-01-01"^^xsd:date ; ## illustrative . ################################################################# # Business Architecture # # https://help.sap.com/docs/leanix/ea/business-capability-modeling-guidelines # https://help.sap.com/docs/leanix/ea/organization-modeling-guidelines # https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines ################################################################# :CustomerManagement a lmm:BusinessCapability ; skos:prefLabel "Customer Management"@en ; skos:notation "lxdoc-bc-1" ; dcterms:type "BusinessCapability" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.9 ; . :OrderProcessing a lmm:BusinessCapability ; skos:prefLabel "Order Processing"@en ; skos:notation "lxdoc-bc-2" ; dcterms:type "BusinessCapability" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.85 ; . :Finance a lmm:Organization ; skos:prefLabel "Finance"@en ; skos:notation "lxdoc-org-1" ; dcterms:type "Organization" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :SalesEmea a lmm:Organization ; skos:prefLabel "Sales EMEA"@en ; skos:notation "lxdoc-org-2" ; dcterms:type "Organization" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . ## "Accounting Shared Services" is the documentation's example of an ## Organization subtype inside Finance, which is also what makes it the natural ## demonstration of the fact sheet hierarchy. :AccountingSharedServices a lmm:OrganizationUnit ; skos:prefLabel "Accounting Shared Services"@en ; skos:notation "lxdoc-org-3" ; dcterms:type "OrganizationUnit" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :LeadToCash a lmm:ValueStream ; skos:prefLabel "Lead to Cash"@en ; skos:notation "lxdoc-vs-1" ; dcterms:type "ValueStream" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :CreateCustomerInvoice a lmm:Process ; skos:prefLabel "Create Customer Invoice"@en ; skos:notation "lxdoc-proc-1" ; dcterms:type "Process" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :GoldCreditCard a lmm:Product ; skos:prefLabel "Gold Credit Card"@en ; skos:notation "lxdoc-prod-1" ; dcterms:type "Product" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . ################################################################# # Application & Data Architecture # # https://help.sap.com/docs/leanix/ea/application-modeling-guidelines # https://help.sap.com/docs/leanix/ea/interface-modeling-guidelines # https://help.sap.com/docs/leanix/ea/data-object-modeling-guidelines ################################################################# :S4HanaFinance a lmm:Application ; skos:prefLabel "SAP S/4HANA Finance"@en ; skos:altLabel "S/4HANA Finance" ; skos:notation "lxdoc-app-1" ; dcterms:type "Application" ; dcterms:source ; dcterms:created "2024-02-01T09:00:00Z"^^xsd:dateTime ; ## illustrative dcterms:modified "2026-07-30T14:12:00Z"^^xsd:dateTime ; ## illustrative lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.82 ; ## illustrative ap:atLifecycleStage ap:Active ; lmm:hasLifecyclePhase :S4HanaActivePhase, :S4HanaPhaseOutPhase ; lmm:hasSubscription :S4HanaAccountable, :S4HanaResponsible ; lmm:hasTag :OnPremHostingTag ; . :S4HanaActivePhase a lmm:LifecyclePhase ; ap:atLifecycleStage ap:Active ; lmm:phaseStart "2024-04-01"^^xsd:date ; ## illustrative . :S4HanaPhaseOutPhase a lmm:LifecyclePhase ; ap:atLifecycleStage ap:PhaseOut ; lmm:phaseStart "2028-01-01"^^xsd:date ; ## illustrative — a planned phase . :SalesforceSalesCloud a lmm:BusinessApplication ; skos:prefLabel "Salesforce Sales Cloud"@en ; skos:notation "lxdoc-app-2" ; dcterms:type "BusinessApplication" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.68 ; ## illustrative ap:atLifecycleStage ap:Active ; lmm:hasSubscription :SalesforceObserver ; lmm:hasTag :SaasHostingTag ; . ## An archived fact sheet, to exercise the third status value. LeanIX keeps ## archived fact sheets readable and refuses updates to them; nothing about ## being archived says the software stopped running, which is why the lifecycle ## stage here is independent of the status. :LegacyBillingSystem a lmm:Application ; skos:prefLabel "Legacy Billing System"@en ; skos:notation "lxdoc-app-3" ; dcterms:type "Application" ; lmm:factSheetStatus lmm:StatusArchived ; ap:atLifecycleStage ap:Retired ; skos:editorialNote '''The one fact sheet here with no dcterms:source, and deliberately so: the name is invented. The documentation names example applications but none that is archived, and the ARCHIVED status is worth demonstrating because it is the value most likely to be mishandled — an archived record is not a retired application.'''@en ; . :OrderExportApi a lmm:Interface ; skos:prefLabel "Order export API"@en ; skos:notation "lxdoc-itf-1" ; dcterms:type "Interface" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; ap:atLifecycleStage ap:Active ; . :CustomerProfile a lmm:DataObject ; skos:prefLabel "Customer Profile"@en ; skos:notation "lxdoc-do-1" ; dcterms:type "DataObject" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :InvoiceData a lmm:DataObject ; skos:prefLabel "Invoice Data"@en ; skos:notation "lxdoc-do-2" ; dcterms:type "DataObject" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . ################################################################# # Technical Architecture # # https://help.sap.com/docs/leanix/ea/it-component-modeling-guidelines # https://help.sap.com/docs/leanix/ea/tech-category-modeling-guidelines # https://help.sap.com/docs/leanix/ea/platform-modeling-guidelines # https://help.sap.com/docs/leanix/ea/provider-modeling-guidelines ################################################################# :Postgresql15 a lmm:ITComponent ; skos:prefLabel "PostgreSQL 15"@en ; skos:notation "lxdoc-itc-1" ; dcterms:type "ITComponent" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; ap:atLifecycleStage ap:Active ; . :KubernetesCluster a lmm:ITComponent ; skos:prefLabel "Kubernetes cluster"@en ; skos:notation "lxdoc-itc-2" ; dcterms:type "ITComponent" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; ap:atLifecycleStage ap:Active ; . :DatabaseCategory a lmm:TechCategory ; skos:prefLabel "Database"@en ; skos:notation "lxdoc-tc-1" ; dcterms:type "TechCategory" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :CloudPlatformCategory a lmm:TechCategory ; skos:prefLabel "Cloud Platform"@en ; skos:notation "lxdoc-tc-2" ; dcterms:type "TechCategory" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :CustomerDataPlatform a lmm:Platform ; skos:prefLabel "Customer Data Platform"@en ; skos:notation "lxdoc-plat-1" ; dcterms:type "Platform" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; lmm:completion 0.4 ; ## illustrative . ## System is the optional thirteenth fact sheet type. The name is the ## documentation's own example of one. :EccProdSystem a lmm:System ; skos:prefLabel "SAP ERP Central System (ECC PROD)"@en ; skos:notation "lxdoc-sys-1" ; dcterms:type "System" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; ap:atLifecycleStage ap:PhaseOut ; . :SapProvider a lmm:Provider ; skos:prefLabel "SAP"@en ; skos:notation "lxdoc-prov-1" ; dcterms:type "Provider" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . :MicrosoftAzureProvider a lmm:Provider ; skos:prefLabel "Microsoft Azure"@en ; skos:notation "lxdoc-prov-2" ; dcterms:type "Provider" ; dcterms:source ; lmm:factSheetStatus lmm:StatusActive ; . ################################################################# # Tags # # The tag group "Application Hosting" and its values On-Prem, SaaS, PaaS and # IaaS are the worked example on # https://help.sap.com/docs/leanix/ea/it-components-hosting-modeling-v3 — # which is also why the group matters: "SaaS" means something only relative to # it. Tag identifiers are illustrative. ################################################################# :OnPremHostingTag a lmm:Tag ; skos:notation "lxdoc-tag-1" ; lmm:tagName "On-Prem" ; lmm:tagGroup "Application Hosting" ; dcterms:source ; . :SaasHostingTag a lmm:Tag ; skos:notation "lxdoc-tag-2" ; lmm:tagName "SaaS" ; lmm:tagGroup "Application Hosting" ; dcterms:source ; . ################################################################# # Subscriptions # # The three subscription types are documented and fixed: # https://help.sap.com/docs/leanix/ea/fact-sheet-subscription # https://help.sap.com/docs/leanix/ea/managing-fact-sheet-subscriptions # Roles are configured per workspace and may be scoped to one type or to all, # which is why lmm:subscriptionRole is a plain string: # https://help.sap.com/docs/leanix/ea/subscription-roles # # The people and their email addresses are invented. So is the pairing of a # person with a role. ################################################################# :JaneDoe a arch:Stakeholder ; skos:prefLabel "Jane Doe"@en ; . :MarcusReid a arch:Stakeholder ; skos:prefLabel "Marcus Reid"@en ; . :S4HanaAccountable a lmm:Subscription ; lmm:subscriber :JaneDoe ; lmm:subscriberEmail "jane.doe@example.org" ; lmm:subscriptionType lmm:Accountable ; lmm:subscriptionRole "Application Owner" ; dcterms:source ; . :S4HanaResponsible a lmm:Subscription ; lmm:subscriber :MarcusReid ; lmm:subscriberEmail "marcus.reid@example.org" ; lmm:subscriptionType lmm:Responsible ; lmm:subscriptionRole "Technical Owner", "Data Steward" ; dcterms:source ; . ## A subscription identified by address alone — the legitimate fallback where a ## converter has no stable identity to mint a stakeholder from, and the case the ## sh:or in LeanIXSubscriptionShape exists to permit. :SalesforceObserver a lmm:Subscription ; lmm:subscriberEmail "sales-ops@example.org" ; lmm:subscriptionType lmm:Observer ; dcterms:source ; . ## The accountable subscriber is the natural source for the core-level ## governance owner, which makes "who owns this?" answerable without knowing ## anything about LeanIX. :S4HanaFinance arch:conceptOwner :JaneDoe . ################################################################# # Relationships — direct triples # # Relationship types are documented at # https://help.sap.com/docs/leanix/ea/meta-model. Which element relates to # which is this repository's reading, not SAP's. ################################################################# ## Supporting — Application → BusinessCapability :S4HanaFinance lmm:supports :OrderProcessing . :SalesforceSalesCloud lmm:supports :CustomerManagement . ## Requiring — Application → ITComponent :S4HanaFinance lmm:requires :Postgresql15 . :SalesforceSalesCloud lmm:requires :KubernetesCluster . ## Interface provision and consumption — the asymmetry that makes the Interface ## fact sheet worth having. The documentation describes the "Order export API" ## as an interface between a front end and the ERP system. :S4HanaFinance lmm:hasInterface :OrderExportApi . :SalesforceSalesCloud lmm:consumesInterface :OrderExportApi . ## Data usage — from an Application and from an Interface, the second being why ## lmm:usesData has Interface in its domain as well :S4HanaFinance lmm:usesData :InvoiceData . :OrderExportApi lmm:usesData :CustomerProfile . ## Impact — Initiative → Application :ErpConsolidation lmm:impacts :S4HanaFinance . :ErpConsolidation lmm:impacts :LegacyBillingSystem . ## Driving — Objective → Initiative :ReduceRunCost lmm:drives :ErpConsolidation . ## Organizational usage — Organization → Application :Finance lmm:usedByOrg :S4HanaFinance . :SalesEmea lmm:usedByOrg :SalesforceSalesCloud . ## Provision — ITComponent → Provider :Postgresql15 lmm:providedBy :SapProvider . :KubernetesCluster lmm:providedBy :MicrosoftAzureProvider . ## Categorization — ITComponent → TechCategory :Postgresql15 lmm:categorizedBy :DatabaseCategory . :KubernetesCluster lmm:categorizedBy :CloudPlatformCategory . ## Fact sheet hierarchy — parent → child, same fact sheet type. This is ## relToParent/relToChild, the only structural relation in the meta model. ## skos:broader is emitted alongside, so a consumer that understands SKOS gets ## the tree without knowing anything about LeanIX. :Finance lmm:parentOf :AccountingSharedServices . :AccountingSharedServices skos:broader :Finance . ## Platform membership — member → Platform, across all three member types :SalesforceSalesCloud lmm:partOfPlatform :CustomerDataPlatform . :CustomerManagement lmm:partOfPlatform :CustomerDataPlatform . :KubernetesCluster lmm:partOfPlatform :CustomerDataPlatform . ## Business context — supported by an application, realizing a capability :S4HanaFinance lmm:supportsContext :CreateCustomerInvoice . :SalesforceSalesCloud lmm:supportsContext :LeadToCash . :LeadToCash lmm:contextRealizes :CustomerManagement . :CreateCustomerInvoice lmm:contextRealizes :OrderProcessing . ## Objective → BusinessCapability, which Objective's own definition mentions :ReduceRunCost lmm:targetsCapability :OrderProcessing . ## System composition — to an Application and to an ITComponent :EccProdSystem lmm:composedOf :S4HanaFinance, :Postgresql15 . ## Impact on a Platform, which the widened range of lmm:impacts permits :ErpConsolidation lmm:impacts :CustomerDataPlatform . ################################################################# # Relationships — qualified resources # # One per relationship type, which is also what a converter reading a LeanIX # export produces: every exported relation becomes a resource, because that is # where the workspace's own relation name and any relation attributes go. # # The direct triple above is always emitted as well (P-7): a consumer doing # SPARQL traversal or reasoning depends on it, and the qualified resource alone # is not enough. # # Covering all sixteen types here is deliberate rather than thorough for its own # sake — leanIX-shapes.ttl carries one endpoint shape per type, and a shape that # no fixture reaches is a shape whose own class IRIs are unchecked. Both branches # of the DataUsage source alternative are exercised for the same reason. ################################################################# :rel-S4HanaFinance-supports-OrderProcessing a lmm:Supporting, arch:ModelConcept ; skos:prefLabel "SAP S/4HANA Finance supports Order Processing"@en ; arch:source :S4HanaFinance ; arch:target :OrderProcessing ; dcterms:type "relApplicationToBusinessCapability" ; . :S4HanaFinance arch:hasQualifiedRelationship :rel-S4HanaFinance-supports-OrderProcessing . :rel-S4HanaFinance-requires-Postgresql15 a lmm:Requiring, arch:ModelConcept ; skos:prefLabel "SAP S/4HANA Finance requires PostgreSQL 15"@en ; arch:source :S4HanaFinance ; arch:target :Postgresql15 ; dcterms:type "relApplicationToITComponent" ; . :S4HanaFinance arch:hasQualifiedRelationship :rel-S4HanaFinance-requires-Postgresql15 . ## Data usage from an Application … :rel-S4HanaFinance-uses-InvoiceData a lmm:DataUsage, arch:ModelConcept ; skos:prefLabel "SAP S/4HANA Finance uses Invoice Data"@en ; arch:source :S4HanaFinance ; arch:target :InvoiceData ; dcterms:type "relApplicationToDataObject" ; . :S4HanaFinance arch:hasQualifiedRelationship :rel-S4HanaFinance-uses-InvoiceData . ## … and from an Interface, which is the other branch of the same relation :rel-OrderExportApi-uses-CustomerProfile a lmm:DataUsage, arch:ModelConcept ; skos:prefLabel "Order export API carries Customer Profile"@en ; arch:source :OrderExportApi ; arch:target :CustomerProfile ; dcterms:type "relInterfaceToDataObject" ; . :OrderExportApi arch:hasQualifiedRelationship :rel-OrderExportApi-uses-CustomerProfile . :rel-ReduceRunCost-drives-ErpConsolidation a lmm:Driving, arch:ModelConcept ; skos:prefLabel "Reduce IT run cost drives the ERP Consolidation Program"@en ; arch:source :ReduceRunCost ; arch:target :ErpConsolidation ; dcterms:type "relObjectiveToInitiative" ; . :ReduceRunCost arch:hasQualifiedRelationship :rel-ReduceRunCost-drives-ErpConsolidation . ## Source is the Organization, not the Application — the direction the ontology ## declares, which is the opposite of how the predicate name reads :rel-Finance-uses-S4HanaFinance a lmm:OrganizationalUsage, arch:ModelConcept ; skos:prefLabel "Finance uses SAP S/4HANA Finance"@en ; arch:source :Finance ; arch:target :S4HanaFinance ; dcterms:type "relOrganizationToApplication" ; . :Finance arch:hasQualifiedRelationship :rel-Finance-uses-S4HanaFinance . :rel-Postgresql15-providedBy-Sap a lmm:Provision, arch:ModelConcept ; skos:prefLabel "PostgreSQL 15 is provided by SAP"@en ; arch:source :Postgresql15 ; arch:target :SapProvider ; dcterms:type "relITComponentToProvider" ; . :Postgresql15 arch:hasQualifiedRelationship :rel-Postgresql15-providedBy-Sap . :rel-Postgresql15-categorizedBy-Database a lmm:Categorization, arch:ModelConcept ; skos:prefLabel "PostgreSQL 15 is categorized as Database"@en ; arch:source :Postgresql15 ; arch:target :DatabaseCategory ; dcterms:type "relITComponentToTechCategory" ; . :Postgresql15 arch:hasQualifiedRelationship :rel-Postgresql15-categorizedBy-Database . :rel-S4HanaFinance-provides-OrderExportApi a lmm:InterfaceOwnership, arch:ModelConcept ; skos:prefLabel "SAP S/4HANA Finance provides Order export API"@en ; arch:source :S4HanaFinance ; arch:target :OrderExportApi ; dcterms:type "relApplicationToInterfaceProvider" ; . :S4HanaFinance arch:hasQualifiedRelationship :rel-S4HanaFinance-provides-OrderExportApi . :rel-SalesforceSalesCloud-consumes-OrderExportApi a lmm:InterfaceConsumption, arch:ModelConcept ; skos:prefLabel "Salesforce Sales Cloud consumes Order export API"@en ; arch:source :SalesforceSalesCloud ; arch:target :OrderExportApi ; dcterms:type "relInterfaceToConsumerApplication" ; . :SalesforceSalesCloud arch:hasQualifiedRelationship :rel-SalesforceSalesCloud-consumes-OrderExportApi . :rel-Finance-parentOf-AccountingSharedServices a lmm:FactSheetHierarchy, arch:ModelConcept ; skos:prefLabel "Finance is the parent of Accounting Shared Services"@en ; arch:source :Finance ; arch:target :AccountingSharedServices ; dcterms:type "relToChild", "relToParent" ; . :Finance arch:hasQualifiedRelationship :rel-Finance-parentOf-AccountingSharedServices . :rel-ErpConsolidation-impacts-S4HanaFinance a lmm:Impact, arch:ModelConcept ; skos:prefLabel "ERP Consolidation Program impacts SAP S/4HANA Finance"@en ; arch:source :ErpConsolidation ; arch:target :S4HanaFinance ; dcterms:type "relInitiativeToApplication" ; . :ErpConsolidation arch:hasQualifiedRelationship :rel-ErpConsolidation-impacts-S4HanaFinance . :rel-SalesforceSalesCloud-partOf-CustomerDataPlatform a lmm:PlatformMembership, arch:ModelConcept ; skos:prefLabel "Salesforce Sales Cloud is part of the Customer Data Platform"@en ; arch:source :SalesforceSalesCloud ; arch:target :CustomerDataPlatform ; dcterms:type "relApplicationToPlatform" ; . :SalesforceSalesCloud arch:hasQualifiedRelationship :rel-SalesforceSalesCloud-partOf-CustomerDataPlatform . :rel-S4HanaFinance-supports-CreateCustomerInvoice a lmm:ContextSupport, arch:ModelConcept ; skos:prefLabel "SAP S/4HANA Finance supports Create Customer Invoice"@en ; arch:source :S4HanaFinance ; arch:target :CreateCustomerInvoice ; dcterms:type "relApplicationToBusinessContext" ; . :S4HanaFinance arch:hasQualifiedRelationship :rel-S4HanaFinance-supports-CreateCustomerInvoice . :rel-LeadToCash-realizes-CustomerManagement a lmm:ContextRealization, arch:ModelConcept ; skos:prefLabel "Lead to Cash realizes Customer Management"@en ; arch:source :LeadToCash ; arch:target :CustomerManagement ; dcterms:type "relBusinessContextToBusinessCapability" ; . :LeadToCash arch:hasQualifiedRelationship :rel-LeadToCash-realizes-CustomerManagement . :rel-ReduceRunCost-targets-OrderProcessing a lmm:CapabilityTargeting, arch:ModelConcept ; skos:prefLabel "Reduce IT run cost targets Order Processing"@en ; arch:source :ReduceRunCost ; arch:target :OrderProcessing ; dcterms:type "relObjectiveToBusinessCapability" ; . :ReduceRunCost arch:hasQualifiedRelationship :rel-ReduceRunCost-targets-OrderProcessing . :rel-EccProdSystem-composedOf-Postgresql15 a lmm:SystemComposition, arch:ModelConcept ; skos:prefLabel "SAP ERP Central System is composed of PostgreSQL 15"@en ; arch:source :EccProdSystem ; arch:target :Postgresql15 ; dcterms:type "relSystemToITComponent" ; . :EccProdSystem arch:hasQualifiedRelationship :rel-EccProdSystem-composedOf-Postgresql15 . ## Impact on a Platform rather than an Application — the second branch of the ## widened lmm:impacts range, and the reason lmm:Impact's endpoint shape uses ## sh:or on its target :rel-ErpConsolidation-impacts-CustomerDataPlatform a lmm:Impact, arch:ModelConcept ; skos:prefLabel "ERP Consolidation Program impacts the Customer Data Platform"@en ; arch:source :ErpConsolidation ; arch:target :CustomerDataPlatform ; dcterms:type "relInitiativeToPlatform" ; . :ErpConsolidation arch:hasQualifiedRelationship :rel-ErpConsolidation-impacts-CustomerDataPlatform .