GEDI Message Codes
"A 'GEDI Message Code', is a definition of a specific function that a 'GEDI Message' will execute"
Introduction
In the 'GEDI Message Codes' page view in Business Central you will find 'GEDI Message Codes'. A 'GEDI Message Code', is a definition of a specific function that a 'GEDI Message' will execute. Each unique function has a corresponding unique 'GEDI Message Code'. For example Importing an EDI order is one 'GEDI Message Code', exporting an EDI Invoice is another.
Often 'GEDI Message Codes' comes in a pair of two; one request and one execution. The request is created in the 'GEDI Message Queue' triggered by an event in Business Central. When that request is later processed, the function is actually executed. For example, information is extracted and inserted as 'GEDI message lines' or a control process is executed. After execution, a second 'GEDI Message' on another 'GEDI Message Code' is created for the result. This way the event that puts 'GEDI Messages' in the 'GEDI Message Queue' are separated from the execution of the actual function. This allows batch processing via a Job Queue running in the background, instead of delaying the user experience.
For each 'GEDI Message Code', you can define a 'GEDI Status' that will be created. This will then update the processed record with the latest status.
On the 'GEDI Message code' you can define a number of days in the field "Delete in Queue Days Back" deciding how long 'GEDI Messages' should be saved in the 'GEDI Message Queue'. A Job Queue Entry will handle the deletion of entries past due.
Directions
A 'GEDI Message Code' can be configured in different Directions. This determines the main function of the 'GEDI Message Code'. The directions are;
Down: For importing data from a 'GEDI Message'. Usually originating from the CIP.
For example, an EDI order is written to 'GEDI Message' from CIP and should be imported as a Sales order.
Internal: For requests to create another 'GEDI Message' with another 'GEDI Message Code'.
For example, an invoice is being posted and the invoice request message is added to the 'GEDI Message Queue'.
Up: For exporting data to a 'GEDI Message'. Usually because the CIP should receive it.
For example, when invoice data is exported to 'GEDI Message' to later be read by the CIP.
Control: For controlling data in Business Central. Usually checking if required fields are missing data.
For example, an EDI order is imported and a control checks if there is article number match on all order lines.
Up Auto Finished: For a function that should be automatically marked as finished, to prevent the CIP from reading the 'GEDI Message'.
For example, a PDF invoice being sent out via Business Central e-mail functionality.
Posted: For exporting data to a 'GEDI Message' and directly posting it up to the CIP via xml port instead of letting the CIP read the 'GEDI Message'. Usually this is only used when the CIP is not allowed to have a web service integration with Business Central. As the CIP in this case has no way of sending back information such as status updates to Business Central.
For example, an EDI Invoice is sent via Basic Invoice Setup, which doesn't require a web service. Statuses for the EDI Invoice is only stored and found in the CIP portal, as they are not sent back to Business Central.
Last updated
