Receiving EDI Purchase Order document (850) in Odoo

An EDI 850 PO inbound transaction occurs when an Odoo Seller’s system receives an EDI 850 Purchase Order (PO) document from a trading partner (buyer). That inbound PO generates a new Sales Order (SO) in the seller’s system.

How EDI PO 850 (Inbound) Works with Steersman’s Odoo Integration

1. A trading partner (buyer) will initiate a purchase order in their system. Their system will send the order to their EDI VAN (Value Added Network), which is linked to. Steersman’s EDI VAN (Kleinschmidt)
2. The trading partner’s (buyer’s) EDI system converts their outbound EDI 850 PO file into a standardized EDI format and then sends it to Kleinschmidt.
3. Kleinschmidt’s VAN translates the data into JSON format(human-readable format) and sends that data to Odoo.
4. Steersman’s Odoo-integrated EDI system will generate a sales order and map the translated data to the correct fields.
5. Depending on what has been configured, the trading partner’s (buyer’s) original PO will appear in Odoo as a new SO draft or a confirmed SO in the Odoo database.

EDI Event Logs

• Anytime an EDI event is received, it is added to a detailed log of EDI events in Odoo. This log will display the data received from the trading partner (buyer) and link it to the SO generated by the event.
• If, for some reason, a field (ex, product identifier) on the EDI event does not match a record in your Odoo database, an error message will appear in the header of the event log describing the issue.
• Steersman’s EDI integration also has a unique way of dealing with price discrepancies.
  • Let’s say you receive an incoming 850(PO) that has a different product price than you have in your internal price list, you can choose to mange the price mismatch by either using the price on the original document(buyer price), using the price you have set in your internal price list, or simply logging a warning in the chatter of the order without confirming it.

Common Fields Steersman’s EDI Integration Sends and Receives for 850 Documents

• PO number
• Ship date
• Must deliver by date
• Release number
• Buyer contact details (Name, phone #, email…)
• Internal tracking number
• Order date
• Billing information
• shipping address
• Payment terms (discounts, currency code, etc.)
• Shipping terms (carrier, routing, shipping payment, etc.)
• Product identifiers (product code, SKU, part number, etc.)
• Product description
• Product details (quantity, price, UoM, etc.)

Most trading partners have specific EDI requirements; Steersman offers other customizable fields to fulfill these requirements.