Data view and data structure

whats the difference between a data view and a data structure

Hi
<b>View:</b>
Data about an application object is often distributed on several tables.
By defining a view, you can define an application-dependent view that combines this data.
The structure of such a view is defined by specifying the tables and fields used in the view.
Fields that are not required can be hidden, thereby minimizing interfaces.
A view can be used in ABAP programs for data selection.
http://help.sap.com/saphelp_47x200/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
<b>Structures:</b>
A structure (structured type) comprises components (fields).
Types are defined for the components.
A component can refer to an elementary type (via a data element or by directly specifying
the data type and length in the structure definition), another structure or a table type.
A structure can therefore be nested to any depth.
Structures are used to define the data at the interface of module pools and screens
and to define the parameter types of function modules.
http://help.sap.com/saphelp_47x200/helpdata/en/ac/3547360f2ea61fe10000009b38f839/frameset.htm
Kindly assign points for useful answers!
Best regards,
Thangesh

Similar Messages

Data View and Data Source buttons Greyed out

I have Site Admin permissions on an On Prem SharePoint 2013 site.
In SharePoint Designer 2013 the Data View and Data Source buttons are greyed out.
Can anyone shed some light as to why this is occurring?

Hi grantzre,
Could you provide a screenshot about the location you want to insert the Data View web part and Data Source?
I think you may put the mouse cursor in the incorrect place to add the data view web part, please try putting the cursor before the tag </ZoneTemplate> and see if "Data View" button is enabled, then you can insert an empty
dataview web part and then insert the data source in tag <DataSources> by clicking ribbon button "Data Source" (also click the ribbon button "Parse HTML" of the page if needed).
Thanks
Daniel Yang
TechNet Community Support

Merging Basic data View and Classification View in Material Master

Hi,
There is a requirement to append Classification View under Basic Data View and then finally to delete Classification View.
As per my understanding, it is not possible. Please let me know if it is possible, if so, please let me know how is it possible.
A quick response is appreciated.
Thanks & Regards
Bhaskar Baddela

Hi,
Refer the thread: Problem creating Material Master sales view with LSMW which discuss the same issue. You may check and revert back.
Regards,
AKPT

How to view "date from" and "date to"

Hi,
I have loaded EMP data. In the mapping "date from" and "date to" are visible. But these fields are not seen when I display the EMP data.Can someone please tell me how to view these fields?
Thanks,
Williams

I got your question . Please find my understandings .
In the transformation Please check weather routine or formula is written which is stopping the dats
to be updated to the target .
I mean data is there in the source but if its not updating to target it seems some rules have been set up in the transformation . Please check .
Assign marks is the best way to appreciate help

Default view and date format for anonymous access in convergence calendar

Hi,
is there an option to configure default view and date format when user access to a calendar with anonymous access ?
Actually, date format is M/D and I want D/M.
And the default view is monthly, and I would like to set to 7 days view.
Thx for your help
Regars,
JC

jchatriot wrote:
is there an option to configure default view and date format when user access to a calendar with anonymous access ?No. I've raise a new Request For Enhancement:
RFE #6961895 - "Provide configuration option and URL parameter to set Anonymous Calendar view and date format"
Regards,
Shane.

BDoc: Related Data Type and Message Structure

Related Data Type and Message Structure are two attributes of a BDoc. Can anyone tell what they are used for?
Thanks in advance.
Regards,
Hui
BTW: Mush reward for good answers.

A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
For technical reasons, a data type is not sufficient to describe the instance of a message. In XML schema, data types are defined as abstract types that are not yet fixed to an element. You can only describe an instance of a message when you have specified a data type as an element type. Therefore, a message type defines the root element of a message.
A message type does not define the direction of the message exchange, in other words, whether it is a request or a response. In exceptional cases you can use the same message type for both the request and the response message.

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

Is there a way to manually custom-edit the "Date created" and "Date modified" attributes of files in Mac OS 10.6?

In "List View" in a Finder window, among the many column options are "Date created" and "Date modified." In "View Options" (command-J) for any folder, one can add these columns, along with the standard ones "Size," "Kind," "Label," etc.
A user can alter a file's name, and a file's "label" (i.e. its color). On the other hand, a user can NOT arbitrarily edit/alter a file's official "size" -- other than by physically altering the contents of the file itself, obviously.
But what about a file's "Date created" and "Date modified"? Can either of those be manually edited/changed, just as a file's name can be changed -- or is a file's creation-date an immutable attribute beyond the editorial reach of the user, just as a file's "size" is?
And yes, a person can "alter" a file's "Date modified" by simply modifying the file, which would change its "Date modified" to be the moment it was last altered (i.e. right now). But (and here's the key question) can a user somehow get inside a file's defining attributes and arbitrarily change a file's modification date to be at any desired point in the past that's AFTER its creation date and BEFORE the present moment? Or will so doing cause the operating system to blow a gasket?
If it is possible to arbitrarily manually alter a file's creation date or modification date, how would it be done (in 10.6)? And if it is NOT possible, then why not?

sanjempet --
Whew, that's a relief!
But as for your workaround solution: All it will achieve is altering the created and modified dates to RIGHT NOW. What I'm looking to do is to alter the modification/creation dates to some point in the past.
I'm not doing this for any nefarious reason. I just like to organize my work files chronologically according to when each project was initiated, but sometimes I forget to gather the disparate documents all into one folder right at the beginning, and as a result, sometimes after I finish a job, I will create a new folder to permanently house all the files in an old project, and when that folder is places in a bigger "completed projects" folder and then is organized by "Date created" or "Date modified" in list view, it is out-of-order chronologically because the creation and modification dates of that particular project folder reflect when the folder was created (i.e. today), and not when the files inside the folder were created (i.e. weeks or months ago).
The simplest solution would simply to be able to back-date the folder's creation or modification date to match the date that the project actually started!

Data Carriers and Data carrier type

Hi Sap Gurus,
Pls let me know is there any necesssity of defining any new Data Carrier types other than PC,
if so at what circumstances and requirements,
also pls throw some light about data Carriers, when is the new data carriers required to be created
at what circumstances and requirements.
is that to access a document from different server or Different system, if it is so why is this required as the documents are always stored in a central content server and Once checked in, any one can access the document from Server,
2) can we make use of Application softwares Installed in one System and make it run in another system, example,
if there are say 4 system totally, among this S1 system1 has Autocad Installed in it ,
rest of the 3 system have not installed Autocad, Can the system 2,3 and 4 edit the auto cad drawings in there system, does at this situations where Datacarries and Data carries types come in to picture,
Please throw some light on this
Thanks and regards
Sathish

Dear Christoph Hopf,
Thanks a lot for your Quick Response
as you have Explained,i assume it is mainly used to store a local copy or extra copy of the Original application files in the system which we use to View them, or if we feel to store the copy in any other system also.
Example Say there are 3 systems S1, S2 and S3
if we are viewing an original file in System S1 and want the same Copy to be stored in System S2 or S3.....
then this data carrier configuration is required if iam right?
But Sir apart from this funtionality can i also know the SAP definition purpose, as it defines data carrier type as below
The system requires the data carrier type in order to exchange data with other data carriers.
This is the case, for example, if the user:
wants to process original application files stored on another computer
wants to use an application installed on another computer
if i can interpret this in right way
it tells us that, by use of data carrier and Data carrier types
we can access a original file stored in Different systems,
if it is so why is this required as the documents are always stored in a central content server and Once checked in, any one can access the document from Server,
2) can we make use of Application softwares Installed in one System and make it run in another system, example,
if there are say 3 system totally, among this S1 system1 has Autocad Installed in it ,
rest of the 2 system have not installed Autocad, Can the system 2, and 3 edit the auto cad drawings in there system, does at this situations where Datacarries and Data carries types come in to picture,
if so how is this made possible?
pls explain with example or Screen shots in Wiki if possible
can u tell me what is the difference between Datacarrier and Datacarrier types with any examples as well
Thanks and regards
Sathish
Edited by: sathish kumar on May 22, 2008 2:17 AM

Calender using Date From and Date To

Hi,
I'm trying to build a calender based on a table that has a user_name, date_from, date_to and comments.
Basically I want the calender to show all the dates betwwen the date from and date to. Is there any way of getting the calender to use those dates and all the days in between or will I have a to build a view that returns one row for each day between the start and end
Whats the best way of doing this and does any one have an example
Thanks in advance

Andy,
See my blog post here:
http://deneskubicek.blogspot.com/2007/05/create-pseudo-tables.html
and the corresponding example:
http://htmldb.oracle.com/pls/otn/f?p=31517:83
Denes Kubicek
http://deneskubicek.blogspot.com/
http://htmldb.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

Data type and Data object

Hi Friends,
        What is the difference between Data type and Data object?
Best Regards,
VRV Singh

hi
good
Each ABAP program define its own data types using the statement.
TYPES dtype TYPE type ...
and declare its own variables or instance attributes of classes using the statement
DATA var {TYPE type} ...
Within the program or a class, you can also define local data types and variables within procedures. Local variables in procedures obscure identically-named variables in the main program or class.
When creating data types and data objects, there are a number of naming convention that also apply for other local program definitions, such as procedures. These are described in detail in the keyword documentation.
The Additions TYPE and LIKE
The additions TYPE type and LIKE dobj are used in various ABAP statements. The additions can have various meanings, depending on the syntax and context.
·        Definition of local types in a program
·        Declaration of data objects
·        Dynamic creation of data objects
·        Specification of the type of formal parameters in subroutines
·        Specification of the type of formal parameters in methods
·        Specification of the type of field symbols
Constructing New Data Types
The TYPE addition allows you to construct new data types in the TYPES, DATA; CONSTANTS; and STATICSstatements. In the TYPES statement, these are local data types in the program. In the other statements, they are attributes of new data objects, meaning that the newly defined data types are not free-standing. Rather, they are linked to database objects.This means that you can refer to them using the LIKEaddition, but not using TYPE.
To construct new data types, the addition TYPE can be used with the following type constructors:
·        Construction of reference types
REF TO type|dobj
·        Construction of structured data types
BEGIN OF struc_type.
END OF struc_type.
·        Construction of table types
tabkind OF linetype
These data types only exist during the runtime of the ABAP program.
Referring to Known Data Types or Data Objects
Using the additions TYPE or LIKE in the TYPESstatement, local data types in a program can be referred to known data types or data objects. This is mainly the case with user-defined elementary data types. If you declare variables using the additions TYPE type or LIKE dobj with statement DATA, the data type of var is already fully defined before the declaration is made.
The known types or data that are referred to must be visible at the point where the data type or variable is declared.
A known data type can be any of the following:
·        A predefined ABAP type to which you refer using the TYPE addition
·        An existing local data type in the program to which you refer using the TYPE addition
·        The data type of a local data object in the program to which you refer using the LIKE addition
·        A data type in the ABAP Dictionary to which you refer using the TYPE addition. To ensure compatibility with earlier releases, it is still possible to use the LIKE addition to refer to database tables and flat structures in the ABAP Dictionary. However, you should use the TYPE addition in new programs.
The LIKE addition takes its technical attributes from a visible data object. As a rule, you can use LIKE to refer to any object that has been declared using DATA or a similar statement, and is visible in the current context. The data object only has to have been declared. It is irrelevant whether the data object already exists in memory when you make the LIKE reference.
·        In principle, the local data objects in the same program are visible. As with local data types, there is a difference between local data objects in procedures and global data objects. Data objects defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program.
·        You can also refer to the data objects of other visible ABAP programs. These might be, for example, the visible attributes of global classes in class pools. If a global class cl_lobal has a public instance attribute or static attribute attr, you can refer to it as follows in any ABAP program:
DATA dref TYPE REF TO cl_global.
DATA: f1 LIKE cl_global=>attr,
       f2 LIKE dref->attr.
You can access the technical properties of an instance attribute using the class name and a reference variable without first having to create an object. The properties of the attributes of a class are not instance-specific and belong to the static properties of the class.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2ff3358411d1829f0000e829fbfe/content.htm
thanks
mrutyun^

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

SQL DM - Data Transformation and Data Movement option ?

SQL DM - Data Transformation and Data Movement option ?
I am using SQL DM 3.0.0.665. I need your thoughts on following.
We find that Erwin introduced Data Transformation and Data Movement functionality to support ETL need. We were able to generate ETL spec using this feature.
Does SQL DM have any plan to introduce such features?
How do we use the current SQL DM to build ETL spec ?
Thanks in helping us out.

Hello,
I am currently experimenting with SQL Data Modeler to produce high level solution designs and ETL specifications.
Have not completed what I am doing but so far have come up with the following:
Current assumption I am working on:
All objects specified within the SQL Data Modeler will export to the Reporting Schema tables set up in an Oracle database. Once the data is within these tables then it will be a simple task to develop a SQL report to extract the data in any format required.
1) There is nothing in the physical (Relational) Model section that supports this
- though I have yet to fully use the Dimensional Modelling functionality which may have the mapping functionality required to specify an ETL
2) We need diagrams of the processes as well as the ETL mapping
- Process modelling is available in the Logical
- Reverse Engineer all Physical objects to become Logical object i.e. one Table to one Entity
- For each Entity set up an Information Structure
(Currently this can only be done in a convoluted method via creating a diagram, creating a Flow and editing the Flow then drilling down)
MESSAGE to SQL Data Modeler Support: Can things be set up so that Information Structures can be set up directly from the Browser, current method is a bit nonsensical
- You are now set up to use the Logical Process Modeling functionality to capture the ETL requirements
- Advise that you reference the training to understand what primitive, composite and transformation processes objects are
- Also, take the time to understand what an external agent object is
- Will assume you know what a Data Store is
Here is the standard I am heading towards that seems feasible, will need to run a proof of concept within the larger team to ensure it works though:
- A Logical is kept that is a one for one with the Physical
(The only reason for this is that there is no process modeling functionality for the Physical objects
MESSAGE to SQL Data Modeler Support: Can you duplicate the Process Modeling for the Logical to be available for the Physical objects too, would be a great help to specify ETL jobs.
- An External Agent is used to represent an external source e.g. Billing application
- A primitive process is used to represent the high Level design
- A composite process is used to specify processes which can be further broken down to ETL jobs
- A transformation process is used to represent an ETL job
Within a Transformation process you can specify the mapping from multiple sources to a target table
There are some negatives to this approach:
- You lose the physical schemas the tables are part of, though a naming convention will get round this
- You need to maintain a logical that is one for one with the physical, this is not a big overhead
However, as I have stated in my message to the SQL Data Modeler support team, would all be resolved if the Process Modeling functionality were also made available within the Physical objects environment.
Please note that we have not as yet adopted the above approach and are still assessing is SQL Data Modeler will meet this requirement to our satisfaction. The critical bit will be if the data exports to the Reporting Schema, if it does then we have plenty of SQL resource that can produce the reports required procided the data can be captured.
Hope that all helps.
Also, hope I have not missed the point of your email.
Kind regards,
Yusef

Tutorials for MVC, Data Controls, and Data Bindings

I am looking for some good tutorials on:
Model View Controller concept
Creating Data Controls from Java Beans
Creating and Using Data Bindings
We are using JDeveloper, but do not want to use ADF as we want more control than ADF offers.
Thanx
Pam

Just curious, what control do you need that ADF doesn't offer you?
If you use ADF, you don't have to use it for every page. You can bind some components on your page using adf directly to your adf data controls, and you can bind other components to your backing beans, and have full control. No reason to throw out adf if there are just a few cases where you need more control.
Btw, do you have a link to a page describing these non adf data controls and data bindings?

Difference between data dictionary and data base

Hi,
Please give me clear view on data dictionary and data base.
Thanks
margani

Hi Margini,
Please check the forms u can find the lot of answers
Here is a link
http://www.sapdb.info/abap-data-dictionary/
What is a data dictionary?
Data Dictionary is a central source of data in a data management system. Its main function is to support the creation and management of data definitions. It has details about
·            what data is contained?
·            What are the attributes of the data?
·            What is the relationship existing between the various data elements?
Best regards,
raam

Data view and data structure

Similar Messages

Maybe you are looking for