To enable our customers to plan their journey to SAP S/4HANA in detail, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511.” This list provides detailed functional-level descriptions of the required changes to individual transactions and solution capabilities in SAP S/4HANA. It supports customers who are transitioning from SAP ERP 6.x or SAP Simple Finance, on-premise edition, to SAP S/4HANA, on-premise 1511 edition and includes guidance on the activities customers need to complete before, during, and after the conversion to SAP S/4HANA.

In addition to the Simplification List the Maintenance Planner, the conversion Pre-Checks and the Custom Code Migration Worklist are offered to give a tool-based support for the customer.

For more details regarding these tools see the following S/4HANA SCN Blog: http://scn.sap.com/docs/DOC-68976

Based on the experience gained from current projects, we expect that a typical customer system will be affected by on average 30 to 40 of the currently around 300 Simplification Items. Technical pre-checks, which assess the usage and configuration of a customer’s existing SAP Business Suite system, identify the relevant Simplification Items. Customers can run these pre-checks on their existing SAP Business Suite systems during the planning phase prior to the actual conversion to SAP S/4HANA. SAP plans to further improve the process of identifying Simplification Items by providing additional pre-checks and even more advanced tools that will reduce the list per system to a specific subset for that particular system.

The Simplification List, therefore, serves three purposes:

• Planning the actual system conversion from a traditional ERP solution to SAP S/4HANA
• Reducing efforts during the actual conversion by enabling individual Simplification Items to be dealt with in advance for those customers intending to migrate in a future project (if, for example, they are currently tied up in other projects)
• Implementing SAP S/4HANA-compliant strategic capabilities when rolling out new capabilities to avoid rework on SAP S/4HANA (relevant to, for example, customers who still need to finish major rollouts prior to converting to SAP S/4HANA)

With this S/4SCN Blog we want to start a series of blogs providing more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. We are planning to provide for a list if dedicated simplification items per item a dedicated S/4HANA SCN blog with dedicated information. Based on the single S/4HANA SCN blogs feedback can be given and questions can be raised (which we try to answer as fast as possible). See below an initial list of items where we plan to offer such additional S/4HANA SCN blogs with additional information.

We start this approach with the first item – the Business Partner Approach (Customer-Vendor Integration).

Hi All,

I have tried looking for any documentation support on condition contracts but could find only the below one. I could not make much use of it and need some help. Please suggest some steps or documents you have on the process of condition contracts. I understand in S/4 HANA, settlement management with condition contracts have to be used as a replacement for rebate management. I tried setting up the same in the system but am not sure what contract type to be used, etc. I created a contract but do not see the condition type in the billing document. My worry is that I might be missing something without understanding the full picture and hence need help.

Condition Contract-Based Settlement - Compensation Management - SAP Library

Thanks & Regards,

Vidya

Hi All,

I understand the SD Rebate Management is not available in S/4 HANA and Condition Contracts in settlement management has to be used. I have searched for documentation on this but have not got any. The only document available is SAP Help but not much information is available in that too in terms of setting up the config and the process. I tried to do the steps myself but after creating a contract and while settling it, the system says that the schema could not be determined. So, there could be many things which I might be missing.

So, request you all to provide any documentation you have on this functionality or provide any information which can be helpful for me to set it up completely.

Thanks,

Vidya

Dear All,

While creating sales order in s/4 hana, Im getting the below error

Error when calling Credit Management: Technical Error

Message no. UKM_PI008

Can you guys please help me get through it?

Regards

Akber

Release of SAP S/4HANA, on-premise edition 1511

In November 2015 (1511) updates have been released for both, SAP S/4HANA, on-premise and cloud edition. In November 2015, SAP delivered a massive wave of simplification and innovation in the core of SAP S/4HANA. With this delivery, enterprises can drive unprecedented business value with innovative use-cases - in core financial and operational areas such as in logistics – taking full advantage of a simplified data model and a responsive user experience.

Key simplifications and innovations include:

• Optimized working capital with new accounts payables and receivables cockpits
• Decreased stock buffers with simplified data model in inventory management for real-time, high-volume processing
• Increased visibility with real-time stock and material flow insight
• Reduced manufacturing cycle time with streamlined material flow for internal requirements (MRP)
• Augmented reactivity with real-time monitoring of production orders regarding flow and critical issues
• Improved operational decisions with easy simulation of supply alternatives
• Lower procurement costs with standard integration to the Ariba Business Network
• Better customer service with new sales order fulfillment cockpit for instantly identifying bottlenecks and issues

For more information see as well the SCN blog from Sven Denecken: Link

The System Conversion to SAP S/4HANA, on-premise edition 1511

Different transition paths are supported with SAP S/4HANA, on-premise edition 1511:

• New Implementation
  New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
• System Conversion
  Customers who want to change their current system into a SAP S/4HANA system.
• Landscape Transformation
  Customers who want to consolidate their landscape or to selectively transform data into a SAP S/4HANA system.

The SAP S/4HANA, on-premise edition 1511 system conversion supports one-step procedure (Database, SAP NetWeaver and application transition in one step) for SAP ERP 6.0 EHP x…7 systems. System Conversion requires a Unicode (UC) source system. Non-Unicode source systems will require a two-step approach (first move to Unicode then to SAP S/4HANA, on-premise edition 1511).

Basically it can be distinguished between technical and semantic tasks during the system conversion. The technical installation procedure is based on established lifecycle management tools (Maintenance Planner, Software Update Manager [SUM] and Database Migration Option [DMO]). Due to the fact that SAP S/4HANA is a new product line (and not the successor of SAP Business Suite) things are done differently in SAP S/4HANA.

• Many of the changes are technical in nature and have no or only limited impact on peoples work and thus do not trigger business change management. Such changes will be mandatory when converting a system to SAP S/4HANA.
• Other decisions are more of a strategic nature determining which version of functional support will evolve into the digital era and provide the capabilities demanded from the unstoppable business process innovation. Where those strategic directions demand change management through adoption, SAP at large keeps the traditional capabilities available as compatibility scope enabling a rather technical migration of these processes and leaving the time of change management at customer decision that may well happen when initially converting or at a later point in time.

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

The technical procedure – well established tooling

Maintenance Planner

The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the conversion.

The Maintenance Planner is a pre-requisite for the system conversion to SAP S/4HANA, on-premise edition 1511. The Maintenance Optimizer (MOPZ) is not used

For more information regarding Maintenance Planner see SAP Help: http://help.sap.com/maintenanceplanner

Software Update Manager (SUM)

Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA, on-premise edition 1511.

Note:

• You must run the Maintenance Planner before the SUM.
• Ensure that the latest version of the Software Update Manager is used:

For all information about using the SUM, please see the document Conversion of SAP Systems to SAP S/4HANA, on-premise edition Using Software Update Manager available at:

• service.sap.com/sltoolset (LINK)
  • Software Logistics Toolset 1.0
  • Section "Documentation"
  • System Maintenance

Database Migration Option (DMO)

DMO - the one-step-migration to SAP HANA database for SAP systems. It is called "database migration option (DMO) of Software Update Manager (SUM)". For SAP S/4HANA it combines the installation of the SAP S/4HANA, on-premise software and database migration to SAP HANA in one tool

See the following SCN Blog with helpful information regarding DMO - SCN LINK

Adoption Tasks – how SAP support the customer

Simplification List for SAP S/4HANA, on-premise edition 1511

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

For more information see Simplification List for SAP S/4HANA, on-premise edition 1511 (FPS1): PDF

Conversion Pre-Checks

Pre-checks are shipped as SAP Notes to customers that want to convert to SAP S/4HANA. Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the instances that need addressing before attempting the conversion process. The checks are run twice again during the conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist.

Implement SAP Note 2182725, and all the related notes attached to it. Make sure to use latest version of this note and regularly check for updates of all attached notes. Implement and run these reports on every system (Sandbox, DEV, QA, PROD) you want to convert to SAP S/4HANA, on-premise edition 1511. Report R_S4_PRE_TRANSITION_CHECKS.

Custom Code Checks

These checks are based on the Simplification list concept. Before converting to SAP S/4HANA, on-premise edition 1511 you need to check your custom code against the SAP S/4HANA simplifications. These simplifications are loaded into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA 1511, on-premise edition

For more information about the Custom Code Check tool, see SAP Help Portal: Link and the following SCN blog: SAP S/4HANA Custom Code Migration Worklist.

Related information – at a glance

If you're here in Orlando with us for SAPPHIRE NOW, here are three Wednesday sessions to add to your agenda.

Speed Your Transformation with a Digital Core in the Cloud

Optimize your operations by launching your cloud strategy. Use the SAP S/4HANA Enterprise Management Cloud to establish your digital core. Benefit from an SAP Fiori user experience that is responsive and easy to use.

Grow Your SAP HANA Investment with SAP S/4HANA

Expand the benefits of an in-memory platform and optimize your operations. Understand why customers already running the SAP Business Warehouse application or SAP Business Suite powered by SAP HANA software should move to SAP S/4HANA software, and explore new suite innovations. Hear about customers that have taken this step and see what is involved.

Discover the Power of Embedded Analytics in SAP S/4HANA

Enable live contextualized insights and proactive decision making. Explore how SAP S/4HANA embedded analytics software brings together analytics and transactions. Compare SAP HANA Live offerings and SAP S/4HANA embedded analytics and see the best use cases for each. Learn what analytic content is delivered and how to build your own analytics.

Dear Expert,

I ran Maintenance Planner to generate stack for S4HANA conversion. My current system is running on ERP 6.0 EHP5 and I plan to convert the system to S4HANA. I received the following error:

I have checked in SOLMAN_SETUP and the RFC for READ is configured and working fine :

I need some idea on how to solve this issue as the Maintenance Planner keep complaining the READ RFC is not exist.

Thanks and Best Regards

Tarmizee

SAP S/4HANA Cookbook

The SAP S/4HANA Cookbook covers the most important aspects of implementing SAP Business Suite 4 SAP HANA (SAP S/4HANA).

It consists of a small set of HTML landing pages that provide abstracts for specific topics, along with links to further deep-dive information.

The content on these pages follows an iterative approach and will be updated regularly.

Comments are disabled on this page to keep it lean.

Please use the SAP S/4HANA forum to raise questions about SAP S/4HANA.

For comments regarding the cookbook itself, please use the accompanying blog.

Table of Contents

1. What is SAP S/4HANA

• Read this page to get an overview of SAP S/4HANA, current releases and capabilities, transition paths, ...

2. SAP Simple Finance, On-Premise Edition 1503: Implementation Information

• This first on-premise version of SAP S/4HANA was released in March 2015. Since this version currently has the highest implementation figures, there is a separate page on it in the cookbook.

3. Implementing SAP S/4HANA with SAP Activate (this page)

This page gives an overview of the accelerators consolidated in SAP Activate that  help SAP partners and customers throughout the different phases of SAP S/4HANA implementation projects:

• SAP Activate: Overview
• End-to-End Customer Experience
• Discover
• Prepare
• Explore
• Realize

Note: For access to SAP Notes and roadmap information, an 'S-user' is required (see here).

SAP Activate: Overview

SAP Activate project phases:

Discover

Prepare

Explore

Realize

Comments are disabled on this page. Please use the forum to raise questions, comments, or ideas.

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item: Subcontracting in MRP

Simplification List Item Description

SAP ERP had three different ways of planning parts to be provided to a subcontractor:

•Planning subcontracting demand together with internal demand in the make-to-stock planning segment (3.0 logic)

•Separating subcontracting demand and stock into single subcontracting planning segments and planning uncovered subcontracting demand together with internal demand in the make-to-stock planning segment (4.0 logic)

•Planning the demand of each subcontractor separately using subcontracting MRP areas (available from SAP ERP release 4.5)

In SAP S/4HANA 1511, the 4.0 logic was removed while the 4.5 logic was simplified. The SAP S/4HANA MRP uses default planning parameters if MRP area–specific material master records do not exist. You only have to create an MRP area for every subcontractor. Of course, it is still possible to create MRP area/supplier-specific material master data if required.

Business Impact

The default way of planning parts to be provided to subcontractors is based on MRP areas. A subcontracting MRP area should be created for every subcontractor. You do not have to create an MRP area-specific material master record for every part to be provided to the subcontractor but of course this is possible if you want to overrule the default planning parameters.

Required and Recommended Action(s)

If you have several subcontractors requiring the same component materials and if you do not yet use MRP areas to plan the required components then proceed as follows:

• Create MRP areas for every subcontractor (can be done before or after upgrade)
• Run regenerative MRP after the upgrade

For more details see the PDF attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2268044

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item: Storage Location MRP

Description

In SAP ERP, storage locations can be excluded from MRP or they can be planned separately from other storage locations. In the latter case, where storage locations are excluded from MRP, a reorder point procedure with maximum lot size is used to trigger transport reservations to fill up the storage location.

MRP areas cover the very same business requirements. Materials with the MRP area-specific MRP type 'ND' (no MRP) can be used instead of materials with a storage location excluded from MRP. Materials with the MRP area-specific MRP type 'VB' (reorder point planning) can be used instead of materials with separately planned storage locations. The storage location functionality is a subset of the MRP areas capabilities.

The S/4HANA MRP only plans on plant and MRP area level. Planning on storage location level is not available in SAP S/4HANA.

Business Impact

Storage location MRP is not available in SAP S/4HANA. You have to use planning on MRP area level instead.

Required and Recommended Action(s)

• Execute the related conversion pre-checks. Adaption required depending on the pre-check results
• Run report MRP_AREA_STORAGE_LOC_MIGRATION if the pre-checks detect that storage location MRP is used
• Remove and avoid inconsistent customizing and generate the required material master records for planning on MRP area level using the storage location material records

For more details see the PDF attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2268045

Hi All

I installed S/4HANA on-premise 30 days trial version (IDES ERP 6.0 Including Enhancement Package 7 on SAP HANA) on Amazon EC2 and activated already. Access by SAPGUI is OK. And now, I want to access by Fiori lunchpad.

Does anyone know how could I archive this?

I walked through scn topics on this, there are some posts for Fiori launchpad configuration step by step, that's very specific. I just can't figure it out clearly. and not sure was Fiori configured in this trial version already or not?

Is there anyone experienced the same thing and got solution already?

Thanks

Dear All,

We have 2 Independent Systems (2 boxes), 1 ECC 6.0 and other SAP HANA, we need to move the customizations from ECC to HANA System, is there any mechanism to achieve this, can we establish STMS between these 2 systems and move the requests or do we have any other option to achieve the same. We also need to move the existing ABAP Developments to HANA. Kindly suggest.

Thanks,

Regards,

Santosh

Alright everyone, tomorrow's the last day of SAPPHIRE. Here are the can't miss sessions before heading to the concert!

Explore SAP S/4HANA Now and in the Future

Explore the benefits of staying current when it comes to software innovation. Learn about the innovations delivered in the digital core, SAP S/4HANA, and understand the road map for the suite. Uncover the resources available for you to research and learn more.

Make Strategic Deployment Choices for SAP S/4HANA

Explore deployment strategies based on your organization's technology starting point. Understand the available transition paths for SAP S/4HANA software. Learn from the experience of existing SAP S/4HANA suite customers about the decisions that need to be taken in each phase of the journey.

Align Business and IT Priorities for Strategic Digital Transformation

Embrace co-innovation throughout your business to enable digital transformation. Hear SAP customers discuss how IT and lines of business are working together to transform business processes and models. Learn how the SAP S/4HANA suite is helping companies run in real time and is making an impact on the bottom line.

While I don't think you'll be able to see the concert via the live stream, there are some great sessions, so head over there now! View Live Agenda

Be on the lookout for recorded sessions coming soon!

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item: Material Field Length Extension

Simplification List Item Description

• With SAP S/4HANA, on-premise edition 1511, the maximum field length of the material number is extended from 18 to 40 characters.

• The appropriate related SAP development entities (domains, structures, table types, and transparent tables, external and internal interfaces, user interfaces, and so on) have been adapted accordingly. Where required, automated logic is in place and executed automatically in case a customer converts his current SAP Business Suite system into SAP S/4HANA 1511.
• The default setting, both after the move to SAP S/4HANA and for new installations, is that the extended material number functionality is NOT activated. To use a material number with 40 characters, the customer needs to activate this functionality

Business Impact

• In case the customer continues to use to 18 characters long material number functionality, there is no business impact. Depending from the details there might be an impact on existing custom code.
• In case the customer does activate the extended material number functionality the impact within the multi-system landscape need to be considered where not all related systems are able to deal with a 40 character material number.

Required and Recommended Action(s)

• Execute the related conversion pre-checks and custom code migration worklist to get detailed information about the potentially required custom code adaption effort.

For more details see the PPT attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2267140

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item: Credit Management

Simplification List Item Description

• FI-AR-CR Credit Management is not available in SAP S/4HANA, on-premise edition 1511. It has been replaced by SAP Credit Management (FIN-FSCM-CR) for Financials and Sales and Distribution (SD).

Business Impact

• If you are not using FI-AR-CR Credit Management there is no business impact for you.
• If you are using FIN-FSCM-CR SAP Credit Management already today, there is no business impact for you.
• If you are using FI-AR-CR Credit Management you need to migrate to FIN-FSCM-CR SAP Credit Management. S/4HANA provides various tools in order to support and automate this migration.
• FIN-FSCM-CR SAP Credit Management provides additional functionality compared to FI-AR-CR Credit Management. The configuration and activation of the additional functionality is not required in the context of the migration. However, we recommend that you get familiar with these additional capabilities in order to leverage the full value of FIN-FSCM-CR SAP Credit Management and to optimize your credit management processes.

Required and Recommended Action(s)

• In case a migration is required (see above), you need to migrate configuration data, master data, credit exposure data and credit decision data.
• FIN-FSCM-CR SAP Credit Management is available since ERP 6.0 (without any enhancement packages). Therefore you have the option to activate to FIN-FSCM-CR SAP Credit Management in your existing ERP 6.0 landscape, independent of / before your S/4HANA migration project. This way you can take out complexity out of your S/4HANA migration project. However, there are no tools available on those releases that do an automatic migration of configuration data and master data, as they are on S/4HANA.

For more details see the PPT attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2270544

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item: Simplified Data Model in Pricing and Condition Technique

Simplification List Item Description

• Several data model changes in the Pricing and Condition Technique area are provided with SAP S/4HANA 1511. These are:
• Replacement of table KONV with the new table PRCD_ELEMENTS as data persistency for pricing results. KONV is and can still be used for data declaration purposes. It still defines the structure of the pricing result within the application code.
• The concatenated variable key field VAKEY of a condition table has been removed from all condition header tables, including KONH (pricing), NACH (output determination), KOND3 (campaign determination), KONDN (free goods determination), KONHM (portfolio determination), J_3GPRLHD (CEM price list determination), and WIND (document index). The concatenated variable data field VADAT has also been removed.
• Several field length extensions

Business Impact

• No impact on the standard SAP business processes
• The SAP internal program logic has been adapted to the new persistency and the new field lengths.
• Pricing results of existing documents created before the system conversion (that is, the content of table KONV) are converted as part of the system conversion and transferred automatically to the new data table.
• It might be required to adapt custom code that is related to the changed data model.
• Customer code has to be adapted according to the cookbooks in SAP Note 2220005.

Recommended Action

• Execute conversion pre-check class CL_S4_CHECKS_PRICING delivered via SAP Note 2188735. If Check ID ‘SAP_KONV_EXTENSION_CHECKS’ indicates that table KONV has been enhanced with customer-specific fields, follow instructions in SAP Note 2189301.
• Follow instructions in “How-To-Guides” included in SAP Note 2220005 to adapt your objects and code where necessary
• Run post-processing report PRC_MIG_POST_PROCESSING: See SAP Note 2267308 and “How-To-Guide” in SAP Note 2220005.

For more details see the PPT attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2267308

Dear members

I am confused about the functionality of SAP S/4Hana related to BI . Does  S/4 HANA has all feature / functionality which one will get in Business Objects ? . Do we still need to purchase Business Object for BI related functionality  , if we install S/4 HANA ? .

Kindly guide us pl .

With Regards

B Mittal

Hello to everyone,

We have an issue trying to connect ERP S/4HANA ON-PREMISE to HCI.  How can I create a proxy connection to HCI or with RFCD?.  I can't find information about S/4HANA ON-PREMISE, a lot of information for ECC but we need S/4HANA.

thanks for your attention.

regards,

Carlos Andres Gonzalez

Hi,

we would like to get started with S/4HANA and therefore we would like to buy a dev machine. What is the requirement (doesn't need to be certified) for a S/4HANA system for the start? Where did you buy your system?

I already know the tools like  https://apps.support.sap.com/sap/bc/bsp/sap/qs_oberflaeche/hana.do?sap-language=en&bsp-language=en 

but I would like to know some real world system configuration. Looking forward to see some configurations.

Regards, Vanessa

Hello,

I'm currently implenting S4 Hana 1511 (FPS01) for a customer.

We need to send the Business Partners created/changd in S4 to a legacy system.

We were thinking that Idocs is the best approach but I cannot find any Idocs associated to Business Partners that contains all relevant information.

What are the options to be able to send Business Partners (and relations) to a leagcy system?

I thank you in advance for your help.

Best regards,

Rémy

SAP Finance Consultant.