EHP6: Side Panels

Context-sensitive side panels work only with NWBC (version 3.5 or later). Side Panels enhance traditional SAP GUI transactions, by providing context-sensitive information. To date, SAP has shipped side panels for over 500 SAP GUI transactions in ECC 6.0 EHP6 (and over 900 in EHP6 SP4).

For an example of a side panel in action, see this video: SAP Visual Enterprise .

For more details, see the SAP Library documentation.

For details about each Chip, including tags and prerequisites, there is documentation available in the Chip Catalog.

Experts from the Business Suite have also written this three-part blog:

Side panel for SAP Business Suite - Overview

Side panel for SAP Business Suite (2) - Adapting SAP’s Side Panel content and creating new content

Side panel for SAP Business Suite (3) - How to build a master data and a chart-based CHIP?

Collaboration Chips

These Chips allow you to display information from your SAP JAM server alongside an ABAP transaction. There are currently two Chips available: Feeds, and Groups. Since some of you have asked about how to configure these, I have reproduced the documentation below.

As a prerequisite, you need to configure your SAP JAM server as described in this Configuration Guide.

For general information on SAP JAM, see this Press Release. : SAP JAM - Secure Social Collaboration Where You Work.

Feeds Chip

Description
In the Feeds CHIP, you can view feeds, create feed entries, or reply to them.

Tags
/BSSP/:BORTYPE (BOR Object Type) and Tags for all Key Fields of the BOR Object Type

Prerequisites
The business function BC_SRV_STW_03 must be activated in the side panel system. Furthermore make the necessary customizing settings in Customizing for SAP NetWeaver under "Application Server/Basis Services/Collaboration".

Groups Chip

Description
In the Groups CHIP, you can create or change groups, or mark them as completed.

Tags
/BSSP/:BORTYPE (BOR Object Type) and Tags for all Key Fields of the BOR Object Type

Prerequisites
The business function BC_SRV_STW_03 must be activated in the side panel system. Furthermore make the necessary customizing settings in Customizing for SAP NetWeaver under "Application Server/Basis Services/Collaboration".

This documentation is also available in the Chip Catalog.

FAQs for the Side Panel:

• How do I find out which business functions to activate for each side panel?

At present, the business functions you need to activate are documented in the Chip Catalog itself (separately for each Chip). For the future, we are in the process of creating an XLSX with all side panel chips, their availability (by SP), plus the business functions they require. 

• Where can I find a list of chips?

For NetWeaver Chips: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/62/88224213424de5aeb2cef68a7d7d00/content.htm?frameset=/en/a9/db5099ff304335b7db73a244950cda/frameset.htm

For Business Suite Chips: SAP Note 1718873 (Note: This list covers only the first 74 Chips, released for EHP6, SP01. That is, there are now approximately 30 more Chips available, which are not included in this note. Documentation for these Chips is available by selecting them directly in the Chip Catalog. However, this SAP Note provides a useful introduction).

• Where are the chips for the side panel or a list of applications that use the chips?

In your development system, Call transaction BSSP_CONTENT. (This is a support transaction for administrators/consultants. It is available with EHP6 SP05.)

Here you can find information about roles, side panels, and the transactions in which they are used.

Use the generic search (for example, SAP_ for roles and BSSP_SP* for side panels).

EHP5: Page Builder

Creating mashups to design home pages that enable users to access their main tasks and that provide the option to adapt the page, for instance by adding CHIPs to it in which their favorite Web pages are embedded.

Many Page Builder entry pages and work centers are role-specific, which means that they work only with NWBC (version 3.5 or later). For more details, see the SAP Library documentation.

EHP4: Floorplan Manager (FPM)

NWBC integrates different UI Technologies such as FPM to reduce development costs and to improve the user experience. With a highly configurable and adaptable UI we follow the pattern approach to achieve a harmnonized UI and  coherent user experience. More information.

The following video shows how easy it is to configure your application using FPM, modification free: NWBC 4.0 with FPM

EHP2: POWLs

(NWBC is the recommended client)

Both Power Lists (POWLs) and NWBC are role-based, using the PFCG role repository, SAP recommends that you use SAP NetWeaver Business Client with POWLs. The following SCN Wiki provides more information on POWLs; SAP Library documentation on POWLs is also available.

Video (links to YouTube)

SAP NetWeaver Business Client 4.0 in 5 Minutes

Experi: Happy with NWBC 4.0

Blogs

Note: These are external blogs. The opinions expressed in them are not necessarily those of SAP.

Bluefin: Can NWBC compete against the new competition?

A new User Experience with SAP Netweaver Business Client

UI Innovations optimized for NWBC

Web Dynpro-based UI Innovations

HCM Renewal 1.0

works only in NWBC (version 4.0).

With this new functionality, SAP offers a more user friendly, harmonized and intuitive
experience. In this blog,  New SAP HCM Functionality - HR Renewal 1.0, SAP Mentor Jarret Pazahanick provides details and some nice screenshots ofthis innovation. As you see here the new landing page with swim lanes:

Integration with NWBC

CRM, Web Client UI Framework

You can use individual WebClient UI components integrated with SAP NetWeaver Business Client (NWBC).

This integration is meant for users who use mostly applications that do not use the WebClient UI with NWBC and need to access only a few WebClient UI applications.

See chapter 9, How-to Guides, How To Integrate CRM WebClient into NWBC

Introduction

Setting up the RFC Connection: ABAP

1. In NWBC (or SAP GUI), open RFC Destination: Display/Maintain (SM59).
2. Create a new ABAP connection (type 3).
3. Enter the settings you need:

• Target Host, System No. : Get these from the System Selector
• IP Address: By default the IP Address field may be blank. Just switch to Hostname and back, and the IP Address appears (derived from the target host you just entered).

Testing the ABAP RFC connection

1. Choose Test Connection, from the toolbar at the top.. You should see something like this:

 

Setting up the RFC Connection: HTTP

1. Again, create a connection, this time HTTP Connection to ABAP System (Type H), and make the following settings:

• Target Host, Service No. (= Port No.) : Get these from the System Selector

Testing the Connection: HTTP

This is a blog series in three parts::

• RFC Connections
• Trusted Relationsships
• Single Sign-On

Users want single sign-on. ie They want to simply log on once, then  consume applications, regardless of which system these come from, without having to enter their password more than once.  Setting up the trusted relationship enables you to set up single sign-on for users.

Before you start: Make sure you have completed Part One: Setting Up RFC Connections

From that blog, note down the name of the RFC destination (ABAP connection, type 3 is fine).

Before you create the trusted relationship, you need to assign your user to a role. This role contains the authorization profile, which in turn specifies: system ID, client, user, and optionally a transaction.

The trusted relationship you then create specifies the RFC destination (from part one, which in turn specifies connection type, IP address, client) and user.

The whole setup looks a bit like this:

Before you start:

• Make sure you have completed Part One: Setting Up RFC Connections. From that blog, note down the name of the RFC destination (ABAP connection, type 3).
• Make sure you have 2 identically-named users, one in each system, ERP and CRM. Check that they are both OK, by logging on to each system in turn.

1. Creating an authorization role and profile (in PFCG)

Start in the calling system - that is, the CRM system (M20 in this blog)

1. Open the transaction Roles (PFCG) and create a role. I called mine ZJP_TRUST.
2. On the Authorizations tab, click the icon beside Profile Name  (tooltip = Propose Profile Names):

The system automatically generates a profile name:

3. Choose Save.

4. Once the profile is created, choose Change Authorization Data. (You don't need a template).

5. Add a new profile, by choosing from the toolbar, then enter the authorization object S_RFCACL.

6. Drill down, then enter the following:

7. Choose Generate (also from the toolbar) and save your changes. (If necessary, choose Generate again from the dialog that appears).

8. Now switch to the user tab.

9. Add your user to the role and do a user comparison.

10. Save your changes.

2. Creating a Trusted-Trusting Connection (in SMT1)

1. Still in the CRM System, M20, open the transaction Trusted-Trusting Connections, (SMT1).
2. Choose Create from the lower toolbar.
3. Work through the wizard:
   • Enter the RFC Destination that you created in Part One (connection type = ABAP, type 3).
   • Log on to the ERP System, M10, by entering your user and password. The system will then log on to our ERP System, M10, and create a relationship from M10 to M20.
   •   Display Information: All the necessary information, such as the application server name and the security key is supplied automatically.
   •   Configuration (optional): You can specify a validity period or a specific transaction.

   • Finish: When you press this pushbutton in the last dialog box, the trust relationship is set up and can be used.

4. Save your changes and log off from M20.

3. In the ERP System: Creating a Trusted-Trusting Connection (in SMT2)

1. Log on to the ERP System, M10 - using the same user to which you added the authorization role in Step 1 of this tutorial.
2. Open the transaction Trusted-Trusting Connections, SMT2.
3. Switch to the tab Systems that trust current system.
4. Select the CRM System, M20 and check its status, by choosingSingle Status.
5. The status should turn green.
6. Now test the connection:
   1. Double-click the system M20
   2. Choose Transaction Call.
   3. Enter any transaction for which you are authorized, eg SE80. (Optional: Choose New Session = Yes).

The CRM System, M20, should open in a new NWBC shell.

OK, you are nearly finished. You just need to do Part Three: Configuring Single Sign-On, which doesn't take long.

For more information, eg troubleshooting your connections, the following may help:

SAP Library: SAP NetWeaver Business Client, Chapter 7.4 Trusted Relationships

This is a blog series in three parts:

• RFC Connections
• Trusted Relationsships
• Single Sign-On

OK, you have connected the two systems. And you have set up a trusted relationship. However, the trusted relationship is not single sign-on; it enables you to set up single sign-on.

The last step (and it is relatively quick and painless) is to set up single sign-on, based on the trusted relationship.

Before you start:

Make sure you have completed Part One (RFC Connections) and Part Two (Trusted Relationships) of this series.

CRM System: Logon Ticket Administration

1. In the CRM System, open transaction Logon Ticket Administration for SSO, SSO2
2. Enter the RFC destination you created in Part One (ABAP connection, type 3).
3. Choose Execute .
4. In the logon screen that appears, log on to the ERP System, M10.
5. On the screen that appears, make sure all profile parameters are up-to-date, by choosing Enter Certificate in ACL and, if necessary, Certificate List (F9).

Your screen should look roughly like this:

If so, you're done! You have now fulfilled all the prerequisites and can add CRM functions to your ERP System roles, simply by following the SAP Library documentation:

9.3 How to Integrate CRM in NWBC

For more information, see also:

Authentication and Single Sign-On with SAP NetWeaver Business Client (NWBC) - blog by Nikhil Dhairyawan

NetWeaver Single Sign-On Space

TechEd 2013: Bangalore

Teched Las Vegas and Amsterdam are over.

However, I'll be posting blogs and a Q&A here, so please bear with me ;-).

Join us in Bangalore December 11-13.

My blog: SAP NetWeaver Business Client: TechEd 2013 Sessions - you may want to bookmark this, because I'll be adding to it - Session info before and during, plus I hope to blog on my experiences, questions asked etc, after I get back from Amsterdam.

General information on all locations: http://www.sapteched.com/home.htm

Follow us on Twitter @NWBClient_SAP

NWBC: Connecting 2 Backend Systems - all 3 parts

OK , some of you have spotted this already, but I 've just finished a blog on this here:

Connecting Two Backend Systems - Part One (RFC Connections)

Connecting Two Backend Systems - Part Two (Trusted Relationships)

Connecting Two Backend Systems - Part Three (Single Sign-On)

Among other things, it is probably useful background info for TechEd - not essential, but could provide additional insights for 1 of our exercies in CD267.

NWBC: New Roadmap

I've already included this in the blog on the SAP Mentor Monday webinar, but just in case you missed it:

NWBC 4.0 - Roadmap for October 2013

BTW - this is the roadmap version we'll be showing and talking about at Teched (Las Vegas, Amsterdam, and Bangalore), so if you've any questions or feedback, feel free to either leave a comment OR ask us live.

SAP Mentor Monday on NWBC - Update

OK, the session is now over, but I would highly recommend the recording:

Public SAP Mentor Monday Webinar - It's all about NWBC! - Monday the 23rd (except in NZ)

Here's a recap of what went on:

SAP Mentors Matt Harding and  John Moy talk about NWBC: What is it? Does it actually work? Has anyone got any real world experience to share? (Hint: the answers to questions 2 and 3 are Yes and Yes).

... while PO Claudia Binder and I answer the question: What does the future hold for NWBC?

SAP NetWeaver Business Client: Sample Roles

We are often asked about roles. Ideally, you need to ask a consultant. However, I hope this list of roughly 130 sample roles will help you get started with the Business Client. SAP delivers many predefined roles, which you can use as templates, by copying and adapting. These roles were developed as part of best practices and follow these naming conventions:

• SAP_AIO_* (= All In One) - These single roles were designed as templates for you to define your own enterprise-specific roles.
• SAP_BPR_* (=Best Practice Role, delivered in EHP3)
• SAP_NBPR_* (= New Best Practice Role, delivered in EHP4)

For more documentation on each of these roles, see SAP Library: Preconfigured Roles, POWER Lists, and Reports

Key

Purple = Role with FPM application(s)  + WD applications + POWLs

Blue = Role with WDA applications + POWLs

Green = Role with POWLs

Black = Roles with transactions only

Roles in EHP7

Roles in NWBC (for EHP7) 

Roles in EHP6

Some sample documentation. I hope to add to this later.

Note: Each of these root documents is a placeholder. The useful information is in the structure to the left, so make sure you haven't hidden the structure ;-):

SAP Retail

Single Roles Logistics General

Single Roles Materials Management

Single Roles Logistics Execution

Single Roles Sales and Distribution

Single Roles Basis

Roles in EHP5

The following business function documentation contain a list of new roles available in EHP5 for each business function:

Business Function ERP_NWBC_ROLES = ERP Roles for SAP NetWeaver Business Client

Business Function HCM_NWBC_ROLES = HCM Roles for SAP NetEaver Business Client

For more information on each of these roles, see SAP Library: Roles in SAP NetWeaver Business Client (again the useful info is in the structure to the left).

Roles in EHP5: Page Builder Roles

(I have color-coded these black, because, apart from the WD-based home page, they seem to contain only transactions. Please correct me if I'm wrong; I haven't been able to check every single one).

SAP_EP_RW_FDMN

SAP_EP_RW_FKMN

SAP_EP_RW_FSCM-CR

SAP_EP_RW_CO_KSMN

SAP_EP_RW_CO_KAMN

SAP_EP_RW_CO_CK00

SAP_EP_RW_CO_KKPM

SAP_EP_RW_CO_KEMN

SAP_EP_RW_IM

Roles in EHP4

Other All-in-One Roles

Roles in EHP3

Using  the sample roles: Getting started

.      To find what transactions and applications are available, choose a role from the list above and open it in Role Maintenance(PFCG) , in Display Mode.

Look for the different application types as follows:

• Transactions
• POWL: Type = WDY_APPLICATION, Object = POWL
• FPM application or WD ABAP application = WDY_APPLICATION  (many but not all FPM application names contain the string “FPM”.
• Page Builder: Type = WDY_APPLICATION, Object = WDR_CHIP_PAGE .
  There are only 12 of these. These are intended as templates to get you started. Generally, we expect you to want the freedom to choose your own content. They are listed at the end of this document
• Side panel = Type = WDY_APPLICATION, Object = WDR_CHIP_PAGE.
  Unlike Page Builder cockpits, the Node Option = Side Panel (View this by choosing Other Node Details)
• Web page : Type = Web Address or File, Object = <URL>.

For example, the role Production Planner SAP_NBPR_PRODPLANNER-S looks like this:

You can now extend the role by copying transactions or folders from other roles.

For more information, see SAP Help Portal: Role Maintenance in PFCG

Using the sample roles: Next steps

I hope to add more information to this blog as it becomes available.  In the meantime, to find out more, your best bet is to ask a consultant for your  line of business.

More information on innovations in the Business Suite:
SAP Business Suite Road Maps for User Experience

1. www.sapsolutionbrowser.com
2. www.sapimprovementfinder.com

Alternatively, have a look at the RDS packages available: www.sap.de/rds

Single Sign-On in Remote Scenarios

The first part of this blog series dealt with accessing one or more ABAP back end systems (see here NWBC meets Single Sign-On: Simplify Secure Data... | SCN). Part two describes how to access multiple systems. Referencing from one system to the other via PFCG mapping.

Example:

You have a leading system (also your role system, let's call it system one, SY1) but you need to execute certain applications in a remote system (SY2). Alternatively, you are using what is known as side-by-side scenario* (see the screenshot below) to enhance transactions of older systems (e.g. by nice HTML5 charts), integrated remotely in PFCG, with a side panel that was not available before NetWeaver 7.03.

The procedure below describes a side-by-side scenario where a user calls a classic dynpro (sales order) with remote side panel content (charts, route planer). The main application running in SY1, the side panel content running in SY2.

*If your SAP ERP system is based on a release older than SAP ERP 6.0 EHP6 (not

older than SAP ERP ECC 6.0) and you want to avoid having to upgrade the system, you

can use the side panels in a side-by-side scenario. This means that the side

panels and application transactions do not run in the same physical system. The

role system contains the side panel definitions, CHIPs (including the

corresponding coding) and the tag table entries, based on SAP NetWeaver 7.31 and

SAP Business Suite Foundation 7.31 SP03 or higher. The application system

(back-end server) contains the dynpro applications and does not have to be

upgraded to SAP ERP 6.0 EHP6.

Source: SAP Note 1795171

Prerequisites

NWBC 4.0, SSO 2.0, SAP NetWeaver 7.3

Procedure

1. Implement SSO with Kerberos (see How-To-Videos), create your SAP GUI system connection, for example System 1, in SAP Logon.
2. Set up the NWBC and SAP GUI connections as described in part 1 of this blog series.
3. Define the RFC destinations used by NWBC in SM59 (see SAP NetWeaver Business Client Administration Guide -> Role Maintenance in PFCG -> Remote Systems).
4. Insert remote applications in PFCG and reference the target system (see SAP NetWeaver Business Client Administration Guide -> Role Maintenance in PFCG -> Remote Systems).

Define RFC Connections in SM59

Information to access transactions in system SY2 is derived from SY2CLNT001. SY2CLNT001_HTTP is mainly used for accessing web based applications.

Note: You set up these destinations for NWBC only. At runtime, RFC technology is not involved; NWBC simply evaluates a number of destination properties in order to generate navigation URLs.

Define RFC Destination for Application in Remote System (SY2CLNT001)

Tab: Technical Settings

Relevant fields: Target Host, System Number

Tab: Logon & Security

Relevant fields: Client

Note: SNC and load balancing settings are derived from the SAP GUI connection that is assigned to the NWBC connection for SY2. Define such NWBC connections for each SY2 application server (details in SAP NetWeaver Business Client End User Guide -> Configuring System Connections -> SAP GUI Logon Description).

Define RFC Destination for Application in Remote System (SY2CLNT001_HTTP)

Tab: Technical Settings

Relevant fields: Target Host (<server>.<domain>), Service No. (<port>).

To activate SSL, you can either create a destination SY2CLNT001_HTTPS, or activate it in a SY2CLNT001_HTTP connection in the “Logon & Security” settings as shown below.

Relevant fields: Client, SSL

Remote Applications in PFCG

Result

Runtime: Single Sign-On for user, SNC for transaction, SSL for Web Dynpro Applications

Find more information in the SCN Space for SAP NetWeaver Single-Sign On.

Find more information on side panels in Julies article: NWBC: Side Panels, POWLs and Web Dynpro ABAP

Nowdays we meet with this phenomenon more and more. Let's check, what is the cause of this behavior.

Users can start "transaction" /N/OPT/VIM in the SAP GUI:

The result is, they get a different menu tree, a menu tree for Opentext VIM:

However, when users start the "transaction" /N/OPT/VIM in NWBC Desktop Client:

they get an error message: Transaction /OTP/VIM is unknown

The reason is the following:

/OPT/VIM is NOT A TRANSACTION, but an Area menu, that can be checked in transaction SE43:

This is the reason, why it cannot be called in NWBC as a transaction. NWBC builds the menu tree once during log on, and to use this menu, the menu tree should be built again.

To make the users be able to use this menu in NWBC, the menu has to be assigned to the user as a Default menu in SU01:

When this is done, and the user logs into NWBC, then he is able to use this newly assigned menu structure:

To use /OPT/VIM menu structure in NWBC, this is the only way to do it. The transactions are available for starting also without a menu tree, when users still want to use SAP Standard Easy Access Menu. It is important, that for using SAP standard / Area menus in NWBC, checkbox 'Use SAP menu instead of User Menu' has to be set:

General:

Which features are available for which SAP NW AS ABAP for NWBC 3.5 or Higher?

See here: SAP Library: Business Client Versions

Authentication

Q: How does the SAP GUI protocol recognize the NWBC web logon (in PFCG mode)?

A: NWBC uses HTTP to contact the ABAP system, which then sends back a MYSAPSS02 cookie. This is
then used to talk to the ABAP system. This should be in the documentation – See SAP Lbrary : 7.1 NWBC
and Authentication

Caution:

It is the responsibility of the customers to make whatever security settings are necessary in the browser. Pay particular attention to your proxy settings. NWBC uses the security settings from the Internet Explorer. NWBC does not store or persistently keep any authentication data in any form.

Recommandation:

To make data access both simple and secure we recommand combining NWBC with SAP NetWeaver Single Sign-On.

As of release SAP NetWeaverSingle Sign-On 2.0, SAP NetWeaver Single Sign-On offers support for SPNEGO for ABAP.

Leveraging this Kerberos-based single sign-on technology, you can implement an SAP NetWeaverSingle Sign-On solution for your NWBC quickly and easily, and without the need for a Java stack.

See how in the following blog by Sandra Thimme:

NWBC meets Single Sign-On: Simplify Secure Data Access (Part 1)

Compatibility

Q: Are NWBC 3.5 and 4.0 downwards compatible?

A: Yes, NWBC 3.0, 3.5 and 4.0 can connect to all backends from NW 7.00 SP21, NW 7.01 SP06 onwards.

This means that end users can connect to any system with this release or highrer. However, some features
require a higher release- such as Side Panel, which requires ECC6.0, EHP6.

Documentation

NWBC 3.5

NWBC 4.0

Main SAP Notes for NWBC requirements are:

1029940 SAP NetWeaver Business Client Requirements and Restrictions

1620514 NWBC 3.5 for Desktop: Requirements and Restrictions

1620576 NWBC 3.5 for HTML: Requirements and Restrictions

Display of Error Messages

Q: Can you influence the position of error message?

A: No. Error message depends on the application's UI technology. If this is dynpro (SAP GUI), message is displayed in a status bar at the bottom, for e.g. WDA applications, the message is displayed at the top. NWBC cannot influence this.

Performance

General:

NWBC does not change the performance behavior of the contained applications. The shell adds some additional performance on top but this happens in a constant way and does not relate to the performance behavior of the application. The application footprint is the same as if it were running in a standalone scenario.

Q: Can NWBC manage over 10,000 users?

A: Yes, see the section in the documentation on the performance profile for NWBC: SAP Library : 8
Performance Aspects

Q: What are the performance characteristics / bandwidth requirements for NWBC?

A: This is explained in detail in the documentation, in chapter 8 on Performance Aspects and in
subchapters.

Q: Does NWBC support load balancing?

A: You could place a reverse proxy in front of your application servers to spread the load, and allow you to
later dynamically consider additional servers. Or start NWBC for Desktop via the message server to
automatically lock onto the least busy application server.

This is described in detail in the documentation. SAP Library : 3.6 Using NWBC with a Load Balancer

Q: What sort of overhead is there that might affect performance?

A: The performance and overhead footprint of all applications running within NWBC are still the same as if
they would run standalone. The question is what additional overhead does NWBC add?

NWBC for Desktop: It accesses the server only once during startup to authenticate the user and then to
verify that the navigation tree in its cache is still valid. In the usual case, two HTTP requests are all that are
needed once a day for NWBC for Desktop (extra features, such as searching for transactions, does add
additional requests to the server, but these should be the norm on a shop floor).

NWBC for HTML: The server renders the shell. Each interaction with the shell, for example starting a new
application, results in a small amount of network overhead to get a new shell rendered from the ABAP
server, plus of course the ABAP session.

ABAP runtime: The client fires a set of HTTP requests to the server. For the desktop client, it is the
sequence of requests to validate its cache. For the HTML shell it is the series of requests to trigger the
navigation. The ABAP runtime becomes stateful (keeps the ABAP session) for 15-30 seconds, before the
session is cleared again. As such, the overhead is very little on ABAP. (Keep in mind that the desktop client
only calls once on startup.)

In addition, with the v3.5 ABAP runtime (NW7.03+), we have added in memory objects to cache complex
role operations, which will dramatically speed up the HTML shell’s performance if this is preferred.

Q: What are the performance requirements for VPN-/MPLS connections using NWBC 3.0 or the
portal.?

A: The NWBC client requirements are similar to normal applications. Initially, NWBC for desktop loads the
navigation tree and caches it on the client. After caching the network traffic is the same as when an
application is run in standalone mode.

By default, NWBC for desktop uses SAP GUI for Windows instead of SAP GUI for HTML.

Personalization

Q: Can I change the work center/service map icons?

Yes.

• In both 3.5 and 4.0, you can change the Work Center/ Service Map icons in Role Maintenance (PFCG):
  SAP Library: 5.5 Navigation Tree (scroll down to “Other Node Details).
• In 3.5, you can also change Work Center icons by right-clicking the tab. See SAP Library : 2.3 Navigation
  (This is no longer relevant in 4.0).

Q: Can I add custom icons to the work center/service map?

A: No

Q: In NWBC 4.0, can I change the welcome message?

The message on the Index page can be replaced by a different text, even with parameters.

Use parameter WELCOME_MESSAGE in the backend configuration table NWBC_CFG. See also SAP
Library: 4.6 Configuration in Table NWBC_CFG

Q: If an end user makes personalization changes in NWBC are they valid for his or her user ID or for
his or her local installation?

A: All changes stored locally on a user’s PC (for example reordering of work centers / icons for work centers /
hide some work centers / font changes/ etc) do not work on another PC.

All changes within canvas applications are stored on the server and would work on another computer.

Personalization: Options are stored locally and are Windows-user specific. The sequence of the work centers
and the icons are even stored per connection and per user accessing the connection.

Positioning: NWBC vs SAP GUI vs Portal

Q: In what situations would you recommend NWBC over SAP GUI?

A: NWBC is of particular interest to customers familiar with SAP GUI who also want to work with the new
Web Dynpro ABAP screens within one unified environment. NWBC supports role-based navigation so that
the end user sees those applications that are relevant to his or her role.

Q: Does NWBC share technology with SAP GUI?

A: Yes, SAP GUI for Windows is also installed with NWBC since end users want to work with the traditional
SAP GUI screens as well as with Web Dynpro applications.

Q: Will NWBC typically be co-deployed with SAP GUI, as a complementary technology?

A: Generally NWBC and SAP GUI will be installed together although they can be installed separately.

Q: Are there plans to align more closely in future, or merge roadmaps?

Yes. The next versions of NWBC and SAP GUI will be released jointly as one product.

Q: When is NWBC expected to become the ‘go to’ desktop client? Will we start to phase out SAP
GUI? If so, when?

A: NWBC 3.0 is the “go-to” desktop client and is being rolled out externally. You can check the relevant
EHPs in the Product Availability Matrix on the Service Marketplace. NWBC does not replace SAP GUI
because it uses SAP GUI to display the traditional SAP GUI screens.

Q: In what situations would you recommend NWBC over the portal?

A: NWBC is most suited to the needs of the power user, that is, someone concentrating on transactions
processing a large amount of data in an ABAP-centric system landscape. A typical example would be a
payroll clerk. NWBC is of particular interest to customers familiar with SAP GUI who also want to work with
the new Web Dynpro ABAP screens within one unified environment.

Q: In what situations would you recommend the portal over NWBC?

A: The portal is most suited to users working with a variety of systems (SAP and non-SAP) often in different
locations; or for customers who want to integrate Mobile and Cloud solutions. A typical example would be
a Product Manager. The other strengths of the portal include collaboration, document management and
branding.

Q: I have Microsoft Sharepoint/ IBM WebSphere. Should I use SAP Enterprise Portal or SAP
NetWeaver Business Client in conjunction with these?

A: Both SAP Enterprise Portal and SAP NetWeaver Business Client (HTML Client) work with Microsoft
Sharepoint or IBM WebSphere. Which one you use depends on your other requirements – see above.

To integrate NWBC with either Microsoft Sharepoint or IBM WebSphere, see the following documentation:

9.1 How To Integrate NWBC into a Microsoft SharePoint Portal

9.2 How to Integrate NWBC into an IBM WebSphere Portal

Positioning : Desktop vs HTML client

What are the benefits of NWBC (HTML)?

Access to ABAP systems

Zero footprint

Use case for NWBC (HTML):

Extranet: eg Volkswagen runs SAP. Its component suppliers do not, necessarily. They can use NWBC for
HTML To access (parts of) VW's ABAP-based systems.

Q: What are the main differences between the HTML NWBC and the desktop NWBC?

Desktop NWBC performance is better, how much better depends on number of work centers, size of
navigation tree, which browser is used, and the power of the PC

HTML NWBC uses SAP GUI for HTML; desktop NWBC uses SAP GUI for Windows

HTML NWBC has no overflow, no D+D of work centers, no search

All-in-One uses the desktop NWBC

HTML NWBC does NOT use the portal, only ABAP systems

HTML NWBC is aimed at the casual user

The HTML NWBC has an address field for a URL.

Programming Aspects

Q: In the installation under C:\Program Files\SAP\NWBC\ there are a number of executables, dlls and
other files. What do they do?

A: NWBC.exe – That is what gets executed when you click on the icon on the desktop.

NWBCCore.exe – This is the main process to run NWBC.

NWBCSAPlets. Exe – This is an SAP widget engine for SAPLets (not productized)

NWBCURLHandler. Exe – This is a small launcher to react to a URL like: „sap-nwbc://“. It is used to start
NWBC against a specific server. The customer can create “sap-nwbc://xxx” link Web page and by click user
would start NWBC.

sapAcfDummy. Html - Acf specific (Active Component Framework). Used for JGannt/JNett, Microsoft
Office integration

SAPAcfEolasPatch.js

Roles (PFCG)

Q: How much work is involved in maintaining roles in PFCG? Doesn’t that generate work and raise
costs for migrating from SAP GUI to NWBC?

Before you maintain the roles you have to clearly define the business processes. You can then derive the
business roles from these and then turn them fairly quickly into PFCG roles. Creating the menus should
then be straightforward.

In our experience most customers need to spend more time defining their business processes. This leads to
concrete, time-consuming but crucial preliminary questions of the form: “Is Mr. X allowed to do Y or only
Z?” and “To what extent to we want to restrict our employees’ working environment?”

Q: What happens if roles are duplicated?

A: NWBC uses a merging function, so there are no double entries.

Q: Can you import roles from one system to another?

A: Yes, using SM59 see SAP Library: 5.11 Remote Systems

System Connections

Q: Is there a maximum number of systems?

A: There is no technical limitation to the number of systems.

But: The more systems you have the more complex it is to maintain. PFCG was not built to maintain lots of
systems.

If you have lots of systems use the portal. It has better tools.

Q: Is there an .ini file for NWBC?

A: Yes, there is an ini file to maintain technical information as with SAP GUI.

Q: Can you access more than one system?

A: Yes, you can access 2 or more systems by opening 2 instances of NWBC.

Q: While using NWBC, how can I ascertain which system I am logged into (DEV, QA, PRD)?

A: Here, we have to distinguish between NWBC for desktop and NWBC for HTML.

Desktop client : you can find out about NWBC using the menu options Help -> About NetWeaver Business
Client and then you can find out even more by clicking System Information. You can also click on the SAP
icon right at the bottom of the NWBC to access system information.

But that does not tell you whether you are in a QM system etc.

In new versions if NWBC for Desktop such as 4.0 or in the HTML Add-On our developers are working on
theming. For example, you could display the shell in a different colour depending on whether the system is
a production system, a QM system or a development system.

With the HTML version you can specify a Welcome message. This message appears at the top of NWBC.

You could mention the system type (eg QM) in this Welcome message.

HTML Client: Welcome Message (currently only in NW 7.31), see docu chapter 4.6

Here is the technical background:

***

WELCOME_MESSAGE

At runtime, the system selects the welcome message in the logon language.

If no matching language entry is found, LANG=' ' or LANG='*' is used as a fallback.

The welcome message is displayed in NWBC for HTML next to the Log Off pushbutton.

The VALUE field contains the text. You can use the following placeholders:

&NAME&: first name

&SURNAME&: last name

&FULL_NAME&: full name

&USER&: user name

&CLIENT&: client

&SYSTEM&: system ID

***

Q: Does NWBC cause bandwidth problems?

A: Usage of the SAP GUI for Windows instead of SAP GUI for HTML results in a significant bandwidth
reduction. The NWBC for Windows shell is rendered on the client side and the role XML is cached on the
client side. Therefore shell rendering is generally a bandwidth reduction compared with the NetWeaver
Portal shell. Web content (like BSP or Web Dynpro) running within NWBC is unchanged in its bandwidth
requirements.

Q: Is there a maximum number of windows that can be open in NWBC?

A: So far there is no limitation from the NWBC side, except a memory limit. It is possible to open 100
windows, but be careful; some servers limit the number of open sessions. For example, by default, SAP
J2EE limits the number of open Web Dynpro JAVA applications to 20. With SAP GUI you can have a
maximum of 6 windows open in parallel.

Q: Do the connections have to be defined for SAP GUI and for NWBC, that is, twice?

A: Yes.

Q: Which client technology is recommended by SAP for customers running Linux if they use roles
that mix Dynpro and Web Dynpro applications?

A: NWBC for desktop does not run on Linux. NWBC uses SAP GUI for Windows to display dynpros. It does
not use the Java GUI.

However, NWBC for HTML does run in Firefox, which will work on Linux.

Citrix: Q: Does NWBC support Citrix?

A: Yes, Testing@SAP” contains a NWBC installation.

NWBC for Desktop works on Windows platforms, also on Citrix. NWBC for HTML is browser-based (see
SAP’s browser PAM); it also runs in Citrix environments.

Integration

Adobe Reader

Q: Does the documentation specify which version of Adobe Reader has to be installed? Or does
NWBC itself incorporate a specific version of Adobe Reader?

A: There are no specific requirements regarding NWBC and Adobe Reader. When forms are displayed in
NWBC then this involves forms integrated in Web Dynpro ABAP. For information about browser support for
Adobe Forms please read the PAM (Product Availability Matrix), available on SAP Service Marketplace.

Business Server Pages (BSPs)

Q: Are there are any technical restrictions when linking Business Server Pages within the NetWeaver
Business Client?

A: There is no limitation for BSP or Web Dynpro ABAP technology for NWBC.

Business Suite: CRM

Q: Can I integrate CRM Content in NWBC?

Yes:

First, you need to set up a connection and trusted relationship between the two systems:

Connecting Two Backend Systems - Part One (RFC Connections)

Connecting Two Backend Systems - Part Two (Trusted Relationships)

Connecting Two Backend Systems - Part Three (Single Sign-On)

Then, you need to follow the documentation:

SAP Library: How to Integrate CRM Content in NWBC

Business Suite: ESS/MSS

“As of EhP5 for ERP 6.0, We officially support NWBC scenario for ESS/MSS. For casual users like ESS we
position NWBC HTML since it is zero footprint client (no installation). However even NWBC Desktop is
supported.

“You can find the deployment options described in help portals.

http://help.sap.com/erp2005_ehp_05/helpdata/en/44/bfc5a026ea4689a964b14609bd4111/frameset.htm

http://help.sap.com/erp_mss_addon10/helpdata/en/2a/8dcc65a90444e2bf6ab0b39d05b455/frameset.htm

“We have also a consulting note 1450179 that describes all kinds of combinations possible.

“For NWBC environment, we provide POWL for all kind of approval scenarios based on SAP workflow. For
specific approvals like Leave and Time entry approvals there is better functionality offered compared to
UWL (like multiple approvals in a single click).

“There are no restrictions from ESS/MSS WD ABAP application consumption perspective to use NWBC.
However customer must decide switching from portal based on overall requirements like how much they
do specific branding, theming, custom development & help content.

Business Suite: Side Panel

Note: The aim of this section is to cover questions not in the documentation. Before posting an additional
question, please read the documentation: SAP Library : 5.10 Side Panel

General:

Side panel feature requires backend SAP NetWeaver 7.03 = SAP NetWeaver 7.31 or higher together with NWBC 3.5 client or higher. Reason here is that the context-specific side panel requires enhancements in the role maintenance transaction as well as a table for doing the UI field mapping. Downports of PFCG enhancements are out of scope.

Q: Can customers display documentation in the side panel?

A: Yes.

There is an appropriate chip:

Title = SAP Help Portal

Name = X-SAP-WDY-CHIP:WDR_CHIP_IFRAME

Package = SWDP_CCP_WD_API

This is generally available. (It defaults to Page Builder docu, but you can get to SAP Library from there).

Alternatively, Side Panels can include a Web Chip, which expects a URL ; docu can be accessed by URL;
therefore the customer could also make their own.

Q: Are there side panels with map data, for example where a simple address can be displayed?

A: Yes. For example, one could:

1. Create a Web CHIP.
2. Specify the URL for Google Maps.
3. Specify the appropriate URL parameter.

For more details, see SAP Library : 6.7 Side Panel Programming

Q: In which release are the Side Panel and the Page Builder available?

A: NWBC for Desktop 3.5 comes along with the Side Panel. You define the side panel in the back end in
transaction PFCG from release NW7.03 onwards. The same is true of some Page Builder chip features. The
side panel is part of NW7.03, shipping in Suite ECC6 EHP6.
Page Builder is already available with 7.02, Business All-In-One is using this in their shipment

Business Suite: SRM

See also SAP Note 1378659

Business Suite: Web Dynpro ABAP-based Applications

If a screen has been converted to WDA can I still revert to SAP GUI if I prefer the old screen?

SAP does not convert each SAP GUI screen 1 to 1 to a new WDA screen. The new WDA screens are always
part of new process and engineered for support the new process. The assumption is that the SAP GUI

screen is replaced by the new process.
However, users are generally still able to access the old SAP GUI transactions. They are still available in the
system.

It may be the case that the old transactions are no longer part of the role.

Q: What percentage of screens have been converted to WDA? Is there a roadmap for this? Will all
SAP GUI screens be converted eventually?
With EhP6 we have more than 2000 WDA screens. The redesign depends always on the end-user needs
and the corresponding use cases.

Q: How much work is involved for the customer in converting SAP GUI screens to WDA screens?
It depends. As most WDA screens are related to new processes some minor end user training might be
required. As the end user can also personalize the screens, these features need to be explained.
It is possible to configure WDA screens via the Floor Plan Manage (FPM). The customer can also use the
FPM to create his own screens. If the customers uses for example our Business Object Layer (BOL) he can
create the UI via configuration of the FPM against the BOL framework.

Q: Are the new WDA screens automatically available when a new EHP is installed or does each
screen have to be activated?

You need to activate the corresponding Business Functions. Only after a Business Function activation the
new screens will be visible.

HTML5

Q: What does the roadmap look like for rendering HTML5 pages?

A: If a customer has IE 9+ (with an HTML 5 rendering engine) on his computer then NWBC will render HTML
5 based pages.

Keep in mind we always use Internet Explorer as the HTML rendering engine.

IBM WebSphere/ Microsoft Sharepoint

Q: I have Microsoft Sharepoint/ IBM WebSphere. Should I use SAP Enterprise Portal or SAP
NetWeaver Business Client in conjunction with these?

A: Both SAP Enterprise Portal and SAP NetWeaver Business Client (HTML Client) work with Microsoft
Sharepoint or IBM WebSphere. Which one you use depends on your other requirements – see above.

To integrate NWBC with either Microsoft Sharepoint or IBM WebSphere, see the following documentation:

9.1 How To Integrate NWBC into a Microsoft SharePoint Portal

9.2 How to Integrate NWBC into an IBM WebSphere Portal

Microsoft Silverlight

Q: A customer has some Silverlight applications. I assume they are “integrated” in NWBC using a
URL. Is this correct?

A: Yes, they can run Silverlight application as a normal URL-based application. Of course, the Silverlight
plug-in must be installed on the user’s PC.

SAP NetWeaver Portal

Q: How should we deal with users who access SAP both via Portal (casual HCM) and directly
(primary job function)?

A: One option is for them to use the portal most of the time and then to talk directly to the back end using
NWBC for HTML. Another is to use just NWBC for desktop but using a portal connection rather than talking
directly to the back end.

Third-Party Content

Q: What options are there for integrating 3rd party applications in NWBC?.

A: In general, you can integrate any third-party content that can be accessed by URL.

In Web Dynpro, you can integrate 3rd party UI controls via FlashIsland/SilverlightIslands into Web Dynpro
screens.

It’s possible to run/launch 3rd party application from NetWeaver Business Client by defining a new entry in
PFCG with “Web address/file URL” type (like Web Dynpro/Transaction/other types).

Related Content

SCN Space : UI Technology

Web Dynpro ABAP

SAP NetWeaver Portal

SAP Single Sign-On

Copyright

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

Important update (4th June, 2014): SAP no longer advises the use of logon tickets, which are cookie-based. Use assertion tickets instead. (For more information on the difference between the two, see SAP Library 7.3 Logon and Assertion Tickets .)

This is a blog series in three parts:

• RFC Connections
• Trusted Relationsships
• Single Sign-On

OK, you have connected the two systems. And you have set up a trusted relationship. However, the trusted relationship is not single sign-on; it enables you to set up single sign-on.

The last step (and it is relatively quick and painless) is to set up single sign-on, based on the trusted relationship.

Before you start:

Make sure you have completed Part One (RFC Connections) and Part Two (Trusted Relationships) of this series.

CRM System: Logon Ticket Administration

1. In the CRM System, open transaction Logon Ticket Administration for SSO, SSO2
2. Enter the RFC destination you created in Part One (ABAP connection, type 3).
3. Choose Execute .
4. In the logon screen that appears, log on to the ERP System, M10.
5. On the screen that appears, make sure all profile parameters are up-to-date, by choosing Enter Certificate in ACL and, if necessary, Certificate List (F9).

Your screen should look roughly like this:

If so, you're done! You have now fulfilled all the prerequisites and can add CRM functions to your ERP System roles, simply by following the SAP Library documentation:

9.3 How to Integrate CRM in NWBC

For more information, see also:

Authentication and Single Sign-On with SAP NetWeaver Business Client (NWBC) - blog by Nikhil Dhairyawan

NetWeaver Single Sign-On Space

Introduction

In case you didn't find this document by reading Why not to use /nwbc to access NWBC? it's okay but you should still read it in order to understand why this document exists.

Creating a custom ICF External Alias

Go to transaction SICF, press F8 (Execute) on the selection screen. In the next screen press the External Aliases button.

Press F5 (Create) to create a new ICF External Alias.

Name the new ICF External Alias /znwbc and give a description. Now switch to the Trg Element tab.

Expand the hierarchical tree, set the focus on /sap/bc/nwbc and double click it to set it as the target element for the ICF External Alias. Here I would like to mention that if you want to use (or later change to) the SAP NetWeaver User Interface Services (e.g. UI2) version of NWBC, the correct path is /sap/bc/ui2/nwbc.

The new ICF External Alias is now pointing to the ICF NWBC service /sap/bc/nwbc (or /sap/bc/ui2/nwbc),

Configuring the custom ICF External Alias

Numerous configuration changes might be required, such as

• Session Timeout
• Load Balancing
• Compression
• Logon Procedures
• Security
• Error Pages including System Logon configuration (see below)

Whatever configuration is required, it is customer specific e.g. transportable from one system to another and SAP won't interfere with it. You are ready to start using the new ICF External Alias, just point your NWBC or browser to /znwbc and that's it (unless you want to configure it further).

Configuring System Logon

In case you are one of the lucky ones and you have Single Sign-On (SSO) in place for both NWBC for Desktop and NWBC for HTML you will probably want to skip this chapter. If you are not so lucky, here is the deal. By default the System Logon that users are presented with when authenticating to NWBC looks as follows (AS ABAP 7.31)

I don't know about you but I like my web applications a bit more modern. So let's do just that. In the configuration of the new custom ICF External Alias go to the Error Pages tab, select System Logon radio button and press Configuration.

This is what it looks like by default

Change the configuration as follows

If you want, you can configure the System Logon screen further by pressing the Adjust Links and Images button. Here is what your System Logon screen will look like

A definite improvement if you ask me. If you want, you can customize the SAP NetWeaver text (or logo), Logo and Copyright text by using the Adjust Links and Images button as mentioned before.

Conclusion

ICF nodes and External Aliases can be extensively configured and in some situations they have to be configured. That said it makes even more sense to have a custom ICF External Alias so that configurations can be done without affecting the default configuration provided by SAP.

The purpose of this document is to have a place to capture ideas for feature requests and product improvements around The NetWeaver Business Client (NWBC).

Feel free to add items to the list, add columns to the table etc... this is a community resource to own (please read to make sure your idea or a similar one isn't already here before adding it).

This is open to everyone and I don't necessarily expect SAP to deliver any of these suggestions, so you shouldn't either. But hopefully SAP will take the list into consideration when possible.

I’ve been involved in presales activities and customer implementations as well, where requirements as simple as “We would really like to see a picture of the material” came up. In standard SAP GUI this isn’t possible. However with the sidepanel in NWBC, we now have a possibility to view a material image that is context sensitive.

Here’s how to build such a simple chip, that shows an image uploaded via SE78.

Let this be inspiration for what else to build. Share your ideas in the comments section.

Create the web dynpro component

Firstly we need to build a web dynpro component to be used.

Go to transaction SE80 and select Web dynpro component and give your component a name, which fits your namespace.

Give a good description and save it as a local object for now.

After this we need to build create a context, where we can input our material number for identification in the viewer.

Afterwards create the attribute in which we will put the material number, make sure to input the type as matnr as well

Create the view

Now we are ready to create our view.

Select the main view and choose the context tab.

Drag the IMAGE_NODE from the component controller to the context in the context main windows

Afterwards create a new attribute in the context and use the type string

This will act as our image source url. Later we will program the URL.

Now go to the layout tab.

Right click the ROOTUIELEMENTCONTROLLER and choose insert element

Set the ID and set the type as image

As you see in the screenshot below, we now need to connect the source to our context.

Doubleclick the URL in the context

Now it is time to program the url, so our image becomes dynamic. We want the image to change when we select different materials right ;-)

Goto the methods tab and select modifyview. The reason why we are using this method is that it is called everytime an event is happening.

Insert the sourcecode from below

DATA: lo_image typerefto cl_wd_image,

lo_component typeREFTO if_wd_component,

lo_context TYPEREFTO if_wd_context,

lo_controller TYPEREFTO if_wd_controller,

lo_node TYPEREFTO if_wd_context_node,

lo_child TYPEREFTO if_wd_context_node,

lv_matnr type mara-matnr.

Data: i_name TYPE STXBITMAPS-TDNAME value'ZLOGOTEST',

i_id TYPE STXBITMAPS-TDID VALUE'BMAP',

i_btype TYPE STXBITMAPS-TDBTYPE VALUE'BMON',

l_bds_bytecnt TYPE i,

l_bds_content TYPETABLEOF bapiconten.

"First we get our context

lo_component = wd_comp_controller->wd_get_api().

lo_controller ?= lo_component.

CALLMETHOD lo_controller->get_context

  RECEIVING

    context = lo_context.

lo_node = lo_context->root_node.

"Then we get the data from the node IMAGE_NODE, if you have changed this name, then change here.

lo_child = lo_node->get_child_node('IMAGE_NODE').

"Then the value in the matnr attribute

CALLMETHOD lo_child->get_attribute(

  EXPORTING

    name = 'MATNR'

  IMPORTING

    value = lv_matnr ).

i_name = lv_matnr.

i_btype = 'BCOL'.

*-- Get image contents

CALLFUNCTION'SAPSCRIPT_GET_GRAPHIC_BDS'

  EXPORTING

    i_object   = 'GRAPHICS'

    i_name     = i_name "Image name

    i_id       = i_id

    i_btype    = i_btype "Image type(color or gray)

  IMPORTING

    e_bytecount = l_bds_bytecnt

  TABLES

    content    = l_bds_content[]

  EXCEPTIONS

    not_found  = 1

    OTHERS     = 2.

Data: l_length TYPE i,

l_content TYPE tsf_xsf_ct.

CALLFUNCTION'SAPSCRIPT_CONVERT_BITMAP'

  EXPORTING

old_format = 'BDS'

    new_format = 'BMP'

    bitmap_file_bytecount_in = l_bds_bytecnt

  IMPORTING

    bitmap_file_bytecount   = l_length

  TABLES

bds_bitmap_file         = l_bds_content[]

bitmap_file = l_content[]

  EXCEPTIONS

    OTHERS= 1.

Data: w_file TYPExstring,

l_grline TYPELINEOF tsf_xsf_ct,

l_linelength TYPE i.

DESCRIBEFIELD l_grline LENGTH l_linelength IN BYTE MODE.

LOOPAT l_content INTO l_grline.

  IF l_length > l_linelength.

    CONCATENATE w_file l_grline-line INTO w_file IN BYTE MODE.

  ELSE.

    CONCATENATE w_file l_grline-line(l_length)INTO w_file IN BYTE MODE.

  ENDIF.

  l_length = l_length - l_linelength.

1. ENDLOOP.

DATA:url TYPE string,

guid TYPE guid_32,

cached_response TYPEREFTO if_http_response.

CREATEOBJECT cached_response

  TYPE

  cl_http_response

  EXPORTING

    add_c_msg = 1.

* set image to mime

cached_response->set_data( w_file ).

cached_response->set_header_field(

name = if_http_header_fields=>content_type

value = 'image/pjpeg').

cached_response->set_status(code = 200 reason = 'OK').

cached_response->server_cache_expire_rel( expires_rel =

180 ).

CALLFUNCTION'GUID_CREATE'

  IMPORTING

    ev_guid_32 = guid.

cl_wd_utilities=>construct_wd_url(EXPORTING

application_name = 'ZTEST1'"Webdynpro application name

IMPORTING out_local_url = url ).

CONCATENATE url '/' guid sy-uzeit INTO url.

cl_http_server=>server_cache_upload(

url = url

response = cached_response ).

DATA lo_el_context TYPEREFTO if_wd_context_element.

DATA ls_context TYPE wd_this->element_context.

* get element via lead selection

lo_el_context = wd_context->get_element().

* get single attribute

lo_el_context->set_attribute(

EXPORTING

name = `URL`

value = url ).

Ok so now we have set the url to be changed dynamically by the input from the material number. However we still need to input something into the matnr attribute in our component comtroller.

Create the import method

Go back to the component controller and create a new method.

Make sure to mark this method as an interface method.

Create an importing parameter with the structure of MARA

Now use the web dynpro code wizard to set the material number into the context

Remember to press the set operation

Press the ok button and change the last value in the single attribute to the PARAM-IN-matnr

       set single attribute
LO_EL_IMAGE_NODE->SET_ATTRIBUTE(
NAME =  `MATNR`
VALUE = PARAM_IN-MATNR ).

Now right click on your web dynpro component and press activate. Mark everything and press ok

Now it is time for us to create a chip to be used in the sidepanel. This is instead of a web dynpro application

Creating the CHIP

Right click on your newly created web dynpro component and press create à Web Dynpro Chip

Give the chip a saying name and press continue

Save it in a local package

Give a proper display name and description and press save.

Click the inports tab and press the new button

Choose the INPORT_METH that we created in the component controller

If the popup comes up empty, check if you have set your inport_meth in your component controller as an interface method.

Press the new button in the parameters of port INPORT_METH

Select only MATNR, as this is the only one we are using for now.

Mark the line afterwards and press the show tags button

Press the new button in tags for parameter MATNR and input /BSSP/:MATNR (This is SAP standard tag for material number and we might as well reuse this ;-)

Now we are done with the web dynpro component and we move on to creating a role to test with.

Creating the role

Go to transaction PFCG and create a single role with a saying name

Give a proper descripton and switch to the users tab. Assign your user and switch to the menu tab afterwards.

Create a folder and give a saying name. Then press the transaction button and include VA01, VA02 and VA03 in that

Afterwards create an additional folder and double click the folder afterwards. Now press the Other node details and input the following

Application alias = {TR=VA01;VA02;VA03}{WDA=LO_OIF*}

Folder options = Sidepanel

So what does that mean?

Well the folder option is to indicate that this folder is only holding sidepanel content and shouldn’t be visible from the index page in NWBC and the application alias is a place to put which transactions and web dynpro applications this sidepanel is active for. So if you wanted this to work for MM03 as well, what should you input? ;-)

Press save.

Creating the sidepanel page using pagebuilder

Press the little marker next to transaction and select web dynpro application

Make sure that you select the application type: Page. Now enter WDR_CHIP_PAGE as web dynpro application and the application config with a saying name. Press the create button

Now specify a name for the web dynpro component configuration as well, this can be the same. Then save this as a local object

Press continue and save your role.

Now right click on your newly created web dynpro application and press execute.

Internet explorer will open our new pagebuilder page, which is empty at the moment. Press the Wrench icon and select configuration

Press the add button. We are now loading the chip catalog, in here you will find all the chips that you can use for sidepanel content. (NB: it takes a while ;-)

We will search for the one we just created.

Select the entry. Don’t worry that it is grey, this is because we haven’t created a description for it. Press the ok button.

Now it should load the material image chip and you can press save.

Close down internet explorer.

We are now done with the setup and are ready to test our newly created sidepanel. But first we need to upload a picture.

Upload an image

Go to transaction SE78.

Click the import button

Find your BMP picture of your material.

Save the image with the filename of the material number. Remember we have to do this because we are using the material number to construct the dynamic URL.

And choose as a color bitmap image

Press continue.

Now that the image is uploaded we are ready to test our sidepanel content.

Testing our hard work.

Open NWBC and go into VA01.

Input order type and customer name and input the material number.

Doubleclick the material number and open your sidepanel

Et voilá you have now created your own custom sidepanel

After installation of NWBC I wondered how to run it. To be precise I had no idea what to enter into the logon screen as parameters. By default screen comes like this in version 4.0 of  NWBC:

You need to maintain fields Name and URL. Alternatively you can put description of SAP system connection from your SAP GUI. This would go to field: “SAP GUI Logon Description”. Right after you save entry you can access it. After that you get logon screen:

Clicking on Log On button will display pop-up where you enter user’s logon credentials. In my case I got following error:

However if you have everything configured you should be directly connected to SAP System via NWBC. As per instruction in the error I tried to access NWBC client via web browser with following URL:

http(s)://<Fully_Qualified_Domain_Name>:8014/sap/bc/nwbc/nwbc_test?sap-client=800

So it looked that everything was running in the browser. I went through all the checks on server side that are required as per online documentation. So I had to make sure that:

1. HTTP(s) service was up and running in my system. I checked that in TA SMICM

2. Service /sap/bc/nwbc  and all its subnodes were active in TA SICF.

3. Fully Qualified Domain Name (FQDN) was established as per profile parameter icm/host_name_full in my system.

4. System security settings: parameter login/accept_sso2_ticket = 1 and login/create_sso2_ticket was equal to 3 but it should be set to 2. So I changed it to 2.

Here’s how same transaction (SE16) looks like in NWBC:

Once I tried to run NWBC I got different screen where I could enter user credentials directly to the screen instead of pop-up. Afterwards I was logged into NWBC:

Finally I want to mention transaction NWBC. This may help you also to identify possible issue with NWBC.

Further information:

900000 - Netweaver Business Client – FAQ

NWBC Online documentation

PS: This blog is cross published on my personal blog site.

Hi all,

I've been looking a lot into HANA pretty much since the launch in 2012. Also i am very interested in how to make SAP a better place for the users. I personally think that NWBC and the use of powerlists is helping the usability in SAP a lot.

I have tried to look into how the HANA fits into the powerlist framework, and for now i have only seen that the powerlists can be cached in odata services. But this does doesn't really help us, who wants to use NWBC as the usual frontend.

SAP have posted blogs about how easy it is to create an ALV list based on a HANA view, and that is very cool. (If you are interested look here: How to use the SAP List Viewer (ALV) with Integrated Data Access on SAP HANA - YouTube )

However my blog today will be about how to expose a HANA view into the powerlist framework.

So first of all this is created on a suite on HANA system, so I don't need to access any other databases. I have an attribute view created in my HANA modeler which simply joins KNA1 and T005T. From this view I output the customer, name, city, postalcode, countrycode and country name.

From HANA studio ABAP perspective we can publish this view as a data dictionary view to be consumed in ABAP.

The view is an external view

Now this view is available in SAP ECC. So I can go to SE11 and view the data in it.

However the descriptions isn't copied to the table view. We will solve this problem for our powerlist by creating a structure with the same data

We are now ready to create our feeder class for the powerlist. Go to SE24 and create a class. Add the CL_02C_POWL_ABSTRACT_CLASS as a superclass

Now there are four methods we are going to reimplement in this tutorial, its the:

• get_object_definition - This method is used to define the container (e.g. specify field types) where the selected data gets stored.
  get_field_catalog - Specifies the columns to be visible in our powerlist
• get_sel_criteria - Initializes the selection criteria
• get_objects - Fetches the data to be shown in our powerlist

But first we will specify some attributes in our private section.

Here i am reusing my structure created before, this is much easier than declaring all the variables once again.

privatesection.

 

 

types: beginof gy_result.

  includetype ZSAT_KNA1_POWL.

  TYPESendof gy_result.

types: BEGINOF ty_ls_seltab.

typessign    TYPE char1.

types option  TYPE char2.

types low    TYPE char4.

types high    TYPE char4.

typesENDOF ty_ls_seltab .

  types:

    ty_lt_seltab TYPESTANDARDTABLEOF ty_ls_seltab .

 

  types: gx_result TYPESTANDARDTABLEOF gy_result WITHNON-UNIQUEDEFAULTKEY.

 

  data: mt_result type gx_result.

 

    data MT_ACTIONS type POWL_ACTDESCR_TTY .

  data MT_SELCRITERIA type POWL_SELCRIT_TTY .

  data MT_FIELDCAT type POWL_FIELDCAT_TTY .

  data MT_CRITERIA_DEFAULT type RSPARAMS_TT .

Afterwards i implement my get_object_definition with the following code

  method IF_POWL_FEEDER~GET_OBJECT_DEFINITION.

 

    e_object_def ?= cl_abap_tabledescr=>describe_by_data( mt_result ).

 

  endmethod.

Then i specify my selection criteria to be used for selecting the fields. In this example i will only specify the customer number

method IF_POWL_FEEDER~GET_SEL_CRITERIA.

 

    DATA: ls_selcrit          TYPE powl_selcrit_sty,

        ls_criteria_default  TYPE rsparams.

 

 

  IF mt_selcriteria ISINITIAL.

* LFA1-LIFNR

    CLEAR ls_selcrit.

    ls_selcrit-selname    = 'KUNNR'.

    ls_selcrit-kind        = 'S'.          " select option

    ls_selcrit-param_type  = 'I'.          " input field

    ls_selcrit-selopt_type = 'I'.  "M & I  " Select-option with interval and multi-selection

    ls_selcrit-quicksearch_crit  = 'X'.

    ls_selcrit-datatype = 'KUNNR'.

    ls_selcrit-ref_table = 'KNA1'.

    ls_selcrit-ref_field = 'KUNNR'.

    ls_selcrit-ddic_shlp = ''.

    ls_selcrit-allow_admin_change = 'X'.

    APPEND ls_selcrit TO mt_selcriteria.

 

    e_selcrit_defs_changed = 'X'.

    e_default_val_changed = 'X'.

    c_selcrit_defs        = mt_selcriteria.

    c_default_values      = mt_criteria_default.

  ELSE.

 

    c_selcrit_defs = mt_selcriteria.

    c_default_values = mt_criteria_default.

    e_selcrit_defs_changed = 'X'.

 

  ENDIF.

 

  CLEAR c_default_values.

 

 

  endmethod.

Now i am ready to create my field catalog, which represents the columns in my list

  method IF_POWL_FEEDER~GET_FIELD_CATALOG.

 

    DATA: ls_fieldcat      TYPE powl_fieldcat_sty,

        ls_dfies          TYPE dfies,

        ls_fcat          TYPE lvc_s_fcat,

        l_seqnr  TYPE int4.

 

  DEFINE add_colpos.

    add1to l_seqnr.

    ls_fieldcat-colpos = l_seqnr.

  END-OF-DEFINITION.

 

 

  IF mt_fieldcat ISINITIAL.

    CLEAR ls_fieldcat.

    ls_fieldcat-colid = 'KUNNR'.

*  ls_fieldcat-text_ref = ''.  "Link-Action Reference

    add_colpos.

    ls_fieldcat-fixed = 'X'.

    ls_fieldcat-display_type = 'TV'.

    ls_fieldcat-col_visible = 'X'.

    ls_fieldcat-technical_col = ''.

    ls_fieldcat-enabled = 'X'.

    ls_fieldcat-allow_filter = 'X'.

    ls_fieldcat-allow_sort = 'X'.

    ls_fieldcat-header = 'Customer number'.

    ls_fieldcat-width = 16.

    INSERT ls_fieldcat INTOTABLE mt_fieldcat.

 

    CLEAR ls_fieldcat.

    ls_fieldcat-colid = 'NAME1'.

*  ls_fieldcat-text_ref = ''.  "Link-Action Reference

    add_colpos.

    ls_fieldcat-fixed = 'X'.

    ls_fieldcat-display_type = 'TV'.

    ls_fieldcat-col_visible = 'X'.

    ls_fieldcat-technical_col = ''.

    ls_fieldcat-enabled = 'X'.

    ls_fieldcat-allow_filter = 'X'.

    ls_fieldcat-allow_sort = 'X'.

    ls_fieldcat-header = 'Name'.

    ls_fieldcat-width = 16.

 

    INSERT ls_fieldcat INTOTABLE mt_fieldcat.

 

  CLEAR ls_fieldcat.

    ls_fieldcat-colid = 'ORT01'.

*  ls_fieldcat-text_ref = ''.  "Link-Action Reference

    add_colpos.

    ls_fieldcat-fixed = 'X'.

    ls_fieldcat-display_type = 'TV'.

    ls_fieldcat-col_visible = 'X'.

    ls_fieldcat-technical_col = ''.

    ls_fieldcat-enabled = 'X'.

    ls_fieldcat-allow_filter = 'X'.

    ls_fieldcat-allow_sort = 'X'.

    ls_fieldcat-header = 'City'.

    ls_fieldcat-width = 16.

 

    INSERT ls_fieldcat INTOTABLE mt_fieldcat.

 

CLEAR ls_fieldcat.

    ls_fieldcat-colid = 'PSTLZ'.

*  ls_fieldcat-text_ref = ''.  "Link-Action Reference

    add_colpos.

    ls_fieldcat-fixed = 'X'.

    ls_fieldcat-display_type = 'TV'.

    ls_fieldcat-col_visible = 'X'.

    ls_fieldcat-technical_col = ''.

    ls_fieldcat-enabled = 'X'.

    ls_fieldcat-allow_filter = 'X'.

    ls_fieldcat-allow_sort = 'X'.

    ls_fieldcat-header = 'Postcode'.

    ls_fieldcat-width = 16.

 

    INSERT ls_fieldcat INTOTABLE mt_fieldcat.

 

CLEAR ls_fieldcat.

    ls_fieldcat-colid = 'LAND1'.

*  ls_fieldcat-text_ref = ''.  "Link-Action Reference

    add_colpos.

    ls_fieldcat-fixed = 'X'.

    ls_fieldcat-display_type = 'TV'.

    ls_fieldcat-col_visible = 'X'.

    ls_fieldcat-technical_col = ''.

    ls_fieldcat-enabled = 'X'.

    ls_fieldcat-allow_filter = 'X'.

    ls_fieldcat-allow_sort = 'X'.

    ls_fieldcat-header = 'Country code'.

    ls_fieldcat-width = 16.

 

    INSERT ls_fieldcat INTOTABLE mt_fieldcat.

 

 

  CLEAR ls_fieldcat.

    ls_fieldcat-colid = 'LANDX'.

*  ls_fieldcat-text_ref = ''.  "Link-Action Reference

    add_colpos.

    ls_fieldcat-fixed = 'X'.

    ls_fieldcat-display_type = 'TV'.

    ls_fieldcat-col_visible = 'X'.

    ls_fieldcat-technical_col = ''.

    ls_fieldcat-enabled = 'X'.

    ls_fieldcat-allow_filter = 'X'.

    ls_fieldcat-allow_sort = 'X'.

    ls_fieldcat-header = 'Counrty'.

    ls_fieldcat-width = 16.

 

    INSERT ls_fieldcat INTOTABLE mt_fieldcat.

 

    e_visible_cols_count = l_seqnr.

    e_default_technical_col = 'X'.

 

    e_fieldcat_changed = 'X'.

    e_visible_rows_count = 10.

    c_fieldcat = mt_fieldcat.

 

  ELSE.

    c_fieldcat = mt_fieldcat.

  ENDIF.

  endmethod.

Then its time for my get objects, which fetches the data from my HANA view

  method IF_POWL_FEEDER~GET_OBJECTS.

 

      DATA: lt_selcrit TYPE rsparams_tt,

        ls_selcrit TYPE rsparams.

 

  DATA: ls_seltab_kunnr TYPE ty_ls_seltab,

        lt_seltab_kunnr TYPE ty_lt_seltab.

 

 

  DATA: lt_result    TYPE gx_result,

        ls_result type gy_result.

 

    FIELD-SYMBOLS: <lf_kunnr>TYPE gy_result.

 

    LOOPAT i_selcrit_values INTO ls_selcrit.

    CASE ls_selcrit-selname.

      WHEN'KUNNR'.

        ls_seltab_kunnr-sign  = ls_selcrit-sign.  "'I'.

        ls_seltab_kunnr-option = ls_selcrit-option."'BT'.

        ls_seltab_kunnr-low  = ls_selcrit-low.

        ls_seltab_kunnr-high  = ls_selcrit-high.

        APPEND ls_seltab_kunnr TO lt_seltab_kunnr.

 

  endcase.

  endloop.

 

 

  select kunnr, name1, ORT01, pstlz, land1, landx intoCORRESPONDINGFIELDSOFTABLE @lt_result from ZAT_KNA1_POWL where kunnr in @lt_seltab_kunnr.

 

    LOOPAT lt_result ASSIGNING<lf_kunnr>.

    MOVE-CORRESPONDING<lf_kunnr>TO ls_result.

    INSERT ls_result INTOTABLE me->mt_result.

  ENDLOOP.

 

  E_RESULTS = me->mt_result.

 

 

  endmethod.

Ok we are done with the coding. Now its time to create our powerlist. Go to transaction POWL_COCKPIT.

On the initial screen press F8 and go to change mode afterwards.

Go to the bottom of the list and input the name of your powerlist application

Afterwards click the maintain type button

Then click new entries

Give your powerlist type a name and then input the feeder class, this is the name of your newly created ABAP class.

Afterwards we are ready to link the powl type to our application. Go back to the application maintanence and click register type

Now click new entries once again and add the name of your powerlist application and powerlist type (NB: Mine are called the same in this example)

Now we are ready to register our query, that will use our powerlist type.

Go back to the application maintenance and click register query

and then maintain query

Now give your query a name and then add the powerlist type you just created

Save and go back to the register POWL query list and then press new entries

Add the powerlist application and the query you have just created (NB: Once again i'm showing my lazy side and have named it the same)

Now everything is done!

We are now ready to test our hard work.

Go to your test client and Make sure that your customizing requests are copied to your test client

Then enter the transaction POWL_COCKPIT once again. Mark the line of your newly created powerlist application and then press launch powl

Now the power of HANA is unleashed in the powerlist framework