EPMA 11.1.2.1 Interface Tables Aliases are added as orphans

Hi,
I am setting up an EPMA shared library through interface tables and my aliases are not being recognized as aliases. EPMA is trying to import them as members and cannot find a hierarchy, so it is adding them to my shared dimensions as orphans.
In my database, I have it set up as follows (for simplicity I will only use 1 dimension (Years) and the alias for that dimension).
IM_DIMENSION
LOADID-----C_DIMENSION_NAME-----C_DIMENSION_CLASS_NAME-----C_MEMBER_TABLE_NAME-----C_HIERARCHY_TABLE_NAME
NULL-----------YEARS-------------------------YEAR-------------------------------------NULL---------------------------------YEARS_VW
C_PROPERTY_ARRAY_TABLE_NAME-----C_DIM_PROPERTY_TABLE_NAME
YEARS_ALIAS_VW-------------------------------NULL
In my YEARS_VW I have
LOADID-----PARENT-----CHILD-----ISPRIMARY
null-------------YEARS--------FY09----- 1
null-------------YEARS--------FY10----- 1
and i have this for FY09- FY16 (The alias will be the year written out 2009, 2010, 2011, 2012, etc)
My alias view looks like this:
LOADID------PROPERTY------NAME------KEY------VALUE
null--------------Alias---------------2009-------Default---null
I have a row for each year 2009-2016
Within EPMA, I created the alias dimension and the years dimension. I associated the alias dimension to the years dimension. I also created the import profile for the years dimension (PROF_YEARS). In the Map Dimensions section I have the dimension Years mapped to the Years shared library and selected replace as the process type. In the mapping options, only the alias column shows up and it is automatically mapped to Alias.
When I run the profile, I get the following errors:
"Member '2009' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2010' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2011' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2012' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2013' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2014' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2015' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
"Member '2016' will be added but it is an orphan. Please check the Hierarchy Section/Table for member"
(I get this error for each alias that I have)
The members all get added correctly, but the aliases are not being added as aliases, but as orphan members.
Any help you can provide would be greatly appreciated.
Thanks,
Daniel

If you are just using the default alias and you want to put an alias against a member then you include it in your hierarchy table.
You would have a column called ALIAS=DEFAULT e.g.
LOADID-----PARENT-----CHILD-----ALIAS=DEFAULT------ISPRIMARY
null-----------YEARS-------FY09----- 2009----------------------1
You would then map the column in the import profile
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

EPMA 11.1.2.1 (Interface Tables) Working with Shared Upper Level Members

Hi Everyone,
I am building a hierarchy with interface tables in which I specify a shared member. In the interface table, I assign a null datastorage and a 0 for the ISPrimary to designate the shared member. The stored member has a datastorage of storedata and an ISPrimary of 1. The sort order for the shared member is set at 999999 and the sort order for the stored member is 6.
We have an org hierarchy that goes Division->Business Group->Department. Please reference the member that is highlighted for the two questions I have below.
I just made up some hierarchy names and placed in parenthesis what the member name would look like in our real hierarchy.
Example Hierarchy:
Organization
|--Main_Hierarchy
|--|--Division1 (DV_XYZ)
|--|--|--BusinessGroup1 (BG_ABCD)
|--|--|--|--Department1 (DP_1234)
|-Alternate Rollup
*|--|--Division2 (DV_ABC) [stored]*
|--|--|--BG_123
|--|--|--|--DP_9999
|--|--|--|--DP_9876
|--|--Research Division (DV_ZZZ)
*|--|--|--Division2(DV_ABC) [shared]*
I have 2 issues with this setup.
1) When I run an import into the shared library, I see the shared member with children underneath it (the same children that are under the stored member) Is this supposed to look like that, or is there an additional configuration that I need to make? When I look in the application library, I see it correctly with the shared members having no children, but the shared library shows the shared members with children.
2) When I run a deploy to the application, the application library shows the hierarchy correctly, but Planning and the Essbase Outline reversed the members (The stored member comes in as shared and the shared member comes in as stored in essbase and planning, but the application library shows it the correct way). Just wondering if someone could suggest a starting point for me to try and troubleshoot this issue.

Is this an essbase only application? It seems like the property is defaulting to stored and then flipping the initial stored member to shared because Essbase isn't interpreting the deployment correctly. I would try using ShareData as the datastorage property (I think that is the correct spelling). Also, I believe the correct way to set IsPrimary is Y/N and not 0/1.
If that did not work I would try the following in this order:
1 - I would first extract the dimension in question using the file generator and confirm that the properties are indeed correct.
2 - If they were correct. I would toggle the dimension from shared->local->shared. EPMA is still a little nutty and this will fix a fair amount of issues as it will 'refresh' the application's version of the dimension. I would then deploy
3 - deploy from EPMA->Planning only (no essbase creation), then deploy to essbase separately after ensuring the property represents itself in planning. If it is essbase only - create the outlnie instead of refresh.
4 - create a duplicate app in EPMA and deploy the copy of the app - and see if it has the same problem
Try that and see how it goes.

Use of open interface tables in R12

Hello,
Can someone tell me the status of using open interface tables in release 12. Is this still a supported mechanism for importing data into the product, or must you use a PL/SQL/Java API, XML gateway etc?
iREP for 11.5.10 lists these open interface tables, but they are missing from the embedded iREP in R12. However, looking in the database for the RA_CUSTOMERS_INTERFACE_ALL shows that the tables exists. Is it supported to still use open interface tables, or are they just there for legacy upgrade purposes? If it is supported, where is the documentation for these R12 open interface tables?
I wish to integrate into various modules using Oracle Data Integrator and it seems to only have 'integration knowledge modules' to support open interface tables.
i look forward to your response.
Cheers,
John

Hi Helios,
Thanks for your response. Two of the links do not work.
All I really need to know for sure is that R12 supports open interface tables.
Perhaps I didn't use the embedded R12 iRep correctly - the standard view by product family certainly didn't show any open interface table, and they did not appear in the 'interface type' drop down list. However, I notice from an example on the web that you can pivot the results by interface type. I will try that when the environment becomes available again.
cheers,
John

Which Interface table should I select

I require to insert data into the interface tables for the shipping done against the customer order.
I have doubt as to which interface tables are to be selected. I am listing the interface tables which are known to me.
1. WSH_DELIVERIES_INTERFACE
2. WSH_NEW_DEL_INTERFACE
3. WSH_TRIPS_INTERFACE
Are the table names I have listed above are correct. If there are any more tables that I have to select please suggest me
Thanks in advance
Vishwanath

Hi,
Please help me out how to use the WSH_FREIGHT_COSTS_PUB.Create_Update_Freight_Costs API.
I had used the below code but it returns with error.
pub_freight_costs.delivery_id      := Delivery_Id;
     pub_freight_costs.freight_cost_type_id := P_type;
     pub_freight_costs.currency_code := 'USD';
     pub_freight_costs.unit_amount      := nvl(I.shipping_charges, 0);
     p_action_code := 'UPDATE';
APPS.WSH_FREIGHT_COSTS_PUB.Create_Update_Freight_Costs (
     p_api_version_number => 1.0
     , p_init_msg_list => init_msg_list
     , p_commit => p_commit
     , x_return_status => x_return_status
     , x_msg_count => x_msg_count
     , x_msg_data => x_msg_data
     , p_pub_freight_costs     => pub_freight_costs
     , p_action_code => p_action_code
     , x_freight_cost_id => freight_cost_id
Please send the reply to [email protected]

Purge interface tables

Hi
Can anyone suggest how to find custom and standard interface tables that are used .We need to find the purging criteria that is currently there for the table. Based on the data , we need to give recommendations if the current purge criteria is adequate.
Please suggest ASAP.
Thanks and Regards,
Ronak

You can determine standard interface tables and their purging programs/criteria by reading thru the various user and implementation guides at http://www.oracle.com/technology/documentation/applications.html.
Interface tables are also be found by looking up table documentation in http://etrm.oracle.com.
For custom interface tables and their purging criteria, you will have to refer to your own custom documentation.
HTH
Srini

Error Key word when interfacing EPMA interface table

Hi,
I'm trying to interface a SQL server database with EPMA interface tables. So basically, I'm doing SQL server to SQL server.
I already have several Interfaces that work fine, but I encounter an issue when interfacing a ...PropertyArray table in EPMA IT.
This table has a column called "Key" and I wonder if that's not the problem, key must be a special word.
Here is the error message:
ODI-1226: Step PRODUCT_INTERFACE_PROPERTYARRAY fails after 1 attempt(s).
ODI-1240: Flow PRODUCT_INTERFACE_PROPERTYARRAY fails while performing a Control operation. This flow loads target table HS_Product_PropertyArray.
ODI-1228: Task HS_Product_PropertyArray (Control) fails on the target connection CSPL_EPMA_IT.
Caused By: java.sql.SQLSyntaxErrorException: [OWLS][SQLServer JDBC Driver][SQLServer]Invalid column name 'Key'.
     at weblogic.jdbc.sqlserverbase.dda4.b(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda4.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda3.b(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda3.a(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.ddr.v(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.ddr.a(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.ddq.a(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.ddr.a(Unknown Source)
     at weblogic.jdbc.sqlserver.ddj.l(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.e(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddb9.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.v(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.x(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddb9.executeUpdate(Unknown Source)
     at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java:665)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeUpdate(SnpSessTaskSql.java:3218)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java:1785)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2805)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
     at java.lang.Thread.run(Thread.java:619)
Any idea how to fix this problem ? I gladly take workarounds too ;)
Thanks a lot,
Cyril

Hi Phani,
I don't see what you mean, sorry I'm a beginner with ODI.
I might have found a workaround though, I can update UDAs, aaliases and attribute in the Hierarchy table, I have no use of the property array table.
Thanks for your help.
Cyril

EPMA 11.1.2.2, EPMA Interface tables, .ADS File

DRM Gurus!
I'm looking for recommendations for updating EPMA with DRM. Thoughts about loading the EPMA interface tables vs using the new EPMA interface that comes with DRM 11.1.2.2 (creates the .ads file)? This client is going to have a large number of attributes... in case that matters. Recommendations are appreciated!
Cheers!

Use the DRM to EPMA templates to create .ADS files. I tend to be a late adopter of new software, i.e., DRM to EPMA using the DRM Web Services API. Wait until the bugs have been ironed out and then try the new adapter on your next gig perhaps.

Loading metadata into EPMA applications using Interface tables-Automation

Hi,
I am loading the metadata into epma applications using interface tables as ODI dont perit to load metadata into epma applications. Is there any way of using ODI and interface tables together to load the metadata
This process also need to be automated.

Hi,
It is certainly possible and has be done, though there is not anything available that will do it for you, you will have to put in some effort learning the structure of the interface tables, then build interfaces and then a package in ODI to streamline the process.
Cheers
John
http://john-goodwin.blogspot.com/

Interface tables bug?? Hyp 11.1.1.2 with EPMA patched

HI,
I am facing one issue. When loading metadata from interface tables to dimension library, not all my member properties make their way into dimension library.
This happens when i am performing load of all dimensions in one profile:
E.g. Account dimension. In interface tables i set up 'account type' as Expense and 'Variance reporting' as Expense. After I import dimensions i still see for a member these properties as 'Revenue' and 'NonExpense'. So it does not take into account my changes.
But when I load dimension account alone, these changes are being transformed to dimension library. Problem arises when i have e.g. 1 associated table with account dimension (mostly Alias dimension). Without selecting this dimension the log gives me an error (alias must be also selected) but changes will go through. When i add alias or more dimensions I will get no error which is right but changes will not go through.
Can you please help with this issue?

Is this an essbase only application? It seems like the property is defaulting to stored and then flipping the initial stored member to shared because Essbase isn't interpreting the deployment correctly. I would try using ShareData as the datastorage property (I think that is the correct spelling). Also, I believe the correct way to set IsPrimary is Y/N and not 0/1.
If that did not work I would try the following in this order:
1 - I would first extract the dimension in question using the file generator and confirm that the properties are indeed correct.
2 - If they were correct. I would toggle the dimension from shared->local->shared. EPMA is still a little nutty and this will fix a fair amount of issues as it will 'refresh' the application's version of the dimension. I would then deploy
3 - deploy from EPMA->Planning only (no essbase creation), then deploy to essbase separately after ensuring the property represents itself in planning. If it is essbase only - create the outlnie instead of refresh.
4 - create a duplicate app in EPMA and deploy the copy of the app - and see if it has the same problem
Try that and see how it goes.

EPMA - Interface Tables

I have a profile set to 'Replace' and when I use the EPMA batch client to load from the interface tables like this,
Execute Import Parameters(importtype, profilename, filename, waitforcompletion)
Values('InterfaceTables', 'Accounts', '', 'true');
...it only builds the "Revenue" hierarchy. There is an "Expense" and other siblings in this hierarchy also...
What can I be doing wrong?
Thanks,
Jz

this is the error when I try and build in EPMA...
"An error occurred while attempting to replace an existing dimension. Further dimension updates will not be processed. Error: 'Cannot remove Primary Reference Member before removing Shared Members.'"
...there are no Shared members in the dim...

EPMA very slow to import large dimension from interface tables

I am attempting to import a dimension into the master library from the EPMA interface tables. The dimension is roughly 255,000 members. The import from the interface tables into an empty dimension member is taking close to 3 hours. CPU utilization on the EPMA server is a steady 6% (epma_server.exe) for the entire time. We are on 11.1.2.1.001 of EPMA. The rest of the suite is at 11.1.2.1. The dimension generic type. I have had the same result when importing into a local dimension. The performance degrades after about 6000 members.
Your thoughts would be much appreciated.

I have found my answer from EPMA guide:
In addition to the dimension interface tables created by the template script, you can add interface tables for additional dimensions. For example, the template script contains one set of tables for the Entity dimension. You can add more Entity dimensions as needed. For each dimension added to the interface tables, you must also include the dimension in the IM_Dimension system table so that the dimension is available during profile creation.

Epma 11.1..2.0 Interface tables created but could not find the dimension

Epma gurus, interface tables (4) for Dimension account are copied to Account1 (4) tables, after copying in the Datasource,
creating a new profile

In 11.1.2.3 the data source configuration should be available in Workspace, have a read of Configuring Interface Data Sources
Cheers
John
http://john-goodwin.blogspot.com/

Problem while reversing Oracle EBiz interface tables

Hi,
I need to reverse the interface tables of EGO, GL, AP, AR modules. I have created the Data Server with "APPS" as username and pwd. I have selected the Schema and Work Schema as "APPS".
When i am reversing the model using Customized Reverse mode with "RKM EBusiness Suite", i am not getting the desired output. Not all the tables are reversed.
I am not getting interface tables for EGO, GL modules.
Any solutions would really help.
Thanks in Advance,
Ram Mohan T

Hi John,
Thanks for your quick reply.
we were successful in reversing the Dimension for Planning Classical Applications.
This error is for Planning EPMA Application.
what do you suggest.

Rejecting a moving member when using interface tables

Hi,
I'm using the interface tables to update some of my dimensions in EPMA.
My problem is that I want the process to reject members when they are moved, and I can't do that.
Let me explain a little bit more: if I have a product A under a parent X, and that in the next load, A is specified under Y, then I want the process to fail with a message like this: "the member cannot be created because it already exists under another parent".
Right now what it does is that it create the new A under Y and the A under X as shared member. I've tried to change the settings of my profile: I change Merge as Primary for 'replace' but that's not what I want. I tried 'Move' but it's not what I want. I tried to set my IsPrimary column as blank string, doesn't change anything.
Does anyone know how to do that ? Basically, we want to make sure that no product are moved by mistake. Any movement should be performed manually by the admin in the dimension library before interfacing.
Thanks for your help.
Cyril

I used only IM_Dimension & HS_Account_Hierarchy table to load data and that worked.
But now, if I want to give option to user to select the Load_Id while importing, IM_Load_Info needs to be populated.
The problem arises at the time when you try to insert data in IM_Load_Info. Even if we clear data from the table it generates next sequential Load_ID from previously deleted record. For eg. Load_Id in IM_Dimension & hierarchy table is 1, then for the same record in IM_Load_Info can have Load_id as 14.
Now user can select 14 while importing but cannot import any data since all records are having Load_Id as 1.
I am still not able to resolve/handle this problem

[Error] Import metadata from interface tables

Hi all!
We're trying to update Entity dimension through import profile and we're getting the following error:
"This member cannot be inserted because the parent member has another child member with the same name" - This happen to all members of dimension.
Since the members already exist in dimension, the import process should skip them.
We already checked if there was any issue related with Case Sensitive and there is no issue.
Hyperion Version: 11.1.1.3
Anyone can help wit this?
Regards,
Luís

Hi vvipirailo,
Thanks for your answer.
Following your tip we've tried to create a new member manually with the same name and we got the same error.
We can update old member with properties in interface table without any problem.
Looks like it sees the update as a new member, instead of old member with new properties.
About the lenght of member name or aliases we don't believe that can be an issue because we only have names and aliases with less than 25 chars.
Regards,
Luís

EPMA 11.1.2.1 Interface Tables Aliases are added as orphans

Similar Messages

Maybe you are looking for