Is it safe to use EDI Reference fields?

One of our customers would like their PO, PO Line, and PO Release number to appear on our sales order acknowledgment form in a particular format. We’re wondering where exactly to put their PO Release number in sales order entry.

There is of course the PO field on the Sales Order header, and the PO Line field on the order line. But there isn’t a field for PO Release.

On the order line, there’s a Reference field, about which Field Help states:

Specifies additional customer information that you want to store for this order line.

It doesn’t state it, but it also prints on the sales order acknowledgment. And the Technical Details tab of the Field Help window describes it as an “EDI Reference”.

Additionally, on the order release, there’s another Reference field. Field Help says:

Specifies any additional information you want to record with this order release. It often is used for entering customer information like the customer PO number. This text is printed on the Sales Order Acknowledgment, Packing Slip and AR Invoice.

We’d like to use these Reference fields, but we don’t use EDI and are concerned it will break EDI if we misused these fields and decide to use EDI later.

Is it safe to put the customer’s release number in this Reference field on the sales order release, or are we setting ourselves up for issues later on?

1 Like

We’ve used those fields for years and have only added EDI in the last couple of years and we have not had any issues related to our use of those reference fields.

2 Likes

I could be wrong but I think the plain Reference field is OK to use.

It’s the DemandReference field that’s tied to EDI and/or Demand Management. In general, our EDI setup uses UD fields for easy capture and reuse in outbound docs.

What I was hoping, thanks Dan!

I suspected as much! Thanks John.

1 Like