Object data type

I ve created a variable that contains an array. Each array
element is a generic object that further contains an array n that
array again contains a generic object whith .x and .y properties..
Now i wanted this to pass to the asp. the problem is that i cant
extract the .x and .y values frm the variable passed in asp..
Please tell me what to do so that i can get the values ....thnx in
advance

You can't just pass a Flash array to ASP like that. If you
use remoting, you
can do things like that - but I've only used AMFPHP which is
a remoting
gateway for PHP. Not sure of one for ASP... Without remoting,
Flash passes
your variables just like a form would - using POST. You'll
need to serialize
your array into name/value pairs and pass those instead. Not
trivial with
nested arrays like you have. I just did a Google search on
'flash remoting
asp' and found quite a bit of info - so I'd suggest you look
into that. Once
you get remoting figured out you will never go back to the
old-school way of
getting and sending name/value pairs.
Dave -
Head Developer
http://www.blurredistinction.com
Adobe Community Expert
http://www.adobe.com/communities/experts/

Similar Messages

Oracle Object Data Type and EJB

Hi, All:
Has anyone implemented a project with Oracle user-defined data type (Object
Data Type) together
with EJB? That is, using ORDBMS (Object Relational Database) together with
EJB. I am thinking to use ORDBMS together with EJB. Any information, samples
and references to this direction is appreciated.
Thanks,
John Wen
RM2M, LLC
[email protected]

I''ve got a solution! I've had sql in my query
SELECT
ltrim(OPERATIVE_REPORT."orderText",11),
OPERATIVE_REPORT."resolID",
COUNT(OPERATIVE_REPORT."(usrID)order_executionUser")
FROM
OPERATIVE_REPORT
GROUP BY
ltrim(OPERATIVE_REPORT."orderText",11),
OPERATIVE_REPORT."resolID"
where orderText has clob datatype. And the reason is GROUP BY. GROUP BY deny CLOB usage.

Object Data Type support and JDBC2 SQLData interface

Another useful and probably easy to implement feature is to support
persistent-aware classes based on JDBC SQLData interface._
It will let us persist such a member of persistent class to an object
type column._
The interface is very simple and quite limited (no support for arrays
etc) but useful.
The only thing we would need is to maintain jdbc object maps for our
database connections and tell Kodo metadata not to enhance this
particular class member but treat is as a simple type_
Alex

In SPROXY you can open your proxy and then view the Activation Log under the GoTo menu. The log will explain better what the problems might be. In my case I needed to activate another data type enhancement first.
Thanks,
Matt

Pl/sql object data type and "instance of"

Hello!
I have an object datatype A, and two objects, B and C, which are subtypes of A.
Then I have a function taking one parameter of type "A". In runtime, I send an object of type "B" as parameter to this function, and I want to determine if the "A" object is an instance of type "B" or "C". A test similar to "instanceof" in Java. Is there a way to do this in pl/sql?
Thank you.
- Paul

If I understand correctly have you tried...
http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/conditions014.htm#sthref2978

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Issue with Info Object Transport after changing Data Type

Hi Experts,
We have a DSO which is running past 5 years. And recently(3 days back) we added new fields into that DSO. Delta loaded for last three days and new info object (Say XXX) data populated into DSO.
Now the problem is, We identified that, info object data type is not correct. We used data type NUMC instead of CHAR.So Character information is missing for that field.
Example:
Data from ECC: ABC123
Data Loaded to DSO: 123 (Missed character ABC)
So we deleted data from DSO and changed the info object data type in Development system.
And also I have deleted only last three days delta records from DSO and transported my info object to Production. But its giving error as: Info object contains data in DSO".
But that info object field is empty in DSO. I have already deleted last three days delta.
Do I need to Delete all 5 years data from DSO to change the data type of recently added new info object ?
Please give me your solutions and ideas to solve this issue.
Thank you,
Best Regards,
Santhosh

Hi Raman,
Thank you for your answer.
When I changed the data type of info object in Dev, I deleted the content of DSO. And same thing transported to QA as well. Before importing changed info object, I just deleted the content of DSO from QA. So transport done successfully QA.
But in Production we have a history of past 5 years. So I cant delete all contents of DSO.
So just deleted only the delta request's which contains data for that info object(3 days back, we moved that info object(NUMC data type) to production,So last 3 days delta only loaded for that info object). And tried to transport it. But it was failed. I am sure we need to drop all data from DSO, if I am interested to go with same info object.
I have some comments on your first approach,
1. If we delete info objects from Dev DSO and transport to Production will give transport failure, Why because, my previous transports errors clearly saying that info object contains data in DSO . So it wont allow to remove that info object from DSO.
2.We are using same info object technical name in BO Data federator also. So if we change add new info objects again we need to make changes with BO as well. I am thinking this point as my last option if i cant find any other solution.
Thank you.
Best Regards.

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
 In the ABAP type concept, fields are called data objects. Each data object is an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data object as well as the name of a data type.
Data Types:
 As well as occurring as attributes of a data object, data types can also be defined independently. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program (using the TYPES statement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
 Data types can be divided into elementary, reference, and complex types
Data objects:
 Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their data type. You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
ABAP contains the following kinds of data objects
Literals
 Named Data Objects
Predefined Data Objects
Dynamic Data Objects

Data types and data objects

diff b/w data types and data objects

hi prasanth,
Data Types and Data Objects
Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
regards,
sravanthi

Date type attribute in web dynpro callable object

Hi all,
I am creating a callable object with date type attribute as input parameter in a web dynpro callable object.
date type I have used is java.sql.date.
But when I am exposing that callable object in GP its giving an error:
Technical Exception:
Web dynpro Component cannot be created.
And when i am changing date type as java.util.date then I am not able to asssign that date attribute in my view layout.
Can anyone plese help me.

Hi Ritu ,
u have to convert the util date to sql date in the execute method .
do it as showm below in Execute method in the component Controller :
let the Attribute be planEndDate in the Context:
public void execute( com.sap.caf.eu.gp.co.api.IGPExecutionContext executionContext ) {
java.util.Date planEndDate = null;
planEndDate = (java.util.Date) inputStructure.getAttributeAsDate(IContextElement.PLAN_ENDDATE);
java.sql.Date sqlDate = new java.sql.Date(planEndDate.getTime());
wdContext.currentContextElement().setPlanEnddate(sqlDate);
Thanks and Regards

Data type of Souce Object Vs BW Object

Hi All,
Our Source system is Oracle system.We have a field 'delivered date' (Database type is 'DATE' and Type in DDIC is 'DATS').
for example: 20.09.2005 08:17:15
Our requirement is to display this data as it is in BW report on ODS.
Shall go for BW infoObject with data type 'CHAR' ? does it lead to any issues while loading from oracle to BW as source data type is 'DATS' and BW Object data type is 'CHAR'?
Is necessary to maiantain same data types here?
If dont go with data type 'CHAR', it is not possible to display date and time together.
I have tested with flat file and it works fine.
Thanks

Hi,
Thanks for your reply.Thats what i had thought of doing.we need not represent it as Date as its combination of date and time.This is the only way to get it i guess.(defining 'CHAR' infoObject and mapping to 'DATS' of source field ).
Any other possibilities?
Thanks

Difference Between Data Type and Data Object

Difference Between Data Type and Data Object

hi magesh
Data types can be divided into
elementary,
reference, and
complex types.
Elementary Types
Elementary types are the smallest indivisible unit of types. They can be grouped as those with fixed length and those with variable length.
Fixed-Length Elementary Types
There are eight predefined types in ABAP with fixed length:
Four character types:
Character (C),
Numeric character (N),
Date (D),
and Time (T).
One hexadecimal type:
Byte field (X).
Three numeric types:
Integer (I),
Floating-point number (F)
and Packed number (P).
Variable-Length Elementary Types
There are two predefined types in ABAP with variable length:
STRING for character strings
XSTRING for byte strings
Reference Types
Reference types
describe data objects that contain references (pointers) to other objects (data objects and objects in ABAP Objects).
Data Types
1) As well as occurring as attributes of a data object, data types can also be defined independently.
2)You can then use them later on in conjunction with a data object.
3) The definition of a user-defined data type is based on a set of predefined elementary data types.
4) You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary.
5) You can use your own data types to declare data objects or to check the types of parameters in generic operations.
Data Objects
1)Data objects are the physical units with which ABAP statements work at runtime.
2) The contents of a data object occupy memory space in the program.
3) ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type..
4) For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
5) Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type).
6) You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures).
7) As well as fields in the memory area of the program, the program also treats literals like data objects.
hope this helps u,
reward points if useful
Ginni

Using OFFLINE_INSTANTIATION with a spatial object - SDO_GEOMETRY type

Hello
I am looking for guidance on the usage of DBMS_REPCAT_RGT.INSTANTIATE_OFFLINE for a table object with an SDO_GEOMETRY
column defined.
The table is:
SQL> descr jtx.jtx_jobs_aoi
Name Null? Type
OBJECTID NOT NULL NUMBER(38)
JOB_ID NUMBER(10)
SHAPE MDSYS.SDO_GEOMETRY
SE_ANNO_CAD_DATA BLOB
The mview is defined as:
CREATE MATERIALIZED VIEW jtx.JTX_JOBS_AOI REFRESH FAST WITH PRIMARY KEY FOR UPDATE AS
SELECT * FROM JTX.JTX_JOBS_AOI@ncgsdb_master_s;
And the command we are using is:
SQL> SET SERVEROUTPUT ON
SQL>
SQL> DECLARE
2 dt_num NUMBER;
3 BEGIN
4 dt_num := DBMS_REPCAT_RGT.INSTANTIATE_OFFLINE(
5 refresh_template_name => 'jtx_refg_dt',
6 user_name => 'jtx',
7 site_name => 'NCGSDB_MVSITE1',
8 next_date => SYSDATE,
9 interval => 'SYSDATE + (1/96)');
10 DBMS_OUTPUT.PUT_LINE('Template ID = ' || dt_num);
11 END;
12 /
When we run this on an 11.1.0.6 database we get:
DECLARE
ERROR at line 1:
ORA-30373: object data types are not supported in this context
ORA-06512: at "SYS.DBMS_REPCAT_RGT_CUST", line 1991
ORA-06512: at "SYS.DBMS_REPCAT_RGT", line 1330
ORA-06512: at line 4
Now the strange thing is this appears to work for ONLINE_INSTANTIATION.
1. Is this supported?
2. If so what are we doing wrong?
Thanks
Richard

Here a full example with CAST MULTISET as @PhilHerring wrote and with CAST COLLECT using the simplest possible function make_geometry:
CREATE OR REPLACE TYPE t_sdo_geometries AS TABLE OF MDSYS.sdo_geometry;
CREATE OR REPLACE FUNCTION make_geometry (p_points t_sdo_geometries)
RETURN t_sdo_geometries IS
BEGIN
RETURN p_points;
END;
SELECT make_geometry (
        t_sdo_geometries (
          sdo_geometry(2001, 32774, sdo_point_type(1, 1, null), null, null),
          sdo_geometry(2001, 32774, sdo_point_type(2, 2, null), null, null),
          sdo_geometry(2001, 32774, sdo_point_type(3, 3, null), null, null),
          sdo_geometry(2001, 32774, sdo_point_type(4, 4, null), null, null)))
        AS geom
FROM DUAL;
WITH geoms(pcol) AS
(SELECT sdo_geometry(2001, 32774, sdo_point_type(1, 1, null), null, null) FROM dual UNION ALL
SELECT sdo_geometry(2001, 32774, sdo_point_type(2, 2, null), null, null) FROM dual UNION ALL
SELECT sdo_geometry(2001, 32774, sdo_point_type(3, 3, null), null, null) FROM dual UNION ALL
SELECT sdo_geometry(2001, 32774, sdo_point_type(4, 4, null), null, null) FROM dual)
SELECT make_geometry(cast(multiset(select pcol from geoms a) as t_sdo_geometries)) FROM dual;
WITH geoms(pcol) AS
(SELECT sdo_geometry(2001, 32774, sdo_point_type(1, 1, null), null, null) FROM dual UNION ALL
SELECT sdo_geometry(2001, 32774, sdo_point_type(2, 2, null), null, null) FROM dual UNION ALL
SELECT sdo_geometry(2001, 32774, sdo_point_type(3, 3, null), null, null) FROM dual UNION ALL
SELECT sdo_geometry(2001, 32774, sdo_point_type(4, 4, null), null, null) FROM dual)
SELECT make_geometry(cast(collect(pcol) as t_sdo_geometries)) FROM geoms;
Hope that helps
_jum

Error while creating data type

Hi
I am creating data type for the scenario from File to IDOC
Namespace urn:xiworkshop:groupxx:legacy is not defined in the software component version NEWPRODUCT , 100 of sap Object Message Type Vendor | urn:xiworkshop:groupxx:legacy references the inactive object Data Type Vendor | urn:xiworkshop:groupxx:legacy
Please help me

Hi;
First activate your namespace and then create the data type.
Namespace + default datatypes should be activated together.
Then your data type
Mudit

Dates in BEx query coming into designer as a dimension with Char data type

This must be an old issue with a well documented work around ... but alas i can find it !
When i build a universe over a BEx query with dates the universe designer builds them as Dimensions of CHAR type not DATE. Therefore all WebI date functionality fails .. eg sorting, automatic time hierarchies etc.
What is the workaround ?
Andrew Fox

Is the data source an InfoSet or an InfoCube? It appears the date type object has not been implemented yet for Infosets. Here's SAP Note 1370410:
Symptom
Infoset date type objects (DATS type) are mapped as Character types in a universe based on a SAP BEX Query.
Prompts related to the Date field variables are coming as List of values instead of Calendar in WebIntelligence.
Reproducing the Issue
Create a BusinessOjects universe on a Super Query which is based on a multiprovider containing an Infoset or
Create a BEx superquery directly on Infoset.
BusinessObjects Enterprise XI 3.1
SAP Integrated Solutions Kit XI 3.1
Cause
This behaviour has been considered as an enhancement request and tracked under ADAPT01229917.
Resolution
This enhancement request is scheduled to be addressed in Service Pack 3 (SP3) for BusinessObjects Enterprise XI 3.1 due approximately April 2010.
I did try a BEx query that uses an InfoCUBE as a source and the objects are coming into the universe correctly as dates.

Display data type

hi,
how to display oralce's data type from system table is there any system table to fetch the data types for that version i'm using Oracle 11g.
in sql server we fetch the details by using
select * from sys.types
this will return what the data types supported by that version
Thanks!

There is a package called STANDARD in the SYS schema that defines many of the standard datatypes and functions.
e.g.
CREATE OR REPLACE package SYS.STANDARD AUTHID CURRENT_USER is -- careful on this line; SED edit occurs!
/********** Types and subtypes, do not reorder **********/
type BOOLEAN is (FALSE, TRUE);
type DATE is DATE_BASE;
type NUMBER is NUMBER_BASE;
subtype FLOAT is NUMBER; -- NUMBER(126)
subtype REAL is FLOAT; -- FLOAT(63)
subtype "DOUBLE PRECISION" is FLOAT;
subtype INTEGER is NUMBER(38,0);
subtype INT is INTEGER;
subtype SMALLINT is NUMBER(38,0);
subtype DECIMAL is NUMBER(38,0);
subtype NUMERIC is DECIMAL;
subtype DEC is DECIMAL;
subtype BINARY_INTEGER is INTEGER range '-2147483647'..2147483647;
subtype NATURAL is BINARY_INTEGER range 0..2147483647;
subtype NATURALN is NATURAL not null;
subtype POSITIVE is BINARY_INTEGER range 1..2147483647;
subtype POSITIVEN is POSITIVE not null;
subtype SIGNTYPE is BINARY_INTEGER range '-1'..1; -- for SIGN functions
type VARCHAR2 is NEW CHAR_BASE;
subtype VARCHAR is VARCHAR2;
subtype STRING is VARCHAR2;
subtype LONG is VARCHAR2(32760);
subtype RAW is VARCHAR2;
subtype "LONG RAW" is RAW(32760);
subtype ROWID is VARCHAR2(256);
-- Ansi fixed-length char
-- Define synonyms for CHAR and CHARN.
subtype CHAR is VARCHAR2;
subtype CHARACTER is CHAR;
type MLSLABEL is new CHAR_BASE;
-- Large object data types.
-- binary, character, binary file.
type BLOB is BLOB_BASE;
type CLOB is CLOB_BASE;
type BFILE is BFILE_BASE;
-- Verbose and NCHAR type names
subtype "CHARACTER VARYING" is VARCHAR;
subtype "CHAR VARYING" is VARCHAR;
subtype "NATIONAL CHARACTER" is CHAR CHARACTER SET NCHAR_CS;
subtype "NATIONAL CHAR" is CHAR CHARACTER SET NCHAR_CS;
subtype "NCHAR" is CHAR CHARACTER SET NCHAR_CS;
subtype "NATIONAL CHARACTER VARYING" is VARCHAR CHARACTER SET NCHAR_CS;
subtype "NATIONAL CHAR VARYING" is VARCHAR CHARACTER SET NCHAR_CS;
subtype "NCHAR VARYING" is VARCHAR CHARACTER SET NCHAR_CS;
subtype "NVARCHAR2" is VARCHAR2 CHARACTER SET NCHAR_CS;
subtype "CHARACTER LARGE OBJECT" is CLOB;
subtype "CHAR LARGE OBJECT" is CLOB;
subtype "NATIONAL CHARACTER LARGE OBJEC" is CLOB CHARACTER SET NCHAR_CS;
subtype "NCHAR LARGE OBJECT" is CLOB CHARACTER SET NCHAR_CS;
subtype "NCLOB" is CLOB CHARACTER SET NCHAR_CS;
subtype "BINARY LARGE OBJECT" is BLOB;
subtype pls_integer is binary_integer;
type TIME is new DATE_BASE;
type TIMESTAMP is new DATE_BASE;
type "TIME WITH TIME ZONE" is new DATE_BASE;
type "TIMESTAMP WITH TIME ZONE" is new DATE_BASE;
type "INTERVAL YEAR TO MONTH" is new DATE_BASE;
type "INTERVAL DAY TO SECOND" is new DATE_BASE;
SUBTYPE TIME_UNCONSTRAINED IS TIME(9);
SUBTYPE TIME_TZ_UNCONSTRAINED IS TIME(9) WITH TIME ZONE;
SUBTYPE TIMESTAMP_UNCONSTRAINED IS TIMESTAMP(9);
SUBTYPE TIMESTAMP_TZ_UNCONSTRAINED IS TIMESTAMP(9) WITH TIME ZONE;
SUBTYPE YMINTERVAL_UNCONSTRAINED IS INTERVAL YEAR(9) TO MONTH;
SUBTYPE DSINTERVAL_UNCONSTRAINED IS INTERVAL DAY(9) TO SECOND (9);
TYPE UROWID IS NEW CHAR_BASE;
type "TIMESTAMP WITH LOCAL TIME ZONE" is new DATE_BASE;
subtype timestamp_ltz_unconstrained is timestamp(9) with local time zone;
subtype BINARY_FLOAT is NUMBER;
subtype BINARY_DOUBLE is NUMBER;
-- The following data types are generics, used specially within package
-- STANDARD and some other Oracle packages. They are protected against
-- other use; sorry. True generic types are not yet part of the language.
type "<ADT_1>" as object (dummy char(1));
type "<RECORD_1>" is record (dummy char(1));
type "<TUPLE_1>" as object (dummy char(1));
type "<VARRAY_1>" is varray (1) of char(1);
type "<V2_TABLE_1>" is table of char(1) index by binary_integer;
type "<TABLE_1>" is table of char(1);
type "<COLLECTION_1>" is table of char(1);
type "<REF_CURSOR_1>" is ref cursor;
-- This will actually match against a Q_TABLE
type "<TYPED_TABLE>" is table of "<ADT_1>";
subtype "<ADT_WITH_OID>" is "<TYPED_TABLE>";
-- The following generic index table data types are used by the PL/SQL
-- compiler to materialize an array attribute at the runtime (for more
-- details about the array attributes, please see Bulk Binds document).
type " SYS$INT_V2TABLE" is table of pls_integer index by binary_integer;
-- The following record type and the corresponding generic index table
-- data types are used by the PL/SQL compiler to materialize a table
-- at the runtime in order to record the exceptions raised during the
-- execution of FORALL bulk bind statement (for more details, please
-- see bulk binds extensions document in 8.2).
type " SYS$BULK_ERROR_RECORD" is
 record (error_index pls_integer, error_code pls_integer);
type " SYS$REC_V2TABLE" is table of " SYS$BULK_ERROR_RECORD"
 index by binary_integer;
/* Adding a generic weak ref cursor type */
type sys_refcursor is ref cursor;
/* the following data type is a generic for all opaque types */
type "<OPAQUE_1>" as opaque FIXED(1) USING LIBRARY dummy_lib
 (static function dummy return number);
type "<ASSOC_ARRAY_1>" is table of char(1) index by varchar2(1);
/********** Add new types or subtypes here **********/
/********** Predefined constants **********/
BINARY_FLOAT_NAN constant BINARY_FLOAT;
BINARY_FLOAT_INFINITY constant BINARY_FLOAT;
BINARY_FLOAT_MAX_NORMAL constant BINARY_FLOAT;
BINARY_FLOAT_MIN_NORMAL constant BINARY_FLOAT;
BINARY_FLOAT_MAX_SUBNORMAL constant BINARY_FLOAT;
BINARY_FLOAT_MIN_SUBNORMAL constant BINARY_FLOAT;
BINARY_DOUBLE_NAN constant BINARY_DOUBLE;
BINARY_DOUBLE_INFINITY constant BINARY_DOUBLE;
BINARY_DOUBLE_MAX_NORMAL constant BINARY_DOUBLE;
BINARY_DOUBLE_MIN_NORMAL constant BINARY_DOUBLE;
BINARY_DOUBLE_MAX_SUBNORMAL constant BINARY_DOUBLE;
BINARY_DOUBLE_MIN_SUBNORMAL constant BINARY_DOUBLE;
/********** Add new constants here **********/
/********** Predefined exceptions **********/
CURSOR_ALREADY_OPEN exception;
 pragma EXCEPTION_INIT(CURSOR_ALREADY_OPEN, '-6511');
DUP_VAL_ON_INDEX exception;
 pragma EXCEPTION_INIT(DUP_VAL_ON_INDEX, '-0001');
..and so it goes on... take a look yourself
Edited by: BluShadow on 18-Dec-2012 09:32

Object data type

Similar Messages

Maybe you are looking for