Navigational attribute in selection screen gives no applicable data

Hi Gurus
In the report i am using the navigational attribute in the selection screen.e.g Brand (attribute of material)
My problem is whenevr i enter value in the navigational attribute (brand) in the selection screen and execute its says no data found.
If i do not fill this parameter and fill only the parent attribute (material) in the selection screen , then i can see the results and from its properties (drilling down )i can see the values of brand .
If the values of brand exist why via selection screen its not giving vales, However Via material i can drill down and see brand values.
I have done all the necessary steps to make this attribute as navigational.
On top of this i have this same navigation attributes as one of the characterisitc in the cube.
Thanks
DD

Hello,
I've the same problem... for new nav. attributes for 0Material.
Settings for nav. attibutes in BEx Q.D. are OK.
But in BEx Analyzer:
1- not display all values for this attributes. Some values are displayed, some don't.
I try display it with and without selection screen. The result is the same.
2- I try to display (normal) attributes - not nav. In this case everything is OK.
But I've 2 columns: normal attribute for all values and nav. attribute only with some values...
(the query is something like: 0Material + 0Material_NOTnav_attr + 0Material_NOTnav_attr)
It isn't a normal...
I don't know... Maybe it's depend of the time?
I can't clear all master data for 0Material, because they're used in some cubes. I had old characteristic without nav. attr. but with master data. I added nav. attr. in 0Material and activated it. Next I load master data (full method). Then I added nav. attr. in infocube, activated it, delete and load data into the cube (Init + Delta).
If I display data for the cube in RSA1, I can see nav. attr. for all records. I can't see it in BEx Analyzer...
Can U explain it?
Thx,
MSzN

Similar Messages

Navigational Attributes as Selection Criteria in Infopackage?

Is it possible to use navigational attributes as selection criteria in the infopackage? I have the MRP cube that only does full loads. I would like to ONLY load the material type FERT (finished goods). 0MATERIAL has 0MATL_TYPE as a navigational attribute. I would like to put 0MATL_TYPE in the selection criteria in the infopackage.
If this is possible, please let me know. The only other way I have come up to do this is to load in one cube and then use and APD to load into another cube. I would like to avoid this if possible.
Thanks,
Brent

Hi there,
you can try this:
create a routine in 0material infoobject.
And put this code in the routine after the part where this appears:
*       Insert source code to current selection field
*$*$ begin of routine - insert your code only below this line        *-*
data: l_idx like sy-tabix.
read table l_t_range with key
     fieldname = 'MATNR'.
l_idx = sy-tabix.
after the *.... delete all the code there and insert this one:
data: i_table like /BI0/PMATERIAL occurs 0 with header line.
data: t_range TYPE rssdlrange.
select * from /BI0/PMATERIAL INTO TABLE i_table
WHERE OBJVERS = 'A' and MATL_TYPE = 'FERT'.
clear t_range.
t_range-IOBJNM = '0MATERIAL'.
t_range-FIELDNAME = 'MATNR'.
t_range-SIGN = 'I'.
t_range-OPTION = 'EQ'.
LOOP at i_table.
    t_range-LOW = i_table-MATERIAL.
    APPEND t_range to l_t_range.
endloop.
p_subrc = 0.
Save it and execute the InfoPackage. It might take a while to execute the infopackage.
Diogo.

Selection screen must show current date + 1

Hi Guys,
In my selection screen i have given
parameters: date like sy-datum default sy-datum.
I have added + 1 after sy-datum.
But i am not getting tommorows date.
So can I display current date = current day + 1 Day in selection screen itself.
Thanks,
Prasad.

parameters: date like sy-datum default sy-datum.
INITIALIZATION.
DATE = sy-datum + 1. " Tommorows date will be display on the selection screen.
OR:
parameters: date like sy-datum default sy-datum.
AT SELECTION_SCREEN OUTPUT.
DATE = sy-datum + 1.
Regards,
Gurpreet

Query varibale - display InfoObject attribute in selection screen

Hi,
At my Query I have a variable for ZSurvey (InfoObject), when I run the report I got the first screen to select a Survey (ZSurvey).
in This Selection Screen I have 2 columns ( Survey number & Description)
How Do I add third Column (Start Time) Which is Attribute in ZSurvey infoobject ( Time Depended)
please help
Thanks

Hi.
Do you want to restrict Start Time by any variable ?
Is Start Time navigational attribute ?
Regards.

Hide display attributes in selection screen?

Hi @ All,
Does anybody knows how I can hide some display attributes of one characteristic in the selection screen in the portal?
For example, I have the characteristic 0plant with the display attribute 0ALTITUDE which I want to hide in the selection screen.
Any ideas?
Thanks!
Stephan

Hi Abhijit,
yes we talking about BW report selection screen
0plant is my input variable in query designer. 0plant is also navigational in the infocube.
0ALTITUDE is an attribute of 0plant. It is not navigational and not input variable in query designer.
Any ideas how I only set some attributes of 0plant visible for the selection screen, and some not?
Thanks,
Stephan

Using navigational attributes in selection for a forecast profile

Hello All,
I could understand that the forecasting can be done on navigational attributes.
But when I goto transaction /SAPAPO/MSDP_FCST2, I could not create a selection on navigational attribute.
Because I could not see the navigational attribute field in the selection screen for selection criteria/profile creation.
Does anyone have any idea of how to do this?
Also I saw the method SEL_CHANGE of BADI /SAPAPO/SDP_FCST5. But the documentation is confusing, since it says that using this method, we could delete the navigational attributes from the selection condition. Could any one suggest me how to use this BADI if I cannot create a selection with navigational attribute?
Thanks,
Suresh

Hi Sunitha,
Thanks a ton for your reply.
The real problem is the OSS note is confusing.
OSS Note for this method says "This method can be used to change the selection to be stored in
in the generated selection table. Navigation attributes can be removed, such as the function of assigning a forecast
profile to the selection can also be allowed for selections with navigation attribute without a basic characteristic."
I am really confused what it says.
If we can't create a navigational attribute for a selection, how could we delete it from a selection?
Thanks,
Suresh

Navigation attribute as selection criteria for automatic forecast model

Hello Experts,
I have a requirement like this.
In Transaction /SAPAPO/MSDP_FCST2, I enter a planning area and click execute.
Then I create a selection (using selection management button). But here I am not able to see the navigational attributes as a selection field.
Could you please let me know how I could use this as a selection criteria?
Can I use the method SEL_CHANGE of the BADI /SAPAPO/SDP_FCST5 for implementing this?
Please suggest.
Thanks,
Suresh

Hi Manimaran,
Thanks for your reply!
I hope you could have created a selection using the Create Activity and assign activity to a job. And during this part, for assigning the selection to the job, we could use the selection created in Interactive planning - Tcode /SAPAPO/SDP94.
The problem is what if the planners are not given authorization for the creating the job or activity. And what if the planners do the model fitting for a product/location and he wants to exclude it from the selection.
Thanks and Best Regards,
Suresh

Calling the selection screen of report with data for the selection field

I have the selection screen with 2 fileds.
sales order and payment terms.
My requirement is to update the payment terms into the ztable for the given order.
Sometimes the payment terms will be there ie already maintained ,in that case i need to show to the user the existing payment term ,so that he can modify and save that one.If the payment term is not existing then simply i can go inside the program and update the payment term.
What I thought of doing is , writing a report program and then after the user inputs the selection screen ie order number , I Will check in the ztable and if the payment terms is found then i will use the key word leave list processing. But i dont know how to populate the payement term in the selection screen oncegaing from the program

Hi shiva,
when the user enters sales order number on screen, in parameter 1,
you want to show payment term, on selection screen itself, in parameter 2.
We can use the event
AT SELECTION-SCREEN.
Eg. PO Number <----
> User
Below is sample code for same.
If you enter PO Number, the system will show the corresponding user in parameter2.
Just copy paste.
REPORT YAM_TEMPA09.
PARAMETERS : EBELN LIKE EKKO-EBELN.
PARAMETERS : ERNAM LIKE EKKO-ERNAM.
AT SELECTION-SCREEN.
ERNAM = ''.
SELECT SINGLE ERNAM
FROM EKKO
INTO ERNAM
WHERE EBELN = EBELN.
regards,
amit m.

In the LDB selection screen -Diff b/w Data selection / person selection

Hi Experts,
Want to know what is the difference between
Data Selection Period
Person Selection Period
in the other period , in the selection screen of the LDB PNP.
Thanx in Advance.
Regards,
IFF

hi,
Please Refer to this link.
[abap hr question;
This will Help You.
Reward if helpful.
Regards
Sumit Agarwal

LDB selection screen -Diff b/w Data selection / person selection period

Hi Experts,
Want to know what is the difference between
Data Selection Period
Person Selection Period
in the other period , in the selection screen of the LDB PNP.
Thanx in Advance.
Regards,
IFF

hi,
Plz follow this link.
Re: Data selection period & Person selection period
This will Help.
Regards
Sumit Agrwal

Will Restricted key figure give no applicable data

Hi,
After the query is run it shows no applicable data.
There is applicable data as far as characterstics and filters are concerned.
But the key figures are restircted ones and there is no data matching that restirction.
But shouldnt the query in that case give the output with the char rows which are present and the key figure column as 0.
Kindly provide pointers to the same.
Thanks & Regards,
Rathy

If there is no data that matches the restrictions on the RKFs, then no data will be displayed. The values are not "0" in this case, they don't exist.
Perhaps an example will clarify...
Let's assume there are 3 RKFs restricted by Calendar Month to 01/2007, 02/2007 and 03/2007. If I request data for a date range including these months, then the appropriate data will be displayed. However, if I request data for 07/2007 -> 09/2007, it would not make sense to show "char rows which are present" for those months with "the key figure column as 0".
However, you can essentially get the result you are looking for by turning off all zero suppression and hiding all of the RKFs.
Hope this helps...
Bob

EDIT PNP Selection screen

Hello
I would like to edit my PNP selection screen (000) with screen painter. Does anyone know if this is possible?
Otherwise is it maybe possible to add tabs to the screen dynamically?
Greets

hi ,
go to the attributes of the program>hr report catagory>then you can create your own selection screen give the name and description...
regards,
venkat.

F4 functionality on selection screen

Hi,
i am having One requirement that need to create f4 functionality on selection screen.
please give me solution on that

Hi,
When you refer your selection screen element to a data element which has a F4 option, then it gives you a F4 help automatically.
If not try using match code objects.
Refer to the below related threads
match code
match code
Match Code
Match code
Matchcodes are defined in two stages in Abap/4 Dictionary:
1) The revelant table and fields are stipulated in matchcode object. A matchcode object describes the set of all possible search paths for a search item.
2) One or more matchcode ID can be defined for a matchcode object. A matchcode ID describes a special search path for a search term.The fields or combination of fields via which the search is to take place is defined in the matchcode ID.
In the initial screen of Data Dictionary,
Enter a name for your new object, click on the Matchcode radio button, and press the Create button.
Enter descriptive text as you enter your primary table on the Attributes screen and press the Save button.
The primary table represents the primary source table for the subsequent field search. Secondary tables can also be maintained at this point by double-clicking on the primary table or pressing the Tables button. These tables must link to the primary table through foreign keys.
The Maintain Matchcode Object attributes screen.
At this point you have the option of creating the matchcode as a local object or attaching it to a transport request. After you have done this, click on the Save button
The Create Object Catalog Entry screen.
As the status bar reflects, the mandatory key fields are transferred automatically .If you want, you can press the Fields button and maintain any selection fields you want. At this point you need to click on the green arrow to go back to the Maintain Attributes screen.
The Maintain Matchcode Object (Fields) screen.
The next step in the creation process is to activate the matchcode object. The status of the object is New and Saved .
The matchcode attributes prior to activation.
The status is now set to Active and Saved. Next you need to create a matchcode ID or your object will be incomplete.
To do this, click the Matchcode IDs button.
The matchcode attributes after activation.
The system will prompt you to create a new ID if one does not exist To do this, click on the Yes button.
A prompt to Create Object.
On the Create Matchcode ID screen , specify a matchcode ID number, valid input ranges from all of the alphabet, and any number. You can also click on the down arrow to view a range of valid entries.
The Create Matchcode ID dialog box.
Let's view some possible entries this list window shows a number of matchcode IDs and a short description of each. Choose one and click on the green arrow.
A Matchcode hit list.
Follow these steps we learned to maintain selection fields for this matchcode ID, be sure to enter an Update type, and click on Save . At this point, you can enter further selection criteria by pushing the Selection Criteria button.
Maintenance of matchcode attributes.
In the Maintain Selection Conditions screen, you can enter and maintain fields and selection criteria for your matchcode IDs. Here is an example of a requirement of a Material Number not greater than the value of 8888 .When finished, click Save and the green arrow to go back.
The Maintenance Selection Conditions dialog box.
Now all you have to do is activate your matchcode ID and your new object is ready to use
Generate and use the matchcode.
Reward if helpful.
Regards,
Narendra.

Call Selection Screen

Hi,
can any one give me good links for
All variants of at selection screen..
some thing on call selection screen
Thx,
Shashi

·     AT SELECTION-SCREEN
You should only perform very expensive checks with AT SELECTION-SCREEN if the program is then started. Here, you can read the system field SSCRFIELDS-UCOMM (provided a statement TABLES SSCRFIELDS exists). If the field has one of the values 'ONLI' (= Execute) or 'PRIN' (= Execute and Print), the report is then started, i.e. the selection screen is closed and the processing continues with START-OF-SELECTION.
     Additions:
·     ... ON psel
Effect
This event is assigned to the selection screen fields corresponding to the report parameter or selection criterion psel.
If the report starts an error dialog at this point, precisely these fields become ready for input.
·     ... ON END OF sel
          For each selection criterion sel on the selection screen, you can call a further screen by pressing a pushbutton. On this screen, you can enter any number of single values and ranges for the selection criterion sel..
When this screen has been processed (i.e. at the end of PAI for this screen), the event AT SELECTION-SCREEN ON END OF sel is executed.
At this point, all the values entered are available in the internal table sel.
·     ... ON VALUE-REQUEST FOR psel_low_high
Effect
In this addition, the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH, where sel is the name of a selection criterion. The effect of this is twofold:
1.     The possible entries pushbutton for F4 appears beside the appropriate field.
2.     When the user activates this pushbutton or presses F4 for the field, the event is executed. You can thus implement a self-programmed possible entries routine for the input/output fields of the selection screen. If the program contains such an event and the user presses F4, the system processes this rather than displaying the check table or the fixed values of the Dictionary field.
·     ... ON HELP-REQUEST FOR psel_low_high
Effect
As with the addition ON VALUE-REQUEST the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH, where sel is the name of a selection criterion. When the user presses F1 on the relevant field, the subsequent processing block is executed. You can thus implement a self-programmed help for the input/output fields of the selection screen. If the program contains such an event and the user presses F1, the system processes this rather than displaying the documentation of the Dictionary field - even if the report parameter or the selection option with LIKE or FOR points to a Dictionary field.
·     ... ON RADIOBUTTON GROUP radi
Effect
This event is assigned to the radio button groups on the selection screen defined by PARAMETERS par RADIOBUTTON GROUP radi. If the report starts at an error dialog at this point ,precisely these fields of the radio button group
radi become ready for input again.
·     ... ON BLOCK block
Effect
This event is assigned to the blocks on the selection screen defined by SELECTION-SCREEN BEGIN/END OF BLOCK block. If the report starts at an error
dialog at this point, precisely these fields of the block block become ready for input again.
     The events assigned to the radio button groups are executed according to the first parameter of the radio button group.
The events assigned to the blocks are executed "from the inside to the outside".
·     ... OUTPUT
Effect
This event is executed at PBO of the selection screen every time the user presses ENTER - in contrast to INITIALIZATION. Therefore, this event is not suitable for setting selection screen default values. Also, since AT SELECTION-SCREEN OUTPUT is first executed after the variant is imported (if a variant is used) and after adopting any values specified under SUBMIT in the WITH clause, changing the report parameters or the selection options in AT SELECTION-SCREEN OUTPUT would destroy the specified values. Here, however, you can use LOOP AT SCREEN or MODIFY SCREEN to change the inout/output attributes of selection screen fields.
·     ... ON EXIT-COMMAND
Effect
This event is executed at the exit command of the selection screen - that is, at Back, Cancel, or End,events executed after the screen is sent that do not cause the system to check the input and execute the PAI.
plz reward if useful
vivek

At Selection-screen Events!

Hi!
Pls tell me the order of selection screen events in sequence
Pls give some sample program for validation of selection screen i/p without using search helps.
Thanks

Hi Rahul
Basic form
AT SELECTION-SCREEN.
Additions
1. ... ON psel
2. ... ON END OF sel
3. ... ON VALUE-REQUEST FOR psel_low_high .
4. ... ON HELP-REQUEST FOR psel_low_high
5. ... ON RADIOBUTTON GROUP radi
6. ... ON BLOCK block
7. ... OUTPUT
Effect
This event only makes sense in reports, i.e. in programs set to type 1 in the attributes. Type 1 programs are started via a logical database and always have a selection screen where the user can specify the database selections.
The event is processed when the selection screen has been processed (at the end of PAI ).
If an error message ( MESSAGE Emnr ) is sent during the event, all fields on the selection screen become ready for input.
After further user input, AT SELECTION-SCREEN is executed again.
Note
You should only perform very expensive checks with AT SELECTION-SCREEN if the program is then started (not every time the user presses ENTER). Here, you can read the system field SSCRFIELDS-UCOMM (provided a statement TABLES SSCRFIELDS exists). If the field has one of the values 'ONLI' (= Execute) or 'PRIN' (= Execute and Print), the report is then started, i.e. the selection screen is closed and the processing continues with START-OF-SELECTION . Remember that the selection screen (and thus also AT SELECTION-SCREE N ) is also processed in variant maintenance and with SUBMIT VIA JOB . You can determine which of these applies by calling the function module RS_SUBMIT_INFO .
Addition 1
... ON psel
Effect
This event is assigned to the selection screen fields corresponding to the report parameter or selection criterion psel .
If the report starts an error dialog at this point, precisely these fields become ready for input.
Addition 2
... ON END OF sel
Effect
For each selection criterion sel on the selection screen, you can call a further screen by pressing a pushbutton. On this screen, you can enter any number of single values and ranges for the selection criterion sel .
When this screen has been processed (i.e. at the end of PAI for this screen), the event AT SELECTION-SCREEN ON END OF sel is executed.
At this point, all the values entered are available in the internal table sel .
Addition 3
... ON VALUE-REQUEST FOR psel_low_high
Effect
With this addition, the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH , where sel is the name of a selection criterion. The effect of this is twofold:
The pushbutton for F4 (Possible entries) appears beside the appropriate field.
When the user selects this pushbutton or presses F4 for the field, the event is executed. You can thus implement a self-programmed possible entries routine for the input/output fields of the selection screen. If the program contains such an event and the user presses F4 , the system processes this rather than displaying the check table or the fixed values of the Dictionary field - even if the report parameter or the selection option with LIKE or FOR points to a Dictionary field. You can, for example, use the CALL SCREEN statement to display a selection list of possible values. The contents of the field psel_low_high at the end of this processing block are copied to the appropriate input/output field.
This addition is only allowed with report-specific parameters (PARAMETERS ) or selection options (SELECT-OPTIONS ). For database-specific parameters or selection options, you can achieve the same effect by using the addition VALUE-REQUEST FOR ... with the key word PARAMETERS or SELECT-OPTIONS in the include DBxyzSEL (where xyz = name of logical database). In this case, you must program the value help in the database program SAPDBxyz .
Addition 4
... ON HELP-REQUEST FOR psel_low_high
Effect
As with the addition ON VALUE-REQUEST the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH , where sel is the name of a selection criterion. When the user presses F1 on the relevant field, the subsequent processing block is executed. You can thus implement a self-programmed help for the input/output fields of the selection screen. If the program contains such an event and the user presses F1 , the system processes this rather than displaying the documentation of the Dictionary field - even if the report parameter or the selection option with LIKE or FOR points to a Dictionary field.
This addition is only allowed with report-specific parameters (PARAMETERS ) or selection options (SELECT-OPTIONS ). For database-specific parameters or selection options, you can achieve the same effect by using the addition HELP-REQUEST FOR ... with the key word PARAMETERS or SELECT-OPTIONS in the include DBxyzSEL (where xyz = name of logical database). In this case, you must program the help in the database program SAPDBxyz .
Addition 5
... ON RADIOBUTTON GROUP radi
Effect
This event is assigned to the radio button groups on the selection screen defined by PARAMETERS par RADIOBUTTON GROUP radi .
If the report starts an error dialog at this point, precisely these fields of the radio button group radi become ready for input again.

Addition 6
... ON BLOCK block
Effect
This event is assigned to the blocks on the selection screen defined by SELECTION-SCREEN BEGIN/END OF BLOCK block .
If the report starts an error dialog at this point, precisely these fields of the block block become ready for input again.
Note
In which sequence are the events AT SELECTION-SCREEN ON psel ... , AT SELECTION-SCREEN ON RADIOBUTTON GROUP ... , AT SELECTION-SCREEN ON BLOCK ... , AT SELECTION-SCREEN processed?
The AT SELECTION-SCREEN ON psel ... events assigned to the parameters or selection options are executed in the sequence they are declared in the program, i.e. in the sequence they appear on the selection screen.
The events assigned to the radio button groups are executed according to the first parameter of the radio button group.
The events assigned to the blocks are executed "from the inside to the outside".
Example
SELECT-OPTIONS SEL0 FOR SY-TVAR0.
SELECTION-SCREEN BEGIN OF BLOCK BL0.
SELECT-OPTIONS SEL1 FOR SY-TVAR1.
SELECTION-SCREEN BEGIN OF BLOCK BL1.
PARAMETERS P0 RADIOBUTTON GROUP RADI.
PARAMETERS P1 RADIOBUTTON GROUP RADI.
SELECTION-SCREEN BEGIN OF BLOCK BL2.
PARAMETERS P3.
SELECTION-SCREEN END OF BLOCK BL2.
SELECT-OPTIONS SEL2 FOR SY-TVAR2.
SELECTION-SCREEN END OF BLOCK BL1.
SELECTION-SCREEN END OF BLOCK BL0.
Sequence:
AT SELECTION-SCREEN ON...
SEL0
SEL1
RADIOBUTTON GROUP RADI
P3
BLOCK BL2
SEL2
BLOCK BL1
BLOCK BL0
AT SELECTION-SCREEN is executed at the very end.
Addition 7
... OUTPUT
Effect
This event is executed at PBO of the selection screen every time the user presses ENTER - in contrast to INITIALIZATION . Therefore, this event is not suitable for setting selection screen default values. Also, since AT SELECTION-SCREEN OUTPUT is first executed after the variant is imported (if a variant is used) and after adopting any values specified under SUBMIT in the WITH clause, changing the report parameters or the selection options in AT SELECTION-SCREEN OUTPUT would destroy the specified values.
Here, however, you can use LOOP AT SCREEN or MODIFY SCREEN to change the input/output attributes of selection screen fields.
Example
Output all fields of the
SELECT-OPTION NAME
highlighted:
SELECT-OPTIONS NAME FOR SY-REPID MODIF ID XYZ.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
 CHECK SCREEN-GROUP1 = 'XYZ'.
 SCREEN-INTENSIFIED = '1'.
 MODIFY SCREEN.
ENDLOOP.
The addition MODIF ID XYZ to the key word SELECT-OPTIONS assigns all fields of the selection option NAME to a group you can read in the field SCREEN-GROUP1 . At PBO of the selection screen, all these fields are then set to highlighted.

check these links
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
Reward all helpfull answers
Regards
Pavan

Navigational attribute in selection screen gives no applicable data

Similar Messages

Maybe you are looking for