Add shared members to interfaces tables

Hi guys
I need to load shared members to a generic dimension using interface tables?
How can I do it?
Regards

Hi John
Thanks for your help. I can add shared member to the generic dimension called PCM_Prod, however I am getting the following issue
at validate one application that I used:
Error : Last generation 2 member of dimension PCM_Prod is Total Productos. Expected member name "NoMember".
Error : Dimension 'PCM_Prod' does not support shared members because the dimension hierarchy type is set to 'Stored'. Member: '3032182'.
Error : Shared member '3032182' cannot exist under generation 2 ancestor member 'Total Productos' in dimension 'PCM_Prod' because it does not belong to a StoreData hierarchy. Either set the dimension-level Hierarchy Type property to 'StoreData', or else set the Hierarchy Type property of generation 2 ancestor of this member to 'StoreData'
If I upload using ADS I did not get the issue.
So I do not why using interface tables I got the error.
Regards

Similar Messages

Loading shared members from interface tables

Hi,
I am loading data to Hyp. Planning via interface tables. I need to load shared members. Where can i tell him that this is a shared member?
thank you very much
lubos

Will not it cause probles when loading shared members first before the original ones?
I thought that DataStorage only accpet values like StoreData, NeverShare etc.
I will try it out.
Thank you very much for your help
lubos

Shared Members on interface changes of Entity or account hierarchy

Hello,
Is there any scripted way to remove 'Shared Members' from the Account and Entity hierarchy, or if not, is there any means of finding them on mass, as we have set up a database interface to maintain account and entities, but the problem is after accounts or entity change parent they leave a 'Shared Member' on the original parent, which is not desired functionality as it throws totals out on forms / reports.
thanks for your input, no blogs please as our security prohibits me seeing them.
Robert.

Thanks John, can I ask you a follow on also...
If a member had never share as its property and you used the hierarchy interface to assign it to a new would would it; -
a. Prevent update of its parent hierarchy via the interface
b. Move it to whatever new parent you deemed and remove it from its original
thanks for your input,
Robert.

EPMA interface load for shared members

Hi,
Iam trying to load metadata to EPMA shared library through interface tables. was able to load everything except the shared members. I checked with IsPrimary value and set it to N/0 values also kept datastorage type to shareData. But still not getting updated. Import result gives the follwoing warning.
"The import section 'Hierarchies' contains multiple primary instances of member '698035' in dimension 'Account_Shared'. Only the first instance will be processed"
Please help me out.
thanks,

am still not able to sort out the above problem. can some one please help me to load shared members to EPMA shared library ?
thanks,

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/

Dimension load thru Interface tables

Hi,
I have a generic type dimension with its members in interface tables (member, property, propertyarray and hierarchy). All the three dimensions im_load_info, im_dimension and im_dimension_association have relevant data and i_Load_ID in im_Load_info table has a value say 1. This 1 has been mentioned in the rest 2 tables also.
Now, while I am creating a profile for interface table, it is asking for interface load id but in the right side "find" icon, I cannot see any load_id and in fact, I am getting an error message that no load_id is present in the interface tables.
Please suggest if anything else needs to be done to view the load id during creation of the profile.
I am using 11.1.1.3.
Thanks.

Hey Guys,
Is there any update on this?
Thanks.

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.

Interfacing to a third-party system through a shared SQL Server DB Table

Guys, I have been given a task of interfacing to a third-party system through a shared SQL Server database table.I had never come across such implementation.Can anyone please let me know the methodologies involved in it.
Thanks,
Jack.

This line:
stmt.executeQuery(query);
should be:
stmt.executeUpdate(query);

Impact if I add many shared members...

Hi,
I currently have a dim say Mgttax..
There is a requirement now to maintain a new roll up under Mgttax which is going to have all the leaf members which are currently now under Mgttax..
All the current leaf members are stored now...
As they are going to be duplicate they will be as Shared members..
So if I add all these members to a new rollup which has all the lead members as shared members...will theere be any impact on the calc time..i mean will it increase the calc time??
I'll have only two roll ups under the new roll up...
Say original dim is mgttax which has many roll ups and all the leaf members are stored...
I add a new rollup(say NEW) just below the top parent Mgttax under which i have only 2 roll ups(say X and Y)
and all the leaf children which are now will go to any one of the 2 roll ups(either X or Y) under the new roll up(NEW)
By this will there be any major impact???
Thanks in advance..

If the shared members are split evenly between the two parents, thats 1000 members per parent, It's worse if it's uneven. If possible I would suggest adding more levels in your share (If possible) to reduce the number of blocks that have to be read to create a perent. If you can't then try calcfrombottomup (Look for the correct spelling in the function reference and read the disclamer). At any rate 2000 members is not terrible depending on the number of dimension and the number of members in the other dimensions of your cube.

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.

Moving of Shared members

Hi,
I have to move shared members within a dimension in outline from one hierarchy to other, using a dimension build rule. I am doing this through flat file, using Parent-Child relationship, and unchecked the option of "Do Not Share" and "Allow Moves". But This is not working out, as my stored members are getting moved first.
Its like I want to cut an existing Shared member from one hierarchy in a dimension and paste to another hierarchy in same dimension.
Also the entire dimension is statically built and we can't re-create the entire dimension with dimension rule file and add the shared member where needed and then using "Remove Unspecified" option delete the shared member which is not required.
Is there any other settings or is there any possibility of achieving this without building the entire dimension through rule file as I have lots of generations and children involved in it.
Experts, please help me out.!!!

Well, you sure don't want to add them manually. :)
How about a source table for this dimension in parent/child format?
You can have the "master" a & b in the first rollup to a parent, and then the shared reference as many times as you want.
Of course don't sum the parents or you will count the values of a and b multiple times and get a really screwy number.
For an excellent review of how to do this through a dimension load rule, see our old friend the DBAG.
Regards,
Cameron Lackpour

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

Import standard Purchase Order process and interface tables

Hi all,
We are populating three PO interface tables from our custom developed application. PO_HEADERS_INTERFACE, PO_LINES_INTERFACE and PO_DISTRIBUTIONS_INTERFACE. We are using 11.5.10.2 version of Oracle Apps.
Initially we did not manage to populate the distributions interface table, but, now we are populating it. And after doing so, when we run the Import standard Purchase Order process for 'Approved' POs, the process_id for even the record which has correct distributions info also gets 'Rejected' as a value. The process is considering a mix of records : the approved POs that DO NOT HAVE distribution info in PO_DISTRIBUTIONS_INTERFACE (which we had not managed to populate) and the approved POs that HAVE distribution info in PO_DISTRIBUTIONS_INTERFACE.
does the Import standard Purchase Order process populate partial data that could be good or it rejects the whole lot of records?
Can anyone guide on this issue?
Thanks and kind regards,
Aparna
Edited by: Aparna on Jul 24, 2009 3:45 AM
Another piece of info I would like to share is
I have run the process for an approved PO with distributions info in PO_DISTRIBUTIONS_INTERFACE. This time no mixed data. In PO_INTERFACE_ERRORS table, an entry was found: for column name : PO_DISTRIBUTION_ID in ERROR_MESSAGE column 'Error: Has no distributions'.
Edited by: Aparna on Jul 24, 2009 8:03 AM
After carrying out number of tests, I have found out that
1) if the approval_status for the po is 'Approved' in the po_headers_interface table, it gives the above mentioned error and the process_id is 'rejected'.
2) if the approval_status for the po is 'Incomplete' in the po_headers_interface table, the process add the 'accepted' value for the process_id. But, the charge account number is not populated in shipments.
Edited by: Aparna on Jul 31, 2009 1:07 AM
There has been some progress on this issue. The process sees distributions data into the PO_DISTRIBUTIONS_INTERFACE table. Yet the following errors are found in the process log file:
Start dist default process
before getting period name
after getting period name
-->Intfc error occurred ...PO_PDOI_INVALID_GL_ENC_PER
before workflow
unit price = 18.5, rate = , unit price in functional currency = 18.5
after workflow
Start dist creation process
Start dist validation process
-->Intfc error occurred ...PO_PDOI_INVALID_BUDGET_ACCT
Start insert new record into po_distributions
Distribution ID: 252
dist num: 1
last updated by: 1189
po header id: 5283
po line id: 5878
line loc id: 5924
sob id: 21
cc id: 1560
qty ordered: 10
Req Header Ref num :
Req line Ref num :
Req dist id :
ROW ID: AAHUc1AFPAAAQ04AAC
call tax
Rollback for the Last Errored Line: 10
All Lines in error - Rolling back the header
We opened new GL periods for the calendar and yet same errrors are seen. Can anyone suggest any solution?
Kind regards,
Aparna

Hi
Do you have a copy of your insert statement?
regards

Add shared members to interfaces tables

Similar Messages

Maybe you are looking for