ORACLE FINANCIAL CLOUD SOURCE
SYSTEM TYPE NAME CHANGED TO ORACLE ERP CLOUD
In
Data Management on the Source System page, the name of the source system type
“Oracle Financials Cloud” has been changed to “Oracle ERP Cloud.” All
pre-existing “Oracle Financials Cloud” source system type names now show with
the “Oracle ERP Cloud” source system type name. This is a name change
only and you do not need to take any action.
For
your reference, the Oracle ERP Cloud source systems include:
- Oracle
General Ledger
- Fusion
Budgetary Control
- All
ERP Cloud Adapters
The
file source system type name remains “File.” The Oracle Human Capital
Management Cloud source system type name remains “Oracle HCM Cloud.” The
NetSuite source system type name remains “NetSuite.”
NEW SYSTEM SETTING FOR MIGRATION
OF DATA LOAD MAPPINGS IN DATA MANAGEMENT
A
new Map LCM Format profile option in Data Management System Settings enables
you to export individual data load mappings by location or combine mappings by
all locations for Migration (lifecycle management activities).
If
you select “Individual Data Load Mapping by Location,” maps are exported
individually for each location and imported individually for each location. If
you have a large number of maps for each location, use this method since
it allows loading of maps in smaller sets by location. This method is also
useful to migrate maps for certain locations selectively. With this
method, existing maps are deleted and replaced by new maps in the snapshot.
If
you select “Combine Data Load Mapping for All Locations,” maps are exported in
a single artifact for all locations. With this method, maps from the snapshot
are merged to the existing maps in the target system. This is the default
setting.
The
new Map LCM Format setting is available on the Data Management System Settings
page as shown below:
REPLACE MODE
FOR ALL DATA TYPE WITH SECURITY LOAD METHOD NOW SUPPORTED
When
loading data to Planning or Essbase target applications using the All Data Type
with Security load method, the Replace mode is now supported for administrator
users only.
In Replace mode, the system first clears any existing
data in the application for those referenced in the dataload file. Then the
system performs the data load in Merge mode.
LCM
MIGRATION OF DATA LOAD MAPPINGS IN DATA MANAGEMENT
In
order to improve the performance of export and importing large data load
mappings, Data Management now exports the mapping by individual locations.
When
importing the mappings to the target environment, the existing mappings are
completely replaced with mappings from the source environment. Prior to this
update, data load mappings from the source were merged into the target
environment.
EPM
INTEGRATION AGENT WRITE-BACK
The
EPM Integration Agent, which provides connectivity between EPM Cloud and
on-premises sources, now provides write-back functionality where data from EPM Cloud
can be loaded back to the on-premises database.
To
support this feature, a new data export application allows you to export data
to the on-premises database. There are two modes in which you can load data to
the target table. To use the simple mode, you register the application and
specify the table name and include all the columns from the table in the
application. The system generates the INSERT statements automatically and loads
the data. To use the advanced mode, you provide an INSERT statement with
the appropriate source value and any SQL expressions in an INSERT query.
In
addition, the agent can execute two event scripts during the write-back
execution: BefExport and AftExport. Using
a BefExport event, you can perform any action before
inserting data to the table or you can override the default insert
processing. Using an AftExport event, you can do any post
processing cleanup after inserting data to the table.
The
write-back feature is supported for agents running in both SYNC and ASYNC
modes.
STEPS
TO ENABLE
Download
the EPMAgent.zip from
the Download Agent option on the Actions menu in Data Integration. Unzip
the EPMAgent.zip and overwrite your
existing agent folder. There is no further action. You don’t need to update the
ini file or certificate.
NEW CLEAR
REGION OPTION IN DATA INTEGRATION
A
new Clear Region option in Data Integration lets you select the slice of data
to be cleared before loading data in Replace mode to a Planning module
application. In addition, when loading budgets to the Oracle General
Ledger, you can optionally clear prior budgets before loading a new
budget. This feature can only be used with Oracle Financials Cloud 20C or
higher.
You
define the clear region by specifying member selection criteria for
dimensions such as a static list of members, member function selections, and
members derived from the data. By default, the system defines a default clear
script based on Entity, Scenario, Version, Year, and Period values included in the
data load.
- For
Planning, the Period, Year, and Scenario dimensions are derived
automatically based on the data and you do not have to specify any filters
for these dimensions.
- For
Fusion, the Ledger, Scenario, and Accounting Period dimensions are derived
automatically based on the data and you do not have to specify any filters
for these dimensions.
The
Clear Region option is available on the Options page in Data Integration.
Clear Region Tab
The
Clear Region option is only available for the Planning module and Oracle Fusion
General Ledger (Fusion update 20C or higher required) target applications.
