972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Master data

EDI 244 Product Source Information

The X12 document used to send classification and categorization data about a company's products, processes and facilities.

Sent by
Supplier or manufacturer
Received by
Trading partners or listing agencies
Standard
ANSI ASC X12

What is an EDI 244?

The EDI 244 Product Source Information is the ANSI X12 transaction set used to transmit classification and categorization data about a company's products, processes and facilities to existing and prospective trading partners or listing agencies.

Buyers searching for suppliers, and directories that list them, need to know what a company makes, how and where. Structured source information lets them find suppliers by classification codes and capabilities rather than by reading brochures. It complements listings in procurement and supplier directories, where buyers search by classification code.

How the EDI 244 worksDiagram of the EDI 244 Product Source Information. Supplier or manufacturer sends it to trading partners or listing agencies. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required NM1 loop with NM1 (Individual or Organizational Name), DTM (Date/Time Reference) and the required N1 loop with N1 (Party Identification) and the required BSF loop with BSF (Business Function), the required NX2 loop with NX2 (Location ID Component) and the required PID loop with PID (Product/Item Description). 0 optional loops are listed by their first segment.How the EDI 244 worksProduct Source Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 244SENDERSupplier ormanufacturerRECEIVERTrading partners orlisting agencies997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code PNGS … GETransaction set 244ST … SEHEADINGBGNBeginning Segment+ required NM1 (NM1)Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 244. Your trading partner's implementation guide adds its own requirements.
How the EDI 244 worksDiagram of the EDI 244 Product Source Information. Supplier or manufacturer sends it to trading partners or listing agencies. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required NM1 loop with NM1 (Individual or Organizational Name), DTM (Date/Time Reference) and the required N1 loop with N1 (Party Identification) and the required BSF loop with BSF (Business Function), the required NX2 loop with NX2 (Location ID Component) and the required PID loop with PID (Product/Item Description). 0 optional loops are listed by their first segment.How the EDI 244 worksProduct Source Information: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 244SENDERSupplier ormanufacturerRECEIVERTrading partnersor listingagencies997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code PN (GS … GE)Transaction set 244 (ST … SE)HEADINGBGNBeginning Segment+ required NM1 (NM1)Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 244. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 244, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 244 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Listing a company in supplier directories
  • Describing manufacturing capabilities to buyers
  • Updating product and facility classifications

Where it fits in the document flow

This document 244 Product Source Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 244 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • NM1
  • DTM
  • N1
  • BSF
  • NX2
  • PID
  • SE

Practical example

The 244 in practice

A machining company registers with a procurement directory used by large manufacturers. It sends a 244 with its product classifications, its processes, such as CNC milling and heat treatment, and its facilities and certifications. Buyers searching the directory for those capabilities find the company.

Implementation

Implementation considerations for the 244

  • Use classification codes the directory or buyer recognizes.
  • Keep listings current as capabilities change.
  • Only list capabilities that can be supported by evidence.
  • Include facility locations where relevant.

How ECOM helps

Automate the 244 with ECOM

Industry

Industrial Manufacturing

Distributor, OEM customer and supplier integration for industrial manufacturers.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

Trading Partner Onboarding

EDI certification and automation onboarding for customers, suppliers and carriers, by whichever method each partner can support.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related master data documents

All 25 master data documents

Need help with the EDI 244?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us