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

Similar Messages

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

Can PI objects (such as data type) name been changed after the object was

activated?
Again I am new to PI and not aware lots of PI rules
I would like to express my appreciation first here

Yes, it can be. And that is almost same for all SAP objects. I would suggest that instead of posting threads first, go through the existing threads and documents on SCN and try to play with the your sandbox or dev system.
Regards,
Prateek Raj Srivastava

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.

Info Object: Change of Data Type (NUMC to CHAR)

We have a scenario wherein one of the Info objects is defined currently as NUMC. Due to the change in the Source system, the info object is now defined with data type as CHAR. The info object in consideration is the "Cost element".
As the current info object contains data, it will not be possible to change the data type from NUM to CHAR.
Is there any pre-defined way of doing this data type change without loss of data (in the info object as well as the info cube(s) where the info object is used)?
Regards
Bala

Hi Balakrishana,
Try this:
Insted of changing the definition of infoobject(NUMC to CHAR), why cant you change the data itself from CHAR to NUMC...?? If length is same.
You can write a simple routine in transfer rules and you can convert.
Hope it Helps
Srini

Numeric Data Types

What are the numeric data types in Oracle? I created the following table:
CREATE TABLE CONTRACT (
CONTRACT_ID INTEGER NOT NULL,
QUOTE_ID LONG,
BOOK_RATE NUMBER,
IBTSS_CONTRACT_NUM VARCHAR2(20)
But in the Object Browser, the data type of CONTRACT_ID becomes NUMBER which can accept numbers such as 123.25. This is not my intention. I thought LONG is not an acceptable data type but it actually works and the data type of QUOTE_ID shown in the Object Browser is correctly LONG. However, both LONG and INTEGER behave like NUMBER because I can insert values such as 123.56 into columns CONTRACT_ID and QUOTE_ID.
So my questions are
1. What are the supported numeric data types in Oracle?
2. Are we supposed to use INTEGER or LONG at all since they do not behave as expected? Are we supposed to always use NUMBER(n) instead?
Thanks.
Edited by: user10896541 on Apr 23, 2009 2:43 PM

LONG in Oracle is not an integer data type. LONG is a depricated data type that was designed to store text more than 4k in length. Oracle has been asking folks to stop using LONG and use CLOB (or BLOB for binary data) since 8.1.5.
INTEGER maps to NUMBER(38) which does not allow decimal values. You might be confused because Oracle truncates values if you insert them into a column that has less precision than the column allows
SQL> create table x (
2    col1 integer
3 );
Table created.
SQL> desc x;
Name                                      Null?    Type
COL1                                               NUMBER(38)
SQL> insert into x values( 1 );
1 row created.
SQL> insert into x values( 1.25 );
1 row created.
SQL> select * from x;
      COL1
         1
         1
SQL>Justin

External SOAP client Accessing Webservice using built in Java Data type

We have built a webservice and deployed it on WLS. We accessed this from a swing
client it works fine.The webservice methods uses non-built in JAVA data types
as parameters.These are Value Objects and the JAVA Serializer and Deserializer
classes are generated using Ant task itself.The client coding uses Value objects
given by the Client_jar (generated using <Clientgen> ant task) to pass to the
webservice. We dont want to go by this way.Is there anyway were in we can pass
parameters to the method which expects non-built in java datatypes?
Why i am asking this is, i want to know how an external client (.Net client )
will be able to exceute my webservice (i.e., passing the required Object which
the method is expecting)?

Hi Anish,
Well first off, your web service doesn't send or receive "objects". It only sends
and recieves XML, which is in turn converted to/from Java objects at invocation
time. Second, a .NET (or Perl, or Python, or C++) client will be able to call
your web service, because the wsdl.exe tool (for .NET) will generate "programming
language specific" objects from the <types><schema> elements, in the WSDL of your
web service :-) The wsdl.exe tool will create C# objects from the WSDL, that will
convert XML to/from C# when your web service is called. That's the beauty of XML
schema - it's a "universal typing system", so it's not tied to a particular programming
language. The only issue is whether or not the web services platform vendor's
XML Schema/WSDL processor, can successfully process the WSDL. Some vendors have
more complete implementations of the WSDL and XML Schema specs than others, so
expect varying success here. The one in WLS 7.0 is pretty good, so you shouldn't
have too many problems consuming WSDL generated by .NET tools (or any other tool
for that matter).
Regards,
Mike Wooten
"Anish" <[email protected]> wrote:
>
We have built a webservice and deployed it on WLS. We accessed this from
a swing
client it works fine.The webservice methods uses non-built in JAVA data
types
as parameters.These are Value Objects and the JAVA Serializer and Deserializer
classes are generated using Ant task itself.The client coding uses Value
objects
given by the Client_jar (generated using <Clientgen> ant task) to pass
to the
webservice. We dont want to go by this way.Is there anyway were in we
can pass
parameters to the method which expects non-built in java datatypes?
Why i am asking this is, i want to know how an external client (.Net
client )
will be able to exceute my webservice (i.e., passing the required Object
which
the method is expecting)?

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

Does new 1402 Activity object in Cloud for Customer have wrong data type namespaces?

I see that the individual "activity" objects (e.g., ActivityTask, AppointmentActivity, etc) are being deprecated as of 1405 and moving to a new Activity object with a TypeCode. That makes a lot of sense.
In reviewing this new Activity object, I've noticed that many of the node elements utilize Data Types in the http://sap.com/xi/Common/DataTypes namespace instead of the http://sap.com/xi/AP/Common/GDT. For example, the root node element UUID has a data type UUID in the http://sap.com/xi/Common/DataTypes namespace, unlike all the other objects in the Public Solution Model.
There are many more elements in this new Activity object that are mismatched like this to other common usage in other objects. Is this a new trend or a mistake?

Hello Gregory, Alessandro,
just for clarification:
SAP wanted to eliminate the superflous supplementary components from the data types used in the Business Objects.
Take the GDT Identifier as an example. It has the following supplementary components:
SCHEME_ID
SCHEME_VERSION_ID
SCHEME_AGENCY_ID
SCHEME_AGENCY_SCHEME_ID
SCHEME_AGENCY_SCHEME_AGENCY_ID
CONTENT
You very seldom need the SCHEME_ID or the SCHEME_AGENCY_ID (if the ID is a GTIN or DUNS number then you need them). I never came over a situation to use the SCHEME_AGENCY_SCHEME_AGENCY_ID.
So the data types from the "new" namespace omit those components. But SAP noticed the effort to adapt all the coding.
Therefore it was decided that only new objects will use the data types from the new namepace.
In the case of the ActivityTask, AppointmentActivity, etc. this wil requires - as Alessandro mentioned - some adoption effort.
HTH,
Horst

Issue with the Data Type 'Number' in Business Objects

Hi,
I have an Object in the Universe where the Data Type of the Object is a number. This Column pertaining to this Object has certain values in the database out of which there is a 17 Digit Value which is 00000000031101165.
Now, when trying to retreive the same value through Business Objects it is getting rounded off to 00000000031101200 automatically when trying to view in Webi and when trying to retreive the same in Designer/Deski, it displays as 0.000000003110116E+16.
So, I would like to know if there is any other alternative in trying to retreive the Original Value that would not round off. Also, do we have any Limitation for the Data Type Number in Business Objects? The Version we are on is XI3.1.
Note: There are no functions that are used on this Object at the Universe Level and would not like to use any functions here.

What is the underlying database?
It looks like the data is considered to have two decimals, but is rounded to zero decimals.
Only you don't see the number formatting.
Is this a BW query?
Is this a calculated keyfigure?
In the query you can specify the rounding you want and it is also possible to specify it on an infoobject level.
Check those settings...
Hope this helps,
Marianne
PS. Oh, and about the formatting, you can specify a default object format in the universe and override it on the final client (WebI, Crystal)

Retriving data through stored procedure returning Table of object type

I am trying to retrieve the data returned as a table(secret_tab_type) of object type(secret_type). Now we can get the secret_tab_type table through
rset = (ResultSet) cstmt.getObject(1); but how to map the SQL object type to Java object type ??
FUNCTION Fetchthat(
secretinfo out SECRET_TAB_TYPE,
message OUT varchar2
) return number;
These are the declaration of secret_type object and secret_tab_type(table returned by fetchthat procedure)
create or replace type secret_type as object
(secret_id number(3),
secret_question varchar2(100),
valid_flag char);
create or replace type secret_tab_type as table of secret_type;

Amit,
Your question has been previously asked (and answered) on this forum. I suggest searching this forum's archives for the terms STRUCT and ARRAY.
For your benefit, here are the results of my search:
http://tinyurl.com/auvl8
Good Luck,
Avi.

How to access complex data type objects in webdynpro

Hi
Need help on the detailed procedure to access the complex data type objects.
I am importing an external wsdl file, its request and response have complex data type objects , how do i access the same as the values are nested in them.
The structure of request and response at my end is as below:
request(I level)
--complextypeobject(II level)
requestheader(III level)
field1
field2
request
--response
messages
resp1
resp2
Any help would be highly appreciated.
Thanks and Regards,
Amar Bhagat Challa.

here you go
WS Structure
Request_MI_PortWellOB_MI_PortWellOB
|-- MT_PortWellOut
   |--agency ( attr)
   |--user (attr)
   |-- well ( node)
     |-- borehole
     |-- downhole
     |-- interval
     |-- surface
// code to set complex type
          wdContext.nodeRequest_MI_PortWellOB_MI_PortWellOB().bind(new Request_MI_PortWellOB_MI_PortWellOB());
          //        port well object
          Request_MI_PortWellOB_MI_PortWellOB oPWRequest = new Request_MI_PortWellOB_MI_PortWellOB();
          ComplexType_DT_PortWell oPWParameters = new ComplexType_DT_PortWell();
          oPWRequest.setMT_PortWellOut(oPWParameters);
          wdContext.nodeRequest_MI_PortWellOB_MI_PortWellOB().bind(oPWRequest);
          DT_PortWell oPWInputbean =
               this.wdContext.nodeRequest_MI_PortWellOB_MI_PortWellOB().nodeMT_PortWellOut().currentMT_PortWellOutElement().modelObject().getOriginalBean();
          //       oPWInputbean.setTEST("test");
          //          well object
          DT_CWR_Well oWParameters = new DT_CWR_Well();
          //          all object
          //        surface
          DT_CWR_Surface oSParameters = new DT_CWR_Surface();
          ComplexType_DT_CWR_Surface s = new ComplexType_DT_CWR_Surface();
          //          Borehole
          DT_CWR_BoreHole[] oBParameters = new DT_CWR_BoreHole[wdContext.nodeBoreholedetail().size()];
          //          Downhole
          DT_CWR_DownHole[] oDParameters = new DT_CWR_DownHole[wdContext.nodeDownholedetail().size()];
          //          Interval
          DT_CWR_Interval[] oIParameters = new DT_CWR_Interval[wdContext.nodeIntervaldetail().size()];
          //        add all into well object
          oWParameters.setSURFACE(oSParameters);
          oWParameters.setBOREHOLE(oBParameters);
          oWParameters.setDOWNHOLE(oDParameters);
          oWParameters.setINTERVAL(oIParameters);
          //       oPWParameters.setWELL(oWParameters );
          oPWInputbean.setWELL(oWParameters);
          oPWRequest.setMT_PortWellOut(oPWParameters);
          wdContext.nodeRequest_MI_PortWellOB_MI_PortWellOB().bind(oPWRequest);
          wdContext.currentMT_PortWellOutElement().setUSERID("user");
          wdContext.currentMT_PortWellOutElement().setAGENCY("agency");
Rahul

ADF View Object query to use Oracle LONG data type

Hi,
I'm using a view object that uses Oracle LONG data type.The following exception is thrown
*"java.sql.SQLException: Stream has already been closed"* and it is not fetching the correct data.
I have searched in many forums,they suggested to use LOB instead of LONG as LONG is deprecated. But in my case I can't avoid using LONG as some of my legacy applications using the same DB.
Please suggest me a way
Thanks in Advance
Felix

Thanks for your reply Arun,
I have solved this problem using the solution suggested by this blog [AskTom-Link|http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:839298816582]
In the above blog link,they have suggested to convert Long to Varchar by functions and asked to use this function in the column.
Thank you all guys who have seen this post.
Regards,
Felix

How to convert object type to only Date type ?

Hii everyone,
I have a table in database and their is column called as date and its data type is DateTime
In my UI part i have taken a Datepeacker and what ever user selected that date i am storing in my Date properties which has the same data type DateTime and at the Insertion time the date inserting successfully but at the time of updating data i am getting
error that the Date is not correct format because in date property it having the value 23:12:2014 00:00:00 which is crate problem at the time of update. So how to solve this ?
Note : I am using VS2008 and using Datagrid inside datgrid what ever changes user make tat one i required to update ,below are my update code which done through datatable i.e
first i have done datatable dt=new datatable();
                              dt = EmpBusinessLayer.SelectManager(dd.Eno)
then my update logic is :
    for (int i= 0; i < dt.Rows.Count; i++)
                ee.Ename = dt.Rows[i][0].ToString();
                ee.Job = dt.Rows[i][1].ToString();
                ee.Dept = dt.Rows[i][2].ToString();
                ee.Gender = dt.Rows[i][3].ToString();
                ee.Status =Convert.ToInt32(dt.Rows[i][4]);
                ee.Dates = Convert.ToDateTime(dt.Rows[i][6]);// Hear i am getting value like 23.8.2104 00:00:00
                ee.Eno = Convert.ToInt32(dt.Rows[i][9]);
                cmd = new SqlCommand("update Employee set sEname='"+ee.Ename+"', sEJob='"+ee.Job+"', sEDept='"+ee.Dept+"',
sGender='"+ee.Gender+"', bStatus="+ee.Status+", dDates="+ee.Dates+" where iEmpNo="+ee.Eno, con);       // Hear Getting Error tat incorrect syntax 00
                if (con.State != ConnectionState.Open)
                    con.Open();
                if (cmd.ExecuteNonQuery() > 0)
                    return 1;
S.K Nayak

You could use the yyyy-MM-dd format by calling the ToString method on the DateTime object:
cmd = new SqlCommand("update Employee set sEname='"+ee.Ename+"', sEJob='"+ee.Job+"', sEDept='"+ee.Dept+"', sGender='"+ee.Gender+"', bStatus="+ee.Status+", dDates=" + ee.Dates.ToString("yyyy-MM-dd") +" where iEmpNo="+ee.Eno, con);
Note that you should use parameters when create a command like this though:
https://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlparametercollection.addwithvalue(v=vs.110).aspx
But that's another story for another thread in another forum.
Please remember to close your threads by marking helpful posts as answer and then start a new thread if you have a new question.

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.
<b>Data Types:</b>
                 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
<b>Data objects:</b>
                  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 type of Souce Object Vs BW Object

Similar Messages

Maybe you are looking for