Technical Discussion on Clean Core
3 min
SAP ECC or S/4 Private (non-CMIS)
Clean core perspective depends on many factors. Below is a non-CMIS view of this clean core discussion for SAP ECC and S/4 Private (SAP Public is clean core by nature, see section "SAP Public" at bottom of page).
- Non-BPT based SAP ECC or S/4 Private (Rise or Cloud Edition)
- Considered clean core level A for:
- Archiving and business document storage
- Considered clean core level B if:
- Metadata or routing is required for ArchiveLink objects (as Link Enterprise SAP Business Object lookup is required) and metadata is available using classic or released standard SAP oData or RFC API's
- Considered clean core level C if:
- Metadata or routing is required for GOS or DMS objects (as Link Enterprise SAP Business Object lookup for those objects is required that reads SAP tables directly with ABAP)
- Metadata or routing is required and metadata is NOT available through classic or released standard SAP oData or RFC API's
- Typically direct SAP table access via ABAP required
- Notes on Inbound processing clean core level:
- Inbound processing clean core level is dependent on the logic implemented within the Link EnterpriseSAP ABAP wrapper (delivered within the Link Enterprisenamespace)
- If classic or released standard SAP oData or RFC API's, this can be considered clean core level A or B
- Direct table access would push this to level C
- BTP based SAP ECC or S/4 Private (Rise or Cloud Edition)
- Considered clean core level A for:
- Archiving and business document storage
- Metadata or routing is required and metadata is available via SAP standard SAP oData or RFC released API's
- Considered clean core level B if:
- Metadata or routing is required and metadata is available via SAP standard SAP oData or RFC classic API's
- Considered clean core level C if:
- Metadata or routing is required and metadata is NOT available through classic or released standard SAP oData or RFC API's
- Typically direct SAP table access via ABAP required
- Notes on Inbound processing clean core level:
- Inbound processing clean core level is dependent on the logic implemented within the Link Enterprise SAP ABAP wrapper (delivered within the Link Enterprisenamespace)
- If classic or released standard SAP oData or RFC API's, this can be considered clean core level A or B
- Direct table access would push this to level C
SAP Public
- Clean core level A only
- Uses CMIS only
- Metadata (above that provided in the original CMIS request) and master data sync uses released oData API's only (via BAIP/BPT or direct)
- No Link Enterprise SAP Business Object looked required for CMIS