SAP Base Policy Level (v1.0)
Description
This policy level (aka compliance level) sap:base:v1 MUST be fulfilled by all SAP applications and services.
It includes the essential validations that ensure proper metadata discovery and aggregation.
Usually SAP applications and services will use the more complete and opinionated sap:core:v1 policy level.
General Policies
Policy Levels
- SAP applications and services MAY define custom policy levels, but they MUST be namespaced under their application-specific namespace, e.g.
sap.s4:core:v1. - Only centrally aligned policy levels (such as
sap:base:v1orsap:core:v1) MAY use the rootsapnamespace. Custom policy levels MUST NOT use the rootsapnamespace, e.g.sap:s4:v1is not allowed.
Namespaces
- All SAP namespaces MUST be registered in the SAP namespace-registry.
- All ORD resources owned by SAP MUST use the
sapvendor namespace - ORD resources / extensions created by the customer MAY use the
customervendor namespace or MUST use their own vendor namespace.
- All ORD resources owned by SAP MUST use the
Packages
- The vendor of a Package MUST be set and be equal to one of the allowed values:
sap:vendor:SAP:,customer:vendor:Customer:.
Misc Constraints
- Although
Vendoris technically not validated by a policy level, we need to ensure that within SAP we don't define the SAP vendor multiple times or reference it differently.- The SAP
VendorMUST NOT be defined by any SAP application or service, as this is done centrally. - The correct value for a SAP vendor reference is
sap:vendor:SAP:.
- The SAP