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

Transcription

1 White Paper CUSTOMER Document Version: Simplification List for SAP S/4HANA, on-premise edition 1511

2 Table of Content 1 INTRODUCTION Purpose of the Document General Topics for the simplification list Description Business Process related information Recommendations Pre-Check Relevance Custom Code related information Categories THE SIMPLIFICATION LIST PER APPLICATION AREA Master Data Business Partner Approach Simplified Product Master Table Material Number Field Length Extension Simplification of Parameter Effectivity Foreign Trade fields in Material Master MRP fields in Material Master Material Type SERV Product Catalog functionality for integration with Internet Application Components Product Catalog Object Identifier Type Code MDM 3.0 integration SRM Product Master Logistics Batch Management Business Partner IDOC Types (DEBMAS and CREMAS) Classifications functionality of customer master Sales & Distribution SD Simplified Data Models Data Model Changes in SD Pricing Foreign Trade within SAP S/4HANA Credit Management ERP SD Revenue Recognition Optimization of SD Rebate Processing for TPM Customers Simplification in SD Analytics Advanced Order Processing and Billing for Contractors to the public sector Operational Data Provisioning

3 Business Role Internal Sales Representative Webshops by Internet Sales or Web Channel Experience Management Commodity Management Sales Sales Activities Billing Document Output Management SD Rebate Processing replaced by Settlement Management Miscellaneous minor functionalities in SD Area Industry-Specific SD Complaint Handling SD FI/CA Integration with distributed systems Customer Service Customer Interaction Center (CIC) Procurement Co-Deployment of SAP SRM Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC) Vendor evaluation based on LIS Subsequent Settlement - Vendor Rebate Arrangements ERP Shopping Cart Internet Application Components (IAC) MDM Catalog Pricing Data Model Simplification Output Management Adoption in Purchase Order MM-PUR WebDynpro Applications Classic MM-PUR GUI Transactions replacement Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes Supplier Distribution via MDG-S Authority Concept for Supplier Invoice Foreign Trade within SAP S/4HANA Procurement Commodity Management Procurement Automatic Document Adjustment Logistics AB Agency Business Logistics ATP New advanced ATP in SAP S/4HANA Table VBBS icon (E2open) New fashion solution Logistics - Environment, Health & Safety (EHS) Industrial Hygiene and EC interfaces Occupational Health Waste Management Simplification in Incident Management and Risk Assessment Logistics GT Global Trade Management Logistics Material Management Inventory Management (MM-IM) Data model in inventory management (MM-IM) Availability of Transactions in MM-IM

4 Material Ledger Obligatory for Material Valuation Material Valuation - Statistical moving average price Logistics PLM Enterprise Search Assemblies Product Designer Workbench Access Control Management (ACM) cfolders cdesk Recipe Management Engineering Client Viewer (ECL) Easy Document Management (Easy DMS) Engineering Desktop (EDesk) STEP Support DMS Documents@WEB Variant Configuration Classification IPPE-BOM Converter BOM, Routing, Production Version SAP PLM Recipe Development PH_Sample iview Engineering Change Management ECR/ECO Engineering Change Management Change Sequence Graph Engineering Workbench Collaborative Engineering ippe Time Analysis Integration to SAP Portfolio and Project Management Routing Component Assignment Release Management Framework Engineering Record Logistics PP PP-MRP - Subcontracting Storage Location MRP External Interfaces in PP Graphical Planning Table Logistic Information System in PP Sales and Operation Planning Simplified Sourcing Browser-based Process Instruction-Sheets/Electronic Work Instructions Internet Kanban ERP Line-Balancing and Sequencing MRP in HANA Planning File Total Dependent Requirements Forecast Based Planning

5 Demand Forecasting Release status for different RFC function modules revoked Computer Aided Processing Planning (CAP) ABAP-List-Based PI-Sheets ANSI/ISA S95 Interface Digital Signature Electronic Records Downtimes Functionality MiniApps PP-PI Process Data Evaluation (PP-PI-PMA) Campaign Weighing and Dispensing Production Campaign (ERP) Electronic Batch Record Process Messages Control Recipes/Instructions Process Operator Cockpits Material Identification/Reconciliation Flow Manufacturing Process Flow Scheduling (PP-PI) Rate and Rough-Cut Planning Planning Horizon Batch History Logistics PS Simplification of maintenance transactions Navigation to Project Builder instead of special maintenance functions Production Resources and Tools functions for projects Project Planning Board, Gantt-Chart, Hierarchy and Network Graphics Current simulation functions in project system Specific PS archiving transactions Project texts (PS texts) Claim Management Selected project financial planning and control functions Simplification of Date Planning Transactions Workforce Planning Progress Tracking & Monitoring Dates Project Claim factsheet Project Reporting Selected Interfaces Construction Progress Report and Valuation ITS Services Selected PS Business Function Capabilities Selected Logistics Capabilities Selected Project System BAPIs Logistics PSS QM Interface

6 IUCLID5 Interface Enterprise Search Model Hazardous Substance Management Add-On: SAP Product and REACH Compliance (SPRC) Add-On: EHS Web-Interface Add-On: Genifix (Labelling solution) BW Extractors for Dangerous Goods Management and Specification Management PS&S Key Figures MyApps for Product Safety and Dangerous Goods Management SARA Reports Substance Volume Tracking Selection Criteria based on tables VBUK and VBUP Simplification in Product Compliance for Discrete Industry Logistics Plant Maintenance LIS in EAM Download Data in MS Access out of List Scheduling of Maintenance Plan Mobile Asset Management (MAM) Batch Input for Enterprise Asset Management (EAM) Change Order and Operations WebDynpro Application for Maintenance Planner (<= EhP4) Enterprise Search Logistics Quality Management Results Recording ITS services in QM QM WEB Workplace (MiniApps) based on ITS Services Quality Notifications Quality Management Information System (QMIS) Quality Inspection Engine (QIE) Logistics - Execution Transportation Transportation (LE-TRA) Logistics Warehouse Management Warehouse Management (WM) Financial General Different Start Releases Data Model Changes in FIN Replaced Transaction Codes and Programs Financial - General Ledger General Ledger SAP Invoice and Goods Receipt Reconciliation SAP HANA ODP on HANA Calc View-Based Reporting SAP HANA Live Reporting Financials - Accounts Payable/Accounts Receivable SAP Working Capital Analytics/DSO and DPO Integration with FSCM Biller Direct (FI-AR) Integration with FSCM Biller Direct (FI-AP)

7 Financial - Asset Accounting Data Structure Changes in Asset Accounting Asset Accounting Integration to Lease Accounting Engine (LAE) Joint Venture Accounting (JVA) Financial - Cash Management Cash Management - General Financial Controlling Technical Changes in Controlling Profit and Loss Planning and profit center planning Activity-Based Costing General Cost Objects and Cost Object Hierarchies Transfer Prices/ Parallel Delta Versions ALE Scenarios Cost Elements SAP Margin Analysis Financials - Treasury and Risk Management Correspondence Functionality Interest Rate and Yield Curve Functionality Accrual/Deferral of Expenses and Revenues Commodity Risk Management Credit Risk Analyzer Link to Cash Management Exposure Management Fiduciary Deposits Drawable Bonds Drilldown Reporting in Treasury and Risk Management Master Agreements Offers Simulation in Transaction Management Quantity Ledger Always Active for Money Market Transactions Several Kinds of Financial Objects Disabled Credit Risk Analyzer Link to Cash Management Disabled Financials Miscellaneous Credit Management Technical Changes in Material Ledger Real Estate Classic Data Archiving SAP Smart Business for SAP Simple Finance Globalization Globalization Financials Globalization Logistics Human Ressource General HCM Approach within SAP S/4HANA Industry Cross Industry Functionality BRIM - Billing of Event Data Records (EDR)

8 BRIM - Common Object Layer (COL) BRIM - Integration with FSCM Biller Direct (FI-CA) BRIM - Solution Sales and Billing BRIM Immediate Master Data Replication to SAP Convergent Charging Industry Banking SEM Banking Industry Beverage IS-Beverage Cleanup IS-Beverage solution Industry DIMP Aerospace & Defence Collective Processing Pegging Cost Distributing Processing Manufacturer Part Number Flight Scheduling Enhancements Actual Labour Costing / Time Recording Enhancements subcontracting special stock types not available AECMA Spec 2000M Military version Industry - Automotive Tracking Inbound Supplier Workplace External Service Providers Cross-System Transit between Two Plants Long Material Number Material Version Planning Regular Route Shipments BSP based Dealer Portal Industry: DIMP Engineering, Construction & Operations Real Estate Sales (Homebuilding) Industry: DIMP High Tech Software License Management Installed Base Management Contract Mgt. Enhancements Billing Process Enhancements Software Maintenance User Exits in DRM Condition Technique in DRM: Rule Configuration Manufacturer/Supplier Processes Distributor/Reseller Processes Industry DIMP Mill Non Ferrous Metal Processing Sales Order Versions Stock Overview and Object Search by Characteristics Scheduling PRTs Process Batch Industry Public Sector

9 Former Budgeting System (FBS) in Funds Management Functionality for FACTS I and FACTS II (Federal Agencies Centralized Trial Balance System) Expenditure Certification Specific fields on Business Partner Fund Accounting based on Special Ledger Data Structure changes in BCS Funds Management Dimensions as part of the Universal Journal Functionality for BCS Multi-level Budget Structure Functionality Average Daily Balance-based Distribution Functionality German Local Authorities Industry Telecommunication Lock and unlock services using IST_TDATA Portal Roles for Network Lifecycle Management (NLM) Industry Utilities Monitoring Profile Value Import Utilities Customer Electronic Services (UCES) Stock and Transaction IS-U Sales Processing Marketing - IS-U Loyalty Program Front Office (EC20) GIS Business Connector Enterprise Services for SAP for Utilities (IS-U) Cross Topics Output Management Analytics Enterprise Search Internet Pricing and Configurator (SAP IPC) Job Scheduling Legacy System Migration Workbench (LSMW)

10 DISCLAIMER THIS DOCUMENT OUTLINES OUR GENERAL PRODUCT DIRECTION AND SHOULD NOT BE RELIED UPON IN MAKING A PURCHASE DECISION. THIS PRESENTATION IS NOT SUBJECT TO YOUR LICENSE AGREEMENT OR ANY OTHER AGREEMENT WITH SAP. SAP HAS NO OBLIGATION TO PURSUE ANY COURSE OF BUSINESS OUTLINED IN THIS PRESENTATION OR TO DEVELOP OR RELEASE ANY FUNCTIONALITY MENTIONED IN THIS PRESENTATION. THIS PRESENTATION AND SAP S STRATEGY AND POSSIBLE FUTURE DEVELOPMENTS ARE SUBJECT TO CHANGE AND MAY BE CHANGED BY SAP AT ANY TIME FOR ANY REASON WITHOUT NOTICE. THIS DOCUMENT IS PROVIDED WITHOUT A WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. SAP ASSUMES NO RESPONSIBILITY FOR ERRORS OR OMISSIONS IN THIS DOCUMENT, EXCEPT IF SUCH DAMAGES WERE CAUSED BY SAP INTENTIONALLY OR GROSSLY NEGLIGENT SAFE HARBOR STATEMENT THIS DOCUMENT IS INTENDED TO OUTLINE FUTURE PRODUCT DIRECTION, AND IS NOT A COMMITMENT BY SAP TO DELIVER ANY GIVEN CODE OR FUNCTIONALITY. ANY STATEMENTS CONTAINED IN THIS DOCUMENT THAT ARE NOT HISTORICAL FACTS ARE FORWARD-LOOKING STATEMENTS. SAP UNDERTAKES NO OBLIGATION TO PUBLICLY UPDATE OR REVISE ANY FORWARD-LOOKING STATEMENTS. ALL FORWARD-LOOKING STATEMENTS ARE SUBJECT TO VARIOUS RISKS AND UNCERTAINTIES THAT COULD CAUSE ACTUAL RESULTS TO DIFFER MATERIALLY FROM EXPECTATIONS. THE TIMING OR RELEASE OF ANY PRODUCT DESCRIBED IN THIS DOCUMENT REMAINS AT THE SOLE DISCRETION OF SAP. THIS DOCUMENT IS FOR INFORMATIONAL PURPOSES AND MAY NOT BE INCORPORATED INTO A CONTRACT. READERS ARE CAUTIONED NOT TO PLACE UNDUE RELIANCE ON THESE FORWARD-LOOKING STATEMENTS, AND THEY SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISIONS. 10

11 REVISION LOG Version Date Remarks Release of the first version of the Simplification List for SAP S/4HANA, on-premise edition Update relevant Finance - Chapter SAP Smart Business for SAP Simple Finance: Added the footnote with the remark Relevant for SAP Simple Finance, on-premise edition 1503 customer - Chapter Integration with FSCM Biller Direct (FI-AR) (moved from Area Cross Industries to FIN AP/AR area) - Chapter Integration with FSCM Biller Direct (FI-AP) added to FIN AP/AR area - Chapter SAP Margin Analysis added in FIN CO area Update relevant for Industry Utilities - Chapter Enterprise Services for SAP for Utilities (IS-U): Adapted text Added dedicated enterprise services not available within SAP S/4HANA, on-premise edition 1511 Update relevant for Logistics (PS) - Chapter Selected Project System BAPIs: Added Item to Simplification List Update relevant for Logistics (QM) - Chapter Quality Inspection Engine (QIE) added Update relevant for Cross Industry Functionality - Chapter Integration with FSCM Biller Direct (FI-AR) (moved from Area Cross Industries to FIN AP/AR) - Chapter BRIM - Solution Sales and Billing added - Chapter BRIM Master Data Replication to SAP Convergent Charging added Update relevant for Procurement - Chapter Output Management Adoption in Purchase Order added Update relevant for Industry Telecommunication - Chapter Portal roles (SAP ERP) for the Network Lifecycle Management (NLM) added Update relevant for Industry Aerospace & Defence - Chapter AECMA Spec 2000M Military version added Update relevant for Master Data Area - Chapter MDM 3.0 integration added. - Chapter SRM Product Master added. - Chapter Logistics Batch Management added Area Sales & Distribution - Chapter SD Simplified Data Models: Adapted the required and recommended action chapter - Chapter Data Model Changes in SD Pricing: Adapted the required and recommended action chapter - Chapter Renamed from Contract Billing to Advanced Order Processing and Billing for Contractors to the public sector to avoid misunderstandings. Area Globalization - Chapter Globalization Logistics added Update relevant for Master Data Area - Chapter Business Partner IDOC Types added - Chapter Customer classification added Miscellaneous Adaptions in Simplification Items - SD: Chapter Industry-Specific SD Complaint Handling - PP: Chapter Browser-based Process Instruction-Sheet - PS: Chapter ITS Services 11

12 1 Introduction SAP S/4HANA is SAPs next-generation business suite, it is not a legal successor of any SAP Business Suite product. It is a new product completely built on one of the most advanced in-memory platform today SAP HANA and modern design principles with the 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 the digital economy. In the approach to build SAP S/4HANA, SAP is re-architecting its solution for modern business processes demanded by an increasing digitization of the world. Re-architecting a solution that has been growing over the past 25 years means and sometimes evolved into different data structures and architectures means as well that we have to decide on one data structure and architecture moving forward. This is the only way how we can prepare the solution for more simplicity and faster innovation cycles. Example: In the current ERP system we do have two general ledgers, the classical general ledger and the new general ledger, that has been introduced mainly driven by the need to support multiple valuation methods. Moving forward in SAP S/4HANA of course we have to decide on one general ledger structure and here we have chosen the structure of the new general ledger offering much more flexibility. In most cases SAP is pursuing the functional strategies already laid out in the existing Business Suite world, where many innovations have been started (like in the example above). In consequence it is possible to prepare for the SAP S/4HANA System Conversion by a adopting the target capabilities already in the classical SAP Business Suite. That said SAP is taking responsibility for managing the impact of these decisions. 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. The total list of simplifications for SAP S/4HANA, on-premise edition 1511 compared to the SAP Business Suite products captured in this list might appear quite long. However, SAP does not foresee that any customer system will be hit by all of them as these go across all capabilities of the system including industry solutions. This list must be treated as a complete inventory that needs to be mapped against a productive environment to determine the impact when converting. 12

13 SAP expects, that the same applies to custom code implemented by our customers themselves or by partners. This code has grown over time and experience has shown that a large share of custom code is not even used anymore. Simplifying your own extensions will benefit the general simplification of your system. To ease this process SAP will provide an analysis that will determine custom code in the context of these changes and as such the effort of custom code migration will become projectable. In addition, customer should be aware of the fact that only S/4HANA packages (and no other software) shall be deployed on an S/4HANA installation. Details are set forth in the Software Use Rights document. 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 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. 1.1 Purpose of the Document The purpose of this document is to support customer in the system conversion from SAP ERP 6.x or SAP Simple Finance, on-premise edition to SAP S/4HANA, on-premise 1511 Edition. Note: The Simplification List for SAP S/4HANA is edition/release dependent. In this collection we are focusing on SAP S/4HANA, on-premise 1511 Edition. For future SAP S/4HANA releases, a new list will be made available. 1.2 General Topics for the simplification list Moving to SAP S/4HANA On-Premise 1511 delivery, for a typical ERP 6.x customer requires a database migration to SAP HANA (if the customer is not yet on SAP HANA) followed by the installation of the new simplified code and requires also changes in adaptions on customer s side. The most prominent example where the customer needs to adapt to these SAP S/4HANA On-Premise 1511 delivery simplifications is the custom code which needs to be compliant with the data structure and scope of the appropriate SAP S/4HANA release. In addition, customer should be aware of the fact that only S/4HANA packages (and no other software) shall be deployed on an S/4HANA installation. Details are set forth in the Software Use Rights document. Customers expectation related to the move to SAP S/4HANA On-Premise 1511 delivery is that SAP informs and gives guidance about the required steps and tasks on this journey. Based on the Simplification List for SAP S/4HANA, on-premise edition 1511, SAP will provide the information per application/functional area about the SAP S/4HANA On-Premise 1511 delivery related simplifications. The Simplification List is a collection of single Simplification Items with the 13

14 focus on what has to be considered through an Implementation / System Conversion Project from SAP ERP 6.X Customers to SAP S/4HANA On-Premise 1511 delivery. Per Simplification Item the following information will be provided: Description, Business Impact and Recommendations SAP Notes (for related Pre-Checks or Custom Code Checks) Description The Simplification List is structured into different application / functional area known from SAP Business Suite with a short explanation about the technical change Business Process related information Here it is described what the Simplification Item means for the related business processes Recommendations The dedicated recommendations will give a description about how the related custom code needs to be adapted (based on SAP Notes). Note: The recommendations and SAP Notes are formulated in a general manner corresponding to a standard customer SAP Business Suite architecture and therefore may differ depending on the real System Landscape in place. 1.3 Pre-Check Relevance Pre-checks are shipped as SAP Notes to customers that want to convert to 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. 1.4 Custom Code related information To support the customer to detect custom code which need to be adapted moving to SAP S/4HANA On-Premise 1511 delivery, SAP offered a custom code analysis tools (as part of the NW 7.50). The customer can verify if his current custom code will be compliant with the SAP S/4HANA On-Premise 1511 delivery data structures and scope. For more Info, see details on the SAP Documentation: SAP Help 1.5 Categories The simplification items can be categorized base on the type of Impact: 14

15 Re-architecting for SAP HANA in-memory platform Used for functionality which is optimized to leverage the capabilities of SAP HANA database, e.g. New Data Modell Consolidation of existing functionalities Functionality which is unified in the core and optimized according to the principle of one, but from a business process and user point of view the functionality basically stays the same. No functional equivalent Compared to the SAP Business Suite, there may be no functional equivalent available in SAP S/4HANA on premise 1511 delivery for S/4HANA is not a legal successor of an SAP Business Suite product. Alternative functionality with application innovation is in many cases already available in an S/4HANA scope or is on the roadmap. 15

16 2 The Simplification List Per Application Area Master Data Business Partner Approach Description There are redundant object models in the traditional ERP system. Here the vendor master and customer master is used. The (mandatory) target approach in S/4HANA is the Business Partner approach. Business Partner is now capable of centrally managing master data for business partners, customers, and vendors. With current development, BP is the single point of entry to create, edit, and display master data for business partners, customers, and vendors. Additional Remarks: It is planned to check the introduction of the Customer/Vendor Integration in the pre-checks and the technical Conversion procedure of SAP S/4HANA, on-premise edition A system where the customer/vendor integration is not in place will be declined for the transition. The Business Partner Approach is not mandatory for the SAP Simple Finance, on-premise edition Business Process related information Only SAP Business Suite customer with C/V integration in place can move to SAP S/4HANA, on-premise edition 1511 (Conversion approach). It s recommended but not mandatory that BuPa ID and Customer-ID / Vendor ID are the same. The user interface for SAP S/4HANA, on-premise edition 1511 is transaction BP. There is no specific user interface for customer/vendor like known from SAP Business Suite (the appropriate specific transaction like XD01, XD02, XD03 or VD01, VD02, VD03 / XK01, XK02, XK03 or MK01, MK02, MK03 etc. are not available in SAP S/4HANA, on-premise edition 1511) Transaction not available in SAP S/4HANA on-premise edition 1511 FD01, FD02, FD03, FD05, FD06, FD0 FK01, FK02, FK03, FK05, FK06, FK08 MAP1, MAP2, MAP3 MK01, MK02, MK03, MK05, MK06, MK12, MK18, MK19, V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21, V+22, V+23 VAP1, VAP2, VAP3 VD01, VD02, VD03, VD05, VD06 XD01, XD02, XD03, XD05, XD06, XD07 XK01, XK02, XK03, XK05, XK06, XK07 Currently mass maintenance for customers and vendors via transaction MASS is not available (on the roadmap of a future SAP S/4HANA release) 16

17 Required and Recommended Action(s) Perform Conversion Pre-Check to verify start situation Introduce Business Partner Approach (Customer/Vendor Integration) on start release (in case not done yet) Even if it is not mandatory required for the Conversion to SAP S/4HANA to have the same ID for Business Partner (BuPA) - Customer and BuPa - vendor it is recommended to align the IDs accordingly Related SAP Notes Conversion Pre-Checks SAP Notes: , Simplified Product Master Table Description Table T130F (Table of Field attributes) does have delivery class E (E = Control table, SAP and customer have separate key areas). In SAP Business Suite the delivery class of table T130F is G (G= Customizing table, protected against SAP Update, only INS all) Business Process related information No influence on business processes expected Required and Recommended Action(s) None Material Number Field Length Extension SAP S/4HANA, on-premise edition 1511 can support a material number with 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, on-premise edition Nevertheless there might be constellations where a customer needs to be aware about. For example: In certain constellations there might be the requirement to adapt custom code related to the material number field length extension. In a multi-system landscape, the customer has to decide if and when to switch on the extended material number functionality, as the switch impacts how compatible the system communicates within a system landscape. In the following chapters, the different aspects of the material number field length extension are described. 17

18 Overview With SAP S/4HANA, on-premise edition 1511, the maximum field length of the material number is extended from 18 to 40 characters. The material number field length extension was done with SAP S/4HANA and is available within the SAP S/4HANA, on-premise edition 1511 and SAP S/4HANA, cloud-edition For the first step into SAP S/4HANA SAP Simple Finance, on-premise edition 1503 the maximum field length is still 18 characters long. Additional remark: The next version of SAP Simple Finance, on-premise edition which will be based on Enhancement Package 8 will as well be based on an 18 characters long material number Consistent Usage in System-Internal Coding Extending the material number means that in the coding within the system it must be ensured that 40 characters can be handled at all relevant coding places. Especially, it must be made sure that the material number will not be truncated to its former length of 18 characters as this would result in data loss. In an SAP system, this consistent behaviour is usually ensured by the fact that all data elements used to type relevant fields are derived from the same domain, the domain defining the technical length of the derived fields. Whenever coding uses these fields, the coding is automatically adapted when the domain changes. For the material number itself we identified the domains that are used to define material number fields. All these domains have been extended to 40 characters. Besides these direct usages of the material, it may be that a specific material is also used in other fields. An example may be characteristic values: A material may well be used as characteristic value. For all such fields for which a material besides other possible values is a valid content, it has been checked that these fields are long enough to hold the extended material number. These fields (or the underlying domains) have been extended as well. Extending further dependent fields of course means that the usages of the fields have been investigated as well. 18

19 Extending such target fields which are not material numbers by themselves was only done if the material number needs to be handled in the field, as extending a field usually trigger follow up changes. At several places, the material number is used as reference, template, or for other reasons but another (shorter) value, for example, a GUID, could be used as well. In these and other similar cases, it may be the better choice to switch to another value. Using this other value has been done at all places where this was appropriate. Overall, the complete data flow in the system has been analysed to identify all places at which a material number was moved to a field that was not long enough for a 40 character material number. All these conflicts have been handled in one of the ways described above. Such an analysis also needs to be done in customer or partner coding. The described changes have also been applied to parameters of all interfaces that are usually called only within one system, that is, local function modules, class methods, BAdIs etc. In the types and structures used as parameters in these local calls, the material number has simply been extended to 40 characters. The same is true for other extended fields as well. This was usually also done for unreleased remote enabled function modules as the main use case for such function modules is an internal decoupling within one system. For interfaces that are usually called remotely, a different way has been chosen. For more information, see the specific chapter below Storage of the Material Number on the Database Extending the material number on the database means that the field length of the MATNR field on the database has been extended from 18 to 40 characters. This has been done in all tables (and all fields within the tables) in which a material number can be stored. Although the maximum length of the database field used to store the material number is now 40 characters, the way how the material number content is stored in the database field has not been changed compared to SAP Business Suite. This means that for such fields usually no data conversion is needed when converting from SAP Business Suite to SAP S/4HANA, on-premise edition This holds especially true for pure numeric material numbers. With standard Customizing (leading zeroes are not significant, lexicographic flag not set), pure numeric material numbers are still restricted to 18 characters and will be filled up on the database only up to 18 characters by leading zeroes. This is the same behaviour as in SAP Business Suite. Overall, the chosen way of storing material number content avoids data conversions in the database. Note that data conversion will be needed when a material number is stored in a field that has a concatenated content, and the material number is part of that concatenated content: Concatenation in the code uses the complete technical length of the field (which now is 40 characters) and is also reflected in the database content. This will be explained in detail later in this Simplification Item. 19

20 The Material Number in Released External Interfaces Usually a customer has a multi-system landscape: The ERP system is connected to miscellaneous internal and external (SAP or non-sap) systems. Accordingly, a SAP S/4HANA, on-premise edition 1511 system with a material number field length of 40 characters needs to consider this multi-system landscape requirement where not all related systems are able to deal with a 40 character material number. Furthermore, it cannot be assumed that all ERP systems in a customer landscape will be converted to SAP S/4HANA, on-premise edition 1511 at the same point in time. That means that the external interfaces used for integration have to be compatible to old versions of the interface. This is especially relevant for the commonly used integration techniques BAPI, RFC, and IDoc as these techniques rely on a fixed length and order of fields in the transmitted data. Simply extending the material number field (or other extended fields) in these interfaces would therefore technically break the version compatibility. We have decided to provide a technical-version compatibility for released external interfaces in the way that is commonly used and proposed for BAPI interfaces: The already existing field keeps its original length and a new field has been added at the end of the structure (or as new parameter) that allows transmitting material numbers with 40 characters. Besides this, it must be ensured that no material number (or other extended field) can be maintained in the system with a content length greater than the old length of the field. To enforce this and to make the field length extension as far as possible non-disruptive for the SAP S/4HANA customers, the extended material number functionality must be switched on explicitly. Only after this decision it is possible to allow more than 18 characters for the material number. The changes described have been done for BAPIs, IDocs, and released remote-enabled function modules. This has additionally been implemented where necessary for remote function calls issued by the SAP S/4HANA system and for unreleased remote-enabled function modules that are used to communicate with other SAP Business Suite products like SAP SCM or SAP CRM. A complete list of relevant function modules, IDocs, and structures that have been extended in this way can be found in the piece lists in the simplification database. For released WebServices (SOA?), adding a new field or extending the material number field was not necessary as these services usually already allow material number with up to 60 characters in their interfaces. After an SAP Business Suite System has been converted to SAP S/4HANA, on-premise edition 1511 or a SAP S/4HANA on-premise edition 1511 was newly installed, the extended material number functionality will by default be switched off. 20

21 System Behaviour Depending on the Extended Material Number Switch If the extended material number functionality is NOT switched on, the system behaves as follows: After an SAP Business Suite System was converted to SAP S/4HANA, on-premise edition 1511, the B2B and A2A communication via BAPIs, IDOCs, Web-Services, released RFCs (inbound), and remotely called RFCs (outbound) still work without further changes The shorter versions of the extended fields o are still part of the interfaces o are still filled when sending data o are still understood when retrieving data If the extended field is used as part of a communicated concatenated field, this concatenated field has still to be sent in the original field in the old short format and has to be interpreted in the inbound case in the old short format. The system prevents that data is created that cannot be sent via the old interface, that is the usage of the extended fields is restricted to the old length. Communication partners can still rely on the old known behaviour of the interfaces. The long version of the extended field in the interfaces is filled and interpreted, too. For example, the 18 character material number is also communicated via the 40 character field. This means that the communication partners can already adapt their interfaces for using the long field although only short material numbers are allowed. When extended material number functionality is switched on, the system no longer guarantees that all fields are filled in a way that they can be transmitted via the old fields. Therefore the following applies: Material numbers and other extended fields can be used with the full length (40 characters). The shorter version of an extended field is obsolete in communication interfaces. Only the extended field is relevant in communication interfaces. That means: o Only the extended version of the field is sent. o Only the extended version of the field is accepted in the inbound case. o If short fields are still filled this is handled as an error. This is implemented to prevent that communication partners send truncated values. Concatenated keys containing extended fields are sent and evaluated in the new format Communication partner have to adjust to the new fields and data formats. Be aware: All SAP Business Suite systems are communication partners! Internal Calls of External Interfaces As described in the previous chapters, different strategies have been chosen for internal and for released external APIs. If a released external API is called internally, that is locally within one system, it is always ensured that the call can be done with new extended field length, no compatibility is required. Therefore and to be safe when extended material number functionality is activated all internal calls of external interfaces must only use the newly added extended fields. 21

22 This is also true if structures are used internally that are also used in released external interfaces and that therefore have been changed in the way described. Then only the new extended field shall be used in all internal coding, too System Settings to Activate the Extended Material Number Functionality 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. The following settings are required for that: 1. Activation of the Extended Material Number Functionality The activation is realized as client-dependent customizing table. IMG Cross-Application Components General Application Functions Field length Extension Activate extended fields Alternative: Transaction FLETS (For the table maintenance the authorization group FLE [authorization object S_TABU_DIS] is required). 2. Changing the Material Number Format Transaction OMSL allows a customer-specific settings regarding the material number field length. Here the settings need to be adapted to allow a field length of more than 18 characters. Define Output Format of Material Number can be accessed via IMG ( Logistics General Material Master Basic Settings) Note: If the extended material number functionality is activated in a system, it cannot be easily deactivated as values may exist in different fields that are only allowed with extended material number The Long Material Number within the DIMP Add-On (Discrete Industries & Mill Products) The extension of the material number is a well-known requirement in SAP Business Suite requested by several customers. An Add-On solution was provided several years ago as part of the industry solution Discrete Industries & Mill Products (DIMP). The so-called DIMP LAMA-functionality is a part of the industry solution Automotive which is one component of the Add-On DIMP (Discrete Industries & Mill Products) 1. The industry solution DIMP is part of SAP S/4HANA, on-premise edition 1511, but the DIMP LAMAfunctionality with the long material number (LAMA) is not part of SAP S/4HANA. The reason is purely based on the fact that the material number is natively extended to 40 characters within SAP S/4HANA. 1 See SAP Note

23 A migration of the DIMP LAMA functionality to the native 40 character long material number within SAP S/4HANA is planned for a later release of SAP S/4HANA (and not available with SAP S/4HANA, on-premise edition 1511).Additional DIMP-specific information related to the Material Field Length extension: The material version functionality (available in the industry solution Discrete Industries & Mill Products) is not available with SAP S/4HANA, on-premise edition Manufacturer Part Number (MPN) is not available within SAP S/4HANA, on-premise edition ALE Change Pointers ALE change pointers related to Master Data Distribution (see SAP Help: LINK) have to be processed completely upfront to the move to SAP S/4HANA, on-premise edition They will no longer be available compatibly after conversion to SAP S/4HANA, on-premise edition SAP Notes and Restrictions related to Material Number Field Length Extension Conversion Pre-Checks related to Material Number Field Length Extension It s recommended to execute conversion pre-check (for details see SAP Note: ). For the conversion of selection variants see SAP Note for details. Custom Code related information See SAP Note: , Restrictions SAP S/4HANA, on-premise edition 1511 restriction note (general): Collection of restriction related to MFLE: o ALE generation for BAPIs: SAP Note o Extended Material Number in Suite Integration: SAP Note o Extended Material Number Display in Archived Data: SAP Note o Length of Customer and Supplier Material Number: SAP Note o Extended Material Number in LIS: SAP Note o Product Structure Browser: SAP Note o Characteristic Values in PLM: SAP Note

24 Simplification of Parameter Effectivity Description SAP S/4HANA, on-premise edition 1511, the field KZEFF in table MARA is not available anymore. The current setting KZEFF is such that the field will be hidden only from the UI, but still continue to be available in the database. However, Assign effectivity parameter values/ override change numbers (KZEFF) impacts the parameter effectivity in BOM explosion by providing a popup to manually overwrite validity parameters. Hence, the value of this field needs to be reset from X to space. This ensures similar behaviour in UI & in the backend Required and Recommended Action(s) Execute conversion pre-check Related SAP Notes Conversion Pre-Checks SAP Note: , Foreign Trade fields in Material Master Description The Foreign Trade functionality as part of Sales & Distribution is not available within SAP S/4HANA, on-premise edition The functional equivalent in SAP S/4HANA is SAP Global Trade Services (GTS). For more information see Simplification Item related to Foreign Trade in Sales & Distribution The below mentioned fields for Letter of Credit/ Legal control/ Export control/ Preference management in Foreign Trade is supported by GTS from S/4HANA 1511 release onwards and not through Material Master: CAP product list no. CAP prod. group Preference status Vendor decl. status Exemption Certificate Exemption Cert. No. Iss.date of ex.cert. Military goods Related SAP Notes General information about this Simplification Item SAP Note

25 MRP fields in Material Master Description The SAP S/4HANA simplification is done on the following tabs in transaction MM01/02/ Lot Size data in MRP1 Tab: unit of measure group is considered in only retail henceforth it is not required to switch it on in the material master. o Unit of Measure Group 2. Procurement in MRP2: MRP considers quota arrangements always, henceforth it is not required to switch it on in the material master. o Quota arr. usage. 3. BOM explosion /dependent Requirement tab in MRP4 o Selection Method 4. Repetitive manufacturing /assembly /deployment strategy tab of MRP4 o Action control o fair share rule o push distribution o Deployment horizon. 5. Storage Location in MRP4 o SLoc MRP indicator o spec.proc.type SLoc o Reoder Point o Replenishment qty. 6. Also the backend database fields for these "omitted functionality" remains existing in the system. For more information see simplification item in Production Planning Storage Location MRP Related SAP Notes General information about this Simplification Item SAP Note Material Type SERV Description Material type "SERV" for services is introduced for Product Master in S/4HANA for simplification purposes. When you use material type SERV, some fields and departments that are irrelevant in S/4 are hidden from the screen. This gives all transactions relevant for material master, a leaner and simplified look. Therefore, a new material type SERV (Service Materials) is created with reduced user departments and fields in the classical transactions: MM01/MM02/MM03 from SAP S/4HANA, on-premise edition 1511release onwards. 1. Supported user departments : o Accounting o Purchasing o Basic Data o Sales 25

26 2. The selected fields are hidden only from the material type "Service Materials" however they are supported for other material types. Below fields/tabs are not available for SERV: Basic data 1 EAN/ UPC EAN Category Product allocation Assign Effected vals Matl Grp Package Matls Basic data 2 Sales General/Plant Replacement part Availability check Material freight grp Shipping Data - Trans. Grp, LoadingGrp, Setup time, Proc. time, Base qty Packaging material data - Matl Grp Pack.Matls, Maximum level, Packaging mat. Type, Stack ability factor, Allowed pkg weight, Excess wt tolerance, Allowed pkg volume, Excess volume tol., Ref. mat. for pckg, Closed General plant parameter - Neg. stocks, SerialNoProfile, DistProf, SerializLevel, IUID-Relevant, External Allocation of UII, IUID Type Purchasing Material freight grp Other data - GR Processing time, Post to insp. stock, Critical Part, Source list, Quota arr. usage, JIT delivery sched. Accounting 1 VC: Sales order stk Price control nur Wert S Moving price Total Stock Proj. stk val. Class Total Value Valuated Un Accounting Previous Year (Button) o MovAvgPrice PP o Total stock o Total value PP Std cost estimate (Button) Accounting 2 26

27 Sales: Sales Org 1 X-distr. Chain status Valid from Dchain-spec status Valid from Min. dely qty Delivery Unit Sales: Sales Org 2 Matl statistics grp Product attributes - Product attribute 1/2/3/4/5/6/7/8/9/ Required and Recommended Action(s) Configurations required for SERV that are part of SET: 1. Material type SERV(Table T134, delivery class: G) 1. This attribute of SERV is provided by SET content 2. Screen sequence control(spro transaction: OMT3E 1. Table T133K Influencing Factors: Screen Sequence No. / Delivery Class: G 2. Tables T133S and T133T are also part of SET content Related SAP Notes General information about this Simplification Item SAP Note Product Catalog functionality for integration with Internet Application Components Description A subset of the Product Catalog functionality was used in the past as means of integration to the SAP ERP built in Online Store (related to IAC, Internet Application Components). As the built-in Online Store is not relevant anymore, this type of integration is not needed anymore. Hybris is the strategic solution to support web-channel processes, with the respective backend Integration Business Process related information Business Process related information for the current software Version: SAP ERP Online Store is not relevant anymore. Transaction not available in SAP S/4HANA on-premise edition 1511 WCU1 Maintain customer WCUM Maintain customer WW10 IAC product catalog WW20 IAC Online Store WW30 SD part for IAC MM-SD 27

28 Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Product Catalog Description Product Catalog functionality was used in the past as means of integration to web-channel solutions. Hybris is the strategic solution to support web-channel processes, with the respective backend Integration. Thus, Product Catalog functionality is not the target architecture Business Process related information Hybris is the strategic solution to support web-channel processes, with the respective backend Integration. Thus, Integration via Product Catalog is not the target architecture, but still available in SAP S/4HANA, on-premise edition Transaction not available in SAP S/4HANA on-premise edition 1511 WPC1 Prepare product catalog IDocs WPC2 Prepare item IDocs WPC3 Prepare catalog change IDocs WPC4 Prepare item change IDocs WPC5 Convert product catalog WWCD Product catalog: Display change docs. WWM1 Create product catalog WWM2 Change product catalog WWM3 Display product catalog WWM4 Copy product catalog WWM5 Delete product catalog Required and Recommended Action(s) None Object Identifier Type Code Description The field NO_CONVERSION is not available in the definition of object identifier type codes (also known as scheme IDs table MDGI_IDSTC_BS). Any existing usages have already been switched to non-conversion data elements in their key structures. In the "key mapping" IMG activity "Define Object Identifiers", the checkbox "No Conversion" was removed, as it was not considered any more. 2 Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional equivalent is available. 28

29 Business Process related information No influence on business processes expected Required and Recommended Action(s) None MDM 3.0 integration Description The MDM specific transaction codes for IDoc processing (inbound and extraction) are not available within SAP S/4HANA, on-premise edition Business Process related information MDM3.0 was discontinued, all known customer implementations have migrated to Netweaver MDM or Master Data Governance. All known customer implementations have already replaced the MDM specific IDoc processing according to SAP note "Tables MDMFDBEVENT, MDMFDBID, MDMFDBPR growing significantly" Transaction not available in SAP S/4HANA onpremise edition 1511 MDM_CLNT_EXTR "Local Extraction" Required and Recommended Action(s) None Related SAP Notes General SAP Note related to Simplification Item SAP Note: SRM Product Master Description The functional scope of SAP Supplier Relationship Management (SAP SRM) will gradually be made available within SAP S/4HANA. The related functions will become part of the procurement solution of SAP S/4HANA. Technically, the procurement solution within SAP S/4HANA is not a successor to the SAP SRM components. Therefore, the SAP SRM software components and SAP S/4HANA cannot be installed on the same system. For more details see Simplification Item Co-Deployment of SAP SRM. Accordingly the SRM Product Master is not available in SAP S/4HANA, on-premise edition

30 Business Process related information There is no influence on the business processes, as the SRM product master was not used in ERP functionality. Transaction not available in SAP S/4HANA onpremise edition 1511 COM_PR_MDCHECK COMC_MATERIALID_ALL COMC_PR_ALTID COMC_PR_ALTID_BSP COMC_PR_OBJ_FAM COMC_PR_OBJ_FAM1 COMC_PR_RFCDEST COMC_PRODUCT_IDX COMC_SERVICEID_ALL COMCMATERIALID COMCPRAUTHGROUP COMCPRD_BSP_ID COMCPRFORMAT COMCPRLOGSYS COMCPRMSG COMCPRTYPENRO COMCSERVICEID COMM_DEL_PRWB_USER COMM_EXTRSET COMM_HIERARCHY COMM_IOBJ_RECATEG COMM_MSG01 COMM_PRAPPLCAT COMM_PRDARC COMM_PROD_RECATEG COMMPR_PCUI COMMPR01 COMMPR02 CRM_PRODUCT_LOG CRM_PRODUCT_STA CRMCFSPRODID Required and Recommended Action(s) None 30

31 Logistics Batch Management Description The following transactions related to Logistics Batch Management are not available in SAP S/4HANA, onpremise edition 1511: MSC1, MSC2, MSC3 and MSC4. The functional equivalent in SAP S/4HANA, on-premise edition 1511 are the following transactions: MSC1N Create Batch MSC2N Change Batch MSC3N Display Batch MSC4N Display Change Documents for Batch As of Release 4.6A, the maintenance of batch master data has been completely reworked and assigned to new transaction codes. Already at this point in time it was recommended to use the new transaction codes (MSC*N). The previous transactions and with that the belonging program code are not available within SAP S/4HANA, on-premise edition Business Process related information No influence on the business process alternatively mentioned transaction codes need to be used. Transaction not available in SAP S/4HANA on-premise edition 1511 MSC1 MSC2 MSC3 MSC Business Partner IDOC Types (DEBMAS and CREMAS) Description The business partner related idoc message types - DEBMAS and CREMAS are not available with Sap S/4HANA, on-premise edition They are planned to be available in a future release of SAP S/4HANA, on-premise edition. In SAP Business Suite systems, DEBMAS was used to transfer data pertaining to customer master data, and CREMAS was used to transfer data pertaining to supplier master data. In SAP S/4HANA, on-premise edition master data (customer and supplier) must be created only by using business partner as the leading object Business Process related information If you try to transfer data using these message types in S/4HANA, data would be transferred without actually having created a business partner. If you want to perform a master transfer of data pertaining to customer or supplier, SAP recommends that you do so after contacting the S/4HANA Master Data team for Business Partner (DL STE_MD_BP <DL_5555B04B7BCF84913B000007@exchange.sap.corp>). 31

32 Classifications functionality of customer master Description In traditional ERP systems, you could classify customers using transactions for customer master data maintenance (using the menu Extras -> Classification). These transactions are not available in SAP S/4HANA, on-premise edition The available Business Partner related transaction BP does currently not support the functionality of classifications for customer master data in SAP S/4HANA, on-premise edition Sales & Distribution SD Simplified Data Models Description The following data model simplifications have been implemented for the SD area: Elimination of Status Tables VBUK, VBUP: Status fields have been moved to the corresponding header and item tables - VBAK and VBAP for sales documents, LIKP, and LIPS for deliveries, VBRK for billing documents Simplification of Document Flow table VBFA Field length extension of SD document category: Data element VBTYP (Char1) has been replaced by data element VBTYPL (Char4), also: elimination of field VBTYP_EXT (Char4) Elimination of redundancies Document Index Tables VAKPA, VAPMA, VLKPA, VLPMA, VRKPA, VRPMA Elimination of redundancies Rebate Index Table VBOX: see simplification item SD Rebate Optimization Key benefits of the data model changes: Reduced memory footprint (simplified Document Flow, elimination of index tables, fewer aggregates) Increased performance of HANA queries and code pushdown (one select statement instead of two select statements, easier join for header/items including status and business data) Increased robustness of Rebate processing (no redundancies due to aggregates) The changes are described in more detail in the guidelines attached to the related note Business Process related information No influence on business processes expected Required and Recommended Action(s) 1. Adapt customer coding according to the custom code check results, see Note for a detailed description. 2. If you have added one or more append structures to database tables VBUK or VBUP (document status header and item table) in the source release to store additional data for documents that are persistent 32

33 in tables VBAK/VBAP, LIKP/LIPS, or VBRK, and these fields are to be used in S/4HANA, you must ensure that the appended fields are added to the respective document tables. An append field to the document header status table VBUK must be added to one or several of the document header tables VBAK, LIKP, or VBRK. This decision depends on which of the document types the respective field is relevant for. An append field to document item status table VBUP must be added to one or more of the document item tables VBAP or LIPS. Again, the choice depends on which of the document types the respective field is relevant for. Each append field must have the same name and the same data type as it does in the source table, and each one has to be appended to the table-specific status include structure (DDIC structures VBAK_STATUS, LIKP_STATUS, VBRK_STATUS, VBAP_STATUS or LIPS_STATUS). Only then will the field be considered by the automatic data conversion from VBUK to VBAK/LIKP/VBRK and from VBUP to VBAP/LIPS, as well as by read function modules that can be used to replace direct SELECTs to the deprecated status tables VBUK/VBUP. Do not choose a different field name or data type. Do not append the field directly to the document table. It is possible to have several append structures for one status include structure. When do you have to add the append fields to the status include structures in order to have the data transferred automatically during the SAP S/4HANA transformation? In the development system, you have to add the fields during phase ACT_UPG, when you are prompted for SPDD. In all other systems, you may use modification adjustment transports or customer transport integration during the upgrade-like conversion. The append fields must be contained in one of the custom transport requests from the development system. The conversion pre-check class CLS4H_CHECKS_SD_DATA_MODEL delivered via Note provides a check for such append fields and issues a warning if such append fields are recognized in the source release. The warning refers to the necessary action to add the append fields to the status include structures Related SAP Notes Conversion Pre-Checks SAP Note Custom Code related Customer coding has to be adapted according to the cookbooks in the information Note Data Model Changes in SD Pricing Description Business documents within the SAP Business Suite such as the sales order or the purchase order used to store the pricing result in the database table KONV. In SAP S/4HANA, table KONV was replaced in its data persistency role by the new table PRCD_ELEMENTS. However, KONV is and can still be used for data declaration purposes. It still defines the structure of the pricing result within the application coding. The content of KONV is transferred to PRCD_ELEMENTS when moving to SAP S/4HANA; Within condition technique, the following DDIC changes and interface changes have been done: o DDIC changes: The concatenated variable key field VAKEY of a condition table has been removed from all condition header tables, including KONH (pricing), NACH (output 33

34 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. This has been done to avoid data migration of these tables as a result of the material number extension For internal processing, long data elements VAKEY_LONG and VADAT_KO_LONG with the length CHAR255 have been introduced The content of the new long VAKEY and VADAT can be determined at runtime using methods of the service class CL_COND_VAKEY_SRV Data element QUDIW (special value source in access sequence) has been extended from CHAR20 to CHAR50. Data element SKONDTAB (CHAR128, for archiving SD conditions) has been replaced by SDKONTAB_LONG (CHAR512). Data element KOND_DATA (used for general condition determination) has been extended from CHAR255 to CHAR512. o Interface changes: Batch input of price condition records (program RV14BTCI): For compatibility reasons, the field VAKEY_LONG (CHAR255) was added to the batch input structures. If this field is filled or used by external programs, then the content of this field is used instead of the content of the still existing field VAKEY. IDOC COND_A for price condition records: For compatibility reasons, the fields MATNR_LONG (CHAR40), UPMAT_LONG (CHAR40), BOMAT_LONG (CHAR40) and VAKEY_255 and VADAT_255 have been added to the COND_A IDOC segments. If these fields for the extended material number or long VAKEY/VADAT are to be filled in addition to the still existing short fields, then the content of the long fields has priority. Several data elements have been extended, especially the key field ZAEHK in the KONV with the data element DZAEHK The maximum number of possible accesses in an access sequence (DTEL KOLNR) has been increased from 99 to 999. Therefore, the solution described in SAP Pilot Note (only relevant for customers for which this note was released) is no longer necessary nor valid. Any content from this solution will automatically be transferred to the standard tables during the upgrade process to SAP S/4HANA Data Element Description Former Length New Length KOLNR, EVSNR, FSELNR Number of Access in Access Sequence NUMC2 NUMC3 KOBED, KOFRM, KOFRA, GRLNR KOFRS Pricing Formula and Requirement Number NUMC3 NUMC7 DZAEHK, DZAEHK_IND, DZAEKO, Condition Counter in Pricing Result NUMC2 NUMC3 BBP_ZAEHK 34

35 Data Element Description Former Length New Length GRLNR Group condition routine NUMC2 NUMC7 KALKS, KALVG Customer and document classification for pricing procedure determination CHAR1 CHAR2 The following elements in KONV have been changed in addition: Element Description Type of Change KOLNR3 Access Sequence - Access Number Field is obsolete. Possible field content will be merged with content of KOLNR and moved to PRCD_ELEMENTS STUFE WEGXX Level (in multi-level BOM explosions) Path (for multi-level BOM explosions) Field is obsolete and will not be transferred to PRCD_ELEMENTS Field is obsolete and will not be transferred to PRCD_ELEMENTS Business Process related information No influence on business processes expected Required and Recommended Action(s) Carefully follow the instructions in SAP Notes , , and SAP provides an automated migration to migrate data from the old database table KONV to the new database table PRCD_ELEMENTS. However, the document currency field WAERK of table PRCD_ELEMENTS needs to be filled with the currency of the related document header. To reduce downtime, it was decided to move this step to the post-processing phase. Within the automatic migration, the currency is filled with the technical currency '2' allowing the system to correctly convert PRCD_ELEMENT to KONV format and vice versa. However, to fill the currency consistently in accordance with the related document, SAP recommends that you run the post-processing report PRC_MIG_POST_PROCESSING as soon as possible. If you have added one or more append structures to database table KONV in the source release to store additional data, and these fields are to be used in S/4HANA, you must ensure that the appended fields are also added to the new database tables PRCD_ELEMENTS and PRCD_ELEM_DRAFT. Each append field must have the same name and the same data type as it does in the source table. When do you have to add the append fields to the tables PRCD_ELEMENTS and PRCD_ELEM_DRAFT? o In the development system, you have to add the fields to PRCD_ELEMENTS during phase ACT_UPG, when you are prompted for SPDD. 35

36 o This is necessary to ensure that the automatic data migration transfers the field content from KONV to PRCD_ELEMENTS during the upgrade-like conversion. The append fields to table PRCD_ELEM_DRAFT can be added later in the development system as this table is not relevant for the automated migration. In all other systems, you may use modification adjustment transports or customer transport integration during the upgrade-like conversion for the appends to both tables PRCD_ELEMENTS and PRCD_ELEM_DRAFT The append fields must be contained in one of the custom transport requests from the development system. The conversion pre-check delivered via Note provides a check for such append fields and issues a warning if such append fields are recognized in the source release. The warning refers to the necessary action to add the append fields to the new database tables Related SAP Notes General information Carefully follow the instructions in SAP Notes , , and Conversion Pre-Checks SAP Note: Pre-checks delivered with Note Custom Code related information SAP Note: Foreign Trade within SAP S/4HANA Description Currently there are two software services for international trade transactions: Foreign Trade and Global Trade Service. Foreign Trade is part of the normal SD. GTS is an external service that can be installed on an additional instance. With SAP S/4HANA on-premise edition 1511, the Foreign Trade functionality will be not available because SAP Global Trade Services (GTS) is the successor for the business requirement. For Intrastat a customer can leverage functionality within SAP S/4HANA, on-premise edition For the functionalities Letter of Credit; Legal Control and Preference Management the functionalities based on SAP Global Trade Services (GTS) can be used. SAP GTS can be natively integrated with S/4HANA. Additional functionalities for Import- and Export Management are available with SAP GTS Business Process related information The customer needs to check whether 3rd party Foreign Trade systems are in use for foreign trade processes. Because of the replaced foreign trade functionality in S/4HANA, it is possible that 3rd party Foreign Trade system will need adjustments by the respective 3rd party Solution/Service Provider. However, SAP GTS can be connected to S/4HANA to run the respective foreign trade processes. Transaction not available in SAP S/4HANA on-premise edition 1511 VX99 FT/Customs: General overview EN99 General Foreign Trade Processing VI09X Change FT Data in Purchasing Doc. VI08X Display FT data in purchasing doc. 36

37 VI80X Change FT Data in Goods Receipt VI79X Display FT Data in Goods Receipt VI77X Change FT Data in Outbound Delivery VI64X Display FT Data in Outbound Delivery VI14X Change FT Data in Billing Document VI10X Display FT Data in Billing Document VIIM FT: Op. Cockpit: Purchase order VIWE FT: Op. Cockpit: Goods Receipt VIEX FT: Journal Export Actual VE85 Change Statistical Value Import VE86 Display Statistical Value Import VE88 Change Statistical Value Export VE89 Display Statistical Value Export VE87 Change Stat.Value Subcontracting VEI3 Display Stat.Value Subcontracting OVE1 Commodity Code / Import code no. VXCZ INTRASTAT: Form - Czech Republic VXHU INTRASTAT: Form - Hungary VXPL INTRASTAT: Form Poland VXSK INTRASTAT: Form Slovakia VEBE INTRASTAT: XML File - Belgium VECZ INTRASTAT: File - Czech Republic VEHU INTRASTAT: File Hungary VEPL Create INTRASTAT CUSDEC EDI PL VESK Create INTRASTAT CUSDEC EDI SK VEIA Create INTRASTAT CUSDEC EDI SE VEIB Create INTRASTAT CUSDEC EDI PT VEID Create INTRASTAT CUSDEC EDI LU VEI0 Create INTRASTAT CUSDEC EDI IE VEI7 Create INTRASTAT CUSDEC EDI GB VEI8 Create INTRASTAT CUSDEC EDI AT VEI9 Create INTRASTAT CUSDEC EDI ES VE02 INTRASTAT: Create Form Germany VE03 INTRASTAT: Create File - Germany VE06 INTRASTAT: Paper Form Belgien VE07 Create INTRASTAT Form for France VE08 Create INTRASTAT File for Italy VE09 Create INTRASTAT file for Belgium VE10 Create INTRASTAT file for Holland VE11 Create INTRASTAT file for Spain VE12 Create INTRASTAT form for Holland VE15 Create disk - INTRA/EXTRA/KOBRA/VAR VE16 Create INTRASTAT form for Austria VE17 Create INTRASTAT form for Sweden VE32 INTRASTAT: Paper Form Ireland VE37 INTRASTAT: File - France VE33 INTRASTAT: Paper Form - U.K. 37

38 VE42 INTRASTAT: File - Denmark VE45 INTRASTAT: Paper Form Greece VE46 INTRASTAT: File - Finland VE95 Create INTRASTAT papers: Portugal VICZ Create INTRASTAT CUSDEC EDI CZ VIIE Create INTRASTAT XML IE VEFU Foreign Trade: Add INTRASTAT Data VIMM Decl. Recpts/Disptch Min. Oil Prod. VE96 EXTRASTAT Data Select.: Init. Screen VE04 EXTRASTAT: Data selection for export VE05 EXTRASTAT: Create File Germany VE97 Create EXTRASTAT tape: Netherlands VEXU Foreign Trade: Add EXTRASTAT Data VE13 KOBRA data selection: export Germany VE14 Create KOBRA file for Germany VE15 Create disk - INTRA/EXTRA/KOBRA/VAR VE21 VAR: Selection of bill. docs Switz. VE22 Create VAR form for Switzerland VE23 V.A.R.: File Switzerland VE18 SED data selection for USA exporter VE25 SED: Selection: USA Carriers VE19 Create SED form for USA VE20 Create AERP file for USA VE27 HMF: Selection USA VXJ1 MITI Declarations VXJ2 Declaration of ImportBill.Docs Japan VEIAI INTRASTAT Archiving VEIAE EXTRASTAT Archiving VE81 Check Report: General FT Data VE73 Goods Catalog: Create Document VE74 Goods Catalog: Create Diskette VXA5 Document. Payments: Print Monitoring VXA7 Documentary Payments: Simulation ENSV Data Service VX01N Create License VX02N Change License VX03N Display License VX22N Change License Data VX23N Display license data VE31 Blocked SD Documents VE30 Existing licenses VE29 Assigned Documents for Each License VE82 Check Report: Export Control Data VI83 Check Customer Master/Legal Control VX07 Simulation: License Check VX09 Simulation: Embargo Check VX08 Simulation: Boycott List Check 38

39 VX16 BAFA diskette: Selection VX17 Create BAFA diskette VX10 Countries of Destination for License VX05 Customers for License VX06 Export Control Classes for License VE56 Check Export Control for Consistency VI84 Doc.Payments: Check Customer Master VX14N Maintain Financial Document VX11N Create Financial Document VX12N Change Financial Document VX13N Display Financial Document VI73N Foreign Trade: Maintain Long-Term Vendor Declaration VI74N FT: Display Vendor Declaration VI78 Foreign Trade: Countries VI54 Customs Approval Numbers VI55 Approval Number per Plant VED1 Print Parameters for Export Documents OVE1 Commodity Code / Import Code Number VPAR Archiving Preference Logs VFAI Archiving INTRASTAT VFAE Archiving EXTRASTAT FTUS Foreign Trade: Maintain User Data ENCO Printing / Communication ENGK Legal Control ENLO Documentary payments ENPR Preference Processing ENGR Periodic Declarations ENSV Foreign Trade Data Maintenance ENZD Customs Objects: Documentation/Info. VOIM Check Import Purchase Order VOWE Check Goods Receipt VI09X Change Import Purchase Order VI53X Change Goods Receipt VOLI Check Export Delivery VOEX Check Export Billing Document VI77X Change Export Delivery VI14X Change Export Billing Document VI85 Check Report: Vendor Master VE81X Check Report: General Foreign Trade Data VE82X Check Report: Export Control Data VE83X Check Report: Preference Data VI86 Cross-plant Check of Foreign Trade Data VI82X Foreign Trade: Customer Master Consistency General VI83X Foreign Trade: Customer Master Consistency Control VI84X Foreign Trade: Customer Master Consistency - Letter of Credit VIE4 Periodic Declarations: Log of Incomplete Items 39

40 VE24X Foreign Trade: Information Commodity Code VI24X Foreign Trade: Information Import Code Number FTIM Journal: Purchase Orders FTGR Journal: Goods Receipts FTIM Import Order Analysis FTGR Import Gds Receipt Analysis FTEX Export Bill. Documents Journal FTEX Exp.bill.doc.analysis VE30 Expiring Licenses VE29 Sales Orders for a License VXA2 Financial Documents: List VXA1 Financial Documents: SD Documents VI74N Display Vendor Declaration CAAT Foreign Trade: Call up FT Atrium VIUL Foreign Trade: Data Upload VIBA Send IDoc Output-AES-Initial Procg VIBC Send IDoc Output-AES-Error in Procg VIBB Send IDoc Output-AES-Repeat Procg VIB7 Send IDoc Output - Initial Procg VIB9 Send IDoc Output - Error in Procg VIB8 Send IDoc Output - Repeat Procg VIB4 Print Transaction: Initial Procg VIB6 Print Transaction: Error in Procg VIB5 Print Transaction: Repeat Procg VIB3 Foreign Trade Output Status VEII SAPMSED8: Call IMPINV01 VEIE SAPMSED8: Call EXPINV02 VX00 Preference Handling LEAN Request long-term VendDecl. (vendor) LEMA Dun long-term vendor decl. (vendor) VE67 Aggregate Vendor Declarations LEER Create long-term VenDecl. (customer) VE55 Preference Determination: Individual VE54 Preference Determination: Collective VEB5 Calculate Assemblies Individually VEB6 Calculate Assemblies Collectively VEPR Customs log VE91 Display Preference Values VE90 Change preference values VE83 Check Report: Preference Data VE66 Preference Procedure VE65 Preference Reg./Percentage Rates VE64 Commodity Code/Customs Areas VE94 Load Commodity Code for EU Countries VEM4 Merge: EU - Commodity Code VI94 Load Import Code Nos - EU Countries VIM4 Merge: EU - Import Code Number 40

41 VA94 Load Commodity Codes for Japan VAM4 Merge: Japan - Commodity Code VP94 Load Import Code No. for Japan VPM4 Merge: Japan - Import Code Number VEU4 Load Commodity Code-Other Countries VEI4 Merge: Remaining Commodity Codes VIU4 Load Import Code No.-Other Countries VII4 Merge: Rest - Import Code Number VE24 Comm. Code Number Information (old) VI24 Code Number Information Import VI20 Display Customs Quota VI21 Display Pharmaceutical Products VI22 Display Customs Exemption VI23 Display Preferential Customs Duties VI19 Display Third-country Customs Duties VI18 Display Anti-dumping VXA3 Financial Documents: Blocked Docs VXA2 Existing Financial Documents VE68 Request Vendor Declarations VI75 Vendor Declarations - Dunning notice VE84 Monitoring: Purchasing Info Records VE83 Check Report: Preference Data VXSIM Simulate Import WZFT01 FT: Wizard - Declara. to Auth. (MM) WZFT02 FT: Wizard - Declara. to Auth. (SD) Required and Recommended Action(s) Analysis of all currently used foreign trade processes Related SAP Notes Conversion Pre-Checks SAP Note: Custom Code related information SAP Note: Credit Management Description The FI-AR-CR Credit Management is not available with SAP S/4HANA, on-premise edition The functional equivalent in SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR). This Sales & Distribution Simplification Item corresponds to the Simplification Item in Financials Area: Credit Management 41

42 Business Process related information You need to carry out a migration from FI-AR-CR to FIN-FSCM-CR. This migration has several elements: configuration data master data credit exposure data credit decision data SAP provides tools for support. Influence on Business Processes Generally, your business process will not change. However, you will need to use new transactions for certain use cases, because old transactions become obsolete. Examples: Maintenance of the credit account master data is not done through transaction FD32 anymore, but through transaction UKM_BP The release of credit blocked sales orders is not done through transaction VKM1, but through transaction UKM_MY_DCDS All IMG activities for credit management are listed under the IMG structure Financial Supply Chain Management Credit limit check for sales document types can only be specified as type D in SAP Credit Management, or left empty (no credit limit check). Credit limit check types A, B and C no longer work. Credit check on the basis of the maximum document value and credit check when changing critical fields have been removed from SD side. Transaction not available in SAP S/4HANA on-premise edition 1511 VKM2 Released SD Documents VKM3 Sales Documents VKM5 Deliveries F.31 Credit Management Overview F.32 Credit Management - Missing Data F.33 Credit Management - Brief Overview F.34 Credit Management - Mass Change FCV3 Early Warning List FD24 Credit Limit Changes FD32 Change Customer Credit Management (But FD33 "Display Customer Credit Management" is available in SAP S/4HANA, on-premise edition 1511) FDK43 Credit Management - Master Data List S_ALR_ Display Changes to Credit Management S_ALR_ Credit Master Sheet Required and Recommended Action(s) Required Action: Customers need to eliminate the usages of SAP objects in their own code that are indicated by note

43 If FI-AR-CR Credit Management was used on the start release, a migration to FIN-FSCM-CR Credit Management is mandatory. The necessary migration steps need to be performed after the technical downtime of the conversion. The migration steps are available as IMG activities under the IMG paths Migration from SAP ERP to SAP Accounting powered by SAP HANA --> Preparations and Migration of Customizing --> Preparatory Activities and Migration of Customizing for Credit Management and Migration from SAP ERP to SAP Accounting powered by SAP HANA --> Migration --> Credit Management Migration Related SAP Notes Custom Code related information SAP Note: ERP SD Revenue Recognition Description The" ERP SD Revenue Recognition" (see SAP Help: Link) is not available within SAP S/4HANA. The newly available "SAP Revenue Accounting and Reporting" functionality should be used instead. The new functionality supports the new revenue accounting standard as lined out in IFRS15 and adapted by local GAAP's. The migration to the new solution is required to comply with IFRS15 even if no upgrade to S/4HANA is done Business Process related information SD Revenue Recognition is not available in S/4HANA. None of the "SD-Revenue Recognition" functionality will work in S/4HANA. For sales orders or contracts that were processed by "SD-Revenue Recognition" and are not migrated to "SAP Revenue Accounting and Reporting", this includes: Realize deferred revenue Realize revenue before invoice posting Defer revenue at invoice posting Check SD-Revenue Recognition data consistency Cancel SD-Revenue Recognition postings Transaction not available in SAP S/4HANA on-premise edition 1511 VF42 "Update Sales Documents" VF43 "Revenue Recognition: Posting Doc" VF44 "Revenue Recognition: Work list" VF45 "Revenue Recognition: Revenue Report" VF46 "Revenue Recognition: Cancellation" VF47 "Revenue Recognition: Consistency Check" VF48 "Revenue Recognition: Compare Report" 43

44 Required and Recommended Action(s) Prior to the Conversion to S/4HANA, you need to migrate all sales order and contracts processed by "SD- Revenue Recognition" to "SAP Revenue Accounting and Reporting" that are not fully delivered and invoiced have deferred revenue still to be realized for which you expect follow-on activities like increase quantity, create credit memo or cancel invoice Please note that the Release 1.1 of "SAP Revenue Accounting and Reporting" does not include the full functional capabilities of SD-Revenue Recognition. Examples of not available functionalities in SAP S/4HANA, on-premise edition 1511 are: Revenue Recognition Type D (billing based): Invoice cap and exchange rate per invoice are not available. Call off Orders: While SD-Contracts are supported call of orders are not available. If you are using "SD-Revenue Recognition" you need to evaluate if a migration to "SAP Revenue Accounting and Reporting" is possible for your business before you decide to Conversion to S/4HANA. More details about the migration to "SAP Revenue Accounting and Reporting" can be found in the migration chapter of the online help: RevAcc Help and in the administrator guide for product "SAP SD Integration with SAP Revenue Accounting and Reporting": Admin Guide Integration SD Related SAP Notes Conversion Pre-Checks SAP Note: Custom Code related information SAP Note: Optimization of SD Rebate Processing for TPM Customers Description Customers, who will integrate their existing CRM TPM scenario with S/4HANA, still have to use SD Rebate Processing, even though a successor is already being provided by Settlement Management (cp. simplification item SD Rebate Processing replaced by Settlement Management). For those customers, the existing SD Rebate functionality is optimized with regard to the data base footprint. For this purpose, from a technical standpoint, the rebate index table VBOX is not available Business Process related information Please note, that also TPM customers are not able to create new rebate agreements in S/4HANA or extend existing ones (cp. simplification item SD Rebate Processing replaced by Settlement Management). However, for the TPM process this is not necessary at all, since for this business process rebate agreements are created by CRM TPM. Transaction not available in SAP VBO1 Create Rebate Agreement 44

45 S/4HANA on-premise edition 1511 VB(D Extend Rebate Agreements Required and Recommended Action(s) If the customer is using the extended SD rebate processing a rebuild of the S469 content is required after the upgrade. The customer has to maintain new customizing settings Related SAP Notes Custom Code related information SAP Note: Simplification in SD Analytics Description Simplification in SD analytics follows the overall analytics strategy in SAP S/4HANA, on-premise edition 1511 (see CT_ANAN - Analytics): Instead of prebuilt aggregates and/or redundant data for analytical purposes, the SAP S/4HANA Analytics approach is based on ODATA and Open CDS (aka ABAP-managed CDS = Core Data Services) directly on top of the original database. Corresponding analytics content will be provided within SAP S/4HANA. This content will grow over time. CDS Basic Views representing the Core Entities in SD The SD specific business objects Sales Order, Customer Invoice, Outbound Delivery and many others on top of the database tables VBAK, LIKP and VBRK are represented by CDS views that encompass the access of the analytics CDS queries to the database in a uniform manner. This is achieved by offering semantical field names and associations to connected business objects such as Customer, Material, etc. The complete analytics content will be built on top of these core entities. Incoming Sales Orders and Sales Volume based on CDS Views The first delivered analytics content consists of two CDS queries "Incoming Sales Orders" and "Sales Volume" that exemplify the capabilities of S/4HANA to report directly on the database without any prebuilt aggregates, with the possibility to make use of all dimensions for grouping, aggregation and filtering on the fly. New persistent fields in the database To make effective use of the SAP S/4HANA capabilities for SD Analytics, there are new persistent fields in the database (which, in the past, were only calculated on the fly): Sales Order Open Delivery Quantity and Amount (on schedule line level - VBEP) Sales Order Requested Quantity in Base Unit (on item level - VBAP) Allowance for using BW and LIS/SIS 3 Customers are allowed to extract data from SAP S/4HANA, on-premise edition 1511 to their own BW-Hub and 3 Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional equivalent is available. 45

46 to make extended use of the LIS/SIS 4 tool, as long as the CDS based approach in SD is not yet available in a comparable standard Business Process related information No influence on business processes expected. Transaction not available in SAP S/4HANA on-premise edition 1511 VA06 Sales Order Monitor Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Advanced Order Processing and Billing for Contractors to the public sector Description The functionality Advanced Order Processing and Billing for Contractors to the public sector is not available in SAP S/4HANA (and not on the roadmap) Business Process related information Customers using Advanced Order Processing and Billing for Contractors to the public sector in ERP and are planning to move to SAP S/4HANA, have to remodel their business processes accordingly. Transaction not available in SAP S/4HANA on-premise edition 1511 VACB Customizing t-codes: Advanced Order Processing and Billing /CBAD/ /CBAD/ /CBAD/ /CBAD/ /CBAD/ /CBAD/ /CBAD/ /CBAD/ /CBAD/ Note: If you use a material number longer than 18 characters - see restriction note Extended Material Number in LIS: SAP Note

47 /CBAD/ /CBAD/ /CBAD/ Related SAP Notes Custom Code related information SAP Note: Operational Data Provisioning Description Operational Data Provisioning in SD (see SAP Help: Link) is not available within SAP S/4HANA. Simplification in SD Analytics follows the overall analytics strategy in SAP S/4HANA, on-premise edition 1511 (see Simplification Item SD Analytics): The SAP S/4HANA Analytics approach is based on ODATA and Open CDS (aka ABAP-managed CDS = Core Data Services) directly on top of the original database. Corresponding analytics content will be provided within SAP S/4HANA. This content will grow over time. Successor: HANA Analytics CDS Basic Views representing the Core Entities in SD The SD-specific business objects Sales Order, Customer Invoice, Outbound Delivery and many others on top of the database tables VBAK, LIKP and VBRK are represented by CDS views that encompass the access of the analytics CDS queries to the database in an uniform manner by offering semantical field names and associations to connected business objects as Customer, Material, and so on. The complete analytics content will be built on top of these core entities Business Process related information No influence on business processes expected Required and Recommended Action(s) If operational or analytical reporting is requested, it is recommended that the customer starts evaluating the use of HANA Analytics Related SAP Notes Custom Code related information SAP Note:

48 Business Role Internal Sales Representative Description The business role "Internal Sales Representative" (ISR) was originally built to support the sales representative that works in close relationship with customers and logistical and financial departments collaborating with sales. This role became available with SAP ERP 6.0 and was enhanced in SAP ERP EhP4 and SAP ERP EhP5. Two options to run this role were possible either through the SAP Portal or by using the Business Client (as part of SAP NetWeaver). In S/4HANA the business role "Internal Sales Representative" (ISR) is not available within SAP S/4HANA, on-premise edition This also includes the POWLs (Personal Object Work Lists). Instead a set of new FIORI roles, e.g. SAP_BR_INTERNAL_SALES_REP are offered as successor. As a first step, those roles offer a basic set of transactions that are typically needed for the day-to-day work of a sales representative. During the next releases those roles will be further enhanced with custom-made apps based on FIORI. More information about this new concept can be found in note Business Process related information Transaction not available in SAP S/4HANA on-premise edition 1511 VPW1 VPWL Required and Recommended Action(s) Adaption to the new FIORI role concept Change View "Tasks" Change View "Maintain Portal Targets" Related SAP Notes Custom Code related information SAP Note: Webshops by Internet Sales or Web Channel Experience Management Description Web shops based on SAP Internet Sales (SAP ISA) or SAP Web Channel Experience Management (SAP WCEM) are not available in SAP S/4HANA. From a technical point of view, those components require TREX and IPC. Both components, however, are not available in SAP S/4HANA. From a strategic point of view, the required web shop functionality based on S/4HANA backend will be provided by SAP hybris e-commerce in a future release Business Process related information Customers that use SAP Internet Sales (SAP ISA) or SAP Web Channel Experience Management (SAP WCEM) and are planning to move to S/4HANA, have to remodel their business processes accordingly or wait for an appropriate future release, which supports SAP hybris e-commerce. Transaction not available in SAP S/4HANA on-premise edition 1511 Transactions ISA_CAT_REPLICATION Replication of product catalogs to TREX ISA_CAT_REPL_DELETE ISA: Deletion of indices created by product catalog replication 48

49 Also the following customizing t-code are not available: S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EB5_ S_EBJ_ S_EBJ_ S_EBS_ S_EBS_ S_EBS_ S_EBS_ S_EBS_ S_EBS_ S_EBS_ S_EBS_ Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Commodity Management Sales Description Commodity Sales is switched off technically in SAP S/4HANA, on-premise edition A successor is planned for a future release of SAP S/4HANA, on-premise edition The deactivated main functional building blocks are: Commodity Pricing through Commodity Pricing Engine (CPE & CPF) Basis Handling Integration of Commodity Features into Sales Documents Differential & Final Billing in Sales Integration of Sales into Commodity Risk Management 49

50 Day End / Month End Processing Commodity Analytics (Position Reporting & Mark to Market) Business Process related information The sales processes are not yet supported by commodity management functions Required and Recommended Action(s) None Related SAP Notes Conversion Pre-Checks The central pre-transformation check will check the deactivated CM Business Functions. Check if the Commodity Business Functions are active if yes, the upgrade with active Commodity Management Business Functions to SAP S/4HANA, on-premise edition 1511is not possible. The following Commodity Management Business Functions have been deactivated in SAP S/4HANA, on-premise edition 1511: Business Functions: Commodity Sales LOG_CPE_SD_MM LOG_CPE_FA_FE LOG_SD_COMMODITY LOG_SD_COMMODITY_02 LOG_SD_COMMODITY_03 LOG_SD_COMMODITY_04 General Information SAP Note: Sales Activities Description Sales Support: Computer-Aided Selling (SD-CAS) - see SAP Help LINK is not available within SAP S/4HANA onpremise edition, because it is not the target architecture. It is recommended to use SAP CRM on-premise (sideby-side with SAP S/4HANA) or SAP Cloud for Customer Business Process related information Sales Support is no longer available in SAP S/4HANA. The creation of new business documents or editing of migrated business documents is not possible. Transaction not available in SAP S/4HANA on-premise edition 1511 OV/8 OV/9 OV1Z Test Data - Transfer Data - Cond. Display Test Data Define Product Allocation Procedure 50

51 OV2Z Define Product Allocation Object OV3Z Determine Prod. Allocation Hierarchy OV5Z Maintain Consumption Periods OV7Z Create Characteristics for Rem.Alloc OV8Z Check Settings OV9Z Suitable Statistical Structures OVBR Assignment to Item Category OVBS Rule Table for Determining Dates OVCB Structure of Reporting View OVCC Assign View to User OVCD Definition of Reporting View OVCE Control Update of Perform.Measures OVCF Control Reporting - Info Blocks OVCI C SD Set Workflow Action box OVL5 Maintain Transit Time SDCAS_MCQ Call MC/Q From Address Selection V+01 Create Sales Call V+02 Create Telephone Call V+03 Create Sales Letter V+11 Create Direct Mailing V+21 Create Sales Prospect V+22 Create Competitor V+23 Create Business Partner VC_2 Customer Fact Sheet PDF Version VC/2 Customer Master Data Sheet VC/A Sales Activity Description 01 VC/B Sales Activity Description 02 VC/C Sales Activity Description 03 VC/D Sales Activity Description 04 VC/E Sales Activity Description 05 VC/F Sales Activity Description 06 VC/G Sales Activity Description 07 VC/H Sales Activity Description 08 VC/I Sales Activity Description 09 VC/J Sales Activity Description 10 VC01 Create Sales Activity VC Only Follow-up Activities VC Do not Delete Mail. Camp.+Addresses VC Internet mailing VC01N Edit Sales Activity VC01N_DRAG_KONTAKT Edit Sales Activity 51

52 VC01N_DRAG_MAILING Edit Sales Activity VC01N_M Edit Mailing VC02 Change Sales Activity VC05 Sales support monitor VC06 Parallel Processing for Address List VC10 Report Tree - Select Addresses VC10_BMENU Area Menu for VC10 VC15 Crossmatching VCR1 Competitive products VCU3 Display Incompletion Log VIM6 Customer Exits: Data Selection VMG1 Create Material Group 1 VMG2 Create Material Group 2 VMG3 Create Material Group 3 VMG4 Create Material Group 4 VMG5 Create Material Group 5 VN05 No.Assignment for Address List(SSup) VN06 Create No.Interval-Sales Activities VOC1 Customizing for List of Addresses VUC2 Maintain Incompletion Log VV51 Create Output for Sales Activity VV52 Change Output: Sales Activity VV53 Display Output: Sales Activity VVCB Maintain Activity Authorization Required and Recommended Action(s) If sales support functionality is requested, we recommend that customers start evaluating a side-by-side CRM on-premise scenario, or that they use Cloud for Customer Related SAP Notes Custom Code related information SAP Note: Billing Document Output Management Description With SAP S/4HANA a new Output Management approach is in place. By design, the new output management includes cloud qualities such as extensibility enablement, multi tenancy enablement and modification free configuration. Therefore, the complete configuration differs from the configuration that is used when output management is based on NAST. The configuration is based on BRF+ which is accessible for Customers. In SAP S/4HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For the form 52

53 determination rules (along with other output parameters) BRF+ functionality is used (in this sense in combination with the message determination). Output management based on NAST is not available for new documents in SD Billing. Billing documents that are migrated from legacy systems and for which NAST based output has been determined, can be processed with this technology. For all new billing documents the new output management is used. Therefore in Sales & Distribution in the area billing / customer invoice there is a need to adapt the configuration settings related to Output Management. In application Billing it is recommended to use Adobe Forms but due to compatibility the form technologies known from Business Suite (like SmartForms, SapScript) are supported as well. This is also true for the print reports. In contrast to the output management based on NAST the new output management supports only the Channels PRINT, , XML and IDOC (for on premise). Other channels are not available by default. Additional information to the new output management in SAP S/4HANA, on-premise edition 1511can be found in the cross topics simplification item Output Management Business Process related information In cases where there is not customer specific configuration for the new output management in the area of SD Billing, it will be not possible to print billing documents or to send billing documents via or XML Required and Recommended Action(s) None SD Rebate Processing replaced by Settlement Management Description In general, SD Rebate Processing is not available within SAP S/4HANA. The functional equivalent in SAP S/4HANA is SD Rebate Processing is Settlement Management. However, there is one exception. CRM TPM customers can still use SD Rebate Processing for their business process, but have to adapt to a SAP S/4HANA optimized solution (cp. simplification item Optimization of SD Rebate Processing for TPM Customers) Business Process related information In SAP S/4HANA, Settlement Management replaces SD Rebate Processing, which means that existing rebate agreements can only be processed up until the end of the validity date of the agreement and must then be closed by a final settlement. New agreements can only be created based on condition contracts. Therefore, the corresponding transaction codes VBO1 resp. VBD for the creation of rebate agreements is not available any more. Transaction not available in SAP S/4HANA on-premise edition 1511 VBO1 VB(D Create Rebate Agreement Extend Rebate Agreements 53

54 Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Miscellaneous minor functionalities in SD Area Description SAP ERP contains in a lot of cases several versions of the same or similar functionality, e.g. SAPGUI transactions or BAPI function modules. Older versions are marked as deprecated or obsolete, but are still avaiable for compatibility reasons. In SAP S/4HANA, on-premise edition 1511, for many of such objects only the most recent and most comprehensive version is available. Deprecated versions have been are disabled. In the SD area, a couple of deprecated BAPI function modules and SAPGUI transactions have been disabled. SAP Note contains a list of objects not available within SAP S/4HANA and, if available, the respective successor object Business Process related information No influence on business processes expected Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Industry-Specific SD Complaint Handling Description The industry specific SD complaints handling in ERP is not available within SAP S/4HANA, on-premise edition The functional equivalent to be used is the standard SD complaints handling (Transaction CMP_PROCESSING) Business Process related information The industry specific SD complaints handling is related to business function LOG_SD_EACOMPLAINTS. Customers having this business function active in SAP Business Suite start system can convert to SAP S/4HANA, on-premise edition However, independently from the activation status of the business function LOG_SD_EACOMPLAINTS, the corresponding functionality is not available in SAP S/4HANA, on-premise edition Customers with business function LOG_SD_EACOMPLAINTS not active in SAP Business Suite start release are not able to activate the business function after the 54

55 conversion to SAP S/4HANA, on-premise edition This business function is defined as obsolete in SAP S/4HANA. Transaction not available in SAP S/4HANA on-premise edition 1511 WCMP_PROCESSING Complaints Processing WCMP_MASS Mass Complaints Processing Customer Number WCMP_RESULT Results Display for Mass Complaints Processing Required and Recommended Action(s) None Related SAP Notes Custom Code related information See SAP Note SD FI/CA Integration with distributed systems Description The integration between Contract Accounts Receivable and Payable (FI-CA) and Sales and Distribution (SD), when using each component in separate systems, is not yet available in SAP S/4HANA, on-premise edition The FI-CA within SAP S/4HANA on-premise edition 1511, however, can be used as before. The system conversion to SAP S/4HANA on-premise edition 1511 will be blocked for customers, which have activated the Business Function LOG_SD_FICA_DISTRIBUTED in their ERP system. Therefore, as a prerequisite for the system conversion, the customer has to deactivate the (reversible) Business Function LOG_SD_FICA_DISTRIBUTED in his ERP system Business Process related information Customers that used the integration between FI-CA and SD in a distributed scenario, and are planning to move to S/4HANA, have to use the FI-CA within S/4HANA. Transaction not available in SAP S/4HANA onpremise edition 1511 Customizing t-codes: S_EBJ_ Required and Recommended Action(s) In case a customer used the integration between FI-CA and SD in a distributed scenario in ERP and decides to use the FI-CA within S/4HANA instead Related SAP Notes Custom Code related information See SAP Note

56 2.1.3 Customer Service Customer Interaction Center (CIC) Description Transaction CIC0 provides a basic Call Center help desk application which is technically outdated and not available within SAP S/4HANA. CRM on Premise, Cloud 4 Service and SAP Hybris provide state of the art successors for interaction center help desk use cases Business Process related information Business processes that require a help desk / call center integration cannot be executed in the customer interaction center any more. Instead they have to be integrated into the interaction center / help desk applications offered by CRM on Premise, Cloud 4 Service or SAP Hybris. Transaction not available in SAP S/4HANA on-premise edition 1511 CIC Required and Recommended Action(s) Business processes that require a help desk / call center integration should be integrated into the interaction center / help desk applications offered by CRM on Premise, Cloud 4 Service or SAP Hybris Related SAP Notes Custom Code related information See SAP Note Procurement Co-Deployment of SAP SRM Description The functional scope of SAP Supplier Relationship Management (SAP SRM) will gradually be made available within SAP S/4HANA. The related functions will become part of the procurement solution of SAP S/4HANA. In the first release of SAP S/4HANA, on-premise edition a limited functional scope might be available compared to SAP SRM. The coverage will grow over time. Technically, the procurement solution within SAP S/4HANA is not a successor to the SAP SRM components. Therefore, the SAP SRM software components and SAP S/4HANA cannot be installed on the same system. Technically, it is not a co-deployment, but in the future the procurement solution will evolve to take over the SAP SRM functions Business Process related information Customers with SAP SRM and SAP Business Suite on one server need to re-implement the procurement processes on the SAP S/4HANA, on-premise edition system which have been used on SAP Business Suite source 56

57 release within the SAP SRM installation. It is not possible to install the SAP SRM software components within the SAP S/4HANA stack. The functional scope of the new procurement solution available with the first release of SAP S/4HANA is not identical with the SAP SRM functions Required and Recommended Action(s) Perform Conversion pre-check to identify the constellation on SAP Business Suite start release Related SAP Notes Conversion Pre-Checks SAP Note: Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC) Description The goal is that - over time - the functional scope of SAP Supplier Lifecycle Management (SAP SLC) will be available within the SAP S/4HANA stack. Customers who have deployed SAP Supplier Lifecycle Management on SAP ERP and want to migrate to S/4HANA can continue to use those parts of the SAP SLC functionality that have been integrated into the S/4HANA Core and are referred to as "Supplier and Category Management". For the functional differences, see simplification item Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes. Customers who have been using a standalone SAP SLC system can continue to use it, but have to use MDG-S for supplier data integration. For more information, see simplification item Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes Business Process related information The functional scope of Supplier and Category Management in SAP S/4HANA is currently not identical with the SAP SLC functionalities. Master categories in purchasing category are not available. As a successor, material groups are available in purchasing categories Required and Recommended Action(s) Perform the Conversion pre-check to identify the state of the SAP ERP before the conversion to SAP S/4HANA Related SAP Notes Conversion Pre-Checks SAP Note: Implementation Description

58 Vendor evaluation based on LIS Description The current vendor evaluation based on Logistics Information System (LIS 5 ) is still available with SAP S/4HANA, on-premise edition 1511, but is not considered the target architecture 6. We recommend that you use the SAP HANA reporting capabilities for vendor evaluation based on CDS views and smart business technology Business Process related information The current functions are unchanged within SAP S/4HANA, on-premise edition No influence on business processes expected Required and Recommended Action(s) We recommend that you use the SAP HANA reporting capabilities for vendor evaluation based on CDS views and smart business technology Related SAP Notes Custom Code related information SAP Note: Subsequent Settlement - Vendor Rebate Arrangements Description In SAP S/4HANA, the Subsequent Settlement (MM-PUR-VM-SET) application is replaced by the new Contract Settlement (LO-GT-CHB) application. For this reason, the functional scope of subsequent settlement has been restricted, that is, in SAP S/4HANA, it is no longer possible to: Create new rebate arrangements using transaction MEB1 or Extend existing rebate arrangements using transactions MEBV / MEB7 / MEBH Additionally, as a consequence of the material field length extension in the SAP S/4HANA landscape, the structure of table S111 was adjusted. This can have some impact if the business volume data has to be rebuilt in the SAP S/4HANA system Business Process related information In SAP S/4HANA, Contract Settlement replaces Subsequent Settlement, which means that existing rebate agreements can only be processed up until the end of the validity date of the agreement and must then be closed by a final settlement. Afterwards new agreements can only be created based on condition contracts. 5 Note: If you use a material number longer than 18 characters - see restriction note Extended Material Number in LIS: SAP Note Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional equivalent is available. 58

59 Furthermore, if recompilation of the business volume data in SAP S/4HANA, on-premise edition 1511 is required, the index table S111 has to be rebuilt as described in SAP Note (Subseq.settl.: Retrospec.compltn/recompltn of busin.vol.data). Transaction not available in SAP S/4HANA on-premise edition 1511 MEB1; MEB7; MEBV, MEBH Required and Recommended Action(s) In SAP S/4HANA there are no direct activities required for continuing the business process for subsequent settlement, with the only exception that the agreements have to be closed after the end of the validity period. If a recompilation of the business volume data is required, the table S111 has to be rebuilt with the report RMEBEIN3 as described in note Related SAP Notes Conversion Pre-Checks SAP Notes: , Related SAP Notes SAP Note: ERP Shopping Cart Description The SAP ERP shopping cart function is not available within SAP S/4HANA, on-premise edition 1511 and will be replaced by S/4HANA Self Service Procurement. The shopping cart function in SAP Business Suite is associated to the business function LOG_MM_SSP_1. The business function LOG_MM_SSP_1 needs to be in status OFF in the start release Business Process related information Transaction not available in SAP S/4HANA on-premise edition 1511 /SRMERP/BRFP_DSS_SC /SRMERP/BRFP_DS_APPR /SRMERP/BRFP_DS_SC /SRMERP/BRFP_FOOTY /SRMERP/BRFP_FOO_TYP /SRMERP/BRFP_MATGRP /SRMERP/BRFP_MOV_TYP SRMERP/BRFP_PROC_L /SRMERP/BRFP_PROC_S /SRMERP/BRFP_PURGRP /SRMERP/DISPLAY_LOGS /SRMERP/SC_ARCHIVING /SRMERP/SNUM /SRMERP/WF_GEN /SRMERP/WDA_I_CAT_ADAPTER /SRMERP/WDA_I_DSS_DS /SRMERP/WDA_I_SC_ESS 59

60 /SRMERP/WDA_I_SC_FS_ESS /SRMERP/WDA_I_SC_ITM_ESS /SRMERP/WDA_I_WSCP /SRMERP/WDA_I_WSCP_ADMIN /SRMERP/WF_TRACE Required and Recommended Action(s) Business function LOG_MM_SSP_1 needs to be in status OFF in the start release Related SAP Notes Custom Code related information SAP Note: Internet Application Components (IAC) Description As of SAP S/4HANA the Materials Management (MM) Internet Application Components (IAC) is not available in SAP S/4HANA, on-premise edition Transaction not available in SAP S/4HANA on-premise edition 1511 MEW0 Procurement Transaction MEW1 Create Requirement Request MEW2 Status Display: Requirement Requests MEW3 Collective Release of Purchase Reqs. MEW5 Collective Release of Purchase Order MEW6 Assign Purchase Orders WEB MEWP Web based PO Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: MDM Catalog Description The SAP SRM MDM catalog is replaced by the catalog search function as part of S/4HANA Self Service Procurement. In the first release of SAP S/4HANA, on-premise edition a limited functional scope might be available compared to the SAP SRM MDM catalog. An available SAP SRM MDM catalog instance can still be integrated with S/4HANA as a punch-out catalog via OCI. 60

61 Business Process related information S/4HANA Self Service Procurement must be used instead of the SAP SRM MDM catalog, the content of which needs to be imported into S/4HANA via OCI5 ( Catalog content will be managed as part of S/4HANA Self Service Procurement Required and Recommended Action(s) None Pricing Data Model Simplification Description See information provided in Sales & Distribution area in simplification item Data Model Changes in SD Pricing. These information are basically relevant as well for the pricing in procurement Business Process related information See simplification item Data Model Changes in SD Pricing Required and Recommended Action(s) See simplification item Data Model Changes in SD Pricing Related SAP Notes General information Carefully follow the instructions in SAP Notes , , and Conversion Pre-Checks SAP Note: Pre-checks delivered with Note Custom Code related information SAP Note: Output Management Adoption in Purchase Order Description With SAP S/4HANA a new Output Management approach is in place. By design, the new output management includes cloud qualities such as extensibility enablement, multi tenancy enablement and modification free configuration. Therefore, the complete configuration differs from the configuration that is used when output management is based on NAST. The configuration is based on BRF+ which is accessible for Customers. In SAP S/4HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For the form determination rules (along with other output parameters) BRF+ functionality is used (in this sense in combination with the message determination). 61

62 Output management based on NAST is no longer supported for new documents in purchase order. Purchase orders which are migrated from legacy systems and for which NAST based output has been determined, can be processed with this technology. For all new purchase orders the new output management is used. Therefore in Procurement for purchase order there is a need to adapt the configuration settings related to Output Management. In purchase order it is recommended to use Adobe Forms but due to compatibility the form technologies known from Business Suite (like SmartForms, SapScript) are supported as well. This is also true for the print reports. In Purchase order processing it is recommended to use Adobe Forms but due to compatibility the form technologies known from Business Suite (like SmartForms, SapScript) are supported as well. This is also true for the print reports. In contrast to the output management based on NAST the new output management supports only the Channels PRINT, , XML (for Ariba Network Integration) and IDOC (for on premise). Other channels are not supported by default. Additional information to the new output management in SAP S4/HANA can be found in the general simplification item related to Output Management (Cross Topic Area) Business Process related information Output Management for Purchase Order has to be configured. In cases where there is not customer specific configuration for the new output management for purchase orders, it will not be possible to print purchase orders or to send purchase orders via or XML MM-PUR WebDynpro Applications Description WebDynpro Applications of SAP ERP Materials Management (MM) are not available with SAP S/4HANA, onpremise edition 1511any more. The corresponding functionality is replaced with existing SAP GUI transactions, Fiori applications or Smart Business within SAP S/4HANA, on-premise edition The coverage of Fiori applications will grow over time Business Process related information ABAP Web Dynpro Applications not available in SAP S/4HANA. WebDynpro Application Description SAP S/4HANA Replacement 62

63 MMPUR_CPPR_MAIN_APPL MMPUR_SPPR_MAIN_APPL Collective Processing of Purchase Requisition Purchase Requisition Processing MMPUR_ACCOUNT_ASSIGN_COMP Account assignments MMPUR_ADDRESS_COMP Display Address SAP GUI report BBP_EXTREQ_TRANSFER, Fiori Application SAP GUI transaction ME51N, Fiori Application MMPUR_BWLAUNCHER_APP BW Starter Smart Business? BW Integration? MMPUR_CFOLDERS_EP_EVENT MMPUR_CFOLDERS_URL_APP MMPUR_DISPLSCHEDLINE_APP MMPUR_DOCTRK_APP MMPUR_DOC_TRACE MMPUR_FINDSUPPLIER_COMP MMPUR_FORECAST_APP Document Storage Document Storage Display of Delivery Schedule Lines for Item Document Tracing Graphical document tracing Find Supplier Expected Contract Release Orders Smart Business? MMPUR_MAVERICK_APP Maverick Buying Analysis Smart Business? MMPUR_PRICECOND_APP MMPUR_RELEASEDOC_APP MMPUR_REL_STRAT_APP MMPUR_SRCOFSUPPLY_APP MMPUR_UI_PR_APP MMPUR_VNDCONF_APP MMPUR_VNDCTCDTA_APP MMPUR_VNDPARTNER_APP Pricing Conditions Contract Release Order Release Strategy Display Sources of Supply Purchase Requisition Processing Process Different Vendor Confirmations Display of Vendor Contact Data Including Contact Persons Display of Partner Roles of a Vendor Related SAP Notes Custom Code related information SAP Note: Classic MM-PUR GUI Transactions replacement Description Classic SAP ERP Materials Management (MM) transactions and BAPIs for the business objects Purchase Order, Purchase Requisition, and Supplier Invoice have been replaced by the corresponding transactions and BAPIs made available with SAP R/3 Enterprise With SAP S/4HANA, on-premise, these classic MM transactions and BAPIs will no longer be available. The replacements that are available since SAP R/3 Enterprise 4.70 shall be used. 63

64 Business Process related information No influence on business processes expected Transaction not available in SAP S/4HANA on-premise edition 1511 BAPIs not available SAP S/4HANA onpremise edition 1511 ME21 ME22 ME23 ME24 ME25 ME26 ME27 ME28 ME51 ME52 ME53 ME54 ME59 MR01 MR1M BAPI_PO_CREATE BAPI_REQUISITION_CREATE BAPI_PO_GETDETAIL Required and Recommended Action(s) See SAP notes: : FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc : Replacing MR01 / Functions of MR1M (Release 4.6) Related SAP Notes Custom Code related information SAP Notes: : FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc : Replacing MR01 / Functions of MR1M (Release 4.6) Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes Description The following processes of SAP Supplier Lifecycle Management (SAP SLC) are not available within SAP S/4HANA, on-premise edition 1511: - All sell-side processes: Supplier Registration and Supplier Data Maintenance - Several buy-side processes: Supplier Hierarchies, Supplier Classification, Area of Validity in Supplier Evaluation, Supplier Qualification, Certificate Management, External Tasks in Activity Management 64

65 Business Process related information The functional scope of Supplier and Category Management in SAP S/4HANA is currently not identical with the SAP SLC functionalities Required and Recommended Action(s) We recommend that you evaluate on a project basis whether you want to use Supplier and Category Management in SAP S/4HANA or whether you want to use SAP SLC as a standalone system to leverage the full functional scope of SAP SLC Related SAP Notes Conversion Pre-Checks Pre-check required to guide customers who have installed SAP SLC and SAP ERP on one server. See Simplification Item Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC) for details Supplier Distribution via MDG-S Description After the conversion of SAP ERP to S/4HANA, customers who have been using SAP SLC as a standalone system communicating with SAP ERP have to use MDG-S (Master Data Governance for Suppliers) for supplier distribution Business Process related information SAP S/4HANA leverages MDG-S for supplier distribution. The MDG-S license is not part of the SAP S/4HANA license Required and Recommended Action(s) A project needs to be set up to implement MDG-S for supplier distribution Related SAP Notes Custom Code related information If customers have enhanced interfaces for point-to-point supplier distribution from SAP SLC to SAP ERP using the SLC integration component in SAP ERP, communication with MDG-S must be enhanced accordingly Authority Concept for Supplier Invoice Description The previous concept was based on checking header data against the item authorization object for all items. The system checked for all items if a user was allowed to complete certain activities in the plants. 65

66 With the new concept, the behaviour of the system is more comprehensive. The new concept introduces a header authorization object that enables the system to perform the following authorization checks: Check header data against the header authorization object (M_RECH_BUK). This authorization object checks the common activities a user performs for the header company code. Check item data against the item authorization object (M_RECH_WRK). This authorization object checks the common activities a user performs for the plant for the respective item Business Process related information No influence on business processes expected Required and Recommended Action(s) You must edit the user roles. Users working with supplier invoices, additionally need the authorizations based on M_RECH_BUK. The standard roles delivered with SAP S/4HANA contain this new authorization object. If the customer roles are derived from these standard roles, you must do the following: Edit the values of the organizational levels for the new authorization object M_RECH_BUK. Regenerate the profiles related to the roles using PFCG. If you have created a role by yourself, you must manually insert the authorization object M_RECH_BUK into the role. You can do this preliminary work once SAP S/4HANA is available Foreign Trade within SAP S/4HANA Procurement Description Currently there are two software services for international trade transactions: Foreign Trade and SAP Global Trade Services (GTS). Foreign Trade is part of standard Materials Management (MM). SAP GTS is an external service that can be installed on a separate instance. With SAP S/4HANA on-premise edition 1511, the foreign trade solution will be not available because SAP Global Trade Services is the successor for the business requirement. For Intrastat a customer can leverage functionality within SAP S/4HANA, on-premise edition Additional functions for import and export management are available with SAP GTS Business Process related information The customer needs to check whether 3rd party foreign trade systems are in use for foreign trade processes. Because of the replaced foreign trade functionality in S/4HANA, it is possible that 3rd party foreign trade system will need adjustments by the respective 3rd party Solution/Service Provider. However, SAP GTS can be connected to S/4HANA to run the respective foreign trade processes. 66

67 Transaction not available in SAP S/4HANA on-premise edition 1511 VX99 FT/Customs: General overview EN99 General Foreign Trade Processing VI09X Change FT Data in Purchasing Doc. VI08X Display FT data in purchasing doc. VI80X Change FT Data in Goods Receipt VI79X Display FT Data in Goods Receipt VI77X Change FT Data in Outbound Delivery VI64X Display FT Data in Outbound Delivery VI14X Change FT Data in Billing Document VI10X Display FT Data in Billing Document VIIM FT: Op. Cockpit: Purchase order VIWE FT: Op. Cockpit: Goods Receipt VIEX FT: Journal Export Actual VE85 Change Statistical Value Import VE86 Display Statistical Value Import VE88 Change Statistical Value Export VE89 Display Statistical Value Export VE87 Change Stat.Value Subcontracting VEI3 Display Stat.Value Subcontracting OVE1 Commodity Code / Import code no. VXCZ INTRASTAT: Form - Czech Republic VXHU INTRASTAT: Form - Hungary VXPL INTRASTAT: Form Poland VXSK INTRASTAT: Form Slovakia VEBE INTRASTAT: XML File - Belgium VECZ INTRASTAT: File - Czech Republic VEHU INTRASTAT: File Hungary VEPL Create INTRASTAT CUSDEC EDI PL VESK Create INTRASTAT CUSDEC EDI SK VEIA Create INTRASTAT CUSDEC EDI SE VEIB Create INTRASTAT CUSDEC EDI PT VEID Create INTRASTAT CUSDEC EDI LU VEI0 Create INTRASTAT CUSDEC EDI IE VEI7 Create INTRASTAT CUSDEC EDI GB VEI8 Create INTRASTAT CUSDEC EDI AT VEI9 Create INTRASTAT CUSDEC EDI ES VE02 INTRASTAT: Create Form Germany VE03 INTRASTAT: Create File - Germany VE06 INTRASTAT: Paper Form Belgien VE07 Create INTRASTAT Form for France VE08 Create INTRASTAT File for Italy VE09 Create INTRASTAT file for Belgium VE10 Create INTRASTAT file for Holland VE11 Create INTRASTAT file for Spain VE12 Create INTRASTAT form for Holland VE15 Create disk - INTRA/EXTRA/KOBRA/VAR VE16 Create INTRASTAT form for Austria 67

68 VE17 Create INTRASTAT form for Sweden VE32 INTRASTAT: Paper Form Ireland VE37 INTRASTAT: File - France VE33 INTRASTAT: Paper Form - U.K. VE42 INTRASTAT: File - Denmark VE45 INTRASTAT: Paper Form Greece VE46 INTRASTAT: File - Finland VE95 Create INTRASTAT papers: Portugal VICZ Create INTRASTAT CUSDEC EDI CZ VIIE Create INTRASTAT XML IE VEFU Foreign Trade: Add INTRASTAT Data VIMM Decl. Recpts/Disptch Min. Oil Prod. VE96 EXTRASTAT Data Select.: Init. Screen VE04 EXTRASTAT: Data selection for export VE05 EXTRASTAT: Create File Germany VE97 Create EXTRASTAT tape: Netherlands VEXU Foreign Trade: Add EXTRASTAT Data VE13 KOBRA data selection: export Germany VE14 Create KOBRA file for Germany VE15 Create disk - INTRA/EXTRA/KOBRA/VAR VE21 VAR: Selection of bill. docs Switz. VE22 Create VAR form for Switzerland VE23 V.A.R.: File Switzerland VE18 SED data selection for USA exporter VE25 SED: Selection: USA Carriers VE19 Create SED form for USA VE20 Create AERP file for USA VE27 HMF: Selection USA VXJ1 MITI Declarations VXJ2 Declaration of ImportBill.Docs Japan VEIAI INTRASTAT Archiving VEIAE EXTRASTAT Archiving VE81 Check Report: General FT Data VE73 Goods Catalog: Create Document VE74 Goods Catalog: Create Diskette VXA5 Document. Payments: Print Monitoring VXA7 Documentary Payments: Simulation ENSV Data Service VX01N Create License VX02N Change License VX03N Display License VX22N Change License Data VX23N Display license data VE31 Blocked SD Documents VE30 Existing licenses VE29 Assigned Documents for Each License VE82 Check Report: Export Control Data 68

69 VI83 Check Customer Master/Legal Control VX07 Simulation: License Check VX09 Simulation: Embargo Check VX08 Simulation: Boycott List Check VX16 BAFA diskette: Selection VX17 Create BAFA diskette VX10 Countries of Destination for License VX05 Customers for License VX06 Export Control Classes for License VE56 Check Export Control for Consistency VI84 Doc.Payments: Check Customer Master VX14N Maintain Financial Document VX11N Create Financial Document VX12N Change Financial Document VX13N Display Financial Document VI73N Foreign Trade: Maintain Long-Term Vendor Declaration VI74N FT: Display Vendor Declaration VI78 Foreign Trade: Countries VI54 Customs Approval Numbers VI55 Approval Number per Plant VED1 Print Parameters for Export Documents OVE1 Commodity Code / Import Code Number VPAR Archiving Preference Logs VFAI Archiving INTRASTAT VFAE Archiving EXTRASTAT FTUS Foreign Trade: Maintain User Data ENCO Printing / Communication ENGK Legal Control ENLO Documentary payments ENPR Preference Processing ENGR Periodic Declarations ENSV Foreign Trade Data Maintenance ENZD Customs Objects: Documentation/Info. VOIM Check Import Purchase Order VOWE Check Goods Receipt VI09X Change Import Purchase Order VI53X Change Goods Receipt VOLI Check Export Delivery VOEX Check Export Billing Document VI77X Change Export Delivery VI14X Change Export Billing Document VI85 Check Report: Vendor Master VE81X Check Report: General Foreign Trade Data VE82X Check Report: Export Control Data VE83X Check Report: Preference Data VI86 Cross-plant Check of Foreign Trade Data VI82X Foreign Trade: Customer Master Consistency General 69

70 VI83X Foreign Trade: Customer Master Consistency Control VI84X Foreign Trade: Customer Master Consistency - Letter of Credit VIE4 Periodic Declarations: Log of Incomplete Items VE24X Foreign Trade: Information Commodity Code VI24X Foreign Trade: Information Import Code Number FTIM Journal: Purchase Orders FTGR Journal: Goods Receipts FTIM Import Order Analysis FTGR Import Gds Receipt Analysis FTEX Export Bill. Documents Journal FTEX Exp.bill.doc.analysis VE30 Expiring Licenses VE29 Sales Orders for a License VXA2 Financial Documents: List VXA1 Financial Documents: SD Documents VI74N Display Vendor Declaration CAAT Foreign Trade: Call up FT Atrium VIUL Foreign Trade: Data Upload VIBA Send IDoc Output-AES-Initial Procg VIBC Send IDoc Output-AES-Error in Procg VIBB Send IDoc Output-AES-Repeat Procg VIB7 Send IDoc Output - Initial Procg VIB9 Send IDoc Output - Error in Procg VIB8 Send IDoc Output - Repeat Procg VIB4 Print Transaction: Initial Procg VIB6 Print Transaction: Error in Procg VIB5 Print Transaction: Repeat Procg VIB3 Foreign Trade Output Status VEII SAPMSED8: Call IMPINV01 VEIE SAPMSED8: Call EXPINV02 VX00 Preference Handling LEAN Request long-term VendDecl. (vendor) LEMA Dun long-term vendor decl. (vendor) VE67 Aggregate Vendor Declarations LEER Create long-term VenDecl. (customer) VE55 Preference Determination: Individual VE54 Preference Determination: Collective VEB5 Calculate Assemblies Individually VEB6 Calculate Assemblies Collectively VEPR Customs log VE91 Display Preference Values VE90 Change preference values VE83 Check Report: Preference Data VE66 Preference Procedure VE65 Preference Reg./Percentage Rates VE64 Commodity Code/Customs Areas 70

71 VE94 Load Commodity Code for EU Countries VEM4 Merge: EU - Commodity Code VI94 Load Import Code Nos - EU Countries VIM4 Merge: EU - Import Code Number VA94 Load Commodity Codes for Japan VAM4 Merge: Japan - Commodity Code VP94 Load Import Code No. for Japan VPM4 Merge: Japan - Import Code Number VEU4 Load Commodity Code-Other Countries VEI4 Merge: Remaining Commodity Codes VIU4 Load Import Code No.-Other Countries VII4 Merge: Rest - Import Code Number VE24 Comm. Code Number Information (old) VI24 Code Number Information Import VI20 Display Customs Quota VI21 Display Pharmaceutical Products VI22 Display Customs Exemption VI23 Display Preferential Customs Duties VI19 Display Third-country Customs Duties VI18 Display Anti-dumping VXA3 Financial Documents: Blocked Docs VXA2 Existing Financial Documents VE68 Request Vendor Declarations VI75 Vendor Declarations - Dunning notice VE84 Monitoring: Purchasing Info Records VE83 Check Report: Preference Data VXSIM Simulate Import WZFT01 FT: Wizard - Declara. to Auth. (MM) WZFT02 FT: Wizard - Declara. to Auth. (SD) Required and Recommended Action(s) Analysis of all currently used foreign trade processes Related SAP Notes Custom Code related information SAP Note: Commodity Management Procurement Description Commodity Procurement is switched off technically in SAP S/4HANA, on-premise edition A successor is planned for a future release of SAP S/4HANA, on-premise edition The deactivated main functional building blocks are: 71

72 Commodity Pricing via Commodity Pricing Engine (CPE & CPF) Basis Handling Integration of Commodity Features into Procurement Documents Differential & Final Invoicing in Procurement Integration of Procurement into Commodity Risk Management Day End / Month End Processing Commodity Analytics (Position Reporting & Mark to Market) Business Process related information Commodity Management cannot be activated. The procurement processes are not yet supported by commodity management functions Required and Recommended Action(s) None Related SAP Notes Conversion Pre-Checks The central pre-transformation check will check the deactivated CM Business Functions. Check if the Commodity Business Functions are active if yes, the System Conversion with active Commodity Management Business Functions to SAP S/4HANA on-premise edition 1511 is not possible. The following Commodity Management Business Functions have been deactivated in SAP S/4HANA, on-premise edition 1511: Business Functions: Commodity Procurement LOG_CPE_SD_MM LOG_CPE_FA_FE LOG_MM_COMMODITY LOG_MM_COMMODITY_02 LOG_MM_COMMODITY_03 LOG_MM_COMMODITY_04 General Information SAP Note: Automatic Document Adjustment Description In SAP S/4HANA, the following differences to the process of automatic document adjustment apply: 1. The direct entry function is activated per default for all document categories to simplify the creation of worklist entries. 2. The field length of the Material Number data element (MATNR) is 40 characters. As a consequence, the field length of data element 'VAKEY' is enhanced and the database tables WIND and S111 have also been adjusted. 72

73 Business Process related information 1. In SAP S/4HANA, the indicator for direct entry is set now automatically during the update process of conditions. This means that: When a user saves a condition change - including the creation of a new condition - an entry is made in the worklist (table WIND) for all document categories with valid Customizing settings. For worklist creation, the transaction MEI4 can no longer be used. For more information, please see SAP Note (Conversion of the procedure for Worklist creation). Note also that change pointers do not have to be updated for message type CONDBI if direct entries are activated. With the conversion to the 'direct entry' procedure, you can deactivate the update of change pointers if you do not use it for other purposes 2. Rebuilding business data volume (tables WIND and S111) SAP recommends that you process all open worklist entries completely before conversion to SAP S/4HANA. In this case, no activities for automatic document adjustment are required after the system conversion process If the worklist cannot be completed in the SAP ERP system, you can proceed with the procedure described in section 'Required and Recommended Actions on Start Release. Transaction not available in SAP S/4HANA on-premise edition 1511 MEI4 - Create Worklist Required and Recommended Action(s) If in the ERP system the worklist could not be completely processed, a rebuilding of the worklist for automatic document adjustment is required in SAP S/4HANA, on-premise edition > please follow in this case the following procedure: Delete the content for automatic document adjustment of table S111 ( Report RMEBEIN6 (transaction MEI6)) and Delete the content of table WIND ( Report RMEBEIN5 (transaction MEI5) Rebuild the table entries for S111 and WIND for the used document categories by using the appropriate setup reports (see below). Make sure that the filter selection for rebuilding the S111 entries is meaningful by selecting the appropriate organizational criteria ( time, org data, docnr,...) [Rebuild is in SAP S/4HANA] Doc. category Description Report for rebuilding S111 and WIND entries 01 Purchase Order RMEBEIN3 02 Scheduling Agreement RMEBEIN3 10 Sales Price Calculation RWVKP Sales Price Calculation Index RWVKP Customer billing document RMEBEIL3 73

74 30 Vendor billing document RMEBEIL3 31 Expense document RMEBEIL3 32 Vendor settlement document RMEBEIV3 35 Remuneration list RMEBEIL3 40 Vendor settlement request RMEBEIZ3 50 Assortment List RMEBEIN3 55 POS-Outbound RMEBEIN3 60 Customer settlement RMEBEIK3 If you want to process multiple applications in one step (subsequent settlement and automatic document adjustment), you can also use report RMCENEUA Related SAP Notes Conversion Pre-Checks SAP Notes: , Logistics AB Agency Business Description Simplification of DB Key Fields and tables structures (WBRL,WBRRE, WBRF, WBRFN and WBRP) Replacement of concatenated fields by corresponding new fields in mentioned DB tables (Details mentioned notes below) Replaced fields are moved to the dynamical part of the communication structures to avoid runtime errors and to ensure the same system behaviour as before All redundant transaction and reports or business processes where replaces by one unified set of transaction, reports and business processes Business Process related information The application simplification offers now for each business process step one single transaction instead of many. Redundant functionalities were combined into one transaction or business process. This will help to streamline each single business step and to reduce unnecessary complexity by eliminating of similar business processes steps. The Remuneration Request List is not available within SAP S/4HANA. The functional equivalent in SAP S/4HANA is the Extended Remuneration List offers the same business capability as well. This means that the customizing of the Extended Remuneration List has to be set up to ensure that the same documents are created. The replacement of the Remuneration List by the extended one can be done before or after the system conversion to SAP S/4HANA, on-premise edition Details about the system configuration kind be found in the note:

75 The Standard Settlement Methods to generate Settlement Documents is not available win SAP S/4HANA. The functional equivalent in SAP S/4HANA is the New Settlement Method. The System will adjust all documents which were created with reference to standard settlement method and the customizing data automatically. So you have to process the documents with respect to the business process steps of the new settlement method. Details about the system configuration kind be found in the note: Transaction Codes and Reports not available in SAP S/4HANA Here you will find a list of all transactions or reports which are not available within SAP S/4HANA and the corresponding successor transactions or reports (see also note ). Obsolete Report RWLF1001 RWLF1002 Obsolete Report Title Billing docs (header data) Billing documents (with item data) Obsolete Tcode Successor Report Successor Report Title Successor Tcode WLFB RWLF1051 List Output Settlement WLI2 Management Documents WLFC RWLF1051 List Output Settlement WLI2 Management Documents RWLF1003 Settlement Document Lists (Header Information) WLFD RWLF1051 List Output Settlement Management Documents WLI2 RWLF1004 RWLF1005 Settlement Document Lists (With Item Data) Settlement Requests (Header Information) WLFE RWLF1051 List Output Settlement Management Documents WLFG RWLF1051 List Output Settlement Management Documents WLI2 WLI2 RWLF1006 RWLF1007 RWLF1008 Settlement Requests (With Item Data) Settlement Request Lists (Header Data) Settlement Request List (Item Data) WLFH RWLF1051 List Output Settlement Management Documents WLFO RWLF1051 List Output Settlement Management Documents WLFP RWLF1051 List Output Settlement Management Documents WLI2 WLI2 WLI2 RWLF1009 RWLF1010 RWLF1011 RWLF1012 RWLF1013 RWLF1014 Customer Settlement Lists (Header Data) Customer Settlement Lists (With Item Data) Display Relevant Payment Documents for Settlement Doc List Creation Display Relevant Billing Documents for Creation of Settlem. Doc Lists Display Relevant Customer Settlement Lists for Settl Doc List Creation Customer Settlement (Header Information) WLFQ RWLF1051 List Output Settlement Management Documents WLFR RWLF1051 List Output Settlement Management Documents WLRA WLRB WBLRB S_AL0_ RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL RWLF1051 Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) List Output Settlement Management Documents WLI2 WLI2 WLFSLRL WLFSLRL WLFSLRL WLI2 75

76 RWLF1015 RWLF1016 Customer Settlement (With Item Data) Expenses Settlement (Header Information) S_AL0_ S_AL0_ RWLF1051 RWLF1051 List Output Settlement Management Documents List Output Settlement Management Documents WLI2 WLI2 RWLF1017 RWLF1018 RWLF1019 RWLF1050 RWLF1052 RWLF1CHD RWLF1KO1 RWLF1KO2 RWLF1KO3 RWLF1KO4 Expenses Settlement (With Item Data) Display Customer Settlements for Settlement Document List Creation Relevant Expenses Settlements for Settlement Document List Creation List Output Single Documents List Output List Documents Display Change Document for Settlement Management Documents Conditions for Settlement Requests (Vendor) Conditions for Settlement Request Lists Conditions for Settlement Document Lists Conditions for Settlement Requests (Customer) S_AL0_ S_AL0_ S_AL0_ RWLF1051 RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL List Output Settlement Management Documents Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) WLI1 RWLF1051 List Output Settlement Management Documents WLI3 RWLF1051 List Output Settlement Management Documents RWLF_CHANGE_D OCUMENTS RWLF1051 RWLF1051 RWLF1051 RWLF1051 Display Change Documents List Output Settlement Management Documents List Output Settlement Management Documents List Output Settlement Management Documents List Output Settlement Management Documents WLI2 WLFSLRL WLFSLRL WLI2 WLI2 WLF_CHANGE_DO CUMENTS WLI2 WLI2 WLI2 WLI2 RWLF1KO5 RWLF2001 RWLF2002 Conditions for Customer Settlement List Documents Mass Release of Settlement Documents to Accounting Mass Cancellation of Settlement Requests RWLF1051 List Output Settlement Management Documents WLFF RWLF2056 Mass Release of Settlement Management Documents WLFI RWLF2055 Mass Cancellation of Settlement Management Documents WLI2 WAB_RELEASE WAB_CANCEL RWLF2003 Mass Cancellation of Billing Documents WLFJ RWLF2055 Mass Cancellation of Settlement Management Documents WAB_CANCEL RWLF2004 RWLF2005 Mass release of billing documents to accounting Mass Release of Remuneration Lists to Accounting WLFK RWLF2056 Mass Release of Settlement Management Documents WLFL RWLF2056 Mass Release of Settlement Management Documents WAB_RELEASE WAB_RELEASE RWLF2006 Generate Settlement WLFM RWLF9039 Create Settlement Document WLF_RRLE_CREAT 76

77 RWLF2007 RWLF2008 RWLF2009 Document Lists from Vendor Billing Documents Generate Remuneration Lists from Payment Documents Mass Release of Settlement Request Lists to Accounting Mass release of posting lists to Accounting Lists WLFN RWLF9039 Create Settlement Document Lists WRL4 RWLF2056 Mass Release of Settlement Management Documents WBL4 RWLF2056 Mass Release of Settlement Management Documents E WLF_RRLE_CREAT E WAB_RELEASE WAB_RELEASE RWLF2010 Create posting lists from preceding documents WBLR RWLF2052 Generate Customer Settlement Lists from Settlement Documents WBLRN RWLF2011 RWLF2012 Create Settlement Document Lists from Customer Settlement Lists Complete Settlement Request Lists WLFV RWLF9039 Create Settlement Document Lists WLFW RWLF2057 Mass Completion of Settlement Management Documents WLF_RRLE_CREAT E WAB_CLOSE RWLF2013 RWLF2014 RWLF2016 RWLF2018 RWLF2019 RWLF2020 Mass Release of Customer Remuneration Lists to Financial Accounting Create Customer Settlements for Settlement Requests Create Remuneration Lists from Customer Settlements Mass Release of Customer Settlements for Financial Accounting Mass Cancellation of Settlement Request Lists Mass Cancellation of Customer Settlements WLFLK RWLF2056 Mass Release of Settlement Management Documents S_AL0_ S_AL0_ S_AL0_ S_AL0_ S_AL0_ RWLF2051 RWLF9039 RWLF2056 RWLF2055 RWLF2055 Generate Customer Settlements from Settlement Documents Create Settlement Document Lists Mass Release of Settlement Management Documents Mass Cancellation of Settlement Management Documents Mass Cancellation of Settlement Management Documents WAB_RELEASE WLF1K WLF_RRLE_CREAT E WAB_RELEASE WAB_CANCEL WAB_CANCEL RWLF2021 RWLF2022 RWLF2023 RWLF2024 Mass Cancellation of Remuneration Lists Mass Cancellation of Customer Settlement Lists Mass Price Determination for Settlement Request Lists Mass Price Determination for Payment Documents S_AL0_ S_AL0_ S_AL0_ S_AL0_ RWLF2055 RWLF2055 RWLF2054 RWLF2054 Mass Cancellation of Settlement Management Documents Mass Cancellation of Settlement Management Documents Mass Pricing for Settlement Management Documents Mass Pricing for Settlement Management Documents WAB_CANCEL WAB_CANCEL WAB_PRICING WAB_PRICING RWLF2025 Create Remuneration S_AL0_96000 RWLF9039 Create Settlement Document WLF_RRLE_CREAT 77

78 RWLF2026 RWLF2027 Lists from Expense Settlements Mass Release of Expense Settlements for Financial Accounting Mass Cancellation of Expense Settlement 333 Lists E S_AL0_ S_AL0_ RWLF2056 RWLF2055 Mass Release of Settlement Management Documents Mass Cancellation of Settlement Management Documents WAB_RELEASE WAB_CANCEL RWLF2028 RWLF2029 RWLF2030 RWLF2031 RWLF2032 RWLF2033 RWLF2034 RWLF2059 RWLF2059 D Complete Settlement Requests Complete Vendor Billing Documents Create Settlement Request Lists from Preceding Documents Complete Expenses Settlements Reopen Settlement Requests Reopen Vendor Billing Documents Reopen Expenses Settlements Generate Posting Lists from Settlement Requests Dispatcher: Create Posting Lists S_AC0_ S_AC0_ RWLF2057 RWLF2057 Mass Completion of Settlement Management Documents Mass Completion of Settlement Management Documents WRLV RWLF2053 Generate Vendor Settlement Lists from Settlement Documents S_AC0_ S_AC0_ S_AC0_ S_AC0_ RWLF2057 RWLF2058 RWLF2058 RWLF2058 Mass Completion of Settlement Management Documents Mass Reopening of Settlement Management Documents Mass Reopening of Settlement Management Documents Mass Reopening of Settlement Management Documents WBLRO RWLF2052 Generate Customer Settlement Lists from Settlement Documents WBLRO_DISP RWLF2052D Dispatcher: Create Customer Settlement Lists WAB_CLOSE WAB_CLOSE WRLVN WAB_CLOSE WAB_REOPEN WAB_REOPEN WAB_REOPEN WBLRN WBLRN_DISP RWLF2060 RWLF2061 RWLF4001 RWLF4002 RWLF4003 RWLF4004 RWLF4005 Generate Customer Settlements from Settlement Requests Create Settlement Lists from Settlement Requests Delete Archived Vendor Billing Documents from the Database Delete Archived Customer Settlement Lists from Database Delete Archived Settlement Document Lists from Database Delete Archived Settlement Documents from Database Delete Archived Vendor Settlement Lists from Database WLF1KO RWLF2051 Generate Customer Settlements from Settlement Documents WRLVO RWLF2053 Generate Vendor Settlement Lists from Settlement Documents WACLFR WLF_DEL Archiving Vendor Billing Docs and Vendor Settlements: Delete Program WACBLR WBU_DEL Archiving Customer Settlement Lists: Delete Program WACLRR WRECH_DEL Archiving Settlement Document Lists: Delete Program WACZRR WZR_DEL Archiving Settlement Documents: Delete Program WACRLR WREG_DEL Archiving Vendor Settlement Lists: Delete Program WLF1K WRLVN 78

79 RWLF4006 RWLF4007 RWLF7001 RWLF7002 RWLF7003 RWLF7004 RWLF7005 RWLF9002 RWLF9003 RWLF9004 RWLF9005 RWLF9006 RWLF9007 RWLF9008 RWLF9009 RWLF9010 RWLF9011 RWLF9012 Delete Archived Customer Settlements from Database Delete Archived Expense Settlements from Database Display Document Flow of Vendor Billing Documents Display Document Flow for Customer Settlement Lists Display Document Flow for Settlement Document Lists Display Document Flow for Settlement Document Display Document Flow for Vendor Settlement Lists Generate Extended Remuneration Lists From Payment Documents Create Extended Remuneration Lists From Posting Lists Settlement Documents for Application Status Vendor Settlement Lists for Application Status Generate Remuneration Lists from Vendor Billing Documents Generate Remuneration Lists From Customer Settlements Generate Remuneration Lists From Expense Settlements Relevant Payment Documents For Extended Remuneration List Creation Relevant Customer Settlements For Extended Remuneration List Creation Relevant Posting Lists For Extended Remuneration List Creation Relevant Expense Settlements for Extended Remuneration List Creation WACCIR WCI_DEL Archiving Customer Settlements: Delete Program WACSIR WSI_DEL Archiving Expense Settlements: Delete Program WFL1 RWLF1051 List Output Settlement Management Documents WFL2 RWLF1051 List Output Settlement Management Documents WFL3 RWLF1051 List Output Settlement Management Documents WFL4 RWLF1051 List Output Settlement Management Documents WFL5 RWLF1051 List Output Settlement Management Documents S_ALN_ S_ALN_ RWLF9039 RWLF9039 Create Settlement Document Lists Create Settlement Document Lists WAPZR RWLF1051 List Output Settlement Management Documents WAPRL RWLF1051 List Output Settlement Management Documents S_ALN_ S_ALN_ S_ALN_ S_ALN_ S_ALN_ S_ALN_ S_ALN_ RWLF9039 RWLF9039 RWLF9039 RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL Create Settlement Document Lists Create Settlement Document Lists Create Settlement Document Lists Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) WLI2 WLI2 WLI2 WLI2 WLI2 WLF_RRLE_CREAT E WLF_RRLE_CREAT E WLI2 WLI2 WLF_RRLE_CREAT E WLF_RRLE_CREAT E WLF_RRLE_CREAT E WLFSLRL WLFSLRL WLFSLRL WLFSLRL 79

80 RWLF9013 RWLF9014 RWLF9015 RWLF9016 RWLF9017 RWLF9018 RWLF9019 RWLF9020 RWLF9021 RWLF9022 RWLF9023 RWLF9024 RWLF9028 RWLF9029 RWLF9030 RWLF9031 RWLF9032 Relevant Vendor Billing Documents, Extended Remuneration List Creation Simulate Generation of Remuneration Lists From Payment Documents Simulate Generation of Remuneration Lists From Posting Lists Simulate Generation of Remuneration Lists From Customer Settlements Generate Simulation of Remuneration Lists From Expense Settlements Simulate Generation of Remuneration List From Vendor Billing Documents Create Extended Remuneration Lists from Remuneration Lists Relevant Remuneration Lists for Extended Remuneration List Creation Create Simulation of Remuneration Lists from Remuneration Lists Generate Extended Remuneration Lists from Preceding Documents Relevant Preceding Documents for Extended Remuneration List Creation Create Simulation of Remuneration Lists from Preceding Documents Generate Extended Remuneration Lists from FI Documents Generate Simulation Remuneration Lists from FI Documents Generate Remuneration Lists from Vendor Settlements Generate Simulation of Remuneration Lists from Vendor Settlements Relevant Vendor Settlements for S_ALN_ S_ALN_ S_ALN_ S_ALN_ S_ALN_ S_ALN_ S_AEN_ S_AEN_ S_AEN_ S_AEN_ S_AEN_ S_AEN_ S_E37_ S_E37_ S_PRN_ S_PRN_ S_PRN_ RWLF_SETTLEME NT_LIST_RL RWLF9042 RWLF9042 RWLF9042 RWLF9042 RWLF9042 RWLF9039 RWLF_SETTLEME NT_LIST_RL RWLF9042 RWLF9039 RWLF_SETTLEME NT_LIST_RL RWLF9042 RWLF9039 RWLF9042 RWLF9039 RWLF9042 RWLF_SETTLEME NT_LIST_RL Worklist based Creation of Settlement Document List (Dialog) Simulate Settlement Document Lists Simulate Settlement Document Lists Simulate Settlement Document Lists Simulate Settlement Document Lists Simulate Settlement Document Lists Create Settlement Document Lists Worklist based Creation of Settlement Document List (Dialog) Simulate Settlement Document Lists Create Settlement Document Lists Worklist based Creation of Settlement Document List (Dialog) Simulate Settlement Document Lists Create Settlement Document Lists Simulate Settlement Document Lists Create Settlement Document Lists Simulate Settlement Document Lists Worklist based Creation of Settlement Document List WLFSLRL WLF_RRLE_SIM WLF_RRLE_SIM WLF_RRLE_SIM WLF_RRLE_SIM WLF_RRLE_SIM WLF_RRLE_CREAT E WLFSLRL WLF_RRLE_SIM WLF_RRLE_CREAT E WLFSLRL WLF_RRLE_SIM WLF_RRLE_CREAT E WLF_RRLE_SIM WLF_RRLE_CREAT E WLF_RRLE_SIM WLFSLRL 80

81 RWLF9033 RWLF9034 RWLF9037 RWLF9038 RWLF9080 Extended Remuneration List Creation Generate Extended Remuneration Lists from SD Billing Documents Generate Simulation of Remuneration Lists from SD Billing Documents Relevant SD Billing Documents for Extended Remuneration List Creation Relevant FI Documents for Extended Remuneration List Creation Posting List Creation Dispatcher S_E4R_ S_E4R_ S_E4R_ S_E4R_ S_AEN_ RWLF9039 RWLF9042 RWLF_SETTLEME NT_LIST_RL RWLF_SETTLEME NT_LIST_RL RWLF2052D (Dialog) Create Settlement Document Lists Simulate Settlement Document Lists Worklist based Creation of Settlement Document List (Dialog) Worklist based Creation of Settlement Document List (Dialog) Dispatcher: Create Customer Settlement Lists WLF_RRLE_CREAT E WLF_RRLE_SIM WLFSLRL WLFSLRL WBLRN_DISP RWLF9081 Customer Settlement Creation Dispatcher S_AEN_ RWLF2051D Dispatcher: Create Customer Settlements WLF1K_DISP RWLF9082 RWLF9083 Mass Release Dispatcher Settlement Request List Creation Dispatcher S_AEN_ S_AEN_ RWLF2056D RWLF2053D Dispatcher: Mass Release of Settlement Management Doc. Dispatcher: Create Vendor Settlement Lists WAB_RELEASE_DI SP WRLVN_DISP RWLF9084 RWLF9085 RWLF9086 RWLFFLO W RWLFIDOC Extended Remuneration List Creation Dispatcher Dispatcher Message Output Dispatcher Mass Reversal Display Document Flow Information for Settlement Management Documents Extended IDoc Reporting S_AEN_ S_E37_ RWLF9039D RWLFWR14D RWLF2055D Dispatcher: Create Settlement Document Lists Dispatcher: Message Output for Settlement Mgmt Documents Dispatcher: Mass Cancellation of Settlement Management Docs WLFU RWLF1051 List Output Settlement Management Documents WLFEIR RWLFIDOC_NEW IDoc Processing WLF_RRLE_CREAT E_DISP WLN14D WAB_CANCEL_DIS P WLI2 WLF_IDOC RWLFM30 RWLFM31 RWLFM32 RWLFM40 RWLFM40 Automatic Document Adjustment of Vendor Billing Documents Automatic Document Adjustment of Expenses Documents Automatic Document Adjustment of Vendor Settlements Automatic Document Adjustment of Payment Documents Automatic Document Adjustment of Payment WLFM30 RWLFM99 Automatic Document Adjustment of Settlement Management Documents WLFM31 RWLFM99 Automatic Document Adjustment of Settlement Management Documents WLFM32 RWLFM99 Automatic Document Adjustment of Settlement Management Documents WLFM60 RWLFM99 Automatic Document Adjustment of Settlement Management Documents WLFM40 RWLFM99 Automatic Document Adjustment of Settlement Management WLFM99 WLFM99 WLFM99 WLFM99 WLFM99 81

82 RWLFWR0 1 Documents Messages from Vendor Billing Documents Documents WLN1 RWLFWR14 Issue Messages from Settlement Management Documents WLN14 RWLFWR0 2 RWLFWR0 3 RWLFWR0 4 Messages from Customer Settlement Lists Messages from Remuneration Lists for Vendor Billing Documents Messages from settlement requests WLN2 RWLFWR14 Issue Messages from Settlement Management Documents WLN3 RWLFWR14 Issue Messages from Settlement Management Documents WLN4 RWLFWR14 Issue Messages from Settlement Management Documents WLN14 WLN14 WLN14 RWLFWR0 5 RWLFWR0 6 RWLFWR1 0 RWLFWR1 1 Messages from Settlement Request Lists Messages from Remuneration Lists for Settlement Requests Messags from Customer Settlements Messages from Expenses Settlements WLN5 RWLFWR14 Issue Messages from Settlement Management Documents WLN6 RWLFWR14 Issue Messages from Settlement Management Documents WLN10 RWLFWR14 Issue Messages from Settlement Management Documents WLN11 RWLFWR14 Issue Messages from Settlement Management Documents WLN14 WLN14 WLN14 WLN14 RWLFWR1 2 RWLFWR1 3 RWLWRCI NV Messages from Remuneration Lists for Customer Settlements Messages from Remuneration Lists for Expenses Settlements Archive Customer Settlements WLN12 RWLFWR14 Issue Messages from Settlement Management Documents WLN13 RWLFWR14 Issue Messages from Settlement Management Documents WACCIA WCI_WRI Archiving Customer Settlements: Write Program WLN14 WLN14 RWLWRILS Archive Settlement Document List WACLA WRECH_WRI Archiving Settlement Document Lists: Write Program RWLWRIN V RWLWRPL S Archive Vendor Billing Documents Archive Customer Settlement Lists WACLFA WLF_WRI Archiving Vendor Billing Docs and Vendor Settlements: Write Program WACBA WBU_WRI Archiving Customer Settlement Lists: Write Program RWLWRSIN V Activate Expense Settlements WACSIA WSI_WRI Archiving Expense Settlements: Write Program RWLWRSLS Archive Settlement Request List WACRLA WREG_WRI Archiving Vendor Settlement Lists: Write Program RWLWRSM R RWLF3001 Archive Settlement Documents Read Vendor Billing Documents from the Archive (Display Items) WACZRA WZR_WRI Archiving Settlement Documents: Write Program WLFT RWLFLIST Document Monitor WLI5 82

83 RWLF3002 RWLF3003 RWLF3004 RWLF3005 RWLF3006 RWLF3007 Read Customer Settlement Lists from the Archive (Display Items) Read Settlement Document Lists from the Archive (Display Items) Read Settlement Documents from the Archive (Display Items) Read Vendor Settlement Lists from the Archive (With Items) Read Customer Settlements (with Item Data) from the Archive Read Expense Settlements (with Item Data) from the Archive WLA8 RWLFLIST Document Monitor WLI5 WLA5 RWLFLIST Document Monitor WLI5 WLA6 RWLFLIST Document Monitor WLI5 WLA7 RWLFLIST Document Monitor WLI5 WLACII RWLFLIST Document Monitor WLI5 WLASII RWLFLIST Document Monitor WLI5 Obsolete Tcode WLR1 WBL1 OAGZ Successor Tcode WLFSLRL WBLRN n/a Required and Recommended Action(s) Pre-Check is performed for the component LO-AB. Custom code adoption on the new DB-Design can be checked in the start release to identify the code places which have to adjust to the new DB-Structures. Batch or online processes which needed the obsolete transactions or reports have to be adjusted so that the new transactions and reports are used instead the obsolete once. Mostly all replaced reports and transaction where part of the solution portfolio of SAP_APPL and EA-RETAIL of the Business Suite To simplify the Conversion to S/4 it is recommended to adjust the business process in the start release by a step by step replacement of the obsolete transactions by the once which will be part of S/4. You have to activate the software component EA- RETAIL to use the successor reports or transactions. You can also adopt the business processes in S/4 without to change the processes in the current release Related SAP Notes Custom Code related information SAP Notes: , , ,

84 2.1.6 Logistics ATP New advanced ATP in SAP S/4HANA Table VBBS Description The database table VBBS contained pre-aggregated sales requirements. The requested (OMENG) and confirmed (VMENG) quantities have been aggregated on a daily basis. With the new HANA ATP we do not need pre-aggregation anymore and therefore this table is obsolete. Instead of the VBBS we use the VBBE where each ATP-relevant requirement is explicitly stored. The old ERP- ATP-check coding is redirected to use VBBE, too Business Process related information No influence on business processes expected. The customizing where the VBBS could be activated in the business suite is deactivated in SAP S/4HANA, on-premise edition New entries will automatically "choose" to use VBBE instead of VBBS Required and Recommended Action(s) There are two checks to be carried out before the upgrade to make sure if the VBBS is used: 1. Start transaction "SE16" and display the entries in table "VBBS". If there are any entries the XPRA has to run. If there are no entries the next step has to be executed: 2. Start transaction "OVZ2": And check the entries for the fields "SUMAU" and "SUMLF". If there is any entry other than "A: Single records", the XPRA needs to be executed. Just create a db-view on table VBBE and use that view instead of the table VBBS in custom code Related SAP Notes Custom Code related information SAP Note: icon (E2open) Description The interface to icon-scm (now E2open) is not available in SAP S/4HANA. Accordingly this external planning engine is not available in SAP S/4HANA Business Process related information The icon-scm planning engine and algorithms can't be used any more. 84

85 Business processes which are based on the icon-scm planning engine and algorithms can't be used any more Required and Recommended Action(s) Check if the icon-scm integration is necessary If YES you have to re-consider the system conversion to SAP S/4HANA, on-premise edition Related SAP Notes Custom Code related information SAP Note: New fashion solution Description The new fashion solution comprising characteristic based ATP is not available anymore in SAP S/4HANA, onpremise edition Appropriate Business Function LOG_SEGMENTATION will be 'always off' within SAP S/4HANA, on-premise edition Business Process related information Business processes which are based on ATP check for segmentation cannot be used any more. Business processes which are based on the new fashion solution can't be used any more Required and Recommended Action(s) Describe the required/recommended customer actions (e.g. perform Conversion Pre-Check on start release to identify start situation; start of recommended application adaptions on start release). In case a different variants of a functionality are available in SAP Business Suite and as part of the principle of one there is one target architecture you should recommend to move to this target architecture Logistics - Environment, Health & Safety (EHS) Industrial Hygiene and EC interfaces Description Industrial Hygiene and Safety With SAP EHS Management as part of SAP ERP, customers can use the Industrial Hygiene and Safety (EHS-IHS) solution for managing incidents and performing risk assessments. In SAP S/4HANA on-premise edition 1511, this solution is no longer available. However, customers can use the incident management solution and the health and safety management solution of Environment, Health, and Safety as part of SAP S/4HANA to support their business processes. Interfaces to SAP Environmental Compliance 85

86 Customers can use SAP Environmental Compliance (SAP EC) to support emissions and compliance-relevant processes. In addition, Environmental Compliance provides interfaces to exchange data with other applications. In SAP S/4HANA on-premise edition 1511, the following interfaces are not available: 1. Environmental Compliance - Specification Database: o Environmental Compliance will not be able to read specification data or units of measurement from Environment, Health, and Safety as part of SAP S/4HANA 2. Environmental Compliance - Incident: o Environmental Compliance will not be able to read incident or location data from Environment, Health, and Safety as part of SAP S/4HANA 3. EAM - Environmental Compliance: o Enterprise Asset Management (EAM), as part of SAP S/4HANA, will not be able to display Environmental Compliance data A successor solution for SAP Environmental Compliance is planned for Environment, Health, and Safety in a future SAP S/4HANA delivery Business Process related information Industrial Hygiene and Safety (EHS-IHS) is replaced by the new incident management solution and health and safety management solution of Environment, Health, and Safety as part of SAP S/4HANA. Business processes are described in the documentation for Environment, Health, and Safety as part of SAP S/4HANA. Transaction not available in SAP S/4HANA on-premise edition 1511 CBIH02,CBIH03,CBIH12,CBIH13,CBIH14,CBIH42,CBIH43,CBIH50,CBIH51, CBIH52,CBIH72, CBIH73,CBIH82,CBIH83,CBIH88,CBIH89,CBIHB0,CBIHB1,CBIHB2,CBIHB3, CBIHB4,CBIHB5,CBIHB6,CBIHM2,CBIHM3,CBIHMR01,CBIHMR02, CBIHMR03,CBIHMR04,CBIHMR05,CBIHMR06,CBIHMR07,CBIHMR08,CBI HMR09,CBIHT0,CBIHT1,CBIHT2,CBIHT3,CBIHT4,CBIHT5,CBIHT6,CBIHT Related SAP Notes Custom Code related information SAP Note: Occupational Health Description With SAP EHS Management as part of SAP ERP, customers can use the Occupational Health (EHS-HEA) function to support general employee occupational healthcare in their company. In SAP S/4HANA on-premise edition 1511, this solution is no longer available and there is no successor solution. 86

87 Business Process related information Occupational Health (EHS-HEA) is not available in SAP S/4HANA. Related Business Processes are not available in SAP S/4HANA. Transaction not available in SAP S/4HANA on-premise edition 1511 EHSAMBTAET,EHSASSIGN,EHSASSLTA,EHSASSPERS, EHSBC02,EHSBP11,EHSBP12,EHSBP13,EHSBP31,EHSBP32,EHSBP33,EHS BP41,EHSBP42,EHSBP43,EHSBP51,EHSBP52,EHSBP53, EHSCALPROX,EHSCBER,EHSCDCT, EHSCMAS,EHSDATIMP,EHSDIAGSL,EH SEVAL00,EHSEXIST0, EHSH_C_NR_EXA_C,EHSH_C_NR_NEWPE,EHSH_C_NR_RECN,EHSH_C_N R_VAC_I,EHSH_D_CALPHYS,EHSH_D_PCP, EHSMQUEST,EHSMQUEST01,EHSPERSHC1,EHSPP01,EHSPRANZ,EHSPRL OE,EHSQCATOH,EHSQEVAL01,EHSQUESTOH, EHSSCAN,EHSSERV,EHSSERV01,EHSSERV11,EHSSERV30,EHSSER50,EHSS TRU00,EHSSUGGP,EHSTERM01, EHSVA02,EHSVU01,EHSVU01_SELSCREEN,EHSVU11,EHSVU21,EHSVU Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Waste Management Description With SAP EHS Management as part of SAP ERP, customers can use the Waste Management (EHS-WA) solution for handling waste disposal processes within their company. In SAP S/4HANA on-premise edition 1511, this solution is not available Business Process related information Waste Management (EHS-WA) is not available in SAP S/4HANA, on-premise edition Related Business Processes are not available in SAP S/4HANA, on-premise edition Transaction not available in SAP S/4HANA on-premise edition 1511 WAA01,WAA02,WAA03,WAA04,WAA10,WAA11,WAA12,WAA13,WAA1 9,WAA20,WAA21,WAA22,WAA23,WAA24,WAA25,WAA26, WAAP, WACB01,WACM01,WACM02,WACM03,WACM04,WACM10,WACM30, 87

88 WACO02,WACO02OLD,WACO03OLD,WACO04OLD, WACS1,WACS2,WACS3,WACS4,WACS6,WADC,WADI,WAE01,WAE02,W AE03,WAE10,WAEA,WAGE, WAM01, WAM02,WAM03,WAM04,WAM05,WAMC,WAMI,WAMR,WANP,WARE P001, WASM100, WASM101,WASM102,WASM109,WASS100,WASS101,WASS102,WASS1 03,WASS104,WASS105,WASS106,WASS107,WASS108,WASS110, WASS111,WASS112,WASS113,WASS114,WASS115,WASS116,WASS117, WASS118,WASS119,WASS120,WASS121,WASS122,WASS123,WASS124, WATR,WATREE Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Simplification in Incident Management and Risk Assessment Description With component extension for SAP EHS Management, customers can use the Incident Management (EHS- MGM-INC) solution and the Risk Assessment (EHS-MGM-RAS) solution for managing their health and safety business processes. In SAP S/4HANA on-premise edition 1511, some functions are not available. Incident Management The following incident management functions are not available in SAP S/4HANA: BI extraction and queries for incident reporting GRC integration of incidents MM integration for released material as part of incidents Novareto integration for incidents esoa services for incidents Enterprise search for incidents Direct creation of HR absences from incidents Creation of quality notifications from incidents Creation of service notifications from incidents Service orders for financial tracking Risk Assessment The following risk assessment functions are not available in SAP S/4HANA: BI extraction and queries for chemicals 88

89 Amounts/data series Creation of customer notifications from risk assessments Creation of quality notifications from risk assessments Identification of risks effected by OEL changes IH work area integration with locations Business Process related information Incident reporting is not available in SAP S/4HANA on-premise edition There is no functional equivalent available. Reporting for chemicals is not available in SAP S/4HANA on-premise edition There is no functional equivalent available. The amounts/data series function is not available within SAP S/4HANA, on-premise edition The functional equivalent is workplace sampling management. See SAP Note Required and Recommended Action(s) Recommended actions for Incident Management: Close all open quality notifications for incidents. Set the end date of recurring quality notifications for incidents to a date that is earlier than the Conversion to the target system. Close all open customer service notifications for incidents. Set the end date of recurring customer service notifications for incidents to a date that is earlier than the Conversion to the target system. Recommended actions for Risk Assessment: Close all open quality notifications for risk assessments. Set the end date of recurring quality notifications for risk assessments to a date that is earlier than the Conversion to the target system. Close all open customer service notifications for risk assessments. Set the end date of recurring customer service notifications for risk assessments to a date that is earlier than the Conversion to the target system Related SAP Notes Conversion Pre-Checks SAP Note: Custom Code related information SAP Note: Additional related SAP Notes SAP Note:

90 2.1.8 Logistics GT Global Trade Management Description Simplification of DB Key Fields and tables structures (WBHF, WBGT, WBIT, WBASSOC, WCOCOF, WB2_D_BUSVOLBASE, WB2_D_BVB_SETTL) Replacement of concatenated fields by corresponding new fields in mentioned DB tables (Future details can be found in the mentioned notes below) Change of Domain definition from CHAR to NUMC for item number related fields Replaced fields are moved to the dynamical part of the communication structures to avoid runtime errors and to ensure the same system behaviour as before Business Process related information Dictionary changes will have no influence on the business processes as such. Custom related code has to be adjusted to adopt the new data model. If one of the obsolete transactions or reports is used within the business process the new transactions and reports have to be used instead. Transaction Codes and Reports not available in SAP S/4HANA See also note Obsolete Report RWB2B001 RWB2B001 WB2B_CREATE_TC_USER Obsolete Report Title Trading Contract: General Document Overview Trading Contract: General Document Overview Create User For TC At Web Obsolete TCode Successor Report Successor Report Title WB24 RWB2BREL Trading Contract: Follow on document prosessing WB25_COMP RWB2BMAS Mass Processing (Release and Status update) WB2B_NETUSER Successor TCode WBRR WB24N Obsolete TCode Successor TCode POFO1 POFO2 POFO3 POFO31 POFO32 POFO33 90

91 Required and Recommended Action(s) Pre-Check is performed for the component LO-GT. Custom code adoption on the new DB-Design can be checked in the start release to identify the code places which have to adjust to the new DB-Structures. Batch or online processes which needed the obsolete transactions or reports have to be adjusted so that the new transactions and reports are used instead Related SAP Notes Custom Code related information SAP Notes: , , Logistics Material Management Inventory Management (MM-IM) Data model in inventory management (MM-IM) Description The SAP ERP 6.0 stock inventory management data model consists of the two document tables MKPF for document header information and MSEG for document item data. Additionally there were aggregated actual stock quantity data stored in several tables. Some of these tables do also store material master data attributes like the tables MARC, MARD and MCHB. Such tables with material master data attributes as well as actual stock quantities will be named as hybrid tables in the following. In contrast there are also tables like MSSA containing only aggregated actual stock quantities for sales order stock. Such tables will be called in the following as replaced aggregation tables. With S/4HANA this data model has been changed significantly. The new de-normalized table MATDOC has been introduced which contains the former header and item data of a material document as well as a lot of further attributes. Material document data will be stored in MATDOC only and not anymore in MKPF and MSEG. Additionally the aggregated actual stock quantities will not be persisted anymore in the hybrid or replaced aggregation tables. Instead, actual stock quantity data will be calculated on-the-fly from the new material document table MATDOC for which some of those additional special fields are used. Hence, with the new MM-IM data model the system will work on data base level in an INSERT only mode without DB locks. Nevertheless, for stock decreasing processes there will be still ABAP locks to ensure stock consistency. A further advantage of the new MM-IM data model is the capability of simple and fast reporting because the most information is in one place: MATDOC. All below mentioned tables of the SAP ERP 6.0 world do still exist in S/4HANA as DDIC definition as well as data base object and the hybrid tables will still be used to store the material master data attributes. For compatibility reasons there are Core Data Service (CDS) Views assigned as proxy objects to all those tables ensuring that each read access to one of the mentioned tables below still returns the data as before in SAP ERP 6.0. The CDS Views do the on-the-fly aggregation of actual stock quantities from the new MM-IM data model and join the master data attributes from the material master data table. Hence all customer coding will work as before because each read access to one of the tables will get redirected in the database interface layer of NetWeaver to the assigned CDS view. The affected tables are listed below: 91

92 Table Table description DDL Source of CDS View for redirect View to read the content of the database table (w/o redirect to compatibility view) View to read the master data attributes only MKPF Material NSDM_DDL_MKPF NSDM_MIG_MKPF - document header MSEG Material NSDM_DDL_MSEG NSDM_MIG_MSEG - document item MARC Plant Data for NSDM_DDL_MARC NSDM_MIG_MARC V_MARC_MD Material MARD Storage Location NSDM_DDL_MARD NSDM_MIG_MARD V_MARD_MD Data for Material MCHB Batch stocks NSDM_DDL_MCHB NSDM_MIG_MCHB V_MCHB_MD MKOL Special Stocks NSDM_DDL_MKOL NSDM_MIG_MKOL V_MKOL_MD from Vendor MSLB Special Stocks NSDM_DDL_MSLB NSDM_MIG_MSLB V_MSLB_MD with Vendor MSKA Sales Order Stock NSDM_DDL_MSKA NSDM_MIG_MSKA V_MSKA_MD MSSA Total Customer NSDM_DDL_MSSA NSDM_MIG_MSSA - Orders on Hand MSPR Project Stock NSDM_DDL_MSPR NSDM_MIG_MSPR V_MSPR_MD MSSL Total Special NSDM_DDL_MSSL NSDM_MIG_MSSL Stocks with Vendor MSSQ Project Stock NSDM_DDL_MSSQ NSDM_MIG_MSSQ - Total MSKU Special Stocks NSDM_DDL_MSKA NSDM_MIG_MSKU V_MSKU_MD with Customer MSTB Stock in Transit NSDM_DDL_MSTB NSDM_MIG_MSTB - MSTE Stock in Transit to NSDM_DDL_MSTE NSDM_MIG_MSTE - Sales and Distribution Document MSTQ Stock in Transit NSDM_DDL_MSTQ NSDM_MIG_MSTQ - for Project MCSD DIMP: Customer NSDM_DDL_MCSD NSDM_MIG_MCSD MCSD_MD Stock MCSS DIMP: Total NSDM_DDL_MCSS NSDM_MIG_MCSS MCSS_MD Customer Stock MSCD DIMP: Customer NSDM_DDL_MSCD NSDM_MIG_MSCD MSCD_MD stock with vendor MSCS DIMP: Customer NSDM_DDL_MSCS NSDM_MIG_MSCS MSCS_MD stock with vendor - Total MSFD DIMP: Sales Order NSDM_DDL_MSFD NSDM_MIG_MSFD MSFD_MD Stock with Vendor MSFS DIMP: Sales Order NSDM_DDL_MFS NSDM_MIG_MSFS MSFS_MD Stock with Vendor - Total MSID DIMP: Vendor NSDM_DDL_MSID NSDM_MIG_MSID MSID_MD Stock with Vendor MSIS DIMP: Vendor NSDM_DDL_MSIS NSDM_MIG_MSIS MSIS_MD 92

93 Stock with Vendor - Total MSRD DIMP: Project NSDM_DDL_MSRD NSDM_MIG_MSRD MSRD_MD Stock with Vendor MSRS DIMP: Project NSDM_DDL_MSRS NSDM_MIG_MSRS MSRS_MD Stock with Vendor - Total MARCH History NSDM_DDL_MARCH NSDM_MIG_MARCH - MARDH History NSDM_DDL_MARDH NSDM_MIG_MARDH - MCHBH History NSDM_DDL_MCHBH NSDM_MIG_MCHBH - MKOLH History NSDM_DDL_MKOLH NSDM_MIG_MKOLH - MSLBH History NSDM_DDL_MSLBH NSDM_MIG_MSLBH - MSKAH History NSDM_DDL_MSKAH NSDM_MIG_MSKAH - MSSAH History NSDM_DDL_MSSAH NSDM_MIG_MSSAH - MSPRH History NSDM_DDL_MSPRH NSDM_MIG_MSPRH - MSSQH History NSDM_DDL_MSSQH NSDM_MIG_MSSQH - MSKUH History NSDM_DDL_MSKAH NSDM_MIG_MSKAH - MSTBH History NSDM_DDL_MSTBH NSDM_MIG_MSTBH - MSTEH History NSDM_DDL_MSTEH NSDM_MIG_MSTEH - MSTQH History NSDM_DDL_MSTQH NSDM_MIG_MSTQH - MCSDH History NSDM_DDL_MCSDH NSDM_MIG_MCSDH - MCSSH History NSDM_DDL_MCSSH NSDM_MIG_MCSSH - MSCDH History NSDM_DDL_MSCDH NSDM_MIG_MSCDH - MSFDH History NSDM_DDL_MSFDH NSDM_MIG_MSFDH - MSIDH History NSDM_DDL_MSIDH NSDM_MIG_MSIDH - MSRDH History NSDM_DDL_MSRDH NSDM_MIG_MSRDH - Note: The DIMP hybrid tables have now new pure DIMP related material master data tables Business Process related information Valuation of special stock is derived from customizing as well as the material master and stored in the predecessor of the material document. The valuation is also stored in the material document and was stored in SAP ERP 6.0 in the aggregate tables MSSA, MSSQ and MSSL respectively too. Hence in SAP ERP 6.0 there was just one possible valuation for special stock at order on hand, project stock and special stock with vendor. With the new MM-IM data model various valuations would be possible but this is not available across the whole process chain. Therefore right now a change of the valuation after an initial posting on special stock will not be supported. The reports MBCKMSSAS, MBMSSACOS, MBMSSAPOS, MBMSSQCOS, MBMSSQRS cannot be used to change the valuation value in field KZBWS for special stock at order on hand or project stock. The transaction /SAPNEA/JSCR21 cannot be used to change the valuation value in field XOBEW for special stock with vendor Required and Recommended Action(s) The above mentioned Conversion Pre-Checks on the start release to identify the start situation should be performed. Before the system conversion to Sap S/4HANA, on-premise edition 1511 the required DDIC adjustments for appends on above mentioned tables shall be done. 93

94 Related SAP Notes Conversion Pre-Checks SAP note If customer is using ECC-DIMP (without LAMA): SAP note Custom Code related Customer Appends on the former document tables MKPF and MSEG information If the attributes in the appends on those tables do have a master data or process controlling character then the appends need to be appended to the table MATDOC and the assigned proxy views can be made compatible via extension views. See SAP NetWeaver 7.4 documentation. Customer Appends on the hybrid and replaced aggregation tables Fields containing material master data attributes If the append is not at the end of the hybrid table then the append should be moved to the end if possible and then no further action is required because the delivered DDL sources for the proxy views provide the $EXTENSION feature. For replaced aggregation tables appends with master data attributes are not available. If such appends are really required in the customer processes then the approach described in the next chapter maybe feasible. In the core functionality of material document processing there will be no write process on these tables. Thus update of the fields in appends require maybe some additional customer coding. Fields representing a customer defined stock type or quantity/value to be aggregated. If own stock types or a dimension which needs to be aggregated have been introduced by the customer then the view stack of the CDS view assigned to the table with the additional stock type needs to be modified. Right now, there is no technology support for modification free enhancement. If the stock type has not been introduced by new entries or enhancements in the tables T156x - which controls in the core functionality the mapping between a posting and a stock type - then the process logic needs to be adapted. Code Optimization (optional/recommended) Technically it is still possible to do DB write operations on the tables MKPF, MSEG as well as the fields representing actual stock quantities in the hybrid and replaced aggregation tables. But such write operations are without any effect! Therefore write operations on MKPF, MSEG as well as the fields representing actual stock quantities in the hybrid and replaced aggregation tables shall be removed/adjusted from/in customer coding. DB read operations on the hybrid and replaced aggregation tables have a performance decrease. In general, it shall be avoided to read any stock quantities when only master data is required. Therefore it is recommended to adjust the customer coding in the following way: If material master data as well as actual stock quantity data are required then the SELECT...<table> should be replaced by using a data access method in class CL_NSDM_SELECT_<table>. These classes provide access methods for single as well as array read operations. If material master data are required then the SELECT...<table> should be replaced by SELECT...V_<table>_MD where V_<table>_MD is one 94

95 of the above mentioned views for master data access. Alternatively corresponding material master data read methods in the class CL_NSDM_SELECT_<table> can be used. Also the data type declarations should be adjusted from TYPE...<table> to TYPE...V_<table>_MD. For the DIMP aggregate tables the new pure master data tables <table>_md should be used. If actual stock quantity data are required then the SELECT...<table> should be replaced by SELECT...NSDM_V_<table>_DIFF where NSDM_V_<table>_DIFF is one of the views in the view stack of the above mentioned proxy view. Also the data type declarations should be adjusted from TYPE...<table> to TYPE...NSDM_V_<table>_DIFF. General SAP Note For performance critical coding parts these adjustments are strongly recommended. For non-critical parts it is optional short term but recommended on long term Material Inventory Management: change of data model in S/4HANA Availability of Transactions in MM-IM The following transactions for entering and displaying goods movements (material documents) - called "MB transactions" (below) are not available with SAP S/4HANA. In SAP S/4HANA the single-screen generalized transaction MIGO is available (transaction MIGO is available in SAP Business Suite since Release 4.6): MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST and MBSU The transactions MMBE_OLD (Stock overview), MMBE (Stock overview), MB51 (Material Document List), MB52 (Display Warehouse Stocks of Material) and MB5B (Stock at posting date) are still available but will be not available midterm. Successor functionalities are already available as Fiori applications and/or as Virtual Data Model (VDM) to be consumed by SAP Lumira or SAP Design Studio: MMBE_OLD: Fiori application Stock Single Material, VDM view C_MaterialStockActual MMBE: Fiori application Stock Single Material, VDM view C_MaterialStockActual MB51: Fiori application Material Documents Overview MB52: Fiori application Stock Multiple Materials, VDM view C_MaterialStockActual MB5B: Fiori application Stock Multiple Materials, VDM view C_MaterialStockByKeyDate Business Process related information No influence on business processes expected Required and Recommended Action(s) None 95

96 Material Ledger Obligatory for Material Valuation Description This simplification makes it obligatory to use the Material Ledger in all SAP S/4HANA systems. When a system is converted to SAP S/4HANA the Material Ledger will be activated if not active already. Latest trends in material management aim for improved and more flexible valuation methods in multiple currencies and parallel accounting standards while simultaneously reducing required system resources and improving scalability of the business processes. Since the data model of the Material Ledger (ML) module supports these business requirements, it was chosen as the basis for material inventory valuation in the new solution SAP S/4HANA. It is very important to distinguish between Material Ledger, in its role as an inventory subledger in Accounting, and business feature Actual Costing. Material Ledger, as the inventory subledger, valuates material inventories in multiple currencies and GAAPs in parallel. In addition Material Ledger is a base prerequisite for the use of Actual Costing. With Actual Costing you can valuate your material inventories, work in process and cost of goods sold with weighted average unit costs that are being calculated after the fact by evaluating business transactions of one or several posting periods. Also other features, e.g. actual cost component split, are provided by Actual Costing. Even though Material Ledger is become obligatorily active, Actual Costing is not. Activation of Actual Costing is still optional. Before S/4HANA, the inventory valuation tables xbew(h) - tables: EBEW, EBEWH, MBEW, MBEWH, OBEW, OBEWH, QBEW, QBEWH - contain transactional as well as master data attributes. With S/4HANA, the inventory valuation tables do still exist as DDIC definition as well as database object. However, they will only be used to store material master data attributes. The transactional fields LBKUM, SALK3 and SALKV will be retrieved from the Material Ledger. Hence, those fields are not updated anymore in the original xbewh(h) tables. As a consequence, the above mentioned tables need to be updated less often, which leads to a higher throughput due to less database locks. For compatibility reasons there are Core Data Service (CDS) Views assigned as proxy objects to all those tables ensuring that each read access to one of the mentioned tables still returns the data as before. The CDS views consist of database joins in order to retrieve both master data from the original xbew(h) table and transactional data from Material Ledger tables. Hence all customer coding, reading data from those tables, will work as before because each read access to one of the tables will get redirected in the database interface layer of NetWeaver to the assigned CDS view. Write accesses to those tables have to be adjusted, if transactional fields are affected. The following table gives an overview of the new relevant database objects in the S/4HANA Inventory Valuation data model: Table Table description DDL source of CDS view for redirect (proxy view) EBEW Sales Order Stock Valuation View to read the content of the original database table (w/o redirect to proxy view) View to read master data attributes only MBV_EBEW MBVEBEWOLD V_EBEW_MD 96

97 EBEWH History of Sales MBV_EBEWH MBVEBEWHOLD V_EBEWH_MD Order Stock Valuation MBEW Material Valuation MBV_MBEW MBVMBEWOLD V_MBEW_MD MBEWH History of Material MBV_MBEWH MBVMBEWHOLD V_MBEWH_MD Valuation OBEW Valuated Stock with MBV_OBEW MBVOBEWOLD V_OBEW_MD Subcontractor (Japan) OBEWH History of Valuated MBV_OBEWH MBVOBEWHOLD V_OBEWH_MD Stock with Subcontractor (Japan) QBEW Project Stock MBV_QBEW MBVQBEWOLD V_QBEW_MD Valuation QBEWH History of Project Stock Valuation MBV_QBEWH MBVQBEWHOLD V_QBEWH_MD Table 1: Affected tables with information about corresponding proxy objects, views for accessing original database table and views for reading master data only Business Process related information If customers are not using the material ledger already it will be activated during the conversion process. In MM02 and MR21 material prices can now be maintained in multiple currencies. In Financials the inventory account balances are calculated separately for each currency and result therefore in a cleaner and more consistent valuation in other currencies than the local currency Transaction not available in SAP S/4HANA on-premise edition 1511 MMPI: Initialize period for material master records (Not available with activated Material Ledger) Required and Recommended Action(s) Perform Conversion Pre-Checks on start release to identify start situation Related SAP Notes Conversion Pre-Checks SAP Note: SAP Note: Custom Code related information SAP Notes:

98 Material Valuation - Statistical moving average price Description One major innovation in SAP S/4HANA in the area of MM is the significant increase of transactional data throughput for high volume transactions, especially goods movements. To enable this from a technical point of view, application logic should avoid exclusive locking on the application layer. For goods movements this can be achieved with few exceptions for materials with price control "Standard", where the relation between unit costs for material inventory (standard price) on one hand, and inventory quantity and inventory value is kept constant during goods movements. To calculate a consistent moving average valuation, the system is still forced to use exclusive locks. Therefore not the same increase of transactional data throughput can be achieved for materials with price control "Moving Average" in comparison to materials with price control Standard. In classic SAP Business Suite the system calculates for materials with price control "Standard", also a moving average valuation in parallel, the so called "statistical" moving average price. Obviously this statistical valuation requires also exclusive locking. As said, exclusive locking is limiting the transactional data throughput, and therefore shall be avoided in SAP S/4HANA. In consequence, this parallel statistical moving average valuation is not available in SAP S/4HANA, on-premise edition The deactivation of the statistical moving average is not mandatory in SAP S/4HANA, but recommended to achieve a significant increase of transactional data throughput for goods movements. It is important to note that the deactivation is not reversible. The deactivation of the statistical moving average is the consequence of a new lock behaviour for materials with price control "Standard". This new lock behaviour does not use exclusive locks anymore. The activation of the new lock behaviour leads to the deactivation of the statistical moving average. As a result, end users, creating material master data in SAP S/4HANA, have to select one of the following material valuation methods for a material: Price control "Standard" that offers a fixed price inventory valuation, no parallel "statistical" moving average valuation. Only dedicated business transactions can change unit costs (e.g. MR21). But a significantly increased transactional data throughput for goods movements can be achieved. Price control "Moving Average" with which unit costs of material inventory might be changed by any business transaction, but transactional data throughput is still limited by the exclusive locking. In table MBEW, EBEW, OBEW, QBEW the attributes SALKV and VERPR are not updated anymore for materials with price control Standard. The same is valid for the history tables MBEWH, EBEWH, OBEWH and QBEWH. In table CKMLCR the attributes PVPRS and SALKV are not updated anymore for materials with price control Standard. In table MLCR the attributes SALKV, SALKV_OLD and PVPRS_OLD are not updated anymore for materials with price control Standard. 98

99 If Actual Costing is used, the above mentioned fields will still be updated with the periodic unit price during the Actual Costing Closing Steps. No update of the mentioned fields entails that the statistical moving average price and the value based on the statistical moving average price are not available anymore in the user interface. This concerns the following transaction codes: MM01, MM02, MM03, CKM3 and MR Business Process related information The statistical moving average price is as the name already implies purely statistical and does not have an impact on actual financials-relevant valuation. Without the statistical moving average price in few scenarios an alternative way of valuation needs to be used. This concerns for instance: Balance Sheet Valuation: Selection variants must be checked and adapted. Product Cost Planning: Valuation variants must be checked and adapted Required and Recommended Action(s) As described above custom code must be checked and adapted if necessary. To identify such locations, it is required to make use of the where-used functionality of transaction SE11 and considering other techniques like transaction CODE_SCANNER to find locations which SE11 cannot handle like dynamic programming or native SQL statements. Finally the report SAPRCKM_OBLIGATORY_SETTINGS can be used to deactivate the statistical moving average price. This can be done for converted systems running the S/4HANA on-premise edition. In the S/4HANA cloud edition or new installs of the SAP S/4HANA on-premise edition the statistical moving average price is disabled by default Related SAP Notes Custom Code related information If within custom code the fields mentioned in chapter Description are evaluated for materials with price control Standard, then this usage should be removed. One possible reaction to this change could be to use instead of the V-Price (VERPR) either the S-Price (STPRS) or the V-Price (VERPR) depending on the configured price control for the respective material Logistics PLM Enterprise Search Description With SAP S/4HANA, on-premise edition 1511 the Enterprise Search models are now replication free search models (using HANA DB tables instead) within SAP Product Lifecycle Management (SAP PLM). 99

100 Business Process related information With the new solution the following searches are not available in SAP S/4HANA: Document search with linked documents Engineering Record with custom ER types (with custom header tables) Synchronization BOM to BOM search with assigned MBOMs Synchronization PSM to BOM search with source PSM Structure and target MBOMs Specification and PSM search with status data MBOM, Recipe and PSM search with assigned classification data MBOM, Recipe and PSM search with assigned document data Label search with recipe data origin Recipe search with formula item quantity Document search with attached document content Search for any object without leading zeroes No changes expected in the business process Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note: Assemblies Description In SAP S/4HANA, the functions related to Assemblies in product structure management within SAP Product Lifecycle Management (SAP PLM) are not available Business Process related information Product Assembly is not available in SAP S/4HANA, on-premise edition If customers would like to activate it, they need to follow the steps described in SAP note: General PFCG related authorizations can apply. Following functionalities are no longer available: Creation of Product Assemblies Changing Product Assemblies The navigation to the Product Assembly Web UI Support of Product Assemblies in the Engineering Record Display of Product Assemblies in the Object Navigator Usage of Product Assembly Groups as Phantom Assemblies in the Product Structure Management Web UI 100

101 Required and Recommended Action(s) Customers moving from SAP Business Suite to SAP S/4HANA, on-premise edition 1511 can use the report /PLMI/ER_ASM_DELECTION to remove Product Assembly related entries from the Engineering Record and Object Navigator customizing Related SAP Notes Custom Code related information SAP Note: Product Designer Workbench Description In SAP S/4HANA, the functions related to the Product Designer Workbench, previously accessible via transaction PDN, have been removed from SAP Product Lifecycle Management (SAP PLM). It is recommended that customers use the product structure management functions provided in SAP PLM for any related business requirements Business Process related information Following objects are not available in SAP S/4HANA ippe-objects not type of CMP-application of the product structure o Colour nodes (type COL) o Generic nodes (type GEN) o Focus nodes (type FOC) o Concept nodes (type CON) Non-configurable part of the product structure, e.g. variant assembly Alternatives of the product structure Following functionalities are not available Priority definition for nodes Variant differentiation Transaction not available in SAP S/4HANA on-premise edition 1511 PDN Required and Recommended Action(s) Customers shall move to Product Structure for SAP S/4HANA, on-premise edition Related SAP Notes Custom Code related information SAP Note:

102 Access Control Management (ACM) Description The PLM specific Access Control Management will be deactivated in the SAP S/4HANA, on-premise edition shipment and is planned to be replaced by a generic authorization concept for SAP S/4HANA. Access Control related UI fields are removed from the PLM objects' Web screens. Authorization restriction is not in place so these fields won't be considered and system won't restrict authorizations. Customers requiring that functionally before the successor is in place should contact SAP for additional information. Also please check the related SAP Note: Business Process related information Hiding the ACM for SAP S/4HANA, on-premise edition 1511 means that no PLM object specific authorization is in place by default. If customers would like to activate it, they need to follow the steps described in SAP note: General PFCG related authorizations can be used. PLM Object specific authorizations not available by default Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Note cfolders Description With SAP S/4HANA, on-premise edition 1511 the current cfolder interfaces is not available. SAP recommends to evaluate SAP Mobile Documents as a substitute for selected collaboration scenarios. No screen enhancements are known. Configuration in customizing tree: 102

103 Business Process related information It is no longer possible to exchange data (Documents, Materials, Bill of Materials, ippe Objects) between PLM and cfolders. Transaction not available in SAP S/4HANA on-premise edition 1511 CFI01 Importing Documents CFE01 Exporting Documents CFI02 Importing Documents, Materials and Bills of Material CFE02 Exporting Documents, Materials and Bills of Material CFI03 Importing Documents, Materials, Bills of Material and ippe Objects CFE03 Exporting Documents, Materials, Bills of Material and ippe Objects CFC01 Customizing for cfolders backend integration CFC02 Customizing for cfolders backend integration, BOMs Required and Recommended Action(s) Customers have to establish data exchange processes with partners using other techniques like SAP Jam or SAP Mobile Documents Related SAP Notes Custom Code related information SAP Note: cdesk Description The CAD Integration in SAP PLM (cdesk) is not available in SAP S/4HANA. As an alternative functionality for CAD integration, it is planned to release SAP Engineering Control Center (Partner Product - SBR) for SAP S/4HANA, on-premise edition in the future. For more information see SAP Note:

104 Business Process related information Customers will not be able to store CAD files directly in SAP DMS. Downstream processes like Visual Enterprise Function will be restricted. Customer might use alternative solution SAP Engineering Center. Planned for further S/4HANA release. Process for CAD-Data Management (derive BOM, store drawings, generation/consumption of viewable) cannot be implemented. in SAP S/4HANA on-premise edition 1511 CDESK, CDESK_CUS, CDESK_DEL_DBTRACE, CDESK_READ_DBTRACE, CDESK_SAVE_DBTRACE Required and Recommended Action(s) Customers shall move to partner solution SAP Engineering Control Center as soon it is available for SAP S/4HANA, on-premise edition Custom Code related information CDESK is not a "reuse" component. CDESK is rather an application with hooked in BAdis and custom code. If the CDESK-Application is not available, no BAdis are executed and therefore custom code is not executed Recipe Management Description SAP PLM Recipe Management (RM) is not available in SAP S/4HANA, on-premise edition This also affects PLM RM sub-functions such as Labelling, Trial Management and Handover to Manufacturing. The appropriate business requirements are covered within successor functionality SAP S/4HANA PLM Recipe Development (excluding Trial Management.) The takeover of recipes from SAP Business Suite into SAP S/4HANA, on-premise edition 1511 is supported, so the recipes are available and can be displayed after the system conversion to SAP S/4HANA, on-premise edition To use and further develop them, they need to be migrated via the migration function integrated into recipes in SAP S/4HANA PLM Recipe Development Business Process related information Functions related to PLM Recipe Development (RM), such as the Recipe Workbench, Recipe, Labelling and Trial Management, are not available within SAP S/4HANA, on-premise edition The functional equivalent is SAP PLM Recipe Development (RD). 104

105 The customer needs to implement development processes based on SAP PLM Recipe Development which will change the user interaction with the software and might include minor process changes. It also allows users to leverage new capabilities of PLM Recipe Development to increase the software based support for the product developer. Transaction not available in SAP S/4HANA on-premise edition 1511 Customizing Transaction not available in SAP S/4HANA onpremise edition 1511 RMWB Start Workbench BD_GEN_GRCP General Recipe Distribution BD_GEN_SRCP Replicate Site Recipe FRML02 Edit Recipe Formula FRML03 Display Recipe Formula FRML04 Formula Information System MRTRS_START Start MR Transformation MRTRSC01 RFC Destination of GR MRTRSC02 Master Recipe Generation RMSL02 Change Label Set RMSL03 Display Label Set RMSTAT Mass Status Change ORCP*, RCP*, RMS*, RMX* Required and Recommended Action(s) Projects need to migrate their processes from PLM Recipe Management functional capabilities to PLM Recipe Development functional capabilities. Data Migration from RM recipes to RD recipes is an integrated part of the tool and can be executed after the system conversion SAP S/4HANA, on-premise edition For the detailed steps, follow the guides for the migration from PLM RM to PLM RD. The specification object is not impacted by the switch over to PLM RD Related SAP Notes Conversion Pre-Checks Does the customer use TRIAL MANAGEMENT Check which recipes, formulas and label objects need to be migrated Migration transactions - executable before or after system conversion /PLMI/RCP_MIGRATION Recipe Migration /PLMI/RMSL_MIGRATION Migration of Label Sets Custom Code related information SAP Note:

106 Engineering Client Viewer (ECL) Description With SAP S/4HANA, on-premise edition 1511 the ECL-Viewer Functionality within SAP Product Lifecycle Management (SAP PLM) will no longer be available. Parts of the functionality and use cases can be covered by SAP Visual Enterprise Viewer Business Process related information 2D and 3D viewing in GUI transactions with ECL viewer will not be available any longer You may consider Visual Enterprise Viewer as an alternative in some transactions like e.g. Document Management and for some of the file formats for other file formats you may think about using the frontend application instead where appropriate Influence on Business Processes None - technology simplification Required and Recommended Action(s) In case Visual Enterprise Viewer shall be used, check the appropriate customizing Related SAP Notes Custom Code related information No influence expected since no open interfaces are available and the usage is stopped before launching itself. BAPI 'EASYDMS_ECL_OPEN_DOCUMENT' will issue an error if it is called remotely in custom code Easy Document Management (Easy DMS) Description With SAP S/4HANA, on-premise edition 1511 the Easy DMS Functionality within SAP Product Lifecycle Management (SAP PLM) will no longer be available. As an alternative, customers using easy DMS may consider the PLM DMS integration into SAP Mobile Documents Business Process related information Use DMS integration with Mobile document Business processes can be achieved by using DMS and Mobile Document integration. Transaction not available in SAP S/4HANA on-premise EASYDMS_CUS 106

107 edition Required and Recommended Action(s) Switch to DMS and Mobile Doc integration which is more powerful Related SAP Notes Custom Code related Custom plugin developed (in VC++) for Easy DMS solution has no information influence as the application usage is stopped at log-in level Engineering Desktop (EDesk) Description With SAP S/4HANA, on-premise edition 1511 the EDesk functionality within SAP Product Lifecycle Management (SAP PLM) application is not available. As successor functionality for CAD integration requirements, it is planned to release SAP Engineering Control Center for SAP S/4HANA, on-premise edition in the future. For more information see SAP Note: Business Process related information Customers will not be able to store CAD files directly in SAP DMS. Downstream processes like Visual Enterprise Function will be restricted. Customer might use alternative solution SAP Engineering Center, planned for further S/4HANA release. Process for CAD-Data Management (derive BOM, store drawings, generation/consumption of viewable) cannot be implemented. Transaction not available in SAP S/4HANA on-premise edition 1511 EDESK_CUS, EDESK_IPPE Required and Recommended Action(s) Customers shall move to the new product SAP Engineering Control Center as soon it is available for SAP S/4HANA, on-premise edition Custom Code related information EDESK is not a "reuse" component. EDESK is rather an application with hooked in BAdis and custom code. If the CDESK-Application is not available, no BAdis are executed and therefore custom code is not executed. 107

108 STEP Support Description With SAP S/4HANA, on-premise edition 1511 the STEP support within SAP Product Lifecycle Management (SAP PLM) is not available. Standard for exchanging Product Model data is not available in SAP S/4HANA, on-premise edition Business Process related information STEP is used for export Product Model data in format like XML. But this is not used by many customers due to changing standard for exchanging the data. No influence on business process expected and Product Model data can still be extracted using various custom methods. Transaction not available in SAP S/4HANA on-premise edition 1511 STEP10, STEP Required and Recommended Action(s) Check if there is any scenario which is using STEP and use alternative methods to exchange the data Related SAP Notes Custom Code related information SAP Note: DMS Description With SAP S/4HANA, on-premise edition 1511 is not available. Web transactions like CVW* are not available in SAP S/4HANA, on-premise edition This is obsolete now and PLM WUI can be used for the same Business Process related information Use PLM WUI. Transaction not available in SAP S/4HANA on-premise edition 1511 CVW* 108

109 Required and Recommended Action(s) Check if Web Document is used anywhere. Use PLM WUI or FIORI tiles for CV transactions Related SAP Notes Custom Code related information SAP Note: Variant Configuration Description The following functionality is disabled in SAP S/4HANA, On Premise 1511: Object dependencies of type actions have been documented as obsolete. Creation of object dependencies of type actions isn't possible anymore (e.g. transaction CU01). Configuration models containing actions are still supported and behave like before, but new actions can't be created. It's not possible to maintain "Classification as Selection Condition" in Material BOM items anymore (e.g. transactions CS01, CS02). If in Material BOM items classes as selection condition are already maintained, the BOM explosion will work as before. But it's not allowed to use "Classification as Selection Condition" for BOM items, where it wasn't used before. Transactions have been removed (see list below) Business Process related information Object dependencies of type procedures should be used instead of type actions. It's recommended to substitute existing actions by procedures in the configuration models. Class nodes should be used in Material BOM items instead of "Classification as selection condition". It's recommended to make this substitution also in existing material BOMs. Transaction not available in SAP S/4HANA on-premise edition 1511 CU51E -> Included in CU51 CU52 -> Included in CU51 CU52E -> Included in CU51 CU55 -> Obsolete CU80 -> Use PMEVC instead CUMODEL -> Use PMEVC instead Required and Recommended Action(s) None Related SAP Notes Custom Code related information SAP Notes: ,

110 Classification Description With SAP S/4HANA, on-premise edition 1511 transactions of the Classification is renovated so that transactions may have changed functionality or may be completely removed within SAP Product Lifecycle Management (SAP PLM). User Defined Data Type (031) for characteristics has been removed. Rename Characteristic functionality has been disabled. Parameter Effectivity has been hidden. Due to security reasons batch import has been limited and batch import is possible only from presentation server Business Process related information Parameter Effectivity has been hidden for classification in the SAP S/4HANA, on-premise edition 1511 shipment. As an alternative solution, Variant Configuration shall be used with object based dependencies. Transaction not available in SAP S/4HANA on-premise edition 1511 CL20 CL22 CL24 CL6E CL6F CL6G CL6R CLB1 CLB2 CLB3 GENC O005 O021 O023 Assign Object to Classes Allocate Class to Classes Assign Objects to One Class Copy DIN Standard Copy DIN Characteristic Data Create Material w. DIN Char. Data Direct Input for Classes Batch Input for Classification Direct Input for Classification Display Classification File Generate Source Code C CL Characteristic Default Settings Class Data Transfer Display Class Maintenance Data File 110

111 O024 Transfer Class Data: Direct Input S_ABA_ S_ABA_ S_ALR_ S_ALR_ IMG Activity: SIMG_CFMENUO000O1CL IMG Activity: SIMG_CFMENUO000O008 S_ALR_ IMG Activity: SIMG_CFMENUO000O016 S_ALR_ IMG Activity: SIMG_CFMENUO000O002 S_ALR_ IMG Activity: SIMG_CFMENUO000SMOD S_ALR_ IMG Activity: SIMG_CFMENUO000MERK S_ALR_ IMG Activity: SIMG_CFMENUO000KLAS S_ALR_ IMG Activity: SIMG_CFMENUO S_ALR_ IMG Activity: SIMG_CFMENUO000O12A S_ALR_ IMG Activity: SIMG_CFMENUO000O003 S_ALR_ IMG Activity: SIMG_CFMENUO000O005 S_ALR_ IMG Activity: SIMG_CFMENUO000O004 S_ALR_ IMG Activity: SIMG_CFMENUO000O017 S_ALR_ IMG Activity: SIMG_CFMENUO000O006 S_ALR_ S_AX6_ IMG Activity: BWCLBW_CTBW S_S6B_ IMG Activity: CTWUL_LOCDEP S_S6B_ IMG Activity: CTWUL_LOCDEP S_S6B_ S_S6B_ S_S6B_

112 CLNA CT01 CT02 CT03 CT05 CT06 CT11 CT21 CT22 CT23 CT24 CT25 CTCP Namespace f. Classes/Characteristics Create Characteristic Change Characteristic Display Characteristic Create Characteristic Display Characteristic CT12 Batch Input for Characteristics Maint. Seq. File for Characteristics Display Chars for Change Number Display Change Numbers Used Where-Used List of Chars in Deps Copy C tables for characteristics S_ABA_ CL2A CL6B CL6BN CL6C CL6D CL6H CL6M CL6O CLHP CL2B Classification Status Object List Object List (ALV) Class Hierarchy Classes Without Superior Class Classes: Reassign/Split/Merge Delete Class (with Assignments) Plus-Minus Object Display Graphical Hierarchy Maintenance Class Types 112

113 CL6A CL6AN CL6Q CL6T CLCP Class List Class List (ALV) Where-Used List for Classes Copy Text for Classes Copy Classification C Tables S_ALR_ S_ALR_ CLVL CTBW CL21 CL23 CL25 CL26 CL30 CLGT Maintain Variable Lists Table Maint. for BW and Classes Display Object in Classes Display Class for Classes Display Objects in Class Mass Release of Assignments Find Objects in Classes Set Up Tables for Search Required and Recommended Action(s) No special actions required. In case hidden functionality is needed, it can be reactivated by following the steps in SAP Note Related SAP Notes Custom Code related information SAP Note: IPPE-BOM Converter Description With SAP S/4HANA, on-premise edition 1511 the IPPE-BOM Converter within SAP Product Lifecycle Management (SAP PLM) is not available. Customers using this functionality might consider using Product 113

114 Structure Management and Product Structure Synchronization instead of ippe and BOM Converter. Please observe that ippe and PSM are two separate applications and a migration might be necessary Business Process related information ippe CMP structures cannot be converted to classic BOMs anymore. Transfer of ippe to BOM Transaction not available in SAP S/4HANA on-premise edition 1511 PPECS Required and Recommended Action(s) Customers using this functionality should evaluate if Product Structure Management and Product Structure Synchronization fit their needs Related SAP Notes Custom Code related information SAP Note: BOM, Routing, Production Version Description With SAP S/4HANA, on-premise edition 1511, the functional relation between Bill of Material (BOM), Routing and Production Version has changed. The Customizing for date validity is no longer considered for BOM explosion. Instead, only BOMs with valid production version are considered during BOM explosion. Therefore, it is now mandatory for Manufacturing BOMs to maintain the product version for correct BOM explosion. For all BOMs in the system, it is recommended to maintain product versions using the report Product Version Migration for BOM (transaction code CS_BOM_PRODVER_MIGRATION). Maintaining product version enables to combine the BOM and Routing entities which helps in streamlining the release/ revision process in future. The customizing that determines the items valid for BOM explosion now has the default value 2 (Version with latest valid-from date). This customizing is available in Define Modification Parameters under Production -> Basic Data -> Bill of Material -> Control Data for Bills of Material Business Process related information BOM Explosion for Manufacturing BOM will depend on Production Versions only. Manufacturing BOM determination can only happen via production version. 114

115 Required and Recommended Action(s) An interactive migration report has been provided to create new production versions based on existing BOM data. Run Report CS_BOM_PRODVER_MIGRATION to create Production Versions Related SAP Notes Custom Code related information SAP Notes: , SAP PLM Recipe Development Description With SAP S/4HANA, on-premise edition 1511 following functional changes were done: 1) Maintenance a specification using the Fast Entry Screen is not available. A successor is planned. 2) The compliance check functionality will the ABAP based implementation and will not support and will not need the EH&S Expert Server Business Process related information Fast Entry Screen: This tool cannot be used however there's a successor product planned. Compliance check without expert server: A successor product is also planned, currently functionality is limited to use without expert server, which means a narrower functionality. No influence on Business Processes expected. Users shall use the already available maintenance for the specification Related SAP Notes Custom Code related information SAP Note: PH_Sample iview Description The iview was as an option for Pharmaceutical Sales Reps who were running CRM Mobile Sales to manage their inventory of free samples. This functionality is not available within SAP S/4HANA, on-premise edition 1511 without a functional equivalent Business Process related information Business Processes using this solution will no longer work. An alternative solution has to be developed in a customer project. 115

116 Required and Recommended Action(s) Customers using the solution have to develop their own UI on their platform of choice to be deployed to mobile devices of their sales reps Related SAP Notes Custom Code related information As this is an iview, customers were not able to develop custom code Engineering Change Management ECR/ECO Description With SAP S/4HANA, on-premise edition 1511 the current the Engineering Change Record / Engineering Change Order functionality within SAP Product Lifecycle Management (SAP PLM) is not available anymore. It is recommended for new customers to use Engineering Record instead for tracking, approving and facilitating (change management) purposes Business Process related information Managing (tracking, approving and facilitating) changes will still be possible. The Engineering Record (only available on Web UI) shall be used for this. The change number will serve to identify the explicit changes and the Engineering Record is to be used to manage the whole process. The approval process, the objects to be changed will all be part of the Engineering Record, while the change number will solely be used to facilitate the changes after approval has been given. Transaction not available in SAP S/4HANA on-premise edition 1511 CC31 - Create Change Request CC32 - Change Change Request CC33 - Display Change Request CC62 - Conversion of change packages OS72 - ECH: Workflow for ECR/ECO OS73 - ECH: Workflow for Object Mgmt Record Required and Recommended Action(s) Set up Engineering Record (ER Types, status network, BRF+) and Process Route (Activities, services, process route templates, BRF+) Engineering Change Management Change Sequence Graph Description With SAP S/4HANA, on-premise edition 1511 the current Change Sequence Graph functionality within SAP Product Lifecycle Management (SAP PLM) is not available anymore. 116

117 Business Process related information No influence on business processes expected. Transaction not available in SAP S/4HANA on-premise edition 1511 CCSEQ_CSGUPD - Update Change Sequence Graph CCSEQ_CUST - Activate Change Sequence Graph CCSEQ_CYCLE - Display Cycles Required and Recommended Action(s) None Engineering Workbench Description With SAP S/4HANA, on-premise edition 1511 the Engineering Workbench is not the target architecture and will not receive any further updates Business Process related information Customers using Engineering Workbench today will be required to use alternative UIs, e.g. in Fiori, Web UI or GUI to maintain BOMs and Routings. Transaction not available in SAP S/4HANA on-premise edition 1511 CEWB (affected but not removed) Required and Recommended Action(s) Please use another transaction in WUI in place of Engineering Workbench Collaborative Engineering Description With SAP S/4HANA, on-premise edition 1511 the Collaborative Engineering is not available. SAP recommends to evaluate SAP Mobile Documents as a substitute for selected collaboration scenarios. 7 Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional equivalent is available. 117

118 Business Process related information The Collaborative Engineering Functionality is not available and current alternative solutions like e.g. Mobile Documents should be evaluated as alternatives. Transaction not available in SAP S/4HANA on-premise edition 1511 CE01 CE02 CE03 CEP_R3_MON Required and Recommended Action(s) Evaluate Mobile Document as alternative for collaboration Related SAP Notes Custom Code related information SAP Note: ippe Time Analysis Description In SAP S/4HANA, the integration of time analysis tools into the ippe Workbench is not available. This integration was previously available via the customizing transaction OPPE07. This transaction will be removed Business Process related information Transaction not available in SAP S/4HANA on-premise edition 1511 OPPE Required and Recommended Action(s) If the integration of a time analysis tool into the ippe workbench was done via transaction OPPE07, this integration has to be done by customer own implementation now Related SAP Notes Custom Code related information Transaction OPPE07 is not available any longer 118

119 Integration to SAP Portfolio and Project Management Description SAP Portfolio and Project Management is integrated with ERP in various ways. SAP plans to simplify and improve this integration in the way to ease configuration and leverage HANA capabilities 8. The integration topics are: Integration of Portfolio Management with ERP Project System, ERP Plant Maintenance, ERP Financials etc. Object Links between SAP Portfolio and Project Management objects and ERP objects (various) Integration of Project Management with ERP Financials via the Generic Cost Collector/Accounting Object Manager Integration of Project Management with PLM Document Management CATS Integration for time recording For the time being, customers can continue using the integration as it is offered today. Screen enhancements were done (not necessary complete) in: Internal Order displaying data from project in PPM Value help for internal orders to search for orders created by PPM Project System projects displaying data from project in PPM CATS displaying project and task from PPM Configuration in customizing tree: 8 Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional equivalent is not available yet. 119

120 Controlling cockpit for "Collaboration Projects": (Only the first transaction "Cockpit for Controlling Integration (cprojects)" is affected, the others are standard CO transactions.) Business Process related information No influence on business processes expected Required and Recommended Action(s) None 120