Transaction Interpretation — X12 850 Purchase Order
1. Summary
This document is an EDI X12 850 Purchase Order (transaction code 850), functioning as a license order — the header PO type is DS and the PO number is literally labeled LICENSEPO. This suggests a license/subscription-style purchase rather than a standard physical goods order.
- BEG segment purpose code
00= Original order (this is a new PO, not a change or cancellation). - Bill-to party: NORTHWIND SUPPLY CO.
- Ship-to party: Alex Rivera (individual recipient, likely an end-user/licensee)
- The transaction contains a single line item (1 unit), consistent with a single license/software entitlement being ordered.
2. Header
| Field | Value | Interpretation |
|---|---|---|
| PO Purpose Code (BEG01) | 00 |
Original order |
| PO Type (BEG02) | DS |
Distributor/Direct Ship-related PO type code (interpreted from BEG02; exact meaning depends on partner-specific code list) |
| PO Number (BEG03) | LICENSEPO |
Purchase order number/reference used to identify this transaction |
| PO Date (BEG05) | 2022-09-22 |
Date the purchase order was created |
| Currency (CUR) | USD |
All monetary amounts (unit price) are in US Dollars |
Dates (DTM segments):
| Qualifier | Meaning | Date | Interpretation |
|---|---|---|---|
002 |
Delivery Requested Date | 2022-09-21 | Date requested for delivery |
092 |
Contract Effective Date | 2022-09-21 | License/contract term start |
093 |
Contract Expiration Date | 2023-09-21 | License/contract term end |
The 092/093 pairing (2022-09-21 → 2023-09-21) confirms a 12-month license period, reinforcing that this PO is for a software/license entitlement rather than physical goods.
Note: A CSH (Sales Requirements) and FOB (F.O.B. Related Instructions) segment are present in the histogram but no decoded values were provided in the facts — terms cannot be stated beyond their presence.
3. Parties
| Entity Code | Role | Name | Address | Notes |
|---|---|---|---|---|
BT |
Bill-To | NORTHWIND SUPPLY CO. | (not provided) | The party responsible for payment/invoicing |
ST |
Ship-To | Alex Rivera | 100 EXAMPLE WAY, Docatello, ID 83201, US | ID qualifier 92 (Assigned by Buyer or Buyer's Agent) with ID 0010395441 — likely a customer/account or license-holder identifier |
Only two N1 loops are present (matching partyCount: 2 and N1 histogram count of 2) — no separate Sold-To, Vendor, or Remit-To party is included in this transaction.
4. Line Items
| Line | Product ID(s) | Qty | Unit | Unit Price |
|---|---|---|---|---|
| 00010 | BP: ESD-DDD809A-G00-15.0 / VP: 6DDDTP459 |
1 | EA | 433.67 USD |
Product ID qualifiers:
BP= Buyer's Part Number —ESD-DDD809A-G00-15.0(internal identifier used by the buyer; the "ESD" prefix commonly denotes Electronic Software Delivery/Distribution in licensing contexts, though this is an inference from the value pattern, not a coded fact)VP= Vendor's (Seller's) Part Number —6DDDTP459
Only one line item is present, consistent with lineItemCount: 1 and totalLineItems: "1".
5. References & Totals
REF segments:
| Qualifier | Value | Interpretation |
|---|---|---|
CO |
0332424801 |
Customer Order Number — a customer-assigned order reference |
EU |
450176628677 |
End User's Reference Number — ties the order to a specific end-user identifier, consistent with the individual Ship-To (Alex Rivera) |
CTT (Transaction Totals):
- Count of line items = 1 (matches the single PO1 segment; no hash total value was provided in the parsed facts).
Contacts (PER segments) — four contact roles are listed, indicating a formal licensing workflow:
| Function Code | Role | Name |
|---|---|---|
BD |
Buyer's Designee/Broker/Dept. contact | Licensing 7 |
AP |
Accounts Payable contact | ORDER FLOW TEAM |
IC |
Information Contact | PAT MORGAN |
FF |
Freight Follow-Up contact | SAM ELLIS |
All contact phone/fax/email details are redacted (PII) and not available for review.
Consultant note: This 850 appears to be a license renewal or license order PO (single line, 12-month contract dates, PO number literally "LICENSEPO") rather than a physical-goods purchase order, despite carrying standard PO1/TD5/FOB freight-related segments in the histogram (TD5 and FOB present but no decoded values supplied — recommend reviewing raw segments if freight/routing details are needed).