https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/ Recent content in EDI and integration on Product Documentation Hugo en-US https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-interface/ Mon, 01 Jan 0001 00:00:00 +0000 https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-interface/ <h2 id="purpose">Purpose</h2> <p>This page describes the EDI interface in Automotive from basic configuration through partner and message-type setup to the operational processing of inbound and outbound messages. It serves as the central orientation point for scenarios in which call-offs, invoices, delivery-note data, or transport information are exchanged automatically with partners.</p> <h2 id="business-value">Business value</h2> <ul> <li>You choose a suitable transmission mode for partner communication.</li> <li>You set up partners, message types, and number series so that messages are created, recognized, and archived reliably.</li> <li>You understand the difference between inbound and outbound message processing.</li> <li>You use protocol and history for error analysis, evidence, and restart scenarios.</li> </ul> <h2 id="core-edi-processing-logic">Core EDI processing logic</h2> <p>The EDI interface connects Business Central with converters, web services, or file locations. The process always follows the same core logic:</p> https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-message-processing/ Mon, 01 Jan 0001 00:00:00 +0000 https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-message-processing/ <h2 id="purpose">Purpose</h2> <p>This page describes operational message processing in Automotive. It complements the EDI setup with the daily work on inbound and outbound messages, the EDI documents generated from them, and the related sales and transport objects.</p> <h2 id="core-principle">Core principle</h2> <p>Message processing is the central place for all inbound and outbound message types. This is where the live operation is managed. It is not the place where the EDI baseline is configured.</p> https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-setup-and-partners/ Mon, 01 Jan 0001 00:00:00 +0000 https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-setup-and-partners/ <h2 id="purpose">Purpose</h2> <p>This page deepens the EDI interface around the concrete setup of transmission type, number series, partners, partner lines, message types, and field mapping. It complements the EDI overview page with the fields and project decisions that were described in detail in the legacy wiki.</p> <h2 id="build-edi-setup-in-a-clear-order">Build EDI Setup in a clear order</h2> <p>The base setup is structured into several tabs. Do not maintain them in parallel. Work through them in a fixed sequence.</p> https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-protocol-and-history/ Mon, 01 Jan 0001 00:00:00 +0000 https://bc.help.be-terna.com/en-us/docs/business-central/cross-industry-solutions/automotive/edi/edi-protocol-and-history/ <h2 id="purpose">Purpose</h2> <p>This page describes the historical traceability of the EDI interface. The focus is on the EDI log as the technical evidence trail and on the history view for inbound delivery-note EDI in EDL/consignment and purchasing scenarios.</p> <h2 id="edi-protocol-as-the-technical-evidence-trail">EDI protocol as the technical evidence trail</h2> <p>The EDI protocol stores all interface actions in a traceable way. It is therefore the first place to look when a message is expected but it is unclear whether it was imported, processed, sent, or ended with an error.</p>