Limitations to a Lookup Property Table

I am relatively new to Hyperion DRM. I have a question regarding any limitations to a lookup property table. How many members or rows can a look up table contain. I have a need to cross reference our sku numbers to a platform. The first thing that came to mind was a lookup property, but it could contain several thousand members. That would seem to be too much in my mind. Would an alternate hierarchy be more efficient?

Product Hierarchy
Partno123
Partno456
-----these have a value in the Product Line Property
*Example of a Lookup Hierarchy for Product Line - One Top Node and all leafs below
Product Line Hierarchy
(leaf) Product Line 1
(leaf) Product Line 2
(leaf) Product Line 3
You create a validation on the Product Line Property in the Product Hierarchy that uses the function ExistsInHierarchy which returns a T or F. The validation fires when you enter a value for the Product Line Property in the Product Hierarchy. If the Value exists in the Product Line Hierarchy, then the Boolean property you ctreate for the validation will be T and the value is accepted; if it does not exist it will return a F and you would put out the Message: Invalid Product Line - Entered Product Line does not Exist in the Product Line Hieraqrchy.

Similar Messages

Workaround on all the limitations of Qualified Lookups, Multivalued Tuples.

Dear Experts,
As we all know, there are lots of limitations on Qualified Lookups in MDM 5.5 and also in MDM 7.1....
1) Can't write Assignments...
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
5) Role level constraints not applicable for Qualified lookup and tables referencing from QL directly or indirectly.
6) Qualified link level check-in check-out operations are not possible.
7) Qualified link level unique constraints are not possible (this becomes pain if links get duplicated by mistake)
8) Duplication of QL link is not allowed in data manager (for copying Qualifier values in new Qualified link).
9) Tuple is replacement for qualified lookup, but its more restrictive than QL (validation are not allowed on multivalued tuple).
10) ....... many more (which might have discovered by you all)
What if we make all the qualified lookups as main table and link those table to actual main table using Lookup [ Main] field type?
Well it will restrict the data analysis objective which is one of goal of Master Data Management...
But this will solve all the problems and limitations due to Qualified Lookup or Multivalued Tuple!
I think its feasible and technically possible (But only in MDM 7.1 onward)
How is the IDEA !!!
Thanks & Regards,
- Shailesh.

Dear Michael,
Thanks for your valuable replay...
Well out of 9 pain points I listed above...
Some of them may be fixed in future releases...
But there are some points which (I feel) may not be on the feature list of future releases like....
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
6) Qualified link level check-in check-out operations are not possible.
(all these points are applicable for tuples also)
Above points can be ignored at the time of fresh implementation
But its become blocker in new scenarios which are taken-up after go-live! (i.e expansion of already live repository)
Most of the people in MDM might not be aware of that import works on a single main table at a time.
Well you are an expert, what you said is something new and useful... Thanks for that !
Thanks & Regards,
Shaailesh.

Record Count Limit for Lookup Flat tables

Hello Experts,
I wanted to know if there is any limit on the number of lookup values(records) that can be created in a Lookup Flat table. If yes, what is the limit and where can we find such details. Is there any SAP provided documentation for the same.
Thanks in Advance.
Best Regards,
Uday

Hi Udaya,
There should be limited number of records in lookup table when we consider MDM Performance considerations.
There is also desirable share of Main table records Vs lookup table provided by SAP.
Please refer below documentation for more details: 8.1 Performance considerations Page 61/97 onwards.
Kindly refer 8.3 Lookup tables and 8.5 Qualified tables
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70b0caa1-92e5-2c10-c687-a8d05e778e59?quicklink=index&overridelayout=true
It clearly tells that in Section 8.3 Lookup tables,
*Lookup tables and qualified lookup tables should have a very limited number of fields and number of records.
*Lookup table that are not referred should be eliminated.
*Lookup tables records between 10,000 and 100,000 records should be avoided.
*Lookup tables records above 100,000 should be absolutely avoided.
Regards,
Mandeep Saini

Limitation on the number of tables in a Database Schema!

Hi All,
Is there a limitation on the number of tables present in a schema that can be fetched in Designer while creating a universe.
Customer is using Oracle schema which contains 22000 tables and while trying to insert tables in Designer XIR2 (or trying to get the table browser) Designer hangs.
In BO 6.5 there are no issues while retrieving the tables from the schema in Designer.
Is there a way to retrieve only a certain amount of tables in Designer XIR2?
Thanks for your help!

Hi Ganesh,
Following are the Answers regaring your queries:
Query : 1
There is no limitation on the number of components (objects, classes, tables, joins, hierarchies, lov's, etc) in a universe. But of course as the number of components increases, you could run into problems related to performance.
This depends on available RAM and the processing speed.
Query 2:
There is NO such option to select the number of table to be automatically inserted in to the universe because Suppose if you have 22000 tables in DB and you want only 1000 table ,you entered 1000 tables as the value to insert tables in Universe then How Designer will come to know which tables you want to take in Schema to build the Universe?
It all depends on the DBA and Universe Designer which tables are important for organizations reporting needs.
When you create connection to the DB then Connection will fetch all table from the database and we canu2019t limit DB data retrieval.
I hope this Helps...
Thanks...
Pratik

Syndicatng from both the main tables on change in lookup main table

Hi SDNers,
I have 2 main tables, say Main table, Lookup Main Table.
The requirement is, on change/addition of values in Lookup Main table, I want the record to be syndicated consisting of the fields from the lookup main table and the corrseponding fields from the Main table.
If any one has tried this/ any work arounds, please guide.
Thanks,
Priti

Hey
This can not be done through regular syndicator, you need to use Java API/ webservice for this.
Thanks
Aamir

Lookup Flat Table and Lookup Qualifier Table

Hi,
Can any body confirm that if I will change the type of lookup-flat type field to lookup-qualifier type field. But the structure of Lookup Flat table and Lookup Qualifier table will be the same then the Java code written to populate the lookup-flat type field will work without any changes with its new type (lookup-qualifier).
Right now when I run the code after the above said changes, no error comes but no values is assigned to that field.
Another way to ask this question, can a simple Qualifier Lookup table(without having any qualifier type field) be used as like Lookup flat table.
I would appreciate if any body can help me in this regard ASAP.
Regards
Shahid Nadeem

Hi Alok,
I think this Qualifier importing after main table import is quite trickier that you estimate.
1)Map all the fields of qualified table with source fields whther they are qualifiers or non-qulaifiers.
- we will only be able to view the Non Qualifier field in the qualified table.
2)Now the main step is when you finish all field and value mapping there will be also a Target field name on your qualified table with values of display field. this field must be mapped to a source field to import qualified table. do value mapping also.
- This target field is the linkup field you are talking abot i feel, and it is viewed only in the main table and, as i have only on one non- qualifier this will not be a combination of any display fields.
3)I am not abl eto see the Non -Qualifier in my main table
So how do i proceed.
Kindly guide
Thanks
Simona

Maintain lookup/hierarchy tables from Netweaver Portal

How do we maintain loopup/ hiearchy tables from SAP Portal instead of data manager? Is this part of standard delivered portal content iviews or we need to create custom code to perform this?
Any pointer or guidance or best practice would be greatly appreciated.
Thanks in advance.

Hi,
I think it is not possible to maintain lookup / hierarchy table directly on portal, you can create lookup / hierarchy data on MDM data manager and by using standard Business content of MDM iview or by customizing iview you can represent hierarchy data to portal
refer following link for MDM Portal Content Development Guide
http://help.sap.com/saphelp_nwmdm71/helpdata/en/45/c87d0243e56f75e10000000a1553f6/frameset.htm
Thanks,
Jignesh Patel

Limiting duplicate records in secondary tables?

I have a report in CR2010 that links multiple tables. One of the linked tables has a many-to-one relationship with the primary table. I need a way to say, in effect, "Only the record with the latest date from the secondary table", thus pruning the earlier dated records. Con someone please provide a few pointers and/or some articles I can read to assist in this? Thanks!!
ETA: What's happening is that, because of the multiple records associated with each primary record, I'm getting multiple identical details, with only the one field from the other table different. I need to only have ONE detail line that is limited to that latest secondary table record.

you've got a couple of choices then...
A > Group Selection Formula
1) you can create a Group on the date field and have the Group for Every Day.
2) you can then create a Maximum on the date field
3) create a Group Selection Formula where you have = Max()
the problem with this is that you don't limit the number of records coming back to your report...you're just hiding them
B > Experiment with a SQL Expression to Use in Your Record Selection Filter
please note that this is not a supported functionality of SQL Expression fields and will sometimes work and sometimes not...hopefully it will. the following uses the Orders table in the sample Xtreme database for crystal.
1) create a new SQL Expression Field called "MaxOfMyDate" with syntax like the following...please note that i have aliased the Orders table that is used in the main report as Orders2...this is to avoid any errors by using the SQL Expression in the Record Selection Filter
(SELECT MAX(`Orders2`.`Order Date`) FROM `Orders` `Orders2`)
2) now go back to your Record Selection Filter and change it to something like
{Orders.Order Date} = {%MaxOfMyDate}
the above, if it works off of your database, will bring back only order dates that are equal to the very latest order date.
cheers,
jamie

Lookup database tables

Hi
Is any way to lookup database tables for specific values directly from FDM-script?

Yes, just connect to your database using ADO scripting and retrieve the values.

LrBinding.andAllKeys and LrBinding.orAllKeys - with optional property-table param (optObject): anybody ever got that to work?

LrBinding.andAllKeys and LrBinding.orAllKeys - with optional property-table param (optObject): anybody ever got that to work?
If so, please share your secret.
I may have it figured out by the time you post, but so far it has never worked for me - bug? or am I not doing something right?

I guess this is a bug
Lightroom SDK 5: LrBinding.andAllKeys and orAllKeys in conjunction with optional bind-to object param - doesn't work, or…

How to lookup percentile table and Records table For Dashboard purpose?

Hi Folks,
I have Created one USP_Storedprocedure : whic is create table 1 results, I have another stored procedure
which has N no of columns. But For the dashboard purpose I want 2 columns only (whic are
table 2 sample Results, that table held N no of rows that will vary every month )
my Requirement is i wnat to look up boath tables using T-Sql or any other. I neeed to find % of each person value:
i am excepingting this code for second table person %
Select PersonID,((Value * 100)/(Select MAX(values)
From XX Table) From XX Table
?? how can I lookup boath tables can you please advise me thanks in advance

Hi Cherkuri
What I understand from your statement, you want to get the percentile no in table 1 for each record in table 2.
Below is my proposed solution and its output:
DECLARE @Table1 AS TABLE
PercentileNo INT,
Per1 INT,
Per2 INT
DECLARE @Table2 AS TABLE
Person_ID VARCHAR(50),
Value INT
INSERT INTO @Table1
SELECT 1, 1, 10
UNION SELECT 2, 11, 20
UNION SELECT 3, 21, 30
UNION SELECT 4, 31, 40
UNION SELECT 5, 41, 50
UNION SELECT 6, 51, 60
UNION SELECT 7, 61, 70
UNION SELECT 8, 71, 80
UNION SELECT 9, 81, 90
UNION SELECT 10, 91, 100
INSERT INTO @Table2
SELECT 'person1',12
UNION SELECT 'person1',11
UNION SELECT 'person2',5
UNION SELECT 'person3',18
UNION SELECT 'person3',16
SELECT * FROM @Table1 t
INNER JOIN @Table2 t2 ON 1=1
WHERE t2.Value BETWEEN t.Per1 AND t.Per2
Below is the output:

How to map lookup main table field in another main table using MDM 7.1?

We created a new SAP MDM 7.1 repository with multiple main tables. The first main table is called ProductMaster table which contains Products information. The ProductCode is the primary key and the only display field for the table during data loading process. The second main table is ProductByRegion table which has a main table lookup field ProductCode and a RegionId field. These two fields (ProductCode and RegionId) combine as the PK for this main table. Both main tables have key mapping enabled.
I was able to load ProductMaster table using Import Manager. But Iu2019m having trouble to load data into ProductByRegion table using MDM Import Manager. Although I have met all the 5 requirements below (excerpted from MDM Import Manager Reference Guide P.222), the ProductCode wonu2019t show up on the destination value pane. If I mapped all productCode to NULL field, ProductCode wonu2019t load. If I u2018Addu2019 all ProductCode to Destination Value pane, the Import Manager added duplicated rows to Product Master table while only loading 1 record to ProductByRegion table. I canu2019t get ProductCode show up in Matching Destination Field list. When I checked ProductMaster records in MDM Data Manager, I right-clicked on one of records, chose Edit Key Mappings, it didnu2019t show anything. However, if I right-clicked on one of those duplicated rows, Edit Key Mapping shows remote system and key correctly.
Where did I do wrong? How can I fix the problem?
Thank you for help in advance.
From: SAP MDM Import Manager Reference Guide:
Mapping to Main Table Lookup Destination Fields
Import Manager handles main table lookup fields (Lookup [Main])
differently than other MDM lookup fields. Specifically, Import Manager
does not display the complete set of display field values of the records
of the underlying lookup table. Instead, the values it displays for a main
table lookup field are limited by both the key mappings for the lookup
table and the values in the source file.
Also, Import Manager does not automatically display the values of a
Lookup [Main] destination field in the Destination Values grid when you
select the field in the Destination Fields grid. Instead, for a main table
lookup field value to appear in the Destination Values grid, all of the
following conditions must be met:
u2022 The lookup table must have key mapping enabled
u2022 The lookup field must be mapped to a source field
u2022 The source field must contain key values for the lookup table
u2022 The destination value must have a key on the current remote system
u2022 The destination valueu2019s key must match a source field value
NOTE ►► The current remote system is the remote system that was
selected in Import Manageru2019s Connect to Source dialog (see
u201CConnecting to a Remote Systemu201D on page 416 for more information).
Vicky

Hi Michael,
Thank you very much for your response. I'm new to SAP MDM, I need some clarification and help regarding your solution.
I did use two maps to load ProductMaster and ProductByRegion separately. Here were my steps:
1. create main table ProductMaster with key mapping enabled at the table level and set ProductCode as unique and writable once (primary key).
2. create a map to load ProductMaster record from a staging table located an oracle database. But Key mapping didn't show anything when I looked at them using Data Manager.
3. create main table ProductByRegion with a lookup field looking at ProductMaster table. This field and RegionId combines as a unique field for ProductByRegion table.
4. create a map to load ProductByRegion table. But ProductCode records only shows on the source pane not destination pane and can't be mapped properly.
My questions:
1. How can I "Ensure that you add key mapping info for all ProductMaster records" besides enabling Key Mapping on the table level?
2. How can I define a concatenation of ProductCode and RegionId as a REMOTE KEY"?
Thanks a lot for your help!
Vicky

JDBC Lookup - Import table data from a different schema in same DB

Hi XI Experts,
We are facing an issue while importing a Database table into the external definition in PI 7.1.
The details are as below:
I have configured user 'A' in PI communication channel to access the database. But the table that I want to access is present in schema "B". Due to this, I am unable to view the table that I have to import in the list available.
In other words, I am trying to access a table present in a different schema in the same database. Please note that my user has been given all the required permissions to access different schema. Even then, I am unable to access the table in different schema.
Kindly provide your valuable suggestions as to how I can import table which is present in another schema but in the same Database.
Regards,
Subbu

If you are using PI 7.1, then you can do JDBC Lookup to import JDBC meta data (table structures from DB). Configure a jdbc receiver communication channel where you specify username and password which has permission to access schema A and Schema B of database. Specify database name in the connection string. Then you might have access to import both schema.
Please refer these links
SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
How to use JDBC Lookup in PI 7.1 ?

Memory Limitation on EXPORT & IMPORT Internal Tables?

Hi All,
I have a need to export and import the internal tables to memory. I do not want to export it to any data base tables. is there a limitation on the amount of memroy that is can be used for the EXPORT & IMPORT. I will free the memory once I import it. The maximum I expect would be 13,000,000 lines.
Thanks,
Alex (Arthur Samson)

You don't have limitations, but try to keep your table as small as possible.
Otherwise, if you are familiar with the ABAP OO context, try use Shared Objects instead of IMPORT/EXPORT.
<a href="http://help.sap.com/saphelp_erp2004/helpdata/en/13/dc853f11ed0617e10000000a114084/frameset.htm">SAP Help On Shared Objects</a>
Hope this helps,
Roby.

Using Dense/Sparse Lookup on Tables or files from different Databases

Hi,
I have a Subject Area which is built on Essbase cube. I have a requirment where I have to use a Lookup on Flat file and/or Database Table.
I followed below steps
1. Created a Logical Column in BMM Layer for a cube dimension
2. Opened the LTS Properties --> Column Mapping and gave below formula
Lookup(SPARSE "Function1"."E:\502125500".""."Function2.txt"."ALIAS", 'NA', "TNWD06613.genpitfi01.og.ge.com"."GOGREP".""."GOGREP"."Gen5,Functions" )
where
Function1"."E:\502125500".""."Function2.txt"."ALIAS" ---> Column from File (Created File DSN and imported in RPD)
"TNWD06613.genpitfi01.og.ge.com"."GOGREP" ---> Essbase Cube
3. Dragged the Column to Presentation for Subject Area on Cube
When I try to create a report on this column I get below error.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 16001] ODBC error state: 22005 code: -3030 message: [Microsoft][ODBC Text Driver] Expression too complex. [nQSError: 16015] SQL statement execution failed. (HY000)
SQL Issued: SELECT 0 s_0, "Essbase Test"."Functions"."Alias" s_1, "Essbase Test"."Functions"."Gen5,Functions" s_2, SORTKEY("Essbase Test"."Functions"."Gen5,Functions") s_3 FROM "Essbase Test" FETCH FIRST 65001 ROWS ONLY
Can anybody help me on the same?

You can script schemas from all DBs and in case of conflicts you will have to decide what to do.
For example if you have the same SP or UDF on two DBs that does different things, you need to decide what to do with them.
Only if the conflict is tables with the same structure and without KEY constraints and you can also script data and go on.
If you have PK-FK relationships (which I bet is the case) you really need to design your changes based on them and I suspect you will end up scripting instead of putting boxes on SSIS.
It really is a migration job for an experienced DBA and am afraid SSIS can do that much as
Integrate.. not Migrate.

Limitations to a Lookup Property Table

Similar Messages

Maybe you are looking for