Query on Projection View

Sometimes we create a Projection View to specify less no of fields of a table. the same can be done by creating a temporary structure in the program. then what is the need to go for the Projection view?

Similar Messages

Can I write a SELECT query on maintenance view?

Hi,
Can we write a select query on maint. view? If not what are the views on which we can write the select queries?

hi,
you can write select query for maintenance view, database view and projection view but not helpview as it is only intended for f4 help.
reward if helpful
prasanth

Select query in materialized view with two dblinks

Hi All,
We have oracle 10g On windows.
We are trying to create materialized view. Scenario is we have base table on other database and we are creating mview on different database.
Basa database have two schema's and i am selecting records from that two schema's using two private db links.
But when i am tryin gto create mview its not getting created. After 15 hrs. its still showing creation command and not finished.
Query is :-
Is it good practice to have two db links in select query of materialized view.

Billy Verreynne wrote:
Chanchal Wankhade wrote:
Is it good practice to have two db links in select query of materialized view.Same db link being used twice, or two different db links?
If the former, you ideally want the local Oracle db to send the join to the remote database, and for the remote database to drive the join between those 2 tables. There is a hint (<i>driving_site</i>) that can be used - or the join query can be defined on the remote database as a view, and the local materialised view can then use that remote view.
If you have 2 different db links and joining across these - usually a bad idea to perform distributed database joins. There are lots of limitations as to how the tables can be joined. Worse case, full table scans of both remote tables, pulling all the rows from the 2 remote database tables to the local database, and joining these on the local database.
I have seen some severe performance issues in the past as a result of distributed joins. I'll rather use 2 materialised views for pulling both distributed tables's data locally, and then do the join on local data (using indexes, partition pruning, etc)Hi Billy,
My scenario is i have two database database A and database B. Database A is having two schema's SCOTT AND HR. SCOTT schema have select privileges on HR schema.
DB LINK is between Database B to Database A. name is db.link.B.A.oracle.com.
What if i priovide while creating materialized view, the schema name before the table name in database B for this particuler table so it will pick up the table from that schema using same DB LINK(db.link.B.A.oracle.com.) that i am using to fetch records from SCOTT schema.
Above schnario is like two base schema's and one db link using two schema.

Query SharePoint List View

As per http://msdn.microsoft.com/en-us/library/ms434064.aspx if we use
list.GetItems(query, view.ID.ToString("B").ToUpper());
properties of the view that is specified by the viewName parameter override the properties that are specified in the query object that is passed through the query parameter. For example, if the query
object includes a tag that specifies only items containing a particular column value, while the view specifies to return all items, this method retrieves all of the items
So is there any way to query a sharepoint list view (not All Items) using CAML query?
I this retrieving view in a data table and query it later, which is an option but might give a performance degradation.
Regards, Aj (http://www.aj-sharepoint.blogspot.com/) MCTS

Hello,
Did you try with SPView.Query method? If not then this can be query to specific view.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spview.query.aspx
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

Snowflake dimension: named query vs. database view

A test question features a Product table with a Product Size code; Product Size description is taken from ProductSize table. As far as I can tell, the question asks me to choose between (a) setting up a database view joining Product and ProductSize, and
(b) doing the join in a data-source-view named query. I don't see a clear winner. (My thinking is as follows. Yes, he view would speed up the processing, even if not materialized. On the other hand, with a small dataset, the performance gain would be
minor in absolute terms. Do I want to have an extra database object in the picture?) Yet the question's author does. Can anyone advise please?

Hi Demyan,
According to your description, you want to know which is better, using named query in datasource view or using database view, right?
Based on my research, there is no performance differences between using named query in datasource view and using database view because they both result in SQL query being sent to the source system. Here is a blog which discuss this issue.
Consistency: If you already have logic in database views, I would continue to use them. As long as you know that you go to one spot to view/change the logic. Putting the logic in 2 different spots could lead to confusion.
Security Permissions: often you may not have permission to alter the source databases, in this case you have no choice but to setup named queries in the dsv.
Reference
http://geekswithblogs.net/darrengosbell/archive/2006/09/05/90278.aspx
http://bennyaustin.wordpress.com/2013/07/16/dbview/
Regards,
Charlie Liao
TechNet Community Support

Use of project view to group project records in multi-project report

I have a summary level multi-project report to report summary level information for active projects. We are using project view to organize our projects between departments and divisions (hierarchical structure) - represented by folders in project view. Projects are occasionally moved between project folders. If anyone has experience with report development using folder structure? My intent is to create grouping band based on folder structure and list projects under appropriate folder/band.
Any assistance is greatly appreciated.
I am using CM14.1 with OBIP 10.1.1.7
Thanks,
Prath

If you are creating a standard multi-project report (no retrieval criteria; project_state=0) and you run this report from within PCM, PCM automatically appends to your syntax the filtering criteria for the "folder" the user has highlighted in the project tree. In this case you would have one report that would retrieve multiple sets of data actively depending upon the project tree position. I have seen sometimes this causing issues with certain base syntax, but in general this should work.
Sounds, though, like you're building your report to call to the raw project_view tables, and Rick pointed out you need to use both of these tables then most likely.

The little clips i'm editing in iMovie 10 in the project view are hallway grayed out. Why is that?

the little clips i'm editing in iMovie 10 in the project view are hallway grayed out. Why is that?

Judy444 wrote:
.. Is there a How To beginners tutorial for this program?
here: http://www.apple.com/findouthow/movies/
and the built-in Help of iMovie (as any other Apple app) explains a lot..

Sorting and Grouping in Projects View

In Projects view, when either of two of the three grouping options is selected, there are two sorts in effect: the groups themselves are sorted, and the contents of each group are sorted. These sorts are handled differently, depending on the grouping selected and the sort order selected.
(It appears that there is a bit of the old Apple voodoo in here. The results are arbitrary , but they seem to have been carefully chosen to meet most users expectations. That is to say -- and this is an Apple programming trait -- the arbitrariness is faithful to the expected users' needs, not to logic.)
There are four sorts available, and three groupings
Sorts:
. Name
. Date -- Oldest First
. Date -- Newest First
. Library
Groupings:
. Ungrouped
. Group by year
. Group by folder
So that's twelve possible ways to display Projects in Projects view.
Let's look at a few of them. I'm going to refer to the groups as "Year groups" or "Folder groups" and to the contents of the groups as "Projects". So there is sorting of the groups, and sorting of the contents of the groups (same as "within the group"). These I'll refer to as "Groups sorting" and "Projects sorting".
Sort: Date -- Newest First
Grouping: Group by Year
Result: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
Sort: Date -- Oldest First
Grouping: Group by Year
Results are as expected; a reversal of the "Newest First" sort, but with the same groups: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
Sort: Name
Grouping: Group by Year
Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are sorted alphabetically, descending.
Sort: Library
Grouping: Group by year
Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector. (Note that this last is literal: a Project named "Aardvark Close-ups" if it's in a Folder named "Zoography" will be listed after all the projects in "Yellow Paintings" and all the Projects in "X-rays, thoracic" if those Projects are in alphabetical order by Folder name in the Library. You can see all the Projects in your Library listed on the Library tab of the Inspector by "{Option}+clicking" the disclosure triangle next to "PROJECTS & ALBUMS" twice.)
Sort: Date - Newest First
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, newest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder.
Sort: Date - Oldest First
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, oldest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
Sort: Name
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted alphabetically by name, descending. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
Sort: Library
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector (see note above). Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are listed in the order they appear in the Library).
Ernie [asked:|http://discussions.apple.com/thread.jspa?threadID=2816124&tstart=0]
+I see those icons but note that those projects in folders will be in different sections arranged alpha, and then date within. Am I correct on that?+
The answer is, it depends.
If "Group by year" is selected, the Groups-sorting will always be by date, regardless of the sort order specified. The Groups-sorting order will follow whatever is specified for the Projects sort order (or default to "oldest first").
If "Group by folder" is selected, the Groups-sorting will always be alphabetical, descending, regardless of the sort order specified. (So if you use Projects view, take care in naming your Folders. Use prefixes if needed to force a desired alpha sort.)
If "Ungrouped" is selected, there are no Groups and perforce no Groups-sorting.
That's all I have to say on this topic (today).
Message was edited by: Kirby Krieger

In Projects view, when either of two of the three grouping options is selected, there are two sorts in effect: the groups themselves are sorted, and the contents of each group are sorted. These sorts are handled differently, depending on the grouping selected and the sort order selected.
(It appears that there is a bit of the old Apple voodoo in here. The results are arbitrary , but they seem to have been carefully chosen to meet most users expectations. That is to say -- and this is an Apple programming trait -- the arbitrariness is faithful to the expected users' needs, not to logic.)
There are four sorts available, and three groupings
Sorts:
. Name
. Date -- Oldest First
. Date -- Newest First
. Library
Groupings:
. Ungrouped
. Group by year
. Group by folder
So that's twelve possible ways to display Projects in Projects view.
Let's look at a few of them. I'm going to refer to the groups as "Year groups" or "Folder groups" and to the contents of the groups as "Projects". So there is sorting of the groups, and sorting of the contents of the groups (same as "within the group"). These I'll refer to as "Groups sorting" and "Projects sorting".
Sort: Date -- Newest First
Grouping: Group by Year
Result: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
Sort: Date -- Oldest First
Grouping: Group by Year
Results are as expected; a reversal of the "Newest First" sort, but with the same groups: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
Sort: Name
Grouping: Group by Year
Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are sorted alphabetically, descending.
Sort: Library
Grouping: Group by year
Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector. (Note that this last is literal: a Project named "Aardvark Close-ups" if it's in a Folder named "Zoography" will be listed after all the projects in "Yellow Paintings" and all the Projects in "X-rays, thoracic" if those Projects are in alphabetical order by Folder name in the Library. You can see all the Projects in your Library listed on the Library tab of the Inspector by "{Option}+clicking" the disclosure triangle next to "PROJECTS & ALBUMS" twice.)
Sort: Date - Newest First
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, newest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder.
Sort: Date - Oldest First
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, oldest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
Sort: Name
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted alphabetically by name, descending. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
Sort: Library
Grouping: Group by folder
Result: Folder groups are sorted alphabetically by name, descending. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector (see note above). Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are listed in the order they appear in the Library).
Ernie [asked:|http://discussions.apple.com/thread.jspa?threadID=2816124&tstart=0]
+I see those icons but note that those projects in folders will be in different sections arranged alpha, and then date within. Am I correct on that?+
The answer is, it depends.
If "Group by year" is selected, the Groups-sorting will always be by date, regardless of the sort order specified. The Groups-sorting order will follow whatever is specified for the Projects sort order (or default to "oldest first").
If "Group by folder" is selected, the Groups-sorting will always be alphabetical, descending, regardless of the sort order specified. (So if you use Projects view, take care in naming your Folders. Use prefixes if needed to force a desired alpha sort.)
If "Ungrouped" is selected, there are no Groups and perforce no Groups-sorting.
That's all I have to say on this topic (today).
Message was edited by: Kirby Krieger

Showing dates in Projects view like iPhoto does in Events view

Hello, I recently imported my iPhoto library into Aperture and am overall pleased with all that Aperture has to offer. However, there are a couple things that are really frustrating to me that I miss in iPhoto.
For instance, in iPhoto when I scroll through Events by dragging the little scrubber bar on the far left of the screen, an overlay appears in the middle of the screen that tells me what the date is of the Event that is in the middle of the screen. When I do the same thing in the Projects view in Aperture, I get no such helpful overlay. Is there a way to turn this feature on? I know it sounds like a small thing, but it is very useful when browsing for particular photos.
Thanks for your help!

I'm not familiar with iPhoto, but in Aperture you have quite a few options to sort and view your projects by date, folders, etc.
Here's a screenshot in which I marked the sorting options field: http://skitch.com/pbmbuss/rk4td/aperture-3-projects-sorting
Hope it helps!
Pedro.

Question about Dates in Project View

I usually have no problems when it comes to date metadata, changing dates if need be, batch changes, etc... But this is something that is confusing me and I haven't been able to solve it.
My wife found one of her old PAS digital cameras, and it had images on the card. I decided to import them for her into Aperture, but it was immediately apparent to me that the date and times were off. The time zone was fine, so I imported the images using a card reader, adding the appropriate metadata of my choosing. After importing the images, I proceeded to change the date and time to the correct dates and times. This worked fine as well, only in Project view, the project doesn't fall into the right place. I have my projects organized into folders, and have them set to Date - Oldest First. The photos from this import show as today's date when I scroll over the image preview box and the project is organized as the last project, which is consistent with that date. The metadata shows that the file date is the date that I set it to be (which in this case would make it the oldest project in the folder). Nothing I do changes anything.
I then decided that maybe it had something to do with importing the images via a card reader instead of off of the Camera directly, so I decided to import straight from the camera. This time, the project is organized as the oldest project, but when I scroll over the Project preview box, the date that shows up is the original incorrect date, not the new date that I changed the photos to. The new date would still make the images the oldest project.
I really just want the dates to match up, and I can't imagine why the Projects preview is showing me one date when the metadata (and my own knowledge of the situation) is telling me that it should be showing a different date. When I made the adjustments to the date and time, I also applied the changes to the Master file.
Does anyone know what is going on here, why Aperture has a problem with something like this and if there is anyway to fix the problem?
Much obliged,
Mac

Update:
I just solved the issue, but I don't know why it should work like this, nor why this should happen.
Basically, the first time that I imported the images, I imported them separately as groups of photos so that I could import them each into individual new projects. I noticed that the first project I created had the right information both in the metadata and in the project pane. This being the case, I decided to import everything again, only this time I imported everything at the same time into one project and called the project, "Test" (this is arbitrary and has nothing to do with the solution).
Next I batch changed the date and time of all of the images in this "Test" project. Once that was done, I separated the images out into their own projects. This time everything showed up and was organized correctly.
Again, I don't know why it had to be done this way, but apparently once I imported the first time, that was the only time that the metadata was accurately recorded. The subsequent imports off of the same card were not recorded properly. Again, I have no idea why, nor what to do about that, but my data is correct now and this seems to have solved the issue.
If anyone has anything to say about the topic, please chime in.
Thanks,
Mac

Wrong project opens when double clicking on a project in project view

This is really weird. I have a personal library that was created by importing my entire iPhoto library and a Pro library that was created by just importing groups of images and folders from one of my drives. Both libraries are 100% managed. When Aperture opens, and my Personal library was the library that was open when I last closed Aperture, this behavior occurs. I go to double click on a project in project view and some other project opens. It's not random either. If I click on the project "Kennesaw Hike" for example, then "Jeremy's Birthday" will open every time.
Now the strange thing is when I go to File, Switch To Library, and choose my Pro Library and then switch right back to my Personal library, the projects in the project view open correctly. Something else that might be related. A few times in the last week when the Personal library was the open library when Aperture was closed last, and then I open Aperture later, it would prompt for my serial number again.
Another tidbit that might be of interest. I recently replaced the drive both libraries were on and copied them both to a new larger drive.
Any ideas?
Thanks

I'd like to add a "me too" to this.

Select a Project in the Library Inspector from Projects View -- now broken?

The new interface is missing something I used to use all the time. In Olde Aperture (3.3.1), double-clicking any selected Project(s) in Projects View showed the contents of that (those) Project(s) in the Browser and selected them in the Library tab of the Inspector. This behavior has been changed (3.3.2): now the contents are shown in the Browser, but as a subset of the superset of Projects, which remains selected in the Library tab of the Inspector.
This represents a bit of a dam in my workflow. I manage a few Libraries with thousands of nested Projects. I often need to select the Project in the Library tab of the Inspector. Double-clicking a Project (or Projects) was a great way to select those Projects in the Library tab of the Inspector. Is there a quick way to do this in 3.3.2? The old way kept with Aperture's visual orientation. Currently, I am having to memorize the names of Projects in order to find them. This is, afaict, a step backwards.
Is there any justification/benefit to having "Projects" remain selected after one double-clicks a Project or Projects in Projects View?
Notes:
- when two or more Projects are selected in Projects View and then double-clicked, one can right-click an Image and select "Show in Project" from the pop-up context menu. When only one Project is selected originally, that menu choice is not shown.
- you cannot open the Project Info pane after double-clicking a Project in Projects View. You must either return to Projects View and click the "i" icon on the Project tile, or otherwise right-click the Project name in the Library tab of the Inspector and select "Show Project info" from the context menu pop-up.
Thanks .
Added:
Léonie and I discussed this once already, but other than acknowledging the problem, didn't progress.
Message was edited by: Kirby Krieger

Kirby, I see you have explored this annoying change more since your post last month, when AP 3.3 came out.
Is there any justification/benefit to having "Projects" remain selected after one double-clicks a Project or Projects in Projects View?
None that I can think of.
Is there a quick way to do this in 3.3.2? The old way kept with Aperture's visual orientation.
Only the "Goto Project" button in the "Project Info" panel, but I would not call that quick.
Notes:
- when two or more Projects are selected in Projects View and then double-clicked, one can right-click an Image and select "Show in Project" from the pop-up context menu. When only one Project is selected originally, that menu choice is not shown.
But that is really a nice work-around - just take care to at least select two projects at the same time.
I missed that feature, because I was annoyed that it does not work when selecting one project.
- you cannot open the Project Info pane after double-clicking a Project in Projects View. You must either return to Projects View and click the "i" icon on the Project tile, or otherwise right-click the Project name in the Library tab of the Inspector and select "Show Project info" from the context menu pop-up.
But at least you can still double click the project and go to the project with the "Project Info" HUD open, and it will stay open. But it is cumbersome to have to remember to open the HUD before going to the project. Otherwise not even the name of the project will be displayed. I have added the name of the project to each metadata view, so I can see it in the Inspector HUD as well.
I rarely use the projects view and rely heavily on the folder structure and the search field to quickly find my projects.
Cheers
Léonie

Changing the query on a view object

I have a view object right now, based on an entity. It is the default view object, so that means the query in the view object is straight forward, it grabs all of the attributes from the table. And there is no WHERE clause.
In reality I only want to show a finite set of rows from my table. Every time a record is changed/edited in this entity and committed, a new row in the database is created with the same information (I'm using CreateWithParams) except for a few columns.
I actually don't really have update on this table, just creation of new rows. But to the user, I want it to 'look' like they are editing something in the table.
Example:
12, 11:32,Thompson, 60 (the user edits this information in an adf table, and a new row is created in the db)
12, 11:55, Thompson, 75
I have a timestamp (see above) field in the database that is used as part of my primary key, so that I know which record is the latest.
When the VO query is run, I want the user to only see the latest row from the db.
12, 11:55, Thompson, 75
So...
I went to my VO, and I changed the WHERE query to add this:
where t1.TimeStamp = (Select MAX(t2.TimeStamp) FROM rcl.x t2 where t1.uid = t2.uid);
Now, this isn't a mysql/sql question. There's actually a better query that I'd rather run, but the VO editor doesn't allow me to change the query itself....
When I save the new WHERE to my VO, run my page again, I get the expected result (showing me only the latest records).
However, when I try and sort on the table in which my data is displayed, I am now getting ORDER BY errors.
I don't want my VO to be read-only sql based. I want to be able to update my table, so I have my VO running off of the entity.
Why doesn't the VO allow me to change the query itself? (Like do a subquery, instead of having my where clause do the work)
Why are order by errors being thrown when I sort on my adf table after changing the where clause in my view?
Hopefully I wasn't too convoluted in the explanation of my problem..
Thanks in advance,
Joel

HI Joe,
Regarding your problem you can do one of the following tasks:
1- easily to tuning on your view object, I mean in the tuning page of the view you can set that only return 1 record or 2-3 record fetch not all the record.
in the order by you will order by the timestamp field and descending.
2- you can order by the timestamp descending and in the where clause only set the rownum<2 (will return the last record) you can also set rownum<5 and get the 4 last record etc.
3-editing the view query in the expert mode is not advised at all because of many consequences that you will face.
4- maybe it is not bat that you add a readonly view for the table you mentioned and every time you unpdate the entity just re-execute the read-only view.( this method maybe is good maybe is not it depends on your business logic)
Regards.
Edited by: Amir Khanof on Sep 3, 2010 11:11 PM

Running a query in a View Designer results in an error, but running the same query in a Query window works

Hi everyone,
Just as my title says, I have a query which I've written in a query window and it works perfectly.
But when I try to add the query code into the view designer, it throws a Syntax error.
Error in ON clause near '('.Unable to parse query text.
Also, when running the query from the view designer (pressing red exclamation mark) I get a different error.
SQL Execution Error.Executed SQL statement: SELECT Sku, ParentSku, UPC, ...Error Source: .Net SqlClient Data ProviderError Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Has anyone else experienced this and is there any workaround?
I have tried to create the view with T-SQL (CREATE VIEW etc.), but when opening it in the view designer I get the error from the 1st image.
Thank you,
Radu

Hi Radu,
Yes, I have faced similar issue. I had a View and it was working totally fine but when once I opened it in via right click - View Design, it was giving parse error.
Cause is that Query designer parse and executes the query without error but the way View designer works, it can't parse it.
Later I ignored View desinger and just used T-SQL like CREATE/ALTER view.
Workaround is to do right click on View - Script View as - CREATE To/ ATER To.
Regarding Timeout error, again the issue with View designer which couldn't execute query in there and ended up with timeout error.
If your SELECT query and SELECT * FROM YourView works fine in Query designer, you are good to go.
Similar threads:
View with errors still saved, and still works...
Parsing error when creating view
-Vaibhav Chaudhari

Creation of Database View , Projection View

Hi ABAP EXPERTS,
Can anyone plz send me the step by step creation of DATABASE and PROJECT VIEWS. Just steps by step explanation will do , screen shots will be more than appreciated.
Kind Regards,
Sunil Ranal.

Database View (SE11)
Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set. In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.
Check this link for database view creation.
http://help.sap.com/saphelp_40b/helpdata/en/cf/21ed06446011d189700000e8322d00/content.htm
Projection View
Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed. A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.
Check this link for Projection view creation.
http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ed20446011d189700000e8322d00/content.htm
Regards,
Maha

Query on Projection View

Similar Messages

Maybe you are looking for