Before you Begin
This 25-minute hands-on tutorial shows you how to manually export dimension metadata from Enterprise Data Management Cloud to a connected Planning environment, and then import the metadata into Planning. The sections build on each other and should be completed sequentially.
Background
Enterprise Data Management Cloud provides solutions for managing changes in your business by ensuring consistency across enterprise data, even across disparate applications.
Enterprise Data Management Cloud offers three ways to manage the integration of your dimension metadata with Planning:
- Manual: You can manually export dimension metadata from Enterprise Data Management Cloud to a flat file that is stored either locally or exported directly to a Planning instance. Then in Planning, you can run an import job to import the metadata.
- EPM Automate: You can download the EPM Automate client and issue commands to export dimension metadata from Enterprise Data Management Cloud, copy it to Planning, and then import it to Planning using a saved import job. This can be done with interactive commands or in a batch script.
- Groovy rules: You can create a Groovy business rule in Planning that calls the Enterprise Data Management REST API to export the dimension metadata, then imports the metadata to Planning using a saved import job.
In this tutorial, you update the Product dimension in Enterprise Data Management Cloud and then synchronize the changes to Planning by manually exporting the dimension and then importing it to Planning.
Note:
See the Next Steps section for links to tutorials on using EPM Automate and Groovy rules.What do you need?
An EPM Cloud Service instance allows you to deploy and use one of the supported business processes. To deploy another business process, you must request another EPM Enterprise Cloud Service instance or remove the current business process.
- Have Service Administrator access to two instances of EPM Enterprise Cloud Service. The instances should not have business processes created.
- Configure one of your instances for Enterprise Data Management Cloud and configure the other instance for Planning.
- Upload and import this snapshot into your Enterprise Data Management Cloud instance.
- Upload and import this snapshot into your Planning instance.
Note:
If you have already set up these instances for one of the tutorials listed in the Next Steps section, you can continue to use the same environments. Your results may vary from those shown in the screenshots for this tutorial, depending on whether and in which order you have completed the related tutorials.Note:
For more information on uploading and importing migration snapshots, refer to the Administering Migration for Oracle Enterprise Performance Management Cloud documentation.Setting up the Planning application connection in Enterprise Data Managment Cloud
In this section, in Enterprise Data Management Cloud, you set up and test a connection to your Planning instance so you can export dimension metadata directly to the Planning instance inbox.
You can also export dimension metadata to a file on your local drive.
- On the Enterprise Data Management Cloud home page, click Applications.
- Click Corporate Planning to open the inspector.
- Select the Connection tab.
- Select the Production connection, then click Edit.
- Modify the connection details for your Planning instance:
Field Valid Values Example Instance Location Enter a connection URL to your Planning instance in the format: https://ServiceName-IdentityDomain-ServiceType.DataCenter.oraclecloud.com
https://planbudget-uscompany-entplan.US11.oraclecloud.com
where
ServiceName
isplanbudget
IdentityDomain
isuscompany
ServiceType
isentplan
DataCenter
isUS11
Identity Domain Enter the identity domain of your Planning instance. Note: This is the same Identity Domain used in the Instance Location.
uscompany
Username Enter an authorized user name. Note: The user must be a Service Administrator of the Planning instance.
tom.smith
Note: You must enter the identity domain in either the Identity Domain or Username fields. For example, enter
uscompany
in Identity Domain oruscompany.tom.smith
in Username.Password Enter the user's password. xxxxxxxx - Select Primary Connection to make this connection the default for importing and exporting.
- Click Test Connection.
The message "Connection Successful" is displayed.
If your connection test is not successful, check your connection information and try again.
- Click OK, then click Save.
- Click Close to close the inspector.
Adding a product in Enterprise Data Management Cloud
Currently, the Product dimensions in Enterprise Data Management Cloud and Planning are in sync. In this section, you add a new product to the Corporate Planning application in Enterprise Data Management Cloud.
- On the Enterprise Data Management Cloud home page, click Views.
- Click Corporate Planning to open the view.
- Select the Product viewpoint.
- In the Product hierarchy, expand Total Product, then All Product, and then SmartPhones.
- Click New Request to start a request to add a product.
- In the SmartPhones row, click the Actions icon and select Add Child.
- Enter property values for the new product (for any properties not listed in the table, use the default value):
Property Value Name Smart Phone 7 in Description Smart Phone 7 in Hierarchy type Stored - Click Submit to commit the changes.
You receive a message that the request was successfully submitted.
Submitting the request validates your changes. If there are no validation issues and there is no approval workflow defined, the changes are immediately commited to the dimension.
- Click Close to close the view, then return to the home page.
Exporting dimension metadata from Enterprise Data Management Cloud to a Planning connection
In this section, you manually export the Product dimension metadata to the inbox of your Planning application, using the connection that you set up earlier.
- On the Enterprise Data Management Cloud home page, select Applications.
- In the Corporate Planning application row, click the Actions icon, and select Export.
- Select the Product dimension.
- Configure the export:
- Export Target: Connection
- Connection: Production
- Export file name: Product.csv
- Click Export.
You get a message that the export completed successfully.
- Click Close.
Viewing the exported file
In this section, you open the Planning Inbox/Outbox Explorer to verify that the Product.csv file was exported from Enterprise Data Management Cloud directly to your Planning instance.
- Open a new browser tab and log in to your Planning instance. From the home page, select Application, and then select Overview.
- Click Actions, then select Inbox/Outbox Explorer.
- Notice that the Product.csv file has been exported from Enterprise Data Management Cloud to Planning.
- Click Close to return to the Application Overview page.
Creating an import job
To load files stored in the Planning Inbox/Outbox, you must create a saved import job. In this section, you create an import job for the Product.csv file.
- Select the Dimensions tab.
- Click Import to display the Import Metadata dialog box.
- Click Create.
- For Location, select Inbox.
- In the Product dimension row, enter Product.csv, and accept the default (Comma delimited) for the File Type.
- Click Save as Job.
- Configure the job:
- Name: Import_Product
- Error File: edmc_product_error
This file provides information about the metadata records that were not imported for each dimension. If you specify an error zip file, a separate error file is created for each dimension, then the error files are zipped together, and the zip file is stored in the Outbox where you can download the file using Inbox/Outbox Explorer.
- Refresh Database if Import Metadata is successful: Selected
You must refresh the database after modifying dimensions and members. In a production environment, Oracle recommends that you notify all users, asking them to save their work and close the application, before you refresh the database. For more information on database refreshes, please see Before Refreshing the Database in Administering Planning.
- Click Save, then click OK to close the information message.
- Click Close to close the first Import Metadata dialog box.
- In the second Import Metadata dialog box, click Refresh to view the list of saved import metadata jobs.
The job you created is displayed in the list.
Running the import job and viewing results
In this section, you run the saved import job and verify that the new product is added to Planning.
- In the row for the import job, click the Actions icon and select Submit.
A message that the job was submitted is displayed.
- Click OK to close the message, then click Close to close the Import Metadata dialog box.
- Click the Jobs card (located at the top of the page) to verify that the job completed successfully.
- Notice that the top two jobs listed in Recent Activity are the metadata import and the subsequent database refresh. The jobs completed successfully.
- Click the Overview card to return to the application overview, then select the Dimensions tab again.
- In the Cube drop-down, select OEP_FS.
- Click Product to view the Product dimension.
- Expand Total Product, then All Product, and then SmartPhones.
The new product, Smart Phone 7 in, was added to the dimension.
Next Steps
Integrating Dimension Metadata from Enterprise Data Management Cloud with Planning using Manual Export and Import
F41735-01
April 2021
Copyright © 2021, Oracle and/or its affiliates.
This 25-minute hands-on tutorial shows you how to manually export dimension metadata from Enterprise Data Management Cloud to a connected Planning environment, and then import the metadata into Planning.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.