Wednesday 25 March 2015

EXPORT IMPORT SECURITY UTILITIES


EXPORT IMPORT SECURITY UTILITIES

The ExportSecurity utility exports Planning access permissions to the SecFile.txt file, enabling you to export and import access permissions across applications

The ImportSecurity utility loads access permissions for users or groups from a text file into Planning.

To locate the Export Import Utilities:

Navigate to the bin directory in this path -

HYPERION_HOME/products/Planning/bin



To execute the ExportSecurity command, open a command prompt and navigate to the directory containing the ExportSecurity command.

Limit the export by specifying a member parameter.

/A=ApplicationName

/U=username

Use only /S_USER or /S_GROUP, not both.



Enter the password


Successful initialization of Planning Application:


The ExportSecurity utility automatically creates the SecFile.txt file, from which we can import access permissions.




The ImportSecurity command will import the security contained in the secFile.txt.  Using the command prompt, navigate to the directory containing the ImportSecurity utility.


The syntax used to execute the utility is:

ImportSecurity.cmd “Application,username,SL_COMMA,,,”



A message will appear notifying if the import failed or was successful. You can also check the log file importsecurity.log in the bin directory to verify the results.

Thursday 19 March 2015

Creating A Data Server - Oracle Data Integrator (ODI)



To Create a Data Server:


1. In Topology Navigator expand the  Technologies node in the Physical Architecture accordion.



2. Select the Technology you want to create a data server for

3. Right click and select New Data Server



4. Fill in the fields in the Definition tab

Name: Name of the Data Server that will appear in ODI

5. Define the Connection parameters for the Data Server



To Connect Through JDBC:

Go to the JDBC tab, and fill in the following fields:

JDBC Driver - Name of the JDBC Driver used for connecting to the data server

JDBC Url - Url allowing you to connect to the Data Server



6. From the File menu, click Save to validate the creation of the Data Server





Friday 6 March 2015

Managing Database Connections for Financial Reporting


Editing Database Connections - Financial Reporting

You can edit database connections, when required.

 To edit a database connection:
  1. In Database Connection Manager, select the database connection to edit, then click Edit.
  2. Make your changes, then click OK.

Thursday 5 March 2015

ODI - Logical Schema


ODI - Logical Schema


The aim of the logical schema is to ensure the portability of procedures and models on different physical schemas at runtime.

A logical schema is an alias that allows a unique name to be given to all the physical schemas containing the same datastore structures.

A logical schema can have one or more physical implementations on separate physical schemas, but they must be based on data servers of the same technology.

A logical schema is always directly linked to a technology.

To be usable, a logical schema must be declared in a context.

Declaring a logical schema in a context consists of indicating which physical schema corresponds to the alias -logical schema - for this context.

Creating a Logical Schema

To create a logical schema:

In Topology Navigator expand the Technologies node in the Logical Architecture accordion.





Select the technology you want to attach your logical schema to.

Right-click and select New Logical Schema.




Fill in the schema name.




For each Context in the left column, select an existing Physical Schema in the right column. This Physical Schema is automatically associated to the logical schema in this context. Repeat this operation for all necessary contexts.

From the File menu, click Save

Processing Batch Files


To process batch files, you use Batch Loader, which you initiate from FDM Workbench or FDM Task Manager. You run Batch Loader from the Batch Processing screen (accessed from Workbench or Task Manager) or through a script (created manually or in the Batch Processing screen).

Overview of Batch Loader Files 

The batch files processed by Batch Loader are of two types: 

Standard—Text files that can contain only one month and that are usually loaded through the Import screen 

Multiload—Text or Excel files that can contain multiple periods and locations 

Name Format for Batch Files 

The names of standard batch files consist of the following segments in the following order: 

1. File ID—A free-form field that can be used to control load order (Batch files load in alphabetic order by file name. Thus, for example, a file named a_Texas_Actual04_Jan-2004_RR.txt loads before a file named b_Texas_Actual04_Jan-2004_RR.txt.) 

2. Location 

3. Category

4. Period 

5. Load Method—A two-character item (Character 1 = FDM append or replace, and character 2 = target append or replace. Valid values are A and R. 

Because Multiload files contain metadata, they do not require a specific file name format. 

Running Batch Loader  

To initiate the batch load process:  

1 Create the batch files, and place them in the appropriate FDM directory.  

2 Perform an action: 

From Workbench, select Tools > Batch Processing. 

From Task Manager, select Start > Programs > Oracle EPM System> Financial Data Quality Management > Task Manager > Task Manager. The Batch Processing screen is displayed. 

3 Set the batch controls. 

4 Perform an action: 

To run the batch with the selected controls, click Execute. 

The Batch Monitor section lists the files that Batch Loader is processing and updates with the results for each file.  

To create a script with the selected controls, click Create Script. You are prompted for a script name. You can add the script name to a scheduled task and, thus, set the script to run automatically.

Batch Processing Screen Results 

As a batch is processed, the Batch Monitor field of the Batch Processing screen provides a graphical display of the batch results. Each completed load displays a symbol that indicates which processes failed and which processes passed: 

Auto Corrected—Failed steps are automatically corrected. 
Successful—All steps completed successfully. 
Failure—One of more steps failed. 
Invalid POV—Process is being loaded to an invalid period, category, or location

Scripting for Batch Loader 

You can run Batch Loader from within Workbench or from within a script environment— manually or through Task Manager. You can create scripts manually—by copying the following scripts—or by using the Batch Processing screen.

Script for Standard Batch Loads 

Sub BatchLoad() 
‘-------------------------------------------------------------------------- --- 
‘ FDM Custom Script: ‘ 
‘Created By: ADMIN 
‘Date Created: 3/24/2006 09:00 ‘ 

‘Purpose: Execute a STANDARD Serial Processing FDM Batch 
‘-------------------------------------------------------------------------- --- 

‘Declare Local Variables 
Dim lngProcessLevel 
Dim strDelimiter 
Dim blnAutoMapCorrect 
‘Initialize Variables 
lngProcessLevel = 12 ‘Up-To-Check 
strDelimiter = “_” 
blnAutoMapCorrect = 0 
‘Create the file collection Set BATCHENG.PcolFiles = BATCHENG.fFileCollectionCreate(CStr(strDelimiter)) ‘Execute a Standard Serial batch 
BATCHENG.mFileCollectionProcess BATCHENG.PcolFiles, CLng(lngProcessLevel), , CBool(blnAutoMapCorrect) 
End Sub 


After a script is created, you can create a FDM Task Manager event to run Batch Loader on a scheduled basis.

Script for Parallel Batch Loads 

Because FDM supports parallel processing of batch files, multiple files (up to 50) can run simultaneously. FDM groups files into processes. The files within each process run sequentially (requiring that one file complete its run before the next file starts its run), and the processes run simultaneously.

Sub ParallelBatch()
‘------------------------------------------------------------------
‘ FDM Custom Script: 
‘ 
‘Created By: Admin 
‘Date Created: 3/23/2006 13:50

‘Purpose: Execute a FDM Batch Loader with parallel processing
‘------------------------------------------------------------------ 
‘Declare Local Variables 
Dim lngProcessLevel
Dim strDelimiter 
Dim blnAutoMapCorrect
Dim lngParallelProcessCount
Dim strLoadBalanceServerName
‘Initialize Variables
lngProcessLevel = 12 ‘Up-To-Check 
strDelimiter = “_”
blnAutoMapCorrect = 0 
lngParallelProcessCount = 5 
strLoadBalanceServerName = “LocalHost” 
‘Create the file collection 
Set BATCHENG.PcolFiles = BATCHENG.fFileCollectionCreate(CStr(strDelimiter)) 
‘Execute a Standard Parallel batch 
BATCHENG.mFileCollectionProcessParallel BATCHENG.PcolFiles, CLng(lngProcessLevel), CLng(lngParallelProcessCount), 
CStr(strLoadBalanceServerName), , CBool(blnAutoMapCorrect) 
End Sub