top of page
Search

Push to ASO cube via Data Exchange with Clear Regions enabled - 'Cannot Clear Partial Data' error resolved.

  • Writer: Sarah Ansell
    Sarah Ansell
  • 1 day ago
  • 3 min read

There are many ways to synchronise data between cubes in EPM Planning. I was recently working with a data integration that had been setup in an Oracle EPM Planning application via Data Exchange - where Data Load Mappings were being utilised.


We added clear regions to this integration to simplify the process for the client to run the push nightly via a pipeline, and on demand. After adding the clear region, we were receiving an error message and it wasn't initially obvious how to resolve it.


Error in log received upon Export step: 

"2026-05-06 13:25:01,391 ERROR [AIF]: Cannot Clear Partial Data. Essbase Error(1260046): Unknown Member [Period].[Mar] used in query"

A few lines above this in the log, it shows the CrossJoin replace data script which is used to clear the data for ASO; since a standard Essbase calculation cannot be used in an ASO cube:

2026-05-06 13:25:01,364 INFO  [AIF]: Replace data script: 
CROSSJOIN({Descendants([Account].[TOT_ACC],[Account].Levels(0))},CROSSJOIN({Descendants([Entity].[OEP_Total Entity].[UKRI],[Entity].Levels(0))},CROSSJOIN({[Period].[Mar]},CROSSJOIN({[Scenario].[OEP_Plan]},CROSSJOIN({[Version].[OEP_Working]},{[Years].[FY26]})))))

You can see here it is using [Period].[Mar] in the Crossjoin script too.


Clear Region Definition


The clear region in this case is nice and simple:


Export Mode


When running the integration I use Import mode: Replace and Export Mode: Replace since the clear region is only run when Export Mode: 'Replace' is used.



The integration was failing on the Export data to Essbase Application step.


Resolution: Updating Period Mappings to Uniquely Qualified Names


Users cannot add the Period dimension to a Clear Region definition, since it is derived from the periods selected at run time - this cannot be overridden.


Therefore, the CrossJoin picks up the name of the period [Period].[Mar] from the period mappings.


The mappings were as per the defaults:



I couldn't see anything wrong with this! However, by adding the Qualified Member Name for each period key in the Target Period - Month column I was able to resolve this issue.


I updated this only within the Application Mapping tab for my target application - the ASO cube being pushed to.


Uniquely Qualified Name example:

[Period].[YearTotal].[Mar]        (instead of Mar)

Updated period mapping:



Only the Target Period - Month column needed to be updated:




Successful Replace Data Script in Log


After updating the 'Target Period - Month' period mappings in the ASO application to be uniquely qualified and running the integration again, the integration was successful.


Here I can see in the log that the crossjoin had been updated and there was no error after this:

2026-05-06 13:38:54,548 INFO  [AIF]: Replace data script: 
CROSSJOIN({Descendants([Account].[TOT_ACC],[Account].Levels(0))},CROSSJOIN({Descendants([Entity].[OEP_Total Entity].[UKRI],[Entity].Levels(0))},CROSSJOIN({[Period].[YearTotal].[Q4].[Mar]},CROSSJOIN({[Scenario].[OEP_Plan]},CROSSJOIN({[Version].[OEP_Working]},{[Years].[FY26]})))))
2026-05-06 13:38:54,548 INFO  [AIF]: EssbaseRuleFile.getReplaceDataScript - END

Updating Period Mappings in Bulk


If you're unsure on the steps - it's nice and simple to update the period mappings in one go via Export to / Import from Excel.


  • In Data Exchange navigate to Actions - Setup - Period Mappings.



  • Find the Application Mapping tab and select the correct ASO target application from the drop down list.

  • Click Actions and see the Import from Excel and Export to Excel buttons.

  • The Excel file can be updated with the new uniquely qualified period names in bulk, re-imported, and then saved.


Summary


The client were previously advised that Clear Regions couldn't be used with an ASO cube, so they were pleased to have this up and running successfully. Now the integration can be run on demand and will clear the slice before pushing new data - with no need for any additional steps.


Luckily, it is quite easy to update the period mappings so the maintenance cost is low.


Comment if you've faced a similar issue with Clear Regions & ASO cubes.


Comments

bottom of page