Here’s an interested blog having discussing a proper skills and background of common programmers. Do you think it is applicable for ABAP programmer or even for SAP consultants too? LoL
Sunday, March 30, 2008
SAP NetWeaver Business Client (NWBC)
NWBC is a new (first delivered since March 2007 as version 1.0) platform for GUI based on business user approach to SAP applications. NWBC is one of deliverables of project Muse. It does integrates classics SAP’s transactions as so far can be accessible via classic SAP GUI and new web dynpro applications. It runs over HTTP(s) protocol (instead of SAP DIAG protocol which is used by SAP GUI). Main aim is to cross a gap between current SAP GUI (thick client) and web browser (thin client). In principle NWBC is still reach client which is able to run all set of SAP applications: classics transactions and dynpros, BSP pages, BI analytics dashboards, portals pages, iviews, web dynpros and Visual Composer applications.
NWBS does reflect user’s experience (UX) paradigm and SAP design strategy with combining technologies like: User Interface (UI) building blocks (web dynpro and patterns), self services (ESS & MSS), analytics tool (BI), NetWeaver Portal and Collaboration; Duet; SAP Interactive Form by Adobe; blogs, wikis, instant messaging and in future maybe with voice capability (e.g. Text to Speach), UI adoption and personalization, RSS, RFID.
Basically we can access SAP systems based on ABAP Stack of NetWeaver Application Server or (NWBC with ABAP) and JAVA or Enterprise Portal based SAP systems (NWBC with Portal).
How it looks like? Here we go…
To setup access of NWBC to ABAP system (apart of server settings) do following: in menu System -> Preferences; Add new SAP system to be connected via NWBC, specify:
- Name of the system
- Type of system: PORTAL (SAP Enterprise Portal) or ERP (ABAP)
- Protocol: HTTP/HTTPs; Check transaction SMICM -> Goto -> Services in system which is to be connected.
- Host name. Check transaction SMICM ->Goto -> Services.
- Port number. Check transaction SMICM -> Goto -> Services.
- Path specification in the ICF services. Check transaction SICF for node /sap/bc/nwbc/
- System client
- System language
- User name in system
Moreover: are you looking for downloading of NWBC? Check out following post: SAP NetWeaver Business Client - where to download it?
Saturday, March 29, 2008
Auto code completion in new ABAP editor
As I announced in some of my very first blog post SAP GUI 7.0 has a bunch of new functionalities like New ABAP Frontend Editor - auto code completion. Having being annoyed with functionality of new ABAP editor – auto code completion? You trying to enter a few letters starting to be an ABAP statement; tool tip with proper statement shows up but it is not possible to select?
Guess what: You need to configure keyboard short cut to pick up a keyword from tool tip. You can access this Option menu by clicking to icon on very right side of your SAP GUI.
Following popup shows up and you need in Keyboard section of it select Edit.Autocomplete item and customized a keyboard short cut to access this feature. In my case for selecting auto code suggestion I need to use shortcut CTRL + Space.
Wednesday, March 26, 2008
WD4A – WebDynpro for ABAP
Want to start with WD4A? All you need is miniSAP at least NetWeaver 7.0 and lot of time. Go to the TA SE80 choose “web dynpro Component/ Intf.” and search for demo application called: salv_wd_demo_table_cv. Copy it to customer namespace Z* and start to learn it by modifying it.
Here’s output in web browser.
A few words about technology at the beginning: Web Dynpro is a development and runtime environment used to create professional user interfaces for business applications powered by NetWeaver. It provides a declarative meta model for developing Web applications, without writing much programming code. From this abstract definition, Web Dynpro generates code to create a ready-to-run Web application for different runtime platforms and frontend technology. This development environment is enabling to model and develop professional applications based on browser technology, including a standards-based, device-independent complete runtime environment. Web Dynpro bridges the gap between different platforms such as J2EE, ABAP and Microsoft.NET, and between different Internet browsers and mobile platforms.
Tuesday, March 25, 2008
From WAS to AS
During September 2001 SAP started to deliver SAP Web Application Server (WAS) 6.10 (under General Availability), the natural evolution of its proven application server technology. WAS was a new version of SAP R/3 technology foundation called SAP Basis Component (BC) or just simply SAP Basis. WAS introduced open standards technologies like a native web enabling infrastructure, the embracement of the latest technical standards, like HTTP, HTTPS, XML, SMTP and SOAP, was one of the highlights of SAP Web Application Server 6.10. So far no JAVA arrived on scene. After one year (in 2002) a second version of WAS become available. SAP Web Application Server 6.20, one of the key capabilities of the mySAP Technology platform, supports all existing and new releases of mySAP.com (later called only mysap) components, any JAVA 2 Enterprise Edition (J2EE) based application or any third party or custom developed – as well as a new component of SAP NetWeaver initiative: eXchange Infrastructure (XI) and Enterprise Portal (EP) infrastructure. This application server comprised of 2 stacks: ABAP (as a classic one) and new one: JAVA. After one year (in 2003) a third version of WAS arrived on market. SAP Web Application Server 6.30 had major improvements in its JAVA stack like: J2EE 1.3 support, J2EE Cluster Infrastructure, Java Persistence (Open SQL for JAVA, comprising JDBC and SQLJ; Object-relational persistence), JAVA Development Infrastructure (NetWeaver Developer Studio based on Eclipse project was introduced). Them Web Service Framework based on open industry standards. Web Dynpro was very hot new thing in here as well.
Later during years 2004 and afterwards a strong focus on NetWeaver from SAP was observed. As a major release of SAP NetWeaver ’04 on October 1, 2004 SAP Web Application Server 6.40 was introduced as flag ship WAS release. ABAP stack got aligned up with JAVA development features. There are no overall architecture changes since SAP Web AS 6.30 but main features covers web Dynpro, a runtime and development environment for creating easily adaptable Web based user interfaces. It includes extensive enhancements within SAP NetWeaver Developer Studio as well. JAVA lifecycle management is added as well with the Design Time Repository (DTR), a global System Landscape Directory (SLD), automatic Component Build Service (CBS) and Change Management Services (CMS) similar to the ABAP transport system. Based on those changes development in JAVA gets equal to ABAP development as we always being to do so. Also, the SAP
Comparing SAP basis/WAS’s milestones in brief:
- Application Server <6.10
- User access
- SAP GUI
- Web Browser and
- User interface programming
- Dynpro
- Programming language
- ABAP
- Connectivity
- RFC
- Access to 3rd party infrastructure via connectors and gateways
- Web Application Server 6.10
- User access
- SAP GUI
- Web Browser and
- User interface programming
- Dynpro
- BSP (Business Server Pages)
- Programming language
- ABAP
- Connectivity
- RFC
- HTTP(S)
- SMTP
- SOAP/XML
- Web Application Server 6.20
- User access
- SAP GUI
- Web Browser and
- User interface programming
- Dynpro
- BSP (Business Server Pages)
- JSP (JAVA Server Pages)
- Programming language
- ABAP
- JAVA
- Connectivity
- RFC
- HTTP(S)
- SMTP
- SOAP/XML
- Web Application Server 6.30
- User access
- SAP GUI
- Web Browser and
- User interface programming
- Dynpro
- Web Dynpro
- BSP (Business Server Pages)
- JSP (JAVA Server Pages)
- Programming language
- ABAP
- JAVA
- Connectivity
- RFC
- HTTP(S)
- SMTP
- SOAP/XML
- Web Application Server 6.40
- Integrated Internet Transaction Server (ITS) in WAS kernel
- User access
- SAP GUI
- Web Browser and
- Adobe Forms
- User interface programming
- Dynpro
- Web Dynpro
- BSP (Business Server Pages)
- JSP (JAVA Server Pages)
- Programming language
- ABAP core (Shared Objects, Dynamic Assertions & Breakpoints, Dynamic Type Creation)
- ABAP tools (Memory Inspector, New ABAP Debugger, ABAP Unit, ABAP XML)
- JAVA
- Connectivity
- RFC
- HTTP(S)
- SMTP
- SOAP/XML
Since mySAP ERP and its component Enterprise Core Component (ECC) was introduced as successor of SAP
Something about SAPConsole
SAP as a big vendor of software for logistics’ companies was trying to deliver its customer solution how to view/enter data in not very convenient form e.g. in warehouses when logistic guy is struggling to confirm goods recipient document. For such a person it is crucial benefit to access its information system not only from his desk but from any place in warehouse. He needs to work with system while he is processing any goods or managing stocks. For that kind of users SAP provided solution call SAPConsole which translates SAP GUI screens to character based screens which are commonly used portable/smart/palm/handheld/terminals computers where wide of screen is limited. Such a device is communicating with server based on radio frequency (RF) control. SAP started to offer such a solution with the version 3.0H of SAP R/3. RF possibility has origin back in 90’s of last century when SAP became partnering and afterwards bough company called OFEK-tech. At that time this company was focusing on market of warehouse management solutions. With this solution SAP enhanced its initiative of “Mobile Data Entry” (component LE-MOB in online SAP help) functionality within Logistics Execution System (LES) in version 4.6B of SAP R/3. In here transaction specially to be displayed on RF devices was offered.
Mobile Data Entry is supporting various processes in warehouse like following:
- Goods receipts and issues
- Picking
- Putaway
- Interleaving
- Inventory counting
- Loading and unloading
For details see Warehouse Management system (WMS) documentation.
The software behind this solution is SAPConsole. Basically SAPConsole enables displaying of standard frontend SAP GUI component for character-cell environments. Technically speaking SAPConsole is provides for the connection to the R/3 backend and the exchange of information with between backend and client terminal. The exchanged information is usually in the form of descriptions of screen elements and their contents. SAPConsole comprise of the following elements:
- SAPConsole Interface module
- SAPConsole Administration environment
- I/O Engine
SAPConsole is also responsible for managing the interaction between user and screens. However it does lack of ability to perform any actual I/O operations. Then it uses an I/O Engine an additional software component; through which all SAPConsole user-related I/O operations are performed.
During dot com boom in late 90’s SAP re-branded SAPConsole to new name "SAP Web Console (Web SAP Console)". Refer to term “SAP/WEBSAPConsole” on OSS.
SAPConsule server is delivered with every installation of SAP GUI up to 6.40 versions. In newest version of SAP GUI it is not delivered anymore. Due to fact that for many years SAP delivered it with SAP GUI; SAP Console has been unnecessarily installed on numerous clients and not just on a few servers as it should be. Therefore one of new features of SAP GUI 7.10 (NWSAPSetup) is able to customize other applications to be installable with SAP GUI.
Where’s my activation icon?
In BW’s Administration Workbench transaction RSA1 under modeling area in source system section there was a nice icon available indicating that your particular source system is activated.
This feature started to be available as far as I remember at least in BW version 3.10.
Yes I’m speaking correctly “it was available” because since BI 7.0 SP 13 and higher this icon is disappeared from RSA1. I’m wandering what was reason of this icon removal. I’m not able to find any SAP note to explain this :(
Thursday, March 20, 2008
New design of web reporting since BIWEBAPP 7.00 SP14
I was involved recently within upgrade of BI system and in scope of this small project was an upgrade of SAP NetWeaver portal. Upgrade of JAVA Stack of NW was performed to SP14. Since this upgrade I observe and enjoy much more look and feel design of SAP’s BI web reporting. Here’s some screenshots:
Query opening pop-up dialog window:
New feature: popup windows are resizable.
Portal screen is nicely grayed out in order to highlight pop-up window in front:
Some
Wednesday, March 19, 2008
Error when opening BEx Query Analyzer under SAP GUI 7.10
While you are trying to run transaction RRMS in SAP GUI 710 under version BW 7.x you might experience an error message saying:
Microsoft Excel is not installed; install Microsoft Excel ViewerMessage no. RSR_LAUNCH_EXCEL102
Error behaves as well when you try to run BEx Query Designer via Start menu of Windows. Then your whole Excel got stuck. The solution is to upgrade your SAP GUI to the newest version of its Patch Level (PL). Currently there is available PL 6 (gui710_6.exe) for GUI 710. Make sure that you are using BI 7.0 ADDON FOR SAP GUI 7.10 (bi710sp02p_201-10004472.exe) for SAP GUI as well.
Download PLs from OSS or FTP servers. On OSS navigate your self like following: Downloads -> Support Packages and Patches -> Entry by Application Group -> SAP Frontend Components -> SAP GUI FOR WINDOWS -> SAP GUI FOR WINDOWS 7.10 CORE -> Installation -> Win 32.
Tuesday, March 18, 2008
Business Intelligence Java Components aka BI-JAVA
I was recently helping to upgrade SAP BW system comprehended with SAP NetWeaver Enterprise Portal (EP). In case of BI related JAVA components of EP I was not very able to distinguish between them. Over here I summarize such a components.
To be able access and model BW query in EP you need to maintain following BI-JAVA Development Components (DC) installed in portal JAVA Stack:
BI-BASE-S – Base Services
BI-WEBAPP – Web Applications
BI-IBC – Information Broadcasting
BI-REPPLAN - Reporting and Planning
BI-WDALV – WebDynPro ALV
BI-MMR -
BI-UDI - Universal Data Integration
Those DCs are from J2EE technical point of view so called Software Component Archives (SCAs). Sometimes you may encounter a term Bundled resources in SAP BI Technology.
Once you are upgrading them you need to consider some of them that they need to be upgraded on same Support Package level. Check this out in SAP notes database.
BI-Java is used to provide the Java runtime for scenarios such as Enterprise Reporting, Query, and Analysis as well as Business Planning and Analytical Services. It enables variants such as Information Broadcasting and Ad-hoc Query & Analysis. It also enables Web Dynpro-based BI applications and third party data access via Universal Data Integration. BI-Java is a usage type provided by SAP and contains all of the web based BI tools available for BI 7.0.
BI-Java requires AS Java and Enterprise Portal Core (EPC) and EP in the same system. Optionally, it can be combined with other usage types in one system. Usually, scenarios running on usage type BI-Java also require usage types BI and AS ABAP. While installing
There are some changes within BI 7.x in conjunction with JAVA. BI-JAVA components are involved in these changes as well. In version of BI 7.x everything new here like web reporting is executed via BI-JAVA and not via Internet Connection Manager (ICM) of ABAP Stack of BI backend. E.g. embedding of query you have invoked via web reporting functionality is taking place on server where is BI-JAVA installed in place of BI backend system. In case of version 3.x HTML stuff is generated in BW system and is going to be outputted to user’s web browser via ICM. New concept of BI 7.x is more data scalability and virtualization enabled architecture with distributed landscape. BW server as it self is more focused on basics data warehouse functions like data acquisition, ETL as long presentation layer is separated. However possibility of query execution and web templates generation can take place in BW system as well; in case SAP EP system is not available in your landscape. The difference can be observer in the URL of queries generated for the 7.x vs. 3.x systems. A 3.x based query would have a URL that points back to the BI server and the HTTP port configured in TA SICF. In a 7.x query, the URL will point to the URL of the JAVA Application Server that is hosting EP and BI-Java components (e.g. a port in the 50000 range that is used by the EP).
Let me add a few sentences about particular BI-JAVA DCs. BI-BASE-S and BI-WEBAPP incorporates basis services for accessing BW queries from web environment to BW backend. BI-IBC is JAVA part of BI’s Information broadcasting functionality to allow make objects with business intelligence content available to a wide range of users, according different requirements. BI-REPPLAN a part of BW’s reporting and planning (e.g. Planning Modeller) functionality encapsulated in JAVA stack. BI-WDALV is a component responsible for handling of ABAP List Viewer (ALV) in web environment. BI-MMR - BI Metadata Repository Manager regulates read and write access to metadata (InfoCubes, queries, Web templates, workbooks, etc.) and the documentation on this metadata in BI system. The BI Metadata Repository Manager also allows access to online links generated using BEx Information Broadcasting. BI-UDI - Universal Data Integration is resource adapter consists of:
BI SAP Query Connector (BW-BEX-UDI) - adapter based on SAP Query, which is a component of NW Application Server that allows you to create custom reports without any ABAP programming knowledge. The BI SAP Query Connector uses SAP Query to allow applications created with the BI Java SDK to access data from these SAP operational applications. You can also use the BI SAP Query Connector to make these data sources available in BI systems via UD Connect. The SAP Query Connector implements the BI-Java SDK's IBIRelational interface.
BI ODBO Connector (BW-BEX-UDI) - adapter based on Microsoft's OLE DB for OLAP (ODBO), which is the established industry-standard OLAP API for the Windows platform. The BI ODBO Connector may be deployed into NW Application Server, and allows you to connect applications built with the BI-Java SDK to ODBO-compliant OLAP data sources such as Microsoft Analysis Services, SAS, and Microsoft PivotTable Services. You can also use the BI ODBO Connector to make these data sources available in BI systems via UD Connect. The ODBO Connector implements the BI Java SDK's IBI OLAP interface.
As of SAP NW 2004s, BI-UDI and BI-MMR are integral parts of NW Application Server. You can use the functions that these two formerly separate components provide after you have completed the necessary follow-up activities and configuration tasks.
For further information refer to SAP note:
Wednesday, March 12, 2008
When your SAP GUI will die?
With an increasing amount of different SAP products and its much more different versions there is a high demand for stable and all products and version accessible SAP GUI. As you are in charge of you global release and maintenance strategy of SAP GUI you might be interesting when and for which version of SAP GUI support will be over. As a first source of this kind of information is PAM (Product Availability Matrix) followed by SAPGUI section of SAP support portal (OSS). Good tip would be to search for “Updated Support Matrix SAP GUI for Windows” on OSS. In case you want to be sure about exactly your version of SAP GUI try to search for particular SAP note. As very useful SAP note I found is 147519 - Maintenance strategy / deadlines 'SAP GUI'. Just short update is saying that version 7.10 of SAP GUI will be supported till at least to end of 2011. Most used and widespread version of SAP GUI is 6.40. This version will be supported by SAP AG till 14th of October, this year. A reason is that on this date the used development environment of GUI: Microsoft Visual Studio 2003 will not be supported by Microsoft anymore.
Make your SAP GUI speak - JAWS screen reader for SAP GUI
To enable more users’ accessibility there is an option how to make SAP GUI be speaking. All you need is installation of Freedom Scientifics’ JAWS software. This must be installed first as a prerequisite of SAP GUI’s screen reader extension add-on called JawsScript. To make your SAP GUI speaking you need to activate this extension, enable SAP GUI scripting on the application server.
For detailed information about add-on installation see note 740785 - Accessibility: SAP GUI for Windows and JAWS integration; 480149 - New profile parameter for user scripting at the front end.
Tuesday, March 4, 2008
Scratched filter pane of BW report
After applying of Support Package (SP) 16 to BW 7.0 for ABAP stack and subsequent JAVA stack SP you most likely will experience strange behavior of JAVA stack while browsing your BW reports. Area of filter pane in web reporting becomes tine and narrow.
Filter area serves for filtering of characteristics for specifics values with the query. The filter pane is displayed between the application toolbar and the table (or graphic). The characteristics that you can use for filtering are displayed in the filter area. You can select the characteristic values to be used for filtering for each characteristic that is used in the data provider. It is quite important for user to have this area big enough to seek up characteristics and filter them out. If you want to make this area you need to implement following SAP notes:
1141110 Filter pane item: "Cannot find advanced control with uid..."
1089420 SPS 12/13: Filter pane item: Dropdown does not appear
1048994 Filter pane item: No dropdowns when tray is collapsed
1037254 Filter pane item: Characteristics are unsorted
1054907 WAD: Error messages for characteristic in filter element
956794 Filter Pane: Error in execution
1062330 Filter pane expanded over other elements
1138296 BEx Web Analyzer: Filter pane has a fixed height
1089420 SPS 12/13: Filter pane item: Dropdown does not appear
1037254 Filter pane item: Characteristics are unsorted
1048994 Filter pane item: No dropdowns when tray is collapsed
- update 09/04/2008 -
When you do upgrade BI 7.0 system to SP 14 you encounter this error as well. In this case implement note no. 1138296 - see above.
SP vs. SAP note
In case user finds an error or bug with an SAP application a message is raised on SAP Support portal (so called Online Support System –
A collection of such a SAP notes (typical volume of notes is couple of hundreds) is called “Support Package or Support Pack (SP)”. Support Packages are compiled periodically and are SAP application or component specifics and are available in the SAP Support portal. SP can be implement able via transactions SPAM (Support PAckage Manager) or SAINT (SAP Add-On INstallation Tool.). For JAVA stack of WAS a tool called Java Support Package Manager (JSPM) is used for SP deployment.
Monday, March 3, 2008
Difference between ODS and DSO objects
Since SAP BW version 7.x there is a new term introduced for former ODS (Operational Data Store) object. DSO stands for Data Store Object. Some general information about ODS/DSO: In principle from data warehousing point of view such an objects are serving for storing of data from multiple sources to make analyses of data and simplifying reporting. Since data is coming from different sources data needs to be cleansed (e.g. redundancy) and consolidated (e.g. from business point of view). ODS/DSO objects store data in detailed level (atomic). In addition pure “data warehouse theory definition” would be that data to ODS/DSO is captured in “real time” or “near real time” mode and there is bigger portion of data available as opposite to data warehouse’s cubes. ODS/DSO is combining key field (e.g. business document or its item) with data field (e.g. business document status and other properties) as a key figures. There is nothing multidimensional (no dimension neither fact tables) with ODS/DSO as with cubes. Data in ODS/DSO is stored in transparent (flat) database tables. ODS/DSO objects are reportable.1. Standard DSO object – as standard 3.x ODS; 3 tables with different data version (new/active/delta) data.
2. DSO object for direct update - as transactional 3.x ODS; data in a single version.
3. Write optimized DSO - contains only one table of active data; data is loaded using the data transfer process.
In BW 3.x following types of ODS are used:
1. Standard ODS:
i. Inbound ODS object – or Inflow ODS where the data is stored in the same form as it is when delivered from the source system.
ii. Consistent ODS object - Data is stored here in granular form and consolidated.
iii. Application-related ODS object – data is combined according to the business process rules and serves as a basis for operative reporting.
2. Transactional ODS object – data is immediately available here for reporting no data is stored in different versions (active, delta, modified).
In BW 7.x following types of ODS were introduced:
1. Standard DSO object – as standard 3.x ODS; 3 tables with different data version (new/active/delta) data.
2. DSO object for direct update - as transactional 3.x ODS; data in a single version.
3. Write optimized DSO - contains only one table of active data; data is loaded using the data transfer process.
Saturday, March 1, 2008
SAP Business Intelligence Platform Roadmap
Surely; after acquisition of Business Objects (BOBJ) SAP has renewed its BI strategy to reflect newly acquired products to its BI portfolio. Some time has passed and in February; almost a half a year after acquiring company is coming with new BI roadmap. So what BI tool will stay as originally developed by SAP and what will be replaced by „better“ BOBJ products?
According this strategy there are several areas of both companies products integration. In case of reporting basically BEx suite of application will become less and less important in future and will be removed by BOBJ’s Crystal Reports / Crystal Reports Light. Within dash boarding tools SAP’s Web Application Designer will be replaced by BOBJ’s Xcelsius combined with Dashboard Builder. For OLAP Analyses SAP’s Bex Web/Excel Analyzer will be combined with BOBJ’s Voyager and it will become a tool called Pioneer. In area of data quality and master data services; SAP MDM and BOBJ DQ will join in Master Data Management+.
See whole strategy here. For regular updates of BOBJ integration check SDN BOBJ section; keep an eye on SDN BOBJ Forum plus some sites with overall information: sap.com/businessobjects businessobjects.com/solutions/sap
- update 10/25/2008 –
Version of 08/2008
Version as of August 2008 of BI roadmap was published on SDN. Mostly discussing BOBJ components of SAP BI strategy. Evolution of BI is depicted as well: BI Tools => BI Suite => Process-Centric BI. Plus further strategies within SAP BI products portfolio.
- update 02/23/2009 –
Version of 02/2009
- update 09/13/2009 –
As SDN site is being changed quite often most of link provided above is not working.Therefore I decided to put all the road maps available over time in this blog. So see how road map has evolved:
- update 01/15/2010 –
Subscribe to:
Posts (Atom)
