Let's see how to load numeric & non-numeric data directly into Planning applications in PBC/EPC instance via the Simplified Interface without using the Data Management.
Method: Using the Source Type Planning
If an import error occurs during a Planning data load, the import will continue to load valid data (partial load). Any errors will be noted in the import and export status.
All we need is the data to be loaded in a specified format to get loaded. The format should be like the following file, (CSV Format)
In this case, we are loading the data to the Account members for Jan to Jun period for the specified POV and for the Database Plan1
You can export the data from the Planning application via the Simplified Interface to get this format.
To export, the data click on Navigator
Access the Export Data under Actions
You can click on create
Specify the Row, columns and the POV for which you need to export the data and hit the Export option.
Note: You can also create this as a job by Specify the location as Outbox (in the Pod) so you can run the job by EpmAutomate via the batch file.
This will create a data export file in a Zip format.
Once we have the data export we can use the same file for importing the data (numeric as well as non-numeric data).
I have created the following members under Account Dimension for loading the non-numeric values
- Alloc-Perct% -For loading the Percentage
- EnteredBy-Text -For loading the Text
- IsLatest-SL -For loading the Smartlist
- Start-Date -For loading date
Along with 2 members as of example to load the numeric value.
My data load import file will look as below,
Let me load the file via the simplified interface - Import Data
And hit Create
Select the locally saved file from your machine for import and hit import
Note: I have removed the selection on Include Metadata, for now, will explain the functionality later in this post.
The Job is submitted and the status is shown below,
The result of the load is shown under Jobs,
The result of the load is shown under Jobs,click on the latest job
The Status is shown as below,
Let me run a Smartview Adhoc for the loaded POV to check if the data is actually loaded,
I could see all the numeric & non-numeric data loaded for the specific POV.
With Option "Include Metadata"
Now let's load the data using the same above method with the option "Include Metadata"
From the documentation:
Clear Include Metadata to improve data import performance and to prevent members from changing position in the outline during data import. If you opt to exclude metadata, the required metadata must already exist in the application before you can load the application data.
Load file with 2 members currently not present in the application present in the load file
Now let's load the data using the same above method with the option "Include Metadata"
From the documentation:
Clear Include Metadata to improve data import performance and to prevent members from changing position in the outline during data import. If you opt to exclude metadata, the required metadata must already exist in the application before you can load the application data.
Load file with 2 members currently not present in the application present in the load file
AddMember0 |
AddMember1 |
During the import data, the job failed,
But the members were added to the application,
I did add one more new member and imported the data,
It failed again for the member AddMember2, and it loads the data successfully if you run the data import again.
So it looks for the member at the first attempt and adds the member and fails the load. And if you run the import again it adds the data since it was added in the previous load.
And the property of the newly added member is as shown below,
As the document says its wise add the member before loading the data as adding both is not so smooth. Hope this was useful to load the data directly into Planning application.
Method: Using the Source Type Essbase
Make sure the load file is in Essbase accepted format as shown below and save it as .txt
In Simplified Interface select "Essbase" as Source Type and select the Cube you need to laod the data.
You can check the status of the load under jobs
And validate the data load via the Smartview
Hope this was useful for loading the data directly into Planning application without the Data Managment.
But the members were added to the application,
I did add one more new member and imported the data,
It failed again for the member AddMember2, and it loads the data successfully if you run the data import again.
So it looks for the member at the first attempt and adds the member and fails the load. And if you run the import again it adds the data since it was added in the previous load.
And the property of the newly added member is as shown below,
As the document says its wise add the member before loading the data as adding both is not so smooth. Hope this was useful to load the data directly into Planning application.
Method: Using the Source Type Essbase
If any import errors occur during an Essbase data load, the import will quit and no data will be loaded.
Let's see how to load the data using the "Source Type Essbase".Make sure the load file is in Essbase accepted format as shown below and save it as .txt
In Simplified Interface select "Essbase" as Source Type and select the Cube you need to laod the data.
You can check the status of the load under jobs
And validate the data load via the Smartview
Hope this was useful for loading the data directly into Planning application without the Data Managment.
Thanks Dayalan for your efforts to explain Data Load from Workspace in details. I wanted to add one thing here, The only main reason to use Data Management to load the data is that we have wow functionality of Dimension mappings normal as well as Cross Dim's Mappings, which Workspace Data Load can't provide us.
ReplyDelete