Request a Consultation

CheckPoint Consulting Blog

Anyone who has used FDMEE to automate loads via OpenBatch has come across the problem of the “openbatch” directory filling up with archive directories. FDMEE creates an archive directory each time a Batch Execution is run, whether or not any files are processed. This not only clogs up the directory, but also makes it very difficult to find previously loaded files due to FDMEE’s naming convention for archived files.

A solution was needed to organize the archived directories, rename the directories with a date/time reference, and delete empty archive directories. This was accomplished using Custom script that is run after the OpenBatch procedure is completed.

We will walk through the default OpenBatch process to show the “out-of-the-box” functionality, as well as the process with the Custom script implemented.

Note:  All screenshots and narrative relate to FDMEE version 11.1.2.4.200

In our example, we have one HFM application (TestApp) that will have OpenBatch procedures scheduled to load the application. We have created a directory with the application’s name under the “openbatch” directory. This is necessary to keep multiple application’s files/directories separated and for the Custom script to place the archived directories in the proper directory.

Image_1_Archopen_B.png

There are 3 Trial Balance files dropped into the application’s “openbatch” directory (TestApp) for processing.

Image_2_Archopen_B.png

The Batch Definition is setup as follows. Note that we define the “TestApp” application in the “Open Batch Directory” field. This is where the batch process retrieves the load files from.

Image_3_ARCHOPEN_B.png

The Batch Name is executed (usually via Schedule).

Image_4_ARCOPEN_B.png

By default, FDMEE creates an archive directory in the “openbatch” directory. The naming convention is sequential, and not very informative.

image_5_ARCHOPEN_B.png

The archived directory contains the 3 load files.

Image_6_ARCOPEN_B.png

Now we attach the Custom “After Batch Script” script to the Batch Definition.

Image_7_ARCHOPEN_B.png

A directory with a text file was created to ensure that the script does not delete the application’s directory if it is empty.

Image_8a_ARCHOPEN_B.png

Image_8b_ARCHOPEN_B.png

We once again place the 3 Trial Balance files into the application’s “openbatch” directory for processing.

Image_9_ARCHOPEN_B.png

The Batch Name is executed.

Image_10_ARCHOPEN_B.png

Notice that after the batch is executed the “openbatch” directory only contains the “TestApp” directory.

Image_11_ARCHOPEN_B.png

The archive folder that FDMEE created was moved to the “TestApp” application directory and renamed with a date/time file name designation.

Image_12_ARCHOPEN_B.png

The 3 loaded files are archived in the directory.

Image_13_ARCHOPEN_B.png

The Custom script not only helps organize directories it, also keeps the “openbatch” directory clutter-free. Hopefully this helps clarify what the current FDMEE OpenBatch functionality is and what can be done with Custom script to enhance the ease of use.