About selection in the table
hi,
I select multi record in table, but i don't want to use the 'Ctrl' or 'Shift'.
Thanks a lot!
hi pei.....
In the table property, you have an option called "rowselectable". just check it and the "selectionmode" as multi. Now you will be able to select multiple rows without using ctrl or shift.
---regards,
alex b justin
Similar Messages
-
Record selected in the table control
Hi All,
How do i know the line no of the record selected in the table control.I have declared a table control CONTROLS : t_control1 type tableview using screen 200.But in t_control1-current_line the line no that is stored is always 1.
Thanks,
Rakesh.in table control property window you have to set that suppose you have set itab-mark as the sel field then it will always be X if you select the field ...
regards
shiba dutta -
Contextual Event on row selection in the table
Hi,
My taskflow has just a view activity which queries a view object and displays results as a table. This taskflow is inserted in the main page as a region. I have set up a selection listener on the table, to map to a method in a managed bean. I have made this method binding a producer of my contextual event. and another method binding on the main page as a consumer. I have mapped producer and the consumer on a event map on the main page.
My problem is when a row is selected in the table, I see the method (in the selection listener) is called but the event is not fired and the consumer method is not called. I don't know, if it is because the producer method (selection listener) takes SelectionEvent as a parameter?.
I added just to test, a button on my view activity and mapped the action listener to another method(with out parameters) on the same managed bean and made this a producer. In this situation the event got fired and the consumer method got called.
Why is the selection listener method not firing the event?
Thanks in advance.Hi,
the two events that are supported for ADF Faces component events are ActionEvent and ValueChangeEvent. So if you have a selection event, you need to take this infromation and create an ActionEvent from it.
http://java.sun.com/javaee/javaserverfaces/1.2/docs/api/javax/faces/event/ActionEvent.html
Frank -
I want to know what InputField is selected in the table
Hi Experts
Please help me
I have table with 4 columns (each column have TableCellEditor of type InputField)
I need to know what InputField is selected in the table(or in wich column)Hi,
You can get the selcted row for the table but not for a particular column. Even if you are editing something your input field the complete row would be selected.
Regards,
Murtuza -
Hi,
Our senerio is as follows:
We need to capture the single selection in the table.
There are three options:
1. No element in the Table(no selection).
2. single selection(one row selected).
3. multiple selection(more than one row selected).
How can we code to differentiate all these??
regards
AnumitHi,
I guess you need some thing as follows
WDTableSelectionMode mode ; //An attribute which is buund to the table selection mode property
if( mode.equals(WDTableSelectionMode.MULTI))
//Do respective
else if( mode.equals(WDTableSelectionMode.SINGLE))
//Do respective
else
//Do respective
Regards
Ayyapparaj -
Keep view in row selected in the table
Hello,
i have a webdynpro view with a table. This table has 256 records, and visibleRowCount property is set to 10 records.
My problem is when i selected the record number 174 for example, the scroll table returns to position 1 and i can not see the record selected.
How can i do for the scroll table keep the row selected in the table?
Thank youHi,
Try this.
1. create one context ctx_va_firstvisblerow.
2.get the leadselection record and set ctx_va_firstvisblerow context.write this code in wdDoModifyView.and also following code in wdDoModifyView.
IWDTable table = (IWDTable) view.getElement("Ur table id");
table.setFirstVisibleRow(wdContext.currentContextElement().getCtx_va_visiblerow());
3.Bind the ctx_va_firstvisblerow context to the table FirstVisibleRow.
Thanks
Abhilasha
Edited by: Abhilasha Dahare on Sep 14, 2010 3:35 PM -
Urgent. . .About select * from multiple tables
When I am doing the 'Select * from tables' in JSP,
sql = dbconn.prepareStatement("SELECT * FROM protein WHERE protein_id ='"+p_i+"'");
It works, because I only select one table.
Then, I change to select from two tables,
sql = dbconn.prepareStatement("SELECT * FROM protein, fuses WHERE protein_id ='"+p_i+"'");
It also works properly?
However, When I do like:
sql = dbconn.prepareStatement("SELECT * FROM protein, protein_taxa WHERE protein_id ='"+p_i+"'");
It doesn?t work.
So, I think it might be the problem that there is a common column 'protein_id' in both tables, although protein_taxa.protein_id is a foreign key of protein.protein_id. Therefore, I can select two table protein, fuses which have different columns, but no way to select the table they have same name column.
However, it?s essential for me to select all the data from the database. Any way I could achieve it? Thanks a lot!!SELECT *
FROM protein, protein_taxa
WHERE protein.protein_id = 'a_protein_id'
and protein.protein_id = protein_taxa.protein_id It would also be good to indicate which fields you want on the select clause. This will liberate the server to return two fields with the same name.
SELECT protein.protein_id, protein.name, protein_taxa.taxa /* ??? */
FROM protein, protein_taxa
WHERE protein.protein_id = 'a_protein_id'
and protein.protein_id = protein_taxa.protein_id -
How do we capture the record selected in the table control?
Hi,
In the table control when the user selects a record we need to capture that record and pass it to the next screen.how can we do this?
Thanks,
Rakesh.Hello
First of all you need a 'mark' column in your TC structure.This should be char1.
This column has to be put into the TC Attributes as mark column.
Then to get back the info from the TC go the following way:
PAI
loop at <fs_it> . "Field symbol of your table.
MODIFY <fs_it> FROM wa_basic
INDEX tc_maintenance-current_line.
endloop.
Message was edited by:
Werner Gerbert -
Newbie question - parameter selection -- update the table - basic flow?
Greetings
Newbie here trying to work my way through a 'simple' example for a demo.
I'm currently using a workspace on the Apex web site and have uploaded a table with seven (7) columns of which the first three (3) make up the primary key. This is a copy of an actual Production table so I can't change the PK setup.
What I'm trying to develop as a demonstration of OAE is a Page 1 parameter form that allows the user to input any portion of any or all of the PK values, press the GO button and have Page 2 be a multi-row form showing the results based on the values input on Page 1 and having the user be able to update any of the remaining non-PK columns. After pressing an 'Apply Changes' button to perform the update the user will press a 'New Query' button and go back to Page 1 with the original values cleared out.
It sounds pretty straight forward but I know the 3-column PK creates some headaches.
What I'd like is some guidance on what types of pages I need to create and how to clear out the parameter values.
I was able to create a page with the parameters on it and get them assigned to the session variables but was not able to create the 2nd page that would even just report on the data based on the input parameters.
I don't need the user to be able to add or delete rows, just update existing ones to correct data values.
I'm continuing to go through the documentation and manuals but a little nudge in the right direction would certainly help.
Many thanks for sharing your experiences.
-garyHi Ben and any others who elect to reply:
Thanks to your guidance I've made some good progress. I have been able to create a parameter form that will accept part or all of my three (3) PK columns and put those in session variables. a 'GO' button is pressed and the 2nd page comes up which is based on a SQL query using the session variables from the first page and displays multiple rows of data. It even shows the correct data!
I also modified the non-PK column attributes to make them updatable, at least I can over-type what shows up.
The issue I'm struggling with now is how to get the COMMIT to happen to the database. I have an 'APPLY CHANGES' button on my report page and I thought I was relating that to a simple 'COMMIT' PL/SQL page process, but nothing gets committed.
Do I need to code a manual version of a multiple row update (MRU)?
If so, how do I do that?
If not, what basic piece of understanding am I missing?
Many thanks for your help.
-gary -
What is the table for query name
Hi All,
I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
Thanks,
Alex.hi Alex,
try RSRREPDIR, RSZCOMPDIR.
there is one oss note all the tables.
Table containing Work Book and query relation
Query Detailes
oss 792779
Symptom
Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
The program is recommended for BW system administrators.
Other terms
Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
Reason and Prerequisites
ATTENTION: the described version of the program is delivered with the following Support Packages:
SP27 for release BW 3.0B
SP21 for release BW 3.1C
SP13 for release BW 3.5
All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
Check prerequisites
Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
Checks for query elements in 'D' version are possible only in the systems which are set as content.
Checks description
Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
1. Table RSRREPDIR
The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
The following errors can be found:
- queries with missing definition;
- queries with missing GENUNIID;
- queries with technical names different than in RSZCOMPDIR;
- non-queries in the table.
1.1 Queries with missing definition
The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
1.2 Queries with missing GENUNIID
Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
1.3 Queries with technical names different than in RSZCOMPDIR
The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
1.4 Non-queries in the table
The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
2. Table RSZCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
The following errors can be found:
- local elements in RSZCOMPIC;
- components with inconsistent definition;
- components based on non-existing InfoProviders;
- components based on non-active InfoProviders.
2.1 Local elements in RZSCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
2.2 Components with inconsistent definition
The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
2.3 Components based on non-existing InfoProviders
Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
2.4 Components based on non-active InfoProviders
Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
The check is available only for the query elements in object version 'A' (active).
3. Table RSZCOMPDIR
The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
The following errors can be found:
- duplicated technical names (COMPID);
- components with inconsistent definition;
- components without InfoProvider assignment;
- components with missing OWNER.
3.1 Duplicated technical names (COMPID)
The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
different queries are available in BEX Analyzer and RSRT under the same name;
wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
replacement of variables does not work... etc.
The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
3.2 Components with inconsistent definition
Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.3 Components without InfoProvider assignment
All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.4 Components with empty ONWER field
Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
4. Table RSZELTXREF
The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
The following errors can be found:
- missing elements (INCONSISTENCY dump);
- not supported relations between query elements;
- extended RSZELTXREF check.
4.1 Missing elements
Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
4.2 Not supported relations between query elements
Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
4.3 Extended RSZELTXREF check
The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
- records with empty INFOCUBE field
- records which are not used in any query or query component
Records with empty INFOCUBE field
The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
Records which are not used in any query or query component
The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
records used in existing queries or query components with empty INFOCUBE field;
records used in existing queries or query components with wrong INFOCUBE assignment;
records with or without INFOCUBE assignment which are not used in any query or query component.
For further check details read the OSS note 859086.
5. Table RSZGLOBV
The table RSZGLOBV contains the definitions and technical properties of the variables.
The following errors can be found:
- variables with inconsistent definition;
- variables with missing or incorrect properties;
5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
5.2 Variables with missing or incorrect properties
Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
6. Table RSZELTDIR
The table RSZELTDIR is the main directory table containing all query elements available in the system.
ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
The following errors can be found:
- local elements not in use;
- reusable elements not in RSZCOMPDIR table;
- reusable elements not in RSZCOMPIC table;
- structure (STR) without structure members;
- selections or RKF without definition in RSZSELECT table;
- formulas or CKF without definition in RSZCALC table;
- variables (VAR) without definition in RSZGLOBV table;
- queries (REP) without entries in RSRREPDIR table.
6.1 Local elements not in use
Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
6.2 Reusable elements not in RSZCOMPDIR table
Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
6.3 Reusable elements not in RSZCOMPIC table
Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
6.4 Structures (STR) without structure members
Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
6.5 Local selection of RKFs without records in RSZSELECT table
Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
6.6 Local formulas of CKFs without records in RSZCALC table
Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
6.7 Variables without records in RSZGLOBV table
Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
6.8 Queries without records in RSRREPDIR table
Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
hope this helps. -
How to have both Single and Mutilple Selection in a table?
Hi ,
I have a page with an advanced, there is a multiple selection for the table for deleting row. Now I want to have a single selection column for other purpose. But it does not seem that we can have both in a table.
If I implement SingleSelection myself by using OAMessageRadioButton, from dev guide, I need to programmatically assign radio btton all the same
name by calling setName() for each radio button and also assign an identifying value for each bean. I can radio for radio button, but how can I assign value for each radio button bean when they are in a table? Will it possible to use View Attribute of radio button bean property?
thanks
LeiLei, its possible to have both in ur table! You can add a single selection child to your table. Then u can add messagecheckbox as last column of table, which can be attached to a transient VO attribute.
--Mukul -
Error while importing the tables from MySQL using the data source connection
Hi,
I am trying to import tables from MySQL into Powerpivot using the data source connection, if use the import using the Query option its working fine but not with the select list of table option.
when i click on the select list of tables option, i get the below error after selecting all the tables to be imported:
OLE DB or ODBC error.
An error occurred while processing table 'XXXXXXXXXX'.
The current operation was cancelled because another operation in the transaction failed.Hi Bharat17an,
Please provide the detail information when create the MySQL connection in your PowerPivot model. Here is a good article regarding "how to Use MySQL and Microsoft PowerPivot Together" for your reference, please see:
http://www.datamensional.com/2011/09/how-to-use-mysql-and-microsoft-powerpivot-together-2/
If this issue still persists, please help to collection windows event log information. It maybe helpful for us to troubleshoot this issue.
Regards,
Elvis Long
TechNet Community Support -
Select from nested table in a nested table security problem
please help
running Oracle 9.2.0.3.0 on RH AS 2.1
I can select the inner most nested table as the creator, but can't use the same select statement as USER2.
ORA-00942: table or view does not exist
-- begin make of objects and tables
create or replace type mydata_t as object ( x float, y float);
create or replace type mydata_tab_t as table of mydata_t;
create or replace type mid_t as object (
graphname varchar2(12),
datapoints mydata_tab_t );
create or replace type mid_tab_t as table of mid_t;
create or replace type top_t as object (
someinfo int,
more_mid mid_tab_t );
create table xyz (
xyzPK int,
mainstuff top_t )
nested table mainstuff.more_mid store as mid_nt_tab
(nested table datapoints store as mydata_nt_tab)
-- grants
grant all on mydata_t to user2;
grant all on mydata_tab_t to user2;
grant all on mid_t to user2;
grant all on mid_tab_t to user2;
grant all on top_t to user2;
grant all on xyz to user2;
-- insert
insert into xyz values (1, top_t(22,mid_tab_t(mid_t('line1',mydata_tab_t(
mydata_t(0,0),
mydata_t(15,15),
mydata_t(30,30))))));
commit;
-- select fails as user2
select * from table(select Y.datapoints as DP_TAB
from table(select X.mainstuff.more_mid as MORE_TAB
from scott.xyz X
where X.xyzPK=1) Y
where Y.graphname='line1') Z;
-- select works as user2, but i need individual lines
select Y.datapoints as DP_TAB
from table(select X.mainstuff.more_mid as MORE_TAB
from scott.xyz X
where X.xyzPK=1) Y
where Y.graphname='line1';Thank you for your reply.
I have tried
select value(t) from table t;
but it is still not working. I got almost the same answer as before.
Anyway thank you very much again.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by MARCELO OCHOA ([email protected]):
Originally posted by meimei wu ([email protected]):
[b]I created a nested object-relational table using REF type in oracle8i. when I tried to select * from the table, I got lots of number as the ref type values, but actually, the value in ref type should be of type varchar2 and number. The number I got looked like following code:
JARTICLE_REF_TYPE(000022020876108427C2FE0D00E0340800208FD71F76103B99B12009C0E0340800208FD71F,
Does anyone know how I can get the actual value that I inserted into the nested table?
your help is appreciated.<HR></BLOCKQUOTE>
Try this:
select value(t) from table t;
Best regards, Marcelo.
null -
How to edit a particular row in the table ctrl when a push button is clickd
Hi Experts,
How to edit a particular row (except the Primary keys) after selecting it in the TABLE CONTROL when a
push button is clicked in the table control.
For Eg. If you have a push button say "Modify", the particular row what we select in the table control should be in a
editable mode after clicking "Modify" Push button.
Please help me out.
Thanks in advance.Hey Ram,
Thanks a ton.
Its working fine...sorry for the late reply.
The reason behind the delay is because i had modified my code as per your logic it worked fine but the thing is that the whole column was in editable mode but not a single row.
For E.g If i want to edit a particular row, first i select the row and then click on "Modify" button. After i click on the button, the whole column gets in a editable mode including the one which i intentionally selected.
Here, the solution is that you have to set a flag in PBO so that once it is done with PBO then it need not come back again after we click on "Modify" button.
And one more query is that after you modify a particular row in the table control ( When it is in editable mode) and click on the "Save" button, it is not getting updated to database.
To update the database, we need to select the row once again after modifying it and click on the "Save" button.
Here, database is updating only when it is selected again. If it is not selected, it is not getting updated.
If you have any alternative solution, then please help me out.( I hope i am clear with the question.)
Thanks,
Ananth. -
How to perform Autosubmit on Row selection in ADF Table
Hi,
I am using ADF Table , in which I want to enable AutoSubmit for the Table Row Selection.
I want to enable some button on my screen when a row is selected in the table.
I want to achive this with out using SelectionListener .. any iputs for this?
Thanks,
SwathiHi Timo,
here is my code : this code is to implement Custom shuttle .. where I am using two ADF Tables to display the Available list and Selected List ..and using navigation buttons to move the selected item.When I select a Row in the left table .. I want to enable the 'add' button.
<af:table value="#{pageFlowScope.ebean.al}" var="row"
rowBandingInterval="0" varStatus="vs" id="t2"
rowSelection="single"
binding="#{pageFlowScope.ebean.availableList}"
partialTriggers="::cb2 ::cbAdd ::cbRemove"
summary="#{backingBeanScope.BundleBean.MEASURES}"
selectionListener="#{pageFlowScope.ebean.rowSelection}"
inlineStyle="height:200.0px;" horizontalGridVisible="false">
<af:column sortProperty="Name" sortable="false"
headerText="Name"
id="c3" width="300" rowHeader="unstyled">
<af:panelGroupLayout id="pgl6">
<af:image source="/images/file_ena.png" id="i2"
shortDesc="#{backingBeanScope.BundleBean.FILE_ENA}"/>
<af:outputText value="#{row.label}" id="ot2"/>
</af:panelGroupLayout>
</af:column>
</af:table>
</af:panelGroupLayout>
<af:panelGroupLayout id="pgl3" layout="vertical"
inlineStyle="width:39px;">
<af:commandButton id="cbAdd"
actionListener="#{pageFlowScope.ebean.onAdd}"
partialSubmit="true"
disabled="#{pageFlowScope.ebean.dataToAdd==null}"
icon="/images/shuttleright_ena.png"
shortDesc="#{backingBeanScope.BundleBean.ADD}"
partialTriggers="t2"/>
<af:spacer width="10" height="10" id="s1"/>
<af:commandButton id="cbAddAll" action="addAll"
actionListener="#{pageFlowScope.ebean.onAddAll}"
disabled="#{pageFlowScope.ebean.availableListSize==0}"
icon="/images/shuttlerightall_ena.png"
shortDesc="#{backingBeanScope.BundleBean.ADD_ALL}"
partialTriggers="cbRemove"/>
<af:spacer width="10" height="10" id="s2"/>
<af:commandButton id="cbRemove" partialSubmit="true"
actionListener="#{pageFlowScope.ebean.onRemove}"
icon="/images/shuttleleft_ena.png"
shortDesc="#{backingBeanScope.BundleBean.REMOVE}"
partialTriggers="t3"
disabled="#{ pageFlowScope.ebean.dataToRemove==null}"/>
<af:spacer width="10" height="10" id="s4"/>
<af:commandButton id="cbRemoveAll"
actionListener="#{pageFlowScope.ebean.onRemoveAll}"
icon="/images/shuttleleftall_ena.png"
shortDesc="#{backingBeanScope.BundleBean.REMOVE_ALL}"
disabled="#{pageFlowScope.ebean.listSize==0}"
partialTriggers="cbAdd "/>
</af:panelGroupLayout>
<af:panelGroupLayout id="pgl5">
<af:outputText value="#{backingBeanScope.BundleBean.SELECTED_MEASURES}#{pageFlowScope.ebean.listSize}#{backingBeanScope.BundleBean.CB}"
id="ot3"
inlineStyle="font-weight:bold; font-size:small;"
partialTriggers="cbAdd cbRemove"/>
<af:table value="#{pageFlowScope.ebean.sl}" var="row"
rowBandingInterval="0" varStatus="vs" id="t3"
rowSelection="single"
binding="#{pageFlowScope.ebean.list}"
partialTriggers="::cbAdd ::cbAddAll ::cbRemove ::cbRemoveAll"
summary="#{backingBeanScope.BundleBean.MEASURES}"
selectionListener="#{pageFlowScope.ebean.rowSelection}"
inlineStyle="height:200.0px;" horizontalGridVisible="false">
<af:column sortProperty="Name" sortable="false"
headerText="Name"
id="c5" width="300" rowHeader="unstyled">
<af:panelGroupLayout id="pgl9">
<af:image source="/images/file_ena.png" id="i3"
shortDesc="#{backingBeanScope.BundleBean.FILE_ENA}"/>
<af:outputText value="#{row.label}" id="ot1"/>
</af:panelGroupLayout>
</af:column>
</af:table>
</af:panelGroupLayout>
public void rowSelection(SelectionEvent selectionEvent) {
RichTable at = (RichTable)selectionEvent.getComponent();
if(at.getId().equals("t2"))
getDataToAdd();
else
getDataToRemove();
public Object getDataToAdd(){
if(availableList!=null)
return availableList.getComponent().getSelectedRowData();
return null;
public Object getDataToRemove() {
if (list != null && list.getComponent().getSelectedRowKeys()!=null)
return list.getComponent().getSelectedRowData();
return null;
}Thanks,
Swathi
Maybe you are looking for
-
I need a copy of the key code to use the product. It has stopped working.
-
I have experiencing irregularities with the vertical spacing of images in different browsers. I am working on an iMac 10.4.11. The site looks as I intended it to read while in Safari, but when opened in Firefox the text-based navigation bar which run
-
Hiding the submit button on click
Hi All, I have a req where i have 4 buttons which displays some info on the same page when clicked. if i click on button 1, button1 should not be displayed after clicking, if i click on button 2, button2 should not be displayed. I tried this using se
-
SUNOPSIS to ODI migration : AS/400 error in work repository upgrade
Hi, We're migrating SUNOPSIS v3.2.02.19 to ODI 10.1.3.5.0, with repositories on DB2 AS/400. We achieve to migrate master repository without any problem, and we try now to migrate the work repository and we have the following error : +java.sql.SQLExce
-
Hi, I have some issues with cookies on my Safari (Version 4.0.5 (6531.22.7), Mac OS X 10.6.3): document.cookie = "ONE=" + new Array(3000).join("a") + "; path=/"; document.cookie = "TWO=" + new Array(3000).join("b") + "; path=/"; console.log(document.