MSS custom query restrictions (table/view/join)

Dear all,
We are currently trying to integrate a sap query which also gathers data from event management. This query is based on an infoset and a table view and not on a logical database.
When executing the query within the portal (generictableview iview) we get the error message "No data records found". While debugging the function module HR_INFO_GET_USING_QUERY which is called here we found out that the error message is generated because no logical database is retrieved.
Therefore my question is: are mss queries in portal restricted to queries which are based on logical databases only or can we create and use queries in portal which are based on table/views/joins?
Any help on this issue is greatly appreciated!
Thanks already very much in advance,
Helga

Hello MIG,
I am still searching and I have not found a solution yet.
Interestingly enough the query can be executed without any problems in R/3 but not from the portal iView. Therefore I am wondering if it is only a restriction on the MSS side.
@forum users: did anyone of you face this problem and has a solution to it?
Thanks very much for any input on this!
Kind regards,
Helga

Similar Messages

Adding custom fields to table view assignment block

Hi All,
I want to add two news fields to 'Service Contract Item Level' in 'Object List' assignment block. How can i add these two custom fields to table view assignment block using AET. I have tried to add new fields using AET but there is no business object supports to my requirement.
Thanks & Regards
Nitish

Hi Nitish,
As naveen sadid use Cutomer_i object . I guess it will be more appropriate.
And following link will be helpful for AET creation.
CRM 7.0 How to --4 Adding Custom Fields With The New Application Enhancement Tool (AET)
Regards
Loks

Query in table view -filter.

hi,
    i have one probs. for using the filter in the tableview.
   These r the following code i used.
    <%
      data: columnDefinitions type TABLEVIEWCONTROLTAB,
              wa                type TABLEVIEWCONTROL.
        data filters type tableviewFilterTab.
        field-symbols: <filter> like line of filters,
                       <wa>     type IHTTPNVP2.
        append initial line to filters assigning <filter>.
        <filter>-columnName = 'connid'.
i want to fetch all connid value from DB in the dropdownlistbox ,insteed of giving manually.here manually i am giving the value to the dropdownlistbox.
i tryed in some ways,but still i am not getting.
can any one help me to sole the probs.
        append initial line to <filter>-dropdownlistbox table assigning <wa>.
        <wa>-name = '*'.
        <wa>-value = '*'.
        append initial line to <filter>-dropdownlistbox_table assigning <wa>.
        <wa>-name = '0820'.
        <wa>-value = '0820'.
%>
   <htmlb:tableView    id            = "tv2"
                       headerText    = "Books that match your query"
                       headerVisible = "true"
                       footerVisible = "false"
                       design        = "ALTERNATING"
                       visibleRowCount = "30"
                       filter           = "server"
                       sort             = "server"
                       columnFilters     = "<%=filters%>"
                       onRowSelection = "MyEventRowSelection"
                       selectionMode = "SINGLESELECT"
                       table         = "<%= itab %>" >
with regards,
ravi.

Hi Ravi,
Go through the weblog,
/people/sap.user72/blog/2005/05/05/bsphowto-filter-using-dropdown-in-tableview
Regards,
Azaz Ali.

Customizing Graphical Planning Table Views

Where do I go to alter the look of the graphical planning tables that I find in transactions like CM21, 27, 31 and 32? There are no labels, everything is gray and difficult to read! Where can I go in and change the way these graphical planning tables look? Mainly the colors of the dispatched orders into the work centers (the single gray bars).

Dear,
Please refer this link,
[Lay-out Profile Set|New Lay-out Profile for CM25]
Regards,
R.Brahmankar

How to Query E-Business Tax tables/views

I run SQL queries on the following tables:
ZX_TRANSACTION
ZX_TRANSACTION_LINES
but it returns no rows. How to query ZX tables/views?
My main purpose is to retrieve tax code which is in 12i no longer available in AP Transaction Distributions table/view.
Please advise.
Thanks in advance.

Hi Srini,
I followed PL/SQL procedure stated in note 415860.1. But still can't do the query. See below.
SQL> begin
2 fnd_global.apps_initialize(1079,51569,235);
3 mo_global.init('ZX');
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> select count(*) from ZX_TRANSACTION
2 /
COUNT(*)
0
SQL> select count(*) from ZX_TRANSACTION_LINES
2 /
COUNT(*)
0
Thanks,
Corry

Custom Query modified/Altered By BO

Hi All,
I am facing a strange behavior in Info view of WEB XI 3.1. I have 4 cross tabs in my report & has written a custom query using full outer join for the fourth cross tab with Year, Month & URL as Filter. I ran the queries & it gave me accurate results. I refreshed my report at least 7 times & i did not face any issue but when i refreshed the report by changing the URL for which i need to see the data i get some different results. 1st 3 cross tabs give me accurate result but the 4th gives me inaccurate result. When i clicked on edit query to check the SQL of the 4th Cross tab my custom query no longer remained custom query it was turned to a BO generated query. I don't understand why this strange behavior happened.
Can any one please let me know as to why this happens.
Thank You

Mohd,
by changing the URL for which i need to see the data i get some different results.
Did you perform this activity back in Edit Query?
my custom query no longer remained custom query it was turned to a BO generated query
If you modify your query on the Edit Query screen (either by removing or adding objects to Results Object panel or adding/deleting objects in the Filters) you will cause the app to revert back to the default query (e.g. lose your custom code).
Thanks,
John

OBIEE 11G help with report narrative and table view

Hi,
I have a report designed like the below, I have used "narrative view" for customer detail and "table view" for order detail. In the narrative view I can say row = 1 and it picks up the first record of the customer detail, but order detail shows all rows. How can I control it so the order detail shows only the detail record of the customer associated. Also how do I go to the second record and so forth. Please help. If this is not possible and if there are any alternates, please let me know. Thanks for your time and help.
Customer Number:
Customer Name:
Customer Address:
Order Detail:
Line number | Order No | Order description | Order Status

ssk1974 wrote:
Hi,
I have a report designed like the below, I have used "narrative view" for customer detail and "table view" for order detail. In the narrative view I can say row = 1 and it picks up the first record of the customer detail, but order detail shows all rows. How can I control it so the order detail shows only the detail record of the customer associated. Also how do I go to the second record and so forth. Please help. If this is not possible and if there are any alternates, please let me know. Thanks for your time and help.
Customer Number:
Customer Name:
Customer Address:
Order Detail:
Line number | Order No | Order description | Order StatusWhy don't you do this?
1) Build a dashboard prompt for Customer Number. and save to a PV.
2) Build a report with all the columns for customer and order (in Criteria View) with a filter for the PV to capture the dashboard prompt.
3) Build a pivot table with Customer Number and Customer Name in the Rows section. Put the Customer Address in the Measures section and change the Aggregation Rule to Max.
This will serve as the summary table showing only the information of the customer selected.
2) Build Pivot Table:2 with the Order details.
3) In the Compound Layout, put Pivot table one on the top and Pivot Table:2 below it.
When a customer is selected, you will have the customer data with the order details under it for that customer only.

RMAN Last Completed Backup recorded in any table/view?

Hi Friends,
we are running RMAN backup of Full Database every day on 11g R2 Database.
I would like to know where can i query the last completed backup date/time (in any table/view...) so that i will put a script to query that table/view to verify that the backup is completed .
Regards,
DB

Hello;
if you are using a catalog you can try this :
select
        db_name,
        start_time,
        end_time,
        status,
        time_taken_display,
        output_bytes_display,
        output_device_type,
        session_key,
        session_recid,
        session_stamp
from rc_rman_backup_job_details where end_time > sysdate -1If you not using a catalog V$RMAN_BACKUP_JOB_DETAILS should provide similar information.
Best Regards
mseberg

Can we implement the custom sql query in CR for joining the two tables

Hi All,
Is there anyway to implement the custom sql query in CR for joining the two tables?
My requirement here is I need to write sql logics for joining the two tables...
Thanks,
Gana

In the Database Expert, expand the Create New Connection folder and browse the subfolders to locate your data source.
Log on to your data source if necessary.
Under your data source, double-click the Add Command node.
In the Add Command to Report dialog box, enter an appropriate query/command for the data source you have opened.
For example:
SELECT
    Customer.`Customer ID`,
    Customer.`Customer Name`,
    Customer.`Last Year's Sales`,
    Customer.`Region`,
    Customer.`Country`,
    Orders.`Order Amount`,
    Orders.`Customer ID`,
    Orders.`Order Date`
FROM
    Customer Customer INNER JOIN Orders Orders ON
        Customer.`Customer ID` = Orders.`Customer ID`
WHERE
    (Customer.`Country` = 'USA' OR
    Customer.`Country` = 'Canada') AND
    Customer.`Last Year's Sales` < 10000.
ORDER BY
    Customer.`Country` ASC,
    Customer.`Region` ASC
Note: The use of double or single quotes (and other SQL syntax) is determined by the database driver used by your report. You must, however, manually add the quotes and other elements of the syntax as you create the command.
Optionally, you can create a parameter for your command by clicking Create and entering information in the Command Parameter dialog box.
For more information about creating parameters, see To create a parameter for a command object.
Click OK.
You are returned to the Report Designer. In the Field Explorer, under Database Fields, a Command table appears listing the database fields you specified.
Note:
To construct the virtual table from your Command, the command must be executed once. If the command has parameters, you will be prompted to enter values for each one.
By default, your command is called Command. You can change its alias by selecting it and pressing F2.

Tables of View Joined in Wrong Order When View Joined to Other Tables

I have the following view:
select
     distinct
     'PKG' item_type_code,
     msibk.organization_id,
     msibk.inventory_item_id
from
     mtl_system_items_b_kfv msibk,
     mtl_item_categories mic,
     mtl_default_category_sets mdcs,
     mtl_categories_b_kfv mcbk
where
     msibk.organization_id = mic.organization_id
     and msibk.inventory_item_id = mic.inventory_item_id
     and mic.category_set_id = mdcs.category_set_id
     --1 Inventory (Lookup = MTL_FUNCTIONAL_AREAS)
     and mdcs.functional_area_id = 1
     and mic.category_id = mcbk.category_id
     and mcbk.segment1 = 'EXP'
     and mcbk.segment2 in ( 'PACKAGING' )When I access the columns like this:
select
from
     xxcus_mtl_sys_item_types_v
where
     organization_id = :1
     and inventory_item_id = :2
     and item_type_code = :3It correctly accesses MTL_SYSTEM_ITEMS_B second in the explain plan and everything is good.
But when it is part of a join, it accesses MTL_SYSTEM_ITEMS_B last in the explain plan and has performance issues.
select
     msi.segment1
from
     xxcus_mtl_sys_item_types_v x,
     mtl_system_items msi
where
     msi.organization_id = x.organization_id
     and msi.inventory_item_id = x.inventory_item_id
     and x.item_type_code = 'PAK'Any ideas why the view tables are getting joined incorrectly when the view is joined with another table?
Thanks,
Kurz

The query I posted for the view is just an excerpt. It is several nearly identical queries with UNION ALL between them. I get the same results when I have only one query in the view.
Here is the explain plan for the first query:
| Id | Operation                          | Name                         | Rows | Bytes | Cost (%CPU)|
|   0 | SELECT STATEMENT                   |                              |     5 |   160 |    25 (20)|
|   1 | VIEW                              | XXCUS_MTL_SYS_ITEM_TYPES_V   |     5 |   160 |    25 (20)|
|   2 |   UNION-ALL                        |                              |       |       |            |
|   3 |    SORT UNIQUE NOSORT              |                              |     1 |    71 |     5 (20)|
|* 4 |     FILTER                         |                              |       |       |            |
|   5 |      NESTED LOOPS                  |                              |     1 |    71 |     4   (0)|
|   6 |       NESTED LOOPS                 |                              |     1 |    36 |     3   (0)|
|   7 |        NESTED LOOPS                |                              |     1 |    17 |     1   (0)|
|   8 |         TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 9 |          INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 10 |         INDEX UNIQUE SCAN          | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
|* 11 |        INDEX RANGE SCAN            | MTL_ITEM_CATEGORIES_U1       |     1 |    19 |     2   (0)|
|* 12 |       TABLE ACCESS BY INDEX ROWID | MTL_CATEGORIES_B             |     1 |    35 |     1   (0)|
|* 13 |        INDEX UNIQUE SCAN           | MTL_CATEGORIES_B_U1          |     1 |       |     0   (0)|
| 14 |    SORT UNIQUE NOSORT              |                              |     1 |    63 |     5 (20)|
|* 15 |     FILTER                         |                              |       |       |            |
| 16 |      NESTED LOOPS                  |                              |     1 |    63 |     4   (0)|
| 17 |       NESTED LOOPS                 |                              |     1 |    36 |     3   (0)|
| 18 |        NESTED LOOPS                |                              |     1 |    17 |     1   (0)|
| 19 |         TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 20 |          INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 21 |         INDEX UNIQUE SCAN          | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
|* 22 |        INDEX RANGE SCAN            | MTL_ITEM_CATEGORIES_U1       |     1 |    19 |     2   (0)|
|* 23 |       TABLE ACCESS BY INDEX ROWID | MTL_CATEGORIES_B             |     1 |    27 |     1   (0)|
|* 24 |        INDEX UNIQUE SCAN           | MTL_CATEGORIES_B_U1          |     1 |       |     0   (0)|
| 25 |    SORT UNIQUE NOSORT              |                              |     1 |    71 |     5 (20)|
|* 26 |     FILTER                         |                              |       |       |            |
| 27 |      NESTED LOOPS                  |                              |     1 |    71 |     4   (0)|
| 28 |       NESTED LOOPS                 |                              |     1 |    36 |     3   (0)|
| 29 |        NESTED LOOPS                |                              |     1 |    17 |     1   (0)|
| 30 |         TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 31 |          INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 32 |         INDEX UNIQUE SCAN          | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
|* 33 |        INDEX RANGE SCAN            | MTL_ITEM_CATEGORIES_U1       |     1 |    19 |     2   (0)|
|* 34 |       TABLE ACCESS BY INDEX ROWID | MTL_CATEGORIES_B             |     1 |    35 |     1   (0)|
|* 35 |        INDEX UNIQUE SCAN           | MTL_CATEGORIES_B_U1          |     1 |       |     0   (0)|
| 36 |    SORT UNIQUE NOSORT              |                              |     1 |    71 |     5 (20)|
|* 37 |     FILTER                         |                              |       |       |            |
| 38 |      NESTED LOOPS                  |                              |     1 |    71 |     4   (0)|
| 39 |       NESTED LOOPS                 |                              |     1 |    36 |     3   (0)|
| 40 |        NESTED LOOPS                |                              |     1 |    17 |     1   (0)|
| 41 |         TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 42 |          INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 43 |         INDEX UNIQUE SCAN          | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
|* 44 |        INDEX RANGE SCAN            | MTL_ITEM_CATEGORIES_U1       |     1 |    19 |     2   (0)|
|* 45 |       TABLE ACCESS BY INDEX ROWID | MTL_CATEGORIES_B             |     1 |    35 |     1   (0)|
|* 46 |        INDEX UNIQUE SCAN           | MTL_CATEGORIES_B_U1          |     1 |       |     0   (0)|
| 47 |    SORT UNIQUE NOSORT              |                              |     1 |    71 |     5 (20)|
|* 48 |     FILTER                         |                              |       |       |            |
| 49 |      NESTED LOOPS                  |                              |     1 |    71 |     4   (0)|
| 50 |       NESTED LOOPS                 |                              |     1 |    36 |     3   (0)|
| 51 |        NESTED LOOPS                |                              |     1 |    17 |     1   (0)|
| 52 |         TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 53 |          INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 54 |         INDEX UNIQUE SCAN          | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
|* 55 |        INDEX RANGE SCAN            | MTL_ITEM_CATEGORIES_U1       |     1 |    19 |     2   (0)|
|* 56 |       TABLE ACCESS BY INDEX ROWID | MTL_CATEGORIES_B             |     1 |    35 |     1   (0)|
|* 57 |        INDEX UNIQUE SCAN           | MTL_CATEGORIES_B_U1          |     1 |       |     0   (0)|
--------------------------------------------------------------------------------------------------------Here is the explain plan for the second query:
| Id | Operation                           | Name                         | Rows | Bytes | Cost (%CPU)|
|   0 | SELECT STATEMENT                    |                              |     5 |   240 |    10 (50)|
|   1 | NESTED LOOPS                       |                              |     5 |   240 |    10 (50)|
|   2 |   VIEW                              | XXCUS_MTL_SYS_ITEM_TYPES_V   |     5 |   160 |     5 (100)|
|   3 |    UNION-ALL                        |                              |       |       |            |
|   4 |     HASH UNIQUE                     |                              |     1 |    71 |     1 (100)|
|* 5 |      FILTER                         |                              |       |       |            |
|   6 |       NESTED LOOPS                  |                              |    17 | 1207 |    77   (0)|
|   7 |        NESTED LOOPS                 |                              |    16 |   992 |    77   (0)|
|   8 |         NESTED LOOPS                |                              |     1 |    43 |     7   (0)|
|   9 |          TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 10 |           INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 11 |          TABLE ACCESS BY INDEX ROWID| MTL_CATEGORIES_B             |     1 |    35 |     6   (0)|
|* 12 |           INDEX RANGE SCAN          | MTL_CATEGORIES_B_N1          |    44 |       |     2   (0)|
|* 13 |         TABLE ACCESS BY INDEX ROWID | MTL_ITEM_CATEGORIES          |    49 |   931 |    70   (0)|
|* 14 |          INDEX RANGE SCAN           | MTL_ITEM_CATEGORIES_N3       |   441 |       |     4   (0)|
|* 15 |        INDEX UNIQUE SCAN            | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
| 16 |     HASH UNIQUE                     |                              |     1 |    63 |     1 (100)|
|* 17 |      FILTER                         |                              |       |       |            |
| 18 |       NESTED LOOPS                  |                              | 2158 |   132K|   250   (1)|
| 19 |        NESTED LOOPS                 |                              | 2134 |   112K|   249   (0)|
| 20 |         NESTED LOOPS                |                              |    44 | 1540 |     7   (0)|
| 21 |          TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 22 |           INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
| 23 |          TABLE ACCESS BY INDEX ROWID| MTL_CATEGORIES_B             |    44 | 1188 |     6   (0)|
|* 24 |           INDEX RANGE SCAN          | MTL_CATEGORIES_B_N1          |    44 |       |     2   (0)|
|* 25 |         TABLE ACCESS BY INDEX ROWID | MTL_ITEM_CATEGORIES          |    49 |   931 |    70   (0)|
|* 26 |          INDEX RANGE SCAN           | MTL_ITEM_CATEGORIES_N3       |   441 |       |     4   (0)|
|* 27 |        INDEX UNIQUE SCAN            | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
| 28 |     HASH UNIQUE                     |                              |     1 |    71 |     1 (100)|
|* 29 |      FILTER                         |                              |       |       |            |
| 30 |       NESTED LOOPS                  |                              |    33 | 2343 |    77   (0)|
| 31 |        NESTED LOOPS                 |                              |    33 | 2046 |    77   (0)|
| 32 |         NESTED LOOPS                |                              |     1 |    43 |     7   (0)|
| 33 |          TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 34 |           INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 35 |          TABLE ACCESS BY INDEX ROWID| MTL_CATEGORIES_B             |     1 |    35 |     6   (0)|
|* 36 |           INDEX RANGE SCAN          | MTL_CATEGORIES_B_N1          |    44 |       |     2   (0)|
|* 37 |         TABLE ACCESS BY INDEX ROWID | MTL_ITEM_CATEGORIES          |    49 |   931 |    70   (0)|
|* 38 |          INDEX RANGE SCAN           | MTL_ITEM_CATEGORIES_N3       |   441 |       |     4   (0)|
|* 39 |        INDEX UNIQUE SCAN            | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
| 40 |     HASH UNIQUE                     |                              |     1 |    71 |     1 (100)|
|* 41 |      FILTER                         |                              |       |       |            |
| 42 |       NESTED LOOPS                  |                              |    17 | 1207 |    77   (0)|
| 43 |        NESTED LOOPS                 |                              |    16 |   992 |    77   (0)|
| 44 |         NESTED LOOPS                |                              |     1 |    43 |     7   (0)|
| 45 |          TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 46 |           INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 47 |          TABLE ACCESS BY INDEX ROWID| MTL_CATEGORIES_B             |     1 |    35 |     6   (0)|
|* 48 |           INDEX RANGE SCAN          | MTL_CATEGORIES_B_N1          |    44 |       |     2   (0)|
|* 49 |         TABLE ACCESS BY INDEX ROWID | MTL_ITEM_CATEGORIES          |    49 |   931 |    70   (0)|
|* 50 |          INDEX RANGE SCAN           | MTL_ITEM_CATEGORIES_N3       |   441 |       |     4   (0)|
|* 51 |        INDEX UNIQUE SCAN            | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
| 52 |     HASH UNIQUE                     |                              |     1 |    71 |     1 (100)|
|* 53 |      FILTER                         |                              |       |       |            |
| 54 |       NESTED LOOPS                  |                              |    17 | 1207 |    77   (0)|
| 55 |        NESTED LOOPS                 |                              |    16 |   992 |    77   (0)|
| 56 |         NESTED LOOPS                |                              |     1 |    43 |     7   (0)|
| 57 |          TABLE ACCESS BY INDEX ROWID| MTL_DEFAULT_CATEGORY_SETS    |     1 |     8 |     1   (0)|
|* 58 |           INDEX UNIQUE SCAN         | MTL_DEFAULT_CATEGORY_SETS_U1 |     1 |       |     0   (0)|
|* 59 |          TABLE ACCESS BY INDEX ROWID| MTL_CATEGORIES_B             |     1 |    35 |     6   (0)|
|* 60 |           INDEX RANGE SCAN          | MTL_CATEGORIES_B_N1          |    44 |       |     2   (0)|
|* 61 |         TABLE ACCESS BY INDEX ROWID | MTL_ITEM_CATEGORIES          |    49 |   931 |    70   (0)|
|* 62 |          INDEX RANGE SCAN           | MTL_ITEM_CATEGORIES_N3       |   441 |       |     4   (0)|
|* 63 |        INDEX UNIQUE SCAN            | MTL_SYSTEM_ITEMS_B_U1        |     1 |     9 |     0   (0)|
| 64 |   TABLE ACCESS BY INDEX ROWID       | MTL_SYSTEM_ITEMS_B           |     1 |    16 |     1   (0)|
|* 65 |    INDEX UNIQUE SCAN                | MTL_SYSTEM_ITEMS_B_U1        |     1 |       |     0   (0)|
---------------------------------------------------------------------------------------------------------

How do I use the option "table view" in NetWeaver 2004s Query Designer?

Dear,
We have used NetWeaver 2004s Query Designer, We found a strange problem. The option to select table view is not available. It is greyed out. How can you select table view (tabular) in 2004s Query Designer?
I have read the help doc about tabular view of NetWeaver 2004s Query Designer, I check my query, it has only one structure . but the option is still greyed out. I rebuild the query with 3.x Query Designer in tabular view, and reopen it with 2004s Query Designer, So there is a tab named "tabular view" display, but the option to select table view is still not available, and when users view the query result in web , it is still not in tabular view display. So I am confused, is there a bug with NetWeaver 2004s Query Designer?
Please help me. Thanks!

Note 1002271. Seach this note to use key word "table view"

Unable to create visual composer table view from the Bex Query

Hi
I am trying to create the visual composer lay out from a Bex query. The Bex query contains a set of Key figures and a structure.
These key figure and structure combination is forming a table in the query output. Key figure parameters are coming as rows and Structure parameters are coming as columns.
example query out put:
Total, HPC, FDS excel ICe etc are as Structure elements and coming as columns in query out put and
Invoice value, Gross sale value, Efficient operations etc are as Key figure elements in query and coming as rows in query out put.
But if I map this query to visual composer table view all these are coming as columns as given below.
Total Invoice value , Total Gross sale value, Total Efficient operations, HPC Invoice vale,.........
And if execute the query will giving the out put in single row.
Can anybody help me out to map this in the row column format?
Is it really possible to do in VC?
I am using CE 7.2. The VC model I need to be embedding in BPM.
Please help me to solve this issue. I completely stuck up this issue.
Regards
Sajith P
Edited by: Sajith P on Aug 17, 2010 3:07 PM
Edited by: Sajith P on Aug 17, 2010 3:15 PM

Hi,
Try to use some function module which will convert query data into flat tables. (eg., RS_VC_GET_QUERY_VIEW_DATA_FLAT).
Hope this solves your issue.
Regards,
Vinay

Table View in Query Designer is not avaliable

Hi Guru:
The "table view" in the menu item "View" is grey in the query designer.
I have only 1 structure ( key figure structure ) in my query.
How to change it to the "Table View" mode then?
Thanks.
Eric

Hi
Please create another structure in your query. Once you have 2 structures then only table view will be enabled.
Regards
Pradip

Addition of a custom column in a table view

Hi all,
I want to add a custom column in a table view. Kindly tell me if this is possible.
Regards,
Vivek Pandey

Hi Vivek,
This can definately be done....you will have to declare and iterator and in the GET_COLUMN_DEFINITIONS, declare the column name....
Referr to blogs :
<a href="/people/brian.mckellar/blog/2003/10/31/bsp-programming-htmlb-tableview-iterator Basics</a>
and
<a href="/people/thomas.jung3/blog/2004/09/15/bsp-150-a-developer146s-journal-part-xi--table-view-iterators Iterator.</a>
The second blog shows how to insert a icon, which is an extra column...
Hope this helps.
<b><i>Do reward each useful answer..!</i></b>
Thanks,
Tatvagna.

Query and update a table/view

What is the best & fastest way to do this?
1) Put up a query input region for users to enter parameters.
2) Run a query on a table/view using those parameters.
3) Allow the output in (2) to be modified by user (multiple rows at a time) and then Submit the updates back to update th table/view
I can do (1) and (2) easily. How can I do (3)?
Thanks

Make a report on the table. Go to the definition of
the report column and change the "Display As" type to
text field or select list or whcih ever is
applicable. Write a process on submit to insert these
values back to the table. You will have control over
which columns the user can modify.Thats a good idea and I was able to start on it. But how can my after submit process tell which rows to modify? i.e. what will my after submit process look like?
for rec in (....)
loop
update my_table set
end loop;
Help? Thanks

MSS custom query restrictions (table/view/join)

Similar Messages

Maybe you are looking for