Importing a content package

Performing subsequent updates to an integration, initially set up by importing of a content package, can be done by importing another content package. You must ensure that the initial and subsequent content packages originate from the same source. Source denotes an integration and an IGFC instance or tenant.

An example is a business solution content created in IGFC’s integ101 in a specific IGFC instance or tenant. The initial and subsequent content packages must also come from the same integration of the same instance or cloud tenant.

See Export and import functionalities.

  1. Select Content Management > Import/Export Data.
  2. On the Import tab, select the content package to import. A content package must be in .zip file format to be valid.
  3. Click Import.
  4. Select Yes.
    Upon confirmation, the document poller is automatically deactivated to suspend the processing of business documents.

    The imported documents along with the related search templates are displayed on the BOD, custom master data, and DSV pages; these documents are automatically generated. For accounting framework integration, business rules contain expressions, journal entry templates, journal user fields and rules for the transactional business documents. For flexible output integration, business rules contain expressions and rules for the master data and transactional business documents.

  5. Run these tasks after import:
    1. Modify the configurations and setup data.
      Configurations and setup data that are imported cannot be modified directly, except for custom master data content (data entry). A customize option is available to allow changes to a record.

      See Customizing an imported record.

    2. Rules included in the package will not contain entity references. In order to define Sender/Receiver entities in the rules page, these relevant setups must be performed:
      1. Register the entities. See Register entities.
      2. Map the entities. See Mapping entities.
      3. Update search template type expressions with source entity references. This applies to expressions whose source master data is a master data business document. Upon import, a default Sender Entity is assigned for expressions previously defined with a specific entity from the source of the content package. Review the expressions and update the source entity accordingly.
      4. Import API security keys and definitions referenced in expressions. See Import API requirements
      5. Update the rules page with sender and receiver entities.
        Note: Click Customize before specifying the entities.
      6. Save and activate the rule record.
      7. For accounting framework integration, dimension code assignments and general ledger mapping pages must also be updated, if applicable.

        See Assigning dimensions and Define general ledger mapping.

    3. For accounting framework integration, rules with a summarized posting method are imported with Account summarization option set to All, by default. If applicable, modify this setting.
    4. Activate the document poller.