print this page
Latest Post

HANA License FREE with SAP Solution Manager 7.2

All customers with a valid SAP maintenance agreement can use SAP HANA as database for SAP Solution Manager. There is no additional SAP HANA licensing required.

Who should consider this?
This extension of usage rights is especially valuable for customers who are:
– SAP HANA only
– in a transition phase to SAP HANA
– paying maintenance for their SAP Solution Manager database (ex., Oracle, MSSQL)









HANA Memory- How to free up memory by unloading table from memory ?

Under normal circumstances, the SAP HANA database manages the loading and unloading of tables into and from memory independently. Actually, the main aim of SAP HANA database is to keep all relevant data in memory.

But, one can manually load and unload individual tables if necessary. How?....It’s simple, and it can be done from SAP HANA Studio itself.

Select the table by right click and choose the option “Unload …”
And later, manually load the table into memory again, if needed.
Moreover, if somebody fires the query associated to the same unloaded table, SAP HANA will pick & load the same table into memory FULL or PARTIALLY, purely depending upon the executed query.
Again, if one needs to free up memory, he/she can manually trigger the delta merge operation for a column table manually in SAP HANA Studio. The delta merge operation is related to the memory management concept of the column store, i.e, the part of the SAP HANA Database that manages data organized in columns in memory.

So, options are as follows:
“Unload …” – Free up memory by unloading table from memory
“Load …” – Loading the table into memory
“Merge…” – Triggering delta merge operation for a column table

Post By Debajit 

HANA System hangs with high CPU usage - what to do?

Root cause:
Problem caused by the configuration of transparent huge page

What to Check
1. Check Transparent Huge Page whether it is set to [never] by running the command "cat /sys/
kernel/mm/transparent_hugepage/enabled"

Fix
Apply KBA 2031375 - SAP HANA: Transparent HugePages (THP) setting on Linux


Tags: SAP HANA system hangs,

Expensive Statements Trace Activation - HANA

File: global.ini
Property: expensive_statement
Default: Inactive

HANA Studio
You activate and configure the expensive statements trace in the Administration editor on either the Trace Configuration tab or the Performance tab.

Additional Info:
You can configure the expensive statement trace further using the following properties in the expensive_statement section of global.ini configuration file.









Maintenance Planner Screens SAP S/4 HANA

Maintenance Planner Screens SAP S/4 HANA

Ex., Preparing the Stack for ERP 6.0 EHP8 S/4 HANA Finance 1605 using Maintenance Planner




S/4HANA- Why Sourcing and Procurement Will Never Be the Same with SAP S/4HANA?

Imagine for a moment that you are a procurement officer working for a national retail chain. You just learned that your marketing team is gearing up to launch a national promotional campaign for a product line. The promotion is a very big deal for the company, and many executives are relying on it to meet revenue and profit targets.
But wait a minute: It’s Friday, and you have already planned an exciting weekend off. The last thing you want is this promotion overshadowing it. Now, what if you had all the information you need right now that can help you ensure that the promotion is successful without running out of stock or ending up with lots of excess inventory?
Let’s compile a quick list of critical information you might need:
  • Which vendors currently supply the materials that are part of the promotion?
  • When do their contracts expire, and what are their consumption rates?
  • What are the historic performance scores of these suppliers?
  • Are there other suppliers that were used in the past that you could procure form?
  • How long will it take to onboard these alternative suppliers, if needed?
I’m sure you can think of a few more questions but let’s work off of these for the time being. Now, revisit the above list again and mark down how many of these questions you can answer right now at this very moment. How many of them you can answer within the next 24 hours. How many in 48 hours? More important, how many cannot be answered at all?
…How is that weekend looking so far?

SAP S/4HANA: Three Ways to Make Sourcing and Procurement Strategies More Productive

A significant burden falls on procurement leaders who have to deal with an ever-increasing number of materials, suppliers, and contracts. Real-time insights into supplier spend, evaluations, scores, and contracts can have an immediate impact on their company’s bottom line and competitive position. Yet, many procurement executives are left with legacy technologies that hamper their productivity and diminishes their ability to spot gaps in suppliers’ performance and act immediately.
In sourcing and procurement, SAP S/4HANA can help procurement leaders be more productive by enhancing their ability to manage and optimize operational procurement. Let’s have a deeper look at how S/4HANA is different from classic procurement approaches enabled by pre in-memory enterprise resource planning (ERP) applications running on classical databases. (To find out how SAP S/4HANA is different from pre in-memory solutions in the supply chain line of business check out my previous blog here.)

Instant Material Search

With SAP S/4HANA, you can instantly search for a specific term – such as a supplier, material, or rate – by using a Google-like search field. From there, you can drill down and navigate to various object pages, navigating from supplier object pages to materials pages. This level of insight uncovers suppliers that are delivering the same material and provides alternatives that you can onboard with ease, if needed.  In classical ERP system users had to deal with isolated displays of documents and lacked the ability to execute searches across all documents and master data which sapped their productivity and limited their ability to quickly respond to material shortages.

Supplier Evaluation and Spend Management

SAP S/4HANA brings new real-time insights and advanced analytics to procurement officers. A wide array of real time analytical views are now provided through the Fiori User Experience for Supplier Analytics such as On-time delivery,Price Variance and Quantity Variance, Contract Analytics such as Unused ContractsContract Expiry, and Contract Leakage and Spend Analytics such asNon-Managed SpendPurchasing Spend and Of-Contract Spend to name a few. By running on data in real time without extracting the data into a separate data warehouse, you receive alerts from key performance indicators whenever thresholds are affected. In turn, procurement managers can make instant decisions about which suppliers to choose based on up-to-the-minute information.



Proc.png
















Figure 1- Lab preview of SAP S/4HANA Procurement overview page showing filter cards across suppliers, materials, material groups, purchasing category, purchasing, group, plant, company code

Supplier Collaboration

SAP S/4HANA also benefits from native integration with the Ariba Network. In the past, with SAP ERP running on a classical database, a separate add-on was used to integrate into the Ariba Network. Unfortunately, this made the IT system too complex. Now with SAP S/4HANA, integration with the Ariba Network is prebuilt natively into the solution. Order creation, order change, order confirmation, advanced shipping notification, and invoicing can now be sent directly to the Ariba Network from within the software facilitating supplier collaboration.
This allows procurement officers to create orders in SAP S/4HANA and then send them to their suppliers on the Ariba Network for processing. Suppliers can then confirm orders or let their customers know if items are back-ordered. Suppliers can also notify their customers that items have shipped, and send an invoice for payment. Business rules can help enforce process and document compliance. For example, procurement officers can require that a supplier must confirm an order, create a ship notice, or wait for a goods receipt notice before they can send an invoice. Future functionality is planned such as supporting Variable Supplier Response in case suppliers can’t commit to the full order and Advance Shipping Notification in cases where special handling requirements are needed (e.g. special forklift or storage temperature for the delivered items).



Proc 2.PNG
















Figure 2 – example of a purchase order and invoice automation between SAP S/4HANA cloud edition and the SAP Ariba Network (note the SAP HANA Cloud Integration layer is optional).

The Before and After Picture

For a quick side by side explanation of how SAP S/4HANA can transform your sourcing and procurement processes compared to pre in-memory solutions (and free up your weekend), check out the “before and after” infographic below.



SAP_S&P_Final


This story originally appeared on SAP Business Trends.

HANA to Netweaver Gateway - Connectivity Steps

High Level Step-by-Step Procedure 
  1. Install the SAP HANA DBSL kernel files on the SAP NetWeaver Gateway application server
  2. Install the SAP HANA client on the SAP NetWeaver Gateway application server
  3. Maintain DBCON Table in Gateway System
  4. Create Model Class
  5. Configure a service
  6. Implement a BAdI Class for DB determination
  7. Register a Service and test it


SAP ERP 6.0 to SAP S/4HANA in Four Steps

First Published on SAP News

You can migrate to SAP S/4HANA using the standard migration paths. For those already running SAP ERP 6.0, a system conversion is the correct method.
SAP S/4HANA is the next generation of the SAP Business Suite enterprise software from SAP. Based on the SAP HANA in-memory platform, SAP developers have carefully tailored the solution to meet the needs and challenges of the digital economy. Not only can companies optimize existing processes, but they can now also realize new processes to assert their advantage in the digital competition.

By employing SAP S/4HANA as the digital core of their IT architectures, enterprises can firmly focus on digital processes, where business scenarios are effectively implemented and powerfully marketed. As such, SAP S/4HANA is more than just a successor to SAP Business Suite, it represents a completely new product line.

The migration to SAP S/4HANA is therefore not a one-off project such as an upgrade or database migration. Instead, it involves the entire IT system landscape. Enterprises should always plan the transformation in terms of their optimum future SAP target architecture. This makes life much simpler for users: Thanks to the holistic nature of the transformation, it allows often complex and heterogeneous IT system landscapes to be eliminated (unlike a pure migration to SAP HANA), laying the foundations for simpler, more streamlined processes.

Three Paths to the Destination
As with the SAP Business Suite, enterprises can choose from three possible methods for migrating to SAP S/4HANA: greenfield, system conversion, or landscape transformation. In assessing which path is the right path, the target architecture alluded to above is very important (more on this topic later in the first article of our series “SAP S/4HANA: Chart the Route for Digital Transformation”). Companies that are already running SAP ERP 6.0 (enhancement package 0 and higher) can migrate directly to SAP S/4HANA with a system conversion.

S4HANA_MigrationScenarios
Which path is the right path for my company? A decision matrix illustrates the various paths for migrating to SAP S/4HANA.

System Conversion
In technical terms, a system conversion to SAP S/4HANA retains the system ID for Customizing, development, data, authorizations, and interfaces. This is also known as in-place migration. For systems running SAP ERP 6.0 enhancement package 0 and higher, companies can migrate directly to SAP S/4HANA without having to upgrade to a higher enhancement package. This assumes that the system is already a Unicode system. Following the release of SAP NetWeaver 7.5, SAP only supports Unicode systems. If a company’s system is not Unicode, it must be converted to Unicode before the conversion. The actual system conversion to SAP S/4HANA is supported by the SUM-DMO, the Software Update Manager with Database Migration Option. This helps companies upgrade and migrate databases in one step, meaning just one period of downtime.

Readiness Checks Pave the Way for the Migration
To ensure the migration is successful, companies need to adjust their IT systems to meet the framework requirements of SAP S/4HANA during the system conversion. It is best to analyze the required adjustments in four steps. This “readiness check” for SAP S/4HANA should be performed as early as possible to obtain an overview of possible adjustments. These preparatory measures can then be analyzed during live operation where applicable.

Step 1: Maintenance Planner
The Maintenance Planner checks an organization’s business functions, industry solutions, and IT system add-ons. If the check does not produce a valid conversion path (for example, because an add-on has not yet been published), the Maintenance Planner prevents the system conversion because no stack XML file can be generated. In this case, the relevant partner should be contacted to find out when the add-on will be released. For sandbox system conversions, it is possible to create an exception to continue the system conversion without an add-on release.

Step 2: Simplification List
At a functional level, the simplification list provides a detailed description of how SAP S/4HANA will impact the individual transactions and solution functions of the SAP ERP system. If this list shows transactions or functions no longer exist, this does not mean that certain functions will be lost. Instead, these functions will be merged with other elements or reflected in a new solution or architecture.

The individual objects of the simplification list are dependent on the current SAP S/4HANA Feature Package Stack, and can be grouped into the following categories:

Changes to existing functions
Functions no longer supported
Functions that are no longer strategic
At present, numerous objects of the simplification list can already analyzed using pre-checks (see the next step). Other automated processes to determine whether simplification objects are relevant with regard to customer-specific system usage are currently being planned. It is worth noting that not all points are relevant for a system. Instead, the effort required for the conversion should be determined for the relevant points.

Step 3: Pre-Checks
Pre-checks review the system settings that are required to perform the actual system conversion. These are available to customers in the form of SAP Notes, and can therefore also be used in step 2.

Step 4: Review the Customer Codes
One of the most important features of SAP S/4HANA is the simplification of the data model. SAP provides compatibility views for tables that are no longer required in the migration to SAP S/4HANA. SAP also provides a check tool based on SAP NetWeaver 7.5 that checks necessary adjustments, for example adjustments required for field length extensions. The SAP S/4HANA simplifications can be imported in a file, and compared with a code extract of the SAP ERP system. A list is created showing the reviewed customer code and indicating any code that needs to be changed to make it compatible with SAP S/4HANA. There are plans to fully integrate these checks as a check variant of the SAP Code Inspector in future. The tool currently supports checks of the adjustment of the material number lengths.

Migration via SAP S/4HANA Finance
The migration to SAP S/4HANA can also be performed with an interim step for SAP S/4HANA Finance. The logistical processes have not yet been simplified in this step. In technical terms, this is an add-on that is available as an add-on for enhancement package 7 for version 1503, or an add-on for enhancement package 8 for version 1605. Again, the migration is possible in one step, and the system must be a Unicode system. SAP provides customers with an ABAP report to check the requirements for this type of migration. This report must be run in the local SAP ERP system.

Post by  Andreas Schmitz

SAP Fiori vs SMP [SAP Mobile Platform]

Look at the differences between the two, most focused mobility offerings of SAP, namely SMP and SAP Fiori. The table below will guide you, on which of the two approaches to choose from.


SAP HANA Virtualization Platforms Supported

SAP HANA is supported on bare-metal and virtualized platforms.

VMware --> vSphere

IBM  -------> PowerVM

Hitachi ----> LPAR

Huawei----->FusionSphere

RedHat RHEL ---> KVM Hypervisor

SUSE Linux ------> Enterprise Hypervisor












 
Copyright © 2011. SAP HANA TUTORIALS FREE - S/4 HANA - All Rights Reserved