Data Manager Parameters (Standard only)

Exporting packages with YTD, QTD, or PERIODIC options

When running a Data Manager export package with the YTD, QTD, or PERIODIC option and you have parent members in the selection (for example, <ALL> is selected for one or more dimensions), you may encounter a system memory issue. This may occur because the MDX query takes into account parent members for data generation.

To avoid this issue, consider performing the following steps:

1. If it is not necessary to export 'YTD', 'QTD', or 'PERIODIC' data, use the 'SIGNEDDATA' option when running the package. This option runs an RSDRI query and the memory consumption is dramatically less.

2. If the SIGNEDDATA option does not meet your requirements, make sure there are no parent members for the dimensions that you set in the selection. This can be achieved by using the filter function in the Data Manager member selector with the filter condition CALC=N.

3. If choosing parent members is unavoidable, there is a parameter value in the DM dynamic script that can be adjusted so that the selection is split by Data Manager. Follow these steps:

   1. Click More  Organize Package List in the Data Manager interface.

   2. Select the export package you use and click Modify.

   3. Click View Package in the dialog.

   4. In the dynamic script editor dialog, find the INFO node and the parameter %DIMVALUE%, whose default value is E=24.

   5. Change the parameter value by following these steps:

      1. Set the value in the form [Dimension type]=value; different pairs should be separated by a semicolon.

      2. The dimension type can be all the delivered dimension types in the system: A for Account, C for Category, D for Datasrc, E for Entity, I for Intercompany, R for Currency, and T for Time.

      3. Generally, set the dimension that has more members in the selection for splitting.

When data volume is larger than the package size defined in Data Manager Process Chain

When loading transaction data into the system with the option Run default logic checked, the result of the logic calculation may be incorrect if the data volume is larger than the package size defined in Data Manager Process Chain.

Data Manager and script logic process data in different ways: Data Manager processes data in packages while script logic does not. If the total amount of data to load is larger than the package size defined, Data Manager will process the data in several rounds, and each time it loads the data and the default logic is invoked. When the script logic is executed for the subsequent packages of data, it will query data according to the selections and this is very likely to get data that has already been processed in previous rounds. This leads to the new result overwriting the original result.

To avoid issues, follow one of these solutions:

• Adjust the package size of the Data Manager Process Chain to a value that is larger than the total amount of data records.

  1. Run transaction RSPC, and double-click the process chain that is used for loading data. Then, double-click the process variant Convert.

  2. Click Display  Change and set the value of SPACKAGE_SIZE to a value larger than the total number of data records to be loaded.

  3. Click Save.

• Load the transaction data without selecting the option Run default logic option, and later run the default logic separately after the data is loaded.

• Change the script to force the members to be calculated each time the script logic is called. As an example, if the problem lies in the ACCOUNT dimension, you can use the statement below to force the system to select the members in ACCOUNT for calculation.

  *XDIM_MEMBERSET GRPACCOUNT=BAS(TOTAL_ACCOUNT)

For more details on the information presented above, see the following table: