Activities

For each legal entity, you can set up several addresses. For each of these addresses, you can define the Global Location Number (GLN code). You can use the GLN code in EDI to identify the unique location.

For the created key vault, set up an access policy to allow the earlier registered app to access the key vault.

On creation of the access policy:

• On permission selection, select these Secret permissions: Get and List.
• On principal selection, select the earlier registered app.

For more information, refer to Assign a Key Vault access policy.

If all errors and warnings of an EDI Delfor journal are solved, accepted, or canceled, you must approve the EDI Delfor journal. The EDI Delfor journal is again validated according to the applicable journal validation setup. If the applicable validation rules are met, the EDI Delfor journal journal status is set to Approved. Approved EDI Delfor journals are processed by the 'Sales (Delfor) - EDI Delfor journal to Order' message batch.

In EDI studio:

• All EDI transactions are logged in EDI history management (BisEdiHistory table).
• You can use the staging concept to validate data in an intermediate area before it is further processed. Several predefined staging journals are available for EDI studio:
  • EDI purchase journal
  • EDI Sales journal
  • EDI Delfor journal
  • EDI inventory journal
  • EDI transfer journal

To prevent the database from containing too much data, you can clean up the EDI history and EDI staging journals in recurring mode.

For example, you want to keep the EDI staging journals for six months. Each week, you can do a cleanup, deleting staging journals older than six months.

In EDI studio, you can use the staging concept to validate data in an intermediate area before it is further processed.

Several predefined staging journals are available for EDI studio:

• EDI purchase journal
• EDI sales journal
• EDI Delfor journal
• EDI inventory journal
• EDI transfer journal

To prevent the database from containing too much data, you can clean up the EDI staging journals manually.

To enable browsing the app service, add a redirect URI to the earlier registered app.

To add the redirect URI:

• Select the 'Web' platform.
• Enter this URI: [app service URL]/signin-oidc. For example: https://example.azurewebsites.net/signin-oidc. You can copy the URL from the App service Overview page.
• Select the ID tokens check box.

For more information, refer to Add a redirect URI.

When you use the AS2 web app, you need a key vault to set up the secrets and certificates that are required to run the AS2 web app.

Create a key vault and generate these certificates and secrets in the key vault:

For more information, refer to:

• Quickstart: Create a key vault using the Azure portal
• Quickstart: Set and retrieve a certificate from Azure Key Vault using the Azure portal
• About Azure Key Vault secrets

To get the AS2 web app running in the cloud, deploy the created app service. Ask STAEDEAN for the AS2WebApp.zip file that contains the AS2 web app files that are required for deployment.

Deploy the AS2 web app files with the Zip Push Deploy tool of the Kudu services portal.

You can use EDI studio to receive EDI message files from the AS2 web app. These EDI message files are stored in a general storage location. From the general storage location, these EDI message files must be distributed to specific storage locations from where the files can be processed by the applicable inbound messages.

To distribute the EDI message files from the general storage location, run the project inbound definitions. Usually, you run the inbound definitions in recurring mode. Always, all inbound definitions of the selected project are run. The inbound definitions are run in the defined sequence.

When an inbound definition is run:

1. It connects to the general storage location as defined by the connector.
2. The EDI message files that match the read filter are opened to search for this data:
   • Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
   • Recipient: The data in the file that indicates to which company in D365 FO the data must be imported. For example, the GLN.
3. Based on this data, the applicable file distribution definition is determined.
4. The message, as defined for the applicable file distribution definition is used to:
   • Rename the EDI message file: If renaming is applicable, the source document of the message defines how the EDI message file is renamed.
   • Move the EDI message file: The source connector of the message defines to which specific storage location the EDI message file is moved for further processing.
5. If the inbound definition is mandatory, and an EDI message file cannot be processed, the EDI message file is moved to the error location as defined for the connector.

To have a quick start with the EDI setup, you can use the standard EDI tutorials. These tutorials have several pre-defined EDI messages with related setup. The related setup includes, for example: the project, the source and target connectors, and the source and target documents.

These standard EDI tutorial projects are available as a resource:

• Tutorial - EDI
• Tutorial - EDI - 3PL
• Tutorial - EDI Delfor

You can import the standard EDI tutorials by importing the related projects from resource.

If you set up an EDI integration using TIE Kinetix, to have a quick start with the EDI setup, you can use the TIE Kinetix specific EDI tutorials. These tutorials have several pre-defined EDI messages with related setup. The related setup includes, for example: the project, the source and target connectors, and the source and target documents.

These TIE Kinetix specific EDI tutorial projects are available as download:

• Tutorial - TIE Sales
• Tutorial - TIE Purchase
• Tutorial - TIE Warehouse 3PL

You can import these EDI tutorials by importing the related projects from file.

Before you can import the project, download the ZIP file that contains the project files. To do so, click this link: TIE Kinetix integration EDI tutorial projects. After download, extract the ZIP file.

All EDI transactions are logged in EDI history management (BisEdiHistory table).

This topic explains how to monitor the overall EDI history.

For each customer with whom you exchange EDI messages, you can monitor the related document flows.

Only the applicable document flows are shown. For more information on how the applicable document flows are searched for, refer to 'Search for document flow: Vendor'.
To edit vendor document flows, refer to 'Set up buyer messages document flows'.

For each EDI Delfor journal with message status Processed, you can open the related sales order from the EDI Delfor journal.

If you use a web service, as defined on the applicable document flow, also define the applicable web service action here.

Register an application in Azure to manage the authentication and permissions for the AS2 web app. For more information, refer to Register an application with the Microsoft identity platform.

Add a client secret to the registered application. For more information, refer to Add a client secret.

Later in the AS2 setup, you need these values of the registered app:

• Application (client) ID
• Directory (tenant) ID
• Application ID URI
• Client secret value

You can use the File explorer to quickly access and view the general storage location as defined by the connector of a selected inbound definition. The File explorer offers limited functionality. You can only view, copy, move, or delete files.

You can, for example, use the file explorer to see if all EDI message files in the general storage location are distributed.

If you use the AS2 protocol to receive EDI messages from an EDI partner, use the AS2 web app to manage the interaction with the EDI partner.

The AS2 web app runs in the Azure cloud.

When the web server of the EDI partner sends data to the AS2 web app, it:

1. Decompresses the received data, if the received data is compressed.
2. Decrypts the data.
3. Checks the signature.
4. Stores the data in an EDI message file in the general storage location.
5. Sends an MDN reply to the web server of the EDI partner. The MDN reply can be that the data is:
   • Processed successfully.
   • Not processed because something went wrong. For example, the data cannot be decrypted, or the signature is invalid.

If you use the AS2 protocol to send EDI messages to an EDI partner, use the AS2 web app to manage the interaction with the EDI partner.

The AS2 web app runs in the Azure cloud.

When you run a web service action using the AS2 protocol, an EDI message is sent to the AS2 web app.

The web service action calls the send method of the AS2 web app to send the data to the EDI partner.

The AS2 web app send method:

• Encrypts the data.
• Signs the data.
• Compresses the data, if applicable.
• Sends the data to the web server of the EDI partner.
• Receives an MDN reply from the web server of the EDI partner.
• Sends the MDN reply from the EDI partner to EDI history of the web service action in EDI studio that originally sent the data.

Set up an app configuration. Create the App Configuration and in the App Configuration set the required key values.

Copy the connection string of the App Configuration from the Access keys page and save it somewhere. Usually, you use the connection string of the primary key. You need the connection string to connect the App Service to the App Configuration, in the configuration of the App Service.

For more information, refer to About Azure App Configuration.

Key values

To add the key values to the App Configuration, download the Default AS2 App Configuration and extract it.

The default AS2 web app name prefix for the keys is 'AS2WEBAPP'. If you want to use another prefix, you can change it. To do so, before you import the key values, edit the 'DefaultAS2AppConfiguration.json' file in a text editor.

Note:

• You define the AS2 web app name in the App Service settings (ApplicationSetup:ApplicationId). For consistency purposes, you are advised to use the same name for the App Service and the AS2 web app name.
• When you edit the 'DefaultAS2AppConfiguration.json' file, you can also set the key values. However, do not set the values for these keys in the file:
  • AS2WEBAPP:As2Setup:OwnedPrivateKey
  • AS2WEBAPP:As2Setup:PartnerPublicKey
  • AS2WEBAPP:Storage:Key

When you have finished editing the JSON file, import the 'DefaultAS2AppConfiguration.json' file to your App Configuration. For more information, refer to Import data from a configuration file.

In the App Configuration, you can edit the values of the imported keys with the Configuration explorer. To do so:

• For most of the keys, you can use the Edit option.
• For these keys, use the Add Key Vault reference option:
  • AS2WEBAPP:As2Setup:OwnedPrivateKey
  • AS2WEBAPP:As2Setup:PartnerPublicKey
  • AS2WEBAPP:Storage:Key

The key configuration that is required for the AS2 web app is:

Create and configure an App service in the Azure portal. The app service is the AS2 web app.

On creation of the app service, in the:

• Runtime stack field, select '.NET 6 (LTS)'.
• Operation system field, select 'Windows'.

Fill in the other fields as desired. For more information, refer to Create a Web app.

To configure the web app, add and edit the required app settings. Do not remove the automatically generated app settings. For more information, refer to Configure app settings.

Add and edit these app settings:

If you run the AS2 web app in the AS2 inbound process, it stores the data in EDI message files in the general storage location. Usually, the general storage location is defined by an Azure Storage account.

You can create an Azure Storage account or, if you already have an Azure Storage account, use that one. For more information, refer to Create an Azure storage account.

In the storage account, create the file share where the EDI message files must be stored by the AS2 web app. For more information, refer to Create a file share.

Set up a document flow to import an item counting message from a specific 3PL warehouse.

On the document flow, set the 'Warehouse - XML to Counting journal' message. This message receives the item counting information from the 3PL warehouse.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Warehouse - XML to Counting journal' message as request message.

Set up a document flow to send a picking list message to a specific 3PL warehouse.

On the document flow, set the 'Warehouse - Picking list to XML' message. This message sends the picking list to the 3PL warehouse.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Warehouse - Picking list to XML' message as request message.

Set up a document flow to define how to import a picking list registration that you received from a specific 3PL warehouse.

On the document flow, you can set one of these EDI messages to import a picking list registration:

• 'XML picking list registration to EDI inventory order' (custom message): If you use staging, use this message to receive a picking list registration from a 3PL warehouse. This message imports the received picking list registration into the EDI inventory order journal. When the import is completed, the applicable validations are done automatically.
• 'Warehouse - XML to Picking list registration': If you do not use staging, use this message to receive a picking list registration from a 3PL warehouse. This message imports the received picking list registration directly into the Picking list registration journal.

You can choose to exchange this EDI message using a web service. In this case, instead of a message, use an inbound web service action with one of the above messages as request message.

Set up a document flow to define how to import an order acknowledgement message from a specific vendor.

On the document flow, set the 'Purchase - XML to Acknowledgement' message. This message updates the acknowledgement status in the EDI history.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Acknowledgement' message as request message.

Set up a document flow to define how to import a packing slip message from a specific vendor.

On the document flow, set the 'Purchase - XML to Delivery' message. This message imports the packing slip from your vendor into the arrival journal. This message is also known as an advance shipping notice (ASN).

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Delivery' message as request message.

Set up a document flow to define how to import an invoice message from a specific vendor.

On the document flow, set the 'Purchase - XML to Invoice' message. This message imports the invoice from your vendor into the invoice register journal.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Invoice' message as request message.

Set up a document flow to define how to send a purchase order message to a specific vendor.

On the document flow, set the 'Purchase - Order to XML' message. This message sends the purchase order to your vendor.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Purchase - Order to XML' message as request message.

Set up a document flow to define how to import an order confirmation message from a specific vendor.

On the document flow, set the 'Purchase - XML to EDI confirmation' message. This message imports the order confirmation into the EDI purchase order journal. When the import is completed, the applicable validations are done automatically.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to EDI confirmation' message as request message.

Set up a document flow to send a receipts list message to a specific 3PL warehouse.

On the document flow, set the 'Warehouse - Receipts list to XML' message. This message sends the receipts list to the 3PL warehouse.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Warehouse - Receipts list to XML' message as request message.

Set up a document flow to define how to send a sales packing slip message to a specific customer.

On the document flow, set the 'Sales - Delivery to XML' message. This message sends the packing slip to your customer. This message is also known as an advance shipping notice (ASN).

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Sales - Delivery to XML' message as request message.

Set up a document flow to define how to send a sales order confirmation message to a specific customer.

On the document flow, set the 'Sales - Confirmation to XML' message. This message sends the sales order confirmation to your customer.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Sales - Confirmation to XML' message as request message.

Set up a document flow to define how to send a sales invoice message to a specific customer.

On the document flow, set the 'Sales - Invoice to XML' message. This message sends the sales invoice to your customer.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Sales - Invoice to XML' message as request message.

Set up a document flow to define how to import a received order (Delfor) from a specific customer.

On the document flow, you can set the 'Sales (Delfor) - XML to EDI Delfor journal' message. This message imports the received sales order (Delfor) into the EDI Delfor journal. When the import is completed, the applicable validations are done automatically.

You can choose to exchange this EDI message using a web service. In this case, instead of a message, use an inbound web service action with the 'Sales (Delfor) - XML to EDI Delfor journal' message as request message.

If you set up EDI to export data to the AS2 web app, for the outbound document flows, define a web service action instead of a message.

Make sure the desired export message is defined for the web service action that you use in an outbound document flow. You can link, for example, the EDI tutorial export messages to a web service action that you define for an outbound document flow.

Before you can exchange EDI messages, set up the EDI setup for your legal entity.

Use inbound definitions when you receive EDI message files from the AS2 web app.

Set up an inbound definition of type EDI to move files that are structured in line with an EDI standard (for example, EDIFACT) from the general storage location to a specific storage location.

To determine which file distribution definition applies, this data must be read from the file:

• Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
• Recipient: The data in the file that indicates to which company in D365 FO the data must be imported.

Example

EDI file content example:

UNH+1+ORDERS:d:12A:EU:EAN123

Example of setup that can be applied to get the type (ORDERS):

Use inbound definitions when you receive EDI message files from the AS2 web app.

Set up an inbound definition of type Fixed text to move files with defined start positions and lengths for fields from the general storage location to a specific storage location.

To determine which file distribution definition applies, this data must be read from the file:

• Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
• Recipient: The data in the file that indicates to which company in D365 FO the data must be imported.

Example

Fixed text file content example:

ORDER10002US-027M0001123.452025-03-01

Example of setup that can be applied to get the customer ID (US-027):

Use inbound definitions when you receive EDI message files from the AS2 web app.

Set up an inbound definition of type JSON to move files with data-object notation from the general storage location to a specific storage location.

To determine which file distribution definition applies, this data must be read from the file:

• Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
• Recipient: The data in the file that indicates to which company in D365 FO the data must be imported.

Example

JSON file content example:

{"Stores":["Lambton Quay","Willis Street"],"Manufacturers":[{"Name":"Acme Co","Products":[{"Name":"Anvil","Price":50}]},{"Name":"Contoso","Products":[{"Name":"Elbow Grease","Price":99.95},{"Name":"Headlight Fluid","Price":4}]}]}

Examples of JSON path expressions that can be applied to this example:

• Manufacturers[0].Name: Finds the name of the first manufacturer: Acme Co.
• $..*[?(@.* == 'Acme Co')]: Finds the name of the token: Name.

Note: JSON path expressions are case sensitive.

Use inbound definitions when you receive EDI message files from the AS2 web app.

Set up an inbound definition of type Text to move files with field and line separators (for example, CSV files) from the general storage location to a specific storage location.

To determine which file distribution definition applies, this data must be read from the file:

• Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
• Recipient: The data in the file that indicates to which company in D365 FO the data must be imported.

Example

Text file content example:

ORDER;10002;US-027;M0001;123.45;2025-03-01

Example of setup that can be applied to get the customer ID (US-027):

Use inbound definitions when you receive EDI message files from the AS2 web app.
Set up an inbound definition of type XML to move files in XML format from the general storage location to a specific storage location.

To determine which file distribution definition applies, this data must be read from the file:

• Type: The EDI message type of the data in the file. For example, 'Order' or 'Invoice'.
• Recipient: The data in the file that indicates to which company in D365 FO the data must be imported.

Example

XML file content examples, without and with namespace:

• <xml><invoice><header><id>invoice123</id><sender>ABC</sender></header></invoice></xml>
• <xml xmlns=[namespace]><invoice><header><id>invoice123</id><sender>ABC</sender></header></invoice></xml>

Examples of XPath expressions that can be applied to this example:

• /*: Finds the name of the first tag: invoice. Note: if you use * in the XPath expression, it finds the name of the tag instead of the tag value.
• /xml/invoice/header/sender: Finds the value of the 'sender' tag: ABC.
• /ns:xml/ns:invoice/ns:header/ns:id: Finds the value of the 'id' tag: invoice 123. Note: If the XML has a namespace, make sure to define the namespace in the Namespace field. When the inbound definition is run, in the expression, 'ns' is replaced with the defined namespace.

Set up a web service application for the project that connects to the AS2 web app.

For more information refer to: Set up web service application for project.

For the web service application, use these settings:

Set up the outbound web service actions to export data to the AS2 web app. With the mentioned settings, the web service action calls the send method of the AS2 web app to send the data to the EDI partner.

For more information, refer to Set up web service action - Outbound.

For the outbound web service actions for AS2, use these settings:

For the outbound web service actions for AS2, set these attributes:

When an EDI Delfor journal is processed with the 'Sales (Delfor) - EDI Delfor journal to Order' message, errors can occur. If an error occurs:

• The EDI Delfor journal is not processed.
• The EDI Delfor journal message status is set to Error.
• The error is logged in the EDI Delfor journal Infolog.

You can solve processing errors and have the EDI Delfor journal processed again.

The delivery forecast sales orders that you receive with the 'Sales (Delfor) - XML to EDI Delfor journal (830)' message are stored in the EDI Delfor journal.

These EDI Delfor journals are validated according to the applicable journal validation setup. If the applicable validation rules are not met, an error or warning is given. Before the EDI Delfor journals can be processed further, review the errors and warnings, and take appropriate actions.
If journal validation errors are given, you have these options:

• Solve the errors. You can solve validation errors in:
  • The EDI Delfor journal, where you can make the appropriate changes.
  • Microsoft Dynamics 365 for Finance and Operations. For example, if the setup must be changed to solve the error.
• Cancel the EDI Delfor journal, line, or address with errors.

You cannot accept headers, lines, or addresses with errors. If you do so, and approve the EDI Delfor journal, the header, line, or address with errors is again set to Rejected.

If the errors are solved or lines or addresses with errors are canceled, approve the EDI Delfor journal.

The delivery forecast sales orders that you receive with the 'Sales (Delfor) - XML to EDI Delfor journal (830)' message are stored in the EDI Delfor journal.

These EDI Delfor journals are validated according to the applicable journal validation setup. If the applicable validation rules are not met, an error or warning is given. Before the EDI Delfor journals can be processed further, review the errors and warnings, and take appropriate actions.

If journal validation warnings are given, you have several options:

• Accept the header, line, or address with warnings.
• Solve the warnings. You can solve validation warnings in:
  • The EDI Delfor journal, where you can make the appropriate changes.
  • Microsoft Dynamics 365 for Finance and Operations. For example, if the setup must be changed to solve the warning.
• Cancel the EDI Delfor journal, line, or address with warnings.

If all warnings are solved, accepted, or canceled, approve the EDI Delfor journal.

• The EDI inventory order is not processed.
  
• The EDI inventory order message status is set to Error.
  
• The error is logged in the EDI inventory order journal Infolog.
  

The EDI inventory orders are validated according to the applicable journal validation setup. If the applicable validation rules are not met, an error or warning is given. Before the EDI inventory order can be processed further, review the errors and warnings, and take appropriate actions.
If journal validation errors are given, you have these options:

• Solve the errors. You can solve validation errors in:
  • The EDI inventory order, where you can make the appropriate changes.
  • Microsoft Dynamics 365 for Finance and Operations. For example, if the setup must be changed to solve the error.
• Cancel the EDI inventory order, line, or address with errors.

You cannot accept headers, lines, or addresses with errors. If you do so, and approve the EDI inventory order, the header, line, or address with errors is again set to Rejected.

If you use EDI inventory order staging in your EDI process, the received information is imported into the EDI inventory order journal by the relevant custom messages. You can, for example, use staging in your EDI process for picking list registrations or product receipts.
The EDI inventory orders are validated according to the applicable journal validation setup. If the applicable validation rules are not met, an error or warning is given. Before the EDI inventory order can be processed further, review the errors and warnings, and take appropriate actions.

• The EDI purchase order confirmation is not processed.
  
• The EDI purchase order confirmation message status is set to Error.
  
• The error is logged in the EDI purchase order confirmation journal Infolog.
  

The purchase order confirmations that you receive with the 'Purchase - XML to EDI confirmation' message are stored in the EDI purchase order confirmations journal.
These EDI purchase order confirmations are validated according to the applicable journal validation setup. If the applicable validation rules are not met, an error or warning is given. Before an EDI purchase order confirmation can be processed further, review the errors and warnings, and take appropriate actions.
If journal validation errors are given, you have these options:

• Solve the errors. You can solve validation errors in:
  • The EDI purchase order confirmation, where you can make the appropriate changes.
  • Microsoft Dynamics 365 for Finance and Operations. For example, if the setup must be changed to solve the error.
• Cancel the EDI purchase order confirmation, line, or address with errors.

You cannot accept headers, lines, or addresses with errors. If you do so, and approve the EDI purchase order confirmation, the header, line, or address with errors is again set to Rejected.

The purchase order confirmations that you receive with the 'Purchase - XML to EDI confirmation' message are stored in the EDI purchase order confirmations journal.

You can test if the setup of a specific inbound definition or of all inbound definitions delivers the expected result. usually, you do so for a test file.

During the test, these checks are done:

• Is the selected test file found? Or if no test file is defined, are the files in the general storage location found?
• Is a matching file distribution definition found in the selected inbound definition? Or if no inbound definition is selected, is a matching file distribution definition found in any of the inbound definitions?

The test result is shown in an info message.

Note: During the test, no files are moved from the general storage location. Also, no renaming of the files is applied.

To test an inbound definition, make sure a test file is available in the Working folder as defined by the connector of the inbound definition.

Use the EDI Delfor journal to monitor the delivery forecast sales orders.

The delivery forecast sales orders that you receive with the 'Sales (Delfor) - XML to EDI Delfor journal (830)' message are stored in the EDI Delfor journal.

If you monitor EDI Delfor journals, the statuses are important. For more information on these statuses, refer to 'EDI staging journal statuses'.

For each customer, item, and customer order combination, for which you receive delivery forecasts, you can provide an overview of the related EDI Delfor sales information. You can use this data to apply several validation rules to EDI Delfor journals.

The EDI Delfor sales information is:

• Created and updated when an EDI Delfor journal is processed, and the related delivery forecast order is imported into the Sales orders table with the 'Sales (Delfor) - EDI Delfor journal to Order' message. To create and update the EDI Delfor sales information, on this 'Sales (Delfor) - EDI Delfor journal to Order' message, you must add the mapping for the EDI Delfor Sales information (BisEdiDelforSalesData) table.
• Updated when a packing slip is posted for a sales order that is created based on an EDI Delfor journal. This update is only done if the EDI Delfor sales information exists for the customer, item, and customer order combination.