Tuesday, August 9, 2022

EPM CLOUD - FCCS / EPBCS / PBCS - NEW SAVE AS OPTION FOR JOBS

The new "Save As" option for jobs enables you to create a duplicate of an existing job, and then update it to avoid starting over making selections each time you create a new job.

"Save As" is supported for the Export Data, Import Data, Export Metadata, Import Metadata, Refresh Database, Clear Cube, and Import Exchange Rates job types.

To duplicate a job, click Application, then Overview, click Actions, and then select one of the following actions:

Export Data

Import Data

Export Metadata

Import Metadata

Refresh Database

Clear Cube

Import Exchange Rates

On the listing page, click the ellipses icon (...) in the Actions column next to the job that you want to duplicate. 

Click Save As, enter a name for the new job, and then click OK. 

After the duplicate job is created, you can then open the job and update it. 

The error file for the duplicate job will automatically use the new job name as a prefix.

 

DISPLAY MEMBER NAMES AND ALIASES IN SEPARATE COLUMNS IN SMART VIEW AD HOC GRIDS

A new Member display option in Oracle Smart View for Office, Member Name and Alias, allows you to display both the member names and their aliases in separate columns on row dimensions in ad hoc grids.

The Member Name and Alias display option allows users to see the member name and the alias side by side during adhoc zoom interactions within the grid. 


In Smart View, place an ad hoc grid on a worksheet. You may have more than one row dimension in the grid.

In the Smart View ribbon, select Options.

In the Member Options tab, Member Name Display, select Member Name and Alias, then click OK.

In either the Smart View ribbon or the provider Ad Hoc ribbon, click Refresh.

For row members, both member names and their corresponding aliases are displayed in the ad hoc grid.


STEPS TO ENABLE

To enable the Member Name and Alias option for Smart View users working with ad hoc grids, the business process application option, Smart View Ad Hoc Behavior, must be set to Standard.

All new and recreated applications are automatically set to Standard.

For existing and migrated applications, to set the application option, Smart View Ad Hoc Behavior, to Standard:


Click Application, and then click Settings.

For the Smart View Ad Hoc Behavior option, select Standard.

Click Save.


NOTE

The Member Name and Alias option is supported with:

Standard-mode applications only

Smart View 22.100 and later

Thursday, August 4, 2022

ORACLE NETSUITE – ORACLE EPM CLOUD Integration

 
NetSuite Adapter
https://docs.oracle.com/middleware/12213/adapter-netsuite/using-netsuite-adapter/GUID-C7EBFF8A-13CF-4F5A-ABAE-5032E9A31386.htm


Oracle NetSuite Adapter Capabilities
https://docs.oracle.com/en/cloud/paas/integration-cloud/netsuite-adapter/oracle-netsuite-adapter-capabilities.html


Integrating Oracle NetSuite
https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/erpia/netsuite_intro_100xbda13a64.html


Using the Oracle NetSuite Adapter with Oracle Integration
https://docs.oracle.com/en/cloud/paas/integration-cloud/netsuite-adapter/preface.html#GUID-7E890AB2-AA82-4D33-82FC-0080971DB08B


Getting Started with the Oracle NetSuite Adapter
https://docs.oracle.com/en/cloud/paas/integration-cloud-service/icsns/getting-started-oracle-netsuite-adapter.html


Using the Oracle NetSuite Adapter with Oracle Integration
https://docs.oracle.com/en/cloud/paas/integration-cloud/netsuite-adapter/using-oracle-netsuite-adapter-oracle-integration.pdf


Youtube

https://www.youtube.com/embed/vX3RGihxXO0?rel=0&autoplay=1

Other Links
https://system.eu2.netsuite.com/pages/customerlogin.jsp
https://brovanture.com/connecting-two-clouds-netsuite-to-oracle-pbcs-cloud-to-cloud-integration/
https://netsuitehub.com/forums/topic/saved-search-for-ytd-sales/

Oracle EPM FCCS - ICP Eliminations - points to remember

In preparing consolidated financial statements, we need to eliminate transactions between companies or entities included in the group for consolidation and only report results arising out of transactions with third parties. This is achieved through intercompany elimination.

To perform Intercompany Elimination in Oracle Financial Consolidation and Close Cloud Service (FCCS) below pre-requsites should be met,

Prerequisites to perform intercompany eliminations in Oracle Financial Consolidation and Close Cloud Service (FCCS)

1. Intercompany feature should be enabled while creating the application.
2. Account must be set as an Intercompany account.
3. The account must have a Plug account assigned to it.
4. Entity must be set as an Intercompany entity.
5. Run a consolidation.
6. Intercompany transactions are eliminated automatically after running consolidation in Oracle Financial Consolidation and Close Cloud Service (FCCS).

How to extract Alias details using EPM Cloud Data management in EPBCS/PBCS/FCCS Applications

Now it is possible to extract a member of a dimension and its Alias information using EPM Cloud Data management in EPBCS/PBCS/FCCS Applications.

Follow the process to use the option > Data Export to File, A target application gets created as Data Target type and complete the setup process,

For extracting the Alias - which is part of metadata use the below SQL command to extract the details 

Like Mapping -- * to #SQL 

(

SELECT DISTINCT ALIAS FROM AIF_TARGET_APPL_MEMBERS WHERE UDX = MEMBER_NAME 

)

--- Note: Replace UDX with the actual UD number from the target application dimension class.

Wednesday, June 22, 2022

Unable to load Dates to EPBCS application using Oracle EPM Cloud Data Management

Issue Description 

There might be a scenario where you are trying to load Dates into EPBCS application and you end up with dates not getting loaded, and for the dates column you get a Blank value.

But in Data load workbench it shows that the data is loaded successfully.

The Import and Export process also shows success.

Root Cause

The Format for the column which holds the Date information is not correct.

Solution

Data management supports loading date in two formats

MM-DD-YYYY     &      DD-MM-YYYY

Based on the date format set in your EPBCS application the date format can be selected

Most preferably MM-DD-YYYY

So while designing the source file which is a CSV file, ensure you select the entire Date column

Right Click > Format Cells > Select Custom > and in the TYPE: section enter MM-DD-YYYY  or DD-MM-YYYY based on what is defined in your application.

Note: 

Ensure the value entered in the Type section should be in CAPS, Data management will not throw an error if you use Lower case, but the Date information wont get loaded to the EPBCS application.

Monday, April 25, 2022

Cloning Applications between environments using Clone Environment option in Oracle EPM Cloud

 Cloning Applications between environments using Clone Environment option in Oracle EPM Cloud  

Click on Navigate > Under Tools section > Click on Clone Environment  


Enter the details of your Target environment where you need to clone this application

Target environment URL, Target environment Username, Target environment Password

Roles Required

You must have either a Service Administrator or a Service Administrator with Identity Domain Administrator predefined role.

For Oracle Cloud Classic to OCI cloning, you must sign in as a Service Administrator, who also has the Identity Domain Administrator predefined role to ensure that users and their roles are cloned to the OCI environment.


For cloning artifacts, you can choose the options as per your requirements



  1. Optional: Select the Users and Predefined Roles check box to clone users and their predefined role assignments.

If you are performing an Oracle Cloud Classic to OCI migration, you must select this check box.

  1. Optional: for environments other than Oracle Enterprise Data Management Cloud and Narrative Reporting only: Deselect the Data Management check box if you do not want to clone Data Management records. Cloning of Data Management records may take a long time if the staging tables contain a very large number of records.

Clone Data Management records only if both the source and target environments are on the same monthly update or the target environment is one update newer than the source environment. For example, you can clone 22.01 Data Management records to another 22.01 environment or to a 22.02 environment only.

  1. Optional: for Planning, Planning Modules, Free Form, Financial Consolidation and Close, and Tax Reporting only: Deselect the Job Console check box if you do not want to clone Job Console records.
  2. Optional: for Planning, Planning Modules, and Free Form only: Deselect the Application Audit check box if you do not want to clone application audit records.

Note: Application audit data of Financial Consolidation and Close, and Tax Reporting is, by default, included in the snapshot.

  1. Optional: Select the Stored Snapshots and Files check box if you want to clone the contents of inbox and outbox, and stored snapshots. This process may take a long time depending on the number and size of stored snapshots and files in inbox and outbox.
  2. Click Clone to initiate the process.

Tasks to Perform After Cloning Environments

1.       Daily Maintenance Start Time

The daily maintenance start time of the target environment is automatically reset to that of the source environment from which the snapshot was cloned, ensure to change the time in the target environment accordingly.

2.       Update EPM Automate Scripts

If you have written any script to perform an activity, ensure the script is updated with the target environment URL with identity domain name updated.

Also, if you are using native accounts then ensure password is updated In the scripts.

3.       Smart View URLs

Modify the public and private connection Smart View URLs so that they point to the cloned environment. Also, update connection URLS as needed.

4.       Integrated Business Process

a.       Single Sign On

If you are moving multiple instances in an integrated business process to a new domain, SSO between instances will not work until all instances are migrated.

If you had setup SSO to authenticate the users and the migration resulted in a change in the identity domain being used, for example, after Oracle Cloud Classic to OCI migration, you must reconfigure SSO.

While cloning between same domains SSO need not be reconfigured, instead update the PROD application in the list.

b.      Updating Integrations and Connections details

There are places where you need to update the connection details, like updating data management target application connections, source system connections, ensure the URL`s, Usernames and password are updated accordingly.


Other posts

How is the data size calculated for a EPM Cloud service instance?

The total size of data used by your EPM Cloud service instance is the sum of the following: Application data stored in Essbase Artifact...