Physical hierarchy and ownership
How to Read EDI 852 Product Activity Data
Follow ST through SE while keeping product and activity evidence separate.
Begin with exact ST01=852 and resolve the release from envelope evidence. Public Smart Mapping supports generic 004010, 004030, and 005010. Values remain lexical strings and physical SourceIndex remains file-global.
Read the transaction in source order
- ST opens the transaction.
- XQ supplies reporting context such as handling, period, report identifier, and purpose.
- Header parties, references, dates, pricing, adjustments, packaging, and amounts remain header-owned.
- LIN begins product context and owns ordered qualifier/value pairs plus product QTY.
- Each physical ZA creates one PRODUCT_ACTIVITY row.
- ZA-local QTY remains activity quantity evidence.
- SDQ owns paired locations and quantities.
- G95 owns performance-condition evidence and its DTM children.
- CTT remains source-reported summary evidence; SE closes the transaction.
Understand canonical grain and fallback
One physical ZA produces one PRODUCT_ACTIVITY row. Repeating structures remain compact collection JSON in 18 top-level Count/Occurrences pairs with 9 nested paths. A transaction without ZA produces one SUMMARY fallback row at the documented anchor.
Preserve ownership
Product QTY and activity QTY never merge. SDQ evidence stays on its ZA. G95 dates stay with their physical G95 sibling. Party children, references, dates, and pricing evidence remain with their physical owner. Duplicates remain distinct, and CTT is never reconciled to LIN, ZA, or canonical-row counts.
Inspect product activity without inventing totals
Open the browser-local EDI Parser, inspect the EDI 852 field reference, or review objective 852 validation. For the adjacent but different inventory message, read what an EDI 846 reports.