SAP S/4 HANA - Realtime and Simple

SAP R/2 was the first highly stable solution released by SAP. "R" stood for real-time data processing and "2" stood for the two layers: presentation + integrated application & database. This was in late 70's, when companies were running their business applications on mainframes, and R/2 was apt with the existing technology. SAP R/2 marked the first generation of SAP's business solution.

Then came SAP R/3 in the 90's, capitalizing on client-server architecture. "3" signified the three layer architecture (database, application and presentation). The separation of application layer from database layer reduced the load off database and helped improve the overall performance of the solution. This was immensely popular (second) generation of SAP's business solutions. One can attribute the success to Y2K and SAP R/3 fitting the business needs of most organizations looking to dodge Y2K paranoia.

SAP was riding the wave of Y2K-led-success while the dot com bubble of the late-90's slipped past them. They joined the the web technology a bit late with the release of SAP Web AS or NetWeaver (refrigerator). Their third generation business solution-SAP ERP, which was based on Web AS, was released in 2003-04.

SAP has been supporting multiple database vendors. SAP applications and data models were designed keeping the abilities of those popular database vendors in mind. The core SAP application was not optimized for a single database software. This has changed with the 4th generation. The data model is simpler now and is optimized for SAP HANA.

SAP S/4 HANA - Realtime and Simple

SAP's next big thing is SAP S/4HANA.

The main featured of SAP S/4HANA are:

  • Reduced DB footprint – 1/10 because of simplified data model)
  • 3-7 higher throughput
  • Up to 1800x faster analytics
  • 4x less processing steps
  • No locking, no updates, parallelism for throughput
  • Multitenancy
  • Unlimited workload capacity
  • Capable of running all kinds of the systems (ERP, BW, CRM, SCM, PLM) in one system – will be available as phased availability
  • Fiori UI – responsive for any device
  • Capable of processing all type of data: text, social, geographic, graph processing
  • Deployments possible as (public/managed) cloud, on-premise
  • Guided configuration – reinvented implementation guide (IMG)
  • No anyDB approach any more, it only runs on HANA DB

SAP is moving towards a new paradigm as it has always done in the past. A lot of changes this time. For example: tables like MARA that have been around since R/2 days will not continue to exist on S/4HANA. SAP GUI may be phased out, it's all on Fiori. New innovations will not happen around AnyDB (non-SAP databases), it's all on HANA. There won't be separate transactional and analytical systems.

One has to keep up with where SAP is going with S/4HANA. You can find that out from the upcoming openSAP course SAP Business Suite 4 SAP HANA in a Nutshell. The free course starts on March 25th.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more