Oracle released the cool feature of "CROSS APPLICATION SUPPORT FOR SMART PUSH IN DATA MAPS" in April 2022.
Cross Application Smart Push feature enables customers with multiple applications to instantly move data, cell comments and supporting detail from a cube in a source application to a reporting or other cube in a remote target application
Applies to: Planning, Planning Modules (both as source and target), FreeForm (both as source and target), Financial Consolidation and Close (target only), Tax Reporting (target only).
Create a connection:
Create a Cross-Application Data Map
The Cross Application Smart Push feature enables customers with multiple environments to
instantly transfer data, cell comments, and supporting detail from a Planning cube in a source
environment to a reporting or other Planning cube in a remote environment while working in
forms.
To transfer data, cell comments, and support from a source cube to a remote
reporting cube:
Click Application, then Data Exchange, and then click Data Maps.
Click Create.
5. Under Source, select a cube from the available cubes for the current application.
6. Under Target and from the Cube drop-down, choose Select Remote Cube.
From the Select Remote Cube page, select the connection and cube for the
target application and then click OK.
Under Connection, select the connection to use to connect to the target cube.
Under Cube, select the cube from the remote application.
All the available connections in the source application are displayed. The
cubes from the remote application are displayed based on the selected
connection.
Click OK.
Map any source members with their corresponding target members when member
names differ in the source and target applications.
On the Detail page, click Save and Close.
Note: You cannot execute the Data Map, it has to be via Smart Push
Open a form and add the Smart Push to the form.
You can call the Smart Push via the Calculation Manager Business rule using Groovy Script so you can call it as needed,
A Known issue:
We have identified an issue with the data map creation when the
combined length of the user name and password of the user used in the
connection definition is greater than 55 characters. Oracle acknowledged and said they will be
addressing the issue soon.
Workaround:
As an alternate solution, you can try creating the data map by using a new connection where the
combined length of the user name and password is less than 55
characters.
Hope this was useful, cheers!!!
No comments:
Post a Comment