Controlling Data Synced from SAP to Salesforce
enosix Sync for Salesforce enables real-time data integration from SAP to Salesforce. To help manage performance, storage utilization and cost, customers can control the amount of data being transferred and/or stored using the three supported methods described below.
1. Filter at the Source in SAP (Recommended)
How: Configure the SAP Business Object (BO) tied to a CID to limit which records are eligible for synchronization.
Where: SAP system /ENSX/BO_CONFIG table (configured by your SAP team)
Effect:
- ✅ Reduces data transferred to Salesforce
- ✅ Reduces data stored in Salesforce
Details:
This approach allows SAP to only send relevant records based on pre-defined selection criteria. It’s the most efficient method, preventing unnecessary data from ever leaving the source system.
Best for: Clients with SAP access and control over BO configurations.
2. Apply Search Criteria via Apex Class in the enosix Sync App
How:
- Create a custom Apex class in Salesforce that sends search criteria as part of the request to SAP.
- In the enosix Sync app, specify the class name in the SAP Adapter’s Search Criteria Class field.
Where: Salesforce Org + enosix Sync App configuration
Effect:
- ✅ Reduces data transferred to Salesforce
- ✅ Reduces data stored in Salesforce
Details:
This method allows Salesforce to tell SAP which records should be retrieved. It is especially useful when SAP pre-defined selection criteria isn’t feasible or when sync search criteria logic needs to vary by context.
Best for: Clients without SAP access but with Salesforce development resources.
Refer to Search Criteria Class Feature for Apex class examples and technical configuration guides.
3. Use Valence Transformation Filters to Discard Unwanted Records
How:
Use the Transformations screen in the enosix Sync app to configure filters that ignore certain inbound records after they’ve been received from SAP.
Where: enosix Sync app in Salesforce
Effect:
- ❌ Does not reduce data transferred to Salesforce
- ✅ Reduces data stored in Salesforce
Details:
Valence supports inbound filtering through plug-and-play filters, such as the include-exclude sample filter. However, this functionality requires installing a filter package. If you need more advanced filtering logic, it may require Apex development or switching to methods 1 or 2.
Best for: Admins who can install pre-built filters for basic exclusion logic. More complex filtering may require Apex development.
Comparison Table
| Method | Reduces Transfer | Reduces Storage | Requires SAP Access | Requires Apex Development | Admin Friendly |
|---|---|---|---|---|---|
| SAP BO Config (CID) | ✅ | ✅ | ✅ | ❌ | ⚠️ (SAP config needed) |
| Search Criteria Class (enosix Adapter) | ✅ | ✅ | ❌ | ⚠️ (Apex developer needed) | ⚠️ (Dev setup required) |
| Valence Transformation Filters | ❌ | ✅ | ❌ | ⚠️ (for custom filters or logic) | ⚠️ (Install or dev required) |
Recommendations
- Use SAP filtering via BO Config (Method 1) whenever possible for optimal performance and efficiency.
- Combine methods for layered control—e.g., filter at the SAP source and apply Valence Transformation Filters for extra precision.