SAP S/4 HANA Simple Logistics- Overview for Consultants New to S4 HANA SLOG/FINANCE with SAP FIORI


This blog is only for New Consultants in S4 HANA Simple Logistics and Simple Finance. I hope experience in S4 already know this information and Concepts. The Videos here given taken from our friends Video Presentation and some from SAP Directly. I am also new S4 HANA Simple Log and when i gone thro’ I found below Videos are more useful. Thanks again to SAP and our Friends. Credit goes to them. I have just aggregated the Videos and frame this blog.


Blog Covers

S4 HANA Simple Logistics- Procurement/ PO Tracking/PO Approval *

S4 HANA Simple Logistics- Warehouse/Inventory Management/ Logistics Document Tracking *

S4 HANA Simple Logistics- MRP/ Production Planning/ PM Notification*

S4 HANA Simple Logistics- Sales- OTC/SO Tracking*

S4 HANA Simple Finance*

SAP FIORI & it’s application in each Module*

SAP HANA/ FIORI Guided Configuration *

SAP Activate *

SAP ECC6.0 to SAP S4 HANA Migration *

SAP S4 HANA on Cloud/ On-premise

SAP S4 HANA Free access Trail for 30 Days


 What is SAP S/4HANA? I hope this Blog answers the Query. SAP S/4HANA is a new product fully built on the most advanced in-memory platform – SAP HANA – and modern design principles with SAP Fiori User Experience (UX). SAP S/4HANA delivers massive simplifications (customer adoption, data model, user experience, decision making, business processes and models) and innovations (Internet of Things, Big Data, business networks, and mobile-first) to help businesses run simple in a digital and networked economy.   We can see  information in SAP FIORI section of the document. Please see below link for good Introduction on S4 HANA by SAP.

“It is quite interesting to Know which components/Process/Tables/New Modifications in SAP S/4 HANA Simple Logistics, because for a logistics consultants to got with the Rapid change in ERP/SCM Environment/Market- he/she must know the recent changes to get adequate knowledge in consulting. I hope this blog will help them and get into S4 SLOG. I have summarized Video presentation from different People and some from SAP itself. Really very nice Videos. We can treat this blog for complete understanding – how to use FIORI and integrated with S4 HANA Simple Logistics.

Beautiful Videos from SAP. Thanks to SAP.

SAP HANA- JAM (it is a social network for a company implementing S4 HANA Simple Log like a Face book.

Thanks for everyone who presented good presentation Videos. When i tried to learn SAP S4 HANA Simple logistics. this videos helped me more and made me to understand the concepts easily and Quickly. Thanks Friends !!!

SAP Jam Features Tour

SAP JAM for Sales & Sales Team

SAP JAM for Marketing

SAP JAM for HR, Learning & Knowledge Management.,

In-memory computing benefits I mean instead of storing the data in hard disk instead it will directly access the RAM which increases the performance and fastness in transaction and reporting.

Multi core processing –meaning that it will process multiple transactions @ the same time. Multiple process can be executed in Parallel.

SAP HANA Called Columnar Database

Third benefit would be SAP HANA can stores the data in rows as well as columns instead of the traditional data based can execute in Rows.

SAP S/4 HANA to function it needs SAP HANA database. It will not run in oracle or SQL as the traditional versions of ERP SAP..ECC.

It is next generation business suite designed to run the transaction simple.

Built on advanced in-memory Platform SAP HANA

Offers personalized user experience with SAP Fiori. Here user experience in the sense. Meaning that when we check with the users on current GUI screen or transactions definitely they will said it is more complex and difficult and this is avoided in Fiori which works on any platform or any device- even in tabs and mobile more simpler which is more easy to operate and navigate b/w transactions.

Deployable in both Cloud or on- Premise – Means SAP HANA when in cloud can reduce the Hardware/networking device cost and we need to pay only subscriptions to use the cloud. It again depends on clients likes/dislikes..

In cloud server management is taken care by Third party and no technical people server team is required and cost will be saved.

Let’s say one client is replacing the data base with SAP HANA but still If they use ECC EHP7 for the application then we cannot say it is a migration. They just utilizing the HANA databased for their operation. If they completely migrate I mean using SAP HANA data based and SAP HANA S/4 for their application then it is a complete processing the advantage is some process which is more complex in current ECC which is overridden in SAP S/4 HANA SLOG.

Best example would be MRP in ECC. It is a general talk system talking more time on execution f planning run for a material in ECC. They simplified and execution time Is quick- how they achieved is by using SAP HANA Database.

Second one is currently we have SAP ECC, BI, APO, SRM, EWM etc. In different different boxes and execution data would take more time – this is avoided in SAP HANA and it brings everything in common SAP HANA Platform and so we don’t have to depend on QRFC connection or RFC/Interfaces..Etc.. New dimensional components such Hybris, Arriba and everything will be in one single platform. This is achieved in 1511 as starting era in SAP S/4 HANA and later SAP moved to next version or gen 1610.

So here MRP is stream lined, Credit management is streamlined and SO creation is simplified, Material ledger or Material valuation is simplified, Inventory valuation is simplified. So transaction processing is simplified and also wherever possible they increased the performance with the current existing ECC transactional system. SAP Jotted down the areas where users or clients or end users reporting issues they tried to avoid these errors and bug as the Market is moving from B2B to B2C and end customer satidifcation is more required for a company or service provide to grow in that terms SAP HANA is a next generation one.

Principle of one– in current ECC we have many functionalities that are redundant. Same process but 2 functionalities. For example credit management. In current system we have AR SD Credit management and also FSCM Credit Management. Unnecessarily we have 2 functionalities for the same process. This is avoided in SAP S/4 HANA because all the components or modules in single platform so we can avoid red tendency… SAP removed AR SD Credit management and use only FSCM Credit management where some additional functionalities available compared to AR SD Credit management.

Key Enables or Features

Due to removal of redundancy in SAP S4 HANA the speed is 10X times the ECC.

7X times throuput. Less throuput means less input and higher output.

1800X times faster analytics and reporting (speed is More Faster in SAP S4 HANA).

4X times less than the process times. Let’s say the PO creation time in ECC is 40 s but in HANA it is 10 S.

One more example is Inventory valuation- we have 2 functionalities one is Inventory valuation and another one is activating the material ledger. So in SAP S/4 HANA Inventory valuation is removed and keeping the functionality activation the Material ledger mandatory.

Built to drive instant, Value across lines of business-

Not particular across the lines of business let us say P2P, OTC or finance.. but it is for common for all the lines of business I mean complete SAP.. in 1511 and now we have 1610 in usage.

For example if you are posting GR in ECC normally we all know affected tables are MSEG and MKPF but we know from our experience that not only 2 there are so many table getting hit when posting Material doc these are called aggregate tables and this and when we process the transaction these tables get locked on processing of data and so we are unable to process second one till end of the first one. But this is avoided in SAP S4 HANA where using power calculation functionality and it is not going for aggregate tables.. so SAP S4 HANA calculation engine is very powerful and aggregate table concept is removed. New table was introduced called MATDOC which will hold all the data stored in aggregate tables… which will calculate and process all the transaction involved. This is applicable for Reporting also – we can depend on only MATDOC for reporting which simplifies all and reduces time of processing.

SAP S4 HANA is using AGILE methodology called SAP Activate methodology which replaces our traditional water fall model- ASAP Methodology.. also major changes in respect to modules are MM SD PP and PS and in WM or CRM or SRM no major changes or it is same as the existing functionality in 1511 and in 1610 SAP included it SRM/CRM/APO..

Related to Master data – no more XD01 or XK01 in SAP S4 HANA. We need to use business partner for Material and customer.

Material master charcter length extended from 18 to 40 all the integrated system utilizes this option- EWM, APO, PLM etc..


Simplified SD pricing – KONV table is replaced by one another table. Also access sequence increased from 99 (ECC) to 999 in HANA.

Unified credit management- as already mentioned we have CM with FSCM.

Smarter solution in case SO fulfillment cockpit.

Output determination is simplified – no complexity in configuration

Here simple changes means table replacement and not covers functional changes.

One more important thing SAP is more curious to completely migrate to SAP S4 HANA by 2025 for those who already having SAP in their premise but for fresh clients no issues all are from SAP S4 HANA scratch.

In case WM SAP S4 HANA will not consider it more and future changes will be on SAP EWM and it supports SAP EWM only.

Choice of Deployment- On premise, Cloud & Hybrid.

ECC in premise, In-house, CRM in Cloud.

Disadvantage in cloud is we are doing subscription and level of changes in the layout or development aspects is somehow stringent as cloud belongs to third party (it will affect other subscribers also)we have some limitation compared to on premise where ownership is ours and we can do the changes as per our requirement.

In S4 HANA SLOG we have guided configuration in case of cloud edition. We cannot override the prescribed guided configuration because it will affect other subscribers in the cloud. (It gives a tour of the best practice for a particular undergoing implementation- it is a SAP Fiori UI apps. Even if the person not known to the enterprise structure in traditional ECC can able to get the guidance and do configuration).

While in on premise you can do required config based on client requirements.

S4 Core


The market pressure is creating an expectation on the part of multinational and multiregional organizations to be able to transact in smaller volumes, just in time. Whether internally within an organization’s own procurement department or through an e-procurement facility, organizations are also demanding end-to-end and self-service capabilities. Procurement service need to keep up with these demands and be able to offer seamless automation and integration with the suppliers but to a level with which the buyer is comfortable.

The benefits mainly include greater efficiency, time and cost-savings through simplification and the elimination of process duplication.

On Premise SAP S4 HANA Simple Logistics

Limitation in Traditional systems

In a traditional system, a lot of the collaboration between suppliers and buyers has been lost or was slowed down due to limited transparency. Customers worked with many manual interfaces and error-prone processes. All of this made it difficult to identify new business opportunities. SAP S/4HANA delivers full transparency of process status per purchase order and invoice line items, real-time updates of business process information, increased process efficiency for buyers and suppliers. Which leads to another considerable improvement with SAP S/4HANA is the reduction in cycle time.

Please Find below some useful links created by SAP and our Friends.. really it is great work and I hope it will be more useful to our friends in SCN. Once again i am giving my hearty thanks for making me to understand SAP S4 HANA SLOG+ FIORI UI application on ERP World. Awesome !!!

SAP GUI Vs FIORI Difference

SAP user Menu in 1610

From Zero to SAP Fiori and one custom app in 30 minutes -by Gregor Wolf

SAP Sales & Distribution- OTC

Order to cash with Fiori by Wim Lagae

S/4 HANA Operations and Inventory Management

Inventory Management

What inventory management aspects need to be considered these days with a promise to my customer?

The challenge of inventory management was ever since to have precisely the amount available for providing customers with the right products in the right time and thus reduce storage costs to an absolute minimum. These targets were, even with classical processes and IT landscapes, possible to achieve in the past.

Classical inventory planning cannot keep up with flexible accommodations, or custom configurations which customers expect these days. Slow update cycles lead to outdated information as new orders fly in constantly high speed. Limited inventory visibility increases error rate and supply shortages which will affect available-to-promise to the customers and can lead to customer churn.

This logistic challenge requires a synchronization of processes in the warehouse as well as in the entire value chain. Employees within a company’s value chain are tasked to do their daily work at high efficiency. Employees in sales, warehouse, production and purchasing therefore need to have the same source of truth to be able to rely on each other.

The old way of design and thinking updates several aggregate tables in parallel to the original document table. Multiple applications make use of the information coming from MM-IM but require different levels of details. This results in high redundancy and software complexity managing the consistency. The Aggregate-tables contain redundant data with a certain risk that inconsistencies might occur.

Classical Database Structure

Up to ECC6 the material management inventory functionality stores the document data in two tables: MKPF and MSEG. The first one is the header table and the second one is the line item table. The link between MKPF and MSEG is established via MBLNR (Document No.) and MJAHR (Fiscal Year).

New Table MATDOC replaces aggregate Tables

Today stock quantities are stored in up to 15 tables. Values and valuated quantities require further tables: 3 out of the 15 stock tables are master data tables with additional fields containing stock quantities. The remaining 11 tables are pure aggregate tables. Additionally, each aggregate table is shadowed by a history table storing the aggregated stock quantities of previous periods (each entry in the standard table is accompanied by an entry in the historical table for the previous period) (see Figure below).

Innovations in SAP S/4HANA Enterprise management – Inventory Management

Real Time Inventory with SAP S/4HANA by SAP

Great User Experience for SAP S/4HANA 1610 with SAP Fiori 2.0 by SAP

 MRP/ PP in S4 HANA Simple Logistics

Materials Requirements Planning MRP – SAP ERP powered by SAP HANA by SAP

SAP Sales and Operations Planning, Powered by SAP HANA by SAP

Create a Fiori-Like App: Sales Order Tracking by SAP

Highlights with SAP S/4HANA

With the 1610 release, SAP S/4HANA supports the new direction in Procurement departments and simplifies the close collaboration with other Line of Businesses. Operational procurement covers all processes and functions required for processing of purchase requisitions and purchase orders. Sourcing and contract management covers all processes and functions for creation and identifying the best source of supply, negotiating and determining prices and managing the contracts. Working closely together is made easy with these functionalities:

Each action of a buyer or supplier refers to an object. Let us take a look at one example, the purchase order or the invoice. In this cases we talk about any outbound or inbound message that represents a kind of sub process of that specific collaboration process. A very basic sub process here, with regards to the collaboration process of “Order Collaboration” is the creation of a PO that is, based on the system settings of the respective SAP S/4HANA Cloud solution, sent to the SAP Ariba supplier account, instead of being printed out. The supplier sees the PO in his PO list and can react accordingly.

The scope or success of the digital collaboration depends on

  1. the available outbound / inbound messages as published and released by SAP and
  2. On the specifically agreed upon collaboration processes b/w supplier and customer.
In our example, the supplier can react on a PO by physically supplying his customer and after having sent the goods, he would just create and electronically send an invoice. DONE!

The broader the collaboration scope, the more procurement and sourcing use cases for more and more material categories can run more efficient and digital.

Overall we can say, that the operational overhead are getting significantly reduced and the business challenges as of today become eliminated.

Procurement with the SAP S/4HANA 1610 release. Overall we can say that the enhancements in procurement with the 1610 release are generating greater efficiency, time and cost-savings through simplification and the elimination of process duplication. 

Raising efficiency with the Procurement Overview Page

Throughout SAP S/4HANA, the purchaser receives support in his daily work with the Procurement Overview Page, which is part of the real-time reporting and monitoring. With this SAP Fiori app it is easy to monitor critical business events, purchasing spend and supplier performance. Users are able to see all relevant information, analytical and transactional, on one screen, and can show all data in real-time as well as can drill-down for further details or perform direct actions. This app provides its user with a set of actionable cards that you can easily rearrange as required.

For instance can the user filter down to one specific supplier and all the charts on the screen will automatically show only the required information. This makes it so much more efficient to work as the user no longer needs to start different transactions and reports separately. Everything is visible on one single page. The purchaser immediately sees his or her most relevant tasks and can navigate to KPI drilldowns, worklists, or specific object pages to get more detailed information if needed.

Operational cards

Examples of operational cards are the monitoring of contracts, so that you see which contracts are about to expire and require your attention, as well as purchase requisitions, showing you where a source of supply is missing. When users go into this card they can get an overview of all purchase requisitions that have not been converted into a purchase order yet and you can see possible sources of supply that can be assigned.

Analytical cards

Examples of analytical cards are the purchasing spend by supplier and material group, and the monitoring of the supplier performance.

In the supplier performance, for example, a company’s suppliers are evaluated to obtain a basis for your business relationship with them and for optimizing your supply base. Based on the feedback you gather through questionnaires, you obtain a scorecard for each supplier evaluated. The scorecard helps you to assess a supplier’s strengths and shortcomings and to initiate measures for improvement. This enables purchasers to easily compare suppliers within a peer group.


You can filter the content of cards by various criteria, such as by suppliers, purchasing categories, material groups, and purchasing groups. This enables you to make informed decisions and take immediate action.

New SAP Fiori Apps for Collaborative Sourcing and Contract Management

There are many other enhancements in the procurement functionality with the 1610 release. Increase supplier relationship and performance by using activity and task management functions, leverage purchasing category in real-time analytics to monitor the key performance indicators (KPIs) along business responsibilities, and visualize planned spend versus actual spend per purchasing category.

Next to that several new SAP Fiori apps have been delivered in the collaborative sourcing and contract management, like Manage Purchasing Info Records, Manage Contracts, Manage Source List, Manage Source of Supply, Manage Request for Quotation and Supplier Quotation.

Let us now take a closer look at the Manage Source of Supply app, which is part of the Source Assignment. The user uses the source assignment solution to identify potential sources of supply based on past purchase orders and existing long-term purchasing agreements. Sourcing enables you to find the most qualified and reliable suppliers, negotiate with them, and create both scheduling agreements and purchase contracts.

One last significant topic is integration. SAP S/4HANA offers a standard integration to the Ariba Business Network for sending request for quotations to create a sourcing request in SAP Ariba Sourcing. The awarded quotes are sent back from SAP Ariba Sourcing via Network to SAP S/4HANA. The integration is built integrated in standard output management – no separate add-on for the integration is required.

SAP FIORI App for Warehouse Management

SAP WM/EWM in S4 HANA Simple Logistics

Today’s warehouses are subjected to pressures from an increased number of smaller orders via a growing number of sales channels. It’s no surprise that our customers in logistics are looking for ways to improve the efficiency of their warehouses, which can number in the hundreds and be distributed all over the globe.

The common challenges customers have with Warehouse Management are:

  • Rapidly increasing numbers of smaller orders coming from a growing number of sales channels
  • The need to improve customer order synchronization and to seamlessly support customer order requests
  • The necessity to create and manage more “mini-warehouse zones” due to much smaller e-commerce orders and the continuing growth of SKUs
The new realities of e-commerce and evolving customer ordering practices will necessitate changes in the way companies organize and operate their warehouses. Inventory accuracy, inventory location, utilization of space and optimization of picking are all factors to consider when addressing the need to improve customer order synchronization and seamlessly support customer order requests.

SAP S/4HANA 1610 SAP offers two Warehouse Management Systems

  • SAP Warehouse Management (WM) application, which was first introduced as a submodule of the Materials Management application within SAP R/3,
  • SAP Extended Warehouse Management (EWM), which was developed as a component of SAP Supply Chain Management and now comes integrated in SAP S/4HANA.
  • As mentioned SAP WM is not given importance and SAP is slowly moving towards SAP EWM and even in they highlighted that they allocated budget to develop new capabilities and enhancements in SAP EWM and keep WM as it is. It means in near future they can ramp-down SAP WM. Possibilities there..
SAP EWM supports warehouse managers with more flexibility in building objects like warehouse structure, picking, put away, handling unit, and more.

SAP EWM for SAP S/4HANA 1610 has additional features in place to enable companies to execute goods issue activities and goods receipt activities in their warehouses, as well as flexibly plan and coordinate these activities.

For instance, the Inbound Processing feature provides all the process steps for the physical acceptance and putaway of goods. This includes multi-step putaway tasks, including unloading, counting and deconsolidation. Inbound processing also optimizes the warehouse capacity and material flow by using putaway strategies that automatically determine suitable storage bins for the new products.

Quality Management allows companies to check whether delivered products or packaging satisfy their quality criteria as part of the inbound process. In this way, companies can improve the quality of the products and better monitor product quality.

The Outbound Processing feature contains all process steps for the physical removal of goods from stock, including packing the goods according to the requirements of customers, prior to the outbound delivery.

Internal Warehouse Movements uses RF transactions to control the internal movements of products in the company’s warehouse efficiently

The features above are only a subset of the basic warehouse management features available as part of the SAP S/4HANA license. Advanced features require an additional product license.

SAP Fiori Apps for EWM available in the SAP Fiori Launchpad

SAP EWM for SAP S/4HANA 1610 leverages the SAP Fiori user experience and with that, many different Fiori apps that can be used for roles such as Warehouse Clerk, Warehouse Operative and Warehouse Shift Supervisor.

One app developed for S/4HANA 1610 and targeted for warehouse clerks is Change Inbound Delivery. With this app, warehouse clerks can change inbound deliveries. When a truck arrives with a delivery, the clerk can compare the delivery in the system to the delivery note and easily change the quantities, create handling units, delete delivery items, and enter or create new batches.

New warehouse management app: Change Inbound Delivery

Another app for warehouse clerks is Run Outbound Processes – Deliveries. This app is optimized for small and medium warehouses using outbound process without waves. In an overview screen, the warehouse clerk has all the relevant information for the deliveries planned for one to several days ahead. The clerk can create the tasks to trigger the picking process. Exceptions can be identified and the clerk can navigate to a second screen in the app to resolve issues that arise.

Leverage SAP’s EWM centrally in SAP S/4HANA 1610

Because customers’ business and IT requirements are diverse, we’re introducing the full scope of the SAP EWM application in the core of the release of SAP S/4HANA 1610. This is not a replacement of the decentralized EWM, but rather an additional option which will provide customers with flexible deployment options to run all kinds of warehouses within a single SAP solution.

Now you may ask… what is the value of the centralized EWM, versus the current decentralized EWM?

First of all, it’s a full-fledged EWM solution, providing a high level of process and inventory transparency, a precise planning of warehouse steps, as well as efficient distribution and storage.

Additionally, integrated in SAP S/4HANA 1610, EWM gets all the advantage of “one system” like the ability to leverage other SAP S/4HANA 1610 innovations without interface. These include, but are not limited to direct usage of master data and the support of the 40-digit material number.

Of course, this architecture will ensure consistency by avoiding redundant objects. And, direct access to central objects in SAP S/4HANA’s core eliminates the need of the core interface for business partner data, material master data and batch master data.

From the point of view of user experience, Extended WM in SAP S/4HANA 1610 will leverage the new Fiori Theme “Belize”, which will foster the adoption of the product.

And finally, it gives an opportunity to simplify the SAP landscape, and deactivate components. This will directly reduce the TCO of the overall business suite landscape.

This centralized version of SAP EWM is a full-fledged EWM system with clear to see business advantages, like the Fiori user experience and ability to leverage other SAP S/4HANA 1610 innovations without interface.

Now, let’s dive deeper into the advantages from a technical point of view. It is about 3 things: one system, reduction of data redundancy, and simplification.

One System

Having SAP Extended Warehouse Management brought into the core of SAP S/4HANA 1610 brings many technical benefits. Many customers are looking for simplification options of their SAP landscape, and this is possible with integrated extended warehouse management. Here are some concrete example of IT benefits.

With EWM in the core of S/4HANA 1610, the core interface (CIF) is no longer needed to transfer business partner data, material master data and batch master data from SAP ERP into SAP EWM. Now, there is a direct read of the business partner in EWM in S/4HANA instead of replication of the data across two systems. This facilitates a reduced DB footprint, reduced TCO (avoid replication & monitoring) and an overall simplified set-up and operations.

Another benefit is that companies can now leverage other enhancements from S/4HANA like the SAP Fiori user experience that has been harmonized with the 1610 version. The FIORI Launchpad is the single point of access for all applications, and all have the same look and feel with the new Belize theme. This UX provides a simple unified user experience across all UI technologies, giving the ability to merge transactions from different applications into one role. For instance, quality management functionalities and needed and available for warehouse managers with this 1610 release.

Another S/4HANA enhancement that EWM can now leverage without interface is the support of 40-digit material numbers, available since SAP S/4HANA 1511.

Reduction of Data Redundancy

For example, in the integrated version of SAP EWM in SAP S/4HANA, there is no longer a need replicate the orders and create a Expected Goods Receipt. The inbound delivery gets information directly from the Purchase/Manufacturing Order.

Reduction of data redundancy in the inbound delivery process in SAP EWM in the core of S/4HANA

Similarly, warehouse request objects can now be skipped. You can process outbound delivery orders without using outbound-delivery requests; process inbound deliveries without having inbound-delivery notifications and process posting changes without using posting-change requests.

Across many areas, the same reduction of data tables can be seen, such as the elimination redundant customizing tables, redundant product valuation data, redundant accounting data and the replacement of project stock mapping table.

In the quality management process, the Quality Inspection Engine can be eliminated. Only one inspection document is maintained in SAP EWM in SAP S/4HANA instead of working with a quality inspection document and a quality management (QM) inspection lot. It is triggered by an inspection rule.


Built-in quality and continuous improvement with SAP S/4HANA

In today’s highly competitive markets, many companies are struggling to secure but also to extend their market share. In order to survive in these highly competitive environments, high quality is crucial as it serves as one of the main differentiators from competitors. But this is not the only challenge manufacturing companies are facing these days. Due to ever increasing customer expectations, delivering superior quality becomes more important every day. Meanwhile, since customers are also expecting highly individualized products, mass production becomes obsolete. Therefore, manufacturing companies need to pursue mass personalization while ensuring consistent quality in every product.

To master these challenges, manufacturers require flexible and fully integrated end-to-end quality management processes spanning from the design phase to the final delivery of the product. SAP S/4HANA 1610 provides this. With this release, quality management becomes integrated to the core of SAP S/4HANA fully supporting all processes in quality engineering and quality improvement. Throughout the application, quality management data and processes have been streamlined and integrated.

The new 1610 release delivers two main enhancements: streamlined and exceptional end user experience together with new functionalities. Correspondingly, quality inspection professionals including technicians, engineers, planners, managers, auditors, and technicians are supported throughout the entire quality process. For each of this job groups, SAP S/4HANA delivers distinct SAP Fiori roles. Equipped with a personalized role-specific Fiori Launchpad, quality professionals receive all important information at one glance and therefore can focus on what is really important. As a consequence, quality professionals can work more efficiently.

Quality Management Result Recording

A major new innovation of the new 1610 release is the SAP Fiori app for recording results of quality inspections. With this new app, quality technicians can record the results of their quality inspection easily and efficiently. Supported by the new user experience for quality management, quality technicians can utilize flexible and state-of-the-art worklists for inspection lots, operations, samples and characteristics. Moreover, the user interfaces for the recording of the quality inspection results are easy-to-use but nevertheless comprehensive. A huge variety of inspection characteristics are supported, such as qualitative, quantitative, single, mean, values, etc.

Further enhancing end-user experience, new SAP Fiori roles have been added with the new SAP S/4HANA release, such as:

  • Quality technician
  • Quality engineer
  • Quality planner
  • Quality manager
  • Quality auditor
  • Calibration technician

Leveraging this new end-user roles, core quality management processes are now supported with new role-specific SAP Fiori Launchpad. SAP Fiori App Record Inspection Results Nevertheless, with SAP S/4HANA 1610 not only new SAP Fiori roles but also new SAP Fiori apps have been shipped.

The new transactional SAP Fiori app for results recording has been designed specifically for quality technicians to make their work easier and more efficient. In order to achieve this, the app provides flexible and state-of-the-art worklists to handle inspection lots, samples and characteristics. Manufacturing- PP/APO SAP APO was always restricted to large companies due to the high costs of ownership and maintenance of the complex landscape. It means that small and midsized companies could not get the benefit of SAP APO functionalities such as finite capacity planning during the planning run or the material requirements planning (MRP) calculation in buckets smaller than days (i.e., executing MRP runs planned down to hours, minutes, and seconds of a specific date). In the new approach done by SAP S/4HANA 1610 with embedded Production Planning and Detailed Scheduling, liveCache is integrated in the SAP HANA database, which means that liveCache is now faster, since it runs in memory on SAP HANA, and maintaining two different databases is obsolete.

In addition, the SAP PP/DS transactions are executed directly in SAP S/4HANA, which means that you no longer need a separate installation to run SAP APO PP/DS transactions. The material master and the work center creation is also synchronous, and a material or a work center that has just been created can be immediately available for planning in SAP PP/DS. Core Interface (CIF): The connection between SAP ECC and APO The data exchange between SAP ECC and SAP APO is done by an interface called CIF, and provides the following central functions: – Determination of source and target systems within complex system environments – Supply of SAP APO with the master and transaction data relevant to planning – Transfer of changes to transaction data – Return of planning results from SAP APO The CIF integration occurs via remote function calls (RFCs) and inbound / outbound queues where data is processed when received or sent.

In SAP ECC, data is frequently stuck on these queues, causing a disruption in the supply chain planning process. With SAP S/4HANA, we introduced with the 1511 release a data model simplification in financials (table ACDOCA) and also in logistics (table MATDOC). This simplification in the logistics area help us to reduce the complexity of the CIF interface as we have now one material master and one resource maintenance and we can create and update the data for source of supply without queues. It also means that you don’t need to maintain an integration model or to transfer the material master and work center through the CIF anymore.

Comprehensive Plan to Produce in ONE System In many customer cases, unconstrained Materials and Resource Planning (MRP) is used alongside constraint-based planning and scheduling, many customers run two systems sequentially. With the embedded PP/DS in SAP S/4HANA 1610 on a single shared platform, therefore having the capability to harmonize a single MRP run.

The MRP now can also plan SAP PP/DS materials together with SAP ERP materials, and there is a single report to convert planned orders, whereas in the past, we had one for the SAP APO materials and another one for the SAP ERP materials. Other major benefits are that “material masters” and “resource maintenance” come from the same source and integration is significantly simplified. Renovated MRP SAP Fiori app New User experience with SAP Fiori apps With the embedded Production Planning and Detailed Scheduling directly in SAP S/4HANA, the benefit is that the users are working with one coherent application with a consistent look at feel, intuitive navigation. In the same way, the users have a simplified navigation across SAP PP/DS and SAP ERP and are working with one SAP Fiori based Planner Launchpad for material flow and capacity.

Three new SAP Fiori app has been added with the 1610 release: – The Production Scheduling Board app – The Monitor Capacity Utilization app – The MRP app, Create Optimal Orders for Shipment   Aggregate tables contain it´s by nature redundant information because stock quantities are the sum of a material movement document, stored in MKPF and MSEG. This makes the entire process memory intense and predisposed for inconsistency conflicts. However, before the in-memory technology, aggregates and indexes were required to map various requirements of the documents.     SAP FIORI New user interface which function same as SAP GUI in ECC. SAP divided FIORI apps in 3 parts Transactional – Creating PO, Post GR, Create SO.

Even configuration will be considered as transactional. Analytical (For Reports)-  List of open PO, Open GR/IR Reports. Fact sheets- Reports on total number of supplier invoices per plant (processed- let us say 10. It will show 10 Invoices which are processed. It is kind of Dash Board whereas a Purchase manager likes to take how many PO raised per day and within that how many are released , how much are material received../week/Month/year. Etc… (It is complete overview in a single screen).

Let us say a client uses ECC and also in another location they have S4 HANA Implemented with the same user Interface FIORI 2 system can communicate- it means FIORI is not only or only meant for S4 HANA.. This is a common interface for whatever system used by client ( for all landscapes)… Some of the clients implemented FIORI for ECC also. it was launched by SAP in 2013. For Z-process- new screen which is not a standard. Fiori can be used for that Z-purpose I mean it is meant not only for Standard one.

SAP launches 1000 more Fiori apps to cater the Z- development process. Here is the sample Fiori screen Here we can see Time sheet integration with all other Apps. Ex- this one is employee related apps. his benefits and if you are a purchase manger and you are log into the system using your ID. You cannot get all this employee related apps. You will get create PO, create PR etc.. I mean based on the role you can get the required apps. So here we can control efficiently based on roles. S4 HANA Screens Our Normal SAP easy access screen is replaced with Fiori Launch pad in S4 HANA- Kind of brand new user experience. Here we can see periodic activities, Master data navigation, Operational/Transactional Processing, General Reporting and Analytics.. Based on the module/user role access we can use the option.

Bringing Digital core does not change the existing Functional Process. So everything is available but some enhancement changes in S4 HANA which is meant for Process Optimization.  In WM no change because SAP leave WM as it is and no changes and they are more concentrating on SAP EWM to get synch with S4 HANA SLOG.

As already discussed instead of Inventory valuation we have Material Ledger Activation called Material valuation in S4 HANA.   Procurement Related– Supplier management, Purchasing Analysis We cannot see the table data directly in FIORI. It can be checked in backend- I mean HANA server. But very quickly SAP is trying to process configuration steps/path from FIORI as we know we cannot map thousands of changes in a single shot. In 1511 we have to do config in SPRO path and SAP will have a plan to move to FIORI.. We have Option to approve or Reject option against each orders without entering Notification. Here the slide shows tracking by date. It will list 10 days for the PO. We can form a group- Let’s say we are running Procure to Pay process – we can form a group based on the transaction steps- PR- PO-GR..Etc…   Also we can customize the Options either in a sequential Manner or based on the need.

We have user menu/SAP menu –using that we can add custom our Fiori Launch pad.     We can Details related to Supplier- Distance of preferred supplier from plant and his score given by purchasing team based on quantity, Quality, on time, Accuracy etc.. If supplier is @ close proximity and material is in more frequent use then we can change it to JIT It is plant manager decision to change the type to JIT. We can check the effect the change of Process in Fiori launch pad. Here Inventory is streamlined. Before change you can see up and downs in Inventory.. Manage solutions when you type in Search- it will list the apps.

  Choosing the below option encircled in Red will display all the apps. Here scree shot shows end to end implementation- we cannot see any apps because we need to map the apps based on the requirement.    It will give the sample company code, Plant which is already configured- Fiori based guided configuration utility apps. Called manage your solutions. We can customize Fiori apps to make required or needed fields in transactions. For example in company code address page we have many fields it is again our decision to add or remove those fields- Fiori apps are full controlled. So no coding like ABAP usage, only field mapping in Fiori for selecting the Fields. So Fiori is simpler. Also it is a duty of Fiori consultant to map the same Z- changes to ECC through Gateway connection.

Mainly person in ABAP can learn as a secondary skill but Fiori not involves coding like ABAP. Fiori consultant will create App. If suppose particular App not available in Fiori then S4 HANA Consultant will inform Fiori consultant to create an APP and after that he will do config. One important thing is guided config with cloud will help the client to use SAP immediately on the day1 of the decision after paying subscription fee and they can use SAP. Time is saved and cost is saved. Whereas on premise will take more time for implementation, cost is more. Normally suitable for small and medium scale industries they can pay subscription and ready to use tailor made solution.

Access 30 Day Free- Trial –

Free Trial Registration

Build your First App

Try for advanced Capabalities

Trials/ Downloads


SAP has Given 80+ Business Process, 60+ Fiori Apps, 50+ HANA Live Reports

***Normally in Cloud based we have changes for every 3 Months but in case On-premise we have changes Annually***. We will see the Topics in next coming Blogs.

SAP S4 HANA Simple Finance Videos. Once again i like to point out. This blog will help Consultants to know about SAP S4 HANA Simple Logistics/ Finance. I hope it will help them to shape their future Career in S4 HANA.

Below Videos for Simple Finance.

For More Reference Please use SAP for S4 HANA.

On Premise