Pharma supply chain
EDI Migration from IDoc to cXML
Challenge
A pharma key account switched its procurement platform. The existing vendor-managed-inventory data exchange via SAP IDoc over SFTP had to be replaced by cXML over HTTPS without interrupting the ability to deliver.
Solution
We specified and supported the migration from the IDoc PROACT01 to the cXML ProductActivityMessage via the GEP platform: field mapping for header, line items, quantity types and addresses, an as-is/to-be description, coordination with the EDI provider and integration with the ERP.
Result
The supplier continues to receive stock and consumption data automatically, now via the customer's modern channel. The specification is documented so that the mapping can be adapted internally when future changes come up.
Starting point
In vendor-managed inventory, the supplier monitors the stock at the customer and replenishes it independently. To make that work, the customer regularly sends stock and consumption data. So far this arrived as a SAP IDoc of type PROACT01 via SFTP, was converted by the EDI provider and loaded into the ERP. With the introduction of the GEP procurement platform, the key account announced the switch to cXML ProductActivityMessage via HTTPS POST. For the supplier that meant a new format, a new transport path and the same demand for reliability.
As-is/to-be analysis
First we documented the existing data flow: which IDoc segments are actually used, which fields end up in the ERP, where the EDI provider intervenes. Against this stood the structure of the cXML message as delivered by the customer’s platform. The as-is/to-be description made visible which information can be transferred one-to-one and where interpretation is needed.
Field mapping specification
The core is the mapping specification in four areas. In the header, sender, receiver, timestamp and message ID are assigned. Line items cover the customer’s and supplier’s part numbers, units and references. Quantity types were the most delicate part: stock, consumption, open orders and reservations must carry the same meaning in both formats. For addresses, the customer’s delivery points and warehouse locations are cleanly mapped to the master data in the ERP.
Coordination and integration
The migration involves three parties: the customer with its platform, the EDI provider handling conversion and transport, and the supplier’s own ERP. We coordinated the alignment, ran test messages and prepared the ERP integration so that incoming data is processed without manual re-entry.
Outcome
The data exchange continues to run automatically, now over HTTPS instead of SFTP and in the format the customer supports long term. The documentation makes the mapping traceable so future adjustments are possible in-house. For suppliers with key accounts that change platforms, this is a recurring topic that a clean specification makes plannable.