Skip to content
X12 EDI

Granite City Electric X12 852 Product Activity Data

Plan X12 852 Product Activity Data for Granite City Electric (via Epicor Eclipse). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
9
Loops
3
X12 852
Partner references ↗
Book an EDI demo ← All Granite City Electric (via Epicor Eclipse) transactions

Implementation guide

Granite City Electric (via Epicor Eclipse): 852 mapping and validation

X12 852 Product Activity Data is used when product sales or inventory activity is reported. Preserve item, location, activity type and reporting period so the product activity report in your business system stays connected to the original document.

This document is listed for Granite City Electric (via Epicor Eclipse). Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record product activity report

item, location, activity type and reporting period
  • Define which combination of item, location, activity type and reporting period identifies one business record, its lines and any later revision.
Update the receiving system Processing the product activity report

ID assigned by the receiving system and processing result
  • Keep sales, returns and stock movements in separate measures.
  • Replace a corrected reporting period without counting the original activity twice.
Check the processing result Processing status for the product activity report

Original document reference and matching response
  • Reconcile the product activity report with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 9 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when product sales or inventory activity is reported. Name the operational owner of the product activity report and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map item, location, activity type and reporting period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Granite City Electric guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic product activity report data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful product activity report processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 852 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic product activity report data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out product activity report without processing it twice.

Transaction context

Where 852 Product Activity Data fits on Granite City Electric (via Epicor Eclipse)

Granite City Electric channels
1 of 1

1 of Granite City Electric's 1 channel list 852

Trading partners
33

partner references list 852

Channels
38

channel entries list 852

Frequently listed alongside 852

The directory associates Epicor Eclipse and 852 with 1 channel.

Document structure

X12 852 Product Activity Data at the element level

The X12 852 reference contains 24 segment entries and 100 data elements; 46 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
24
Data elements
100
Mandatory elements
46
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
XQ 3 2
XPO 4 1
N9 2 1
PER 4 1
N1 4 1
N2 2 1
N3 2 1
FOB 1 1
DTM 2 1
LIN 9 2
AMT 2 2
ZA 3 1
Key identifiers in 852
  • Transaction Handling Code
  • Date
  • Purchase Order Number
  • Reference Identification Qualifier
  • Contact Function Code
  • Entity Identifier Code
  • Name
  • Address Information
Segment reference — 9 segments 3 loops · X12 852 Product Activity Data
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

XQ Reporting Date/Action 2 elements

To specify reporting date and action to be taken

N1 Loop Repeat: 200
N1 Name 4 elements

To identify a party by type of organization, name, and code

LIN Loop Repeat: 999,999
LIN Item Identification 9 elements

To specify basic item identification data

ZA Loop
ZA Product Activity Reporting 7 elements

To provide activity details concerning product being reported

CTT Transaction Totals 2 elements

To transmit a hash total for a specific element in the transaction set

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Related references

Other transactions in Granite City Electric (via Epicor Eclipse)

Other EDI documents listed on this channel.

Invoice X12 810 Payment Order Remittance Advice X12 820 Product Transfer Account Adjustment X12 844 Price Authorization Acknowledgment Status X12 845 Response To Product Transfer Account Adjustment X12 849 Purchase Order X12 850 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Product Transfer And Resale Report X12 867

Showing 9 of 9 references

Browse the full directory

Granite City Electric (via Epicor Eclipse) EDI 852 questions

Common questions about 852 Product Activity Data on the Granite City Electric (via Epicor Eclipse) channel.

What is X12 852 Product Activity Data used for?

852 is used when product sales or inventory activity is reported. It carries information for the product activity report. Match it to your business system using item, location, activity type and reporting period.

Is 852 required for Granite City Electric (via Epicor Eclipse)?

852 is listed for Granite City Electric (via Epicor Eclipse). Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 852?

Start with item, location, activity type and reporting period and the target product activity report. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 852 error handling?

Keep sales, returns and stock movements in separate measures. Replace a corrected reporting period without counting the original activity twice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 852 relate to other EDI messages?

Keep 852 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the product activity report workflow; confirm any required companion messages with your partner.

Connect Granite City Electric EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform