Sunday, 16 April 2017


SAP recommends to update SPAM /SAINT to latest  version  before applying any Support packs or Add-on in SAP system

Please note :For  SPAM and SAINT update, you do not have to follow increment approach like other SAP ABAP components.
For example if your current SPAM/SAINT version is 7.00/0034 ,you can directly update this component to the latest . You do not have to apply version 35,36,37..and son on to reach to target level.

Following screen-cast will show you how to update your SPAM /SAINT .

1.To check the current Support Package manager version ,Log into SAP and execute transaction SPAM.
SAP SPAM Version before update
In the above screen you can see that our Support package manager version is 7.00/0034

2. Now we will go to SAP market place to check the latest  version of SPAM available for our release.Go to > Support Packages and Patches > Browse Our Download Catalog > Additional Components
2.1 Select SAP SPAM/SAINT Update  > Select appropriate version for your system.
In our example we are trying to update SPAM from version 7.00/0034 to latest available. So we will select SPAM/SAINT Update 700.
SAP Market Place download SPAM package
2.2 Now click on "Support Packages" and select the latest version.
SAP Download SPAM SAINT Update 2
Download the selected file and copy it to /usr/sap/trans/EPS/in , you can deploy this file without copying at OS level also,but its recommended to keep it at mentioned directory, so that it can be reused for all the systems that landscape.

The gadget spec URL could not be found

3. Go to transaction SPAM - client 000 (do not use DDIC) and go to Support Package > From Application Server > and press Yes.
4.This will upload the file from /usr/sap/trans/EPS/in and you will get below screen.
5.Now go to menu and select Support Package >import SPAM /Saint Update and press green check mark to start deploying the update.
SAP import SPAM SAINT update
Known Error : If SPAM updates through an error , go out and execute SPAM and execute step 5 again.

6.Once the update is finished , go out and execute SPAM again. Now you can see the new version deployed.
SPAM SAINT version after update

Friday, 31 March 2017

SAP Landscape Transformation SLT

SAP Landscape Transformation (SLT)
In previous article Overview of Data Provisioning in SAP HANA, we explained various data provisioning technique in HANA.
In this article, we will learn more about SLT.

One of the main features of HANA is that, it can provide real time data to the customer at any point of time. This is made possible with the help of SLT (SAP Landscape Transformation) where real time data is loaded to HANA from SAP or Non-SAP source systems.
What is SLT?
SAP Landscape Transformation Replication Server (“SLT”)
•    is for all SAP HANA customers who need real-time or scheduled data replication, sourcing from SAP and NON-SAP sources
•    Uses trigger-based technology to transfer the data from any source to SAP HANA in real-time.
SLT server can be installed on the separate system or on SAP ECC System.

Benefit of SLT system
•    Allows real-time or schedule time data replication.
•    During replicating data in real-time, we can migrate data in SAP HANA Format.
•    SLT handles Cluster and Pool tables.
•    This is fully integrated with SAP HANA Studio.
•    SLT have table setting and transformation capabilities.
•    SLT have monitoring capabilities with SAP HANA Solution Manager.

SLT Architecture overview between SAP System and SAP HANA

SLT Replication Server transforms all metadata table definitions from the ABAP source system to SAP HANA.
For SAP source, the SLT connection has the following features -
•    If your source system is SAP then you can install SLT as separate system or in Source itself.
•    When a table is replicated, SLT Replication server create logging tables in the source system.
•    Read module is created in the SAP Source System.
•    The connection between SLT and SAP Source is established as RFC connection.
•    The connection between SLT and SAP HANA is established as a DB connection.
•    If you install SLT in Source system itself, then we no more need to have an RFC Connection
SLT Server automatically create DB connection for SAP HANA database (when we create a new configuration via transaction LTR). There is no need to create it manually.

The SAP Note (1605140) provides complete information to install SLT system.
In case SLT Replication Server is installed in the Source System the architecture will be as shown below

SLT Architecture overview between Non-SAP System and SAP HANA

•    The above figure shows real time replication of data from non-sap sources to HANA system. When the source is non-sap we have to install SLT as a separate system.
•    The main changes when compared to first scenario where source is SAP System are
o    Connection between Source and SLT is going to be a DB Connection.
o    Read modules will be in SLT instead of Source.

Components of SLT
The main components involved in real-time replication using SLT are
Logging Tables: Logging tables are used to capture the changed/new records from application tables since last successful replication to HANA.
Read Modules: Read modules are used to read the data from application tables for initial loading and convert the cluster type tables into transparent.
Control Module: The control module is used to perform small transformation on the source data. Data from here will be moved to write tables.
Write Modules: The functionality of write table is to write the data to HANA system.

Multi System Support
SLT Replication Server supports both 1:N replication and and N:1 replication.
Multiple source system can be connected to one SAP HANA system.
One source system can be connected to multiple SAP HANA systems. Limited to 1:4 only.

Monday, 27 March 2017

Configure SLD Registration SAP HANA

You can configure an SAP HANA system to connect to the System Landscape Directory (SLD) using the SAP HANA database lifecycle manager (HDBLCM) resident program in the graphical user interface.

SAP HANA Upgrade

The SAP HANA lifecycle manager tools HDBLCM (command line) and HDBLCMGUI were introduced with the SPS 07 release of SAP HANA. They are wrapper tools, which make use of their underlying tools, including hdbinst for system installation, and hdbupd for update.

license keys available for SAP HANA

There are two types of permanent license keys available for SAP HANA: unenforced and enforced.
If an unenforced license key is installed, the operation of SAP HANA is not affected if its memory consumption exceeds the licensed amount of memory.
However, if an enforced license is installed, the system is locked down when the current memory consumption of SAP HANA exceeds the licensed amount of memory plus some tolerance. If this happens, either SAP HANA needs to be restarted, or a new license key that covers the amount of memory in use needs to be installed.