About Context Administration

This section explains Coexistence Mapping Context. Coexistence Mapping Context is an easy way to deal with a mixed V5/V6 structure. It enables, during transaction, to gather data into a defined set, isolate or unsynchronize them from data related to other Coexistence Mapping Contexts. A Coexistence Mapping Context can be seen as the association between a Mapping Table string and a logical/physical location. The Coexistence scenarios are managed in a given Mapping Context called the main Context. A main Context can reference a list of Mapping Contexts, which are called friend Contexts.

Related Topics
Setting Up Coexistence Mapping Context

The strings in a Coexistence Mapping Context are,

  • The Context Name. This is the string given to the Mapping Table Manager to tag all the Mapping Table elements created by this Manager. So, the Context Name is associated to every components transferred by a Mapping Table Manager. For example, if a V5 document is imported into V6 in a given Coexistence Context, another import of this document in the same Context is not possible. However, an import of this document in a different Context is allowed if this document has not been imported previously in this Context.

Using Coexistence Mapping Context it is possible to,

  • Carry over : a specific Mapping Context can be used for a given transaction and not reused later ( for example by adding the date of the day in the Context name ).

  • V5/V6 loops: for a set of data, several interactions between V5 and V6 can be managed in loop if the same Mapping Context is used at import and export stage

  • Search order at FBDI: the order of friend Contexts is relevant for FBDI process. If data doesn't exist in main Context during import, then data is searched sequentially from the first friend Context until data is found. If data is not found, it is mapped in the main Context and then imported. With this search mechanism, it is possible to define data preferences at import stage.

A Coexistence Mapping Context is mandatory for all FDBI transactions. By default, all transactions are processed in the default Mapping Context named 'COEXISTENCE'.

The Context tab in Tools > Options allows you to define personalized Coexistence Mapping Contexts. You can,

  • Create/Add Contexts
  • Add friends to a Context
  • Save/Update the XML file containing the context definitions

Note: You cannot delete or reorder contexts using the Context tab and it is strongly not recommended to modify manually the .xml file. It is possible to add new context in time, but any change made on context definition could have critical impact on FBDI results. That is why it is very important to manage context definition at administration level.