SAP Enterprise Portal is designed to empower folks to collaborate successfully across the internet on any given job at any time and from anywhere. As the leading enterprise portal offering available on the market right now, SAP Enterprise Portal incorporates each platform expertise and content material in its distinctive offering.Subsequently, it offers workers and external stakeholders, such as clients, suppliers, enterprise companions, and investors with a role-based mostly, central entry level to personalized information, applications, and services. As with any platform, it is basically useless until there are applications that run on it. SAP supplies clients with a leap start in creating such applications by providing business packages with focused content for varied roles within the organization, or external to it.
The role is without doubt one in every of the central ideas of the mySAP Enterprise Portal. A job is a group of tasks, companies and information for a bunch of users. The role defines which service and data the user should be in a position to access and the actions she or he might perform. The position additionally defines how the visualization of the contents and the navigation structure within the mySAP Enterprise Portal. A job might contain all kinds of knowledge and combines every part the consumer will see on his or her mySAP Enterprise Portal. Roles are stored in the Portal Content material Listing (PCD). Within the SAP Enterprise Portal 5.0, the PCD is a file system through which the objects necessary to build roles are stored.
Person access to content material is set by function definitions. A portal position is a set of content. Whereas portal content material is developed to allow access to data relevant to the organization during which the portal is deployed, roles outline the subset of content obtainable to each purposeful function within the organization. Users are assigned to the role or roles that provide content relevant to them. A consumer has entry to the content material that has been assigned to all of his or her roles.
The function definition determines the navigation structure throughout the portal. The navigation structure consists of the top-level navigation bar, and the detailed navigation tree. The top-level navigation bar is a collection of tabs in the title area of the portal header. A user navigates portal pages and services by clicking tabs in the high-stage navigation bar.A web page can show a detailed navigation tree. The navigation tree presents a hierarchical checklist of portal pages and services. A user can navigate portal pages and companies by clicking on the nodes within the detailed navigation tree. Whether or not detailed navigation timber seem, and the configuration of both the highest-degree navigation and the detailed navigation is decided by the position definition.
An iView is a logical portal content material object representing a visual application or a component thereof.IViews are usually based on Portal Components, the implementation of IViews.Through out the IView configuration a system alias is assigned. This system alias specifies the back end system, the IView is linked to. There are various kinds of IViews obtainable comparable to completely different connectivity technologies. Throughout the IView Configuration the identify of the corresponding backend service is configured.
CRM UI Frame Work
The controllers are the principle parts of the framework.SAP delivers a number of controllers to offer completely different view on data like checklist view, hierchy, html, ...
Position based display screen appearance: Different roles can have completely different views on applications.Context-conscious navigation: Utility assigned to the function might be shown also in case of navigation through hyperlinks only with the view assigned to this specific role.
Each IView is assigned to a Service in a Backend System. SAP EP helps completely different IView Templates for different Technologies for Backend Services.The related CRM transactions for the CRM Roles have been modified from the User Interface Expertise ‘Dynpro’ to the User Interface Know-how ‘Enterprise Server Pages’. Therefore many of the IViews of the CRM Enterprise Bundle are based mostly on the IView Template for BSPs. The IViews comprise the title of the corresponding BSP, some attributes and an ordinary System Alias SAP_CRM. The IViews for SAP BW Stories comprise the System Alias SAP_BW. These IViews are primarily based on the BSP technology, too.Some roles comprise IViews to be related to a SEM System. The Standard System Alias is SAP_SEM.With the System Alias the roles of the business package deal include the information about the back end system type for each IView.
Import Editor
The next rules apply for storing the migrated objects in the goal system:
The portal system is ready up to issue SAP logon tickets. In other phrases, the login module stack utilized by the portal authentication scheme ought to contain the login module CreateTicketLoginModule. By default the portal is set as much as subject logon tickets,therefore you do not want to make any changes. For extra data, see Portal Platform Safety Guide B Single Signal-On B Single Signal-On with SAP Logon. Tickets B Configuring Portal Server for SSO with SAP Logon Tickets .You may export the Certificate: Choose System Administration B System Configuration and select Keystore Administration within the Detail Navigation. Select Obtain verify.der File and choose a Folder to repeat the File to. Unzip the File.In the back end system use transaction STRUSTSSO2 to check the imported certificates. You can import the certificate with this transaction.
User Administration
For authentication based mostly on SSO the next configurations are necessary:
Related Posts
SAP CRM Technology Overview
CRM Software Logistics and Support
SAP ABAP All Topics Complete Courses
SAP CRM All Topics Complete Courses
The role is without doubt one in every of the central ideas of the mySAP Enterprise Portal. A job is a group of tasks, companies and information for a bunch of users. The role defines which service and data the user should be in a position to access and the actions she or he might perform. The position additionally defines how the visualization of the contents and the navigation structure within the mySAP Enterprise Portal. A job might contain all kinds of knowledge and combines every part the consumer will see on his or her mySAP Enterprise Portal. Roles are stored in the Portal Content material Listing (PCD). Within the SAP Enterprise Portal 5.0, the PCD is a file system through which the objects necessary to build roles are stored.
Person access to content material is set by function definitions. A portal position is a set of content. Whereas portal content material is developed to allow access to data relevant to the organization during which the portal is deployed, roles outline the subset of content obtainable to each purposeful function within the organization. Users are assigned to the role or roles that provide content relevant to them. A consumer has entry to the content material that has been assigned to all of his or her roles.
The function definition determines the navigation structure throughout the portal. The navigation structure consists of the top-level navigation bar, and the detailed navigation tree. The top-level navigation bar is a collection of tabs in the title area of the portal header. A user navigates portal pages and services by clicking tabs in the high-stage navigation bar.A web page can show a detailed navigation tree. The navigation tree presents a hierarchical checklist of portal pages and services. A user can navigate portal pages and companies by clicking on the nodes within the detailed navigation tree. Whether or not detailed navigation timber seem, and the configuration of both the highest-degree navigation and the detailed navigation is decided by the position definition.
An iView is a logical portal content material object representing a visual application or a component thereof.IViews are usually based on Portal Components, the implementation of IViews.Through out the IView configuration a system alias is assigned. This system alias specifies the back end system, the IView is linked to. There are various kinds of IViews obtainable comparable to completely different connectivity technologies. Throughout the IView Configuration the identify of the corresponding backend service is configured.
CRM UI Frame Work
The controllers are the principle parts of the framework.SAP delivers a number of controllers to offer completely different view on data like checklist view, hierchy, html, ...
- Every display half (search, serach outcome, element area) has it‘s personal controller
- The controller receives information inserted by the consumer and calls business logic by means of the interplay layer of the model
- The controller receives data from the mannequin after knowledge processing and decides now how you can display the data.
- The controller calls the specific views to show the data.
Position based display screen appearance: Different roles can have completely different views on applications.Context-conscious navigation: Utility assigned to the function might be shown also in case of navigation through hyperlinks only with the view assigned to this specific role.Each IView is assigned to a Service in a Backend System. SAP EP helps completely different IView Templates for different Technologies for Backend Services.The related CRM transactions for the CRM Roles have been modified from the User Interface Expertise ‘Dynpro’ to the User Interface Know-how ‘Enterprise Server Pages’. Therefore many of the IViews of the CRM Enterprise Bundle are based mostly on the IView Template for BSPs. The IViews comprise the title of the corresponding BSP, some attributes and an ordinary System Alias SAP_CRM. The IViews for SAP BW Stories comprise the System Alias SAP_BW. These IViews are primarily based on the BSP technology, too.Some roles comprise IViews to be related to a SEM System. The Standard System Alias is SAP_SEM.With the System Alias the roles of the business package deal include the information about the back end system type for each IView.
Import Editor
The next rules apply for storing the migrated objects in the goal system:
- If the trail in the Portal Catalog is totally identical within the source and goal methods, the item in the goal system is overwritten.
- If the trail doesn't exist within the goal system, it is automatically created.
- If the trail within the target system differs at a certain location from that of the supply system, the path is only created anew beginning with the situation the place the source and goal methods differ.
- The names of folders in the Portal Catalog are misplaced through the transport and are changed with the IDs in the Portal Catalog after the import. You therefore see the item ID of the folder within the target system, and never the title that you recognize from the source system.
The portal system is ready up to issue SAP logon tickets. In other phrases, the login module stack utilized by the portal authentication scheme ought to contain the login module CreateTicketLoginModule. By default the portal is set as much as subject logon tickets,therefore you do not want to make any changes. For extra data, see Portal Platform Safety Guide B Single Signal-On B Single Signal-On with SAP Logon. Tickets B Configuring Portal Server for SSO with SAP Logon Tickets .You may export the Certificate: Choose System Administration B System Configuration and select Keystore Administration within the Detail Navigation. Select Obtain verify.der File and choose a Folder to repeat the File to. Unzip the File.In the back end system use transaction STRUSTSSO2 to check the imported certificates. You can import the certificate with this transaction.
User Administration
For authentication based mostly on SSO the next configurations are necessary:
- Test the System Object: Select System Administration B System Configuration and select System in the Element Navigation. Seek for the System Object and navigate to the detail view with proper mouse click on Edit. Choose Property Category User Management. The log on method have to be LOG ON TICKET.
- Create or discover out the corresponding consumer in CRM System: Select transaction SU01 in the CRM System to create or edit a user. Assign the corresponding function to the person and test the permissions in transaction PFCG.
- Create a Person in Portal: Choose User Administration B Customers and choose Create Users within the Element Navigation. Enter a minimum of Consumer ID, last name, first title and e mail address. The Person ID in Portal and Back end system must be similar.
- Assign User to a role: Choose User Administration B Roles and seek for the Consumer you may have created.Navigate in edit mode with the link edit to these user. Seek for the Position you wish to assign on the proper hand side and select add. Dont overlook to save the settings.
Related Posts
SAP CRM Technology Overview
CRM Software Logistics and Support
SAP ABAP All Topics Complete Courses
SAP CRM All Topics Complete Courses
No comments :
Post a Comment