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.

Similar Messages

Project Server 2010: PWA Removing Default Project Site Security Groups When Creating a New Project

I looked for this specific issue with Project Server 2010/PWA/SharePoint and could not find an exact answer... hopefully someone can help.
We are currently using Project Server 2010 and have a number of project site templates that are used dependent upon the enterprise project type selected. Each of these project site templates have unique permissions which should create the default security
groups on the project site upon publishing/syncing:
<Project Name> Members
<Project Name> Owners
<Project Name> Visitors
<Project Name> Project Managers (Project Web App Synchronized)
<Project Name> Team Members (Project Web App Synchronized)
Web Administrators (Project Web App Synchronized)
Whether a user creates a project through PWA or Project Pro 2010 and imports the project into PWA, we get a weird result in the Site Permissions of the newly created project site. PWA will remove all default security groups from the project site template
and add a whole list of users in the Site Permissions list without groups.
Once the project is published and the project site is created, we can then go back and add those default security groups back in the project Site Permissions and even add a couple of custom groups without them being removed on all subsequent project syncs
or publishing.
How do we get PWA to not overwrite the project site templates' security groups and place each user in the proper default security groups? At the same time, how is PWA adding a number of users into the Project Site Permissions?
Thanks in advance.

Paul,
Thanks for that information. Right now we are using the Test environment to turn the Auto-sync feature back on. I suspect that the reason this is happening is due to PWA groups/categories/security templates. There may be more than one PWA group that is "overwriting"
the default project site groups upon initial creation of the project. We will look further into the security settings to tighten up the policies.

Project Server default groups when we create new project site

Hi,
When we create new project site in project server 2013 in site settings page some default groups are already present with some default permissions and some default members.
Interesting thing is that the members of these group are same when ever we create a new site.
Can you please help me understand, what these groups are, how they get created and how they are having some default members. Where are these members coming from.
Our project server is having project server permission mode.
Thanks,
Bhawna.

I briefly searched the MSTechNet but was not able to find a succinct article on this point for 2013, if someone has that, can they pls share. However, if you read most of the articles under this area,
you get the idea.
http://technet.microsoft.com/en-us/library/fp161361(v=office.15).aspx
From 2010 this applies and is still "similar"
http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
In 2013, for every Project Site (connected SharePoint site as it is now called in 2013), 2 Site specific SharePoint security groups are created: "SiteProjectName Project Managers (Project Web App Synchronized)"
& "SiteProjectName Team Members (Project Web App Synchronized)".
And Web Administrators (Project Web App Synchronized) is also created.
In addition, the default SharePoint groups for: Site Members, Site Owners, Site Visitors are present but remain empty.
Project Server controls the creation of these groups and the membership. The membership is a "formula" that goes something like this: If the user is the Project Owner then put them in the PM group.
If the user is a PWA Administrator, then put them in the Administrators group. If the user is a team member on the project, then put them in the Team Members group. There are other factors like RBS that are used in the formula.
Reading the descriptions of the groups reveals that for Project Managers =
Users who have Published this project or who have Save Project Permission in PWA.
For Team Members = Users who have assignments in this project in PWA.
I believe these are the old 2010 descriptions and actually Team Members = anyone who is part of the Build Team even if no assignments.
Further complicating matters is that if you are a site collection admin, you will see all the groups, for PWA and for all the project site (b/c you are actually seeing the site collection groups).
But only the ones mentioned above apply specifically to this project site.
Hope this sheds some light on the topic,
Thanks, Eric S. Pcubed

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

Projection views vs SE16

Hi,
We can use SE16 for selecting few fields of table which we want to dispay.
But is there any particular technical reason why projection views are used for doing the same thing?
Regards,
Subhashini

Hi,
Projection views are used to mask out certain fields of 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 only refer to one table. Selection conditions cannot be specified for projection views.
In an INSERT with a projection view, the fields which were masked out are supplied with their initial values, thus avoiding NULL values.
and you don't have to worry for masked fields even while programming using select and all.
Rgds/Abhi

Problem with showing a group of records in dynamic page (PLS-00428 error)

Hi
I have problems with viewing a group of records from db. I've created Page, which "Page Type" attribute is "PL/SQL". In "PL/SQL Code" field, I've written very simple SQL query: "SELECT * FROM PORTAL_DEMO.EMP ;"
I'd like to generate HTML table with it's result. Unfortunately, every time I get the same Exception:
Error 30584: DBMS_SQL has raised an unhandled exception. ORA-06550: line 1, column 7: PLS-00428: an INTO clause is expected in this SELECT statement
Is it necessary to write a COURSOR (and use HTP function) to realize this functionality? I succeed, trying this way - but it is very uncomfortable ( a lot of code ).
What I have done in wrong way?
Please help me.
Best regards
Mario

How do I handle this?

Grid using Object Oriented View

Can anyone send me program for grid using object oriented view.

hi Sandeep,
please look at this code
REPORT Z_PICK_LIST .
TABLES: RESB.
SELECTION-SCREEN BEGIN OF BLOCK BL1 WITH FRAME TITLE TEXT-BL1.
SELECT-OPTIONS: S_WERKS FOR RESB-WERKS," Plant
S_AUFNR FOR RESB-AUFNR," Order number
S_BDTER FOR RESB-BDTER." Req. date
SELECTION-SCREEN END OF BLOCK BL1.
PARAMETERS: P_VARI LIKE DISVARIANT-VARIANT DEFAULT '/STANDARD'.
DATA: BEGIN OF OUT OCCURS 10,
AUFNR LIKE RESB-AUFNR, " Order number
MATNR LIKE RESB-MATNR, " Material
BDMNG LIKE RESB-BDMNG, " Requirements in UM
MEINS LIKE RESB-MEINS, " Unit of Measure (UM)
ERFMG LIKE RESB-ERFMG, " Requirements in UE
ERFME LIKE RESB-ERFME, " Unit of Entry (UE)
MAKTX LIKE MAKT-MAKTX, " Mat. description
END OF OUT.
INCLUDE Z_ALV_VARIABLES.
INITIALIZATION.
REPNAME = SY-REPID.
PERFORM INITIALIZE_FIELDCAT USING FIELDTAB[].
PERFORM BUILD_EVENTTAB USING EVENTS[].
PERFORM BUILD_COMMENT USING HEADING[].
PERFORM INITIALIZE_VARIANT.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM F4_FOR_VARIANT.
AT SELECTION-SCREEN.
PERFORM PAI_OF_SELECTION_SCREEN.
START-OF-SELECTION.
PERFORM GET_ORDERS.
PERFORM GET_MATERIAL_DESCRIPTION.
END-OF-SELECTION.
PERFORM BUILD_LAYOUT USING LAYOUT.
PERFORM BUILD_PRINT USING PRINTS.
PERFORM WRITE_USING_ALV.
FORM INITIALIZE_FIELDCAT *
--> P_TAB *
FORM INITIALIZE_FIELDCAT USING P_TAB TYPE SLIS_T_FIELDCAT_ALV.
DATA: CAT TYPE SLIS_FIELDCAT_ALV.
CLEAR CAT.
ENDFORM. " INITIALIZE_FIELDCAT
*& Form GET_ORDERS
text
FORM GET_ORDERS.
SELECT AUFNR MATNR BDMNG MEINS ERFMG ERFME
FROM RESB
APPENDING TABLE OUT
WHERE XLOEK EQ SPACE " deletion indicator
AND XWAOK EQ 'X' " goods movement indicator
AND WERKS IN S_WERKS " plant
AND BDTER IN S_BDTER " req. date
AND AUFNR IN S_AUFNR. " pr. order
ENDFORM. " GET_ORDERS
*& Form GET_MATERIAL_DESCRIPTION
text
FORM GET_MATERIAL_DESCRIPTION.
SORT OUT BY MATNR.
LOOP AT OUT.
SELECT SINGLE MAKTX
INTO OUT-MAKTX
FROM MAKT
WHERE MATNR EQ OUT-MATNR
AND SPRAS EQ 'EN'.
MODIFY OUT.
ENDLOOP.
SORT OUT BY AUFNR MATNR.
ENDFORM. " GET_MATERIAL_DESCRIPTION
FORM TOP_OF_PAGE *
FORM TOP_OF_PAGE.
DATA: L_POS TYPE P.
first line
WRITE:/ TEXT-001. " Plant:
IF S_WERKS-HIGH NE SPACE.
WRITE: S_WERKS-LOW, TEXT-TO1, S_WERKS-HIGH.
ELSEIF S_WERKS-LOW NE SPACE.
LOOP AT S_WERKS.
WRITE: S_WERKS-LOW.
ENDLOOP.
ELSEIF S_WERKS-LOW EQ SPACE.
WRITE: TEXT-ALL.
ENDIF.
L_POS = ( SY-LINSZ DIV 2 ) - ( STRLEN( TEXT-TIT ) DIV 2 ).
POSITION L_POS. WRITE: TEXT-TIT.
L_POS = SY-LINSZ - 20.
POSITION L_POS. WRITE: TEXT-011, SY-UNAME RIGHT-JUSTIFIED. " User:
second line
WRITE:/ TEXT-002. " Order:
IF S_AUFNR-HIGH NE SPACE.
WRITE: S_AUFNR-LOW, TEXT-TO1, S_AUFNR-HIGH.
ELSEIF S_AUFNR-LOW NE SPACE.
LOOP AT S_AUFNR.
WRITE: S_AUFNR-LOW.
ENDLOOP.
ELSEIF S_AUFNR-LOW EQ SPACE.
WRITE: TEXT-ALL.
ENDIF.
L_POS = SY-LINSZ - 20.
POSITION L_POS. WRITE: TEXT-012,SY-DATUM. " Date:
third line
WRITE:/ TEXT-003. " Req. Date:
IF S_BDTER-HIGH(1) NE '0'.
WRITE: S_BDTER-LOW, TEXT-TO1, S_BDTER-HIGH.
ELSEIF S_BDTER-LOW(1) NE '0'.
LOOP AT S_BDTER.
WRITE: S_BDTER-LOW.
ENDLOOP.
ELSEIF S_BDTER-LOW(1) EQ '0'.
WRITE: TEXT-ALL.
ENDIF.
L_POS = SY-LINSZ - 20.
POSITION L_POS. WRITE: TEXT-013, SY-PAGNO. " Page:
ENDFORM. " TOP_OF_PAGE
FORM END_OF_LIST *
FORM END_OF_LIST.
DATA: L_POS TYPE P.
ULINE.
WRITE:/ '|', TEXT-021. " Delivered by:
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|', TEXT-031. " Received by:
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
WRITE:/ '|'.
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|'.
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
ULINE.
WRITE:/ '|', TEXT-012. " Date:
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|', TEXT-012. " Date:
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
WRITE:/ '|'.
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|'.
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
ULINE.
ENDFORM. " END_OF_LIST
*& Form WRITE_USING_ALV
text
FORM WRITE_USING_ALV.
Look this code*****
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
I_PROGRAM_NAME = REPNAME
I_INTERNAL_TABNAME = 'OUT'
I_INCLNAME = REPNAME
CHANGING
CT_FIELDCAT = FIELDTAB.
IF SY-SUBRC 0.
WRITE: 'SY-SUBRC: ', SY-SUBRC,
'REUSE_ALV_FIELDCATALOG_MERGE'.
ENDIF.
LOOk this code also.*********
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = REPNAME
i_callback_pf_status_set = 'PF_STATUS_SET'
i_callback_user_command = 'USER_COMMAND'
I_STRUCTURE_NAME = 'OUT'
IS_LAYOUT = LAYOUT
IT_FIELDCAT = FIELDTAB
I_DEFAULT = 'A'
I_SAVE = G_SAVE
IS_VARIANT = G_VARIANT
IT_EVENTS = EVENTS[]
IS_PRINT = PRINTS
TABLES
T_OUTTAB = OUT.
IF SY-SUBRC 0.
WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_LIST_DISPLAY'.
ENDIF.
ENDFORM. " WRITE_USING_ALV
***************report over***************
HOPE THIS CODE HELPS U
Reward if its useful.............
thanks and regards
suma sailaja

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

What is the use of Database View, maintenace , projection and Help view

hello friends,
I created tables..and set check table relation.
how to create Database View, maintenace , projection and Help view
phani

Hi,
have a look at this.
4 type of views
database
maintainance
help
projection view
check this link as well
(https://forums.sdn.sap.com/click.jspa?searchID=9904886&messageID=4885135)
Database views are implemented with an equivalent view on the database.
Projection views are used to hide fields of a table (only projection).
Database views should be created if want to select logically connected data from different tables simultaneously.
Database views implement an inner join.
Application programs can access the data of a database view using the database interface. (Just as we write select queries on database tables, we can write them for views as well.)
Includes in Database Views
An entire table can be included in a database view. In this case all the fields of the included table will become fields of the view (whereby you can explicitly exclude certain fields).
To include one of the tables in the view, enter character * in field View field, the name of the table to be included in field Table and character * again in field Field name on the View fields tab page of the maintenance screen of the view.
You can also exclude individual fields of an included table. If you do not want to include a field of the included table in the view, enter - in field View field, the name of the included table in field Table and the name of the field to be excluded in field Field name.
Inserts with Database Views
If a database view contains only one single table, data can be inserted in this table with the view .
You have the following options for the contents of the table fields not contained in the view:
If the field is defined on the database with NOT NULL as initial value, the field is filled with the corresponding initial value.
If the field is defined on the database as NOT NULL without initial value, an insert is not possible. This results in a database error.
If the field is not defined on the database as NOT NULL, there will be a NULL value in this field.
A maintenance view permits you to maintain the data of an application object together.
The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
Read only: Data can only be read through the view.
Read, change, delete, insert: Data of the tables contained in the view can be
changed, deleted, and inserted through the view.
Read and change: Existing view entries can be changed. However, records
cannot be deleted or inserted.
Read and change (time-dependent views): Only entries whose non-time
dependent part of the key is the same as that of existing entries may be
inserted.
Maintenance View ( SE54 )
You can use a maintenance view to maintain data, which is distributed over several tables, at the same time.
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
Creating maintenance View:
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecdf446011d189700000e8322d00/frameset.htm
regards,
vipul

How to view all photo's in an Aperture project using Front Row?

My projects have folders below them where I actually store the photos. In Front Row I cannot select a "top level folder" (let's say a project in Aperture) and press the play button on the Apple remote. Instead, it drills down into the project/folder until I have reached a folder that doesn't contain subfolders anymore. The effect is that I cannot simply see all photos in a project.
I suppose I can work around this by creating a dummy folder in the project, copying all photos of the project into that folder and use that to view it in Front Row, but I'm hoping there is a setting somewhere that would circumvent this stupid behavior?

Hello Keaux2r,
Do you mean that you want to use command to remotely check the updates?
We could use the PsExec tool to conduct the remote control.
1. Download the tool and copy to file to C:\Windows\System32
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
2. Run cmd as administrator
3. We could run the command psexec \\<computername > -u <username> -p <password> <command> to run command in remote computer.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Can i use adobe pdf viewer dll in educational commercial project in c

I want to read PDF file in my project ..for that i want PDF viewer..so m asking you ..can i use adobe PDF viewer in my project.
Its a educational product for one of my client.
Regards,
Shain Singh

You can write software which uses an installed copy of Adobe Reader and its interfaces.
You cannot distribute the DLL by itself, or include it in your project files.
You can apply for permission to distribute Adobe Reader as a complete installer, subject to license.

Org.xml.sax.SAXException: Invalid element    error when using code in view project

I have a SOAP (RPC style) client bundled in a jar. It uses Axis1.4.
I have created a ADFBC model project with programmatic view & entity objects that uses this soap client for CRUD operations.
The Model project works fine when I run the Appmodule and a standalone java tester class.
This model project is then deployed as a library and included in a different ADF web application.
When running this application, I get the following exception for one method.
Has anyone faced this issue? Any idea what's going on?
Surprisingly, "dbAttributes" -the cause of the error is not even in the User class (or any other class in the entire application)!
I am using JDeveloper 11.1.1.5. Issue occurs in integrated wls.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: SomeClass - dbAttributes
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:localhost.localdomain
org.xml.sax.SAXException: Invalid element in some.package.User - dbAttributes
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1359)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:173)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at some.package.ManagerSoapBindingStub.createUser(ManagerSoapBindingStub.java:879)
at some.package.Proxy.createUser(Proxy.java:294)

PROBLEM SOLVED.
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
org.xml.sax.SAXException: Invalid element in
I think this is a very common problem, and the sad thing is there are so many forums with no answers. I was getting this error because I was using client stubs generated by wscompile instead of wsdl2java. Once i used the stubs from wsdl2java, the error vanished****. I think its because the wscompile classes do not have property descriptors for each field in the response class. an example of such descriptors would be:
        typeDesc.setXmlType(new javax.xml.namespace.QName("https://ns.ns.btu", "LoginResponseData"));
        org.apache.axis.description.ElementDesc elemField = new org.apache.axis.description.ElementDesc();
        elemField.setFieldName("sessionID");
        elemField.setXmlName(new javax.xml.namespace.QName("https://ns.ns.btu", "SessionID"));
        elemField.setXmlType(new javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "int"));
        elemField.setNillable(false);
        typeDesc.addFieldDesc(elemField);The wsdl2java classes do have these descriptors for each field.
Please also look at the following links if you still having problems:
http://marc.info/?l=axis-user&m=103705794612785&w=2
http://www.opensubscriber.com/message/[email protected]/1877996.html

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

Create a Custom View in Project Server 2010 that is Visible in MS Project

Hello All,
We want our PMs to consistently report Physical % Complete, but couldn't find an existing "Status" or "EVM" view. So, in Project Server 2010, using Server Settings > Look and Feel > Manage Views, I created a customized project
view using existing fields (no customized fields, if that matters). The problem is that I cannot find the view when I open MS Project. Under Manage Views, in the Format View section, I have selected "Gantt Chart (Views)" for the Gantt
Chart format field. The view defaulted to "Timesheet" for the Grouping format field. Under the Security Categories section, I have selected My Projects and My Tasks. I have not applied a Filter. Any ideas why I cannot find
this new custom view in MS Project?
Was I supposed to create the new customized view directly in MS Project? If so, where would I find the steps to do that? Thank you!
Julie

Julie --
Nice try, my friend. Your only mistake was trying to create the Microsoft Project view in PWA. You have to open the Enterprise Global for editing in Microsoft Project, and then create the custom view and table in the Enterprise Global. To
open the Enterprise Global for editing, click File > Info > Manage Enterprise Global. When you finish creating the custom view and table, then save, close, and check in the Enterprise Global file, and then exit Microsoft Project completely.
The next time you or any of your PMs launch Microsoft Project and connect to Project Server, the custom view and table will be visible for every current and future project. Hope this helps.
Dale A. Howard [MVP]

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

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

Similar Messages

Maybe you are looking for