Export and import functionalities

Export allows the users to extract data from an IGFC instance to another. The user specifies which master data and transactional BODs to export. The data is then placed into a folder called package. The package has these contents:

  • Master data BODs

    The selected Infor, custom, and DSV master data document’s mapping of attributes with names, description and datatypes, and its related search templates. For flexible output integration, the content for a masterdata BOD also includes its related expressions and rules.

  • Custom master data

    The selected custom master data’s setup of table structure which includes attributes with names, description and data types, the content (data entry), and its related search templates.

  • Transactional BODs

    The selected Infor, custom, or DSV transactional document’s mapping of attributes with names, description and data types, its related expression and rules. For accounting framework integration, a transactional BOD content also includes its related journal entry templates and journal user fields.

Import makes use of the exported content package to input a set of data to an IGFC instance. This requires that the content comes from a source with an earlier or the same IGFC version as that of the destination.

Note: For IGFC versions 10.4.1.0 or earlier, import requires that the content comes from a source with the same application version as that of the destination.

Given the relationship between business documents, it is important that a package also includes the related documents that provide relevant information. Consider a purchase order transaction that refers to an item master to determine standard cost. In this case, both documents should be included in the package.

These are not included in the package:

  • Entity registration
  • Entity mapping
  • General ledger mapping
  • Web service security and API registration

The first three are all under master data setup module, which requires relevant master data business documents to be sent first to IGFC. While REST API type expressions are also included in the content package, if applicable, the corresponding API components are not part of the exported content from IGFC as this must come directly from ION API. This ensures that the API security keys and definitions are accurate and up to date when used in IGFC output generation rules.