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.

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.

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.

2. 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.

3. 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.
4. 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.

5. 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.
6. 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.

EPM Cloud Data management / FDMEE / Troubleshooting steps

 

Required Roles for Loading Data

If you have an issue with loading data to Oracle Enterprise Performance Management Cloud using Data Integration, Data Management, EPM Automate or REST APIs, make sure that the user loading the data has one of the following roles:

• Service Administrator predefined role
• Power User predefined role and Run Integration application role

How to trace issues  using ERROR log

• The process details log in data management is the key log to trace any issues
• Ensure the Log level is set to 5 under System Settings tab > select Profile type to ALL
• Open the process details log in Notepad / Notepad++
• Find (Ctrl+F) for the key word "error"

How to determine the load status from DATA LOAD  WORKBENCH

In the Workflow tab > Data load workbench > there are four icons (fish icon) > Import , Validate , Export , Check

If the Import fish is grey, then the import step is failed the source system level 

• Ensure the source system connection is setup correctly 
• Ensure the file name is defined correctly in the data load rule 
• Ensure the data is available in the source combination in which it is extracting 
• Ensure the source filters are defined properly 

If the Import fish is Orange and Validate fish is Grey

• Go the Data load workbench > click on Validation errors 
• You will find the details of the missing mapping members 
• Ensure the mappings are defined correctly for those members and re-run the validate step

If the Import fish is Green, Validate fish is Green but the Export fish is Grey

• Ensure the connection is available and the properties of the target system is defined properly for the target system
• In the error log you will find an error code "Error: 3303", "Error: 3335" - it describes that the member is not available in the target 
• In those scenarios we need to manually create the members in the target system if it valid

Known error codes and solution

3303 Member not found in database.

3304 Insufficient access to store data.

3333 Bad data value supplied.

3335 Record rejected because of duplicate member names.

3336 Member/Data unknown.

3337 Record rejected because of dimension conflicts with Header Name

How to Verify that Microsoft Active Directory Federation Service is Working

 

1.  Access the Microsoft Active Directory Federation Service Sign In page: https://adfs.example.com/adfs/ls/IdpInitiatedSignOnPage (replace adfs.example.com with your Microsoft Active Directory Federation Service hostname)

2.  If required, select Sign in to this site and click Sign In.

3.  Enter the Microsoft Active Directory credentials for a user that exists on both Microsoft Active Directory Federation Service and Oracle Identity Cloud Service (in this example, csaladna@example.com) and click Sign In.

4. Confirm that the message You are signed in is displayed.

EPM SSO Configuration - IDP metadata File and Setting Attributes

 

EPM Cloud supports only Service Provider (SP) initiated SSO; it does not support Identity Provider (IdP) initiated SSO.

Reference : https://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/csimg/configuring-oracle-cloud-service-provider.html

 

1. SSO PROTOCOL : Available are HTTP POST, HTTP Artifact - ___________________
2. User Identifier : Available are User ID, User Email Address - _____________________
3. Contained in : _________ (If the User Identifier value is the user ID, then the contained in field must be the SAML attribute and you must specify the name of the SAML attribute for the contained in field such as SamAccountName in the case of Microsoft Active Directory Federation Services. If it is selected as Email Address then the contained in will be Name ID by default)
4. Provider Metadata : Users can export the provider metadata file by default will be sha2.0 we can leverage to get sha256 methodology as well from oracle support, Partner Active Directory admin team has to import that file into MSAD and provide us back the “Federation.xml” file.
5. This Federation file will be imported in oracle my services for further setup and configuration.