Query in Navigation

Hi all,
We have a requirement in SAP CRM 5.2 which requires us to navigate between views of different components ( say from Lead Component to Opportunity Component) .
Kindly guide us on how to achieve the above please.
To be more specific :
We are putting a button in the view BT108S_LEA/Result of the Lead Component ( Component : BT108S_LEA ).
When we click that button we need to navigate to the view BT111H_OPPT/ DetailsOV ( Component : BT111H_OPPT ).
Please guide us on the above with screen shots etc.
Kindly reply immediately as this is bit urgent .
Regards,
Vijay

press Shift+F5.

Similar Messages

Execute query without navigation

hi all,
My problem today that I want to execute query without navigation.
I create a global variable
(:global.usr := :block.username;)
as you see the global variable takes the value of the current user accessing the system.
I want the user to be able to change his password without any privilage to see the other users.
when_new_form_instance
execute_query;
that what I did but what I want is to restrict his access only according to the value in the global variable

I tryed to run the following code but I dont know why the condition in the else clause always execute.
if :global.usr = :global.usr = upper('ADMIN') or
     :global.usr = upper('SYS_ADMIN') then
     set_block_property('SYS_USER', DEFAULT_WHERE, '');
     execute_query;
     else
               set_block_property('SYS_USER', DEFAULT_WHERE, 'USER_NAME = :global.usr');
               execute_query;
     end if;

Filtering in query through navigational attribute.

Hi all,
I want to restrict my query on the basis of navigational attribute (Material Type) of my info object (0Material) in query designer but when i drag material attribute in Filter tab page it doest work and does not appear in filter tab.
Please help me how can i restrict this in this manner.

if it is selected, then in query, drag drop 0material___type infoobject.. do not use attribute under 0material.. you can find this in the same dimension as of 0material.

Infoset - Query with navigational attribute as filter

Dear all,
We have created an InfoSet linking an InfoObject 0COORDER to an Info InfoCube containing order data.
We have used a Left outer join to link 0COORDER tol 0COORDER in the InfoCube. The purpose is to be able to report on all 0COORDER even if they have no transaction data.
When creating a query we get a list of all 0COORDER as expected. The problem arises when we try to use the navigational attribute "Status" from the InfoObect 0COORDER as a filter in the query. This does not work at all.
Does anyone know what we are doing wrong here ? We are using BEx Query Designer 7.0.
Kind Regards,
Mikkel

Hi Mikkel
When you say that your Status field does not work at all, what is the error you are getting? Are you able to see this field in the query designer. If that is not the case that means your "status" is not chosen in the infoset design.
If you are able to see it in the designer then please let us know what is the exact error you are getting.
Thanks.

Query on Navigational attribute of navigation attribute

Hello,
we work on BW 7.0 but use still the 3.5 BEX. Is it possible to navigate
on a navigational attribute of a navigational attribute? If yes, is
this only possible in the the next version of BEX? Because in the
version 3.5 I didn't find a possibility to do that.
Thanks.
Regards, Lars.

Hello Lars,
This isn't possible; you can also refer to below thread -
Navigational Attr of Navigational Attr in cube

Query regarding navigation in OBIEE.

Hi,
I have a report1 having columns
a b c
I haver another report 2 with columns
d e c
I want if any value of column c in report 1 is clicked, it should navigate to report2.
Also I want all the filters selected in report 1 should be carried to report 2.
Please suggest how to do this.
Regards,
RC

Thanks Balla for the reply.
I don't want column c to be prompted in any of my report.
Column c is the sales fact . I want to see the distribution of sales fact among the sales reps in my report2 where report 1 shows sales at region level.
in report 1 i have qte=r and product as prompts which i want to carry to report2 .

Query Syntax for Dynamic Navigation Menu

I'm trying to build a Navigation menu from a query using the following syntax:
select LEVEL,
       LABEL,
       LINK,
       'NO' as IS_CURRENT,
       null as IMAGE
from V$RC_MENUS
where CLUB = :APP_CLUB
start with PID is null
connect by prior ID = PID
order by SEQUENCE, LABEL
The query itself works fine for all values of APP_CLUB but it only generates the menu entries for some values of APP_CLUB, but not others. The SEQUENCE value determines the order of the entries within each level. Is this the correct syntax for a query-based navigation menu? How does it determine which sub-levels belong to a parent? Does the ordering of the resultset have any impact on how the menu is generated?

Jritschel-Oracle wrote:
I'm trying to build a Navigation menu from a query using the following syntax:
select LEVEL,
      LABEL,
      LINK,
      'NO' as IS_CURRENT,
      null as IMAGE
from V$RC_MENUS
where CLUB = :APP_CLUB
start with PID is null
connect by prior ID = PID
order by SEQUENCE, LABEL
The query itself works fine for all values of APP_CLUB but it only generates the menu entries for some values of APP_CLUB, but not others. The SEQUENCE value determines the order of the entries within each level. Is this the correct syntax for a query-based navigation menu? How does it determine which sub-levels belong to a parent? Does the ordering of the resultset have any impact on how the menu is generated?
As stated in the documentation:
...do not specify either ORDER BY or GROUP BY, because they will destroy the hierarchical order of the CONNECT BY results. If you want to order rows of siblings of the same parent, then use the ORDER SIBLINGS BY clause.
Try:
select LEVEL,
      LABEL,
      LINK,
      'NO' as IS_CURRENT,
      null as IMAGE
from V$RC_MENUS
where CLUB = :APP_CLUB
start with PID is null
connect by prior ID = PID
order siblings by SEQUENCE, LABEL

Cosmetic issue in WEBI report while creating on top of BEX query

While Creating WEBI report on tob of BEX Query, it is displaying both Technical names and descriptions at webi design level.
The infoobjects we had used in BEx Query is Navigation Attributes.
In case if we are using normal Infoobjects, we can able to restrict as per my requirement like uniqe name, description or both.
In this webi report user(Power user) having flexibility to drag and drop available characteristics.
Due to this issue column heading is displaying both technical name and description. For example Customer(ZCUSTOMER)

How come , if it is display for data means it also need to be display for header (Dimension also).
you can try alternatively in webi by creating variable for that Iobj .
Refer below blog provide details:
BOBJ Tricks: Toggle the Display of Text and Key in Webi
Regards,
Seshu.P

How to use Navigational attributes in BEx

Hi experts,
I have searched many threads regarding navigational attributes in BEX.
But unable to find any info.
How the navigational attributes are used in BEx query designer.
What is the difference between characteristics and Nav attr in Query designer.
Every one n saying Nav attr are used for drill down purpose.
What exactly is this drill down .
Please send me any related documents also.
Please answer me.
Thanks in advance
Sundar

Hi,
Characteristic attributes can be converted into navigation attributes. They can be selected in the query in exactly the same way as the characteristics for an InfoCube. In this case, a new edge/dimension is added to the InfoCube. During the data selection for the query, the data manager connects the InfoProvider and the master data table (u2018joinu2019) in order to fill the Query.
Navigational attribute is like any other master data attribute except that we can navigate (filter, drill down and selection) in reports on this characteristic.
Drilldown means after you executed the query , you want to see further detailed data with particular combination ,
in that case you navigate further or do restiction that is drilldown.
If you restict a navigational attribute in Query , then it behaves like a normal characteristic and not as a navigation attribute.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a63e7e07211d2acb80000e829fbfe/content.htm
Also check the link:
http://help.sap.com/saphelp_nw70/helpdata/en/43/f234619e3c4c5de10000000a155369/frameset.htm
Regards,
Amit

Querying Data from 3rd Party System

We would like to query data from a 3rd party (non-SAP) system. Our BW is an MSSQL DB and the 3rd party is also an MSSQL DB. We do not want to physically load the data from the external system we just want to use the BW query tools to display the data.
Is this possible? I thought this is what a Remote Cube would be used for but SAP's instructions on Remote Cubes are vague and confusing.
       1.      In BW, create a source system for the external system that you want to use.
       2.      Define the required InfoObjects.
       3.      Load the master data:
·        Create a master data InfoSource for each characteristic
·        Load texts and attributes
       4.      Define the RemoteCube
       5.      Define the queries based on the RemoteCube

Hi Jon,
SAP RemoteCube is an InfoProvider. This is a special RemoteCube that allows
you to define queries with direct access to transaction data in other SAP systems. SAP RemoteCubes are defined on the basis of an InfoSource with flexible updating, and assume the characteristics and key figures of the InfoSource.
Use/Data Flow
Unlike with other RemoteCubes, it is not necessary to program extractors. The
same extractors are used to select data in the source system that are also used when replicating data into the BW. When executing a query, each navigation step sends a request to the extractors for the assigned source systems. In addition, characteristics selection and selection criteria for these characteristics are transformed to fields in the transfer structure, in accordance with the transfer rules. They are transferred to the extractor in this form. The delivered datasets run through the transfer rules in BW and are filtered once again in the query.
In your case Remote cube can be an option .
Cheers
Raja

Currency conversion by Calendar month in the query?

Hellow...
Users want DB currencies when executing query at first. And then want to change currency conversion by Calendar month in the query, if navigating by target currency. Tried as created TEST Currency Translation Key. Database currency is different currencies.
Appreciate your help.
Don.

Hi,
Create Currency conversion type using Trans: RRC1.
1.Specify your Exchange rate type.
2.Dynamic Exchange rate type
3.Source curency from data rec.
4.Fixed currency say USD.
5.Select Variable Time reference "Start Month" and Special Info Object - 0calmonth
Secondly In the key figure field to be converted in the query, select properties - select the currency conversion key name .
Thanks,
Nagesh
Sony Singapore

FRM:41361 Cannot navigate out of form in 'Enter Query Mode'

Hi,
I am using a master - detail block in my form.When I query the master block I am getting this error message
FRM:41361 Cannot navigate out of form in 'Enter Query Mode'
I have given DO_KEY('ENTER-QUERY') in WHEN-NEW-BLOCK-INSTANCE trigger of master block.
and in property palette of Master block I have given the next navigation block as Detail block.
According to the value which is queried in Master Block the Detail block should be populated.
My form should open in 'Enter Query Mode'.This problem always happens from second time onwards
I open the form.When I open the form first time this problem is not occuring.
Can anyone suggest a solution for this
Thanks,
Nasiya

Have you written a Key-EntQuery trigger at the Master block or the form level,
If yes, then can you put that code here.
The NEXT-NAVIGATION-BLOCK is only used for navigation when you use a next-block built-in on a key-trigger.
Have you written a ENTER-QUERY command on any trigger that fires prior to the said WHEN-NEW-BLOCK-INSTANCE trigger?
If yes, then thats the reason that the first time you run the form, your form is in ENTER-QUERY mode.
Also, maybe execute on enter-query fails and hence the blocks are not getting populated.
Also, ENTER-QUERY is always on a single block. And while the block is in enter-query mode, navigation out of that block is prohibited.
you have to either have a successful EXECUTE-QUERY or use:
EXIT_FORM(NO_VALIDATE) to come out of ENTER-QUERY mode.

Is it possible to a "sliding" navigator?

Is it possible to create a navigator on the date that slides with current time? For example, I would like to show the followign navigation options:
Dates:
Past Week
Past Month
Past Year
Thanks,
Kevin

Hi Kevin,
One can create navigators like what you are describing, such as:
All (5000)
today (10)
within a week (50)
within two weeks (110)
within a month (220)
within two months (409)
within six months (1030)
within one year (3030)
within two years (3402)
Typically this has been performed by creating extras field/navigators in the index profile, as well as applying custom logic during document processing
and in the search front-end. Another approach is to use the manual-cut feature for numeric navigators in the index profile, but this requires performing hot updates as often as daily (depending on the desired granularity).
A more optimal solution is to combine manual-cut with query-side navigator options. For instance, the sample query parameter below specifies various
4 buckets (years <=1999, 2000-2004, 2005-2006, >=2007) for 'docdatetimenavigator'
To use manual cut, you can use discretize=manual in the query parameter which will override/ignore intervals, algorithm and range labels are ignored.
For example:
rpf_navigation:navigators=docdatetimenavigator(discretize=manual/3694649208/3695009208) overrides intervals, algorithm and range labels are ignored.
One can also change the default minute specification to seconds by adding the parameter: [datetime-resolution =”seconds”] to the field.
An example of a manual cut navigator definition in index profile would be below:
      <numeric-navigator name="docdatetimenavigator2" display="Timestamp" algorithm="manual" resolution="1440">
      <manual-cut value="3689170560" />
      <manual-cut value="3691801440" />
      <manual-cut value="3692327040" />
      <manual-cut value="3692852640" />
      <field-ref name="docdatetime"/>
    </numeric-navigator>
Thanks!
Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support
Customer Service & Support
Microsoft
| Services

Inconsistencies with Navigation Attributes

Hello all,
We are experiencing some inconsistencies with navigation attributes. Attributes are flagged as navigational on the InfoObject Level and also selected in the InfoProvider's Navigation Attributes folder. However some of them are showing in the Query as Navigation Attributes while other's don't. The same process was followed for all of them. Any ideas why this might happen?
Thank you so much!

Take the "Company", "Area" and "Department" out from the attribute list of the Org Unit !!
then delete "Company", "Area" and "Department" one by one ..
And then try deleting orgunit ..
Regards.

Query Performance Differs

Hi, I have a query with navigation attribute, when I run that query separately in web browser and then try to select a value of nav attribut then it runs fine. But when I try to use that same single query in a web template and then try to select a filter value on the same nav attribute the selection screen window times out and gives the below error.
Its a basic web template, nothing complex. But can't understand why the filter selection screen of the nav attribute differs in performance?
Any ideas?
MS
Edited by: Mark Smith on Sep 24, 2008 9:54 PM

Here is the time out message:
500 Connection timed out
Error: -5
Version: 7000
Component: ICM
Date/Time: Wed Sep 24 19:54:07 2008
Module: icxxthr_mt.c
Line: 2698
Server: slice_BWP_00
Error Tag: {-}
Detail: Connection to partner timed out after 60s

Query in Navigation

Similar Messages

Maybe you are looking for