Defining File-Based Options

For file-based integrations, you can specify the file name and inbox folder used to store the file. Using a file, you can load data to a single period or multiple periods. There are several methods to load data to multiple periods. One method is to use a single file with multiple columns and each column can be mapped to period either using header record or period mappings. The option is to use a single file for each period. To use one file per period, then you can use a specific file name format to identity the period.

Category and periods settings associated with the file may use predefined values. These settings may restrict the options available when editing selections.

Note:

If the Period and Year are mapped in the import format (on the Map Dimensions page), the Period Mapping Type and Calendar show on the Options page. If the Period and Year are not mapped in the import format, the Period Mapping Type and Calendar fields do not show on the Options page.

Watch this tutorial for information about setting file-based data integrations options: Setting File-Based Data Integration Options and Running Integrations in Enterprise Planning Cloud.

To select file-based options:

1. From the Data Integration home page, click to the right of the file-based integration, and then select Options.
2. Select the Options tab.
3. From File Name, select the name of the source system file.

   If you do not specify a directory name, the system imports data files from the Data Integration home directory. In this case, reference the file in the Applications-Inbox/Outbox Explorer using the format: epminbox/<filename> in the file name field. epminbox/<filename> should not specified in the Directory field.

   When only the file name is provided, then data must be entered for a single period on the Run Integration page.

   To load multiple periods, create a file for each period and append a period name or period key to the file name. When the integration is executed for a range of periods, the system constructs the file name for each period and uploads it to the appropriate POV.

4. In Directory, specify the folder where the file is located.

   Note:

   If you do not specify a directory name for a file, the system imports data files from the Data Integration home directory. In this case, reference the file in the Applications-Inbox/Outbox Explorer using the format: epminbox/<filename> in the File Name field, but do not specify epminbox/<filename> in this field.
5. From the File Name Suffix to load data into multiple periods, select either: Period Name or Period Key.

   A suffix is appended to the file name, and the system adds the file extension after adding the suffix. If you leave the file name blank, then the system looks for a file with suffix. When the file name suffix type is provided, then the file name is optional in this case, and it is not required on the Run Integration page.

   If the file name suffix type is a period key, the suffix indicator and period date format are required (as the suffix set) in the file name and must be validated as a valid date format.

   For example, specify:

   1. 1_Jan-2018.txt
   2. 1_Feb-2018.txt
   3. 1_Mar-2018.txt

   In this case, when you run the integration, enter 1_.txt in the file name field and select Period Name for the suffix indicator. Then run the integration for the January to March periods.

6. In Period Key Date Format, specify the data format of the period key that is appended to the file name in JAVA date format (SimpleDateFormat).
7. From Category, select the category.

   The categories listed are those that you created in the in the Data Integration setup, such as "Actual." See Managing Category Mappings.

8. From Cube, specify the plan type to load the data.
9. Click Save.