BW Modeling Tools (for SAP HANA BW)

Whole SAP development world is moving away of SAP GUI. This trend is obvious. ABAP developers can develop their programs in Eclipse for quite some time already. See details e.g. FAQs - ABAP Development Tools for Eclipse. SAP HANA Studio which supports developing of HANA’s artefacts like Attribute/Analytic/Calculation Views, DB schemas, tables, sequences, procedures, table types etc. is also based in Eclipse. It was obvious that soon or later BW will get also possibility of developing its objects outside native SAP GUI’s RSA1 transaction and/or outside BEx Query Designer tool.

I remember back in 2009 there were rumors that next “big tool of BW” will be based in Eclipse. Logically it should be successor of Visual Composer (VC) which was/is based in Eclipse also. After VC there is another tool SAP BusinessObjects Design Studio also based in Eclipse. Design Studio is tool for creation of analysis applications and dashboards based on BW/HANA/Universe based data sources for browsers and mobile devices.

On other hand purpose of BW Modeling Tools is to support modeling of BW’s InfoProviders such as "CompositeProvider" and "Open ODS View". CompProv and Open ODS Views are newly introduced objects which came with SAP NetWeaver 7.40 SP5. The tool further supports consumption of SAP HANA Views in BW Models.

In order to use the tool you need few plugins to be installed into the SAP HANA Studio:

• ABAP Development Tools – current version 2.48 (as of 12/07.2017)
• BW Modeling Tools – current version 1.13 (as of 12/07.2017), Note: 1944835

Both can be downloaded from service.sap.com/swdc -> search for SAP HANA Studio

Installation guide for Modelling Tools is available on SMP here (S* ID required).

Personally I’m very looking forward to “united” developer IDE where all kin dof SAP objects can be developed. On other hand I think I’ll be nostalgic for all the transaction in SAP GUI like SE80, SE38/37 and so on.

PS: explanation of new terms:

CompProv – in this new type of object it is possible to merge data from classic BW InfoProviders with data from SAP HANA models using Union and Join or just merge BW data. See the details here.

You can only use this new CompositeProvider if you are using a SAP HANA database.

Open ODS Views – You can define BW data models using it for integration of existing BW objects (DataSources) without the need to create InfoObjects. Open ODS View represents BW metadata of BW structures. While not having InfoObjects high level of consistency of the data model is not guaranteed. On other hand you can change the model much more quickly comparing to the model with InfoObjects. Also it has no separate storage of master and transaction data. See the details here.

-      Update 02/05/2016 –

BW Modeling Tools are usually referred by abbreviation BWMT

-      Update 12/07/2017 –

Current version for ABAP and BW tools updated. For details see here for BW Modeling Tools and here for ABAP tools.

Few words on table RSPOR_T_PORTAL – Portals connected to BW

This blog is originally posted on SCN:

Few words on table RSPOR_T_PORTAL – Portals connectedto BW

This table is very important from portal access to BW system point of view. It stores the configuration information about connected portals. There may be several portals connected into one BW system. One of them must be marked as default one. There is information about logical destination of portal, its system name, prefixes of URL/Metadata Repository, etc. Table has other information when it comes to configuration of Report to report interface (RRI), Adobe Document Services (ADS), SAP Export Library, fonts and portal platform.

Customizing of the table is available via IMG path: SAP Reference IMG -> SAP NetWeaver -> SAP Business Information Warehouse -> Reporting-relevant Settings -> BEx Web -> Integration into the SAP Enterprise Portal -> Maintaining Portal-Server Settings for EP 6.0. In newer versions of BW 7.x this customizing entry is disabled and directly ABAP report RSPOR_SETUP shall be used as specified in customizing note “Settings for Integration with SAP EP 6.0” in TA SPRO.

Important Fields:

RFCDEST                    Logical Destination - RFC Destination to connect the portal from BW and vice versa. It is maintained in TA SM59. Format of the field can look like e.g.: __

SYSTEM_NAME         System Name in Portal System Landscape – Value for BW is usually „SAP_BW“

DEFAULT_PORTAL   Indicates Whether Entry Points to Standard Portal. Only one of several connected portals can be default. This is important for RRI functionality. Parameter RSPOR_DEFAULT_PORTAL needs to be added to user master record. See SAP Note 1818322 - RSPOR_T_PORTAL configuration in the context RRI

URL_PREFIX                         URL Prefix for Portal URLs – it is needed for the input help in BEx Information Broadcasting. BEx report uses URL prefix for iViews. Value usually is: http(s)://hostname:

KM_RM_PREFIX                   Prefix for BW Metadata Repository Manager (RM) – so called RM prefix for BW metadata.  It determines path in Knowledge Management (KM) used by BW metadata while accessing repository manager. Usage of the field is used e.g. when broadcasting: links to BEx objects in the portal are generated. Value usually is: /bw_metadata

CM_RM_PREF_META           Prefix for BI CM Repository for Metadata – IF documents for metadata are migrated to the portal KM (to a BI CM repository) the prefix is used. By this prefix BW checks if whether/where the documents were migrated. Value usually is: /bi_documents.

CM_RM_PREF_MAST           Prefix for BI CM Repository for Master Data – Same as above. But prefix is for master data.

CM_RM_PREF_TRAN           Prefix of BI CM Repository InfoProv. Data - Same as above. But prefix is for transactional data – data stored in InfoProviders.

SAP_EXPORT_LIB               Use SAP Export Library (PDF) – If you want to use BI Export Library for exporting of BW report’s output into the different format like PDF. In that case put X as value.

FONT_PATH                          Directory of Fonts – path to fonts if you are using BI Export Library. See field above. Also see SAP Note 1166921 - Default font not used when font path empty

ADS_HTTPS                          Use HTTPS for Adobe Document Services (PDF). In case of issues see SAP Note 1112378 - USE_HTTPS_FOR_ADS=X is not evaluated.

PORTFOLIO_PATH   Directory for "My Portfolio" - in BEx Web, value must include string "" -> see Note 1830507 - Directory of My portfolio field in rspor_t_portal table

DEFAULT_FONT        Standard Font –While using the BI Export Library this specifies default font to be used by the library.

PLATFORM              Runtime Platform – Either your portal is based on NetWeaver or BusinessObjects Enterprise. Values NW for NetWeaver or BOE for the other one.

SAP’s new programming language – RIVER

During last year SAP announced also one new programming language - SAP River. Let’s have a look what it is about. River is harvested partly on SAP acquisition of Coghead and Frictionless Commerce. Coghead contributed by foundation of web based platform to build and host custom online database applications. This mainly became part of "River" OnDemand platform. Frictionless Commerce contributed by its rapid application development platform.

Married by those two and years of development on top of that SAP came up with River. The River is rapid web based development platform based on the SAP HANA. From programming perspective it is programming model that allows end users to create light-weight applications using drag and drop tools. In connection to HANA; it generates all the HANA development artefacts for HANA.

On other hand there is RDL (River Definition Language). It is executable specification language that allows focus on what application does. It stays away from how the application’s requirement is realized on top of HANA.

To sum it up:

River (original or platform River) - cloud based platform for rapidly developing applications with Flex UI design time and default runtime. It offers REST API for exposing server functionality over it own UI can be built.

RDL - Started as a new language which embeds original River, as a design time paradigm. Later RDL changed embraced within HANA to enable HANA based applications.

Useful links:

SAP River Datasheet

River Language Reference

River Developer Guide

FAQ – what is SAP River

RDL

SAP HANA SPS 07 SAP River

sap-river.com – Try it live now!

SAP BI Export Library

An export of BI report’s output into the different format like PDF is very common. Also SAP’s reporting frontend’s tools are offering that. In case of web reporting based on JAVA stack an export functionality of reports is done by this library. For example BEx Broadcaster is creating PDFs documents also by the library. The BI Export Library is an alternative to Adobe Document Services (ADS). However in contrast to ADS you can use the Export Library only within application based on JAVA Stack. Technically the Library is delivered within Business Intelligence Java Components (BI-JAVA) BI-BASE-S and BI-WEBAPP.

To enable using of the Library you need to maintain field SAP_EXPORT_LIB in table RSPOR_T_PORTAL via TA SM30. By default the Library delivers only font for export TrueType font "Arial Unicode J". If you want to use other fonts you need to put them as files into the folder. Then maintain the directory name into the same table in field FONT_PATH. You can maintain also default font by specifying it in field DEFAULT_FONT I the same table.

For more details see:

1112132 - The SAP BI Export Library

SMP Component: BW-BEX-ET-WJR-EXP Export Services and Printing

Adobe Document Services (ADS)

ADS is used within SAP systems to enable form based processing of data. Functionalities of ADS can be called form both stacks of NetWeaver (JAVA and ABAAP) regardless the fact that ADS is running on JAVA stack of NW. Technology is supporting even interactive forms and they can be used even in offline mode. PDF that are generated by ADS can have possibility of annotating, digitally signing and can be embedded as attachments.

ADS is one of web services (AdobeDocumentServices*) build on top of JAVA stack. Refer to JAVA Stack URL: http://:port/wsnavigator to see all your services. The services of ADS are actually doing the job of forms processing. Either form is being created here (e.g. merging it from template and filling up with the data or extracting the data from XML format of the form and sending it back to app. The form can be developed in ABAP stack in TA SMARTFORMS and in JAVA stack in SAP NetWeaver Developer Studio. The application enables form is interactive. E.g. user input can be validated and therefore checked for its correctness.

The form like that with possibility of user interaction we call SAP Interactive Forms or SAP Interactive Forms by Adobe.

For more details see:

SCN community of Interactive Forms by Adobe

SAP Interactive Forms by Adobe - Getting Started

944221 - Troubleshooting if problems occur in forms processing

SMP Component: BC-SRV-FP Forms Processing

SAP for SEPA

This weekend an Super Bowl XLVIII took place in East Rutherford, NJ was an event which dominated in North America. In Europe on other hand over the weekend happened something else which for the people who were involved wasn’t that much fun as Super Bowl. Actually Single Euro Payments Area or SEPA went live in post of EU’s banks. The SEPA is payment integration initiative within European Union aiming to simplify cross border payments and enables cashless euro payments to subjects located anywhere in the European area. This is possible by using a single bank account and a single set of payment instruments. As SAP systems are heavily involved in banking industry there were changes required into those systems.

Changes in SAP software are related to many solutions and components. Here’s I’m briefly introducing some of SAP ECC components which relates to the changes:

CA-BK – Bank

FI-AR-AR-N - Financial Accounting -> Accounts Receivable -> Basic Functions -> Master Data

FI-AP-AP-B - Financial Accounting -> Accounts Payable -> Basic Functions -> Payment Program / Payment transfer (DE, JP, US)

FI-BL-PT-FO - Financial Accounting -> Bank-Related Accounting -> Payment Transactions -> Payment forms

FI-CAX - Financial Accounting -> Non-industry specific contract accounts receivable, payable

FS-CD - Financial Services -> Collections and Disbursements

IS-PS-CA - Industry-Specific Component Public Sector -> Public Sector Contract Accounting

IS-T-CA - Industry-Specific Component Telecommunications -> Contract Accounting

IS-U-CA - Industry-Specific Component Utilities -> Contract Accounts Receivable and Payable

HCM – Human Capital Management

To see all the information on SEPA related to the SAP see following site on SMP and Note:

service.sap.com/sepa

1855795 - SEPA composite SAP Note: Customer Connection

Intermediate Support Packages

With respect to SPS or SP (Support Package Stack) topic which is discussed here someone may heard also about Intermediate Support Packages (iSP). iSP is basically the same - a package of support packages and patches (de facto a collection of SAP Notes)  for a certain quarterly timed release. In case of some components of SAP software iSP were introduced like BW, PI (XI), etc.

What I understand that iSP is? Usually when there is a new particular SP released and there are some follow up SAP Notes related to that. These Notes have to be implemented manually by TA SNOTE. To prevent this intermediate Support Packages were introduced. So all the Notes released after SP release are packed into iSP.

In case or BW intermediate Support Package are dedicated to ABAP Stack and front-end (GUI) Support Packages. There is no iSP for BW JAVA Stack.

However in case of BW iSP were discontinued.  There are no longer delivered as of BW Support Package Stack 14.

Something about Support Packages

SP vs. SAP note

service.sap.com/sp-stacks

SAP Information Steward

This SAP offering originally from its BusinessObjects portfolio aims to provide a single environment to discover, assess, define, monitor, and improve the quality of your enterprise data assets. It is a part of SAP Enterprise Information management (EIM). This sounds really like pure marketing. Well I realized it J Therefore let’s talk about it in plainer and more technical English.

What is this software trying to address is the data quality. Image how difficult is to get Month End Closing (MEC) done for many organization when they have their data spread over x different departments. Every department is using their “practices” to deal with the data. Users sometimes do not know what definition of the data is, they do not know ability to analyze data dependencies, and they lack visibility where the data is coming from. At the event of MEC there is a lot of rush to consolidate eh data into form that is needed to be. So this is where EIM is coming to: it has components to handle Information Governance, Master Data Management, Content Management, Event Processing and Data Service. Following the Information Steward solution it has in particular these components:

Components and capabilities:

SAP BusinessObjects Data Insight – Data profiling

SAP BusinessObjects Metadata Management – Metadata Analysis

SAP BusinessObjects Data Services – e.g. Data Cleaning within Cleansing Package Builder (CPB)

SAP BusinessObjects Data Quality Management – Data Quality (DQ) Monitoring

As Information Steward was originally BusinessObjects products there are /were following versions available:

Versions:

SAP Information Steward 4.0

SAP Information Steward 4.1

SAP Information Steward 4.2 (includes Data Cleansing Advisor feature)

Useful links:

sap.com/eim – EIM homepage

SAP Information Steward – homepage

Information Steward - SCN community

SAP BusinessObjects Information Steward – presentation from 2011

EIM-IS - SMP component

Dealing with 3.x specific DataSources in BW 7.x

3.x DataSources (R3TR ISFS) became obsolete with introduction of BW 7.0 (R3TR RSDS). New versions of BW are still supporting it. By support it is meant that BW 7.x run such a DSs emulated 3.x DataSources. However for some reasons you may need to migrate the 3.x DS to 7.x fashion. This is possible in TA RSDS->menu DataSource-> Migrate 3.x DataSource -> DataSource.

Also if you for some reason need to the change the originally 3.x DS which was migrated to 7.x back to 3.x state. This is supported by TA RSDS as well. See in menu DataSource-> Restore 3.x DataSource.

One thing that you need to be aware is that it is not possible to change/edit a 3.x DataSource directly in TA RSDS only to display it. To change the DS is only possible once transfer rule is generated fot the DS. This can be either done manually in TA RSA1 or generated in TA DSDS. In RSDS what you need to do is just to witch to Edit mode of the DS. You will be prompted to confirm the generation of transfer rule. System generates transfer structure, Persistent Staging Area and all needed corresponding DDIC objects.

For details see SAP Note:

997739 - You cannot edit a 3.x DataSource directly

936644 - 3.x DataSource:No active version displayed in UI (emulation)

Other DS related blog posts:

What is TA to maintain fields of Datasource?

Operational Data Provisioning (ODP)

OpenUI5

Only very short time ago I blogged about SAPUI5 and here’s continuation. SAP wants to be more and more involved in open source software. As a proof on last year’s Teched 2013 they introduced continuation of SAPUI5 in form of open source called as OpenUI5. The basic difference between those two is that OpenUI5 is free version available under the Apache 2.0 Open Source license. On other hand SAPUI5 is for SAP’s customers and partner having SAP licenses. From central functionalities point of view they both are equal.

For all the details see the OpenUI5 announcement blog at SCN.

To see what UI you can get out of OpenUI5 see here.

Useful links for OpenUI5:

sapui5.org – official page

sap.github.io/openui5

@OpenUI5 - twitter

SAP Product Road Map SAP User Interface Technologies

13 reasons why SAP should open-source SAPUI5

This is why I like #openUI5!

Industry analysis view on OpenUI5

Transport option IMPORT ALL for BW objects

Since Solution Manager (SOLMAN) system arrived to SAP scene a huge push to automation of SAP systems administration takes place. This of course involves transport between SAP systems. The transports in particular because especially in BW area transports are really painful. SOLMAN forces to use so call IMPORT ALL transport procedure. What is technically done is as follows. The option IMPORT ALL or sometime called as tp import all is involved within METHOD EXECTION phase of transport (during which the objects are being stored into target’s system repositories). Basically in case there are more transport requests (TR or CTS) present in transport queue they are all taken and imported into target system. But is objects (e.g. IOs) which are influencing other objects (e.g. InfoProvider) are not in same TR but in several TRs it is very likely that some of TR will fail during its after-import processing. This would not be an issue in case of ECC (or R/3) objects. However it is an issue in case of BW objects because of dependencies, metadata and so on. Therefore it is needed to handle after-import phase differently. Objects from all TRs are merged together into the one list and the list is processed just once.

If you want to use this functionality notice that there are 2 versions of this solution depending on your BW release:

Pilot and final version. Within pilot you need to set parameter RSVERS_BI_IMPORT_ALL of RSADMIN table to X. Refer to Notes below for further details.

Also notice that in such a scenario of transport setup all the logs from all the TRs are collected into the log of 1^st TR.

1115759 - Error during import of BI objects with "Import all"

1556801 - Restrictions for IMPORT ALL in relation to BW objects

1385869 - Parallel execution of BI after-import methods

Switch Framework for BW

You may hear about term Switch Framework. It simplifies ABAP based NetWeaver systems by enabling of switching on/off features of the system. Switching on/off approach means objects change their visibility in repository. The purpose is to adapt/activate the industry settings or solution in particular system. The intention is to provide more functionality by enhancing standard functionality with aim to minimize custom development. The Switch Framework controls which enhancement implementations are to be performed. This is controlling:

- Switch on industry solutions and Enterprise Add-Ons delivered by SAP

- Enhance delivered partner and customer systems delivered by partners

See details here on components and architecture of Switch Framework here:

By which transaction I manage Switch Framework?

SFW1                      Create switches

SFW2                      Create business functions

SFW3                      Create business functions sets

SFW5                      Switch on business functions

SFW2 and SFW5       Maintaining information about business functions

SFW_BROWSER        Display and check the status of business functions

When it comes to BW there are also objects which can be managed by Switch Framework. In this case it is about query components. In particular about Business Content (BCT) delivered queries. The framework is called "Switchable Query Components in the Switch Framework".

All query components that are not reusable (e.g. characteristics, attributes, structure elements, conditions, exceptions and cells) are switchable in the Switch Framework. In case query is missing some functionality you can do the switch in TA RSOSCSW.

For more details refer to documentation. 

- Update on 04/08/2017 –

The BW Switch Framework is being further enhanced in recent versions of BW. As per SAP Note 2094114 with the Switch Framework it is possible to influence the BW system behavior either system-wide or user specific. 

Few words on table RSDIOBJ - directory of all InfoObjects

This blog is originally posted on SCN:

Few words on table RSDIOBJ - directory of all InfoObjects

Here's it is just cross-published:

Sometimes we need to find proper IO while we developing BW’s flow’s and associated InfoProviders. It is definitely easy to reuse what’s already pre-delivered (in form of Business Content aka BCT) with BW than to develop custom IOs. To find out if particular IO is already activated from BCT we usually use TA RDS1. If IO is not popping up within this TA we usually activate it.

But there is a different way except to find the IO via RSD1 or RSA1 transactions. Actually repository of all the IOs is stored in table RSDIOBJ. The table acts as directory of all the IOs. So let’s have a look on what is other interesting information within the above mention table.

Main field:

IOBJTP - Type of an InfoObject:

CHA    Characteristic

KYF     Key figure

TIM     Time characteristic

DPA    Data packet characteristic

UNI     Unit of measurement

BCT relevant fields:

CONTREL – BCT Content release e.g. 7.1/01, 1.2/02

CONTTIMESTMP - Time stamp of last modification to the object by SAP (BCT timestamp)

OWNER - Person who created object = always SAP as it is BCT relevant field

BWAPPL - BW Application where the objects bellows to, e.g. BW, APO, etc

ACTIVFL – if X active and revised version do not agree

Time stamp relevant fields:

TSTPNM - Last changed by, in case OBJVER is D it is always SAP, if custom it is name of user who touched the objects for last time

TIMESTMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss) of object last change

Version relevant fields:

OBJVERS – describes Object Version with regards to BCT:

A        Active

M       Revised

N        New

D        Content

H        Historic

T        Transport

OBJSTAT - describes Object Status from object as itself:

ACT    Active, executable

INA     Inactive, not executable

OFF    Switched off

PRO    Productive

Other fields:

PROTECFL – value X if IO is protected, it means that changes to data and metadata are not allowed for the object because it is internal system object, e.g. 0DATE* 0 date related, 0D* - e.g. 0H_ALEAFNOC, 0FACTCOUNT, 0H* - hierarchy related, 0LANGU, 0OBJECTID, 0TXTLG, 0TXTMD, 0TXTSH

PRIVATEFL - IO is Private means used for Temporal Hierarchy Join InfoObjects, IO which are on Hierarchy tab of IO maintenance screen enabled as "Use Temporal Hierarchy Join" That’s the feature that is to be used for this characteristic with time-dependent hierarchies. (e.g. 0D_FC_CUST1, 0D_FC_PERS1, 0D_FC_SEMP1, 0D_NW_CHB1, 0D_NW_CRB1, 0D_NW_EMPL1, 0D_NW_ORGU1)

FIELDNM – name of the IO in structures (not in database table), by structures is meant start/end routine structues of source/result_package, also the name is used in ABAP DDIC structures of InfoProviders where the IO is used (e.g. 0SALES has field name = SALES, ZZ_IPPORT = /BIC/ZZ_IPPORT)

ATRONLYFL - IO is exclusively an attribute (not used in ICs), this settings is available on General tab of IO maintenance screen. If set it can only be used as a display attribute for another IO and not as a navigation attribute. Also particular IO cannot be included in InfoCubes.

BCTCOMP - Obsolete - do not translate. It was used on older version of BW (<7 .x="" 7.x="" and="" anymore.="" as="" assign="" bct="" been="" business="" by="" component.="" components="" dp_db="" e.g.:="" example="" framework="" have="" ims-usa.="" in="" is-oil="" is="" it="" not="" o:p="" of="" packages="" replaced="" switched="" to="" used="" values="" witch="" xsa="">

BDSFL - Characteristic is allowed as attribute of documents, used for Comments functionality. Feature can be switched on via General tab of IO maintenance screen. The check box is called “Characteristics is Document Property”. Here you define if the characteristic is permitted as a property for documents. User can assign a comment for a combination of characteristic values for such an IO.

ORIGIN - Origin of Object, technical flag to control upgrading of BCT. Attributes of the IO can be deleted with the new BCT. IO created using TA EEWB "Easy Enhancement Workbench" are not affected by this. Possible values:

E        Extensibility

          Default

NODIM function in BEx query formula to keep unit associated with KF

Data functions are heavily used with the formulas in BEx queries. You can achieve a lot by proper using of data functions. There is a wide variety of scenarios where they can be used.  In this post I’d like to briefly discuss of how we can use NODIM function within formula where several different units of measure are involved.

Main purpose of NODIM is to strip particular figure from unit of measure which is associated with. It syntax is follows:

NODIM()

Imagine we have a formula in BEx query consists of several key figures each of them having different unit. The formula can be set up in a way that NODIM function would be used to embrace each component of formula/expression. Doing this BEx Query Designer triggers following warning:

Element “formula XYZ” is not correctly defined (check the query definition) (BRAIN-206)

The correct way of how to setup this formula is to have just one NODIM functions for the component of formula which causes strike of different units. By this even system keeps correct unit associated with KF.

CORRECT:

INCORRECT:

Download developer edition and trial version of SAP software

- updated on 18th of Feb 2021 –

SAP ABAP Platform 1909, Developer Edition – installation on WIN OS

 

 - updated on 12th of Nov 2019 –

SAP NetWeaver AS ABAP Developer Edition 7.52 SP04 – my installation blog

 

SAP NetWeaver AS ABAP Developer Edition 7.52 SP01 (not available for download any more) – my installation blog

 

SAP NetWeaver AS ABAP Developer Edition 7.51 SP02 – my installation blog

 

SAP NetWeaver AS ABAP Developer Edition 7.50 SP02

 

SAP NetWeaver App Server 7.03 SP03 Trial, Ready for ABAP in Eclipse (not available for download any more) – my installation blog

 

SAP NetWeaver Application Server ABAP 7.02 SP11 with Gateway SP04 Trial - Ready for SAP Gateway (not available for download any more) – my installation blog

 

Few remarks: most of below download links is not valid anymore. Sap store site at store.sap.com is now defunct. It was moved to another URL (partner.store.sap.com) but it is only available for SAP partners.

 Going forward main download site is located at  developers.sap.com/trials-downloads.html

A long time ago (yes it was Nov of 2007 ~ 7 years!) I posted blog about SAP software available for download. The post still live here:

miniSAP – where to download it?

At that time we called trial version of SAP as miniSAP. Times passed by and now we call it Developer or Developer Edition or Trial version of the same. Also platform where the software is downloadable has changes. SAP - specially SCN team started to migrate the downloads from SCN it self (scn.sap.com/community/downloads) to SAP store: store.sap.com. The downloads are part of Database and Technology department of the store. 

From NetWeaver based on ABAP stack perspective currently there are following three versions available for the developers:

SCN - SAP NetWeaver Application Server ABAP 7.02 SP6 64-bit Developer Edition

SCN - SAP NetWeaver Application Server ABAP 7.02 SP6 32-bit Trial Version

SCN - SAP NetWeaver Application Server ABAP 7.03 64-bit Trial

So all my dear SAP developers rejoyce! Software download is back!