Shp2SDO and measured shapes

Hi all,
Does anyone know whether shp2sdo for 9i will correctly convert measured shapefiles (X,Y,M)? I currently tried this with shp2sdo for 8.1.7 and it seems to ignore the M values both in the metadata (user_sdo_geom_metadata) and the control file.
Would upgrading to 9i solve the problem?
Thanks in advance,
Pano

Hello Pano,
Does the third dimension end up in the sqlldr control file, or is it just missing?
Upgrading will have no effect on the behavior of the shp2sdo converter with respect to measured shapes.
Regards,
Dan

Similar Messages

  • SHP2SDO and SQLLDR error.

    Hi,
    I've got a ESRI shape file and i've been trying to load into oracle 9i by converting it with shp2sdo and loading it with Sql loader. but i keep getting a features rejected. the following is the SQLLDR log file.
    Ive converted the same shape file to a mapinfo tab file and it loads fine through Easyloader. Any ideas what might be going wrong?
    Thanks,
    John.
    SQL*Loader: Release 9.2.0.1.0 - Production on Thu Aug 19 10:39:09 2004
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Control File: tblriversubbasins.ctl
    Data File: tblRiverSubBasins.dat
    Bad File: tblRiverSubBasins.bad
    Discard File: none specified
    (Allow all discards)
    Number to load: ALL
    Number to skip: 0
    Errors allowed: 50
    Bind array: 64 rows, maximum of 256000 bytes
    Continuation: 1:1 = 0X23(character '#'), in next physical record
    Path used: Conventional
    Table TBLRIVERSUBBASINS, loaded from every logical record.
    Insert option in effect for this table: TRUNCATE
    TRAILING NULLCOLS option in effect
    Column Name Position Len Term Encl Datatype
    MI_PRINX FIRST * | CHARACTER
    NAME NEXT * | CHARACTER
    NULL if NAME = BLANKS
    MS_CD NEXT * | CHARACTER
    NULL if MS_CD = BLANKS
    EU_CD NEXT * | CHARACTER
    NULL if EU_CD = BLANKS
    DIST_CD NEXT * | CHARACTER
    NULL if DIST_CD = BLANKS
    AREAKM2 NEXT * | CHARACTER
    FORDER NEXT * | CHARACTER
    TYPE NEXT * | CHARACTER
    NULL if TYPE = BLANKS
    SEG_CD_T NEXT * | CHARACTER
    NULL if SEG_CD_T = BLANKS
    GEOLOC DERIVED * COLUMN OBJECT
    *** Fields in GEOLOC
    SDO_GTYPE NEXT * | CHARACTER
    SDO_SRID NEXT * | CHARACTER
    SDO_ELEM_INFO DERIVED * VARRAY
    Terminator string : '|/'
    *** Fields in GEOLOC.SDO_ELEM_INFO
    X FIRST * | CHARACTER
    *** End of fields in GEOLOC.SDO_ELEM_INFO
    SDO_ORDINATES DERIVED * VARRAY
    Terminator string : '|/'
    *** Fields in GEOLOC.SDO_ORDINATES
    X FIRST * | CHARACTER
    *** End of fields in GEOLOC.SDO_ORDINATES
    *** End of fields in GEOLOC
    Record 592: Rejected - Error on table TBLRIVERSUBBASINS, column GEOLOC.SDO_ELEM_INFO.X.
    error converting data
    ORA-01722: invalid number
    Table TBLRIVERSUBBASINS:
    995 Rows successfully loaded.
    1 Row not loaded due to data errors.
    0 Rows not loaded because all WHEN clauses were failed.
    0 Rows not loaded because all fields were null.
    Space allocated for bind array: 215168 bytes(64 rows)
    Read buffer bytes: 1048576
    Total logical records skipped: 0
    Total logical records read: 996
    Total logical records rejected: 1
    Total logical records discarded: 0
    Run began on Thu Aug 19 10:39:09 2004
    Run ended on Thu Aug 19 10:39:25 2004
    Elapsed time was: 00:00:16.86
    CPU time was: 00:00:04.20

    Hi,
    Thanks for all your input.
    I've tried setting the NLS_LANG reg entry but it made no difference, I previously had set the NLS_LANG variable at the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE level, Which one is correct?
    The control file is as follows:
    LOAD DATA
    INFILE tblRiverSubBasins.dat
    TRUNCATE
    CONTINUEIF NEXT(1:1) = '#'
    INTO TABLE TBLRIVERSUBBASINS
    FIELDS TERMINATED BY '|'
    TRAILING NULLCOLS (
    MI_PRINX INTEGER EXTERNAL,
    NAME      NULLIF NAME = BLANKS,
    MS_CD      NULLIF MS_CD = BLANKS,
    EU_CD      NULLIF EU_CD = BLANKS,
    DIST_CD      NULLIF DIST_CD = BLANKS,
    AREAKM2,
    fORDER,
    TYPE      NULLIF TYPE = BLANKS,
    SEG_CD_T      NULLIF SEG_CD_T = BLANKS,
    GEOLOC COLUMN OBJECT
    SDO_GTYPE INTEGER EXTERNAL,
    SDO_SRID INTEGER EXTERNAL,
    SDO_ELEM_INFO VARRAY TERMINATED BY '|/'
    (X FLOAT EXTERNAL),
    SDO_ORDINATES VARRAY TERMINATED BY '|/'
    (X FLOAT EXTERNAL)
    below is the SQL script created by shp2sdo to create the table:
    -- tblRiverSubBasins.sql
    -- This script creates the spatial table.
    -- Execute this script before attempting to use SQL*Loader
    -- to load the tblRiverSubBasins.ctl file.
    -- This script will also populate the USER_SDO_GEOM_METADATA table.
    -- Loading the .ctl file will populate the TBLRIVERSUBBASINS table.
    -- To load the .ctl file, run SQL*Loader as follows
    -- substituting appropriate values:
    -- sqlldr username/password tblRiverSubBasins.ctl
    -- After the data is loaded in the TBLRIVERSUBBASINS table, you should
    -- migrate polygon data and create the spatial index
    -- Creation Date : Thu Aug 19 10:33:34 2004
    -- Copyright 1999, 2004 Oracle Corporation
    -- All rights reserved
    DROP TABLE TBLRIVERSUBBASINS;
    CREATE TABLE TBLRIVERSUBBASINS (
    MI_PRINX      NUMBER(38)
         PRIMARY KEY,
    NAME      VARCHAR2(100),
    MS_CD      VARCHAR2(22),
    EU_CD      VARCHAR2(24),
    DIST_CD      VARCHAR2(24),
    AREAKM2      NUMBER,
    fORDER      NUMBER,
    TYPE      VARCHAR2(22),
    SEG_CD_T      VARCHAR2(12),
    MI_STYLE VARCHAR2(254 BYTE),
    GEOLOC      MDSYS.SDO_GEOMETRY);
    DELETE FROM USER_SDO_GEOM_METADATA
    WHERE TABLE_NAME = 'TBLRIVERSUBBASINS' AND COLUMN_NAME = 'GEOLOC' ;
    INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
    VALUES ('TBLRIVERSUBBASINS', 'GEOLOC',
    MDSYS.SDO_DIM_ARRAY
    (MDSYS.SDO_DIM_ELEMENT('X', -180.000000000, 180.000000000, 0.500000000),
    MDSYS.SDO_DIM_ELEMENT('Y', -90.000000000, 90.000000000, 0.500000000)
    82086);
    COMMIT;
    The bad file contains the following:
    060.000000|
    #98600.000000|313060.000000|98600.000000|313080.000000|
    #98580.000000|313080.000000|98580.000000|313100.000000|
    #98420.000000|313100.000000|98420.000000|313120.000000|
    #98400.000000|313120.000000|98400.00000
    313140.00
    00|
    #98
    0.000000|313140.000000|98380.000000|313160.000000|
    #98
    0.000000|313160.000000|98360.000000|313180.000000|
    #98
    0.000000|313180.000000|98320.000000|313220.000000|
    #98
    0.000000|313220.000000|98300.000000|313260.000000|
    #98
    0.000000|313260.000000|98280.000000|313300.000000|
    #98
    0.000000|313300.000000|98260.000000|313340.000000|
    #98
    0.000000|313340.000000|98280.000000|313420.000000|
    #98
    0.000000|313420.000000|98260.000000|313480.000000|
    #98
    0.000000|313480.000000|98180.000000|313580.000000|
    #98
    0.000000|313580.000000|98200.000000|313660.000000|
    #98
    0.000000|313660.000000|98180.000000|313680.000000|
    #98
    0.000000|313680.000000|98160.000000|313700.000000|
    #98
    0.000000|313800.000000|98180.000000|313800.000000|
    #98
    0.000000|313840.000000|98200.000000|313840.000000|
    #98
    0.000000|313880.000000|98220.000000|313880.000000|
    #98
    #93100.000000|334660.000000|93080.000000|334660.000000|
    #93080.000000|334540.000000|93060.000000|334540.000000|
    #93060.000000|334220.000000|93040.000000|334220.000000|
    #93040.000000|334160.000000|93020.000000|334160.000000|
    #93020.000000|334120.000000|93000.000000|334120.000000|
    #93000.000000|334100.000000|92980.000000|334100.000000|
    #92980.000000|334060.000000|92960.000000|334060.000000|
    #92960.000000|334040.000000|92920.000000|334040.000000|
    #92920.000000|334000.000000|92900.000000|334000.000000|
    #92900.000000|333980.000000|92880.000000|333980.000000|
    #92880.000000|333940.000000|92860.000000|333940.000000|
    #92860.000000|333920.000000|92840.000000|333920.000000|
    #92840.000000|333900.000000|92820.000000|333900.000000|
    #92820.000000|333860.000000|92800.000000|333860.000000|
    #92800.000000|333820.000000|92780.000000|333820.000000|
    #92780.000000|333780.000000|92620.000000|333780.000000|
    #92620.000000|333800.000000|92600.000000|333800.000000|
    #92600.000000|333820.000000|92540.000000|333820.000000|
    #92540.000000|333840.000000|92480.000000|333840.000000|
    #92480.000000|333860.000000|91980.000000|333860.000000|
    #91980.000000|333840.000000|91940.000000|333840.000000|
    #91940.000000|333860.000000|91820.000000|333860.000000|
    #91820.000000|333880.000000|91640.000000|333880.000000|
    #91640.000000|333900.000000|91540.000000|333900.000000|
    #91540.000000|333920.000000|91480.000000|333920.000000|
    #91480.000000|333940.000000|91460.000000|333940.000000|
    #91460.000000|333960.000000|91440.000000|333960.000000|
    #91440.000000|333980.000000|91420.000000|333980.000000|
    #91420.000000|334000.000000|91400.000000|334000.000000|
    #91400.000000|334020.000000|91380.000000|334020.000000|
    #91380.000000|334040.000000|91360.000000|334040.000000|
    #91360.000000|334060.000000|91340.000000|334060.000000|
    #91340.000000|334080.000000|91320.000000|334080.000000|
    #91320.000000|334100.000000|91300.000000|334100.000000|
    #91300.000000|334120.000000|91280.000000|334120.000000|
    #91280.000000|334140.000000|91260.000000|334140.000000|
    #91260.000000|334160.000000|91240.000000|334160.000000|
    #91240.000000|334180.000000|91220.000000|334180.000000|
    #91220.000000|334200.000000|91200.000000|334200.000000|
    #91200.000000|334220.000000|91180.000000|334220.000000|
    #91180.000000|334240.000000|91160.000000|334240.000000|
    #91160.000000|334360.000000|91140.000000|334360.000000|
    #91140.000000|334380.000000|91120.000000|334380.000000|
    #91120.000000|334400.000000|91080.000000|334400.000000|
    #91080.000000|334440.000000|91060.000000|334440.000000|
    #91060.000000|334460.000000|91040.000000|334460.000000|
    #91040.000000|334500.000000|91060.000000|334500.000000|
    #91060.000000|334760.000000|91080.000000|334760.000000|
    #91080.000000|334780.000000|91120.000000|334780.000000|
    #91120.000000|334800.000000|91140.000000|334800.000000|
    #91140.000000|334820.000000|91200.000000|334820.000000|
    #91200.000000|334840.000000|91220.000000|334840.000000|
    #91220.000000|334880.000000|91240.000000|334880.000000|
    #91240.000000|334900.000000|91260.000000|334900.000000|
    #91260.000000|334940.000000|91280.000000|334940.000000|
    #91280.000000|334960.000000|91300.000000|334960.000000|
    #91300.000000|334980.000000|91340.000000|334980.000000|
    #91340.000000|335000.000000|91360.000000|335000.000000|
    #91360.000000|335020.000000|91380.000000|335020.000000|
    #91380.000000|335040.000000|91400.000000|335040.000000|
    #91400.000000|335060.000000|91420.000000|335060.000000|
    #91420.000000|335080.000000|91480.000000|335080.000000|
    #91480.000000|335100.000000|91500.000000|335100.000000|
    #91500.000000|335120.000000|91520.000000|335120.000000|
    #91520.000000|335180.000000|91540.000000|335180.000000|
    #91540.000000|335220.000000|91560.000000|335220.000000|
    #91560.000000|335240.000000|91580.000000|335240.000000|
    #91580.000000|335300.000000|91600.000000|335300.000000|
    #91600.000000|335320.000000|91620.000000|335320.000000|
    #91620.000000|335340.000000|91640.000000|335340.000000|
    #91640.000000|335360.000000|91660.000000|335360.000000|
    #91660.000000|335400.000000|91680.000000|335400.000000|
    #91680.000000|335420.000000|91700.000000|335420.000000|
    #91700.000000|335440.000000|91720.000000|335440.000000|
    #91720.000000|335460.000000|91740.000000|335460.000000|
    #91740.000000|335480.000000|91760.000000|335480.000000|
    #91760.000000|335500.000000|91780.000000|335500.000000|
    #91780.000000|335520.000000|91800.000000|335520.000000|
    #91800.000000|335540.000000|91820.000000|335540.000000|
    #91820.000000|335560.000000|91840.000000|335560.000000|
    #91840.000000|335620.000000|91860.000000|335620.000000|
    #91860.000000|335800.000000|91840.000000|335800.000000|
    #91840.000000|335820.000000|91820.000000|335820.000000|
    #91820.000000|335840.000000|91780.000000|335840.000000|
    #91780.000000|335960.000000|91760.000000|335960.000000|
    #91760.000000|336020.000000|91740.000000|336020.000000|
    #91740.000000|336060.000000|91720.000000|336060.000000|
    #91720.000000|336080.000000|91740.000000|336080.000000|
    #91740.000000|336120.000000|91760.000000|336120.000000|
    #91760.000000|336140.000000|91740.000000|336140.000000|
    #91740.000000|336160.000000|91680.000000|336160.000000|
    #91680.000000|336380.000000|91660.000000|336380.000000|
    #91660.000000|336420.000000|91640.000000|336420.000000|
    #91640.000000|336500.000000|91620.000000|336500.000000|
    #91620.000000|336560.000000|91600.000000|336560.000000|
    #91600.000000|336620.000000|91580.000000|336620.000000|
    #91580.000000|336660.000000|91560.000000|336660.000000|
    #91560.000000|336680.000000|91540.000000|336680.000000|
    #91540.000000|336760.000000|91560.000000|336760.000000|
    #91560.000000|336820.000000|91580.000000|336820.000000|
    #91580.000000|337100.000000|91600.000000|337100.000000|
    #91600.000000|337120.000000|91620.000000|337120.000000|
    #91620.000000|337140.000000|91640.000000|337140.000000|
    #91640.000000|337160.000000|91660.000000|337160.000000|
    #91660.000000|337180.000000|91640.000000|337180.000000|
    #91640.000000|337220.000000|91660.000000|337220.000000|
    #91660.000000|337240.000000|91740.000000|337240.000000|
    #91740.000000|337220.000000|91780.000000|337220.000000|
    #91780.000000|337240.000000|91840.000000|337240.000000|
    #91840.000000|337260.000000|91880.000000|337260.000000|
    #91880.000000|337280.000000|91920.000000|337280.000000|
    #91920.000000|337300.000000|91960.000000|337300.000000|
    #91960.000000|337320.000000|91980.000000|337320.000000|
    #91980.000000|337340.000000|92000.000000|337340.000000|
    #92000.000000|337360.000000|92020.000000|337360.000000|
    #92020.000000|337380.000000|92340.000000|337380.000000|
    #92340.000000|337360.000000|92640.000000|337360.000000|
    #92640.000000|337380.000000|92680.000000|337380.000000|
    #92680.000000|337400.000000|92720.000000|337400.000000|
    #92720.000000|337420.000000|92740.000000|337420.000000|
    #92740.000000|337440.000000|92760.000000|337440.000000|
    #92760.000000|337460.000000|92820.000000|337460.000000|
    #92820.000000|337480.000000|92840.000000|337480.000000|
    #92840.000000|337500.000000|92960.000000|337500.000000|
    #92960.000000|337520.000000|93000.000000|337520.000000|
    #93000.000000|337540.000000|93040.000000|337540.000000|
    #93040.000000|337560.000000|93120.000000|337560.000000|
    #93120.000000|337580.000000|93160.000000|337580.000000|
    #93160.000000|337600.000000|93180.000000|337600.000000|
    #93180.000000|337620.000000|93200.000000|337620.000000|
    #93200.000000|337640.000000|93220.000000|337640.000000|
    #93220.000000|337660.000000|93280.000000|337660.000000|
    #93280.000000|337680.000000|93340.000000|337680.000000|
    #93340.000000|337700.000000|93360.000000|337700.000000|
    #93360.000000|337720.000000|93400.000000|337720.000000|
    #93400.000000|337740.000000|93420.000000|337740.000000|
    #93420.000000|337760.000000|93440.000000|337760.000000|
    #93440.000000|337780.000000|93460.000000|337780.000000|
    #93460.000000|337800.000000|93480.000000|337800.000000|
    #93480.000000|337820.000000|93500.000000|337820.000000|
    #93500.000000|337880.000000|93520.000000|337880.000000|
    #93520.000000|337920.000000|93540.000000|337920.000000|
    #93540.000000|337940.000000|93560.000000|337940.000000|
    #93560.000000|337960.000000|93580.000000|337960.000000|
    #93580.000000|337980.000000|93600.000000|337980.000000|
    #93600.000000|338000.000000|93680.000000|338000.000000|
    #93680.000000|338020.000000|93740.000000|338020.000000|
    #93740.000000|338040.000000|93780.000000|338040.000000|
    #93780.000000|338060.000000|93820.000000|338060.000000|
    #93820.000000|338080.000000|93840.000000|338080.000000|
    #93840.000000|338100.000000|93880.000000|338100.000000|
    #93880.000000|338120.000000|93920.000000|338120.000000|
    #93920.000000|338140.000000|93960.000000|338140.000000|
    #93960.000000|338160.000000|93980.000000|338160.000000|
    #93980.000000|338180.000000|94000.000000|338180.000000|
    #94000.000000|338200.000000|94400.000000|338200.000000|
    #94400.000000|338220.000000|94440.000000|338220.000000|
    #94440.000000|338200.000000|94420.000000|338200.000000|
    #94420.000000|338160.000000|94380.000000|338160.000000|
    #94380.000000|338120.000000|94360.000000|338120.000000|
    #94360.000000|338000.000000|94320.000000|338000.000000|
    #94320.000000|337980.000000|94300.000000|337980.000000|
    #94300.000000|337960.000000|94280.000000|337960.000000|
    #94280.000000|337940.000000|94260.000000|337940.000000|
    #94260.000000|337920.000000|94240.000000|337920.000000|
    #94240.000000|337720.000000|94260.000000|337720.000000|
    #94260.000000|337660.000000|94240.000000|337660.000000|
    #94240.000000|337640.000000|94220.000000|337640.000000|
    #94220.000000|337500.000000|94200.000000|337500.000000|
    #94200.000000|337460.000000|94180.000000|337460.000000|
    #94180.000000|337380.000000|94160.000000|337380.000000|
    #94160.000000|337320.000000|94140.000000|337320.000000|
    #94140.000000|337300.000000|94120.000000|337300.000000|
    #94120.000000|337260.000000|94100.000000|337260.000000|
    #94100.000000|336820.000000|94060.000000|336820.000000|
    #94060.000000|336800.000000|94020.000000|336800.000000|
    #94020.000000|336780.000000|93980.000000|336780.000000|
    #93980.000000|336740.000000|93960.000000|336740.000000|
    #93960.000000|336700.000000|93940.000000|336700.000000|
    #93940.000000|336640.000000|93920.000000|336640.000000|
    #93920.000000|336620.000000|93900.000000|336620.000000|
    #93900.000000|336360.000000|93880.000000|336360.000000|
    #93880.000000|336260.000000|93860.000000|336260.000000|
    #93860.000000|336220.000000|93840.000000|336220.000000|
    #93840.000000|336180.000000|93820.000000|336180.000000|
    #93820.000000|336160.000000|93800.000000|336160.000000|
    #93800.000000|336140.000000|93620.000000|336140.000000|
    #93620.000000|336120.000000|93600.000000|336120.000000|
    #93600.000000|336040.000000|93560.000000|336040.000000|
    #93560.000000|336020.000000|93520.000000|336020.000000|
    #93520.000000|335980.000000|93480.000000|335980.000000|
    #93480.000000|335920.000000|93460.000000|335920.000000|
    #93460.000000|335900.000000|93440.000000|335900.000000|
    #93440.000000|335720.000000|93400.000000|335720.000000|
    #93400.000000|335700.000000|93380.000000|335700.000000|
    #93380.000000|335680.000000|93360.000000|335680.000000|
    #93360.000000|335660.000000|93380.000000|335660.000000|
    #93380.000000|335580.000000|93360.000000|335580.000000|
    #93360.000000|335480.000000|93380.000000|335480.000000|
    #93380.000000|335400.000000|93420.000000|335400.000000|
    #93420.000000|335320.000000|93440.000000|335320.000000|
    #93440.000000|335300.000000|93460.000000|335300.000000|
    #93460.000000|335280.000000|93480.000000|335280.000000|
    #93480.000000|335220.000000|93500.000000|335220.000000|
    #93500.000000|335160.000000|93520.000000|335160.000000|
    #93520.000000|335140.000000|93540.000000|335140.000000|
    #93540.000000|335040.000000|/

  • Possible to limit dimensions and measures when creating presentations?

    We are trying to use OLAP/BI Beans to add BI functionality to our next-generation data warehouse application. This application has its own security framework, with the ability to define permissions/privileges for objects. We need to integrate BI Beans/OLAP with this security framework.
    One of the things we need to do is control which OLAP objects (like dimensions and measures) are available to a given user in the Items tab when creating a presentation. For example, user A might see dimensions Alpha, Bravo and measure Charlie, while user B might see dimensions Delta, Echo and measure Foxtrot.
    We need to be able to apply these dimension/measure restrictions without using different Oracle users, with each having access only to their own OLAP objects. Our data warehousing application does not use Oracle and Oracle users to control security; it has its own internal frameworks for privileges/permissions. We therefore need to find a way to restrict access to OLAP objects in some programmatic way.
    Here's an example of how this might work:
    - I am a clinical analyst. I sign on to the data warehouse application. The data warehouse knows that as a clinical analyst, I have access to a certain list of objects and functionality across the application. One of the apps I have privilege to is the BI Bean Presentation Creation Application, so I click the menu to bring this up. I can now create BI presentations, but since I am a clinical analyst my list of available dimensions and measures do not contain any of the G/L, payroll or other financial OLAP objects.
    - If I signed onto the data warehousing application as a different user, one that has a financial analyst role, I might see a different set of OLAP objects when I run the presentation application application.
    So what we need is some API way to specify which dimensions and measures are available to a given user when they launch the presentation wizard. I've been digging through the BI Beans help and javadoc and have found a few things, but they aren't what I need.
    Here's what I found:
    - setItemSearchPath: this allows you to specify which folders are to be displayed. We want control at the OLAP object level, not at the folder level, so this doesn't work for us
    - setVisibleDimensions: this controls which dimensions are available in the Dimensions tab, not which dimensions can be selected in the Items tab. Doesn't work for us
    - setDimensionContext/setMeasureContext: These might work for us but I haven't been able to get them to retrieve anything yet. It also seems to me that these might set which dimensions/members are initially selected in the Items tab, not the list of dims/measures that are available for selection.
    Any assistance on this matter would be greatly appreciated.
    s.l.

    Reply from one of our developers:
    The get/setMeasureContext and get/setDimensionContext methods are currently only used by the Thick CalcBuilder (in a few limited scenarios) and cannot be used "to scope the dimensions and measures listed in Query and Calc builder based on user access rights".
    The scoping of dimensions and measures based on user access rights should be performed at the MetadataManager/Database level.
    This may change going forward as the real issue here is the static nature of the metadata and a general issue with the GRANT option within the database. So from the database perspective it is not possible to grant select priviledges on a single column of a table.
    The metadata issue is more complex as the OLAP API reads the metadata only once on startup of a session. The list of available measures is based on the GRANT priviledge, so for relational OLAP this limits the data scoping capabilities. In 10g, the metadata for AW OLAP becomes more dynamic and contained and read directly from the AW. Therefore, with an AW OLAP implementation with 10g it could be possible to scope boht dimensions and measures quickly and easily.
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • [svn:fx-trunk] 9407: Reordering the if-statement in isMeasureFixed() exposed that hostFormat can be null when measure() is called if styles changed and measure is done before the next commitProperties .

    Revision: 9407
    Author:   [email protected]
    Date:     2009-08-19 15:11:34 -0700 (Wed, 19 Aug 2009)
    Log Message:
    Reordering the if-statement in isMeasureFixed() exposed that hostFormat can be null when measure() is called if styles changed and measure is done before the next commitProperties.  This states test exposed this.
    We should rethink if we want to clear hostFormat rather than have a hostFormatChanged flag.  If there is no hostFormat at measure then it has to be fixed because there is no line break format to check for auto-size.
    QE notes:
    Doc notes:
    Bugs: SDK-22779
    Reviewer: Gordon
    Tests run: checkintests
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22779
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/RichEditableText.as

    Oh my god, it is too long! You definitely check out types, casting and especially ODP.Net (it does everything for you)... etc. They can help you to simplify your code. I do not have enough time to copy paste it to Studio and understand and solve your issue, so I got title of your message as your main question.
    In Oracle, you can create an autonumber field by using sequences object. This is really useful when you need to create a unique number to act as a primary key.
    Basically you can create a sequence simply typing;
    CREATE SEQUENCE MY_SEQUENCE;
    now you have a sequence called "MY_SEQUENCE"... Then, I advice you select a number from sequence;
    select MY_SEQUENCE.nextval from dual;
    I said I advice actually kinda must, although it called sequence, I cannot be sequential. Do not even try to predict the value. You can be sure that it is unique number so you can use it.
    Then insert you record and use that number part of your primary key. I think that's it. Have fun.

  • Function Modules for creation of characteristics and Measurement Points

    Hello everybody
    I'm new in ABAP (trainee) and especially the use of characteristics. I'd be very happy if somebody could help me :).
    Can anybody out there with some experience in creating characteristics and measurement points tell me how to create them with function-modules or by changing database tables?
    I'm happy about every hint and ready to give some reward points.
    Best Regards,
    Steffen

    FM and TABLES
    http://72.14.235.104/search?q=cache:71IXBMWcX_8J:reflexcontracts.co.uk/SAP_R3_QUICK_REF.xlsupdatetable+tse05&hl=en&ct=clnk&cd=1&gl=in
    FUNCTION MODULES
    http://www.erpgenie.com/abap/functions.htm
    http://www.sapdevelopment.co.uk/fmodules/fmssap.htm
    http://www.erpgenie.com/abap/index.htm
    http://www.geocities.com/victorav15/sapr3/abapfun.html
    Rewards if useful..........................
    Minal

  • Setting currency and measurement unit for a field in an ALV report

    Plz give sample code to set currency and measurement unit for a field in an ALV report

    dear friend
    i am seanding you
    the display form
    if you need select form
    and process form also pls keep in touch.
    if help full rewards are expecting.
    yours
    vivek
    FORM build_field_catalog .
      DATA: w_dthigh(10).
      CLEAR fcat.
      fcat-fieldname = 'VBELN'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'COMMERCIAL INVOICE'.
      fcat-seltext_m = 'Commercial Invoice'.
      fcat-seltext_l = 'COMMERCIAL INVOICE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-key = 'X'.
      fcat-hotspot = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'EXNUM'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'EXCISE INVOICE'.
      fcat-seltext_m = 'Excise Invoice'.
      fcat-seltext_l = 'EXCISE INVOICE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-hotspot = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'EXDAT'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'EXCISE DATE'.
      fcat-seltext_m = 'Excise Date'.
      fcat-seltext_l = 'EXCISE DATE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'D'.
      fcat-datatype = 'DATS'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'NAME1'.
      fcat-outputlen = 30.
      fcat-seltext_s = 'CUSTOMER'.
      fcat-seltext_m = 'Customer'.
      fcat-seltext_l = 'CUSTOMER'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-lowercase = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'ZZPD'.
      fcat-outputlen = 15.
      fcat-seltext_s = 'COUNTRY'.
      fcat-seltext_m = 'COUNTRY'.
      fcat-seltext_l = 'COUNTRY'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-lowercase = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'WERKS'.
      fcat-outputlen = 4.
      fcat-seltext_s = 'PLANT'.
      fcat-seltext_m = 'Plant'.
      fcat-seltext_l = 'PLANT'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-key = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'ARKTX'.
      fcat-outputlen = 40.
      fcat-seltext_s = 'MATERIAL DESCRIPTION'.
      fcat-seltext_m = 'Material Description'.
      fcat-seltext_l = 'MATERIAL DESCRIPTION'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-lowercase = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'FKART'.
      fcat-outputlen = 4.
      fcat-seltext_s = 'Billing type'.
      fcat-seltext_m = 'Billing type'.
      fcat-seltext_l = 'Billing type'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-key = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'INCO1'.
      fcat-outputlen = 5.
      fcat-seltext_s = 'INCO TERMS'.
      fcat-seltext_m = 'INCO TERMS'.
      fcat-seltext_l = 'INCO TERMS'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'INCO2'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'INCO TERMS DES'.
      fcat-seltext_m = 'INCO TERMS DES'.
      fcat-seltext_l = 'INCO TERMS DES'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      APPEND fcat.
    CLEAR fcat.
    fcat-fieldname = 'FKIMG'.
    fcat-outputlen = 14.
    fcat-seltext_s = 'QUANTITY'.
    fcat-seltext_m = 'Quantity'.
    fcat-seltext_l = 'QUANTITY'.
    fcat-ddictxt = 'M'.
    fcat-inttype = 'P'.
    fcat-datatype = 'QUAN'.
    APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'FKLMG'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'QUANTITY'.
      fcat-seltext_m = 'QUANTITY'.
      fcat-seltext_l = 'QUANTITY'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'QUAN'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'MEINS'.
      fcat-outputlen = 5.
      fcat-seltext_s = 'UNIT'.
      fcat-seltext_m = 'UNIT'.
      fcat-seltext_l = 'UNIT'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'KBETR'.
      fcat-outputlen = 8.
      fcat-seltext_s = 'RATE'.
      fcat-seltext_m = 'Rate'.
      fcat-seltext_l = 'RATE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'NSR'.
      fcat-outputlen = 8.
      fcat-seltext_s = 'Exmill'.
      fcat-seltext_m = 'Exmill'.
      fcat-seltext_l = 'Exmill'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'KURSK'.
      fcat-outputlen = 8.
      fcat-seltext_s = 'EXCHANGE RATE'.
      fcat-seltext_m = 'Exchange Rate'.
      fcat-seltext_l = 'Exchange Rate'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'WAERK'.
      fcat-outputlen = 5.
      fcat-seltext_s = 'CURRENCY'.
      fcat-seltext_m = 'Currency'.
      fcat-seltext_l = 'CURRENCY'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CUKY'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'LCURR1'.
      fcat-outputlen = 14.
      fcat-seltext_s = 'GROSS AMT'.
      fcat-seltext_m = 'Gross Amt'.
      fcat-seltext_l = 'GROSS AMT'.
      fcat-ddictxt = 'L'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
    fcat-do_sum = 'X'.
      APPEND fcat.
    ================================= *****************
      fheader-typ = 'H'.
      SELECT SINGLE butxt
        FROM t001
        INTO fheader-info
       WHERE bukrs EQ '1000'.
      APPEND fheader.
      CLEAR fheader.
      fheader-typ = 'H'.
      fheader-info = 'Daily Shipments For Exp'.
      APPEND fheader.
      CLEAR fheader.
    Plant
      SORT s_werks BY low.
      READ TABLE s_werks INDEX 1.
      fheader-typ = 'S'.
      WRITE s_werks-low TO fheader-key.
      SORT s_werks BY high DESCENDING.
      READ TABLE s_werks INDEX 1.
      IF s_werks-high NE space.
        CONCATENATE fheader-key 'TO' s_werks-high INTO fheader-info
                                SEPARATED BY space.
      ELSE.
        WRITE fheader-key TO fheader-info.
      ENDIF.
      CLEAR fheader-key.
      fheader-key = 'PLANT : '.
      APPEND fheader.
      CLEAR fheader.
    Billing Typ
    SORT S_FKART BY LOW.
    READ TABLE S_FKART INDEX 1.
    FHEADER-TYP = 'S'.
    WRITE S_FKART-LOW TO FHEADER-KEY.
    SORT S_FKART BY HIGH DESCENDING.
    READ TABLE S_FKART INDEX 1.
    IF S_FKART-HIGH NE SPACE.
    CONCATENATE FHEADER-KEY 'TO' S_FKART-HIGH INTO FHEADER-INFO
                             SEPARATED BY SPACE.
    ELSE.
       WRITE FHEADER-KEY TO FHEADER-INFO.
    ENDIF.
    CLEAR FHEADER-KEY.
    FHEADER-KEY = 'DOCUMENT TYPE : '.
    APPEND FHEADER.
    CLEAR FHEADER.
    Date...
      fheader-typ = 'S'.
    FHEADER-KEY = S_FKDAT-LOW.
      WRITE s_fkdat-low  TO fheader-key.
      WRITE s_fkdat-high TO w_dthigh.
      CONCATENATE fheader-key 'TO' w_dthigh INTO fheader-info
                              SEPARATED BY space.
      CLEAR fheader-key.
      fheader-key = 'PERIOD : '.
      APPEND fheader.
      CLEAR fheader.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
        EXPORTING
          i_list_type     = 0
        IMPORTING
          et_events       = fevents[]
        EXCEPTIONS
          list_type_wrong = 1
          OTHERS          = 2.
      READ TABLE fevents WITH KEY name = 'TOP_OF_PAGE'.
      IF sy-subrc = 0.
        fevents-form = 'TOPOFPAGE'.
        MODIFY fevents INDEX sy-tabix.
        CLEAR fevents.
      ENDIF.
      rptname = sy-repid.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
                        EXPORTING
                          i_callback_program                = rptname
                          it_fieldcat                       = fcat[]
                          i_default                         = 'S'
                          it_events                         = fevents[]
                          i_save                            = 'X'
                         TABLES
                           t_outtab                          = it_output[]
                      EXCEPTIONS
                        PROGRAM_ERROR                     = 1
                        OTHERS                            = 2
    ENDFORM.                    " BUILD_FIELD_CATALOG

  • Bi beans- i can't see my dimensions and measures!!!!

    hye! i have cretaed 2 cubes in oem (rolap)...
    i inserted some information in the tables (some tables are empty)...
    anyways...
    now, when i try to connect to olap from jdev it's working!!!!!
    but, when i try to make a graph or anything a can't see any of the stuff that i made in oem:::
    bi designer---new graph---on the step 2 of 8 the only things available are:
    - financial data
    - sales performance data
    (dimensions and measures from bibdemo i think....)
    where are my dimensions and measures???????????
    i tryded to copy objects from remote catalog... and make new catalog connection... with bibcat but it's not working!
    but i think this was not the thing to do!!!!!
    what shoul i do next??????
    help asap!!!! plezzzz!!!!

    Did you execute the following after defining your OLAP Catalog metadata in OEM?
    EXECUTE CWM2_OLAP_METADATA_REFRESH.MR_REFRESH;
    The CWM2_OLAP_METADATA_REFRESH package provides procedures that refresh the cached metadata tables used by the OLAP API / BI Beans. This step is required to 'see' your ROLAP cubes. Unfortunately, OEM does not execute this package. It must be done manually.
    Please refer to the OLAP Application Developer's Guide 9.2.0.4.1 or OLAP Reference 9.2.0.4.0. You can find them on OTN at the OLAP site:
    http://www.oracle.com/technology/products/bi/olap/olap.html

  • Is it possible to group the dimensions and measures into respective folders in SAP BO Analysis office - excel?

    Hi Guys,
    We can group the similar dimensions or measures into folders in Universe which can be further consumed in other BO reporting tools.
    Is it possible to do the same while connecting AO with HANA?
    I want to group similar dimensions and measures so that it comes as respective folders in AO and makes the experience for the user better. Is it possible?
    Regards,
    Krishna Tangudu

    Hi Michael,
    Thanks for your reply. If this feature is not present or not in the roadmap too then i might have to follow the same solution as well.
    Hoping Tammy Powlas has some answer for this.
    Regards,
    Krishna Tangudu

  • Enable Commenting and Measuring without a mouse

    I work for a large nonprofit with no tech department. (I'm on a mac OS 10.6, others have OS 10.7) We've just upgraded 3 of us to Acrobat Pro X (from Acrobat Pro 7).
    I need to be able to do the following to many many files every day -  with fewer than 2 mouseclicks.
    File > Save As > Reader Extended PDF > Enable Commenting and Measuring ... [confirm over wright in same folder on the shared (windows) server] ... [close document]
    Best case scenario: Adobe makes this an export option in inDesign, where it belongs.
    Next best: a "droplet" app that can enable many PDFs  at once.
    Next best: a working applescript that I can invoke from my script menu
    Next best: <sigh> an adobe Action that I can script in Acrobat
    Next best: working javascript code that someone can help me figure out how to deploy for 3 users...

    The scrolling option is now in System Preferences > Universal Access > mouse & trackpad tab > mouse options.. button > check scrolling.

  • Making system settings for measurement documents and measuring point

    What is the significance of making system settings for measurement documents and measuring point in spro?
    Edited by: Pallavi Kakoti on Jul 14, 2011 1:23 PM

    Hi,
    << Moderator message - Cut and paste response from http://www.consolut.com/en/s/sap-ides-access/d/s/doc/YY-OLI0IMRCCUST removed. Plagiarism is not allowed in SCN >>
    Regrds
    Jitender
    Edited by: Rob Burbank on Jun 6, 2011 10:53 AM

  • Relation between notification no and measuring point no or document

    Dear Expert's
    I want to link between notification no (qmnum) and measuring point no or measuring point document.
    I want to search measuring point number thorough notification no.
    plz suggest me ABAP purpose.
    thanks.
    regards:
    Neelesh Sonkar

    Hi,
    1. Get the EQUNR from the table "QMIH" using QMNUM.
    2. Get the MOVING_OBJECT from the table "IEQT_WL_MP" using EQUNR.
    3. Get the MDOCM (Measurement Document) POINT (Measuring Point) from the table "IMRG"
        using MOVING_OBJECT ( which is MDOCM ).
    Hope this will help you.
    Regards,
    Smart Varghese

  • Reg: measuring point creation and measuring point counter creation

    how to create measuring point and measuring point counter.
    what is the difference between these two.
    what is measuring point category,
    what is measuring point
    what is measuring point object
    what is measuring position.
    can anyone explain me in an easy for better understanding.

    Firstly a Measuring point is nothing but, a factor which you measure on an equipment/FL. (Temperature, Vibration etc)
    Then, a measuring point is created either on a Functional location or on an Equipment.
    IK01 is the T-code for creating it.
    If it is for F/L you have to use IFL as measuring point object, when it is an equipment you use IEQ
    Generally these two will be in use.
    In the IK01 screen if you tick the counter checkbox, the MP becomes a counter.
    Example for simple MP is temperature.
    And example for a Counter MP is 'Litres of petrol consumed'
    In the first case you don't need to add the temperature measurements, whereas in the petrol consumption you may wish to have the cumulative value of readings taken for a period of time.
    The measuring position: Example : If you are measuring the temperature of a Motor on the Drive side, you may put 'Drive End' in this field, or similar many applications.
    Category would group these MPs.
    In case of need you may define in customisation a sep[arate MP category.
    Then each time you read a MP through IK11 or other methods a Measuring Document is created.
    Regards
    Jogeswara Rao

  • How to create cube and measure in sql?

    How to create cube and measure in sql?

    Cubes, measures and dimensions are created in the AW using the Java API for Analytic Workspaces or through XML documents that are processed by this API. SQL commands are not available for creating cubes, measures or OLAP dimensions.

  • Use business indicator and measurements

    I'm working with 11g
    I have try to use business indicator (BI) and measurements. I found the istruction on " Getting started" ( and in Oracle documentation too)
    I have created :
    - BI dimension string --> that is associated at string variable typeDocument of the iniziator human task
    - BI mesurament int --> single
    - BI (numberTypeDocument) counter associated at the human task
    I set new dashboard in workspace. In "Data sources" I define :
    - Dimension
    Series --> Revision ( default)
    Group --> with BI dimension
    - Measure
    Variable -->with BI mesurament
    Operation type --> sum
    Value type     --> variable
    - Filter --> Revision(default)
    BUt I don't see nothing
    Can you help me?

    I have find .....
    http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15731/bam.htm
    Go to Tools > Internet Options > Security > Trusted sites and click Sites.
    Uncheck Require server verification (https:) for all sites in this zone if necessary (it is necessary unless you have Oracle BAM set up for SSL).
    Add the Oracle BAM URL to the list:  http://<bam_servername>
    I try at create BAM data object ....
    thanks
    Elena

  • Keithley source and measure code

    Hi all,
    I an trying a code in Labview on Keithley 2400 instrument.
    here my requirement is on my block diagram i want to write a program for source and measure and that can list out the any  error in that instrument once i run the code. it will list the errors like error1,error2,.......like that.
    In the out put window i want to see the instrument serial number.
    GPIB address
    set volt, set current and limit.
    display the error.
    please suggest me how to do this.

    The driver should have an error query on the utility menu. Modify it for the extra functionality and save it with a new name.

Maybe you are looking for