Importing and Exporting Intersections

About Importing and Exporting Valid Intersections

You can export the filtered list of valid intersections from the listing page to a location on your local computer, or you can export them to the server. If no filter is defined on the listing page, then all intersections are exported.

Use the Import action to import intersections into the application from a location on your local computer or import them from the server. When you perform an import, the system tests the import file for anything that might break a definition; for example, if a cube is missing, or if an anchor dimension doesn't exist, or if a subrule is not found, errors are logged in the error file. Import jobs will only complete successfully if the import file has no errors.

Note:

Subrules provide information about the content of the rules such as the member selection or exclusion for anchor and non anchor dimensions, and the restriction type applied for each subrule.

Depending on the export or import location you choose, the intersections are exported or imported in either an Excel file format (XLSX) or a zip file format.

Note:

Locked valid intersection rules are not exported when you export valid intersections. Locked valid intersection rules (and rules that start with restricted prefixes such as FCCS_, OCX_, OEP_, OFS_, OPF_, OWP_, TRCS_) are not imported when you import valid intersections.

Valid Intersections Import File

The Excel import file must have two sheets with the following names for the first and second sheets:

  1. Rules
  2. Sub Rules

The Rules sheet has the following column headings:

  • Name
  • Position
  • Description
  • Enabled
  • Definition Type
  • Anchor Dim Name
  • Anchor Dimension Apply to Selected Members
  • Dim1
  • Dim1 Required
  • Dim2
  • Dim2 Required
  • DimX
  • DimX Required

The Sub Rules sheet has the following column headings:

  • Name - This column must contain the name of the Rule from the first sheet
  • Anchor Members
  • Anchor Exclusion
  • Anchor Exclusion All
  • Dim1 Members
  • Dim1 Exclusion
  • Dim1 Exclusion All
  • Dim2 Members
  • Dim2 Exclusion
  • Dim2 Exclusion All
  • DimX Members
  • DimX Exclusion
  • DimX Exclusion All

Exporting and Importing Valid Intersections

To export and import intersections:

  1. Click Application, and then click Valid Intersections.

  2. Apply filters to the listing, as needed. See Filtering Valid Intersections.

  3. To export, click Actions, then Export, and then select the target location for the export file:

    • Local: Saves the export file to a location on your local computer. If you choose this option, click Export, and then specify where to save the export file.

    • Outbox: Runs a job that saves the export file in a zip format to the server which you can download now or use to schedule an export job later. If you choose this option, click Save and Run Job.

      To download the export file from the Outbox:

      1. Click Application, and then click Jobs.
      2. Under Recent Activity click the export job.
      3. On the Job Details page, click Download icon to select a download location for the export file. You can also download the export file from the Inbox/Outbox Explorer for your business process.
  4. If editing the export file in Excel, note that the Excel file has two sheets: Rules and Sub Rules.

  5. To import, click Actions, then Import, and then select the location of the import source file:

    • Local: Loads the import file from a location on your computer. For Source File, click Browse to select the import file on your computer, and then click Import.

    • Inbox: Runs a job that loads the import file from the server. The import file must be in a zip file format. Enter the name of the file in Source File, click Save and Run Job, and then specify the Name and Error File on the Save as Job dialog. The error file provides information about the intersections that were not imported. You can download the error file from the Inbox/Outbox Explorer for your business process.