- Created by Ashhad Alam , last modified on Jun 16, 2023
You are viewing an old version of this content. View the current version.
Compare with Current View Version History
« Previous Version 21 Current »
Electronic Data Interchange (EDI) transactions have become a vital component of modern supply chain management, particularly in the manufacturing industry. With the increasing demand for cost-effective and efficient methods of conducting business transactions, EDI has revolutionized the way manufacturing companies communicate with their suppliers, customers, and other partners in the supply chain. EDI transactions in the manufacturing industry include transactions related to purchasing, invoicing, shipping, inventory management, and more. The use of EDI transactions has helped manufacturing companies streamline their business processes, reduce errors, improve data accuracy, and ultimately increase productivity. In this context, it is crucial for manufacturing companies to understand the benefits of EDI transactions and adopt them to stay competitive in today's fast-paced business environment.
Adeptia also offers EDI solution for manufacturing that comprises the following EDI Transactions:
This Transaction is used to place an order for goods or services between trading partners. The 850 Purchase Order message provides information about the products or services being ordered, including their quantities, prices, and delivery details.
Details | EDI 850 4010 Inbound Transaction details | EDI 850 4060 Inbound Transaction details | EDI 850 5010 Inbound Transaction details |
|---|---|---|---|
Name | Purchase Order EDI 850 4010 Inbound to SAP | Purchase Order EDI 850 4060 Inbound to SAP | Purchase Order EDI 850 5010 Inbound to SAP |
Description | Inbound Transaction to receive Purchase Order EDI 850 4010 and generate SAP IDOC Orders. | Inbound Transaction to receive Purchase Order EDI 850 4060 and generate SAP IDOC Orders. | Inbound Transaction to receive Purchase Order EDI 850 5010 and generate SAP IDOC Orders. |
Type | EDI Inbound | EDI Inbound | EDI Inbound |
Network | Manufacturing | Manufacturing | Manufacturing |
Partner Name | Manufacturing Partner | Manufacturing Partner | Manufacturing Partner |
Project | EDI Manufacturing | EDI Manufacturing | EDI Manufacturing |
EDI Standard | X12 | X12 | X12 |
EDI Standard Version | 4010 | 4060 | 5010 |
Transaction Set | 850 | 850 | 850 |
Source and Target | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Inbound_850_4010_SourceFile.edi | EDI_Inbound_850_4060_SourceFile.edi | EDI_Inbound_850_5010_SourceFile.edi |
Output File Name Pattern | PurchaseOrder_SAP_Orders_yyyymmdd_HHmmss.SSS.idoc For example, PurchaseOrder_SAP_Orders_20220323_163245.001.idoc | PurchaseOrder_SAP_Orders_yyyymmdd_HHmmss.SSS.idoc For example, PurchaseOrder_SAP_Orders_20220323_163245.001.idoc | PurchaseOrder_SAP_Orders_yyyymmdd_HHmmss.SSS.idoc For example, PurchaseOrder_SAP_Orders_20220323_163245.001.idoc |
Trigger Type | File Exist | File Exist | File Exist |
Action Type | Create File | Create File | Create File |
This Transaction is used to confirm the receipt of a purchase order. The 855 message is typically sent by the seller to the buyer in response to an EDI 850 Purchase Order.
Details | EDI 855 4010 Outbound Transaction details | EDI 855 4060 Outbound Transaction details | EDI 855 5010 Outbound Transaction details |
|---|---|---|---|
Name | Purchase Order Acknowledgement EDI 855 4010 Outbound from SAP | Purchase Order Acknowledgement EDI 855 4060 Outbound from SAP | Purchase Order Acknowledgement EDI 855 5010 Outbound from SAP |
Description | Outbound Transaction to send Purchase Order Acknowledgement EDI 855 4010 against the received SAP IDOC Orders. | Outbound Transaction to send Purchase Order Acknowledgement EDI 855 4060 against the received SAP IDOC Orders. | Outbound Transaction to send Purchase Order Acknowledgement EDI 855 5010 against the received SAP IDOC Orders. |
Type | EDI Outbound | EDI Outbound | EDI Outbound |
Network | Manufacturing | Manufacturing | Manufacturing |
Partner Name | Manufacturing Partner | Manufacturing Partner | Manufacturing Partner |
Project | EDI Manufacturing | EDI Manufacturing | EDI Manufacturing |
EDI Standard | X12 | X12 | X12 |
EDI Standard Version | 4010 | 4060 | 5010 |
Transaction Set | 855 | 855 | 855 |
Source and Target | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Outbound_855_4010_SourceFile.idoc | EDI_Outbound_855_4060_SourceFile.idoc | EDI_Outbound_855_5010_SourceFile.idoc |
Output File Name Pattern | PurchaseOrderAcknowledgement_EDI_855_4010_yyyymmdd_HHmmss.SSS.edi For example, PurchaseOrderAcknowledgement_EDI_855_4010_20220118_161356.023.edi | PurchaseOrderAcknowledgement_EDI_855_4060_yyyyddmm_HHmmss.SSS.edi For example, PurchaseOrderAcknowledgement_EDI_855_4060_20220118_161356.023.edi | PurchaseOrderAcknowledgement_EDI_855_5010_yyyymmdd_HHmmss.SSS.edi For example, PurchaseOrderAcknowledgement_EDI_855_5010_20220118_161356.023.edi |
Trigger Type | File Exist | File Exist | File Exist |
Action Type | Create File | Create File | Create File |
This Transaction is used to communicate details of a shipment from a seller to a buyer. The 856 message provides information about the contents of a shipment, including the products being shipped, the quantities, and the expected delivery dates.
EDI 856 4010 Outbound Transaction details | |
|---|---|
Name | Advanced Shipment Notice EDI 856 4010 Outbound from XML |
Description | Outbound Transaction to send Advanced Shipment Notice EDI 856 4010 from the received XML File. |
Type | EDI Outbound |
Network | Manufacturing |
Partner Name | Manufacturing Partner |
Project | EDI Manufacturing |
EDI Standard | X12 |
EDI Standard Version | 4010 |
Transaction Set | 856 |
Source and Target | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Outbound_856_4010_SourceFile.xml |
Output File Name Pattern | AdvancedShipmentNotice_EDI_856_4010_yyyymmdd_HHmmss.SSS.edi For example, AdvancedShipmentNotice_EDI_856_4010_20230223_213131.456.edi |
Trigger Type | File Exist |
Action Type | Create File |
This Transaction is used to send an invoice for goods or services from a seller to a buyer. The 810 message provides details of the invoice, including the items being billed, the quantities, and the prices.
Details | EDI 810 4010 Outbound Transaction details | EDI 810 4060 Outbound Transaction details | EDI 810 5010 Outbound Transaction details |
|---|---|---|---|
Name | Invoice EDI 810 4010 Outbound from SAP | Invoice EDI 810 4060 Outbound from SAP | Invoice EDI 810 5010 Outbound from SAP |
Description | Outbound Transaction to send Invoice EDI 810 4010 from the received SAP IDOC Invoices. | Outbound transaction to send Invoice EDI 810 4060 from the received SAP IDOC Invoices. | Outbound transaction to send Invoice EDI 810 5010 from the received SAP IDOC Invoices. |
Type | EDI Outbound | EDI Outbound | EDI Outbound |
Network | Manufacturing | Manufacturing | Manufacturing |
Partner Name | Manufacturing Partner | Manufacturing Partner | Manufacturing Partner |
Project | EDI Manufacturing | EDI Manufacturing | EDI Manufacturing |
EDI Standard | X12 | X12 | X12 |
EDI Standard Version | 4010 | 4060 | 5010 |
Transaction Set | 810 | 810 | 810 |
Source and Target | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Outbound_810_4010_SourcrFile.idoc | EDI_Outbound_810_4060_SourcrFile.idoc | EDI_Outbound_810_5010_SourcrFile.idoc |
Output File Name Pattern | Invoice_EDI_810_4010_yyyymmdd_HHmmss.SSS.edi For example, Invoice_EDI_810_4010_20210616_154531.006.edi | Invoice_EDI_810_4060_yyyymmdd_HHmmss.SSS.edi For example, Invoice_EDI_810_4060_20210616_154531.006.edi | Invoice_EDI_810_5010_yyyymmdd_HHmmss.SSS.edi For example, Invoice_EDI_810_5010_20210616_154531.006.edi |
Trigger Type | File Exist | File Exist | File Exist |
Action Type | Create File | Create File | Create File |
EDI 810 5010 Outbound Transaction details | |
|---|---|
Name | Invoice EDI 810 5010 Outbound from XML |
Description | Outbound Transaction to send Invoice EDI 810 5010 from the received XML file. |
Type | EDI Outbound |
Network | Manufacturing |
Partner Name | Manufacturing Partner |
Project | EDI Manufacturing |
EDI Standard | X12 |
EDI Standard Version | 5010 |
Transaction Set | 810 |
Source and Target | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Outbound_810_5010_SourceFile.xml |
Target File Name Pattern | Invoice_EDI_810_5010_yyyymmdd_HHmmss.SSS |
Trigger Type | File Exist |
Action Type | Create File |
This Transaction is used to transmit payment and remittance information from a buyer to a seller. The 820 message provides details of the payment, including the amount, payment date, and any deductions or adjustments.
Details | EDI 820 4010 Outbound Transaction details |
|---|---|
Name | Payment Order EDI 820 4010 Outbound from xml |
Description | Outbound Transaction to send Payment Order Remittance EDI 820 4010 from the received canonical XML file. |
Type | EDI Outbound |
Network | Manufacturing |
Partner Name | Manufacturing Partner |
Project | EDI Manufacturing |
EDI Standard | X12 |
EDI Standard Version | 4010 |
Transaction Set | 820 |
Source and Target | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Outbound_820_4010_SourceFile.xml |
Output File Name Pattern | PaymentOrder_EDI_820_4010_month-dd-yyyy_HH:mm:ss.edi For example, PaymentOrder_EDI_820_4010_Feb-16-2022_15:16:35.edi |
Trigger Type | File Exist |
Action Type | Create File |
EDI 820 4010 Inbound Transaction details | |
|---|---|
Name | Payment Order EDI 820 4010 Inbound to XML |
Description | Inbound Transaction to receive Payment Order Remittance EDI 820 4010 and generate canonical XML file. |
Type | EDI Inbound |
Network | Manufacturing |
Partner Name | Manufacturing Partner |
Project | EDI Manufacturing |
EDI Standard | X12 |
EDI Standard Version | 4010 |
Transaction Set | 820 |
Source and Target | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Inbound_820_4010_SourceFile.edi |
Target File Name Pattern | PaymentOrder_EDI_820_4010_XML_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, PaymentOrder_EDI_820_4010_XML_Output_Dec-22-2023_18:25:32.006.xml |
Trigger Type | File Exist |
Action Type | Create File |
This Transaction is used to instruct a warehouse to ship goods to a buyer. The 940 message provides details of the shipment, including the items being shipped, the quantities, and the shipping instructions.
Details | EDI 940 4010 Outbound Transaction details |
|---|---|
Name | Warehouse Shipping Order EDI 940 4010 Outbound From SAP |
Description | Outbound Transaction to send Warehouse Shipping Order EDI 940 4010 from the received SAP IDOC DELVRY. |
Type | EDI Outbound |
Network | Manufacturing |
Partner Name | Manufacturing Partner |
Project | EDI Manufacturing |
EDI Standard | X12 |
EDI Standard Version | 4010 |
Transaction Set | 940 |
Source and Target | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Outbound_940_4010_SourceFile.idoc |
Output File Name Pattern | WarehouseShippingOrder_EDI_940_4010_IDoc_Output_yyyymmdd_hhmmss.SSS.edi For example, WarehouseShippingOrder_EDI_940_4010_IDoc_Output_20220325_192338.165.edi |
Trigger Type | File Exist |
Action Type | Create File |
This Transaction is used to communicate details of a shipment from a warehouse to a buyer. The 945 message provides information about the contents of a shipment, including the products being shipped, the quantities, and the expected delivery dates.
EDI 945 4010 Inbound Transaction details | |
|---|---|
Name | Warehouse Shipping Advice EDI 945 4010 Inbound to SAP |
Description | Inbound transaction to receive Warehouse Shipping Advice EDI 945 4010 and generate SAP IDOC DELVRY. |
Type | EDI Inbound |
Network | Manufacturing |
Partner Name | Manufacturing Partner |
Project | EDI Manufacturing |
EDI Standard | X12 |
EDI Standard Version | 4010 |
Transaction Set | 945 |
Source and Target | SFTP, Adeptia hosted FTP server |
Source File Name | EDI_Inbound_945_4010_SourceFile.edi |
Target File Name Pattern | Warehouse_Shipping_Advice_EDI_945_4010_Idoc_Output_month-dd-yyyy_hh:mm:ss.SSS.xml For example, Warehouse_Shipping_Advice_EDI_945_4010_Idoc_Output_June-16-2021_17:15:20.005.xml |
Trigger Type | File Exist |
Action Type | Create File |
This Transaction is used to send the response by acknowledging the receipt and validity of the transaction, and providing information on any errors or issues that were encountered during processing. It contains information such as the sender and receiver of the original transaction, the date and time the transaction was received, and a status code indicating whether the transaction was accepted or rejected.
When you want to send an acknowledgment against an Inbound EDI Transaction, you need to use an ACK EDI 997 Outbound Transaction.
When you want to receive an acknowledgment against an Outbound EDI Transaction, you need to use an ACK EDI 997 Inbound Transaction.
Details | ACK EDI 997 5010 Outbound Transaction details | ACK EDI 997 4060 Outbound Transaction details | ACK EDI 997 4010 Outbound Transaction details |
|---|---|---|---|
Name | Manufacturing Partner ACK EDI 997 5010 Outbound | Manufacturing Partner ACK EDI 997 4060 Outbound | Manufacturing Partner ACK EDI 997 4010 Outbound |
Description | EDI Acknowledgement 997 (ACK) 5010 version to be used for all Inbound EDI 5010 transactions for Manufacturing Trading Partner. | EDI Acknowledgement 997 (ACK) 4060 version to be used for all Inbound EDI 4060 transactions for Manufacturing Trading Partner. | EDI Acknowledgement 997 (ACK) 4010 version to be used for all Inbound EDI 4010 transactions for Manufacturing Trading Partner. |
Type | EDI Outbound | EDI Outbound | EDI Outbound |
Network | Manufacturing | Manufacturing | Manufacturing |
Partner Name | Manufacturing Partner | Manufacturing Partner | Manufacturing Partner |
Project | EDI Manufacturing | EDI Manufacturing | EDI Manufacturing |
EDI Standard | X12 | X12 | X12 |
EDI Standard Version | 5010 | 4060 | 4010 |
Transaction Set | 997 | 997 | 997 |
Target | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server |
Source File Name | TBD. Is this parameter valid here? | TBD. Is this parameter valid here? | TBD. Is this parameter valid here? |
Target File Name Pattern | edi_ack_997_5010_manufacturing_yyyymmdd_HHmmss.SSS.txt For example, edi_ack_997_5010_manufacturing_20230312_141625.168.txt | edi_ack_997_4060_manufacturing_yyyymmdd_HHmmss.SSS.txt For example, edi_ack_997_4060_manufacturing_20230312_141625.168.txt | edi_ack_997_4010_manufacturing_yyyyddmm_HHmmss.SSS.txt For example, edi_ack_997_4010_manufacturing_20230312_141625.168.txt |
Action Type | Create File | Create File | Create File |
Details | ACK EDI 997 5010 Inbound Transaction details | ACK EDI 997 4060 Inbound Transaction details | ACK EDI 997 4010 Inbound Transaction details |
|---|---|---|---|
Name | Manufacturing Partner ACK EDI 997 5010 Inbound | Manufacturing Partner ACK EDI 997 4060 Inbound | Manufacturing Partner ACK EDI 997 4010 Inbound |
Description | EDI Acknowledgement 997 (ACK) 5010 version to be used for all Outbound EDI 5010 transactions for Manufacturing Trading Partner. | EDI Acknowledgement 997 (ACK) 4060 version to be used for all Outbound EDI 4060 transactions for Manufacturing Trading Partner. | EDI Acknowledgement 997 (ACK) 4010 version to be used for all Outbound EDI 4010 transactions for Manufacturing Trading Partner. |
Type | EDI Inbound | EDI Inbound | EDI Inbound |
Network | Manufacturing | Manufacturing | Manufacturing |
Partner Name | Manufacturing Partner | Manufacturing Partner | Manufacturing Partner |
Project | EDI Manufacturing | EDI Manufacturing | EDI Manufacturing |
EDI Standard | X12 | X12 | X12 |
EDI Standard Version | 5010 | 4060 | 4010 |
Transaction Set | 997 | 997 | 997 |
Source | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server | SFTP, Adeptia hosted FTP server |
Source File Name | TBD. Is this parameter valid here? | TBD. Is this parameter valid here? | TBD. Is this parameter valid here? |
Trigger Type | File Exist | File Exist | File Exist |
- No labels