Select distinct in view

Hi Experts,
I am creating a database view. I am using this view in my search help(created in se11). Now this view is returning recurring values. I want only the distinct values in my search help. Can anyone please suggest how do I go about it?
Regards,
Abdullah

Hi George,
I am using
select-options: s_groes for mara-groes matchcode object zgroes modif id chr.
If i opt for coding I will have use something similar to the code below.,
at selection-screen on value-request for s_groes-low.
perform f_f4_groes.
at selection-screen on value-request for s_groes-high.
perform f_f4_groes.
I will explore the search help exit.
Regards,
Abdullah
Edited by: Abdullah Ismail on May 12, 2009 3:41 PM

Similar Messages

How to select distinct values from a table when it has composite primary ke

Hi
I have the requirement like , I need to select distinct one column values from the table which has composite primary key. How to acheive this functioinality using view object.
Eg : Table 1 has col1 and col2, col3
col1 col2 col3
1 A NA
1 B NA
2 A NA
3 C NA
2 D NA
primary key (col1,col2)
I have to select distinct col1.
Thanks

Hi
I got the solution for above. By Creating the read only view object we can acheive this.
thanks

Error while selecting from a view ORA-01031: Insufficient privileges

As DBA I have granted select privileges on a view to a user, but whenever I login as that user and try to select from the view I get the message 'ORA-01031'. When I run the query in the view as the user I do not have problem and can see the results. This view joins tables from more than one schema and does a distinct on the resultset. I am new to Oracle and would appreciate any help I can get.
Thanks

Back on this problem when I created another user with select permission on the same view and a default role that has reference on all the objects on the other schemas, I end up with the same error message. Although this time the schema owner of the view has select privileges on all the tables from other schemas referenced in the view.
Thanks

Invalid Column Name on select from materialized view?

Hey all, I have created this materialized view for my java to select from. For some reason when I try to select from it, I get invalid column name. Here is my mat view statement in its simplest form:
create materialized view mv_pgridtcevcluster_property as
select distinct clustername_ as "OBJECT_ID", CLUSTERNAME_, LICENSEMODE_
from p_gridtcevcluster p
order by clustername_;
Now when I run my select statement from jdbc:
SQL: select object_id from MV_PGRIDTCEVCLUSTER_PROPERTY
java.sql.SQLException: Invalid column name
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
     at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java:3319)
     at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:1926)
     at oracle.jdbc.driver.OracleResultSet.getString(OracleResultSet.java:1515)
     at com.mchange.v2.c3p0.impl.NewProxyResultSet.getString(NewProxyResultSet.java:3342)
     at historian.objects.mgmt.udrManagerTest.gatherObjects(udrManagerTest.java:73)
Anyone have issues with this before? It seems to throw the error sporatically, any help would be much appreciated!
Regards,
TimS
Edited by: TimS on Mar 30, 2009 1:54 PM
Nevermind, figured it out. Was using wrong column name identifier when picking values from resultset.

Since you have "OBJECT_ID" in quotes, Oracle stores the column name literally and case sensitively, and the column name must be capitalized when referenced.
From a regular sql*plus window, try
select object_id from mv_pgridtcevcluster_property;
select OBJECT_ID from mv_pgridtcevcluster_property;
select "OBJECT_ID" from mv_pgridtcevcluster_property;What is the result from each of them?

SELECT DISTINCT does not work - Another Problem!

Dear All
Previous Post
I just posted a thread, which has been answered by an expert. It's here:
SELECT DISTINCT does not work. Why?
My original problem was that the Query returned duplicate records, and SELECT DISTINCT did not work.
The solution was to change this select:
T0.[U_SupInv]      AS 'Link'
... to this:
CAST(T0.[U_SupInv] as nvarchar(100))      AS 'Link'
The amended Query worked.
New Problem
I just discovered that resolving the problem created a new one.
The field U_SupInv (Link) is in fact a UDF.
I created it so that all Suppliers' Invoices could be Scanned to pdf files, and these pdf could be linked
to the respective AP Invoice.
Originally, when I clicked 'Link' in my Query results, the pdf scan pops up.
When the Query is amended by adding CAST, the link becomes dead.
Help
Could anyone tell me how I can make SELECT DISTINCT work, as well keeping the LINKS live?
The main purpose of my Query is to help users view the pdf scans by clicking on the links.
Thanks
Leon Lai
Here's my Original Query
SELECT
T0.[UpdateDate] AS 'Update Dt',
T0.[TaxDate] AS 'Doc Dt',
CASE T5.[TransType]
     WHEN '18' THEN 'PU ' + CONVERT(VARCHAR(6), T0.[DocNum])
     WHEN '19' THEN 'PC ' + CONVERT(VARCHAR(6), T0.[DocNum])
END 'SAP Ref.',
T1.[ImportLog]     AS 'Ship #',
T0.[CardCode] + '' AS 'Supplier #',
T0.[CardName]      AS 'Supplier Name',
T0.[DocTotal]      AS 'Rs',
T1.[BlockNum]      AS 'Reqn #',
T0.[DocNum]        AS 'Doc No',
T0.[U_SupInv]      AS 'Link'
FROM klship.[dbo].[OPCH] T0
INNER JOIN klship.[dbo].[PCH1] T1 ON T0.[DocEntry] = T1.[DocEntry]
INNER JOIN klship.[dbo].[OJDT] T5 ON T0.[TransID] = T5.[TransID]
WHERE
(T0.[UpdateDate] >= '[%2]' AND
T0.[UpdateDate] <= '[%3]' AND
T0.[U_SupInv] IS NULL)
OR
(T0.[UpdateDate] >= '[%4]' AND
T0.[UpdateDate] <= '[%5]' AND
T0.[U_SupInv] IS NOT NULL)
FOR BROWSE

Dear István Korös,
Thanks a lot for your answer.
I will test your suggestion tomorrow, as it's night and I am returning home now.
However, I do not think it will suit my requirements for the foll reasons:
- I worked hard to get rid of the need to enter anything in the @Scan2 field.
- This UDF was created solely as a text of instruction for my staff.
   Unfortunately I had to fill in something to make the Query work.
- The problem is that if the user forgets to click the drop-down arrow and leaves @Scan2
   blank, the query does not work.
- With the help of another expert, I succeeded in ignoring @Scan2 altogether.
- I posted only a simplified version of my Query on the forum, without the codes relating to eliminating the
need to enter something in @Scan2, so you may not be aware of my requirement.
- I hope you understand my reluctance. But I will try your suggestion nevertheless.
My Suggestion
I think using PCH1.VISORDER may be the solution.
If we select only those rows where visorder = 0, then
   - there will be no duplication
   - I need not use SELECT DISTINCT
   - All my LINKS to pdf files will be live because I need not use CAST
   - I may retain that part of my Query which permits ignoring @Scan2 altogether.
- A Dream!-
The problem is that I don't know how and where to place that VISORDER.
If you think I may be right, could you help me along that line?
Best Regards
Leon Lai

How to undo "select distinct" in OBIEE

Hello guys
I found that pretty much in all the reports that we created in OBIEE, the presentation service would generate SQL that starts with "select distinct" when I view the query log..
I'd like to know what configuration in the Admin Tool or presentation service is controlling this behavior of OBIEE. For some reason as I am tuning the performance by running the same query in DB, the same query without "distinct" can go so much faster than the original one from OBIEE.. So I'd like to configure my RPD so that certain reports will not have "select distinct". I know that by default, the BI server will always generate a "distinct", but is there a way to override this default, if not, what might be some performance tuning tactics I can use?
Any thoughts?
Thanks
Edited by: user7276913 on Oct 27, 2009 8:20 PM

BenS wrote:
Two issues with this that I encountere:
When I selected the first suggested option at the Physical Layer for the database, I found the "DISTINCT SUPPORTED" option. There were two columns checked: Value and Default. I was able to unselect Value but not Default.
(1) What is the difference between Value and Default?
(2) If I only unselect Value will it stop Answers from adding the DISTINCT to every query created?
Second, when I selected the source from the business model mapping, it already did not have the DISTINCT box checked. Therefore, I could not limit this at the Logical layer as I would have preferred.
If you could help me understand the first option it may clarify how to implement option # 2.
Thanks...1) the defaults are stored in an .ini file and serve the purpose of defining the defaults when you hit the 'revert to default' button.
If you unselect value, you are telling OBIEE that the database for which you are changing these options does not support the distinct clause, I doubt you wish to do this across the entire application.
I think you will find that OBIEE applies the distinct :
1) when the LTS has distinct ticked.
2) When the column in question is not part of a dimension hierachy key (if it is, your telling the OBIEE server these should be unique, so wont issue the distinct)
or
3) the column forms part of a key in either logical BMM layer or as part of a physical key.
adding the column to a Dim Hierachy wont be an option in most cases, you could try playing with just setting this column as a key on the BMM layer or Physical layer , and let us know if this helps.

SELECT DISTINCT with LINQ

Hey,
I am trying to perform a SELECT DISTINCT COL1, COL2, COL3 FROM VIEW WHERE CONDITION using LINQ with ODAC 112030 but I get different results.
C#:
var s1 = context.Select(v=>new { v.COL1, v.COL2, v.COL3}).Where(...).Distinct();
Any ideas?

Hey,
I think this way works - with anonymous types:
context.Entity.Where(...).Select(ent => new { col1 = ent.COL1, ... }).Distinct();.
You can also do context.Entity.Select("distinct it.COL1, it.COL2").Where("..."); but one should be careful to add all necessary columns in select statement.
Edited by: 917334 on Jun 7, 2012 7:11 AM

"connect by" problem with "select distinct"

When I run the following SQL (using "Scott" DB):
select *
from emp
where deptno = 30 or mgr is null
start with mgr is null
connect by prior empno = mgr
order siblings by ename
I get the results one would expect. The President is first and all those reporting to him/her are listed in correct sequence.
EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO
7839,KING,PRESIDENT,,11/17/1981,5000,10
7698,BLAKE,MANAGER,7839,5/1/1981,2850,30
7499,ALLEN,SALESMAN,7698,2/20/1981,1600,300,30
7900,JAMES,CLERK,7698,12/3/1981,950,30
7654,MARTIN,SALESMAN,7698,9/28/1981,1250,1400,30
7844,TURNER,SALESMAN,7698,9/8/1981,1500,0,30
7521,WARD,SALESMAN,7698,2/22/1981,1250,500,30
However, when I run the same query but make it "select distinct" I get the following:
EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO
7499,ALLEN,SALESMAN,7698,2/20/1981,1600,300,30
7698,BLAKE,MANAGER,7839,5/1/1981,2850,,30
7900,JAMES,CLERK,7698,12/3/1981,950,,30
7839,KING,PRESIDENT,,11/17/1981,5000,,10
7654,MARTIN,SALESMAN,7698,9/28/1981,1250,1400,30
7844,TURNER,SALESMAN,7698,9/8/1981,1500,0,30
7521,WARD,SALESMAN,7698,2/22/1981,1250,500,30
Why would adding "distinct" to the select cause the result to be sorted STRICTLY by ename (per "order siblings by...")?
Finally, if I "select distinct" but don't specify any "order" I get this, in NO APPARENT order:
EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO
7499,ALLEN,SALESMAN,7698,2/20/1981,1600,300,30
7521,WARD,SALESMAN,7698,2/22/1981,1250,500,30
7654,MARTIN,SALESMAN,7698,9/28/1981,1250,1400,30
7698,BLAKE,MANAGER,7839,5/1/1981,2850,,30
7839,KING,PRESIDENT,,11/17/1981,5000,,10
7844,TURNER,SALESMAN,7698,9/8/1981,1500,0,30
7900,JAMES,CLERK,7698,12/3/1981,950,,30
Thanks in advance for any insight offered!
-Gene

you have to specify what is going to be the distict field.No you don't. DISTINCT keyword applies to the whole SELECT list. See your own link.
In any case this does not appear to have anything to do with what you SELECT, rather that the SORT UNIQUE caused by the DISTINCT keyword appears to prevent the ORDER SIBLINGS BY clause from working correctly.
Not really sure why you need DISTINCT in this example, no doubt this is being applied elsewhere. Given that you have duplicates in the rowset and that hierarchical query now supports views, perhaps it would be more efficient to apply DISTINCT keyword first, something like...
SELECT e.*
FROM (SELECT DISTINCT e.*
FROM emp e
WHERE e.deptno = 30
OR e.mgr IS NULL) e
START WITH e.mgr IS NULL
CONNECT BY PRIOR e.empno = e.mgr
ORDER SIBLINGS BY e.ename;
Alternatively you could skip ORDER SIBLINGS BY clause and use SYS_CONNECT_BY_PATH function to get your order, something like...
SELECT e.*
FROM (SELECT DISTINCT e.*,
SYS_CONNECT_BY_PATH () path
FROM emp e
WHERE e.depno = 30
OR e.mgr IS NULL
START WITH e.mgr IS NULL
CONNECT BY PRIOR e.empno = e.mgr) e
ORDER BY e.path
Padders

How to select a custom view in BAPI_MATERIAL_SAVEDATA

In our company we have defined some CUSTOM views for different materials. I want to select a custom view in the header data but don't see an option. The only options I see are as follows:
MATERIAL
IND_SECTOR
MATL_TYPE
BASIC_VIEW
SALES_VIEW
PURCHASE_VIEW
MRP_VIEW
FORECAST_VIEW
WORK_SCHED_VIEW
PRT_VIEW
STORAGE_VIEW
WAREHOUSE_VIEW
QUALITY_VIEW
ACCOUNT_VIEW
COST_VIEW
INP_FLD_CHECK
MATERIAL_EXTERNAL
MATERIAL_GUID
MATERIAL_VERSION
How can I select a view (in BAPI_MATERIAL_SAVEDATA) that's not a standard SAP view?
Please help!
Thanks.

Hi,
which views do you select in the structure HEADDATA? Do you select STORAGE_VIEW?
Cheers

Query help in select Distinct on one column.

CREATE GLOBAL TEMPORARY TABLE Table1 (
ID1 varchar2(100) ,
Name1 varchar2(100),
Name11 varchar2(100)
insert into Table1 values ('a','n1','h3');
insert into Table1 values('b','n2','h2');
insert into Table1 values('a','n3','h1');
insert into Table1 values('c','n4','h5');
insert into Table1 values ('c','n5','h4');
insert into Table1 values('d','n6','h6');
select * from Table1;
ID1,NAME1,     NAME11
a,     n1,     h3
b,     n2,     h2
a,     n3,     h1
c,     n4,     h5
c,     n5,     h4
d,     n6,     h6
I am trying to select distinct ID1 and all values associated with it which is max row.I want to result as -
ID1,NAME1,     NAME11
a,     n3,     h1
b,     n2,     h2
c,     n5,     h4
d,     n6,     h6
Can you please help me to write simple query to get above result.
Edited by: 871447 on Jul 25, 2011 9:42 AM
Edited by: 871447 on Jul 25, 2011 9:45 AM

Hi,
Do a self-join, to combine the two rows for each value of id1 onto one output row.
Make it an outer join, in case there is only one row with a vlaue for id1.
SELECT l.id1
,     l.name1
,     NVL ( r.name11
         , l.name11
         )          AS name11
FROM              table1     l
LEFT OUTER JOIN     table1     r ON l.id1     = r.id1
                          AND l.name1     < r.name1
;Edited by: Frank Kulash on Jul 25, 2011 12:57 PM
Sorry, I mis-read the problem.
Lee's solution, above, assumes that name1 is unique, as it is in your sample data.
What output would you want if that's not the case?
If name1 is not unique, but the combination of (id1, name1) is unique, then you can modify Lee's solution like this:
SELECT *
FROM    table1
WHERE   (id1, name1) IN (
                    SELECT    id1
                    ,       MAX (name1)
                           FROM          table1
                    GROUP BY id1
;Or, if you can't make any assumptions about uniqueness, you might need something like this:
WITH     got_r_num     AS
     SELECT id1, name1, name11
     ,     ROW_NUMBER () OVER ( PARTITION BY id1
                               ORDER BY         name1     DESC
                         ,                name11     DESC
                       )      AS r_num
     FROM     table1
SELECT id1, name1, name11
FROM     got_r_num
WHERE     r_num     = 1
;

Select a specific view in MM02/MM01

Hi Abappers,
I am doing a BDC on MM01 transaction and want to just select the accounting view and extend materials for different valuation types. But the position of accounting view is coming different on different material and my BDC recording is failing to select the accounting view. Does anyone has any idea how we can pinpoint and select the accounting view?
Thanks,
David.

SELECTION_VIEWS_FIND - This FM Will work depends on material type..
in your case this FM Is not required and you need to have Accounting view.
Any way See below program and you will get some idea and uploaded data into Material master change mode and it is applicable to user defined view
REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
zjpm001.
*&   I N B O U N D V I A   A B A P : Batch input Session method     *
*&   Development ID: IM_DD_306_LJP                                   *
*&   Report        : ZJPMUIM306                                      *
*&   The Purpose of the Object is to interface Create Input Record   *
*&   for SAP Migration from the Material master of BPCS All the      *
*&   information received at BPCS is collected into a single record. *
*&   By using session method upload data from file ,one item is
*&   created for one record                                          *
*&   Change Log:                                                     *
*&   Init       Who              Date         Text                   *
*& MALIKDH1   Seshu Reddy    26-07-2003   Initial Version           *
                         Constants                                   *
CONSTANTS:c_vkorg(4) type c value 'JP20',        " Sales Organization
          c_vtweg(2) type c value 'TR' ,         " Distribution Channel
          c_werks(4) Type c value 'JP01' ,       " Plant
          c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
          c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
          c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
          c_seq_code(2) VALUE 'Z1',              " Sequential Code
          c_keep(1) TYPE c VALUE 'X',           " Keep
          c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
          c_tcode LIKE tstc-tcode VALUE 'MM02', " Transaction Code
          c_blank(1) VALUE ' ',                   " Blank
          c_intls(1) VALUE 'N'.                  " Logistic Status
              Variables                                      *
DATA: g_flag1(1), " Variable to hold
      g_flag(1),   " Variable to hold
      g_file LIKE rlgrap-filename VALUE
     'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
       Internal tables/ Work area                           *
Internal Table for Delimter
DATA : BEGIN OF t_delim OCCURS 0,
       text(1000),
       END OF t_delim.
Internal table for BDC processing
DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
Internal table for holding the data which has to be uploaded.
DATA: BEGIN OF t_bpcs OCCURS 0,
      matnr(15) TYPE c, " material no
      dosage(40) TYPE c, " Dosage form(Local)
      appearance(40) TYPE c, " Appearance
      idcode(6) TYPE c,     " Identification Code
      prostformno(10) TYPE c, "SOP
      weitab(7) TYPE c,    " Weight/tablet
      uom1(2) TYPE c,     " UOM of Carton
      uom2(2) TYPE c,     " UOM of Case
      carsize(14) TYPE c, " Carton size
      cassize(14) TYPE c, " Case size
      rupqty(11) TYPE c, " Round up
      abvname(3) TYPE c, " Product short name
      END OF t_bpcs.
*Internal table for t_bpcs
DATA: BEGIN OF t_mdata OCCURS 0,
      matnr LIKE marc-matnr, " Material number
      zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
      zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
      zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
      zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
      zzjp_wei_tab(10) type c , " Weight/tablet
      zzjp_bio LIKE marc-zzjp_bio,"Biologics Indicator
      zzjp_itf LIKE marc-zzjp_itf, " ITF code
      zzjp_car(2) type c, " UOM of Carton
      zzjp_cas(2) type c, " UOM of Case
      zzjp_car_size(11) type c," Carton size
      zzjp_cas_size(11) type c, " Case size
      zzjp_rupqty(11) type c, " Round up
      zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
      zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
      zzjp_re2 LIKE marc-zzjp_re2, "Report type
      zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
      zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
      zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
      zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
      zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
      zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
      zzjp_spl_id LIKE mvke-zzjp_spl_id, " Sample internal order
      END OF t_mdata.
Internal table for Mara Table
DATA: BEGIN OF t_mara OCCURS 0,
      matnr LIKE mara-matnr, " material Number
      vpsta LIKE mara-vpsta, " Maintenance status of complete material
      pstat like mara-pstat, " Maintenance status
      END OF t_mara.
Internal table for Material Master View Selection Screens
DATA: BEGIN OF t_bildtab OCCURS 0.
        INCLUDE STRUCTURE mbildtab.
DATA: END OF t_bildtab.
internal table for T_bildtab
DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
*Work area for T_bildtab internal table(Views Selection)
DATA: BEGIN OF w_data,
      flag1 type c,
      anzd70 TYPE i,
      field1(20) type c,
      field2(20) type c,
      field3(20) type c,
      field4(20) type c,
      count(2) TYPE c,
      END OF w_data.
            Main Processing                           *
START-OF-SELECTION.
Store data from file into internal table
PERFORM f_uplaod_data.
Transfer the uploaded data into t_mdata internal Table
PERFORM f_process_data.
Selecting The views based on Material number
PERFORM f_view_list.
Open a BDC Session
PERFORM f_bdc_open.
*Selecting the fields from mara table
SELECT matnr
         vpsta
         pstat
    FROM mara
INTO TABLE t_mara
FOR ALL ENTRIES IN t_mdata
WHERE matnr = t_mdata-matnr.
SORT t_mara BY matnr.
SORT t_mdata BY matnr.
Transfer the uploaded data into BDCDATA structure
PERFORM f_process_bdc.
Close The BDC Session
PERFORM f_close_group.
*&      Form F_VIEW_LIST                                             *
         Routine to used for Calling the function module            *
          Selection_views_find                                      *
FORM f_view_list.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
       EXPORTING
            bildsequenz     = c_seq_code
            pflegestatus    = c_viewlist
       TABLES
            bildtab         = t_bildtab
       EXCEPTIONS
            call_wrong      = 1
            empty_selection = 2
            OTHERS          = 3.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " F_VIEW_LIST
*&      Form f612_view_sort                                          *
Routine to used for Selecting The views based on Material Number *
FORM f612_view_sort.
t_bildtab_dup[] = t_bildtab[].
Reading the Internal table t_mara
READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
TRANSLATE t_mara-pstat USING ' $'.
CLEAR: w_data-flag1, w_data-anzd70.
LOOP AT t_bildtab_dup.
    IF t_bildtab_dup-pstat CA t_mara-pstat.
      w_data-anzd70 = w_data-anzd70 + 1.
      IF t_bildtab_dup-kzanz IS INITIAL.
        t_bildtab_dup-kzanz = 'X'.
        w_data-flag1 = 'X'.
        MODIFY t_bildtab_dup.
      ENDIF.
    ELSE.
      IF NOT t_bildtab_dup-kzanz IS INITIAL.
        CLEAR t_bildtab_dup-kzanz.
        w_data-flag1 = 'X'.
        MODIFY t_bildtab_dup.
      ENDIF.
    ENDIF.
ENDLOOP.
TRANSLATE t_mara-pstat USING '$ '.
IF NOT w_data-flag1 IS INITIAL.
    SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
ENDIF.
*Reading The internal table for T_bildtab_dup
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
    WRITE sy-tabix TO w_data-count.
    w_data-count = w_data-count + 2.
    IF w_data-anzd70 > 18.
      w_data-count = w_data-count - 18.
    ENDIF.
    CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
    CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
ENDIF.
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF t_bildtab_dup-kzanz = 'X'.
    WRITE sy-tabix TO w_data-count.
    IF w_data-anzd70 > 18.
          w_data-count = w_data-count + 2.
      w_data-count = w_data-count - 18.
    ENDIF.
    CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
    CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
ENDIF.
ENDFORM.                    " f612_view_sort
*&      Form f_uplaod_data                                           *
Routine to used for Uploading the data from file to Internal table *
FORM f_uplaod_data.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = g_file
            filetype                = 'DAT'
       TABLES
            data_tab                = t_delim
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF t_bpcs IS INITIAL.
    LOOP AT t_delim.
      SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
                                     t_bpcs-dosage
                                     t_bpcs-appearance
                                     t_bpcs-idcode
                                     t_bpcs-prostformno
                                     t_bpcs-weitab
                                     t_bpcs-uom1
                                     t_bpcs-uom2
                                     t_bpcs-carsize
                                     t_bpcs-cassize
                                     t_bpcs-rupqty
                                     t_bpcs-abvname.
      APPEND t_bpcs.
    ENDLOOP.
ENDIF.
ENDFORM.                    " f_uplaod_data
*&      Form F_BDC_OPEN
      Routine to create BDC Session to be processed
FORM f_bdc_open.
CALL FUNCTION 'BDC_OPEN_GROUP'
       EXPORTING
            client              = sy-mandt
            group               = c_group
            keep                = c_keep
            user                = sy-uname
       EXCEPTIONS
            client_invalid      = 1
            destination_invalid = 2
            group_invalid       = 3
            group_is_locked     = 4
            holddate_invalid    = 5
            internal_error      = 6
            queue_error         = 7
            running             = 8
            system_lock_error   = 9
            user_invalid        = 10
            OTHERS              = 11.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
ENDIF.
ENDFORM.                    " F_BDC_OPEN
*&      Form F_PROCESS_BDC
      Processing of BDCDATA Structure
FORM f_process_bdc.
LOOP AT t_mdata.
    PERFORM f612_view_sort.
    PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
    PERFORM f_bdc_field USING 'BDC_CURSOR'
                                  'RMMG1-MATNR'.
    PERFORM f_bdc_field USING 'BDC_OKCODE'
                                  '=AUSW'.
    PERFORM f_bdc_field USING 'RMMG1-MATNR'
                                  t_mdata-matnr.
    PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
    PERFORM f_bdc_field USING 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
    IF w_data-anzd70 > 18.
      PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '=P+'.
      PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0070'.
      PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
    ENDIF.
reading the t_bildtab internal table
    READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
    IF t_bildtab_dup-kzanz = 'X'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    w_data-field1.
      PERFORM f_bdc_field       USING w_data-field2 'X'.
      g_flag = 'X'.
    ENDIF.
reading the t_bildtab internal table
    READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
    IF sy-subrc EQ 0.
      g_flag = 'X'.
    ENDIF.
    IF t_bildtab_dup-kzanz = 'X'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    w_data-field3.
      PERFORM f_bdc_field       USING w_data-field4 'X'.
      g_flag1 = 'X'.
    ENDIF.
    IF g_flag = 'X' AND g_flag1 = 'X'.
      PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
      PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                    'RMMG1-VTWEG'.
      PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                    '=ENTR'.
      PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                    c_werks.
      PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                    c_vkorg.
      PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                    c_vtweg.
      CLEAR g_flag.
      CLEAR g_flag1.
    ELSE.
      IF g_flag = 'X'.
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
        PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                    c_werks.
        PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
      ELSE.
        IF g_flag1 = 'X'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        'RMMG1-VTWEG'.
          PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                      c_werks.
          PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                        c_vkorg.
          PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                        c_vtweg.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                         '=ENTR'.
        ENDIF.
      ENDIF.
    ENDIF.
*Processing of SCM View
    PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
    PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_DOS_FRM'
                                  t_mdata-zzjp_dos_frm.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_APRN'
                                  t_mdata-zzjp_aprn.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CON_ID'
                                  t_mdata-zzjp_con_id.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_NYU_SOP'
                                  t_mdata-zzjp_nyu_sop.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_WEI_TAB'
                                  t_mdata-zzjp_wei_tab.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR'
                                  t_mdata-zzjp_car.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS'
                                  t_mdata-zzjp_cas.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR_SIZE'
                                  t_mdata-ZZJP_CAR_SIZE.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS_SIZE'
                                  t_mdata-ZZJP_CAS_SIZE.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RUPQTY'
                                   t_mdata-ZZJP_RUPQTY.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_BIO'
                                  t_mdata-zzjp_bio.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_ITF'
                                  t_mdata-zzjp_itf.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_INIT_LS'
                                  t_mdata-zzjp_init_ls.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE1'
                                  t_mdata-zzjp_re1.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE2'
                                  t_mdata-zzjp_re2.
    PERFORM f_bdc_field       USING 'MARC-ZZJP_RE3'
                                  t_mdata-zzjp_re3.
    PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
*Processing of SD View
    PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
    PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_PRO_ID'
                                  t_mdata-zzjp_pro_id.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_BU_ID'
                                  t_mdata-zzjp_bu_id.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_NAME'
                                  t_mdata-zzjp_abv_name.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID1'
                                  t_mdata-zzjp_abv_id1.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID2'
                                  t_mdata-zzjp_abv_id2.
    PERFORM f_bdc_field       USING 'MVKE-ZZJP_SPL_ID'
                                  t_mdata-zzjp_spl_id.
    PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
    PERFORM f_bdc_dynpro      USING 'SAPLSPO1' '0300'.
    PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                  '=YES'.
perform f_bdc_insert.
REFRESH T_BDCDATA.
ENDLOOP.
ENDFORM.                    " F_PROCESS_BDC
*&      Form f_bdc_dynpro
p_prog is the program name to which data is passed                *
p_dyno is the screen number to which the data is passed
    Routine for populating the BDCDATA structure with the
    Screen related information
FORM f_bdc_dynpro USING    p_prog
                           p_dyno.
t_bdcdata-program = p_prog.
t_bdcdata-dynpro   = p_dyno.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " F_bdc_dynpro
*&      Form F_BDC_FIELD
      p_fnam is the field name to which value is passed
      p_fval is the field value which is passed
   p_fnam is the field name to which value is passed
   p_fval is the field value which is passed
FORM f_bdc_field USING    p_fnam
                          p_fval.
t_bdcdata-fnam = p_fnam.
t_bdcdata-fval = p_fval.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " F_bdc_field
*&      Form F_PROCESS_DATA                                          *
     Routine to used for moving data from T_bpcs internal table to *
     t_mdata Internal Table                                         *
FORM f_process_data.
LOOP AT t_bpcs.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              input = t_bpcs-matnr
         IMPORTING
              output = t_mdata-matnr.
    MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
    MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
    MOVE t_bpcs-idcode TO t_mdata-zzjp_con_id.
    MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
    MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
    MOVE c_blank TO t_mdata-zzjp_bio.
    MOVE c_blank TO t_mdata-zzjp_itf.
    MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
    MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
    MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
    MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
    MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
    MOVE c_intls TO t_mdata-zzjp_init_ls.
    MOVE c_blank TO t_mdata-zzjp_re1.
    MOVE c_blank TO t_mdata-zzjp_re2.
    MOVE c_blank TO t_mdata-zzjp_re3.
    MOVE c_blank TO t_mdata-zzjp_pro_id.
    MOVE c_blank TO t_mdata-zzjp_bu_id.
    MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
    MOVE c_blank TO t_mdata-zzjp_abv_id1.
    MOVE c_blank TO t_mdata-zzjp_abv_id2.
    MOVE c_blank TO t_mdata-zzjp_spl_id.
    APPEND t_mdata.
ENDLOOP.
ENDFORM.                    " F_PROCESS_DATA
*&      Form f_bdc_close
      Routine to close the BDC Session
FORM f_close_group.
CALL FUNCTION 'BDC_CLOSE_GROUP'
       EXCEPTIONS
            not_open    = 1
            queue_error = 2
            OTHERS      = 3.
IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " f_close_group
*&      Form f_bdc_insert
     routine to input batch data into the Transaction MM02 from the
     session created
FORM f_bdc_insert.
CALL FUNCTION 'BDC_INSERT'
         EXPORTING
              tcode            = c_tcode
         TABLES
              dynprotab        = t_bdcdata
         EXCEPTIONS
              internal_error   = 1
              not_open         = 2
              queue_error      = 3
              tcode_invalid    = 4
              printing_invalid = 5
              posting_invalid = 6
              OTHERS           = 7.
    IF sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDFORM.                    " f_bdc_insert
Reward Points if it is helpful
Thanks
Seshu

Need of SQL query in selecting distinct values from two tables

hi,
I need a query for selecting distinct values from two tables with one condition.
for eg:
there are two tables a & b.
in table a there are values like age,sex,name,empno and in table b valuses are such as age,salary,DOJ,empno.
here what i need is with the help of empno as unique field,i need to select distinct values from two tables (ie) except age.
can anybody please help me.
Thanks in advance,
Ratheesh

Not sure what you mean either, but perhaps this will start a dialog:
SELECT DISTINCT a.empno,
                a.name,
                a.sex,
                b.salary,
                b.doj
FROM    a,
        b
WHERE   a.empno = b.empno;Greg

Serious performance problem - SELECT DISTINCT x.JDOCLASSX FROM x

I am noticing a huge performance problem when trying to access a member that
is lazily loaded:
MonitorStatus previousStatus = m.getStatus();
This causes the following query to be executed:
SELECT DISTINCT MONITORSTATUSX.JDOCLASSX FROM MONITORSTATUSX
This table has 3 million records and this SQL statement takes 3 minutes to
execute! Even worse, my app heavily uses threads, so this statement is
executed in each of the 32 threads. As a result the application stops.
Is there any way that I can optimize this? And more importantly, can Kodo
handle a multithreaded app like this with a huge database? I've been having
a lot of performance problems since I've started doing stress & load
testing, and I'm thinking Kodo isn't ready for this type of application.
Thanks,
Michael

You can prevent this from happening by explicitly enumerating the valid
persistent types in a property. See
http://docs.solarmetric.com/manual.html#com.solarmetric.kodo.PersistentTypes
for details.
>
Inconveniently, this nugget of performance info is not listed in the
optimization guide. I'll add in an entry for it.This setting did in fact prevent the query from running which fixed the
problem. It definitely belongs in the optimization guide.
And more importantly, can Kodo
handle a multithreaded app like this with a huge database? I've beenhaving
a lot of performance problems since I've started doing stress & load
testing, and I'm thinking Kodo isn't ready for this type of application.I'd like to find out more information about details about your issues. We
do a decent amount of stress / load testing internally, but there are
always use cases that we don't test. Please send me an email (I'm assuming
that [email protected] is not really your address) and let's
figure out some way to do an analysis of what you're seeing.This email is just for posting to usenet, to avoid spam. I'm now running my
app through stress/load testing so I hope to discover any remaining issues
before going into production. As of this morning the system seems to be
performing quite well. Now the biggest performance problem for me is the
lack of what I think is called "outer join". I know you'll have this in 3.0
but I'm suprised you don't have this already because not having it really
affects performance. I already had to code one query by hand with JDBC due
to this. It was taking 15+ minutes with Kodo and with my JDBC version it
only takes a few seconds. There are lots of anti-JDO people and performance
issues like this really give them ammunition. Overall I just have the
impression that Kodo hasn't been used on many really large scale projects
with databases that have millions of records.
Thanks for configuration fix,
Michael

Issue with "Select Distinct" query in Oracle 10g against Oracle 9i

Hi,
I would appreciate if some one help me here because it is really urgent.
We are upgrading our database from 9i to 10g.
There are the "Select distinct" queries in the code which populated the grid on the applications screens. We found a difference in 9i and 10g the way the result is populated for these queries. If "Select Distinct" query wihtout a order by clause is executed in 9i then the result is automatically sorted. But Oracle 10g does not do this.
We can change the queries adding order by clause but we are almost at the end of the testing and want to know if there is any way that we can do this from database settings. Would there be any impact of these settings change on overall operation of Oracle 10g?
I would appreciate if some one can help me here.
Thanks,
Dinesh

then the result is automatically sorted.No. Oracle may have done a sort operation to perform the distinct, but it still did not guarantee the order of your results.
In 10g and in 9i, if you want your results in a certain order you must use order by.

Select Distinct and join in ODI

Hi,
I have following task to perform: I am loading metadata into Planning dimension from Oracle database. I have two tables
1. "Sales"
Columns: Name, Number, Value
Sample Data:
Product 1, 10, 200
Product 2, 30, 100,
Product 1, 15, 500
2. P&R
Columns:
Name, Alias
Product 1, SampleSoda1
Product 2, SampleSoda2,
Resource 1, CanForSoda,
Resource 2, CO2
What I need to do is: I have to select name and alias from second table of all products that were sold.
So I need to select distinct Name from Table 1, naxt join it with Table 2 (so I have Name and Alias) and load it to planning.
I am a little confused how to do it.
Any help would be great!
Best regards,
Greg

Hi Greg,
What you can do is either :
- Create a yellow interface with your table Sales as source. Map the name column directly in the target. In the flow tab, click on your target and select "Distinct rows".
- Create a second interface, with your first interface as source. Select the "Use Temporary Interface as Derived Table (Sub-Select)" checkbox.
- Add your second datastore and join it. Or you can use a lookup table.
OR
- Create an interface with Sales and P&R as source (or set P&R as a lookup table).
- Go on the flow tab and select "Distinct rows".
If you've a lot a data in the first table, I would go for the first solution.
Hope it helps.
Regards,
JeromeFr
Edited by: JeromeFr on Feb 14, 2013 9:52 AM
To be more clear in the first step of solution 1

Select distinct in view

Similar Messages

Maybe you are looking for