This article is part of our Integration Cookbook.
SAP Cloud Integration Content only comes in two levels of content: Package & Artifact.
A package only groups artifacts like iFlows but does not appear in the monitoring or provides any further object isolation. The key element is the artifact which should be
- Short
- Speaking & self-explaining
- Following a good area grouping
SAP is not using much at the moment, e.g.
- Communicate to SII
- Replicate Business Partner Address to SAP ERP
- Generic Update Request to SuccessFactors HCM Suite Talent Management
We recommend to use own areas to identify the business domain (Finance, Sales, Logistics, HCM, …) and/or define the integrating parties (A2A / B2B / B2G / IOT / A2X).
| Name | Pattern | Example |
| Integration Package |
<Area> <Scenario> |
|
| Integration Flow |
<Area> <Interface> |
|
| Value Mapping | <Area> <opt:Interface> Value Mapping |
|
| OData Service |
<Area> <Interface/Object> | |
| System | <Name> |
|
| Communication Channel |
<AdapterType> _<Direction: SND/RCV> _<opt:Technical Details> _<opt:Object> |
|
| Adapter (Camel) | <Name> (also use the vendor domain) |
|
