Oracle Financial Services Analytical Applications (OFSAA) enables financial institutions to measure and meet risk-adjusted performance objectives, cultivate a risk management culture, lower the costs of compliance and regulation, and improve customer insight.
Topics:
· OFSAA-EDMCS Application Dimensions
· Mapping the OFSAA User to EDMCS User Groups
· Accessing the EDMCS-OFSAA Interface
· Prerequisites for Deploying OFSAA-EDMCS Connectors
· Deploying or Undeploying OFSAA-EDMCS InterfaceConnectors
· OFSAA-EDMCS Interface Modifications or Upgrade
· Executing OFSAA-EDMCS Connectors
· EDMCS Dimension Type Information
EDMCS has a different way in the creation of dimensions and respective hierarchies as compared to DRM.
In EDMCS, you can create the dimensions structure through application and node creations. Once the structures are created, data can be imported for the created dimensional attributes through a CSV file format. Once the data is successfully uploaded, hierarchy is automatically created within the EDMCS application. EDMCS exposes Rest services which are used in DIH DRM Interface to download CSV files to EDS location.
The mapping between the delimited extracted files (EDD) and OFSAA staging tables (ADI) is predefined in the EDM connectors. The interfaces are then executed to load the data from the delimited into the target staging tables.
Figure 22: EDMCS - OFSAA Data Flow
The following files provide a reference list of attributes that OFSAA supports for the dimensions involved. Ensure that the attributes extracted from your EDMCS instance or tenancy are in the order that they appear in the files:
· Product
Note that while OFSAA supports the list of attributes in the files above for dimensions, your instance of EDMCS or its sources for dimension information may not mark them mandatory. Values for the following attributes are automated by the integration application:
· NODE ID – This is a unique ID auto-generated by the application.
· SORT ORDER – This is assigned based on the alphabetical order of sibling members or nodes at each level
· LEAF NODE INDICATOR FLAG – This is assigned based on identifying nodes that do not have any child nodes.
User group mapping enables you to map users to a specific user group which in turn is mapped to a specific Information Domain and role. Every user group mapped to the infodom must be authorized.
See Mapping the OFSAA User to DRM User Groups section under DRM OFSS Integration for more information.
Access the DRM-OFSAA Interface using the login credentials (User ID and Password). The built-in security system ensures that you are permitted to access the window and actions based on authorization only.
See Accessing the DRM-OFSAA Interface section under DRM OFSS Integration for more information.
The deployment process requires some actions to be performed as prerequisites. Ensure that these requirements are met before starting the deployment:
See Prerequisites for Deploying OFSAA-DRM Connectors section under DRM OFSS Integration for more information.
To deploy or undeploy OFSAA-EDMCS Connectors using the Refresh DRM Interface window, follow these steps.
1. From the Interface for Oracle Data Relationship Management window, select DRM Administration and then select Refresh DRM Interface. The Source Information window is displayed.
Figure 23: Oracle Data Relationship Management – Source Information
2. Select the Source Application Version (Enterprise Data Management Cloud Service) from the drop-down list.
3. Enter the following details.
4. EDMCS URL
5. User ID
6. Password.
Figure 24: Oracle Data Relationship Management – Source Information
7. Click Next. The list of dimensions registered in EDMCS to OFSA application and the dimension combination is displayed in the EDMCS Application Dimension drop-down list.
8. For the listed OFSAA Dimension list, select the required EMCS Application Dimension from the drop-down list, and click Next. This information is saved and used to configure data movement routines.
Figure 25: Oracle Data Relationship Management – Source Information
9. Under the Review, click Save and Deploy. A confirmation message is displayed: “Deployment Successful”.
NOTE:
It is possible to edit the EDMCS Application Dimensions and click Save at any given time.
10. To undeploy the connector, click Undeploy All. A message is displayed: “Are you sure you want to Undeploy the Selected Version?”
11. Click Yes to proceed.
12. To check deployed EDDs and Mappings, select DRM Data Mapping from the Interface for Oracle Data Relationship Management window, and then select External Data Descriptor. These are EDDs defined as standard, reflecting the data expected from EDMCS.
Figure 26: External Data Descriptor Summary Window
13. To check deployed Connectors and Mappings, select DRM Data Mapping from the Interface for Oracle Data Relationship Management window, and then select Connectors. These are the Connectors that perform data movement into Staging entities.
Figure 27: Connectors Summary Window
The following are the DRM EDD and Connectors deployed in this version and corresponding Source File Names.
Table 5: Deployed EDMCS DRM EDD and Connectors List
11EDD |
Connectors |
Dimension |
|---|---|---|
EDM Organization Unit |
EDM Org Attributes Connector |
Organization Unit Code |
EDM Organization Unit |
EDM Org B Tl Hier Connector |
Organization Unit Code |
EDM Products |
EDM Prod Attributes Connector |
Product |
EDM Products |
EDM Prod B Tl Hier Connector |
Product |
EDM Chart of Accounts |
EDM COA Attributes Connector |
Chart of Accounts |
EDM Chart of Accounts |
EDM COA B Tl Hier Connector |
Chart of Accounts |
EDM General Ledger |
EDM GL Attributes Connector |
General Ledger |
EDM General Ledger |
EDM GL B Tl Hier Connector |
General Ledger |
14. Predefined batch <INFODOM>_DRM_CONNECTORS is created to execute the set of connectors in this version.
You can use the Undeploy button to undeploy the connectors. Use the undeploy feature in the following scenarios.
If there is an upgraded source application available, ensure to select undelopy all to undeploy the existing version of the connector, and then select the upgraded source version to deploy. The current available source version for DRM connector supports:
· Data Relationship Management - 11.1.2.3/11.1.2.4
· Enterprise Data Management Cloud Service
After the predefined OFSAA EDMCS connectors are deployed, they must be executed.
To execute OFSAA-EDMCS Connectors, see Publishing and Executing OFSAA-DRM Connectors to ODI environment through DIH.
See the Chart of Accounts (COA) file for the DRM Column Name and the Target Logical Name.
See General Ledger (GL) file for the DRM Column Name and the Target Logical Name.
See the Organizational Unit file for the DRM Column Name and the Target Logical Name.
See the Product file for the DRM Column name and the Target Logical Name.