Netweaver Portal Project Blueprint [Project Name] DOCUMENT INFORMATION & HISTORY [Company Name] DOCUMENT INFORMATION SHEET PROJECT/ORGANIZATION: 1. DOCUMENT CATEGORY: Blueprinting DOCUMENT: Business Blueprint CREATE DATE: Version Date 1. Author 2. Approvals 3. Date 1. 0 1. 1 Project Team Customer name: Project name: Project location: Name Role Contacts e-mail Phone Project Manager Functional Design Technical Design Graphics Design CONTENT 1 Management summary4 2 Netweaver Portal Program Strategy4 2. 1 Portal Program4 2. 2 Portal Scope4 2. 3 Target Portal Users4 . 4 Technology Strategy4 2. 5 Rollout, Release and Upgrade Strategy4 3 Portal User Management Strategy5 3. 1 User Persistence Design5 3. 2 Portal Authentication Procedure5 3. 3 User Groups and Master Data Design5 3. 4 Single Sign On Concept6 4 Portal Security Concept6 4. 1 Technical and Integration Design6 5 Functional Specification6 5. 1 Relevant Business Intelligence Content6 5. 2 Portal Content Application Specification7 5. 3 Required Content Source Development and Customizing7 5. 4 KM/Collaborative Content Specification 8 5. 5 Search Requirements9 Portal User Interface, Navigation and Framework Design10 6. 1 Layout10 6. 2 Portal Navigation Structure/Content 10 6. 3 Portal Theme11 6. 4 Portal Desktop and Display Rules12 7 Portal Content Directory Structure and Objects Specification14 7. 1 PCD Structure14 7. 2 iView Specifications15 7. 3 Page Specifications16 7. 4 Worksets Specifications18 7. 5 Role Specifications18 8 Custom Development20 8. 1 PAR File Development20 8. 2 Webdynpro Development20 8. 3 HTML Code / Dev 20 1 Management summary 2 Netweaver Portal Program Strategy 2. 1 Portal Program . 2 Portal Scope 2. 3 Target Portal Users Position Role Count Total 2. 4 Technology Strategy 2. 5 Rollout, Release and Upgrade Strategy [The first rollout of the Enterprise Portal project would be on xxxxx] 3 Portal User Management Strategy 3. 1 User Persistence Design 3. 2 Portal Authentication Procedure Authorization Strategy (Please describe the mechanism of accessing the back end system) 3. 3 User Groups and Master Data Design Position Role Count Total 3. 4 Single Sign On Concept . 4 Portal Security Concept 4. 1 Technical and Integration Design Functional Specification 5. 1 Relevant Business Intelligence Content [The reports provided in the first rollout of the Enterprise Portal project are as follows] Report Functional Area 5. 2 Portal Content Application Specification Application Name: Type: General Description Documentation Location of Business Blueprint documents 5. 3 Required Content Source Development and Customizing [The following development work may be needed in the SAP R/3 systems to get the data required for example for an MSS report. Iview Name Employee Basic Information Source System
SAP R/3, SAP BW Content Source Description The latest employee information to be fetched from R/3. Input Parameter Personnel Number Output Parameter Parameter Extract Details Employee Name Infotype 2 Personnel Number Infotype 1 Position Infotype 1 Birth Date Infotype 2 Organization Description Table HRP1000 Initial Infotype 2 Gender Infotype 2 Network ID Infotype 105 Nationality Infotype 2 Data fetch from BW Creating RFC by using the MDX for reading the infocube and returning the information. ] 5. 4 KM/Collaborative Content Specification [Sample
The following list contains all applications and their specifications: Search, the TREX search engine will be used in order to implement all search functions. Any items indexed will be available as search results on the search engine. The search engine will be provided on the main navigation bar of the portal and available of all pages viewed by the end user. Discussion groups, this shall be implemented using the collaboration features and facilities of the portal. Users shall be grouped according to their role or position, each role has access to limited resources that matches role specification.
Text areas are available to enter questions or discussion topics. Radio buttons are available to select target group. The user can sort discussions by date or topic. Headlines, a folder stored in KM or CM repository shall contain all headlines to be presented on the “Brand Site” portal main page. Announcements, several folders, 8 folders, stored in KM or CM repository shall contain all headlines to be presented on the “Brand Site” portal main page. Each folder represents a certain position or role. The matching user types shall be receiving announcements that have been entered to the system.
Quick polls, for administrative use, the administrator shall be granted access to enter a question and list of choices. The end user shall preview the quick poll on an iView located at the portals main page] 5. 5 Search Requirements [Users shall be provided a search facility to search the following: e. g Content – Reports stored in the Knowledge Management System Manuals – IR, … People Intranet Discussion Forums (threads) ] 6 Portal User Interface, Navigation and Framework Design 6. 1 Layout The banner Top-Level Navigation Tool Area Detailed Navigation
Content Area Dynamic Navigation ] 6. 2 Portal Navigation Structure/Content The Portal Navigation Structure provides a mechanism by which the user can access the portal content. The navigation structure provides the path using which specific content could be reached. There are multiple levels of navigation starting from the top level navigation and proceeding to the detailed navigation in the navigation panel of the portal interface. The user can switch from one content to another by routing back and forth using the navigation structure. ] 6. 3 Portal Theme
The portal theme defines the appearance of the portal elements, font size, colors and contrast of the user interface elements of a portal desktop and does not define the layout, structure or contents of a portal desktop. You create a portal theme in the Theme Editor. Is there as standard SAP User Group, form or template that can be used as a model? If so, please identify it. The SAP Enterprise Portal has out-of-the-box themes such as: SAP Streamline SAP Tradeshow SAP Chrome SAP High Contrast [Paste screen shot of theme here. Indicate key areas such as color, font, size, etc.
Since there are 100’s of potential areas to modify, try to include areas where modifications are made from standard only. ] 6. 4 Portal Desktop and Display Rules The following objects are involved in defining the portal display at runtime: Portal Desktops SAP Enterprise Portal supplies a default portal desktop, named Default Framework Page, which comprises the default framework page (Default Framework Page) and a number of standard portal themes. Location in Portal Catalog: Portal Content > Portal Users > Standard Portal Users > Default Portal Desktop (pcd:portal_content/every_user/general/defaultDesktop) Framework Pages
The default framework page supplied with SAP Enterprise Portal provides the navigational and structural components required to navigate and operate the portal. It can be modified to create framework pages to meet the specific requirements. Location in Portal Catalog: Portal Content > Portal Users > Standard Portal Users > Default Framework Page (pcd:portal_content/every_user/general/frameworkpage) Portal Themes Refer to the ‘Themes’ Section Rule Collection SAP Enterprise Portal out-of-the-box supplies a default rule collection object, named Master Rule Collection (main_rules).
The portal runtime analyzes the display rules defined in this object to determine which portal desktop to provide to a user when he or she logs on to the portal. Location in Portal Catalog: Portal Content > Portal Administrators > Super Administrators > Master Rule Collection (main_rules) (pcd:portal_content/administrator/super_admin/main_rules). 7 Portal Content Directory Structure and Objects Specification [The different Portal Content Objects that constitute the ‘’Brand Site’ are listed below] 7. 1 PCD Structure 7. 2 iView Specifications iView 1 e. g. Employee Basic Information
Type: Category: Description: Personalization: Eventing: Interfaces: iView Title IView Type: jspdynpage, webdynpro, bw/bi, km, url, sap IView Template Developer iViewProperties Value (You do not need to list all iView Properties. List the ones that have been changed only. ) 7. 3 Page Specifications Over here please indicate how you want the iViews displayed within the page and the layout of page. Page Title (You do not need to list all Page Properties. List the ones that have been changed only or are custom) Page Properties Value Page Layout (See above List for Values) Page Content List . 4 Worksets Specifications Workset Title Workset ID Developer Workset Structure (count of what’s in Workset and type Ex : Pages ( 5) IViews (3) Workset Properties 7. 4. 1. 1. 1 Value Can be Merged Yes/No Merge ID Description Display in Portal Yes/No Entry Point Yes/No Sort Priority 7. 5 Role Specifications Role Title Role ID Developer Request Date (MM/DD/YYYY) [You do not need to list all Roles Properties. List the ones that have been changed only] Roles Properties Value User Administration: List all LDAP groups related to this role: List all Merged Roles. (If any)
Describe in details the procedures of assigning the roles to user groups. Specify whether it’s done manually or automatically. Note: Role structure should include all worksets / pages/ folders added to this role. 8 Custom Development 8. 1 PAR File Development [Provide pseudocode, DFD, code, iView dependencies, etc related to PAR File development] 8. 2 Webdynpro Development [Provide pseudocode, DFD, code, iView dependencies, etc related to PAR File development] 8. 3 HTML Code / Dev [Provide references to stylesheets, URLs, layout, screenshots, templates, code, etc. to support what was built. ]