Skip to content
X12 EDI

Sysco Corporation X12 867 Product Transfer and Resale Report

Plan X12 867 Product Transfer and Resale Report for Sysco Corporation (via iTrade Network). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
19
Loops
5
X12 867
Partner references ↗

Implementation guide

Sysco Corporation (via iTrade Network): 867 mapping and validation

X12 867 Product Transfer and Resale Report is used when transfers or downstream sales are reported. Preserve product, transfer or resale reference and reporting period so the product transfer and resale record in your business system stays connected to the original document.

This document is listed for Sysco Corporation (via iTrade Network). 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 transfer and resale record

product, transfer or resale reference and reporting period

  • Define which combination of product, transfer or resale reference and reporting period identifies one business record, its lines and any later revision.
Update the receiving system Processing the product transfer and resale record

ID assigned by the receiving system and processing result

  • Keep a transfer between locations separate from a sale to an end customer.
  • Deduplicate corrected resale reports before calculating rebates or channel demand.
Check the processing result Processing status for the product transfer and resale record

Original document reference and matching response

  • Reconcile the product transfer and resale record 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 19 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 transfers or downstream sales are reported. Name the operational owner of the product transfer and resale record and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map product, transfer or resale reference and reporting period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Sysco Corporation 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 transfer and resale record 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 transfer and resale record processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 867 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic product transfer and resale record 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 transfer and resale record without processing it twice.

Transaction context

Where 867 Product Transfer and Resale Report fits on Sysco Corporation (via iTrade Network)

Sysco Corporation channels
1 of 1

1 of Sysco Corporation's 1 channel list 867

Trading partners
10

partner references list 867

Channels
11

channel entries list 867

The directory associates iTradeNetwork and 867 with 1 channel.

Document structure

X12 867 Product Transfer and Resale Report at the element level

The X12 867 reference contains 30 segment entries and 90 data elements; 50 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
30
Data elements
90
Mandatory elements
50
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BPT 4 2
DTM 2 1
REF 2 1
N1 4 1
N3 2 1
PTD 3 1
N2 1 1
QTY 2 1
LIN 11 2
Key identifiers in 867
  • Transaction Set Purpose Code
  • Date
  • Date/Time Qualifier
  • Reference Identification Qualifier
  • Entity Identifier Code
  • Address Information
  • Product Transfer Type Code
  • Name
Segment reference — 19 segments 5 loops · X12 867 Product Transfer and Resale Report
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

BPT Beginning Segment for Product Transfer and Resale 5 elements

To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit identifying data

DTM Date/Time Reference 2 elements

To specify pertinent dates and times

REF Reference Identification 3 elements

To specify identifying information

N1 Loop Repeat: 5
N1 Name 4 elements

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

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

PER Loop Repeat: 5
PER Administrative Communications Contact 4 elements

To identify a person or office to whom administrative communications should be directed

PTD Loop Repeat: 5
PTD Product Transfer and Resale Detail 1 element

To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data

CTT Loop Repeat: 1
CTT Transaction Totals 4 elements

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

AMT Monetary Amount 2 elements

To indicate the total monetary amount

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)

QTY Loop
QTY Quantity 3 elements

To specify quantity information

LIN Item Identification 11 elements

To specify basic item identification data

PO4 Item Physical Details 10 elements

To specify the physical qualities, packaging, weights, and dimensions relating to the item

UIT Unit Detail 3 elements

To specify item unit data

PID Product/Item Description 2 elements

To describe a product or process in coded or free-form format

Related references

Other transactions in Sysco Corporation (via iTrade Network)

Other EDI documents listed on this channel.

Showing 3 of 3 references

Browse the full directory

Sysco Corporation (via iTrade Network) EDI 867 questions

Common questions about 867 Product Transfer and Resale Report on the Sysco Corporation (via iTrade Network) channel.

What is X12 867 Product Transfer and Resale Report used for?

867 is used when transfers or downstream sales are reported. It carries information for the product transfer and resale record. Match it to your business system using product, transfer or resale reference and reporting period.

Is 867 required for Sysco Corporation (via iTrade Network)?

867 is listed for Sysco Corporation (via iTrade Network). Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 867?

Start with product, transfer or resale reference and reporting period and the target product transfer and resale record. 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 867 error handling?

Keep a transfer between locations separate from a sale to an end customer. Deduplicate corrected resale reports before calculating rebates or channel demand. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 867 relate to other EDI messages?

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

Connect Sysco Corporation 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.