Description
Pimcore SAP S/4HANA Connector connects your PIM with SAP S/4HANA through OData APIs to sync catalog and business data in both directions.
Admins add credentials in Pimcore Studio, select the Pimcore class for each SAP entity, and map the fields, with the same mapping used for both import and export.
Product data sync creates or updates Pimcore objects from SAP materials, product groups, business partners, and sales orders, while media is added to the Pimcore DAM as assets.
The job view reports total records, processed, created, and updated counts, with the elapsed time and the credential that was used.
The bundle targets Pimcore 12 with the Studio UI and PHP 8.4 or later. A Symfony Messenger worker handles the queue, so a long import never blocks a screen.
Additionally, if you want to connect Pimcore with an ERP that also covers sales and inventory, then check Pimcore Odoo Connector.
Highlighted Features of Pimcore SAP S/4HANA Connector
Two-Way Data Sync
Bidirectional sync moves products, categories, customers, orders, and attributes from SAP to Pimcore and back.
Idempotent Runs
Records match on their business key, so a repeat run updates in place and never creates a duplicate.
Background Job Queue
Symfony Messenger runs each import and export in the queue, so no admin screen waits on SAP.
Encrypted Secrets
Client secrets, API keys, and passwords are stored encrypted with libsodium, never as plain text.
Why Do We Need Pimcore SAP S/4HANA Connector?
Pimcore SAP S/4HANA Connector integrates Pimcore with SAP S/4HANA to sync materials, prices, and customer data across both systems.
Someone manually exports a CSV from SAP, cleans the data, and imports it into Pimcore, which can leave stock outdated and create duplicate products.
It reads the SAP OData APIs directly, matches every record on its business key, and writes curated Pimcore data back to SAP.
Auto Sync screen lists every entity twice, once for import and once for export, so stock and price can refresh every 30 minutes while orders run hourly and media stays off.
Also, if you want to load catalog data into Pimcore from files instead of an ERP, you can check our bundle Pimcore DataImport Bundle.
Use Cases
-
Seed A New PIM Catalog
A brand starting with Pimcore pulls its full material master out of SAP in one import run.
-
Keep Stock And Price Current
The Stock & Price import refreshes existing Pimcore products, so listed prices match SAP.
-
Enrich Once, Publish Back
Marketing writes copy and adds media in Pimcore, then exports the finished record to SAP.
-
Sync Customers And Orders
Business partners and sales orders land in Pimcore, giving reporting one place to read from.
Object Mapping and Field Mapping
Object Mapping decides which Pimcore class backs each SAP entity. Field Mapping then aligns the single fields inside that class with their SAP counterparts.
- Bind Product, Category, Customer, Order, and Attribute to a Pimcore class.
- Choose an entity tab, then list each Pimcore field beside its SAP field.
- Mark the match key row that identifies a record on both sides.
- Use Add field and Remove to grow or trim the map.
- Save each entity map on its own with Save Product mapping.
- One saved map is read by both the import and the export.
Import Data from SAP S/4HANA to Pimcore
Import pulls seven entity types from SAP S/4HANA by letting admins select an entity, choose a credential, and press Start Import to queue the run.
- Import products from A_Product, matched on SKU.
- Import categories from A_ProductGroup, matched on category code.
- Refresh Stock & Price on products that already exist in Pimcore.
- Pull SAP attachments into the DAM, with identical images de-duplicated.
- Import business partners as customers, matched on customer number.
- Import sales orders from A_SalesOrder, matched on order number.
- Read per-locale text from the OData to_* expands.
- Skip products SAP has flagged for deletion, and skip unchanged saves.
Export Pimcore Data to SAP S/4HANA
Export writes curated Pimcore records to SAP by following the SAP create contract, where the root is written first and child collections follow.
- Export Pimcore products to SAP as materials with their descriptions.
- Send attributes as characteristics, each with its description row.
- Write a business partner, its role, and the customer record together.
- Push an order header with its item lines in one call sequence.
- Export categories as classification Classes, since SAP product groups are read-only.
- Read every failed record and its reason on the run detail page.
Auto Sync Schedules for Each Entity
Auto Sync lets admins set individual schedules for each entity, with the grid showing separate import and export entries along with their frequency and last run time.
- Turn the whole schedule on or off with one toggle.
- Set Daily, Hourly, Every 30 min, or Off for each row.
- Read the Last run column and the due or off badge beside it.
- Press Run now to fire the due jobs without waiting.
- A job still sitting in the queue is never queued a second time.
Job History and Run Monitoring
Each import and export screen keeps its own run history, showing Run, Status, Credential, Items, Started, and Ended details, with Open providing access to each run.
- Read Total records, Processed, Created, and Updated as separate tiles.
- Check the running time and the credential the job used.
- Watch the progress bar and the completion message while a job runs.
- Stop a run mid-flight, or while it is still queued.
- Retry a finished run without setting it up again.
- Open the error list to see each rejected record and its SAP message.
Support
For any query or issue, please create a support ticket here http://webkul.uvdesk.com/
You may also check our quality Magento 2 Extensions.