Live SAP NETWEAVER Online Training Classes by Experts | Acutesoft
India:+91 (0)8885575549, 040-42627705 | USA: +1 973-619-0109 | UK: +44 207-993-2319








Download [PDF]

  • Overview of the SAP Netweaver

      Internal structure of JAVA
      Working with JAVA stack
      START and STOP the Java engine
      Major roles in SAP EP
      EP Versions
      H/W and S/W requirements
      Installation of EP 7.0
      Creating Users and assigning Roles to Users
      Creating Groups and assigning groups to Users
      Role Upload
      Batch input
      Understanding the Transport functionality
      Creating Transport package
      Exporting and Importing Transport packages
      System Object
      Creating System Objects
      Creating System alias and User Mapping
      FPN (Federal Portal Network ) Global Portal.
      Portal Components
      Creating iviews/pages/worksets/roles/users
      Object relation : Delta Link / Copy
      Business packages
      Creating custom Business Packages
      Permission on the portal content
      Locking the user / resetting PW
      Creating new portal desktop
      Importing template theme
      Internationalization (multi linguistic)
      Support and messages
      Configuring Single Sign On
      Logon Tickets
      Connecting to Portal to R/3 server
      Deploying support packages through SDM and JSPM
      How to change SDM password
      JCO connections
      SLD Connections
      Configuring NWDI and NWDS
      Activate Emergency user SAP Roles, transactions, BSP applications, Webdynpro applications from Backend system to portal
  • Admin Tools
      Config tool
      Visual admin tool, SDM tool
      Visual Composer tool
  • SAP XI/PI Configurations
      Integration Builder
      Integration Repository
      SAP XI Adapter’s configuration
      IDOC / RFC
      JDBC / JMS
  • SAP XI/PI XI Administration
      Handling caches
      Integrating BW server with XI
      Creating BW server with XI
      Handling Acknowledgement for IDOC
      Transport XI content using CMS
      Creation New users
      CPA Cache refreshing
      Trouble Shooting
  • BI (Business Intelligence) (BW)
      Report authorization
      Installation business content




For updated Schedules please contact


  • What’s the difference between SAP Enterprise Portal and SAP Netweaver Portal?

      Before SAP’s strategy turn towards the SAP Netweaver Architecture, what we commonly refer to as “SAP Portal” was called just that or SAP Enterprise Portal. It was just a way to identify this SAP standalone product that was capable (and still is) to connect with all kinds of external systems. These systems could be SAP modules or external systems built on different technologies, such as proprietary client systems or legacy systems. By shifting it’s strategy around Netweaver, SAP put the Portal inside the Netweaver platform, arranging its components in order to improve and simplify it’s communication with other systems, as well as harmonizing some of its core capabilities and re-utilize those of the Netweaver platform. In a daily basis, we just refer to it as SAP Portal and specify the version (e.g. Portal 6.0, Portal 7.0 or NW Portal).
  • How can I check the installed version of ESS/MSS?
      Take note of the following steps in order to find out if indeed you have the ESS and MSS components and in which versions do you have them. Please note that there are alternative ways to check this like, e.g., using the Visual Administrator tool. This is just a way that works for me because most of the times clients won’t allow access to the V.A. tool by external consultants.
  • What checklist items should I follow to check an ESS Portal installation?
      This must be one of the most asked topics in SDN and there are lots of references in the web. My first recommendation is that you start by reading my post “Employee Self-Services Initial Steps Wiki”. This “ESS Initial Steps” wiki intends to provide a hands-on initial contact with the ESS implementation.
  • What are the main components of the SAP Netweaver Portal?
      SAP NetWeaver Portal unifies key information and applications to give users a single view that spans IT silos and organizational boundaries. It allows you to take full advantage of all your information resources – and maximize the return on your IT investments. And, its predefined business content accelerates implementation and reduces the cost of integrating your existing systems.
  • What’s the relation between the Netweaver Portal and the Universal Worklist (UWL)?
      The Universal Work list is for the Netweaver Portal what the SAP Business Workplace is for the ERP system. So if you want to enable any Workflow activities using the Portal, ESS and MSS, you will need to use the Universal Work list so that users receive their tasks and act upon them. The UWL is tied to the backend using a Portal System connector which has to be configured before being able to use it. Many users complain about data refresh issues using the UWL. Even though SAP is aware of this and try to advise some workarounds, like the optimization of the delta pull mechanism, the UWL is still the main functionality to deliver work items and tasks to users in the Portal, coming from SAP Business Workflow or Guided Procedures tasks. The UWL is delivered with a standard configuration but usually SAP consultants customize it to meet the client’s and project requirements. See how to configure the UWL for Guided Procedures on Composition Environment.
  • What’s the difference between a Portal role and an ERP role?
      This question arises some doubts, mainly in beginners starting to work with Portal. The role assignment function in the portal allows role assignment to users and groups. These roles will reflect the user’s or group’s function within the company (example: ESS, MSS, HR Administrator, etc.). For a Portal user to run properly, the person responsible for User Management will have to assign both portal roles as well as ERP roles. There are, however, situations for which only an ERP role is assigned.
      Portal roles define how portal content is grouped together and how it is displayed in the portal navigation area. By assigning a portal role to a user or group, you’ll define which content is available for a certain user or group.
      ERP roles define a set of authorization objects. By assigning an ERP role to a user or group, you grant the set of authorizations that the role defines to the user or group. In the portal, SAP recommends that you work with portal roles.
  • How does the Portal connect to the ERP?
      The main Portal object which is needed for the Portal to connect to the ERP is what is commonly referred to as a System. Systems are PCD objects, such as folders, pages or iViews. What this means is that Systems must have a unique ID, a prefix (typically com.companyname) and a name. Systems have specific parameters that need to be configured, in order to enable the connection between the portal and the backend (ERP). Ideally, you will have created a customer folder in the PCD and you should create any needed systems in a specific client folder, in a folder name such as ‘Systems’.
      Systems can only be maintained using the System Landscape Editor, which is an option which is only available for the under System Administrator role.
      Although systems can be transported through the portal transport mechanism, they don’t need to be and, in my opinion, they shouldn’t. This is because the systems that are accessed from a development portal are normally different to the systems accessed by QA and production portals – they connect to different backends!
  • What is Single Sign-On (SSO)?
      SAP defines Single Sign-On (SSO) as the following:
      Single Sign-On (SSO) is a key feature of the Enterprise Portal that eases user interaction with the many component systems available to the user in a portal environment. Once the user is authenticated to the enterprise portal, he or she can use the portal to access external applications. With SSO in the Enterprise Portal, the user can access different systems and applications without having to repeatedly enter his or her user information for authentication.
      The Enterprise Portal SSO mechanism is available in two variants depending on security requirements and the supported external applications:
      SSO with SAP logon tickets
      SSO with user ID and password
      Both variants eliminate the need for repeated logons to individual applications after the initial authentication at the enterprise portal. Whereas SSO with SAP logon tickets is based on a secure ticketing mechanism, SSO with user ID and password forwards the user’s logon data (user ID and password) to the systems that a user wants to call.
      In case you need to know and understand the necessary steps to configure SSO, please read my post Configure Single Sign-On (SSO) on the Portal and the ERP.
  • How can I change a standard ESS application to meet my client’s own needs?
      Well, this is a hot topic on SDN. I must say that I’ve had lots of challenges regarding this matter, due to client’s requirements and short time to develop. In terms of WebDynpro Java, there is more than one way to change ESS and MSS standard applications, as well as some workarounds. In my experience, the most controlled and effective way to do this is using the Netweaver Developer Infrastructure (NWDI) as a kind of middle-ware and access the ESS and MSS applications source code directly. This versioning system allows developers to import ESS and MSS software components into their own desktops as local projects. Once here, they can work on them, doing the necessary changes. When they want to see the changes, they will generally check-in their development activities (NWDI transport requests) and view them directly in the Development Portal. There are several key points to have in mind when performing changes to standard ESS and MSS applications, using NWDI:
      Start by understanding very well how each application is built; not all of them are clear, they can include comments in German or Indian and they sometimes use external Development Components and use the Floor plan Manager (FPM), which isn’t clear to everybody;
      The NWDI doesn’t know how to manage a new Support Package implementation along with your own changes. Please be aware that whenever a new Support Package is installed, all your custom coding, bindings, context elements, model changes, etc. will be overwritten. A good and thorough documentation will help you manage these challenges;

Make sure to trace the boundaries between your job and technical tasks that will need to be performed in NWDI. Usually the client wraps everything in a global ‘Portal’ subject, and you’ll be responsible for everything. A good basis team which is able to solve issues with NWDI is also a plus.