GEDI Message Selection

"A 'GEDI Message Selections', is a definition of which events that should trigger 'GEDI Messages'"

GEDI Message Selection

Introduction

In the 'GEDI Message Selection' page view in Business Central you will find a overview of all 'GEDI Message Selections'. A 'GEDI Message Selection', is a definition of which events in Business Central should trigger which 'GEDI Message Codes' to be created as 'GEDI Messages'.

Example of how the 'GEDI Message Selection' overview can look like

The events are also categorized in subpages, as can be seen on the picture bellow. In general, the main 'GEDI Message Selection' overview is better to use for review, and the exact subpage is better for editing.

Examples of different 'GEDI Message Selection' subpages

A 'GEDI Messages' will only be created if the 'GEDI Profile' that runs the event, is allowed to use the 'GEDI Message Code' as defined in the 'GEDI Message Setup'. For example, multiple 'GEDI Message Codes' could be defined on the same event, but depending on the 'GEDI Profile' running the event, only some or all of the 'GEDI Message Codes' will actually trigger 'GEDI Messages'.

Active and Passive Events

Some events are Active and some are Passive;

• Active events: Events that are tracked when they happen, and then creates the 'GEDI Message' with the 'GEDI Message Code'. Usually this is standard Business Central events.

  For example, Posting of a Invoice, Release of an Order etc.

• Passive events: Only to define which job queue Categories should run which 'GEDI Message codes' in the 'GEDI Message Queue'. The actual 'GEDI Message' is created by another source than the event itself.

  For example, the CIP created a incoming sales order, a 'GEDI Mapping Document' created a status update.

Processing Methods

There are two different options to configure how the 'GEDI Message' should be processed; by a Job Queue Entry or "immediate". Most events will only work with either of the two options, and this is predefined.

• Job Queue Processing: Configured by selecting a 'Job Queue Category Code' that should process the 'GEDI Message Code'. This is the most common method and is used for almost all export, import and other actions that can be processed in the background.

  For example, the event "S.Invoice" happens after a Sales Invoice has been posted. The 'GEDI Message Code' for the Sales Invoice export request will be created in the 'GEDI Message Queue'. And the actual execution of the export will be done later by the Job Queue Entry with the corresponding Category Code.

• Immediate Processing: Configured by checking the "Manual Immediate Run" checkbox. Usually this means that the 'GEDI Message Code' defined is a control that will be processed directly. Either in the interface or in the background. This processing method is for example used for pop-up controls or for export of temporary data.

  For example, the event "C.S.Invoice" happens when a Sales order is requested to be posted for invoicing. This enables the control 'GEDI Message Code' to either allow or rollback the posting event. In the control, certain fields that are required for allowing the posting can be defined. If requirements are not met the posting event will be rolled back.