Skip to content

EDX - Electronic Data eXchange#

General#

EDX - Electronic Data eXchange stands for the document exchange module of KUMAVISION 365. EDI documents are sent in different formats, e.g. EDIFACT, VDA, OpenTrans etc.. A converter takes over the conversion from the external format into the EDX internal XML format.

EDX then processes the converted messages and imports them into Microsoft Business Central. Required message acknowledgements are automatically sent within the internal document exchange. In the case of external EDI (electronic data interchange), the message acknowledgement must be coordinated with the EDI service provider.

The incoming messages are validated by the EDX module. This means that the message content is loaded into the EDX document and checked for accuracy, discrepancies and completeness. The user can manually correct the data in the EDX document and then create the corresponding Business Central document.

For incoming messages, a mapping between the external and the article units stored in Business Central is often required. For this purpose, the EDX module offers corresponding mapping tables.

The following diagram is intended to clarify the task EDX performs in the electronic document exchange:

Area Description
1. communication The communication of the data exchange parties takes place in this area.
Various protocols are used for the transmission. The transmission protocols are usually specified by the data sender. Automotive, for example, uses the OFTP2 protocol. The trade sector tends to use X.400 or AS2.
It is not always necessary to use a service provider for document exchange. For X.400 transmission, for example, FileWork from Telekom can be used. However, if the OFTP½ protocol is required, then it makes sense to transfer the task of document exchange to a service provider.
2. news converter The incoming messages are converted from the source format to the EDX target format using a converter. For example, EDIFACT messages are converted to EDX in-house format. For outgoing messages, the message is converted from EDX in-house format to the respective target format.
3. EDX Inhouse Format The in-house format maps the documents of the Business Central business processes in a defined format. EDX uses the XML format for this purpose. The documents are described in the "KUMAVISION EDI Guideline".
4. EDX Business Logic In this area, the previously converted documents are transferred into intermediate documents. With the "Business Logic" all relevant process steps are served, which are necessary for the examination of the document, creation as well as processing of the Business Central document. If it is possible by the document, an automation of the business process takes place.

Business processes#

The EDX module enables internal as well as external document exchange. BC documents can be exchanged within a group of companies as well as with external EDI partners.

Internal document exchange#

If there is a hierarchical company structure with several companies, then the document exchange can be implemented with the EDX module. Here, the documents of the individual companies can be exchanged among each other.

Prerequisites for internal document exchange:
* Main company and companies are in one databaseIn this case, the internal document exchange can be set up directly with the wizard.

  • Main company and companies are located in separate databaseIn this case, the document exchange must be set up manually.
  • There is a common network structure and all participants can access a shared network path

The following figure shows the document flow between customer and supplier in connection with the EDX module:

Main company = Customer Company = Supplier

External document exchange#

If documents are sent to an external partner (EDI), this is described below as external document exchange.

The external document exchange contains document types developed for use with EDI service providers. The EDI service provider receives the EDX messages, transforms them into the target format and transfers the messages to the recipient.

It is not absolutely necessary to use an EDI service provider. Depending on the requirements, the transformation and transfer can also be implemented as an in-house solution with corresponding modules.

Available vouchers#

The following documents are already available in XML format after installation:

Purchasing * Order outgoing * Order change outgoing * Order confirmation received * Purchasing delivery incoming * Purchase invoice incoming * Purchasing complaint outgoing

Sale * Sell order received * Sell order change incoming * Order confirmation outgoing * Sales offer starting * Outgoing delivery bill * Sales invoice starting * Sales credit outgoing * Sales complaint outgoing

Establishment#

The module has numerous configuration and customization options, which will be explained in more detail in the following chapters. The first part of the documentation covers all topics concerning administration and configuration. The second part describes the operation of the data exchange.

Entitlement rates#

About the installation of the EDX Apps are automatically different authorization sets integrated into your Business Central application. Assigning these authorization sets to your users or user groups ensures that the respective Users can get access to the connection and execute the functions depending on the assigned record.

Authorization record Description
EDX SETUP Permissions to read, write, modify as well as delete records for all EDX tables.
This permission set allows EDX setup as well as access to all EDX objects.
This role must be assigned to the BC Administrator as well as the task queue user.
EDX SALES Authorizations to read, write and modify data records related to the sales business process.
This role must be assigned to users from the Sales area.
EDX PURCHASE Authorizations to read, write as well as change data records which are related to the purchasing business process.
This role must be assigned to users from the purchasing area.
EDX EDI/IC Authorizations to execute the EDI and Intercompany business processes.
This role must be assigned to users from the Sales and Purchasing departments.
EDX OPENTRANS 1.0 Authorizations to run the OPENTRANS business processes.
This role must be assigned to users from the sales area.
EDX BASE DATA EXCHANGE Authorizations to execute the Basic Data Export business process.
This role must be assigned to users from the Sales and Purchasing departments.
EDX ONPREM This role must be assigned to all users if interfaces from the OnPrem domain are used (file transfer, FTP, etc.).
EDX WEBSERVICES This role must be assigned to the BC Administrator as well as the task queue user.
EDX KBA This role must be assigned to all users when the KUMAVSION KBA is installed.
EDX FACTORY This role must be assigned to all users when the KUMAVSION FACTORY is installed.
EDX TRADE This role must be assigned to all users if the KUMAVSION TRADE is installed.
EDX MED This role must be assigned to all users when the KUMAVSION MED is installed.

Roll Center#

The EDX Role Center represents the central work platform for the entire EDX module. All necessary information regarding documents (incoming/outgoing), items (incoming/outgoing) and configurations are displayed with corresponding stacks in the role center. Incoming and outgoing documents are displayed as links in the Purchasing, Sales and Logistics overviews, indicating the number of each. A click on the link opens the relevant document or an overview of the documents. It is therefore possible to navigate from the role center to all EDX relevant documents.

Furthermore, all settings as well as error entries and system messages are displayed in additional overviews.

EDX Setup#

In the EDX Setup, settings can be made that are valid for the entire module. The EDX Setup can be called up via the "Facilities and extensions" > "Service connections" > "KVSEDX Setup" start page.

In the "Interface directory" tab, the directories for documents, test as well as the productive must be defined.

Further entries are not necessary for the time being, as these are made with the "EDX Setup Wizard". Further information can be found in the section with the same name.

For completeness, all fields of the EDX setup are explained in more detail below:

Inforegister General#

Field Description
Test environment This flag controls whether the messages are processed in the subdirectory for the production or test database.
see "Interface directory" info tab
Database name Name of the current SQL database

Inforegister interface directory#

Field Description
Documents directory (UNC) Basic directory for electronic document exchange.
The path must refer to a network share and be written according to UNC notation.
Example: \server_name\EDX|
Test environment subdirectory Subdirectory for test environment
Subdirectory Productive Environment Subdirectory for productive environment

Inforegister Azure Storage#

Field Description
Memory account name Name of the Azure storage account that has been created. See Azure Environment: All Resources-> Storage Account
Shared Access Key Access key for the storage account
After selecting the storage account in the Azure environment, the access key (key1) can be retrieved and copied to the "Shared Access Key" field.
Container Name of the blob container in the storage account
Azure sub-directory Prod Subdirectory for productive data
Azure sub-directory test Subdirectory for test data
Enabled When enabled, the Azure Storage interface is registered as a service connection and can be used.

The Azure service connection is registered when you close the setup dialog. Before the Azure Connection Test action can be performed, the setup dialog must be closed and reopened.

Afterwards, the action "Azure connection test" can be executed.

The following actions are performed during the test: * Create Readme.txt file in container * List files in container * Read in the "Readme.txt" file * Delete the "Readme.txt" file.

Information register partner#

Field Description
Extension Vendor

EDX Partner Code
Extension Debitor EDX Partner Code Within the EDX module EDI partners are created based on a customer or vendor. The partner codes are composed of the respective BC vendor or customer number and the extension specified here.

Example:
Create an EDX partner based on the vendor 1000.
The EDX partner is managed as V1000.

The extension codes are freely selectable.
Both extension codes must be filled in.

Inforegister numbering#

All incoming EDX documents are first stored in EDX intermediate tables. For these EDX documents number series are necessary. If the EDX module is used exclusively for outgoing documents, then the specification of number series is not necessary.

Field Description
EDX order number Incoming order from the customer.
EDX Order change number Incoming order change from the customer.
EDX purchase delivery number Incoming sales delivery from the supplier.
EDX Purchase Invoice Number Incoming sales invoice from the supplier.
EDX order confirmation number Incoming order confirmation from the supplier.

Information register web service#

Field Description
Log input data web service Specifies logging of incoming web service calls. Logging takes place in the EDX inbox.
Log output data web service Specifies logging of outbound web service calls. Logging takes place in the EDX outbox.

Inforegister error handling#

Field Description
Time span until e-mail is sent The parameter "Time span until e-mail is sent" can be used to control the period for which the errors are collected. Only after the expiration of this time span the mail dispatch of all occurred errors takes place.
Error mail address Mail address to which error messages are sent.
Only error messages that occur within the server processing are sent.
The following list shows a few examples of when error mails are sent automatically:

An error occurs when reading an XML file.
Possible error causes:
• General errors within the XML file (Wellformed)
• The XML file does not match the expected schema

An error occurred during automatic further processing "Receiving a sales order".
Possible error causes:
• Within the sales order, a reference is made to a Business Central master data record (e.g. article number, article unit) which does not exist.
• When the sales order is created, queries are made which must be confirmed by the user (e.g. credit limit). These queries are not allowed in a background process.

An error occurs when sending an XML file.
Possible error causes:
• No authorization to write the output directory.

A link to call up the associated Business Central Page is provided in the error e-mail. For further information, please refer to the section "Sending e-mails einrichten".

Inforegister XML#

Field Description
Disable XML Byte Order Mark This switch can be used to control whether the XML message to be output should contain the byte Order Mark.

Inforegister Reorganization#

Field Description
Archive outputs / inputs that are older The date formula in the "Archive outputs/inputs that are older" fields can be used to specify the date from which EDX inputs/outputs are moved to the archive. Only outgoing items will be moved to the archive where no transmission error has occurred.
Outgoing items with transmission errors can be manually moved to the archive using the "Archive outgoing items with transmission errors" action.

In the case of incoming items, only completed acknowledgement messages are moved to the archive.
The archiving of other incoming messages, such as EDX sales orders, is controlled via the respective EDX document.

Inforegister BC Configuration#

Field Description
Use new article references Specifies whether new article references should be used.
Task maintenance items in seconds interval Once the switch is active, all EDX task queue items except for the "Reorganization" and "Send Mail" parameters are executed at one-second intervals.

Inforegister Facility Overview#

The fields on the "Setup Overview" info tab give an overview of which points are already set up in EDX.

EDX Setup Wizard#

To make the setup of the connection as comfortable as possible for the user, a setup wizard has been developed to guide you through the individual steps. This setup wizard can be called up via the EDX Setup menu ribbon ("More options" > "Action" > "Setup" > "EDX setup wizard").

The EDX setup wizard is started.

The "General" selection is used to create the document types as well as number series for incoming messages.

If you want to send purchase orders, delivery bills or invoices to another client, then select the "internal document exchange" function. For more information, see the "Internal document exchange" setup section.

EDX Document types#

When installed, the EDX module already has some document types which can be used for internal and external document exchange.

Establishment#

The EDX document types are created using the "EDX Setup Wizard" action within the EDX setup.

You can view the "EDX document types" using the call of the same name via the user search. The individual fields are explained in more detail below:

Field Description
Document Name of the EDX document
Description Description of the EDX document
Document direction Incoming/outgoing document
GS1 Business Message Standard Indicates whether the message is from the GS1 Business Message Standard.
Intercompany role Role of the document within the intercompany message exchange Debtor/creditor
Processing sequence Default value for the processing sequence.
This ensures that a purchase order confirmation is processed before the purchase delivery.
Field setting active Default value for the field setting.
If the document supports the field setting, then the field setting can be called up after the document has been assigned to an EDX partner.
See Field Settings Document Verification
Collective shipment allowed Default value for collective consignments.
See processing
Embed PDF allowed Specifies to include the associated Business Central PDF document as a base64 string in the message.
Messages coding Sets the message encoding.
Web service function The EDX document can be accessed via SOAP web service.
Web service function name Name of the associated web service function.

Distribution of EDX document types#

All EDX document types have a prefix that can be used to assign an area.

The areas are divided as follows:

Field Description
IC Internal document exchange
EXT External document exchange
These documents are used for EDX versions < 10 for external document exchange.
CC External document exchange Vouchers reconciled with clearing center
These documents are used from EDX version >= 10 for external document exchange.
See also KUMA EDI Guideline
Document Description Document direction
BASE CUSTOMER Basis debtor export Based on
BASE ITEM Base article export Based on
BASE VENDOR Base Vendor Export Based on
CC PURCHASE ORDER Send purchase order (CC) Based on
CC PURCHASE ORDER CHANGE Send purchase order change (CC) Based on
CC PURCHASE RETURN ORDER Send purchase complaint (CC) Based on
CC PURCHASE RETURN ORDER CHG Send purchase complaint change (CC) Based on
CC PURCHASE INVOICE Receive purchase invoice (CC) In-depth
CC PURCHASE RECEIPT Receive purchase delivery (CC) In-depth
CC PURCHASE ORDER CONF Receive purchase order confirmation (CC) In-depth
CC SALES INVOICE Send sales invoice (CC) Based on
CC SALES ORDER Receive sell order (CC) In-depth
CC SALES ORDER CHG Receive sell order change (CC) In-depth
CC SALES ORDER CONF Send order confirmation (CC) Based on
CC SALES SHIPMENT Send sales delivery (CC) Based on
CC DESPATCH ADVICE Send purchase delivery (CC) This message can only be used in connection with the KUMAVISION dispatch processing The message contains the assigned load carriers and their hierarchy. Based on
CC SALES CR.MEMO Send sales credit note (CC) Based on
CC SALES RETURN ORDER Send sales complaint (CC) Based on
CC SALES RETURN ORDER CHG Send sales complaint change (CC) Based on
CC SERVICE INVOICE Send service invoice (CC) Based on
CC SERVICE CR.MEMO Send service credit note (CC) Based on
CONFIRMATION RECEIVE Receive acknowledgement In-depth
CONFIRMATION SEND Send acknowledgement of receipt Based on
GS1 APP REC ACK IMP Receive acknowledgement In-depth
GS1 APP REC ACK IMP Send acknowledgement of receipt Based on
IC PURCHASE INVOICE Receive purchase invoice (IC) In-depth
IC PURCHASE ORDER Send purchase order to vendor (IC) Based on
IC PURCHASE ORDER CHG Send order change (IC) Based on
IC PURCHASE ORDER CONF Receive order confirmation (IC) In-depth
IC PURCHASE SHIPMENT Receive purchase delivery (IC) In-depth
IC SALES INVOICE Send sales invoice (IC) Based on
IC SALES ORDER Receive sell order (IC) In-depth
IC SALES ORDER CHG Sales change received (IC) In-depth
IC SALES ORDER CONF Send order confirmation (IC) Based on
IC SALES SHIPMENT Send sales delivery (IC) Based on
IC SALES DELFOR Receive delivery schedule (FACTORY only) In-depth

EDX Partner#

In order to be able to exchange documents, one or more partners must first be defined in the EDX module. These partners can be created based on existing accounts payable or accounts receivable.

EDX partners are managed under a code consisting of the respective Business Central creditor or debtor number and a prefix.

Before creating the EDX partner, the "Our account number" field must be defined in the vendor/customer.

Example for "Our account number": Role of the supplier: For customer 1000, 61000 is entered in the "Our account number" field. Role of the customer: For vendor 61000, 1000 is entered in the "Our account number" field.

Partner type debtor#

A new EDX partner is created directly from the partner overview. To do this, first call up the "EDX partners" via the user search.

The action "Create customer" creates a new EDX partner based on a customer.

For the EDIFACT UNB segment to be created, the fields GLN, data sender as well as recipient ID can be used.

The fields Data sender and Recipient ID are not subject to a format check. Accordingly, an ODETTE-Id, DUNS-No. etc. can be entered.

For the transmission of XInvoices to an EDI service provider, the "Routing Id." is required. see "IT Standards Coordination Office".

Basically all above mentioned fields have to be coordinated with the EDI service provider. The fields are transmitted within the CC messages invoice, credit bill as well as delivery bill in the element "Routing".

G/L account and unit mapping#

G/L accounts mapping#

In the internal document exchange, for example, it is possible to send purchase orders to an internal partner. Since no lines of the type resource can be entered in purchase orders, a mapping is necessary at this point. The G/L account mapping is opened directly from the "EDX Partner Overview" for the selected EDX partner.

One resource or G/L account no. can be entered per partner.

Example:
Partner V01254796
Resource: Cargo
G/L account no. 3400 (Internal freight)

These inputs lead to the following result: If a purchase order is sent, in which a line with the type G/L account and the no. 3400 exists, then this line is created at the recipient in the sales order as resource "Freight".

Units mapping#

A unit mapping is necessary to change the customer's unit code to your own unit code.

Example:
A customer orders 5 PCS, the unit code in BC is Piece. In this case, a mapping must be created for the translation from PCS to Piece.

The unit mapping is called up via the "EDX Partner Overview" via the menu ribbon.

It is not necessary to store a unit mapping for each EDX partner and article. As a rule, the unit "PCS" must be converted to the Business Central unit "piece" for all EDX partners and articles.

The following sequence is used to determine the unit mapping:

  1. Mapping with EDX Search partner, article and reference code
  2. Search mapping with article and reference code
  3. Mapping with EDX Partner and reference code search
  4. Search mapping with reference code

The unit mapping is used with the following documents: * Sell orders * Sales order changes * Purchase order confirmations * Purchasing deliveries * Purchase Invoices

For the outgoing documents, the unit mapping is performed only in the "Clearing Center Messages". * born sale delivery * born sales invoice * Order * Order confirmation

Additions/Detractions Mapping#

In EDX additions/deductions mapping, additions and deductions can be assigned to articles, resources, G/L accounts and fields in the document header.

Examples: * G/L account for the surcharge advertising costs * Item as freight charges * Amount incl. VAT" field from the sales header as an insurance surcharge.

Only fields from the sales header can be used. Amounts and percentages can be specified. These two fields are disabled for lines surcharges/discounts. The "Position" field is filled automatically and is only information for the user.

The addition and deduction codes are selected from a separate table.
The surcharge/discount mapping is only used for external outgoing document dispatch with Clearing Center. This includes the following documents: * Order confirmation * Booked sales invoice * Booked sales credit

Service GTIN Mapping#

With the "EDX Service GTIN Mapping" resources, G/L accounts etc. can be provided with a GTIN. The stored GTIN is sent within the service invoice as well as credit note.

EDX Occupancy device#

For each EDX partner different voucher types can be defined. With the "EDX voucher setup" the vouchers are assigned to the EDX partner as well as configured.

With the action "New" an EDX voucher is assigned to a previously created EDX partner. The fields of the EDX voucher setup card are explained in more detail below.

Inforegister General#

Field Description
Partner no. Selection of the EDX partner.
Only active EDX partners can be selected.
EDX Voucher Selection of the EDX document.

The following documents are included by default:
• Order outgoing
• Order confirmation received
• Order change outgoing
• Sell order received
• Sell order change incoming
• Order confirmation outgoing
• Outgoing delivery bill
• Sales invoice starting
EDX Voucher Description A freely selectable description can be entered here. This is for information purposes only.
EDX document direction Specifies the direction of the document exchange (incoming or outgoing).
EDX transmission from From the date set here BC vouchers will be received or sent.
Receipt confirmation check The receipt confirmation check can be used to control whether a message confirmation should be requested.

Example:
Sending a purchase order with acknowledgement of receipt check
After receipt of the order on the other side, a confirmation of receipt is sent to the message sender. The EDX status within the order automatically changes to "Recipient received".

After the Business Centrals sales order has been created at the recipient, another acknowledgement is sent. The EDX status within the order automatically changes to "Recipient accepted".

If the recipient rejects the EDX sales order, then an acknowledgement is also sent. The EDX status in the sent order changes to "EDX Rejected".

The confirmation check should be enabled on the outgoing as well as incoming message.

Outgoing confirmation messages e.g. for the receipt of an EDX sell order are now sent via the EDX outbox.
The "Source record" field now always refers to the associated document.
Acknowledgement check is now supported by all EDX documents, sales deliveries, sales invoices as well as sales credit memos.

In the case of external EDI, the acknowledgement messages may have to be coordinated with the EDI service provider.
Test indicator Marks the incoming or outgoing messages as a test message
See chapter Productive/test database

Inforegister transfer#

Field Description
EDX Transmission type File transfer
When using a shared network share (UNC), file transfer can be selected here. See section EDX Setup General.

Client transfer
If the sender and receiver are in the same database, then the Client transfer option can be selected here.

FTP TransferUsing
FTP transfer, documents can be transferred to or retrieved from an FTP server.

E-mailWith
this transmission type it is possible to send receipts by e-mail.

Azure StorageAll
messages are stored or retrieved on the specified Azure Storage.

Inforegister Azure / File Transfer#

Field Description
EDX File Path Input/output path for files.
Either an absolute or dynamic path can be entered in this field. The dynamic path is stored with the placeholder %ROOT_DIR%.

This placeholder is exchanged at runtime for the base directory from the EDX setup.
SeeEDX Setup

Thus, when moving a directory share, it is sufficient to change the new directory in the "Documents (UNC) directory" field within the EDX setup.

In the above example %ROOT_DIR% is replaced with \kvsdodc01\temp\EDX\Test10\Prod.

As soon as the "Test Environment" switch is activated, the following directory applies to %ROOT_DIR%
\\kvsdodc01\temp\EDX\Test10\Test\

The same rules apply to the placeholder %AZURE_CONTAINER%.
• In this case, the Azure container that has been set up is used.

Inforegister Azure Forwarding#

The forwarding parameters are sent to an "Azure Logic App" or "Power Automate". The Azure Logic App is not part of EDX. For processing the parameters below, a corresponding "Azure Logic App" or "Power Automate" must be created in the customer project. For the creation of the "Azure Logic App" the template "EDX_Outbound_Message" can be used.

When using the forwarding parameters, the GS1 messages "GS1 APP REC ACK IMP" as well as "GS1 APP REC ACK EXP" must be assigned to the EDX partner.

Field Description
Forwarding type This parameter can be used within the Logic App to decide which Azure Connector is used.
Forwarding ID Determines the EDI party
Forwarding Destination Determines the destination of the message

**Example CC Invoice message is to be transmitted to EDI service provider EDI1 via SFTP. The message is to be placed on the destination FTP server in the /inbound directory.

Set the following forwarding parameters:

field description
Forwarding type SFTP
Forwarding ID EDI1

FTP information register#

The FTP parameters must be set up when the FTP transfer type is selected.

Field Description
FTP Server
FTP user
FTP password
FTP file path
Enable FTP SSL These fields are editable if the transfer type is set to FTP.
The access data for the FTP server are entered in these fields.
The transfer can be established to an FTP server (port 21) as well as an SFTP server (port 22).

Inforegister e-mail#

Field Description
Sender email address The sender email address must match the mail address in the SMTP setup.
Sender name Sender name
Recipient e-mail address E-mail address of the message recipient
Email subject Specifies the subject of the e-mail.
Email text (HTML) Specifies the text of the e-mail.

Information register processing#

The processing parameters for the incoming as well as outgoing messages are defined in this info register.

Field Description
Automatic processing EDX Input Document:
The received EDX document is automatically checked. If no errors occur during the check, the Business Central document is created.

If an error occurs when checking or creating the Business Central document, an error mail is sent automatically.

This function is currently available for EDX sell orders.
See section: Automatic processing

EDX Output Document:
So far, the following outgoing documents can be sent automatically:

• Sales delivery
• Sales invoice
• Sales credit
• Order
• Order changes

See section: Automatic processing
Processing sequence Sets the processing order of incoming messages.
Do not add a transmission ID If this option is enabled, the "EDX Transmission ID" element is not transferred to the XML file.
The EDX module basically assumes that the element "TransmissionID" is present in the incoming XML document. This element e.g. is used for the document navigation within EDX.
If the incoming XML document does not contain the TransmissionID, then it is automatically added as the first element.
Note
The setting of this switch should only be changed if it has been described in the respective application documentation (customer project).
Ignore zero bill Invoices with a value of 0 € will not be transferred if this option is enabled.
Ignore zero credits Credits with a value of 0 € will not be transferred if this option is enabled.
Automatic archiving Specifies that the associated EDX input is archived after EDX document processing.
Direct purchase invoice Switched off:
When processing an incoming purchase invoice, the information of the purchase delivery is expected. Based on the purchase delivery number, the corresponding purchase order is determined.
The purchase delivery as well as the purchase order are then used for plausibility checks.

Switched on:
The data of the EDX purchase invoice are directly transferred into an unposted purchase invoice. Plausibility checks are performed with regard to the "Purchasing from vendor" as well as the articles.
Embedding the associated PDF document In the case of outgoing messages for the Clearing Center, the associated PDF document can be included directly in the message.
The PDF document is transmitted as a base64 encoded string.
Collective consignment If the created Business Central documents (sales delivery bill, sales invoice as well as sales credit bill) are not to be sent immediately when they are posted, then a document collection can be activated with this option.

This option is currently supported by EDX documents Sales Delivery (CC), Sales Invoice (CC), Sales Credit Note (CC).

The time for sending the document can be set via the processing time window.
Next list number When sending collective consignments, a list number is usually required. In the "Next list number" field, you can specify the list number that will be used for the next transmission.

Note
Sales deliveries can be transmitted as collective consignments. The assignment of a list number is not provided for.
Normally, a forwarding order number must be transmitted within the delivery note message. This is currently not supported by the EDX CC delivery note message.
BC Release document This setting controls that a scanned document is automatically released after creation.
BC Post voucher Determines whether an incoming EDX document should be posted or not.
Use booking date Specifies which date to use for incoming EDX documents. Options "Posting date, current date, work date, incoming document date".
Use article references Since in the rarest cases a consolidated article master exists between the partners, it is necessary to ensure a reliable assignment of the article numbers. The setting "Use article references" controls a check of the transmitted article number, as well as the transmitted reference number. The article/reference number check is based on the Business Central article master > References.

The following requirements are necessary when using this function:

• It is mandatory that the partner transmits the GTIN or reference number.
• The article references of the partner must be maintained in the article master.

If a GTIN is transmitted, the Business Central article is determined on the basis of the GTIN field in the article master. If no matching article is found, then a search is performed using the article references with type "Barcode". The reported article unit is used for the article reference search.

If this search also does not lead to any result, then the search is carried out using the article references with type "Customer" or "Vendor". The reported article reference number from the message is used.
Use article unit mapping This setting controls an automatic mapping of the article units.
Example:
The EDX partner transmits the article unit "PCS"
for any article, which is managed as "Piece" in Business Central. If the corresponding mapping table is maintained and the setting "Article unit mapping" is maintained, the unit is changed accordingly upon receipt.
See EDX Document Processing > Item Unit Mapping
EDX Automatic archiving If an EDX document is processed, this setting can be used to control that the associated incoming item is archived.
Processing time window For outgoing documents, the processing time window controls the time at which the document is sent. For incoming documents, the processing time window controls the check and creation time.
Example of outgoing sales invoices:
Sales invoices are to be collected by Saturday and mailed at 10:00 pm.
In this case, the "Run Saturday" option will be enabled in the processing time window. All other days will be deactivated. The start time is set to 22:00 and the end time to 23:00.
The earliest start date is calculated automatically.
Once the specified time window is reached, all invoices that have not yet been sent will be sent.
Example of incoming sales order:
Sell orders should be processed automatically every day at 22:00.
In this case, each day is activated in the processing time window. The start time is set to 22:00 and the end time to 23:00.
Note
Once the specified time window is reached, all unprocessed EDX sales orders are checked and created as BC orders.

Info tab Advanced#

Field Description
Partner type Indicates whether the displayed EDX partner is a customer or vendor.
Partner BC No. Displays the BC Customer or Vendor No. depending on the partner type.
Document type Displays the BC document type associated with the EDX Document Setup.
Doc Tables No Displays the BC Table No. associated with the EDX Document Setup.
Object type
Object ID
Displays the XMLPort or code unit that is responsible for message processing.
Messages coding Sets the message encoding. This parameter has no effect on EDX standard messages. Within project specific messages this parameter can be used for the encoding of the message.
Web service function Sets the message for use within the internal web service functions.
Web service function name Sets the name of the internal web service function.

Function "Field settings document check "#

The function "Field settings for document check" in the ribbon defines which fields of the EDX document are checked or transferred to the Business Central document.

Field Description
Validation order According to the defined validation sequence, the data is transferred from the EDX intermediate document to the BC document.
Use default values The option "Use default value" can be used to preassign fields within the EDX document, which are e.g. not included in the message.
Default value For example, for the due date in the sales header, it can be set that this field is always initialized with the work date.
Within the default value, constant values or placeholders can be used. When using a constant, care must be taken that the value is entered according to XML format.

A fixed date must therefore be entered in the format YYYY-MM-DD. For decimal values, the period must be used as a separator.
The XML format was chosen to avoid translation errors of different languages. If an employee sets the date 15.01.2018 as default value and then an English-speaking employee checks the message, the default date cannot be converted.

The default values are initialized when the EDX document is checked.
List of placeholders:
Placeholder Description
%WORKDATE -> Work date
%TIME -> Current time
%TODAY -> Current date
%COMPANYNAME -> Client name
@fieldname -> Reference to another field of the current table
Create field content This indicator controls whether the field contents from the EDX document should be checked and transferred to the BC document.

Set up task queue item#

Automated message sending/receiving is done by setting up the task queue items. These are created using the EDX setup wizard. See EDX Setup.

Process distribution within the task queue items#

The following task queue items are created using the EDX Wizard:
CodeUnit: 5487951 EDX Job Queue

Parameter Description
INBOUND_TRANSMISSION Read in data according to the specified transfer type (e.g. file transfer) and make it available in "EDX input".
INBOUND_TO_EDX_DOCUMENT Process all EDX input items with status "Unprocessed".
INBOUND_POST_EDX_DOCUMENT Check all created EDX documents (sales order, purchase order confirmation, etc.) configured with the "Automatic processing" flag and create the corresponding BC document if necessary.
OUTBOUND_SEND_NAV_DOCUMENT All created BC documents (sales delivery, sales invoice, etc.) configured with the "Automatic processing" flag are transferred to the "EDX Outbox".
OUTBOUND_TRANSMISSION Send all EDX outgoing items with status "Unprocessed" according to the specified transmission type.
SEND_MAIL Send any processing errors that have occurred by mail.
REORGANIZATION Archives the EDX outputs.
Time of archiving is defined in the EDX setup.

GLN facility#

In addition to the GLN in the customer, further GLNs are required for the creation of an EDIFACT message. With EDIFACT, the message recipient is transmitted in the UNB segment. The GLN of the message recipient may differ from the GLN of the customer.

According to EDIFACT, GLN's are mapped in the following segments:

))

GLNGlobal Location Number  

News
Segment
Description Identifier
UNB Interchange header (message sender/receiver)

If the "Invoice to customer" belongs to a federation, then GLN of the federation customer, otherwise GLN of the "Invoice to customer".
Special case: The message recipient requests a GLN which does not belong to the master data mentioned above. In this case the GLN of the EDX partner is used.
NAD Name and address data SU = Supplier
BY = Buyer
DP = Delivery address
IV = Billing address

The GLN's are entered in the following Business Central master data:

Message receiver (UNB)#

The GLN for the message recipient/sender (UNB) is entered directly at the EDX partner in the "GLN" field.

Debtor (NAD segment)#

The GLN for the customer (NAD segment) is entered directly on the customer card in the "GLN" field in the "Invoicing" info tab.

Delivery to address (NAD segment)#

The GLN for the Delivery to Address (NAD segment) is entered directly on the Customer Card > Delivery to Addresses in the "GLN" field in the "General" info tab.

The transmission of the above GLN's is supported by the XMLPorts for EDI service providers (prefix CC).

Set up e-mail dispatch#

As described in the previous sections, EDX automatically sends mails if, for example, an error has occurred during processing.

The following items must be set up to send mail:

SMTP mail setup#

The SMTP server must be set up via the SMTP mail setup. This setup depends on the technical conditions of the environment and should be done by the company's IT department.

BC Administration (Management Console)#

Mail is usually sent using the Business Central instance JOBQUEUE01. Since this is a process without client service, it is necessary that the base URL is entered.

The URL of a Business Central instance with the Enable Client Services option enabled must be entered in the Windows Client Base URL field.

Example:
DynamicsNAV://srvnav:7246/NAVProd01/

This base URL is then used, for example, for the PageLinks within the error mail.

Internal document exchange#

Set up with the EDX Setup Wizard#

The internal document exchange can be set up completely via the EDX Setup Wizard if both clients are present in one database.

Note

Before starting the wizard, the EDX setup must be set up in both clients.

For further information, please refer to "EDX Setup".

Afterwards the action "EDX Setup Wizard" can be started in the EDX Setup.

The setup for the internal document exchange can now be started with the action "EDX Setup Wizard".

After starting the wizard, the following parameters must be set: * Set the function of the wizard to "internal document exchange". * Set role of the current client. * Selection of the communication interfaceCurrently, the
interfaces "File transfer" and "Azure Storage" are available. * Use purchase price as sales priceThe
price from the sent purchase order is transferred to the sales order.
see Field control. * Selection of the client with which messages are to be exchanged. * Assignment of customer and vendor according to the clients.

After executing the action "Finish" the reconciliation of the field "Our account number" between the customer and the vendor takes place. In both clients, the required EDX partners and the related intercompany documents are assigned.

Manual setup#

If the clients exist in different databases, then the setup must be done manually.

The following messages are to be set up on the customer side:

Partner no. EDX Voucher EDX document direction EDX Voucher Description Partner type Partner BC No. EDX Transmission type
V10000 IC PURCHASE ORDER CHG Based on Send order change Vendor 10000 File transfer
V10000 IC PURCHASE ORDER CONF In-depth Receipt order confirmation Vendor 10000 File transfer
V10000 IC PURCHASE ORDER Based on Send order Vendor 10000 File transfer
V10000 IC PURCHASE SHIPMENT In-depth Receive purchase delivery Vendor 10000 File transfer
V10000 IC PURCHASE INVOICE In-depth Receipt purchase invoice Vendor 10000 File transfer
V10000 CONFIRMATION RECEIVE In-depth Acknowledgement Receive Vendor 10000 File transfer

The following messages are to be set up on the supplier side:

Partner no. EDX Voucher EDX document direction EDX Voucher Description Partner type Partner BC No. EDX Transmission type
C10000 IC SALES ORDER CONF Based on Sending the order confirmation Debtor 10000 File transfer
C10000 CONFIRMATION SEND Based on Acknowledgement of the messages Debtor 10000 File transfer
C10000 IC SALES ORDER In-depth Receiving sales orders Debtor 10000 File transfer
C10000 IC SALES ORDER CHG In-depth Receive order change Debtor 10000 File transfer
C10000 IC SALES SHIPMENT Based on Send sales delivery Debtor 10000 File transfer
C10000 IC SALES INVOICE Based on Send sales invoice Debtor 10000 File transfer

When setting up the intercompany documents manually, the EDX file paths must be configured manually.

The output message is configured first. The associated path must be stored temporarily. The input message can then be configured. The path from the previously configured output message must be used here.

The message recipient and sender can thus communicate via the same directory.

The following steps must be carried out using the "IC PURCHASE ORDER" example. The EDX basic setup must already have been carried out and partners must have been created. This process must be performed for all incoming messages: * Open client "Customer". * Create EDX document facility for document "IC PURCHASE ORDER" and buffer path. * Switch to the "Supplier" client. * Create EDX document setup for document "IC SALES ORDER" using the path of the outgoing document.

Shipping order / load carrier#

To use the outgoing message "CC DESPATCH ADVISE" (DESADV), it is necessary to set up the shipping orders including the load carriers.

The general information about setting up the shipping orders and load carriers can be found in the corresponding manual "KUMAVISION Shipping Processing". In the following, you will only find notes on the relevant settings for the outbound message mentioned above.

Setup storage location#

In order to be able to assign the load carriers/packages in the shipping order, the option "Shipping order" must be selected in the field "Shipping processing" in the storage location or must remain free.

Shipping order setup#

Use the Shipping and Load Carrier Setup menu item to set up your shipping orders. If you want to ship load carriers with information about the NVE/SSCC, the fields "Company ID" must be filled with the base number (GLN) of the company, and "Load Carrier ID Numbers" with a number series. Instead of storing the number series here in general, these can also be stored specifically for individual load carriers. In addition, the option "Create check digit for carrier ID" must be activated so that the check digit specified by GS1 can be calculated and added for the NVE/SSCC.

!!! note "Note In the field "Company ID" a reserve digit (see GS1 specification) must be prefixed before the base number, so that a correct NVE/SSCC can be generated.

In order for a NVE/SSCC to be generated automatically, the option "Assign load carrier ID on order release" must also be activated.

The NVE/SSCC has a total length of 18 digits (see GS1 specification). Therefore, the combination of company ID with reserve digit, number series of the load carrier and check digit must be exactly 18 digits long. If this is not the case when releasing a shipping order and the option "Assign load carrier ID when releasing order" is activated, a corresponding note appears.

Load carrier setup#

The required load carriers can be set up via the "Load carrier" menu item. If load carriers including NVE/SSCC are to be transferred, the option "ID mandatory" should be set here. If no number series is stored in the "Load carrier ID number" field in the shipping order or if a different number is to be used for the respective load carrier, a previously created number series can be selected here.

Please note the information on the NVE/SSCC from the chapter "Shipping order setup".

Create DESADV#

The outgoing message "CC DESPATCH ADVISE" is generated from a booked dispatch order with EDX partner.

In order for a valid DESADV file to be created and, if necessary, further processed by an EDI converter, the following requirements must still be met when creating shipping orders.

The shipping order must refer to a booked sales delivery, otherwise no valid EDX partner can be transferred to the booked shipping order.

Each line with packaging materials/cargo carriers must be assigned to at least one delivery line.

Incoming documents#

Incoming documents are first temporarily stored in EDX documents.

Data flow of an incoming document#

The incoming message is first read into the EDX inbox. The system creates an EDX inbox item and stores the message in the item.

The EDX intermediate document is then created from the EDX incoming item. Within the EDX intermediate document, the user can intervene and correct data. Furthermore, the user can reject the EDX intermediate document if necessary or create a Business Central document from it.

EDX input items#

All incoming documents are first stored in the EDX Inbox table. When the business process for this document is completely finished, then the item will be automatically transferred to the "EDX Inbox Archive".

Field Description
EDX status Indicates the current status.

Unprocessed
The document has been transferred to the EDX module and an
EDX incoming item has been created.
The item has not been sent yet.

Error
An error occurred while processing the item.
The "Error" field displays the number of errors that occurred.
The look-up of the "Error" field can be used to retrieve the related error items.

EDX document generated
An EDX intermediate document was created from the incoming item.

BC Document created
A BC document has been created from the created EDX intermediate document. The associated EDX inbound item is now completed and will be moved to the "EDX Inbound Archive".
EDX message If there are system messages for this item, they can be retrieved via the look-up.
EDX error If there were any processing errors for this item, they can be retrieved by clicking the Look-Up button.
Show file action This action displays the document contained in the item.
"Manual processing" action If an error occurred during automatic input processing and this error has been corrected in the meantime, then the input item can be processed again using the "Manual processing" action.
Upload message action See section "Edit and reprocess EDX incoming items".

EDX Edit and reprocess incoming items#

The "View file" function can be used to download the XML message of the selected EDX input item and edit it if necessary. The "Save files" function downloads the XML message from all selected input items and saves it in a selected folder.

Note

Currently this action "Save file" is not available in the WebClient (.NET Framework)

The file must be saved with the action "Show file" and then save.

If an EDX inbound item runs into an error because, for example, a field length in the EDX intermediate document is exceeded or the XML structure is incorrect, the XML message can be downloaded from the EDX inbox, edited, and uploaded again for new processing.

Using the "Upload message" function, the XML message can be uploaded again to the document directory on the server.

After the successful upload, the message will be processed again.

Note

The new EDX input item does not appear immediately after calling the function, but only when the message has been retrieved from the task queue again.

Manual processing of an EDX document#

For the processing of EDX documents, a basic distinction is made between two cases.

Incoming EDX document, the BC document has not yet been created.

Example:
A sales order is received. The corresponding BC document has not yet been created.
When the incoming EDX document is created, it results in a new BC sales order.

Incoming EDX document, the BC document already exists.
Example:
An incoming EDX order confirmation refers to an already existing Business Central order.

Before a Business Central document can be created from an incoming EDX intermediate document, the incoming EDX document must first be checked. After a successful check, the EDX document receives the status "Ready for creation". All EDX documents with this status can be transferred to a corresponding Business Central document.

EDX Intermediate document#

The EDX intermediate documents contain partly identical fields as the BC documents (see EDX sales order). Special EDX fields and their related functionality are described below.

EDX messages/errors
If there are any system messages or errors specifically for this document, they can be retrieved via the look-up.

EDX status * Unprocessed
The EDX document was created automatically. No further processing steps have been performed yet. * Error:
An error occurred while processing the document. * Ready to put on
The EDX document is checked and can be created. * BC Document created
A BC document was created from the EDX document already created. This item is now completed and will be moved to the EDX incoming archive * Inconsistent data
There is already an existing BC document for the incoming EDX document. * Rejected
The incoming document was rejected * Manual processing
If it is not possible to create an incoming EDX document as a BC document, it will receive the status "Manual processing". * Archived
EDX documents that have already been archived. * Deleted
EDX documents that have been deleted by the user.

EDX Voucher Check#

During the verification, the system performs a validation of the data. In the process, the field contents are checked. The validation of the field contents is based on the settings made in the document setup.

If errors are detected, the EDX document receives the status "Error". In the field "Error" on the document header or the document lines the number of occurred errors is indicated. You can open related error items using the Look-Up button.

If errors are detected, they can be corrected directly in the EDX document. Each field change in the EDX document is logged. By means of a lookup on the field "EDX Note" these changes can be retrieved.

After manual correction in the EDX voucher, the action "Check" must be executed again. After all errors have been corrected, the BC document can be created using the "Create" action.

Processing of EDX documents with status "Inconsistent data"#

During the check, the data of the EDX document is compared with the data of the Business Central document. This is the case, for example, with an incoming order change.

To avoid having to manually compare the existing Business Central sales order with the EDX order change, EDX checks the discrepancies and displays them clearly.

If any discrepancies are found, the EDX status will be set to "Inconsistent Data". With a click on the lookup field "EDX Error" all deviations are displayed.

Example:
An order change for an item with a quantity increase from 20 pieces to 30 pieces was received.

The EDX status is set to "Unequal data".

By clicking on the EDX error number (line), a dialog is displayed in which the deviations are shown.

The "Apply changes" selection determines whether the displayed change is to be transferred to the Busniess Central document. The "Value EDX" column shows the currently transferred value. The "Value BC" column shows the current value of the Business Central document.

After defining which changes are to be accepted, the action "Accept changes" must be executed.

Delete EDX document#

Deleting an EDX document depends on the status. If the EDX status contains one of the following values, deletion is not possible:
BC Document created
Rejected
Manual processing
Archived

If the document is not in this status, the EDX document can be deleted with the action "Delete EDX document".

After executing the action "Delete EDX voucher", a dialog box appears with the note that a deletion reason must be specified and whether you actually want to delete the voucher. This query must be confirmed with "Yes".

Subsequently, the reasons that led to the deletion of the message can be recorded.

Create EDX document#

The "Create" action transfers the EDX intermediate document to the associated Business Central document.

Reject EDX document#

It is possible to reject incoming EDX vouchers.

The rejection is transmitted to the message sender if the "Receipt confirmation check" field has been activated in the EDX document device.

Rejection reasons must be recorded before the action is completed.

EDX document with "Manual processing" status#

EDX documents with the status "manual processing" indicate that the EDX document cannot be created or confirmed as a Business Central document. This may be due to the following reasons: * The existing document has already been delivered * Reservations are available * A clear assignment of the document is not possible * A clear assignment of the lines is not possible * There are deviations that cannot be processed automatically

Since these EDX documents cannot be processed by the system, further processing must be performed by the user.

The EDX document is closed by archiving it.

Automatic processing#

Automatic processing" can be activated within the "EDX voucher setup". The received voucher will be checked automatically. If no errors occur during the check, the Business Central voucher is created.

Up to now, incoming sales orders have been processed automatically.

Outgoing document#

Outgoing EDX documents are not transferred to an EDX intermediate document. When the EDX message is created, an EDX outgoing item is created directly.

EDX information#

Each outgoing document contains information that is required for transmission. This information is displayed in the "EDX" info tab.

Below you will find a more detailed explanation of the fields of the info register that are required for the transfer:

Field Description
EDX document Yes
The document has been recognized as an EDX document by the document facility. The transfer of the document is possible

No
No document facility exists for the document. The transfer is not possible.
EDX status Indicates the current status:

Unprocessed
The document has been transferred to the EDX module and can be sent.

Processed
The EDX output item has already been created.

Dispatched
The EDX outgoing item has been sent.

Recipients receive
With a message acknowledgement, the recipient can signal that the message has arrived in the target system.

Error
An error has occurred during processing. This can be looked up in the EDX system error log.

Ignored
Documents with the status "Ignored" will not be sent.
The "Ignored" status is set automatically when the following conditions are met:
If a sales invoice that has not yet been sent is cancelled, then both documents (invoice/credit note) are set to the "Ignored" status.
If a sales delivery that has not yet been shipped is cancelled by a complaint, then the status of the sales delivery is set to "Ignored".
Sales delivery, invoice as well as credit note
In the sales order it can be defined that certain documents should not be sent with the next posting.

If a posting number for delivery bill or invoice is reserved via the sales order and the sales order is deleted without using this posting number, then a posted document with the note "deleted document" is created according to BC Standard.
These documents are not transferred.

Manual processing#

Send EDX document manually#

Manual document dispatch takes place directly from the associated Business Central document with the action "Send EDX document".

EDX output items#

All sent documents are first saved in the "EDX Outbox" overview. When the process is complete, the system automatically transfers the item to the EDX Outbox Archive overview.

EDX status * Unprocessed:
The document has been transferred to the EDX module. This item has not been sent yet. * Error:
An error occurred while processing the item. For more details, see the Error Log field.
If the error occurred due to insufficient file permissions, then the EDX document can be processed again after correcting the permissions. For this purpose, the action "Reprocess" is selected.
If the transfer type is set to FTP, the FTP error is displayed directly. * Dispatched:
The item was transmitted to the partner. With the columns "Messages" as well as "Errors" information about the outgoing item can be retrieved.

Action "Show file"
This action displays the document contained in the item.

Action "BC Voucher Display
This action displays the corresponding BC document.

Display archived BC document" action
Display of the archived document.

Automatic processing#

So far, the following outgoing documents can be sent automatically:

  • Sale

deliveryShipping takes place when booking.

  • Sales

InvoiceShipping takes place when booking.

  • OrderShipping will be done upon approval.
  • Order changes

The shipment takes place when the order is released.

If the order is released and has already been sent via EDX, then an order change is automatically sent.
A check for quantity or date changes is currently not provided.

The automatic dispatch of Business Central documents can be controlled within the EDX document facility.

The following conditions apply to the EDX occupancy facility: * The EDX partner must be of type Customer or Vendor. * The EDX "Transfer date from" must be greater than or equal to the work date.

The following conditions apply to the BC documents delivery bill, invoice and purchase order: * The "EDX Partner" field has a value. * The document date is greater than or equal to the "EDX transmission from". * The "EDX Status" is "Unprocessed".

The following condition applies to the BC delivery bill: * The "Sales to customer" field must match the "BC partner no." from the EDX voucher setup.

The following condition applies to the BC bill: * The "Invoice to Customer" field must match the "BC Partner No." from the EDX document setup.

Reset EDX status#

With the action "Reset EDX status" documents can be sent again.

Enhancements in "Internal document exchange#

Purchasing deliveries without goods receipt#

In the case of purchasing deliveries, it was previously always assumed that the storage location used was posted by goods receipt. The processing of purchase deliveries has been changed so that now also storage locations without goods receipt can be used. In this case, the field "Quantity current delivery" in the respective order line is initialized with the reported delivery quantity.

The document must be posted by the user.

Purchase deliveries with batch / serial number#

Batch/serial numbers are now supported for purchase deliveries.

The batch/serial number to be delivered is entered in the sales order. The batch is then transferred to the recipient with the posted sales delivery.

The transmitted batches/serial numbers can be retrieved in the "EDX Purchasing Delivery" using the line menu.

After checking / creating the EDX purchase delivery, the item tracking data is transferred to the purchase order.

After posting the order, the item/batch is available on the storage location.

Additions/deductions in "internal document exchange"#

Surcharges/discounts can now be used in internal document exchange. The prerequisite is that the "Sales price without VAT" field is activated in the field control for the sales order received. Otherwise, the order line will be created without a sales price.

Article variants in "internal document exchange"#

The article variants are now supported in the internal document exchange.  

Order date in "internal document exchange#

When sending the order, the "planned date of receipt of goods" is transmitted from the order. Further processing looks like this:

Process Field Description
Send order "Planned date of goods receipt". Send date
Receive sales order "Requested delivery date" Validate "Scheduled Goods Receipt Date" from the purchase order in "Requested Delivery Date" field.
The validation automatically calculates the fields "planned delivery date", "planned goods issue date" as well as "goods issue date" in the sales order.
Send order confirmation "Promised delivery date"
as well as
"Planned delivery date"
Send date
Receipt purchase confirmation "Committed date of receipt of goods".

"Planned date of goods receipt".
Validate "Committed delivery date" from the order confirmation to "Committed goods receipt date" of the purchase order.
Validate "Planned delivery date" from the order confirmation to "Planned goods receipt date" of the purchase order.
Send order change "Planned date of goods receipt". Send date
Reception order change "Requested delivery date" As for "Receive sales order

Remark texts#

During internal document exchange, the "remarks" are transferred from the Business Central order, header as well as line. On receipt, the remarks are saved in the EDX sales order. Likewise, comments can be reported back with the EDX order confirmation. In this case, the remarks are stored in the EDX purchase order confirmation.

Received remarks are not transferred to the Business Central sales order or the Business Central purchase order. Otherwise, it would no longer be possible to distinguish between remarks entered by the user and remarks from the other party.

Receive delivery schedules#

In the internal document exchange, previously sent purchase orders/framework orders can be received as delivery schedules. The setup for sending purchase orders can be done as described above. On the receiver side the message "IC SALES DELFOR" is set up.

When a delivery schedule is received, a delivery schedule and a scheduling agreement are created for each order/article. This functionality is only available within the KUMAVISION factory365.

Direct delivery#

When sending a purchase order with reference to a sales order (direct delivery), the data of the sales order is also transmitted.

Upon receipt, the data of the direct delivery is transferred to the EDX intermediate document for sales orders.

Further processing of this data must be implemented in the customer project.

Master data export#

The EDX Framework provides the following documents for the master data export:

Document Description Document direction
BASE CUSTOMER Basis debtor export Based on
BASE ITEM Base article export Based on
BASE VENDOR Base Vendor Export Based on

Example: In the following example, the document "BASE CUSTOMER" is assigned to the EDX Partner C10000.

Subsequently, the configuration for the export fields is made with the action "Field setting for document check". Only the customer fields selected in the "Create field content" column will be exported.

If one of the specified fields is changed in a customer, then the export of the customer is performed automatically.

The output has the following format: )

Productive -/Test database#

When copying the production database to the test database, overlaps may occur in the interface directory area. Furthermore, it should be ensured that test messages do not get into the productive system.

The steps required to secure the production database are explained in more detail in the following sections.

Before the copy#

Before the production database is copied to the test database, all task queue items (all clients) should be set to "Wait".

After copying the production database to the test database#

When the production database is copied to the test database, there is usually an overlap of the interface directories. The document directories in the production and test databases are identical. This can lead to the fact that current EDI documents are not imported into the productive but into the test database.

For this case a security query was integrated, which is displayed when opening the test database.

If the query is answered with "Current database is the test database", the option "Test environment" is automatically activated in the EDX setup.

All clients with active EDX setup should be opened once after copying the database. Furthermore, the interface directories must be copied from the "Prod." subdirectory to "Test".

EDX voucher setup (FTP)#

If documents with the transfer type FTP are entered in the "EXD document setup" (test database), then these must be changed to "File transfer".

Task queue items#

The task queue items can now be reactivated in both databases.

Test indicator#

The "Test Indicator" is used to mark incoming as well as outgoing messages during the EDI test phase. For EDIFACT messages, this indicator is contained in the UNB segment (Interchange Header). The message recipient can use this indicator to control whether the message is transferred to the production or test system.

However, this "test indicator" is not available in all message formats (VDA, OpenTrans, etc.).

In the EDX document facility, it is possible to set whether the message (order, delivery bill, invoice, etc.) is a test message.

Effect of the test indicator on processing in Business Central:

Direction Description
Document received in BC:
Sales order
Sales order change
Purchase order confirmation
Purchase delivery
Purchase invoice
If the test indicator is enabled within the incoming message or in the document facility, then the EDX document will be marked as a test document.

This allows the test to be enabled for messages even if the original message (e.g. VDA) does not support the test indicator.

EDX receipts with the test indicator enabled will only be processed automatically if the "Test Environment" option is enabled in EDX Setup at the same time. Otherwise, an error will be generated and sent by mail.
Document sent from BC The test indicator from the document setup is transferred to the outgoing document.

Receipt of a sales order with test indicator
. The test indicator is transferred from the Business Central sales order to the delivery as well as invoice. This means that if a Business Central sales order was received as a test message, then the outbound delivery/invoice messages will also be marked as a test message.

Azure FileSync#

Azure FileSync can be used to exchange files between networks. Synchronization between source and destination directories can take up to several minutes.

If time-critical messages need to be exchanged, which is the case, for example, when messages are provided for a label printer, then the switch should be made to FTP file transfer.

EDX MasterDataExport#

With the EDX Master Data Export the following master data can be exported:

  • Article sub-tables
    Article variants, article units as well as article references
  • Customer sub-tables
    Contacts
  • Vendor

Establishment#

The setup of the AddOn is done with the EDX setup.

EDX Setup#

At the beginning, the necessary setups are done via the setup wizard. This setup wizard can be called up via the EDX Setup menu ribbon ("More options" > "Action" > "Setup" > "EDX setup wizard"). The EDX setup wizard is started. Via the selection "General" the required document types as well as number series are created.

EDX Document types#

After setup via the setup wizard, the following document types are available:

Document Description Document direction
BASE CUSTOMER Basis debtor export Based on
BASE ITEM Base article export Based on
BASE VENDOR Base Vendor Export Based on
Setting up the document types#

For each EDX partner different voucher types can be defined. With the "EDX voucher setup" the previously created voucher types are assigned to the EDX partner as well as configured.

Field settings#

The "Field settings for document verification" function in the EDX document setup card ribbon allows you to configure which fields are to be exported from the associated master data table.

Field Description
Table name Specifies the table name for which the master data is to be transferred. For example, "Article" or a sub-table of the article, such as "Article variant".
Field name Specifies the respective field name for which the master data is to be transferred.
Validation sequence The validation order sets the element order in the XML output message.
Default value This option is not available for the master data export
Create field content Specify which fields will be exported.

Master data export#

The master data export takes place automatically as soon as a change is made to the master data record. Here, only field changes that were specified in the field settings are monitored.

Example:
The article description has been changed for an article. After the data record has been saved, the export takes place.

The output file contains the following elements:

)

Calculated fields#

Currently, only the calculated field "Stock" is provided. Calculated fields of the debtor or creditor are not provided by this AddOn, but can be implemented in the project.

Bulk data export#

At the beginning of a project, a function is usually needed to export all records of a table.

This can be controlled via the "Collective item" option within the document setup.

As soon as you activate the switch, all records of the table will be exported during the next data export. Afterwards, the "Collective export" option will be deactivated automatically.

EDX OpenTrans 1.0#

With the EDX AddOn OpenTrans 1.0 the following OpenTrans messages are provided:

  • DISPATCHNOTIFICATION (shipping notification)
  • INVOICE (Invoice)
  • ORDER (sell order)
  • ORDERRESPONSE (order confirmation)

Establishment#

The setup is done with the EDX setup.

EDX Setup#

At the beginning, the necessary setups are done via the setup wizard. This setup wizard can be called up via the EDX Setup menu ribbon ("More options" > "Action" > "Setup" > "EDX setup wizard"). The EDX setup wizard is started. Via the selection "General" the required document types as well as number series are created.

EDX Document types#

After setup, the following document types are available:

Document Description Document direction
OT1.0 SALES INVOICE OpenTrans 1.0 Invoices outgoing Based on
OT1.0 SALES ORDER OpenTrans 1.0 Orders incoming In-depth
OT1.0 SALES ORDER CONFIRMATION OpenTrans 1.0 Order confirmations outgoing Based on
OT1.0 SALES SHIPMENT OpenTrans 1.0 deliveries outgoing Based on
Setting up the document types#

The document types listed above are then assigned to an EDX partner.

Field settings#

The field setting is only available for the OpenTrans message "OT1.0 SALES ORDER". See EDX "Field setting for document verification".

Processing#

The processing of OpenTrans 1.0 messages is done in EDX standard. Incoming sales orders are provided as "EDX sales order". The order confirmation can be created via the corresponding Business Central sales order. The sales delivery and sales invoice can be sent manually or automatically.