ERP Integration Patterns for Packaging Compliance: Pulling Data from SAP, Oracle, NetSuite, and D365
Pulling packaging data from your ERP for EPR and PPWR reporting does not require a year-long IT project. Here are the practical extract patterns that work across SAP, Oracle, NetSuite, and Dynamics 365.
By Kevin Kai Wong, Managing Partner at gCurv Technologies
May 5, 2026
The integration question
Packaging compliance data sits in several places: BOM data in PLM or ERP, weights and materials in packaging spec systems, sales volumes in ERP and ecommerce, country-of-sale in order management, supplier evidence in document storage. The ERP usually holds the volume and BOM linkage that ties everything together.
The question is not "should we integrate to the ERP?", you have to. The question is what to extract, at what frequency, and how to do it without a multi-quarter IT engagement.
What to extract from the ERP
The fields the compliance system actually needs from the ERP are narrower than IT's first instinct. You generally need:
- Material master data. SKU IDs, descriptions, base UOM, status (active/discontinued).
- BOM data. SKU-to-component relationships with quantity-per. Often available as a BOM explosion or as a packaging-specific BOM view.
- Component master. Component IDs, descriptions, weight, material classification (where stored in ERP vs PLM).
- Sales volume. Period units shipped, with ship-to country (or a derived field that yields country of sale).
- Customer/channel data. Enough to classify shipments as retail, ecommerce, B2B, etc., for household-stream allocation.
- Legal entity and selling-org information. Which legal entity sold what, in what country, in what period.
You generally do not need: pricing, COGS, GL postings, financial close data, full transaction history. Compliance is volume-driven and component-driven, not financial.
Extract patterns by ERP
SAP (S/4HANA or ECC). The high-value tables are MARA (material master), MARC (plant), MAKT (descriptions), STKO/STPO (BOM header/items), and the sales document tables for volume. Standard CDS views or a CPI/DataSphere extract are usually faster than custom ABAP. For packaging-specific BOM, many SAP installations have a dedicated packaging variant or a separate BOM type, find that before extracting all BOMs.
Oracle (EBS or Fusion). Item master from EGO/INV tables, BOM structures from BOM tables, sales orders from OM. Oracle Fusion's OIC connectors or a flat-file scheduled extract usually suffice. The packaging-specific complication: many Oracle installations carry packaging components as inventory items rather than as BOM children, requiring an item-class filter to isolate them.
NetSuite. Item records (with packaging items typically flagged via item type or custom segment), BOM definitions, and saved searches that join sales transactions to items. SuiteAnalytics or saved-search exports are sufficient for most compliance volumes. NetSuite's strength is the relative simplicity of getting consolidated data out.
Dynamics 365 (F&O or BC). Released products, BOM versions, sales order lines. F&O via OData entities or a Synapse Link export; BC via API endpoints or saved CSV exports. Watch for D365's distinction between engineering BOMs and production BOMs, packaging usually lives in production BOMs.
Frequency and freshness
Most compliance reporting is quarterly or annual. The ERP extract does not need to be real-time. Workable cadences:
- Material and component master: monthly refresh, or change-data-capture if available.
- BOM data: monthly refresh.
- Sales volume: monthly refresh, with quarterly reconciliation against finance.
- Country/channel attribution: monthly refresh.
Real-time extracts are expensive and add no compliance value. Batch is fine.
What goes wrong in ERP integrations
Failure 1, Trying to extract everything. Compliance does not need 200 fields per material. It needs 15. Scope-creep at extract design adds months and increases data quality issues.
Failure 2, Treating BOM as static. BOMs change when suppliers change, when components are reformulated, when weights drift. The integration needs to capture BOM versions and effective dates, not just current state.
Failure 3, Country mis-attribution. Ship-to country in the ERP is not always the country where the packaging is placed on the market, particularly for distribution centers serving multiple markets. Country logic often needs derivation, not direct extraction.
Failure 4, Missing legal-entity context. Multi-entity ERP setups can produce extracts that lose track of which entity is the producer. Legal-entity stamping has to be part of the extract, not a downstream lookup.
Failure 5, Ignoring packaging spec systems. ERP rarely holds material composition, recycled content, or detailed weights. Those live in PLM or a packaging spec system. The ERP integration is necessary but not sufficient.
What this means operationally
The realistic plan for an ERP integration into a packaging compliance system:
- 4 to 6 weeks to scope, agree extract field list, and set refresh cadence.
- 4 to 8 weeks for first extract delivery, depending on IT bandwidth.
- 2 to 4 weeks for data quality validation against a known-good period.
- Steady-state monthly refresh thereafter.
That is months, not years. The year-long projects come from over-scoping or from trying to fix master data quality during the integration rather than extracting what exists and remediating downstream.
What to do in 2026
- Scope your extract by output, not by table. Start from the compliance fields you need and work backward.
- Capture BOM history, not just current BOM.
- Stamp legal entity and country into every extract row at the source.
- Pair the ERP extract with a separate PLM or packaging spec extract for material composition data.
How Packgine helps
Packgine has prebuilt extract templates for SAP, Oracle, NetSuite, and Dynamics 365, defining the minimal field set needed for compliance and the joins to assemble it. Your IT team delivers the extract once; Packgine handles the taxonomy mapping, evidence linking, and jurisdictional reporting on top.
Related reading
Ready to automate your packaging compliance?
See how Packgine manages EPR, PPWR, and sustainability reporting from a single dashboard.
