Your Integration Hub sync failure stems from how SAP Cloud ERP exposes analytical attributes through OData services, combined with specific configuration requirements in Mendix 9.24. I’ll address all three critical areas:
1. Field Mapping Configuration:
SAP analytical attributes use a different metadata structure than standard fields. The ‘CostCenter’ field you’re trying to map is likely exposed as a navigation property rather than a direct attribute. Update your Integration Hub entity mapping:
// Map analytical attributes via navigation
CostCenter := $SAPEntity/AnalyticalData/CostCenter
ProfitCenter := $SAPEntity/AnalyticalData/ProfitCenter
The field mapping configuration needs to traverse the analytical data structure, not map directly to the root entity.
2. SAP Metadata Import for Analytics:
Re-import your SAP metadata with analytical annotations enabled. In the Integration Hub connector configuration, go to SAP Service Settings and enable ‘Include Analytical Annotations’. Then refresh the metadata:
// Connector settings
ODataVersion: V2
IncludeAnalyticalAnnotations: true
MetadataNamespace: SAP/ANALYTICS
This ensures custom analytics attributes are properly discovered during metadata import. The initial import likely excluded the analytical extension namespace, which is why transactional data works but analytical data fails.
3. Custom Analytics Attributes Query Configuration:
Modify your Integration Hub data retrieval microflow to explicitly request analytical extensions in the OData query. SAP Cloud ERP requires the $expand parameter for analytical dimensions:
// In your sync microflow
ODataQuery := '$select=*&$expand=AnalyticalExtensions';
RetrieveFromSAP(ODataQuery);
Without the expansion, SAP returns only base entity data, causing the field mapping to fail when processing custom analytical attributes.
Additional Configuration:
Verify your SAP technical user has authorization for analytical data access (authorization object S_RS_COMP for analytical components). Also check that your OData service in SAP Cloud ERP has the analytical view properly activated - sometimes services are published without analytical capabilities enabled.
For the specific error at record 1247, this suggests the first 1246 records succeeded, meaning some records have analytical data while others don’t. Add null-checking in your field mapping to handle records without analytical attributes gracefully.
After making these changes, clear the Integration Hub cache and re-run the sync. The reporting data should now flow correctly into your Mendix analytics dashboards.