Synchronizing Cloud EDM Dimensions and Mappings with Cloud EPM Applications

This sample scenario explores synchronizing a dimension between an Oracle Fusion Cloud Enterprise Data Management application and an Oracle Fusion Cloud Enterprise Performance Management application.

You use the scripts in this section to complete these tasks:

• Export a dimension from an Cloud EDM application
• Export mappings from an Cloud EDM application dimension
• Copy the export files to a Cloud EPM environment
• Import dimension metadata and mappings into the Cloud EPM application

To synchronize a dimension and mappings between an Cloud EDM application and a Cloud EPM application:

1. Create a script file by copying the following script:

   rem Integration example to sync application dimensions between Cloud EDM and Cloud EPM
   rem Windows script for demonstration purposes only; do not use in production environments
   
   set EDMUSER=userid
   set EDMSVR=https://hostname
   set EDMPWDFILE=example_EDM
   set EDMAPP=appname
   set EDMDIM=dimname
   set EDMLOC=location
   
   set EPMUSER=userid
   set EPMSVR=https://hostname
   set EPMIMPJOB=importjobname
   set PWDFILE=C:\Oracle\EPM.epw
   set DIMFILE=dimension.csv
   set MAPFILE=mapping.csv
   
   rem Synchronizing EDM ---> EPM
   rem Export Dimension and Mappings from EDM
   
   call epmautomate login %EDMUSER% %EDMPWDFILE% %EDMSVR%
   call epmautomate exportdimension %EDMAPP% %EDMDIM% %DIMFILE%
   call epmautomate exportdimensionmapping %EDMAPP% %EDMDIM% %EDMLOC% %MAPFILE%
   call epmautomate logout
   
   rem Log into the Cloud EPM environment
   call epmautomate login %EPMUSER% %PWDFILE% %EPMSVR%
   
   rem Copy exported files from EDM environment to EPM and import metadata and mappings
   call epmautomate copyfilefrominstance %DIMFILE% %EDMUSER% %EDMPWDFILE% %EDMSVR% inbox/%DIMFILE%
   call epmautomate importmetadata %EPMIMPJOB%
   
   call epmautomate copyfilefrominstance %MAPFILE% %EDMUSER% %EDMPWDFILE% %EDMSVR% inbox/%MAPFILE%
   call epmautomate importmapping %EDMDIM% %MAPFILE% REPLACE FALSE %EDMLOC%
   
   call epmautomate logout

2. Modify the script file and set the required parameter values. See Parameters for Script Execution for explanation and example of the parameters.
3. Run the script manually or schedule it to run as needed. See Automating Script Execution.

Parameters for Script Execution

The script files in this section requires you to specify some of the parameter values explained in the following table. Not all these parameters are used in all the scripts.

Table 3-28 Parameter Values for Script Files

Parameter	Description
EDMUSER	User login ID of an Cloud EDM Service Administrator. Example: EDMUSER=[e-mail]
EDMSVR	URL of the Cloud EDM environment. Example: EDMSVR=https:// example.oraclecloud.com
EDMPWDFILE	Name and location of the encrypted password file (EPW) of the Cloud EDM Service Administrator. Example: EDMPWDFILE=edm_jdoe.epw
EDMAPP	Name of an Cloud EDM application dimension. Example: EDMAPP=USOperations
EDMDIM	Name of the dimension to export or import. Example: EDMDIM=entity
EDMLOC	Name of the location to export. Example: EDMLOC=Loc1
EPMUSER	Login name of a Cloud EPM Service Administrator. Example: EPMUSER=[e-mail]
EPMSVR	URL of the Cloud EPM environment. Example: EPMSVR=https://example.oraclecloud.com
EPMIMPJOB	Name of an existing import job of type import metadata in the Cloud EPM environment. Example: EPMIMPJOB=imp_DIMMetadata
EPMEXPJOB	Name of an existing job of type export metadata in theCloud EPM environment. Example:EPMEXPJOB=Exp_DIMMetadata
PWDFILE	Name and location of the encrypted password file (EPW) for Cloud EPM Service Administrator. See the encrypt command. Example: PWDFILE=pwd_jdoe.epw
DIMFILE	Name of the file to hold exported dimension data. Example: DIMFILE=entity_file.CSV
MAPFILE	Name of the file to hold exported mapping data. Example: MAPFILE=map_file.CSV