GEDI Mapping
"A 'GEDI Mapping Document', is a definition of rules to be applied when processing"
Last updated
"A 'GEDI Mapping Document', is a definition of rules to be applied when processing"
Last updated
In the 'GEDI Mapping List' page view in Business Central you will find 'GEDI Mapping Documents'. A 'GEDI Mapping Document', or short 'GEDI Mapping', is a definition of tables and fields in Business Central that should be exported from, imported to or be controlled. Along with rules and filters to be applied.
The 'GEDI Mapping' is structured in a table and processed from top to bottom row. There are many different types of rules that can be used, and new rules are often added upon release of new Standard App versions. This allows for a very powerful and flexible framework that can be used for much more than just EDI.
'GEDI Mappings' can be divided into some different concepts;
Import: Moving data from 'GEDI Messages' into tables and fields in Business Central.
Export: Moving data from tables and fields in Business Central to 'GEDI Messages'.
Control: There are different types of controls. For example controlling if fields in Business Central contains certain values or if they are empty etc.
Can be used as a pop-up error at certain events, for example release of Order or other Posting events.
Can be used to create comments in Business Central.
Can be used as "If this then that" rules to generate new 'GEDI messages'. The result can for example be triggering an error message to be sent by e-mail or a record to be updated with a 'GEDI status'.
Send PDF: Generate PDF mails with the Standard Business Central functionality, using the automization logic from the Standard App.
For example, when Invoice is posted, then the Invoice PDF will be automatically e-mailed to the customer as per configuration.
Internal functions: Running only internal functions, such as updating a status, creating a 'GEDI Message Log' or running a Code Unit.
As previously mentioned, the CIP integrates with the Standard App via an internal JSON format. In the Standard App the JSON format is structured by 'GEDI Class names' and 'GEDI property names'.
'GEDI Class names' correspond to a Message Document type, for example 'ORDER' or 'INVOICE' etc.
'GEDI Property names' correspond to a field or 'tag' as it's often called in EDI, for example 'OrderNumber' or 'InvoiceNumber'
When creating import mappings or export mappings, one of the main purposes is to define the rules for which Business Central tables and fields shall correspond to which 'GEDI Class Name' and 'GEDI Property Name' in the internal format.
