Today we look at the changes to the XML Content and Actions tool, which lets you automate the creation of portal content. Instead of using the administration interfaces to create iViews, pages, worksets, roles and other portal objects, you can simply upload an XML file with all the information and — poof! — all you content is created.

The tool is good if you are designing content on a test machine, and then you want to create the content on another machine. Also, if you need to create a lot of objects that are similar — several roles with similar structure; you create the XML for one role, and simply duplicate it in the file and upload the file.

In addition, some companies design their content based on some back-end data, or use some tool (such as Excel) to define the content. From Excel, for example, you can then create a small conversion algorithm to export the Excel data to XML, and then upload the XML.

The tool is a lot like the PCD Inspector, in that it provides a type of backdoor for modifying PCD content. And like the PCD Inspector, you must be careful and check your XML, as you can create a lot of content — but also do a lot of other things, perhaps unintentionally, to harm the portal.

A Quick Review

Open the tool by going to System Administration –> Transport –> XML Content and Actions.

The import tool lets you upload a well-formed and valid XML file. After you export the file, the portal parses it and creates the portal objects and performs the actions defined in the XML. A report of the execution is displayed, showing what objects were created, what actions were performed, what sections did not parse correctly, and so forth.

How to Write XML to Create Content

The XML for the XML Content and Actions tool is, essentially, a collection of tags, possibly nested, and each tag defines an object to create, modify or delete. The type of object is specified by the handler name provided in the objectClass attribute.

For example, to create an iView, you specify com.sapportals.portal.iview.

You can also add tags, that specify an action — such as deleting all objects from a folder, running another script, or assigning users to groups. These tags are not nested.

The following is an example file that creates a folder, a workset in the folder, a page in the workset, and an iView in the page:


   
   

What’s New

The main addition in SP15 was the addition of an export tool, that lets you take existing content and create an XML file based on it. You can then take this XML file, modify as needed, and upload the file so that the content — or similar content — is created on the same portal, perhaps in a different area, or on another portal.

With the tool, you do not need to code XML by hand. You can design the skeleton of what you want and export it to XML. You can then modify the attributes, copy the elements to create additional objects, and so forth.

In addition, a large group of handlers were added in SP13, with which you still may not be familiar. The following objects can now be created:

• Translation worklists
• Related items (of iViews)
• System aliases

The following actions can now be performed:

• Run a script from within another script
• Copy and mirror content
• Assign users to groups and roles

Documentation

And, of course, we have a document that explains all the rules for building a valid XML file for the XML Content and Actions tool. It also lists all the objects you can create and all the actions that you can perform.

The documentation is located at How to Automate Content Creation via XML.

You’re a BPX, it’s Monday morning and you’ve arrived at a brand new client. You have a limited engagement of one week. Your mission: to produce documented recommendations for new technology supporting an existing business process requiring some redesign. How do you get the job done?

This scenario is a common occurrence to the Business Process Expert who functions as the ‘hired gun’. It is not uncommon for the BPX to be called into situations which require high- to mid-level analysis and a quick, but comprehensive set of recommendations as output.

To accomplish this task, the BPX must deal with the following factors:

- quickly developing a relationship with the client, to establish trust and credibility
- sorting through the business issues, often with little or no understanding of the client’s business or particular circumstances
- analyzing the technology in place and understanding the future of the landscape (i.e., upgrades, etc.)
- designing (at a high-level) various alternate solutions
- creating thorough recommendations (and the corresponding document).
How does a BPX quickly establish a relationship with a new client?
To establish trust and credibility, it is important for the BPX to become a ‘trusted advisor’ to the client as quickly as possible. Sometimes the client is aware of the BPX’s profile and history; however, regardless of the client’s prior knowledge, it is still imperative that a face-to-face relationship be established to increase the productivity of interaction between the client and BPX.

Clear communication is key between a BPX and any client, but particularly essential in a short-term assignment which results in ultimately influencing business change. Some of the tactics of a BPX for creating a relationship should include:

- listening attentively to the client (often they drop hints about the pains in their culture; sometimes they may actually be explicit)
- active listening: asking questions for clarity
- demonstrating forthrightness: be clear that you do not have a hidden agenda, and that you are working for them
- briefly outlining your own experience in two minutes or less, focusing on other occasions where you were a trusted advisor

Typically, this openness will precipitate a comfortable, receptive relationship which facilitates your getting the information you need to create your conclusions.
How can a BPX sort through business issues when he/she knows nothing of the client’s business?

This can be a tricky situation and often requires reliance on two things: your past experience and intuition. However, that’s sometimes easier said than done.

It is easy to feel like a fish out of water in a foreign environment, however one of the surest ways to gaining an understanding of the client’s business environment and issues is by listening for similarities to your own past experiences. Often situations, although radically different in exterior application, can be very similar in nature at their core.

By actively listening to the client and asking clarifying questions regarding business priorities and areas of greatest pain, a BPX can quickly get a sense of where the most urgent concerns exist. Generally, this will naturally become evidence to formulating recommendations.

It is critical to accumulate information that forms the “bigger picture” which includes the client’s culture, technical environment and political landscape. Having this bigger picture can direct the recommendations to solve very specific issues.
Analyzing the technical environment

While seemingly straightforward, it is often necessary to dig deep into the system landscape only to ensure that nonconforming systems are indeed identified in any formal architecture discussions. No one likes surprises at the end of an assignment where he/she discovers that there was a complete application built for one area of the business outside of the main landscape, which executed the exact requirements of the consulting assignment! Know all the players involved, even if you must unearth clues through your listening.

Also, ensure that a complete technical landscape is provided to you, inclusive of the go-forward plan for technical upgrades. This can impact the timing of implementation of your recommendations or can drive to a phased implementation approach.
Now that I have the information I need, how do I design the solutions?

This step typically involves your own personal style. Generally speaking, the recommended solutions will begin to become apparent throughout your discussions with the client. As the client unfolds their circumstance and explains their issues, the possible solutions often naturally ‘fall out’ of the analysis.

Again, the development of solutions is reliant on your own knowledge and experience, and in cases where some information may not be available, a healthy dose of your own intuition may be required. More often than not, implementation of similar solutions follows a similar path at its most fundamental level. Intuition, then, can be useful in making a best guess on high-level timing of a project or an approach to phasing-in a solution.
And, finally, I have to write the recommendations document: what should I address?

Typically, a comprehensive document should include the following sections:

- Introduction (why is this document being created) - Scoping Summary (when the exercise and occurred and what the general outcome was)
- Detailed Business Process Information of the specific scope reviewed
- Alternative Recommendations (a text description of the recommended solutions)
- Organizational Impact Assessment (how will the organization be affected)
- Interfaces (a brief description of any foreseen technical interfaces into the new solution)
- Security, Authorizations and Roles (how the new solution will impact who does what in the organization, both from a business and a technical point of view)
- Integration Points (what other parts of the business and technical landscape may be affected by the new solution)
- Training Requirements (at a high-level)
- Description of Improvements and Business Benefits (a brief summary)
- Resource Estimates of the main actions to be taken to implement the solution
- Proposed Timing of the Activities
- Issues (any issues within the organization which have been identified and must be addressed as part of the project)
- Key Success Factors (what will it take to make the project successful)
- Project Assumptions (what was assumed to create the recommendations and resource estimates)

Closing thoughts…
The expectation of the client is that the BPX has the knowledge, expertise, ability and confidence to ‘hit the ground running.’ This can be a tall order in politically difficult situations, however by sticking to the basics of analysis and design as discussed above, the BPX has excellent odds of being successful under most circumstances. These tactics have worked for me and for others. Honing one’s skills through repeated exercise is the key for owning the process of quick situation analysis.

 

 

 

Inspired by Eddy De Clercq’s SDN World Map and the German Podcast Pimp My Brain where they introduced me into Google Maps I’ve tried out to combine this with our SAP CRM People Centric User Interface (PC-UI). The result is this little BSP application which uses ABAP Object Persistence Service and Simple Transformations.

During my research about geocoding in a SAP environment I found Geocoding for BW and Geocoding for Business Partners. You find more information about this topic in the SPRO customizing transaction at SAP NetWeaver -> General Settings -> Set Geocoding. Unfortunately I’ve found no documentation how to implement this standard interface and I implemented my own. External Geocoding solutions can be found in the Partner Directory Solution Search. SAP Notes regarding Geocoding can be found in the OSS Application Area BC-SRV-GEO.

There is also an SDN Article “Using Geo Services with Web Dynpro” which uses the standard interface which calls external providers using the IGS.

But now let’s start to build our solution which will result in:

Preparation

Sign up to the Google Maps API

To use Google Maps you have to Sign up for the Google Maps API. You have to provide the web site URL which must exactly match your WebAS URL including the Port. I. e. http://webas.test.com:8000/. After the sign up you get a sample HTML Source which you can save locally and play around using the API Documentation.

Create Database Table for Geocoding Data

I’ve put all development objects together in the Package ZBPGOOGLEMAP:

Here I’ve created also the DB Table ZBPGEOCODE which will contain the Geocode information for a Business Partner (BP). To detect changes on the BP I also save Street, Street No., Postal Code and City in this table.

Create Persistent class for Geocoding Data

A long time ago I’ve read Thomas Jung’s Weblog on “ABAP Persistent Classes: Coding without SQL” but never tried it on my own. But here I’ve done it and created the Class ZCL_BPGEOCODE which is from Class Type “Persistent class”. All the rest is described in detail in the mentioned Blog. Be aware that you have to use the DB Table ZBPGEOCODE.

Transform Google KML to ABAP

I did not attend the ABAP Online Meet-up on Simple Transformations but it inspired me to use this to transform the return of the Geocoding HTTP Request into an ABAP Structure. To test the Transformation I first downloaded the result of this request to my local drive:

http://maps.google.com/maps/geo?q=Neurottstr.+15a,+Walldorf,+DE&output=xml&key=…

Don’t forget to use your key which you’ve got after sign up at Google Maps. The result of the request looks like this:

<?xml version="1.0" encoding="UTF-8" ?> <kml xmlns="http://earth.google.com/kml/2.0"> <Response> <name>Neurottstr. 15a,69190 Walldorf, DE</name> <Status> <code>200</code> <request>geocode</request> </Status> <Placemark><br /> <address>Neurottstraße 15, 69190 Walldorf, Germany</address> <p> <AddressDetails xmlns="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0"> <Country> <CountryNameCode>DE</CountryNameCode> <AdministrativeArea> <AdministrativeAreaName>Baden-Württemberg </AdministrativeAreaName> <SubAdministrativeArea> <SubAdministrativeAreaName>Rhein-Neckar-Kreis </SubAdministrativeAreaName> <Locality> <LocalityName>Walldorf</LocalityName> <Thoroughfare> <ThoroughfareName>Neurottstraße 15</ThoroughfareName> </Thoroughfare> <PostalCode> <PostalCodeNumber>69190</PostalCodeNumber> </PostalCode> </Locality> </SubAdministrativeArea> </AdministrativeArea> </Country> </AddressDetails> <Point> <coordinates>8.643352,49.293884,0</coordinates> </Point> </Placemark> </Response> </kml> The main problem for me was the Namespace used by the Google KML Format. To get access to the components I had to add this line to the “xsl:transform” element:

xmlns:kml=”http://earth.google.com/kml/2.0″ Also be aware that the Values which should be transferred to ABAP Variables, Structures or Tables must be Uppercase. Here is the complete XSLT which I’ve saved as ZGOOGLE_GEOCODE_TO_ABAP:

<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:asx="http://www.sap.com/abapxml" xmlns:kml="http://earth.google.com/kml/2.0" version="1.0"> <xsl:template match="/">   <asx:abap version="1.0"> <asx:values> <GEOCODE> <LON> <xsl:value-of select="substring-before(kml:kml/kml:Response/kml:Placemark/kml:Point/kml:coordinates,',')"/> </LON> <LAT> <xsl:value-of select="substring-before(substring-after(kml:kml/kml:Response/kml:Placemark/kml:Point/kml:coordinates,','),',')"/> </LAT> <ALT> <xsl:value-of select="substring-after(substring-after(kml:kml/kml:Response/kml:Placemark/kml:Point/kml:coordinates,','),',')"/> </ALT> </GEOCODE> </asx:values> </asx:abap>   </xsl:template>   </xsl:transform> When you test the Transformation you should get this result:

<?xml version="1.0" encoding="utf-8" ?> <asx:abap xmlns:asx="http://www.sap.com/abapxml" xmlns:kml="http://earth.google.com/kml/2.0" version="1.0"> <asx:values> <GEOCODE> <LON>12.570170</LON> <LAT>48.057432</LAT> <ALT>0</ALT> </GEOCODE> </asx:values> </asx:abap>

Implement the BSP

Now we can put the elements together and create the BSP Application ZBPMAP with the Page default.htm. Please maintain this Page Attributes:

Here is the layout:

<%@page language="abap" %> <%@extension name="htmlb" prefix="htmlb" %> <htmlb:content design="design2003" > <htmlb:document> <htmlb:documentHead title="Business Partner in Google Map" > <% DATA: onload type string, onunload type string. if mapcenter is not initial. onload = 'load()'. onunload = 'GUnload()'. %> <htmlb:headInclude/> <script src="http://maps.google.com/maps?file=api&v=2&key=..." type="text/javascript"></script> <script type="text/javascript"> //<![CDATA[ function load() { if (GBrowserIsCompatible()) { varmap = new GMap2(document.getElementById("map")); map.addControl(new GSmallMapControl()); map.addControl(new GMapTypeControl()); map.setCenter(new GLatLng(<%= mapcenter%>), 15); var marker = new GMarker(map.getCenter()); map.addOverlay(marker); GEvent.addListener(marker, “click”, function() { marker.openInfoWindowHtml(”<%= address %>“); }); marker.openInfoWindowHtml(”<%= address %>“); } } //]]> </script> <% endif. %> </htmlb:documentHead> <htmlb:documentBody onLoad="<%= onload %>” > <htmlb:form method="GET" > <htmlb:label for = "BP" text = "Business Partner Number" /> <htmlb:inputField id = "BP" value = "<%= BP %>” /> <htmlb:button text = "Search" onClick = "myClickHandler" /> <% if mapcenter is not initial. %></p> <div id="map" style="width: 500px; height: 350px"></div> <p><% endif. %> </htmlb:form> </htmlb:documentBody> </htmlb:document> </htmlb:content> Please note that you have to insert your Key. Finally the Event Handler OnInputProcessing:

* event handler for checking and processing user input and * for defining navigation   DATA: ls_addressdata TYPE bapibus1006_address.   IF NOT bp IS INITIAL. * Get leading zeros for BP Number CALL FUNCTION ‘BAPI_BUPA_GET_NUMBERS’ EXPORTING businesspartner = bp IMPORTING businesspartnerout = bp. * Get BP’s default address CALL FUNCTION ‘BAPI_BUPA_ADDRESS_GETDETAIL’ EXPORTING businesspartner = bp IMPORTING addressdata = ls_addressdata. * Prepare the address to display in marker CONCATENATE ls_addressdata-street ls_addressdata-house_no ‘<br /> ‘ ls_addressdata-postl_cod1 ls_addressdata-city INTO address SEPARATED BY space.   * Check if Geocoding for address already exists DATA: geocode TYPE zbpgeocode.   DATA: connection TYPE REF TO zcl_bpgeocode, agent TYPE REF TO zca_bpgeocode.   DATA: exc TYPE REF TO cx_root, getgeocode TYPE flag, updategeocode TYPE flag.   agent = zca_bpgeocode=>agent.   TRY. * Get Persistence Object by Key connection = agent->get_persistent( i_partner = bp ). * Has the Address been changed? IF ls_addressdata-street = connection->get_street( ) AND ls_addressdata-house_no = connection->get_house_no( ) AND ls_addressdata-postl_cod1 = connection->get_postl_cod1( ) AND ls_addressdata-city = connection->get_city( ). geocode-lon = connection->get_lon( ). geocode-lat = connection->get_lat( ). geocode-alt = connection->get_alt( ). ELSE. * Address was changed and needs to be updated getgeocode = ‘X’. updategeocode = ‘X’. ENDIF. * Object does not exist. So we have to get the geocode CATCH cx_root INTO exc. getgeocode = ‘X’. ENDTRY.   IF getgeocode = ‘X’. * HTTP Client according to * https://weblogs.sdn.sap.com/pub/wlg/1960   DATA: client TYPE REF TO if_http_client, url TYPE string, c_xml TYPE string. * Build URL to call Googe Maps Geocoding url = ‘http://maps.google.com/maps/geo?q=’. IF NOT ls_addressdata-house_no IS INITIAL. CONCATENATE url ls_addressdata-house_no ‘+’ INTO url. ENDIF. CONCATENATE url ls_addressdata-street ‘,’ INTO url. CONCATENATE url ls_addressdata-postl_cod1 ‘,’ ls_addressdata-city ‘,’ ls_addressdata-countryiso ‘&output=xml’ ‘&key=…’ INTO url.   ****Create the HTTP client CALL METHOD cl_http_client=>create_by_url EXPORTING url = url IMPORTING client = client EXCEPTIONS OTHERS = 1.   client->send( ). client->receive( ).   ****Get the response content in Character format c_xml = client->response->get_cdata( ).   ****Transform XML to ABAP Values   CALL TRANSFORMATION zgoogle_geocode_to_abap SOURCE XML c_xml RESULT geocode = geocode.   IF NOT geocode IS INITIAL. MOVE-CORRESPONDING ls_addressdata TO geocode. geocode-partner = bp. geocode-erzet = sy-uzeit. geocode-erdat = sy-datum. IF updategeocode = ‘X’. * Update Persistent Object connection->set_erzet( geocode-erzet ). connection->set_erdat( geocode-erdat ). connection->set_lon( geocode-lon ). connection->set_lat( geocode-lat ). connection->set_alt( geocode-alt ). connection->set_street( geocode-street ). connection->set_house_no( geocode-house_no ). connection->set_postl_cod1( geocode-postl_cod1 ). connection->set_city( geocode-city ). COMMIT WORK. ELSE. * Create Persistent Object TRY. connection = agent->create_persistent( i_partner = geocode-partner i_erdat = geocode-erdat i_erzet = geocode-erzet i_lon = geocode-lon i_lat = geocode-lat i_alt = geocode-alt i_street = geocode-street i_house_no = geocode-house_no i_postl_cod1 = geocode-postl_cod1 i_city = geocode-city ). COMMIT WORK. ENDTRY. ENDIF. ENDIF. ENDIF. ENDIF. * Only fill Mapcenter if geocode is valid IF NOT geocode IS INITIAL. DATA: lat type string, lon type string. * Prepere Latitude for Javascript IF geocode-lat < 0. geocode-lat = geocode-lat * -1. lat = geocode-lat. CONCATENATE '-' lat INTO lat. ELSE. lat = geocode-lat. ENDIF. * Prepere Longitude for Javascript IF geocode-lon < 0. geocode-lon = geocode-lon * -1. lon = geocode-lon. CONCATENATE '-' lon INTO lon. ELSE. lon = geocode-lon. ENDIF. CONCATENATE lat ',' lon INTO mapcenter. ENDIF. Also here insert your own key to the generated URL. The result is this little BSP Application which provides a Map with a marker where our Business Partner is located.:

To combine this BSP with the PC-UI of CRM please have a look at my Blog: “Use CRM PCUI HTML viewer to call a custom URL”.

I’m not sure if this should be an obituary or a eulogy entitled “Ode to SAP NetWeaver Components”? Anyway it got your attention and I should proceed. If you are involved with any SAP NetWeaver projects, this is essential for you to know.

In the late hours of October 28th 2005, the term ‘SAP NetWeaver components’ passed peacefully away into SAP product terminology history and was put to rest from future SAP NetWeaver use at SAP. They were the fortunate victims of the evolution of the single SAP NetWeaver platform. It was a very somber and poignant moment for the SAP NetWeaver teams as this page in SAP NetWeaver terminology closed and they joined other famous past terms like mySAP.com (remember the enjoy release smiley? sob sob!!), SAP R/3, SAP Basis, SAP R/2, etc.
Coincidently the date coincided with the birth of the SAP NetWeaver 2004s release of SAP NetWeaver (i.e. into the Ramp-up program).

Fortunately we opened a new page and SAP NetWeaver has a terminology succession plan! You may have seen a sneak preview of them at the ‘SAP NetWeaver, BW, and Portals’ conference, ASUG conferences, and our SAP TechEds.
‘SAP NetWeaver components’ have been succeeded by the IT-Practice & IT-Scenario concepts. SAP NetWeaver, the platform, will be rolled out based upon these concepts going forward. Therefore we strongly encourage you to become familiar with these new concepts as it will affect everyone who comes in contact with SAP NetWeaver or SAP NetWeaver powered by applications. They are already here!
For system administrators I suggest that you also look at the new “usage type” concept too.
My colleague, Matt Kangas, has a good introductory Blog on these concepts here. (https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2731)
To see how IT Practices and IT Scenarios are implemented in the SAP Service Marketplace SAP NetWeaver home page click here (http://service.sap.com/netweaver)
For the people without access to the SAP Service Marketplace, for the information on the published IT Practices, click here (http://www.sap.com/solutions/netweaver/itpractices/index.epx)
And for information on the published IT Scenarios, click here (http://www.sap.com/solutions/businessmaps/6064CC13D46849EC8491E2308AA43795/index.epx)
Update: SDN is now moving to the IT Practice and IT Scenario view too: https://www.sdn.sap.com/irj/sdn/developerareas/itpractices

So you say, “What exactly went the way of the Dodo?” (kind of like a funeral crasher’s question “who was he? - I’m just here for the food and drinks!”
For those of you who don’t know what a funeral crasher is, it’s a wedding crasher who realized that you don’t have to bring a present to a Wake! A Dodo is a casualty of evolution or unintelligent design (not too politically correct I guess.. oops)

Well, the SAP NetWeaver components themselves evolved from the new dimension product names and were rolled into SAP NetWeaver in 2003. Unfortunately for historians the actual SAP NetWeaver component names also evolved in the short 3 years too – more times than Prince has changed his name! Did someone get paid per name change?
I’ll endeavor to explain the rationale for sending the components to the branding graveyard in the sky later in the post mortem at the end of the blog.
So moving on, here are the terms that will no longer be used going forward for describing SAP NetWeaver;

• SAP NetWeaver Application Server (formerly SAP Web Application Server – SAP Web AS)
• SAP NetWeaver Business Intelligence (formerly SAP Business Information Warehouse - SAP BW)
• SAP NetWeaver Exchange Infrastructure (formerly SAP Exchange Infrastructure - SAP XI)
• SAP NetWeaver Portal (formerly SAP Enterprise Portal – SAP EP)
• SAP NetWeaver Mobile (formerly SAP Mobile Infrastructure – SAP MI)

  The astute readers will notice that SAP NetWeaver MDM escaped the axe, but this is only temporary until it is rolled into the SAP NetWeaver synchronized release and that’s a blog of its own on its roadmap!

Note that while the SAP NetWeaver components are no longer used by SAP for all NEW content delivered as of SAP NetWeaver 2004s, the ghost of SAP NetWeaver components past will still haunt the SAP websites and materials until SAP NetWeaver ’04 leaves maintenance (2013!). Now that’s some haunting!

As with every loss, some of the readers will have mixed feelings about this progress. We have already had some interactive discussions and we encourage feedback via SDN forums and blog discussions too - we will endeavor to follow up and to provide bereavement counseling ;-). Some of you will move on quickly to the new concepts, but some of you will have some difficulty with the loss and change – in particular the more mature SAP NetWeaver customers/partners who used these components before there was SAP NetWeaver (yes those exciting pioneer New Dimension days).
With regard to moving on, you will start to see the components phased out on SAP Service Marketplace, online help, SDN, and other SAP product information repositories – Just remember all new materials will be IT-Practice/IT Scenario based going forward. If you are looking for functionality grouping names to describe SAP NetWeaver, you still have the SAP NetWeaver ‘fridge’ with the ‘key capabilities’ listed. The fridge is not deceased, but it will continue to evolve as more capabilities are added … and there are more coming next year – of course!

The Post-Mortem:

SAP NetWeaver components’ time has simply past, the meaning just gave out and we cannot use them to adequately describe the new integrated capabilities of SAP NetWeaver. The components segregated the technology platform into meaningful point-in-time ‘buckets’ but things have radically changed since their inception. With the new release of SAP NetWeaver (SAP NetWeaver 2004s) these buckets quite frankly do not adequately represent what IT is doing with SAP NetWeaver to deliver business solutions. SAP NetWeaver’s integration really blurs the lines between ‘old components’ and makes most of them irrelevant within the context of the platform. That is, the sum of all of the components into a whole platform means that the underlying technology can be reused and developed upon in any context. Essentially, the whole platform is greater than the sum of the parts (components).

It’s a natural progression that occurs with most technology evolution, innovation and progress. The emphasis here is ‘progression’ as customers can easily utilize and expand using the the new IT Practice/IT Scenario concepts with their existing SAP NetWeaver deployments. No point in throwing the baby out with the bathwater!

I’ll give a quick example:
- In the past the SAP NetWeaver Business Intelligence (aka SAP BW) component represented data warehousing functionality running on the SAP NetWeaver Application Server (aka SAP Web AS) ABAP stack.
- The BI capabilities of SAP NetWeaver 2004s are now built on technologies from other ‘old components’ of SAP NetWeaver and some clever new technology too! In short if we use the previous ‘component’ view, you will now need the SAP NetWeaver Portal running on the SAP NetWeaver Application Server Java stack with some special SAP NetWeaver BI Java capabilities in addition to the old SAP NetWeaver BI component to develop/deploy queries and analytical applications and to manage the Data Warehouse – Phew!. So doing the math…



Does the SAP NetWeaver BI component name still fit if you are using most of the technology of the platform?
We don’t think so… so it’s time for the old terminology to die and a bigger, better concept to take its place.

R.I.P.