DESTINATION_APP dimension value unable to be set in *REC

Hi,
I want to move data from one application to another and set the value of a destination dimension (which is not part of the source application so I use ADD_DIM to add it) to the property of a source dimension.
However, I get a validation error at the *REC statement stating the destination dimension is not a valid keyword. All dimensions which are NOT part of ADD_DIM work in *REC but all new dimensions which are listed in ADD_DIM do not work in the *REC statement.
Here is the code I am trying to validate:
*DESTINATION_APP = GL
*SKIP_DIM = Z_COSTCENTRE, Z_CX_IDNO, Z_CX_KEYFIG, Z_FLOW, Z_LCGU
*ADD_DIM Z_GLACCOUNT=31301, Z_GL_ENTRYNO = CX001, Z_GL_KEYFIG = DR, Z_GL_BU = BU_1070
*WHEN Z_CX_KEYFIG
*IS "CX_SPEND"
*REC(FACTOR=1,Z_GL_BU=Z_COSTCENTRE.BU)
*ENDWHEN
The error says: "Unknown dimension name in Keyword: Z_GL_BU"
Any idea's on how I can set the value of the destination based on a property of the source.

Hi,
May be you can try:
*DESTINATION_APP = GL
*SKIP_DIM = Z_COSTCENTRE, Z_CX_IDNO, Z_CX_KEYFIG, Z_FLOW, Z_LCGU
*ADD_DIM Z_GLACCOUNT=31301, Z_GL_ENTRYNO = CX001, Z_GL_KEYFIG = DR, Z_GL_BU = BU_1070
*WHEN Z_CX_KEYFIG
*IS "CX_SPEND"
*REC(FACTOR=1)
*ENDWHEN
The reason I removed the other part from the REC statement is because you are adding the dimension Z_GL_BU with a default value of BU_1070. This means that every record transferred will have the same BU_1070. We cannot change the member of this dimension using the REC statement.
Hope this helps.

Similar Messages

How to get Implicit Dimensions/Dimension Values in the result set?

Hi All,
How does endeca return implicitly selected dimensions in the result set? For example, consider a dimension set up for Television data as below.
Brand
Samsung
LG
Philips
Type
LEDs
LCDs
Plasma
Lets say, I refine the result set by brand, by selecting Philips. Now lets assume that there were 2 results returned for philips and both the results were of Type - Plasma. In this case, Endeca does not return the Type dimension in the result set, as we cannot drill down the 2 results further based on LED or LCD.
How does Endeca return these implicit dimensions in the result set in such scenarios? Suppose if there was a requirement to show to the user that both the results were of Type - Plasma, how do we get this information from Endeca, by default?
Thanks in advance :)

How does Endeca return these implicit dimensions in the result set in such scenarios?Check out: Navigation.getCompleteDimensions() or Navigation.getCompleteDimGroups()
http://docs.oracle.com/cd/E28910_01/PresentationAPI.622/apidoc/javadoc/navigation/index.html

Dynamic setting of the dimension values.

Summary:
How can I programmatically control the dimension values displayed in ‘Selected’ window of ‘Edit worksheet’ wizard. of Oracle BI Discoverer plus for OLAP 10.12.48
My objective is to dynamically set the dimension values for a particular dimension based on some criteria.
Requirement:
1.The user should be able to select one of the pre-defined options.
2.Based on the option selected by the user, the necessary business logics need to be applied and then resets the dimension values. The ‘Selected’ window of ‘Edit Worksheet’ should be refreshed.
3.Based on the option the short description & long description should be changed
Existing Application Implementation:
We already implemented this logic in oracle express 6.3.4 as follows.
1.Radio buttons are provided to select the display option
2.Whenever the option is changed, a program is executed in the Express objects. This program evaluates the option, applies the necessary business logics and displays the dimension values based on the option chosen. View is then refreshed to reflect the new dimension values. Note that this process does not affect the total “available dimension” values. The total number of “available dimension” values remains the same. It just manipulates the values in the ‘Selection’ object.
3.The formula of the short description and long description is modified. This formula checks the option and based on it changes the description
Issues I faced to Implement this logic in Oracle BI Discoverer plus for OLAP 10.1.2.48
1. No provision to add radio buttons, hence were trying to implement the functionality with a dimension.
2. No options available for applying business rule and setting the desired dimension values.
3. No ‘event’ available to refresh the views
How can I achieve this in Oracle 10g discoverer plus for olap 10.1.2.48
Thanks,
Natarajan

I think this is not possible.
When you give this settings while creating the SMARTForm, SMARTForm will generate a FM based on that settings. And it is not possible to change those settings at runtime.
We have some constriants like this for dynamic paradigm in SMARTForm. Like, we can provide shading or Box color for the cell.
Regards,
Naimesh Patel

Limiting Dimension Values to Dimension Values used on Specfic Day

If I have a dimension with thousands of values. And within my cube, on a given day only a few of those dimension values are actually used. How can I limit the scope of my dimension values to be only the values that exist on that given day?

You can check OLAP DML Programs chapter (chapter 4 in 11g doc set) in Oracle OLAP DML Reference document. It's part of the standard olap documentation.
Also regd the parameterization question:
The code as pasted below is already parameterized. By parameterization, do you mean something other than passing value from front-end to the back-end (database)?
Typically the front end report/query will refer to a series of time dimension values -- say, 16-Jul-2012 to 22-Jul-2012 for time. The report would reference a measure with a formula referring to an olap dml program. This program is called repeatedly for each cell and the appropriate dimension member values are passed as input to the program.
argument _tm time <-- implies that the program accepts time dimension value (corresponding to a single cell) as input and works off the same in its calculation.
limit time to _tm <-- usually this is done within a tempstat context to make such changes temporary for calculation w/o affecting external time dimension status. This allows the program to set the context of calculation to current cell (say 18-Jul-2012)
"hence what follows for the rest of the program acts on the restricted status in order to calculate the current cell's value corresponding to time dimension value = 18-Jul-2012.
That's also why the same program can return a different value for each cell (different return value for 18-Jul-2012 compared to return value for 21-Jul-2012) although it's being looped over dimension status implicitly.
HTH
Shankar

Logical column - Fact measure using Dimension value

Hello all, I have a Fact table that has a metric (Value) where I have set the Aggregation rule to Sum. Now I'd like to create a metric based on the value of a Product Dimension that joins to this Fact table. So I create logical column that has the syntax - Case When Product_Desc = 'A' then Value else 0 End.
The issue is in Answers when I bring this new metric in it doesn't bring in the correct value, are there steps I am missing with creating this metric?
My assumption is if I just bring that new metric in by itself it would return one record - A sum of the Value where the Product = 'A'.
Thank you

Hi BRizzle,
In your scenario, you creatre a calculated measure using the employee dimension, and then this measure show "#VALUE" on the pivot table, right? It seems that it's a limitation of using calculated measures in SQL Server Analysis. Calculated measures cannot
be secured using Dimension Security in a straight forward manner, in fact they won't be listed at all in the Dimension tab of the role where we define the Dimension security. When such measures are browsed in client tools like Excel, the value that would be
displayed is an error value like #VALUE. For the detail information about it, please see:
Limitations / Disadvantages of using Calculated Measures / Calculated Members in SSAS
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Best Practices - Dynamic Ranking, Dimension Values to Return, etc.

The pinned post says non-technical questions belong on the Business Forum. I can't find an Endeca-specific business forum. If there is one, please tell me where to find it.
My question is about dynamic ranking and the initial display of only the top N dimension values with a "More..." option to see the rest of them.
What's the current wisdom on this from a usability point of view? Use it, don't use it? If using it, show how many values initially?
Or, if not using it, you instead set up a hierarchy of dimensions so that the user never has to look at 50 choices for something?
This is not a technical question. What is the current wisdom? What are the best practices?
Thanks!

Dynamic ranking is a good choice only if all choices cannot be further grouped. In my practice most of the content can be normalized and restricted to a very limited set of options. Dynamic ranking with "more" is an easy way out and seems like a lazy take on content management.

Can you hide a dimension value but display one of it's attributes?

Can you hide a dimension value but display one of it's attributes in a query output?

Hi Prakash,
I assume you are referring to a characteristic ('dimension').
This is possible: If the attribute is a navigational attribute you can include it in the query definition without the 'parent' char.
If the attribute is a Display attr then you can try by setting the Display property of the parent char to No Display (right click the char in the query > Properties)
Hope this helps...

Partial Update - Unknown Dimension Value ID

Hello Old Endeca Friends,
I am getting a lot of these sorts of errors when I perform a partial update:
ERROR 04/25/13 16:56:21.115 UTC (1366908981115) DGRAPH {dgraph,update} Record change references unknown dimension value id 4294484500 [recspec=`UPI:100224148']
I am using MDEX 6.4 and PS 6.1.3. The dimension value ids in question seem to be in the autogen_dimensions.xml, but the dgraph doesn't seem to recognize to know about them. Why?
Any further insight would be appreciated. "Just run a baseline" is not a good answer, I need to do partials every hour throughout the day.

Thanks for the input, everyone.
It looks like my issue was that my state file had a set of updated dimensions but my dgraph did not.
I had a baseline extract with properties X, Y and Z (let's say) and I was adding in new dimensions A and B. I moved my state files from my test environment to my production environment with entries on dimensions A and B. I started getting partial data for dimensions A and B and processing it. However, my dgraph knew nothing about A and B. So, although forge created the dim vals fine and the state files were modified appropriately, my dim val updates and adds on my dgraph failed because my dgraph had never processed a baseline extract with dimensions A and B.
Once I ran a baseline with dimensions A and B, partial updates went fine and have now processed dozens without issue.
Unfortunately, I only get baseline data once a week, so it took me a bit of time to realize what was going on.

Sorting dimension values

Is it possibe to sort dimension values in hierarchy in order diffirent from alphabetic?

When you define a dimension you should notice on the first tab an option to set the type of dimension. The options are: User and Time. For a Time dimension you need to select type Time and this will automatically sort the members into calendar order for you. However, your source table does need to contain some additional metadata such as Time span (number of days for each time period; week=7, month=28 or29 or 30 or 31 Quarter=90 or 91 and Year = 365 or 366) and End Date for each time period. These two additional attributes are used for both sorting and to enable the time based calculations such as:
Year To Date
Prior Period
Future Period
Moving Total
Moving Max
Moving Min
Does that help?
Keith Laker
Oracle EMEA Consulting
OLAP Blog: http://oracleOLAP.blogspot.com/
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
DM Blog: http://oracledmt.blogspot.com/
OWB Blog : http://blogs.oracle.com/warehousebuilder/
OWB Wiki : http://wiki.oracle.com/page/Oracle+Warehouse+Builder
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Navigation from a chart to different reports depending on dimension value

Hi all,
Quick question: Imagine you have a bar graph based on a metric displayed for a specific dimension (#items sold by geographical regions). In this case each different bar represents the different dimension value (the different geographical region). I know on clicking a graph, the action can be drill down (if the dimension supports it) or a navigation to another report.
What i need to do is navigate to another report, and filter that report according to the actual bar ive selected (i.e. in this case im taking to a report with additional detail but only for the region i have clicked on in the bar graph).
Any ideas?

In the target report, just set the dimension column as IS PROMPTED. and in the main report chart set the navigation to the target report. thats it, now when ever you click on the value that passes the dimension value to target report.

How to limit dimensions values of querybuilder

Hi,
I want to learn how to limit dimension value in query builder. i want, the user who run the querybuilder can not see a dimension value which i do not want to display.
For example,
The time dimension has "2000" and "2001" values as default which is defined in database. Normally when i run the querybuilder for create new presentation or calculation, In the dimensions panel of the querybuilder display all values of each of dimension. The user can select values which she/he want from that list.
But i want to limit values which the user can see in the dimensions panel of the querybuilder. for this time dimension example, i want to hide "2001" value from the user. How can i do it. if there is any sample code, please share.
Thank you very much for your helps.
ilknur

Thanks Thomas, excellent suggestions as always.
If anybody wants more information regarding Thomas' suggestions please refer to
Oracle9i OLAP Developer's Guide to the OLAP DML for the AW Permit command.
In sumamry: To create permission programs, you define two programs with the names permit_read and permit_write. In these programs, you can specify PERMIT commands that grant or restrict access to individual workspace objects. In addition, you write these programs as user-defined functions that return a Boolean value, and the return value indicates to Oracle OLAP whether or not the user has the right to attach the workspace.
For relational security there is an excellent tutorial on the database pages of OTN, follow this link:
http://otn.oracle.com/obe/start/index.html
then follow the links for Oracle9i Database Release 9.2.0.2 - Security - Creating Label-based Access Control. This module describes how to use Oracle Label Security to setup security based on label policies
These security layers should be transparent to the OLAP metadata layer, therefore, once you have implemented your chosen security method your BI Beans application will only need to connect with the appropriate user to inherit the security layer. For more information see the Security section of the BI Beans Help:
http://otn.oracle.com/bibeans/903/help/
BI Beans product Management Team
Oracle Corporation

Using a session object to hold the value of a record set?

Hi,
I'm trying to hold the value of a record set (or literally the content of a column in a query in a db) in a session variable so that I can call on this later and insert into another table.
I'm not sure of the correct syntax, I've already made a connection to the DB. I'm trying the following but it doesnt seem to like the code:
<% session.setAttribute("code",rs("column_name")); %>
<%String attrib =
String.valueOf ( session.getAttribute("code")); %>
Hello <%= attrib %>
Any ideas, I dont know how to reference the record set, I declared the recordset previously as rs. Help! Can't find examples anywhere on the net!

So just to recap. I appear to be seeing the column name "custorderno" within the Microsoft Access query "lastcust". But I get "no data found" when I run the following code (which I have sectioned off)
<!-- connect to database and lastcust query --!>
<%
try{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
Connection conn = DriverManager.getConnection("jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=C:/Tomcat/jakarta-tomcat-4.1.31/webapps/ROOT/Oatcake.mdb","","");
Statement statement = conn.createStatement();
String sql = "SELECT * FROM lastcust";
ResultSet rs = statement.executeQuery(sql);
while (rs.next()) {
%>
<TR><TD><%= rs.getString("custorderno") %></TD>
</TR>
<% session.setAttribute("code",rs.getString("custorderno")); %>
<% String attrib =
String.valueOf ( session.getAttribute("code") ); %>
Hello <%= attrib %> [B]
<%
%>
</TABLE>
<%
if (statement != null)
statement.close();
if (conn != null)
conn.close();
catch (Exception e) {out.print(e);}
%>
</BODY>
</HTML>
No as mentioned I am (as you can see) declaring everything as a string when in actual fact the contents of the "custorderno" within the query is set to a autonumber within MS Access.
The while loop does work by returning the contents but the session object part is not working correctly with the following result returned:
[B]java.sql.SQLException: No Data Found
Help please!

Help Needed in Input Value Help of Custom Set attribute

Hi All,
We have maintained value table for custom set type attribute. We generated UI configuration for this set type and brought it into the web UI. But, we did not get the value help on the UI.
We are trying to get the value help by implementing the BADI crm_prdgenset_valuehelp. This BADI returns object of type cl_bsp_wd_valuehelp_f4descr.
PFB the code that is showing up the Value help icon but it is not showing any values.
DATA: lv_valuehelp_descriptor type ref to cl_bsp_wd_valuehelp_f4descr.
*    lv_fname_prefix = 'STRUCT'.
   ls_map-context_attr = component. "ZCSDR_PRD_CLS
   ls_map-f4_attr = 'KEY'.
   INSERT ls_map INTO TABLE lt_outmap.
   INSERT ls_map INTO TABLE lt_inmap.
   CONCATENATE 'ZCSDR_CLS' 'ZZ0010' INTO lv_help_id SEPARATED BY '-'.
   CREATE OBJECT lv_valuehelp_descriptor
     TYPE
       cl_bsp_wd_valuehelp_f4descr
     EXPORTING
       iv_help_id                  = lv_help_id
       iv_help_id_kind             = if_bsp_wd_valuehelp_f4descr=>help_id_kind_comp
       iv_input_mapping            = lt_inmap
       iv_output_mapping           = lt_outmap
       iv_trigger_submit           = ABAP_TRUE.
   rv_valuehelp_descriptor = lv_valuehelp_descriptor.
Any pointers on this is really helpful.
Thanks,
Udaya

Hi Chand,
Sorry for the late response. As far as i recollect, i guess we have enhanced the setter getter methods and written logic in the get-v method.
Let me know if the issue is resolved.
regards,uday

Few dimension values used in FACT tables.

Hello all,
We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
Thanks and Regards,
Upendra

nilanjan chatterjee wrote:
Hi,
>
> The data for the parent members should be available in the SQL tables.
> For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
>
> Hope this helps.
I guess you meant should not, right ?

Dimension values display order and record details

Hi All,
I have explicitly ordered my dimension values to be in a logical order instead of alphabetical. Ex: Small, Medium, Large. This works great in the navigation tree but when I view a specific record and it has those 3 dimvals they are listed in alphabetical order.
Is there a when doing a record query to ask Endeca to respect the same display order as in the nav query?
Thanks,
Luc

We are used to add two dummy records in each dimension.
We add the following data:
We use '-1' (surr-key) for Invalids and '-2' for Unknown.
Easy way to populate these dimensions is to add a script together with all objects when you release new functionality. Beware you use the same descriptions.
Even better is to think of a more general solution (more easy to maintain) and store these values in a support table. In such a table you will be able to add more columns to get more details per row. Use this reference table when you load youre dimension. Also you will find the opportunity to add more error handling cases. Especially when you add the dimension in this support table.
Regards
Moscowic

DESTINATION_APP dimension value unable to be set in *REC

Similar Messages

Maybe you are looking for