White Paper
Document Version: 1.0 – 2016-10-31
Simplification List for SAP S/4HANA 1610
Initial Shipment Stack
CUSTOMER
Table of Content
1
1.1
INTRODUCTION ...................................................................................................................... 15
Purpose of the Document .................................................................................................................. 16
1.2
General Topics for the Simplification List ........................................................................................... 16
1.2.1 Simplification Item Information .......................................................................................................... 17
1.2.2 Simplification Categories ..................................................................................................................... 17
1.2.3 Related Business Impact Note ............................................................................................................. 18
1.3
System Conversion Sequence ............................................................................................................ 18
1.3.1 Maintenance Planner .......................................................................................................................... 18
1.3.2 Pre-Check Relevance ........................................................................................................................... 19
1.3.3 Custom Code-Related Information ...................................................................................................... 19
1.4
2
The Simplification List 1610 – this document ..................................................................................... 19
THE SIMPLIFICATION LIST FOR SAP S/4HANA 1610 ................................................ 21
2.1
Simplification List - Per Application Area ........................................................................................... 21
2.1.1 Master Data ......................................................................................................................................... 21
2.1.1.1
Business Partner Approach ......................................................................................................... 21
2.1.1.2
Simplified Product Master Table................................................................................................. 23
2.1.1.3
Material Number Field Length Extension ................................................................................... 24
2.1.1.4
Simplification of copy/reference handling .................................................................................. 29
2.1.1.5
Foreign Trade fields in Material Master ..................................................................................... 30
2.1.1.6
MRP fields in Material Master .................................................................................................... 30
2.1.1.7
Material Type SERV ..................................................................................................................... 31
2.1.1.8
Product Catalogue functionality for integration with Internet Application Components .......... 34
2.1.1.9
Product Catalogue ...................................................................................................................... 34
2.1.1.10 Object Identifier Type Code ........................................................................................................ 35
2.1.1.11 MDM 3.0 integration .................................................................................................................. 36
2.1.1.12 SRM Product Master ................................................................................................................... 36
2.1.1.13 Logistics Batch Management ...................................................................................................... 37
2.1.1.14 Classifications functionality of customer master ........................................................................ 38
2.1.1.15 Business partner data exchange between SAP CRM and SAP S/4HANA .................................... 38
2.1.1.16 External Interfacing BAPIs, IMG Nodes and BOR objects of SCM ............................................... 40
2.1.1.17 HANA-based Analytics for Master Data Governance .................................................................. 45
2.1.1.18 Business Partner Time Dependency ........................................................................................... 45
2.1.2 Sales & Distribution ............................................................................................................................. 47
2.1.2.1
Business Role Internal Sales Representative .............................................................................. 47
2.1.2.2
Webshops by Internet Sales or Web Channel Experience Management ................................... 47
2.1.2.3
Commodity Management Sales .................................................................................................. 49
2.1.2.4
Sales Activities ............................................................................................................................ 50
2.1.2.5
Billing Document Output Management ...................................................................................... 52
Simplification List for SAP S/4HANA 1610
2
2.1.2.6
SD Rebate Processing replaced by Settlement Management ..................................................... 53
2.1.2.7
Miscellaneous minor functionalities in SD Area ......................................................................... 53
2.1.2.8
SD Complaint Handling ............................................................................................................... 54
2.1.2.9
SD – FI/CA Integration with distributed systems ........................................................................ 55
2.1.2.10 SD Simplified Data Models .......................................................................................................... 55
2.1.2.11 Enterprise Search in SD and LE ................................................................................................... 57
2.1.2.12 Data Model Changes in SD Pricing .............................................................................................. 58
2.1.2.13 Foreign Trade .............................................................................................................................. 60
2.1.2.14 Credit Management .................................................................................................................... 66
2.1.2.15 ERP SD Revenue Recognition ...................................................................................................... 68
2.1.2.16 Optimization of SD Rebate Processing for TPM Customers ........................................................ 70
2.1.2.17 Simplification in SD Analytics ...................................................................................................... 71
2.1.2.18 Advanced Order Processing and Billing for Contractors to the public sector ............................. 72
2.1.2.19 Operational Data Provisioning .................................................................................................... 73
2.1.3 Customer Service ................................................................................................................................. 74
2.1.3.1
Customer Interaction Center (CIC) .............................................................................................. 74
2.1.3.2
PH Sample iView ......................................................................................................................... 74
2.1.4 Procurement ........................................................................................................................................ 75
2.1.4.1
MM-PUR WebDynpro Applications ............................................................................................ 75
2.1.4.2
Classic MM-PUR GUI Transactions replacement ........................................................................ 76
2.1.4.3
Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes .......................... 77
2.1.4.4
Supplier Distribution via MDG-S ................................................................................................. 78
2.1.4.5
Authority Concept for Supplier Invoice....................................................................................... 78
2.1.4.6
Foreign Trade within SAP S/4HANA Procurement ...................................................................... 79
2.1.4.7
Commodity Management Procurement ..................................................................................... 80
2.1.4.8
Automatic Document Adjustment .............................................................................................. 81
2.1.4.9
RFQ Simplified Transaction ......................................................................................................... 83
2.1.4.10 Co-Deployment of SAP SRM ....................................................................................................... 84
2.1.4.11 Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC) ............................................ 84
2.1.4.12 Vendor evaluation based on LIS.................................................................................................. 85
2.1.4.13 Subsequent Settlement - Vendor Rebate Arrangements ........................................................... 86
2.1.4.14 ERP Shopping Cart....................................................................................................................... 86
2.1.4.15 Internet Application Components (IAC) ...................................................................................... 87
2.1.4.16 MDM Catalog .............................................................................................................................. 88
2.1.4.17 Pricing Data Model Simplification ............................................................................................... 88
2.1.4.18 Output Management Adoption in Purchase Order .................................................................... 89
2.1.5 Logistics – AB ....................................................................................................................................... 90
2.1.5.1
Agency Business .......................................................................................................................... 90
2.1.6 Logistics – ATP ..................................................................................................................................... 98
2.1.6.1
New advanced ATP in SAP S/4HANA – Table VBBS..................................................................... 98
2.1.6.2
icon (E2open) .............................................................................................................................. 99
2.1.6.3
New fashion solution .................................................................................................................. 99
2.1.7 Logistics - Direct Store Delivery (LE-DSD) .......................................................................................... 100
2.1.7.1
Direct Store Delivery ................................................................................................................. 100
2.1.8 Logistics - Environment, Health & Safety (EHS) ................................................................................. 101
2.1.8.1
Deprecation of EHS Data Series and Amounts .......................................................................... 101
Simplification List for SAP S/4HANA 1610
3
2.1.8.2
Deprecation of 'Inspect Safety Control' Fiori app ..................................................................... 101
2.1.8.3
Deprecation of 'Retrieve Safety Information' Fiori app ............................................................ 102
2.1.8.4
Simplification of Authorizations in Incident Management ....................................................... 102
2.1.8.5
Removal of EHS Home Screens ................................................................................................. 104
2.1.8.6
Simplification of Incident Management workflows .................................................................. 104
2.1.8.7
Changed data model for listed substances ............................................................................... 105
2.1.8.8
Industrial Hygiene and EC interfaces ........................................................................................ 106
2.1.8.9
Occupational Health ................................................................................................................. 107
2.1.8.10 Waste Management ................................................................................................................. 108
2.1.8.11 Simplification in Incident Management and Risk Assessment .................................................. 109
2.1.8.12 Removal of EHS workflows for requesting controls, impacts, agents ...................................... 110
2.1.8.13 Responsible person for Planned Maintenance at EHS locations .............................................. 111
2.1.8.14 Remote Integrationsszenarien mit EHS Health and Safety Management ................................ 112
2.1.8.15 Collection of various small and medium sized changes in EHS ................................................. 113
2.1.9 Logistics – GT ..................................................................................................................................... 113
2.1.9.1
Global Trade Management ....................................................................................................... 113
2.1.10
Logistics Material Management Inventory Management (MM-IM) ............................................. 115
2.1.10.1 DATA MODEL IN INVENTORY MANAGEMENT (MM-IM)........................................................... 115
2.1.10.2 AVAILABILITY OF TRANSACTIONS IN MM-IM ............................................................................ 121
2.1.10.3 Material Ledger Obligatory for Material Valuation .................................................................. 121
2.1.10.4 Material Valuation - Statistical moving average price .............................................................. 124
2.1.10.5 Performance optimizations within Material Document Processing - lock behaviour .............. 125
2.1.10.6 Material Valuation Data Model Simplification in S/4HANA 1610 and Higher .......................... 130
2.1.10.7 Goods movements without exclusive locking by material valuation........................................ 133
2.1.10.8 CWM in S4HANA ....................................................................................................................... 135
2.1.11
Logistics – PLM .............................................................................................................................. 136
2.1.11.1 Engineering Desktop (EDesk) .................................................................................................... 136
2.1.11.2 DMS - STEP Support .................................................................................................................. 137
2.1.11.3 DMS Documents@WEB ............................................................................................................ 137
2.1.11.4 Variant Configuration................................................................................................................ 138
2.1.11.5 Classification ............................................................................................................................. 139
2.1.11.6 IPPE-BOM Converter ................................................................................................................. 141
2.1.11.7 BOM, Routing, Production Version ........................................................................................... 142
2.1.11.8 Engineering Change Management ECR/ECO ............................................................................ 143
2.1.11.9 Enterprise Search in SAP Product Lifecycle Management (SAP PLM) ....................................... 144
2.1.11.10
Engineering Change Management Change Sequence Graph ............................................... 145
2.1.11.11
Engineering Workbench ....................................................................................................... 145
2.1.11.12
Collaborative Engineering .................................................................................................... 146
2.1.11.13
iPPE Time Analysis ................................................................................................................ 147
2.1.11.14
Integration to SAP Portfolio and Project Management ........................................................ 147
2.1.11.15
Routing Component Assignment .......................................................................................... 148
2.1.11.16
Release Management Framework........................................................................................ 148
2.1.11.17
Engineering Record............................................................................................................... 149
2.1.11.18
Assemblies ............................................................................................................................ 149
2.1.11.19
Product Designer Workbench .............................................................................................. 150
2.1.11.20
Access Control Management (ACM)..................................................................................... 151
Simplification List for SAP S/4HANA 1610
4
2.1.11.21
cFolders ................................................................................................................................ 152
2.1.11.22
cDesk .................................................................................................................................... 152
2.1.11.23
Recipe Management............................................................................................................. 153
2.1.11.24
Engineering Client Viewer (ECL) ........................................................................................... 154
2.1.11.25
Easy Document Management (Easy DMS) ........................................................................... 155
2.1.11.26
SAP PLM Recipe Development ............................................................................................. 156
2.1.12
Logistics – PP ................................................................................................................................. 156
2.1.12.1 ERP Line-Balancing and Sequencing ......................................................................................... 156
2.1.12.2 MRP in HANA ............................................................................................................................ 157
2.1.12.3 Planning File .............................................................................................................................. 161
2.1.12.4 Total Dependent Requirements................................................................................................ 162
2.1.12.5 Forecast Based Planning ........................................................................................................... 163
2.1.12.6 Demand Forecasting ................................................................................................................. 164
2.1.12.7 Release status for different RFC function modules revoked .................................................... 164
2.1.12.8 Computer Aided Processing Planning (CAP) ............................................................................. 165
2.1.12.9 ABAP-List-Based PI-Sheets ........................................................................................................ 166
2.1.12.10
ANSI/ISA S95 Interface ......................................................................................................... 166
2.1.12.11
PP-MRP - Subcontracting ...................................................................................................... 167
2.1.12.12
Digital Signature ................................................................................................................... 168
2.1.12.13
Electronic Records ................................................................................................................ 169
2.1.12.14
Downtimes Functionality ...................................................................................................... 169
2.1.12.15
MiniApps PP-PI ..................................................................................................................... 170
2.1.12.16
Process Data Evaluation (PP-PI-PMA) ................................................................................... 170
2.1.12.17
Campaign Weighing and Dispensing .................................................................................... 171
2.1.12.18
Production Campaign (ERP) .................................................................................................. 171
2.1.12.19
Electronic Batch Record ........................................................................................................ 171
2.1.12.20
Process Messages ................................................................................................................. 172
2.1.12.21
Control Recipes/Instructions ................................................................................................ 172
2.1.12.22
Storage Location MRP .......................................................................................................... 173
2.1.12.23
Process Operator Cockpits ................................................................................................... 174
2.1.12.24
Material Identification/Reconciliation.................................................................................. 174
2.1.12.25
Flow Manufacturing ............................................................................................................. 174
2.1.12.26
Process Flow Scheduling (PP-PI) ........................................................................................... 175
2.1.12.27
Rate and Rough-Cut Planning ............................................................................................... 175
2.1.12.28
Planning Horizon .................................................................................................................. 177
2.1.12.29
Batch History ........................................................................................................................ 177
2.1.12.30
Selected Business Functions in PP area ................................................................................ 178
2.1.12.31
External Interfaces in PP ....................................................................................................... 179
2.1.12.32
Graphical Planning Table ...................................................................................................... 180
2.1.12.33
Logistic Information System in PP ........................................................................................ 181
2.1.12.34
Sales and Operation Planning ............................................................................................... 182
2.1.12.35
Simplified Sourcing ............................................................................................................... 183
2.1.12.36
Browser-based Process Instruction-Sheets/Electronic Work Instructions ........................... 187
2.1.12.37
Internet Kanban .................................................................................................................... 188
2.1.13
Logistics – PS ................................................................................................................................. 188
2.1.13.1 Simplification of Date Planning Transactions ........................................................................... 188
Simplification List for SAP S/4HANA 1610
5
2.1.13.2 Workforce Planning .................................................................................................................. 189
2.1.13.3 Progress Tracking & Monitoring Dates ..................................................................................... 190
2.1.13.4 Project Claim Factsheet ............................................................................................................ 190
2.1.13.5 Project Reporting ...................................................................................................................... 191
2.1.13.6 Selected Project System Interfaces ........................................................................................... 195
2.1.13.7 Construction Progress Report and Valuation............................................................................ 196
2.1.13.8 Project System ITS Services ....................................................................................................... 197
2.1.13.9 Selected PS Business Function Capabilities .............................................................................. 197
2.1.13.10
Selected Logistics Capabilities .............................................................................................. 198
2.1.13.11
Simplification of maintenance transactions ......................................................................... 199
2.1.13.12
Selected Project System BAPIs ............................................................................................. 200
2.1.13.13
Handling Large Projects Business Functions ......................................................................... 200
2.1.13.14
Navigation to Project Builder instead of special maintenance functions ............................. 201
2.1.13.15
Production Resources and Tools functions for projects ....................................................... 202
2.1.13.16
Project Planning Board, Gantt-Chart, Hierarchy and Network Graphics .............................. 203
2.1.13.17
Current simulation functions in project system ................................................................... 203
2.1.13.18
Specific PS archiving transactions ......................................................................................... 204
2.1.13.19
Project texts (PS texts) .......................................................................................................... 205
2.1.13.20
Claim Management .............................................................................................................. 205
2.1.13.21
Selected project financial planning and control functions ................................................... 206
2.1.14
Logistics – PSS................................................................................................................................ 207
2.1.14.1 MyApps for Product Safety and Dangerous Goods Management ............................................ 207
2.1.14.2 PS&S SARA Reports ................................................................................................................... 208
2.1.14.3 Substance Volume Tracking Selection Criteria based on tables VBUK and VB ......................... 208
2.1.14.4 Simplification in Product Compliance for Discrete Industry ..................................................... 209
2.1.14.5 QM Interface ............................................................................................................................. 211
2.1.14.6 IUCLID5 Interface ...................................................................................................................... 211
2.1.14.7 PS&S Enterprise Search Model ................................................................................................. 211
2.1.14.8 Hazardous Substance Management ......................................................................................... 212
2.1.14.9 Add-On: SAP Product and REACH Compliance (SPRC) .............................................................. 212
2.1.14.10
Add-On: EHS Web-Interface ................................................................................................. 213
2.1.14.11
Add-On: Genifix (Labelling solution) ..................................................................................... 214
2.1.14.12
BW Extractors for Dangerous Goods Management and Specification Managemen ............ 214
2.1.14.13
PS&S Key Figures .................................................................................................................. 214
2.1.15
Logistics – Plant Maintenance ....................................................................................................... 215
2.1.15.1 LIS in EAM ................................................................................................................................. 215
2.1.15.2 Download Data in MS Access out of List ................................................................................... 215
2.1.15.3 Scheduling of Maintenance Plan .............................................................................................. 216
2.1.15.4 Mobile Asset Management (MAM) .......................................................................................... 216
2.1.15.5 Batch Input for Enterprise Asset Management (EAM) ............................................................. 216
2.1.15.6 Change Order and Operations .................................................................................................. 217
2.1.15.7 WebDynpro Application for Maintenance Planner (<= EhP4) .................................................. 217
2.1.15.8 Enterprise Search in EAM and PLM........................................................................................... 218
2.1.16
Logistics – Quality Management ................................................................................................... 218
2.1.16.1 Quality Management Information System (QMIS) ................................................................... 218
2.1.16.2 Quality Inspection Engine (QIE) ................................................................................................ 219
Simplification List for SAP S/4HANA 1610
6
2.1.16.3 Results Recording...................................................................................................................... 219
2.1.16.4 ITS services in QM ..................................................................................................................... 220
2.1.16.5 QM WEB Workplace (MiniApps) based on ITS Services ............................................................ 221
2.1.17
Logistics - Execution Transportation ............................................................................................. 221
2.1.17.1 Transportation (LE-TRA) ............................................................................................................ 221
2.1.18
Logistics – Warehouse Management ............................................................................................ 222
2.1.18.1 Warehouse Management (WM) ............................................................................................... 222
2.1.19
Financial – General ........................................................................................................................ 222
2.1.19.1 DATA MODEL CHANGES IN FIN ................................................................................................. 222
2.1.19.2 REPLACED TRANSACTION CODES AND PROGRAMS IN FIN ....................................................... 228
2.1.20
Financial – General Ledger ............................................................................................................ 230
2.1.20.1 GENERAL LEDGER ...................................................................................................................... 230
2.1.20.2 SAP INVOICE AND GOODS RECEIPT RECONCILIATION .............................................................. 231
2.1.20.3 SAP HANA ODP ON HANA CALC VIEW-BASED REPORTING....................................................... 231
2.1.20.4 Closing Cockpit with S/4 HANA OP ........................................................................................... 232
2.1.20.5 Currencies in Universal Journal ................................................................................................. 232
2.1.21
Financials - Accounts Payable/Accounts Receivable ..................................................................... 236
2.1.21.1 SAP Working Capital Analytics/DSO and DPO ........................................................................... 236
2.1.21.2 Integration with FSCM Biller Direct (FI-AR) ............................................................................... 236
2.1.21.3 Integration with FSCM Biller Direct (FI-AP) ............................................................................... 237
2.1.22
Financial - Asset Accounting .......................................................................................................... 237
2.1.22.1 DATA STRUCTURE CHANGES IN ASSET ACCOUNTING .............................................................. 237
2.1.22.2 ASSET ACCOUNTING ................................................................................................................. 238
2.1.22.3 INTEGRATION TO LEASE ACCOUNTING ENGINE (LAE) .............................................................. 238
2.1.22.4 JOINT VENTURE ACCOUNTING (JVA) ........................................................................................ 238
2.1.22.5 SELECTED BUSINESS FUNCTIONS IN FINANCIAL ACCOUNTING (FI-GL AND FI-AA) ................... 239
2.1.23
Financial - Cash Management ....................................................................................................... 239
2.1.23.1 CASH MANAGEMENT - GENERAL .............................................................................................. 239
2.1.24
Financial – Controlling ................................................................................................................... 246
2.1.24.1 Reference and Simulation Costing ............................................................................................ 246
2.1.24.2 Summarization Hierarchies in Controlling ................................................................................ 247
2.1.24.3 Technical Changes in Material Ledger with Actual Costing ...................................................... 248
2.1.24.4 TECHNICAL CHANGES IN CONTROLLING ................................................................................... 253
2.1.24.5 PROFIT AND LOSS PLANNING AND PROFIT CENTER PLANNING ............................................... 254
2.1.24.6 ACTIVITY-BASED COSTING ........................................................................................................ 256
2.1.24.7 GENERAL COST OBJECTS AND COST OBJECT HIERARCHIES ...................................................... 257
2.1.24.8 TRANSFER PRICES/ PARALLEL DELTA VERSIONS ....................................................................... 258
2.1.24.9 COST ELEMENTS ........................................................................................................................ 259
2.1.24.10
Reporting/Analytics in Controlling ....................................................................................... 261
2.1.24.11
Profitability Analysis ............................................................................................................. 262
2.1.25
Financials - International Trade ..................................................................................................... 264
2.1.25.1 Material classification with commodity codes ......................................................................... 264
2.1.26
Financials - Treasury and Risk Management ................................................................................. 264
2.1.26.1 Drilldown Reporting in Treasury and Risk Management .......................................................... 264
2.1.26.2 Quantity Ledger Always Active for Money Market Transactions ............................................. 265
2.1.26.3 Several Kinds of Financial Objects Disabled .............................................................................. 265
Simplification List for SAP S/4HANA 1610
7
2.1.26.4 Accrual/Deferral of Expenses and Revenues ............................................................................ 265
2.1.26.5 Fiduciary Deposits ..................................................................................................................... 265
2.1.26.6 Drawable Bonds ........................................................................................................................ 265
2.1.26.7 Master Agreements .................................................................................................................. 266
2.1.26.8 Offers ........................................................................................................................................ 266
2.1.26.9 Simulation in Transaction Management ................................................................................... 266
2.1.26.10
Correspondence Functionality ............................................................................................. 266
2.1.26.11
Interest Rate and Yield Curve Functionality ......................................................................... 268
2.1.26.12
Commodity Risk Management ............................................................................................. 269
2.1.26.13
Credit Risk Analyzer Link to Cash Management ................................................................... 269
2.1.26.14
Exposure Management 1.0................................................................................................... 270
2.1.27
Financials – Miscellaneous ............................................................................................................ 271
2.1.27.1 Credit Management .................................................................................................................. 271
2.1.27.2 Technical Changes in Material Ledger ...................................................................................... 273
2.1.27.3 Real Estate Classic ..................................................................................................................... 274
2.1.27.4 SAP Data Aging for SAP S/4HANA Finance ................................................................................ 275
2.1.27.5 Conversion to S/4HANA 1610 Material Ledger and Actual Costing .......................................... 276
2.1.28
Globalization ................................................................................................................................. 277
2.1.28.1 Globalization – Financials.......................................................................................................... 277
2.1.28.2 Globalization – Logistics ............................................................................................................ 278
2.1.29
Human Ressource.......................................................................................................................... 278
2.1.29.1 General HCM Approach within SAP S/4HANA .......................................................................... 278
2.1.29.2 Conversion of Employees to Business Partners ........................................................................ 279
2.1.29.3 SAP Learning Solution ............................................................................................................... 280
2.1.29.4 SAP E-Recruiting ........................................................................................................................ 280
2.1.29.5 Java-Based ESS and MSS ........................................................................................................... 280
2.1.30
Industry – Cross Industry Functionality ......................................................................................... 280
2.1.30.1 BRIM - Billing of Event Data Records (EDR) .............................................................................. 280
2.1.30.2 BRIM - Common Object Layer (COL) ......................................................................................... 281
2.1.30.3 BRIM - Integration with FSCM Biller Direct (FI-CA) ................................................................... 281
2.1.30.4 BRIM - Solution Sales and Billing............................................................................................... 282
2.1.30.5 BRIM – Immediate Master Data Replication to SAP Convergent Charging .............................. 282
2.1.31
Industry Banking............................................................................................................................ 283
2.1.31.1 SEM Banking ............................................................................................................................. 283
2.1.32
Industry Beverage ......................................................................................................................... 284
2.1.32.1 IS-Beverage Cleanup ................................................................................................................. 284
2.1.32.2 IS-Beverage solution ................................................................................................................. 284
2.1.32.3 Beverage Empties Management and Pendulum List ................................................................ 285
2.1.33
Defense & Security ........................................................................................................................ 287
2.1.33.1 DFPS eSOA services ................................................................................................................... 287
2.1.33.2 DFPS BI content ......................................................................................................................... 287
2.1.33.3 Integration of DFPS with Investigative Case Management (ICM) ............................................. 287
2.1.33.4 Integration of DFPS with Environmental Compliance ............................................................... 288
2.1.34
Industry DIMP – Aerospace & Defence ......................................................................................... 288
2.1.34.1 Collective Processing Pegging ................................................................................................... 288
2.1.34.2 Cost Distribution Processing ..................................................................................................... 289
Simplification List for SAP S/4HANA 1610
8
2.1.34.3 Manufacturer Part Number ...................................................................................................... 290
2.1.34.4 Flight Scheduling ....................................................................................................................... 293
2.1.34.5 Enhancements Actual Labour Costing / Time Recording .......................................................... 293
2.1.34.6 Enhancements Subcontracting Special Stock Types Not Available ........................................... 294
2.1.34.7 AECMA SPEC 2000M Military Version ...................................................................................... 294
2.1.35
Industry – Automotive .................................................................................................................. 295
2.1.35.1 Tracking Inbound ...................................................................................................................... 295
2.1.35.2 Supplier Workplace ................................................................................................................... 296
2.1.35.3 External Service Providers ........................................................................................................ 297
2.1.35.4 Cross-System Transit between Two Plants ............................................................................... 298
2.1.35.5 Long Material Number .............................................................................................................. 299
2.1.35.6 Material Version ....................................................................................................................... 300
2.1.35.7 Planning Regular Route Shipments ........................................................................................... 301
2.1.35.8 BSP based Dealer Portal ............................................................................................................ 302
2.1.36
Industry: DIMP – Engineering, Construction & Operations........................................................... 303
2.1.36.1 Obsolete BAPIS of Bill of Services (BOS) ................................................................................... 303
2.1.36.2 BOS Cost Transfer to PS removed ............................................................................................. 304
2.1.36.3 ZDEP ETM CATS package ........................................................................................................... 304
2.1.36.4 ETM General ............................................................................................................................. 304
2.1.36.5 ETM Tables obsolet ................................................................................................................... 305
2.1.36.6 REAL ESTATE SALES (HOMEBUILDING) ..................................................................................... 305
2.1.37
Industry: DIMP – High Tech ........................................................................................................... 306
2.1.37.1 Manufacturing Execution Systems ........................................................................................... 306
2.1.37.2 RosettaNet ................................................................................................................................ 306
2.1.37.3 Software License Management ................................................................................................ 307
2.1.37.4 Installed Base Management ..................................................................................................... 307
2.1.37.5 Contract Management Enhancements ..................................................................................... 307
2.1.37.6 Billing Process Enhancements................................................................................................... 308
2.1.37.7 Software Maintenance Processing ........................................................................................... 308
2.1.37.8 User Exits in DRM ...................................................................................................................... 308
2.1.37.9 Condition Technique in DRM: Rule Configuration .................................................................... 309
2.1.37.10
Manufacturer/Supplier Processes ........................................................................................ 309
2.1.37.11
Distributor/Reseller Processes ............................................................................................. 310
2.1.38
Industry DIMP – Mill ...................................................................................................................... 311
2.1.38.1 Non ferrous metal processing ................................................................................................... 311
2.1.38.2 Sales Order Versions ................................................................................................................. 311
2.1.38.3 Stock Overview and Object Search by Characteristics .............................................................. 312
2.1.38.4 Mill specific enhancements to scheduling PRTs ....................................................................... 313
2.1.38.5 Process batch ............................................................................................................................ 314
2.1.38.6 Fast data entry of characteristics in trading contract ............................................................... 315
2.1.38.7 Selection by characteristics in mass processing of orders ........................................................ 315
2.1.38.8 Fast data entry of characteristics in sales document ................................................................ 316
2.1.39
Industry Oil .................................................................................................................................... 317
2.1.39.1 Handling Oil & Gas obsolete t-codes Oil ................................................................................... 317
2.1.39.2 Optimization in Oil & Gas - TD module for STO and sales order with POD b............................ 318
2.1.39.3 Data Model in Oil & Gas Inventory management ..................................................................... 318
Simplification List for SAP S/4HANA 1610
9
2.1.39.4 Optimization in Oil&Gas - Inter company sales - Cross border excise duty .............................. 324
2.1.39.5 IS-OIL Proper sign operation for ACDOCA ................................................................................. 325
2.1.39.6 Unit of Measure (UoM) Group enahncement .......................................................................... 326
2.1.39.7 eNetting Deprecation ............................................................................................................... 327
2.1.39.8 Dynamic Scheduling deprecation ............................................................................................. 328
2.1.39.9 Financial Based netting deprecation ......................................................................................... 329
2.1.39.10
Oil & Gas inconsistency reports deprecation ....................................................................... 329
2.1.40
Industry Public Sector.................................................................................................................... 331
2.1.40.1 Authorization in Funds Management ....................................................................................... 331
2.1.40.2 Functionality German Local Authorities ................................................................................... 332
2.1.40.3 Former Budgeting System (FBS) in Funds Management .......................................................... 333
2.1.40.4 Functionality for FACTS I and FACTS II (Federal Agencies Centralized Trial Balance System) .. 334
2.1.40.5 Expenditure Certification .......................................................................................................... 335
2.1.40.6 Specific fields on Business Partner............................................................................................ 336
2.1.40.7 Fund Accounting based on Special Ledger................................................................................ 337
2.1.40.8 Data Structure changes in BCS .................................................................................................. 338
2.1.40.9 Funds Management Dimensions as part of the Universal Journal ........................................... 339
2.1.40.10
Functionality for BCS Multi-level Budget Structure .............................................................. 341
2.1.40.11
Functionality Average Daily Balance-based Distribution ...................................................... 342
2.1.41
Industry Retail & Fashion .............................................................................................................. 343
2.1.41.1 Logistical Variant ....................................................................................................................... 343
2.1.41.2 SAP Forecasting & Replenishment Integration ......................................................................... 343
2.1.41.3 Retail Power Lists ...................................................................................................................... 344
2.1.41.4 Retail Closed BW Scenarios....................................................................................................... 344
2.1.41.5 Retail Markdown Plan ............................................................................................................... 345
2.1.41.6 Retail Bonus Buy ....................................................................................................................... 345
2.1.41.7 Retail Sales Forecasting............................................................................................................. 346
2.1.41.8 Retail Order Optimizing: Load Build, Investment Buy .............................................................. 346
2.1.41.9 Retail Rapid Replenishment ...................................................................................................... 347
2.1.41.10
Retail Additionals .................................................................................................................. 347
2.1.41.11
Article Discontinuation ......................................................................................................... 348
2.1.41.12
GDS simplified Inbound Price Catalog Interface ................................................................... 349
2.1.41.13
Business Partner in Site Master ............................................................................................ 349
2.1.41.14
Article Hierarchy ................................................................................................................... 350
2.1.41.15
Market Basket Calculation .................................................................................................... 350
2.1.41.16
Merchandise and Assortment Planning (ERP based) ........................................................... 351
2.1.41.17
Retail Method of Accounting ................................................................................................ 351
2.1.41.18
Perishables Procurement ..................................................................................................... 352
2.1.41.19
Fresh Item Procurement ....................................................................................................... 353
2.1.41.20
Retail Ledger / Profit Center Analytics ................................................................................. 353
2.1.41.21
Goods Receipt Capacity Check ............................................................................................. 354
2.1.41.22
Online Store .......................................................................................................................... 354
2.1.41.23
Generic Article Harmonization ............................................................................................. 354
2.1.41.24
Retail Labeling ...................................................................................................................... 355
2.1.41.25
Seasonal Procurement.......................................................................................................... 355
2.1.41.26
Replenishment ...................................................................................................................... 356
Simplification List for SAP S/4HANA 1610
10
2.1.41.27
Retail Information System .................................................................................................... 356
2.1.41.28
SAP Retail Store .................................................................................................................... 357
2.1.41.29
Retail iViews ......................................................................................................................... 357
2.1.41.30
Prepack Allocation Planning ................................................................................................. 358
2.1.41.31
Assortment List ..................................................................................................................... 358
2.1.41.32
In-store food production integration ................................................................................... 359
2.1.41.33
PRICAT Outbound ................................................................................................................. 360
2.1.41.34
Retail Business Function Harmonization .............................................................................. 360
2.1.41.35
Retail Obsolete Transactions ................................................................................................ 360
2.1.41.36
Value and Quota Scales ........................................................................................................ 363
2.1.41.37
AIN ........................................................................................................................................ 363
2.1.41.38
Retail Season Conversion ..................................................................................................... 364
2.1.41.39
SAP Smart Business for Retail Promotion Execution ............................................................ 365
2.1.41.40
Retail Factsheets................................................................................................................... 366
2.1.41.41
Retail Short Text Replacement ............................................................................................. 366
2.1.41.42
Retail Store Fiori App ............................................................................................................ 366
2.1.41.43
SAP AFS Integration .............................................................................................................. 367
2.1.41.44
POS Outbound via Idoc WP_PLU .......................................................................................... 367
2.1.41.45
Valuation in Retail ................................................................................................................ 368
2.1.41.46
Retail Demand Management Integration ............................................................................. 369
2.1.42
Industry Telecommunication ........................................................................................................ 369
2.1.42.1 Lock and unlock services using IST_TDATA ............................................................................... 369
2.1.42.2 PORTAL ROLES FOR NETWORK LIFECYCLE MANAGEMENT (NLM) ........................................... 370
2.1.43
Industry Utilities ............................................................................................................................ 370
2.1.43.1 CVI Integration for SAP ISU ....................................................................................................... 370
2.1.43.2 Multichannel Foundation for Utilities ....................................................................................... 371
2.1.43.3 Monitoring Profile Value Import ............................................................................................... 372
2.1.43.4 Utilities Customer Electronic Services (UCES) ........................................................................... 373
2.1.43.5 Stock and Transaction ............................................................................................................... 373
2.1.43.6 IS-U Sales Processing ................................................................................................................. 373
2.1.43.7 Marketing - IS-U Loyalty Program ............................................................................................. 373
2.1.43.8 Front Office (EC20) .................................................................................................................... 373
2.1.43.9 GIS Business Connector ............................................................................................................ 374
2.1.43.10
Enterprise Services for SAP for Utilities (IS-U) ...................................................................... 374
2.1.43.11
Central and Eastern European localization for Utility & Telco ............................................. 374
2.1.44
Cross Topics ................................................................................................................................... 375
2.1.44.1 Output Management ................................................................................................................ 375
2.1.44.2 Analytics - SAP S/4HANA and SAP Business Warehouse Content............................................. 378
2.1.44.3 Enterprise Search ...................................................................................................................... 379
2.1.44.4 Internet Pricing and Configurator (SAP IPC) ............................................................................. 379
2.1.44.5 Job Scheduling .......................................................................................................................... 380
2.1.44.6 Legacy System Migration Workbench (LSMW) ......................................................................... 382
2.1.44.7 FIORI Application for SAP Business Suite powered by SAP HANA ............................................ 383
2.1.44.8 Social Intelligence ..................................................................................................................... 384
2.1.44.9 Custom Fields ............................................................................................................................ 385
2.1.44.10
Ariba Network Integration.................................................................................................... 385
Simplification List for SAP S/4HANA 1610
11
2.1.44.11
2.1.44.12
SAP HANA Live Reporting ..................................................................................................... 387
Side Panel functionality in SAP S/4HANA ............................................................................. 387
2.2
The Simplification List Items related to SAP Add-Ons ...................................................................... 390
2.2.1 SAP Portfolio and Project Management 1.0 for SAP S/4HANA ......................................................... 390
2.2.1.1
Web Dynpro Applications for Resource Maintenance in SAP PPM .......................................... 390
2.2.1.2
Workforce Deployment (WFD) integration in SAP Portfolio and Project Mana ....................... 390
2.2.1.3
Integration to SAP cFolders in SAP Portfolio and Project Management for ............................. 391
2.2.1.4
KM Documents in SAP Portfolio and Project Management for SAP S/4HANA ......................... 391
2.2.1.5
SRM Integration in SAP Portfolio and Project Management for SAP S/4HANA ........................ 392
2.2.1.6
cFolders not available anymore in SAP Portfolio and Project Management f .......................... 392
2.2.1.7
Global Settings in SAP Portfolio and Project Management for SAP S/4HANA .......................... 393
2.2.1.8
Fiori apps of UI FOR SAP PORTF PROJ MGMT 6.0 in SAP Portfolio and Projec ......................... 397
2.2.1.9
Portfolio Structure Graphic in SAP Portfolio and Project Management for ............................. 397
2.2.1.10 SAP Smart Forms in SAP Portfolio and Project Management for SAP S/4HANA ...................... 397
2.2.1.11 Resource Management Web Dynpro Views in SAP Portfolio and Project Manage .................. 398
2.2.1.12 WebDAV and EasyDMS Integration in SAP Portfolio and Project Management f .................... 398
2.2.1.13 SAP Portal Integration in SAP Portfolio and Project Management for SAP S ........................... 399
2.2.1.14 cRoom Integration in SAP Portfolio and Project Management for SAP S/4HAN ...................... 399
2.2.1.15 xPD Integration in SAP Portfolio and Project Management for SAP S/4HANA ......................... 399
2.2.1.16 Xcelsius Integration in SAP Portfolio and Project Management for SAP S/4 ............................ 400
2.2.1.17 SAP BusinessObjects Explorer Integration in SAP Portfolio and Project Ma ............................ 400
2.2.1.18 Project simulation in SAP Portfolio and Project Management for SAP S/4HA ......................... 401
2.2.1.19 Simplification of data model in SAP Portfolio and Project Management for ........................... 401
2.2.1.20 Deletion of obsolete packages in EPPM.................................................................................... 401
2.2.1.21 Business Partner in SAP Portfolio and Project Management for SAP S/4HANA ....................... 402
2.2.1.22 Simplified ACLs (Access Control Lists) concept in SAP Portfolio and Proj ................................. 402
2.2.1.23 SAP Web Dynpro usage in SAP Port. and Proj. Management for SAP S/4HANA ...................... 403
2.2.1.24 Changes compared to older releases than SAP Port. and Proj. Mngt. 6.1 ................................ 404
2.2.1.25 Not strategic functionalities within SAP S/4HANA.................................................................... 404
2.2.1.26 Control Plans in SAP Portfolio and Project Management for SAP S/4HANA ............................ 406
2.2.1.27 HTTP-Based Document Management in SAP Portfolio and Project Management f ................. 406
2.2.1.28 Object Links to SAP Environmental Compliance in SAP Portfolio and Projec ........................... 407
2.2.1.29 Microsoft Project Import/Export in SAP Portfolio and Project Management .......................... 407
3
3.1
APPENDIX ...............................................................................................................................408
Related Information – SAP Help....................................................................................................... 408
Simplification List for SAP S/4HANA 1610
12
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 “AP “ “T‘ATEGY
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 FORWARDLOOKING 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.
Simplification List for SAP S/4HANA 1610
13
REVISION LOG – SAP S/4HANA 1610 – INITIAL SHIPMENT
Version
1.0.
Initial
Version
Date
Remarks
Initial version of the Simplification List for SAP S/4HANA 1610.
The Simplification List 1610 spreadsheet (see SAP Note 2313884) does
contain the following information:
Simplification Items which are new with SAP S/4HANA 1610
201610-31
o
Items which are new and related to the industries Oil and Retail
(supported with SAP S/4HANA 1610)
o
Simplification Items related to SAP Add-On Portfolio and Project
Management (PPM)
o
Ne Co e ite s i “AP “/ HANA this i ludes items which
changed their simplification category – example: industry DIMPAutomotive – si plifi atio Lo g Mate ial Nu e
Simplification Items which are relevant for the upgrade from SAP
S/4HANA On-Premise edition 1511 to SAP S/4HANA 1610
Simplification List for SAP S/4HANA 1610
14
1 Introduction
“AP® “/ HANA is “AP s e t-generation business suite. As such, it is not a legal successor of any SAP
Business Suite product. It is a new product, built entirely on one of the most advanced in-memory
platforms today – SAP HANA® – and incorporates modern design principles through 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.
Through its approach to building SAP S/4HANA, SAP is re-architecting its solution for modern
business processes that the ever-increasing digitization of the world demands. Re-architecting a
solution that has been growing over the past 25 years and has, at points, evolved into different data
structures and architectures means that we also have to decide on one data structure and
architecture as we move forward. This is the only way that we can prepare the solution for increased
simplicity and faster innovation cycles.
Example: In the current ERP system, we have two general ledgers: the classical general ledger and
the new general ledger. The new general ledger was introduced mainly as a result of the need to
support multiple valuation methods. As progressed in SAP S/4HANA, we naturally had to decide on
one general ledger structure. We went with the structure of the new general ledger, which offers
much higher flexibility.
In most cases, SAP is pursuing the functional strategies that were already laid out in the existing
Business Suite world, where many innovations originate from (as in the example above).
Consequently, it is possible to prepare for the system conversion to SAP S/4HANA by already
adopting the future target capabilities in the classic SAP Business Suite.
That being said, SAP is taking on responsibility for managing the impact of these decisions.
Many of the changes are purely technical and will have no or only li ited i pa t o people s
work; therefore they will not trigger business change management. Such changes will be
mandatory when converting a system to SAP S/4HANA.
Other decisions are of a more strategic nature, determining which version of functional
suppo t ill e ol e i to the digital e a a d p o ide the apa ilities that toda s u stoppa le
business process innovation demands. When these strategic directions demand change
management through adoption, SAP will generally keep the traditional capabilities available
as compatibility scope, enabling a predominantly technical migration of these processes and
leaving the timing of change management as a customer decision. Change management may
therefore take place during the initial conversion or be postponed to a later point in time.
When compared to the number of SAP Business Suite products that appear in this list, the total list of
simplifications for SAP S/4HANA may appear rather long. However, SAP does not foresee that any
one customer system will be affected by all of them, because the simplifications cover all capabilities
of the system, including industry solutions. This list should be treated as a complete inventory that
needs to be mapped against a productive environment to determine the impact of converting.
Simplification List for SAP S/4HANA 1610
15
SAP expects that the same applies to custom code that our customers or partners have
implemented. 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 to identify custom
code in the context of these changes, thereby quantifying the effort involved in custom code
migration into a projectable quantity.
In addition, customers should be aware of the fact that only SAP S/4HANA packages (and no other
software) shall be deployed on an SAP S/4HANA installation. Details are provided in the Software Use
Rights document.
To enable our customers to better plan and estimate their path to SAP S/4HANA, we have created
the “i plifi atio List fo “AP “/ HANA . I this list e des i e i detail, o a fu tio al le el, hat
happens to individual transactions and solution capabilities in SAP S/4HANA. Compared to the SAP
Business Suite products, we have in some cases merged certain functionality with other elements or
reflected it within a new solution or architecture.
1.1 Purpose of the Document
The purpose of this document is to support customers in converting their system from SAP ERP 6.x
or SAP Simple Finance, to SAP S/4HANA.
Note: The Simplification List for SAP S/4HANA is edition/release dependent. In this collection we
focus on SAP S/4HANA 1610.
For future SAP S/4HANA releases, a new list will be made available.
1.2 General Topics for the Simplification List
For a typical ERP 6.x customer, moving to the SAP S/4HANA On-premise edition requires a database
migration to SAP HANA (if the customer is not yet running SAP HANA), followed by the installation of
the new simplified ode. Cha ges i adaptio o the usto e s side a e also e ui ed.
The most prominent example for which the customer needs to adapt to these SAP S/4HANA Onpremise edition 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, customers 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.
Custo e s e pe tatio elated to the o e to the SAP S/4HANA On-premise edition delivery is that
SAP informs and provides guidance about the required steps and tasks on this journey.
Based on the “i plificatio List for “AP “/4HANA , SAP will provide information about the SAP
S/4HANA On-Premise delivery related simplifications for each application/functional area. The
“i plifi atio List is a olle tio of i di idual “i plifi atio Ite s that fo us o hat eeds to e
Simplification List for SAP S/4HANA 1610
16
considered throughout an implementation or system conversion project from SAP ERP 6.X Customers
to SAP S/4HANA On-premise edition.
1.2.1 Simplification Item Information
Each Simplification Item will provide the following information:
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 areas that you should
already be familiar with from SAP Business Suite, with a short explanation about the technical
change.
Business Process-Related Information
Here you will find a description of what the Simplification Item means for the related business
processes.
Recommendations
The dedicated recommendations provide 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 may therefore differ depending on the
System Landscape that is actually in place.
1.2.2 Simplification Categories
The simplification items can be categorized based on their type of impact:
Re-architecting for SAP HANA in-memory platform
Used for functionality that is optimized to leverage the capabilities of the SAP HANA
database, for example the new data model.
Consolidation of existing functionalities
Functionality that is unified in the core and optimized according to the principle of one, but
from a business process and user perspective, the functionality basically remains the same.
No functional equivalent
Compared to the SAP Business Suite, there may be no functional equivalent available in the
SAP S/4HANA On-premise edition delivery, because SAP 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 SAP S/4HANA scope, or it is on the roadmap.
Simplification List for SAP S/4HANA 1610
17
1.2.3 Related Business Impact Note
With SAP S/4HANA 1610 the text of the single simplification items are maintained in separate SAP
Notes (so called Business Impact Notes). An XLS sheet with an overview of the Simplification Items
and their corresponding SAP Notes and application components can be found as attachment in SAP
Note 2313884.
1.3 System Conversion Sequence
SAP provides a process for the conversion to SAP S/4HANA. The following figure gives an overview of
the tools, the phases, and the activities involved in the process.
Recommendation: We recommend that you do the activities in the sequence shown in the figure
and explained in the sections below.
Figure 1: SAP S/4HANA System Conversion Sequence
For more details see SAP S/4HANA Conversion Guide 1610 within SAP Help:
http://help.sap.com/s4hana
1.3.1 Maintenance Planner
You have to use the Maintenance Planner to do the system conversion to SAP S/4HANA On-premise
edition. Based on the Maintenance Planner, which is recommended to run in an early phase of the
SAP S/4HANA System Conversion Project, the following items are checks if they are supported for the
conversion:
Any Add-Ons to your system1
Any active Business Functions in your system2
Industry Solutions3
If there is no valid conversion path for any of the items listed above (for example, an add-on is not
released for the conversion yet), the Maintenance Planner prevents the conversion. After the check,
the Maintenance Planner generates the download files (add-ons, packages, DBDs, and the stack
1
For a list of supported add-ons, see SAP Note 2214409
SAP Notes 2240359 for the Always-Off Business Functions and 2240360 for the Always-On Business Functions
3
See SAP Note 2214213 for supported industry solutions
2
Simplification List for SAP S/4HANA 1610
18
configuration file) and creates the stack configuration file (stack.xml), which is used by SUM to
convert to SAP S/4HANA On-premise edition.
1.3.2 Pre-Check Relevance
Pre-checks are shipped to customers that want to convert to SAP S/4HANA On-premise edition in the
form of SAP Notes. Customers can use these pre-checks to find out what mandatory steps they have
to carry out before converting to SAP S/4HANA. The results list the instances that need to be
addressed before attempting the conversion process.
1.3.3 Custom Code-Related Information
To support the customer in detecting custom code that needs to be adapted for the move to SAP
S/4HANA, SAP offered custom code analysis tools (as part of NW 7.50). The customer can verify if his
current custom code will be compliant with the SAP S/4HANA On-premise edition data structures
and scope. For more Info see details related to custom code within SAP Documentation: SAP Help
1.4 The Simplification List 1610 – this document
The Simplification List for SAP S/4HANA 1610 provides the information related to the Simplification
List Items which are applicable for customers doing a system conversion from SAP ERP 6.0 to SAP
S/4HANA 1610.
The Simplification List Items and corresponding Business Impact Notes
The text of the Simplification Items included in this Simplification List is generated based on
corresponding SAP Notes (they are called in the context of the Simplification List the Business Impact
Notes). Examples:
Simplification Item
Business Impact Note
Business Partner Approach
2265093
Material Number Field Length Extension
2267140
You can find the corresponding Business Impact Note in the Simplification List as XLS. The Business
Impact Note might contain additional information related to the Simplification Item. For example
references to other SAP Notes or additional How-To-Guides. For example there the Simplification
Item related to the Business Partner Approach contains a PDF describing the detailed Business
Partner Conversion Activities. Please be aware that we do not include these additional information in
the Simplification List document.
In this sense the Simplification List document is always a collection of the texts of the dedicated
Simplification Item which is stored as original in the corresponding Business Impact Notes. In case
you have questions or requests to improve the text related to a Simplification Item feel free to open
a support ticket based on the component of the Business Impact note.
The generation of the Simplification List document based on the business impact note does have an
influence to the format and the length of this document.
Simplification List for SAP S/4HANA 1610
19
New Simplification List Items with SAP S/4HANA 1610
With SAP S/4HANA 1610 the functional scope of SAP S/4HANA has been enhanced. For example
additional industries are supported (e.g. Oil and Retail are supported now) or the SAP Add-On SAP
Portfolio and Project Management 1.0 for SAP S/4HANA. Accordingly there are additional
Simplification Items listed in this document which go aside to this enhanced functional scope of SAP
S/4HANA. In the Simplification List as XLS the Simplification Items which are new with SAP S/4HANA
1610 are marked accordingly.
The Simplification List Items as XLS
Beside the Simplification List as PDF (this document) the Simplification List is available additionally in
XLS format as attachment of SAP Note 2313884. In this note you can find different XLS spreadsheets
for the different SAP S/4HANA releases. The Simplification List 1610 spreadsheet does contain the
following information:
Simplification Items which are new with SAP S/4HANA 1610
o
Items which are new and related to the industries Oil and Retail (supported with SAP
S/4HANA 1610)
o
Simplification Items related to SAP Add-On Portfolio and Project Management (PPM)
o
New Co e ite s i “AP “/ HANA (this includes items which changed their simplification
category – example: industry DIMP-Automotive – si plifi atio Lo g Mate ial Nu e
Simplification Items which are relevant for the upgrade from SAP S/4HANA On-Premise
edition 1511 to SAP S/4HANA 1610
Simplification List for SAP S/4HANA 1610
20
2
The Simplification List for SAP S/4HANA 1610
2.1
Simplification List - Per Application Area
2.1.1
2.1.1.1
Master Data
Business Partner Approach
2.1.1.1.1
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 1610. 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 1503 and 1605.
2.1.1.1.2
Business Process related information
Only SAP Business Suite customer with C/V integration in place can move to SAP S/4HANA, onpremise (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 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).
Transaction not available in
SAP S/4HANA on-premise
edition
2.1.1.1.3
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
Required and Recommended Action(s)
Before you begin the BP conversion from an SAP ERP system to an SAP S/4 HANA system, you have to
answer the questions
Simplification List for SAP S/4HANA 1610
21
Whether the Business Partner ID and Customer-ID /Vendor ID should be the same in the S/4
HANA System?
The keys for a smooth synchronization of the ERP customer/vendor into the S/4 system with the
business partner as the leading object are beside Business Partner Know-How also consistent
customer/vendor data and valid and consistent custom/vendor and Business Partner customizing
entries. For this reason, the customer/vendor data has to be cleaned up before it can be converted
into the S/4 Business Partner.
Prepare: Pre-Checks and clean-up customer/vendor data in the ERP System
Implement SAP S/4HANA Conversion Pre-Checks according to the SAP S/4HANA Conversion
guide chapter Pre-Checks.
Activate Business Function CA_BP_SOA.
In case that the Business Function CA_BP_SOA not yet in the system exist you have to create
a new Business Function in the customer namespace with the switches VENDOR_SFWS_SC1
and VENDOR_SFWS_SC2. The new customer specific Business Function must be of type
Enterprise Business Function (G) - see also Mandatory checks for customer, vendor and
contact.
Check CVI customizing and trigger necessary changes e.g. missing BP Role Category, Define
Number Assignments according to the S/4 Conversion guide chapter Introduce Business
Partner Approach (Customer Vendor Integration).
Check and maintain BP customizing e.g. missing tax types.
Check and clean-up customer/vendor data e.g. missing @-sign in the e-mail address.
Synchronization
Synchronization (Data load) is done via Synchronization Cockpit according to the S/4
Conversion guide Customer Vendor Integration.
In case of an error during the synchronization process due to data/customizing mismatch you
will find the errors in the monitor tab button Call PPO in Synchronization Cockpit.
Run Business Partner Pre-Check PRECHECK_UPGRADATION_REPORT to verify the results
according to the note 2211312.
Conversion Process
Conversion Process must be triggered according to the BP_Conversion Document.pdf
attached to the Business Impact Note.
Business Partner Post Processing
The customer/vendor transformation is bidirectional. You can both process customer/vendor
master records from business partner maintenance as well as populate data from
customer/vendor processing to the business partner. After the successful S/4 conversion
process you have to activate the post processing for direction Business Partner Customer
/Vendor according to the S/4 Conversion guide chapter Customer Vendor Integration.
Simplification List for SAP S/4HANA 1610
22
2.1.1.1.4 Related SAP Notes & Additional Information
Conversion Pre-Checks SAP Notes: 2211312, 2210486, 2216176
Other SAP Notes
SAP Note: 1623677, 954816
SAP Help
Refer to the attachments:
2.1.1.1.5
BP_Conversion Document.pdf: Description of business partner
conversion activities
01_TOP-Item_MD_Business-Partner-Approach_Version1.0.pdf:
Presentation on Business Partner Approach and Customer Vendor
Integration during Conversion
Industry Specific Actions
IS-OIL Specific Actions:
2.1.1.2
In S4HANA all the IS-OIL specific fields (including customer BDRP data fields) have been
adapted as per the new Framework of BP.
The IS-OIL Fields related to Vendor and Customer now have been moved to BP under the roles
FLCU01 (Customer), FLVN01 (Vendor).
Simplified Product Master Table
2.1.1.2.1
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).
2.1.1.2.2
Business Process related information
No influence on business processes expected
2.1.1.2.3
Required and Recommended Action(s)
None
2.1.1.2.4 Business Process related information
No influence on business processes expected
2.1.1.2.5
None
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
23
2.1.1.3
Material Number Field Length Extension
SAP S/4HANA can support a material number with 40 characters. The appropriate related SAP
development entities (domains, data elements, 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. 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.
Overview
With SAP S/4HANA, on-premise edition 1511, the maximum field length of the material number was
extended from 18 to 40 characters.
The material number field length extension was done with SAP S/4HANA and is available starting
with the SAP S/4HANA, on-p e ise editio
. Fo the fi st step i to “AP “/ HANA “AP “i ple
Finance, on-p e ise editio
the a i u field le gth is still
ha a te s lo g. Additio al
remark: SAP S/4HANA Finance 1605 based on Enhancement Package 8 is 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 behavior 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. E te di g su h ta get
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
Simplification List for SAP S/4HANA 1610
24
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 analyzed 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 a system
from SAP Business Suite to SAP S/4HANA, on-premise edition 1511 (or higher releases). 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 behavior 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. If you have activated the DIMP (Discrete Industries & Mill
Products) long material number or manufacturer parts number, changes of the content that is stored
on the database for the material number will be needed. For further information see the section
below and the references therein.
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 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
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 sequence
of fields in the transmitted data. Simply extending the material number field (or other extended
Simplification List for SAP S/4HANA 1610
25
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 remoteenabled 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,
adding a new field or extending the material number field was not necessary as these services usually
already allow material numbers with up to 60 characters in their interfaces. After an SAP Business
Suite System has been converted to SAP S/4HANA or a SAP S/4HANA system was newly installed,
the extended material number functionality will by default be switched off.
System Behavior 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.
o If the extended field is used as part of a communicated concatenated field, this
concatenated field is still sent in the original field in the old short format and is
interpreted in the inbound case in the old short format.
o 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.
o Communication partners can still rely on the old known behaviour of the interfaces.
o The long version of the extended field in the interfaces is filled and interpreted, too.
This means that the communication partners can already adapt their interfaces for
using the long field although only short material numbers are allowed.
For example, the 18 character material number is also communicated via the 40
character field. This is also true if the extended field is used as part of a
communicated concatenated field: the new extended field will contain and expect
the new long format.
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:
Simplification List for SAP S/4HANA 1610
26
Material numbers and other extended fields can be used with the full length (40 characters).
That means:
o It cannot longer be guaranteed that the old short fields can be filled or accepted: if
the material number or other extended fields are used with more than the original
length, the shorter version of an extended field cannot longer be filled in the
interface and is therefore left empty.
o This is also true for concatenated keys containing extended fields. If the value that is
part of the concatenate is longer than the original field length, the concatenate can
only be sent and evaluated in the new format.
o Before FPS2 the old short fields have not been filled or accepted when the extended
material number functionality is switched on. This has been changed with FPS2:
If the current value of the material number or the current value of another
extended field still fits into the old short field in the interface, the short
field is filled in outbound and accepted in inbound as well.
This is also true for concatenated values: if the old format can still be
used because the current value of the extended field contained in the
concatenate is short enough, the old format is still sent in outbound and
accepted in inbound in the old short field.
o 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. 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
Simplification List for SAP S/4HANA 1610
27
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). See SAP Note 1597790. Although the industry solution DIMP is part of
SAP S/4HANA, the already existing DIMP LAMA-functionality for a long material number (LAMA) will
not be part of SAP S/4HANA. In S/4HANA the material number is natively extended to 40 characters.
Special conversion steps are needed to migrate the existing DIMP LAMA solution to the new
S/4HANA extended material number. For further information on the conversion of the DIMP LAMAfunctionality and the DIMP Manufacturer Parts Number to S/4HANA please check notes 2270396 and
2270836.
ALE Change Pointers
ALE change pointer entries related to Master Data Distribution (see SAP Help: LINK) have to be
processed completely upfront to the move to SAP S/4HANA. Changes recorded before conversion
will no longer be available compatibly after conversion to SAP S/4HANA.
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: 2216958). For
the conversion of selection variants see SAP Note 1696821 for details.
Custom Code related information
See SAP Note: 2215424, 2215852
Restrictions
SAP S/4HANA restriction notes:
o SAP S/4HANA, on-premise edition 1511 restriction note (general): 2214213
o SAP S/4HANA 1610: 2333141
Collection of restriction related to MFLE: 2233100
o ALE generation for BAPIs: SAP Note 2232497
o Extended Material Number in Suite Integration: SAP Note 2232396
Simplification List for SAP S/4HANA 1610
28
o
o
o
o
o
2.1.1.4
Extended Material Number Display in Archived Data: SAP Note 2232391
Length of Customer and Supplier Material Number: SAP Note 2232366
Extended Material Number in LIS: SAP Note 2232362
Product Structure Browser: SAP Note 2229892
Characteristic Values in PLM: SAP Note 2229860
Simplification of copy/reference handling
During the preparation of the migration to an S/4 system, the preliminary checks return either an
error or a warning with the check ID SAP_APPL_LO_MD_MM_T130F_CHECK. The error message
indicates that the table T130F contains entries that are either not yet included in the table T130F_C
or that have differing contents. In an S/4 HANA system, the entries delivered by SAP can no longer be
adjusted customer-specifically, with the result that deviating settings are overwritten with the SAP
delivery settings during an upgrade. To prevent any customer-specific settings in T130F for the copy
control being replaced in the material master and the article master, an S/4 HANA system Release
101 or higher contains an additional Customizing table T130F_C, which allows alternative
maintenance of the copy control to the SAP delivery. The settings in T130F_C are then taken into
account during the maintenance of material master and article master data. Therefore, all entries
from the table T130F that are relevant for the copy control must be copied to the new table
T130F_C, and their field contents must be identical. If the pre-check issues a warning message, it may
be the case that the fields relevant for copying control from T130F have to be copied to the new
table T130F_C. However, it is only necessary to copy the entries if the S/4 HANA target release is
higher than or equal to 101. In this case, it is advisable to migrate the entries from T130F to the table
T130F_C to when the warning appears, as described in the "Solution" section. Otherwise the system
will later issue an error message during the migration phase when you execute the pre-check
because the system only then contains the information concerning the S/4 HANA target release to
which the data is migrated. To proceed further, you must then first carry out the data migration. If
the S/4 HANA target release is equal to 100, the system only issues a warning during the migration
phase because the new table does not exist in this release. In this case, proceed with the migration
process. If you use an SAP ERP for Retail system that requires at least the S/4 HANA target release
version 101, the system issues an error message at all times if the pre-check determines
inconsistencies. The data migration must be carried out in any case.
2.1.1.4.1
Description
In SAP S/4HANA, the table type of the table T130F has been changed so that the entries delivered by
SAP can no longer be changed in a customer system without a modification. It is simply possible to
create new, customer-specific entries in customer namespaces predefined especially for the purpose.
However, since some of the fields in T130F control the copy behavior during the creation of products,
and in Retail also when you change them, these settings should be retained during a migration. For
this purpose, the relevant fields of T130F must be copied beforehand to a new Customizing table
T130F_C so that these settings can continue to be defined customer-specifically.
Simplification List for SAP S/4HANA 1610
29
2.1.1.4.2
Required and recommended actions
Execute the migration pre-check.
Implement the report RMMT130F_CPY in your SAP ERP system with the aid of SAP Note
2323185. In addition, you must implement the new table T130F_C in your system based on
the correction instructions in SAP Note 2324325.
Execute the report with the standard settings. If entries are to be migrated, remove the
indicator for the test mode on the initial screen and execute the report again. Check the
messages output to establish whether the entries in all clients have been migrated
successfully.
2.1.1.4.1 Related SAP Notes
Migration pre-check
Migration report
2.1.1.5
SAP Note: 2206932
SAP Note: 2323185, 2324325
Foreign Trade fields in Material Master
2.1.1.5.1
Description
The Foreign Trade functionality as part of Sales & Distribution is not available within SAP S/4HANA,
on-premise edition 1511. 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
2.1.1.5.2 Related SAP Notes
General information about this Simplification
Item
2.1.1.6
SAP Note 2204534
MRP fields in Material Master
2.1.1.6.1
Description
The SAP S/4HANA simplification is done on the following tabs in transaction MM01/02/03.
Simplification List for SAP S/4HANA 1610
30
1. 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.
Fo
o e i fo
atio see si plifi atio ite
i P odu tio Pla
2.1.1.6.2 Related SAP Notes
General information about this Simplification
Item
2.1.1.7
i g “to age Lo atio M‘P .
SAP Note 2224371
Material Type SERV
2.1.1.7.1
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. As of SAP S/4HANA, onpremise edition 1511release changes are done as listed below:
1. Supported user departments:
o
o
o
o
Accounting
Purchasing
Basic Data
Sales
Simplification List for SAP S/4HANA 1610
31
2. The selected fields are hidden only from the material type "Service Materials", however, they
are supported for other material types.
2. 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)
Simplification List for SAP S/4HANA 1610
32
Accounting 2
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/10
As of S/4HANA 1605 CE and 1511 FPS2, additionally, the following fields are not supported for
Service Materials (SERV) type:
Basic data 1
X-plant matl status
Lab/Office
Prod. Hierarchy
Valid from
Packaging material data (entire section)
Sales General/Plant
Qual.f.FreeGoodsDis.
Purchasing
Qual.f.FreeGoodsDis.
Accounting 1
ML act indicator
Sales: sales org. 2
Product Hierarchy
2.1.1.7.2
Required and Recommended Action(s)
Configurations required for SERV that are part of SET:
Simplification List for SAP S/4HANA 1610
33
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
2.1.1.7.1 Related SAP Notes
General information about this Simplification
Item
2.1.1.8
SAP Note 2224251
Product Catalogue functionality for integration with Internet Application Components
2.1.1.8.1 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.
2.1.1.8.2 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 WCU1 Maintain customer
SAP S/4HANA
WCUM Maintain customer
WW10 IAC product catalogue
WW20 IAC Online Store
WW30 SD part for IAC MM-SD
2.1.1.8.3
None
Required and Recommended Action(s)
2.1.1.8.4 Related SAP Notes
Custom Code related information
2.1.1.9
SAP Note: 2226782
Product Catalogue
2.1.1.9.1 Description
Product Catalog functionality was used in the past as means of integration to web-channel solutions.
Simplification List for SAP S/4HANA 1610
34
Hybris is the strategic solution to support web-channel processes, with the respective backend
Integration. Thus, Product Catalog functionality is not the target architecture4.
2.1.1.9.2 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 1511.
Transaction not available in WPC1 Prepare product catalogue IDocs
SAP S/4HANA
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
2.1.1.9.3
None
Required and Recommended Action(s)
2.1.1.10 Object Identifier Type Code
2.1.1.10.1 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.1.1.10.2 Business Process related information
No influence on business processes expected.
2.1.1.10.3 Required and Recommended Action(s)
None
4
Functionality available in SAP S/4HANA 1610 delivery but not considered as future technology. Functional
equivalent is available.
Simplification List for SAP S/4HANA 1610
35
2.1.1.11 MDM 3.0 integration
2.1.1.11.1 Description
The MDM specific transaction codes for IDoc processing (inbound and extraction) are not available
within SAP S/4HANA 1511.
2.1.1.11.1 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 1529387 "Tables MDMFDBEVENT, MDMFDBID,
MDMFDBPR growing significantly"
Transaction not available in SAP S/4HANA
MDM_CLNT_EXTR "Local Extraction"
2.1.1.11.1 Required and Recommended Action(s)
None
2.1.1.11.1 Related SAP Notes
General SAP Note related to Simplification Item
SAP Note: 1529387
2.1.1.12 SRM Product Master
2.1.1.12.1 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 Error! Reference source not found..
Accordingly the SRM Product Master is not available in SAP S/4HANA 1511.
2.1.1.12.2 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
COM_PR_MDCHECK
COMC_MATERIALID_ALL
COMC_PR_ALTID
COMC_PR_ALTID_BSP
Simplification List for SAP S/4HANA 1610
36
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
2.1.1.12.3 Required and Recommended Action(s)
None
2.1.1.13 Logistics Batch Management
2.1.1.13.1 Description
The following transactions related to Logistics Batch Management are not available in SAP S/4HANA
1511: MSC1, MSC2, MSC3 and MSC4. The functional equivalent in SAP S/4HANA 1511 are the
following transactions:
Simplification List for SAP S/4HANA 1610
37
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 1511.
2.1.1.13.2 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
MSC1
MSC2
MSC3
MSC4
2.1.1.14 Classifications functionality of customer master
2.1.1.14.1 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 1511. The available Business Partner related transaction BP does currently not support the
functionality of classifications for customer master data in SAP S/4HANA 1511.
2.1.1.15 Business partner data exchange between SAP CRM and SAP S/4HANA
This Simplification Item is relevant for you if the following applies:
You are using an SAP ERP release and support package that is lower than the following
releases and support packages:
o SAP enhancement package 6 for SAP ERP 6.0
o SAP enhancement package 7 (SP11) for SAP ERP 6.0
o SAP enhancement package 8 (SP01) for SAP ERP 6.0
o You are using a live integration of SAP CRM and SAP ERP.
o You are planning to convert from SAP ERP to SAP S/4HANA, on-premise edition.
You are planning to activate the customer vendor integration (CVI) in SAP ERP and start a
mass synchronization based on the customer master or vendor master (Customizing activity
Synchronization of Mass Data) to generate business partners.
2.1.1.15.1 Description
In SAP S/4HANA, on-premise edition, the central business partner approach is mandatory. The
master data is processed using the SAP Business Partner in combination with an activated CVI, and
the customer or vendor master is updated automatically in the background. For more information,
Simplification List for SAP S/4HANA 1610
38
see the simplification item Business Partner Approach (SAP Note 2265093). If you have not worked
with the CVI beforehand, you need to activate it and generate business partners before converting
your system to SAP S/4HANA, on-premise edition. In addition, you have to make settings to set up
the business partner data exchange between SAP S/4HANA, on-premise edition and SAP CRM.
2.1.1.15.1 Business Process related information
There is no effect on business processes if the settings are performed as described in this
Simplification Item.
2.1.1.15.2 Required and Recommended Action(s)
Note that you must perform the pre-conversion actions described in this SAP Note before activating
the CVI and starting mass synchronization.
1. Required Actions in SAP ERP
A Business Add-In (BadI) implementation has been provided to ensure that the mass synchronization
does not generate new GUIDs instead of using the existing GUIDs from the CRM mapping tables. The
BAdI is contained in SAP Note 2283695. It is imperative that SAP Note 2283695 is implemented
before the Customer Vendor Integration (CVI) is activated and the mass synchronization of customer
master or customer vendor data for the generation of business partners is started. If you start the
synchronization before SAP Note 2283695 has been implemented, the mapping between business
partners that is used in an integration scenario with SAP CRM is irretrievably lost. A check report has
been provided to examine whether the BAdI implementation is available in your system. In addition,
a check report is available that identifies any existing inconsistencies (if you have been using an
active CVI already) or any inconsistencies that appear after mass synchronization. For more
information about the check reports, see SAP Note 2304337.
2. Required actions in SAP S/4HANA, on-premise edition
Settings for integration of SAP CRM with SAP S/4HANA, on premise-edition 1511 Feature Package
Stack 01. If you want to integrate your SAP CRM system with SAP S/4HANA, on premise-edition 1511
FPS 01, several limitations apply to the exchange of business partner data. For more information, see
SAP Note 2231667. Most of the limitations are resolved with SAP S/4HANA, on premise-edition 1511
FPS 02. In the integration scenario with SAP S/4HANA, on premise-edition 1511 FPS 01, you must
make the settings described in SAP Notes 1968132 and 2070408. Settings for integration of SAP CRM
with SAP S/4HANA, on premise-edition 1511 FPS 02, or a higher FPS. You need to adjust the settings
in transaction COM_BUPA_CALL_FU according to SAP Note 2283810.
Download Objects and Filters
(Note that the download objects named in the following paragraph are located in S/4HANA, onpremise edition, and the transactions are located in SAP CRM.). We recommend to use the download
objects BUPA_MAIN and BUPA_REL for initial loads and request. Due to the fact that in SAP
S/4HANA, on-premise solution, the SAP Business Partner is the main master data object for
processing customer and vendor master data, the download objects BUPA_MAIN and BUPA_REL now
Simplification List for SAP S/4HANA 1610
39
also support all general, customer-specific, and vendor-specific data. Download object
VENDOR_MAIN is not available. The download objects CUSTOMER_MAIN and CUSTOMER_REL
continue to be available for initial loads (transaction R3AS) and requests (transactions R3AR2 and
R3AR4). We recommend that you only use these download objects for specifying filters that are
specific to the customer master, like sales area details, account IDs, and partner functions. In
addition, filter conditions maintained in transaction R3AC1 for CUSTOMER_MAIN and
CUSTOMER_REL continue to be considered when downloading business partners and their related
customers from SAP S/4HANA, on-premise edition, to SAP CRM.
3. Miscellaneous required actions
See SAP Note 2286880 for handling error messages regarding SEPA and partner functions in SAP
CRM. No manual actions are required after implementing the SAP Note. If you have implemented the
user exits DE_BALE or DE_AALE in SAP ERP, see SAP Note 2289876. For further information about
business partner synchronization, see SAP Note 2265093.
2.1.1.15.3 Related SAP Notes
Pre-Check
SAP Note 2303003
2.1.1.16 External Interfacing BAPIs, IMG Nodes and BOR objects of SCM
SAP APO system is being migrated to SAP S/4HANA, on-premise edition. During this process, SAP APO
SWCs are added to S/4. As a result of this stack extension, few SAP APO business processes, IDOC,
BAPIs and IMG activities will not be available and be part of S/4 layer.
2.1.1.16.1 Description
Some IDOC Basic Types, IMG Customization Nodes and BOR (Business Object Repository) objects
are not available in SAP S/4HANA. These were available in standalone SAP APO systems before
migrating to SAP S/4 HANA
2.1.1.16.2 Business Process related information
Following IDOC Basic types, IMG Customization Entries and BOR objects are not available in SAP
S/4HANA.
PRDAPS_DELETELOCPRODUCTMULTI01 R3TR/
IDOC
MSCMB_BAPI_MD
PRDAPS_DELETELOCPRODUCTMULTI02 R3TR/
IDOC
MSCMB_BAPI_MD
PRDAPS_DELETEPRODUCTMULTIPLE01 R3TR/
IDOC
MSCMB_BAPI_MD
Simplification List for SAP S/4HANA 1610
IDOC basic type is for
deletion of one or more
location products.
IDOC basic type is for
deletion of one or more
location products.
IDOC basic type is for
deletion of one or more
products.
40
PRDAPS_DELETEPRODUCTMULTIPLE02 R3TR/
IDOC
ABC indicator
IMG
Activity
Rounding Profile
IMG
Activity
Maintain ATP group
IMG
Activity
Dangerous Goods Indicator Profile
IMG
Activity
MSCMB_BAPI_MD
Merchandise Distribution - Adjustment IMG
Profile
Activity
Specify Output Format of Product
Number
IMG
Activity
BUS10001
R3TR
SOBJ
BUS10015
Hierarchy
Product APS
Location Product
R3TR
SOBJ
MSCMB_BAPI_MD
MSCMB_BAPI_MD
Simplification List for SAP S/4HANA 1610
IDOC basic type is for
deletion of one or more
products.
IMG activity shall be
disabled from SCM;
however, this is now to
be used from ERP
customization.
IMG activity shall be
disabled from SCM,
however this is now to be
used from ERP
customization.
IMG activity shall be
disabled from SCM,
however this is now to be
used from ERP
customization.
IMG activity shall be
disabled from SCM,
however this is now to be
used from ERP
customization.
IMG activity shall be
disabled from ERP,
however this is now to be
used from SCM
customization.
IMG activity shall be
disabled from SCM,
however this is now to be
used from ERP
customization.
BOR Object shall be
deleted. SCM master
data fields are added to
ERP Product Master
(Material Master).
It is not possible to create
or maintain SCM master
data fields from SCM
transactions/ BORs/
BAPIs or APIs
BOR Object shall be
deleted. SCM master
data fields are added to
41
ERP Product Master
(Material Master).
BUS10017
BUS10011
Product Hierarchy
PartnerProductAPS
R3TR
SOBJ
R3TR
SOBJ
MSCMB_BAPI_MD
MSCMB_BAPI_MD
/SCMB/TG_BAPI_LOCPROD_UPD
LIMU
FUNC
/SCMB/PTRIG
/SCMB/TG_BAPI_LOCPROD_UPD2
LIMU
FUNC
/SCMB/PTRIG
/SCMB/TG_BAPI_PROD_UPD
LIMU
FUNC
/SCMB/PTRIG
/SCMB/TG_BAPI_PROD_UPD2
LIMU
FUNC
/SCMB/PTRIG
Simplification List for SAP S/4HANA 1610
It is not possible to create
or maintain SCM master
data fields from SCM
transactions/ BORs/
BAPIs or APIs
BOR Object shall be
deleted. SCM master
data fields are added to
ERP Product Master
(Material Master).
It is not possible to create
or maintain SCM master
data fields from SCM
transactions/ BORs/
BAPIs or APIs
BOR Object shall be
deleted. SCM master
data fields are added to
ERP Product Master
(Material Master).
It is not possible to create
or maintain SCM master
data fields from SCM
transactions/ BORs/
BAPIs or APIs
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
42
BAPI_PRTPRDSRVAPS_GETLIST2
LIMU
FUNC
BAPI_PRTPRDSRVAPS_SAVEMULTI2
LIMU
FUNC
BAPI_PRDSRVAPS_REMOVECLASSES
LIMU
FUNC
BAPI_PRDSRVAPS_GETCLASSES
LIMU
FUNC
BAPI_PRDSRVAPS_SETCLASSES
LIMU
FUNC
BAPI_PRDSRVAPS_REMOVEITEMS
LIMU
FUNC
BAPI_PRDSRVAPS_DELMULTI
LIMU
FUNC
BAPI_PRDSRVAPS_GETLIST
LIMU
FUNC
BAPI_PRDSRVAPS_REQUESTLIST
LIMU
FUNC
BAPI_PRDSRVAPS_REQUESTLIST2
LIMU
FUNC
BAPI_PRDSRVAPS_SAVEMULTI_30A
LIMU
FUNC
BAPI_PRDSRVAPS_SAVEMULTI2
LIMU
FUNC
MSCMB_BAPI_MD_PRT As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD_PRT As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to S/4 HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
Simplification List for SAP S/4HANA 1610
43
BAPI_LPHSRVAPS_GETDETAIL
LIMU
FUNC
BAPI_LPHSRVAPS_REMOVENODES
LIMU
FUNC
BAPI_LPHSRVAPS_REQUESTDETAIL
LIMU
FUNC
BAPI_LPHSRVAPS_SAVENODES
LIMU
FUNC
BAPI_PHSRVAPS_REMOVENODES
LIMU
FUNC
BAPI_PHSRVAPS_REQUESTDETAIL
LIMU
FUNC
BAPI_PHSRVAPS_SAVENODES
LIMU
FUNC
BAPI_PRTPRDSRVAPS_DELETEMULTI
LIMU
FUNC
BAPI_PHSRVAPS_GETDETAIL
LIMU
FUNC
BAPI_PHSRVAPSIF_RECEIVEDETAIL
LIMU
FUNC
BAPI_PRDSRVAPSIF_RECEIVELIST2
LIMU
FUNC
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD\_PRT As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
MSCMB_BAPI_MD
As a result of stack
extension of SAP-APO
“WC s to “/ HANA, FM
shall be blacklisted
Simplification List for SAP S/4HANA 1610
44
2.1.1.16.3 Required and Recommended Action(s)
Knowledge transfer to key and end users
2.1.1.17 HANA-based Analytics for Master Data Governance
2.1.1.17.1 Description
SAP HANA-based Analytics for Master Data Governance is not available within SAP S/4HANA, onpremise edition 1511.
2.1.1.17.2 Business Process related information
With this system conversion the content generation for SAP HANA-based Analytics for Master Data
Governance is no longer available.
2.1.1.17.3 Required and Recommended Action(s)
Please check if SAP HANA-based Analytics for Master Data Governance is in use.
2.1.1.17.4 How to Determine Relevancy
Check if content for SAP HANA-based Analytics for Master Data Governance has been generated.
This can be done via the following steps:
Use transaction SLG1 and check if log entries for MDG_ANA_HANA are existing.
Check if generated content is available on the HANA Database. This can be done for example
by looking for calculation view 'ChangeRequestHeader'.
2.1.1.18 Business Partner Time Dependency
2.1.1.18.1 Description
The time dependency functionality in Business Partner is not supported in the header level (BUT000).
Though the functionality is available through SPRO, SAP strongly recommends that the end user
should NOT maintain the header level data using Customizing. Customers who have activated time
dependency in the releases prior to 1610/11, refer to the section Required and Recommended
Action(s).
Simplification List for SAP S/4HANA 1610
45
2.1.1.18.2 Business Process Related Information
Switch-on and switch-off of the time dependency at BUT000 level will result in certain additional
activities. For instance, switching OFF the table BUT000_TD converts the time dependent entries to
time independent entries.
Once the BUT000_TD is ON, we can create time slice for central BP. The currently valid time slice will
be stored in BUT000 table and the past/future time slice will be stored in BUT000_TD table.
When BUT000_TD is switched OFF:
If the BP had split validities in BUT000 and BUT000_TD tables, you will not be able to open or
edit this BP.
The following error message appears:
Data set BUT
fo BP
XXX ai tai ed ti e-dependently, despite inactive Time
dep. essage appea s Hot Ne s Note
.
2.1.1.18.3 Required and Recommended Action(s)
For customers who have not enabled time dependency:
Do not enable the time dependency at the header level (BUT000) using SPRO.
For customers who have enabled time dependency in releases prior to 1610/11:
You need to deactivate time dependency. It is a one-time process.
1. Run the report Z_NTD_BUT000 attached with this Note. To run this:
1. Call up SE38.
2. Enter Z_NTD_BUT00 and choose Create.
3. Choose type as Executable Program.
4. Paste the code content from the attachment.
5. Save, activate, and then execute the report.
2. This Z report will delete all the BUT000_TD entries (past and future entries) and extend the
BUT000 entries (current entry) from 1.1.0001 to 31.12.9999 (which means loss of past/future
data).
3. Deactivate TD for BUT000 in V_TB056 view. Now you will not be able to maintain future/past
entries for central BP.
Notes:
The report Z_NTD_BUT000 has a test run mode and BP range as the selection parameter.
2.1.1.18.4 How to Determine Relevancy
This simplification item is relevant in case the time dependency is enabled in BUT000_TD.
Simplification List for SAP S/4HANA 1610
46
2.1.2
2.1.2.1
Sales & Distribution
Business Role Internal Sales Representative
Description
The Internal Sales Representative (ISR) business role was originally built to support sales
representatives who work in close coordination with customers, as well as 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 existed, accessible through either
the SAP Portal or by using the Business Client (as part of SAP NetWeaver). In SAP S/4HANA, the
Internal Sales Representative (ISR) business role is not available. This also includes the POWLs
(Personal Object Work Lists). Instead, a set of new FIORI roles, such as
SAP_BR_INTERNAL_SALES_REP, are offered as successors. As a first step, these 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, these roles will be further enhanced with custom-made apps based on FIORI. For more
information about this new concept, see SAP Note 2223838.
Business Process related information
Transaction not available in SAP
S/4HANA
VPW1
VPWL
Change View "Tasks"
Change View "Maintain Portal Targets"
Required and Recommended Action(s)
Adaption to the new FIORI role concept
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using the business role Internal Sales
Representative (ISR).
2.1.2.2
Webshops by Internet Sales or Web Channel Experience Management
Description
Web shops resp. e-commerce solutions based on SAP Internet Sales (component CRM-ISA), SAP ECommerce (component CRM-ISE), SAP Web Channel (component CRM-MD-PCT) or SAP Web Channel
Experience Management (component WEC) are not available in SAP S/4HANA. From a technical point
of view, these 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 the SAP
S/4HANA backend is provided by SAP hybris e-commerce in SAP S/4HANA 6.0.
Simplification List for SAP S/4HANA 1610
47
Business Process-Related Information
Customers that use web shops resp. e-commerce solutions based on the components mentioned
above and are planning to move to SAP S/4HANA shall use the SAP hybris e-commerce solution
instead (available with S/4HANA 6.0).
Transaction not available in SAP
S/4HANA
Transactions
ISA_CAT_REPLICATION
Replication of product
catalogues to TREX
ISA_CAT_REPL_DELETE ISA: Deletion of indices created
by product catalog replication
Also the following customizing t-code are not available:
S_EB5_05000537
S_EB5_05000608
S_EB5_05000609
S_EB5_05000612
S_EB5_05000660
S_EB5_05000669
S_EB5_05000670
S_EB5_05000679
S_EB5_05000680
S_EB5_05000691
S_EB5_05000692
S_EB5_05000762
S_EBJ_98000052
S_EBJ_98000078
S_EBS_44000154
S_EBS_44000345
S_EBS_44000346
S_EBS_44000415
S_EBS_44000421
S_EBS_44000427
S_EBS_44000505
S_EBS_44000536
Required and Recommended Action(s)
None
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using a web shop or an e-commerce
solution based on one of the components mentioned above.
Simplification List for SAP S/4HANA 1610
48
2.1.2.3
Commodity Management Sales
Description
Commodity Sales is switched off technically in SAP S/4HANA, on-premise edition 1511 and SAP
S/4HANA 1610. The main functional building blocks that have been deactivated are:
Commodity Management Integration in Sales E2E Process and Documents
Commodity Management Integration in Global Trade Management
Commodity Pricing / Commodity Pricing Engine (CPE) / Configurable Parameters & Formulas
(CPF)
Basis & Future Pricing
Differential / Final Invoicing & Billing
Commodity master data
Market data management for commodity prices and price curves
Day End / Month End Processing
Commodity Analytics (End of Day, 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 1511 or SAP S/4HANA
1610 is not possible.
The following Commodity Management Business Functions have been
deactivated in SAP S/4HANA, on-premise edition 1511 or SAP S/4HANA
1610:
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
LOG_SD_COMMODITY_05
Simplification List for SAP S/4HANA 1610
49
General information
2.1.2.4
COMMODITY_PROC_SALES_01
SAP Note: 2226096
Sales Activities
Description
Sales Support: Computer-Aided Selling (SD-CAS) - (see SAP Help LINK) is not available in SAP
S/4HANA, because it is not the target architecture. We recommended that you use SAP CRM onpremise (side-by-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
OV/8
OV/9
OV1Z
OV2Z
OV3Z
OV5Z
OV7Z
OV8Z
OV9Z
OVBR
OVBS
OVCB
OVCC
OVCD
OVCE
OVCF
OVCI
OVL5
SDCAS_MCQ
V+01
V+02
V+03
V+11
V+21
V+22
Test Data - Transfer Data - Cond.
Display Test Data
Define Product Allocation Procedure
Define Product Allocation Object
Determine Prod. Allocation Hierarchy
Maintain Consumption Periods
Create Characteristics for Rem.Alloc
Check Settings
Suitable Statistical Structures
Assignment to Item Category
Rule Table for Determining Dates
Structure of Reporting View
Assign View to User
Definition of Reporting View
Control Update of Perform.Measures
Control Reporting - Info Blocks
C SD Set Workflow Action box
Maintain Transit Time
Call MC/Q From Address Selection
Create Sales Call
Create Telephone Call
Create Sales Letter
Create Direct Mailing
Create Sales Prospect
Create Competitor
Simplification List for SAP S/4HANA 1610
50
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
VC010102
Only Follow-up Activities
VC010103
Do not Delete Mail. Camp.+Addresses
VC010104
Internet mailing
VC01N
Edit Sales Activity
VC01N_DRAG_KONTAKT Edit Sales Activity
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
Simplification List for SAP S/4HANA 1610
51
Required and Recommended Action(s)
If sales support functionality is requested, we recommend that customers start evaluating a side-byside CRM on-premise scenario, or that they use Cloud for Customer.
Related SAP Notes
Custom code-related information
2.1.2.5
SAP Note: 2214585
Billing Document Output Management
Output management for SAP S/4HANA includes cloud qualities such as extensibility enablement,
multi- tenancy enablement, and modification-free configuration. Therefore, the entire 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 combination
with message determination). Because output management for SAP S/4HANA only supports the
"pure" output channels, while the NAST-based output is also used for several kinds of postprocessing, output management for SAP S/4HANA cannot be used if one of the following NAST
transmission mediums is required:
8 Special function
9 Events (SAP Business Workflow)
A Distribution (ALE)
T Tasks (SAP Business Workflow)
In this case, please refer to the included correction instruction on how to switch back to NAST-based
output management for all billing documents.
Description
The new output management is used for newly created billing documents. Billing documents that are
migrated from legacy systems, and for which NAST-based output has been determined, can be
processed with this technology. If output management for SAP S/4HANA is used, the configuration
settings that are related to output management in Sales & Distribution in the area of billing /
customer invoicing need to be adapted. The following forms are delivered by SAP and can be
adapted:
-
SDBIL_CI_STANDARD_... used for standard customer invoices
SDBIL_CI_PROF_SRV_... used for professional service invoices
SDBIL_CM_STANDARD_... used for credit memos
SDBIL_IL_STANDARD_... used for invoice lists
Because the forms may differ from country to country, there is a separate form for each country. For
example, SDBIL_CI_STANDARD_DE is for Germany.
Simplification List for SAP S/4HANA 1610
52
For technical and implementation details, please refer to simplification Item Output Management
SAP Note 2228611
2.1.2.6
SD Rebate Processing replaced by Settlement Management
Description
In general, SD Rebate Processing is not available within SAP S/4HANA. The functional equivalent
of SD Rebate Processing in SAP S/4HANA 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 an 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. VB(D for the creation of rebate
agreements is not available anymore.
Transaction not available in SAP
S/4HANA
VBO1
VB(D
Create Rebate Agreement
Extend Rebate Agreements
Required and Recommended Action(s)
See the attached document for more detailed information.
How to Determine Relevancy
Use SE16 to check table KONA: If table KONA contains records with ABTYP = A then SD Rebate
Processing is used.
Related SAP Notes
Custom code-related information
2.1.2.7
SAP Note: 2226380
Miscellaneous minor functionalities in SD Area
Description
Simplification List for SAP S/4HANA 1610
53
In a lot of cases, SAP ERP contains several versions of the same or similar functionality, for example,
SAPGUI transactions or BAPI function modules. Older versions are marked as deprecated or obsolete,
but are still available for compatibility reasons. In SAP S/4HANA, only the most recent and most
comprehensive version is available for many of these objects. Deprecated versions have been
disabled. In the SD area, a couple of deprecated BAPI function modules and SAPGUI transactions
have been disabled. SAP Note 2228098 contains a list of objects not available in SAP S/4HANA and, if
available, the respective successor object.
Business Process-Related Information
No impact on business processes expected.
Required and Recommended Action(s)
None
How to Determine Relevancy
This Transition Worklist Item is relevant if the custom code check shows results that refer to note
2228098, or if the customer directly uses any of the transactions or programs listed in note 2228098
as deprecated objects.
2.1.2.8
SD Complaint Handling
Description
The industry-specific SD complaints handling in ERP is not available within SAP S/4HANA. 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 that have this business function active in SAP Business Suite
start system can convert to SAP S/4HANA. However, independently of the activation status of the
business function LOG_SD_EACOMPLAINTS, the corresponding functionality is not available in SAP
S/4HANA. Customers that do not have the business function LOG_SD_EACOMPLAINTS active in the
SAP Business Suite start release are not able to activate the business function after the conversion to
SAP S/4HANA. This business function is defined as obsolete in SAP S/4HANA.
Transaction not available in
SAP S/4HANA
WCMP_PROCESSING Complaints Processing
WCMP_MASS Mass Co plai ts P o essi g Custo e Nu e
WCMP_RESULT Results Display for Mass Complaints Processing
Simplification List for SAP S/4HANA 1610
54
Required and Recommended Action(s)
None
Related SAP Notes
Custom code-related information
2.1.2.9
SAP Note 2239184
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 1511 SP01. The FI-CA within SAP S/4HANA, however, can be used as
before. The system conversion to SAP S/4HANA will be blocked for customers that 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 SAP S/4HANA on premise edition 1511 SP01 have to use FI-CA within SAP S/4HANA.
Transaction not available in SAP S/4HANA
Customizing t-codes: S_EBJ_98000092
Required and Recommended Action(s)
Applies to cases in which a customer has used the integration between FI-CA and SD in a distributed
scenario in ERP. Either use the FI-CA within SAP S/4HANA instead or move to SAP S/4HANA on
premise edition 1511 SP02 or a higher release.
Related SAP Notes
Custom code-related information
SAP Note 2239189
2.1.2.10 SD Simplified Data Models
Description
The following data model simplifications have been implemented for the SD area:
Simplification List for SAP S/4HANA 1610
55
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:
o Data element VBTYP (Char1) has been replaced by data element VBTYPL (Char4);
o Field VBTYP_EXT (Char4) has been eliminated
Elimination of redundancies Document index tables VAKPA, VAPMA, VLKPA, VLPMA, VRKPA,
VRPMA
Elimination of redundancies
o Rebate index table VBOX: See simplification item "SD Rebate Processing replaced by
Settlement Management", SAP Note 2267377.
o LIS tables S066, S067: See simplification item "Credit Management", SAP Note
2270544.
Key benefits of the data model changes:
Reduced memory footprint (simplified document flow, elimination of index tables, fewer
aggregates)
Increased performance of HANA queries
Functional scope enhancement through extended field lengths
The changes are described in more detail in the guidelines attached to the related SAP Note
2198647.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
1. Adapt customer code according to the custom code check results, see SAP Note 2198647 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 in tables VBAK/VBAP, LIKP/LIPS, or VBRK, and these fields are
to be used in SAP 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
Simplification List for SAP S/4HANA 1610
56
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 system conversion?
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 SAP Note 2224436 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.
How to Determine Relevancy
This Transition Worklist Item is relevant if the custom code check shows results that refer to note
2198647.
Related SAP Notes
Conversion pre-checks
Custom code-related
information
SAP Note 2224436
Customer code has to be adapted according to the cookbooks in SAP
Note 2198647.
2.1.2.11 Enterprise Search in SD and LE
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 Enterprise Asset Management SAP EAM).
Business Process related information
With the new solution the following searches will not work:
SD
Search for Sales Documents, for example Sales Orders, Sales Quotations, Sales Group
Contracts and Sales Contracts
Search for Customer Billing Documents and Invoice Lists
LE related
Search for Inbound Deliveries, Outbound Deliveries and Return Deliveries
Simplification List for SAP S/4HANA 1610
57
Required and Recommended Action(s)
No changes expected in the business process.
2.1.2.12 Data Model Changes in SD Pricing
Description
Business documents within the SAP Business Suite, such as the sales order and the purchase
order, are used to store the pricing result in database table KONV. In SAP S/4HANA, table
KONV has been 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 code. The content of
KONV is transferred to PRCD_ELEMENTS when moving to SAP S/4HANA.
The following DDIC changes and interface changes have been made to the condition
technique:
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 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 was 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 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) has
been added to the batch input structures. If this field is filled or used
by external programs, 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
Simplification List for SAP S/4HANA 1610
58
VAKEY/VADAT are to be filled in addition to the still existing short
fields, the content of the long fields has priority.
Several data elements have been extended, especially the key field ZAEHK in table 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 1812828 (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
conversion process to SAP S/4HANA.
Data Element
Description
KOLNR, EVSNR, FSELNR
Number of access in access sequence
KOBED, KOFRM, KOFRA,
GRLNR, KOFRS
Pricing formula and requirement number
DZAEHK, DZAEHK_IND,
DZAEKO, BBP_ZAEHK
Condition counter in pricing result
GRLNR
Group condition routine
KALKS, KALVG
Customer and document classification for
pricing procedure determination
Former
Length
NUMC2
NUMC3
NUMC2
NUMC2
CHAR1
New
Length
NUMC3
NUMC7
NUMC3
NUMC7
CHAR2
In addition, the following elements in KONV have also been changed:
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
Level (in multi-level BOM
explosions)
Field is obsolete and will not be transferred to PRCD_ELEMENTS
WEGXX
Path (for multi-level BOM
explosions)
Field is obsolete and will not be transferred to PRCD_ELEMENTS
Business Process-Related Information
No impact on business processes is expected.
Required and Recommended Action(s)
Carefully follow the instructions in SAP Notes 2188695, 2189301, and 2220005.
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 SAP S/4HANA, you must
Simplification List for SAP S/4HANA 1610
59
ensure that the appended fields are also added to the new structure PRCS_ELEMENTS_DATA,
which is included in all necessary tables and structures, such as database tables
PRCD_ELEMENTS and PRCD_ELEM_DRAFT, for example.
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 structure PRCS_ELEMENTS_DATA?
o In the development system, you have to add the fields to PRCS_ELEMENTS_DATA
during phase ACT_UPG, when you are prompted for SPDD.
This is necessary to ensure that the automatic data migration transfers the field
content from KONV to PRCD_ELEMENTS during the upgrade-like conversion.
o In all other systems, you may use modification adjustment transports or customer
transport integration during the upgrade-like conversion for the appends to
structure PRCS_ELEMENTS_DATA.
The append fields must be contained in one of the custom transport requests from
the development system.
The conversion pre-check delivered via SAP Note 2188735 provides a check for such append
fields and issues a warning if these 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.
An overview over the pre-checks is provided in SAP Note. 2313318.
In the development system, you have to make all necessary adjustments in your code to deal
with the changed data model. See SAP Note 2220005 for more information. You need to do
this before going productive again.
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. After a
recommended test, this report is supposed to run on the productive data. However, note
that running the report is not mandatory before going productive again. Its execution can be
postponed to a later point in time.
Related SAP Notes
General information
Conversion pre-checks
Custom code-related
information
Carefully follow the instructions in SAP Notes 2188695, 2189301,
2313318, and 2220005
SAP Note: Pre-checks delivered with Note 2188735
SAP Note: 2220005
2.1.2.13 Foreign Trade
Description
Simplification List for SAP S/4HANA 1610
60
There are currently two software services for international trade transactions: Foreign Trade and SAP
Global Trade Services (GTS). Foreign Trade is part of the standard Sales and Distribution (SD) scope.
SAP GTS is an external service that can be installed on an additional instance. As of SAP S/4HANA, the
Foreign Trade functionality will be not available because SAP GTS is the successor for this business
requirement. For Intrastat, customers can leverage functions within SAP S/4HANA. For Legal Control
and Preference Management, you can use functions based on SAP GTS. SAP GTS can be natively
integrated with SAP S/4HANA. Letter of Credit is planned to be covered by Treasury and Risk
Management. For this plan, Treasury and Risk Management would be integrated with SAP S/4HANA
Sales for the processing of Letter of Credit. Additional functions for Import and Export Management
are available with SAP GTS.
Business Process-Related Information
The customer needs to check whether third-party foreign trade systems are in use for foreign trade
processes. Because of the replaced foreign trade functionality in SAP S/4HANA, it is possible that the
third-party foreign trade system will need to be adjusted by the respective third-party
solution/service provider. However, SAP GTS can be connected to SAP S/4HANA to run the respective
foreign trade processes.
Transaction not available in
SAP S/4HANA
VX99
EN99
VI09X
VI08X
VI80X
VI79X
VI77X
VI64X
VI14X
VI10X
VIIM
VIWE
VIEX
VE85
VE86
VE88
VE89
VE87
VEI3
OVE1
VXCZ
VXHU
VXPL
VXSK
FT/Customs: General overview
General Foreign Trade Processing
Change FT Data in Purchasing Doc.
Display FT data in purchasing doc.
Change FT Data in Goods Receipt
Display FT Data in Goods Receipt
Change FT Data in Outbound Delivery
Display FT Data in Outbound Delivery
Change FT Data in Billing Document
Display FT Data in Billing Document
FT: Op. Cockpit: Purchase order
FT: Op. Cockpit: Goods Receipt
FT: Journal Export Actual
Change Statistical Value – Import
Display Statistical Value – Import
Change Statistical Value – Export
Display Statistical Value – Export
Change Stat.Value – Subcontracting
Display Stat.Value – Subcontracting
Commodity Code / Import code no.
INTRASTAT: Form - Czech Republic
INTRASTAT: Form - Hungary
INTRASTAT: Form – Poland
INTRASTAT: Form – Slovakia
Simplification List for SAP S/4HANA 1610
61
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.
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
Simplification List for SAP S/4HANA 1610
62
VE15
VE21
VE22
VE23
VE18
VE25
VE19
VE20
VE27
VXJ1
VXJ2
VEIAI
VEIAE
VE81
VE73
VE74
VXA5
VXA7
ENSV
VX01N
VX02N
VX03N
VX22N
VX23N
VE31
VE30
VE29
VE82
VI83
VX07
VX09
VX08
VX16
VX17
VX10
VX05
VX06
VE56
VI84
VX14N
VX11N
Create disk - INTRA/EXTRA/KOBRA/VAR
VAR: Selection of bill. docs Switz.
Create VAR form for Switzerland
V.A.R.: File – Switzerland
SED data selection for USA exporter
SED: Selection: USA Carriers
Create SED form for USA
Create AERP file for USA
HMF: Selection – USA
MITI Declarations
Declaration of ImportBill.Docs Japan
INTRASTAT Archiving
EXTRASTAT Archiving
Check Report: General FT Data
Goods Catalog: Create Document
Goods Catalog: Create Diskette
Document. Payments: Print Monitoring
Documentary Payments: Simulation
Data Service
Create License
Change License
Display License
Change License Data
Display license data
Blocked SD Documents
Existing licenses
Assigned Documents for Each License
Check Report: Export Control Data
Check Customer Master/Legal Control
Simulation: License Check
Simulation: Embargo Check
Simulation: Boycott List Check
BAFA diskette: Selection
Create BAFA diskette
Countries of Destination for License
Customers for License
Export Control Classes for License
Check Export Control for Consistency
Doc.Payments: Check Customer Master
Maintain Financial Document
Create Financial Document
Simplification List for SAP S/4HANA 1610
63
VX12N
VX13N
VI73N
VI74N
VI78
VI54
VI55
VED1
OVE1
VPAR
VFAI
VFAE
FTUS
ENCO
ENGK
ENLO
ENPR
ENGR
ENSV
ENZD
VOIM
VOWE
VI09X
VI53X
VOLI
VOEX
VI77X
VI14X
VI85
VE81X
VE82X
VE83X
VI86
VI82X
VI83X
VI84X
Credit
VIE4
VE24X
VI24X
FTIM
FTGR
Change Financial Document
Display Financial Document
Foreign Trade: Maintain Long-Term Vendor Declaration
FT: Display Vendor Declaration
Foreign Trade: Countries
Customs Approval Numbers
Approval Number per Plant
Print Parameters for Export Documents
Commodity Code / Import Code Number
Archiving Preference Logs
Archiving – INTRASTAT
Archiving – EXTRASTAT
Foreign Trade: Maintain User Data
Printing / Communication
Legal Control
Documentary payments
Preference Processing
Periodic Declarations
Foreign Trade Data Maintenance
Customs Objects: Documentation/Info.
Check Import Purchase Order
Check Goods Receipt
Change Import Purchase Order
Change Goods Receipt
Check Export Delivery
Check Export Billing Document
Change Export Delivery
Change Export Billing Document
Check Report: Vendor Master
Check Report: General Foreign Trade Data
Check Report: Export Control Data
Check Report: Preference Data
Cross-plant Check of Foreign Trade Data
Foreign Trade: Customer Master Consistency – General
Foreign Trade: Customer Master Consistency – Control
Foreign Trade: Customer Master Consistency - Letter of
Periodic Declarations: Log of Incomplete Items
Foreign Trade: Information Commodity Code
Foreign Trade: Information Import Code Number
Journal: Purchase Orders
Journal: Goods Receipts
Simplification List for SAP S/4HANA 1610
64
FTIM
FTGR
FTEX
FTEX
VE30
VE29
VXA2
VXA1
VI74N
CAAT
VIUL
VIBA
VIBC
VIBB
VIB7
VIB9
VIB8
VIB4
VIB6
VIB5
VIB3
VEII
VEIE
VX00
LEAN
LEMA
VE67
LEER
VE55
VE54
VEB5
VEB6
VEPR
VE91
VE90
VE83
VE66
VE65
VE64
VE94
VEM4
Import Order Analysis
Import Gds Receipt Analysis
Export Bill. Documents Journal
Exp.bill.doc.analysis
Expiring Licenses
Sales Orders for a License
Financial Documents: List
Financial Documents: SD Documents
Display Vendor Declaration
Foreign Trade: Call up FT Atrium
Foreign Trade: Data Upload
Send IDoc Output-AES-Initial Procg
Send IDoc Output-AES-Error in Procg
Send IDoc Output-AES-Repeat Procg
Send IDoc Output - Initial Procg
Send IDoc Output - Error in Procg
Send IDoc Output - Repeat Procg
Print Transaction: Initial Procg
Print Transaction: Error in Procg
Print Transaction: Repeat Procg
Foreign Trade Output Status
SAPMSED8: Call IMPINV01
SAPMSED8: Call EXPINV02
Preference Handling
Request long-term VendDecl. (vendor)
Dun long-term vendor decl. (vendor)
Aggregate Vendor Declarations
Create long-term VenDecl. (customer)
Preference Determination: Individual
Preference Determination: Collective
Calculate Assemblies Individually
Calculate Assemblies Collectively
Customs log
Display Preference Values
Change preference values
Check Report: Preference Data
Preference Procedure
Preference Reg./Percentage Rates
Commodity Code/Customs Areas
Load Commodity Code for EU Countries
Merge: EU - Commodity Code
Simplification List for SAP S/4HANA 1610
65
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 foreign trade processes that are currently in use.
Related SAP Notes
Conversion pre-checks
Custom code-related information
SAP Note: 2205202
SAP Note: 2223144
2.1.2.14 Credit Management
Description
Credit Management (FI-AR-CR) is not available as part of SAP S/4HANA. The functional equivalent in
SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR).
Simplification List for SAP S/4HANA 1610
66
Business Process-Related Information
You need to migrate FI-AR-CR to FIN-FSCM-CR. This migration comprises several elements:
Configuration data
Master data
Credit exposure data
Credit decision data
The migration from one-system landscapes is supported by tools that SAP provides.
Influence on Business Processes
There will be no change to your business processes because of the migration. However, some
transactions become obsolete and are replaced by new transactions. Here are some examples for
such cases:
Examples for replaced
For the maintenance of the credit account master data, transaction
transactions in SAP S/4HANA FD32 is replaced by transaction UKM_BP.
For releasing credit-blocked sales orders, transaction VKM1 is
replaced by transaction UKM_MY_DCDS. To use transaction
UKM_MY_DCDS, the credit specialist might need additional
authorizations. As a workaround, the transactions VKM1 and VKM4
are still available.
Transactions not available in F.28 - Customers: Reset Credit Limit
SAP S/4HANA
F.31 - Credit Management - Overview
F.32 - Credit Management - Missing Data
F.33 - Credit Management - Brief Overview
F.34 - Credit Management - Mass Change
FCV1 - Create A/R Summary
FCV2 - Delete A/R Summary
FCV3 - Early Warning List
FD24 - Credit Limit Changes
FD32 - Change Customer Credit Management (but FD33 still
available for Migration checks)
FDK43 - Credit Management - Master Data List
S_ALR_87012215 - Display Changes to Credit Management
S_ALR_87012218 - Credit Master Sheet
VKM2 - Released SD Documents
VKM3 - Sales Documents
VKM5 - Deliveries
Reports not available in SAP
S/4HANA
RFARI020 - FI-ARI: Extract from credit master data
RFARI030 - FI-ARI: Import credit master data
Simplification List for SAP S/4HANA 1610
67
RFDFILZE - Credit Management: Branch/Head Office Reconciliation
Program
RFDKLI*NACC Reports
RFDKLxx Reports
The following settings in Customizing are affected by the migration:
All IMG activities for SAP Credit Management are listed in Customizing under the following
path: Financial Supply Chain Management > Credit Management.
The credit limit check for sales document types can only be specified as type D in SAP Credit
Management or can be left empty (no credit limit check). The credit limit check types A, B,
and C are no longer available.
The credit check when changing critical fields has been removed from the SD side.
The payment guarantee-related Letter of Credit has been removed from the SD side.
A credit check on the basis of the maximum document value is not supported in SAP
S/4HANA 1511 SP00 and SP01.
It is supported as of SAP S/4HANA 1511 FPS2.
Required and Recommended Action(s)
1. Prerequisites for the migration to SAP Credit Management:
You have completed all documents related to payment guarantee Letter of Credit.
You have completed the migration for Accounting.
If you are running on your own code, you have eliminated the usage of SAP objects in your
own code. For details on how to adapt user-defined customer code that relies on the
changed objects, see the following SAP Notes:
o 2227014 (Financials)
o 2227014 (SD)
2. Perform the recommended actions in the Task List PDF attached to this Note (only available in
English). This list is only valid for the conversion of one-system landscapes.
Related SAP Notes
Custom code-related information (SD)
Custom code-related information (Financials)
SAP Note: 2217124
SAP Note: 2227014
2.1.2.15 ERP SD Revenue Recognition
Description
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 outlined in IFRS15 and adapted by
Simplification List for SAP S/4HANA 1610
68
local GAAPs. The migration to the new solution is required to comply with IFRS15, even if no upgrade
to SAP S/4HANA is performed.
Business Process-Related Information
Sales and Distribution (SD) Revenue Recognition is not available in SAP S/4HANA. None of the SD
Revenue Recognition functionality will work in SAP 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
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"
Required and Recommended Action(s)
Prior to the Conversion to SAP 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
and for which you expect follow-on activities like increase quantity, create credit memo or
cancel invoice
Please note that release 1.1 of SAP Revenue Accounting and Reporting does not include the full
functional capabilities of SD Revenue Recognition. Examples of unavailable functionalities in SAP
S/4HANA include:
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 whether a migration to SAP Revenue
Accounting and Reporting is possible for your business before you decide to convert to SAP
S/4HANA.
Simplification List for SAP S/4HANA 1610
69
You can find more details about the migration to SAP Revenue Accounting and Reporting can in the
migration chapter of the online help (RevAcc Help) and in the administrator guide for the product
SAP SD Integration with SAP Revenue Accounting and Reporting: Admin Guide Integration SD
Related SAP Notes
Conversion pre-checks
Custom code-related information
SAP Note: 2227824
SAP Note: 2225170
2.1.2.16 Optimization of SD Rebate Processing for TPM Customers
Description
Customers who will integrate their existing CRM TPM scenario with SAP S/4HANA need 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 these customers, the existing SD Rebate functionality has been optimized with regard to the
database footprint. For this purpose, from a technical viewpoint, the rebate index table VBOX is not
available.
Business Process-Related information
Please note that TPM customers are also unable to neither create new rebate agreements in SAP
S/4HANA nor 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
S/4HANA
VBO1
VB(D
Create Rebate Agreement
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.
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using Trade Promotion Management in his
CRM system which is connected with the ERP system.
Related SAP Notes
Custom code-related information
SAP Note: 2200691
Simplification List for SAP S/4HANA 1610
70
2.1.2.17 Simplification in SD Analytics
Description
Simplification in SD Analytics follows the overall analytics strategy in SAP S/4HANA (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 (also known as ABAP-managed Core
Data Services (CDS)), which sit 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 Represent the Core Entities in SD
The SD-specific business objects Sales Order, Customer Invoice, Outbound Delivery, and many others
on top of database tables VBAK, LIKP, and VBRK are represented by CDS views that encompass access
of the analytics CDS queries to the database in a uniform manner. This is achieved by offering
semantic field names and associations to connected business objects, such as Customer, Material,
and so on.
All analytics content will be built on top of these core entities.
Incoming Sales Orders and Sales Volume Based on CDS Views
The initially delivered analytics content consists of two CDS queries: Incoming Sales Orders and Sales
Volume. These two exemplify the capability of SAP S/4HANA to report directly on the database,
without any prebuilt aggregates, but 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 SAP S/4HANA's 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[1]
Customers are allowed to extract data from SAP S/4HANA to their own BW-Hub and to make
extended use of the LIS/SIS[2] tool, as long as the CDS-based approach in SD is not yet available in a
comparable standard.
Business Process-Related Information
No impact on business processes is expected.
Transaction not available in SAP
S/4HANA
VA06 Sales Order Monitor
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
71
None
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using LIS/SIS or if the customer is
extracting data from SAP S/4HANA to their own BW-Hub.
Related SAP Notes
Custom code-related information
SAP Note: 2227750
[1] Functionality available in the SAP S/4HANA delivery, but not considered as future technology.
Functional equivalent is available.
[2] Note: If you use a material number longer than 18 characters - see restriction note Extended
Material Number in LIS: SAP Note 2232362.
2.1.2.18 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
that are planning to move to SAP S/4HANA need to remodel their business processes accordingly.
Transaction not available in SAP
S/4HANA
VACB
Advanced Order Processing and Billing
Customizing t-codes:
/CBAD/98000075
/CBAD/98000076
/CBAD/98000077
/CBAD/98000078
/CBAD/98000079
/CBAD/98000080
/CBAD/98000081
/CBAD/98000082
/CBAD/98000083
/CBAD/98000084
/CBAD/98000085
Simplification List for SAP S/4HANA 1610
72
/CBAD/98000086
Related SAP Notes
Custom code-related information
SAP Note: 2223800
2.1.2.19 Operational Data Provisioning
Description
Operational Data Provisioning in SD (see SAP Help: Link) is not available in SAP S/4HANA.
Simplification in SD Analytics follows the overall analytics strategy in SAP S/4HANA (see Simplification
Item SD Analytics): The SAP S/4HANA Analytics approach is based on ODATA and Open CDS (also
known as ABAP-managed Core Data Services (CDS)), which sit directly on top of the original
database. Corresponding analytics content will be provided in 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 database tables VBAK, LIKP, and VBRK are represented by CDS views that encompass access
of the analytics CDS queries to the database in an uniform manner by offering semantic field names
and associations to connected business objects as Customer, Material, and so on.
All analytics content will be built on top of these core entities.
Business Process-Related Information
No impact on business processes is 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.
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer has used Operational Data Provisioning in
SD.
Related SAP Notes
Simplification List for SAP S/4HANA 1610
73
Custom code-related information
2.1.3
SAP Note: 2228056
Customer Service
2.1.3.1
Customer Interaction Center (CIC)
2.1.3.1.1
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.
2.1.3.1.2
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
2.1.3.1.3
CIC0
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.
2.1.3.1.4 Related SAP Notes
Custom Code related information
2.1.3.2
See SAP Note 2229726
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. No
functional equivalent is available.
Business Process related information
Business Processes using this solution will no longer work. An alternative solution has to be
developed in a customer project.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
74
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.
How to Determine Relevancy
The iView was meant to be used to provide pharmaceutical sales reps with the ability to review their
stock of drug samples (van stock). It provides a view into the standard ERP inventory.
This note is relevant for customers using the SAP Portal and have configured this iView.
Related SAP Notes
Custom Code related information
2.1.4
2.1.4.1
As this is an iView, customers were not able to
develop custom code
Procurement
MM-PUR WebDynpro Applications
Description
WebDynpro Applications of SAP ERP Materials Management (MM) are not available with SAP
S/4HANA, on-premise 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 1511. 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
MMPUR_CPPR_MAIN_APPL
MMPUR_SPPR_MAIN_APPL
MMPUR_ACCOUNT_ASSIGN_CO
MP
MMPUR_ADDRESS_COMP
MMPUR_BWLAUNCHER_APP
MMPUR_CFOLDERS_EP_EVENT
MMPUR_CFOLDERS_URL_APP
MMPUR_DISPLSCHEDLINE_APP
SAP S/4HANA Replacement
SAP GUI report
Collective Processing of Purchase
BBP_EXTREQ_TRANSFER, Fiori
Requisition
Application
SAP GUI transaction ME51N, Fiori
Purchase Requisition Processing
Application
Account assignments
Display Address
BW Starter
Smart Business? BW Integration?
Document Storage
Document Storage
Display of Delivery Schedule Lines
for Item
Simplification List for SAP S/4HANA 1610
75
MMPUR_DOCTRK_APP
MMPUR_DOC_TRACE
MMPUR_FINDSUPPLIER_COMP
MMPUR_FORECAST_APP
MMPUR_MAVERICK_APP
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
Document Tracing
Graphical document tracing
Find Supplier
Expected Contract Release Orders Smart Business?
Maverick Buying Analysis
Smart Business?
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
2.1.4.2
SAP Note: 2228261
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 4.70. 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.
Business Process related information
No influence on business processes expected
Transaction not available in SAP
S/4HANA on-premise edition 1511
ME21
ME22
ME23
ME24
ME25
ME26
ME27
ME28
ME51
Simplification List for SAP S/4HANA 1610
76
ME52
ME53
ME54
ME59
MR01
MR1M
BAPIs not available SAP S/4HANA on- BAPI_PO_CREATE
premise edition 1511
BAPI_REQUISITION_CREATE
BAPI_PO_GETDETAIL
Required and Recommended Action(s)
See SAP notes:
1803189: FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc.
144081: Replacing MR01 / Functions of MR1M (Release 4.6)
Related SAP Notes
Custom Code related
information
SAP Notes:
2.1.4.3
1803189: FAQ: End of Support of ME21, ME51, and
BAPI_PO_CREATE etc.
144081: 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
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)
Simplification List for SAP S/4HANA 1610
77
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
2.1.4.4
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 If customers have enhanced interfaces for point-to-point supplier
information
distribution from SAP SLC to SAP ERP using the SLC integration component in
SAP ERP, communication with MDG-S must be enhanced accordingly.
2.1.4.5
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. With the new concept, the behavior of the system is more comprehensive. The new concept
introduces a header authorization object that enables the system to perform the following
authorization checks:
Simplification List for SAP S/4HANA 1610
78
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.
2.1.4.6
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 onpremise 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 1511. 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.
Transaction not available in
SAP S/4HANA
See Transaction Code List in Sales & Distribution Foreign Trade
Simplification Item.
Simplification List for SAP S/4HANA 1610
79
Required and Recommended Action(s)
Analysis of all currently used foreign trade processes.
Related SAP Notes
Custom Code related information
2.1.4.7
SAP Note: 2223144
Commodity Management Procurement
Description
Commodity Procurement is switched off technically in SAP S/4HANA, on-premise edition 1511 and
SAP S/4HANA 1610. The deactivated main functional building blocks are:
Commodity Management Integration in Procurement E2E Process and Documents
Commodity Management Integration in Global Trade Management
Commodity Pricing / Commodity Pricing Engine (CPE) / Configurable Parameters & Formulas
(CPF)
Basis & Future Pricing
Differential / Final Invoicing & Billing
Commodity master data
Market data management for commodity prices and price curves
Day End / Month End Processing
Commodity Analytics (End of Day, 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 or SAP
S/4HANA 1610 is not possible.
Simplification List for SAP S/4HANA 1610
80
The following Commodity Management Business Functions have been
deactivated in SAP S/4HANA, on-premise edition 1511 and SAP S/4HANA
1610:
Business Functions: Commodity Procurement
General Information
2.1.4.8
LOG_CPE_SD_MM
LOG_CPE_FA_FE
LOG_MM_COMMODITY
LOG_MM_COMMODITY_02
LOG_MM_COMMODITY_03
LOG_MM_COMMODITY_04
LOG_MM_COMMODITY_05
COMMODITY_PROC_SALES_01
SAP Note: 2226096
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.
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 519685 (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
Simplification List for SAP S/4HANA 1610
81
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 1511 -> 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
01
02
10
11
20
30
31
32
35
40
50
55
60
Description
Report for rebuilding S111 and WIND entries
Purchase Order
RMEBEIN3
Scheduling Agreement
RMEBEIN3
Sales Price Calculation
RWVKP012
Sales Price Calculation Index RWVKP012
Customer billing document RMEBEIL3
Vendor billing document
RMEBEIL3
Expense document
RMEBEIL3
Vendor settlement document RMEBEIV3
Remuneration list
RMEBEIL3
Vendor settlement request RMEBEIZ3
Assortment List
RMEBEIN3
POS-Outbound
RMEBEIN3
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
Simplification List for SAP S/4HANA 1610
82
Conversion Pre-Checks
2.1.4.9
SAP Notes: 2192984, 2215169
RFQ Simplified Transaction
The previous concept was based on Request for Quote with a mandatory Supplier Field. In addition it
was only possible to enter one Supplier Quote per Request for Quote. This does not fit to different
Sourcing Integration Scenarios (Example Ariba Sourcing, Ariba Spot Quote. With the new concept,
the behaviour of the system allows to send RFQ via Fiori App to external sourcing platforms without
a Supplier included and to receive from them multiple Supplier Quotes. Following IDOCS and
Transactions related to Request for Quote are not considered as the target architecture
(Functionality available in current SAP S/4HANA delivery but not considered as future technology.
Functional equivalent is not available).
It is planned to replace them with cXML messages:
REQOTE (Basic Idoc type = ORDERS05) is the IDOC for RFQ
QUOTES (Basic Idoc type = ORDERS05) is the Idoc for Quote
The following transactions are not strategic anymore and it is planned to replace them
with corresponding Fiori Apps:
ME41
ME42
ME43
ME44
ME45
ME47
ME48
ME49
ME4B
ME4C
ME4L
ME4M
ME4N
ME4S
Create
Change
Display
Maintain Supplement
Release
Maintain
Display
Price Comparison List
RFQs by Requirement Tracking Number
RFQs by Material Group
RFQs by Vendor
RFQs by Material
RFQs by RFQ Number
RFQs per Collective Number
Create Request For Quotation
Change Request For Quotation
Display Request For Quotation
Maintain RFQ Supplement
Release RFQ
Create Quotation
Display Quotation
Price Comparison List
RFQs by Requirement Tracking Number
RFQs by Material Group
RFQs by Supplier
RFQs by Material
RFQs by RFQ Number
RFQs by Collective Number
Business Process related information
Before using the new Fiori App you need to close your open RFQ created with the old transactions.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
83
You must edit the user roles. As soon as the new Fiori Apps will be available also the standard roles
delivered with SAP S/4HANA contain this new authorization object.
2.1.4.10 Co-Deployment of SAP SRM
Description
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. The functional scope is described in the content of
the feature scope description of SAP S/4HANA.
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 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.
2.1.4.11 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
Simplification List for SAP S/4HANA 1610
84
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 2186288
Description 2187627
2.1.4.12 Vendor evaluation based on LIS
Description
The current vendor evaluation based on Logistics Information System (Note: If you use a material
number longer than 18 characters - see restriction note Extended Material Number in LIS: SAP Note
2232362.) is still available with SAP S/4HANA, on-premise edition 1511, but is not considered the
target architecture (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is available.). 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 1511. 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: 2228247
Simplification List for SAP S/4HANA 1610
85
2.1.4.13 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. Furthermore, if recompilation of the business volume data in SAP S/4HANA, onpremise edition 1511 is required, the index table S111 has to be rebuilt as described in SAP Note
73214 (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 73214
Related SAP Notes
Conversion Pre-Checks
Related SAP Notes
SAP Notes: 2194923, 2215220
SAP Note: 73214
2.1.4.14 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
Simplification List for SAP S/4HANA 1610
86
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
/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.
2.1.4.15 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 1511.
Transaction not available in SAP
S/4HANA on-premise edition 1511
MEW0
MEW1
MEW2
MEW3
MEW5
Procurement Transaction
Create Requirement Request
Status Display: Requirement Requests
Collective Release of Purchase Reqs.
Collective Release of Purchase Order
Simplification List for SAP S/4HANA 1610
87
MEW6 Assign Purchase Orders WEB
MEWP Web based PO
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2228250
2.1.4.16 MDM Catalog
Description
The SAP SRM MDM catalog is no more available in S/4HANA. He is replaced by the catalog search
function as part of S/4HANA Self Service Procurement. In the first release of SAP S/4HANA, onpremise 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.
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 (http://scn.sap.com/docs/DOC-35441).
Catalog content will be managed as part of S/4HANA Self Service Procurement.
Required and Recommended Action(s)
None
2.1.4.17 Pricing Data Model Simplification
Description
See the information provided in the Sales & Distribution area in simplification item Data Model
Changes in SD Pricing. On a basic level, this information is also relevant for the pricing in
procurement.
Business Process-Related information
See simplification item Data Model Changes in SD Pricing.
Simplification List for SAP S/4HANA 1610
88
Required and Recommended Action(s)
See simplification item Data Model Changes in SD Pricing.
Related SAP Notes
General information
Conversion pre-checks
Custom code-related
information
Carefully follow the instructions in SAP Notes 2188695, 2189301,
and 2220005.
SAP Note: Pre-checks delivered with Note 2188735.
SAP Note: 2220005
2.1.4.18 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). Nevertheless Output management based on NAST is still 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 the new and with NAST
technology. The user can decide whether he wants to use for all new purchase orders the new
output management or NAST. 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, EMAIL, 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 e-mail or XML.
Simplification List for SAP S/4HANA 1610
89
2.1.5
Logistics – AB
2.1.5.1
Agency Business
2.1.5.1.1
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
2.1.5.1.2
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 1511. Details about the system configuration kind be found in the note: 2197892 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: 2197898
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 2204135).
Obsolete
Report
RWLF1001
Obsolete Report Title
RWLF1002
RWLF1003
RWLF1004
Obsolete
Tcode
WLFB
Successor Report
Successor Report Title
Successor Tcode
RWLF1051
WLI2
Billing documents (with item
data)
WLFC
RWLF1051
Settlement Document Lists
(Header
Information)
Settlement Document Lists
(With Item
Data)
WLFD
RWLF1051
WLFE
RWLF1051
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
Billing docs (header
data)
Simplification List for SAP S/4HANA 1610
WLI2
WLI2
WLI2
90
RWLF1005
Settlement Requests
(Header
Information)
WLFG
RWLF1051
List Output Settlement
Management Documents
WLI2
RWLF1006
Settlement Requests (With
Item
Data)
Settlement Request Lists
(Header
Data)
Settlement Request List
(Item
Data)
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)
WLFH
RWLF1051
WLI2
WLFO
RWLF1051
WLFP
RWLF1051
WLFQ
RWLF1051
WLFR
RWLF1051
WLRA
RWLF_SETTLEME
NT_LIST_RL
WLRB
RWLF_SETTLEME
NT_LIST_RL
WBLRB
RWLF_SETTLEME
NT_LIST_RL
S_AL0_9
6000193
RWLF1051
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
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
Customer Settlement (With
Item
Data)
Expenses Settlement
(Header
Information)
S_AL0_9
6000194
RWLF1051
WLI2
S_AL0_9
6000195
RWLF1051
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
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
S_AL0_9
6000196
RWLF1051
WLI2
S_AL0_9
6000198
RWLF_SETTLEME
NT_LIST_RL
S_AL0_9
6000334
RWLF_SETTLEME
NT_LIST_RL
WLI1
RWLF1051
RWLF1052
List Output List
Documents
WLI3
RWLF1051
RWLF1CHD
Display Change Document
for Settlement Management
Documents
Conditions for Settlement
Requests
(Vendor)
Conditions for Settlement
Request
Lists
List Output Settlement
Management
Documents
Worklist based Creation of
Settlement Document List
(Dialog)
Worklist based Creation of
Settlement Document List
(Dialog)
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
Display Change
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
WLI2
RWLF1007
RWLF1008
RWLF1009
RWLF1010
RWLF1011
RWLF1012
RWLF1013
RWLF1014
RWLF1015
RWLF1016
RWLF1017
RWLF1018
RWLF1019
RWLF1050
RWLF1KO1
RWLF1KO2
RWLF_CHANGE_D
OCUMENTS
RWLF1051
RWLF1051
Simplification List for SAP S/4HANA 1610
WLI2
WLI2
WLI2
WLI2
WLFSLRL
WLFSLRL
WLFSLRL
WLI2
WLI2
WLFSLRL
WLFSLRL
WLI2
WLI2
WLF_CHANGE_DO
CUMENTS
WLI2
91
RWLF1KO3
RWLF1KO4
RWLF1KO5
RWLF2001
RWLF2002
RWLF2003
RWLF2004
RWLF2005
RWLF2006
RWLF2007
RWLF2008
RWLF2009
RWLF2010
RWLF2011
RWLF2012
RWLF2013
RWLF2014
RWLF2016
RWLF2018
RWLF2019
RWLF2020
Conditions for Settlement
Document
Lists
Conditions for Settlement
Requests
(Customer)
Conditions for Customer
Settlement List
Documents
Mass Release of Settlement
Documents to
Accounting
Mass Cancellation of
Settlement
Requests
Mass Cancellation of Billing
Documents
RWLF1051
RWLF1051
RWLF1051
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
Mass Release of Settlement
Management
Documents
Mass Cancellation of Settlement
Management
Documents
Mass Cancellation of Settlement
Management
Documents
Mass Release of Settlement
Management
Documents
Mass Release of Settlement
Management
Documents
Create Settlement Document
Lists
WLI2
WLI2
WLI2
WLFF
RWLF2056
WLFI
RWLF2055
WLFJ
RWLF2055
Mass release of billing
documents to
accounting
Mass Release of
Remuneration Lists to
Accounting
Generate Settlement
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
WLFK
RWLF2056
WLFL
RWLF2056
WLFM
RWLF9039
WLFN
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
WRL4
RWLF2056
WAB_RELEASE
WBL4
RWLF2056
Create posting lists from
preceding
documents
Create Settlement Document
Lists from Customer
Settlement Lists
Complete Settlement
Request
Lists
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
WBLR
RWLF2052
WLFV
RWLF9039
Mass Release of Settlement
Management
Documents
Mass Release of Settlement
Management
Documents
Generate Customer Settlement
Lists from Settlement
Documents
Create Settlement Document
Lists
WLFW
RWLF2057
WAB_CLOSE
WLFLK
RWLF2056
S_AL0_9
6000192
RWLF2051
S_AL0_9
6000197
RWLF9039
Mass Completion of Settlement
Management
Documents
Mass Release of Settlement
Management
Documents
Generate Customer Settlements
from Settlement
Documents
Create Settlement Document
Lists
S_AL0_9
6000212
RWLF2056
WAB_RELEASE
S_AL0_9
6000307
RWLF2055
S_AL0_9
6000308
RWLF2055
Mass Release of Settlement
Management
Documents
Mass Cancellation of Settlement
Management
Documents
Mass Cancellation of Settlement
Management
Documents
Simplification List for SAP S/4HANA 1610
WAB_RELEASE
WAB_CANCEL
WAB_CANCEL
WAB_RELEASE
WAB_RELEASE
WLF_RRLE_CREAT
E
WAB_RELEASE
WBLRN
WLF_RRLE_CREAT
E
WAB_RELEASE
WLF1K
WLF_RRLE_CREAT
E
WAB_CANCEL
WAB_CANCEL
92
RWLF2021
Mass Cancellation of
Remuneration
Lists
Mass Cancellation of
Customer Settlement
Lists
Mass Price Determination for
Settlement Request
Lists
Mass Price Determination for
Payment
Documents
Create Remuneration Lists
from Expense
Settlements
Mass Release of Expense
Settlements for Financial
Accounting
Mass Cancellation of
Expense
Settlement
Complete Settlement
Requests
S_AL0_9
6000306
RWLF2055
S_AL0_9
6000309
RWLF2055
S_AL0_9
6000324
RWLF2054
S_AL0_9
6000325
RWLF2054
S_AL0_9
6000333
RWLF9039
S_AL0_9
6000335
RWLF2056
S_AL0_9
6000336
RWLF2055
S_AC0_5
2000143
RWLF2057
RWLF2029
Complete Vendor Billing
Documents
S_AC0_5
2000169
RWLF2057
RWLF2030
Create Settlement Request
Lists from Preceding
Documents
Complete Expenses
Settlements
WRLV
RWLF2053
S_AC0_5
2000170
RWLF2057
RWLF2032
Reopen Settlement
Requests
S_AC0_5
2000172
RWLF2058
RWLF2033
Reopen Vendor Billing
Documents
S_AC0_5
2000174
RWLF2058
RWLF2034
Reopen Expenses
Settlements
S_AC0_5
2000175
RWLF2058
RWLF2059
Generate Posting Lists from
Settlement
Requests
Dispatcher: Create Posting
Lists
WBLRO
RWLF2052
WBLRO_
DISP
RWLF2052D
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
WLF1KO
RWLF2051
WRLVO
RWLF2053
WACLFR
WLF_DEL
WACBLR
WBU_DEL
WACLRR
WRECH_DEL
RWLF2022
RWLF2023
RWLF2024
RWLF2025
RWLF2026
RWLF2027
RWLF2028
RWLF2031
RWLF2059
D
RWLF2060
RWLF2061
RWLF4001
RWLF4002
RWLF4003
Mass Cancellation of Settlement
Management
Documents
Mass Cancellation of Settlement
Management
Documents
Mass Pricing for Settlement
Management
Documents
Mass Pricing for Settlement
Management
Documents
Create Settlement Document
Lists
WAB_CANCEL
Mass Release of Settlement
Management
Documents
Mass Cancellation of Settlement
Management
Documents
Mass Completion of Settlement
Management
Documents
Mass Completion of Settlement
Management
Documents
Generate Vendor Settlement Lists
from Settlement
Documents
Mass Completion of Settlement
Management
Documents
Mass Reopening of Settlement
Management
Documents
Mass Reopening of Settlement
Management
Documents
Mass Reopening of Settlement
Management
Documents
Generate Customer Settlement
Lists from Settlement
Documents
Dispatcher: Create Customer
Settlement Lists
WAB_RELEASE
Generate Customer Settlements
from Settlement
Documents
Generate Vendor Settlement Lists
from Settlement
Documents
Archiving Vendor Billing Docs and
Vendor Settlements: Delete
Program
Archiving Customer Settlement
Lists: Delete Program
WLF1K
WAB_CANCEL
WAB_PRICING
WAB_PRICING
WLF_RRLE_CREAT
E
WAB_CANCEL
WAB_CLOSE
WAB_CLOSE
WRLVN
WAB_CLOSE
WAB_REOPEN
WAB_REOPEN
WAB_REOPEN
WBLRN
WBLRN_DISP
WRLVN
Archiving Settlement Document
Lists: Delete Program
Simplification List for SAP S/4HANA 1610
93
RWLF4004
RWLF4005
RWLF4006
RWLF4007
RWLF7001
RWLF7002
RWLF7003
RWLF7004
RWLF7005
RWLF9002
RWLF9003
RWLF9004
RWLF9005
RWLF9006
RWLF9007
RWLF9008
RWLF9009
RWLF9010
RWLF9011
RWLF9012
RWLF9013
Delete Archived Settlement
Documents from
Database
Delete Archived Vendor
Settlement Lists from
Database
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
Relevant Vendor Billing
Documents, Extended
Remuneration List Creation
WACZRR
WZR_DEL
Archiving Settlement Documents:
Delete Program
WACRLR
WREG_DEL
Archiving Vendor Settlement Lists:
Delete Program
WACCIR
WCI_DEL
Archiving Customer Settlements:
Delete Program
WACSIR
WSI_DEL
Archiving Expense Settlements:
Delete Program
WFL1
RWLF1051
WLI2
WFL2
RWLF1051
WFL3
RWLF1051
WFL4
RWLF1051
WFL5
RWLF1051
S_ALN_0
1000170
RWLF9039
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
Create Settlement Document
Lists
S_ALN_0
1000171
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
WAPZR
RWLF1051
WLI2
WAPRL
RWLF1051
S_ALN_0
1000172
RWLF9039
List Output Settlement
Management
Documents
List Output Settlement
Management
Documents
Create Settlement Document
Lists
S_ALN_0
1000173
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
S_ALN_0
1000174
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
S_ALN_0
1000175
RWLF_SETTLEME
NT_LIST_RL
Worklist based Creation of
Settlement Document List
(Dialog)
WLFSLRL
S_ALN_0
1000176
RWLF_SETTLEME
NT_LIST_RL
WLFSLRL
S_ALN_0
1000177
RWLF_SETTLEME
NT_LIST_RL
S_ALN_0
1000178
RWLF_SETTLEME
NT_LIST_RL
S_ALN_0
1000179
RWLF_SETTLEME
NT_LIST_RL
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)
Simplification List for SAP S/4HANA 1610
WLI2
WLI2
WLI2
WLI2
WLF_RRLE_CREAT
E
WLI2
WLF_RRLE_CREAT
E
WLFSLRL
WLFSLRL
WLFSLRL
94
RWLF9014
RWLF9015
RWLF9016
RWLF9017
RWLF9018
RWLF9019
RWLF9020
RWLF9021
RWLF9022
RWLF9023
RWLF9024
RWLF9028
RWLF9029
RWLF9030
RWLF9031
RWLF9032
RWLF9033
RWLF9034
RWLF9037
RWLF9038
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
S_ALN_0
1000371
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_ALN_0
1000372
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_ALN_0
1000373
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_ALN_0
1000375
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_ALN_0
1000376
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_AEN_1
0000032
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
Relevant Remuneration Lists
for Extended Remuneration
List Creation
Create Simulation of
Remuneration Lists from
Remuneration Lists
Generate Extended
Remuneration Lists from
Preceding Documents
S_AEN_1
0000033
RWLF_SETTLEME
NT_LIST_RL
WLFSLRL
S_AEN_1
0000034
RWLF9042
Worklist based Creation of
Settlement Document List
(Dialog)
Simulate Settlement Document
Lists
S_AEN_1
0000060
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
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
S_AEN_1
0000065
RWLF_SETTLEME
NT_LIST_RL
WLFSLRL
S_AEN_1
0000066
RWLF9042
Worklist based Creation of
Settlement Document List
(Dialog)
Simulate Settlement Document
Lists
S_E37_1
7000019
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
S_E37_1
7000020
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_PRN_5
3000718
RWLF9039
Create Settlement Document
Lists
WLF_RRLE_CREAT
E
Generate Simulation of
Remuneration Lists from
Vendor Settlements
Relevant Vendor Settlements
for 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
S_PRN_5
3000719
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_PRN_5
3000720
RWLF_SETTLEME
NT_LIST_RL
WLFSLRL
S_E4R_3
5000021
RWLF9039
Worklist based Creation of
Settlement Document List
(Dialog)
Create Settlement Document
Lists
S_E4R_3
5000022
RWLF9042
Simulate Settlement Document
Lists
WLF_RRLE_SIM
S_E4R_3
5000025
RWLF_SETTLEME
NT_LIST_RL
WLFSLRL
S_E4R_3
5000024
RWLF_SETTLEME
NT_LIST_RL
Worklist based Creation of
Settlement Document List
(Dialog)
Worklist based Creation of
Settlement Document List
(Dialog)
Simplification List for SAP S/4HANA 1610
WLF_RRLE_SIM
WLF_RRLE_SIM
WLF_RRLE_CREAT
E
WLFSLRL
95
RWLF9080
Posting List Creation
Dispatcher
S_AEN_
1000003
7
RWLF2052D
Dispatcher: Create Customer
Settlement Lists
WBLRN_DISP
RWLF9081
Customer Settlement
Creation
Dispatcher
S_AEN_1
0000038
RWLF2051D
Dispatcher: Create Customer
Settlements
WLF1K_DISP
RWLF9082
Mass Release
Dispatcher
S_AEN_1
0000075
RWLF2056D
Dispatcher: Mass Release of
Settlement Management
Doc.
WAB_RELEASE_DI
SP
RWLF9083
Settlement Request List
Creation
Dispatcher
S_AEN_1
0000074
RWLF2053D
Dispatcher: Create Vendor
Settlement Lists
WRLVN_DISP
RWLF9084
Extended Remuneration List
Creation
Dispatcher
S_AEN_1
0000083
RWLF9039D
Dispatcher: Create Settlement
Document Lists
WLF_RRLE_CREAT
E_DISP
RWLF9085
Dispatcher Message
Output
S_E37_1
7000021
RWLFWR14D
Dispatcher: Message Output for
Settlement Mgmt
Documents
WLN14D
RWLF9086
Dispatcher Mass
Reversal
RWLF2055D
WAB_CANCEL_DIS
P
RWLFFLOW
Display Document Flow
Information for Settlement
Management Documents
Extended IDoc
Reporting
WLFU
RWLF1051
WLFEIR
RWLFIDOC_NEW
Dispatcher: Mass Cancellation of
Settlement Management
Docs
List Output Settlement
Management
Documents
IDoc
Processing
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
Documents
Messages from Vendor
Billing
Documents
Messages from Customer
Settlement
Lists
Messages from
Remuneration Lists for
Vendor Billing
Documents
Messages from settlement
requests
WLFM30
RWLFM99
WLFM99
WLFM31
RWLFM99
WLFM32
RWLFM99
WLFM60
RWLFM99
WLFM40
RWLFM99
WLN1
RWLFWR14
WLN2
RWLFWR14
WLN3
RWLFWR14
Automatic Document Adjustment
of Settlement Management
Documents
Automatic Document Adjustment
of Settlement Management
Documents
Automatic Document Adjustment
of Settlement Management
Documents
Automatic Document Adjustment
of Settlement Management
Documents
Automatic Document Adjustment
of Settlement Management
Documents
Issue Messages from Settlement
Management
Documents
Issue Messages from Settlement
Management
Documents
Issue Messages from Settlement
Management
Documents
WLN4
RWLFWR14
WLN14
Messages from Settlement
Request
Lists
WLN5
RWLFWR14
Issue Messages from Settlement
Management
Documents
Issue Messages from Settlement
Management
Documents
RWLFIDOC
RWLFM30
RWLFM31
RWLFM32
RWLFM40
RWLFM40
RWLFWR01
RWLFWR02
RWLFWR03
RWLFWR04
RWLFWR05
Simplification List for SAP S/4HANA 1610
WLI2
WLF_IDOC
WLFM99
WLFM99
WLFM99
WLFM99
WLN14
WLN14
WLN14
WLN14
96
RWLFWR06
Messages from
Remuneration Lists for
Settlement Requests
Messags from Customer
Settlements
WLN6
RWLFWR14
WLN10
RWLFWR14
RWLFWR11
Messages from Expenses
Settlements
WLN11
RWLFWR14
RWLFWR12
Messages from
Remuneration Lists for
Customer
Settlements
Messages from
Remuneration Lists for
Expenses Settlements
Archive Customer
Settlements
WLN12
RWLFWR14
WLN13
RWLFWR14
WACCIA
WCI_WRI
Archive Settlement
Document
List
Archive Vendor Billing
Documents
WACLA
WRECH_WRI
Archiving Settlement Document
Lists: Write Program
WACLFA
WLF_WRI
Archive Customer
Settlement
Lists
Activate Expense
Settlements
WACBA
WBU_WRI
Archiving Vendor Billing Docs and
Vendor Settlements: Write
Program
Archiving Customer Settlement
Lists: Write Program
WACSIA
WSI_WRI
Archiving Expense Settlements:
Write Program
Archive Settlement Request
List
Archive Settlement
Documents
Read Vendor Billing
Documents from the Archive
(Display Items)
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
WACRLA
WREG_WRI
WACZRA
WZR_WRI
WLFT
RWLFLIST
Archiving Vendor Settlement Lists:
Write Program
Archiving Settlement Documents:
Write Program
Document Monitor
WLI5
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
RWLFWR10
RWLFWR13
RWLWRCIN
V
RWLWRILS
RWLWRINV
RWLWRPLS
RWLWRSIN
V
RWLWRSLS
RWLWRSM
R
RWLF3001
RWLF3002
RWLF3003
RWLF3004
RWLF3005
RWLF3006
RWLF3007
Obsolete Tcode
WLR1
WBL1
OAGZ
Issue Messages from Settlement
Management
Documents
Issue Messages from Settlement
Management
Documents
Issue Messages from Settlement
Management
Documents
Issue Messages from Settlement
Management
Documents
WLN14
Issue Messages from Settlement
Management
Documents
Archiving Customer Settlements:
Write Program
WLN14
WLN14
WLN14
WLN14
Successor Tcode
WLFSLRL
WBLRN
n/a
Simplification List for SAP S/4HANA 1610
97
2.1.5.1.3
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 DBStructures. 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.
2.1.5.1.4 Related SAP Notes
Custom
Code
related SAP Notes: 2197892, 2197898, 2204135, 2203518.
information
2.1.6
2.1.6.1
Logistics – ATP
New advanced ATP in SAP S/4HANA – Table VBBS
2.1.6.1.1
Description
Database table VBBS contained pre-aggregated sales requirements. The requested (OMENG) and
confirmed (VMENG) quantities were 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 code is also
redirected to use VBBE.
2.1.6.1.2 Business Process related information
No impact on business processes is expected. The customizing where the VBBS could previously be
activated in the Business Suite has been deactivated in SAP S/4HANA, on-premise edition 1511. New
entries will automatically "choose" to use VBBE instead of VBBS.
2.1.6.1.3 Required and Recommended Action(s)
There are two optional checks to be carried out before the upgrade to verify 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 second 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.
If you are still using table VBBS, please read the related note 2209696 how to convert your data after
upgrade.
If you have custom code calling table VBBS, create a db view on table VBBE, and use that view
instead of the table VBBS.
Simplification List for SAP S/4HANA 1610
98
2.1.6.1.4 Related SAP Notes
Custom Code related information
2.1.6.2
SAP Note: 2209696
icon (E2open)
2.1.6.2.1
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.
2.1.6.2.2
Business Process related information
The icon-scm planning engine and algorithms can't be used any more. Business processes which are
based on the icon-scm planning engine and algorithms can't be used any more.
2.1.6.2.3 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 1511.
2.1.6.2.4 Related SAP Notes
Custom Code related information
2.1.6.3
SAP Note: 2228349
New fashion solution
2.1.6.3.1
Description
The new fashion solution comprising characteristic based ATP is not available in SAP S/4HANA.
Appropriate Business Function LOG_SEGMENTATION will be 'always off' within SAP S/4HANA.
2.1.6.3.2
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.
2.1.6.3.3 Required and Recommended Action(s)
Do not upgrade to S4HANA for now if you rely on stock segmentation.
Simplification List for SAP S/4HANA 1610
99
2.1.7
Logistics - Direct Store Delivery (LE-DSD)
2.1.7.1
Direct Store Delivery
2.1.7.1.1
Description
The Direct Store Delivery (LE-DSD) functionalities are not available within SAP S/4HANA. The Direct
Store Delivery functionality is on the roadmap for SAP S/4HANA.
Remark:
The Direct Store Delivery (LE-DSD) is related to Business Function EA-CP. In SAP S/4HANA
1511 the status of Business Function EA-CP is defined as "always_off". If a business function
was switched on in the start release system, but defined as "always_off" in the target
release, then a system conversion is not possible. It is planned to change the state of
Business Function EA-CP so that a system conversion is possible for customers having
business function EA-CP switched on.
Customers having Business Function EA-CP not switched on in the start release system
cannot switch on this Business Function in SAP S/4HANA.
2.1.7.1.2
Business Process related information
The Direct Store Delivery (LE-DSD) functionality is not available within SAP S/4HANA 1511.
Accordingly the related business processes are not available within SAP S/4HANA.
Transaction not available in
SAP S/4HANA
/DSD/DE_ENTRY
Tour Data Entry: Entry
/DSD/DE_FUPREC
Tour Data Entry Control
/DSD/DE_SL
Tour Data Entry: Selection
/DSD/DX_AUDIT
Display DEX data for audit purpose
/DSD/RP_DYNDISP
Dynamic Transportation Planning
/DSD/SL_COCKPIT
Settlement Cockpit
/DSD/SL_FSR DSD Final Settlement Run
/DSD/SL_RADB Fill Route Accounting DB
/DSD/ST_TOUR Overview of DSD Tours
/DSD/SV_LC_COUNT Confirm Load
/DSD/SV_MAN_COR
Reprocess MM Record
/DSD/SV_RL_RELEASE Release Final Unloading Document
/DSD/SV_STOCK_AD_CR
Create SV Material Movements
/DSD/SV_STOCK_AD_DP
Display SV Material Movements
/DSD/VC_VL Maintain Visit List
/DSD/VC_VL_VIEW
Display Sales Call List
/DSD/VC_VP Maintain Visit Plans
/DSD/VC_VP_CREATE Create Sales Call Schedules
/DSD/VC_VP_VIEW
Display Sales Call Schedules
Simplification List for SAP S/4HANA 1610
100
2.1.8
2.1.8.1
Logistics - Environment, Health & Safety (EHS)
Deprecation of EHS Data Series and Amounts
Description
EHS data series information used to be stored in the so called Data Series and Amount objects in EHS.
These data objects were renovated and their information now is stored in different tables.
All data dictionary objects (like data elements, tables and so on) were marked as obsolete
(but they still exist).
All standard coding (like classes, function modules and so on) working with the above data
was deleted.
Note: These data dictionary objects and database tables had already been marked as "obsolete" with
S/4HANA 1511.
Business Process related information
See note 2065178.
Required and Recommended Action(s)
See note 2065178.
How to Determine Relevancy
This Simplification Item is relevant if you are using EHS Data Series and/or Amounts. This is usually
the case if table EHFNDD_DTS_ROOT has 5 or more entries.
2.1.8.2
Deprecation of 'Inspect Safety Control' Fiori app
Description
The Fiori application 'Inspect Safety Control' has been been deprecated and is no longer available
under S/4HANA.
Business Process related information
There is currently no successor application available.
Required and Recommended Action(s)
Inform your business users.
Simplification List for SAP S/4HANA 1610
101
How to Determine Relevancy
This Simplification Item is relevant if you have the 'Inspect Safety Control' Fiori application in use.
2.1.8.3
Deprecation of 'Retrieve Safety Information' Fiori app
Description
The Fiori application 'Retrieve Safety Information' has been been deprecated and is no longer
available under S/4HANA.
Business Process related information
There is currently no successor application available.
Required and Recommended Action(s)
Inform your business users.
How to Determine Relevancy
This Simplification Item is relevant if you have the 'Retrieve Safety Information' Fiori application in
use.
2.1.8.4
Simplification of Authorizations in Incident Management
Description
The authorization concept for Incident Management was quite hard to handle for some of the
existing authorization objects. Therefore the concept was renovated and authorization objects were
replaced.
The following authorization objects have been set to obsolete (but they still exist):
EHHSS_INC1 (EHSM: Incident)
EHHSS_INC3 (EHSM: Incident Group)
EHHSS_INC5 (EHSM: Incident by Location)
The following authorization objects have been newly introduced:
EHHSS_INC6 (EHS: Incident)
o This replaces EHHSS_INC1 and EHHSS_INC5
EHHSS_INC7 (EHS: Incident Group)
Simplification List for SAP S/4HANA 1610
102
o
This replaces EHHSS_INC3
Most authorization criteria which previously were covered by EHHSS_INC5 are now covered by
EHHSS_INC6. But some of the criteria from EHHSS_INC5 (like for example 'Location Authorization
Group') no longer exist; the mitigation of this missing authorization aspect is planned to be done in a
successor release of S/4HANA 1610. The standard implementations of the following BAdIs together
with their implementing standard classes were removed (the BAdIs themselves still exist; customer
implementations are not touched):
BADI_EHHSS_INC_EXT_AUTH_CHECK (extended authorization check based on EHHSS_INC3)
BADI_EHHSS_INC_EXT_LOC_CHECK (extended authorization check based on EHHSS_INC5)
These BAdIs (see also SAP Implementation Guide (IMG)): Environment, Health and Safety Incident
Management Business Add-Ins Business Add-Ins for Authorization BAdI: Extended Authorization
Checks) are the place where the authorization checks for the now obsolete authorization objects
EHHSS_INC3 and EHHSS_INC5 took place. As the standard implementations do no longer exist,
EHHSS_INC3 and EHHSS_INC5 are now ignored by the standard.
Business Process related information
Incident Management will not work before you have adjusted your business roles in a way that they
also contain the newly introduced authorization objects.
Required and Recommended Action(s)
Review your authorization concept and your EHS roles. Replace the obsolete authorization objects
accordingly with the new authorization objects EHHSS_INC6 and EHHSS_INC7. In case you want to
perform additional authorization checks based on the now obsolete authorization objects
EHHSS_INC3 and EHHSS_INC5, do a customer implementation of the above mentioned BAdIs. In this
case make sure that your users still own the appropriate authorizations. SAP recommends to
consider this option thoroughly and only use it if the new authorization objects are not sufficient and
you cannot wait for the planned extensions of the authorization concept. In case you have previously
already done a custom implementation of the above BAdIs please keep in mind the following:
If you have written your own class or have copied the SAP class as basis for your own
implementation, please be aware that these BAdIs are still active and working. You need to
de-activate them if you want to de-activate the processing of EHHSS_INC3 and EHHSS_INC5.
If you have derived your custom implementation class from the standard implementation
class of the BAdI, please be aware that this derived class will be deleted during the upgrade!
How to Determine Relevancy
This Simplification Item is relevant if you have EHS Incident Management in use. This is usually the
case if table EHHSSD_INC_ROOT hat 20 or more entries.
Simplification List for SAP S/4HANA 1610
103
2.1.8.5
Removal of EHS Home Screens
Description
The following EHS roles used to have a home page to enter the system:
Industrial Hygienist (SAP_EHSM_HSS_HYGIENIST)
Corporate Health & Safety Manager (SAP_EHSM_HSS_HSMGRCORP)
Hazardous Material Manager / Hazardous Substance Manager
(SAP_EHSM_HSS_HAZSUBMGR)
Sampling Technician (SAP_EHSM_HSS_SMPLTECH)
Incident Manager (SAP_EHSM_HSS_INCIDENT_MANAGER)
These home pages are no longer available in SAP S/4HANA.
Business Process related information
The users of the mentioned roles should use the following alternative approaches to access the
former home page functionality:
To access the overview charts from the former home pages, use the corresponding SAP Fiori
launchpad tiles.
o Example: To get the same information as from the "Risks" chart on the former
Industrial Hygienist home page, use the "Risk overview" tile from the SAP Fiori
launchpad.
To access the applications and activities which were accessible via links on the former home
pages, use the corresponding SAP Fiori launchpad tiles.
o Example: To start the "Search/edit risks" application as known from the former
Industrial Hygienist home page, use the "Manage Risks" tile from the SAP Fiori
lauchpad.
Required and Recommended Action(s)
Inform the end users about the changed user interface (UI) and how Fiori and the SAP Fiori
launchpad replace the former UI concepts.
How to Determine Relevancy
This Simplification Item is relevant if you use Risk Assessment or Incident Management. This is
usually the case if either table EHHSSD_INC_ROOT or table EHHSSD_RAS_ROOT has 20 or more
entries.
2.1.8.6
Simplification of Incident Management workflows
Description
Simplification List for SAP S/4HANA 1610
104
In case of a fatality or when a cost collector has been added to an incident, workflows can be
triggered to notify relevant people. These workflows have been re-worked.
The following functions in Incident Management have been replaced with new functions:
Fatality notification workflow to inform stakeholders when a fatality was maintained
in an incident
Inform involved workflow which allows the user to notify involved persons about an added
cost collector
The workflow templates 500006 Fatality Email and 800022 Inform Involved and the contained
tasks remain the same. Only internal logic of workflow templates and tasks has been changed.
Business Process related information
There are no changes in the general business logic.
Required and Recommended Action(s)
If you have used the standard template, no action is required. If you have copied one of the above
mentioned workflow templates, perform the following actions:
Deactivate the delivered workflow template 500006 / 800022.
Double check the triggering event of your copied template and also check the parameter
binding of the event.
If required, copy the new template and adapt it to your requirements.
How to Determine Relevancy
This Simplification Item is relevant if you use Incident Management. This is usually the case if table
EHHSSD_INC_ROOT has 20 or more entries.
2.1.8.7
Changed data model for listed substances
Description
A new table for listed substances has been introduced. This table serves to eliminate duplicates
between the listed substances that are created by customers and the ones that are delivered as
content. After the upgrade, you need to transfer your listed substances to this new table and
eliminate duplicate entries.
Business Process related information
There are no changes in the general business logic.
Simplification List for SAP S/4HANA 1610
105
Required and Recommended Action(s)
Run the following reports manually:
Report R_EHFND_LISU_MIGRATION transfers existing listed substances from
table EHFNDD_LISU_ROOT to the new table EHFNDD_LISU_RT.
Report R_EHFND_LISU_SUBSTITUTE eliminates duplicate entries by replacing customerspecific listed substances with SAP-specific listed substances.
How to Determine Relevancy
This Simplification Item is relevant if you make use of listed substances in EHS. This is normally the
case if you have EHS Risk Assessment, EHS Environment Management or Product and Reach
Compliance in use.
2.1.8.8
Industrial Hygiene and EC interfaces
Description
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 onpremise 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
Customers can use SAP Environmental Compliance (SAP EC) to support emissions and compliancerelevant 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.
Simplification List for SAP S/4HANA 1610
106
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 onpremise edition
1511
CBIH02,CBIH03,CBIH12,CBIH13,CBIH14,CBIH42,CBIH43,CBIH50,CBIH51,CBI
H52,CBIH72,
CBIH73,CBIH82,CBIH83,CBIH88,CBIH89,CBIHB0,CBIHB1,CBIHB2,CBIHB3,CB
IHB4,CBIHB5,CBIHB6,CBIHM2,CBIHM3,CBIHMR01,CBIHMR02,
CBIHMR03,CBIHMR04,CBIHMR05,CBIHMR06,CBIHMR07,CBIHMR08,CBIH
MR09,CBIHT0,CBIHT1,CBIHT2,CBIHT3,CBIHT4,CBIHT5,CBIHT6,CBIHT7
Related SAP Notes
Custom Code related information
2.1.8.9
SAP Note: 2217206
Occupational Health
Description
With SAP EHS Management as part of SAP ERP, customers can use the Occupational Health (EHSHEA) 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.
Business Process related information
Occupational Health (EHS-HEA) is not available in SAP S/4HANA and the related business processes
are no longer supported.
Transaction not
available in SAP
S/4HANA onpremise edition
1511
EHSAMBTAET,EHSASSIGN,EHSASSLTA,EHSASSPERS,
EHSBC02,EHSBP11,EHSBP12,EHSBP13,EHSBP31,EHSBP32,EHSBP33,EHSBP41,EHS
BP42,EHSBP43,EHSBP51,EHSBP52,EHSBP53,
EHSCALPROX,EHSCBER,EHSCDCT, EHSCMAS,EHSDATIMP,EHSDIAGSL,EHSEVAL00,
EHSEXIST0,
EHSH_C_NR_EXA_C,EHSH_C_NR_NEWPE,EHSH_C_NR_RECN,EHSH_C_NR_VAC_I,
EHSH_D_CALPHYS,EHSH_D_PCP,
Simplification List for SAP S/4HANA 1610
107
EHSMQUEST,EHSMQUEST01,EHSPERSHC1,EHSPP01,EHSPRANZ,EHSPRLOE,EHSQ
CATOH,EHSQEVAL01,EHSQUESTOH,
EHSSCAN,EHSSERV,EHSSERV01,EHSSERV11,EHSSERV30,EHSSER50,EHSSTRU00,E
HSSUGGP,EHSTERM01,
EHSVA02,EHSVU01,EHSVU01_SELSCREEN,EHSVU11,EHSVU21,EHSVU31
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2217205
2.1.8.10 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 and the related business processes
are no longer supported.
Transa
ction
not
availab
le in
SAP
S/4HA
NA onpremis
e
edition
1511
WAA01,WAA02,WAA03,WAA04,WAA10,WAA11,WAA12,WAA13,WAA19,WAA20,WAA21,W
AA22,WAA23,WAA24,WAA25,WAA26, WAAP,
WACB01,WACM01,WACM02,WACM03,WACM04,WACM10,WACM30,WACO02,WACO02OL
D,WACO03OLD,WACO04OLD,
WACS1,WACS2,WACS3,WACS4,WACS6,WADC,WADI,WAE01,WAE02,WAE03,WAE10,WAEA,
WAGE, WAM01,
WAM02,WAM03,WAM04,WAM05,WAMC,WAMI,WAMR,WANP,WAREP001,
WASM100,
WASM101,WASM102,WASM109,WASS100,WASS101,WASS102,WASS103,WASS104,WASS1
05,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)
Simplification List for SAP S/4HANA 1610
108
None
Related SAP Notes
Custom Code related information
SAP Note: 2217202
2.1.8.11 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, the 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
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 1511. There is no functional
equivalent available. Reporting for chemicals is not available in SAP S/4HANA on-premise edition
1511. There is no functional equivalent available. The amounts/data series function is not available
Simplification List for SAP S/4HANA 1610
109
within SAP S/4HANA, on-premise edition 1511. You can collect amounts using workplace sampling
process. For more information, see SAP Note 2065178.
Required and Recommended Actions
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
Custom Code related information
Additional related SAP Notes
SAP Note: 2194782
SAP Note: 2217208
SAP Note: 2065178
2.1.8.12 Removal of EHS workflows for requesting controls, impacts, agents
Description
Within EHS Risk Assessment there used to be various places where - during a process - the user could
request the creation of certain missing master data objects by clicking a link or a button and thereby
starting a creation workflow to an administrator. As these workflows are quite cumbersome and
oversized for that task, this functionality was removed and the workflows were deleted.
The following functions no longer exist in Health and Safety Management (formerly known as Risk
Assessment)
Requesting controls ...
o ... while editing controls in a Risk Assessment
o ... while identifying risks using the guided activity for Risk Identification
Requesting impacts ...
o ... while editing impacts in the Edit Impact popup window
Simplification List for SAP S/4HANA 1610
110
o ... while identifying risks using the guided activity for Risk Identification
Requesting agents ...
o ... while identifying risks using the guided activity for Risk Identification
Requesting hazards ...
o ... while identifying risks using the guided activity for Risk Identification
Technical Details
The following WebDynpro component configurations were changed so that the according buttons
and links are no longer shown on the screens.
EHHSS_RAS_OIF_NEWCONTR_LST (for Controls)
EHHSS_RAS_IDENTIF_CON_LST (for Controls)
EHHSS_RAS_OIF_REV_IMP_LST (for Impacts)
EHHSS_RAS_IDENTIF_IMP_LST (for Impacts)
EHHSS_RAS_HAZ_PHYS_AGT_LST (for Agents)
EHHSS_RAS_IDENTIF_HAZARD_LST (for Hazards)
EHHSS_RAS_HAZ_PHYS_AGT_LST (for Hazards)
EHHSS_RAS_IDENTIF_HAZ_JHA_LST (for Hazards)
EHHSS_RAS_IDENTIF_CHM_DLG_LST (for Hazards)
EHHSS_RAS_IDENTIF_AIRBOR_DLG_LST (for Hazards)
Business Process related information
The creation of needed master data within the above processes will have to be managed differently
in the future. Triggering an administrator to perform this activity should be done via traditional
channels like telephone or email.
Required and Recommended Action(s)
Knowledge transfer to key and end users.
How to Determine Relevancy
This Simplification Item is relevant if you have EHS Risk Assessment in use. This is usually the case if
table EHHSSD_RAS_ROOT has 20 or more entries.
2.1.8.13 Responsible person for Planned Maintenance at EHS locations
Description
The EHS Location master data object used to have a screen to maintain the Planned Maintenance
responsible person for this location. In SAP S/4HANA this screen is not shown for locations which are
linked to S/4HANA Enterprise Asset Management (EAM) objects (like e uip e t s or functional
locations).
Business Process related information
Simplification List for SAP S/4HANA 1610
111
The Planned Maintenance responsible person is redundant information within EHS as it already has
been maintained at the linked EAM object. Users can jump to the linked EAM object from EHS by
clicking on it. There the responsible person can be viewed.
Required and Recommended Action(s)
Knowledge transfer to key and end users.
How to Determine Relevancy
This Simplification Item is relevant if you have EHS Risk Assessment in use. This is usually the case if
table EHHSSD_RAS_ROOT has 20 or more entries.
2.1.8.14 Remote Integrationsszenarien mit EHS Health and Safety Management
Description
The following remote integration scenarios for EHS under S/4HANA are no longer supported:
Integration of EHS with an external Enterprise Asset Management (EAM, PM) system
Integration of EHS with an externalWork Clearance Management (WCM) system
Integration of EHS with an externalMaterial Management / Inventory Management
(MM/IM) system
Integration of EHS with an external substance or specification database
Integration of EHS with an externalFinancials (FIN/Accounting) system
Integration of EHS with an external Human Resources, Human Capital Management(HR,
HCM) system
Integration of EHS with an external business partner (BuPa) administration
Business partner process-related information
It is only possible in S/4HANA with the S/4HANA own functions and modules to integrate the above
areas. Other integrations are not supported.
Required and recommended action(s)
Contact your SAP Account Manager, if you currently connect EHS with an external system of the type
described above, and discuss possible alternatives.
Determination of relevance
This simplification item is relevant if you want to connect EHS with one or several external systems of
the types mentioned above.
Simplification List for SAP S/4HANA 1610
112
2.1.8.15 Collection of various small and medium sized changes in EHS
You want to convert component extension for SAP EHS Management or EHS Management as part of
SAP ERP to SAP S/4HANA 1610. The attached conversion information provides information about
specific activities for Environment, Health, and Safety that you have to carry out before or after the
conversion. For general information about converting to SAP S/4HANA, see the conversion guide on
the SAP Help Portal at http://help.sap.com/s4hana_op_1610.
Description
see attachment of Businss Impact Note
Business Process related information
see attachment of Businss Impact Note
Required and Recommended Action(s)
see attachment of Businss Impact Note
How to Determine Relevancy
This Simplification Item is relevant if you have EHS Risk Assessment or EHS Incident Management in
use. This is usually the case if table EHHSSD_RAS_ROOT has 20 or more entries or if table
EHHSSD_INC_ROOT has 20 or more entries.
2.1.9
2.1.9.1
Logistics – GT
Global Trade Management
2.1.9.1.1
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
2.1.9.1.2 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.
Simplification List for SAP S/4HANA 1610
113
Differential Invoicing is not part of SAP S/4 HANA anymore because these transactions are replaced
already in SAP ERP EHP7.
Transaction Codes and Reports not available in SAP S/4HANA
See also note 2204137
Obsolete Report
Obsolete
Report
Title
RWB2B001
Trading
Contract:
General
Document
Overview
RWB2B001
Trading
Contract:
General
Document
Overview
WB2B_CREATE_TC_USER Create
User For
TC At Web
Obsolete TCode
Successor
Report
WB24
RWB2BREL
WB25_COMP
RWB2BMAS
Successor
Report
Title
Trading
Contract:
Follow on
document
prosessing
Mass
Processing
(Release
and Status
update)
Successor
TCode
WBRR
WB24N
WB2B_NETUSER
Obsolete TCode Successor TCode
POFO1
POFO31
POFO2
POFO32
POFO3
POFO33
2.1.9.1.3
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 DBStructures. 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.
2.1.9.1.4 Related SAP Notes
Custom Code related information
SAP Notes: 2198031, 2204137, 2198035
Simplification List for SAP S/4HANA 1610
114
2.1.10 Logistics Material Management Inventory Management (MM-IM)
2.1.10.1 DATA MODEL IN INVENTORY MANAGEMENT (MM-IM)
You have customer enhancements, modifications or own functionalities in the area of inventory
management (component MM-IM) which were built for SAP ERP 6.0.
You are using functionalities which behave different in SAP S/4HANA Supply Chain (MM - Inventory
Management) compared to Suite on HANA. 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 database 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 all in one place: MATDOC. All below
mentioned tables of the SAP ERP 6.0 product do still exist in S/4HANA as DDIC definition as well as
database 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 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.
The affected tables are:
Table
MKPF
MSEG
MARC
Table description
DDL Source of CDS
View for redirect
Material document
NSDM_DDL_MKPF
header
Material document item NSDM_DDL_MSEG
Plant Data for Material NSDM_DDL_MARC
View to read
View to read the
the master
content of the database
data
table (w/o redirect to
attributes
compatibility view)
only
NSDM_MIG_MKPF
-
NSDM_MIG_MSEG
NSDM_MIG_MARC
V_MARC_MD
Simplification List for SAP S/4HANA 1610
115
MARD
MCHB
MKOL
MSLB
MSKA
MSSA
MSPR
MSSL
MSSQ
MSKU
MSTB
MSTE
MSTQ
MCSD
MCSS
MSCD
MSCS
MSFD
MSFS
MSID
MSIS
MSRD
MSRS
MARCH
MARDH
MCHBH
MKOLH
MSLBH
Storage Location Data
for Material
Batch stocks
Special Stocks from
Vendor
Special Stocks with
Vendor
Sales Order Stock
Total Customer Orders
on Hand
Project Stock
Total Special Stocks with
Vendor
Project Stock Total
Special Stocks with
Customer
Stock in Transit
Stock in Transit to Sales
and Distribution
Document
Stock in Transit for
Project
DIMP: Customer Stock
DIMP: Total Customer
Stock
DIMP: Customer stock
with vendor
DIMP: Customer stock
with vendor - Total
DIMP: Sales Order Stock
with Vendor
DIMP: Sales Order Stock
with Vendor - Total
DIMP: Vendor Stock
with Vendor
DIMP: Vendor Stock
with Vendor - Total
DIMP: Project Stock
with Vendor
DIMP: Project Stock
with Vendor - Total
History
History
History
History
History
NSDM_DDL_MARD
NSDM_MIG_MARD
V_MARD_MD
NSDM_DDL_MCHB
NSDM_MIG_MCHB
V_MCHB_MD
NSDM_DDL_MKOL
NSDM_MIG_MKOL
V_MKOL_MD
NSDM_DDL_MSLB
NSDM_MIG_MSLB
V_MSLB_MD
NSDM_DDL_MSKA
NSDM_MIG_MSKA
V_MSKA_MD
NSDM_DDL_MSSA
NSDM_MIG_MSSA
-
NSDM_DDL_MSPR
NSDM_MIG_MSPR
V_MSPR_MD
NSDM_DDL_MSSL
NSDM_MIG_MSSL
NSDM_DDL_MSSQ
NSDM_MIG_MSSQ
-
NSDM_DDL_MSKA
NSDM_MIG_MSKU
V_MSKU_MD
NSDM_DDL_MSTB
NSDM_MIG_MSTB
-
NSDM_DDL_MSTE
NSDM_MIG_MSTE
-
NSDM_DDL_MSTQ
NSDM_MIG_MSTQ
-
NSDM_DDL_MCSD
NSDM_MIG_MCSD
MCSD_MD
NSDM_DDL_MCSS
NSDM_MIG_MCSS
MCSS_MD
NSDM_DDL_MSCD
NSDM_MIG_MSCD
MSCD_MD
NSDM_DDL_MSCS
NSDM_MIG_MSCS
MSCS_MD
NSDM_DDL_MSFD
NSDM_MIG_MSFD
MSFD_MD
NSDM_DDL_MFS
NSDM_MIG_MSFS
MSFS_MD
NSDM_DDL_MSID
NSDM_MIG_MSID
MSID_MD
NSDM_DDL_MSIS
NSDM_MIG_MSIS
MSIS_MD
NSDM_DDL_MSRD
NSDM_MIG_MSRD
MSRD_MD
NSDM_DDL_MSRS
NSDM_MIG_MSRS
MSRS_MD
NSDM_DDL_MARCH
NSDM_DDL_MARDH
NSDM_DDL_MCHBH
NSDM_DDL_MKOLH
NSDM_DDL_MSLBH
NSDM_MIG_MARCH
NSDM_MIG_MARDH
NSDM_MIG_MCHBH
NSDM_MIG_MKOLH
NSDM_MIG_MSLBH
Simplification List for SAP S/4HANA 1610
116
MSKAH
MSSAH
MSPRH
MSSQH
MSKUH
MSTBH
MSTEH
MSTQH
MCSDH
MCSSH
MSCDH
MSFDH
MSIDH
MSRDH
History
History
History
History
History
History
History
History
History
History
History
History
History
History
NSDM_DDL_MSKAH
NSDM_DDL_MSSAH
NSDM_DDL_MSPRH
NSDM_DDL_MSSQH
NSDM_DDL_MSKAH
NSDM_DDL_MSTBH
NSDM_DDL_MSTEH
NSDM_DDL_MSTQH
NSDM_DDL_MCSDH
NSDM_DDL_MCSSH
NSDM_DDL_MSCDH
NSDM_DDL_MSFDH
NSDM_DDL_MSIDH
NSDM_DDL_MSRDH
NSDM_MIG_MSKAH
NSDM_MIG_MSSAH
NSDM_MIG_MSPRH
NSDM_MIG_MSSQH
NSDM_MIG_MSKAH
NSDM_MIG_MSTBH
NSDM_MIG_MSTEH
NSDM_MIG_MSTQH
NSDM_MIG_MCSDH
NSDM_MIG_MCSSH
NSDM_MIG_MSCDH
NSDM_MIG_MSFDH
NSDM_MIG_MSIDH
NSDM_MIG_MSRDH
-
The hybrid tables of the former Industry Solution DIMP have now new tables containing the material
master data only. The name of the new tables is presented in the right column of above
table. According to the fact that data will not persisted anymore in the header and item tables MKPF
and MSEG the transaction DB15 behaves differently in the environment of archiving. Transaction
DB15, which allows the retrieval of statistical data for DB tables grouped by the archiving objects that
refer to these tables, does not provide correct information for tables MKPF and MSEG. When
selecting tables from which data is archived for archiving object MM_MATBEL, and navigating to
Online Space or Space Statistics for tables MKPF or MSEG, the statistics No. Records and Table Space
are shown in the result screen. These numbers are taken from the original tables MKPF and MSEG,
and not calculated by redirecting the request to table MATDOC. Consequently, when executing
archiving for arching object MM_MATBEL, this will have no effect on the numbers shown for tables
MKPF and MSEG in transaction DB15.
Solution
One impact of the simplified MM-IM data model does exist if there are customer APPENDs or
INCLUDEs with customer fields on the mentioned tables. The NetWeaver redirect capability requires
that DB table and assigned proxy view is compatible in the structure: number of fields, their
sequence and their type. Thus if there is an APPEND or INCLUDE on one of the above mentioned
tables then the assigned DDL source of the CDS view must be made compatible. In some cases for
S/4HANA on-premise 1511 this does not require customer interaction especially in those cases where
the append has been put at the end of a table which is strongly recommended (not somewhere in
between which may happen if a table is composed by include structures like for MARC). For other
cases and in general for S/4HANA on-premise 1610 the structure of the proxy view can be made
compatible to the table by extension view. This extension view is always an extension to the above
mentioned view in the DDL source of the CDS view used for redirect. In the extension view the fields
have to be listed in exactly the same order as in the append. For more information about view
extension see e.g. SAP NetWeaver 7.4 documentation.
Simplification List for SAP S/4HANA 1610
117
Another impact of the simplified MM-IM data model is a performance decrease of DB read
operations on the above mentioned tables just because a data fetch on one of the mentioned tables
is in S/4HANA slower than in SAP ERP 6.0 due to the on-the-fly aggregation and the JOIN operation.
Hence performance critical customer coding may be adjusted to improve performance. Furthermore
customer coding writing data to aggregated actual stock quantity or to the former document header
or item table shall be adjusted!
1. Customer Appends
With SAP Note 2194618 and 2197392 SAP offers a check to be executed on the start release to
identify APPEND issues described in the following sub chapters. Hence customer is not forced to scan
all above listed tables manually.
1.1 Customer Appends on the former document tables MKPF and MSEG
If there are APPENDs on MKPF and MSEG where fields with the same fieldname do exist then there is
a name conflict in case that the content of field MKPF-A is different from field MSEG-A (fields with
same name and identical content do exist on MKPF and MSEG also in SAP Standard for performance
reasons e.g. BUDAT). In this case it is required to add a further field A_NEW to the append, copy the
data from A to A_NEW with a special customer program and then all coding sections, Dynpros, etc.
need to be adjusted to use A_NEW and then field A needs to be dropped from the append. This must
be done before migration from ERP 6.0 to S/4HANA.
If the attributes in the APPENDs or INCLUDEs (e.g. CI_M* INCLUDEs as introduced with consulting
note 906314) on table MKPF and MSEG do have a master data or process controlling character then
the fields from the APPENDs/INCLUDEs need to be appended to the table MATDOC and the assigned
proxy views can be made compatible via extension views.
In case of a system conversion all these customer fields in such APPENDs or INCLUDEs need to be
appended to table MATDOC during the ACT_UPG phase (SPDD). It has to be done in any case before
the MM-IM converison program will be executed which move the data from MKPF and MSEG to
MATDOC otherwise data in customer fields gets lost. The structure compatibility between table
MKPF/MSEG and their assigned proxy view shall be created directly after system conversion by
creating extend views, see note 2242679.
Fields from APPENDs/INCLUDEs to table MKPF should be appended to sub structure
NSDM_S_HEADER of table MATDOC.
Fields from APPENDs/INCLUDEs to table MSEG should be appended to sub structure NSDM_S_ITEM
of table MATDOC.
1.1.1 Customer include CI_COBL in table MSEG
Table MSEG contains the customer include CI_COBL where customers can insert own fields. The
CI_COBL include has been made available also in the new MM-IM data model with note 2240878.
This note must be applied before the data migration starts in the ACT_UPG phase (SPDD); otherwise
you may loose data. With the implemented CI_COBL the table MSEG and it's assigned proxy view is
Simplification List for SAP S/4HANA 1610
118
not compatible in their structure anymore. The structural compatibility can be re-created by applying
note 2242679. This must be done directly after system conversion has been finished.
1.2 Customer Appends on the hybrid and replaced aggregation tables
1.2.1 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 within S/4HANA on-premise 1511. Due to too many side
effects like unpredictable sequence of fields from APPENDs, this has been changed with S/4HANA
On-Premise 1610 where always an EXTEND VIEW for a CDS proxy view has to be created for an
APPEND on a material master data table. For the DIMP tables the append has to be appended also to
the new pure DIMP material master data tables.
The structural compatibility between table and CDS proxy view can be re-created by applying
note 2242679. This must be done directly after system conversion has been finished (e.g. creating
just an EXTEND VIEW with the customer fields using ABAP Development Tools for S/4HANA On
Premise 1610 and higher).
For replaced aggregation tables appends with master data attributes are not supported. 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 the appends requires maybe some
additional customer coding.
1.2.2 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 (T156,
T156SY, T156M, T156F) - which controls in the core functionality the mapping between a posting and
a stock type - then the process logic needs to be adapted.
1.3 Customer Appends on views
There are several views in SAP Standard which also do have an assigned proxy view because the view
provide actual stock quantity data. View and assigned proxy view must be compatible in structure
too. If there are customer appends on such view the same rules as for tables apply. Views with
assigned proxy compatibility view can be determined by searching via transaction SE16N in table
DD02L with TABCLASS = VIEW and VIEWREF <> '' or you may use above mentioned check
functionality in your start release.
1.3.1 Customer views on MKPF/MSEG
Views are database objects and thus a view is executed on the database. Because the table MKPF
and MSEG will not contain data anymore (except legacy data from migration) such a customer view
Simplification List for SAP S/4HANA 1610
119
will never return any record. Such views have to be either adjusted by fetching data from table
MATDOC or to be created new as DDL source with a different name. In the last case all usages of the
old DDIC SQL view must be replaced by the new CDS view.
1.3.2 Customer views on material master attributes
Such views using only material master data attributes from the hybrid tables do not need to be
changed.
1.3.3 Customer views using aggregated stock quantity data
Customer views having at least one actual stock quantity aggregate cannot be used anymore because
-
the field representing this aggregate on the database will be empty forever
the quantity must be aggregated from table MATDOC which is not possible with DDIC SQL
views.
Such views must be defined new as DDL source with a new name. Each of the above mentioned DDL
sources can be used as template. All usages of the old DDIC SQL view must be replaced by the new
CDS view.
2 Code adjustments and optimizations
Technically it is still possible to do DB write operations (INSERT, UPDATE, DELETE, MODIFY) 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 from customer coding. Write operations on the
material master data attributes in the hybrid tables are still possible. Write operations on table
MATDOC and your moved customer append fields are done by class CL_NSDM_STOCK.
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 from 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 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.
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.
Simplification List for SAP S/4HANA 1610
120
For table MARC and field STAWN valid from S/4HANA On Premise 1610 please read
note #mce_temp_url#
For performance critical coding parts these adjustments are strongly recommended. For non critical
parts it is optional short term but recommended on long term.
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.
Consider SAP Note 28022 if there are issues with the where-used functionality in the customer
system. In the where-used dialog it is possible via the button "Search Range" to search specific for
key words like SELECT, INSERT and so on.
2.1.10.2 AVAILABILITY OF TRANSACTIONS IN MM-IM
The following transactions for entering and displaying goods movements (material documents) called "MB transactions" - below, have been replaced by the single-screen generalized transaction
MIGO:
MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL,
MBSF, MBSL, MBST and MBSU
The transaction MMBE_OLD has been replaced by transaction MMBE. Alternatively there is also the
Fiori App Stock Overview
These transaction do still exist as transaction codes but calling these transaction codes from the
menu has the consequence that an error message is raised.
These transaction codes shall not be used in customer coding.
The transaction codes will be deprecated in the near future.
Solution
-
Use transaction MIGO or MMBE in dialog.
Replace customer coding using these MB transaction codes by make use of function module
BAPI_GOODSMVT_CREATE-
2.1.10.3 Material Ledger Obligatory for Material Valuation
Description
This simplification makes it mandatory to use the Material Ledger (ML) in all SAP S/4HANA systems.
After the technical SUM migration, the Material Ledger needs to be migrated.
Simplification List for SAP S/4HANA 1610
121
Relevant IMG migration activities:
Customizing migration:
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1511: transaction: SPRO -->
Migration from SAP ERP Accounting powered by SAP HANA --> Preparations and
Migration of Customizing --> Preparations and Migration of Customizing for Material
Ledger --> Migrate Material Ledger Customizing
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1610: transaction: SPRO -->
Migration to SAP S/4HANA Finance --> Preparations and Migration of Customizing -->
Preparations and Migration of Customizing for Material Ledger --> Migrate Material
Ledger Customizing
Data migration:
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1511: transaction: SPRO -->
Migration from SAP ERP Accounting powered by SAP HANA --> Migration --> Material
Ledger Migration
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1610: transaction: SPRO -->
Migration to SAP S/4HANA Finance --> Data Migration --> Start and Monitor Data
Migration
You need to migrate the Material Ledger even if you are already using SAP Simple Finance (that is,
you are migrating from SAP Simple Finance to SAP S/4 HANA Inventory Management). In addition,
you need to migrate the Material Ledger even if you are already using the Material Ledger in your
source system. If you performing an upgrade from S/4HANA 1511 to S/4HANA 1610, no manual IMG
Material Ledger data migration is necessary. 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 module supports these business
requirements, it was chosen as the basis for material inventory valuation in the new SAP S/4HANA
solution. It is very important to distinguish between Material Ledger, in its role as an inventory
subledger in Accounting, and the business feature Actual Costing. Material Ledger, as the inventory
subledger, values material inventories in multiple currencies and GAAPs in parallel. In addition
Material Ledger is a basic prerequisite for the use of Actual Costing. With Actual Costing you can
value 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 more
posting periods. Actual Costing also provides additional features, such as actual cost component
splits. Even though activation of Material Ledger is now mandatory, 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 definitions as well as database objects.
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. (From S/4HANA 1610 these
transactional fields will be retrieved from the Universal Journal Entry Line Items table ACDOCA and
the Material Ledger table. For more detailed information please see SAP Note: 2337383). Hence,
those fields are not updated anymore in the original xBEW(H) tables. As a consequence, the above
mentioned tables need to be updated less often, which leads to a higher throughput due to fewer
database locks. For compatibility reasons there are Core Data Service (CDS) Views assigned as proxy
Simplification List for SAP S/4HANA 1610
122
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. (From S/4HANA
1610 transactional data from the Universal Journal Entry Line Items table ACDOCA and the Material
Ledger table. For more detailed information please see SAP Note: 2337383).
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
EBEW
Table description
Sales Order Stock
Valuation
EBEWH History of Sales
Order Stock
Valuation
MBEW Material Valuation
MBEWH History of Material
Valuation
OBEW Valuated Stock with
Subcontractor
(Japan)
OBEWH History of Valuated
Stock with
Subcontractor
(Japan)
QBEW Project Stock
Valuation
QBEWH History of Project
Stock Valuation
DDL source of CDS
view for redirect
(proxy view)
MBV_EBEW
View to read the content of
the original database table
(w/o redirect to proxy view)
MBVEBEWOLD
View to read
master data
attributes only
V_EBEW_MD
MBV_EBEWH
MBVEBEWHOLD
V_EBEWH_MD
MBV_MBEW
MBV_MBEWH
MBVMBEWOLD
MBVMBEWHOLD
V_MBEW_MD
V_MBEWH_MD
MBV_OBEW
MBVOBEWOLD
V_OBEW_MD
MBV_OBEWH
MBVOBEWHOLD
V_OBEWH_MD
MBV_QBEW
MBVQBEWOLD
V_QBEW_MD
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 already using the material ledger, 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.
Simplification List for SAP S/4HANA 1610
123
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
Custom Code related information
SAP Note: 2194618
SAP Note: 2129306
SAP Notes: 1804812
2.1.10.4 Material Valuation - Statistical moving average price
Description
One major innovation of SAP S/4HANA in the area of MM-IM is the significant increase of
transactional data throughput for high-volume transactions, especially goods movements. To enable
this from a technical point of view, it is necessary for the application logic to avoid exclusive locking
on the application layer. For goods movements this can be achieved (with a few exceptions) for
materials with price control "Standard", where the relationship between unit costs for material
inventory (standard price) on the one hand, and inventory quantity and inventory value on the other
hand, is kept constant during goods movements. To calculate a consistent moving average valuation,
the system is still forced to use exclusive locks. Therefore it is not possible to achieve the same
increase in transactional data throughput for materials with price control "Moving Average" as for
materials with price control Standard. In SAP ERP, for materials with price control "Standard" the
system also calculates a moving average valuation in parallel, the so-called "statistical" moving
average price. Obviously this statistical valuation requires exclusive locking as well. As previously
mentioned, exclusive locking limits the transactional data throughput, and therefore needs to be
avoided in SAP S/4HANA. In consequence, this parallel statistical moving average valuation is not
available in SAP S/4HANA, on-premise edition 1511. Deactivation of the statistical moving average is
not mandatory in SAP S/4HANA, but is nevertheless recommended in order to achieve a significant
increase of transactional data throughput for goods movements. It is important to note that the
deactivation is not reversible. 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", which offers a fixed price inventory valuation and 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 can be changed
by any business transaction, but transactional data throughput is still limited by exclusive
locking.
Simplification List for SAP S/4HANA 1610
124
In addition, the following database table fields are affected by the deactivation of the statistical
moving average:
In table MBEW, EBEW, OBEW, QBEW the fields SALKV and VERPR are not updated anymore
for materials with price control Standard. The same applies to the history tables MBEWH,
EBEWH, OBEWH and QBEWH.
In table CKMLCR the fields PVPRS and SALKV are not updated anymore for materials with
price control Standard.
In table MLCR the fields SALKV, SALKV_OLD and PVPRS_OLD are not updated anymore for
materials with price control Standard.
If Actual Costing is used, the above mentioned fields will still be updated with the periodic
unit price during the Actual Costing Closing Steps.
As a consequence of not updating the above-mentioned fields, the statistical moving average price
and the value based on the statistical moving average price are no longer available on the user
interface. This concerns the following transaction codes: MM01, MM02, MM03, CKM3 and MR21.
Business Process related information
As its name implies, the statistical moving average price is purely statistical and does not have any
impact on actual financials-relevant valuation.
Without the statistical moving average price, an alternative way of valuation needs to be used in few
scenarios. This concerns, for instance, Balance Sheet Valuation and Product Cost Planning, where
selection/valuation variants must be checked and adapted.
Required and Recommended Action(s)
If within custom code the fields mentioned above under 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. To identify such locations, it is
required to make use of the where-used functionality of transaction code SE11 and to consider other
techniques like transaction code CODE_SCANNER to find locations which SE11 cannot handle such as
dynamic programming or native SQL statements. Finally, the
report SAPRCKM_NO_EXCLUSIVELY_LOCKING 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.
2.1.10.5 Performance optimizations within Material Document Processing - lock behaviour
1. General
Simplification List for SAP S/4HANA 1610
125
With the introduction of the new MM-IM data model there are opportunities and drawbacks. The
opportunities will offer new process modes whereas the drawbacks require changes of the process
behavior. Both will have effects on follow-on processes or side processes.
2. Opportunities
2.1 Locks to protect stock
With the introduction of the new MM-IM data model in S/4HANA OP1511 there are no UPDATE
processes on the actual stock quantity fields in the material master and stock aggregate tables
anymore. Instead of the UPDATEs only INSERTs into the new material document table will be done.
Hence from a data base perspective there are no locks anymore on DB level. That enables - from a
DB perspective - parallel execution of material document processing. Anyway, from a business
perspective there are still logical locks required because
1. Consistency with material master data (i.e. prevent parallel change of master data
attributes). This can be ensured already with a shared logical lock because with such a lock a
change of material master is protected.
2. Defined sequence of material documents (e.g. for moving average price).
3. Consistency with stock quantity (check availability if negative stock is not allowed).
The consistency with master data and with stock quantity (1 + 3) is necessary in any case. The
defined sequence of material documents (2) is ensured only in the case that exclusive lock is chosen
in the customizing. Regarding the lock of materials to enable a consistent quantity check (lock reason
3) there are currently two different kinds of lock strategies: early exclusive quantity lock and late
exclusive quantity lock.
2.2 Early lock strategy
In the early exclusive lock strategy, all material master data and quantities are read in an array fetch
before the item processing (except for special stocks) and exclusive locks are set during the entire
processing of the material document. As this implies that valid quantities are read from the buffer,
this option has the best performance regarding process runtime, but on the other hand it has a worst
performance regarding process throughput in scenarios with many equal material items in parallel
processes.
2.3 Late lock strategy
In the late exclusive lock strategy, the material master data and quantities are read also in an array
fetch before the item processing but no exclusive locks are set. An exclusive lock will be set only for a
short period of time during the item processing for each specific item. This exclusive lock will be
converted into a shared lock after checks for stock underrun.
As the new MM-IM data model changes the old key figure model to an account model this enables a
more finer granular locking for the late quantity lock case starting with S/4HANA OP1610 and
CE1608. For the key figure model the locks have been set on material and plant level in S/4HANA
OP1511. With the account model the locks can be set on material, plant, storage location, stock
Simplification List for SAP S/4HANA 1610
126
identifier, special stock identifier level (in principle what defines the stock in the new model) starting
with S/4HANA OP1610 and CE1608. Hence, even in parallel processes the probability for a lock
collision is rather likely. Furthermore, by changing the sequence of sub-process steps under the hood
of the exclusive look in the late lock strategy the duration of this exclusive lock can be shortened.
With S/4HANA OP1610 and CE1608 a further option to increase throughput will be introduced. This
is the option to define in the customizing that, for the late lock strategy, no exclusive lock shall be
set. In this case only late shared locks will be set which really enables parallel material document
processing (stock underrun checks are still possible because in this case all processes communicate
their withdrawals to the lock server who in this case serves as second storage for stock changes (first
storage is the DB) and the calculation operates on data from the first and the second storage).
2.4. Locks on batches
Locks on batch materials will be set in the current process to protect parallel changes of the batch
master. In S/4HANA OP1511 those locks will be set without any conditions, means they will be set
even if the material document posting does not change any of the batch master data. Starting with
S/4HANA OP1610 and CE1608, to reduce the collision rate of parallel material document postings for
batch material line items those batch locks will be set only if the batch master data like production
date or best before date are entered during the MM-IM document processing and these data differ
from the data on the DB.
3. Overcome drawbacks
With the introduction of the new MM-IM data model for S/4HANA OP1511 the material stock
quantity data are not stored anymore as pre aggregated data in the old hybrid (containing material
master and material actual stock quantity data) or aggregate (containing only material actual stock
quantity data) tables. Instead the material stock quantity data will be calculated on-the-fly from the
material document table. For applications this is transparent because the calculation of stock data as
well as the determination of the material master data will be done via CDS-compatibility views which
are assigned as proxy objects to those tables with hybrid or aggregate character and each fetch to
the tables get redirected in the DBI layer to the assigned proxy view. According to the on-the-fly
calculation, read accesses to those hybrid and aggregate tables are much slower than in Suite on
HANA where the aggregated quantity changes have been stored in these tables as actual stock
quantity data.
During material document processing, material data is read from the database in general in an array
fetch at the beginning of the processing. A second access to the database to read material data will
be done in case of the late exclusive lock during the item processing. In both cases due to the
compatibility view the material master as well as the material stock quantity data will be read
whereas in the prefetch only the master data is required and during the late exclusive lock phase
only the material stock quantity data is required.
To turn the drawback of on-the-fly calculation into an advantage the following will be introdcued
with S/4HANA OP1610 and CE1608:
during the prefetch phase only the material master data will be read into internal buffers
by using the pure material master data views to retrieve the data from DB
Simplification List for SAP S/4HANA 1610
127
during the item processing the stock quantity data will be read in the account model from
the data base, and this will be done only in case of stock decreasing processes where
negative stocks are prohibited
Because it is known that HANA can process a single array fetch faster than many single fetches, the
stock quantity read and stock underrun check mentioned in the last bullet point can also be done
outside of the item processing. This array operation, which does also the lock operation, is executed
directly in the function module MB_CREATE_GOODS_MOVEMENT after the item processing therein
has been finished. The decision whether the read and check operations are done during or after item
processing is done at the beginning of the processing. The new BAdI BADI_NSDM_READ_STOCK can
be used by customers to overrule the decision.
This changes to turn the drawbacks have been done irrespective of the lock strategy. It is effective in
early as well as late lock strategy.
Hence for S/4HANA OP1610 and CE1608, the adaptation done for the late lock strategy allows
parallel execution of material document processes whereas the stock quantity read from DB and
stock underrun check reduces the processing time of a single material document process. Overall it
increases the performance of material document processing in S/4HANA OP1610 and
CE1608 compared to S/4HANA OP1511 and Suite on HANA.
4. Permission of negative stocks
It is possible to allow on plant level negative stocks. Also on storage location level negative stocks can
be permitted. And for the material itself a negative stock can be enabled. All this was possible to
configure already in S/4HANA OP1511 and also in Suite on HANA. If on all 3 level the permission on
negative stock has been granted then in S/4HANA OP1610 and CE1608
1. no locks at all will be set in the late lock strategy case.
2. no stock determination from the data base will be done and no stock underrun check will be
executed (in both lock strategies).
Hence for such a configuration and setting of material master data the runtime and the throughput
may increase further.
5. Business process related information
5.1 Modifications in the coding of Material Document Processing
As already described in the Overcome Drawback section, stock quantity data will be read and
calculated only for stock decreasing processes where negative stocks are prohibited. And this will be
done, if necessary, in the new account model. Hence, the actual stock quantity fields in the internal
tables XMabc tables used and routed internally are always zero and cannot be used for any
subsequent calculation incorporated in the material document processing. There is no option to
populate these actual stock quantity fields in the internal tables XMabc tables anymore! Thus,
customer coding modifications using stock quantity data from those XMabc internal tables must be
Simplification List for SAP S/4HANA 1610
128
adjusted. Stock change information is available
via it_stock_change = cl_nsdm_mmim_read_stock=>get_instance( )->get_stock_change_for_bte( ).
5.2 Logistics Information System (LIS)
LIS processing during any document processing means that document data will be prepared
(transformed) into LIS structures and those data will be finally written into so called LIS information
structures. Customers can enrich those data structures as well as define their own
information structures. LIS processing means that the document processing time gets enlarged,
increases significantly the memory footprint due to the LIS information structures and forces (at least
for MM-IM) a serialized processing in case of V1 mode. Data in those LIS information structures will
be used for special reporting by customers.
A forced serialization of MM-IM document processing due to active LIS and a customizing of late lock
strategy to enable parallel processing for MM-IM does not make sense at all. Furthermore several LIS
key figures like # of times a zero stock would be reached by a posting, cannot be determined reliable
in parallel processes. Hence, active LIS and late lock mode is defined now as an inconsistent system
state starting with S/4HANA OP1610 and CE1608!
Furthermode, because several fields in internal structures (exactly those stock quanitity fields of the
former key figure model like field LABST in the internal structure XMARD) are not populated with
data anymore with the active optimization, absolut stock quanities can not be send via the INVCON0x
IDOC (message type INVCON).
If an On-Premise system is configured for early lock strategy then LIS and the INVCON message type
can be used. In this case the processing will be internally switched into the legacy mode. That means
that none of the above described optimizations will be executed. This is necessary just because the
optimized coding does not fill the internal XMabc tables with stock data in the key figure model
anymore (just because in many cases stock data are not calculated at all) and the data in those
internal tables are required for LIS processing and the INVCON message type.
MM-IM development plans to provide step by step Virtual Data Model (VDM) views as successor for
LIS. The first VDM's released with S/4HANA OP1610 and CE1608 will be for stock quantity reporting.
Switching the lock strategies
The toggling between early lock and late lock strategy can be done via customizing transaction OMJI.
Marking the flag "Exclusive block" means early lock strategy whereas marking "Late exclusive block"
means late lock strategy. Toggling of these two lock modes is possible. The setting of "no exclusive
lock" for the late lock strategy has to be done by executing
program SAPRCKM_NO_EXCLUSIVELY_LOCKING. This change can not be undone. For this setting
please refer especially to note 2267835.
The strategy late lock/non-exclusive seems to be a good strategy if - by business means - it is ensured
that goods receipt postings are always be processed before goods issue or transfer postings are
done.
Simplification List for SAP S/4HANA 1610
129
LIS
LIS settings can be done by executing the customizing transaction OMO9. LIS update processing is
only possible for early lock strategy. For late lock strategies LIS has to be deactivated by setting "No
updating" for all LIS info structures (in transaction OMO9 do a double click on an info structure; the
Parameters dialog box appears and in this dialog mark "No updating"; do that for each info
structure). Toggling on/off of LIS is not that easy as for the lock strategies. Toggling LIS from off to on
requires the re-generation of the content of the LIS info structures.
Permission of negative stocks
At first the permission has to be granted on plant level. Go to SAP IMG --> Materials Management -->
Inventory Management and Physical Inventory --> Plant Parameters. Here you can grant negative
stocks on special stock types.
At second the permission has to be granted on storage location level. Go to SAP IMG (or use
customizing transaction OMJ1) --> Materials Management --> Inventory Management and Physical
Inventory --> Goods Issue / Transfer Postings --> Allow negative stocks. Here you can grant negative
stocks for storage locations in a plant assigned to a valuation area.
At third the permission has to be granted for the material itself. Execute material maintenance (e.g.
transaction MM02) and enter the tab "Plant data / stor. 2". Mark flag "Neg. stocks in plant"
Customer modifications
Real modification of SAP coding by customers in the area of function group MBWL or the MIGO main
program SAPMM07M and it includes using stock aggregate data from the internal tables XMabc must
be refactored. Implemented BAdI methods are not affected by this.
2.1.10.6 Material Valuation Data Model Simplification in S/4HANA 1610 and Higher
Description
If you upgrade from SAP S/4HANA 1511 to SAP S/4HANA 1610, the Material Ledger (ML)
functionalities will be changed for simplification. The impacts on the inventory valuation tables
xBEW(H) - tables: EBEW, EBEWH, MBEW, MBEWH, OBEW, OBEWH, QBEW, QBEWH - are described in
the following:
The transactional fields LBKUM, SALK3 and VKSAL will be retrieved from the Universal Journal Entry
Line Items table (ACDOCA) with on-the-fly aggregation. And the transactional field SALKV will be
retrieved from the Material Ledger table. 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 Universal
Journal Entry Line Items table and Material Ledger table. Hence all customer coding, reading data
Simplification List for SAP S/4HANA 1610
130
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. One impact of the simplified
MM-IM Inventory Valuation data model does exist if there are customer appends on the mentioned
tables. The NetWeaver redirect capability requires that the database table and the assigned proxy
view are compatible in the structure with respect to the number of fields and their type. Thus, if
there is an append on one of the above mentioned tables, the assigned DDL source of the CDS proxy
view must be made compatible. Another impact of the simplified inventory valuation data model is a
performance decrease of database read operations on the above mentioned tables. A data fetch on
one of the mentioned tables in S/4HANA is slower than in SAP ERP 6.0 due to JOIN operations and
on-the-fly aggregation. Hence performance-critical customer coding may need to be adjusted to
improve performance.
1. Customer appends on xBEW(H) tables
In order to identify append issues, you can execute method GET_S4_DEV_SYSTEM_RESULTS of class
CL_S4_CHECKS_MM_IM. Please focus only on the results of the xBEW(H)-tables.
If the check identifies appends on xBEW(H) tables, view extensions of the following CDS views need
to be created or adapted.
Table with customer
appends
DDL sources of CDS-views which needs to be enhanced
or replaced in case of customer appends
EBEW
-
MBV_EBEW
EBEWH
-
MBV_EBEWH
MBEW
-
MBV_MBEW
MBEWH
-
MBV_MBEWH
OBEW
-
MBV_OBEW
OBEWH
-
MBV_OBEWH
QBEW
-
MBV_QBEW
QBEWH
-
MBV_QBEWH
Table 1: Affected CDS views which needs to be enhanced or replaced in case of customer appends
If you upgrade from S/4HANA 1511 to S/4HANA 1610, you do not need the view extensions for the
views listed in table 2 anymore. These view extensions should be deleted.
Table with customer appends
DDL sources of CDS-views for which view extensions are not
needed anymore
Simplification List for SAP S/4HANA 1610
131
EBEW
-
MBV_EBEW_EXT
MBV_EBEW_ML_ONLY
MBV_EBEW_BASIS
MBV_EBEW_CASE
EBEWH
-
MBV_EBEWH_EXT
MBV_EBEWH_ASSOC
MBV_EBEWH_ML_ONLY
MBV_EBEWH_BASIS
MBV_EBEWH_CASE
MBEW
-
MBV_MBEW_EXT
MBV_MBEW_ML_ONLY
MBV_MBEW_BASIS
MBV_MBEW_CASE
MBV_MBEW_MOTH_SEG
MBEWH
-
MBV_MBEWH_EXT
MBV_MBEWH_ASSOC
MBV_MBEWH_ML_ONLY
MBV_MBEWH_BASIS
MBV_MBEWH_CASE
MBV_MBEWH_MOTH_SEG
OBEW
-
MBV_OBEW_EXT
MBV_OBEW_ML_ONLY
MBV_OBEW_BASIS
MBV_OBEW_CASE
OBEWH
-
MBV_OBEWH_EXT
MBV_OBEWH_ASSOC
MBV_OBEWH_ML_ONLY
MBV_OBEWH_BASIS
MBV_OBEWH_CASE
QBEW
-
MBV_QBEW_EXT
MBV_QBEW_ML_ONLY
MBV_QBEW_BASIS
MBV_QBEW_CASE
QBEWH
-
MBV_QBEWH_EXT
MBV_QBEWH_ASSOC
MBV_QBEWH_ML_ONLY
MBV_QBEWH_BASIS
MBV_QBEWH_CASE
Table 2: Affected CDS views for which view extensions are not needed anymore
1.1 Fields containing material master data attributes
If customer appends only contain material master data attributes, the views could be made
compatible by extension views. Extension views ensure that fields, defined in the extension view, are
appended at the end of the extended view. An extension view needs to be defined for the CDS-view,
listed in table 1, for the corresponding xBEW(H) table.
For more information about view extension see SAP NetWeaver 7.4 documentation
Simplification List for SAP S/4HANA 1610
132
1.2 Fields representing a customer defined quantity/value to be aggregated
If customer appends contain aggregated fields, the proxy view (same approach as described for
material master data attributes) and most probably also the views in the view-hierarchy needs to be
replaced by new CDS views in the customer namespace. This view must contain the same fields and
types as the corresponding xBEW(H) table. The newly created CDS view must be specified as a new
proxy view via transaction SE11 --> Menu --> Extras --> Proxy Object.
In most cases extension views cannot be used, since currently they do not support aggregate
expressions.
2. Code adjustments and optimizations
DB read operations on the xBEW(H) tables have a performance decrease, since transactional data is
retrieved from the Universal Journal Entry Line Items table and the Material Ledger via database
joins and aggregation. Consequently, reading transactional data should be avoided 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 transactional data is required, the SELECT <table> should be
replaced by using a data access method from class CL_MBV_SELECT_<table>. These classes
provide access methods for single (SINGLE_READ) as well as array (ARRAY_READ) read
operations.
If only material master data is required, the SELECT <table> should be replaced by SELECT on
view V_<table>_MD. Alternatively, corresponding material master data read methods
(READ_MASTER_DATA) in the class CL_MBV_SELECT_<table> can be used. Also the data type
declarations should be adjusted from TYPE <table> to TYPE V_<table>_MD.
If only transactional fields are required, the SELECT <table> could be replaced by using
the data access methods ARRAY_READ_TRANSACTIONAL_DATA and
SINGLE_READ_TRANSACTIONAL_DATA from class CL_MBV_SELECT_<table>.
For performance critical coding parts, these adjustments are strongly recommended. For non-critical
parts it is optional in the short term but recommended in the long term. 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. If there are issues with the where-used
functionality in the customer system, see SAP Note 28022. In the where-used dialog it is possible via
the button "Search Range" to search for specific key words like SELECT, INSERT and so on.
2.1.10.7 Goods movements without exclusive locking by material valuation
Description
One major innovation of SAP S/4HANA in the area of MM-IM is the significant increase of
transactional data throughput for high volume transactions, especially goods movements. To enable
Simplification List for SAP S/4HANA 1610
133
this from a technical point of view, it is necessary for the application logic to avoid exclusive locking
on the application layer.
Currently two different locking methods are available for goods movements:
The first method locks all affected materials exclusively on their plant level during the entire
document processing stage. This method offers the fastest document processing speed, since
only a few locks need to be set and all required material data only needs to be read once for
the whole process. The drawback of this method is a high lock collision probability for similar
parallel postings. Moreover, this effect worsens with document size since every additional
item extends the total exclusive locking duration and scope. This method is called Exclusive
block in Customizing.
The second method involves individual locking of material master and valuation data.
Reduced exclusive locking times are used to minimize the collision probability between
parallel postings. To achieve this, intended stock changes are communicated early in the
process via the central enqueue server. All similar postings need to read these numbers from
the enqueue server and take them into account along with the data read from the database.
The drawback of this method is increased effort resulting in a longer total runtime for each
document. This method is called Late block in Customizing.
With SAP S/4HANA, on-premise edition 1511, a new option to increase transactional data throughput
for materials with Standard price control was introduced (for anonymous stock only). This option
requires deactivation of the statistical moving average price and activation of Late block. With SAP
S/4HANA, on-premise edition 1610, this option also includes materials with Moving Average price
control and all special stock types. The benefit of this option is that exclusive locking is no longer
required for material valuation, which enables parallel material document processing. However,
exclusive locking is still required if material master data is created or changed by a goods
movement. Material master data is created by a goods movement if split valuation is used and a new
batch has to be created, for instance. Changes of material master data concerns especially materials
with Moving Average price control. When a goods movement changes the ratio between the stock
value (SALK3) and the valuated stock quantity (LBKUM), the moving average price must be adjusted
accordingly, which ultimately requires an exclusive lock until the V1 update. The quantity/value ratio
is mainly changed by goods movements with an external value (for example, from the purchase
order). However, if the change originates due to rounding differences only, the moving average price
is not adjusted. SAP for Oil & Gas currently does not benefit from the new option and the
recommendation is to use Exclusive block. In addition, exclusive locking is still required, if SAP Note
1704534 (Deactivation of delivery costs for ML update) has been implemented.
Business Process related information
The drawback of the new option described above is that temporary inconsistencies due to rounding
differences may occur:
Valuated stock quantity (LBKUM) = 0 and Stock Value (SALK3) <> 0
Valuated stock quantity (LBKUM) > 0 and Stock Value (SALK3) < 0
Valuated stock quantity (LBKUM) < 0 and Stock Value (SALK3) > 0
Simplification List for SAP S/4HANA 1610
134
In addition, the same inconsistencies can occur for value-only articles with VKSAL instead of LBKUM,
if SAP for Retail is used. These inconsistencies are temporary because they are usually corrected by
the next goods movement. Otherwise, transaction code MR23 (Adjustment of Inventory Value) is
available to correct inconsistent stock values. You can find more information about the Adjustment
of Inventory Value transaction in the SAP Help Portal.
Required and Recommended Action(s)
See SAP Note 2267835 for more information about the deactivation of statistical moving average
price, which is the prerequisite to increase transactional data throughput as described above.
2.1.10.8 CWM in S4HANA
CWM is not supported in SAP S/4HANA even though CWM objects are technically given in S4CORE
(QRT_STAG). If you have activated the Industry Solution IS-CWM, the following SAP S/4HANA
transition worklist item is applicable. Note, that two simplified features will no longer be supported
in SAP S/4HANA:
The 'old architecture' of Industry Solution IS-CWM that was part until SAP enhancement
package 3 for SAP ERP 6.0
The category type 'B' = Parallel Unit of Measure (BUoM is Valuation Unit of Measure)
Description
1. No further support of CWM business function /CWM/BF on SAP S/4HANA
When the CWM-solutio is ade a aila le i “AP “/ HANA, the old a hite tu e™ of the i dust
solution IS-CWM (SAP ERP 6.0) will not be supported on SAP S/4HANA anymore. The 'new
architecture' of IS-CWM was introduced in SAP enhancement package 4 for SAP ERP 6.0. This 'new
architecture' is harmonized with the SAP ERP standard and removes the dependencies to
components Inventory Accounting (FIN-BAC-INV) and Logistics Inventory Management Engine (LIME).
With SAP enhancement package 5 for SAP ERP 6.0, SAP provides migration tools (see note 1450225 SAP CWM: Data Migration from Old to New Architecture and its attachments). Please be aware that
this migration is a project that requires preparation. SAP strongly recommends to contact the CWM
Solution Management before! Check if the business functions /CWM/BF or /CWM/CM_1 are active
in any client. Use the transaction SFW_BROWSER and expand the subtree for business function set
/CWM/BFS. If the business function /CWM/BF is active and you intend to move to SAP S/4HANA you
ha e to do a ig atio to s it h to the e a hite tu e™ of CWM o “AP E‘P . . In case business
function /CWM/CM_1 is active you are using the new architecture and no further action is needed.
2. Category of Parallel Unit of Measure
In ECC 6.0 IS-CWM supported two categories of parallel unit of measure (PUoM). These are
maintained in the material master, choosing the additional data tab Unit of measure. The category B
Simplification List for SAP S/4HANA 1610
135
(Parallel Unit of Measure (BUoM is Valuation Unit of Measure)) will not be supported in SAP
S/4HANA. CWM does not support the unit of measure category 'B' because of the following reasons:
For CWM it is unnecessary to store quantities in a second unit of measure, such as category
'B', without any depending functionality.
In SAP S/4HANA the category 'B' is reserved for Extended Warehaouse Management (EWM).
For EWM the category 'B' will control the usage of a PUoM only for the EWM solution in
S4CORE.
You can check whether you use category 'B' with transaction SE16. Enter table 'MARM' and make
sure that field /CWM/TY2TQ is on the selection screen. If done select entry 'B' for this field and
execute. In case you get the message 'No table entries found for specified key' no further steps are
required. If you find any materials please refer to note 2358909 for further information.
2.1.11 Logistics – PLM
2.1.11.1 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, customers can use SAP Engineering Control Center for SAP S/4HANA, onpremise edition.
For more information see SAP Note: 2234028
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
EDESK_CUS, EDESK_IPPE
Required and Recommended Action(s)
Customers can move to SAP Engineering Control Center for SAP S/4HANA.
Custom Code related information
Simplification List for SAP S/4HANA 1610
136
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.
2.1.11.2 DMS - 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 1511.
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
STEP10, STEP20
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: 2216258
2.1.11.3 DMS Documents@WEB
Description
With SAP S/4HANA, on-premise edition 1511 Documents@web is not available.
Documents @ Web transactions like CVW* are not available in SAP S/4HANA, on-premise edition
1511. This is obsolete now and PLM WUI can be used for the same
Business Process related information
Use PLM WUI.
Simplification List for SAP S/4HANA 1610
137
Transaction not available in SAP S/4HANA
CVW*
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: 2217857
2.1.11.4 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
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
Simplification List for SAP S/4HANA 1610
138
Custom Code related information
SAP Notes: 2210904 , 2214906
2.1.11.5 Classification
Description
With SAP S/4HANA, on-premise edition 1511 transactions of the Classification are 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
Transaction not available in SAP S/4HANA
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.
CL20
Assign Object to Classes
CL22
Allocate Class to Classes
CL24
Assign Objects to One Class
CL6E
Copy DIN Standard
CL6F
Copy DIN Characteristic Data
CL6G Create Material w. DIN Char. Data
CL6R
Direct Input for Classes
CLB1
Batch Input for Classification
CLB2
Direct Input for Classification
CLB3
Display Classification File
GENC Generate Source Code
O005 C CL Characteristic Default Settings
O021 Class Data Transfer
O023 Display Class Maintenance Data File
O024 Transfer Class Data: Direct Input
S_ABA_72000139
S_ABA_72000140
S_ALR_87003718
IMG Activity: SIMG_CFMENUO000O1CL
S_ALR_87003725
IMG Activity: SIMG_CFMENUO000O008
Simplification List for SAP S/4HANA 1610
139
S_ALR_87003732
IMG Activity: SIMG_CFMENUO000O016
S_ALR_87003741
IMG Activity: SIMG_CFMENUO000O002
S_ALR_87003752
IMG Activity:
SIMG_CFMENUO000SMOD
S_ALR_87003765
IMG Activity: SIMG_CFMENUO000MERK
S_ALR_87003777
IMG Activity: SIMG_CFMENUO000KLAS
S_ALR_87003789
IMG Activity: SIMG_CFMENUO0002239
S_ALR_87003802
IMG Activity: SIMG_CFMENUO000O12A
S_ALR_87003812
IMG Activity: SIMG_CFMENUO000O003
S_ALR_87003831
IMG Activity: SIMG_CFMENUO000O005
S_ALR_87003842
IMG Activity: SIMG_CFMENUO000O004
S_ALR_87003852
IMG Activity: SIMG_CFMENUO000O017
S_ALR_87003863
IMG Activity: SIMG_CFMENUO000O006
S_ALR_87009587
S_AX6_42000002
IMG Activity: BWCLBW_CTBW
S_S6B_86000002
IMG Activity: CTWUL_LOCDEP
S_S6B_86000003
IMG Activity: CTWUL_LOCDEP
S_S6B_86000004
S_S6B_86000005
S_S6B_86000006
CLNA Namespace f. Classes/Characteristics
CT01
Create Characteristic
CT02
Change Characteristic
CT03
Display Characteristic
CT05
Create Characteristic
CT06
Display Characteristic
CT11 Use CT12 instead
CT21 Batch Input for Characteristics
CT22 Maint. Seq. File for Characteristics
CT23 Display Chars for Change Number
CT24 Display Change Numbers Used
CT25 Where-Used List of Chars in Deps
CTCP Copy C tables for characteristics
S_ABA_72000141
CL2A Classification Status
CL6B
Object List
CL6D Classes Without Superior Class
CL6M Delete Class (with Assignments)
CL6O Plus-Minus Object Display
CL2B
Class Types
CL6A Class List
CL6Q Where-Used List for Classes
Simplification List for SAP S/4HANA 1610
140
CL6T
Copy Text for Classes
CLCP
Copy Classification C Tables
S_ALR_87009588
.
S_ALR_87011758
.
CL21
Display Object in Classes
CL23
Display Class for Classes
CL25
Display Objects in Class
CL26
Mass Release of Assignments
CL30
Find Objects in Classes
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 2213569.
Related SAP Notes
Custom Code related information
SAP Note: 2213569
2.1.11.6 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 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
PPECS
Required and Recommended Action(s)
Customers using this functionality should evaluate if Product Structure Management and Product
Structure Synchronization fit their needs.
Simplification List for SAP S/4HANA 1610
141
Related SAP Notes
Custom Code related information
SAP Note: 2226275
2.1.11.7 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.
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: 2215061, 2215123
SAP PLM Recipe Development
Description
Fast Entry screen and Compliance with Expert server not supported on S/4 HANA
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.
Simplification List for SAP S/4HANA 1610
142
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: 2212999
How to Determine Relevancy
Compliance Check with the Expert Server is used if entries exist in DB Table EHSBC_RC_PARA
(check with SE16)
2.1.11.8 Engineering Change Management ECR/ECO
Description
The Engineering Change Record / Engineering Change Order functionality is no more available with
SAP S/4HANA. With SAP S/4HANA 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
Simplification List for SAP S/4HANA 1610
143
Required and Recommended Action(s)
Existing and running Change Requests and Change Orders should be finished before system upgrade
is facilitated as working with these type of object will not be possible in S/4HANA. Additional settings
will be required in the system for the Customer to use the Engineering Record. Set up Engineering
Record (ER Types, status network, BRF+) and Process Route (Activities, services, process route
templates, BRF+) for tracking, approving and facilitating business object related changes.
How to Determine Relevancy
The Engineering Change Request / Engineering Change Order functionality is used if entries
exist in DB Table AENR where the CCART field is fileld (check with SE16)
Use ST03N (on the production system, if possible) to check transaction profile of the
complete last month, whether the following transactions have been used: CC31, CC32, CC33,
CC62, OS72, OS73
2.1.11.9 Enterprise Search in SAP Product Lifecycle Management (SAP PLM)
Description
PLM Enterprise Search models will not work after an upgrade to S/4HANA. With SAP S/4HANA, onpremise edition 1511 the Enterprise Search models are now replication free search models (using
HANA DB tables instead) within SAP Product Lifecycle Management (SAP PLM).
Business Process related information
With the new solution the following searches are not available in SAP S/4HANA:
Document search with linked documents
Document search with attached document content
Synchronization BOM to BOM search with assigned MBOMs
Synchronization PSM to BOM search with source PSM Structure and target MBOMs
MBOM, Recipe and PSM search with assigned classification data
MBOM, Recipe and PSM search with assigned document data
Specification and PSM search with status data
Label search with recipe data origin
Recipe search with formula item quantity
Search for any object with IDs without leading zeroes
Required and Recommended Action(s)
Customizing and Custom Code related information
SAP Note: 2217234
Simplification List for SAP S/4HANA 1610
144
How to Determine Relevancy
1. Navigate to the PLM Search customizing: Product Lifecycle Management (PLM) -> PLM Web
User Interface -> PLM Web Applications -> PLM Search -> Define Settings for PLM Search
2. Check if any of the following columns contains entries referring to a custom search model or
a class that resides in the customer namespace:
1. Object Type of Service
2. Result Class Name
3. Key Conv. Class Name
4. Configuration ID
2.1.11.10 Engineering Change Management Change Sequence Graph
Description
Transactions related to Change Sequence Graph are not available in SAP S/4HANA anymore.
With SAP S/4HANA the current Change Sequence Graph functionality within SAP Product Lifecycle
Management (SAP PLM) is not available anymore.
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
How to Determine Relevancy
Change Sequence Graph is used if entries exist in DB Tables ENODE or EDGE (check with
SE16)
2.1.11.11 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 (Functionality available in SAP S/4HANA onSimplification List for SAP S/4HANA 1610
145
premise edition 1511 delivery but not considered as future technology. Functional equivalent is
available).
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.
2.1.11.12 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.
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: 2226803
Simplification List for SAP S/4HANA 1610
146
2.1.11.13 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
OPPE07
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
2.1.11.14 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
(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is not available yet).
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
Simplification List for SAP S/4HANA 1610
147
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 (see attachments)
Controlling cockpit for "Collaboration Projects" (see attachments)
(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
2.1.11.15 Routing Component Assignment
Description
With SAP S/4HANA, on-premise edition 1511 the current Routing Component Assignment (RCA) in
Guided Structure Synchronization is not available. As Visual Enterprise Manufacturing Planner would
be the successor for RCA.
Business Process related information
Following features shall be accomplished using VEMP
Creation of MBOM from EBOM via Routing
Component Allocation from MBOM to Routing
Required and Recommended Action(s)
Switch Component Allocation Process from RCA to VEMP or Routing UI
Related SAP Notes
Custom Code related information
SAP Note: 2216303
2.1.11.16 Release Management Framework
Description
Simplification List for SAP S/4HANA 1610
148
With SAP S/4HANA, on-premise edition 1511 the current Release Management Framework
functionality within SAP Product Lifecycle Management (SAP PLM) is not available anymore. It is
recommended for new customers to have a look at the Engineering Record and check if the
functionality there covers your requirements.
Business Process related information
Managing Releases with the Release Management Framework will not be possible any longer.
Transaction not available in SAP S/4HANA
on-premise edition 1511
RLMFW_CUST, RLMFW_NUM, RLMFW_OOCU
Required and Recommended Action(s)
It is recommended for new customers to have a look at the Engineering Record and check if the
functionality there covers your requirements.
Related SAP Notes
Custom Code related information
SAP Note: 2226357
2.1.11.17 Engineering Record
Description
The PLM Web UI Engineering Record (ER) will be renovated. Customers can still continue to use the
existing functionalities of Engineering Record (ER) within SAP S/4HANA, on-premise edition
1511. Moreover, the renovated Engineering Record (ER) will be available in the future.
Business Process related information
Customers can still continue to use the existing functionalities of Engineering Record (ER) within SAP
S/4HANA, on-premise edition 1511.The the renovated Engineering Record (ER) will be available in
the future.
2.1.11.18 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
Simplification List for SAP S/4HANA 1610
149
Product Assembly is not available in SAP S/4HANA, on-premise edition 1511. If customers would like
to activate it, they need to follow the steps described in SAP note: 2217112. 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
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: 2217112
2.1.11.19 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
Simplification List for SAP S/4HANA 1610
150
Priority definition for nodes
Variant differentiation
Transaction not available in SAP S/4HANA
PDN
Required and Recommended Action(s)
Customers shall move to Product Structure for SAP S/4HANA, on-premise edition 1511.
Related SAP Notes
Custom Code related information
SAP Note: 2226431
2.1.11.20 Access Control Management (ACM)
Description
The PLM specific Access Control Management will be deactivated in the SAP S/4HANA 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: 2212593
Business Process related information
Hiding the ACM for SAP S/4HANA 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:
2212593. 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 2212593
How to Determine Relevancy
This Simplification Item is relevant if:
Simplification List for SAP S/4HANA 1610
151
ACM objects are linked to Business Objects, thus entries exist in DB Table
/PLMB/AUTH_OBSID (check with SE16)
ACM is used if entries exist in DB Table HRP7600 where Otype=CC, as these entries contain
ACM type objects (check with SE16)
2.1.11.21 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.
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 CFI01 Importing Documents
S/4HANA on-premise edition
CFE01 Exporting Documents
1511
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: 2224778
2.1.11.22 cDesk
Description
The CAD Integration in SAP PLM (cDesk) is not available in SAP S/4HANA. As an alternative customers
can use SAP Engineering Control Center for SAP S/4HANA. For more information see SAP Note:
2234028
Simplification List for SAP S/4HANA 1610
152
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. Customers might use alternative solution SAP Engineering
Control Center. Process for CAD-Data Management (derive BOM, store drawings,
generation/consumption of viewable) cannot be implemented.
in SAP S/4HANA on-premise CDESK, CDESK_CUS, CDESK_DEL_DBTRACE, CDESK_READ_DBTRACE,
edition 1511
CDESK_SAVE_DBTRACE
Required and Recommended Action(s)
Customers can move to SAP Engineering Control Center for SAP S/4HANA.
2.1.11.23 Recipe Management
Description
SAP PLM Recipe Management (RM) is not available in SAP S/4HANA. This also affects PLM RM subfunctions 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 is supported, so the recipes are available and can be displayed after the system
conversion to SAP S/4HANA. 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. The functional equivalent is
SAP PLM Recipe Development (RD). 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
RMWB
BD_GEN_GRCP
BD_GEN_SRCP
FRML02
FRML03
FRML04
MRTRS_START
MRTRSC01
MRTRSC02
RMSL02
Start Workbench
General Recipe Distribution
Replicate Site Recipe
Edit Recipe Formula
Display Recipe Formula
Formula Information System
Start MR Transformation
RFC Destination of GR
Master Recipe Generation
Change Label Set
Simplification List for SAP S/4HANA 1610
153
RMSL03
Display Label Set
RMSTAT
Mass Status Change
Customizing Transaction not ORCP*, RCP*, RMS*, RMX*
available in SAP S/4HANA onpremise edition 1511
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. 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
Custom Code related
information
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
o /PLMI/RCP_MIGRATION
Recipe Migration
o /PLMI/RMSL_MIGRATION
Migration of Label Sets
SAP Note: 2222345
How to Determine Relevancy
The PLM Recipe Management is used if entries exist in DB Table RMSAT_HDR or
RMXTT_TRIAL_HD (check with SE16)
Use ST03N (on the production system, if possible) to check transaction profile of the
complete last month, whether the following transactions have been used: RMWB, FRML02,
FRML03, FRML04, RMSL02, RMSL03
2.1.11.24 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
Simplification List for SAP S/4HANA 1610
154
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.
2.1.11.25 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
EASYDMS_CUS
Required and Recommended Action(s)
Switch to DMS and Mobile Doc integration which is more powerful.
Related SAP Notes
Custom Code related
information
Custom plugin developed (in VC++) for Easy DMS solution has no
influence as the application usage is stopped at log-in level.
Simplification List for SAP S/4HANA 1610
155
2.1.11.26
SAP PLM Recipe Development
Fast Entry screen and Compliance with Expert server not supported on S/4 HANA
Description
With SAP S/4HANA, on-premise edition 1511 following functional changes were done:
1)
2)
Maintenance a specification using the Fast Entry Screen is not available. A successor is
planned.
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
How to Determine Relevancy
Compliance Check with the Expert Server is used if entries exist in DB Table EHSBC_RC_PARA
(check with SE16)
2.1.12 Logistics – PP
2.1.12.1 ERP Line-Balancing and Sequencing
Description
Sequence planning determines the production sequence of planned orders on assembly lines
operating at a constant rate or takt. It is part of repetitive manufacturing and only suitable for
repetitive manufacturing planned orders. SAP recommends to perform sequencing planning for
assembly lines with PPDS. Sequencing in PPDS is superior to sequencing in ERP for the following
reasons:
PPDS sequencing in the short term horizon works together with PPDS model-mix planning for
the mid-term horizon
You can define restrictions like "Minimum distance restrictions between two units with
a certain characteristic" or "At most x units per day with a certain characteristic"
Simplification List for SAP S/4HANA 1610
156
PPDS optimizers can compute production sequences that minimize violations of restrictions
The classic sequence planning transactions are still available but will be replaced in a future S/4HANA
release by a PPDS based solution (Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is available).
Business Process related information
Please refer to PPDS Model mix planning in help.SAP.com to get an idea of PPDS sequence planning.
Required and Recommended Action(s)
The classic sequence planning transactions are still available but will be replaced in a future SAP
S/4HANA release by a PPDS based solution. No immediate action is required but we recommend
making yourself familiar with PPDS model mix planning.
Related SAP Notes
Custom Code related
information
Sequence planning in PPDS is an all-new implementation.
Any enhancements or modifications of ERP sequence planning will not
work if PPDS sequence planning is used.
2.1.12.2 MRP in HANA
Description
Production planners have to make sure material is available when needed. MRP assists production
planners with this task. The MRP run determines expected material shortages and creates planned
orders, purchase requisitions, or delivery schedule lines to cover the expected material shortages. A
shortage exists for a material if the material is subject to demand-driven planning and if the total
quantity of material requirements (sales orders, stock transfer requirements, production
requirements, and forecast requirements) up to a certain point in time exceeds the total quantity of
material receipts (inventory, production orders, purchase orders, delivery schedule lines, firmed
planned orders, and firmed purchase requisitions).
SAP S/4HANA features MRP Live; an MRP run optimized for SAP HANA. MRP Live reads material
receipts and requirements, calculates shortages, and creates planned orders and purchase
requisitions all in one database procedure. This minimizes the volume of data that has to be copied
from the database server to the application server and back, which considerably improves
performance. MRP Live has some additional advantages including the following, for example:
The definition of the planning scope is more flexible. MRP Live allows you to plan a set of
materials with all components, materials for which a certain production planner is
responsible, or one material across all plants.
Simplification List for SAP S/4HANA 1610
157
If a material is transferred from one plant to another then the stock-transfer requirement is
not known in the supplying plant until after the material has been planned in the receiving
plant. MRP Live determines the sequence in which materials have to be planned across
several plants.
MRP Live is a prerequisite for the future production planning and detailed scheduling PP/DS
solution in SAP S/4HANA.
Classic MRP is still available as an interim solution(Functionality available in SAP S/4HANA on-premise
edition 1511 delivery but not considered as future technology. Functional equivalent is available),
which at the moment has to be used for creating MRP lists.
Business Process related information
MRP live differs from classic MRP in the following aspects:
MRP live does not write MRP lists.
Multi-level, make-to-order planning (transaction MD50) is not optimized for HANA.
Individual project planning (transaction MD51) is not optimized for HANA.
The creation indicator for purchase requisitions is not available in MRP Live. MRP Live always
creates purchase requisitions if the material is procured externally.
The creation indicator for delivery schedule lines is not available in MRP Live. MRP Live
always creates delivery schedule lines if a valid delivery schedule exists.
MRP Lists
MRP lists were intended for checking the MRP result. MRP lists were used to find materials with
issues quickly. MRP lists are snapshots of the material supply and demand situation at the time of
the last MRP run. The snapshot is often outdated. With HANA, stock/requirements lists can be read
with high speed. The MRP apps determine materials with issues in real-time. In SAP S/4HANA there is
no need for outdated MRP lists.
Planning of individual make-to-order sales orders and projects
Multi-level, make-to-order planning was a performance measure only. Rather than planning all
planning segments, the system only planned a selected planning segment. Thanks to the speed of
HANA, it is no longer required to support this performance measure. This also makes the MRP run
simpler.
Creation indicators
Classic MRP has a complicated set of rules for instructing the MRP run to create either purchase
requisitions or planned orders for externally procured materials. A similar set of rules instructs classic
MRP to create delivery schedule lines, purchase requisitions, or planned orders for externally
procured materials with valid delivery schedules. Creation indicators are defined in MRP groups, on
the initial screen of the MRP run, and default values are defined in the code. This is a complex logic
Simplification List for SAP S/4HANA 1610
158
with very limited business value. Planned orders for external procurement have to be converted into
purchase requisitions eventually. Creating planned orders first and converting them into purchase
requisitions is an unnecessary process step. Creation indicators were originally intended to separate
the responsibilities of production planners and purchasers. Production planners were responsible for
planned orders and purchasers were responsible for purchase requisitions. Today the roles of
production planners and purchasers have changed. Purchasers very often focus on negotiating
contracts with suppliers while the operative creation of purchase requisitions and purchase order
handling is left to material planners and MRP. Therefore MRP live always creates delivery schedule
lines for externally procured material with valid delivery schedules and it creates purchase
requisitions for all other externally procured material. The sourcing BAdi PPH_MRP_SOURCING_BADI
=> SOS_DET_ADJUST allows you to change the MRP element type of a material receipt to be created
by MRP. Implement this BAdi if you want MRP live to create planned orders rather than purchase
requisitions for externally procured materials.
Required and Recommended Action(s)
Classic MRP is still available in the SAP S/4HANA on-premise edition 1511. You can start using MRP
live rather than the classic MRP at any time. Therefore, there is no need to become active on the
start release. Before you start using MRP live, check the following:
Re-implement BAdI implementations and extensions of the classic MRP as AMDP BAdIs.
Make yourself familiar with the MRP apps and check whether they can be used as a
successor to MRP lists if you used MRP lists in the past.
Related SAP Notes
Conversio No
n PreChecks
Custom MRP Live is implemented in SQLScript running on the database server as opposed to
Code
classic ABAP code, which is performed on the application server. Any enhancement or
related
BAdI implementation of the classic MRP run does not work with MRP Live. A new set of
informatio AMDP BADIs will be available for MRP Live from SAP S/4HANA on-premise edition 1603.
BAdI implementations of the classic MRP have to be translated into AMDP BAdI
n
implementations if still required. This affects the following BAdIs:
Purpose
Classic BAdI or
extension
AMDP BAdI
Subcontracti
PPH_MRP_RUN_BADI =>
MD_SUBCONT_LOGIC
ng logic
MDPS_ADJUST
Comment
See
simplification
item
2.1.11.1PP-MRP
- Subcontracting
Reading
material
MD_CHANGE_MRP_DA PPH_MRP_RUN_BADI =>
receipts and TA
MDPS_ADJUST
requirements
Simplification List for SAP S/4HANA 1610
159
Scheduling of
stock transfer MD_STOCK_TRANSFER
requirements
User-defined
MRP
MD_ADD_ELEMENTS
elements in
MRP
Planned
independent
MD_PIR_FLEX_CONS
requirement
consumption
Change
planning
parameters
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
PPH_MRP_LOTSIZING_BADI =>
MD_MRP_PARAMETER LOT_SIZE_CALC
PPH_MRP_NETTING_BADI =>
S
NET_REQ_CALC
Change MRP
MD_MRP_LIST
list
Change
purchase
requisitions
created by
MRP
Change
planned
orders
created by
MRP
MRP lists are
not available by
MRP Live
PPH_MRP_RUN_BADI =>
MD_PURREQ_CHANGE,
PURREQ_BEFORE_UPDATE_ADJU
MD_PURREQ_POST
ST
PPH_MRP_RUN_BADI =>
MD_PLDORD_CHANGE,
PLANORD_BEFORE_UPDATE_ADJ
MD_PLDORD_POST
UST
Source of
MD_MODIFY_SOURCE,
supply
PPH_MRP_SOURCING_BADI =>
MD_MODIFY_PRODVER
determinatio
SOS_DET_ADJUST
S
n in MRP
See
simplification
item
2.1.11.7Simplifi
ed Sourcing
Package size
MD_MRP_RUN_PARALL MRP_DISPATCHER_BADI =>
for parallel
EL
DISPATCH_CREATE_TASK
processing
Material
PPH_MRP_NETTING_BADI =>
selection for Extension M61X0001 AT_PLANNING_FILE_ENTRIES_RE
MRP run
AD
Simplification List for SAP S/4HANA 1610
160
2.1.12.3 Planning File
Description
Context
MRP calculations are complex and therefore an MRP run can be lengthy. An important means to
improve MRP performance is net change planning. An MRP running in net change planning mode
only plans materials that have experienced a relevant change since the previous MRP run. A material
has to be planned by the next MRP if the material was received or issued, if a material requirement
like, for example, a sales order was changed, or if master data like the BOM or the product master
was changed. The planning file stores the materials that have to be planned by the next MRP.
Description
The new planning file does not have columns for low level code and record type. This information
does not have to be copied from the material master into the planning file when updating the
planning file. The MRP planning run reads the low level code of all materials requiring planning from
the material master.
Reason
In SAP S/4HANA the planning file was optimized for simplified update logic, consistency and for
update performance.
Business Process related information
In the classic Business Suite, reports RMMDVM10 and RMMDVM20 made a first setup of planning
file entries and checked planning file consistency for operative planning. In SAP S/4HANA, run report
PPH_SETUP_MRPRECORDS instead. For long-term planning, the reports RMMDVL10 and RMMDVL20
are replaced by the report PPH_SETUP_MRPRECORDS_SIMU. SAP S/4HANA, on-premise edition 1511
no longer supports net change planning in the planning horizon (processing key NETPL). MRP always
determines material shortages for all known material requirements. MRP can no longer cover only
the material shortages inside a limited planning horizon. This is valid both for the classic MRP and
MRP Live. For details refer to simplification item Planning Horizon.
Transaction not
available in SAP
S/4HANA on-premise
edition 1511
MDAB, MDRE (batch versions of above reports for operative planning file
entries replaced by PPH_MDAB)
MSAB, MSAC (batch version of above reports for long-term planning.
Planning file entries replaced by PPH_MSAB and PPH_MSAC).
Reports (not available RMDBVM00, RMDBVM10 (for conversion MDVM/MDVL into DBVM/DBVL
in SAP S/4HANA)
and back),
RMMDVM10, RMMDVM20 (creation and consistency check for
MDVM/DBVM), RMMDVL10, RMMDVL20 (creation and deletion for
MDVL/DBVL).
Simplification List for SAP S/4HANA 1610
161
Required and Recommended Action(s)
No actions are required on start release. After the system conversion, you should run report
PPH_SETUP_MRPRECORDS to populate the new planning file table with operative MRP records (PPMRP) and the report PPH_SETUP_MRPRECORDS_SIMU for simulative MRP records (PP-MP-LTP).
Related SAP Notes
Conversion Pre-Checks
Custom Code related
information
The original planning files MDVM/MDVL and DBVM/DBVL no longer
exist. They were replaced by the new planning file PPH_DBVM.
If your custom code creates planning file entries directly by updating or
inserting into tables MDVM, MDVL, DBVM, or DBVL, then you have to
adapt the custom code and call function module DISPSATZ_ERSTELLEN
instead. If your custom code only reads from the tables DBVM or DBVL,
no adaption is necessary. Queries from table DBVM or DBVL will be
redirected to the new planning file PPH_DBVM by compatibility views.
See note 2227059
2.1.12.4 Total Dependent Requirements
Description
Context
MRP runtime depends among many other factors on the number of material receipts and
requirements that have to be read to compute a material's shortages. Materials, which are
component of very many BOMs, can have many thousands of dependent requirements. Total
dependent requirements reduced the number of dependent requirements, which had to be read by
MRP at the expense of possible locking conflicts when updating the total dependent requirements.
Description of Simplification
HANA is very good at summing up many rows in a table. There is no need to compute and write
totals every time a single record is changed. Neither MRP Live nor the classic MRP support total
dependent requirements in SAP S/4HANA.
Reason
BOM explosion creates dependent requirements for all component materials needed to manufacture
a material. Total dependent requirements create locking problems if the same component material is
used in the BOM of different materials. MRP live creates very many planned orders in parallel.
Locking conflicts would impair parallel processing and total MRP runtime.
Business Process related information
Simplification List for SAP S/4HANA 1610
162
Business processes are not changed. MRP reads individual dependent requirements rather than total
dependent requirements.
Required and Recommended Action(s)
Follow the instructions for "Clean up Total Requirements" in the SAP help portal (Link)
Related SAP Notes
Custom Code related information
Custom code reading one of the tables RQIT, RQHD, or MDRI will
no longer work. Read table RESB instead.
See SAP Note 2229126
2.1.12.5 Forecast Based Planning
Description
In forecast based planning (MRP type VV) the MRP creates planned orders or purchase requisitions if
total forecast demand up to a certain point of time exceeds the total firmed receipt quantity up to
the same point of time. The total firmed receipt quantity includes inventory, production orders,
purchase orders, firmed planned orders, and firmed purchase requisitions. Forecast based planning is
a simple planning procedure, which does not require managing planned independent requirements.
For Forecast based planning the following things need to be considered:
MRP live does not perform forecast based planning in HANA but sends the affected materials
into the classic ABAP planning procedure. This results in a performance loss.
Forecast demand and planned independent requirements are semantically very similar. SAP
S/4HANA tries to avoid redundant functionality.
The Fiori-UI for planned independent requirements does not differentiate between forecast and
planned independent requirements. A statistical forecast is just one of several possible data sources
and the result is always planned independent requirements. SAP will not build separate Fiori-UIs for
forecast demand.
Business Process related information
In the long run forecast based planning should be replaced by MRP type planning. Proceed as
follows:
Step 1: Convert forecast requirements into planned independent requirements (PIR)
Step 2: Change MRP type VV to one of the MRP types PD, P1, P2, P3, or P4
Required and Recommended Action(s)
No mandatory action
Simplification List for SAP S/4HANA 1610
163
2.1.12.6 Demand Forecasting
Description
Demand forecasting estimates future material demand based on historic material consumption data.
The material demand forecast can be copied into planned independent requirements or it can be
used to compute safety stocks and reorder points. Classic demand forecasting copies the
consumption history into an ABAP application server, performs the forecasting algorithm in ABAP
and writes the result back into the database. Copying data between database server and ABAP
application server takes time. HANA has a built in library of forecasting algorithms, which could be
utilized for forecasting material demand. A future demand forecasting solution will probably perform
the forecasting algorithm in HANA utilizing HANA's forecasting library. Transactions MP30, MP31,
MP32, MP33, MP38, and MP39 are still available in SAP S/4HANA on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is not available yet). Currently there is no functional
equivalent available within SAP S/4HANA, on-premise edition 1511.
Business Process related information
Business processes will not change if the forecasting algorithm is changed.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related
information
Custom code or BAdi-implementations in material demand forecasting will
not be called when demand forecasting is performed in HANA.
2.1.12.7 Release status for different RFC function modules revoked
Description
RFC function modules use dictionary structures to type exporting or importing parameters. Some of
the fields in the dictionary structures have been extended (for example the material ID fields, which
are usually named "MATERIAL" and typed with domain "MATNR). It was not possible to keep the
short version of these fields and add an additional longer version as the same dictionary structures
are also used in very many internal interfaces. Therefore the released status of the following RFC
function modules was revoked.
Function Module
COCF_SN_CREATE_EAM
COCF_SN_CREATE_PP
Structure
RIQS5
RIQS5
Affected fields
BAUTL, MATNR, EMATNR, RM_MATNR
BAUTL, MATNR, EMATNR, RM_MATNR
Simplification List for SAP S/4HANA 1610
164
COCF_SN_GET_LIST_EAM
COCF_SN_GET_LIST_PP
COCF_S_SN_LIST_FLAT
COCF_S_SN_LIST_FLAT
MATNR, EMATNR, RM_MATNR
MATNR, EMATNR, RM_MATNR
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Check custom code
How to Determine Relevancy
If you call the above mentioned RFC function modules from within custom code and if you do not use
data elements typed with domain "MATNR" then you have to adjust the data types used in the
custom code. See note 2199837
2.1.12.8 Computer Aided Processing Planning (CAP)
Description
Standard value calculation with "Computer Aided Process Planning" CAPP was intended to determine
the processing durations for production operations. Standard values can be determined in several
ways:
Time studies
Estimating
Polling
Sampling and statistical procedures for determining times (for example, period time sheets)
Calculation methods (for example, MTM, WF and planned times)
Standard value calculation with CAPP allows you to define formulas, with which durations can be
computed based on product properties. CAPP is not available in SAP S/4HANA.
Business Process related information
Consider alternative approaches to determine standard values. SAP S/4HANA, on-premise edition
1511 will feature reports for comparing planned and actual processing durations. This can be used to
implement feedback control processes to manage standard values.
Transaction not available in SAP S/4HANA
on-premise edition 1511
CE11. CE12, CE13, CE21, CE22, CE23, CE31, CE32, CE33,
CE41
Simplification List for SAP S/4HANA 1610
165
Required and Recommended Action(s)
If you used CAPP you should consider alternative approaches and tools to determine standard values.
2.1.12.9 ABAP-List-Based PI-Sheets
Description
Starting with R/3 4.6 C formerly used ABAP list-based process instruction sheets have been replaced
by browser-based PI sheets (see SAP Note 397504 - Support for ABAP list-based PI sheet). Currently
only very few customers (less than 5 known) still use ABAP list-based PI sheets. The code needed for
list-based PI sheets is still available in SAP S/4HANA on-premise edition 1511 but will be not available
in a future release. Use browser-based PI sheets for the time being.
Business Process related information
Customers that used ABAP list-based PI sheets temporarily have to switch to browser-based PI
sheets: The corresponding control recipe destinations of type 1 (ABAP-based PI sheets) have to be
replaced with other control recipe destinations of type 4 (browser-based PI sheets). This mostly
affects the used master recipes and process orders. Browser-based PI sheets offer a better support of
the business processes that include the usage of ABAP-list based PI sheets. No influence on business
processes expected. Transactions CO55, CO60, CO60XT, CO64, and CO67 are still available but will be
replaced in a future release when a successor for browser-based PI sheets is available. The possibility
to select ABAP list-based PI sheets is still available in SAP S/4HANA, on-premise edition 1511 but will
be not available in a future release.
Required and Recommended Action(s)
Start exchanging control recipe destinations of type 1 (ABAP list-based PI sheets) with master recipes
(process orders). Create and send test control recipes for the exchanged control recipe destinations.
Check the browser-based PI sheets that are generated from the test control recipes.
Recommended:
Use XStep-based process instructions instead of characteristic-based process instructions
Replace generation scopes and filters that are defined in customizing (of the control recipe
destination) with XStep-based generation scopes and valuation symbols
2.1.12.10 ANSI/ISA S95 Interface
Description
Simplification List for SAP S/4HANA 1610
166
The ANSI/ISA S95 interface is outdated and has functional gaps that prevent easy consumption.
Therefore the ANSI/ISAS S95 interface is not in use by customers. Usage of the ANSI /ISA S95
interface is not recommended in S/4HANA. The code needed for ANSI/ISA S95 interface is still
available in SAP S/4HANA, on-premise edition 1511(Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional equivalent is
available) but will be not available in a future release. Use MES Integration or the POI Interface
instead.
Business Process related information
Usage of the ANSI/ISA S95 interface is not recommended anymore.
Required and Recommended Action(s)
Use the POI interface or the MES interface to connect SAP S/4HANA to an MES system or a planning
system. For details, see the MES integration documentation (link) and the POI documentation (link).
There is no immediate action required since the classic S95 Interface is still available. Check if you call
the above mentioned RFC function modules from an external system.
2.1.12.11 PP-MRP - Subcontracting
Description
Context
SAP ERP had three different ways of planning parts to be provided to a subcontractor:
Planning subcontracting demand together with internal demand in the make-to-stock
planning section (3.0-logic)
Separating subcontracting demand and stock into single subcontracting planning sections
(one section per subcontractor) and planning uncovered subcontracting demand together
with internal demand in the make-to-stock planning section (4.0-logic)
Planning separately the demand of every subcontractor by means of subcontracting MRP
areas (available from SAP ERP release 4.5)
Description
In SAP S/4HANA on-premise edition 1511, the 4.0 logic was removed while the 4.5 logic was
simplified. The SAP S/4HANA MRP uses default planning parameters if MRP-area-specific material
master records do not exist. You only have to create an MRP area for every subcontractor. Of course,
it is still possible to create MRP area/supplier-specific material master data if required.
Reason
This simplification has the following advantages:
Simplification List for SAP S/4HANA 1610
167
Separate planning of every subcontractor is possible without having to create an MRP-areaspecific material master record.
The planning logic is simplified. There are two rather than three different ways to plan parts
to be provided to a subcontractor.
Business Process related information
The default way of planning parts to be provided to subcontractors is based on MRP areas. A
subcontracting MRP area should be created for every subcontractor. It is not required to create an
MRP-area-specific material master record for every part to be provided to the subcontractor, but of
course it is possible if you want to overrule the default planning parameters.
Required and Recommended Action(s)
If you have several subcontractors requiring the same component materials and if you do not yet
use MRP areas to plan the required components then proceed as follows:
Create MRP areas for every subcontractor (can be done before or after upgrade)
Run regenerative MRP after the upgrade
Related SAP Notes
Custom Code related information
SAP Note: 2227532
2.1.12.12 Digital Signature
Description
Digital signature legacy functionality is based on function modules of package CJ in SAP_APPL. The
code needed for the legacy functionality is still available in SAP S/4HANA, on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is available). Since SAP_ABA 6.20 the successor functionality
(class-based signature tool, package DS) is available. Implementations of digital signature
functionality using class-based signature tool is easier to establish. Use the class-based signature tool
instead of the legacy functionality.
Business Process related information
No influence on business processes expected. Transaction DSAL is still available in SAP S/4HANA, onpremise edition 1511 but will be replaced by a successor functionality in a future release.
Required and Recommended Action(s)
Check that signature processes are completed. This is generally relevant for all signature processes,
independent of the signature functionality used (legacy or class-based signature tool).
Simplification List for SAP S/4HANA 1610
168
Related SAP Notes
SAP Note
SAP Note: 700495
2.1.12.13 Electronic Records
Description
Electronic records (LO-ELR) provide tools for evaluation of the logs that can be written for changes in
database table content. These logs are stored in database table DBTABLOG. It is also possible to
display change documents and logs of long text changes. Electronic records are part of the SAP
functionality that supports legal compliance in the regulated environment (production of active
ingredients and pharmaceuticals). Since SAP_BASIS 7.03, the successor functionality (NetWeaverbased audit trail) is available in SAP_BASIS (package S_AUT). In addition to the functionality of the
electronic records, the NetWeaver-based audit trail provides the following functions:
Access to archived change documents and database table records
Compliance with the Information Lifecycle management (ILM) standard of SAP
Improved functionality to define custom selections on database table logs and change
documents
The NetWeaver-based audit trail provides a migration report to transfer the customizing settings of
the electronic records. The functionality of electronic records is still available in SAP S/4HANA, onpremise edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but
not considered as future technology. Functional equivalent is available).
Business Process related information
No changes to business processes. Transactions AUT01 - AUT05, AUT10 are still available in SAP
S/4HANA, on-premise edition 1511. These transaction codes will be not available in a future release.
Required and Recommended Action(s)
If necessary, transfer the customizing settings using SAP report AUT_MIGRATE_ENHAT_DB_DATA in
old release before migrating to SAP S/4HANA, on-premise edition 1511.
2.1.12.14 Downtimes Functionality
Description
Downtimes functionality (PP-PI-DTR) was developed in SAP R/3 4.6 C, but its productive usage has
been withdrawn (as described in SAP Note 333382 - Downtimes: Function not available/released).
The usage of downtimes functionality is therefore withdrawn in SAP S/4HANA, on-premise edition
1511 (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
Simplification List for SAP S/4HANA 1610
169
future technology. Functional equivalent is not available yet.). Currently there is no functional
equivalent available within SAP S/4HANA, on-premise edition 1511.
Business Process related information
No changes on business processes expected
Required and Recommended Action(s)
None
2.1.12.15 MiniApps PP-PI
Description
In SAP R/3 4.6 C, coding was created to support MiniApps and workplaces. MiniApps and workplaces
were never released for productive usage. The MiniApp functionality is still available in SAP
S/4HANA, on-premise edition 1511 (Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is not available yet.). There is
currently no functional equivalent available.
Business Process related information
No changes on business processes expected
Required and Recommended Action(s)
None
2.1.12.16 Process Data Evaluation (PP-PI-PMA)
Description
In SAP R/3 4.7, the support for process data evaluation was stopped (see SAP Note 511488 - Support
set for process data evaluation). The functionality of process data evaluation is still available in SAP
S/4HANA, on-premise edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
170
None
2.1.12.17 Campaign Weighing and Dispensing
Description
The functionality of campaign weighing and dispensing was not used productively. The corresponding
xMII content is not available anymore. The functionality is still available in SAP S/4HANA, on-premise
edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is available)
Business Process related information
No changes to business processes. The weighing solution of the SAP PP-PI consulting organization
does support the required functionality. Transaction CMATRANGE is still visible in SAP S/4HANA, onpremise edition 1511.
Required and Recommended Action(s)
None
2.1.12.18 Production Campaign (ERP)
Description
The functionality of production campaign is still available in SAP S/4HANA, on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is not available yet).
Business Process related information
Transactions CPCN, PCA1-PCA3, and PCCO are still available.
2.1.12.19 Electronic Batch Record
Description
The functionality of electronic batch record (EBR) is required by customers who work in a regulated
environment (production of active ingredients, pharmaceuticals, and so on).
Simplification List for SAP S/4HANA 1610
171
The content of the EBR is stored in optical archives (using SAP ArchiveLink technology). EBR Content
is revisited during external audits. The content has to be available for 10 years on average.
The functionality is still available and working in SAP S/4HANA, on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Before upgrading to SAP S/4HANA, on-premise edition 1511, it is recommended that you complete
all open approval procedures for electronic batch records.
2.1.12.20 Process Messages
Description
The functionality of process messages is still available in SAP S/4HANA, on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected.
2.1.12.21 Control Recipes/Instructions
Description
The functionality of control recipes and control instructions is still available in SAP S/4HANA, onpremise edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but
not considered as future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Not required.
Simplification List for SAP S/4HANA 1610
172
2.1.12.22 Storage Location MRP
Description
Context
In SAP ERP, storage locations can be excluded from MRP planning or they can be planned separately
from other storage locations. In the latter case a reorder point procedure with maximum lot size is
used which triggers transport reservations to fill up the storage location. MRP areas cover the very
same business requirements. Materials with MRP-area-specific MRP type 'ND' (no MRP) can be used
instead of materials with a storage location excluded from MRP. Materials with MRP-area-specific
MRP type 'VB' (reorder point planning) can be used instead of materials with separately planned
storage locations. The storage location functionality is a subset of the MRP areas capabilities.
Description of Simplification
The S/4HANA MRP only plans on plant and MRP area level. Planning on storage location level is not
available in SAP S/4HANA, on-premise edition 1511.
Reason
The reason for this change are:
The MRP logic is simplified. There is only one solution for planning on storage location level
The MRP area logic is more advanced than the logic for planning on storage location level. All
MRP types and lot-sizing procedures are possible on MRP area level
The system creates planning file entries on plant and MRP area level. If planning is required
on MRP area level, then the system only plans the affected MRP area. The system does not
create planning file entries on storage location level and it did not do so in SAP ERP. The SAP
ERP MRP had to plan all separately planned storage locations and the plant level every time
inventory or an expected receipt was changed in a single separately planned storage
location. Planning on MRP area level is more efficient
Business Process related information
Storage Location MRP is not available in SAP S/4HANA, on-premise edition 1511. Planning on MRP
area level has to be used instead.
Required and Recommended Action(s)
Conversion Pre-Checks raise an error if storage location MRP is used in the source ERP system. Run
report MRP_AREA_STORAGE_LOC_MIGRATION if the pre-checks detect that storage location MRP is
used. The report first checks some prerequisites like MRP types, lot-sizing procedures, and MRP
areas in customizing. If the required customizing entries are missing, you have to create them
manually. Follow the instructions provided by the report. If all prerequisites are fulfilled, then the
Simplification List for SAP S/4HANA 1610
173
report generates material master records for planning on MRP area level using the storage location
material records. After the report was performed, planning is done on MRP area level, also if MRP is
performed on the start release.
Related SAP Notes
Conversion Pre-Checks
Custom Code related information
SAP Note: 2216528
SAP Note: 2227579
2.1.12.23 Process Operator Cockpits
Description
The functionality of process operator cockpits (POC) is still available in SAP S/4HANA, on-premise
edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Not required.
2.1.12.24 Material Identification/Reconciliation
Description
The functionality of material identification/reconciliation is still available in SAP S/4HANA, onpremise edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but
not considered as future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Not required
2.1.12.25 Flow Manufacturing
Description
Simplification List for SAP S/4HANA 1610
174
The functionality of flow manufacturing is still available in SAP S/4HANA, on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is available). SAP Advanced Planning and Optimization (SAP
APO) acts as successor.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Create required master data in SAP APO and set up flow manufacturing in SAP APO.
Related SAP Notes
Custom Code related
information
ERP coding enhancements will not be supported after replacement with
SAP APO.
2.1.12.26 Process Flow Scheduling (PP-PI)
Description
The process flow scheduler PFS was a scheduling tool for the process industries offered by SAP. Since
SAP R/3 4.6 C, the process flow scheduler is replaced by SAP Advanced Planning and Optimization
APO (see also SAP Note 217113 - PFS: Missing functions). The PFS interfaces is not available in SAP
S/4HANA on-premise edition 1511.
Business Process related information
No influence on business processes expected
Transaction not available in SAP S/4HANA on-premise edition
1511
PFSM
Required and Recommended Action(s)
None
2.1.12.27 Rate and Rough-Cut Planning
Description
SAP ERP production versions allowed you to reference routings, rate routings, and rough-cut
planning profiles in parallel. MRP then created capacity requirements for detailed planning, rateSimplification List for SAP S/4HANA 1610
175
based planning, and rough-cut planning in parallel. The detailed capacity requirements originated
from the explosion of routings, the rate-based capacity requirements originated from the explosion
of rate routings, and the rough-cut capacity requirements originated from the explosion of rough-cut
planning profiles. S/4 has only one scheduling level. The S/4 MRP explodes the one routing defined in
the production version, which can be a routing, a rate routing, or a rough-cut planning profile. This
was changed for the following reasons:
S/4 planned orders and production orders have consistent capacity requirements. There are
no discrepancies between detailed planning, rough-cut planning, and rate-based planning
A production process is performed either on an assembly line or in a job-shop environment.
If something is produced on a takt-based assembly line, then the production process should
be modelled by a rate routing. If something is produced in a job-shop environment then the
production process should be modelled by a standard routing. There is no production
process that is both rate-based and job-shop simultaneously. Therefore there is no need to
perform rate-based and detailed scheduling in parallel. Of course it is still possible to define
alternative production versions for the same material, where one production version is
performed on an assembly line and the other one is performed in a job-shop. A single
production version, however, always has a single model of the production process.
Different scheduling levels make reporting on capacities utilization and capacity load more
difficult. Users always have to specify the scheduling level.
S/4 can easily aggregate capacity requirements originating from different production
versions. In SAP ERP, however, you were only allowed to aggregate the capacity
requirements of a selected scheduling level. You had to make sure not to mix the detailed
capacity requirements and rate-based capacity requirements. Analytics on capacity load
across departments was difficult if one department used job-shop manufacturing and the
other used assembly lines.
Two scheduling levels double the runtime needed for scheduling. Three scheduling levels
triple the runtime needed for scheduling.
Capacity planning in S/4 shall be simple. PPDS offers advanced capacity planning features for
the more difficult planning problems.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
The Conversion pre-check raises a warning if you use scheduling levels other than "Detailed
planning". In this case you should check the production versions. The unfortunate naming of the
scheduling levels could have resulted in a separation of job-shop and rate based capacity planning.
Copy any rate routings from scheduling level "Rate-based planning" to scheduling level "Detailed
planning" if the production process is modelled by a rate routing and if the routing is only defined for
scheduling level "Rate-based planning".
Related SAP Notes
Conversion Pre-Checks
Pre-Check class CLS4H_PP_MRP
Simplification List for SAP S/4HANA 1610
176
2.1.12.28 Planning Horizon
Description
The SAP ERP MRP covered material demand inside the planning horizon only if processing key
"NETPL" was used. It covered all material demand if processing key "NETCH" was used. Planning
inside the planning horizon was a performance measure intended to improve MRP runtime. With
planning inside the planning horizon, MRP had to create fewer planned orders and was therefore
running faster. This was achieved at the expense of a more complicated planning procedure.
Planning horizons for materials on different BOM levels had to be aligned. Periodically, net change
planning with processing key "NETCH" had to be performed in order to create planned orders for
material demand in the more distant future. The S/4 MRP always covers all material demand.
Planning inside the planning horizon is no longer available. Thanks to performance improvements of
MRP in HANA, the additional performance improvements of net change planning are negligible and
do not justify the additional effort.
Business Process related information
A planning run is usually executed in batch mode via the planning batch transactions MDBT for MRP,
MSBT for Long Term Planning and MDBS for MPS-Planning. In that context, variants can be defined. If
old variants still contain the processing key NETPL, they won't work anymore.
Required and Recommended Action(s)
If there are still variants for the planning run batch Transactions having the processing key filled with
NETPL, these variants have to be deleted. Customers can build their own planning application using
the BAPI BAPI_MATERIAL_PLANNING. The BAPI has got the same planning parameter options as the
classical planning transactions. In that context the processing key NETPL cannot be used any more.
Conversion Pre-Checks and Custom Code related information
Custom Code related
information
Customers can build their own planning application using the BAPI
BAPI_MATERIAL_PLANNING. The BAPI has got the same planning
parameter options as the classical planning transactions. In that context the
processing key NETPL cannot be used any more.
2.1.12.29 Batch History
Description
The functionality Batch History is considered as not the target architecture within SAP S/4HANA, onpremise edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but
not considered as future technology. Functional equivalent is available). The available functional
equivalent is global batch traceability (GBT)
Business Process related information
Simplification List for SAP S/4HANA 1610
177
No influence on business processes expected. The transaction codes related to Batch History are still
available within SAP S/4HANA, on-premise edition 1511.
2.1.12.30 Selected Business Functions in PP area
Description
Selected PP business functions are not the target architecture in SAP S/4 HANA, on-premise edition
1511 FPS1:
The usage of the following PP business functions are not the target architecture in SAP S/4
HANA. With SAP S/4 HANA, on-premise edition 1511 FPS1 they are changed to customerswitchable and obsolete in SAP S/4 HANA, on-premise edition 1511 FPS1:
o
o
o
LOG_PP_INTELI_01
LOG_PP_PRSP
EA-SCM
The following PP business functions are customer-switchable and obsolete in SAP S/4 HANA,
on-premise edition 1511 FPS1. The related functions are planned to be replaced in future:
o
o
LOG_PP_BATCH_HISTORY
LOG_PP_CFB
Basic Information related to Business Functions
If a business function was switched ON in the Business Suite start release system, but defined as
always_off in the SAP S/4HANA, on-premise edition target release, then a system conversion is not
possible with this release. See SAP Note 2240359 - SAP S/4HANA, on-premise edition 1511: AlwaysOff Business Functions. If a business function is defined as "customer_switchable" in the target
release (SAP S/4HANA, on-premise edition 1511 FPS1), then the business function status remains
unchanged from the status on start release. Business Functions defined as obsolete cannot be
switched ON
Business Process related information
Customer having one or all of these business functions switched ON in Business Suite start release
can execute the system conversion. Nevertheless the functionality related to these business
functions is not available within SAP S/4 HANA, on-premise edition 1511 FPS1.
Customers having none of these business functions switched ON in Business Suite start release
cannot activate these business functions after the system conversion to SAP S/4 HANA, on-premise
edition 1511 FPS1.
Simplification List for SAP S/4HANA 1610
178
2.1.12.31 External Interfaces in PP
Description
The following interfaces to external systems are not available in SAP S/4HANA:
Interface
Package Reason
PFS-Interface CPFS
The process flow scheduler PFS was a scheduling tool for the process
industries offered by SAP. It was replaced by SAP-SCM with R/3 release
4.6C. See also separate simplification item 2.1.11.33Process Flow Scheduling
(PP-PI)
LPOXLPO
Lean planning and operations LPO was an algorithm for levelling production
Interface
based on lean principles. The algorithm was never productized
Icon
/SCRM/* Icon was a response management solution. SAP's preferred solution for
Interface
response management is IBP for response
CBP Interface CBPC
The constraint-based planning interface (CBP interface) was replaced by the
POI interface in 2002. For details, see note 500526
KK2 Interface
This interface used an outdated interface technology (flat file)
KK5 Interface
This interface used an outdated interface technology (flat file)
S95 Interface
See separate simplification item 2.1.11.19ANSI/ISA S95 Interface
Use the POI interface or the integration with Manufacturing Execution Systems instead.
Business Process related information
Use the POI interface or the MES interface to connect SAP S/4HANA to an MES system or a planning
system. For details, see the MES integration documentation and the POI documentation
Transaction not available in SAP S/4HANA
on-premise edition 1511
RFC-enabled function modules are not
available in SAP S/4HANA
CBP1, CBP2, CBP3, CBP4, CBP5, CBP6, CBP7, CBPV,
CBCACT, CBCAT, CBCBRG, CBCF, CBCMLGMRP,
CBCMLGSOP, CBCMLS, CBCMOD, CBCMSV, CBCMTG,
CBCONFMRP, CBCONFSOP, CBCPAR, CBCS, CBCSTEP,
CBPRO, PFSE, PX01, PX02, PX03, PX04, PX05
LPO_BOM_GETDETAIL, LPO_DEMANDS_GETLIST,
LPO_ITEM_GETDETAIL, LPO_MATDATA_FIND,
LPO_MATDATA_GETDETAIL, LPO_PLANT_GETLIST,
LPO_PRODCOMPLETE_GETLIST,
LPO_PRODCONF_CREATE,
LPO_PRODSHIPMENT_GETLIST,
LPO_ROUTE_GEDETAIL,
LPO_SCHEDULEPLAN_UPDATE, LPO_STOCK_GETLIST,
LPO_WORKCENTER_FIND,
LPO_WORKCENTER_GETDETAIL,
CBP_MRP_DEMORDERLIST_GET_RFC,
CBP_MRP_DEMORDER_GET_RFC,
CBP_MRP_MANORDERLIST_GET_RFC,
CBP_MRP_MANORDER_GET_RFC,
Simplification List for SAP S/4HANA 1610
179
CBP_MRP_PLAN_DISMISS_RFC,
CBP_MRP_PLAN_REQUEST_RFC,
CBP_MRP_PLAN_SAVE_RFC,
CBP_MRP_PLAN_STARTUP_RFC,
CBP_EXC_CAPACITY_REQT_REQUEST,
CBP_EXC_DELKZ_DESC_REQUEST,
CBP_EXC_OPER_DURATION_REQUEST,
CBP_EXC_WC_CAPACITY_REQUEST,
CBP_SOP_PLAN_DISMISS_RFC,
CBP_SOP_PLAN_REQUEST_RFC,
CBP_SOP_PLAN_SAVE, CBP_SOP_PLAN_SAVE_RFC,
CBP_SOP_PLAN_STARTUP_RFC,
CBP_GEN_INTERACTIVE_START_RFC
Required and Recommended Action(s)
Check if you call any of the above mentioned RFC-enabled function modules from an external
system. Call RFC function modules of the POI interface instead.
Related SAP Notes
Custom Code related information
SAP Note: 2226966
2.1.12.32 Graphical Planning Table
Description
The graphical planning table (also known as graphical planning board or Gantt chart) can be used for
capacity load levelling and sequence planning. The graphical planning table is still available in SAP
S/4HANA, but not considered as the target architecture. Currently there is no functional equivalent
available within SAP S/4HANA, on-premise edition 151(Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional equivalent is not
available yet).
Business Process related information
The future graphical planning table implementation will support the basic features like changing
operation start times or resources by drag and drop. The influence on business processes should
therefore be minimal. It will however not be possible to translate customizing and personalization of
the classic graphical planning table into a UI configuration of a future graphical planning table.
Required and Recommended Action(s)
Invest reasonably in the classic planning board
Simplification List for SAP S/4HANA 1610
180
2.1.12.33 Logistic Information System in PP
Description
Remark: For the general approach regarding analytics within SAP S/4HANA see the following
analytics simplification item in cross topics area.
The shop floor information system is part of the logistics information system LIS (Note: If you use a
material number longer than 18 characters - see restriction note Extended Material Number in LIS:
SAP Note 2232362). The LIS can be used to compare planned vs. actual parameters like lead time,
execution time, queue times, scrap, and so on. The classic ERP implementation of the LIS has some
specifics:
LIS operates on redundant data. Every business transaction not only updates the business
documents, but also pre-aggregated data in LIS. Performance suffers, locking conflicts might
occur, and memory is wasted
LIS operates on pre-aggregated data. It is not possible to drill down into the individual
business documents. Multi-dimensional reporting (aka Slicing and dicing) is only possible for
dimensions provided in the pre-aggregated data
LIS uses an old UI technology making multi-dimensional reporting clumsy
LIS only supports material numbers with up to 30 characters
Future production analytics will be based on HANA, CDS views aggregating transactional data
dynamically, and powerful analytical UIs for multi-dimensional reporting. With this it will be possible
to replace the current LIS. You will be able to use classic LIS and the future production analytics in
parallel for some time as long as you do not switch off the update of the LIS tables(Functionality
available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology).
Once future production analytics supports all your analytics requirements, you can switch off the
update of the LIS tables. Once you have switched off updating LIS tables, you will notice the following
improvements:
Improved performance of many transactions (fewer tables to update, fewer locking conflicts)
Less memory required
Business Process related information
The following reports require a closer look:
Kanban: Info structure S029 collects frequency information of status changes. This information is
only stored in S029. In future we intend to collect not only frequency information but the individual
historic Kanban events. Any information in S029 will be lost after this change is implemented.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
181
Invest reasonably in the LIS. The LIS is intended as an interim solution, which can be used until PP
analytics in HANA has the required scope. This also allows you to migrate your business processes
step by step from SAP ERP to SAP S/4HANA, on-premise edition 1511.
Related SAP Notes
Custom Code related
information
Enhancements and modifications of the LIS will not work for the future
analytics solution.
Custom reports reading one of the following tables will not work after the
update of the LIS tables is switched off:
S021: Order item data for material
S022: Operation data for work center
S023: Totals for material
S024: Totals for work center
S025: Run Schedule
S026: Material usage
S028: Reporting point statistics
S029: Kanban
S094: Stock/Requirements Analysis
S225: Goods receipts: repetitive manufacturing
S227: Product costs: repetitive manufacturing
These tables will be replaced by CDS views providing more or less the
same information but with different column names and structures.
2.1.12.34 Sales and Operation Planning
Description
Sales & Operations Planning (SOP) is a forecasting and planning tool for setting targets for sales and
production based on historical, current, or estimated data. SOP is used for long-term strategic
planning, not short-term tactical planning. Resource requirements can be computed to
determine work center load and utilization. SOP is often performed on aggregated levels such as
product groups and work-center hierarchies. Sales & Operations Planning includes standard SOP and
flexible planning. Standard SOP comes preconfigured with the system. Flexible planning offers
options for customized configuration. Sales & Operations Planning (SOP) will be replaced by
Integrated Business Planning IBP(Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology). Integrated Business Planning supports all SOP
features plus advanced statistical forecasting, multi-level supply planning, an optimizer, collaboration
tools, an Excel-based UI, and Web-based UIs.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
182
PP SOP is intended as a bridge or interim solution, which can be used until IBP is available as part of
SAP S/4HANA, on-premise edition 1511 and which allows you a stepwise system conversion from SAP
ERP to SAP S/4HANA, on-premise edition 1511.
Related SAP Notes
Custom Code related
information
Integrated Business Planning (IBP) is an all-new implementation for sales and
operations planning. Any enhancements or modifications of SOP will not
work once IBP is used.
2.1.12.35 Simplified Sourcing
Description
Context
MRP determines material shortages, then determines lot sizes, and then sources of supply. Lot sizing
can decide to cover several material shortages with just one material receipt. After lot sizing, the
planned material receipts with the requirement date and quantity are known. Subsequently sourcing
determines whether the required quantity is manufactured or purchased and from which supplier
the material is purchased.
Description of Simplification
The Basic idea of this simplification is a reduced set possible sources of supply. SAP S/4HANA
supports the following types of sources of supply:
Production versions
Delivery schedules
Purchasing contracts
Purchasing info records
Sources of supply have a common set of attributes like a temporal validity interval and a quantitative
validity interval. Sourcing selects valid sources of supply with the following conditions:
The source of supply is a production version
o and the procurement type of the material is either 'E' (in-house production) or 'X'
(Both procurement types)
o and the production version is neither "Locked for any usage" nor "Locked for
automatic sourcing"
o and the planned material receipt's quantity is inside the quantity range of the
production version
o and the planned material receipt's delivery date is in the validity period of the
production version
The source of supply is a purchasing info record
Simplification List for SAP S/4HANA 1610
183
and the procurement type is 'F' (external procurement)
and the purchasing info record is flagged for "Relevant for automatic sourcing"
and the planned material receipt's quantity is inside the quantity range of the
purchasing info record
o and the planned material receipt's delivery date is in the validity period of the
purchasing info record
The source of supply is a delivery schedule and the procurement type is 'F' (external
procurement)
The source of supply is a purchasing contract and the procurement type is 'F' (external
procurement)
o
o
o
Quota arrangements can be used to prioritize sources of supply in case several sources of supply are
valid simultaneously. If sourcing determines several valid sources of supply for the same material,
plant, quantity, and date, but does not find any quota arrangements, then it prefers production
versions over delivery schedules, delivery schedules over purchasing contracts, and purchasing
contracts over purchasing info records. If sourcing selects a production version as source of supply,
then the material receipt is going to be a planned order. If sourcing selects a purchasing info record,
then the planned material receipt is going to be a purchase requisition.
The SAP S/4HANA sourcing logic differs from the classic business suite sourcing logic in the following
aspects:
Business Suite Logic
SAP S/4HANA Logic
Reason
Material master attribute
Production versions are the only source of supply Simplification of the sourcing logic;
"Selection Method" MARCfor in-house production. The material master
symmetry of different sources of
ALTSL determines if MRP finds attribute MARC-ALTSL no longer exists. Sourcing
supply; only production versions are
a BOM via the BOM's validity selects material BOMs only if a suitable production integrated into quota arrangements;
period, the BOM's quantity
version exists. Sourcing does not need production only production versions make sure
range, or via production version versions to find make-to-order and make-to-project BOM and routing fit together
bills of material, but production versions are
required to select routings also if make-to-order or
make-to-project BOMs are used.
The order type attribute
Production versions are the only source of supply Simplification of the sourcing logic
"Routing selection" T399Xfor in-house production. A production version
ARBPA determines how a
references a routing. This routing is used to create
routing is determined during production orders
production order creation. The
attribute can be defined in
customizing transaction OPL8.
The production version has a MRP only selects production versions that are
The new status "Locked for automatic
locking indicator with values
neither 'Locked for any usage' nor "Locked for
sourcing" corresponds to the
'Locked' and 'Not locked'. MRP automatic sourcing."
"Relevant for automatic sourcing"
only selects production versions
indicator on the purchasing info record
that are not locked.
(Symmetry); you can use one
production version (maybe with an
artificial routing) as the default for
new planned orders and manually
dispatch these planned orders to
proper lines/work centers
Phantom assemblies are
Production versions are the only source of supply Simplified sourcing logic and the
exploded with the
for phantom assemblies. If a phantom assembly
possibility to synchronize BOM
method defined in the
production version exists with the same ID as
explosion on several BOM levels.
the production version exploded on finished
Simplification List for SAP S/4HANA 1610
184
phantom assembly's material material level, then the phantom BOM explosion
master attribute MARC-ALTSL. explodes the BOM defined in the production
version with the same production version ID. If no
such production version exists, then the system
searches for a phantom assembly production
version using the explosion date and the quantity.
Subcontracting purchase
Production versions are the only source of supply
requisitions are exploded with for subcontracting. If you use subcontracting
the method defined in the
purchasing info records to define the supplier,
material master attribute
you should define the production version in the
MARC-ALTSL
purchasing info record. In all other cases, the
system selects the material's production versions,
also for subcontracting
MRP only selects purchasing
Purchasing info records are a source of supply in
info records if a source list
their own right. MRP selects purchasing info
entry exists that references the records if the "relevant for automatic sourcing"
supplier referenced in the info indicator is set in the purchasing info record
record
MRP uses source lists to
Source lists are not considered in the S/4HANA ondetermine vendors, contracts, premise edition 1511 until SP01.
or delivery schedules
Simplified sourcing logic and the
possibility to define a supplier-specific
production version. Different suppliers
may need different subcontracting
components from the client while
procuring the other parts from
elsewhere
Simplification of the sourcing logic: It is
not required to create a source list
entry on top of the purchasing info
record
Optionally, source lists can be used to
temporarily block a source of supply or
MRP-enable it only for a limited period
In later releases source lists can be used to provide of time.
additional information for sources of supply. For
example, the source list may be used to block a
source of supply or MRP-enable it only for a limited
period of time.
Alternatively quota arrangements can be used as a
workaround.
MRP only considers quota
MRP considers quota arrangements always. It is not In the early days of MRP, reading and
arrangements if the material required to switch it on in the material master
considering quota arrangements was
master attribute MARC-USEQU
expensive. MARC-USEQU was a
is set
performance measure, with which you
could switch off quota arrangements
in MRP to improve performance. MRP
in HANA does not suffer much from
considering quota arrangements.
Reason
Simplified sourcing in SAP S/4HANA is simpler than sourcing in the classic SAP ERP for the following
reasons:
The different sources of supply are pretty symmetrical. Sources of supply have a temporal
validity, a quantitative validity, a deletion indicator, and a "relevant for automatic sourcing"
indicator. The sourcing logic can treat the different sources of supply in a uniform way
Quota arrangements can be used to prioritize any of the possible sources of supply
Purchasing info records are proper sources of supply. The SAP S/4HANA MRP can select
purchasing info records without source list entries. It is sufficient to define the supplier
information of a material in the purchasing info record.
Production versions make sure BOM and routing fit together
Production versions have always been the only in-house production source of supply
integrated with APO PP/DS. With production versions as the only in-house production source
of supply, ERP sourcing and PP/DS sourcing become more similar.
Simplification List for SAP S/4HANA 1610
185
Purchasing info records, contracts, and delivery schedules have always been the external
procurement sources of supply integrated with APO. With purchasing info records being
proper sources of supply, ERP sourcing and PP/DS sourcing become more similar
A unified source of supply model is the basis for future innovations in sourcing
Business Process related information
If you want a BOM or routing to be considered by MRP, you have to create a production version. If
you want MRP to source a purchase requisition from a certain supplier, you no longer have to define
a source list entry. It is sufficient to set the indicator "relevant for automatic sourcing" in the
purchasing info record.
Required and Recommended Action(s)
-Actions required for manufactured materials
Check if production versions exist for those BOMs and routings that should be considered by MRP.
The Conversion pre-check mentioned above can be used to this end. Report
CS_BOM_PRODVER_MIGRATION creates proposals for production versions based on BOM validities.
Run the report and accept or reject the proposed production versions. Note 2194785 contains report
CS_BOM_PRODVER_MIGRATION.
-Actions required for externally procured materials
Analyse your source list entries
No action is required if source list entries refer to contracts and delivery schedules. S/4HANA
sourcing finds contracts and delivery schedules without source list entries.
Activate the automatic sourcing indicator in the corresponding purchasing info record if the
source list entry only refers to a supplier and if the supplier shall be selectable by MRP
Related SAP Notes
Conversion PreChecks
The pre-check with the check ID "SAP_PP_MRP_PRODNVERS_FOR_BOMS_CHECKS" checks if
there are materials for which the SAP ERP MRP would find a BOM but not the SAP S/4HANA
MRP. The SAP S/4HANA MRP only finds BOMs with valid production versions. SAP ERP MRP
also finds BOMs with valid temporal or quantitative validity intervals if the BOM selection
method specifies BOM selection using date or quantity. The pre-check raises a warning if a
material has a BOM that is valid in the future and if the BOM selection method MARC-ALTSL
is not yet specifying production versions as source of supply. If the pre-check detects such
issues, proceed as described in section "Required and Recommended Actions on Start
Release".
The Conversion Pre-check is not mandatory and it only raises a warning, so you do not have
to create production versions for dead materials, for materials for which you do not expect
the need to produce the material. It is however recommended to perform the pre-check and
create production versions for all materials likely to be manufactured in future.
Simplification List for SAP S/4HANA 1610
186
Custom Code
related
information
SAP Note: 2226333
If you implemented BADI MD_MODIFY_SOURCE in SAP ERP, you should check if the
intended functionality still works. Also check the changes related to the Simplification Item
2.1.11.11MRP in HANA.
See note 2226333 for details
2.1.12.36 Browser-based Process Instruction-Sheets/Electronic Work Instructions
Description
The functionality of browser-based PI sheets and electronic work instructions is still available in SAP
S/4HANA on-premise edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is not available yet). There is
no functional equivalent as alternative available within SAP S/4HANA, on-premise edition 1511.
Browser-based Process Instruction Sheets (PI-Sheets) and electronic work instructions (EWI) are
based on a framework that allows the creation of worker UIs optimized for the needs of individual
workers. The content of the PI sheets/EWI is rendered as plain HTML and displayed in the SAP HTML
Viewer of ABAP dynpros. It requires SAPWinGUI as UI technology and does not work with
SAPWebGUI. Because SAPWinGUI is used, the browser-based PI sheets and EWIs are dependent on
MS Internet Explorer (technical prerequisite for HTML control). Content of browser-based PI sheets
and EWIs is defined using process instruction characteristics (XStep-based process instructions or
characteristic-based process instructions [only PI sheets]). Based on the process instruction content,
the control recipes/control instructions are created. If the control recipes/instructions belong to the
control recipe destination of type 4, the corresponding browser-based PI sheet/EWI is created when
the control recipe/instruction is sent. The rendered HTML content of browser-based PI sheets and
EWIs uses XSL and CSS. SAP standard XSL and CSS can easily be exchanged by custom style sheets.
This allows easy custom adoption of the UI at the customer. Browser-based PI sheets are used in the
regulated environment (pharma production, and so on) to control and track the production
execution. They can be archived to optical archives as part of the electronic batch record (EBR) to
ensure compliant manufacturing (comply with US CFR21 part 11 and so on). Starting with SAP R/3 4.6
C, formerly used ABAP-list based process instruction sheets have been replaced by browser-based PI
sheets (see SAP Note 397504 - Support for ABAP list-based PI sheet). Related functionality is still part
of SAP ECC and S/4 -> separate simplification item.
Business Process related information
A future production operator UI will be built using state-of-the-art UI technology. It will not be
possible to translate the UI configuration of browser-based PI sheets/EWIs into a UI configuration of
a future worker UI. It has to be checked if the XSteps (the building blocks for browser-based PI
sheets/EWIs) can be used as the basis for generating modern worker UIs.
Required and Recommended Action(s)
Invest reasonably in XSteps, electronic work instructions, and browser-based PI sheets.
Simplification List for SAP S/4HANA 1610
187
Related SAP Notes
Custom Code related information
Enhancements and modifications of the browser-based PI
sheets/EWIs will not work for future worker UIs.
2.1.12.37 Internet Kanban
Description
Internet Kanban allowed suppliers to log onto a manufacturer's system and view the status of
Kanban containers in the manufacturer's system. It used a primitive browser UI to support suppliers
without SAP-GUI. Adjustments were required but sensitive from a security point of view. Deep
HTML knowledge was required to implement the required adjustments. With the availability of the
HTML-GUI, it is no longer necessary to hand-craft your own UIs. FIORI UIs will be another alternative
in the future to display the Kanban status.
Business Process related information
There are several alternatives to internet Kanban
Use SNC for supplier collaboration
Give suppliers access to Transaction PK13N in the HTML-GUI and adapt it to your needs using
screen personas
Transaction not available in SAP S/4HANA
on-premise edition 1511
PKW1
Required and Recommended Action(s)
Check whether you grant access to transaction PKW1 to your suppliers.
Related SAP Notes
Custom Code related information
SAP Note: 2228178
2.1.13 Logistics – PS
2.1.13.1 Simplification of Date Planning Transactions
Description
Simplification List for SAP S/4HANA 1610
188
There are currently multiple (partially redundant) transaction available to plan dates in projects. It´s
the target to have to simplify the related transaction in future. Accordingly the recommendation is to
use the Project Builder transaction CJ20N for this business requirements even if other transactions
are still available with SAP S/4HANA 1511(Functionality available in SAP S/4HANA 1511 delivery but
not considered as future technology. Functional equivalent is available.). For cross network
scheduling still transactions CN24 and CN24N are available with SAP S/4HANA 1511, however, these
transactions are planned to be replaced by other, simplified cross project / network scheduling
functions in future and hence are not the target architecture as well. Overall hence the following
date planning / scheduling transactions are categorized not as the target architecture:
CN24N Overall Network Scheduling
CN24 Overall Network Scheduling
CJ21 Change Basic Dates
CJ22 Display Basic Dates
CJ23 Change Forecast Dates
CJ24 Display Forecast Dates
CJ25 Change Actual Dates
CJ26 Display Actual Dates
CJ29 Update WBS (Forecast)
Business Process related information
The currently parallel (partly redundant) transactions for date planning and scheduling are still
available with SAP S/4HANA 1511 but they are not the target architecture. Customer invest (for
example related custom code or new end user knowledge transfer) need to consider this.
Required and Recommended Action(s)
End user knowledge transfer required to switch from multiple date planning transactions to single
maintenance transaction CJ20N.
2.1.13.2 Workforce Planning
Description
There are currently several workforce planning functions such as usage of PS teams and transactions
CMP2/CMP3/CMP9 available. These traditional transactions are still supported with SAP S/4HANA
1511 in project system but they are not considered as the target architecture (Functionality available
in SAP S/4HANA 1511 delivery but not considered as future technology. Functional equivalent is not
available yet.). It´s the target to have simplified and improved ways of workforce planning available
in future. The following transactions are hence categorized not to be the target architecture:
CMP2 Workforce Planning: Project View
CMP3 Workforce Planning: Work Center View
CMP9 Workforce Planning - Reporting
Simplification List for SAP S/4HANA 1610
189
Business Process related information
Still the existing workforce planning functions can be used. However, these functions and related
transactions are not the target architecture any longer and might be replaced in future by other
solutions which might not provide exactly the same functional scope of currently existing functions.
Required and Recommended Action(s)
None
2.1.13.3 Progress Tracking & Monitoring Dates
Description
Current progress tracking and project monitoring function in Project System are still available with
SAP S/4HANA 1511 but not considered as the target architecture (Functionality available in SAP
S/4HANA 1511 delivery but not considered as future technology. Functional equivalent is not
available yet.). It is recommended not to continue to enable progress tracking for PS objects and
project monitoring function. It is the intention in future to offer a simplified solution for this business
requirements. The following transactions are hence categorized not to be the target architecture:
NTWXPD Progress Tracking: Networks
WBSXPD Progress Tracking: WBS
NWTM Monitoring Network Dates
ACOMPXPD Progress Tracking Evaluations
AXPD Progress Tracking Evaluations
COMPXPD Progress Tracking for Components
DEXP Expediting
EXPD Expediting
Business Process related information
Still the existing progress tracking and monitoring dates functions can be used. However, these
functions and related transactions are not the target architecture and might be replaced in future by
other solutions which might not provide exactly the same functional scope of currently existing
functions.
Required and Recommended Action(s)
None
2.1.13.4 Project Claim Factsheet
Description
With SAP S/4HANA 1511 the Project Claim factsheet will not be available anymore since the claim
functionality is categorized not as the target architecture (see note 2267169).
Simplification List for SAP S/4HANA 1610
190
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
It is recommended using Project Issue and Change Management functionality and not PS
claim Management for appropriate business requirement.
Knowledge Transfer to key- and end-user
2.1.13.5 Project Reporting
Description
Current project reporting and analytic functions in Project System (PS) are still available with SAP
S/4HANA 1511 but not considered as the target architecture (Functionality available in SAP S/4HANA
1511 delivery but not considered as future technology. Functional equivalent is not available yet.). It
is intended to offer a simplified and even more flexible solution leveraging SAP HANA capabilities in
an optimized way for this business requirements in future. Please note that for example in Financials
partly already simplified reports exist with role SAP_SFIN_BCR_C ONTROLLER, which could be used as
replacements for certain PS reports. The following transactions are hence categorized not to be the
target architecture:
CN40 Project Overview
CN41 Structure Overview
CN42 Overview: Project Definitions
CN43 Overview: WBS Elements
CN44 Overview: Planned Orders
CN45 Overview: Orders
CN46 Overview: Networks
CN47 Overview: Activities/Elements
CN48 Overview: Confirmations
CN49 Overview: Relationships
CN50 Overview: Capacity Requirements
CN51 Overview: PRTs
CN52 Overview: Components
CN53 Overview: Milestones
CN60 Change Documents for Projects/Netw.
CN70 Overview: Batch variants
CN71 Create versions
CNB1 Purchase requisitions for project
CNB2 Purchase orders for project
CNMT Milestone Trend Analysis
CNS40 Project Overview
CNS41 Structure Overview
CNS42 Overview: Project Definitions
CNS43 Overview: WBS Elements
Simplification List for SAP S/4HANA 1610
191
CNS44 Overview: Planned Orders
CNS45 Overview: Orders
CNS46 Overview: Networks
CNS47 Overview: Activities/Elements
CNS48 Overview: Confirmations
CNS49 Overview: Relationships
CNS50 Overview: Capacity Requirements
CNS51 Overview: PRTs
CNS52 Overview: Components
CNS53 Overview: Milestones
CNS54 Overview: Sales Document
CNS55 Overview: Sales and Dist. Doc. Items
CNS60 Change Documents for Projects/Netw.
CNS71 Create versions
CNS83 PS: Archiving project - Info System
CNSE5 Progress Analysis
CJH1 Reconstruct Project Inheritance
CJH2 Project Inheritance Log
CJSA Data Transfer to SAP-EIS
CJSB Select Key Figure and Characteristic
CN41N Project structure overview
CNPAR Partner Overview
CJ74 Project Actual Cost Line Items
CJ76 Project Commitment Line Items
CJ7M Project Plan Cost Line Items
CJ80 Availability Control - Overview
CJ81 Update Report List
CJBBS1 Planning Board Report Assignment
CJBBS2 Structure Overview Report Asst
CJE0 Run Hierarchy Report
CJE1 Create Hierarchy Report
CJE2 Change Hierarchy Report
CJE3 Display Hierarchy Report
CJE4 Create Project Report Layout
CJE5 Change Project Report Layout
CJE6 Display Project Report Layout
CJEA Call Hierarchy Report
CJEB Background Processing, Hier.Reports
CJEC Maintain Project Crcy Trans.Type
CJEK Copy Interfaces/Reports
CJEM Project Reports: Test Monitor
CJEN Reconstruct: Summarized Proj.Data
CJEO Transport Reports
CJEP Transport Forms
CJEQ Import Reports from Client
CJET Translation Tool - Drilldown
CJEV Maintain Global Variable
CJEX Reorganize Drilldown Reports
Simplification List for SAP S/4HANA 1610
192
CJEY Reorganize Report Data
CJEZ Reorganize Forms
CJI1 Project Budget Line Items
CJI2 Budget Line Items: Document Chain
CJI3 Project Actual Cost Line Items
CJI3N Projects Line Items Actual Costs New
CJI4 Project Plan Cost Line Items
CJI4N Projects Line Items Plnd Costs New
CJI5 Project Commitment Line Items
CJI8 Project Budget Line Items
CJI9 Project Struct.Pld Costs Line Items
CJIA Project Actual and Commt Paymt LIs
CJIB Project Plan Payment Line Items
CJIF Projects: Profitability Analysis LI
CJT2 Project Actual Payment Line Items
CJVC Value Category Checking Program
OPI1 Maintain Value Categories
OPI2 Value Categories for Cost Elements
OPI3 Update Control: File RPSCO
OPI4 Commitment Item Value Categories
OPI5 Value Categories for Stag.Key Figs
OPI8 Display Value Category
S_ALR_87013503 SObj: Actual/Plan/Variance
S_ALR_87013504 SObj: Actual/Plan/Commitment
S_ALR_87013505 SObj: Current/Cumulated/Total
S_ALR_87013511 Order Profit
S_ALR_87013512 SObj: Actual/Plan/Variance
S_ALR_87013513 SObj: Current/Cumulated/Total
S_ALR_87013531 Costs/Revenues/Expenditures/Receipts
S_ALR_87013532 Plan/Actual/Variance
S_ALR_87013533 Plan/Actual/Cmmt/Rem.Plan/Assigned
S_ALR_87013534 Plan 1/Plan 2/Actual/Commitments
S_ALR_87013535 Actual in COArea/Object/Trans. Curr.
S_ALR_87013536 Plan/Actual/Down Payment as Expense
S_ALR_87013537 Commitment Detail
S_ALR_87013538 Project Version Comparison:Act./Plan
S_ALR_87013539 Project Version Comparison: Plan
S_ALR_87013540 Forecast
S_ALR_87013541 Project Interest: Plan/Actual
S_ALR_87013542 Actual/Comm/Total/Plan in COAr crcy
S_ALR_87013543 Act/plan/variance abs. / % var.
S_ALR_87013544 Actual/Plan Comparison: Periods
S_ALR_87013545 Period Comparison - Actual
S_ALR_87013546 Commitments: Period comparison
S_ALR_87013547 Period Comparison - Plan
S_ALR_87013548 Stat. key figures/periods
S_ALR_87013549 Act/plan compare with partner
S_ALR_87013550 Debit in object/CO area currency
Simplification List for SAP S/4HANA 1610
193
S_ALR_87013551 Plan: Debits in obj./CO area crcy
S_ALR_87013552 Debit/credit actual
S_ALR_87013553 Debit/credit plan
S_ALR_87013554 Comparison of 2 plan versions
S_ALR_87013555 Project results
S_ALR_87013556 Funds Overview
S_ALR_87013557 Budget/Actual/Variance
S_ALR_87013558 Budget/Actual/Commitmt/Rem.Plan/Assg
S_ALR_87013559 Budget/Distributed/Plan/Distributed
S_ALR_87013560 Budget updates
S_ALR_87013561 Availability Control
S_ALR_87013562 Annual Overview
S_ALR_87013563 Structure
S_ALR_87013564 Plan/Actual/Variance
S_ALR_87013565 Planned Contribution Margin
S_ALR_87013566 Actual Contribution Margin
S_ALR_87013567 Quotation/Order/Plan/Actual
S_ALR_87013568 Project Results
S_ALR_87013569 Incoming Orders/Balance
S_ALR_87013570 Act/plan/variance abs. / % var.
S_ALR_87013571 Actual/Plan Comparison: Periods
S_ALR_87013572 Project results
S_ALR_87013573 Overview
S_ALR_87013574 Expenditures
S_ALR_87013575 Revenues
S_ALR_87013577 Costs/Revenues/Expenditures/Receipts
S_ALR_87015124 Progress Analysis
S_ALR_87015125 Progress Analysis: Detail
S_ALR_87100185 Actual Costs Per Month, Current FY
S_ALR_87100186 Plan Costs per Month, Current FY
S_ALR_87100187 Commitment per Month, Current FY
S_ALR_87100188 Cumulated Actual Costs
S_ALR_87100189 Actual/Planned Time Series
S_ALR_87100190 Actual/Plan/Var Project + Respons
S_ALR_87100191 Receipts/Expenditures in Fiscal Year
CN42N Overview: Project Definitions
CN43N Overview: WBS Elements
CN44N Overview: Planned Orders
CN45N Overview: Orders
CN46N Overview: Networks
CN47N Overview: Activities/Elements
CN48N Overview: Confirmations
CN49N Overview: Relationships
CN50N Overview: Capacity Requirements
CN51N Overview: PRTs
CN52N Overview: Components
CN53N Overview: Milestones
CN54N Overview: Sales Document
Simplification List for SAP S/4HANA 1610
194
CN55N Overview: Sales and Dist. Doc. Items
CNVL Variable Overviews
OPU8 Overview Var.: Header Line Info Sys.
OPU9 Overview Variant: Item Line
CNE5 Progress Analysis
CJCD Change documents: WBS
CODC Change Documents for Network
Please note that PS analytical apps from Smart Business for Project Execution will not be
immediately available with SAP S/4HANA 1511 but similar functions are planned for future releases.
Hence SAP Fiori apps corresponding to the following apps are planned to be delivered only after SAP
S/4HANA 1511:
F0293
F0294
F0297
F0298
F0299
F0300
F0301
F0302
F0303
F0304
F0305
F0306
F0630
F0631
F0632
F0633
F0635
F0696
F0697
F0698
F0699
WBS Element Cost Variance
WBS Element Costs at Risk
Due Project Milestones
Overdue Project Milestones
Overdue Project PO Items
Due Project PO Items
Due Network Activities
Overdue Network Activities
Due WBS Elements
Overdue WBS Elements
Project Missing Parts
Project Open Reservations
WBS-Element Revenue Variance
WBS-Element planned cost variance
WBS-Element Exceeding Work
WBS-Element Pending Work
Project Report
WBS Element Percentage of Completion
WBS Element Earned Value
Project Earned Value
Project Percentage of Completion
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
None – the functionality is available in SAP S/4HANA, on-premise edition 1511.
2.1.13.6 Selected Project System Interfaces
Description
Simplification List for SAP S/4HANA 1610
195
Selected Project System Interface are not available in SAP S/4HANA 1511:
OpenPS for Microsoft Project for a bidirectional data exchange with Microsoft Project (the
usage of SAP Enterprise Project Connection (EPC) for a data exchange with Microsoft Project
Server could be considered instead) transaction OPENPS for the download of activities to
Palm Pilot
MPX up- and download functions including transactions CN06 and CN07 and related
functions in PS reporting transactions such as CN41 etc.
Export to Graneda and Microsoft Access (see also 1670678 - New features in SAP GUI for
Windows 7.30 )
Business Process related information
The selected interfaces listed above will not be available anymore in SAP S/4HANA 1511. Alternative
solutions such as SAP Enterprise Project Connection or leveraging PS BAPIs should be considered.
Transaction Codes not available in
SAP S/4HANA
CN06
MPX Download: Standard Network
CN07
MPX Upload: Standard Network
OPENPS
Download Activities to Palm Pilot
Required and Recommended Action(s)
Knowledge Transfer to key- and end user.
2.1.13.7 Construction Progress Report and Valuation
Description
The Construction Progress Report and Valuation function is not available in SAP S/4HANA 1511.
Business Process related information
The Construction Progress Report and Valuations functions and related transactions are not available
in SAP S/4HANA 1511.
Transaction Codes not available in /SAPPCE/PNV01
SAP S/4HANA
/SAPPCE/PNV03
/SAPPCE/PNV04
/SAPPCE/PNV05
/SAPPCE/PNV07
Create Construction Progress Report
Display Construction Progress Report
Display construction progress report
Create and Change CPR
Create and Change Remaining Plan
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
196
Knowledge Transfer to key- and end-user. A customer specific solution or a switch to SAP standard
functions should be considered.
2.1.13.8 Project System ITS Services
Description
The following ITS services in Project System are not available any longer in S/4HANA as of SAP
S/4HANA 1511:
CNW1
CNW4
SR10
WWW: Confirmation
Project Documents
Claims
Business Process related information
Selected ITS services for document search, confirmations and creation of claims are not available as
of SAP S/4HANA 1511.
Required and Recommended Action(s)
Knowledge Transfer to key- and end user.
2.1.13.9 Selected PS Business Function Capabilities
Description
Selected PS business functions and related transactions are not the target architecture anymore in
SAP S/4HANA 1511.
With SAP S/4 HANA 1511 - FPS1 the following business functions are switchable but obsolete:
OPS_PS_CI_3
LOG_XPD_EXT_1
The following PS business functions are customer-switchable in SAP S/4 HANA 1511 FPS1. The
related functions are intended to be replaced in future by improved functions and hence are not the
target architecture (Functionality available in SAP S/4HANA 1511 delivery but not considered as
future technology. Functional equivalent is not available yet.).
OPS_PS_CI_1
OPS_PS_CI_2
Simplification List for SAP S/4HANA 1610
197
The following transactions are hence categorized not to be the target architecture:
CN08CI Config. of Commercial Proj Inception
CNACLD PS ACL Deletion Program transaction
CNSKFDEF SKF defaults for project elements
Basic Information related to Business Functions
If a business function was switched ON in the Business Suite start release system, but defined as
always_off in the SAP S/4HANA, on-premise edition target release, then a system conversion is not
possible with this release. See SAP Note 2240359 - SAP S/4HANA, on-premise edition 1511: AlwaysOff Business Functions. If a business function is defined as "customer_switchable" in the target
release (SAP S/4HANA, on-premise edition 1511 FPS1), then the business function status remains
unchanged from the status on start release. Business Functions defined as obsolete cannot be
switched ON
Business Process related information
Customer having one or all of these business functions switched ON in Business Suite start release
can execute the system conversion. Customers having none of these business functions switched ON
in Business Suite start release cannot activate the obsolete business functions after the system
conversion to SAP S/4 HANA 1511.
The Business Functions OPS_PS_CI_1 and OPS_PS_CI_2 are available and selectable with SAP
S/4HANA 1511, but the related functionalities are not considered as target architecture.
Alternative standard functions should be considered.
Required and Recommended Action(s)
None
2.1.13.10 Selected Logistics Capabilities
Description
Selected PS logistics functions are not the target architecture in SAP S/4HANA (Functionality available
in SAP S/4HANA 1511 delivery but not considered as future technology. Functional equivalent is not
available yet.). However, the functions are still available in SAP S/4HANA 1511.
The following transactions are categorized not as the target architecture and are planned to be
replaced by new functions in future:
o
o
CNMM Project-Oriented Procurement
CNC4 Consistency checks for WBS
Simplification List for SAP S/4HANA 1610
198
o
CNC5 Consistency checks sales order/proj.
In addition it is also intended to provide alternative solutions for using the non-valuated project stock
and the Open Catalog Interface (OCI).
Business Process related information
No influence on business processes expected functionality still available
Required and Recommended Action(s)
None
2.1.13.11 Simplification of maintenance transactions
Description
There are currently multiple, partially redundant transactions to maintain projects in project system.
It´s the target to have one single maintenance transaction in future. The target transaction is
transaction CJ20N Project Builder. The following maintenance transactions are hence categorized not
as target architecture (Functionality available in SAP S/4HANA 1511 delivery but not considered as
future technology. Functional equivalent is available):
CJ01 Create Work Breakdown Structure
CJ02 Change Work Breakdown Structure
CJ03 Display Work Breakdown Structure
CJ06 Create Project Definition
CJ07 Change Project Definition
CJ08 Display Project Definition
CJ11 Create WBS Element
CJ12 Change WBS Element
CJ13 Display WBS Element
CJ14 Display WBS Element (From DMS)
CJ20 Structure planning
CJ2A Display structure planning
CJ2D Structure planning
OPUM Maintain Subprojects
CN19 Display Activity (From DMS)
CN20 Dsply network/act.bsc data init.scrn
CN21 Create Network
CN22 Change Network
CN23 Display Network
CJ27 Project planning board
CJ2B Change project planning board
CJ2C Display project planning board
Simplification List for SAP S/4HANA 1610
199
CN26 Display Mat.Comp/Init: Ntwk,Acty,Itm
CN26N Display Mat. Components (From DMS)
Business Process related information
Transaction CJ20N Project Builder is the strategic functionality related to project maintenance. The
currently parallel (partly redundant) transactions are still available with SAP S/4HANA 1511 but they
are not the target architecture. However, navigation e.g. from strategic reports or other strategic
transactions to the list of maintenance transactions not the target architecture will be exchanged by
navigation to the Project Builder transaction CJ20N. Customer invest (for example related custom
code or new end user knowledge transfer) need to consider this.
Required and Recommended Action(s)
It´s recommended to use single maintenance transaction CJ20N (Project Builder) instead of using
multiple project related transactions.
End user knowledge transfer required to switch from multiple transactions to single maintenance
transaction CJ20N.
2.1.13.12 Selected Project System BAPIs
Description
The Project System (PS) BAPIs referring to business objects ProjectDefinition, Network, and
WorkBreakdownStruct (as part of CN package) are not considered as the target architecture in SAP
S/4HANA 1511 (Functionality available in SAP S/4HANA 1511 delivery but not considered as future
technology. Functional equivalent available.). The functionality is still available in SAP S/4HANA 1511,
but it is recommended to use the corresponding BAPIs for business objects ProjectDefinitionPI,
NetworkPI, and WBSPI (within package CNIF_PI) instead.
Business Process related information
No influence on business processes expected functionality still available
Required and Recommended Action(s)
It is recommended to verify if it is possible to use the corresponding BAPIs for business objects
ProjectDefinitionPI, NetworkPI, and WBSPI (within package CNIF_PI).
2.1.13.13 Handling Large Projects Business Functions
Description
Simplification List for SAP S/4HANA 1610
200
Project System business functions for Handling Large Projects and related transactions are not the
target architecture anymore in SAP S/4HANA. With SAP S/4 HANA 1511 - FPS1 hence the following
business functions are switchable (to enable technical conversion) but obsolete:
OPS_PS_HLP_1
OPS_PS_HLP_2
The following transactions and related IMG activities are categorized not to be the target
architecture and cannot be used any longer with SAP S/4HANA:
PSHLP10 Project Worklist
PSHLP20 Project Editor
PSHLP30 Draft Workbench
PSHLP90 Administrator Workbench
Basic Information related to Business Functions
If a business function was switched ON in the Business Suite start release system, but defined as
always_off in the SAP S/4HANA, on-premise edition target release, then a system conversion is not
possible with this release. See SAP Note 2240359 - SAP S/4HANA, on-premise edition 1511: AlwaysOff Business Functions. If a business function is defined as "customer_switchable" in the target
release (SAP S/4HANA, on-premise edition 1511 FPS1), then the business function status remains
unchanged from the status on start release. Business Functions defined as obsolete cannot be
switched ON
Business Process related information
Customer having these business functions switched ON in Business Suite start release can execute
the system conversion. Nevertheless the functionality related to the business functions
OPS_PS_HLP_1, OPS_PS_HLP_2 are not available within SAP S/4 HANA 1511. Customers having none
of these business functions switched ON in Business Suite start release cannot activate these
business functions after the system conversion to SAP S/4 HANA 1511.
Alternative standard functions should be considered. Instead of Handling Large Projects transactions
e.g. the Project Builder transaction should be used.
Required and Recommended Action(s)
None
2.1.13.14 Navigation to Project Builder instead of special maintenance functions
Description
Simplification List for SAP S/4HANA 1610
201
There are currently multiple, partially redundant transactions to maintain projects. It´s the target to
have one single maintenance transaction in future. The target transaction is transaction CJ20N
Project Builder. See as well SAP note 2270246. With SAP S/4HANA 1511 the target for links and
references in reports, still classified as relevant for the target architecture, is going to the single
maintenance transaction CJ20N (Project Builder). For reports classified as not strategic anymore the
navigation has not been adopted.
Business Process related information
Transaction CJ20N Project Builder is the strategic functionality related to project maintenance. The
currently parallel (partly redundant) transactions are still available with SAP S/4HANA 1511 but they
are not the target architecture. Customer invest (for example related custom code or new end user
knowledge transfer) need to consider this. With SAP S/4HANA 1511 the target for links and
references in strategic reports and transactions is going to single maintenance transaction CJ20N
(Project Builder) and not longer to other project related transactions. A customer can re-enable on
project specific basis the link and reference to the old (multiple) transactions, which are still
available.
Required and Recommended Action(s)
It´s recommended to use single maintenance transaction CJ20N (Project Builder) instead of using
multiple project related transactions and accordingly the links and references from related
transactions should have CJ20N (Project Builder). End user knowledge transfer required to switch
from multiple transactions to single maintenance transaction CJ20N.
Custom Code related information
In case of custom code for special maintenance functions only, customer should consider to enable
the custom code for the Project Builder transactions
2.1.13.15 Production Resources and Tools functions for projects
Description
The current handling of Production Resources and Tools (PRT) is not the target
architecture (Functionality available in SAP S/4HANA 1511 delivery but not considered as future
technology. Functional equivalent is not available yet) in SAP S/4HANA 1511 since the Project Builder
transaction does not support PRTs. Currently no functional equivalent for Production Resources and
Tools (PRT) for projects in SAP S/4HANA 1511 exist. PRTs will not be available in the Project Builder
transaction CJ20N.
Business Process related information
No functional equivalent for Production Resources and Tools (PRT) exist in SAP S/4HANA 1511. Still
old special maintenance functions can be used for PRT handling. However, please note that special
Simplification List for SAP S/4HANA 1610
202
maintenance functions are not the target architecture and the Project Builder transaction does not
support PRTs (Functionality available in SAP S/4HANA 1511 delivery but not considered as future
technology. Functional equivalent is not available yet).
Required and Recommended Action(s)
Knowledge Transfer to key- and end user, usage of alternatives to PRTs need to be considered
2.1.13.16 Project Planning Board, Gantt-Chart, Hierarchy and Network Graphics
Description
Please be informed that graphics in Project System including Gantt charts, network graphics and
hierarchy graphics might be replaced in future by new graphic user interface patterns. The existing
graphical views hence are categorized not as the target architecture (Functionality available in SAP
S/4HANA 1511 delivery but not considered as future technology. Functional equivalent is not
available yet). Because of this also the following transactions are categorized not as the target
architecture:
CJ27 Project planning board
CJ2B Change project planning board
CJ2C Display project planning board
Business Process related information
Still the existing graphics and corresponding transactions can be used. However, the graphics might
be replaced in future by new and improved graphic user interface patterns which might not provide
exactly the same functional scope of currently existing functions.
Required and Recommended Action(s)
Knowledge Transfer to key- and end user
2.1.13.17 Current simulation functions in project system
Description
With SAP S/4HANA 1511 the current simulation functions in project system are still available but not
considered as the target architecture (Functionality available in SAP S/4HANA 1511 delivery but not
considered as future technology. Functional equivalent is not available yet). The following
transactions are hence categorized not as the target architecture:
CJV1 Create project version (simulation)
Simplification List for SAP S/4HANA 1610
203
CJV2 Change project version (simulation)
CJV3 Display Project Version (Simulation)
CJV4 Transfer project
CJV5 Delete simulation version
CJV6 Maintenance: Version administration
CJV7 Display transfer log
Business Process related information
Still the existing simulation functions can be used. However, the existing simulation functions and
related transactions are not the target architecture and might be replaced in future by other,
improved simulation capabilities which might not provide exactly the same functional scope of
currently existing functions.
2.1.13.18 Specific PS archiving transactions
Description
With SAP S/4HANA 1511 the Project system specific archiving transactions are still available, but they
are not considered as the target architecture any longer (Functionality available in SAP S/4HANA
1511 delivery but not considered as future technology. Functional equivalent is available). It is
recommended to use the central archiving transaction SARA instead. The following transactions are
categorized not as the target architecture:
CN80
Archiving project structures
CN81
PS: Archiving project - preliminary
CN82
PS: Archiving project structures
CN83
PS: Archiving project - Info System
CN84
PS: Archiving project - admin.
CN85
PS: Delete operative structures
CN99
Archiving Standard Networks
KBEA
Trsfr Price Docs: Set Del.Indicator
KBEB Trsfr Price Docs: Generate Archive
KBEC Trsfr Price Docs: Manage Archive
Business Process related information
Still the existing project specific archiving transactions can be used. However, these transactions are
not the target architecture. Going forward it is recommended to use the central archiving transaction
SARA instead.
Required and Recommended Action(s)
It is recommended to use central archiving transaction SARA instead of project system
specific transactions.
Simplification List for SAP S/4HANA 1610
204
Knowledge Transfer to key- and end-user
2.1.13.19 Project texts (PS texts)
Description
With SAP S/4HANA 1511 in Project System the Project texts (PS texts) are not considered as the
target architecture (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is not available yet). It is planned to replace
the PS texts with alternative functionality. The following transactions are hence categorized not as
the target architecture as well:
CN04
CN05
Edit PS Text Catalog
Display PS Text Catalog
Business Process related information
Still the Project texts can be used. However, this function is not the target architecture. Going
forward it is recommended to use alternative ways of document handling for projects.
2.1.13.20 Claim Management
Description
With SAP S/4HANA 1511 the Project System Claim Management is still available but not considered
as the target architecture (Functionality available in SAP S/4HANA on-premise edition 1511 delivery
but not considered as future technology. Functional equivalent is available). It is recommended to
use alternative solutions such as Project Issue and Change Management for this business
requirement. The following transactions are hence categorized not as the target architecture:
CLM1
CLM10
CLM11
CLM2
CLM3
Create Claim
Claim Overview
Claim Hierarchy
Change Claim
Display Claim
Please note that hence also the factsheet/object page Project Claim will not be available with SAP
S/4HANA 1511 (see note 2267283).
Business Process related information
Still the existing claim management functionality can be used. However, the related functions and
transactions are not the target architecture.
Simplification List for SAP S/4HANA 1610
205
Going forward it is recommended to use alternative solutions such as Project Issue and Change
Management for this business requirement. This might require also process changes as claim
management and Project Issue and Change Management partially provide different capabilities.
Required and Recommended Action(s)
It is recommended to use Project Issue and Change Management functionality and not PS claim
management for appropriate business requirement. Knowledge Transfer to key- and end-user,
evaluation of Project Issue and Change Management as alternative to PS claim management.
2.1.13.21 Selected project financial planning and control functions
Description
With SAP S/4HANA 1511 project financial planning and control functions including the Easy Cost
Planning (ECP) tool are still available but not considered as the target architecture (Functionality
available in SAP S/4HANA 1511 delivery but not considered as future technology. Functional
equivalent is not available yet.) any longer since it is planned to provide improved project costing and
project financial planning tools addressing customer needs. The following transactions are hence
categorized not as the target architecture:
CJFA Analysis of Data Trans. into PS Cash
CJFN CBM Payment Converter
CJ48 Change Payment Planning: Init.Screen
CJ49 Display Payment Planning: Init.Screen
FM48 Change Financial Budget: Initial Scn
FM49 Display Financial Budget: Init.Scrn
CJ8V Period Close for Project Selection
CJC1 Maintenance Dialog for Stat.by Per.
CJC2 Maintain Planned Status Changes
CJSG Generate WBS Element Group
CJZ1 Act. Int Calc.: Projects Coll. Proc.
CJZ2 Actual Int.Calc.: Project Indiv.Prc.
CJZ3 Plan Int.Calc.: Project Indiv.Prc.
CJZ5 Plan Int.Calc.: Project Coll.Prc.
CJZ6 Actual Int.Calc.: Indiv.CO Order Prc
CJZ7 Planned Int.Calc: Indiv.CO Ord.Proc.
CJZ8 Actual Int.Calc.: Coll.CO Order Prc.
CJZ9 Plan Int.Calc.: Coll.CO Order Prc.
CNFOWB Forecast Workbench
CJ9D Copy Plan Versions
CJ9ECP Project System: Easy Cost Planning
CJ9K Network Costing
CJ9L Forecast Costs: Individual Projects
CJ9M Forecast Costs: Coll.Project Proc.
CJ9Q Integrated Planning for Ntwks(Coll.)
Simplification List for SAP S/4HANA 1610
206
CJ9QS Integrated Planning for Ntwks (Ind.)
CNPAWB Progress Analysis Workbench
DP101 Reset Billing Plan Date
DP80 SM: Resource-Related Quotation
DP81 PS: Sales Pricing
DP82 PS: Sales Pricing Project
DP98 Resource for Billing Request
DP99A Doc.Flow Reporting - Res.-Rel. Bill.
DP99B Doc.Flow for Res.-Rel. Bill. - SD
DP99C Doc.Flow for Res.-Rel. Bill.-Service
DP60 Change Accounting Indicator in LI
DP70 Conversion of Individual Orders
RKPSANALYSE RKPSANALYSE
CJF1 Create Transfer Price Agreement
CJF2 Change Transfer Price Agreement
CJF3 Display Transfer Price Agreement
CJF4 Transfer Price Agreement List
CJG1 Enter Transfer Price Allocation
CJG3 Display Transfer Price Allocation
CJG4 Enter Trsfr Price Allocation: List
CJG5 Cancel Transfer Price Allocation
CJL2 Collective Agreement
CNPRG Network Progress
Business Process related information
No influence on business processes expected.
2.1.14 Logistics – PSS
2.1.14.1 MyApps for Product Safety and Dangerous Goods Management
Description
SAP PS&S MyApps function modules are not available within SAP S/4HANA.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
None
How to Determine Relevancy
Simplification List for SAP S/4HANA 1610
207
None
2.1.14.2 PS&S SARA Reports
Description
The creation of SARA reports is not available within SAP S/4HANA. A successor functionality is on the
roadmap for a future release.
Business Process related information
Transaction CBIHSR01 is not available in SAP S/4HANA.
2.1.14.3 Substance Volume Tracking Selection Criteria based on tables VBUK and VB
Description
In many countries regulations require that chemicals and hazardous substances must be registered if
they are purchased, imported, produced, sold, or exported in specific quantities and within a certain
period. SAP Substance Volume Tracking helps companies to comply with the relevant regulations by
recording the quantities of substances that need to be tracked. By comparing the recorded quantities
with the limit values, the system can issue a warning in good time before a limit value is exceeded. If
a limit value is exceeded, the system can also block the relevant business process. This means
companies can ensure that they stay within the quantity limits. In substance volume tracking, the
system reads logistics data from the following tables depending on the scenario:
Scenario
PUR
Scenario Category
PURCHASE_REQUISITION
Tables
EBAN
PUR
PURCHASE
EKKO, EKPO, EKET,
MKPF,
SO
SO
MSEG
VBAK, VBAP, VBEP,
VBPA,
SALES
VBUP
LIKP, LIPS, VBPA,
VBUP,
DELIVERY
IMP
PURCHASE_REQUISITION
IMP
PURCHASE
MKPF, MSEG
EBAN
EKKO, EKPO, EKET,
MKPF,
Date for Planned Quantities
EBAN-LFDAT: Delivery date of
item
EKET-EINDT: Delivery date of item
VBEP-EDATU: Schedule line date
LIKP-WADAT: Planned date of
goods movement
EBAN-LFDAT: Delivery date of
item
EKET-EINDT: Delivery date of item
MSEG
Simplification List for SAP S/4HANA 1610
208
EXP
EXP
PRO
SALES
VBAK, VBAP, VBEP,
VBPA,
VBUP
LIKP, LIPS, VBPA,
VBUP,
DELIVERY
MKPF, MSEG
AUFK, AFKO, AFPO,
RESB,
PRODUCTION
PRO
REPET_MANUFACTURING
CON
PRODUCTION
CON
REPET_MANUFACTURING
MKPF, MSEG
PLAF, RESB, MKPF,
MSEG
AUFK, AFKO, AFPO,
RESB,
MKPF, MSEG
PLAF, RESB, MKPF,
MSEG
VBEP-EDATU: Schedule line date
LIKP-WADAT: Planned date of
goods movement
AFKO-GSTRS: Scheduled start
PLAF- PSTTR: Basic start date
AFKO-GSTRS: Scheduled start
PLAF- PSTTR: Basic start date
As a result of the SAP S/4HANA data model change in Sales & Distribution, tables VBUK and VBUP are
no longer supported in this Customizing activity. Selection criteria which relate to the status of a
sales document need to be defined based on the corresponding header and item tables (VBAK, VBAP,
LIKP and LIPS). For further details of the data model change see Simplification Item in Sales &
Distribution area.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Adaption of the selection criteria for substance volume tracking as described in SAP Note 2198406.
How to Determine Relevancy
Check the selection criteria for substance volume tracking as described in SAP Note 2198406.
2.1.14.4 Simplification in Product Compliance for Discrete Industry
Description
With component extension for SAP EHS Management, customers can use the Product Compliance for
Discrete Industry (EHS-MGM-PRC) solution for managing their product safety and stewardship
Simplification List for SAP S/4HANA 1610
209
business processes. In SAP S/4HANA on-premise edition 1511 and later, some functions are not
available.
BI extraction and queries for product compliance reporting including the roles
SAP_EHSM_PRC_BI_EXTR and SAP_EHSM_PRC_BW_ANALYTICS
Compliance Assessment Workflows
Compliance Requirement Check Conflict Workflows
Automated updated of contact person information upon import from Supplier declarations
from SAP Product Stewardship Network
Business Process related information
In SAP S/4HANA on-premise edition the compliance reporting in BI is not available. For parts of the BI
reporting, the compliance explorer and the exemption explorer is a functional equivalent. If you are
using SAP Product Stewardship Network to collaborate with your suppliers, the contact person
information are not updated automatically any more in SAP S/4HANA on-premise edition. The
following compliance requirement check conflict workflow templates are not available in SAP
S/4HANA, on-premise edition. They have been replaced with a new application that allows exploring
the compliance requirement check conflicts based on native master data using CDS views.
Workflow Template / Process Control Object
00600054 - EHPRC_CHK_BA
00600049 - EHPRC_CHK_CH
00600056 - EHPRC_CHK_IM
00600069 - EHPRC_CHK_JG
00600053 - EHPRC_CHK_SV
00600068 - EHPRC_CHK_RO
Class Name / Event
CL_EHPRC_PCO_COMP_REQ_BASE
CL_EHPRC_PCO_COMP_REQ_CHROHS
CL_EHPRC_PCO_CMP_REQ_IMDS
CL_EHPRC_PCO_CMP_REQ_JIG
CL_EHPRC_PCO_COMP_REQ_SVHC
CL_EHPRC_PCO_COMP_REQ_EUROHS
The following compliance assessment workflow templates are not available in SAP S/4HANA, onpremise edition. The assessment processes for components and products have been replaced with a
new application that provides an overview of running assessments for products and components
based on native master data using CDS views.
Workflow Template / Process Control Class Name / Event
Object
00600070 - EHPRC_BMASMT
CL_EHPRC_PCO_BASMAT_ASSMNT
00600071 - EHPRC_COASMT
00600062 - EHPRC_PRASMT
CL_EHPRC_PCO_COMP_ASSMNT
CL_EHPRC_PCO_PROD_ASSMNT
Type of Assessment
Process
Basic Material
Assessment
Component Assessment
Product Assessment
Required and Recommended Action(s)
Details about the necessary activities vebore and after converting, you find in the attachment. Ensure
that you always have the latest version of the document.
Simplification List for SAP S/4HANA 1610
210
2.1.14.5 QM Interface
Description
The previous PSS QM interface is not available within SAP S/4HANA. The corresponding menu item
'QM Inspection Plan Creation' has been removed from transaction CG02 (Substance Workbench) and
CG02BD (Specification Workbench). The appropriate business requirements are covered within the
successor functionality for SAP Quality Management: Integration of Inspection Plans in EHS.
Business Process related information
Customers who are still using the previous QM interface need to start using the new functionality
within SAP QM (See SAP Help: Link). With the new QM interface, the inclusion of PS&S data into an
inspection plan is now triggered from the QM module (pull mechanism) vs the PS&S module (push
mechanism).
Required and Recommended Action(s)
Use the new QM Interface to create master inspection characteristics based on specifications.
How to Determine Relevancy
None
2.1.14.6 IUCLID5 Interface
Description
The IUCLID5 interface to exchange PS&S data between the PS&S specification database and an
IUCLID5 system was a pilot implementation. The pilot implementation was cancelled in 2011. The
corresponding functionality is not available within SAP S/4HANA.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
None
How to Determine Relevancy
None
2.1.14.7 PS&S Enterprise Search Model
Description
Simplification List for SAP S/4HANA 1610
211
The existing Enterprise Search Model for the PS&S specification data base (based on data replication)
has been replaced in SAP S/4HANA with a replication free search model. The search model and the
data replication development objects of the previous search model have been deleted. The
Enterprise Search Model for specification data can only be used via the corresponding Recipe
Development transactions.
Business Process related information
See generic Transition Worklist Item for Enterprise Search for details.
Required and Recommended Action(s)
Use the new Enterprise Search Model. In case of customer-specific enhancements of the previous
Enterprise Search Model, the enhancements have to carry over into the new replication free Search
Model (if they are still required).
2.1.14.8 Hazardous Substance Management
Description
The existing functionality SAP Hazardous Substance Management (EHS-HSM) can be used within SAP
S/4HANA, however the use of component SAP Risk Assessment (EHS-MGM-RAS) is recommended
instead (Functionality available in SAP S/4HANA delivery but not considered as future technology.
Functional equivalent is available.).
Business Process related information
Some adjustments in the SAP Easy Access menu have been made:
The menu item Hazardous Substance Management has been removed from the Product
Safety and Stewardship SAP Easy Access Menu.
The two menu items Hazardous Substance Master and Filling from Specification
Management are now located under: Logistics Product Safety and Stewardship - Product
Safety - Tools - Hazardous Substance Master.
SAP Risk Assessment provides a disjunctive functionality without any dependency on Hazardous
Substance Management.
2.1.14.9 Add-On: SAP Product and REACH Compliance (SPRC)
Description
The add-on SAP Product and REACH Compliance (SPRC) will not be supported within SAP S/4HANA.
SPRC supports process and discrete industry manufacturers in meeting the respective directives and
regulations. Both need to prove the safety of substances, products, and their uses according to the
REACH (Registration, Evaluation and Authorization of Chemicals) chemical regulation. Discrete
industry manufacturers need to provide proof of compliance with environmental directives, such as
Simplification List for SAP S/4HANA 1610
212
EU RoHS, China RoHS, JIG, and GADSL. Product Compliance Management of SAP Environment, Health
and Safety Management Extension EHSM provides compliance functionality for the needs of
the discrete industry. If you use the discrete industry solution of SPRC or Compliance for Products
(CfP), you are able to migrate to Product Compliance Management. For the process industry solution
of SPRC, no successor exists. The focus of SPRC version 2.0 was to support process and
discrete industry manufacturers to become REACH compliant by using functionalities, such as
campaign management for supply chain communication, bulk material assessment and registration
and endpoint management.
With the deadline for the last REACH registration period in 2018, the focus of customers will switch
towards functionality which supports them to remain REACH compliant. The provision of new cloudenabled solution capabilities, which take these new requirements into account, is planned within SAP
S/4HANA.
Business Process related information
No influence on business processes expected. The tools of SPRC version 2.0 will only be relevant for
process industry manufacturers until the deadline of the last REACH registration period in 2018. The
focus of customers will then switch to functionality which supports them to remain REACH
compliant. All transaction codes which were delivered with the SPRC add-on are not available within
SAP S/4HANA.
Required and Recommended Action(s)
You need to uninstall the add-on before you do a system conversion to SAP S/4HANA. Follow SAP
Note 2298456 to perform the uninstallation. If you use the discrete industry solution of SPRC or CFP,
you are able to migrate to Product Compliance Management of SAP Environment, Health and Safety
Management (EHSM), which provides functionalities for discrete industries. For details refer to
http://help.sap.com/ehs-comp or SAP Note 1489703.
2.1.14.10 Add-On: EHS Web-Interface
Description
The add-on EHS Web-Interface will not be supported with SAP S/4HANA.
Business Process related information
You are no longer able to publish your reports on the internet or intranet.
Required and Recommended Action(s)
You need to uninstall the add-on before you do a system conversion to SAP S/4HANA. Follow SAP
Note 2307624 to perform the uninstallation.
Simplification List for SAP S/4HANA 1610
213
2.1.14.11 Add-On: Genifix (Labelling solution)
Description
The add-on Genifix (labeling solution) will not be supported within SAP S/4HANA. Successor
functionality is available in SAP component SAP Global Label Management (EHS-SAF-GLM).
Business Process related information
All transaction codes which were delivered with the Genifix add-on are not available within SAP
S/4HANA.
Required and Recommended Action(s)
You can migrate to SAP Global Label Management (EHS-SAF-GLM). You need to uninstall the add-on
before you do a system conversion to SAP S/4HANA. It is not yet possible to uninstall the add-on
via the SAP Add-On Installation Tool (SAINT).
2.1.14.12 BW Extractors for Dangerous Goods Management and Specification Managemen
Description
The relevant BW extractors and data sources for Dangerous Goods Management and Specification
Management are not available within SAP S/4HANA.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
None
How to Determine Relevancy
None
2.1.14.13 PS&S Key Figures
Description
The SAP PS&S key figure functionality is not available within SAP S/4HANA.
Business Process related information
No influence on business processes expected.
Simplification List for SAP S/4HANA 1610
214
Required and Recommended Action(s)
None
How to Determine Relevancy
None
2.1.15 Logistics – Plant Maintenance
2.1.15.1 LIS in EAM
Description
Currently there is no functional equivalent for Logistics Information System (Note: If you use a
material number longer than 18 characters - see restriction note Extended Material Number in LIS:
SAP Note 2232362) in EAM within SAP S/4HANA, on-premise edition 1511 (Functionality available in
SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional
equivalent is not available yet.).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
No action required.
2.1.15.2 Download Data in MS Access out of List
Description
In most of our list in SAP GUI download to MS Access is offered. This functionality is not the target
architecture, it´s recommended to download to MS EXCEL instead (Functionality available in SAP
S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional
equivalent is available.).
Business Process related information
No influence on business processes expected.
Simplification List for SAP S/4HANA 1610
215
Required and Recommended Action(s)
No action required.
2.1.15.3 Scheduling of Maintenance Plan
Description
Mobile Asset Management functionality is not the target architecture (Functionality available in SAP
S/4HANA on-premise edition 1511 delivery but not considered as future technology. Functional
equivalent is not available yet.).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
No action required.
2.1.15.4 Mobile Asset Management (MAM)
Description
Product Mobile Asset Management (MAM) functionality is not the target architecture within SAP
S/4HANA, on-premise edition 1511. The available functional equivalent is SAP Work Manager
( Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not considered as
future technology. Functional equivalent is available. ).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
No action required.
2.1.15.5 Batch Input for Enterprise Asset Management (EAM)
Description
Simplification List for SAP S/4HANA 1610
216
Currently there is no functional equivalent for enterprise asset management (EAM) within SAP
S/4HANA, on-premise edition 1511 (Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is not available yet.).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
No action required.
2.1.15.6 Change Order and Operations
Description
Currently there is no functional equivalent for Change Order and Operations related transactions
(IW39, IW37, and IW49) within SAP S/4HANA, on-premise edition 1511. It´s recommend to use
transaction IW37n instead.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
No action required.
2.1.15.7 WebDynpro Application for Maintenance Planner (<= EhP4)
Description
Old WD Application covering Maintenance Worker, Planner, and Supervisor is not the target
architecture (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is available.).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
No action required.
Simplification List for SAP S/4HANA 1610
217
2.1.15.8 Enterprise Search in EAM and PLM
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 Enterprise Asset Management SAP EAM).
Business Process related information
With the new solution the following searches will be missing:
EAM
Document search with attached document content
Document search with linked documents Search with Classification data
PLM related
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
Required and Recommended Action(s)
No changes expected in the business process.
2.1.16 Logistics – Quality Management
2.1.16.1 Quality Management Information System (QMIS)
Description
The Quality Management Information System (QMIS) which is part of the Logistics Information
System (LIS) is not the target architecture (Functionality available in SAP S/4HANA on-premise edition
1511 delivery but not considered as future technology. Functional equivalent is not available
Simplification List for SAP S/4HANA 1610
218
yet.) anymore within SAP S/4HANA and will be replaced by corresponding new applications in the
future. This applies to evaluations for quality notifications as well as inspection lots and related data.
Business Process related information
No influence on business processes expected. Customers should just consider this when they think
about investments into their QMIS functionality. The old functionality will stay available until the new
functionality is released.
2.1.16.2 Quality Inspection Engine (QIE)
Description
The Quality Inspection Engine (QIE) which is part of EWM is not the target architecture (Functionality
available in SAP S/4HANA on-premise edition 1511 delivery but not considered as future technology.
Functional equivalent is not available yet.) within SAP S/4HANA and will be replaced by
corresponding new functions in the future.
Business Process related information
No influence on business processes yet. Customers should consider this when they use QIE for other
purposes. The old functionality will stay available until the new functionality is released.
2.1.16.3 Results Recording
Description
The functionality to create worklists for mobile devices such as PalmPilot (transaction QEH1) is not
available within SAP S/4HANA, on-premise edition 1511.
Business Process related information
As an alternative, you could use the POWL and the WebDynpro application for results recording that
is included in the PFCG role for NWBC Quality Inspector (SAP_SR_QUALITY_INSPECT_5).
Transaction not available in SAP S/4HANA
QEH1
Required and Recommended Action(s)
Knowledge transfer to key and end users
Simplification List for SAP S/4HANA 1610
219
2.1.16.4 ITS services in QM
Description
SAP Internet Transaction Server (ITS) is considered to be an old technique. Therefore the ITS services
for the Internet Application Components (IAC) in QM are not available within SAP S/4HANA, onpremise edition 1511.
Business Process related information
As alternatives, you could use the corresponding QM transactions in SAP GUI for HTML or you could
use the WebDynpro applications mentioned below, which are part of the PFCG role for NWBC
Quality Inspector (SAP_SR_QUALITY_INSPECT_5).
a) Results Recoding: WebDynpro application QI_RECORD_RESULTS_ETI_APPL
b) Quality Notifications: WebDynpro application QIMT_NOTIFICATION_APP
c) Certificates: No WebDynpro application available. However, existing QM transactions are still
available, such as QC20, QC21
Transaction
Code
QC40
Corresponding ITS
Service
QC40
QC40A
QC40A
QC42
QC42
QEW01
QEW01
QEW01V
QEW01V
QMW1
QMW1
QISR
QISR
QISRW
QISRW
Description
Package
Internet Certificate
for Delivery
Internet Certificate
for Delivery
Batch certificate on
QC
Application
Component
QM-CA-MD
QC
QM-CA-MD
QC
QM-CA-MD
Basic Data for
Certificates
Basic Data
forCertificates
Basic Data for
QM-IM
Certificates
Quality Inspection
QM-IM
Quality Inspection
QM-QN
Quality Notifications
QM
Quality Notifications
QM
Quality Notifications
WWW
Results Recording on QEWW
Web
Variant Maint.:
QEWW
Recording on Web
Create quality
QQM
notification (WWW)
Internal Service
QNWEB
Request
Internal Service
QNWEB
Request on the Web
Area
Required and Recommended Action(s)
Knowledge transfer to key and end users
Simplification List for SAP S/4HANA 1610
220
2.1.16.5 QM WEB Workplace (MiniApps) based on ITS Services
Description
SAP Internet Transaction Server (ITS) and mySAP Workplace are not available within SAP
S/4HANA. Therefore the MiniApps that are based on these techniques are not available within SAP
S/4HANA.
Business Process related information
As alternatives, you could use the corresponding QM transactions in SAP GUI for HTML or the
corresponding Web Dynpro applications, which are part of the PFCG role for NWBC Quality Inspector
(SAP_SR_QUALITY_INSPECT_5).
Transaction not
available in SAP
S/4HANA on-premise
edition 1511
IQS8WP
IQS8 - Call from Workplace/MiniApp
IQS9WP
IQS9 - Call from Workplace/MiniApp
QA32WP
QA32 - Call from Workplace/MiniApp
QE09WP
Call QE09 from Workplace
QPQA32
QM MiniApp Selection Variant
QPQGC1
QM MiniApp Selection Variant
QPQM10
QM MiniApp Selection Variant
QPQM13
QM MiniApp Selection Variant
QM10WP
QM10 - Call from Workplace/MiniApp
QM13WP
QM13 - Call from Workplace/MiniApp
QPIQS8 QM
MiniApp Selection Variant
QPIQS9 QM
MiniApp Selection Variant
WAO_QA32WP QA32 -Call from Workplace/MiniApp
WAO_QM10WP QM10 - Call from Workplace/MiniApp
WAO_QM13WP QM13 - Call from Workplace/MiniApp
WAO_QPQA32 QM
iView Selection Variant Insp.Lot
WAO_QPQM10 QM
iView Selection Variant Notificat
WAO_QPQM13 QM
iView Selection Variant Task
Required and Recommended Action(s)
Knowledge transfer to key and end users
2.1.17 Logistics - Execution Transportation
2.1.17.1 Transportation (LE-TRA)
2.1.17.1.1 Description
The Logistics Execution Transportation (LE-TRA) is not the target architecture within SAP S/4HANA,
on-premise edition 1511 (Functionality available in SAP S/4HANA on-premise edition 1511 delivery
Simplification List for SAP S/4HANA 1610
221
but not considered as future technology. Functional equivalent is available.). The (already available)
alternative functionality is Transportation Management (SAP TM).
2.1.17.1.2 Business Process related information
No influence on business processes expected on the current business processes related to the
Logistics Execution Transportation (LE-TRA). The related functionality are still available within the
SAP S/4HANA 1511.
2.1.17.1.3 Required and Recommended Action(s)
The Logistics Execution Transportation (LE-TRA is not the target architecture anymore within SAP
S/4HANA. The (already available) alternative functionality is Transportation Management (SAP TM)
and a customer could start introducing SAP TM upfront to the SAP S/4HANA installation.
2.1.18 Logistics – Warehouse Management
2.1.18.1 Warehouse Management (WM)
2.1.18.1.1 Description
The Warehouse Management (LE-WM) is not the target architecture anymore within SAP S/4HANA,
on-premise edition (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is available.). The (already available)
alternative functionality is Extended Warehouse Management (SAP EWM).
2.1.18.1.2 Business Process related information
No influence on business processes expected related to the Warehouse Management. The
functionality related to Warehouse Management (LE-WM) and the other components described
above is still available within the SAP S/4HANA architecture stack. All related functionalities can be
used in an unchanged manner.
2.1.18.1.3 Required and Recommended Action(s)
The Warehouse Management (LE-WM) and the other components described above is not the target
architecture within SAP S/4HANA. The (already available) alternative functionality is Extended
Warehouse Management (SAP EWM) and a customer could start introducing EWM upfront to the
SAP S/4HANA installation.
2.1.19 Financial – General
2.1.19.1 DATA MODEL CHANGES IN FIN
Description
Simplification List for SAP S/4HANA 1610
222
With the installation of SAP Simple Finance, on-premise edition totals and application index tables
were removed and replaced by identically-named DDL SQL views, called compatibility views. These
views are generated from DDL sources. This replacement takes place during the add-on installation
of SAP Simple Finance using SUM related data is secured into backup tables. The compatibility views
ensure database SELECTs work as before. However, write access (INSERT, UPDATE, DELETE, MODIFY)
was removed from SAP standard, or has to be removed from custom code refer to SAP note
1976487.
Original
Table
Compatibility View
(identically-named view in
DDIC)
DDL Source (for the
Backup Table (for
identically-named DDIC View) original table content)
BSAD
BSAD
BSAD_DDL
BSAD_BCK
BSAK
BSAK
BSAK_DDL
BSAK_BCK
BSAS
BSAS
BSAS_DDL
BSAS_BCK
BSID
BSID
BSID_DDL
BSID_BCK
BSIK
BSIK
BSIK_DDL
BSIK_BCK
BSIS
BSIS
BSIS_DDL
BSIS_BCK
FAGLBSAS
FAGLBSIS
FAGLBSAS
FAGLBSIS
FAGLBSAS_DDL
FAGLBSIS_DDL
FAGLBSAS_BCK
FAGLBSIS_BCK
GLT0
KNC1
GLT0
KNC1
GLT0_DDL
KNC1_DDL
GLT0_BCK
KNC1_BCK
KNC3
KNC3
KNC3_DDL
KNC3_BCK
LFC1
LFC1
LFC1_DDL
LFC1_BCK
LFC3
LFC3
LFC3_DDL
LFC3_BCK
COSP
COSS
COSP
COSS
V_COSP_DDL
V_COSS_DDL
COSP_BAK
COSS_BAK
V_FAGLFLEXT_DDL
FAGLFLEXT_BCK
FAGLFLEXT FAGLFLEXT
In SAP Simple Finance, on-premise edition add-on 2.0 and SAP S/4HANA on-premise edition 1511,
additional tables were (partially) replaced by Universal Journal (ACDOCA). The approach for
compatibility views in release 2.0 differs from 1.0 in the following ways:
Compatibility views do not have the same name as the original tables.
Instead, the database interface (DBI) redirects all related database table SELECTs to a
compatibility view, which retrieves the same data based on the new data model (ACDOCA,
and so on).
The connection between table and compatibility view is NOT created during the installation
w/ SUM
Again, write access (INSERT, UPDATE, DELETE, MODIFY) was adapted in SAP standard, or has to be
adapted in custom code refer to SAP note 1976487.
Simplification List for SAP S/4HANA 1610
223
Original
Table
DDL Source (for the
Compatibility View (view in
identically-named DDIC
DDIC for redirect)
view)
View to read the content of
the database table (w/o
redirect to compatibility
view)
ANEA
FAAV_ANEA
FAA_ANEA
FAAV_ANEA_ORI
ANEK
FAAV_ANEK
FAA_ANEK
FAAV_ANEK_ORI
ANEP
FAAV_ANEP
FAA_ANEP
FAAV_ANEP_ORI
ANLC
FAAV_ANLC
FAA_ANLC
FAAV_ANLC_ORI
ANLP
BSIM
FAAV_ANLP
V_BSIM
FAA_ANLP
BSIM_DDL
FAAV_ANLP_ORI
V_BSIM_ORI
CKMI1
V_CKMI1
V_CKMI1_DDL
V_CKMI1_ORI
COEP
V_COEP
V_COEP
V_COEP_ORI
FAGLFLEXA FGLV_FAGLFLEXA
MLCD
V_MLCD
FGL_FAGLFLEXA
V_MLCD_DDL
V_FAGLFLEXA_ORI
V_MLCD_ORI
MLCR
V_MLCR
V_MLCR_DDL
V_MLCR_ORI
MLHD
MLIT
V_MLHD
V_MLIT
V_MLHD_DDL
V_MLIT_DDL
V_MLHD_ORI
V_MLIT_ORI
MLPP
T012K
V_MLPP
V_T012K_BAM
V_MLPP_DDL
V_T012K_BAM_DDL
V_MLPP_ORI
V_T012K_MIG
T012T
V_T012T_BAM
V_T012T_DDL
V_T012T_MIG
FMGLFLEXA FGLV_FMGLFLEXA
FGL_FMGLFLEXA
V_ FMGLFLEXA _ORI
FMGLFLEXT FGLV_FMGLFLEXT
FGL_FMGLFLEXT
V_ FMGLFLEXT _ORI
PSGLFLEXA FGLV_PSGLFLEXA
PSGLFLEXT FGLV_PSGLFLEXT
FGL_PSGLFLEXA
FGL_PSGLFLEXT
-
JVGLFLEXA FGLV_JVGLFLEXA
JVGLFLEXT FGLV_JVGLFLEXT
FGL_JVGLFLEXA
FGL_JVGLFLEXT
V_ JVGLFLEXA _ORI
V_ JVGLFLEXT _ORI
ZFGL_GLSI_C<number>
-
ZFGL_GLTT_C<number>
-
ZZ<CUST>A
ZFGLV_GLSI_C<number>
*
ZZ<CUST>T
ZFGLV_GLTT_C<number>
*
Besides the database tables, some old, related DDIC database views were replaced, either by
equivalent code, a new identically-named DDL SQL compatibility view, or an automatic redirect to a
new compatibility view. For the views that have been replaced by code, custom code also needs to
be adapted refer to SAP note 1976487. Similarly, customer-owned DDIC views referencing the
database tables or views affected need to be replaced by equivalent code.
Original DDIC
database view
Obsolete
database
As of release Replaced by
table
used
Simplification List for SAP S/4HANA 1610
Compatibilit DDL Source (for the
y View
compatibility view)
224
BKPF_BSAD
BSAD
sFIN 1.0
Identicallynamed DDL
view
BKPF_BSAD BKPF_BSAD_DDL
BKPF_BSAD_ BKPF_BSAD_AEDAT_DD
AEDAT
L
BKPF_BSAD_AEDAT
BSAD
sFIN 1.0
Identicallynamed DDL
view
BKPF_BSAK
BSAK
sFIN 1.0
Identicallynamed DDL
view
BKPF_BSAK BKPF_BSAK_DDL
BKPF_BSAK_AEDAT
BSAK
sFIN 1.0
Identicallynamed DDL
view
BKPF_BSAK_
BKPF_BSAK_AED_DDL
AEDAT
BKPF_BSID
BSID
sFIN 1.0
Identicallynamed DDL
view
BKPF_BSID
BKPF_BSID_AEDAT
BSID
sFIN 1.0
Identicallynamed DDL
view
BKPF_BSID_
BKPF_BSID_AEDAT_DDL
AEDAT
BKPF_BSIK
BSIK
sFIN 1.0
BKPF_BSIK_AEDAT
BSIK
sFIN 1.0
GLT0_AEDAT
GLT0
Identicallynamed DDL
view
Identicallynamed DDL
view
BKPF_BSIK
BKPF_BSID_DDL
BKPF_BSIK_DDL
BKPF_BSIK_
BKPF_BSIK_AEDAT_DDL
AEDAT
sFIN 1.0
Identicallynamed DDL
view
GLT0_AEDA
GLT0_AEDAT_DDL
T
KNC1_AEDA
KNC1_AEDAT_DDL
T
KNC3_AEDA
KNC3_AEDAT_DDL
T
KNC1_AEDAT
KNC1
sFIN 1.0
Identicallynamed DDL
view
KNC3_AEDAT
KNC3
sFIN 1.0
Identicallynamed DDL
view
LFC1_AEDAT
LFC1
sFIN 1.0
LFC3_AEDAT
LFC3
sFIN 1.0
TXW_J_WITH
BSAK
sFIN 1.0
Identicallynamed DDL
view
V_COSP_A
COSP
sFIN 1.0
Code
V_COSS_A
COSS
sFIN 1.0
Code
Identicallynamed DDL
view
Identicallynamed DDL
view
Simplification List for SAP S/4HANA 1610
LFC1_AEDAT LFC1_AEDAT_DDL
LFC3_AEDAT LFC3_AEDAT_DDL
TXW_J_WIT
TXW_J_WITH_DDL
H
225
VB_DEBI
BSID
sFIN 1.0
Identicallynamed DDL
view
VB_DEBI
VB_DEBI_DDL
VF_BSID
VF_BSID_DDL
VF_BSID
BSID
sFIN 1.0
Identicallynamed DDL
view
VFC_DEBI
KNC1
sFIN 1.0
Identicallynamed DDL
view
VFC_DEBI
VFC_DEBI_DDL
VFC_KRED
LFC1
sFIN 1.0
Identicallynamed DDL
view
VFC_KRED
VFC_KRED_DDL
ENT2006
GLT0
sFIN 1.0
Code
ENT2163
ENT2164
KNC1
LFC1
sFIN 1.0
sFIN 1.0
Code
Code
ENT2165
KNC3
sFIN 1.0
Code
ENT2166
EPIC_V_BRS_BSAS
LFC3
BSAS
sFIN 1.0
sFIN 1.0
Code
Code
EPIC_V_BRS_BSIS
EPIC_V_BSID
BSIS
BSID
sFIN 1.0
sFIN 1.0
Code
Code
EPIC_V_BSIK
EPIC_V_CUSTOMER
BSIK
BSID
sFIN 1.0
sFIN 1.0
Code
Code
EPIC_V_VENDOR
BSIK
sFIN 1.0
Code
FMKK_BKPF_BSAK
FMKK_BKPF_BSIK
BSAK
BSIK
sFIN 1.0
sFIN 1.0
Code
Code
/GRC/V_BANK_ACCT T012
SAP Simple
Finance, on- Compatibility V_GRC_BAN V_GRC_BANK_ACCT_DD
premise
view (redirect) K_ACCT
L
edition 1503
ANEKPV
SAP Simple
Finance, on- Compatibility FAAV_ANEK
FAA_ANEKPV
premise
view (redirect) PV
edition 1503
ANEP
COPC_V_T012_SKB1 T012K
SAP Simple
Finance, on- Compatibility V_COPC_T0 V_COPC_V_T012_SKB1_
view (redirect) 12_SKB1
DDL
premise
edition 1503
COPC_V_T035D
T012K
SAP Simple
Finance, on- Compatibility V_COPC_T0
V_COPC_V_T035D_DDL
view (redirect) 35D
premise
edition 1503
COVP
COEP
SAP Simple Compatibility
V_COVP
Finance, on- view (redirect)
Simplification List for SAP S/4HANA 1610
V_COVP_DDL
226
premise
edition 1503
FAP_V_CMP_HBACC T012
SAP Simple
Finance, on- Compatibility V_FAP_CMP V_FAP_V_CMP_HBACC_
premise
view (redirect) _HBACC
DDL
edition 1503
MLREADST
MLHD
SAP Simple
Finance, on- Compatibility V_MLREADS
V_MLREADST_DDL
premise
view (redirect) T
edition 1503
MLIT
SAP Simple
Finance, on- Compatibility V_MLREPOR
V_MLREPORT_DDL
premise
view (redirect) T
edition 1503
MLHD
SAP Simple
Finance, on- Compatibility
V_MLXXV
premise
view (redirect)
edition 1503
ANEP
SAP Simple
Finance, on- Compatibility FAAV_V_AN
FAA_V_ANEPK
premise
view (redirect) EPK
edition 1503
ANEP
SAP Simple
Finance, on- Compatibility FAAV_V_AN
FAA_V_ANLAB
view (redirect) LAB
premise
edition 1503
ANLA
SAP Simple
Finance, on- Compatibility FAAV_V_AN
FAA_V_ANLSUM_1
premise
view (redirect) LSUM_1
edition 1503
ANEP
SAP Simple
Finance, on- Compatibility FAAV_V_AN
FAA_V_ANLSUM_2
premise
view (redirect) LSUM_2
edition 1503
ANLA
SAP Simple
Finance, on- Compatibility FAAV_V_AN
FAA_V_ANLSUM_5
premise
view (redirect) LSUM_5
edition 1503
MLREPORT
MLXXV
V_ANEPK
V_ANLAB
V_ANLSUM_1
V_ANLSUM_2
V_ANLSUM_5
V_MLXXV_DDL
Business Process related information
There are mandatory configuration steps in General Ledger, Asset Accounting, Account-Based CO-PA,
and Cash Management (if used).
IMG -> Migration from SAP ERP to SAP Accounting powered by SAP HANA
Simplification List for SAP S/4HANA 1610
227
2.1.19.2 REPLACED TRANSACTION CODES AND PROGRAMS IN FIN
Description
With the installation of the SAP Simple Finance on-premise edition, certain transaction codes and
programs in the application areas of AC, CO, FI, AA and FIN - compared to EhP7 for SAP ERP 6.0 have been replaced with newer transactions, programs, or WebDynpro applications. The
transactions, programs, and WebDynpro applications and its replacements that are affected are
listed in the table below.
Refer to SAP Note 1946054 for more details.
Old Functionality Type New Functionality
Type
Text
FS01
TA
FS00
TA
Create G/L Accounts
Included in Role
FS02
TA
FS00
TA
Change G/L Accounts
FS03
TA
FS00
TA
Display G/L Accounts
KP06
TA
FCOM_IP_CC_COSTELEM01
WEBDYN
Change Cost and Activity Inputs
SAP_SFIN_ACC_PLANNING
KP07
TA
FCOM_IP_CC_COSTELEM01
WEBDYN
Display Cost and Activity Inputs
SAP_SFIN_ACC_PLANNING
KP65
TA
FCOM_IP_CC_COSTELEM01
WEBDYN
Create Cost Planning Layout
SAP_SFIN_ACC_PLANNING
KP66
TA
FCOM_IP_CC_COSTELEM01
WEBDYN
Change Cost Planning Layout
SAP_SFIN_ACC_PLANNING
KP67
TA
FCOM_IP_CC_COSTELEM01
WEBDYN
Display Cost Planning Layout
SAP_SFIN_ACC_PLANNING
CJ40
TA
FCOM_IP_PROJ_OVERALL01
WEBDYN
Change Project Plan
SAP_SFIN_ACC_PLANNING
CJ41
TA
FCOM_IP_PROJ_OVERALL01
WEBDYN
Display Project Plan
SAP_SFIN_ACC_PLANNING
CJ42
TA
FCOM_IP_PROJ_OVERALL01
WEBDYN
Change Project Revenues
SAP_SFIN_ACC_PLANNING
CJ43
TA
FCOM_IP_PROJ_OVERALL01
WEBDYN
Display Project Revenues
SAP_SFIN_ACC_PLANNING
CJR2
TA
FCOM_IP_PROJ_COSTELEM01 WEBDYN
PS: Change plan CElem/Activ. input
SAP_SFIN_ACC_PLANNING
CJR3
TA
FCOM_IP_PROJ_COSTELEM01 WEBDYN
PS: Display plan CElem/Activ. input
SAP_SFIN_ACC_PLANNING
SAP_SFIN_ACC_PLANNING
CJR4
TA
FCOM_IP_PROJ_COSTELEM01 WEBDYN
PS: Change plan primary cost
element
CJR5
TA
FCOM_IP_PROJ_COSTELEM01 WEBDYN
PS: Display plan primary cost elem.
SAP_SFIN_ACC_PLANNING
CJR6
TA
FCOM_IP_PROJ_COSTELEM01 WEBDYN
PS: Change activity input planning
SAP_SFIN_ACC_PLANNING
SAP_SFIN_ACC_PLANNING
KPF6
TA
FCOM_IP_ORD_COSTELEM01
WEBDYN
Change CElem/Activity Input
Planning
KPF7
TA
FCOM_IP_ORD_COSTELEM01
WEBDYN
Display CElem./Acty Input Planning
SAP_SFIN_ACC_PLANNING
KO14
TA
FCOM_IP_ORD_COSTELEM01
WEBDYN
Copy Planing for Internal Orders
SAP_SFIN_ACC_PLANNING
KPG7
TA
FCOM_IP_ORD_COSTELEM01
WEBDYN
Display Cost Planning Layout
SAP_SFIN_ACC_PLANNING
CK11
TA
CK11N
TA
Create Product Cost Estimate
CK13
TA
CK13N
TA
Display Product Cost Estimate
CK41
TA
CK40N
TA
Create Costing Run
CK42
TA
CK40N
TA
Change Costing Run
CK43
TA
CK40N
TA
Display Costing Run
CK60
TA
CK40N
TA
Preselection for Material/Plant
CK62
TA
CK40N
TA
Find Structure: BOM Explosion
CK64
TA
CK40N
TA
Run: Cost Estimate of Objects
CK66
TA
CK40N
TA
Mark Run for Release
CK68
TA
CK40N
TA
Release Costing Run
CK74
TA
CK74N
TA
Create Additive Costs
Simplification List for SAP S/4HANA 1610
228
KB11
TA
KB11N
TA
Enter Reposting of Primary Costs
KB21
TA
KB21N
TA
Enter Activity Allocation
KB31
TA
KB31N
TA
Enter Statistical Key Figures
KB33
TA
KB33N
TA
Display Statistical Key Figures
KB34
TA
KB34N
TA
Reverse Statistical Key Figures
KB51
TA
KB51N
TA
Enter Activity Posting
KE21
TA
KE21N
TA
Create CO-PA line item
KE23
TA
KE24
TA
Display CO-PA line item
KKE1
TA
CKUC
TA
Add Base Planning Object
KKE2
TA
CKUC
TA
Change Base Planning Object
KKE3
TA
CKUC
TA
Display Base Planning Object
KKEC
TA
CKUC
TA
Compare Base Object - Unit Cost Est
KKED
TA
CKUC
TA
BOM for Base Planning Objects
KKB4
TA
CKUC
TA
Itemization for Base Planning Obj.
KKBF
TA
KKR0
TA
Order Selection (Classification)
KKPHIE
TA
CKMDUVMAT/CKMDUVACT
(Distribution)
TA
Cost Object Hierarchy
KKP2
TA
CKMDUVMAT/CKMDUVACT
(Distribution)
TA
Change Hierarchy Master Record
KKP4
TA
CKMDUVMAT/CKMDUVACT
(Distribution)
TA
Display Cost Object Hierarchy
KKP6
TA
CKMDUVMAT/CKMDUVACT
(Distribution)
TA
Cost Object: Analysis
KKPX
TA
CKMDUVMAT/CKMDUVACT
(Distribution)
TA
Actual Cost Distribution: Cost Obj.
KKPY
Ta
CKMDUVMAT/CKMDUVACT
(Distribution)
TA
Actual Cost Distribution: Cost Obj.
RFDOPO10
PROG RFDEPL00
PROG
F.24
TA
RFINTITAR/RFINTITAP
PROG
A/R: Interest for Days Overdue
F.2A
TA
RFINTITAR/RFINTITAP
PROG
A/R Overdue Int.: Post (Without OI)
F.2B
TA
RFINTITAR/RFINTITAP
PROG
A/R Overdue Int.: Post (with OI)
F.2C
TA
RFINTITAR/RFINTITAP
PROG
Calc.cust.int.on arr.: w/o postings
F.4A
TA
RFINTITAR/RFINTITAP
PROG
Calc.vend.int.on arr.: Post (w/o OI)
F.4B
TA
RFINTITAR/RFINTITAP
PROG
Calc.vend.int.on arr.: Post(with OI)
F.4C
TA
RFINTITAR/RFINTITAP
PROG
Calc.vend.int.on arr.: w/o postings
FA39
TA
RFINTITAR/RFINTITAP
PROG
List of Customer Open Items
F.47
TA
RFINTITAR/RFINTITAP
PROG
Vendors: calc.of interest on arrears
RFFOD__L
PROG PMW
Payment Medium Germany - Pmts
in Ger.For.Tr.Regs (Z1 Form)/Foreign
DME
RFFOD__S
PROG PMW
International Payment Medium Check (without check management)
RFFOUS_T
PROG PMW
Payment Medium USA Transfers/Bank Direct Debits in ACH
Format
RFFOM200
PROG PMW
International Payment Medium SWIFT Format MT200
RFFOM202
PROG PMW
International Payment Medium SWIFT Format MT202
RFFOM210
PROG PMW
International Payment Medium SWIFT Format MT210
RAGITT01
PROG S_ALR_87011990
TRAN
Asset History Sheet
FAGL_FC_VAL
TA
TRAN
Foreign Currency Valuation
FAGL_FCV
Simplification List for SAP S/4HANA 1610
229
S_PL0_86000030 TA
FIS_FPM_GRID_GLACC_BAL
WEBDYN
G/L Account Balances
SAP_SFIN_ACC_CLOSING
S_PCO_36000218 TA
FCOM_FIS_AR_OVP
WEBDYN
Receivables Segment
SAP_SFIN_ACC_CLOSING
S_PCO_36000219 TA
FCOM_FIS_AP_OVP
WEBDYN
Payables Segment
SAP_SFIN_ACC_CLOSING
S_ALR_87012326 TA
FCOM_FIS_GLACCOUNT_OVP
WEBDYN
Chart of Accounts
SAP_SFIN_ACC_CLOSING
S_E38_98000088 TA
Profit Center Group:
Plan/Actual/Dif
FIORI
Profit Center - Plan/Actual (FioriID: F0926;
Query: /ERP/SFIN_M01_Q2701)
S_E38_98000089 TA
Profit Center Group:
Plan/Plan/Actual
FIORI
Profit-Center - Plan/Actual current
year (Fiori-ID: F0932;
Query: /ERP/SFIN_M01_Q2702)
S_AC0_52000887 TA
Receivables: Profit Center
WEBDYN
Receivables Profit Center
SAP_SFIN_ACC_CLOSING
S_AC0_52000888 TA
Payables: Profit Center
WEBDYN
Payables Profit center
SAP_SFIN_ACC_CLOSING
S_ALR_87100992 TA
Account Assignment Manual
no replacement
2.1.20 Financial – General Ledger
2.1.20.1 GENERAL LEDGER
Description
General Ledger in S/4H is based in the Universal Journal; the line items are stored in the new
database table ACDOCA, optimized to SAP HANA. You can migrate Ledgers of New General Ledger of
the Business Suite or the Classic General Ledger GL to the Universal Journal in S/4H. Please note, that
the number of Ledgers and the configuration of its currency will stay; it is not possible to introduce
new ledgers or new currencies during the migration to S/4H. If Classic General Ledger was used, the
ledger '00' is migrated to the new leading ledger '0L' of the universal journal.
As Controlling is now part of the Universal Journal as well, now all CO internal actual postings are
visible in General Ledger as well. The secondary cost elements are part of the chart of accounts.
There is no longer a need for Co realtime integration for transfer of secondary CO postings to NewGL
or the Reconciliation Ledger of Classic GL. It is not possible to introduce new currencies in GL during
the migration to S/4H. The order (resp. technical fieldnames in table ACDOCA) of the currencies
might change during the migration from Classic or New GL, as the the currency type of the
controlling are will determine the second currency (fieldname KSL), but the compatibility view for
classic or New GL garantuee that the reporting based on these structures shows the same result as
before.
Required and Recommended Action(s)
Mandatory application configuration steps related to General Ledger.
IMG -> Preparation and Migration of Customizing for the General Ledger
The step "Migrate General Customizing" migrates all important customizing around ledgers,
currencies and CO integration. It is important to carry out this step before manual changes are done
in the img activities below this activity.
Simplification List for SAP S/4HANA 1610
230
Therefore we recommend to go though all activites of "Preparation and Migration of Customizing for
the General Ledger" in its sequence in the UI.
Please use the consistency check (Execute Consistency Check of General Ledger Settings, tx
FINS_CUST_CONS_CHK) and clean up all inconsistencies prior to the migration of tranactional data. If
the consistency check raises messages for company codes, which are not used productively, you can
exclude these by activating the flag "Template" in view V_001_TEMPLATE.
2.1.20.2 SAP INVOICE AND GOODS RECEIPT RECONCILIATION
Description
"SAP HANA Live" provides reporting capabilities for Business Suite and Suite on HANA customers. A
strategic decision was taken to switch the technology from Calculation Views to CDS Views with SAP
S/4HANA. Reporting scenarios built with the SAP HANA Live content, such as the "Goods Receipt
Invoice Receipt Reconciliation Monitor" in Business Suite, Suite on HANA, or Simple Finance
installations have to be rebuilt manually with CDS Views in SAP S/4HANA. With SAP Invoice and
Goods Receipt Reconciliation (part of the HANA License), every Business Suite, SoH, or Simple
Finance Customer could organize the processing of GR/R differences. This functionality is not
available for SAP S/4HANA, on-premise edition 1511. The transactions and apps to process GR/IR
differences such as MR11 remain available, only the monitoring and organization capabilities added
by SAP Invoice and Goods Receipt Reconciliation are no longer available.
Business Process related information
Customers traditionally use Microsoft Excel sheets and other reporting means to monitor and
organize the GR/IR account. With SAP S/4HANA, they have to revert to these methods. Monitoring of
GR/IR Account needs to be organized by the customer
2.1.20.3 SAP HANA ODP ON HANA CALC VIEW-BASED REPORTING
Description
With Simple Finance 10, one reporting option was to use Embedded BW functionality based on
ODPs, which in turn use Calculation Views for real time data access. A strategic decision was taken to
switch the technology from Calculation Views to CDS Views with SAP S/4HANA Reporting scenarios
built with these ODPs. Simple Finance installations 1.0 or 1503 have to be rebuilt manually with CDS
Views in SAP S/4HANA and Simple Finance 1602 SP 1602.
Business Process related information
It should be possible to rebuild all existing reporting scenarios with CDS Views.
Simplification List for SAP S/4HANA 1610
231
Required and Recommended Action(s)
If such ODPs are used, time and resources should be planned for migration to CDS Views.
Customers will have to rebuild the reporting scenarios using CDS Views. End users will have to redo
personalization and variants of reports
2.1.20.4 Closing Cockpit with S/4 HANA OP
Task: Check if the customer uses any of the transactions CLOCO, CLOCOC, CLOCOS and CLOCOT.
Procedure: Use transaction ST03N to list transaction codes used in the system in the past.
Rating:
If at least one transaction codes has been used -> YELLOW
If none of the transaction codes has been used -> GREEN
Description:
The functionality of the standard Closing cockpit is not not available in SAP S/4 HANA 1511, 1610 or
subsequent release. Thus transaction codes CLOCO, CLOCOC, CLOCOS and CLOCOT are not supported
for S/4 HANA OP.
Business Process related information
Consider to use the Add-On Financials Closing Cockpit 2.0 instead.
2.1.20.5 Currencies in Universal Journal
Situation in ECC:
In the Business Suite (ECC) there used to be up to 3 parallel currencies in FI (table T001A / tx
OB22) and 2 parallel currencies in CO (TKA01 / tx OKKP): CO area currency and object
currency.
The currencies of non leading ledgers in NewGL (T882G) were a subset of the currencies in
the leading ledger (T001A).
One of the CO currencies needed to be the local currency (CT 10), but it was not necessary
that the other currency in CO was also configured in FI.
Simplification List for SAP S/4HANA 1610
232
Situation in S/4H:
With the universal journal and the common line item table ACDOCA for FI and CO, there is also a
central currency configuration for the universal journal. As the currency configuration depends on
the universal journal ledgers, there is a combined view cluster for ledgers and currencies, tx
FINSC_LEDGER.
IMG menu path: Financial Accounting( New ) - Financial Accounting Global Settings (New) - Ledgers Ledger - Define Settings for Ledgers and Currency Types.
Overview on amounts fields of the Universal Journal (as of S/4H 1610 and S/4H Finance 1605)
ACDOCA
Fieldname
Description
WSL
Amount in Transaction
Currency (Document
Currency)
Original currency of the transaction, not contained in
balances, as it might happen that different currencies cannot
be aggregated; corresponds to BSEG-WRBTR.
TSL
Amount converted to the currency of the G/L account, in
Amount in Balance Transaction
order to allow aggregation on G/L account level; corresponds
Currency
to BSEG-WRBTR.
HSL
Currency of the company code; corresponds to BSEG-DMBETR
Amount in Company
in FI and object currency in CO (except co area currency type
Code Currency (Local Currency)
is local currency)
KSL
Amount in Global Currency
Currency type configured in the controlling area (TKA01-CTYP)
OSL
Amount in Freely Defined
Currency 1
Currency configured per ledger and company code in tx
finsc_ledger
VSL
Amount in Freely Defined
Currency 2
Currency configured per ledger and company code in tx
finsc_ledger
BSL
Amount in Freely Defined
Currency 3
Currency configured per ledger and company code in tx
finsc_ledger
CSL
Amount in Freely Defined
Currency 4
Currency configured per ledger and company code in tx
finsc_ledger
DSL
Amount in Freely Defined
Currency 5
Currency configured per ledger and company code in tx
finsc_ledger
Simplification List for SAP S/4HANA 1610
233
ESL
Amount in Freely Defined
Currency 6
Currency configured per ledger and company code in tx
finsc_ledger
FSL
Amount in Freely Defined
Currency 7
Currency configured per ledger and company code in tx
finsc_ledger
GSL
Amount in Freely Defined
Currency 8
Currency configured per ledger and company code in tx
finsc_ledger
CO_OSL
Amount in Object currency of
CO
Object currency of CO, only if it is really the object currency
(70)
The second and third parallel currencies of FI (BSEG-DMB2 or BSEG-DMBE3) correspond to 2
amount fields of KSL - GSL according to configuration in tx FINSC_LEDGER.
Table BSEG is not extended and still contains only 3 parallel currencies. Our goal is to implement full
process integration of all currencies fields in all processes in accounting.
Overview on supported processes for currency fields
Our goal is to implement full process integration of all currency fields in all processes in accounting.
With S/4H 1610 (or S/4H Finance 1605) we achieved the following coverage:
HSL KSL OSL VSL BSL CSL DSL ESL FSL GSL
Example configuration
Universal Journal (ACDOCA)
10
BSEG and Fixed Asset Accountning
10
Material Ledger
10
Controlling
10
30 40
50
60 Z1
Z2
Z3 Z4 Z5
30 40
30 40
30
Supported Processes (for example config.)
Realtime currency conversion
X
X
X
X
X
X
X
X
X
X
Balance zero per journal entry
X
X
X
X
X
X
X
X
X
X
Open item management (FI-AP, FI-AR, FI-GL) X
X
X
X
X
X
X
X
X
X
Simplification List for SAP S/4HANA 1610
234
Regrouping
X
X
X
1
1
1
1
1
1
1
GL and CO Allocations
X
X
X
X
X
X
X
X
X
X
Fixed Asset Accounting
X
X
X
1
1
1
1
1
1
1
Material Ledger
X
X
X
1
1
1
1
1
1
1
CO settlement
X
X
1
1
1
1
1
1
1
1
CO reposting
X
X
1
1
1
1
1
1
1
1
This means that all journal entry items are converted in the accounting interface for all configured
currencies, regardless of the source where the business transaction originates from. In the
accounting interface the journal entry is converted according to the conversion settings in tx
FINSC_LEDGER (exchange rate type, ....), and balance zero per journal entry is guaranteed. Some
processes require more that a mere document wise currency conversion with the current rate. These
processes require that the amounts are converted with rates of the historical data being processed.
This is not yet supported for all processes. We achieved this for open item management in FI-AP, FIAR, and FI-GL or for CO and GL allocations, but not yet for Fixed Asset depreciations or CO
settlements. As a fallback the amounts are converted with the current exchange rate. In such a case
there might remain a difference caused by rounding effects or different exchange rates for the
amount fields which are marked with '1' in the above table.
Usage of new currencies
New Installations
You can configure the new currencies in the universal journal.
Please carefully consider which currencies are integrated with BSEG, FI-AA, CO, ML, FI-AA,
and which is generically converted.
Migration of Customer Installations
Migration from ERP, SFIN 1503 or S/4H 1511
Old currency configuration is migrated to universal journal without changes of the used
currencies.
S/4H Migration is not able to introduce new currencies.
ERP Installations using transfer pricing make use of the new currency fields, as
all currencies/valuations combinations are migrated to the same ledger.
Usage of additional currencies is not possible without a conversion project. You must not
simply configure additional currencies, are the existing data does not contain the new
currencies, and some open processes would not work properly, if the currency configuration
was changed.
Simplification List for SAP S/4HANA 1610
235
Currency configuration in previous S/4H releases
In S/4H 1511 there were only 2 freely defined currencies (WSL, TSL, HSL, KSL, OSL, VSL, FSL) . There
was no realtime conversion available for the customer defined currency types. Foreign currency
valuation could be used as a substitute for the missing realtime conversion. In SFIN 1503 there
are amounts fields (WSL, TSL, HSL, KSL, OSL, VSL) to cover the CO and FI amount fields of ECC.
2.1.21 Financials - Accounts Payable/Accounts Receivable
2.1.21.1 SAP Working Capital Analytics/DSO and DPO
Description
With SAP Working Capital Analytics, an innovative means of analyzing DSO and DPO was provided to
every Business Suite, SoH, or Simple Finance Customer (part of the HANA License). This functionality
is not available within SAP S/4HANA. Alternative reports for DSO and DPO analysis are available,
covering the most important aspects of DSO and DPO analysis.
Business Process related information
DSO and DPO Analysis have to move to the new reports.
Required and Recommended Action(s)
DSO and DPO Analysis have to move to the new reports.
2.1.21.2 Integration with FSCM Biller Direct (FI-AR)
Description
With the integration of SAP Accounts Receivable (FI-AR) with FSCM Biller Direct it is possible to offer
to end-customers the convenience of receiving invoices, viewing account status, and making
payments online as a self-service. The functionality is not considered as the target architecture. The
Customer can still continue to use the functionality to make the system conversion to SAP S/4HANA,
on-premise edition 1511 less disruptive (Functionality available in SAP S/4HANA on-premise edition
1511 delivery but not considered as future technology. Functional equivalent is not available yet.).
Business Process related information
The functionality integration of SAP Accounts Receivable (FI-AR) with FSCM Biller Direct is not the
target architecture, but still available and can be used within SAP S/4HANA, on-premise edition 1511.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
236
None
2.1.21.3 Integration with FSCM Biller Direct (FI-AP)
Description
With the integration of SAP Accounts Payable (FI-AP) with FSCM Biller Direct it is possible to offer
to end-vendors the convenience of uploading invoices, monitor the corresponding account
movements online as a self-service. The functionality is not considered as the target architecture.
The Customer can still continue to use the functionality to make the system conversion to SAP
S/4HANA, on-premise edition 1511 less disruptive (Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional equivalent is not
available yet.).
Business Process related information
The functionality integration of SAP Accounts Payable (FI-AP) with FSCM Biller Direct is not the target
architecture, but still available and can be used within SAP S/4HANA, on-premise edition 1511.
Required and Recommended Action(s)
None
2.1.22 Financial - Asset Accounting
2.1.22.1 DATA STRUCTURE CHANGES IN ASSET ACCOUNTING
Description
Actual items
Actual data of ANEK, ANEP, ANEA, ANLP, ANLC is now stored in table ACDOCA. ANEK data is
stored in BKPF.
Compatibility views FAAV_<TABLENAME> (for example, FAAV_ANEK) are provided in order
to reproduce the old structures.
Access to old data in tables still possible via the views FAAV_<TABLENAME>_ORI (for
example, FAAV_ANEA_ORI)
Non-actual items
Statistical data (for example, for tax purposes) previously stored in ANEP, ANEA, ANLP, ANLC
is now stored in table FAAT_DOC_IT
Plan data previously stored in ANLP and ANLC is now stored in FAAT_PLAN_VALUES
Simplification List for SAP S/4HANA 1610
237
2.1.22.2 ASSET ACCOUNTING
Description
Classic Asset Accounting is mostly transformed automatically into the New Asset Accounting.
Required and Recommended Action(s)
Execute mandatory application configuration steps related to Asset Accounting.
IMG -> Preparations and Migration of Customizing for Asset Accounting
2.1.22.3 INTEGRATION TO LEASE ACCOUNTING ENGINE (LAE)
Description
If you want to use new Asset Accounting, you are not allowed to use Integration to LAE
(Lease Accounting Engine).
For more information, see SAP Help portal at http://help.sap.com/sfin200 -> Application
Help: SAP ERP Central Component -> Accounting ->
SAP Simple Finance, on-premise edition -> Migration to SAP Accounting powered by SAP
HANA -> Migration to New Asset Accounting
2.1.22.4 JOINT VENTURE ACCOUNTING (JVA)
Description
With SAP S/4HANA, on-premise edition 1511 (or SAP S/4HANA Finance Edition 1503 SPS2, or higher
releases of this add-on), Asset Management transfers in Joint Venture Acccounting are no longer
supported. This comprises the following transactions:
GJT1 - Asset to WiP
GJT2 - Asset to asset
GJT3 - Asset retirement
GJT4 - Asset sale
GJT5 - WIP to WIP
GJT6 - WIP to Asset
GJT0 - Reverse.
For more information (for example, on business processes and recommended workarounds), please
refer to SAP Note 2137314 - Joint Venture Accounting with SAP Simple Finance powered by SAP
HANA and the attachment in that Note.
Simplification List for SAP S/4HANA 1610
238
2.1.22.5 SELECTED BUSINESS FUNCTIONS IN FINANCIAL ACCOUNTING (FI-GL AND FI-AA)
Description
Selected business functions in Financial Accounting are not the target architecture in SAP S/4 HANA
1511:
The usage of the following Financial Accounting business functions are not the target
architecture in SAP S/4 HANA. With SAP S/4 HANA 1511 FPS2 they are changed to customerswitchable and obsolete in SAP S/4 HANA:
o FIN_AA_CI_1:
FI-AA, Asset Accounting.
o FIN_GL_REORG_1: FI-GL (new), Profitcenter Reorganization and Segmentreporting
o FIN_GL_REORG_SEG: FI-GL (new), Segment Reorganization
Basic Information related to Business Functions
If a business function was switched ON in the Business Suite start release system, but defined as
always_off in the SAP S/4HANA, on-premise edition target release, then a system conversion is not
possible with this release. See SAP Note 2240359 - SAP S/4HANA, on-premise edition 1511: AlwaysOff Business Functions. If a business function is defined as "customer_switchable" in the target
release (SAP S/4HANA, on-premise edition 1511), then the business function status remains
unchanged from the status on start release. Business Functions defined as obsolete cannot be
switched ON
Business Process related information
As of support pack FPS 2, Customer having one or all of these business functions switched ON in
Business Suite start release can execute the system conversion. Nevertheless the functionality
related to business functions FIN_GL_REORG_1 and FIN_GL_REORG_SEG is not available and not
supported within SAP S/4 HANA, on-premise edition 1511. Functionality related to business function
FIN_AA_CI_1 is part of the standard and active independent of the business function state.
Customers having none of these business functions switched ON in Business Suite start release
cannot activate these business functions after the system conversion to SAP S/4 HANA, on-premise
edition 1511.
2.1.23 Financial - Cash Management
2.1.23.1 CASH MANAGEMENT - GENERAL
Description
Simplification List for SAP S/4HANA 1610
239
Once customers have installed SAP S/4HANA, SAP Cash Management is the only compatible cash
management product to be used. The classic Cash and Liquidity Management (Cash Management
and Liquidity Planner) is not officially supported in SAP S/4HANA. An SAP Business Suite customer
using classic Cash and Liquidity Management needs to activate the new SAP Cash Management after
converting to SAP S/4HANA.
Comparison of Functional Scope
The following table summarizes the differences between the classic Cash and Liquidity Management
(Cash Management and Liquidity Planner) and SAP Cash Management.
Classic Cash and
SAP Cash Management, delivered
Liquidity Management
with SAP S/4HANA 1511
Banks / Bank
Accounts
Create Bank:
FI01
Change Bank:
FI02
Display Bank:
FI03
House Bank /
House Bank
Account: FI12
Business
Partner (Role
TR0703): BP
SAP Cash Management,
delivered with SAP S/4HANA
1610 (Delta to 1511)
The following transaction codes are
replaced by the new Fiori app
Manage Banks, which can be
accessed from the Fiori Launchpad.
Create Bank: FI01
Change Bank: FI02
Display Bank: FI03
Bank Account Management (BAM)
Bank hierarchy based on
bank business partners
Free-style bank account
groups allow ad-hoc watch
for several bank accounts.
Fuzzy search for bank
accounts
Attachments
The transaction FI12 House
Bank / House Bank Account
is no longer supported.
Instead, you use the
following apps via the Fiori
Launchpad to manage
house banks and house
bank accounts:
o Define house
banks: Use
the Fiori app
Manage Banks
o Define house bank
accounts: You can
do so in the Fiori
Simplification List for SAP S/4HANA 1610
Support centralized bank
account management that
bank accounts managemed by
BAM could be replicated via
iDoc to other systems on
Simple Finance 1503,
S/4HANA Finance 1605+,
S/4HANA OP 1610+, SAP ERP
6.0 EhP6+.
240
app Manage Bank
Accounts by
editing the bank
account master
data, on the
Connectivity Path
tab.
o House bank and
house bank
accounts
are longer
configuration
data, instead they
are maintained as
master data.
Database table T012K is
redirected to the new BAM
tables.
Bank Account Management Lite
(BAM Lite):
A basic version of Bank Account
Management is provided for
customers without the license of
SAP Cash Management. It provices:
Attributes include account
holder, internal contact
persons, and house bank
account related settings on
bank accounts.
No workflow-based bank
account processes.
The transaction FI12 House
Bank / House Bank Account
is no longer supported.
Instead, you use the
following apps via the Fiori
Launchpad to manage
house banks and house
bank accounts:
o Define house
banks: Use
the Fiori app
Manage Banks
o Define house bank
accounts: You can
do so in the Fiori
app Manage Bank
Simplification List for SAP S/4HANA 1610
241
Cash Position /
Liquidity
Cash Position: FF7A
Liquidity Forecast: FF7B
Forecast
Data Integration:
Bank statement
accounting
documents
Payment accounting
documents
AR/AP accounting
documents
Memo records
Purchase orders
Sales orders
TRM
CML
FI-CA
Real-Estate
Public Sector
Accounts by
editing the bank
account master
data, on the
Connectivity Path
tab.
o House bank and
house bank
accounts
are longer
configuration
data, instead they
are maintained as
master data.
For information on the
differences between BAM
and BAM Lite, see SAP note
2165520.
Cash Position:
Use app Cash Position to
check high-level KPIs.
Use app Cash Position
Details to display
detailed positions on
bank accounts.
Liquidity Forecast:
Use SAP BusinessObjects Analysis,
edition for Microsoft Office (AO)
or transaction code RSRT to open Liquidity Forecast:
the BW queries for liquidity
forecast.
Fiori app Liquidity
Forecast
Data Integration:
Liquidity Forecast Detail
Bank statements
Bank statement
Accounting documents
Payment accounting
documents
AR/AP accounting
documents
Memo records
TRM
CML
FI-CA
Not integrated: Industryspecific data sources,
Simplification List for SAP S/4HANA 1610
242
sales orders, purchase
ordersï¼ fund, grant.
Memo Record
Payment (F110,
F111)
Create memo records: FF63 and FF65 are supported with
cash management accounts
FF63
Display memo records replaced by house banks and
house bank accounts.
List: FF65
F110
F111
Liquidity Planner Plan part:
BPC or BW-IP set up in
a separate system.
ETL for master data
and transactional data
is necessary.
F110 and F111 are supported as
before.
Plan part:
Actual part:
Actual Cash Flow
Report:FLQREP
Configuration:
Embedded Liquidity Plan
with BPC/PAK (Planning
Application Kit) and
Design Studio UI.
No ETL is needed.
Automated liquidity
forecast is integrated.
Actual part:
Account assignment
through Query and
Query Sequence
Actual part:
Old transaction is no
longer supported.
Actual Cash Flow,
You can use SAP
BusinessObjects
Cash Flow Detail
Analysis, edition for
Analysis
Microsoft Office (AO) or
transaction code RSRT to
show the integrated
actual cash flow
information.
Configuration:
Cash
Concentration
Create: FF73
Access with Variant:
FF74
Print Confirmations:
FF.8
Post: FF.9
Account assignment
through Query and
Query Sequence
Cash Concentration can work
based on the new Bank Account
Management (BAM) accounts in
the Fiori app Manage Bank
Accounts.
Cash pools can be defined by
creating bank account groups in
BAM applications directly.
Simplification List for SAP S/4HANA 1610
243
Distributed Cash
Retrieve remote Liquidity Planner
Load remote Cash Position and actual data and cash summary
Liquidity Forecast data through data of classic cash into the One
IDOC.
Exposure of S/4 HANA Cash
Management.
Business Process Related Information
Transactions not available
in SAP S/4HANA
FF$3
FF$4
FF$5
FF$6
FF$7
FF$A
FF$B
FF$C
FF$D
FF$L
FF$S
FF$X
FF.8
FF.9
FF.D
FF/1
FF/8
FF:1
FF-3
FF-4
FF-5
FF-6
FF69
FF70
FF71
FF72
FF7A
FF7B
FFTL
FFZK
FLQAB
FLQAC
Simplification List for SAP S/4HANA 1610
244
FLQAD
FLQAF
FLQAL
FLQAM
FLQAM_TP
FLQC10
FLQC12
FLQC13
FLQC13F
FLQC1A
FLQC2
FLQC20
Required and Recommended Actions
With the use of SAP S/4HANA, the old transactions of maintaining house bank accounts are
no longer supported. Instead, you manage your house bank accounts in the new bank
account master data, using either the Bank Account Management Lite or the full version of
Bank Account Management (with SAP Cash Management). As a result, before you go live
with SAP S/4HANA, you must migrate house bank accounts if there are any.
All the apps must be accessed from the Fiori Launchpad.
Customers who were using the full SAP Cash Management and are upgrading to SAP
S/4HANA 1610 from Simple Finance 1503, S/4HANA Finance 1605 and S/4HANA OP 1511,
should configure the customizing activity Define Basic Settings under "Financial Supply Chain
Management"->"Cash and Liquidity Management"->"General Settings".
How to Determine Relevancy
You can identify via this description if the Simplification Item might be relevant.
Task 1: Check result of report FINS_PRE_CHECK_SFIN_1503 for the use of classic Cash Management.
Procedure:
Check if one the following messages is shown:
If there is no company codes with active cash management found, it means classic Cash
Management is not used;
If indicator for cash management is active for the following company codes, you then need
to check the following manually:
1. Run transaction SE16
2. Check the table entries in one of the following tables: FDM1, FDM2, FDMV, FDS1, FDS2,
FDSB, FDSB2, FDSBDIST, FDSP, FDSR, FDSR2, FDSRDIST, FDT1, FDW1, FDD1, FDES, FDESDIST,
FDFIEP, FDI1, FDLF, FDLF2, FDRE.
Simplification List for SAP S/4HANA 1610
245
3. If you find no entries, it means classic Cash Management is not used; If you find any entries,
it means classic Cash Management is used.
Rating: Yellow, if classic Cash Management is used; Otherwise, it's green.
Task 2: Check manually for the use of Liquidity Planner.
Procedure:
1. Run transaction SE16
2. Check the table entries in one of the following tables: FLQSUM and FLQSUM_FC.
3. If you find no entries, it means Liquidity Planner is not used; If you find any entries, it
means Liquidity Planner is used.
Rating: Yellow, if Liquidity Planner is used; Otherwise, it's green.
If classic Cash Management and Liquidity Planner are used (e.g. for cash position reporting), you
need to re-implement the new SAP Cash Management.
2.1.23.1.1 Related SAP Notes
Trouble Shooting Consulting SAP Note: 2175053
Note for migration
Relates Note
2149337 Release Scope Information - SAP Cash Management
(SAP S/4HANA Finance, On-Premise Edition 1503)
2.1.24 Financial – Controlling
2.1.24.1 Reference and Simulation Costing
Description
You are currently using base planning objects to store cost estimates that can be included in cost
estimates for projects, sales orders and so on as items of type B (base planning object). The creation
of cost estimates with reference to base planning objects is no longer supported in SAP S/4HANA.
Instead you are recommended to use transaction CKECP to prepare ad-hoc cost estimates and CKUC
to prepare multilevel material cost estimates where BOMs and routings are not available for the
material in question.
Business Process related information
Check your existing processes for cost estimation to determine whether you use costing items of
type B (base planning object) as references for other cost estimates.
Simplification List for SAP S/4HANA 1610
246
Transaction not available in SAP S/4HANA on-premise edition 1511
Create Base Planning Object
Change Base Planning Object
Display Base Planning Object
Revaluate Base Planning Object
Base Planning Object vs. Other Unit Cost Estimate
Costed Multilevel BOM (only Base Planning Object Exploded)
Transaction Code
KKE1
KKE2
KKE3
KKEB
KKEC
KKED
KKB4
Itemization
Overview of Base Planning Objects
S_ALR_87013028
Where Used List of Base Planning Objects
S_ALR_87013029
Multilevel Explosion of Base Planning Object
S_ALR_87013036
Required and Recommended Action(s)
Remove above transactions from existing roles and train users to work with alternative transactions.
2.1.24.2 Summarization Hierarchies in Controlling
Description
You are currently using summarization hierarchies, order hierarchies, or project hierarchies and want
to understand the impact of moving to SAP S/4HANA. Summarization hierarchies allow you to
aggregate data on orders or projects using the characteristics in the order header. The layers of the
hierarchy are created using transaction KKR0 (Create Summarization Hierarchy). The top node of the
hierarchy is always the controlling area. The next layers might be company code, plant, product
hierarchy and material. In SAP ERP the totals for each node in the hierarchy were calculated using a
data collection run (transaction KKRC) that typically ran at period close and calculated the totals for
each material, each product group, each plant and each company code in the above example and
updated these values to the CO totals tables (COSP and COSS) as summarization objects (object type
VD). The results of these aggregations could be viewed using transaction KKBC_HOE. SAP S/4HANA
offers a new transaction KKBC_HOE_H that uses the hierarchy structure defined using transaction
KKR0 but aggregates the order values on the fly and displays the results by node immediately. Note
that this aggregation will aggregate actual costs, commitments, planned costs, and so on, but does
Simplification List for SAP S/4HANA 1610
247
not calculate target costs or variances on the fly. You must run transaction KKS1 or KKS1H to
calculate target costs and variances before executing the new transaction.
Business Process related information
Transaction KKRC and KKBC_HOE are typically executed at period close since they require the precalculation of target costs. You can now run KKBC_HOE_H more frequently since it is not updating to
the totals records by period, providing that you also run the target cost calculation KKS1 or KKS1H
first.
Transaction not available in SAP S/4HANA on-premise edition 1511 Transaction Code
Data Collection Run
KKRC
Analyze Summarization Hierarchy
KKBC_HOE
Required and Recommended Action(s)
Check your existing roles to determine which include transaction KKBC_HOE and KKRC and replace by
KKBC_HOE_H.
2.1.24.3 Technical Changes in Material Ledger with Actual Costing
Material Ledger Actual Costing has been activated already in the system before the system
conversion to SAP S/4HANA.
You can verify if Material Ledger Actual Costing is active for one or more plants via SAP Reference
IMG / SAP Customizing Implementation Guide (transaction SPRO)
-> Controlling
-> Product Cost Controlling
-> Actual Costing/Material Ledger
-> Actual Costing
-> Activate Actual Costing
-- Activate Actual Costing
=> Checkbox 'Act.Costing' (Updating Is Active in Actual Costing)
Simplification List for SAP S/4HANA 1610
248
When this checkbox is marked, this means that Material Ledger Actual Costing is active in this plant.
Technically this can be verified via database table T001W, field MGVUPD. 'X' means that Material
Ledger Actual Costing is active in this plant.
In addition, the table T001W shows the link between the plant and the valuation area.
Description
With S/4HANA the data model for material ledger data has been changed significantly, especially
when actual costing is active.
The main purpose for the changed data model is:
Simplified Data Model
Simplification of Calculation Logic
Leverage the Strength of HANA
Business Process related information
Reduce complexity and improve runtime in the Material Ledger Costing Cockpit for Actual
Costing
Example: 4 separate process steps ('Single-Level Price Determination', 'Multilevel Price
Determination', 'Revaluation of Consumption', 'WIP Revaluation' ) are merged to one process
step ('Settlement')
New 2-dimensional distribution logic to avoids rounding errors
Less "not-distributed" values
No lock conflicts caused by material movements (in current period)
Change of standard price for materials and activities within the period is supported
Required and Recommended Action(s)
It is recommended to deactivate the statistical moving average price to benefit from
performance improvements (non reversible).
Separate currency customizing of Material Ledger (transactions OMX2 / OMX3) has become
obligatory, Material Ledger is acting on a subset of the currencies defined for Financials.
There is no default Material Ledger Type 0000 anymore.
It is not allowed to use a ML Type that references to currency settings defined in FI or CO
(flags Currency Types from FI resp. Currency Types from CO). Instead you have to define
explicitly the currency and valuation types that are relevant for Material Ledger.
Steps to be executed: 1. Define the currency and valuation types that are relevant for
Material Ledger using transaction OMX2. 2. Afterwards assign this ML Type to your valuation
area using transaction OMX3.
Before system conversion is started, all Material Ledger costing runs, no matter if actual
costing (transaction CKMLCP) or alternative valuation run (transaction CKMLCPAVR) need to
be finished (e.g. step 'post closing' successfully executed, no error, no materials with status
Simplification List for SAP S/4HANA 1610
249
'open'). Reason: After system conversion to SAP S/4HANA it will not be possible to do any
changes on costing runs created before system conversion.
It is not allowed to change Material Ledger costing runs, nor to run steps of Material Ledger
costing runs during the process of system conversion.
It is not allowed to activate or deactivate Material Ledger Actual Costing during the process
of system conversion for one or more plants.
Details:
Simplified Data Model
Tables MLDOC and MLDOCCCS
o The new Material Ledger Document tables MLDOC and MLDOCCCS replace most
former periodic tables (MLHD, MLIT, MLPP, MLPPF, MLCR, MLCRF,
MLKEPH, CKMLPP, CKMLCR, MLCD, CKMLMV003, CKMLMV004, CKMLPPWIP,
CKMLKEPH). For more information refer to note 2352383.
o Some of the former periodic tables are still required for the following purposes:
The Material Ledger Closing Document is stored in the former ML document
tables (ML*)
Standard Price. Periodic Unit Price and Price Control are still managed in
table CKLMLCR
Cost Component Split for Prices is still managed in tables CKMLPRKEKO and
CKMLPRKEPH
o The design of tables MLDOC/ MLDOCCCS allows storing both line item and
aggregated data.
o Periodic transactions (goods movements, activity confirmation, etc.) update tables
MLDOC/ MLDOCCCS with line item data using the INSERT ONLY principle.
o Material Ledger Period Close creates (run-dependent) settlement records in tables
MLDOC/ MLDOCCCS to store the results from Actual Costing. These records are
stored under the costing run key (field Run Reference) so that they are visible only by
the corresponding costing run. In this way different runs (e.g. a periodic run and an
AVR) can store their results independently from each other.
o Important design changes
Single- and multilevel differences are no longer distinguished. In table
MLDOC all price/exchange rate differences are stored in fields PRD/KDM. In
table MLDOCCCS the CCS for price/exchange rate differences are stored
under the CCS types E/F (field MLCCT).
The CCS is stored in a table format using the cost component (field
ELEMENT) as additional key. This allows increasing the number of cost
components without modification.
The CCS for preliminary valuation is always stored
Tables MLDOC_EXTRACT and MLDOCCCS_EXTRACT
o The table MLDOC_EXTRACT holds information about quantity and valuation changes.
Transaction based updates, like goods movements or invoice receipts, usually update
tables MLDOC and MLDOC_EXTRACT in parallel. But table MLDOC_EXTRACT can be
compressed. After compression, the table will contain only one entry per cost
estimate number, period and currency type valuation view. Table MLDOC_EXTRACT
Simplification List for SAP S/4HANA 1610
250
allows fast and efficient calculation of total quantity and total value, by cumulating
all records for specific cost estimate number(s). The same is true for table
MLDOCCCS_EXTRACT which has been designed for holding cost component
information. During period shift (transaction MMPV) the tables MLDOC_EXTRACT
and MLDOCCCS_EXTRACT will be compressed automatically for periods older than
previous period. Manual compression via program
FCML4H_RMLDOC_EXTRACT_COMPRESS or via function module
FCML4H_MLDOC_EXTRACT_COMPRESS is possible and recommended in case of very
high number of material movements.
Table MLRUNLIST
o Table MLRUNLIST replaces the former table CKMLMV011 (Object List for Costing
Run), but has some additional functions:
Materials and activities selected for a costing run are stored under the
corresponding run id.
It manages the period status of materials and activities
Data Conversion
In case Material Ledger Actual Costing has been activated already in the system, in one or
more valuation areas, before the system conversion to SAP S/4HANA (when the system is e.g. on
release SAP ERP 6.0 or on SAP Simple Finance), the tables MLDOC, MLDOCCCS, MLDOC_EXTRACT and
MLDOCCCS_EXTRACT are filled automatically with data, during Migration Step M10: Migrate Material
Ledger Master Data for the valuation areas, where Material Ledger Actual Costing has been
activated. The data will be created starting from last period of previous year until the current period
in the system. All material related goods movements or price changes from previous years will
be converted to the MLDOC tables as if the goods movement or the price change has taken place in
the last period of previos year. The data of the current year will be converted not based on single
material documents or price change documents, but there will be one entry per period, per currency
type and valuation view, per category (e.g. "Receipts"), per process catregory (e.g. "Production") and
per production process. Data related to ML Alternative Valuation Runs are not converted
automatically during Migration Step M10.
Functional changes/improvements
Material Price Analysis (Transaction CKM3):
No separate view for Cost Components, but integrated in main screen
Flag for selection of cost components not relevant for material valuation, or only cost
components relevant for material valuation; by default selection of inventory relevant cost
component split
Display of WIP Reduction for material; by default WIP Reduction is hidden; If WIP reduction is
displayed, both WIP reduction and consumption of WIP for order are shown in opposite sign
in different folder.
Plan/Actual Comparison is removed in new CKM3
Technically, data are retrieved from table MLDOC, MLDOCCCS and MLDOC_EXTRACT and
MLDOCCCS_EXTRACT
Simplification List for SAP S/4HANA 1610
251
Remark: Data older than last period of previous year (related to the time of system conversion)
cannot be displayed via transaction CKM3 because the 'old' data has not been converted to the
MLDOC-tables. To show data older than last period of previous year you can use transaction
CKM3OLD('Material Price Analysis') or CKM3PHOLD ('Material Price History')
ML Actual Costing Cockpit (Transaction CKMLCPAVR):
In the transactions CKMLCP and CKMLCPAVR, there is an additional parameter
Application. This means that the application can be chosen so that it is possible to process
Alternative Valuation Runs via the transaction CKMLCP and Actual Costing Runs via the
transaction CKMLCPAVR.
In the toolbar of the transactions CKMLCP and CKMLCPAVR, there is a new button next to the
Display <-> Change-Button to switch the application from Costing Run to Run Reference and
back.
When the application is switched to Run Reference, a run reference can be created, changed
or displayed. A run reference is a reference that contains all settings of an Alternative
Valuation Run. It can be used when creating an Alternative Valuation Run but it is only
mandatory for creating Alternative Valuation Runs for Parallel COGM. It can also be created
for a single period run, for year-to-date run or for a rolling run.
There are 2 options for creating an AVR:
o Create a Classic AVR which is the same like before.
o Create an AVR with run reference which means the settings are taken from the run
reference and cant be changed. Only the plants must be chosen.
Some of the programs and therefore also the steps in the section Processing have changed.
The new steps of an ML costing run are:
o Selection (program FCML4H_SELECTION)
o Preparation (program FCML4H_PREPROCESSOR)
o Settlement (program FCML4H_SETTLEMENT)
o Post Closing (program FCML4H_POST_CLOSING)
It is no longer possible to use delta posting runs.
Additionally to the status of the materials, the status of the activity types is displayed in the
section Processing. The button Activity Types for displaying the activity types value flow has
been removed.
The section Costing Results has been removed. It will be replaced by the report
FCML4H_RUN_DISPLAY_MATERIALS that displays a material list with status. It will called via
the button Results in the section Processing.
The classical CKMLCP steps Single Level Price Determination, Multilevel Price Determination,
Revaluation of Consumption and WIP Revaluation have been replaced by the new step
Settlement which essentially does all cost allocations and actual price calculations.
Additionally the step Preparation is required to prepare the data (e.g. reading of
apportionment structures, actual activity prices, cost sequence determination).
A change of standard price for materials and activities within the period is now supported
Easier reprocessing: If a material is reprocessed by settlement the depending materials on
higher costing levels which need to be reprocessed are recognized automatically
Consumption Price Differences (i.e. Price Differences updated in Consumption Folder) are
now taken into account
Simplification List for SAP S/4HANA 1610
252
A new 2-dimensional distribution logic avoids rounding errors. The new CKM3 will match
vertically and horizontally even on level of Cost Components
Price Limiter Logic is accurate on level of Cost Component Split
Materials and Activity Types are widely treated as equivalent objects. The cost allocation
logic is essentially the same. The same reports (e.g. CKM3, CKMVFM) can be used for both of
them (-> to be enabled yet!)
Alternative Valuation Run (AVR):
o The new AVR do no longer copy the data into a separate key area. (Only the
settlement records are stored under the AVR Run Reference, see above). In
particular,
the cumulation of several period is done On-the-fly.
o The former step Cumulate Data is no longer needed
o The complex rescale logic, which adjusts all materials data to a common preliminary
AVR price, is no longer needed.
o All AVR can now handle WIP
o Post Closing:
Post Closing uses a push logic (in accordance to the new Settlement). This
means that the price differences rolled from an input to the output are now
posted
in the closing document of the input (material/activity)
For activity types (and business processes) a new posting has been
introduced. See the documentation in transaction OBYC for the new
transaction key PRL:
Price differences for activity types or business processes. During settlement in
the material ledger, these price differences are posted from cost centers
(Transaction/Account Modification GBB/AUI) to the material ledger
(transaction PRL) and then further allocated to the receivers (finished
products/WIP).
Restrictions
AVR Delta Posting Logic is not available
External Ending/Cumulated Inventory Valuation is currently not available
The BAdI CKMLAVR_SIM is currently not available
Material Ledger Costing Runs and Alternative Valuation Runs, which have been created
before the system conversion cannot be changed nor reversed any more after the conversion
to SAP S/4HANA
Material Ledger Valuated Quantity Structure (Transaction CKMLQS) is currently not available
2.1.24.4 TECHNICAL CHANGES IN CONTROLLING
Description
Actual Items:
Actual data of COEP (WRTTP = 04) is now stored in ACDOCA.
Simplification List for SAP S/4HANA 1610
253
Actual statistical data of COEP (WRTTP = 11) is stored in ACDOCA using additional columns
for the statistical account assignments and in COEP for compatibility access
Actual data needed for long-term orders/projects from COSP_BAK, COSS_BAK is stored in
table ACDOCA.
Currently, COBK is written as before.
Compatibility views V_<TABLENAME> (for example, V_COEP) are provided to reproduce the
old structures.
Access to old data in tables is still possible via the views V_<TABLENAME>_ORI (for
example, V_COEP_ORI).
Value types other than 04 and 11 are still stored in COEP, COSP_BAK, COSS_BAK.
Business Process related information
The former tables COEP, COSP, and COSS are replaced by views of the same name, so-called
compatibility views.
CO standard transactions are adapted in a stepwise manner to access the new universal journal table
(ACDOCA) directly instead of using compatibility views.
From a business point of view, all classic transactions are still running - based on compatibility views
or using direct acces to ACDOCA.
These views calculate the old total table structures on the fly. They provide a bridge to the new data
model.
Customer coding still runs based on compatibility views.
Required and Recommended Action(s)
Please check your customer-specific programs using CO tables.
Customer coding should be adapted by replacing the access via compatibility views with direct access
to ACDOCA for value types 04 and 11.
Details are described in note 2185026.
Related SAP Notes
2185026
Compatibility views COSP, COSS, COEP, COVP: How do you optimize their
use.
Notes linked in 2185026
2.1.24.5 PROFIT AND LOSS PLANNING AND PROFIT CENTER PLANNING
Description
CO-OM planning, P&L planning, and profit center planning are now covered by SAP BPC for S/4HANA
Finance (formerly known as Integrated Business Planning) (SAP Note 2081400). If you do not want to
use SAP BPC for S/4HANA but classic FI-GL and CO-OM planning functions instead, you may apply the
modifications as indicated in the followng SAP Notes. Bear in mind, however, that in this case the
planning results are written to the totals tables and require "plan integration" to share data between
plans. Reports designed specifically for use with S/4 HANA Finance do not read these totals tables.
Simplification List for SAP S/4HANA 1610
254
FI-GL Planning - SAP Note 2253067
Cost Center Planning by Cost Element - SAP Note 2142447
Order Planning by Cost Element - SAP Note 2148356
Project Planning by Cost Element - SAP Note 2135362
Project Planning Overall - SAP Note 2142732
With these modifications, the deactivation of the old FI-GL and CO-OM planning transactions can be
removed and the transactions used as before. Customer project required to activate SAP BPC for
S/4HANA Finance and adapt the delivered queries to customer needs. Customers preferring to delay
such a project can reactivate the classic planning transactions using the SAP Notes described above.
Note that it is also possible to run the two solutions in parallel. SAP Note 2061419 describes how to
retract data from SAP BPC for S/4HANA Finance into the totals tables so that this data can be used as
a basis for cost center allocations and activity price calculation and order/project budget setting and
settlements and to extract the data back to SAP BPC for S/4HANA Finance so that it is available for
reporting when the planning cycle is complete.
Business Process related information
If SAP BPC for S/4HANA Finance is desired or required , then SAP BPC for S/4HANA Finance has to be
set up (SAP Note 2081400). Implications:
Customer roles (menus and authorizations) may need to be adapted.
Decision needed as to whether plan/actual reporting will be based on totals tables or take
place using SAP S/4HANA Finance reports
Decision needed as to whether planning data is needed for follow-on processes in S/4HANA
Finance (e.g. target cost calculation for cost centers, project budgeting)
Decision needed as to whether order and project planning is required for reporting and
budgeting purposes in Investment Management
Implications : SAP BPC needs to be installed and configured, respective front-ends chosen,
and so on.
Transaction not available
in SAP S/4HANA onpremise edition 1511
GP12N, GP12NA, FAGLP03 (plan data entry in FI) plus plan assessment cycles
(FAGLGA4* transactions) and plan distribution cycles (FAGLGA2* transactions)
CJ40/CJ42 (overall planning on projects) KP06/KP07 (cost centre planning),
CJR2/CJR3 (project planning) and KPF6/KPF7 (order planning) can be reactivated
by SAP Note
Required and Recommended Action(s)
Decision needed concerning scope of existing planning processes, requirements for
plan/actual reporting and ability to use delivered business content for SAP BPC for S/4HANA
Finance.
Activate SAP BPC for S/4HANA Finance and compare against project needs.
No changes to existing tables. Instead new business content for SAP BPC for S/4HANA
Finance must be activated as described in SAP Note 2081400.
Simplification List for SAP S/4HANA 1610
255
Follow steps in Installation Guide provided with SAP Note 1972819. Explore SAP BPC
functions to extend scope (e.g. use of business process flows)
Related SAP Notes
Conversion Pre-Checks
Related SAP Notes
Please check scope of existing planning activities and determine whether they
can be covered using the business content currently available for SAP BPC for
S/4HANA Finance. If you are currently using activity price calculation to set
activity rates or Investment Planning, you can still use Integrated Business
Planning for Finance but will need to retract the results to tables COSP_BAK,
COSS_BAK to perform the follow-on processes. If you are using costing-based
CO-PA the table structure will remain unchanged and there will be no loss of
functionality.
SAP Note: 2081400, 1972819
2.1.24.6 ACTIVITY-BASED COSTING
Description
Activity-Based Costing (CO-OM-ABC) using delta versions is not available in SAP S/4HANA. Delta
versions in general are not available in SAP S/4HANA, so the option to use Parallel Activity Based
Costing (setting in the controlling area) is no longer available. Activity-Based Costing using version 0
(Integrated Activity Based Costing in the controlling area settings) is still supported.
Business Process related information
Allocations performed in parallel activity based costing are no longer supported.
Transaction not available Transaction codes do not distinguish parallel and operative activity based
in SAP S/4HANA oncosting, so transaction codes remain in the menu but are not available for
premise edition 1511
delta versions (error message).
Required and Recommended Action(s)
Activate Operational Activity Based Costing.
Related SAP Notes
Conversion Pre-Checks
Check controlling area settings in customizing to determine the type of
Activity Based Costing which is active. Check version settings in
Customizing to determine whether there are CO versions other than
version 0 that contain actual data.
Simplification List for SAP S/4HANA 1610
256
2.1.24.7 GENERAL COST OBJECTS AND COST OBJECT HIERARCHIES
Description
General Cost Objects and Cost Object Hierarchies are not available within SAP S/4HANA, on-premise
edition 1511.
Business Process related information
General Cost Objects are not available within SAP S/4HANA, on-premise edition 1511 (consider using
internal orders or product cost collectors instead). The associated functions were previously part of
the menu Controlling > Product Cost Controlling > Cost Object Controlling > Intangible Goods and
Services. Note that a general cost object is not the same as a CO object which can refer to orders,
WBS elements or any item to which costs can be assigned. Cost Object Hierarchies are not available
within SAP S/4HANA, on-premise edition 1511 (consider using summarization hierarchies for
aggregation of costs on manufacturing orders and distribution of usage variances function to
distribute inventory differences and activity differences instead). The associated functions were
previously part of the menu Controlling > Product Cost Controlling > Cost Object Controlling >
Prooduct Cost by Period. Custom Code to update cost object to CO tables will still run. Contact SAP
for pilot note to release functions for short term use. Where the cost object hierarchy is being used
to aggregate costs collected on the manufacturing orders, it is recommended that an order hierarchy
be used instead. These hierarchies are created by using transaction KKR0 and are aggregated at
runtime by using transaction KKBC_HOE_H. Note that this transaction behaves like transaction
KKBC_HOE but does not require a data collection run to pre-aggregate the data for each hierarchy
node. Where the cost object hierarchy is used to collect costs at an aggregate level and then
distribute them to the associated manufacturing orders, it is recommended that transaction
CKMATDUV be used to distribute material usage variances and CKMDUVACT to distribute activity
usage variances.
Analyze reporting processes to determine whether cost objects are used as an account assignment
and understand the nature of the costs posted to the cost object nodes. Use distribution of usage
variances function as an alternative for cost distribution. Analyze reporting processes to determine
whether cost objects are used to aggregate costs and understand the nature of the reporting
hierarchy (representation of profit centers, cost centers, responsibility areas) and determine
alternative ways of reporting.
Transaction not available KKC1, KKC2, KKC3 - Create, change and display general cost object
in SAP S/4HANA onKKPH - General cost objects - collective entry
premise edition 1511
KKH1, KKH2, KKH3 - Create, change and display cost object groups
KK16, KK17 - Cost object planning by cost element and activity
KK46, KK47 - Cost object planning by statistical key figure
KKC4, KKC5, KKC& - Create, change and display cumulative cost object planning
KKBC_KTR - Analyze cost object
KKC5 - Display cost object line items
CPTG, CPTH - Template allocation for cost objects
KKN1, KKN2 - Revaluation of actual prices for cost objects
KKPZ, KKPJ - Overhead allocation for cost objects
KK88, KK89 - Settlement of cost objects
KKPHIE - Cost Object Hierarchy (consider using an order hierarchy KKBC_HOE_H
Simplification List for SAP S/4HANA 1610
257
instead and building the hierarchy nodes using transaction KKR0)
KKP2 - Change Hierarchy Master Record (no hierarchy master record is required
with order hierarchies, but the hierarchy is built dynamically using fields in the
order master)
KKP4 - Display Cost Object Hierarchy( no hierarchy master record is required with
order hierarchies)
KKP6 - Cost Object Analysis (consider using an order hierarchy KKBC_HOE_H
instead)
KKPX - Actual Cost Distribution: Cost Objects (consider using distribution of usage
variances (transactions CKMATDUV.and CKACTDUV instead)
KKPY -.Actual Cost Distribution: Cost Objects (consider using distribution of usage
variances instead)
KKAO, KKAV - WIP Calculation for cost object hierarchies
KKP5, KKPT - Variance calculation for cost object hierarchies
BAPI_COSTOBJECT_GETDETAIL and BAPI_COSTOBJECT_GETLIST
Required and Recommended Action(s)
Do not activate Cost Objects in controlling area. Do not build a data model that requires use of
general cost objects or cost object hierarchies. Investigate alternative solutions outlined above if you
are using cost objects or cost object hierarchies as you move to SAP S/4HANA. Adjust roles and
authorizations to remove deprecated transactions.
2.1.24.8 TRANSFER PRICES/ PARALLEL DELTA VERSIONS
Ursache und Voraussetzungen
Task:Check if any currency and valuation profile is assigned to any controlling area:
Procedure: Go to implementation guide (Transaction SPRO) --> Controlling --> General Controlling -->
Multiple Valuation Approaches/Transfer Prices --> Basic Settings Select 'Maintain Controlling Area' -> 'Assign Currency&Valuation Profile to Controlling Area If there is any entry in column C+V Profile
this note is relevant for you.
Description
The functionality for valuing the transfer of goods or services according to legal, group, or profit
center valuation is supported as of SAP S/4 HANA 1610. The Functionality is not available in SAP
S/4HANA 1511, on-premise edition. Transfer prices provide parallel valuation methods for legal,
group, and profit center valuation.
The legal perspective looks at the business transactions from a companys point of view.
Pricing is driven by legal requirements and tax optimization strategies.
Profit center valuation looks at profit centers as independent entities within the group.
The group view considers the group as a whole. The processes are valued by eliminating
intercompany/inter-profit center profits.
Simplification List for SAP S/4HANA 1610
258
With the merge of FI and CO into the Universal Journal, a new approach for parallel valuations was
implemented:
Transfer prices can be updated within a ledger containing all valuation views or alternatively with
separate ledgers per valuation view.
Parallel delta versions for actuals in Controlling are used for statistical line items updating table COEP
only.
All other actual line items updating table ACDOCA use the new data model.
Installed based customers using transfer prices in ERP can migrate to SAP S/4HANA 1610.
The migration of transactional data involves a transformation from the ERP data model to the SAP
S/4HANA data model in Financials.
The necessary Customizing steps can be found in the Preparations and Migration of Customizing
area under Preparations and Migration of Customizing for General Ledger.
The functionality of Multiple Valuation of Cost of Goods Manufactured providing parallel valuations
in CO according to multiple accounting principles is not yet supported in SAP S/4HANA.
ABC using delta versions is not supported in SAP S/4HANA (for more details see note 2270408 Activity-Based Costing).
Business Process related information
All business processes supporting transfer pricing in ERP are re-enabled in S/4 HANA 1610.
Related SAP Notes
Conversion Pre-Checks
Check against currency and valuation profiles during migration.
2.1.24.9 COST ELEMENTS
Description
Cost elements become part of the chart of accounts. They are maintained in GL account master data.
There is no separate cost element master data maintenance.
Account master record includes new field for cost element category which classifies GL accounts into
the following types:
Balance Sheet Account - Account that is posted from business transactions. The balance of a
balance sheet account is carried forward at fiscal year-end.
Nonoperating Expense or Income - Income statement account that records expenses or gains
from activities that are not part of the main purpose of the company, such as gains realized
from financial investments by a manufacturing company.
Simplification List for SAP S/4HANA 1610
259
Primary Costs or Revenue - Income statement account that functions as a cost element for
primary costs or revenue. Primary costs reflect operating expenses such as payroll, selling
expenses, or administration costs.
Secondary Costs - Income statement account that functions as a cost element for secondary
costs. Secondary costs result from value flows within the organization, such as internal
activity cost allocations, overhead allocations, and settlement transactions.
Accordingly GL accounts have now attributed on three levels:
Chart of accounts area - Contains the data that is valid for all company codes, such as the
account number.
Company-code-specific area - Contains data that may vary from one company code to
another, such as the currency.
Controlling-area-specific area - Contains data that may vary from one controlling area to
another, such as the cost element category. Only needed for accounts of the type Primary
Costs or Revenue and Secondary Costs.
Default account assignments for cost elememts can be set in transaction OKB9 rather than in the
cost element master. Field status groups can remain unchanged.
Excisting GL accounts and cost elements are migrated into new data model automatically by a
separate step within the migration process. The migration adds the new GL account category and
creates for the secondary cost elements the required entries in the chart of accounts.
Implications: Customer roles (menus and authorizations) need to be adjusted. To maintain primary
and secondary cost elements you will need authorization for both G/L accounts and cost elements.
To allow postings in specific periods ensure that postings are allowed for the appropriate accounts in
GL and in parallel for the appropriate CO business transactions (transaction OKP1).
Business Process related information
The universal journal contains one field account that covers both G/L accounts and cost elements.
The account master offers new account types for primary costs/revenues and secondary costs.
G/L accounts of account type primary costs/revenues require a CO account assignment (cost centers,
account, project, CO-PA characteristic). G/L accounts of account type secondary costs will be updated
during direct activity allocation, assessment, distribution, settlement, and so on. New reports such as
the trial balance will display all postings (primary and secondary) by account. Classic reports will
display cost elements via compatibility views. Customizing settings such as costing sheets, cost
component structures, settlement profiles, allocations, and so on will continue to display cost
elements. All journal entries are recorded under G/L accounts, including primary costs (wages,
salaries, depreciation, raw materials, and so on) and secondary costs (direct and indirect activity
allocations, settlement, and so on). Cost element groups are still available to group accounts of type
primary or secondary cost element for selection and reporting.
Simplification List for SAP S/4HANA 1610
260
Transaction not
KA01 - Create primary cost element
available in SAP S/4HANA KA02 - Change cost element
on-premise edition 1511 KA03 - Display cost element
KA06 - Create secondary cost element
Default account assignments (cost center, order) will be transferred from
cost element masters to table TKA3A (view using transaction OKB9).
Required and Recommended Action(s)
Design for chart of accounts must include all profit and loss accounts and secondary cost
elements that represent value flows within the company.
2.1.24.10 Reporting/Analytics in Controlling
Description
You want to use the new reporting tools and the universal journal for your reporting tasks, but need
to understand which controlling reports are not yet covered in SAP S/4HANA. The universal journal
brings together the account assignments traditionally considered to be part of Controlling (cost
center, order, WBS element, and so on), Profitability Analysis (products, product groups, customers,
customer groups, regions, and so on) and Enterprise Controlling (profit center). This provides a profit
and loss statement with a drill-down to the above reporting dimensions and dedicated reports by
profit center, functional area, cost center, internal order, project, and market segment. The merge of
accounts and cost elements means that you also effectively see CO postings in the trial balance and
related reports. From a reporting point of view this means that the conventional component barriers,
no longer hold. Where a drill-down report in the general ledger could previously drill down by any
dimension in FAGLFLEXT but not to the CO account assignments, with SAP S/4HANA you have more
flexibility and can report on any of the dimensions listed above. Nevertheless if you continue to use a
classic drill-down report (built using transaction FGI1), you will only see the reporting dimensions
that were previously available in the SAP General Ledger, because you are technically using a
compatibility view. To use the new reports, you will have to activate the relevant Fiori apps, and in
some cases the embedded BW content within SAP S/4HANA to enable these reports. There are Fiori
apps for reporting on cost centers, internal orders, projects, and sales order items. The account
structure for these reports can be based on the financial statement version or on the cost element
groups. For cost centers, internal orders, and projects you can distinguish between real and statistical
postings in reporting. Nonetheless, you need to be aware that plan/actual reporting is based on SAP
BPC for S/4 HANA Finance and you will need to activate the appropriate planning applications and
BW content. There are not yet Fiori apps for reporting on commitments for any of the CO account
assignments. For the cost centers there are not yet Fiori apps for reporting on target costs, variance
categories, and intercompany eliminations. For the internal orders and projects, there are not yet
Fiori apps for reporting on budget, allotted costs, work in process or results analysis. For the sales
orders, there are not yet Fiori apps for reporting on cost estimates or results analysis. For these
reporting tasks, you will need to continue to use Report Writer/Painter or drill-down reports as
appropriate. All classic reports, including the line item reports, continue to display cost elements and
cost element groups rather than accounts and account groups. If you choose to use a mixture of new
Simplification List for SAP S/4HANA 1610
261
applications and classic tools, you should be aware that it is possible to retract planning data from
SAP BPC to cost center planning, order planning and project planning and to fill the general ledger
and profit center plan via plan integration in order to provide the appropriate plan/actual reports by
cost element. There are Fiori apps for reporting on market segments based on the account-based
approach. Plan/actual reporting here is also based on SAP BPC and you will need to activate the
appropriate planning applications and BW content. SAP S/4HANA includes new functions allowing
you to derive the market segments at the time of postings to cost centers, orders, and projects. Such
market segment information is only available in the new reporting apps. Traditional drill-down
reports, built using transaction KE30, and the line item report (KE24) will continue to work, but will
only show revenues and costs where the account assignment is a CO-PA characteristic (ie values are
assigned to object type EO). Costing-based CO-PA continues to be supported. The existing extractors
to SAP BW will continue to work. You should also consider using the new datasource
0FI_ACDOCA_10 to extract the complete universal journal to SAP BW, where BW runs as a dedicated
data warehouse, rather than in embedded mode.
Business Process related information
Analyze existing roles to determine which reporting applications are used by which business users.
Check against Fiori business catalogs to determine which reporting apps can be offered to which user
groups. Analyze existing roles in SAP BW to determine whether some operational reporting
applications can be moved back into SAP S/4HANA. Check existing planning process and determine
whether it is possible to move some (or even all) planning activities to SAP BPC.
Transaction not available in SAP S/4HANA onpremise edition 1511
All transactions available, but are making use of
compatibility views
Required and Recommended Action(s)
All existing reports in Report Writer/Painter, drill-down reporting and ABAP List Views (ALV) will
continue to work using compatibility views but will not provide insight beyond what was already
available in SAP ERP. Activate appropriate Fiori reporting apps and test with end users. Check existing
planning process and determine whether it is possible to move some (or even all) planning activities
to SAP BPC.
2.1.24.11 Profitability Analysis
Description
The universal journal (ACDOCA) is the heart of Accounting and includes all Profitability Analysis (COPA) characteristics in order to allow multi-dimensional reporting by market segment. The universal
journal includes columns for the standard CO-PA characteristics and all additional characteristics
included in an organizations operating concern (up to fifty characteristics). If you have already
configured an operating concern, columns will be created for each of the CO-PA characteristics
during migration. If you have worked with account-based CO-PA in SAP ERP, you no longer need to
reduce the number of characteristics available in account-based CO-PA compared to costing-based
CO-PA, but can include all available characteristics in the universal journal. It is not possible to use
more than 50 characteristics in one operating concern.
Simplification List for SAP S/4HANA 1610
262
Business Process related information
If you currently work with costing-based CO-PA, you can continue to run both approaches in parallel,
by making the appropriate settings per controlling area. The essential difference is that costing-based
CO-PA is a key figure based model, rather than an account-based model. Account-based CO-PA
covers record types F (billing documents, B (direct FI postings), C (settlement) and D (assessment) in
costing-based CO-PA.
There is no direct migration from costing-based CO-PA to account-based CO-PA. Please bear in mind
the following general principles as you consider a conversion:
Revenues and sales deductions are included in CO-PA whenever the price conditions are mapped
to an account. Statistical price conditions are not included.
Cost of goods sold (COGS) postings are captured at the time of the goods issue from the
warehouse. New functions are available to split the COGS posting to multiple accounts in
accordance with the relative weight of the assigned cost components. Functions to support the
matching principle between revenues and COGS are planned.
Production order variances can be split to multiple accounts to separate scrap, price variances,
quantity variances, and so on.
Assessment cycles and settlement will update under secondary cost elements. Depending on how
many value fields you used before, you may need to define additional cost elements and adjust
your cycles/settlement profiles to give you the required detail.
You may be able to replace some assessment cycles and settlements by having the system derive
the CO-PA characteristics at the time of posting instead of moving them from the cost center,
order or project at period close.
Top-down distribution works in account-based CO-PA, but you must include the account/cost
element in the selection criteria.
New fields are included in the universal journal for the invoice quantities. BADIs can be used to
convert e.g. the quantity from the invoice to a base unit of measure and from there to a reporting
unit.
Transaction not available in SAP S/4HANA onpremise edition 1511
All transactions available, but some transactions
(e.g. KE27) only
support costing-based CO-PA.
Required and Recommended Action(s)
Analyze existing reporting requirements to understand how market segment reporting is handled
today. Also include transfer of profitability information to other systems, including data warehouses.
If costing-based CO-PA is currently used, analyze what workarounds are being used to reconcile the
profit and loss statement with costing-based CO-PA to determine whether these will be required in
the future.
Simplification List for SAP S/4HANA 1610
263
2.1.25 Financials - International Trade
2.1.25.1 Material classification with commodity codes
You classify materials with commodiy codes in transaction MM01 / MM02. This functionality
(material classification with commodity codes) is redesigned in SAP S/4HANA
1610. Following redesign apply:
1. Management of commodity codes
-
Old in ECC and S/4HANA 1511: not time-dependent, valid for a country
New in S/4HANA 1610: time-dependent, valid for a country or multiple countries, new app,
new data model
2. Classification of materials with commodity codes
-
Old in ECC and S/4HANA 1511: not time-dependent, valid for material and plant, done in
material master apps (e.g. MM01, MM02)
New in S/4HANA 1610: time-dependent, valid for material and a country or multiple
countries, new FIORI apps, new data model
2.1.25.1.1 Business Process related information
Before conversion you can run the pre-check report to check if there is inconsistent
data. Inconsistent data is not taken over in new data model. If there is inconsistent data, you can
check and correct it (Details in note 2332472) before conversion is triggered. During upgrade to
S/4HANA 1610, a XPRA - /SAPSLL/XPRA_1610_MARC_STAWN - migrates classification data to new
data model.
2.1.25.1.2 Required and Recommended Action(s)
Knowledge transfer to key and end users
2.1.25.1.3 How to Determine Relevancy
This Simplification Item is relevant if you classify materials using commodity code. You are likely using
this functionality if you find non initial values in field STAWN of table MARC.
2.1.26 Financials - Treasury and Risk Management
2.1.26.1 Drilldown Reporting in Treasury and Risk Management
Description
Simplification List for SAP S/4HANA 1610
264
The drilldown reporting has been disabled for Treasury and Risk Management. For reporting
purposes, you can use the logical databases available for the TRM.
2.1.26.2 Quantity Ledger Always Active for Money Market Transactions
Description
The quantity ledger is now always used for money market transactions.
2.1.26.3 Several Kinds of Financial Objects Disabled
Description
The creation of the following outdated kinds of financial objects has been disabled in Risk
Management:
Security Order
Positions
Variable Transactions
Positions of Fictitious/Simulated Transactions
Facilities
Non-Interest Profit and Loss Items
2.1.26.4 Accrual/Deferral of Expenses and Revenues
Description
The old functions for the accrual/deferral of expenses and revenues have been replaced by a central
function for the accrual/deferral of expenses and revenues for all kinds of financial transactions.
Required and Recommended Action(s)
The customers have to implement the new central accrual/deferral of expenses and Revenues
functionality before they go to SAP S/4HANA On Premise 1511 Edition.
2.1.26.5 Fiduciary Deposits
Description
Fiduciary deposits based on product category 570 are not available within SAP S/4HANA, on-premise
edition 1511.
2.1.26.6 Drawable Bonds
Description
Simplification List for SAP S/4HANA 1610
265
Drawable bonds based on product category 041 are not available within SAP S/4HANA, on-premise
edition 1511.
2.1.26.7 Master Agreements
Description
Master agreements are not available in SAP S4/HANA. Read the following information in case the
pre-upgrade check in your system issues a message for the check ID SI11_MASTER_AGREEMENTS
"Master Agreements": This check issues a warning if it finds entries in the database which indicate
that master agreements were created in some client of the system. The warning message is for your
information, no further mandatory action is required. Read the following information in case the
custom code analysis has detected customer coding related to this transition worklist item: SAP
objects which are used by the detected customer code shall not be used any more. Adapt the
customer code accordingly.
2.1.26.8 Offers
Description
Offers in transaction management are not available in S4/HANA. Read the following information in
case the pre-upgrade check in your system issues a message for the check ID SI12_OFFERS "Offers":
This check issues a warning if it finds entries in the database which indicate that offers were
created in some client of the system. The warning message is for your information, no futher
mandatory action is required. Read the following information in case the custom code analysis has
detected customer coding related to this transition worklist item: SAP objects which are used by the
detected customer code shall not be used any more. Adapt the customer code accordingly.
2.1.26.9 Simulation in Transaction Management
Description
Simulations in transaction management are not available in S/4HANA. Read the following
information in case the pre-upgrade check in your system issues a message for the check
ID SI13_SIMULATION "Simulation in Transaction Manager": This check issues a warning if it finds
entries in the database which indicate that simulations were created in some clients of the system.
The warning message is for your information, no further mandatory action is required. Read the
following information in case the custom code analysis has detected customer coding related to this
transition worklist item: SAP objects which are used by the detected customer code shall not be used
any more. Adapt the customer code accordingly.
2.1.26.10 Correspondence Functionality
Description
Simplification List for SAP S/4HANA 1610
266
Starting with SAP enhancement package 4 for SAP ERP 6.0 the Treasury and Risk Management
provides a new correspondence framework that provides a highly automated process for incoming
and outgoing correspondence (details can be found in enhancement package 4 EKT material).
Within SAP enhancement package 5 for SAP ERP 6.0 this correspondence framework was enhanced
(details can be found in enhancement package 5 EKT material). When switching to the
correspondence framework new customizing is necessary. It is possible to migrate customizing from
old correspondence functionality, but this will create many technical customizing entries. SAP
strongly recommends that you do not migrate and instead manually create necessary customizing. In
SAP ERP starting with SAP enhancement package 4 for SAP ERP 6.0 you can activate the
correspondence framework via business function FIN_TRM_CORR_FW. With SAP enhancement
package 5 for SAP ERP 6.0 business function FIN_TRM_CORR_FW_2 is available. In SAP S/4HANA
1511 both business functions are always on and correspondence framework is active, because the
old correspondence functionality is not that flexible as the Correspondence Framework and also uses
SAPscript forms, so this outdated functionality is not available anymore in SAP S/4HANA 1511.
Required and Recommended Action(s)
Customers have to implement the Correspondence Framework before they go to SAP S/4HANA 1511.
If you are not using old correspondence functionality and you do not plan to use correspondence
framework you can upgrade to S/4HANA without any difficulties. If you are using old correspondence
functionality and upgrade to SAP S/4HANA from a release in which correspondence framework is
technically available, SAP recommends that you activate correspondence framework and create
necessary customizing before upgrading to SAP S/4HANA. However it is possible to upgrade to SAP
S/4HANA without activating correspondence framework, but in that case you cannot create
correspondence in SAP S/4HANA until customizing for the Correspondence Framework is available
(which is an own project and needs time). If you are using old correspondence functionality and
upgrade to SAP S/4HANA from an older release in which correspondence framework is technically
not available, SAP recommends that you first upgrade to a release in which
correspondence framework is available and activate correspondence framework including necessary
customizing creation, before upgrading to SAP S/4HANA. However it is possible to upgrade to SAP
S/4HANA without activating Correspondence Framework, but in that case you cannot create
correspondence in SAP S/4HANA until customizing for the Correspondence Framework is available
(which is an own project and needs time).
Pre-Check
The pre-check for SAP S/4HANA transition issues a warning with check ID SI1_TCOR if business
function FIN_TRM_CORR_FW (more precise: switch FTRMO_SFWS_SC_C02S04_CORR) is not active
and at least one client exists in system in which correspondence was created with old
correspondence functionality within last year (database table VTBKORES contain according entry).
Information: SAP reserved clients 000 and 001 are exempt from the check. The warning message is
for your information. As described above SAP recommends that you first setup correspondence
framework before you upgrade to SAP S/4HANA as this project takes some time. If you are sure you
can run SAP S/4HANA without correspondence functionality you can upgrade to SAP S/4HANA
despite warning message. You can stop the warning message from appearing by activating business
function FIN_TRM_CORR_FW.
Simplification List for SAP S/4HANA 1610
267
2.1.26.11 Interest Rate and Yield Curve Functionality
Description
The classical yield curve functionality has been replaced by the more flexible yield curve framework,
which enables you to do the following:
Define reference interest rates with independent payment and compounding frequencies of
less than one year
Define basis spreads (tenor or currency spreads) and basis spread curves in market data
management
Add basis spread curves and credit spread curves to yield curves and account for them in net
present value calculations
Refer to note 1873119 for more information on the yield curve framework functionality and technical
availability. In SAP ERP, the yield curve framework can be activated via business function
FIN_TRM_YCF and a customizing activity. In S/4HANA, on-premise-edition, it is always active,
irrespective of the customizing setting.
Required and Recommended Action(s)
The definition of reference interest rates and yield curves in customizing differs between the classical
yield curve functionality and the yield curve framework. Therefore, the customizing needs to be
adapted when switching to the new yield curve framework. Report FTBB_YC_MIGRATE is available to
partly automate the necessary migration steps. If you upgrade to S/4HANA from a release in which
the yield curve framework is technically available, SAP recommends that you activate the yield curve
framework before upgrading to S/4HANA.
If you upgrade to S4/HANA directly from an older release, in which the yield curve framework is not
yet available, you have to perform the migration to the yield curve framework in S4/HANA before
you can continue using yield-curve related functionality, such as the calculation of NPVs with
transaction TPM60. Refer to note 1873119 and its related notes for more information on the yield
curve framework. The pre-upgrade-check for S4/H transition issues a warning with check ID
SI5_YCF if at least one client exists in the system in which the yield curve framework is not active, or
if the system is on a release level in which the yield curve framework is not yet technically available.
(Clients 000 and 001 are exempt from the check.)
How to Determine Relevancy
-
Use transaction SFW_BROWSER to check the activation status of object FIN_TRM_YCF .
If the business function is not activated, the classical interest rate and yield curve
functionality is active.
If the business function is activated, use transaction SPRO to check the status of the following
customizng activity:
Financial Supply Chain Management -> Treasury and Risk Management -> Basic Functions ->
Market Data Management -> Settings for Ref. Interest Rates and Yield Curves -> Activate
Yield Curve Framework
Simplification List for SAP S/4HANA 1610
268
-
If the Yield Curve Framework is activated in the customizing, the classical interest rate and
yield curve functionality is not technically in use anymore. Otherwise it is still active.
2.1.26.12 Commodity Risk Management
Description
Commodity Risk Management is switched off technically in SAP S/4HANA, on-premise edition 1511
and SAP S/4HANA 1610. The following main functional building blocks are deactivated:
Commodity master data
Market data management for commodity prices and price curves
Exposure Management for commodity price risk exposures
Financial transaction management for commodity derivatives
Market Risk Analyzer functionality for commodity derivatives and commodity price risk
exposures
Business Process-Related Information
Commodity Management cannot be activated within SAP S/4HANA on-premise edition 1511 and SAP
S/4HANA 1610.
Required and Recommended Action(s)
Execute the Conversion Pre-Checks. The central pre-transformation check checks 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 or SAP S/4HANA 1610 is not possible. The following Commodity Management Business
Functions have been deactivated in SAP S/4HANA, on-premise edition 1511 and SAP S/4HANA 1610:
FIN_TRM_COMM_RM
FIN_TRM_COMM_RM_2
LOG_TRM_INT_1
FIN_TRM_COMM_RM_3
FIN_TRM_COMM_RM_4
FIN_TRM_COMM_RM_5
FIN_TRM_COMM_RM_6
COMMODITY_MANAGEMENT_01
COMMODITY_MANAGEMENT_02
2.1.26.13 Credit Risk Analyzer Link to Cash Management
Description
Simplification List for SAP S/4HANA 1610
269
The link from classical Cash Management to the Treasury and Risk Management analyzers
(transactions RMCM and KLMAP) has been disabled in S4/HANA.
Required and Recommended Actions
Read the following information in case the Pre-Upgrade-Check in your system issues a message for
the check ID SI5_CM_TO_CRA "Classic cash management link to analyzers": The link from classic cash
management to the analyzers (transactions RMCM and KLMAP) is no longer supported in S/4HANA.
This check issues a warning if it finds entries in the corresponding customizing table KLCMMAPPING
in any client of the system. The warning message is for your information, no further mandatory
action is required. You can stop the warning message from appearing by removing all customizing
entries from table KLCMMAPPING (transaction KLMAP) in all clients of the system. Read the
following information in case the custom code analysis has detected customer coding related to this
transition worklist item: SAP objects which are used by the detected customer code are deprecated
and shall not be used any more. The customer code will not work anymore.
2.1.26.14 Exposure Management 1.0
The Exposure Management 1.0 is no longer the target architecture and has been disabled technically.
Exposure Management 2.0 is the more flexible and comprehensive successor application. There is no
standard migration tool from Exposure Management 1.0 to Exposure Management 2.0 though. You
have to set up Exposure Management 2.0 and transfer the data into the new application just in the
same way as if you had used another software system before and wanted to migrate to the SAP
solution. The basic functionality of the Exposure Management 2.0 is available with the business
functions TRM, Hedge and Exposure Management, New Financial Product (FIN_TRM_LR_FI_AN_2)
deliverd with SAP ERP 6.0 enhancement package 4. There are several other business functions, for
example, TRM, Enhancements in Exposure Management 2.0 (FIN_TRM_LR_FI_AN_4) delivered
with SAP ERP 6.0 enhancement package 7 . These business functions are always on in SAP S/4HANA.
Customers have to implement the Exposure Management 2.0 before they go to SAP S/4HANA.
-
-
If you are not using Exposure Management 1.0 and you do not plan to use Exposure
Management 2.0 you can upgrade to SAP S/4HANA without any difficulties.
If you are using Exposure Management 1.0 and upgrade to SAP S/4HANA from a release
in which Exposure Management 2.0 is technically available, SAP recommends that
you set up Exposure Management 2.0 and create necessary customizing before
upgrading to SAP S/4HANA. However it is possible to upgrade to SAP S/4HANA without
setting up Exposure Management 2.0, but in that case you cannot use Exposure
Management 2.0 in SAP S/4HANA until customizing for the Exposure Management 2.0 is
available (which is an own project and needs time).
If you are using Exposure Management 1.0 and upgrade to SAP S/4HANA from an older
release in which Exposure Management 2.0 is technically not available, SAP recommends
that you first upgrade to a release in which Exposure Management 2.0 is available and
set up the Exposure Management 2.0 including necessary customizing creation, before
upgrading to SAP S/4HANA. However it is possible to upgrade to SAP S/4HANA without
setting up Exposure Management 2.0, but in that case you cannot use Exposure
Management 2.0 in SAP S/4HANA until customizing for the Exposure Management 2.0 is
available (which is an own project and needs time).
Simplification List for SAP S/4HANA 1610
270
Read the following information in case the Pre-Upgrade-Check in your system issues a message for
the check ID SI6_EXP_MGT_10 "Exposure Management 1.0": This check issues a warning if it finds
entries in the database which means that exposures have been entered in at least one client in the
system. The warning message is for your information, no further mandatory action is required. Read
the following information in case the custom code analysis has detected customer coding related to
this transition worklist item: SAP objects which are used by the detected customer code are
deprecated and shall not be used any more. The customer code will not work anymore.
2.1.27 Financials – Miscellaneous
2.1.27.1 Credit Management
Description
Credit Management (FI-AR-CR) is not available as part of SAP S/4HANA. The functional equivalent in
SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR).
Business Process-Related Information
You need to migrate FI-AR-CR to FIN-FSCM-CR. This migration comprises several elements:
Configuration data
Master data
Credit exposure data
Credit decision data
The migration from one-system landscapes is supported by tools that SAP provides.
Influence on Business Processes
There will be no change to your business processes because of the migration. However, some
transactions become obsolete and are replaced by new transactions. Here are some examples for
such cases:
Examples for replaced
For the maintenance of the credit account master data, transaction
transactions in SAP S/4HANA FD32 is replaced by transaction UKM_BP.
For releasing credit-blocked sales orders, transaction VKM1 is
replaced by transaction UKM_MY_DCDS. To use transaction
UKM_MY_DCDS, the credit specialist might need additional
authorizations. As a workaround, the transactions VKM1 and VKM4
are still available.
Simplification List for SAP S/4HANA 1610
271
Transactions not available in F.28 - Customers: Reset Credit Limit
SAP S/4HANA
F.31 - Credit Management - Overview
F.32 - Credit Management - Missing Data
F.33 - Credit Management - Brief Overview
F.34 - Credit Management - Mass Change
FCV1 - Create A/R Summary
FCV2 - Delete A/R Summary
FCV3 - Early Warning List
FD24 - Credit Limit Changes
FD32 - Change Customer Credit Management (but FD33 still
available for Migration checks)
FDK43 - Credit Management - Master Data List
S_ALR_87012215 - Display Changes to Credit Management
S_ALR_87012218 - Credit Master Sheet
VKM2 - Released SD Documents
VKM3 - Sales Documents
VKM5 - Deliveries
Reports not available in SAP
S/4HANA
RFARI020 - FI-ARI: Extract from credit master data
RFARI030 - FI-ARI: Import credit master data
RFDFILZE - Credit Management: Branch/Head Office Reconciliation
Program
RFDKLI*NACC Reports
RFDKLxx Reports
The following settings in Customizing are affected by the migration:
All IMG activities for SAP Credit Management are listed in Customizing under the following
path: Financial Supply Chain Management > Credit Management.
The credit limit check for sales document types can only be specified as type D in SAP Credit
Management or can be left empty (no credit limit check). The credit limit check types A, B,
and C are no longer available.
The credit check when changing critical fields has been removed from the SD side.
The payment guarantee-related Letter of Credit has been removed from the SD side.
A credit check on the basis of the maximum document value is not supported in SAP
S/4HANA 1511 SP00 and SP01.
It is supported as of SAP S/4HANA 1511 FPS2.
Required and Recommended Action(s)
1. Prerequisites for the migration to SAP Credit Management:
You have completed all documents related to payment guarantee Letter of Credit.
You have completed the migration for Accounting.
Simplification List for SAP S/4HANA 1610
272
If you are running on your own code, you have eliminated the usage of SAP objects in your
own code. For details on how to adapt user-defined customer code that relies on the
changed objects, see the following SAP Notes:
o 2227014 (Financials)
o 2227014 (SD)
2. Perform the recommended actions in the Task List PDF attached to this Note (only available in
English). This list is only valid for the conversion of one-system landscapes.
Related SAP Notes
Custom code-related information (SD)
Custom code-related information (Financials)
SAP Note: 2217124
SAP Note: 2227014
2.1.27.2 Technical Changes in Material Ledger
This simplification makes it obligatory to use the Material Ledger (ML) which is now part of the
standard and automatically active in all SAP S/4HANA systems. Actual Costing (including Actual Cost
Component Split) is still optional. When an existing SAP system is converted to SAP S/4HANA, the
Material Ledger will be activated during the migration process (if not already active). If any additional
plants are added at a later point in time, the material ledger has to be activated for those plants
(valuation areas) manually via transaction OMX1. As a consequence of the close integration of
Material Ledger into sFIN processes, further simplification, refactoring, and process redesign has
been implemented. This has incompatible effects especially on database table design and therefore
direct SQL accesses to the affected tables.
The content of most of the former Material Ledger database tables is now stored in table ACDOCA
which allows simpler and faster (HANA optimized) access to the data. The attributes of the ML data
model that are relevant for the inventory subledger functionality are now part of table ACDOCA. The
former tables are obsolete. Therefore the following tables must not be accessed anymore via SQL
statements. In most cases a corresponding access function or class has been provided that must be
used instead.
Period Totals and Prices
o CKMLPP Material Ledger Period Totals Records Quantity
o CKMLCR Material Ledger: Period Totals Records Values
o Access function: CKMS_PERIOD_READ_WITH_ITAB
Material Ledger Document and associated views
o MLHD
o MLIT
o MLPP
o MLPPF
o MLCR
o MLCRF
o MLCRP
o MLMST
Simplification List for SAP S/4HANA 1610
273
Access functions: CKML_F_DOCUMENT_READ_MLHD,
CKML_F_DOCUMENT_READ_MLXX
o Further tables (with no access function): MLKEPH, MLPRKEKO, MLPRKEPH
o Obsolete database views: MLXXV, MLREPORT, MLREADST
Index for Accounting Documents for Material
o CKMI1
o Obsolete, no further access possible
o
In addition, some further simplifications have to be taken into account:
Separate currency customizing of Material Ledger (transactions OMX2 / OMX3) is now
mandatory. The Material Ledger acts on the currencies defined for the leading ledger in
Financials.
There is no default Material Ledger Type 0000 anymore.
Customizing in Financial applications allows you to assign more than three currency and
valuation types as being relevant in your company code. As the Material Ledger still supports
only three currency and valuation types, it is no longer allowed to use an ML Type that
references currency settings defined in FI or CO (flags Currency Types from FI and Currency
Types from CO). Instead you have to explicitly define the currency and valuation types that
are relevant for the Material Ledger.
Steps to be executed:
1. Use transaction OMX2 to define the currency and valuation types that are relevant for the
Material Ledger.
2. Then use transaction OMX3 to assign this ML Type to your valuation area.
See also note https://i7p.wdf.sap.corp/sap/support/notes/2291076
Material Price Analysis (transaction CKM3 / CKM3N)
The transaction CKM3/CKM3N was refactored and now provides a simplified and improved
view of materials in plants with active Actual Costing. It replaces the former CKM3 view Price
Determination Structure.
The former CKM3 Price History view is still available via transaction CKM3PH for all materials
(independent of price determination control and active Actual Costing).
All other views formerly offered by CKM3/CKM3N are no longer available.
For details about new Actual Costing simplification, please check the corresponding upgrade
information SAP Note.
2.1.27.3 Real Estate Classic
Description
SAP Real Estate Management is the real estate solution from SAP. From SAP ECC up to and including
SAP ERP 6.0, SAP has provided two versions of the real estate solution. The older version is "Real
Estate Classic (RE Classic)" and the new version is "Real Estate Flexible (RE-FX)" (see SAP Note
443311). The editions SAP S/4HANA on premise 1511 and SAP S/4HANA Finance 1503 (and all other
OP versions) do not support Real Estate Classic (RE Classic). The business requirements can be
covered by using Real Estate Flexible (RE-FX) functionality. As RE-FX is the more up-to-date solution
Simplification List for SAP S/4HANA 1610
274
and has a much broader functional scope (see SAP Note 517673), only RE-FX is included as the RE
component in the SAP S/4HANA on-premise edition.
Business Process related information
Before the system conversion to SAP S/4HANA, on-premise edition 1511 (or SAP S/4HANA Finance
edition 1503, or higher releases), customers who use RE Classic need to migrate RE Classic to RE-FX
as part of a migration project. It is not possible to migrate after switching to SAP S/4HANA.
Customers have to be aware, that it is not possible anymore to view and display classic RE data in S/4
HANA. Migrating data from Classic RE to RE-FX is not a simple technical conversion. Similar to a
legacy data transfer, the migration must be planned as a project and executed. In this sense, the
migration programs are the technical support for the data transfer project. A migration project can
be more or less time consuming depending on how complex your data is, the capacity in which you
work with customer developments and the extent to which you use the RE-FX functions.
For more information, see SAP Note 828160.
2.1.27.4 SAP Data Aging for SAP S/4HANA Finance
You must note the following things or implement the corresponding corrections:
Adjustment of the customer programs during an access to aggregates and application indexes
for Financial Accounting (SAP Note 2076652). The following adjustments are required for all
SAP Simple Finance releases. SAP standard programs are adjusted with the delivery of SAP
Simple Finance 1.0.
Adjustment of customer programs during access to the general ledger view in conjunction with
the entry view (SAP Note 2143420). The described adjustments are required only if you have
already moved FI documents to the historic part of the database for SAP Simple Finance 1.0
and if you use SAP Simple Finance 1503 or above. Adjustments to SAP standard programs were
delivered with SAP Note 2164573.
Adjustment of customer programs during access to CO/ML/AA data from the database in
conjunction with archived data (SAP Note 2170778 for CO, SAP Note 2190816 for ML, SAP Note
2190818 for AA). This is required as of SAP Simple Finance 1503. Adjustments to SAP standard
programs were not required.
Adjustment of customer programs during access to old CO/ML data. In addition to the archive,
data in the historic area of the database is accessed. Consulting note 2190841 and SAP Note
2175897 are available for SAP standard programs.
Adjustment of aging object FI_DOCUMENT for journal entry. SAP Note 2178388 is a
prerequisite for the use of the aging run as of SAP Simple Finance 1503.
Adjustment of existing archiving. With SAP Simple Finance 1503, some tables are no longer
archived or are only written to the archive as copies. This is due to the fact that this
information is now persisted in the journal entry. A further consequence of this and of the
migration to the new persistence is restricted reload options for archiving objects that offer
these.
Simplification List for SAP S/4HANA 1610
275
For some adjustments, corrections were necessary after the delivery of the release. These are listed
in case they are suitable for use as templates for your own corrections. Note that pure corrections
are not collected here.
The FAQ note 2190848 for SAP Data Aging in SAP Simple Finance is also available.
2.1.27.5 Conversion to S/4HANA 1610 Material Ledger and Actual Costing
This simplification makes it obligatory to use the Material Ledger (ML) which is now part of the
standard and automatically active in all SAP S/4HANA systems. Actual Costing (including Actual Cost
Component Split) is still optional. When an existing SAP system is converted to SAP S/4HANA, the
Material Ledger will be activated during the migration process (if not already active). If any additional
plants are added at a later point in time, the material ledger has to be activated for those plants
(valuation areas) manually via transaction OMX1. As a consequence of the close integration of
Material Ledger into sFIN processes, further simplification, refactoring, and process redesign has
been implemented. This has incompatible effects especially on database table design and therefore
direct SQL accesses to the affected tables.
Description
The content of most of the former Material Ledger database tables is now stored in table ACDOCA
which allows simpler and faster (HANA optimized) access to the data. The attributes of the ML data
model that are relevant for the inventory subledger functionality are now part of table ACDOCA. The
former tables are obsolete. Therefore the following tables must not be accessed anymore via SQL
statements. In most cases a corresponding access function or class has been provided that must be
used instead.
Period Totals and Prices
o CKMLPP Material Ledger Period Totals Records Quantity
o CKMLCR Material Ledger: Period Totals Records Values
o Access function: CKMS_PERIOD_READ_WITH_ITAB
Material Ledger Document and associated views
o MLHD
o MLIT
o MLPP
o MLPPF
o MLCR
o MLCRF
o MLCRP
o MLMST
o Access functions: CKML_F_DOCUMENT_READ_MLHD,
CKML_F_DOCUMENT_READ_MLXX
o Further tables (with no access function): MLKEPH, MLPRKEKO, MLPRKEPH
o Obsolete database views: MLXXV, MLREPORT, MLREADST
Index for Accounting Documents for Material
o CKMI1
o Obsolete, no further access possible
Simplification List for SAP S/4HANA 1610
276
In addition, some further simplifications have to be taken into account:
Separate currency customizing of Material Ledger (transactions OMX2 / OMX3) is now
mandatory. The Material Ledger acts on the currencies defined for the leading ledger in
Financials.
There is no default Material Ledger Type 0000 anymore.
Customizing in Financial applications allows you to assign more than three currency and
valuation types as being relevant in your company code. As the Material Ledger still supports
only three currency and valuation types, it is no longer allowed to use an ML Type that
references currency settings defined in FI or CO (flags Currency Types from FI and Currency
Types from CO). Instead you have to explicitly define the currency and valuation types that
are relevant for the Material Ledger.
Steps to be executed:
1. Use transaction OMX2 to define the currency and valuation types that are relevant for the
Material Ledger.
2. Then use transaction OMX3 to assign this ML Type to your valuation area.
See also note https://i7p.wdf.sap.corp/sap/support/notes/2291076
Material Price Analysis (transaction CKM3 / CKM3N)
The transaction CKM3/CKM3N was refactored and now provides a simplified and improved
view of materials in plants with active Actual Costing. It replaces the former CKM3 view Price
Determination Structure.
The former CKM3 Price History view is still available via transaction CKM3PH for all materials
(independent of price determination control and active Actual Costing).
All other views formerly offered by CKM3/CKM3N are no longer available.
For details about new Actual Costing simplification, please check the corresponding upgrade
information SAP Note.
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2352383
Conversion to S/4HANA 1610 Material Ledger and Actual
Costing
Business Impact
2354768
Technical Changes in Material Ledger with Actual Costing
Business Impact
2332591
Technical Changes in Material-Ledger
2.1.28 Globalization
2.1.28.1 Globalization – Financials
2.1.28.1.1 Description
With the installation of the SAP S/4HANA 1511, certain country-specific transaction codes and
programs in the application area of Financials have been replaced with newer transactions or
Simplification List for SAP S/4HANA 1610
277
programs (compared to EhP7 for SAP ERP 6.0). For more details about the affected transactions and
programs and their replacements, refer to SAP Notes 2029012 and 2227963.
2.1.28.1.1 Related SAP Notes
SAP Note
2227963 SAP S/4HANA, on-premise edition 1511 and SAP S/4HANA Finance 1605 :
Obsolete transaction codes and programs in Financials localizations
2029012 SAP Simple Finance: Obsolete transaction codes and programs in Financials
localizations
2.1.28.2 Globalization – Logistics
2.1.28.2.1 Description
The following functionality related to Country Version for Brazil is not available in SAP S/4HANA
1511:
Legal Books and Fixed Asset taxes credit (ICMS and PIS/COFINS).
TAXBRJ Tax procedure has restricted maintenance but it is still available for compatibility reasons.
2.1.28.2.2 Required and Recommended Action(s)
SAP recommends using the following:
TAXBRA tax procedure for the tax calculation.
SAP Tax Declaration Framework for Fiscal and Accounting Legal Reporting.
Note: SAP Tax Declaration Framework is part of the Compatible Add-ons and requires an additional
license.
2.1.28.2.3 Related SAP Notes
General
Custom Code related information
SAP Note: 2244803 - Fiscal and Accounting Legal Reporting for
SAP S/4HANA, on premise edition 1511
SAP Note: 2195701
2.1.29 Human Ressource
2.1.29.1 General HCM Approach within SAP S/4HANA
Description
SuccessFactors, the next generation HCM suite in the public Cloud, is the go-forward HCM solution
for both editions of SAP S/4HANA, cloud and on premise. Productized integration exists today so
Simplification List for SAP S/4HANA 1610
278
customers can easily connect these solutions. Customers choosing SAP S/4HANA as their nextgeneration business suite deserve a next-generation HCM suite and this is the focus of
SuccessFactors. SuccessFactors connect easily with SAP S/4HANA with productized integration based
on HCI content
Productized Integrations among SuccessFactors with SAP S/4HANA on-premise based on HCI content
will be available with SAP S/4HANA, on-premise edition 1511. SAP S/4HANA customers may also
using SAP ERP HCM on-premise and might not be willing/able to move to SuccessFactors in the near
term and like to continue to use SAP ERP HCM. SAP HCM can be run in either a separate instance or
single instance with SAP S/4HANA. The integration among both on-premise instances (SAP HCM with
SAP S/4HANA on-premise) will be available via ALE in case SAP HCM is running on separate instance.
In case SAP HCM is running inside of SAP S/4HANA on-premise then the integration is
automatically given as part of so-called Compatibility Mode.
Business Process related information
When using S/4HANA and SAP HCM in one system (Compatibility Mode), then only the Software
components SAP-HR and EA-HR are still available in SAP S/4HANA. The go-to architecture in the HCM
area is SuccessFactors, in particular SAP SuccessFactors Employee Central for Core HR, SAP
SuccessFactors Learning for Learning, and SAP SuccessFactors Recruiting Management for Recruiting.
It´s not planned to provide application simplifications based on the traditional SAP HCM
functionalities. As example: It is not planned to offer Fiori-based user interfaces for these traditional
functionalities. SAPGui based functionality stay unchanged for those customers unable to make the
move to SuccessFactors in the near term.
Required and Recommended Action(s)
The go-to architecture in the HCM area is SuccessFactors. Accordingly it is recommended to move
the human resources-related functionalities to SuccessFactors.
2.1.29.2 Conversion of Employees to Business Partners
Description
SuccessFactors, the next generation HCM suite in the public Cloud, is the go-forward HCM solution
for both editions of SAP S/4HANA, cloud and on premise. Productized integration exists today so
customers can easily connect these solutions. Customers choosing SAP S/4HANA as their nextgeneration business suite deserve a next-generation HCM suite and this is the focus of
SuccessFactors. SuccessFactors connect easily with SAP S/4HANA with productized integration based
on HCI content. Productized Integrations among SuccessFactors with SAP S/4HANA on-premise based
on HCI content are available with SAP S/4HANA, on-premise edition 1511. SAP S/4HANA customers
may also using SAP ERP HCM on-premise and might not be willing/able to move to SuccessFactors in
the near term and like to continue to use SAP ERP HCM. SAP HCM can be run in either a separate
instance or single instance with SAP S/4HANA. The integration among both on-premise instances
(SAP HCM with SAP S/4HANA on-premise) will be available via ALE in case SAP HCM is running on
Simplification List for SAP S/4HANA 1610
279
separate instance. In case SAP HCM is running inside of SAP S/4HANA on-premise then the
integration is automatically given as part of so-called Compatibility Mode.
Business Process related information
The new data model in S/4HANA is based on Business Partners (BP). A BP must be assigned to
each employee.
Required and Recommended Action(s)
After transformation to S/4HANA, the migration report /SHCM/RH_SYNC_BUPA_FROM_EMP must
be executed before productive use of the system. Due to customizing dependencies, the report
cannot be executed in technical downtime.
2.1.29.3 SAP Learning Solution
For details see corresponding Business Impact Note.
2.1.29.4 SAP E-Recruiting
For details see corresponding Business Impact Note.
2.1.29.5 Java-Based ESS and MSS
For details see corresponding Business Impact Note
2.1.30 Industry – Cross Industry Functionality
2.1.30.1 BRIM - Billing of Event Data Records (EDR)
2.1.30.1.1 Description
EDR Management is used to transfer event detail records (EDR) from an external system, manage the
received information and prepare it for billing. Instead of the EDR Management you can use the
Billing of Billable Items. The BRIM solution covers CRM, CI / FI-CA (ERP) and SAP Convergent Charging
components/systems. The Event Data Records Solution was developed to charge and to bill single
events like Toll Collects or downloads. This Solution was replaced by BIT BILLING since 2008.
2.1.30.1.2 Business Process related information
No influence on business processes expected. All EDR Customer are informed about this
2.1.30.1.3 Required and Recommended Action(s)
None
Simplification List for SAP S/4HANA 1610
280
2.1.30.2 BRIM - Common Object Layer (COL)
2.1.30.2.1 Description
The Common Object Layer Framework (COL framework) can be used to distribute data (e.g. master
data, provider contracts) from SAP CRM System into SAP Convergent Charging and SAP ERP System.
In SAP S/4HANA 1511 the distribution between these systems is done directly, the framework is not
provided any more. The BRIM solution covers CRM, FI-CA (ERP) and SAP Convergent Charging
components/systems. The Common Object Layer was developed in SAP_APPL to provide the
technical possibility to distribute master data from ERP to SAP Convergent Charging without using
the software component FI-CA. However, no customer used this feature. The BRIM solution is always
used with FI-CA or CI component. Thus, the Common Object Layer is not available in SAP S/4HANA
1511. The distribution of objects is now done directly in software component FI-CA.
2.1.30.2.2 Business Process related information
No influence on business processes expected for customers: the master data distribution still works
in SAP S/4HANA On Premise.
2.1.30.2.3 Required and Recommended Action(s)
None
2.1.30.3 BRIM - Integration with FSCM Biller Direct (FI-CA)
2.1.30.3.1 Description
With the integration of SAP Contract Accounts Receivable and Payable (FI-CA) with FSCM Biller Direct
it is possible to offer to end-customers the convenience of receiving invoices, viewing account status,
and making payments online as a self-service. The functionality is not considered as the target
architecture, but the Customer can still continue to use the functionality to make the upgrade to S/4
less disruptive5.
2.1.30.3.2 Business Process related information
The functionality Biller Direct with FI-CA is not the target architecture, but still available and can be
used within SAP S/4HANA 1511.
2.1.30.3.3 Required and Recommended Action(s)
None
5
Functionality available in SAP S/4HANA 1511 delivery but not considered as future technology. Functional
equivalent is not available yet.
Simplification List for SAP S/4HANA 1610
281
2.1.30.4 BRIM - Solution Sales and Billing
2.1.30.4.1 Description
The BRIM solution / hybris Billing covers CRM, CI / FI-CA (ERP) and SAP Convergent Charging
components / Systems. Provider contracts are created from CRM. For the integration of provider
contracts in SAP Contract Accounts Receivable and Payable, SAP Convergent Invoicing and finally SD
Billig with FI-AR, the provider contracts need additional information for processing in SD. In
additional to that business agreements assigned to a business partner need to be created
automatically in background without replication in CRM. As the follow up processing of CI Billing
Documents in SD Billing is currently not available within SAP S/4HANA, on-premise edition, this
feature is not provided. Billing and Invoicing of consumption data is still possible within FI-CA but not
with SD and FI-AR. In addition to that the BRIM SD deployment variant was developed to invoice
consumption data also in SD billing with accounting in FI-AR. This solution is currently not available
within Sap S/4HANA, on-premise edition 1511. Therefore the additions on the provider contract with
SD Biliing relevant data and the background creation of contract accounts in ERP without existing
contract accounts in CRM is not required.
UPDATE:
The integration of CI Billing Documents in SAP Convergent Invoicing into SD Billing is meanwhile
available for S/4HANA as "SAP S/4HANA for Subscription Billing, Salesand Distribution Option 1.0" as
part of Hybris Billing. For further details please check note 2347269 Release stategy of the ABAP AddOn SOLINVE 800. Therefore the business function FICAX_SOLESALESBILL has been reenabled and set
to customer switchable. for further detials check note 2348426 - Reactivation of Business Function
FICAXSOLSALESBILL.
2.1.30.5 BRIM – Immediate Master Data Replication to SAP Convergent Charging
2.1.30.5.1 Description
In SAP S/4HANA 1511, the master data replication from FI-CA to SAP Convergent Charging is only
supported as joint replication. For example master data (business partners, contract accounts, prepaid accounts) are only replicated to SAP Convergent Charging if the data for the related provider
contract is received in FI-CA. This means that the master data of business partners, contract
accounts, and prepaid accounts cannot be replicated independently of each other and immediately
to SAP Convergent Charging any more.
2.1.30.5.2 Business Process related information
No influence on business process since the master data replication (as Joint Master Data Replication
approach) still works in S/4HANA On Premise.
2.1.30.5.3 Required and Recommended Action(s)
One of the following business functions needs to be activated:
•
FICAX_INV_2G
Simplification List for SAP S/4HANA 1610
282
•
ISU_INV_2G
•
PSCD_COLLECTIONS_MANAGEMENT_4G
•
TEL_INV_2G
Afterwards, the joint master data replication needs to be activated in the IMG customizing under
Contract Accounts Receivable and Payable -> Integration -> Convergent Charging Activate Joint
Replication of All Master Data. For further activities, please refer to the documentation of this IMG
activity.
2.1.31 Industry Banking
2.1.31.1 SEM Banking
2.1.31.1.1 Description
The SEM Banking functionality is not included in SAP S/4HANA. Larger parts of the SEM Banking
functionality have already been replaced by the Bank Analyzer (part of the Banking platform
"Banking Services from SAP"), but it's important to note there are still functions, which have no
successor. A technical disablement of SEM Banking was done as follows:
The SEM Banking menu was disabled (hidden)
The SEM Banking IMG was disabled (hidden)
Central SEM Banking transactions will terminate with an "A-message"
It's not allowed to execute SEM Banking transactions anymore.
2.1.31.1.2 Business Process related information
The whole SEM Banking application with its parts "Datapool", "Profit Analyzer", "Risk Analyzer" and
"Strategy Analyzer" won't be offered in the context of SAP S/4HANA.
Transaction not
All SEM Banking related transaction codes for "Datapool", "Profit
available in SAP S/4HANA Analyzer", "Risk Analyzer" and "Strategy Analyzer".
2.1.31.1.3 Required and Recommended Action(s)
Users of SEM Banking have to evaluate alternatives to the usage of SEM Banking in SAP S/4HANA
systems (e.g. replacement of SEM Banking functionality by the Bank Analyzer or keeping SEM
Banking on a separate ERP installation).
2.1.31.1.4 How to Determine Relevancy
There is an active risk management area and / or there is an active Banking operating concern in
the system
Simplification List for SAP S/4HANA 1610
283
2.1.31.1.5 Related SAP Notes
Custom Code related information
For more details see SAP Note 2211665
2.1.32 Industry Beverage
2.1.32.1 IS-Beverage Cleanup
2.1.32.1.1 Description
2004 IS-Beverage has been moved to ERP core. Some parts of the former IS solution were heavy
modifying the core. These parts have been moved to ERP too but have never been made functional
available for customers. Repository and DDIC objects of those functionalities were assigned to
packages with either the name /BEV*OBSOLETE* or the short text contained OBSOLETE and those
are not available from the system now.
2.1.32.1.2 Business Process related information
No influence on business processes expected.
2.1.32.1.3 Required and Recommended Action(s)
None
2.1.32.1.4 Related SAP Notes
Custom Code related information
SAP Note: 2224144
2.1.32.2 IS-Beverage solution
2.1.32.2.1 Description
In 2014 the IS-Beverage solution has been moved to ERP. Some of the functionalities were never
available for ERP customers whereas others are available but there are not much customers using
those functionalities. For the IS-Beverage functionality Sales Returns there is the successor Advanced
Return Management available. For the IS-Beverage functionality Excise Duty - which is released for
German alcohol tax only - there will be right now no successor available.
The IS-Beverage functionality Empties Management is still available but maybe replaced later by a
successor functionality.
2.1.32.2.2 Business Process related information
If you are using IS-Beverage Sales Returns (SR) then you need to set up the SD functionalities
Advanced Return Management (ARM). The processes flows of SR and ARM are mostly different. For
details see the corresponding documentations.
If you are using IS-Beverage Excise Duty you may contact SAP CD for a customer solution.
Simplification List for SAP S/4HANA 1610
284
Transaction not available in SAP S/4HANA
All the Beverage related transactions are not
available within SAP S/4HANA
2.1.32.2.3 Required and Recommended Action(s)
None
2.1.32.2.4 Related SAP Notes
Custom Code related information
SAP Note: 2224144
2.1.32.3 Beverage Empties Management and Pendulum List
2.1.32.3.1 Description
The functionalities of IS Beverage Empties Management and Pendulum List functionalities are not
available within SAP S/4HANA 1511. The Beverage Empties Management and Pendulum List
functionalities are on the roadmap for SAP S/4HANA.
Remark:
The Beverage Empties Management and Pendulum List is related to Business Function EA-CP.
In SAP S/4HANA 1511 the status of Business Function EA-CP is defined as "always_off". If a
business function was switched on in the start release system, but defined as "always_off" in
the target release, then a system conversion is not possible. It is planned to change the state
of Business Function EA-CP so that a system conversion is possible for customers having
business function EA-CP switched on.
Customers having Business Function EA-CP not switched on in the start release system
cannot switch on this Business Function in SAP S/4HANA.
2.1.32.3.2 Business Process related information
The Beverage Empties Management and Pendulum List functionalities are not available within SAP
S/4HANA 1511. Accordingly the related business processes are not available within SAP S/4HANA.
Transaction not available in
SAP S/4HANA
/BEV1/EM0
Material Sorting Variant
/BEV1/EM1
Form for Material Sorting Variant
/BEV1/EM2
Maintenance of Print Indicator
/BEV1/EM3
Maintenance Empties Material Types
/BEV1/EM4
Maintenance of Empties Materials
/BEV1/EM5
Empties: Assign Item Categories
/BEV1/EMA
Empties Balance
/BEV1/EMB
Archive Monthly Empties Stock
/BEV1/EMC
Reload Monthly Empties Stock
/BEV1/EMD
Archive Empties Update
/BEV1/EME
Reload Empties Update
/BEV1/EMF
Delete Reloaded Empties Records
/BEV1/EMN
Empties Update Number Assignment
/BEV1/EMS
Empties Evaluation
/BEV1/EM_MIGERP01 Empties Migration
Simplification List for SAP S/4HANA 1610
285
/BEV1/NEMB51 Material Document List (w. Empties)
/BEV1/NE_LISTBALPO Empties Balances in Purchasing
/BEV4/PLAA
Display Sales Request Data
/BEV4/PLAC
Change Sales Request Data
/BEV4/PLAE
Correction of Incorrect Confirmation
/BEV4/PLAF
Aut. Filling of Update Determination
/BEV4/PLAN New Creation of Sales Request Data
/BEV4/PLCA
Display Customizing Pendulum List
/BEV4/PLCU
Pendulum List Customizing
/BEV4/PLEA
Reported Sales Import
/BEV4/PLER
Manual Entry Confirmation
/BEV4/PLFA
Display Update Determination
/BEV4/PLFC
Change Update Determination
/BEV4/PLFN
Create Update Determination
/BEV4/PLGN Report Generation of Request
/BEV4/PLKA
Display Assignment Nos Customers
/BEV4/PLKC
Change Assignment Nos Customers
/BEV4/PLKK
Schedule Job Update
/BEV4/PLKM Update
/BEV4/PLKN
Creation of Assignment Nos Customers
/BEV4/PLPL
Area Menu Pendulum List
/BEV4/PLPQ
Subsequent Output
/BEV4/PLPR
Check Outstanding Sales
/BEV4/PLRS
Cancel Confirmation Pendulum List
/BEV4/PLSF
Create Order for Confirmation
/BEV4/PLSS
Cancelation of a Request Run
/BEV4/PLST
Cancelation Request Pendulum List
/BEV4/PLUA Display Conversion Extern. Materials
/BEV4/PLUB
Schedule Job: Import Master Data
/BEV4/PLUC
Change Conversion External Materials
/BEV4/PLUD Schedule Job: Import Sales
/BEV4/PLUE
Import Master Data Ext. Customers
/BEV4/PLUJ
Schedule Job to Generate Request
/BEV4/PLUK
Correction of Incorrectly Read Data
/BEV4/PLUN Creation for Conversion Ext. Matl.
/BEV4/PLUP
Logs Sales Pendulum Lists
/BEV4/PLVF
Create Orders After Request Termintd
2.1.32.3.3 Required and Recommended Action(s)
None
Simplification List for SAP S/4HANA 1610
286
2.1.33 Defense & Security
2.1.33.1 DFPS eSOA services
The enterprise services (eSOA services) for DFPS are not available in SAP S/4HANA, on-premise
edition 1511. Currently there is no functional equivalent available within SAP S/4HANA, on-premise
edition 1511. Depending on customer requests they may be replaced by OData services in the future.
All related objects do still exist, therefore no technical problems (like syntax errors) will occur. The
services have been marked as "not released". The use of these eSOA services with SAP S/4HANA, onpremise edition 1511 is in the customer's responsibility only.
2.1.33.2 DFPS BI content
BI content, Data Sources and Extractors for DFPS are not available in SAP S/4HANA, on-premise
edition 1511. Depending on customer requests they may be replaced by real-time operational
reporting with SAP S/4HANA Embedded Analytics utilizing Virtual Data Models, and CDS-Views in the
future. All related objects do still exist. The use of these within SAP S/4HANA, on-premise editon
1511 is in the customer's responsibility only. In case of transitioning from ERP Business Suite to
S/4HANA, check existing BI content based on DFPS extractors. Start exploring the new possibilities
for real-Time operational reporting using SAP S/4HANA Analytics which enables a key user to create
and modify reports, KPIs or any other analytical artefacts according to their needs.
2.1.33.3 Integration of DFPS with Investigative Case Management (ICM)
Description
The integration of DFPS with the CRM solution of Investigative Case Management is not available in
SAP S/4HANA due to missing customer adoption in the SAP Business Suite. There is no functional
equivalent available in SAP S/4HANA.
Business Process related information
The features provided by the activation of Business Function DFPS_ICM_OF are not available in SAP
S/4HANA, e.g.
Necessary technical prerequisites for accessing Organizational Flexibility functions from a
CRM system for implementing the Investigative Case Management System.
Display of the assignment of a case ID to an operation in the Structures Workbench
application.
Assignment of a position to a force element via the A/B 290 relationship to specify which
position is responsible for an operation as the operation planner.
Required and Recommended Action(s)
Implement Business Scenarios and Business Processes based on the functionality available within SAP
S/4HANA.
How to Determine Relevancy
Simplification List for SAP S/4HANA 1610
287
Check in transaction SFW5, whether Business Function DFPS_ICM_OF is available and has been
activated in your existing SAP Business Suite system.
2.1.33.4 Integration of DFPS with Environmental Compliance
Description
The integration of DFPS with Environmental Compliance is not available in SAP S/4HANA, due to the
simplification of the central EH&S solution making Business Function OPS_EC_INTEGRATION
(Environmental Compliance Integration in Enterprise Asset Management) obsolete. There is no
functional equivalent available in SAP S/4HANA.
Business Process related information
Business function OPS_EC_INTEGRATION, and as a consequence the DFPS-related features provided
by the Business Function, are not available in SAP S/4HANA, e.g.
Distribution of Facility Master Data from Environmental Compliance
Generation, import and archiving of Checklists (PDF Forms)
Check SAP Note 1161250 for additional information on those topics.
Required and Recommended Action(s)
Implement Business Scenarios and Business Processes based on the functionality available within SAP
S/4HANA.
How to Determine Relevancy
The simplification item is possibly relevant if Business Function OPS_EC_INTEGRATION
(Environmental Compliance Integration in Enterprise Asset Management) is active in your existing
SAP Business Suite system. You can check the status via transactions SFW_BROWSER (Switch
Framework Browser) or SFW5 (Switch Framework Customizing). Customers having Business Function
OPS_EC_INTEGRATION switched ON in Business Suite can execute the system conversion.
evertheless the functionality related to the Business Function is not available within SAP S/4 HANA.
Customers not having the Business function switched ON in Business Suite cannot activate it after the
system conversion to SAP S/4 HANA.
2.1.34 Industry DIMP – Aerospace & Defence
2.1.34.1 Collective Processing Pegging
Description
Simplification List for SAP S/4HANA 1610
288
With SAP S/4HANA, transaction PEG01 (Pegging: Collective Processing) and its programs are not
available. The old transaction PEG01 is replaced by transaction PEG01N (A&D GPD Pegging: Collective
Processing).
Business Process related information
Transaction PEG01 (Pegging: Collective Processing) is not available with SAP S/4HANA. Customers
need to use transaction PEG01N as the successor transaction.
Transaction not available in SAP S/4HANA
Transaction PEG01 (replaced by PEG01N)
Required and Recommended Action(s)
Start using transaction PEG01N in SAP S/4HANA and educate the end user.
Related SAP Notes
Custom code related information
SAP Note 2200942
2.1.34.2 Cost Distribution Processing
Description
With SAP S/4HANA, transaction DIS01 (Cost Distribution Processing) and its program are not
available. The old transaction DIS01 is replaced by the new transaction DIS01N (GPD Cost
Distribution: Collective Processing).
Business Process related information
Transaction DIS01 (Cost Distribution Processing) is not available with SAP S/4HANA. Customers need
to use transaction DIS01N as the successor transaction.
Transaction not available in SAP S/4HANA
Transaction DIS01 (replaced by DIS01N)
Required and Recommended Action(s)
Start using transaction DIS01N in SAP S/4HANA and educate the end user.
Related SAP Notes
Custom Code related information
SAP Note: 2200942
Simplification List for SAP S/4HANA 1610
289
2.1.34.3 Manufacturer Part Number
Description
The functionality for the Manufacturer Part Number (MPN) is not available in SAP S/4HANA 1511.
Refer to SAP Note 2270836 for more information. The industry solution for the manufacturer part
number is changed technically in SAP S/4HANA 1610. The newly redesigned solution for
Manufacturer Part Number will be available from SAP S/4HANA 1610 onwards.
The below points specify details about the changes at the technical level as well as the changes with
respect to configuration of the MPN in SAP S/4HANA 1610:
How MPN will be stored and rendered
In SAP S/4HANA 1610 release, MPN has been technically redesigned. MPN material number will be
stored as key(MATNR) in MARA table. Hence conversion exit which was used in earlier releases, is no
longer relevant.
MPN Material number is the concatenation of Manufacturing Part number and External
Manufacturer separated by the delimiter specified in Logistics - General --> Interchangeability of
Parts --> Specify Settings for Inventory-Managed MPN.
eg: Manfuacturing Part number = 'MPN123' External Manufacturer = 'MANF1' Delimiter = ':', then
the MPN Material number formed will be 'MPN123:MANF1'.
If Manufacturer Part number is a numerical Material number and no manufacturer is specified, then
the part number will suffixed with the delimiter specified in the customizing settings
eg: Manufacturer Part number = 1234 and External Manufacturer = ' ', then MPN Material number
formed will be '1234:'.
The above behavior is relevant only if 'Concatenated Material No.' option is selected for the material
type of the MPN Material.
Concatenation checkbox in material types
MPN functionality is activated when you select 'Activate Inventory-Managed MPN' in the
Customizing. You can reach the new settings using the path: Logistics - General --> Interchangeability
of Parts --> Specify Settings for Inventory-Managed MPN.
From the SAP S/4HANA 1610 release onwards, Inventory Managed MPN will be created as the
material number (MARA-MATNR) itself.
The MPN attributes like MFRPN and EMNFR are maintained in the initial screen of the material
master.
Simplification List for SAP S/4HANA 1610
290
These fields are editable only if the following settings are enabled in the 'Material Type' Customizing
by following the path: Logistics-General -->Material Master --> Basic Settings --> Material Types -->
Define Attributes of Material Types
'Concatenated Material No.' field should be enabled.
For more information related to the settings, refer to the documentation of the field 'Concatenated
Material No.'.
MPN numbers can no longer be changed once created in SAP S/4HANA
In the ECC-DIMP systems, MPN number can be maintained as an additional value for the material in
the 'Basic Data1' tab as well as in 'Purchasing' view.
With the help of the conversion exit, MPN values were displayed as the material number.
In SAP S/4HANA, this approach is not available due to its shortcoming like performance impact and
maintenance effort.
Also with the extension of material field length to 40 characters, it will be possible to use the field for
storing the MPN material number.
MPN materials will be stored and displayed as the material number itself. Hence the name of the
MPN material cannot be changed once created.
This behavior is enabled only if 'Concatenated Material No.' indicator is enabled in the respective
'Material Type' Customizing.
MPN data held in MIGO transaction will not be converted in SAP S/4HANA
MIGO transaction enables saving of MPN data for a user using the option 'Hold' so that it could be
reused later in the application.
During migration to SAP S/4HANA, this MPN data will not be converted.
Hence MPN data thus saved before migration cannot be used in SAP S/4HANA.
Customer needs to maintain the entry again.
Non-MPN materials that contain MFRPN (Manufacturer Part Number) will have different
behavior in SAP S/4HANA
In the ECC-DIMP system, if the DIMP 'Conversion exit' is activated, then the external material
number stored in the table MATERIALID field MATNR_EXT will be displayed instead of the material
number. The external material number will be populated in the case of LAMA and MPN.
Simplification List for SAP S/4HANA 1610
291
This behavior is enabled irrespective of the material type. For material type HALB, if the MPN
information is maintained in the 'Purchasing' view tab in the material master and 'Conversion exit' is
activated from the Customizing, the MPN material will be displayed instead of the generated
material number.
In SAP S/4HANA, the following behavior is different. If the MPN is activated and concatenation
checkbox is enabled in the respective material type Customizing, MPN information maintained in the
material master will be displayed and stored as the material number itself. Otherwise the MPN
information will behave as a normal attribute of a material.
Individual attributes of the material MFRPN (Manufacturer Part Number) and EMNFR
(External Manufacturer) should not be updated in SAP S/4HANA
If the concatenation checkbox is enabled for a material type, then the individual attributes MFRPN
and EMNFR should not be updated manually. This will lead to inconsistencies in the master data.
In SAP S/4HANA, MPN material number is derived by concatenating Manufacturing Part Number and
External Manufacturer in the material master. Hence it is restricted to change these MPN attributes
once the material is created through the UI as well as SAP-delivered APIs.
This restriction is applicable only if MPN is enabled with the concatenation checkbox in the
Customizing.
Customer should ensure that the MPN material should not get modified in SAP S/4HANA.
Following online transaction will not work after system conversion with MPN materials in
SAP S/4HANA
Transactions MM17 and MMCC are not available for MPN materials in SAP S/4HANA.
Use of new APIs for interacting with SAP S/4HANA system from non-SAP S/4HANA system
during material creation
While transferring a material created in the non-SAP S/4HANA to SAP S/4HANA system using any API,
the RFC-enabled function module MPN01_MATNR_DERIVE should be called by giving destination as
SAP S/4HANA system. This function module will return the MPN material number confirming with
the SAP S/4HANA system.
For more information, refer to the documentation of the function module MPN01_MATNR_DERIVE.
Report variants will be ignored during migration to SAP S/4HANA
Screen variants that are created in ECC-DIMP system will be ignored during migration to SAP
S/4HANA.
Customer needs to create the variants again in the SAP S/4HANA.
Simplification List for SAP S/4HANA 1610
292
Parts Interchangeability in SAP S/4HANA
The Parts interchangeability functionality earlier part of the ECC-DIMP is now available as part of SAP
S/4HANA 1610. The functionality is decoupled from MPN (Manufacturer Part Number) and works
without an MPN material. Additionally the ECC-DIMP fields of vendor master are available as part of
business partner fields in SAP S/4HANA 1610. The Purchasing view of business partner role "FLVN01
Vendor " is enhanced with the Interchangeability tab.
Required and Recommended Action(s)
Refer to the below SAP Notes before performing the system conversion to SAP S/4HANA:
2334012
2334008
2270836
SAP Notes
2.1.34.4 Flight Scheduling
Description
The DIMP A&D Flight Scheduling solution functionality is not available with SAP S/4HANA. A&D Flight
Scheduling solution was developed, but never released for productive use for customers.
Business Process related information
No influence on business processes expected no productive use for customer.
Required and Recommended Action(s)
No actions required from the customer side.
Related SAP Notes
Custom code related information SAP Note: 2382229
2.1.34.5 Enhancements Actual Labour Costing / Time Recording
Description
The DIMP Enhancements Actual Labour Costing / Time Recording functionality is not available with
SAP S/4HANA. DIMP Enhancements Actual Labour Costing / Time Recording (See SAP Note 1856717
2013) was never released to the customer.
Simplification List for SAP S/4HANA 1610
293
No further developments are planned in this area.
Purpose of function
Read-only directory traversal in Activity Allocation Conversion IS-ADEC-ALC contains a vulnerability
through which an attacker can potentially read arbitrary files on the remote server, possibly
disclosing confidential information.
Business Process related information
Report 'RAD02_PROJBASED_OP_IT_LIST' is not available in SAP S/4HANA. No influence on business
processes expected no productive use for customer
Required and Recommended Action(s)
None
2.1.34.6 Enhancements Subcontracting Special Stock Types Not Available
Description
DIMP Enhancements Subcontracting special stock types "SC RTP" (I), "SC Vendor consignment" (J),
"Customer Stock" (B), "SCCustomerOrderStock" (F) are not available within SAP S/4HANA 1511.
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Knowledge Transfer to the end user about the non availability of the special stocks in SAP S/4HANA
1511. "Customer Stock" (B) and "SCCustomerOrderStock" (F) will be available as a part of the future
releases of SAP S/4HANA.
2.1.34.7 AECMA SPEC 2000M Military Version
Description
Enhancements AECMA SPEC 2000M Military version is not available in SAP S/4HANA. Consider using
the solution SPEC2K Interface for ATA SPEC 2000.
Related SAP Notes
Pre Check
2349033
Simplification List for SAP S/4HANA 1610
294
Custom code check 2382203
2.1.35 Industry – Automotive
2.1.35.1 Tracking Inbound
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECC-DIMP) for
tracking of inbound deliveries and shipments is not available with SAP S/4HANA. To calculate and
track the exact time of arrival, the recipient of goods could use the tracking of inbound deliveries and
shipments. Event information could be received via EDI message with type TRXSTA and processed
with reference to an inbound delivery or inbound shipment. The event location had to be defined as
node of a route assigned to the delivery or shipment document. The event time is used then to
calculate the expected time of arrival based on the duration information stored with the route for
scheduling. The automotive industry solution for tracking of inbound deliveries and shipments has a
low customer adoption rate. With SAP Transportation Management, a much more comprehensive
and scalable solution exists.
Business Process related information
The industry-specific solution for tracking of inbound deliveries and shipments is not available with
SAP S/4HANA.
How to Determine Relevancy
The Simplification Item is relevant, if:
EDI messages of message type TRXSTA have been processed (check for entries with MESTYP
= 'TRXSTA' in table EDIDC with transaction SE16)
Required and Recommended Action(s)
Evaluate SAP Transportation Management to manage and track shipments and related deliveries
before conversion to SAP S/4HANA. Archive EDI messages of message type TRXSTA before
conversion to SAP S/4HANA.
Related SAP Notes
Custom Code Check
SAP Note 2228139
Simplification List for SAP S/4HANA 1610
295
2.1.35.2 Supplier Workplace
Description
The Supplier Workplace (SWP) is an early collaboration solution in SAP ERP Discrete Industries & Mill
Products (ECC-DIMP), enabling suppliers to access supplier-related data directly from the SAP ERP
system of a company in addition or as an alternative to EDI communication. With SWP, the company
could allow their suppliers to display purchasing documents and price information, view and confirm
scheduling agreement releases, create, change or display inbound deliveries, view goods receipt and
settlement information, and returnable packaging account information. The Supplier Workplace has
a low customer adoption rate, is not strategic and the technology used is no longer the target
architecture, therefore it will be not available with SAP S/4HANA. With SAP Ariba and Ariba Networks
or SAP Supply Network Collaboration (SNC), there are successors available.
Business Process related information
Implementing a successor solution for supplier collaboration will result in a change in the IT system
landscape and integration as well as in the business applications used for supplier collaboration. Not
all scenarios covered by SWP are supported by the successor products.
ISAUTO_SICASN1, ISAUTO_SICASN2, ISAUTO_SICASN3,
ISAUTO_SICASN4, ISAUTO_SICBC, ISAUTO_SICCO, ISAUTO_SICDDL1,
ISAUTO_SICENG, ISAUTO_SICIV, ISAUTO_SICJIT, ISAUTO_SICPDI,
Transactions not available
ISAUTO_SICPH, ISAUTO_SICPI, ISAUTO_SICRL,
in SAP S/4HANA
ISAUTO_SICRLRD, ISAUTO_SICRPM, ISAUTO_SICSR, ISA_SICALERT,
ISA_SICKANBAN, ISI_BCI, ISI_BCO, ISI_POD, ISI_PR,
ISIPI_CP, ISIPI_CS, ISIPI_ESP, ISIPI_OEPM, ISIPI_POD, ISIPI_PUL,
ISIPI_SM, ISIPI_SUMJIT, ISIPI_TRACK, ISIT_PR, SIC_MA, SIC_MD, ME69
How to Determine Relevancy
The Simplification Item is relevant, if:
The industry switch AM_SWP is active (check with transaction SFW1), and
Supplier Workplace users have been assigned to vendors (check for entries in table
ISAUTOSICVENDTAB with transaction SE16)
Required and Recommended Action(s)
Evaluate SAP Ariba / Ariba Networks or SAP Supply Network Collaboration as successor or alternative
solution. Remove all Supplier Workplace users assigned to vendors from table ISAUTOSICVENDTAB.
Related SAP Notes
Pre Check
Custom Code Check
SAP Note 2326822
SAP Note 2228218
Simplification List for SAP S/4HANA 1610
296
2.1.35.3 External Service Providers
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECC-DIMP) for
managing supplier stock at External Service Providers (ESP) is not available in SAP S/4HANA. The
solution had been addressed to companies purchasing direct material from vendors who put the
products to stock at an ESP for replenishment to the customer. The stock at the ESP is still owned by
the vendor until the supply to the customer who requests a just in time replenishment directly from
the ESP to the production. An EDI message with type STOACT allowed the transmission of the current
vendor stock for each product in inventory at the ESP; the inbound processing compared that stock
information with the current vendor consignment stock at a defined storage location assigned to the
ESP and posted the differences. It was recommended to exclude the ESP storage location from MRP
to not consider the vendor's stock into account when planning and creating delivery schedules. For
evaluation reasons, the vendor consignment stock at ESP storage locations could be included when
defining selection rules for the stock/requirements list.
Business Process related information
The automotive solution for managing supplier stock at external service providers (ESP) had a very
low adoption rate and is not available in SAP S/4HANA. Managing vendor consignment stock in
general is available in SAP S/4HANA and stock at storage locations could be separated in MRP by
defining specific storage location MRP areas.
Transactions not available in SAP S/4HANA
OESP, ESPLOG, ESPLOGD
How to Determine Relevancy
The Simplification Item is relevant, if:
Plant and storage location parameters for ESP processing have been maintained (check for
entries in tables ESPPL and ESPST with transaction SE16), and
EDI messages of message type STOACT have been processed (check for entries with MESTYP
= 'STOACT' in table EDIDC with transaction SE16)
Required and Recommended Action(s)
Evaluate a redesign of the affected business process before the conversion to SAP S/4HANA. Remove
all entries in tables ESPPL and ESPST before the conversion to SAP S/4HANA. Archive all EDI messages
of message type STOACT before the conversion to SAP S/4HANA.
Related SAP Notes
Custom Code Check
SAP Note 2228219
Simplification List for SAP S/4HANA 1610
297
2.1.35.4 Cross-System Transit between Two Plants
Description
The automotive industry solution for cross-system transit between two plants addressed the need to
manage stock in transit between different plants of a company operating in different SAP ERP
systems. The goods issue posting at the supplying plant resulted in a goods movement posting to the
stock in transit of the receiving plant using a remote function call in the target system. The goods in
transit are then managed and valuated automatically by the receiving plant. A goods receipt in the
receiving plant then resulted in a transfer posting from the stock in transit to a storage location stock.
The automotive industry solution focused especially on the usage of scheduling agreements for
procurement between the plants. That solution had a very low adoption rate and is not available in
SAP S/4HANA.
Business Process related information
The automotive industry solution for managing stock in transit for goods transferred between two
plants of a company operating in different systems is not available in SAP S/4HANA.
Transactions not available in S/4HANA
XLOC, XLOR, XLOS
How to Determine Relevancy
The Simplification Item is relevant, if:
Purchasing documents exist with document types maintained for cross-system stock in
transit (check first for entries in table T161 with XLOKZ <> initial with transaction SE16; use all
BSART found in T161 to check for entries in table EKKO with transaction SE16)
Sales documents exist with schedule lines with movement types for cross-system stock in
transit (check for entries with BWART = '6A1', '6A3', '6AA' or '6AC' in table VBEP with
transaction SE16)
The transaction codes XLOC, XLOR or XLOS are used
Required and Recommended Action(s)
Evaluate a redesign of the affected business process before the conversion to SAP S/4HANA. Archive
all purchasing documents with document types maintained for cross-system stock in transit before
the conversion to SAP S/4HANA. Archive all sales documents with the movement types for crosssystem stock in transit or remove all related schedule lines before the conversion to SAP S/4HANA.
Related SAP Notes
Pre Check
Custom Code Check
SAP Note 2349033
SAP Note 2228220
Simplification List for SAP S/4HANA 1610
298
2.1.35.5 Long Material Number
Description
In SAP ERP, the automotive industry solution for the long material number did not extend the
material number used as key and reference field in database tables. Instead it provided an additional
extended representation of the material number up to 40 characters and a conversion from the 18
characters internal representation to the external representation and vice versa. The external
representation has been entered and displayed on user interfaces and has been added to technical
interfaces like BAPIs and IDOCs. The solution is activated with business function MGV_LAMA. It had
restrictions and with its necessary conversions between an internal and external representation, it
is suboptimal from a performance perspective. In SAP S/4HANA, the material number is natively
extended to 40 characters, therefore the automotive industry solution for the long material number
is obsolete and will not be supported. For more information on the material number field length
extension in SAP S/4HANA, see SAP Note 2267140. A conversion to SAP S/4HANA 1511 is not
supported; In SAP S/4HANA 1511, the business function MGV_LAMA is set to "Always off".
Business Process related information
The industry solution for long material numbers has been replaced by a natively extended material
number, clearly beneficial with regards to simplification, performance and integration. The industry
solution for long material numbers and its replacement by an extended material number requires a
database conversion replacing the internal representation of the material number by the external
representation. Not in all cases it will be an identical exchange and not in all cases an exchange might
be supported. Interfaces like BAPIs, IDocs or Webservices had been extended by the industry
solution for long material numbers, and they had been extended additionally for the natively
extended material number. The interfaces might not provide the material numbers in exactly the
same way before and after the conversion. A compatability mode is provided to support
the interface extensions of the industry solution for long material numbers. For more details on
conversion to S/4HANA with respect to long material numbers, refer to SAP Note 2360860.
How to Determine Relevancy
The Simplification Item is relevant, if:
The Business Function MGV_LAMA has been activated (check with transaction SFW2 or
SFW_BROWSER).
Required and Recommended Action(s)
Consider SAP Note 2384347 for proceeding with the conversion to SAP S/4HANA.
Related SAP Notes
Restrictions
SAP Note 2384347
Simplification List for SAP S/4HANA 1610
299
Pre-Check
SAP Note 2326776
Custom Code Check SAP Note 2228241
2.1.35.6 Material Version
Description
The automotive industry solution for material versions in SAP ERP Discrete Industries & Mill Products
(ECC-DIMP) is based on the industry solution for the long material number which is activated using
the business function MGV_LAMA. The implementation of the long material number will be
fundamentally changed in SAP S/4HANA, and considering the limited functionality and value of the
solution for material versions and the very low customer adoption rate, that solution will be not
available with SAP S/4HANA.
Features of the material versioning solution in SAP ERP Discrete Industries & Mill Products
When material versioning had been activated in SAP ERP, a version could be created with reference
to a non-versioned material (called "header material"). Each version is created as an own material
master, uniquely identified by the material number of the header material and its version ID. The
master data maintenance of a material version is controlled by the version type and the logistics
switch. The version type specified with each material version created defines which material
attributes are version-specific and could be maintained for each version independently (like it is valid
for non-versioned material) and which shall be equal for the header material and all its versions. For
these attributes, a change will be applied to the header material and all other versions
simultaneously. The logistics switch controls whether logistics-relevant views could be maintained for
a material version or not. One reason is to create material versions for documentary reasons like
minor changes in drawings etc. Another reason is to use material versions in logistics only in early
phases of product development where changes occur often and continue in the mature phases of the
lifecycle with the header material only. Except for the master data maintenance, the only application
specifically handling material versions is the BOM explosion from iPPE (Integrated Product and
Process Engineering). An iPPE could be maintained just using header materials as components, so
new material versions do not require the maintenance of iPPE objects. During BOM explosion, a valid
material version with active logistics switch is dynamically determined and the header material
replaced by its version if found. The validity for material versions is determined via ECM (Engineering
Change Management) which is obligatory for material versions to be used. All other applications do
not distinguish between header material and material versions. A conversion to SAP S/4HANA 1511 is
not supported; In SAP S/4HANA 1511, the business function MGV_LAMA is set to "Always off".
Business Process related information
The automotive industry solution for material versions is not available with SAP S/4HANA. Material
versions as material master referring to a header material with version ID and version type could not
be maintained. Instead, material versions could be maintained as other materials with a material
number combining the header material number and the version ID. Version type specific material
master maintenance, logistics switch and material version determination during iPPE explosion
according to the validity defined in ECM is not supported.
Simplification List for SAP S/4HANA 1610
300
Transactions not available in S/4HANA MMLS, TCLSVERS, VTCU
How to Determine Relevancy
The Simplification Item is relevant, if:
The Business Function MGV_LAMA has been activated (check with transaction SFW2), and
Material versions have been activated (check TMCNV-MVAKT = 'X' with transaction SE16),
and
Material versions have been maintained (check for entries in table MATERIALID, field
MATNR_VERS with transaction SE16)
Required and Recommended Action(s)
A conversion of material versions is not supported by the standard conversion tools for long material
numbers. Create an incident on application component IS-A-LMN with short text "S4HANA
conversion for material versions required" to get support in converting material versions to normal
material numbers in SAP S/4HANA.
Related SAP Notes
Pre-Check
Custom Code Check
SAP Note 2326776
SAP Note 2228242
2.1.35.7 Planning Regular Route Shipments
Description
The automotive industry solution for planning inbound shipments for regular routes based on route
schedules in SAP ERP Discrete Industries & Mill Products (ECC-DIMP) is not available in SAP S/4HANA.
Regular routes like milk-run tours lead to recurrent shipments. Route schedules could be defined as
basis for generating these recurrent inbound shipments. Inbound deliveries created based on
shipping notifications from suppliers could be directly linked as items to the generated inbound
shipments. The inbound shipments could then be used for goods receipt processing collectively for
all inbound deliveries shipped together. Planning regular route shipments has a low customer
adoption and is not available in SAP S/4HANA. With SAP Transportation Management, a new solution
for planning, executing and settling shipments is available.
Business Process related information
In SAP S/4HANA, the automotive industry solution for maintaining schedules for regular routes and
planning and creating inbound shipments based on route schedules is not available.
Simplification List for SAP S/4HANA 1610
301
Transactions not available in SAP S/4HANA
VL51A, VL52A, VL53A, VL54A
How to Determine Relevancy
The Simplification Item is relevant, if:
Route schedules have been maintained (check for entries in table BORRTTS with transaction
SE16)
Route schedule determination records have been maintained (check for entries in table
BORRTFI with transaction SE16)
Required and Recommended Action(s)
Evaluate SAP Transportation Management for planning and scheduling shipments before conversion
to SAP S/4HANA. Remove route schedules and route schedule determination records before
conversion to SAP S/4HANA.
Related SAP Notes
Custom Code Check
SAP Note 2227568
2.1.35.8 BSP based Dealer Portal
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECC-DIMP) includes
two different Dealer Portals. For simplification reasons, only one Dealer Portal solution is supported
in SAP S/4HANA. The Dealer Portal based on Discrete Industries Web Interface (DIWI) and Business
Server Pages (BSP) is not available in SAP S/4HANA. The successor Web Dynpro based Dealer Portal,
introduced with SAP ERP 6.04 and accessible via SAP Netweaver Business Client, is available in SAP
S/4HANA. The Web Dynpro based Dealer Portal allows managing vehicle sales, spare parts
procurement, and warranty claim processing in collaboration with dealers.
Business Process related information
The Dealer Portal based on Discrete Industries Web Interface (DIWI) and Business Server Pages is not
available with SAP S/4HANA. The Web Dynpro based Dealer Portal is recommended as successor
application. The user interface changes by the Dealer Portal switch, but the business processes are
not affected.
How to Determine Relevancy
The Simplification Item is relevant, if:
Simplification List for SAP S/4HANA 1610
302
a user to partner mapping for the BSP based Dealer Portal exists (check for entries in
database table /SAPDII/CUSPRMAP with transaction SE16), or
a logical system to RFC destination mapping for the BSP based Dealer Portal exists (check for
entries in database table /SAPDII/CSYSRFCM with transaction SE16), or
a partner to system mapping for the BSP based Dealer Portal exists (check for entries in
database table /SAPDII/CPRSYSM with transaction SE16).
Required and Recommended Action(s)
The migration to the Web Dynpro based Dealer Portal is recommended before doing the system
conversion to SAP S/4HANA. For migration purposes, move
the user to partner mapping for the BSP based Dealer Portal to the one for the Web Dynpro
based Dealer Portal with transaction DPCOMMON_MAP_U_P
the logical system to RFC destination mapping for the BSP based Dealer Portal to the one for
the Web Dynpro based Dealer Portal with transaction DPCOMMON_MAP_S_R
the partner to system mapping for the BSP based Dealer Portal to the one for the Web
Dynpro based Dealer Portal with transaction DPCOMMON_MAP_P_S
A training for dealer users regarding the Web Dynpro based Dealer Portal is expected to be required.
Enhancements to the BSP based Dealer Portal have to be reimplemented for the Web Dynpro Dealer
Portal, if applicable. Remove the settings for the BSP based Dealer Portal after migrating to the Web
Dynpro based Dealer Portal before doing the system conversion to SAP S/4HANA.
Related SAP Notes
Custom Code Check
SAP Note 2228244
2.1.36 Industry: DIMP – Engineering, Construction & Operations
2.1.36.1 Obsolete BAPIS of Bill of Services (BOS)
Description
Certain BAPIs provided for the Bills of Services functionality are not available in SAP S/4HANA.
Business Process related information
As an alternative, you could use other provided BAPIs for the Bills of Services functionality.
Required and Recommended Action(s)
Check if the BAPIs included in the piece list are used in custom code. If yes, you must adapt the
custom code.
Simplification List for SAP S/4HANA 1610
303
2.1.36.2 BOS Cost Transfer to PS removed
In SAP S/4 HANA the Bills of Services (BOS) functionality is available to be used.
Nevertheless be aware that the related functionality is considered to be a Non-Strategic-function.
Restrictions:
In SAP S/4 HANA Bills of Services functionality transfer cost to the Project is no longer
available . Please contact SAP via a customer message
2.1.36.3 ZDEP ETM CATS package
-
The package /SAPCEM/CATT is replaced with the package /SAPCEM/CATT_REPORT.
SCAT test cases /SAPCEM/BAL90, /SAPCEM/BGL91 are replaced with the reports
/SAPCEM/BAL90, /SAPCEM/BGL91
Please use the replaced objects which are in the form of reports.
for other objects in the package /SAPCEM/CATT has no equivalent objects or reports
available as of SAP S/4HANA 1610
2.1.36.4 ETM General
Description
ETM functionality is available from SAP S/4HANA 1610 release with the possibility of creating ETM
master data recipient as a business partner. Customers who used ETM functionality in their earlier
ERP releases will have to plan ETM recipient data migration to business partner. A conversion to SAP
S/4HANA 1511 is not supported. In SAP S/4HANA 1511, ETM is not available.
Business Process Related Information
There is no change in ETM functionality except the changes to ETM recipient. Nevertheless the
related functionality is classified in the simplification list as Non-Strategic-function
Required and Recommended Action(s)
Please consider to convert the ETM recipient related customer master records to business partner
records. Refer to the SAP Note 2265093. Ensure that you perform the following pre-requisite
steps during conversion of ECC DIMP ETM recipient to Business partner :
1. Perform additional Customizing for ETM recipient:
a) Create an ETM-specific grouping and assign it to a business partner number range
b) Assign the ETM-specific grouping to the J3G account group
Simplification List for SAP S/4HANA 1610
304
2. Ensure that the Customizing settings from the Customizing client are copied to the productive
client
3. Ensure that the business partner assignment is set to required or optional entry in the customizing
transaction OBD2- ( As mentioned in steps below)
a) Choose customer account group J3G
b) Double-click Sales data in the Field status group box
c) Double-click Partner usage in the Select Group group box
d) Set the Business partner assignment as required or an optional entry
Restrictions:
Graphical Planning Board Transaction for ETM: As part of the ETM enablement the Graphical
Planning Board transaction is as well available via the classic SAP GUI Client. Nevertheless due to
technical limitation the Graphical Planning Board transaction is not availabe as an SAP Fiori Visual
Theme for classic applications and SAP Fiori Launchpad.
2.1.36.5 ETM Tables obsolet
Certain tables in the ETM package are not required anymore. Therefore, these tables are removed.
There is no change in functionality.
Business Process related information
No change in the process.
Required and Recommended Action(s)
No action required.
2.1.36.6 REAL ESTATE SALES (HOMEBUILDING)
The Home Building Solution (HBS) will not be available in SAP S/4HANA. Before doing a system
conversion to SAP S/4HANA, check if HBS functionality was active in your system. As HBS
functionality is not available in SAP S/4HANA, all HBS related data would be lost during conversion.
Please ensure that you take necessary steps to backup HBS data. Objects under ECO_HBS and
ECO_HBS_APP switches and objects under DI_HBS and DI_HBS_APP packages will not be available
after system conversion. SAP Note 2343388 gives more detailed information on the objects
which will not be available after conversion.
Simplification List for SAP S/4HANA 1610
305
2.1.37 Industry: DIMP – High Tech
2.1.37.1 Manufacturing Execution Systems
Description
Industry Solution High Tech Manufacturing Execution (IS-HT-MES) was an add-on solution developed
for High Tech semiconductor manufacturers. This solution is used to track the semiconductor
manufacturing process using process orders, with enhanced capabilities around lot split, lot merge,
lot rework, lot genealogy, lot inheritance, lot search and Statistical Process Control (SPC) quality
inspection. Support for IS-HT-MES was made unavailable starting with ECC-DIMP 6.0 EhP4 (see SAP
Note 1162438). Similarly, IS-HT-MES is also not available with SAP S/4HANA. Depending on the
customer business process, SAP S/4HANA may address certain of the requirements that were
addressed by IS-HT-MES.
Business Process related information
Transactions
not available in
SAP
S/4HANA
/SAPHT/MESCL30 - Batch Characteristic Search
/SAPHT/MESZMLG - Batch Genealogy
/SAPHT/MESZPRM - Formula parameter dynamic generation
/SAPHT/SPCZQ02 - QM: SPC Review Control Chart
2.1.37.2 RosettaNet
Description
Industry Solution HighTech RosettaNet (IS-HT-RN) was an add-on solution providing and RNIF
adapter to support B2B collaboration for the RosettaNet industry standard. Support for IS-HT-RN was
made unavailable starting with ECC-DIMP 6.0 EhP4 (see SAP note 1168556). Similarly, IS-HT-RN is not
available with SAP S/4HANA, and there is no successor functionality available in SAP S/4HANA.
Business Process related information
/SAPHT/RN_DUNS - RosettaNet Building Block: DUNS implementation
/SAPHT/RN_GTIN1 - RosettaNet Building Block: GTIN implementation
Business Add-Ins not
/SAPHT/RN_USER_DUNS - RosettaNet Building Block: DUNS implementation available in SAP S/4HANA User exit
/SAPHT/RN_USER_GTIN - RosettaNet Building Block: GTIN implementation - User
exit
Simplification List for SAP S/4HANA 1610
306
2.1.37.3 Software License Management
Description
Software License Management was part of the IS-HT-SW industry solution. It supports business
processes for licensing software, such as: Software License creation, Version Change processing,
Product Bundle creation, Software License pricing. IS-SW and thus Software License Management
capabilities are not available in SAP S/4HANA. There is currently no functional equivalent available in
SAP S/4HANA.
Business Process related information
Transaction not available in
SAP S/4HANA
VB“Y Billi g Pla “
h o izatio
2.1.37.4 Installed Base Management
Description
Installed Base Management was part of the IS-SW industry solution. It used the SAP Installed Base
(IBASE) database to manage software licenses, with capabilities including: business data inheritance,
license bump processing, IBASE record splits. IS-SW and thus Installed Base Management capabilities
have not been brought in to SAP S/4HANA. There is no specific, targeted successor solution in SAP
S/4HANA for these capabilities.
Business Process related information
Transaction not available in
SAP S/4HANA
PASW - Partner Inheritance Switch
2.1.37.5 Contract Management Enhancements
Description
Contract Management Enhancements was part of the IS-SW industry solution. It enhanced standard
capabilities for managing contracts, such as: sold-to party eligibility, contract availability period,
contract messages, contract assignment, and price protection. It also provided more of a usability
enhancement to manage multiple business partners as part of a contract list. IS-SW and thus
Contract Management Enhancements capabilities have not been brought in to SAP S/4HANA. There
is no specific, targeted successor solution in SAP S/4HANA for these capabilities. However, some
basic contract management capabilities have been moved in to SAP S/4HANA. Although managing
business partners in the contract is done in a different way, e.g., add individual business partners
(sold-to parties) versus a contract list.
Simplification List for SAP S/4HANA 1610
307
2.1.37.6 Billing Process Enhancements
Description
Billing Process Enhancements was part of the IS-SW industry solution. It provided billing plan
synchronization and billing plan type determination, specifically to link/synchronize billing plans and
with software license orders, e.g., if the software license order was changed from 10 to 15 users then
the previous order would be closed and a new one created/linked. IS-SW and thus Billing Process
Enhancements capabilities are not available with SAP S/4HANA. There is no specific, targeted
successor solution in SAP S/4HANA for these capabilities.
2.1.37.7 Software Maintenance Processing
Description
Software Maintenance was part of the IS-SW industry solution. It supports the process of distributing
new levels of software code to licensed customers, specifically: maintenance level management
(MLM), to distribute maintenance code/corrections/fixes; and Version Change Protection (VCP), to
automatically a new software product or version change to licensed customers (providing a new
license). IS-SW and Billing Process Enhancements capabilities are not available in SAP S/4HANA.
There is no specific, targeted successor solution in SAP S/4HANA for these capabilities.
Business Process related information
Transaction not available in
SAP S/4HANA
OK32 - SMP Order Due List
OK30 - Software Maintenance Process
OK36 - SMP Log
2.1.37.8 User Exits in DRM
Description
Distributor Reseller Management (DRM) was part of the Discrete Industries and Mill Products (DIMP)
industry solution. DRM supports business processes for the distribution and resale of High Tech
products, from the perspective of both a High Tech Manufacturer and a Distributor. It provided
capabilities such as ship-and-debit agreements, sell-in and sell-through distribution, drop-shipment
to distributor customer, ship-and-debit claims processing, price change and price protection. User
Exits in DRM• provided specific user-exit enhancements to the core DRM solution. All of these user
exits are Business Add-Ins (BAdIs). DRM is not available in SAP S/4 HANA and thus User Exits in DRM•
is also not available SAP S/4HANA. Within SAP Business Suite, DRM had been superseded by the SAP
CRM Channel Management for High Tech solution. SAP Channel Management for High Tech solution
is not available with SAP S/4HANA.
Simplification List for SAP S/4HANA 1610
308
2.1.37.9 Condition Technique in DRM: Rule Configuration
Description
Distributor Reseller Management (DRM) was part of the Discrete Industries and Mill Products (DIMP)
industry solution. DRM supports business processes for the distribution and resale of High-Tech
products, from the perspective of both a High-Tech Manufacturer and a Distributor. It provided
capabilities such as ship-and-debit agreements, sell-in and sell-through distribution, drop-shipment
to distributor customer, ship-and-debit claims processing, price change and price protection.
Condition Technique in DRM: Rule Configuration provided rules configuration enhancements to the
core DRM solution, specifically to treat claims differently depending on parameters such as tracking
partner, sales area, material, etc. Within SAP Business Suite, DRM had been superseded by the SAP
CRM Channel Management for High Tech solution. DRM and thus Condition Technique in DRM: Rule
Configuration have not been brought into SAP S/4HANA. SAP Channel Management for High Tech is
also not available in SAP S/4HANA. There is no specific, targeted successor solution in SAP S/4HANA
for these capabilities.
2.1.37.10 Manufacturer/Supplier Processes
Description
Distributor Reseller Management (DRM) was part of the Discrete Industries and Mill Products (DIMP)
industry solution. DRM supports business processes for the distribution and resale of High Tech
products, from the perspective of both a High Tech Manufacturer and a Distributor. It provided
capabilities such as ship-and-debit agreements, sell-in and sell-through distribution, drop-shipment
to distributor customer, ship-and-debit claims processing, price change and price protection.
Manufacturer/Supplier Processes• provided the core capabilities for High Tech Manufacturers.
Within SAP Business Suite, DRM had been superseded by the SAP CRM Channel Management for
High Tech solution. DRM and thus Manufacturer/Supplier Processes• have not been brought into
SAP S/4HANA, nor has SAP Channel Management for High Tech been brought into SAP S/4HANA.
Thus, there is no specific, targeted successor solution in SAP S/4HANA for these capabilities.
Business Process related information
Transactions not available in SAP
S/4HANA
DRMPPMS_C - Price Protection (Create Due List)
DRMPPMS_P - Price Protection (Change/Process Due List)
DRMPPMS_D - Price Protection (Display Due List)
D‘MPPM“ P i e P ote tio (Background Processing)
D‘MCLM“ “hip-and-Debit
D‘MBUM“ Bill-up
D‘MI‘M“ I e to ‘e o iliatio
D‘MLMM“ Ma ual Lot Mai te a e
D‘M‘ M“ “AP T a sa tio s
Simplification List for SAP S/4HANA 1610
309
D‘M“TGM“ D‘M “tagi g A ea
D‘MXM‘PT T a s issio ‘epo t
D‘MCDM“ Dis epa
i “hip-and-Debit Claims
D‘MM“BU“MET Busi ess Met i s
D‘MPCM“ P i e P ote tio Co e tio ‘epo t
D‘MPEM“ Pa t e Validatio ‘epo t
2.1.37.11 Distributor/Reseller Processes
Description
Distributor Reseller Management (DRM) was part of the Discrete Industries and Mill Products (DIMP)
industry solution. DRM supports business processes for the distribution and resale of High Tech
products, from the perspective of both a High Tech Manufacturer and a Distributor. It provided
capabilities such as ship-and-debit agreements, sell-in and sell-through distribution, drop-shipment
to distributor customer, ship-and-debit claims processing, price change and price protection.
Distributor/Reseller Processes• provided the core capabilities for HighTech Manufacturers. Within
SAP Business Suite, DRM had been superseded by the SAP CRM Channel Management for High Tech
solution. DRM and thus Distributor/Reseller Processes have not been brought into SAP S/4HANA, nor
has SAP Channel Management for HighTech been brought into SAP S/4HANA. Condition Technique in
DRM: Rule Configuration is not available in SAP S/4HANA. Thus, there is no specific, targeted
successor solution in SAP S/4HANA for these capabilities.
Business Process related information
Transactions not available /SAPHT/DRMPPDR_C - Price Protection (Create Due List)
in SAP S/4HANA
/SAPHT/DRMPPDR_P - Price Protection (Change/Process Due List)
/SAPHT/DRMPPDR_D - Price Protection (Display Due List)
/“APHT/D‘MPPD‘ P i e P ote tio Ba kg ou d P o essi g
/“APHT/D‘MCLD‘ “hip-and-Debit
/“APHT/D‘MBUD‘ Bill-up
/“APHT/D‘M‘ D‘ T a sa tio s T a ki g & P o essi g
/“APHT/D‘M“TGD‘ P o essi g of “tagi g Ite s
/“APHT/D‘MLMD‘ Ma ual Lot Mai te a e
/“APHT/D‘MIAD‘ I alid “hip a d De it Ag ee e ts epo t
/“APHT/D‘MD‘BU“MET Busi ess Metrics report
/“APHT/D‘MIM‘CN I e to Ma age e t
Reconciliation report
/“APHT/D‘M“L“‘POUT D‘M “ales epo t
Simplification List for SAP S/4HANA 1610
310
2.1.38 Industry DIMP – Mill
2.1.38.1 Non ferrous metal processing
Description
Non Ferrous Metal Processing functionality enables to consider fluctuating metal prices in area of
Sales and Purchasing pricing. In SAP ERP the functionality is part of Industry Solution Mill Products. In
parallel in SAP ERP the new Solution SAP Commodity Management is available. SAP Commodity
Management is for SAP the strategic solution with new innovations. It is planned to replace the Non
Ferrous Metal (NFM) functionality in longterm. In SAP S/4HANA on-premise edition 1511 release the
NFM functionality is available, but defined as "not strategic any more". See SAP note 2269324 Compatibility Scope Matrix for SAP S/4HANA, on-premise edition. As SAP Commodity Management is
not yet included in S/4HANA, the NFM functionality is still available in this release for time being.
Business Process related information
In S/4HANA on-premise edition 1511 the SD and MM-PUR documents does not get default value in
field exchange key (the key for the stock exchange, e.g. LME). User must enter this information
manually into the SD/MM documents. Reason: Customer / Vendor master transactions are combined
into new Business Partner transaction "BP". The NFM field Exchange key is not available anymore in
transaction "BP" and therefore can not passed over to SD / MM documents.
Required and Recommended Action
No special actions for Non Ferrous Metal customers during transition from SAP ERP to SAP S/4HANA
on-premise edition 1511.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP. Furthermore, the NF Metal Activated indicator is set at
Customizing step IMG -> Logistics - General -> NF Metal Processing -> NF Cross-Application
Components -> Maintain Basic Settings for NF Metal Processing. The simplification item is relevant if
there are entries in table /NFM/TORDERPOS. You can use transaction SE16 to verify.
2.1.38.2 Sales Order Versions
Description
The special Mill Sales Order Versions function is not available in S/4HANA. For more information, see
SAP Note 2226678
Business Process related information
Simplification List for SAP S/4HANA 1610
311
This sales order versions function cannot be used anymore.
Required and Recommended Action(s)
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP. The item is relevant if there are any entries in table
VSVBUK_CN and VSVBUP_CN. You can use transaction SE16 to verify.
Related SAP Notes
Custom Code related information
SAP Note: 2226678
2.1.38.3 Stock Overview and Object Search by Characteristics
Description
This function displays stocks and objects (such as orders) with particular characteristics. The
following Customizing activity is not available in S/4HANA:
Path: Materials Management --> Inventory Management and Physical Inventory --> Reporting -->
Define Profiles for Selection by Characteristics
Transaction: OMILL_MMCL
S_KM5_93000002 MILL_CUST IMG Activity: SIMGMPWMM_OMILL_MMCL
The following transaction is not available in S/4HANA:
SAP Easy Access Menu: Logistics ->Material Management ->Inventory Management ->Environment
Stock
Stock overview by characteristics
Transaction: MMCL - Stock overview and Object Search by characteristics
MMCL MILL_BAS Stock Overview by Characteristics
The transaction MMCL has been replaced with the transaction BMBC (Batch Information Cockpit).
Business Process related information
Simplification List for SAP S/4HANA 1610
312
Business Process supported based on BMBC - Batch Information Cockpit can be used to fulfil the
requirements.
Required and Recommended Action(s)
BMBC - Batch Information Cockpit can be used to fulfil the requirements.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP. The item is relevant if you are using transaction MMCL.
Related SAP Notes
Custom Code related
information
If you have enhanced MMCL Report (Stock Overview and Object Search by
Characteristics), you need to bring the enhancements to the successor
transaction BMBC (Batch Information Cockpit) also
For more information, see SAP Note 2226677
2.1.38.4 Mill specific enhancements to scheduling PRTs
Description
The mill specific function that enhances the handling of production resources and tools (PRTs) in the
context of production orders is not available in SAP S/4HANA. The following customizing activity is
not available in S/4HANA:
Path: Shop Floor Control ->Master Data
Production Resources
Tools
Permit Assignment of PRTs to Work Centre
The following transaction is not available in S/4HANA:
SAP Easy Access Menu:
Logistics ->Production ->Master Data
o Production Resources and Tools
o Production Resources
o Tools
o Compare PRT Pool
Logistics ->Production ->Shop Floor Control ->Order ->Replace PRT in Order
Simplification List for SAP S/4HANA 1610
313
Business Process related information
The PRT handling is reduced only by scope of these mill features. The special Mill Scheduling PRT
functions are not available in SAP S/4HANA.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP. The item is relevant to you if you are using the transaction
/SAPMP/TOOL_REPLACE or /SAPMP/TOOL_POOL_CHK.
Related SAP Notes
Custom Code related information
SAP Note: 2226674
2.1.38.5 Process batch
Description
The Mill specific Process Batch functionality (see SAP Help) is not available in SAP S/4HANA as the
successor core solution WIP Batch (Work in Process Batch) is already available. The process batch is a
batch that you create for the production order so that you can document the properties of a material
during the production process.
Business Process related information
The WIP Batch provides similar functionality of process batch with additional features, but has the
limitation in SAP S/4HANA, on-premise edition 1511, that the Mill specific order combination
function is not available. As of SAP S/4HANA 1610, WIP Batch is enhanced to support order
combination for both production and process orders.
Required and Recommended Action(s)
It is required to use/convert to WIP Batch functionality in SAP S/4HANA. Please refer to SAP Note
2326769 for migration from process batch to WIP batch. Please refer to SAP Note 2346054 for
information on enhancement to support order combination with WIP Batch.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP
Simplification List for SAP S/4HANA 1610
314
The item is relevant to you if you have been using process batch functionality. You are using process
batch functionality if there are valid entries in table MILL_PBWU. You may use transaction SE16 to
check.
2.1.38.6 Fast data entry of characteristics in trading contract
Description
As of SAP S/4HANA 1610, the fast data entry of characteristics functionality from tab page 'Fast Data
Entry' is merged into Item Overview tab page in trading contract transactions WB21, WB22, and
WB23.
Business Process related information
The customer can expect an integrated and unified user interface for display and maintenance of
configuration characteristics of items on the same tab page.
Required and Recommended Actions
If you have been using the functionality prior to SAP S/4HANA 1610 and convert to SAP S/4HANA
1610 or newer releases, you have to note down existing settings before system conversion and apply
those settings after conversion in customizing. Please refer to SAP note 2337868.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function /SAPMP/GEN_CI_1 (Mill,
OrderToCash & Global Trade) is active in your system. You can check its status via transaction
SFW_BROWSER (Switch Framework Browser) under object DIMP. The simplification item is relevant
if you are using fast data entry of characteristics in trading contract transactions WB21, WB22, WB23.
You are likely using the fast data entry of characteristics in trading contract if there are own specific
entries for transaction type Trading Contract in customizing step Define Application Group for
Characteristic Display and Define Characteristics Display for Overview Screen under IMG Logistics
General->Global Trade Management->Trading contract->Fast Entry of Characteristics.
2.1.38.7 Selection by characteristics in mass processing of orders
Description
As of SAP S/4HANA 1610, the feature selection by characteristics in mill specific transaction
/SAPMP/PP_COHV is merged into transactions for Mass processing of Production orders (COHV) and
Mass Processing of Process Orders (COHVPI).
Business Process related information
The users can make selection of manufacturing orders by characteristics along with other selection
criteria of transactions COHV and COHVPI.
Simplification List for SAP S/4HANA 1610
315
Required and Recommended Actions
Customers using transaction /SAPMP/PP_COHV in the past now need to shift to transaction COHV
and/or COHVPI instead. Please refer SAP note 2358159.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP.
The simplification item is relevant if you are using the mill specific transaction /SAPMP/PP_COHV.
2.1.38.8 Fast data entry of characteristics in sales document
Description
As of SAP S/4HANA 1610, the fast data entry of characteristics functionality from tab page 'Fast data
entry' is merged into tab page Configuration in sales document transactions like VA01, VA02, and
VA03.
Business Process related information
The customer can expect an integrated and unified user interface for display and maintenance of
configuration characteristics of items on the same tab page.
Required and Recommended Actions
If you have been using the fast data entry of characteristics functionality prior to SAP S/4HANA 1610
and convert to SAP S/4HANA 1610 or newer releases, you have to make the settings in customizing
for sales document item configuration. For more information, please refer to SAP note 2319234.
How to Determine Relevancy
The simplification item is possibly relevant if the Business Function DIMP_SDUD (Discrete Indus. - Mill
Products) is active in your system. You can check its status via transaction SFW_BROWSER (Switch
Framework Browser) under object DIMP. The simplification item is relevant if you are using Fast data
entry tab page in one or more of the transactions VA01, VA02, VA03, VA11, VA12, VA13, VA21, VA22,
VA23, VA41, VA42, VA43. You are likely using the Fast data entry tab page if there are own specific
entries for transaction type Sales Document in customizing step Define Application Group for
Characteristic Display and Define Characteristics Display for Overview Screen under IMG ->Sales and
Distribution->Sales Document->Fast Data Entry of Characteristics in Sales Documents.
Simplification List for SAP S/4HANA 1610
316
2.1.39 Industry Oil
2.1.39.1 Handling Oil & Gas obsolete t-codes Oil
You are using a SAP ERP system and intend to perform the upgrade-like conversion to SAP S/4 HANA
1610. With the installation of the SAP S/4HANA on premise edition certain Transaction codes in the
application areas of IS-OIL compared to EhP7 for SAP ERP 6.0 - have been deprecated/removed and
partially replaced with newer transactions. Transaction codes which are not supported or replaced by
newer applications in SAP S/4HANA IS-OIL are listed below. SAP ERP contains few SAPGUI
transactions in SAP IS-OIL in Older versions will not be available, but are still supported for
compatibility reasons. With the installation of the SAP S/4HANA on premise edition 1610, certain
transaction codes in the application areas of IS-OIL - compared to EhP7 for SAP ERP 6.0 - will not be
available and partially replaced with newer transactions. All usages of SAP few OIL transaction codes
will not be available, and partially replaced with newer transactions. Below you find a list of OIL
Tcodes and the respective successor Tcode if a successor Tcode is available. It is recommended to
use the successor Tcode instead of the older Tcode. Reference to obsolete transactions in
BAPIs/BDC/LSMW etc. should be adapted to new transaction code.
Obsolete Transaction
code
O300
O3C1
O3C2
O4KC
O4KE
O4KG
O4KH
O4KI
O4NC
O4NS
O4NV
O4T0
O4TC
O4TCB
O4TDL
O4TE
O4TE_CORRECT
O4TE_REVERSE
O4TF
O4TG
O4TH
O4TO
O4TW
O4TX
Older Transaction Code
Successor Tcode
IS-Oil Administration info system SE43
Create Oil Conversion Defaults
O3DEFAULTS
Change Oil Conversion Defaults O3DEFAULTS
Revaluation active check report No Replacement available
2/2
Excise Duty Valuation record 2/3 No Replacement available
Excise Duty Stock values 2/3
No Replacement available
Excise Duty Stock values 3/3
No Replacement available
Excise Duty Valuation record 3/3 No Replacement available
Create Nomination
O4NCN/O4NM
Display Nomination
O4NSN/O4NM
Change Nomination
O4NM
IS-OIL TSW (Trader's & Scheduler's No Replacement available
W
Generate Stock Projection
O4TCN
Generate Stock Projection for
O4TCN
batch
OIL-TSW Delete Location
O402N
OIL-TSW: Enter movement ticket O4TE
OIL-TSW: Correct ticket
O4TENCORR
actualization
OIL-TSW: Reverse ticket
O4TENREV
actualization
OIL-TSW: Change ticket
O4TFN
OIL-TSW: Display Ticket
O4TGN
OIL-TSW: Delete movement ticket O4THN
Work list
O4TO_LIST
OIL-TSW Create Location
O401
OIL-TSW Change Location
O402
Simplification List for SAP S/4HANA 1610
317
O4TY
O547
O548
OIL-TSW Display Location
O403
Reconciliation OIA07
No Replacement available
Reconcile Movb. Netting balance No Replacement available
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.2 Optimization in Oil & Gas - TD module for STO and sales order with POD b
You are doing a system conversion to SAP S/4HANA, on-premise edition 1610. This is an IS-OIL note
for the SAP S/4HANA on premise 1610 release. If you do not have IS-OIL, this note doesnt apply to
you. This note is specific to TD -Sales Orders with PoD Check & Intra Company STOs. The following
SAP S/4HANA Transition Worklist item is applicable in this case. While performing Load Confirmation
(TD process- O4G1) for Sales Order (with PoD) & STO process, the system would throw an error
saying there is no stock in Intransit storage location XXXX for the given material. This is because of
the new SAP S/4HANA MM-IM optimization and performance re-design during execution of MIGO.
When we perform load confirmation for example, in STO the movements which will post are 311
which will put the stock to in transit (Vehicle) and then this will be issued with a 647(GI) movement
followed by 101 movement all in single material document. But now in SAP S/4HANA re-design data
model, we have separate stock checks for 311 movement, 647& 101 respectively, resulting in stock
deficit as it is not considering the fact that the same posting is also bringing in stock. This issue is
handled by splitting into two material documents one material document for 311 movement (stock
into in transit) and another material document for 641/647 (in case of STO) followed by 101
movement for the same outbound delivery at the time of load confirmation
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.3 Data Model in Oil & Gas Inventory management
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. In addition Oil & Gas has
MSEGO1 for quantity conversion parameters for material documents and MSEGO2 Material
Document Quantities in Additional Units of Measure. 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 MARCO1, MARDO1, MCHBO1, MKOLO1, MSLBO1, MSKAO1, MSKUO1 &
MSPRO1. Such tables with material master data attributes as well as actual stock quantities will be
named as hybrid tables in the following. There were also tables like MARCHO1, MARDHO1,
MCHABO1, MKOLHO1, MSLBHO1, MSKAHO1, MSKUHO1 & MSPRHO1 which holds periodical history
data.
Simplification List for SAP S/4HANA 1610
318
With SAP S/4HANA 1610, this data model has changed significantly. The new de-normalized table
MATDOC is 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. Oil appends from MKPF & MSEG are added to MATDOC as an
append. To be in line with core data model MATDOCOIL table has been introduced which contains
former MSEGO1 & MSEGO2 table data and some attributes from core MATDOC table. Additionally
the aggregated actual stock quantities will not be available 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 MATDOCOIL for which some of those additional special fields are used.
The affected tables are listed below:
Table
Table Description Core CDS View
MBV_MBEW_EXT
View to read the content of
View to read the
DDL Source of CDS View the database table (w/o
master data
for redirect
redirect to compatibility
attributes only
view)
OIH_OILEMBEW7_MBEW_
EXT_DDL
CWM_MBEW_EXT_DDL
MBV_MBEW_ML_ONLY
OIH_OILEMBEW7_MBEW_
ML_DDL
CWM_MBEW_ML_DDL
MBV_MBEW_BASIS
OIH_OILEMBEW7_MBEW_
BASIS_DDL
CWM_MBEW_BASIS_DDL
MBEW
Material Valuation
MBV_MBEW_CASE
OIH_OILEMBEW7_MBEW_
CASE_DDL
CWM_MBEW_CASE_DDL
OIH_OILEMBEW7_MBEW_
MOTH_DDL
MBV_MBEW_MOTH_SEG
CWM_MBEW_MOTH_SEG_
DDL
MBV_MBEW
OIH_OILEMBEW7_MBEW_
DDL
CWM_MBEW_DDL
EBEW
MBV_EBEW_EXT
OIH_OILEMBEW7_EBEW_E
XT_DDL
MBV_EBEW_ML_ONLY
OIH_OILEMBEW7_EBEW_
ML_DDL
Sales Order Stock
Valuation
Simplification List for SAP S/4HANA 1610
319
QBEW
OBEW
Project Stock
Valuation
MBV_EBEW_BASIS
OIH_OILEMBEW7_EBEW_B
ASIS_DDL
MBV_EBEW_CASE
OIH_OILEMBEW7_EBEW_C
ASE_DDL
MBV_EBEW
OIH_OILEMBEW7_EBEW_D
DL
MBV_QBEW_EXT
OIH_OILEMBEW7_QBEW_E
XT_DDL
MBV_QBEW_ML_ONLY
OIH_OILEMBEW7_QBEW_
ML_DDL
MBV_QBEW_BASIS
OIH_OILEMBEW7_QBEW_B
ASIS_DDL
MBV_QBEW_CASE
OIH_OILEMBEW7_QBEW_C
ASE_DDL
MBV_QBEW
OIH_OILEMBEW7_QBEW_D
DL
MBV_OBEW_EXT
OIH_OILEMBEW7_OBEW_E
XT_DDL
MBV_OBEW_ML_ONLY
OIH_OILEMBEW7_OBEW_
ML_DDL
Valuated Stock with
MBV_OBEW_BASIS
Subcontractor
OIH_OILEMBEW7_OBEW_B
ASIS_DDL
MBV_OBEW_CASE
OIH_OILEMBEW7_OBEW_C
ASE_DDL
MBV_OBEW
OIH_OILEMBEW7_OBEW_D
DL
CWM_MARC_COSTING
MARC
Plant Data for
Material
NSDM_DDL_MARC
MKPF
Header: Material
Document
NSDM_DDL_MKPF
OI0_COMMON_2_OILMAR
C_DDL
OI0_COMMON_2_OILMKPF
_DDL
CWM_MSEG_DDL
MSEG
Document Segment:
NSDM_DDL_MSEG
Material
OI0_COMMON_2_OILMSE
G_DDL
OIO_OIOMSEG_DDL
MA07V
Material Master: DB
View for Inventory NSDM_E_MA07V
Management
OI0_COMMON_OILVAP_M
A07V_DDL
Simplification List for SAP S/4HANA 1610
320
VAPMA
Sales Index: Order
Items by Material
MARCO1
Appendix for
Additional Quantities
at Plant Level
OIB_DDL_MARCO1
V_OIB_MG_MARCO1
V_MARCO1_MD
MARDO1
Appendix for Storage
Location Additional
Quantities
OIB_DDL_MARDO1
V_OIB_MG_MARDO1
V_MARDO1_MD
MCHBO1
Appendix for
Additional Quantities
at Batch Level
OIB_DDL_MCHBO1
V_OIB_MG_MCHBO1
V_MCHBO1_MD
MKOLO1
Special stocks from
vendor additional
quantity appendix
OIB_DDL_MKOLO1
V_OIB_MG_MKOLO1
V_MKOLO1_MD
MSLBO1
Appendix for Special
Stocks with Vendors:
Add. Quantities
OIB_DDL_MSLBO1
V_OIB_MG_MSLBO1
V_MSLBO1_MD
MSKAO1
Special Stocks
Appendix: Additional
Quantities
OIB_DDL_MSKAO1
V_OIB_MG_MSKAO1
V_MSKAO1_MD
MSKUO1
Appendix for Special
Stocks with
Customers: Add.
Quantities
OIB_DDL_MSKUO1
V_OIB_MG_MSKUO1
V_MSKUO1_MD
MSPRO1
Project Stock
additional quantities
OIB_DDL_MSPRO1
V_OIB_MG_MSPRO1
V_MSPRO1_MD
MARCHO1
MARCH: Additional
quantities appendix
OIB_DDL_MARCHO1
V_OIB_MG_MARCHO1
MARDHO1
MARDH: Aditional
quantities appendix
OIB_DDL_MARDHO1
V_OIB_MG_MARDHO1
MCHBHO1
Appendix for
Additional Quantities
at Batch Level
OIB_DDL_MCHBHO1
V_OIB_MG_MCHBHO1
MKOLHO1
MKOLH: Additional
quantities appendix
OIB_DDL_MKOLHO1
V_OIB_MG_MKOLHO1
MSLBHO1
MSLB: Additional
quantities appendix
OIB_DDL_MSLBHO1
V_OIB_MG_MSLBHO1
MSKAHO1
MSKAH: Additional
quantities appendix
OIB_DDL_MSKAHO1
V_OIB_MG_MSKAHO1
MSKUHO1
MSKUH: Additional
quantities appendix
OIB_DDL_MSKUHO1
V_OIB_MG_MSKUHO1
V_VAPMA
OIF_OILVAPMA_DDL
Simplification List for SAP S/4HANA 1610
321
MSPRHO1
MSPRH: Additional
quantities appendix
OIB_DDL_MSPRHO1
V_OIB_MG_MSPRHO1
MSEGO1
Quantity Conversion
Parameters for
Material Documents
OIB_DDL_MSEGO1
V_OIB_MG_MSEGO1
MSEGO2
Material Document
Quantities in
Additional Units of
Measure
OIB_DDL_MSEGO2
V_OIB_MG_MSEGO2
Business Process related information
MATDOCOIL Table
MATDOCOIL table has the following structure.
Some technical key fields, optimized for memory consumption
Stock identifier fields from MATDOC table
All fields from the existing oil document table MSEGO1
All fields from the existing oil document table MSEGO2 in column format with provision of 60
UoMs
Material Stock condensate table MATDOCOILEXTRACT
MATDOCOILEXTRACT is the condensed table of MATDOCOIL which contains technical key fields to
optimize memory consumption, stock identifier fields, period fields and additional quantity fields.
Records will be inserted in this condensate table MATDOCOILEXTRACT at the same time as records
are inserted in the material document table MATDOCOIL. The Pre-compacting functionality
Running at the period end closing
Can be scheduled as periodic job
Creates a condensate from all records having the same values in its stock identifying fields
Inserts this condensate as new record and deletes all records contributing to this
condensate. Hence the actual stock needs to be calculated only from this condensate and all
document records created since the last Pre-Compacting run. Thus, the overall number of
records in the condensate table is much less than in the material document table as well as
the number of records to be aggregated on-the-fly is less resulting in high performance.
UoM Index Table
As per the new SAP S/4HANA data model, table MATDOCOIL contains MSEGO2 data. This table
stores multiple UoMs in columnar format as UoM1 | UoM2 | UoM60 (provision is made to store up
to 60 UOMs). Earlier in MSEGO2, UoMs were stored in row format. In SAP S/4HANA, columnar
storage is supported due to performance improvements. Therefore if each UoM is provided with
index number and stored in respective columns, aggregation will be faster in HANA DB. Thus
Simplification List for SAP S/4HANA 1610
322
MATDOCOIL_INDEX table would be used to determine the position of the UoMs and their quantities
during the data insert to MATDOCOIL table. MATDOCOIL_INDEX table get updated as follows
Initial Load: This is based on MSEGO2 & MARCO1, the UoMs would be updated to the Oil
index table MATDOCOIL_INDEX during migration.
Delta Load: When the posting is done, the UoM is checked for existence in the
MATDOCOIL_INDEX table. If not present, then that UoM is added by assigning next index
number.
Flexible framework for UoM extension after 60 UoM
According to SAP S4 HANA redesign in HPM, the system supports up to 60 unique UoMs. Once the
UoM count exceeds 60, the user will not be able to post material documents with new UoM. To
overcome this problem a flexible framework is provided to customers. As per the framework when
the UoM count reached to warning limit (total UoM fileds 5 UoM fields i.e. 60-5 = 55), an
information message will be popped up in MIGO process stating UoM count has reached XX number,
to retain smooth operation implement SAP note 2293641.
Data Archiving in S/4HANA for HPM (MATDOCOIL)
With SAP S/4HANA the database design for material documents was changed from the old tables
MKPF and MSEG to the new table MATDOC and in IS-OIL from MSEGO1 and MSEGO2 to MATDOCOIL.
For the tables MKPF, MSEG, MSEGO1 and MSEGO2 an archiving function is in place through the
archiving object MM_MATBEL. The existing implementation of the archiving object MM_MATBEL
shall be changed in a way that it works with the new table while existing settings for this archiving
object are still valid and data which has already been archived in the customer environment is still
accessible. When material documents are moved from the DB into archive files it must be ensured
that the calculation of the current stock level, as well as of historical stock levels is still working
accurately. As the stock level is calculated on the basis of all stock movements for a particular stock
identifier, this means that the archiving of material documents goes together with the creation of
representatives for the archived entities. It must be ensured that the aging and deletion of archived
material documents does not happen in parallel. For this purpose a new lock object
EMATDOC_AGING with client (MANDT) as lock parameter is introduced. When starting data aging for
aging object MM_MATDOC in the aging runtime an exclusive lock shall be raised, while the delete
program for material documents shall raise a shared lock for the same client. A new program
NSDM_MM_MATBEL_POST_PROCESSING (package MBND_ARCHIVING) is provided to consolidate
the archive representatives (i.e. records of type ARC_DELTA) that were created by report
RM07MADES.Consolidation means that the key figures of all representatives having the same
aggregation key are aggregated into a single new representative and inserted into the table MATDOC
and MATDOCOIL, while the representatives forming this new representative are deleted from the
table MATDOC and MATDOCOIL. It must be ensured that the aging and consolidation of archive
representatives does not happen in parallel. For this purpose, the same lock object is used that is
already applied to protect the aging and deletion of material documents (i.e. lock object
EMATDOC_AGING). But as compared to the delete program, where a shared lock is used to enable
the parallel execution of the delete process, the post processing program shall raise an exclusive lock.
By using an exclusive lock it is ensured that the post processing program is called only once at a time
(i.e. it must not run parallel). Old BAdI implementation for Oil and Gas (OI0_MM_MATBEL_WRITE) is
Simplification List for SAP S/4HANA 1610
323
deleted from the BAdI ARC_MM_MATBEL_WRITE as the BAdI call is inappropriate. The material
documents already present in the customers archive will still be accessible as before. There will be no
difference from the user perspective between material documents archived before the changes
described and material documents archived after these changes.
Required and Recommended Action(s)
Any update to MKPF, MSEG, MSEGO1 & MSEGO2 tables in custom code needs to be changed
for MATDOC & MATDOCOIL tables correspondingly.
Custom appends in MKPF & MSEG need to be created in MATDOC table and similarly
MSEGO1 & MSEGO2 appends in MATDOCOIL table.
If UoMs were exceeding more than 60, refer & implement SAP note 2293641.
Select queries on hybrid core & oil tables only for master fetch will be replaced with
corresponding master data views to improve the performance. For this refer SAP note
2328444.
Any inconsistency between MATDOC & MATDOCOIL will be corrected by running report
ROIBSCAN_MISSING_O1O2. Existing inconsistency report of MSEG with MSEGO1 & MSEGO2
is modified to check inconsistence between MATDOC & MATDOCOIL and update the same.
For this refer SAP note 2328561.
ADQNT float field of MSEGO2 table has been obsolete due least usage of field. No more
value available in the field. For this refer SAP note 2328455.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.4 Optimization in Oil&Gas - Inter company sales - Cross border excise duty
This is an IS-OIL specific note for the SAP S/4HANA on premise edition 1610 release. If you do not
have IS-OIL, this note doesnt apply to you. This note does not apply to you if TDP-CrossCompany/Cross-Border Sales and Stock Transfers BC set is not activated in your system. You are
doing a system conversion to SAP S/4HANA on premise edition 1610, the following SAP S/4HANA
note supports inter-company sales- Cross Border Excise duty movement cancellation. In TDP,
Intercompany sales Cross Border Excise duty business process concept of notional plant is
introduced to handle the tax determination, when we perform PGI against the outbound delivery the
following movements will be posted: 601 from supplying plant, 501(Goods receipt without PO)
movement into notional plant & 601 from notional plant. However, when we perform
mateial movement (inter company) cancellation (through VL09), the availability check will occur
at every line item and throws error (deficit of stock) at notional plant.
This will impact 3 different variants
a) delivered; CoT@Load
b) delivered; CoT@Discharge outside TD
c) delivered: Customer Pickup
Simplification List for SAP S/4HANA 1610
324
With the new SAP S/4HANA MM-IM
optimization, single item process as well as array processing is possible.With the single processing th
e items will be processed item by item & throws error (deficit of stock).
The solution for this scenario is by implementing a BADI BADI_NSDM_READ_STOCK, which
checks whether there is a notional plant in OIH79 table and if exists,
assign 'A' (array processing) to variable IS_SINGLE_OR_ARRAY which will take care of inter company S
ales (cross border excise duty) reversal scenarios.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.5 IS-OIL Proper sign operation for ACDOCA
In SAP S/4HANA, on-premise edition 1610, IS-OIL can support a sign operation in ACDOCA. Where
required, automated logic is in place and executed automatically in case a customer converts the
current SAP Business Suite system into SAP S/4HANA, on-premise edition 1610.
Nevertheless there might be constellations where a customer needs to be aware about. For example:
Any FI Posting happened in the system Excise duty values come with sign operation,
Condition credit indicator H with negative values posting can see in ACDOCA
Overview
With SAP S/4HANA, on-premise edition 1610, posting proper sign operation adapted in ACDOCA.
Posting any FI document with Credit Indicator H, negative sign values applied to posting document
and Debit indicator S there is no sign-operation applied. Posting proper sign to ACDOCA we
implemented BADI BADI_OIL_ACDOCA_POST_SIGN and with Implementing Class
CL_OIL_ACDOCA_POST_SIGN. Coding part done in above class using interface method
IF_BADI_FINS_ACDOC_POST_EV_INT~SUBST_ACDOCA_EXTENSION_FIELDS.
System Behavior Depending on the IS-Oil Switch
If the IS-OIL functionality is switched on, then only proper sign operation posting into ACDOCA.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Simplification List for SAP S/4HANA 1610
325
2.1.39.6 Unit of Measure (UoM) Group enahncement
UoM g oup
assig ed to a ate ial; ot possi le to ha ge o delete.
1) Program will consider QCI parameter values from O3DEFAULTS (as the starting point). It is good to
maintain QCI parameter values for all the combinations (Material/Plant/Storage Location/Batch) that
are affected by adding a new UoM to the UoM group.
2) If there are any physical inventory count document for which physical inventory posting is not yet
done, either post the physical inventory document or delete the physical inventory count document
before adding new UoM to UoM group.
A epo t ‘_OIB_ _UOM_ADD_IN“E‘T_“UM has ee de eloped, hi h adds the e UoM i to
UoM group and adjust the stock for all the materials belonging to UoM group for the new UoM by
inserting summary records.
Description
UoM group is one of the major object in HPM module of IS-OIL. UoM attached to material decides
additional UoMs for that material. Hence it plays a major role in stock calculation, document posting
and display if stock. In older IS-Oil releases, it was not possible to add new UoM to existing UoM
group (where there are material documents for the materials which are assigned with the UoM
group in context). This restriction will block few business scenarios for customers. IS-OIL SAP S4HANA
1610 release does not have this restriction and customer can add a new UoM to existing UoM group
(where there are material documents for the materials which are assigned with the UoM group in
context). Changing/deleting of UoMs in UoM group is not possible. Whenever a new UoM is added to
UoM group, system adjusts stock (at Plant/Storage Location/Batch level) with respect to new UoMs
for all the materials which were assigned to that UoM group. Report
‘_OIB_ _UOM_ADD_IN“E‘T_“UM must be executed which will add new UoM to UoM group and
adjusts the stock for all the materials belonging to UoM group by inserting summary records for new
UoM. Summary record will not have material document number. The report needs to be executed in
individual system. In order to be in sync between all the systems of landscape, the report has to run
in Development, Quality and Production system in sequence. Enter the UoM Group that needs to be
e ha ed a d the UoM that has to e added to the UoM G oup. B default Test Mode flag is ON so
that the end user can simulate to see if there are any errors. Simulation output shows which all
combinations (Material/Plant/Storage location/Batch) are affected, if there are any issues and for
which all combinations summary record can be created. If there are issues, it is suggested to fix the
issues and run the report again. Once all the issues are fixed, user can run the report by removing the
flag fo Test Mode . ‘ole “AP_I“OIL_UOM_G‘ Autho izatio o je t OIB_UOM ith a ti it
fo
Simulation and 10 for Post (or Update) needs to be assigned to the user for executing this report.
Use cases handled:
1. If a ate ial is a ked fo deletio , p og a still eates su
a e o d ut Mate ial flag
fo deletio olu
is a ked
as just FYI
2. Negative stocks are also handled with QCI conversion to new UoM
3. If material in context has few material postings (GR & GI) and nett stock in base UoM is 0, as
the base UoM stock is zero, no summary record is created
Simplification List for SAP S/4HANA 1610
326
4. Stock in Base UoM is negligible quantity (Ex: 0,001 KG) and newly added UoM is biggest UoM
(Ex: MBL), as conversion of 0,001 KG to MBL will lead to ~0 value, summary record with 0
quantity will be added and stock in MBL will be shown as 0 in MMBE for newly added UoM
(i.e. MBL)
5. If there are more than 1 O3DEFAULTS maintained for same material/plant/storage location,
most relevant record (active and valid on current date) will be considered for QCI conversion
to new UoM
6. There are some cases where material documents are created with a UoM (For Ex: BBL) which
is ot pa t of UoM g oup. I su h ases, p og a e su es that the e UoM s ua tit i
summary record is calculated such that new quantity of base UoM when converted to new
UoM will match properly
Base UoM had net quantity as 360 KG and assuming correct QCI conversion into BBL is 2
1. Case1: If BBL was part of only few material documents, assuming net quantity in BBL from
existing material documents is 1 BBL, Summary record will be created for BBL as 1 so that in
MMBE after summary record is created, stock for BBL will be shown as 2
2. Case2: If BBL was part of only few material documents, assuming net quantity in BBL from
existing material documents is 0 BBL, Summary record will be created for BBL as 0 so that in
MMBE after summary record is created, stock for BBL will be shown as 2
3. Case3: If BBL was part of only few material documents, assuming net quantity in BBL from
existing material documents is -1 BBL, Summary record will be created for BBL as 3 so that in
MMBE after summary record is created, stock for BBL will be shown as 2
Business Process related information.
New functionality available in SAP S4HANA 1610
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.7 eNetting Deprecation
Description:
eNetting application is used for exchange reconciliation and was available till 4.6C version of ERP. The
exchange detail statement generated from R/3 is transmitted to eNetting application for exchange
reconciliation. The data transfer between an R/3 system and a non-R/3 system is typically achieved
using the IDOC interface. In the eNetting scenario, the exchange detail statement IDOC is generated
from the R/3 system and is transmitted to the SAP Business Connector (middleware tool) through
ALE integration technology. The SAP Business Connector is then responsible for the transformation
of the data from IDOC to XML that is used for further processing by the eNetting application. SAP has
stopped supporting middleware tool SAP Business Connector with the latest solutions like Process
integration availability.
Simplification List for SAP S/4HANA 1610
327
Business Process related information
eNetting functionality was available till 4.6C version of ERP which is not available in SAP S/4HANA
1610.
Required and Recommended Action:
There is no equivalent functionality of eNetting available in SAP S/4HANA 1610.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.8 Dynamic Scheduling deprecation
Dynamic scheduling application is an integration of Stock Projection Worksheet (SPW) and Three-way
pegging (3WP) functionality.The application integrates these two applications so that when a user
makes a data-change in one application, he can see the effect of it in the other application in realtime (without requiring a data-save). This allows the user the create simulations in 3-way pegging,
see its effects on the inventory in the Stock Projection, modify the simulations, undo-redo changes,
make changes to already published nomination. Once satisfied, the user can save these changes to
the database.As this application is not used much and thus is removed in SAP S/4HANA 1610.
Description:
Dynamic scheduling application is an integration of Stock Projection Worksheet (SPW) and Three-way
pegging (3WP) functionality. Dynamic Scheduling integrates these two applications so that when a
user makes a data-change in one application, they can see the effect of it in the other application in
real-time (without requiring a data-save). This allows the user to create simulations in 3-way pegging,
see its effect on the inventory in the Stock Projection, modify the simulations, undo/redo changes,
and make changes to already published nomination. Once satisfied, the user can save these changes
to the database. As SAP has come up with similar applications recently, it creates confusion to
customers with similar solutions and hence Dynamic Scheduling has been removed in SAP S/4HANA
1610.
Business Process related information: Dynamic scheduling is an integration of SPW and 3WP
functionality which has been removed from SAP S/4HANA 1610.
Required and Recommended Action: There is no equivalent functionality of dynamic scheduling
available in SAP S/4HANA 1610, but advanced functionalities like Inventory Planning Workbench
(IPW) and Nomination Planning Workbench (NPW) are available.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Simplification List for SAP S/4HANA 1610
328
2.1.39.9 Financial Based netting deprecation
Movement based netting has more advantages over Financial Based Netting functionality
Description
Financial Based Netting is not available within SAP S/4HANA 1610. But you can still display and
process existing Financial Based Netting documents.
Business Process related information
The Transaction codes O54X(Create Selection) , O3A4(Create netting document) used to create
Financial Based Netting are removed from SAP S/4HANA 1610. As an alternative, you should use
Movement Based Netting functionality in Exchanges module. Transactions not available in SAP
S/4HANA on-premise edition 1610 : O54X and O3A4
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.39.10 Oil & Gas inconsistency reports deprecation
Description
In SAP S4HANA 1610 there is a change in MM-IM data model. Data is moved from existing MM-IM
tables to new tables MATDOC and MATDOCOIL. Due to this change the old inconsistency check
reports for aggregate and history tables are now deprecated.
The following table provides the change details regarding the new data model:
Data Storage as per Old
Data Model
Data Storage as per New
Data Model
Details
MKPF
MATDOC
No data is stored in MKPF
MSEG
MATDOC
No data is stored in MSEG
MSEGO1
MATDOCOIL
No data is stored in MSEGO1
MSEGO2
MATDOCOIL
No data is stored in MSEGO2
Core Aggregate tables
(MARC...)
Aggregate Table +
MATDOC
Master data is stored in Aggregate table,
the transactional data is calculated on the
fly from MATDOC using redirect CDS view
Oil Aggregate tables
(MARCO1...)
Aggregate Table +
MATDOCOIL
Master data is stored in Aggregate table,
the transactional data is calculated on the
fly from MATDOCOIL using redirect CDS
view
Core History Tables
(MARCH...)
Aggregate Table +
MATDOCOIL
Master data is stored in Aggregate table,
the transactional data is calculated on the
fly from MATDOC using redirect CDS view
Simplification List for SAP S/4HANA 1610
329
Oil History Tables
(MARCHO1)
Aggregate Table +
MATDOCOIL
Master data is stored in Aggregate table,
the transactional data is calculated on the
fly from MATDOCOIL using redirect CDS
view
Business Process related information
As per the old data model the data was maintained in the Aggregate/History tables for both Core and
Oil & Gas, there was a necessity to check and correct any inconsistency between the Core and Oil
tables. The reports for this purpose are as listed below:
ROIBCHAR (MARDO1 Inconsistency check)
ROIBSCAN_MCHBO1 (MARDO1 Inconsistency check)
ROIBSCAN_SEL_MSEGO2 (Oil Aggregate table Inconsistency check)
ROIBSCAN_SEL_MSEGO2_H (Oil History table Inconsistency check)
Since the new data model eliminates data storage in the Aggregate/History tables there is no
longer the requirement to correct inconsistencies between the Core and Oil counterpart
tables. The 4 reports mentioned above are deprecated with SAP S4HANA 1610.
Required and Recommended Actions
The reports for inconsistency check in the Oil Aggregate/History tables are no longer
available.
To check for inconsistency between MATDOC and MATDOCOIL the following report can be
executed:
o
ROIBSCAN_MISSING_O1O2
Data Storage as per Old
Data Model
Data Storage as per New
Data Model
Details
MKPF
MATDOC
No data is stored in MKPF
MSEG
MATDOC
No data is stored in MSEG
MSEGO1
MATDOCOIL
No data is stored in MSEGO1
MSEGO2
MATDOCOIL
No data is stored in MSEGO2
Core Aggregate tables
(MARC...)
Aggregate Table + MATDOC
Master data is stored in Aggregate table, the
transactional data is calculated on the fly from
MATDOC
Oil Aggregate tables
(MARCO1...)
Aggregate Table +
MATDOCOIL
Master data is stored in Aggregate table, the
transactional data is calculated on the fly from
MATDOCOIL
Core History Tables
(MARCH...)
Aggregate Table +
MATDOCOIL
Master data is stored in Aggregate table, the
transactional data is calculated on the fly from
MATDOC
Simplification List for SAP S/4HANA 1610
330
Oil History Tables
(MARCHO1)
Aggregate Table +
MATDOCOIL
Master data is stored in Aggregate table, the
transactional data is calculated on the fly from
MATDOCOIL
How to Determine Relevancy
This item is relevant for all IS-Oil customer
2.1.40 Industry Public Sector
2.1.40.1 Authorization in Funds Management
Description
In the Business Suite, authorizations for Funds Management master data elements could be
maintained in two ways:
old authorization concept (up until 4.6c) based on the key of the respective master data
object
new authorization concept (beginning with SAP R/3 Enterprise EA-PS 200) using
'authorization groups'
In SAP S/4HANA, the decision was taken to only support the use of authorization groups.
Business Process related information
Customers need to switch to the new authoization concept provided with SAP R/3 Enterprise, which
is the only concept supported in S/4HANA.
Influence on Business Processes
Revise your authorization concept for Funds Management by determining authorization groups,
rather than assigning individual master data keys to the respective authorization object.
How to determine relevancy
Go to transaction SE16N. Enter the name of the table FMISPS. Click on execute or F8. In the table
entry check the value of the field AUTH_CHECK_OLD. If the value is blank, nothing has to be done. If
the value is X that means you are still using the old authorization concept thats not supported
anymore.
Required and Recommended Action(s)
In the ECC source system which you are planning to convert to SAP S/4HANA,
Simplification List for SAP S/4HANA 1610
331
1. Assign authorization groups to your master data objects by using the following transactions:
Maintain Commitment Item (transaction FMCIA)
Create/change Funds Center (transaction FMSA/FMSB)
Create/change Fund (transaction FM5I/FM5U
Edit Budget Period (transaction FMBPD)
Process Functional Area (transaction FM_FUNCTION)
Edit Funded Program (transaction FMMEASURE)
2. Assign the authorization groups used in the above master data transactions to the authorization
objects and remove the individual master data keys from the authorization objects. Make sure the
new or revised authorization objects are included in the respective user roles (transaction PFCG).
3. De-activate the 'old authorization' concept in the IMG menu of Funds Management using Public
Sector Management --> Funds Management Government --> Basic Settings --> Authorization check -> Activate Old Authorization Check
Make sure the flags are unchecked in this entry
4. De-activate the BAdI for 'Partially Activate Old Activities' in the IMG menu of Funds Management
using Public Sector Management --> Funds Management Government --> Basic Settings -->
Authorization check --> BAdI: Partially Activate Old Activities
Make sure no active BAdIs remain here.
2.1.40.2 Functionality German Local Authorities
Description
In Funds Management, all transactions, configuration and master data attributes related specifically
to German Local Authorities have been disabled/hidden by a switch.
How to determine relevancy
Go to transaction SE16N and type FMISPS" to the table field. Click on the execute button (or F8).
Check field KOM_ACTIVE. If the field value is empty, no action is required. If the field value is "X",
please proceed as follows.
Business Process related information
Customers requiring functionality from the scope of the objects removed need to check on an
individual basis if and how their needs can be satisfied with the remaining Funds Management
functionality. Affected business processes cannot be executed any longer.
Related SAP Notes
Simplification List for SAP S/4HANA 1610
332
Custom Code related information
SAP Note: 2226072
2.1.40.3 Former Budgeting System (FBS) in Funds Management
Description
In the Business Suite, the process budget maintenance was reflected by two tools, the older Former
Budgeting System or FBS (co-development with the Project System budget capabilities) and the more
recent Budget Control System (BCS). While a migration from FBS to BCS is available since release ECC
5.0 already, a large number of customers was quite satisfied with FBS and never saw a business need
to execute the migration. SAP did never announce the end of life for FBS in the Business Suite. For
SAP S/4HANA, the decision was taken to only support BCS as a tool, also because the architecture of
BCS is much more suitable to the simplification approach.
Business Process related information
Customers need to reconsider their needs in budget maintenance and how these are best reflected
in BCS. Different objects and configuration (compared to FBS) is available to support budget
maintenance. The BCS tool is already available since ECC 5.0, thus impact analysis, PoCs, migration
tests and migration can take place before the system conversion to SAP S/4HANA. Once on SAP
S/4HANA, the FBS data is still available but operational transactions are blocked. As the typical
timeframe of an approved budget is one year, the time remaining after system conversion to SAP
S/4HANA might not be sufficient to consider and execute a smooth Conversion. It is therefore
recommended from a business perspective to perform the FBS -> BCS migration before the system
conversion to SAP S/4HANA.
How to determine relevancy
1. Using transaction SE16N, read table FM01 to get the list of all FM areas in the client.
2. Using transaction SE16N, read BCS configuration table FMBCSA for each FM area defined in
table FM01.
o
o
o
Case 1: BCS is active. If the maintained year (fiscal year) is earlier than or equal to
the current fiscal year of the FM area, BCS is already in use. No action is required.
Case 2: FBS to BCS migration is planned for future years. Maintained fiscal year is
later than current fiscal year. Check if migration from FBS was already completed by
selecting from the BCS budget header table FMBH using transaction code SE16N.
If an FMBH entry was found, then migration to BCS was already
completed. No action is required.
If no FMBH entry was found, migration to BCS was not completed and FBS
might still be in use. Proceed as described above in Business Process related
information to migrate FBS to BCS
Case 3: FBS is still active. If no entry is found for an FM area:
look for entries in the totals tables BPJA and BPGE (for OBJNR like FSXXXX*
where XXXX is the FM area)
Simplification List for SAP S/4HANA 1610
333
If an entry is found in one of the totals table (BPJA or BPGE), then migration
to BCS was not performed and FBS might still be in use. Proceed as
described above in Business Process related information to migrate FBS to
BCS.
If NO entry is found in any of the 2 tables (BPJA or BPGE), FBS has not been
used. No action is required.
Influence on Business Processes
The business process change is not predictable and strongly depends on the chosen implementation
of BCS.
Required and Recommended Action(s)
None
Related SAP Notes
Conversion Pre-Checks
Custom Code related
information
The FBS tool is only technically disabled, not removed. Customer code referencing
FBS objects thus remains technically functional. Customers need to analyse what
their code is doing and need to consider if and how to reflect this in BCS. A
complete rewrite will be required as the two tools do not share objects.
For more details see SAP Note: 2226048
2.1.40.4 Functionality for FACTS I and FACTS II (Federal Agencies Centralized Trial Balance System)
Description
As mandated by US Treasury, the US Federal specific Trial Balance System has been changed from
FACTS I (Federal Agencies Centralized Trial Balance System I) and FACTS II (Federal Agencies
Centralized Trial Balance System II) to GTAS (Government-wide Treasury Account Symbol Adjusted
Trial Balance System) starting with fiscal year 2014. SAP's US Federal Ledger 95 (FMUSGA and
FMUSFGT) is now the single reporting ledger for financial reports such as GTAS bulk files and Trial
Balances. It replaces the US Federal Ledgers 96 and 97 (FMUSFGFACTS1A, FMUSFGFACTS1T as well
as FMUSFGFACTS2A and FMUSFGFACTS2T).
Business Process related information
All known customer implementations have already switched to GTAS, aligning with the legal
regulations for FACTS/GTAS. This entry just appears for the record. The business process remains as
is.
Transaction not available in SAP S/4HANA
RFACTS1_BL
RFACTS1_FILE_SEND
Simplification List for SAP S/4HANA 1610
334
RFACTS2_BL
RFACTS2_UPLMAF
RFACTS2_MAF
RFACTS2_EXTRACT
RFACTS2_FOOTNOTE
RFACTS2_EDITS
RFACTS2_FILE_SEND
How to determine relevancy
Go to transaction SE16N and type FMUSFGFACTS1A into the table field. Enter the current fiscal year
(RYEAR) and prior year for selection. Click on the execute button (or F8). If no entries were found in
the selection, type in table name FMUSFGFACTS2A instead, enter the current fiscal year (RYEAR) and
prior year, and execute. If entries are found in either of the selections, look at note 2225817. If no
entries are found in either of the selections, nothing else has to be done.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related
information
All related objects do still exist, thus no technical problems (like syntax errors)
will occur all existing data resulting from the use of ADB in the Business Suite will
remain untouched/unchanged
Custom code for reporting purposes does not need to be changed to continue to
display existing FACTS results and rules. Code that is used to maintain the FACTS
settings or to execute FACTS functionality can no longer be executed.
This is documented in SAP note 2225817.
2.1.40.5 Expenditure Certification
Description
Expenditure Certification is a functionality which was based on a legal framework of subsidy funding
from the European Community. This type of funding was last approved by the European Union in
2012, after which the legal framework was changed such that the detailed kind of process is no
longer legally required. Due to this, and as Expenditure Certification also was only used by a few
customers in ERP, it is no longer considered the target architecture in SAP S/4HANA. Activation of BF
in SAP S/4HANA is not supported for new customers, customers with BF activated in Business Suite
and migrating to S/4HANA should contact SAP Product Management to discuss strategy going
forward. Currently there is no functional equivalent as alternative available.
Business Process related information
Simplification List for SAP S/4HANA 1610
335
Customers, who used Expenditure Certification in ERP and are planning to move to S/4HANA, have to
remodel their business processes accordingly if they still see a need or use for such functionality.
Transaction not available in SAP S/4HANA onpremise edition 1511
FMECDERIVE
FMECDERIVER
FMEUFDD
FMEUFFINTYP
FMEUFINTERV
FMEUFLEVELS
FMEUFLP1
FMEUFLP2
FMEUFPROC
FMEUFRCODE
FMEUFTAXHAN
How to determine relevancy
Go to transaction SFW2 and check if the Business Function PSM_EXP_CERT is active or not. If the
activation status of the Business Function is not ON then they have to do nothing.
If the Activation status of the Business Function is ON: Go to transaction SE16N, check if there are
any entries in the table FMEUFRUN. If there are any entries in the table FMEUFRUN, then please
refer to the note 2270418. If no entries are found, no action is needed.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related
information
SAP note 226049
2.1.40.6 Specific fields on Business Partner
Description
With the introduction of Business Partner and Customer/Vendor Integration (CVI) as mandatory
aspects of SAP S/4HANA, customer and vendor master record creation, maintenance and display is
only possible via the Business Partner functionality. In both customer and vendor client and company
code-specific tables, specific fields relevant for US Federal Financials had been added, which are now
also available via the business partner transaction 'BP'. Refer to the simplification item for business
partner for general information (Business Partner Approach).
Business Process related information
Simplification List for SAP S/4HANA 1610
336
Business Partner transaction 'BP' is now used to create, change or display customer or vendor data.
This also applies to the specific fields required in US Financials. Use the role for 'Business Partner
Vendor (FI part)' (FLVN01) and 'Business Partner Customer (FI part)' (FLCU01)' and the tabs
'Customer - USFG Fields' and 'Vendor - USFG Fields' to display and maintain the specific fields.
The business process is not affected, only a different transaction needs to be used
Transaction not available in SAP S/4HANA
FK01
FK02
FK03
XK01
XK02
XK03
FD01
FD02
FD03
XD01
XD02
XD03
How to determine relevancy
please refer to OSS note 2265093 for a general overview of the Business Partner conversion concept
and how to to determine relevancy.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related
information
Customer code to create or change customer or vendor master data needs
to be changed such that the business partner is created or maintained
instead. The alignment with customer/vendor master data tables is the
executed automatically as part of the CVI feature.
For more details see SAP Note: 2226131
2.1.40.7 Fund Accounting based on Special Ledger
Description
In SAP S/4HANA, the Universal Journal is the functionality to reflect the General Ledger (GL). All
master data entities required to support fund accounting (like Functional Area and Fund) are
Simplification List for SAP S/4HANA 1610
337
available in the Universal Journal database table ACDOCA. Document splitting as the core feature to
achieve self-balancing accounting documents by Fund also is available in the standard General Ledger
in SAP S/4HANA. A migration from New General Ledger as well as from the classic General Ledger
into a basic implementation of the General Ledger using the Universal Journal is mostly done
automatically - see simplification item General Ledger for details. Any functionality based on Special
Ledger (and therefore Fund Accounting based on Special Ledger as well), whether built as a custom
implementation or based on SAP recommendations, is still supported in SAP S/4HANA. However,
new developments / simplifications will be based on the Universal Journal Entry only. Customers
currently using Fund Accounting based on Special Ledger might consider a migration to New General
Ledger with document splitting prior to the system conversion to SAP S/4HANA (due to the fact that
a direct migration from Special Ledger with document splitting to the GL with Universal Journal and
document splitting in SAP S/4HANA is not yet available).
Business Process related information
The available successor functionality offers the same processes and features.
How to determine relevancy
Go to transaction SE16N and type T881 into the table field. Enter "FI" into the selection field
Application and "SL" into the selection field Subapplication. Click on the execute button (or F8). Look
for any ledger with a Totals Table in the "ZZ*" name range. Remember this table name. Click on the
back button (F3). Enter the name of the totals table that was found in the previous step as Table, and
execute. If no entries are found in the table, nothing else has to be done.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related
information
There is no direct influence expected, custom code remains functional.
With a Conversion from Fund Accounting based on Special Ledger to any
new approach, all custom coding will need to be adjusted
2.1.40.8 Data Structure changes in BCS
Description
All 3 aggregate/totals tables in the Budget Control System (BCS) are no longer updated. The totals
table update has been replaced as follows:
Budget totals, stored in table FMBDT: For any budget change, BCS has always created
corresponding line items, stored in table FMBDP. With SAP S/4HANA, totals are no longer
updated in table FMBDT, instead they are calculated via FMBDP. As the line items already
Simplification List for SAP S/4HANA 1610
338
exist, no migration is needed for migrating customers. A compatibility view is attached as
proxy object to the totals table (CDS view V_FMBDT).
Revenue Increasing Budget (RIB) totals, stored in table FMRBT: For this table, normally no
customer has ever written any line items. However, since RIB rules are strictly yeardependent, a simple reconstruction is needed for upgrade customers: Run TA FMRBREINIT
for the current fiscal year to populate the line item table FMRBP, making the RIB functions
work again. The table FMRBT is no longer update. A compatibility view is attached as proxy
object to the totals table (CDS view V_FMRBT).
Active Availability Control (AVC) totals, stored table FMAVCT: For this table normally no
customer has written change or line items. The update of the change records for AVC in table
FMAVCT_RECON_YR is initiated by executing the re-initialization of AVC data via transaction
FMAVCREINIT. Until execution, the totals table will still be updated for migrating customers.
For new customers (in the sense of no technical migration from a non-SAP S/4HANA system),
change records will be created from the beginning and the totals table is not updated. There
is a compatibility view for AVC, the CDS view V_FMAVCT_COMPAT. However, this view is not
yet attached as proxy object to table FMAVCT.
Business Process related information
The change is of technical nature. All business processes and transactions remain functional and
appear unchanged to users
How to determine relevancy
Go to transaction SE16N and check if there are any entries in the totals table FMRBT for Revenue
Increasing Budget. If there are any entries in the table, run transaction FMRBREINIT for the current
fiscal year to populate the line item table, as described above.
Related SAP Notes
Custom Code related
information
No technical object has been deleted or changed, thus no syntax error will
occur, However, data content is changed and needs to be considered
For more details see SAP note 2226129
2.1.40.9 Funds Management Dimensions as part of the Universal Journal
Description
All fields which used to be supported in the standard newGL tables for Public Sector, FMGLFEXx and
PSGLFLEXx, (such as Functional Area and Fund) are now part of the Universal Journal Entry table
ACDOCA. The new journal entry feature offers all dimensions needed to generate financial as well as
management information compliant with Public Sector accounting regulations. Document splitting
functionality remains as before. Migration from New General Ledger to Universal Journal Entry also
manages Public Sector Management (PSM) fields and specific source tables. Compatibility views for
the no longer updated newGL tables are generated as part of the migration process
Simplification List for SAP S/4HANA 1610
339
Business Process related information
Customers will technically use the Universal Journal as the GL transaction data table.
Transaction not available in SAP S/4HANA
See the respective FI-GL simplification items.
How to determine relevancy
Go to transaction SE16N and type T881 into the table field. Click on the execute button (or F8). Look
for the row where the column named Leading Ledger has an X and Subapplication is PSM or PSX.
Check that row for the name of the leading ledger, which is indicated by the column called Totals
Table. Remember this table name. Click on the back button (F3). Enter the name of the totals table
that was found in the previous step, and execute. If there are entries in the table, above information
given under "Description" and below required and recommended actions apply. If no entries are
found in the leading ledger table, nothing else has to be done
Required and Recommended Action(s)
Due to the existence of compatibility views, custom code for reporting purposes does not need to be
changed to continue to display GL data. You should however consider to exchange access to GL data
by natively accessing the universal journal table ACDOCA to benefit from the flexibility that this new
concept offers. Also, consider that the concept of compatibility views puts the focus on compatibility
of the new structures with old structures, not on improving the performance of old access. Code that
is used to maintain GL settings should no longer be executed. You need to adapt such coding to the
new GL functionality using the new GL configuration. Code that is used to post journal voucher
entries via GL entry documents is not affected and will continue to work. Data migration activities are
required and covered in the documentation for the universal journal.
Related SAP Notes
Custom Code related
information
All related objects do still exist,
no technical problems (like syntax errors) will occur all existing data resulting from
the use of classic GL or newGL in the Business Suite will remain
untouched/unchanged compatibility views do exist which technically read data
from the universal journal table ACDOCA but present them to consumer
programs under their old name and structure
For more details see SAP Note: 2226134
Simplification List for SAP S/4HANA 1610
340
2.1.40.10 Functionality for BCS Multi-level Budget Structure
Description
Multi-level Budget Structure (MBS) in the Budget Control System allows a customer to perform
hierarchical budget processes like:
top-down distribution
bottom-up roll-up
The functionality does support timeframe-dependent definition of hierarchies of Funds Management
master data. The functionality was only used by less than 5 productive customers in the Business
Suite, and deemed as complex to configure and complex to handle. It was this decided to discontinue
the functionality without commitment that any kind of successor would be offered with a future
release. It is therefore no longer considered the target architecture in SAP S/4HANA. Activation of BF
in SAP S/4HANA is not supported for new customers, customers with BF activated in Business Suite
and migrating to SAP S/4HANA should contact SAP Product Management to discuss strategy going
forward.
Business Process related information
A customer needs to decide if hierarchy-based budget processes are relevant to him and how to
reflect them with the remaining functionality. No standard suggestion can be given. The existing
Business Processes cannot be executed in a hierarchical environment any longer.
Transaction not available in SAP S/4HANA onpremise edition 1511
FMHIE_CHANGE
FMHIE_CHKINCONDATA FMHIE_CHKINCONDISTR
FMHIE_COPY FMHIE_DELETE
FMHIE_DISPLAY
FMHIE_EXPORT FMHIE_GENERATION
FMHIE_HIEID FMHIE_IMPORT
How to determine relevancy
Go to transaction SFW2 and check if any of the two MBS business functions PSM_FM_BCS_MBS and
PSM_FM_BCS_MBS_2 are turned ON or not. If both of the Business Function are not turned ON then
nothing has to be done. If either one or both of the Business Functions are turned ON, then please
proceed as mentioned above.
Required and Recommended Action(s)
None.
Related SAP Notes
Custom Code related information
SAP Note: 2226122
Simplification List for SAP S/4HANA 1610
341
2.1.40.11 Functionality Average Daily Balance-based Distribution
Description
The Average Daily Balance-based Distribution functionality is not available with SAP S/4HANA. The
architecture of the functionality would require considerable rework to follow the simplification
paradigms of SAP S/4HANA. This is not justified as it has only been used by very few customers. The
functionality is not part of a legal requirement. Technically, the functionality has only been disabled,
all objects and all existing data remains in place
Business Process related information
The feature did require to keep a complete copy of the leading general ledger on a daily fiscal year
variant basis to support the calculation of average daily balances. This data is no longer
needed/supported thus reducing the data footprint. The distribution result are FI journal voucher
documents which remain unchanged. Also, as the functionality is only disabled, the full configuration
and calculation trail that had existed is still available for review purposes. If the business process is
still used, a customer needs to establish distribution-relevant information from the leading ledger via
an analytical approach (possible, but no content made directly available), calculate the distribution
and enter a journal voucher to distribute the amounts in question from source to target.
Transaction not available in SAP S/4HANA
FMADB_CREATE_FYV
FMADB_CUSTOM
FMADB_POST
FMADB_TRACE
How to determine relevancy
Execute transaction SM34, enter view cluster VC_FMADB. Click on Display.
Select each ADB rule (table FMADB_HEADER), and look for records in the following folders:
o Pool account assignments (tables FMADB_POOL)
o Bank Accounts (FMADB_GLACCOUNT)
o Incoming Interest Posting (table FMADB_INT_DOC) without blanks in document type
and account fields
o Transfer Parameters (table FMADB_DOC) without blanks in document type, posting
keys and target account fields
If all these customizing records are found for at least one ADB rule (header), please proceed
as described above.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2226071
Simplification List for SAP S/4HANA 1610
342
2.1.41 Industry Retail & Fashion
2.1.41.1 Logistical Variant
Description
For articles with several units of measures it was possible via logistical variants to a) manage the
stocks of an article separately for different units of measure and b) plan requirements according to
the unit of measure
Business Process related information
In SAP S/4HANA logistical variants are not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to logistical variants available in SAP S/4HANA. It is under
evaluation whether there will be functionality in a future release to address the business
requirement.
How to Determine Relevancy
This Simplification Item is relevant if logistical variants are used. This can be checked via transaction
SE16N. Enter table MARA and check whether there are entries with field BFLME (Logistical Variant)
not equal blank.
2.1.41.2 SAP Forecasting & Replenishment Integration
Description
In SAP S/4HANA Retail for merchandise management, functionality to support SAP Forecasting &
Replenishment integration is available, but defined as "not strategic any more". See SAP
note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
SAP evaluates whether to develop a replenishment solution as a consuming application on SAP
Customer Activity Repository. Unified Demand Forecasting (UDF) is already available part of SAP
Customer Activity Repository.
Required and Recommended Action
Simplification List for SAP S/4HANA 1610
343
No special actions for SAP Forecasting & Replenishment integration is needed when converting from
SAP ERP to SAP S/4HANA.
Move to strategic replenishment solution once available.
How to Determine Relevancy
This Simplification Item is relevant if Forecasting & Replenishment integration is used.
This is the case if transactions FRE*, WRF_DISP*, WRF_REF* are used.
2.1.41.3 Retail Power Lists
Description
In SAP S/4HANA Retail for merchandise management, retail power lists are available, but defined as
"not strategic any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, onpremise edition .
Business Process related information
Move to strategic technology once available, e.g. relevant CDS content.
Required and Recommended Action
No special action for retail power lists is needed when converting from SAP ERP to SAP S/4HANA.
2.1.41.4 Retail Closed BW Scenarios
Description
In SAP S/4HANA Retail for merchandise management, retail closed loop BW scenarios are available,
but defined as "not strategic any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP
S/4HANA, on-premise edition .
Business Process related information
Move to strategic technology once relevant content for CDS, or BW/4HANA is available.
Required and Recommended Action
No special action for retail closed loop BW scenarios is needed when converting from SAP ERP to SAP
S/4HANA.
How to Determine Relevancy
Simplification List for SAP S/4HANA 1610
344
This Simplification Item is relevant if retail closed loop BW scenarios are used.
This is for example the case if transactions WA56 is used.
This also can be checked via transaction SE16N. Enter table TMCW_AA_QRY and check whether there
are any entries, this is a good indicator for usage.
2.1.41.5 Retail Markdown Plan
Description
In SAP S/4HANA Retail for merchandise management, functionality of retail markdown plan is
available, but defined as "not strategic any more". See SAP note 2269324 - Compatibility Scope
Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
Move to available functionality of markdown profile integrating in the price planning workbench.
Furthermore, SAP evaluates whether to develop a price and markdown optimization solution as a
consuming application on SAP Customer Activity Repository.
Required and Recommended Action
No special actions for retail markdown plan is needed when converting from SAP ERP to SAP
S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if markdown planning is used.
This is the case if transactions WMF*, WMR* are used.
This also can be checked via transaction SE16N. Enter table WMFH, or WMFP and check whether
there are any entries.
2.1.41.6 Retail Bonus Buy
Description
In SAP S/4HANA Retail for merchandise management, bonus buy functionality via transactions VBK1
VBK2 VBK3 VBK6 is available, but defined as "not strategic any more". See SAP note 2269324 Compatibility Scope Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
Move to available bonus buy functionality via transactions RDMBB*.
Required and Recommended Action
No special actions for bonus buy is needed when converting from SAP ERP to SAP S/4HANA.
Simplification List for SAP S/4HANA 1610
345
How to Determine Relevancy
This Simplification Item is relevant if market basket calculation is used.
This is the case if transactions VBK1 VBK2 VBK3 VBK6 are used.
This also can be checked via transaction SE16N. Enter table KONBBYH and check whether there are
any entries.
2.1.41.7 Retail Sales Forecasting
Description
In SAP S/4HANA Retail for merchandise management, retail sales forecasting is available, but defined
as "not strategic any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP S/4HANA,
on-premise edition .
Business Process related information
The following areas are affected:
Sales forcasting for stores
Import of external forecast data
Forecast with AHD (Alternative Historical Data)
UDF (Unified Demand Forecast) is strategic for forecasting in retail, which is part of SAP Customer
Activity Repository.
Required and Recommended Action
No special actions for retail sales forecasting is needed when converting from SAP ERP to SAP
S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if retail sale forecasting is used.
This is the case if transactions MAHD*, MDRD*, WFCS*, MPR2 are used.
This also can be checked via transaction SE16N. Enter table MAHD, WFCS_WRFT and check whether
there are any entries.
2.1.41.8 Retail Order Optimizing: Load Build, Investment Buy
Description
In SAP S/4HANA Retail for merchandise management, functionality to support order optimizing via
load build, and investment buy is available, but defined as "not strategic any more". See SAP
note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
Simplification List for SAP S/4HANA 1610
346
SAP evaluates whether to develop order optimizing functionality part of a future replenishment
solution.
Required and Recommended Action
No special actions for order optimizing via load build, and investment buy is needed when
converting from SAP ERP to SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if retail order optimizing is used.
This is the case if transactions WLB* are used.
This also can be checked via transaction SE16N. Enter table WVFB, WBO* and check whether there
are any entries.
2.1.41.9 Retail Rapid Replenishment
Description
In SAP S/4HANA Retail for merchandise management, rapid repelnishment and planning workbench
is available, but defined as "not strategic any more". See SAP note 2269324 - Compatibility Scope
Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
There is SAP Forecstaing & Replenishment as an existing solution alternative.
Furthermore, SAP evaluates whether to develop a future replenishment solution as an consuming
application on SAP Customer Activity Repository.
Required and Recommended Action
No special actions for rapid repelnishment is needed when converting from SAP ERP to SAP
S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if rapid replenishment, or planning workbench is used.
This is the case if transactions WRP1R, WWP* are used.
2.1.41.10 Retail Additionals
Description
In SAP S/4HANA Retail for merchandise management, additionals functionality is available, but
defined as "not strategic any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP
S/4HANA, on-premise edition .
Simplification List for SAP S/4HANA 1610
347
Business Process related information
For the use cases of additionals the alternatives are:
There is an existing Fiori app to print labels.
There is existing functionality of value added services for activities or products which are
applied to ordered products that enhance their value, worth, functionality, or usefulness. It is
planned to enhance functionality of value added services in future releases.
To support processes of floor ready merchandise: development of a future solution closely
integrated with SAP EWM is under evalution.
Required and Recommended Action
No special actions for additionals functionality is needed when converting from SAP ERP to SAP
S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if additionals are used.
This is the case if transactions WTAD*, WRF_WTAD*, WTR1, WTR2, WRF_WTR3 are used.
This also can be checked via transaction SE16N. Enter table WTADDI and check whether there are
any entries.
2.1.41.11 Article Discontinuation
Description
At the end of the lifetime of an article, the discontinuation needs to be carried out to remove the
relevant article segments.
Business Process related information
In SAP S/4HANA article discontinuation via transactions WSE1, WSE2, WSE3, WSE4, WSE5, WSE8 is
not available anymore. Article discontinuation should be carried out via transaction WRF_DIS_SEL,
and WRF_DIS_MON which are richer in functionality than WSE*.
Required and Recommended Action(s)
Switch to article discontinuation via transactions WRF_DIS_SEL, and WRF_DIS_MON.
How to Determine Relevancy
This Simplification Item is relevant if transactions WSE1, WSE2, WSE3, WSE4, WSE8 are used.
Simplification List for SAP S/4HANA 1610
348
2.1.41.12 GDS simplified Inbound Price Catalog Interface
Description
In SAP S/4HANA GDS only works if the latest Open Catalog Interface (either enterprise service or IDoc
PRICECATALOGUE) is used. IDoc PRICAT is not supported anymore.
Also transaction PRICAT is not supported anymore. Transactions W_SYNC or W_PRICAT_MAINTAIN
need to be used.
Business Process related information
It is required that the latest Open Catalog Interface is used.
Required and Recommended Action(s)
Execute process as described in referenced note 2326511.
How to Determine Relevancy
This Simplification Item is relevant if GDS is used.
This is the case if transactions PRICAT, W_SYNC, W_PRICAT_MAINTAIN are used.
2.1.41.13 Business Partner in Site Master
Description
With S/4HANA 1610 the Business Partner harmonization becomes available for the site. Sites can be
migrated during the upgrade so they fulfill the new Business Partner paradigm in S/4HANA (every
customer/supplier master record must have a Business Partner as leading entity; this was not
possible on ERP for customers/vendors assigned to retail sites).
Business Process related information
The Business Partner will be the leading object.
Certain functionality of department store/shop concept is not available SAP S/4HANA. Transactions
WRFCATEGORYSHOP, WRFCLOSESHOPS, WRFDELIVERYSITESHOPS, WRFREGIONSHOPS,
WRFSHOPCAT, WRFSHOPDEP, WRF_ARC_DEPSHOP, WRF_TCHAIN_MIGR, WSHOPMIGR are not
available.
Required and Recommended Action(s)
Follow instructions in the referenced note.
How to Determine Relevancy
Simplification List for SAP S/4HANA 1610
349
This Simplification Item is relevant if retail sites are used.
This is the case if transactions WB* are used.
This can be checked via transaction SE16N. Enter table T001W and check whether there are entries
with field VLFKZ (Plant Category) not equal blank.
2.1.41.14 Article Hierarchy
Description
The article hierarchy allows grouping of articles, using a customer-oriented structure. This means it is
possible to map any hierarchical grouping of articles, in particular the consumer decision tree (CDT).
The CDT is oriented around consumers and their needs and, as far as possible, it reflects how, and
according to what needs the consumer decides to make a purchase.
Business Process related information
In SAP S/4HANA article hierarchiy maintenance via transactions MATGRP* is not available anymore.
Article hierarchies should be maitained via transactions WMATGRP* which are richer in functionality
than MATGRP*.
Required and Recommended Action(s)
Switch to article hierarchies via transactions WMATGRP*.
How to Determine Relevancy
This Simplification Item is relevant if article hierarchy of this type is used.
This is the case if transactions MATGRP01 - MATGRP07 are used.
This also can be checked via transaction SE16N. Enter table MATGRP_HIER and check whether there
are any entries.
2.1.41.15 Market Basket Calculation
Description
Market basket price calculation allowed changing sales prices for a group of articles and sites,
based on sales and gross margin figures for the articles in the market-basket, while simulating the
effects of these changes on the total gross revenue from the market.
Business Process related information
In SAP S/4HANA market basket calculation is not available anymore (as it is based on key figures from
RIS (Retail Information System), which is not available anymore).
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
350
There is no equivalent functionality to market basket calculation available in SAP S/4HANA. It is
under evaluation whether there will be functionality in a future release, or as a consuming solution
on SAP Customer Activity Repository to address the business requirement.
How to Determine Relevancy
This Simplification Item is relevant if market basket calculation is used.
This is the case if transactions WKK1 - WKK4 are used.
This also can be checked via transaction SE16N. Enter table WWKK, or WWKP and check whether
there are any entries.
2.1.41.16 Merchandise and Assortment Planning (ERP based)
Description
Merchandise and assortment planning/category management offered planning functionalities,
analysis and reporting options, for seasonal and non-seasonal retailers,
Business Process related information
In SAP S/4HANA, merchandise and assortment planning/category management is not available
anymore (software packages CM_MAP, WIS_PLAN, transaction CMMAP*, WXP*), as it is based on
key figures from RIS (Retail Information System), which is not available anymore. Please note that
this is not the BW based solution SAP Merchadise and Assortment Planning (SAP MAP). Strategic
solutions are SAP Merchandise Planning for Retail, and SAP Assortment Planning for Retail, based on
SAP Customer Activity Repository.
Required and Recommended Action(s)
Switch to strategic solutions SAP Merchandise Planning for Retail, and SAP Assortment Planning for
Retail.
How to Determine Relevancy
This Simplification Item is relevant if Merchandise and Assortment Planning/category management is
used.
This is the case if transactions WXP*, or CMMAP*are used.
This also can be checked via transaction SE16N. Enter tables S202 S203 S204 S206 S207 S208 S209
S210 S211 S212 S214 S216 S217 S218 S219 and check whether there are any entries.
2.1.41.17 Retail Method of Accounting
Description
The traditional retail method of accounting (RMA) is an averaging method that was practiced in the
retail industry. Its philosophy is based on tracking and calculating inventory information that drives
Simplification List for SAP S/4HANA 1610
351
margins, compensation, reporting, buying, pricing, and other merchandizing decisions. It was
developed before the advent of perpetual inventory systems.
Business Process related information
In SAP S/4HANA, retail method of accounting is not available anymore. Functioanlity of eRMA
(extended Retail Method of Accounting) is still available.
Required and Recommended Action(s)
Switch to eRMA.
How to Determine Relevancy
This Simplification Item is relevant if Retail Method of Accounting is used.
This is the case if transactions WRMA* are used.
This also can be checked via transaction SE16N. Enter table WRMA_CLIENT and check whether there
are any entries.
2.1.41.18 Perishables Procurement
Description
A perishables buyer needs to have all the relevant data available in order to make a qualified decision
about the perishables assortements, quantities, prices, source of supply, delivery dates and the
distribution. To address this need, the central Perishables Procurement Work Center was developed.
This work center supported the buyer with tools and consolidated informations that are required to
manage purchasing\distribution decisions for perishables across the company.
Business Process related information
In SAP S/4HANA, perishables procurement is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to perishables procurement available in SAP S/4HANA. It is under
evaluation whether there will be functionality in a future release.
How to Determine Relevancy
This Simplification Item is relevant if perishables procurement is used.
This is the case if transactions WDFR, WDFR2, WDFR3 are used.
This also can be checked via transaction SE16N. Enter table WDFR_DISP and check whether there are
any entries.
Simplification List for SAP S/4HANA 1610
352
2.1.41.19 Fresh Item Procurement
Description
Fresh item procurement was used to procure special perishable products, which are usually
characterized by a brief shelf life and are often offered by multiple vendors with restricted delivery
capacity.
Business Process related information
In SAP S/4HANA, fresh item procurement is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to fresh item procurement available in SAP S/4HANA. It is under
evaluation whether there will be functionality in a future release.
How to Determine Relevancy
This Simplification Item is relevant if fresh item procurement is used.
This is the case if transactions FIP_MD, FIP_SD, FIP_TD are used.
2.1.41.20 Retail Ledger / Profit Center Analytics
Description
The planning application "Profit Center Analytics in Retail: Store Planning" allowed planning the
finances for stores in the retail sector. A store was portrayed as a profit center and a cost center. It
was possible to perform both revenue planning and cost planning for the stores.
Business Process related information
In SAP S/4HANA, Retail Ledger / Profit Center Analytics is not available anymore.
Required and Recommended Action(s)
Strategic planning solutions are SAP Merchandise Planning for Retail, and SAP Assortment Planning
for Retail
How to Determine Relevancy
This Simplification Item is relevant if profit center analytics is used.
This is the case if transactions RETAIL_* are used.
This also can be checked via transaction SE16N. Enter table PCRRETAILA and check whether there are
any entries.
Simplification List for SAP S/4HANA 1610
353
2.1.41.21 Goods Receipt Capacity Check
Description
Goods receipt capacity was used for checking the schedule and the delivery dates of a vendor. Thus,
allowing to distribute the load of the goods receipt evenly, avoiding bottlenecks during inbound
delivery.
Business Process related information
In SAP S/4HANA, goods receipt capacity check is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to goods receipt capacity check available in SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if goods receipt capacity check is used.
This is the case if transactions WGRC* are used.
This also can be checked via transaction SE16N. Enter table WGRC_ACT* and check whether there
are any entries.
2.1.41.22 Online Store
Description
The online store was a solution for electronic commerce. The online store could be configured for
consumer-to-business and for business-to-business use.
Business Process related information
In SAP S/4HANA, online store functionality is not available anymore.
Required and Recommended Action(s)
SAP Hybris Commerce is the strategic solution for omnichannel commerce.
How to Determine Relevancy
This Simplification Item is relevant if online store is used.
This is the case if transactions WW10, WW20, WW30 are used.
2.1.41.23 Generic Article Harmonization
With SAP S/4HANA, Generic article harmonization becomes available for configurable material. In
SAP S/4HANA, Generic article is assigned to a configuration class and the variant creating
Simplification List for SAP S/4HANA 1610
354
characteristics for that generic article are taken from that configuration class of iBase storage only.
For this reason, different DB tables are needed to be accessed to get data like variant creating
characteristics, assigned configuration class and so on. So if you have custom code, which access DB
tables to read data about variant creating characteristics of a generic article then please check the
attached pdf document to see how to access it now in SAP S/4HANA.
2.1.41.24 Retail Labeling
Description
It was possible to trigger label printing via retail labeling.
Business Process related information
In SAP S/4HANA, retail labeling (software package WETI) via transactions WEBU, WENA, WESO is not
available anymore
Required and Recommended Action(s)
The Fiori app Print Lables should be used to trigger label printing.
How to Determine Relevancy
This Simplification Item is relevant if labeling is used.
This is the case if transactions WEBU, WENA, WESA are used.
2.1.41.25 Seasonal Procurement
Description
Seasonal procurement covers purchasing processes that are specially designed to suit the
requirements of seasonal procurement of retail goods, for example, from the area of fashion.
Business Process related information
In SAP S/4HANA, seasonal procurement is not available anymore.
Software packages WRF_APC, WRF_AT_GENERATE, WRF_PRC_CON_APPL, WRF_PRC_CTR_APPL,
WRF_PRC_OTB_APPL, WRF_PRC_POHF_APPL, WRF_SEAS.
Transactions: WRFAPC*, WA10, WCOC*, WPCTR*, WOTB*, WPOHF*, WRFROCAT, WOOS.
Required and Recommended Action(s)
Processes for fashion retailers that are available already or wÃll be released in the future should be
used for seasonal procurement. Planning solutions SAP Merchandising Planning for Retail, and
SAP Assortment Planning for Retail should be considered as well.
Simplification List for SAP S/4HANA 1610
355
How to Determine Relevancy
This Simplification Item is relevant if seasonal procurement is used.
This is the case if transactions WRFAPC*, WA10, WCOC*, WOTB*, WPCTR*, WPOHF*, WRFROCAT,
WOOS are used.
This also can be checked via transaction SE16N. Enter table WRF_APC_PLH and check whether there
are any entries.
This also can be checked via transaction SE16N. Enter table EKKO and check whether there are
entries with field POHF_TYPE (Seasonal Purchase Order Processing) is not equal blank.
2.1.41.26 Replenishment
Description
Replenishment calculates the procurement dates and quantities for articles per store, based on
various parameters (e.g. on-hand inventory, forecasted demand, shelf space), and can also create the
resulting procurement documents.
Business Process related information
In SAP S/4HANA, replenishment (main transaction WRP1) and multi-step replenishment (transactions
WRFE, WRSO, WRSR, ...) are not available anymore.
Required and Recommended Action(s)
Rapid Replenishment (transaction WRP1R) covers a similar scope, but is superior from a performance
perspective.
How to Determine Relevancy
This Simplification Item is relevant if replenishment is used.
This is the case if transactions WR30, WR31, WR94, WR95, WRP1, WRFE, WRSO, WRSR are used.
2.1.41.27 Retail Information System
Description
The information systems used to plan, control, and monitor business events at different stages in the
decision-making process. Tools were available in Customizing to allow a self-defined information
system to be created and tailored to specific requirements.
Business Process related information
In SAP S/4HANA, RIS functionality is not available anymore.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
356
RIS (Retail Information System) technology is not available anymore. To cover operational reporting
requirements CDS (Core Data Services) technology should be used. It is planned to offer retail specific
content in a future release.
How to Determine Relevancy
This Simplification Item is relevant if RIS is used.
This also can be checked via transaction SE16N. Enter table S077 S078 S079 S080 S081 S082 S083
S084 S085 S086 S087 S105 S106 S107 S108 S110 S117 S119 S120 S121 S122 S123 S124 S160 S200
S202 S203 S204 S205 S206 S207 S208 S209 S210 S211 S212 S214 S216 S217 S218 S219 S270 S271
S272 S273 S274 S275 S276 S277 S278 S279 and check whether there are any entries.
2.1.41.28 SAP Retail Store
Description
SAP Retail Store enhanced and optimized tools available for executing store-oriented processes by
providing store associates with specially developed store management functions. It offered a webbased user interface that was tailored specifically to the requirements of stores.
Business Process related information
In SAP S/4HANA, SAP Retail Store is not available anymore.
Required and Recommended Action(s)
Simplified user interfaces to support store associates/managers are available as Fiori apps or as part
of In-Store MIM (Merchandise and Inventory Management) (Web Dynpro ABAP).
How to Determine Relevancy
This Simplification Item is relevant if SAP Retail Store is used.
This is the case if transactions WCSO WCSOD WCU2 WSAK WSAM_ENTRY WSAU WSGM WSHT
WSSW WSTA WSTE WSTE_NEW WSTED WSTI WSTL WSTP WSTSA WSTU WSTV
WSTV_R_PDC_MATDATA WOSCR_CBL WSRS_HI_MENU are used. This is not a complete list.
2.1.41.29 Retail iViews
Description
An iView (integrated view) was a logical portal content building block representing a visual
application or part thereof. There were some iViews to support retail buying.
Business Process related information
In SAP S/4HANA, retail buying iViews are not available anymore.
Simplification List for SAP S/4HANA 1610
357
Required and Recommended Action(s)
In SAP S/4HANA there are alternatives to display the information.
How to Determine Relevancy
This Simplification Item is relevant if iViews for retail buying are used.
This is can be observed if functions modules WRB_RFC_GET_OPEN_PO_OVERVIEW,
WRB_RFC_GET_VENDOR_OPEN_PO, WRB_RFC_GET_OOS_OVERVIEW,
WRB_RFC_VENDOR_GET_OUTOFSTOCKS, WRB_RFC_VENDOR_GET_CONTACTDATA are called.
2.1.41.30 Prepack Allocation Planning
Description
Prepacks are integrated into the allocation planning process. Via prepack allocation planning it was
possible to define prepacks for a generic article using existing quota scales (size curves) or by
manually entering size distributions. Allocation tables and vendor purchase orders could be
generated and kept synchronized.
Business Process related information
In SAP S/4HANA, prepack allocation planning is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to prepack allocation planning available in SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if prepack allocation planning is used.
This is the case if transactions WSTN11, WSTN13, WSTN14, WSTN15 are used.
This also can be checked via transaction SE16N. Enter table WSTN_PP_HEADER and check whether
there are any entries.
2.1.41.31 Assortment List
Description
Assortment List can be used, among other use cases, to send article information to POS, or store
merchandise management solutions. It comprises all the article the respective store carries.
Information per store includes short text, GTIN, unit of measure, sales prices etc. It is possible to send
a manual, inital or a delta version of the assortment list.
Business Process related information
Simplification List for SAP S/4HANA 1610
358
In SAP S/4HANA, assortment list functionality via transaction WBBA, WDBI, WDBI_ALV, WDBM,
WDBM_ALV, WDBU, WDBU_ALV is not available anymore.
Required and Recommended Action(s)
Assortment List HPR (High Performance Retailing) functionality via transaction WDB*HPR* is
still available in SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if assortment list is used.
This is the case if transactions WBBA, WDBI, WDBI_ALV, WDBM, WDBM_ALV, WDBU, WDBU_ALV are
used.
2.1.41.32 In-store food production integration
Description
In the retail grocery industry it can be relevant to manage processes involving a store's fresh items.
The in-store food production integration enabled integration to an external In-Store Food Production
(ISFP) software solution.
Business Process related information
In SAP S/4HANA, in-store food production integration is not available anymore.
Required and Recommended Action(s)
There are other communication scenarios in SAP S/4HANA to allow integration with non-SAP
solutions.
How to Determine Relevancy
This Simplification Item is relevant if in-store food production integration is used.
This is the case if enterprise services
StoreERPReplicationBulkRequest_Out
StoreGroupERPReplicationBulkRequest_Out
SupplierERPReplicationBulkRequest_Out
ProductCategoryHierarchyERPReplicationRequest_OUT
PhysicalInventoryCountERPRequest_Out
PhysicalInventoryCountERPCreateRequest_In
PhysicalInventoryCountERPConfirmation_In
GoodsMovementERPCreateRequest_In
GoodsMovementERPNotification_Out
are used.
Simplification List for SAP S/4HANA 1610
359
2.1.41.33 PRICAT Outbound
Description
PRICAT outbound was used to send material master data and price information to business partners.
Business Process related information
In SAP S/4HANA, PRICAT outbound is not available anymore.
Required and Recommended Action(s)
There are other communication scenarios in SAP S/4HANA to send article information.
How to Determine Relevancy
This Simplification Item is relevant if PRICAT outbound is used.
This is the case if transactions VPRE, VPRICAT, WEB_PRICAT, WPRI are used.
This also can be checked via transaction SE16N. Enter table PRICAT_K001 and check whether there
are any entries.
2.1.41.34 Retail Business Function Harmonization
Description
In SAP S/4HANA the structure of the Retail Business Functions was reorganized and simplified so
that most of the Retail functions and features can be switched on by the Enterprise Business
Function ISR_RETAILSYSTEM..
Business Process related information
Business processes will not be affected directly. For details see referenced note.
Required and Recommended Action(s)
No activity is needed. For details see referenced note.
How to Determine Relevancy
This Simplification Item is relevant if you have activated the Business Function Set ISR_RETAIL. This
can be checked via transaction SFW5.
2.1.41.35 Retail Obsolete Transactions
Description
With the installation of the SAP S/4HANA, certain transactions will not be available anymore.
Simplification List for SAP S/4HANA 1610
360
Business Process related information
Transactions which are not available anymore in SAP S/4HANA are listed below.
Required and Recommended Action(s)
Obsolete Transaction
CLWA
CLWB
CLWC
CLWD
CLWJ
CLWK
CLWL
WTRA1
WTRA2
WTRA3
WA05
WA06
WA07
WA12
WA15A
WA15B
WA15C
WA40
WA50
WA53
WA54
WA60
WC11
Description of Transaction
Create Material Group (MMS)
Change Material Group (MMS)
Display Material Group (MMS)
Delete Material Group (MMS)
Change Generic Article (MMS)
Display Generic article (MMS)
Delete Generic Article (MMS)
Maintain Runtime Customizing Table
Runtime Measurement: Delete Logs
Runtime Measurement: Display Logs
Alloc Tbl FDG: Generate POs
Alloc Tbl FDG: Generate Deliveries
Alloc Tbl FDG: Generate Wrhse Orders
Create Reminders/Accept Plnd Qties
Mess.Deter., Alloc Tbl: Creat.Cond.R
Mess.Deter.,Alloc Tbl: Chng Cond.Rec
Mess.Deter.Alloc Tbl: Displ Cond.Rec
Adjust Alloc Tbl After Entering GR
Generate Allocation Rule
Create Selection Variants
Generate Alloc Rule / Test RIS-L
Create Selection Variant for PO
Batch Changes, Assortments
WC21
Batch Reorg Data in LIS
WC25
Batch Assortment List/Shelf-Edge Lab
WC26
Batch Forecast
WC27
Batch Requirements Planning per Plnt
WC33
Batch worklist for doc. index
WC41
Assortment List: Initial. & FullVers
WER_RULE_PROC_TEST
WB07
WB08
WB30
WB35
WBTE
WBTI
WBTIMEX
WBTIMEX_CUST
WDH1
Test program for processing rules
Change plant/customer assignment
Change plant/vendor assignment
Mass maintenance MG to plant
Layout overview
Export plant data (file transfer)
Import plants (file transfer)
Site Master Transport
Customize Site Master Transport
Maintain plant hierarchy (SD)
Simplification List for SAP S/4HANA 1610
Alternative Transaction
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
not relevant anymore
not relevant anymore
not relevant anymore
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was never released
WA/A
WA/B
WA/C
was already obsolete in SAP ERP
obsolete because of deprecated RIS
obsolete because of deprecated RIS
obsolete because of deprecated RIS
obsolete because of deprecated RIS
batch transaction of "real"
transaction
batch transaction of "real"
transaction
batch transaction of "real"
transaction
batch transaction of "real"
transaction
batch transaction of "real"
transaction
batch transaction of "real"
transaction
batch transaction of "real"
transaction
test transaction
not relevant anymore
not relevant anymore
WB30N
obsolete because of deprecated RIS
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
361
WDH2
WOG3
WF10A
WF50A
WF80_DEL
WF90_DEL
WLB3
WGDS_CONFIRM
WGDS_CONFIRM_MANAGER
ARTE
WLAM
WLMM
WLMV
WLWB
WPLG
WRFMATCHARVAL
WRF_WSOA1
WRF_WSOA2
WRF_WSOA3
WRF_WSOA4
W_PRICAT_ASSIGN_001
W_PRICAT_ASSIGN_003
W_PRICAT_SEL_CREATE
WRF_PRICAT_LOG1
WSFP_LOG_ALL_IN
WSFP_LOG_ALL_OUT
WSFP_LOG_CHG_OUT
WSFP_LOG_INIT_OUT
WSFP_LOG_INTERNAL
WSFP_LOG_MAN_OUT
WSFP_TRANSFER
WLAN
WSK3
WSL3
WSL4
WSL5
WSL6
WSL7
WSLA
WSLB
WSLG
WSM4
WSM6
WSM7
WSM8
WSM11
WSOA5
WSOE
WSP6
WSOSDISPLAY
MGW0
MGW1
MGW2
MGW3
Display customer hierarchy (SD)
Plant groups
Collective PO Without Tabstrips
Adjust Distribution
Display Delivery Generation Logs
Delete Delivery Generation Logs
Autom. opt. PO-based load building
Send confirmation
Confirmation manager
Replace Articles in Layout Modules
Layout Maintenance
Layout Module Maintenance
Maintenance of Layout Module Version
Layout Workbench
Space Management
Char. Value Change to Variants
Create Assortments
Change Assortments
Display Assortments
Delete Assortment
Assignment ILN Vendor Pur. Group
Assignment SAP Mat. Gr. - Purch.Gr.
Maintain Price Catalog
Log for Price Catalog
Ind Processing, All Logs
All Logs
Change Messages Log
Initial Data Transfer
For Internal Use Only
Manual Selection
Master Data Transfer
Listing Conditions for Layout Module
Assortment copy, batch input
Material listed in plant before?
Analyze material in module
Modules in plant
Assortment structure, Plants
Vendor material list
Assortment Users per Assortment
Assortment per Assortment User
Compare promotion POs - sales orders
Relist after ch. plant/ mat. grp mas
Delete Individual Listing, Material
Delete Individual Listing, Material
Setup assrt.owner assortment as WRF6
replicate sales data to site level
Assign assortment to customer
Assign material groups
Delete ind. listing, mat. - plant
Display Possible Sources of Supply
Create Components for Set Material
Display Components for Set Material
Create Components for Display Matl
Display Components for Display Matl
Simplification List for SAP S/4HANA 1610
not relevant anymore
was already obsolete in SAP ERP
WF10
WF50
WF80
WF90
WLB13
not relevant anymore
not relevant anymore
not relevant anymore
WLWBN
WLWBN
WLWBN
WLWBN
WPLGN
not relevant anymore
WSOA1
WSOA2
WSOA3
WSOA4
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
WESLOG
WESLOG
WESLOG
WESLOG
WESLOG
WESLOG
WESOUT
not relevant anymore
not relevant anymore
WSL11
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
was already obsolete in SAP ERP
was already obsolete in SAP ERP
WSE6
WSE6
WSM3
not relevant anymore
WSOA2
was already obsolete in SAP ERP
WSE6
not relevant anymore
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
362
MGW4
MGW5
MGW6
MGW7
MGW 8
MGW9
MGWA
MGWB
DUMMY_MASS_VENDOR
MASS_VENDOR
WMATGRP06
WMATGRP08
WOOS
WDKR
Create Components for Prepack Matl
Display Components for Prepack Matl
Create Components for Full Product
Display Components for Full Product
Change Components for Set Material
Change Components for Display Matl
Change Components for Prepack
Change Components for Full Product
Load programs global data
Vendor Mass Maintenance
Copy Article Hierarchy
Simulation of Article hierarchy copy
Order View
Create customer from vendor
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
was already obsolete in SAP ERP
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
How to Determine Relevancy
This Simplification Item is relevant if any of the above listed transactions is used.
2.1.41.36 Value and Quota Scales
Description
For variants of a generic article it is possible to define ratios for the respective variants via value and
quota scales. Those ratios can be used in purchase orders, or allocation tables to propose default
quantities for procurement.
Business Process related information
In SAP S/4HANA value and quota scales are not available anymore. Distribution curve is the strategic
solution with similar semantics but richer in functionality than value and quota scales.
Required and Recommended Action(s)
Switch to strategic functionality of distribution curves.
How to Determine Relevancy
This Simplification Item is relevant if value and quota scales are is used.
This is the case if transactions WC01 WQ01 WQ02 WQ03 WQ04 WQ05 WQ11 WQ12 WQ13 WQ14
WQ15 WQ21 are used.
This also can be checked via transaction SE16N. Enter table WMQK, or WMWK and check whether
there are any entries.
2.1.41.37 AIN
Description
Simplification List for SAP S/4HANA 1610
363
Via AIN the following functions could be performed for India:
Control the price fluctuations and protect the margin agreed between the buyer and the
vendor during the procurement process.
Update the MRP (Maximum Retail Price) of an article in the purchase order (PO) and the
article master if there is a change in the MRP when you receive the goods from the vendor
Business Process related information
In SAP S/4HANA, AIN (India Margin Protection) is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to AIN available in SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if AIN is used.
This is the case if transactions J1IR01 J1IR02 J1IR03 J1IR10 J1IR20 J1IRAIN01 J1IRAIN02 J1IRAIN03
J1IRAIN10 J1IRAIN20 are used.
This also can be checked via transaction SE16N. Enter table J_1IRAINHDR and check whether there
are any entries.
2.1.41.38 Retail Season Conversion
Description
In SAP S/4HANA certain functionality is not supported anymore, among others the Retail Season (e.g.
customizing tables T6WSP, TWSAI).
With the conversion, the following new season fields are introduced:
SEASON YEAR
SEASON
COLLECTION
THEME
The old season fields in the article master on the Basic Data (table MARA) are not used
anymore. The new season fields will be maintained on Basic Data 2 (table FSH_SEASONS_MAT).
Business Process related information
The season will not be defined in the customizing anymore, instead there is the Season
Workbench (transaction FSH_SWB) available as a application transaction. Part of the conversion from
SAP ERP to SAP S/4HANA, article need to be resasigned from "old" to "new" season. With the
conversion, the following tables are filled automatically:
Simplification List for SAP S/4HANA 1610
364
Assignment season to article
o FSH_SEASONS_MAT
Season definition
o FSH_SEASONS
o FSH_SEASONS_T
o FSH_SD_PERIODS
o FSH_MM_PERIODS
o FSH_COLLECTIONS
o FSH_COLLECTION_T
Note: The season fields are no longer maintained in table MARA. All relevant season information is
now maintained in table FSH_SEASONS_MAT.
Required and Recommended Action(s)
During the conversion, the following reports are executed automatically:
R_FSH_S4_SEASONS_MD_MIG to convert the season Customizing data
R_FSH_S4_SEASONS_MAT_MIG_XPRA (XPRA) to convert the season assignment to article
In case of problems during the conversion, you can execute these reports manually.
Note that R_FSH_S4_SEASONS_MAT_MIG_XPRA is a cross-client enabled report, whereas
R_FSH_S4_SEASONS_MD_MIG has to be executed in each client required.
How to Determine Relevancy
This Simplification Item is relevant if retail season is used.
This can be checked via transaction SE16N. Enter table MARA and check whether there are entries
with field SAISO (Season) not equal blank.
2.1.41.39 SAP Smart Business for Retail Promotion Execution
Description
SAP Smart Business for Retail Promotion Execution offers insight-to-action capabilities based on realtime overviews to mitigate exceptions for promotion execution.
Business Process related information
In SAP S/4HANA, SAP Smart Business for Retail Promotion Execution (based on SAP HANA Live VDM
(Virtual Data Model)) is not available.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 1610
365
There is no equivalent functionality to SAP Smart Business for Retail Promotion Execution available in
SAP S/4HANA. It is under evaluation whether there will be functionality in a future release.
2.1.41.40 Retail Factsheets
Description
Fiori Factsheets allow to user friendly display of business objects.
Business Process related information
In SAP S/4HANA, retail specific Fiori Factsheets for article, site, allocation, promotion, and bonus buy
are not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality. It is under evaluation whether there will be Object Pages for
those business objects in a future release.
2.1.41.41 Retail Short Text Replacement
Description
Via short text replacement industry specific terminology can be used on user interfaces. In Retail, e.g.
material, plant, material group, factory calendar are not common terms. Terms article, site,
merchandise category, logistics calendar are more common.
Business Process related information
In SAP S/4HANA, retail short text replacement (as described in note 897714) is not available
anymore.
Required and Recommended Action(s)
There is no equivalent functionality. It is under evaluation how to provide industry specific
terminology in a future release.
How to Determine Relevancy
This Simplification Item is relevant if retail short text replacement is used.
Call transaction MM01. If it reads "Create Article" the replacement is used, if it reads "Create
Material" it is not used.
2.1.41.42 Retail Store Fiori App
Description
Simplification List for SAP S/4HANA 1610
366
In SAP S/4HANA, some table structures have changed. Thus, open transfer stock documents need to
be closed prior to the conversion.
Business Process related information
Business processes will not be affected.
Required and Recommended Action(s)
Please, follow instructions of referenced note.
How to Determine Relevancy
This Simplification Item is relevant if the Fiori app for transfer stock is used.
This can be checked via transaction SE16N. Enter table TRF_DOC_HEAD and check whether the table
exists or there are any entries in the table.
2.1.41.43 SAP AFS Integration
Description
SAP Apparel & Footwear (SAP AFS) is not part of the SAP S/4HANA solution portfolio. It is planned to
release verticalized fashion processes in the future.
In SAP S/4HANA the functionality to integrate with SAP AFS is available, but defined as "not strategic
any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, on-premise
edition
Business Process related information
Move to verticalized fashion processes once available.
Required and Recommended Action
No special actions for the SAP AFS integration scenario is needed when converting from SAP ERP to
SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if Apparel and Footwear integration is used.
This is the case if transaction WAFS is used.
2.1.41.44 POS Outbound via Idoc WP_PLU
Description
Simplification List for SAP S/4HANA 1610
367
In SAP S/4HANA Retail for merchandise management, there are several alternatives for sending
product information to stores (typically to POS solutions, or in-store merchandise management
solutions).
In SAP S/4HANA 1610 release sending information via IDoc WP_PLU is available, but defined as "not
strategic any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, onpremise edition
Business Process related information
Move to other communcation methods (e.g. Assortment List (High Performance Retailing), enterprise
service Merchandise Replication).
Required and Recommended Action
No special actions for POS outbound scenario via IDoc WP_PLU is needed when converting from SAP
ERP to SAP S/4HANA.
2.1.41.45 Valuation in Retail
Data model changes in Material Ledger and Accounting (see note #2337368) have affected the way,
retail revaluations are posted. When you are using the stock valuation at sales price, as this is usual in
retail systems, this note describes the changes, that may be relevant for custom coding.
Revaluations affecting margins are posting financial documents
Function Module STOCK_SALES_PRICE_REVALUATION, as well as the
FORMS purchase_price_calculate and purchase_prepare_price_data have been changed, so that
they are posting financial documents at the end. In SAP ERP this was the case for the revaluation not
affecting margins only. The financial posting leads to entries in tables ACDOCA and
ACDOCA_M_EXTRACT which are used to aggregate the MBEW-VKSAL field. (See changes in Material
Ledger note #2337368).
Revaluations not affecting margins are updating stock values at cost in alternative material ledger
currencies
When a revaluation leads to changes in the stock value at purchasing price, this change is now posted
in all material ledger currencies. This is normally the case, when you use a revaluation profile "not
affecting margins". This change is implemented in FORM add_material_ledger_currencies in
include LWBW1F09.
How to Determine Relevancy
This Simplification Item is relevant if sales price valuation, or value-only articles are is used.
This can be checked via transaction SE16N.
Sales price valuation: Enter table T001K and check whether there are entries with field XVKBW (Sales
price valuation active) not equal blank.
Simplification List for SAP S/4HANA 1610
368
Value-only article: Enter table T023W and check whether there are entries with field WWGPA
(Material group material) not equal blank. If this is the case, that is a good indicator that value-only
articles are used.
2.1.41.46 Retail Demand Management Integration
Description
SAP Retail Demand Management is not part of the SAP S/4HANA solutions portfolio.
In SAP S/4HANA Retail for merchandise management, functionality to support Retail Demand
Management integration is available, but defined as "not strategic any more". See SAP note 2269324
- Compatibility Scope Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
Move to other available communcation methods.
Required and Recommended Action
No special actions for Retail Demand Management integration is needed when converting from SAP
ERP to SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if retail demand management integration is used.
This is the case if transactions RDMCHG RDMINI RDMMAN RDMREO RDMSEL RDM_S* are used.
2.1.42 Industry Telecommunication
2.1.42.1 Lock and unlock services using IST_TDATA
Description
The IST_DATA table is used to store all telecommunications services data that is relevant to
Receivables Management Contract (RM-CA) used for creating requests to lock or unlock services. In
case of using the provider order in Accounting Receivables Management (RM-CA) this table is not
needed any more. All necessary data can be retrieved from the provider contract
Business Process related information
In case you are already using database table IST_TDATA for managing telecommunication services
and the provided contract as well, you can continue storing telecommunication service data in
database table IST_TDATA. In case you decide to discontinue using table IST_TDATA RM-CA items
already posted, still overdue and reason for locking the telecommunication service are still processed
Simplification List for SAP S/4HANA 1610
369
based on the functionality using the database table IST_TDATA. New open items, posted on a
provider contract and causing a request for locking the telecommunication service are processed
based on the provider order data and do not lead to a new entry in database table IST_TDATA. For
discontinuation of using database table IST_TDATA please change the settings in customizing:
SAP Telecommunications -> Basic Settings -> Telecommunications Services in SAP RM-CA -> Define
Basic Settings for Managing Service Data
Required and Recommended Action(s)
No changes in business processes, it might (if you decides for) only has an influence on technical level
in the sense of "how necessary information are be retrieved from system".
2.1.42.2 PORTAL ROLES FOR NETWORK LIFECYCLE MANAGEMENT (NLM)
Description
Portal roles (SAP ERP) for the Network Lifecycle Management (NLM) area of the telecommunications
sector are not available within SAP S/4HANA, on-premise edition 1511 (no functional equivalent
available). This functionality was intended to implement the following portal roles as business
packages for the Network Lifecycle Management area of the telecommunications sector:
Business Package for Site Technician (Telecommunications)
Business Package for Workforce Manager (Telecommunications)
Business Package for Network Operation Manager (Telecommunications)
Business Process related information
No influence on business processes as the functionality itself is still available. This is only related to
the possibility of implementing the portal roles
2.1.43 Industry Utilities
2.1.43.1 CVI Integration for SAP ISU
Description
In SAP S/4HANA, on-premise edition, the central business partner approach is mandatory. Customer
and vendor master record creation, maintenance and display is only possible via the Business Partner
functionality (Transaction 'BP'). For more information, see the simplification item Business Partner
Approach (SAP Note 2265093).
Simplification List for SAP S/4HANA 1610
370
Consequently, the former concept of SAP IS-U Business Partner and SAP SD Customer integration in
SAP ERP has been substitued by SAP Customer Vendor Integration (CVI) in SAP S/4HANA. Please note
that 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 1511. A system where
the customer/vendor integration is not in place will be declined for the transition.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
In addition to following the required steps as suggested in the 'Required and Recommended
Action(s)' section of SAP Note 2265093, execute the following two reports for data conversion:
Report Name
Purpose
REU_CVI_CUST_LINK
Establishes a link between the business partner and the customer as required
by the standard Customer Vendor Integration (CVI) solution
REU_CVI_EKUN_TO_BUT0ID
Converts the ISU-specific identification fields from the table EKUN to the table
BUT0ID in the system
SAP Note 2202282 is used for the SAP S/4 HANA IS-UT master check for the system conversion check
in order to ensure the data conversion. If the aforeementioned two reports are not run, the system
master check S4TC will fail.
Related Information
For further information, please see
Conversion Guide for SAP S/4HANA 1511, on-premise edition
IS-U Specifics on the Set-Up-and-Load-Guide for the Business Partner in SAP S/4HANA.
(attached with this note)
IS-U Specifications for the Set-Up and Load Guide for Business Partner Relationships and
Partner Roles (attached with this note)
2.1.43.2 Multichannel Foundation for Utilities
You currently use or are planning to use product SAP Multichannel Foundation for Utilities and Public
Sector for your B2C consumer self-services and you are doing a system conversion to SAP S/4HANA.
The following SAP S/4HANA Transition Worklist item is applicable in this case.
Description
Simplification List for SAP S/4HANA 1610
371
SAP Multichannel Foundation for Utilities and Public Sector (SAP MCF) offers utilities companies a
powerful and cost-effective way to extend their customer interactions to digital channels such as
Mobile, Web, and Social. SAP MCF exposes business processes out of SAP IS-U and SAP CRM for
Utilities by way of OData services enabling the utilities company to offer self-service apps and
website for their consumers. MCF is delievered as 3 add-ons: UMCERP01 on SAP ERP, UMCCRM01 on
SAP CRM and UMCUI501 on SAP Gateway. The SAP ERP and SAP CRM add-ons contain OData
services for self-service business processes whereas the SAP Gateway add-on UMCUI501 contains
two template SAPUI5 apps/UIs that are integrated with the OData services. These SAPUI5 template
apps serve as examples demonstrating the consumption of SAP MCF's OData services and how they
may be integrated into a self-service website or mobile app. With SAP S/4HANA 1610, the SAP ERP
add-on UMCERP01 has been retrofitted into the IS-UT layer. The SAP CRM add-on UMCCRM01
remains unaffected and you can continue to use it after conversion of your SAP ERP system to SAP
S/4HANA 1610. If you are currently using one of the two SAPUI5 template apps delivered in add-on
UMCUI501 or are using your own UI/mobile app, you will need to adapt the code as per the
instructions in this Note (See "Required and Recommended Action(s)' section below) and the
corresponding custom code SAP note: 2352104. Optionally, you can also use our new SAPUI5
responsive UI template delivered in a new UI SAP Gateway add-on called UIS4MCF. This new UI
template is pre-integrated into SAP Multichannel Foundation for Utilities and Public Sector on
S/4HANA 1610. These instructions will also apply if you use the SAP MCF mobile app called SAP SelfService for Utilities for Android and iOS. The code of the mobile app will need to be adapted as well.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Follow the instructions in SAP note: 2352104 and the attached Cookbook.
2.1.43.3 Monitoring Profile Value Import
Description
SAP EDM (Energy Data Management) provides a transaction for monitoring the import of profile data
from external sources into the SAP EDM data repository. The former transaction EDM1 has been
replaced by the new transaction EDM1N that provides more functional features, improved
enhancement capabilities and improved user interfaces. Usage of SAP EDM and specifically import of
EDM profile data is indicated by entries in table EEDMIMPORTLOG_DB (checked via transaction
SE16).
Business Process related information
No change in business process
Transaction not available in SAP
S/4HANA on-premise edition 1511
EDM1
Simplification List for SAP S/4HANA 1610
372
2.1.43.4 Utilities Customer Electronic Services (UCES)
This Simplification Item is only relevant if you are using the SAP Netweaver JAVA component Utility
Customer E-Service. Functionality Utilities Customer Electronic Services (UCES) is not available in SAP
S/4HANA 1511. Functional equivalent named Multichannel Foundation for Utilities and Public Sector
(MCF) is planned for shipment in SAP S/4HAHA 1610. MCF provides a set of standardized and
reusable OData services that consist of self-service scenarios that enable customers to securely
access and manage key account information and perform important self-service activities online, like
bill payment, entering meter readings, creating inquiries, sending requests to a utility company and
so on.
2.1.43.5 Stock and Transaction
Description
IS-U Stock and Transaction Statistics based on Logistics Information System (LIS) is not available
within SAP S/4HANA, on-premise edition 1511. The corresponding functionality and transactions can
be found in SAP Business Suite in the SAP Easy Access menu under "Utilities Industry" - "Information
System" - "Utlities Information System" - "Stock Statistics" and "Transaction Statistics", respectively.
In SAP S/4HANA, "Stock Statistics" and "Transaction Statistics" are not available anymore. Usage of
UIS is indicated by entries in database tables TE789C and TE790C with ACTIVE field set to X. If no
entries exist, this note is not relevant for you. The check can be done via transaction SE16.
2.1.43.6 IS-U Sales Processing
Description
IS-U Sales Processing is not available within SAP S/4HANA, on-premise edition 1511.
Transactions ISU_SALES_QUOTATION - Create Sales Quotation - and ISU_SALES_ORDER - Create Sales
Order - are not available in SAP S/4HANA. Usage of IS-U Sales Processing is indicated by entries in
database table ESALES_PRODSALES. If there are no entries, this note is not relevant for you.
2.1.43.7 Marketing - IS-U Loyalty Program
Description
IS-U Loyalty Program is not available within SAP S/4HANA, on-premise edition 1511. All functionality
and transactions related to Loyalty Program are not available in SAP S/4HANA. Usage of Loyalty
Management is indicated by entries in table ELACC.
2.1.43.8 Front Office (EC20)
Description
Simplification List for SAP S/4HANA 1610
373
IS-U Front Office (EC20) is not available within SAP S/4HANA, on-premise edition 1511.
2.1.43.9 GIS Business Connector
Description
IS-U GIS Business Connector is not available within SAP S/4HANA, on-premise edition 1511. An
indicator for usage of IS-U GIS Business Connector is the existence of entries in table GCCA.
2.1.43.10 Enterprise Services for SAP for Utilities (IS-U)
Description
The following Enterprise Services for SAP for Utilities (IS-U) are not available in SAP S/4HANA, onpremise edition 1511, and following releases:
TEST_UtilitiesConnectionStatusChangeRequestConfirmation_Out
TEST_UtilitiesConnectionStatusChangeRequestCancelRequest_In
TEST_UtilitiesConnectionStatusChangeRequestRequest_In
UtilitiesConnectionStatusChangeRequestConfirmation_In
UtilitiesConnectionStatusChangeRequestCancelRequest_Out
UtilitiesConnectionStatusChangeRequestRequest_Out
UtilitiesTimeSeriesBundleItemCreateConfirmation_In
UtilitiesTimeSeriesBundleItemCreateRequest_In
UtilitiesTimeSeriesBundleItemCreateConfirmation_Out
UtilitiesTimeSeriesBundleItemCreateRequest_Out
There is no precise check on the usage of obsolete Enterprise Services. Looking for service messages
of these obsolete enterprise services in the monitoring transactions SXMB_MONI (using Monitor for
Processed XML Messages) and SRT_MONI indicates the usage. Please check referenced
notes 1541831 - UtilitiesConnectionProcessing enterprise services in EHP5 - and 1527380 Deprecated ES, EHP6 for ERP, UtilitiesTimeSeriesProcessing - for detailled information.
2.1.43.11 Central and Eastern European localization for Utility & Telco
Description
As of SAP S/4HANA 1610 (components FI-CA 801 and IS-UT 801) the localization Add-On CEEISUT for
Telco and Utilities industries is retrofitted into SAP S/4HANA - see the release strategy SAP Note
1014997. Appends of DDIC objects enhancing core structures and tables shipped with the CEEISUT
have become switchable. Therefore it is necessary to have these Switches switched on (in active
state) before upgrade to S/4HANA in order to avoid any data loss. A customer using CEEISUT need to
ensure that a dedicated Business Function Set is active before he converts his system to SAP
S/4HANA - either UTILITIES or TELCO. The related pre-check (see the SAP Note 2314696) raises an
error when CEEISUT Add-On is installed and none of the following Business Function Sets is in active
state or any its underlying object (Business Function, Switch, Package) is not present in an active
Simplification List for SAP S/4HANA 1610
374
version in a system or any of Business Functions or Switches is not in active state. See the hierarchy
of both Business Function Sets below.
Business Function Set 'UTILITIES':
Business Function /SAPCE/ISU_LOC_CEE
o Switch /SAPCE/ISU_LOC_CEE_SFWS_02
Switch Package /SAPCE/IU_LOC_CEE_SFWS_02
o Switch /SAPCE/FICA_LOC_CEE_SFWS_02
Switch Package SAPCE/FK_LOC_CEE_SFWS_02
Business Function ISU_UTIL_WASTE
o Switch /SAPCE/ISU_LOC_CEE_SFWS_01
Switch Package /SAPCE/IU_LOC_CEE_SFWS_01
o Switch /SAPCE/FICA_LOC_CEE_SFWS_01
Switch Package /SAPCE/FK_LOC_CEE_SFWS_01
Business Function Set 'TELCO':
Business Function /SAPCE/TEL_LOC_CEE
o Switch /SAPCE/FICA_LOC_CEE_SFWS_02
Switch Package /SAPCE/FK_LOC_CEE_SFWS_02
Business Function /SAPCE/TEL_LOC_CEE_HIDDEN
o Switch /SAPCE/ISU_LOC_CEE_SFWS_01
Switch Package /SAPCE/IU_LOC_CEE_SFWS_01
Business Function RM_CA
o
Switch /SAPCE/FICA_LOC_CEE_SFWS_01
Switch Package /SAPCE/FK_LOC_CEE_SFWS_01
Business Process related information
No influence on business processes and custom code.
Required and Recommended Action(s)
Execute related pre-check (see the SAP Note 2314696) on SAP Business Suite start-release.
2.1.44 Cross Topics
2.1.44.1 Output Management
2.1.44.1.1 Description
The new output management is going to be the successor of all other output management
frameworks (SD Output Control, FI Correspondence, FI-CA Print Workbench, CRM Post-Processing).
Simplification List for SAP S/4HANA 1610
375
However, all other frameworks are still available and can be used. It is not mandatory to use the new
output management. Business applications that have already adopted the new output
management use it by default. Nonetheless, customers can always revert back to the other
supported framework. How this reversion is realized depends on the business application (for
example via SAP Note or by implementation of an enhancement point). It is also possible to reenable the new output management again at a later point in time. Hence, the new output
management for SAP S/4HANA coexists with other frameworks. Customers can decide on business
application level which framework supports their output scenarios best. The output management for
SAP S/4HANA comprises all functionalities and processes that are related to the output of
documents. This includes the integration of output management functions into the business
applications, the reuse component output control, as well as the SAP NetWeaver technologies and
the technical infrastructure. Output control is the central element of output management. It serves
as an interface between business applications and SAP NetWeaver technologies. Note that although
output control is by definition one of several parts of output management, the term output
management is often used to describe the functionality of output control. When you use applications
that have adopted the new output control, please consider the following aspects and consult the
following SAP Notes:
Technical setup - SAP Note 2292571
Configuration - SAP Note 2292539
New form templates used by output control:
o Form templates with fragments - SAP Note 2292646
o Form master templates - SAP Note 2292681
o Customized forms - SAP Note 2294198
Conversion (see below)
Features and functions
The following table provides an overview of existing features and functions of the new output
control:
Supported channels
Supported UI technologies
Supported form technologies
Master form templates
P i te Usi g the spool
E ail Allo s fle i le o figu atio of se de a d e ipie t s as
well as use of email templates
XML I teg atio ith the Ariba Network
IDoc (limited support only; for more information, see below)
Fiori
SAP GUI and SAP GUI for HTML
PDF-based print forms with fragments (default)
PDF-based print forms
Smart Forms
SAPscript
A master form template defines a universally valid layout and features
reuseable parts of a form, such as header, footer, or logo (only available for
PDF-based print forms with fragments). This allows you to maintain general
Simplification List for SAP S/4HANA 1610
376
content and application-specific content separately. If you make changes in
the general content (master form), the application forms will be updated
accordingly.
Determination of master form
Master form templates can be determined based on preconfigured
templates
parameters, such as company, sender country, or channel. This makes it
easy to define separate logos or footer texts per company.
Output parameter determination All output parameters can be automatically determined via a configuration
via BRFplus
activity based on BRFplus. The benefits are:
Dispatch time
Application log
Used frameworks/services
You can send multiple messages to multiple recipients using
multiple channels at the same time.
You can configure anything without the need for ABAP exits.
You can base each determination step on application-specific fields
that can be extended.
You can use predelivered content/determination rules to simply
run output control out of the box.
Extensibility via CDS is supported.
Immediately or scheduled via batch job (application-specific)
The system creates one application log per output request instance. In
addition, you can filter messages by output request item. You can display
the log in the business application or via transaction SLG1 once an output
item has been processed.
BOPF
BRFplus
KPro
Gateway Services
Fiori
Web Dynpro
SAP GUI
IDoc
Currently, IDocs are not fully supported by the new output management. Their use is restricted to
business applications that previously used NAST. Furthermore, the following limitations apply:
Only output types which can be mapped 1:1 to the NAST-KSCHL can use IDoc.
Only business partner-based communication is supported, but no communication to logical
systems (no ALE support).
Manually created output items cannot be used for IDoc, as the partner role cannot be set for
such items.
Please check your business requirements against these limitations. Refer to the simplification item
list of the business applications to check which business scenarios support the use of IDoc.
Conversion
Simplification List for SAP S/4HANA 1610
377
In the ECC Business Suite, different output frameworks are used in different applications (SD Output
Control, FI Correspondence, FI-CA Print Workbench, CRM Post-Processing Framework). Considering
the conversion of an existing system to SAP S/4HANA, it becomes evident that there cannot be one
generic approach to cover the conversion of all other OM frameworks. Looking further into the most
prominent existing OM framework SD Output control (NAST), it becomes clear that:
100% feature parity is not a given (and, most likely, is not wanted).
Migration of data cannot be performed because even the NAST is highly generic.
Therefore, the recommendation is not to carry out a conversion, but to establish a coexistence of
old and new output management.
This means:
For existing customers who are using the old output management:
o Data from the old OM is kept.
o Customizing for the old OM is kept.
o Customers need to customize the new OM.
o Documents that were processed in the old OM will still be processed using the old
OM.
o New documents will only use the new OM (if the corresponding application has
already adopted this framework).
For new customers
o Customers need to customize the new OM.
o All documents will be using the new OM (if the corresponding application has already
adopted this framework).
2.1.44.2 Analytics - SAP S/4HANA and SAP Business Warehouse Content
2.1.44.2.1 Description
The BI-content software components BI_CONT and BI_CONT_XT are not supported in all the editions
and releases of SAP S/4HANA (cloud and on premise), even though they are technically installable.
2.1.44.2.2 Business Process related information
The BI-content software components BI_CONT and BI_CONT_XT are not supported in all the editions
and releases of SAP S/4HANA (cloud and on premise), even though they are technically installable.
2.1.44.2.3 Required and Recommended Action(s)
Knowledge Transfer to key- and end-user. Extractors for S/4HANA are in general available but please
check the central restriction note 2214213 and the individual notes linked there for extractors that
might not be released.
Simplification List for SAP S/4HANA 1610
378
For new installations we highly recommend to not install the software components BI_CONT and
BI_CONT_XT at all.
2.1.44.2.1 Related SAP Notes
SAP S/4HANA 1511 restriction note
BI Content Release strategy
SAP Note 2214213
SAP Note 153967
2.1.44.3 Enterprise Search
2.1.44.3.1 Description
ESH_SEARCH was the generic search UI of Enterprise Search in previous releases. Its successor in SAP
S/4HANA is the integrated search functionality in the Fiori Launchpad.
2.1.44.3.2 Business Process related information
If a customer migrates from an older release to SAP S/4HANA and if he created his own search
models or enhanced existing ones before, he needs to migrate his enhancements to the maybe
changed standard search models of SAP S/4HANA.
Note that the navigation targets are not maintained any longer in the Enterprise Search model, but in
the Fiori Launchpad Designer.
Transaction not available in SAP S/4HANA
ESH_SEARCH
2.1.44.3.3 Required and Recommended Action(s)
The search functionality is always available in the header area of the Fiori Launchpad. So you don't
need a transaction code to start it. The users may need a general introduction into the Fiori
Launchpad. Only if the customer created his own search models or enhanced existing ones before, he
needs to migrate his enhancements to the maybe changed standard search models of SAP S/4HANA.
Note that the navigation targets are not maintained any longer in the Enterprise Search model, but in
the Fiori Launchpad Designer.
2.1.44.3.4 Related SAP Notes
Custom Code related information
SAP Note: 2227007
2.1.44.4 Internet Pricing and Configurator (SAP IPC)
2.1.44.4.1 Description
The Internet Pricing and Configurator (SAP IPC) is not released within SAP S/4HANA. For scenarios
and business processes where the Internet Pricing and Configurator is currently used alternative
functionality like ABAP-based configuration (LO-VC) can be used in SAP S/4HANA.
Simplification List for SAP S/4HANA 1610
379
2.1.44.4.2 Business Process related information
In the Business Suite, The Internet Pricing and Configurator (aka SAP AP Configuration Engine) is
usually used for the following use cases:
Configuration Processes in SD/MM (incl. Pricing) as alternative to LO-VC
Creation of Material Variants
For the Vehicle Management System (VMS), SAP IPC could be used for vehicle configuration
as alternative to the variant configuration (LO-VC). For each vehicle model defined as
configurable material, the configuration engine could be switched from variant configuration
to SAP IPC and vice versa
Configuration Simulation in combination with SAP CRM
Web Channel (aka Internet Sales) ERP Edition - this application is not released with S/4HANA
For scenarios and business processes where the Internet Pricing and Configurator is currently used
alternative functionality like ABAP-based configuration (LO-VC) can be used in SAP S/4HANA.
2.1.44.4.3 Required and Recommended Action(s)
Implement Business Scenarios and Business Processes based on the functionality available within SAP
S/4HANA like ABAP-based configuration (LO-VC). Revert entries in CUCFGSW if needed.
2.1.44.4.4 How to Determine Relevancy
There is no unambiguous single indicator whether IPC is productively used. However, there are a
number of hints:
-
-
If table IBIB shows any entries in field KBID, configurations created with IPC have been
stored. This is an indicator at least for usage in the past.
Table TCUUISCEN contains mandatory information for the configuration UI. If this table
contains records, at least the installation has been set up. It is quite likely that IPC is
actively used.
Table CUCFGSW contains the "IPC Switch". If this table contains records, master data has
been set up to use IPC instead of VC. This is not only an indicator for IPC usage, moreover
entries must be reverted prior to conversion to S/4HANA.
2.1.44.4.5 Related SAP Notes
Custom Code related information
SAP Note: 2238670
2.1.44.5 Job Scheduling
2.1.44.5.1 Description
SAP S/4HANA contains a new component which automatically schedules certain technical
background jobs. Deleting or modifying such jobs manually (via transaction SM37) will not have a
lasting effect since the automation mechanism will re-schedule these jobs with predefined attributes.
Simplification List for SAP S/4HANA 1610
380
Job Definitions can be customized or deactivated via transaction SJOBREPO. Scheduling (and
monitoring) "Standard Jobs" (e.g. SAP_REORG_SPOOL, SAP_REORG_ABAPDUMPS, SAP_REORG_JOBS
etc.) was a manual action in SAP ERP. Choosing Standard Jobs in transaction SM36 displayed a table
of standard job templates which the customer could choose to schedule. In SAP S/4HANA, this
manual action has been replaced by an automatic mechanism, the Technical Job Repository. SAP
S/4HANA Technical Job Repository takes care of scheduling (and de-scheduling) necessary standard
jobs (as defined and delivered by SAP) automatically, without any user intervention. Nevertheless, in
case of conflicts, it is possible to do customizations to job definitions, for example modify the
execution period (or start time) of a job or disable automatic job scheduling of a job entirely. Two
important job definitions which should be reviewed by customers after upgrade to SAP S/4HANA are
described here:
1) SAP_REORG_JOBS:
This job definition schedules report RSBTCDEL2 daily in client 000 with variant SAP&001. This
report+variant performs deletion of background jobs older than 14 days. If customer
desires different deletion criteria (for example delete all jobs older than 7 days), disable SAPdelivered job definition SAP_REORG_JOBS via transaction SJOBREPO (must be logged on in client 000
because this job definition is only relevant for client 000) and schedule a custom job with custom
variant.
2) SAP_REORG_SPOOL:
This job definition schedules report RSPO0041 daily in client 000 with variant SAP&001. This report +
variant performs deletion of spool requests that have reached their deletion date in all clients. If
customer desires different spool deletion criteria, disable SAP-delivered job definition
SAP_REORG_SPOOL via transaction SJOBREPO (must be logged on in client 000) and schedule a
custom job with custom variant.
Note: It is possible for customers to create customer-owned job definitions via transaction SE80.
For more information and a guide to SAP S/4HANA Technical Job Repository, see SAP Note 2190119.
2.1.44.5.2 Business Process related information
No influence on business processes expected.
2.1.44.5.3 Required and Recommended Action(s)
None.
2.1.44.5.4 Related SAP Notes
SAP Note
SAP Note: 2190119
Simplification List for SAP S/4HANA 1610
381
2.1.44.6 Legacy System Migration Workbench (LSMW)
2.1.44.6.1 Description
The LSMW (Legacy System Migration Workbench) function is still available within SAP S/4HANA, (onpremise edition) but not considered as the migration tool. LSMW might propose incorrect migration
interfaces that cannot be used in SAP S/4HANA anymore. The Legacy System Migration Workbench
(LSMW) is an SAP NetWeaver tool for data migration that was first introduced with R/2 to R/3
migrations. It uses standard interfaces like BAPIs, IDocs, Direct Input and Batch Input programs and
recordings. Due to this nature, the use of LSMW is restricted for migrations to SAP S/4HANA. The
Legacy System Migration Workbench (LSMW) can only be considered as a migration tool for SAP
S/4HANA using workarounds and careful testing for each and every object. The use of LSMW for data
load to SAP S/4HANA is not recommended and at the customer's own risk.
There are two workarounds already available. There is no commitment from SAP to provide such
workarounds for all objects that were available before with the SAP Business Suite. Please use the
links below to get more information about the workarounds:
1. Business Partner
http://scn.sap.com/community/s4hana/blog/2016/03/10/uploading-business-partner-datausing-lsmw
2. Asset Management data:
http://service.sap.com/sap/support/notes/2208321
Also expect restrictions around transaction recording (as this is not possible with the new SAP Fiori
screens) and changed interfaces (for instance the Business Partner CVI interface instead of customer
and vendor IDocs). Standard Batch Input programs may also no longer work as transactions may have
changed functionality or may be completely removed within some areas. For example, due to
security reasons batch import has been limited for RCCLBI02 program. Also, transactions for
customer master data (FD*/XD*) and vendor master data (FK*/XK*) cannot be used anymore due to
the change to the Business Partner data model in SAP S/4HANA. Instead, SAP S/4HANA data
migration content called SAP Rapid Data Migration based on SAP Data Services software is offered to
migrate data into SAP S/4HANA (on premise). You can find more information under the link below:
http://service.sap.com/public/rds-dm2s4op.
This content has been specifically built for the new SAP S/4HANA target system, its interfaces and
data structures. The content is free of charge and can be downloaded under the link above. There
are two ways to leverage the content:
1. Base: Data Integrator
SAP S/4HANA customers have access to a basic Data Integrator license key that comes with
the underlying SAP HANA license (HANA REAB or HANA Enterprise). This key code applied to
SAP Data Services provides full ETL functionalities (Extract, Transform, Load). Thus, it replaces
a mapping and load tool like LSMW with the Rapid Data Migration content. With this basic
data load functionality of SAP Data Services and together with the Rapid Data Migration
Simplification List for SAP S/4HANA 1610
382
content, legacy data can be loaded into SAP S/4HANA (on premise) including data validation
but without further Data Quality (de-duplication, data cleansing) and reporting capabilities.
For this use case with the aforementioned functionality, SAP Data Services is free of charge
and there is no additional cost.
2. Full: Data Services
Using the full SAP Data Services license (separately licensed and not part of SAP S/4HANA)
unleashes all Data Quality features like data cleansing and de-duplication for mitigating risk
during the data migration process of a new SAP S/4HANA implementation.
2.1.44.6.2 How to Determine Relevancy
This simplification item is relevant if you plan to continue to use Legacy System Migration
Workbench to migrate Data into SAP S/4HANA after System Conversion
2.1.44.7 FIORI Application for SAP Business Suite powered by SAP HANA
2.1.44.7.1 Description
SAP S/4HANA, on-premise edition comes with a corresponding UI product for frontend server
installation. The new SAP S/4HANA, on-premise edition UI product is not the successor of any
Business Suite product and delivers a set of applications which is from a technical and scope
perspective independent from any previous Business Suite UI product. This implies the following
conversion behaviour:
1. Different product scope
There is no automatism that apps from Business Suite will be offered in the same way for SAP
S/4HANA, on-premise edition as well. Apps might be replaced, enhanced, changed, implemented
using different technology or not offered in the SAP S/4HANA context. The available app scope can
be checked in the SAP Fiori apps reference library (see detailed description below).
2. No automated conversion
The central frontend server must support multiple back-end systems. Therefore it is not possible to
convert the existing settings from Business Suite applications during the installation as this would
break the existing apps and Business Suite installations on the same frontend server. The new
S/4HANA UI product can be co-deployed and runs only against the SAP S/4HANA, on-premise edition
back-end. Also the other way round, existing Business Suite UI products will not run against a SAP
S/4HANA, on-premise edition back-end. Configuration details for every app can be found in the SAP
Fiori apps reference library.
Simplification List for SAP S/4HANA 1610
383
2.1.44.7.1 Required and Recommended Action(s)
Use the SAP Fiori apps reference library to check which applications are available for SAP S/4HANA,
on-premise and for configuration details.
Option 1: Filter those apps, which are available in S/4HANA on-premise edition
In SAP Fiori apps reference library, use the Filter Required Back-E d P odu t™ a d sele t ˜“AP
S/4HANA, on-p e ise editio ™ to displa a list of all Fio i apps a aila le. This filte a e o i ed
with other filters like Line of Business or Role.
Option 2: Check availability in SAP S/4HANA on-premise edition for a single app
Select the Fiori app in the SAP Fiori apps reference library. A drop-down list box will appear in the
header area of the app details page, if the app is available in multiple products. In case the selected
app is not available for S/4HANA on-premise edition check, whether a successor app exist. You will
can directly navigate to the successor app from the bottom of the PRODUCT FEATURES tab.
Example: Fio i app M “pe d™ fo E‘P has a su esso M “pe d™, hi h is a aila le fo E‘P AddO “AP FIO‘I fo “AP “FIN
™ as ell as “/ HANA o -p e ise
™
Option 3: Check availability in in S/4HANA on-premise edition for multiple apps
Filter and select all apps ou a t to he k. A ti ate Agg egate™ at the otto of the app list to
display a consolidated view about all selected apps. Select SAP S/4HANA, on-p e ise editio ™ i the
drop-down on top of the list. All apps which are not available for SAP S/4HANA, on-premise edition
will be highlighted as not available at the bottom of the list of selected apps.
Check in the details of the individual apps whether a successor app is available (see option 2 above).
2.1.44.7.1 Related SAP Notes
Release Information: Changes in Fiori Content in SAP S/4HANA Finance SAP Note: 2242596
1605 (sFIN 3.0)
Changes in Fiori Application for SAP SAP S/4 HANA in Sales and Distribution SAP Note: 2290488
2.1.44.8 Social Intelligence
Social Intelligence data harvesting features were provided in ERP EhP7 and EhP8. Customer could
harvest data from social sources like Twitter, Facebook, etc. After text analysis using HANA, the
sentiment data used to be stored in underlying BS_FND tables. Consent Management and Archiving
features were also provided. These features will not be available in S/4 from the initial release. As of
now, there is no alternative for this solution in S/4 HANA. There is no successor available yet.
Simplification List for SAP S/4HANA 1610
384
2.1.44.9 Custom Fields
2.1.44.9.1 Description
You have done a system conversion to SAP S/4HANA. Now, the following item of the SAP S/4HANA
transition worklist is applicable if you have extension fields and want to use them in:
SAP Fiori apps
CDS-based analytical reports
Adobe-based print forms
Email templates
OData services
With SAP S/4HANA, custom fields can be managed with the SAP Fiori app Custom Fields and Logic.
This app, together with other SAP Fiori apps, can be used to add custom fields to OData services, CDS
views, or SAP Fiori apps, for example.
2.1.44.9.2 Business Process-Related Information
In the SAP GUI transaction SCFD_EUI, existing custom fields can be enabled for use in the app Custom
Fields and Logic. In some cases, existing fields need to be prepared in advance.
For more information, see <link to online documentation>.
2.1.44.9.3 Required and Recommended Actions
Use the transaction SCFD_EUI to enable your existing custom fields for use in the app Custom
Fields and Logic, and to see preparation steps, if necessary.
2.1.44.10 Ariba Network Integration
2.1.44.10.1 Description
This SAP Note is relevant if you use the SAP ERP add-on of Ariba Network Integration 1.0 for SAP
Business Suite. In SAP S/4HANA, Ariba Network integration functionality is not provided as an add-on
but as part of the SAP S/4HANA core product. As of now, not all integration processes and messages
that are provided with Ariba Network Integration 1.0 for SAP Business Suite are available in SAP
S/4HANA. After the conversion from SAP ERP to SAP S/4HANA, the processes and cXML messages
listed below are not supported by SAP S/4HANA.
2.1.44.10.2Business Process related information
Note the restrictions for SAP S/4HANA, on-premise edition 1511 listed below.
The following processes are not supported:
Simplification List for SAP S/4HANA 1610
385
Processing of CC invoices (invoices transfered from SAP S/4HANA to Ariba Network)
Service procurement/invoicing process
Payment process
Discount management process
Processing of scheduling agreement releases
Consignment process
Subcontracting process
Processing of forecast data
Multi-tier purchase order processing
Purchase order return items processing
Integration processes for suppliers
The following cXML message types are not available:
ReceiptRequest
CopyRequest.InvoiceDetailRequest
ServiceEntryRequest
PaymentRemittanceRequest
PaymentRemittanceStatusUpdateRequest
PaymentProposalRequest
CopyRequest.PaymentProposalRequest
ProductActivityMessage
ComponentConsumptionRequest
ProductReplenishmentMessage
QuoteRequest
QuoteMessage
Note the restrictions for SAP S/4HANA 1610 listed below.
The following processes are not supported:
Processing of CC invoices (FI invoices transfered from SAP S/4HANA to Ariba Network)
Processing of scheduling agreement releases
Consignment process
Subcontracting process
Processing of forecast data
Multi-tier purchase order processing
Purchase order return items processing
Integration processes for suppliers
The following cXML message types are not available:
ProductActivityMessage
ComponentConsumptionRequest
ProductReplenishmentMessage
Simplification List for SAP S/4HANA 1610
386
2.1.44.10.3 Required and Recommended Action
Implement the master conversion pre-check SAP Note "2182725 - S4TC Delivery of the SAP
S/4HANA System Conversion Checks" and follow the instructions in this note.
For Ariba Network Integration, also implement the pre-check SAP Note "2237932 - S4TC
Ariba BS Add-On Master Check for SAP S/4HANA System Conversion Checks". This note is
also listed within the master note.
If pre-checks fail, see the following SAP Note: "2246865 - S/4 Transition: Activities after failed
PreChecks".
Access SAP Note: "2341836 - Ariba Network Integration in SAP S/4HANA on-premise
edition", download the following documents, and follow the steps described.
o Before the conversion: S4H_CONV_INTEGRATION_ARIBA_NETWORK_PREPC.PDF
o After the conversion: S4H_CONV_INTEGRATION_ARIBA_NETWORK_POSTC.PDF
2.1.44.11 SAP HANA Live Reporting6
2.1.44.11.1Description
SAP HANA Live provides reporting capabilities for Business Suite and Suite on HANA customers. A
strategic decision was taken to switch the technology from Calculation Views to CDS Views with SAP
S/4HANA. Reporting scenarios built with the SAP HANA Live content in Business Suite, Suite on
HANA, or Simple Finance installations have to be rebuilt manually with CDS Views in SAP S/4HANA.
2.1.44.11.2Business Process related information
It should be possible to rebuild all existing reporting scenarios with CDS Views. Limitations might
exist with respect to consumption.
2.1.44.11.3Required and Recommended Action(s)
If HANA Live views are used, time and resources should be planned for migration to CDS Views or for
implementation of the additional RDS package (if that is available).
2.1.44.11.4Related SAP Notes
Custom Code related If the customer copied calculation views delivered by SAP or created
information
user-defined calculation views on top of SAP delivered views, they need
to be redone with CDS Views
2.1.44.12 Side Panel functionality in SAP S/4HANA
2.1.44.12.1Description
SAP S/4HANA (on-premise) comes with a new UI product. The S/4HANA (on-premise) UI product is
not the successor of any Business Suite product and delivers a set of applications which is from a
technical and scope perspective independent from any previous Business Suite UI product. The SAP
Business Client Side Panel functionality is available in S/4HANA (on-premise). Some of the Business
6
Relevant for SAP Simple Finance, on-premise edition 1503 customer
Simplification List for SAP S/4HANA 1610
387
Suite Side Panel CHIPs (Collaborative Human Interface Part) are no longer available in
S/4HANA and the delivered CHIP catalog is adjusted accordingly.
A CHIP (Collaborative Human Interface Part) is an encapsulated piece of software used to provide
functions in collaboration with other CHIPs in a Web Dynpro ABAP Page Builder page or side panel.
All available CHIPs are registered in a library (CHIP catalog). From a technical point of view, CHIPs are
Web Dynpro ABAP components that implement a specific Web Dynpro component interface.
More information is available at:
http://help.sap.com/erp2005_ehp_07/helpdata/en/f2/f8478f40ca420991a72eed8f222c8d/content.h
tm?current_toc=/en/58/327666e82b47fd83db69eddce954bd/plain.htm
2.1.44.12.2Business Process-Related Information
The new program paradigm in S/4HANA and the consumption of functionality via SAP Fiori results in
an adjustment of the delivered CHIP catalog for the SAP Business Client Side Panel functionality.
The following SAP Business Client Side Panel CHIPs are no longer available:
CHIP Name
BSSP_LPD_FI_AP
BSSP_LPD_FI_AR
BSSP_LPD_FI_AA
BSSP_LPD_CO_OM_CCA
BSSP_LPD_FI_GL
BSSP_LPD_CO_OM_OPA
BSSP_LPD_PM_OM_OPA
BSSP_LPD_CO_PC
BSSP_LPD_FI_GL_PRCTR
BSSP_FI_AA_POSTED_DEPREC
BSSP_CO_OM_CC_ACT_PLAN_AGGR
BSSP_FI_AR_TOTALS
BSSP_FI_AR_DUE_ANALYSIS
BSSP_FI_AR_DUE_FORECAST
BSSP_FI_AR_OVERDUE
BSSP_CO_OM_IO_ACT_PLAN_AGGR
BSSP_CO_PC_MAT_ACT_PLAN_AGGR
BSSP_GR_IR_GOODS_RECEIPT
BSSP_GR_IR_INVOICE_RECEIPT
BSSP_GR_IR_OPEN_ITEM
BSSP_FI_AP_TOTALS
BSSP_FI_AP_DUE_ANALYSIS
BSSP_FI_AP_DUE_FORECAST
BSSP_FI_AP_OVERDUE
BSSP_FI_AA_POSTED_DEPREC_C
CHIP
Accounts Payable Reporting (Links)
Accounts Receivable Reporting (Links)
Asset Accounting Reporting (Links)
Cost Center Reporting (Links)
General Ledger Reporting (Links)
Internal Order Reporting (Links)
Maintenance / Service Order Reporting (Links)
Product Cost Reporting (Links)
Profit Center Reporting (Links)
Asset Accounting: Posted Depreciation (Reports (Display as Form / List))
Cost Center: Cumulative Actual/Planned Costs (Reports (Display as Form / List))
Cost Center Balance: Totals (Reports (Display as Form / List))
Customer Due Date Analysis (Reports (Display as Form / List))
Customer Due Date Forecast (Reports (Display as Form / List))
Customer Overdue Analysis (Reports (Display as Form / List))
Internal Order: Cumulative Actual/Planned Costs (Reports (Display as Form / List))
Material: Aggregated Actual / Planned Costs (Reports (Display as Form / List))
Purchase Order History: Goods Receipt (Reports (Display as Form / List))
Purchase Order History: Invoice Receipt(Reports (Display as Form / List))
Purchase Order: Open Items (Reports (Display as Form / List))
Vendor Balance Totals (Reports (Display as Form / List))
Vendor Due Date Analysis (Reports (Display as Form / List))
Vendor Due Date Forecast (Reports (Display as Form / List))
Vendor Overdue Analysis (Reports (Display as Form / List))
Asset Accounting: Posted Depreciation (Reports (Display as Chart))
Cost Center: Breakdown Actual/Planned Costs by Period (Reports (Display as
BSSP_CO_OM_CC_PERIOD_BD_C
Chart))
BSSP_CO_OM_CC_ACT_PLAN_AGGR_C Cost Center: Cumulative Actual/Planned Costs (Reports (Display as Chart))
BSSP_FI_AR_PERIOD_C
Customer Balance: Period Drilldown (Reports (Display as Chart))
BSSP_FI_AR_TOTALS_C
Customer Balance: Totals (Reports (Display as Chart))
BSSP_FI_AR_DUE_ANALYSIS_C
Customer Due Date Analysis (Reports (Display as Chart))
BSSP_FI_AR_DUE_FORECAST_C
Customer Due Date Forecast (Reports (Display as Chart))
Simplification List for SAP S/4HANA 1610
388
BSSP_FI_AR_OVERDUE_C
Customer Overdue Analysis (Reports (Display as Chart))
BSSP_FI_GL_ACC_BALANCE_C
G/L Account Balance (Reports (Display as Chart))
BSSP_CO_OM_IO_PERIOD_BD_C
Internal Order: Actual/Planned Costs by Period (Reports (Display as Chart))
BSSP_CO_OM_IO_ACT_PLAN_AGGR_C Internal Order: Cumulative Actual/Planned Costs (Reports (Display as Chart))
BSSP_CO_PC_MAT_ACT_PLAN_AGGR_C Material: Aggregated Actual / Planned Costs (Reports (Display as Chart))
BSSP_CO_PC_MAT_PERIOD_BD_C
Material: Breakdown Actual/Planned Costs by Period (Reports (Display as Chart))
BSSP_FI_AP_PERIOD_C
Vendor Balance: Period Drilldown (Reports (Display as Chart))
BSSP_FI_AP_TOTALS_C
Vendor Balance Totals (Reports (Display as Chart))
BSSP_FI_AP_DUE_ANALYSIS_C
Vendor Due Date Analysis (Reports (Display as Chart))
BSSP_FI_AP_DUE_FORECAST_C
Vendor Due Date Forecast (Reports (Display as Chart))
BSSP_FI_AP_OVERDUE_C
Vendor Overdue Analysis (Reports (Display as Chart))
BSSP_FI_AA_POSTED_DEPREC_C2
Asset Accounting: Posted Depreciation (Reports (Display as HTML5 Chart))
Cost Center: Breakdown Actual/Planned Costs by Period (Reports (Display as
BSSP_CO_OM_CC_PERIOD_BD_C2
HTML5 Chart))
BSSP_CO_OM_CC_ACT_PLAN_AGGR_C2 Cost Center: Cumulative Actual/Planned Costs (Reports (Display as HTML5 Chart))
BSSP_FI_AR_PERIOD_C2
Customer Balance: Period Drilldown (Reports (Display as HTML5 Chart))
BSSP_FI_AR_TOTALS_C2
Customer Balance: Totals (Reports (Display as HTML5 Chart))
BSSP_FI_AR_DUE_ANALYSIS_C2
Customer Due Date Analysis (Reports (Display as HTML5 Chart))
BSSP_FI_AR_DUE_FORECAST_C2
Customer Due Date Forecast (Reports (Display as HTML5 Chart))
BSSP_FI_AR_OVERDUE_C2
Customer Overdue Analysis (Reports (Display as HTML5 Chart))
BSSP_FI_GL_ACC_BALANCE_C2
G/L Account Balance (Reports (Display as HTML5 Chart))
BSSP_CO_OM_IO_PERIOD_BD_C2
Internal Order: Actual/Planned Costs by Period (Reports (Display as HTML5 Chart))
Internal Order: Cumulative Actual/Planned Costs (Reports (Display as HTML5
BSSP_CO_OM_IO_ACT_PLAN_AGGR_C2
Chart))
BSSP_CO_PC_MAT_ACT_PLANAGGR_C2 Material: Aggregated Actual / Planned Costs (Reports (Display as HTML5 Chart))
Material: Breakdown Actual/Planned Costs by Period (Reports (Display as HTML5
BSSP_CO_PC_MAT_PERIOD_BD_C2
Chart))
BSSP_FI_AP_PERIOD_C2
Vendor Balance: Period Drilldown (Reports (Display as HTML5 Chart))
BSSP_FI_AP_TOTALS_C2
Vendor Balance Totals (Reports (Display as HTML5 Chart))
BSSP_FI_AP_DUE_ANALYSIS_C2
Vendor Due Date Analysis (Reports (Display as HTML5 Chart))
BSSP_FI_AP_DUE_FORECAST_C2
Vendor Due Date Forecast (Reports (Display as HTML5 Chart))
BSSP_FI_AP_OVERDUE_C2
Vendor Overdue Analysis (Reports (Display as HTML5 Chart))
Simplification List for SAP S/4HANA 1610
389
2.2
The Simplification List Items related to SAP Add-Ons
2.2.1 SAP Portfolio and Project Management 1.0 for SAP S/4HANA
The following Simplification Items are related to the Add-On SAP Portfolio and Project Management
1.0 for SAP S/4HANA and are relevant for customers converting from the following PPM
functionality:
SAP CPROJECT SUITE 4.00
SAP CPROJECT SUITE 4.50
SAP PORTF AND PROJ MGMT 5.0
SAP RPM 4.5
SAP PORTF AND PROJ MGMT 6.0
SAP PORTF AND PROJ MGMT 6.1
These items are not relevant for customers who do not have one of the mentioned PPM versions
installed on their SAP ERP 6.0 start release.
2.2.1.1
Web Dynpro Applications for Resource Maintenance in SAP PPM
2.2.1.1.1
Description
The Web Dynpro application 'Create Resource' is no longer available. Furthermore, it is no longer
possible to edit standard fields of a business partner with the Web Dynpro application 'Edit
Resource'. Use the standard functions for creating and editing business partner data.
SAP Note 2321885 provides a pre-conversion check for this feature.
2.2.1.1.2
Business Process-Related Information
No effects on business processes are expected.
2.2.1.1.3
Required and Recommended Action(s)
The functionality and integration functionality for Business Partner is still available and can be used.
No further actions expected.
2.2.1.1.4
Related SAP Notes
Conversion pre-checks
2.2.1.2
SAP Note 2321885
Workforce Deployment (WFD) integration in SAP Portfolio and Project Mana
Description
Workforce Deployment is no longer available for Resource Management in Project Management of
SAP Portfolio and Project Management for SAP S/4HANA.
Simplification List for SAP S/4HANA 1610
390
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions expected.
2.2.1.3
Integration to SAP cFolders in SAP Portfolio and Project Management for
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the SAP cFolders Integration
functionality is no longer supported.
Business Process-Related Information
It is no longer possible to exchange data between SAP Portfolio and Project Management for SAP
S/4HANA and SAP cFolders.
Required and Recommended Action(s)
SAP recommends to evaluate SAP Document Center as a substitute for selected collaboration
scenarios.
2.2.1.4
KM Documents in SAP Portfolio and Project Management for SAP S/4HANA
In SAP Portfolio and Project Management for SAP S/4HANA, the usage of Knowledge Management
(KM) for Document Management is no longer available.
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
In order to prevent the loss of the linkage between documents stored in KM and SAP Portfolio and
Project Management for SAP S/4HANA during the system conversion, it is required to switch from
the KM based document management to a KPRO based solution. For this, migrate your KM
documents to KPRO documents using the report /RPM/MIGRATE_KM_DOCS. For this, you can use
the report /RPM/MIGRATE_KM_DOCS. You can find more information in the Upgrade Master Guide
of the current start release.
Simplification List for SAP S/4HANA 1610
391
2.2.1.5
SRM Integration in SAP Portfolio and Project Management for SAP S/4HANA
Description
The SRM Integration for external service procurement is not available in SAP Portfolio and Project
Management for SAP S/4HANA.
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process related information
It is not possible anymore to order external materials and resources directly from Project
Management through SRM.
Required and Recommended Action(s)
The SRM Integration related data cannot be migrated to SAP Portfolio and Project Management for
SAP S/4HANA, therefore it is required to clean up the data before the system conversion in order to
prevent any data loss. Archive the corresponding projects or delete not needed SRM Integration
related data before you continue the system conversion.
2.2.1.6
cFolders not available anymore in SAP Portfolio and Project Management f
Description
With SAP Portfolio and Project Management for SAP S/4HANA, the cFolders component is not
available anymore. SAP recommends to evaluate SAP Document Center as a substitute for selected
collaboration scenarios. SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process related information
All the features of cFolders application and all the integration between cFolders and other
applications, e.g. SAP PLM, SAP SRM etc., are not available anymore.
Required and Recommended Action(s)
Because cFolders is not available anymore with SAP Portfolio and Project Management for SAP
S/4HANA, customers need to archive existing cFolders data before the system conversion by
following the steps below:
1. This step is mandatory to continue the conversion. Go to the collaboration overview page,
select the collaborations you would like to archive, and click 'Archive' button in the toolbar
above the list. Then the system will set a deletion indicator and remove the collaboration
from the collaboration overview.
Simplification List for SAP S/4HANA 1610
392
2. This step is not mandatory for the conversion, but it's highly recommended to keep the
integrity of your data. Use SAP Data Archiving and archive object 'CFX_ARCH' to archive the
collaboration data.
For the collaboration with partners, customers could consider to use other products like SAP
Document Center.
How to Determine Relevancy
This Simplification Item is relevant if:
2.2.1.7
cFolders is used if entries exist in Table CFX_COL, and column TO_BE_ARCHIVED is not set to
'X' (check with SE16)
Global Settings in SAP Portfolio and Project Management for SAP S/4HANA
Description
The following Customizing settings under SAP Portfolio and Project Management -> Project
Management -> Basic Settings -> Check Global Settings have been changed in SAP Portfolio and
Project Management for SAP S/4HANA.
Area
Text
Name
Text
2
Master
Switches
5
Integration with Other
Components (see SAP Note
1391444)
2
Master
Switches
7
Integration with PS and FI/CO
(see SAP Note 1427365)
2
Master
Switches
8
2
Master
Switches
13
2
Master
Switches
14
2
Master
Switches
15
2
Master
Switches
16
2
Master
Switches
17
2
Master
Switches
18
2
Master
Switches
21
Enhanced Capital and Resource
Mgmt Switch (see SAP Note
1457426)
Flag is Obsolete (SAP Note
1759150)
Flag is Obsolete - Change
Documents for Financial and
Capacity Planning
Milestone Filter for
Tasks ('X'=On, ' '=Off)
Accumulate the Number of
Objects in the Dashboard
('X'=On, ' '=Off)
Flag is obsolete (SAP Note
1780409)
Flag is Obsolete - Automatic
Refresh of Project Dashboards
('X'=On, ' '=Off)
Integration with PLM
E gi ee i g ‘e o d X = ON, ''
= OFF)
Delivered
Default
Settings
Value
X
Availability in S/4HANA PPM
Switch will be removed. Feature will be activated by
default. In most cases, using the features require further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch is obsolete and will be deleted.
Switch is obsolete and will be deleted.
X
X
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch is obsolete and will be deleted.
Switch is obsolete and will be deleted.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Simplification List for SAP S/4HANA 1610
393
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
2
Master
Switches
22
Activate Operative Object Links
( 'X' = ON, '' = OFF)
6
User
Interface
Settings
21
DEPRECATED: Display
Additional Information on Gantt
Chart (' ': No, 'X': Yes)
Switch is obsolete and will be deleted.
23
Flag is obsolete (SAP Note
1756616)
Switch is obsolete and will be deleted.
24
Flag is obsolete (SAP Note
1769591)
Switch is obsolete and will be deleted.
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
7
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
User
Interface
Settings
General
Default
Values
26
28
Display Additional Information
on Multi-Project Monitor (' ':
No, 'X': Yes)
Adjustment of Structure Tree
Area by Splitter ('X'=Enabled, '
'=Disabled)
Summary of Project Data in
Multi-Project Monitor ('X'=Yes, '
'=No)
Concurrent Status Changes for
Multiple Tasks ('X'=Enabled, '
'=Disabled)
Display Mirrored Task
Relationships in MP Monitor
('X'=Enabled, ' '=Disabled)
Assignment of Multiple Roles to
Tasks at a Ti e X =E a led,
=Disa led
Allow Constraint Icons without
Add. Info. in Graphical View
('X'=On, ' '=Off)
Enhance Display of Details
Window in Graphical View
('X'=On, ' '=Off)
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Additional Display Options for
Assignments to Project
Elements (' '=No, 'X'=Yes)
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
One-Click Completion of
Subordinate Project Elements ('
'=No, 'X'=Yes)
Improved Alignment of Project
Evaluation Display (' '=No,
'X'=Yes)
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
29
Delete Button in Project
Dashboard ('X'=Yes, ' '=No)
30
Data Aggregation in Projects
('X'=Enabled, ' '=Disabled)
31
Fullscreen Mode for Graphical
View ('X'=Enabled, ' '=Disabled)
32
Move-Up/Move-Down Buttons
in Project ('X'=Yes, ' '=No)
33
34
35
36
37
38
40
41
42
17
X
SAP Notes Language
Independent
X
Simplification List for SAP S/4HANA 1610
394
7
General
Default
Values
22
Document Alignment(' ': KM,
'X': KPRO)
7
General
Default
Values
23
Default number of columns
initially displayed in Financial
and Capacity Planning
Switch is obsolete and will be deleted.
27
Check-in/Check-out of
Documents (' ': Normal, 'X':
HTTP-Based)
Switch will be Removed. Feature will no longer be
available.
28
HTTP Destination for SAP
BusinessObjects Explorer
Switch will be Removed. Feature will no longer be
available.
31
Flag is obsolete (SAP Note
1677356)
Switch is obsolete and will be deleted.
36
Flag is obsolete: Activate
calculation of derived capacity
attribute
Switch is obsolete and will be deleted.
38
Flag is obsolete (SAP Note
1755486)
Switch is obsolete and will be deleted.
39
Activate Multiple Object
Selection for Reporting Cockpit
('X' =Yes, ' ' = No )
40
Flag is obsolete
Switch is obsolete and will be deleted.
46
Override Authorizations for
Documents in Item Versions
('X'=Yes, ' '=No)
9
Use Project Calendar for Linked
Item ('X'=Yes, ' '=No)
1
Updating Staffing According To
Tasks ('X'=Enabled, ' '=Disabled)
Switch will be removed. Feature will be activated available
by default. In most cases, using the feature requires
further configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
7
7
7
7
7
7
7
7
9
11
11
11
11
11
11
11
11
11
12
General
Default
Values
General
Default
Values
General
Default
Values
General
Default
Values
General
Default
Values
General
Default
Values
General
Default
Values
General
Default
Values
Portfolio
Item Project
Integration
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Staffing and
Resource
Management
Scheduling
and Project
Structuring
2
3
4
5
6
7
8
12
1
Confirmed Role Efforts in
Staffing Overview of Projects
('X'=Yes, ' '=No)
Export of Cross-Project
Resource/Staffing Data
('X'=Enabled, ' '=Disabled)
Consider User Group
Authorization in Resource
Management (Yes = 'X', No = ' ')
Personalized Layout for
Resource Management Screens
('X'=Yes, ' '=No)
SAP Notes in Cross-Project
Staffing Overview ('X'=Yes, '
'=No)
Updating Multiple Roles
According to Tasks ('X'=Enabled,
' '=Disabled)
Project Number as Search
Criterion in Role Search ('X'=Yes,
' '=No)
Retain Node Expansion After
Saving in Overview Screens
('X'=Yes, ' '=No)
Automatic Scheduling of All
Project Elements ('X'=Enabled, '
'=Disabled)
X
X
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Simplification List for SAP S/4HANA 1610
395
12
12
12
12
Scheduling
and Project
Structuring
Scheduling
and Project
Structuring
Scheduling
and Project
Structuring
Scheduling
and Project
Structuring
3
4
5
6
Creation/Deletion of Multiple
Relationships ('X'=Enabled, '
'=Disabled)
Optimization of Task and
Milestone Relationships
('X'=Enabled, ' '=Disabled)
Changing Scheduling Type in
Project ('X'=Enabled, '
'=Disabled)
Preserve Relationships When
Canceling Tasks ('X'=Enabled, '
'=Disabled)
Sending E-Mails from Project
Elements ('X' = Enabled, ' ' =
Disabled)
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
13
Additional
Features
1
13
Additional
Features
2
Export/Import of Templates
('X'=Enabled, ' '=Disabled)
13
Additional
Features
4
Comparison with Actual Dates
in Graphical View ('X'=Enabled, '
'=Disabled)
13
Additional
Features
5
Export of Multi-Project Monitor
Data ('X'=Enabled, ' '=Disabled)
13
Additional
Features
6
Export of Resource Planning
Data 'X =E a led, ' '=Disa led
X
13
Additional
Features
7
Export of Graphical View ('X'
=Enabled, ' ' =Disabled)
X
13
Additional
Features
8
Export of Evaluation Data
'X =E a led, ' '=Disa led
X
13
Additional
Features
9
Project-Specific Display of
Earliest or Latest Dates
('X'=Enabled, ' '=Disabled)
X
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
Switch will be removed. Feature will be activated by
default. In most cases, using the feature requires further
configuration.
SAP Note 2321885 provides a pre-conversion check for some of these features.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
Review the settings in your system before the conversion. If you have overwritten the default values,
SAP recommends to delete the entries that have been deleted by SAP.
Related SAP Notes
Conversion pre-checks
Http-based Check-In/Check-out
SAP Note 2321885
SAP Note 2353984
Simplification List for SAP S/4HANA 1610
396
2.2.1.8
Fiori apps of UI FOR SAP PORTF PROJ MGMT 6.0 in SAP Portfolio and Projec
Description
The SAP Fiori apps of the UI FOR SAP PORTF PROJ MGMT 6.0 product version are no longer
supported. For the Program Manager role, the following SAP Fiori apps are not available anymore:
Approve Decision Points
Create Portfolio Item Proposals
Change Portfolio Items
For the Project Team Member role, a new Confirm Project Tasks app is available.
Business Process-Related Information
The functionality is also provided by corresponding Web Dynpro applications, therefore no major
impact is expected.
Required and Recommended Action(s)
If you are using the apps for the Program Manager role, check the Web Dynpro applications.
2.2.1.9
Portfolio Structure Graphic in SAP Portfolio and Project Management for
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the graphic view of the portfolio
structure is no longer available.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
The table view for the portfolio structure is still available. No further actions expected.
2.2.1.10 SAP Smart Forms in SAP Portfolio and Project Management for SAP S/4HANA
Description
In SAP Portfolio and Project Management for SAP S/4HANA, SAP Smart Forms for printing Project
Management information like Status Reports and so on are no longer available. Instead the
Adobe PDF-based Forms can be used.
Simplification List for SAP S/4HANA 1610
397
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions expected.
How to Determine Relevancy
To determine if this Simplification Item is relevant please check if you use SAP Smart Forms for
printing Project Management information.
2.2.1.11 Resource Management Web Dynpro Views in SAP Portfolio and Project Manage
Description
The old Resource Management views (invisible by default, but possible to make them visible by BAdI
DPR_RES_OVERVIEW) are not available in SAP Portfolio and Project Management for SAP S/4HANA.
Instead the new overview views can be used.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions expected.
2.2.1.12 WebDAV and EasyDMS Integration in SAP Portfolio and Project Management f
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the WebDAV integration and EasyDMS
integration are not available.
Business Process-Related Information
It is no longer possible to exchange data using WebDAV integration or EasyDMS integration.
Required and Recommended Action(s)
SAP recommends to evaluate SAP Document Center as a substitute.
How to Determine Relevancy
Simplification List for SAP S/4HANA 1610
398
To determine if this Simplification Item is relevant please check if you use WebDAV and EasyDMS
Integration.
2.2.1.13 SAP Portal Integration in SAP Portfolio and Project Management for SAP S
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the integration to SAP NetWeaver
Portal is not available.
Business Process-Related Information
SAP recommends to evaluate SAP NetWeaver Business Client as a substitute.
How to Determine Relevancy
This Simplification Item is relevant if the integration to SAP NetWeaver Portal has been used.
2.2.1.14 cRoom Integration in SAP Portfolio and Project Management for SAP S/4HAN
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the cRoom integration is not available.
Business Process-Related Information
It is no longer possible to exchange data using the cRoom integration.
Required and Recommended Action(s)
SAP recommends to evaluate SAP Document Center as a substitute.
How to Determine Relevancy
To determine if this Simplification Item is relevant please check if you use cRoom integration.
2.2.1.15 xPD Integration in SAP Portfolio and Project Management for SAP S/4HANA
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the SAP xPD integration is no longer
available.
Business Process-Related Information
Simplification List for SAP S/4HANA 1610
399
It is no longer possible to exchange data between SAP Portfolio and Project Management for SAP
S/4HANA and SAP xPD.
Required and Recommended Action(s)
SAP recommends to evaluate SAP Innovation Management as a substitute.
2.2.1.16 Xcelsius Integration in SAP Portfolio and Project Management for SAP S/4
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the Xcelsius integration is not available.
Business Process-Related Information
It is no longer possible to exchange data using Xcelsius integration.
Required and Recommended Action(s)
No further actions expected.
How to Determine Relevancy
To determine if this Simplification Item is relevant please check if you use Xcelsius integration.
2.2.1.17 SAP BusinessObjects Explorer Integration in SAP Portfolio and Project Ma
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the SAP BusinessObjects Explorer
integration is not available.
Business Process-Related Information
It is no longer possible to analyze data using SAP BusinessObjects Explorer integration.
Required and Recommended Action(s)
No further actions expected.
How to Determine Relevancy
This Simplification Item is relevant if in the customizing of global settings the setting 0007/0028
contains HTTP destination.
Simplification List for SAP S/4HANA 1610
400
2.2.1.18 Project simulation in SAP Portfolio and Project Management for SAP S/4HA
Description
In SAP Portfolio and Project Management for SAP S/4HANA, project simulation without an operative
project is not available.
Business Process-Related Information
It is only possible to create project simulations based on operative projects.
Required and Recommended Action(s)
No further actions expected.
2.2.1.19 Simplification of data model in SAP Portfolio and Project Management for
Description
With SAP Portfolio and Project Management for SAP S/4HANA, the current data model is considered
as not strategic in SAP Portfolio and Project Management for SAP S/4HANA, because there is a
known need to change or replace the current data model by a simplified one. The current data
model can still be used with SAP Portfolio and Project Management 1.0 for SAP S/4HANA to enable
an end-to-end business process, but could be changed, removed or replaced according to the
roadmap for SAP Portfolio and Project Management for SAP S/4HANA.
Business Process related information
Changes or replacements of the current data model should primarily influence how a business
process is supported by the solution, but do not necessarily lead to a change of the business process
itself.
Required and Recommended Action(s)
The current data model is still used in SAP Portfolio and Project Management 1.0 for SAP S/4HANA
to enable an end-to-end business process, but will be subject of renovation and simplification
according to the roadmap for SAP Portfolio and Project Management for SAP S/4HANA.
2.2.1.20 Deletion of obsolete packages in EPPM
Description
In SAP Portfolio and Project Management for SAP S/4HANA, packages with development objects that
were already obsolete in SAP Porfolio and Project Management 6.1 have been deleted.
Business Process-Related Information
Simplification List for SAP S/4HANA 1610
401
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions necessary.
2.2.1.21 Business Partner in SAP Portfolio and Project Management for SAP S/4HANA
Description
In SAP Portfolio and Project Management for SAP S/4HANA user assignments of business partners of
type 'Resource' are no longer available. User Assignments using transaction BP are no longer
possible, therefore you cannot create a business partner of type 'Employee' with user assignment
using transaction BP.
Required and Recommended Action(s)
SAP recommends to evaluate other options to use business partners of type 'Employee' for which
user assignments are still possible according to Human Resources processes, for example:
1. Use transaction PA40 (action Hiring) to create a minimum set of HR master data
2. Use transaction PA30 to maintain the user information in infotype 0105/0001
3. Run report /SHCM/RH_SYNC_BUPA_FROM_EMPL (S/4 HANA BUPA Synchronization)
A business partner of type 'Employee' is then created which has an user assignment. For this business
partner also the type 'Resource' can be maintained, e.g. to define a cost rate.
How to Determine Relevancy
This Simplification Item is relevant if business partners of type 'Employee' and type 'Resource' with
user assignments have been used in SAP Portfolio and Project Management.
2.2.1.22 Simplified ACLs (Access Control Lists) concept in SAP Portfolio and Proj
Description
A simplified ACLs (Access Control Lists) concept in SAP Portfolio and Project Management for SAP
S/4HANA is now in place to reduce business complexity. Some options are not available any longer
and a simplified logic leads to different results. Major changes are:
a) Authorizations related to organizational units of project elements are not available in SAP
Portfolio and Project Management for SAP S/4HANA.
b) 'NoAuth' activity is not available in SAP Portfolio and Project Management for SAP S/4HANA.
c) c) User Groups are only considered up to the third level until the level 3 and activities are only
considered up to the fifth level.
Simplification List for SAP S/4HANA 1610
402
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process related information
Since the new and simplified ACLs (Access Control Lists) concept is now used, depending on the
maintained authorizations the results of authorization determination could now differ from results of
the non simplified authorization concept in the SAP Portfolio and Project Management solution. You
can now check and adapt the authorizations maintained in your projects according to the
information given by the pre-check.
Required and Recommended Action(s)
In case you used some of the options not available any longer, adjust the maintained authorizations
and in addition make knowledge transfer to key and end users. The note 2321885 contains the
report DPR_PRE_CHECK_S4MIG_AUTHREF to analyze the authorizations in a more detailed way than
the corresponding pre-conversion check.
How to Determine Relevancy
This Simplification Item is relevant in case options have been used that are no longer supported or in
case authorizations have been set up in such a way that the new authorization logic leads to different
results.
2.2.1.23 SAP Web Dynpro usage in SAP Port. and Proj. Management for SAP S/4HANA
Description
With SAP Portfolio and Project Management for SAP S/4HANA, it is planned to revise various features
in order to simplify the solution. This includes the renovation of the user interface, whereas SAP Fiori
is the preferred technology. That means that the SAP Web Dynpro based user interfaces of SAP
Portfolio and Project Management for SAP S/4HANA are considered as not strategic anymore, means
no major improvements are currently planned based on this technology for the solution. This applies
to the portfolio management and project management part of SAP Portfolio and Project
Management for SAP S/4HANA and comprises for example:
SAP Web Dynpro based dashboards (e.g. project dashboard) and table views (e.g. table
view for the project structure)
SAP Web Dynpro based detail screens (e.g. detail view for the project structure or for the
portfolio item)
SAP Web Dynpro based functionalities, e.g. project favorites for the project dashboard.
As the renovation with SAP Fiori is planned based on a step-wise approach according to the roadmap
of SAP Portfolio and Project Management for SAP S/4HANA and will take some time, the SAP Web
Dynpro based user interface can still be used to enable end-to-end business processes.
Business Process related information
Simplification List for SAP S/4HANA 1610
403
The renovation of the user interface of SAP Portfolio and Project Management for SAP S/4HANA with
SAP Fiori is planned to happen along business roles, to provide a more simple solution for e.g. the
project manager.
Required and Recommended Action(s)
No immediate action required, but with each additionally released SAP Fiori based app you should
check if you could apply it for your business process.
How to Determine Relevancy
This item is relevant for every customer of SAP Portfolio and Project Management for SAP S/4HANA.
2.2.1.24 Changes compared to older releases than SAP Port. and Proj. Mngt. 6.1
Description
SAP provides transition worklist items based on changes between SAP Portfolio and Project
Management 6.1 and SAP Portfolio and Project Management for SAP S/4HANA. SAP does not provide
transition worklist items for changes that happened already between older releases and SAP
Portfolio and Project Management 6.1. SAP Note 2321885 provides a pre-conversion check for this
feature.
Business Process related information
Each release of SAP Portfolio and Project Management may contain changes which could impact
business processes.
Required and Recommended Action(s)
In case you plan a conversion from a release older than SAP Portfolio and Project Management 6.1 to
SAP Portfolio and Project Management for SAP S/4HANA, you need to read and check all Release
Notes and Upgrade Master Guides of all releases between your start release and (including) SAP
Portfolio and Project Management 6.1.
How to Determine Relevancy
Check the release of your SAP Portfolio and Project Management installation by logon the ABAP
system, open "System" -> "Status.." in the menu and click the button "Components" in the opened
dialog.
2.2.1.25 Not strategic functionalities within SAP S/4HANA
Description
With SAP Portfolio and Project Management for SAP S/4HANA, many features are changed in order
to improve and simplify the solution. To streamline the solution, some features are removed. SAP
Simplification List for SAP S/4HANA 1610
404
plans to continue to improve, simplify and streamline SAP Portfolio and Project Management for SAP
S/4HANA in future. The list below summarizes features which SAP considers as not strategic in SAP
Portfolio and Project Management for SAP S/4HANA, because there is a known need to change or
replace them in future. These features can still be used with SAP Portfolio and Project Management
1.0 for SAP S/4HANA to enable an end-to-end business process, but could be changed, removed or
replaced by another feature in future according to the roadmap of SAP Portfolio and Project
Management for SAP S/4HANA.
Document management: There is a known need to adjust this feature with the planned SAP
Fiori Attachment Service.
Phase approvals: There is a known need for a more generic approval feature, means a
feature which also enables an approval process of e.g. milestones.
Decision flow management: With SAP Portfolio and Project Management for SAP S/4HANA, it
is planned to simplify the object and data model. Based on that, there is a known need
to adjust the decision flow management accordingly.
Field control: There is a known need to streamline the different field control features of the
solution.
SAP Smart Forms for E-Mail: There is a known need to replace SAP Smart Forms.
Business Context Viewer: There is a known need to streamline different analytical features.
Extractors for SAP Business Warehouse: There is a known need to streamline different
analytical features.
RFC enabled function modules of the project management as well as of the portfolio
management part: Both have never been released for usage by customer.
Integration to the PLM object navigator: There is a known need for a renovation of this
feature with SAP Fiori. According to that, the integration needs to be adjusted.
Search within documents with SAP TREX: There is a known need to streamline different
search capabilities.
Integration with SAP Identity Management: There is a known need to streamline different
capabilities.
Business Process related information
Changes or replacements of the mentioned features should primarily influence how a business
process is supported by the solution, but do not necessarily lead to a change of the business process
itself.
Required and Recommended Action(s)
No immediate action required, but customers should be aware that one or more of the mentioned
features could be changed, removed or replaced by another feature in future.
How to Determine Relevancy
This item is relevant for every customer of SAP Portfolio and Project Management for SAP S/4HANA.
Simplification List for SAP S/4HANA 1610
405
2.2.1.26 Control Plans in SAP Portfolio and Project Management for SAP S/4HANA
Description
In SAP Portfolio and Project Management for SAP S/4HANA, control plans (incl., for example. control
plan templates and search for control plan objects) are not available anymore. SAP recommends to
evaluate the control plan functionality in SAP S/4HANA as a substitute.
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process-Related Information
In case that control plans are used, the corresponding business processes have to be adapted.
Required and Recommended Action(s)
The control plan data cannot be migrated to SAP Portfolio and Project Management for SAP
S/4HANA, therefore it is required to clean up the data before the system conversion in order to
prevent any data loss. Archive the corresponding projects or delete not needed control plan data
before you continue the system conversion.
The control plan UI field customizing (customer own) cannot be migrated to SAP Portfolio and Project
Management for SAP S/4HANA, therefore needs to be deleted. Further details are described in the
consulting note 2363785.
2.2.1.27 HTTP-Based Document Management in SAP Portfolio and Project Management f
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the HTTP-Based Document Management
for the check-in/check-out of documents is no longer available. The HTTP-Based check-in/check-out
feature had provided the possibility to upload and download documents including the possibility to
checkout a document and open a document with the specified client application. The HTTPbased check-in/check-out required a Java installation and a valid certificate on client-side.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
The functionality to upload and download documents is still available and can be used. No further
actions necessary.
How to Determine Relevancy
Simplification List for SAP S/4HANA 1610
406
Please check the Global Settings in Customizing: SAP Portfolio and Project Management -> Project
Management -> Basic Settings -> Override Default Global Settings.
If Master Switch 0007 (General Default Values) 0027 (Check-in/Check-out of Documents (' ': Normal,
'X': HTTP-Based)) is set to X, the Transition Worklist item is relevant.
Related SAP Notes
Conversion pre-checks
SAP Note 2321885
2.2.1.28 Object Links to SAP Environmental Compliance in SAP Portfolio and Projec
Description
Object Links to SAP Environmental Compliance are not longer available in SAP Portfolio and Project
Management for SAP S/4HANA.
Business Process-Related Information
Objects from SAP Environmental Compliance can't be linked to a project or portfolio item anymore in
SAP Portfolio and Project Management for SAP S/4HANA.
Required and Recommended Action(s)
In case you plan to use a similar functionality in SAP Portfolio and Project Management for SAP
S/4HANA, you may create a custom own object link type.
2.2.1.29 Microsoft Project Import/Export in SAP Portfolio and Project Management
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the import/export function for Microsoft
Project Client data has been changed. The system no longer uses the binary file format of Microsoft
Project (.MPP). Instead the XML format for Microsoft Project is used. Neither an ActiveX installation
nor a definition of security lists for office controls is required.
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions are expected.
Simplification List for SAP S/4HANA 1610
407
3
Appendix
3.1
Related Information – SAP Help
System Conversion related information in SAP Help
SAP Help
SAP S/4HANA 1511
(FPS2)
SAP S/4HANA On-Premise documentation
SAP S/4HANA 1610
(initial shipment)
http://help.sap.com/s4hana
(select the appropriate release dependent information)
Getting Started With SAP S/4HANA
Conversion Guide for SAP S/4HANA
Simplification List for SAP S/4HANA
Maintenance Planner
Software Update Manager (SUM) Software Logistics Toolset
PDF
PDF
PDF
PDF
PDF
PDF
Link
Link
System Maintenance
Custom Code Migration (SAP Help)
SAP S/4HANA Feature Scope Description
Simplification List for SAP S/4HANA 1610
Link
PDF
Link
PDF
408
Sara Millán Adame