SAP ECC and Virtualstock

Operational impact: When Virtualstock's supplier-specific SKUs do not map correctly to SAP ECC's internal Material Masters, automated processing fails. This prevents the creation of accurate Goods Receipts against drop-ship Purchase Orders. The finance team is then unable to process supplier invoices, delaying payouts and requiring extensive manual data correction to close out orders.

Prevention / Action: The integration must enforce a strict, centralised mapping between supplier SKUs and SAP Material Master numbers. This mapping should be owned within a single source of truth. Design the integration to hold any inbound transaction, such as a ship notice or supplier invoice, in an exception queue if its product identifiers do not have a valid mapping. This prevents un-matchable data from creating failed IDocs or financial discrepancies in SAP.

Operational impact: Virtualstock provides councils or invoices for drop-shipped goods, but if these do not align with SAP's record of what was received, reconciliation becomes a major task. The finance team must manually investigate discrepancies between Virtualstock's invoice data and SAP's Goods Receipt and Purchase Order records. At scale, this delays supplier payments and means financial journals for cost of sales are inaccurate until the period-end close.

Prevention / Action: The integration's financial workflow should be event-driven and sequenced correctly. The creation of a supplier invoice in SAP should be triggered by a confirmed Goods Receipt status in ECC, not simply by the despatch advice from Virtualstock. This ensures the three-way match between the Purchase Order, the physical receipt record, and the invoice is always performed against SAP's own verified data, routing any exceptions to a commercial team member for approval.

Operational impact: Drop-ship fulfilment generates a high volume of asynchronous updates, such as despatch advices and cancellations, which can arrive out of order. If a cancellation message from Virtualstock is processed after the SAP Inbound Delivery IDoc has already been posted, it can lead to incorrect stock records and failed payment runs. This leaves the operations and customer service teams with an inaccurate view of the real order state.

Prevention / Action: The integration layer should be designed to handle out-of-sequence events, typically using a staging table or a message queue with stateful logic. Before posting a transaction to SAP, the logic should check the status of the parent Sales Order or Purchase Order to ensure the update is valid (e.g., a despatch advice is not processed for an already cancelled line). This requires establishing clear ownership of the 'final' order status within SAP.

Operational impact: SAP ECC often uses strict data formats, such as padded, fixed-length Material Numbers (e.g. '000012345'), while supplier SKUs in Virtualstock may be variable-length ('12345'). This mismatch causes lookup failures for almost every transaction, from order placement to goods receipt. The result is a high volume of failed IDocs that require manual reprocessing, delaying the entire order-to-cash cycle and creating significant work for support teams.

Prevention / Action: Define a clear data marshalling policy where the integration middleware is solely responsible for transforming data formats between systems. All identifier logic, like padding SAP Material Numbers or trimming spaces from supplier data, should be centralised in the integration layer. Pre-launch data validation across the entire supplier catalogue is critical to identify and remediate any format conflicts before they impact live transactions.