Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 12 Next »

System Integration is a process of connecting different IT systems (applications) so that the data can be shared between these systems, as needed. This will help in lowering operational costs or improve workflow efficiency. Different integration methods are used to connect these systems.

We can use various integrations methods to connect to the client’s ERP system so that data can be transmitted from (or to) Seko systems. The common integrations methods used are API, EDI, or via flat files (like XML or CSV). Flat files like excel and CSV are not preferred options since most of the time these files are created manually and are prone to human typo errors.

Please refer to the below section for information on each of the connection types and what is required from the client/vendor before we can start development.

API

Partner API

We can connect to partner APIs to send/receive data (e.g. Shipment Booking). This will require development effort at our end.

What do we need from the partner for API:

  1. API endpoints → Providing information on how to connect to their system

  2. API documentation → Providing details on each field/parameter for the API

  3. A technical contact (from the partner-side) for testing and answering any questions related to the development

SEKO API

Partners can connect to SEKO API’s to send/receive data. We do not have any development effort on this other than providing credentials to client. The documentation for Seko API’s can be found here.

SEKO API’s can be used to connect to:

  1. Domestic system for quoting, booking and status

  2. CargoWise One for booking and status.

EDI

EDI (Electronic Data Interchange) is electronic exchange of business documents such as orders, invoices, shipment status etc. These documents are transmitted between the business partners in the form of structured data (aka specification document).

What do we need from the client for EDI:

  1. EDI Specification document.

  2. EDI Connection Type (AS2, VAN or sFTP)

  3. A technical contact for testing, or answering questions related to the setup/document

The common EDI specification documents are provided in the below table for easy reference. SEKO EDI spec is provided in the last column, if available. We can use either our document or client document for integration. Development effort will reduce if SEKO specification document is used for the integration.

EDI#

FUNCTION

DESCRIPTION

SPECIFICATION

EDI204

Load Tender

Used by shipper to offer or tender truckload or LTL shipment to a carrier

SEKO EDI204 Mapping Guide

EDI210

Invoice

Pricing for services

SEKO EDI210 Mapping Guide

EDI214

Status Message

Gives the buyer a status of their shipment

SEKO EDI214 Mapping Guide

EDI315

Ocean Status

Status update for ocean shipment

EDI850

Purchase Order

Customer orders product to ship to SEKO warehouse

EDI856

Ship Notice / Manifest

Supplier sends to customer for notification about upcoming delivery of shipment

SEKO EDI856 Mapping Guide

EDI860

Goods Receipt

Return message confirming products received in purchase order

EDI861

Inventory Summary

Summary of stock on hand at SEKO warehouse

EDI888

Parts Master

List of products that SEKO will stock on customers' behalf

EDI940

Sales Order

Request for shipment from SEKO warehouse to buyers' location

EDI945

Ship Confirmation

Return message confirming shipment has been shipped

EDI990

Response to Load Tender

Response to EDI204, determines whether carrier will pick up shipment

SEKO EDI990 Mapping Guide

EDI996

File Transfer Transactions

Used to transmit file information between both parties

  • No labels