Welcome to the Emery Jensen EDI integration guide. In just a few steps, you’ll learn how to connect your Flxpoint source with Emery Jensen’s EDI feed to automate data retrieval, including fulfillment acknowledgements. Follow along below to configure your credentials and streamline your workflow.
How to Connect
Step 1: Log into your Flxpoint account and navigate to the Sources tab.
Step 2: Click on Configure Single Source (or + Add Source)
to begin creating a new source.
Step 3: Fill in your source details (e.g., vendor name, fulfillment preferences).
Once completed, click Save.
Step 4: After saving, navigate to
Get Fulfillment Request Acknowledgements under
Integrations in the left menu. If you see
"No integrations have been configured for this process yet",
click Start Creating Integrations.
Step 5: From the list of Custom Integrations or Standard Integrations,
locate and select Emery Jensen Distribution.
This will open the connection setup screen.
Step 6: In the New Emery Jensen Distribution Connection form,
enter your Connection Name, FTP Protocol, FTP Host,
FTP Port, FTP User, and FTP Password.
Advanced Settings:
Maintain Constant Connection – keeps an active FTP session throughout the process.
Use Unbuffered Private Data Channel – useful for secure FTPS connections
with “534 Policy requires SSL” errors.
Advanced Settings:
Step 7: Click Test Connection to ensure your credentials
are valid. Once verified, click Save Connection.
Step 8: You’ll see the Configure Settings screen.
Provide your Outbound Remote File Folder and Inbound Remote File Folder
to specify where Flxpoint will place or retrieve EDI files.
Next, enter:
Our Sender/Receiver Qualifier and Our Sender/Receiver ID
Their Sender/Receiver Qualifier and Their Sender/Receiver ID
These EDI qualifiers and IDs ensure acknowledgements are exchanged correctly.
Click Save and Proceed when finished.
Step 9: Next, select or create your Mapping Template
under Define a Mapping Template. Map the EDI fields (e.g., PO Number,
Acknowledgement Codes) to Flxpoint’s corresponding fields. Once mapped, click
Save and Complete.
Step 10: Your Emery Jensen integration for
Get Fulfillment Request Acknowledgements is now active.
Flxpoint will begin retrieving acknowledgements from your Emery Jensen EDI feed
according to your scheduled settings.
Order Operations
Flxpoint manages the entire order lifecycle, from submitting orders to your vendors for fulfillment to retrieving shipment details and acknowledgements. This ensures real-time visibility and synchronization between order processing, vendor updates, and shipment tracking.
Get Shipments
Supported:
The Emery Jensen Get Shipments integration supports EDI 856 files for capturing shipment details. Flxpoint connects to your configured FTP location, downloads the 856 file, and processes key segments to extract tracking and order fulfillment information:
By leveraging these mapping options, you can tailor how shipment data flows into Flxpoint—ensuring accurate and timely tracking information for each order.
The Emery Jensen Get Shipments integration supports EDI 856 files for capturing shipment details. Flxpoint connects to your configured FTP location, downloads the 856 file, and processes key segments to extract tracking and order fulfillment information:
- BSN Segment (Ship Notice Start): Retrieves the Transaction Set Purpose Code (BSN01),
Shipment Date (BSN03), and Shipment Time (BSN04).
Transaction Set Purpose Codes:
- 00 = Tracking Notice
- 05 = Replacement Parts (Not Supported)
- HL Segment (Hierarchical Level): Used to identify the shipment level (HL03 = S)
and item-level hierarchies (HL03 = I).
- TD5 Segment (Carrier Details): Provides carrier and routing information such as
SCAC (TD503) and Shipment Speed (TD505).
- REF-2I Segment (Tracking Number): Captures the tracking or PRO number (REF02).
- DTM Segment (Shipment Date Information): Indicates the date the shipment began
(DTM01 = 011).
- PRF Segment (Purchase Order Reference): Contains the Purchase Order Number
(PRF01).
- HL-ITEM Segment (Item-Level Hierarchy): Breaks down each item shipped.
- LIN Segment: Vendor Part Number (LIN02, LIN03) and UPC (LIN04, LIN05)
- SN1 Segment: Number of Units Shipped (SN102) and Unit of Measurement Code (SN103)
Connection & Settings:
This process requires a custom FTP connection to download the EDI 856 files. In addition to standard FTP credentials, the following fields are exposed in Flxpoint for EDI-specific settings:
- Our Qualifier / Our Sender/Receiver ID
- Their Qualifier / Their Sender/Receiver ID
- Inbound Remote Folder / Outbound Remote Folder
Mapping Template Overview:
Flxpoint provides a Mapping Template specifically for Shipment processing. You can map EDI fields (e.g., Tracking Number, Vendor Part Number, UPC) to Flxpoint’s internal fields (e.g., Carrier Info, SKU, Quantity, etc.). The template editor offers several options:
- Field: Directly map an EDI field to a Flxpoint field.
- Value: Assign a fixed value.
- Mapping Set: Apply predefined transformations or lookups.
- Rules: Use conditional logic for more complex scenarios.
By leveraging these mapping options, you can tailor how shipment data flows into Flxpoint—ensuring accurate and timely tracking information for each order.
Get Fulfillment Acknowledgements
Supported:
The Emery Jensen Get Fulfillment Request Acknowledgements integration supports EDI 855 files for acknowledging purchase orders. Flxpoint connects to your configured FTP location, downloads the 855 file, and processes key segments to capture acknowledgment details:
These ensure the correct exchange of EDI 855 files.
If you encounter line item status codes beyond the common ACK codes, Flxpoint defaults them to “Acknowledged.” This ensures orders continue to process even when Emery Jensen indicates minor changes.
With the Emery Jensen Get Fulfillment Request Acknowledgements integration, you can streamline how PO acknowledgements flow into Flxpoint, saving time, reducing errors, and maintaining accurate order updates.
The Emery Jensen Get Fulfillment Request Acknowledgements integration supports EDI 855 files for acknowledging purchase orders. Flxpoint connects to your configured FTP location, downloads the 855 file, and processes key segments to capture acknowledgment details:
- BAK Segment: Retrieves the Purchase Order Number (BAK03) and Date (BAK04).
- PO1 Segment: Extracts item-level details (e.g., Quantity, Unit Price,
Vendor/Customer Product Numbers, UPC).
- ACK Segment: Determines the line item status code and whether an item is acknowledged,
rejected, canceled, or changed. Examples include:
- IA – No Change
- IQ – Quantity Change
- R1 – Item Rejected
- R4 – Cancelled Item
- DR – Date Change
- IP – Price Change
- IC – More than One Change
Cancellations:
Certain status codes (e.g., R4) fully or partially cancel line items. If all items are canceled, the order is treated as fully canceled. If only some items are canceled, Flxpoint treats the order as a partial cancellation.
Certain status codes (e.g., R4) fully or partially cancel line items. If all items are canceled, the order is treated as fully canceled. If only some items are canceled, Flxpoint treats the order as a partial cancellation.
Partial Acknowledgements:
If some items are acknowledged (IA) while others are changed (IQ, IP, etc.) or canceled (R4), Flxpoint marks the order as partially acknowledged. This allows you to see which items remain valid and which have been updated or removed.
If some items are acknowledged (IA) while others are changed (IQ, IP, etc.) or canceled (R4), Flxpoint marks the order as partially acknowledged. This allows you to see which items remain valid and which have been updated or removed.
Item Association:
The PO1 segment also includes references for vendor or customer product numbers (PO106, PO107, PO108, PO109) and UPC (PO110, PO111), ensuring items in the EDI file are correctly matched to items in Flxpoint.
The PO1 segment also includes references for vendor or customer product numbers (PO106, PO107, PO108, PO109) and UPC (PO110, PO111), ensuring items in the EDI file are correctly matched to items in Flxpoint.
Connection & Settings:
This process requires a custom FTP connection. In addition to standard FTP credentials,
the following fields are available in Flxpoint for EDI-specific settings:
- Our Qualifier / Our Sender/Receiver ID
- Their Qualifier / Their Sender/Receiver ID
- Inbound Remote Folder / Outbound Remote Folder
Mapping Template Overview:
Flxpoint provides a Mapping Template specifically for Fulfillment Request Acknowledgements.
You can map EDI fields, such as the line item status, quantity, or vendor item number, to
Flxpoint’s internal fields (e.g., Acknowledgement Code, Quantity,
SKU, etc.). The template editor offers options for:
- Field: Directly map an EDI field to a Flxpoint field.
- Value: Assign a fixed value.
- Mapping Set: Apply predefined transformations or lookups.
- Rules: Use conditional logic for more complex scenarios.
If you encounter line item status codes beyond the common ACK codes, Flxpoint defaults them to “Acknowledged.” This ensures orders continue to process even when Emery Jensen indicates minor changes.
With the Emery Jensen Get Fulfillment Request Acknowledgements integration, you can streamline how PO acknowledgements flow into Flxpoint, saving time, reducing errors, and maintaining accurate order updates.
Get Invoices
Supported:
The Emery Jensen Get Invoices integration supports EDI 810 files for capturing invoice details. Flxpoint connects to your configured FTP location, downloads the 810 file, and processes key segments to extract relevant data:
By leveraging these mapping options, you can tailor how invoice data flows into Flxpoint—ensuring accurate and efficient invoice capture.
The Emery Jensen Get Invoices integration supports EDI 810 files for capturing invoice details. Flxpoint connects to your configured FTP location, downloads the 810 file, and processes key segments to extract relevant data:
- BIG Segment (Invoice Beginning): Retrieves the Invoice Date (BIG01),
Invoice Number (BIG02), Purchase Order Number (BIG04),
and Transaction Type Code (BIG07).
Transaction Type Codes:
- DI = Debit Invoice
- CR = Credit Invoice
- IT1 Segment (Line Items): Captures line-level detail, including
Quantity Invoiced (IT102), Unit of Measurement Code (IT103),
Unit Price (IT104), Vendor Number (IT106, IT107),
and UPC Code (IT108, IT109).
- PID Segment (Product Descriptions): Includes descriptive information
about each line item (PID05).
- TDS Segment (Total Invoice Amount): Shows the total amount being invoiced
(TDS01).
- SAC Segment (Allowances & Charges): Indicates whether an item or total is a
Charge (SAC01 = C) or an Allowance (SAC01 = A), and applies codes such as
D240 (Freight), D500 (Handling), F800 (Promotional Allowance),
H750 (Tax), and more. The corresponding amount is stored in SAC05.
Connection & Settings:
This process requires a custom FTP connection to download the EDI 810 files. In addition to standard FTP credentials, the following fields are exposed in Flxpoint for EDI-specific settings:
- Our Qualifier / Our Sender/Receiver ID
- Their Qualifier / Their Sender/Receiver ID
- Inbound Remote Folder / Outbound Remote Folder
Mapping Template Overview:
Flxpoint provides a Mapping Template specifically for Invoice processing. You can map EDI fields (e.g., Invoice Number, Quantity, Unit Price) to Flxpoint’s internal fields (e.g., Order Number, Quantity, Cost, etc.). The template editor offers several options:
- Field: Directly map an EDI field to a Flxpoint field.
- Value: Assign a fixed value (e.g., if you always want a certain field to have a static value).
- Mapping Set: Apply predefined transformations or lookups.
- Rules: Use conditional logic for more complex scenarios.
By leveraging these mapping options, you can tailor how invoice data flows into Flxpoint—ensuring accurate and efficient invoice capture.