Is there a list of available substitutions for EDI 850?

Specifically adding REF01 and REF02 after BEG. We are attempting to set up EDI with US Foods and one of their requirements is to include the <tpid> in REF02. I'm very green to EDI so this may all be way off base. Any detailed training or documentation would be awesome.

The most obvious way to do this, I would think would be to add List: <TPID>_O_REF Your: IA Partner: <TPID> but that doesn't work.

Find more posts tagged with

Accepted answers

Brent Honadel

Hi Brian,

The the specific data substitution information you are looking for is missing from the User Guide for EDI for Supply Management.

List Name: ADD_HEADER_REF

Your Value: <trading partner id>

Partner Value: <the REF segment that should be included>

My understanding is US Foods requires two header REF segments

one for "US Foodservice Assigned Identifier for the Trading Relationship. Value will be provided by US Foodservice" with a "ZZ" qualifier.

one "that identifies source of purchase order" with an "OS" qualifier: REF^OS^INFOR

As examples, if your trading partner id was "USF" and USF assigned identifier for you was "GLOBOTECH". You would create two data sub records

List Name: ADD_HEADER_REF

Your Value: USF

Partner Value: REF^OS^INFOR

List Name: ADD_HEADER_REF

Your Value: USF

Partner Value: REF^ZZ^GLOBOTECH

Brent Honadel

EDI for Supply Chain Management at https://docs.infor.com/ifsm/latest/en-us/ifsmolh/default.html?helpcontent=ifsmediug/cover.html

However, it does not have all available. while Release Notes have always included documentation about new Data Substitutions, the User Guide has not been kept current. We are actively working on updating the guide with documentation on enhancements as well as other improvements

All comments

Brent Honadel

Hi Brian,

The the specific data substitution information you are looking for is missing from the User Guide for EDI for Supply Management.

List Name: ADD_HEADER_REF

Your Value: <trading partner id>

Partner Value: <the REF segment that should be included>

My understanding is US Foods requires two header REF segments

one for "US Foodservice Assigned Identifier for the Trading Relationship. Value will be provided by US Foodservice" with a "ZZ" qualifier.

one "that identifies source of purchase order" with an "OS" qualifier: REF^OS^INFOR

As examples, if your trading partner id was "USF" and USF assigned identifier for you was "GLOBOTECH". You would create two data sub records

List Name: ADD_HEADER_REF

Your Value: USF

Partner Value: REF^OS^INFOR

List Name: ADD_HEADER_REF

Your Value: USF

Partner Value: REF^ZZ^GLOBOTECH

Brian Merrill

This is exactly what I needed. Thank you so much! Where should I look for the full list of available List Names?

Brian Merrill

Looks like we also need to add a REF to the ST N1 loop. I've tried ADD_N1LOOP_REF, ADD_LOOP_REF, ADD_N1_LOOP_REF but no joy.

Brent Honadel

I am not aware or familiar with that requirement. What is supposed to be sent in the REF within the N1ST Loop?

Brian Merrill

should look something like this.

BEG*00*NE*PONUMBERB**20091001~
REF*ZZ*USF-TRADING-PARTNERID~
REF*OS*PO-SOURCE~

PER*BD*ORDER CONTACT NAME*TE*1234567890~
DTM*002*20091002~
N1*SF*US FOODSERVICE DIVISION*91*9D~
N1*ST*CUSTOMER NAME*91*12345678~
N3*ADDRESS LINE 1~
N4*CITY*ZZ*12345~
REF*DP*00~ <- this one

PO1*1*3*EA*12.34*PE*VN*1419332~
PID*F****PRODUCT DESCRIPTION~

Brian Merrill

also not sure how exactly to include the N1*SF segment.

Brent Honadel

EDI for Supply Chain Management at https://docs.infor.com/ifsm/latest/en-us/ifsmolh/default.html?helpcontent=ifsmediug/cover.html

Brent Honadel

you can enable including the N3 and N4 for ship to address info with INCLUDE_SHIPTO_ADDRESS data sub.
there is not currently a way to include a N1ST loop level REF segment. It was not part of the enhancement request that lead to the ADD_HEADER_REF data sub.
According to a copy of a USFoods guideline I have, the REF segment is for a department number. The segment is marked as "Used", not "Must Use", which should mean that it is not required.

Copyright © 2025 Infor. All rights reserved.