EDI party validation

Introduction

EDI party validation is a mechanism in EDI studio that ensures inbound EDI messages are processed and an EDI staging journal is created, even when required setup is missing. Missing setup can be the EDI party or document flow.

Note: If no target company is defined in the inbound EDI message, the message is not processed and no EDI journal is created.

Setup

To apply EDI party validation, define the relevant setup on:

EDI parameters
Documents
Messages
Validation rules
Journal validations

EDI parameters

In the EDI parameters, set the Ignore missing setup field:

Value	Description
No	By default, the missing setup is not ignored when you run a message. Running a message, with missing setup in the inbound EDI message, results in an error. No EDI staging journal is created. You can use this option if you want to not ignore missing setup for most of your inbound EDI messages. In this case, no changes to the existing documents and messages are required. Only if you want to ignore missing setup for a specific message, change the related document and message.
Yes	By default, the missing setup is ignored when you run a message. Running a message, with missing setup in the inbound EDI message, creates a staging journal without an EDI party or related document flow defined. You can use this option, for example, if you already have many messages defined. And if you want to ignore missing setup for most of your inbound EDI messages. In this case, no changes to the existing documents and messages are required. Only if you want to not ignore missing setup for a specific message, change the related document and message.

Value

Description

By default, the missing setup is not ignored when you run a message. Running a message, with missing setup in the inbound EDI message, results in an error. No EDI staging journal is created.

You can use this option if you want to not ignore missing setup for most of your inbound EDI messages. In this case, no changes to the existing documents and messages are required.

Only if you want to ignore missing setup for a specific message, change the related document and message.

Yes

By default, the missing setup is ignored when you run a message. Running a message, with missing setup in the inbound EDI message, creates a staging journal without an EDI party or related document flow defined.

You can use this option, for example, if you already have many messages defined. And if you want to ignore missing setup for most of your inbound EDI messages. In this case, no changes to the existing documents and messages are required.

Only if you want to not ignore missing setup for a specific message, change the related document and message.

Note: The setting of the Ignore missing setup field in the EDI parameters only applies to inbound EDI messages that are used to create an EDI staging journal.

For more information, refer to Set up EDI studio parameters.

Document setup

Use a document of type 'Staging' to import data in an EDI staging journal. On the Staging document, to the BisEdiHistory record, add the IgnoreSetupError field.

For more information, refer to Set up staging document.

Message setup

Set up an EDI message to import data into an EDI staging journal. Use the document of type 'Staging' as target document. For the BisEdiHistory record, set up the mapping for the IgnoreSetupError field.

Apply a constant value and define the desired constant value:

Value	Description
No	If in the EDI parameters the Ignore missing setup field is set to 'Yes', by default, the missing setup is ignored when you run a message. For specific messages, you can set the missing EDI party setup to be not ignored.
Yes	If in the EDI parameters the Ignore missing setup field is set to 'No', by default, the missing setup is not ignored when you run a message. For specific messages, you can set the missing EDI party setup to be ignored.

Value

Description

If in the EDI parameters the Ignore missing setup field is set to 'Yes', by default, the missing setup is ignored when you run a message.

For specific messages, you can set the missing EDI party setup to be not ignored.

Yes

If in the EDI parameters the Ignore missing setup field is set to 'No', by default, the missing setup is not ignored when you run a message.

For specific messages, you can set the missing EDI party setup to be ignored.

For more information, refer to Set up messages.

Validation rule setup

With the setup to ignore missing setup, EDI staging journals can be created without an EDI party or related document flow defined. Processing such a staging journal results in errors. Therefore, make sure the staging journals are validated accordingly. To do so, set up validation rules that check if:

An EDI party exists.
A document flow is defined for the EDI party.

For the EDI staging journal tables, these predefined validation rules are available to check if the EDI party exists or to check if a document flow is defined for the EDI party:

Table	Validation class	Description
BisEdiPurchaseJour	BisEdiCheckVendorExist	Checks if the vendor exists for the purchase order, using the vendAccount field.
	BisEdiCheckVendorDocumentFlowExists	Checks if a document flow is defined for the vendor of to the purchase order.
BisEdiPurchaseArrivalJour	BisEdiCheckPurchaseArrivalVendorExist	Checks if the vendor for the purchase arrival exists.
	BisEdiCheckPurchaseArrivalVendorDocumentFlowExists	Checks if a document flow is defined for the vendor of to the purchase arrival.
BisEdiSalesJour	BisEdiCheckWarehouseExist	Checks if the warehouse on the sales order exists in the InventLocation table, using the InventLocationId field.
	BisEdiCheckWarehouseDocumentFlowExists	Checks if a document flow is defined for the warehouse of the sales order.
	BisEdiCheckCustomerExist	Checks if the customer exists for the sales order, using the CustAccount field.
	BisEdiCheckCustomerDocumentFlowExists	Checks if a document flow is defined for the customer of the sales order.
BisEdiInventoryOrderJour	BisEdiCheckInventoryOrderWarehouseExists	Checks if the warehouse for the inventory order exists, using the inventlocationId field.
	BisEdiCheckInventoryOrderDocumentFlowExists	Checks if a document flow is defined for the warehouse of the inventory order.
BisEdiTransferOrderJour	BisEdiCheckTransferFromLocationExists	Checks if the from warehouse of the transfer order exists, using the inventlocationFrom field.
	BisEdiCheckTransferFromWarehouseDocumentFlowExists	Checks if a document flow is defined for the from warehouse of the transfer order.
	BisEdiCheckTransferToLocationExists	Checks if the to warehouse of the transfer order exists, using the inventlocationIdTo field.
	BisEdiCheckTransFerToWarehouseDocumentFlowExists	Checks if a document flow is defined for the to warehouse of the transfer order.
BisEdiDelforJour	BisEdiCheckCustomerExist	Checks if the customer exists for the sales order, using the CustAccount field.

For more information, refer to Set up validation rules.

Journal validation setup

Set up an EDI journal validation that applies the validation rules to check if the EDI party exists and to check if a document flow is defined for the EDI party.

Make sure, to use an account relation of type 'Legal entity'.

For more information, refer to Set up journal validations.

Process

If you have finished the EDI party validation setup, incoming EDI messages are processed accordingly.

For more information, refer to Process EDI messages.

Based on the applied EDI party validation setup, EDI journals can be created with missing information. The applied validation rules will give a warning or error message. Before you can further process the EDI journal, manually add the missing setup.

For more information, refer to Monitor EDI.

Related to	Notes
Set up EDI studio parameters
Set up EDI studio parameters

EDI party validation Concept