Monthly Archives: August 2013

Oracle EPMA | Error on import

We are doing a fair amount of work with Oracle Enterprise Performance Management Architect (EPMA) application at the moment. We came across the following error message recently. (In the spirit of paying it forward we thought we should share it with you.)

“EPMA Error on import – Member cannot be inserted because the parent member has another child member with the same name.”

It took me some time to understand this one although in the end the cause was quite simple. I hope that this can save you some time…

One of my imports to EPMA was failing and returning the error “This member cannot be inserted because the parent member has another child member with the same name.”

130802_Seismi_EPMA Error on Import_1

 

130802_Seismi_EPMA Error on Import_2

 

At first this seemed like a simple mistake in my load file. After checking, I was disappointed to discover the error message was misleading. My file contained the correct structure:

#root|BALSHT

BALSHT|ASSET_ACC

The member ASSET_ACC was not repeated in the hierarchy section. The import profile was set to replace the current dimension so the fact that the member ASSET_ACC was already in EPMA should not have been an issue.

This article from Oracle’s Knowledge Base gave me a hint as to the source of the issue in the document EPMA Error “This member cannot be inserted because the parent member has another child member with the same name” [ID 1361635.1]

The issue was that in my current dimension, the member BALSHT was written BalSht. It looks like EPMA is only partially case sensitive so it was partly recognizing BALSHT and BalSht as being the same member but it was not updating that member correctly. As soon as I renamed BALSHT to BalSht in the file, the import worked.

The root cause to keep in mind is that EPMA does not handle subtle differences in cases well.

Tagged , ,