White Paper
Document Version: 1.32– 2024-02-26
PUBLIC
Simplification List for
SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1
and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment &
Feature Pack Stack 1
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 2
Table of Content
1. Introduction ................................................................................................................................. 26
1.1 Purpose of the Document ............................................................................................................... 27
1.2 General Topics for the Simplification List ..................................................................................... 27
1.3 System Conversion Sequence ......................................................................................................... 29
1.4 The Simplification List for SAP S/4HANA release 2023 Initial Shipment & Feature Pack Stack 1 –
this document ........................................................................................................................................... 30
2. Cross Topics ................................................................................................................................ 32
2.1 ABAPTWL - Visualization of SAP Business Workflow Metadata .................................................. 32
2.2 ABAP4TWL - Removal of Tagging Framework ............................................................................. 33
2.3 ABAP4TWL - Removal LT Check ATC Adapter ............................................................................. 34
2.4 ABAP4TWL - Removal of ILM Store Monitoring GUI ................................................................... 35
2.5 ABAP4TWL - Removal of Drag and Relate Workplace Plugin ...................................................... 35
2.6 ABAP4TWL - Removal of Package SCMO .................................................................................... 36
2.7 ABAP4TWL - Removal of ByDesign Config Framework Services ................................................. 37
2.8 ABAP Test Framework: Export of ATC Results to 3rd Party Tools ............................................... 37
2.9 ABAPTWL - Deprecation of Hana Rules Framework .................................................................... 38
2.10 ABAPTWL - No support for non simplified system flavour ....................................................... 39
2.11 ABAPTWL - Cleanup of orphaned objects ................................................................................ 40
2.12 ABAPTWL - SSCR license key procedure is no longer supported ............................................. 41
2.13 S4TWL - Removal of Business Application Accelerator ............................................................ 42
2.14 ABAPTWL - VM Container not supported ................................................................................ 43
2.15 ABAPTWL - AS Java not available ........................................................................................... 44
2.16 ABAPTWL - Dual Stack not supported ...................................................................................... 45
2.17 ABAPTWL - Instances without ICM not supported ................................................................... 46
2.18 ABAPTWL - Removal of OSS1 (Logon to SAP Service Marketplace) ....................................... 46
2.19 ABAPTWL - End of Support for Pool Tables ............................................................................ 47
2.20 S4TWL - FIORI APPLICATIONS FOR SUITE ON HANA ON-PREMISE ............................... 50
2.21 S4TWL - SAP S/4HANA AND SAP BUSINESS WAREHOUSE CONTENT .............................. 52
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 3
2.22 S4TWL - Social Intelligence ...................................................................................................... 54
2.23 S4TWL - Custom Fields ............................................................................................................. 54
2.24 S4TWL - Side Panel functionality in SAP S/4HANA (on-premise) ............................................ 56
2.25 S4TWL - Changed Interfaces ..................................................................................................... 59
2.26 S4TWL - SAP Support Desk ($$-Messages) .............................................................................. 61
2.27 S4TWL - Changes in Process Observer .................................................................................... 62
2.28 ABAP4TWL - Removal of Transceiver Integration ................................................................... 64
2.29 S4TWL - BI Extractors in SAP S/4HANA .................................................................................. 65
2.30 S4TWL - MRS Enhancements for Material Master ................................................................... 69
2.31 S4TWL - Change of Situation Types in Situation Handling ...................................................... 70
2.32 ABAPTWL - Change of workflow system user and workflow system jobs ................................. 72
2.33 ABAPTWL - Change of authorization checks SAP Business Workflow ..................................... 74
2.34 S4TWL - Business User Management ....................................................................................... 78
2.35 S4TWL - Generic Check for SAP S/4HANA Conversion and Upgrade ..................................... 88
2.36 S4TWL - Removal of Add-On CTS_PLUG ................................................................................ 91
2.37 S4TWL - Removal of obsolete Data Modeler (SD11) content ................................................... 91
2.38 S4TWL - Simplified data model in Joint Venture Accounting ................................................... 93
2.39 S4TWL - New Default Security Settings for SAP S/4HANA ...................................................... 95
2.40 S4TWL - Extended Check of Output Device in Output Control ................................................. 96
2.41 S4TWL - Deprecation of Design Studio Apps............................................................................ 98
2.42 SWTL - Deprecation of Obsolete Data Handling Tool .............................................................. 99
2.43 S4TWL - CATSXT .................................................................................................................... 100
2.44 S4TWL - OUTPUT MANAGEMENT ....................................................................................... 102
2.45 S4TWL - SAP HANA LIVE REPORTING ................................................................................ 104
2.46 S4TWL - ENTERPRISE SEARCH ........................................................................................... 105
2.47 S4TWL - Duplicate request entries in Output Management .................................................... 107
2.48 S4TWL - Ariba Network Integration ....................................................................................... 108
2.49 S4TWL - INTERNET PRICING AND CONFIGURATOR (SAP IPC) ..................................... 112
2.50 S4TWL - JOB SCHEDULING ................................................................................................. 114
2.51 S4TWL - LEGACY SYSTEM MIGRATION WORKBENCH .................................................... 116
3. Master Data ............................................................................................................................... 122
3.1 S4TWL - MDM 3.0 integration .................................................................................................... 122
3.2 S4TWL - SRM Product Master ..................................................................................................... 123
3.3 S4TWL - Logistics Batch Management ........................................................................................ 125
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 4
3.4 S4TWL - Product catalog ............................................................................................................. 126
3.5 S4TWL - Object Identifier Type Code .......................................................................................... 129
3.6 S4TWL – Deprecation of 4 fields from FSBP table BP1010 ........................................................ 129
3.7 S4TWL: Business partner data exchange between SAP CRM and S/4HANA .............................. 132
3.8 S4TWL - HANA-based Analytics for Master Data Governance ................................................... 135
3.9 S4TWL - Business Partner BUT000/Header Level Time Dependency ......................................... 136
3.10 S4TWL - BADI ADDRESS_SEARCH (Duplicate Check) is Not Supported in SAP S/4HANA 139
3.11 S4TWL - Business Partner Hierarchy Not Available .............................................................. 140
3.12 S4TWL - MDG in Lama ........................................................................................................... 141
3.13 S4TWL - Migration of Business Partner Data specific to GST India ...................................... 142
3.14 S4TWL - MDG_MDC in Lama ................................................................................................ 144
3.15 S4TWL - Batch Input for Customer Master/Supplier Master .................................................. 145
3.16 S4TWL - API RFC_CVI_EI_INBOUND_MAIN is obsolete .................................................... 146
3.17 S4TWL - Removal of Gender Domain Fixed Values ............................................................... 147
3.18 S4TWL - Usage of obsolete links in tables BD001 / BC001 .................................................... 149
3.19 S4TWL - Business Partner Approach ...................................................................................... 151
3.20 S4TWL - Reduction of Redundant Business Partner Data Storage in the 'BUTADRSEARC .. 156
3.21 S4TWL - Simplified Product Master Tables Related to OMSR Transaction ........................... 158
3.22 S4TWL - Material Number Field Length Extension ................................................................ 160
3.23 S4TWL - Simplification of copy/reference handling ................................................................ 168
3.24 S4TWL - Foreign Trade fields in Material Master .................................................................. 170
3.25 S4TWL - MRP fields in Material Master ................................................................................. 172
3.26 S4TWL - Material Type SERV ................................................................................................. 175
4. Commercial Project Management ............................................................................................ 180
4.1 S4TWL - CPM - Rate Card .......................................................................................................... 180
4.2 S4TWL - Interface of SAP CPM with SAP Cloud for Customer ................................................... 180
4.3 S4TWL - Fiori Apps of SAP Commercial Project Management................................................... 181
4.4 S4TWL - Launchpads of Gantt Chart and Commercial Project Inception................................... 182
4.5 S4TWL - Workbooks in Project Cost and Revenue Planning ....................................................... 183
4.6 S4TWL - CPM - Forecast from financial plan versions ............................................................... 185
4.7 S4TWL - CPM - Personal Activity List ........................................................................................ 186
5. Commodity Management .......................................................................................................... 188
5.1 S4TWL - CM: Simplified Market Data ........................................................................................ 188
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 5
5.2 S4TWL - CM: Simplified CPE Activation ................................................................................... 189
5.3 S4TWL - CM: CPE Simplified Formula Assembly & Formula Evaluation ................................. 190
5.4 S4TWL - CM: CPE Simplification of Routines & Rules .............................................................. 191
5.5 S4TWL - CM: CPE Simplified Data Model ................................................................................. 192
5.6 S4TWL - Simplified Commodity Curves ....................................................................................... 192
5.7 S4TWL - Simplified DCS Access .................................................................................................. 193
5.8 S4TWL - Simplification in Position Reporting for Financial Transactions ................................. 194
5.9 S4TWL - Simplified Data Flow of logistics data for Risk Reporting Database ........................... 195
5.10 S4TWL - Position Reporting on versioned pricing data .......................................................... 196
5.11 S4TWL - Hedge Management for logistics transactions ......................................................... 198
5.12 S4TWL - Position Reports delivered by Agricultural Contract Management ......................... 199
5.13 S4TWL - Risk Determination and Pricing for MM Contracts not supported yet ..................... 200
5.14 S4TWL - Unification of supported technologies in analytical data provisioning .................... 201
5.15 S4TWL - Risk Determination on a schedule line level ............................................................. 202
5.16 S4TWL - Simplification of DCS based Market Data Handling for Fin Transactions ............. 203
5.17 S4TWL - Deprecation of Non DCS based Market Data for Financial Transactions .............. 205
5.18 S4TWL - Deprecation of functions using Non DCS based Market Data ................................. 206
5.19 S4TWL - Simplified Data Model/Master Data ........................................................................ 207
5.20 S4TWL – Contract Processing Monitor & Logistical Options w/ GTM not supported ........... 209
5.21 S4TWL - Mark-to-Market & Profit-and-Loss Reporting for logistics transactions ................ 209
5.22 S4TWL - Mark-to-Market & Profit-and-Loss Reporting for Derivatives ................................ 211
5.23 S4TWL - Mark to Market Accounting Changes ....................................................................... 213
5.24 S4TWL – Integration of Pricing and Payment Events in GTM with Commodity Mngmt. ....... 214
5.25 S4TWL - Performance Optimization of Risk Analytics CDS Views ......................................... 214
5.26 S4TWL - CM: CCTR CPE Commodity Code Harmonization ................................................. 217
5.27 S4TWL - Simplified Commodity Pricing Engine Data Model ................................................. 221
5.28 S4TWL - Data Model Change in the Commodity Condition Types Mapping .......................... 224
6. Corporate Close ......................................................................................................................... 226
6.1 S4TWL - Usage of long Material Number in EC-CS.................................................................... 226
6.2 S4TWL - Consolidation (EC-CS) and preparations for consolidation ......................................... 227
6.3 S4TWL - Consolidation (EC-CS) and preparations for consolidation ......................................... 229
6.4 S4TWL – Real-Time Consolidation (RTC) ................................................................................... 230
6.5 S4TWL – Business Consolidation (SEM-BCS) ............................................................................. 232
6.6 S4TWL – Configuration Changes in Group Reporting ................................................................ 233
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 6
7. Customer Service ....................................................................................................................... 237
7.1 S4TWL - Customer Service .......................................................................................................... 237
7.2 S4TWL - PH_Sample iView.......................................................................................................... 238
7.3 S4TWL - Customer Interaction Center (CIC) .............................................................................. 239
8. Financials – General .................................................................................................................. 241
8.1 S4TWL - DMEE............................................................................................................................ 241
8.2 S4TWL - DATA MODEL CHANGES IN FIN ............................................................................... 243
8.3 S4TWL - REPLACED TRANSACTION CODES AND PROGRAMS IN FIN ............................... 251
8.4 S4TWL - SAP Travel Management in SAP S/4HANA Suite ......................................................... 253
8.5 S4TWL - Plan data is not migrated to SAP S/4HANA .................................................................. 259
8.6 S4TWL – Migration from account solution to ledger solution ..................................................... 264
8.7 S4TWL - Special Purpose Ledger ............................................................................................... 266
8.8 S4TWL - Cost of Sales Ledger ..................................................................................................... 267
8.9 S4TWL - Report Writer / Report Painter in Finance and Controlling ........................................ 269
8.10 S4TWL - Schedule Manager .................................................................................................... 271
9. Financials - Accounts Payable/Accounts Receivable ................................................................ 273
9.1 S4TWL - Integration with FSCM Biller Direct (FI-AR) ............................................................... 273
9.2 S4TWL - Integration with FSCM Biller Direct (FI-AP) ............................................................... 274
10. Financials - Asset Accounting ................................................................................................... 276
10.1 S4TWL - DATA STRUCTURE CHANGES IN ASSET ACCOUNTING ................................... 276
10.2 S4TWL - ASSET ACCOUNTING ............................................................................................. 278
10.3 S4TWL - INTEGRATION TO LEASE ACCOUNTING ENGINE (LAE) .................................. 299
10.4 S4TWL - Asset management transfers in Joint Venture Acccounting (JVA) .......................... 300
10.5 S4TWL - SELECTED BUSINESS FUNCTIONS IN FINANCIAL ACCOUNTING (FI-GL AND
FI-AA) 301
10.6 S4TWL - Check for duplicate internal asset line items (FAAT_DOC_IT) ............................... 304
10.7 S4TWL - Group Assets ............................................................................................................ 305
11. Financials - Cash Management ................................................................................................. 307
11.1 S4TWL - Electronic Payment Integration for China ............................................................... 307
11.2 S4TWL - CASH MANAGEMENT - GENERAL ....................................................................... 308
11.3 S4TWL - CASH MANAGEMENT - Bank Accounts ................................................................. 316
11.4 S4TWL - CASH MANAGEMENT - Memo Record................................................................... 323
11.5 S4TWL - Logic changes in Flow Builder ................................................................................. 326
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 7
11.6 S4TWL - Fiori app Adjust Assigned Liquidity Items deprecated ............................................. 331
11.7 S4TWL - End-of-Day Memo Record Reconciliation................................................................ 332
12. Financials – Controlling ............................................................................................................ 334
12.1 S4TWL - Reference and Simulation Costing ........................................................................... 334
12.2 S4TWL - Summarization Hierarchies in Controlling .............................................................. 335
12.3 S4TWL- Legacy MDI Cost Center Replication ....................................................................... 337
12.4 S4TWL - Technical Changes in Material Ledger with Actual Costing.................................... 338
12.5 S4TWL - Material Ledger: deprecated table for currency and valuation types ...................... 347
12.6 S4TWL - EC-PCA - Classical profit center accounting ......................................................... 348
12.7 S4TWL - Changes in EBRR backend transactions .................................................................. 350
12.8 S4TWL - TECHNICAL CHANGES IN CONTROLLING ......................................................... 354
12.9 S4TWL - PROFIT AND LOSS PLANNING AND PROFIT CENTER PLANNING ................. 356
12.10 S4TWL - ACTIVITY-BASED COSTING .................................................................................. 361
12.11 S4TWL - GENERAL COST OBJECTS AND COST OBJECT HIERARCHIES ....................... 364
12.12 S4TWL - TRANSFER PRICES/ PARALLEL DELTA VERSIONS ............................................ 367
12.13 S4TWL - ALE SCENARIOS ..................................................................................................... 369
12.14 S4TWL - COST ELEMENTS ................................................................................................... 371
12.15 S4TWL - Reporting/Analytics in Controlling .......................................................................... 374
12.16 S4TWL - Profitability Analysis ................................................................................................ 378
13. Cost Management and Profitability Analysis ........................................................................... 384
13.1 S4TWL - Profitability Segment Number Change of Type ........................................................ 384
14. Financials - General Ledger ...................................................................................................... 388
14.1 S4TWL - Profit Center and Segment Reorganisation .............................................................. 388
14.2 S4TWL - GENERAL LEDGER ................................................................................................ 389
14.3 S4TWL - SAP HANA ODP ON HANA CALC VIEW-BASED REPORTING ........................... 391
14.4 S4TWL - Closing Cockpit with S/4 HANA OP......................................................................... 392
14.5 S4TWL - Currencies in Universal Journal .............................................................................. 393
14.6 S4TWL - Manual Accruals (Accrual Engine) .......................................................................... 399
14.7 S4TWL - Amount Field Length Extension ............................................................................... 401
14.8 S4TWL - Removal of D/C Indicator from Editing Options ...................................................... 410
15. Financials - International Trade ............................................................................................... 412
15.1 S4TWL - Material classification with commodity codes ......................................................... 412
15.2 S4TWL - Personal Data in Provider of Information ............................................................... 413
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 8
15.3 S4TWL - Determination of default values in Intrastat reporting ............................................. 415
15.4 S4TWL - Company code address data in provider of information .......................................... 418
16. Financials - Treasury and Risk Management ........................................................................... 420
16.1 S4TWL - Drilldown Reporting in Treasury and Risk Management ......................................... 420
16.2 S4TWL - Master Agreements ................................................................................................... 421
16.3 S4TWL - Offers ........................................................................................................................ 422
16.4 S4TWL - Simulation in Transaction Management ................................................................... 423
16.5 S4TWL - Quantity Ledger Always Active for Money Market Transactions ............................. 423
16.6 S4TWL - Several Kinds of Financial Objects Disabled ........................................................... 425
16.7 S4TWL - Allocation of FX Transactions to Financial Documents and Cash Management .... 427
16.8 S4TWL - Correspondence Functionality ................................................................................. 428
16.9 S4TWL - Interest Rate and Yield Curve Functionality ............................................................ 430
16.10 S4TWL - Accrual/Deferral of Expenses and Revenues ............................................................ 432
16.11 S4TWL - Credit Risk Analyzer Link to Cash Management ...................................................... 434
16.12 S4TWL - Exposure Management 1.0 ....................................................................................... 435
16.13 S4TWL - Drawable Bonds ....................................................................................................... 437
17. Financials – Miscellaneous ........................................................................................................ 438
17.1 S4TWL - Credit Management .................................................................................................. 438
17.2 S4TWL - Technical Changes in Material Ledger .................................................................... 442
17.3 S4TWL - Real Estate Classic ................................................................................................... 445
17.4 S4TWL - Conversion to S/4HANA Material Ledger and Actual Costing ................................ 446
17.5 S4TWL - Differentiation Category Dependent FS Datasets Not Available in S/4HANA ......... 454
17.6 S4TWL - Product Design Cost Estimate .................................................................................. 457
18. Human Resources ...................................................................................................................... 460
18.1 S4TWL – Compensation Management .................................................................................... 460
18.2 S4TWL – Personnel Cost Planning ........................................................................................ 461
18.3 S4TWL – HR Employee Interaction Center ............................................................................ 462
18.4 S4TWL – Enterprise Services Personnel Administration ........................................................ 464
18.5 S4TWL – Expert Finder ........................................................................................................... 465
18.6 S4TWL – Funds and Position Management ............................................................................ 466
18.7 S4TWL – HCM Processes and Forms JAVA and Adobe ......................................................... 467
18.8 S4TWL – Landing Pages and Suite Page Builder ................................................................... 469
18.9 S4TWL – HCM Obsolete Packages ......................................................................................... 471
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 9
18.10 S4TWL - General HCM Approach within SAP S/4HANA ....................................................... 472
18.11 S4TWL – Recruiting ................................................................................................................ 474
18.12 S4TWL – Obsolete Payroll Reports ......................................................................................... 475
18.13 S4TWL – HR Shared Service Framework ............................................................................... 477
18.14 S4TWL – Training and Event Management............................................................................. 478
18.15 S4TWL – Workforce Viewer .................................................................................................... 480
18.16 S4TWL – HIS and Structural Graphic ..................................................................................... 481
18.17 S4TWL – Parts of Time Management ...................................................................................... 482
18.18 S4TWL - SuccessFactors Employee Central Integration ........................................................ 484
18.19 S4TWL – Australia Public Sector ESS Not Supported in JAVA Technology ........................... 487
18.20 S4TWL - Conversion of Employees to Business Partners ....................................................... 488
18.21 S4TWL - E-Recruiting Localization for Brazil PS in SAP HCM for SAP S/4HANA ............... 490
18.22 S4TWL – Flexible Benefits not supported in ESS technologies ............................................... 491
18.23 S4TWL – HR Policy Management - India – Not supported Apps ............................................ 493
18.24 S4TWL – US Effort reporting – Not supported in ESS and MSS technologies ........................ 494
18.25 S4TWL – HCM Obsolete Package - US Federal Public Sector Functions ............................. 496
18.26 S4TWL - SAP E-Recruiting ..................................................................................................... 498
18.27 S4TWL - ESS and MSS ............................................................................................................ 501
18.28 S4TWL - Travel Management SRA004 Simplified Model ........................................................ 503
18.29 S4TWL – Managers Desktop ................................................................................................... 505
18.30 S4TWL – Country Version Denmark (PY-DK) ........................................................................ 506
18.31 S4TWL – Personnel Development ........................................................................................... 508
18.32 S4TWL - BAdIs not supported in EC Payroll .......................................................................... 510
19. Logistics – General .................................................................................................................... 516
19.1 S4TWL - Advanced Track & Trace.......................................................................................... 516
19.2 S4TWL - Season Field Length Extension ................................................................................ 517
20. Logistics – AB ............................................................................................................................ 519
20.1 S4TWL - Agency Business ....................................................................................................... 519
21. Logistics – ATP .......................................................................................................................... 545
21.1 S4TWL - New advanced ATP in SAP S/4HANA – Table VBBS ............................................... 545
22. Logistics – DSD .......................................................................................................................... 547
22.1 S4TWL - Direct Store Delivery ................................................................................................ 547
22.2 S4TWL - Direct Store Delivery in SAP S/4HANA ................................................................... 548
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 10
23. Logistics - Environment, Health & Safety (EHS) ..................................................................... 551
23.1 S4TWL - Deprecation of EHS Data Series and Amounts ........................................................ 551
23.2 S4TWL - Deprecation of 'Inspect Safety Control' Fiori app .................................................... 552
23.3 S4TWL - Deprecation of 'Retrieve Safety Information' Fiori app ........................................... 553
23.4 S4TWL - Simplification of Authorizations in Incident Management ....................................... 554
23.5 S4TWL - Removal of EHS Home Screens ................................................................................ 556
23.6 S4TWL - Specification Workbench Adjustments ...................................................................... 558
23.7 S4TWL - Simplification of Incident Management workflows .................................................. 559
23.8 S4TWL - Changed data model for listed substances ............................................................... 560
23.9 S4TWL - Changed data model for Occupational Exposure Limits .......................................... 562
23.10 S4TWL - Removal of task und document tab pages on incidents ............................................ 564
23.11 S4TWL - Changed process for risk identification .................................................................... 566
23.12 S4TWL - Industrial Hygiene and EC interfaces ...................................................................... 568
23.13 S4TWL - Renovation of EHS authorization concept ................................................................ 570
23.14 S4TWL - Changed data model for Job Steps ........................................................................... 573
23.15 S4TWL - Adjustments needed due to changed data model for Compliance Requirement ....... 576
23.16 S4TWL - Deprecation of action templates in control master .................................................. 577
23.17 S4TWL - Simplification of Risk Assessment Lifecycle ............................................................. 578
23.18 S4TWL - Renovation of task management ............................................................................... 580
23.19 S4TWL - Deprecation of Mapping Workbench in Foundation of EHS.................................... 585
23.20 S4TWL - Renovation of Investigation Lifecycle Workflow ...................................................... 586
23.21 S4TWL - Barcode reader not supported in app Display Safety-Relevant Information ............ 587
23.22 S4TWL - Replacement of Office integration in Risk Assessment Step ..................................... 589
23.23 S4TWL - Replacement of Excel integration in Exposure Assessment ...................................... 591
23.24 S4TWL - Occupational Health ................................................................................................ 593
23.25 S4TWL - Deprecation of Incident Management Apps ............................................................. 595
23.26 S4TWL - Deprecation of Manage Compliance Requirement app ........................................... 596
23.27 S4TWL - Enablement for continuous delivery of listed substance content .............................. 597
23.28 S4TWL - Waste Management .................................................................................................. 599
23.29 S4TWL - Simplification in Incident Management and Risk Assessment .................................. 600
23.30 S4TWL - Removal of EHS workflows for requesting controls, impacts, agents ...................... 603
23.31 S4TWL - Responsible person for Planned Maintenance at EHS locations ............................. 605
23.32 S4TWL - Remote Integration Scenarios with EHS Health and Safety Management ............... 606
23.33 S4TWL - Conversion relevant changes in EHS ....................................................................... 608
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 11
24. Logistics – GT ............................................................................................................................ 610
24.1 S4TWL - Global Trade Management ....................................................................................... 610
24.2 S4TWL - Invoice Forecasting Worklist not available in SAP S/4HANA ................................. 612
25. Logistics - Management of Change ........................................................................................... 614
25.1 S4TWL - Simplifications in Management of Change ............................................................... 614
26. Logistics - MM-IM .................................................................................................................... 618
26.1 S4TWL - FMP in S4HANA ...................................................................................................... 618
26.2 S4TWL - Blocked customer or supplier in Inventory Management ......................................... 619
26.3 S4TWL - Document Flow Consistency for Goods Receipt to Inbound Delivery ..................... 623
26.4 S4TWL - Change in default IDoc inbound processing with message type DESADV ............. 627
26.5 S4TWL - DATA MODEL IN INVENTORY MANAGEMENT (MM-IM) .................................. 629
26.6 S4TWL - AVAILABILITY OF TRANSACTIONS IN MM-IM ................................................... 639
26.7 S4TWL - Material Ledger Obligatory for Material Valuation ................................................ 640
26.8 S4TWL - Material Valuation - Statistical moving average price ............................................ 644
26.9 S4TWL - Performance optimizations within Material Document Processing - lock beh ........ 647
26.10 S4TWL - Material Valuation Data Model Simplification in S/4HANA 1610 and Higher ....... 653
26.11 S4TWL - Goods movements without exclusive locking by material valuation......................... 655
26.12 S4TWL - CWM in SAP S/4HANA ............................................................................................ 657
27. Logistics – PLM ......................................................................................................................... 664
27.1 S4TWL - Engineering Desktop (EDesk) .................................................................................. 664
27.2 S4TWL - DMS - STEP Support ................................................................................................ 665
27.3 S4TWL - DMS Documents@WEB ........................................................................................... 666
27.4 S4TWL - Variant Configuration .............................................................................................. 667
27.5 S4TWL - Classification ............................................................................................................ 669
27.6 S4TWL - IPPE-BOM Converter .............................................................................................. 673
27.7 S4TWL - BOM, Routing, Production Version ......................................................................... 674
27.8 S4TWL - SAP PLM Recipe Development ................................................................................ 676
27.9 S4TWL - Engineering Change Management ECR/ECO .......................................................... 677
27.10 S4TWL - Enterprise Search in SAP Product Lifecycle Management (SAP PLM) ................... 679
27.11 S4TWL - Engineering Change Management Change Sequence Graph .................................. 681
27.12 S4TWL - Engineering Workbench ........................................................................................... 682
27.13 S4TWL - Collaborative Engineering ....................................................................................... 683
27.14 S4TWL - iPPE Time Analysis .................................................................................................. 684
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 12
27.15 S4TWL - Routing Component Assignment ............................................................................... 685
27.16 S4TWL - Release Management Framework ............................................................................ 686
27.17 S4TWL - Engineering Record .................................................................................................. 687
27.18 S4TWL - PLM Labeling Usage ................................................................................................ 690
27.19 S4TWL - Engineering Record with LAMA............................................................................... 691
27.20 S4TWL - Assemblies ................................................................................................................ 692
27.21 S4TWL - New Access Control Management ............................................................................ 693
27.22 S4TWL - Process Route in PLM Web UI ................................................................................. 694
27.23 S4TWL - Classification - Data Cleanup before Migration ...................................................... 695
27.24 S4TWL - Behavior change for AVC Sales Order (SET) scenario configuration models ......... 696
27.25 S4TWL - Project Management Integration with DMS ............................................................. 700
27.26 S4TWL - Product Designer Workbench .................................................................................. 701
27.27 S4TWL - cFolders .................................................................................................................... 702
27.28 S4TWL - cDesk ........................................................................................................................ 703
27.29 S4TWL - Recipe Management ................................................................................................. 705
27.30 S4TWL - Engineering Client Viewer (ECL) ............................................................................ 707
27.31 S4TWL - Easy Document Management (Easy DMS)............................................................... 708
28. Logistics – PM ........................................................................................................................... 710
28.1 S4TWL - Object List Number Field Length Extension ............................................................ 710
28.2 S4TWL - Obsolete predictive scenarios in PM ........................................................................ 711
28.3 S4TWL - Obsolete POWL Applications in Maintenance Management .................................. 712
28.4 S4TWL - LIS in EAM ............................................................................................................... 713
28.5 S4TWL - Download Data in MS Access out of List ................................................................. 715
28.6 S4TWL - Scheduling of Maintenance Plan .............................................................................. 716
28.7 S4TWL - Mobile Asset Management (MAM) ........................................................................... 717
28.8 S4TWL - Batch Input for Enterprise Asset Management (EAM) ............................................. 717
28.9 S4TWL - Changes In List Reports For Order and Notification ............................................... 719
28.10 S4TWL - WebDynpro Application for Maintenance Planner (<= EhP4) ............................... 720
28.11 S4TWL - Enterprise Search in EAM ........................................................................................ 722
28.12 S4TWL - SAP Graphics in EAM Transactions ........................................................................ 723
29. Logistics – PP ............................................................................................................................. 725
29.1 S4TWL - ERP Line-Balancing and Sequencing ....................................................................... 725
29.2 S4TWL - MRP in HANA .......................................................................................................... 727
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 13
29.3 S4TWL - Planning File ............................................................................................................ 733
29.4 S4TWL - Total Dependent Requirements ................................................................................ 735
29.5 S4TWL - Forecast Based Planning ......................................................................................... 736
29.6 S4TWL - Release status for different RFC function modules revoked ..................................... 738
29.7 S4TWL - Computer Aided Processing Planning (CAP) .......................................................... 740
29.8 S4TWL - ABAP-List-Based PI-Sheets ...................................................................................... 742
29.9 S4TWL - ANSI/ISA S95 Interface ............................................................................................ 743
29.10 S4TWL - PP-MRP - Subcontracting ........................................................................................ 744
29.11 S4TWL - Electronic Records ................................................................................................... 746
29.12 S4TWL - Downtimes Functionality.......................................................................................... 750
29.13 S4TWL - MiniApps PP-PI ....................................................................................................... 750
29.14 S4TWL - Process Data Evaluation (PP-PI-PEV) .................................................................... 751
29.15 S4TWL - Campaign Weighing and Dispensing ....................................................................... 752
29.16 S4TWL - Production Campaign (ERP) ................................................................................... 753
29.17 S4TWL - Electronic Batch Record........................................................................................... 754
29.18 S4TWL - Process Messages ..................................................................................................... 760
29.19 S4TWL - Control Recipes/Instructions .................................................................................... 763
29.20 S4TWL - Storage Location MRP ............................................................................................. 766
29.21 S4TWL - Process Operator Cockpits ....................................................................................... 768
29.22 S4TWL - Material Identification/Reconciliation ..................................................................... 773
29.23 S4TWL - Flow Manufacturing ................................................................................................. 780
29.24 S4TWL - Process Flow Scheduling (PP-PI) ............................................................................ 782
29.25 S4TWL - Rate and Rough-Cut Planning .................................................................................. 783
29.26 S4TWL - Planning Horizon ..................................................................................................... 785
29.27 S4TWL - Batch History ............................................................................................................ 786
29.28 S4TWL - Selected Business Functions in PP area ................................................................... 787
29.29 S4TWL - Time Streams Usage in Kanban ............................................................................... 790
29.30 S4TWL - Graphical display of available quantity in MRP evaluations ................................... 791
29.31 S4TWL - External Interfaces in PP ......................................................................................... 792
29.32 S4TWL - Data Destruction in Kanban .................................................................................... 794
29.33 S4TWL - Scheduling beyond year 2048 ................................................................................... 794
29.34 S4TWL - Graphical Planning Table ........................................................................................ 796
29.35 S4TWL - Logistic Information System in PP ........................................................................... 797
29.36 S4TWL - Sales and Operation Planning .................................................................................. 800
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 14
29.37 S4TWL - Simplified Sourcing .................................................................................................. 802
29.38 S4TWL - Browser-based Process Instruction-Sheets/Electronic Work Instructions ............... 809
29.39 S4TWL - Internet Kanban ........................................................................................................ 817
30. Logistics – PP/DS ....................................................................................................................... 819
30.1 S4TWL - Performance optimizations for publication of planning orders ............................... 819
31. Logistics – PS ............................................................................................................................. 822
31.1 S4TWL - Project Claim Factsheet ........................................................................................... 822
31.2 S4TWL - Selected Project System Interfaces ........................................................................... 823
31.3 S4TWL - Construction Progress Report and Valuation .......................................................... 824
31.4 S4TWL - Project System ITS Services ..................................................................................... 825
31.5 S4TWL - Selected PS Business Function Capabilities ............................................................. 825
31.6 S4TWL - Selected Project System BAPIs ................................................................................. 832
31.7 S4TWL - Handling Large Projects Business Functions .......................................................... 833
31.8 S4TWL - Hierarchy Graphics in Project Systems ................................................................... 834
31.9 S4TWL - Project System Analytical Apps ................................................................................ 835
31.10 S4TWL - Project System - Compatibility Scope ...................................................................... 837
31.11 S4TWL- Deprecation of Project Cost Reports - Overview and Line Items ............................. 839
31.12 S4TWL - Navigation to Project Builder instead of special maintenance functions ................. 840
31.13 S4TWL - Production Resources and Tools functions for projects ........................................... 841
31.14 S4TWL - Specific PS archiving transactions ........................................................................... 842
31.15 S4TWL - Project texts (PS texts).............................................................................................. 844
32. Logistics – PSS ........................................................................................................................... 846
32.1 S4TWL - PS&S SARA Reports ................................................................................................. 846
32.2 S4TWL - Substance Volume Tracking Selection Criteria based on tables VBUK and VB ...... 846
32.3 S4TWL - Simplification in Product Compliance for Discrete Industry ................................... 848
32.4 S4TWL - Replacement of Event Type Linkages ....................................................................... 850
32.5 S4TWL - QM Interface ............................................................................................................ 853
32.6 S4TWL - PS&S Enterprise Search Model ............................................................................... 854
32.7 S4TWL - Hazardous Substance Management .......................................................................... 855
32.8 S4TWL - Add-On: SAP Product and REACH Compliance (SPRC) ........................................ 856
32.9 S4TWL - Add-On: EHS Web-Interface .................................................................................... 858
32.10 S4TWL - Add-On: Genifix (Labelling solution) ....................................................................... 859
32.11 S4TWL - BW Extractors for Dangerous Goods Management and Specification Managemen 860
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 15
33. Logistics – QM ........................................................................................................................... 861
33.1 S4TWL - Quality Management Information System (QMIS) ................................................... 861
33.2 S4TWL - Redundant Transactions in QM ................................................................................ 863
33.3 S4TWL - Removed Navigation to Transactions for Evaluations in QM .................................. 864
33.4 S4TWL - Authorization Objects in QM .................................................................................... 865
33.5 S4TWL - Results Recording ..................................................................................................... 868
33.6 S4TWL - ITS services in QM ................................................................................................... 869
33.7 S4TWL - QM WEB Workplace (MiniApps) based on ITS Services ......................................... 871
34. Logistics – TRA ......................................................................................................................... 873
34.1 S4TWL - Transportation (LE-TRA) ......................................................................................... 873
35. Logistics – WM .......................................................................................................................... 876
35.1 S4TWL - Task & Resource Management ................................................................................. 876
35.2 S4TWL - Warehouse Control Interface ................................................................................... 877
35.3 S4TWL - Decentral WM .......................................................................................................... 878
35.4 S4TWL - Wave Management ................................................................................................... 880
35.5 S4TWL - Cross Docking .......................................................................................................... 881
35.6 S4TWL - Yard Management .................................................................................................... 882
35.7 S4TWL - Value Added Services ............................................................................................... 884
36. Portfolio and Project Management (PPM) ............................................................................... 886
36.1 S4TWL - Web Dynpro Applications for Resource Maintenance in SAP Portfolio and Pr ...... 886
36.2 S4TWL - Workforce Deployment (WFD) integration in SAP Portfolio and Project Mana ..... 887
36.3 S4TWL - Integration to SAP cFolders in SAP Portfolio and Project Management for ........... 888
36.4 S4TWL - KM Documents in SAP Portfolio and Project Management for SAP S/4HANA....... 889
36.5 S4TWL - SRM Integration in SAP Portfolio and Project Management for SAP S/4HANA ..... 890
36.6 S4TWL - cFolders not available anymore in SAP Portfolio and Project Management f ........ 891
36.7 S4TWL - Global Settings in SAP Portfolio and Project Management for SAP S/4HANA ....... 893
36.8 S4TWL - Fiori apps of UI FOR SAP PORTF PROJ MGMT 6.0 in SAP Portfolio and Projec 903
36.9 S4TWL - Portfolio Structure Graphic in SAP Portfolio and Project Management for ........... 904
36.10 S4TWL - SAP Smart Forms in SAP Portfolio and Project Management for SAP S/4HANA ... 905
36.11 S4TWL - Resource Management Web Dynpro Views in SAP Portfolio and Project Manage . 906
36.12 S4TWL - WebDAV and EasyDMS Integration in SAP Portfolio and Project Management f .. 907
36.13 S4TWL - SAP Portal Integration in SAP Portfolio and Project Management for SAP S ........ 908
36.14 S4TWL - cRoom Integration in SAP Portfolio and Project Management for SAP S/4HAN .... 909
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 16
36.15 S4TWL - xPD Integration in SAP Portfolio and Project Management for SAP S/4HANA ..... 910
36.16 S4TWL - Xcelsius Integration in SAP Portfolio and Project Management for SAP S/4 .......... 911
36.17 S4TWL - SAP BusinessObjects Explorer Integration in SAP EPPM....................................... 911
36.18 S4TWL - Project simulation in SAP Portfolio and Project Management for SAP S/4H ......... 912
36.19 S4TWL - Deletion of obsolete packages in EPPM .................................................................. 913
36.20 S4TWL - Business Partner in SAP Portfolio and Project Management for SAP S/4HANA .... 914
36.21 S4TWL - Simplified ACLs (Access Control Lists) concept in SAP Portfolio and Proj ............ 916
36.22 S4TWL - Handling of actual date in scheduling (EPPM) ....................................................... 918
36.23 S4TWL - UI5 GANTT replacing JGANTT ............................................................................... 919
36.24 S4TWL - Object links to marketing campains in SAP CRM .................................................... 921
36.25 S4TWL - Changes compared to older releases than SAP Port. and Proj. Mngt. 6.1 .............. 922
36.26 S4TWL - Control Plans in SAP Portfolio and Project Management for SAP S/4HANA ......... 923
36.27 S4TWL - HTTP-Based Document Management in SAP Portfolio and Project Management f 924
36.28 S4TWL - Object Links to SAP Environmental Compliance in SAP Portfolio and Projec ....... 925
36.29 S4TWL - Microsoft Project Import/Export in SAP Portfolio and Project Management ......... 926
37. Procurement .............................................................................................................................. 928
37.1 S4TWL - MM-PUR WebDynpro Applications ......................................................................... 928
37.2 S4TWL - Classic MM-PUR GUI Transactions replacement ................................................... 930
37.3 S4TWL - Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes ..... 931
37.4 S4TWL - Supplier Distribution via MDG-S ............................................................................. 933
37.5 S4TWL - Authorization Concept for Supplier Invoice ............................................................. 934
37.6 S4TWL - Foreign Trade within SAP S/4HANA Procurement .................................................. 935
37.7 S4TWL - RFQ Simplified Transaction ..................................................................................... 946
37.8 S4TWL - Webdynpro Applications for Purchase Requisition Transfer from ERP to SRM ...... 948
37.9 S4TWL - Co-Deployment of SAP SRM .................................................................................... 949
37.10 S4TWL - Supplier Invoice New Archiving ............................................................................... 950
37.11 S4TWL - New Customizing for Exchange Rate Difference Handling ...................................... 951
37.12 S4TWL - Deprecation of Fiori Apps and Machine Learning Scenarios .................................. 952
37.13 S4TWL - CI Include Conflicts in EKKO_INCL_EEW_PS and EKPO_INCL_EEW_PS ......... 954
37.14 S4TWL - Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC) ....................... 957
37.15 S4TWL - Vendor evaluation based on LIS ............................................................................... 958
37.16 S4TWL - ERP Shopping Cart .................................................................................................. 960
37.17 S4TWL - Internet Application Components (IAC) ................................................................... 962
37.18 S4TWL - MDM Catalog........................................................................................................... 963
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 17
37.19 S4TWL - Pricing Data Model Simplification........................................................................... 964
37.20 S4TWL - Output Management Adoption in Purchase Order ................................................... 965
37.21 S4TWL - CI Include Conflicts in Table MMPUR_ANA_E ...................................................... 966
38. Sales & Distribution .................................................................................................................. 968
38.1 S4TWL - Business Role Internal Sales Representative ............................................................ 968
38.2 S4TWL - Webshops by Internet Sales or Web Channel Experience Management .................. 969
38.3 S4TWL - Sales Activities .......................................................................................................... 971
38.4 S4TWL - Billing Document Output Management .................................................................... 975
38.5 S4TWL - SD Rebate Processing replaced by Settlement Management ................................... 976
38.6 S4TWL -Miscellaneous minor functionalities in SD Area ....................................................... 978
38.7 S4TWL - SD Complaint Handling ........................................................................................... 979
38.8 S4TWL - SD Simplified Data Models ...................................................................................... 980
38.9 S4TWL - VBFA - Indirect Docflow Relationships ................................................................... 983
38.10 S4TWL - Data Model Changes in SD Pricing ......................................................................... 985
38.11 S4TWL - Foreign Trade........................................................................................................... 990
38.12 S4TWL - Credit Management ................................................................................................ 1003
38.13 S4TWL - ERP SD Revenue Recognition ................................................................................ 1008
38.14 S4TWL - Optimization of SD Rebate Processing for TPM Customers .................................. 1010
38.15 S4TWL - Simplification in SD Analytics ................................................................................ 1012
38.16 S4TWL - Advanced Order Processing and Billing for Contractors to the public sect .......... 1014
38.17 S4TWL - Operational Data Provisioning .............................................................................. 1016
39. Service Operations & Processes .............................................................................................. 1018
39.1 Industry functionality from SAP CRM which is not supported in S/4HANA ......................... 1018
40. Transportation Management .................................................................................................. 1020
40.1 S4TWL - Simplified customizing of Transportation Manangement (TM) integration ........... 1020
40.2 S4TWL - Forwarding Settlement Document Transfer in TM................................................. 1022
40.3 S4TWL - Location Geo-Coding Adjustments ......................................................................... 1026
41. Globalization Financials .......................................................................................................... 1030
41.1 S4TWL - Globalization – Financials ..................................................................................... 1030
41.2 S4TWL - Annexing Solution for Israel ................................................................................... 1030
41.3 S4TWL - Funds Management Portugal ................................................................................. 1032
41.4 S4TWL - Golden Tax Interface for China ............................................................................. 1034
41.5 S4TWL - Replacement of legal reports with SAP S/4HANA ACR ......................................... 1035
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 18
41.6 S4TWL - Add-on for Polish SAF-T regulatory requirements ................................................ 1036
41.7 S4TWL - Russia Manage Additional Payment Attributes app ............................................... 1039
41.8 S4TWL - SAF-T RO: Replacement of ABAP Report Solution with DRC Solution ................. 1042
42. Globalization Logistics ............................................................................................................ 1044
42.1 S4TWL - Globalization – Logistics ........................................................................................ 1044
42.2 S4TWL - eDocument Framework Migration to SAP S/4HANA ............................................. 1045
43. Industry – Cross ...................................................................................................................... 1047
43.1 S4TWL - BRIM - Billing of Event Detail Records (EDR) ...................................................... 1047
43.2 S4TWL - BRIM - Common Object Layer (COL) ................................................................... 1048
43.3 S4TWL - BRIM - Integration with FSCM Biller Direct (FI-CA) ........................................... 1049
43.4 S4TWL - BRIM - Solution Sales and Billing .......................................................................... 1050
43.5 S4TWL - BRIM – Immediate Master Data Replication to SAP Convergent Charging ......... 1052
44. Industry Banking ..................................................................................................................... 1056
44.1 S4TWL - Business User integration of BPs with user name and personal number ............... 1056
44.2 S4TWL - FSBP Table Additional Partner Numbers (BPID001) obsolete ............................. 1061
44.3 S4TWL - SEM Banking .......................................................................................................... 1062
44.4 S4TWL - CML-specific functions with regard to collaterals and collateral objects ............. 1064
44.5 S4TWL - Deprecation of app F3987...................................................................................... 1066
45. Industry Beverage ................................................................................................................... 1068
45.1 S4TWL - IS-Beverage (Excise Duty) ..................................................................................... 1068
45.2 S4TWL - IS-Beverage (Sales Returns) ................................................................................... 1069
45.3 S4TWL - IS-Beverage (Pendulum List) ................................................................................. 1070
46. Defense&Security .................................................................................................................... 1071
46.1 S4TWL - DFPS eSOA services .............................................................................................. 1071
46.2 S4TWL - BI content, Datasources and extractors for DFPS ................................................. 1072
46.3 S4TWL - Integration of DFPS with Investigative Case Management (ICM) ........................ 1074
46.4 S4TWL - Integration of DFPS with Environmental Compliance ........................................... 1075
46.5 S4TWL - Force organization, personnel and sustainment for DFPS .................................... 1076
47. Industry DIMP - Aerospace & Defense................................................................................... 1078
47.1 S4TWL - Collective Processing Pegging ............................................................................... 1078
47.2 S4TWL - Actual labor and costing ........................................................................................ 1079
47.3 S4TWL - Renovation of Grouping, Pegging and Distribution Functionality ........................ 1080
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 19
47.4 S4TWL - Cost Distribution Processing ................................................................................. 1086
47.5 S4TWL - Manufacturer Part Number .................................................................................... 1087
47.6 S4TWL - Flight Scheduling ................................................................................................... 1093
47.7 S4TWL - Enhancements Actual Labour Costing / Time Recording ....................................... 1094
47.8 S4TWL - Enhancements Subcontracting Special Stock Types Not Available ........................ 1095
47.9 S4TWL - AECMA SPEC 2000M Military Version................................................................. 1096
47.10 S4TWL - Obsolete transactions and Enhancements in GPD ................................................. 1096
48. Industry DIMP – Automotive ................................................................................................. 1100
48.1 S4TWL - Vehicle search using SAP TREX as external search engine ................................... 1100
48.2 S4TWL - Handling Unit Management - Obsolete Transactions ............................................ 1101
48.3 S4TWL - JIT Inbound ............................................................................................................ 1106
48.4 S4TWL - JIT Outbound .......................................................................................................... 1109
48.5 S4TWL - Self-Billing Cockpit ................................................................................................ 1112
48.6 S4TWL - Sales Scheduling Agreement with TAM processing ................................................ 1116
48.7 S4TWL - Returnable Packaging Logistics ............................................................................. 1119
48.8 S4TWL - Tracking Inbound ................................................................................................... 1121
48.9 S4TWL - Supplier Workplace ................................................................................................ 1123
48.10 S4TWL - External Service Providers ..................................................................................... 1125
48.11 S4TWL - Cross-System Transit between Two Plants ............................................................. 1127
48.12 S4TWL - Long Material Number ........................................................................................... 1129
48.13 S4TWL - Material Version..................................................................................................... 1131
48.14 S4TWL - Planning Regular Route Shipments ........................................................................ 1134
48.15 S4TWL - BSP based Dealer Portal........................................................................................ 1135
48.16 S4TWL - Web Dynpro based Dealer Portal .......................................................................... 1138
49. Industry DIMP - EC&O .......................................................................................................... 1140
49.1 S4TWL - Obsolete BAPIS of Bill of Services (BOS) .............................................................. 1140
49.2 S4TWL - BOS Cost Transfer to PS removed ......................................................................... 1141
49.3 S4TWL - ZDEP ETM CATS package .................................................................................... 1142
49.4 S4TWL - ETM General .......................................................................................................... 1144
49.5 S4TWL - ETM Tables obsolete .............................................................................................. 1146
49.6 S4TWL - REAL ESTATE SALES (HOMEBUILDING) .......................................................... 1147
49.7 S4TWL Business Package for Subcontracting (EC&O) ........................................................ 1148
50. Industry DIMP - High Tec ...................................................................................................... 1150
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 20
50.1 S4TWL - Manufacturing Execution Systems.......................................................................... 1150
50.2 S4TWL - RosettaNet .............................................................................................................. 1151
50.3 S4TWL - Software License Management ............................................................................... 1152
50.4 S4TWL - Installed Base Management for IS-SW ................................................................... 1153
50.5 S4TWL - Contract Management Enhancements .................................................................... 1154
50.6 S4TWL - Billing Process Enhancements ............................................................................... 1155
50.7 S4TWL - Software Maintenance Processing ......................................................................... 1156
50.8 S4TWL - User Exits in DRM ................................................................................................. 1157
50.9 S4TWL - Condition Technique in DRM: Rule Configuration ................................................ 1157
50.10 S4TWL - Manufacturer/Supplier Processes .......................................................................... 1159
50.11 S4TWL - Distributor/Reseller Processes ............................................................................... 1160
51. Industry DIMP – Mill .............................................................................................................. 1163
51.1 S4TWL - Non ferrous metal processing ................................................................................. 1163
51.2 S4TWL - Sales Order Versions .............................................................................................. 1164
51.3 S4TWL - Stock Overview and Object Search by Characteristics .......................................... 1165
51.4 S4TWL - Mill specific enhancements to scheduling PRTs ..................................................... 1167
51.5 S4TWL - Process batch ......................................................................................................... 1168
51.6 S4TWL - Fast entry of characteristic values in trading contract .......................................... 1170
51.7 S4TWL - Selection by characteristics in mass processing of orders ..................................... 1171
51.8 S4TWL - Fast entry of characteristic values in sales document ............................................ 1172
52. Healthcare (IS-H) .................................................................................................................... 1174
52.1 S4TWL - SAP Patient Management (IS-H) is not available in SAP S/4HANA ...................... 1174
53. Industry Insurance .................................................................................................................. 1176
53.1 S4TWL - FS-RI - Deletion of obsolete packages ................................................................... 1176
53.2 S4TWL - Technical changes to Statutory Reporting Tables .................................................. 1177
53.3 S4TWL - FS-RI - Replacement of msg.PM Connection by SAP Standard ............................. 1177
53.4 S4TWL - FS-RI - Redesign Data Access Framework ............................................................ 1181
53.5 S4TWL - Deletion of obsolete objects (Compat-Packages) ................................................... 1208
53.6 S4TWL - FS-RI - Deletion of LSMW Integration ................................................................... 1210
53.7 S4TWL - FS-RI - Replacement of a Semantic Object in Fiori App and Transaction ............. 1211
53.8 S4TWL - FS-RI - Ensuring the functionality of the Extension Service .................................. 1212
53.9 S4TWL - FS-RI deletion of obsolete functionality for FI-AR ................................................. 1216
53.10 S4TWL - FS-RI - Deletion and Replacement of Obsolete CDS Views ................................... 1217
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 21
53.11 S4TWL - FS-RI Deletion of obsolete functionality for FS-RI-B ............................................ 1220
53.12 S4TWL - FS-RI – Deprecation of RAM APIs with SAP S/4HANA 2021................................ 1222
53.13 S4TWL - FS-RI - Interface adaptation in the claim ............................................................... 1224
53.14 S4TWL - FS-RI – Replacement of old OA Accounting Reports ............................................. 1230
53.15 S4TWL - FS-RI - Interface adaption of the navigation tree................................................... 1232
53.16 S4TWL - FS-RI – Deprecation of RAM APIs with SAP S/4HANA 2022................................ 1233
53.17 S4TWL - FS-RI - Correction of misleading method names ................................................... 1235
53.18 S4TWL - FS-RI - Deprecation of RAM APIs with SAP S/4HANA 2023 ................................ 1237
53.19 S4TWL - FS-RI – Changing “Remote-Enabled Module” to “Normal Function Module” .... 1238
53.20 S4TWL - FS-RI - Renaming of a field in PMQ ...................................................................... 1240
53.21 S4TWL - FS-RI - Deletion of obsolete Claim Methods .......................................................... 1241
53.22 S4TWL - Insurance localization for Russia - deprecation ..................................................... 1243
53.23 S4TWL - Insurance localization for Turkey........................................................................... 1248
54. Industry Media ........................................................................................................................ 1251
54.1 S4TWL - SAP Media availability in SAP S/4HANA .............................................................. 1251
54.2 S4TWL - Media Product Master ............................................................................................ 1252
55. Industry Oil ............................................................................................................................. 1254
55.1 S4TWL- ACM - Simplification for Contract Approval .......................................................... 1254
55.2 S4TWL- ACM: Simplification for Pre-payment and External Interfacing ............................ 1256
55.3 S4TWL - ACM: Simplification of Cross Topics ..................................................................... 1257
55.4 S4TWL - ACM: Simplification of Application Document Batch Split Process ...................... 1258
55.5 S4TWL - ACM Temporary Lots for Draft Contracts ............................................................. 1259
55.6 S4TWL - Handling Oil & Gas obsolete t-codes Oil .............................................................. 1261
55.7 S4TWL - Optimization in Oil & Gas - TD module for STO and sales order with POD b ..... 1263
55.8 S4TWL - Data Model in Oil & Gas Inventory management .................................................. 1264
55.9 S4TWL - Improved update logic for excise duty related movements in MBEW .................... 1272
55.10 S4TWL - UoM Group Extension Improvements .................................................................... 1273
55.11 S4TWL - Extended IS-OIL Customizing ................................................................................ 1275
55.12 S4TWL - IS-OIL - Commodity Management Integration ....................................................... 1276
55.13 S4TWL - IS-OIL Data Archiving For Exchanges .................................................................. 1277
55.14 S4TWL – iTSW available only for ACM customers ............................................................... 1278
55.15 S4TWL - Service Station Retailing ........................................................................................ 1279
55.16 S4TWL – Shipment Cost Processing ..................................................................................... 1280
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 22
55.17 S4TWL - Optimization in Oil&Gas - Inter company sales - Cross border excise duty ......... 1282
55.18 S4TWL – Freight Costs ......................................................................................................... 1284
55.19 S4TWL - Remote Logistics Management ............................................................................... 1286
55.20 S4TWL - IS-OIL Proper sign operation for ACDOCA .......................................................... 1287
55.21 S4TWL - Unit of Measure (UoM) Group enahncement ......................................................... 1289
55.22 S4TWL - eNetting Deprecation ............................................................................................. 1292
55.23 S4TWL - Dynamic Scheduling deprecation ........................................................................... 1293
55.24 S4TWL - Financial Based netting deprecation ...................................................................... 1294
55.25 S4TWL - Oil & Gas inconsistency reports deprecation ........................................................ 1295
56. Industry Oil – OGSD ............................................................................................................... 1299
56.1 S4TWL - OGSD - Classic Data Collation ............................................................................. 1299
56.2 S4TWL - OGSD - Classic OGSD Interfaces .......................................................................... 1301
56.3 S4TWL - OGSD - Sales Logistics Cockpit ............................................................................. 1303
56.4 S4TWL - OGSD - Liquid Petrol Gas ..................................................................................... 1305
56.5 S4TWL - OGSD - Infosheet ................................................................................................... 1307
56.6 S4TWL - OGSD - Best Buy .................................................................................................... 1308
56.7 S4TWL - OGSD - Formroutines Telesales ............................................................................ 1310
56.8 S4TWL - OGSD - Intercompany Processes ........................................................................... 1312
56.9 S4TWL - OGSD - Classic Method Framework ...................................................................... 1313
56.10 S4TWL - OGSD - Old Notes .................................................................................................. 1315
57. Industry Oil – OTAS ............................................................................................................... 1317
57.1 S4TWL - OTAS - Integrated Dispatch Managment ............................................................... 1317
57.2 S4TWL - OTAS - Integrated Petroleum Report ..................................................................... 1319
57.3 S4TWL - OTAS - Sales Activities ........................................................................................... 1320
58. Industry Public Sector ............................................................................................................. 1322
58.1 S4TWL - Functionality German Local Authorities ................................................................ 1322
58.2 S4TWL - Authorization in Funds Management ..................................................................... 1323
58.3 S4TWL - Public Sector localization for Hungary Deprecation ............................................. 1325
58.4 S4TWL - Former Budgeting System (FBS) in Funds Management ....................................... 1326
58.5 S4TWL - Functionality for FACTS I and FACTS II (Federal Agencies Centralized Tri ....... 1329
58.6 S4TWL - Expenditure Certification ....................................................................................... 1331
58.7 S4TWL - Specific fields on Business Partner ........................................................................ 1332
58.8 S4TWL - Fund Accounting based on Special Ledger ............................................................ 1334
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 23
58.9 S4TWL - Data Structure changes in BCS .............................................................................. 1336
58.10 S4TWL - Funds Management Dimensions as part of the Universal Journal ........................ 1337
58.11 S4TWL - Functionality for BCS Multi-level Budget Structure .............................................. 1339
58.12 S4TWL - Functionality Average Daily Balance-based Distribution ..................................... 1341
59. Industry Retail & Fashion ....................................................................................................... 1344
59.1 S4TWL - Retail Power Lists .................................................................................................. 1344
59.2 S4TWL - Retail Closed BW Scenarios ................................................................................... 1344
59.3 S4TWL - Retail Markdown Plan ............................................................................................ 1345
59.4 S4TWL - Retail Bonus Buy .................................................................................................... 1346
59.5 S4TWL - Retail Sales Forecasting ......................................................................................... 1347
59.6 S4TWL - Retail Order Optimizing: Load Build, Investment Buy ........................................... 1349
59.7 S4TWL - Retail Rapid Replenishment ................................................................................... 1350
59.8 S4TWL - Automatic Document Adjustment ........................................................................... 1350
59.9 S4TWL - Retail Additionals ................................................................................................... 1353
59.10 S4TWL - Article Discontinuation .......................................................................................... 1354
59.11 S4TWL - GDS simplified Inbound Price Catalog Interface................................................... 1355
59.12 S4TWL - Business Partner in Site Master ............................................................................. 1356
59.13 S4TWL - Logistical Variant ................................................................................................... 1357
59.14 S4TWL - Article Hierarchy .................................................................................................... 1358
59.15 S4TWL - Market Basket Calculation ..................................................................................... 1359
59.16 S4TWL - Merchandise and Assortment Planning (ERP based) ............................................. 1360
59.17 S4TWL - Retail Method of Accounting .................................................................................. 1362
59.18 S4TWL - Fresh Item Procurement ......................................................................................... 1363
59.19 S4TWL - Retail Ledger / Profit Center Analytics .................................................................. 1364
59.20 S4TWL - Goods Receipt Capacity Check .............................................................................. 1365
59.21 S4TWL - Online Store ............................................................................................................ 1366
59.22 S4TWL - Generic Article Harmonization .............................................................................. 1367
59.23 S4TWL - Retail Labeling ....................................................................................................... 1369
59.24 S4TWL - Seasonal Procurement ............................................................................................ 1370
59.25 S4TWL - Replenishment ........................................................................................................ 1371
59.26 S4TWL - Retail Information System ...................................................................................... 1372
59.27 S4TWL - SAP Retail Store ..................................................................................................... 1375
59.28 S4TWL - Retail iViews ........................................................................................................... 1379
59.29 S4TWL - Prepack Allocation Planning ................................................................................. 1380
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 24
59.30 S4TWL - Assortment List ....................................................................................................... 1381
59.31 S4TWL - In-store food production integration ...................................................................... 1382
59.32 S4TWL - PRICAT Outbound ................................................................................................. 1383
59.33 S4TWL - Retail Business Function Harmonization ............................................................... 1384
59.34 S4TWL - Retail Obsolete Transactions ................................................................................. 1385
59.35 S4TWL - Value and Quota Scales.......................................................................................... 1390
59.36 S4TWL - AIN ......................................................................................................................... 1391
59.37 S4TWL - SAP Smart Business for Retail Promotion Execution ............................................. 1392
59.38 S4TWL - Retail Factsheets .................................................................................................... 1393
59.39 S4TWL - Retail Short Text Replacement ............................................................................... 1394
59.40 S4TWL - Subsequent Settlement - Vendor Rebate Arrangements .......................................... 1394
59.41 S4TWL - Segmentation (from 1809 onwards) ....................................................................... 1397
59.42 S4TWL - Allocation Run Master Data ................................................................................... 1399
59.43 S4TWL - Fashion Contract Disablement ............................................................................... 1401
59.44 S4TWL - Allocation Run ........................................................................................................ 1402
59.45 S4TWL - Segment Field Length Extension ............................................................................ 1405
59.46 S4TWL - Fashion Functionality ............................................................................................ 1406
59.47 S4TWL - Season Active in Inventory Management ................................................................ 1409
59.48 S4TWL - Segmentation (Upgrade SAP S/4HANA 1709 to 1809) .......................................... 1410
59.49 S4TWL - Conversion of Season Master Data to SAP S/4HANA 1809 ................................... 1411
59.50 S4TWL - Supply Assignment Preview (upgrade to SAP S/4HANA 1809).............................. 1414
59.51 S4TWL - Vendor Characteristic Values ................................................................................ 1415
59.52 S4TWL - Lean SAF Interface ................................................................................................. 1416
59.53 S4TWL - BAdI for Article Reference Handling ..................................................................... 1417
59.54 S4TWL - Retail Store Fiori App ............................................................................................ 1418
59.55 S4TWL - SAP AFS Integration .............................................................................................. 1419
59.56 S4TWL - POS Outbound via Idoc WP_PLU.......................................................................... 1420
59.57 S4TWL - Valuation in Retail .................................................................................................. 1421
59.58 S4TWL - Retail Demand Management Integration ............................................................... 1422
60. Industry Telecommunications ................................................................................................. 1424
60.1 S4TWL - Lock and unlock services using IST_TDATA .......................................................... 1424
60.2 S4TWL - PORTAL ROLES FOR NETWORK LIFECYCLE MANAGEMENT (NLM) ........... 1425
61. Industry Utilities ...................................................................................................................... 1427
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 25
61.1 S4TWL - CVI Integration for SAP ISU .................................................................................. 1427
61.2 S4TWL - Multichannel Foundation for Utilities .................................................................... 1429
61.3 S4TWL - SAP Waste and Recycling: Activation .................................................................... 1430
61.4 S4TWL - IDE Outgoing Payment Processing ........................................................................ 1432
61.5 S4TWL - SAP Waste and Recycling: Service orders in EWACONTS .................................... 1433
61.6 S4TWL - Late Payment Change ............................................................................................ 1434
61.7 S4TWL - IS-Utilities Settlement Control ............................................................................... 1435
61.8 S4TWL - Maintenance of non-billable Point of Delivery services ........................................ 1436
61.9 S4TWL - Deprecation of transaction EA22_TOOL ............................................................... 1437
61.10 S4TWL - Refund Claim for Germany .................................................................................... 1438
61.11 S4TWL - Monitoring Profile Value Import ............................................................................ 1440
61.12 S4TWL - Prepayment solution for the utilities industry ........................................................ 1440
61.13 S4TWL - Utilities Customer Electronic Services (UCES) ..................................................... 1441
61.14 S4TWL - IS-U Stock, Transaction and Master Data Statistics (UIS, BW)............................. 1443
61.15 S4TWL - IS-U Sales Processing ............................................................................................ 1445
61.16 S4TWL - Marketing - IS-U Loyalty Program ........................................................................ 1446
61.17 S4TWL - Front Office (EC20) and CIC0 Configuration ....................................................... 1446
61.18 S4TWL - GIS Business Connector ......................................................................................... 1447
61.19 S4TWL - Enterprise Services for SAP for Utilities (IS-U) ..................................................... 1448
61.20 S4TWL - Central and Eastern European localization for Utility & Telco ............................ 1449
62. SAP Ariba ................................................................................................................................ 1452
62.1 S4TWL - Ariba Cloud Integration ......................................................................................... 1452
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 26
1. Introduction
SAP® S/4HANA is SAP’s next-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 limited impact
on 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 support will evolve into the digital era and provide the capabilities that
today’s unstoppable 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 27
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.
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 know 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 “Simplification List for SAP S/4HANA”. In this list we describe in
detail, on a functional level, what 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 or doing an upgrade of their
SAP S/4HANA system.
Note: The Simplification List for SAP S/4HANA is edition/release dependent. In this
collection we focus on SAP S/4HANA release 2023 Initial Shipment & Feature
Pack Stack 1 and SAP S/4HANA Cloud Private Edition release 2023 – Initial
Shipment & Feature Pack Stack 1 (for better readability we will use in this
document the term ‘SAP S/4HANA release 2023 Initial Shipment & Feature Pack
Stack 1’ for both product options.
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 code. Changes in adaption on
the customer’s side are also required.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 28
The most prominent example for which the customer needs to adapt to these SAP
S/4HANA On-premise release 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.
Customers’ expectation related to the move 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 “Simplification List for SAP S/4HANA”, SAP will provide information
about the SAP S/4HANA On-Premise delivery related simplifications for each
application/functional area. The Simplification List is a collection of individual
“Simplification Items” that focus on what needs to be considered throughout an
implementation or system conversion project from SAP ERP 6.X Customers to SAP
S/4HANA On-premise edition.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 29
Related Business Impact Note
The texts of the single simplification items are maintained in separate SAP Notes (so
called Business Impact Notes). The related Business Impact Note and the related
application component is provided per each single simplification Item within this
document.
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 2020 within SAP Help:
http://help.sap.com/s4hana
Maintenance Planner
You must 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 system
1
• Any active Business Functions in your system
2
• Industry Solutions
3
1
For a list of supported add-ons, see SAP Note 2214409
2
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 30
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 configuration file) and creates the stack configuration
file (stack.xml), which is used by SUM to convert to SAP S/4HANA On-premise edition.
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 must carry out before converting to SAP S/4HANA. The results list
the instances that need to be addressed before attempting the conversion process.
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.52 or
higher). 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 for SAP S/4HANA release 2023 Initial Shipment
& Feature Pack Stack 1 – this document
This document provides information related to the Simplification List Items which are
applicable for customers doing a system conversion from SAP ERP 6.0 on any EHP to
SAP S/4HANA release 2023 Initial Shipment or Feature Pack Stack 1, or doing an
upgrade of their SAP S/4HANA system to release 2023 Initial Shipment or Feature Pack
Stack 1.
The Simplification List Items
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) in their state at begin of general availability of this
software release.
Examples:
Simplification Item
Business Impact Note
Business Partner Approach
2265093
Material Number Field Length Extension
2267140
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 31
Note: As the content of the related Business Impact Notes may change based on new
insights at a later point of time, you should always read the related Business Impact Note
directly for the latest version in the SAP note system within the SAP Support Portal.
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, 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 this additional information in the Simplification List
document.
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 on the format and the length of this document
A webbased UI for searching and displaying Simplification Items
For accessing an up-to-date version of the Simplification List please use:
• The Simplification Item Catalog , which allows you to search and browse the full
SAP S/4HANA Simplification List.
• The SAP Readiness Check for SAP S/4HANA , which creates a customer
specific Simplification List based on usage and configuration of the customer
system.
For legacy reasons, for the time being, the Simplification List is still provided as a static
PDF document. Please note that this is not the recommended medium for consuming the
information of the Simplification List, as it does not contain all information that is
available via the Simplification Item Catalog or the SAP Readiness Check for SAP
S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 32
2. Cross Topics
2.1 ABAPTWL - Visualization of SAP Business Workflow Metadata
Application Components:BC-BMT-WFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2896183
ABAPTWL – visualization of SAP
Business Workflow metadata
Symptom
With the upgrade or system conversion to SAP S/4HANA 2020, all SWFVISU settings
are overwritten with the delivery data. Customer-specific workflow tasks may respond
differently at runtime or are not displayed as usual.
Reason and Prerequisites
For technical reasons, the delivery class of SWFVISU tables had to be changed from type
"G" to "E". With type "G", customers could only add data records delivered by SAP.
Existing settings were not overwritten. Type "E" also allows changing contents.
Solution
Description
You make the settings for displaying tasks and object types using SWFVISU or
SWFVMD1.
SWFVISU saves the settings for all clients and is used by SAP to deliver the data.
SWFVMD1 saves the data client-dependently (customizing) and should be used by
customers to enter own settings or overwrite data delivered by SAP.
Up to now, SWFVISU settings were not overwritten on the customer side. Only data that
was newly delivered by SAP was added.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 33
Business-Process-Related Information
If you have entered your own settings in SWFVISU or have adjusted delivered data, the
appearance or response of individual work items in MyInbox may change.
Required and Recommended Action(s)
Transfer your settings manually to SWFVMD1 before the upgrade or conversion.
Call transaction SWFVISU.
Call transaction SWFVMD1 in a second window.
Transfer only your changed settings to SWFVMD1 and save them.
To be on the safe side, you can export the entire content of SWFVISU to a Microsoft
Excel file. This file serves only documentation purposes and cannot be imported
automatically.
Other Terms
IMG activity: Visualization of SAP Business Workflow Metadata
2.2 ABAP4TWL - Removal of Tagging Framework
Application Components:BC-SRV-TFW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2865890
Package STFW and Sub-Packages are
missing
Symptom
The packages STFW and its sub-packages STFW_* of re-use component Tagging
Framework are missing.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 34
Tagging Framework functionality has been withdrawn.
Solution
The functionality has been withdrawn without replacement.
Other Terms
STFW
2.3 ABAP4TWL - Removal LT Check ATC Adapter
Application Components:BC-CUS-TOL-LT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2862972
Package S_CHECK_SAP_LT is missing
Symptom
Package S_CHECK_SAP_LT containing checks for consistency of long text are deleted
in ABAP Platform.
Reason and Prerequisites
The checks belong to an SAP internal use case and have been withdrawn.
Solution
There is no substitution for programmatic usage.
All checks relevant for quality assurance of ABAP programs are part of the ABAP Test
Cockpit test content.
Other Terms
CL_ATC_ADP_LT_CDOC_CHECK, CL_CHK_LT_CDOC_CHECK,
CL_ATC_ADP_LT_FIELD_CHECK, CL_CHK_LT_FIELD_CHECK
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 35
2.4 ABAP4TWL - Removal of ILM Store Monitoring GUI
Application Components:BC-ILM-STO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2926764
Packages
S_ILM_STOR_MONITOR_CSV and
S_ILM_STOR_MONITOR_GUI are
missing
Symptom
Package S_ILM_STOR_MONITOR_CSV and S_ILM_STOR_MONITOR_GUI of
solution management are missing.
Reason and Prerequisites
The functionality is replaced by other functionality in SAP Solution Manager. There is no
direct recommendation to replace the deleted code, because functionality is tailored
differently.
Solution
The functionality has been withdrawn without without replacement.
Other Terms
Package S_ILM_STOR_MONITOR_CSV
Package S_ILM_STOR_MONITOR_GUI are missing
2.5 ABAP4TWL - Removal of Drag and Relate Workplace Plugin
Application Components:CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2862992
Packages DRSCENARIOS, POR4,
PORX and PORX_COMPATIBILITY are
missing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 36
Symptom
The packages DRSCENARIOS, POR4, PORX and PORX_COMPATIBILITY of
Workplace Plug-in 3.0 and Workplace Plug-in 4.0 are missing.
Reason and Prerequisites
"Drag & Relate" functionality has been withdrawn, see also SAP Note 1829697.
Solution
The functionality has been withdrawn without replacement.
Other Terms
Business Object Type DRDYNFIELD
Function Groups SDW4, SDWP, SDWZ, SPR4, SPRT
Transaction SPO0, SPO1, SPO4, SPO4_DISP, SPO5
2.6 ABAP4TWL - Removal of Package SCMO
Application Components:SV-SMG-SDD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2926680
Package SCMO is missing
Symptom
The package SCMO covering CRM Service Data download functionality is missing
Reason and Prerequisites
The functionality is replaced by other business functionality. There is no direct
recommendation to replace the deleted code, because business functionality is tailored
differently.
Solution
The functionality has been withdrawn without replacement.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 37
Other Terms
Package SCMO, Function Group CMON
2.7 ABAP4TWL - Removal of ByDesign Config Framework Services
Application Components:BC-CFG-RT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2886479
Package C2_SERVER and its sub-
packages are missing
Symptom
The package C2_SERVER and its sub-packages are missing.
Reason and Prerequisites
Configuration framework used in older cloud products of SAP has been removed from
latest product versions of SAP CP ABAP Environment, S/4HANA CE, S/4HANA OP
and similar.
Solution
There is no replacement of the functionality.
Other Terms
C2_BCSETS, C2_CORE, C2_EXCEPTION, C2_INTERFACES, C2_SERVER,
C2_SERVER_FRAMEWORK, C2_SERVICES, SC2_IDE, SC2_IDE_APP_SYS,
SC2_MDA_GEN, SC2_META_REP, SC2_PERSISTANCE, SC2_REP_SERVICES
2.8 ABAP Test Framework: Export of ATC Results to 3rd Party Tools
Application Components:BC-DWB-TOO-ATF
Related Notes:
Note Type
Note Number
Note Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 38
Business Impact
3150564
ABAP package
SATC_CI_EXT_TOOLS_INTEGRATION
is not available in S/4HANA
Symptom
ABAP package SATC_CI_EXT_TOOLS_INTEGRATION is not available in S/4HANA.
Reason and Prerequisites
Replication of scan results from Code Vulnerability Analyzer to external targets is
discontinued.
Solution
In case you have references in your custom programs to ABAP artifacts of
package SATC_CI_EXT_TOOLS_INTEGRATION, please remove these usages before
you migrate your SAP NetWeaver based custom ABAP to S/4HANA product family.
Other Terms
Replicating CVA Results from ATC to external tools
2.9 ABAPTWL - Deprecation of Hana Rules Framework
Application Components:BC-SRV-BR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3243120
S4TWL - Deprecation of SAP Hana
Rules Framework
Symptom
You are upgrading your system to S/4HANA On-Premise 2022 FPS1 or following
releases from an older release.
Reason and Prerequisites
Deprecation of SAP HANA Rules Framework.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 39
Description
The functionality to build and to model analytical rules via BRF+ and to push these rules
down to HANA (SAP HANA Rules Framework) is deprecated now and will
be removed as a comprised component in S/4HANA On-Premise 2023.
Business Process related information
It will not be possible to create analytical functions in BRF+ projects. Already created
analytical functions will stop working with S/4HANA On-Premise 2023.
Required and Recommended Action(s)
Please carry out a manual migration or remodeling from HRF (analytical function) to
Business Rule Framework plus (BRF+).
See
also https://help.sap.com/docs/ABAP_PLATFORM_NEW/9d5c91746d2f48199bd465c3
a4973b89/9a6b67ce7c26446483af079719edf679.html?version=201809.000
Other Terms
Business Rule Framework plus (BRF+), SAP HANA Rules Framework (HRF)
2.10 ABAPTWL - No support for non simplified system flavour
Application Components:BC-ABA-LA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2656503
No support for non simplified system
flavour
Symptom
You are using profile parameter system/usage_flavor without any effect.
Reason and Prerequisites
S/4 systems only support the simplified system flavor. This includes for example that it
support Hana database only.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 40
The parameter is obsolete and shall no longer be set. The new behavior equals parameter
value SIMPLE.
Other Terms
Simplification
2.11 ABAPTWL - Cleanup of orphaned objects
Application Components:BC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2672757
Simplification of SAP_BASIS within SAP
S/4HANA 1809
Symptom
With SAP S/4HANA 1809 some technical features have been withdrawn, which are not
available for SAP S/4HANA on-premise.
Reason and Prerequisites
This SAP Note serves as a reference for SAP S/4HANA custom code checks (see SAP
Notes 2190420, 2241080) related to some obsolete and orphaned objects which were
deleted in SAP_BASIS 7.53.
The deleted objects do not belong to a specific, released functionality. Hence no
functional impact of the deletion on customers is expected.
Solution
Remove any usages of these deleted objects found by ABAP Test Cockpit in your custom
code and replace them with equivalent objects in customer namespace.
Other Terms
Conversion SAP ERP, SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 41
2.12 ABAPTWL - SSCR license key procedure is no longer supported
Application Components:BC-ABA-LA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2309060
The SSCR license key procedure is not
supported in SAP S/4 HANA
Symptom
You have developer authorization and use ABAP development tools, but the SSCR
license key request is not shown.
Reason and Prerequisites
Your system is either any of the SAP S/4HANA on premise system variants, starting with
S/4HANA 1511, or any of the SAP BW/4HANA variants. The SSCR license key
procedure is not implemented in S/4HANA or BW/4HANA.
Depending on your task and question you may proceed as outlined in the solution section
of this SAP Note.
Solution
Q1 – Is it possible to activate SSCR license key?
The SSCR license key functionality is activated and deactivated by the product.
Q2 – What feature substitute the control mechanism of SSCR Keys?
SSCR keys are no control mechanism of ABAP content. They are a licensing feature for
some older products, but not for S/4HANA.
Q3 – How is it possible to control development?
To keep control over development is multi-step approach.
You define changeability of SAP system by transaction SE06. You reach this setting by
the button "System Change Option" in the toolbar of transaction SE06.
You define client specific behavior for development by transaction SCC4 “Clients:
Overview”.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 42
Developers getting to SAP delivered artifacts, receive message TR852 or are blocked,
depending on above settings.
Furthermore, you should assign developer permissions (authorization objects
S_TRANSPRT and S_DEVELOP) carefully. I.e. tailored to the organization of your
development projects by using the authorization fields DEVCLASS, OBJTYPE,
OBJNAME, P_GROUP, and ACTVT of S_DEVELOP.
Q4 – How can I monitor, what SAP code has been changed?
Changes on SAP ABAP software can be found in transaction SE95.
Q5 – Is there a difference between modification and correction instruction?
The ABAP development tools do not distinguish the reason for change. From software
lifecycle every change on originally delivered version must be adjusted when new
software version is implemented. The reason for the change is not relevant for the
authority check.
Other Terms
SAP S/4HANA, SSCR key, Developer key, Access key, object key, modification
2.13 S4TWL - Removal of Business Application Accelerator
Application Components:BC-DB-DBI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
1694697
SAP Business Application Accelerator
powered by HANA
Symptom
You are looking for information about the SAP Business Application Accelerator
powered by HANA.
Solution
The SAP Business Application Accelerator powered by HANA has been offered as
ABAP Add-on in a restricted shipment mode until end of 2016.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 43
Starting with 2017 the Add-on is no longer available for new customers.
The Add-on is in general not supported in S/4 HANA. The existence of the Add-on is
blocking technical conversions to S/4HANA 1511 and 1610. Technical conversions to
1709 and beyond are possible.
Support for existing customers on non-4/HANA products is continued under the same
conditions as before.
To benefit from SAP HANA it is recommended to migrate the entire system to SAP
HANA, possibly with a multi node setup for optimized load distribution.
For a description of the functionality and usage of the SAP Business Application
Accelerator powered by HANA please read the attached Customer Guide.
Contents:
1 Introduction
2 Concept
2.1 Redirected Operations
2.1.1 Statements
2.1.2 Source
2.2 Context Definition
2.3 Context Evaluation at Runtime
3 Using the SAP Business Application Accelerator
3.1 Installation
3.2 General Activation
3.3 Loading Scenarios
3.3.1 Predefined SAP Scenarios
3.3.2 Custom Scenarios
3.4 Trouble Shooting
Other Terms
Suite Accelerator, Scenarios, Context, RDA_MAINTAIN
2.14 ABAPTWL - VM Container not supported
Application Components:BC-VMC
Related Notes:
Note Type
Note Number
Note Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 44
Business Impact
2560708
Kernel for S/4 HANA does not support
VMC
Symptom
Starting with S/4HANA release 1809, which corresponds to SAP Kernel version 7.73, the
Virtual Machine Container (VMC) funtionality is no longer included.
Reason and Prerequisites
S/4HANA release 1809 and later does not support Virtual Machine Container (VMC)
functionality.
Kernel 7.73 and following are not compatible with earlier versions of the SAP kernel.
Solution
Do not use a kernel version >= 7.73 with systems that require VMC functionality. For
such systems, a SAP Kernel with a version <= 7.53 has to be used.
If you want to preserve Java functionality implemented on the VMC, you have to migrate
it to a standalone Java program or Java container, like SAP Application Server Java.
Other Terms
VMC
2.15 ABAPTWL - AS Java not available
Application Components:BC-JAS-SF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2560753
Kernel for S/4 HANA cannot be used for
NetWeaver AS Java
Symptom
Starting with SAP Kernel version 7.73 the NW AS Java is no longer supported.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 45
S/4 HANA does not contain the NetWeaver Application Server Java (AS Java).
Kernel 7.73 and following are not compatible with earlier versions of the SAP kernel.
Solution
Do not use a kernel version >= 7.73 with the NetWeaver AS Java.
Other Terms
AS Java, J2EE
2.16 ABAPTWL - Dual Stack not supported
Application Components:BC-CST
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2560791
Kernel for S/4 HANA does not support
Dual Stack Systems
Symptom
Starting with S/4HANA release 1809, which corresponds to SAP Kernel version 7.73, the
Dual Stack system setup is no longer supported.
Reason and Prerequisites
S/4HANA release 1809 and later does not support a dual stack system setup.
Kernel 7.73 and following are not compatible with earlier versions of the SAP kernel.
Solution
Do not use a kernel version >= 7.73 with a dual-stack system. For systems with dual-
stack setup, a SAP Kernel with a version <= 7.53 has to be used.
If you need to migrate a dual-stack system to a release >= 1809, which corresponds to
SAP Kernel version 7.73, you have to split the system into Java and ABAP parts befrore
the upgrade. The Software Provisioning Manager (SWPM) offers such a migration
option.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 46
Other Terms
Dual Stack, AS Java
2.17 ABAPTWL - Instances without ICM not supported
Application Components:BC-CST-IC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2560792
ABAP instances in SAP S/4HANA
always start with an icman process
Symptom
AS ABAP instance always starts with an ICM process. Parameter rdisp/start_icman no
longer exists and is ignored.
Reason and Prerequisites
The configuration option was removed.
Solution
Intended behaviour.
Other Terms
ICM, Instance
2.18 ABAPTWL - Removal of OSS1 (Logon to SAP Service Marketplace)
Application Components:BC-CCM-MON
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2797047
OSS1: Transaction is deactivated
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 47
This transaction is not needed furthermore because of the update of the SAP Support
Backbone and new kind of connections to SAP.
Reason and Prerequisites
Shut down of SAP Service Marketplace SAP Frontend (OSS) and new kind of
communication with SAP Backbone
Solution
Please read SAP Note 2738426 - Automated Configuration of new Support Backbone
Communication for further info, here you could see the new needed info about the new
tools and how to use.
Other Terms
RSEFA910, SAPOSS, SM01, SAP Service Marketplace SAP Frontend
2.19 ABAPTWL - End of Support for Pool Tables
Application Components:BC-DWB-DIC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2577406
S4TWL - End of support for pool tables,
cluster tables, table pools and table
clusters with S/4 HANA 1809
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 1809 on-premise
edition release 1809 or higher. You have been using pool tables or cluster tables. The
following SAP S/4HANA Transition Worklist Item is applicable in this case.
Solution
Description
Starting with release S/4 HANA 1809 pool tables and cluster tables are no longer
supported. Automatic transformation of pool tables and cluster tables to transparent tables
and the removal of table pools and table clusters is integrated into the upgrade or
migration to S/4 HANA 1809.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 48
Hint: Table clusters (examples: CDCLS, RFBLG, DOKCLU, ...) or cluster tables
(examples: CDPOS, BSEG, DOKTL, ... in non-HANA Systems) must not be mixed up
with export/import-tables (examples: INDX, STXL, ...). Export/import tables are used to
store object collections as data clusters with the ABAP statement "EXPORT ... TO
DATABASE ...". Export/import tables are still supported in 1809.
Business Process related information
The concept of pool and cluster tables is regarded as obsolete, particularly in the context
of the HANA database. They implement an own limited in-memory mini-DBMS that is
not transparent to the underlying database and that interferes with the optimization
strategies of the underlying database. Accordingly, de-clustering and de-pooling is part of
migrations to HANA based products already before release 1809. However, creation of
new pool and cluster tables was still possible. With the mandatory transformation into
transparent tables it is guaranteed that tables always have the optimal format for HANA.
Required and Recommended Action(s)
As in release 1809 table pools and table clusters (both have the object type R3TR SQLT;
example table pool is ATAB; example table cluster is CDCLS) are removed, customer
coding that has references to table pools or table clusters needs to be adapted. Such
references are typically rare. ABAP coding normally deals with the logical tables (pool
table or cluster table), which are still existing as transparent tables after the conversion,
and not with the container tables (i.e. the table pools or table clusters).
If references to table pools and table clusters are not removed, syntax errors will show up
in coding with such references after the upgrade or conversion to release 1809.
In addition coding that referenced the repository tables for table pools and table clusters
needs to be adapted. All access to the tables DD06L, DD06T, DD16S and to the views
DD06V, DD06VV and DD16V needs to be removed, as those tables and views do no
longer exist in release 1809.
How to Determine Relevancy
Coding places that need to be adapted can be found as follows:
References to table pools and table clusters:
Determine object list of references to table pools and table clusters:
All SQLT objects, that will no longer exist in release 1809 can be found in the
table TADIR. Display the table content of table TADIR with transaction SE16
and select all SQLT object names with the selection "program id" =
R3TR; "object type" = SQLT. Copy the list of SQLT objects into the clipboard.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 49
Quick Check:
Use the cross-reference table WBCROSSGT to find all coding places that use
SQLT objects. First make sure that in the system you are using for the check the
cross-reference tables are properly filled (see SAP Note 2234970 for details). Then
display the table content of table WBCROSSGT with transaction SE16 and select
all programs that use SQLT objects with the selection "version number
component" = TY; "object" = <paste the object list determined in step 1>. If the
result list shows customer programs you are affected.
Detailed Check:
Use the code inspector (transaction SCI) to get a detailed list of all coding places.
Create a check variant using the check "Search Functions" -> "Objects used in
programs". In the search pattern list enter \TY:<SQLT object> for all SQLT
objects determined in step 1 (Example: \TY:ATAB ). Define an object set that
includes all customer objects and run an inspection with the check variant and
object set to get the detail list of all places.
Remove all usages of SQLT objects in your coding. Hint: Pure type
references can be replaced by references to the fields of the logical tables.
As an alternative you can use in releases based on ABAP Platform 1709
(SAP_BASIS 752) or newer the code inspector check variant "Pools/Cluster-
Types used in Programs". With this check variant you don't need to enter the
object list manually.
References to SQLT repository tables and views:
Repository tables object list:
DD06L, DD06T, DD16S, DD06V, DD06VV, DD16V
Quick Check:
Use the cross-reference table WBCROSSGT to find all coding places that use the
objects from step 1. Display the table content of table WBCROSSGT with
transaction SE16 and select all programs that use the objects with the selection
"version number component" = TY; "object" = <paste the object list from step 1>.
If the result list shows customer programs you are affected.
Detailed Check:
Use the code inspector (transaction SCI) to get a detailed list of all coding places.
Create a check variant using the check "Search Functions" -> "Objects used in
programs". In the search pattern list enter \TY:<object list from step
1> (Example: \TY:DD06L ). Define an object set that includes all customer
objects and run an inspection with the check variant and object set to get the detail
list of all places.
Remove all usages of the repository tables and views in your coding.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 50
Transport behavior
Cross release transports (R3trans) are in general not recommended. The import
behavior for pool- and cluster related objects and content in systems with release 1809 or
higher is given below for your information:
Importing definitions of table pools or table clusters (R3TR SQLT):
The object is not imported into the system. The transport finishes with RC = 4. In
the DDIC import protocol a warning is issued.
Importing content of a table pool or table cluster (R3TR TABU on table pool or
table cluster):
The content is not imported as the table cluster or table pool does not exist in the
target system. The R3trans return code is RC = 8.
Importing definitions of pool tables or cluster tables (R3TR TABD/TABL for
tables that are pool tables or cluster tables in the export system):
The table is treated as transparent table.
Importing content of a pool table or cluster table (R3TR TABU on table pool or
table cluster):
The content is imported as of today if an according transparent table is existing.
2.20 S4TWL - FIORI APPLICATIONS FOR SUITE ON HANA ON-
PREMISE
Application Components:XX-SER-REL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2288828
S4TWL - Fiori Applications for SAP
Business Suite powered by SAP HANA
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. You already
use existing Fiori Apps in your Business Suite (e.g. ERP Enhancement
Packages) landscape and would like to understand the conversion behavior and adoption
needs on the frontend server.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 51
Reason and Prerequisites
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.
Solution
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-End Product’ and
select ‘SAP S/4HANA, on-premise edition’ to display a list of all Fiori apps available.
This filter can be combined 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 52
Example: Fiori app ‘My Spend’ for ERP has a successor ‘My Spend’, which is available
for ERP Add-On ‘SAP FIORI for SAP SFIN 1503’ as well as ‘S/4 HANA on-premise
1511’
Option 3: Check availability in in S/4HANA on-premise edition for multiple apps
Filter and select all apps you want to check. Activate ‘Aggregate’ at the bottom of the
app list to display a consolidated view about all selected apps. Select ‘SAP S/4HANA,
on-premise edition’ in 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).
Additional information provided per application area (where required):
Note 2242596 - Release Information: Changes in Fiori Content in S/4Hana Finance,
on-premise edition 1605 (sFIN 3.0)
Note 2290488 - Changes in Fiori Application for SAP S/4 HANA in Sales and
Distribution
Other Terms
Fiori, Conversion, Business Suite, S/4HANA on-premise, Conversion
2.21 S4TWL - SAP S/4HANA AND SAP BUSINESS WAREHOUSE
CONTENT
Application Components:BW-BCT-GEN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2289424
S4TWL - SAP S/4HANA and SAP
Business Warehouse Content -
BI_CONT / BW4CONT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 53
Symptom
You are doing a new installation or system conversion to SAP S/4HANA, on-premise or
cloud edition. The following item is applicable in this case.
Solution
Embedded BW in SAP S/4HANA
The software components BI_CONT (BI Content) and BI_CONT_XT (BI Content
Extensions) are not supported in the Embedded BW client of all editions and releases
of SAP S/4HANA (cloud and on premise), even though they are technically installable.
Exception: For usage of SEM-BCS in embedded BW in S/4HANA on premise as
outlined in SAP Note 2360258, installation of BI_CONT is a necessary prerequisite
Content Bundle: The only supported Content Bundle in SAP S/4HANA system is
/ERP/SFIN_PLANNING (Simplified Financials Planning). All other content bundles are
not supported in SAP S/4HANA.
Standalone SAP Netweaver BW
Only the SAP HANA-optimized Business Content shipped with the software component
version BI_CONT 7.57 (BI Content 7.57; see also SAP Note 153967) is supported for the
whitelisted DataSources delivered with SAP S/4HANA (as specified in SAP Note
2500202). For further details on SAP HANA-Optimized Business Content please check
SAP Note 2548065.
Standalone SAP BW/4HANA
All content included in the BW/4HANA Content Basis (software component
BW4CONTB) and BW/4HANA Content (software component BW4CONT) is supported
for the whitelisted DataSources delivered with SAP S/4HANA (as specified in SAP Note
2500202). For further details on SAP HANA-Optimized Business Content please check
SAP Note 2548065.
Other Terms
BI_CONT, BI_CONT_XT, BW4CONTB, BW4CONT, SAP BW, SAP BW/4 HANA,
SAP_BW, DW4CORE, Business Content, SAP Netweaver, S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 54
2.22 S4TWL - Social Intelligence
Application Components:CA-EPT-SMI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2323655
Social Intelligence Non-availability
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
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
Solution
As of now, there is no alternative for this solution in S/4 HANA
2.23 S4TWL - Custom Fields
Application Components:BC-SRV-APS-EXT-FLD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2320132
S4TWL - Custom Fields
Symptom
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:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 55
SAP Fiori apps
CDS-based analytical reports
Adobe-based print forms
Email templates
OData services
Reason and Prerequisites
You have set up the adaptation transport organizer. For more information,
see Configuration Information: Adaptation Transport Organizer.
Solution
Description
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.
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 Enabling Custom Database Fields for Usage in SAP Fiori
Applications.
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 preperation steps, if necessary.
For more information, see Enabling Custom Database Fields for Usage in SAP Fiori
Applications.
Other Terms
Extension, Custom, Fields
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 56
2.24 S4TWL - Side Panel functionality in SAP S/4HANA (on-premise)
Application Components:FI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2340424
Availability of Side Panels in S/4HANA
(on-premise)
Symptom
You are doing a system conversion to SAP S/4HANA (on-premise). You use Side Panels
in the SAP Business Client and would like to understand the conversion behavior.
Reason and Prerequisites
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 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/f8478f40ca420991a72eed8f222c
8d/content.htm?current_toc=/en/58/327666e82b47fd83db69eddce954bd/plain.htm
Solution
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
CHIP
BSSP_LPD_FI_AP
Accounts Payable Reporting (Links)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 57
BSSP_LPD_FI_AR
Accounts Receivable Reporting (Links)
BSSP_LPD_FI_AA
Asset Accounting Reporting (Links)
BSSP_LPD_CO_OM_CCA
Cost Center Reporting (Links)
BSSP_LPD_FI_GL
General Ledger Reporting (Links)
BSSP_LPD_CO_OM_OPA
Internal Order Reporting (Links)
BSSP_LPD_PM_OM_OPA
Maintenance / Service Order Reporting
(Links)
BSSP_LPD_CO_PC
Product Cost Reporting (Links)
BSSP_LPD_FI_GL_PRCTR
Profit Center Reporting (Links)
BSSP_FI_AA_POSTED_DEPREC
Asset Accounting: Posted Depreciation
(Reports (Display as Form / List))
BSSP_CO_OM_CC_ACT_PLAN_AGGR
Cost Center: Cumulative Actual/Planned
Costs (Reports (Display as Form / List))
BSSP_FI_AR_TOTALS
Cost Center Balance: Totals (Reports
(Display as Form / List))
BSSP_FI_AR_DUE_ANALYSIS
Customer Due Date Analysis (Reports
(Display as Form / List))
BSSP_FI_AR_DUE_FORECAST
Customer Due Date Forecast (Reports
(Display as Form / List))
BSSP_FI_AR_OVERDUE
Customer Overdue Analysis (Reports
(Display as Form / List))
BSSP_CO_OM_IO_ACT_PLAN_AGGR
Internal Order: Cumulative Actual/Planned
Costs (Reports (Display as Form / List))
BSSP_CO_PC_MAT_ACT_PLAN_AGGR
Material: Aggregated Actual / Planned Costs
(Reports (Display as Form / List))
BSSP_GR_IR_GOODS_RECEIPT
Purchase Order History: Goods Receipt
(Reports (Display as Form / List))
BSSP_GR_IR_INVOICE_RECEIPT
Purchase Order History: Invoice
Receipt(Reports (Display as Form / List))
BSSP_GR_IR_OPEN_ITEM
Purchase Order: Open Items (Reports
(Display as Form / List))
BSSP_FI_AP_TOTALS
Vendor Balance Totals (Reports (Display as
Form / List))
BSSP_FI_AP_DUE_ANALYSIS
Vendor Due Date Analysis (Reports (Display
as Form / List))
BSSP_FI_AP_DUE_FORECAST
Vendor Due Date Forecast (Reports (Display
as Form / List))
BSSP_FI_AP_OVERDUE
Vendor Overdue Analysis (Reports (Display
as Form / List))
BSSP_FI_AA_POSTED_DEPREC_C
Asset Accounting: Posted Depreciation
(Reports (Display as Chart))
BSSP_CO_OM_CC_PERIOD_BD_C
Cost Center: Breakdown Actual/Planned
Costs by Period (Reports (Display as 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))
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 58
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))
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))
BSSP_CO_OM_CC_PERIOD_BD_C2
Cost Center: Breakdown Actual/Planned
Costs by Period (Reports (Display as 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))
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 59
BSSP_CO_OM_IO_ACT_PLAN_AGGR_C2
Internal Order: Cumulative Actual/Planned
Costs (Reports (Display as HTML5 Chart))
BSSP_CO_PC_MAT_ACT_PLANAGGR_C2
Material: Aggregated Actual / Planned Costs
(Reports (Display as HTML5 Chart))
BSSP_CO_PC_MAT_PERIOD_BD_C2
Material: Breakdown Actual/Planned Costs
by Period (Reports (Display as HTML5
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))
Other Terms
CHIPs, Side Panel for Business Suite, S/4HANA (on-premise), Conversion
2.25 S4TWL - Changed Interfaces
Application Components:XX-SER-REL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2259818
RFC enabled Function Modules with
incompatible signature change
compared to its version in ERP are
blocked from external access.
Symptom
You are using SAP S/4HANA. Certain RFC enabled Function Modules have been
blocked from external access using RFC Unified Connectivity Filter Services.
Reason and Prerequisites
Many RFC Function Modules that were delivered with ERP, are now available in SAP
S/4HANA delivering same functionality and services. RFC Function Modules can be
categorized by their "Release"-Status: "Released" implies an RFC enabled Function
Module can be called from any remote SAP or non SAP Application. "Not Released"
implies an RFC Function Module is not accessible by customer but can be called from
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 60
any remote SAP application and hence used internally for cross application
communication.
In SAP S/4HANA, some small percentage of RFC enabled Function Modules (with
either "Released" and "Not Released" status) have had their signature modified in an
incompatible way, compared to the signature of their version in ERP. RFC enabled
Function Module use memory copy to transfer parameters between the source and target
in most cases and thus any incompatible change to the signature of the RFC enabled
Function Module may lead to the target receiving incomplete or garbled data as
parameter value.
Using these Function Modules across-system may harm the data integrity of your
SAP S/4HANA System, since the caller might still use the old signature.
If all callers of such a Function Module have been explicitly adapted to the changed
signature, and if there are no un-adapted calls from your landscape, then using
such a module is possible.
If external non-SAP systems provided by 3rd parties want to use such a Function
Module, then ask them explicitly, if they have adapted their coding to the new
signatures.
Additionally, some RFC enabled Function Modules have been marked as "Obsolete" and
hence they are also blocked from external access.
An RFC Enabled Function Module that has been blocked from external or remote
access can be verified by remotely calling this RFC Enabled Function Module on your
SAP S/4HANA system and receiving a short dump, as described in the note #2249880.
Solution
RFC Blacklist
SAP uses a feature called RFC Blacklist, whereby, those remote enabled function
modules that need to be restricted from being called by external RFC Clients, are added a
RFC Blacklist object, which has the same identifity as a package. SAP releases one
blacklist package per S/4HANA OP release. The names of the RFC Blacklist packages
are as follows:
S/4HANA OP Release # | Blacklist Package
S/4HANA OP 2021 | ABLMUCON2021
S/4HANA OP 2020 | ABLMUCON2020
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 61
S/4HANA OP 1909 | ABLMUCON1909
S/4HANA OP 1809 | ABLMUCON1809
S/4HANA OP 1709 | ABLMUCON1709
S/4HANA OP 1610 | ABLMUCON1610SP00
View the contents of RFC Blacklist
The RFC blacklist and its contents can be viewed from a program
RS_RFC_BLACKLIST_COMPLETE. This program can be run on any S/4HANA OP
instance. Upon executing this program you would be asked to provide the package name
of the blacklist. For example, on an S/4HANA OP 1909 instance, provide the package
name is ABLMUCON1909 & the names of blacklisted remote enabled Function
Modules would appear in the result .
Applies to S/4HANA 1610 OP and above.
Override the Blacklist on your landscape
For any reason, you wish to unblock the access of any RFC enabled Function Module by
an external RFC client, then please follow the instructions mentioned in the note
#2408693.
Other Terms
RFC UCON, RFC Unified Connectivity, Signature Incompatibility
2.26 S4TWL - SAP Support Desk ($$-Messages)
Application Components:CA-NO, QM-QN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2852082
S4TWL – existence check for basis
notification and $$ notification
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 62
You use $$ notifications and basic notifications that were created in table
DNOD_NOTIF. The function module DNO_OW_EXTERN_SEND_NOTIF_2_BC,
which was used to create basic notifications, is no longer supported in SAP S/4HANA.
Reason and Prerequisites
Renewal
Solution
Business value
Instead of the $$ notifications and basis notifications, SAP Support is available via SAP
Support Portal at https://support.sap.com.
Required and recommended action(s)
Check whether an entry has been defined in the table DNOD_NOTIF.
Other Terms
$$, $$ notifications, support notifications, enter support notifications, DNOD_NOTIF,
function module DNO_OW_EXTERN_SEND_NOTIF_2_BC,
DNO_OW_EXTERN_SEND_NOTIF_2_BC
2.27 S4TWL - Changes in Process Observer
Application Components:CA-EPT-POC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2412899
Changes in Process Observer when
moving from SAP Business Suite to
S/4HANA OP
Symptom
A few changes occurred in the implementation of Process Observer in S/4HANA, which
may affect you when moving from SAP Business Suite to S/4HANA OP version.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 63
1) Business Function FND_EPT_PROC_ORCH_1 for Process Observer is always on
2) Improved IMG structure in S/4HANA
3) Name change for background job for event processing
4) Authorization check for maintaining process definitions enabled
5) Predecessor determination by document relationship browser (DRB) is off by default
Solution
1) Business Function FND_EPT_PROC_ORCH_1:
In order to use Process Observer in S/4HANA, there is no need to
activate FND_EPT_PROC_ORCH_1 any more, as it is set to 'always on' in the s/4HANA
systems. The remaining steps to activate process observer is the:
- activation setting: via IMG or transaction POC_ACTIVE
- scheduling of background job for event processing: via IMG or transaction
POC_JOB_SCHEDULER
2) Improved IMG structure for Process Observer:
Please see note 2461687 to find information about the changes to the IMG structure of
Process Observer, and to relocate the activities.
3) Background job for event processing:
The name of the running background job for event processing was changed from
'POC_JOB_<client>' in SAP Business Suite to
'SAP_POC_PROCESS_EVENT_QUEUES'. This may be relevant, for example when
managing the job via SM37.
4) Authorization check for maintaining process definitions:
The authorization check for maintaining process definitions via IMG or transaction
POC_MODEL was not activated by default SAP Business Suite. In S/4HANA the
authorization object POC_DEFN is checked when trying to create, change or delete
process definitions. Make sure the corresponding user roles in S/4HANA contain this
authorization object with the appropriate settings.
5) Predecessor determination via DRB:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 64
In your SAP Business Suite implementation you may be relying on predecessor
determination for events using DRB, if the following appies:
- you are using BOR events for monitoring
- different business object types are part of one process definition
- you did not implement or configure a specific predecessor determination for your
objects (like referencing an attribute in BOR event, or BAdI implementation)
In order to activate the predecessor determination via DRB again in S/4HANA do the
following: enter the relevant BOR events in the follwing IMG activity:
<...> Process Observer - Application Instrumentation - BOR Event Instrumentation -
Enable Data Relationship Browser (DRB) Usage
Other Terms
Process Performance Monitoring in S/4HANA
2.28 ABAP4TWL - Removal of Transceiver Integration
Application Components:CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2879911
Package BALI is missing
Symptom
The package BALI covering transceiver functionality of R/3 up-to release 6.10 is
missing.
Reason and Prerequisites
Transceiver functionality is discontinued.
Solution
The transceiver functionality has been withdrawn and has been replaced with new
interfaces, see SAP Note 176927.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 65
Other Terms
Programs CONFQMID,
RCONFCC1, RCONFCC2, RCONFCC3, RCONFCC4, RCONFCC5, SAPBAL10,
SAPCDUP1, SVCTKANA
Function group TRAR
Business object types
IDOCCONF11, IDOCCONF21, IDOCCONF22, IDOCCONF31, IDOCCONF32, IDOC
CONF41, IDOCCONF42
Workflow tasks TS00200089,
TS00200090, TS00200096, TS00200097, TS00200098, TS00200099, TS00200101
2.29 S4TWL - BI Extractors in SAP S/4HANA
Application Components:XX-SER-REL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2500202
S4TWL - BW Extractors in SAP
S/4HANA
Symptom
Customers considering moving to SAP S/4HANA (on premise) seek information whether
BW extractors (aka data sources) known form SAP ERP still work, to be able to evaluate
the potential impact on the BW environment when moving to SAP S/4HANA. To meet
this requirement, SAP reviewed the status and the attached list (MS Excel document)
provides the information that we have per extractor. The results are valid from SAP
S/4HANA 1709 (on premise) until further notice or otherwise and in most cases apply to
SAP S/4HANA 1610 and SAP S/4HANA 1511 as well (see respective flags in attached
MS Excel document).
Reason and Prerequisites
Parts of this information are already available in CSS and can be found through 2333141
- SAP S/4HANA 1610: Restriction Note. The status of the extractors is collected in one
list (the attached MS Excel document), see the attached MS Powerpoint document for
information how the list is typically used. Not all extractors that are technically available
in SAP S/4HANA are covered, SAP is planning to provide clarifications for additional
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 66
extractors and share new versions of the list via this note. Hence it is recommended to
review this note for updates.
The information in this file is dated as of 10.09.2018. Please acknowledge that S/4HANA
functionality is set forth in the S/4HANA Feature Scope Description. All business
functionality not set forth therein is not licensed for use by customer.
Please note that extractors in the namespace 0BWTC*, 0TCT* and 8* are related to the
"Embedded BW" that is offered as a technology component within the S/4HANA software
stack. They are all not explicitly whitelisted in this SAP Note as they are not part of the
delivered Business Content by the S/4HANA Lines of Business but can be used for
extraction.
0BWTC* and 0TCT* are extractors providing technical statistical information from
the Embedded BW such as query runtime statistics or data loading statistics.
8* are Export DataSources for transferring business data from InfoProviders of the
“Embedded BW” system to a target system
For a SAP BW target systems this is achieved by the SAP Source System type
For a data transfer via the ODP Source System type (only option in SAP
BW/4HANA target system) these Export DataSources are obsolete and
invisible. Instead, the ODP-BW context is used. For more information on
Operational Data Provisioning see the ODP FAQ document.
For more information and positioning on the "Embedded BW" see:
https://www.sap.com/documents/2015/06/3ccee34c-577c-0010-82c7-eda71af511fa.html
For more information on partner registered data sources and to find partner details from
partner namespaces, please create a message on component XX-SER-DNSP.
This is a collective note, containing information of several industries and areas. In
case issues arrise with extractors listed in the Excel, or missing extractors, please do
raise an incident on the APPLICATION COMPONENT of the
respective EXTRACTOR. This is the only way to ensure that your incident reaches
the responsible desk in the shortest time. You can find this in column E,
'Appl.component' in the attached excel document. Do not use the component from
this note. Thank you!
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 67
Solution
Details can be found in the respective note per area:
Item Area - Line of
Business
Note number for details
Asset Management
2299213 - Restrictions for BW-Extractors in S/4HANA in the
Enterprise Asset Management domain (EAM)
Business Process
Management
2796696 - Restrictions for BW extractors relevant for S/4HANA as
part of SAP S/4HANA, on-premise edition 1709 and above
Customer Services
2533548 - Restrictions for BW-Extractors in S/4HANA in the CS
(Customer Service) area
Enterprise Portfolio and
Project Management
2496759 - Restrictions for BW extractors relevant for S/4HANA in
the area of Enterprise Portfolio and Project Management
Financials
2270133 - Restrictions for BW extractors relevant for S/4HANA
Finance as part of SAP S/4HANA, on-premise edition 1511
Flexible Real Estate
2270550 - S4TWL - Real Estate Classic
Global Trade
Globalization Services
Finance
2559556 - Restrictions for BW extractors in Financial Localizations
relevant for S/4HANA Finance as part of SAP S/4HANA, on-
premise edition 1511
Human Resources
Incident Management and
Risk Assessment
2267784 - S4TWL - Simplification in Incident Management and
Risk Assessment
Master Data
2498786 - Data Sources supported by Central Master Data in
S/4HANA
2576363 - Data Sources supported by Master Data Governance in
S/4HANA
Procurement
2504508 - Restrictions for BW Extractors relevant for S/4 HANA
Procurement as part of SAP S/4HANA, on premise edition 1709
and above
Produce
2499728 - Restrictions for BW extractors relevant for S/4HANA in
the area of Production Planning and Detailed Scheduling
2499716 - Restrictions for BW extractors relevant for S/4HANA in
the area of Production Planning and Control
2499589 - Restrictions for BW extractors relevant for S/4HANA in
the area of Quality Management
2499310 - Restrictions for BW extractors relevant for S/4HANA in
the area of Inventory Management
Sales and Distribution
2498211 - Restrictions for BW extractors relevant for S/4HANA
Sales as part of SAP S/4HANA, on-premise edition 1709
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 68
Supply Chain – Extended
Warehouse Management
2552797 List of BI Data Sources used in EWM
2382662 List of BI Data Sources from SCM Basis used in EWM
Context
Supply Chain –
Transportation
Management
All Data Sources working and whitelisted, no separate note exists
Master data governance for
Finance
All Data Sources working and whitelisted, no separate note exists
Item Area - Industry
Note number for
details
DIMP Automotive
Defense and Security
2544193 - Restrictions for BW extractors relevant for S/4HANA in
the area of Defense & Security
2273294 - S4TWL - BI content, Datasources and Extractors for
DFPS
Financial
Services
2543469 - "SAP for Banking": SAP extractors in connection with
"SAP S/4HANA on-premise edition
2546102 - "SAP for Insurance": SAP extractors in connection with
"SAP S/4HANA on-premise edition“
Higher Education
IS Healthcare
-
IS Utilities
2270505 - S4TWL - IS-U Stock, Transaction and Master Data
Statistics (UIS, BW)
Oil and Gas
Public Sector Collection and
Disbursement (PSCD)
All Data Sources working and whitelisted, no separate note exists
Public Sector Management
(PSM)
2556359 - Restrictions for BW extractors relevant for S/4HANA in
the area of Public Sector Management
IS Retail
2543543 - Restrictions for BW extractors relevant for S/4HANA in
the area of Retail
The classification scheme is:
Current
status
Status for Publication
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 69
Whitelisted
DS working - no restrictions
DataSource is available with S/4
and works without any
restrictions compared to ERP
DS working – regeneration of extractor and
check of BW content based on this DS
is needed
.
DataSource is working, because
of data model changes, it is
recommended to check the
upward dataflow.
Not Whitelisted
DS working - restrictions
DataSource is available with S/4
but works with noteworthy
restrictions; e.g. not all fields are
available
DS not working - alternative exists
DataSource is not working with
S/4 but an alternative exists,
such as a new extractor, CDS
view
DS not working - alternative planned
DataSource is not working with
S/4 but equivalent available on
roadmap for future release
Deprecated
DS obsolete
DataSource is obsolete - legacy
extractors
DS not working - no alternative exists
DataSource is not working with
S/4 but no alternative exists
Generated
Data Source
DS working - no restrictions
Because of the nature of the
extractors, being generated in
the system, we cannot whitelist
those in general. Experience so
far showed that they should be
working without restrictions.
Not relevant for
BW extraction
DS not relevant
Datasource is available in
ROOSOURCE, however, not to
be used for extraction by BW.
Other Terms
BW, Extractors, Datasources, SAP S/4HANA
2.30 S4TWL - MRS Enhancements for Material Master
Application Components:CA-MRS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2493452
MRS enhancements to Material master
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 70
Symptom
SAP Multiresource Scheduling 1.0 for SAP S/4HANA does not support the material
master enhancement for requirements profiles.
If you have used this functionality in previous SAP Multiresource Scheduling releases
and would like to store the data before they might be lost during SAP Multiresource
Scheduling 1.0 for SAP S/4HANA installation, please execute the steps describe in the
manual activities attached to this note.
Reason and Prerequisites
Not supported functionality in SAP Multiresource Scheduling 1.0 for SAP S/4HANA.
Solution
Follow the steps describe in the manual activity.
Other Terms
Master Check, S/4 System Conversion, Material Master, MRS.
2.31 S4TWL - Change of Situation Types in Situation Handling
Application Components:CA-SIT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3324958
SIC for ZDM Upgrade Check in
Situation Handling
Symptom
You execute a system conversion to S/4HANA, On-Premise - Edition 2023 or higher and
are using the Situation Handling Framework - extended.
Reason and Prerequisites
You use at least one of the following apps:
1. Manage Situation Types : Extended
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 71
2. Manage Situation Scenarios.
3. Manage Situation Objects
Solution
The Simplification Item Check checks, if the requirements before the upgrade are met
and all required SAP notes (currently SAP Note 3271299) have been implemented to
ensure there is no concurrent access or attempt to write to the underlying tables during
the data conversion.
If this is not the case the Software Update Manager (SUM) will be asking to install the
required SAP notes before proceeding,
The checks performed by Simplification Item Check are
Check if any of the apps: Manage Situation Types- Extended, Manage Situation
Scenarios or Manage Situation Objects are active in the system.
If this is not the case, the implementation of the Simplification Item Check is not
required.
Check if the required SAP Note 3271299 is implemented in the system. The check is
done by checking the availability of the interface
IF_SIT2_CHECK_ZDM_RUNNING that gets implemented by the SAP Note.
If the check is successful, it's ensured there is no concurrent access or attempt
to write to the underlying tables during the data conversion and the
Software Update Manager (SUM) can proceed with the system upgrade
If the check is not successful, the SUM is aborted, and it cannot proceed with
the system upgrade. SAP Note 3271299 needs to be implemented to
proceed with the upgrade.
Required and Recommended Action(s) :
After implementing the SIC (Simplification Item Check) : If the consistency check
fails and the update in the Software Update Manager (SUM) is aborted, please implement
the SAP Note 3271299 to ensure that all requirements before the upgrade are
implemented and the system upgrade can happen properly.
Other Terms
Situation Handling; Manage Situation Types - Extended; Manage Situation Scenarios ,
Manage Situation Objects
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 72
2.32 ABAPTWL - Change of workflow system user and workflow system
jobs
Application Components:BC-BMT-WFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2568271
Change of workflow system user and
workflow system jobs with S/4HANA
On-Premise 1709
Symptom
You upgraded your system to S/4HANA On-Premise 1709, 1809, 1909, 2020, 2021 (or
following releases) from a release prior S/4HANA On-Premise 1709. In "Automatic
Workflow Customizing", transaction SWU3 you notice the status is not green for "Edit
Runtime Environment".
Reason and Prerequisites
Change of workflow system user and workflow system jobs with S/4HANA On-Premise
1709.
Solution
Description
Starting with S/4 Hana OnPremise 1709 the workflow system user and workflow system
jobs changed. The workflow system user is called SAP_WFRT now instead of WF-
BATCH. The workflow system jobs start with SAP_WORKFLOW now and are
scheduled automatically by "Technical Job Repository", transaction SJOBREPO.
Starting with S/4 Hana OnPremise 1809 the workflow system jobs are scheduled under
the user, under which the system jobs of Technical Job Repository run. This might be a
different user than SAP_WFRT.
Business-Process-Related Information
SAP Business Workflow does not continue after upgrade.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 73
In case you upgraded from an older release to S/4HANA OnPremise 1709 you need to
perform the following steps, in S/4 HANA OnPremise 1809, 1909 and 2020 only steps 2
to 6 are relevant:
Deschedule the "old" workflow jobs in all system clients, in case these are still
scheduled from the time before the upgrade. These are the following jobs:
SWWDHEX
SWWERRE
SWWCOND
SWWWIM
SWEQSRV
SWWCLEAR
If you upgrade to S/4 HANA OnPremise 1809, these jobs are automatically
descheduled.
Make sure that user SAP_WFRT exists in the system and has role
SAP_BC_BMT_WFM_SERV_USER_PLV01 assigned.
Check role SAP_BC_BMT_WFM_SERV_USER_PLV01 e.g. in transaction PFCG:
Ensure that there is a green traffic light on tab "Authorizations". Regenerate the
profile if necessary.
Afterwards check the traffic light on the tab "User". Run the "User Comparison"
if the traffic light is not green.
In "Technical Job Repository" (transaction SJOBREPO) the automatic scheduling of
jobs must be switched on. Note 2190119 - Background information about
S/4HANA technical job repository - describes the prerequisites needed.
Wait for the next run of system job "R_JR_BTCJOBS_GENERATOR" for the
Technical Job Repository. It runs by default every hour and schedules all new
workflow system jobs starting with SAP_WORKFLOW.
After the workflow jobs are scheduled, you will see green lights in transaction
SWU3.
Job SAP_WORKFLOW_RESTART is automatically scheduled in the system. It runs
once a day and restarts all workflows in error status automatically. These are
workflows, you can find in transaction SWPR. If you do not want these
workflows to be restarted, please deactivate the job in transaction SJOBREPO.
Other Terms
SJOBREPO, SAP_WFRT, SWU3, 1709, 1809, 1909, 2020, 2021
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 74
2.33 ABAPTWL - Change of authorization checks SAP Business Workflow
Application Components:BC-BMT-WFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2979517
ABAPTWL - Change of authorization
checks SAP Business Workflow
Symptom
After an upgrade of your system you face authorization issues in reports or transactions
of SAP Business Workflow. Especially this concerns helper reports or transactions like
for example RSWD_MAINTAIN_USER_ATTR or RSWEQADMIN.
Reason and Prerequisites
Originally the concerned reports and transactions have been protected by an authorization
check basing on the authorization group of the report. This check uses authorization
object S_PROGRAM, which does not support checking the activity of a user action; that
mean, no clear separation between display and change actions is possible.
Solution
Description
You use in your system helper reports or transactions from SAP Business Workflow.
Business-Process-Related Information
If you want to use the helper reports and transactions further, you have to change the
authorizations of the user, which should be allowed to do so.
Required and Recommended Action(s)
From SAP_BASIS 756 onwards the authorization check by authorization object
S_PROGRAM has been replaced by an authorization check on auhorization object
S_WF_ADM. This new authorization object has two authorization fields:
WF_GROUP
ACTVT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 75
To a group all reports/transactions are assigned caring about the same topic. For example
reports RSWF_SHOW_SWW_WIREGISTER (Registered Actions for Work Items) and
RSWEQADMIN (Event Queue Administration) are both assigned to group 'EVENT'.
With the activity you can differentiate the actions, which are allowed to the user. For example by
report RSWF_SHOW_SWW_WIREGISTER you can display the registered actions for work items,
but you cannot change them. Therefore the display-activity is checked. But in report RSWEQADMIN
several actions can be triggered, therefore it checks on the execute-activity.
Your roles for the user needing these reports or transactions need to be adapted accordingly.
Other Terms
Authorization objects:
S_WF_ADM, S_PROGRAM
Reports:
RHWFCOPL, LSWDDF32, LSWEQBROWSERF01, RHXWOSHW, RSLEI_TRC,
RSSWW_MOVE_TO_HOT, RSWD_CONFIG_INITIATOR,
RSWD_MAINTAIN_USER_ATTR, RSWD_REPLICATE_FROM_9999, RSWDACT0,
RSWDACTIVATE, RSWDADHOCDEL, RSWDCHECKALL, RSWDCOR8,
RSWDFXSTRT, RSWDLOG, RSWDSTRT, RSWDVER9, RSWDVERCNT,
RSWE_ELIM_INCONSIST, RSWECONSCOUP, RSWEDELCPLG,
RSWEENABLEFI, RSWEINST, RSWEINSTVMAINT, RSWELCFG, RSWELCFG2,
RSWELOGA, RSWELOGD, RSWELOGS, RSWELTOGGLE, RSWEQADMIN,
RSWEQDELETE, RSWEQMAINTAIN, RSWEQSRV, RSWEQSRV_ASYNC,
RSWEQSRVDELETE, RSWEQSRVSCHEDULE, RSWF_ADD_OM_EXIT_CLASS,
RSWF_ADM_SUSPEND, RSWF_ADM_SWWWIDH,
RSWF_ALM_DELETE_MONITOR, RSWF_ANALYZE_RESUBMIT,
RSWF_BAM_ADM, RSWF_CCMS_MONITOR_TEST,
RSWF_CHECK_CONTAINER_STRUCTS,
RSWF_CLEAR_SECMETHOD_MEMORY, RSWF_CNT_BOR_ELEM_REPLACE,
RSWF_CNT_CHECK_STRUCTURE, RSWF_CNT_COMPARE,
RSWF_CNT_DEL_LOC_STRUCTURE, RSWF_CNT_EDIT,
RSWF_CNT_JOB_SHMEMUPD_DELETE,
RSWF_CNT_JOB_SHMEMUPD_INSERT, RSWF_CNT_MAINTENANCE,
RSWF_CNT_PREPARE_STRUCTURE, RSWF_CNT_TEST_CONVERSION_XML,
RSWF_CREATE_WITEXT, RSWF_CRL_BUILDER,
RSWF_DATABASE_UPGRADE, RSWF_DELETE_CONTAINER_ELEMENT,
RSWF_DISPLAY_APPL_LOG, RSWF_FLEX_DEMO_CHECK,
RSWF_FLEX_DEMO_CHECK_F01, RSWF_FLEX_DEMO_CHECK_O01,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 76
RSWF_FLEX_DEMO_CHECK_TOP, RSWF_FLEX_SWI2_FREQ,
RSWF_FLEX_SWPINTRO, RSWF_FLEX_UTL_PROCESS_VIEW,
RSWF_FLEX_UTL_PROCESS_VIEW_F01,
RSWF_FLEX_UTL_PROCESS_VIEW_F02,
RSWF_FLEX_UTL_PROCESS_VIEW_F03, RSWF_GET_FOOTPRINT,
RSWF_LOG_DISPLAY, RSWF_MANAGE_WORKFLOW_DAEMON,
RSWF_MIG_CNT_STRUCTS_INTERNAL, RSWF_MIG_CONTAINER_STRUCTS,
RSWF_MIG_TOPWIID, RSWF_MON_ACTIVATED_DEADLINES,
RSWF_MON_DATABASE_SIZE, RSWF_NOTIF_ACTIVATION,
RSWF_OUTPUT_MANAGEMENT, RSWF_POWL_CHECK_QUERIES,
RSWF_PUSH_NOTIF_EXECUTE_DEMO,
RSWF_PUSH_NOTIFICATION_EXECUTE, RSWF_RESTART_WORKFLOWS,
RSWF_SHOW_AGING_INCONSISTENCY,
RSWF_SHOW_EXT_CONFIGURATION, RSWF_SHOW_SWW_USRATT,
RSWF_SHOW_SWW_WIREGISTER, RSWF_SHOW_SWWLOGHIST,
RSWF_SHOW_SWWLOGHIST_TOPLEVEL, RSWF_SHOW_SWWWIHEAD,
RSWF_SHOW_SWWWIHEAD_TOPLEVEL, RSWF_SHOW_SWWWITEXT,
RSWF_SYSTEM_ACTIONS, RSWF_SYSTEM_CLEANUP,
RSWF_SYSTEM_DELAYED, RSWF_SYSTEM_SCHEDULER,
RSWF_SYSTEM_TEMPORARY, RSWF_TCM_MIGR_CUST_CONF_XPRA,
RSWF_TCM_MIGRATE_CUST_CONFIG, RSWF_TRC_BAM,
RSWF_UNIT_CHCK_CONTAINER, RSWF_UNIT_CONFIGURATION,
RSWF_UNIT_MONITORING, RSWF_UTL_ENABLE_DEFAULT_TRACE,
RSWF_UTL_EXECUTE_ACTIONS, RSWF_WLC_WI_EVT_ADM,
RSWF_WLC_WI_EVT_ADM_F01, RSWF_WLC_WI_EVT_ADM_F02,
RSWF_XI_CACHE_RESET, RSWF_XI_REORG, RSWF_XI_SWI2,
RSWF_XI_SWPC, RSWF_XI_SWPR, RSWF_XI_TEST_BULK,
RSWF_XI_UNPROCESSED_MSGS, RSWF_XI_UNSENT_MSGS,
RSWF_XI_UNSENT_MSGS_F01, RSWF_XI_WORKLOAD_TEST,
RSWFADM_CHECK_SWWWIDH, RSWFEVTLOG, RSWFEVTLOGDEL,
RSWFEVTLOGF01, RSWFSLSDHIN, RSWFSLSDLEX, RSWFSLSDLEX_INSERT,
RSWFVMD, RSWH_DEMOINFO, RSWH_TEST_INBOX_TRANSLATION,
RSWI_MIGRATE_OUTBOX, RSWI_REGENERATE_WI2OBJ,
RSWI_WORKFLOW_DATABASE, RSWIADM2, RSWIDEAD_NEW, RSWIDIAG,
RSWIDISP, RSWIDONE, RSWIEXEC, RSWIEXEL, RSWIEXET, RSWIFREQ_NEW,
RSWILOAD, RSWIMEAN, RSWIODIA, RSWIOFIN, RSWIOINS, RSWIOTPD,
RSWIRROR, RSWIUNIT_NEW, RSWIUSAG_NEW, RSWIW3DO, RSWIW3OD,
RSWIW3OI, RSWIW3OT, RSWIWORK, RSWJ_PPF_PCOND,
RSWL_INPLACE_INBOX_DEMO, SWL_INPLACE_INBOX_DEMO_PROFI,
RSWL_SETUSERDEFAULT, RSWN_CHECK_DATA_VOLUME,
RSWN_CHECK_DATA_VOLUME_F01, RSWN_CHECK_DATA_VOLUME_F02,
RSWN_RUNTIME_DATA_REORG, RSWN_SET_APP_OBJ_KEY_HASH,
RSWN_SET_RECIPIENT_HASH2, RSWNNOTIFDEL, RSWNNOTIFDEL_DELETE,
RSWNNOTIFDEL_INSERT, RSWP_ADM_CREATE_CONFIG_PARAM,
RSWP_CHANGE_MAX_NODES, RSWP_CHECK_CB_CONSISTENCY,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 77
RSWP_CONTINUE_WORKFLOWS_GRID,
RSWP_RESTART_WORKFLOWS_GRID, RSWP_WFM_RUN_COMPATIBILITY,
RSWR_TEST_MOBILE_API, RSWTDREQ, RSWTTR01, RSWTTR02, RSWTTR03,
RSWTTR04, RSWTTR05, RSWTTR06, RSWUDFOL, RSWUDI00, RSWUDI01,
RSWUDI02, RSWUDI03, RSWUDI04, RSWUDI05, RSWUDI06, RSWUDI07,
RSWUDI08, RSWUDI09, RSWUDI10, RSWUESIM, RSWUMMES, RSWUOBJEX,
RSWUOBJEXBO, RSWUOCHECK, RSWUODEL, RSWUSETT, RSWUTR01,
RSWUVWIZBTE, RSWUVWIZCD, RSWUVWIZLIS,
RSWW_ACTIVATE_MEMORY_DIFFTOOL, RSWW_DAAG_AGING_RUN,
RSWW_DELETE_BINDEF, RSWW_DELETE_SWWRUNMETH,
RSWW_DEST_SET_UNICODE, RSWW_DROP_OBSOLETE_TABLES,
RSWW_EXEC_SUSPENDED_CALLBACK,
RSWW_EXEC_SUSPENDED_CANCEL, RSWW_FILL_DEFGUID,
RSWW_FILL_USER_ATTR, RSWW_MIG_FOOTPRINT,
RSWW_REORG_SWWUSERWI, RSWW_RUNTIME_MONITORING,
RSWW_STRAIGHTEN_SWW_REGISTER,
RSWW_STRAIGTHEN_FINAL_WRKFLWS, RSWWARCL, RSWWCLEAR,
RSWWCLEAR_DELETE, RSWWCLEAR_INSERT, RSWWCOND,
RSWWCOND_DELETE, RSWWCOND_INSERT, RSWWCOND_MON,
RSWWCOND_STRAIGHTEN_REGISTER, RSWWDELTAB, RSWWDHEX,
RSWWDHEX_DEBUG, RSWWDHEX_DELETE, RSWWDHEX_EXTENDED,
RSWWDHEX_INSERT, RSWWDHEX_INTERNAL,
RSWWDHEX_XMB_INTERNAL, RSWWDHIN, RSWWERIN, RSWWERRE,
RSWWERRE_DEBUG, RSWWERRE_DELETE, RSWWERRE_INSERT,
RSWWHIDE, RSWWMONB_BACKGROUND_STARTED, RSWWRUNCNT,
RSWWSTAT, RSWWWIDE, RSWWWIDE_DEP, RSWWWIDE_TOPLEVEL,
RSWWWIM, RSWWWIM_DELETE, RSWWWIM_INSERT,
RSWX_FORMABSENC_MONITOR, RSWXML_FIND, SWN_SELSEN_TEST,
SWXFORMA, SWXFORMC, SWXFORMD, SWXFORMS, SWXFORMS_SHOW,
SWXFORMS_TB, WDHEX_XMB_INTERNAL_DEADF01, WFUNIT_INTERNAL,
WFUNIT0001, WFUNIT0002, WORKITEM_DEL
Transactions:
RSWF_EXECUTE_ACTIONS, RSWF_PUSH_NOT, RSWF_RESTART_WF,
RSWF_SYSTEM_CLEANUP, RSWWCLEAR, RSWWCOND, RSWWDHEX,
RSWWWIM, SWDD_ACTIVATE, SWDD_DISPLAY, SWDD_REPLICATE,
SWDD_SCENARIO, SWDD_SCENARIO_DISP, SWDM, SWE3, SWE4, SWE5,
SWEL, SWELS, SWEM, SWEQADM, SWEQDEL, SWF_CREATE_WITEXT,
SWF_ENABLE_TRACE, SWF_EXECUTE_ACTIONS, SWF_FOOTPRINT,
SWF_HELPERS_DISP, SWF_JOBREPO_SLG1_DSP,
SWF_PROCESS_ADMIN, SWF_PROCESS_VIEW, SWF_SYSTEM_STATUS,
SWFC, SWFVMD1, SWI1, SWI1_RULE, SWI11, SWI13, SWI2_ADM1,
SWI2_DEAD, SWI2_DIAG, SWI2_DURA, SWI2_FREQ, SWI5, SWI6, SWIA,
SWIADM1, SWIADM2, SWPC, SWPR, SWU0, SWU2, SWU3, SWU4, SWU5, SWU6,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 78
SWU7, SWU9, SWUD, SWW_MOVE_TO_HOT, SWWDHEX_DEBUG,
SWWERRE_DEBUG
2.34 S4TWL - Business User Management
Application Components:BC-SEC-USR-ADM, CA-HR-S4
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2570961
Simplification item S4TWL - Business
User Management
Symptom
You need information about Business User Management in SAP S/4HANA.
Reason and Prerequisites
Business User Management in SAP S/4HANA is mandatory and is automatically
activated during the conversion from SAP Business Suite to SAP S/4HANA.
Solution
What Has Changed in Business User Management in SAP S/4HANA?
What is the difference between business users and SU01 users?
What is the business impact of that change?
Limitations
User Management
Business Partner
Human Capital Management (HCM)
HCM Integration active or inactive: What does it mean?
HCM Integration Switch (System Table T77S0)
External Resources Switch (System Table T77S0)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 79
How to create Business Users in SAP S/4HANA
HCM Integration is Active
HCM Integration is Inactive
Maintenance of the Business User Workplace Address
Conversion
How to Determine Relevance
What Has Changed in Business User Management in SAP S/4HANA?
SAP S/4HANA is introducing a new identity model for business users, which is based on
the "principle of one". A business user is defined as a natural person who is represented
by a business partner and a link to a user in the system. Business users interact with the
software in the context of a business process, for example, in the role of a purchaser, a
sales representative, or a production planner.
In SAP S/4HANA, the business partner is the natural person who maintains the user data
for the person, work center, and communication-related information. For logon, changing
the user ID (BNAME) is no longer supported. However, one person can still log on with
a user alias or email. The user alias or email can be changed (see SAP Note 2883989).
The identity model for business users ensures correct auditing, workflows, and jobs. It
also avoids errors in documents after a change of the user ID (BNAME). Auditors require
a consistent history of all documents that contains the user ID (BNAME).
SAP S/4HANA Business User Management enables and supports the entire life cycle
maintenance of business users such as organizational changes, change of employment, or
retirement. A user in SAP S/4HANA has a one-to-one relationship with a corresponding
business partner (natural person). This reduces redundant maintenance and prevents
outdated information.
What is the difference between business users and SU01 users?
The business user is a SU01 user, but also has a one-to-one relation to the corresponding
business partner. This relationship is time independent and cannot be changed anymore.
For more details about important user related constraints see SAP Note 2571544.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 80
The business user concept is used in many new applications in SAP S/4HANA. SU01
users with Classic Address (Identity Address Type 00 - User's Old Type 3 Address) lead
to limitations because the new business user model is a prerequisite for many business
applications. As soon as Fiori apps are activated and used, business users are mandatory
(for example Teams, CreditAnalyst in Credit Management or Situations).
The business partner contains the personal information, for example private address,
workplace address, bank details, vendor and customer related data. The business partner
and SU01 user share personal details and workplace address related data. The advantage
of the new business user model is that the entire lifecycle of that person works without
redundant maintenance of user address data. Business users can still be managed using
transaction SU01, Central User Administration or identity management systems.
In the SAP Business Suite, you can use transaction BP (Business Partner Maintenance) to
assign users to business partners. In SAP S/4HANA this is not possible anymore to avoid
an inconsistent data model for business users. Existing business partners cannot be
converted to business users, because of Data Protection and Privacy (DPP). Already
existing business partners could have been part of a distribution scenario.
What is the business impact of that change?
With the new business user model in SAP S/4HANA we have a clear maintenance
ownership. It can be owned by Human Capital Management (HCM), Business Partner
(BP) or User Management. The ownership of HCM is only relevant when HCM
integration is active. (More details about HCM integration see section HCM Integration
active or inactive: What does it mean?)
Using the example of SU01 the following data categories exist:
Person: The personal data for the business user is derived from the corresponding
business partner. In case HCM integration is active this data is mapped from
the corresponding employee of the HCM system (SAP SuccessFactors or SAP
HCM).
Work Center: The work center data for the business user is derived from the
workplace address of the corresponding business partner. In case HCM
integration is active, the function and department fields are mapped by default
from the corresponding employee of the HCM system (for customizing options,
see SAP Note 2548303).
Communication: The communication data for the business user is derived from the
workplace address of the corresponding business partner (for customizing options,
see SAP Note 2548303).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 81
Company: During the conversion of a SU01 user from SAP Business Suite (classic
user) to a business user in SAP S/4HANA the company address is copied to the
business partner workplace address.
Limitations - User Management
Due to the new business user model the database view USER_ADDR can no longer be
used in SAP S/4HANA. This view can only display the users with classic address but not
the business users. It is not possible to enhance this view. Instead of the database view
USER_ADDR use the search help USER_ADDR (which is equivalent to an official API
for searching users). In exceptional cases, you can use the SAP internal CDS view
P_USER_ADDR, but have in mind that it can be changed by SAP at any time. With the
ABAP statement "with privileged access" the authorization check is ignored. As a
reference, use the coding of the search help exit F4IF_USER_ADDR_SUID_EXIT.
Limitations - Business Partner
In general, business partners that are neither employee nor contingent workforce cannot
be managed as business users.
In transaction BP (Business Partner Maintenance) you can no longer assign SU01 users
to business partners in SAP S/4HANA. This feature has been removed.
You can no longer maintain the following fields in transaction BP (Business Partner
Maintenance):
Personnel Number (BUS000EMPL-EMPLOYEE_ID)
User (BUS000EMPL-USERNAME), for example, shown for role category WFM001
(Resource)
Internet User (BUS000EMPL-INTERNETUSER), for example, shown for role
category BUP005 (Internet User)
You can no longer assign the roles belonging to the following role categories in
transaction BP:
Employee (BUP003)
Freelancer (BBP010) → Contingent worker
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 82
External Resource / Service Performer (BBP005) → Contingent worker with
additional supplier relation (staffed from external supplier)
Collaboration Business User (BUP012)
Resource (WFM001) → Only needed for SAP Portfolio and Project Management
(component PPM-PFM-RES).
This means you have to create the business partners in one of the mentioned role
categories. (New Procedures see section How to create Business Users in SAP
S/4HANA)
Existing business partners cannot be expanded by the following role categories later on:
Employee, Freelancer, Service Performer. The reason is business partners with the
referenced roles have special behavior regarding:
Authorization management (driven by GDPR/DPP requirements)
Replication/distribution (no replication from SAP S/4HANA to any system)
For business partners which are assigned to one of these role categories, the fields of the
following field groups cannot be maintained via transaction BP or the customer/supplier
master Fiori UIs (independent from whether HCM integration is active or inactive):
Field group 1: Partner Number (+ Role for Change Doc. Display)
Field group 8: Form of Address
Field group 9: Bank Details (for bank detail’s ID HC*)
Field group 25: Person: First Name
Field group 26: Person: Academic Title
Field group 29: Person: Correspondence Language
Field group 30: Person: Complete Name Line
Field group 33: Person: Gender
Field group 38: Person: Birth Name
Field group 41: Person: Middle Name
Field group 43: Person: Initials of Person
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 83
Field group 54: Person: Last Name
Field group 61: Address: Address Usage (HCM001, HCM002). Note that the address
data can be edited in transaction BP but will be overwritten by the periodically
scheduled sync report /SHCM/RH_SYNC_BUPA_FROM_EMPL.
Workplace address (table MOM052) attributes such as phone number or email address
are not displayed in transaction BP. There are no plans to enhance transaction BP as of
now. Please use transaction SU01 to display the workplace address attributes.
Relationships of relationship category BUR025 (Service Provider) cannot be maintained
for roles of role category BBP005 (Service Performer).
Business partners which are assigned to one of these role categories cannot be maintained
using SAP Master Data Governance for business partners, customers or suppliers.
The usage of such workforce business partners in SAP Master Data Governance is also
restricted:
In partner function maintenance: Only the ID of the workforce business partners is
visible, and navigation to that business partner is not possible.
In business partner relationships: Relationships to workforce business partners are not
visible and thus can’t be maintained.
Limitations - Human Capital Management (HCM)
In case of multiple employments (concurrent / global employment / country transfer) only
the main employment is allowed to have a user assigned. Additional user assignments are
not allowed.
HCM Integration active or inactive: What does it mean?
HCM integration active means that you rely on the HR mini master (HR infotype based
PERNR data model including the PA-Tables). This HR mini master can be locally
maintained (for example via transaction PA30 or PA40) or via real integration scenarios
with SAP SuccessFactors Employee Central or an external (third party) HCM system.
If you don't need the HR mini master you should deactivate HCM integration.
Based on the HCM integration, business users are handled the following way:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 84
If the HCM integration is active, it is mandatory to schedule the sync report
/SHCM/RH_SYNC_BUPA_FROM_EMPL regularly as a background job so that
the business users are automatically synchronized with the PA-Tables.
You can maintain business users via
Transaction PA30 or PA40
HCM integration.
If the HCM integration is inactive, you can maintain business users via
Fiori app Maintain Employees
Fiori app Maintain External Resources
SOAP Service ManageBusinessUserIn
Report RFS4BPU_IMPORT_BUSINESS_USER.
An example of why we need the HCM integration:
For using the standard SD partner functions for employees, it is necessary to maintain the
employees with the features of the HCM compatibility pack in SAP S/4HANA.
It is not sufficient to maintain persons without active HCM integration (see SAP
Note 2763781).
HCM Integration Switch (System Table T77S0)
Description
Group
(GRPID)
Sem. abbr.
(SEMID)
HCM Integration
inactive
HCM Integration
active
Activate HCM
Integration
HRALX
HRAC
SPACE (Blank)
X
Integration P-BP
Activated
HRALX
PBPON
OFF
ON
HCM Integration for External Resources (BBP005) is set by the External Resources
Switch. It interacts with the HCM Integration Switch as follows:
External Resources Switch (System Table T77S0)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 85
Description
Group
(GRPID)
Sem.
abbr.
(SEMID)
HCM
Integration
inactive
HCM
Integration
inactive
HCM
Integration
inactive
HCM
Integration
active
Activate
External
Resources
Switch
HRALX
PEXON
OFF
OFF
ON
ON
Activate
HCM
Integration
HRALX
HRAC
SPACE (Blank)
X
SPACE (Blank)
X
Integration
P-BP
Activated
HRALX
PBPON
OFF
ON
OFF
ON
How to create Business Users in SAP S/4HANA - HCM Integration is Active
The HR mini master is the origin of business users (see HCM simplification SAP Note
2340095). The user assignment in the HR mini master has to be maintained in infotype
105 subtype 0001.
The creation of business users is managed by the periodically scheduled sync report
/SHCM/RH_SYNC_BUPA_FROM_EMPL. This report performs the following steps:
Creation of business partner in one role of the role categories Employee (BUP003),
Freelancer (BBP010) or External Resource / Service Performer (BBP005) with
private address
bank details
workplace address
customer/vendor related data (see Customer Vendor Integration [CVI])
relationships
Assignment of SU01 user. If the user doesn't exist, then the assignment takes place
once the SU01 user is created.
Errors of the sync report are stored in the application log. The application log can be
accessed via transaction SLG1 (or SLGD) for object SHCM_EE_INTEGRATION,
Subobject BUPA_SYNC (filter via External ID field to Personnel Number PERNR).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 86
Exception:
The creation of Collaboration Business User (BUP012) and Resource (WFM001) does
not work with sync report /SHCM/RH_SYNC_BUPA_FROM_EMPL. They can only be
created by using the following Fiori apps:
Fiori
ID
App Title
Business
Partner Role
Category
As Of
Release
Comments
F4911
Maintain
Collaboration
Users
BUP012
2020
FPS01
F3505
Maintain
Resources
WFM001
1809
FPS01
Only needed for SAP Portfolio and
Project Management (component
PPM-PFM-RES).
How to create Business Users in SAP S/4HANA - HCM Integration is Inactive
There are three options to create business users:
Business users can be created in SAP S/4HANA by using the following Fiori apps
(including CSV import for mass processing):
Fiori ID
App Title
Business
Partner Role
Category
As Of
Release
Comments
F2288A
Maintain
Employees
BUP003
2020
FPS01
F2288
Maintain
Employees
BUP003
1709
FPS02
Replaced by Fiori app F2288A.
F4911
Maintain
Collaboration
Users
BUP012
2020
FPS01
F3505A
Maintain External
Resources
BBP005
2020
FPS01
F3505
Maintain
Resources
WFM001
1809
FPS01
Only needed for SAP Portfolio and
Project Management (component
PPM-PFM-RES).
For mass maintenance, you can also use the report
RFS4BPU_IMPORT_BUSINESS_USER (As of SAP S/4HANA 1809). For SAP
S/4HANA 1610 you can use report RFS4BPU_EMPLOYEE_UPLOAD - see
SAP Note 2567604.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 87
SOAP Service ManageBusinessUserIn - can be set up via SOA Manager (Transaction
SOAMANAGER).
Maintenance of the Business User Workplace Address
There are three possible application areas to maintain the workplace address of the
business user:
Human Resources (HR)
Business Partner Management (BP)
User Management (US)
SAP S/4HANA 1709 FPS02 provides a configuration view that defines the maintenance
source of the workplace address attributes. SAP delivers a default proposal for both
variants, HCM integration active/inactive. See SAP Note 2548303 for details. This
configuration ensures that updates to the workplace address are restricted to one
dedicated application area.
The configuration view TBZ_V_EEWA_SRC can be set via Transaction SPRO (SAP
Reference IMG) Under 'SAP Business Partner' at node 'Additional customizing for SAP
Business Partner' (see SAP Note 2591138).
The configuration view has the following constraints:
If a field is configured for the application area User Management and the Central
User Administration (CUA) is active, the maintenance rules of the CUA
apply. (Transaction SCUM)
If the HCM integration switch is active, BP is not applicable as maintenance source.
If the HCM integration switch is inactive, HR is not applicable as maintenance
source.
The location part of the workplace address (company address - transaction SUCOMP)
is not part of configuration view TBZ_V_EEWA_SRC because it can only be
maintained by User Management. (See SAP Note 2571544)
Conversion
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 88
If HCM integration is active and the conversion from SAP Business Suite to SAP
S/4HANA is done, employees are automatically converted to business users via the
periodically scheduled sync report /SHCM/RH_SYNC_BUPA_FROM_EMPL.
If HCM integration is inactive:
Business partners that exist in an ERP system with user linkage via table HRP1001
from BP-CP-US are automatically converted to business users in SUM-Phase as
of SAP S/4HANA 1809 (see conversion report
RFS4BPU_CONVERT_BUSINESS_USER).
Business partners that exist in an ERP system with user linkage via table BP001 are
automatically converted to business users in Silent Data Migration (SDM) as of
SAP S/4HANA 2020 (see class CL_SDM_BUPA_BPU_BP001).
How to Determine Relevance
Simplification item S4TWL - Business User Management is relevant for all SAP
S/4HANA conversion customers.
2.35 S4TWL - Generic Check for SAP S/4HANA Conversion and Upgrade
Application Components:CA-TRS-PRCK
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2618018
S4TWL - Generic Check for SAP
S/4HANA Conversion and Upgrade
Symptom
You are planning to do
a system conversion from SAP ERP 6.0 or SAP S/4HANA Finance to SAP
S/4HANA
or a release upgrade SAP S/4HANA to a higher SAP S/4HANA release
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 89
and want to learn about important things to know, critical preparation activities and
checks to be done, which are directly related to the preparation of the the system
conversion or upgrade.
Solution
Unlike other Simplification Items, this Simplification Item does not describe a specific
functional or technical change in SAP S/4HANA. But it is a collector for various generic,
technical checks which need to run before a conversion or upgrade in SAP S/4HANA and
which could affect any customer system - irrespective of the specific SAP S/4HANA
target release. Many of these checks are not even SAP S/4HANA specific, but are
checking for constellations which were already considered to be inconsistent in SAP ERP
and could also have caused issues during an SAP ERP release upgrade.
As of now the check class CLS4SIC_GENERIC_CHECKS for this Simplification
Item contains the following generic checks:
Check for orphaned client dependent data
All client dependent data in a system must be associated with a client
which officially exists in the system (in table T000). In case a client was
improperly / incompletely deleted in the past, this might lead to the
situation that orphaned, client dependent data exists in a system, which is
no longer associated to a registered client. This can cause issues during
lifecycle processes like upgrades and system conversions. Hence the check
class will do a heuristic check as of SAP S/4HANA 1809, whether there is
any orphaned, client dependent data in your system and raise a
corresponding warning. While not mandatory, it's highly recommended to
clean this up before a system conversion or release upgrade.
To avoid long check runtime, the check is only looking for usr02 (user
master data) records which do not belong to a client that exists in the
system. In order to further analyze to what extent orphaned, client
dependent data exists in your system, for those clients mentioned in the
check message, you can do additional manual checks on other commonly
used, client dependent tables. e.g. if the check did report orphaned data in
client 123, you can go to DBACOCKPIT=> Diagnostics => SQL Editor
and run the following SQL "SELECT * FROM <table name> WHERE
mandt = 123" for tables like MARA, BSEG, VBAK, EKKO, MARC,
MARD...
Depending on whether you also find data in these other tables for this non-
existent client, you can decide, whether a cleanup activitiy is required.
The recommended approach for cleaning up such orphaned client data is,
to first recreate the client for which orphaned data exists, then logon to this
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 90
client and properly delete it with transaction SCC5. But before always
check, if this orphaned data is indeed no longer required - the technical
possibility to have client dependant data without an associated client is
sometimes misused in consulting projects or by customer specific/3rd
party coding e.g. to have "hidden" client backups in the system or for data
replication purposes. To be on the safe side, keep a system backup from
before deleting the data.
In addition the check also identifies clients that have no
data but still an entry in T000. In such a case the orphaned T000 entry can
be deleted with transaction SCC4.
Existence and syntax check for check classes
Checks, whether the other check classes and related objects ( XS4SIC_* /
CLS4SIC_* ) of the Simplification Item Check framework exist in the
system and if they are syntactically correct. This check might prompt you
to manually reactivate some objects or install specific notes, in case any
issues are found.
Check for inconsistent entries in tables TNIW5 / TNIW5W
Please see SAP Note 1484142 for further information.
Check for inconsistent entries in tables TBP2B / TFB03T
Please see SAP Note 2749796 for further information.
In addition, this Simplification Item serves as an anchor for assigning custom code
check related content (see SAP note 2241080), which is not related to any
technical or functional changes in SAP S/4HANA. Most notably the deletion SAP
development objects from the SAP S/4HANA codeline which are unused /
orphaned. Therefore, in case this note is mentioned in the result of SAP
S/4HANA specific ATC checks, please remove all usages of the related SAP
objects from your custom code. There are no specific replacements for these
objects.
Other Terms
SAP S/4HANA, Generic Checks, Simplification Item
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 91
2.36 S4TWL - Removal of Add-On CTS_PLUG
Application Components:BC-CTS-TMS-CTR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2820229
S4TWL - Add-On CTS_PLUG
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case if add-on CTS_PLUG
is installed in the system.
Reason and Prerequisites
CTS_PLUG, as an add-on, is neither required nor support in S/4HANA contexts.
Solution
Description & Business Process related information
The add-on CTS_PLUG is no longer requried in SAP S/4HANA system contexts, as all
coding changes have been migrated back into the basis of S/4HANA. Before a
conversion to S/4HANA, on-premise addition can be performed, CTS_PLUG needs to be
uninstalled. Please refer to note 2630240 for more details.
Other Terms
cCTS, central CTS, CTS Server Plugin
2.37 S4TWL - Removal of obsolete Data Modeler (SD11) content
Application Components:XX-SER-REL, BC-DWB-TOO-DMO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2850096
S4TWL - Removal of obsolete Data
Modeler (SD11) content
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 92
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Along with SAP R/3 Enterprise Edition 4.6C for some R/3 modules Data Modeler
(SD11) content was delivered by SAP. Later on this was no longer updated or
complemented with additional data models. Hence this content gradually became
outdated during SAP R/3 Enterprise Edition 4.7, SAP ERP 5.0 and SAP ERP 6.0
timeframe. The meanwhile obsolete SD11 content has been removed in SAP S/4HANA.
There are currently no plans to deliver new content for SD11.
Business Process related information
No impact on business processes is expected.
Required and Recommended Action(s)
Inform your users who did access this SD11 content in the past about this change.
For information about major data model changes in SAP S/4HANA (compared to SAP
ERP 6.0) you can alternatively check the following notes and the further information
linked therein:
SD/Pricing:
2267306
2267308
MM-IM:
2206980
2337383
FIN:
2270333
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 93
This information is relevant for you, if some of your users did access the application
specific content in Data Modeler (SD11) for reference purposes. See ST03N usage data
for transaction SD11.
Other Terms
SD11, Data Modeler content
2.38 S4TWL - Simplified data model in Joint Venture Accounting
Application Components:CA-JVA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2967210
S4TWL - Joint Venture Accounting on
ACDOCA
Symptom
You are planning to do a system conversion to SAP S/4HANA with Joint Venture
Accounting. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Reason and Prerequisites
Renovation
Solution
Business Value
As of OP1909, JVA customers can optionally run the Joint Venture Accounting on a new
data model that is based on the ACDOCA table ("JVA on ACDOCA"). The new data
model has several advantages compared with the classic JVA design: (a) The overall
footprint of the JV accounting data is greatly reduced. (b) Automatic re-conciliation
between FI, JVA and CO is guaranteed. (c) JVA can utilize the new functionalities
introduced through the ACDOCA design, for example: up to 10 local currencies; fast
retrieval of aggregated data; new reporting tools.
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 94
The classic JVA is based on a couple of separate database tables that basically contained
copies of the documents posted to the FI and CO ledgers (plus additional JVA-only
documents). When the new JVA_ON_ACDOCA business function is switched on in an
S4HANA system, these separate tables are not used, anymore. Instead, all JVA
processing is based on the ACDOCA table ("Universal Journal Entries" - UJE).
Important remark: It is not mandatory to run JVA on the new data model in S4HANA,
that is, the classic data model can still be used in S4HANA. However, if the new data
model is not used right from the start, there is no standard solution by SAP to migrate
from classic JVA to JVA on ACDOCA at a later point of time!
Business Process related information
Although the underlying data model of JVA on ACDOCA has changed fundamentally
(which required a re-development of all JVA month-end processes), the general business
logic remains the same. Even the old transaction codes can still be used (when using the
SAP GUI). Major changes happened in three areas only: (a) The Venture Bank Switching
transactions ared replaced by Funding transactions that make use of the special
ACDOCA featuers. (b) The reconciliation transaction GJ90 is not required, anymore. (c)
The JVA variants of FI valuation transaction are not required anymore (GJ91, GJNO);
instead, the corresponding FI transaction can and need to be used; these were enhanced to
cover the JVA requirements.
The main difference regarding user experience is in the JVA reporting where the old SAP
GUI-based reporting transaction are replaced by Design Studio-based FIORI apps that
can be accessed via the Fiori Launchpad, only.
The master data model, on the other hand, has not been changed; just a few options had
to be added to adapted to meet the required of the above-mentioned functionalities. The
maintenance transactions have changed in the related areas only.
Required and Recommended Actions
Before the conversion process is started, the following checks should be executed:
The main pre-requisite for the migration to JVA on ACDOCA is the NewGL-JVA
integration. That is, a system with the classic JVA without NewGL integration
can NOT be migrated to JVA on ACDOCA. So, if your system is still based on
classic GL with classic JVA, you need to migrate to the JVA-integrated NewGL
first. For detailed information on the supported scenarios, see note 2927005.
A technical consistency check of the JVA ledgers should be executed by running the
reports RGUSLSEP (to check the summary table consistency) and RGUREP11
(to check the object number consistency). For more information, see note 764523.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 95
How to Determine Relevancy
To check the relevancy of this simplification item, execute the following checks:
Check if the business function 'JVA' is active (via transaction SFW5).
Check if any company code has been activated for JVA (via transaction GJZA).
Other Terms
JVA, Joint Venture Accounting, migration, worklist
2.39 S4TWL - New Default Security Settings for SAP S/4HANA
Application Components:XX-PROJ-CON-SEC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2926224
Collection Note: New security settings
for SAP S/4HANA and SAP BW/4HANA
using SL Toolset and SUM
Symptom
This is the central entry point for all information around new secure-by-default settings
for SAP S/4HANA.
You want to know more details about the new secure-by-default settings for SAP
S/4HANA systems. During SAP S/4HANA provisioning you were asked to review the
profile parameters set by SL Toolset (e.g. SWPM, SUM).
Reason and Prerequisites
You are using the latest SL Toolset or SUM. This will introduce the latest recommended
security settings for SAP S/4HANA systems and SAP BW/4HANA systems.
From SAP S/4HANA 1909 onwards and SAP BW/4HANA 2021 onwards, new
installations (with SWPM), system copies (with SWPM) and system conversions from
SAP ERP to SAP S/4HANA (with SUM) will automatically receive the recommended
security settings. An opt-out is possible for the security relevant profile parameters, but
not recommended from SAP side.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 96
In SAP S/4HANA and SAP BW/4HANA upgrades (with SUM), security settings are not
adjusted automatically. In some cases, preparations are necessary before configurations /
parameters can be switched to secure values in upgraded systems. That’s why
configurations / parameters are not changed during the upgrade process. Though it’s
recommended to also apply the updated security settings in system which have been
upgraded from older SAP S/4HANA and BW/4HANA releases.
Solution
For more details, how the security settings change in each SAP S/4HANA and SAP
BW/4HANA release and what you need to do and know about these changes from system
operations point of view, please refer to the release specific SAP notes linked in this note.
The attached spreadsheet contains the list of all security settings that are
recommended. The attached spreadsheet was updated with the list of security settings for
SAP S/4HANA 2022.
Other Terms
Software Provisioning Manager (SWPM), SWPM, SAPinst, SL Toolset, security, profile
parameter, Software Update Manager (SUM), SUM, security, conversion, upgrade
2.40 S4TWL - Extended Check of Output Device in Output Control
Application Components:CA-GTF-OC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3093397
S4TWL - Extended Check of Output
Device in Output Control
Symptom
You upgrade to SAP S/4HANA 2021 release and use SAP S/4HANA output control as
output solution.
Reason and Prerequisites
In the SAP S/4HANA 2021 release, the output solution SAP S/4HANA output control
introduces an enhanced check for output devices defined within the spool administration,
which are used for printing of output request items.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 97
This simplification item is relevant for you if there already exist output control items for
channel PRINT which should be still processed after the upgrade (e.g. as the status is 'In
Preparation', etc.). If such an output control item uses an output device with now
invalidated settings, any output action fails after the upgrade to SAP S/4HANA 2021.
Refer to note 3057330 for details on the enhanced check.
Solution
Business Process related information
Talking about output devices, it is worth mentioning two points in advance:
Output devices are defined cross-client, i.e. a change in spool administration
immediately affects all working clients
Output devices are used of course not only in output control, but within the complete
business suite, and a change in spool administration does affect the complete
business suite
Required and Recommended Action(s)
To securely upgrade to SAP S/4HANA 2021 from any lower SAP S/4HANA release, the
Simplification Item Check (SIC) has to be carried out to detect such invalidated output
devices. Once detected, depending on your business data (see bullet points above), there
are two possibilities to ensure a smooth upgrade:
Adapt the detected output devices in spool administration
Create new output devices and exchange the detected output devices for relevant
output request items (transaction data) and printer settings (configuration data)
For details refer to note 3057330.
Please notice that all errors of this simplificaction item are skippable, e.g. because the
detected output control items are outdated, or in a state that there will be no further
processing, or in a non-relevant client. Another option could be to accept the fact, that
some output control items of channel PRINT will run into the output device error after
the upgrade and to treat these cases manually. This could come in handy if there is only a
low number of detected output control items.
However, especially if the findings point to a structural problem, i.e. an output device
became invalid which is heavily used within relevant output control items through all
working clients, it is highly recommended, to become active before the upgrade.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 98
SAP S/4HANA output control, Printing, Print Device, Printing Device, Device Type,
CLS4SIC_APOC_CHK_ITEM_DEVICE, S4SIC_APOC_CHK_OPD_DEV
2.41 S4TWL - Deprecation of Design Studio Apps
Application Components:CA-UX
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3133221
S4TWL - Deprecation of Design Studio
Apps
Symptom
You are doing an upgrade from a lower to a higher SAP S/4HANA release and are using
the functionality described in this note. The following SAP S/4HANA Simplification
Item is applicable in this case.
Solution
Description
As of SAP S/4HANA 2021 SAP Design Studio apps have been deprecated. This includes
all Finance apps based on the Design Studio technology. For all deprecated SAP Design
Studio apps Web Dynpro data grid apps exist as alternatives. For a list of all deprecated
SAP Design Studio apps and their alternatives refer to SAP note 3081996.
As of SAP S/4HANA 2022 most of these SAP Design Studio apps have been set to
obsolete. This includes most Finance apps based on the Design Studio technology. Refer
to SAP note 3170381 for more information.
Business Process related information
Deprecated SAP Design Studio apps are no longer available by default on the SAP Fiori
launchpad. However, you can still use them and also locate them using the app finder
until they are deleted. Nevertheless, we strongly recommend switching to the SAP Web
Dynpro successor apps as soon as possible. The Web Dynpro apps are already the default
tiles on the SAP Fiori launchpad.
Obsolete SAP Design Studio apps are no longer supported and have been deleted from
the system.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 99
You can continue to use Design Studio reports that you created using the View Browser.
However, you can no longer create new ones. We recommend creating Web Dynpro
reports instead.
For more information refer to the What's New Viewer article on help.sap.com and
note 3112220 - FAQ: Web Dynpro Apps and Design Studio Apps in SAP S/4HANA and
SAP S/4HANA Cloud.
Required and Recommended Action(s)
For deprecated SAP Design Studio apps:
Evaluate the SAP Web Dynpro apps as alternatives to the SAP Design Studio apps
and decide when to switch to the successor apps. However, this need to happen
latest before the next release upgrade of your SAP S/4HANA system.
If you use custom design studio apps note that they cannot be migrated automatically
to Web Dynpro apps. You need to recreate them as Web Dynpro reports using the
View Browser. Refer to SAP note 3081996 for details.
For obsolete SAP Design Studio apps:
Switch to the SAP Web Dynpro apps provided as alternatives to the SAP Design
Studio apps latest with your upgrade.
Other Terms
SAP S/4HANA, Upgrade, Design Studio Apps, WebDynpro Grid
2.42 SWTL - Deprecation of Obsolete Data Handling Tool
Application Components:CA-EPT-ODH, BC-CCM-ODH
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
3335020
New Obsolete Data Handling
Framework in SAP S/4HANA
Business Impact
3358954
SWTL - Deprecation of Obsolete Data
Handling Tool
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 100
You are doing an upgrade from a lower SAP S/4HANA release to release 2023 (or
higher) and have been already using the obsolete data handling tool (report/transaction
code ODH_Data_processing) in the past for deleting obsolete data that remains after the
conversion of your system from SAP ERP to SAP S/4HANA 2023, or after a previous
SAP S/4HANA upgrade. The following SAP S/4HANA Simplification Item is applicable
in this case.
Reason and Prerequisites
With SAP S/4HANA release 2023 a new obsolete data handling tool is delivered.
The old tool (report/transaction code ODH_Data_processing) is deprecated and can only
be used with SAP S/4HANA release 2023 to view the logs of already finished cleaning
runs.
We plan to make it obsolete in favor of the designated successor functionality as of
release SAP S/4HANA 2025.
For more details on the old obsolete data handling tool, see SAP Note 2661837 .
Solution
All new obsolete data cleaning activity must be done with the new, class-based
tool (transaction code SODH).
For information on how to enable and use this tool in the productive SAP
S/4HANA 2023 system, see SAP Note 3335020 .
The SAP note xxxxxx describes to migration of ODH deletion content and log files to the
successor functionality.
Other Terms
SAP S/4HANA, System Conversion, Upgrade, deprecation, ODH,
ODH_Data_processing
2.43 S4TWL - CATSXT
Application Components:CA-TS-SV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3150537
S4TWL – CATSXT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 101
Symptom
You are using the functionality “Cross Application - Time Sheet Service Provider” in
release SAP S/4HANA on-premise 2022 or lower. SAP deprecated this functionality
with release SAP S/4HANA on-premise 2022 and plans it will not be available with
release SAP S/4HANA on-premise 2023 or higher. SAP intends in particular that the
transaction CATSXT will not function with release SAP S/4HANA on-premise 2023 or
higher. Up to and including release SAP S/4HANA on-premise 2022 CATSXT is,
however, still fully available.
Reason and Prerequisites
SAP plans to make an alternative solution for “Cross Application - Time Sheet Service
Provider” available.
Solution
Description
SAP intends to deliver a future solution for customers which currently use CATSXT in
S/4HANA on-premise 2022 or lower. SAP does not commit to deliver this future
solution. SAP plans for this with re-use of the database table CATSDB. This future
solution is not a “successor solution” for CATSXT as its capabilities will be different:
The details of its functions and features will be communicated via the SAP Product
Roadmap.
Until the new solution will be available the Fiori App “My Timesheet” with its
configuration and enhancement options may be used. There is also the Cross-Application
Time Sheet (CATS), which is a cross-application tool for recording working times and
tasks.
Further details will be published in this note in the future.
Business Process related information
Transactions not available in SAP S/4HANA on-premise 2023 or
higher
CATSXC
CATSXC_CHECK
CATSXC_COMP_DTL
CATSXT
CATSXT_ADMIN
S_AL0_96000015
S_ALR_87100621
S_ALR_87100718
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 102
S_ALR_87100771
S_ALR_87100775
S_ALR_87100776
S_ALR_87100782
S_ALR_87100834
S_P00_07000122
S_P00_07000322
Other Terms
CA-TS-SV, CATSXC, CATSXT, CATSXT_ADMIN, CATSXT_COMP_DTL,
S4TWL: S/4 HANA Transition Worklist Item.
2.44 S4TWL - OUTPUT MANAGEMENT
Application Components:CA-GTF-OC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2470711
S4TWL - OUTPUT MANAGEMENT
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Business Value
SAP S/4HANA output management is a modern solution for output related tasks. It takes
the functionality from existing SAP output solutions and adds additional features
like seamless integration into Fiori apps, flexible email configuration and email templates
as well as the support of SAP Cloud Platform Forms by Adobe.
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 103
SAP S/4HANA output management comes as an optional part of SAP S/4HANA. There
are no mandatory actions for customers using this framework. All existing output
management solutions like SD Output Control, FI Correspondence, FI-CA Print
Workbench, and CRM Post-Processing are still supported. There are currently no plans to
deprecate any of these solutions.
Business Process Related Information
Business processes can benefit from one common output management solution across the
product. Users always have the same look and feel and functionality, no matter if they
perform output related tasks in Logistics, Procurement, or Financials. Also, an
administrator only needs to setup and configure one output management framework. The
SAP S/4HANA output management also offers at many places integration to standard
extensibility, allowing business users to extend the solution without the need for an
implementation project.
Required and Recommended Action(s)
Business applications that already adopted to SAP S/4HANA output management should
offer a switch to enable or disable the use of it.
Required actions for all business applications in scope:
Define the active output management framework for the individual business
applications.
Open the customizing activity 'Manage Application Object Type Activation' under
SAP Reference IMG -> Cross-Application Components -> Output Control.
Set the desired value in the column Status for all available Application Object Types
by either changing an existing entry or by adding new entries.
All Application Object Types not listed in this customizing activity should have
linked their corresponding simplicification item to SAP Note 2228611 providing
individual information on how to enable or disable SAP S/4HANA output
management. Please check the list of SAP Notes under section 'References' in this
note.
If a business application is not listed in the customizing activity and has no
simplification item or does not mention any changes regarding output
management in its existing simplification item, it is likely not using SAP
S/4HANA output management.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 104
In case SAP S/4HANA output management is enabled, please refer to the SAP Note
2228611 for more information and related notes for the technical setup and
configuration.
In case SAP S/4HANA output management is not enabled or disabled, please setup
the according other output management solution for the particular business
application.
How to Determine Relevancy
The SAP S/4HANA output management might be relevant for you if:
The existing functionality described in SAP Note 2228611 fully meets your business
requirements. According limitations / differentiations are listed in this note and
linked subsequent SAP Notes. Additional functionality for SAP S/4HANA output
management will only be delivered within a new release of SAP S/4HANA.
You want to use SAP delivered Fiori apps including output functionality.
The business applications of your business scope already adopted to SAP S/4HANA
output management allowing the use of one output framework along the business
processes.
The SAP S/4HANA output management might not be relevant for you if:
You want to continue using your existing output management setup in SAP
S/4HANA.
You require functionality that is not covered by SAP S/4HANA output management.
Other Terms
OM, Output Management, Output Control
2.45 S4TWL - SAP HANA LIVE REPORTING
Application Components:XX-SER-REL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270382
S4TWL - SAP HANA Live Reporting
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 105
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
SAP HANA Live provides reporting capabilities for Business Suite and Suite on HANA
customers. In S/4HANA, database tables have changed in many areas. Thus, the Hana
Live Calc Views will not work on those changed structures. In addition, 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 either to be adjusted
manually to the changed DB-table structures or to be rebuilt manually with CDS Views
in SAP S/4HANA.
Business Process related information
It should be possible to rebuild all existing reporting scenarios with CDS Views.
Limitations might exist with respect to consumption.
Required 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).
Related SAP Notes
Custom Code related
information
If the customer copied calc views delivered by SAP or created user-
defined calc views on top of SAP delivered views, those
potentially need to be redone to reflect changed DB-table structures
(in case there are some).
2.46 S4TWL - ENTERPRISE SEARCH
Application Components:BC-EIM-ESH
Related Notes:
Note Type
Note Number
Note Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 106
Business Impact
2318521
S4TWL - Enterprise Search
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
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
1511
ESH_SEARCH
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.
Related SAP Notes
Custom Code related information
SAP Note: 2227007
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 107
2.47 S4TWL - Duplicate request entries in Output Management
Application Components:CA-GTF-OC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2679118
Simplification item check for duplicate
output request entries
Symptom
Upgrade to SAP S/4HANA 1809 On Premise release
Reason and Prerequisites
SAP S/4HANA 1809 On Premise release introduces a new seconday key index to the
following tables:
1. APOC_D_OR_ROOT
2. APOC_D_OR_ITEM
3. APOC_D_OR_ITEM_A
4. APOC_D_OR_ITEM_E
It is necessary to make sure that there are no multiple database entries in these tables that
match with the new unique key. If there are any duplicate entries, the new seconday key
index constraint cannot be added to the tables.
Therefore, to upgrade to SAP S/4HANA 1809 from any lower S/4HANA releases, the
Simplification Item Check (SIC) has to be carried out to detect these duplicate entries.
Once detected, duplicate entries are to be deleted from the tables to ensure a smooth
upgrade.
Solution
If there are duplicate entries (multiple entries in the database matching key constraints) in
the following tables, the SIC will detect them:
1. APOC_D_OR_ROOT
2. APOC_D_OR_ITEM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 108
3. APOC_D_OR_ITEM_A
4. APOC_D_OR_ITEM_E
Duplicate table entries detected by SIC must be deleted from their corresponding tables.
Please go to the table via transaction se16n. Enable &sap_edit. Filter the entries based on
the key fields displayed by SIC.
You may now analyze the entries and delete the duplicate ones.
2.48 S4TWL - Ariba Network Integration
Application Components:BNS-ARI-SE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2341836
S4TWL - Ariba Network Integration in
SAP S/4HANA on-premise edition
Symptom
You are planning a system conversion from SAP ERP to SAP S/4HANA on premise. The
information below is important.
Solution
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.
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 integration of processes and cXML
messages listed below are not nativly supported by SAP S/4HANA.
Please take into account that there will be no further development of new features or
functionalities for the S/4HANA native Ariba Integration. You should consider a
transition to the SAP Ariba Cloud Integration Gateway as soon as possible. More details
are provided in the note 2705047 (Roadmap for Ariba Integration Solutions).
The preferred approach to migrate the ERP add-on of Ariba Network Integration to the
S/4HANA on-premise edition would be first to convert this add-on to the SAP Ariba
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 109
Cloud Integration Gateway and only then start the ERP system converion. See Migrating
from SAP Business Suite Add-On.
Business Process Related Information
Note the restrictions for SAP S/4HANA, on-premise edition 1511 listed below.
The following processes are not supported:
Processing of CC invoices (invoices transfered from SAP S/4HANA to Ariba
Network)
Service procurement/invoicing process
Payment process
Discount management process
Update of Advanced Shipping Notifications
Ariba Supply Chain Collaboration e.g.
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
Quality Management Process (e.g. Quality Notificiaton, Quality Inspection,
Quality Certificates...)
The following cXML message types are not available:
ReceiptRequest
CopyRequest.InvoiceDetailRequest
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 110
ServiceEntryRequest
PaymentRemittanceRequest
PaymentRemittanceStatusUpdateRequest
PaymentProposalRequest
CopyRequest.PaymentProposalRequest
ProductActivityMessage
ComponentConsumptionRequest
ProductReplenishmentMessage
QuoteRequest
QuoteMessage
QualityNotificationRequest
QualityInspectionRequest
QualityInspectionResultRequest
QualityInspectionDecisionRequest
ApprovalRequest.ConfirmationRequest
OrderStatusRequest
Note the restrictions for SAP S/4HANA, on-premise edition 1610, 1709, 1809 and
1909 listed below.
The following processes are not supported:
Processing of FI - CC invoices (transfered from SAP S/4HANA to Ariba Network)
Update of Advanced Shipping Notifications
Ariba Supply Chain Collaboration e.g.
Processing of scheduling agreement releases
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 111
Consignment process
Subcontracting process
Processing of forecast data
Multi-tier purchase order processing
Purchase order return items processing
Integration processes for suppliers
Quality Management Process (e.g. Quality Notificiaton, Quality Inspection,
Quality Certificates...)
The following cXML message types are not available:
ProductActivityMessage
ComponentConsumptionRequest
ProductReplenishmentMessage
QualityNotificationRequest
QualityInspectionRequest
QualityInspectionResultRequest
QualityInspectionDecisionRequest
ApprovalRequest.ConfirmationRequest
OrderStatusRequest
Required and Recommended Action
Conversions to 1511 or 1610: 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.
Conversions 1709 and later: Implement the master conversion pre-check SAP Note
"2502552 - S4TC - SAP S/4HANA Conversion & Upgrade new Simplification
Item Checks" and follow the instructions in this note.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 112
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.
Regarding customer code relevant changes please read the following SAP
Note "2406571 - SAP S/4HANA Simplification: Ariba Network Integration
(custom code relevant changes)"
If pre-checks fail, see the following SAP Note: "2246865 - S/4 Transition: Activities
after failed PreChecks".
Access SAP Note: "2341836 - S4TWL - Ariba Network Integration in SAP
S/4HANA on-premise edition", download the following documents, and follow
the steps described.
Before the
conversion: S4H_CONV_INTEGRATION_ARIBA_NETWORK_PREP
C.PDF
After the conversion:
S4H_CONV_INTEGRATION_ARIBA_NETWORK_POSTC.PDF
2.49 S4TWL - INTERNET PRICING AND CONFIGURATOR (SAP IPC)
Application Components:AP-CFG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2318509
S4TWL - INTERNET PRICING AND
CONFIGURATOR (SAP IPC)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 113
currently used alternative functionality like ABAP-based configuration (LO-VC) can be
used in SAP S/4HANA.
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.
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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 114
- 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.
Related SAP Notes
Custom Code related information
SAP Note: 2238670
2.50 S4TWL - JOB SCHEDULING
Application Components:BC-CCM-BTC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2318468
S4TWL - JOB SCHEDULING
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
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. Job Definitions can be customized or deactivated
via transaction SJOBREPO.
Solution
Description
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 115
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 because you want to use an own job with different report
variant.
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 or exclude certain jobs from deletion), disable SAP-delivered 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.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
IMPORTANT: Before the upgrade/migration to SAP S/4HANA (i.e. in your original
system), apply SNOTE correction from note 2499529.
This correction ensures that automatic job scheduling of Technical Job Repository in
the SAP S/4HANA system will be delayed even after the point in time when the technical
upgrade is over. In other words, it ensures that no automatic job scheduling by Technical
Job Repository occurs automatically after the conversion to SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 116
Applying the note prevents for example that jobs automatically scheduled by Job
Repository in SAP S/4HANA (this can occur once the technical upgrade phase is
over) delete valuable data (e.g. background jobs older than 14 days, spool requests that
have reached their retention period) of your old system which the customer wants to
retain after the technical upgrade phase.
Without above correction, Job Repository will schedule jobs (including
SAP_REORG_JOBS, SAP_REORG_SPOOL) directly after the end of the technical
upgrade phase, which may not be desired! For example, job SAP_REORG_JOBS
(scheduled from Job Repository) deletes all background jobs older than 14 days.
IMPORTANT: After the upgrade/migration to SAP S/4HANA, apply the correction
from note 2499529 also in your new system. This correction will ensure that
automatic job scheduling by Technical Job Repository will commence once report
BTCTRNS2 is executed by the conversion team. Be sure to have deactivated unwanted
job definitions (for example SAP_REORG_JOBS) in SJOBREPO by that time.
Other Terms
Background Jobs, Batch, Standard Jobs, SM36
2.51 S4TWL - LEGACY SYSTEM MIGRATION WORKBENCH
Application Components:BC-SRV-DX-LSM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2287723
LSMW in SAP S/4HANA on-premise
(S4CORE)
Symptom
For the data migration to SAP ERP, SAP offered the legacy system migration workbench
(transaction code LSMW). But for the migration of business data to SAP S/4HANA and
SAP S/4HANA Cloud, the SAP S/4HANA migration cockpit is the tool of choice.
LSMW is on the simplification list and the use of LSMW is restricted in the context of
data migrations to SAP S/4HANA. Even if the LSMW could be used in some areas, it
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 117
might propose incorrect migration interfaces that cannot be used in SAP S/4HANA
anymore. There is no support given in the context of data migrations to SAP S/4HANA.
This SAP Note is valid only for customers implementing SAP S/4HANA.
Reason and Prerequisites
The Legacy System Migration Workbench (LSMW) is an SAP NetWeaver tool for data
migration that was first introduced with R/2 to R/3 data migration. It uses standard
interfaces like BAPIs, IDocs, Direct Input and Batch Input programs and recordings
initially build for SAP ERP. Due to this nature, the use of LSMW is restricted in the
context of data migrations to SAP S/4HANA.
For restrictions on certain BAPIs, IDocs, Batch Input or Direct Input programs that are
used by LSMW, please get in touch with the application components directly.
Solution
The use of LSMW for data load to SAP S/4HANA is not recommended and at the
customer's own responsibility. Instead, the SAP S/4HANA migration cockpit is SAP’s
solution for data migration to SAP S/4HANA. You should always check if the object is
available with the SAP S/4HANA migration cockpit before using the LSMW.
If you still use the LSMW, you have to carefully test the processes so that you can
ensure that it is actually working for you. It might not work for you and in any case.
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). 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.
Option 1: SAP S/4HANA Migration Cockpit and Migration Object Modeler
The SAP S/4HANA migration cockpit is SAP’s recommended tool of choice for the data
migration to SAP S/4HANA and SAP S/4HANA Cloud. It provides all functions
required for the migration of business data in a new implementation and is part of SAP
S/4HANA and SAP S/4HANA Cloud.
For the migration to SAP S/4HANA Cloud, the migration cockpit is the only way to
migrate business data.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 118
For the data migration, the cockpit uses predefined migration content that is, standard
migration objects such as customers, suppliers or purchase orders to identify and transfer
the relevant data. These migration objects contain predefined mapping to facilitate the
migration.
From SAP S/4HANA 2020 and SAP S/4HANA Cloud 2008, the SAP S/4HANA
migration cockpit has the following two migration approaches:
Migrate Data Using Staging Tables (SAP S/4HANA and SAP S/4HANA Cloud)
As of Release SAP S/4HANA 1709, FPS01, the migration cockpit contains the data
transfer option using staging tables. From SAP S/4HANA 2020 and SAP S/4HANA
Cloud 2008 a new Fiori UI was introduced and since then, the file migration approach is
embedded in the Staging tables approach (“Migrate Data Using Staging Tables”,
Migrate your Data – Migration Cockpit App). This means that XML template files are
provided for every migration object and, you can use these templates to fill the staging
tables with data. Alternatively, you can fill the staging tables by using your preferred
tools (for example SAP Data Services, SDI, etc.). The SAP S/4HANA migration cockpit
creates staging tables for the migration objects that are relevant for your project and
migrates data from these staging tables to the target SAP S/4HANA system.
Migrate Data Directly from SAP System (new with SAP S/4HANA 1909, only for
On-Premise)
This new migration approach that is delivered with SAP S/4HANA 1909 allows you to
directly transfer data from SAP source systems to SAP S/4HANA. The migration cockpit
selects the migration objects in the source system with the help of predefined selection
criteria and directly transfers them to the SAP S/4HANA target system via an RFC
connection.
For more information about the direct transfer approach please refer to the SAP Help
Portal: SAP S/4HANA Migration Cockpit - Transferring Data Directly from an SAP
System
Integration of custom data:
In addition, the cockpit allows you to integrate your custom data objects into the
migration using the migration object modeler which is part of the cockpit. For example,
you can adjust the predefined standard migration objects delivered with the cockpit by
adding fields to them. As of SAP S/4HANA 1610, FPS02 in the file and staging
approach, you can also create your own custom-specific migration objects or SAP
standard objects that have not yet been included in the scope of the migration cockpit. For
the direct transfer, the migration object modeler is also available in a first version.
Required roles:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 119
For file and staging approach:
SAP S/4HANA (S4CORE):
For current information and more details about the file and staging approaches
and required roles for SAP S/4HANA (on-premise version), please see:
SAP Help Portal: SAP S/4HANA - SAP S/4HANA Migration Cockpit
Installation Guide for S/4HANA (on-premise only) available under:
https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE →
<Filter-Version> Product Documentation → Installation Guide →
7. Installation Follow-Up Activities
SAP S/4HANA Cloud (SAPSCORE):
For current information and more details about the file and staging approaches
for SAP S/4HANA Cloud and required roles, please see:
SAP Help Portal: SAP S/4HANA Cloud - SAP S/4HANA Migration
Cockpit
Installation Guide for S/4HANA (on-premise only) available under:
https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE →
<Filter-Version> Product Documentation → Installation Guide →
7. Installation Follow-Up Activities
For direct transfer approach:
For current information about the business roles needed and more details about the direct
transfer, please see:
SAP Help Portal: SAP S/4HANA Migration Cockpit - Transferring Data Directly
from an SAP System
Installation Guide for S/4HANA (on-premise only) available under:
https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE → <Filter-
Version> Product Documentation → Installation Guide → 7. Installation Follow-
Up Activities
Data Migration Objects available for the Migration Cockpit:
For a list of available migration objects that are supported with SAP S/4HANA 1909 or
higher versions, see https://help.sap.com/S4_OP_MO
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 120
For further information about data migration and the migration cockpit, see the data
migration landing page in the SAP Help Portal under https://help.sap.com/S4_OP_DM
Option 2: SAP Rapid Data Migration with SAP Data Services
SAP S/4HANA data migration content called SAP Rapid Data Migration based on SAP
Data Services software is still available and will be maintained further to migrate data
into SAP S/4HANA (on premise). But no new objects will be created. Yet, SAP will
further invest into migration content for the SAP S/4HANA migration cockpit which
already offers more migration objects than the RDS.
This package is part of SAP’s Rapid deployment solution (RDS). You can find more
information in SAP Note 2239701 - SAP Rapid Data Migration for SAP S/4HANA, on
premise edition and under the link below:
https://rapid.sap.com/bp/RDM_S4H_OP
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:
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
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.
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.
The SAP S/4HANA migration cockpit can be used in addition to the Rapid Data
Migration content.
For more information, please click the link below:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 121
https://blogs.sap.com/2016/06/21/how-to-migrate-to-sap-s4hana or check the SAP Best
Practices Explorer (https://rapid.sap.com/bp/scopeitems/2Q2)
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
Migration Cockpit versus LSMW
As mentioned earlier, the SAP S/4HANA migration cockpit is SAP’s recommended tool
of choice for data migration to SAP S/4HANA. In this section we would like to point out
a few advantages of the SAP S/4HANA migration cockpit against LSMW:
The cockpit’s preconfigured migration content significantly facilitates data migration
projects whereas the LSMW does not provide any content. Migration logic had to
be created from scratch.
The migration object modeler is a powerful and easy-to-use state-of-the-art modeling
environment that allows the creation of custom migration objects as well as the
adaptation of SAP content.
If you have any feedback regarding the SAP S/4HANA migration cockpit compared to
LSMW please feel free to share this via [email protected]
Other Terms
LSMW, Rapid Data Migration, RDS, Best Practices, SAP S/4HANA 1511, 1610, 1709,
1809 and 1909, SAP S/4HANA Migration Cockpit, SAP Data Services
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 122
3. Master Data
3.1 S4TWL - MDM 3.0 integration
Application Components:LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267295
S4TWL - MDM 3.0 integration
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist Item is applicable in this case.
Solution
Description
The MDM specific transaction codes for IDoc processing (inbound and extraction) are
not available within SAP S/4HANA, on-premise and cloud edition. The item is valid
starting with S/4 HANA release 1511 as well as for all newer releases.
Business Process related information
MDM 3.0 was discontinued. All known customer implementations have migrated to SAP
NetWeaver MDM or SAP Master Data Governance, Central Governance. All known
customer implementations have already replaced the SAP MDM 3.0 specific IDoc
processing according to SAP note 1529387 "Tables MDMFDBEVENT, MDMFDBID,
MDMFDBPR growing significantly".
Required and Recommended Action(s)
None
Related SAP Notes
General SAP Note related to Simplification Item
SAP Note: 1529387
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 123
3.2 S4TWL - SRM Product Master
Application Components:AP-MD-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267297
S4TWL - SRM Product Master
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The functional scope of SAP Supplier Relationship Management (SAP SRM) will
gradually be made available within SAP S/4HANA. The related functions will become
part of the procurement solution of SAP S/4HANA. Technically, the procurement
solution within SAP S/4HANA is not a successor to the SAP SRM components.
Therefore, the SAP SRM software components and SAP S/4HANA cannot be installed
on the same system.
For more details see Simplification Item Co-Deployment of SAP SRM.
Accordingly the SRM Product Master is not available in SAP S/4HANA, on-premise
edition 1511.
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
on-premise edition 1511
COM_PR_MDCHECK
COMC_MATERIALID_ALL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 124
COMC_PR_ALTID
COMC_PR_ALTID_BSP
COMC_PR_OBJ_FAM
COMC_PR_OBJ_FAM1
COMC_PR_RFCDEST
COMC_PRODUCT_IDX
COMC_SERVICEID_ALL
COMCMATERIALID
COMCPRAUTHGROUP
COMCPRD_BSP_ID
COMCPRFORMAT
COMCPRLOGSYS
COMCPRMSG
COMCPRTYPENRO
COMCSERVICEID
COMM_DEL_PRWB_USER
COMM_EXTRSET
COMM_HIERARCHY
COMM_IOBJ_RECATEG
COMM_MSG01
COMM_PRAPPLCAT
COMM_PRDARC
COMM_PROD_RECATEG
COMMPR_PCUI
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 125
COMMPR01
COMMPR02
CRM_PRODUCT_LOG
CRM_PRODUCT_STA
CRMCFSPRODID
Required and Recommended Action(s)
In SAP S/4HANA the COMM* tables (COMM_PRODUCT, COMM_HIERARCHY )
are no longer available .It is recommended that users archive the ABAP Basis COMM*
product master tables and proceed with the upgrade.
In a non-productive client, use reports COM_PRODUCT_DELETE_ALL to delete
products and COM_HIERARCHY_DELETE_ALL to delete hierarchies.
For productive clients, set the deletion indicator using transaction COMMPR01 and
archive the products using transaction SARA, then delete the hierarchies using
COMM_HIERARCHY.
For SRM-OneClient deployment the users should be aware that the SRM product master
data is not accessible after S/4 conversion.
3.3 S4TWL - Logistics Batch Management
Application Components:LO-BM-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267298
S4TWL - Logistics Batch Management
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 126
The following transactions related to Logistics Batch Management are not available in
SAP S/4HANA, on-premise edition 1511: MSC1, MSC2, MSC3 and MSC4. The
functional equivalent in SAP S/4HANA, on-premise edition 1511 are the following
transactions:
MSC1N Create Batch
MSC2N Change Batch
MSC3N Display Batch
MSC4N Display Change Documents for Batch
As of Release 4.6A, the maintenance of batch master data has been completely reworked
and assigned to new transaction codes. Already at this point in time it was recommended
to use the new transaction codes (MSC*N). The previous transactions and with that the
belonging program code are not available within SAP S/4HANA, on-premise edition
1511.
Business Process related information
No influence on the business process – alternatively mentioned transaction codes need to
be used.
Transaction not available in SAP
S/4HANA on-premise edition 1511
MSC1
MSC2
MSC3
MSC4
3.4 S4TWL - Product catalog
Application Components:LO-MD-PC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267292
S4TWL - Product Catalog
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 127
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Product Catalog functionality was used in the past as means of integration to web-
channel solutions.
Hybris is the strategic solution to support web-channel processes, with the respective
backend Integration. Thus, Product Catalog functionality is not part of the target
architecture.
Business Process related information
Hybris is the strategic solution to support web-channel processes, with the respective
backend Integration. Thus, integration via Product Catalog is not part of the target
architecture in SAP S/4HANA.
If the Product Catalog was used for other integration scenarios as the one mentioned
above, a switch to alternatives availabe in S/4HANA is required.
Required and Recommended Action(s)
There are other communication scenarios in SAP S/4HANA to send article and price
information.
The alternatives include e.g.:
Article data (i.e. if retail Business Functions are active) combined with prices
WES SOAP Service ReplicateMerchandiseDemandManagement
DRF SOAP Service ProductMerchandiseViewReplication (available with
SAP S/4HANA 1909)
Assortment List IDoc
Article data (i.e. if retail Business Functions are active)
DRF SOAP Service ProductMDMBulkReplicate (available with SAP
S/4HANA 2020)
ARTMAS IDoc
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 128
Material data (i.e. if retail Business Functions are not active)
DRF SOAP Service ProductMDMBulkReplicate (available with SAP
S/4HANA 2020)
MATMAS IDoc
Prices (independent of retail Business Functions)
DRF SOAP Service SalesPricingConditionRecord (available with SAP
S/4HANA 1909)
COND_A IDoc
Transaction not available in
SAP S/4HANA.
WCU1 Maintain customer
WCUM Maintain customer
WPC1 Prepare product catalog IDocs
WPC2 Prepare item IDocs
WPC3 Prepare catalog change IDocs
WPC4 Prepare item change IDocs
WPC5 Convert product catalog
WPCC Prepare prod. catalog change IDocs
WPCI Prepare product catalog IDocs
WPCJ Prepare product catalog IDocs
WW10 IAC product catalog
WW20 IAC Online Store
WW30 SD part for IAC MM-SD link
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
Till SAP S/4HANA 1909 FPS0, transactions WWM1, WWM2, WWM3,
WWM4, WWM5 can be executed. That is an error. In the blocklist (table
ABLM_BLACKLIST) these transactions are only excluded for Cloud. They should be
excluded for usage on-premise as weel. This will be corrected in a future release.
Required and Recommended Action(s)
Switch to strategic solution.
In case you reuse ABAP objects of packet WWMB or WWMI in your custom code,
please see attached note.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 129
This Simplification Item is relevant if Product Functionality is used.
This is the case if any of the following transactions are used: WCU1, WCUM, WPC1,
WPC2, WPC3, WPC4, WPC5, WPCC, WPCI, WPCJ, WW10, WW20, WW30, WWCD,
WWM1, WWM2, WWM3, WWM4, WWM5.
3.5 S4TWL - Object Identifier Type Code
Application Components:CA-MDG-KM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267294
S4TWL - Object Identifier Type Code
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
None
3.6 S4TWL – Deprecation of 4 fields from FSBP table BP1010
Application Components:FS-BP
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 130
Note Type
Note Number
Note Description
Business Impact
3216733
S4TWL - Rating fields of table BP1010
(Creditworthiness Data) of FSBP
enhancement to SAP BP) will become
obsolete
Symptom
You execute a system conversion from ERP to S/4HANA or an upgrade from a lower
S/4HANA release to a higher one (higher than 2023 - in S4/HANA 2023 the functionality
will still be available).
The four fields SOL_INS (Institute Providing Credit Standing Information), SOL_TXT
(Additional credit standing information), SOL_I_D (Date of Credit Standing
Information) and RATING (Rating) of the Financial Services Business Partner table
Creditworthiness Data (table name BP1010) will become obsolete in a future release.
The data contained in these fields have to be migrated to the ratings table BP1012. This
note has the purpose to make you aware of this change. The migration can already be
executed by customers now, however only if they do not use either of the applications
Loans Management and Treasury Management, which still access the 4 fields that will
become obsolete.
Reason and Prerequisites
The four mentioned fields in Financial Services Business Partner table for
Creditworthiness Data must not be used any more from a future S/4HANA release
onwards. Reason is that these fields have the character of a rating and for ratings there is
a separate table available. There is a migration report available already, which can be
used to migrate these fields into a rating entry in table BP1012. At the moment this
migration cannot be executed as long as you use either of the two applications Treasury
Management or Loans Management. In addition the switch (FSBP_MIGCS_SWITCH -
can be displayed in transaction SFW1) can currently not be activated in order to make
sure that the four obsolete fields cannot be maintained/displayed any more. Reason for
this is that there is currently no business function available that is assigned to this switch.
Solution
Procedure for determining the relevance (relevance condition):
"The migration needs to be executed as soon as there is at least one entry in one of the
four mentioned fields of table BP1010 in any of the clients of your system apart from 000
and 066."
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 131
We have also provided a consistency check class that is triggered by the SUM process.
Currently the SUM process does not return any warning or error if the relevance
condition is true. But as soon as we enforce the migration in a future release our check
class will return an error and the SUM process will be stopped, in case the above
relevance condition is true. With this the migration will then be enforced.
Required and recommended actions
In case you do not use TRM or CML applicaiton you may already now execute the
migration from BP1010 to BP1012 (for the 4 obsolete fields). See below for more details.
Currently - however - it is not possible to activate switch FSBP_MIGCS_SWITCH,
which would remove the 4 obsolete fields from transaction BP and corresponding IMG
activities from transaction SPRO. Reason is that there is no business function assigned to
this switch. We are currently working on the creation of a business function. As soon as
the business function is available we will update this note.
If you would like to execute the conversion (provided that you do not use TRM and
CML), please find information below how to execute the migration.
In SAP note 1765305 (after new business function is available we will probably provide a
new note) you can find an ASU Toolbox Content XML file that can be started using the
so-called ASU-Toolbox. With this you are guided through the migration. Activating the
business function is currently not possible, the other steps should however be possible, so
that you can execute the migration.
The main steps are the following:
Activate business function FSP_FSBP_MIGRATION_CS (manual step) (currently
not yet possible!)
Check whether data needs to be converted (automatic step when executing the XML
in the ASU toolbox)
Analyze and configure Customizing settings for mapping (Customizing - manual
step)
Execute Report FSBP_MIGCS_MAPPING_EDIT for customizing assignment
(automatic step)
Mass conversion of credit standing data to ratings
(report FSBP_MIGCS_MASS_MIGRATION, automatic step)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 132
You will be guided through the whole process supported by the system after starting ASU
toolbox. For details how to start this guided process please check note 1765305 and the
referenced note 1000009.
Other Terms
SAP Business for Financial Services, Business Partner, SAP BP, FSBP, SOL_INS,
SOL_TXT, SOL_I_D, RATING, BP1010, BP1012, Creditworthiness data, ratings
3.7 S4TWL: Business partner data exchange between SAP CRM and
S/4HANA
Application Components:CRM-MD-BP-IF, S4CORE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2285062
S4TWL: Business partner data
exchange between SAPCRM and S/4
HANA, on-premise edition
Symptom
This SAP Note 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:
SAP enhancement package 6 for SAP ERP 6.0
SAP enhancement package 7 (SP11) for SAP ERP 6.0
SAP enhancement package 8 (SP01) for SAP ERP 6.0
You are using a live integration of SAP CRM and SAP ERP.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 133
Introduction
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, 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.
Business Process Information
There is no effect on business processes if the settings are performed as described in this
SAP Note.
Required and Recommended Actions
Note that you must perform the pre-conversion actions described in this SAP Note before
activating the CVI and starting mass synchronization.
Reason and Prerequisites
System landscape with CRM and S/4 HANA is planned or available
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 134
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, on-premise 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 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 135
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.
Other Terms
CUSTOMER_MAIN, CUSTOMER_REL
BUPA_MAIN, BUPA_REL
VENDOR_MAIN
R3AR2, R3AR4, R3AS, R3AC1
COM_BUPA_CALL_FU
3.8 S4TWL - HANA-based Analytics for Master Data Governance
Application Components:CA-MDG-ANR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2375319
S4TWL - HANA-based Analytics for
SAP Master Data Governance
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in case SAP Master Data Governance is used.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 136
SAP HANA-based Analytics for SAP Master Data Governance is not available within
SAP S/4HANA, on-premise edition 1511 and higher.
Business Process related information
With this system conversion the content generation for SAP HANA-based Analytics for
SAP Master Data Governance is no longer available.
Required and Recommended Action(s)
The following check is only required in case that you have SAP Master Data Governance
in active usage. In this case please check if also SAP HANA-based Analytics for SAP
Master Data Governance is set up and running.
How to Determine Relevancy
Check if content for SAP HANA-based Analytics for SAP 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 one of the SAP HANA Databases that are
connected to the according system. This can be done for example by looking for
calculation view 'ChangeRequestHeader'.
3.9 S4TWL - Business Partner BUT000/Header Level Time Dependency
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2379157
S4TWL - Business Partner
BUT000/Header Level Time
Dependency
Symptom
You are doing a system conversion to SAP S/4HANA.The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 137
Solution
*** Note : The attcahment of this note has been changed with a new report
(Z_NTD_BUT000_NEW) on 2nd Jan,2018 to improve the performance .***
Business Value
Time dependency has been disabled at the header level of BUT000 in SAP S/4HANA to
ensure that there are no inconsistencies in the master data.
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 SAP ERP before the SAP S/4HANA
system conversion or in the SAP S/4HANA, on-premise edition 1511 release, refer to the
section Required and Recommended Action(s).
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 BUT000 for BP 0000000XXX maintained time-dependently, despite
inactive Time dep.” message appears (Hot News Note 1759416).
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 138
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.
Run the report BUPTDTRANSMIT which will make BUT000 data up to date.
Run the report Z_NTD_BUT000_NEW attached with this Note. To run this:
Call up SE38.
Enter Z_NTD_BUT00_NEW and choose Create.
Choose type as Executable Program.
Paste the code content from the attachment.
Save, activate, and then execute the report.
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). Also , it will 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_NEW has a test run mode and BP range as the selection
parameter.
How to Determine Relevancy
This simplification item is relevant when time dependency is enabled for BUT000 at the
header level. Meaning, the simplification item is relevant when DEV_ISACTIVE is X for
development object (field DEVELOP) BUT000 (or) ALL_BP_TD in V_TB056 view.
When the time dependency is enabled, BUT000_TD will have atleast one entry.
Other Terms
Time dependency, BUT000, BUT000_TD, S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 139
3.10 S4TWL - BADI ADDRESS_SEARCH (Duplicate Check) is Not
Supported in SAP S/4HANA
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2416027
S4TWL - BAdI ADDRESS_SEARCH
(Duplicate Check) Neither Certified Nor
Supported for SAP S/4HANA Fiori
Symptom
You are doing a system converson to S/4HANA On Premise. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
The BAdI ADDRESS_SEARCH was not designed to meet the newer generation codings
of SAP S/4HANA which gets called in Fiori smart template apps such as Manage
Customer Master, Manage Supplier Master and so on. When this BAdI is activated, the
apps generate errors such as program termination, or run time exceptions occur.
Solution
Business Value
The BAdI ADDRESS_SEARCH is not compatible with the new generation code of SAP
S/4HANA Fiori and hence it is neither certified nor supported.
Description
The duplicate check using the BAdI ADDRESS_SEARCH to find dupliacte addresses is
neither certified nor supported in SAP S/4HANA Fiori. The BAdI is available with the
standard implementation and will be inactive. If there is a requirement to use the BAdI, it
can be used for SAP GUI applications.
Business Process related information
This BAdI was used to implement a check that identifies potentially duplicate addresses
(in create and edit mode) and notifies the user. The user could decide whether the new
account or contact is required or is in fact a duplicate of an existing account or contact.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 140
While not supporting this BAdI implementation for Fiori applications, SAP S/4HANA is
in a conceptualize stage for a better solution for Fiori Apps.
Required and Recommended Action(s)
Be informed that the BAdI ADDRESS_SEARCH for duplicate check is no more certified and
supported for Fiori Apps.
How to Determine Relevancy
This is relevant for all SAP S/4HANA customers.
Other Terms
Duplicate Check, BAdI SIC_ADDRESS_SEARCH, BAdI ADDRESS_SEARCH
3.11 S4TWL - Business Partner Hierarchy Not Available
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2409939
S4TWL - Business Partner Hierarchy
Not Available
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Business Partner hierarchy is removed in SAP S/4HANA to avoid redundancy as
customer hierarchy is already available for the applications to consume.
Description
The Business Partner Hierarchy is no more available in S/4HANA. S/4HANA is in
conceptualize stage for a better hierarchy solution.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 141
You will not be able to access the BP hierarchy data anymore after the system conversion
to S/4HANA.
Transaction not available in SAP S/4HANA on-
premise edition
BPH, BPH_TYPE
BAPIs not available in SAP S/4HANA on-premise
edition
BUHI_ASSIGN_BP_TO_NODE
BUHI_CLEAR_BUFFER
BUHI_DELETE_BP_FROM_NODE
IMG activity node not available in SAP
S/4HANA on-premise edition
Business Partner Group Hierarchy
BOR Object not available in SAP S/4HANA on-
premise edition
BUS1006004
Required and Recommended Action(s)
Knowledge transfer to key and end users
How to Determine Relevancy
This item is relevant if you have created and are using Business Partner Hierarchies. You
can check for the existence of Business Partner Hierarchies in transaction BPH or check
for the existence of entries in table BUT_HIER_TREE.
3.12 S4TWL - MDG in Lama
Application Components:CA-MDG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2379272
S4TC MDG_APPL Master Check for S/4
System Conversion Checks
Symptom
Implementation of MDG_APPL check class for S/4 transformation checks as described
in SAP note 2182725.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 142
This note implements a "Precheck DIMP/LAMA upgrade to S/4 for MDG-M (Material
Governance) in software component SAP_APPL."
Reason and Prerequisites
If you upgrade master data material to S/4 it is recommended, to have no open change
request for material (MDG-M)
If you upgrade a system with long material number (LAMA) it is mandatory to finalize
(activate or delete) all open change request creating new materials, else you have to
delete open change requests creating new materials in LAMA system manually after
upgrade.
This change requests can not processed any more after upgrade.
Solution
Implement the technical prerequisites for the S/4 transformation checks via this note.
Other Terms
S4TC
MDG_APPL
MDGM
3.13 S4TWL - Migration of Business Partner Data specific to GST India
Application Components:XX-CSC-IN-MM, XX-CSC-IN, XX-CSC-IN-SD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2877717
GST IN: Tables J_1IMOVEND and
J_1IMOCUST are not updated post
S/4HANA migration
Symptom
CIN data isn't updated in tables J_1IMOCUST and J_1IMOVEND when BP is updated
for customer and vendor role post S/4HANA migration.
Reproducing the Issue
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 143
Go to transaction BP.
Save Vendor classification/Pan number data for vendor or customer role.
Go to tables J_1IMOCUST and J_1IMOVEND.
Fields Vendor classification/Pan number isn't updated with values.
Cause
Customer or vendor master core data is completely integrated with Business Partner. The
master data in the new transaction is being maintained in tables KNA1 and LFA1.
Fields from tables J_1IMOCUST and J_1IMOVEND are also migrated into tables KNA1
and LFA1 in S/4HANA system.
Resolution
Implement the note '2285611 - BP Enhancements for CIN' and execute the
transaction LOIN_CV_MD_MIG to migrate data from tables J_1IMOCUST and
J_1IMOVEND into KNA1 and LFA1.
See Also
2421394 - GST India: SAP ERP Solution Notes
2285611 - BP Enhancements for CIN
2387589 - BP Migration Report Log issue while processing huge number of records
Keywords
GST, GST India, Master data, CIN, CIN data, S/4HANA, HANA, Migration, Upgrade,
Conversion, XX-CSC-IN-MM, XX-CSC-IN-SD, XX-CSC-IN-FI, J_1IMOCUST,
J_1IMOVEND, field, J_1IMOVEND-VEN_CLASS, vendor classification,
PAN, J_1IPANNO, LFA1, KNA1, J_1IMOVEND-J_1IPANNO, J_1IEXCIVE.
Environment
Sales And Distribution (SD)
Logistics Execution (LE)
SAP S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 144
This is relevant for India Localization or Country India version (CIN) component
3.14 S4TWL - MDG_MDC in Lama
Application Components:CA-MDG-CMP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2442665
S4TC MDG_MDC Master Check for S/4
System Conversion Checks
Symptom
Implementation of MDG_MDC check class for S/4 transformation checks as described in
SAP note 2182725.
This note implements a "Precheck DIMP/LAMA upgrade to S/4 for MDC-M (Material
Consolidation and Mass Change) in software component MDG_MDC."
Reason and Prerequisites
If you upgrade master data material to S/4 it is recommended, to have no open process
for material (MDG_MDC).
If you upgrade a system with long material number (LAMA) it is mandatory to finalize
(activate or delete) all open processes (MDC) for materials, else you have to delete
open processes manually after upgrade.
Also it is suggested to have no open imports or process drafts.
Solution
Implement the technical prerequisites for the S/4 transformation checks via this note. The
note checks for active processes for materials.
Other Terms
S4TC
MDG_MDC
MDG-C
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 145
3.15 S4TWL - Batch Input for Customer Master/Supplier Master
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2492904
S4TWL - Batch Input for Customer
Master/Supplier Master
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Batch Input as a technology to maintain customer master and supplier master data will
not be supported in release from SAP S/4HANA 1809 onwards.
Since we follow "Business Partner first" approach in SAP S/4HANA, Batch
Input programs will now work with API based approach which would replace the
traditional Batch Input technology as classical customer and supplier transactions have
been made obsolete.
As an alternative, we recommend the usage of the following:
Business Partner SOAP Services. Refer to SAP Note 2472030 for more information.
IDocs (CREMAS/DEBMAS)
Mass Transactions (XK99/XD99)
Business Process related information
No influence on business processes is expected.
Required and Recommended Action(s)
Please check if you use Batch Input for creating/changing customer master or supplier
master data. If yes, please switch to the recommended alternatives.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 146
3.16 S4TWL - API RFC_CVI_EI_INBOUND_MAIN is obsolete
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2506041
S4TWL - API
RFC_CVI_EI_INBOUND_MAIN is not
supported from the release S/4 HANA
OP 1709 FPS2 and in Cloud Edition
1805 onwards
Symptom
Customer is migrating to SAP S/4HANA on-premise edition, and they are using function
module RFC_CVI_EI_INBOUND_MAIN to migrate business partners.
Reason and Prerequisites
RFC_CVI_EI_INBOUND_MAIN in SAP S/4HANA, was initially used to migrate
business partners.
Solution
Description
RFC_CVI_EI_INBOUND_MAIN is used to update/create BP in S/4 HANA. However, it
is not the recommended approach as it doesn't cover all the features.
RFC_CVI_EI_INBOUND_MAIN is not an officially released SAP Function module and
was created for internal use only. Hence, it has been decided to stop supporting this
function module from the OP release 1709 FPS2 and in Cloud Edition 1805 onwards.
Customers should refer to the SAP Note 2417298 for maintenance of Business Partners.
Business Process related information
No impact on business processes is expected.
Required and Recommended Action(s)
Check if you use RFC CVI_EI_INBOUND_MAIN for creating/changing customer master
or supplier master data. If yes, please switch to the recommended alternatives in the SAP
Note 2417298.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 147
Other Terms
Business Partner, RFC CVI_EI_INBOUND_MAIN, Customer Master, Supplier Master
3.17 S4TWL - Removal of Gender Domain Fixed Values
Application Components:LO-MD-BP, BC-SRV-ADR, BC-SRV-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2928897
S4TWL - Removal of Gender Domain
Fixed Values
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Support for new gender codes in SAP Business Partner, Business Address Services,
Customer and Supplier Master
Solution
Description
You are looking to maintain additional gender values such as Neutral or Diverse in SAP
Business Partner (BP). It was not possible to maintain gender values other than Male,
Female and Unknown in a Business Partner so far. With S/4HANA On-premise 2020, in
addition to the existing values Male, Female and Unknown, two new gender values are
available in Business Partner master data:
Nonbinary - an identity other than male or female. For example, Divers in Germany.
Not specified - any identity with legal rights; but chooses not to specify the gender
Further details are available in SAP Help documentation for S/4HANA 2020.
To support new gender codes, the existing fixed values for gender related domains in
Business Partner data model have been replaced with new value tables. These value
tables will hold gender codes Male, Female and Unknown (existing from older releases)
and new gender codes Nonbinary and Not specified (new from S/4HANA 2020)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 148
Business Value
SAP Business Partner now provides a possibility to maintain gender codes other than
Male and Female maintainence.
Business Process relation Information
All business processes which involve maintenance of Business Partner Master Data and
in that specifically the Gender information for the Business Partner are affected. This
includes primarily Business Partner maintenance via
Transaction BP
Fiori Apps for Business Partner, Customer and Supplier maintenance
Supported external interfaces for like oData, SOAP, iDocs
Released APIs
SAP delivered business processes have been adjusted to make use of new value tables for
gender codes instead of domain fixed values. Further sections in this Note provide
guidelines on relevancy and recommended actions for customer specific coding for
Business Partner maintenance.
Compatibility Considerations
To support the new gender codes, a new field GENDER has been introduced in Business
Partner main table BUT000. This field will support all existing gender codes (Female,
Male and Unknown) and new gender codes (Nonbinary and Not Specified). To ensure
compatibility, old fields XSEXF, XSEXM and XSEXU from the table BUT000 will
continue to be maintained with gender values when chosen gender value is Female, Male,
or Unknown.
Similarly, a new field GENDER has been introduced in the interface structures and can
be used to maintain all five gender codes. Existing field SEX will continue to support
gender codes Female, Male or Unknown. Further details are available in the cookbook
attached to this SAP Note.
How to determine Relevancy
As Business Partner is one of the most fundamental business objects in S/4HANA and as
there would invariably be Business Partner of type Person in any organization, this
simplification item is relevant in most customer cases.
ABAP domains listed below have been changed to support additional gender codes.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 149
Domain
Fixed Values Removed
Replacement Value Table
BU_SEXID
Female, Male and Unknown
TB995
AD_SEX
Female, Male and Unknown
TSAD15
SEXKZ
Female, Male
TSAD15
If you have custom ABAP artefacts (screens, programs, classes etc.) for BP Maintenance
referring to these domains, the changes are relevant for you.
Required and Recommended actions
Attached PDF document titled 'Cookbook_GenderDomainChanges.pdf' describes in
detail the how the custom adoption has to be done for the data model changes listed
above.
Other Terms
Business Partner Gender Code, Nonbinary, Divers, BU_SEXID, AD_SEX, SEXKZ
3.18 S4TWL - Usage of obsolete links in tables BD001 / BC001
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3010257
S4TWL - Usage of obsolete links in
tables BD001 / BC001
Symptom
You execute a system conversion to S/4HANA 2021 or lower. If you use the customer
vendor integration (CVI) and still have entries in the old link tables BD001/BC001
(Business Partner: Assignment Customer – Partner/Business Partner: Assign Vendor –
Partner) you need to migrate these entries to the new link tables
CVI_CUST_LINK/CVI_VEND_LINK ( Assignment Between Customer and Business
Partner/ Assignment Between Vendor and Business Partner) before migration.
Reason and Prerequisites
With this note a new check is integrated into the pre-upgrade checks which enforces
migration of the old link tables. Before migration can be executed the old link tables need
to be migrated to the new ones.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 150
Solution
Procedure to determine relevance
A new check class is integrated into the simplification element check report
/SDF/RC_CHECK_START. (This is delivered as part of note-3009162 -
Simplification Check in BD001 and BC001 Tables)
This class checks if there are still unmigrated entries in the database tables
BD001/BC001. If so, a migration is not possible.
In detail the following checks are made:
- select all entries from BD001/BC001 tables.
- For all entries found in BD001 select entries in CVI_CUST_LINK
- For all entries found in BC001 select entries in CVI_VEND_LINK
- if at least one entry is found in BD001 that is not available in CVI_CUST_LINK
or in BC001 that is not available in CVI_VEND_LINK an error is returned by the check
class.
An error in the check class means that the migration cannot be executed until the
underlying problem is solved.
Required Action:
In case the check class returns an error, you need to execute the two migration reports
CVI_MIGRATE_CUST_LINK and CVI_MIGRATE_VEND_LINK.
After that all links should be available in CVI_CUST_LINK/CVI_VEND_LINK tables
and the check should not lead to an error anymore.
Further actions sometime after the conversion
After the conversion all entries in the two tables- BD001/BC001 need to be deleted.
Before you do this, you should wait some time in order to be sure that the customer and
BP link/Vendor and BP link is correctly working in all the relevant applications.
The deletion should be done at the latest, before you start planning the next upgrade to a
higher release level of S/4HANA.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 151
BD001, BC001, CVI_CUST_LINK, CVI_VEND_LINK,
CVI_MIGRATE_CUST_LINKS, CVI_MIGRATE_VEND_LINKS
3.19 S4TWL - Business Partner Approach
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2265093
S4TWL - Business Partner Approach
Symptom
You are doing a system conversion to SAP S/4HANA, any of the listed on-premise
editions -> 1511, 1610, 1709,1809, 1909, 2020, 2021, 2022. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
In SAP S/4HANA, Business Partner is the leading object and single entry point to
maintain Business Partner, Customer and Supplier (formerly known as Vendor) master
data. This is to ensure ease of maintenance of the above master data and to achieve
harmonization between them. Compared to classical ERP transactions, maintenance of
Customer and Supplier master data via Business Partner has multiple advantages. Some
of them are as follows:
Business Partner allows maintenance of multiple addresses with
corresponding address usages.
In classical transactions, one customer can only be associated to one account group.
But in Business Partner, multiple roles can be associated to the same Business
Partner.
Maximal data sharing and reuse of data which lead to an easier data consolidation.
General Data available for all different Business Partner roles, specific data is stored
for each role.
Maintenance of multiple relationships to the same Business Partner.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 152
Maintenance of Time Dependency at different sub-entities roles, address,
relationship, bank data etc.
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 1511, 1610, 1709, 1809, 1909 and 2020. 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.
Business Process related information
Only SAP Business Suite customer with C/V integration in place can move to SAP
S/4HANA, on-premise(Conversion approach). It is 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 specific
transactions 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)
Transactions not available in
SAP S/4HANA on-premise
edition
Transactions that get redirected to transaction BP:
FD01,FD02,FD03, FK01,FK02,FK03,MAP1,MAP2,MAP3, MK01,
MK02, MK03, V-03,V-04,V-05,V-06,V-07,V-08,V-09, V-11,
VAP1, VAP2, VAP3, VD01, VD02,VD03, XD01, XD02, XD03,
XK01, XK06, XK07, XK02, XK03
Transactions that are obsolete:
FD06, FK06, MK06, MK12, MK18, MK19, VD06, XD06, V+21,
V+22, V+23
Points to Note in SAP S/4HANA:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 153
In addition, note the following points while using the following functionalities in SAP
S/4HANA:
Consumer - While creating a consumer, ensure that you use the BP Grouping that is
associated to the customer account group (Consumer) in TBD001 (Assignment of
Account Group BP Grouping). Note that customer itself is a contact person, hence
no further relationships can be maintained.
One-time Customer/Supplier - While creating a one-time customer or supplier,
ensure that you use the BP Grouping that is associated to the customer/supplier
account group (One time customer/supplier) in TBD001 and TBC001
(Assignment of Account Group BP Grouping).
The idocs DEBMS/CREMAS and cremas are not recommended for data integration
between S/4HANA systems. In S/4HANA, BP is the leading object. Therefore,
only customer or supplier integration should be avoided. In S/4HANA, Business
Partner is the leading object. Therefore, customer or supplier only integration
should be avoided. You can use Business Partner web services (SOAP) via API
Business Hub for SAP S/4HANA integration. It is recommended to use IDocs
only if the source system has Customer or Supplier (no Business Partner) master
data.
Role Validity - In SAP S/4HANA, you can maintain the validity of roles. With this
feature, the user can close the (prospect) role and move to another after the
mentioned validity period. For example, a business partner with prospect role can
set the role change to sold-to-party by specifying the validity and by closing the
previous validity.
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
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 154
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 master data consistency using CVI_MIGRATION_PRECHK and maintain
consistency.
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
attached BP Conversion Document.pdf > Chapter 5. Convert Customer/Supplier
Data into Business Partner.
In case of an error during the synchronization process due to data/customizing
mismatch you can find the errors using Logs button. You can also view this via
MDS_LOAD_COCKPIT> Monitor tab > Call PPO button in Synchronization
Cockpit.
Conversion Process
Conversion Process must be triggered according to the BP Conversion Document.pdf
attached to this SAP 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 a Customer /Vendor.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 155
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 (in SAP Note 2265093):
BP_Conversion Document.pdf: Description of Busines Partner
Approach and conversion activities
01_TOP-Item_MD_Business-Partner-Approach_Version1.0.pdf:
Presentation on Business Partner Approach and Customer
Vendor Integration during Conversion
Custom Code Adaption
If you are writing a direct write statement or a custom code on the tables mentioned in
piece list SI_MD_BP, Please follow the below mentioned steps instead.
Reason and Prerequisites:
You want to create BP/Customer/Supplier with direct write statements or a particular
piece of custom code.
You need an API to create Business Partner with Customer and Supplier roles.
The following are possible use-cases:
Requirement to create business partners in the same system: You can use API
CL_MD_BP_MAINTAIN. Pass the data in CVIS_EI_EXTERN structure format
and pass it to the method VALIDATE_SINGLE. This method validates all the
data that is passed; after that, you can use the method MAINTAIN to create
business partners.
Integration of data with various landscapes: If you want to integrate
BP/Customer/Supplier master data across different systems, you can use
following interfaces:
a. IDOCs
There are two types of IDocs available that can be used:
DEBMAS: If you want to integrate customer (without BP) data between two
systems, this IDOC can be used.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 156
CREMAS: If you want to integrate supplier (without BP) data between two
systems, this IDOC can be used.
b. SOA Services
If the system has data of Business Partners, use SOA services for integration.
Business Partner SOAP services enable you to replicate data between two
systems. There are both inbound and outbound services available. Refer to
SAP Note 2472030 for more information.
However, the IDocs DEBMAS and CREMAS are not recommended for data integration
between S/4HANA systems. In S/4HANA, Business Partner is the leading object.
Therefore, you can use Business Partner web services (SOAP) for SAP S/4HANA
integration.
Industry Specific Actions
IS-OIL Specific Actions:
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).
Retail Sites Specific Action:
Customers and vendors assigned to Retail sites are not handled by CVI
synchronization (MDS_LOAD_COCKPIT) on SAP ERP as described in this
note, but by a specific migration process during SAP S/4HANA conversion. See
SAP Note 2310884 for more information.
3.20 S4TWL - Reduction of Redundant Business Partner Data Storage in the
'BUTADRSEARC
Application Components:LO-MD-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2576961
S4TWL - Reduction of Redundant
Business Partner Data Storage in the
'BUTADRSEARCH' Table
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 157
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Business Value
Fields BIRTHDT, AUGR, XDELE, XBLCK, TYPE, and REGION in
table BUTADRSEARCH is no longer requried
as the redundancy of data storage is minimized in SAP S/4HANA.
Description
Fields BIRTHDT, AUGRP, XDELE, XBLCK, TYPE, and REGION were updated
in BUTADRSEARCH if the indexing was activated in TB300 table.In S4/HANA this is
no longer requried as we plan to phase this out to avoid redundant data storage.However
these fields will be maintained in the respective table listed below.
BUT000-BIRTHDT
BUT000-AUGRP
BUT000-XDELE
BUT000-XBLCK
BUT000-TYPE
ADRC-REGION
Business Process related information
No further development is planned.We instead plan to phase this out to avoid redundant
data storage.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 158
Be informed that the redundant storage of 'Business Partner' data in BUTADRSEARCH
is only kept for compatibility reasons (customers doing a conversion that have already
activated this indexing) and must not be activated by new customers.
How to Determine Relevancy
This simplification list item is releavent if TB300-ADDRSRCH_ACTIVE = ‘X’ which
means the indexing is activated.
Other Terms
'BUTADRSEARCH', 'TB300'
3.21 S4TWL - Simplified Product Master Tables Related to OMSR
Transaction
Application Components:LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267138
S4TWL - Simplified Product Master
Tables related to OMSR transaction
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In SAP S/4HANA, the tables related to OMSR transaction("Field groups and Field
selection for data screens") such as T130F (Table of Field attributes), T130A (Table of
Material master field selection), T133F (Table of Material master field selection part2)
,etc., has delivery class E (E = Control table, SAP and customer have separate key areas).
In SAP Business Suite, the delivery class of these tables is G (G= Customizing table,
protected against SAP Update, only INS all).
Business Process related information
No influence on business processes expected
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 159
Required and Recommended Action(s)
Customizing the field selection for data screens in SAP namespace is not recommended
anymore.
To customize the field selection settings, kindly follow the below process.
In OMSR/OMS9 transaction, select the field ref. you want to change.
Click on Copy As icon or press F6.
Enter the Field reference ID in allowed namespace.
Make the required changes for the field groups and press enter.
Click on Save.
The created field reference can be assigned to required material type / plant.
To assign it to a material type, go to transaction OMS2.
Open the required material type, update the Field reference. Click on Save.
To assign it to a plant, go to transaction OMSA.
Add an entry by clicking New entries. Click on Save.
General Recommendation
In S/4HANA the recommendation is to adjust the field references from a transaction
based approach to a material type approach. In the SAP standard, the transaction based
field references were set to optional, so that the field selection can be controlled via the
field references of the material type.
In case you continue to work with a transaction based approach, you need to double-
check the modifications you made to these field references after each upgrade, since the
modifications to these field references might be overwritten with the SAP standard.
Changing the field selection group also has to be double-checked after each upgrade,
since the modifications of the field selection groups might also be overwritten with the
SAP standard.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 160
3.22 S4TWL - Material Number Field Length Extension
Application Components:LO-MD-MM, CA-FLE-MAT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267140
S4TWL - Material Number Field Length
Extension
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
In SAP S/4HANA, the material number field length has been extended from 18 to 40
characters. This change was first implemented in SAP S/4HANA, on-premise edition
1511 and affects this release and higher releases.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 161
This note focuses on the neccessary technical adjustments which are a consequence of
the field length extension. These adjustments are relevant regardless of the intention to
enable the extended length for material numbers in customizing or not. The decision for
activation of the extended length needs to be taken based on business requirements and
considering the restrictions outlined in this note, the notes referenced in this note and is
completely independent of the required technical adjustments.
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-premise edition 1511. For the first step
into SAP S/4HANA – SAP Simple Finance, on-premise edition 1503 – the maximum
field length is still 18 characters long. Additional remark: 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 behaviour is usually ensured by the fact that all data
elements used to type relevant fields are derived from the same domain, the domain
defining the technical length of the derived fields. Whenever coding uses these fields, the
coding is automatically adapted when the domain changes.
For the material number itself we identified the domains that are used to define material
number fields. All these domains have been extended to 40 characters.
Besides these direct usages of the material, it may be that a specific material is also used
in other fields. An example may be characteristic values: A material may well be used as
characteristic value. For all such fields for which a material – besides other possible
values – is a valid content, it has been checked that these fields are long enough to hold
the extended material number. These fields (or the underlying domains) have been
extended as well. Extending further – dependent – fields of course means that the usages
of the fields have been investigated as well.
Extending such “target” fields which are not material numbers by themselves was only
done if the material number needs to be handled in the field, as extending a field usually
trigger follow up changes. At several places, the material number is used as reference,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 162
template, or for other reasons but another (shorter) value, for example, a GUID, could be
used as well. In these and other similar cases, it may be the better choice to switch to
another value. Using this other value has been done at all places where this was
appropriate.
Overall, the complete data flow in the system has been analysed to identify all places at
which a material number was moved to a field that was not long enough for a 40
character material number. All these conflicts have been handled in one of the ways
described above. Such an analysis also needs to be done in customer or partner coding.
The described changes have also been applied to parameters of all interfaces that are
usually called only within one system, that is, local function modules, class methods,
BAdIs etc. In the types and structures used as parameters in these local calls, the material
number has simply been extended to 40 characters. The same is true for other extended
fields as well. This was usually also done for unreleased remote enabled function
modules as the main use case for such function modules is an internal decoupling within
one system.
For interfaces that are usually called remotely, a different way has been chosen. For more
information, see the specific chapter below.
Storage of the Material Number on the Database
Extending the material number on the database means that the field length of the
MATNR field on the database has been extended from 18 to 40 characters. This has been
done in all tables (and all fields within the tables) in which a material number can be
stored.
Although the maximum length of the database field used to store the material number is
now 40 characters, the way how the material number content is stored in the database
field has not been changed compared to SAP Business Suite. This means that for such
fields usually no data conversion is needed when converting from SAP Business Suite to
SAP S/4HANA.
This holds especially true for pure numeric material numbers. With standard Customizing
(lexicographic flag not set, i.e. leading zeroes are not significant), pure numeric material
numbers are still restricted to 18 characters and will be filled up on the database only up
to 18 characters by leading zeroes. This is the same behaviour as in SAP Business Suite.
Overall, the chosen way of storing material number content avoids data conversions in
the database. Regarding the storage format for material number content there is no
difference between conversion of existing systems and new installations of S/4HANA,
the impact on data conversion was merely a factor for the chosen format. 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:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 163
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, the content that is stored in the database for the
material number will need to be changed. 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 fields) in these
interfaces would therefore technically break the version compatibility.
We have decided to provide a technical-version compatibility for released external
interfaces in the way that is commonly used and proposed for BAPI interfaces: The
already existing field keeps its original length and a new field has been added at the end
of the structure (or as new parameter) that allows transmitting material numbers with 40
characters.
Besides this, it must be ensured that no material number (or other extended field) can be
maintained in the system with a content length greater than the old length of the field. To
enforce this and to make the field length extension as far as possible non-disruptive for
the SAP S/4HANA customers, the extended material number functionality must be
switched on explicitly. Only after this decision it is possible to allow more than 18
characters for the material number.
The changes described have been done for BAPIs, IDocs, and released remote-enabled
function modules. This has additionally been implemented where necessary for remote
function calls issued by the SAP S/4HANA system and for unreleased remote-enabled
function modules that are used to communicate with other SAP Business Suite products
like SAP SCM or SAP CRM.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 164
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 was newly installed, the extended material number functionality will by
default be switched off.
System Behaviour Depending on the Extended Material Number Switch
If the extended material number functionality is NOT switched on, the system behaves as
follows:
After an SAP Business Suite System was converted to SAP S/4HANA, on-premise
edition 1511, the B2B and A2A communication via BAPIs, IDOCs, Web-
Services, released RFCs (inbound), and remotely called RFCs (outbound) still
work without further changes.
The shorter versions of the extended fields
are still part of the interfaces.
are still filled when sending data.
are still understood when retrieving data.
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.
The system prevents that data is created that cannot be sent via the old
interface, that is the usage of the extended fields is restricted to the old
length.
Communication partners can still rely on the old known behaviour of the
interfaces.
The long version of the extended field in the interfaces is filled and
interpreted, too. 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 165
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:
Material numbers and other extended fields can be used with the full length (40
characters).
That means:
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.
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.
Before SAP S/4HANA, on-premise edition 1511 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 SAP S/4HANA,
on-premise edition 1511 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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 166
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:
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).
Changing the Material Number Format
Transaction OMSL allows a customer-specific settings regarding the material
number field length. Here the settings need to be adapted to allow a field length of
more than 18 characters.
Define Output Format of Material Number can be accessed via IMG (à Logistics
General à Material Master à Basic Settings)
Note:
If the extended material number functionality is activated in a system, it cannot be easily
deactivated as values may exist in different fields that are only allowed with extended
material number.
The Long Material Number within the DIMP Add-On (Discrete Industries & Mill
Products)
The extension of the material number is a well-known requirement in SAP Business Suite
requested by several customers. An Add-On solution was provided several years ago as
part of the industry solution Discrete Industries & Mill Products (DIMP). The so-called
DIMP LAMA-functionality is a part of the industry solution Automotive which is one
component of the Add-On DIMP (Discrete Industries & Mill Products). See SAP Note
1597790.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 167
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 LAMA-functionality 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.
Note that code adaptions will be needed even if you decide not to activate the
extended material number functionality and stay with 18 characters
Custom Code related information
See SAP Note: 2215424, 2215852
Restrictions
SAP S/4HANA restriction note:
2214213 for SAP S/4HANA, on-premise edition 1511
2333141 for SAP S/4HANA 1610
Collection of restriction related to MFLE: 2233100
ALE generation for BAPIs: SAP Note 2232497
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 168
Extended Material Number in Suite Integration: SAP Note 2232396
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
Other Terms
18 digits, 40 digits
3.23 S4TWL - Simplification of copy/reference handling
Application Components:LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2330063
S4TWL - Simplification of
copy/reference handling
Symptom
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/4HANA 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 SAP
S/4HANA system Release 1610 or higher contains an additional Customizing table
T130F_C. This allows alternative maintenance of the copy control to the SAP delivery.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 169
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 precheck 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/4HANA target release is higher than or equal
to SAP S/4HANA 1610. 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 precheck because the system only then contains the information
concerning the S/4HANA target release to which the data is migrated. To proceed
further, you must then first carry out the data migration.
If the S/4HANA target release is equal to SAP S/4HANA 1511, 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/4HANA target
release version SAP S/4HANA 1610, the system issues an error message at all times if
the precheck determines inconsistencies. The data migration must be carried out in any
case.
Reason and Prerequisites
You want to migrate an SAP ERP system to an S4 system Release SAP S/4HANA 1610.
Solution
Business value
The information provided in this Simplification Item ensure that customer-specific
settings referring to the copy control of fields in the product master are still available
after the migration to S/4HANA. This means that the copy control in S/4HANA will
work in the same way as before the migration. The changes explained above under
"Symptom" are necessary to define the “Virtual Data Model” (VDM), which is needed
for the new SAP Fiori application.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 170
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.
Required and recommended actions
Execute the migration precheck.
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.
Related SAP Notes
Migration precheck
SAP Note: 2206932
Migration report
SAP Note: 2323185, 2324325
Other Terms
SAP_APPL_LO_MD_MM_T130F_CHECK S4 T130F field control
3.24 S4TWL - Foreign Trade fields in Material Master
Application Components:LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267225
S4TWL - Foreign Trade fields in
Material Master
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 171
Solution
1.1.1.1.1 Description
The Foreign Trade functionality as part of Sales & Distribution is not available within
SAP S/4HANA Product Master Data, from on-premise edition 1511. 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 not available through Material Master:
CAP product list no. (MARC-MOWNR)
CAP prod. group (MARC-MOGRU)
Preference status (MARC-PREFE)
Vendor decl. status (MARC-PRENE)
Validity date of vendor declaration (MARC-PRENG)
Exemption Certificate (MARC-PRENC)
Exemption Cert. No. 9 (MARC-PRENO)
Iss.date of ex.cert. (MARC-PREND)
Military goods (MARC-ITARK)
1.1.1.1.2 Related SAP Notes
General information about this Simplification Item
SAP Note 2204534
Information about the report
ZUPDATE_MARC_FOREIGN_TRADE
SAP Note 2458666
Required and Recommended Action(s)
In case any of the fields listed above contain data, the simplification item check generates
a skippable error (RC7). This indicates that the customer can request an exemption for
this scenario after having acknowledged that the information provided in the description
has been understood and, he can continue the conversion process without making
changes to the data. The data in the above mentioned fields should be deleted in the post-
conversion phase before release of SAP S/4HANA to users.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 172
Note: The skippable error RC7 is only available if your note 2641097 has been
implemented.
3.25 S4TWL - MRP fields in Material Master
Application Components:LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267246
S4TWL - MRP fields in Material/Article
Master
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Simplification: MRP fields in Material Master in MM01/02/03
The SAP S/4HANA simplification is done on the following tabs in transaction
MM01/02/03.
Lot Size data in MRP1 Tab:
Unit of Measure Group (MARC-MEGRU)
Procurement in MRP2: MRP considers quota arrangements always, henceforth it is
not required to switch it on in the material master.
Quota arr. usage. (MARC-USEQU)
BOM explosion /dependent Requirement tab in MRP4
Selection Method (MARC-ALTSL)
Repetitive manufacturing /assembly /deployment strategy tab of MRP4
Action control (MARC-MDACH)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 173
This field is made available from SAP S/4HANA 2020. However,
there is no action required and no impact of existing data.
fair share rule (MARC-DPLFS)
push distribution (MARC-DPLPU)
Deployment horizon. (MARC-DPLHO)
Storage Location in MRP4
SLoc MRP indicator (MARD-DISKZ)
spec.proc.type SLoc (MARD-LSOBS)
Reoder Point (MARD-LMINB)
Replenishment qty. (MARD-LBSTF)
Also the backend database fields for these "omitted functionality" remains existing in
the system.
Simplification: MRP fields in Article Master in MM41/42/43
The SAP S/4HANA simplification is done on the following tabs/views in transaction
MM41/42/43.
Screen "Procurement" in views "MRP/Forecast Data: DC" and "MRP/Forecast Data:
Store", screen "General plant parameters" in views "Other Logistics Data: DC"
and "Other Logistics Data: Store"
Quota arr. usage. (MARC-USEQU)
Screen "Repetitive manufacturing/assembly" in views "MRP/Forecast Data: DC",
"Logistics: DC 2" and "MRP/Forecast Data: Store"
Action control (MARC-MDACH)
This field is made available from SAP S/4HANA 2020. However,
there is no action required and no impact of existing data.
Screen "BOM explosion/dependent requirements" in views "MRP/Forecast Data:
DC", "Logistics: DC 2" and "MRP/Forecast Data: Store"
Selection Method (MARC-ALTSL)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 174
Screen "Storage location MRP" in views "MRP/Forecast Data: DC", "Logistics: DC
2" and "MRP/Forecast Data: Store"
SLoc MRP indicator (MARD-DISKZ)
spec.proc.type SLoc (MARD-LSOBS)
Reoder Point (MARD-LMINB)
Replenishment qty. (MARD-LBSTF)
Also the backend database fields for these "omitted functionality" remains existing in
the system.
The retail customers do not need to adapt the usage of the fields MARC-MEGRU and
MARC-MDACH (the field is made available from SAP S/4HANA 2020).
Scheduling Margin Key
In S/4HANA, the scheduling margin key (field MARC-FHORI) is mandatory if defined
in t-code OMSR. By default the scheduling margin key is not mandatory.
In ECC, the scheduling margin key (field MARC-FHORI) was mandatory if MRP Type
was:
Not reorder point planning
Not time-phased planning
This was independent from the customizing in t-code OMSR.
Reasons:
SAP strives to simplify material master maintenance in SAP S/4HANA. The
scheduling margin key is not required for MRP in S/4HANA. If the scheduling
margin key is not specified, then the floats before and after production will be
zero as well as the opening period. Zero opening period means you should run the
conversion of planned orders into production orders every day.
Additional Information
For more information see simplification item in Production Planning “Storage Location
MRP”.
Related SAP Notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 175
General information about this Simplification
Item
SAP Note 2224371
MARC-MDACH
Action control (MARC-MDACH)
This field is made available from SAP S/4HANA 2020. However,
there is no action required and no impact of existing data.
fair share rule (MARC-DPLFS)
push distribution (MARC-DPLPU)
Deployment horizon. (MARC-DPLHO)
Other Terms
MRP, Simplification
3.26 S4TWL - Material Type SERV
Application Components:LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267247
S4TWL - Material Type SERV
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 176
The Product type SERV, as compared to the product type DIEN, has the product type
group assigned (2-Services). SAP recommends that Cloud and On-Premise customers of
S/4HANA use SERV over DIEN, particularly in scenarios such as lean service
procurement. However, for scenarios where the subtleties of lean service procurement
are not applicable, customers may use DIEN.
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, on-premise edition 1511release changes are done as listed below:
1. Supported user departments :
Accounting
Purchasing
Basic Data
Sales
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 177
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)
MovAvgPrice PP
Total stock
Total value PP
Std cost estimate (Button)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 178
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 179
Accounting 1
ML act indicator
Sales: sales org. 2
Product Hierarchy
Required and Recommended Action(s)
Configurations required for SERV that are part of SET:
Material type SERV(Table T134, delivery class: G)
This attribute of SERV is provided by SET content
Screen sequence control(SPRO transaction: OMT3E
Table T133K “Influencing Factors: Screen Sequence No.“ / Delivery Class:
G
Tables T133S and T133T are also part of SET content
Related SAP Notes
General information about this Simplification
Item
SAP Note 2224251
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 180
4. Commercial Project Management
4.1 S4TWL - CPM - Rate Card
Application Components:CA-CPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2318716
S4TWL - CPM - Rate Card
Symptom
You are doing a system conversion to SAP Commercial Project Management for SAP
S/4HANA. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Solution
Description
With SAP Commercial Project Management for SAP S/4HANA, the Rate Card
application is not available. Note that a functional equivalent is available.
Required and Recommended Actions
Use alternative transactions like VK11 for appropriate business requirements.
Inform key users and end users.
Other Terms
Rate Card, SAP Commercial Project Management, rate, CA-CPD, S/4HANA
4.2 S4TWL - Interface of SAP CPM with SAP Cloud for Customer
Application Components:CA-CPD
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 181
Note Type
Note Number
Note Description
Business Impact
2318733
S4TWL – Interface of SAP Commercial
Project Management with SAP Cloud for
Customer
Symptom
You are doing a system conversion to SAP Commercial Project Management for SAP
S/4HANA. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Solution
Description
There is no interface of SAP Commercial Project Management with SAP Cloud for
Customer in SAP Commercial Project Management for SAP S/4HANA.
Required and Recommended Actions
Inform key users and end users.
Other Terms
C4C, SAP Commercial Project Management, SAP Cloud for Customer, CA-CPD,
S/4HANA
4.3 S4TWL - Fiori Apps of SAP Commercial Project Management
Application Components:CA-CPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2320143
S4TWL – Fiori Apps of SAP Commercial
Project Management
Symptom
You are doing a system conversion to SAP Commercial Project Management for SAP
S/4HANA. The following SAP Commercial Project Management for SAP S/4HANA
Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 182
Solution
Description
Note that the following Smart Business analytical and transactional apps are not
immediately available with SAP Commercial Project Management for SAP S/4HANA.
F0709 My Commercial Projects
F0710 Action Items in Commercial Projects
F0779 Status Management in Commercial Projects
F0784 Overview of Commercial Projects
F0786 Costs and Revenues of Commercial Projects
F0787 Analysis of Commercial Projects
BuInformation Related to Business Processes
No influence on business processes is expected.
Required and Recommended Actions
None
Other Terms
SAP Commercial Project Management, CA-CPD, S/4HANA, Fiori apps
4.4 S4TWL - Launchpads of Gantt Chart and Commercial Project
Inception
Application Components:CA-CPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2318728
S4TWL – Launchpad of Gantt Chart and
Commercial Project Inception
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 183
You are doing a system conversion to SAP Commercial Project Management for SAP
S/4HANA. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Reason and Prerequisites
The Gantt chart launch option is dependent on the business function switche
OPS_PS_HLP_2 which is not available in SAP S/4HANA, on-premise edition.
The Commercial Project Inception launch option is dependent on the business function
switche OPS_PS_HLP_2 which is not available in Initial SAP S/4HANA, on-premise
edition.
Solution
Description
With SAP Commercial Project Management for SAP S/4HANA, the launchpads of the
following functions are not available in SAP S/4HANA, on-premise edition:
Gantt Chart (to launch master project structures of PS projects in Gantt charts)
Commercial Project Inception
Required and Recommended Actions
Inform key users and end users.
Other Terms
SAP Commercial Project Management, Gantt Chart, launchpad, launch, CA-CPD,
S/4HANA
4.5 S4TWL - Workbooks in Project Cost and Revenue Planning
Application Components:CA-CPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2323806
S4TWL - Workbooks Delivered in
Project Cost and Revenue Planning
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 184
Symptom
You are doing a system conversion to SAP Commercial Project Management for SAP
S/4HANA. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Solution
Description
Note that the following workbooks that were delivered in SAP Commercial Project
Management 1.0 are not available with SAP Commercial Project Management for SAP
S/4HANA.
/CPD/PFP_A01_IRQ0001_PL_WB01
Daily Planning (with Selection Options)
/CPD/PFP_A01_IRQ0002_PL_WB01
Daily Planning
/CPD/PFP_A01_IRQ0003_PL_WB01
Weekly Planning (with Selection Options)
/CPD/PFP_A01_IRQ0004_PL_WB01
Weekly Planning
/CPD/PFP_A01_IRQ0008_PL_WB01
MRS Weekly Planning (with Selection Options)
/CPD/PFP_A01_IRQ0009_PL_WB01
MRS Daily Planning (With Selection Options)
/CPD/PFP_A02_BOQ_PL_WB01
BOQ Monthly Planning (with Selection Options)
/CPD/PFP_A02_IRQ0001_PL_WB01
Monthly Planning
/CPD/PFP_A02_IRQ0002_PICM_WB01
PICM Monthly Planning
/CPD/PFP_A02_IRQ0003_PL_WB01
MRS Monthly Planning
/CPD/PFP_M_A1_EAC_IRQ0001_WB01
EAC Forecast
/CPD/PFP_M_A1_ETC_IRQ0002_WB01
ETC Forecast
/CPD/PFP_M_A1_ETC_IRQ0004_WB01
ETC Forecast (With Selection Option)
/CPD/PFP_M_A1_POC_IRQ0003_WB01
POC Forecast
/CPD/PFP_M_A1_POC_IRQ0008_WB01
POC Forecast with Quantity and Cost (with
selection option)
/CPD/PFP_M_A2_IRQ0001_PL_WB01
Periodic Planning
/CPD/PFP_M_A2_IRQ0002_PL_WB01
Periodic Planning (with Selection Options)
/CPD/PFP_M_A2_IRQ0003_PL_WB01
MRS Periodic Planning
/CPD/PFP_M_A2_IRQ0004_PL_WB01
MRS Periodic Planning (with Selection Options)
/CPD/PFP_M_A4_ETC_IRQ0001_WB01
ETC Forecast for Fiscal Period
/CPD/PFP_M_A4_ETC_IRQ0002_WB01
ETC Forecast for Fiscal Period (with Selection
Options)
/CPD/PFP_M_A4_ETC_IRQ0003_WB01
ETC Forecast for Fiscal Period (with Qty and
Cost)
/CPD/PFP_M_A4_ETC_IRQ0004_WB01
MRS ETC Forecast for Fiscal Period (with
Selection Options)
/CPD/PFP_M_A4_ETC_IRQ0005_WB01
MRS ETC Forecast for Fiscal Period
/CPD/PFP_M_A6_IRQ0001_PL_WB01
Periodic Cash Flow Planning (with Selection Opt
/CPD/PFP_R01_Q0001_VC_WB01
Version Comparison
Required and Recommended Actions
Inform key users and end users.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 185
SAP Commercial Project Management, CA-CPD-FP, S/4HANA, Workbooks, Project
Cost and Revenue Planning
4.6 S4TWL - CPM - Forecast from financial plan versions
Application Components:CA-CPD, CA-CPD-FP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2711002
S4TWL - CPM - Forecast from financial
plan versions
Symptom
You are performing a system conversion of SAP Commercial Project Management 2.0
SP08 to SAP S/4HANA 1809 FPS01. The following SAP S/4HANA transition worklist
item is applicable in this case.
Solution
Description
With SAP Commercial Project Management for SAP S/4HANA, the Forecast function
which you can trigger for financial plan versions with various options is not available.
Note that a functional equivalent is available.
Required and Recommended Actions
Use transaction SE38 and execute the alternative program Mass Forecast and
Transfer (/CPD/PFP_MASS_FORCAST_TRANSFER). This program enables
you to perform in-period forecasting by selecting a cut-off date.
New KPIs (up to the cut-off date) which were available in SAP Customer Project
Management 2.0 SP08 are calculated only if you select the forecast method Based on
Actuals or With Constant EAC.
However, if you select the Based on Configuration option, the forecast program will
calculate only KPIs that were made available in SAP S/4HANA 1809 FPS0. All
additional KPIs that were delivered with SAP Commercial Project Management 2.0 SP08
will not be calculated or updated.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 186
The configuration that is referred by this forecast method is available under Customizing
for Commercial Project Management, under Project Cost and Revenue Planning à Define
Plan Scenarios à Link Plan Scenario to Resource Types.
Other Terms
In-period forecast with cut-off date, SAP Commercial Project Management, CA-CPD,
S/4HANA,CA-CPD-FP,
4.7 S4TWL - CPM - Personal Activity List
Application Components:CA-CPD, CA-CPD-PCM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2712156
S4TWL - CPM - Personal Activity List
Symptom
You are doing a system conversion to SAP Commercial Project Management for SAP
S/4HANA 1809 or upgrading from earlier versions of S/4HANA Commercial Project
Management. The following SAP S/4HANA Transition Worklist item is applicable in
this case.
Reason and Prerequisites
Project activity app provides simillar functionality to that of personal activity list
Solution
Description
With SAP Commercial Project Management for SAP S/4HANA 1809, "Personal Activity
List" is not available.Navigation to the Personal Activity List is withdrawn from
multiproject overview application and from project workspace.Note that a functional
equivalent is available.
Required and Recommended Actions
Use Project Activities application for managing activities.
Adapt related custom enhancements.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 187
Inform key users and end users.
Other Terms
Personal Activity List, SAP Commercial Project Management, CA-CPD, S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 188
5. Commodity Management
5.1 S4TWL - CM: Simplified Market Data
Application Components:SD-BF-CPE, LO-CMM-BF, MM-PUR-GF-CPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2460737
S4TWL - CPE Simplified Market Data
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the Commodity Pricing Engine only
supports market data based on Derivative Contract Specifications (DCS). The market
data defined using Quotation Source, - Type and - Name are no longer supported.
Business Process related information
Quotations have to be defined based on Quotation Rules
All relevant quotation rules have to be transfered to use market data based on DCS.
Relevant open documents have to be closed before the conversion
MM Contracts are not supported in the current version
The assigned document 'Cookbook From Exchange to DCS' describes examples how to
set up Derivative Contract Specifications (DCS).
Required and Recommended Action(s)
Source system EHP 7 and EHP 8 (Conversion to DCS based market data has to be done
in the source system)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 189
In the assigned document 'Cookbook Market Data in Commodity Managment', the
process how to replace quotation Source, -Type and - Name based market data to
DCS based market data is described. This step has to be executred in the source
system before starting the conversion.
Accessing market data moved to the quotation rule, the definition as part of the term
itself is no longer supported. All relevant settings have to be transferred to a
quoation rule, assigned to the term. The assigned document 'Function in Details -
Quotation Rule' describes the necessary steps to convert the data.
Source System before EHP 7 (Conversion to DCS based market data has to be done in
the target system)
In the assigned document 'Conversion to DCS based Market Data before EHP7' a project
based solution how to convert the data is described.
5.2 S4TWL - CM: Simplified CPE Activation
Application Components:LO-CMM-BF, SD-BF-CPE, MM-PUR-GF-CPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2461004
S4TWL - CM: CPE Simplified CPE
Activation
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the activation of the Commodity Pricing
Engine (CPE), the flagging of Condition Types to be relevant for CPE and the required
settings in the pricing procedure are simplified. This is especially relevant if you are
using CPE together with IS-OIL.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 190
The settings for the activation of the CPE have to be adjusted manually, if you are using
CPE together with IS-OIL. If no IS-OIL is active, the conversion is done automatically
during the update.
Required and Recommended Action(s)
In the assigned document 'Function in Details - Simplified CPE Activation', the process
how to adjust the relevant settings is described.
5.3 S4TWL - CM: CPE Simplified Formula Assembly & Formula
Evaluation
Application Components:SD-BF-CPE, MM-PUR-GF-CPE, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2461021
S4TWL - CM: CPE Simplified Formula
Assembley & Formula Evaluation
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the Formula Assembly of the Commodity
Pricing Engine (CPE) is done based on BRF+ and for Forumla Evaluation, the access to
document data has been simplified.
Business Process related information
The configuration of Formula Assembly has to be transferred to BRF+.
Customer coding using the field mapping information in Formula Evaluation has to
be adjusted.
The necessary adjustments are done in the target system
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 191
In the assigned document 'Cookbook Formula Assembly based on BRFplus', the
process how to transfer Formula Assembly to BRF+ is described.
In the assigned document 'Function in Details - Formula Evaluation', all the necessary
information how to adjust customer coding is included.
5.4 S4TWL - CM: CPE Simplification of Routines & Rules
Application Components:LO-CMM-BF, MM-PUR-GF-CPE, SD-BF-CPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2461014
S4TWL - CM: CPE Simplification of
Routines & Rules
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 some of the delivered routiones for the
Commodity Pricing Engine (CPE) are simplified, some others are no longer available.
Business Process related information
All relevant routines and rules have to be adjusted.
Relevant open documents have to be closed before the conversion (see attached
document 'Cookbook Open Documents using not supported routines').
Required and Recommended Action(s)
In the attached document 'Cookbook Supported CPE Routines', the affected routines are
described.
The attached document 'Cookbook Application independent Reference Date Routines in
Commodity Pricing Eingine' describes the simpliefied application independent reference
date routines and the necessary steps required in conversion.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 192
5.5 S4TWL - CM: CPE Simplified Data Model
Application Components:MM-PUR-GF-CPE, SD-BF-CPE, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2461007
S4TWL - CM: CPE Simplified Data
Model
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the data model of the Commodity Pricing
Engine has been simplified.
Business Process related information
The necessary conversions are done during installation
Required and Recommended Action(s)
Actions are only relevant for customer specific coding. Details are described in the
attached document 'Function in Details - Simplified Data Model'.
5.6 S4TWL - Simplified Commodity Curves
Application Components:LO-CMM-BF, FIN-FSCM-TRM-MR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2551913
S4TWL - CM: Simplified Commodity
Curves
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 193
You are doing a system conversion to SAP S/4HANA FPS1, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
With SAP S/4HANA, on-premise edition 1709 FPS1, the master data of Commodity
Curves have been sinplified. As part of the ovall simplification of the data model in
Commodity Management, the Commodity ID has been deprecated. Based on this
simplification, also the definition and the access to Commodity Curves is simplified and
the only supported commodity Curve Category is '2 Based on DCS'. Commodity Curves
are now defined and accessed using the DCS ID, MIC (optional) and Commodity Curve
Type.
For the usage of Commodity Curves within the Commodity Pricing Engine, it is no loger
required to activate The Business Functions of Commodity Management for Treasury
(FIN_TRM_COMM_RM).
Note 2553281 describes the process regarding the depracation of the Commodity ID in
Commodity Management. Details regarding the simplified Commodity Curves can be
found in chapter 'Conversion of Commodity Curves'.
5.7 S4TWL - Simplified DCS Access
Application Components:LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2551960
S4TWL - CM: Simplified DCS Access
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
With SAP S/4HANA, on-premise edition 1709 FPS1, the access to DCS based Market
Data, Commodity Curves and Financial Transactions has been simplified. Details about
the simplification can be found in the attached document 'Function in Details - Simplified
DCS Access'.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 194
5.8 S4TWL - Simplification in Position Reporting for Financial
Transactions
Application Components:LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2556089
S4TWL - Simplification in Position
Reporting for Financial Transactions
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case
Solution
Description
With SAP S/4HANA the Commodity Risk Management provides Position Reporting for
the Financial Transaction Management. All analytical data is persisted based
on versioned data records and exposed through Core Data Servcies (DCS) to the
analytical tools like SAP Analysis for Microsoft Excel .
Business Process related information
In the Business Suite the Financial Transaction data that is relevant for the analytical
source data for position reporting was stored in the versioned data base table for
commodity exposures (TEXT_CTY_EXPOS) . This data base table was also used for
logistical data via the Logistics to Treasury Management interface (LOG2TRM). The
update happened via a background process.
In S4 1709 FPS01 there is a new data flow to support analytical reporting. The Financial
Transaction data is updated automatically from all relevant Financial Transaction
business processes into a new data base table (CMM_VFIND) in real time. In case of an
error it is possible to monitor messages in the application log and to re-process.
S4 1709 FPS01 the analytical reporting keyfigures are provided in one single technology
that provides a reporting CDS stack in order to allow commodity position snapshot
reporting across commodities.
Functional Restrictions
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 195
In S4 1709 FPS01 the Position Reporting for Financial Transactions does not
support option delta factors.
Required and Recommended Action(s)
As described in the attached 'Function in Details - Simplification in Postion
Reporting for Financial Transactions' a couple of steps need to be considered:
historical position data can not be migrated to the new S/4HANA analytical data
model. The data should be exported BEFORE the S4 upgrade to keep it accessible
from an XLS or BW InfoCube
Financial Transaction data can be loaded initially into the database table which is
used in S4 1709 FPS1 onwards for position reporting
if BEX Queries on top of Operational Data Providers are used in the Business Suite,
these BEX Queries need to be converted into CDS Queries in S4 on top of the
new CDS InterfaceViews
if CDS Queries have been used for Position Reporting in the Suite, these need to be
converted into CDS Queries in S4 on top of the new CDS InterfaceViews
Other Terms
Commodity Risk Management, Commodity Exposure Positions
5.9 S4TWL - Simplified Data Flow of logistics data for Risk Reporting
Database
Application Components:LO-CMM-BF, LO-CMM-ANL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2547343
S4TWL - CM: Simplified Data Flow of
Logistics Data for Commodity Position
Reporting
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 196
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the data flow and persistencies of
commodity price risk data derived from logistics documents and transactions have been
revised.
Business Process related information
As described in the attached word file, a reduced number of background queues needs
to be monitored for errors.
Error handling for commodity position data does not require the usage of transaction
LITRMS anymore.
Instead, queues in error need to be monitored and re-started, after the errors were
resolved.
Required and Recommended Action(s)
In the attached document, you can find information on the revised handling of
background processes and thus requirements on system monitoring.
Other Terms
Error handling, Commodity Position Reporting
5.10 S4TWL - Position Reporting on versioned pricing data
Application Components:LO-CMM-ANL, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2547347
S4TWL - CM: Commodity Position
Reporting on Versioned Pricing Data
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 197
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the database table and available
infosources for commodiy price risk data required for commodity position reporting got
unified and revised.
Business Process related information
The Business Suite's Commodity Position Reporting used raw expsoures created from
logistics documents and transactions.
Based on the raw exposures, the commodity position table TEXT_CTY_EXPOS was
updated for the Commodity Position Reporting. In S4H, the data footprint and
processing layers were reduced.
Key figures, which were formerly exposed in different technology stacks (ODP/BEx
versus CDS views) are now provided in one single technology and reporting stack only to
allow a unified reporting for different commodities and scenarios.
Required and Recommended Action(s)
As described in the attached 'Function in Details - Position Reporting on Versioned
Pricing Data' word file, the following steps need to be performed:
Historical position data should be exported BEFORE the S4HANA upgrade to keep
the data accessible from an XLS or BW InfoCube
Logistics transactions need to be loaded to the database table, which is used in S4H
1709 FPS1 onwards for the Commodity Position Reporting
If BEx queries on top of Operational Data Providers (ODP) are used in the Business
Suite, these BEx queries must be converted to CDS queries in S4H on top of the
new CDS interface views
If CDS queries have been used for the Commodity Position Reporting in the Business
Suite, these queries need to be converted to CDS queries in S4H on top of the new
CDS interface views
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 198
Other Terms
ODP, BEx Query, CDS views
5.11 S4TWL - Hedge Management for logistics transactions
Application Components:LO-CMM-ANL, FIN-FSCM-TRM-CRM, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2556106
S4TWL - CM: Hedge Management for
Logistics Transactions
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709, the raw exposure interface for logistics
transactions has been deprecated.
Business Process related information
In the Business Suite, raw exposures were created from logistics documents based on the
commodity pricing information.
For these raw exposures, risk hedges could be managed.
Required and Recommended Action(s)
Check, whether you used raw exposure information for Hedge Accounting for Exposures.
In S4H 1709 FPS01, Commodity Position Reporting is provided without raw exposures.
Based on reported positions of logistics transactions, the corresponding risk hedges must
be triggered manually.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 199
Hedge Accounting for Exposures, HACC
5.12 S4TWL - Position Reports delivered by Agricultural Contract
Management
Application Components:LO-CMM-BF, LO-CMM-ANL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2556134
S4TWL - CM: Agri-Specific Commodity
Position Queries
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709, the database table and available
infosources for risk data required for position reporting got unified and revised.
New Core Data Services (CDS) views are provided to determine keyfigures for position
reporting.
For keyfigures, which are specific for Futures/Basis pricing - as common in the
Agricultural industry - CDS (interface) views are available.
However, queries on top of these are not provided with the software layer of Commodity
Management.
Instead, these are provided in the Agicultural Contract Managament (ACM) software
layer.
Business Process related information
Agri-specific Queries include
- Futures Risk / Slate report with a keyfigure layout tailored to Future / Basis pricing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 200
- Basis / Premium report
- Price Type report
Required and Recommended Action(s)
If you require Agri-specific queries, check the availability of Agicultural Contract
Managament (ACM) in your system.
If ACM is not available you may need to create queries on top of the available
(Commodity Management) interface views during system implementation.
Other Terms
ACM, agricultural industry, commodity position reporting, CDS views
5.13 S4TWL - Risk Determination and Pricing for MM Contracts not
supported yet
Application Components:LO-CMM-BF, LO-CMM-ANL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2560298
S4TWL - Commodity Pricing in
Purchasing Contracts and Scheduling
Agreements
Symptom
Within S/4HANA 1709 - from FPS00 until FPS02, MM Contracts and Scheduling
Agreements do not support the following functionality:
Risk Distribution Plan (RDP)
Usage of Commodity Pricing Engine (CPE) and Configurable Parameters and
Formulas (CPF)
Starting with S/4HANA 1709 FPS03, MM Contracts are supported with the following
functionality:
Usage of Commodity Pricing Engine (CPE) and Configuable Parameters and
Formulas (CPF) using time independent conditions (document conditions).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 201
Existing MM Contracts (with time-dependent conditions) have to be closed and
new MM contracts with time independent conditions have to be created for the
open quantity and validity period.
Risk Distribution Plan (RDP) for time independent conditions.
Starting with S/4HANA 2020 FPS00 Scheduling Agreements are supported with
commodity pricing (CPE, CPF) using time-dependent conditions.
Solution
Before S/4HANA 1709 FPS03, Customers converting to S/4HANA using RDPs or
CPE/CPF within MM Contracts or Scheduling Agreements cannot convert.
Other Terms
RDP, CPE, CPF, Purchasing Contract, Scheduling Agreements
5.14 S4TWL - Unification of supported technologies in analytical data
provisioning
Application Components:LO-CMM-ANL, FIN-FSCM-TRM-CRM, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2555990
S4TWL - CM: Unification of
Technologies for Analytical Data
Provision
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709 the technologies by which analytical data
is provided got unified:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 202
- Operational Data Providers (ODP), BW Extractors and BEX Queries on top of these
providing Position Reporting and Mark-to-Market are deprecated
- HANA Live calculation views are not supported for Commodity Position Reporting and
Mark-to-Market valuation/reporting.
Instead, all analytical data is exposed through Core Data Services (CDS) views.
Business Process related information
In the Business Suite's Commodity Position Reporting, different sources of analytical
information were available in different technologies:
Some data were reported based on Operational Data Providers (ODPs), some data based
on CDS views, some information was exposed through HANA Live calculation views.
In S4HANA, all analytical data for commodities is exposed through CDS views reducing
the TCO by using a unified technology.
Required and Recommended Action(s)
Check, whether the required analytical data is provided by CDS views with S4H 1709
FPS01.
Note, that some analytical information for commodities formerly provided in the
Business Suite may not be supported yet. These restrictions are documented in other
simplification items.
You may need to convert your queries to enable the consumption by the new CDS views
available in S4H.
Other Terms
ODP, BEx Query, CDS view, Commodity Position Reporting, Commodity Position
Overview, MtM
5.15 S4TWL - Risk Determination on a schedule line level
Application Components:LO-CMM-ANL, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 203
Business Impact
2556063
S4TWL - CM: Commodity Price Risk
Determination from Schedule Lines
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709, the commodity risk determination for
commodity price risks got simplified.
Business Process related information
In the Business Suite it was possible to activate the commodity price risk determination
based on schedule lines of a purchase order or sales order.
For this purpose a price simulation was called in the background for each schedule line
with the schedule line date as reference date and pertaining quantity.
This is not supported in S4HANA.
Required and Recommended Action(s)
If you require to split and distribute commodity price risk information, you need to split it
on the item level accordingly.
Other Terms
Schedule Line Item, Purchase Order, Sales Order, Delivery Schedule
5.16 S4TWL - Simplification of DCS based Market Data Handling for Fin
Transactions
Application Components:FIN-FSCM-TRM-CRM, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 204
Business Impact
2556164
S4TWL - Simplification of DCS-Based
Market Data Mngmt for Financial
Transactions: DCS ID Extension
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case
Reason and Prerequisites
The DCS ID with data type 6 chars used to be a restriction for customers and
did not allow to enter a meaningful description, and to support longer market data codes
from market data providers for commodity prices based on commodity forward indexes.
Solution
With SAP S/4HANA, on-premise edition 1709 FPS1, the Derivative Contract
Specification Identifier (DCSID) as defined in the system configuration has been
extended by using a DCSID data type with 20 CHAR. With this data type you can
describe the entity in more detail such as, for example, with reference to the material, the
exchange and the location.
Business Process-Related Information
The market data interface is adjusted to support the new DCSID data type.
The access to market data and commodity curves is now based on the longer DCSID. The
Financial Transaction Management and the related processes are adjusted accordingly.
Required and Recommended Action(s)
Actions are only nessecary for customer-specific coding. Manual conversion steps are
need for the conversion of datafeed functionality. For more information, see SAP Note
2553281 - Cookbook Deprecation of Commodity ID in Commodity Management.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 205
Derivative Contract Specification (DCS), DCS ID, market data feed
5.17 S4TWL - Deprecation of Non DCS based Market Data for Financial
Transactions
Application Components:FIN-FSCM-TRM-CRM, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2556220
S4TWL - Simplification of DCS-Based
Market Data Management for Financial
Transactions
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case
Reason and Prerequisites
Check in your business suite (ERP) implementation, whether and which market data are
based on DCS
Solution
Description
With SAP S/4HANA, on-premise edition 1709, the commodity market data is based only
on definitions of derivative constract specifications (DCS). The following derivative
categories are supported for using the DCS:
Commodity Future
Listed Option
Commodity Forward Index
Financial transaction pricing data uses DCS-based market data only.
Business Process-Related Information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 206
To support the DCS-based market data including DCS-based commodity curves, the
Financial Transaction Management and its commodity-specific processes like price
adjustments for unpriced commodity derivatives were adjusted accordingly.
Required and Recommended Action(s)
Check your Business Suite (SAP ERP) implementation, whether you used market data
based on quotation source, quotation type, quotation name.
The market data must be converted to support DCS-based market data.
The financial transactions pricing data based on the previous market data concept can be
converted according to the cookbook (see SAP note 2553281 - Cookbook Deprecation of
Commodity ID in Commodity Risk Management).
Other Terms
Commodity Risk Management, Derivative Contract Specification/DCS, Market Identifier
Code/MIC, commodity
5.18 S4TWL - Deprecation of functions using Non DCS based Market Data
Application Components:LO-CMM-BF, FIN-FSCM-TRM-CRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2556176
S4TWL - Deprecation of Non-DCS-
Based Market Data for Financial
Transactions 2: VaR, Market Data Shifts
and Scenarios, Statistics Calculator
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case
Solution
Business Process-Related Information
In the Business Suite (ERP), the market data that was not related to derivative contracts
specification (DCS) and was based on quotation name, quotation type, quotation source
could be used for
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 207
volatilities with moneyness for OTC commodity options
the definition of shifts and scenarios
the statistics calculator for volatilities and correlations
calculation of value at risk results
creation of generic transactions for market risk analyzer analytics
Hedge Accounting for commodity price risks and exposures from financial and
logistics transactions
Required and Recommended Action(s)
These functions are not avaliable in S/4HANA 1709. It is planned to support these
functions in a future release of Commodity Management.
Other Terms
Commodity Risk Management, Value at Risk, Market Data Shift, Market Data Scenario,
Market Risk Analyzer (MRA) MRA simulation, Statistics Calculator for Volatilities,
Correlations
5.19 S4TWL - Simplified Data Model/Master Data
Application Components:LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2554440
S4TWL - Simplified Commodity
Management Data Model / Master Data
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 208
The master data model for the commodity master data in S/4HANA has been simplified
and allows a single definition of the commodity as an attribute of the Derivative Contract
Specification (DCS). This allows a standardized access to the DCS-based market data
for derivative transactions and processes, and for logistics transactions.
The determination of market data by quotation name, quotation type and quotation source
is deprecated in S/4HANA (see reference note).
Solution
Description
With SAP S/4HANA on-premise edition 1709 FPS1 the data model of Commodity
Management master data has been simplified. The commodity as a system entity to
represent traded material is defined as attribute of derivative contact specifications
(DCS). To make the deprecation of commodity master data possible, the definition of
market data and the market data access were adjusted accordingly. For the assignment of
the DCS and market identifier code (MIC) to financial transaction data, in order to
replace the Commodity ID, all financial transactions and processes were adjusted.
Business Process related information
The following functional areas are adjusted:
Financial Transaction Management
BAPIs for Financial Transactions
FUT and LOPT - Class Data
BAPIs for Class Data
Commodity Price Adjustments
Mass Cash Settlement
MRA Basic Functions and Reports: Analysis Parameters, JBRX,
TPM60, AISGENKF
Functional Restrictions
see business impact note 2556176
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 209
For customer specific coding and configuration please refer to the Custom Code Impact
Note. Manual conversion steps are needed. Please refer to the details that are described in
the SAP Note 2553281 - Cookbook Deprecation of Commodity ID in Commodity Risk
Management.
Other Terms
Commodity Risk Management, Commodity ID, Commodity Master Data,
FCZZ, Financial Transactions, Real Commodity, Abstract Commodity, Physical
Commodity, Derivative Contract Specification, DCS
5.20 S4TWL – Contract Processing Monitor & Logistical Options w/ GTM
not supported
Application Components:LO-GT-CMM, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2672696
S4TWL – Integration of Contract
Processing Monitor(CPM) and Logistical
Options(LOP) with GTM not supported
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
With SAP S/4HANA, All on-premise editions, the integration of Global Trade
Management (GTM) with Commodity Management processes (not ACM!) is partially
supported.
Contract Processing Monitor (CPM) and Logistical Options (LOP) are not supported in
S/4HANA. Also, there is no equivalent available for the same.
5.21 S4TWL - Mark-to-Market & Profit-and-Loss Reporting for logistics
transactions
Application Components:LO-CMM-BF, LO-CMM-ANL
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 210
Note Type
Note Number
Note Description
Business Impact
2591598
S4TWL - CM: Mark-to-Market & Profit-
and-Loss for logistics transactions
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1709, the database table used for Mark-to-
Market Reporting got unified.
Instead of three database tables storing valuation results for Purchasing, Sales and
Trading Contracts, only one table is supported storing versioned pricing source data.
Business Process related information
The Business Suite's Mark-to-Market Reporting stored valuation results in the tables
CMM_MTM_PO, CMM_MTM_SO and WB2B_CMM_MTM_TC.
However, this did not facilitate snapshot-based reporting (such as the End-of-Day
Snapshot Mark-To-Market reporting) since the market data may not be present in the
system at the time when these snapshots need to be valued.
For this purpose, to store versioned source data, table CMM_VLOGP had been
introduced with SAP ERP 6.0 Enhancement Package 8.
Based on table CMM_VLOGP, the valuation with market data is performed at reporting
time.
In S4H only, table CMM_VLOGP is supported as basis for the Mark-to-Market reporting
on logistics transactions.
Required and Recommended Action(s)
As described in the attached document 'Function in Details - Mark-to-Market and Profit-
and-Loss for Logistics Transactions', the following steps need to be performed:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 211
If using discounting, you need to make use of forward FX rates instead to convert
between currencies towards a statistics currency.
If using aggregation, you need to define reporting groups in the Customizing for
Commodity Risk Management and aggregate at these groups at reporting time.
If BEx queries on top of Operational Data Providers (ODP) are used in SAP ERP,
these BEx queries must be converted to CDS queries in S4H on top of the
provided CDS interface views.
Other Terms
CMM_VLOGP CMM_MTM_PO CMM_MTM_SO WB2B_CMM_MTM_TC
5.22 S4TWL - Mark-to-Market & Profit-and-Loss Reporting for Derivatives
Application Components:FIN-FSCM-TRM-CRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2596369
S4TWL - Mark-to-Market & Profit-and-
Loss Reporting for Derivatives
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA the Commodity Risk Management provides Markt-to-Market and
Profit-and-Loss Reporting for the Financial Transaction Management. All analytical data
and analytical results are persisted based on versioned data records and exposed through
Core Data Servcies (DCS) to the analytical tools like SAP Analysis for Microsoft Excel .
Business Process related information
In the Business Suite the Financial Transaction data that is relevant for the analytical
source data for Markt-to-Market and Profit-and-Loss reporting was stored in Market Risk
Analyzer (MRA) data base tables. The analytical results were provided in the framework
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 212
of the MRA functionality 'Determination of Single Records' and stored in the Result Data
Base.
In S/4HANA 1709 FPS02 there is a new data flow to support analytical reporting. The
Financial Transaction data is updated automatically from all relevant Financial
Transaction business processes into new data base tables. In case of an error it is possible
to monitor messages in the application log and to re-process.
In S/4HANA 1709 FPS02 the analytical reporting key figures are provided in one single
technology that provides a reporting CDS stack in order to allow Mark-to-Market and
Profit-and-Loss snapshot reporting across commodities.
Functional Restrictions
In S/4HANA 1709 FPS02 the Position, Markt-to-Market and Profit-and-Loss Reporting
for Financial Transactions does not support option delta factors.
Required and Recommended Action(s)
For the Simplification in Markt-to-Market and Profit-and-Loss Reporting for Financial
Transactions a couple of steps need to be considered:
historical position data can not be migrated to the new S/4HANA analytical data
model. The data should be exported BEFORE the S/4HANA upgrade to keep it
accessible from an XLS or BW InfoCube
Financial Transaction data can be loaded initially into the database tables which is
used in S/4HANA 1709 FPS2 onwards for Markt-to-Market and Profit-and-Loss
reporting
if BEX Queries on top of Operational Data Providers are used in the Business Suite,
these BEX Queries need to be converted into CDS Queries in S/4HANA on top of
the new CDS InterfaceViews
if CDS Queries have been used for Markt-to-Market and Profit-and-Loss Reporting in
the Suite, these need to be converted into CDS Queries in S/4HANA on top of the
new CDS InterfaceViews
Other Terms
Commodity Risk Management, Commodity Mark-to-Market Reporting for Derivatives,
Commodity Profit -and -Loss Reporting for Derivatives
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 213
5.23 S4TWL - Mark to Market Accounting Changes
Application Components:LO-CMM-BF, LO-CMM-ANL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2608098
S4 PreChecks: Conversion Report of
Mark-to-Market Accounting for transition
from Business Suite to S/4 HANA
Symptom
S4TC Pre-Transition Checks for Mark-to-Market Accounting returns following error
messages:
"Action Required in client XXX: WBRP entries available for conversion
exist. Migration cannot proceed without pre-conversion. See SAP Note 2608098."
Reason and Prerequisites
Mark-to-Market(MtM) Accounting uses Agency Business (AB) as a vehicle to create and
reverse accounting documents. Data base optimization in S/4 HANA are performed in
AB.The pre-conversion report RCMM_MTM_CONVERSION from this note executes
the obligatory conversion of data for already created AB documents with MtM
references. The S4TC Pre-Transition Checks for Mark-to-Market Accounting has to be
successful after the execution of the pre-conversion report
RCMM_MTM_CONVERSION
Solution
For source release SAP_APPL 618 implement this note. (Further releases up to and
including S/4HANA 1709 FPS1 are added here to keep the report version in
sync.)
For all conversions, run the report RCMM_MTM_CONVERSION in the source
system in execution mode using the check box. Do this for each client indicated in
the error messages.
Other Terms
S/4 HANA migration, Pre-Checks, LO-CMM, Conversion Report, Markt-to-Market
Accounting
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 214
5.24 S4TWL – Integration of Pricing and Payment Events in GTM with
Commodity Mngmt.
Application Components:LO-CMM-BF, LO-GT-CMM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2671009
S4TWL – Integration of Pricing and
Payment Events in GTM with
Commodity Management
Symptom
You are doing a system conversion to SAP S/4HANA 1809 FPS0, on-premise edition.
The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
With SAP S/4HANA, on-premise edition 1809, the integration of Global Trade
Management (GTM) with Commodity Management processes (not ACM!) is partially
supported.
Pricing and Payement Events integration in Commodity Management is now supported in
GTM. This functionaility is encapsulated within the Business Function
ISR_GLT_CMMINTEG.
NOTE: For functionalities that existed earlier in business function
ISR_GLT_CMMINTEG, please refer to notes 2551942 and 2671010
5.25 S4TWL - Performance Optimization of Risk Analytics CDS Views
Application Components:LO-CMM-BF, LO-CMM-ANL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3327638
S4TWL - CM Replacement of Risk
Analytics CDS Views by new
performance optimized versions
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 215
With S4 HANA 2021 new CDS views for Commodity Risk Analytics have been
delivered having multiple performance optimizations compared to the CDS views
delivered in lower versions.
As some of these changes require a data migration in underlying risk information tables
(like table CMM_VLOGP), the optimization have been shipped in new views.
From S4HANA 2023 FP0 upwards the old CDS views are deprecated and usage should
be removed as they will be deleted in a future Release.
Reason and Prerequisites
You are upgrading to S4HANA 2023 FP0 or higher.
Your are using CDS views which will get obsolete in subsequent Releases.
Solution
Requied Data migration is happening with Silent Data Migration (SDMI) when
upgrading to 2021 FP0 or higher.
If using SAP Standard Queries listed below as deprecated, use the new Query delivered
as replacement as per belows list.
If having an own Query on top of a Cube listed below as deprecated, adapt your Query to
use the new Cube.
Obsolete
to be replaced by
Descriptio
n
Queries
C_CMMDTYMTMLOGEODQRY
C_CMMDTYMTMLOGENDOFDAYQRY_2
MtM end-
of-day
C_CMMDTYMTMLOGDODQRY
C_CMMDTYMTMLOGDAYOVERDAYQRY
_2
MtM day-
over-day
C_CMMDTYMTMLOGCURQRY
C_CMMDTYMTMLOGCURRENTDAYQRY
_2
MTM
Current
Day
C_CMMDTYMTMSTKEODQRY
C_CMMDTYSTOCKENDOFDAYQRY
MtM stock
day-over-
day
C_CMMDTYBPPNLVALUE_QUERY
C_CMMDTYBEGINPOSPNLVALQRY
Beginning
Position
(P/L)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 216
C_CMMDTYNAPNLVALUE_QUERY
C_CMMDTYNEWACTPNLVALQRY
New
Activity
(P/L)
C_CMMDTYPOSENDOFDAYQRY
C_CMMDTYPOSENDOFDAYQRY_2
Position
end of
day
C_CMMDTYPOSCURRENTDATEQR
Y
C_CMMDTYPOSCURRENTDATEQRY_2
Position
current
day
C_CMMDTYPOSDAYOVERDAYQRY
C_CMMDTYPOSDAYOVERDAYQRY_2
Position
Day Over
Day
C_CMMDTYMTMENDOFDAYQRY
C_CMMDTYMTMENDOFDAYQRY_2
Union MtM
End-of-
Day
C_CMMDTYMTMDAYOVERDAYQRY
C_CMMDTYMTMDAYOVERDAYQRY_2
Union MtM
Day over
Day
C_CMMDTYMTMCURRENTDATEQR
Y
C_CMMDTYMTMCURRENTDATEQRY_2
Union MtM
Current
Value
C_CMMDTYPOSVALUEATRISKQRY
C_CMMDTYPOSVALUEATRISKQRY_2
Commodit
y Position
EoD
Interface –
Query
Cubes
I_CMMDTYMTMVALUECUBE
I_CMMDTYMTMVALUECUBE_2
MTM
Cube
I_CMMDTYMTMVALUECUBE
I_CMMDTYSTOCKVALUECUBE
MTM
Stock
Cube
I_CMMDTYMTMLOGFINVALCUBE
I_CMMDTYMTMLOGFINVALCUBE_2
UNION
MTM
Cube
I_CMMDTYBPPNLVALUE_CUBE
I_CMMDTYBEGINPOSPNLVALCUBE
Beginning
Position
(P/L) Cube
I_CMMDTYNAPNLVALUE_CUBE
I_CMMDTYNEWACTPNLVALCUBE
New
Activity
(P/L) Cub
e
I_CMMDTYPOSITIONREPQTYCUBE
I_CMMDTYPOSITIONREPQTYCUBE_2
Position
CUbe
I_CMMDTYPOSVALUEATRISKCUBE
I_CMMDTYPOSVALATRISKCUBE_2
Commodit
y Position
Interface -
Cube
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 217
Other Public I-Views
I_CMMDTYBPPNLVALUE
I_CMMDTYBEGINPOSPNLVALUE
PnL Value
for
Beginning
Position
I_CMMDTYNAPNLVALUE
I_CMMDTYNEWACTPNLVALUE
Commodit
y PnL
Value New
activity
I_CMMDTYPOSVALUEATRISKCNVR
SN
I_CMMDTYPOSVALUEATRISKCNVRSN_
2
Conversio
n of
quantity
fields
5.26 S4TWL - CM: CCTR CPE Commodity Code Harmonization
Application Components:LO-CMM-BF, MM-PUR-GF-CPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3020849
S4TWL - CM: CCTR CPE Commodity
Code Harmonization
Symptom
You are doing a system upgrade of SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case. During the upgrade, you have received
a return code ERROR_SKIPPABLE (7) from consistency check
class CLS4SIC_LOG_CMM_PRC_CMMDTY_HAR.
Solution
Description
This simplification item is about the harmonization of commodity codes between central
purchase contract and commodity management. In addition to the following guidelines,
please also raise a support ticket to software component MM-PUR-GF-CPE with
reference to this SAP Note.
Business Process related information
"Commodity Code" in the Central Contract is an identifier for a group of raw materials
defined in customizing table MMPUR_CMDT_CODES.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 218
The target of this simplification item is to replace these commodity codes with the
commodities of Commodity Management defined in customizing table
TBAC_PHYSCOMM.
The source identifier "Commodity Code" permits a string length of up to 50 characters,
whereas the target identifier "Commodity" can have a maximum of 18 characters only. If
a commodity code exceeds 18 characters, you must manually shorten the length of the
identifier accordingly.
In addition, for the target Customizing, you must manually define a unit of measure
during the migration,
This replacement allows an easier integration of the business area Commodity
Management with Central Procurement, or vice versa.
Relevancy Check
This note is relevant for the following use cases:
For SAP S/4HANA on Premise customers, who upgrade to S/4HANA 2021
You have already been used central purchase contract functionalities and have
defined commodity codes within the customizing table
MMPUR_CMDT_CODES MMPUR.
You have maintained commodity quantity data within central purchase contracts. For
SAP S/4HANA on Premise customers, this can be checked by using transaction
SE16 and checking, whether database table EKPO_WEIGHTS has any content.
If the prior mentioned requirements apply, you must execute the migration steps
stated previously before the upgrade to S/4HANA on Premise 2022.
Required and Recommended Actions
After the technical upgrade in the target release, the migration is to be performed in 3
steps. To guide you through the migration process, an assistance report is provided,
which can be accessed in the following ways:
SAP S/4HANA on Premise customers can perform this report by using transaction
CMM_MIGRTN_COMMCODE.
SAP S/4HANA on Premise customers can execute the report
CMM_MIGRATE_COMMODITY_CODE via transaction SE38.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 219
SAP S/4HANA on Premise customers can access the Fiori Launchpad tile
“Commodity Code Migration Assistant”, which can be found in business catalog
“Commodity Management – Commodity Code Migration”.
For SAP S/4HANA on Premise customers:
Business catalog SAP_CMM_BC_CMMDTY_MIGRTN and business catalog
group SAP_CMM_BCG_CMMDTY_MIGRTN are part of the business role
SAP_BR_CENTRAL_PURCHASER.
1. Customizing Data Migration
For the migration of the customizing entries, perform the following steps:
Open the Fiori tile “Commodity Code Migration Assistant”. If this tile is not
present on your Fiori Launchpad, use “App Finder” to search for it.
A table control is presented with a list of available commodity codes within
your system. This list contains the “Migration Status” flag, which
indicates whether a commodity code has already been migrated. If a
commodity code has already been migrated, the data cannot be adjusted
anymore within this report.
If either the commodity or the mapping needs to be adjusted, use the
previously mentioned self-service configuration UIs for the adjustment.
If the commodity code length is below or equal to 18 characters, the system
will propose the commodity identifier. You can adjust this commodity
identifier if required. If the commodity code length exceeds 18 characters,
you must provide a commodity identifier with less or equal to 18
characters.
Enter a unit of measure for every commodity.
Select the “Migrate Customizing” button within the toolbar. If the system asks
for a customizing transport, provide a propriate one.
If problems occurred during the customizing migration see the message log.
The customizing changes must be transported from your quality tenant to your productive
tenant.
2. Application Data Migration
As a next step application data can be migrated within the quality tenant for testing
purposes and in addition within your productive tenant. SAP strongly recommends to
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 220
execute this step during times where users do not actively edit central contracts.. To
execute the application data migration, proceed as follows:
Access the assistant with the Fiori tile “Commodity Code Migration
Assistant” and select the “Migrate Application Data" button.
Now, the system shows a list of messages. If errors occurred during
processing, check the errors. Repeat executing the migrate function until
no error messages occurred. If an object was locked by another user, re-
execute this step.
With the migration of the application data, the new solution has not been activated yet on
the user interface. You will still see the old commodity code fields within the central
contract but, if editing the commodity quantity records, the system will keep the values in
sync.
Note:
Ensure that all central contracts are migrated from commodity code to commodity before
activating the feature toggle.
3. Activation of “Commodity” for S/4HANA On Premise Customers
To finally activate the new solution, you can use the “Activate Commodity” button
within the assistant, Alternatively, directly run transaction SFW5 “Switch Framework:
Display Business Function Status”. Expand the “LIGHTWEIGHT_FUNCTIONS” node
and search for business function “LOG_CMM_PRC_BF_MIGRATION”. Activate this
business function from the context menu.
After this activation, you will see the columns for commodity and commodity description
in the commodity quantity facet of the central contract, and the columns for the
commodity code will be disappeared. On the condition amount object page for CPE
conditions, within the screen section “Commodity Details”, the “commodity code” field
will be replaced by “commodity”. From now on, with the database table for commodity
quantity (EKPO_WEIGHTS), the column for commodity codes will not be updated
anymore.
Other Terms
central contract, central procurement, commodities, commodity management, commodity
quantity, commodity weight, CLS4SIC_LOG_CMM_PRC_CMMDTY_HAR,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 221
5.27 S4TWL - Simplified Commodity Pricing Engine Data Model
Application Components:CA-GTF-CPE
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
3207069
Migration Process for Optimized CPE
Database Model
Business Impact
3203753
S4TWL - Simplified Commodity Pricing
Engine Database Model
Symptom
You plan a system conversion from SAP ERP to SAP S/4HANA, on-premise edition or
an upgrade from a lower to a higher SAP S/4HANA release. The following SAP
S/4HANA Simplification Item is applicable in this case.
Solution
Historical Background:
The development of the existing CPE architecture started 15 years ago, pointing to
relational databases. The CPE database architecture was designed in a way that CPE
object artefacts have been stored in application tables only in case that other data sources
(customizing) where unavailable. Therefore, a huge amount of data were accessed on the
fly during the pricing process.
This approach required several tables with different keys for the same CPE object type
(formula, terms, conversions etc.), which were accessed each time an object were
processed, even when the object wasn’t changed by the user.
For accessing the objects, “internal buffers” were used. Each CPE object had several,
different buffers.
This apporach would greatly reduce the effort when developing future Fiori applications
such as for Central Purchase Contract, Sourcing Projects & Supplier Quotations, etc
based on RAP or BOPF.
Also, a mass data processing and the handling with documents with a high-complex
pricing hierarchy would have a negative impact on the performance.
Change Reason:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 222
The new database architecture can be used in a simple way for BOPF- and RAP-based
developments and improves the CPE pricing performance.
In addition, the new architecture solves the problem that customizing entities, which are
not stored in application tables, can be changed during the lifetime of a document.
Summary of Changes:
Simplified data model: Each CPE object (formula, terms and so on) will have just one
table. No changes in functional level and minimal changes to consuming SAP
components. Therefore new buffers should be included as well, pointing to the
new tables.
Changes in the key: New key DOCITEMCOND_GUID was introduced. All tables
will share this GUID as well as additional fields required by the key.
Every update on the old buffer will be reflected simultaneously on the new buffer and
will be recorded in the new DB.
Silent Data Migration (SDM) CL_SDM_CPED_MIGRATE_COMPLETE from the
old to the new DB ensures that all continues to work properly. After the new
installation, the system will automatically perform the migration report (SDM), so
that both databases will be updated with the same records for a certain period of
time.
New data model is activated by two business functions:
LOG_CMM_PRC_CPE_SMPLFCTN LOG_CMM_PRC_CPE_STOP_OLD.
Before customers can use the new tables in transactions, both business function
must have been activated.
Comparison report CMM_SCPE_COMPARISON_REPORT: With this report you
check the results of the data migration from the old to the new CPE database
tables. For more information, see the report documentation.
List of the tables that are involved
Original DB Table
Corresponding Optimized DB Table
CPED_FORMDOC
CPE_FORMULA
CPED_FORMINPUT
CPE_FORMULA
CPED_FORMCONVIN
CPE_FORMCONV
CPED_FORMCONVOUT
CPE_FORMCONV
CPED_FORMROUNDIN
CPE_FORMROUNDING
CPED_TERMOUT
CPE_TERM
CPED_TERMGRPOUT
CPE_TERM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 223
CPED_TERMINPUT
CPE_TERM
CPED_PERIODDTIN
CPE_TERM
CPED_PERIODDTOUT
CPE_TERM
CPED_PRIFIXDEF
CEP_TERM
CPED_TIER
CPE_TERM
CPED_TERMCONVIN
CPE_TERMCONV
CPED_TERMCONVOUT
CPE_TERMCONV
CPED_TERMROUNDIN
CPE_TERMROUNDING
CPED_EXCHRATE
CPE_EXCHANGERATE
CPED_QUOTATION
CPE_QUOTATION
Total of original CPE tables: 18
Total of optimized CPE tables: 8
Business Process related information
Since it expected that old and new data model are semantically equivalent, no impact on
business processes is expected.
Required and Recommended Action(s)
SAP delivers a “Silent Database Migration”, which will migrate all standard fields from
the old data model to the new data model. Customers can use both data models in parallel
for a certain time of period to check the consistency with a provided report. Two business
functions are provided to finally switch to the new data model.
While standard fields are migrated without any manual work, please note that for custom
fields and custom coding manual preparational steps might be necessary.
This could mean, for example, that custom fields need to be added again to the new
database table so that they can be filled during the migration by the SDM report.
For detailed description of the migration process, please refer to note 3207069
Other Terms
CPE, Commodity Pricing, Commodity
Management, CL_SDM_CPED_MIGRATE_COMPLETE, LOG_CMM_PRC_CPE_SM
PLFCTN LOG_CMM_PRC_CPE_STOP_OLD
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 224
5.28 S4TWL - Data Model Change in the Commodity Condition Types
Mapping
Application Components:CA-GTF-CPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3203820
S4TWL - Data Model Change in the
Commodity Condition Types Mapping
Symptom
You are using an SAP S/4HANA On Premise system, Commodity Management solution.
When using Commodity pricing Engine in the area of central procurement(Central
Purchase Contract and Sourcing Projects) the customizing activity "Map Purchase
Condition types to commodities" has been maintained.
The custom code check shows those customer objects that are affected by simplifications.
SAP objects used by the customer objects have been changed in a way that the would
give inconsistent results.
Reason and Prerequisites
There is a data model change in the Commodity Condition Types Mapping. An
Additional Key is added to the data base table CMM_CMDTY_CND. This additional
key enables the mapping to be maintained for Sales Conditions. Previously the table was
restricted to store only Purchase Conditions.
Solution
Where ever the table CMM_CMDTY_CND is used in Customer Code to fetch data, the
new additional key field must be included in the the code so as to maintian the
consistency in the data fetch.
If CDS View I_CommodityConditionMapping is used then this should be replaced
with the CDS View I_PurCommodityConditionMapping for Purchase and
I_SlsCommodityConditionMapping for Sales.
Other Terms
Commodity, Condition Types, Mapping
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 225
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 226
6. Corporate Close
6.1 S4TWL - Usage of long Material Number in EC-CS
Application Components:EC-CS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2471287
S4TWL - Usage of long Material
Number in EC-CS
Symptom
You are preparing a system conversion to SAP S/4HANA. Pre-transition checks for the
application EC-CS SAP Consolidation must be carried out before the conversion.
This SAP Note describes simplification item SI01: EC_CS_MATNR. See also SAP note
2209784 for the old pre-check framework.
Reason and Prerequisites
This SAP Note is relevant for you when your start release for the system conversion is an
ERP release.
It is not relevant if your start release is SAP S/4HANA.
Solution
Description
In SAP S/4HANA, the material number was extended to a maximum length of 40
characters. As a result, the material number is longer than the maximum length defined
for characteristics in the EC-CS data model.
Business Process Related Information
If you have included a field of type MATNR (material number) as a customer-defined
subassignment in the EC-CS data model, the EC-CS data model must be adjusted before
the upgrade.
Required and Recommended Action
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 227
If the check detects that such a field is used in the EC-CS data model as a customer-
defined subassignment, contact SAP Support by creating a customer indicident on SAP
Service Marketplace to application component EC-CS.
Rationale: The EC-CS data model in your system must be changed in this case. This
change of the data model implies that the EC-CS Consolidation transaction data must be
converted and information may also be lost during this process, because fields of type
MATNR (material number) must be removed from the data model.
Other Terms
S4TC, CLS4SIC_EC_CS, XS4SIC_EC_CS
6.2 S4TWL - Consolidation (EC-CS) and preparations for consolidation
Application Components:EC-CS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2999249
S4TWL - Consolidation and Preparation
for Consolidation
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Consolidation (EC-CS) and preparations for consolidation are part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, Consolidation (EC-CS) and preparations for consolidation can be found under
the ID 434.
This means that you need to migrate from Consolidation (EC-CS) and preparations for
consolidation to the designated alternative functionality "SAP S/4HANA Finance for
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 228
Group Reporting" before expiry of the compatibility pack license. This note shall provide
further information on what to do to move to the alternative functionality.
Business Process related information
For a description of the functional scope of EC-CS in the context of SAP S/4HANA refer
to SAP note 2371973 and to the SAP S/4HANA Feature Scope Description in sections
SAP S/4HANA Compatibility Packs > Consolidation (EC-CS) and Preparations for
Consolidation.
For information about the alternative solution SAP S/4HANA Finance for Group
Reporting refer to the SAP Help Portal and SAP note 2659672 - FAQ About SAP
S/4HANA Finance for Group Reporting (On Premise).
Required and Recommended Action(s)
Make yourself familiar with SAP S/4HANA for Group Reporting and define your
strategy when to switch to the new solution.
For information how to transition from EC-CS to SAP S/4HANA for Group Reporting
refer to SAP note 2833748.
Most important aspect to consider are as follows:
In SAP S/4HANA 1809, coexistence of EC-CS and SAP S/4HANA for Group
Reporting in the same SAP S/4HANA instance is not supported. You must set up
a separate (new) SAP S/4HANA instance for usage of Group Reporting.
As of SAP S/4HANA 1909, parallel usage of EC-CS and SAP S/4HANA for Group
Reporting is possible ("hybrid system state"). This allows you to test usage of
Group Reporting in parallel to the productive use of EC-CS.
If you are on SAP S/4HANA 1909 or later and wish to run your system in the hybrid
state to prepare the transition to Group Reporting, you need to contact SAP
Support because the transition from EC-CS into hybrid system state is executed in
a multiple step procedure of which some steps are executed by SAP Support.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Consolidation, ID 434
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 229
6.3 S4TWL - Consolidation (EC-CS) and preparations for consolidation
Application Components:EC-CS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2999249
S4TWL - Consolidation and Preparation
for Consolidation
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Consolidation (EC-CS) and preparations for consolidation are part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, Consolidation (EC-CS) and preparations for consolidation can be found under
the ID 434.
This means that you need to migrate from Consolidation (EC-CS) and preparations for
consolidation to the designated alternative functionality "SAP S/4HANA Finance for
Group Reporting" before expiry of the compatibility pack license. This note shall provide
further information on what to do to move to the alternative functionality.
Business Process related information
For a description of the functional scope of EC-CS in the context of SAP S/4HANA refer
to SAP note 2371973 and to the SAP S/4HANA Feature Scope Description in sections
SAP S/4HANA Compatibility Packs > Consolidation (EC-CS) and Preparations for
Consolidation.
For information about the alternative solution SAP S/4HANA Finance for Group
Reporting refer to the SAP Help Portal and SAP note 2659672 - FAQ About SAP
S/4HANA Finance for Group Reporting (On Premise).
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 230
Make yourself familiar with SAP S/4HANA for Group Reporting and define your
strategy when to switch to the new solution.
For information how to transition from EC-CS to SAP S/4HANA for Group Reporting
refer to SAP note 2833748.
Most important aspect to consider are as follows:
In SAP S/4HANA 1809, coexistence of EC-CS and SAP S/4HANA for Group
Reporting in the same SAP S/4HANA instance is not supported. You must set up
a separate (new) SAP S/4HANA instance for usage of Group Reporting.
As of SAP S/4HANA 1909, parallel usage of EC-CS and SAP S/4HANA for Group
Reporting is possible ("hybrid system state"). This allows you to test usage of
Group Reporting in parallel to the productive use of EC-CS.
If you are on SAP S/4HANA 1909 or later and wish to run your system in the hybrid
state to prepare the transition to Group Reporting, you need to contact SAP
Support because the transition from EC-CS into hybrid system state is executed in
a multiple step procedure of which some steps are executed by SAP Support.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Consolidation, ID 434
6.4 S4TWL – Real-Time Consolidation (RTC)
Application Components:FIN-RTC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3205500
S4TWL - Real-Time Consolidation
(RTC) in SAP S/4HANA
Symptom
You are using Real-Time Consolidation (RTC) in SAP S/4HANA. The following
SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 231
SAP regards Real-Time Consolidation (RTC) in SAP S/4HANA no longer as strategic
solution. Therefore, SAP has decided to phase out RTC in SAP S/4HANA. If you already
use RTC in SAP S/4HANA releases up to release 2021, RTC is in deprecation state as of
release SAP S/4HANA 2022. This means after an upgrade to SAP S/4HANA 2022 you
can still continue using RTC with full support and maintenance. However, SAP does not
plan to provide new features for RTC. Designated alternative for RTC is SAP S/4HANA
Finance for Group Reporting.
Note that the features of Real-Time Consolidation are only available for customers who
have licensed these features before October 1st, 2022, including maintenance for these
features.
Business Process related information
For a description of the functional scope of RTC in the context of SAP S/4HANA refer to
the SAP S/4HANA Feature Scope Description "Corporate Close - Data Preparation".
For information about the alternative solution "SAP S/4HANA Finance for Group
Reporting" refer to the SAP Help Portal and SAP note 2659672 - FAQ About SAP
S/4HANA Finance for Group Reporting (On Premise).
Required and Recommended Action(s)
Make yourself familiar with SAP S/4HANA Finance for Group Reporting (S/4GR) and
define your strategy when to switch to the new solution.
For technical setup of S/4GR, see the IMG (Implementation Guide) for this product. In
particular, the following activities are required:
Either "Install SAP Best Practice Content" or execute the IMG activity "Initialize
Settings"
Create master data for accounts, account hierarchies, organizational units and
business configuration in S/4GR, in analogy with the existing entities which you
have been using in RTC in SAP S/4HANA
Create opening balance in S/4GR based on legacy transaction data from RTC in SAP
S/4HANA
For further information, please contact your SAP Account Executive.
Other Terms
SAP S/4HANA, RTC, Real-Time Consolidation, deprecation state
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 232
6.5 S4TWL – Business Consolidation (SEM-BCS)
Application Components:FIN-SEM-BCS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3205515
S4TWL - Business Consolidation (SEM-
BCS) in SAP S/4HANA
Symptom
You are using Business Consolidation (SEM-BCS) in SAP S/4HANA based on
Embedded BW. The following SAP S/4HANA Simplification Item is applicable in this
case.
Solution
Description
SAP regards Business Consolidation (SEM-BCS) in SAP S/4HANA no longer as
strategic solution. Therefore, SAP has decided to phase out SEM-BCS from SAP
S/4HANA. If you already use SEM-BCS in SAP S/4HANA releases up to release 2021,
SEM-BCS is in deprecation state as of release SAP S/4HANA 2022. This means after an
upgrade to SAP S/4HANA 2022 you can still continue using SEM-BCS with full support
and maintenance. However, SAP does not plan to provide new features for SEM-BCS in
SAP S/4HANA. Designated alternative for SEM-BCS in SAP S/4HANA is "SAP
S/4HANA Finance for Group Reporting".
Note that the features of SEM-BCS in SAP S/4HANA are only available for customers
who have licensed these features before October 1st, 2022, including maintenance for
these features.
If you want to deploy a consolidation solution on top of a data warehouse, outside of SAP
S/4HANA, you can use "SAP BW/4HANA, Business Consolidation Add-On"
(BCS/4HANA). The relevant release information on BCS/4HANA is provided in SAP
Note 1330000 and in the rollout materials quoted therein.
Business Process related information
For a description of the functional scope of SEM-BCS in the context of SAP S/4HANA
refer to SAP Note 2360258 and to the SAP S/4HANA Feature Scope
Description "Business Consolidation".
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 233
For information about the alternative solution "SAP S/4HANA Finance for Group
Reporting" refer to the SAP Help Portal and SAP note 2659672 - FAQ About SAP
S/4HANA Finance for Group Reporting (On Premise).
Required and Recommended Action(s)
Make yourself familiar with "SAP S/4HANA Finance for Group Reporting" (S/4GR) and
define your strategy when to switch to the new solution.
For technical setup of S/4GR, see the IMG (Implementation Guide) for this product. In
particular, the following activities are required:
Either "Install SAP Best Practice Content" or execute the IMG activity "Initialize
Settings"
Create master data for accounts, account hierarchies, organizational units and
business configuration in S/4GR, in analogy with the existing entities which you
have been using in SEM-BCS in SAP S/4HANA
Create opening balance in S/4GR based on legacy transaction data from SEM-BCS in
SAP S/4HANA
For further information, please contact your SAP Account Executive.
Other Terms
SAP S/4HANA, SEM-BCS, business consolidation, deprecation state
6.6 S4TWL – Configuration Changes in Group Reporting
Application Components:FIN-CS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3326805
S4TWL - Configuration in Groupe
Reporting using Selections and FS item
Role attribute
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 234
You are preparing a system upgrade to SAP S/4HANA 2023 (S4CORE 108). The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
In the Global System Settings (transaction code CXB3), one of the following options for
the Settings for Configuration Control are not marked:
- Reclassification: Sel Object in Trigger
- Breakdon Category: Sel.Obj in Max.Sel
- Currency Translation: Selection Object
- Use Item Role Attribute
Solution
Business Value
The configuration of some functions in Group Reporting (breakdown categories,
currency translation methods, reclassification methods, automatic postings on Selected
FS items...) can be flexibly defined using
Selections (https://help.sap.com/docs/SAP_S4HANA_ON-
PREMISE/4ebf1502064b406c964b0911adfb3f01/b3d1255de2244af486cb116919c1c5f1.
html?locale=en-US) and using FS item Role attribute
(https://help.sap.com/docs/SAP_S4HANA_ON-
PREMISE/4ebf1502064b406c964b0911adfb3f01/bb5a08412bf145e9a950bee1bf4c6c6b.
html?locale=en-US).
The options to use these feature are defined in the Global System Settings (transaction
code CXB3). They are by default selected. Only in some circumstances (migration from
EC-CS, inital release 103) some of these options are possibly not selected.
Description
As of SAP S/4HANA 2023 (S4CORE 108), these options in the Global System Settings
are always selected and cannot be edited.
Business Process related Information
If some of these options are not selected in your system, you must adjust your
configuration before the upgrade to use the Selections and the FS item Role.
Required and Recommended Actions(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 235
Check in the Global System Settings (transaction code CXB3) which of the following
options are not selected:
- Reclassification: Sel Object in Trigger
- Breakdon Category: Sel.Obj in Max.Sel
- Currency Translation: Selection Object
- Use Item Role Attribute
If you don't use the options Reclassification: Selection Object in Trigger, Breakdown Category:
Selection Object in Maximum Selection, or Currency Translation: Selection Object
Follow this procedure to replace sets with selections in the configuration:
In the configuration activities Define Reclassification Methods, Define Breakdown
Categories, and Define Currency Translation Methods, list all the sets you use and
their content.
In the Check Global System Settings configuration activity, select the options
Reclassification: Selection Object in Trigger, Breakdown Category: Selection
Object in Maximum Selection, and Currency Translation: Selection Object.
In the Define Selections app, create a selection to replace the sets.
In the configuration activities Define Reclassification Methods, Define Breakdown
Categories, and Define Currency Translation Methods, replace the sets by the
Selections.
Check and test the configuration.
If you don't use the Use Item Role Attribute option, you can keep you configuration
unchanged, or you can adjust your configuration to use the FS item Role attribute to
select the FS item:
In the Check Global System Settings configuration activity, select the Use Item Role
Attribute option.
In the Define Currency Translation Methods and Define Reclassification Methods
configuration activities, check and adjust the configuration of selected FS items so
that the role assigned corresponds to the correct FS item.
Check and test the configuration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 236
Other Terms
Sets, Selections, FS item Role attribute, Global System Settings, CXB3
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 237
7. Customer Service
7.1 S4TWL - Customer Service
Application Components:CS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2962632
S4TWL - Customer Service
Symptom
You are currently using Customer Service (CS) as compatibility scope in SAP S/4HANA
on-premise edition. More information on compatibility scope in S/4HANA can be found
in the following note 2269324. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
Description
Customer Service (CS) provides Service Management functionality for planning,
executing and billing service orders. CS is used for Field Service, In-House Repair as
well as Service Projects. It works in conjunction with Plant Maintenance (PM)
functionality and provides integration to Resource Related Billing as well as Service
Contracts.
Customer Service (CS) will be replaced by S/4HANA Service. S/4HANA Service will
be the new state-of-the-art Service Management backend as part of SAP S/4HANA.
Required and Recommended Action(s)
Customer Service (CS) in S/4HANA is intended as a bridge or interim solution, which
allows you a stepwise system conversion from SAP ERP to SAP S/4HANA on-premise
edition and SAP S/4HANA Service.
Custom Code related information
S/4HANA Service is an all-new and own Service Management solution. It will re-use
selected functionalities of ERP CS and partly PM but will mainly come with a new
solution scope, including new processes and capabilities . Any enhancements or
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 238
modifications of CS will not work once S/4HANA Service is used
As a rough guideline, it is currently planned to re-use master data focused objects (e.g.
Equipment, Functional location) mainly from ERP, while the more transactional data
(e.g. service orders) for the operational service execution in S/4HANA service will be
based on new objects. For customers with a high need of CS service order elements
comparable to Plant Maintenance orders, it is planned to reflect these requirements in the
solution as much as possible as well. More detail will be available around September
2020 as the new solution continues to take shape.
7.2 S4TWL - PH_Sample iView
Application Components:LO-PDM-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271201
S4TWL - PH_Sample iView
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 avialble.
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)
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 239
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 usign the SAP Portal and have configured this iView.
Related SAP Notes
Custom Code related information
As this is an iView, customers were not able to
develop custom code
7.3 S4TWL - Customer Interaction Center (CIC)
Application Components:CS-CI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267412
S4TWL - Customer Interaction Center
(CIC)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Transaction CIC0 provides a basic Call Center help desk application which is technically
outdated and not available within SAP S/4HANA.
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 SAP S/4HANA, SAP CRM or SAP
C/4HANA.
Transaction not available in SAP S/4HANA on-premise edition 1511
CIC0
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 240
Business processes that require a help desk / call center integration should be integrated
into the interaction center / help desk applications offered by SAP S/4HANA, SAP CRM
or SAP C/4HANA.
Related SAP Notes
Custom Code related information
See SAP Note 2229726
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 241
8. Financials – General
8.1 S4TWL - DMEE
Application Components:CA-GTF-CSC-DME
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3370503
S4TWL - DMEE
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using a DMEE transaction. The
following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Business Value
SAP has decided to replace legacy solution DMEE (Data Medium Exchange Engine)
with the DMEEX (Data Medium Exchange Engine eXtended).
DMEEX delivers following new capabilities for the end-user:
Faster processing of output files
https://blogs.sap.com/2021/02/09/performance-
acceleration-in-dmeex/
Format Trees delivered in hierarchy
(standard - country - customer
specific)
https://blogs.sap.com/2018/09/21/mass-synchronization-in-
dmeex/
Synchronization of Format Trees to
be up to date with standard
https://blogs.sap.com/2018/09/21/mass-synchronization-in-
dmeex/
Calculations and variables
https://blogs.sap.com/2018/12/11/calculations-in-dmeex/
Improved version management
(automatic backups)
New syntax checks to ensure
consistency of the format tree
XSD validation
https://blogs.sap.com/2022/07/20/xsd-validation-for-
dmeex/
Removing empty elements from XML
file as native functionality
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 242
Apart from these, there are many minor improvements like preferences in conditions,
faster UI, improved test tool and more.
DMEEX is regularly updated with new features. On the contrary, DMEE is in a
maintenance state and it's unlikely that it will receive any updates in the future.
Description
To learn about business features, please refer to Business Value section above.
Business Process related information
DMEE consists of two main logical parts - configuration and runtime.
Configuration is when you define a new or modify an existing format tree to comply
with the requirements of your bank, financial institution or public administration
institutions.
From SAP S/4HANA 2025, configuration of format trees in the outgoing direction (file
generation) will no longer be possible in DMEE.
Configuration will be available only via DMEEX. Once a DMEE tree is opened in
DMEEX transaction it will be automatically migrated to the DMEEX.
Runtime is when the format tree is interpreted and filled with data to generate the output
file.
For all existing format trees in DMEE the runtime phase will remain intact in SAP
S/4HANA 2025. There will be no "Day one impact".
All existing custom code integrations will remain functional after SAP S/4HANA 2025
regardless of whether DMEE or DMEEX is used. However, when a change is required
for a DMEE tree, such tree will be migrated automatically to the DMEEX.
Required and Recommended Action(s)
To migrate a format tree from DMEE to DMEEX, open your DMEE tree in the DMEEX
transaction and confirm the migration pop-up. Testing the format tree after migration is
strongly recommended.
There is no need to migrate all your existing trees at once. More realistic option is to
migrate when a certain change to an existing format tree is required. Usually, testing of
such changed format tree would happen anyway.
After activating the migrated format tree in the DMEEX, usually some syntax errors will
show up in the error log. These are caused by more rigorous syntax checks that control
the consistency of your format tree. Fixing these syntax checks shall, in typical situations,
take only few minutes.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 243
There are some known inconsistencies between DMEE and DMEEX. Such cases are
documented and regularly updated in SAP Note
3370488: https://me.sap.com/notes/3370488
During 2024, SAP plans to deliver a migration log that will detect potential issues as per
SAP Note 3370488.
During 2024, SAP plans to deliver a migration report that will enable customers to easily
compare DMEE and DMEEX output files.
How to Determine Relevancy
You are using custom DMEE format trees to generate output files (payment formats,
statutory reports etc.).
Other Terms
SAP S/4HANA, System Conversion, Upgrade, deprecation, DMEE
8.2 S4TWL - DATA MODEL CHANGES IN FIN
Application Components:CO, FI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270333
S4TWL - Data Model Changes in FIN
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
The universal journal significantly changes the way transactional data is stored for
financial reporting. It offers huge benefits in terms of the ability to harmonize internal
and external reporting requirements by having both read from the same document store
where the account is the unifying element. You still create general journal entries in
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 244
General Ledger Accouting, acquire and retire assets in Asset Accounting, run allocation
and settelement in Controlling, capitalize research and development costs in Investment
Management, and so on, but in reporting, you read from one source, regardless of
whether you want to supply data to your consolidation system, report to tax authorities, or
make internal mangement decisions.
Totals records that store the data in the General Ledger, Controlling, Material Ledger,
Asset Accounting, Accounts Payable and Accounts Receivable by period have been
removed as have index tables that are designed to optimize certain selections. This
simplifies the data structure and makes accounting more flexible in the long term as
reporting is no longer limited by the number of fields in the totals records.
Description
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
identically-named DDIC
View)
Backup Table (for
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
FAGLBSAS
FAGLBSAS_DDL
FAGLBSAS_BCK
FAGLBSIS
FAGLBSIS
FAGLBSIS_DDL
FAGLBSIS_BCK
GLT0
GLT0
GLT0_DDL
GLT0_BCK
KNC1
KNC1
KNC1_DDL
KNC1_BCK
KNC3
KNC3
KNC3_DDL
KNC3_BCK
LFC1
LFC1
LFC1_DDL
LFC1_BCK
LFC3
LFC3
LFC3_DDL
LFC3_BCK
COSP
COSP
V_COSP_DDL
COSP_BAK
COSS
COSS
V_COSS_DDL
COSS_BAK
FAGLFLEXT
FAGLFLEXT
V_FAGLFLEXT_DDL
FAGLFLEXT_BCK
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 245
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.
Original
Table
Compatibility View (view in
DDIC for redirect)
DDL Source (for the
identically-named DDIC
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
FAAV_ANLP
FAA_ANLP
FAAV_ANLP_ORI
BSIM
V_BSIM
BSIM_DDL
V_BSIM_ORI
COEP
V_COEP
V_COEP
V_COEP_ORI
FAGLFLEXA
FGLV_FAGLFLEXA
FGL_FAGLFLEXA
V_FAGLFLEXA_ORI
T012K
V_T012K_BAM
V_T012K_BAM_DDL
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
FGL_PSGLFLEXA
-
PSGLFLEXT
FGLV_PSGLFLEXT
FGL_PSGLFLEXT
-
JVGLFLEXA
FGLV_JVGLFLEXA
FGL_JVGLFLEXA
V_ JVGLFLEXA _ORI
JVGLFLEXT
FGLV_JVGLFLEXT
FGL_JVGLFLEXT
V_ JVGLFLEXT _ORI
ZZ<CUST>A *
ZFGLV_GLSI_C<number>
ZFGL_GLSI_C<number>
-
ZZ<CUST>T *
ZFGLV_GLTT_C<number>
ZFGL_GLTT_C<number>
-
Any access to the following tables (Material Ledger) is supported up to release S/4
HANA OP 1809:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 246
Read access via redirection to compatibility views
Write access (INSERT, UPDATE, DELETE, MODIFY) was adapted in SAP
standard, or has to be adapted in custom code – refer to SAP note 1976487.
From release S/4 HANA OP 1909 and subsequent these tables and views are
obsolete. No read or write access is allowed anymore.
Original
Table
Compatibility View
(view in DDIC for
redirect)
DDL Source (for the
identically-named DDIC
view)
View to read the content of
the database table (w/o
redirect to compatibility view)
CKMI1
V_CKMI1
V_CKMI1_DDL
V_CKMI1_ORI
MLCD
V_MLCD
V_MLCD_DDL
V_MLCD_ORI
MLCR
V_MLCR
V_MLCR_DDL
V_MLCR_ORI
MLHD
V_MLHD
V_MLHD_DDL
V_MLHD_ORI
MLIT
V_MLIT
V_MLIT_DDL
V_MLIT_ORI
MLPP
V_MLPP
V_MLPP_DDL
V_MLPP_ORI
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
Obsole
te
databa
se
table
used
As of
release
Replaced
by
Compatibility
View
DDL Source (for the
compatibility view)
BKPF_BSAD
BSAD
sFIN 1.0
Identically
-named
DDL view
BKPF_BSAD
BKPF_BSAD_DDL
BKPF_BSAD_AE
DAT
BSAD
sFIN 1.0
Identically
-named
DDL view
BKPF_BSAD_AE
DAT
BKPF_BSAD_AEDAT_D
DL
BKPF_BSAK
BSAK
sFIN 1.0
Identically
-named
DDL view
BKPF_BSAK
BKPF_BSAK_DDL
BKPF_BSAK_AE
DAT
BSAK
sFIN 1.0
Identically
-named
DDL view
BKPF_BSAK_AE
DAT
BKPF_BSAK_AED_DDL
BKPF_BSID
BSID
sFIN 1.0
Identically
-named
DDL view
BKPF_BSID
BKPF_BSID_DDL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 247
BKPF_BSID_AED
AT
BSID
sFIN 1.0
Identically
-named
DDL view
BKPF_BSID_AED
AT
BKPF_BSID_AEDAT_DD
L
BKPF_BSIK
BSIK
sFIN 1.0
Identically
-named
DDL view
BKPF_BSIK
BKPF_BSIK_DDL
BKPF_BSIK_AED
AT
BSIK
sFIN 1.0
Identically
-named
DDL view
BKPF_BSIK_AED
AT
BKPF_BSIK_AEDAT_DD
L
GLT0_AEDAT
GLT0
sFIN 1.0
Identically
-named
DDL view
GLT0_AEDAT
GLT0_AEDAT_DDL
KNC1_AEDAT
KNC1
sFIN 1.0
Identically
-named
DDL view
KNC1_AEDAT
KNC1_AEDAT_DDL
KNC3_AEDAT
KNC3
sFIN 1.0
Identically
-named
DDL view
KNC3_AEDAT
KNC3_AEDAT_DDL
LFC1_AEDAT
LFC1
sFIN 1.0
Identically
-named
DDL view
LFC1_AEDAT
LFC1_AEDAT_DDL
LFC3_AEDAT
LFC3
sFIN 1.0
Identically
-named
DDL view
LFC3_AEDAT
LFC3_AEDAT_DDL
TXW_J_WITH
BSAK
sFIN 1.0
Identically
-named
DDL view
TXW_J_WITH
TXW_J_WITH_DDL
V_COSP_A
COSP
sFIN 1.0
Code
V_COSS_A
COSS
sFIN 1.0
Code
VB_DEBI
BSID
sFIN 1.0
Identically
-named
DDL view
VB_DEBI
VB_DEBI_DDL
VF_BSID
BSID
sFIN 1.0
Identically
-named
DDL view
VF_BSID
VF_BSID_DDL
VFC_DEBI
KNC1
sFIN 1.0
Identically
-named
DDL view
VFC_DEBI
VFC_DEBI_DDL
VFC_KRED
LFC1
sFIN 1.0
Identically
-named
DDL view
VFC_KRED
VFC_KRED_DDL
ENT2006
GLT0
sFIN 1.0
Code
ENT2163
KNC1
sFIN 1.0
Code
ENT2164
LFC1
sFIN 1.0
Code
ENT2165
KNC3
sFIN 1.0
Code
ENT2166
LFC3
sFIN 1.0
Code
EPIC_V_BRS_BS
AS
BSAS
sFIN 1.0
Code
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 248
EPIC_V_BRS_BSI
S
BSIS
sFIN 1.0
Code
EPIC_V_BSID
BSID
sFIN 1.0
Code
EPIC_V_BSIK
BSIK
sFIN 1.0
Code
EPIC_V_CUSTO
MER
BSID
sFIN 1.0
Code
EPIC_V_VENDO
R
BSIK
sFIN 1.0
Code
FMKK_BKPF_BS
AK
BSAK
sFIN 1.0
Code
FMKK_BKPF_BSI
K
BSIK
sFIN 1.0
Code
/GRC/V_BANK_A
CCT
T012
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
V_GRC_BANK_A
CCT
V_GRC_BANK_ACCT_D
DL
ANEKPV
ANEP
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
FAAV_ANEKPV
FAA_ANEKPV
COPC_V_T012_S
KB1
T012K
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
V_COPC_T012_S
KB1
V_COPC_V_T012_SKB1
_DDL
COPC_V_T035D
T012K
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
V_COPC_T035D
V_COPC_V_T035D_DDL
COVP
COEP
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
V_COVP
V_COVP_DDL
FAP_V_CMP_HB
ACC
T012
SAP
Simple
Finance,
Compatibil
ity view
(redirect)
V_FAP_CMP_HB
ACC
V_FAP_V_CMP_HBACC
_DDL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 249
on-
premise
edition
1503
MLREADST
MLHD
SAP
Simple
Finance,
on-
premise
edition
1503
Obsolete
from
release
S/4
HANA
1909 and
subsequ
ent
Compatibil
ity view
(redirect)
V_MLREADST
V_MLREADST_DDL
MLREPORT
MLIT
SAP
Simple
Finance,
on-
premise
edition
1503
Obsolete
from
release
S/4
HANA
1909 and
subsequ
ent
Compatibil
ity view
(redirect)
V_MLREPORT
V_MLREPORT_DDL
MLXXV
MLHD
SAP
Simple
Finance,
on-
premise
edition
1503
Obsolete
from
release
S/4
HANA
1909 and
suseque
nt
Compatibil
ity view
(redirect)
V_MLXXV
V_MLXXV_DDL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 250
V_ANEPK
ANEP
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
FAAV_V_ANEPK
FAA_V_ANEPK
V_ANLAB
ANEP
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
FAAV_V_ANLAB
FAA_V_ANLAB
V_ANLSUM_1
ANLA
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
FAAV_V_ANLSU
M_1
FAA_V_ANLSUM_1
V_ANLSUM_2
ANEP
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
FAAV_V_ANLSU
M_2
FAA_V_ANLSUM_2
V_ANLSUM_5
ANLA
SAP
Simple
Finance,
on-
premise
edition
1503
Compatibil
ity view
(redirect)
FAAV_V_ANLSU
M_5
FAA_V_ANLSUM_5
Business Process Related Information
There are mandatory configuration steps in General Ledger, Asset Accounting, Account-
Based CO-PA, and Cash Management (if used). For detailed information, refer to IMG ->
Migration from SAP ERP to SAP Accounting powered by SAP HANA as well as to the
respective simplification items for the used financial applications. We also recommend
reading the guide attached to SAP note 2332030 - Conversion of accounting to SAP
S/4HANA.
You should also consider adapting your reporting strategy to use the new Fiori reports
that are designed specifically to handle the many fields in the universal journal, rather
than continuing to work with the classic reports that aggregate on the fly according to the
fields in the old totals fields.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 251
Required and Recommended Actions
Adapt access to new simplified finance data model in your customer-specific programs –
refer to SAP note 1976487.
8.3 S4TWL - REPLACED TRANSACTION CODES AND PROGRAMS IN
FIN
Application Components:FI, AC, FIN-FSCM, CO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2742613
Obsolete or replaced transaction codes
and programs in Finance applications of
S/4
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition.
With the installation of the SAP S/4HANA on-premise edition certain transaction codes
and programs in the application areas of Controlling, General Ledger, Asset Accounting,
Accounts Payable and Receivable, Treasury and Risk Management - compared to EhP7
for SAP ERP 6.0 - have been removed and partially replaced with newer transactions,
programs or WebDynpro applications.
Reason and Prerequisites
Task: Check if the customer uses any of the transactions or programs listed in the
attached list of transactions and programs.
Procedure: Use transaction ST03N to list transaction codes and programs used in the
system in the past.
Solution
SAP recommends you to read the scope information in SAP Note 2119188 for a general
overview on supported functions and compatibility information.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 252
Note that with S/4HANA the logic of SAP General Ledger (New GL) is used.
The Classic General Ledger application is automatically transformed into a basic
implementation of New General Ledger (not adding addidional ledgers, nor document
splitting functionality). Therefore transactions of classic General Ledger have to be
replaced by the relevant transactions from New General ledger. These transactions are
not explicitly mentioned in this note.
Transactions, programs and WebDynpro applications which are not supported are listed
in the attached PDF document.
Classic CO-OM planning transactions instead of SAP BPC optimized for SAP
S/4HANA
In case you cannnot transition to SAP BPC optimized for SAP S/4HANA in the short-
term, but have strong reasons to continue to use the classic CO-OM planning functions,
you may do so, but these transactions are not included in the SAP Easy Access Menu.
Please be aware that the classic planning functions don't update the new planning table
(ACDOCP), which is available from SAP S/4HANA 1610. This means that legacy
reports and follow-on processes will continue to work, but that Fiori apps based on the
new table will not display plan data entered with classic planning functions.
BW-Extractors and SAP BPC optimized for SAP S/4HANA
Customers that in the past used BW-extractors to extract and report FI-GL plan data will
as of now make use of the SAP BPC optimized for SAP S/4HANA functionality. This
new planning application serves to record plan data for FI and CO. In order to activate
the SAP BPC optmized for SAP S/4HANA functionality, check SAP Note 1972819. The
documentation can be found here: http://help.sap.com .
The classic GL planning functions can be reactivated for a transition period by following
the instructions in the SAP Notes 2253067 and 2474069.
Treasury and Risk Management
Obsolete Transactions and Programs in Treasury and Risk Management are described
and listed in the SAP Note 2726778.
Asset Accounting
The affected transactions, programs and WebDynpro applications and its replacements
are listed in the release notes for Asset Accounting and the following notes:
Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 253
2270387: S4TWL - Asset Accounting: Changes to Data Structure
2270388: S4TWL - Asset Accounting: Parallel Valuation and Journal Entry
2257555: S4TWL - Asset Accounting: Business Functions from FI-AA and FI-GL
Release Notes:
EN: ttp://help.sap.com/saphelp_sfin200/helpdata/en/ce/fbe15459e0713be10000000a441
76d/content.htm?frameset=/en/6f/bf8f546ac0c164e10000000a44176d/frameset.htm&curr
ent_toc=/en/55/4b6154b6718c4ce10000000a4450e5/plain.htm&node_id=12
DE: ttp://help.sap.com/saphelp_sfin200/helpdata/de/ce/fbe15459e0713be10000000a441
76d/content.htm?frameset=/de/6f/bf8f546ac0c164e10000000a44176d/frameset.htm&curr
ent_toc=/de/55/4b6154b6718c4ce10000000a4450e5/plain.htm&node_id=12
Other Terms
Out of scope, disabled transactions
8.4 S4TWL - SAP Travel Management in SAP S/4HANA Suite
Application Components:FI-TV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2719018
S4TWL - SAP Travel Management in
SAP S/4HANA Suite
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition.
Reason and Prerequisites
This is an information note, which provides the roadmap, the scope of the shipment and
the possible differences between Business-Suite and S/4HANA Suite.
Solution
This note contains in attachment the roadmap in S/4HANA for the new product SAP
Travel Management for SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 254
The scope will be comparable to the one in S/4HANA compatibility scope pack
corresponding to ECC 6.0 Enhancement package 8.
It is not necessary to change from ERP to the compatibility mode of SAP S/4HANA.
Customers can then switch directly to the SAP S/4HANA system (release 2022).
The migration process is comparable to a new release installation. There is a migration
guide to assist customers with the migration.
Additional information: There will be no major change as the architecture stays the same
(database / SAP GUI applications, Web Dynpro applications, Workflows, Transfer to
Accounting/Payroll etc.).
The new product will be compliant with S/4HANA standards
Adoption of the GDPR framework for archiving, data deletion, RAL*, etc.
Accessibility
Performance (Fiori apps old/new)
Display harmonization
The major difference is the availability of a set of new FIORI applications based on Fiori
Element Framework with CDS views and RAP Technology. The goal of this
development is to ensure the maintenance security and adherence to the SAP guideline.
The new Fiori Applications are based on the same customizing than the previous Fiori
versions (V1 & V2 and WebDynpro), there is no new customizing to configure. The
approval applications (My-Inbox) will be based on a new Odata Service for the display of
the information, but there is no major change and you can reuse your own configuration
in the same way. In S/4HANA for accessibility reason only the PDF forms are allowed,
you will not be able to use HTML Form in standard.
Two new roles are available in this context the "Business Traveler" role and the "Traveler
Assistant" role. Corresponding to the roles, two new "Business Catalogs" are available in
standard.
Here the list of new Fiori applications:
For "Business Traveler" role
My Travel Requests for Business Traveler (Fiori ID F6015)
My Travel Plans for Business Traveler (Fiori ID F6768)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 255
My Travel and Expenses for Business Traveler (Fiori ID F6190)
My Credit Card Transactions (Fiori ID F6506)
For "Traveler Assistant" role
Travel Requests for Travel Assistant (Fiori ID F0409B)
Travel Plans for Travel Assistant (Fiori ID F6771)
Travel and Expenses for Travel Assistant (Fiori ID F0584B)
For the Public Sector Germany, two new processes : Relocation and separation allowance
will be available for customers. Both processes will be available for Domestic or
International trips.
German Regulation of International Separation Allowances (ATGV)
German Law on Inland Relocation Costs (BUKG)
German Regulation of Foreign Relocation Costs (AUV)
Due to strategy the initial shippement will not include all existing features but existing
gaps will be filled in the next FSPs. For an exhaustive list of limitations please check the
following information underneath:
Country versions for CEE (Central and Eastern Europe).
Public Sector-specific features.
Table PTK99: The use of table PTK99 is not supported. Instead we provide an
extensibility concept (please see SAP KBA 3296253 and 3260453). If you want
to manage old data in the cluster corresponding to the structure PTK99, you will
need to manage the mapping between the old structure (PTK99) and new
structures yourself via extensibility concept.
Import of participants from an excel list is not supported: Not for initial shipment,
planned with FPS1
Missing Cost Assignment buttons "Create from destination" at mileages and receipt
level: Not for initial shipment, planned with FPS1
Itemization: only the deduction of Private expense is available in the initial shipment,
the rest (Division and Spit receipt) is not yet available : Not for initial shipment,
planned for FPS1
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 256
Merge of receipts are not supported: Not for initial shipment, planned for futur
releases
Concurrent assignment: Not for initial shipment planned for futur releases (HCM
dependency), this feature is provided centrally by HCM.
Copy of Mileage and copy of Receipt inside the same expense report: Not for initial
shipment planned with FPS1
List of Transactions Deprecated in S/4HANA:
Many old features are not relevant anymore, all transactions around travel planning or in
relation with old technology will be marked as Deprecated in a first step.
Here the definition of Deprecated and Obsolete statuses:
Deprecated
(computing) (of a software feature) to be considered outdated and best avoided
and planned to be removed in near future release even though you can still use
it now, usually because it has been replaced with a newer feature.
Therefore, it means the UI / functionality still works and is officially supported but is
not recommended to be used anymore. No improvements / new features can be
expected. In the foreseeable future it is planned to make it obsolete (see below) in
favor of the designated successor UI / functionality.
Obsolete
(computing) no longer valid, no longer works as expected, must not be used.
Therefore, it means The UI / functionality must not be used anymore. It is either
significantly restricted in functionality (e.g. view only mode) or no longer supported
at all. Customers cannot expect that it works correctly. It is recommended that
execution is blocked. The UI could be finally removed from the system at a later
point in time. The designated successor UI / functionality must be used instead at
this phase.
Here the list of transactions marked deprecated for the release S/4HANA 2022
Transaction
Name
Successor
PR01
Maintain (Old) Trip Data
PR05
PR05_ESS
Travel Expense Manager via
ESS
PR20
Create Trip
PR05
PRAA
Automatic Vendor
Maintenance
BP
PRCC_CDF3
Obsolete; Use
PRCC_CDF3_V2
PRCC_CDF3_V2
PRCT
Current Settings
SPRO
PREX
Create expense report
TRIP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 257
PRPL
Create Travel Plan
TRIP
PRRQ
Create Travel Request
TRIP
PRTAXFIN
Tax Report Finland
PRCRKATRE
PRTC
Display Imported Documents
PRCCD
PRTS
Overview of Trips
PRTE
PRWW
Expense Reports (Offline)
PTRV_OFFLINE
Activate Offline Travel
Manager
PTRV_RTREE
Display Trav. Management
Report Tree
SE43
TRIP_EWT
Travel Manager
PR05_ESS
ITS Service
PRWW
ITS Service
TP10
Travel Plan Synchronization
(AIR)
TP12
Travel Plan Synchronization
(Manual)
TP14
Travel Plan Synchronization
(Queue)
TPLOG
Short cut for TPLOG
TP_LOG
VPNR
View of the active PNR in 1A
AMADEUS
Amadeus Direct
APOLLO
Apollo Bypass
BYPASS
Bypass for All Reservation
Systems
FITP_RESPO
Contact Partner
Responsibilities
FITP_SETTINGS
Settings for Travel Planning
FITP_SETTINGS_TREE
Tree Maintenance Current
Settings
GALILEO
Galileo Bypass
GALILEO_SYNCH
Synchronization of Galileo
PNRs
GALILEO_VPNR
Galileo Bypass VPNR
HUGO
Settings for Travel Planning
TP01
Planning Manager
TP02
Travel Planning (End User)
TP02_EWT
Travel Planning (End User)
TP03
Planning Manager (Expert)
TP04_EWT
Travel Request (End User)
TP20
Create Travel Plan
TP30
Display Travel Planning report
tree
TP40
Maintain Routings
TP41
Initial Screen via IMG
TP50
Global flight availability
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 258
TP60
Synchronization of Hotel
Catalog
TPPF_D
Display Entry V_TA23PF by
Key
TPPR
Travel Profile Display
TPQ0
Quicktrip Manager
SABRE
SABRE Bypass
SABRE_PNR
Display a Sabre PNR
SABRE_VPNR
SABRE Bypass VPNR
TPLP
Create/Change LPs for
SABRE
PR_WEB_1000
Trip Data
PR_WEB_1200
General Trip Data
PR_WEB_1300
Trip Receipts
PR_WEB_1400
Trip Deductions
PR_WEB_1500
Trip Advances
PR_WEB_1600
Trip Destinations
PR_WEB_1700
Cost Distribution: Trip
PR_WEB_1710
Cost Distribution for Receipts
PR_WEB_1720
Cost Apportionment
Destinations
PR_WEB_1730
Cost Distribution:
Miles/Kilometers
PR_WEB_1800
Legs of Trip
PR_WEB_1900
Check Trip
Fiori Application
Successor
F0409 Travel Request V1
Obsolete
F0409B My Travel Requests (S/4
HANA)
F0409A Travel Request V2
Deprecated
F0409B My Travel Requests (S/4
HANA)
F0584 Travel &Exp V1
Obsolete
F0584B My Travel & Expenses (S/4
HANA)
F0584A Travel & Exp V2
Deprecated
F0584B My Travel & Expenses (S/4
HANA)
In addtion the usage of XI interface is not supported in S/4HANA, the booking of Train
ticket with BIBE ot Hotel Reservation with HRS is not allowed with XI interface.
These services are available only with our partners (Amadeus and Sabre with the
respectives products cytric and GetThere).
For more information please check the note 2892303 - Travel Planning External content
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 259
SAP Travel Management, S/4HANA, S4HCM
8.5 S4TWL - Plan data is not migrated to SAP S/4HANA
Application Components:FI-SL-SL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2474069
Reactivate G/L planning
Symptom
You have migrated from an ERP system to an S/4HANA Finance or an S/4HANA
system. You have used the General Ledger Accounting (new) (FI-GL (new)) planning
function. After the upgrade and the migration, you can no longer access the G/L planning
data. The planning transactions have disappeared from the SAP menu, as have the IMG
activities for G/L planning. In the columns for the planning data, the system always
displays the value 0 if you have defined the following: drilldown reports, Report Painter
reports, or Report Writer reports that read G/L planning data (such as planned/actual
comparisons).
Reason and Prerequisites
The classic ERP FI-GL (new) planning is no longer supported in S/4HANA Finance or
S/4HANA and is replaced with the component BPC for S/4HANA (Business Planning
and Consolidation, formerly IBPF Integrated Business Planning for Finance). All
information about this (links to the installation guides and documentation, other SAP
Notes, and so on) can be found consolidated in SAP Note 2081400.
Solution
If you cannot immediately convert your entry of G/L planning data and your reporting to
BPC for S/4HANA, you can continue to use your G/L planning function for a time in
S/4HANA as well via the steps described below. The steps also contain modifications.
SAP reserves the right to deactivate the old ERP planning function definitively at some
point.
Additional conditions are: The old G/L planning can really only continue to be used. In
other words, planning can be done only for ledgers that already existed in the ERP system
(but not, for example, for ledgers that were created after the migration). For example, you
can no longer add any new customer fields to your old G/L table. Your existing
planned/actual comparisons are restricted to the dimensions that they had before the
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 260
migration. For instance, they cannot report about dimensions of your choice in the
universal journal introduced in S/4HANA. The status is frozen to a certain extent.
1. Implement SAP Notes 2227515 and 2226649 to release deactivated functions (or
import the relevant Support Package) if you have not already done so.
2. Implement the corrections of technical prerequisite note 2253067 or import the
relevant Support Package.
3. In order to activate G/L planning, you must first execute the report
FINS_SET_DEPR_STATUS (with the option 'Activate') - if this has not already been
done - and then insert some transactions into the view FINS_DEPR_OBJECT using
transaction SM30. This addition is a modification; SAP can change or delete these
entries. The following list is to be considered as a superset; we recommend that you add
only the ones that you actually require (Note: adding Transaction GP12N is
mandatory). Point 3) is also the only thing that you have to do if all source code
corrections are already present in your system (so if you have an S4CORE 100 system
with an SP level above 1 or if you have an S4CORE 101 (or a higher release) system). If
you are a greenfield customer, you must also refer to point 4.
GP12N ("Enter planning data")
GP12NA (" Display Plan Data")
FAGLP03 ("Display Plan Line Items")
GLPLUP ("Upload Plan Data from Excel")
FAGLGP52N ("Copy Planning Data")
FAGL_PLAN_VT ("Balance Carryforward: Plan Data")
FAGLPLSET ("Set Planning Profile")
FAGLGA47 ("Create Plan Distribution")
FAGLGA48 ("Change Plan Distribution")
FAGLGA49 ("Display Plan Distribution")
FAGLGA4A ("Delete Plan Distribution")
FAGLGA4B ("Execute Plan Distribution")
FAGLGA4C (for the plan distribution overview)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 261
FAGLGA27 ("Create Plan Assessment")
FAGLGA28 ("Change Plan Assessment")
FAGLGA29 ("Display Plan Assessment")
FAGLGA2A ("Delete Plan Assessment")
FAGLGA2B ("Execute Plan Assessment")
FAGLGA2C ("Plan Assessment Overview")
FAGLGCLE ("Activate Plan Line Items")
FAGLPLI ("Create Planning Layout")
FAGLPLC ("Change Planning Layout")
FAGLPLD ("Display Planning Layout")
GLPLD (also "Display Planning Layout")
FAGL_CO_PLAN ("Transfer Planning Data from CO-OM")
In the view FINS_DEPR_OBJECT, set the object type TRAN for all of these
transactions.
If you use the BAPI BAPI_FAGL_PLANNING_POST for the external data transfer, you
must also include the program (object type PROG)
SAPLFAGL_PLANNING_RFC in the view.
If you want to use the report FAGL_PLAN_ACT_SEC to activate/deactivate the update
of planning data to secondary cost elements (see also SAP Note 1009299), you must also
include the program (object type PROG) FAGL_PLAN_ACT_SEC here.
Save the newly added entries.
4. Only for customers who have installed a fresh S/4HANA Finance or S/4HANA system
(a greenfield approach) or who have migrated from classic G/L (table GLT0):
Call transaction GLPLINST, enter the table FAGLFLEXT as the totals table, and
press F8 ("Execute") and F3 ("Back").
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 262
Use transaction SE38 to create the program
ZCOPY_ENTRIES_FOR_GL_PLANNING (in a valid customer package) with
the title "Copying of Entries for GL Planning", type 1 ("Executable Program").
Copy and paste the coding of ZCOPY_ENTRIES_FOR_GL_PLANNING from
the attachment 'ZCOPY_ENTRIES_FOR_GL_PLANNING'. After program was
created, navigate to the text elements of the program. Create text symbol 001 with
the text "Warning", text symbol 002 with the text "Do you want to continue?
Integrated FI currencies of the non-leading ledgers for the company code can't be
changed any more.", text symbol 003 with text "OK" and text symbol 004 with
the text "Cancel". Activate the text elements.
Decide in which ledgers and company codes you want to use planning. If this
includes new company codes just recently created, go to IMG activity Financial
Accounting->Financial Accounting Global Settings->Ledgers->Ledger->Define
Settings for Ledgers and Currency Types (transaction FINSC_LEDGER). Here,
go to view 'Company Code Settings for the Ledger' for each of the affected
ledgers and check and maintain currency settings according to your requirements
in the new company codes.
Execute the program ZCOPY_ENTRIES_FOR_GL_PLANNING for all ledgers and
all company codes in which you want to use planning.
Attention:
Execute report ZCOPY_ENTRIES_FOR_GL_PLANNING only after you made
sure currency settings are correctly maintained for the affected company codes in
transaction FINSC_LEDGER.
The purpose of report ZCOPY_ENTRIES_FOR_GL_PLANNING is to create
entries in obsolete tables T881 and T882G. These will be used in the reactivated
classic G/L planning. Once created, there is no IMG activity to remove the entries
from the obsolete tables T881 and T882G in S/4HANA. These entries have an
influence on maintenace of the 2nd and 3rd integrated FI currency in transaction
FINSC_LEDGER. If entries in table T882G exist, 2nd and 3rd integrated FI
currencies are not inherited from the leading to the non-leading ledger, because
migrated company codes are identified via existing entries in table T882G to
prevent changes. In ECC integrated FI currencies were not automatically inherited
to the non-leading ledgers. By contrast, these properties are inherited for new
created company codes in S/4HANA.
Check the assignment of your ledgers to the General Ledger Accounting (new) update
scenarios (transaction SM34, view cluster VC_FAGL_LEDGER) and, if
necessary, assign the desired update scenarios to your ledgers. During the transfer
of planning data from CO to GL, only the fields assigned here (via the scenarios)
are updated. (These scenarios are irrelevant for the actual data update in
S/4HANA; they apply only for classic planning data.)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 263
If you are on S4CORE 100 or SAP_FIN 730 please make sure that SAP Note
2346854 is implemented. Otherwise, the system might think that you still need to
carry out a migration (even though you are a greenfield customer) and might
therefore set a posting lock; you are then unable to carry out any further actual
postings.
If the planning layouts should be missing when executing planning transaction
GP12N, please execute transaction GLPLIMPORT to import the following
planning layouts from client 000:
0FAGL-01
0FAGL-02
0FAGL-03
0FAGL-04
0FAGL-05
0FAGL-06
0FAGL-07
5. You should now be able enter, display and report G/L planning data, and all of your
functions in the G/L planning environment should exist and work properly.
6. If you migrate from classic G/L, the planning data which existed already before
migration is copied to table GLT0_BCK. To copy this data to the reactivated planning
tables, please ask the SAP support to give you access to pilot note 2924568 - SAP
S/4HANA: Transfer of classic planning data from table GLT0_BCK.
7. The G/L planning transactions (see the list above) are no longer available in the SAP
menu, and the G/L planning IMG activities are also not included in the SAP Reference
IMG. We recommend creating a folder in your favorites that contains all the transactions
you require. The following is a list of the IMG activities or their transaction codes:
SM30, view V_T001B_PL ("Define Plan Periods")
GLPV (for defining planning versions)
GLP2 (for assigning and activating planning versions)
FAGLGCLE ("Activate Line Items")
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 264
GP30 (for defining distribution keys)
FAGLPLI ("Create Planning Layout")
FAGLPLC ("Change Planning Layout")
FAGLPLD ("Display Planning Layout")
GLPLADM (for creating/changing planner profiles)
GLPLANZ (for displaying planner profiles)
SM30, view V_FAGL_T889A ("Define Document Types for Planning")
SNRO, object FAGL_PL_LC ("Define Number Ranges for Plan Documents")
FAGL_CO_PLAN ("Transfer Planning Data from CO-OM")
KE1Z ("Transfer Planning Data from CO-PA")
8. If you are missing plan/actual reporting transactions like S_E38_98000088
or S_PL0_86000031, you can easily recreate them with transaction maintenance SE93-
>Create, on the next popup select "Transaction with parameters (parameter transaction)",
Enter, on the next screen copy the all the values from the respective transaction in your
ERP system (open SE93 in your ERP system, enter e.g. transaction S_E38_98000088,
press "Display" and copy the values you find there)
9. Note that you only require SAP Note 2403964 if you want to reactivate certain
planning transactions only for the component FI-SL.
In this case this SAP Note 2474069 is not required.
8.6 S4TWL – Migration from account solution to ledger solution
Application Components:FI-AA, FI-GL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3042755
S4TWL - Migration from account
solution to ledger solution
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 265
You are doing a system conversion to SAP S/4HANA or you are already in an SAP
S/4HANA release and would like to use the parallel ledger functionality. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
You are using parallel accounts in an SAP ERP or SAP S/4HANA system and would like
to work with parallel ledgers within SAP S/4HANA.
Solution
Introduction
The whole financial accounting and management accounting functionality in SAP
S/4HANA builds on the universal journal and the usage of parallel ledgers to manage
parallel accounting principles. Future innovations assume the usage of parallel ledgers.
Customers who have used parallel GL accounts to represent different accounting
principles would need to move to parallel ledgers in order to fully benefit from the
innovations in SAP S/4HANA.
Business Process related information
If you use parallel GL accounts to represent different accounting principles in SAP ERP,
you can still perform a system conversion to SAP S/4HANA and continue to use parallel
GL accounts for this purpose. However, to fully profit from recent and future innovations
in SAP S/4HANA you would need to move to parallel ledgers.
For a move to parallel ledgers, you need to consider the following:
If you use SAP ERP and you would like to switch to parallel ledgers, you can do the
migration already in SAP ERP before converting to SAP S/4HANA. Prerequisite
for this migration is the usage of the New General Ledger in SAP ERP.
SAP offers services to perform the migration. Refer to SAP note 756146.
If you already use SAP S/4HANA and would like to do the transformation from
parallel accounts to parallel ledgers, SAP also offers a service to do the migration.
Please contact your SAP account team if you are interested.
Alternatively, you could do the migration in SAP S/4HANA by setting up a new
company code and perform a data migration.
Note: If you plan to do your transition from SAP ERP to SAP S/4HANA by a new
implementation of SAP S/4HANA, we strongly recommend that you no longer use the
account approach for parallel accounting.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 266
Other Terms
Parallel accounts, parallel ledgers
8.7 S4TWL - Special Purpose Ledger
Application Components:FI-SL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3015013
S4TWL - Special Purpose Ledger
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
The usage of special purpose ledger is partly included in the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, this topic is listed under the ID 430.
This note shall provide information on the restrictions that apply for special purpose
ledger in SAP S/4HANA.
Business Process related information
You find a description of the functionality in compatibility scope in the SAP S/4HANA
Feature Scope Description > section Special Ledger (FI-SL).
Generally, special purpose ledger as framework is not part of compatibility scope, which
means it will be available and supported beyond the compatibility scope expiry date.
However, special ledgers and respective tables and reports which have been defined for
applications that are part of the compatibility scope will not be supported beyond expiry
date. This applies to the following applications
EC-PCA - Classical profit center accounting (compatibility scope ID 427)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 267
Cost of Sales ledger (compatibility scope ID 430)
Consolidation preparation - Closing Operations (compatibility scope ID 430)
Custom-defined ledgers based on the applications listed above will also not be support
beyond expire date. Custom-defined ledgers based on any other SAP applications or
custom-built tables will be supported.
Refer to the attached spreadsheet for detailed availability description of the SAP
delivered ledgers and related tables.
Required and Recommended Action(s)
Refer to the following notes and simplification items for further information on the
handling the deprecated applications.
Classical profit center accounting - note 2993220
Cost of Sales ledger - note 3006586
Consolidation preparation - Closing Operations - note 2999249
For all other special purpose ledgers no actions are required.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Special Ledger, ID 430
8.8 S4TWL - Cost of Sales Ledger
Application Components:FI-SL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3006586
S4TWL - Cost of Sales Ledger
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 268
Solution
Description
The usage of the cost of sales ledger is part of the SAP S/4HANA compatibility scope,
which comes with limited usage rights. For more details on the compatibility scope and
it’s expiry date and links to further information please refer to SAP note 2269324. In the
compatibility matrix attached to SAP note 2269324, cost of sales ledger can be found
under the ID 430.
This means that you need to migrate from cost of sales ledger to its designated alternative
functionality cost of sales accounting (CSA) reporting in SAP S/4HANA based on the
Universal Journal before expiry of the compatibility pack license.
Also refer to the SAP S/4HANA Feature Scope Description section Cost of Sales Ledger.
Business Process related information
The cost of sales ledger is used to provide a type of profit and loss statement that matches
sales revenues to the costs of the products sold. It is based on functional areas. In SAP
ERP classic General Ledger Accounting, functional areas are always managed and
reported only in FI Special Ledger. Table GLFUNCT, ledger 0F, contains the totals
records for cost of sales accounting.
In SAP S/4HANA the contents of the cost of sales ledger and all special ledgers created
in table GLFUNCT are included in the Universal Journal (table ACDOCA).
Required and Recommended Action(s)
To use CSA reporting in SAP S/4HANA based on the Universal Journal, you need to
fulfill several prerequistes. Refer to SAP note 932272 for a detailed explanation.
The main points to consider for SAP S/4HANA are as follows:
If you have used classic General Ledger Accounting or General Ledger Accounting
(new) without CSA in SAP ERP, CSA reporting cannot be used in S/4 for the
years in question because the system cannot derive functional areas
properly. Thus, after a conversion to SAP S/4HANA, CSA reporting would
initially still need to be done in the FI-SL ledger 0F.
Once the correct derivation of a functional area has been set-up and complete and
correct account assignments in Accounting can be ensured, CSA reporting based
on the Universal Journal can take place.
However, SAP recommends that you still use CSA reporting in FI-SL for a
transition period of at least one year.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 269
To enable the complete assignment of allocations and postings from CO in SAP
S/4HANA, refer to SAP Note 2680760.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Special Ledger, ID 430
8.9 S4TWL - Report Writer / Report Painter in Finance and Controlling
Application Components:FI-GL-IS, FI-SL-IS, EC-PCA-IS, PS-IS, SD-IS, QM-QC-IS, PM-IS, PP-IS,
CO-PC-IS, CO-OM-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2997574
S4TWL - Report Writer / Report Painter
in Finance and Controlling
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Report Writer and Report Painter are tools for creating reports that fulfil reporting
requirements in Finance. The usage of Report Writer and Report Painter is partly
included in the SAP S/4HANA compatibility scope, which comes with limited usage
rights. For more details on the compatibility scope and it’s expiry date and links to further
information please refer to SAP note 2269324. In the compatibility matrix attached to
SAP note 2269324, this topic is listed under the ID 433 - Reporting/Analytics in Finance
and Controlling.
This note shall provide information on the restrictions that apply for Report Writer and
Report Painter in SAP S/4HANA.
Business Process related information
A general description of the functionality in compatibility scope you find in the SAP
S/4HANA Feature Scope Description > section Report Writer and Report Painter: Usage
in Finance.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 270
Report Writer and Report Painter as tools are not part of compatibility scope, which
means they will be available and supported beyond the compatibility scope expiry
date. However, Report Writer / Painter libraries and respective reporting tables and
reports for applications that are part of the compatibility scope will not be supported
beyond expiry date. This applies to the following applications
EC-PCA - Classical profit center accounting (compatibility scope ID 427)
Cost of Sales ledger (compatibility scope ID 430)
Consolidation preparation - Closing Operations (compatibility scope ID 430)
Reporting for Product Cost Controlling based on KKBx tables
Custom-built reports and libraries will also not be support beyond expire date if they are
based on reporting tables of the applications listed above. Refer to the attached document
for detailed status description of the SAP delivered Report Writer libraries and related
table structures and applications.
Required and Recommended Action(s)
Which reporting capabilities you can use as alternative to Report Writer / Report Painter
depends on the reporting strategies for the alternative applications of the functionalities in
compatibility scope. Refer to the following notes and simplification items for further
information.
Classical profit center accounting - note 2993220
Cost of Sales ledger - note 3006586
Consolidation preparation - Closing Operations - note 2999249
Reporting for Product Cost Controlling based on KKBx tables - note 326525
General recommendations for financial reporting in SAP S/4HANA you find in
note 2579584.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Report Painter, Report Writer, ID 433
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 271
8.10 S4TWL - Schedule Manager
Application Components:CA-GTF-SCM, FI-GL-GL-G
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3003364
S4TWL - Schedule Manager
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Schedule Manager is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope and it’s expiry date and
links to further information please refer to SAP note 2269324. In the compatibility matrix
attached to SAP note 2269324, Schedule Manager can be found under the ID 431.
This means that you need to migrate from Schedule Manager to its designated alternative
functionality SAP S/4HANA Financial Closing Cockpit before expiry of the
compatibility pack license. This note shall provide an overview how you can migrate to
the alternative functionality.
Business Process related information
SAP Financial Closing cockpit is available as of SAP S/4HANA 1709. You find
information about functional scope and setup of SAP S/4HANA Financial Closing
cockpit at help.sap.com.
Note that SAP S/4HANA Financial Closing cockpit requires an extra license. As an
alternative you may consider using standard Closing Cockpit (without license). Refer to
SAP note 2332547 - S4TWL - Closing Cockpit with S/4HANA OP for more information.
SAP also offers SAP S/4HANA Cloud for advanced financial closing as strategic
solution for orchestrating entity close across complet system landscapes. For further
information refer to SAP note 2873915 - FAQ: SAP S/4HANA Cloud for advanced
financial closing.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 272
Required and Recommended Action(s)
As Schedule Manager can be used until the expiry date of the compatibility pack license,
it’s up to each customer to decide, when (with which of the coming
SAP S/4HANA releases) they want to migrate to the designated alternative functionality.
If decide to use the SAP S/4HANA Financial Closing cockpit you can take over your
Schedule Manager task list as templates to this application.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, SCMA, ID 431
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 273
9. Financials - Accounts Payable/Accounts
Receivable
9.1 S4TWL - Integration with FSCM Biller Direct (FI-AR)
Application Components:FIN-FSCM-BD-AR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270384
S4TWL - Integration with FSCM Biller
Direct (FI-AR)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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. Integration of FSCM Biller
Direct with FI-AR is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope and it’s expiry date and
links to further information please refer to SAP Note 2269324. In the compatibility
matrix attached to SAP Note 2269324, this topics can be found under the ID 437.
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.
SAP Biller Direct has been in maintenance mode for years and there is no new
development for this product. The successor product is SAP S/4HANA Cloud for
customer payments. To view the documentation for the successor product, click here.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 274
None
9.2 S4TWL - Integration with FSCM Biller Direct (FI-AP)
Application Components:FIN-FSCM-BD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270386
S4TWL - Integration with FSCM Biller
Direct (FI-AP)
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
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 integration of SAP Accounts Payable (FI-AP) with FSCM Biller Direct is part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, FSCM Biller Direct integration with FI-AP can be found under the ID 437.
Refer to SAP Ariba solutions as its designated alternative functionality.
Required and Recommended Action(s)
As FSCM Biller Direct integration with FI-AP can be used until the expiry date of the
compatibility pack license, it’s up to each customer to decide, when (with which of the
coming SAP S/4HANA releases) they want to migrate to the designated alternative
functionality. Though the decision, at which point in time this will be done, should be
taken early in advance in order to plan accordingly for the migration efforts.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 275
Other Terms
Compatibility Scope, System Conversion, Upgrade
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 276
10.Financials - Asset Accounting
10.1 S4TWL - DATA STRUCTURE CHANGES IN ASSET ACCOUNTING
Application Components:FI-AA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270387
S4TWL - Asset Accounting: Changes to
Data Structure
Symptom
You have been using classic Asset Accounting until now and will be using new Asset
Accounting in SAP S/4HANA.
Other scenarios (such as the switch from SAP ERP 6.0, EhP7 with new Asset Accounting
to SAP S/4HANA) are not considered here.
Reason and Prerequisites
To be able to use new Asset Accounting in SAP S/4HANA, you have to also use new
General Ledger Accounting. If you were using classic General Ledger Accounting before
the conversion to SAP S/4HANA, new General Ledger Accounting is activated
automatically with the conversion.
Solution
The data structures of Asset Accounting have changed as follows:
Actual data:
Actual values from tables ANEP, ANEA, ANLP, ANLC are saved in table
ACDOCA in new Asset Accounting.
The values from table ANEK are saved in tables BKPF and ACDOCA in
new Asset Accounting.
Postings are still made to the table BSEG.
You can continue to use your existing reports and developments with the help
of compatibility views. More details about this can be found below.
Statistical data and plan data:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 277
Statistical values (for example, for tax reasons) from tables ANEP, ANEA,
ANLP and ANLC, are saved in new Asset Accounting in table
FAAT_DOC_IT.
Planned values from tables ANLP and ANLC are saved in table
FAAT_PLAN_VALUES in new Asset Accounting.
10.1.1 Compatibility Views: System and User Usage
The Asset Accounting tables ANEA, ANEP, ANEK, ANLC and ANLP are no longer
updated in SAP S/4HANA.
However, to be able to continue using the reports of Asset Accounting and your own
developments, selections from these tables are automatically diverted to the
corresponding compatibility views. These compatibility views make the information from
the new data store available in the format of the original tables. If it should be necessary
to read the contents of the original tables for a particular reason, you can do this using
DDIC views (for example, FAAV_ANEA_ORI). If you use selections from ANLP please
refer to note 2297425 to check some specific limitations.
Compatibility Views
Access to Original Table
Table
DDL Source
DDIC View
DDL Source
DDIC View
ANEA
FAA_ANEA
FAAV_ANEA
FAA_ANEA_ORI
FAAV_ANEA_ORI
ANEP
FAA_ANEP
FAAV_ANEP
FAA_ANEP_ORI
FAAV_ANEP_ORI
ANEK
FAA_ANEK
FAAV_ANEK
FAA_ANEK_ORI
FAAV_ANEK_ORI
ANLC
FAA_ANLC
FAAV_ANLC
FAA_ANLC_ORI
FAAV_ANLC_ORI
ANLP
FAA_ANLP
FAAV_ANLP
FAA_ANLP_ORI
FAAV_ANLP_ORI
The tables listed above are part of the existing DDIC view. Selections from the DDIC
views listed below are automatically diverted to the corresponding compatibility view.
Compatibility View
DDIC View
DDL Source
DDIC View
V_ANEPK
FAA_V_ANEPK
FAAV_V_ANEPK
ANEKPV
FAA_ANEKPV
FAAV_ANEKPV
V_ANLSUM_2
FAA_V_ANLSUM_2
FAAV_V_ANLSUM_2
V_ANLAB
FAA_V_ANLAB
FAAV_V_ANLAB
V_ANLSUM_1
FAA_V_ANLSUM_1
FAAV_V_ANLSUM_1
V_ANLSUM_5
FAA_V_ANLSUM_5
FAAV_V_ANLSUM_5
Other Terms
SAP S/4HANA; Asset Accounting; ACDOCA; compatibility view
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 278
10.2 S4TWL - ASSET ACCOUNTING
Application Components:FI-AA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270388
S4TWL - Asset Accounting: Parallel
valuation and journal entry
Symptom
You have been using classic Asset Accounting until now and will be using new Asset
Accounting in SAP S/4HANA.
Other scenarios (such as the switch from SAP ERP 6.0, EhP7 with new Asset Accounting
to SAP S/4HANA) are not considered here.
Reason and Prerequisites
To be able to use new Asset Accounting in SAP S/4HANA, you have to also use new
General Ledger Accounting. If you were using classic General Ledger Accounting before
the conversion to SAP S/4HANA, new General Ledger Accounting is activated
automatically with the conversion.
Solution
10.2.1 Parallel Valuation and Journal Entry
In new Asset Accounting you can map parallel valuations with the ledger approach or
accounts approach. A mixture of the two is not supported (ledger with accounts
approach).
You can record the leading valuation of Asset Accounting in any depreciation area of
new Asset Accounting. It is no longer necessary to use depreciation area 01 for
this. The system now posts both the actual values of the leading valuation and the
values of parallel valuation in real time. This means the posting of delta values
has been replaced; as a result, the delta depreciation areas are no longer required
and are no longer supported.
New Asset Accounting makes it possible to post in real time in all valuations (that is,
for all accounting principles). You can track the postings of all valuations, without
having to take into account the postings of the leading valuation, as was partly the
case in classic Asset Accounting.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 279
Asset Accounting is based on the universal journal entry. This means there is no longer
any redundant data store.
Reconciliation postings are no longer necessary with closing operations as General
Ledger Accounting and Asset Accounting are reconciled permanently anyway
due to the universal journal entry.
The hitherto existing periodic posting run for APC values is redundant.
Postings for group assets are redundancy-free.
Parallel Valuation in Realtime
For each asset-related transaction (acquisition, capitalization of assets under construction
(AUC), retirement, post-capitalization and so on), the asset values for all posting
depreciation areas are updated in realtime.
10.2.2 Separate Document for each Valuation
Different accounting principles or valuations are represented - as in new General Ledger
Accounting – in separate ledgers (for the ledger approach) or in a separate set of accounts
(for the accounts approach).
The depreciation areas have equal status. Separate accounting-principle-specific
documents are posted for each accounting principle or valuation.
A business transaction created using integration is split by the system into the operational
part and the valuating part. A posting is made in each case against a technical clearing
account. For the asset acquisition using integration you require a new technical clearing
account for integrated asset acquisition; however, for the asset retirement using
integration the existing clearing accounts asset retirement with revenue and asset
retirement clearing are used. The operational part is posted across accounting principles,
the valuating part is posted accounting-principle-specifically.
10.2.3 Entry of Value Differences for Each Depreciation Area or Accounting Principle
(Ledger Group).
Value differences for each accounting principle or depreciation area can be entered in a
separate transaction (AB01L) for an asset acquisition, a post-capitalization, and a manual
depreciation or write up. This has the following consequences:
It is no longer necessary (or possible) to restrict the transaction types to individual
depreciation areas.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 280
The user exit APCF_DIFFERENT_AMOUNTS_GET is no longer supported.
10.2.4 Entering a Business Transaction
Using the appropriate fields, you can restrict the posting to an accounting principle and
depreciation areas, or limit it to certain areas using the selection of a depreciation area.
The following applies when making entries: The last confirmed entry (restriction) applies
for the posting. In addition, you can adjust the line items of particular depreciation areas
for certain transactions using the Change Line Items function. If you have changed basic
values (such as for the accounting principle, depreciation areas or the posting amount),
the line items are generated again. A business transaction is always entered in local
currency. If you limit the posting to one or more depreciation areas in the same foreign
currency, then the entry (and posting) is made in this foreign currency.
If you select depreciation areas to which differing foreign currencies are assigned and no
depreciation area was selected in local currency, the system issues an error message; you
have to enter several postings for a business transaction like this.
10.2.5 Updating Journal Entries
The journal entries are updated in Financial Accounting at asset level. The entry also
contains the asset number.
10.2.6 Asset Balance Changes in Real Time/Immediately in All Valuations
In SAP S/4HANA, all changes to asset balances are posted to the general ledger in real
time or immediately. Periodic asset balance postings are therefore superfluous and
are no longer supported. This also applies for the processing of special reserves.
This affects the Customizing settings for the depreciation area as follows: When posting
to the general ledger, all options previously used to post asset balances to the general
ledger periodically, no longer apply. Instead, one of the following options must be chosen
for the affected depreciation area:
Depreciation Area
Indicator “Posting in GL”
Area for special reserves (ledger approach and
accounts approach)
4 - Area Posts APC Immediately, Depreciation
Periodically
Area for parallel valuation with the accounts
approach
4 - Area Posts APC Immediately, Depreciation
Periodically
Area for parallel valuation with the ledger
approach
1 - Area Posts in Real Time
Recommendation for depreciation areas in a foreign currency:
In classic Asset Accounting, you may have a depreciation area in a foreign currency that
posts to the general ledger periodically (in other words, in Customizing for the
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 281
depreciation area, you have selected the option Area Posts APC and Depreciation on
Periodic Basis).
However, in new Asset Accounting it is no longer possible that a foreign currency area
posts to the general ledger.
We recommend that you choose the option 0 - Area Does Not Post for postings to the
general ledger. Consequently, this foreign currency area of Asset Accounting is then
managed as a statistical area.
Note about derived depreciation areas for special reserves:
The following applies for both the ledger approach and the accounts approach: For areas
for special reserves, you must choose either option 4 – Area Posts APC Immediately,
Depreciation Periodically or option 0 – Area Does Not Post.
10.2.7 Reconciliation Between Asset Accounting and the General Ledger
It is no longer necessary to reconcile the general ledger with the subledger of Asset
Accounting as from now on Asset Accounting is permanently reconciled with the general
ledger automatically. The programs for reconciliation that existed until now
(RAABST01, RAABST02 and FAA_GL_RECON) are therefore no longer available in
SAP S/4HANA.
10.2.8 Unilateral Assets
Depending on the legal requirements, it may be necessary to manage a fixed asset in one
accounting principle (such as local valuation) as an asset, but in a different accounting
principle (for example, IFRS) not to manage it as an asset, but post the costs directly to
profit and loss instead. You can map these differing capitalization rules in new Asset
Accounting using 'unilateral' assets.
10.2.9 Transaction Types
In new Asset Accounting, it is not possible and also not necessary to restrict transaction
types to depreciation areas. This is not necessary since, when you enter a transaction, you
can restrict it to a depreciation area or accounting principle. In addition, in a posting
transaction, you can select the depreciation areas to be posted to. This can significantly
reduce the number of transaction types that need to be defined in the system.
If you nonetheless have migrated transaction types that are restricted to depreciation areas
(table TABWA or view cluster V_TABWA), this is rejected by the system.
Investment support and also revaluation and new valuation are an exception:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 282
The transaction types for investment support and revaluation are automatically
generated by the system when you create a corresponding measure, and therefore
are restricted to the depreciation area to be posted to.
The transaction types for revaluation and new valuation that relate to transaction type
group 81/82/89 must continue to be restricted to depreciation areas.
Customizing for Transaction Types:
Customizing for restricting transaction types to depreciation areas is - aside from the
above exceptions - now completely superfluous. Therefore the activities for this are no
longer included in the IMG structure for Asset Accounting.
10.2.10Default Transaction Types for Down Payments
Default transaction types for down payments are no longer defined in Customizing
activity Determine Transaction Types for Internal Transactions (table TABWV) as
previously the case. They are now defined in Customizing activity Specify Default
Transaction Types (table TABWD). The system moves existing entries.
The same applies for the default transaction type Gain/loss on retirement for internal
posting of write-ups from gain/loss from asset retirement (the EVL rule).
10.2.11Document Display
A business transaction is split (1) into an operational part that creates an accounting-
principle-independent or ledger-group-independent document and (2) into a valuating
part that creates an accounting-principle-specific/ledger-group-specific document for
each valuation. Several documents are posted, therefore. These documents are displayed
together in the document display. The system displays the complete integrated asset
acquisition in accordance with a valuation that you have selected.
If a business transaction is not entered in Asset Accounting using integration, then only
the valuating documents are posted by the entry. For each valuation that an asset
manages, a valuation-specific document is created.
For each valuation, an accounting-principle-specific document is displayed in the
document display. The operational document is not linked with the valuating document,
and therefore cannot also be displayed.
This document display in Asset Accounting is available in both document simulation and
in the document display.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 283
You can switch the view between the individual valuations (choose the Change
Accounting Principle pushbutton) and between the currency types (choose the Change
Display Currency pushbutton).
Standard Layout for Document Display:
There is the following standard layout for the document display in new Asset
Accounting: Standard: Asset Accounting (New) (3SAP).
We recommend that you use this standard layout or a copy of it adapted to meet your
requirements, since the layout supports you in interpreting the accounting-principle-
specific documents.
10.2.12Asset Explorer
In the navigation area of the Asset Explorer, the depreciation areas of the relevant
assignment are displayed grouped according to accounting principles. The accounting
principle with the leading ledger appears uppermost.
10.2.13Changed and deleted functions in detail
10.2.14Post-Capitalization
You enter post-capitalization both gross and net in the same transaction (transaction
ABNAL). The system always calculates the depreciation values, meaning in the standard
system it assumes that you are entering gross values.
If you want to enter the post-capitalization net, you have to specify the net amount in the
transaction, and reset the depreciation values in the line items.
10.2.15Revaluation
A revaluation is always posted accounting principle-specific. The Accounting Principle
field in transaction ABAWL (Revaluation) is therefore a required entry field.
It is not possible to have manual revaluation postings together with automatic revaluation
through indexes on the same fixed asset in the same depreciation area.
10.2.16Retirement: Distribute the proportional value percentage rate to prior-year asset
acquisitions and current-year acquisitions
If you have been using user exit AFAR0004 to date, you have to move your enhancement
to the following BAdI method:
BAdI: FAA_DC_CUSTOMER, method: PROPVAL_PERCENT_ON_SPECIAL_RET.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 284
You can copy the code from the user exit 1:1 when doing so, since the enhancement
interface has not been changed.
10.2.17Retirement: Posting with net book value
If up to now you have been using the "Post Net Book Value at Retirement" logic, note the
following:
The restriction of posting logic to certain depreciation areas is done in classic Asset
Accounting using area types (as set out in SAP Note 1069166). In new Asset Accounting,
this setting is replaced by the new Customizing activity Post Net Book Value Instead of
Gain/Loss -> Subactivity Specify Depreciation Areas for Net Book Value Posting.
10.2.18Partial retirement
With a partial retirement it is no longer possible to adjust the retirement amount
manually, for example for cost-accounting areas.
Instead you must perform an adjustment posting in an extra step for the cost-accounting
area.
10.2.19Depreciation Posting Run
The determination of the accumulated depreciation of an asset and the posting of
depreciation expense takes place in the system from now on at different points in time:
Calculate depreciation (transaction AFAR):
The planned depreciation is determined with each master record change and with
each posting on the asset and updated in the database accordingly.
Post depreciation (transaction AFAB):
The depreciation run adopts the planned asset values and posts them in Financial
Accounting. The posting document is updated in Financial Accounting at asset
level.
The new program for posting depreciation (depreciation run) has the following
characteristics:
For the update of accumulated depreciation and depreciation expense, the following
applies:
The planned depreciation is determined with master record changes and with
postings on the asset and updated in the database accordingly.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 285
The depreciation run adopts the planned asset values and posts them.
The journal entry is updated in Financial Accounting at asset level.
Errors with individual assets do not necessarily need to be corrected before period-
end closing; period-end closing can still be performed.
You have to make sure that all assets are corrected by the end of the year only so that
depreciation can be posted completely.
It is possible to execute a mid-year test run (also the first run of a period) with a
restriction on assets.
The following applies to parallel processing. The program always carries out parallel
processing.
Caution:
You can still specify a server group.
If you specify a server group, the system behaves as it has until now.
Until now if nothing was specified for the server group then no parallel
processing took place. However, in the new program parallel processing
takes place for the depreciation run on all available servers.
Only the following statuses exist now for the depreciation run:
Errors occurred
Documents posted successfully
No documents to post
You can check the status of the depreciation run in the log (job log or spool output) or in
the Schedule Manager.
The following constraints still apply:
In a test run, the depreciation run can be started in dialog with a limit to a
maximum of 1000 assets.
The update run can only be started in the background.
In an update run, the company code must be capable of being posted to, in
other words, the posting periods must be open.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 286
If the program is started in the background, an entry is written in the Schedule
Manager for each combination of company code/accounting principle (ledger
group).
One difference now is that it is no longer necessary to specify a run type because the
program recognizes whether the depreciation run is being run for the first time or whether
it is a repeat run.
You can no longer jump directly from the depreciation log to line items in an update run
as you could before in classic Asset Accounting.
Instead however, you can generate a list of posted depreciation documents for one or
more periods in the general ledger. In the journal entry the system updates the documents
for depreciation in Financial Accounting at asset level. As such you have the complete
detailed information available in the document. For example, create a list of line items in
the general ledger by choosing Accounting -> Financial Accounting -> General Ledger -
> Account -> Change/Display Items (New) (program FAGL_ACCOUNT_ITEMS_GL)
in the SAP Easy Access Menu. Alternatively, you can choose a corresponding report
under Accounting -> Financial Accounting -> General Ledger -> Information System ->
General Ledger Reports -> Line Items -> G/L Line Items, List for Printing. Select the
relevant documents for the desired combination of G/L accounts, document type and
posting period/year.
Another option is to use the app Display Line Items in General Ledger. Here you can
filter the line items for status "All Items" and for ledger, company code, asset and where
necessary G/L account.
The smoothing method is no longer necessary and is therefore no longer supported. If
you have used this method before the conversion to SAP S/4HANA, you may observe
changes in the book values in the period after the conversion.
As of release SAP S/4HANA 1809, the BSEG table will no longer be updated with the
depreciation run (transaction AFAB, AFABN). (See also SAP Note 2383115.)
It is also no longer possible to subsequently activate this update.
You can still use program RAPOST2001 (transaction AFBP) to display depreciation runs
in the Schedule Manager. However, the selection screen of the program was adjusted to
the new program logic for posting depreciation.
10.2.20Cross-Company Code Posting of Depreciation and Interest
Controlling no longer supports any cross-company code processes in a simplified
manner. This means: In SAP S/4HANA it is not possible to post depreciation and interest
expense to a CO receiver object that is in a different company code to the fixed asset. The
cross-company code cost center check can no longer be activated. For more information,
see SAP Note 2913340.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 287
10.2.21Insurance Values
Until now there were two ways to map insurable values in the system:
Defining specific information for insuring the complex fixed asset in the asset master
record
Managing insurance values in a dedicated depreciation area
In SAP S/4HANA only the second option is supported, the management of insurable
values in a dedicated depreciation area.
The Customizing activities for the first option are no longer available. Their
corresponding fields/field groups in the asset master record are also no longer available.
To map insurable values in SAP S/4HANA, you must create a new depreciation area for
insurance values (area type 05) in the chart of depreciation and define allowed entries for
the depreciation area in the asset classes of the affected complex fixed assets. Note that
new depreciation areas can only be implemented for new fixed assets, not for existing
fixed assets. Existing fixed assets must therefore be transferred manually with the
conversion to SAP S/4HANA, alternatively you can also implement and build the new
depreciation areas in your ERP system for existing fixed assets before the conversion to
SAP S/4HANA. The usual asset lists and journal entry reports are available for reporting.
Special reports for reporting insurance values are no longer necessary.
Please check note 2403248 for the availability of a tool to subsequently create new
depreciation areas for assets already in use.
10.2.22Leasing Management
The leasing opening entry from the asset master record is not supported in SAP
S/4HANA.
You can use the Leasing solution of the component Flexible Real Estate Management
(RE-FX) instead. For more information, see SAP Note 2255555.
10.2.23BAPIs and BAdIs
Changed BAPIs
In the BAPIs that already existed in classic Asset Accounting, the fields Accounting
Principle/Ledger Group and Depreciation Area have been added.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 288
You are only allowed to fill these fields if the Customizing switch for new Asset
Accounting is active.
The following BAPIs from classic Asset Accounting have been adapted for new Asset
Accounting:
Business Object:
Short Description
Business Object:
Object Name
Function Modules
Asset Acquisition
AssetAcquisition
BAPI_ASSET_ACQUISITION_CHECK,
BAPI_ASSET_ACQUISITION_POST
Asset Retirement
AssetRetirement
BAPI_ASSET_RETIREMENT_CHECK,
BAPI_ASSET_RETIREMENT_POST
Asset Post-Capitalization
AssetPostCapitaliztn
BAPI_ASSET_POSTCAP_CHECK,
BAPI_ASSET_POSTCAP_POST
Asset Document Reversal
AssetReversalDoc
BAPI_ASSET_REVERSAL_CHECK,
BAPI_ASSET_REVERSAL_POST
New BAPIs
There are the following new BAPIs:
Business-Object:
Short Description
Business Object:
Object Name
Function Modules
Assets: Down payment
AssetDownPayment
BAPI_ASSET_DOWNPAYMENT_CHECK,
BAPI_ASSET_DOWNPAYMENT_POST
Assets: Investment
Support
AssetInvestSupport
BAPI_ASSET_INV_SUPPORT_CHECK,
BAPI_ASSET_INV_SUPPORT_POST
Assets: Revaluation
AssetRevaluation
BAPI_ASSET_REVALUATION_CHECK,
BAPI_ASSET_REVALUATION_POST
Assets: Subsequent
Costs and Revenues
AssetSubCostRev
BAPI_ASSET_SUB_COST_REV_CHECK,
BAPI_ASSET_SUB_COST_REV_POST
Assets: Transfer
Postings
AssetTransfer
BAPI_ASSET_TRANSFER_CHECK,
BAPI_ASSET_TRANSFER_POST
Assets: Depreciation
AssetValueAdjust
BAPI_ASSET_VALUE_ADJUST_CHECK,
BAPI_ASSET_VALUE_ADJUST_POST
Assets: Write-Up
AssetWriteUp
BAPI_ASSET_WRITEUP_CHECK,
BAPI_ASSET_WRITEUP_POST
Changed BAdIs
In release SAP S/4HANA 2020, the following Business Add-Ins (BAdIs) for the
depreciation calculation have been adjusted for technical reasons:
Customer-Specific SAP Standard Enhancements (FAA_DC_CUSTOMER) and
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 289
BAdI for Customer-Specific Enhancements (FAA_EE_CUSTOMER)
If you use implementations of these BAdIs, you must check them and adjust them if
necessary. For more information, read the long text of error message AU176 (Check on
BAdI implementation for depr. calcul. required; see long text).
New BAdIs
Until now you could use Business Add-In (BAdI) BADI_FIAA_DOCLINES to make
customer-specific changes to the asset document. As of release SAP S/4HANA 1909, this
BAdI has been replaced with the new BAdI FAA_DOCLINES_CUSTOMER; the system
no longer calls existing implementations of the BAdI BADI_FIAA_DOCLINES. If
therefore you have used BAdI BADI_FIAA_DOCLINES until now, you must implement
the interface of the new BAdI FAA_DOCLINES_CUSTOMER instead.
10.2.24Fiscal Year Change/Balance Carryforward
The balance carryforward of Asset Accounting is integrated with the balance
carryforward of Financial Accounting with the universal journal entry:
With the balance carryforward of Financial Accounting, values carried forward are
written on both account and ledger level for each asset.
The new year is opened in Asset Accounting only when all representative ledgers of a
company code have been carried forward.
In order to determine the planned depreciation values for the depreciation run, the
system automatically triggers a recalculation of values for all fixed assets in the
new year.
If errors occurred, you should start the recalculation again manually.
The program Fixed Assets-Fiscal Year Change (RAJAWE00, transaction AJRW) is no
longer necessary and no longer has to be performed at fiscal year change.
10.2.25Year-End Closing
As of release SAP S/4HANA 1909, year-end closing is executed and reset using
transaction FAA_CMP. The following applies for a ledger:
You can close a fiscal year for accounting for a ledger or a depreciation area.
You can also reopen the fiscal year last closed for one or more depreciation areas.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 290
Despite these adjustments, program RAJABS00 (transaction AJAB) is still available in
the SAP Easy Access menu (only until release SAP S/4HANA 1909).
In addition, as of SAP S/4HANA 2020, the program Year-End Closing Asset Accounting
(Cross-Company Code and Ledger) (program FAA_CLOSE_FISCAL_YEARS,
transaction FAA_CLOSE_FISC_YEARS) is available. You use this program to close a
fiscal year from an accounting perspective for one or more company codes or ledgers.
10.2.26Reports for Posted Depreciation
Reports for posted depreciation that are based on table ANLP (especially report Posted
Depreciation, Cost Center-Related, transaction S_ALR_87010175, InfoSet
/SAQPQUERY/AM27) can no longer work on the basis of the account assignment
objects of the fixed asset they are based on.
Exception: The accumulated depreciation accounts are managed as a statistical cost
element. (See also SAP Note 2297425.)
Whilst there is no new fixed asset-specific report, you can display the Fiori app G/L
Account Line Items with the corresponding filter criteria instead. The expense items are
from now on updated with the information of the source fixed asset.
10.2.27Segment Reporting
For segment reporting, the business function FI-AA, Segment Reports on Fixed
Assets (FIN_AA_SEGMENT_REPORTING) is available as of SAP S/4HANA 1610,
FPS01. This business function is always on. In contrast to the business function FI-GL
(New), Profit Ctr Reorganization and Segment Reports (FIN_GL_REORG_1) only
available for ECC (as of SAP enhancement package 5 for SAP ERP 6.0), the new
FIN_AA_SEGMENT_REPORTING business function supports automatic transfer
postings in case of asset master data changes. (See also SAP Note 2257555.)
10.2.28Legacy Data Transfer
The legacy data transfer had to be adjusted in Asset Accounting due to the introduction of
the universal journal entry.
Manual Legacy Data Transfer
The manual legacy data transfer is now divided into the following steps:
You create asset master records for the legacy data transfer using transaction AS91.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 291
You post the transfer values using transaction ABLDT; In doing so, a universal
journal entry is posted for the fixed asset.
With transaction AB01, you post, for a legacy data transfer during the year, the
transactions that occurred in the fiscal year of the legacy data transfer between the
start of the fiscal year and the date of the legacy data transfer.
You use transaction ABLDT_OI to post the open items for an asset under
construction with line item processing.
The following functions are also available with the manual legacy data transfer:
If wrong transfer values were posted, you must reverse the journal entry and then
recreate it.
You can use transaction AS92 to change master data; transaction AS93 to display
master data; and transaction AS94 to create subnumbers for the asset master
record.
There are corresponding transactions for group assets with the legacy data transfer
(transactions AS81 to AS84).
You can find the changed Customizing activities and functions for the legacy data
transfer in Customizing for Asset Accounting under Asset Data Transfer.
Automatic Legacy Data Transfer
In addition to the manual transfer, the following automatic (mass-compatible) transfer
methods are available:
Legacy data transfer using Microsoft Excel (transaction AS100)
Transaction AS100 is still available; it has been completely adapted to the logic of
the universal journal entry.
Legacy data transfer using the Legacy System Migration Workbench (transaction
LSMW)
With the legacy data transfer using transaction LSMW, you can only transfer
legacy assets using the business object method. The options Batch Input and
Direct Input are no longer available.
Legacy data transfer using BAPI
With this you create a customer-defined program that calls module
BAPI_FIXEDASSET_OVRTAKE_CREATE.
This corresponds with choosing method CREATEINCLVALUES of business
object BUS1022 in transaction LSMW.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 292
Transfer of mid-year transactions
You cannot only transfer mid-year transactions when creating legacy assets; You
can also post them subsequently using the standard BAPI for Asset Accounting.
All standard functions of the relevant posting BAPI are available with this. The
system posts these transactions automatically against the migration clearing
account.
Due to extensive changes in the data store of Asset Accounting, the following mass-
compatible transfer methods are no longer supported:
Program RAALTD01
Program RAALTD11
Program RAALTD11_UNICODE
Any type of batch input on the transactions AS91, AS92, AT91, AT92, AS81, AS82,
AT81 and AT82 only allows the creation and change of master data. Values
cannot be transferred this way. You must rather use transaction ABLDT;
however, this is not mass-compatible. The AT** transactions were also deleted;
the above also and explicitly refers to customer-defined replacement transactions
created analog.
10.2.29Archiving
The reload program for archiving RAARCH03 is no longer supported.
Archived documents of Asset Accounting can only be written but not reloaded.
10.2.30Constraints
The following constraints apply:
As of release SAP S/4HANA 1610, user-defined currencies are available in General
Ledger Accounting (FI-GL). These are not available in Asset Accounting, but
they are translated with the document life. The parallel local currencies used until
now are translated in the meantime historically in the fixed assets, provided that
depreciation areas are set up for parallel currencies.
For more information on currencies in the universal journal, see SAP Note
2344012.
The following are not supported in new Asset Accounting: The subsequent
implementation of a ledger, the subsequent switch from the accounts approach to
the ledger approach (scenario 7 and 8 in the migration scenarios for new General
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 293
Ledger Accounting), and the implementation of a new depreciation area.
The function subsequent implementation of a further accounting principle is
available as of release SAP S/4HANA 1610, provided that you use the ledger
approach.
And as of release SAP S/4HANA 1809, you can use the functions available for
the subsequent implementation of a depreciation area (program
RAFAB_COPY_AREA and BAdI FAA_AA_COPY_AREA).
Not all transaction data is deleted in Asset Accounting when you reset a company
code (using transaction OABL). See also SAP Note 2419194.
ALE transfer is not available in new Asset Accounting.
The batch input method for transactions based on AB01 is no longer available; you
can use the changed and new BAPIs for postings instead. Information about these
BAPIs can be found above.
The batch input technique for master data is no longer available. You can use a
different transfer method instead for the legacy data transfer, for example the
BAPI for master data or direct input.
The integrated posting of investment support on assets using FI transactions is no
longer supported. Instead, use transaction ABIFL, and post the customer
transaction against a clearing account.
Impairments from the business function New General Ledger Accounting 3
(FIN_GL_CI_3), SAP enhancement package 5 for SAP ERP 6.0 are no longer
available.
For Lease Accounting Engine (LAE) see SAP Note 2270391.
For Joint Venture Accounting (JVA) see SAP Note 2270392.
For specific business functions see SAP Note 2257555.
10.2.31Existing Data and Conversion/Migration
10.2.32Existing Data
Master Data
Existing master data is not changed by the activation of new Asset Accounting or the
upgrade to SAP S/4HANA.
Customizing Data
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 294
However, you might possibly have to migrate and adjust your Customizing data. This
depends on your source release, so the release you have before the migration to SAP
S/4HANA. Existing Customizing settings from classic Asset Accounting or from new
Asset Accounting are transferred; this means that to the extent you have already been
working with classic or new Asset Accounting, you do not have to make all the
Customizing settings again. You have to migrate, to some extent check, change and add
to your Customizing data in these two cases: you are migrating from classic General
Ledger Accounting with classic Asset Accounting, or from new General Ledger
Accounting with classic or from new Asset Accounting.
Transaction Data
Transaction data is migrated from the existing subledger data store of Asset Accounting
to the universal journal entry. The data however remains in the original database tables
and can be read using the compatibility view in the previous format, for example in
customer-defined programs (for the compatibility views, cf. SAP Note 2270387). The
tables of the existing subledger entry are no longer required for further processing and
can be unloaded from the database if necessary. All the required information is now in
the new database tables.
Note the following also:
The migration must take place at a time when only one fiscal year is open in Asset
Accounting.
Once migration is completed, you are not allowed to open any fiscal year again
that occurred before the migration in Asset Accounting.
You cannot reverse documents that were created before the conversion from classic to
new Asset Accounting. Instead, you have to make an inverse posting.
It is not possible to reverse integrated asset postings that were posted in new Asset
Accounting in SAP enhancement package 7 for SAP ERP 6.0, SP02 or higher and
were migrated. Instead, you have to make an inverse posting.
The values for migrated asset line items (MIG_SOURCE = A) are migrated solely
from BSEG relevant currencies. Subsequently added currencies which were not
available before the migration are not created for migrated asset line items in the
standard. This is especially the case for automatically created free defined
currencies during the migration (for example if the CO currency was not available
in G/L before migration it is automatically added as a free defined currency
during migration). If currencies were subsequently added to migrated documents,
then it is not possible to reverse migrated asset documents. Instead, you have to
make an inverse posting.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 295
If until now you updated transactions in parallel valuations with different fiscal year
variants and want to continue using this update, then you must implement a new
representative ledger using the SAP General Ledger Migration Service before you
install SAP S/4HANA. For more information about alternative fiscal year variants
with parallel valuation, see SAP Note 2220152.
It may no longer be possible to process worklists that have been created before the
changeover to the new Asset Accounting. This involves worklists that create
transaction data (however, not master data changes), such as worklists for
retirement without revenue, retirement with revenue, intercompany asset transfer,
and impairment posting. You should therefore either process these worklists
before you activate the Customizing switch, or create them again once you have
activated new Asset Accounting.
For more information, see SAP Note 2220152.
For more information about the conversion or migration to SAP S/4HANA, see the
following:
Information Source
Explanation
Conversion Guide for SAP S/4HANA
Conversion Overview: Getting Started, Preparing
the Conversion, Realizing the Conversion
SAP Note 2332030
Specification for the Conversion/Migration in
Accounting
Application Documentation of New Asset
Accounting
Specification for the Migration in Asset
Accounting: Recommended Time for the
Migration, Prerequisites, Migration of
Customizing with Many Examples, Among
Others.
10.2.33User Interface
Implementation Guide
New Asset Accounting uses its own IMG structure in the SAP Reference IMG:
This IMG structure contains some of the same activities as are in classic Asset
Accounting, some changed activities, and some new activities; a few of the classic Asset
Accounting activities are no longer contained in the IMG structure at all.
SAP Easy Access Menu
The SAP Easy Access Menu for new Asset Accounting remains largely the same as for
classic Asset Accounting. You can continue to find it under SAP Menu -> Accounting ->
Financial Accounting -> Fixed Assets.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 296
However, there is rerouting to some new transactions and some transactions which have
become superfluous are no longer available. (Compare the following explanations of the
transactions.)
Transactions
Some of the classic Asset Accounting transactions have been replaced by corresponding
new ones. So that you can make accounting-principle-specific postings, the input fields
Depreciation Area and Accounting Principle can be found on the screen for the new
transactions. The name of the relevant new transaction ends in "L". Example: The
previous transaction AB01 (Create Asset Transactions) is replaced by the new transaction
AB01L.
The new transactions are: AB01L, ABAAL, ABAKL, ABAOL, ABAVL, ABAWL,
ABGFL, ABGLL, ABIFL, ABMAL, ABMRL, ABNAL, ABNEL, ABNKL, ABSOL,
ABSTL, ABUML, ABZEL, ABZOL, ABZPL, ABZUL.
If you enter the transaction familiar from classic Asset Accounting (that does not end in
L), you are automatically transferred to the new transaction (that ends in L).
As of release SAP S/4HANA 1909, both transactions OAAR and OAAQ have been
redirected to transaction FAA_CMP.
As of release SAP S/4HANA 2020, transaction AJAB (program RAJABS00) is
redirected to transaction FAA_CLOSE_FISC_YEARS.
Transaction ABSO_OLD from classic Asset Accounting is no longer available in new
Asset Accounting; you can use transaction AB01L instead. All SAP Notes that refer to
transaction ABSO_OLD are automatically invalid in SAP S/4HANA.
The following transactions are no longer available:
ABST, ABST2, ABSTL
ABAWN
ABUB
AW01_AFAR
ABF1 and ABF1L
AJRW
OASV
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 297
AB02
ASKB and ASKBN
ABMW
ABCO
AUN1, AUN2, AUN3, AUN4, AUN5, AUN6, AUN7, AUN8, AUN9, AUN10,
AUN11
AR16, S_ALR_87101171 (deleted as of release SAP S/4HANA 2022)
Programs
The following programs are no longer available:
RAALTD01, RAALTD11, RAALTD11_UNICODE
RAPERB2000, RAPOST2000, RAPOST2010
RAABST01, RAABST02, FAA_GL_RECON
RAJAWE00
RAUMFE20
RAAEND02 (deleted as of release SAP S/4HANA 2022)
RARUECK1
Adjustment programs RACORR_0TW_COMPLETE,
RACORR_ADD_MISSING_T082AVIEWB, RACORR_ANEK_AWSYS,
RACORR_ANLA_AKTIV, RACORR_ANLA_ZUJHR,
RACORR_ANLC_ANLP_POSTED_VALUES,
RACORR_ANLC_DEL_ANLB_LGJAN, RACORR_ANLH_LANEP,
RACORR_ANLW, RACORR_ASSET_GROUP_IND, RACORR_DELETE_ANLBZA,
RACORR_DELETE_EMPTY_TABW_ENTRY, RACORR_EUROGSBER,
RACORR_LINE_ITEMS_CHECK, RACORR_MIGRATION_NEWGL_LDGRP,
RACORR_MISSING_ANEP_REVERSALS, RACORR_NEW_GRP_ASSET_ASSIGN,
RACORR_PERFY_REPAIR, RACORR_T082AVIEW1, RACORR_T093_VZANSW,
RACORR_TABA_ENTRY_CREATE, RACORR_VIEW0_SET, RACORR_XNEGA,
RACORR_XZORG, RACORR_XZORG_46A, RACORR07A, RACORR10_PERFY24,
RACORR100, RACORR100_WITOUT_AV, RACORR101, RACORR102,
RACORR103, RACORR104, RACORR105, RACORR106, RACORR107,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 298
RACORR108, RACORR110_3ERRELEASES, RACORR110_B, RACORR111,
RACORR112, RACORR113, RACORR113_TCODE_FILL, RACORR114,
RACORR114_A, RACORR115, RACORR116, RACORR117, RACORR118,
RACORR119, RACORR120, RACORR121, RACORR122, RACORR125,
RACORR126, RACORR127, RACORR128A, RACORR129, RACORR130,
RACORR131, RACORR132, RACORR133, RACORR134, RACORR135,
RACORR137, RACORR138, RACORR139, RACORR14_OLD, RACORR140,
RACORR141, RACORR142, RACORR143, RACORR144, RACORR145,
RACORR146, RACORR147, RACORR148, RACORR149, RACORR150,
RACORR151, RACORR151_CREATE_ANLC, RACORR152, RACORR16,
RACORR17, RACORR18, RACORR20_A, RACORR21, RACORR23_NEW,
RACORR24, RACORR45A, RACORR46, RACORR47, RACORR48, RACORR49,
RACORR50, RACORR51, RACORR52, RACORR53, RACORR54, RACORR55,
RACORR56, RACORR57, RACORR58, RACORR59, RACORR60, RACORR61,
RACORR62, RACORR63, RACORR64, RACORR65, RACORR66, RACORR68,
RACORR69, RACORR75, RACORR76, RACORR77, RACORR78, RACORR79,
RACORR7A, RACORR7B, RACORR80, RACORR81, RACORR82, RACORR83,
RACORR83_A, RACORR84, RACORR85, RACORR86, RACORR87, RACORR87A,
RACORR88, RACORR89, RACORR89B, RACORR90, RACORR91, RACORR92,
RACORR93, RACORR94, RACORR96_SINGLE_ASSETS, RACORR97, RACORR98,
RACORR99, RAFABDELETE
Authorization Objects
The following authorization object is no longer available:
A_M_ANLKL (deleted as of release SAP S/4HANA 2022)
Other Terms
SAP S/4HANA; Asset Accounting; parallel valuation; parallel accounting; ledger
approach; accounts approach; ACDOCA; post-capitalization; revaluation;
retirement; partial retirement; depreciation; AFAR; AFAB; smoothing method; posting
BAPI; fiscal year change, balance carryforward; Legacy data transfer; legacy asset;
RAARCH03; scenario 7; scenario 8; ALE transfer; batch input; worklist; impairment;
conversion; migration; deleted programs; deleted transactions
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 299
10.3 S4TWL - INTEGRATION TO LEASE ACCOUNTING ENGINE
(LAE)
Application Components:CRM-LAM, FI-LA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270391
S4TWL - Integration to Lease
Accounting Engine (LAE)
Release Restriction
2211665
Release information for "SAP for
Banking" in connection with "SAP
S/4HANA, on-premise edition 1511"
Release Restriction
2328754
Release information for "SAP for
Banking" in connection with "SAP
S/4HANA 1610" ("SAP S/4HANA, on-
premise edition 1610")
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
If you have one at least one entry in table TFILA_FA_002 this note is relevant for you!
The LAE (Lease Accounting Engine) does not support the new Asset Accounting
which is automatically activated in S4H.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 300
10.4 S4TWL - Asset management transfers in Joint Venture Acccounting
(JVA)
Application Components:FI-AA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270392
S4TWL - Joint Venture Accounting
(JVA)
Symptom
You are converting your system to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Prerequisites:
Joint Venture Accounting is active and at least one of the transactions listed below are
used. This means that
Component 'JVA' is active in table TRWCA: See transaction SM30 for table
TRWCA and check that the record for COMP = JVA has a "To year" greater
or equal to the current year.
For at least one company code the global JVA parameters have been maintained: A
record has been created on view V_T8JZA with transaction GJZA.
You are using the AM/MM Method 8 ("United States (COPAS)") or a different one,
for which records have been defined on table T8JHL .
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 301
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.
10.5 S4TWL - SELECTED BUSINESS FUNCTIONS IN FINANCIAL
ACCOUNTING (FI-GL AND FI-AA)
Application Components:FI-AA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2257555
S4TWL - Asset Accounting: Business
Functions from FI-AA and FI-GL
Symptom
You will be using new Asset Accounting in SAP S/4HANA.
You would like to know which business functions relevant for Asset Accounting from the
SAP enhancement packages for SAP ERP 6.0 are available in SAP S/4HANA.
Solution
10.5.1 Business Functions of Asset Accounting
The following business functions exist for Asset Accounting:
Description
Technical Name
Release
Status in
SAP
S/4HANA
On Premise
Usability in
SAP
S/4HANA
FI-AA, Asset
Accounting
FIN_AA_CI_1
SAP
enhancement
Customer
switchable
Obsolete
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 302
package 6 for
SAP ERP 6.0
FI-AA,
Parallel
Valuation
FIN_AA_PARALLEL_VAL
SAP
enhancement
package 7 for
SAP ERP 6.0,
SP02
Customer
switchable
Obsolete
FI-AA,
Segment
Reports on
Fixed Assets
FIN_AA_SEGMENT_REPORTING
SAP S/4HANA
1610, FPS01
Always on
See below
In SAP S/4HANA, only new Asset Accounting is available.
The corresponding functions are available there without them being linked to the business
function.
The following business functions FIN_AA_CI_1 and FIN_AA_PARALLEL_VAL are
therefore obsolete in SAP S/4HANA.
If you have not activated the respective business function before the switch to SAP
S/4HANA (in your source release), you do not need to activate the business
function there (in order to be able to use the corresponding functions).
If you have activated one or both of the above-mentioned business functions before
the switch to SAP S/4HANA (in your source release), the actual activation status
in SAP S/4HANA remains as "on".
For information about the business function FI-AA, Segment Reports on Fixed
Assets (FIN_AA_SEGMENT_REPORTING), see the following section 'Business
Functions of General Ledger Accounting'.
10.5.2 Business Functions of General Ledger Accounting
For Asset Accounting, the following business functions from General Ledger Accounting
are relevant:
Description
Technical Name
Release
Status in SAP
S/4HANA On
Premise
Usability in
SAP S/4HANA
FI-GL (New),
Profit Ctr
Reorganization
and Segment
Reports
FIN_GL_REORG_1
SAP
enhancement
package 5 for
SAP ERP 6.0
Customer
switchable
Not supported
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 303
FI-GL (New),
Segment
Reorganization
FIN_GL_REORG_SEG
SAP SAP
enhancement
package 6 for
SAP ERP 6.0
Customer
switchable
Not supported
The functions from both these business functions are not available in SAP S/4HANA.
If you have not activated either of these two business functions before the switch to
SAP S/4HANA (in your source release), you cannot activate either of the two
business functions in SAP S/4HANA.
If want to subsequently activate segment reporting for fixed assets in SAP
S/4HANA, then you need to use the business function FI-AA, Segment Reports on
Fixed Assets (FIN_AA_SEGMENT_REPORTING); this was separated from the
business function FIN_GL_REORG_1 and is available separately as of SAP
S/4HANA 1610, FPS01 and SAP S/4HANA 1709 (see also SAP Note 2375643).
As of SAP S/4HANA 1511, FPS02, the following applies: If you have activated one
or both business functions before the switch to SAP S/4HANA (in your source
release), you can switch to SAP S/4HANA but you cannot use the functions of
the business functions in SAP S/4HANA.
The exception to this is segment reporting for fixed assets; this is still available in
SAP S/4HANA.
10.5.3 Other Business Functions
Description
Technical Name
Release
Status in SAP
S/4HANA On
Premise
Usability in SAP
S/4HANA
CO, Parallel
Valuation of Costs
of Goods
Manufactured
FIN_CO_COGM
AP enhancement
package 5 ff. for
SAP ERP 6.0
Customer
switchable
Supported (see
details below)
Materials
Management -
Enhancements in
Procurement
LOG_MM_CI_3
SAP enhancement
package 5 for SAP
ERP 6.0
Customer
switchable
Supported
New Asset Accounting relates as follows to the business functions listed:
CO, Parallel Valuation of Cost of Goods Manufactured (FIN_CO_COGM), SAP
enhancement package 5 ff. for SAP ERP 6.0
If this business function is active, you can also use different valuation for
investment measures according to different accounting principles. These valuation
approaches are activated for each depreciation area when you settle investment
measures for assets under construction (AUC) and for the full settlement to
completed assets, depending on the accounting principle. Differing capitalization
percentage rates from the Customizing activity for calculating the capitalization
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 304
value of investment measures (transaction OKGK) are taken into account.
For information about the availability of the business function in SAP S/4HANA,
see SAP Notes 2270414 and 1852519.
Materials Management - Enhancements in Procurement (LOG_MM_CI_3), SAP
enhancement package 5 for SAP ERP 6.0
If you use purchase orders for low-value assets (LVA) in Asset Accounting, then
in the future it is not possible to note purchase orders if the LVA maximum
amount is exceeded. If you want to use the function for noting purchase orders,
we recommend that you activate the business function Materials Management -
Enhancements in Procurement (LOG_MM_CI_3).
Other Terms
SAP S/4HANA; Asset Accounting; FIN_AA_CI_1; FIN_AA_PARALLEL_VAL;
FIN_AA_SEGMENT_REPORTING; FIN_GL_REORG_1; FIN_GL_REORG_SEG;
FIN_CO_COGM; LOG_MM_CI_3
10.6 S4TWL - Check for duplicate internal asset line items (FAAT_DOC_IT)
Application Components:FI-AA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2977180
S4TWL - Checking for duplicate records
in the asset line item table
(FAAT_DOC_IT)
Symptom
Previously, a program error caused duplicate records to be updated in the asset line item
table. However, this error does not affect reported asset values in this release or in a
previous release.
Nevertheless, due to an incompatible change in SAP NetWeaver, the presence of these
records during an upgrade now causes a technical termination that stops the upgrade
process as such. The Software Update Manager (SUM) can be used to identify and
resolve this situation before the upgrade to SAP S/4HANA 1909, 2020, and so on.
Reason and Prerequisites
Program error
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 305
Solution
For technical details about the cause of the error and how to resolve it, see SAP Note
2948964.
Other Terms
FAAT_DOC_IT, CLS4SIC_FI_AA, FAA_DELETE_DUPLICATE_DOC_IT,
SI6_FIN_AA
10.7 S4TWL - Group Assets
Application Components:FI-AA, CA-JVA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3014869
S4TWL - Group Assets
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
The functionality group assets in Asset Accounting is part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, group assets can be found under the ID 428.
SAP does not plan to provide an alternative for group assets in Asset Accounting. If you
wish to group your assets also in future we recommend building your own solution by
introducing respective user fields in asset master or make use of the existing feature
“Asset Super Number” to group asset if it is not yet used for any other purpose.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 306
A description of the functionality in compatibility scope you find in the SAP S/4HANA
Feature Scope Description in section FI-AA: Group Assets.
Required and Recommended Action(s)
Until the expiry date of the compatibility pack license, you can still use group asset
functionality. However, we recommend defining your future strategy early in advance of
this date because group asset functionality must not be used after this point in time.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Joint Venture Accounting, ID 428
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 307
11.Financials - Cash Management
11.1 S4TWL - Electronic Payment Integration for China
Application Components:FI-LOC-EPI-CN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3087756
Deprecation of Cash Operations for
China (COPC) and EPIC Embedded
Cash Budgeting
Symptom
You would like to use Cash Operations for China (also known as COPC) to manage
your cash pools and cash concentration, or you would like to use EPIC embeded Cash
Budgeting functions. However, this is not recommended since the solution of COPC is
out of development and will be deprecated in SAP S/4HANA 2023.
Reason and Prerequisites
The functions provided by Cash Operations for China have been replaced by the
solution Cash and Liquidity Management under component FIN-FSCM-CLM.
The functions provided by EPIC embedded Cash Budgeting have been replaced by Cash
Budgeting in SAP S/4HANA Finance for cash management, version for China.
Solution
In order to leverage the latest product features and maintainance delivered by SAP, please
make sure you use Cash and Liquidity Management for your treasury management
requirements. If you would like to use Fiori-based apps, you are recommended to use
SAP S/4HANA 1809 or above.
Please be reminded of the risks of using COPC:
Feature and/or processing logic explanation, suggestions about system operation
and/or configuration, and how-to requests are not supported via customer
incidents. You can find further details in SAP note 83020.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 308
COPC folder under "SAP Menu -> Accounting -> Financial Accounting -> Banks ->
Country Specifics -> China -> Cash Operations" will be officially removed and
use of T-codes will not be authorized after one release.
Other Terms
EPIC, COPC, Cash Concentration, Cash Pool, EPIC embedded Cash Budgeting
11.2 S4TWL - CASH MANAGEMENT - GENERAL
Application Components:FIN-FSCM-CLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270400
S4TWL - Cash Management - General
Symptom
You are working on a system conversion to SAP S/4HANA. The following SAP
S/4HANA Transition Worklist item is applicable to this case.
Reason and Prerequisites
System Conversion to SAP S/4HANA.
Solution
Description
Once customers have installed SAP S/4HANA, SAP S/4HANA Finance for 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
available in SAP S/4HANA.
For customers who want to move from the classic Cash and Liquidity Management
to SAP S/4HANA Finance for cash management, they need to carry out the following
activities:
Convert their system to SAP S/4HANA or set up a new SAP S/4HANA system.
Activate and then implement SAP S/4HANA Finance for cash management.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 309
The conversion to SAP S/4HANA is supported by data migration tools, which also
consider cash management data. The implementation of Bank Account Management
(included in SAP S/4HANA Finance for cash management) is an essential part of the
SAP S/4HANA implementation/conversion project.
Business Value
The new SAP S/4HANA Finance for cash management provides cash managers with
novel user experiences, flexibility and new processes:
1. End-to-end process of monitoring bank statement imports, checking cash position, and
transferring fund to handle surplus and deficit.
2. Medium-term liquidity forecast and rolling plans of long-term liquidity.
3. Centralized bank account management, with which business users can manage bank
accounts as master data with more business attributes.
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
Liquidity
Management
SAP Cash
Management,
delivered with SAP
S/4HANA 1511
SAP S/4HANA
Finance for cash
management,
delivered
with SAP
S/4HANA 1610
(Delta to 1511)
SAP
S/4HANA
Finance
for cash
manageme
nt,
delivered
with SAP
S/4HANA
1709
(Delta to
1610)
SAP
S/4HANA
Finance for
cash
managemen
t, delivered
with SAP
S/4HANA
1809 (Delta
to 1709)
Cash
Position /
Liquidity
Forecast
Cash Position:
FF7A
Liquidity
Forecast: FF7B
Data Integration:
Cash Position:
Use app Cash
Position to
check high-
level KPIs.
Use app Cash
Position
Details to
Liquidity
Forecast:
You can now use
the following Fiori
apps in your Fiori
launchpad:
Cash
Position
and
Liquidity
Forecast:
With the
app "Cash
Flow
Analyzer",
Data
Integration:
Promise-
to-
pay
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 310
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
display
detailed
positions on
bank
accounts.
Liquidity Forecast:
Use SAP
BusinessObjects
Analysis, edition for
Microsoft Office
(AO) or transaction
code RSRT to open
the BW queries for
liquidity forecast.
Data Integration:
Bank
statements
Bank statement
Accounting
documents
Payment
accounting
documents
AR/AP
accounting
documents
Memo records
TRM
CML
FI-CA
Not integrated:
Industry-
specific
data
sources,
sales
orders,
purchase
orders,
Liquidity
Forecast
Liquidity
Forecast
Detail
Data Integration:
MM
(Materials
Manage
ment)
SD (Sales
and
Distributi
on)
you can
obtain an
overview of
the
aggregate
amounts
and line
item details
of short-
term cash
position,
medium-
and long-
term
liquidity
forecast,
and actual
cash flows.
You can
analyze
cash flows
over days,
weeks,
months,
quarters, or
years. You
can get an
end-of-
period
report with
shifts to
working
days. You
can also
display an
Bank
Account
Group
Hierarchy
view and
Liquidity
Item
Hierarchy
view. This
is a
successor
app for
"Cash
Position
Details", as
well as
combining
the key
features
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 311
fund, grant,
payment
orders,
payment
requests
from
"Liquidity
Forecast
Details"
and "Cash
Flow Detail
Analysis".
Data
Integration
:
Promis
e-
to-
pay
Memo
Record
Create memo
records:
FF63
Display memo
records
List: FF65
FF63 and FF65 are
supported with cash
management
accounts.
You can now use
the following Fiori
apps in your Fiori
launchpad:
Actual Cash
Flow
Cash Flow -
Detailed
Analysis
Memo
record is
physically
stored in
One
Exposure.
New Fiori
app
"Manage
Memo
Records"
available for
normal
maintenance
. FF63/FF65
are not
deprecated
yet.
Payment
(F110,
F111)
F110
F111
F110 and F111 are
supported as
before.
Liquidity
Planner
Plan part:
BPC or BW-IP
set up in a
separate
system.
ETL for master
data and
transaction
al data is
necessary.
Plan part:
Embedded
Liquidity
Plan with
BPC/PAK
(Planning
Application
Kit) and
SAP
BusinessOb
jects
Analysis,
Actual part:
You can now use
the following Fiori
Theme apps in
your Fiori
launchpad:
Actual Cash
Flow
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 312
Actual part:
Actual Cash
Flow
Report:FLQ
REP
Configuration:
Account
assignment
through
Query and
Query
Sequence
edition for
Microsoft
Office UI.
No ETL is
needed.
Automated
liquidity
forecast is
integrated.
The
functionality
of hedge
planning/re
port and
currency
conversion
among
different
planning
units are
not
supported.
Actual part:
Old transaction
is not
available.
You can use
SAP
BusinessOb
jects
Analysis,
edition for
Microsoft
Office (AO)
or
transaction
code
RSRT to
show the
integrated
actual cash
flow
information.
Configuration:
Cash Flow -
Detailed
Analysis
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 313
Account
assignment
through
Query and
Query
Sequence
Cash
Concentrat
ion
Create: FF73
Access with
Variant:
FF74
Print
Confirmatio
ns: FF.8
Post: FF.9
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.
The cash
pooling
process is
managed by
the apps
"Manage
Cash Pools"
- to maintain
cash pool
master data,
"Manage
Bank
Accounts" -
to
assign/unass
ign bank
accounts to
cash pool(s)
and
"Manage
Cash
Concentratio
n" - to trigger
the
simulation
and create
payment
requests of
cash
concentratio
n.
Distributed
Cash
Load remote Cash
Position and
Liquidity Forecast
data through IDOC.
Retrieve remote
Liquidity Planner
actual data and
cash summary data
of classic cash into
the One Exposure
of S/4 HANA Cash
Management.
A new web
service is
provided to
capture
external
cash flows.
BW
Extractor
The extractor
0TR_CM_1 is for
ECC.
The extractor
0TR_CM_1 is for
ECC only and it
reads data from
classic cash tables.
Those classic cash
tables does NOT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 314
have business data
in SAP S/4HANA.
Business Process Related Information
Transactions not
available in SAP
S/4HANA
FF$3
FF$L
FF$X
FF-3
FF-4
FF-5
FF-6
FF/1
FF/2
FF.3
FF/8
FF69
FF70
FF71
FF72
FF7A
FF7B
FF:1
FFTL
FFZK
FLQAB
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 315
FLQAC
FLQAD
FLQAF
FLQAL
FLQAM
FLQAM_TP
FLQC10
FLQC12
FLQC13
FLQC13F
FLQC1A
FLQC2
FLQC20
Another known limitation is that, if the bank name is saved in Japanese with half-width
kana, no results can be found, when you use these half-width kana for keyword search.
Note：
Depending on your license, you can use a basic scope of Cash and Liquidity
Management or a full scope of this solution capability. For information about the scope
differences between the two capabilities, see the help document.
Required and Recommended Actions
For required and recommended actions, please check the Configuration Guide for SAP
S/4HANA Finance for Cash Management at https://help.sap.com/s4_op_clm.
How to Determine Relevancy
Please refer to the Relevance Check section of the simplification item.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 316
If classic Cash Management and Liquidity Planner are used (e.g. for cash position
reporting), you need to re-implement the new SAP S/4HANA Finance for cash
management.
Other Terms
SAP S/4HANA Transition Worklist
11.3 S4TWL - CASH MANAGEMENT - Bank Accounts
Application Components:FIN-FSCM-CLM-BAM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2870766
S4TWL - Cash Management - BAM
Symptom
You are doing a system conversion to SAP S/4HANA and you are going to use BAM
(Bank Account Management). The following SAP S/4HANA Transition Worklist for
BAM is applicable in this case.
Solution
Description
Once customers have installed SAP S/4HANA, SAP S/4HANA Finance for 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 available in SAP S/4HANA. An SAP Business Suite customer using classic
Cash and Liquidity Management needs to activate the new SAP S/4HANA Finance for
cash management after converting to SAP S/4HANA.
As part of cash management, BAM (Bank Account Management) offers customers the
capability in maintaining banks and bank accounts, among other relevant features.
Business Value
With BAM, customers are able to:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 317
1. Manage their banks and bank accounts (including house banks and house bank
accounts)
2. Manage their bank account groups and bank hierarchies
3. Control bank account maintenance process via dual control mode or workflow mode
4. Analyze their bank fee data
Comparison of Functional Scope
The following table summarizes the differences in bank account management between
the classic Cash and Liquidity Management and SAP S/4HANA Finance for cash
management.
Classic Cash
and
Liquidity Manag
ement
SAP Cash
Management,
delivered with SAP
S/4HANA 1511
SAP
S/4HANA
Finance
for cash
managem
ent,
delivered
with SAP
S/4HANA
1610
(Delta to
1511)
SAP S/4HANA
Finance for cash
management,
delivered
with SAP
S/4HANA 1709
(Delta to 1610)
SAP S/4HANA
Finance for
cash
management,
delivered
with SAP
S/4HANA
1809 (Delta to
1709)
Banks
/ Bank
Accou
nts
Create Bank:
FI01
Change
Bank:
FI02
Display
Bank:
FI03
House Bank
/ House
Bank
Account:
FI12
Business
Partner
(Role
TR0703):
BP
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
Centralize
d bank
account
manageme
nt is
supported.
Bank
accounts c
an be
replicated
via iDoc to
other
systems
on Simple
Finance
1503,
S/4HANA
Finance
1605+,
S/4HANA
OP 1610+,
With this release,
the following
features have
changed for the app
"Manage Bank
Accounts":
You can now
choose to
implement
a dual
control
process for
bank
account
manageme
nt.
Revisions
are then
saved
whenever
you or any
other users
Bank Account
Management
(BAM):
The
transaction
FI12 has been
reactivated.
You can now
use this
transaction to
manage house
banks and
house bank
accounts.
The use of the
FI12
transaction for
bank accounts
varies
depending on
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 318
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 not available.
Instead, you
use the
following apps
via the Fiori
Launchpad to
manage house
banks and
house bank
accounts:
Define
house
banks:
Use
the Fio
ri
app Ma
nage
Banks
Define
house
bank
accoun
ts: You
can do
so in
the
Fiori
app M
anage
Bank
Accoun
ts by
editing
SAP ERP
6.0 EhP6+.
create,
modify,
copy,
reopen, or
close a
bank
account.
You can
use the
revisions
to:
Ask
ano
the
r
aut
hori
zed
use
r to
acti
vat
e
you
r
revi
sio
n to
gen
era
te a
ne
w
acti
ve
ban
k
acc
oun
t
ver
sio
n
Compa
re
revi
sio
ns
to
ide
ntif
the bank
account
activation
setting in your
system:
If the
“Activa
te
Directl
y”
setting
is set
in your
system
for the
bank
accoun
t
activati
on
mode,
you
can
use
the
FI12
transac
tion to
manag
e bank
accoun
ts.
If you have
implem
ented
workflo
w or
dual
control
proces
ses in
your
system
, you
can
define
bank
accoun
ts in
the
Manag
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 319
the
bank
accoun
t
master
data,
on
the Co
nnectiv
ity
Path ta
b.
House
bank
and
house
bank
accoun
ts
are lon
ger
configu
ration
data,
instead
they
are
maintai
ned as
master
data.
Database table
T012K is
redirected
to the new
BAM tables.
Bank Account
Management Lite
(BAM Lite)*:
Attributes include
account holder,
internal contact
persons, and
house bank
account related
y
diff
ere
nce
s
bet
we
en
diff
ere
nt
ban
k
acc
oun
t
ver
sio
ns○
View
ban
k
acc
oun
t
hist
ory
to
trac
k
acc
oun
t
cha
nge
s
This
process ensures
the 4-eye principle
but is easier to
implement than the
business workflow
approach.
Settings for
bank
statements
have been
added to
bank
account
e Bank
Accou
nts
Fiori
app or
use
the
NWBC
transac
tion to
open
an
HTML
applica
tion.
Bank Account
Management
Lite (BAM
Lite)*:
The
transaction
FI12 has been
reactivated.
You can now
use this
transaction to
manage house
banks, house
bank accounts,
and bank
accounts.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 320
settings on
bank accounts.
No workflow-based
bank account
processes.
The transaction
FI12 House
Bank / House
Bank Account
is not available.
Instead, you
use the
following apps
via the Fiori
Launchpad to
manage house
banks and
house bank
accounts:
Define
house
banks:
Use
the Fio
ri
app Ma
nage
Banks
Define
house
bank
accoun
ts: You
can do
so in
the
Fiori
app M
anage
Bank
Accoun
ts by
editing
the
bank
accoun
t
master
data,
master
data.
A new field for
financial
object
numbers
has been
added and
allows for
integration
with
Treasury
and Risk
Manageme
nt.
The system
automatical
ly
generates a
financial
object
number for
each bank
account.
A new field for
transaction
type is
available
for
processing
this
account's
electronic
bank
statements.
A new way to set
up workflows using
the Fiori app
"Manage Workflows
- For Bank
Accounts":
With this release,
the workflow
functionality for
bank account
management is
redesigned
including a new
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 321
on
the Co
nnectiv
ity
Path ta
b.
House
bank
and
house
bank
accoun
ts
are lon
ger
configu
ration
data,
instead
they
are
maintai
ned as
master
data.
For information on
the differences
between BAM
and BAM Lite,
see SAP note
2165520.
workflow template,
new apps for
processing and
tracking workflow
requests, and a
new app Manage
Workflows - For
Bank Accounts for
making workflow
configurations. With
this app, you can
do the following:
View the
predefined
workflow
for
maintaining
bank
accounts
Check workflow
details,
such as
status,
validity
period, and
preconditio
ns for
starting the
workflow
Create new
workflows
by copying
existing
ones
You can
define
workflow
processes
for bank
account
manageme
nt
according
to your own
business
requiremen
ts by
defining
preconditio
ns, step
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 322
sequence,
and
recipients.
Activate and
deactivate
workflows
Define an order
for
activated
workflows
The system
evaluates
the order
and the
preconditio
ns of each
activated
workflow to
determine
which
workflow to
trigger for
different
bank
accounts
and
scenarios.
Delete an
existing
workflow
that is
deactivated
*Bank Account Management Lite (BAM Lite): A basic version of Bank Account
Management which is part of the basic cash managment capability. It is provided for
customers who do not have the license of SAP S/4HANA Finance for cash management.
For more information about the scope differences between the basic cash management
capability and SAP S/4HANA Finance for cash management, see the help document.
Required and Recommended Actions
Prior to SAP S/4HANA 1809, the old transactions of maintaining house bank
accounts are not available. Instead, you manage your house bank accounts in the
new bank account master data, using either the basic cash management capability
or the full scope of Bank Account Management (with SAP S/4HANA Finance for
cash management). As a result, before you go live with SAP S/4HANA, you must
migrate house bank accounts if there are any. For more information about the
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 323
migration activity, in the Configuration Guide, select your software version and
then search for "Migration of House Bank Accounts".
All the apps must be accessed from the Fiori Launchpad.
Customers who have been using the full scope of cash management and are
converting to SAP S/4HANA 1610 from Simple Finance 1503, S/4HANA
Finance 1605 and S/4HANA OP 1511, must configure the customizing
activity Define Basic Settings under "Financial Supply Chain Management"-
>"Cash and Liquidity Management"->"General Settings".
11.4 S4TWL - CASH MANAGEMENT - Memo Record
Application Components:FIN-FSCM-CLM-COP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2781585
Cash Management: Memo Records in
SAP S/4HANA 1809
Symptom
Your system has been upgraded to SAP S/4HANA 1809, where the memo record
functionality has changed in many aspects. You want to understand the changes and the
impact.
Solution
Description
This note aims to provide you an overview about the changes and impacts on your
existing data and configuration settings of memo records in S/4HANA 1809.
Business Value
In SAP S/4HANA 1809, a Fiori APP Manage Memo Records (Fiori ID: F2986) is
available for memo records. With this app, you can create memo records centrally for
expected cash flows that are not yet generated in the system. The memo records are then
displayed in the cash management apps, such as Cash Flow Analyzer and Check Cash
Flow Items. You can also use this app to view, change, and delete the intraday memo
records that are generated automatically from imported intraday bank statements.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 324
Data Storage Change
In S/4HANA 1809, memo records are no longer stored in table FDES. Instead, it is now
stored in One Exposure from Operations (table FQM_FLOW).
To migrate memo records that are stored in the FDES table, proceed as follows:
1. Run transaction SE38.
2. Execute report FCLM_MIGR_FDES2FQM to migrate the existing memo records from
table FDES to table FQM_FLOW.
Number Range
In S/4HANA 1809, all memo records are numbered by order, regardless the company
code. Consequently, the number range setting on company codes is no longer relevant to
memo records
To enable the new number range mechanism:
Run transaction SNRO
Enter object FCLM_MRN
Enter number range 01
Bank Account
In the Fiori app Manage Memo Records, Cash Management Accounts are no longer
required. This is because you can create memo records only for active bank accounts.
And it would be reflected on cash reports accordingly.
The concept is kept as it is for transaction FF63 and FF65.
Planning Level
With Fiori app Manage Memo Records, Planning Types mapping with Planning Levels
would not be mandatory any more.
Since planning levels are all supported with new memo records, in the classic cash report
FF7AN/FF7BN, FI flows could not be differentiated from memo records through
planning level any more, and drill-down to each memo record is not supported.
There’s no change for FF63 and FF65.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 325
Snapshot
The snapshot feature, available with the Full Cash scope, would also be effective towards
the memo record data in the Cash Flow Analyzer. For more information about the
snapshot setting, see the Implementation Guide of the Customizing activity Define Basic
Settings.
To enable Snapshot feature, go to IMG ->Financial Supply Chain Management > Cash
and Liquidity Management > General Settings->Define Basic Settings->Enable Snapshot
Expiration memo record from intraday bank statement
S/4HANA 1809 introduces a new logic of expiration memo record from intraday bank
statement: see note 2719289 for more details.
Fields in table FDES that are no longer supported in S/4HANA 1809
Field Name
Field Label
DSART
Planning Type
ZUONR
Assignment
REFER
Reference
VOART
Transaction Type
SDATM
Start Date
ZINSS
Interest Rate
KLART
Calendar Type
Custom field extension
The custom fields that were added by
customers are not supported from S/4HANA
1809
Required and Recommended Actions
To use the new memo records, make sure the following settings are properly defined in
your system.
You have activated the source application One Exposure (FI) for relevant
company codes in the Activate Individual Source Applications or the Activate
Multiple Source Applications Customizing activity. You can find these
Customizing activities in Customizing under Financial Supply Chain
Management > Cash and Liquidity Management > Cash Management > Data
Setup -> Activate Individual Source Applications.
You have defined a planning level for memo records in the Define Planning Levels
Customizing activity. You can find this Customizing activity in Customizing
under Financial Supply Chain Management Cash and Liquidity Management
Cash Management Planning Levels and Planning Groups.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 326
Other Terms
Memo Records, FDES, Planning Type, Memo Records Migration
11.5 S4TWL - Logic changes in Flow Builder
Application Components:FIN-FSCM-CLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3249131
Simplification Item S4TWL - Flow
Builder
Symptom
You execute a system conversion to S/4HANA, On-Premise-Edition 2022 or higher.
Reason and Prerequisites
You use at least one of the following Fiori apps:
Short-Term Cash Positioning
Cash Flow Analyzer
Check Cash Flow Items
Bank Account Balance
Cash Position
Solution
Business Value
Flow Builder Plus is a module to generate cash flow items from Accounting (FI) and MM
source applications.
Flow Builder Plus will provide these benefits comparing with old Flow Builder or we call
it Flow Builder 1.0:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 327
Get liquidity analysis result immediately together with cash position or separately
with time deferral
Support more business scenarios
Analyze liquidity analysis document chain with traceability
Gain improvement on performance and solve out of memory issue
Enable parallel runs for Flow Builder and embed the ‘Packaging’ concept
Update less volume of cash flows by comparing with the existing flows especially
enabling the Snapshot function
Utilize flexible extensibility
Simplify and less implementation efforts for upgrade
Keep updated for continuous innovations on Flow Builder
Description
From OP2021 FPS1, Flow Builder Plus is an option for you to generate cash flow items
for Accounting (FI) and MM source applications.
From OP2022, once your upgrade is finished, Flow Builder Plus is mandatory if you still
need to populate cash flow items from cash and liquidity management.
Business Process Related Information
Cash flow analysis by liquidity item could be more accurate, for example, even if the
actual outgoing payment is netted from Account Payable and Account Receivable, the
liquidity item derivation can reveal as if it was not netted and retrieve the separated
liquidity items for Account Payable and Account Receivable on corresponding split
amounts.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 328
Before using Flow Builder Plus, we suggest you review your business requirements,
because now there’s more flexibility and you can decide on which level you want to use
it. For example, if you only need cash position information, you could do the
configuration accordingly, therefore you could skip the whole set of liquidity analysis
process to simplify the configuration as well as faster runtime response.
Please take notes below two new tables:
Table FQMC_ACT_FI introduced but only available to Advanced Cash user. And no
default content shall be applied.
Table FCLM_FB2_CONFIG introduced without default content.
Learning the key configuration steps with our help document online and reading the
mentioned notes below is primary, based on our experience, the preparation for testing is
the most time-consuming part, but setting up the needed configurations is not that
complicated. For example, if you understand your requirements, it just take hours to
configurate the system for upgrading customers, but it may take weeks to test and
confirm the expected result.
Because we change the pairing logic in Flow Builder Plus, you have to confirm if your
business department could accept the change in most cases. The result of derived
liquidity items is the same for most cases, however, still could see different result due to
new pairing algorithm in Flow Builder Plus, for example, in Flow Builder Plus we
separate cashflow items for customer and vendor though they are the same business
partner for your client, we will not net them on your behalf.
If your end user is not using Flow Builder manually, you just need to train them on the
new concept of "cash position cash flow" and "liquidity analysis cash flow", then they
could understand the figures in related cash reports or cash apps.
If your end user also has to run Flow Builder manually, some basic trainings are still
needed here to let him/her know the updated UI.
If you have your own extensions in Flow Builder 1.0, you have to review them carefully.
We suggest you using the new enhancement points.
Liquidity Analysis for all customers is individual and there are individual needs. Flow
Builder Plus provides you with several options to adopt the behavior.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 329
Enhancement Point FCLM_FB2_EXT
This enhancement provides the following interfaces:
DOC_FKONT_EXT
This interface is to adjust FKONT of a document item in the offsetting document.
FKONT of an item affects how the item would be paired to other items in a document
and how account assignments are replaced in chain tracing. The interface provides the
document keys and the document item keys together with amounts and flow type (also
flow level), as well as the FKONT decided by default.
CLR_FKONT_EXT
This interface is to adjust FKONT of a document item in offsetting clearing. FKONT of
an item affects how the item would be paired to other items in a clearing relationship and
how account assignments are replaced in chain tracing. The interface provides the
clearing information together with account information, and the document item keys
together with amounts and flow type (also flow level), as well as the FKONT decided by
default.
DOC_LR_EXT
This interface is to adjust pairing side of a document item in offsetting document. It
directly decides how the item would be paired to other items in a document, overwriting
the default decision by FKONT. The interface provides the document keys and the
document item keys together with amounts and flow type (also flow level), as well as the
side (value ‘L’ or ‘R’) decided by default.
CLR_LR_EXT
This interface is to adjust pairing side of a document item in offsetting clearing. It
directly decides how the item would be paired to other items in a clearing relationship,
overwriting the default decision by FKONT. The interface provides the clearing
information together with account information, and the document item keys together with
amounts and flow type (also flow level), as well as the side (value ‘L’ or ‘R’) decided by
default.
FINAL_DECISION_EXT
This interface is to adjust the decision whether a flow has been completely built in Flow
Builder Plus. The interface provides the original item and offset item of a flow together
with FKONTs on both sides and the current split amounts, as well as the final flag
decided by default. You can change the final flag if you think the flow tracing should
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 330
stop or go further. Final flag is the only field which could be modified. Changing the item
keys would possibly cause flow lost.
Enhancement Point ES_FQM_FLOW_ADJUST_CORE
This enhancement is reused for all the source applications considered in One Exposure.
You can adjust all aspects of the resulting flows to your needs. Validation is applied
afterwards. The origin reference together with origin flow ID must be unique; origin
transaction must not be created; and company code must not be changed.
Please refer to Note 3111810 Optimized Data Model and Algorithm: Technical Setup
Guide for necessary technical setup after you switched on Optimized Data Model and
Algorithm.
Please refer to Note 3144000 - SAP S/4HANA Finance, On-Premise Edition 2021:
Troubleshooting Note for Flow Builder Plus for the FAQ of Flow Builder Plus.
Please refer to Note 3128064 - Flow Builder: Technical Changes in S4CORE version 106
Please refer to Note 3211170 - Logic changes in Flow Builder
How to Determine Relevancy
You use at least one of the following Fiori apps:
Short-Term Cash Positioning
Cash Flow Analyzer
Check Cash Flow Items
Bank Account Balance
Cash Position
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 331
Other Terms
Flow Builder
Flow Builder Plus
11.6 S4TWL - Fiori app Adjust Assigned Liquidity Items deprecated
Application Components:FIN-FSCM-CLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3227455
S4TWL - 'Adjust Assigned Liquidity
Items' Fiori app has been deprecated
since S/4HANA on-premise 2022
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise 2022 edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The Fiori application 'Adjust Assigned Liquidity Items' has been deprecated since
S/4HANA on-premise 2022.
Business Process related information
There is currently no successor application available.
Required and Recommended Action(s)
Inform your business users.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 332
This Simplification Item is relevant if you have the 'Adjust Assigned Liquidity Items'
Fiori application in use.
Other Terms
SAP S/4HANA, Upgrade
11.7 S4TWL - End-of-Day Memo Record Reconciliation
Application Components:FIN-FSCM-CLM-COP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3351947
S4TWL - End-of-Day Memo Record
Reconciliation
Symptom
You are doing a system conversion to SAP S/4HANA 2023. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
App and transaction in the SAP S/4HANA solution for EoD memo record reconciliation
are deprecated as of SAP S/4HANA 2023.
Currently there is no successor application available.
Business Process related information
The following objects have been deprecated:
Fiori App ID/Transaction Code
Description
F4867
Reconcile Cash Flows - Memo Records
FCLM_CR_MMRD
Reconcile End-of-Day Memo Records
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 333
Required and Recommended Action(s)
Inform your business users.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you are using one or more of the
deprecated objects that are listed above.
Other Terms
SAP S/4HANA, Upgrade, F4867, FCLM_CR_MMRD
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 334
12.Financials – Controlling
12.1 S4TWL - Reference and Simulation Costing
Application Components:CO-PC-PCP-REF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349294
S4TWL - Reference and Simulation
Costing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
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.
Task: Check, if base planning objects are used in the customer system.
Procedure: Call transaction se16 and select CKHS. On the selection screen you have to
enter BZOBJ ='1' and use action 'Number of Entries' to determine the number of base
planning objects.
Rating:
Simplification item and note is not relevant for the customer, if no CKHS entries exists
with BZOBJ = '1'.
Solution
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 335
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.
Transaction not available in SAP S/4HANA on-premise edition 1511
Transaction Code
Create Base Planning Object
KKE1
Change Base Planning Object
KKE2
Display Base Planning Object
KKE3
Revaluate Base Planning Object
KKEB
Base Planning Object vs. Other Unit Cost Estimate
KKEC
Costed Multilevel BOM (only Base Planning Object Exploded)
KKED
Itemization
KKB4
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.
Other Terms
Base Planning Object
12.2 S4TWL - Summarization Hierarchies in Controlling
Application Components:CO-PC-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349282
S4TWL - Summarization Hierarchies in
Controlling
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case. In existing systems
you can identify the use of summarization hierarchies by the fact that there are object
numbers beginning with VD in tables COSP and COSS and entries for the hierarchy
structure exist in View V_TKKR0_OR_NEW.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 336
Reason and Prerequisites
Description
You are currently using summarization hierarchies, order hierarchies, or project
hierarchies and want to understand the impact of moving to SAP S/4HANA.
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 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.
Solution
Business Process related information
Transaction KKRC and KKBC_HOE are typically executed at period close since they
require the pre-calculation 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.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 337
Order Hierarchy, Project Hierarchy
12.3 S4TWL- Legacy MDI Cost Center Replication
Application Components:FI-GL-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3247070
S4TWL – Legacy MDI Cost Center
Replication
Symptom
You are doing a system upgrade to SAP S/4HANA 2022 or higher and use the legacy
MDI cost center replication. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Reason and Prerequisites
The legacy MDI cost center replication is only available in SAP S/4HANA releases from
2020 until 2023. Fore more information regarding the legacy MDI Cost Center
Replication please check the SAP Help documentation. Afterwards it is not possible to
use this old functionality anymore.
Solution
Before upgrading to SAP S/4HANA 2022 or higher, check whether the functionality is
used or not. If not, there are no further actions. If yes, a migration to the new model is
recommended and mandatory with SAP S/4HANA release 2023 at the latest. See SAP
Note 3232417.
How to Determine Relevancy
This Simplification Item is relevant if you have entries in table DRFC_APPL_SYS, field
OUTB_IMPL = FI_CO_CCTR. You can check if the replication model is active in table
DRFC_APPL
Other Terms
MDI, Cost Center Replication, FI_CO_CCTR
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 338
12.4 S4TWL - Technical Changes in Material Ledger with Actual Costing
Application Components:FIN-MIG-ML, CO-PC-ACT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2354768
S4TWL - Technical Changes in Material
Ledger with Actual Costing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition, higher or
equal to on-premise 1610. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Reason and Prerequisites
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)
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 339
In addition, the table T001W shows the link between the plant and the valuation area.
Solution
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)
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. For further details regarding this matter please see
description in SAP Support Note 2267835. With SAP S/4HANA, on-premise
edition 1610, this option also includes materials with Moving Average price
control and all special stock types. Additional details can be found in SAP
Support Note 2338387.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 340
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 '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. You can create new costing runs for previous periods or for
the current period, after data conversion in the new system, but it is important to
have no incomplete costing runs, where just some steps have been started. This
means, if you are doing a conversion in an open period (e.g. in the middle of a
month), do not start a costing run in the old system on the old release, for this
open period. You can create the costing run for this period later, after system
conversion in the new system.
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
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 341
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 (But the values to Price
Type 'B')
The design of tables MLDOC/ MLDOCCCS allows storing both line item and
aggregated data.
Periodic transactions (goods movements, activity confirmation, etc.) update
tables MLDOC/ MLDOCCCS with line item data using the INSERT
ONLY principle.
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.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 342
Tables MLDOC_EXTRACT and MLDOCCCS_EXTRACT
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 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
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 year before 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 year before previous year. The data of
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 343
the current year and of the previous 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 category
(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. This behavior can be enhanced by implementing
SAP Support Note 2467398 (further details are described within this note)
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
Remark: Data older than last period of year before previous year (related to current
period in the system for a specific company code, at 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 year before previous year
you can use transaction CKM3OLD('Material Price Analysis') or CKM3PHOLD
('Material Price History'). To display single material ledger documents, created before
system conversion, you can also use transaction CKM3OLD. The system conversion will
not convert single material ledger documents, but there will be one entry per category,
process category and procurement alternative/process, with aggregated quantities,
amounts and price/currency differences of single material ledger documents. So CKM3
will show data also on this level for migrated data.
CKM3 will show all details on single material ledger documents for postings created
after system conversion.
CKM3OLD will not show postings created after system conversion
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 344
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:
Create a “Classic AVR” which is the same like before.
Create an AVR with run reference which means the settings are taken from
the run reference and can’t 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:
Selection (program FCML4H_SELECTION)
Preparation (program FCML4H_PREPROCESSOR)
Settlement (program FCML4H_SETTLEMENT)
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”.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 345
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
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):
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’.
The former step Cumulate Data is no longer needed
The complex rescale logic, which adjusts all materials data to a common
preliminary AVR price, is no longer needed.
All AVR can now handle WIP
Post Closing:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 346
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
The BAdI BADI_ENDING_INV for external valuation is currently not available.
Static external valuation (for ending inventory or cumulated inventory) based on
table CKMLPR_EB is available with note 2613656
The BAdI CKMLAVR_SIM has been replaced by the
BAdI FCML4H_MODIFY_VALUES. For more information refer to the
following note:
2876478 Documentation for BAdI FCML4H_MODIFY_VALUES
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 available
after implementing the following notes (, or related support package):
2378468 Enable CKMLQS based on table MLDOC
2495950 CKMLQS: Connection to CKM3
Other Terms
ML, Actual Costing, CKM3, CKMLCP, CKMLCPAVR, MLDOC, MLDOC_CCS,
MLAST, T001W, MGVUPD, plant, WERKS_D, BWKEY, CKMLQS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 347
12.5 S4TWL - Material Ledger: deprecated table for currency and valuation
types
Application Components:CO-PC-ML
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3017994
S4TWL -Material Ledger: deprecated
table for currency and valuation types
Symptom
You are doing a system upgrade or conversion to SAP S/4HANA 2021. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
The custom code check shows customer objects affected by simplifications.
SAP objects used by the customer objects have become obsolete.
Reason and Prerequisites
Renovation
SAP table CKMLCT (Currency Types and Valuation Types in a Valuation Area) has
become obsolete with SAP S/4HANA 2021.
This note contains detailed descriptions about how to adopt customer objects to the data
model change.
Solution
Required and Recommended Action(s)
Please run the ATC custom code check for simplification item S4TWL - Material Ledger: deprecated
table for currency and valuation types.
If the custom code check returns affected objects, please replace all usages of table CKMLCT with
view FMLV_CKMLCT. The view FMLV_CKMLCT has the same structure like table CKMLCT.
With S/4HANA the posting amounts of Material Ledger and General Ledger are always in sync.
Therefore the fields ADJUST_FLAG (Currency Type Reconc), ADJUST_VERS (SAP Release),
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 348
ADJUST_DATE (Reconcil. Date) and ADJUST_USER ( User Who Performed the Reconciliation)
are not needed anymore. The view FMLV_CKMLCT returns initial values for this fields.
Other Terms
Worklist
CKMLCT
Currency Types and Valuation Types in a Valuation Area
12.6 S4TWL - EC-PCA - Classical profit center accounting
Application Components:EC-PCA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2993220
S4TWL - EC-PCA - Classical profit
center accounting
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Classical Profit Center Accounting (PCA) is part of the SAP S/4HANA compatibility
scope, which comes with limited usage rights. For more details on the compatibility
scope and it’s expiry date and links to further information please refer to SAP note
2269324. In the compatibility matrix attached to SAP note 2269324, Classical Profit
Center Accounting can be found under the ID 427.
This means that you need to migrate from Classical Profit Center Accounting to its
designated alternative functionality "Profit Center Accounting on Universal Journal" in
SAP S/4HANA before expiry of the compatibility pack license. This note shall provide
information on what to do to move to the alternative functionality.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 349
Classic PCA in SAP S/4HANA is active if the active indicator is set in transaction 0KE5
(field PCRCH for the corresponding controlling area in the table TKA00 is set to '2')
and the online posting of data records in the tables (GLPCA = actual line items table,
GLPCT = totals table, GLPCP = plan line items table) has been activated using
transaction 1KEF.
A description of the functionality in compatibility scope you find in the SAP S/4HANA
Feature Scope Description in section Profit Center Accounting (EC-PCA).
Required and Recommended Action(s)
Refer to SAP note 2425255 - Profit Center Accounting in the universal journal in SAP
S/4HANA, on-premise edition for a description of
how PCA is mapped in the context of SAP S/4HANA and
to what extent classical PCA can be used in parallel with SAP S/4HANA.
what changes if classical PCA is deactivated in SAP S/4HANA
In the following you find important aspects relevant for a switch from classical Profit
Center Accounting to Profit Center Accounting on Universal Journal. For details refer to
SAP note 2425255.
In SAP S/4HANA, PCA is mapped in the universal journal by default. This means, if
you still use classical PCA, Profit Center Accounting in the universal journal is
also always active in parallel. To stop using classical PCA you have to deactivate
it as described in note 2425255.
It is not necessary to migrate data from classic PCA (tables GLPCA/GLPCP/GLPCT)
to the universal journal, that is, to the table ACDOCA, when deactivating
classical PCA.
The existing authorization objects are still available and valid.
The libraries for classic PCA in Report Writer are part of the compatibility scope and
are available only for a limited period of time as well. Refer also to compatibility
scope ID 433 "Report Writer / Report Painter in Finance and Controlling". As
explained in note 2425255 you can use the report FAGL_RMIGR to change the
data source of your existing reports.
The planning transactions for classic PCA are part of the compatibility scope and are
avaliable only for a limited period of time. If you want to use classical planning
transactions, please use transactions GP12N, GP12NA, FAGLP03 (plan data
entry in FI, including profit center) , together with the plan assessment cycles
(FAGLGA4* transactions) and plan distribution cycles (FAGLGA2*
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 350
transactions) instead. Refer also to simplification item SI2_FIN_CO and
note 2270407 - S4TWL - Profit and Loss Planning, profit center planning, cost
center planning, order planning, and project planning.
A migration of allocations from classic Profit Center Accounting to the universal
journal is not possible.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Profit Center Accounting, ID 427
12.7 S4TWL - Changes in EBRR backend transactions
Application Components:CO-PC-OBJ-EBR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3226957
S4TWL - Changes in EBRR backend
transactions
Symptom
You are doing an upgrade from a lower to a higher SAP S/4HANA release and are using
a transaction, or report described in this note. The following
SAP S/4HANA Simplification Item is applicable in this case.
This note describes changes of backend transactions and the Fiori application portfolio of
Event-Based Revenue Recognition with SAP S/4HANA 2022.
Reason and Prerequisites
Renovation
Solution
Following transactions and reports are deprecated as of release SAP S/4HANA 2022.
This means, these transactions and reports are still available and supported but no new
features or enhancements can be expected. We plan to make them obsolete in favor of the
designated successor functionality as of release SAP S/4HANA 2023.
GUI transactions:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 351
REV_REC_COL_PRO (Event-Based Revenue Recognition: Projects/WBS
Elements)
REV_REC_COL_PRO_RSP (Event-Based Revenue Recognition: Re-evaluate
Projects)
REV_REC_COL_SD (Event-Based Revenue Recognition: Sales Documents/SD
Items)
REV_REC_COL_SVD (Event-Based Revenue Recognition: Service Document
Items)
REV_REC_PEC_RV_SD (Reverse Revenue Recognition)
Reports:
FINS_TRR_COLACT_PRO (Event-Based Revenue Recognition: Projects/WBS
Elements)
FINS_TRR_COLACT_PROBG (Event-Based Revenue Recognition: Projects/WBS
Elements)
FINS_TRR_COLACT_PRO_LOGBG (Event-Based Revenue Recgn: Re-evaluate Projects from
Log)
FINS_TRR_COLACT_PRO_RSP (Event-Based Revenue Recognition: Re-evaluate Projects)
FINS_TRR_COLACT_SD (Event-Based Revenue Recognition: Sales Documents/SD
Items)
FINS_TRR_COLACT_SDBG (Event-Based Revenue Recognition: Sales Documents/SD
Items)
FINS_TRR_COLACT_SVD (Event-Based Revenue Recognition: Service Document
Items)
FINS_TRR_COLACT_SVDBG (Event-Based Revenue Recognition: Service Document
Items)
FINS_TRR_REEVAL_REVERSE (Reverse Reevaluation Documents from EBRR)
Business Process related information
Link to Help Portal documentation:
Event-Based Revenue Recognition for Projects
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 352
Event-Based Revenue Recognition for Sales Orders
Event-Based Revenue Recognition for Service Documents
Reverse Revenue Recognition
Required and Recommended Action(s)
Based on your preferences, we recommend you switch to the following successor
transactions or fiori applications.
Deprecated Transactions and Reports
Successor Transactions and Fiori
applications
Transactions
REV_REC_COL_PRO
REV_REC_COL_PRO_RSP
Reports
FINS_TRR_COLACT_PRO
FINS_TRR_COLACT_PROBG
FINS_TRR_COLACT_PRO_LOGBG
FINS_TRR_COLACT_PRO_RSP
Transactions (Starting with S/4HANA 2022)
REV_REC_PEC_RT (Manage Real-Time
Revn. Recgn. Issues)
REV_REC_PEC_PROJ (Run Revenue
Recognition – Projects)
Fiori applications (available with Sales
Accountant role -
SAP_BR_SALES_ACCOUNTANT)
F4767 Event-Based Revenue Recognition
- Projects
F4101 Manage Real-Time Revenue
Recognition Issues
F4100 Manage Revenue Recognition
Issues - Projects
F4277 Run Revenue Recognition -
Projects
Transaction
REV_REC_COL_SD
Reports
FINS_TRR_COLACT_SD
FINS_TRR_COLACT_SDBG
Transactions (Starting with S/4HANA 2022)
REV_REC_PEC_RT (Manage Real-Time
Revn. Recgn. Issues)
REV_REC_PEC_SD (Run Revenue
Recognition – Sales Orders)
Fiori applications (available with Sales
Accountant role -
SAP_BR_SALES_ACCOUNTANT)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 353
F2441 Event-Based Revenue Recognition
- Sales Orders
F4101 Manage Real-Time Revenue
Recognition Issues
F4185 Manage Revenue Recognition
Issues - Sales Orders
F4276 Run Revenue Recognition - Sales
Orders
Transaction
REV_REC_COL_SVD
Reports
FINS_TRR_COLACT_SVD
FINS_TRR_COLACT_SVDBG
Transactions (Starting with S/4HANA 2022)
REV_REC_PEC_RT (Manage Real-Time
Revn. Recgn. Issues)
REV_REC_PEC_SVD (Run Revenue
Recognition – Service Documents)
Fiori applications (available with Sales
Accountant role -
SAP_BR_SALES_ACCOUNTANT)
F6007 Event-Based Revenue Recognition
- Service Documents
F4101 Manage Real-Time Revenue
Recognition Issues
F4186 Manage Revenue Recognition
Issues - Service Documents
F4278 Run Revenue Recognition - Service
Documents
Transaction
REV_REC_PEC_RV_SD
Report
FINS_TRR_REEVAL_REVERSE
Transactions (Starting with S/4HANA 2022)
REV_REC_PEC_RV (Reverse Revenue
Recognition)
Fiori applications (available with Sales
Accountant role -
SAP_BR_SALES_ACCOUNTANT)
F6638 Reverse Revenue Recognition
Other Terms
SAP S/4HANA, Upgrade, deprecation
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 354
12.8 S4TWL - TECHNICAL CHANGES IN CONTROLLING
Application Components:CO-PC, CO-PA, CO-OM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270404
S4TWL - Technical Changes in
Controlling
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is relevant if you are doing a conversion from ERP ECC 6.0 (EHP 7 or
higher) to S/4 HANA.
Solution
Business Value
In SAP S/4 HANA the totals records for primary and secondary costs have been removed
and the universal journal includes all actual cost postings, both primary and secondary.
This ensures for primary postings that there is a single source of truth, such that all
general ledger items with an assignment to cost centers, orders, WBS elements,
business processes, or CO-PA characteristics are treated as one data record which
is enriched with the relevant profit center, functional area, segment, and so on.
Since Financial Accounting and Controlling will always be in synch, the company
code is checked during all postings to an account assignment in Controlling and
that it is no longer possible to remove the flag "CoCd Validation" in the
controlling area.
For secondary postings this ensures that all sender-receiver relationships that are
triggered by allocations, settlement, and so on are captured in the universal
journal along with the partner profit centers, functional areas, and so on that are
affected by the allocation.
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 355
Actual Items:
Actual data of COEP (WRTTP = ‘04’) is now stored in ACDOCA.
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, that aggregate the data in the universal journal on the fly in
accordance with the old table structures.
CO standard transactions are adapted in a stepwise manner to access the new universal
journal table (ACDOCA) directly instead of using compatibility views. The conversion
process is ongoing.
From a business point of view, all classic transactions are still running - based on
compatibility views or using direct acces to ACDOCA.
The goal of the compatibility views is to provide a bridge to the new data model. Using
these views may have a performance impact on existing reports and you are
recommended to investigate whether the new Fiori reports meet your business needs.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 356
Related SAP Notes
2185026
Compatibility views COSP, COSS, COEP, COVP: How do you
optimize their use.
Notes linked in 2185026
Other Terms
SAP_FIN, S4CORE
12.9 S4TWL - PROFIT AND LOSS PLANNING AND PROFIT CENTER
PLANNING
Application Components:CO-OM, FI-GL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270407
S4TWL - Profit and Loss Planning,
profit center planning, cost center
planning, order planning, and project
planning
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This Simplification Item is relevant if:
Classic Profit Center Planning is used if entries exist in Table GLPCP (check with
SE16).
CO-OM Planning is used if entries exist in Table COEJ (check with SE16).
P&L Planning is used: Use ST03N (on the production system, if possible) to check
transaction profile of the complete last month, whether the following transactions
have been used: FSE5N, FSE6N, FAGLPLSET, GP12N, GP12NA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 357
Production/process order planning is used if planned cost calculation is active for the
combination of plant and order type and is carried out automatically when the
production order (CO01 or CO02) or the process order (COR1 or COR2) is
created, changed or released.Use Customizing T-codes COR4 and OPL8 to check
whether plan costs are determined for production order and process orders.
Solution
Business Value
The universal journal is the unifying element for Accounting. From SAP S/4HANA 1610
it is possible to store the results of planning in a new table, ACDOCP, that has the same
structure as the universal journal (ACDOCA). The same unifying approach is taken in
planning, meaning that wages and salaries planned on a cost center are automatically
assigned to the correct profit centers, functional areas, company codes, and so on and
targets set by profit center can automatically be broken down to the assigned cost objects.
In many organizations planning tasks had been moved to a data warehouse on account of
the lack of flexibility in the ERP tables. This flexibility is now achieved by using SAP
Analytics Cloud for Planning. This holds true for S/4HANA On-Premise and S/4HANA
Cloud. Master data and transactional data can be sourced from SAP S/4HANA to SAP
Analytics Cloud. In SAP Analytics Cloud pre-defined business content for Integrated
Financial Planning can be leveraged as a project foundation. The business content is
aligned to structures in S/4HANA and enables the E2E planning process.
Description
CO-OM planning, P&L planning, and profit center planning are now covered by SAP
Analytics Cloud for S/4HANA Finance. If you do not want to use SAP Analytics Cloud
with S/4HANA On-Premise, but classic FI-GL and CO-OM planning functions instead,
you can continue to use the classic planning transactions. 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, so the planned data will only be visible in Report
Writer/Painter transactions.
FI-GL Planning - SAP Note 2253067 describes how to reactivate
Profit Center Planning (classic) - SAP Notes 2345118 and 2313341 describe how to
reactivate
Cost Center Planning by Cost Element - no longer in menu but can be used in SAP
S/4 HANA
Order Planning by Cost Element - no longer in menu but can be used in SAP S/4
HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 358
Project Planning by Cost Element - no longer in menu but can be used in SAP S/4
HANA
Project Planning Overall - no longer in menu but can be used in SAP S/4 HANA
Customer project requires to import business content “Integrated Financial Planning for
S/4HANA” from SAP Analytics Cloud content network and adapt the delivered objects
to customer needs. Customers preferring to delay such a project can reactivate the classic
planning transactions using the SAP Notes described above. Note that classic profit
center planning is part of the compatibility scope and usage rights will expire in future.
Note that it is also possible to run the two solutions in parallel, however this should only
be taken into account to support a transition to ACDOCP with SAP Analytics Cloud.
Running two solutions in parallel, either classic CO planning with SAP BPC for
S/4HANA Finance or with SAP Analytics Cloud is not the strategic direction of SAP.
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.
Transaction KEPM (Profitability Planning) supports both account-based CO-PA within
the universal journal and costing-based CO-PA and is still in the menu. The investment
planning and budgeting transactions are still in the menu and supported. As an alternative
to transaction KEPM, you can now use the new planning applications in SAP BPC for
market segment planning (amounts by market segment - available from 1511), sales
planning (quantities and prices by market segment - available from 1610) and product
cost simulation (valuation of sales quantities using product cost estimate - available from
1610).
Planning data is also created automatically when production/process orders are saved or
released. This planned data currently updates both table CKIS and COSP/COSS and the
new planning table, ACDOCP. The new table stores two types of planned values for the
production order: the planned costs (as in CKIS) and the standard costs adjusted for the
order lot size (previously only accessed during target cost calculation). The two types of
planned values are assigned to plan categories (PLANORD01:Production order plan costs
and PLANORD02:production order standard costs) and provide the basis for target cost
calculation in the SAP Fiori apps Production Cost Analysis and Analyze Costs by Work
Center/Operation.
Business Process related information
To start with Integrated Financial Planning for S/4HANA the business content needs to
be imported to SAP Analytics Cloud. See SAP Note 2977560 for more details.
Implications:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 359
Customer roles (menus and authorizations) may need to be adapted.
Decision needed as to when plan/actual reporting will be based on Universal Journal
or take place in Integrated Financial Planning content in SAP Analytics Cloud.
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
or order budgeting )
Decision needed as to whether order and project planning is required for reporting
and budgeting purposes in Investment Management
Implications : SAP Analytics Cloud needs to be set up and configured.
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:
SAP BPC is not the strategic planning solution anymore. If an on-premise planning
solution is a must, SAP BPC is a comprehensive and mature option. Anyhow this
should only be considered as an intermediate step towards a transformation to
SAP Analytics Cloud. Please check end-of-maintenance dates prior to any new
BPC project.
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 Fiori apps.
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
or order 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.
If you are intending to implement project planning, please ensure that there is a
master data status in place to prevent changes to the WBS number (business
transaction: Change WBS number) once planned data has been entered, since the
content delivered for project planning (/ERP/PROJECT and /ERP/WBSELMT)
uses a view to read the business definition of the project definition and WBS
element rather than the internal ID. If the WBS number is changed, you will lose
the link to the associated planned data. Please refer to the following SAP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 360
knowledge base article for further details.
https://launchpad.support.sap.com/#/notes/2162222
If you currently calculate planned costs for production orders, no business process
changes are required, but be aware that the information in the new planning table
is only visible in Fiori apps, such as Production Cost Analysis and Analyze Costs
by Work Center/Operation. The information shown in the SAPGUI transactions
(CO01-3, COR1-3 and KKBC_ORD) is based on the old tables so you will not
see costs by work center or operation in these transactions even though the
additional detail is stored in the ACDOCP table.
Transactions which
have been removed
from the menu in SAP
S/4HANA on-premise
edition 1511
GP12N, GP12NA, FAGLP03 (plan data entry in FI) plus plan
assessment cycles (FAGLGA4* transactions) and plan distribution
cycles (FAGLGA2* transactions) - can be reactivated using SAP Note
2253067.
CJ40/CJ42 (overall planning on projects) KP06/KP07 (cost centre
planning), CJR2/CJR3 (project planning) and KPF6/KPF7 (order
planning) - femoved from menu but can still be used.
7KE1-6 and 7KEP (profit center planning), IKE0 (transfer CO-OM plan
to profit center plan) - part of compatability scope
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
Analytics Cloud or SAP BPC for S/4HANA Finance.
No changes to existing tables, but table ACDOCP offered in addition from 1610.
Follow steps in attachment provided with SAP Note 2661581 to set up plan
categories. During system installation, upgrade, the pre-delivered table entries are
only imported into client 000. For new client, the table entries can be copied to a
new client during client copy automatically. But for existing client before the
upgrade, the table entries should be imported into the target client manually.
Activate business content for Integrated Financial Planning in SAP Analytics Cloud.
Related SAP Notes
Conversion Pre-Checks
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 361
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.
Related SAP Notes
SAP Note: 2081400, 1972819
Other Terms
ACDOCP
12.10S4TWL - ACTIVITY-BASED COSTING
Application Components:CO-OM-ABC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270408
S4TWL - Activity-Based Costing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
In the conversion check, you get an error message FI_GL_08: CO-version XXXX/YYYY
is an ABC delta version and not usable in S/4.
Reason and Prerequisites
Task: Check if "Activity Based Costing" is activated in any controlling area.
If the component is active, check whether the component is being used for parallel
calculation, since the delta versions needed for parallel calculation are no longer
supported in SAP S/4HANA.
Procedure: To check whether the component is active, go to the implementation guide
(Transaction SPRO) and choose Controlling --> General Controlling --> Maintain
Controlling Area--> On the popup chose "Maintain Controlling Area" and check
the relevant controlling areas: Choose the controlling area. Press "Activate
components/control indicators": Check whether the Activity Based Costing is activated
under "Activate components/control indicators".
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 362
Alternatively: Instead of checking the customizing entries for all controlling
areas manually, use transaction SE16 to check whether table TKA00 (controlling areas)
contains at least one entry with the field value TKA00-COABC = 1 ("Component Active
for Parallel Calculation") or 2 ("Component Active for Parallel Calculation and
Integrated Calcluation"). If TKA00-COABC is empty the component "Activity Based
Costing" is not active.
If the component "Activity Based Costing" is active, check whether delta versions have
been created for parallel calculation. In the implementation guide, choose Controlling ->
General Controlling -> Maintain Versions and check which versions are defined. Delta
versions for Activity Based Costing can be identiifed by the existence of a reference
version in the Controlling Area Settings. Choose "Controlling Area Settings" and check
whether a reference version has been assigned. Then check "Controlling Area Settings >
Delta Version: Business Transactions from Reference Version" to determine which
transactions are currently being included in this delta version.
Alternatively: instead of checking the customizing entries for all versions manually, use
transaction SE16 to check whether table TKA09 (CO versions) contains at least one entry
where TKA09-REFVS points to a reference version. If TKA09-REFVS is empty, then
delta versions are not in use.
Rating:
If at least one controlling area has set "Component Active for Parallel Calculation" or
"Component Active for Parallel Calculation and Integrated Calcluation" this note is
relevant for you. If all controlling areas have set "Component Not Active" this note is
not relevant for you.
If you have defined a CO version that uses a Reference Version to store the values for
Activity Based Costing, this note is relevant for you. If there are no entries for reference
versions in the controlling area settings for the version, then this note is not relevant to
you.
Solution
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.
If you can work without delta versions after the S/4 conversion, you can ignore the check.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 363
In this case we recommend to delete the data of the delta versions in the ECC system
according to note 3126356 to aviod any error messages in the conversion check.
Alternatively you can skip the error message in the conversion check and not map the
delta versions to a ledger for migration. They will then be ignored and no longer visible
in reporting.
Business Process related information
Allocations performed in parallel activity based costing are no longer supported.
Transaction not
available in SAP
S/4HANA on-premise
edition 1511
Transaction codes do not distinguish parallel and operative activity
based costing. Where version 0 is used, there will be no change.
Where a delta version is used, the system will issue an error message.
Since the period close transactions for Cost Center Accounting
include the business process as a sender/receiver, there is no need for
the separate transactions for Activity-Based Costing. For this reason
transaction CPV5 has been replaced by KSV5 (distribution),
transaction CPP5 by KSU5 (assessment), transaction CPC5 by KSC5
(indirect activity allocation), and CPII by KSII (activity price calculation).
The same applies to the transactions to maintain cycles so CPV1-3 are
covered by KSV1-3, CPP1-3 by KSU1-3 and CPC1-3 by KSC1-3.
Similarly the actual posting transactions for Cost Center Accounting
include the business process as an account assignment so there is no
need for separate transactions for Activity-Based Costing. Therefore
transactions KB11NP, KB13NP and KB14NP are covered by
transactions KB11N, KB13N and KB14N. Transactions KB21NP,
KB23NP and KB24NP are covered by transactions KB21N, KB23N
and KB24N. Transactions KB31NP, KB33NP and KB34NP are
covered by transactions KB31N, KB33N and KB34N. Transactions
KB15NP, KB16NP and KB16NP are covered by transactions KB15N,
KB16N and KB17N. Transactions KB51NP, KB53NP and KB54NP are
covered by transactions KB51N, KB53N and KB54N.
The planning transactions for Activity Based Costing (CP06/CP07,
CP26/CP27, CP46/CP47 and CP97/CP98 use the old data model and
update the totals records. The business process is not included in the
delivered data model for SAP Analytics Cloud for Planning or SAP
BPC optimized for S/4HANA. If you are unable to access some of the
planning transactions, please refer to SAP Note 2366171.
Required and Recommended Action(s)
Activate Operational Activity Based Costing. Check existing roles and adjust assigned
transactions if necessary.
Related SAP Notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 364
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.
Other Terms
Activity Based Costing (CO-OM-ABC)
12.11S4TWL - GENERAL COST OBJECTS AND COST OBJECT
HIERARCHIES
Application Components:CO-PC-OBJ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270411
S4TWL - General Cost Objects and
Cost Object Hierarchies
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Table CKPH contains master data for cost objects and/or cost object hierarchies.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 365
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
CKMDUVMAT 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 in SAP
S/4HANA on-premise
edition 1511
KKC1, KKC2, KKC3 - Create, change and display general cost object
KKPH - General cost objects - collective entry
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 366
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 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 CKMDUVMAT and
CKMDUVACT 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 367
Adjust roles and authorizations to remove deprecated transactions.
12.12S4TWL - TRANSFER PRICES/ PARALLEL DELTA VERSIONS
Application Components:CO-PA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270414
S4TWL - Transfer Prices / COGM / ABC
using Delta Versions
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
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 implies that you are using transfer prices
or COGM. If you are using an edition prior to 1610, this note is relevant for you.
To check whether parallel Activity Based Costing is active in your system, please refer to
the instructions in SAP Note 2270408.
Solution
Business Value: Transfer Prices
Globalization, a history of mergers and acquisitions, and stringent fiscal rules often mean
that companies have structured their organization into multiple legal entities. As a
consequence, many internal supply chains are represented as a series of sales processes
between affiliated companies. As these organizations move to a single instance with SAP
S/4HANA, transfer pricing becomes a major topic and group costing no longer requires a
data warehouse approach but can be captured in the operational system. The transfer
pricing capabilities are now delivered in the universal journal using a more streamlined
and consistent approach than was possible in previous releases. In this context the group
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 368
is represented by the controlling area and group valuation covers all material movements
within that controlling area. Intercompany transfer prices are agreed between legal
entities (company codes) by defining the appropriate pricing agreements. It is also
possible to define transfer prices between profit centers to provide a divisional view of
the organization. The capture of the group view as the material movements are posted
can significantly reduce the period close tasks and provide a simplified basis for legal
consolidation.
Business Value: Parallel Valuation of Cost of Goods Manufactured
Multinational organizations often report according to multiple accounting principles, such
as IFRS as the global accounting standard and US-GAAP or Russian GAAP as local
standards. For those countries that do not report solely according to IFRS, it is possible to
set up additional ledgers for the local GAAPs and to calculate activity prices and material
prices that are based on the different inputs, such as the different approaches to
depreciation, pensions, and so on. This approach can significantly redice the amount of
manual effort at period close to meet the additional accounting standards.
Description
Transfer prices
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 company’s 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.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 369
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.
Multiple Valuation of Cost of Goods Manufactured
The functionality of multiple valuation of cost of goods manufactured (COGM) provides
parallel valuations according to multiple accounting principles.
COGM using parallel accounts is not supported.
COGM using parallel ledgers is available with SAP S/4HANA 1610 FPS01 for new
customers and for installed base customers with SAP S/4HANA 1610 FPS02.
For detailed information about COGM in S/4HANA 1610, please see the FAQ section of
SAP note 1852519. This note has a powerpoint presentation attached relating to this
topic.
ABC
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.
Other Terms
Parallel valuations.
12.13S4TWL - ALE SCENARIOS
Application Components:CO-PA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 370
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270416
S4TWL - ALE Scenarios
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is relevant if you are using ALE scenario for master and transactional data. In
S/4HANA system you have a consistent data model for FI and CO and Accounts and
Cost Elements are merged. In a Business Suite system you have separate tables for FI and
CO documtents, as well as for Accounts and Cost Elements.
The most important changes for Master Data are:
The attribute "G/L Account Type" has been introduced at the level of the chart of
accounts.
G/L account master records are created for secondary cost elements, too.
Cost elements can no longer be maintained in a time-dependent manner.
You can do the following check in the your system:
Enter Easy Access menu and navigate to: Tools --> ALE --> ALE Administration -->
Runtime Settings --> Partner Profiles
Select the partner profile for Logical Systems (Partner Type LS).
Select you productive client --> If the outbound parameters contain message type
GLMAST or COELEM this note is relevant for you.
The most important information for Transactional Data are:
Business Suite / S/4HANA -> S/4HANA
FIDCMT01 is not supported anymore
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 371
CODCMT01 must be executed in addition to the FI documents (even though receving
system is using Universal Journal)
Changes in respect to the ALE scenario "S/4HANA -> Business Suite" are described in note "2313879
- Distribution of documents via ALE from or to S/4HANA"
Solution
Description
Further details can be found in the following notes:
ALE for transactional data --> see note 2313879
Master Data ALE for GL Accounts/cost elements --> see note 2355812
Business Process related information
Required and Recommended Action(s)
no actions required
12.14S4TWL - COST ELEMENTS
Application Components:CO-PA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270419
S4TWL - Account/Cost Element
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 372
This note is relevant for you when your start release for the system conversion is an ERP
release.
It is not relevant if your start release is S/4HANA Finance or S/4HANA.
Solution
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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 373
Default account assignments for cost elememts can be set in transaction OKB9 rather
than in the cost element master. The cost element attribute mix does not exist
any longer. Field status groups can remain unchanged.
Existing 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.
Separate G/L accounts for CO-FI real time reconciliation postings are no longer needed,
since intercompany postings will be updated using the secondary cost element defined in
Controlling rather than rolled up to reconciliation 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).
Account determination for intercompany postings originating in Controlling is different.
Some intercompany cost allocations affect Controlling only and should not be reported in
legal reports, such as the balance sheet or income statement.
Therefore, we recommend assigning a separate intercompany clearing account of type
"Nonoperating Expense or Income" to each G/L account. This allows you to assign the
sending and receiving lines to the same node in your financial statement version so that
the intercompany cost allocations won't impact your financial statement.
For more information, see SAP Note 2457163.
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). Intercompany postings originating in
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 374
Controlling (such as an intercompany activity allocation) will be updated under the
secondary cost element rather than a reconciliation account.
Cost element groups are still available to group accounts of type primary or secondary
cost element for selection and reporting.
Transaction not available in SAP S/4HANA
on-premise edition 1511
KA01 - Create primary cost element
KA02 - Change cost element
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).
Fiori Application F0125 - Cost Element (Fact
Sheet)
Fiori Application F0126 - Cost Element Group
(Fact Sheet)
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.
12.15S4TWL - Reporting/Analytics in Controlling
Application Components:CO-PA-IS, CO-OM-IS, CO-PC-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349297
S4TWL - Reporting/Analytics in
Controlling
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 375
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is relevant if you are doing a conversion from ERP ECC 6.0 (EHP 7 or
higher) to S/4 HANA.
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. You also need to understand where the plan data for reporting resides.
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. This means that the relevant data has to be aggregated on the fly from the universal
journal for the fields in the compatability view. These reports also currently show
planning data created for the GL dimensions using transaction GP12N. Reports in
Controlling also work with compatibility views. This means that they continue to display
cost elements and cost element groups rather than accounts and account groups and have
to aggregate the relevant fields in the universal journal on the fly. The classic reports also
read planning data created using transactions KP06 (cost centers), KPF6 (internal orders)
and CJR2 (projects).
To use the new reports, you will have to activate the relevant Fiori apps. 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. A new field has been introduced to the
universal journal that represents the old CO object number and works using a
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 376
combination of object type = ACCASSTY (KS for cost center, OR for order, and so on)
and account assignment = ACCASS (the cost center number, order number and so on).
This provides the means to replace the reports formerly delivered under the Cost and
Revenue Accounting InfoSystem. Nonetheless, you need to be aware that plan/actual
reporting is based on SAP BPC for S/4 HANA Finance or on SAP Analytics Cloud for
Planning and you will need to activate the appropriate planning applications. Planning
functions exist that transfer data from the classic planning transactions to the new data
structures.
The first Fiori app for reporting on target and actual costs on production orders is the
Production Cost Analysis app from 1610 and can be used as an alternative to the classic
target/cost analyses in ABAP list viewer. In 1809 this app was extended to provide access
to the detailed costs by work center and operation and to calculate target costs on the fly
for these entities. For the reporting of the variance categories on production orders (stored
in table COSB) you should continue to use the classic reports or move to the event-based
approach delivered in combination with Universal Parallel Accounting.
The first Fiori apps for reporting on commitments by project and cost center have been
delivered in the cloud using the predictive accounting approach where commitments are
stored in an extension ledger rather than the dedicated CO table (COOI). From 1809 you
can switch to Fiori apps to display commitments for projects and cost centers and to
report budget usage by project. The predictive accounting approach is also used to update
the values from incoming sales orders to an extension ledger and to store statistical sales
conditions by market segment.
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 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. You can identify the need for such reports by checking whether
entries for WIP and variances are shown in table COSB. Target costs and
intercompany eliminations are identified by the value type WRTYP in table COEP. There
are not yet Fiori apps to display statistical key figures on profit centers, cost centers,
orders and WBS elements.
If you choose to use a mixture of new 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 and that
similar functions are available if you plan using SAP SAC.
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. Alternatively if you use
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 377
SAP SAC for planning, plan/actual reports are built directly on the ACDOCP planning
table. 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). To see
CO-PA characteristics that were derived from the account assignments in Controlling use
transaction KE24N. 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.
Solution
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 or SAP SAC.
Transaction not available in SAP S/4HANA on-
premise edition 1511
All transactions available, but are making use of
compatibility views
Required and Recommended Action(s)
Most existing reports in Report Writer/Painter, drill-down reporting and ABAP List
Views (ALV) will continue to work using compatibility views which will provide access
to all fields available in the original report but will not provide insight over and
above what was already available in SAP ERP. The merge of the cost elements and the
accounts mean that only the account is stored in the universal journal but that you can use
compatibility views to convert the account view back to the cost element view.
The exception are those Report Writer/Painter reports in library 5A1 (Cost Element
Accounting) which read from table COFIT. The reconciliation ledger is no longer filled
after the conversion to SAP S/4HANA. Here you will have to use the new reports to
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 378
show the costs and revenues by G/L account and account assignment. If you select the
new fields ACCASS and ACCASSTY as drill-downs you can show all postings to cost
center, order, and so on as in the classic cost element reports.
Please ensure that the transactions such as CK11N (create standard cost estimate), CO01-
CO03 (create/change/display production order) and CR01-CR03 (create/change/display
process order) are calling ABAP List Views rather than the old Report Writer reports. To
do this, choose transaction OKN0, select the tab "Report Selection" and ensure that the
flags "Flexible itemization", "Flexible cost component report" and "Flexible cost display"
are active.
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 or SAP SAC.
12.16S4TWL - Profitability Analysis
Application Components:CO-PA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349278
S4TWL - Profitability Analysis
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Task: Check if Profitability Analysis is activated in your system.
Procedure: Go to implementation guide (Transaction SPRO) --> Controlling -->
Profitability Analysis --> Flows of Actual Values --> Activate Profitability Analysis. If
there is an activation flag in the columns “costing-based” or “account-based” this note is
relevant for you.
Solution
Options for Profitability Analysis in SAP S/4HANA on-premise edition
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 379
The SAP S/4HANA on-premise edition allows for two different profitability analysis
solutions:
Margin Analysis
Profitability Analysis within the Universal Journal addressing the needs of
internal and external accounting, supporting real-time derivation of reporting
dimensions and embedded analytics.
Costing-based CO-PA
Groups revenues and costs according to value fields and applies costing-based
valuation approaches. Data is recorded in a dedicated persistency apart from
external accounting.
SAP recommends using Margin Analysis in SAP S/4HANA. Margin Analysis has been
extended broadly over the past releases and we continue to conduct new developments in
this area only. It is perfectly integrated into the overall concept of the Universal Journal
and is therefore fully in line with our Financial Accounting development strategy. Margin
Analysis is active if there is an activation flag for 'account-based' in the IMG procedure
mentioned above.
In addition to Margin Analysis, SAP also offers Costing-based CO-PA. Before the
conversion to SAP S/4HANA on-premise, SAP recommends that you verify whether
Margin Analysis can already cover all requirements and costing-based CO-PA can
remain de-activated.
Business Value
The universal journal (ACDOCA) is the heart of Accounting and includes all Margin
Analysis characteristics in order to allow multi-dimensional reporting by market segment.
The universal journal includes columns for the standard characteristics and all additional
characteristics included in an organization’s operating concern (up to sixty
characteristics, including the fixed characteristics). If you have already configured an
operating concern for Margin Analysis, columns will be created for each of the
characteristics during migration.
The benefit of this approach is that all revenue and cost of goods sold postings are
automatically assigned to the relevant characteristics at the time of posting and that
allocations and settlements are made to the characteristics at period close. It is also
possible to configure some expense postings such that the characteristics are derived
automatically, so that material expenses assigned to a WBS element (account
asssignment) are automatically assigned to the characteristics entered as settlement
receivers for the WBS element. This automatic derivation of the characteristics can
reduce the number of settlements and allocations to be performed at period close and
provide real-time visibility into spending during the period.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 380
There are also no reconciliation issues between the general ledger and Margin Analysis.
Be aware, however, that revenue is recognized at the time of invoicing and cost of goods
sold when the delivery is made. If there is a time gap between delivery and invoicíng,
costs may be visible in Margin Analysis for which no revenue has yet been posted
(matching principle). A new approach to delay the cost of goods sold posting until the
invoice is posted is currently available in S4HC.
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. Margin Analysis covers record types F (billing documents), B
(direct FI postings), C (settlement) and D (assessment) in costing-based CO-PA. A
different approach is taken for record type A (incoming sales orders) where predictive
accounting documents are created to represent the sales order prior to delivery and
invoicing.
There is no direct migration from costing-based CO-PA to Margin Analysis. Please bear
in mind the following general principles as you consider a conversion. These principles
may result in a change in the valuation approach and the value flows compared to
systems working only with costing-based CO-PA:
Revenues and sales deductions are included in Margin Analysis whenever the price
conditions are mapped to an account and result in postings to Financial
Accounting. Statistical price conditions are included from SAP S/4HANA 1809
(or 1808 cloud edition).
Cost of goods sold (COGS) postings are assigned to an account/cost element 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. This split can be updated with the results of actual
costing from SAP S/4HANA 1809. Functions to support the matching principle
between revenues and COGS are available. In sell-from-stock scenarios the
COGS valuation is based on the material's valuation price at the time of the goods
issue. In drop-shipment scenarios the COGS valuation is based on the amount in
the supplier invoice.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 381
You may be able to replace some assessment cycles and settlements by having the
system derive the 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 Margin Analysis, but you must include the
account/cost element in the selection criteria. Reference data for the distribution
must be account-based.
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. Note that only three additional quantity fields are
supported, though convertible quantities (e.g. grams to kilograms) can be handled
in the same field.
It is not possible to summarize G/L fields such as profit center, partner profit center,
etc, and account assignments such as WBS element and internal order.
In many processes the system automatically sets an account assignment to a
profitability segment. The availability of this account assignment may prevent the
system from deriving default account assignments e. g. from OKB9 or may
change the behavior by following the substitutions defined in OKC9. Please refer
to note 2516083 for further information.
Variances for production orders are inherently available within Margin Analysis
(optionally including a split into variance categories; see above), without any
further configuration in the settlement profile.
Transaction not available in SAP S/4HANA on-
premise 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 and consolidation. During conversion, the system will create
columns in the universal journal for all characteristics in the operating concern.
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. Check whether the functions available with Margin
Analysis can already satisfy your reporting requirements or whether you will continue to
need costing-based CO-PA for an interim period. If combined Profitability Analysis is
currently used, check whether the functions available with Margin Analysis can already
satisfy your requirements.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 382
Existing reporting transactions, such as KE30 and KE24, will continue to work, but also
investigate possible usage of the Fiori apps to display information by market segment,
including additional currencies and data from the extension ledgers.
Creation of Profitability Segments and Account Determination for COGS
If you only used costing-based CO-PA but no Margin Analysis before the conversion you
need to understand when a profitability segment is created in the sales process and how
COGS are posted during the delivery. In Margin Analysis the billing and the delivery are
recorded as separate documents and both journal entries are assigned to a profitability
segment. This means a change to include the assignment to a profitability segment in the
COGS posting and the need to change the account determination to select an account/cost
element.
The profitability segment is always derived for the sales order item and referenced
during the delivery. Since the delivery document is now assigned to a profitability
segment, you will need to ensure that you are updating an account of type P
(primary costs and revenues) rather than an account of type N (non-operating
expenses) . Check the account determination for transaction GBB (Offsetting
Entry for Inventory Posting) and account modification constants VAX and VAY.
COGS posted before the conversion are posted without a cost element (type N),
but after the conversion with a cost element (type P). To avoid issues, assign an
account of type N to account modification VAX and an account of type P to
account modification VAY (Margin Analysis works with VAY as a default).
If you only worked with costing-based CO-PA and did not use incoming sales orders
(record type A) prior to the migration, you will have open sales order items and
delivery documents with no assignment to a profitability segment, even though
this is required once Margin Analysis is active and the system will issue a
message that the assignment to a profitability segment is missing if you
reschedule the sales order item or post a goods issue after the migration. You can
use transaction KE4F to derive the missing profitability segments for a small
numbers of sales order items. For larger volumes of data, run the transaction in
parallel over multiple packets of different sales orders (see SAP Note 2225831).
Where sales orders are partially delivered at the time of conversion, it is
recommended to cancel the deliveries and create new ones as this will result in the
profitability segment being selected with reference to the sales order during
delivery. However, this solution is not practical where goods movements have
already been posted with reference to the delivery. The COGS for these goods
movements will not be visible in Margin Analysis.
If you chooose to use the same G/L account for account modification constants VAX
and VAY, you should also cancel all deliveries posted prior to the conversion and
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 383
create new ones to ensure that the assignment to the profitability segment is
correct.
Other Terms
Account-based CO-PA Margin Analysis S/4HANA S/4 HANA Migration Profitability
Analysis
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 384
13.Cost Management and Profitability Analysis
13.1 S4TWL - Profitability Segment Number Change of Type
Application Components:CO-PA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3320010
S4TWL - Profitability Segment Number
Change of Type
Symptom
You are using CO-PA and are upgrading from S/4 HANA Release 2022 or earlier to S/4
HANA Release 2023 or a later release.
The type of Profitability Segment Number field has been changed from type NUMC
length 10 to type CHAR length 10.
As a consequence, you now have more information on the profitability segment and
therefore more proftability segments in total.
If you are using the profitability analysis CO-PA and you are upgrading to S/4 HANA
Release 2023 or a later release, the change of the underlying data type of the Profitability
Segment Number could be relevant.
Reason and Prerequisites
If you are using profitability analysis CO-PA and you are upgrading to S/4 HANA
Release 2023 or later release, the change of the underlying data type of the Profitability
Segment Number could be relevant.
Task: Check if Profitability Analysis is activated in your system.
Procedure: Go to implementation guide (Transaction SPRO) --> Controlling -->
Profitability Analysis --> Flows of Actual Values --> Activate Profitability Analysis. If
there is an activation flag in the columns “costing-based” or “account-based” this note is
relevant for you.
Due to the limited number of possible values, the technical type of Profitability Segment
Number field has been changed from numerical character (type NUMC) length 10 to
type character (type CHAR) length 10. Say, after the upgrade to S4HANA 2023 the
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 385
profitability segment number field is represented by a different technical type. As a
consequence, the ABAP processing logic dealing with profitability segment numbers has
to be prepared to deal with these types of non-numeric characters values.
The domain change is relevant for Margin Analysis as well as Costing-Based profitability
analysis.
IS INITIAL Checks
Even so non-numerical characters do not yet occur in your system, one immediate
consequence of the change is the so called initial value of the profitability segment
number. Since in the ABAP processing logic this initial value typically represents an
undecided or not yet defined value, the check for the initial value is a very frequent
operation - in SAP and customer ABAP coding.
Du to the technical change the initial value of the Profitability Segment Number field
changes from 000000000000 to space with the upgrade to S/4 HANA Release 2023.
Since the existing profitability segment numbers will remain in use, there will be two
different "initial" values in future. As the ABAP processing logic has to deal with both
types of profitability segment numbers, say, numbers created before and after the upgrade
to S/4 HANA Release 2023, both initial values have to be checked.
Furthermore, other less frequent consequences of the technical type change could occur, a
detailed list of the different technical consequences of the type change are explained in
SAP note 3320427.
Solution
13.1.1 Business Process related information
The change of the technical type of Profitability Segment Number field has no business
related impact.
13.1.2 Required and Recommended Action(s)
To avoid any errors in system behaviour due to the change of the type in profitability
segment field, you need to adapt your customer coding for this change. The adaption of
the initial value check needs to be carried out, regardless of whether you will be using the
additional alphanumeric profitability segments or not.
In order to identify coding that needs to be adapted, the Code Inspector checks is
executed as part of the related simplification item. If you are using the decommissioned
CDS field ProfitabilitySegment in customer defined CDS Views, you must switch to the
replacement field ProfitabilitySegment_2.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 386
This SAP Note only covers the actions that all customers must take. For customers that
require more profitability segment numbers see SAP Note <needs to be created>.
What to do before the upgrade
Please ensure that you update the check logic to the most recent version, by
implementing all relevant, new notes from SAP note 2436688. Otherwise you might get
wrong or missing check results.
Independent whether you are using initial check or select statement; please investigate if
you have set PAOBJNR to empty in your own (customer) coding. The change of the
underlying technical domain in the ABAP dictionary could lead to changed behavior
when moving profitability segment numbers into different types or when doing numerical
calculations. All of these possible changes due to the technical change are addressed by
the Code Inspector check variant SAP_COM_FIELD_EXT_1 which is executed as part
of the simplification item.
As described above, the initial value of the field PAOBJNR will be space rather than
0000000000 for new profitability segments. However old values on the database will not
be updated during the upgrade process. This means that all code that checks whether
field PAOBJNR is empty needs to check for both values:
ABAP Code Examples
ABAP code such as
data: lv_paobjnr type rkeobjnr.
...
" check if prof. segment is initial
IF lv_paobjnr IS INITIAL.
...
ENDIF.
has to be changed to
data: lv_paobjnr type rkeobjnr.
...
" check if prof. segment is initial using predefined constant values
" for either the new or the old initial value
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 387
IF ( lv_paobjnr = if_fco_copa_paobjnr=>c_init
OR lv_paobjnr = if_fco_copa_paobjnr=>c_zero ).
...
ENDIF.
Likewise the IS NOT INITIAL check has to be changed as follows:
data: lv_paobjnr type rkeobjnr.
...
" check if prof. segment is not initial
IF lv_paobjnr IS NOT INITIAL.
...
ENDIF.
has to be changed to
data: lv_paobjnr type rkeobjnr.
...
" check if prof. segment is not initial using predefined constant values
" for either the new and the old initial value
IF ( lv_paobjnr <> if_fco_copa_paobjnr=>c_init
AND lv_paobjnr <> if_fco_copa_paobjnr=>c_zero ).
...
ENDIF.
Other Terms
Domain RKEOBJNR. Data element RKEOBJNR. Global field ProfitabilitySegment.
Decommissioning of CDS field ProfitabilitySegment. Replace usages with
ProfitabilitySegment_2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 388
14.Financials - General Ledger
14.1 S4TWL - Profit Center and Segment Reorganisation
Application Components:FI-GL-REO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3087195
Profit center reorganization and
segment reorganization
Symptom
The profit center and segment reorganization of ECC are not available in SAP S/4HANA.
The business functions FIN_GL_REORG_1 and FIN_GL_REORG_SEG cannot be
activated in SAP S/4. When you create a new reorganization plan, the system issues an
error message.
With Release SAP S/4HANA 2022, there is a new solution for profit center
reorganization. This new solution does not have to be activated using a business function,
and can be configured and used directly, instead. The new solution is part of the SAP S/4
product and does not require an additional license.
With Release 2022, the new profit center reorganization solution does not yet include the
full scope of functions of the reorganization solution in ECC.
Segment reorganizations are not yet possible in SAP S/4.
Reason and Prerequisites
Due to the changed architecture of the finance applications in SAP S/4, the ECC profit center and
segment reorganization solution cannot be supported. The mentioned business functions cannot be
activated. As of Release 2022, please use the new profit center solution.
Solution
SAP plans to enhance the new solution for reorganizations. Due to the complexity of the
solution, there will be a phased rollout starting with functions for profit center
reorganization (as of OP2022).
For information about the SAP Road Map, see the following link:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 389
https://roadmaps.sap.com/board?PRODUCT=73554900100800000266&range=CURRE
NT-LAST&q=org#Q4%202020;INNO=6CAE8B28C5DB1ED799F409A6F94920C3
Other Terms
Profit center reorganization, segment reorganization, reorganization, organizational
change
14.2 S4TWL - GENERAL LEDGER
Application Components:FI-GL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270339
S4TWL - General Ledger
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
The universal journal significantly changes the way transactional data is stored for
financial reporting. It offers huge benefits in terms of the ability to harmonize internal
and external reporting requirements by having both read from the same document store
where the account is the unifying element.
You still create general journal entries in General Ledger Accouting, acquire and retire
assets in Asset Accounting, run allocation and settelement in Controlling, capitalize
research and development costs in Investment Management, and so on, but in reporting,
you read from one source, regardless of weather you want to supply data to your
consolidation system, report to tax authotities, or make internal mangement decisions.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 390
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 guarantee that the reporting based on these structures shows the same
result as before.
Classic Report Writer/Painter and drilldown reports will continue to show the data from
the universal journal in separate views, so reports in Financial Accounting will show only
the fields formerly available in FAGLFLEXT and reports in Controlling will show only
the fields formerly available in COSP/COSS. To see the combined data you are
recommended to work with the new Fiori reports that show all the fields in the universal
journal.
The upgrade to S/4HANA is not a 'normal' upgrade but a system conversion which comes
along with some incompatible changes. The incompatible changes refer to the usage of
summary and index tables and the update of table BSEG and further changes are
described in detail in the note 2431747 "General Ledger: Incompatible Changes in
S/4HANA compared to classic ERP releases".
Required and Recommended Action(s)
Mandatory application configuration steps related to General Ledger in the IMG
(transaction SPRO):
Folder Preparations and Migration of Customizing
Please use the step "Check Customizing Settings Prior to Migration" (transaction
FINS_MIG_PRECHECK) and clean up all inconsistencies prior to the migration
of Customizing and ransactional data.
Folder 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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 391
Therefore we recommend to go though all activites of "Preparation and Migration
of Customizing for the General Ledger" in its sequence in the UI.
As last step perform "Execute Consistency Check of General Ledger Settings"
(transaction FINS_CUST_CONS_CHK). If this step yields errors for prdouctively
used company codes, plese solve these errors before you start the migration of
transactional data in Folder Data Migration. If you are getting errors for non-
productively used company codes, you can exclude these by activating the flag
"Template" in view V_001_TEMPLATE (transaction SM30).
It is recommended to investigate the use of the new reports that show all fields in the
universal journal to achieve maximum benefit from the conversion.
If you have not used the New General Ledger before, that means that you still have used
the Classic General Ledger before migrating to SAP S/4 HANA, please be aware that the
handling of the Foreign Currency Evaluation, the Line Item Display and the Balance
Carry Forward has slightly changed. Please make yourself familiar with the new handling
of them in NewGL before the Migration.
14.3 S4TWL - SAP HANA ODP ON HANA CALC VIEW-BASED
REPORTING
Application Components:FI-GL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270360
S4TWL - Calc View-Based Reporting
(HANA live)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With Simple Finance 1.0, 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 392
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.
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
14.4 S4TWL - Closing Cockpit with S/4 HANA OP
Application Components:FI-GL-GL-G, CA-GTF-SCM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2332547
S4TWL - Closing Cockpit with S/4HANA
OP
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Task: Check if the customer uses any of the Business
Functions FIN_ACC_LOCAL_CLOSE, FIN_ACC_LOCAL_CLOSE_2,
FIN_ACC_LOCAL_CLOSE_3 are active.
Procedure: Use transaction SFW5 to list active Enterprise Business Functions.
Rating:
If at least one transaction codes has been used -> YELLOW
If none of the transaction codes has been used -> GREEN
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 393
Solution
Description:
The functionality of the standard Closing cockpit (without license) is available, but
defined as "not the target architecture" in SAP S/4HANA 1511, 1610 or subsequent
releases. The Business Functions FIN_ACC_LOCAL_CLOSE,
FIN_ACC_LOCAL_CLOSE_2, FIN_ACC_LOCAL_CLOSE_3 (requiring a license for
SAP Financial Closing cockpit) are flagged as obsolete in S/4HANA OP.
Business Process related information
If any of the Business Functions listed above are active, instead of using the classical
Closing cockpit,
under SAP S/4HANA 1610 OP consider to use the Add-On Financials Closing
Cockpit 2.0,
under SAP S/4HANA OP 1710 ff. use the SAP S/4HANA Financial Closing
cockpit.
Other Terms
SYSTEM_ABAP_ACCESS_DENIED
14.5 S4TWL - Currencies in Universal Journal
Application Components:FI-GL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2344012
Currencies in Universal Journal
Symptom
You are doing new installation of SAP S/4HANA or a system conversion to SAP
S/4HANA. All currency configurations can be migrated to the universal journal of
S/4HANA.
This note provides information on the new configuration capabilities for parallel
currencies in FI and CO.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 394
Reason and Prerequisites
This note is relevant, if you are use FI / CO in S/4HANA.
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.
Solution
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
later releases 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 395
TSL
Amount in Balance
Transaction Currency
Amount converted to the currency of the G/L
account, in order to allow aggregation on G/L
account level; corresponds to BSEG-PSWBT.
HSL
Amount in Company
Code Currency (Local
Currency)
Currency of the company code; corresponds to
BSEG-DMBETR in FI and object currency in CO
(except co area currency type 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
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)
WSL, TSL, HSL and KSL mandatory currencies in all ledgers.
KSL is filled, if the company code is assigned to a controlling area. The currency type for
KSL is defined by the setting in the controlling area.
The second and third parallel currencies of FI (BSEG-DMBE2 or BSEG-DMBE3)
correspond to 2 amount fields of KSL - GSL according to configuration in tx
FINSC_LEDGER.
Table BSEG is not (and will not be) extended and still contains only 3 parallel
currencies; the BSEG relevant currency types can be configured in the overview screen
of the company code assignment in tx FINSC_LEDGER in the columns on the right
side (1st / 2nd / 3rd FI Currency). Here you can choose from the configured currency
types the BSEG relevant currency types. Currency types in customer name space are not
allowed as BSEG relevant currency.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 396
When a currency type is marked as BSEG relevant in the leading ledger (2nd or 3rd FI
Currency) and this currency type is also configured in a non-leading ledger, then it needs
to be a BSEG relevant in the non leading ledger as well.
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, 1709 and 1809 (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
30
40
50
60
Z1
Z2
Z3
Z4
Z5
BSEG and Fixed Asset
Accountning
10
30
40
Material Ledger
10
30
40
Controlling
10
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
Foreign Currency Valuation
X
X
X
X
X
X
X
X
X
X
Regrouping
X
X
X
1
1
1
1
1
1
1
GL Allocations (Assessment
and Distribution)
X
X
X
X
X
X
X
X
X
X
CO Allocations (Assessment
and Distribution)
X
X
4
4
4
4
4
4
4
4
CO-PA Allocations
X
X
3
3
3
3
3
3
3
3
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
2
2
2
2
2
2
2
2
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 397
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, FI-AR, and FI-GL or for CO and GL
allocations (marked with X in the above table), but not yet for Fixed Asset depreciations
or CO settlements.
1: 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.
2: Since Release OnPrem 2020 CO Settlement supports all ACDOCA currencies, if this
is activated in the settlement profile
3: Since Release OnPrem 2021 CO-PA Allocation are available as part of Universal
Allocation. Universal Allocation supports all currencies; the classic CO-PA Allocations
still support 10 and 30 only.
4: CO Allocations can treat all 10 amounts field precisely, if you include amount field in
the cycle definition, or otherwise convert with current exchange rates. Also in cross
company or in the COGM scenario, the amounts are converted with current exchange
rates.
Overview on supported reporting for currency fields
With S/4H 1610 and later releases the currencies that are not stored in BSEG can be
displayed in following UIs:
Description
Transaction Code
Display Document
FB03
Display Document in General Ledger View
FB03L
Display G/L Account Balances
FAGLB03
Display G/L Account Line Items
FAGLL03
Line Item Browser
FAGLL03H
Display G/L Account Line Items
Fiori App
Journal Entry Analyzer
Fiori App
Audit Journal
Fiori App
Display Financial Statement
Fiori App
In addition the new analytics with FIORI UI based on CDS Views supports all currencies
of the Universal Journal. Note 2579584 contains details on the CDS based analytics.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 398
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.
Since S/4Hana OP 1809 it is possible to introduce a freely defined currency,(but not a
BSEG relevant currency!). You find the conversion tools in the IMG tree below
Financial Accounting Global Settings - Tools - Manage Currencies.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 399
14.6 S4TWL - Manual Accruals (Accrual Engine)
Application Components:FI-GL-GL-ACE, FI-GL-GL-AAC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2582883
S4TWL - Manual Accruals (Accrual
Engine)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is only relevant if you are using the application Manual Accruals: The Manual
Accruals application is based in the reuse tool Accrual Engine.
Solution
Business Value
With release S/4HANA 1809, a new Accrual Engine has been developed. The new
Accrual Engine is called S/4HANA Accrual Engine.
The S/4HANA Accrual Engine is seamlessly integrated with the General Ledger. The
following features are available in the S/4HANA Accrual Engine:
The Accrual Engine supports all currencies of the General Ledger.
Postings can be performed on ledger level instead of only accounting principle level.
Complex postings are supported, for example the posting of exchange rate
differences: An accrual posting can now contain more than two line items.
The number of database tables has been reduced. For example the original document
of the accrual postings is now contained in the Universal Journal Entry, table
ACDOCA.
Description
The old Accrual Engine still exists and is still being used by applications like
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 400
Accruals For Rights Management
Revenue Recognition For License Sales
Accruals For License Acqusitions
Accruals For Real Estates
But the application Manual Accruals is the first application that has been adopted to the
new S/4HANA Accrual Engine:
After upgrading to release S/4HANA 1809 the application Manual Accruals is only
available based on the S/4HANA Accrual Engine.
As a consequence, after upgrading to release S/4HANA 1809 you need to migrate the
content of the old database tables of the old Accrual Engine into the new tables of the
S/4HANA Accrual Engine. This affects customizing tables as well as transactional tables
of the Accrual Engine.
Required Actions
The migration of the Accrual Engine data can be performed after you migrated the
General Ledger data to S/4HANA.
Mandatory application configuration steps related in the IMG (transaction SPRO):
Applying migration relevant SAP Notes mentioned in step 3 of SAP Note 2795791.
As a first step you migrate the customizing of the Accrual Engine.
You will find the corresponding IMG activity in the following IMG folder:
Conversion of Accounting to SAP S/4HANA -> Preparations and Migration of
Customizing -> Preparations and Migration of Customizing for Accrual Engine.
In this folder you also need to create a mass data project. This project is needed
for the migration of the transactional data of the Accrual Engine: The
transactional data consist of Accrual Engine postings (table ACEPSOIT) and
accrual object data (tables ACEOBJ, ACEDS_... and ACEPS_...).
Both, the migrated customizing and the mass data project creation are recorded in
a customizing transport.
Afterwards you perform the migration of the transactional data of the Accrual Engine
by executing the mass data project:
You will find the corresponding IMG activity in the following IMG folder:
Conversion of Accounting to SAP S/4HANA -> Activities after Migration -
> Migration of Accrual Engine Data.
After the customizing transport was imported in the productive system, you need to
execute the mass data project in the productive system also.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 401
Note that you do not need to perform the migration of the Accrual Engine
customizing in the productive system: The migrated customizing was imported by
the customizing transport. Only the migration of the transactional data needs to be
performed in each system and client separately.
The migration of the Accrual Engine does not require a system down time: You can
perform this migration even if the system is already being used productively: The only
restriction is that activities that affect the Accrual Engine data, like accrual postings,
creation or change of accrual objects is not possible as long as you did not finish the
Accrual Engine migration.
How to Determine Relevancy
You can easily check wether you are using the application Manual Accruals or not: If the
database table ACEOBJ contains entries that fullfill the condition COMP = 'ACAC', then
you need to perform the above mentioned migration steps. Exceptional case: If the entries
in this table are obsolete from a business point of view, then you do not need to perform
the migration of the Accrual Engine.
Further Information
The migration process, new features and incompatible changes of Manual Accruals in
S/4HANA 1809 are described in the attached presentations.
These presentations are also available as pdf document. You can access it using the
following URL:
https://www.sap.com/documents/2019/07/d010dfa6-577d-0010-87a3-c30de2ffd8ff.html
Other Terms
ACE, ACAC.
14.7 S4TWL - Amount Field Length Extension
Application Components:FI-GL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2628654
S4TWL: Amount Field Length Extension
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 402
Selected currency amount field lengths and related data types have been extended.
This is relevant, if you are converting from SAP ERP ECC60 or upgrading to SAP
S/4HANA On-Premise 1809 or higher.
Reason and Prerequisites
In SAP S/4HANA, currency amount fields with a field length between 9-22 including 2
decimals have been extended to 23 digits including 2 decimals. In addition to currency
amount fields, selected data elements of DDIC type DEC, CHAR, and NUMC with
varying lengths and decimal places that may hold amounts have been affected. This
feature is available in SAP S/4HANA, on-premise edition 1809 and higher releases.
Solution
Table of Contents:
Introduction
Motivation and Scope
Consistent Usage in System-Internal Code
Decoupling
Code Adaptation
Storage of an Amount on the Database
Internal Interfaces
Write To List
Strict Type Checks
External Interfaces
System Settings to Activate the Provided Amount Field Length Extension in
Customizing
Functions that may use the Provided Amount Field Length Extension
Introduction
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 403
SAP S/4HANA can support extended amount fields. We have adapted the appropriate
related SAP development entities (domains, data elements, structures, table types, and
transparent tables, external and internal interfaces, user interfaces, and so on)
accordingly. There are some scenarios where it will be required for you to adapt your
code. In a multi-system landscape, you must decide if and when to activate the provided
amount field length extension in customizing, as this will impact how the system
communicates compatibly within a system landscape. To ensure consistent behavior, the
provided amount field length extension must be explicitly activated in customizing. Note
that the extended field length in the data dictionary is not influenced by this
activation. Refer to the below in section System Settings to Activate the
Provided Amount Field Length Extension in Customizing for details.
This note focuses on what is affected by the amount field length extension and what
adjustments are necessary to ensure that the system remains technically and functionally
stable. The different aspects of the amount field length extension in SAP S/4HANA are
described in the following sections. Consider the restrictions outlined here and in the
notes listed under References.
Motivation and Scope
The amount field length extension was developed to meet the requirements of banks and
financial institutions to post financial documents representing balance sheet information
with amounts that exceed what the previous definition in SAP ERP ECC60 and previous
S/4HANA releases support. Therefore, we extended the amount fields within the general
ledger and Controlling application areas. As part of these changes, we changed data
elements of other application components with shared dependencies.
The fields that were subject to extension were primarily data elements of type CURR
with a defined length between 9 and 22, including 2 decimal places. Additionally, data
elements of type DEC, CHAR, and NUMC that were used to store amounts were also
extended.
While this scope was limited, there was a broad usage of the extended data elements
across other applications that will not use extended amounts, for example Logistics. We
decoupled the data elements that would be extended by creating copies of the original
with the original domain and technical attributes, and replaced them in all data dictionary
usages outside of the areas that were planned for extension. We extended the original
data elements by exchanging the existing shorter domains with new longer domains.
Conversion routines were created and assigned to the longer domains to limit
the maximum value permitted as screen input where the provided amount field length
extension is not activated in customizing.
To maintain the stability of the applications, certain adjustments were required for data
dictionary objects, ABAP source code, dependent user interfaces, as well as in both
internal and external interfaces.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 404
See the attached document for a list of application components with extended
amounts.
Assumptions
Data elements of type CURR with more than 2 decimal places are generally
not related to currency amounts.
Any currency amount with a field length of less than 9 digits including
2 decimals was not intended for long amounts in the first place.
At a high level, there are the below impacts to your objects due to the extended amount
field lengths:
There are code changes that may be necessary to adapt, irrespective of whether you
will support the provided amount field length extension or not. This is necessary
to avoid runtime errors and syntax errors once you upgrade to S/4HANA 1809 or
higher. Refer to notes 2628040, 2610650 for more information.
If you choose not to support the provided amount field length extension in your code,
although you interact with modules that do support and/or use extended amounts,
adjustments may be necessary to ensure that your code is not impacted. Refer to
notes 2628040, 2628699, 2628704, 2628706, 2628724 for more information.
If you choose to support the provided amount field length extension, enablement is
necessary and adjustments should be made. Note, however, that your enablement
is directly dependent on the areas where the provided amount field length
extension is supported in SAP S/4HANA 1809 or later. Refer to notes 2628040,
2610650, 2628617, 2628641, 2628699, 2628704,2628706 2628714, and 2628724,
In the following section, we will provide an introduction to what has been done to enable
the extended amounts in S/4HANA, and explain how it affects your code. For more
information, see attached notes under section "References".
Consistent Usage in System-Internal Code
Decoupling
The consistent behavior of the SAP system is secured through the use of data dictionary
objects, data elements and domains. The relevant internal fields that are typed to these
data elements derive their technical details (for example, data type, length, decimals, etc.)
from the domain. Cross-usages of the data elements to be extended existed between the
application areas that will use the provided amount field length extension, and the
application areas that will not use extended amounts. To maintain data integrity and
compatibility between these areas while preventing any impact on user interfaces,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 405
database entries, external interfaces, etc., the cross-usages had to be identified and
decoupled. We created new data elements and introduced them in the data dictionary
objects in the areas without the provided amount field length extension.
For more information, see related SAP Note 2628040.
Code Adaptation
To facilitate the correct handling of the extended amount fields within the ABAP coding,
the specific circumstances and requirements of each possible scenario were
considered. Overflow errors could occur if an extended amount is moved into a shorter
amount. Syntax errors and report generation errors can be identified though S/4HANA
Readiness code scans.
The decoupling activities together with the amount field length extension created type
conflicts due to a mismatch between data elements assigned to each other in one
statement. All amount fields referring to an extended data element had to be checked to
ensure that these fields were long enough to hold the extended amounts. If the dependent
fields were also extended, all usages of these fields had to be analyzed as well. Extending
one field typically triggered follow up changes. Overall, the complete data flow had to be
analyzed to identify all places where an extended amount is moved into a shorter amount
field. Such analysis must also be done in your custom coding.
The described changes have also been applied to local interface signatures, including
function modules, class methods, form routines, BAdIs and so on. The types and
structure parameters of these local calls were also extended wherever an amount field
exists. External interfaces were also adapted. However, a different approach was taken
for these remote calls.
For more information, see related SAP Note 2610650.
Storage of an Amount on the Database
By extending the data elements of an amount field, the field length on the database is also
extended. Although the maximum length is larger, the manner in which the content is
stored has not changed. There is no difference in how an amount is stored on the
database in SAP S/4HANA 1809 compared to previous versions of S/4HANA as well as
in the SAP Business Suite. No data conversions are needed unless an amount is part of
concatenated content. Concatenation in the code uses the complete technical length of the
field, which is now longer, and is also reflected in the database content.
Internal Interfaces
Interface related conflicts will occur if the lengths of actual and formal parameters are no
longer the same. These type conflicts were found in the internal interface calls between
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 406
different applications as well as in the interface calls within the same application. A
variance in the formal and actual parameters will result in a syntax error or a short dump
at run time. Resolving local interface conflicts depends mainly on the direction of the
call (are the caller and receiver using extended amounts?) and data flow (importing,
exporting, using, changing, or returning parameter) within each call had to be
analyzed. The parameter could either be a structure/table or it could be a single
field. For more information, see related SAP Note 2628699.
Write Statements for List Output
When amount fields that are extended are used in WRITE statements for list processing,
they may cause the list to go out of alignment and overlapping values independent of
whether the provided amount field length extension is active or not. Data can
be truncated or completely lost if no adjustment is made. Other write statements might
need adjustments in case of multi-row output, printing column headings, or splitting the
preparation of one row into multiple WRITE statements. For more information,
see related SAP Note 2610650.
Strict Type Checks
There are statements within the ABAP code that require strict type checks where data
elements assigned to each other must have the same data type and length. A syntax error
will be issued when the fields within the statement are incompatible. Conflicts will occur
if an extended amount is used in this type of statement within an application area that is
not using the provided amount field length extension. There is no implicit type
conversion done in this case. Adjustments are necessary to avoid syntax errors. This can
be solved with the help of an auxiliary variable or by changing the type to the copied data
element. For more information, see related SAP Note 2610650.
External Interfaces
A typical ERP system is connected to miscellaneous internal and external (SAP or non-
SAP) systems. Accordingly, an S/4HANA system with the provided amount field length
extension activated in customizing must consider that not all related systems will be able
to handle extended amounts. Furthermore, it cannot be assumed that all ERP systems in
your landscape will be converted or upgraded to SAP S/4HANA 1809 at the same point
in time. That means that the external interfaces that are used for integration must be able
to function as in the previous 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 amount fields in these interfaces would technically break how
they interact with the inbound and outbound calling programs.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 407
As mentioned above, we used a different approach for internal and released external
APIs. 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 remains with its original length, and an additional extended field is
added at the end of the structure parameter (or as an additional single parameter) allowing
for transmision of the extended lengths. It must be ensured that no extended field can be
maintained in the system with a content length greater than the original length of the
field.
It must be ensured that any released external API containing an extended amount field as
a single parameter or as part of a structure parameter, can be called internally or locally
within one system. Hence, when the provided amount field length extension is activated
in customizing, all internal calls of external interfaces must only use the extended fields.
The changes described were done for BAPIs, IDocs, and released remote-enabled
function modules, and where necessary, unreleased remote enabled function modules
used to communicate with other SAP Business Suite products like other SAP ERP
installations 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 in SAP
Notes 2628699, 2628706 and 2628704.
Refer to notes 2628040, 2628724 for more information.
System Settings to Activate the Provided Amount Field Length Extension in
Customizing
When converting from the SAP Business Suite System, or upgrading from an older
version of SAP S/4HANA, to SAP S/4HANA 1809 or later, the amount field
length extension is not activated in customizing by default.
Note: Once the provided amount field length extension is activated in customizing, it
cannot be deactivated.
The activation is realized as a client-dependent customizing table that can be accessed in
Customizing via the following path:
Cross-Application Components -> General Application Functions -> Field Length
Extension -> Activate Extended Fields
Set the checkbox for Extended Amount Length and SAVE.
Alternatively, transaction FLETS. Authorization group FLE [authorization object
S_TABU_DIS] is required for table maintenance.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 408
Below is a list of functions that can be used with the amount field length extension:
Manage Profit Center Groups
Manage Profit Centers
Edit Master Data – Profit Centers – Collective
This process step is to make changes to large quantities of profit center master data
without having to change the master data for each single profit center.
Edit Company Code Assignment Profit Centers
In this activity, you make changes to the company code assignments of a larger number
of profit centers without having to change the master data for each single profit center.
Display Parked Journal Entries
You can use document parking to enter and store (park) incomplete documents in the
SAP System without carrying out extensive entry checks. Parked documents can be
completed, checked, and then posted later or deleted – if necessary by a different
accounting clerk. With this app you can display parked documents.
Parked Journal Entry Changes
You can use document parking to enter and store (park) incomplete documents in the
SAP System without carrying out extensive entry checks. Parked documents can be
completed, checked, and then posted later or deleted – if necessary by a different
accounting clerk. With this app you can track all changes made in parked journal entries.
Post General Journal Entries
You receive G/L account documents that must be posted manually in the SAP
system. When posting to the balance sheet accounts only, you only need to make an
entry in the Segment field. If the field is left blank segment 1000_C will be defaulted and
will need to be reconciled.
Upload General Journal Entries
You receive G/L account documents that must be posted manually in the SAP
system. When posting to the balance sheet accounts only, you only need to make an
entry in the Segment field. If the field is left blank segment 1000_C will be defaulted and
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 409
will need to be reconciled. The app allows for multiple G/L account documents to be
uploaded using a single upload file.
Verify General Journal Entries
You use Verify General Journal Entries for Requester to enter a journal entry which
needs to be checked before final posting. You can check the status of the documents
submitted for verification in various tabs: All, Submitted, Rejected and Others. For those
rejected, you can edit and submit again for approval to Processor. Documents with status
Submitted have not been posted yet. Once approved by the processor, the document is
posted automatically and it can be seen in the SAP Fiori App Manage Journal Entries.
Approve Verify General Journal Entries (for Processor – Inbox)
You receive G/L account documents that need to be checked before final posting. After
checking the documents, you can either approve or reject with a comment/ reason. Once a
document has been selected and approved, it disappears from the list. If a document is
approved, posting of FI document is automatically triggered.
Reject Verify General Journal Entries (for Processor – Inbox)
You receive G/L account documents that need to be checked before final posting. After
checking the documents, you can either approve or reject with a comment/ reason. Once a
document has been selected and rejected, it disappears from the list and goes back to the
requester.
Edit a Rejected Verify General Journal Entry (Requester)
The G/L account documents need to be checked before final posting. The document you
submitted is rejected and for it to be approved and posted you need to make the changes
requested by the approver.
Manage Journal Entries
Display G/L Account Balances
Display G/L Account Line Items – Reporting View
Display G/L Account Line Items – Posting View
Manage Recurring Journal Entries
This functionality supports postings that can periodically be created on a regular basis.
Recurring entries are similar to standing orders with banks for debiting rent, contribution
payments, or loan repayments directly. The postings are done by the recurring entry
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 410
program based on the recurring entry documents. In G/L accounting, recurring entries
can be used for example, for periodic posting of deferrals and accruals, if there are fixed
amounts to be posted. The following data of a recurring entry document remains
unchanged:
Posting Key
Account
Amount
You only need to enter the data that changes occasionally in a recurring entry document.
This document does not result in transaction figures being updated. The recurring entry
program uses this document to create a journal entry.
Display changes of Recurring Entry
Clear G/L Accounts – Manual Clearing
Clear G/L Accounts
For detailed information, refer to the J58 Best Practices page
at https://rapid.sap.com/bp/#/scopeitems/J58.
Other Terms
Amount Field Length Extension, 23 digits, Currency, Decoupling
14.8 S4TWL - Removal of D/C Indicator from Editing Options
Application Components:FI-GL-GL-A
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2865285
S4TWL - Removal of D/C Indicator from
Editing Options
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 411
The "D/C indicator as +/- sign" cannot be used anymore in Enjoy transactions after
conversion / upgrade to S/4 HANA 1809 or higher.
Reason and Prerequisites
Changed behaviour of the amount fields after AFLE conversion introduced with S/4
HANA 1809.
Solution
Implement the attached correction instructions or import the specified support package.
The correction will remove the "D/C indicator as +/- sign" from the editing options
screen, as negative values
in the amount fields are not allowed after AFLE conversion.
How to Determine Relevancy
The affected transactions are: FB50, FB50L, FV50, FV50L, FB60, FB65, FV60, FV65,
FB70, FB75, FV70, FV75.
Required and Recommended Action(s)
Educate your users about this change in UI behaviour.
Other Terms
RFOPTE-XSHKE, AFLE, negative values, D/C indicator.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 412
15.Financials - International Trade
15.1 S4TWL - Material classification with commodity codes
Application Components:SLL-LEG-FUN-CLS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2376556
S/4 HANA - Material classification with
commodity codes in SAP S/4HANA
1610
Symptom
You are doing a system conversion to SAP S/4HANA 1610 or a later release.
You classify materials with commodity codes in transaction MM01 / MM02 or you
classify articles with commodity codes in transaction MM41 / MM42.
This functionality (material/article classification with commodity codes) is redesigned in
SAP S/4HANA 1610. Following redesign applies:
1. Management of commodity codes
Old in ECC and S/4HANA 1511: not time-dependent, valid for a country.
New in S/4HANA 1610 onwards: time-dependent, valid for a country or multiple
countries, new app, new data model.
2. Classification of materials/articles with commodity codes
Old in ECC and S/4HANA 1511: not time-dependent, valid for material/article and
plant/site, done in material master apps (e.g. MM01, MM02) or article master
apps (e.g. MM41, MM42), classification of materials/articles can be distributed
via MATMAS/ARTMAS IDoc (outbound and inbound processing possible) and
inbound processing via BAPIs supported.
New in S/4HANA 1610 onwards: time-dependent, valid for material /article and a
country or multiple countries, functionality accessible only via FIORI apps, new
data model, classification of materials/articles cannot be distributed via
MATMAS/ARTMAS IDoc (inbound processing not possible anymore, only
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 413
simplified outbound processing supported) and inbound processing via BAPIs not
supported anymore.
Reason and Prerequisites
Upgrade or conversion to SAP S/4HANA 1610 or later release
Solution
During upgrade to S/4HANA 1610, a XPRA - /SAPSLL/XPRA_1610_MARC_STAWN
- migrates classification data to new data model.
How to Determine Relevancy
This Simplification Item is relevant if you classifly materials using commodity code. You
are likely using this functionality if you find non initial values in field STAWN of table
MARC.
Required and Recommended Action(s)
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.
Go through KBA 2432527 for detailed information on classification functionality in
S/4HANA
Knowledge transfer to key and end users
Other Terms
Material classification with commodity codes, International Trade, STAWN.
15.2 S4TWL - Personal Data in Provider of Information
Application Components:SLL-LEG-ISR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2471388
S/4HANA Intrastat: Maintaining contact
person data in POI master
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 414
Symptom
You use Intrastat reporting in S/4HANA and are upgrading to on-premise release 1709
from lower S/4HANA release (1511 or 1610).
In 1709 release you can not maintain contact person related personal information directly
in 'Maintain Provider of Information' app or transaction /ECRS/POI_EDIT. Rather,
you shall specify a business partner of type 'Person' and with BP role 'SLLSTL' (Person
Responsible) in the POI master data.
Reason and Prerequisites
In the provider of information (POI) master data record, the data related to contact person
of this POI is stored. This contact person data is used for some countries when creating a
declaration file to transmit this data with the file to authority. New data security and
privacy regulations require special treatment of person related data. To be compliant
with these regulations the data related to the contact person of POI should not be stored
anymore in POI master data record, but as a business partner of type person. In the POI
master data only the reference to the business partner should be stored.
Solution
If Intrastat authorities in your country require 'contact person' information, proceed as
follows.
1. A new business partner(BP) role 'SLLSTL' is delivered in client 000. Either copy the
role from client 000 or create the BP role manually in affected business client. To create
BP role manually proceed as follow:
- Transaction SPRO -> Cross Application Components -> SAP Business Partner ->
Basic Settings -> Business Partner Roles -> Define BP Roles.
- Define a BP role category as 'SLLSTL'. Specify the title and description as 'Person
Responsible'. Specify business partner category as 'Person'.
- Next create a new BP role 'SLLSTL' with title and description as 'Person Responsible'.
Specify BP role catogory as 'SLLSTL'.
- Save.
2. Create Business partner of type 'Person' and BP role 'SLLSTL' (Person Responsible).
Maintain relevant personal information (like Name, E-mail, Telephone, Mobile number
etc.)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 415
3. In transaction /ECRS/POI_EDIT (or app 'Maintain Provider of Information'), specify
the business partner number as Contact Person
Other Terms
Provider of Information (POI), Personal Data, /ECRS/RP_EDIT, /ECRS/POI_EDIT,
Contact Person, S/4HANA OP 1709.
15.3 S4TWL - Determination of default values in Intrastat reporting
Application Components:SLL-ITR-ISR, SD-FT-GOV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2468294
S4TWL - Determination of default
values in Intrastat reporting
Symptom
You use Intrastat reporting in SAP S/4HANA and are upgrading to on-premise release
1709 or higher.
With SAP S/4HANA 1709, the determination of default values for business transaction
type, procedure and movement code has been changed in a way that some tables and
fields become obsolete and new customizing activities are introduced instead. You shall
not maintain the defaults values in the obsolete tables and fields anymore. Rather, you
shall specify the defaults values in the new customizing activities.
Reason and Prerequisites
Reason for this change is the following:
Before release 1709, the determination of defaults values for business transaction
type, procedure and movement code for sales is based on organizational data. This
can result in a high number of redundant data. With release 1709, the
determination of defaults values for business transaction type, procedure and
movement code for sales is not based on organizational data anymore.
Before release 1709, the determination of default values for business transaction type
and procedure for receipts and returns to supplier in intercompany sales requires
conversion of the code list for business transaction type and procedure from one
country to another. This conversion is not possible for all country combinations.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 416
With release 1709, the determination of default values for business transaction
type and procedure for receipts and returns to supplier in intercompany sales does
not require conversion of the code list anymore.
With release 1709, the determination of the procedure based on the procedure in the
customizing activity for stock transfer is not required anymore. Therefore, the
procedure in the customizing activity for stock transfer become obsolete.
Solution
Description
With release 1709, the determination of default values for business transaction type,
procedure and movement code is as follows:
The determination of the default values for sales is based on the customizing activity
“Define Default Values for Sales”. In this customizing activity the default values can be
defined depending on country of declaration, sales document item category and material
group for export and import. Sales document item category is taken from the billing
document and material group is determined from the material and delivering plant. Note
that if the material group is not initial and no default values are defined for this material
group, the second access with initial value for material group is done for determination of
default values in this customizing activity.
The determination of the default values for receipts from supplier in purchasing is based
on the customizing activity “Define Default Values for Purchasing”.
The determination of the default values for returns to supplier in purchasing is done in
two steps: in the first step, the defaults values for receipts from supplier based on the
customizing activity “Define Default Values for Purchasing” are determined and, in the
second step, the conversion of these default values based on the customizing activities
“Define Business Transaction Type for Returns to Supplier” and “Define Procedure for
Returns to Supplier” is done.
Business Value
With the new solution the following is achieved:
Reduce the number of entries to be maintained for determination of default values for
sales by removing the dependence of default values on organizational data (sales
organization, distribution channel and division).
Allow the definition of defaults values for receipts and returns to supplier in
intercompany sales that is valid for all country combinations and without
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 417
maintaining the conversion of code list for business transaction type and
procedure
Required and Recommended Action(s)
The following tables and fields become obsolete in release 1709:
Customizing table T605Z: Foreign Trade: Proposal for Bus. Transaction Type in
Export
Customizing table T616Z: Foreign Trade: Proposal for Procedure in Export
Customizing table T605U: Foreign Trade: Convert Export/Import Bus. Trans. Type
Customizing table T616U: Foreign Trade: Import/Export Procedure Conversion
Field T161W-EXPRF: Procedure in customizing table T161W: Order Types for
Stock Transfer
The following customizing activities should be used instead:
Define Default Values for Sales (SM30-view /ECRS/V_TDVS)
Define Default Value for Purchasing (SM30-view /ECRS/V_T161B)
Define Business Transaction Type for Returns to Supplier (SM30-view
/ECRS/V_TBTR)
Define Procedure for Returns to Supplier (SM30-view /ECRS/V_TPRR)
The migration should be done as follows:
Define determination of the default values for sales including receipts and returns to
supplier in intercompany sales based on the customizing activity “Define Default
Values for Sales” (SM30-view /ECRS/V_TDVS)
Define determination of the default values for receipts from supplier in purchasing
based on the customizing activity “Define Default Value for Purchasing” (SM30-
view /ECRS/V_T161B)
Define determination of the default values for returns to supplier in purchasing based
on the customizing activities “Define Business Transaction Type for Returns to
Supplier” (SM30-view /ECRS/V_TBTR) and “Define Procedure for Returns to
Supplier” (SM30-view /ECRS/V_TPRR)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 418
Test and validate the correctness of determination of the default values in the
selection reports RVEXST00 and RMIMST00 for all Intrastat relevant sales and
purchasing processes
How to Determine Relevancy
You are upgrading to S/4HANA on premise edition 1709 or higher, you use Intrastat
reporting, and data exists in at least one of the following tables or fields:
Customizing table T605Z: Foreign Trade: Proposal for Bus. Transaction Type in
Export
Customizing table T616Z: Foreign Trade: Proposal for Procedure in Export
Customizing table T605U: Foreign Trade: Convert Export/Import Bus. Trans. Type
Customizing table T616U: Foreign Trade: Import/Export Procedure Conversion
Field T161W-EXPRF: Procedure in customizing table T161W: Order Types for
Stock Transfer
Other Terms
Intrastat
15.4 S4TWL - Company code address data in provider of information
Application Components:SLL-ITR-ISR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2782281
S/4HANA Intrastat: Reuse address data
from company code in Provider of
Information
Symptom
You use Intrastat reporting in S/4HANA and are upgrading to on-premise release 1909 or
higher.
From 1909 release you can not maintain address data of POI(Provider of Information)
directly in 'Maintain Provider of Information' app or transaction /ECRS/POI_EDIT.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 419
This address data already exists in the system defined as the address data of the company
code POI is created for.
Therefore, the address data of the company code should be reused for the POI and not
entered in the app 'Maintain Provider of Information' anymore.
Reason and Prerequisites
This is to remove redundant address maintenance in app 'Maintain Provider of
Information'.
Solution
In the app 'Maintain Provider of Information' the address data is not entered anymore but
displayed from the address data of the company code.
IMPORTANT: Please take backup of address defined for POI in transaction
/ECSR/POI_EDIT before upgrade to 1909 as this data will be lost after upgrade. This is
to ensure that incase you have correct address data defined directly in POI and not in
company code, then after upgrade you dont loose the address information and use it to
specify the correct address data in company code.
Other Terms
Provider of Information (POI), Address Data, /ECRS/POI_EDIT, Company Code,
S/4HANA OP 1909.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 420
16.Financials - Treasury and Risk Management
16.1 S4TWL - Drilldown Reporting in Treasury and Risk Management
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270522
S4TWL - Drilldown Reporting in
Treasury and Risk Management
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
Currently there is no pre-upgrade check available to check if this simplification item is a
valid restriction for your system conversion.
The drilldown reporting has been disabled for Treasury and Risk Management. You can't
use your reports defined with the drilldown reporting.
For reporting purposes, you can use the following logical databases available for the
Treasury and Risk Management:
FTI_TR_CASH_FLOWS
Treasury Payment Information
FTI_TR_CASH_FLOWS_2
Treasury Payment Info + addtnl position attrs
FTI_TR_POSITIONS_2
Treasury : Positions Eval + addtnl position attrs
FTI_TR_THX_HEDGE
Treasury P-Hedge Accounting Reporting
FTI_TR_DEALS
Treasury Transaction Reporting
FTI_TR_EXP_POS
Treasury: Exposure Positions
FTI_TR_HEDGE
Treasury E-Hedge Accounting Reporting
FTI_TR_PERIODS
Treasury: Period-Based Evaluations
FTI_TR_PERIODS_1
Treasury: Period Analysis Projection
FTI_TR_PERIODS_2
Treasury: Period-Based Eval + addtnl postn attrs
FTI_TR_PL_CF
Treasury: Revenue and Cash Flow Reporting
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 421
FTI_TR_PL_CF_2
Treasury: Revenue and Cash Flow Reporting
FTI_TR_POSITIONS
Treasury Positions
FTI_TR_POSITIONS_1
Treasury Positions Projection
Based on these logical databases you can use the SAP Query functionality available in
the area menu of the Treasury and Risk Management under Transaction Manager ->
Infosystem -> Tools -> SAP Query and define your own queries using Maintain Queries
(transaction SQ01), Maintain InfoSets (transaction SQ02) and Maintain User Groups
(transaction SQ03).
In addtion you can use the available reports in the area menu of the Treasury and Risk
Management under Transaction Manager -> Infosystem -> Reports.
Other Terms
S4TC, S/4 Transition
16.2 S4TWL - Master Agreements
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270523
S4TWL - Master Agreements
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 422
agreements 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.
Other Terms
S4TC, S/4 Transition
16.3 S4TWL - Offers
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270526
S4TWL - Offers
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
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.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 423
S4TC, S/4 Transition
16.4 S4TWL - Simulation in Transaction Management
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270527
S4TWL - Simulation in Transaction
Management
Symptom
You are planning a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
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 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.
Other Terms
S4TC, S/4 Transition
16.5 S4TWL - Quantity Ledger Always Active for Money Market
Transactions
Application Components:FIN-FSCM-TRM
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 424
Note Type
Note Number
Note Description
Business Impact
2270529
S4TWL - Quantity Ledger Always Active
for Money Market Transactions
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
Description
The quantity ledger is now always used for OTC transactions.
Business Process Related Information
The quantity ledger is a technical prerequisite for the function valuation class transfer.
Required and Recommended Action(s)
Before you make the conversion to SAP S/4HANA, you should set the quantity ledger
active for OTC transactions in your ERP system.
In the Customizing of the Treasury and Risk Management under Transaction Manager -
> General Settings -> Tools -> Conversion -> Conversion Customizing -> Set Migration
Type and Assign to Customizing Request choose the migration type Conversion from >=
Enterprise 2.0 and <= ERP 6.0. Assign your transport request and enter the names of
your logical systems of your production system, test system, and customizing system.
Under Transaction Manager -> General Settings -> Tools -> Conversion Program
(transaction TPM_MIGRATION) you now execute first the step H02 OTC: Adjust
Valuation Class in Bus. Transactions (Optional) and then the step H03 OTC: Generate
Quantity Positions (Optional).
Upgrade Pre-Check
The pre-check for the SAP S/4 HANA transition of the quantity ledger functionality
raises an error with check-id SI14_TRQ (message ‘Conversion required: Client …,
Company Code … . See SAP note 2270529.’) if it finds company codes in at least one
client, with the exception of clients 000 and 066, which require generation of quantity
positions. Generation of quantity positions is required if an entry exists in table
TRGT_MIG_CC_PT providing a defined conversion status which is incomplete. If there
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 425
is no entry in table TRGT_MIG_CC_PT or the check finds otherwise an undefined
conversion status, it further checks table TRQT_BUSTRANS where for each business
transaction a corresponding entry has to exist. If there are no entries in
TRQT_BUSTRANS for at least one business transaction, the pre-check raises the same
error.
For SAP Enhancement Packages < 3 for SAP ERP 6.0 (EA-FINSERV 600), the pre-
check raises a skippable message with check id SI14_ACCR (message ‘Conversion
required. See SAP note 2270529.’). This message does not show an insistency and can be
skipped during the SUM upgrade. Note that you have to do the conversion after finishing
the upgrade.
Other Terms
S4TC, S/4 Transition
16.6 S4TWL - Several Kinds of Financial Objects Disabled
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270530
S4TWL - Several Kinds of Financial
Objects Disabled
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
SEM Banking is not part of SAP S/4HANA edition. So the creation of the following
outdated kinds of financial objects of SEM Banking has been disabled in function
Process Financial Objects (transaction JBDO) of the Risk Analyzers of the Treasury and
Risk Management:
Security Order
Namespace of Financial Object: T2*
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 426
Master Data Maintenance Transaction: JBWPORD
[IMPORTANT] The namespace T2* is shared between the security order of
SEM Banking (maintained via transaction JBWPORD; Radiobutton
"Security Order" in financial object master data transaction JBDO), and
the security transaction of SAP Treasury and Risk Management (financial
transaction created via FTR_CREATE or TS01; Radiobutton
Derivatives/Money Market/Forex/Listed Transaction/Security Transaction
in financial object master data transaction JBDO). The T2*-financial
objects of SAP Treasury and Risk Management are continued to be
supported.
Positions
Namespace of Financial Object: B1*
Master Data Maintenance Transactions: JBB0, JBB1. JBB2
[IMORTANT] This is to be distinguished from the financial objects for
different kinds of positions in SAP Treasury and Risk Management, like
the securities account class position (namespace of financial object: T9*),
class position in futures account (namespace of financial objects: TA*) or
the lot-based position in futures account (namespace of financial objects:
TF*) which are continued to be supported.
Variable Transactions (applies for the SAP Banking application component only)
Namespace of Financial Object: BV*
Master Data Maintenance Transactions: JBVT*
Positions of Fictitious/Simulated Transactions
Namespace of Financial Object: R3*
Master Data Maintenance Transaction: RTBST
Facilities in SAP Banking
Namespace of Financial Object: F2*
Master Data Maintenance Transactions: KLFZ01, KLFZ02. KLFZ03
[IMORTANT] This is to be distinguished from the facility instrument in SAP
Treasury and Risk Management (product category 560) which is
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 427
continued to be supported in SAP S/4HANA edition. The namespace of
the financial object for facilities of product category 560 is T5*.
Non-Interest Profit and Loss Items
Namespace of Financial Object: PL*
Master Data Maintenance Transaction: JBA_US_MD_NIPL
The other financial objects of group 1 (= SAP Banking) and of group 2 (= Treasury and
Risk Management objects) are still available.
Customer code which makes use of coding objects which are specific to the disabled
financial object types is no longer relevant.
Business Process Related Information
The SEM Banking is not part of SAP S/4HANA edition. So these objects are obsolete.
How to Determine Relevancy
Check in the Customizing of your system whether you activated the financial object
integration for these financial objects or not.
Other Terms
S4TC, S/4 Transition
16.7 S4TWL - Allocation of FX Transactions to Financial Documents and
Cash Management
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2524941
S4TWL - Allocation of FX Transactions
to Financial Documents and Cash
Management
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 428
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
The allocation of FX transactions of SAP Treasury and Risk Management to financial
documents of the classical Financial Accounting or to memo records of the classical Cash
Management as a preparational step for special revaluation programs has been disabled
(see also simplification item S4TWL - General Ledger, business impact note 2270339,
and simplification item S4TWL - Cash Management General, business impact note
2270400).
There is no successing function offered.
In case of transferring FX hedging effects of SAP Treasury and Risk Management to
the new General Ledger using hedge accounting rules contact SAP for further
information of the new functionality.
Other Terms
S4TC, S/4 Transition
16.8 S4TWL - Correspondence Functionality
Application Components:FIN-FSCM-TRM-TM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270450
S4TWL - Correspondence Functionality
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
Business Value
Starting with SAP enhancement package 4 for SAP ERP 6.0 the Treasury and Risk
Management provides a new correspondence framework for incoming and outgoing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 429
correspondence. Within SAP enhancement package 5 for SAP ERP 6.0 this
correspondence framework was enhanced.
This new correspondence framework offers a higher automation in the correspondence
processing and a higher flexibility. Details can be found in the EKT Material of
Enhancement Package 4 and 5.
Description
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.
From SAP S/4HANA OP 1511 on the new correspondence framework is the only possible
way to manage incoming and outgoing correspondence. The support of SAPScript ceases
with the new correspondence framework.
Required and Recommended Action(s)
Customers have to implement the Correspondence Framework before they go to SAP
S/4HANA OP 1511 or subsequent releases.
If you are not using old correspondence functionality and you do not plan to use the
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 the Correspondence Framework is technically available, you need to
activate the Correspondence Framework and create necessary customizing before
upgrading to SAP S/4HANA. 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 (which is an own project and needs time).
If you use the old correspondence functionality and upgrade to S/4HANA from an older
release where the correspondence framework is technically not available, you will get an
error message during migration. Skip this error message, which is only relevant for the
correspondence framework, and proceed with migration to SAP S/4HANA. If you want
to use the correspondence framework in SAP S/4HANA, set up the customizing for it
manually (this is a separate project and takes time).
Pre-Upgrade-Check
The pre-upgrade check for SAP S/4HANA transition issues an error with check ID
SI1_TCOR if business function FIN_TRM_CORR_FW (more
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 430
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 the last year (database table VTBKORES contains an according
entry).
Information: SAP reserved clients 000 and 066 are exempt from the check.
You can skip this error directly.
Other Terms
S4TC S/4 Transition
16.9 S4TWL - Interest Rate and Yield Curve Functionality
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270461
S4TWL - Interest Rate and Yield Curve
Functionality
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
With the new yield curve framework customers can benefit from
More flexibility in the calculation of net present values of financial transactions
The ability to comply with accounting standards like IFRS13
The possibility to reduce the number of yield curves for which market data needs to
be stored
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 431
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 SI2_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 066 are exempt from the check.)
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 432
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
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.
16.10S4TWL - Accrual/Deferral of Expenses and Revenues
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270462
S4TWL - Accrual/Deferral of Expenses
and Revenues
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
As of SAP Enhancement Package 3 for ERP 6.0 (EA-FINSERV 603), Business Function
TRM: Hedge Accounting, New Financial Products, New Key Figures a central function
for Accrual/Deferral of Expenses and Revenues (transaction TPM44, reversal transaction
TPM45) for all financial transactions is available.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 433
The accrual/deferral functions for OTC transactions (transactions TBB4 and TBB5) have
been replaced by this new functionality.
In SAP S/4HANA only this central function is available.
The accrual/deferral functions of transactions ACCR01 - ACCR07 plus accompanying
transactions are no longer supported.
Required and Recommended Action(s)
If you are upgrading from SAP Enhancement Packages >= 3 for SAP ERP 6.0 (EA-
FINSERV 603 ff.), and you are still using the old functionality, you have to switch to the
new functionality before you make the conversion to SAP S/4 HANA edition.
If you are upgrading from SAP Enhancement Package < 3 for SAP ERP 6.0 (EA-
FINSERV 600) to S/4HANA and you are still using the old functionality for the
accrual/deferral of expenses and revenues for OTC transactions, you may continue the
conversion to S/4HANA, because the needed migration tool is not available on this
release. However, you have to switch to the new functionality after finishing the upgrade
to SAP S/4HANA edition.
Conversion to the new Functionality
In the Customizing of the Treasury and Risk Management under Transaction Manager -
> General Settings -> Tools -> Conversion -> Conversion Customizing -> Set Migration
Type and Assign to Customizing Request choose the migration type Conversion from >=
Enterprise 2.0 and <= ERP 6.0. Assign your transport request and enter the names of
your logical systems of your production system, test system, and customizing system.
In your Customizing system in the Customizing of the Treasury and Risk Management
under Transaction Manager -> General Settings -> Tools -> Conversion Program
(transaction TPM_MIGRATION) you now execute the report G01 OTC: Convert
Customizing for Accrual/Deferral.
When the new Customizing is available in the productive system, execute the
step H01 OTC: Convert Accruals/Deferrals available in the Customizing of the Treasury
and Risk Management under Transaction Manager -> General Settings -> Tools ->
Conversion Program (transaction TPM_MIGRATION).
Upgrade Pre-Check
The pre-check for the SAP S/4 HANA transition of the accrual/deferral functionality
raises an error with check-id SI3_ACCR (message ‘Conversion required: Client …,
Company Code … . See SAP note 2270462.’) if it finds company codes in at least one
client, with the exception of clients 000 and 066, which require conversion. Conversion is
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 434
required if an entry exists in table TRGT_MIG_CC_PT providing a defined conversion
status which is incomplete. Undefined conversion status are checked in table
TRDT_TRDBUSTRANS where at least one business transaction for the company code
and one of the versions “Enterprise 2.0 to ERP 2005”, “Enterprise 1.10” or “CFM 1.0 SP
4 to CFM 2.0” has to exist.
For SAP Enhancement Packages < 3 for SAP ERP 6.0 (EA-FINSERV 600), the pre-
check raises a skippable message with check ID SI3_ACCR (message ‘Conversion
required. See SAP note 2270462.’). This message does not show an inconsistency and
can be skipped during the SUM upgrade. Note that you have to do the conversion after
finishing the upgrade.
Other Terms
S4TC, S/4 Transition
16.11S4TWL - Credit Risk Analyzer Link to Cash Management
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270470
S4TWL - Credit Risk Analyzer Link to
Cash Management Disabled in
S/4HANA
Symptom
You are planning a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
Description
The link from classical Cash Management to the Treasury and Risk Management
analyzers (transactions RMCM and KLMAP) has been disabled in S/4 HANA.
Instead with SAP S/4HANA 1709 Bank Account Management is integrated with the
Market Risk Analyzer and the Credit Risk Analyzer of the Treasury and Risk
Management by a new type of financial object for bank account balances.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 435
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 SAP 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 futher 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 any more.
If you want to use the integration of Bank Account Management with Treasury and Risk
Management in SAP S/4HANA 1709, you have to setup the automatic integration of
financial objects for bank accounts.
Other Terms
S4TC, S/4 Transition
16.12S4TWL - Exposure Management 1.0
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2340804
S4TWL - Exposure Management 1.0
within Treasury and Risk Management
Symptom
You are planning a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 436
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).
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 futher mandatory action is required.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 437
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 any more.
Other Terms
S4TC, S/4 Transition
16.13S4TWL - Drawable Bonds
Application Components:FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270521
S4TWL - Drawable Bonds
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA transition worklist item is applicable in this case.
Solution
Description
Drawable bonds based on product category 041 are not available within SAP S/4HANA,
on-premise edition 1511, and subsequent releases.
Other Terms
S4TC, S/4 Transition
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 438
17.Financials – Miscellaneous
17.1 S4TWL - Credit Management
Application Components:FI-AR-CR, FIN-FSCM-CR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270544
S4TWL - Credit Management
Symptom
You are doing a system conversion to SAP S/4HANA and you are using Credit
Management (FI-AR-CR) on SAP ERP. In this scenario, the following SAP S/4HANA
Transition Worklist item applies.
Solution
In the following we distinguish between the three possible constellations in your system:
You are only using FI-AR-CR Credit Management in your source release
You are only using SAP Credit Management (FIN-FSCM-CR) in your source release
You are using both Credit Management solutions (FI-AR-CR & FIN-FSCM-CR) in
your source release
You are not using any of the Credit Management solutions (Then this note is not
relevant for you)
(with the prefixes A, B, C, D we mark the explanations as relevant for these scenarios in
the following chapters)
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).
Risk category -> Risk class maintained for the whole business partner (not per
customer & credit control area), as the probability of a credit default of your
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 439
customer does depend on the characteristics of your customer and not your
internal organizational structures.
Maintenance of customer master data in business partner transaction
The credit checks carried out for a customer depend on the assigned check rule in the
business partner transaction. They do not depend on the risk class (formerly risk
category).
Releasing blocked documents via Case Management (documents the blocking reason)
How to Determine Relevancy:
A: Indicators for the usage of FI-AR-CR Credit Management are:
You are using transaction FD31 or FD32 to maintain credit account master data (this
data is stored in table KNKK & KNKA)
You are using transactions VKM1-4 to process sales documents (e.g. releasing
blocked sales orders)
Function module UKM_IS_ACTIVE returns space for flag E_ACTIVE and
E_ERP2005
In general: You are using parts of the obsolete transactions and reports listed in
chapter “Business Process related Information”.
Exposure data is stored and updated continuously in database tables S066 and S067.
B: Indicators for the usage of SAP Credit Management (FIN-FSCM-CR) are:
You are using transaction BP or UKM_BP to maintain credit account master data
(this data is stored in table UKMBP_CMS_SGM & UKMBP_CMS)
You are using transaction UKM_CASE to process sales documents (e.g. releasing
blocked sales orders)
Function module UKM_IS_ACTIVE returns ‘X’ for parameter E_ACTIVE and
E_ERP2005
C: Indicators of A and B apply for you.
D: None of the indicators of A and B apply for you.
Business Value:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 440
Higher degree of automation, thanks to automatic calculation of credit scores, risk
classes and credit limits
Credit events help the credit analyst to focus on exceptions during his daily business
Create a relationship from credit analysts to customers
Process of credit limit requests
Documented credit decisions
Higher / lower account relationship of business partners (adds up exposure of lower
accounts on higher accounts)
Less redundant data (reading FI-data via HANA view)
Business Process related information:
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR. The migration from one-
system landscapes is supported by tools that SAP provides in the IMG. (see details in
chapter “Required and Recommended Action(s)”)
Influence on Business Processes:
A & B & C: There will be no change to your business processes because of the system
conversion.
A & C: However, some transactions become obsolete and are replaced by new
transactions.
Here are some examples for such cases:
Examples for replaced
transactions in SAP
S/4HANA
For the maintenance of the credit account master data, transaction
FD32 is replaced by transaction UKM_BP.
For releasing credit-blocked sales orders, transaction VKM1 is
replaced by transaction UKM_MY_DCDS.
Transactions not available in
SAP S/4HANA
F.28 - Customers: Reset Credit Limit
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 441
available for Migration checks)
FDK43 - Credit Management - Master Data List
S_ALR_87012215 - Display Changes to Credit Management
S_ALR_87012218 - Credit Master Sheet
VKM1 - Blocked SD Documents
VKM2 - Released SD Documents
VKM3 - Sales Documents
VKM4 - SD 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):
B: Migrating Credit Management is not needed. Review of BadIs
“UKM_R3_ACTIVATE” and “UKM_FILL” is advisable. Think of using the default
implementation provided by SAP. (FI-data will then be read real-time with the default
implementation of BadI “UKM_R3_ACTIVATE”. The implementation of BadI
“UKM_FILL” is then not needed anymore.)
D: Nothing to do, migration of Credit Management is not needed.
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR completely. This migration
comprises several elements:
Configuration data
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 442
Master data
Credit exposure data
Credit decision data
The migration from one-system landscapes is supported by tools that SAP provides.
Reviewing the migrated Customizing is advisable afterwards: For example, risk classes
are now maintained once for a customer (for all segments) instead of maintaining them
per customer’s credit control area.
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:
2227014 (Financials)
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.
C (additionally): Review of BadIs “UKM_R3_ACTIVATE” and “UKM_FILL” is
advisable. Think of using the default implementation provided by SAP.
Related SAP Notes
Custom code-related information (SD)
SAP Note: 2217124
Custom code-related information (Financials)
SAP Note: 2227014
17.2 S4TWL - Technical Changes in Material Ledger
Application Components:CO-PC-ACT
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 443
Note Type
Note Number
Note Description
Business Impact
2332591
S4TWL - Technical Changes in Material
Ledger
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
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.
Solution
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
CKMLPP “Material Ledger Period Totals Records Quantity”
CKMLCR “Material Ledger: Period Totals Records Values”
Access function: CKMS_PERIOD_READ_WITH_ITAB
Material Ledger Document and associated views
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 444
MLHD
MLIT
MLPP
MLPPF
MLCR
MLCRF
MLCRP
MLMST
Access functions: CKML_F_DOCUMENT_READ_MLHD,
CKML_F_DOCUMENT_READ_MLXX
Further tables (with no access function): MLKEPH, MLPRKEKO,
MLPRKEPH
Obsolete database views: MLXXV, MLREPORT, MLREADST
Index for Accounting Documents for Material
CKMI1
Obsolete, no further access possible
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 445
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.
Other Terms
ML, Document, CKMB, CKM3, Period Totals, LBKUM, SALK3
17.3 S4TWL - Real Estate Classic
Application Components:RE-RT, RE-IT, RE-PR, RE-BD, RE-BP, FS-CML, RE-IS, RE-CO, RE-CP,
RE-TP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270550
S4TWL - Real Estate Classic
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 446
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 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.
Other Terms
RE, Classic, real estate management, REMICL, RE-FX Real Estate Management, RE
Classic, RE-Classic
17.4 S4TWL - Conversion to S/4HANA Material Ledger and Actual Costing
Application Components:FIN-MIG-ML
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2352383
S4TWL - Conversion to S/4HANA
Material Ledger and Actual Costing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 447
Symptom
You are doing a system conversion from SAP ERP Business Suite or SAP Simple
Finance to SAP S/4HANA. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
Description
In SAP S/4HANA, the material ledger is mandatory. Therefore, migration of the material
ledger is required in the following scenarios:
Migration from SAP ERP to SAP S/4HANA 1610 or higher
Migration from SAP Simple Finance to SAP S/4HANA 1610 or higher
You always need to migrate the material ledger, even if you were not using the material
ledger in the source system.
Required Action(s)
Before starting the conversion, please make sure to implement relevant SAP Notes that
are mentioned in SAP Note 2345739.
Customizing Migration
Before migrating the material ledger, you need to complete the following IMG activities
under Migration to SAP S/4HANA Finance.
Under Preparations and Migration of Customizing:
Preparations and Migration of Customizing for General Ledger (These
activities only need to be executed if you are migrating from SAP ERP
Business Suite to SAP S/4HANA. If you are already using SAP Simple
Finance 2.0 or higher, they are not relevant.)
Preparations and Migration of Customizing for Material Ledger -> Migrate
Material Ledger Customizing (This activity always needs to be executed,
even if you are migrating from SAP Simple Finance to SAP S/4HANA.)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 448
Data Migration
To start the material ledger migration activities, go to the IMG and navigate to Migration
to SAP S/4HANA Finance -> Data Migration and start the activity Start and Monitor
Data Migration.
For further information, see the IMG documentation on the Start and Monitor Data
Migration activity.
The currency conversion in step M10 and M11 is done via standard exchange rate type
'M'.
The process of migrating the material ledger consists of the following activities in the
Start and Monitor Migration activity:
M10: Migrate Material Ledger Master Data
This activity ensures that the material ledger is activated for all valuation areas, since it is
mandatory in SAP S/4HANA. The activity creates material ledger master data (tables:
CKMLHD, CKMLPR, CKMLPP and CKMLCR) in all material ledger currencies for
periods more recent than the last period of the previous year.
In addition, all existing inventory aggregate values (tables MBEW, EBEW, QBEW,
OBEW) and their complete historic data (tables MBEWH EBEWH, QBEWH, OBEWH)
are migrated into the new universal journal entry table ACDOCA and
ACDOCA_M_EXTRACT. Period records more recent than the last period of the
previous year are converted into material ledger currencies using standard exchange rate
type 'M'. Periods earlier than the last period of the previous year are only migrated in
home currency. During migration, balance carryforward records (fields: BSTAT = ‘C’
and MIG_SOURCE = ‘N’) are created in ACDOCA. If you are already using the material
ledger, existing material ledger records (tables CKMLPP and CKMLCR) are transferred
into ACDOCA and ACDOCA_M_EXTRACT with all existing currency information.
This migration activity does not activate actual costing, since actual costing is still
optional in SAP S/4HANA. However, if you are already using actual costing in the
migration source system, ML data for actual costing will be transferred to new data
structures to enable fast and efficient cost calculation. In particular, the following
database tables will be filled for periods more recent than the last period of the year
before the previous year until the current period.
Attention: The relevant periods are determined via table MARV (fields VVJGJ,
VVJMO, LFGJA, LFMON). Make sure that data in MARV is correct. Do not transport
table entries of table MARV from different systems, where MARV might not be up-to-
date. This can lead to severe data inconsistencies.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 449
Table
Name
Des
crip
tion
Replacement
for
Purpos
e
Re
mar
k
for
Mig
rati
on
MLDOC
Mat
eria
l
Led
ger
Doc
um
ent
MLHD, MLIT,
MLPP,
MLPPF,
MLCR,
MLCRF,
CKMLPP,
CKMLCR,
MLCD,
CKMLMV003,
CKMLMV004,
CKMLPPWIP
etc.
Optimiz
ed data
structur
e for
ML
actual
costing.
Will
be fille
d during
transact
ional
update
of ML
data
and
during
ML
settlem
ent.
Duri
ng
step
M1
0,
dat
a in
ML
DO
C is
cre
ate
d
fro
m
the
last
peri
od
of
the
pre
viou
s
yea
r to
the
curr
ent
peri
od
for
all
valu
atio
n
are
as
whe
re
actu
al
cost
ing
is
acti
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 450
vate
d.
MLDOCCC
S
Mat
eria
l
Led
ger
Doc
um
ent
Cos
t
Co
mp
one
nt
Spli
t
MLKEPH,
CKMLKEPH,
(CKMLPRKEK
O)
Optimiz
ed data
structur
e for
cost
compon
ent split
in ML
actual
costing
Duri
ng
step
M1
0,
cost
com
pon
ent
split
dat
a
are
cre
ate
d
bas
ed
on
ML
DO
C
entr
ies.
MLDOC_E
XTRACT
Extr
act
of
Mat
eria
l
Led
ger
Doc
um
ent
Similar to
MLDOC, but
contains only
information
about quantity
and value. It is
possible to
compress this
table to one
entry per
period and
cost estimate
number via
report
FCML4H_MLD
OC_EXTRAC
T_COMPRES
S.
During
migratio
n, one
entry is
created
for each
combin
ation of
cost
estimat
e
number
,
currenc
y type,
period,
categor
y, and
process
categor
y.
MLDOCCC
S_EXTRA
CT
Extr
act
of
Mat
eria
l
-
Similar
to
MLDOC
_EXTR
ACT
but with
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 451
Led
ger
Doc
um
ent
Cos
t
Co
mp
one
nt
Spli
t
informat
ion per
cost
compon
ent.
Tables
MLDOC
_EXTR
ACT
and
MLDOC
CCS_E
XTRAC
T will
be used
especia
lly to
calculat
e
informat
ion
about
beginni
ng
inventor
y in
specific
period,
by
cumulat
ing
quantiti
es and
values
from all
previou
s
periods.
MLRUNLIS
T
Obj
ect
List
for
Cos
ting
Run
CKMLMV011,
status in
CKMLPP
Informa
tion
about
status
of
material
s and
activity
types in
ML
costing
runs
Duri
ng
mig
rati
on,
tabl
e
ML
RU
NLI
ST
is
fille
d
bas
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 452
ed
on
cost
ing
run
s
cre
ate
d in
the
star
t
rele
ase.
Note
For all ML costing runs created in the start release, the Post Closing step needs to be
finished. It will not be possible to process costing runs created earlier in the new release.
The Posting Logic of the new Actual Costing has been changed in some details. These
changes require the following adjustments in the Account Determination (Transaction
OBYC or IMG -> Materials Management -> Valuation and Account Assignment ->
Account Determination -> Account Determination Without Wizard -> Configure
Automatic Postings).
Transaction PRL (Activity Price Differences):
This transaction was introduced with SAP S/4HANA 1610. It is used for the offsetting
posting of the cost center credit posting (Transaction/Account Modification GBB/AUI).
Maintain the rules and posting key for transaction PRL. Then assign the accounts that
will receive the activity price differences credited to the cost centers. From SAP
S/4HANA 1610 all activity related postings are performed with valuation class <blank>.
It is therefore not necessary to activate the Valuation Modification in the rules of
transaction PRL.
Transaction GBB/Account Modification AUI:
From SAP S/4HANA 1610 all activity related postings are performed with valuation
class <blank>. If you have activated the Valuation Modification in the rules of
transaction GBB, make sure to create an account assignment entry for General
Modification AUI and Valuation Class <blank> also.
Transactions PRV and KDV:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 453
These transactions are obsolete with SAP S/4HANA 1610 (since the new Actual Costing
no longer distinguishes between single-level and multilevel variances).
Their account assignment entries may be removed.
M20: Check Material Ledger Master Data
After performing the material ledger master data migration activity, this activity checks
and verifies the migrated data. For instance, existing values from the inventory and
material ledger tables are compared with aggregation via table ACDOCA.
Check the error messages. Usually no adjustment is necessary for insignificant errors,
such as those from time periods long in the past or from company codes that are not
productive. If you have any doubts, discuss them with your auditor. You have the option
to accept errors that are not to be corrected After you have accepted all errors, you can
continue with the next migration step. If anything was adjusted, you can reset the run and
repeat it.
M11: Migrate Material Ledger Order History
If the material ledger was not active in any valuation area before SAP S/4HANA
conversion, this actvity ensures that all existing purchase order history table records
(tables EKBE, EKBEH, EKBZ, EKBZH) and production order history table records
(tables MLAUFCR and MLAUFCRH) are converted into the material ledger currencies
using standard exchange rate type 'M'.
M21: Check ML Production Order and Purchase Order History
This activity verifies whether all production and purchase order history records have been
converted into the material ledger currencies.
Note
If you want to minimize the amount of data to be migrated, archive or delete any data that
is no longer needed. This will decrease the migration downtime. The relevant tables are
the following:
Inventory valuation tables: MBEWH, EBEWH, QBEWH, OBEWH
Material ledger inventory tables (only relevant if material ledger was active
before SAP S/4HANA migration): CKMLPP, CKMLCR
Purchase order history tables: EKBE, EKBEH, EKBZ, EKBZH
Production order history tables: MLAUFCR, MLAUFCRH
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 454
The migration activities are parallelized using background jobs. Make sure that enough
background jobs are available.
During parallelization, a standard package size of 20,000 is used in all material ledger
migration activities. You may adapt this size by setting user parameter
FML_MIG_PKG_SIZE.
This makes sense e.g. in case step M10 causes issues in Physical Memory of the system,
like Runtime Error ‘TSV_NEW_PAGE_ALOC_FAILED’ (SAPLCKMS).
To do so go to transaction SU3 / Tab "Parameters" -> set parameter
FML_MIG_PKG_SIZE to value 5000 (example) for the user, who is running step M10 in
transaction FINS_MIG_STATUS.
After that Step M10 can be repeated in transaction FINS_MIG_STATUS ->‘Control’ Tab
-> set Cursor on line with step M10 -> press button ‘Next Activity’ -> Resume
Migration.
Other Terms
Migration On-Premise
17.5 S4TWL - Differentiation Category Dependent FS Datasets Not Available
in S/4HANA
Application Components:FS-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2448350
S4TWL - Differentiation Category
Dependent FS Datasets Not Available in
S/4HANA
Symptom
You are doing a system conversion to S/4 HANA On Premise 1610 or higher. In this
release differentiation-category dependent Financial Services data cannot be read or
maintained any more.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 455
The recommended general replication service for distribution of business partners
between systems (BusinessPartnerSUITEBulkReplicateRequest) does not support the
header attribute "Differentiation Category". This means that through this replication
service, differentiation-category dependent data cannot be processed, as long as these
data depend on the differentiation category header attribute of the business partner.
Because of this within Financial Services extension of SAP Business Partner the
following datasets will not be maintainable any more with a differentiation category:
BP1012 - Ratings
BP1013 - Differentiated Attribute
BP3100 - Additional information
Differentiation-Category dependent maintenance within Financial Services Business
Partner roles (for example, FS0003) is not possible any more.
Note that differentiation-independent maintenance of the three datasets is (of course) still
possible.
Solution
Description
Differentiation Category Dependent FS Datasets Not Available in S/4HANA.
Business Process related information
Differentiation category dependent datasets can save data depending on so-called
differentiation categories (for example, different affiliates of a company - each affiliate
could save a separate rating for the business partner). This was possible for Ratings
(database table BP1012), Additional Information (database table BP3100) and
Differentiated Attributes (database table BP1013).
Required and Recommended Action(s)
No action necessary when no differentiation category dependent data have been used in
former release. Only customers who have used differentiation category dependent
datasets in pre-upgrade release might have the need for taking actions. For all other
customers the differentiation-category dependent datasets must not be used.
How to Determine Relevancy
This is relevant for all S/4HANA customers who have used differentiation-category
dependent datasets in the former releases. This can be checked by executing the "number
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 456
of entries" function in transaction SE16 for all three mentioned database tables with the
following selection criteria:
Select "not equal to" space in the corresponding differentiation category field
(DFTVAL for table BP1013, DIFTVAL for table BP1012, CRITER for table BP3100) and
press button "number of entries". If at least one entry is found in any of the tables there
was a usage of differentiation-category dependent data.
Exception: Customers who have used application Credit Management may have
differentiation-category dependent data in tables BP1012 and BP3100. These customers
can continue to use credit management and maintain differentiation-category dependent
data. The restriction is only valid for customers who do not use credit management.
Activities
Customers who have differentiation-category dependent data in one or more of the three
tables should check if these entries are still needed. Only in case this question is answered
with yes the differentiation-dependency can be re-activated by executing the following
steps:
Call up transaction SM30, enter view V_BPCONSTANTS and click Change.
Select constant 'FSDT' and enter constant value '1'.
Save the entry.
With this, the differentiation-category dependent datasets are available again in all
channels (BDT - transaction BP and direct input, BAPI/API, FSBP_READ-function
modules).
Additional Information
The restriction that the differentiation category header attribute is not supported by the
central replication service has been considered in the simplification implementation.
Even if a customer re-activates the differentiation-category dependent datasets, they are
not dependent on the exixstence of a role in table BUT100 with filled key field DFVAL.
With this the data can be replicated to other systems of a system landscape.
Other Terms
Financial Services Business Partner, FSBP, FS-BP, Ratings, BP1012, Differentiated
Attribute, BP1013, Additional Information, BP3100, Differentiation Category,
Differentiation Criterion
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 457
17.6 S4TWL - Product Design Cost Estimate
Application Components:FIN-BA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2442292
S4TWL - PDCE - Product Design Cost
Estimate
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is relevant for you if your start release for the system conversion is SAP ERP
6.0 or any enhancement Package or SAP ERP 6.0 or SAP S/4HANA Finance and if you
are using PDCE functionality.
Solution
Description
The PDCE solution is not available in SAP S/4HANA. Reason for this is that even in
SAP ERP this solution was barely used by customers anymore and customers had moved
to the recommended successor solution (SAP Product Lifecycle Costing or PLC) which is also
available in SAP S/4HANA.
Business Value
The recommended successor solution (SAP Product Lifecycle Costing or PLC ) provides
the following advantages compared to PDCE.
No need to create material master, cost center rates for future periods where customer
is not sure if the offer will come
Integration with SAP ERP and non sap erp systems to load BOMs (e.g. Winchill, or
Baan)
Excel like UI
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 458
Simulation capabilities
Covering lifecycle years not only calculations at a certain valuation date
Able to create and combine single calulations with reference calculations on multiple
levels
Using the full fledged BO Suite for analytics
Integrated in the SAP PLM world
Wide range of easy to use extensibility opions
Business Process related information
The product design cost estimate is a solution for planning, monitoring, and optimizing
the costs of new products during the planning, design, or quoting phase. The costs of
many products are largely determined by engineering. Therefore, you use the product
design cost estimate in an early phase of the product life cycle. At that point, the product
costs can only be approximately estimated with reference to an incomplete data basis, but
you can set the course for the real costs that occur later.
Main transactions not available in SAP S/4HANA on-premise edition
UAMO Product Design Cost Estimate
UAMO_REPORTING UAMO Reporting
UAST Costing Solutions: Structure Maint.
UA_CE_REPORT Costing Engine Analysis
UA_DATABASIS Define Data Basis
UA_IMG IMG for Costing
UA_STRUC_MAINT1 Costing Solutions: Structure Maint.
You can see the whole list of affected PDCE transactions in the content which is
delivered for PDCE in the custom code check. For more detail please refer to notes
2190420, 2241080 and the AS ABAP documentation.
AS ABAP documentation links are herebelow:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 459
https://help.sap.com/saphelp_nw751abap/helpdata/en/9a/e4c2c072b8479f94f52fb2eed12
225/content.htm
https://help.sap.com/saphelp_nw751abap/helpdata/en/34/9d954ade3048bab1ee408ba0da
5c83/content.htm
https://help.sap.com/saphelp_nw751abap/helpdata/en/39/ac9e9ec7164040b1bcde1d09e00
730/content.htm
Required and Recommended Action(s)
Remove all potential references in your custom code to PDCE objects as these may no
longer used any more in SAP S/4HANA. Please use the SAP S/4HANA specific custom
code check in SAP code inspector for this purpose.
If you still need a functionality equivalent to PDCE please look into introducing the
recommended successor functionality (SAP Product Lifecycle Costing or PLC ). For
details please see attached documents.
If you had built custom code extensions on top of PDCE please look into if you still need
them on (SAP Product Lifecycle Costing or PLC) and if required re-implement them
there.
How to Determine Relevancy
This Simplification Item is probably relevant for your, if you have activated any of the
following business functions:
FIN_PDCE_COSTQUOT Cost and Quotation Management
FIN_PDCE_COSTQUOT_CI_1 Cost Estimate and Simulation
FIN_PDCE_PI PDCE, Improved Performance
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 460
18.Human Resources
18.1 S4TWL – Compensation Management
Application Components:PA-CM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224317
S4TWL – Compensation Management
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Compensation Management (PA-CM) functionality is only available in SAP ERP HCM
and SAP HCM in Compatibility Pack in SAP S/4HANA, which comes with limited
usage rights. For more details on the Compatibility Pack and its expiry date and links to
further information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 416.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use Compensation Management (PA-CM) functionality anymore. See SAP Note
3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar functionality is provided with Enterprise
Compensation Management (PA-EC) which needs to be implemented. SAP does not
provide a standard migration tool.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 461
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
Additional information for RISE with SAP S/4HANA Cloud, private edition
customers:
Enterprise Compensation Management (PA-EC) is not available for RISE with SAP
S/4HANA Cloud, private edition customers because this is not part of the offering. See
SAP Note 3091160.
How to Determine Relevancy
This Simplification Item is relevant if you have entries in tables PA0380 or PA0381. That
indicates that you are using the old Compensation Management (PA-CM). If you already
use Enterprise Compensation Management (PA-EC), this simplification item is not
relevant.
Other Terms
Compensation Management, Compatibility Scope, Compatibility Package, SAP HCM for
SAP S/4HANA, PA0380, PA0381
18.2 S4TWL – Personnel Cost Planning
Application Components:PA-CM-CP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224288
S4TWL – Personnel Cost Planning
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Personnel Cost Planning (PA-CM-CP) functionality is only available in SAP ERP HCM
and SAP HCM in Compatibility Pack in SAP S/4HANA, which comes with limited
usage rights.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 462
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 132; 137.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use Personnel Cost Planning (PA-CM-CP) functionality anymore. See SAP Note
3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with Personnel Cost
Planning and Simulation (PA-CP) which needs to be implemented. SAP does not provide
a standard migration tool.
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
This Simplification Item is relevant if you have entries in tables T77KD or HRP1015.
That indicates that you are using the old Personnel Cost Planning (PA-CM-CP). If you
already use Personnel Cost Planning and Simulation (PA-CP), this simplification item is
not relevant.
Other Terms
Personnel Cost Planning, Compatibility Scope, Compatibility Package, SAP HCM for
SAP S/4HANA, T77KD
18.3 S4TWL – HR Employee Interaction Center
Application Components:PA-EIC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224334
S4TWL – HR Employee Interaction
Center
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 463
Symptom
The following SAP S/4HANA Transition Worklist item is applicable in the following
cases:
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to use HCM in Compatibility Pack
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to use SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA)
Reason and Prerequisites
The Employee Interaction Center (PA-EIC) functionality is only available in SAP ERP
HCM. It is already not part of the SAP HCM in Compatibility Pack, see also SAP
S/4HANA Feature Scope Description.
Business Process related information
After the conversion to SAP S/4HANA, it is not allowed to use Employee Interaction
Center anymore.
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use EIC (PA-EIC) functionality anymore. See SAP Note 3091160.
Solution
Before the conversion to SAP HCM for SAP S/4HANA 2022 or higher, check whether
the old functionality is used or not. If not, there are no further actions. If the functionality
is used and still required, please be aware that there is no alternative available. Keep in
mind that a similar functionality is provided with
Interaction center / help desk applications offered by SAP S/4HANA (CRM-S4-IC)
or SAP CRM (CRM-CIC)
SAP Service Cloud
SAP SuccessFactors Employee Central Service Center
which needs to be implemented. You also have the choice to stay on SAP ERP HCM its
expiry date.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 464
This Simplification Item is relevant if Business Function HCM_EIC_CI_1 is activated
and transaction HREIC is executed. That indicates that you are using the Employee
Interaction Center (PA-EIC).
Other Terms
HREIC, Employee Interaction Center, EIC, PA-EIC, Compatibility Scope, Compatibility
Package, SAP HCM for SAP S/4HANA
18.4 S4TWL – Enterprise Services Personnel Administration
Application Components:PA-PA-SOA, PT-SOA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224335
S4TWL – Enterprise Services Personnel
Administration
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 and want to use
SAP Human Capital Management for SAP S/4HANA (in the following called SAP
HCM for SAP S/4HANA). The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Reason and Prerequisites
Enterprise Services from packages PAOC_PAD_SE_PROXY (Personnel Administration)
and PAOC_TIM_SE_PROXY (Time Management) are only available in SAP ERP HCM
and SAP HCM in Compatibility Pack in SAP S/4HANA, which comes with limited
usage rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 419.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it is not allowed to use the
Enterprise Services from packages PAOC_PAD_SE_PROXY (PA-PA-SOA) and
PAOC_TIM_SE_PROXY (PT-SOA). See SAP Note 3091160.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 465
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions. If yes, please
note that there is no alternative functionality.
How to Determine Relevancy
This Simplification Item is relevant if business function HCM_SRV_CI_2 is
activated. That indicates that you are using Enterprise Services.
Other Terms
Enterprise Services, PA-PA-SOA, PT-SOA, Compatibility Scope, Compatibility
Package, SAP HCM for SAP S/4HANA
18.5 S4TWL – Expert Finder
Application Components:PA-XF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224305
S4TWL – Expert Finder
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
The Expert Finder (PA-XF) functionality is only available in SAP ERP HCM and was
already not part of SAP HCM in Compatibility Pack in SAP S/4HANA.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the Expert Finder functionality anymore. See SAP Note 3091160.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 466
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions. If yes, please
note that there is no alternative functionality.
You also have the choice to stay on SAP ERP HCM until its expiry date.
How to Determine Relevancy
This Simplification Item is relevant if you have entries in tables HRP5030 and/or
HRP5031.That indicates that you are using the Expert Finder (PA-XF).
Other Terms
Expert Finder, SAP HCM for SAP S/4HANA, PEXP
18.6 S4TWL – Funds and Position Management
Application Components:PA-PM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224336
S4TWL – Funds and Position
Management
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
The old parts of HR Funds and Position Management(PA-PM) are only available in SAP
ERP HCM and SAP HCM in Compatibility Pack in SAP S/4HANA, which comes with
limited usage rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 424.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 467
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the old parts of HR Funds and Position Management (PA-PM) functionality anymore.
See SAP Note 3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the old functionality is used or not. If not, there are no further actions. If
the functionality is used and still required, a similar function is provided with Position
Budgeting and Control (PA-PM-PB). which needs to be implemented. There is no
automated migration path. You also have the choice to stay on SAP ERP HCM or SAP
HCM in Compatibility Pack in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
This Simplification Item is relevant if you have any entries in filed BSTAT of table table
HRP1500. That indicates that you are using or have used old HR Funds and Position
Management. If you already use Position Budgeting and Control (PA-PM-PB), this
simplification item is not relevant.
Other Terms
HR Funds and Position Management, Compatibility Scope, Compatibility Package, SAP
HCM for SAP S/4HANA
18.7 S4TWL – HCM Processes and Forms JAVA and Adobe
Application Components:PA-AS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224318
S4TWL – HCM Processes and Forms
JAVA, WDA with Adobe
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 468
Reason and Prerequisites
Java / Adobe Forms
HCM Processes and Forms JAVA and Adobe (PA-AS) functionality is only available in
SAP ERP HCM. HCM Processes and Forms JAVA is not part of SAP S/4HANA as NW
AS Java is no longer supported. See SAP Note 2560753.
WebDynpro ABAP / Adobe Forms
HCM Processes and Forms based WebDynpro ABAP with Adobe form technology is
part SAP HCM in Compatibility Pack in SAP S/4HANA only, which comes with limited
usage rights. See SAP Note 3006433
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 137.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use HCM Processes and Forms based WebDynpro ABAP with Adobe form technology
anymore. See SAP Note 3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality isused or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with SAP HCM
Processes and Forms based on Fiori or WebDynpro ABAP (without Adobe).
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
This Simplification Item is relevant if report RPASR_RPT_START_TX_PASR_WD is
executed and/or the following WDA services are in use:
Check in table ICFSERVLOC if field ICF_NAME and ICFACTIVE = X
ICF_NAME
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 469
P8K00070
EH400065
EH4000164
EH4000132
P8K00043
EH500079
P8K00073
P8K00071
EH4000160
That indicates that you are usingthe HCM Processes and Forms based on JAVA and/or
Adobe. If you already useSAP HCM Processes and Forms based on Fiori or WebDynpro
ABAP (without Adobe), this simplification item is not relevant.
Other Terms
HCM Processes and Forms with Adobe, Compatibility Scope, Compatibility Package,
SAP HCM for SAP S/4HANA
18.8 S4TWL – Landing Pages and Suite Page Builder
Application Components:PA-PAO, CA-UI2-AR-FE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224337
S4TWL – Landing Pages and Suite
Page Builder
Symptom
The following SAP S/4HANA Transition Worklist item is applicable for the following
cases:
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher
and want to use HCM in Compatibility Pack
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to use SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA).
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 470
Suite Page Builder is the foundation for the HR Renewal landing pages. The landing
pages are web-based UIs and were used to provide a single point of access to employee
and organizational master data.
The Suite Page Builder & Landing Pages for HR Renewal are only available in SAP ERP
HCM and SAP HCM in Compatibility Pack in S/4HANA up to Release 2021.
With S/4HANA Release 2022 the Suite Page Builder & Landing Pages for HR Renewal
become obsolete and will be no longer supported.
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 137.
Business Process related information
After the conversion or upgrade to SAP S/4HANA 2022 or higher, on-premise edition
technically it will not be possible to use the HR Renewal Landing Pages and the Suite
Page Builder. See SAP Note 3091160
Required and Recommended Action(s)
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions.
If the functionality is used and still required, a similar function is provided with the Fiori
role for HR Specialist. See also SAP Roadmap items:
HR Specialist role
Employee Search app
Empoyee Actions app
The new role follows the latest UX strategy from SAP by using an SAP Fiori role instead
of HR Renewal Landing Pages based on the Suite Page Builder.
Please note: the Web Dynpro ABAP services to maintain employee related data are still
supported and will be incorporated into the new HR Specialist role.
Solution
How to Determine Relevancy
This Simplification Item is relevant if you have entries in table ICFSERVLOC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 471
field ICF_NAME = ARSRVC_SPB_ADMN and field ICFACTIVE = X
field ICF_NAME = ARSRVC_SUITE_PB and field ICFACTIVE = X
That indicates that you are using the HR Renewal Landing Pages and the Suite Page
Builder.
If you are not using HR Renewal Landing Pages and the Suite Page Builder, this
simplification item is not relevant.
Other Terms
HR Administrator, HR Professional; Landing Page, HR Renewal, Suite Page Builder,
Compatibility Package, SAP HCM for SAP S/4HANA
18.9 S4TWL – HCM Obsolete Packages
Application Components:PA-PA-XX, PA-PA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224319
S4TWL – HCM Obsolete Package
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
The packages PDEL, PZ1R, PBAS_BPO are only available in SAP ERP HCM
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it is not allowed to use
functionality out of these packages anymore. See SAP Note 3091160.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 472
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check manually whether functionalities out of these packages are used or not. If not, there
are no further actions. If functionalities out of these packages are required, please copy
the packages to customer namespace. Please keep in mind that SAP will not support
customer owned code.
You also have the choice to stay on SAP ERP HCM until its expiry date.
How to Determine Relevancy
This Simplification Item is relevant if you use functionalities out of these packages.
Other Terms
PDEL, PZ1R, PBAS_BPO, Compatibility Scope, Compatibility Package, SAP HCM for
SAP S/4HANA
18.10S4TWL - General HCM Approach within SAP S/4HANA
Application Components:PY-XX, PA-BC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273108
S4TWL - General HCM Approach within
SAP S/4HANA
Symptom
You are doing a system conversion to SAP S/4HANA and use SAP HCM in S/4HANA
in the Compatibility Pack. You also like to continue using HCM functionality on-premise
beyond the limited usage rights of the compatibility scope.
The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
SAP ERP HCM is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope, it’s expiry date and
links to further information please refer to SAP Note 2269324 – Compatibility Scope
Matrix for SAP S/4HANA on-premise. In the compatibility matrix attached to SAP Note
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 473
2269324, SAP ERP HCM component refers to the IDs 101, 117, 132, 414-420 and 422-
424.
SAP S/4HANA customers using HCM functionality on-premise can therefore continue
using SAP ERP HCM in the so-called Compatibility Mode. HCM functionality can run in
either a separate instance or single instance with SAP S/4HANA. The integration among
both on-premise instances (SAP ERP HCM with SAP S/4HANA on-premise) is available
via ALE in case SAP ERP HCM is running on separate instance. In case HCM
functionality is running inside of SAP S/4HANA, then the integration is
automatically given as part of Compatibility Mode.
Before expiry of the compatibility pack license, customers are required to migrate
from SAP HCM Compatibility Pack in SAP S/4HANA to the designated alternative
functionalities SAP SuccessFactors or SAP Human Capital Management for SAP
S/4HANA (SAP HCM for SAP S/4HANA).
SAP HCM for SAP S/4HANA is available since SAP S/4HANA release 2022 and based
on SAP ERP HCM with optimizations and selected innovations to leverage SAP
S/4HANA. The planned scope matches the key functionality of SAP ERP HCM. Please
find more information about the key functionality of SAP HCM for SAP S/4HANA
in this blog post. Please keep in mind that some of the known SAP HCM ERP
functionality is not part of SAP HCM for SAP S/4HANA, see SAP
Note 3091160. Customers can run SAP HCM for SAP S/4HANA either embedded or on
a separate SAP S/4HANA on-premise instance.
As SAP SuccessFactors remains the primary focus of our HCM innovation at SAP, there
are no plans for major additional functionality or re-architectures. It is intended as a
bridge to give customers additional time to move to SAP SuccessFactors.
Additional information for RISE with SAP S/4HANA Cloud, private edition
customers:
All talent solutions are not part of the offering. For more details see SAP Note 3091160.
Business Process related information
SAP SuccessFactors remains the primary focus of our HCM innovations and is therefore
the go-to architecture in the HCM area. For customers who are not willing or able to
move to SAP SuccessFactors in the near future, continuity and investment protection for
HCM functionality on-premise is provided via SAP HCM for SAP S/4HANA.
Required and Recommended Action(s)
SAP S/4HANA customers can use SAP ERP HCM until the expiry date of the
compatibility pack license. Afterwards a migration to SAP HCM for SAP S/4HANA is
required. If the current HCM configuration is affected by one or more simplifications (see
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 474
SAP Note 3091160), the affected functionalities must be replaced by their alternatives, if
applicable. Alternatively, customers can move to SAP's HCM go-to solution SAP
SuccessFactors. To assist in scoping and planning the transformation to SAP
SuccessFactors solutions, see SAP Note 3193560 - SAP Readiness Check for SAP
SuccessFactors Solutions.”
18.11S4TWL – Recruiting
Application Components:PA-RC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224353
S4TWL - SAP Recruiting
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA edition (in the
following referred to as SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
SAP Recruiting (PA-RC) functionality is only available in SAP ERP HCM and SAP
HCM in the Compatibility Pack in SAP S/4HANA, which comes with limited usage
rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 421.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the SAP Recruiting functionality anymore. See SAP Note 3091160.
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with SAP E-
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 475
Recruiting in SAP HCM for SAP S/4HANA or SAP SuccessFactors Recruiting
Management which needs to be implemented.
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry date.
Additional information for customers using RISE with SAP S/4HANA Cloud,
private edition:
SAP E-Recruiting is not available for RISE with SAP S/4HANA Cloud, private edition
customers because this is not part of the offering. See SAP Notes 3091160 and 2383888.
How to Determine Relevancy
This simplification item is relevant if you have entries in the table PB4000 or transactions
starting with PB* are executed. That indicates that you are using SAP Recruiting (PA-
RC). If you already use SAP E-Recruiting or an alternative solution such as SAP
SuccessFactors Recruiting, this simplification item is not relevant.
Other Terms
SAP Recruiting, PA-RC, Compatibility Scope, Compatibility Pack, SAP HCM for SAP
S/4HANA, PB4000, PB00, PB10, PB20, PB30, PB40, PB50
18.12S4TWL – Obsolete Payroll Reports
Application Components:PY-XX
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224325
S4TWL – Obsolete Payroll Reports
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Payroll Posting
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 476
Reports RPCIPE00_OLD, RPCIPE00_OLD_CE, RPCIPI00, RPCIPX00, RPCIPT00,
RPCIPL00 and RPCIPM00 are only available in SAP ERP and not part of SAP HCM in
Compatibility Pack in SAP S/4HANA. See SAP Note 3145947.
Payroll
Reports RPCS0000 and RPCSC000 are only available in SAP ERP HCM and SAP HCM
in Compatibility Pack in SAP S/4HANA, which comes with limited usage rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 117.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
execute these reports anymore. See SAP Note 3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the reports are used or not. If not, there are no further actions. If the
reports are used and still required, a similar function is provided which needs to be
implemented. SAP does not provide a standard migration tool.
Old Report
Alternative
TemSeFuntionality
RPCIPI00
RPCIPX00
RPCIPT00
RPCIPL00
RPCIPM00
On-premise:
Distribution via ALE (SAP S/4HANA OP)
Cloud:
Web Service in case FIN runs in SAP S/4HANA Cloud for payroll
posting
RPCIPE00_OLD
RPCIPE00_OLD_CE
RPCIPE01CE
RPCIPE00/01
RPCIPE00, RPCIPE01_CE
RPCIPE01_CE (no functional change - see SAP Note 3146771)
RPCS0000
RPCSC000
Process model(s) using the process workbench (transactions PEST
and PUST)
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 477
This Simplification Item is relevant if you execute the reports mentioned in that SAP
Note. That indicates that you are usingthese reports. If you already use the alternatives,
this simplification item is not relevant.
Other Terms
RPCS0000, RPCSC000, RPCIPE00_OLD, RPCIPE00_OLD_CE, RPCIPI00,
RPCIPX00, RPCIPT00, RPCIPL00, RPCIPM00, Compatibility Scope, Compatibility
Package, SAP HCM for SAP S/4HANA,
18.13S4TWL – HR Shared Service Framework
Application Components:CRM-IC-HCM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224338
S4TWL – HR Shared Service
Framework
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher, and
want to use SAP Human Capital Management for SAP S/4HANA (in the following
called SAP HCM for SAP S/4HANA). The following SAP S/4HANA Transition
Worklist item is applicable in this case.
Reason and Prerequisites
The Shared Service Framework for HCM-Integration functionality (related to Business
Functions HCM_SSC_EIC_1, HCM_SSC_EIC_2, HCM_SSC_EIC_3) incl. integration
of E-Recruiting (related Business Functions HCM_ERC_EIC_1, HCM_ERC_EIC_2) is
only available in SAP ERP HCM and SAP HCM in Compatibility Pack in SAP
S/4HANA, which comes with limited usage rights. For more details on the Compatibility
Pack and its expiry date and links to further information please refer to SAP Note
2269324. In the Compatibility Scope Matrix document attached to SAP Note 2269324,
this topic is listed under the Compatibility Scope Matrix Item ID 118.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use Shared Service Framework for HCM-Integration functionality anymore. See SAP
Note 3091160.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 478
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the old functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, please be aware that there is no alternative
available. Keep in mind that a similar functionality is provided with:
SAP Shared Service Framework for S/4HANA
SAP CRM
SAP SuccessFactors Employee Central Service Center
which needs to be implemented. You also have the choice to stay on SAP ERP HCM its
expiry date.
How to Determine Relevancy
This Simplification Item is relevant if Business Functions HCM_SSC_EIC_1 (+
HCM_SSC_EIC_2, HCM_SSC_EIC_3) and HCM_ERC_EIC_1 (+ HCM_ERC_EIC_2)
are activated. That indicates that you are using the Shared Service Framework for HCM-
Integration.
Other Terms
Shared Service Framework for HCM, Compatibility Scope, Compatibility Package, SAP
HCM for SAP S/4HANA, HCM_SSC_EIC_1
18.14S4TWL – Training and Event Management
Application Components:PE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224320
S4TWL – Training and Event
Management
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 479
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Training and Event Management functionality is only available in SAP ERP HCM and
SAP HCM in Compatibility Pack in SAP S/4HANA, which comes with limited usage
rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 135 & 136.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the Training and Event Management functionality anymore. See SAP Note 3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with SAP Learning
Solution (PE-LSO) in SAP HCM for SAP S/4HANA or SAP SuccessFactors Learning
which needs to be implemented.
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
Additional information for RISE with SAP S/4HANA Cloud, private edition
customers:
SAP Learning Solution (PE-LSO) is not available for RISE with SAP S/4HANA Cloud,
private edition customers because this is not part of the offering. See SAP Note 3091160.
How to Determine Relevancy
This Simplification Item is relevant if transactions PSV1, PSV2, PSV3 or PVCT are
executed. That indicates that you are using Training and Event Management. If you
already use SAP Learning Solution (PE-LSO) or SAP SuccessFactors Learning, this
simplification item is not relevant.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 480
Training and Event Management, Compatibility Scope, Compatibility Package, SAP
HCM for SAP S/4HANA, PSV1, PSV2, PSV3, PVCT
18.15S4TWL – Workforce Viewer
Application Components:PA-PAO-WFV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224339
S4TWL – Workforce Viewer
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 and want to
activate SAP Human Capital Management for SAP S/4HANA (in the following called
SAP HCM for SAP S/4HANA). The following SAP S/4HANA Transition Worklist item
is applicable in this case.
Reason and Prerequisites
Workforce Viewer functionality is only available in SAP ERP HCM and SAP HCM in
Compatibility Pack in SAP S/4HANA, which comes with limited usage rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item IDs 137, 417 and 420.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the Workforce Viewer functionality anymore. See SAP Note 3091160.
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with My Team and
Organizational Chart App (Fiori Apps for Managers) or SAP SuccessFactors Employee
Central (for e.g. customers having an already existing hybrid HR architecture) which
needs to be implemented. Further information for My Team (Fiori App for Managers)
can be found on SAP Help:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 481
My Team Fiori 2.0
https://help.sap.com/viewer/c6c3ffd90792427a9fee1a19df5b0925/2021.000/en-
US/f1ff00d3a2cb40e3b318a6c8442fc129.html
Organizational Chart App (on roadmap)
Roadmap Explorer
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
This Simplification Item is relevant if Business Function HCM_PD_ORGVIS_1 is
activated. That indicates that you are using Workforce Viewer.
Other Terms
Workforce Viewer, WFV, Compatibility Scope, Compatibility Package, SAP HCM for
SAP S/4HANA
18.16S4TWL – HIS and Structural Graphic
Application Components:PA-IS, BC-BMT-OM, BC-BMT-OM-GRF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224340
S4TWL – HIS and Structural Graphic
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the following
called SAP HCM for SAP S/4HANA). The following SAP S/4HANA Transition
Worklist item is applicable in this case.
Reason and Prerequisites
HR Information System (PA-IS) and Structural Graphic (BC-BMT-OM-GRF)
functionality is only available in SAP ERP HCM and SAP HCM in Compatibility Pack in
SAP S/4HANA, which comes with limited usage rights.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 482
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 132, 137.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use HIS (PA-IS) and Structural Graphic (BC-BMT-OM-GRF) functionality anymore. See
SAP Note 3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality is used or not. If not, there are no further actions. If yes,
please note that there is no alternative functionality.
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
This Simplification Item is relevant if you execute transaction PPIS. That indicates that
you are using the HR Information System (PA-IS) and Structural Graphic (BC-BMT-
OM-GRF)
Other Terms
HR Information System, HIS, Structural Graphic, Compatibility Scope, Compatibility
Package, SAP HCM for SAP S/4HANA, PPIS
18.17S4TWL – Parts of Time Management
Application Components:PT-EV, PT-RC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224341
S4TWL – Parts of Time Management
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 483
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Several Infotypes, related reports, BAdIs, function modules and operations of SAP
Timedata Recording and Management (PT-RC) and SAP Time Evaluation (PT-EV) are
only available in SAP ERP HCM and SAP HCM in Compatibility Pack in SAP
S/4HANA, which comes with limited usage rights.
Details can be found in the following SAP Notes:
3139908 – Functionality no longer available in Time Data Recording and
Management (PT-RC)
3138281 – Functionality no longer available in Time Evaluation (PT-EV)
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID132, ID137.
Already obsolete functionality in SAP ERP HCM and SAP HCM in Compatibility
Pack in SAP S/4HANA:
Two BAdIs and the integration of external time recording systems (interface CC1 (KK1))
won’t be available with S/4HANA Release 2022. For more details refer to:
3140931 - Integration of external time recording systems: Interface CC1 (KK1) no
longer available
3138644 - BAdIs no longer available in attendance/absence counting
Business Process related information
Related to SAP HCM for SAP S/4HANA
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the functionality mentioned in SAP Notes 3139908 and 3138281
Related to HCM in Compatibility Pack
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 484
After the upgrade to SAP S/4HANA 2022 it will technically not be possible to use the
functionality mentioned in SAP Notes 3140931 and 3138644 as it is already obsolete.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality is used or not. If not, there are no further actions. If the
functionality is used, please refer to the corresponding SAP Notes mentioned above for
the similar functionality.
How to Determine Relevancy
This Simplification Item is relevant if you have entries in tables:
CC1PAR KANAL =1 and CCVER = 1 and/or 2
PA0005
PA0083
PA2005
T77S0 GRPID = TIMGT and SEMID = PT40 and GSVAL = X
V_EXT_ACT EXIT_NAME = TIM00ABSCOUNTRY_DAY and IMPNAME = Y*
and/or Z*
V_EXT_ACT EXIT_NAME = TIM00ATTABSCOUNTING and IMPNAME = Y*
and/or Z*
Other Terms
PT-RC, PT-EV, IT0005, IT0083, IT2005, Compatibility Scope, Compatibility Package,
SAP HCM for SAP S/4HANA, Time Management, Time Evaluation, Infotypes, Reports,
Function Modules, RPTIME00, UPDLE, HRS1H, HRS1Q, VARST, TIMQU, TQUxx;
KK1, HR-PDC, PT41, PT42, PT43, PT44; BADI, attendance counting, absence
counting, PT_ABS_ATT_COUNTRY, TIM00ATTABSCOUNTING,
TIM00ABSCOUNTRY_DAY
18.18S4TWL - SuccessFactors Employee Central Integration
Application Components:LOD-EC-INT-EE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3255864
S4TWL – SuccessFactors Employee
Central Integration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 485
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher. The
following SAP S/4HANA Transition Worklist item is applicable in this case if add-on
product SFSF EC INTEGRATION (incl. software component PA_SE_IN) is installed in
the system.
Reason and Prerequisites
For the integration of SAP S/4HANA with SAP SuccessFactors Employee Central for
core HR SAP provides product SFSF EC INTEGRATION as an add-on to SAP
S/4HANA. This product includes to the following main components:
PA_SE_IN – used for replication of organizational and employee master data to SAP
SuccessFactors Employee Central
ODTFINCC – used for the replication of cost center data to SAP SuccessFactors
Employee Central
With SAP S/4HANA 2022 or higher the new add-on product SFSF EC S4 HCM
INTEGRATION (incl. software component ECS4HCM) is released. SFSF EC S4 HCM
INTEGRATION is the successor of SFSF EC INTEGRATION. It can be installed
independently of SAP HCM in Compatibility Pack or SAP HCM for SAP S/4HANA.
The prerequisite is only SAP S/4HANA 2022 or higher. Please refer to SAP Note
3250816.
Business Process related information
As of release SAP S/4HANA 2022 add-on SFSF EC INTEGRATION (PA_SE_IN) has
status deprecated for usage with SAP S/4HANA. This means, customers who already use
SFSF EC INTEGRATION can continue to use the add-on until SAP S/4HANA release
2023. After the conversion or upgrade to SAP S/4HANA 2022 or 2023 it is not
mandatory to diretctly install the new product SFSF EC S4 HCM INTEGRATION
(ECS4HCM). However, SFSF EC INTEGRATION will only be released up to SAP
S/4HANA 2023 and not for subsequent SAP S/4HANA releases. For more information,
see the following table and please refer SAP Note 3250816:
Table 1: Maintenance view SFSF EC INTEGRATION (PA_SE_IN) and SFSF EC S4
HCM INTEGRATION (ECS4HCM) in SAP S/4HANA
SAP S/4HANA Release
PA_SE_IN
ECS4HCM
2022
X
X
2023
X
X
2025
X
2027
X
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 486
For more information about the product SFSF EC S4 HCM INTEGRATION please refer
to this SAP Blog Post.
Please note: SFSF EC S4 HCM INTEGRATION does not contain a component for cost
center replication. As alternative for ODTFINCC you can use SAP Master Data
Integration (MDI) for cost center replication to SAP SuccessFactors Employee Central.
For integration to other SAP HCM in Compatibility Pack or SAP HCM for SAP
S/4HANA systems you can also use IDOC COSMAS.
However, because components PA_SE_IN and ODTFINCC are separately installable
instances of product SFSF EC INTEGRATION, you could keep ODTFINCC when
migrating PA_SE_IN to ECS4HCM in SAP S/4HANA releases 2022 and 2023. With
SAP S/4HANA 2025, though, ODTFINCC will no longer be provided as well.
Solution
It is strongly recommended to replace the product SFSF EC INTEGRATION
(PA_SE_IN) with SFSF EC S4 HCM INTEGRATION (ECS4HCM). In the Software
Update Manager (SUM) it is possible to select the installation of SFSF EC S4 HCM
INTEGRATION. With the installation of the new product SFSF EC S4 HCM
INTEGRATION, SFSF EC INTEGRATION (PA_SE_IN) will be replaced
automatically. Please note: After the installation of the new product SFSF EC S4
HCM INTEGRATION a mandatory migration with manual activities must be
executed. The guides for product SFSF EC S4 HCM INTEGRATION can be found
on SAP Help. The implementation guide for upgrading from PA_SE_IN to ECS4HCM
for Data Replication from Employee Central can be found on SAP Help.
It is also recommended to replace the ODTFINCC cost center replication add-on with
cost center replication using SAP Master Data Integration (MDI). The documentation for
cost center replication using the SAP Master Data Integration service running on the SAP
Business Technology Platform can be found on SAP Help. For integrating SAP
SuccessFactors Employee Central with SAP Master Data Integration the documentation
can be found on SAP Help.
How to Determine Relevancy
This Simplification Item is relevant if you have an entry in table CVERS – Component
PA_SE_IN
Other Terms
SFSF EC INTEGRATION, PA_SE_IN, SFSF EC S4 HCM INTEGRATION,
ECS4HCM, ODTFINCC, Cost Center Replication, MDI, Compatibility Scope,
Compatibility Package, SAP HCM for SAP S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 487
18.19S4TWL – Australia Public Sector ESS Not Supported in JAVA
Technology
Application Components:PA-PA-AU
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3238213
S4TWL – Australia Specific Public
Sector ESS Not Supported in JAVA
Technology
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher, on-
premise edition and want to use SAP Human Capital Management for SAP
S/4HANA, on-premise edition (in the following called SAP HCM for SAP S/4HANA).
The following SAP S/4HANA Transition Worklist item is applicable in this case.
SAP S/4HANA does not contain the NetWeaver Application Server for Java (AS Java),
therefore the Java-based ESS and MSS scenarios cannot be used in Compatibility Mode
nor in SAP HCM for SAP S/4HANA.
Other ESS /MSS technologies not supported with Compatibility Pack and /or SAP HCM
for SAP S/4HANA.
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 417, 420.
ESS/MSS functionality has changed over time. Note that some technologies have already
been replaced in former releases and others will no longer be available under SAP HCM
for SAP S/4HANA. Refer to the SAP Note 2383879 for more information.
Reason and Prerequisites
ESS/MSS on WD Java (already replaced)
Java-based ESS and MSS are already not available in Compatibility Mode, see SAP Note
2383879. For more details on the Compatibility Pack and its expiry date and links to
further information refer to SAP Note 2269324. You can also refer to SAP Note 3091160
for more information on SAP HCM for SAP S/4HANA- General Approach and Strategy.
The Australia specific Public Sector HCM applications affected are as follows:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 488
Superannuation Australia PS (0507)
Absence for Australia PS (0573)
Activity with Higher Rate of Pay (0509)
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether this functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, refer to the replacement functionality based on
ABAP WebDynpro technology, as described in the SAP Note 3085487.
How to Determine Relevancy
This Simplification Item is relevant if you use former ESS technology listed in the SAP
Note 3085487.
Other Terms
Employee Self Service, Manager Self Service, ESS, MSS, Compatibility Scope,
Compatibility Package, SAP HCM for SAP S/4HANA, 0220, 0507, 0573, 0509, Activity
with Higher Rate of Pay, Absence for Australia, Superannuation Australia
18.20S4TWL - Conversion of Employees to Business Partners
Application Components:PY-XX, PA-BC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2340095
S4TWL - Conversion of Employees to
Business Partners
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 489
With the conversion to SAP S/4HANA the implementation of the employee business
partner is mandatory if HR data (HR infotype based PERNR data model including the
PA-Tables) is needed. The HR data can be locally maintained (for example via
transaction PA30 or PA40) or via integration scenarios with SAP HCM as hub
implementation, SAP SuccessFactors Employee Central or an external (third party) HCM
system.
Constellation SAP HCM embedded in SAP S/4HANA
It is mandatory to synchronize employees to employee business partners.
Constellation SAP HCM ERP as hub implementation (non SAP S/4HANA)
The synchronization of employees to employee business partners does not take
place in the SAP HCM hub system. If the HR mini master record is distributed to
connected systems, it is mandatory to synchronize employees to employee
business partners in the receiving SAP S/4HANA system(s).
Constellation SAP HCM in SAP S/4HANA as hub implementation
The synchronization of employees to employee business partners takes place in
the SAP HCM hub system. Additionally, if the HR mini master record is
distributed to connected systems, it is mandatory to synchronize employees to
employee business partners in the receiving SAP S/4HANA system(s).
Constellation SAP SuccessFactors in a hybrid scenario
In a hybrid scenario where employees are maintained in SAP SuccessFactors
Employee Central and distributed to SAP S/4HANA system(s) it is mandatory to
synchronize employees to employee business partners.
To generate the employee business partners the HCM integration must be activated via
the HCM Integration Switch in system table T77S0.
Description
Group (GRPID)
Sem. abbr.
(SEMID)
HCM Integration
inactive
HCM Integration
active
Activate HCM
Integration
HRALX
HRAC
Space (blank)
X
If the HR mini master is not needed the HCM integration can be deactivated.
As of SAP S/4HANA 2020 OP a new Employee Business Partner Model was introduced.
This new model was also provided with Support Packages for the lower releases SAP
S/4HANA 1809 OP SP06 and 1909 OP SP04. See SAP Note 2954033. It is
recommended to use the New Employee Business Partner Model.
Nevertheless, you can also use the legacy models (VMODE1, VMODE2). For more
information regarding legacy employee business partner models please refer to this blog
post and the integration guide attached to this Note.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 490
Business Process related information
The data model in SAP S/4HANA is based on Business Partners (BP). A BP must be
assigned to each employee.
Required and Recommended Action(s)
After the conversion to SAP S/4HANA, the migration report
/SHCM/RH_SYNC_BUPA_FROM_EMPL must be executed before productive use of
the system. In case of concerns regarding performance caused by large data volume it is
recommended to use report /SHCM/RH_SYNC_BUPA_EMPL_SINGLE for the initial
load. Due to customizing dependencies, the reports cannot be executed in technical
downtime. For the daily synchronization the report
/SHCM/RH_SYNC_BUPA_FROM_EMPL needs to be scheduled. It is recommended to
run the report once a day after the initial run in order to synchronize future-dated
employee changes to the Business Partner. Non future-dated changes to employee data
are synchronized to the Business Partner automatically.
18.21S4TWL - E-Recruiting Localization for Brazil PS in SAP HCM for SAP
S/4HANA
Application Components:PY-BR-PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3219250
S4TWL - SAP E-Recruiting Localization
for Brazil Public Sector in SAP HCM for
SAP S/4HANA (PY-BR-PS)
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher, on-
premise edition and want to use SAP Human Capital Management for SAP
S/4HANA, on-premise edition (in the following called SAP HCM for SAP S/4HANA).
You are a HCM Brazil Public Sector customer using the existent solution from
LOCBRPY Add-On, and you use the SAP E-Recruiting localization for SAP
HCM Brazil Public Sector.
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 134, 421.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 491
For more information about Brazil Public Sector localization for SAP E-Recruiting, refer
to SAP Notes 2772355, 2430071, 2364562.
Reason and Prerequisites
SAP E-Recruiting with component ERECRUIT was already in the so-called
Compatibility Mode to up to SAP S/4HANA 1709 as described in SAP Note 2383888.
Refer to SAP Note 2383888 for more details.
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the Brazil Public Sector localization for SAP E-Recruiting functionality is used
or not. If not, there are no further actions. If the functionality is used and still required,
each customer needs to plan for an alternate solution.
How to Determine Relevancy
This Simplification Item is relevant if you use the Brazil Public Sector localization
for SAP E-Recruiting (ERECRUIT) in the LOCBRPY Add-On. Refer to the above-listed
SAP Notes for further information.
Other Terms
E-Recruiting, Brazil, PS, ERECRUIT, LOCBRPY, Compatibility Scope, Compatibility
Package, SAP HCM for SAP S/4HANA, "Criar Agências – Setor Público", "Regras para
Classificação (Cotistas e PCD)", "Requisição – Setor Público", "Candidatura – Setor
Público", "Perfil do Candidato – Setor Público", "Programa de Classificação de
Candidatos – Setor Público", "Transferência de Candidatos – Setor Público", 5200,
HRP5200
18.22S4TWL – Flexible Benefits not supported in ESS technologies
Application Components:PA-BN-FB-GB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3221404
S4TWL – Flexible Benefits not
supported in ESS technologies (PA-BN-
FB-GB)
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 492
Versions:
2nd version: general release, released on 07.09.2022.
3rd version: text correction, released on 11.01.2023.
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher, on-
premise edition and want to use SAP Human Capital Management for SAP
S/4HANA, on-premise edition (in the following called SAP HCM for SAP S/4HANA).
The Employee Self Service (ESS) functionality has changed over time. Please note that
some technologies have already been replaced in former releases and others will no
longer be available under SAP HCM for SAP S/4HANA. Refer to the SAP
Note 2383879 for more information.
The Employee Self Service (ESS) solution for the Flexible Benefits for Great Britain
functionality (Flexible Benefits for Great Britain) will no longer be available under SAP
HCM for SAP S/4HANA.
Reason and Prerequisites
ESS/MSS on WD Java (already replaced)
Java-based ESS and MSS are already not available in Compatibility Mode, see SAP
Note 2383879. For more information regarding ESS/MSS please refer to SAP
Note 2269324. You can also refer to SAP Note 3091160 for more information on SAP
HCM for SAP S/4HANA- General Approach and Strategy.
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the ESS solution for the Flexible Benefits for Great Britain functionality
(Flexible Benefits for Great Britain) is used or not.
If not, there are no further actions. If the functionality is used and it is still required,
customers need to plan for an alternative solution.
How to Determine Relevancy
This Simplification Item is relevant if you use former ESS/MSS technologies listed
above.
For more information regarding ESS/MSS please
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 493
Employee Self Service, ESS, SAP HCM for SAP S/4HANA, WebDynpro Java
18.23S4TWL – HR Policy Management - India – Not supported Apps
Application Components:PA-PA-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3218356
S4TWL – HR Policy Management -
India – Not supported Applications
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher, on-
premise edition and want to use SAP Human Capital Management for SAP
S/4HANA (in the following called SAP HCM for SAP S/4HANA). The following SAP
S/4HANA Transition Worklist item is applicable in this case.
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 417, 420.
Solution
ESS/MSS functionality has changed over time. Please note that the below mentioned
ABAP Webdynpro applications under HR Policy management application which allows a
company to create and manage policy for a company, will no longer be available under
SAP HCM for SAP S/4HANA.
Policy Management:
HR_IN_P2E_AP_POL_ACTIV_ROLLOUT P2E - Policy rollout and activate
HR_IN_P2E_AP_POL_CREATE - HR Policy Management
HR_IN_P2E_AP_POL_INBOX - Policy Inbox
HR_IN_P2E_AP_POL_REQUEST_EDIT P2E - Edit Policy Request
HR_IN_P2E_AP_POL_REQUEST_NEW P2E - New Policy Request
HR_IN_P2E_AP_POL_REQUEST_SRCH P2E - Policy Request Search
HR_IN_P2E_AP_POL_REQUEST_STAT P2E - Policy Request Status
HR_IN_P2E_AP_POL_WOLIST - HR Policy Management
WD_HR_IN_P2E_REQUEST - dynpro application
Policy Request Management:
HR_IN_P2E_AP_REQUEST_URL P2E - Policy Request Screen with URL Parameters
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 494
HR_IN_P2E_AP_REQ_APP_STATUS_AC P2E - Request Status (Accessible)
HR_IN_P2E_AP_REQ_INBOX- Request Inbox
HR_IN_P2E_AP_REQ_NEW_H P2E - New policy Request for HR
WD_HR_IN_P2E_REQUEST_APPROVER - Request Approver
Policy Request Approval:
HR_IN_P2E_AP_REQ_NEW_M P2E - New Policy Request MSS
HR_IN_P2E_AP_REQ_SRCH_M P2E - Policy Request Search for Manager
HR_IN_P2E_AP_REQ_SRCH_H P2E - Policy Request Search for HR Administrator
HR_IN_P2E_WF_LEVELS - Workflow Levels and Approvers W1
HR_IN_P2E_FORW_SUBT P2E - Forward Workitems
HR_IN_P2E_REQ_SETTINGS- Policy Request Settings
Required and Recommended Action(s)
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality (HR Policy Management India | SAP Help Portal) is used or
not. If not, there are no further actions. If the functionality is used and still required,
customer needs to plan for an alternate solution.
How to Determine Relevancy
This Simplification Item is relevant if you are former user of HR Policy Management –
India solutions and you have activated the switch HRLOCIN_SFWS_UI_07.
Other Terms
Employee Self Service, Manager Self Service, ESS, MSS, Compatibility Scope,
Compatibility Package, SAP HCM for SAP S/4HANA
18.24S4TWL – US Effort reporting – Not supported in ESS and MSS
technologies
Application Components:PA-PA-US-EFR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3218111
S4TWL – US Effort reporting – Not
supported in ESS and MSS
technologies
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 495
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher, on-
premise edition and want to use SAP Human Capital Management for SAP
S/4HANA, on-premise edition (in the following called SAP HCM for SAP S/4HANA).
The following SAP S/4HANA Transition Worklist item is applicable in this case.
SAP S/4HANA does not contain the NetWeaver Application Server for Java (AS Java),
therefore the Java-based ESS and MSS scenarios cannot be used in Compatibility Mode
nor in SAP HCM for SAP S/4HANA.
Other ESS /MSS technologies not supported with Compatibility Pack and /or SAP HCM
for SAP S/4HANA.
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 417, 420.
ESS/MSS functionality has changed over time. Note that some technologies have already
been replaced in former releases and others will no longer be available under SAP HCM
for SAP S/4HANA. Refer to the SAP Note 2383879 for more information.
Reason and Prerequisites
ESS/MSS on WD Java (already replaced)
Java-based ESS and MSS are already not available in Compatibility Mode, see SAP Note
2383879. For more details on the Compatibility Pack and its expiry date and links to
further information refer to SAP Note 2269324. You can also refer to SAP Note 3091160
for more information on SAP HCM for SAP S/4HANA- General Approach and Strategy.
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality (Effort Reporting | SAP Help Portal) is used or not. If not, there
are no further actions. If the functionality is used and still required, each customer needs
to plan for an alternate solution.
How to Determine Relevancy
This Simplification Item is relevant if you use former ESS/MSS technologies listed
above.
Other Terms
Employee Self Service, Manager Self Service, ESS, MSS, Compatibility Scope,
Compatibility Package, SAP HCM for SAP S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 496
18.25S4TWL – HCM Obsolete Package - US Federal Public Sector Functions
Application Components:PY-US-PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3238079
S4TWL – HCM Obsolete Package - US
Federal Public Sector Functions (PY-
US-PS)
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
The packages P10PA, PAOC_PAD_US_FD are only available in SAP ERP HCM and
SAP HCM in Compatibility Pack in SAP S/4HANA, which comes with limited usage
rights. The functionalities included in these packages will no longer be available under
SAP HCM for SAP S/4HANA.
For more details on the Compatibility Pack and its expiry date and links to further
information refer to SAP Note 2269324. In the Compatibility Scope Matrix document
attached to SAP Note 2269324, this topic is listed under the Compatibility Scope Matrix
Item ID 132, 137, 419.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it is not allowed to use
functionality out of these packages anymore. See SAP Note 3091160.
The affected transaction codes are listed below.
HRPBSUSACTION - Nature of Actions
HRPBSUSACTIONCONFIG - Nature of Action Configuration (4.7)
HRPBSUSERRCONFIG - Crediting Plan Configuration for ERR
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 497
The affected programs are listed below.
RHLDRGU0PBS - Random Drug Testing
RHLRIFU0PBS - Reduction in Force Registers
RHUFEDU0PBSCPDF - Organizational Component Translations Report
RPAPS0U0ERR - Electronic Rating and Rankings - Test/Eval Crediting Plan
RPAPU0ERRCONFIG - ERR Crediting Plan Configuration
RPUCFGU0 - Core report for defining field sequence in CPDF file
RPUCFGU1 - Report to define field sequence in dynamic CPDF file
RPUCFGU2 - Report to define field sequence for status CPDF file
RPUCFGU3 - Report to configure fields of status CPDF file
RPUCFGU4 - Report to configure fields for CPDF dynamic file
RPUFEDU0PBSCPDF - Generates CPDF Status and Dynamic Files
RPUNOAU1 - Nature of Action Configuration (4.7)
RPUNOAU2 - External report for Nature of Action Validations
The affected Infotypes are listed below.
0656 - Nature of Actions
0814 - Additional U.S. Federal Information
1660 - U.S. Federal Position Attributes (PD infotype)
1661 - US Federal Job Classification (PD infotype)
Solution
Required and Recommended Action(s)
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionalities mentioned are in use or not. If not, there are no further
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 498
actions. If the functionalities are used and still required, each customer needs to plan for
an alternate solution.
The Help Portal pages for the mentioned functionalities are listed below.
Federal US Public Sector Functions
Nature of Action (Infotype 0656)
Additional U.S. Federal Information (Infotype 0814)
U.S. Federal Position Attributes (PD Infotype 1660)
US Federal Job Classification (PD Infotype 1661)
How to Determine Relevancy
This Simplification Item is relevant if you use functionalities out of these packages.
Other Terms
P10PA, PAOC_PAD_US_FD, Nature of Actions, Reduction in Force
18.26S4TWL - SAP E-Recruiting
Application Components:PA-ER
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2383888
S4TWL - SAP E-Recruiting with
Compatibility Mode and beyond
Symptom
You are doing a system conversion to SAP S/4HANA and use SAP E-Recruiting in the
Compatibility Mode. You also like to continue using SAP E-Recruiting beyond the
limited usage rights of the compatibility scope.
The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
SAP E-Recruiting is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope, it’s expiry date and
links to further information, please refer to SAP Note 2269324 – Compatibility Scope
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 499
Matrix for SAP S/4HANA on-premise. The corresponding entry can be found in the
Compatibility Scope Matrix via ID 134.
SAP S/4HANA customers using SAP E-Recruiting can therefore continue using SAP E-
Recruiting in the so-called Compatibility Mode.
SAP E-Recruiting with component ERECRUIT was technically available in SAP
S/4HANA releases 1511, 1610 and 1709. SAP S/4HANA customers using SAP E-
Recruiting can therefore continue using SAP E-Recruiting in Compatibility Mode up to
SAP S/4HANA 1709. In SAP S/4HANA releases 1809 and higher, ERECRUIT is not
available anymore.
A new add-on product version called SAP E-Recruiting for SAP S/4HANA 1.0 has been
released on 15.03.2021 for the SAP S/4HANA releases 1809 and higher. This add-on
product version is also available for a standalone installation based on ABAP FND 1809
FOR HANA, S/4HANA Foundation release 1909 or higher. This will enable customers
to continue using SAP E-Recruiting in SAP S/4HANA in the Compatibility Mode until
2025. Please refer to SAP Note 3029126 – SAP E-Recruiting for SAP S/4HANA:
Release Information Note (RIN) for additional information.
With the release of SAP Human Capital Management for SAP S/4HANA (SAP HCM for
SAP S/4HANA) in 2022, a new add-on product version called SAP E-Recruiting for SAP
S/4HANA 2.0 is part of the product offering. The maintenance support for SAP E-
Recruiting after 2025 will continue in SAP HCM for SAP S/4HANA. Please find more
information about SAP E-Recruiting for SAP S/4HANA 2.0 in SAP Note 3086299 –
SAP E-Recruiting for SAP S/4HANA 2.0: Release Information Note (RIN) and SAP
HCM for SAP S/4HANA in SAP Note 2273108 - S4TWL - General HCM Approach
within SAP S/4HANA.
Business Process related information
SAP SuccessFactors remains the primary focus of our HCM innovations and is therefore
the go-to architecture in the HCM area. SAP SuccessFactors Recruiting Management is
the go-to solution for recruiting. For customers who are not willing or able to move to
SAP SuccessFactors Recruiting Management in the near future, continuity and
investment protection for the recruiting functionality on-premise is provided via SAP E-
Recruiting for SAP S/4HANA.
Please note: SAP E-Recruiting in Compatibility Mode and HCM for SAP S/4HANA is
not available in the RISE with SAP S/4HANA Cloud, private edition. If you are planning
to move to RISE with SAP S/4HANA Cloud, private edition you need to replace SAP E-
Recruiting with SuccessFactors Recruiting Management.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 500
Implement the latest version of SAP Note 2665372 – S4TC SAP E-Recruiting Check for
S/4HANA System Conversion to ensure that usage of E-Recruiting is verified during the
Readiness Check / Simplification Item Check for S/4HANA Conversion.
Before executing the system conversion of your SAP system running E-Recruiting
instance to SAP S/4HANA or SAP S/4HANA Foundation, please read SAP
Notes 3086299 – SAP E-Recruiting for SAP S/4HANA 2.0: Release Information Note
(RIN) and 3029126 – SAP E-Recruiting for SAP S/4HANA 1.0: Release Information
Note (RIN). These notes provide the pre-requisites and the references to the required
documentations and guides.
In order to continue using SAP E-Recruiting, the add-on product version SAP E-
Recruiting for SAP S/4HANA needs to be part of the target stack for the system
conversion to SAP S/4HANA 1809 or higher release. This addon should get
automatically added to the target stack by the maintenance planner, if the source stack
contains E-Recruiting instance and target stack meets the minimum Support Package
Stack (SPS) criteria. Please ensure that this addon is part of your target stack.
If you are using the product versions <any EHP> FOR SAP ERP 6.0 with instances E-
Recruiting or E-Recruiting Standalone or using S/4HANA 1511 or 1610 or 1709 then
choose one of the below as the target product versions:
Product Version
Minimum required Support Package Stack (SPS)
SAP S/4HANA 1809
SPS 04
SAP S/4HANA 1909
SPS 02
SAP S/4HANA 2020 or higher
releases
Initial Shipment Stack
If you are using the product versions <any EHP> FOR SAP E-RECRUIT 6.0, then
choose one of the below as the target product versions:
Product Version
Minimum required Support Package Stack (SPS)
ABAP FND 1809 on HANA
(S/4HANA Foundation 1809)
SPS 04
SAP S/4HANA Foundation 1909
SPS 02
SAP S/4HANA Foundation 2020 or
higher releases
Initial Shipment Stack
There are no application-related actions required to move from SAP E-Recruiting 6.0 to
SAP E-Recruiting for SAP S/4HANA 1.0. SAP E-Recruiting for SAP S/4HANA 1.0 is
functionally equivalent to EHP7/EHP8 of SAP E-Recruiting 6.0. For transitions brought
in SAP E-Recruiting for SAP S/4HANA 2.0, please refer to the product documentation.
Customers running SAP E-Recruiting have the following options:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 501
Replace SAP E-Recruiting with SuccessFactors Recruiting Management
Move to SAP E-Recruiting for SAP S/4HANA 2.0 as part of SAP Human Capital
Management for SAP S/4HANA
This option is not available in RISE with SAP S/4HANA Cloud, private
edition
Install SAP E-Recruiting for SAP S/4HANA 1.0 on the above supported base product
versions to continue in compatibility mode
This option is not available in RISE with SAP S/4HANA Cloud, private
edition.
18.27S4TWL - ESS and MSS
Application Components:PA-ESS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2383879
S4TWL - ESS and MSS technologies
not available in Compatibility Pack and
SAP HCM for SAP S/4HANA
Symptom
The following SAP S/4HANA Transition Worklist item is applicable in the following
cases:
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to use HCM in Compatibility Pack
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to use SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA)
SAP S/4HANA does not contain the NetWeaver Application Server for Java (AS Java),
therefore the Java-based ESS and MSS scenarios cannot be used in Compatibility Mode
nor in SAP HCM for SAP S/4HANA.
Other ESS /MSS technologies not supported with Compatibility Pack and /or SAP HCM
for SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 502
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 417, 420.
Solution
Description
ESS/MSS functionality has changed over time. Thus, some ESS/MSS technologies have
already been replaced in former releases of SAP EPR HCM, others are not available
within Compatibility Pack in SAP S/4HANA nor within SAP HCM for SAP S/4HANA.
In this SAP Note you find a summery of non-supported ESS and MSS technologies.
ESS on ITS (already obsolete)
SAP Internet Transaction Server (ITS) is considered to be an old technology. ESS on ITS
was already replaced by other technologies. See SAP Note 870126. Therefore, the ITS
services for the Employee Self Service (ESS) are also not available within Compatibility
Pack in SAP S/4HANA nor within SAP HCM for SAP S/4HANA.
MSS based on HTMLB (already obsolete)
Manager Self Service based on HTMLB was already replaced by other technologies. See
SAP Note 1007341. Therefore, the MSS based on HTMLB technology is not available
within Compatibility Pack in SAP S/4HANA nor within SAP HCM for SAP S/4HANA.
ESS/MSS on WD Java (already obsolete)
SAP S/4HANA does not contain the NetWeaver Application Server for Java (AS Java),
therefore it cannot be used within Compatibility Pack in SAP S/4HANA nor within SAP
HCM for SAP S/4HANA. See also SAP Not 2560753. For specific local versions please
refer to SAP Note 3217773.
MSS List reports based on ODP
MSS List reports based on ODP are based on an old technology. Therefore, the MSS
based on ODP technology is not available within Compatibility Pack in SAP S/4HANA
nor within SAP HCM for SAP S/4HANA.
ESS/MSS UI5 (from HR Renewal)
ESS/MSS UI5 known from HR Renewal are not available within SAP S/4HANA as it is
unequal SAP Fiori Technology. In addition, the HR Renewal Landing Pages and the
Suite Page Builder are not available for SAP S/4HANA 2022 or higher. See SAP
Note 3224337.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 503
Business Process related information
SAP recommends using either Fiori Applications or WebDynpro ABAP based services
for ESS/MSS. See SAP Note 3091160.
For HCM SAP Fiori apps 2.0, please have a look at the SAP Fiori Apps Reference
Library.
Required and Recommended Action(s)
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with Employee Self
Service (ESS) and Manager Self-Service (MSS) based on Fiori and WebDynpro ABAP
(WDA) which needs to be implemented. Further information for Employee Self Service
(ESS) and Manager Self-Service (MSS) based on Fiori and WDA can be found on SAP
Help:
Employee Self Service (WDA)
Fiori Apps in HCM
Manager Self Service (WDA)
How to Determine Relevancy
This Simplification Item is relevant if you use former ESS/MSS technologies listed
above.
Other Terms
Employee Self Service, Manager Self Service, ESS, MSS, Compatibility Scope,
Compatibility Package, SAP HCM for SAP S/4HANA
18.28S4TWL - Travel Management SRA004 Simplified Model
Application Components:FI-TV, FI-FIO-TV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3062197
"S4TWL - HR_SRA004 Simplified Model
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 504
Symptom
You are doing a system conversion to SAP S/4HANA On-Premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release or below S/4 HANA 2021.
Solution
Description
The first version of the Fiori application "My Travel Request" aka MTR, corresponding
to the Fiori ID F0409, was developped some years ago in Business Suite Technology
Stack. It was available for ERP release ECC6.0 until ECC6.0 EHP8 and S/4 HANA
releases until 2020.
A second version of this FIORI application "My Travel Requests Version 2" (MTR V2)
with Fiori ID F0409A, is also available since ECC6.0 EHP8. This second application is
much more powerfull in term of functionalities and technology.
When you plan a conversion to S/4HANA, there is no reason to keep the first version as
the landscape includes by default the second application.
For more information about Travel Management in S/4HANA please read the following
note: 2976262 - S4TWL - General Travel Management approach within SAP S/4HANA.
Business Process related information
Implications: Customer roles (menus and authorizations) need to be adjusted in order to
display the new Fiori application in the SAP Fiori Launchpad.
All information about Gateway Service and configuration can be found in the SAP Fiori
Application library here
The old Gateway Service can simply be switch off.
There is no data conversion or impact as the change impacts only on the UI.
Required and Recommended Action(s)
If you are using the ODATA Service SRA004_SRV then this simplification item is
relevant for you.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 505
The new ODATA Service TRV_MTR_SRV is available and must be registered and
activated on the front-end server.
Check - How to Determine Relevancy
Check if the existing Odata Service SRA004_SRV is activated on the Front End Server.
If yes perform the simplification Process, the new Odata Service should be
TRV_MTR_SRV Now and you should deactivate the obsolete OData Service
SRA004_SRV.
You can use the transaction /IWFND/MAINT_SERVICE, one entry can be found with
external service name “SRA004_SRV”.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade
18.29S4TWL – Managers Desktop
Application Components:PA-MA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224315
S4TWL – Managers Desktop
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Managers Desktop functionality is only available in SAP ERP HCM and SAP HCM in
Compatibility Pack in SAP S/4HANA, which comes with limited usage rights.
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 420.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 506
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use the Managers Desktop functionality anymore. See SAP Note 3091160.
Solution
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionality is used or not. If not, there are no further actions. If the
functionality is used and still required, a similar function is provided with Manager Self-
Service (MSS) based on Fiori and WebDynpro ABAP (WDA) which needs to be
implemented. Further information for Manager Self-Service (MSS) based on Fiori and
WDA can be found on SAP Help:
MSS WebDynpro ABAP (WDA)
https://help.sap.com/viewer/c6c3ffd90792427a9fee1a19df5b0925/2021.000/en-
US/c712fc6d47a84baf997ea5340e3df2c6.html
Fiori 2.0 Apps for HCM
https://help.sap.com/viewer/c6c3ffd90792427a9fee1a19df5b0925/2021.000/en-
US/5d3289588bf89244e10000000a4450e5.html
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
How to Determine Relevancy
This Simplification Item is relevant if transaction PPMDT is executed. That indicates that
you are using Managers Desktop.
Other Terms
Managers Desktop, MDT, Compatibility Scope, Compatibility Package, SAP HCM for
SAP S/4HANA
18.30S4TWL – Country Version Denmark (PY-DK)
Application Components:PA-PA-DK, PY-DK
Related Notes:
Note Type
Note Number
Note Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 507
Business Impact
3213848
S4TWL – Simplification of HCM DK
(HRDK) Local Version in SAP HCM for
SAP S/4HANA
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). Also, you run the SAP HCM Local
Version for Master data and Payroll for Denmark.
In the Compatibility Scope Matrix document attached to SAP Note 2269324, this topic is
listed under the Compatibility Scope Matrix Item ID 117, 132.
Reason and Prerequisites
SAP HCM for SAP S/4HANA will be part of the initial shipment of SAP S/4HANA
2022 on-premise. It is not the legal successor of SAP HCM. It contains additional/new
functionality and also functionality which no longer will be part of SAP HCM for SAP
S/4HANA (SAP HCM for SAP S/4HANA is part of SAP Business Suite wide
simplification including the principle of one strategy). To inform customers about the
simplification in advance, this SAP Note serves as info about simplification related to
HCM Denmark. As complete SAP HCM Denmark solution is simplified, you can find
list of main objects roofing this simplification in attached document.
Package PC09_SIMPLIFICATION which includes simplified
solutions/features/objects/... is part of delivery. Objects of this package should not be
used anymore. You can still access master data of your employees in display/delete mode
(no create/change possible). Note: Content of package PC09_SIMPLIFICATION is
subject of possible changes and could be extended in future with respect to fact that
complete SAP HCM Denmark solution is simplified.
Note: If you are doing a system conversion or upgrade to SAP S/4HANA 2022, on-
premise edition and still want to use SAP HCM in compatibility scope you can continue
to use all functionalities of the Compatibility Pack. Please keep in mind that usage rights
of compatibility packages will expire as outlined in SAP Note 2269324. This means after
this point in time the migration to SAP HCM for SAP S/4HANA and the other designated
alternative functionalities outlined above must happen immediately with the technical
conversion to SAP S/4HANA.
Obsolete functions. Dependent on business function H4S4_1
Solution
The corrections will be delivered by support package / initial installation.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 508
Please keep in mind: This SAP Note can be changed and enhanced from time to time
with new information.
Required and Recommended Action(s)
Before the conversion or upgrade to SAP HCM for SAP S/4HANA 2022 or higher, check
whether the functionalities mentioned are in use or not. If not, there are no further
actions. If the customer functionalities are still using objects/functionalities
from PC09_SIMPLIFICATION package, each customer needs to plan for an alternate
solution instead.
How to Determine Relevancy
This Simplification Item is relevant if you use functionalities out
of PC09_SIMPLIFICATION package.
Other Terms
HCM DK, DK infotypes, DK payroll driver, DK reports, DK IMG, DK SAP Easy Access
Menu
18.31S4TWL – Personnel Development
Application Components:PA-PD-DP, PA-PD-SP, PA-PD-AP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3224316
S4TWL – Personnel Development
Symptom
You are doing a system conversion or upgrade to SAP S/4HANA 2022 or higher and
want to activate SAP Human Capital Management for SAP S/4HANA (in the
following called SAP HCM for SAP S/4HANA). The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Appraisal Systems (PA-PD-AP), Development Plans (PA-PD-DP) and Career and
Succession Planning (PA-PD-SP), summarized as Personnel Development functionality,
are only available in SAP ERP HCM and SAP HCM in Compatibility Pack in SAP
S/4HANA, which comes with limited usage rights.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 509
For more details on the Compatibility Pack and its expiry date and links to further
information please refer to SAP Note 2269324. In the Compatibility Scope Matrix
document attached to SAP Note 2269324, this topic is listed under the Compatibility
Scope Matrix Item ID 418, 422, 423.
Business Process related information
After the activation of SAP HCM for SAP S/4HANA it will technically not be possible to
use Personnel Development functionality anymore. See SAP Note 3091160.
Solution
Before activating SAP HCM for SAP S/4HANA in SAP S/4HANA 2022 or higher,
check whether the functionality is used or not. If not there are no further actions. In case
you use transaction PPPM (for qualifications) please consider that you have to check if
you have the right entry in table T77S0 - field GRPID = HAP00 - field SEMID =
REPLA. The right value (field GSVAL) is "A". If you have another entry you get the
error message "Appraisal functionality is simplified" (H4S4_REUSE_SFWS002) when
executing PPPM. For more information please read the Help (F1) in the error message.
If the functionality is used and still required, a similar function is provided with
Objective Settings & Appraisals (PA-PD-PM) or SAP SuccessFactors Performance
& Goals for Appraisal Systems
Talent Management & Development (PA-TM) or SuccessFactors Succession &
Development for Career and Succession Planning and Development Plans
This functionalities need to be implemented.
You also have the choice to stay on SAP ERP HCM or SAP HCM in Compatibility Pack
in SAP S/4HANA until its expiry dates.
Additional information for RISE with SAP S/4HANA Cloud, private edition
customers:
Objective Settings & Appraisals (PA-PD-PM) or SAP SuccessFactors Performance &
Goals and Talent Management & Development (PA-TM) or SuccessFactors Succession
& Development are not available for RISE with SAP S/4HANA Cloud, private edition
customers because this is not part of the offering. See SAP Note 3091160.
How to Determine Relevancy
This Simplification Item is relevant if you have entries in tables:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 510
HRP1000 OTYPE = BS or BA
HRP1000 OTYPE = BL or B
HRP1000 OTYPE = LB
HRP1001 RELAT = 038 or 042 or 043
HRP1001 RELAT = 049
T77S0 GRPID = HAP00; SEMID = REPLA; GSVAL ≠ A.
That indicates that you are using Personnel Development functionality. If you already use
the alternative functionalities mentioned before, this simplification item is not relevant.
Note: in case have implemented SAP Performance Management and using templates
with development plans please also refer to SAP Note: 3257544
Other Terms
Personnel Development, Appraisal Systems, PA-PD-AP, Development Plans, PA-PD-
DP, Career and Succession Planning, PA-PD-SP, Compatibility Scope, Compatibility
Package, SAP HCM for SAP S/4HANA, PPPM, H4S4_REUSE_SFWS002
18.32S4TWL - BAdIs not supported in EC Payroll
Application Components:LOD-EC-GCP-PY-EDR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3394928
S4TWL - BAdIs not supported in EC
Payroll
Symptom
In your SuccessFactors Employee Central Payroll system, you want to do a system
conversion to SAP S/4HANA 2023 or higher, which also requires activating SAP
Human Capital Management for SAP S/4HANA (in the following called SAP HCM
for SAP S/4HANA). The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Reason and Prerequisites
In SuccessFactors Employee Central Payroll system based on SAP HCM for SAP
S/4HANA, some functional simplifications are enforced.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 511
Description
SuccessFactors Employee Central Payroll (EC Payroll) was previously based on SAP
ERP HCM. With EC Payroll being based on SAP HCM for SAP S/4HANA, the
following BAdIs are no longer called by the system.
BAdI HRSFEC_B_CE_CHANGE_IT0000
BAdI HRSFEC_B_CE_EXT_PERNR_MAP
This means that any implementation of these BAdIs being used in your EC Payroll
system before the conversion will become irrelevant after the conversion.
In addition, no customer-specific implementation should be defined for the
BAdI HRPAD00INFTYDB.
Finally, the standard implementation HRPAYUS_CLD_EI_TRACK_PERNR of
BAdI HRPAD00INFTYDB should be deactivated.
Business Process related information
BAdI HRSFEC_B_CE_CHANGE_IT0000
It was already recommended in EC Payroll based on SAP ERP HCM that the
BAdI HRSFEC_B_CE_CHANGE_IT0000 should not be used. Instead, payroll events
should be used. See the following documentation on payroll events:
https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYR
OLL/185f14fbe60d4bbb8d7d5e4f8d89b24b/de1470b517964f62a4be792c17f059ff.html
In EC Payroll based on SAP HCM for SAP S/4HANA, this BAdI is no longer called.
Thus, the use of payroll events is now required.
BAdI HRSFEC_B_CE_EXT_PERNR_MAP
It was already recommended in EC Payroll based on SAP ERP HCM that the
BAdI HRSFEC_B_CE_EXT_PERNR_MAP should not be used. Instead, internal
numbering should be used for creating personnel numbers, or the Employee Central
Assignment ID should be used.
See the following documentation on the Employee Central Assignment ID:
https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYR
OLL/185f14fbe60d4bbb8d7d5e4f8d89b24b/879a851e3b3a48c0bd57381b23fa2d8e.html
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 512
See the following documentation on internal numbering:
https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYR
OLL/185f14fbe60d4bbb8d7d5e4f8d89b24b/b85e2bab779349a486da9970f29b756d.html
In EC Payroll based on SAP HCM for SAP S/4HANA, this BAdI is no longer called.
Thus, you must create personnel numbers through internal numbering, or you must use
the Employee Central Assignment ID.
Customer-specific Implementations of BAdI HRPAD00INFTYDB
It was already recommended in EC Payroll based on SAP ERP HCM that no customer-
specific implementation should be created for the BAdI HRPAD00INFTYDB. Instead,
BAdIs from enhancement point HRSFEC_CE_MASTER_DATA_REPL should be used.
See the following documentation on extensibility in EC Payroll:
https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYR
OLL/185f14fbe60d4bbb8d7d5e4f8d89b24b/dfdd3f16b72b4915a3eb2358ab9ec354.html
In EC Payroll based on SAP HCM for SAP S/4HANA, the PTP Master Data Replication
and the PTP Time Data Replication will end with error messages, if active customer-
specific implementations for this BAdI exist. These are implementations in the ranges
Y*, Z* and /*/*. Thus, you must deactive or delete these implementations and
implement BAdIs from enhancement point HRSFEC_CE_MASTER_DATA_REPL, if
you have requirements that make it necessary to implement BAdIs.
Implementation HRPAYUS_CLD_EI_TRACK_PERNR of BAdI HRPAD00INFTYDB
It was already recommended in EC Payroll based on SAP ERP HCM that the
implementation HRPAYUS_CLD_EI_TRACK_PERNR of BAdI HRPAD00INFTYDB
should not be activated. Instead, the program RPCPAYUS_CLD_NOTIFY_BSI should
be used. This program was delivered with the note 1838192 "BSI:Integration of BSI
TaxFactory SaaS and BSI eFormsFactory". See the following documentation on
extensibility in EC Payroll:
https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYR
OLL/185f14fbe60d4bbb8d7d5e4f8d89b24b/dfdd3f16b72b4915a3eb2358ab9ec354.html
In EC Payroll based on SAP HCM for SAP S/4HANA, the PTP Master Data Replication
and the PTP Time Data Replication will end with error messages, if the implementation
HRPAYUS_CLD_EI_TRACK_PERNR of BAdI HRPAD00INFTYDB is active. Thus,
you must deactivate this implementation and use the
program RPCPAYUS_CLD_NOTIFY_BSI.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 513
BAdI HRSFEC_B_CE_CHANGE_IT0000
If you still use the BAdI HRSFEC_B_CE_CHANGE_IT0000, transition to using payroll
events. If it is not possible for you to change to payroll events, you can request an
exception. With this exception, the BAdI HRSFEC_B_CE_CHANGE_IT0000 is still
called even in an EC Payroll system based on SAP HCM for SAP S/4HANA. To request
an exception, proceed as follows before converting the system to SAP HCM for SAP
S/4HANA:
Create a case under component LOD-EC-GCP-PY-CPA.
Specify as subject “Requesting the continued use of
BAdI HRSFEC_B_CE_CHANGE_IT0000 in EC Payroll based on SAP HCM for
SAP S/4HANA”.
Specify that you are using Employee Central Payroll and that you are transitioning
from a system based on SAP ERP HCM to a system based on SAP HCM for SAP
S/4HANA. Furthermore, specify that you would like to continue using the BAdI
HRSFEC_B_CE_CHANGE_IT0000.
Specify all your Employee Central Payroll systems and clients for which you want to
have this option enabled.
BAdI HRSFEC_B_CE_EXT_PERNR_MAP
If you still use the BAdI HRSFEC_B_CE_EXT_PERNR_MAP for creating personnel
numbers, transition to using internal numbering or to using the Employee Central
Assignment ID. If it is not possible for you to change the way you create personnel
numbers, you can request an exception. With this exception, the
BAdI HRSFEC_B_CE_EXT_PERNR_MAP is still called even in an EC Payroll system
based on SAP HCM for SAP S/4HANA. To request an exception, proceed as follows
before converting the system to SAP HCM for SAP S/4HANA:
Create a case under component LOD-EC-GCP-PY-CPA.
Specify as subject “Requesting the continued use of
BAdI HRSFEC_B_CE_EXT_PERNR_MAP in EC Payroll based on SAP HCM
for SAP S/4HANA”.
Specify that you are using Employee Central Payroll and that you are transitioning
from a system based on SAP ERP HCM to a system based on SAP HCM for SAP
S/4HANA. Furthermore, specify that you would like to continue using the BAdI
HRSFEC_B_CE_EXT_PERNR_MAP.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 514
Specify all your Employee Central Payroll systems and clients for which you want to
have this option enabled.
Customer-specific Implementations of BAdI HRPAD00INFTYDB
If you still use customer-specific implementations for the BAdI HRPAD00INFTYDB,
transition to customer-specific implementations of BAdIs from enhancement point
HRSFEC_CE_MASTER_DATA_REPL. If it is not possible for you to move away from
your customer-specific implementations of BAdI HRPAD00INFTYDB, you can request
an exception. With this exception, the customer-specific implementations of
BAdI HRPAD00INFTYDB can still remain active even in an EC Payroll system based
on SAP HCM for SAP S/4HANA. To request an exception, proceed as follows before
converting the system to SAP HCM for SAP S/4HANA:
Create a case under component LOD-EC-GCP-PY-CPA.
Specify as subject “Requesting the continued use of BAdI HRPAD00INFTYDB in
EC Payroll based on SAP HCM for SAP S/4HANA”.
Specify that you are using Employee Central Payroll and that you are transitioning
from a system based on SAP ERP HCM to a system based on SAP HCM for SAP
S/4HANA. Furthermore, specify that you would like to continue using customer-
specific implementations of the BAdI HRPAD00INFTYDB.
Specify all your Employee Central Payroll systems and clients for which you want to
have this option enabled.
Implementation HRPAYUS_CLD_EI_TRACK_PERNR of BAdI HRPAD00INFTYDB
If you have still activated the implementation HRPAYUS_CLD_EI_TRACK_PERNR
of BAdI HRPAD00INFTYDB, deactivate it and use the
program RPCPAYUS_CLD_NOTIFY_BSI instead. If it is not possible for you to move
away from this BADI implementation, you can request an exception. With this
exception, the implementation HRPAYUS_CLD_EI_TRACK_PERNR of BAdI
HRPAD00INFTYDB can still remain active even in an EC Payroll system based on SAP
HCM for SAP S/4HANA. To request an exception, proceed as follows before converting
the system to SAP HCM for SAP S/4HANA:
Create a case under component LOD-EC-GCP-PY-CPA.
Specify as subject “Requesting the continued use of
implementation HRPAYUS_CLD_EI_TRACK_PERNR
of BAdI HRPAD00INFTYDB in EC Payroll based on SAP HCM for SAP
S/4HANA”.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 515
Specify that you are using Employee Central Payroll and that you are transitioning
from a system based on SAP ERP HCM to a system based on SAP HCM for SAP
S/4HANA. Furthermore, specify that you would like to continue using the
implementation HRPAYUS_CLD_EI_TRACK_PERNR of the BAdI
HRPAD00INFTYDB.
Specify all your Employee Central Payroll systems and clients for which you want to
have this option enabled.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Employee Central
Payroll, EC Payroll
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 516
19.Logistics – General
19.1 S4TWL - Advanced Track & Trace
Application Components:LO-GEN-ATT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2668899
S4TWL - Advanced Track & Trace
Symptom
You plan to convert an ECC or S/4 instance to S/4 HANA 1809 or higher. This requires a
pre-check to be executed to ensure that your setup and components are compatible with
the target release.
Important Remark:
The ERP functionality of Advanced Track and Trace for Pharmaceuticals is released for
S/4 HANA 1809 FPS01 or higher.
The ERP functionality of Advanced Track and Trace for Pharmaceuticals is not
available for S/4 HANA 1809 SP00.
Conversion from a supported ECC version: Conversion to S/4 HANA 1809 SP00 is not
possible.
Upgrade from a supported S/4 HANA version: Upgrade to S/4 HANA 1809 SP00 is not
possible.
Reason and Prerequisites
You have The ERP Add on for Advanced Track and Trace installed (STTPEC).
The conversion pre-checks require a check logic to be implemented. These checkes are
included within this note.
Solution
Implement the attached correction instructions.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 517
Required and recommended actions:
Before implementing this note please carefully read the related consulting note 2716224 -
"S/4HANA 1809+ Conversion/Upgrade Guidelines for Advanced Track & Trace". Data
model changes, retrofit etc. are described in the note 2716224.
Other Terms
ECC, S4HANA, Pre-Check, Simplification
19.2 S4TWL - Season Field Length Extension
Application Components:LO-RFM-CA, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2624475
SAP S/4HANA: Seasons Field Length
Extension
Symptom
You are going to use Season functionality in SAP S/4HANA 1809 or higher. This note
collects information related to the Seasons field length extension. For more information,
see the referenced notes.
Reason and Prerequisites
In SAP S/4HANA, the maximum length of the Seasons (SEASON, COLLECTION
,THEME) value has been extended to 10 characters.
Solution
Description
In SAP S/4HANA 1809, the maximum length of the ID of Season, Collection, Theme has
been extended to 10 characters.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 518
If your SAP S/4HANA system is embedded in a system landscape that contains other
SAP or non-SAP solutions, integration may only be possible if the extended Season field
length functionality is not activated in SAP S/4HANA.
Integration between SAP S/4HANA 1809 and SAP Customer Activity Repository 3.0
(CARAB 2.0) does not work with extended Season field length.
Required and Recommended Action(s)
In case you want to integrate with solutions that can't process Seasons with extended field
lengtht, you can't activate field length extension for Seasons in customizing (Cross-
Application Components -> General Application Functions -> Activate Extended Fields).
For further information regarding integration in a solution landscape, and how to adjust
customer specific coding, please see reference note.
Please note, that currently integration scenarios with SAP Customer Activity Repository
3.0 (CARAB 2.0) and consuming applications are not supported. SAP plans to provide a
note to enable such an integration scenario.
How to Determine Relevancy
This Simplification Item is relevant if Season is used.
This can be checked via transaction SE16N. This simplification item is relevant if there
are entries in table FSH_SEASONS.
Other Terms
FSH_SAISO, FSH_COLLECTION, FSH_THEME
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 519
20.Logistics – AB
20.1 S4TWL - Agency Business
Application Components:LO-AB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267743
S4TWL - Agency Business
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Simplification of DB Key Fields and tables structures (WBRL,WBRRE, WBRF,
WBRFN and WBRP)
Replacement of concatenated fields by corresponding new fields in mentioned DB
tables (Details mentioned notes below)
Replaced fields are moved to the dynamical part of the communication structures to
avoid runtime errors and to ensure the same system behaviour as before
All redundant transaction and reports or business processes where replaces by one
unified set of transaction, reports and business processes
Business Process related information
The application simplification offers now for each business process step one single
transaction instead of many. Redundant functionalities were combined into one
transaction or business process. This will help to streamline each single business step and
to reduce unnecessary complexity by eliminating of similar business processes steps.
The Remuneration Request List is not available within SAP S/4HANA. The functional
equivalent in SAP S/4HANA is the Extended Remuneration List offers the same business
capability as well. This means that the customizing of the Extended Remuneration List
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 520
has to be set up to ensure that the same documents are created. The replacement of the
Remuneration List by the extended one can be done before or after the system conversion
to SAP S/4HANA, on-premise edition 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
Obsolete
Report
Title
Obsolete
Tcode
Successor Report
Success
or
Report
Title
Successor Tcode
RWLF100
1
Billing
docs
(header
data)
WLFB
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
2
Billing
document
s (with
item data)
WLFC
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
3
Settlemen
t
Document
Lists
(Header
Informatio
n)
WLFD
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
4
Settlemen
t
Document
Lists (With
Item Data)
WLFE
RWLF1051
List
Output
Settleme
nt
Manage
WLI2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 521
ment
Documen
ts
RWLF100
5
Settlemen
t
Requests
(Header
Informatio
n)
WLFG
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
6
Settlemen
t
Requests
(With Item
Data)
WLFH
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
7
Settlemen
t Request
Lists
(Header
Data)
WLFO
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
8
Settlemen
t Request
List (Item
Data)
WLFP
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF100
9
Customer
Settlemen
t Lists
(Header
Data)
WLFQ
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF101
0
Customer
Settlemen
t Lists
(With Item
Data)
WLFR
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF101
1
Display
Relevant
WLRA
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
WLFSLRL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 522
Payment
Document
s for
Settlemen
t Doc List
Creation
Creation
of
Settleme
nt
Documen
t List
(Dialog)
RWLF101
2
Display
Relevant
Billing
Document
s for
Creation
of
Settlem.
Doc Lists
WLRB
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF101
3
Display
Relevant
Customer
Settlemen
t Lists for
Settl Doc
List
Creation
WBLRB
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF101
4
Customer
Settlemen
t (Header
Informatio
n)
S_AL0_96000
193
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF101
5
Customer
Settlemen
t (With
Item Data)
S_AL0_96000
194
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF101
6
Expenses
Settlemen
t (Header
Informatio
n)
S_AL0_96000
195
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF101
7
Expenses
Settlemen
t (With
Item Data)
S_AL0_96000
196
RWLF1051
List
Output
Settleme
nt
WLI2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 523
Manage
ment
Documen
ts
RWLF101
8
Display
Customer
Settlemen
ts for
Settlemen
t
Document
List
Creation
S_AL0_96000
198
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF101
9
Relevant
Expenses
Settlemen
ts for
Settlemen
t
Document
List
Creation
S_AL0_96000
334
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF105
0
List
Output
Single
Document
s
WLI1
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF105
2
List
Output
List
Document
s
WLI3
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF1C
HD
Display
Change
Document
for
Settlemen
t
Managem
ent
Document
s
RWLF_CHANGE_DOC
UMENTS
Display
Change
Documen
ts
WLF_CHANGE_DOCU
MENTS
RWLF1K
O1
Conditions
for
Settlemen
t
RWLF1051
List
Output
Settleme
nt
Manage
WLI2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 524
Requests
(Vendor)
ment
Documen
ts
RWLF1K
O2
Conditions
for
Settlemen
t Request
Lists
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF1K
O3
Conditions
for
Settlemen
t
Document
Lists
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF1K
O4
Conditions
for
Settlemen
t
Requests
(Customer
)
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF1K
O5
Conditions
for
Customer
Settlemen
t List
Document
s
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF200
1
Mass
Release
of
Settlemen
t
Document
s to
Accountin
g
WLFF
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF200
2
Mass
Cancellati
on of
Settlemen
t
Requests
WLFI
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 525
RWLF200
3
Mass
Cancellati
on of
Billing
Document
s
WLFJ
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
RWLF200
4
Mass
release of
billing
document
s to
accountin
g
WLFK
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF200
5
Mass
Release
of
Remunera
tion Lists
to
Accountin
g
WLFL
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF200
6
Generate
Settlemen
t
Document
Lists from
Vendor
Billing
Document
s
WLFM
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF200
7
Generate
Remunera
tion Lists
from
Payment
Document
s
WLFN
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF200
8
Mass
Release
of
Settlemen
t Request
Lists to
Accountin
g
WRL4
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 526
RWLF200
9
Mass
release of
posting
lists to
Accountin
g
WBL4
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF201
0
Create
posting
lists from
preceding
document
s
WBLR
RWLF2052
Generate
Customer
Settleme
nt Lists
from
Settleme
nt
Documen
ts
WBLRN
RWLF201
1
Create
Settlemen
t
Document
Lists from
Customer
Settlemen
t Lists
WLFV
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF201
2
Complete
Settlemen
t Request
Lists
WLFW
RWLF2057
Mass
Completi
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CLOSE
RWLF201
3
Mass
Release
of
Customer
Remunera
tion Lists
to
Financial
Accountin
g
WLFLK
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF201
4
Create
Customer
Settlemen
ts for
Settlemen
t
Requests
S_AL0_96000
192
RWLF2051
Generate
Customer
Settleme
nts from
Settleme
nt
Documen
ts
WLF1K
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 527
RWLF201
6
Create
Remunera
tion Lists
from
Customer
Settlemen
ts
S_AL0_96000
197
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF201
8
Mass
Release
of
Customer
Settlemen
ts for
Financial
Accountin
g
S_AL0_96000
212
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF201
9
Mass
Cancellati
on of
Settlemen
t Request
Lists
S_AL0_96000
307
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
RWLF202
0
Mass
Cancellati
on of
Customer
Settlemen
ts
S_AL0_96000
308
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
RWLF202
1
Mass
Cancellati
on of
Remunera
tion Lists
S_AL0_96000
306
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
RWLF202
2
Mass
Cancellati
on of
Customer
Settlemen
t Lists
S_AL0_96000
309
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 528
RWLF202
3
Mass
Price
Determina
tion for
Settlemen
t Request
Lists
S_AL0_96000
324
RWLF2054
Mass
Pricing
for
Settleme
nt
Manage
ment
Documen
ts
WAB_PRICING
RWLF202
4
Mass
Price
Determina
tion for
Payment
Document
s
S_AL0_96000
325
RWLF2054
Mass
Pricing
for
Settleme
nt
Manage
ment
Documen
ts
WAB_PRICING
RWLF202
5
Create
Remunera
tion Lists
from
Expense
Settlemen
ts
S_AL0_96000
333
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF202
6
Mass
Release
of
Expense
Settlemen
ts for
Financial
Accountin
g
S_AL0_96000
335
RWLF2056
Mass
Release
of
Settleme
nt
Manage
ment
Documen
ts
WAB_RELEASE
RWLF202
7
Mass
Cancellati
on of
Expense
Settlemen
t
S_AL0_96000
336
RWLF2055
Mass
Cancellati
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CANCEL
RWLF202
8
Complete
Settlemen
t
Requests
S_AC0_5200
0143
RWLF2057
Mass
Completi
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CLOSE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 529
RWLF202
9
Complete
Vendor
Billing
Document
s
S_AC0_5200
0169
RWLF2057
Mass
Completi
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CLOSE
RWLF203
0
Create
Settlemen
t Request
Lists from
Preceding
Document
s
WRLV
RWLF2053
Generate
Vendor
Settleme
nt Lists
from
Settleme
nt
Documen
ts
WRLVN
RWLF203
1
Complete
Expenses
Settlemen
ts
S_AC0_5200
0170
RWLF2057
Mass
Completi
on of
Settleme
nt
Manage
ment
Documen
ts
WAB_CLOSE
RWLF203
2
Reopen
Settlemen
t
Requests
S_AC0_5200
0172
RWLF2058
Mass
Reopenin
g of
Settleme
nt
Manage
ment
Documen
ts
WAB_REOPEN
RWLF203
3
Reopen
Vendor
Billing
Document
s
S_AC0_5200
0174
RWLF2058
Mass
Reopenin
g of
Settleme
nt
Manage
ment
Documen
ts
WAB_REOPEN
RWLF203
4
Reopen
Expenses
Settlemen
ts
S_AC0_5200
0175
RWLF2058
Mass
Reopenin
g of
Settleme
nt
Manage
ment
WAB_REOPEN
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 530
Documen
ts
RWLF205
9
Generate
Posting
Lists from
Settlemen
t
Requests
WBLRO
RWLF2052
Generate
Customer
Settleme
nt Lists
from
Settleme
nt
Documen
ts
WBLRN
RWLF205
9D
Dispatche
r: Create
Posting
Lists
WBLRO_DIS
P
RWLF2052D
Dispatch
er:
Create
Customer
Settleme
nt Lists
WBLRN_DISP
RWLF206
0
Generate
Customer
Settlemen
ts from
Settlemen
t
Requests
WLF1KO
RWLF2051
Generate
Customer
Settleme
nts from
Settleme
nt
Documen
ts
WLF1K
RWLF206
1
Create
Settlemen
t Lists
from
Settlemen
t
Requests
WRLVO
RWLF2053
Generate
Vendor
Settleme
nt Lists
from
Settleme
nt
Documen
ts
WRLVN
RWLF400
1
Delete
Archived
Vendor
Billing
Document
s from the
Database
WACLFR
WLF_DEL
Archiving
Vendor
Billing
Docs and
Vendor
Settleme
nts:
Delete
Program
RWLF400
2
Delete
Archived
Customer
Settlemen
t Lists
from
Database
WACBLR
WBU_DEL
Archiving
Customer
Settleme
nt Lists:
Delete
Program
RWLF400
3
Delete
Archived
Settlemen
WACLRR
WRECH_DEL
Archiving
Settleme
nt
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 531
t
Document
Lists from
Database
Documen
t Lists:
Delete
Program
RWLF400
4
Delete
Archived
Settlemen
t
Document
s from
Database
WACZRR
WZR_DEL
Archiving
Settleme
nt
Documen
ts: Delete
Program
RWLF400
5
Delete
Archived
Vendor
Settlemen
t Lists
from
Database
WACRLR
WREG_DEL
Archiving
Vendor
Settleme
nt Lists:
Delete
Program
RWLF400
6
Delete
Archived
Customer
Settlemen
ts from
Database
WACCIR
WCI_DEL
Archiving
Customer
Settleme
nts:
Delete
Program
RWLF400
7
Delete
Archived
Expense
Settlemen
ts from
Database
WACSIR
WSI_DEL
Archiving
Expense
Settleme
nts:
Delete
Program
RWLF700
1
Display
Document
Flow of
Vendor
Billing
Document
s
WFL1
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF700
2
Display
Document
Flow for
Customer
Settlemen
t Lists
WFL2
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF700
3
Display
Document
Flow for
Settlemen
t
Document
Lists
WFL3
RWLF1051
List
Output
Settleme
nt
Manage
ment
WLI2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 532
Documen
ts
RWLF700
4
Display
Document
Flow for
Settlemen
t
Document
WFL4
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF700
5
Display
Document
Flow for
Vendor
Settlemen
t Lists
WFL5
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF900
2
Generate
Extended
Remunera
tion Lists
From
Payment
Document
s
S_ALN_0100
0170
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF900
3
Create
Extended
Remunera
tion Lists
From
Posting
Lists
S_ALN_0100
0171
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF900
4
Settlemen
t
Document
s for
Applicatio
n Status
WAPZR
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF900
5
Vendor
Settlemen
t Lists for
Applicatio
n Status
WAPRL
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLF900
6
Generate
Remunera
tion Lists
from
S_ALN_0100
0172
RWLF9039
Create
Settleme
nt
WLF_RRLE_CREATE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 533
Vendor
Billing
Document
s
Documen
t Lists
RWLF900
7
Generate
Remunera
tion Lists
From
Customer
Settlemen
ts
S_ALN_0100
0173
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF900
8
Generate
Remunera
tion Lists
From
Expense
Settlemen
ts
S_ALN_0100
0174
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF900
9
Relevant
Payment
Document
s For
Extended
Remunera
tion List
Creation
S_ALN_0100
0175
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF901
0
Relevant
Customer
Settlemen
ts For
Extended
Remunera
tion List
Creation
S_ALN_0100
0176
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF901
1
Relevant
Posting
Lists For
Extended
Remunera
tion List
Creation
S_ALN_0100
0177
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF901
2
Relevant
Expense
Settlemen
ts for
Extended
Remunera
tion List
Creation
S_ALN_0100
0178
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
WLFSLRL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 534
t List
(Dialog)
RWLF901
3
Relevant
Vendor
Billing
Document
s,
Extended
Remunera
tion List
Creation
S_ALN_0100
0179
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF901
4
Simulate
Generatio
n of
Remunera
tion Lists
From
Payment
Document
s
S_ALN_0100
0371
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF901
5
Simulate
Generatio
n of
Remunera
tion Lists
From
Posting
Lists
S_ALN_0100
0372
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF901
6
Simulate
Generatio
n of
Remunera
tion Lists
From
Customer
Settlemen
ts
S_ALN_0100
0373
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF901
7
Generate
Simulation
of
Remunera
tion Lists
From
Expense
Settlemen
ts
S_ALN_0100
0375
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF901
8
Simulate
Generatio
n of
Remunera
tion List
From
Vendor
S_ALN_0100
0376
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 535
Billing
Document
s
RWLF901
9
Create
Extended
Remunera
tion Lists
from
Remunera
tion Lists
S_AEN_1000
0032
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF902
0
Relevant
Remunera
tion Lists
for
Extended
Remunera
tion List
Creation
S_AEN_1000
0033
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF902
1
Create
Simulation
of
Remunera
tion Lists
from
Remunera
tion Lists
S_AEN_1000
0034
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF902
2
Generate
Extended
Remunera
tion Lists
from
Preceding
Document
s
S_AEN_1000
0060
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF902
3
Relevant
Preceding
Document
s for
Extended
Remunera
tion List
Creation
S_AEN_1000
0065
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF902
4
Create
Simulation
of
Remunera
tion Lists
from
Preceding
Document
s
S_AEN_1000
0066
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 536
RWLF902
8
Generate
Extended
Remunera
tion Lists
from FI
Document
s
S_E37_17000
019
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF902
9
Generate
Simulation
Remunera
tion Lists
from FI
Document
s
S_E37_17000
020
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF903
0
Generate
Remunera
tion Lists
from
Vendor
Settlemen
ts
S_PRN_5300
0718
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF903
1
Generate
Simulation
of
Remunera
tion Lists
from
Vendor
Settlemen
ts
S_PRN_5300
0719
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
RWLF903
2
Relevant
Vendor
Settlemen
ts for
Extended
Remunera
tion List
Creation
S_PRN_5300
0720
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF903
3
Generate
Extended
Remunera
tion Lists
from SD
Billing
Document
s
S_E4R_3500
0021
RWLF9039
Create
Settleme
nt
Documen
t Lists
WLF_RRLE_CREATE
RWLF903
4
Generate
Simulation
of
Remunera
tion Lists
from SD
S_E4R_3500
0022
RWLF9042
Simulate
Settleme
nt
Documen
t Lists
WLF_RRLE_SIM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 537
Billing
Document
s
RWLF903
7
Relevant
SD Billing
Document
s for
Extended
Remunera
tion List
Creation
S_E4R_3500
0025
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF903
8
Relevant
FI
Document
s for
Extended
Remunera
tion List
Creation
S_E4R_3500
0024
RWLF_SETTLEMENT_L
IST_RL
Worklist
based
Creation
of
Settleme
nt
Documen
t List
(Dialog)
WLFSLRL
RWLF908
0
Posting
List
Creation
Dispatche
r
S_AEN_1000
0037
RWLF2052D
Dispatch
er:
Create
Customer
Settleme
nt Lists
WBLRN_DISP
RWLF908
1
Customer
Settlemen
t Creation
Dispatche
r
S_AEN_1000
0038
RWLF2051D
Dispatch
er:
Create
Customer
Settleme
nts
WLF1K_DISP
RWLF908
2
Mass
Release
Dispatche
r
S_AEN_1000
0075
RWLF2056D
Dispatch
er: Mass
Release
of
Settleme
nt
Manage
ment
Doc.
WAB_RELEASE_DISP
RWLF908
3
Settlemen
t Request
List
Creation
Dispatche
r
S_AEN_1000
0074
RWLF2053D
Dispatch
er:
Create
Vendor
Settleme
nt Lists
WRLVN_DISP
RWLF908
4
Extended
Remunera
tion List
Creation
S_AEN_1000
0083
RWLF9039D
Dispatch
er:
Create
Settleme
nt
WLF_RRLE_CREATE_
DISP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 538
Dispatche
r
Documen
t Lists
RWLF908
5
Dispatche
r Message
Output
S_E37_17000
021
RWLFWR14D
Dispatch
er:
Message
Output
for
Settleme
nt Mgmt
Documen
ts
WLN14D
RWLF908
6
Dispatche
r Mass
Reversal
RWLF2055D
Dispatch
er: Mass
Cancellati
on of
Settleme
nt
Manage
ment
Docs
WAB_CANCEL_DISP
RWLFFL
OW
Display
Document
Flow
Informatio
n for
Settlemen
t
Managem
ent
Document
s
WLFU
RWLF1051
List
Output
Settleme
nt
Manage
ment
Documen
ts
WLI2
RWLFIDO
C
Extended
IDoc
Reporting
WLFEIR
RWLFIDOC_NEW
IDoc
Processin
g
WLF_IDOC
RWLFM3
0
Automatic
Document
Adjustmen
t of
Vendor
Billing
Document
s
WLFM30
RWLFM99
Automati
c
Documen
t
Adjustme
nt of
Settleme
nt
Manage
ment
Documen
ts
WLFM99
RWLFM3
1
Automatic
Document
Adjustmen
t of
Expenses
Document
s
WLFM31
RWLFM99
Automati
c
Documen
t
Adjustme
nt of
Settleme
WLFM99
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 539
nt
Manage
ment
Documen
ts
RWLFM3
2
Automatic
Document
Adjustmen
t of
Vendor
Settlemen
ts
WLFM32
RWLFM99
Automati
c
Documen
t
Adjustme
nt of
Settleme
nt
Manage
ment
Documen
ts
WLFM99
RWLFM6
0
Automatic
Document
Adjustmen
t of
Customer
Settlemen
ts
WLFM60
RWLFM99
Automati
c
Documen
t
Adjustme
nt of
Settleme
nt
Manage
ment
Documen
ts
WLFM99
RWLFM4
0
Automatic
Document
Adjustmen
t of
Payment
Document
s
WLFM40
RWLFM99
Automati
c
Documen
t
Adjustme
nt of
Settleme
nt
Manage
ment
Documen
ts
WLFM99
RWLFWR
01
Messages
from
Vendor
Billing
Document
s
WLN1
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
02
Messages
from
Customer
WLN2
RWLFWR14
Issue
Message
s from
WLN14
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 540
Settlemen
t Lists
Settleme
nt
Manage
ment
Documen
ts
RWLFWR
03
Messages
from
Remunera
tion Lists
for Vendor
Billing
Document
s
WLN3
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
04
Messages
from
settlement
requests
WLN4
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
05
Messages
from
Settlemen
t Request
Lists
WLN5
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
06
Messages
from
Remunera
tion Lists
for
Settlemen
t
Requests
WLN6
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
10
Messags
from
Customer
Settlemen
ts
WLN10
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
11
Messages
from
WLN11
RWLFWR14
Issue
Message
WLN14
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 541
Expenses
Settlemen
ts
s from
Settleme
nt
Manage
ment
Documen
ts
RWLFWR
12
Messages
from
Remunera
tion Lists
for
Customer
Settlemen
ts
WLN12
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLFWR
13
Messages
from
Remunera
tion Lists
for
Expenses
Settlemen
ts
WLN13
RWLFWR14
Issue
Message
s from
Settleme
nt
Manage
ment
Documen
ts
WLN14
RWLWRC
INV
Archive
Customer
Settlemen
ts
WACCIA
WCI_WRI
Archiving
Customer
Settleme
nts: Write
Program
RWLWRIL
S
Archive
Settlemen
t
Document
List
WACLA
WRECH_WRI
Archiving
Settleme
nt
Documen
t Lists:
Write
Program
RWLWRI
NV
Archive
Vendor
Billing
Document
s
WACLFA
WLF_WRI
Archiving
Vendor
Billing
Docs and
Vendor
Settleme
nts: Write
Program
RWLWRP
LS
Archive
Customer
Settlemen
t Lists
WACBA
WBU_WRI
Archiving
Customer
Settleme
nt Lists:
Write
Program
RWLWRS
INV
Activate
Expense
WACSIA
WSI_WRI
Archiving
Expense
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 542
Settlemen
ts
Settleme
nts: Write
Program
RWLWRS
LS
Archive
Settlemen
t Request
List
WACRLA
WREG_WRI
Archiving
Vendor
Settleme
nt Lists:
Write
Program
RWLWRS
MR
Archive
Settlemen
t
Document
s
WACZRA
WZR_WRI
Archiving
Settleme
nt
Documen
ts: Write
Program
RWLF300
1
Read
Vendor
Billing
Document
s from the
Archive
(Display
Items)
WLFT
RWLFLIST
Documen
t Monitor
WLI5
RWLF300
2
Read
Customer
Settlemen
t Lists
from the
Archive
(Display
Items)
WLA8
RWLFLIST
Documen
t Monitor
WLI5
RWLF300
3
Read
Settlemen
t
Document
Lists from
the
Archive
(Display
Items)
WLA5
RWLFLIST
Documen
t Monitor
WLI5
RWLF300
4
Read
Settlemen
t
Document
s from the
Archive
(Display
Items)
WLA6
RWLFLIST
Documen
t Monitor
WLI5
RWLF300
5
Read
Vendor
Settlemen
t Lists
from the
WLA7
RWLFLIST
Documen
t Monitor
WLI5
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 543
Archive
(With
Items)
RWLF300
6
Read
Customer
Settlemen
ts (with
Item Data)
from the
Archive
WLACII
RWLFLIST
Documen
t Monitor
WLI5
RWLF300
7
Read
Expense
Settlemen
ts (with
Item Data)
from the
Archive
WLASII
RWLFLIST
Documen
t Monitor
WLI5
RWLF90
60
List
Output of
Inbound
IDoc for
Settlemen
t Request
List
WRLI
RWLFIDOC_NEW
IDoc
Monitor
WLF_IDOC
RWLF90
61
List
Output of
Inbound
IDocs for
Payment
Document
s
WZRI
RWLFIDOC_NEW
Idoc
Monitor
WLF_IDOC
Obsolete Tcode
Successor Tcode
WLR1
WLFSLRL
WBL1
WBLRN
OAGZ
n/a
Required and Recommended Action(s)
Pre-Check is performed for the component LO-AB. Custom code adoption on the new
DB-Design can be checked in the start release to identify the code places which have to
adjust to the new DB-Structures. Batch or online processes which needed the obsolete
transactions or reports have to be adjusted so that the new transactions and reports are
used instead the obsolete once. Mostly all replaced reports and transaction where part of
the solution portfolio of SAP_APPL and EA-RETAIL of the Business Suite To simplify
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 544
the Conversion to S/4 it is recommended to adjust the business process in the start release
by a step by step replacement of the obsolete transactions by the once which will be part
of S/4. You have to activate the software component EA-RETAIL to use the successor
reports or transactions. You can also adopt the business processes in S/4 without to
change the processes in the current release.
Related SAP Notes
Custom Code related
information
SAP Notes: 2197892, 2197898, 2204135, 2203518.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 545
21.Logistics – ATP
21.1 S4TWL - New advanced ATP in SAP S/4HANA – Table VBBS
Application Components:SD-BF-AC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267745
S4TWL - New advanced ATP in SAP
S/4HANA, on-premise edition – Table
VBBS
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. In this
scenario, the following SAP S/4HANA Transition Worklist item applies.
Solution
Business Value
In S/4HANA it is possible to aggregate data in real time, so the aggregate-table for sales
order requirements VBBS is not necessary any more.
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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 546
Required and Recommended Action(s) depending on S/4HANA target release
Depending on the target release of S/4HANA you may have to apply following actions:
S/4HANA 1511 and S/4HANA 1610
There are two optional checks to be carried out before the upgrade to verify if the VBBS
is used:
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.
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.
S/4HANA 1709 and newer
The necessary actions are automated and executed in SUM phase using identifying name
ATP_XPRA_SUITE_TO_S4_V2. Manual actions as described for release S/4HANA 1511 and
S/4HANA 1610 are not needed.
Related SAP Notes
Custom code-related information
SAP Note: 2209696
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 547
22.Logistics – DSD
22.1 S4TWL - Direct Store Delivery
Application Components:LE-DSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273317
S4TWL - Direct Store Delivery
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Direct Store Delivery is part of the SAP S/4HANA compatibility scope, which comes
with limited usage rights. For more details on the compatibility scope and it’s expiry date
and links to further information please refer to SAP note 2269324. In the compatibility
matrix attached to SAP note 2269324, Direct Store Delivery can be found under the ID
475.
This means that you need to migrate from Direct Store Delivery to its designated
alternative functionality Last Mile Distribution for Direct Distribution before expiry of
the compatibility pack license. This note shall provide an overview on the scope of Direct
Store Delivery which is going to expire with the compatibility pack license, how this
maps to the designated alternative functionality, if this alternative functionality is already
available or when it’s planned to be available and how you can migrate to the alternative
functionality.
This note will regularly be updated to reflect more details on the alternative functionality
and the migration.
Business Process-Related Information
The functionality of Direct Store delivery provides tour execution capabilities for pre-
ordered delivery driver scenario, van sales scenario and preseller/merchandiser scenario.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 548
All logistics scenarios enable delivery of goods, handling of empties and returns,
collection of cash and taking service notes. Creation and maintenance of visit plans is
rounding up the functionality.
Within the alternative solution Last Mile Distribution you will get all execution
capabilities following a roadmap until 2022. Visit planning capabilities will be provided
by cloud based visit and activity management capabilities within SAP Sales Cloud or can
be integrated form 3rd party Planning tools.
The first version of Last Mile Distribution for Direct Distribution is released with
S/4HANA OP 2020 and provides the pre-ordered delivery driver scenario paperbased.
Further details on the roadmap can be found in SAP Roadmap Explorer on
http://www.sap.com
Required and Recommended Action(s)
As Direct Store Delivery can be used until the expiry date of the compatibility pack
license, it’s up to each customer to decide, when (with which of the coming SAP
S/4HANA releases) they want to migrate to the designated alternative functionality.
Though the decision, at which point in time this will be done, should be taken early in
advance in order to plan accordingly for the migration efforts.
There is no tool supported migration from Direct Store Delivery to Last Mile Distribution
available, please get in contact with SAP Consulting to investigate migration path
options.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, SAP Direct
Distribution, Direct Store Delivery
22.2 S4TWL - Direct Store Delivery in SAP S/4HANA
Application Components:LE-DSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273317
S4TWL - Direct Store Delivery
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 549
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Direct Store Delivery is part of the SAP S/4HANA compatibility scope, which comes
with limited usage rights. For more details on the compatibility scope and it’s expiry date
and links to further information please refer to SAP note 2269324. In the compatibility
matrix attached to SAP note 2269324, Direct Store Delivery can be found under the ID
475.
This means that you need to migrate from Direct Store Delivery to its designated
alternative functionality Last Mile Distribution for Direct Distribution before expiry of
the compatibility pack license. This note shall provide an overview on the scope of Direct
Store Delivery which is going to expire with the compatibility pack license, how this
maps to the designated alternative functionality, if this alternative functionality is already
available or when it’s planned to be available and how you can migrate to the alternative
functionality.
This note will regularly be updated to reflect more details on the alternative functionality
and the migration.
Business Process-Related Information
The functionality of Direct Store delivery provides tour execution capabilities for pre-
ordered delivery driver scenario, van sales scenario and preseller/merchandiser scenario.
All logistics scenarios enable delivery of goods, handling of empties and returns,
collection of cash and taking service notes. Creation and maintenance of visit plans is
rounding up the functionality.
Within the alternative solution Last Mile Distribution you will get all execution
capabilities following a roadmap until 2022. Visit planning capabilities will be provided
by cloud based visit and activity management capabilities within SAP Sales Cloud or can
be integrated form 3rd party Planning tools.
The first version of Last Mile Distribution for Direct Distribution is released with
S/4HANA OP 2020 and provides the pre-ordered delivery driver scenario paperbased.
Further details on the roadmap can be found in SAP Roadmap Explorer on
http://www.sap.com
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 550
As Direct Store Delivery can be used until the expiry date of the compatibility pack
license, it’s up to each customer to decide, when (with which of the coming SAP
S/4HANA releases) they want to migrate to the designated alternative functionality.
Though the decision, at which point in time this will be done, should be taken early in
advance in order to plan accordingly for the migration efforts.
There is no tool supported migration from Direct Store Delivery to Last Mile Distribution
available, please get in contact with SAP Consulting to investigate migration path
options.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, SAP Direct
Distribution, Direct Store Delivery
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 551
23.Logistics - Environment, Health & Safety
(EHS)
23.1 S4TWL - Deprecation of EHS Data Series and Amounts
Application Components:EHS-MGM, EHS-SUS-FND
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2338405
S4TWL - Deprecation of EHS Data
Series and Amounts
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 552
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.
Other Terms
Environment, Health and Safety
23.2 S4TWL - Deprecation of 'Inspect Safety Control' Fiori app
Application Components:EHS-MGM-RAS, EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2343825
S4TWL - 'Inspect Safety Control' Fiori
app no longer available
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 553
Required and Recommended Action(s)
Inform your business users.
How to Determine Relevancy
This Simplification Item is relevant if you have the 'Inspect Safety Control' Fiori
application in use.
Other Terms
Environment, Health and Safety, EHS Management
23.3 S4TWL - Deprecation of 'Retrieve Safety Information' Fiori app
Application Components:EHS-SUS-HS, EHS-MGM-RAS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2343826
S4TWL - 'Retrieve Safety Information'
Fiori app no longer available
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 554
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.
Other Terms
Environment, Health and Safety
23.4 S4TWL - Simplification of Authorizations in Incident Management
Application Components:EHS-MGM-INC, EHS-SUS-IM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2350330
S4TWL - Simplification of authorizations
in Incident Management
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 555
EHHSS_INC3 (EHSM: Incident Group)
EHHSS_INC5 (EHSM: Incident by Location)
The following authorization objects have been newly introduced:
EHHSS_INC6 (EHS: Incident)
This replaces EHHSS_INC1 and EHHSS_INC5
EHHSS_INC7 (EHS: Incident Group)
This replaces EHHSS_INC3
The following standard BAdI implementations together with their implementing standard
classes were removed (the BAdI Definition BADI_EHFND_BO_EXT_AUTH_CHECK
itself still exists):
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 BAdI implementations (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 BAdI implementations do no longer exist, authorization checks on
the authorization objects 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 556
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.
In case you have previously already done custom BAdI implementations of the BAdI
Definition BADI_EHFND_BO_EXT_AUTH_CHECK, please keep in mind the
following:
These custom BAdI implementations are still active and being executed.
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.
Other Terms
Environment, Health, and Safety; EHS Management
23.5 S4TWL - Removal of EHS Home Screens
Application Components:EHS-MGM-INC, EHS-MGM-RAS, EHS-SUS-IM, EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2350447
S4TWL - Removal of EHS home page
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 557
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.
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.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 558
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.
Other Terms
Environment, Health, and Safety; EHS Management
23.6 S4TWL - Specification Workbench Adjustments
Application Components:EHS-BD-SPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2439345
S4TWL - Specification Workbench
related Simplifications and Adaptions
Symptom
You are carrying out a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The following adjustments have been done in the area Specification Workbench:
The Specification Workbench is now enabled for SAP Fiori Theme
rendering. Therefore, the ENTER button on the Specification Search screen, is
now performing an input validation. That action makes the environment
parameter Confirm Starts Specification Search
(SP_SEARCH_START_ENTER), obsolete. The button F8 and the screen button
Hitlist, generate the search hitlist.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 559
none
How to Determine Relevancy
This note is only relevant in case you make use of the Specification Workbench.
Other Terms
S4TC, S/4 transition
23.7 S4TWL - Simplification of Incident Management workflows
Application Components:EHS-SUS-IM, EHS-MGM-INC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2350795
S4TWL - Simplification of Incident
Management workflows for fatality and
cost collector notification
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 560
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.
Other Terms
Environment, Health, and Safety; EHS Management
23.8 S4TWL - Changed data model for listed substances
Application Components:EHS-MGM-RAS, EHS-MGM-FND, EHS-SUS-FND, EHS-SUS-EM, EHS-
SUS-PMA, EHS-SUS-HS, EHS-MGM-PRC, EHS-MGM-ENV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2376165
S4TWL - Changed data model for listed
substances
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 561
Symptom
You are doing an upgrade to SAP S/4HANA 1511 or higher, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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
afterwards eliminate duplicate entries.
Business Process related information
There are no changes in the general business logic.
Required and Recommended Action(s)
Run the following report manually:
Transfer your listed substances to the new table
Only required for system conversions to SAP S/4HANA 1511. Not required for
system conversions to SAP S/4HANA 1610 or higher.
Run report R_EHFND_LISU_MIGRATION
This report transfers existing listed substances from
table EHFNDD_LISU_ROOT to the new table EHFNDD_LISU_RT.
Comment: This report is run automatically when converting to SAP
S/4HANA 1610 and higher.
Run the following report optionally:
Eliminate duplicate entries
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 562
Run report R_EHFND_LISU_SUBSTITUTE
This report eliminates duplicate entries in table EHFNDD_LISU_RT by
replacing customer-specific listed substances with equivalent SAP-specific
listed substances (where possible).
Please read the documentation of the report for functional details.
Be aware that the report replaces listed substances according to built in logic;
there is no possibility for selective replacement.
How to Determine Relevancy
This Simplification Item is relevant if you make use of listed substances in EHS. This is
the case if table EHFNDD_LISU_ROOT contains entries.
Other Terms
Environment, Health, and Safety, EHS Management
23.9 S4TWL - Changed data model for Occupational Exposure Limits
Application Components:EHS-MGM-RAS, EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2442566
S4TWL - Changed data model for
Occupational Exposure Limits (OELs)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 563
Starting with S/4HANA 1709 EHS Health and Safety Management uses the new data
object Compliance Requirement which had been introduced by EHS Environment
Management in earlier releases. This impacts the way how Occupational Exposure
Limits (OELs) for Listed Substances are maintained and handled within Health and
Safety Management:
OEL - Data maintenance
OELs are no longer maintained via the application Manage Regulatory Lists -
OELs. This application has been deprecated.
Instead, OELs are maintained as Compliance Requirements using the new
application Manage Compliance - Regulations, Policies.
OEL - Configuration
The customizing activity to define regulatory lists for OELs (= Environment,
Health and Safety -> Health and Safety Management -> Master Data
Configuration -> Agents -> Specify Regulatory Lists for OELs) is no
longer needed and was removed from the IMG.
The contents of the above customizing table together with the OELs from the deprecated
application Manage Regulatory Lists - OELs are automatically migrated during the
upgrade into new Compliance Requirements. That data will automatically be migrated
from the old to the new data model; this is done by XPRA (=EXecution of PRogram
After Import) R_EHFND_REQ_MIGRATION. For more details on this XPRA see the
according report documentation in the SAP system.
Business Process related information
The Health and Safety business processes do not change as such. But the data
maintenance of Occupational Exposure Limits (OELs) is done differently now.
Required and Recommended Action(s)
Inform your users about this changed way of maintaining Occupational Exposure
Limits (OELs).
Train your users on the new application Manage Compliance - Regulations, Policies.
Make sure the users working with the old application Manage Regulatory Lists -
OELs now have the new application Manage Compliance - Regulations,
Policies as part of their FIORI launchpad (should be given by default if you are
using the standard EHS roles).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 564
Check the OEL data migration (after the actual upgrade):
Start the new application Manage Compliance - Regulations, Policies.
Select all Compliance Requirements.
These have been generated by the XPRA (see above) during the
upgrade.
They have names like "Migrated <name of former OEL list>",
where <name of former OEL list> strands for the name how your
list used to be named in the customizing activity to define
regulatory lists for OELs (see paragraph "Description").
If you are satisfied with the results, remove the text "Migrated" from the
Compliance Requirement names.
Please note: The old customizing activity to define regulatory lists for OELs
(see paragraph "Description") will no longer be visible in the IMG after the upgrade. But
the according customizing table still exists and can be viewed with transaction SM30
using maintenace view EHFNDV_OELREGL.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you have defined at least one
Occupational Exposure Limit (OEL). This is the case if table EHFNDD_REGL_OEL contains
at least 1 entry.
Other Terms
Environment, Health, and Safety; EHS Management; EHS; EHS Management; Risk
Assessment; Health & Safety Management; Health and Safety Management
23.10S4TWL - Removal of task und document tab pages on incidents
Application Components:EHS-MGM-INC, EHS-SUS-IM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2429619
S4TWL - Simplification of tasks and
documents/reports tab in Incident
Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 565
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
Up to now, documents and tasks could be managed on several tabs in Incident
Management, i.e. People, Assets, Investigation, Releases, Notice of Violation. The aim
was to provide a central place for the creation and management of documents and tasks.
On the tabs listed below the subordinated tab Reports/Documents and the subordinated
tab Tasks were removed:
People
Assets
Releases
Notice of Violation
Investigation
Adding a new document or a link is now centralized on the tab Reports/Documents. The
popup which appears for adding a new document or link was enhanced by the possibility
to select the referenced object. This selection list contains all people, assets, releases,
notice of violations, investigations that are entered for the incident and the incident itself.
Adding a new task is now centralized on the tab Tasks. The creation of a new task was
enhanced by the possibility to select the referenced object. This selection list contains all
people, assets, releases, notice of violations, investigations that are entered for the
incident and the incident itself.
The behavior in processing documents and tasks for a Root Cause Analysis or an
Investigation Step was not changed.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 566
There are no changes in the general business logic.
Required and Recommended Action(s)
If you are using the standard Incident Management User Interface (UI), no action is
required.
If you have custom implementation on the subordinated tab Reports/Documents or on the
subordinated tab Tasks you have to ensure that your custom implementation is also
covered on the remaining main tab Reports/Documents respectively Tasks.
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.
Other Terms
Environment, Health, and Safety; EHS; EHS Management; Incident Management
23.11S4TWL - Changed process for risk identification
Application Components:EHS-SUS-HS, EHS-MGM-RAS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2442567
S4TWL - Changed process for risk
identification
Symptom
You are performing a system conversion to SAP S/4HANA. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 567
Roughly speaking, the EHS Risk Assessment process consists of these three steps:
Identify risks
Plan the assessment of the risks (by grouping them into Risk Assessment projects)
Assess and mitigate the risks (by processing the Risk Assessment projects)
Before S/4HANA 1709, these three steps were addressed by one single application called
Risk Assessment.
In S/4HANA 1709, there are the two new applications Identify Risks and Assign Risks to
Projects; these are now used for the above-mentioned steps 1 and 2. The existing
application Risk Assessment was simplified in a way that it now only supports step 3 from
above. This means that the identification and grouping of risks can no longer be done
from within the application Risk Assessment, but has to be done via the new applications
Identify Risks and Assign Risks to Projects. This means that the button/feature "Identify
Risks" no longer exists in the application Risk Assessment.
Additional Technical Information
- All affected data dictionary objects have been marked with "OBSOLETE" in their
names; these objects will only exist for a limited amount of time.
- The old Guided Activity Floorplan (GAF) behind the button "Identify Risks" still exists
(as mentioned), but will technically no longer work.
Business Process Related Information
The business process "Risk Assessment" has not changed as such; it has changed with
respect to the applications to be used in order to step through the complete process.
Required and Recommended Action(s)
Inform the affected end users about this change.
Train the affected end users on the new applications Identify Risks and Assign Risks to
Projects.
Make sure that the two new applications are part of the relevant users' FIORI
launchpad (should be given by default if you are using the SAP roles).
Please also note the technical information given above saying that the old GAF "Identify
Risks" will no longer work. In case you are calling or enhancing this functionality using
customer-specific implementations, this will no longer work.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 568
How to Determine Relevancy
This Transition Worklist item is relevant for you if you have Health and Safety
Management (formerly known as Risk Assessment) in use.
You have Health and Safety Management in use if table
EHHSSD_RAS_ROOT contains at least 10 entries.
Other Terms
Environment, Health, and Safety; EHS Management; EHS; EHS Management; Risk
Assessment; Health & Safety Management; Health and Safety Management
23.12S4TWL - Industrial Hygiene and EC interfaces
Application Components:XAP-EM, EHS-IHS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267781
S4TWL - Industrial Hygiene and EC
interfaces
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 on-premise edition 1511, this solution is no
longer available. However, customers can use the incident management solution and the
health and safety management solution of Environment, Health, and Safety as part of SAP
S/4HANA to support their business processes.
Interfaces to SAP Environmental Compliance
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 569
Customers can use SAP Environmental Compliance (SAP EC) to support emissions and
compliance-relevant processes. In addition, Environmental Compliance provides
interfaces to exchange data with other applications.
In SAP S/4HANA on-premise edition 1511, the following interfaces are not available:
Environmental Compliance - Specification Database:
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
Environmental Compliance - Incident:
Environmental Compliance will not be able to read incident or location data
from Environment, Health, and Safety as part of SAP S/4HANA
EAM - Environmental Compliance:
Enterprise Asset Management (EAM), as part of SAP S/4HANA, will not be
able to display Environmental Compliance data
A successor solution for SAP Environmental Compliance is planned for Environment,
Health, and Safety in a future SAP S/4HANA delivery.
Business Process related information
Industrial Hygiene and Safety (EHS-IHS) is replaced by the new incident management
solution and health and safety management solution of Environment, Health, and
Safety as part of SAP S/4HANA.
Business processes are described in the documentation for Environment, Health, and
Safety as part of SAP S/4HANA.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
CBIH00, CBIH02, CBIH03, CBIH12, CBIH13, CBIH14, CBIH42,
CBIH43, CBIH50, CBIH51, CBIH52, CBIH72, CBIH73, CBIH82,
CBIH83, CBIH88, CBIH89, CBIH92, CBIH92OLD, CBIH93OLD,
CBIHB0, CBIHB1, CBIHB2, CBIHB3, CBIHB4, CBIHB5, CBIHB6,
CBIHCH1, CBIHCH2, CBIHCH3, CBIHCH4, CBIHM2, CBIHM3,
CBIHMR01, CBIHMR02, CBIHMR03, CBIHMR04, CBIHMR05,
CBIHMR06, CBIHMR07, CBIHMR08, CBIHMR09, CBIHR01,
CBIHSR01, CBIHT0, CBIHT1, CBIHT12, CBIHT13, CBIHT2,
CBIHT22, CBIHT23, CBIHT3, CBIHT32, CBIHT33, CBIHT4,
CBIHT5, CBIHT52, CBIHT53, CBIHT6, CBIHT62, CBIHT63,
CBIHT7, CBIHT72, CBIHT73,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 570
EHSAMBTAET, EHSAMED, EHSASSIGN, EHSASSLTA,
EHSASSPERS, EHSBC02, EHSBP11, EHSBP12, EHSBP13,
EHSBP31, EHSBP32, EHSBP33, EHSBP41, EHSBP42,
EHSBP43, EHSBP51, EHSBP52, EHSBP53, EHSCALPROX,
EHSCBER, EHSCDCT, EHSCMAS, EHSDATIMP, EHSDIAGSL,
EHSEVAL00, EHSEXIST0, EHSH_C_NR_EXA_CO,
EHSH_C_NR_NEWPER, EHSH_C_NR_RECN,
EHSH_C_NR_VAC_ID, EHSH_D_CALPHYS, EHSH_D_PCP,
EHSK_D_ACTION_STATUS, EHSK_D_ASSPERSPROT,
EHSK_D_GEN_SERVERS, EHSK_D_IAL,
EHSK_D_REP_GEN_QUEUE, EHSK_D_REP_REQUESTS,
EHSK_D_RISK_ASSESS, EHSK_D_SHIP_ORDERS,
EHSMQUEST, EHSMQUEST01, EHSPERSHC1, EHSPP01,
EHSPRANZ, EHSPRLOE, EHSQCATOH, EHSQEVAL01,
EHSQUESTOH, EHSSCAN, EHSSERV, EHSSERV01,
EHSSERV11, EHSSERV30, EHSSERV50, EHSSTRU00,
EHSSUGGP, EHSTERM01, EHSVA02, EHSVU01,
EHSVU01_SELSCREEN, EHSVU11, EHSVU21, EHSVU31,
ENHE_SYNCSUB, ENHE_SYNCUNIT
Related SAP Notes
Custom Code related information
SAP Note: 2217206
23.13S4TWL - Renovation of EHS authorization concept
Application Components:EHS-MGM-FND, EHS-MGM-ENV, EHS-MGM-RAS, EHS-MGM-INC,
EHS-SUS-FND, EHS-SUS-EM, EHS-SUS-IM, EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2442150
S4TWL - Renovation of EHS
authorization concept
Symptom
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 571
Solution
Description
The SAP authorization concept uses so called authorization objects which allow
principal access to certain kinds of business objects (e.g. Locations, Incidents). The
authorization object fields then define, which of these business objects exactly a user
may access based on attributes of these objects (e.g. Locations of type ABC, Incidents at
location XYZ).
Some EHS authorization object fields correspond to non-mandatory attributes in the
respective business object. Technically speaking these attributes may have an empty
value (value ' ') for an attribute which is checked in an authorization check. The logic
of this special case of authorization check was changed in order to make the whole
authorization concept safer and more consistent. The following example demonstrates
this change:
Example
Earlier behaviour:
IF...
...user has authorization to
access incidents at ...
THEN...
...user can access incidents
without assigned location
...user can access incidents
at location 'XYZ'
location 'XYZ'
yes(!)
yes
location ' '
yes
no
New behaviour:
IF...
...user has authorization to
access incidents at ...
THEN...
...user can access incidents
without assigned location
...user can access incidents
at location 'XYZ'
location 'XYZ'
no(!)
yes
location ' '
yes
no
Business Process related information
Your business processes are not (directly) affected by this change.
But you might need to adjust your authorization concept in order to make sure that your
users will still be able to access all those data objects they can access today.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 572
If your current EHS authorization concept already explicitly takes into account the
value ' ' for the authorization object fields listed below, then there is nothing to do.
If it is okay for you that your users will no longer be able to access objects
with missing data for the attributes listed below (e.g. incidents without location
assignment), then there is nothing to do.
Else you need to adjust your authorization concept for the authorization objects listed
below.
Make sure you extend all your profiles by an additional authorization object
field value ' ' where you want users to further access the according data
objects with missing assignments (i.e. with empty attribute values).
EHS area
Authorization object
Relevant authorization object fields
Name
technically
Name
technically
EHS
Foundation
Location
EHFND_LOC
Location
Authorization Group
Plant ID
Cost Center
Company Code
Business Area
LOCAUTHGRP
LOCPLANT
LOCCOST
LOCCOMP
LOCBUSAREA
Compliance
Requirement
EHFND_REQ
Country
Region
LOCCOUNTRY
LOCREGION
Sample
Management
EHFND_SPL
Location
Authorization Group
Business Area
Company Code
Cost Center
Plant ID
LOCAUTHGRP
LOCBUSAREA
LOCCOMP
LOCCOST
LOCPLANT
Environment
Management
Scenario
EHENV_SCEN
Location
Authorization Group
Business Area
Company Code
Cost Center
Country
Plant ID
Region
LOCAUTHGRP
LOCBUSAREA
LOCCOMP
LOCCOST
LOCCOUNTRY
LOCPLANT
LOCREGION
Health and
Safety
Management
Health Surveillance
Protocol
EHHSS_HSP
Country Key
Region
COUNTRY
REGIO
Risk Assessment
EHHSS_RAS
Location
Authorization Group
Business Area
Company Code
Cost Center
Plant ID
LOCAUTHGRP
LOCBUSAREA
LOCCOMP
LOCCOST
LOCPLANT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 573
Incident
Management
Incident Report
EHHSS_INC2
Organizational Unit
ID
Plant ID
ORGUNIT_ID
PLANT_ID
Incident
EHHSS_INC6
Country Key
Location ID
Organizational Unit
ID
Plant ID
Region
COUNTRY
LOC_ID
ORGUNIT_ID
PLANT_ID
REGION
How to Determine Relevancy
This Transition Worklist item is relevant for you if you have EHS in use. EHS consists of
the 3 functional areas Health and Safety Management (formerly known as Risk
Assessment), Incident Management and Environment Management.
You have Health and Safety Management in use if table
EHHSSD_RAS_ROOT contains at least 10 entries.
You have Incident Management in use if table EHHSSD_INC_ROOT contains at
least 10 entries.
You have Environment Management in use if table
EHENVD_SCEN_ROOT contains at least 1 entry.
Other Terms
Environment, Health, and Safety; EHS Management; EHS; EHS Management; Risk
Assessment; Health & Safety Management; Health and Safety Management; Incident
Management; Environment Management
23.14S4TWL - Changed data model for Job Steps
Application Components:EHS-SUS-HS, EHS-MGM-RAS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2446055
S4TWL - Technical renovation of job
step concept
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 574
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The way how Job Steps and their information (like name and sequence number) is stored
in EHS has changed. This data used to be stored in the Risk Assessment Business Object;
now it is stored in the new Jobs at Location Business Object. A comparison between old
and new data model can be seen in the attachment.
During the upgrade that data will automatically be migrated from the old to the new data
model (this is done by XPRA (=EXecution of PRogram After
Import) R_EHHSS_XPRA_INIT_JOBSTEP_BO; more details see the according report
documentation in your SAP system).
Note: This item first of all affects customers who have done their own implementations
which use Job and Job Step information.
Business Process related information
Your business processes are not affected at all by this change.
Users will only experience one slight little change: The name of a Job Step used to be an
individual text for Risk Assessments and their follow-up Risk Assessments. Now Risk
Assessments and their follow-up Risk Assessments share the same Job Step names.
Example:
You have an open risk assessment for job A.
Job A consists of the steps "Work" and "Clean up".
You finish this risk assessment and close it.
Some time later you follow-up the risk assessment because things have changed.
In the follow-up risk assessment you decide to rename the job step 2 into "Clean up
workplace".
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 575
Earlier behaviour:
The job step name of the previous risk assessment stays "Clean up".
New behaviour:
The job step name of the previous risk assessment also becomes "Clean up
workplace".
This new behaviour enforces the semantically consistent use of job steps: A job step must
throughout its' life cycle always semantically mean the same thing.
Jop steps from now on may only be syntactically changed (like corrections of spelling
errors), no longer semantically.
Re-using existing job steps for semantically different activities by just renaming the
steps is no longer possible, because this also changes the semantics of that step in
the past (unless this effect is actually intended).
If an existing job step is no longer needed and in parallel a new job step is required,
then you need to "phase out" the no longer needed job step by removing its' risks
and, in parallel, need to create a new, additional job step with new risks.
Required and Recommended Action(s)
Communicate to your end users this change in job step naming behaviour as this
might be quite relevant to them.
Find out whether you have customer specific implementations in place which
access the following table:
EHHSSD_RAS_STEP
Adjust your implementations to the new data model (see attachment).
How to Determine Relevancy
This Transition Worklist item is relevant for you if you have EHS jobs and job steps in
use. This is the case if table EHHSSD_RAS_STEP contains at least 1 entry.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 576
Environment, Health, and Safety; EHS Management; EHS; Risk Assessment; Health &
Safety Management; Health and Safety Management
23.15S4TWL - Adjustments needed due to changed data model for
Compliance Requirement
Application Components:EHS-SUS-EM, EHS-MGM-ENV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2504323
S4TWL - Adjustments needed due to
changed data model of compliance
requirement
Symptom
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The data model of the compliance requirement was changed in S/4HANA 1709. There is
an automatic data conversion during the upgrade that adjusts all existing
data, however, manual pre-work is still necessary.
Business Process related information
If you do not perform the manual steps described below, your S/4HANA
upgrade/conversion might stop during the EHS data conversion step.
Required and Recommended Action(s)
In all productive clients on your system, replace the regulatory list type DEFAULT_LIST
with a new entry for each chemical property in use.
Log on to your backend system.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 577
Start transaction SPRO.
In the Customizing for Environment, Health & Safety, open the activity
under: Environment Management -> Compliance Requirement -> Specify
Regulatory List Types.
Copy the entry DEFAULT_LIST to a new entry HHV, and then, assign a chemical
property HHV to it.
If you use additional chemical properties within the regulatory list type
DEFAULT_LIST, then for each additionally defined chemical property create a
new regulatory list type with the corresponding name.
Delete the record DEFAULT_LIST.
How to Determine Relevancy
This Transition Worklist item is relevant for you, if table EHFNDD_REQ_REGL
contains more than 5 entries.
Other Terms
Environment, Health, and Safety; EHS; EHS Management; Environment Management;
EM
23.16S4TWL - Deprecation of action templates in control master
Application Components:EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2590858
S4TWL - Deprecation of action
templates in control master
Symptom
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 578
Solution
Description
The basic process in Health and Safety Management is the identification and handling of
occupational risks in a working environment. Mitigation of such occupational risks
usually is done by defining controls. To define and track the implementation of these
controls, tasks can be defined for each needed control.
Health and Safety Management used to have a feature where tasks could be defined by
choosing action templates. Action templates are control-specific, pre-defined sets of
actions/tasks that are specified in the control master data. This feature no longer exists.
Business Process related information
The business process as such is not affected by this change. However, users now need to
manually specify all needed tasks for control implementations.
Required and Recommended Action(s)
Inform your Health and Safety Management business users about this functional change.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you are using action templates. This is
the case if table EHFNDD_CTRL_ACTT contains any entries.
Other Terms
Environment, Health, and Safety; EHS; EHS Management; Health and
Safety Management
23.17S4TWL - Simplification of Risk Assessment Lifecycle
Application Components:EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2603300
S4TWL - Deprecation of risk
assessment lifecycle workflow
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 579
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
Whenever a new risk assessment project was created, Health and Safety Management
used to trigger a workflow known as Risk Assessment Lifecycle. The standard recipient of
this workflow was the creator of the risk assessment project. The purpose of this
workflow was for the creator to have a reminder and a collection of all open risk
assessment projects in the My Inbox app.
Now, Health and Safety Management provides several dedicated apps, such as the My
Risk Assessment Projects app, for the purpose of collecting and reminding of relevant risk
assessment projects. Therefore, this workflow is no longer needed and was removed from
Health and Safety Management, together with all its trigger points.
Business Process related information
The business process as such is not affected by this change. To find all open and relevant
risk assessment projects, users now need to look into their My Risk Assessment Projects
app instead of looking into their My Inbox app.
Required and Recommended Action(s)
If you have switched off this workflow and do not use it at all, then no action is required.
Otherwise, inform your Health and Safety Management business users about this
functional change.
In case you have modified or extended the Risk Assessment Lifecycle workflow (that
means: You have extended or exchanged the workflow template WS00800029), be aware
of the fact that this workflow is no longer triggered.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you have already used that workflow
(and probably are still using it therefore). This is the case if table EHHSSD_PRL_ROOT
contains any entries.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 580
Other Terms
Environment, Health, and Safety; EHS; EHS Management; Health and
Safety Management
23.18S4TWL - Renovation of task management
Application Components:EHS-SUS-HS, EHS-SUS-IM, EHS-SUS-EM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2612110
S4TWL - Renovation of task
management
Symptom
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
This SAP Note is intended to provide a deeper insight into the renovation of the EHS task
management process. This information is particularly relevant for customers who have
enhanced EHS Task Management, for example, with custom coding or additional
workflows.
Note: Resulting functional changes are described in the referenced SAP Notes.
Environment, Health, and Safety contains a task management functionality which is used
by its components Health and Safety Management, Incident Management, and
Environment Management. EHS Task Management has been significantly reworked (new
data model, new coding) and moved to Fiori (new user interface). The following
processes have been affected by this change:
Incident Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 581
Standard incident actions
Standard investigation step actions
Plant maintenance notifications
Change requests in SAP Management of Change
Incident lifecycle workflow
Notify HR (absence) administrator workflow
HR absence maintained workflow
Report generation workflow (removed)
Report shipment workflow (removed)
Report approval workflow (removed)
Health and Safety Management
Standard risk assessment actions
Control actions
Plant maintenance notifications
Change requests in SAP Management of Change
Environment Management
Standard compliance scenario actions
Business Process Related Information
The business process as such is not affected by this change, as the task management
functionality is still available.
However, if you are upgrading or converting from 1709 (or lower) releases to 1809 (or
higher) releases and have customer-specific functionalities of workflow processes, these
functionalities will not work after the upgrade or conversion. Before the upgrade or
conversion, we advise you to initiate analysis of your customer-specific functionalities
and plan ways to adapt them to the new task management framework.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 582
A modification of the standard migration, including the incorporation of customer-
specific solutions, is possible by enhancing the migration reports. For example, you can
adapt the migration of task attachments, as described in SAP Note 2900458.
All active EHS processes running at the time of the system upgrade or conversion to
1809 (or higher) releases are canceled automatically. To recreate them after the upgrade
or conversion, you have to run the R_EHFND_WFF_RESTART_PROCESSES report
manually in each client, as described in SAP Note 2905234. In addition to recreating the
active EHS processes, the report also transfers comments and copies attachments into the
new release. Information about the state of the processes that are in progress after the
upgrade or conversion is included as comments in the new workflow. Note that the
R_EHFND_WFF_RESTART_PROCESSES report may require a substantial amount of
time to finish. The long processing time may result from a large volume of attachments.
Note: Upgrading from lower releases refers to an upgrade from SAP S/4HANA 1511 and
SAP S/4HANA 1610, while conversion refers to conversion from Component Extension
for SAP Environment, Health, and Safety Management.
For more information about the steps in the migration of old tasks and work items, see
the Required and Recommended Action(s) section.
For more information about effects on the apps used, see the Affected Apps section.
Required and Recommended Action(s)
Depending on the context of your upgrade, you can find more information about the task
migration actions that you need to perform within that context in the following SAP
Notes:
If you are upgrading or converting from 1709 (or lower) to 1809, perform the
activities described in SAP Note 2905234.
If you are upgrading or converting from 1809 to 1909 (or higher), perform the
activities described SAP Note 2903938. Make sure you have maintained the
relevant parameters as described in SAP Note 2927227.
If you are upgrading or converting from 1709 (or higher) to 1909 (or higher) directly,
perform the activities described in SAP Note 2905234, followed by the activities
described in SAP Note 2903938. Make sure to perform the activities in SAP Note
2917169 only after all activities described in SAP Notes 2905234 and 2903938
are performed.
If you are upgrading or converting from 1809 (or lower) to 2020 (or higher), you can
choose whether to do a manual migration or to use silent data migration. Make
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 583
sure that you have maintained the relevant parameters as described in SAP Note
2927227. For more information about silent data migration, see SAP Note
2975797.
Important Note: A prerequisite for the task migration is to have business users set up. If
you don’t have business users set up in the system before the system conversion, it is
recommended to choose the manual migration option and set up business users before
running the manual migration report.
Affected Apps
As part of task migration during the upgrade to SAP S/4HANA 1809 or higher, the task
functionality in the following apps will be affected:
Task Explorer
Manage Compliance Scenario
Manage Incidents
My Risk Assessment Projects
After task migration is completed, your tasks will be transferred to the new task
management framework. To continue with normal task processing, install the following
new Fiori apps:
Monitor Tasks (F2527)
Manage Compliance Requirement Tasks (F4346)
Manage Compliance Scenario Tasks (F2526)
Manage Incident Tasks (F3091)
Manage Risk Assessment Tasks (F3093)
Manage Control Implementation Tasks (F3094)
Manage Investigation Step Tasks (F3092)
Task Calendar (F3840)
Display Task Instance (F2529)
Manage Task Definition (F2528)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 584
Manage Maintenance Notification (F3359)
My Inbox (F0862)
How to Determine Relevancy
This Transition Worklist item is relevant for you if you are using EHS Task
Management. This is the case if at least one of the following tables contains any entries:
EHHSSD_IAC_ROOT
EHHSSD_PIC_ROOT
EHHSSD_RAC_ROOT
EHHSSD_PRA_ROOT
EHENVD_SAC_ROOT
EHENVD_PSA_ROOT
EHHSSD_PIL_ROOT
EHHSSD_PIH_ROOT
EHHSSD_PIR_ROOT
EHHSSD_PIA_ROOT
EHHSSD_PRL_ROOT
Other Terms
Environment, Health, and Safety; EHS; Health and Safety Management; Incident
Management; Environment Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 585
23.19S4TWL - Deprecation of Mapping Workbench in Foundation of EHS
Application Components:EHS-SUS-FND, EHS-MGM-FND-FRM, EHS-MGM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2408533
S4TWL - Deprecation of Mapping
Workbench in Foundation of EHS
Symptom
You are doing a system conversion or an upgrade from SAP S/4HANA on-premise
edition 1511 or SAP S/4HANA 1610 to SAP S/4HANA 1709.
The following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The Mapping Workbench in the Foundation for EHS enabled you to map business object
nodes to nodes that are used in SAP Interactive Forms by Adobe.
The Mapping Workbench is deprecated.
Business Process related information
Existing SAP Interactive Forms by Adobe which were developed with the help of the
Mapping Workbench continue to work at runtime.
However you will not be able to use the Mapping Workbench in future to develop new
forms or adapt existing forms which were originally developped with the Mapping
Workbench.
Required and Recommended Action(s)
Develop and adapt your SAP Interactive Forms by Adobe via the standard transactions
SFP and SE24.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 586
How to Determine Relevancy
This Simplification Item is relevant if you are using the Mapping Workbench to develop
own SAP Interactive Forms by Adobe for EHS. This is usually the case if table
EHFNDD_MAP_ROOT has entries.
Other Terms
Environment, Health and Safety
23.20S4TWL - Renovation of Investigation Lifecycle Workflow
Application Components:EHS-SUS-IM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2801072
S4TWL - Renovation of the workflow for
the EHS incident investigation lifecycle
Symptom
You are doing a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA. The following Transition Worklist item is applicable for customers who use
the workflow for the EHS incident investigation lifecycle.
Reason and Prerequisites
Renovation
Solution
Description
The workflow for the EHS incident investigation lifecycle has been redesigned and now
uses a new workflow architecture.
This SAP Note provides information on the required manual migration of incident
investigation lifecycle processes to the new architecture.
Business Process Related Information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 587
The end-to-end incident investigation business process as such has not been changed.
Migration to the updated workflow for the EHS incident investigation lifecycle is to be
performed manually.
Required and Recommended Actions
After a system conversion to SAP S/4HANA or a system upgrade within SAP
S/4HANA, be sure to manually run the report
R_EHHSS_INV_LC_MIGRATION.
For more details, see the report documentation.
Check if you have implemented any additional functionality (such as additional or
modified workflow steps) on top of the existing incident investigation lifecycle
workflow.
If this is the case, you may need to adjust your workflow.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you use the workflow for the EHS
incident investigation lifecycle. This is the case if the table
EHHSSD_IIL_ROOT contains any entries.
Other Terms
Environment, Health, and Safety, EHS, Incident Management, Investigation Lifecycle
Workflow, IM
23.21S4TWL - Barcode reader not supported in app Display Safety-Relevant
Information
Application Components:EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3253390
S4TWL - Barcode reader not supported
in app Display Safety-Relevant
Information
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 588
You are carrying out a system conversion or an upgrade to SAP S/4HANA 2020 or
higher.
The following SAP S/4HANA transition worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The Display Safety-Relevant Information app offers you a holistic view on a workplace
(technically: EHS location) from a safety perspective.
For the first step in this app, the selection of an EHS location, the app used to offer a
barcode / QR code reader function (see screenshot in the Attachments section). As this
feature was a basic, built-in Fiori feature which is no longer available in Fiori, the app
Display Safety-Relevant Information has also lost this feature.
Business Process-Related Information
The business process as such does not change, only the step for the selection of an EHS
location has changed.
Required and Recommended Action(s)
Check if you are using the SAP Fiori native app for Apple or Android devices.
Only this native app used to support barcode scanning; the normal Fiori app
started from the Fiori launchpad and running in a normal browser window
has never done so.
This native app was deprecated recently, but your company might still have it
in use.
If the mentioned app is not in use at your company, you are not affected and can stop
reading here.
If the mentioned app is in use, inform your end users that the button Scan barcode is
no longer available and that the desired location needs to be selected using the
normal filter criteria.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 589
This simplification item is potentially relevant if you have EHS Health and Safety
Management in use. This is usually the case if table EHHSSD_RSK_ROOT contains
entries.
Whether you actually use the affected native app Display Safety-Relevant Information
cannot be determined technically; you have to find out this by asking your IT department
or your EHS business.
Other Terms
Environment, Health and Safety; Health and Safety Management; Operational Risk
Management
23.22S4TWL - Replacement of Office integration in Risk Assessment Step
Application Components:EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3036325
S4TWL - Refactoring Office Integration
in EHS Risk Assessment (1)
Symptom
You are carrying out a system conversion or an upgrade to SAP S/4HANA 2021.
The following SAP S/4HANA transition worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The Manage Risk Assessments app enables you to configure additional assessment steps.
One possible such step is the use of a predefined document created in Microsoft Word or
Microsoft Excel to perform a risk assessment. This document could be, for example, a
predefined checklist to fill in.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 590
Such a document used to be displayed and edited in place within the browser. As
the Microsoft Office integration into browsers is no longer supported, this feature has
been reworked to use the download and upload of the relevant document.
Business Process-Related Information
Microsoft Office documents can no longer be displayed and edited in place within the
Manage Risk Assessments app. This feature has been reworked in the following way:
The user selects one of the available template documents.
With this renovation, the system now offers multiple templates.
However, it is only possible to upload one result document.
The user downloads the chosen document to the frontend.
The user edits the document using the appropriate Microsoft Office applicaiton.
The user uploads the edited document as the result.
The business process as such has not changed, only the way in which such a document is
handled.
Required and Recommended Action(s)
Check if you have defined assessment steps using Microsoft Office documents as the
analysis method.
Open the Customizing activity Environment, Health and Safety -> Health and
Safety Management -> Risk Analysis -> Specify Assessment Steps and
Analysis Methods.
Check if the analysis method Office Integration
(Word) (EHHSS_ANM_OFFICE_DOC) or Office Integration
(Excel) (EHHSS_ANM_OFFICE_DOC2) has been assigned somewhere.
If so, inform your business users about the new approach described above.
The changed handling on the UI should be self-explanatory enough that no
extensive training is necessary.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 591
This simplification item is relevant if you have assessment steps defined that use use
Microsoft Office integration as the analysis method. This is the case if table
EHHSSC_ANMASSIGN contains entries where the field TAB_ID = "OFFICE_DOC".
Other Terms
Environment, Health and Safety; Health and Safety Management; Operational Risk
Assessment
23.23S4TWL - Replacement of Excel integration in Exposure Assessment
Application Components:EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3039679
S4TWL - Refactoring Office integration
in EHS Risk Assessment (2)
Symptom
You carrying out a system conversion or an upgrade to SAP S/4HANA 2021.
The following SAP S/4HANA transition worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The Manage Risk Assessments app enables you to configure the process step Exposure
Assessment (Quantitative) / Quantitative Exposure Assessment. Within this step it was
possible to interface to a Microsoft Excel document for the calculation of the exposure
assessment result synchronously and inside the browser.
As the integration of Microsoft Office into browsers is no longer supported, this feature
has been reworked using explicit downloading and uploading.
Business Process-Related Information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 592
Microsoft Office documents can no longer be displayed and edited in place within the
Manage Risk Assessments app. This feature has been reworked the following way:
The user downloads the Microsoft Excel document to the frontend.
All relevant measurement and sampling data is downloaded with the file.
The user edits the document using Microsoft Excel.
The user uploads the edited document.
The exposure assessment calculated within that document is read from the
file and written back to the SAP system.
The business process as such does not change, only the in which such a document is
handled.
Required and Recommended Action(s)
Check if you have the assessment step Quantitative Exposure Assessment in use.
Open the Customizing activity Environment, Health and Safety -> Health and
Safety Management -> Risk Analysis -> Specify Assessment Steps and
Analysis Methods.
Check if Analysis Method Quantitative Exposure
Assessment (EXP_ASSMNT_QUANT) has been assigned somewhere.
If yes, inform your business users about the new approach described above.
The changed handling in the UI should be self-explanatory enough that no
extensive training is necessary.
How to Determine Relevancy
This simplification item is relevant if you have Quantitative Exposure Assessment
defined as the analysis method. This is the case if table EHHSSC_ANMASSIGN
contains entries where the field TAB_ID = "EXP_ASSMNT_QUANT".
Other Terms
Environment, Health and Safety; Health and Safety Management; Operational Risk
Assessment
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 593
23.24S4TWL - Occupational Health
Application Components:EHS-HEA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267782
S4TWL - Occupational Health
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP EHS Management as part of SAP ERP, customers can use the Occupational
Health (EHS-HEA) function to support general employee occupational healthcare in their
company.
In SAP S/4HANA this solution is no longer available.
For SAP S/4HANA 1709 and higher the add-on solution SAP EHS Management for SAP
S/4HANA, occupational health is available to re-establish this Occupational Health
function.
Business Process related information
Occupational Health (EHS-HEA) is not available in SAP S/4HANA.
Transa
ctions
not
availabl
e in
SAP
S/4HA
NA on-
premise
EHSAMBTAET,EHSASSIGN,EHSASSLTA,EHSASSPERS,
EHSBC02,EHSBP11,EHSBP12,EHSBP13,EHSBP31,EHSBP32,EHSBP33,EHSBP41,E
HSBP42,EHSBP43,EHSBP51,EHSBP52,EHSBP53,
EHSCALPROX,EHSCBER,EHSCDCT, EHSCMAS,EHSDATIMP,EHSDIAGSL,EHSEVA
L00,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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 594
EHSMQUEST,EHSMQUEST01,EHSPERSHC1,EHSPP01,EHSPRANZ,EHSPRLOE,EH
SQCATOH,EHSQEVAL01,EHSQUESTOH,
EHSSCAN,EHSSERV,EHSSERV01,EHSSERV11,EHSSERV30,EHSSER50,EHSSTR
U00,EHSSUGGP,EHSTERM01,
EHSVA02,EHSVU01,EHSVU01_SELSCREEN,EHSVU11,EHSVU21,EHSVU31
For S/4HANA 1709, the Repeatable Customer Solution "SAP EHS Management for SAP
S/4HANA, occupational health" is available as a replacement. This add-on is technically
and from a functional point of view equivalent to the deprecated Occupational Health
(EHS-HEA) function.
Required and Recommended Action(s)
If you want to remove the Occupational Health (EHS-HEA) function from your
system, ...
... this is done automatically by the S/4HANA system conversion (for target
release S/4HANA 1610 and below)
... just confirm the pre-check error during the conversion check (for target
release S/4HANA 1709 and higher)
If you want to continue using your existing Occupational Health functionality in
S/4HANA, make sure not to convert to SAP S/4HANA 1511 or 1610.
These conversions would delete all EHS-HEA objects including all existing
EHS-HEA data.
Instead, include the previously mentioned add-on using the SAP Maintenance
Planner into your conversion to SAP S/4HANA 1709 or higher.
If you don't do so and install the add-on after the conversion, your
existing data for Occupational Health will get lost!
If you proceed as described, all your Occupational Health data, transactions and
processes will stay untouched. For further details see the referenced notes.
Other Terms
Occupational Health, EHS-HEA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 595
23.25S4TWL - Deprecation of Incident Management Apps
Application Components:EHS-SUS-IM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3127469
S4TWL - Deprecation of Incident
Management Apps
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Apps in the SAP S/4HANA solution for EHS incident management are deprecated as of
SAP S/4HANA 2021.
The corresponding functionalities are covered by new or enhanced SAP Fiori apps.
Business Process-Related Information
The following apps have been deprecated:
Web Dynpro App/App ID
Description
Successor App
EHHSS_INC_REC_QAF
Report Incident - Basic
Recording
Report Incident (F1992)
EHHSS_INC_REC_GAF_V3
Report Incident - Detailed
Recording
Report Incident (F1992)
EHHSS_INC_REC_SFO_QAF_V3
Report Safety
Observation
Report Incident (F1992)
EHHSS_INC_REC_NRM_QAF_V3
Report Near Miss
Report Incident (F1992)
EHHSS_INC_ENTRY
Manage Incidents
Manage Incidents (F4759)
F3781
Manage Summary
Reports
Manage Summary Reports
(F4758)
Required and Recommended Actions
The app tiles are no longer available by default on the SAP Fiori launchpad. You can still
access the apps via the app finder and continue using them until they become obsolete in
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 596
one of the next releases. Therefore, we recommend that you switch to the successor app
as soon as possible.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you are using one or more of the
deprecated apps that are listed above.
23.26S4TWL - Deprecation of Manage Compliance Requirement app
Application Components:EHS-SUS-EM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3139973
S4TWL - Deprecation of Manage
Compliance Requirement app
Symptom
You are doing an upgrade from a lower to a higher SAP S/4HANA release and are using
the functionality described in this SAP Note. The following
SAP S/4HANA Simplification Item is applicable in this case.
Reason and Prerequisites
Upgrade
Solution
Description
With SAP S/4HANA 2022, the WebDynpro app Manage Compliance Requirement has
been deprecated and is no longer available on the SAP Fiori launchpad. The
corresponding functionalities are covered by a new SAP Fiori app.
Business Value
The successor app comes with a state-of-the-art SAP Fiori user interface and provides an
improved user experience.
Business Process Related Information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 597
You can find more information about the deprecated app and its successor app below.
Web Dynpro App/App
ID
Deprecated App
Successor App
EHENV_REQ_ENTRY_OIF
Manage Compliance
Requirement
Manage Compliance Requirements -
Regulations, Permits, Policies
(F5038)
Required and Recommended Action(s)
Make sure that you switch to the successor app as soon as possible. This need to
happen latest before the next release upgrade of your SAP S/4HANA system.
If you use any custom setup or exstensions, note that they cannot be migrated
automatically to the SAP Fiori app. You need to recreate them with the support of
your service team.
Other Terms
SAP S/4HANA, Upgrade, WebDynpro
23.27S4TWL - Enablement for continuous delivery of listed substance content
Application Components:EHS-SUS, EHS-SUS-CI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3344198
S4TWL - Enablement for continuous
delivery of listed substance content
Symptom
You are doing an upgrade to SAP S/4HANA 2023 or higher and you are using one of the
following products:
SAP S/4HANA for Product Compliance
SAP EHS Management: Product and REACH Compliance
SAP Environment, Health, and Safety Management: Health and Safety
SAP Environment, Health, and Safety Management: Environment Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 598
The following SAP S/4HANA Simplification Item is applicable in this case: SI29:
Logistics_EHS - Listed Substance Content.
Reason and Prerequisites
Renovation
Solution
Description
Content for listed substances will no longer be shipped in client independent tables. The
latter will be gradually sunset and replaced by client dependent tables which will be filled
with content delivered by the SAP Regulatory Content Service.
This note will be regularly updated to inform about the sunset tables.
Required and Recommended Action(s)
Find out whether you have customer specific implementations in place which access
the following tables:
EHFNDI_LSCOND
EHFNDI_LSCOND_T
Replace access to the above tables with access to table EHFNDD_LSCOND.
Configure the SAP Regulatory Content Service for Environment, Health, and Safety
Management and Product Compliance as described in SAP Note 3055767
Plan background job SAP_EHFND_PC_CONTENT_LOAD as described in the
corresponding customizing activities:
SAP S/4HANA for Product Compliance: Schedule Job: Product Compliance -
> Foundation for Product Compliance -> Product Compliance Background
Processing -> Schedule Jobs for Product Compliance Background
Processing
SAP EHS Management: Product and REACH Compliance: Product Safety
and Stewardship -> Product Compliance for Discrete Industries ->
Integration -> Specify Jobs for Listed Substance Content Integration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 599
SAP Environment, Health, and Safety Management: Environment, Health and
Safety -> Foundation for EHS -> Integration -> Listed Substance Content
Integration -> Specify Jobs for Listed Substance Content Integration
Other Terms
SAP S/4HANA; Upgrade; Environment, Health, and Safety; Product Compliance;
Regulatory Content Infrastructure for Sustainability; EHFNDI_LSCOND;
EHFNDI_LSCOND_T; EHFNDD_LSCOND; SAP_EHFND_PC_CONTENT_LOAD;
SI29.
23.28S4TWL - Waste Management
Application Components:EHS-WA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267783
S4TWL - Waste Management
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Trans
action
not
availa
ble in
SAP
WAA01,WAA02,WAA03,WAA04,WAA10,WAA11,WAA12,WAA13,WAA19,WAA20,WAA2
1,WAA22,WAA23,WAA24,WAA25,WAA26, WAAP,
WACB01,WACM01,WACM02,WACM03,WACM04,WACM10,WACM30,WACO02,WACO
02OLD,WACO03OLD,WACO04OLD,
WACS1,WACS2,WACS3,WACS4,WACS6,WADC,WADI,WAE01,WAE02,WAE03,WAE1
0,WAEA,WAGE, WAM01,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 600
S/4HA
NA
on-
premis
e
edition
1511
WAM02,WAM03,WAM04,WAM05,WAMC,WAMI,WAMR,WANP,WAREP001,
WASM100,
WASM101,WASM102,WASM109,WASS100,WASS101,WASS102,WASS103,WASS104,
WASS105,WASS106,WASS107,WASS108,WASS110,
WASS111,WASS112,WASS113,WASS114,WASS115,WASS116,WASS117,WASS118,
WASS119,WASS120,WASS121,WASS122,WASS123,WASS124,
WATR,WATREE
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2217202
23.29S4TWL - Simplification in Incident Management and Risk Assessment
Application Components:EHS-MGM-INC, EHS-MGM-RAS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267784
S4TWL - Simplification in Incident
Management and Risk Assessment
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 601
The following incident management functions are not available in SAP S/4HANA:
BI extraction and queries for incident reporting
- Datasource 0EH_INCIDNT_ATTR, Function Module
EHHSSEX_A_0EH_INCIDNT
- Datasource 0EHSM_HSS_INC_REC_01, Function Module
EHHSSEX_D_INCIDENTS
- Datasource 0EHSM_HSS_INC_REC_02, Function Module
EHHSSEX_D_INJURIES
- Datasource 0EHSM_HSS_INC_REC_03, Function Module
EHHSSEX_D_ASSETS
- Datasource 0EHSM_HSS_INC_REC_04, Function Module
EHHSSEX_D_FINANCIAL
- Datasource 0EHSM_HSS_INC_REC_05, Function Module
EHHSSEX_D_RELEASES
- Datasource 0EHSM_HSS_INC_REC_06, Function Module
EHHSSEX_D_ACTIONS
- Datasource 0EHSM_HSS_INC_REC_07, Function Module
EHHSSEX_D_INVESTIGATIONS
- Datasource 0EHSM_HSS_INC_REC_08, Function Module
EHHSSEX_D_RISK_ASSESSMENTS
- Datasource 0EHSM_HSS_INC_REC_09, Function Module
EHHSSEX_D_VIOLATIONS
- All Incident Text Datasources like 0EH_INJCODE_TEXT,
0EH_INCGRP_TEXT
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 602
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
IH work area integration with locations
Application "Identification of risks effected by OEL changes"
Technically: Web Dynpro application EHHSS_UI_AGT_OEL_CHNG_QAF
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 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 603
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
Custom Code related information
SAP Note: 2217208
Additional related SAP Notes
SAP Note: 2065178
23.30S4TWL - Removal of EHS workflows for requesting controls, impacts,
agents
Application Components:EHS-MGM-RAS, EHS-SUS-HS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2330017
S4TWL - Removal of Health and Safety
workflows for requesting controls,
impacts, agents, hazards
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 604
The following functions no longer exist in Health and Safety Management (formerly
known as Risk Assessment)
Requesting controls ...
... while editing controls in a Risk Assessment
... while indentifying risks using the guided activity for Risk Identification
Requesting impacts ...
... while editing impacts in the Edit Impact popup window
... while indentifying risks using the guided activity for Risk Identification
Requesting agents ...
... while indentifying risks using the guided activity for Risk Identification
Requesting hazards ...
... while indentifying 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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 605
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.
Other Terms
Environment, Health and Safety, EHS Risk Assessment
23.31S4TWL - Responsible person for Planned Maintenance at EHS locations
Application Components:EHS-MGM, EHS-SUS-EM, EHS-SUS-FND, EHS-SUS-HS, EHS-SUS-IM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2329611
S4TWL - Responsible person for
Planned Maintenance at EHS locations
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 606
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 equipments or functional locations).
Business Process related information
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.
Other Terms
Plant Maintenance, PM, Enterprise Asset Management, EAM
23.32S4TWL - Remote Integration Scenarios with EHS Health and Safety
Management
Application Components:EHS-SUS-FND, EHS-MGM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2329574
S4TWL: Remote integration scenarios
of EHS
Symptom
You execute a system conversion in SAP S/4HANA, On-Premise edition. The following
SAP S/4HANA transfer worklist entry is relevant in this case.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 607
Renewal
Solution
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 external Work Clearance Management (WCM) system
Integration of EHS with an external Material Management / Inventory
Management (MM/IM) system
Integration of EHS with an external substance or specification database
Integration of EHS with an external Financials (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.
Other Terms
EHS Risk Assessment, EHFND_INT_DEST_TYPE, DEST_PM, DEST_HR,
DEST_BUPA, DEST_ACC, DEST_EHS, DEST_MMIM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 608
23.33S4TWL - Conversion relevant changes in EHS
Application Components:EHS-MGM, EHS-SUS-IM, EHS-SUS-HS, EHS-SUS-FND
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2336396
S4TWL - Conversion-relevant changes
in EHS
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
You want to convert component extension for SAP EHS Management or EHS
Management as part of SAP ERP to SAP S/4HANA 1610 or higher.
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 for
S/4HANA on the SAP Help Portal at http://help.sap.com/s4hana. Select your target
release and go to the Product Documentation section.
Reason and Prerequisites
Renovation
Solution
Description
See attachment
Business Process related information
See attachment
Required and Recommended Action(s)
See attachment
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 609
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.
Other Terms
Environment, Health, and Safety as part of SAP S/4HANA; conversion to SAP
S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 610
24.Logistics – GT
24.1 S4TWL - Global Trade Management
Application Components:LO-GT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267785
S4TWL - Global Trade Management
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Simplification of DB Key Fields and tables structures (WBHF, WBGT, WBIT,
WBASSOC, WCOCOF, WB2_D_BUSVOLBASE, WB2_D_BVB_SETTL)
Replacement of concatenated fields by corresponding new fields in mentioned DB
tables (Future details can be found in the mentioned notes below)
Change of Domain definition from CHAR to NUMC for item number related fields
Replaced fields are moved to the dynamical part of the communication structures to
avoid runtime errors and to ensure the same system behaviour as before
Business Process related information
Dictionary changes will have no influence on the business processes as such. Custom
related code has to be adjusted to adopt the new data model. If one of the obsolete
transactions or reports is used within the business process the new transactions and
reports have to be used instead. Differential Invoicing is not part of SAP S/4HANA
anymore because these transactions are replaced already in SAP ERP EHP7 by the
Differential Invoicing Functionality of Commodity Management.
Transaction Codes and Reports not available in SAP S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 611
See also note 2204137
Obsolete Report
Obsolete Report
Title
Obsolete
TCode
Successor
Report
Successo
r Report
Title
Successo
r TCode
RWB2B001
Trading Contract:
General
Document
Overview
WB24
RWB2BRE
L
Trading
Contract:
Follow on
document
prosessin
g
WBRR
RWB2B001
Trading Contract:
General
Document
Overview
WB25_COMP
RWB2BMA
S
Mass
Processin
g
(Release
and
Status
update)
WB24N
WB2B_CREATE_TC_US
ER
Create User For
TC At Web
WB2B_NETUSE
R
RWB2DI001
Generate
Differential
Invoices
WB2DI1
RWB2DI002
Over of Billing
Documents releva
nt for Creating
Differential Invs
WB2DI2
RWB2DI003
Process Billing
Documents
regarding
Differential
Invoices
WB2DI3
RWB2DI004
Process Billing
Documents
regarding
Differential Invoice
s
WB2DI4
RWB2B006
Trading Contract:
Financial
Documents
WB31
Obsolete TCode
Successor TCode
POFO1
POFO31
POFO2
POFO32
POFO3
POFO33
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 612
For Target release SAP S/4HANA 1511 and SAP S/4HANA 1610:
Pre-Check is performed for the component LO-GT. Custom code adoption on the new
DB-Design can be checked in the start release to identify the code places which have to
adjust to the new DB-Structures. Batch or online processes which needed the obsolete
transactions or reports have to be adjusted so that the new transactions and reports are
used instead.
Related SAP Notes
Custom Code related information
SAP Notes: 2198031, 2204137, 2198035
If you use Trading Contracts, please check note 2198031 for additonal information.
If you use Condition Contracts, please check note 2204137 for additonal information.
24.2 S4TWL - Invoice Forecasting Worklist not available in SAP S/4HANA
Application Components:LO-AB-IFW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2739164
S4TWL - Invoice Forecasting Worklist
not available in SAP S/4HANA
Symptom
You are doing a system conversion to SAP S/4HANA and using IFW in your original
system, you will find switch ISR_GLT_IFW as always deactivated in SAP S/4HANA
systems.Thus, you cannot use invoice forecasting in SAP S/4HANA systems.
Reason and Prerequisites
Functionality not available.
Solution
Description
Switch ISR_GLT_IFW is deactivated in SAP S/4HANA systems and thus invoice
forecasting cannot be used in SAP S4/HANA systems.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 613
Business Process related information
Implemented business processes need to be adjusted since the functionality is no more
available. IFW data will no more remain relevant in SAP S/4HANA systems.
Required and Recommended Action
IFW related data will no more remain relevant.
How to Determine Relevancy
This simplification item is relevant if Invoice forcasting worklist functionality is in use
which means table IFW_WORKLIST has data.
Other Terms
IFW, SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 614
25.Logistics - Management of Change
25.1 S4TWL - Simplifications in Management of Change
Application Components:CA-IAM-MOC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2616203
S4TWL - Simplifications in Management
of Change
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
Description
The following features of Management of Change (MOC) are not available in SAP
S/4HANA:
Enterprise service to create change requests
Web Dynpro application "Change Request - Quick Entry"
MOC Home Page
"Ask an Expert" function for change requests
Determination of people based on business partner hierarchy (see SAP
Note 2409939)
Integration of related objects from remote systems
Operational data provisioning to analyze change requests and activities
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 615
The following features of MOC have been changed in SAP S/4HANA:
The worklist (POWL) for change requests and activities has been replaced by SAP
Fiori apps.
The business partner integration has been adjusted to the SAP S/4HANA business
user concept (see SAP Note 2570961). Business User Management supports only
business partners of category Person (BUT000-TYPE = 1).
The way of adding activities to change requests or activities has been simplified. Only
adding activities from templates is supported.
The following related object types are supported for MOC on the local SAP S/4HANA
system:
Batch (BAT)
Change Master (ECN)
Customer (CUS)
Document (DOC)
Equipment (EQ)
Functional Location (FL)
Internal Order (IO)
Material (MAT)
Outbound Delivery (DLV)
Outbound Delivery Item (DLI)
Plant (PLA)
Plant Maintenance Notification (PMN)
Plant Maintenance Order (PMO)
Purchase Order (PO)
Purchase Order Item (POI)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 616
Risk Assessment Request in EHS (RAR)
Vendor (VEN)
Business Process Related Information
To create change requests, you can use the "Change Request" Web Dynpro application
instead of the enterprise service and the Web Dynpro application "Change Request -
Quick Entry". It can be accessed in creation mode with parameters to predefine certain
attributes like change request type or leading object.
To access change requests and activities, you can use the new Fiori apps "Manage
Change Requests" and "Manage Change Activities" instead of the "MOC Home Page".
The "Ask an Expert" function has not been replaced by an equivalent.
The process for determination of people has not changed, although adjustments in
configuration may be required.
Related objects have to be available on the local SAP S/4HANA system. To be
compatible with existing and planned features in MOC on SAP S/4HANA, you must not
add the following:
Related objects from remote systems.
Other related object types than the listed above.
The operational data provisioning has not been replaced by an equivalent.
The worklist (POWL) to manage change requests and activities has been replaced by the
following SAP Fiori apps:
Manage Change Requests
Manage Change Activities
The way of handling business users in change requests and activities is the same as it was
for business partners. Adjustments in configuration may be required.
The previous versions of MOC have offered two options to add activities: "Add
Manually" and "Add from Template". In SAP S/4HANA, you can add activities only
from templates.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 617
Required and Recommended Actions
If the enterprise service or the Web Dynpro application "Change Request - Quick Entry"
has been used, use the Web Dynpro application “Change Request” instead.
Check in Customizing under Cross-Application Components > Management of Change
> Define Change Request Type which reference objects (related objects) you are using in
MOC. Check in Customizing under Cross-Application Components > Management of
Change > Settings for Reference Objects if a remote access has been configured for these
reference objects. Ensure that you only use reference objects without remote access in
MOC.
Ensure the correct and complete setup of the business user management. For more
information, see SAP Note 2570961.
Check setup for people determination:
In Customizing under Management of Change > Define Partner Role ensure that
none of the active entries contains Business Partner Hierarchy as Position Origin.
In Basic Determination of People (transactions /MOC/CRBP and /MOC/ACTBP) and
Additional Determination of People using BRFplus ensure that active entries:
Only contain business users as Business Partner.
Do not contain Positions from the Business Partner Hierarchy.
If users of MOC have used "Add Manually" to add activities of certain activity types,
define equivalent activity templates for these activity types.
How to Determine Relevancy
This simplification item is relevant if you have MOC in use. This is usually the case if
table /IAM/D_I_ROOT has 20 or more entries for APPLICATION 'MOC'.
Other Terms
Management of Change, MOC, Change Request
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 618
26.Logistics - MM-IM
26.1 S4TWL - FMP in S4HANA
Application Components:IS-CWM, MM-IM-GF-CWM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2414624
S4TWL - Flexible Material Prices (FMP)
in SAP S/4HANA
Symptom
If you have activated the Business Function /CWM/FMP of the Industry Solution IS-
CWM, the following SAP S/4HANA transition worklist item is applicable.
Flexible Material Prices (FMP) is not supported in SAP S/4HANA even
though objects are technically given in QRT_STAG.
Reason and Prerequisites
Module FMP was introduced with EHP5 of the Industry Solution IS-CWM to support the
customer created price types within the migration to the 'new architecture' of CWM (for
more details please see also note 2358928).
In Inventory Accounting as part of the 'old Architecture' all prices were organized in
price types. With the migration all existing and important prices were transferred into the
standard tables of ERP. But in case a customer had created own price types the
related prices had to be stored in FMP since there was no separate data storage in ERP
available.
In seldom cases customer used this opportunity and defined own price types. So SAP
decided to not support the FMP-module anymore in S/4HANA.
Solution
To check the usage of own price types in FMP call transaction SE16, select table
'/FMP/D_MP_PRIC' and execute. Press the button 'Number of Entries' and in case the
appearing popup shows no entries found you are sure that no own prices were maintained
in FMP.
Please be aware that for S/4HANA:
FMP-data cannot be migrated
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 619
a call of FMP transactions and reports will cause a dump (Blacklisted objects)
objects starting with '/FMP/' must not be used in customer coding
(see note 2296016)
Other Terms
FMP, CWM, IS-CWM, S/4HANA, Simplification List, Flexible Material Prices
26.2 S4TWL - Blocked customer or supplier in Inventory Management
Application Components:MM-IM-PI, MM-IM-GF, BNS-INT-ARI-IM, MM-IM-RS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2516223
S4TWL - Blocked customer or supplier
in Inventory Management
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The end of purpose check for customer and supplier master data has changed in Inventory
Management. From SAP S/4HANA 1709 onwards the following requirements must be
fulfilled for blocking customer or supplier master data:
Material documents that are related to the customer or supplier to be blocked must be
archived.
Special stocks that are related to the customer or supplier to be blocked must
be archived or deleted.
Physical inventory documents that are related to the customer or supplier to be
blocked must be archived.
Open reservations that are related to the customer or supplier to be blocked must be
deleted.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 620
The customer or supplier to be blocked must be removed from plant and storage
location data.
The condition tables used to control the sending of receipt request messages to the
Ariba Network must not contain records related to the supplier to be blocked.
Batch input test data that is related to the supplier to be blocked must be deleted (or
changed).
Short documents (as substitutes for archived material documents) that are related to
the supplier to be blocked must be deleted.
Correction data (contained in database table MMINKON_UP) that is related to the
customer or supplier to be blocked must be deleted.
Consistency check results of aged material documents that are related to the customer
or supplier to be blocked must be deleted.
In case of an upgrade from 1511/1610/1709 to 1709-FPS01 or higher, please read
note 2629400
Required and Recommended Action(s)
Material documents, special stocks, physical inventory documents and open
reservations that are related to blocked customer or supplier master data shall be archived
or deleted before converting or upgrading to SAP S/4HANA 1709 (and above).
Open reservations can be deleted (or flagged for deletion) using transactions MB22 and
MBVR. Material documents, special stocks and physical inventory documents can be
archived using archiving objects MM_MATBEL, MM_SPSTOCK and MM_INVBEL.
Special stocks can be deleted using data destruction objects MM_STO_CONSI_DEST
and MM_STO_SOBES_DEST.
Furthermore, blocked customers and suppliers shall be removed from plant and storage
location data:
The assignment of a blocked customer to a plant can be removed via SAP Reference
IMG / SAP Customizing Implementation Guide (transaction SPRO): Materials
Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order ->
Define Shipping Data for Plants.
The assignment of a blocked supplier to a plant can be removed via transaction XK02
-> Purchasing data -> Extras -> Additional Purchasing Data.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 621
The assignment of a blocked customer or supplier to a storage location can be
removed via SAP Reference IMG / SAP Customizing Implementation Guide
(transaction SPRO): Materials Management -> Purchasing -> Purchase Order ->
Set up Stock Transport Order -> Set Up Stock Transfer Between Storage
Locations -> Define Shipping Data for Stock Transfers Between Storage
Locations.
Condition tables can be changed using transaction NACE:
Select application ME (Inventory Management) and enter “Condition records (F8)”
Select Output Type ARIB (Ariba Rcpt Request)
Select key combination ("Supplier/CoCode" or "Supplier")
In the selection screen for the condition records enter the supplier for that you want to
create or display conditions and press execute (F8).
Enter the conditions (supplier, respectively company code; the other attributes can be
ignored).
Save the changes.
Moreover, batch input test data, short documents, correction data and consistency check
results shall be deleted:
Batch input test data can be deleted (or changed) using maintenance view V_159A.
Short documents (as substitutes for archived material documents) can be deleted
using report RM07MAID.
Correction data (contained in database table MMINKON_UP) can only be deleted
manually.
Consistency check results of aged material documents can be deleted using report
NSDM_MATDOC_CHECK_AGED_DATA.
How to Determine Relevancy
With notes 2502552, 2524011, 2536568 and 2585925 SAP offers a Simplification Item
Check to identify blocked customers and suppliers in Inventory
Management. Alternatively, the following steps can be performed:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 622
Identify blocked customer master data in database table KNB1. The customer is
blocked when the field CVP_XBLCK_B is set. Plants assigned to the company
code of the customer master record can be identified via transaction OX18.
Identify blocked supplier master data in database table LFB1. The supplier is blocked
when the field CVP_XBLCK_B is set. Plants assigned to the company code of the
supplier master record can be identified via transaction OX18.
Identify material documents, special stocks, physical inventory documents, open
reservations, plants and storage locations that are related to blocked customer or
supplier master data in the following database tables: ISEG, MKOL, MSEG,
MSKU, MSLB, MSSL, RESB, RKPF, T001W and T001L. For Discrete
Industries and Mill Products (DIMP) the following database tables are relevant in
addition: MCSD, MCSS, MSCD, MSCS, MSFD, MSFS, MSID, MSIS, MSRD
and MSRS. Filter these database tables by the plant (field WERKS) and by the
customer or supplier. The customer can be contained in the field KUNNR or
VPTNR. The supplier can be contained in the field DISUB_OWNER, EMLIF,
LIFNR, LLIEF or OWNER.
Identify condition records used to control the sending of receipt request messages to
the Ariba Network that are related to blocked supplier master data in the database
tables B082 ("Supplier/CoCode") and B083 ("Supplier"). In both tables the
supplier can be contained in the field ARRLIFNR.
Identify batch input test data that is related to blocked supplier master data by
filtering the database table T159A by the plant (field WERKS) and by the
supplier (field LIFNR).
Identify short documents that are related to blocked supplier master data by filtering
the database table MARI by the plant (field WERKS) and by the supplier (field
LIFNR).
Identify correction data that is related to blocked customer or supplier master data by
filtering the database table MMINKON_UP by the plant (field WERKS) and by
the customer or supplier. The customer can be contained in the field KUNNR.
The supplier can be contained in the field LIFNR or OWNER.
Identify consistency check results that are related to blocked customer or supplier
master data by filtering the database table NSDM_AGING_CHECK by the plant
(field WERKS) and by the customer or supplier. The customer can be contained
in the field KUNNR_SID. The supplier can be contained in the field LIFNR_SID
or DISUB_OWNER_SID.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 623
26.3 S4TWL - Document Flow Consistency for Goods Receipt to Inbound
Delivery
Application Components:LE-SHP-DL-LA, IS-A-GR, MM-IM-GR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2542099
S4TWL - Document Flow Consistency
for Goods Receipt to Inbound Delivery
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP to SAP S/4HANA.
Prerequisite: Business Function Set DIMP for Discrete Industries and Mill Products or
Business Function Set DIMP_PS for Discrete Industries / Mill Products and Public
Services not active in SAP ERP
Solution
Description
When using transaction MIGO to post goods receipt with reference to an inbound
delivery, to cancel a goods receipt with reference to an inbound delivery or post a return
delivery by referring to a material document posted with reference to an inbound
delivery, the inbound delivery is not updated unless the indicator "Document flow update
for stock postings and return delivery" is set in the Global Shipping Data.
This indicator in SAP ERP was so far optional and not set by default except for
installations where the industry solutions for Discrete Industries and Mill Products have
been activated. The implication of having that indicator not set are inconsistent and never
completed inbound delivery documents which could not be archived.
In S/4HANA, the update of the inbound delivery is enforced to ensure the data
consistency across different applications.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 624
When using transaction MIGO to post goods receipt with reference to an inbound
delivery, to cancel a goods receipt with reference to an inbound delivery or post a return
delivery by referring to a material document posted with reference to an inbound
delivery, the new material document will be added as successor document to the inbound
delivery and by that, the goods movement status will be updated accordingly to ensure
the data consistency.
Certain additional system checks are performed by the inbound delivery to ensure data
consistency, restricting the goods receipt process using transaction MIGO:
Goods movement quantity
In case a delivery item is not putaway-relevant, the goods receipt quantity must not be
larger than the delivery quantity minus the current cumulated goods receipt quantity,
otherwise message VLA 308 is raised.
In case a delivery item is putaway-relevant, the goods receipt quantity must not be larger
than the putaway quantity minus the current cumulated goods receipt quantity, otherwise
message VLA 308 is raised.
The return quantity must not be larger than the current cumulated goods receipt quantity,
otherwise message VLA 319 is raised.
The adaptation of delivery quantity or putaway quantity needs to be done via delivery
maintenance by using transactions VL32N or VL60.
Storage location
In case the storage location used for posting the material document differs from the
storage location in the respective delivery item, message VLA 316 is raised.
Before posting goods movement, the respective storage location of the delivery item
needs to be specified or changed via delivery maintenance by using transaction VL32N
or VL60.
Alternatively, specify the storage location in the purchasing document item to be copied
to the inbound delivery item or use s referring to or configure the storage location
determination to automatically fill the storage location for each of the inbound delivery
items.
Batch number
In case the batch number used for posting the material document differs from the batch
number in the respective delivery item, message VLA 317 is raised.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 625
Before posting goods movement, the respective batch number of the delivery item needs
to be specified or changed via delivery maintenance by using transaction VL32N.
Alternatively, use the automatic batch determination for deliveries to avoid a manual
entry of batch numbers for goods receipt posting.
Serial number
In case the serial numbers used for posting the material document differ from the serial
numbers to the respective delivery item, message VLA 315 is raised.
Before posting goods movement, the respective serial numbers to the delivery item need
to be specified or changed via delivery maintenance by using transaction VL32N.
Valuation type
In case the valuation type used for posting the material document differs from the
valuation type of the respective delivery item, message VLA 318 is raised.
Warehouse Management
In case the inbound delivery item is relevant for putaway in warehouse management,
message VLA 314 is raised.
The inbound delivery needs to be posted via delivery processing by using transactions
VL32N, VL06I or VL60.
Distribution to decentral systems
In case the inbound delivery has been distributed or has to be distributed to a decentral
system (e.g. a warehouse management system like SAP EWM), due to an EWM relevant
storage location, message VLA 302 is raised.
The inbound delivery has to be processed by the decentral system.
Packing / Handling units
In case items of the inbound delivery are packed or relevant for packing, message VLA
311 is raised.
The inbound delivery needs to be posted via delivery processing by using transactions
VL32N, VL06I or VL60.
Items without purchase order reference
In case of items without purchase order reference, message VLA 322 is raised.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 626
The inbound delivery needs to be posted via delivery processing by using transactions
VL32N, VL06I or VL60.
Incompleteness
In case the inbound delivery is incomplete, message VLA 303 is raised. In case the
inbound delivery item is incomplete, message VLA 313 is raised.
The inbound delivery needs to be completed first by using transaction VL32N before
posting goods receipt.
How to Determine Relevancy
The Simplification Item is relevant, if all these conditions apply together:
The Business Function DIMP_SDUD is not active (check with transaction SFW2 or
SFW_BROWSER)
The indicator "Document Flow Update for stock postings and return delivery" is not
set in the Global Shipping Data
Check table field TVSHP-SPE_INB_VL_MM via transaction SE16, or check the
indicator using the following Customizing activity: SAP Customizing Implementation
Guide: Logistics Execution > Shipping > Basic Shipping Functions > Configure Global
Shipping Data
Goods receipt postings or return delivery postings are done with reference to inbound
deliveries using transaction MIGO
Check table MSEG for entries with VGART_MKPF = "WE", TCODE2_MKPF =
MIGO_GR, VBELN_IM is not initial, and VBELP_IM is not initial
Required and recommended action(s)
Check the current business process for goods receipt processing whether affected or not
by the stricter consistency checks applied. Change the business process by ensuring the
inbound delivery contains the correct data prior to posting goods receipt, if applicable.
When the check item is relevant, there are two alternative options to proceed with the
conversion to SAP S/4HANA:
Apply for an exemption for this check item
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 627
Set in all clients of the system the indicator "Document Flow Update for stock
postings and return delivery" in the IMG activity “Configure Global Shipping
Data” under “Logistics Execution > Shipping > Basic Shipping Functions”.
Other Terms
MIGO, Goods Receipt, Inbound Delivery, Automotive, ECC-DIMP, S/4HANA
26.4 S4TWL - Change in default IDoc inbound processing with message type
DESADV
Application Components:IS-A-GR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2404011
S4TWL - Change in default
configuration of IDoc inbound
processing with message type DESADV
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP to SAP S/4HANA.
Prerequisite: In SAP ERP, shipping notifications from suppliers are processed by inbound
IDocs of message type DESADV using inbound process code DELS, and neither the
industry solution for Automotive has been activated nor the SAP Service Parts
Management solution has been implemented.
Solution
Description
In SAP S/4HANA, the default processing of shipping notifications via EDI using
inbound IDocs to create inbound deliveries changed, to support in addition the integration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 628
to Extended Warehouse Management, processes from automotive industry and processes
in Service Parts Management.
Business Process Related Information
When receiving an Advanced Shipping Notification (ASN) from a supplier by processing
an inbound IDoc of message type DESADV with inbound process code DELS in SAP
S/4HANA, by default the IDoc is now processed using function
module /SPE/IDOC_INPUT_DESADV1 to create an inbound delivery.
Function module /SPE/IDOC_INPUT_DESADV1 supports Extended Inbound Delivery
Processing used in automotive industry and in service parts management, including an
integration to Extended Warehouse Management. For scenarios where those capabilities
are not required, still function module IDOC_INPUT_DESADV1 is available.
How to Determine Relevancy
In SAP ERP, function module IDOC_INPUT_DESADV1 is assigned to inbound process
code DELS.
Required and Recommended Action(s)
It is recommended to use the more extended function module
/SPE/IDOC_INPUT_DESADV1, but function module IDOC_INPUT_DESADV1 is still
supported.
Option 1: Continue with function module /SPE/IDOC_INPUT_DESADV1
In case of customer extension implementations in SAP ERP using the enhancements
V55K0004, V55K0011, V55K0012 or V55K0013, refer to SAP Note 987150 for more
details on how to move those enhancements to work with function
module /SPE/IDOC_INPUT_DESADV1, if necessary.
Option 2: Continue using the previously used function module
IDOC_INPUT_DESADV1
Call transaction WE42 for maintaining inbound process codes for IDoc processing. Select
process code DELS and choose the details view. Exchange assigned function module
/SPE/IDOC_INPUT_DESADV1 by function module IDOC_INPUT_DESADV1.
Other Terms
S/4HANA, inbound delivery, shipping notification, EDI, DESADV
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 629
26.5 S4TWL - DATA MODEL IN INVENTORY MANAGEMENT (MM-
IM)
Application Components:MM-IM-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2206980
Material Inventory Managment: change
of data model in S/4HANA
Symptom
You want to install SAP S/4HANA and need additional information how to adjust your
customer enhancements, modifications or own functionalities to the new, simplified data
model of SAP S/4HANA Supply Chain (MM - Inventory Management).
You want to have information about what is different in SAP S/4HANA Supply Chain
(MM - Inventory Management) compared to Suite on HANA MM-IM.
Reason and Prerequisites
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 630
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
Table
description
DDL Source of CDS
View for redirect
View to read the
content of the
database table (w/o
redirect to
compatibility view)
View to read
the master
data
attributes
only
MKPF
Material
document
header
NSDM_DDL_MKPF
NSDM_MIG_MKPF
-
MSEG
Material
document
item
NSDM_DDL_MSEG
NSDM_MIG_MSEG
-
MARC
Plant Data
for Material
NSDM_DDL_MARC
NSDM_MIG_MARC
V_MARC_MD
MARD
Storage
Location
Data for
Material
NSDM_DDL_MARD
NSDM_MIG_MARD
V_MARD_MD
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 631
MCHB
Batch
stocks
NSDM_DDL_MCHB
NSDM_MIG_MCHB
V_MCHB_MD
MKOL
Special
Stocks from
Vendor
NSDM_DDL_MKOL
NSDM_MIG_MKOL
V_MKOL_MD
MSLB
Special
Stocks with
Vendor
NSDM_DDL_MSLB
NSDM_MIG_MSLB
V_MSLB_MD
MSKA
Sales Order
Stock
NSDM_DDL_MSKA
NSDM_MIG_MSKA
V_MSKA_MD
MSSA
Total
Customer
Orders on
Hand
NSDM_DDL_MSSA
NSDM_MIG_MSSA
-
MSPR
Project
Stock
NSDM_DDL_MSPR
NSDM_MIG_MSPR
V_MSPR_MD
MSSL
Total
Special
Stocks with
Vendor
NSDM_DDL_MSSL
NSDM_MIG_MSSL
MSSQ
Project
Stock Total
NSDM_DDL_MSSQ
NSDM_MIG_MSSQ
-
MSKU
Special
Stocks with
Customer
NSDM_DDL_MSKU
NSDM_MIG_MSKU
V_MSKU_MD
MSTB
Stock in
Transit
NSDM_DDL_MSTB
NSDM_MIG_MSTB
-
MSTE
Stock in
Transit to
Sales and
Distribution
Document
NSDM_DDL_MSTE
NSDM_MIG_MSTE
-
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 632
MSTQ
Stock in
Transit for
Project
NSDM_DDL_MSTQ
NSDM_MIG_MSTQ
-
MCSD
DIMP:
Customer
Stock
NSDM_DDL_MCSD
NSDM_MIG_MCSD
MCSD_MD
MCSS
DIMP: Total
Customer
Stock
NSDM_DDL_MCSS
NSDM_MIG_MCSS
MCSS_MD
MSCD
DIMP:
Customer
stock with
vendor
NSDM_DDL_MSCD
NSDM_MIG_MSCD
MSCD_MD
MSCS
DIMP:
Customer
stock with
vendor -
Total
NSDM_DDL_MSCS
NSDM_MIG_MSCS
MSCS_MD
MSFD
DIMP:
Sales Order
Stock with
Vendor
NSDM_DDL_MSFD
NSDM_MIG_MSFD
MSFD_MD
MSFS
DIMP:
Sales Order
Stock with
Vendor -
Total
NSDM_DDL_MFS
NSDM_MIG_MSFS
MSFS_MD
MSID
DIMP:
Vendor
Stock with
Vendor
NSDM_DDL_MSID
NSDM_MIG_MSID
MSID_MD
MSIS
DIMP:
Vendor
Stock with
NSDM_DDL_MSIS
NSDM_MIG_MSIS
MSIS_MD
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 633
Vendor -
Total
MSRD
DIMP:
Project
Stock with
Vendor
NSDM_DDL_MSRD
NSDM_MIG_MSRD
MSRD_MD
MSRS
DIMP:
Project
Stock with
Vendor -
Total
NSDM_DDL_MSRS
NSDM_MIG_MSRS
MSRS_MD
MARCH
History
NSDM_DDL_MARCH
NSDM_MIG_MARCH
-
MARDH
History
NSDM_DDL_MARDH
NSDM_MIG_MARDH
-
MCHBH
History
NSDM_DDL_MCHBH
NSDM_MIG_MCHBH
-
MKOLH
History
NSDM_DDL_MKOLH
NSDM_MIG_MKOLH
-
MSLBH
History
NSDM_DDL_MSLBH
NSDM_MIG_MSLBH
-
MSKAH
History
NSDM_DDL_MSKAH
NSDM_MIG_MSKAH
-
MSSAH
History
NSDM_DDL_MSSAH
NSDM_MIG_MSSAH
-
MSPRH
History
NSDM_DDL_MSPRH
NSDM_MIG_MSPRH
-
MSSQH
History
NSDM_DDL_MSSQH
NSDM_MIG_MSSQH
-
MSKUH
History
NSDM_DDL_MSKUH
NSDM_MIG_MSKUH
-
MSTBH
History
NSDM_DDL_MSTBH
NSDM_MIG_MSTBH
-
MSTEH
History
NSDM_DDL_MSTEH
NSDM_MIG_MSTEH
-
MSTQH
History
NSDM_DDL_MSTQH
NSDM_MIG_MSTQH
-
MCSDH
History
NSDM_DDL_MCSDH
NSDM_MIG_MCSDH
-
MCSSH
History
NSDM_DDL_MCSSH
NSDM_MIG_MCSSH
-
MSCDH
History
NSDM_DDL_MSCDH
NSDM_MIG_MSCDH
-
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 634
MSFDH
History
NSDM_DDL_MSFDH
NSDM_MIG_MSFDH
-
MSIDH
History
NSDM_DDL_MSIDH
NSDM_MIG_MSIDH
-
MSRDH
History
NSDM_DDL_MSRDH
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.
Some of the hybrid tables contain a field with the semantic "date of last change" (in many
cases field name is LAEDA). In the ERP solution this field has been updated with each
material document posting. With the introduction of the new data model in S/4 the hybrid
tables will not be updated with actual stock data anymore and also the field LAEDA will not
be updated. Hence, the semantic of this field for the material master data hybrid tables
changes to "date of last change of master data".
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 635
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.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 636
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 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.
If you later on like to make use of one of the fields in EXTEND VIEW for CI_COBL in the app
"Custom fields and logic" then you need to follow the instructions given in this article in the
SAP Help portal. Basically you need to remove the field from the EXTEND VIEW for
CI_COBL, save without activate and then add the field in the app "Custom fields and logic".
This is valid for release 1709 and higher.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 637
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 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 638
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. Those access methods shall not be used if the KEY
table contains more than 1000 records to to limitations of the SELECT.....FOR ALL
ENTRIES.
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 (those access
methods shall not be used if the KEY table contains more than 1000 records to to
limitations of the SELECT.....FOR ALL ENTRIES.). 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.
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.
Other Terms
S4TC, S/4 transition, MM-IM, Material Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 639
26.6 S4TWL - AVAILABILITY OF TRANSACTIONS IN MM-IM
Application Components:MM-IM-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2210569
Obsolete Material inventory
management transactions
Symptom
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 or the BAPI's BAPI_GOODSMVT_CREATE and
BAPI_GOODSMVT_CANCEL:
MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31,
MBNL, MBRL, MBSF, MBSL, MBST, MBSU and MBBM
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 especially with S/4HANA
OP1610 and higher because with this release a new enhanced and improved lock concept
has been introduced for transaction MIGO and the BAPI BAPI_GOODSMVT_CREATE
but the above listed obsolete transactions still using the old lock concept (see note
2319579). Hence in case of paralle posting done via one of the obsolete transactions and
transaction MIGO or BAPI BAPI_GOODSMVT_CREATE you may be able to create
stock inconsistencies just because the postings are not protected by the same lock object.
The transaction codes will be deprecated in the near future.
Reason and Prerequisites
Transaction were alreday outdated in SAP ERP 6.0x.
Solution
Use transaction MIGO or MMBE in dialog.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 640
Replace customer coding using the transaction codes MB01, MB04, MB05, MB0A,
MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL and MBSU (e.g.
by suing CALL TRANSACTION MBxy) by make use of function module
BAPI_GOODSMVT_CREATE
Replace customer coding using the transactions MB02 and MB03 by making use of
function module MIGO_DIALOG
Replace customer coding using the transaction MBST by making use of function module
BAPI_GOODSMVT_CANCEL
Other Terms
MIGO_GR, MIGO_GI, MIGO_ST, BAPI_GOODSMVT_CANCEL,
NSDM_MESSAGES499, NSDM_MESSAGES-499, omcq; MMBE
26.7 S4TWL - Material Ledger Obligatory for Material Valuation
Application Components:MM-IM-GF-VAL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267834
S4TWL - Material Ledger Obligatory for
Material Valuation
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Relevant IMG migration activities:
Customizing migration:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 641
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
from SAP ERP or SAP Simple Finance to SAP S/4HANA 1610 or higher:
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:
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
from SAP ERP or SAP Simple Finance to SAP S/4HANA 1610 or higher:
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 or higher, 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 642
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
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
Table
description
DDL source of
CDS view for
redirect (proxy
view)
View to read the content
of the original database
table (w/o redirect to
proxy view)
View to read
master data
attributes only
EBEW
Sales Order
Stock Valuation
MBV_EBEW
MBVEBEWOLD
V_EBEW_MD
EBEWH
History of Sales
Order Stock
Valuation
MBV_EBEWH
MBVEBEWHOLD
V_EBEWH_MD
MBEW
Material
Valuation
MBV_MBEW
MBVMBEWOLD
V_MBEW_MD
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 643
MBEWH
History of
Material
Valuation
MBV_MBEWH
MBVMBEWHOLD
V_MBEWH_MD
OBEW
Valuated Stock
with
Subcontractor
(Japan)
MBV_OBEW
MBVOBEWOLD
V_OBEW_MD
OBEWH
History of
Valuated Stock
with
Subcontractor
(Japan)
MBV_OBEWH
MBVOBEWHOLD
V_OBEWH_MD
QBEW
Project Stock
Valuation
MBV_QBEW
MBVQBEWOLD
V_QBEW_MD
QBEWH
History of Project
Stock Valuation
MBV_QBEWH
MBVQBEWHOLD
V_QBEWH_MD
Table 1: Affected tables with information about corresponding proxy objects, views for
accessing original database table and views for reading master data only
Business Process related information
If customers are not 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.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
MMPI: Initialize period for material master records (Not available
with activated Material Ledger)
Required and Recommended Action(s)
Perform Conversion Pre-Checks on start release to identify start situation
Related SAP Notes
Conversion Pre-Checks
SAP Note: 2194618
SAP Note: 2129306
Custom Code related information
SAP Notes: 1804812
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 644
26.8 S4TWL - Material Valuation - Statistical moving average price
Application Components:MM-IM-GF-LOCK, MM-IM-GF-VAL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267835
S4TWL - Material Valuation - Statistical
moving average price
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 changing the valuated inventory, the system uses exclusive locks
to calculate a consistent change in inventory value in situations where concurrent
transactions for the same material are ongoing. But, the need for setting exclusive locks is
mainly driven by the inventory valuation method:
An inventory valuation following the "Standard Price" method does (with a few
exceptions) not require to set an exclusive lock. This is because 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.
Whereas an inventory valuation following the "Moving Average Price" method often
requires to set an exclusive lock. This is because the relationship between unit
costs for material inventory (moving average price) on the one hand, and
inventory quantity and inventory value on the other hand, is often changing
during goods movements.
In SAP ERP, for materials with price control "Standard" the system calculates the
inventory valuation following the "Standard Price" method mentioned above.
Additionaly, it does an inventory valuation following the "Moving Average Price"
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 645
method in parallel, the so-called "statistical" moving average price. Unfortunately, this
"statistical" moving average price valuation requires exclusive locking as well.
As mentioned at the beginning, exclusive locking limits the transactional data throughput,
and therefore needs to be avoided to increase transactional data throughput
significantly for scenarios with a high volume of transactions.
If you do a system conversion to SAP S/4HANA on-premise edition, you have the option
to change locking behavior during goods movements to increase transactional data
throughput. As said, this is not mandatory for you, but nevertheless recommended in
order to achieve a significant increase of transactional data throughput for goods
movements.
If you select option to increase your transactional data throughput during goods
movements, this will have following effects:
Materials with price control 'S': System will set (with a few exceptions) only a shared
lock during goods movements.
Materials with price control 'V': System will set an exclusive lock during goods
movements in release SAP S/4HANA 1511. Beginning with release SAP
S/4HANA 1610, system will set an exclusive lock during goods movements only
in dedicated situations, for other situations it sets only a shared lock (see OSS
note 2338387 for details).
As described before, setting only a shared lock for materials with price control 'S' is
in conflict with concept of calculating "statistical" moving average price, which
would require an exclusive lock. Therefore, to gain the increase of transactional
data throughput, system deactivates "statistical" moving average price and
does not calculate it anymore.
In addition, the following database table fields are affected by the deactivation of the
"statistical" moving average price:
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”.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 646
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.
It is important to note that selecting this option can not be un-done.
If you do not select option to increase your transactional data throughput during goods
movements, this will have following effects:
Locking behaviour during goods movements is the same you know from SAP ERP.
Means, exclusive locks are set during goods movements and transactional data
throughput is limited.
Materials with price control 'S': system still calculates "statistical" moving average
price in parallel.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 647
Finally, if you like to select option to increase your transactional data throughput during
goods movements and you accept the drawback that "statistical" moving average price
gets deactivated, you can do the following:
In SAP S/4HANA 1511 and SAP S/4HANA 1610 execute report
SAPRCKM_NO_EXCLUSIVELY_LOCKING. As changes in customizing table
TCURM are not recorded in a customizing request, you have to run report in each
of your systems (customizing, development, production) separately.
Beginning with SAP S/4HANA 1709 you can use IMG activity "Set Material Lock
for Goods Movements" (SPRO -> Materials Management -> General Settings for
Materials Management).
As said, this is optional for converted systems running the S/4HANA on-premise edition.
Further Remarks
In the S/4HANA cloud edition or new installs of the SAP S/4HANA on-premise edition,
the option to increase transactional data throughput during goods movements is
mandatory and being set automatically. Deactivation of "statistical" moving average price
is therefore also mandatory there.
26.9 S4TWL - Performance optimizations within Material Document
Processing - lock beh
Application Components:MM-IM, MM-IM-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2319579
S4TWL - Performance optimizations
within Material Document Processing -
lock behavior and stock underrun
protection
Symptom
1. General
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 648
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
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.
Defined sequence of material documents (e.g. for moving average price).
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 649
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 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 650
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
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 651
no locks at all will be set in the late lock strategy case.
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 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 652
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.
Reason and Prerequisites
Introduction of new MM-IM data model enables improvements in lock behavior and
reduction of processing time and increase of throughput.
Solution
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.
LIS
LIS settings can be done by executing the customizing transaction OMO9 and LBW1 but
only for application "Inventory Controlling)). 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 or LBW1 (application
"Inventory Controlling) 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 653
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 its includes using stock aggregate data from
the internal tables XMabc must be refactored. Implemented BAdI methods are not
affected by this.
Other Terms
MM-IM; BAPI_GOODSMVT_CREATE; MB_CREATE_GOODS_MOVEMENT;
MIGO; Performance; Locks; LIS; INVCON; APO
26.10S4TWL - Material Valuation Data Model Simplification in S/4HANA
1610 and Higher
Application Components:MM-IM-GF-VAL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2337383
S4TWL - Material Valuation Data Model
Simplification in S/4HANA 1610 and
Higher
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 654
You are doing an upgrade from SAP S/4HANA 1511 to SAP S/4HANA 1610. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 655
26.11S4TWL - Goods movements without exclusive locking by material
valuation
Application Components:MM-IM-GF-LOCK
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2338387
S4TWL - Goods movements without
exclusive locking by material valuation
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 656
With SAP S/4HANA 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 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 anymore. In addition,
exclusive locking is still required, if SAP Note 1704534 (Deactivation of delivery costs
for ML update) has been implemented.
SAP S/4HANA for Oil & Gas does also benefit from the new option starting with SAP
S/4HANA 1709. For previous releases of SAP S/4HANA for Oil & Gas the
recommendation is to use “Exclusive block”.
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
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 657
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.
26.12S4TWL - CWM in SAP S/4HANA
Application Components:MM-IM-GF-CWM, IS-CWM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2358928
S4TWL - CWM in SAP S/4HANA
Symptom
CWM is available in SAP S/4HANA On premise beginning with 1610 FPS01. CWM is
not available in earlier releases of SAP S/4HANA even though technical objects are
visible.
Note, that the following features will not be supported by CWM 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 of the unit of measure for a material with value 'B' = Parallel Unit of
Measure (BUoM is Valuation Unit of Measure)
Flexible Material Prices (FMP) a small application to furthermore support the price
types of the ‘old architecture’
In addition to the mentioned features there are some additional changes which might have
impact on customer coding related to CWM (see chapter description).
A conversion from IS-CWM to CWM in SAP S/4HANA is not available as part of SAP
S/4HANA 1610.
As of SAP S/4HANA 1709, CWM is part of SAP's standard conversion tools.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 658
1. No further support of CWM business function /CWM/BF (“old CWM Architecture”)
in SAP S/4HANA
When the CWM-solution is made available in SAP S/4HANA, the ‘old architecture’ of
the industry 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 have to do a migration to switch to the ‘new architecture’ of CWM on
SAP ERP 6.0.
In case business function /CWM/CM_1 is active no further action is needed, because you
are already using the ‘new architecture’.
2. Category of Parallel Unit of Measure
In ECC 6.0 IS-CWM supports 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 of the unit of measure for a material with value 'B' (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 Warehouse Management
(EWM). For EWM the category 'B' will control the usage of a PUoM only for the
EWM solution in S4CORE.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 659
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.
3. Flexible Material Prices (FMP)
With the removal of the ‘old architecture’ all prices of Inventory Accounting (InvAcc)
had to be shifted to standard tables. Especially the last prices for material valuation were
transferred into table MBEW. But not all prices could be stored in the particular standard
tables.
For compatibility reasons FMP solution was developed to cover these self-ruled price
types. With S/4HANA the Flexible Material Prices is not supported.
You can check whether you use FMP with transaction SE16. Enter table
‘/FMP/D_MP_PRIC’ and check if there are entries available. In case there are no entries
you can be sure that this module was not used in the past at all.
For more information, see note: 2414624. See also SI10: Logistics_MM-IM.
In case of further questions please contact the CWM Solution Management.
4. BOR, BAPI, IDoc and ALE changes
Business objects (BOR-objects) and its function modules are provided to connect system
and solutions.
Following the strategy to bring CWM into S4CORE the decision was taken to omit
CWM BOR-objects as well as their respective generated coding. To compensate standard
BAPI function modules were CWM-enhanced instead:
BOR object
BOR method
CWM enhanced Standard BAPI
BUS1001006
SAVEDATA
BAPI_MATERIAL_SAVEDATA
BUS1001006
SAVEREPLICA
BAPI_MATERIAL_SAVEREPLICA
BUS2015
CONFIRMDECENTRAL
BAPI_INB_DELIVERY_CONFIRM_DEC
BUS2015
DELIVERYCHANGE
BAPI_INB_DELIVERY_CHANGE
BUS2015
SAVEREPLICA
BAPI_INB_DELIVERY_SAVEREPLICA
BUS2017
CREATEFROMDATA
BAPI_GOODSMVT_CREATE
LIKP
CONFIRMDECENTRAL
BAPI_OUTB_DELIVERY_CONFIRM_DEC
LIKP
DELIVERYCHANGE
BAPI_OUTB_DELIVERY_CHANGE
LIKP
SAVEREPLICA
BAPI_OUTB_DELIVERY_SAVEREPLICA
LIKP
SPLITDECENTRAL
BAPI_OUTB_DELIVERY_SPLIT_DEC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 660
You need to check if any obsolete CWM object (Type definition or Function Module) is
used by own customer coding. If any usage location is found the respective coding has to
be revised and adjusted.
In case of any question please contact the CWM Solution Management.
The following CWM BOR-objects are not available in SAP S/4HANA:
Deleted BOR object
Description
/CWM/BUS06
Standard material
/CWM/BUS15
Inbound delivery
/CWM/BUS17
Goods Movement
/CWM/BUS28
Material inventory
/CWM/BUS42
REM Backflush
/CWM/BUS70
Handling unit
/CWM/LIKP
Outbound Delivery
(Use transaction SWO1 to inspect the Business Objects)
The following list of dependent objects that are not available can be used to support an
investigation of own coding.
Obsolete Object Type
Method
Message Type
/CWM/BUS06
SAVEDATA
/CWM/MATMAS_BAPI
/CWM/BUS06
SAVEREPLICA
/CWM/MATMAS_MASS_BAPI
/CWM/BUS15
CONFIRMDECENTRAL
/CWM/SHP_IBDLV_CONFIRM_DEC
/CWM/BUS15
DELIVERYCHANGE
/CWM/SHP_IBDLV_CHANGE
/CWM/BUS15
SAVEREPLICA
/CWM/SHP_IBDLV_SAVE_REPLICA
/CWM/BUS17
CREATEFROMDATA
/CWM/MBGMCR
/CWM/LIKP
CONFIRMDECENTRAL
/CWM/SHP_OBDLV_CONFIRM_DEC
/CWM/LIKP
DELIVERYCHANGE
/CWM/SHP_OBDLV_CHANGE
/CWM/LIKP
SAVEREPLICA
/CWM/SHP_OBDLV_SAVE_REPLICA
/CWM/LIKP
SPLITDECENTRAL
/CWM/SHP_OBDLV_SPLIT_DECENTRAL
Obsolete Object Type
Method
IDOC Type
/CWM/BUS06
SAVEDATA
/CWM/MATMAS_BAPI01
/CWM/BUS06
SAVEREPLICA
/CWM/MATMAS_MASS_BAPI01
/CWM/BUS15
CONFIRMDECENTRAL
/CWM/SHP_IBDLV_CONFIRM_DEC01
/CWM/BUS15
DELIVERYCHANGE
/CWM/SHP_IBDLV_CHANGE01
/CWM/BUS15
SAVEREPLICA
/CWM/SHP_IBDLV_SAVE_REPLICA01
/CWM/BUS17
CREATEFROMDATA
/CWM/MBGMCR01
/CWM/LIKP
CONFIRMDECENTRAL
/CWM/SHP_OBDLV_CONFIRM_DEC01
/CWM/LIKP
DELIVERYCHANGE
/CWM/SHP_OBDLV_CHANGE01
/CWM/LIKP
SAVEREPLICA
/CWM/SHP_OBDLV_SAVE_REPLICA01
/CWM/LIKP
SPLITDECENTRAL
/CWM/SHP_OBDLV_SPLIT_DECENTR01
Obsolete Object Type
Method
Function module for outbound ALE
/CWM/BUS06
SAVEDATA
/CWM/ALE_MATERIAL_SAVEDATA
/CWM/BUS06
SAVEREPLICA
/CWM/ALE_MATERIAL_SAVEREPLICA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 661
/CWM/BUS15
CONFIRMDECENTRAL
/CWM/ALE_INB_DELVRY_CONFIRMDEC
/CWM/BUS15
DELIVERYCHANGE
/CWM/ALE_INB_DELVRY_CHANGE
/CWM/BUS15
SAVEREPLICA
/CWM/ALE_INB_DELVRY_SAVEREPL
/CWM/BUS17
CREATEFROMDATA
/CWM/ALE_GOODSMVT_CREATE
/CWM/LIKP
CONFIRMDECENTRAL
/CWM/ALE_OUT_DELVRY_CONFIRMDEC
/CWM/LIKP
DELIVERYCHANGE
/CWM/ALE_OUT_DELVRY_CHANGE
/CWM/LIKP
SAVEREPLICA
/CWM/ALE_OUT_DELVRY_SAVEREPL
/CWM/LIKP
SPLITDECENTRAL
/CWM/ALE_OUT_DELVRY_SPLIT_DEC
Obsolete Object Type
Method
Function module for inbound ALE
/CWM/BUS06
SAVEDATA
/CWM/IDOC_INPUT_MATMAS_BAPI
/CWM/BUS06
SAVEREPLICA
/CWM/IDOC_INPUT_MATMAS_MASS_BA
/CWM/BUS15
CONFIRMDECENTRAL
/CWM/IDOC_INPUT_SHP_IBDLV_CONF
/CWM/BUS15
DELIVERYCHANGE
/CWM/IDOC_INPUT_SHP_IBDLV_CHAN
/CWM/BUS15
SAVEREPLICA
/CWM/IDOC_INPUT_SHP_IBDLV_SAVE
/CWM/BUS17
CREATEFROMDATA
/CWM/IDOC_INPUT_MBGMCR
/CWM/LIKP
CONFIRMDECENTRAL
/CWM/IDOC_INPUT_SHP_OBDLV_CONF
/CWM/LIKP
DELIVERYCHANGE
/CWM/IDOC_INPUT_SHP_OBDLV_CHAN
/CWM/LIKP
SAVEREPLICA
/CWM/IDOC_INPUT_SHP_OBDLV_SAVE
/CWM/LIKP
SPLITDECENTRAL
/CWM/IDOC_INPUT_SHP_OBDLV_SPLT
Obsolete Object Type
Method
IS-CWM Segment
/CWM/BUS06
SAVEDATA
/CWM/E1BP_MBEW
/CWM/E1BP_MBEWX
/CWM/E1BP_MATRETURN2
/CWM/E1BP_MARM
/CWM/E1BP_MARMX
/CWM/BUS06
SAVEREPLICA
/CWM/E1BPE1MBEW
/CWM/E1BPE1MBEWX
/CWM/E1MATMAS_MASS_BAPI
/CWM/E1BPE1MARM
/CWM/E1BPE1MARMX
/CWM/BUS15
CONFIRMDECENTRAL
/CWM/BUS15
DELIVERYCHANGE
/CWM/E1SHP_IBDLV_CHANGE
/CWM/BUS15
SAVEREPLICA
/CWM/E1SHP_IBDLV_SAVE_REPLI
/CWM/BUS17
CREATEFROMDATA
/CWM/LIKP
CONFIRMDECENTRAL
/CWM/E1SHP_OBDLV_CONFIRM_DE
/CWM/LIKP
DELIVERYCHANGE
/CWM/E1SHP_OBDLV_CHANGE
/CWM/LIKP
SAVEREPLICA
/CWM/E1SHP_OBDLV_SAVE_REPLI
/CWM/LIKP
SPLITDECENTRAL
/CWM/E1SHP_OBDLV_SPLIT_DECE
(Use transaction BDBG to inspect Message types, IDoc types, Segments and Function
Modules for ALE.)
5. Screen Sequences CW and CE for Material Master
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 662
Screen sequences 'CW' and 'CE' for Material Master are not delivered as part of CWM in
S/4HANA. Although existing sequences can be migrated to S/4HANA they are no longer
supported by SAP and should be replaced by standard sequences.
In IS-CWM special Screen sequences were delivered to integrate required CW
information in the material master:
CW (Catch Weight Management)
CE (CWM with EWM Views)
These Screen Sequences CW and CE are not necessary in S/4HANA because the CW
related information is integrated in the standard screen sequence '21'.
In the unlikely case that a customer had defined additional screens these customer entries
have to be integrated in the used standard '21'.
Please use transaction OMT3B to review the definitions.
Please use transaction OMT3E to review the Screen sequence control.
Please use transaction OMT3U to review ‘Organizational levels’.
6. Removal of attributes within CWM
There are some table attributes which are (or will be) no longer supported in a CWM
activated solution.
If one of the objects in the following list is used within customer coding, it has to be
adjusted to ensure a correct system behavior.
Tolerance Group: use field ‘CWQTOLGR’ of table MARA instead of
'/CWM/TOLGR'
CWM and EWM use the same tolerance group values. Different semantic
tolerance checks for CWM and EWM have to be harmonized.
Category/Type of a Unit of Measure: use field ‘TY2TQ’ of table MARM instead of
'/CWM/TY2TQ'
In IS-CWM, KZWSM of table MARA and KZWSO of table MARM was set to ‘B’
for all CW materials. In S/4HANA this flag will not be set by CWM. For CW
material, its content will be set according to the settings of Active Ingredient
Management in the same way as for standard materials.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 663
7. Removal of BAdI-Definitions
The following listed Business Add-In (BAdI) are no longer available in S/4HANA. Any
related customer implementation is obsolete and can also be removed.
/CWM/TOLERANCE_GROUP (Tolerance Group)
/CWM/DEFAULT_STOCK_O (Conversion of the BUoM or the PUoM to an
alternative UoM)
/CWM/DEFAULT_MIGO (Allows the entry quantity, the parallel entry quantity and
the entry units of measure to be proposed for catch weight materials in transaction
MIGO)
Other Terms
CWM, IS-CWM, S/4HANA, Simplification List, FMP, Flexible Material Prices, BOR,
BAPI, IDOC, ALE, BAdI, Screen Sequence
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 664
27.Logistics – PLM
27.1 S4TWL - Engineering Desktop (EDesk)
Application Components:PLM-WUI-APP-EDK
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267868
S4TWL - Engineering Desktop (EDesk)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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, on-premise 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 on-premise
edition 1511
EDESK_CUS, EDESK_IPPE
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 665
Customers can move to SAP Engineering Control Center for SAP S/4HANA.
Custom Code related information
EDESK is not a "reuse" component. EDESK is rather an application with hooked in
BAdis and custom code. If the CDESK-Application is not available, no BAdis are
executed and therefore custom code is not executed.
27.2 S4TWL - DMS - STEP Support
Application Components:LO-PDM-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267870
S4TWL - DMS - STEP Support
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 on-
premise edition 1511
STEP10, STEP20
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 666
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
27.3 S4TWL - DMS Documents@WEB
Application Components:CA-DMS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267871
S4TWL - DMS Documents@WEB
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
CVW*
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 667
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
27.4 S4TWL - Variant Configuration
Application Components:LO-VC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267873
S4TWL - Variant Configuration
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
In SAP S/4HANA processes are simplified by switching off obsolete and redundant
functionality related to variant configuration. It is not possible anymore to maintain the
"Classification as selection condition" in the bill of material. Furthermore, the usage
of actions has been disabled.
Thereby, customers can benefit from the following:
The modelling will be simpler.
The error rate is reduced and the consistency of models will increase.
Follow-up processes such as Material Requirements Planning (MRP) Live can be
accelerated.
Description
The following functionality is disabled in SAP S/4HANA, On Premise 1511:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 668
Object dependencies of type actions have been documented as obsolete. Creation of
object dependencies of type actions isn't possible anymore (e.g. transaction
CU01). Configuration models containing actions are still supported and behave
like before, but new actions can't be created.
It's not possible to maintain "Classification as Selection Condition" in Material
BOM items anymore (e.g. transactions CS01, CS02). If in Material BOM
items classes as selection condition are already maintained, the BOM explosion
will work as before. But it's not allowed to use "Classification as Selection
Condition" for BOM items, where it wasn't used before.
Transactions have been removed (see list below)
Business Process related information
Object dependencies of type procedures should be used instead of type actions. It's
recommended to substitute existing actions by procedures in the configuration
models.
Class nodes should be used in Material BOM items instead of "Classification as
selection condition". It's recommended to make this substitution also in existing
material BOMs.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
CU51E -> Included in CU51
CU52 -> Included in CU51
CU52E -> Included in CU51
CU55 -> Obsolete
CU80 -> Use PMEVC instead
CUMODEL -> Use PMEVC instead
Required and Recommended Action(s)
If you use actions in VC models, no action needs to be taken for existing models. For
new models, however, we recommend using the concept involving procedures and
contraints. We also recommend remodeling existing models to be prepared for future
innovations.
If you use "Classification as a selection condition," no action is required for existing
models. For new models we recommend setting up selection conditions in BOMs by class
nodes.
Related SAP Notes
Custom Code related information
SAP Notes: 2210904 , 2214906
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 669
27.5 S4TWL - Classification
Application Components:CA-CL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267878
S4TWL - Classification
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
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.
For batch input and direct input, use SAP S/4HANA Migration Cockpit.
Transaction not available since SAP
S/4HANA on-premise edition 1511
Available alternative transactions and reports
CL20 Assign Object to Classes
CL22 Allocate Class to Classes
CL20N Assign Object to Classes
CL22N Assign Class to Superior Classes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 670
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
O021 Class Data Transfer
O023 Display Class Maintenance Data File
O024 Transfer Class Data: Direct Input
CLNA Namespace f. Classes /
Characteristics
CT01 Create Characteristic
CT02 Change Characteristic
CT03 Display Characteristic
CT05 Create Characteristic
CT06 Display Characteristic
CT11 Where-Used List for Characteristics /
Characteristic Values
CT21 Batch Input for Characteristics
CT22 Maint. Seq. File for Characteristics
CT23 Display Chars for Change Number
CT24 Display Change Numbers Used
CL24N Assign Objects / Classes to Class
-
-
-
-
-
-
-
-
-
-
-
-
CT04 Characteristics
CT04 Characteristics
CT04 Characteristics
CT04 Characteristics
CT04 Characteristics
CT12 Where-Used List for Characteristics /
Characteristic Values
-
-
CC04 Product Structure Browser
CC04 Product Structure Browser
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 671
CT25 Where-Used List of Chars in Deps
CTCP Copy C tables for characteristics
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
CL6T Copy Text for Classes
CLCP Copy Classification C Tables
CL21 Display Object in Classes
CL23 Display Class for Classes
CL25 Display Objects in Class
CL30 Find Objects in Classes
-
-
CL6BN Object List
-
-
-
O1CL Class Types
CL6AN Class List
CC04 Product Structure Browser
-
-
CL20N Assign Object to Classes
CL22N Assign Class to Superior Classes
CL24N Assign Objects / Classes to Class
CL30N Find Objects in Classes
Accessible via Customizing
O005 C CL Characteristic Default Settings
S_ABA_72000139
S_ABA_72000140
S_ALR_87003718 IMG Activity: SIMG_CFMENUO000O1CL
S_ALR_87003725 IMG Activity: SIMG_CFMENUO000O008
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 672
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
S_ABA_72000141
S_ALR_87009588
S_ALR_87011758
Required and Recommended Action(s)
No special actions required.
Related SAP Notes
Custom Code related information
SAP note:2213569
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 673
27.6 S4TWL - IPPE-BOM Converter
Application Components:PLM-PPM-PDN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267879
S4TWL - IPPE-BOM Converter
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 on-premise
edition 1511
PPECS
Required and Recommended Action(s)
Customers using this functionality should evaluate if Product Structure Management and
Product Structure Synchronization fit their needs.
Related SAP Notes
Custom Code related information
SAP Note: 2226275
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 674
27.7 S4TWL - BOM, Routing, Production Version
Application Components:LO-MD-BOM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267880
S4TWL - BOM, Routing, Production
Version
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Production versions are mandatory in S/4HANA. MRP, planned order creation, and
production order creation only find a BOM and routing alternative if a production version
is maintained for the BOM and routing alternative.
Business Value
Production versions allow to define which BOM alternative goes together with which
routing alternative
Mandatory production versions make MRP sourcing simpler. There is only one
option to determine BOM and routing alternatives for a manufactured material
There is no need to control MRP sourcing with additional control indicators like the
selection method MARC-ALTSL in the material master
Production versions are mandatory in PP/DS. PP/DS is an integral part of S/4HANA.
Mandatory production versions make sourcing in MRP and PP/DS more similar
Sourcing for manufactured and for purchased parts is more similar. In S/4HANA
production versions are the source of supply for manufactured materials.
Purchasing info records, contracts, and delivery schedules are the possible sources
of supply for purchased parts. Every possible source of supply has temporal
validity, lotsize interval, and a status, which blocks using the source of supply in
MRP, but not in manual sourcing.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 675
Description
With SAP S/4HANA, on-premise edition 1511, the functional relation between Bill of
Material (BOM), Routing and Production Version has changed. It is now mandatory for
Manufacturing BOMs to maintain the product version for correct BOM explosion.
Production versions can automatically be created for BOMs using report Product Version
Migration for BOM (report CS_BOM_PRODVER_MIGRATION). Production versions
can automatically be created for BOMs and routings using report Program for production
version migration for BOM determination (report
CS_BOM_PRODVER_MIGRATION02).
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.
Required and Recommended Action(s)
It is recommended to migrate BOMs, for which there is no corresponding routing using
report CS_BOM_PRODVER_MIGRATION. It is recommended to migrate BOMs, for
which there exist corresponding routings using report
CS_BOM_PRODVER_MIGRATION02.
Related SAP Notes
Custom Code related information
SAP Notes: 2215061, 2215123
Other Terms
Production version, Bill of Material, BOM, BOM explosion, component list, verid,
components, component, subcontracting, production order, planned order, subcontracting
purchase requisition, subcontracting purchase order, MRP, MD01, MD02, MD03,
MD01N, MRP Live, MS01, MS02, MS03, MD40, MD41, MD42, CS01, CS02, MD11,
MD12, MD13, subcontracting schedule line, subcontracting scheduling agreement, BOM
usage, STLAN, alternatives, ALTSL, selection method, selection priority, priority, BOM
selection ID, selection ID, long-term planning, STLID, LTPID, CSLID, OPPQ, PLSC-
LTPID, MS31, MS32, MS33, STLAN, STLAL, ARANG, MDFV, C223, MM01,
MM02, RMMRP010, RMMRP000, RMMPS000, MDBT, MDBS, MSBT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 676
27.8 S4TWL - SAP PLM Recipe Development
Application Components:PLM-WUI-RCP-RCP, PLM-WUI-RCP-LBL, PLM-WUI-RCP-SPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267893
S4TWL - SAP PLM Recipe
Development
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Fast Entry screen and Compliance with Expert server not supported on S/4 HANA
Solution
Description
With SAP S/4HANA, on-premise edition 1511 following functional changes were done:
1) Maintenance a specification using the Fast Entry Screen is not available.
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.
Compliance check without expert server: the current 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 677
Compliance Check with the Expert Server is used if entries exist in DB Table
EHSBC_RC_PARA (check with SE16)
Other Terms
PLM, Recipe Development, Fast Entry Screen, Compliance, Expert Server
27.9 S4TWL - Engineering Change Management ECR/ECO
Application Components:CA-GTF-ECM, LO-ECH, PLM-WUI-OBJ-ECN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267918
S4TWL - Engineering Change
Management ECR/ECO
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
The Engineering Change Request / Engineering Change Order functionality is no more
available with SAP S/4HANA.
Solution
Description
With SAP S/4HANA the current the Engineering Change Request / Engineering Change
Order functionality within SAP Product Lifecycle Management (SAP PLM) is not
available anymore. It is recommended for new customers to use Change Record instead
for tracking, approving and facilitating (change management) purposes. Alternatively
Engineering Record (only available on Web UI as part of the compatibility
package) could be assessed.
Business Process related information
Managing (tracking, approving and facilitating) changes will still be possible. The
Change Record / Engineering Record shall be used for this.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 678
The change number will serve to identify the explicit changes and the Change Record /
Engineering Record is to be used to manage the whole process. The approval process, the
objects to be changed will all be part of the Engineering Record, while the change
number will solely be used to facilitate the changes after approval has been given.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
CC31 - Create Change Request
CC32 - Change Change Request
CC33 - Display Change Request
CC62 - Conversion of change packages
OS72 - ECH: Workflow for ECR/ECO
OS73 - ECH: Workflow for Object Mgmt Record
Required and Recommended Action(s)
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
Change Record / Engineering Record. Set up Change Record / Engineering Record
(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
Other Terms
Change Number, Change Master, Change Management, Engineering Change Request,
Engineergin Change Order, ECR, ECO
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 679
27.10S4TWL - Enterprise Search in SAP Product Lifecycle Management
(SAP PLM)
Application Components:PLM-WUI-APP-SEA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267836
S4TWL - Enterprise Search
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
PLM Enterprise Search models will not work after an upgrade to S/4HANA.
Solution
Description
With SAP S/4HANA, on-premise edition 1511 the Enterprise Search models are now
replication free search models (using HANA DB tables instead) within SAP Product
Lifecycle Management (SAP PLM).
Business Process related information
With the new solution the following searches are not available in SAP S/4HANA on-
premise 1511 release:
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 680
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
With the SAP S/4HANA op-premise 1610 release the following searches are still not available:
Document search with attached document content
Recipe search with formula item quantity
Search for any object with IDs without leading zeroes
From the SAP S/4HANA op-premise 1709 release on the following searches are still not
available:
Recipe search with formula item quantity
Search for any object with IDs without leading zeroes (with the exception of the
material number, see the note 2935353)
Required and Recommended Action(s)
Customizing and Custom Code related
information
SAP Note: 2217234
How to Determine Relevancy
Navigate to the PLM Search customizing: Product Lifecycle Management (PLM) ->
PLM Web User Interface -> PLM Web Applications -> PLM Search -> Define
Settings for PLM Search
Check if any of the following columns contains entries referring to a custom search
model or a class that resides in the customer namespace:
Object Type of Service
Result Class Name
Key Conv. Class Name
Configuration ID
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 681
Other Terms
PLM, Enterprise Search
27.11S4TWL - Engineering Change Management Change Sequence Graph
Application Components:LO-ECH
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267920
S4TWL - Engineering Change
Management Change Sequence Graph
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Transactions related to Change Sequence Graph are not available in SAP S/4HANA
anymore.
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 682
Change Sequence Graph is used if entries exist in DB Tables ENODE or EDGE
(check with SE16)
Other Terms
Change Sequence Graph, Engineering Change Management
27.12S4TWL - Engineering Workbench
Application Components:LO-EWB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267943
S4TWL - Engineering Workbench
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Upgrade to S/4 HANA
Solution
Description
With SAP S/4HANA, on-premise edition 1511 the Engineering Workbench is not the
target architecture and will not receive any further updates(EWB Functionality in SAP
S4HANA on-premise edition 1511 is not considered as future technology. Functional
equivalent is provided by the visual manufacturing planner, see also the Business Process
related information).
Business Process related information
It is suggested to use alternative UIs, e.g. SAP Fiori App for Maintain Bill of
Material, Visual Manufacturing Planner for Creating Manufacturing BOMS from
EBOMs and also doing component allocation to routings.
The related transaction CWBQM remains available even beyond the defined
compatibility scope period and allows the maintenance of inspection plans (plan type
“Q”) and specific features therein (e.g. multiple specifications for inspection
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 683
characteristics, mass changes). However, no functional equivalent or additional
functionality will be provided in future.
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 SAP in place of Engineering Workbench. As of now
new applications e.g. SAP Fiori App for Maintain Bill of Material, Visual Manufacturing
Planner for Creating Manufacturing BOMS from EBOMs and also doing component
allocation to routings will get innovations an shall be used in order to get new
innovations in S/4HANA.
Other Terms
Engineering Workbench, Bill of Material
27.13S4TWL - Collaborative Engineering
Application Components:LO-CEP-CTL, LO-CEP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268017
S4TWL - Collaborative Engineering
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 684
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
27.14S4TWL - iPPE Time Analysis
Application Components:AP-PPE-ACT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268018
S4TWL - iPPE Time Analysis
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 685
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
27.15S4TWL - Routing Component Assignment
Application Components:PLM-WUI-APP-RTG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268041
S4TWL - Routing Component
Assignment
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 686
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
27.16S4TWL - Release Management Framework
Application Components:PLM-PPM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268042
S4TWL - Release Management
Framework
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
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 Change
Record or Engineering Record functionality 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 687
Required and Recommended Action(s)
It is recommended for new customers to have a look at the Change Record or
Engineering Record functionality and check if the functionality there covers your
requirements.
Related SAP Notes
Custom Code related information
SAP Note: 2226357
27.17S4TWL - Engineering Record
Application Components:PLM-WUI-OBJ-ECR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268043
S4TWL - Engineering Record
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Upgrade information
Solution
Description
The PLM Web UI Engineering Record (PLM-WUI-OBJ-ECR) is part of the
compatibility package, which comes with limited usage rights. For more details on the
compatibility scope and it’s expiry date and links to further information please refer to
SAP note 2269324. In the compatibility matrix attached to SAP note 2269324, PLM Web
UI Engineering Record can be found under the ID 441.
Its alternative solution, Change Record (PLM-CR) is available with more modern user
interface and additional features, and it is continuously being improved. However,
customers can continue to use Engineering Record within SAP S/4HANA as long as the
compatibility pack is supported.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 688
Business Process Related Information
The following capabilities are the key available capabilities in the alternative
solution, Change Record:
SAP Fiori UX to deliver personalized, responsive, and simple user experience
including:
Status-based field attributes
Visual change process to track milestones
Quick overview on assigned change objects
Thumbnails of change objects (on-premise only)
Workflow driven change management process using process routes:
Rule-based automatic or ad-hoc template loading
Support of parallel, sequential
Support of background tasks (on-premise only)
Graphical process route status overview
Integration to S/4HANA Teams and Responsibility Management
Automatic agent determination
Unified My Inbox for task owners to monitor and handle their tasks
Email notifications on task assignments (on-premise only)
Sub-workflows for change objects
Ad-hoc stakeholder communication with SAP CoPilot or built-in commenting
functions
Support of Electronic Signatures including signature strategies (on-premise only)
Easy attachments including support for Document Info Records
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 689
Change impact analysis to determine the related impact in the downstream
processes
Automatic Change Number generation
Change Record hierarchies
Engineering Cockpit, giving actionable insights on business process with visualized
data
Extensibility on customer attributes via
SAP S/4HANA Custom Fields and Logic app
Integration to Classification System
Search capabilities using SAP Fiori Search
Newly Added Features with On-Premise 2022 release:
Enabling Digital Signature at Change Item level (on-premise only)
Ability to assign purpose to a changed record type via configuration
Integration of BOM objects to change records include:-
Equipment BOM
Standard BOM
Functional location BOM
Variant BOM
Order BOM
WBS BOM
Integration of task list object types to change records include:
Equipment (type E)
Functional location (type T)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 690
General maintenance task list (type A)
Rough-cut planning profile task list (type 3)
Reference operation set task list (type S)
Rate routing task list (type R)
Reference rate routing task list (type M)
More information about Change Record can be found in the following applications:
[Manage Change Records]
[Apps in Change Management]
Comparing to the capabilities of Engineering Record in ECC, the following key feature is currently
missing in SAP S/4HANA Change Record:
Allowing customer-defined change objects
Other Terms
Engineering Record, PLM Web UI, Change Record, compatibility pack
27.18S4TWL - PLM Labeling Usage
Application Components:PLM-WUI-RCP-LBL, PLM-WUI-RCP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2387911
S4TWL - PLM Labeling Usage
Symptom
SAP PLM Recipe Development Labeling Usage hiding
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 691
In S4 OP in PLM Recipe Development Labeling usage tab under General Data not
supported
Solution
In SAP PLM Recipe Development Labeling object the header level Usage tab is not
supported and disabled. Relevant rating and validity area search fields were also removed
from the PLM Advanced Search functionality for labeling object. See related Custom
Code note in reference section for details.
Other Terms
S4CORE, Simplification, Hiding, Labeling, Usage
27.19S4TWL - Engineering Record with LAMA
Application Components:PLM-WUI-OBJ-ECR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2401762
S4TWL - Engineering Record with
LAMA
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
When customers perform a conversion to SAP S/4HANA from a DIMP LAMA system,
they need to transfer the changes items from the XML storage to the database persistence
to convert the internal material numbers.
Business Process related information
Run the /PLMI/ER_CI_TRANSFER report.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 692
27.20S4TWL - Assemblies
Application Components:PLM-WUI-OBJ-PSM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267840
S4TWL - Assemblies
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In SAP S/4HANA, the functions related to Assemblies in product structure management
within SAP Product Lifecycle Management (SAP PLM) are not available.
Business Process related information
Product Assembly is not available in SAP S/4HANA, on-premise edition 1511. 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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 693
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.
27.21S4TWL - New Access Control Management
Application Components:PLM-WUI-APP-ACC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2601548
S4TWL - New Access Control
Management (ACM)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Simplification Item is applicable in this case.
Reason and Prerequisites
Access Control Management has restrictions in S/4HANA.
Solution
Description
The PLM specific Access Control Management (ACM) is available in the SAP
S/4HANA, but it has some differences from the Business Suite functionality.
Also please check the related SAP Note: 2212593
Business Process related information
The ACM is available in SAP S/4HANA, but only supports instance specific data access
via the owning contexts (PLM_ACC) for recipes (PLM_RCP), specification (PLM_SPC)
and document info record (PLM_DIR) business objects.
Note, that the Access Control Lists are not supported in SAP S/4HANA anymore.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 694
To check if Access Control Management is in use, see below the "How to Determine
Relevancy" chapter. If you are using Access Control Management (Access Control
Contexts and Access Control Lists) to control access to system data, you should consider
or remodel it with ERP authorization, usually managed with PFCG roles.
Related SAP Notes
Custom Code related information
SAP Note
2212593
S4TWL - Access Control Management (ACM) - only relevant up to S/4HANA
1709 FPS0
SAP Note
2267842
How to Determine Relevancy
This Simplification Item is relevant, if ACM objects are linked to unsupported Business
Objects. Check if entries exist in DB Table /PLMB/AUTH_OBSID using transaction
SE16.
This note is relevant from S/4HANA 1709 FPS1 onwards.
Other Terms
PLM, ACM, Simplification, Access Control Management
27.22S4TWL - Process Route in PLM Web UI
Application Components:CA-EPT-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2704849
S4TWL - Process Route in PLM Web UI
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Upgrade information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 695
Solution
Description
The PLM reusable component Process Route Web UI is embedded in the
following components:
Material (PLM-WUI-OBJ-MAT)
Document (PLM-WUI-OBJ-DMS)
Change Number (PLM-WUI-OBJ-ECN)
Material BOM (PLM-WUI-OBJ-BOM)
Product Structure Management (PLM-WUI-OBJ-PSM)
Recipe Development (PLM-WUI-RCP)
Authorizations and Access Control Context (PLM-WUI-APP-ACC)
This reusable component is part of the compatibility package, which comes with limited
usage rights. For more details on the compatibility scope and it’s expiry date and links to
further information please refer to SAP note 2269324. In the compatibility matrix
attached to SAP note 2269324, Process Route Web UI can be found under the ID
441. The alternative solution is to use the solution Change Record (CR) to manage
the related processes of the objects above. The first version (1809) of the alternative
solution Change Record (CR) is available now, and it is planned to continuously improve
the new solution in the coming years. However，customers can continue to use the
Process Route Web UI embedded in the Web UI for the objects above within SAP
S/4HANA as long as the compatibility pack is supported.
For more detail regarding the alternative solution Change Record (CR), please refer to
SAP Note 2268043.
Other Terms
Process Route Web UI; Change Record
27.23S4TWL - Classification - Data Cleanup before Migration
Application Components:CA-CL
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 696
Note Type
Note Number
Note Description
Business Impact
2949845
S4TWL - Classification - Data Cleanup
Before Migration
Symptom
You are doing a system conversion to SAP S/4HANA 1909 or higher on-premise
edition. The following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
None
Solution
During an upgrade to S/4HANA 1909OP or higher version there is a conversion logic to
fill the CLF_HDR database table.
This logic requires that the INOB table does not contain any duplicates. If the results of
the pre-check contains any inconsistencies, please follow the steps in SAP Note 2948953.
Other Terms
Transition Worklist, SAP S/4HANA, on-premise, CLF_HDR
27.24S4TWL - Behavior change for AVC Sales Order (SET) scenario
configuration models
Application Components:LO-VCH
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3190519
S4TWL - Behavior change for AVC
Sales Order (SET) scenario
configuration models
Symptom
Business Value
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 697
In the future it shall be possible to safely reuse planned order / production order
configuration models in bundles (configuration models with sales order (SET)
configuration profiles) in advanced variant configuration (AVC).
Description
The safe reuse is enabled by introducing a form of encapsulation for object dependencies
from planned order / production order configuration models if they are used in bundles /
SETs. For a detailed explanation please see below.
Reason and Prerequisites
A planned order / production order configuration profile (PPO profile) is used for
standard configuration models. Typically, configurable materials with this type of profile
are configured and sold standalone. But it is also possible to bundle several such PPO
models and to sell them together as a set. Technically, this is achieved by creating a
configuration model with profile type sales order (SET) scenario and by using the PPO
models as the leafs in the BOM.
Example If you want to sell a bundle consisting of a configurable laptop and some
configurable accessories you create a sales order (SET) scenario configuration model
where the laptop and each of the accessories are a leaf item in the maxBOM of the
bundle. Only the laptop and the accessories are produced, not the SET (requirements
generation at component level).
Presently, the AVC supports only PPO and SET profiles as configurable components in
bundles / SETs.
This reuse of PPO models in bundles, however, causes problems in the interpretation of
object dependencies. More precisely, there are two distinct issues:
(1) If the PPO model contains an object dependency that refers to $parent / $root: Imagine, for
example, that characteristic X shall take its value from characteristic Y in the PPO configuration
model. This is frequently expressed via procedures of the form $self.X = $root.Y, where the
assignment target is $self and the "read"-characteristic is on $root. In a PPO model without BOM
explosion $self and $root refer to the same object and everything works as expected. But if the PPO
model is configured as part of a bundle $root suddenly refers to the root item of the bundle model - the
object dependency has changed its meaning. Please note that this phenomenon is not limited to
procedures or $root. It affects all types of object dependencies and all uses of $parent and $root in the
PPO configuration model (keep in mind that PPO models with BOM explosion are not supported in
bundles yet).
(2) If the PPO model contains a constraint that relates characteristics from different classes, and those
classes occur more than once in the bundle: Imagine that characteristic X from class CX shall be equal
to characteristic Y from class CY (and vice versa). This is frequently formulated as a constraint
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 698
OBJECTS: CX IS_A (300) CX, CY IS_A (300) CY.
RESTRICTION: CX.X = CY.Y.
If the PPO model is now included in the bundle twice, the following issue occurs: If you manually set
a value for X on the one instance of the PPO model, the constraint automatically assigns Y, but it does
so on both the one and the other instance. This happens because constraints match globally,
everywhere where the classes addressed occur. However, in our example, clearly this is an unwanted
side-effect from one instance of the PPO model into the other. Please note that this phenomenon is not
limited to including the same PPO model more than once into the bundle - it occurs everytime when
different items in the bundle make use of the same classes addressed by a constraint on one of the
items.
These issues are present in AVC's support of the sales order (SET) scenario today, just as they are
present in LO-VC's support of the scenario. For the AVC we have decided to change this situation by
introducing encapsulation for object dependencies for the reuse of PPO models in bundles. The new
behavior can be described as follows:
Object dependencies belonging to a PPO model in a bundle affect only the PPO model they
belong to.
Please note that it is still possible to express relations between the different items in a bundle:
Object dependencies belonging to the SET model affect all the items in the bundle / have full
visibility.
Solution
How to Determine Relevancy
This note is relevant for you if you have (or are about to create) sales order (SET)
configuration profiles for advanced variant configuration. This is the case if in table
CUCO there is an entry with KDSET = X and PROC_MODE = A.
Transitioning
The new behavior does not become effective immediately. For a period of one S/4 release
both behaviors are available so that remodeling is possible. Once you have adjusted your
configuration models to the new behavior you can switch on the new behavior of AVC as
follows:
In S/4 OP go to transaction VCH_NEW_BUNDLING to switch on the new behavior.
In S/4 Cloud enable toggle IDEA_CONFIGURE_NEW_BUNDLING in the feature
management cockpit.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 699
The new behavior becomes mandatory with the 2023 OP / the 2302 Cloud release of S/4
HANA.
Required and Recommended Actions
Please check your sales order (SET) scenario configuration models and adjust them as
needed. We recommend you pay particular attention to the following points:
(1) If today you relate characteristics from the bundle with characteristics from the PPO
model using $self, $parent and $root, the following idiom may be helpful for replacing
the dependencies. Imagine you have a procedure for value inheritance on the PPO model
that reads $self.X = $root.Y where (different from our previous example) X belongs to
the PPO model, and Y to the bundle. Furthermore assume that $self refers to the instance
of class C_COMP that is on position '0020' of the BOM of $root. Then the following
constraint achieves a similar value inheritance:
OBJECTS: COMP IS_A (300) C_COMP, BUND IS_A (300) C_BUND.
CONDITION: PART_OF(COMP,BUND,'0020').
RESTRICTION: COMP.X = BUND.Y.
With this pattern, the value assignment works from top to bottom and vice versa. If you
want inheritance to be only from top to bottom, use the following constraint pattern:
OBJECTS: COMP IS_A (300) C_COMP, BUND IS_A (300) C_BUND.
CONDITION: PART_OF(COMP,BUND,'0020').
RESTRICTION: COMP.X = BUND.Y IF SPECIFIED BUND.Y.
Note that using these idioms you get a constraint assignment where previously there was
a procedure assignment. There may be situations where you want to keep authorship, for
example, when inheriting a value as a default. Imagine that our previous example is
changed to set a PPO model default from a bundle-level characteristic via a procedure
$self.X ?= $root.Y on the PPO model. Here we recommend using a helper characteristic
XHelper together with a constraint:
OBJECTS: COMP IS_A (300) C_COMP, BUND IS_A (300) C_BUND.
CONDITION: PART_OF(COMP,BUND,'0020').
RESTRICTION: COMP.XHelper = BUND.Y.
and a procedure $self.X ?= $self.XHelper.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 700
(2) If you have allocated constraints that are meant to relate different items in a bundle to
one of the PPO items instead of to the bundle itself we recommend moving the constraint
to the bundle level.
(3) Selection conditions in the bundle model do not need adjusting. They are part of the
bundle model, not the PPO model.
Other Terms
Advanced variant configuration, AVC, sales order (SET) scenario, bundling, object
dependencies
27.25S4TWL - Project Management Integration with DMS
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3300448
S4TWL - Project Management
Integration with DMS
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this
case. Integration to SAP Portfolio and Project Management - Project Management
Integration with DMS is part of the SAP S/4HANA compatibility scope, which comes
with limited usage rights. For more details on the compatibility scope and it’s expiry date
and links to further information please refer to SAP note 2269324. In the compatibility
matrix attached to SAP note 2269324, Integration to SAP Portfolio and Project
Management can be found under the ID 440.
Reason and Prerequisites
The integration of Project Management with SAP Document Management (DMS) is
categorized as not part of the target architecture. To link existing DMS documents object
links can be used. For document management either Project document management or
integration with other tools, such as SAP Document Center or SAP Enterprise Product
Development Collaboration can be used.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 701
Review and evaluate the provided alternatives where applicable.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, DMS, Portfolio and
Project Management, PPM
27.26S4TWL - Product Designer Workbench
Application Components:LO-MD-PPW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267841
S4TWL - Product Designer Workbench
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 via transaction PDN
iPPE-objects not type of CMP-application of the product structure
Colour nodes (type COL)
Generic nodes (type GEN)
Focus nodes (type FOC)
Concept nodes (type CON)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 702
Non-configurable part of the product structure, e.g. variant assembly
Alternatives of the product structure
Following functionalities are not available
Priority definition for nodes
Variant differentiation
The automotive scenarios provided via transaction PPE are not affected. PPE is still
available.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
PDN
Required and Recommended Action(s)
Customers shall move to Product Structure Management for SAP S/4HANA, on-premise
edition 1511.
Related SAP Notes
Custom Code related information
SAP Note: 2226431
27.27S4TWL - cFolders
Application Components:PLM-CFO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267845
S4TWL - cFolders
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 703
With SAP S/4HANA, on-premise edition 1511 cFolders interfaces are not available. SAP
recommends to evaluate SAP Enterprise Product Development 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 S/4HANA on-premise
edition 1511
CFI01 – Importing Documents
CFE01 – Exporting Documents
CFI02 – Importing Documents, Materials and Bills of Material
CFE02 – Exporting Documents, Materials and Bills of Material
CFI03 – Importing Documents, Materials, Bills of Material and
iPPE Objects
CFE03 – Exporting Documents, Materials, Bills of Material and
iPPE Objects
CFC01 – Customizing for cFolders backend integration
CFC02 – Customizing for cFolders backend integration, BOMs
Required and Recommended Action(s)
Customers have to establish data exchange processes with partners using other techniques
like SAP Enterprise Product Development.
Related SAP Notes
Custom Code related information
SAP Note: 2224778
27.28S4TWL - cDesk
Application Components:CA-CAD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267850
S4TWL - cDesk
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 704
Reason and Prerequisites
CAD Desktop is not supported in SAP S/4HANA.
Solution
Business Value
Moving from the CAD-Desktop to SAP Engineering Control Center will provide
additional value to customers:
Customers will be enabled to manage growing product complexity and diversity
Users will receive a much better user experience
SAP Engineering Control Center is the platform to integrate mechanical and electrical
CAD (Computer Aided Design) tools to enable Systems Engineering and
Mechatronic Design.
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
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
edition 1511
CDESK, CDESK_CUS, CDESK_DEL_DBTRACE,
CDESK_READ_DBTRACE, CDESK_SAVE_DBTRACE
Required and Recommended Action(s)
Customers can move to SAP Engineering Control Center for SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 705
For more information on upgrading from CAD Desktop to SAP Engineering Control
Center see SAP Note 2117843 or SAP SCN Wiki
(URL: https://wiki.scn.sap.com/wiki/x/gQrXHQ)
27.29S4TWL - Recipe Management
Application Components:PLM-RM-REC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267863
S4TWL - Recipe Management
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
PLM Recipe Management related transactions are disabled
Solution
Description
SAP PLM Recipe Management (RM) is not available in SAP S/4HANA. This also
affects PLM RM sub-functions such as Labelling, Trial Management and Handover to
Manufacturing. The appropriate business requirements are covered within successor
functionality SAP S/4HANA PLM Recipe Development (excluding Trial Management.)
The takeover of recipes from SAP Business Suite into SAP S/4HANA 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).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 706
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 Start Workbench
BD_GEN_GRCP General Recipe Distribution
BD_GEN_SRCP Replicate Site Recipe
FRML02 Edit Recipe Formula
FRML03 Display Recipe Formula
FRML04 Formula Information System
MRTRS_START Start MR Transformation
MRTRSC01 RFC Destination of GR
MRTRSC02 Master Recipe Generation
RMSL02 Change Label Set
RMSL03 Display Label Set
RMSTAT Mass Status Change
Customizing Transaction not
available in SAP S/4HANA
on-premise edition 1511
ORCP*, RCP*, RMS*, RMX*
Required and Recommended Action(s)
Projects need to migrate their processes from PLM Recipe Management functional
capabilities to PLM Recipe Development functional capabilities.
Data Migration from RM recipes to RD recipes is an integrated part of the tool and can
be executed after the system conversion SAP S/4HANA. For the detailed steps, follow
the guides for the migration from PLM RM to PLM RD.
The specification object is not impacted by the switch over to PLM RD.
Related SAP Notes
Conversion Pre-Checks
Does the customer use TRIAL MANAGEMENT
Check which recipes, formulas and label objects need to
be migrated
Migration transactions - executable before or after
system conversion
/PLMI/RCP_MIGRATION Recipe
Migration
/PLMI/RMSL_MIGRATION Migration of
Label Sets
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 707
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
Other Terms
PLM, Recipe Management, Simplification
27.30S4TWL - Engineering Client Viewer (ECL)
Application Components:CA-DMS-EAI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267864
S4TWL - Engineering Client Viewer
(ECL)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA, on-premise edition 1511 the ECL-Viewer Functionality within
SAP Product Lifecycle Management (SAP PLM) will no longer be available. Parts of the
functionality and use cases can be covered by SAP Visual Enterprise Viewer.
Business Process related information
2D and 3D viewing in GUI transactions with ECL viewer will not be available any longer
You may consider Visual Enterprise Viewer as an alternative in some transactions like
e.g. Document Management and for some of the file formats for other file formats you
may think about using the frontend application instead where appropriate
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 708
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.
27.31S4TWL - Easy Document Management (Easy DMS)
Application Components:CA-DMS-EUI, CA-DMS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267866
S4TWL - Easy Document Management
(Easy DMS)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
With SAP S/4HANA, on-premise edition 1511, the Easy DMS Functionality within SAP
Product Lifecycle Management (SAP PLM) will no longer be available.
Solution
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 to switch to SAP Document Center
for SAP DMS.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 709
However this product is not a replacement for Easy DMS in terms of features and needs
evaluation by customers if it fits specific business processes. Refer to the attachment for
more details on the solution.
Customers can also consider extended document management functionality with Manage
Document FIORI application.
https://help.sap.com/viewer/4c3d1c6b3d744f84aab4c273f979f430/1809.000/en-
US/1bc746147317485ca9a0847be2d0668b.html
Business Process related information
Transaction not available in
SAP S/4HANA on-premise
edition 1511
EASYDMS_CUS
Required and Recommended Action(s)
Switch to SAP Document Center for DMS which is powerful and simple.
Related SAP Notes
Other Terms
Easy DMS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 710
28.Logistics – PM
28.1 S4TWL - Object List Number Field Length Extension
Application Components:LO-MD-SN, LO-HU, SD-SLS, QM-IM, PP-SFC-EXE, MM-PUR, MM-IM,
LE-SHP, PM-WOC-MO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2580670
S4TWL - Object List Number Field
Length Extension
Symptom
You carry out a system migration from SAP ERP to SAP S/4HANA On-Premise or
Cloud edition. In SAP ERP, you use the object list functionality in one or more logistical
processes (maintenance order, service order, inspection lot, delivery, purchase, serial
numbers). In this case, the following worklist item is relevant for the SAP S/4HANA data
transfer:
Reason and Prerequisites
In SAP ERP, you use the object list functionality in the SAP standard system. You also
access object lists in customer-defined programs or change object lists with customer-
defined programs. It does not matter whether the customer-defined programs are called
within SAP ERP (for example, Z reports) or from an external source via interfaces.
Solution
Description:
To enable the processing of even large object list volumes in a future-proof manner, SAP
has decided to extend the object list numbers (table OBJK, domain OBJKN, data element
OBJKNR) from the data format INT4 to the data format INT8. In addition to the table
OBJK, this change affects all further tables that contain a field with a reference to the
data element OBJKNR. For details, see the simplification item "SI10: Logistics_PM"
(title: S4TWL - Object List Number Field Length Extension).
Business-process-related information
No effects on the standard SAP business processes are anticipated.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 711
Required and recommended action(s)
Customer-defined programs must be adjusted accordingly, particularly in line with the
changed interfaces in standard SAP programs (APIs, BAPIs, and so on).
If customer-defined tables with object list information have been created, the tables must
be adjusted and the content must be converted accordingly. This should take place
automatically using the SAP Upgrade Manager (SUM).
System prerequisites:
Release SAP NetWeaver 7.50
The embedded RFC library of SAP GUI has Release 7.50.
Other Terms
"SI10: Logistics_PM", OFLE, S4CORE
28.2 S4TWL - Obsolete predictive scenarios in PM
Application Components:PM-WOC, PM-FIO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3259029
Deprecation of predictive scenarios
PREDICTDAMAGECODE and
PREDICTMAINTOBJECTPART
Symptom
The predictive scenarios PREDICTDAMAGECODE and
PREDICTMAINTOBJECTPART are deprecated without replacement with SAP
S/4HANA 2022 FPS01 / SAP S/4HANA Cloud 2302.
This affects the 'Predicted Maintenance Object part' and 'Predicted Damage code' in the
Malfunction data section in the details page of the app Perform Maintenance Jobs
(F5104A).
Reason and Prerequisites
Functionality is deprecated.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 712
Solution
Functionality is deprecated.
Other Terms
PAL, APL, F5104A
28.3 S4TWL - Obsolete POWL Applications in Maintenance Management
Application Components:PM-PRM-MP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3372889
S4TWL - Obsolete POWL Application
Manage Maintenance Plan and Item List
(W0026)
Symptom
The Manage Maintenance Plan and Item List (W0026) app has been deleted and is no
longer available on the SAP Fiori launchpad. You can use the following successor apps
which are available on the SAP Fiori launchpad: Manage Maintenance Plans (F5325)
and Manage Maintenance Items (F5356).
Reason and Prerequisites
Functionality is obsolete.
Solution
You can use the following successor apps which are available on the SAP Fiori
launchpad: Manage Maintenance Plans (F5325) and Manage Maintenance Items (F5356).
Other Terms
W0026, The Manage Maintenance Plan and Item List, POWL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 713
28.4 S4TWL - LIS in EAM
Application Components:PM-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267463
S4TWL - LIS in EAM
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
28.4.1 Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
28.4.2 Solution
Description
Remark: For the general approach regarding analytics within SAP S/4HANA see the
following analytics simplification item in cross topics area.
The plant maintenance 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
evaluate Equipments, Functional Locations , Notifications and Order. 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 714
LIS only supports material numbers with up to 30 characters
Future plant maintenance 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 plant maintenance specific 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 plant maintenance 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
Required and Recommended Action(s)
Invest reasonably in the LIS. The LIS is intended as an interim solution, which can be
used until PM 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
Custom Code Related information:
Enhancements and modifications of the LIS will not work for the future anayltic solution
Custom reports reading one of the following tables will not work after the update of the
LIS tables is switched off:
S061 Location and planning
S062 Object class and manufacturer
S063 Damage analysis 30
S064 Damage analysis
S065 Object statistics
S070 Breakdown statistics
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 715
S114 Vehicle Consumption Analysis
S115 Cost Evaluation
S116 Customer Analysis
These tables will be replaced by CDS views providing more or less the same information
but with different column names and structures.
28.5 S4TWL - Download Data in MS Access out of List
Application Components:PM-WOC-LE, PM, PM-EQM-LE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270076
S4TWL - Download Data in MS Access
out of List
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 or Open Office
instead (Functionality available in SAP S/4HANA on-premise edition 1511 delivery but
not considered as future technology. Functional equivalent is available.).
We plan to discontinue this functionality inon one of the next releases
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Do not Invest in the download to access functionality. instead use download to Excel or
Open Office . Within Excel / Open Office you can use the embedded tools for populating
an DB.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 716
Custom Code Related information:
In Case you use this functionality plan to populate your MS Access DB in a different
way.
28.6 S4TWL - Scheduling of Maintenance Plan
Application Components:PM-PRM, PM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270078
S4TWL - Scheduling of Maintenance
Plan
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Transaction IP30 is doing scheduling for Maintenance Plans. Within this scheduling
outdated technology (Batch Input) is used.
Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is not available yet.
We plan to discontinue this in one of the next Releases.
The new transaction for doing mass scheduling is IP30H which is optimized for HANA
and is offering parallel processing at a much hiher speed.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Review your background Jobs which you most probably have scheduled periodically for
transaction IP30 (Reports RISTRA20) and create new background jobs for IP30H
(Report RISTRA20H).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 717
28.7 S4TWL - Mobile Asset Management (MAM)
Application Components:PM-WOC-MB, PM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270080
S4TWL - Mobile Asset Management
(MAM)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Product Mobile Asset Management (MAM) functionality is not available with
S/4HANA. For your mobility related requirement to manage maintenance management,
please refer SAP roadmap.
With this change, we plan to discontinue the Objects mentioned in the piece list and
delete these objects from SAP S/4HANA 2021 FPS1 onwards. Refer note 2250183 for
further details.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Please check if you use any of the objects mentioned in the piece list in any of your
Custom Applications , reports etc they will not work anymore and you have to create
alternative arrangement.
28.8 S4TWL - Batch Input for Enterprise Asset Management (EAM)
Application Components:PM
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 718
Note Type
Note Number
Note Description
Business Impact
2270107
S4TWL - Batch Input for Enterprise
Asset Management (EAM)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Transaction IBIP is using Batch Input as an technology to create transactional data for all
EAM Objects (Equipment, Functional Location, Notification, Order, Maintenance Plan,
Task List...). This is an outdated technology.
Within EAM we plan to discontinue to support this technology in a future release.
Batch Input programs may also no longer work as transactions may have changed
functionality or may be completely removed within some areas
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 fully available yet.).
Plant Maintenance offers a set of API´s which are supporting the creation / change of
Plant Maintenance data like:
Equipment
BAPI_EQUI_CREATE
BAPI_EQUI_CHANGE
BAPI_EQUI_GET_DETAIL
Functional Location
BAPI_FUNCLOC_CREATE
BAPI_FUNCLOC_CHANGE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 719
BAPI_FUNCLOC_GET_DETAIL
Notification
BAPI_ALM_NOTIF_CREATE
BAPI_ALM_NOTIF_DATA_ADD
BAPI_ALM_NOTIF_DATA_MODIFY
BAPI_ALM_NOTIF_GET_DETAIL
Maintenance Order
BAPI_ALM_ORDER_MAINTAIN
Please also review the following blogs in SCN
https://blogs.sap.com/2015/11/24/eam-bapi-s-support-now-custom-fields-and-user-status/
https://blogs.sap.com/2015/12/14/eam-order-notification-api-s-support-now-custom-
fields-and-user-status/
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Please check if you use Batch Input for creating / changing Plant Maintenance data. If
Yes do not invest further in this kind of technology. Recommendation within EAM is to
use the API´s wherever possible.
28.9 S4TWL - Changes In List Reports For Order and Notification
Application Components:PM-WOC-MN, PM-WOC-MO, PM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270108
S4TWL - Changes In List Reports For
Order and Notification
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 720
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Prerequisite for executing the list reports for orders and notifications in SAP
S/4HANA are the performance improvements described in notes 393393 and
551133.
The reports listed there need to be executed.
Within Enterprise Asset Management we plan to discontinue IW37, IW49 in a future
release.
It is recommend to use transaction IW37n, IW49n instead.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Implement the notes if needed and run the reports 'QM_PHASE_FILL' and
'RIAFVC_IPHAS_FILL' before the ugrade to SAP S/4HANA if not done yet
In case you use the transaction IW37, IW49, please use IW37n or IW49n instead.
28.10S4TWL - WebDynpro Application for Maintenance Planner (<= EhP4)
Application Components:PM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270110
S4TWL - WebDynpro Application for
Maintenance Planner (<= EhP4)
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 721
You are doing a system conversion to SAP S/4HANA, on-premise edition. You are
using PM Functionality Maintenance Planer, Technician or Supervisor delivered (<=
EhP4). The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Old WD Application covering Maintenance Tenchnician, Planner, and Supervisor
delivered in Business Suite in Release <= EhP4 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.).
Maintenance Technician role is obsolete for S4 HANA release.
Use the new Maintenance Planner and Maintenance Worker Roles available in S/4
HANA (Business Package for Maintenance Worker 1.61).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Activate the below Business Functions to get the full functionality of Maintenance
Planner and Maintenance Worker Role.
LOG_EAM_SIMPLICITY_2
LOG_EAM_SIMPLICITY_3
LOG_EAM_SIMPLICITY_4
LOG_EAM_SIMPLICITY_5
LOG_EAM_SIMPLICITY_6
Other Terms
Maintenance Planer, Technician, Supervisor, S4HANA, Business Package for
Maintenance Worker 1.61,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 722
28.11S4TWL - Enterprise Search in EAM
Application Components:PLM-WUI-APP-SEA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270123
S4TWL - Enterprise Search in EAM
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
All related EAM search models have been transfered to replication free search models.
As well within the EAM Web Dynpro the search models are now used for certain object
within the value help which allows user to sophisticatly search for the corresponding
values
For PLM search models please review Note 2217234
Required and Recommended Action(s)
You have to activate the Enterprise search models
Please check our How To Guide in SCN. https://blogs.sap.com/2016/07/01/eam-
enterprise-search-how-to-guide/
Here yo find all Configuration capabilities within Enterprise search and it will
guide you through how you can change Enterprise Search to your specific needs.
In case you intend to use the value help within EAM Web Dynpro App´s please refer
to
Innovation Discovery: Enterprise search functionality and a master data
information center within the SAP Enterprise Asset Management solution chapter
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 723
Enterprise search in the Input Help you find a ppt with the configuration steps.
https://zinnovationdiscovery-
supportportal.dispatcher.hana.ondemand.com/#/innovation/6CAE8B27FCC31ED
5A995CA1EED5A222A
In case you have mainteained special setting for Value help in Customizing under
Plant Maintenance -> Maintenance Roles -> Maintenance Worker -> Configure
Search help Assignment
check if value help is sufficient for finding the right values
If yes delete correspondinh entry
If no leave this as it is, In this case the value help you have defined will be
used
28.12S4TWL - SAP Graphics in EAM Transactions
Application Components:PM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2482659
S4TWL - Usage of SAP Business
Graphics
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The graphical output in Enterprise Asset Management transactions using SAP Business
Graphics, e.g. in transaction IP19, is not available in SAP S/4HANA.
Generally SAP Business Graphics used in Plant Maintenance applications are no
longer supported in SAP S/4HANA. The attached pdf gives some of the examples where
these charts are used
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 724
No influence on business processes expected.
Required and Recommended Action(s)
Please use the tabular display options.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 725
29.Logistics – PP
29.1 S4TWL - ERP Line-Balancing and Sequencing
Application Components:PP-FLW-SEQ, PP-FLW-LDS, PP-FLW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268084
S4TWL - ERP Line-Balancing and
Sequencing
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
ERP Line-Balancing and Sequencing is part of the SAP S/4HANA compatibility scope,
which comes with limited usage rights. For more details on the compatibility scope and
it’s expiry date and links to further information please refer to SAP note 2269324. In the
compatibility matrix attached to SAP note 2269324, ERP Line-Balancing and
Sequencing can be found under the ID 448.
This means that you need to migrate from ERP Line-Balancing and Sequencing to its
designated alternative functionality PPDS Model mix planning before expiry of the
compatibility pack license. This note shall provide an overview on the scope of ERP
Line-Balancing and Sequencing which is going to expire with the compatibility pack
license, how this maps to the designated alternative functionality, if this alternative
functionality is already available or when it’s planned to be available and how you can
migrate to the alternative functionality.
This note will regularly be updated to reflect more details on the alternative functionality
and the migration.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 726
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 the classic ERP transactions 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"
PPDS optimizers can compute production sequences that minimize violations of
restrictions
PPDS is an integral part of S/4HANA on-premise edition. You do not have to install a
separate APO system.
Please refer to PPDS Model mix planning in help.SAP.com to get an idea of PPDS
sequence planning.
Required and Recommended Action(s)
As ERP Line-Balancing and Sequencing can be used until the expiry date of the
compatibility pack license, it’s up to each customer to decide, when (with which of the
coming SAP S/4HANA releases) they want to migrate to the designated alternative
functionality. Though the decision, at which point in time this will be done, should be
taken early in advance in order to plan accordingly for the migration efforts.
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.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 727
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, ERP Sequence
planning, ERP Line-Balancing, LAS1, LAS2, LAS3, LAS4, LDD1, LDD2, LDD3, ...
29.2 S4TWL - MRP in HANA
Application Components:PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268085
S4TWL - MRP Live on SAP HANA -
MD01N
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
MRP Live is a synonym for MD01N and MRP Live on SAP HANA
Solution
Description
Production planners have to make sure that 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 (MD01N); a new 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
(MD01N) has some additional advantages including the following, for example:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 728
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.
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 in SAP S/4HANA. MRP lists are part of the SAP
S/4HANA compatibility scope, which comes with limited usage rights. For more details
on the compatibility scope and it’s expiry date and links to further information please
refer to SAP note 2269324. In the compatibility matrix attached to SAP note 2269324,
MRP lists can be found under the ID 443.
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.
Master production scheduling can be done in MRP Live using Material Scope "S".
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 Live has also some restrictions. Details are explained in note 1914010.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 729
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 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 (AMDP
BAdI) 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 (see note 2883845 for example).
Not relevant for S/4HANA Essentials Edition: Creation indicator can still be used if the
material is planned using classic MRP transactions. Furthermore the creation indicators
maintained in MRP groups will be considered, if the MRP Live forces a material to be
planned using classic MRP.
Required and Recommended Action(s)
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:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 730
Re-implement BAdI implementations and extensions of the classic MRP as AMDP
BAdI (see "BAdI related information" below for further details).
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.
Please note that it might be necessary to adjust certain BAdI implementations even if you
still use classic MRP. This is since the data reading processes of some classic MRP
transaction (like MD01, MD02, MD03, etc.) have been optimized for HANA database
accesses. That means even the classic MRP reads material receipts and
requirements using an ABAP managed database procedure (AMDP). This HANA
optimized data reading in classic MRP transaction is not switchable in SAP S/4HANA as
it was possible in SAP ECC 617 and 618. For further details regarding necessary BAdI
adjustments see "BAdI releated informations" below.
Related SAP Notes
Convers
ion Pre-
Checks
No
BAdI
related
informat
ion
Many calculations in MRP Live are implemented in SQLScript/CDS
views/AMDPs running on the database server as opposed to classic ABAP code, which
is performed on the application server. Enhancements or BAdI implementations of the
classic MRP run does not work with MRP Live if the material is supported/planned
within MRP Live. Please note: MRP Live can force materials into classic MRP
if materials use a setup which is not supported in MRP live.
Example: MRP Live is started for 2 materials A and B. Material A uses a setup which is
supported in MD01N. Therefore the new BAdIs (see table below) have to be used for
material A. The second material B is not supported in MD01N and the planning run
route this material B into classic MRP. Therefore the existing classic BAdI
implementation still can be used for material B. This refers only to all BAdI
implementations which influence the planning process and storaging behavior of the
classic MRP.
Existing BAdI implementations which influence the data reading process of the classic
MRP (e.g. BAdI MD_CHANGE_MRP_DATA) will or won't be supported in S4HANA
depending on the used planning transactions:
If the planning transactions are not optimized for HANA (like MD50, MD51 or all LTP
planning transactions), then the classic BAdIs/extension with their
implementations will still be supported.
If the planning transactions are optimized for HANA (like MD01, MD02, MD03,
materials forced to classic MRP by MRP Live), then it is required to use an
alternative ABAP BAdI. In this case BAdI MD_ADD_ELEMENTS has to be used
to adjust the data determined by the HANA optimized reading processes.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 731
A new set of AMDP BAdIs will be available for MRP Live from SAP S/4HANA on-
premise edition 1603. BAdI implementations of the classic MRP should be translated
into AMDP BAdI implementations if still required. This affects the following BAdIs:
Purpose
Classic BAdI or
extension
AMDP BAdI
Comment
Subcontra
cting logic
MD_SUBCONT_LO
GIC
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
See simplification
item 2.1.11.1PP-MRP
- Subcontracting
Reading
material
receipts
and
requireme
nts
MD_CHANGE_MRP
_DATA
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
Use BAdI
MD_ADD_ELEMENT
S for classic MRP
transactions which
are optimized for
HANA
Scheduling
of stock
transfer
requireme
nts
MD_STOCK_TRAN
SFER
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
User-
defined
MRP
elements
in MRP
MD_ADD_ELEMEN
TS
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
Planned
independe
nt
requireme
nt
consumpti
on
MD_PIR_FLEX_CO
NS
PPH_MRP_RUN_BADI =>
MDPS_ADJUST
Change
planning
parameter
s
MD_MRP_PARAME
TERS
PPH_MRP_LOTSIZING_BADI
=> LOT_SIZE_CALC
PPH_MRP_NETTING_BADI
=> NET_REQ_CALC
Change
MRP list
MD_MRP_LIST
MRP lists are not
available by MRP Live
Change
purchase
requisition
s created
by MRP
MD_PURREQ_CHA
NGE,
MD_PURREQ_POS
T
PPH_MRP_RUN_BADI =>
PURREQ_BEFORE_UPDATE
_ADJUST
Change
planned
orders
created by
MRP
MD_PLDORD_CHA
NGE,
MD_PLDORD_POS
T
PPH_MRP_RUN_BADI =>
PLANORD_BEFORE_UPDAT
E_ADJUST
Source of
supply
determinati
on in MRP
MD_MODIFY_SOUR
CE,
MD_MODIFY_PROD
VERS,
PPH_MRP_SOURCING_BADI
=> SOS_DET_ADJUST
See simplification
item
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 732
MD_EXT_SUP (see
comment)
2.1.11.7Simplified
Sourcing
The function from
BAdI MD_EXT_SUP
cannot be
implemented for all
scenarios in MRP
Live. MD01N supports
stock transfer
processes from plant
to MRP areas in
standard. Stock
transfer processes
between different
MRP areas in the
same plant are not
possible in MRP Live
with a BAdI
implementation (SAP
note
3233524). Correspon
ding materials can be
set using transaction
MD_MRP_FORCE_C
LASSIC in such a way
that they are
automatically
redirected to classic
MRP in MRP Live.
Package
size for
parallel
processing
MD_MRP_RUN_PA
RALLEL
MRP_DISPATCHER_BADI =>
DISPATCH_CREATE_TASK
Material
selection
for MRP
run
Extension
M61X0001
PPH_MRP_NETTING_BADI
=>
AT_PLANNING_FILE_ENTRIE
S_READ
Table
related
informat
ion
MRP live is still writing most of the classic ERP tables. Most importantly planned orders,
purchase orders, and delivery schedule lines are still written into the same tables. The
classic MRP was writing data into the following tables, which are no longer populated by
MRP live. If your custom code reads data from these tables, then it should be adjusted
to read data from the new data source when moving from the classic MRP to MRP live.
Purpose
Old Table
New data source
Comment
Materials MRP was
not able to plan
MDKP with
selection
group 8
populated
Table PPH_DBVM with MSGID
populated
Various material
master attributes
MDKP
Table MARC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 733
controlling MRP
functions such as
lot-sizing
End of MRP
planning time fence
MDKP field
FIXTR
Add MARC-FXHOR to
PPH_DBVM-DSTMP
MRP list
MDTB
call function
module MD_MDPSX_READ_API
MRP planning file
DBVM,
MDVM
Table PPH_DBVM
See
note 2268088
MRP runtime
statistics
MONI
Table PPHMRPLOGITEM
Other Terms
MRP Live, MD01n
29.3 S4TWL - Planning File
Application Components:PP-MP-LTP, PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268088
S4TWL - Planning File
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 734
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.
Besides the setup reports, which trigger a new planning (NETCH = X) for all objects
and also do a consistency check automatically, there are conversion reports
PPH_CONVERT_MRPRECORDS and PPH_CONVERT_MRPRECORDS_SIMU,
which take over the change flags (NETCH, RESAL, etc.) from the old database table
DBVM. In this context it should be checked with the consistency check report
RMMDVM10 first, whether the old entries in DBVM are consistent and then conversion
can be done.
SAP S/4HANA, on-premise editions 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 2.1.11.35Planning Horizon.
Transaction not
available in SAP
S/4HANA on-premise
edition
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
in SAP S/4HANA)
RMDBVM00, RMDBVM10 (for conversion MDVM/MDVL into
DBVM/DBVL and back),
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 735
RMMDVM10, RMMDVM20 (creation and consistency check for
MDVM/DBVM), RMMDVL10, RMMDVL20 (creation and deletion for
MDVL/DBVL).
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 (PP-MRP) and the report PPH_SETUP_MRPRECORDS_SIMU
for simulative MRP records (PP-MP-LTP). Alternatively, you can also use the
conversion reports PPH_CONVERT_MRPRECORDS and
PPH_CONVERT_MRPRECORDS_SIMU.
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
29.4 S4TWL - Total Dependent Requirements
Application Components:PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268089
S4TWL - Total Dependent
Requirements
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 736
Solution
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
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
29.5 S4TWL - Forecast Based Planning
Application Components:PP-MRP, MM-CBP-CBP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 737
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268095
S4TWL - Forecast Based Planning
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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. Planned independent requirements can be created from forecast demand
The system records all changes of planned independent requirements which facilitates
reporting
Business Process related information
If you decide to replace forecast based planning 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
Using PIRs instead of forecast demands provides several advantages in S/4:
SAP provides APIs to handle PIRs.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 738
SAP provides with new FIORI-apps to handle PIRs (e.g. 'Maintain PIRs').
PIRs allow for a consumption with sales demands and dependent requirements or
stock transfer demands.
It is possible to split PIRs.
It is possible to re-organize unused PIR demands.
For PIRs the history can be recorded.
A detailed description of all actions which can be executed for Step 1 can be found in the
How-To-Guide mentioned in note 2844909 - Data Transfer of Forecast Demands to
Planned Independent Requirements (PIRs) and PIR Reorganization ( - the document
focuses on cloud systems, but the corresponding classical report or transactions are
named as well - ).
Required and Recommended Action(s)
Forecast Based Planning is part of the SAP S/4HANA compatibility scope, which comes
with limited usage rights. For more details on the compatibility scope and it’s expiry date
and links to further information please refer to SAP note 2269324. In the compatibility
matrix attached to SAP note 2269324, Forecast Based Planning can be found under the
ID 450.
As Forecast Based Planning can be used until the expiry date of the compatibility pack
license, it’s up to each customer to decide, when they want to migrate to the designated
alternative functionality. Though the decision, at which point in time this will be done,
should be taken early in advance in order to plan accordingly for the migration efforts.
29.6 S4TWL - Release status for different RFC function modules revoked
Application Components:PP-SFC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268112
S4TWL - Release status for different
RFC function modules revoked
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 739
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
Structure
Affected fields
COCF_SN_CREATE_EAM
RIQS5
BAUTL, MATNR, EMATNR,
RM_MATNR
COCF_SN_CREATE_PP
RIQS5
BAUTL, MATNR, EMATNR,
RM_MATNR
COCF_SN_GET_LIST_EAM
COCF_S_SN_LIST_FLAT
MATNR, EMATNR, RM_MATNR
COCF_SN_GET_LIST_PP
COCF_S_SN_LIST_FLAT
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 740
29.7 S4TWL - Computer Aided Processing Planning (CAP)
Application Components:PP-BD-CAP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268114
S4TWL - Computer Aided Processing
Planning (CAP)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Context
Standard value calculation with "Computer Aided Process Planning" CAPP is intended to
compute standard values and processing durations for production operations based on
work center or product properties. CAPP allows to define formulas, methods, and
procedures to this end.
In general standard values can be determined in several ways:
Estimating
Polling, sampling, and statistical procedures
Time and motion study (REFA in Germany)
Methods-time measurement MTM
Period time sheets
Standard value calculation with CAPP can be used to compute standard values depending
on variables, which can be material attributes, routing attributes, or manually entered
variables.
CAPP has been used to adjust standard values to the variant configuration of the
manufactured material.
CAPP has been used to add work center or standard text specific surcharges.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 741
CAPP has been used to multiply standard values for duration with a season factor.
CAPP has been used to multiply standard values with product dimensions.
The example given in various documents is the following:
MachineTime = NumberOfDrillings * DrillDepth / DrillSpeed.
Obviously parameters like NumberOfDrillings or DrillDepth are neither material nor
routing attributes. Therefore, all parameters would have to be entered manually during
production order creation.
Description
In SAP S/4HANA CAPP is available, but defined as "Functionality Deprecated".
Functional equivalent is not available.
Required and Recommended Action
You can continue to use CAPP after migrating to SAP S/4HANA.
Future Direction
CAPP formulas can contain variables, which must by specified by the user. The classic
production order UI prompts the user to specify such variables. In future releases SAP
intends to provide more user-friendly Fiori UIs for production orders. When using Fiori-
UIs the backend cannot prompt the user to enter data. CAPP cannot be supported in
combination with FIORI production order UIs.
S/4HANA processes focus on automatic conversion of planned orders into production
orders. CAPP variables cannot be entered during automatic planned order conversion.
In S/4HANA Manufacturing for Production Engineering and Operations PEO, routing
operations are detailled by operation activities explaining to production operators the
work that has to be done in more detail. All operation activities of one operation are
produced without interruption by other operations in the same work center and are
subject to the same wage group, business process, and incentive wage policy. Therefore
scheduling and costing will still be on operation level but standard value calculation
could refer to operation activity data rather than CAPP data. The total duration of an
operation for example is the sum of the durations of its operation activities.
SAP advocates open standards. Open standards for estimating standard values are time
studies, MTM, REFA, and others. To calculate standard times using one of the
established methods reach out to one of the following SAP partners:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 742
https://www.dmc-group.com/dmc-ortim/produkte/arbeitsplanung/capp-knowledge
https://mtm.org/software/mtm-software
https://refa-consulting.de/refa-software
Other Terms
CE11. CE12, CE13, CE21, CE22, CE23, CE31, CE32, CE33, CE41
29.8 S4TWL - ABAP-List-Based PI-Sheets
Application Components:PP-PI-PMA-MGT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268116
S4TWL - ABAP-List-Based PI-Sheets
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Starting with R/3 4.6 C the previously 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).
The functionality of the ABAP-list-based PI sheets has been partly deactivated and
underlying code is only partially available in SAP S/4HANA on-premise. ABAP-list-
based process instruction sheets will be carved out fully in a future release.
You can use browser-based PI sheets in SAP S/4HANA, on-premise edition for the time
being.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 743
New capabilities for PI sheets will be offered as part of SAP Digital Manufacturing
Cloud as the functionality of control recipes and process instruction in S/4HANA is not
considered as future technology.
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-list-
based PI sheets) have to be replaced with 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. No effects on
business processes are expected.
Transactions CO56 and CO58 have been deactivated in SAP S/4HANA, on-premise
edition.
Required and Recommended Action(s)
Start exchanging control recipe destinations of type 1 (ABAP-list-based PI sheets) with
control recipes of type 4 (Browser-based PI sheets). 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
For mid- to long-term planning consider new capabilities for PI sheets in SAP Digital
Manufacturing Cloud.
29.9 S4TWL - ANSI/ISA S95 Interface
Application Components:LO-S95
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268117
S4TWL - ANSI/ISA S95 Interface
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 744
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Usage of the ANSI /ISA S95 interface is not possible in S/4HANA. Use MES Integration
or the POI Interface instead.
Business Process related information
Usage of the ANSI/ISA S95 interface is not possible 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).
29.10S4TWL - PP-MRP - Subcontracting
Application Components:PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268044
S4TWL - PP-MRP - Subcontracting
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Master data maintenance has been simplified and offers the following benefits:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 745
Provide the sophisticated planning functionality for subcontracting components using
subcontracting MRP area without the necessaty to maintain appropriate material
master data
Reduction of modeling alternatives for the planning and evaluation processes for the
procurement of subcontracting components
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 of Simplification
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:
Separate planning of every subcontractor is possible without having to create an
MRP-area-specific 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 746
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
29.11S4TWL - Electronic Records
Application Components:LO-ELR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268131
S4TWL - Electronic Records
Symptom
You plan a system conversion from SAP ERP to SAP S/4HANA. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Electronic Records (LO-ELR) is not considered as future technology and therefore part of
the SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date (end of usage right) and links to
further information please refer to SAP note 2269324 Compatibility Scope Matrix for
SAP S/4HANA. You can find the the respective scope item under item ID 447 in the
attached document with Compatibility Scope matrix details.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 747
Electronic Records (LO-ELR) provide tools for evaluation of the logs that can be written
for database table entry changes. 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 (e.g. production of active ingredients, pharmaceutical products).
Audit Trail (BC-SRV-ASF-AT) as part of SAP Information Lifecycle Managements
(ILM) in software component SAP_BASIS is the functional successor of Electronic
Records (LO-ELR). In addition to the functionality of the Electronic Records, 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
Audit Trail provides migration report AUT_MIGRATE_ENHAT_DB_DATA to migrate
the configuration of Electronic Records to the successor feature Audit Trail. For details
please see note 1425152.
Electronic Records development objects which are part of Compatibility Scope are
located in package ENHAT.
Business Process related information
No changes to business processes; no changes to entries of database table DBTABLOG
Transactions
AUT01 Configuration of Logging
AUT02 Configuration of Navigation Help
AUT03 Display Configuration
AUT04 Configuration of Long Text Logs
AUT05 Deletion of Long Texts
AUT10 Evaluation of Audit Trail
are still available in SAP S/4HANA as Compatibility Scope.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 748
Required and Recommended Action(s)
Transfer the configuration/customizing settings using SAP report
AUT_MIGRATE_ENHAT_DB_DATA in SAP ERP before transforming/migrating to
SAP S/4HANA.
Custom Code Check / Adaption
After migration from Electronic Records to new Audit Trail solution check your custom
code for usage of Electronic Records development objects, which are belonging to
compatibility scope and clean-up your custom code. The below (incomplete) list is an
entry point for the analysis of your custom code. Make sure that with end of support of
the compatibility scope no data is saved (insert/update) in Electronic Records database
tables with any custom code.
Transactions (no call or clone in custom code)
AUT01 Configuration of Logging
AUT02 Configuration of Navigation Help
AUT03 Display Configuration
AUT04 Configuration of Long Text Logs
AUT05 Deletion of Long Texts
AUT10 Evaluation of Audit Trail
Database tables (no save of data through custom code)
AUT_ARCH_HIST History for Archiving of Long Text Logs
AUT_STXL SAPscript Text File Lines: Dummy Table for Audit Trails
AUT_STXH_ARCH Buffer and Conversion Table for Archiving
AUT_STXL_ARCH Buffer and Conversion Table for Archiving
AUTDELTTXID Long Text Objects Not To Be Logged on DBTABLOG
AUTDTELLOG Customizing for Change Document Creation
AUTDTELLOGT Text Table for Customizing of Change Document Creation
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 749
AUTTABLOG Customizing for Table Logging
AUTTABLOGT Text Table for Customizing of Table Logging
AUTTRANSLOG Customizing, Assignment of Transaction/Objects via AUT02
Authorization object
C_AUT_TCD
BAdI's
BADI_AUT_ARCHIVE Intern: Badi for Archive Evaluation of Audit Trail - AUT10
BADI_AUT_CONV AUT10: BAdI for Value and Key Conversion
Programs (no call or clone in custom code)
AUT_ARCH01 Archiving of Long Text Logs: Write Program
AUT_ARCH02 Archiving of Long Text Logs: Delete Program
AUT_ARCH03 Archiving of Long Text Logs: Reload Program
AUT_ARCHV Archiving of Long Text Logs: Preprocessing Program
AUT_ARCH_UNDO Archiving of Long Text Logs: Deletion of Last Preprocessing
AUT_CUST01 Customizing tool for AUDIT TRAILs
AUT_CUST_DEL04
AUT_DEL Deletion of Long Text Logs
AUT_DEL05 Deleting of long texts
AUT_REP10 Reporting Tool for AUDIT TRAILs
Other Terms
Transactions AUT01, AUT02, AUT03, AUT04, AUT05, AUT10; Authorization object
C_AUT_TCD, BAdI's BADI_AUT_ARCHIVE, BADI_AUT_CONV AUT10
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 750
29.12S4TWL - Downtimes Functionality
Application Components:PP-PI-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271203
S4TWL - Downtimes Functionality
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Business Process related information
No changes on business processes expected
Required and Recommended Action(s)
None
29.13S4TWL - MiniApps PP-PI
Application Components:PP-PI-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271204
S4TWL - MiniApps PP-PI
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 751
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 and has been removed in SAP
S4HANA. The idea of the MiniApps have been used to implement the Fiori launch pad
and the monitor material shortage app.
Business Process related information
No changes on business processes expected
Required and Recommended Action(s)
None
29.14S4TWL - Process Data Evaluation (PP-PI-PEV)
Application Components:PP-PI-PEV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270267
S4TWL - Process Data Evaluation
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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, but not considered as future technology.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 752
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Check SAP note 511488 for alternative approach
29.15S4TWL - Campaign Weighing and Dispensing
Application Components:PP-PI-PMA-CWD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270200
S4TWL - Campaign Weighing and
Dispensing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The functionality of Campaign Weighing and Dispensing has never been released for
productive use. The corresponding xMII content is not available anymore.
The functionality is still available in SAP S/4HANA, on-premise edition, but not
considered as future technology.
Business Process related information
No changes to business processes. The Weigh&Dispense solution of the SAP PP-PI
consulting organization shall be considered for weigh&dispense processes.
Required and Recommended Action(s)
None
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 753
Transaction CMATRANGE
29.16S4TWL - Production Campaign (ERP)
Application Components:PP-PI-PCM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270216
S4TWL - Production Campaign (ERP)
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Production Campaign functionality groups planned orders and process orders to produce
a certain amount of a material over a certain period of time. This is done in an continuous
sequence on one production line to optimize costs regarding production setup, cleaning,
and teardown processes as well as storage costs.
SAP plans to provide a new Fiori based app/UI as a SAP S/4HANA adapted solution in a
future release for the Production Campaign functionality.
The legacy SAP ERP functionality of Production Campaign is part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, production campaign can be found under the ID 457.
This note will be updated as soon as more details on the new Fiori UX are known.
Business Process related information
Backend transactions PCA1, PCA, PCA3 and PCCO are still available.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 754
No action is required as the SAP ERP Production Campaign functionality can still be
used as compatibility pack scope. Please check for updates and once the SAP S/4HANA
adapted solution with Fiori UX is available, please make use to the new Production
Campaign Fiori app(s). No data migration efforts are expected when switching to the new
Fiori apps.
Other Terms
Package COPC; Transactions PCA1, PCA2, PCA3, PCCO
29.17S4TWL - Electronic Batch Record
Application Components:PP-PI-PDO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270218
S4TWL - Electronic Batch Record
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
The functionality of Electronic Batch Record (EBR) is required by customers who
operate in a regulated environment (e.g. production of active ingredients, pharmaceutical
products).
Batch records contain all quality-relevant data on the production of a batch. The
structure, contents, and processing of batch records comply with international standards
defined in the guidelines on Good Manufacturing Practices (GMP).
The content of the EBR is stored in optical archives (using SAP ArchiveLink
technology). EBR Content is revisited during external audits. The EBR content has to be
kept for several years dependent on the applicable regulatory requirements.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 755
Electronic Batch Record (EBR) is still available in SAP S/4HANA, but not considered as
future technology and therefore part of the SAP S/4HANA compatibility scope, which
comes with limited usage rights. For more details on the compatibility scope and its
expiry date (end of usage right) and links to further information please refer to SAP note
2269324 Compatibility Scope Matrix for SAP S/4HANA. You can find the respective
scope item under item ID 446 in the attached document with Compatibility Scope matrix
details.
New capabilities in this area will be offered as part of SAP Digital Manufacturing Cloud.
Please check https://www.sap.com/products/digital-manufacturing-cloud.html
A functional successor is not yet available. Please check the SAP Road Map for SAP
Digital Manufacturing Cloud for updates.
Access (read-only) to EBR content in the optical archive (transaction OAAD - business
object BUS3053001) will still be possible after the end date of the usage right for scope
item 446 to ensure that data records are kept and accessible throughout the required
retention periods according to regulatory requirements.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Before upgrading to SAP S/4HANA it is recommended that you complete all open
approval procedures for electronic batch records.
Move to a successor solution timely before reaching the end date of the usage right.
Custom Code Check / Adaption
When moving to a successor solution, check your custom code for usage of Electronic
Batch Record development objects, which are belonging to the compatibility scope and
clean-up your custom code. The below (incomplete) list is an entry point for the analysis
of your custom code. Make sure that with end of support of the compatibility scope no
data is saved (insert or update) in Electronic Batch Record database tables with any
custom code.
Transaction (no call or clone in custom code)
COEBR Batch Record
Database tables (no save of data through custom code)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 756
MCHP Batch Record for a Batch
MCHPV Batch Record: Versions
MCHPVS Batch Record: Shadow Table for Link to Archive
MCHPVT Batch Record: Long Text for Version
VBP_APPR_DS_META Approval Batch Record: Meta Data (DS Tool)
BAdI's with interface methods
BADI_VBP_CUST_EXT Batch Record: Customer-Specific Enhancements Using a
BAdI
Interface IF_BADI_VBP_CUST_EXT
ADD_AL_CUST_CONT Adds Archived Customer-Specific Content
ADD_EBR_HEAD_VERS_TO_BUF Adds Data of EBR Header and Version
to Buffer
ARCHIVE_CUST_CONTENT Archives Customer-Specific Contents
BUILD_AL_CUST_EXT_NODE Generates Folder Node for Archived
Customer-Specific Objects
BUILD_CUST_EXT_NODE Generates Folder Node for Customer-Specific
Objects
CHECK_CUST_OBJ_PART_ARC Archiving: Checks for Partially Archived
Cust.-Specific Objs
CHECK_CUST_STATUS_FOR_ARC Archiving: Status Check for
Customer-Specific Objects
CHECK_EBR_CUST_EXT_ALLOWED Checks if Customer-Specific EBR
Enhancements Are Permitted
CLEAR_CUST_CONT_BUFFER Deletes Buffer of Customer-Specific
Object Data
CREATE_CUST_CMENU Generates Context Menu for Nodes of Cust.-
Specific Content
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 757
FILL_CUST_CONT_BUFFER Fills Buffer for Customer-Specific Content
GET_AL_CONN_DATA Provides Connection Data for ArchiveLink Files
GET_AL_CUST_CONTENT Provides Archived Customer-Specific Content
GET_CUST_CONTENT Provides Customer-Specific Content
GET_DOC_TYPES_FOR_ATT Provides Document Types for EBR
Attachments
GET_EBR_ID_BY_CUST_CONT Provides EBR ID for Current Node
GET_FCODE Provides Function Code for Current Node
GET_RELATED_CUST_STRUCT Provides Structure Name for Nodes of
Cust.-Specific Content
HANDLE_CUST_FCODE Processing of Customer-Specific Function Codes
SET_CUST_STATUS Sets Status for Customer-Specific Objects
SET_CUST_STATUS_AFTER_ARC Sets Follow-On Status f. Cust.-Specific
Objs After Archiving
BADI_VBP_DEVI_EXT Extensions for Deviation analysis
Interface IF_BADI_VBP_DEVI_EXT
CHANGE_DEVI_SCREEN_STATUS Changes GUI-Status of Deviation
Analysis
CHECK_EBR_DEVI_EXT_ALLOWED Check if Extensions of Deviation
Check are Permitted
FORCE_ARCHIVING_DEVI_DOC Forces Archiving of Deviation Analysis
(in Dialog)
HIDE_RADIO_BUTTON_CHOICE Hide Radiobutton Selection (Save
Deviation Analysis)
NEW_DEVI_CHECK_ON_APPROVAL Check during Approval: Repeated
Deviation Check Necessary?
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 758
BADI_VBP_DS_EBR_APPROVAL Batch Record: BAdI for DS Tool
Signatures (Approval EBR Version)
Interface IF_BADI_VBP_DS_EBR_APPROVAL
CHECK_DS_EBR_APPROVAL_ALLOWED Checks Approval for DS Tool
Signature (Version Approval)
IS_SIGNER_ID_CHANGEABLE Is SAP User ID of Signer Changeable?
BADI_VBP_LOT_EXT Batch Record: Enhancements for Inspection Lot Processing
Us
Interface IF_BADI_VBP_LOT_EXT
GET_LOTS_FOR_VERS Provides Inspection Lots for an EBR Version
CHECK_EBR_LOT_EXT_ALLOWED Checks if EBR Inspection Lot
Enhancements Are Permitted
CHECK_LOT_STATUS_USAGE_DEC Check of 'Usage Decision Made'
Status
BADI_VBP_ORD_EXT Batch Record: Enhancements for Orders Using a BAdI
Interface IF_BADI_VBP_ORD_EXT
CHECK_EBR_ORD_EXT_ALLOWED Are Order Enhancements Permitted?
CHECK_ORD_CAT_USAGE Checks if Order Category Is to Be Used for
EBR
DISPLAY_ORDER_DATA Executes Transaction for Displaying Order Data
EXCHANGE_MSG Exchange of Message Contents
EXCHANGE_TEXT_SYM Exchange of Text Symbol Contents
GET_ORDER_CAT Provides Order Category for Order Type and Plant
GET_SUPPORTED_ORD_CAT Provides Supported Order Categories
SET_ORD_CAT_CONN Sets Order Category for ArchiveLink Link Data
BADI_VBP_PERS_EXT Batch Record: Personalization Enhancements per BAdI
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 759
Interface IF_BADI_VBP_PERS_EXT
ADD_MAT_TO_NO_PROF_BUF Materials without Overall Profile: Add
Material
CHECK_MAT_HAS_NO_PROF Check that Material has no Overall Profile
SET_ALT_LAYOUT_PROFILE Set Alternative Overall Profile for Material
Forms
PPPI_EBR_USER storage of customer-specific data during archiving of the batch
record
Document Types for the Object TypeBUS3053001
PIEBRCONTE Batch record: table of contents
PIEBRVERS Batch record: version data
PIEBRDEVIA Batch record: deviations
PIEBRORDER Batch record: process order
PIEBRMATLI Batch record: material list
PIEBRPRLOS Batch record: inspection lot
PIEBRPOC Batch record: browser-based PI sheet
PIEBRSHEET Batch record: ABAP list-based PI sheet
PIEBRMESSA Batch record: process messages
PIEBRUSER Batch record: user-defined data
EBR_DOC Batch record attachment: DOC
EBR_RTF Batch record attachment: RTF
EBR_PDF Batch record attachment: PDF
User-defined Any external file as attachment
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 760
Other Terms
GMP-compliant production, transaction COEBR, business object BUS3053001, form
PPPI_EBR_USER, package VBP
29.18S4TWL - Process Messages
Application Components:PP-PI-PMA-MSG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270231
S4TWL - Process Messages
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
The usage of process messages in conjunction with browser-based PI sheets and work
instructions is part of the compatibility scope, which comes with limited usage rights. For
more details on the compatibility scope and it’s expiry date and links to further
information please refer to SAP note 2269324 Compatibility Scope Matrix for SAP
S/4HANA. You can find the the respective scope item under item ID 455 in the attached
document with Compatibility Scope matrix details. This also applies to the maintenance
of the corresponding process instruction content (characteristics-based process
instructions and XStepbased process instructions).
The usage of process messages in conjunction with linking process control systems or
other external systems is possible using Manufacturing Execution Connect (classic) and
is not part of the compatibility scope. This also applies to the maintenance of the
corresponding process instruction content (characteristics-based process instructions and
XStepbased process instructions). For more information, see SAP S/4HANA Feature
Scope Description or note 3035649 FAQ : Manufacturing Execution Connect (classic).
New Process Order integration capabilities will be offered with new SOAP and oData
APIs.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 761
Process Orders Confirmations can be received from a MES, e.g. to SAP Digital
Manufacturing Cloud, with new oData APIs.
Please check the SAP API Business Hub for details: https://api.sap.com
Business Process related information
No influence on business processes expected as long as you continue to use process
messages.
New Process/Work Instruction capabilities will be offered as part of SAP Digital
Manufacturing Cloud. Please check https://www.sap.com/products/digital-
manufacturing-cloud.html
For timelines please refer to the official roadmap for SAP Digital Manufacturing Cloud:
https://roadmaps.sap.com
Of course it is also possible to use the built-in features of SAP S/4HANA for production
execution like transactions CORK, CORZ, COR6N and the apps for the production
operator role SAP_BR_PRODN_OPTR_PROC.
Required and Recommended Action(s)
As process messages can be used until the expiry date of the compatibility pack license,
it’s up to each customer to decide, when (with which of the coming
SAP S/4HANA releases) they want to migrate to the designated alternative functionality.
Though the decision, at which point in time this will be done, should be taken early in
advance in order to plan accordingly for the migration efforts.
Immediate action is not required.
Further information
The usage of control recipes/control instructions (PP-PI-PMA-RCP), process
messages (PP-PI-PMA-MSG) and Material Identification / Reconciliation (PP-PI-
MIR) in conjunction with the PI-PCS interface is further supported in SAP
S/4HANA after end of use rights for the compatibility scope through the SAP
S/4HANA application Manufacturing Execution Connect (classic). This applies
also to the maintenance of the corresponding process instruction content
(characteristics-based process instructions and XStep-based process instructions
[PP-PI-PMA-XS])
The control recipe destination types 2 (Download to external system, initiated by
SAP system) and 3 (Download to external system, initiated by external system)
are used together with the PI-PCS interface and are part of Manufacturing
Execution Connect (classic).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 762
The PI-PCS interface is part of application component PP-PI-PMA and is used to
integrate external 3
rd
party manufacturing execution systems and other external systems.
The usage of control recipes/control instructions (PP-PI-PMA-RCP), process
messages (PP-PI-PMA-RCP) and Material Identification / Reconciliation (PP-PI-
MIR) in conjunction with browser-based PI-sheets and work instructions (PP-PI-
PMA-PMC ) is part of the compatibility scope and is not further supported after
the end of use rights for the compatibility scope items 444 (Control
recipes/instructions), 454 (Browser-based PI-sheet), 455 (Process messages) and
453 (Material Identification / Reconciliation). This applies also to the
maintenance of the corresponding process instruction content (characteristics-
based process instructions and XStep-based process instructions [PP-PI-PMA-
XS]).
The control recipe destination type 4 (Transfer to a browser-based PI sheet) is used
together with the browser-based PI-Sheet and work instructions.
The proposed alternative application for browser-based PI-Sheet is the Production
Operator Dashboard, which is part of the SAP Digital Manufacturing Cloud.
The support of ABAP list-based PI-sheets (PP-PI-PMA-MGT - control recipe
destination type 1- Transfer to an ABAP list-based PI sheet) has already ended.
(see note: 2268116 - S4TWL - ABAP-List-Based PI-Sheets - SAP ONE Support
Launchpad )
Custom Code Check / Adaption
After switching from Browser-based PI sheets to a sucessor solution in SAP DMC
Digital Manufacturing Cloud check your custom code for usage of process messages
which transfer data from browser-based PI sheets to whatever receiver and clean-up your
custom code that make use of process messages.
Make sure that with end of support of the compatibility scope no data is transferred from
Browser-based Process Instruction sheets throught process messages with any custom
code.
Please also check your custom code in conjunction with browser-based PI
sheets/electronic Work Instructions according to note 2268070.
Other Terms
Process Management; PI Sheet; Transactions CO54, CO54XT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 763
29.19S4TWL - Control Recipes/Instructions
Application Components:PP-PI-PMA-RCP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270233
S4TWL - Control Recipes/Instructions
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
The usage of control recipes/control instructions in conjunction with browser-based PI
sheets and work instructions is part of the SAP S/4HANA compatibility scope, which
comes with limited usage rights. This also applies to the maintenance of the
corresponding process instruction content (characteristics-based process instructions and
XStep-based process instructions). For more details on the compatibility scope and it’s
expiry date (end of usage right) and links to further information please refer to SAP note
2269324 - Compatibility Scope Matrix for SAP S/4HANA. You can find the the
respective scope item under item ID 444 in the attached document with Compatibility
Scope matrix details.
The usage of control recipes/control instructions in conjunction with linking process
control systems and other external systems is possible using Manufacturing Execution
Connect (classic) and is not part of the compatibility scope using Manufacturing
Execution Connect (Classic)), see SAP S/4HANA Feature Scope Description or
note 3035649 FAQ : Manufacturing Execution Connect (classic). This also applies to the
maintenance of the corresponding process instruction content (characteristics-based
process instructions and XStepbased process instructions).
New Process Order integration capabilities will be offered with new SOAP and oData
APIs.
Process Orders can be send to a MES, e.g. to SAP Digital Manufacturing Cloud, with
new SOAP APIs.
Please check the SAP API Business Hub for details: https://api.sap.com
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 764
Business Process related information
No influence on business processes expected as long as you continue to use Control
Recipes/Instructions.
New Process/Control Instruction capabilities will be offered as part of SAP Digital
Manufacturing Cloud. Please check https://www.sap.com/products/digital-
manufacturing-cloud.html
For timelines please check the official roadmap for SAP Digital Manufacturing
Cloud (https://roadmaps.sap.com).
Of course it is also possible to use the built-in features of SAP S/4HANA for production
execution like for example transactions CORK, COR6N, CORZ and the apps for the
production operator role SAP_BR_PRODN_OPTR_PROC.
Required and Recommended Action(s)
As Control Recipes/Instructions can be used until the expiry date of the compatibility
pack license, it’s up to each customer to decide, when (with which of the coming
SAP S/4HANA releases) they want to migrate to the designated alternative functionality.
Though the decision, at which point in time this will be done, should be taken early in
advance in order to plan accordingly for the migration efforts.
Immediate action is not required.
Further information
The usage of Control Recipes/Control Instructions (PP-PI-PMA-RCP), Process
Messages (PP-PI-PMA-MSG) and Material Identification / Reconciliation (PP-PI-
MIR) in conjunction with the PI-PCS interface is further supported in SAP
S/4HANA after end of use rights for the compatibility scope through the SAP
S/4HANA Product Manufacturing Execution Connect (classic). This applies also
to the maintenance of the corresponding process instruction content
(characteristics-based process instructions and XStep-based process instructions
[PP-PI-PMA-XS])
The control recipe destination types 2 (Download to external system, initiated by
SAP system) and 3 (Download to external system, initiated by external system)
are used together with the PI-PCS interface and are part of Manufacturing
Execution Connect (classic).
The PI-PCS interface is part of application component PP-PI-PMA and is used to
integrate external 3
rd
party manufacturing execution systems and other external systems.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 765
The usage of control recipes/control instructions (PP-PI-PMA-RCP), process
messages (PP-PI-PMA-RCP) and Material Identification / Reconciliation (PP-PI-
MIR) in conjunction with browser-based PI-sheets and work instructions (PP-PI-
PMA-PMC ) is part of the compatibility scope and is not further supported after
the end of use rights for the compatibility scope items 444 (Control
recipes/instructions), 454 (Browser-based PI-sheet), 455 (Process messages) and
453 (Material Identification / Reconciliation). This applies also to the
maintenance of the corresponding process instruction content (characteristics-
based process instructions and XStep-based process instructions [PP-PI-PMA-
XS]).
The control recipe destination type 4 (Transfer to a browser-based PI sheet) is used
together with the browser-based PI-Sheet and work instructions.
The proposed alternative application for browser-based PI-Sheet is the Production
Operator Dashboard, which is part of the SAP Digital Manufacturing Cloud.
The support of ABAP list-based PI-sheets (PP-PI-PMA-MGT - control recipe
destination type 1- Transfer to an ABAP list-based PI sheet) has already ended.
(see note: 2268116 - S4TWL - ABAP-List-Based PI-Sheets)
Custom Code Check / Adaption
After switching from Browser-based PI sheets to a sucessor solution in SAP DMC
Digital Manufacturing Cloud check your custom code for usage of Control Recipes or
Control Instructions with destination type 4 (Transfer to browser-based PI sheet)
and clean-up your custom code. Control Recipe/Instruction destination type 4 is a fixed
value of SAP domain COMTY which is the elemtary type of Data element COMTY.
Instead of using Control recipes/control instructions use the WebService (SOAP
API) Manufacturing Order - Send to send order data to an external (e.g. Manufacturing
Exexcution System) system.
Make sure that with end of support of the compatibility scope no data is saved (insert or
update) through Browser-based Process Instruction sheets with any custom code.
Please also check your custom code in conjunction with browser-based PI
sheets/electronic Work Instructions according to note 2268070.
Other Terms
Process Management; PI Sheet; Transactons CO53, CO53XT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 766
29.20S4TWL - Storage Location MRP
Application Components:PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268045
S4TWL - Storage Location MRP
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Master data maintenance has been simplified and offers the following benefits:
Reduction of modeling alternatives for similar function of the MRP planning on
storage location level
Support of a single modeling approach that provides the most sophisticated features
and funtions for planning on storage location level
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 767
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 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
SAP Note: 2216528
Custom Code related information
SAP Note: 2227579
See SAP Note 2466264 for S/4 conversion with storage location MRP for a Retail
system.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 768
29.21S4TWL - Process Operator Cockpits
Application Components:PP-PI-PMA-PMC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270235
S4TWL - Process Operator Cockpits
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Process Operator Cockpit (POC) is still available in SAP S/4HANA, but not considered
as future technology and therefore part of the SAP S/4HANA compatibility scope, which
comes with limited usage rights. For more details on the compatibility scope and it’s
expiry date (end of usage right) and links to further information please refer to SAP note
2269324 Compatibility Scope Matrix for SAP S/4HANA. You can find the the respective
scope item under item ID 456 in the attached document with Compatibility Scope matrix
details.
The Process Operator Cockpits, similar as the browser-based PI Sheets (see note 2268070
S4TWL - S4TWL - Browser-based Process Instruction Sheets/Electronic Work
Instructions), require SAP-GUI for Windows as UI technology and therefore are
dependent on MS Internet Explorer (technical prerequisite for HTML viewer).
SAP Digital Manufacturing Cloud (DMC) will provide similar functionality as Process
Operator Cockpits in future. For example, the Production Operator Dashboard (POD),
which is based on standard SAP UI5 and SAP Fiori technology, will allow API calls into
SAP S/4HANA and other systems. The DMC POD Designer will offer flexible and
customer individual configuration of the worker UI. DMC for Insights and DMC
Resource Orchestration will provide dashboards and production monitoring based on
SAP standard and custom specific manufacturing key figures. Additionally, DMC will
provide an extensibility framework to allow customer individual solutions.
For timelines please check the official roadmap for SAP Digital Manufacturing
Cloud (https://roadmaps.sap.com).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 769
Business Process related information
It will not be possible to migrate existing process instruction based Process Operator
Cockpits (POC) into a future worker UIs in SAP DMC.
Required and Recommended Action(s)
You can continue to use your existing cockpits, but not invest anymore into new cockpits.
Consider to evaluate the possibilities of SAP DMC instead.
Custom Code Check / Adaption
Custom enhancements and modifications of POCs in SAP S/4HANA will not work for
successor UIs/PODs in SAP DMC.
Due to the tight integration of Production Operator Cockpit and browser-based Process
Instruction Sheets/Electronic Work Instructions (see note 2268070 S4TWL - Browser-
based Process Instruction Sheets/Electronic Work Instructions) functionality please
perform a combined custom code check.
After switching from process instruction based POC's to a successor solution in SAP
DMC Digital Manufacturing Cloud check your custom code in context of POCs which
transfer data to whatever receiver and clean-up your custom code that makes use of POC
functionality. The below (incomplete) list is an entry point for the analysis of your
custom code. Make sure that with end of support of the compatibility scope item no data
is transferred from a POC with any custom code and that no custom code initiates save of
data (create/update) to respective database tables.
Transactions
COPOC Process Manufacturing Cockpit
O06C Define Process Manufacturing Cockpit
O06S Define Process Manufacturing Cockpit
Database tables (no save of data through custom code)
POC_DB_APPL_STEP Domain Model: Application Steps
POC_DB_ARC_CONN Optical Archiving: Link Data (ArchiveLink)
POC_DB_C_COMMAND Domain Model: Command Collection
POC_DB_C_COMMENT Domain Model: Comment Collection
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 770
POC_DB_C_DEVIAT Domain Model: Deviation Collection
POC_DB_C_DEVVAR Domain model: Collection for variable setting (deviation)
POC_DB_C_METADAT Domain Model: Local Value Collection
POC_DB_C_OPER Domain Model: Operation Collection
POC_DB_C_PARTIT Domain Model: Partition Element Collection
POC_DB_C_PREDEC Domain Model: Predecessor Table
POC_DB_C_SERVICE Domain Model: Service Operation Collection
POC_DB_C_STEP Domain Model: Step Collection
POC_DB_C_SYTABLE Domain Model: Variable Collection (Symbol Table)
POC_DB_C_TRIGGER Domain Model: Trigger Collection
POC_DB_C_VALUE Domain Model: Value Container Collection
POC_DB_COMMAND Domain Model: Table for Step Commands
POC_DB_CONF_REQ Domain Model: Table for Signature Requests
POC_DB_DATA_REQ Domain Model: Table for Data Requests
POC_DB_DEV_SIGN Signature Key: Metadata Signature Process Step
POC_DB_DOMAIN Domain Model: Database Table for Domains
POC_DB_EVT_SIGN Signature Keys: Metadata for Event Log
POC_DB_EXEC_REQ Domain Model: Table for Execution Request
POC_DB_EXEC_STRA Domain Model: Table for Execution Strategies
POC_DB_MESS_REQ Domain Model: Table for Message Requests
POC_DB_OPERATION Domain Model: Table for Operations
POC_DB_PARTITION Domain Model: Partition
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 771
POC_DB_PROC_STEP Domain Model: Table for Process Steps
POC_DB_PROTOCOL Domain Model: Event Log for Process Steps
POC_DB_REAS_SIGN Signature Key: Meta Data Reason for Value Change
POC_DB_SIG_HANDL Domain Model: Signature Handler
POC_DB_SIGNATURE Domain Model: Signature
POC_DB_STEP Domain Model: Table for Step Basic Data
POC_DB_STEP_SIGN Signature Key: Metadata Signature Process Step
POC_DB_TRIG_PROT Logging: Trigger for Event in Domain Model
POC_DB_VALUE Domain Model: DB Table for Value Container
Programs/Reports (no call or clone in custom code)
RCOPOC_START Start Process Manufacturing Cockpit
RCOPOC_COCKPIT_CLIENT_COPY Copy Process Manufacturing Cockpits
Between Clients
RCOPOC_COCKPIT_DELETE Delete Process Manufacturing Cockpit
RCOPOC_COCKPIT_GENERATE Generate Process Manufacturing Cockpit
RCOPOC_COCKPIT_PLANT_COPY Copy Process Manufacturing Cockpits
Between Plants
Function Modules (no call or clone in custom code)
POC_GET_PISHEET_DATA_XML NOTRANSL: Holen des Daten XML für
Herstellanweisung
POC_PRINT_SHEET_IN_EBR_STYLE NOTRANSL: Anzeige der
Herstellanweisung im Druckbildlayout des EBR
POC_SHOW_PMA_CONT_ARCH_LAYOUT Display PI Sheet/Work Instruction in
Archiving Layout
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 772
BAdI's with interface methods (check for custom implementation)
BADI_CMX_POC_ASYNC_SIGN Handle XML change error
IF_BADI_CMX_POC_ASYNC_SIGN~CHANGE_ABORT_MESSAGE
BADI_CMX_POC_DYN_SIGN_STRAT Enhancements for Dynamic Selection of
Signature Strategies
Interface methods IF_BADI_CMX_POC_DYN_SIGN_STRAT~
ADJUST_PI_CHECK_MESSAGE Check Process Instruction: Set Suited
Message Texts
CHECK_DYN_SIGN_STRAT_ALLOWED Check that Dynamic Signature
Strategy Function is Allowed
EXECUTE_INSTR_SEMANTIC_CHECK Executes Additional Checks
during Semantic Check
EXECUTE_XS_INSTR_CONTENT_CHECK XStep-based Process
Instruction: Executes Additional Checks
GET_CUST_DOMAIN_SUBCLASS Value Search: Returns Information on
Characteristic & Subcl.
HANDLE_FAILED_VALUE_SEARCH Search for Selected Signature
Strategy: Error Handling
RESET_STRAT_TO_PLACEHOLDER Reset Signature Strategy to
Placeholder Value
BADI_CMX_POC_REASON_VAL_CHG Processing of Reasons for Value Changes
Interface methods IF_BADI_CMX_POC_REASON_VAL_CHG~
CHECK_COMMENT_OF_REASON Checks the Entered Comment of
Reason for Value Change
CHECK_REASON_VAL_CHG_ALLOWED Checks that Processing of
Reasons is Allowed
Enhancement Spots (check for custom implementation)
ES_RCOPOC_WKLT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 773
ES_SSAPLCMX_PII_CP_SRV_DST_PMC Enhancement PI Interpreter (Name of
Destination)
Other Terms
POC; Process Manufacturing Cockpit; Transactions COPOC, O06C, O06S;
Packages COPOC, CMX_POC
29.22S4TWL - Material Identification/Reconciliation
Application Components:PP-PI-MIR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270236
S4TWL - Material
Identification/Reconciliation
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
The functionality of Material Identification and Material Reconciliation in conjunction
with the browser-based PI sheets is part of the SAP S/4HANA compatibility scope,
which comes with limited usage rights. For more details on the compatibility scope and
it’s expiry date (end of usage right) and links to further information please refer to SAP
note 2269324 - Compatibility Scope Matrix for SAP S/4HANA. You can find the the
respective scope item under item ID 453 in the attached document with Compatibility
Scope matrix details.
The usage of material identification/reconciliation in conjunction with linking process
control systems and other external systems is still possible using Manufacturing
Execution Connect (classic) and is not part of the compatibility scope using
Manufacturing Execution Connect (Classic), see SAP S/4HANA Feature Scope
Description or note 3035649 FAQ : Manufacturing Execution Connect (classic).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 774
A functional sucsessor is not yet available. Please check the SAP Road Map for SAP
Digital Manufacturing Cloud for updates.
Business Process related information
No influence on business processes expected.
New capabilities in this area will be offered as part of SAP Digital Manufacturing Cloud.
Please check https://www.sap.com/products/digital-manufacturing-cloud.html
For timelines please refer to the official roadmap for SAP Digital Manufacturing Cloud
on Road Map for SAP Digital Manufacturing Cloud (https://roadmaps.sap.com).
It is also possible to use the built-in features of SAP S/4HANA in the area of Production
Supply / Material Staging for handling units with transactions COPAWA and
COWBHUWA.
It is also possible to use the built-in features of SAP S/4HANA for material reconciliation
with transaction MIRCMR.
Required and Recommended Action(s)
As Material Identification and Material Reconciliation can be used until the expiry date
of the compatibility pack license, it’s up to each customer to decide, when (with which of
the coming SAP S/4HANA releases) they want to migrate to the designated alternative
functionality. Though the decision, at which point in time this will be done, should be
taken early in advance in order to plan accordingly for the migration efforts.
Immediate action is not required when converting from SAP ERP to SAP S/4HANA.
Further Information
The usage of control recipes/control instructions (PP-PI-PMA-RCP), process
messages (PP-PI-PMA-MSG) and Material Identification / Reconciliation (PP-PI-
MIR) in conjunction with the PI-PCS interface is further supported in SAP
S/4HANA after end of use rights for the compatibility scope through the SAP
S/4HANA application Manufacturing Execution Connect (classic). This applies
also to the maintenance of the corresponding process instruction content
(characteristics-based process instructions and XStep-based process instructions
[PP-PI-PMA-XS])
The control recipe destination types 2 (Download to external system, initiated by
SAP system) and 3 (Download to external system, initiated by external system)
are used together with the PI-PCS interface and are part of Manufacturing
Execution Connect (classic).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 775
The PI-PCS interface is part of application component PP-PI-PMA and is used to
integrate external 3
rd
party manufacturing execution systems and other external systems.
The usage of control recipes/control instructions (PP-PI-PMA-RCP), process
messages (PP-PI-PMA-RCP) and Material Identification / Reconciliation (PP-PI-
MIR) in conjunction with browser-based PI-sheets and work instructions (PP-PI-
PMA-PMC ) is part of the compatibility scope and is not further supported after
the end of use rights for the compatibility scope items 444 (Control
recipes/instructions), 454 (Browser-based PI-sheet), 455 (Process messages) and
453 (Material Identification / Reconciliation). This applies also to the
maintenance of the corresponding process instruction content (characteristics-
based process instructions and XStep-based process instructions [PP-PI-PMA-
XS]).
The control recipe destination type 4 (Transfer to a browser-based PI sheet) is used
together with the browser-based PI-Sheet and work instructions.
The proposed alternative application for browser-based PI-Sheet is the Production
Operator Dashboard, which is part of the SAP Digital Manufacturing Cloud.
Custom Code Check / Adaption
After switching from Browser-based PI sheets to the sucessor solution in SAP DMC
Digital Manufacturing Cloud check your custom code for usage of PI sheets in
conjunction with Material Identification and Material Reconciliation and clean-up your
custom code. The below (incomplete) list is an entry point for the analysis of your custom
code. Make sure that with end of support of the compatibility scope no data is saved
(insert or update) through Browser-based Process Instruction sheets with any custom
code.
Please also check your custom code in conjunction with browser-based PI
sheets/electronic Work Instructions according to note 2268070.
Database tables (no save of data through PI sheets)
BEREIT Material identification: staging data
HUM_KOMMI HUM Picking with Partial GI Posting
MISTATUS Status Table for Material Identification on Mat./Batch Level
Process Instruction categories (no save of data through PI sheets)
MI_HUSTG Picking for HUs
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 776
MI_HUSQU Sequence check for HUs
MI_HUCMP Identification
MI_HUCNS Separate GI posting for HU
MI_HUSTC Check completeness of picking
MI_MATBA Mat.ident. on material / batch level
RECON Material Reconciliation
Process Message categories (no save of data through PI sheets)
PI_HUCNS GI Posting for HUs
PI_HUREC Process Data Message HU Picking/Ident.
PI_HUSTG (Automatic) Material Picking
PI_MIREC Proc.Message Mat.ID. on Mat./Batch Lvl
PI_RECON Process Message for Mat. Reconciliation
PPPI characteristics (no save of data through PI sheets)
PPPI_HU_CANCELLED Reversal of GI Posting
PPPI_HU_CONS_DATE Document Date for Posting
PPPI_HU_CREATED_BY HU Created By
PPPI_HU_DEASSIGNED Assignment to Order Deleted
PPPI_HU_DISPLAY_REQUIRED_HU Display Expected HU
PPPI_HU_EXT_PACKAGING External Handling Unit ID
PPPI_HU_EXT_PACKAGING_TO_PACK External Handling Unit ID
PPPI_HU_EXT_PICKING_BIN_NO External Picking Bin
PPPI_HU_EXT_STAGING_NO External Picking Number
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 777
PPPI_HU_GET_ALLOWED_VALUES Activation of F4 help HUs
PPPI_HU_HIGHER_LEVEL_HU Higher-Level Handling Unit
PPPI_HU_IDENT_LEVEL Level of Identification
PPPI_HU_KIND_OF_COMPLETENESS Type of Completeness Check
PPPI_HU_PACKING_MATERIAL Packaging Material
PPPI_HU_POST_GOODS_ISSUE Post HU GI at Ident.
PPPI_HU_PREREQ_FOR_GOODS_ISSUE Requirement for HU GI Posting
PPPI_MI_BATCH_SPLIT Indicator for Batch Split
PPPI_MI_CHECK_FOR_START_QTY Start / Component Check
PPPI_MI_DISPLAY_MATLIST Material List Display
PPPI_MI_GET_ALLOWED_VALUES Activation of F4 Help
PPPI_MI_IDENT_LEVEL Level of Identification
PPPI_MI_INPUT_MODE Entry Type
PPPI_MI_MAT_TYPE_IN_RESER_LIST Reservation Item Selection
PPPI_MR_FORMULA Reconciliation Formula
PPPI_MR_IF_USED Reconciliation Yes/No [X=Yes]
PPPI_MR_RANGE_HIGH Reconciliation Upper Range
PPPI_MR_RANGE_LOW Reconciliation Lower Range
BAdI (no usage in PI sheets to update data)
BADI_HU_CHANGE_INPUT BAdI for changing HU input - interface
nethod IF_EX_BADI_HU_CHANGE_INPUT~CHANGE_INPUT
Programs (no usage in PI sheets to update data)
MI_HU_CONFIRM_MANUAL_STAGING Manual staging
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 778
MI_HU_HU_CONSUMPTION Material Identification: Sep. Goods Issue
MI_HU_MATERIAL_COMPLETE_CHECK Material Identification: Completeness
MI_HU_MATERIAL_SEQUENCE_CHECK Material Identification: Sequence
MI_MATERIAL_CHECK_DIALOG Programm
MI_MATERIAL_CHECK_DIALOG
PPPI_DEVI_CHECK_MR Deviations Including Material Reconciliation
VHUMI_RECONCILIATION Material Reconciliation
VMIRC_MRCHVW Batch Usage with Material Reconciliation
Function modules (no usage in PI sheets to update data)
MI_MATERIAL_CHECK_COMPLETENESS
MI_MATERIAL_CHECK_RESB
MI_MESSAGES_POST
MI_MISTATUS_GET
MI_MISTATUS_INIT
MI_MISTATUS_POST
MI_MISTATUS_POST_UPDATE_TASK
MI_MISTATUS_SET
COMI_CHECK_PICKING
COMI_CONFIRM_AUTO_STAGING
COMI_CONFIRM_MANUAL_STAGING
COMI_HU_CONSUMPTION
COMI_HU_GOODS_ISSUE
COMI_HU_GOODS_QTY
COMI_I_CONFIRM_MANUAL_STAGING
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 779
COMI_I_HU_CONSUMPTION
COMI_I_MATERIAL_COMPLETE_CHECK
COMI_I_MATERIAL_SEQUENCE_CHECK
COMI_MATERIAL_COMPLETE_CHECK
COMI_MATERIAL_SEQUENCE_CHECK
COMI_MESSAGE_DEST_TEMPLATE
COHU_ADD_TO_EXISTING_HU
COHU_ASSIGN_HU
COHU_ASSIGN_HU_READ
COHU_BEREIT_CREATE_EXTERNAL
COHU_BEREIT_POST
COHU_BEREIT_READ
COHU_BEREIT_SAVE
COHU_CHECK_PICKING_INNER
COHU_DEASSIGN_HU
COHU_DEASSIGN_HU_READ
COHU_DEQUEUE
COHU_EXBEREIT_ALL_LINES_CHECK
COHU_EXBEREIT_LINE_CHECK
COHU_EXBEREIT_NEW_LINES_CHECK
COHU_HU_CANCEL_GI STORNO
COHU_HU_CANCEL_SAVE
COHU_HU_CANCEL_UPDATE
COHU_HU_CREATE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 780
COHU_HU_CREATE_PP
COHU_HU_DISPLAY
COHU_HU_GOODS_ISSUE
COHU_HU_READ_PP
COHU_HU_REFRESH
COHU_HU_UPDATE
COHU_ORDER_DATA_READ
COHU_UPDATE_HUM_KOMMI
Other Terms
PI sheet; Process order; Process Instruction categories MI_HUSTG, MI_HUSQU,
MI_HUCMP, MI_HUCNS, MI_HUSTC, MI_MATBA, RECON; Process Message
categories PI_HUCNS, PI_HUREC, PI_HUSTG, PI_MIREC amd PI_RECON
29.23S4TWL - Flow Manufacturing
Application Components:PP-FLW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270237
S4TWL - Flow Manufacturing
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
The functionality of flow manufacturing including line design, line balancing and
sequence planning is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope and it’s expiry date and
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 781
links to further information please refer to SAP note 2269324. In the compatibility matrix
attached to SAP note 2269324, flow manufacturing can be found under the ID 449.
This means that you need to migrate from flow manufacturing (ERP line design, ERP
line balancing, ERP sequence planning) to its designated alternative functionality PPDS
model mix planning and sequencing before expiry of the compatibility pack license. This
note shall provide an overview on the scope of flow manufacturing which is going to
expire with the compatibility pack license, how this maps to the designated alternative
functionality, if this alternative functionality is already available or when it’s planned to
be available and how you can migrate to the alternative functionality.
This note will regularly be updated to reflect more details on the alternative functionality
and the migration.
Business Process related information
Flow manufacturing in ERP includes functions for line design, line balancing as well as
rate/takt-based sequence planning. It is part of repetitive manufacturing solution and only
suitable for repetitive manufacturing planned orders. Following application transactions
belong to flow manufacturing:
Line design in ERP:
Create Line Hierarchy (LDB1)
Change Line Hierarchy (LDB2)
Display Line Hierarchy (LDB3)
Change Takt Time (LDA2)
Display Takt Time (LDA3)
Line balancing in ERP:
Create Line Balance (LDD1)
Change Line Balance (LDD2)
Display Line Balance (LDD3)
Sequence planning in ERP:
Sequencing in Background Job (LAS1)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 782
Change Sequence Schedule (LAS2)
Display Sequence Schedule (LAS3)
Change Sequence Schedule Interactively (LAS4)
PPDS model mix planning and sequencing is the successor of flow manufacturing. PPDS
was orignially part of the SAP Advanced Planning and Optimization (SAP APO) but is
now part of S/4HANA.
For more details on the concerned migration scope, the alternative functionality and
further business process related information please refer to SAP note 2268084.
Required and Recommended Action(s)
As flow manufacturing can be used until the expiry date of the compatibility pack
license, it’s up to each customer to decide, when (with which of the coming SAP
S/4HANA releases) they want to migrate to the designated alternative functionality.
Though the decision, at which point in time this will be done, should be taken early in
advance in order to plan accordingly for the migration efforts.
SAP recommends to use model mix planning and sequencing in PPDS.
Related SAP Notes
Custom Code related
information
ERP coding enhancements will not be supported after replacement with
PPDS.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Flow
Manufacturing, Line Design, ERP Sequence planning, ERP Line-Balancing, LDA2,
LDA3, LDB1, LDB2, LDB3, LDD1, LDD2, LDD3, LAS1, LAS2, LAS3, LAS4, ...
29.24S4TWL - Process Flow Scheduling (PP-PI)
Application Components:PP-PI-PMA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273079
S4TWL - Process Flow Scheduling (PP-
PI)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 783
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Required and Recommended Action(s)
Use PPDS for detailed planning and scheduling of bottleneck resources. PPDS in part of
SAP S/4HANA.
29.25S4TWL - Rate and Rough-Cut Planning
Application Components:PP-CRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270240
S4TWL - Rate and Rough-Cut Planning
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Reduced complexity in capacity planning and in reporting on capacities utilization
and capacity load
Better performance of scheduling
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 784
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, rate-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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 785
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
29.26S4TWL - Planning Horizon
Application Components:PP-MP-LTP, PP-MP-MPS, PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270241
S4TWL - Planning Horizon
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 786
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.
29.27S4TWL - Batch History
Application Components:LO-BM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270242
S4TWL - Batch History
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 787
Solution
Description
The Batch History is a rarely used part of the broad funtionality in the Batch Information
Cockpit. It must NOT be confused with the batch where-used list or the SAP Global
Batch Traceability solution.
The batch history described here is a change log for a single selected batch master record
and does not reflect the where-used information in the logistic chain. The batch history is
not considered as the target architecture within SAP S/4HANA, on-premise edition
(Functionality available in SAP S/4HANA on-premise edition but not considered as
future technology).
There is no functional equivalent planned for future releases.
Business Process related information
No influence on business processes expected. The batch-where used functionality
(transaction MB56, bottom-up/top-down analysis) are not affected at all.
The transaction codes related to Batch History are still available within SAP S/4HANA,
on-premise edition.
Depending on the configuration of the batch history, it may happen that batch history
records comprise references to business partners. These records will not be found by
the Business Partner End of Purpose (EoP) Check in Batch Management, nor will they be
found by the Information Retrieval Framework (IRF). Hence, if batch history records are
still present in the system, it is in the responsibility of the customer to ensure that these
records are considered in either frameworks by providing dedicated custom
implementations.
29.28S4TWL - Selected Business Functions in PP area
Application Components:PP-PI-PEV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271206
S4TWL - Selected Business Functions
in PP area
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 788
You are doing a system conversion from SAP ERP to SAP S/4HANA, on-premise
edition. The following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
The functional scope of a SAP ERP system is determined by a large set of business
functions. This was necessary because new or enhanced features were not allowed to
change existing reports or transactions. Every release new business functions were added
to switch the features developed for the release. Business functions became unclear over
time and the combinatorics of different business functions difficult to predict. Therefore
business functions have been cleaned up in SAP S/4HANA. Many business functions are
always on. A few business functions have been declared obsolete. This note provides
details for the obsolete business functions in the PP components.
Solution
Description
Selected PP business functions are not part of the target architecture in SAP S/4 HANA,
on-premise edition 1511 – FPS1. The following PP business functions are obsolete and
cannot be switched on in S/4HANA:
LOG_PP_INTELI_01 (Power list for process manufacturing)
LOG_PP_PRSP (Portal for production supervisor)
LOG_PP_BATCH_HISTORY
LOG_PP_CFB (Food and Beverage Solution)
Business EA-SCM is always on in S/4HANA to enable the migration from SAP-ERP to
S/4HANA.
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: Always-Off Business Functions. If a business
function is defined as "Business function is obsolete and cannot be activated" 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 and system conversion is
possible. Nevertheless the functionality related to these business functions is not always
available within SAP S/4 HANA, on-premise edition 1511 – FPS1.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 789
Business Process related Information
Business function LOG_PP_INTELI_01 offered a production supervisor work list. This
is available as of S/4HANA on premise edition 1611 release as Fiori apps "Manage
production order operations" and "Manage production orders".
Business function LOG_PP_PRSP offered portal roles for the production supervisor.
This is available as of S/4HANA on premise edition 1511 release as Fiori roles and
launchpad.
Regarding the functions switched by business function
LOG_PP_BATCH_HISTORY please see the separate note 2270242.
Business function LOG_PP_CFB switched various functions like
Catch Weight Management
Various print reports
Weigh scale integration
Enhanced production version management
Catch weight management is available in S/4HANA w/o switching.
One of the CFB functions was enhanced production version management implemented
by reports CFB_PV_MRP_PREP_MIXCAL and CFB_PV_MRP_RELEASE_LOCK.
The reports allowed to move production versions between active and inactive production
versions, which were stored in a separate databases. Inactive production versions were
invisible to MRP. In S/4HANA production versions have status "Blocked for automatic
sourcing", which serves the same purpose. If you used
reports CFB_PV_MRP_PREP_MIXCAL or CFB_PV_MRP_RELEASE_LOCK then use
the production version status in future.
Enterprise extension EA-SCM offered various functions like
Direct Store Delivery DSD
Cross Docking
Vehicle Space Optimization
Logistical Value Added Services
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 790
The functions switched by EA-SCM are still available as part of the S/4HANA
compatibility pack, but should be considered not part of the S/4HANA target
architecture. Successor functions for cross docking and vehicle space optimization are
available in transportation management SCM-TM.
Originally enterprise extension EA-SCM also switched PI-sheets, X-steps, MES
integration, and production order splitting. These functions have been removed from the
switch. In other words the PI-sheets, X-steps, MES integration, and production order
splitting work in S/4HANA on premise edition even if business function EA-SCM is
switched off. Please also note the corresponding notes for PI-sheets and MES integration.
29.29S4TWL - Time Streams Usage in Kanban
Application Components:PP-KAB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3196066
SAP S/4HANA Simplification Item:
Usage of Time Streams in Kanban
Symptom
In S/4HANA, persisted time streams are not longer used for Kanban time calculations.
Reason and Prerequisites
The usage of persisted time streams for time calculations based on factory calendars and
shift definitions has been removed in Kanban.
For Kanban Calculation, dynamic time streams are used which are generated on the
fly based on the customizing settings.
For the determination of delivery dates and for Kanban Summarized JIT Calls, a new
calculation algorithm was introduced.
In the customizing transactions OM19 ("Define Kanban Calculation Profiles") and OJI3
("Define Time Definition"), the time stream entries in table TTSTR will still be saved
and transported.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 791
If the SAP standard functionality for Kanban time calculation is used, there is no
adoption needed.
Customer specific modifications in the function group includes L0PK1F01, L0PK1F03,
or LPABC1F01 that change the way how time streams are created will have no effect
anymore on the Kanban time calculations.
Other Terms
S/4HANA, TTSTR, Time Stream, Kanban, Kanban Summarized JIT Call, Time
Definitions, Kanban Calculation, OM19, OJI3
29.30S4TWL - Graphical display of available quantity in MRP evaluations
Application Components:PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3018123
S4TWL - Graphical display of available
quantity in MRP evaluations
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In SAP ERP, within the Stock and Requirements List (MD04), a graphical display of
available quantity was available. With the advancement of web-based applications, old
chart technology like used here is no longer supported.
A new graphical display of the available quantity is available in the Manage or Check
Material Coverage apps.
Required and Recommended Action(s)
If planners are using the graphical display of available quantity in Stock and
Requirements List, encourage them to switch to the Manage or Check Material Coverage
apps for graphical evaluations.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 792
29.31S4TWL - External Interfaces in PP
Application Components:LO-SCI, PP-MES
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268048
S4TWL - External Interfaces in PP
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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)
LPO-Interface
XLPO
Lean planning and operations LPO was an algorithm for levelling
production based on lean principles. The algorithm was never
productized
Icon Interface
/SCRM/*
Icon was a response management solution. SAP's preferred solution
for 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 Value
The POI interface offers a comprehensive set of BAPIs and IDocs to connect SAP
S/4HANA with external MES or planning systems. Alternative BAPIs and IDocs are not
required. By deprecating the above mentioned interfaces SAP reduces confusion of
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 793
project teams looking for ways to connect an external system and it facilitates the further
development of the POI interface.
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
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
RFC-enabled function modules are not
available in SAP S/4HANA
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,
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 794
Related SAP Notes
Custom Code related information
SAP Note: 2226966
29.32S4TWL - Data Destruction in Kanban
Application Components:PP-KAB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2935734
Deprecation of Report
PK_DELETE_VENDOR_CUSTOMER
Symptom
Report PK_DELETE_VENDOR_CUSTOMER deletes personal data in area of Kanban.
This report should not be used for this purpose. The functionality is replaced by data
destruction object PP_KANBANCC_DESTRUCTION (documented here) together with
the End-of-Purpose Check for personal data (documented here).
Reason and Prerequisites
Report PK_DELETE_VENDOR_CUSTOMER deletes customer data related to the
process "Kanban with SD" and supplier data in message conditions for summarized JIT
calls. In case you are not using these processes, the note is not relevant.
Solution
After applying the correction, the report will abort immediately issuing an error message
referring to the information given in this note.
29.33S4TWL - Scheduling beyond year 2048
Application Components:PP-CRP-SCH
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2941708
S4TWL - Scheduling beyond year 2048
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 795
Symptom
You upgrade to SAP S/4HANA, on-premise edition 2021. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Domain CX_ZTPKT changed from INT4 to INT8.
Business Value
Manufacturing, maintenance and network orders can be scheduled beyond the date
19.01.2048.
Business Process related information
There is no impact on existing business processes.
How to Determine Relevancy
You are affected if you have own custom code using the scheduling functionality, even
partly and even if you don't schedule beyond 2048. For example if you use the function to
convert date/time into a point in time.
Required and Recommended Action(s)
Check all occurrences in custom code where domain CX_ZTPKT or a data element using
this domain is used.
If the data declaration or interface parameter holds a point in time value (as seconds
since 1.1.1980): Ensure that dependent types are also based on domain
CX_ZTPKT.
In case the data declaration or interface parameter does not hold a point in time value:
Change it to some other INT4 type not using domain CX_ZTPKT.
Check all usages of function module DATE_TIME_CONVERT and ensure that the
parameter POINT_IN_TIME can hold the value 253086767999 after the upgrade. For
example by using domain CX_ZTPKT.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 796
29.34S4TWL - Graphical Planning Table
Application Components:PP-CRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268050
S4TWL - Graphical Planning Table
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
The classic Gantt-chart control only works in SAP-Gui, not in Fiori-UIs
Solution
Description
Graphical planning tables (also known as graphical planning board or Gantt chart) can
be used for capacity load levelling and sequence planning. SAP offered basic capacity
planning by means of transactions CM21, CM22, etc. and advanced capacity planning in
PP/DS. This note is relevant for basic capacity planning by means of CM* transactions.
Transactions CM21, CM22, etc with graphical planning table are still available in SAP
S/4HANA on-premise edition, but not considered as the target architecture. Graphical
Planning Table is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope and it’s expiry date and
links to further information please refer to SAP note 2269324. In the compatibility matrix
attached to SAP note 2269324, Graphical Planning Table can be found under the ID 451.
Transactions CM* will be replaced by apps like "Manage Work Center Capacity",
"Capacity Scheduling Table", and "Capacity Scheduling Board" in SAP S/4HANA. The
use-cases covered and the features provided by the new apps are similar to the classic
CM* transactions. The new apps are available from release SAP S/4HANA on-premise
edition 1909 and in cloud from 1908.
Alternatively consider SAP Digital Manufacturing Cloud DMC component Resource
Orchestration REO. REO works on more granular data defined in Digital Manufacturing
Cloud. In a job-shop environment for example work-centers could be defined in SAP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 797
S/4HANA and the individual machines only in DMC. Dispatching from the work-center
level to the individual machine level is the domain of REO. Further information can be
found on http://help.sap.com/dmc.
Use embedded PP/DS for complex scheduling problems, if for example planned and
production orders of different BOM levels need to be synchronized, or if material
availability needs to be considered in scheduling, or if multiple bottleneck resources must
be aligned. PP/DS is embedded into S/4HANA. It is available on-premise. For details
refer to note 2666947.
Business Process related information
It will not be possible to translate customizing and personalization of the classic graphical
planning table into a UI configuration of the new graphical planning table.
Required and Recommended Action(s)
Consider to migrate to the new apps "Manage Work Center Capacity", "Capacity
Scheduling Table", and "Capacity Scheduling Board"
or evaluate REO
or evaluate (embedded) PP/DS.
Other Terms
Gantt-Chart; Graphical Planning Board; Capacity Levelling; Transactions CM21, CM22,
REO; DMC
29.35S4TWL - Logistic Information System in PP
Application Components:PP-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268063
S4TWL - Logistic Information System in
PP
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 798
Solution
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. Whether or not LIS causes
locking conflicts depends on the frequency of change of the aggregated
information. If several transactions want to update the same aggregated dataset in
parallel, then you will experience a locking conflict.
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 delivery but not considered as future technology).
LIS is part of the S/4HANA compatibility pack. You can continue using LIS. All LIS
tables are available in S/4HANA.
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 799
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. Usually LIS tables store data redundantly and data in
LIS tables can be re-created from the data in other tables. LIS data can theoretically also
be provided by CDS views if the data is stored redundantly. This is not the case for table
S029. Do not switch off the update of LIS table S029 if you need the information.
Required and Recommended Action(s)
Invest reasonably in the LIS. The LIS is intended as an interim solution in S/4HANA,
which can be used until PP analytics in HANA and SAP Digital Manufacturing Insights
DMI have 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.
If LIS did not cause serious locking conflicts in SAP-ERP, then it will likely not cause
any locking conflicts in S/4HANA either. If LIS causes locking conflicts during normal
operations, then investigate the use of HANA based analytics with dynamic aggregation
of data in CDS views. S/4HANA offers some reports using HANA based analytics
technology.
https://help.sap.com/viewer/fe39e10a9a864a8f8dc9537704f0fa13/1809.002/en-
US/d12d2a589aa80a02e10000000a44147b.html
The following analytical Fiori Apps already provide calculated measures:
F2034: Material Scrap
F2034: Operation Scrap
F2171: Excess Component Consumption
F2172: Execution Duration
F2216: Scrap Reason
Moreover, packages PPH_ANALYTICS and VDM_PP with its sub-packages contain
CDS views, which you can use to implement your own analytical queries. For a list of
released CDS views in PP refer to:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 800
https://help.sap.com/docs/SAP_S4HANA_ON-
PREMISE/8308e6d301d54584a33cd04a9861bc52/20bb26e53e12432a830a4243d81c135
a.html
Custome 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
S094: Stock/Requirements Analysis
S225: Goods receipts: repetitive manufacturing
S227: Product costs: repetitive manufacturing
These tables have partially been replaced by CDS views providing more or less the same
information but with different column names and structures.
29.36S4TWL - Sales and Operation Planning
Application Components:PP-SOP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268064
S4TWL - Sales and Operation Planning
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 801
Symptom
You are doing a system conversion to SAP S/4HANA on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 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)
PP SOP is intended as a bridge or interim solution, which allows you a stepwise system
conversion from SAP ERP to SAP S/4HANA on-premise edition and SAP IBP.
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.
Exceptions
ERP Sales & Operations Planning (SOP) will be replaced by Integrated Business
Planning. The following parts of SOP are needed also for other business processes. They
are part of core SAP S/4HANA and will not be replaced:
Using table view V_T001W_DR or using transaction V_T001W_DR you can
maintain the node type of an ERP plant in the distribution network. Node-types
are also needed by various other applications such as APO and IBP integration.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 802
Using transactions MC84, MC85, and MC86 you can maintain product groups.
Product groups are a popular selection condition in MRP apps.
Other Terms
Transactions MC74, MC75, MC78, MC80, MC81, MC82, MC83, MC87, MC88, MC89
Package MCP2
29.37S4TWL - Simplified Sourcing
Application Components:PP-MRP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268069
S4TWL - Simplified Sourcing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Simplification in master data maintenance:
Neither customizing nor source list records needed for sourcing
Reduced complexity: Reduced set of possible sources of supply with a clear and
symmetric definition
Consideration of quota arrangements is not dependent on any material master
attributes.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 803
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
and the procurement type of the material is either 'E' (in-house production) or
'X' (Both procurement types)
and the production version is neither "Locked for any usage" nor "Locked for
automatic sourcing"
and the planned material receipt's quantity is inside the quantity range of the
production version
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
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 804
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)
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 "Selection
Method" MARC-ALTSL determines if
MRP finds a BOM via the BOM's
validity period, the BOM's quantity
range, or via production version
Production versions are the
only source of supply for in-
house production. The material
master attribute MARC-ALTSL
no longer exists. Sourcing
selects material BOMs only if a
suitable production version
exists. Sourcing does not need
production versions to
find make-to-order and make-
to-project bills of material, but
production versions are
required to select routings also
if make-to-order or make-to-
project BOMs are used.
Simplification of the
sourcing logic; symmetry
of different sources of
supply; only production
versions are integrated
into quota
arrangements; only
production versions
make sure BOM and
routing fit together
The order type attribute "Routing
selection" T399X-ARBPA determines
how a routing is determined during
production order creation. The attribute
can be defined in customizing
transaction OPL8.
Production versions are the
only source of supply for in-
house production. A production
version references a routing.
This routing is used to create
production orders
Simplification of the
sourcing logic
The production version has a locking
indicator with values 'Locked' and 'Not
locked'. MRP only selects production
versions that are not locked.
MRP only selects production
versions that are neither
'Locked for any usage' nor
"Locked for automatic
sourcing."
The new status "Locked
for automatic sourcing"
corresponds to the
"Relevant for automatic
sourcing" indicator on
the purchasing info
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 805
record (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 exploded with
the method defined in the phantom
assembly's material master attribute
MARC-ALTSL.
Production versions are the
only source of supply for
phantom assemblies. If a
phantom assembly production
version exists with the same ID
as the production version
exploded on finished material
level, then the phantom BOM
explosion 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.
Simplified sourcing logic
and the possibility to
synchronize BOM
explosion on several
BOM levels.
Subcontracting purchase requisitions
are exploded with the method defined
in the material master attribute MARC-
ALTSL
Production versions are the
only source of supply for
subcontracting. If you use
subcontracting purchasing info
records to define the supplier,
you should define the
production version in the
purchasing info record. In all
other cases, the system
selects the material's
production versions, also for
subcontracting
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
MRP only selects purchasing info
records if a source list entry exists that
references the supplier referenced in
the info record
Purchasing info records are a
source of supply in their own
right. MRP selects purchasing
info records if the "relevant for
automatic sourcing" indicator is
set in the purchasing info
record
Simplification of the
sourcing logic: It is not
required to create a
source list entry on top
of the purchasing info
record
MRP uses source lists to determine
vendors, contracts, or delivery
schedules
Source lists are not considered
in the S/4HANA on-premise
edition 1511 until SP01.
In later releases source lists
can be used to provide
additional information for
sources of supply. For
Optionally, source lists
can be used to
temporarily block a
source of supply or
MRP-enable it only for
a limited period of time.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 806
example, the source list may
be used to block a source of
supply, MRP-enable it only for
a limited period of time or
prioritize available sources of
supply. For more details on
source of supply priorization,
please see note 2614920.
Alternatively quota
arrangements can be used as
a workaround.
MRP only considers quota
arrangements if the material master
attribute "Quota arrangement usage"
MARC-USEQU is set and the quota
arrangement usage configuration
includes MRP
MRP considers quota
arrangements always. It is not
required to switch it on in the
material master
In the early days of
MRP, reading and
considering quota
arrangements was
expensive. MARC-
USEQU was a
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.
Purchase order creation only considers
quota arrangements if the material
master attribute "Quota arrangement
usage" MARC-USEQU is set and the
quota arrangement usage configuration
includes purchase orders
Purchase order creation and
update as well as purchase
requisition creation and update
always consider and update
quota arrangements. It is not
required to switch usage of
quota arrangements on in the
material master
Simplified sourcing logic.
Quota arrangements are
used if they exist.
MRP considers more detailed planning
parameters of the supply source only, if
the parameter for scheduling according
to purchasing info record or agreement
has been set in customizing among the
plant (T399D-GTERM) or MRP group
parameters (T438M-GTERM).
Following parameters have been
considered by the MRP based on these
customizing flags:
Info record:
Planned delivery time
MRP considers always more
detailed planning parameters
of the supply source. It is not
required to switch it on in the
customizing.
Simplified sourcing logic.
Planning relevant
parameters will be
considered as soon as a
certain source of supply
has been choosen by
the MRP logic.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 807
Production version (for
subcontracting)
Contracts/Scheduling agreements:
Planned delivery time
GR processing time
Storage location
Rounding profile
MRP ignores the rounding profile of the
info record, even if the parameter for
scheduling according to purchasing info
record or agreement has been set
among the plant (T399D-GTERM) or
MRP group parameters (T438M-
GTERM).
MRP considers always a
rounding profile assigned to a
chosen info record.
Simplified sourcing logic.
Planning behavior has
been alligned
for different types of
supply sources for
external procurement.
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.
Purchasing info records, contracts, and delivery schedules have always been the
external procurement sources of supply integrated with APO. With purchasing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 808
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. Report CS_BOM_PRODVER_MIGRATION02 can be used to
analyze the situation as well as to create proposals for production versions based on BOM
validities. Run the report and accept or reject the proposed production
versions. Note 2655077 contains report CS_BOM_PRODVER_MIGRATION02.
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
Report
SAP Note: 2655077
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 809
The conversion report CS_BOM_PRODVER_MIGRATION02 lists BOMs to
which no corresponding production version is found.
You can use the conversion report to analyze the situation as well as to
automatically create production versions from valid BOMs and routings.
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
29.38S4TWL - Browser-based Process Instruction-Sheets/Electronic Work
Instructions
Application Components:PP-PI-PMA-PMC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268070
S4TWL - Browser-based Process
Instruction Sheets/Electronic Work
Instructions
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The functionality of browser-based PI sheets and electronic Work Instructions is still
available in SAP S/4HANA (functionality available in SAP S/4HANA but not considered
as future technology).
Browser-based Process Instruction Sheets (PI Sheets) and electronic Work
Instructions are based on a framework that allows the creation of worker UIs optimized
for the needs of individual workers. The content of the PI Sheet/Work Instruction is
rendered as plain HTML and displayed in the SAP HTML Viewer of ABAP SAP GUI
screens. It requires SAP GUI for Windows as UI technology and does not work as plain
WebUI in an internet browser. Browser-based PI sheets and EWIs require the MS
Internet Explorer as the HTML viewer of the SAP GUI for Windows dependends on MS
Internet Explorer (technical prerequisite for HTML viewer). Please check respective
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 810
attached notes 2224356 and 2999251 regarding MS Internet Explorer
lifecycle/compatibilty.
Content of browser-based PI Sheets and Work Instructions 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/Work Instruction is created when the control recipe/instruction is sent.
The rendered HTML content of browser-based PI Sheets and Work Instructions uses
XSL and CSS. SAP standard XSL and CSS can 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 (pharmaceutical
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.
Digital Manufacturing Cloud’s (DMC) Production Operator Dashboard (POD) will
provide similar functionality as PI-sheets in future. It will allow displaying Work
Instructions, recording of actual data, and enforcing predefined production processes. The
POD is developed keeping the following objectives in mind:
The POD is a highly functional, attractive, and usable UI for shop-floor operators
DMC runs together with S/4HANA as well as with S/4HANA Cloud
DMC and S/4HANA communicate through SOAP messages and oData services
Production engineers shall be able to design the POD w/o programming or HTML
skills
When designing the POD, production engineers can choose from many predefined UI
controls
The POD shall run in the most popular browsers using standard UI5 and Fiori
technology
It will be possible to connect the POD with sensors and actuators on the shop-floor
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 811
For timelines please refer to the official roadmap for SAP Digital Manufacturing
Cloud (https://roadmaps.sap.com).
Business Process related information
No migration tool from SAP PP-PI browser-based POC UI configuration to SAP DMC
POD configuration will be offered.
Required and Recommended Action(s)
You can still use PI-sheets using SAP-GUI for Windows. You should however be aware
of the following restrictions:
Most classic dynpro transactions run not only in SAP GUI but also in Web-GUI.
Web-GUI requires zero footprint, no installations on the end-user PCs, and runs
on different operatingn systems and thus simplifies administration. PI-sheets only
run in SAP GUI for Windows, which still has to be installed on end-user PCs.
PI-sheets only run in SAP GUI. They do not run in the Web UI. SAP offers a lot of
innovations in Fiori. Fiori and Web-Gui applications can be launched from the
Fiori launch-pad. Users will miss the innovations shipped in the Fiori
environment.
PI-sheets run in an HTML plugin, which uses MS Internet Explorer technology.
Please check
Custom Code Check / Adaption
Custom enhancements and modifications of Browser-based Process Instruction
Sheets/Electronic Work Instructions in SAP S/4HANA will not work for successor
UIs/PODs in SAP DMC.
Due to the tight integration of browser-based PI Sheets/Work Instructions and Production
Operator Cockpit functionality (see note 2270235 S4TWL - Process Operator
Cockpits) please perform a combined custom code check.
After switching from browser-based PI Sheets/Electronic Work Instructions to a sucessor
solution in SAP DMC check your custom code in context of data transfer from browser-
based PI Sheets/Electronic Work Instructions to whatever receiver and clean-up your
custom code that makes use of Browser-based Process Instruction Sheets/Electronic
Work Instructions functionality. The below (incomplete) list is an entry point for the
analysis of your custom code. Make sure that with end of support of the compatibility
scope item no newly entered or changed data is transferred with any custom code from
browser-based PI Sheets/Electronic Work Instructions and that no custom code initiates
save of data (create/update) to respective database tables.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 812
Transactions (no call or clone in custom code)
CO55 Worklist for Maintaining PI Sheets
CO60 Find PI Sheet
CO60E PI Sheet: Change
CO60XT Find Work Instructions
CO64 Worklist for Completing PI Sheets
CO67 Worklist for Checking PI Sheets
Database tables (no save of data through custom code)
POC_DB_APPL_STEP Domain Model: Application Steps
POC_DB_ARC_CONN Optical Archiving: Link Data (ArchiveLink)
POC_DB_C_COMMAND Domain Model: Command Collection
POC_DB_C_COMMENT Domain Model: Comment Collection
POC_DB_C_DEVIAT Domain Model: Deviation Collection
POC_DB_C_DEVVAR Domain model: Collection for variable setting (deviation)
POC_DB_C_METADAT Domain Model: Local Value Collection
POC_DB_C_OPER Domain Model: Operation Collection
POC_DB_C_PARTIT Domain Model: Partition Element Collection
POC_DB_C_PREDEC Domain Model: Predecessor Table
POC_DB_C_SERVICE Domain Model: Service Operation Collection
POC_DB_C_STEP Domain Model: Step Collection
POC_DB_C_SYTABLE Domain Model: Variable Collection (Symbol Table)
POC_DB_C_TRIGGER Domain Model: Trigger Collection
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 813
POC_DB_C_VALUE Domain Model: Value Container Collection
POC_DB_COMMAND Domain Model: Table for Step Commands
POC_DB_CONF_REQ Domain Model: Table for Signature Requests
POC_DB_DATA_REQ Domain Model: Table for Data Requests
POC_DB_DEV_SIGN Signature Key: Metadata Signature Process Step
POC_DB_DOMAIN Domain Model: Database Table for Domains
POC_DB_EVT_SIGN Signature Keys: Metadata for Event Log
POC_DB_EXEC_REQ Domain Model: Table for Execution Request
POC_DB_EXEC_STRA Domain Model: Table for Execution Strategies
POC_DB_MESS_REQ Domain Model: Table for Message Requests
POC_DB_OPERATION Domain Model: Table for Operations
POC_DB_PARTITION Domain Model: Partition
POC_DB_PROC_STEP Domain Model: Table for Process Steps
POC_DB_PROTOCOL Domain Model: Event Log for Process Steps
POC_DB_REAS_SIGN Signature Key: Meta Data Reason for Value Change
POC_DB_SIG_HANDL Domain Model: Signature Handler
POC_DB_SIGNATURE Domain Model: Signature
POC_DB_STEP Domain Model: Table for Step Basic Data
POC_DB_STEP_SIGN Signature Key: Metadata Signature Process Step
POC_DB_TRIG_PROT Logging: Trigger for Event in Domain Model
POC_DB_VALUE Domain Model: DB Table for Value Container
Programs (no call or clone in custom code)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 814
RCOPOC_CO55 Worklist for Maintaining PI Sheets
RCOPOC_CO60E Program PCOPOC_CO60E
RCOPOC_CO64 Worklist for Maintaining PI Sheets
RCOPOC_CO65 Worklist for Checking PI Sheets
RCOPOC_PIWKLT_ARCHIVE Archiving of PI Sheets/Work Instructions
RCOPOC_TEST_XML_GENERATOR Test: Generate and Download XML File for
Control Recipe
RCOPOC_TEST_XML_PARSING Test Program for Parsing an XML Document for
a PI Sheet
RCOPOC_TESTFRAME_GEN Function Module testframe generation
RCOPOC_WKLT Worklist for PI Sheets/Work Instructions
RCOPOC_WKLT_ARC_PROD_INS Worklist of Archived PI Sheets/Work
Instructions
Function Modules (no call or clone in custom code)
COCB_READ_PI_COMPONENTS Material Listing for PI Sheet
COCB_TRANSFER_CR_TO_MDE Transferring Control Recipe to Manual Data
Entry (PI Sheet)
COMH_CREATE_MESSAGE_NO_DIALOG Generating Status Confirmation for a
PI Sheet
COP0_ARCHIVE_PI_SHEET Archivieren aller Prozeßvorgabenlisten zu einem
Batchrezept
COP0_DELETE_PI_SHEET Löschen von Herstellanweisungen abhängig vom
Prozeßauftrag
COP0_EDIT_PI_SHEET Bearbeiten von Prozeßvorgabenlisten
COP0_GET_MODE_OF_PI_SHEET Liefert Modus des aktuell bearbeiteten PI-
Sheets
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 815
COP0_GET_PI_SHEET_DEVIATIONS Liefert die Abweichungen zu einem PI-
Sheet
COPF_OPC_ITEM_WRITE2 NOTRANSL: OPC Herstellanweisung: Lesen eines
OPC-Item-Werts
COPF_OPC_ITEM_WRITE_CHAR NOTRANSL: OPC Herstellanweisung:
Schreiben eines OPC-Item-Werts
COPF_OPC_ITEM_WRITE_FLOAT NOTRANSL: OPC Herstellanweisung:
Schreiben eines OPC-Item-Werts
COPF_OPC_ITEM_WRITE_MULTIPLE NOTRANSL: OPC Herstellanweisung:
Lesen eines OPC-Item-Werts
COPF_OPC_ITEM_WRITE_TIME NOTRANSL: OPC Herstellanweisung:
Schreiben eines OPC-Item-Werts
COPI_CHAR_IN_PI_SHEETS NOTRANSL: Verwendungsnachweis eines
Merkmales in Prozeßvorgabenlisten und
COPI_CHECK_CHAR_IN_PI_SHEETS NOTRANSL: Verwendungsnachweis für
Merkmale in Prozeßvorgabenlisten und Mel
COPI_CREATE_ELECTRONIC_SIGN
COPI_CREATE_NON_INPUT_MS
COPI_DPS_TEXT_UPDATE
COPI_EDIT_NEW_DPS_TEXT_VERSION
COPS_DELETE_PI_SHEET Deleting all Data Records for a PI Sheet
COPS_FEATURE_VARIABLE_UPDATE Saving PI Sheet Variables
COPS_MDE_FEATURE_UPDATE Database Update for PI Sheet Process
Instructions
COPS_MDE_MESSAGE_UPDATE Storing Data for Manual Data Entry
COPS_MS_FT_ASSIGNM_UPDATE Storing Assignment Table of Process
Messages and Instructions
COPS_SIGNATURE_RECORDS_UPDATE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 816
COPT_BUFFERED_SAVE_TEXT Storing PI Sheet Texts with Buffer
PISHEET_GET_EVENTS_GLOBAL NOTRANSL: Herstellanweisung: Liste von
globale Events
PISHEET_GET_EVENTS_LOCAL NOTRANSL: Cockpit: lokale Events
PI_SHEET_GET_STATE NOTRANSL: Neue & alte Herstellanweisung: Lesen des
Status
PI_SHEET_PRINT_WITH_EBR_STYLE NOTRANSL: Neue Herstellanweisung:
Anzeige/Ausdruck im EBR-Layout
PI_SHEET_SHOW NOTRANSL: Neue & alte Herstellanweisung: Anzeige
(Anzeige-/Änderungsmodus)
BAdI's with interface methods (check for custom implementation)
BADI_CMX_POC_ASYNC_SIGN Handle XML change error
IF_BADI_CMX_POC_ASYNC_SIGN~CHANGE_ABORT_MESSAGE
BADI_CMX_POC_DYN_SIGN_STRAT Enhancements for Dynamic Selection of
Signature Strategies
Interface methods IF_BADI_CMX_POC_DYN_SIGN_STRAT~
ADJUST_PI_CHECK_MESSAGE Check Process Instruction: Set Suited
Message Texts
CHECK_DYN_SIGN_STRAT_ALLOWED Check that Dynamic Signature
Strategy Function is Allowed
EXECUTE_INSTR_SEMANTIC_CHECK Executes Additional Checks
during Semantic Check
EXECUTE_XS_INSTR_CONTENT_CHECK XStep-based Process
Instruction: Executes Additional Checks
GET_CUST_DOMAIN_SUBCLASS Value Search: Returns Information on
Characteristic & Subcl.
HANDLE_FAILED_VALUE_SEARCH Search for Selected Signature
Strategy: Error Handling
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 817
RESET_STRAT_TO_PLACEHOLDER Reset Signature Strategy to
Placeholder Value
BADI_CMX_POC_REASON_VAL_CHG Processing of Reasons for Value Changes
Interface methods IF_BADI_CMX_POC_REASON_VAL_CHG~
CHECK_COMMENT_OF_REASON Checks the Entered Comment of
Reason for Value Change
CHECK_REASON_VAL_CHG_ALLOWED Checks that Processing of
Reasons is Allowed
Enhancement Spots (check for custom implementation)
ES_RCOPOC_WKLT
ES_SSAPLCMX_PII_CP_SRV_DST_PMC Enhancement PI Interpreter (Name of
Destination)
Other Terms
Packages COPOC, CMX_POC, CMX_PII, Transactions CO55, CO60, CO60E,
CO60XT, CO64, CO67
29.39S4TWL - Internet Kanban
Application Components:PP-KAB-CRL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268082
S4TWL - Internet Kanban
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 818
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 819
30.Logistics – PP/DS
30.1 S4TWL - Performance optimizations for publication of planning orders
Application Components:SCM-APO-PPS, SCM-APO-INT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2643483
S4TWL - Performance optimizations for
publication of planning orders
Symptom
You are doing a upgrade to SAP S/4HANA 1809. The following SAP S/4HANA
Transition Worklist item applies, if you are using Production Planning and Detailed
Scheduling (PP/DS).
Reason and Prerequisites
Reason: Upgrade from S/4HANA for Production Planning and Detailed Scheduling
(PP/DS) to SAP S/4HANA 1809.
Prerequisite: Target release is SAP S/4HANA 1809. Source release is SAP S/4HANA
1610 or SAP S/4HANA 1709.
Solution
Description
PP/DS order publishing for planning orders (Planned orders, Purchase requisitions, stock
transfer requisitions) is optimized to improve performance. This has resulted in changes
in the way BAdI's/User exits are called during publication from PP/DS.
Business Process related information
Advanced Planning (PP/DS) is used for production planning and planning receipts are
integrated back to SAP S/4HANA from live-cache.
Required and Recommended Action
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 820
If none of the relevant BAdI's or user exist are not implemented, no action is needed. The
upgrade will be automatic and system will switch over to the new optimized logic.
If you have implemented an effected BAdI's/user exists, the system will retain old
publication logic post upgrade.
This check is made only once while publishing of orders is happening for the first-time .
Post upgrade, you need implement your custom code in the new BAdI's as well, in
addition to the existing available publication BAdI's/user exits to support optimized flow
of planning orders. To switch further to optimized logic, an entry "X" need to be made
in table /SAPAPO/PUB_CHK.
How to Determine Relevancy
This Simplification Item is relevant if Advanced Planning (PP/DS) is used for production
planning and planning receipts are integrated back to SAP S/4HANA from live-cache and
relevant BAdI's/User exits for publishing of orders from PP/DS to PP are implemented.
The following are relevant BAdIs :
/SAPAPO/DM_PO_CHANGE
/SAPAPO/DM_PO_CHANG2
/SAPAPO/CL_EX_CIF_OP
/SAPAPO/DM_PO_MNTN
/SAPAPO/CL_EX_CIF_IP
/SAPAPO/SMOY_PUB_APP
/SAPAPO/DM_CP_CBCLP
The following are relevant Customer exits :
EXIT_SAPLCRV5_001
EXIT_/SAPAPO/SAPLCIF_RSV_001
EXIT_SAPLCSLS_003
EXIT_SAPLCPUR_001
EXIT_/SAPAPO/SAPLCIF_PU_001'
EXIT_SAPLCORD_005'
EXIT_/SAPAPO/SAPLCIF_ORD_001'
EXIT_SAPLCORD_002'
EXIT_SAPLCORD_001'
The following is the new BAdI that needed adaptation.
/SAPAPO/PPDS_ORDER_INT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 821
Other Terms
PP/DS
PPDS
S/4HANA 1809
Order Publishing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 822
31.Logistics – PS
31.1 S4TWL - Project Claim Factsheet
Application Components:PS-CLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267283
S4TWL - Project Claim Factsheet
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
With SAP S/4HANA 1511 the Project Claim factsheet will not be available anymore. As
of SAP S/4HANA 2022 the Fiori app Project Claim Overview (F6497) and the related
Project Claim object page is available as a alternative (see note 2267169).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Use Fiori App for Project Claim (SAP S/4HANA 2022 or higher)
if applicable also usage of Project Issue and Change Management functionality can be
considered for appropriate business requirement.
Knowledge Transfer to key- and end-user
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 823
31.2 S4TWL - Selected Project System Interfaces
Application Components:PS-ST-INT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267288
S4TWL - Selected Project System
Interfaces
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 824
Required and Recommended Action(s)
Knowledge Transfer to key- and end user.
31.3 S4TWL - Construction Progress Report and Valuation
Application Components:PS-REV-CPR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267289
S4TWL - Construction Progress Report
and Valuation
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 SAP S/4HANA
/SAPPCE/PNV01 Create Construction Progress Report
/SAPPCE/PNV03 Display Construction Progress Report
/SAPPCE/PNV04 Display construction progress report
/SAPPCE/PNV05 Create and Change CPR
/SAPPCE/PNV07 Create and Change Remaining Plan
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 825
Knowledge Transfer to key- and end-user. A customer specific solution or a switch to
SAP standard functions should be considered.
31.4 S4TWL - Project System ITS Services
Application Components:PS-CON
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267331
S4TWL - Project System ITS Services
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The following ITS services in Project System are not available any longer in S/4HANA
as of SAP S/4HANA 1511:
CNW1 WWW: Confirmation
CNW4 Project Documents
SR10 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.
31.5 S4TWL - Selected PS Business Function Capabilities
Application Components:PS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 826
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267333
S4TWL - Selected PS Business
Function Capabilities
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Selected PS Business Function capabilities are part of the SAP S/4HANA compatibility
scope, which comes with limited usage rights. For more details on the compatibility
scope and it’s expiry date and links to further information please refer to SAP note
2269324. In the compatibility matrix attached to SAP note 2269324, selected PS
Business Function capabilities can be found under the ID 468.
As of SAP S/4HANA 1511 - FPS1 the following business functions are switchable but
obsolete:
OPS_PS_CI_3
LOG_XPD_EXT_1
The following PS business functions are part of the compatibilty scope
OPS_PS_CI_1
OPS_PS_CI_2
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 827
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: Always-Off 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 Function LOG_XPD_EXT_1 is flagged as obsolete as of SAP S/4HANA
1511 - FPS1. The functionality covered in the business function has been modernized
along with Progress Tracking in SAP S/4HANA 2022. With this modernization, the
functionality becomes part of the perpetual scope of SAP S/4HANA. It is planned to
remove the obsolote flag for the business function with SAP S/4HANA 2022 FPS2.
The Business Functions OPS_PS_CI_1 and OPS_PS_CI_2 are available and selectable
with SAP S/4HANA 1511.
Topics in planning
The following features are currently under investigation. It is planned to modernize the
functions with S/4 capabilities.
OPS_PS_CI_1:
Performance improvements through allocation of status combinations
it is planned modernize the topic of status combination codes by support of
reading via status combination codes in the OData APIs. With this modernization
it is planned to move the feature to the perpetual scope.
OPS_PS_CI_2:
Option for the Down Payment Clearing of Billing Plans and Invoicing Plan
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 828
it is planned to modernize the topic of Cash Management, see also 2267182. With this modernization
it is planned to move the feature to the perpetual scope of S/4HANA.
Modernized topics
Project Builder enhancements
Project Builder enhancements consist of
Display of archived projects (OPS_PS_CI_1)
Intermediate save (OPS_PS_CI_1)
Display of more than 5 projects in work list (OPS_PS_CI_1)
Performance Improvements in the Project Builder and Network Transactions
(OPS_PS_CI_2)
Collective purchase requisitions (OPS_PS_CI_1)
Multilanguage short texts (OPS_PS_CI_1)
The topic of Project Builder enhancements has been modernized by
Display of archived multilanguage short texts in Project Builder (SAP S/4HANA 2022 FPS0)
Support of multilanguage short texts in Fiori apps (SAP S/4HANA 2021 FPS2)
Support of a new processing layer for creating purchase requisitions from network activities (SAP
S/4HANA 2022 FPS1)
All of the above features are carved out of the given business function as of SAP S/4HANA 2022
FPS1 and with the modernization are part of the perpetual scope of SAP S/4HANA.
Project-Oriented Procurement (ProMan) enhancements
With SAP S/4HANA 2021 Project-Oriented Procurement is enhanced by support for
multiple business partner adresses as part of the purchasing integration. The
enhanced Project-Oriented Procurement is available as part of SAP S/4HANA perpetual
scope. This includes also the enhancements to ProMan included in Business
Function OPS_PS_CI_1. See also Note 2267384.
Progress Tracking and Progress Analysis enhancements
Progress Tracking enhancements
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 829
Progress Analysis Workbench enhancements
With SAP S/4HANA 2022 FPS0 Progress Tracking and Progress Analysis Workbench are enhanced
by support of key-user extensibility. The enhanced functionality is available as part of SAP S/4HANA
perpetual scope. This includes also the enhancements included in Business Function OPS_PS_CI_1
and LOG_XPD_EXT_1. See also Note 2267190.
Cost Calculation
Easy Cost Planning for Network Activities
Business Add-Ins for Calculation in the Project System
With SAP S/4HANA 2022 FPS0 Cost Calculation is modernized by support of ACDOCP. The
enhanced cost calculation is available as part of SAP S/4HANA perpetual scope. This includes also
the enhancements included in Business Function OPS_PS_CI_1. See also Note 3033658.
New extractors for BI content
0PROJECT_CUST_ATTR Customer Fields for Project Def. (ci_proj)
0WBS_ELEMT_CUST_ATTR Customer Fields for WBS Element
0NETWORK_CUST_ATTR Customer Fields for network
0ACTIVITY_CUST_ATTR Customer Fields for Network Activity
0ACTY_ELEMT_CUST_ATTR Customer Fields for Activity Element
0WBS_ELEMT_USR_ATTR User Fields for WBS Element
0ACTIVITY_USR_ATTR User Fields for Network Activity
0ACTY_ELEMT_USR_ATTR User Fields for Activity Element
0PS_CLM_ECP ECP Data for Claim
0PS_WBS_ECP ECP for WBS-element
0PS_NWA_ECP ECP for network activities
0PS_NAE_ECP ECP for activity elements
0PROJECT_TEXT Project Definition
0WBS_ELEMT_TEXT Work Breakdown Structure Element
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 830
0NETWORK_TEXT Network Number
the above extractors are modernized by modernization of the related topic, i.e.
Support of key-user extensibility for projects (SAP S/4HANA 2020 FPS2)
Modernization of user-field display (SAP S/4HANA 2020 FPS0)
Modernization of Easy Cost Planning (SAP S/4HANA 2022 FPS0)
Modernization of multi-languge texts (SAP S/4HANA 2022 FPS0)
with these modernizations, the extractors above are part of the perpetual scope of SAP S/4HANA.
OPS_PS_CI_1:
Change Inherited Settlement Rules
the topic of settlement rule is modernized by substitution and validation of WBS
element settlement rule parameters (SAP S/4HANA 2022 FPS1). With the
modernization the functionality becomes part of the perpetual scope of SAP
S/4HANA.
Project System Material Component enhancements
the topic of project system material components is modernized by support of a
new processing layer for creating purchase requisitions from network activities
(SAP S/4HANA 2022 FPS1) as well as by the modernization of the Open Catalog
Interface (SAP S/4HANA 2022 FPS1). With these modernization the
functionality becomes part of the perpetual scope of SAP S/4HANA.
Determine WBS Account Assignment at MRP Area Level
the topic of WBS Account Assignment determination at MRP Area Level is
modernized by the usage in enhanced Project Manufacturing Management and
Optimization (PMMO) scenarios (SAP S/4HANA 2020). With these
modernization the functionality becomes part of the perpetual scope of SAP
S/4HANA.
OPS_PS_CI_2:
Display of Nonarchived and Archived Line Items
the topic of line item reports is moderined by the new Fiori app Project Cost Line
Items (SAP S/4HANA 2022 FPS1), see also note 2267286. With the
modernization the functionality becomes part of the perpetual scope of SAP
S/4HANA.
Topics that stay in compatibility scope
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 831
The following features can be used as part of the compatibility scope. There are no plans
to modernize the functionality, hence usage rights expire with the expiry date of the
compatibility scope.
OPS_PS_CI_1:
Forecast Workbench
Access Control Lists
Display of statistical key figures on an additional tab page
New extractors for BI content
Network: Statistical Key Figure
Network Activity: Statistical Key Figure
Netw. Act. Element: Statistical Key Figures
OPS_PS_CI_3:
The business function provides an optimization for Resource-Related Billing (RRB) for the
source Actual costs - line items. As an alternative, consider using the optimization provided with SAP
Note 2677564 or evaluate the usage of the new source Actuals Cost from Univ. Jrnl (Actuals Cost
from Universal Journal) available as of SAP S/4HANA 2022.
Required and Recommended Action(s)
Check this note for regular updates on modernizations of the business function
capabilities.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 832
31.6 S4TWL - Selected Project System BAPIs
Application Components:PS-ST
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267386
S4TWL - Selected Project System
BAPIs
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 833
31.7 S4TWL - Handling Large Projects Business Functions
Application Components:PS-HLP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2352369
S4TWL - Handling Large Projects
Business Functions
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 834
system conversion is not possible with this release. See SAP Note 2240359 - SAP
S/4HANA, on-premise edition 1511: Always-Off 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
31.8 S4TWL - Hierarchy Graphics in Project Systems
Application Components:PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3000979
S4TWL - Project Hierarchy Graphic
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 835
Description
Hierarchy Graphic in Project System is part of the SAP S/4HANA compatibility scope,
which comes with limited usage rights. For more details on the compatibility scope and
it’s expiry date and links to further information please refer to SAP note 2269324. In the
compatibility matrix attached to SAP note 2269324, hierarchy graphic in Project System
can be found under the ID 465.
Hierarchy graphic is used to visualize the WBS element hierarchy. The existing graphical
views hence are categorized as not part of the target architecture (Functionality available
in SAP S/4HANA 1511 delivery but not considered as future technology). In order to
display the project hierarchy (in a non-graphical way) you can use the Project Builder
(CJ20N) or any other transaction listing project elements hierarchically.
Business Process related information
Existing graphics and corresponding transactions can be used as part of the SAP
S/4HANA compatibility scope until end of expiry date. There is no alternative planned
for a graphical visualization.
In order to display the project hierarchy (in a non-graphical way) you can use the Project
Builder (CJ20N) or any other transaction listing project elements hierarchically.
Required and Recommended Action(s)
Knowledge Transfer to key- and end user
31.9 S4TWL - Project System Analytical Apps
Application Components:PS-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3112420
S4TWL - Project System Analytics Apps
from Smart Business for Project
Execution
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 836
You are doing a system conversion from SAP ERP to SAP S/4HANA and are using the
functionality described in this note. The following SAP S/4HANA Simplification Item is
applicable in this case.
Solution
Description
You are using Project System analytical apps from Smart Business for Project Execution.
These apps are not available in SAP S/4HANA.
Business Process related information
Project System analytical apps from Smart Business for Project Execution are not
available with SAP S/4HANA, this includes the following SAP Fiori Apps
F0293 WBS Element Cost Variance
F0294 WBS Element Costs at Risk
F0297 Due Project Milestones
F0298 Overdue Project Milestones
F0299 Overdue Project PO Items
F0300 Due Project PO Items
F0301 Due Network Activities
F0302 Overdue Network Activities
F0303 Due WBS Elements
F0304 Overdue WBS Elements
F0305 Project Missing Parts
F0306 Project Open Reservations
F0630 WBS-Element Revenue Variance
F0632 WBS-Element Exceeding Work
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 837
F0633 WBS-Element Pending Work
F0635 Project Report
F0696 WBS Element Percentage of Completion
F0697 WBS Element Earned Value
F0698 Project Earned Value
F0699 Project Percentage of Completion
Required and Recommended Action(s)
For use cases in the area of basic list reporting the project related Fiori apps (e.g. Project
Definition Overview F1976, WBS Element Overview F1974, Milestone
Overview F1975, Manage Project Procurement F2930) should be considered.
31.10S4TWL - Project System - Compatibility Scope
Application Components:PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3265838
S4TWL - Project System - Compatibility
Scope
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
This note summarizes Project System functionality that remains part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. Below is a overview of the features and the relevant
entries in the compatibility matrix attached to SAP note 2269324.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 838
Business Process related information
Project Reporting (Simplification Item ID 459)
Change documents (CJCD): WBS: consider using Change Documents for
Projects/Netw. (CN60)
Change Documents for Network (CODC) : consider using Change Documents for
Projects/Netw. (CN60)
Project Actual Cost Line Items (CJI3): consider using Project Actual Cost Line
Items (CJI3N)
Data Transfer to SAP-EIS (CJSA): no alternative planned
Select Key Figure and Characteristic (CJSB): no alternative planned
Consistency check transactions (Simplification Item ID 460)
CNC4 Consistency checks for project structure
CNC5 Consistency checks sales order/proj.
The above transactions are used to check consistency of master data within the project
structure or between project and sales order. For selected use cases validation can be used
as an alternative.
Progress Tracking & Monitoring Dates (Simplification Item ID 464)
Monitoring Network Dates (NWTM): consider using Progress Tracking
Required and Recommended Action(s)
Review and evaluate the provided alternatives where applicable.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Project System
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 839
31.11S4TWL- Deprecation of Project Cost Reports - Overview and Line
Items
Application Components:PS-FIO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3331626
S4TWL - Deprecation of Project Cost
Report - Overview (F2513) and Project
Cost Report - Line Items (F2538) apps
Symptom
You want to use Project Cost Report - Overview (F2513) or Project Cost Report - Line
Items (F2538) app.
Reason and Prerequisites
The Project Cost Report - Overview (F2513) and Project Cost Report - Line Items
(F2538) apps will be deprecated in S/4HANA 2023 and will become obsolete.
We recommend you to switch to the successor apps Project Cost Overview (F6991) and
Project Cost Line Items (F6992) as soon as possible.
Solution
Description
The Project Cost Report - Overview (F2513) and Project Cost Report - Line Items
(F2538) apps will be deprecated in S/4HANA 2023 and will become obsolete.
We recommend you to switch to the successor apps Project Cost Overview (F6991)
and Project Cost Line Items (F6992) as soon as possible.
Business process related information
tbd
Required and Recommended Actions
Switch to the successor apps.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 840
If you are using F2513 or F2538 app, this deprecation note is applicable for you.
Other Terms
Project Cost, Project Reporting
31.12S4TWL - Navigation to Project Builder instead of special maintenance
functions
Application Components:PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270261
S4TWL - Navigation to Project Builder
instead of special maintenance
functions
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
With SAP S/4HANA 1511 the target for links and references in reports CJI3N, CJI4N,
CN41, CNS0 is going to the single maintenance transaction CJ20N (Project Builder).
Business Process related information
Required and Recommended Action(s)
End user knowledge transfer required to switch from multiple transactions to single
maintenance transaction CJ20N.
Custom Code related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 841
In case of custom code for special maintenance functions only, customer should consider
to enable the custom code for the Project Builder transactions
31.13S4TWL - Production Resources and Tools functions for projects
Application Components:PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270262
S4TWL - Production Resources and
Tools functions for projects
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Production Resources and Tools functions for projects is part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and it’s expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, Production Resources and Tools functions for projects can be found under the
ID 463.
Business Process related information
Production Resources and Tools functions for projects can be used as part of the
compatibility scope.
Required and Recommended Action(s)
Knowledge Transfer to key- and end user, usage of alternatives to PRTs need to be
considered
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 842
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, PRT
31.14S4TWL - Specific PS archiving transactions
Application Components:PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270265
S4TWL - Specific PS archiving
transactions
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Project system specific archiving is part of the SAP S/4HANA compatibility scope,
which comes with limited usage rights. For more details on the compatibility scope and
it’s expiry date and links to further information please refer to SAP note 2269324. In the
compatibility matrix attached to SAP note 2269324, Project system specific archiving can
be found under the ID 470.
This means that you need to migrate from Project system specific archiving to its
designated alternative functionality central archiving (transaction SARA) before expiry
of the compatibility pack license. This note shall provide an overview on the scope
of Project system specific archiving which is going to expire with the compatibility pack
license, how this maps to the designated alternative functionality, if this alternative
functionality is already available or when it’s planned to be available and how you can
migrate to the alternative functionality.
This note will regularly be updated to reflect more details on the alternative functionality
and the migration.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 843
Business Process related information
The following Project system specific archiving transactions are part of the compatibility
scope
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
Going forward it is recommended to use the central archiving transaction SARA instead.
Required and Recommended Action(s)
As Project system specific archiving can be used until the expiry date of the compatibility
pack license, it’s up to each customer to decide, when (with which of the coming
SAP S/4HANA releases) they want to migrate to the designated alternative functionality.
Though the decision, at which point in time this will be done, should be taken early in
advance in order to plan accordingly for the migration efforts.
It is recommended to use central archiving transaction SARA instead of project
system specific transactions.
Knowledge Transfer to key- and end-user
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 844
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Archiving
31.15S4TWL - Project texts (PS texts)
Application Components:PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270266
S4TWL - Project texts (PS texts)
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Project texts (PS texts) are part of the SAP S/4HANA compatibility scope, which comes
with limited usage rights. For more details on the compatibility scope and it’s expiry date
and links to further information please refer to SAP note 2269324. In the compatibility
matrix attached to SAP note 2269324, Project Texts can be found under the ID 466.
The current project texts functionality can be used until the expiry date of the
compatibility scope. This includes the transactions
CN04 Edit PS Text Catalog
CN05 Display PS Text Catalog
Business Process related information
With SAP S/4HANA 2021 FPS1 renewed project texts are available. Renewed PS texts
provide a modernized persistency and the Fiori app Project Text for maintenance, while
covering similar features like the previous solution.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 845
Existing PS texts records can be migrated to the renewed PS texts model by using the
report “CN_PS_TEXT_MIGRATION”. The migration is client-dependent, to activate the
renewed PS texts, use IMG node “Activation of renewed PS Text”.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 846
32.Logistics – PSS
32.1 S4TWL - PS&S SARA Reports
Application Components:EHS-HSM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267438
S4TWL - PS&S SARA Reports
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The creation of SARA reports is not available within SAP S/4HANA. A successor
functionality is on the roadmap for the on-premise release S/4HANA 1909.
Business Process related information
Transaction CBIHSR01 is not available in SAP S/4HANA.
32.2 S4TWL - Substance Volume Tracking Selection Criteria based on tables
VBUK and VB
Application Components:EHS-SAF-RCK
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267439
S4TWL - Substance Volume Tracking
Selection Criteria based on tables VBUK
and VBUP
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 847
You are carrying out a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA transition worklist item is applicable in this case.
Solution
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
Scenario Category
Tables
Date for Planned
Quantities
PUR
PURCHASE_REQUISITION
EBAN
EBAN-LFDAT: Delivery
date of item
PUR
PURCHASE
EKKO, EKPO,
EKET, MKPF,
MSEG
EKET-EINDT: Delivery
date of item
SO
SALES
VBAK, VBAP,
VBEP, VBPA,
VBUP
VBEP-EDATU:
Schedule line date
SO
DELIVERY
LIKP, LIPS, VBPA,
VBUP,
MKPF, MSEG
LIKP-WADAT: Planned
date of goods
movement
IMP
PURCHASE_REQUISITION
EBAN
EBAN-LFDAT: Delivery
date of item
IMP
PURCHASE
EKKO, EKPO,
EKET, MKPF,
MSEG
EKET-EINDT: Delivery
date of item
EXP
SALES
VBAK, VBAP,
VBEP, VBPA,
VBUP
VBEP-EDATU:
Schedule line date
EXP
DELIVERY
LIKP, LIPS, VBPA,
VBUP,
MKPF, MSEG
LIKP-WADAT: Planned
date of goods
movement
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 848
PRO
PRODUCTION
AUFK, AFKO,
AFPO, RESB,
MKPF, MSEG
AFKO-GSTRS:
Scheduled start
PRO
REPET_MANUFACTURING
PLAF, RESB,
MKPF, MSEG
PLAF- PSTTR: Basic
start date
CON
PRODUCTION
AUFK, AFKO,
AFPO, RESB,
MKPF, MSEG
AFKO-GSTRS:
Scheduled start
CON
REPET_MANUFACTURING
PLAF, RESB,
MKPF, MSEG
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.
32.3 S4TWL - Simplification in Product Compliance for Discrete Industry
Application Components:EHS-MGM-PRC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267461
S4TWL - Simplification in Product
Compliance for Discrete Industry
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 849
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 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
Class Name / Event
00600054 - EHPRC_CHK_BA
CL_EHPRC_PCO_COMP_REQ_BASE
00600049 - EHPRC_CHK_CH
CL_EHPRC_PCO_COMP_REQ_CHROHS
00600056 - EHPRC_CHK_IM
CL_EHPRC_PCO_CMP_REQ_IMDS
00600069 - EHPRC_CHK_JG
CL_EHPRC_PCO_CMP_REQ_JIG
00600053 - EHPRC_CHK_SV
CL_EHPRC_PCO_COMP_REQ_SVHC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 850
00600068 - EHPRC_CHK_RO
CL_EHPRC_PCO_COMP_REQ_EUROHS
The following compliance assessment workflow templates are not available in SAP
S/4HANA, on-premise 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
Object
Class Name / Event
Type of Assessment
Process
00600070 -
EHPRC_BMASMT
CL_EHPRC_PCO_BASMAT_ASSMNT
Basic Material
Assessment
00600071 -
EHPRC_COASMT
CL_EHPRC_PCO_COMP_ASSMNT
Component
Assessment
00600062 -
EHPRC_PRASMT
CL_EHPRC_PCO_PROD_ASSMNT
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.
32.4 S4TWL - Replacement of Event Type Linkages
Application Components:EHS-SUS-DG, EHS-SUS-SDS, EHS-SUS-PMA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3196565
S4TWL - Replacement of Event Type
Linkages
Symptom
You are using SAP S/4HANA for product compliance and are performing a system
upgrade to SAP S/4HANA 2022 or higher. The following SAP S/4HANA transition
worklist item SI15: Logistics_PSS is applicable in this case.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 851
You have activated the event type linkages in database view SWFDVEVTYP for the
receiver type PCEP_V1.0 and are using a customer-specific receiver class
implementation and not the standard class CL_EHFND_PCEP_EVT_HANDLER. See
also Customizing for Activate Event Type Linkage under Product Compliance ->
Foundation for Product Compliance -> Product Compliance Background Processing ->
Activate Event Type Linkage.
If you are using standard event receiver settings or perform an initial installation of SAP
S/4HANA 2022 or higher (greenfield installation), this note is not relevant.
Solution
Description / Business Value
In SAP S/4HANA for product compliance, the event type linkages have been introduced
for the following main reasons:
Decoupling of a transcation, such as the release of a composition, from the
asynchronous processing of this event to ensure proper follow-on processing of
this event
Providing a possibility to trigger customer-specific actions, such as sending an e-mail
or notifying external systems that a certain event has been raised and needs
follow-on processing
Due to technical restrictions, it is not allowed to use local update tasks in the context of a
logical unit of work of RAP and BOBF business objects. The update task
module SWF_EVT_RAISE_IN_UPDATE_TASK to raise events and carry them out in a
separate update task violates the contract, which may lead to short dumps.
In order solve these technical restrictions, the overall processing logic has been changed
in the following way with SAP S/4HANA 2022. The event type linkages are
replaced with a central determination that has been added to all affected business objects.
The determination is carried out during save and is supposed to check if events have
been created in the same session.
The business object saves the data (for example, as an analytical composition),
creates the corresponding new event(s) (for example, Analytical Composition
Released) in the table EHFNDD_PCE, and raises the system event
SAP_EHFND_PCEP_EVT_CRTED to process these events in a follow-on
activity.
The system event triggers the periodically scheduled background job to process all
new and failed product compliance events and tasks.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 852
Business Process-Related Information
If you are using standard event type linkages, there are no changes to the business
process. If you are using a customer-specific event type linkage in SWFDVEVTYP for
the receiver type PCEP_V1.0 and not the standard class
CL_EHFND_PCEP_EVT_HANDLER, you have to take action.
Required and Recommended Action(s)
You have to replace your customer implementation of the receiver class to reflect the architectural
change.
How to Determine Relevancy
In transaction SPRO, navigate to the Customizing activity for Activate Event Type
Linkage under Product Compliance -> Foundation for Product Compliance -> Product
Compliance Background Processing -> Activate Event Type Linkage. If you have
assigned the events of the receiver type PCEP_V1.0 to a nonstandard class other
than CL_EHFND_PCEP_EVT_HANDLER, this worklist item is relevant for you.
Object Ca
tegory
Object Type
Event
Receiver
Type
Receiver Class
Class
CL_EHFND_PCEP_EVT
_WF_ACMPS
RELEASED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CCI
CSM_ASSGMT_CHGD
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CCI
SAVED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CCM
CREATED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CR
ACTIVATED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CR
CHANGED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CR
DEACTIVATED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CRQ
CLOSED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CRR
CREATED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CRR
RELEASED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_CRR
SAVED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_LCMPS
RELEASED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_LEM
LEM_CHANGED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_MCMPS
RELEASED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 853
Class
CL_EHFND_PCEP_EVT
_WF_PCMPS
RELEASED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_PEF
CHANGED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_PRP
CHANGED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PCEP_EVT
_WF_SUB
SAVED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PC_SERVI
CE_REQUEST
PRIV_SUBSTANCE_REQ
UEST_READY
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PC_SERVI
CE_REQUEST
PRODUCT_REQUEST_R
EADY
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PC_SERVI
CE_REQUEST
PUB_SUBSTANCE_REQ
UEST_READY
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHFND_PC_SERVI
CE_REQUEST
REFRESH_REQUESTED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHPMA_PCEP_EVT
_WF_INTRD
INITIAL_TRACKING_RE
QUESTED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHPMA_PCEP_EVT
_WF_PTRD
TRACKING_REQUESTE
D
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHPMA_PCEP_EVT
_WF_RETRD
RETRACKING_REQUES
TED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
Class
CL_EHSDS_PCEP_EVT
_WF_OR
SDS_OUTPUT_REQUES
T_CREATED
PCEP_V1
.0
CL_EHFND_PCEP_EV
T_HANDLER
32.5 S4TWL - QM Interface
Application Components:EHS-SAF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267387
S4TWL - QM Interface
Symptom
You are carrying out a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA transition worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 854
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
32.6 S4TWL - PS&S Enterprise Search Model
Application Components:EHS-SAF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267421
S4TWL - PS&S Enterprise Search
Model
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 855
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).
32.7 S4TWL - Hazardous Substance Management
Application Components:EHS-HSM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267422
S4TWL - Hazardous Substance
Management
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
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 partially deprecated (see below for details). Alternative exists.
Business Process related information
Some adjustments in the SAP Easy Access menu have been made:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 856
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.
Other Terms
SAP S/4HANA, System Conversion, Upgrade
32.8 S4TWL - Add-On: SAP Product and REACH Compliance (SPRC)
Application Components:EHS-SRC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267423
S4TWL - Add-On: SAP Product and
REACH Compliance (SPRC)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 EU RoHS, China RoHS, JIG, and
GADSL.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 857
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 SAP EHSM Product and REACH Compliance .
For the process industry solution of SPRC, no direct 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.
Process industry customers can use SAP EHS Management Product Safety as follows:
Use Safety Data Sheet authoring and distribution to communicate Use and Exposure
scenarios of your products to your customers
Manage Substance registrations with authorities including registration numbers and
volume thresholds
Use Substance Volume Tracking capabilities to track and monitor the volumes of
substances in your products.
Discrete industry customers can use SAP EHS Management Product and REACH
Compliance as follows:
Maintain and monitor the compliance status of your raw materials for each supplier
Aggregate and monitor the compliance status for your products based on the supplier
information.
The provision of new capabilities, which will cover both process and discrete industries
requirements, is planned to be available as part of SAP S/4HANA for product compliance
and SAP S/4HANA Cloud for product compliance. Selected functionality to manage and
ensure the marketability of your products is already available as of SAP S/4HANA 1808 /
1809. Please check https://www.sap.com/products/product-compliance.html for
additional details.
Business Process related information
No influence on business processes expected
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 858
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 and REACH Compliance 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.
Other Terms
SAP REACH Compliance, SRC, SAP Product and REACH Compliance, SPRC, SAP
EHS Management, EHSM, PRC
32.9 S4TWL - Add-On: EHS Web-Interface
Application Components:EHS-BD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267426
S4TWL - Add-On: EHS Web-Interface
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The add-on EHS Web-Interface will not be supported with SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 859
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.
32.10S4TWL - Add-On: Genifix (Labelling solution)
Application Components:EHS-SAF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267427
S4TWL - Add-On: Genifix (Labeling
solution)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
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).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 860
32.11S4TWL - BW Extractors for Dangerous Goods Management and
Specification Managemen
Application Components:EHS-SAF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267432
S4TWL - BW Extractors for Dangerous
Goods Management and Specification
Management
Symptom
You are carrying out a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA transition worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 861
33.Logistics – QM
33.1 S4TWL - Quality Management Information System (QMIS)
Application Components:QM-QC-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270193
S4TWL - Quality Management
Information System (QMIS)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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 but not considered as future technology).
The following transactions are replaced by corresponding Fiori apps in QM Analytics:
MCOV MCOP MCOX MCOB MCOD MCOM MCOK MCOI MCOG MCOE MCOC
MCOA MCVZ MCVP MCVX MCVD MCVB MCVM MCVK MCVI MCVG MCVE
MCVC MCVA MCXP MCXV MCXX MCXD MCXB MCXM MCXK MCXI MCXG
MCXE MCXC MCXA
The transactions will be removed in the SAP Fiori launchpad for SAP S/4HANA.
Functional equivalent is covered by QM Analytics.
https://help.sap.com/viewer/2bc3ee8d1c83404e8cf62418640004f2/LATEST/en-
US/0d117e44696b4f5d98962070a01a7469.html
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 862
An integrated set of quality data allows you to quickly identify systematic errors, analyze
problems, eliminate root causes, and respond faster to unforeseen events and deviations.
You can perform quality evaluations based on inspection results or based on issue data.
Fiori App
App ID
Inspection lot analytics:
Analyze inspection lots for categories such as accepted and rejected lots, rejection rate, skip
rate, total number of lots, skip lots, and mean processing time
Inspection Lot Analytics Last 365 Days
F3239
Inspection Lot Detailed Analytics
F3273
Characteristic analytics:
Analyze inspection characteristics for categories such as accepted and rejected inspections,
rejection rate, skip rate, mean value, standard deviation, Cp and Cpk index and so on.
Characteristic Analytics Last 365 Days
F3383
Characteristic Detailed Analytics
F3382
Results History
F2428
Nonconformance analytics:
Analyze recorded defects with or without notifications and quality notifications for categories such
as mean processing time and overrun.
Nonconformance Analytics Last 365 Days
F3584
Nonconformance Detailed Analytics
F3583
These Fiori apps are already integrated in the QM Fiori launchpad role templates.
Business Process related information
No influence on business processes expected. Customers should just consider this when
they think about investments into their QMIS functionality.
Other Terms
MCOV MCOP MCOX MCOB MCOD MCOM MCOK MCOI MCOG MCOE MCOC
MCOA MCVZ MCVP MCVX MCVD MCVB MCVM MCVK MCVI MCVG MCVE
MCVC MCVA MCXP MCXV MCXX MCXD MCXB MCXM MCXK MCXI MCXG
MCXE MCXC MCXA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 863
33.2 S4TWL - Redundant Transactions in QM
Application Components:QM, QM-PT-RP-PRC, QM-PT-BD-SPL, QM-CA-MD, QM-PT-BD, QM-
IM-SM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2338215
S4TWL - Redundant transactions in QM
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Several transactions had been available for performing the same task. To simplify
working with the system, redundant transactions have been removed or will not be
available for SAP S/4HANA.
Business Process Related Information
The following transactions are either redundant, can be covered by alternate
transactions/functions or are replaced by corresponding Fiori apps.
The following transactions will not be provided anymore in SAP S/4HANA:
Transaction
Text
Component
Alternative
QE51
Results recording worklist
QE51N
QS45
Display catalog
QM-PT-BD
QS42
QCYF
Report RSTXFCPY,
copies SAPscript forms
QM
SE71
QCYT
Report RSTXTCPY,
allows copying of SAPscript text between two clients
QM
access via
SO10
The following transactions are replaced by corresponding Fiori apps and are therefore not
available in the SAP Fiori launchpad for SAP S/4HANA (but can be called directly):
Transaction
Text
Component
Alternative
QDV3
Display sampling procedure
QM-PT-BD-SPL
Fiori app
Sampling Procedure
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 864
QI03
Display q-info record -
procurement
QM-PT-RP-PRC
Fiori app
Quality Info Records -
Procurement
QPR3
Display sample
QM-IM-SM
Fiori app
Sample
QS34
Display inspection method
version
QM-PT-BD
Fiori app
Inspection Method
The following transactions can be covered by alternate transactions and are therefore not
available in the SAP Fiori launchpad for SAP S/4HANA (but can be called directly):
Transaction
Text
Component
Alternative
QC11
Create certificate profile
assignment
QM-CA-MD
QC15
QC12
Change certificate profile
assignment
QM-CA-MD
QC16
QC13
Display certificate profile
assignment
QM-CA-MD
QC17
QC14
Create certificate profile
assignment with copy model
QM-CA-MD
QC18
Required and Recommended Action(s)
Alternate transactions can directly be used. Fiori apps are already integrated in the QM
Fiori launchpad roles.
33.3 S4TWL - Removed Navigation to Transactions for Evaluations in QM
Application Components:QM-IM, QM, QM-QN, QM-QC-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2340996
S4TWL - Removed Navigation to
Transactions for Evaluations in QM
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 865
Solution
Description
The following transactions won’t work properly by accessing them in SAP GUI for
HTML via the SAP Fiori launchpad. It is planned to replace them by corresponding Fiori
analytical apps.
Business Process Related Information
The following transactions will not be available in the SAP Fiori launchpad for SAP
S/4HANA 1610. Also navigating to the transactions from other transactions will not be
possible:
Transaction
Text
Component
QGA1
Display quality score time line
QM-QC-IS
QM50
Time Line Display of Quality Notifications
QM-QN
QGP1
Results history for task list characteristic
QM-QC-IS
QST05
Graphical Scheduling Overview
QM-IM
Required and Recommended Action(s)
For the time being, open the transaction in SAP GUI for Windows.
33.4 S4TWL - Authorization Objects in QM
Application Components:QM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2505099
Worklist for transition to SAP S/4HANA -
authorization objects in quality
management
Symptom
You execute a system conversion to SAP S/4HANA, on-premise edition. The SAP
S/4HANA transition worklist entry below is relevant in this case.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 866
Renewal
Solution
Description
In some authorization objects in quality management, there is no authorization field for
the activity (for example, create or change). Instead, the authorization is checked via the
authorization object Q_TCODE (transaction code), which must also be maintained. Since
transaction codes are no longer relevant for SAP Fiori apps, the old authorization objects
are being replaced by new authorization objects with an activity in the medium term in
SAP S/4HANA - starting with Release 1709.
It will be possible for the old authorization objects to be deleted in a future release. Until
then, they remain valid. This means that the new authorization objects will be checked in
addition to the old authorization objects.
The following tables show which new authorization objects replace which old
authorization objects.
Changes in SAP S/4HANA 1709:
New authorization
object
Replaces the following old
authorization objects
Comment
Q_CGRP_ACT
Q_CAT_GRP and Q_TCODE
Authorization to edit code groups
and codes
Q_CSSET_ACT
Q_CAT_SSET and Q_TCODE
Authorization to edit selection sets
Q_MINSPCHR
Q_MASTERD, Q_STA_QPMK,
and Q_TCODE
Authorization to edit master
inspection characteristics
Q_INSPMETH
Q_MASTERD, Q_STA_QMTB,
and Q_TCODE
Authorization to edit check methods
Q_SMPLPROC
Q_TCODE
Authorization to edit sampling
procedures
Q_DYNMODRL
Q_TCODE
Authorization to edit dynamic
modification rules
Q_QIRECPRC
Q_MATERIAL and Q_TCODE
Authorization to edit quality info
records for procurement
Q_SMPLSCHM
Q_TCODE
Authorization to edit sampling
schemes
Q_INSPLOT
Q_INSPTYPE, Q_MATERIAL,
and Q_TCODE
Authorization to edit inspection lots
Q_INSPRSLT
Q_INSPTYPE, Q_MATERIAL,
and Q_TCODE
Authorization to enter inspection
results
Q_QLEVEL
Q_MATERIAL and Q_TCODE
Authorization to edit quality levels
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 867
Q_INSPPNT
Q_TCODE
Authorization to edit inspection
points
Changes in SAP S/4HANA 1809:
New authorization
object
Replaces the following old
authorization objects
Comment
Q_CTRLCHRT
Q_SPC and Q_TCODE
Authorization to edit control charts
Q_MATSMPL
Q_MATERIAL with the following
values for QMATMODUS:
J (edit sample record)
K (release physical sample and
sample)
Authorization to edit samples
Q_SMPLSLOC
Q_TCODE
Authorization to edit sample
storage locations
Q_INSPQUAL
Additional authorization for
customizing of inspector
qualification
Q_SDRWGP
Q_MASTERD with QMASTMOD =
102
Authorization to edit sample
drawing procedures
Q_CERT_IN
Q_TCODE
Authorization to edit quality
certificate receipts in procurement
Q_QIRECSLS
Q_MATERIAL with QMATMODUS =
E and Q_TCODE
Authorization to edit quality info
records in Sales and Distribution
Business-process-related information
No consequences are expected for business processes. Consequences are expected only
for system administration.
Required and recommended action(s)
Your users need authorizations for the new authorization checks to be able to continue
using the functions they have used so far. At "Profile Generator: Upgrade and First
Installation" (transaction SU25), you use steps 2a/b and 2c to update the default values
and roles so that they receive the new authorizations. This update takes some time. To
enable your users to work productively in the upgraded system before you update the
default values and roles, run the report REGENERATE_SAP_NEW. This report creates
the role SAP_NEW with the new authorizations. Assign SAP_NEW to the users affected
by the upgrade.
Caution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 868
Remember to delete the role assignments to SAP_NEW after you have updated the authorization
default values and roles.
33.5 S4TWL - Results Recording
Application Components:QM-IM-RR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270124
S4TWL - Results Recording for
handheld devices
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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 on-premise edition
1511
QEH1
Required and Recommended Action(s)
Knowledge transfer to key and end users
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 869
Worklist
33.6 S4TWL - ITS services in QM
Application Components:QM-QC, QM-IM-RR, QM-QN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270126
S4TWL - ITS services in QM
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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, on-premise 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 870
Transaction
Code
Corresponding ITS
Service
Description
Package
Application
Component
Area
QC40
QC40
Internet
Certificate for
Delivery
QC
QM-CA-MD
Basic Data for
Certificates
QC40A
QC40A
Internet
Certificate for
Delivery
QC
QM-CA-MD
Basic Data for
Certificates
QC42
QC42
Batch
certificate on
WWW
QC
QM-CA-MD
Basic Data for
Certificates
QEW01
QEW01
Results
Recording on
Web
QEWW
QM-IM
Quality
Inspection
QEW01V
QEW01V
Variant Maint.:
Recording on
Web
QEWW
QM-IM
Quality
Inspection
QMW1
QMW1
Create quality
notification
(WWW)
QQM
QM-QN
Quality
Notifications
QISR
QISR
Internal
Service
Request
QNWEB
QM
Quality
Notifications
QISRW
QISRW
Internal
Service
Request on
the
Web
QNWEB
QM
Quality
Notifications
Required and Recommended Action(s)
Knowledge transfer to key and end users
Check if the services are used via transaction SICF. Hierarchy Type = "Service", Service
Name e.g. "QC40" and execute. Click on node e.g. "QC40" and check via context menu
(mouse-click right) if service is active. Do the same for all services in the table.
Other Terms
IAC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 871
33.7 S4TWL - QM WEB Workplace (MiniApps) based on ITS Services
Application Components:QM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270129
S4TWL - QM WEB Workplace
(MiniApps) based on ITS Services
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Renovation
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 872
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
Other Terms
IAC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 873
34.Logistics – TRA
34.1 S4TWL - Transportation (LE-TRA)
Application Components:LE-TRA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270199
S4TWL - Transportation (LE-TRA)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Logistics Execution Transportation (LE-TRA) is not the target architecture within SAP
S/4HANA. The functionality is available in SAP S/4HANA but not considered as future
technology. The alternative functionality is selected features of Transportation
Management which is already available within SAP S/4HANA.
Please note however the following exception (details please see in the attachment below):
The Route object of application component LE-TRA and the corresponding objects,
which are needed for the definition and determination of this route, have been
moved from the Compatibility Scope into the Perpetual Scope of SAP S/4HANA.
In other words: The customers can use those objects after 2030 in SAP
S/4HANA.
That allows the customer to use these objects for existing funcionality in other
applications e.g. scheduling in sales order / stock transport order / delivery, etc.
Important: All other objects from LE-TRA which are used for the Transportation
functionality will remain in the Compatibility Scope. And cannot be used after
2030.
This would primarily be the shipment document + shipment cost document and
all corresponding objects / customizing / master data / interfaces.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 874
The Route in SAP S/4HANA is no strategic object:
SAP does not plan further innovations for those objects. As well no integration
into new innovations e.g. Product Compliance is planned.In particular no
integration into SAP S/4HANA Supply Chain for Transportation Management is
available or planned. No standard migration tool from LE-TRA to SAP S/4HANA
TM is planned either.
LE-TRA and the industry solution IS-OIL are functionally different solutions,
however they share some objects on a technical level. These shared objects can
continued to be used, even after the expiry of the compatibility pack license, but
only in OIL&GAS context. These are the areas of Transportation Planning Point
and Shipment type, which are clustered around the tables VTK / TTDS.
Business Process related information
No influence is expected on the current business processes realted to Logistics Execution
Transportation (LE-TRA). The related functionality is still availalbe within SAP
S/4HANA.
Required and Recommended Action(s)
Logistics Execution Transportation (LE-TRA) is not the target architecture anymore
within SAP S/4HANA,.
The alternative functionality is the basic variant of Transportation Management within
SAP S/4HANA, which is already available.
The main functions of LE-TRA have already been replaced with those selected functions
of SAP S/4HANA Supply Chain for Transportation Management.
Currently, that means until the expiration of the usage rights of the Compatibility Packs,
both technical applications (LE-TRA and Transportation Management) are independent
from each other and can be used next to each other in the same SAP S/4HANA database
instance.
However they are not integrated with each other and there is no data exchange.
How to determine Relevancy
The Simplification Item is relevant in the following cases:
- the related customizing for LE-TRA is maintained
--> SPRO: Logistics Execution - Transportation (exception would be the LE-TRA Route
determination)
- the readyness check lists table entries e.g.
-> Tables VTTK, VTPA, VTTS, VFKK are checked
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 875
Detailed description in SAP S/4HANA:
LE-TRA functionality and the equivalent with basic Transportation Management
https://www.sap.com/germany/documents/2021/08/7231ed24-f47d-0010-bca6-
c68f7e60039b.html
In addition please find the detailed description of the parcel process in SAP S/4HANA
und in the attachments:
LE-TRA-XSI functionality and the equivalent process within basic Transportation
Management
For convenience here is the link to the corresponing simplification item of LE-TRA:
https://launchpad.support.sap.com/#sic/itemSet('0050569455E21ED5B3E17678391F
809E','false')
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 876
35.Logistics – WM
35.1 S4TWL - Task & Resource Management
Application Components:LE-TRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889253
S4TWL - Task & Resource
Management
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Task and Resource Management (LE-TRM) 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).
Business Process related information
No immediate influence on business processes expected related to Task and Resource
Management. The functionality Task and Resource Management (LE-TRM) is still
available within the SAP S/4HANA architecture stack as part of the compatibility
packages. All related functionalities can be used in an unchanged manner for a limited
period of time under the conditions of the compatibilty packages (see SAP note 2269324
for more information).
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you need to decide,
if you want to continue using Task and Resource Management (LE-TRM) for a limited
period of time under the conditions of the compatibility packages (see SAP note 2269324
for more information), or if you want to migrate to Extended Warehouse Management
(SAP EWM).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 877
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Once you migrate to Extended Warehouse Management (SAP EWM), but latest with
expiry of the compatibility scope license (see SAP note 2269324 for more information),
you need to remove all usages of Task & Resource Management development objects
delivered by SAP from your custom code, as these are no longer supported after expiry of
the compatibility scope license. Such usages are shown by the SAP S/4HANA specific
custom code checks in ABAP Test Cockpit (see SAP note 2241080).
Other Terms
LE-WM, Stock Room Management
35.2 S4TWL - Warehouse Control Interface
Application Components:LE-WM-IFC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889468
S4TWL - Warehouse Control Interface
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The integration of external systems via IDOCs in 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).
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 878
No immediate influence on business processes expected related to the Integration of
external systems via IDOCs. The functionality Integration of external systems via IDOCs
in Warehouse Management (LE-WM) is still available within the SAP S/4HANA
architecture stack as part of the compatibility packages. All related functionalities can be
used in an unchanged manner for a limited period of time under the conditions of the
compatibility packages (see SAP note 2269324 for more information).
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you need to decide,
if you want to continue using the integration of external systems via IDOCs in
Warehouse Management (LE-WM) for a limited period of time under the conditions of
the compatibility packages (see SAP note 2269324 for more information), or if you want
to migrate to Extended Warehouse Management (SAP EWM).
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Other Terms
LE-WM, Stock Room Management
35.3 S4TWL - Decentral WM
Application Components:LE-WM-IFC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889540
S4TWL - Decentral WM
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 879
This note is only relevant if you use have dedicated ERP instances for Warehouse
Management and others for Enterprise Resource Management. In this setup warehouse
logistics with LE-WM is running on an own decentral ERP instance connected to a
central ERP instance. The usage of Warehouse Management (LE-WM) as decentralized
Warehouse Management is not the target architecture anymore within SAP S/4HANA,
on-premise edition. The (already available) alternative functionality is Extended
Warehouse Management (SAP EWM). Connecting a decentral Warehouse Management
is still target archeitecture within SAP S/4HANA, on-premise edition.
Business Process related information
You mustn't migrate the decentralized Warehouse Management to SAP S/4HANA.
Instead stay on ECC with the decentralized Warehouse Management (taking current end
of maintenance into consideration) and do the system conversion to SAP S/4HANA only
for your central instance where you control your business.
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you have two
options, if you currently use Warehouse Management (LE-WM) as a decentralized
system.
You can proceed using LE-WM as decentralized Wareohouse Management System. In
this case this decentralized system needs to stay on ERP and mustn't be converted to
S/4HANA. The other option is to migrate to Extended Warehouse Management (SAP
EWM).
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Once you migrate to Extended Warehouse Management (SAP EWM), but latest with
expiry of the compatibility scope license (see SAP note 2269324 for more information),
you need to remove all usages of Decentral WM development objects delivered by SAP
from your custom code, as these are no longer supported after expiry of the compatibility
scope license. Such usages are shown by the SAP S/4HANA specific custom code checks
in ABAP Test Cockpit (see SAP note 2241080).
Other Terms
LE-WM, Stock Room Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 880
35.4 S4TWL - Wave Management
Application Components:LE-WM-TFM-CP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889652
S4TWL - Wave Management /
Collective Processing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The functionality of Wave Management / collective Processing in 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 Wave Management in Extended
Warehouse Management (SAP EWM).
Business Process related information
No immediate influence on business processes expected related to Wave Management /
collective Processing. The functionality Wave Management / collective Processing of
Warehouse Management (LE-WM) is still available within the SAP S/4HANA
architecture stack as part of the compatibility packages. All related functionalities can be
used in an unchanged manner for a limited period of time under the conditions of the
compatibility packages (see SAP note 2269324 for more information).
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you need to decide,
if you want to continue using Wave Management / collective Processing in Warehouse
Management (LE-WM) for a limited period of time under the conditions of the
compatibility packages (see SAP note 2269324 for more information), or if you want to
migrate to Extended Warehouse Management (SAP EWM).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 881
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Once you migrate to Extended Warehouse Management (SAP EWM), but latest with
expiry of the compatibility scope license (see SAP note 2269324 for more information),
you need to remove all usages of Wave Management development objects delivered by
SAP from your custom code, as these are no longer supported after expiry of the
compatibility scope license. Such usages are shown by the SAP S/4HANA specific
custom code checks in ABAP Test Cockpit (see SAP note 2241080).
Other Terms
LE-WM, Stock Room Management
35.5 S4TWL - Cross Docking
Application Components:LE-WM-CD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889636
S4TWL - Cross Docking
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
The functionality of Cross Docking in 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 Cross Docking in Extended Warehouse Management (SAP EWM).
Business Process related information
No immediate influence on business processes expected related to Cross Docking. The
functionality of Cross Docking in Warehouse Management (LE-WM) is still available
within the SAP S/4HANA architecture stack as part of the compatibility packages. All
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 882
related functionalities can be used in an unchanged manner for a limited period of time
under the conditions of the compatibility packages (see SAP note 2269324 for more
information).
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you need to decide,
if you want to continue using Cross Docking in Warehouse Management (LE-WM) for a
limited period of time under the conditions of the compatibility packages (see SAP note
2269324 for more information), or if you want to migrate to Extended Warehouse
Management (SAP EWM).
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Once you migrate to Extended Warehouse Management (SAP EWM), but latest with
expiry of the compatibility scope license (see SAP note 2269324 for more information),
you need to remove all usages of Cross Docking development objects delivered by SAP
from your custom code, as these are no longer supported after expiry of the compatibility
scope license. Such usages are shown by the SAP S/4HANA specific custom code checks
in ABAP Test Cockpit (see SAP note 2241080).
Other Terms
LE-WM, Stock Room Management, LE-WM-DCK
35.6 S4TWL - Yard Management
Application Components:LE-YM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889637
S4TWL - Yard Management
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 883
The functionality of Yard Management in 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 Yard Management in Extended Warehouse Management (SAP EWM).
Business Process related information
No immediate influence on business processes expected related to Yard Management.
The functionality Yard Managemen in Warehouse Management (LE-WM) is still
available within the SAP S/4HANA architecture stack as part of the compatibility
packages. All related functionalities can be used in an unchanged manner for a limited
period of time under the conditions of the compatibility packages (see SAP note 2269324
for more information).
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you need to decide,
if you want to continue using Yard Management in Warehouse Management (LE-WM)
for a limited period of time under the conditions of the compatibility packages (see SAP
note 2269324 for more information), or if you want to migrate to Extended Warehouse
Management (SAP EWM).
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Once you migrate to Extended Warehouse Management (SAP EWM), but latest with
expiry of the compatibility scope license (see SAP note 2269324 for more information),
you need to remove all usages of Yard Management development objects delivered by
SAP from your custom code, as these are no longer supported after expiry of the
compatibility scope license. Such usages are shown by the SAP S/4HANA specific
custom code checks in ABAP Test Cockpit (see SAP note 2241080).
Other Terms
LE-WM, Stock Room Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 884
35.7 S4TWL - Value Added Services
Application Components:LE-WM-VAS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2889638
S4TWL - Value Added Services
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
The functionality of Value added Services in 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 Value added Services in Extended Warehouse Management (SAP EWM).
Business Process related information
No immediate influence on business processes expected related to Value added Services.
The functionality Value added Services in Warehouse Management (LE-WM) is still
available within the SAP S/4HANA architecture stack as part of the compatibility
packages. All related functionalities can be used in an unchanged manner for a limited
period of time under the conditions of the compatibility packages (see SAP note 2269324
for more information).
Required and Recommended Action(s)
As part of your SAP S/4HANA system conversion or upgrade project you need to decide,
if you want to continue using Value added Services in Warehouse Management (LE-
WM) for a limited period of time under the conditions of the compatibility packages (see
SAP note 2269324 for more information), or if you want to migrate to Extended
Warehouse Management (SAP EWM).
If your decision is to migrate to Extended Warehouse Management (SAP EWM), plan
accordingly for this in your project.
Please check as well the Release information and restrictions for EWM in SAP
S/4HANA of the S/4HANA Release you will implement.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 885
Once you migrate to Extended Warehouse Management (SAP EWM), but latest with
expiry of the compatibility scope license (see SAP note 2269324 for more information),
you need to remove all usages of Value Added Services development objects delivered
by SAP from your custom code, as these are no longer supported after expiry of the
compatibility scope license. Such usages are shown by the SAP S/4HANA specific
custom code checks in ABAP Test Cockpit (see SAP note 2241080).
Other Terms
LE-WM, Stock Room Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 886
36.Portfolio and Project Management (PPM)
36.1 S4TWL - Web Dynpro Applications for Resource Maintenance in SAP
Portfolio and Pr
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2358376
S4TWL - Web Dynpro Applications for
Resource Maintenance in SAP Portfolio
and Project Management for SAP
S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
Please see note 2379542 for further information on Business Partner in SAP Portfolio and
Project Management for SAP S/4HANA. No further actions expected.
How to determine relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 887
This transition worklist item is relevant for you, if you are using the WebDynpro
applications 'Create resource' or 'Edit resource'.
36.2 S4TWL - Workforce Deployment (WFD) integration in SAP Portfolio
and Project Mana
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2358519
S4TWL - Workforce Deployment (WFD)
integration in SAP Portfolio and Project
Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Description
Workforce Deployment is not longer available for Resource Management in Project
Management of SAP Portfolio and Project Management for SAP S/4HANA.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions expected.
How to Determine Relevancy
Transition Worklist item is relevant, if you use Workforce Deployment.
Related SAP Notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 888
Other Terms
WFM Core
36.3 S4TWL - Integration to SAP cFolders in SAP Portfolio and Project
Management for
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2358921
S4TWL - Integration to SAP cFolders in
SAP Portfolio and Project Management
for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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 integration between Portfolio and Project Management and
SAP Enterprise Product Development collaboration as a substitute for selected
collaboration scenarios.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 889
How to Determine Relevancy
This Transition Worklist item is relevant if cFolders and SAP Portfolio and Project
Management is used.
36.4 S4TWL - KM Documents in SAP Portfolio and Project Management for
SAP S/4HANA
Application Components:PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2354985
S4TWL - KM Documents in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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 2445069 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. You can find more information in the Upgrade Master
Guide of the current start release. If the start release is SAP RPM 4.5 and the documents
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 890
should also be moved, first an upgrade to one of the releases SAP Portfolio and Project
Management 5.0/6.0/6.1 is required. You can find more information in the Conversion
Guide.
How to Determine Relevancy
This Simplification Item is relevant if in the customizing of global settings the value of
the setting Area:0007, Name:0022 is empty (not 'X').
Other Terms
KM, KPRO
36.5 S4TWL - SRM Integration in SAP Portfolio and Project Management
for SAP S/4HANA
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2359354
S4TWL - SRM Integration in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Description
The SRM Integration for external service procurement is not available in SAP Portfolio
and Project Management for SAP S/4HANA.
SAP Note 2445069 provides a pre-conversion check for this feature.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 891
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.
Other Terms
SRM, Supplier Relationship Management
36.6 S4TWL - cFolders not available anymore in SAP Portfolio and Project
Management f
Application Components:PLM-CFO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2348430
S4TWL - cFolders not available
anymore in SAP Portfolio and Project
Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Reason and Prerequisites
Renovation and Simplification of Functionality
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 892
With SAP Portfolio and Project Management for SAP S/4HANA, the cFolders
component is not available anymore. SAP recommends to evaluate integration between
Portfolio and Project Management and SAP Enterprise Product Development as a
substitute for selected collaboration scenarios.
SAP Note 2445069 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:
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.
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 Enterprise Product Development (EPD). Integration between SAP EPD
collaboration and project elements is available via object links as of SAP S/4HANA
2021, with SAP S/4HANA 2021 FPS1 integration to portfolio items and initiatives is
planned. Further information is available via help.sap.com.
How to Determine Relevancy
This Simplification Item is relevant if:
cFolders is used if entries exist in Table CFX_COL, and column
TO_BE_ARCHIVED is not set to 'X' (check with SE16)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 893
36.7 S4TWL - Global Settings in SAP Portfolio and Project Management for
SAP S/4HANA
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2359662
S4TWL - Global Settings in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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
Delivered Default Settings
Value
Availability in
S/4HANA PPM
2
Master
Switches
5
Integration with
Other Components
(see SAP Note
1391444)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the features
require further
configuration.
2
Master
Switches
7
Integration with PS
and FI/CO (see SAP
Note 1427365)
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 894
2
Master
Switches
8
Enhanced Capital
and Resource Mgmt
Switch (see SAP
Note 1457426)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
2
Master
Switches
13
Flag is Obsolete
(SAP Note 1759150)
Switch is obsolete
and will be
deleted.
2
Master
Switches
14
Flag is Obsolete -
Change Documents
for Financial and
Capacity Planning
Switch is obsolete
and will be
deleted.
2
Master
Switches
15
Milestone Filter for
Tasks ('X'=On, '
'=Off)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
2
Master
Switches
16
Accumulate the
Number of Objects
in the Dashboard
('X'=On, ' '=Off)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
2
Master
Switches
17
Flag is obsolete
(SAP Note 1780409)
Switch is obsolete
and will be
deleted.
2
Master
Switches
18
Flag is Obsolete -
Automatic Refresh of
Project Dashboards
('X'=On, ' '=Off)
Switch is obsolete
and will be
deleted.
2
Master
Switches
21
Integration with PLM
Engineering Record
( ‘X’ = ON, '' = OFF)
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)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 895
the feature
requires further
configuration.
6
User Interface
Settings
21
DEPRECATED:
Display Additional
Information on Gantt
Chart (' ': No, 'X':
Yes)
Switch is obsolete
and will be
deleted.
6
User Interface
Settings
23
Flag is obsolete
(SAP Note 1756616)
Switch is obsolete
and will be
deleted.
6
User Interface
Settings
24
Flag is obsolete
(SAP Note 1769591)
Switch is obsolete
and will be
deleted.
6
User Interface
Settings
26
Display Additional
Information on Multi-
Project Monitor (' ':
No, 'X': Yes)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
28
Adjustment of
Structure Tree Area
by Splitter
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
29
Delete Button in
Project Dashboard
('X'=Yes, ' '=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
30
Data Aggregation in
Projects
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
31
Fullscreen Mode for
Graphical View
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 896
the feature
requires further
configuration.
6
User Interface
Settings
32
Move-Up/Move-
Down Buttons in
Project ('X'=Yes, '
'=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
33
Summary of Project
Data in Multi-Project
Monitor ('X'=Yes, '
'=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
34
Concurrent Status
Changes for Multiple
Tasks ('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
35
Display Mirrored
Task Relationships
in MP Monitor
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
36
Assignment of
Multiple Roles to
Tasks at a Time
(‘X’=Enabled, ‘
‘=Disabled)
Switch will be
removed. Feature
will be
activated by
default. In most
cases, using the
feature requires
further
configuration.
6
User Interface
Settings
37
Allow Constraint
Icons without Add.
Info. 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 897
6
User Interface
Settings
38
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.
6
User Interface
Settings
40
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.
6
User Interface
Settings
41
One-Click
Completion of
Subordinate Project
Elements (' '=No,
'X'=Yes)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
6
User Interface
Settings
42
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.
7
General
Default Values
17
SAP Notes
Language
Independent
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
7
General
Default Values
22
Document
Alignment(' ': KM,
'X': KPRO)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
7
General
Default Values
23
Default number of
columns initially
displayed in
Switch is obsolete
and will be
deleted.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 898
Financial and
Capacity Planning
7
General
Default Values
27
Check-in/Check-out
of Documents (' ':
Normal, 'X': HTTP-
Based)
Switch will be
Removed.
Feature will no
longer be
available.
7
General
Default Values
28
HTTP Destination for
SAP
BusinessObjects
Explorer
Switch will be
Removed.
Feature will no
longer be
available.
7
General
Default Values
31
Flag is obsolete
(SAP Note 1677356)
Switch is obsolete
and will be
deleted.
7
General
Default Values
36
Flag is obsolete:
Activate calculation
of derived capacity
attribute
Switch is obsolete
and will be
deleted.
7
General
Default Values
38
Flag is obsolete
(SAP Note 1755486)
Switch is obsolete
and will be
deleted.
7
General
Default Values
39
Activate Multiple
Object Selection for
Reporting Cockpit
('X' =Yes, ' ' = No )
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
7
General
Default Values
40
Flag is obsolete
Switch is obsolete
and will be
deleted.
7
General
Default Values
46
Override
Authorizations for
Documents in Item
Versions ('X'=Yes, '
'=No)
Switch will be
removed. Feature
will be activated
available by
default. In most
cases, using the
feature requires
further
configuration.
9
Portfolio Item
Project
Integration
9
Use Project
Calendar for Linked
Item ('X'=Yes, ' '=No)
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 899
11
Staffing and
Resource
Management
1
Updating Staffing
According To Tasks
('X'=Enabled,
' '=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
2
Confirmed Role
Efforts in Staffing
Overview of Projects
('X'=Yes, ' '=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
3
Export of Cross-
Project
Resource/Staffing
Data ('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
4
Consider User
Group Authorization
in Resource
Management (Yes =
'X', No = ' ')
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
5
Personalized Layout
for Resource
Management
Screens ('X'=Yes, '
'=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
6
SAP Notes in Cross-
Project Staffing
Overview ('X'=Yes, '
'=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
7
Updating Multiple
Roles According to
Tasks ('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 900
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
8
Project Number as
Search Criterion in
Role Search
('X'=Yes, ' '=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
11
Staffing and
Resource
Management
12
Retain Node
Expansion After
Saving in Overview
Screens ('X'=Yes, '
'=No)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
12
Scheduling
and Project
Structuring
1
Automatic
Scheduling of All
Project Elements
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
12
Scheduling
and Project
Structuring
3
Creation/Deletion of
Multiple
Relationships
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
12
Scheduling
and Project
Structuring
4
Optimization of Task
and Milestone
Relationships
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
12
Scheduling
and Project
Structuring
5
Changing
Scheduling Type in
Project ('X'=Enabled,
' '=Disabled)
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 901
12
Scheduling
and Project
Structuring
6
Preserve
Relationships When
Canceling Tasks
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
13
Additional
Features
1
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.
13
Additional
Features
2
Export/Import of
Templates
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
13
Additional
Features
4
Comparison with
Actual Dates in
Graphical View
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
13
Additional
Features
5
Export of Multi-
Project Monitor Data
('X'=Enabled, '
'=Disabled)
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
13
Additional
Features
6
Export of Resource
Planning Data
('X‘=Enabled, '
'=Disabled)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
13
Additional
Features
7
Export of Graphical
View ('X' =Enabled, '
' =Disabled)
X
Switch will be
removed. Feature
will be activated
by default. In
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 902
most cases, using
the feature
requires further
configuration.
13
Additional
Features
8
Export of Evaluation
Data ('X‘=Enabled, '
'=Disabled)
X
Switch will be
removed. Feature
will be activated
by default. In
most cases, using
the feature
requires further
configuration.
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.
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.
How to Determine Relevancy
This Transition Worklist item is relevant if you are using SAP Portfolio and Project
Management for SAP S/4HANA.
Related SAP Notes
Conversion pre-checks
SAP Note 2321885
Http-based Check-
In/Check-out
SAP Note 2353984
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 903
36.8 S4TWL - Fiori apps of UI FOR SAP PORTF PROJ MGMT 6.0 in SAP
Portfolio and Projec
Application Components:PPM-PFM, PPM-PRO, PPM-FIO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2360044
S4TWL - Fiori apps of UI FOR SAP
PORTF PROJ MGMT 6.0 in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 904
If you are using the apps for the Program Manager role, check the Web Dynpro
applications.
How to Determine Relevancy
If you are using Fiori applications, check on the frontend system in the service catalog
(transaction /IWFND/MAINT_SERVICE) whether the ODATA Services
PPM_PFMITPR_CRE, PPM_PFMITPR_CHG, PPM_PFMDCPT_APV and
PPM_PROTSK_CNF are used.
36.9 S4TWL - Portfolio Structure Graphic in SAP Portfolio and Project
Management for
Application Components:PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2360046
S4TWL - Portfolio Structure Graphic in
SAP Portfolio and Project Management
for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 905
How to determine Relevancy
This SAP S/4HANA Transition Worklist item is relevant if you are using portfolio
management.
36.10S4TWL - SAP Smart Forms in SAP Portfolio and Project Management
for SAP S/4HANA
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2359421
S4TWL - SAP Smart Forms in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions expected.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 906
To determine if this Simplification Item is relevant please check if you use SAP Smart
Forms for printing Project Management information.
Other Terms
Smart Forms
36.11S4TWL - Resource Management Web Dynpro Views in SAP Portfolio
and Project Manage
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2359330
S4TWL - Resource Management Web
Dynpro Views in SAP Portfolio and
Project Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 907
DPR_RES_MAIN, VI_ROL_LIST_R, VI_ROL_LIST_S
36.12S4TWL - WebDAV and EasyDMS Integration in SAP Portfolio and
Project Management f
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2359479
S4TWL - WebDAV and EasyDMS
Integration in SAP Portfolio and Project
Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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
To determine if this Simplification Item is relevant please check if you use
WebDAV and EasyDMS Integration.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 908
36.13S4TWL - SAP Portal Integration in SAP Portfolio and Project
Management for SAP S
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2361179
S4TWL - SAP Portal Integration in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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 SAP Portfolio and Project Management
runs in an SAP NetWeaver Portal.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 909
36.14S4TWL - cRoom Integration in SAP Portfolio and Project Management
for SAP S/4HAN
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2361186
S4TWL - cRoom Integration in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 910
36.15S4TWL - xPD Integration in SAP Portfolio and Project Management
for SAP S/4HANA
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2361181
S4TWL - xPD Integration in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Description
In SAP Portfolio and Project Management for SAP S/4HANA, the SAP xPD integration
is no longer available.
Business Process-Related Information
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 911
36.16S4TWL - Xcelsius Integration in SAP Portfolio and Project
Management for SAP S/4
Application Components:PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2361194
S4TWL - Xcelsius Integration in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
36.17S4TWL - SAP BusinessObjects Explorer Integration in SAP EPPM
Application Components:PPM-PRO
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 912
Note Type
Note Number
Note Description
Business Impact
2361202
S4TWL - SAP BusinessObjects Explorer
Integration in SAP Portfolio and Project
Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
36.18S4TWL - Project simulation in SAP Portfolio and Project Management
for SAP S/4H
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2361201
S4TWL - Project simulation in SAP
Portfolio and Project Management for
SAP S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 913
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
36.19S4TWL - Deletion of obsolete packages in EPPM
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368899
S4TWL - Deletion of obsolete packages
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 914
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
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions necessary.
Related SAP Notes
36.20S4TWL - Business Partner in SAP Portfolio and Project Management
for SAP S/4HANA
Application Components:PPM-PFM, PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2379542
S4TWL - Business Partner in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Description
What has changed in Business User Management in SAP S/4HANA?
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 915
To get an understanding on the background of the changes in Business User Management
and how to handle business users and business partners please refer to the Business
Impact note:
https://launchpad.support.sap.com/#/notes/2570961 Simplification item S4TWL -
Business User Management
How do the changes in Business User Management in SAP S/4HANA impact
handling of business partners in SAP Portfolio and Project Management?
In addition to what is mention in note 2570961, it is important to know that it is not
possible any longer to create and maintain business partners of role category WFM001
‘Resource’ with user assignment by using transaction BP.
With SAP S/4HANA 1809 FPS01 Fiori app ‘Maintain Resources’ has been introduced to
create new resources and edit existing resources (business partner with role category
WFM001 ‘Resource’) with user assignment.
Important to know:
When a business partner has been created with app Maintain Resource, this business
partner is not assigned and cannot be assigned to an existing business partner of role
category employee.
In case a business partner of role category BUP003 ‘Employee’ exists, it is possible to
maintain in addition role category ‘Resource’ by using transaction BP
Required and Recommended Action(s)
SAP recommends to evaluate the options described in the above mentioned simplification
note https://launchpad.support.sap.com/#/notes/2570961 and in addition the above
mentioned option for business partners of role category WFM001 ‘Resource’ in SAP
Portfolio and Project Management.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 916
This Simplification Item is relevant if business partners of type BUP003 'Employee' and
type WFM001 'Resource' have been used in SAP Portfolio and Project Management.
Other Terms
Business Partner Approach, Resources
36.21S4TWL - Simplified ACLs (Access Control Lists) concept in SAP
Portfolio and Proj
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2343374
S4TWL - Simplified ACLs (Access
Control Lists) concept in SAP Portfolio
and Project Management for SAP
S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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) All Authorization holders have same weight. For example priority of ‘User’ level
authorization before ‘User Group’ authorization will be skipped.
b) Local Authorizations are no longer stronger than inherited ones. All activities are
inherited down from all levels above.
c) Authorizations related to organizational units of project elements are not available in
SAP Portfolio and Project Management for SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 917
d) 'None' activity is not available in SAP Portfolio and Project Management for SAP
S/4HANA.
e) Versions have no own authorizations any more but refer to authorization of
corresponding operative project.
f) User Groups are only considered up to the third level until level 3.
d) Activity hierarchy Admin - Write - Read is fixed for Fiori user interfaces. There is no
restriction for Web Dynpro user interfaces.
e) Dedicated Authorizations for folders and documents are not supported any more. They
inherit the authorizations from their parent project element, e.g. task.
f) New Super User concept available.
SAP Note 2445069 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.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 918
S4TC, S/4 Transition, Pre-conversion check, Pre-check, Pre-transformation check to S/4,
S/4 PPM, S4PPM, S/4 Portfolio and Project Management
Authorization Inheritance Information Migration, /S4PMM/AUTH_REF, report
DPR_PRE_CHECK_S4MIG_AUTHREF
36.22S4TWL - Handling of actual date in scheduling (EPPM)
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2630630
S4TWL - Copying of Actual Task Dates
to Calculated Dates in SAP Portfolio and
Project Management in SAP S/4HANA
Symptom
You want to convert your system landscape from SAP Portfolio and Project Management
to SAP Portfolio and Project Management in SAP S/4HANA. As of SAP S/4HANA
1809, the following SAP S/4HANA Transition Worklist item is applicable in this case.
It is also applicable when you upgrade your system from SAP Portfolio and Project
Management for SAP S/4HANA or from a SAP S/4HANA release below 1809.
Reason and Prerequisites
Revision and simplification of functionality
Solution
Description
With SAP S/4HANA 1809, the default system behavior during task confirmation and
project scheduling [in SAP Portfolio and Project Management] has changed as follows:
When a task is confirmed, the actual dates are no longer copied to the calculated dates.
As a result, actual dates are ignored by default when projects are scheduled.
This change takes effect if you have not implemented the BAdI DPR_SCHEDULING. If
you have implemented this BAdI, the system behavior remains unchanged
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 919
The default scheduling logic has changed since actual dates are no longer taken into
account by default.
Required and Recommended Action(s)
You only need to take action if you have not implemented BAdI DPR_SCHEDULING
and you do not want to use the new default behavior. Carry out one of the following steps
if you still want to copy actual values to calculated values and take them into account
during scheduling:
By default the “Copy Actual to Planned” checkbox is displayed on the “Dates and
Work” tab in the “Detail” view of the project header. Select this checkbox to
activate the previous behavior for individual projects.
To return to the previous behavior for all projects, implement BAdI
DPR_SCHEDULING. You do not need to implement the BAdI methods. Once
the BAdI implementation is active, the “Copy Actual to Planned” checkbox is no
longer available in the project header and actual dates are copied to calculated
dates by default.
For more information, see the documentation of the methods MOVE_ELEMENT and
BUTTON4MOVE_ELEMENT in Customizing for SAP Portfolio and Project
Management under Project Management -> Structure -> BAdI: Make Settings for
Scheduling.
How to Determine Relevancy
This Transition Worklist item is relevant, if there is no implementation of BAdI
DPR_SCHEDULING in your system.
36.23S4TWL - UI5 GANTT replacing JGANTT
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2768224
S4TWL - UI5 GANTT replacing JGANTT
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 920
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management 1.0 for SAP S/4HANA, SAP S/4
HANA1709 or SAP S/4HANA 1809. The following SAP S/4HANA Transition Worklist
item is applicable, if you want to upgrade to a JDK version higher than JDK 10 in the
context of the conversion process.
Reason and Prerequisites
Java Browser plugin deprecation, see SAP Note 2283330 - SAP statement about Oracle
plans to deprecate Java browser plugins
Solution
Business Value
As per note 2283330 - SAP statement about Oracle plans to deprecate Java browser
plugins , the graphical view of the project structure in SAP Portfolio and Project
Management for SAP S/4HANA or SAP S/4HANA will no longer work if you upgrade
to JDK 11.
The Java plugin (Applet) Gantt control will be replaced by an SAPUI5 Gantt control to
make the graphical view of the project structure available in SAP Portfolio and Project
Management for SAP S/4HANA or SAP S/4HANA regardless of the JDK version.
Description
As of SAP Portfolio and Project Management 1.0 SP06 for SAP S/4HANA or SAP
S/4HANA 1709 SP04 or SAP S/4HANA 1809 FPS2, an SAPUI5 Gantt chart control is
available for the visualization of the graphical view of the project structure in SAP
Portfolio and Project Management for SAP S/4HANA or SAP S/4HANA.
Business Process related information
You can use the graphical view of the project structure regardless of the JAVA version
used in your system landscape.
Required and Recommended Action
You can still use the JAVA-based Gantt chart, if needed. See the details in note 2645827
- GANTT Chart: Replacement of JGantt by UI5 Gantt: Availability and Prerequisites
How to Determine Relevancy
This Transition Worklist Item is relevant for you, if you use the graphical view in your
Project Management applications.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 921
36.24S4TWL - Object links to marketing campains in SAP CRM
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2823375
S4TWL - Object links to marketing
campains in SAP Customer
Relationship Management
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Description
The integration with marketing campaigns in SAP Customer Relationship Management
(SAP CRM) is not available in SAP Portfolio and Project Management for SAP
S/4HANA.
Business Process related information
It is no longer possible to link from Project Management to marketing campains in SAP
CRM.
Required and Recommended Action(s)
Data related to the integration with marketing campains 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 integration related data before you continue
with the system conversion.
Other Terms
CRM, Customer Relationship Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 922
36.25S4TWL - Changes compared to older releases than SAP Port. and Proj.
Mngt. 6.1
Application Components:PPM-PFM, PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349633
S4TWL - Changes compared to older
releases than SAP Port. and Proj. Mngt.
6.1
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 923
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.
36.26S4TWL - Control Plans in SAP Portfolio and Project Management for
SAP S/4HANA
Application Components:PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2353885
S4TWL - Control Plans in SAP Portfolio
and Project Management for SAP
S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 924
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.
Other Terms
S4TC, S/4 Transition, Pre-conversion check, Pre-check, Pre-transformation check to S/4,
S/4 PPM, S4PPM, S/4 Portfolio and Project Management, Control Plan, Control Plan UI
field customizing, PPM_FUNC_CNTR_PLAN_01, PPM_FUNC_CNTR_PLAN_02
36.27S4TWL - HTTP-Based Document Management in SAP Portfolio and
Project Management f
Application Components:PPM-PFM, PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2353984
S4TWL - HTTP-Based Document
Management in SAP Portfolio and
Project Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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 HTTP-based 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 925
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
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.
36.28S4TWL - Object Links to SAP Environmental Compliance in SAP
Portfolio and Projec
Application Components:PPM-PFM, PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2359065
S4TWL - Object Links to SAP
Environmental Compliance in SAP
Portfolio and Project Management for
SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 926
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.
Related SAP Notes
36.29S4TWL - Microsoft Project Import/Export in SAP Portfolio and Project
Management
Application Components:PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2358463
S4TWL - Microsoft Project Import/Export
in SAP Portfolio and Project
Management for SAP S/4HANA
Symptom
You want to convert your existing system landscape from SAP Portfolio and Project
Management to SAP Portfolio and Project Management for SAP S/4HANA. The
following SAP Portfolio and Project Management for SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
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. After downloading the the file, you can open it with you Microsoft Project
application.
Neither an ActiveX installation nor a definition of security lists for office controls is
required.
Business Process-Related Information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 927
No effects on business processes are expected.
Required and Recommended Action(s)
No further actions are expected.
How to determine relevancy
This transition worklist item is relevant, if Microsoft Project Import or Export is used.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 928
37.Procurement
37.1 S4TWL - MM-PUR WebDynpro Applications
Application Components:MM-PUR-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267445
S4TWL - MM-PUR WebDynpro
Applications
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
SAP S/4HANA Replacement
MMPUR_CPPR_MAIN_APPL
Collective
Processing of
Purchase
Requisition
SAP GUI report
BBP_EXTREQ_TRANSFER,
Fiori Application
MMPUR_SPPR_MAIN_APPL
Purchase
Requisition
Processing
SAP GUI transaction ME51N,
Fiori Application
MMPUR_ACCOUNT_ASSIGN_COMP
Account
assignments
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 929
MMPUR_ADDRESS_COMP
Display Address
MMPUR_BWLAUNCHER_APP
BW Starter
Smart Business? BW
Integration?
MMPUR_CFOLDERS_EP_EVENT
Document
Storage
MMPUR_CFOLDERS_URL_APP
Document
Storage
MMPUR_DISPLSCHEDLINE_APP
Display of
Delivery
Schedule Lines
for Item
MMPUR_DOCTRK_APP
Document
Tracing
MMPUR_DOC_TRACE
Graphical
document
tracing
MMPUR_FINDSUPPLIER_COMP
Find Supplier
MMPUR_FORECAST_APP
Expected
Contract
Release Orders
Smart Business?
MMPUR_MAVERICK_APP
Maverick
Buying Analysis
Smart Business?
MMPUR_PRICECOND_APP
Pricing
Conditions
MMPUR_RELEASEDOC_APP
Contract
Release Order
MMPUR_REL_STRAT_APP
Release
Strategy
MMPUR_SRCOFSUPPLY_APP
Display Sources
of Supply
MMPUR_UI_PR_APP
Purchase
Requisition
Processing
MMPUR_VNDCONF_APP
Process
Different Vendor
Confirmations
MMPUR_VNDCTCDTA_APP
Display of
Vendor Contact
Data Including
Contact
Persons
MMPUR_VNDPARTNER_APP
Display of
Partner Roles of
a Vendor
Related SAP Notes
Custom Code related information
SAP Note: 2228261
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 930
37.2 S4TWL - Classic MM-PUR GUI Transactions replacement
Application Components:MM-PUR-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267449
S4TWL - Classic MM-PUR GUI
Transactions replacement
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 are NO
longer supported. 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.
Transactions are NO longer supported in SAP S/4HANA
on-premise edition
ME21
ME22
ME23
ME24
ME25
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 931
ME27
ME28
ME51
ME52
ME53
ME54
ME59
MR01
MR1M
BAPIs are NO longer supported in SAP S/4HANA on-
premise edition
BAPI_PO_CREATE
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)
Specific data retrieval using BAPI_PO_GETDETAIL1 compared to
BAPI_PO_GETDETAIL is limited and hence new BAPI_PO_GETDETAIL1
may consume more time.
To improve response time, use BAdI me_bapi_po_cust method text_output if text
data retrieval is not required.
Other Terms
S4, S/4HANA, system conversion,
37.3 S4TWL - Dedicated SAP Supplier Lifecycle Management (SAP SLC)
business processes
Application Components:SLC-SUP
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 932
Note Type
Note Number
Note Description
Business Impact
2271188
S4TWL - Dedicated SAP Supplier
Lifecycle Management (SAP SLC)
business processes
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The following processes are supported with limitations:
- Supplier Evaluation
- Category Management
- Activity Management (internal)
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 (e.g. Supplier Registration and Supplier Data Maintenance)
- Several buy-side processes (e.g. Supplier Hierarchies, Supplier Classification, Area
of Validity in Supplier Evaluation, Supplier Qualification, Certificate Management,
External Tasks in Activity Management)
Business Value
It is a strategic decision of SAP to consolidate fuctionalities of Supplier Lifecycle
Management (SLC) within SAP S/4HANA Supplier and Category Management together
with SAP Ariba solutions.
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.
Coversion support is not available.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 933
Required and Recommended Action(s)
We recommend that you evaluate on a project basis whether you want to use Supplier
and Category Management in SAP S/4HANA or whether you want to use SAP SLC as a
standalone system to leverage the full functional scope of SAP SLC.
Related SAP Notes
Conversion Pre-Checks
Implementation Target Release S/4HANA <=1709: 2186288
Implementation Target Release S/4HANA >1709: 2441434
General Description: 2187627
37.4 S4TWL - Supplier Distribution via MDG-S
Application Components:SLC-SUP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267719
S4TWL - Supplier Distribution via MDG-
S
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 Value
To ensure data secureness it is necessary to use MDG-S (Master Data Governance for
Suppliers) for supplier distribution.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 934
SAP S/4HANA leverages MDG-S for supplier distribution. The MDG-S license is not
part of the SAP S/4HANA license.
Required and Recommended Action(s)
A project needs to be set up to implement MDG-S for supplier distribution.
Related SAP Notes
Custom Code related
information
If customers have enhanced interfaces for point-to-point supplier
distribution from SAP SLC to SAP ERP using the SLC integration
component in SAP ERP, communication with MDG-S must be enhanced
accordingly.
37.5 S4TWL - Authorization Concept for Supplier Invoice
Application Components:MM-IV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271189
S4TWL - Authorization Concept for
Supplier Invoice
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 behaviour of the system is more comprehensive. The new
concept introduces a header authorization object that enables the system to perform the
following authorization checks:
Check header data against the header authorization object (M_RECH_BUK). This
authorization object checks the common activities a user performs for the header
company code.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 935
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 Value
The new authority concept for supplier invoice enables a simplified
handling especially for invoice items w/o PO reference.
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.
37.6 S4TWL - Foreign Trade within SAP S/4HANA Procurement
Application Components:MM-FT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267740
S4TWL - Foreign Trade within SAP
S/4HANA Procurement
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 936
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Currently there are two software services for international trade transactions: Foreign
Trade and SAP Global Trade Services (GTS). Foreign Trade is part of standard Materials
Management (MM).
SAP GTS is an external service that can be installed on a separate instance. With SAP
S/4HANA on-premise edition 1511, the Foreign Trade solution will be not available
anymore because SAP Global Trade Services (GTS) is the successor for the business
requirement.
For Intrastat a customer can leverage functionality within SAP S/4HANA, on-premise
edition 1511.
Additional functions for import and export management are available with SAP Global
Trade GTS.
Business Value
It is a strategic decision of SAP to use SAP Global Trade Services for international trade
processes. Furthermore, selected international trade functionalities will be provided with
Foreign Trade in SAP S/4HANA.
Business Process related information
The customer needs to check whether 3rd party foreign trade systems are in use for
foreign trade processes. Because of the replaced foreign trade functionality in S/4HANA,
it is possible that 3rd party foreign trade system will need adjustments by the respective
3rd party Solution/Service Provider. However, SAP GTS can be connected to S/4HANA
to run the respective foreign trade processes.
Transaction not available in
SAP S/4HANA on-premise
edition 1511
VX99 FT/Customs: General overview
EN99 General Foreign Trade Processing
VI09X Change FT Data in Purchasing Doc.
VI08X Display FT data in purchasing doc.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 937
VI80X Change FT Data in Goods Receipt
VI79X Display FT Data in Goods Receipt
VI77X Change FT Data in Outbound Delivery
VI64X Display FT Data in Outbound Delivery
VI14X Change FT Data in Billing Document
VI10X Display FT Data in Billing Document
VIIM FT: Op. Cockpit: Purchase order
VIWE FT: Op. Cockpit: Goods Receipt
VIEX FT: Journal Export Actual
VE85 Change Statistical Value – Import
VE86 Display Statistical Value – Import
VE88 Change Statistical Value – Export
VE89 Display Statistical Value – Export
VE87 Change Stat.Value – Subcontracting
VEI3 Display Stat.Value – Subcontracting
OVE1 Commodity Code / Import code no.
VXCZ INTRASTAT: Form - Czech Republic
VXHU INTRASTAT: Form - Hungary
VXPL INTRASTAT: Form – Poland
VXSK INTRASTAT: Form – Slovakia
VEBE INTRASTAT: XML File - Belgium VECZ INTRASTAT:
File - Czech Republic
VEHU INTRASTAT: File – Hungary
VEPL Create INTRASTAT CUSDEC EDI PL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 938
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 939
VE45 INTRASTAT: Paper Form – Greece
VE46 INTRASTAT: File - Finland
VE95 Create INTRASTAT papers: Portugal
VICZ Create INTRASTAT CUSDEC EDI CZ
VIIE Create INTRASTAT XML IE
VEFU Foreign Trade: Add INTRASTAT Data
VIMM Decl. Recpts/Disptch Min. Oil Prod.
VE96 EXTRASTAT Data Select.: Init. Screen
VE04 EXTRASTAT: Data selection for export
VE05 EXTRASTAT: Create File – Germany
VE97 Create EXTRASTAT tape: Netherlands
VEXU Foreign Trade: Add EXTRASTAT Data
VE13 KOBRA data selection: export Germany
VE14 Create KOBRA file for Germany
VE15 Create disk - INTRA/EXTRA/KOBRA/VAR
VE21 VAR: Selection of bill. docs Switz.
VE22 Create VAR form for Switzerland
VE23 V.A.R.: File – Switzerland
VE18 SED data selection for USA exporter
VE25 SED: Selection: USA Carriers
VE19 Create SED form for USA
VE20 Create AERP file for USA
VE27 HMF: Selection – USA
VXJ1 MITI Declarations
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 940
VXJ2 Declaration of ImportBill.Docs Japan
VEIAI INTRASTAT Archiving
VEIAE EXTRASTAT Archiving
VE81 Check Report: General FT Data
VE73 Goods Catalog: Create Document
VE74 Goods Catalog: Create Diskette
VXA5 Document. Payments: Print Monitoring
VXA7 Documentary Payments: Simulation
ENSV Data Service
VX01N Create License
VX02N Change License
VX03N Display License
VX22N Change License Data
VX23N Display license data
VE31 Blocked SD Documents
VE30 Existing licenses
VE29 Assigned Documents for Each License
VE82 Check Report: Export Control Data
VI83 Check Customer Master/Legal Control
VX07 Simulation: License Check
VX09 Simulation: Embargo Check
VX08 Simulation: Boycott List Check
VX16 BAFA diskette: Selection
VX17 Create BAFA diskette
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 941
VX10 Countries of Destination for License
VX05 Customers for License
VX06 Export Control Classes for License
VE56 Check Export Control for Consistency
VI84 Doc.Payments: Check Customer Master
VX14N Maintain Financial Document
VX11N Create Financial Document
VX12N Change Financial Document
VX13N Display Financial Document
VI73N Foreign Trade: Maintain Long-Term Vendor Declaration
VI74N FT: Display Vendor Declaration
VI78 Foreign Trade: Countries
VI54 Customs Approval Numbers
VI55 Approval Number per Plant
VED1 Print Parameters for Export Documents
OVE1 Commodity Code / Import Code Number
VPAR Archiving Preference Logs
VFAI Archiving – INTRASTAT
VFAE Archiving – EXTRASTAT
FTUS Foreign Trade: Maintain User Data
ENCO Printing / Communication
ENGK Legal Control
ENLO Documentary payments
ENPR Preference Processing
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 942
ENGR Periodic Declarations
ENSV Foreign Trade Data Maintenance
ENZD Customs Objects: Documentation/Info.
VOIM Check Import Purchase Order
VOWE Check Goods Receipt
VI09X Change Import Purchase Order
VI53X Change Goods Receipt
VOLI Check Export Delivery
VOEX Check Export Billing Document
VI77X Change Export Delivery
VI14X Change Export Billing Document
VI85 Check Report: Vendor Master
VE81X Check Report: General Foreign Trade Data
VE82X Check Report: Export Control Data
VE83X Check Report: Preference Data
VI86 Cross-plant Check of Foreign Trade Data
VI82X Foreign Trade: Customer Master Consistency – General
VI83X Foreign Trade: Customer Master Consistency – Control
VI84X Foreign Trade: Customer Master Consistency - Letter of
Credit
VIE4 Periodic Declarations: Log of Incomplete Items
VE24X Foreign Trade: Information Commodity Code
VI24X Foreign Trade: Information Import Code Number
FTIM Journal: Purchase Orders
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 943
FTGR Journal: Goods Receipts
FTIM Import Order Analysis
FTGR Import Gds Receipt Analysis
FTEX Export Bill. Documents Journal
FTEX Exp.bill.doc.analysis
VE30 Expiring Licenses
VE29 Sales Orders for a License
VXA2 Financial Documents: List
VXA1 Financial Documents: SD Documents
VI74N Display Vendor Declaration
CAAT Foreign Trade: Call up FT Atrium
VIUL Foreign Trade: Data Upload
VIBA Send IDoc Output-AES-Initial Procg
VIBC Send IDoc Output-AES-Error in Procg
VIBB Send IDoc Output-AES-Repeat Procg
VIB7 Send IDoc Output - Initial Procg
VIB9 Send IDoc Output - Error in Procg
VIB8 Send IDoc Output - Repeat Procg
VIB4 Print Transaction: Initial Procg
VIB6 Print Transaction: Error in Procg
VIB5 Print Transaction: Repeat Procg
VIB3 Foreign Trade Output Status
VEII SAPMSED8: Call IMPINV01
VEIE SAPMSED8: Call EXPINV02
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 944
VX00 Preference Handling
LEAN Request long-term VendDecl. (vendor)
LEMA Dun long-term vendor decl. (vendor)
VE67 Aggregate Vendor Declarations
LEER Create long-term VenDecl. (customer)
VE55 Preference Determination: Individual
VE54 Preference Determination: Collective
VEB5 Calculate Assemblies Individually
VEB6 Calculate Assemblies Collectively
VEPR Customs log
VE91 Display Preference Values
VE90 Change preference values
VE83 Check Report: Preference Data
VE66 Preference Procedure
VE65 Preference Reg./Percentage Rates
VE64 Commodity Code/Customs Areas
VE94 Load Commodity Code for EU Countries
VEM4 Merge: EU - Commodity Code
VI94 Load Import Code Nos - EU Countries VIM4 Merge: EU
- Import Code Number
VA94 Load Commodity Codes for Japan
VAM4 Merge: Japan - Commodity Code
VP94 Load Import Code No. for Japan
VPM4 Merge: Japan - Import Code Number
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 945
VEU4 Load Commodity Code-Other Countries
VEI4 Merge: Remaining Commodity Codes
VIU4 Load Import Code No.-Other Countries
VII4 Merge: Rest - Import Code Number
VE24 Comm. Code Number Information (old)
VI24 Code Number Information – Import
VI20 Display Customs Quota
VI21 Display Pharmaceutical Products
VI22 Display Customs Exemption
VI23 Display Preferential Customs Duties
VI19 Display Third-country Customs Duties
VI18 Display Anti-dumping
VXA3 Financial Documents: Blocked Docs VXA2 Existing
Financial Documents
VE68 Request Vendor Declarations
VI75 Vendor Declarations - Dunning notice
VE84 Monitoring: Purchasing Info Records
VE83 Check Report: Preference Data
VXSIM Simulate Import
WZFT01 FT: Wizard - Declara. to Auth. (MM)
WZFT02 FT: Wizard - Declara. to Auth. (SD)
Required and Recommended Action(s)
Analysis of all currently used foreign trade processes.
Related SAP Notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 946
Custom Code related information
SAP Note: 2223144
37.7 S4TWL - RFQ Simplified Transaction
Application Components:MM-PUR-RFQ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2332710
S4TWL-RFQ Simplified Transaction
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Reason and Prerequisites
The previous concept was based on requests for quotations (RFQs) that included a
mandatory supplier field. In addition, the number of suppliers that could be entered for
each RFQ was limited to one. This restriction doesn’t fit to multiple sourcing-related
integration scenarios, such as Sourcing with SAP Ariba Sourcing.
Solution
New concept enables the system to send RFQs, that were created in a Fiori app, to
external sourcing platforms without mentioning exact supplier. On the sourcing platform,
the registered suppliers can submit their quotations which are later available to the
purchaser.
Following IDOCS and transactions related to RFQ are not considered as the target
architecture. This means that the functionality is currently available in SAP S/4HANA
but it is not considered as future technology and a functional equivalent is not available.
These IDocs are replaced with cXML messages:
REQOTE (Basic IDoc type = ORDERS05) is the IDoc for RFQ
QUOTES (Basic IDoc type = ORDERS05) is the IDoc for supplier quotation
It is planned to introduce SOAP-based messages to further replace cXML messages for
RFQ and supplier quotation.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 947
The following transactions are deprecated in SAP S/4HANA:
ME41
Create
ME42
Change
ME43
Display
ME44
Maintain Supplement
ME45
Release
ME47
Maintain
ME48
Display
ME49
Price Comparison List
ME4B
RFQs by Requirement Tracking Number
ME4C
RFQs by Material Group
ME4L
RFQs by Vendor
ME4M
RFQs by Material
ME4N
RFQs by RFQ Number
ME4S
RFQs per Collective Number
Business Process Related Information
If you want to use functionality related to sourcing of goods and services, you can use the
following apps:
Manage RFQs (F2049)
Monitor RFQ Items (F2425)
Request for Quotation Types (F4149)
Manage Supplier Quotations (F1991)
Compare Supplier Quotations (F2324)
Before you start to use Fiori apps mentioned above you need to close your open RFQs, that were
created via old transactions, and set them to status "Completed".
Required and Recommended Action(s)
You have to maintain the user roles. The new Fiori apps are accompanied by the
standard roles that contain relevant authorization objects. The relevant business roles are:
SAP_BR_PURCHASER (Purchaser) for the apps:
Manage RFQs (F2049)
Monitor RFQ Items (F2425)
Manage Supplier Quotations (F1991)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 948
Compare Supplier Quotations (F2324)
SAP_BR_BUYER (Strategic Buyer) for the app:
Request for Quotation Types (F4149)
Other Terms
SAP S/4HANA,System Conversion, Upgrade, Request for Quotation, Supplier Quotation
37.8 S4TWL - Webdynpro Applications for Purchase Requisition Transfer
from ERP to SRM
Application Components:MM-PUR-REQ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2200412
MM-Transition to S/4: Web Dynpro
Applications for Requisitioning
Symptom
You want to execute a transition of your ERP system to S/4 HANA.
Reason and Prerequisites
CPPR (Collective Processing of Purchase Requisitions) and SPPR (Single Processing Of
Purchase Requisitions ) no longer available in S/4HANA
Solution
SAP® S/4HANA is SAPs next-generation business suite, it is not a legal successor of
any SAP Business Suite product. It is a new product completely built on one of the most
advanced in-memory platform today – SAP HANA® – and modern design principles
with the SAP Fiori user experience (UX). SAP S/4HANA delivers massive
simplifications (customer adoption, data model, user experience, decision making,
business processes, and models) and innovations (Internet of Things, Big Data, business
networks, and mobile-first) to help businesses Run Simple in the digital economy.
In the approach to build SAP S/4HANA, SAP is re-architecting its solution for modern
business processes demanded by an increasing digitization of the world. Re-architecting a
solution that has been growing over the past 25 years means and sometimes evolved into
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 949
different data structures and architectures means as well that we have to decide on one
data structure and architecture moving forward. This is the only way how we can prepare
the solution for more simplicity and faster innovation cycles.
Following the SAP Fiori user experience and simplification approach, the portal content
and web dynpro applications for CPPR (Collective Processing of Purchase Requisition)
and SPPR (Single Processing Of Purchase Requisitions ) are no longer available in
S/4HANA.
Other Terms
CPPR, SPPR
37.9 S4TWL - Co-Deployment of SAP SRM
Application Components:MM-PUR-GF, SRM-CAT, SRM-EBP-SHP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271166
S4TWL - Co-Deployment of SAP SRM
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With SAP ERP it is possible to deploy SAP SRM as an AddOn. With SAP S/4 HANA
this AddOn deployment is not possible anymore. Therefore, a de-installation of the SRM
AddOn is necessary when converting the SAP ERP system to SAP S/4 HANA.
Business Process related information
SRM Self-Service Procurement capabilities are re-implemented within SAP S/4 HANA.
The functional scope is described in the feature scope description under the solution
capability of Self-Service Requisitioning. The functional scope is not identical with the
SAP SRM functionality. However it is planned to reach functional equivalence over time
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 950
by continuous improvement of the S/4 HANA capabilities. There are migration reports
available to transfer the business data from the SAP SRM AddOn to the SAP S/4 HANA
system.
Business Value
Providing Self-Service Requisitioning as an integral part of S/4 HANA has several
business benefits compared to the old AddOn deployment:
Data structures are simplified, e.g. no shopping cart data anymore, instead only
purchase requisition data is used
Seamless UI integration based on SAP Fiori (formerly GUI and WebDynpro) as well
as seamless process integration
No master data replication (formerly data replication between SRM AddOn and ERP
core)
Required and Recommended Action(s)
Perform Conversion pre-check to identify the constellation on SAP Business Suite start
release.
Related SAP Note
2216943 S4TC SRM_SERVER master check for S/4 system conversion checks
2251946 Informational note about migration of SAP SRM shopping carts to SAP S/4
HANA SSP
37.10S4TWL - Supplier Invoice New Archiving
Application Components:MM-IV, MM-IV-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2578291
Simplification Item: Supplier Invoice
Archiving
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 951
Supplier Invoice Archiving does not fully support ILM Integration
Solution
With upgade to 1809 ILM Integration is fully supported.
Please note: BAdI Implementations used in the old archiving reports (RM08RARC,
RM08RADE) are no longer supported. The new archiving reports (RM08RW47,
RM08RD47) use other BAdIs (ARC_MM_REBEL_WRITE,
ARC_MM_REBEL_CHECK) which need to be newly implemented.
37.11S4TWL - New Customizing for Exchange Rate Difference Handling
Application Components:MM-IV-LIV, CO-PC-ML
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3053636
S4TWL: New Customizing for Exchange
Rate Difference Handling
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The IMG activity "Configure How Exchange Rate Differences Are Treated" in the area
of Logistics Invoice Verification is redesigned with SAP S/4HANA 2021. Up to SAP
S/4HANA 2021 configuration was saved in table T169P. With SAP S/4HANA 2021 the
configuration is saved in table FMLC_ERD. Existing configuration from table T169P is
converted into FMLC_ERD automatically at upgrade
(XPRA FML_XPRA_T169P_TO_FMLC_ERD).
Required and Recommended Action(s)
Custom code that uses the old customizing of exchange rate difference handling has to be
adopted. The following fields of table T169P are affected:
XPLCU
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 952
KURST
CTHW
KDHW
CTML1
KDML1
CTML2
KDML2
Details are attached.
Existing implementations of Business Add-In (BAdI) MIRO_ERD_INVOICE
(enhancement spot ES_BADI_MM_EXCHANGE_RATE_DIFF) are not affected.
Parameter I_T169P is still filled whereas the new table FMLC_ERD is used. Additionally
the new parameter IS_ERD_SETTING was introduced that contains the customizing
information for the currency type (CURTP) the BAdI is called for.
Other Terms
ERD
37.12S4TWL - Deprecation of Fiori Apps and Machine Learning Scenarios
Application Components:MM-PUR-REQ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3376141
Deprecation of Fiori Apps and Machine
Learning Scenarios - SAP S/4HANA
2023
Symptom
You are using machine learning scenarios and the Fiori apps described in this note. The
following SAP S/4HANA Simplification Item is applicable in this case.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 953
Deprecation
Solution
Description
Following Fiori apps are deprecated as of release SAP S/4HANA 2023. This means,
these apps are still available and supported but no new features or enhancements can be
expected. We plan to make these obsolete in favor of the designated successor
functionality as of release SAP S/4HANA 2024:
Create Purchase Requisition (F1643) - Fiori app
My Purchase Requisitions (F1639) - Fiori app
Manage Catalog Item Recommendations (F3293) - Fiori app
Schedule Export of Catalog Item Images for Machine Learning (F4641) - Fiori app
Schedule Transfer of Purchase Requisitions for Intelligent Approval (F4155) - Fiori
app
Business Process related information
For more details about these deprecations, see the documentation available
in Deprecation of Machine Learning Scenarios | SAP Help Portal, Create Purchase
Requisition | SAP Help Portal and My Purchase Requisitions | SAP Help Portal.
Deprecated machine learning scenarios are Propose Creation of Catalog Items based on
Free-Text Purchase Orders (2XW), Propose Material Group in Free-Text Purchase
Requisitions (2XV), Image-Based Buying (3UH) and Intelligent Approval Workflow
(43E).
The app tiles are no longer available by default on the SAP Fiori launchpad. You can still
access the apps via the app finder and continue using them, but they will be no longer
supported as of SAP S/4HANA 2023. Therefore, we recommend that you switch to the
designated successor apps.
Required and Recommended Action(s)
We recommend you switch to the following successor apps.
Deprecated App
Successor App
Create Purchase Requisition (F1643)
My Purchase Requisitions -
New (F1639A)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 954
My Purchase Requisitions (F1639)
My Purchase Requisitions -
New (F1639A)
Manage Catalog Item Recommendations (F3293)
No Successor
Schedule Export of Catalog Item Images for Machine
Learning (F4641)
No Successor
Schedule Transfer of Purchase Requisitions for Intelligent
Approval (F4155)
No Successor
Other Terms
SAP S/4HANA, Deprecation
37.13S4TWL - CI Include Conflicts in EKKO_INCL_EEW_PS and
EKPO_INCL_EEW_PS
Application Components:MM-PUR-PO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3092824
Upgrade to S/4HANA 2022 and higher:
New Includes in Structures
'EKKO_INCL_EEW_PS' and
'EKPO_INCL_EEW_PS'
Symptom
In S/4HANA 2022, structures 'EKKO_INCL_EEW_PS' and 'EKPO_INCL_EEW_PS'
now contain Includes CI_EKKODB (on header level) and CI_EKPODB (on item level),
respectively. This may lead to an activation error in phase ACT_UPG for
tables/structures where both the structures are included. The error message in ACT_UPG
is DT963 "Field <your customer field> in table <your table where both structures are
included> is specified twice".
Another possible error is "CI_EKPODB" is not included in table "EKPO"
or "CI_EKKODB" is not included in table "EKKO".
Reason and Prerequisites
Reason: This change will allow On Premise customers to directly use custom fields in CI
Includes in Fiori applications without any data loss. These fields are then available for
both Fiori UI as well as GUI screens (VH).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 955
Prererquisite: It would be best to check the location of the CI_EKKODB /
CI_EKPODB includes before the upgrade and adjust them during the upgrade in
SPDD-phase to avoid the duplicate field error.
Solution
To make it clear, the right place for each include is this:
Purchase Order header: CI_EKKODB needs to be inside of
EKKO_INCL_EEW_PS, which is contained in EKKO table
Purchase Order item: CI_EKPODB needs to be inside of EKPO_INCL_EEW_PS,
which is contained in EKPO table
To avoid the error "Field is specified twice", proceed as follows if includes CI_EKKODB
(on header level) and CI_EKPODB (on item level) exist in your system:
In development systems, during phase ACT_UPG when prompted for SPDD, delete
the CI_EKKODB / CI_EKPODB Includes or the field(s) of CI_EKKODB /
CI_EKPODB from the table/Include where 'EKKO_INCL_EEW_PS'
or 'EKPO_INCL_EEW_PS are also included. Also delete the CI_EKKODB /
CI_EKPODB or the field(s) of CI_EKKODB / CI_EKPODB from the Extension
views in the CDS stack .
Make sure to remove only fields that are contained in CI_EKKODB /
CI_EKPODB from tables/Includes by these steps to avoid any data loss.
If you remove fields from an appended structure or from table, just save your
changes. DO NOT PERFORM 2-step activation at this time, this could
lead to data loss. Mass activation will be performed automatically later in
phase ACT_UPG.
If you delete the appended structure, there is a warning "Deleting the
appended structure results in reactivation of and adjustment of the table
<your table> on the database". In this situation this warning can be
ignored as an adjustment would only happen later during mass activation
when <your table> will contain CI_EKKODB / CI_EKPODB directly, so
the contents of CI_EKKODB / CI_EKPODB fields will not be lost.
Continue with ACT_UPG. The deletion of the appended structure or the change to
table/structures will be activated together with the standard change that
adds CI_EKKODB / CI_EKPODB to your table/Include, there should be no
activation error.
In case you didn't perform these steps at SPDD you can still perform them
after ACT_UPG was stopped with error DT963 "Field <ZZ-field> in table
<your table> is specified twice". In this case you might get the error
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 956
message DT002 "Table <your appended structure to table> does not
exist" when repeating the activation step ACT_UPG after deleting the
appended structure. If there is no activation error for other tables or
structures, especially no error for table, this DT002 error for the deleted
appended structure can be ignored.
These changes will be recorded in a transport request. It is advised to do these adjustments and
activation in one step in a single transport request. In follow-up systems, include the transport
containing the deleted appended structure or the change to table in the upgrade.
In case the CI_EKKODB / CI_EKPODB includes get deleted accidentally from
'EKKO_INCL_EEW_PS' or 'EKPO_INCL_EEW_PS' inside of EKKO / EKPO,
there are two options:
the upgrade can be repeated or
In the shadow system of the upgrade, customer owned objects but also SAP objects
may be modified in the so-called SPDD-phase: before activation! The goal is that
customers can transfer or adjust his/her modifications to the new release. In this
phase, it is possible to enter the CI_ includes into their respective *EEW*
includes inside of EKKO and EKPO. It is important to only save but not activate
until all modifications are done. Here, you can check whether the CI_EKKODB /
CI_EKPODB includes that should not be directly inside of EKKO and EKPO
table is really not there, otherwise delete it but save only, no activation. Then, in
the end, when all is done and checked: mass activate.
Related issues:
Since the CI_EKKODB / CI_EKPODB includes occur also in other tables, additional
problems may occur during the upgrade. Here some notes/ information to help you get
on:
3326565 Upgrade issue in MMPUR_ANA_EKET table from OP2022: CI Include
merged into EEW for EKKO & EKPO
3334975 Upgrade to S/4 HANA 2022: New Includes in Structures
'EKKO_INCL_EEW_X' and 'EKPO_INCL_EEW_X'
3319787 Upgrade error on structure PRITEMFORGR due to extension includes
3338301 Upgrade issue for CI_EKKODBX and CI_EKPODBX: duplicate fields
found -> tool
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 957
3345237 Upgrade to SAP S/4HANA 2022: Error when changing CI_EKPODB
includes. This note tackles the "package MLHELPDESK does not exist" and
"table MLREPEKPO does not exist" errors.
3282761 Object Activation Errors during Upgrade: Field is specified twice
Other Terms
Upgrade to 2022 S/4HANA and higher, CI Include, EKPO, EKKO, CI_EKPODB, EEW,
EKKO, ME21N,
SPDD, EKPO_INCL_EEW_PS, MMPUR_S_EXT_LCL_PO_HEADER,
MMPUR_S_EXT_LCL_PO_ITEM, PRITEMFORGR, MMPUR_ANA_EKET, MLHEL
PDESK, MLREPEKPO
37.14S4TWL - Co-Deployment of SAP Supplier Lifecycle Management (SAP
SLC)
Application Components:SLC-SUP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267413
S4TWL - Co-Deployment of SAP
Supplier Lifecycle Management (SAP
SLC)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 together with
SAP Ariba solutions. Customers who have deployed SAP Supplier Lifecycle
Management on SAP ERP and want to migrate to S/4HANA 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 958
to use it, but have to use MDG-S for supplier data integration. For more information, see
simplification item Dedicated SAP Supplier Lifecycle Management (SAP SLC) business
processes.
Business Process related information
The functional scope of Supplier and Category Management in SAP S/4HANA is
currently not identical with the SAP SLC functionalities.
Master categories in purchasing category are not available. As a successor, material
groups are available in purchasing categories.
Business Value
It is a strategic decision of SAP to provide functionalities of Supplier Lifecycle
Management (SLC) within SAP S/4HANA Supplier and Category Management together
with SAP Ariba solutions.
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
Implementation Target Release S/4HANA <=1709: 2186288
Implementation Target Release S/4HANA >1709: 2441434
General Description: 2187627
37.15S4TWL - Vendor evaluation based on LIS
Application Components:MM-PUR-GF-LIS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267414
S4TWL - Vendor evaluation based on
LIS
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 959
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Business Value
The usage of SAP S/4HANA offers real-time supplier evaluation capabilities without
building and referring to table and structure aggregates. Beside real-time capabilities, it
also provides much more analytical visualization options as LIS.
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 960
37.16S4TWL - ERP Shopping Cart
Application Components:MM-PUR-SSP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271168
S4TWL - ERP Shopping Cart
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Simplification item is applicable in this case - SI5: PROC_SC.
Reason and Prerequisites
The ERP Shopping Cart has been deprecated in S/4 HANA
Solution
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 ERP is associated to the business function LOG_MM_SSP_1 which
can be in status ON.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 961
/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
Business Value
The SAP ERP shopping cart was an own business object, which was very similar to the
Purchase Requisition business object. Following the S/4HANA simplification strategy,
SAP moved the SAP ERP shopping cart functionality into the S/4HANA Purchase
Requisition. So in S/4HANA only one business object for all procurement demands exist.
Required and Recommended Action(s)
Be aware that the Shopping Carts created in SAP ERP will not be available in S/4 HANA
anymore. You can't call the corresponding transactions and webdynpro applications
because they were deprecated.
Other Terms
SAP ERP conversion, S/4 simplification, MM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 962
37.17S4TWL - Internet Application Components (IAC)
Application Components:MM-PUR-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267441
S4TWL - Internet Application
Components (IAC)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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 Procurement Transaction
MEW1 Create Requirement Request
MEW2 Status Display: Requirement Requests
MEW3 Collective Release of Purchase Reqs.
MEW5 Collective Release of Purchase Order
MEW6 Assign Purchase Orders WEB
MEWP Web based PO
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2228250
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 963
37.18S4TWL - MDM Catalog
Application Components:MM-PUR-SSP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271184
S4TWL - MDM Catalog
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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, on-premise edition a limited functional scope might be available
compared to the SAP SRM MDM catalog. An available SAP SRM MDM catalog
instance can still be integrated with S/4HANA as a punch-out catalog via OCI.
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.
Business Value
Customers who are looking for a Catalog solution should take Ariba APC which is a
comprehensive e-catalog solution.
Required and Recommended Action(s)
None
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 964
37.19S4TWL - Pricing Data Model Simplification
Application Components:SD-BF-PR, SD-MD-CM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267442
S4TWL - Pricing Data Model
Simplification
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Description
See the information provided in the Sales & Distribution area in simplification item "Data
Model Changes in SD Pricing".
https://launchpad.support.sap.com/#/notes/2267442
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.
Required and Recommended Action(s)
See simplification item Data Model Changes in SD Pricing.
Related SAP Notes
General information
Carefully follow the instructions in SAP Notes 2188695,
2189301, and 2220005.
Conversion pre-checks
SAP Note: Pre-checks delivered with Note 2188735.
Custom code-related
information
SAP Note: 2220005
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 965
37.20S4TWL - Output Management Adoption in Purchase Order
Application Components:MM-PUR-PO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267444
S4TWL - Output Management Adoption
in Purchase Order
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Additionally to the existing output management based on NAST a new Output
Management solution is adopted S/4 HANA-wide. Thereby a unified solution can be
used for all Output Management activities. The existing Output Management solution
however still can be activated.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 966
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)
Up to release OP1709 you can find more information about how to activate the NAST-
based Output Management in the SAP Customizing Implementation Guide under
Materials Management -> Purchasing -> Purchase Order -> Activate or Deactivate SAP
S/4HANA-Based Output Management.
As of release OP1809 you can find this customizing setting under Cross-Application
components -> Output Control -> Manage Activation of Object Type. The NAST based
output management is now the default solution, but a system upgrade will not change the
previous selected output management.
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.
37.21S4TWL - CI Include Conflicts in Table MMPUR_ANA_E
Application Components:MM-PUR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3326565
Upgrade issue in MMPUR_ANA_EKET
table from OP2022: CI Include merged
into EEW for EKKO & EKPO
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 967
Symptom
Activation issue with duplicate fields in analytical table MMPUR_ANA_EKET while
upgrade to S/4HANA 2022
Reason and Prerequisites
Technically until S/4HANA 2022, the CI includes of DB tables EKKO & EKPO were
not included in respective extension includes EKKO_INCL_EEW_PS
& EKPO_INCL_EEW_PS. Since release S/4HANA 2022, CI include got merged into
respective extension includes.
Analytical table (MMPUR_ANA_EKET) is a denormalised table with EKKO,EKPO and
EKET data and it also contains the extension includes of EKKO & EKPO.
SAP proposes to use unique field names across CI Includes of EKKO & EKPO (see also
note 2899836 and 3101906). If you do not follow this proposal from S/4HANA 2022
onwards there will be an error during upgrade on the analytical table (due to field name
conflict).
Solution
The solution for this is to implement the attached correction in source release before
upgrading to S/4HANA 2022. There are two new specific extension stuctures & one
report delivered as part of this note. Once the note is implemented
report MMPUR_ANA_GEN_EEW_FIELDS has to be executed and verified whether the
custom fields of includes EKKO_INCL_EEW_PS & EKPO_INCL_EEW_PS are
appended to EKKO_INCL_EEW_PS_ANA & EKPO_INCL_EEW_PS_ANA
respectively. The new specific extension structures EKKO_INCL_EEW_PS_ANA
& EKPO_INCL_EEW_PS_ANA will only contain custom fields from extension includes
EKKO_INCL_EEW_PS & EKPO_INCL_EEW_PS, but not from CI includes
CI_EKKODB & CI_EKPODB.
If custom fields from CI_EKKODB & CI_EKPODB are also required to be included in
table MMPUR_ANA_EKET, these need be added manually via append mechanism.
Once the new structures with custom fields are ready in source release, the upgrade can
happen where old extension includes EKKO_INCL_EEW_PS & EKPO_INCL_EEW_PS
in table MMPUR_ANA_EKET are replaced with new
includes EKKO_INCL_EEW_PS_ANA & EKPO_INCL_EEW_PS_ANA.
Other Terms
MMPUR_ANA_EKET, CI_EKKODB, CI_EKPODB, phase ACT_UPG
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 968
38.Sales & Distribution
38.1 S4TWL - Business Role Internal Sales Representative
Application Components:SD-SLS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271150
S4TWL - Business Role Internal Sales
Representative
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
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 EhP2 and was enhanced in SAP ERP EhP3 and SAP ERP EhP4. Two options to run
this role existed, accessible through either the SAP Portal or by using the Business Client
(as part of SAP NetWeaver).
The related functionality is assigned to these Business Functions:
LOG_SD_SIMP_02 (EhP4)
LOG_SD_CI_01 (EhP3)
SD_01 (EhP2)
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. In the first S/4HANA release these roles offer a basic set of
transactions that are typically needed for the day-to-day work of a sales representative.
During the subsequent releases, these roles are enhanced with further suitable FIORI
apps. For more information about this new concept, see SAP Note 2223838.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 969
Transaction not available in SAP
S/4HANA
VPW1 Change View "Tasks"
VPWL 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 has activated one of the
following Business Functions:
LOG_SD_SIMP_02
LOG_SD_CI_01
SD_01
38.2 S4TWL - Webshops by Internet Sales or Web Channel Experience
Management
Application Components:WEC-APP-SLS-ERP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271161
S4TWL - Webshops by Internet Sales or
Web Channel Experience Management
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Description
Web shops resp. e-commerce solutions based on SAP Internet Sales (component CRM-
ISA), SAP E-Commerce (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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 970
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 1610 OP.
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 1610 OP).
Transaction not available in
SAP S/4HANA
Transactions
ISA_CAT_REPLICATION Replication of product catalogs
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 971
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.
38.3 S4TWL - Sales Activities
Application Components:SD-CAS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267375
S4TWL - Sales Activities
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 972
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 on-premise (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.
Transactions not supported in SAP S/4HANA:
OV/8 Test Data - Transfer Data - Cond.
OV/9 Display Test Data
OVCB Structure of Reporting View
OVCC Assign View to User
OVCD Definition of Reporting View
OVCE Control Update of Perform.Measures
OVCF Control Reporting - Info Blocks
OVCI C SD Set Workflow Action box
OVL5 Maintain Transit Time
SDCAS_MCQ Call MC/Q From Address Selection
V+01 Create Sales Call
V+02 Create Telephone Call
V+03 Create Sales Letter
V+11 Create Direct Mailing
V+21 Create Sales Prospect
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 973
V+22 Create Competitor
V+23 Create Business Partner
VC_2 Customer Fact Sheet PDF Version
VC/1 List of Customers (as of Release 1610)
VC/2 Customer Master Data Sheet (as of Release 1610) - Use Fiori App
"Customer 360 Object Page" instead.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 974
VC01N_M Edit Mailing
VC02 Change Sales Activity
VC03 Display 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
VN05 No.Assignment for Address List(SSup)
VN06 Create No.Interval-Sales Activities
VOC1 Customizing for List of Addresses
VUC2 Maintain Incompletion Log
VV51 Create Output for Sales Activity
VV52 Change Output: Sales Activity
VV53 Display Output: Sales Activity
VVCB Maintain Activity Authorization
Required and Recommended Action(s)
If sales support functionality is requested, we recommend that customers start evaluating
a side-by-side CRM on-premise scenario, or that they use Cloud for Customer.
Related SAP Notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 975
Custom code-related information
SAP Note: 2214585
38.4 S4TWL - Billing Document Output Management
Application Components:SD-BIL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2790427
S4TWL - Billing Document Output
Management
Symptom
In SAP S/4HANA, a new output management approach has been implemented, but the
old NAST technique is set as default.
Reason and Prerequisites
This note is relevant for you if your start release for the system conversion is an SAP
ERP release. It is also relevant if your start release is SAP S/4HANA and you do not
require "special" output channels.
The new output management for SAP S/4HANA, called SAP S/4HANA output control,
only supports the "pure" output channels, while the NAST-based output can also be used
for several kinds of post-processing. SAP S/4HANA output control 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 use NAST-based output management. If you don't need these kinds of
"special" output channels, you can use the new SAP S/4HANA output control.
Solution
As there are valid requirements and use cases for both frameworks, there is a new
customizing activity "Manage Application Object Type Activation" where the active
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 976
framework can be maintained.
You can find the Customizing under output control:
Transaction SPRO
SAP Reference IMG -> Cross-Application Components -> Output Control -> Manage
Application Object Type Activation
Choose "Application Active" if you want to switch to new output management for SAP
S/4HANA, which is called SAP S/4HANA output control.
Other Terms
Billing Document Output Management, SAP S/4HANA output control
38.5 S4TWL - SD Rebate Processing replaced by Settlement Management
Application Components:SD-BIL-RB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267377
S4TWL - SD Rebate Processing
Replaced by Settlement Management
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Business Value
The Settlement Management Solution provides a single point of entry to maintain and to
administrate contract-related conditions. Condition contract settlement allows to set up
different rebate scenarios and settlement processes to fulfill your business requirements
by customization. Flexible data sources, business selection criteria, settlement calendar
and further features allow a streamlined contract entry and contract processing. Condition
Contract Management offers an overview of actual business volume even for
retroactively contracts and a rich functionality to control open settlements, business
volume and accruals.
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 977
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, note 2267344).
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 Create Rebate Agreement
VB(D Extend Rebate Agreements
Required and Recommended Action(s)
See the attached documents for more detailed information.
Some countries like countries in Latin America require localization. For example Latin
American authorities require invoicing with pre-assigned number through transaction
IDCP. This functionality is not available as of now for settlement management
documents. Please verify if settlement management solution fulfills the local
requirements in the your specific countries and reach out to the SAP localization team in
case you have questions.
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
SAP Note: 2226380
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 978
38.6 S4TWL -Miscellaneous minor functionalities in SD Area
Application Components:SD-MD-CM, SD-SLS-GF, SD-BIL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267395
S4TWL - Miscellaneous Minor
Functionalities in SD Area
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Description
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 avaiable 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 979
38.7 S4TWL - SD Complaint Handling
Application Components:SD-BIL-IV-CP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267398
S4TWL - Industry-Specific SD
Complaint Handling
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenarion, the following
SAP S/4HANA Transition Worklist item applies.
Solution
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 Complaints Processing – Customer
Number
WCMP_RESULT Results Display for Mass Complaints
Processing
BAdI not available in SAP
S/4HANA
BADI_CMP_PROCESSING Add-In for Complaints
Processing
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 980
None
Related SAP Notes
Custom code-related information
SAP Note 2239184
38.8 S4TWL - SD Simplified Data Models
Application Components:SD-BF-MIG, SD-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267306
S4TWL - SD Simplified Data Models
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Business Value
Data model simplifications in Sales and Distribution (SD) offer the following benefits:
Reduced memory footprint through
elimination of index tables
elimination of status tables
simplified document flow
fewer aggregate tables
Increased performance due to the integration of status tables into document tables.
Field length extension of SD document category allows for functional scope
enhancements
with new code values for SD document category.
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 981
The following data model simplifications have been implemented for the SD area:
Elimination of status tables VBUK, VBUP: Status fields have been moved to the
corresponding header and item tables - VBAK and VBAP for sales documents,
LIKP and LIPS for deliveries, VBRK for billing documents.
This leads to increased performance, e.g.:
Selection of document header data and document header status requires one
SELECT statement (VBAK) instead of two SELECT statements (VBAK
and VBUK). Similar for the item tables.
Views containing document header data and document header status can be
built without JOIN condition.
Simplification of document flow table VBFA
Field length extension of SD document category:
Data element VBTYP (Char1) has been replaced by data element VBTYPL
(Char4);
Field VBTYP_EXT (Char4) has been eliminated
Elimination of redundancies – Document index tables VAKPA, VAPMA, VLKPA,
VLPMA, VRKPA, VRPMA
Elimination of redundancies
Rebate index table VBOX: See simplification item "SD Rebate Processing
replaced by Settlement Management", SAP Note 2267377.
LIS tables S066, S067: See simplification item "Credit Management", SAP
Note 2270544.
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)
Adapt customer code according to the custom code check results, see SAP Note
2198647 for a detailed description.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 982
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 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 and where 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.
Until target release S/4HANA 1610: 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.
As of target release S/4HANA 1709: The check for append fields is integrated into the
upgrade tools (SUM). The check is executed automatically as part of phase ACT_UPG. If
append fields to VBUK or VBUP are found SUM prompts a confirmation whether
adjustmants have been done and whether the upgrade/conversion can be continued.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 983
The check only finds appends fields if they belong to the namespaces Z* or Y*.
Append fields of a namespace /*/, e.g. /ABC/, do not lead to a confirmation prompt as the
upgrade tools cannot safely distinguish the different owner types of /*/ namespaces
(customers or partners or SAP-managed components).
The check is also not executed if there is already a SPDD transport integrated into the
conversion procedure.
(See above, "When and where do you have 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
SAP Note 2224436
Custom code-related
information
Customer code has to be adapted according to the cookbooks in
SAP Note 2198647.
38.9 S4TWL - VBFA - Indirect Docflow Relationships
Application Components:SD-BF-MIG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2469315
S4TWL - VBFA - Indirect Docflow
Relationships
Symptom
You have performed a system conversion to SAP S/4HANA, on-premise edition, with
one of the following target releases:
1511 SP00/SP01/SP02/SP03
1610 SP00/SP01
Or you have a new installation on S/4HANA where the start release is or was one of the
following releases:
1511 SP00/SP01/SP02/SP03
1610 SP00/SP01
The following SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 984
Reason and Prerequisites
In the Simplifications for S/4HANA, the field STUFE had been removed from the
database table VBFA (SD Document Flow).
Compare note 2267306.
In the initial releases of S/4HANA:
- only direct relationships are stored in VBFA
- indirect relationships are not stored in VBFA
- indirect relationships are deleted in the S/4HANA conversion
The field STUFE is introduced again and indirect relationships are stored again in table
VBFA as of the following releases and SP levels:
1709 (SP00)
1610 SP02 = FPS2 (feature pack stack 2)
1511 SP04
Via correction instructions of note 2418242 in 1610 SP00/SP01
Via correction instructions of note 2418242 in 1511 SP00/SP01/SP02/SP03
A reconstruction of missing docflow entries is necessary in the following cases:
System conversion from SAP ERP to 1610 SP00/SP01 or
System conversion from SAP ERP to 1511 SP00/SP01/SP02/SP03
New installation on 1610 SP00/SP01/SP02 or
New installation on 1511 SP00/SP01/SP02/SP03/SP04
For details about the reconstruction, see note 2418242.
Solution
Business Value
The change has the following benefits:
- Performance improvement compared with the initial delivery of S/4HANA 1511
- No further restrictions with respect to archiving of SD documents
Description
The table VBFA and its content changes incompatibly.
Business Process related information
No changes to business processes
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 985
Custom Code where data is retrieved directly from table VBFA must be checked and in
some cases must be adapted. Please check note 2470721 for details.
How to Determine Relevancy
The Simplification Item is likely relevant if you are using S/4HANA Sales and the
underlying SD document flow.
You have to check for custom code adaptation if your custom coding selects directly
from VBFA (see note 2470721).
You have to execute a reconstruction report for VBFA if your system history is:
You have performed a system conversion to SAP S/4HANA, on-premise edition, with
one of the following target releases:
1511 SP00/SP01/SP02/SP03
1610 SP00/SP01
Or you have a new installation on S/4HANA where the start release is or was one of the
following releases:
1511 SP00/SP01/SP02/SP03/SP04
1610 SP00/SP01/SP02
See note 2418242 for more information on the reconstruction report.
38.10S4TWL - Data Model Changes in SD Pricing
Application Components:SD-BF-PR, SD-MD-CM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267308
S4TWL - Data Model Changes in SD
Pricing
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 986
Business Value
Data model simplifications in Sales and Distribution(SD) pricing offer the following
benefits:
Since it is no longer a cluster table, the pricing result can now be directly accessed for
analytical purposes.
Enhanced field lengths for several fields allow for more flexibility in pricing and
condition technique.
Customer and document pricing procedure extensions allow for more flexible
pricing procedure determination.
The number of possible customer condition tables for pricing has
been roughly doubled.
The number of possible accesses in an access sequence has been enhanced
from 99 to 999.
The key of condition tables ('A-Tables') can now be 255 characters long
(previously 100).
The removal of redundant fields from condition header table:
reduces the memory footprint of condition records
prevents additional conversions and, therefore, downtime if field lengths from
pricing field catalogue entries need extension
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 by
the automatic data migration when moving to SAP S/4HANA.
The following DDIC changes and interface changes have been made to the condition
technique:
DDIC changes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 987
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.
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
VAKEY/VADAT are to be filled in addition to the still
existing short fields, the content of the long fields has
priority.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 988
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
Former
Length
New
Length
KOLNR, EVSNR, FSELNR
Number of access in access
sequence
NUMC2
NUMC3
KOBED, KOFRM, KOFRA,
GRLNR, KOFRS
Pricing formula and requirement
number
NUMC3
NUMC7
DZAEHK, DZAEHK_IND,
DZAEKO, BBP_ZAEHK
Condition counter in pricing result
NUMC2
NUMC3
GRLNR
Group condition routine
NUMC2
NUMC7
KALKS, KALVG
Customer and document
classification for pricing procedure
determination
CHAR1
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 989
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 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 and where do you have to add the append fields to the structure
PRCS_ELEMENTS_DATA?
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.
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.
Check for append fields:
Until target release S/4HANA 1610: 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.
As of target release S/4HANA 1709: The check for append fields is integrated
into the upgrade tools (SUM). The check is executed automatically as part
of phase ACT_UPG. If append fields to KONV are found SUM prompts a
confirmation whether adjustmants have been done and whether the
upgrade/conversion can be continued.
The check only finds appends fields if they belong to the namespaces Z*
or Y*.
Append fields of a namespace /*/, e.g. /ABC/, do not lead to a
confirmation prompt as the upgrade tools cannot safely distinguish the
different owner types of /*/ namespaces (customers or partners or SAP-
managed components).
The check is also not executed if there is already a SPDD transport
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 990
integrated into the conversion procedure.
(See above, "When and where do you have to add the append fields to the
structure PRCS_ELEMENTS_DATA?")
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
Carefully follow the instructions in SAP Notes 2188695,
2189301, 2313318, and 2220005
Conversion pre-checks
SAP Note: Pre-checks delivered with Note 2188735
Custom code-related
information
SAP Note: 2220005
38.11S4TWL - Foreign Trade
Application Components:SD-FT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267310
S4TWL - Foreign Trade
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 991
Solution
Description
There are currently two software services for international trade transactions: SAP ECC
SD Foreign Trade (SD-FT) and SAP Global Trade Services (SAP GTS).
Foreign Trade (SD-FT) is part of the standard SAP ECC Sales and Distribution (SD)
scope.
SAP GTS is an external service that can be installed on an additional instance.
In SAP S/4HANA, the Foreign Trade (SD-FT) functionality is not available anymore.
Instead, SAP S/4HANA for international trade within SAP S/4HANA is the successor.
With SAP S/4HANA 1709, letter of credit processing is provided by integration of SAP
S/4HANA Sales with Trade Finance.
For Intrastat, Legal Control and Classification with Commodity Codes customers can
leverage SAP S/4HANA for international trade functions within SAP S/4HANA.
(Please note, that in the sales area Legal Control checks are currently only enabled for
document types C - Sales Orders and G - Contract. For document type I - Free of Charge
order and E - Scheduling Agreement this is planned to be available in one of the next
releases.)
For Preference Management, you can use functions based on SAP GTS. SAP GTS can be
natively integrated with SAP S/4HANA.
For shipped releases compare the Feature Scope Description for SAP S/4HANA under
https://help.sap.com/s4hana -> Product Documentation -> Feature Scope Description
For future releases compare the Roadmap for SAP S/4HANA under
https://www.sap.com/products/roadmaps.html,
section "Lines of Business" --> "LoB: Finance".
Additional functions for Import and Export Management are available with SAP GTS.
Business Value
Intrastat
The selection reports for Intrastat are simplified.
Authorization check on company code level.
Multiple users can work at the same time.
Larger number of supported countries.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 992
Better user experience in processing Intrastat declarations, for example, mass
update of item data is possible.
Classification of services with Intrastat service codes for Italy is available
(with S/4HANA for international trade 1610.
Legal Control
Verification of relevant documents, like purchase orders, sales orders and
outbound deliveries to ensure a proper compliance processes.
Complete overview by using a Trade Compliance Document, which can
consider multiple legal regulations, like Legal Control, Embargo and
Watch List Screening regulations.
Monitoring of compliance relevant documents, across different laws and rules.
Possibility to maintain blocks and to create customer specific rules to
determine blacklisting, whitelisting and/or license types in a specific
order.
Classification
Optimized maintenance of the commodity code.
Classify for multiple countries on cross-plant level.
Time Dependent classification.
One numbering scheme for multiple countries.
Mass classification of multiple products in one step.
Semi-automated upload of classification master data from external
data providers.
Synchronization for the commodity codes between "SAP Global Trade
Services" (SAP GTS) and "SAP S/4HANA for international trade"
without any manual interaction.
Classification for Customs Tariff numbers also
available.
Preference Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 993
Preference Management can be used via SAP GTS. For the relevant license
topics please contact your Account Executive.
Treasury
A complete solution for letter of credit processing through integration of Sales
and Trade Finance of Treasury and Financial Risk Management in SAP
S/4HANA.
All User interfaces are build based on Fiori design principles.
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 FT/Customs: General overview
EN99 General Foreign Trade Processing
VI09X Change FT Data in Purchasing Doc.
VI08X Display FT data in purchasing doc.
VI80X Change FT Data in Goods Receipt
VI79X Display FT Data in Goods Receipt
VI77X Change FT Data in Outbound Delivery
VI64X Display FT Data in Outbound Delivery
VI14X Change FT Data in Billing Document
VI10X Display FT Data in Billing Document
VIIM FT: Op. Cockpit: Purchase order
VIWE FT: Op. Cockpit: Goods Receipt
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 994
VIEX FT: Journal Export Actual
VE85 Change Statistical Value – Import
VE86 Display Statistical Value – Import
VE88 Change Statistical Value – Export
VE89 Display Statistical Value – Export
VE87 Change Stat.Value – Subcontracting
VEI3 Display Stat.Value – Subcontracting
OVE1 Commodity Code / Import code no.
VXCZ INTRASTAT: Form - Czech Republic
VXHU INTRASTAT: Form - Hungary
VXPL INTRASTAT: Form – Poland
VXSK INTRASTAT: Form – Slovakia
VEBE INTRASTAT: XML File - Belgium VECZ INTRASTAT:
File - Czech Republic
VEHU INTRASTAT: File – Hungary
VEPL Create INTRASTAT CUSDEC EDI PL
VESK Create INTRASTAT CUSDEC EDI SK
VEIA Create INTRASTAT CUSDEC EDI SE
VEIB Create INTRASTAT CUSDEC EDI PT
VEID Create INTRASTAT CUSDEC EDI LU
VEI0 Create INTRASTAT CUSDEC EDI IE
VEI7 Create INTRASTAT CUSDEC EDI GB
VEI8 Create INTRASTAT CUSDEC EDI AT
VEI9 Create INTRASTAT CUSDEC EDI ES
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 995
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 996
VE04 EXTRASTAT: Data selection for export
VE05 EXTRASTAT: Create File – Germany
VE97 Create EXTRASTAT tape: Netherlands
VEXU Foreign Trade: Add EXTRASTAT Data
VE13 KOBRA data selection: export Germany
VE14 Create KOBRA file for Germany
VE15 Create disk - INTRA/EXTRA/KOBRA/VAR
VE21 VAR: Selection of bill. docs Switz.
VE22 Create VAR form for Switzerland
VE23 V.A.R.: File – Switzerland
VE18 SED data selection for USA exporter
VE25 SED: Selection: USA Carriers
VE19 Create SED form for USA
VE20 Create AERP file for USA
VE27 HMF: Selection – USA
VXJ1 MITI Declarations
VXJ2 Declaration of ImportBill.Docs Japan
VEIAI INTRASTAT Archiving
VEIAE EXTRASTAT Archiving
VE81 Check Report: General FT Data
VE73 Goods Catalog: Create Document
VE74 Goods Catalog: Create Diskette
VXA5 Document. Payments: Print Monitoring
VXA7 Documentary Payments: Simulation
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 997
ENSV Data Service
VX01N Create License
VX02N Change License
VX03N Display License
VX22N Change License Data
VX23N Display license data
VE31 Blocked SD Documents
VE30 Existing licenses
VE29 Assigned Documents for Each License
VE82 Check Report: Export Control Data
VI83 Check Customer Master/Legal Control
VX07 Simulation: License Check
VX09 Simulation: Embargo Check
VX08 Simulation: Boycott List Check
VX16 BAFA diskette: Selection
VX17 Create BAFA diskette
VX10 Countries of Destination for License
VX05 Customers for License
VX06 Export Control Classes for License
VE56 Check Export Control for Consistency
VI84 Doc.Payments: Check Customer Master
VX14N Maintain Financial Document
VX11N Create Financial Document
VX12N Change Financial Document
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 998
VX13N Display Financial Document
VI73N Foreign Trade: Maintain Long-Term Vendor Declaration
VI74N FT: Display Vendor Declaration
VI78 Foreign Trade: Countries
VI54 Customs Approval Numbers
VI55 Approval Number per Plant
VI68 Control Commodity Code/Code Number
VED1 Print Parameters for Export Documents
OVE1 Commodity Code / Import Code Number
VPAR Archiving Preference Logs
VFAI Archiving – INTRASTAT
VFAE Archiving – EXTRASTAT
FTUS Foreign Trade: Maintain User Data
ENCO Printing / Communication
ENGK Legal Control
ENLO Documentary payments
ENPA Foreign Trade: Periodic Declarations
ENPR Preference Processing
ENGR Periodic Declarations
ENSV Foreign Trade Data Maintenance
ENZD Customs Objects: Documentation/Info.
VOIM Check Import Purchase Order
VOWE Check Goods Receipt
VI09X Change Import Purchase Order
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 999
VI53X Change Goods Receipt
VOLI Check Export Delivery
VOEX Check Export Billing Document
VI77X Change Export Delivery
VI14X Change Export Billing Document
VI85 Check Report: Vendor Master
VE81X Check Report: General Foreign Trade Data
VE82X Check Report: Export Control Data
VE83X Check Report: Preference Data
VI86 Cross-plant Check of Foreign Trade Data
VI82X Foreign Trade: Customer Master Consistency – General
VI83X Foreign Trade: Customer Master Consistency – Control
VI84X Foreign Trade: Customer Master Consistency - Letter of
Credit
VIE4 Periodic Declarations: Log of Incomplete Items
VE24X Foreign Trade: Information Commodity Code
VI24X Foreign Trade: Information Import Code Number
FTIM Journal: Purchase Orders
FTGR Journal: Goods Receipts
FTIM Import Order Analysis
FTGR Import Gds Receipt Analysis
FTEX Export Bill. Documents Journal
FTEX Exp.bill.doc.analysis
VE30 Expiring Licenses
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1000
VE29 Sales Orders for a License
VXA2 Financial Documents: List
VXA1 Financial Documents: SD Documents
VI74N Display Vendor Declaration
CAAT Foreign Trade: Call up FT Atrium
VIUL Foreign Trade: Data Upload
VIBA Send IDoc Output-AES-Initial Procg
VIBC Send IDoc Output-AES-Error in Procg
VIBB Send IDoc Output-AES-Repeat Procg
VIB7 Send IDoc Output - Initial Procg
VIB9 Send IDoc Output - Error in Procg
VIB8 Send IDoc Output - Repeat Procg
VIB4 Print Transaction: Initial Procg
VIB6 Print Transaction: Error in Procg
VIB5 Print Transaction: Repeat Procg
VIB3 Foreign Trade Output Status
VEII SAPMSED8: Call IMPINV01
VEIE SAPMSED8: Call EXPINV02
VX00 Preference Handling
LEAN Request long-term VendDecl. (vendor)
LEMA Dun long-term vendor decl. (vendor)
VE67 Aggregate Vendor Declarations
LEER Create long-term VenDecl. (customer)
VE55 Preference Determination: Individual
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1001
VE54 Preference Determination: Collective
VEB5 Calculate Assemblies Individually
VEB6 Calculate Assemblies Collectively
VEPR Customs log
VE91 Display Preference Values
VE90 Change preference values
VE83 Check Report: Preference Data
VE66 Preference Procedure
VE65 Preference Reg./Percentage Rates
VE64 Commodity Code/Customs Areas
VE94 Load Commodity Code for EU Countries
VEM4 Merge: EU - Commodity Code
VI94 Load Import Code Nos - EU Countries VIM4 Merge: EU
- Import Code Number
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1002
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)
To guarantee sales order payments with Trade Finance, the following transactions are
available for processing letters of credit, standby letters of credit, and bank guarantees:
FTR_CREATE (Create Financial Transaction)
FTR_EDIT (Edit Financial Transaction)
FTR_RCD (Trade Finance: Risk Check Decision Management)
FTR_CHK_CONSTCY (Data Consistency check with S/4HANA Sales)
Required and Recommended Action(s)
Analysis of all foreign trade processes that are currently in use.
To migrate Legal Control data, check the documentation in KBA 2869019.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1003
To migrate financial documents in Foreign Trade to Trade Finance, you carry out the
migration steps available as Customizing activities (transaction SPRO, SAP
Reference IMG) under:
Conversion of Accounting to SAP S/4HANA-->Preparations and Migration of
Customizing-->Preparations for Migration of Financial Documents to
Trade Finance
Conversion of Accounting to SAP S/4HANA-->Data Migration-->Migration
of Financial Documents to Trade Finance and Complete Migration of
Financial Documents to Trade Finance
Conversion of Accounting to SAP S/4HANA-->Activities after Migration--
>Manual Activities for Trade Finance
Related SAP Notes
Conversion pre-checks
SAP Note: 2205202
Custom code-related information
SAP Note: 2223144
38.12S4TWL - Credit Management
Application Components:SD-BF-CM, FI-AR-CR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270544
S4TWL - Credit Management
Symptom
You are doing a system conversion to SAP S/4HANA and you are using Credit
Management (FI-AR-CR) on SAP ERP. In this scenario, the following SAP S/4HANA
Transition Worklist item applies.
Solution
In the following we distinguish between the three possible constellations in your system:
You are only using FI-AR-CR Credit Management in your source release
You are only using SAP Credit Management (FIN-FSCM-CR) in your source release
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1004
You are using both Credit Management solutions (FI-AR-CR & FIN-FSCM-CR) in
your source release
You are not using any of the Credit Management solutions (Then this note is not
relevant for you)
(with the prefixes A, B, C, D we mark the explanations as relevant for these scenarios in
the following chapters)
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).
Risk category -> Risk class maintained for the whole business partner (not per
customer & credit control area), as the probability of a credit default of your
customer does depend on the characteristics of your customer and not your
internal organizational structures.
Maintenance of customer master data in business partner transaction
The credit checks carried out for a customer depend on the assigned check rule in the
business partner transaction. They do not depend on the risk class (formerly risk
category).
Releasing blocked documents via Case Management (documents the blocking reason)
How to Determine Relevancy:
A: Indicators for the usage of FI-AR-CR Credit Management are:
You are using transaction FD31 or FD32 to maintain credit account master data (this
data is stored in table KNKK & KNKA)
You are using transactions VKM1-4 to process sales documents (e.g. releasing
blocked sales orders)
Function module UKM_IS_ACTIVE returns space for flag E_ACTIVE and
E_ERP2005
In general: You are using parts of the obsolete transactions and reports listed in
chapter “Business Process related Information”.
Exposure data is stored and updated continuously in database tables S066 and S067.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1005
B: Indicators for the usage of SAP Credit Management (FIN-FSCM-CR) are:
You are using transaction BP or UKM_BP to maintain credit account master data
(this data is stored in table UKMBP_CMS_SGM & UKMBP_CMS)
You are using transaction UKM_CASE to process sales documents (e.g. releasing
blocked sales orders)
Function module UKM_IS_ACTIVE returns ‘X’ for parameter E_ACTIVE and
E_ERP2005
C: Indicators of A and B apply for you.
D: None of the indicators of A and B apply for you.
Business Value:
Higher degree of automation, thanks to automatic calculation of credit scores, risk
classes and credit limits
Credit events help the credit analyst to focus on exceptions during his daily business
Create a relationship from credit analysts to customers
Process of credit limit requests
Documented credit decisions
Higher / lower account relationship of business partners (adds up exposure of lower
accounts on higher accounts)
Less redundant data (reading FI-data via HANA view)
Business Process related information:
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR. The migration from one-
system landscapes is supported by tools that SAP provides in the IMG. (see details in
chapter “Required and Recommended Action(s)”)
Influence on Business Processes:
A & B & C: There will be no change to your business processes because of the system
conversion.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1006
A & C: However, some transactions become obsolete and are replaced by new
transactions.
Here are some examples for such cases:
Examples for replaced
transactions in SAP
S/4HANA
For the maintenance of the credit account master data, transaction
FD32 is replaced by transaction UKM_BP.
For releasing credit-blocked sales orders, transaction VKM1 is
replaced by transaction UKM_MY_DCDS.
Transactions not available in
SAP S/4HANA
F.28 - Customers: Reset Credit Limit
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
VKM1 - Blocked SD Documents
VKM2 - Released SD Documents
VKM3 - Sales Documents
VKM4 - SD 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1007
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):
B: Migrating Credit Management is not needed. Review of BadIs
“UKM_R3_ACTIVATE” and “UKM_FILL” is advisable. Think of using the default
implementation provided by SAP. (FI-data will then be read real-time with the default
implementation of BadI “UKM_R3_ACTIVATE”. The implementation of BadI
“UKM_FILL” is then not needed anymore.)
D: Nothing to do, migration of Credit Management is not needed.
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR completely. 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.
Reviewing the migrated Customizing is advisable afterwards: For example, risk classes
are now maintained once for a customer (for all segments) instead of maintaining them
per customer’s credit control area.
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:
2227014 (Financials)
2227014 (SD)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1008
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.
C (additionally): Review of BadIs “UKM_R3_ACTIVATE” and “UKM_FILL” is
advisable. Think of using the default implementation provided by SAP.
Related SAP Notes
Custom code-related information (SD)
SAP Note: 2217124
Custom code-related information (Financials)
SAP Note: 2227014
38.13S4TWL - ERP SD Revenue Recognition
Application Components:SD-BIL-RR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267342
S4TWL - ERP SD Revenue Recognition
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
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 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1009
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
OVACT "Revenue Recognition: Activations"
OVEP "Maintain Item Categories: Revenue Recognition"
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 refer to note 2591055 that contains information about known restrictions of SAP
Sales Integration with SAP Revenue Accounting and Reporting (SAP SALES INTEGR
SAP RAR 1.0) which is also known as the SD Integration Component.
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.
You can find more details about the migration to SAP Revenue Accounting and
Reporting in the following notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1010
2582784
Revenue Accounting and Reporting with SAP RAR 1.3 and S/4HANA 1809 &
1909 OP - FAQ's and Guidance
2733866
Migration Guide for SD Revenue Recognition to Revenue Accounting and
Reporting
Related SAP Notes
Conversion pre-checks
SAP Note: 2227824
Custom code-related information
SAP Note: 2225170
38.14S4TWL - Optimization of SD Rebate Processing for TPM Customers
Application Components:SD-BIL-RB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267344
S4TWL - Optimization of SD Rebate
Processing for TPM Customers
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
Business Value
Redundant index data, to determine relevant documents, was removed. This leads to
a significantly reduced database footprint.
Additional information can be found in note 2200691 and the documentation/notes for
business function LOG_SD_REBATE_INDEX.
Description
Customers with an active CRM TPM or Trade Management license can continue using
SD Rebate Processing, even though a successor is already being provided by Settlement
Management (cp. simplification item SD Rebate Processing replaced by Settlement
Management).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1011
Business Process-Related information
For more information, see note 2226380.
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.
Licensed customers can optionally enable the creation of rebate agreements directly in
sales via removal of the blacklist entries for VB01 (Note 2249880). However, for the
TPM process this is not necessary at all, since for this business process, rebate
agreements are created by CRM TPM.
Regardless of any TPM licences the usage right of SD Rebates in SAP S/4HANA will
end with the end of standard or extended maintenance of SAP ERP/ECC.
The SD Rebate solution is only provided in the current scope. Upcoming legal
requirements and additional funcitionalities will only be covered in the Settlement
Management solution.
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 only relevant if the customer has an active Trade
Promotion Management or Trade Management license.
The S/4HANA Readiness Check determines this Transition Worklist Item as relevant if
SD Rebates have been used in the customer system (table KONA has entries with field
ABTYP Equal to 'A').
But in fact only those customers are affected which have an active Trade Promotion or
Trade Management license.
The general changes for SD Rebates are described in note
2267377 - S4TWL - SD Rebate Processing Replaced by Settlement Management
Related SAP Notes
Custom code-related information
SAP Note: 2200691
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1012
38.15S4TWL - Simplification in SD Analytics
Application Components:SD-IS, SD-HBA-SOF, SD-HBA-VDM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267348
S4TWL - Simplification in SD Analytics
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
SD Analytics based on Logistics Information System (LIS) is part of the SAP S/4HANA
compatibility scope, which comes with limited usage rights. For more details on the
compatibility scope and it’s expiry date and links to further information please refer to
SAP note 2269324. In the compatibility matrix attached to SAP note 2269324, SD
Analytics based on LIS can be found under the ID 481.
This means that you need to migrate from "SD Analytics based on Logistics Information
System (LIS)" to its designated alternative functionality SAP S/4HANA Sales Analytics
before expiry of the compatibility pack license.
Business Process-Related Information
Simplification in SD Analytics follows the overall analytics strategy in SAP
S/4HANA: 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 tables. 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1013
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)
Further Usage of BW and LIS/SIS
Data extraction from SAP S/4HANA to a customer-owned BW-Hub is still supported.
See note https://launchpad.support.sap.com/#/notes/2500202 for further information
about the relation of S/4HANA to BW.
If you use a material number longer than 18 characters - see restriction note “Extended
Material Number in LIS: SAP Note 2232362”.
Deprecated or obsolete Transactions
Transaction not
available in SAP
S/4HANA
VA06 - Sales Order Monitor
Instead of transaction VA06 SAP
recommends the Fiori App 'Sales
Order Fulfillment Issues'
Transactions in
compatibility scope
MCTA - SIS: Customer Analysis –
Selection
MCTC - SIS: Material Analysis –
Selection
MCTE - SIS: Sales Org. Analysis
– Selection
MCTG - SIS: Sales Office
Analysis Selection
MCTI - SIS: Sales Empl. Analysis
Selection
MCTK - SIS: Shipping Pt. Analysis
Selection
For alternatives refer to our
documentation for Sales Monitoring
and Analytics on help.sap.com.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1014
As SD Analytics based on LIS can be used until the expiry date of the compatibility pack
license, it’s up to each customer to decide, when (with which of the coming SAP
S/4HANA releases) they want to migrate to the designated alternative functionality.
However, we strongly recommend doing a business evaluation and decision, at which
point in time this will be done, early in advance to plan accordingly for the migration
efforts.
Customers using SD Analytics based on LIS and customers extracting data from SAP
ERP to their own BW-Hub can continue with these processes in SAP S/4HANA
considering the additional information in the referenced notes.
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using any of the transactions
listed above.
Related SAP Notes
Custom code-related information
SAP Note: 2227750
See also Compatibility Scope: What Happens after 2025/2030 | SAP Blogs (bullet point
13 - What happens to Logistic Information System (LIS)?)
Transaction MCSI (for custom-defined info structures) will not be deprecated (perpetual
scope).
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, ID 481
38.16S4TWL - Advanced Order Processing and Billing for Contractors to the
public sect
Application Components:SD-SLS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267350
S4TWL - Advanced Order Processing
and Billing for Contractors to the Public
Sector
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1015
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
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
/CBAD/98000086
Related SAP Notes
Custom code-related information
SAP Note: 2223800
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1016
38.17S4TWL - Operational Data Provisioning
Application Components:SD-SLS-GF-RE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267351
S4TWL - Operational Data Provisioning
Symptom
You are doing a system conversion to SAP S/4HANA. In this scenario, the following
SAP S/4HANA Transition Worklist item applies.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1017
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.
In SAP ERP the functionality was assigned to the Business Function
LOG_SD_ANALYTICS_01.
Related SAP Notes
Custom code-related information
SAP Note: 2228056
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1018
39.Service Operations & Processes
39.1 Industry functionality from SAP CRM which is not supported in
S/4HANA
Application Components:CRM-IA, CRM-IU-DSM, CRM-BTX-CTR-UCO, CRM-ITT, CRM-FM,
CRM-CLA, CRM-MKT-MPL-TPM, CRM-ISR, CRM-IPH, CRM-IM, CRM-CHM, CRM-LAM, CRM-
IHT, CRM-ISH, FS-BP, CRM-IFS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3052214
Industry functionality from SAP CRM
which is not supported in S/4HANA
Symptom
You are considering or planning a migration of an SAP CRM 7.0 or SAP CRM 7.0 EhP
installation to S/4HANA OP 1909 or a higher release. In this case, the following
information about changed or deprecated functionality is relevant.
Solution
Industry functionality from SAP CRM from various industries is not available in
S/4HANA. This comprises the following industry solutions (the corresponding
application component is mentioned in parentheses):
Automotive (CRM-IA)
Financial Services (CRM-IFS), including the SOA services for the Business Partner (FS-
BP)
Healthcare (CRM-ISH)
High Tech (CRM-IHT)
Leasing (CRM-LAM, CRM-BTX-BF-FIN)
Partner Channel Management (CRM-CHM)
Media (CRM-IM)
Pharmaceuticals (CRM-IPH)
Retail (CRM-ISR)
Service Parts Management (no specific application component)
Trade Promotion Management (CRM-MKT-MPL-TPM), including:
Claims Management (CRM-CLA)
Funds Management (CRM-FM)
Travel & Transportation (CRM-ITT)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1019
Usage Based Billing (CRM-BTX-CTR-UCO)
Utilities: Demand Side Management (CRM-IU-DSM)
As a consequence, the following business objects which were based on the CRM business
transactions ("One Order") framework are not supported in S/4HANA:
Financial Services
BUS2000307
FS Object Container
BUS2000308
FS Main Contract
Leasing
BUS2000114
Financing Contract
Media
BUS2000230
License Sales Contract
BUS2000231
License Acquisition Contract
BUS2000232
License Usage Confirmation
TPM: Claims Management
BUS2000310
Claim Submission
BUS2000311
Claim
BUS2000312
Prepayment Request
BUS2000313
Budget Reservation
BUS2000320
Claim Chargeback
BUS2000330
Claim Chargeback Recovery
TPM: Funds Management
BUS2000400
Fund Plan
BUS2000401
Fund
BUS2000402
Budget Posting
Travel & Transportation
BUS2000246
Toll Collect Contract Header
Usage Based Billing
BUS2000250
Pool Contract
Utilities: Demand Side Management
BUS2000410
DSM Application
BUS2000411
DSM Agreement
Other Terms
S4CRMTWL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1020
40.Transportation Management
40.1 S4TWL - Simplified customizing of Transportation Manangement (TM)
integration
Application Components:TM-FRS-IV, TM-FRS-IP, TM-FRS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2465978
S4TWL : Impact on TM process with
conversion of SAP ERP or upgrade of
S/4HANA 1511/1610 to S/4HANA 1709
Symptom
You use SAP ERP Enhancement Package 4, 5, 6, 7 or 8 or S/4HANA 1511 or S/4HANA
1610 for freight settlement process integration with Materials
Management(MM) with SAP TM in a side-by-side mode.
As a part of integration, there are mappings maintained for freight settlement document
(FSD) type to purchase order (PO) Type, material group, plant in the view
TCM_V_PUR_MAP.
There are entries for the same FSD type mapped to different PO type / material group /
plant OR there are entries where FSD type is blank.
The system conversion is planned to S/4HANA 1709 or system upgrade is planned from
S/4HANA 1511 or S/4HANA 1610 to S/4HANA 1709.
Reason and Prerequisites
Conversion to S/4HANA
Solution
Business Value :
Since Transportation Management (TM) is available internally as part of S/4HANA
1709, customers can now have the TM integration in a single system also. Also this has
impact to the side-by-side integration with S/4HANA 1709 onwards.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1021
The mapping requirement for the posting of the freight settlement document in S/4HANA
1709 is now changed. From S/4HANA 1709 release onwards, the usage of the view
TCM_V_PUR_MAP and the underlying customizing table TCM_C_PUR_MAP have
been discontinued.
Description :
In a side by side scenario, with S/4HANA 1709, there are the following changes required.
1. The mapping of purchase organization unit from TM org data to the MM Purchase
organization is no longer required in S/4HANA. SAP TM sends this mapping
information with the message type:
TransportationOrderSUITEInvoicingPreparationRequest used in the A2A service
interface: TransportationOrderSUITEInvoicingPreparationRequest_In on S/4HANA.
2. The other information for posting of the freight settlement document such as PO type,
plant and material group are now maintained in the maintanence view based on the
/SCMTMS/C_SFIR_T table using the customizing activity Assign Purchasing
Information for Posting under Transportation Management > Settlement > Freight
Settlement > Integration for Settlement Posting. You now maintain the PO type, plant
and material group at the freight settlement document type level.
System conversion or upgrade shall take care of copying the entries from the source table
to the target table which is /SCMTMS/C_SFIR_T table. For the copy to happen
successfully, there should not be conflicting entries for the same FSD type or entries with
blank FSD types in the source table i.e. in table TCM_C_PUR_MAP.
Business process related information :
Freight settlement document from stand alone SAP TM is transferred to S/4HANA 1709
for posting using A2A service interface :
TransportationOrderSUITEInvoicingPreparationRequest_In.
Required and Recommended action(s) :
In order to ensure that the data available in TCM_C_PUR_MAP table is consistent
enough to be copied into the target table /SCMTMS/C_SFIR_T via an XPRA which will
be executed during the upgrade / system conversion process, it is required that the source
table doesn't contain :
1. Entries where FSD type is blank
2. Entries for the same FSD type to different PO type / plant / material group.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1022
If you have any of the above combinations of data in the source table, Review these
entries to adjust the right settings either by
1. Deleting the duplicate FSD type records
2. Deleting the records with blank FSD type or specifying the FSD type in such
entries. To add the FSD type where FSD type is blank, you will need to copy such
records in the source table and enter the FSD type before saving and then followed by
deletion of records which are with blank FSD types.
NOTE: Before conversion please also check if there are FSDs in the source SAP TM
system where these combination in conflict are required for posting of the settlement
document. In case, kindly ensure that the above mentioned corrections are made keeping
these yet to be processed FSDs for posting.
How to determine relevancy :
In order to ensure that the data available in TCM_C_PUR_MAP table is consistent
enough to be copied into the target table /SCMTMS/C_SFIR_T via an XPRA which will
be executed during the upgrade / system conversion process, it is required that the source
table doesn't contain :
1. Entries where FSD type is blank
2. Entries for the same FSD type but mapped to different PO type / plant / material group.
Other Terms
System conversion, S/4HANA, SAP TM, Freight settlement document transfer, FSD
transfer, Freight settlement document posting, FSD posting, TM process, TM -
ERP integration, TM Internal in S/4HANA
40.2 S4TWL - Forwarding Settlement Document Transfer in TM
Application Components:TM-FWS, TM-FWS-BIL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2639847
S4TWL : Impact on TM process with
conversion of SAP ERP or upgrade of
S/4HANA 1511/1610/1709 to S/4HANA
1809
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1023
Symptom
You use SAP ERP Enhancement Package 4, 5, 6, 7 or 8 or S/4HANA 1511 or S/4HANA
1610 or S/4HANA 1709 for posting of forwarding settlement and internal settlement
document in Sales and Distribution(SD).
As a part of integration of SAP TM, there are changes to the IMG activities that are used
for the forwarding settlement and internal settlement integration. These changes need to
be evaluated for impact prior to the system conversion to S/4 HANA 1809 or above.
Reason and Prerequisites
Conversion to S/4HANA
Solution
Business Value :
Since Transportation Management (TM) is available internally as part of S/4HANA
1809, customers can now have the TM integration in a single system and in a side-by-
side integration. To minimize the data and system set up for Supply Chain
Transportation Management with in S/4 HANA, TM forwarding settlement module is
redesigned with a few simplification of the IMG activities.
Description :
In a side by side scenario, with S/4HANA 1809, there are the following changes required.
1. The mapping of sales organization unit in the organization Model to the SD Sales
organization is no longer required in TM module in S/4 HANA and in SAP TM. TM
utilizes the SD sales organization available in the field BSG Org. Unit (LOGQS_ID) and
sends this information with the message type:
CustomerFreightInvoiceRequestSUITERequest used in the A2A service
interface: CustomerFreightInvoiceRequestSUITERequest_In_V1 on S/4HANA.
2. The information for posting of the forwarding settlement document or internal
settlement document (inter-company) such as Sales document type, billing type, billing
item type and pricing procedure are now maintained in the table /SCMTMS/C_CFIR_T
for each forwarding settlement document type and internal settlement (inter-
company) document type. The usage of the table TCM_C_SLS_MAP is discontinued .
3.For intra company settlement posting scenario, the usage of tables TCM_C_TCD_MAP
and TCM_C_TCD_PURMAP are discontinued. During system conversion or upgrade,
the system shall take care of copying the entries from the source table
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1024
TCM_C_TCD_MAP to the target table TCM_C_SLSASSGN and from
TCM_C_TCD_PURMAP table to the target table TCM_C_PURASSGN tables.
Business process related information :
Forwarding settlement document or internal settlement document from stand alone SAP
TM is transferred to S/4HANA 1809 for posting using A2A service interface :
CustomerFreightInvoiceRequestSUITERequest_In_V1.
Required and Recommended action(s) :
For the upgrade to be successful, it is recommended that the RFC destination for the TM
system is maintained as a combination of logical system and client separated by an
underscore '_'( LOGSYS_CLIENT)
In order to ensure that the data available in TCM_C_SLS_MAP table is consistent
enough to be copied into the target table /SCMTMS/C_CFIR_T via an XPRA which will
be executed during the upgrade / system conversion process, it is required that the source
table does not contain :
1. Entries where FWSD type is blank
2. Entries for the same FWSD type to different sales document type / billing type / billing
item type and pricing procedure.
3. Entries where there are different division and distribution channel maintained.
4. Entries where the logical system is blank.
5. Entries where the ECC sales organization, FWSD category is blank.
If you have any of the above combinations of data in the source table, Review these
entries to adjust the right settings either by
1. Deleting the duplicate FWSD type records
2.Deleting the records with blank FWSD type or specifying the FWSD type in such
entries. To add the FWSD type where FWSD type is blank, you will need to copy such
records in the source table (TCM_C_SLS_MAP) and enter the FWSD type before saving
and then followed by deletion of records which are with blank FWSD types.
3. Maintain the same division and distribution channel for all the entries in the source
table.
4. Maintain an appropriate logical system for all the entries.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1025
5. Maintain the ECC sales organization and the FWSD category for all the entries.
6.In the table TCM_C_SLS_MAP, maintain the mapping of TM sales org with the ECC
sales org which is the 'BSG Org ID' maintained in the TM org model
In order for the entries to be copied from the tables for TCM_C_TCD_MAP to the
TCM_C_SLSASSGN tables it is required that the data in the source tables does not
contain:
1. Entries where the logical system is blank
2. Entries where the TM sales organization is blank
3.Entries where the controlling area , internal order and cost center are blank
If you have any of the above combinations of data in the source table, Review these
entries to adjust the right settings either by
1. Maintain the appropriate logical system
2. Maintain the TM sales organization
3. Maintain the controlling area, internal order and cost center for all entries
In order for the entries to be copied from the tables for TCM_C_TCDPURMAP to the
TCM_C_PURASSGN tables it is required that the data in the source tables does not
contain:
1. Entries where the logical system is blank
2. Entries where the TM purchase organization is blank
3.Entries where the controlling area , internal order and cost center are blank
If you have any of the above combinations of data in the source table, Review these
entries to adjust the right settings either by
1. Maintain the appropriate logical system
2. Maintain the TM purchase organization
3. Maintain the controlling area, internal order and cost center for all entries
NOTE:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1026
Before conversion please also check if there are FWSDs or internal settlement document
in the source SAP TM system which are not yet posted to SAP ERP or the S/4 HANA
system where these combination in conflict are required for posting of the settlement
document. If these settlement documents are posted post conversion, the new tables
would be used for posting data.
How to determine relevancy :
In order to ensure that the data available in TCM_C_SLS_MAP table is consistent
enough to be copied into the target table /SCMTMS/C_CFIR_T via an XPRA which will
be executed during the upgrade / system conversion process, it is required that the source
table doesn't contain :
1. Entries where FWSD type is blank
2. Entries for the same FWSD type but mapped to different sales document type/ billing
type / billing item type and pricing procedure.
Other Terms
System conversion, S/4HANA, SAP TM, Forwarding settlement document transfer,
FWSD transfer, Forwarding settlement document posting, FWSD posting, TM process,
TM - ERP integration, TM Internal in S/4HANA
40.3 S4TWL - Location Geo-Coding Adjustments
Application Components:TM-MD-TN-LOC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3290708
Impact on TM Location Geo-Coordinate
Determination with conversion of SAP
ERP or upgrade of S/4HANA any
version to S/4HANA OP2023 FPS0
Symptom
The system conversion is planned to S/4HANA 2023 FPS0 or system upgrade is planned
from S/4HANA any version to S/4HANA 2023 FPS0.
You use S/4HANA any version to create/update Location.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1027
There is a change in the behaviour for determining the geo-coordinates. As a result, the
default geo-coordinate for a location might not be valid after installing the changes for
the above-mentioned release.
Reason and Prerequisites
Conversion or upgradation to S/4HANA 2023 FPS0.
Solution
Description:
Currently, the system picks the strategy from the first entry of the customizing
maintained for Geocoding Levels. Please find below the SPRO path for maintaining the
Geocoding Levels. With the new behaviour, the system will check if there is a country
specific GIS Zone for each Geocoding Level. For a particular GC Level, if the system
can find a country specific GIS Zone, then the system determines the corresponding
Strategy from the customizing, if not the system will pick the strategy where the GIS
Zone is empty. Because of the above change, the locations in customer system need to be
checked. If the system finds a location where the current default Geocoding Level &
Strategy differ from the default Geocoding Level and Strategy post upgrade, the customer
has to fix the location Geo-Coordinates. Alternatively, customer can keep the location
Geo-Coordinates as it is.
The customizing for Geocoding Levels is maintained through SPRO->SAP Customizing
Implementation Guide-> Transportation Management->Master Data->Transportation
Network->Location->Geocoding->Define Geocoding Levels. Alternatively, you can use
view /SAPAPO/VLOC_GL to maintain geo coding levels. Please refer table
/SAPAPO/LOC_GL for the existing customizing.
The customizing for GIS Zone for a country is maintained through SPRO->SAP
Customizing Implementation Guide-> Transportation Management->Master Data-
>Transportation Network->Transportation Lane->Distance and Duration Determination-
> Assign Country/Region to GIS Zone. Alternatively, you can use view
/SCMB/V_GIS_ZN_A to maintain GIS Zone for a country. Please refer table
/SCMB/GIS_ZN_A for the existing customizing.
A simplification item is provided to check this behaviour during the upgrade. The
Simplification item will be configured in Software Update Manager (SUM). You run this
SUM framework for the simplification item during the upgrade. First decide if it is
relevant to check the affected locations and if yes:
1. A message will be shown with the number of locations that are going to get affected
after the upgrade for every system client in case if you choose detailed check.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1028
2. A generic message will be shown if there are any locations that are going to get
affected after the upgrade for every system client in case if you choose non-detailed
check.
How to determine check relevancy:
Check customizing in the following path:
SPRO->SAP Customizing Implementation Guide->Transportation Management->Master
Data->Transportation Network->Location-> Geocoding->Define Geocoding Levels.
If it has any of the below configuration, it will be relevant for checking the locations with
affected geo-coordinates.
1. If it has single entry and GIS Zone is not initial.
2. If it has multiple entries.
Required and Recommended action(s):
You might be getting any of the below messages after the successful run of the
simplification item check in SUM.
1. No action required by you. Continue with the upgrade: In this case, there is no
action required by you as mentioned in the message. So, you can go ahead with the
upgrade. This can be shown when checking of locations with affected geo-coordinates is
not relevant or there is no location that will be affected after upgrade.
2. Client XXX: Geographical data for locations will be affected. See note
3290708: This is shown when you run the Simplification Item check through SUM
framework in non-detailed mode. If you get this message, you have to run the
Report /SAPAPO/UPDATE_GEOCODE_LOC in the particular client mentioned in the
message after the upgrade. This report will fix the geo-coordinates of all the affected
locations.
3. Client XXX: Geographical data for XXX locations will be affected. See note
3290708: This is shown when you run the Simplification Item check through SUM
framework in detailed mode. It gives you an idea on how many locations will be affected
after the upgrade. If you get this message, you have to run the Report
/SAPAPO/UPDATE_GEOCODE_LOC in the particular client mentioned in the message
after the upgrade. This report will fix the geo-coordinates of all the affected locations.
How to run Report /SAPAPO/UPDATE_GEOCODE_LOC:
There are two ways to run the report:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1029
1. In Simulation Mode: In this case, you must check the Simulation Mode checkbox and
run the report in background mode. You also need to provide the packet size which
denotes how many locations will be processed at a time. The expected packet size is not
more than 10000. As the name suggests, the system will run in simulation mode and will
not fix the affected locations upon successful execution, a log will be created which you
can check in transaction SLG1 application log by providing the selection parameters
along with the object and sub-object mentioned in the output of the report. The SLG1 log
will show the list of locations that have been affected after the upgrade and need to be
fixed.
2. In Non-Simulation Mode: In this case, you don't need to check the Simulation Mode
checkbox. You can enter the packet size (not more than 10000) and run the report in
background mode. It is preferred to schedule a batch job for the report with the variant
mentioned above. This will fix all the locations with affected geo-coordinates upon
successful execution. A log will be created, and you can check the same in
SLG1 application log by providing the selection parameters along with the object and
sub-object mentioned in the output of the report. The SLG1 log will show the number of
locations that have been successfully updated. It will also show a list of locations that are
failed to get updated.
Other Terms
System conversion, Location Creation, Location Update, Location, Geo Coordinate,
Strategy Determination, GC Level, S/4HANA, SAP TM, TM process, TM Internal in
S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1030
41.Globalization Financials
41.1 S4TWL - Globalization – Financials
Application Components:FI-LOC, XX-CSC-XX
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270311
S4TWL - Globalization – Financials
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With the installation of the SAP S/4HANA on-premise edition 1511, certain country-
specific transaction codes and programs in the application area of Financials have been
replaced with newer transactions or 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.
41.2 S4TWL - Annexing Solution for Israel
Application Components:XX-CSC-IL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2437547
S4TWL - Annexing Solution for Israel
Symptom
The SAP LOCILERP Add-on (software component LOCILERP) has been integrated to
S4H On Premise Edition as of version S4H OP 1610.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1031
Here new Business Functions and switches have been provided to make Area Menus,
IMG nodes etc. switchable.
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release or is S/4HANA Finance release, where you have the Israeli annexing solution
implemented in system via transports solution or via LOCILERP add-on.
It is not relevant if your start release is S/4HANA.
Solution
Description
Israeli Annexing Solution is an On Premise solution provided as LOCILERP Add-On for
the Israeli market based on Inflation Adjustment Law that was published in Israel during
the 80’s.
Business Process related information
Annexing calculation is done via a central FM that is based on Annexing Packages which
includes all the relevant conditions/rules for the calculation, and based it on Indexes,
currency exchange rate and on SD Price List
The annexing calculation is in used in several modules in ERP environment as follow:
Logistic Invoice Verification
Sales and Distribution Billing Process
Loans Cash Flow
Treasury Cash Flow
Flexible Real Estate Contract Adjustment
The annexing solution in all its modules is based on the Master Data of Annexing
Packages and on a local customizing as well.
Required and Recommended Action(s)
The SAP LOCILERP add-on is shipped with the core product starting with SAP
S/4HANA, on premise edition 1610 (S4CORE 101). For more information, see the
attached business functions description: “TRM Localization for Annexing in Israel”, “FI,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1032
LO Localization for Annexing in Israel”. And country-specific release notes: 2349004,
2298073 and 2323282.
In addition, pay attention that LOCILERP modifications should be discarded from system
in the upgrade process from Add-on solution to SAP S/4HANA by performing the reset
to original in the Modification Adjustment transaction (e.g., SPAU).
41.3 S4TWL - Funds Management Portugal
Application Components:XX-CSC-PT-PSM-FM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2469984
S4TWL: Availability of Portuguese
Public Sector Funds Management in
SAP S/4HANA On-Premise 1709
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA and are using the
functionality described in this SAP Note. The following SAP S/4HANA Simplification
Item is applicable in this case.
Solution
Description
This SAP Note is relevant for you when your starting release for the system conversion is
a SAP ERP release or a SAP S/4HANA Finance release, where you have the Localization
for Portuguese Public Sector solution implemented in your system via transport solution
or via LOCPTFM add-on.
It is not relevant for theSAP S/4HANA 1709 FPS00 release.
Business Process related information
The SAP LOCPTFM Add-on (software component LOCPTFM) has been integrated into
SAP S/4HANA, as of release SAP S/4HANA 1709.
However, the Portuguese Public Sector Funds Management features are available as of
SAP S/4HANA 1709 FPS01 with the following restrictions:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1033
As a Customer who used the integration between Logistics documents and Funds
Management with LOCPTFM and is planning to move to SAP S/4HANA, please
note that in SAP S/4HANA, the Funds Management integration with Materials
Management has been enhanced to accomodate local version Portugal
requirements. However, a document chain initiated with the LOCPTFM Add-on
cannot be migrated to SAP S/4HANA and must first be closed in the Add-on
system. This restriction does not apply to customers with new installations, or
new document chains initiated in SAP S/4HANA.
As a Customer who used the integration between Logistics documents and Funds
Management with LOCPTFM and is planning to move to SAP S/4HANA, please
note that in SAP S/4HANA there is a new technical solution to support this
integration but no migration tool is currently available. For new processes
(starting with the pre-commitment document) the new functionality can be used
but not for an unfinished document chain.
Solution: as of SAP S/4HANA 1709 SPS03, SAP S/4HANA 1809 FPS01 or
the after the installation of SAP Note 2674217, this restriction no longer
applies. Please refer to that SAP Note for more information.
The Funds Management (FM) integration with Human Resources (HR) feature of the
SAP LOCPTFM Add-on (software component LOCPTFM) is no longer
considered in SAP S/4HANA. For alternative solutions, see Position Budgeting
and Control (PBC).
Solution: as of SAP S/4HANA 2022 FPS01 or after the installation of SAP
Note 3236088, this restriction no longer applies. Please refer to that SAP
Note for more information.
Required and Recommended Action(s)
For detailed information on the system installation/conversion of the Portuguese Public
Sector Funds Management, available in SAP S/4HANA 1709 FPS01, please see SAP
Note 2595915, Customer Installation/Conversion Procedures for Portuguese LOCPTFM
in S/4HANA On-Premise.
Please note that with the integration of SAP LOCPTFM into SAP S/4HANA 1709, some
ABAP objects of the respective LOCPTFM packages have become obsolete. Therefore,
run the ABAP Test Cockpit (ATC) using the latest simplification item DB content and
remove all detected usages of the LOCPTFM objects from your custom code.
Other Terms
Globalization, Localization, Add-on, PT, Portugal, PTFM, Funds Management, Public
Sector, LOCPTFM, PSM-FM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1034
41.4 S4TWL - Golden Tax Interface for China
Application Components:FI-LOC-FI-CN, XX-CSC-CN-GTI
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
2727947
GTI Data Migration in S/4HANA On
Premise Editions
Business Impact
2771861
S4TWL - Migration of GTI invoices to
SAP S/4HANA 1610 Feature Pack 1 or
higher
Symptom
This note is only relevant for customers who use China GTI (Golden Tax Interface)
solution and convert their system to SAP S/4HANA On-Premise Edition 1610 Feature
Pack 1, SAP S/4HANA On-Premise Edition 1709 or SAP S/4HANA On-Premise Edition
1809.
Starting from release SAP S/4HANA On-Premise Edition 1610 Feature Pack 1 the GTI
solution is using a new data base design and old generated GTI invoices will not be
avalible in the GTI applications.
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release or is an S/4HANA Finance release, where you use the localization of China GTI
solution in the system.
Solution
In the new data base design for the GTI solution invoices will be stored in 6 new tables
and the old invoices can be migarated into these new tables as decribed in note 2727947.
Other Terms
Globalization, Localization, CN, GTI
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1035
41.5 S4TWL - Replacement of legal reports with SAP S/4HANA ACR
Application Components:FI-LOC-SRF-RUN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2835816
Replacement of existing legal reports in
SAP S/4HANA for Advanced
Compliance Reporting (ACR) based
reports
Symptom
In SAP S/4HANA, some of the existing legal notes have been replaced by SAP
S/4HANA for advanced compliance reporting (ACR) based reports. However, the
replacement of reports does not apply to all the countries/regions and reports. Some of
the existing country/region - specific reports are still relevant.
To understand if the activity “Implement the generic ACR Fiori app succeeding the
deprecated legal reports” described in Simplification item SI5: GSFIN_LEG_REP
(S4TWL - Replacement of legal reports with SAP S/4HANA ACR) needs to be
performed after the system upgrade, please check if you are using any combination of
report and country/region listed in note 2480067.
Solution
Advanced Compliance Reporting is a unique and competitive legal reporting solution that
allows you to manage your regulatory requirements across the globe. The solution offers
features that ensure your complex and diverse legal reporting needs are addressed in
uniform, easy to use, and efficient manner. As an all-encompassing global reporting
solution, advanced compliance reporting provides a holistic and real time view of your
compliance status across countries and empowers you to draw meaningful inferences.
One of biggest strengths of advanced compliance reporting is that it offers an
extensibility platform to SAP partners and customers to create new legal reports or
enhance the existing reports. For more details about advanced compliance reporting and
country-specific report features, see the documentation note 2465179 (for OP 1610) and
the SAP help portal. In case of any generic questions/feedback, raise an incident in
component FI-LOC-SRF-RUN.
Other Terms
S/4HANA, ACR, Advanced compliance reporting, Legal Reports, SAP S/4HANA for
advanced compliance reporting, Run Advanced Compliance Reports, Define Advanced
Compliance Reports, Replacement
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1036
41.6 S4TWL - Add-on for Polish SAF-T regulatory requirements
Application Components:XX-PROJ-CDP-571
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3096074
S4TWL - Add-on for Polish SAF-T
regulatory requirements
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note.
The following SAP S/4HANA Simplification Item is applicable in this case: SI6:
GSFIN_PLVAT (S4TWL - Add-on for Polish SAF-T regulatory requirements)
Solution
Description
“SAP ERP, add-on for Polish SAF-T regulatory requirements” is part of the
SAP S/4HANA compatibility scope, which comes with limited usage rights. For more
details on the compatibility scope and its expiry date and links to further information
please refer to SAP note 2269324. In the compatibility matrix attached to SAP note
2269324, SAP ERP, add-on for Polish SAF-T regulatory requirements can be found
under the ID 131.
This means that you may choose another SAP solution or a partner solution as successor
of “SAP ERP, add-on for Polish SAF-T regulatory requirements” before expiry of the
compatibility pack license by 31.12.2025.
This note shall provide an overview to which extend the current scope of “SAP ERP,
add-on for Polish SAF-T regulatory requirements” maps with other SAP solutions and
how you may switch to the alternative functionality considering the respective scope.
This note will regularly be updated to reflect more details on the alternative functionality
and the migration.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1037
Business Process related information
Scope of SAP ERP, add-on for Polish SAF-T regulatory requirements
"SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0" is a stand-alone
solution. It is not related to the SAP standard solution "SAP Starter Solution". For
further information on the "SAP Starter Solution" see SAP Note 2304519 -
SAFT-PL: SAP solution strategy and release dates guidance.
"SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0" is comprised of
two parts:
ERP add-on "PLVAT": This solution is responsible for the generation of the
SAF-T XML files.
Desktop Application "eTransfer" (also named "PLVAT_DESKTOP"): This
application is responsible for the transmission of SAF-T XML files to
the Polish tax authorities.
The solution comprises data extraction only from the following SAP ERP and SAP
S/4HANA modules:
SAP FI
SAP MM
SAP SD
For more information about this solution, see SAP Note 2351241 - SAF-T Poland:
Release Strategy for "SAP Add-on for Polish SAF-T Regulatory Requirements (Private
Cloud Edition/On-Premise)".
The scope of the alternative functionality “SAP Starter Solution”
The “SAP Starter Solution“ comprises SAP ERP Finance and Logistics data.
It covers two stages of the end-to-end process
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1038
Settings for Data Extraction (definition of relevant parameters that control the data
extraction)
Data extraction (collection of relevant transactional data needed for file creation)
Note that the file creation, and file submission step is not covered in the „SAP Starter
Solution“. For this reason, the logic required for creating the XML file will be within
customer’s responsibility.
For guidelines about using „SAP Starter Solution“, please refer to SAP Note 2304519 -
SAFT-PL: SAP solution strategy and release dates guidance. This note will also be
regularly updated regarding any future roadmap decisions.
The scope of the alternative functionality “SAP add-on for Polish SAF-T regulatory
requirements, private cloud edition”
The solution “SAP add-on for Polish SAF-T regulatory requirements, private cloud
edition” has the same functionality as the current solution including the desktop
application “eTransfer”. As the technical basis is very similar, migration process is
comparatively easy.
Customers migrating to SAP S/4HANA Cloud, private edition need to convert their SAF-
T add-on license to license material 8013722.
The scope of the alternative functionality “SAP S/4HANA Cloud, SAP Document and
Reporting Compliance reports”
SAP Document and Reporting Compliance is part of the S/4HANA Cloud (public
edition) and covers SAF-T requirements from various countries including Poland. For a
general overview see SAP KBA 2926588 - SAF-T in SAP S/4HANA Cloud - SAP
Document and Reporting Compliance solution.
Further details can be found in the Product Assistance on SAP Help Portal. (Enter
“Poland” in the search field, then follow path: SAP S/4HANA Cloud -> Poland ->
General Functions -> Document and Reporting Compliance -> SAF-T.) The Product
Assistance is regularly updated with the latest features.
Required and Recommended Action(s)
As SAP ERP, add-on for Polish SAF-T regulatory requirements can be used until the
expiry date of the compatibility pack license which is 31.12.2025, it is up to each
customer to decide, with which of the coming SAP S/4HANA releases they want to
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1039
switch to the designated alternative functionality of another SAP solution or to switch to
an alternative partner solution.
Depending on your future landscape, you have the following options concerning SAP
solutions:
S/4HANA on-premise: “SAP Starter Solution”
S/4HANA Private Cloud Edition: “SAP Starter Solution”, “SAP add-on for Polish
SAF-T regulatory requirements, private cloud edition”
S/4HANA Cloud (Public Edition): “SAP Document and Reporting Compliance
reports”
Sufficient switching time should be considered.
For guideline about uninstalling SAP ERP, add-on for Polish SAF-T regulatory
requirements, please refer to SAP Note 2869393 - Uninstalling ABAP Add-On PLVAT.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, SAF-T Poland,
PLVAT 100, PLVAT100, PLVAT_DESKTOP_100, eTransfer, Standard Audit File,
SAFT, SAF-T, Poland, Polska, Audit, JPK, Jednolity Plik Kontrolny, Legal Change,
OECD, Tax Reporting, VAT, STANDARD AUDIT FILE F.TAX 1.0, SAP ERP, add-on
for Polish SAF-T regulatory requirements 1.0, Release Strategy, SAP Starter Solution
41.7 S4TWL - Russia Manage Additional Payment Attributes app
Application Components:FI-LOC-FI-RU
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3120536
S4TWL - Russia Manage Additional
Payment Attributes app
Symptom
You are doing a system conversion or an upgrade to SAP S/4HANA, on-premise 1909
edition. The following SAP S/4HANA Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1040
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release or SAP S/4HANA on-premise 1809 edition or lower releases.
It is not relevant if your start release is S/4HANA on-premise 1909 or later.
Solution
Business Value
New solution to maintain document attributes for Payments to tax authorities before
output in Payment Medium.
New Manage Additional Payment Attributes app offers you the following benefits:
Unified and simplified user experience via Fiori interface
Improved Mobility. The switch to Fiori delivers advantages to mobile employees.
Fiori’s simple interface lets users work with touch screens.
Increases in Productivity – Fiori-designed interfaces are easier, so they enable more
productive work.
Integration with a Manage Journal Entry app that is main report to see and check
postings.
Description
For tax payments attributes in S/4HANA on-premise 1909 and future releases Manage
Additional Payment Attributes app has to be used:
Find your Payment document in the Manage Journal Entries app and click on the
journal entry number.
Select Manage Additional Payment Attributes and enter payment attributes or change
existing one.
For more information see Tax Payments help page.
Business Process related information
Manage Additional Payment Attributes app replaces the solution:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1041
Payment attributes screen during Financial Document posting and Financial
Document change (Open FI Functional Modules J_3RF_PDOCV_2218 and
J_3RF_PDOC1430)
Note that depending on your SAP S/4HANA release and planned end of support date
previous solution will become obsolete. After end of support date these solutions will not
be updated by new legal changes or corrections. We highly recommend that you use
the Fiori based apps instead of the old previous solution.
SAP S/4HANA on-premise 1809 and previous releases
No planned end of support date
SAP S/4HANA on-premise 1909 and future releases
Only Manage Tax Payment Attributes Fiori will be supported.
Payment attributes screen during Financial Document posting and Financial Document
change (Open FI Functional Modules J_3RF_PDOCV_2218 and J_3RF_PDOC1430) is
obsolete within these releases.
Required and Recommended Actions:
Set up new Fiori app “Manage Additional Payment Attributes (Refer to SAP Note
2931354).
If you have made customer enhancements to the obsoleted Open FI function modules,
check if you need to reimplement them in the new Fiori App. Custom logic can be
implemented in the BAdI FIGLO_PMNT_FIELDS.
Train your users.
How to Determine Relevancy
Check that you have configured the Open FI module J_3RF_PDOCV_2218 for the event
2218 and Open FI module J_3RF_PDOC1430 for the event 1430 or you have entries in
Payment Attributes table J_3RF_PLAT.
Other Terms
Russia, Payment order, additional information, Payment details, J_3RF_PDOC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1042
41.8 S4TWL - SAF-T RO: Replacement of ABAP Report Solution with DRC
Solution
Application Components:FI-LOC-FI-RO, FI-LOC-SAF-RO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3256877
S4TWL - SAF-T RO: Replacement of
ABAP Report Solution with DRC
Solution
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA and are using the
functionality described in this SAP Note.
To understand if the activity “Implement the generic DRC Fiori app succeeding the
deprecated legal reports” described in Simplification item SI9: GSFIN_SAFT_RO
(S4TWL - SAF-T RO: Replacement of ABAP Report Solution with DRC Solution) needs
to be performed after the system upgrade, please check if you are using any combination
of report and country/region listed in note 2480067
Solution
Description
This SAP Note is relevant for you when your starting release for the system conversion is
an SAP ERP release or an SAP S/4HANA Finance release, where you have the ERP
SAF-T for Romania solution implemented (transactions SAFTN_E & SAFTN_G) in your
system.
Business Process related information
In S/4 Hana, the requirement of generating SAF-T files according to the legal format of
Romania is covered by the Document and Reporting Compliance (DRC) Application. For
this reason, the SAF-T Romania solution of ERP (transactions SAFTN_E & SAFTN_G)
is not to be used anymore and shall be replaced by the corresponding report defined in the
DRC app.
There is no need to migrate data. After the transition to S/4 Hana, it is still possible to
generate SAF-T files for previous reporting periods using the DRC application, no matter
if files have been generated for the same reporting period before the transition or not
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1043
Required and Recommended Action(s)
To use the DRC report for SAF-T Romania, some general configuration settings have to
be made, like for example defining the required reporting entities. Refer to the
corresponding help document.
The ERP SAF-T solution for Romania offers a monitoring app (transaction SAFTN_M).
This transaction is not supported anymore in SAP S/4HANA. If you need to keep the
details about extracted data and generated files, we recommend to download the
monitoring details before the transition. In addition, we recommend to clean up the
extraction data using transaction SAFTN_D before the transition to save database storage
space as these entries are not used anymore after the transition to SAP S/4HANA
Please note that with the transition from SAP ERPSAF-T solution for Romania to SAP
DRC, some ABAP objects ofpackage /CEECV/RO_SAFT have become obsolete.
Therefore, run the ABAP Test Cockpit (ATC) using the latest simplification item DB
content and remove all detected usages of the correspondingobjects from your custom
code.
In case you have implemented any extension to the selection logic according to note
3237660, check the need for a corresponding extension after the transition. In case you
still require an extension to the standard logic, use the available DRC extension
techniques to implement them. Find more information on how to do this in the
corresponding help document.
Other Terms
Globalization, Localization, CEE Add-on, RO, SAF-T RO, SAF-T, ANAF 1783/2021,
Romania
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1044
42.Globalization Logistics
42.1 S4TWL - Globalization – Logistics
Application Components:FI-LOC-LO, XX-CSC-BR-REP, XX-CSC-BR, FI-LOC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270312
S4TWL - Globalization – Logistics
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
The SAP Tax Declaration Framework for Brazil solution is an integrated tax management
solution that helps Brazilian companies to be in compliance while saving time and money
by reducing the operational costs with auditing, analyzes and assessments of fiscal
information; by eliminating direct and indirect costs with tax management software; and
by offering greater accuracy on fiscal planning and taxes payment.
TAXBRA tax procedure is a more flexible and up-to-date solution.
Description
The following functionality related to Country Version for Brazil is not available in SAP
S/4HANA, on-premise Edition 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.
Required and Recommended Action(s)
SAP recommends using the following:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1045
SAP Tax Declaration Framework for Fiscal and Accounting Legal Reporting.
TAXBRA tax procedure for the tax calculation.
Note: SAP Tax Declaration Framework is part of the Compatible Add-ons and requires
an additional license.
Related SAP Notes
General
SAP Note: 2244803 - Fiscal and Accounting Legal
Reporting for SAP S/4HANA, on premise edition 1511
Custom Code related information
SAP Note: 2195701
42.2 S4TWL - eDocument Framework Migration to SAP S/4HANA
Application Components:CA-GTF-CSC-EDO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2523749
eDocument Framework: Migration from
SAP ERP to SAP S/4HANA
Symptom
You have implemented the eDocument Framework in SAP ERP and want to migrate to
SAP S/4HANA.
This SAP Note contains additional steps that you must perform in order to migrate the
eDocument Framework and the country solutions that you have implemented.
Reason and Prerequisites
Reason:
In SAP S/4HANA, the SAP Application Interface Framework (AIF) Add-On has been
integrated as standard component. The AIF message index tables ZEDOAIFIDXREQ
and ZEDOAIFIDXRES have been replaced by standard tables EDOAIFIDXREQ and
EDOAIFIDXRES. In addition, BAdI implementations
ZEI_EDOC_AIF_RUNTIME_METHODS and ZEI_EDOC_AIF_V1_ACT have become
obsolete.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1046
Prerequisite:
You have implemented SAP Note 2421589 - eDocument: AIF Changes for S/4HANA
Solution
Perform the manual steps described in the attached document
2523749_Manual_Activities_V02.pdf.
You must perform the mentioned steps in your SAP S/4HANA development system and
transport the changes to the subsequent systems (for example quality and production).
You must run the migration progam EDOC_COPY_AIF_MSG_INDEX_TAB in each
client of every system where entries are available in tables ZEDOAIFIDXREQ and
ZEDOAIFIDXRES.
Date
Version
Description
23.08.2017
1
Released for customers
06.05.2019
2
Updated attachment
28.02.2020
3
Updated note and attachment that report must be executed in each
system/client
Other Terms
EDOC, eDocument Framework, ZEI_EDOC_AIF_RUNTIME_METHODS,
ZEI_EDOC_AIF_V1_ACT, ZEDOAIFIDXREQ, ZEDOAIFIDXRES
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1047
43.Industry – Cross
43.1 S4TWL - BRIM - Billing of Event Detail Records (EDR)
Application Components:FI-CA-BI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271210
S4TWL - BRIM - Billing of Event Detail
Records (EDR)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
EDR Management is used to transfer event detail records (EDR) from an external system,
manage the received information and prepare it for billing.
The BRIM solution covers CRM, CI / FI-CA (ERP) and SAP Convergent Charging
components/systems. It was developed to charge and bill single events like Toll Collects
or downloads. The Event Detail Records solution was replaced by BIT BILLING in
2008.
Business Process related information
No influence on business processes expected. All EDR customers are informed.
Required and Recommended Action(s)
To check if you use EDR Management, call the transaction SE16 and check for entries in
the table DFKKBIBILLACC_H.
Ensure that no fields contained in structure FKKBIINVBILL_I_DATA are used directly
or indicretly in custom code and/or BRF(+)-Implementations to avoid short dumps.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1048
43.2 S4TWL - BRIM - Common Object Layer (COL)
Application Components:FI-CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270317
S4TWL - BRIM - Common Object Layer
(COL)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The Common Object Layer Framework (COL framework) can be used to distribute data
(e.g. master data, provider contracts) from the SAP CRM System to the SAP Convergent
Charging and SAP ERP System. In SAP S/4HANA, on-premise edition 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 the FI-CA or CI component. Thus, the Common
Object Layer is not available in SAP S/4HANA, on-premise edition. The distribution of
objects is directly done in the software component FI-CA now.
Business Process related information
No influence on business processes expected for customers: the master data distribution
still works in SAP S/4HANA, on-premise.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1049
To check if you distribute master data with the help of the COL framework without using
the component FI-CA, call the transaction SE16 to check the table BADIIMPL_ENH.
Enter "ISX_MD_COL_SCENARIO" and "ISX_MD_COL_ADAPTER" in the field
BADI_NAME. Check if there are any entries starting with Z* or Y* in the column
BADI_IMPL (BAdI Implementation).
43.3 S4TWL - BRIM - Integration with FSCM Biller Direct (FI-CA)
Application Components:FI-CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271233
S4TWL - BRIM - Integration with FSCM
Biller Direct (FI-CA)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
With the integration of SAP Contract Accounts Receivable and Payable (FI-CA) with
FSCM Biller Direct it is possible to offer end-customers the convenience of receiving
invoices, viewing account statuses, and making payments online as a self-
service. Integration of FSCM Biller Direct with BRIM/FI-CA is part of the SAP
S/4HANA compatibility scope, which comes with limited usage rights. For more details
on the compatibility scope and it’s expiry date and links to further information please
refer to SAP note 2269324. In the compatibility matrix attached to SAP note 2269324,
“BRIM - Integration with FSCM Biller Direct” can be found under the ID 437.
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, on-premise edition.
Required and Recommended Action(s)
To check if you use FSCM Biller Direct, call the transaction SE16 to check for entries in
the table DEBPPEVENTLOG.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1050
Customers are using normally own branded web based portals. SAP therefore
alternatively offers APIs which are available with SAP S/4HANA on-premise 2021:
Managing Contract Accounts
Managing Provider Contracts
Managing Documents
Managing Installment Plans and Promise-2-Pay
Managing Dispute Cases
Sending Disconnection and Reconnection Request
Customer-Self-Services, e.g. payment via credit card or paypal
Integration with External Collection Agencies
Integration with External Cash Desks
Payment List for Business Partner in Contract Accounting
Invoice List for Business Partner in Contract Accounting
See SAP help portal for more information.
43.4 S4TWL - BRIM - Solution Sales and Billing
Application Components:FI-CAX, SD-BIL-IV-CB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271236
S4TWL - BRIM - Solution Sales and
Billing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1051
Description
The BRIM/Hybris Billing solution covers CRM, CI / FI-CA (ERP) and SAP Convergent
Charging components/systems.
The creation of provider contracts starts in CRM. For the integration of provider contracts
in SAP Contract Accounts Receivable and Payable, SAP Convergent Invoicing and
finally SD Billing with FI-AR, the provider contracts need additional information for
the processing in SD. In addition to that, business agreements that are assigned to a
business partner need to be created automatically in the background without replication in
CRM. As the follow up processing of CI Billing Documents in SD Billing is currently not
available in SAP S/4HANA, on-premise edition, this feature is not provided. Billing and
invoicing of consumption data is still possible in FI-CA but not with SD and FI-AR.
In addition, 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
in SAP S/4HANA, on-premise edition. Therefore, the additions on the provider contract
with SD Billing relevant data and the background creation of contract accounts in ERP
without existing contract accounts in CRM are not required.
UPDATE:
Meanwhile, the integration of CI Billing Documents in SAP Convergent Invoicing into
SD Billing is available for S/4HANA in the form of "SAP S/4HANA for Subscription
Billing, Sales and Distribution Option 1.0" as part of Hybris Billing. For further details
please check note 2347269 - "Release stategy of the ABAP Add-On SOLINVE 800".
Therefore, the business function FICAX_SOLESALESBILL has been reenabled and set
to customer switchable. For further details check note 2348426 - "Reactivation of
Business Function FICAXSOLSALESBILL".
Required and Recommended Action(s)
To check if you use Solution Sales and Billing, call the transaction SE16 to check for
entries in table /SOIN/CI_DOCFLOW.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1052
43.5 S4TWL - BRIM – Immediate Master Data Replication to SAP
Convergent Charging
Application Components:FI-CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271238
S4TWL - BRIM – Immediate Master
Data Replication to SAP Convergent
Charging
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In SAP S/4HANA, on-premise edition 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) is 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 immediately and independently of each other to SAP
Convergent Charging any more.
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.
Required and Recommended Action(s)
One of the following business functions needs to be activated:
FICAX_INV_2G
ISU_INV_2G
PSCD_COLLECTIONS_MANAGEMENT_4G
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1053
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.
Using an integrated SAP CRM system, you need to activate the joint master data
replication in SAP CRM by customizing the distribution schema of your order
distribution infrastructure (ODI) accordingly. The step types "Call ERP Message contract
activation MCC (PCMA)" and "Call ERP Message Contract Deactivation MCC
(PCMD)" need to be used (instead of "Call ERP Message contract activation (PCEA)"
and "Call ERP Message contract deactivation (PCED)"). In addition, call the SAP ERP
contract update with the correct settings. You can make the relevant settings and define
distribution schemas in the customizing for Customer Relationship Management under
Cross-Industry Functions -> Provider Order and Contract Management -> Transactions
-> Document Distribution ->Define Settings for Document Distribution. Activate the
joint replication of master data in SAP ERP according to the corresponding
documentation. Maintain the settings that specify how often you can retry locking the
contract for the asynchronous status updates from SAP ERP in the customizing for
Customer Relationship Management under Cross-Industry Functions -> Provider Order
and Contract Management -> Joint Distribution and Multiple SAP CC Systems for a SAP
CRM System -> Settings for Joint Distribution and Multiple SAP CC Systems -> Settings
for Document Distribution.
To check if you use the joint replication of master data, call the transaction SM31 to
check the customizing table DFKK_CC_MD_REL for entries and if the flags CCREL
and CCSEQUENCE are set. If CCREL is set and CCSEQUENCE is empty, you are
not using joint replication and need to take further action. If CCSEQUENCE does not
exist, you have to upgrade to at least SAP Enhancement Package 7 (SP08) for SAP ERP
6.0 and then take further action. If both flags are set or both flags are empty, you do
not need to do anything. Alternatively to transaction SM31, go to the implementation
guide (transaction SPRO) and check the following customizing path: Financial
Accounting -> Contract Accounts Receivable and Payable -> Integration -> Convergent
Charging -> Activate Replication of Business Partners and Accounts to SAP CC.
Migration from Direct to Joint Master Data Distribution
If you want to migrate to S/4HANA you need to use the joint master data distribution as
this is the only replication method which is supported. If you are currently using the
direct master data distribution, you need to migrate your existing distribution data before
you can activate the joint master data distribution. The migration functionality is
available from SAP ERP 6.0 EHP7 SPS14 and SAP ERP 6.0 EHP8 SPS06 onwards.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1054
Alternatively, if you are using older support packages, you can install the SAP Notes
2401583 and 2387353.
Once the migration functionality is available in your system, proceed as follows to
migrate from the direct to the joint master data distribution:
1. Suspend the master data distribution in SAP CRM before you start with the migration.
(That means business partner, business agreement/contract account, prepaid account,
provider contract and master agreement creation and changes are not distributed to SAP
ERP.)
2. Call up transaction FKKCC_MIG2JOINT in SAP ERP. It consists of three steps but
you can also execute the steps independently from each other (in this case, consider the
step sequence!):
(1) Clean-up of distribution records
The same functionality is provided by report RFKK_CC_MD_CLEAN_UP. This step is
optional but recommended. By reducing the number of existing distribution records, the
migration report will be executed faster.
(2) Creation of rating area assignment and distribution object data
This step is mandatory. It creates rating area assignment records for business partners,
contract accounts, and prepaid accounts for rating area SPACE and creates the
distribution information for provider contracts. Please note that rating areas with value
SPACE are already technically used for the joint master data replication although the
functionality of rating areas (multiple SAP Convergent Charging instances) might not be
active yet.
(3) Adaptation of distribution records
This step is mandatory. All existing distribution records of business partners, contract
accounts, and prepaid accounts that are not marked as obsolete will be adapted to the
joint master data distribution. In addition, if no rating area assignment exists for those
objects up to this point, it will be created. In this step, errors can be thrown if the object to
be processed is currently locked by another process. In this case, you need to execute this
step again when the object lock is removed so that everything is properly migrated to the
joint master data distribution.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1055
Make sure that no errors are shown in the application log of the transaction. Execute the
transaction again until all errors of the affected step are resolved.
3. Activate the joint master data distribution in SAP CRM and SAP ERP.
4. Resume the master data distribution of business partners, business agreements/contract
accounts, prepaid accounts, provider contracts, and master agreements in SAP CRM.
Note:
If erroneously distributed provider contracts still exist in SAP CRM from the direct
master data distribution, you can resolve this by choosing “Cancel Activation …and
Return to Order Processing” in the ODI distribution monitor. Afterwards, you can submit
the order once again. Then, the distribution will be done by using the joint master data
distribution.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1056
44.Industry Banking
44.1 S4TWL - Business User integration of BPs with user name and personal
number
Application Components:FS-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2900607
Simplification Item S4TWL - Business
User integration of Business Partners
with user name and personnel number
Symptom
You execute a system conversion to S/4HANA, On-Premise-Edition 1909 or higher. In
S/4HANA the fields "user name" (XUBNAME) and "personnel number"
(PERS_NR) from table BP001 of the Financial Services enhancement of the SAP
Business Partner are not available. The corresponding information needs to be retrieved
from HR. Because of this a business partner, in which one of the two fields is not initial,
needs to get connected to an HR person during the system conversion. This note
describes activities that need to be executed in the source system before conversion in
order to ensure a smooth conversion process and correct assignment between business
partner, HR person and user name.
Reason and Prerequisites
The fields BP001-XUBNAME and BP001-PERS_NR are not available any more in
S/4HANA. Applications that have accessed these fields need to access the corresponding
HR tables now, for example via CDS view I_BUSINESSUSER. This is ensured by the
corresponding applications in separate notes. To make sure that this access is successful
the corresponding bps need to be connected to an HR person or, in case HR is not active
in your system, to the corresponding object in the FIORI app to maintain employees.
This will happen during the system conversion and will only work without error if some
preconditions are fulfilled. These pre-conditions need to be checked before the upgrade
and will be integrated into the simplification item check.
Solution
Procedure for determining the relevance
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1057
The check only needs to be executed for a business partner if there is at least one entry in
table BP001 for this business partner that contains a non-initial value in one of the fields
XUBNAME or PERS_NR.
Check details
A check class will be integrated into the Simplification Item Check Report
/SDF/RC_CHECK_START. Technically this class is delivered with note 2907836. This
class checks if all pre-conditions are fulfilled so that the integration of the corresponding
BPs into HR or HR app are met. In case of errors the migration to S/4HANA can be
started only after these errors have been solved.
The following checks are executed centrally in all clients of your system (apart from 000
and 066) and per client for all business partners that were found by the above condition:
I. Generic checks (independent if HR is active or not):
For each business partner found in BP001 an entry in the header table BUT000 must
exist.
[This check is a pre-caution as we had few customers with this kind of
inconsistency in the past]
The corresponding business partner needs to be a person (partner category 1).
The corresponding business partner needs to be assigned to a role with role category
"Employee" (role category BUP003 in table TB003 - can be maintained via view
V_TB003 in transaction SM30).
In case there is an entry in table USR21 for the user name from BP001-XUBNAME,
the following conditions dependent on field USR21-IDADTYPE must be
fulfilled:
IDADTYPE 00: The GUID value in USR21-BPPERSON must be initial
IDADTYPE 01 and 03: This IDADTYPE must not be assigned
IDADTYPE 02 and 04: The GUID in USR21-BPPERSON must not be initial and
must be equal to the PARTNER_GUID in table BUT000 for the corresponding
business partner.
The user name (BP001-XUBNAME) and personnel number (BP001-PERS_NR) of
the corresponding business partner must not be assigned to several business
partners.
II. Additional checks for the case that HR is not active:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1058
If BP001-XUBNAME is not initial: A central person for the business partner
number with assigned user name exists in HR table HRP1001 and the user name
needs to be identical to BP001-XUBNAME.
If BP001-XUBNAME is not initial: A central person for the business partner user
name exists in HR table HRP1001 and the business partner assigned to this
central person must be identical to BP001-PARTNER.
III. Additional checks for the case that HR is active:
If BP001-PERS_NR is not initial: the value in field PERS_NR must be numeric and
have a maximum length of 8 digits
The business partner must be assigned to a central person in table HRP1001 via
business partner number in field SOBID (and values SCLAS = 'BP', RSIGN = 'B',
RELAT = '207' and the corresponding plan variant - field PLVAR - from table
T77S0 for the client)
A central person for the business partner with assigned personnel number must exist
in table HRP1001 and the personal number needs to be identical to BP001-
PERS_NR.
The central person assigned to the bp needs to have an entry in HR table PA0105 and
the personnel number needs to be identical to BP001-PERS_NR
If BP001-PERS_NR is not initial:
For this PERS_NR exactly one central person must exist in table HRP1001 which
is assigned to the same business partner, and
for this PERS_NR a user name in table PA0105 must exist with the same user
name as in BP001-XUBNAME
If BP001-XUBNAME is not initial:
An entry for this user name needs to exist in table PA0105 with the same
PERS_NR and the user name needs to be identical to BP001-XUBNAME, and
for this user a central person in table HRP1001 needs to exist with the same
personnel number assigned to the same business partner.
In all cases an error is returned when the condition is not met
Necessary activities in case of errors from the check class
The check class CLS4SIC_FSBP_BP001_HR is provided by SAP and integrated into
report /SDF/RC_START_CHECK. This means that the relevance check can be started
via this report. Further activities are only necessary in case the check class returns at least
one error. These activities are described in the following:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1059
I. Generic checks
In case no BUT000 entry exists for a BP001-entry: execute
report FS_BP_DELETE_ORPHANED_DATASETS in the affected client to
delete orphaned BP001 entries.
Business partner is not of category "Person" (bp category 1): For such business
partners you need to delete the two fields from table BP001.
Role employee is not assigned to the relevant bps: If this check returns an error you
need to create a role with role category "employee" (BUP003) for this bp in table
BUT100. In the simple case you can use role BUP003. Mass creation of role
BUP003 or a custom role can be achieved using transaction MASS for object type
BUS1006 (Business Partner). Alternatively create a small report in customer
name space and call BAPI_BUPA_ROLE_ADD_2 in it.
Inconsistencies in table USR21: You need to correct the concerned entries from table
USR21 in the following way:
IDADTYPE 00: delete the GUID value in field USR21-BPPERSON
IDADTYPE 01 and 03: delete the complete entry from table USR21
IDADTYPE 02 and 04: enter the entry from BUT000-PARTNER_GUID in field
USR21-BPPERSON
The same user name or the same personnel number is assigned to several business
partners: check the assignments and adapt them in a way that every user name and
personnel number is only assigned once in table BP001.
II. Additional checks in case HR is not active:
If BP001-XUBNAME is not initial: Make sure that a central person for the business
partner number with assigned user name exists in HR table HRP1001 and the user
name in HRP1001 is identical to BP001-XUBNAME.
If BP001-XUBNAME is not initial: Make sure that a central person for the business
partner user name exists in HR table HRP1001 and the business partner assigned
to this central person is identical to BP001-PARTNER.
III. Additional checks in case HR is active:
If BP001-PERS_NR is not initial: make sure that the value in field PERS_NR is
numeric and has a maximum length of 8 digits or delete the field BP001-
PERS_NR for this business partner.
Create a central person for this business partner in table HRP1001 via business
partner number in field SOBID (and values SCLAS = 'BP', RSIGN = 'B', RELAT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1060
= '207' and the corresponding plan variant - field PLVAR - from table T77S0 for
the client)
Assign the personnel number from BP001-PERS_NR to corresponding field of the
central person entry in table HRP1001.
Create an entry in table PA0105 for the central person and make sure that the
personnel number is identical to BP001-PERS_NR.
If BP001-PERS_NR is not initial:
Make sure that for this PERS_NR exactly one central person exists in table
HRP1001 which is assigned to the same business partner, and
for this PERS_NR a user name in table PA0105 exists with the same user name as
in BP001-XUBNAME.
If BP001-XUBNAME is not initial:
Make sure that an entry for this user name exists in table PA0105 with the same
PERS_NR in which the user name is identical to BP001-XUBNAME, and
for this user a central person in table HRP1001 exists with the same personnel
number assigned to the same business partner.
Further actions some time after the conversion
After the conversion all entries in the two fields BP001-PERS_NR and BP001-
XUBNAME (including the flags BP001-HR_ORG_FLAG and BP001-STAFF_GRP
need to be deleted.
Before you do this you should wait some time in order to be sure that the user name and
personal number are fetched correctly from HR or the HR app by the applications.
The deletion should be done at the latest, before you start planning the next upgrade to a
higher release level of S/4HANA.
Other Terms
SAP Business for Financial Services, Business Partner, SAP BP, FSBP, BP001, user,
user name, personal number, XUBNAME, PERS_NR, HR Integration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1061
44.2 S4TWL - FSBP Table Additional Partner Numbers (BPID001) obsolete
Application Components:FS-BP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3004812
S4TWL - FSBP table Additional Partner
Numbers (BPID001) is obsolete
Symptom
You execute a system conversion from ERP to S/4HANA or an upgrade from a lower
S/4HANA release to a higher one (2021 or higher).
From S/4HANA 2021 onwards the Financial Services Business Partner table Additional
Partner Numbers (table name BPID001) is obsolete. The data of this table have to be
migrated to table BUT0ID. This note describes activities that have to be executed in order
to perform the migration in the source system before the conversion.
Reason and Prerequisites
Financial Services Business Partner table Additional Partner Numbers (BPID001) must
not be used any more from S/4HANA 2021 onwards. The table is very similar to the
central business partner table Identification Numbers (BUT0ID), therefore the table the
migration into the Identification Numbers table BUT0ID which was optional up to now
will be enforced now.
Solution
Procedure for determining the relevance
The migration needs to be executed as soon as there is at least one entry in table
BPID001 in any of the clients of your system apart from 000 and 066.
There will also be a consistency check class that is triggered by the SUM process. SUM
process will be stopped if there are data in table BPID001 in one of the clients.
Required and recommended actions
In case there are entries in table BPID001 these need to be migrated to table BUT0ID and
deleted afterwards.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1062
In SAP note 1556353 you can find a detailed description what needs to be done to
execute this migration.
The main steps are the following:
Creation of a mapping for customizing (BPID001 -> BUT0ID)
BADI implementation in case of customer-specific enhancement in table BPID001
Activation of business function CA_FSBP_MIGRATION_ID (creates new
customizing entries in table BUT0ID)
Migration of BPID001 data to BUT0ID table (including migration of change
documents)
The migration is implemented via the ASU toolbox. This means that you will be guided
through the whole process supported by the system after starting ASU toolbox. For
details how to start this guided process please check note 1556353 and the referenced
note 1000009.
Other Terms
SAP Business for Financial Services, Business Partner, SAP BP, FSBP,
BPID001, Additional Partner Numbers, BUT0ID, Identification Numbers
44.3 S4TWL - SEM Banking
Application Components:IS-B-PA, IS-B-DP, IS-B-RA, IS-B-SA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270318
S4TWL - SEM Banking
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1063
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") or other
applications, 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.
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 available in SAP S/4HANA
All SEM Banking related transaction codes for
"Datapool", "Profit Analyzer", "Risk Analyzer"
and "Strategy Analyzer".
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).
Moreover the option to archive (delete) obsolete SEM Banking data (after having
switched off SEM Banking and before migrating the system to SAP S/4HANA) should
be considered, in order to avoid that unnecessary data is kept in the SAP S/4HANA
environment. Possible candidates are Banking operating concerns (as part of the SEM
Banking Profit Analyzer) or variable transactions (as part of the SEM Banking Datapool),
but please note that a customer-specific analysis is mandatory, in order to ensure that
only obsolete data is going to be archived (deleted).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1064
How to Determine Relevancy
There is an active risk management area and / or there is an active Banking operating
concern in the system
Related SAP Notes
Custom Code related information
For more details see SAP Note 2211665
Other Terms
SEM Banking
44.4 S4TWL - CML-specific functions with regard to collaterals and
collateral objects
Application Components:FS-CML
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2369934
S4TWL - CML-specific functions with
regard to collaterals and collateral
objects
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
FS-CML Consumer and Mortgage Loans: The CML-specific functions with regard to
collaterals and collateral objects are not available in SAP S/4HANA (including the SAP
Simple Finance editions).
(Remark: See also the entry with the subject "Real Estate Classic" in the "Simplification
List for SAP S/4HANA, on-premise edition 1511".)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1065
Therefore it's not allowed to use CML-specific functions with regard to collaterals and
collateral objects in the context of SAP S/4HANA (including the SAP Simple Finance
editions).
Examples for transactions, which must not be used, are:
Object Processing (Create, Change and Display) - FNO1, FNO2 and FNO3
Collateral Value Calculation (Create, Change and Display) - FN61, FN62 and FN63
Collateral (Create, Change and Display) - FNO5, FNO6 and FNO7
Of course all customizing transactions and settings, which are related to the CML-
specific functions with regard to collaterals and collateral objects, must not be used, too.
Solution
At this point, it is highly recommended to use the functions of application FS-CMS
Collateral Management.
The transition from the CML-specific functions with regard to collaterals and collateral
objects to FS-CMS must take place before the transformation to SAP S/4HANA.
In principle such a transition consists of two steps:
Implementation (i.e. configuration and customizing etc.) of FS-CMS
Migration of data from FS-CML to FS-CMS
Other Terms
RE, Classic, RE-FX Real Estate Management, RE Classic, RE-Classic
Land Register, Land Registry
Business Partner
CML collaterals and collateral objects
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1066
44.5 S4TWL - Deprecation of app F3987
Application Components:FI-GL-GL-ADB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3209838
S4TWL - Deprecation of Average Daily
Balance Key figure Report App ( F3987
)
Symptom
You want to use Average Daily Balance Key figure Report app F3987.
Reason and Prerequisites
The Average Daily Balance Key figure Report App will be deprecated in on premise S/4
HANA 2022 and will become obsolete.
We recommend you to switch to the successor app W0166, as soon as possible.
Solution
Description
The Average Daily Balance Key figure Report App will be deprecated in on premise S/4
HANA 2022 and will become obsolete.
We recommend you to switch to the successor app W0166, as soon as possible.
Business process related information
The Average Daily Balance (ADB) is a figure that represents the average balance of an
account for a specific period. The app F3987 allows you to calculate ADBs for intra-
month dates based on the posting date of FI documents.You can also calculate sevaral
other key figures, such as the year-to-date average balance. This app therefore allows you
to calculate efficiently and accurately the ADB at any point during a year.
With the new app W0166, you can display average daily balances and spot balances. You
can do this for each ledger and all company codes. Using this app, you can add the
measures and dimensions by using drag and drop functions to provide a user-friendly
interface. Also, this allows you to display data in a hierarchical format.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1067
Required and Recommended Actions
Anyone using F3987 app should switch to the successor app W0166.
How to Determine Relevancy
If you are using F3987 app, this deprecation note is applicable for you.
Other Terms
F3987, ADB, ADB Key figure report, ADBKFC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1068
45.Industry Beverage
45.1 S4TWL - IS-Beverage (Excise Duty)
Application Components:SD-SLS-PLL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2531942
IS-Beverage functionality depricated:
Excise Duty is unavailable in S4HANA
Symptom
The IS-Beverage functionality Excise Duty is unavailable in S4HANA. In 2004 the IS-
Beverage solution has been moved to ERP. Some of the functionalities were never
available for ERP customers. The functionalitis which were never available in ERP as
well as some of the later functionalities are deprecated in S4HANA.
Reason and Prerequisites
With the transition from ERP to S/4HANA old Beverage functionalities like Excise Duty
will be unavailable.
Solution
For detailed information on how to identify which of your custom code objects might
need to be adapted in order to be compatible with SAP S/4HANA, please refer to
SAP note 2190420
https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-custom-code-
adaptation-process/
Other Terms
IS-Beverage; S/4HANA; Excise Duty; Deprication
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1069
45.2 S4TWL - IS-Beverage (Sales Returns)
Application Components:SD-BF-EC, SD-SLS-RE-SR, SD-SLS-PLL, MM-IM-ED, SD-BF-AC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2531884
IS-Beverage functionality Sales Returns
is unavailable in S4HANA (equivalent
exists)
Symptom
In 2004 the IS-Beverage solution has been moved to ERP. Some of the functionalities
were never available for ERP customers. The functionalitis which were never available in
ERP as well as some of the later functionalities are deprecated in S4HANA. The IS-
Beverage functionality Sales Returns is unavailable in S4HANA.
For the deprecated IS-Beverage functionality Sales Returns there is the successor
Advanced Return Management available.
Reason and Prerequisites
With the transition from ERP to S/4HANA old Beverage functionalities will be
unavailable.
Solution
For detailed information on how to identify which of your custom code objects might
need to be adapted in order to be compatible with SAP S/4HANA, please refer to
SAP note 2190420
https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-custom-code-
adaptation-process/
Other Terms
IS-Beverage; S/4HANA; Sales Returns; Deprication
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1070
45.3 S4TWL - IS-Beverage (Pendulum List)
Application Components:SD-BIL-RB-PL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2531962
IS-Beverage functionality depricated:
Sales Pendulum List is unavailable in
S4HANA
Symptom
The IS-Beverage functionality Pendulum List is unavailable in S4HANA. In 2004 the IS-
Beverage solution has been moved to ERP. Some of the functionalities were never
available for ERP customers. The functionalitis which were never available in ERP as
well as some of the later functionalities are deprecated in S4HANA.
Reason and Prerequisites
With the transition from ERP to S/4HANA old Beverage functionalities like Pendulum
List will be unavailable.
Solution
For detailed information on how to identify which of your custom code objects might
need to be adapted in order to be compatible with SAP S/4HANA, please refer to
SAP note 2190420
https://blogs.sap.com/2017/02/15/sap-s4hana-system-conversion-custom-code-
adaptation-process/
Other Terms
IS-Beverage; S/4HANA; Pendulum List; Deprication
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1071
46.Defense&Security
46.1 S4TWL - DFPS eSOA services
Application Components:IS-DFS-OF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273297
S4TWL - eSOA Services for DFPS
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Technology migration
Solution
Description
The enterprise services (eSOA services) for DFPS are not available in SAP S/4HANA.
Currently there is no functional equivalent available. Depending on customer requests
they may be replaced by OData services in the future.
Business Process related information
The feature of accessing Defense & Security data via eSOA services (Service Definitions
and XML name spaces containing *DFPS*) is not available in SAP S/4HANA.
Examples of affected service definitions:
/ISDFPS/FUERPMNTASSGMNTUPDRC
- FunctionalUnitERPMaintenanceAssignmentUpdateRequestConfirmation_In
/ISDFPS/FUERPSRVASSGMNTUPDRC -
FunctionalUnitERPServiceOfferUpdateRequestConfirmation_In
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1072
Implement Business Scenarios and Business Processes based on the functionality
available within SAP S/4HANA.
How to Determine Relevancy
The simplification item is not relevant, if Enterprise Extension EA-DFP
(DefenseForces&PublicSecurity) is deactivated. In this case no additional checks
are necessary. You can check the status via transactions SFW_BROWSER (Switch
Framework Browser) or SFW5 (Switch Framework Customizing).
If Enterprise Extension EA-DFP is active in the SAP Business Suite system, you can
check via transactions WSADMIN or SOAMANAGER for activated DFPS eSOA
services.
Customers with activated eSOA services for DFPS in Business Suite can execute the
system conversion. Nevertheless the functionality is not available within SAP S/4
HANA.
Other Terms
eSOA, Enterprise Services, DFPS, Defense Security, Information System Integration
Bundle, Item Unique Identification Bundle, FunctionalUnitERP,
SecurityServicesUnitERP
46.2 S4TWL - BI content, Datasources and extractors for DFPS
Application Components:BW-BCT-DFS-OF, BW-BCT-DFS-PM, BW-BCT-DFS-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273294
S4TWL - BI content, Datasources and
Extractors for DFPS
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Technology migration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1073
Solution
Description
BI content, Data Sources and Extractors for DFPS are not available in SAP S/4HANA.
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.
Business Process related information
BI content based on data sources and extractors for DFPS in the SAP Business Suite is
not available in SAP S/4HANA.
Required and Recommended Action(s)
Implement Business Scenarios and Business Processes based on the functionality
available within SAP S/4HANA.
Start exploring the new possibilities for real-Time operational reporting using SAP
S/4HANA Analytics which enables key users to create and modify reports, KPIs or any
other analytical artefacts according to their needs.
How to Determine Relevancy
You can check in the following way whether SAP BW OLTP Sources for DFPS are
actively used:
Call transaction SE16N for table ROOSOURCE
Enter selection criteria APPLNM = IS-DFS-BW (Application Component), and
OBJVERS = A (active OLTP Source Version)
In case of results being displayed for the selection, active SAP BW OLTP sources for
DFPS exist.
In this case you may want to check details in transactions RSA2 or RSA5.
Customers with active BI content or data sources for DFPS in Business Suite can execute
the system conversion.
Nevertheless the functionality is not available within SAP S/4 HANA.
Other Terms
BW, BI, Business Information, Data Sources, Extractors, DFPS, Defense Security
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1074
46.3 S4TWL - Integration of DFPS with Investigative Case Management
(ICM)
Application Components:IS-DFS-ICM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273299
S4TWL - Integration of DFPS with
Investigative Case Management (ICM)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1075
How to Determine Relevancy
Check in transaction SFW5, whether Business Function DFPS_ICM_OF is available and
has been activated in your exsiting SAP Business Suite system.
Other Terms
ICM, Investigative Case Management, DFPS, Defense Security
46.4 S4TWL - Integration of DFPS with Environmental Compliance
Application Components:IS-DFS-EHS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273311
S4TWL - Integration of DFPS with
Environmental Compliance
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1076
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. Nevertheless 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.
Other Terms
Environmental Compliance Health Safety, EHS, EH&S, DFPS, Defense Security
46.5 S4TWL - Force organization, personnel and sustainment for DFPS
Application Components:IS-DFS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3018378
S4TWL - Defense Forces & Public
Security (DFPS)
Symptom
You are using the industry solution Defense Forces & Public Security (DFPS). You are
considering a system conversion from SAP ERP to SAP S/4HANA or an upgrade from a
lower to a higher SAP S/4HANA release. The following SAP S/4HANA simplification
item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1077
Description
Defense Forces & Public Security (DFPS) is part of the SAP S/4HANA compatibility
scope, which comes with limited usage rights. For more details on the compatibility
scope and its expiry date and links to further information please refer to SAP note
2269324. In the compatibility matrix attached to SAP note 2269324, Defense Forces &
Public Security (DFPS) can be found under the ID 123 (7017755, SAP Force
Organization & Personnel for D&S), 124 (7017756, SAP Force Sustainment for D&S).
This means that you need to migrate from Defense Forces & Public Security (DFPS) to
its designated alternative functionality Defense & Security (D&S) before expiry of the
compatibility pack license.
Business Process related information
A description of functionality in compatibility scope (DFPS) you can find in the
S/4HANA Feature Scope Description in section SAP S/4HANA Compatibility Packs >
Industries > Public Services > Defense and Security.
A description of the functionality of the alternative solution (D&S) you find in the same
document in section SAP S/4HANA LoB Products for specific industries > Public
Service > Defense and Security.
Required and Recommended Action(s)
As DFPS can be used until the expiry date of the compatibility pack license, it is up to
each customer to decide, when (with which of the coming SAP S/4HANA releases) they
want to migrate to the designated alternative functionality. Nevertheless, the decision at
which point in time this will be done, should be taken early in advance in order to plan
accordingly for the migration efforts.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Defense Forces &
Public Security, DFPS, Defense & Security, D&S
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1078
47.Industry DIMP - Aerospace & Defense
47.1 S4TWL - Collective Processing Pegging
Application Components:IS-ADEC-GPD, IS-ADEC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270832
S4TWL - Pegging: Collective
Processing
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1079
47.2 S4TWL - Actual labor and costing
Application Components:IS-ADEC-ALC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2445654
S4TWL - Actual labor and costing
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The DIMP Enhancements Actual Labour Costing / Time Recording functionality is not
available with SAP S/4HANA.
No further developments are planned in this area.
How to determine relevancy
Following objects are not available with SAP S/4HANA.
Transactions not available with SAP S/4HANA
ADAA
Programs/Reports not
available with SAP S/4HANA
AD02PRCE - Program to compute actual labor pricing
AD02ACTV - Activity allocation conversion
AD02_HIERARCHY_DETERMINE_PSJ - Project based
payment run - get project hierarchy
Required and Recommended Action(s)
No influence on business processes expected.
Eliminate the indicated usages from your customer objects.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1080
47.3 S4TWL - Renovation of Grouping, Pegging and Distribution
Functionality
Application Components:IS-ADEC-GPD
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
3246460
SAP S/4HANA 2022, Aerospace and
Defense : Restriction Note
Business Impact
2933435
S4TWL - Grouping Pegging Distribution
(GPD) in SAP S/4HANA
Symptom
You convert your system to SAP S/4HANA and then migrate from SAP S/4HANA
Grouping, Pegging, Distribution (GPD) to SAP S/4HANA Project Manufacturing
Management and Optimization (PMMO).
A side-by-side approach of SAP S/4HANA GPD and PMMO is not possible. You must
migrate your data from GPD to PMMO before using PMMO (unless you use a greenfield
approach).
Reason and Prerequisites
GPD is a deprecated component in SAP S/4HANA. This means that it is still supported
but will be replaced by the PMMO solution in the long term. The date is not set yet.
This note is relevant if you use GPD in an SAP ECC release or SAP S/4HANA release.
Solution
Description
Project Manufacturing Management and Optimization (PMMO) with the application
component LO-PMM is planned to replace the solution Grouping, Pegging, Distribution
(GPD) with the application component IS-ADEC-GPD.
PMMO is a standard function in the project-based production environment and is a core
application component in SAP S/4HANA Enterprise Management. It contains functions
that allocate the individual cost types from grouped stock to the WBS elements that drive
demand requirements.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1081
Business Value
The following items in PMMO list the change of existing functions.
With SAP S/4HANA 2020 release:
PMMO offers multiple improvements compared with GPD, including:
PMMO uses parallel processing in the pegging and distribution programs and code
pushdown in the pegging program. Calibration reports are available to aid in
determining optimal parameters for the parallel processing.
Many improvements have been made in PMMO to the application log of pegging and
distribution programs with error, information and warning messages.
The purchase order item schedule lines are tracked for open orders in PMMO in sync
with MRP.
There are material document checks during goods movement for error handling in
place of termination messages.
The goods receipt system date is used instead of the document date or posting date on
the stock table.
For Stock Transport Order (STO), GPD Pegging could only support a maximum of
two plants in case of Type-2 grouping, whereas in PMMO Pegging STO parts are
not constrained.
Lower-level granular locking during pegging (the option to not lock during pegging)
is also available.
The excess handling logic was improved by assigning excess to the WBS elements in
the group that caused the excess.
The purchase order number, item number, material number and plant from the
pegging assignment is used to fill the corresponding CO posting record (no
customer modification is necessary as in GPD).
The CO posting document number is displayed with a navigation link in the
distribution results when executing online.
Redundant data and aggregates in the distribution of actual costs are eliminated.
The following new functionality were added in PMMO:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1082
The pegging table has a new data structure that provides component to top-level
product information.
The pegging assignment table includes the “Stock Ownership Group WBS” field to
be consistent with the other pegging tables.
The original goods receipt date is used for the goods issue reversal to maintain First-
In First-Out (FIFO).
Additional modernization efforts and flexibility options in PMMO include:
Classes and methods are provided to enable customers to incorporate custom code in
place of BAdIs in GPD.
There is MRP area support at plant level that is also consistent with SAP S/4HANA.
Support for additional goods movement type processes
With SAP S/4HANA 2021 release:
PMMO offers multiple improvements compared with GPD, including:
Support for collective order(or direct production) chain in the pegging table where
several planned or production orders form a chain (linked) from top leading order
on down including multiple branches
Support for blocked and restricted stock depending on the MRP configuration setting
Support for serial number consumption on the component side of the order selecting
the replenishment off the stock table that will be consumed on the next higher.
Support for rounding in pegging based on unit of measure.
Materials are tracked at the subcontract vendor level like inventory adjustments and
scrapping
During conversion of planned orders to production order, planned order to purchase
requisitions, and purchase requisition to purchase orders the pegging records are
updated in the pegging table.
Support for vendor down payments by distributing the down payments cleared to
received (in stock) quantities and the remaining to the open (in procurement)
quantities.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1083
Support of costed option of non-valuated stock gains by creating a production order
without a header material number.
PMMO to support MRP configuration include/exclude vendor confirmation and
Inbound delivery doc.
The following new functionality are available:
Production order split to move components from parent order to child order.
Additional modernization efforts and flexibility options in PMMO include:
A Fiori report that will provide pegging assignments information with associated
distributed costs.
With SAP S/4HANA 2022 release:
PMMO offers multiple improvements compared with GPD, including:
Configurable option to record pegging assignment history to track any changes during
pegging update run and pegging manual changes.
Manually adjust pegging assignment entries.
Prevent distribution of actual costs posting to closed WBS via a configurable option.
Record pegging and distribution update run header data to PMMO_PEG_HEADER
and PMMO_DIS_HEADER tables.
The following new functionality is available:
Production order split functionality that enables actual cost distribution for split
orders between parent and child in product cost controlling.
Additional modernization efforts and flexibility options in PMMO include:
Current Pegging Assignments Fiori App to analyze the pegging assignment results.
Pegging Assignments History Fiori App to analyze the pegging assignment history as
of a certain date and time.
Order Actual Cost Rollup Fiori App to get the true actual cost (direct costs only) for
PMMO relevant orders.
Enhancements by using SAP ABAP class events to enhance the standard coding.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1084
Business Process related information
There are three major features within PMMO:
Grouping (provided by Project Systems)
Pegging Assignment
Cost Distribution
The PMMO application is designed for multiple industries and costing methods. One or
more of the three features may benefit the customers’ business models. The first release
is planned for an Engineer-To-Order (ETO) business model that requires all three.
Pegging
PMMO Pegging data is tightly aligned with MRP by capturing the “Next Higher
Assembly (NHA) Order Number” data and “Top Level Demand” data on each order
assignment record. When Project Systems is involved, their WBS element numbers will
be captured. The pegging records are the cost mapping information for cost distribution.
Distribution
The assignment records are the mapping information for the cost distribution program to
push costs to the appropriate destination. This is how costs get expensed to the project
which is a Non-Valuated (True Actual) costing method.
Costing scenarios that may see PMMO distribute costs:
PMMO-relevant purchase order items from the goods receipt postings and from
vendor invoices being posted
PMMO-relevant production order costs, such as labor, overheads, and plant stock
material costs (non-valuated, such as material master amounts). Also, any costs
from purchase order items attached to such production orders.
Migration from GPD
Prerequisite: Current GPD customers (on ECC or Suite on HANA) planning to deploy
PMMO would first need to move the data to SAP S/4HANA GPD tables purely for
technical purposes only.
A report-based migration tool is provided as part of PMMO included in SAP
S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1085
The report can be used to migrate SAP S/4HANA GPD data to the new SAP
S/4HANA PMMO pegging and distribution tables.
Customers would be responsible for enhancing the delivered report to migrate custom
data fields and tables.
More information can be found here
After GPD to PMMO Migration (and before any new goods movements transactions are
posted), pegging results between GPD and PMMO may differ and could result in cost
distribution postings differences. These differences can be anticipated due to the
improvements in PMMO pegging compared to GPD pegging.
47.3.1 Required and Recommended Action(s)
1) New functionality and enhancements are planned for the PMMO
solution according to the SAP roadmap. GPD in SAP S/4HANA will be in maintenance
(until a date yet to be decided).
2) PMMO features shipped in the SAP S/4HANA releases and features planned for
any future release can be found in the Roadmap Explorer. Based on this information, the
customer may decide on the relevant SAP S/4HANA release to move from GPD to
PMMO, considering their specific business scope.
3) A Migration report will be provided for moving data from SAP S/4HANA GPD to
PMMO.
4) The functionality provided in PMMO in SAP S/4HANA 2020 release is
recommended for blueprinting/template development activities in implementation
projects. Additional functionality and enhancements (including comparable scope as
GPD) is available with PMMO in SAP S/4HANA 2021 release and onwards, which can
be implemented as baseline for productive use depending on customer business
requirements.
5) It is recommended that new SAP customer (greenfield) implementations start with
PMMO.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1086
47.4 S4TWL - Cost Distribution Processing
Application Components:IS-ADEC, IS-ADEC-GPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270834
S4TWL - Cost Distribution Processing
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1087
47.5 S4TWL - Manufacturer Part Number
Application Components:IS-ADEC-MPN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2348023
S4TWL - Manufacturer Part Number
and its System Conversion to SAP
S/4HANA
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
This SAP Note contains business process-related information of system conversion from
ECC-DIMP to SAP S/4HANA on MPN.
Solution
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:
Special character '*', '&' and ',' are not allowed in material number
In S/4HANA it is not allowed to use the following special characters ('*', '&', ',') in the material
number. If you have in table MATERIALID in the field MATNR_EXT such characters, the material
need to be renamed.
Leading space character not allowed in material number
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1088
In S/4HANA it is not allowed to use leading space(s) in the material number. If you have in table
MATERIALID in the field MATNR_EXT such entries, the material number conversion will alter the
S/4 material number (MATNR_LONG) to have leading '_' characters. Communication in external
interfaces in a DIMP LAMA compatibility mode is not affected, as the original MATNR_EXT
content remains intact during the conversion.
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 be suffixed with the delimiter specified in the
customizing settings(This behavior is enabled only if lexicographical flag is switched
off).
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.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1089
'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.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1090
'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 name 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1091
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.
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.
Additonally 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.
Usage of MATERIALID table
MATERIALID table should not be used any more in the coding. For more information
refer the section 'Reference to MATERIALID table' of note 2228241.
Web services
Web services will change incompatibly when conversion exit is used and MPN material
without manufacturer is sent. In S/4HANA if the MPN material is numerical and external
manufacturer is not mentioned, then the delimiter is added as suffix to the MPN Material
number. For eg: MPN Material number, if no external manufacturer is provided, is
displayed as shown below:
DIMP LAMA
S/4HANA
000123
000123:
BI Content
Proposed solution for DIMP LAMA anyway relies on BI content modification by the
customer (FAQ note 735529 as proposal, BW note 906913)
For S/4HANA connection customer shall adapt this existing modification. Replicate
MATERIALID again (we have enhanced this extractor) and add a new transfer rule
where needed when he uses the “old” solution
May get a visible difference between MATNR in S/4HANA and in BW for MPN w/o
manufacturer
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1092
Deprecated objects
Object
Type
Object Name
Remarks
FUNC
MPN01_CHECK_MPN_CONVERSION
It is no longer relevant as there is no
conversion done for the MPN Material.
MPN Material is stored directly in
MARA-MATNR.
DTEL
MPN_OUTLEN
Use the data element 'OUTPUTLEN'
instead
MSAG
AD_MPN_MESS
The messages contained in the
message class is not relevant. Should
you need it, please copy the message
to a new message class.
PROG
FMPN30LCCD
Not relevant. Remove the usage of this
include from your code
PROG
MPNUPGRADE01
MPNUPGRADE02
MPNUPGRADETOP
RMPNAFTERUPGRADE
This is a reconciliation report after
upgrade in EHP releases. Not required.
There are separate conversion
programs available for conversion to
S/4HANA1610 release.
PROG
RIXPRA_ISAD30
RIXPRA_ISAD30_3
Conversions for older release in EHP.
No longer relevant
Required and Recommended Action(s)
Refer to the below SAP Notes before performing the system conversion to SAP
S/4HANA:
SAP Notes
2334012
2334008
2270836
2360860
Other Terms
SAP S/4HANA System Conversion, MPN, Manufacturer Part Number,
S4_TRANSFORMATION
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1093
47.6 S4TWL - Flight Scheduling
Application Components:IS-ADEC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270837
S4TWL - Flight Scheduling
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1094
47.7 S4TWL - Enhancements Actual Labour Costing / Time Recording
Application Components:IS-ADEC-ALC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270838
S4TWL - Enhancements Actual Labour
Costing / Time Recording
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The DIMP Enhancements Actual Labour Costing / Time Recording functionality is not
available with SAP S/4HANA.
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.
Required and Recommended Action(s)
None
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1095
47.8 S4TWL - Enhancements Subcontracting Special Stock Types Not
Available
Application Components:IS-ADEC-SUB, IS-ADEC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270839
S4TWL - Enhancements subcontracting
special stock types not available
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 from SAP
S/4HANA 1610 onwards.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1096
47.9 S4TWL - AECMA SPEC 2000M Military Version
Application Components:IS-ADEC-SPC, IS-ADEC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270840
S4TWL - AECMA SPEC 2000M Military
Version
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Custom code check
2382203
47.10S4TWL - Obsolete transactions and Enhancements in GPD
Application Components:IS-ADEC-GPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2445653
S4TWL - Obsolete transactions and
enhancements in GPD
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1097
Solution
Description
Grouping, Pegging, Distribution (GPD ) is an enhancement to the standard functions in
the project-based production environment.
You can combine material requirements from different work breakdown structures
(WBS) elements (across several projects or plants) into one or more grouping WBS
elements for common inventory management and material requirements planning (MRP).
Therefore, you can achieve greater efficiency and cost savings when procuring material.
The ability to group and plan material requirements across different projects, however,
should not be at the expense of good financial monitoring and allocation. GPD also
contains functions that allow you to allocate the individual cost types from grouped stock
to the original requirements and also to the WBS elements that caused the requirements.
Benefits such as optimized lot sizes and resource-related billing help you control project
costs.
Following transactions are not available with SAP S/4HANA.
CANCDIS01 - Transaction for canceling distribution results is not available in SAP
S/4HANA. From the functional standpoint, distribution should never be canceled.
There is no alternative transaction available for this.
PEG12 - Transaction is used to execute pegging for only one grouping WBS element
that participated in the group to group transfer. Old pegging transaction (PEG01)
is no longer available with SAP S/4HANA.
New pegging transaction (PEG01N) in SAP S/4HANA doesn't support the above
mentioned functionality with one WBS element and all the grouping WBS's participating
in the group to group transfer are considered.
There is no alternative transaction available to the above mentioned obsolete
functionality.
PEG13/PEG15 - New pegging transaction(PEG01N) doesn't consider gathering
replenishment objects in to scope. And this makes the transactions PEG13 and
PEG15 in the SAP S/4HANA obsolete. There is no alternative transactions for
this functionality.
How to Determine Relevancy
The entries in the table 'PEG_TASS' indicates the usage of the functionality by the
customer and this business impact note is relevant.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1098
The below described objects related to GPD are no longer available in SAP S4HANA.
Transactions not available in SAP S/4HANA
CANCDIS01 - Collective Processing Distribution
PEG12 - Filling of Pegging Worklist
PEG13 - Pegging: Unassigned Replenishments
PEG15 - Transfer Pegging Program
Business Add-Ins not available in
SAP S/4HANA
BADI_GPD_02 - Pegging: Distribution of Surplus
BADI_GPD_03 - Pegging: Distribution of Scrap
BADI_GPD_04 - Pegging: Distribution of Stock Differences
BADI_GPD_05 - Pegging: Customer-Specific Adjustment of
Assignments
BADI_GPD_06 - Pegging: Breakpoint Determination
BADI_GPD_07 - Distribution of Other Costs/Payments
BADI_GPD_09 - Distribution: BADI Before Database Update
of Distrib. Values
BADI_GPD_11 - Pegging: Fixing rule - Building real pegging
assignments
BADI_GPD_12 - Pegging: Distribution of Surplus
BADI_GPD_14 - Pegging: Distribution of scrap
BADI_GPD_15 - Pegging: Distribution of lost and found
BADI_GPD_17 - Pegging: Customer-Specific Adjustment of
Assignments
BADI_GPD_18 - Pegging: Read customer specific data into
pegging
BADI_GPD_19 - Pegging: Create the tables for pegging
each mat-grp segment
GDP_MM_EKKO_WRITE - MM_EKKO: Write GPD-specific
data
Required and Recommended Action(s)
Following enhancement spots can be used as an alternative to the above specified
BADI's.
Obsolete
BADI
Alternative Enhancement Spot
Alternative BADI Definition
BADI_GPD_02
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_SURPLUS
BADI_GPD_03
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_SCRAP
BADI_GPD_04
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_LOST
BADI_GPD_05
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_ADJ_BEFORE_COMPL
BADI_GPD_06
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_BREAKPOINT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1099
BADI_GPD_07
ES_BADI_GPD_DISTRIBUTION
BADI_GPD_DIS_ADJUST_COST_CASH
BADI_GPD_09
ES_BADI_GPD_DISTRIBUTION
BADI_GPD_DIS_BEFORE_DB_UPDATE
BADI_GPD_11
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_FIXING_RULE
BADI_GPD_12
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_SURPLUS
BADI_GPD_14
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_SCRAP
BADI_GPD_15
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_LOST
BADI_GPD_17
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_ADJ_BEFORE_COMPL
BADI_GPD_18
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_TECO_LOGIC
BADI_GPD_PEG_CUST_DATA
BADI_GPD_19
ES_BADI_GPD_PEGGING
BADI_GPD_PEG_MAT_GRP_SEGM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1100
48.Industry DIMP – Automotive
48.1 S4TWL - Vehicle search using SAP TREX as external search engine
Application Components:IS-A-VMS-SR, IS-A, IS-A-VMS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2456102
S4TWL - Vehicle search using SAP
TREX or Live Cache technology
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECC-
DIMP) includes an integration of SAP TREX as an external search engine or Live Cache
technology for the search of vehicles by various criteria including vehicle configuration
as part of the Vehicle Management System (VMS) in order to meet performance needs.
SAP S/4HANA provides an embedded search based on SAP HANA to meet performance
requirements also in high volume scenarios which makes the replication of vehicle data
to external search engines like SAP TREX obsolete.
The integration to SAP TREX as external search engine is not available with SAP
S/4HANA.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1101
The vehicle search in VMS using either SAP TREX as external search engine or Live
Cache technology is not supported with SAP S/4HANA.
The embedded search for vehicle based on SAP HANA allows a complete, fast and
extendable search also for large number of vehicles right away without data replication to
an external search engine.
How to Determine Relevancy
The Simplification Item is relevant, if:
a Search Engine Service had been maintained for Business Object VMSVEHICLE
(table COM_SE_BUSOBJ)
a LiveCache connection had been maintained (table VLC_DBCONSTATUS)
Required and Recommended Action(s)
Delete scheduled background jobs for program COM_SE_DISPATCHER for business
object VMSVEHICLE to avoid unnecessary look up for object changes to be pushed to
SAP TREX.
Delete all entries from table COM_SE_CPOINTER corresponding to object type
VMSVEHICLE containing the delta changes to be pushed to SAP TREX.
Other Terms
Automotive, ECC-DIMP, S4HANA, VMS, TREX, LC
48.2 S4TWL - Handling Unit Management - Obsolete Transactions
Application Components:IS-A-HUM, LO-HU
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2633572
S4TWL - Handling Unit Management -
Obsolete Transactions
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1102
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP to SAP S/4HANA.
Prerequisite: Business Function Set DIMP for Discrete Industries and Mill Products or
Business Function Set DIMP_PS for Discrete Industries / Mill Products and Public
Services not active in SAP ERP
Solution
Description
1. The usage of transaction COWBPACK is no longer allowed; error message VHUAP
037 is raised indicating that this transaction is obsolete and transactions COP1 or COP2
should be used instead.
2. The usage of transaction HUP1 is no longer allowed; error message VHUAP 039 is
raised indicating that this transaction is obsolete and transactions MFP1 or MFP2 should
be used instead.
Both transactions COWBPACK and HUP1 have been set to obsolete already from SAP
R/3 4.6B and therefore also in SAP ERP by the industry solution for automotive as part
of industry solutions for Discrete Industries and Mill Products (see also SAP Note
362626). Only customers who did not install or activate these industry solutions could
still use these transactions in SAP ERP. As the industry solutions for Discrete Industries
and Mill Products are always active in SAP S/4HANA, these replacements now affect
also customers who are doing a system conversion from SAP ERP without these industry
solutions activated before.
Business Process related information
1. Create handling units in production with shop-floor manufacturing
With transaction COWBPACK, you could create handling units based on a production
order from shop-floor manufacturing. For packaging specification determination,
additional sales and distribution related data could be specified.
With the following transactions, you have additional features to create handling
units based on production orders with respect to their usage for sales and shipping, and/or
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1103
with respect whether the handling units should be created as planned or directly as
physical existent:
With transaction COP21, handling units could be created without reference to
any sales and distribution document. That is similar to the usage of
transaction COWBPACK, if you do not specify any additional sales and
distribution related information for packaging instruction determination.
With transaction COP22, handling units could be created for assignment to a
sales order or sales scheduling agreement. Sales and distribution related
information from the specified sales document are used for packaging
instruction determination. The handling units created with reference to the
sales document are associated to that document for delivery processing.
Transaction VL10HU lists the associated handing units to the sales
document due for delivery creation, and assigns them when processing the
delivery creation.
With transaction COP23, handling units could be created for assignment to an
open outbound delivery. Sales and distribution related information from
the specified delivery document are used for packaging instruction
determination. The handling units created are linked to that delivery
document.
With transaction COP24, handling units could be created for assignment to a
stock transfer order or stock transfer scheduling agreement. Stock transfer
/ distribution related information from the specified document are used for
packaging instruction determination. The handling units created with
reference to that stock transfer document are associated to that document
for delivery processing. Transaction VL10HU lists the associated handing
units to that stock transfer document due for delivery creation, and assigns
them when processing the delivery creation.
With transaction COP2, there is a general transaction combining the features
from transactions COP21, COP22, COP23 and COP24
With transaction COPP2, handling units for due sales orders, stock transfer
order or open deliveries could be created
For creating planned handling units instead of phyiscally existent ones, the
corresponding transactions COP1, COP11, COP12, COP13, COP14 and
COPP1 are available
For more details, refer to the product assistance of SAP
S/4HANA: https://help.sap.com/viewer/15f6005df5a343d096f63b554e47e14a/6.18.10/en
-US/a3e8c353b677b44ce10000000a174cb4.html
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1104
Create handling units in production with repetitive manufacturing
With transaction HUP1, you could create handling units based on a planned order from
repetitive manufacturing. Transaction MFP21 is a direct replacement of that transaction.
With additional transactions, you have the choice for additional features to create
handling units based on repetitive manufacturing orders with respect to their usage for
sales and shipping, and/or with respect whether the handling units should be created
as planned or directly as physical existent:
With transaction MFP21, handling units could be created without reference to
any sales and distribution document. That is similar to the usage of
transaction COWBPACK, if you do not specify any additional sales and
distribution related information for packaging instruction determination.
With transaction MFP22, handling units could be created for assignment to a
sales order or sales scheduling agreement. Sales and distribution related
information from the specified sales document are used for packaging
instruction determination. The handling units created with reference to the
sales document are associated to that document for delivery processing.
Transaction VL10HU lists the associated handing units to the sales
document due for delivery creation, and assigns them when processing the
delivery creation.
With transaction MFP23, handling units could be created for assignment to an
open outbound delivery. Sales and distribution related information from
the specified delivery document are used for packaging instruction
determination. The handling units created are linked to that delivery
document.
With transaction MFP24, handling units could be created for assignment to a
stock transfer order or stock transfer scheduling agreement. Stock transfer
/ distribution related information from the specified document are used for
packaging instruction determination. The handling units created with
reference to that stock transfer document are associated to that document
for delivery processing. Transaction VL10HU lists the associated handing
units to that stock transfer document due for delivery creation, and assigns
them when processing the delivery creation.
With transaction MFP2, there is a general transaction combining the features
from transactions MFP21, MFP22, MFP23 and MFP24
With transaction MFPP2, handling units for due sales orders, stock transfer
order or open deliveries could be create
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1105
For creating planned handling units instead of phyiscally existent ones, the
corresponding transactions MFP1, MFP11, MFP12, MFP13, MFP14 and
MFPP1 are available
For more details, refer to the product assistance of SAP
S/4HANA: https://help.sap.com/viewer/15f6005df5a343d096f63b554e47e14a/6.18.10/en
-US/cae8c353b677b44ce10000000a174cb4.html
How to Determine Relevancy
The Simplification Item is relevant, if:
The Business Function DIMP_SDUD is not active (check with transaction SFW2 or
SFW_BROWSER), and
Transaction COWBPACK or HUP1 have been used so far for creating handling units
Required and recommended action(s)
Change the business process as follows:
Switch to the transactions recommended as replacement for the obsolete transactions.
Use transaction COP21 (or any other COP* transaction mentioned above) instead of
transaction COWBPACK and/or use transaction MFP21 (or any other MFP* transaction
mentioned above) instead of transaction HUP1.
No further configuration for automatic packing is needed if you just use transaction
COP21 (or COP22, COP23, COP24, COPP2) instead of transaction COWBPACK, as
both use packing transaction profile 0010.
No further configuration for automatic packing is needed if you just use transaction
MFP21 (or MFP22, MFP23, MFP24, MFPP2) instead of transaction HUP1, as both use
packing transaction profile 0008.
Only in case you would like to create planned handling units instead with transactions
COP1, COP11, COP12, COP13, COP14 and COPP1, you should check packing
transaction profile 0015 and adapt it, if needed.
Only in case you would like to create planned handling units instead with transactions
MFP1, MFP11, MFP12, MFP13, MFP14 and MFPP1, you should check packing
transaction profile 0014 and adapt it, if needed.
IMG: Logistics - General > Handling Unit Management > Automatic Packing > Maintain
Packing Transaction Profile
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1106
Other Terms
COWBPACK, HUP1, Automatic packing, Automotive, ECC-DIMP, S/4HANA
48.3 S4TWL - JIT Inbound
Application Components:IS-A-JIT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3159740
S4TWL - JIT Inbound
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP to SAP S/4HANA or upgrade to a higher SAP
S/4HANA release.
Prerequisite: Business Function Set DIMP for Discrete Industries and Mill Products or
Business Function Set DIMP_PS for Discrete Industries / Mill Products and Public
Services are active in SAP ERP.
Solution
Description
The functionality of JIT Inbound as part of the automotive industry solution is not the
target solution in SAP S/4HANA and therefore deprecated. Even if it is not yet defined
when JIT Inbound will become obsolete and be replaced, which means it’s still in
maintenance until communicated otherwise, it will receive no new features and
innovations. SAP recommends implementing JIT Supply to Customer as the strategic
next-generation solution.
Business Process related information
JIT Supply to Customer supports the following key features of JIT Inbound:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1107
Receive EDI messages to create and update summarized JIT calls and sequenced JIT
calls
Usage of sales scheduling agreements for JIT processing
Outbound delivery creation based on customer JIT calls
Action framework, defining
allowed actions per internal processing status
change of internal processing status by action execution
action to be executed based on a change of the external status
interlinked actions, combining multiple actions to be processed together
subsequently.
Monitoring of customer JIT calls
Demand analysis to compare forecast delivery schedules with customer JIT calls
Stock availability analysis
JIT delivery schedule creation based on customer JIT calls for improved material
requirements planning
Production release and confirmation with goods movement control, with backflush
execution in repetitive manufacturing and stock transfer between storage locations
Process customer JIT calls by scan/data entry
Processing reorder JIT calls
Extensibility options for
Processing JIT calls through EDI message
definition of custom-specific actions
extending SAP standard actions in pre-processing and post-processing
Component group determination
JIT Supply to Customer differs from JIT Inbound in the following key features:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1108
No JIT master data buffers to be refreshed
Monitoring of EDI messages through Application Integration Framework (AIF)
Creating and processing of JIT packing groups as own business object
Processing of JIT delivery confirmations from customers for consumption-based
billing or self-billing, using consignment fill-up and issue postings
Emergency correction of customer JIT calls not yet supported with JIT Supply to
Customer
Forwarding sequenced JIT calls to external suppliers not yet supported with JIT
Supply to Customer
Processing internal calls to sequenced JIT calls not supported with JIT Supply to
Customer
In addition, JIT Supply to Customer could be used side-by-side with JIT Inbound for
migration purposes, using a conditional switch.
For more details on JIT Supply to Customer, refer to the product assistance of SAP
S/4HANA: Link
How to Determine Relevancy
The Simplification Item is relevant, if:
The Business Function DIMP_SDUD is active (check with transaction SFW2 or
SFW_BROWSER), and
Inbound JIT calls exist (check database table JITHD for entries)
Required and recommended action(s)
When the check item is relevant, there are two alternative options to proceed with the
conversion to SAP S/4HANA:
Evaluate and implement the next-generation Just-in-Time (JIT) Supply to Customer
solution in SAP S/4HANA instead of continuing with JIT Inbound.
The implementation of the new solution could be done stepwise using the
conditional switch mentioned above, e.g. by plant and customer
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1109
Apply for an exemption for this check item and continue with the current JIT Inbound
implementation and consider a migration to the JIT Supply to Customer solution at a later
point in time
Other Terms
Just-in-Time, Just-in-Sequence, JIT, JIS, Automotive, ECC-DIMP, S/4HANA
48.4 S4TWL - JIT Outbound
Application Components:IS-A-JIT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3155820
S4TWL - JIT Outbound
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP to SAP S/4HANA or upgrade to a higher SAP
S/4HANA release.
Prerequisite: Business Function Set DIMP for Discrete Industries and Mill Products or
Business Function Set DIMP_PS for Discrete Industries / Mill Products and Public
Services are active in SAP ERP.
Solution
Description
The functionality of JIT Outbound as part of the automotive industry solution is not the
target solution in SAP S/4HANA and therefore deprecated. Even if it is not yet defined
when JIT Outbound will become obsolete and be replaced, which means it’s still in
maintenance until communicated otherwise, it will receive no new features and
innovations. SAP recommends implementing JIT Supply to Production as the strategic
next-generation solution.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1110
JIT Supply to Production supports the following key features of JIT Outbound:
Internal replenishment to a production supply area from a source storage location
using summarized JIT calls
Replenishment to a production supply area from an external supplier using
summarized JIT calls
Manage control cycles for JIT supply to production
Create JIT calls as replenishment requests manually
Plan replenishment to production supply areas based on demands from production
Send JIT calls through EDI messages to external suppliers and other communication
partners
Action framework, defining
allowed actions per internal processing status
change of internal processing status by action execution
interlinked actions, combining multiple actions to be processed together
subsequently
Monitor JIT calls
JIT Supply to Production differs from JIT Outbound in the following key features:
Internal replenishment to a production supply area from a warehouse managed source
storage location is supported with Extended Warehouse Management as the
strategic warehouse management solution in SAP S/4HANA. An integration to
the classic Warehouse Management, as supported by JIT Outbound, is not
available and not planned in future
Goods receipt processing in external replenishment to a production supply area using
summarized JIT calls is supported using Inbound Cargo Registration (ICR) as part
of SAP S/4HANA for Manufacturing Logistics.
Processing forwarded sequenced JIT calls are not yet supported with JIT Supply to
Production
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1111
Replenishment of supermarkets close to production lines through demand-driven
replenishment planning is supported with JIT Supply to Production, but not with
JIT Outbound
For more details on JIT Supply to Production, refer to the product assistance of SAP
S/4HANA: Link
For more details on Inbound Cargo Registration, refer to the product assistance of SAP
S/4HANA for Manufacturing Logistics: Link
How to Determine Relevancy
The Simplification Item is relevant, if:
The Business Function DIMP_SDUD is active (check with transaction SFW2 or
SFW_BROWSER), and
Outbound JIT calls exist (check database table JITOHD for entries)
Required and recommended action(s)
When the check item is relevant, there are two alternative options to proceed with the
conversion to SAP S/4HANA:
Evaluate and implement the next-generation Just-in-Time (JIT) Supply to Production
solution in SAP S/4HANA instead of continuing with JIT Outbound
Apply for an exemption for this check item and continue with the current JIT Outbound
implementation and consider a migration to the JIT Supply to Production solution at a later
point in time
Other Terms
Just-in-Time, Just-in-Sequence, Supply to Production Planning, JIT, JIS, S2L,
Automotive, ECC-DIMP, S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1112
48.5 S4TWL - Self-Billing Cockpit
Application Components:SD-BIL-IV-SBI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3168667
S4TWL - Self Billing
Symptom
You plan to use self-billing with your buyer. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
Reason and Prerequisites
Self-Billing (SD-SBI-INV) is not strategic, and customers should evaluate the new
industry cloud solution SAP Self-Billing Cockpit
Self-Billing (SD-SBI-INV) is a deprecated component. This means that it is still
supported but will be replaced by the SAP Self-Billing Cockpit in the long term. The date
is not set yet.
Solution
SAP Self-Billing Cockpit (SD-BIL-SBI) is an industry cloud solution helping suppliers to
efficiently process self-billing documents transmitted from the buyer and prepares the
documents for the clearing process in accounts receivable.
It enhances efficiency through automated simulation result and combined with SAP Fiori
and monitoring capabilities help end users take faster decisions.
SAP Self-Billing Cockpit also supports both Self Billing with Automatic posting (so
called “SBWAP” processing) and Self-billing with Invoice creation (so called “SBINV”
processing)
Being an Industry cloud solution SAP Self-Billing Cockpit is aligned with SAP’s strategy
and has continuous investment with a well-defined roadmap
SAP Self Billing Cockpit integrates with S/4 HANA back-end systems S/4HANA Cloud
and S/4HANA OP. For prerequisites, please refer to chapter “Relevancy”.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1113
Business Process related information
Self-Billing with Automatic Posting (“SBWAP”)
You can only use self-billing with automatic posting for scenarios in which exactly one
invoice is created for each outbound delivery. To be specific, no convergence or split of
billing data from deliveries can occur during invoice creation.
The following processing flows exist in self-billing with automatic posting:
Standard processing involving value and quantity
This is the standard type of processing, where the supplier creates billing documents for
outbound deliveries. After receiving self-billing documents from the buyer, the system determines the
corresponding reference delivery document, and compares the received self-billing documents with
the corresponding reference billing documents.
Value-based clearing invoice without retroactive billing
This type of processing assumes that the transmission explicitly states that it is a clearing invoice, by
referring to a transaction that has already been settled. In addition, such transmissions deal exclusively
with value changes (for example, retroactive price changes) claimed by the customer (that is, the
buyer). Therefore, the received quantity is not considered during value comparison or further
processing.
Value-based clearing invoice with retroactive billing
This type of processing also deals exclusively with value changes (for example, retroactive price
changes) claimed by the customer (that is, the buyer), by referring to a transaction that has already
been processed and settled.
2. Self-Billing with Invoice creation (“SBINV”)
In some countries or regions, legal requirements dictate that the billing documents that
the supplier creates as part of a self-billing process must be identical with the self-billing
documents that SAP Self-Billing Cockpit receives in transmissions from the buyer. In
this scenario, known as self-billing with invoice creation, the supplier can create the final
billing documents only after they have received self-billing documents from the buyer. In
self-billing with invoice creation, the buyer can send several self-billing documents for
one delivery item. SAP Self-Billing Cockpit continues to create billing documents as the
buyer sends them, until the delivery quantity is fully billed.
The following processing flows exist for self-billing with invoice creation:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1114
Initial invoice creation
This type of processing deals with initial invoice creation. After receiving self-billing
documents from the buyer, the system determines the corresponding delivery document
for reference, and compares the received data with the reference data.
Based on the comparison results, the system proceeds in one of the following ways:
It executes self-billing to trigger the creation of invoices (billing type CIXS)
for billing items where there is no difference.
It executes self-billing to create a clearing line, in addition to an invoice, for
billing items where the transmitted net value differs from the reference net
value.
It executes self-billing to create a clearing line and an open line, in addition to
an invoice, if the difference exceeds the predefined tolerance limits.
Credit or debit memos for quantity corrections
This type of processing deals with quantity corrections (such as damaged goods during
the transport) claimed by the buyer, by referring to a transaction that has already been
processed and settled. Therefore, the buyer sends a credit or debit memo for quantity
corrections with reference to one or more existing invoices.
During the process, the system compares the claimed net value change against the
internal net value change, both of which are calculated based on input such as quantity
changes of the settled transaction.
If they match, the system executes self-billing to trigger the creation of a
credit memo (billing type CIXG) or debit memo (billing type CIXL)
exactly as the buyer has prepared it.
If they don't match, the system creates a credit or debit memo and a clearing
line, as well as an open line if the difference exceeds the predefined
tolerance limit.
Credit or debit memos for retroactive price changes
This type of processing is like the previous one except that it deals with retroactive price
changes. Therefore, the system compares the claimed net value change against the
internal retroactive billing value, which is calculated in your system based on input such
as price changes of the settled transaction.
For more details, refer to the product assistance of SAP Self-Billing Cockpit – Link
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1115
Relevancy
The Simplification is relevant for
Self-Billing with Automated posting (SBWAP) – If the table TRNSM has content.
Self-billing with Invoice creation (SBINV) - If content exist when the field MESTYP
is filtered with value SBINV and GSVERF in the table EDIDC
SAP Self-Billing Cockpit is compatible along with below mentioned S/4HANA OP
releases
Scenario
Valid from S/4HANA OP release
SBWAP
OP2020_FPS1
SBWAP retro-billing feature
OP2020_FPS2
SBINV
OP2020_FPS2
* For integration with SAP ERP EHP8 a service offering will be made available soon.
SAP Self-Billing Cockpit Solution Benefits and Business capabilities
Solution Benefits
Gain full visibility with one central overview page
Catch issues easily with an intuitive UI
Enhance efficiency through automated result simulation
Reduce errors through automated processing
Gain early insights through error analysis
Mass change capabilities help you save time
Capabilities
Intuitive User Interface
Two transactions (SBWAP + SBINV) are combined in one central overview page,
multiple legal requirements in one solution are supported
Automatic result simulation capability
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1116
Mass change capabilities in case of errors in self-billing documents
Option to take notes on status or required action
Archiving of transmission
Manual change of Tax code in SBINV
Required and Recommended Action(s)
New functionality and enhancements are planned for Industry cloud application SAP
Self-Billing Cockpit according to the SAP roadmap. Self-Billing (SD-SBI-INV)
in SAP S/4HANA will be in maintenance (until a date yet to be decided).
SAP Self-Billing Cockpit features included in the previous and planned for any
future release can be found in the Roadmap Explorer.
It is recommended that new SAP customer implementations start with Industry cloud
application SAP Self-billing Cockpit.
More information on SAP Self-Billing Cockpit
Feature Scope Description of SAP Self-Billing Cockpit
SAP Self-Billing Cockpit in SAP Store
Quick-Start Service for SAP Self-Billing Cockpit
Other Terms
Self Billing, Self-Billing, Automotive, ECC-DIMP, S/4HANA, Self Billing Cockpit
48.6 S4TWL - Sales Scheduling Agreement with TAM processing
Application Components:SD-SLS-OA-SCH
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3192264
S4TWL-Sales Scheduling agreement
with Delivery orders (TAM)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1117
Symptom
You plan to use Sales Scheduling agreement with Delivery orders (TAM). The following
business impact note is relevant for you.
Reason and Prerequisites
Sales Scheduling agreement with Delivery orders (TAM) is not strategic, and customers
should evaluate the next-generation Just-in-Time (JIT) Supply to Customer solution in
SAP S/4HANA
Sales Scheduling agreement with Delivery orders (TAM) is a deprecated component.
This means that it is still supported but will be replaced by the next-generation Just-in-
Time (JIT) Supply to Customer solution in SAP S/4HANA in the long term. The date is
not set yet.
Solution
Scheduling Agreement with delivery orders (TAM) is a special type of Scheduling
agreement. The process flow is Sales Scheduling agreement ->Sales order (TAM -
Delivery order) -> Delivery ->Invoice.
This process came into existence when Just in Time (JIT) solution was not available.
Since next-generation Just-in-Time (JIT) Supply to Customer solution is now part of the
standard solution, it is recommended to use that solution with summarized JIT calls
instead of TAM.
Business Process related information
“JIT Supply to Customer” is the S/4HANA successor of the SAP ERP “JIT Inbound”
solution. For customers using JIT processes it is recommended to use “JIT Supply to
Customer”from S/4HANA 2021 onwards as “JIT Inbound” will also be deprecated. For
details please refer to note - https://launchpad.support.sap.com/#/notes/3159740
JIT Supply to Customer supports the following key features:
Receive EDI messages to create and update customer JIT calls
Usage of sales scheduling agreements for JIT processing
Outbound delivery creation based on customer JIT calls
Monitoring of customer JIT calls
Stock availability analysis
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1118
Demand analysis to compare forecast delivery schedules with customer JIT calls
JIT delivery schedule creation based on customer JIT calls for improved material
requirements planning
Action framework, defining
allowed actions per internal processing status
change of internal processing status by action execution
action to be executed based on a change of the external status
interlinked actions, combining multiple actions to be processed together
subsequently.
Extensibility options for processing JIT calls through EDI message
Definition of custom-specific actions
Extending SAP standard actions in pre-processing and post-processing
For more details on JIT Supply to Customer, refer to the product assistance of SAP
S/4HANA: Link
Relevancy
The Simplification Item is relevant, if:
There is any entry for the field AUART in the table VBAK with the value TAM
Required and Recommended Action(s)
When the check item is relevant, evaluate and implement the next-generation Just-in-
Time (JIT) Supply to Customer solution in SAP S/4HANA instead of continuing
with Sales Scheduling agreement with Delivery orders (TAM)
Other Terms
Sales Scheduling Agreement with Delivery orders, TAM processing, TAM, Just-in-Time,
JIT, Automotive, ECC-DIMP, S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1119
48.7 S4TWL - Returnable Packaging Logistics
Application Components:IS-A-RL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3213566
S4TWL - Returnable Packaging
Logistics
Symptom
You plan to manage returnable packages with either your vendors or your customers. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Returnable Packaging Logistics (IS-A-RL) is not the target solution in SAP S/4HANA
and therefore deprecated. Even if it’s not yet defined when Returnable Packaging
Logistics will become obsolete and be replaced, which means it’s still in maintenance
until communicated otherwise, but will receive no new features and innovations. SAP
recommends implementing the new industry cloud solution SAP Returnable Packaging
Management as the strategic next-generation solution.
Solution
SAP Returnable Packaging Management (LO-RL) is an industry cloud solution helping
companies to manage the logistics of reusable returnable packaging materials in a supply
chain. Reusable packaging materials such as containers, pallets, tanks, and load carriers
are used to move products safely and efficiently between business partners. With this
product, a packaging manager can determine and plan the exact quantity and location of
these reusable materials in the supply chain, thereby minimizing loss, waste, and rental-
cost of these packaging materials.
Being an Industry cloud solution SAP Returnable Packaging Management is aligned with
SAP’s strategy and has continuous investment with a well-defined roadmap
SAP Returnable Packaging Management integrates with S/4 HANA back-end systems,
S/4HANA Cloud and S/4HANA OP. For prerequisites, please refer to chapter
“Relevancy”.
Business Process related information
1. Packaging Logistics
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1120
When packaged goods are shipped to a customer or vendor the decrease of the package is
automatically captured in a packaging account. When the packages are returned, the
increase is posted to the same packaging account. The status of serial-numbered packages
can be defined, changed, and tracked individually. Stock in plant is displayed based on
storage-location and stock-type. Statements for packaging-accounts showing the
movements for a certain time-period can either be created or received and matched.
2. Packaging Planning and Collaboration
Packaging demand can be forecasted based analysis of the historical consumption pattern.
Account-levels below reorder-point can be replenished automatically via the creation of a
purchase-order in S/4HANA.
3. Returnable Packaging Rentals
The amount for the rental of packages can be calculated for serialized packages and bulk
packages.
For more details, refer to the product assistance of SAP Returnable Packaging
Management – Link
Relevancy
The Simplification is relevant if table RLACPOHD (Accounting Posting Header) has any
content.
Required and Recommended Action(s)
New functionality and enhancements are planned for Industry cloud application SAP
Returnable Packaging Management to the SAP roadmap. Returnable Packaging
Logistics (IS-A-RL) in SAP S/4HANA will be in maintenance until
communicated otherwise.
SAP Returnable Packaging Management features included in the previous
and planned for any future release can be found in the Roadmap Explorer.
It is recommended that new SAP customer implementations start with Industry cloud
application SAP Returnable Packaging Management.
More information on SAP Returnable Packaging Management
Feature Scope Description of SAP Returnable Packaging Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1121
SAP Returnable Packaging Management in SAP Store
Other Terms
Automotive, ECC-DIMP, S/4HANA, Returnable Logistics, RPM, Returnable Packaging
Management
48.8 S4TWL - Tracking Inbound
Application Components:IS-A-TRI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270352
S4TWL - Tracking Inbound
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1122
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
Other Terms
Automotive, ECC-DIMP, S/4HANA, Tracking
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1123
48.9 S4TWL - Supplier Workplace
Application Components:IS-A-SWP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270354
S4TWL - Supplier Workplace
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1124
Not all scenarios covered by SWP are supported by the successor products.
Transactions not
available in SAP
S/4HANA
ISAUTO_SICASN1, ISAUTO_SICASN2, ISAUTO_SICASN3,
ISAUTO_SICASN4, ISAUTO_SICBC, ISAUTO_SICCO,
ISAUTO_SICDDL1,
ISAUTO_SICENG, ISAUTO_SICIV, ISAUTO_SICJIT,
ISAUTO_SICPDI, ISAUTO_SICPH, ISAUTO_SICPI, ISAUTO_SICRL,
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
SAP Note 2326822
Custom Code Check
SAP Note 2228218
Other Terms
Automotive, ECC-DIMP, S/4HANA, Supplier Workplace, SWP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1125
48.10S4TWL - External Service Providers
Application Components:IS-A-ESP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270357
S4TWL - External Service Providers
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1126
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
Other Terms
Automotive, ECC-DIMP, S4HANA, ESP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1127
48.11S4TWL - Cross-System Transit between Two Plants
Application Components:IS-A-XLO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270358
S4TWL - Cross-System Transit between
Two Plants
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1128
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 cross-system stock in transit or
remove all related schedule lines before the conversion to SAP S/4HANA.
Related SAP Notes
Pre Check
SAP Note 2349033
Custom Code Check
SAP Note 2228220
Other Terms
Automotive, ECC-DIMP, S/4HANA, XLO, stock in transit
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1129
48.12S4TWL - Long Material Number
Application Components:IS-A-LMN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270396
S4TWL - Long Material Number
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case, if you are using the automotive
industry solution for the long material number in SAP ERP for Discrete Industries & Mill
Products.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Prerequisite: Target release is SAP S/4HANA 1610 or subsequent.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1130
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.
If you are using SAP Master Data Governance (MDG), execute report
MDG_HDB_MAT_MIGRATE_LONGTEXT right after migration.
If you are using SAF-T (Standard Audit File for Tax) reporting according to regulations
in Portugal and other European countries, refresh the extraction tables after conversion.
See SAP Note 2341690 for more information.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1131
Related SAP Notes
Restrictions
SAP Note 2384347
Pre-Check
SAP Note 2326776
Custom Code Check
SAP Note 2228241
Other Terms
Automotive, ECC-DIMP, S/4HANA, Long Material Number, LMN, LAMA
48.13S4TWL - Material Version
Application Components:IS-A-LMN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270398
S4TWL - Material Version
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Prerequisite: Target release is SAP S/4HANA 1610 or subsequent.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1132
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1133
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.
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
SAP Note 2326776
Custom Code Check
SAP Note 2228242
Other Terms
Automotive, ECC-DIMP, S/4HANA, Material version, LMN, LAMA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1134
48.14S4TWL - Planning Regular Route Shipments
Application Components:IS-A-TP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270399
S4TWL - Planning Regular Route
Shipments
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1135
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.
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
Other Terms
Automotive, ECC-DIMP, S/4HANA, Transportation, Regular Routes
48.15S4TWL - BSP based Dealer Portal
Application Components:IS-A-DP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273102
S4TWL - BSP based Dealer Portal
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1136
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1137
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)
In case the conversion to SAP S/4HANA starts from SAP ERP 6.04 (Enhancement
Package 4) or higher, the migration to the Web Dynpro based Dealer Portal could be
done before the system conversion.
Otherwise, the migration to the Web Dynpro based Dealer Portal needs to be done after
the system conversion to SAP S/4HANA.
The pre-check will raise an error as long as the settings for the BSP based Dealer Portal,
mentioned above to determine the relevancy, are available.
Apply for an exemption for that check item after, or remove these settings for the BSP
based Dealer Portal if the migration to the Web Dynpro based Dealer Portal could be
done before the system conversion.
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
Provide a training for dealer users regarding the Web Dynpro based Dealer Portal.
Enhancements to the BSP based Dealer Portal have to be reimplemented for the Web
Dynpro Dealer Portal, if applicable.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1138
Related SAP Notes
Custom Code Check
SAP Note 2228244
Other Terms
Automotive, ECC-DIMP, S4HANA, DP, DIWI
48.16S4TWL - Web Dynpro based Dealer Portal
Application Components:IS-A-DP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2352485
S4TWL - Web Dynpro based Dealer
Portal
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
Description
The Web Dynpro based Dealer Portal allows managing vehicle sales, spare parts
procurement, and warranty claim processing in collaboration with dealers.
That Dealer Portal solution is not strategic anymore with SAP S/4HANA from a target
architecture perspective.
Business Process related information
No alternative or successor solution is available so far, but the target architecture would
be based on SAP Hybris Commerce for B2B collaboration with Dealers in combination
with SAP Configure, Price and Quote (SAP CPQ), with integration to SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1139
Required and recommended action(s)
Evaluate SAP Hybris Commerce and SAP Configure, Price and Quote for your future
business with Dealers.
Other Terms
Automotive, ECC-DIMP, S/4HANA, DP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1140
49.Industry DIMP - EC&O
49.1 S4TWL - Obsolete BAPIS of Bill of Services (BOS)
Application Components:IS-ADEC-BOQ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2301522
S4TWL - Obsolete BAPIs of Bill of
Services (BOS)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA
Solution
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.
Other Terms
/SAPBOQ/SESBAPI, BOS07, EXIT_SAPLBOS20_10, PS_LDB_GETDETAIL,
/SAPBOQ/SES_CHANGEBOS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1141
49.2 S4TWL - BOS Cost Transfer to PS removed
Application Components:IS-ADEC-BOQ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273314
S4TWL - Enhancements IS-ADEC-BOQ
Billing of Quantity
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case.
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release.
You are using Bill of Services (BOS) functionality part of SAP ERP for Discrete
Industries & Mill Products (ECC-DIMP)
Solution
Description:
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.
Buisness Process related Information:
If you use easy cost planning for cost estimation of service lines or easy cost planning for
cost estimation of WBS elements functionalities of BOS, then following S/4HANA
simplification applies:
Bills of Services functionality transfer cost to the Project is not available
IMG activity configure batch processing profile for cost transfer to Project has been
removed.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1142
The transactions BOSPS01 - Online Processing, BOSPS02 - Batch Processing and
BOSPS_REV1 - BOS/Project Plan/Actual Revenue are not available
Required and Recommended Action(s)
Consider the note 2267182, Simplification related to Project system, Easy Cost Planning
(ECP)
Other Terms
BOS, Cost transfer, BOSPS01, BOSPS02, BOSPS_REV1
49.3 S4TWL - ZDEP ETM CATS package
Application Components:IS-ADEC-ETM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2350332
S4TWL - ZDEP ETM CATS Package
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
transition worklist item is applicable in this case
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release
ETM related SCAT test scripts are not available from SAP S/4HANA 1610 FPS1
Solution
Description:
Transaction SCAT is not available in SAP S/4HANA. Therefore ETM SCAT test cases
/SAPCEM/BAL90 and /SAPCEM/BGL91 are replaced with the reports
/SAPCEM/BAL90 and /SAPCEM/BGL91 respectively. The package
/SAPCEM/CATT is replaced with new package /SAPCEM/CATT_REPORT.
All the other objects in the package /SAPCEM/CATT, other than /SAPCEM/BAL90 and
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1143
/SAPCEM/BGL91 have no equivalent objects or reports available till SAP S/4HANA
1610 FPS1.
Buisness Process related Information.
Test scripts that were used by the workflow for the ETM solution to enable ETM
processes (such as to create an asset or create an ETM catalog with characteristics, create
equipment and change PM order) are now replaced with reports or function modules.
Example: In an ERP release, If you try to create an asset and save, a workflow would
trigger creation of an equipment, creation of PM order, update of equipment number to
asset, update of PM order to an asset, update of PM order in equipment were using SCAT
test scripts.
Required and Recommended Action(s)
From SAP S/4HANA 1610 FPS1, The workflow steps that were calling the SCAT test
scripts are replaced by the function modules. No actions are required if objects
from SCAT test cases or package /SAPCEM/CATT are not part of the custom code.
In case if there are any objects used as part custom code then plan to make necessary
changes with the information in the below table .
BOR Object
Test script name
in ERP release
Test script is replaced by the Function
Module in S/4HANA 1610 FPS1
Report Name
J_3GBU1022
/SAPCEM/AS01
BAPI_FIXEDASSET_CREATE
J_3GRAWFOB01
J_3GBU1022
/SAPCEM/AS02
BAPI_FIXEDASSET_CHANGE
J_3GRAWFOB01
J_3GBU1022
/SAPCEM/WFIE02
/SAPCEM/ETM_UPDATE_EQUIPMENT
J_3GRAWFOB01
J_3GEQUI
/SAPCEM/WFIE02
/SAPCEM/ETM_UPDATE_EQUIPMENT
J_3GRMEQI65
J_3GBU2007
/SAPCEM/IW32
/SAPCEM/ETM_UPDATE_PM_ORDER
J_3GRIARCH00
Other Terms
/SAPCEM/CATT, /SAPCEM/BAL90, /SAPCEM/BGL91, SCAT, ETM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1144
49.4 S4TWL - ETM General
Application Components:IS-ADEC-ETM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2326777
S4TWL - Equipment and Tools
Management (ETM)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA.
Solution
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.
ETM is part of the SAP S/4HANA compatibility scope, which comes with limited usage
rights. For more details on the compatibility scope and it’s expiry date and links to further
information please refer to SAP note 2269324. In the compatibility matrix attached to
SAP note 2269324, ETM can be found under the ID 119.”
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1145
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
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.
Other Terms
S/4HANA, Simplification List, DIMP, Engineering Constructions & Operations,
Recipient, Project site, customer
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1146
49.5 S4TWL - ETM Tables obsolete
Application Components:IS-ADEC-ETM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2301533
S4TWL - ETM (Equipment and Tools
Management) Tables Obsolete
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA
Solution
Description
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.
Other Terms
J_3GKALEND, KOTJ001, KOTJ002, KOTJ003, KOTJ0012
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1147
49.6 S4TWL - REAL ESTATE SALES (HOMEBUILDING)
Application Components:IS-ADEC-HBS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2197116
S4TWL - Real Estate Sales
(Homebuilding)
Symptom
The Home Building Solution (HBS) will not be available in SAP S/4HANA.
Reason and Prerequisites
HBS functionality is not available in SAP S/4HANA.
Solution
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.
Other Terms
HBS, DI_HBS, DI_HBS_APP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1148
49.7 S4TWL Business Package for Subcontracting (EC&O)
Application Components:EP-PCT-IEC-S
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2389447
S4TWL Business Package for
Subcontracting (EC&O)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case
Reason and Prerequisites
Reason: Conversion from SAP ERP for Discrete Industries & Mill Products (ECC-
DIMP) to SAP S/4HANA
Solution
Description
The Business Package for Subcontracting (E&C) was available for the general
contractors to monitor current , upcoming and overall activities. It provided
subcontractors access to the required Information. Using the business package
(EC_PORTAL), general contractors and subcontractors had the access to role-specific
iViews that display the relevant data from multiple SAP ERP sources, including purchase
orders, sales orders, and network activities.
Subcontracting portal is not available with SAP S/4HANA. There are successors with
SAP Ariba and Ariba Networks .
Business Process Related Information
Implementing the successor solution for subcontract portal will result in the IT system
landscape and integration as well as in business applications used for the subcontract
portal. Not all scenarios covered by subcontract portal are supported by the successor
products.
Required and Recommended Action(S)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1149
Package EC_PORTAL is no longer available in S/4HANA. You must remove the usage
of SAP objects from your custom code. as indicated by custom code check
Other Terms
Enterprise Portal, Business Package for Subcontracting (EC&O), EC_PORTAL,
S/4HANA, Simplification List, DIMP
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1150
50.Industry DIMP - High Tec
50.1 S4TWL - Manufacturing Execution Systems
Application Components:IS-HT-MES
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2383042
S4TWL - Manufacturer Execution
Systems
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1151
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
50.2 S4TWL - RosettaNet
Application Components:IS-HT-RN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2383076
S4TWL - RosettaNet
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
Business Add-Ins not available
in SAP S/4HANA
/SAPHT/RN_DUNS - RosettaNet Building Block: DUNS
implementation
/SAPHT/RN_GTIN1 - RosettaNet Building Block: GTIN
implementation
/SAPHT/RN_USER_DUNS - RosettaNet Building Block: DUNS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1152
implementation - User exit
/SAPHT/RN_USER_GTIN - RosettaNet Building Block: GTIN
implementation - User exit
50.3 S4TWL - Software License Management
Application Components:IS-HT-SW-LIC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270848
S4TWL - Software License
Management
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
VBSY – Billing Plan Synchronization
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1153
50.4 S4TWL - Installed Base Management for IS-SW
Application Components:IS-HT-SW-IB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270849
S4TWL - Installed Base Management
for IS-SW
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
For IS-SW, 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1154
50.5 S4TWL - Contract Management Enhancements
Application Components:IS-HT-SW-CM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270850
S4TWL - Contract Management
Enhancements
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1155
50.6 S4TWL - Billing Process Enhancements
Application Components:IS-HT-SW-BIL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270851
S4TWL - Billing Process Enhancements
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
How to Determine Relevancy
This note is only relevant if transaction 'VBSY' or program 'ROGBILLS' is being used in
your system.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1156
50.7 S4TWL - Software Maintenance Processing
Application Components:IS-HT-SW-SMP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270852
S4TWL - Software Maintenance
Processing
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 distribute
a new software product or version change to licensed customers (providing a new
license).
IS-SW and Software Maintenance Processing functionality 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1157
50.8 S4TWL - User Exits in DRM
Application Components:IS-HT-DRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270853
S4TWL - User Exits in DRM
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
50.9 S4TWL - Condition Technique in DRM: Rule Configuration
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1158
Application Components:IS-HT-DRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270855
S4TWL - Condition Technique in DRM:
Rule Configuration
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1159
50.10S4TWL - Manufacturer/Supplier Processes
Application Components:IS-HT-DRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270856
S4TWL - Manufacturer/Supplier
Processes
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1160
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)
DRMPPMS – Price Protection (Background Processing)
DRMCLMS – Ship-and-Debit
DRMBUMS – Bill-up
DRMIRMS – Inventory Reconciliation
DRMLMMS – Manual Lot Maintenance
DRMR3MS – SAP Transactions
DRMSTGMS – DRM Staging Area
DRMXMRPT – Transmission Report
DRMCDMS – Discrepancy in Ship-and-Debit Claims
DRMMSBUSMET – Business Metrics
DRMPCMS – Price Protection Correction Report
DRMPEMS – Partner Validation Report
50.11S4TWL - Distributor/Reseller Processes
Application Components:IS-HT-DRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270858
S4TWL - Distributor/Reseller Processes
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1161
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 in
SAP S/4HANA
/SAPHT/DRMPPDR_C - Price Protection (Create Due List)
/SAPHT/DRMPPDR_P - Price Protection (Change/Process Due
List)
/SAPHT/DRMPPDR_D - Price Protection (Display Due List)
/SAPHT/DRMPPDR– Price Protection (Background Processing)
/SAPHT/DRMCLDR – Ship-and-Debit
/SAPHT/DRMBUDR – Bill-up
/SAPHT/DRMR3DR – Transactions Tracking & Processing
/SAPHT/DRMSTGDR – Processing of Staging Items
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1162
/SAPHT/DRMLMDR – Manual Lot Maintenance
/SAPHT/DRMIADR – Invalid Ship and Debit Agreements report
/SAPHT/DRMDRBUSMET – Business Metrics report
/SAPHT/DRMIMRCN – Inventory Management Reconciliation
report
/SAPHT/DRMSLSRPOUT – DRM Sales report
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1163
51.Industry DIMP – Mill
51.1 S4TWL - Non ferrous metal processing
Application Components:IS-MP-NF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270403
S4TWL - Non Ferrous Metal Processing
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note.
Solution
Description
Non Ferrous Metals is part of the SAP S/4HANA compatibility scope, which comes with
limited usage rights. For more details on the compatibility scope and it’s expiry date and
links to further information please refer to SAP note 2269324. In the compatibility matrix
attached to SAP note 2269324, Non Ferrous Metals can be found under the ID 401 (see
file S4HANA-CompatibilityScopeMatrix-DETAILS.pdf)
With SAP S/4HANA 2023 it is planned to introduce a CDS view. With this change we
plan to move Non Ferrous Metals from status "compatibility scope" to "perpetual scope"
of SAP S/4HANA.
Business Process related information
The functional scope of Non Ferrous Metal in SAP S/4HANA remains unchanged.
Required and Recommended Actions
Before using NFM in S/4HANA the following activities are required:
NFM field “Exchange key” in transaction „Business Partner“:
Since SAP S/4HANA, on-premise edition 1511, Customer and Vendor master
transactions are combined into new Business Partner transaction "BP". The Non
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1164
Ferrous Metals (NFM) field “Exchange key” is not shown in transaction "BP" by
default. In DDIC tables LFM1 [Vendor master record purchasing organization
data] and KNVV [Customer Master Sales Data], the “NFM Exchange Key“ field
/NFM/BOESL is still available. Re-activation by project development is possible.
You can add field “Exchange key” into Transaction “BP” by BadI development.
SAP note 2815395 - Enhancement of transaction BP with Non Ferrous Metals
(NFM) "exchange key" field
Metal price quotations:
If you import metal price quotations from stock exchanges by data feed with
transaction TBD4 please read SAP note 2918965 - NFM (Non Ferrous Metal)
Datafeed via TBD4 in S4/HANA
NFM fields in Material master:
In case the NFM fields in material master are not displayed, please read SAP note
2357870 - SAP S/4HANA: Settings to enable Non Ferrous Metals data in material
master
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Mill Products, Non
Ferrous Metals
51.2 S4TWL - Sales Order Versions
Application Components:IS-MP-SD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270405
S4TWL - Sales Order Versions
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The special Mill Sales Order Versions function is not available in S/4HANA. For more
information, see SAP Note 2226678
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1165
Business Process related information
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
51.3 S4TWL - Stock Overview and Object Search by Characteristics
Application Components:IS-MP-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270409
S4TWL - Stock Overview and Object
Search by Characteristics
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
This function displays stocks and objects (such as orders) with particular characteristics.
The following Customizing activity is not available in S/4HANA:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1166
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 Customizing activity is available in S/4HANA:
Path: Production --> Shop Floor Control --> Master Data à Order à Define Profiles for
Selection by Characteristics
Transaction: MILL_MSP
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
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1167
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
51.4 S4TWL - Mill specific enhancements to scheduling PRTs
Application Components:IS-MP-PP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270410
S4TWL - Mill specific enhancements to
scheduling PRTs
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 customizing activity is not available in S/4HANA: 'Permit Assignment of PRTs to
Work Centers', which was under IMG Path: Production ->Shop Floor Control ->Master
Data ->Production Resources/Tools.
The folllowing transactions are not available in S/4HANA:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1168
/SAPMP/TOOL_POOL_CHK - Compare PRT Pool, which was under SAP Easy
Access Menu: Logistics ->Production ->Master Data ->Production Resources
and Tools.
/SAPMP/TOOL_REPLACE -Replace PRT in Order, which was under SAP Easy
Access Menu: Logistics ->Production ->Shop Floor Control ->Order
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
51.5 S4TWL - Process batch
Application Components:IS-MP-PP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270412
S4TWL - Process Batch
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case..
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1169
Description
The Mill specific Process Batch functionality (see SAP Help for Mill Products ->
Enhancements in Production Planning and Control (PP) -> Process Batch) 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
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.
The item is also relevant to you if you have been using Goods Movements via Mill GI/GR
detail screens in transaction CO11N. (see SAP Help for Mill Products -> Enhancements
in Production Planning and Control (PP) -> Goods Movements in the Confirmation
Transaction).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1170
51.6 S4TWL - Fast entry of characteristic values in trading contract
Application Components:IS-MP-LO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2381873
S4TWL - Fast entry of characteristic
values in trading contract
Symptom
You are doing a system conversion from an older release to SAP S/4HANA 1610 or
newer. The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
As of SAP S/4HANA 1610, the fast entry of characteristic values 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 characteristic values 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 entry of characteristic values in
trading contract transactions WB21, WB22, WB23. You are likely using the fast entry of
characteristic values in trading contract if there are own specific entries for transaction
type ‘Trading Contract’ in customizing step ‘Define Application Group for Characteristic
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1171
Display’ and ‘Define Characteristics Display for Overview Screen’ under IMG “Logistics –
General->Global Trade Management->Trading contract->Fast Entry of Characteristics”.
51.7 S4TWL - Selection by characteristics in mass processing of orders
Application Components:IS-MP-PP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2381891
S4TWL - Selection by characteristics in
mass processing of orders
Symptom
You are doing a system conversion from an older release to SAP S/4HANA 1610 or
newer. The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1172
The simplification item is relevant if you are using the mill specific transaction
/SAPMP/PP_COHV.
51.8 S4TWL - Fast entry of characteristic values in sales document
Application Components:IS-MP-SD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2381843
S4TWL - Fast entry of characteristic
values in sales document
Symptom
You are doing a system conversion from an older release to SAP S/4HANA 1610 or
newer. The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
As of SAP S/4HANA 1610, the fast entry of characteristic values 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 characteristic values of items on the same tab page.
Required and Recommended Actions
If you have been using the fast entry of characteristic values 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.
The Configuration Tab can be set via Fcode “UECO” as default entry Tab for the
overview screen. The End User will then directly be linked to the Configuration Tab
when the transaction is called. The Fcode for the overview screen can be maintained in
the "Define Sales Document types" Customizing settings (Transaction VOV8).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1173
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 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1174
52.Healthcare (IS-H)
52.1 S4TWL - SAP Patient Management (IS-H) is not available in SAP
S/4HANA
Application Components:IS-H
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2689873
SAP S/4HANA: SAP Patient
Management (IS-H): Restriction Note
Symptom
You are using SAP S/4HANA, respectively you are planning or running a conversion to
SAP S/4HANA.
Reason and Prerequisites
SAP does not plan a conversion from SAP Patient Management (IS-H) to S/4HANA.
Solution
For information on planned successor products refer to SAP Road Map for
Healthcare (scroll down on that page).
Even if the Business Function Set HEALTHCARE is not active and therefore a system
conversion to SAP S/4HANA is possible, you must not use any entities in customer
specific code belonging to the above mentioned healthcare products (software component
IS-H). Usages of such entities are identified by the SAP S/4HANA custom code check in
the ABAP Test Cockpit (ATC) with reference to this SAP note.
Also please note, that as of SAP S/4HANA 1809 the majority of the development objects
belonging to the above mentioned healthcare products have been deleted from the
software stack. The remaining objects, still available in S/4HANA, are subject of future
deletions.
Other Terms
IS-H
SAP Patient Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1175
SAP Ambulatory Care Management
i.s.h.med
Business Function Set HEALTHCARE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1176
53.Industry Insurance
53.1 S4TWL - FS-RI - Deletion of obsolete packages
Application Components:FS-RI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2818762
S4TWL - FS-RI - Deletion of obsolete
packages
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
This SAP Note is relevant for you when your start release for the system conversion is an
ERP release.
It is not relevant if your start release is S/4HANA Finance or S/4HANA.
Solution
Description
In SAP Reinsurance Management for SAP S/4HANA and in SAP S/4HANA Insurance
for reinsurance management, packages with development objects that were already
obsolete in SAP Reinsurance Management 7.0 have been deleted.
Business Process related information
Effects on business processes depends on the usage of obsolete objects in custom code.
Required and Recommended Action(s)
Check if the obsolete objects in the piece list are used in custom code. If yes, you must
adapt the custom code.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1177
Other Terms
COMPAT Packages
53.2 S4TWL - Technical changes to Statutory Reporting Tables
Application Components:FS-SR, FS-SR-DE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2810717
S4TWL - FSSR: Correction index 1
(ISSRFLDEO and ISSRFLDEC)
Symptom
You execute a system conversion in SAP S/4HANA, On Premise edition. The following
SAP S/4HANA transition worklist entry is relevant in this case.
Reason and Prerequisites
A change of Index-1 for ISSRFLDEO and ISSRFLDEC to unique is required.
Solution
Description
For the tables mentioned above, there is an index that is not unique. This may lead to
duplicate entries that cause terminations in the application.
Required and recommended action(s)
Proceed as described in SAP Note 2771381.
Other Terms
Worklist
53.3 S4TWL - FS-RI - Replacement of msg.PM Connection by SAP Standard
Application Components:XX-PART-MSG-LRM, FS-RI-LRM
Related Notes:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1178
Note Type
Note Number
Note Description
Business Impact
2954199
S4TWL - Ersetzen der msg.PM
Verbindung durch SAP Standard
Symptom
Sie führen eine Systemkonvertierung in SAP S/4HANA durch. In diesem Fall gilt der
folgende Eintrag im Arbeitsvorrat für den Übergang nach SAP S/4HANA.
Reason and Prerequisites
Dieser SAP-Hinweis ist für Sie relevant, wenn Ihr Ausgangsrelease für die
Systemkonvertierung ein ERP-Release ist.
Er ist nicht relevant, wenn Ihr Ausgangsrelease SAP S/4HANA Finance oder SAP
S/4HANA ist.
Solution
Beschreibung
In SAP Reinsurance Management für SAP S/4HANA und in SAP S/4HANA Insurance
for reinsurance management steht die msg.PM Verbindung nicht mehr zur Verfügung.
Diese muss durch den SAP Standard ersetzt werden.
Geschäftsprozessbezogene Informationen
Die Auswirkungen auf Geschäftsprozesse hängen von der Verwendung der veralteten
Objekte ab.
Erforderliche Aktionen
Überprüfen Sie, ob Sie die veralteten Objekte in Gebrauch hatten. Wenn dies der Fall ist,
müssen folgende Schritte durchgeführt werden:
Es muss die aktuellste CAIMAN-Version (CAIMAN-34140.54) verwendet werden.
Um diese Version verwenden zu können, muss im PM-Customizing die aktuellste
Version eingetragen werden.
Starten Sie die Transaktion /MSG/4_PM_CUSTOMIZE.
Wählen Sie im Feld Anwendung FS-RI-RML-SRA-PM.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1179
Navigieren Sie nach Konfiguration -> RFC-Destinationen -> TCP/IP-
Verbindungen und wählen Sie Ihre CAIMAN-Verbindung aus.
Befüllen Sie das Feld Programm ID mit der aktuellsten CAIMAN-Version
(CAIMAN-34140.54).
Im PM-Customizing muss die Kundeneinstellung gesetzt werden. Dieser Eintrag wird
durch die Conversion geleert.
Starten Sie die Transaktion /MSG/4_PM_CUSTOMIZE.
Wählen Sie im Feld Anwendung FS-RI-RML-SRA-PM.
Navigieren Sie nach Meta-Konfiguration -> Kundeneinstellung
Anwendungen.
Befüllen Sie das Feld PM mit "msg.PM 3.x".
Prüfen Sie im PM-Customizing, dass die Einträge der Request-Destinationen und
Monitor-Destiantionen gesetzt wurden.
Starten Sie die Transaktion /MSG/4_PM_CUSTOMIZE.
Wählen Sie im Feld Anwendung FS-RI-RML-SRA-PM.
Navigieren Sie nach Konfiguration -> Request-Destinationen.
Prüfen Sie die Einträge:
Anwendung: FS-RI-RML-SRA-PM.
RFC-Destination: Tragen Sie die RFC-Destination des PM Runtime
Servers ein.
Drücken Sie "Zurück" und navigieren Sie nach Konfiguration -> Monitor-
Destinationen.
Prüfen Sie die Einträge:
Anwendung: FS-RI-RML-SRA-PM.
RFC-Destination: Tragen Sie die RFC-Destination des PM Runtime
Server Monitors ein.
Produktdaten müssen neu importiert werden.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1180
Starten Sie die Transaktion /MSG/4_PM_CUSTOMIZE.
Wählen Sie im Feld Anwendung FS-RI-RML-SRA-PM.
Navigieren Sie nach Programme -> Produktsammlungs-Import.
Folgende Werte müssen gesetzt werden:
RFC-Destination: Tragen Sie Ihre CAIMAN-RFC-Destination ein
Auftrag/Aufgabe: Wählen Sie einen geeigneten Transportauftrag aus.
Quelle / Datei / Export / Arbeitsbereich / Produktraum: Wählen Sie die
Produktsammlung, welche importiert werden soll, aus.
Übersetzung: Wählen Sie gegenbenenfalls alle relevanten Sprachen
aus.
Fehler zu Warnungen konvertieren: Setzen Sie gegebenenfalls die
relevanten Häkchen.
Protokolle / Verzeichnis: Falls ein Protokoll lokal gesichert werden
soll, setzen Sie das Häkchen und wählen ein Verzeichnis.
Drücken Sie auf "Import durchführen".
Prüfen Sie das Ergebnisprotokoll und drücken Sie auf "Freigeben", falls keine
Fehler vorhanden sind.
Sollte beim Importieren der Produktdaten ein Fehler bzgl. Positivliste auftreten, geben
Sie in der CAIMAN-RFC-Destination unter Anmeldung und Sicherheit folgende Einträge
an:
Gerufener Funktionsbaustein: /MSG/4_PM_FETCH_EXPORTINFOBYUP
Callback-Funktionsbaustein: *
Gerufener Funktionsbaustein: /MSG/4_PM_FETCH_INFORMATION
Callback-Funktionsbaustein: *
Other Terms
msg.PM
CAIMAN
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1181
53.4 S4TWL - FS-RI - Redesign Data Access Framework
Application Components:FS-RI-LRM, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3054946
S4TWL - Data access framework
redesign
Symptom
You are performing a system conversion to SAP S/4HANA.
Reason and Prerequisites
This SAP Note is relevant to you if your source release for the system conversion is an
ERP release.
It is not relevant if your source release is SAP S/4HANA Finance or SAP S/4HANA.
Solution
Description
Interfaces/classes/methods are adjusted or deleted in SAP Reinsurance Management for
SAP S/4HANA and in SAP S/4HANA Insurance for Reinsurance Management:
The following classes for exception calls are not available and have been replaced:
/msg/cx_vrj_after_finish_error
/msg/cx_vrj_assign_error
/msg/cx_vrj_badi_error
/msg/cx_vrj_boc
/msg/cx_vrj_bo_struct_error
/msg/cx_vrj_cmnt_serialisation
/msg/cx_vrj_defaults
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1182
/msg/cx_vrj_illegal_lock_mode
/msg/cx_vrj_invalid_change
/msg/cx_vrj_not_found
/msg/cx_vrj_not_loaded
/msg/cx_vrj_no_da_agent_found
/msg/cx_vrj_object_freed
/msg/cx_vrj_overlapping_vers
/msg/cx_vrj_parent_new
/msg/cx_vrj_parent_not_loaded
/msg/cx_vrj_parent_w_sublvls
/msg/cx_vrj_par_not_bound
/msg/cx_vrj_state_error
/msg/cx_vrj_sublvls_not_loaded
/msg/cx_vrj_type_mismatch
/msg/cx_vrj_undefined_value
/msg/cx_vrj_unknown_rdf_error
/msg/cx_vrj_wrong_journal
The following classes are not available and have been replaced:
/msg/cl_vr_acmarket_001
/msg/cl_vr_aohead_001
/msg/cl_vr_mdtahead_002
/msg/cl_vr_mdtahead_006
/msg/cl_vr_mdtahead_007
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1183
/msg/cl_vr_mmovement_002
/msg/cl_vr_mmovement_006
/msg/cl_vr_mmovement_007
/msg/cl_vr_mmovement_009
/msg/cl_vr_olife_001
/msg/cl_vr_olife_003
/msg/cl_vr_opschr_002
/msg/cl_vr_opschr_003
/msg/cl_vr_opschr_004
/msg/cl_vr_operval_001
/msg/cl_vr_operval_002
/msg/cl_vr_opol_001
/msg/cl_vr_opol_005
/msg/cl_vr_opol_006
/msg/cl_vr_opol_007
/msg/cl_vr_opol_008
/msg/cl_vr_oproalo_001
/msg/cl_vr_oproalo_007
/msg/cl_vr_oproalo_008
/msg/cl_vr_oproalo_009
/msg/cl_vr_oproalo_010
/msg/cl_vr_oproalo_011
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1184
/msg/cl_vr_oproalo_012
The following methods are not available:
inakt_flag (class /MSG/CL_VR_CCOND_002)
set_ inakt_flag (class /MSG/CL_VR_CCOND_002)
inakt_flag (class /MSG/CL_VR_CCOND_003)
set_inakt_flag (/MSG/CL_VR_CCOND_003)
Interface /msg/if_vrj_base
The following objects are not available:
gvt_object_id (variable)
got_changes (object)
gst_field (structure)
gtt_field_list (table)
/msg/if_vrj_core (interface)
get_node_by_id (method)
diff (method)
defaulted_fields (method)
The definition of the following method has been adjusted:
copy
Interface /msg/if_vrj_batr_bo
The definition of the following methods has been adjusted:
load_batchrun
finish_batchrun
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1185
save_batchrun
Interface /msg/if_vrj_batr_boc
The following objects are not available:
gvt_sql_param (variable)
The definition of the following methods has been adjusted:
get_aggatran_nodes
get_closecap_nodes
get_opencap_nodes
get_renewal_nodes
get_reopencap_nodes
Interface /msg/if_vrj_batr_da
The following objects are not available:
gvt_effective_ts (variable)
gvt_processed_ts (variable)
gvt_sql_param (variable)
Interface /msg/if_vrj_batr_jrnl
The following objects are not available:
gtt_batchrun_id (table)
Interface /msg/if_vrj_cross
The following objects are not available:
gst_sql_param (structure)
gst_event_handler (structure)
gtt_event_handler (table)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1186
The definition of the following methods has been adjusted:
select_odelreq
Interface /msg/if_vrj_cust_da
The following objects are not available:
/msg/if_v_dev (interface)
false (alias)
true (alias)
bool (alias)
gst_rnode (structure)
gtt_rnode (table)
select_cclrqst (method)
The definition of the following methods has been adjusted:
select_ccond
select_cestevtra
Interface /msg/if_vrj_mdta_bo
The following objects are not available:
/msg/if_vrj_core_ndim (interface)
got_changes (object)
The definition of the following methods has been adjusted:
dt_changed
after_save
after_release
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1187
load_dt
finish_dt
finish_movement
save_dt
save_movement
Interface /msg/if_vrj_mdta_boc
The following objects are not available:
got_sql_param (object)
gtt_runid (table)
gvt_sql_param (variable)
The definition of the following methods has been adjusted:
create_dtahead
get_dtarun_nodes
get_dtasum_nodes
get_movement_nodes
get_movrun_nodes
get_nullval_nodes
Interface /msg/if_vrj_mdta_da
The following objects are not available:
gst_sql_param (structure)
gst_sql_fieldval (structure)
The definition of the following methods has been adjusted:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1188
select_dtahead
select_movement
select_wmdta
Interface /msg/if_vrj_mdta_jrnl
The following objects are not available:
gtt_jmdta (table)
get_entity_vers (method)
The definition of the following methods has been adjusted:
get_version
get_versions
scroll_processed_back
scroll_processed_forw
Interface /msg/if_vrj_mpol_bo
The following objects are not available:
got_changes (object)
/msg/if_v_dev (interface)
The definition of the following events has been adjusted:
policy_changed
after_save
after_release
The definition of the following methods has been adjusted:
load_pol
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1189
finish_pol
save_pol
Interface /msg/if_vrj_mpol_boc
The following objects are not available:
got_sql_param (object)
gvt_sql_param (variable)
The definition of the following methods has been adjusted:
get_address_nodes
get_calcbase_nodes
get_claimall_nodes
get_claimcon_nodes
get_claimhd_nodes
get_claimimp_nodes
get_claimrev_nodes
get_clairesp_nodes
get_cond_nodes
get_escvect_nodes
get_esc_nodes
get_evidence_nodes
get_hobby_nodes
get_impairmt_nodes
get_insper_nodes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1190
get_inspshr_nodes
get_loadshr_nodes
get_load_nodes
get_occupat_nodes
get_pcshr_nodes
get_perval_nodes
get_polcomp_nodes
get_polresp_nodes
get_proalo_nodes
get_uatch_nodes
Interface /msg/if_vrj_mpol_da
The following objects are not available:
gst_sql_param (structure)
gst_sql_fieldval (structure)
The definition of the following methods has been adjusted:
select_perval
select_wmpol
select_mclevddoc
select_movement
Interface /msg/if_vrj_oapl_bo
The following objects are not available:
reactivate_pol (method)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1191
reactivate_polcomp (method)
reactivate_polcompshr (method)
The definition of the following methods has been adjusted:
load_pol
finish_pol
finish_polcomp
finish_polcompshr
save_pol
save_polcomp
save_polcompshr
Interface /msg/if_vrj_oapl_boc
The following objects are not available:
got_sql_param (object)
gvt_sql_param (variable)
The following methods have been deleted and replaced:
create_esc
create_escvect
delete_esc
delete_escvect
get_esc
get_escvect
get_esc_nodes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1192
lapse_esc
lapse_escvec
set_escvect_data
set_esc_data
The following methods are not available:
get_escvect_nodes
lapse_polalloc
lapse_polresp
The definition of the following methods has been adjusted:
get_calcbase_nodes
get_cond_nodes
get_hobby_nodes
get_insper_nodes
get_inspshr_nodes
get_loadshr_nodes
get_load_nodes
get_occupat_nodes
get_perval_nodes
get_polalloc_nodes
get_polresp_nodes
get_proalo_nodes
Interface /msg/if_vrj_oapl_da
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1193
The following objects are not available:
got_sql_param (object)
gvt_unfinished_run_id (variable)
gst_sql_param (structure)
gst_sql_fieldval (structure)
The following structure has been deleted and replaced:
gstt_proalo
The definition of the following methods has been adjusted:
select_pcshr
select_pol
select_proalo
Interface /msg/if_vrj_oapl_jrnl
The following method is not available:
get_ts_by_movid
Interface /msg/if_vrj_oapp_bo
The following objects are not available:
got_changes (object)
/msg/if_v_dev (interface)
The definition of the following methods has been adjusted:
application_changed
after_save
after_release
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1194
Interface /msg/if_vrj_oapp_boc
The following objects are not available:
got_sql_param (object)
gvt_sql_param (variable)
/msg/if_v_dev (interface)
The definition of the following methods has been adjusted:
get_evidence_nodes
get_impairmt_nodes
get_uatch_nodes
Interface /msg/if_vrj_oapp_da
The following objects are not available:
gst_sql_param (structure)
gst_sql_fieldval (structure)
The definition of the following method has been adjusted:
select_woapp
Interface /msg/if_vrj_oapp_jrnl
The following objects are not available:
gtt_joapp (table)
get_load_keys (method)
get_entity_very (method)
The definition of the following methods has been adjusted:
get_version
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1195
get_versions
scroll_processed_back
scroll_processed_forw
Interface /msg/if_vrj_olif_bo
The following objects are not available:
/msg/if_vrj_core_ndim (interface)
/msg/if_v_dev (interface)
got_changes (object)
reactive_life (method)
reactive_claimhd (method)
The definition of the following events has been adjusted:
after_save
after_release
The definition of the following methods has been adjusted:
load_life
finish_life
finish_claimhd
save_life
save_claimhd
Interface /msg/if_vrj_olif_boc
The following objects are not available:
got_sql_param (object)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1196
gvt_sql_param (variable)
The definition of the following methods has been adjusted:
get_address_nodes
get_claimhd_nodes
get_idalloc_nodes
get_facdem_nodes
get_ident_nodes
get_insinfo_nodes
Interface /msg/if_vrj_olif_da
The following objects are not available:
gst_sql_param (structure)
gst_sql_fieldval (structure)
The definition of the following methods has been adjusted:
select_life
select_wolif
Interface /msg/if_vrj_olif_jrnl
The following objects are not available:
gtt_jolif (table)
gvt_change_user (variable)
get_load_keys (method)
get_entity_vers (method)
The definition of the following methods has been adjusted:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1197
get_version
get_versions
scroll_effective_back
scroll_effective_forw
scroll_processed_back
scroll_processed_forw
get_ts_at
Interface /msg/if_vrj_opol_bo
The following objects are not available:
/msg/if_vrj_core_ndim (interface)
/msg/if_v_dev (interface)
/msg/if_7f_da_mgr (interface)
reactive_claimall (method)
The definition of the following events has been adjusted:
policy_changed
after_save
after_release
The definition of the following methods has been adjusted:
finish_claimall
save_claimall
Interface /msg/if_vrj_opol_boc
The following objects are not available:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1198
got_sql_param (object)
gvt_sql_param (variable)
The definition of the following methods has been adjusted:
delete_cldecidx
get_claimall_nodes
get_claimassreq_nodes
get_claimcon_nodes
get_claimimp_nodes
get_claimrev_nodes
get_clairesp_nodes
get_evidence_nodes
get_impairmt_nodes
Interface /msg/if_vrj_opol_da
The following objects are not available:
gst_sql_param (structure)
gst_sql_fieldval (structure)
The definition of the following methods has been adjusted:
select_claim
select_wopol
select_pprwnd
Interface /msg/if_vrj_opol_jrnl
The following objects are not available:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1199
gtt_jopol (table)
get_load_keys (method)
get_entity_vers (method)
The definition of the following methods has been adjusted:
get_version
get_versiona
scroll_effective_back
scroll_effective_forw
scroll_processed_back
scroll_processed_forw
get_ts_at
Interface /msg/if_vrj_ocm_da
The following objects are not available:
/msg/if_v_dev (interface)
false (alias)
true (alias)
bool (alias)
Interface /msg/if_vrj_pl_callback
The following object is no longer available:
is_defaulting_active (method)
Interface /msg/if_vrj_core
The interface /msg/if_vrj_core is not available and has been partially replaced.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1200
Meta model / object model / entity model OPCSHR
The entity model OPCSHR has been replaced.
BAPI interface /msg/bapi_vmpol_create
The interface of /msg/bapi_vmpol_create has been adjusted. The following parameters have been
removed:
ct_claimall
ct_claimass
ct_claimcon
ct_claimdec
ct_claimimp
ct_evidence
ct_impairmt
ct_uwass
ct_uwipdec
ct_uwpoldat
ct_claimass
ct_evidence_notice
ct_impairmt_notice
ct_claimdec_notice
Adjustment of structures
The fields DEFAULT_VALUE and DEFAULT_END_TS have been removed from the following
structures:
/MSG/BAPI_VDMPCLOGMSGS
/MSG/BAPI_VDMPCSLOGMSGS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1201
/MSG/BAPI_VDMPOLLOGMSGS
/MSG/BAPI_VDMADDLOGMSGS
/MSG/BAPI_VDMCLMLOGMSGS
/MSG/BAPI_VDMCLMCOSLOGMSGS
/MSG/BAPI_VDMCLMASSLOGMSGS
/MSG/BAPI_VDMCLMCONLOGMSGS
/MSG/BAPI_VDMCLMHDLOGMSGS
/MSG/BAPI_VDMCLMDECLOGMSGS
/MSG/BAPI_VDMCLMIMPLOGMSGS
/MSG/BAPI_VDMCLMSHRLOGMSGS
/MSG/BAPI_VDMESCLOGMSGS
/MSG/BAPI_VDMESCVECTLOGMSGS
/MSG/BAPI_VDMEVIDLOGMSGS
/MSG/BAPI_VDMHOBLOGMSGS
/MSG/BAPI_VDMIDENTLOGMSGS
/MSG/BAPI_VDMIMPLOGMSGS
/MSG/BAPI_VDMINSPERLOGMSGS
/MSG/BAPI_VDMLOADLOGMSGS
/MSG/BAPI_VDMLOASHRLOGMSGS
/MSG/BAPI_VDMOCCLOGMSGS
/MSG/BAPI_VDMPERVALLOGMSGS
/MSG/BAPI_VDMPROALOLOGMSGS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1202
Information related to the business process
The impact on business processes depends on the use of the adjusted or deleted objects.
Required Action(s)
Check whether the deleted or changed objects specified in the object list and in this SAP
Note are used. If so, you must replace the deleted or changed objects.
A replacement is delivered for the following deleted objects:
Replace the following deleted classes for exception calls
/msg/cx_vrj_after_finish_error
/msg/cx_vrj_assign_error
/msg/cx_vrj_badi_error
/msg/cx_vrj_boc
/msg/cx_vrj_bo_struct_error
/msg/cx_vrj_cmnt_serialisation
/msg/cx_vrj_defaults
/msg/cx_vrj_illegal_lock_mode
/msg/cx_vrj_invalid_change
/msg/cx_vrj_not_found
/msg/cx_vrj_not_loaded
/msg/cx_vrj_no_da_agent_found
/msg/cx_vrj_object_freed
/msg/cx_vrj_overlapping_vers
/msg/cx_vrj_parent_new
/msg/cx_vrj_parent_not_loaded
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1203
/msg/cx_vrj_parent_w_sublvls
/msg/cx_vrj_par_not_bound
/msg/cx_vrj_state_error
/msg/cx_vrj_sublvls_not_loaded
/msg/cx_vrj_type_mismatch
/msg/cx_vrj_undefined_value
/msg/cx_vrj_unknown_rdf_error
/msg/cx_vrj_wrong_journal
with the superclass: /msg/cx_vrj
Replace the following deleted classes
/msg/cl_vr_acmarket_001: /msg/cl_va_get_market_id
/msg/cl_vr_aohead_001: /msg/cl_va_get_head_id
/msg/cl_vr_mdtahead_002: /msg/cl_vr_get_dtahd_by_dtano
/msg/cl_vr_mdtahead_006: /msg/cl_vr_get_dtahd_wo_sysdta
/msg/cl_vr_mdtahead_007: /msg/cl_vr_get_systemdtaid
/msg/cl_vr_mmovement_002: /msg/cl_vr_get_error_movs_hist
/msg/cl_vr_mmovement_006: /msg/cl_vr_get_single_movement
/msg/cl_vr_mmovement_007: /msg/cl_vr_get_mov_by_refmovid
/msg/cl_vr_mmovement_009: /msg/cl_vr_get_mov_by_dtaid
/msg/cl_vr_olife_001: /msg/cl_vr_get_current_life
/msg/cl_vr_olife_003: /msg/cl_vr_get_life_by_lifeno
/msg/cl_vr_opschr_002: /msg/cl_vr_get_m_shrs_tty_sect
/msg/cl_vr_opschr_003: /msg/cl_vr_get_m_sh_pol_pk_cap
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1204
/msg/cl_vr_opschr_004: /msg/cl_vr_get_prev_shr_vers
/msg/cl_vr_operval_001: /msg/cl_vr_get_pv_by_effective
/msg/cl_vr_operval_002: /msg/cl_vr_get_m_young_perval
/msg/cl_vr_opol_001: /msg/cl_vr_get_m_pol_count
/msg/cl_vr_opol_005: /msg/cl_vr_get_by_polno_cedent
/msg/cl_vr_opol_006: /msg/cl_vr_get_by_pno_origced
/msg/cl_vr_opol_007: /msg/cl_vr_get_by_pnoorigc_ced
/msg/cl_vr_opol_008: /msg/cl_vr_get_by_pnoorigc_orc
/msg/cl_vr_oproalo_001: /msg/cl_vr_get_pl_bal
/msg/cl_vr_oproalo_007: /msg/cl_vr_get_pl_cap
/msg/cl_vr_oproalo_008: /msg/cl_vr_get_pl_by_reverse
/msg/cl_vr_oproalo_009: /msg/cl_vr_get_pl_by_id
/msg/cl_vr_oproalo_010: /msg/cl_vr_get_pl_acc_assign
/msg/cl_vr_oproalo_011: /msg/cl_vr_get_pl_history
/msg/cl_vr_oproalo_012: /msg/cl_vr_get_pl_functional
Replace the following deleted methods (interface /msg/if_vrj_oapl_boc)
create_esc
create_escvect
delete_esc
delete_escvect
get_esc
get_escvect
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1205
get_esc_nodes
lapse_esc
lapse_escvec
set_escvect_data
set_esc_data
with the corresponding method of the interface: /msg/if_vrj_opol_boc
Replace the structure gstt_proalo (interface /msg/if_vrj_oapl_da) with the new
structure: gst_proalo (interface /msg/if_vrj_oapl_da)
The interface /msg/if_vrj_core is not available.
Replace the method META_DATA: Functions available in
/msg/cl_vr_bo_manager
Replace the following methods with the methods from the respective journal
class of the BO models (/msg/cl_vrj_oapl, /msg/cl_vrj_oapp,
/msg/cl_vrj_opol, /msg/cl_vrj_mpol, /msg/cl_vrj_olif, /msg/cl_vrj_mdta):
Replace the method LOAD: /msg/if_vrj_<BO_NAME>_bo->
load_<ENTITYNAME>
Replace the method
LOAD_SUBNODE: /msg/if_vrj_<BO_NAME>_bo->
load_<ENTITYNAME>
Replace the method SAVE: /msg/if_vrj_<BO_NAME>_bo->
load_<ENTITYNAME>
Replace the method
RELEASE_ALL: /msg/if_vrj_<BO_NAME>_bo-> release_all
Replace the method RELEASE: /msg/if_vrj_<BO_NAME>_bo->
release_<ENTITYNAME>
Replace the method CHECK_CHANGED: /msg/if_vrj_oapl_bo-
>check_pol_changed or /msg/if_vrj_base->node_has_changed
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1206
Replace the method
GET_ACCESS_MODE: if_vrj_<BO_NAME>_bo-
>get_acc_mode_<ENTITYNAME>
Replace the method
CREATE_ROOT_BOC: /msg/if_vrj_<BO_NAME>_boc-
>create_<ENTITYNAME>
Replace the method
CREATE_BOC: /msg/if_vrj_<BO_NAME>_boc-
>create_<ENTITYNAME>
Replace the method DELETE_BOC: /msg/if_vr_boc->delete
Replace the method
DELETE_BOC_IRREVOCABLE: /msg/if_vr_boc->delete
Replace the method LAPSE_BOC: /msg/if_vrj_<BO_NAME>_boc-
>lapse_<ENTITYNAME>
Replace the method
SET_ATTIBUTES: /msg/if_vrj_<BO_NAME>_boc-
>set_<ENTITYNAME>_data
Replace the following methods with the methods from /msg/if_vrj_base:
Replace the method RESOLVE_BO_STRUCT: /msg/if_vrj_base ->
resolve_bo_struct
Replace the method BO_NODE_LIST_FROM_DB:
/msg/if_vrj_base->resolve_bo_structure
Replace the method
BO_NODE_LIST_FROM_MEMORY: /msg/if_vrj_base-
>resolve_bo_structure
Replace the method DA_CREATE: /msg/cl_vrj_base -> member
instance mo_legacy_da (/msg/cl_vrj_legacy_da) -> create
Replace the method DA_CREATE_TABLE: /msg/cl_vrj_base ->
member instance mo_legacy_da (/msg/cl_vrj_legacy_da) ->
create_table
Replace the method DA_UPDATE: /msg/cl_vrj_base -> member
instance mo_legacy_da (/msg/cl_vrj_legacy_da) -> update
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1207
Replace the method DA_UPDATE_TABLE: /msg/cl_vrj_base ->
member instance mo_legacy_da (/msg/cl_vrj_legacy_da) ->
update_table
Replace the method DA_DELETE: /msg/cl_vrj_base -> member
instance mo_legacy_da (/msg/cl_vrj_legacy_da) -> delete
Replace the method DA_DELETE_TABLE: /msg/cl_vrj_base ->
member instance mo_legacy_da (/msg/cl_vrj_legacy_da) ->
delete_table
Replace the method GET_CHILDREN:/msg/if_vrj_base-
>get_children.
Replace the method GET_ROOT: /msg/if_vrj_base->get_root
Replace the method GET_PARENT: /msg/if_vrj_base->get_parent
Replace the method GET_PARENT_LEVEL: /msg/if_vrj_base-
>get_parent_level
Replace the method GET_MODEL_NAME: /msg/if_vrj_base-
>get_model_name
Replace the method GET_ENTITY_NAME: /msg/if_vrj_base-
>get_entity_name
Replace the method GET_HIST_TYPE: /msg/if_vrj_base-
>get_hist_type
Replace the method GET_TABLE_NAME: /msg/if_vrj_base-
>get_table_name
Replace the method COPY: /msg/if_vrj_base->copy
Replace the method MODEL: /msg/if_vrj_base->get_model_name
Replace the method SET_MIGRATION: /msg/if_vrj_base-
>set_migration
Replace the method BO_CHANGES: /msg/if_vrj_base-
>changed_attributes or /msg/if_vrj_base->changed_nodes
Replace the constants with the corresponding constants
from: /msg/if_vrj_base
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1208
The meta model / object model / entity model OPCSHR has been replaced:
OPOL_OPCSHR
OAPP_OPCSHR
Check whether the entity model OPCSHR has been redefined:
Call transaction /MSG/7FW_START.
Load the application 10000.
Navigate to "Meta Models -> Object Models -> Entity Models" and open the
entity model OPCSHR.
Check whether a redefinition was performed for the entity OPCSHR.
If a redefinition was performed, create a message for the component FS-RI-LRM to have the
entity models OPOL_OPCSHR or OAPP_OPCSHR enabled for redefinitions.
Objects that are listed as deleted in the object list or in the solution information of this SAP Note
and that do not have a corresponding replacement listed in this SAP Note were deleted
without replacement.
53.5 S4TWL - Deletion of obsolete objects (Compat-Packages)
Application Components:FS-RI-LRM, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3047902
S4TWL - Deletion of obsolete objects
(compat packages)
Symptom
You are performing a system conversion to SAP S/4HANA.
Reason and Prerequisites
This SAP Note is relevant to you if your source release for the system conversion is an
ERP release.
It is not relevant if your source release is SAP S/4HANA Finance or SAP S/4HANA.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1209
Solution
Description
Packages with development objects that were already obsolete in SAP Reinsurance
Management 7.0 are deleted in SAP Reinsurance Management for SAP S/4HANA and in
SAP S/4HANA Insurance for reinsurance management.
Information related to the business process
The impact on business processes depends on the use of the obsolete objects.
Required actions
Check if the obsolete objects in the object list are used in user-specific source code. If
this is the case, you must adjust the user-specific source code.
Some of the deleted programs are replaced by new programs. To do this, you can perform
the following steps:
Replace the obsolete program /MSG/VRP_BA_DEL_DTA with the new
program: /MSG/VRP_BA_DT_DELETE
Replace the obsolete program /MSG/VRP_BA_DEL_DTA_PP with the new
program: /MSG/VRP_BA_DT_DELETE_PP
Replace the obsolete program /MSG/VRP_BA_MOVEMT_PPROC with the new
program: /MSG/VRP_BA_MOV_PROC_PP
Replace the obsolete program /MSG/VRP_BA_MOVEMT_PROC with the new
program: /MSG/VRP_BA_MOV_PROC
Replace the obsolete program /MSG/VRP_BA_MOVEMT_REWND with the new
program: /MSG/VRP_BA_REWIND
Replace the obsolete program /MSG/VRP_BA_CLOSECAP with the new program:
/MSG/VRP_BA_CAP_CLOSE
Replace the obsolete program /MSG/VRP_BA_CLOSECAP_PP with the new
program: /MSG/VRP_BA_CAP_CLOSE_PP
Replace the obsolete program /MSG/VRP_BA_OPENCAP with the new program:
/MSG/VRP_BA_CAP_OPEN
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1210
Replace the obsolete program /MSG/VRP_BA_REOPENCAP with the new program:
/MSG/VRP_BA_CAP_REOPEN
Other Terms
COMPAT Packages
53.6 S4TWL - FS-RI - Deletion of LSMW Integration
Application Components:FS-RI-LRM, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2887844
S4TWL - Deletion of LSMW integration
Symptom
You are performing a system conversion to SAP S/4HANA. In this case, the following
entry in the worklist for the transition to SAP S/4HANA applies.
Reason and Prerequisites
This SAP Note is relevant to you if your source release for the system conversion is an
ERP release.
It is not relevant if your source release is SAP S/4HANA Finance or SAP S/4HANA.
Solution
Description
The "Import of a Data Transmission" background job is no longer available In SAP
Reinsurance Management for SAP S/4HANA and in SAP S/4HANA Insurance for
reinsurance management. When you navigate to a data transmission, the "LSMW" and
"IDocs" tab pages and the import button that are displayed when the data transmission is
being processed are also no longer available.
Information related to the business process
The impact on business processes depends on the use of the obsolete objects.
Required and recommended action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1211
Check whether you used the obsolete objects. If this is the case, you must implement
your own solution for importing a data transmission, if you do not do so already.
Other Terms
LSMW
IDocs
/MSG/VRP_BA_IMPORT_DTA.
53.7 S4TWL - FS-RI - Replacement of a Semantic Object in Fiori App and
Transaction
Application Components:FS-RI-LRM, FS-RI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2970970
S4TWL - FS-RI - Replacement of a
Semantic Object in Fiori App and
Transaction
Symptom
You intend to do a release upgrade from SAP S/4HANA 1909 to SAP S/4HANA 2020.
The following SAP S/4HANA 2020 Transition Worklist item is applicable in this case.
Reason and Prerequisites
This SAP Note is relevant, if the current release is SAP S/4HANA 1909.
Solution
Description
In SAP Reinsurance Management for SAP S/4HANA 2020 following objects are not
available:
Transaction /MSG/X_V_OPEN_POLICY
Program /MSG/X_V_OPEN_POLICY
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1212
semantic object ReinsuranceLifeRiskPolicy
Business Process related information
The effects on business processes depend on the usage of the obsolete objects.
Required Action(s)
Check if the obsolete objects, specified in the piece list, are in use. If yes, you must
follow these steps:
Replace the obsolete transaction/MSG/X_V_OPEN_POLICY with the new
transaction: /MSG/X_V_POLICY_MGMT
Replace the obsolete program /MSG/X_V_OPEN_POLICY with the new program:
/MSG/X_V_POLICY_MGMT
Replace the obsolete semantic object ReinsuranceLifeRiskPolicy with the new
semantic object: RMLifePlcyNumber
Other Terms
Inforce Summary
53.8 S4TWL - FS-RI - Ensuring the functionality of the Extension Service
Application Components:FS-RI-LRM, FS-RI-ES, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2972152
S4TWL - FS-RI - Ensuring the
functionality of the Extension Service
Symptom
You are performing a system conversion to SAP S/4HANA. In this case, the following
entry in the worklist for the transition to SAP S/4HANA applies.
Reason and Prerequisites
This SAP Note is relevant to you if your source release for the system conversion fulfills
one of the following conditions:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1213
ERP system
SAP S/4HANA 1709 (FP 02) to SAP S/4HANA 2020 (Initial Shipment Stack)
Solution
Description
Extension Service objects are no longer available in SAP Reinsurance Management for
SAP S/4HANA and in SAP S/4HANA Insurance for reinsurance management.
Information related to the business process
The impact on business processes depends on the use of the obsolete objects.
Required actions
Check whether you used the obsolete objects. If you did, you must perform the following
steps:
During the SPAU and SPDD adjustment, the system may issue warnings stating that an
adjustment is required for modified objects. This affects Extension Service structures
with the name /MSG/BAPI_ED_* or /MSG/BAPI_EC_*. You can ignore these warnings.
You can also reset the modifications. However, this may result in errors and should
therefore be avoided.
When the Extension Service is regenerated after the upgrade, these BAPI structures are
also regenerated. As a result, the Extension Service is consistent and functioning again.
Create customer variant
Call transaction /MSG/7FW_START.
Double-click "Workplace" and open the application "10000".
Right-click "10000" and choose "Customer Variant".
Populate the following fields:
Customer Variant
License Key
Storage Package of Classes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1214
Class Prefix
Choose "New".
Save the change and choose a suitable request to do so.
Choose "Generate".
Call transaction /MSG/7FW_START again and, before choosing "Generate",
ensure that all requests that contain the relevant objects have been released.
Call transaction /MSG/2_ES_EXT_SRVC.
Under "Applications", select FS-RI-RML-SRA-PM.
Under "Extendable Tables", select the table /MSG/VDOCLAIM.
Under "Enhancements", select /MSG/ED_OCLM01 and choose "Activate" (Ctrl+F3).
In the dialog box that is displayed, create a request and save it.
Confirm any other dialog boxes that may be displayed. If the system displays a dialog
box for the IDocs, choose "No".
If no errors occur, navigate back to transaction /MSG/2_ES_EXT_SRVC and repeat
the steps 3 to 6 for the following tables:
/MSG/VDOCOND
/MSG/VDOCONDBASE
/MSG/VDOINSPER
/MSG/VDOLOAD
/MSG/VDOPCSHR
/MSG/VDOPOL
/MSG/VDOPOLCOMP
Navigate back to transaction /MSG/2_ES_EXT_SRVC and select FS-RI-RML-SRA
under "Applications".
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1215
Repeat the steps 3 to 6 for the following tables:
/MSG/VDOUWASS
/MSG/VDOUWPOLDAT
Note that two enhancements must be generated for /MSG/VDOUWASS.
If errors occur during generation, call the transaction again and generate the enhancement
again.
The system may issue the following error messages:
"Unable to load business object element ENTITY"
"Unable to load business object element PERSISTENCE"
"Unable to load business object element CHMODEL"
"Unable to load business object element CTRLMODEL"
Del-tool for problems with COND
Add the following entry to the table /MSG/0CHECK:
KORVAS-SAP
Call transaction /MSG/2_ES_DEL_TOOL.
Select the entry RCOND01.
Choose "Generate Standard".
Other Terms
Extension Service
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1216
53.9 S4TWL - FS-RI deletion of obsolete functionality for FI-AR
Application Components:FS-RI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2964772
S4TWL - FS-RI deletion of obsolete
functionality for FI-AR
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
This SAP Note is relevant for you when your start release for the system conversion is an
ERP release.
It is not relevant if your start release is S/4HANA Finance or S/4HANA.
Solution
Description
In SAP Reinsurance Management for SAP S/4HANA and in SAP S/4HANA Insurance
for reinsurance management, obsolete FS-RI functionality objects for FI-AR are deleted.
Business Process related information
Following business processes are no longer available:
Goto Accounts Receivable (Transaction /MSG/RFDMN)
Transfer Posting (Transaction /MSG/R_AU)
Cash Loss/Noted Item (Transaction /MSG/R_AS and /MSG/R_AS1)
Broker View of Line Items (Transaction /MSG/R_KM)
For Goto Accounts Receivable use Transaction RFDMN instead of /MSG/RFDMN.
For Transfer Posting use Transaction /MSG/R_AU1 instead of /MSG/R_AU.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1217
Effects on customer business processes depends on the usage of obsolete objects in
custom code.
Required and Recommended Action(s)
Check if the obsolete objects in the piece list are used in custom code. If yes, you must
adapt the custom code.
53.10S4TWL - FS-RI - Deletion and Replacement of Obsolete CDS Views
Application Components:FS-RI-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3040673
S4TWL - deleting and replacing CDS
views
Symptom
You want to perform a release upgrade from SAP S/4HANA 1909 or SAP S/4HANA
2020 to SAP S/4HANA 2021 or higher.
Reason and Prerequisites
This SAP Note is relevant if your current release is SAP S/4HANA 1909 or SAP
S/4HANA 2020.
Solution
Description
CDS views are deleted and replaced in SAP Reinsurance Management for SAP
S/4HANA 1909 and SAP Reinsurance Management for SAP S/4HANA 2020.
The following CDS views are not available in SAP Reinsurance Management for SAP
S/4HANA 2021 and higher and have been replaced:
/MSG/I_RTreatyInvolvementShrB
/MSG/I_VOpPerValMaxID
/MSG/I_VOpPerValMaxValidity
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1218
/MSG/I_REntryCodeB
/MSG/I_RAcctgUnitB
/MSG/I_RClassOfBusinessB
/MSG/I_RLineOfBusinessB
/MSG/I_RUnderwritingAreaB
/MSG/I_RPartnerInvolved
/MSG/I_RTreatyB
/MSG/I_REAKZB
/MSG/V_ACCTRANS_SELECT_CL_NO
The following CDS views were deleted without subsitution:
/MSG/VRP_LATEST_CLAIM_STATUS
/MSG/V_ACCTRANS_SELECT_CLAIM
/MSG/V_ACCTRANS_SEL_CL_LATEST
Information related to the business process
The impact on business processes depends on the use of the deleted CDS views.
Required Action(s)
Check whether the deleted CDS views specified in the object list are used. If so, you must
replace the deleted CDS views:
Replace the obsolete CDS view /MSG/I_RTreatyInvolvementShrB with the new CDS
view: /MSG/I_RTreatyInvolvementShr
Replace the obsolete CDS view /MSG/I_VOpPerValMaxID with the new CDS view:
/MSG/I_VOpSumRiskReinsAccMaxID
Replace the obsolete CDS view /MSG/I_VOpPerValMaxValidity with the new CDS
view: /MSG/I_VOpSumRiskAccuMaxVldty
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1219
Replace the obsolete CDS view /MSG/I_REntryCodeB with the new CDS view:
/MSG/I_REntryCodeBasic
Replace the obsolete CDS view /MSG/I_RAcctgUnitB with the new CDS view:
/MSG/I_RAccountingUnitB
Replace the obsolete CDS view /MSG/I_RClassOfBusinessB with the new CDS
view: /MSG/I_RClassOfBusinessBasic
Replace the obsolete CDS view /MSG/I_RLineOfBusinessB with the new CDS view:
/MSG/I_RLineOfBusinessB
Replace the obsolete CDS view /MSG/I_RUnderwritingAreaB with the new CDS
view: /MSG/I_RUnderwritingAreaBasic
Replace the obsolete CDS view /MSG/I_RPartnerInvolved with the new CDS view:
/MSG/I_RBusPartInvolved
Replace the obsolete CDS view /MSG/I_RTreatyB with the new CDS view:
/MSG/I_RTreatyBasic
Replace the obsolete CDS view /MSG/I_REAKZB with the new CDS view:
/MSG/I_RTreatyUseAssumedCededB
Replace the obsolete CDS view /MSG/V_ACCTRANS_SELECT_CL_NO with the
new CDS view: /MSG/V_AGGSEL_CLAIMSHR_LIFETME
Other Terms
CDS
CDS views
View
Online Analytic
Data Extraction
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1220
53.11S4TWL - FS-RI Deletion of obsolete functionality for FS-RI-B
Application Components:FS-RI, FS-RI-LRM, FS-RI-B
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3061212
Worklist for transition to SAP S/4HANA -
FS-RI: Deletion of obsolete functions for
information system reports
Symptom
You perform a system conversion to SAP S/4HANA. In this case, the following entry
applies in the worklist for the transition to SAP S/4HANA.
Reason and Prerequisites
This SAP Note is relevant to you if your source release for the system conversion is an
ERP release.
It is not relevant if your source release is SAP S/4HANA Finance or SAP S/4HANA.
Solution
Description
In SAP Reinsurance Management for SAP S/4HANA and in SAP S/4HANA Insurance
for Reinsurance Management, obsolete FS-RI functions for information system reports
are deleted.
Information related to the business process
The impact on business processes depends on the use of the obsolete objects.
Required and recommended action(s)
Check if the obsolete objects in the object list are used in user-specific source code. If
this is the case, you must adjust the user-specific source code.
The following transactions are no longer available:
Evaluation of Funds (transaction /MSG/R_A_DEPOT)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1221
Treaties by Broker (transaction /MSG/R_VTGM)
Treaties by Cedent (transaction /MSG/R_VTGZ)
Cedent/Reinsurer (transaction /MSG/R_PGES1)
Broker (transaction /MSG/R_PGES2)
Cedent/Reinsurer and Broker (transaction /MSG/R_PGES3)
Cedent/Reinsurer and/or Broker (transaction /MSG/R_PGES4)
Neither Cedent/Reinsurer nor Broker (transaction /MSG/R_PGES5)
The following user menu items and menu folders are no longer available in the menu
"Insurance -> Reinsurance Information System Reports ->":
Funds -> Evaluation of Funds
Funds
Treaty -> Treaties by Broker
Treaty -> Treaties by Cedent
Business Partner -> Cedent/Reinsurer
Business Partner -> Broker
Business Partner -> Cedent/Reinsurer and Broker
Business Partner -> Cedent/Reinsurer and/or Broker
Business Partner->Neither Cedent/Reinsurer nor Broker
Business Partner
The menu template /MSG/FSRI_800_TEMPLATE has been adjusted accordingly.
The transactions and menu items have been deleted from the following predefined roles:
/MSG/V_LRM_BASIC_SETTING
/MSG/FSRI_800_TEMPLATE
/RUI/BR_RI_TREATY_ADMIN_NL
Group: /RUI/FSRI_BCG_TREATY_ADMIN_REPORTS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1222
/RUI/BR_RI_TREATY_ADMIN_L
Group: /RUI/FSRI_BCG_TREATY_ADMIN_L_REPORTS
Required and recommended action(s)
Check if the obsolete objects in the object list are used in user-specific source code. If
this is the case, you must adjust the user-specific source code.
Check if the obsolete objects in the object list are used in user-specific roles. If this is the
case, you must adjust the user-specific roles.
Check if the obsolete objects in the object list are used in user-specific menus. If this is
the case, you must adjust the user-specific menus.
53.12S4TWL - FS-RI – Deprecation of RAM APIs with SAP S/4HANA 2021
Application Components:XX-PART-MSG-RAM, FS-RI-RAM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3104363
S4TWL - FS-RI - Announcement of
deletion of obsolete RAM APIs
Symptom
You want to perform a system conversion from EHP7 FOR SAP ERP 6.0 - 06 (10/2014) or
higher, or a release upgrade from SAP S/4HANA 1709, SAP S/4HANA 1809, SAP S/4HANA
1909, SAP S/4HANA 2020, or SAP S/4HANA 2021 to SAP S/4HANA 2021 or higher.
Reason and Prerequisites
This SAP Note is relevant if your current release is EHP7 FOR SAP ERP 6.0 - 06 (10/2014)
or higher, SAP S/4HANA 1709, SAP S/4HANA 1809, SAP S/4HANA 1909, SAP S/4HANA
2020, or SAP S/4HANA 2021.
Solution
Description
The following function modules are deprecated with Release SAP S/4HANA 2021 and will be
deleted completely as of Release SAP S/4HANA 2022.
/MRA/A2A_IR_MODIFY_RISK
/MRA/A2A_RTA_C_PRE_ACCOUNTS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1223
/MRA/A2X_IR_F_ENDPER_BY_EL
/MRA/A2X_IR_M_REGISTER_RISK
/MRA/A2X_IR_P_SHIFT_RISK
/MRA/A2X_RR_F_BY_ELEMENTS
/MRA/A2X_RR_M_PRECESSION
/MRA/A2X_RTA_C_PRE_ACCOUNTS
Information related to the business process
If your target release is SAP S/4HANA 2021, using the obsolete function modules has no
effect for the time being. However, we recommend that you start using the replacing function
modules as soon as possible.
If your target release is SAP S/4HANA 2022, it is no longer technically possible to use the
deleted function modules. They must be replaced by the new function modules.
Required Action(s)
Check whether you are using one of the obsolete or deleted function modules and replace it
with the new function module as soon as possible, as described above:
/MRA/A2A_IR_MODIFY_RISK is replaced by
/MRA/A2A_IR_MODIFY_RISK_V2
/MRA/A2A_RTA_C_PRE_ACCOUNTS is replaced by
/MRA/A2A_RTA_C_PRE_ACCOUNTS_V2
/MRA/A2X_IR_F_ENDPER_BY_EL is replaced by
/MRA/A2X_IR_F_ENDPER_BY_EL_V2
/MRA/A2X_IR_M_REGISTER_RISK is replaced by
/MRA/A2X_IR_M_REGISTER_RISK_V2
/MRA/A2X_IR_P_SHIFT_RISK is replaced by
/MRA/A2X_IR_P_SHIFT_RISK_V2
/MRA/A2X_RR_F_BY_ELEMENTS is replaced
by /MRA/A2X_RR_F_BY_ELEMENTS_V2
/MRA/A2X_RR_M_PRECESSION is replaced by
/MRA/A2X_RR_M_PRECESSION_V2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1224
/MRA/A2X_RTA_C_PRE_ACCOUNTS is replaced by
/MRA/A2X_RTA_C_PRE_ACCOUNTS_V2
Other Terms
Risk Aggregation Management (RAM)
/MRA/A2A_IR_MODIFY_RISK
/MRA/A2A_RTA_C_PRE_ACCOUNTS
/MRA/A2X_IR_F_ENDPER_BY_EL
/MRA/A2X_IR_M_REGISTER_RISK
/MRA/A2X_IR_P_SHIFT_RISK
/MRA/A2X_RR_F_BY_ELEMENTS
/MRA/A2X_RR_M_PRECESSION
/MRA/A2X_RTA_C_PRE_ACCOUNTS
53.13S4TWL - FS-RI - Interface adaptation in the claim
Application Components:FS-RI-LRM, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3210235
Transition to SAP S/4HANA - FS-RI -
interface adjustment in loss
Symptom
You are performing a system conversion to SAP S/4HANA 2022.
Reason and Prerequisites
This SAP Note is relevant if your source release for the system conversion is an ERP
release or an SAP S/4HANA release up to and including SAP S/4 HANA 2021.
It is not relevant if your source release is SAP S/4HANA Finance.
Solution
Description
In the Release SAP S/4HANA 2022, the following methods are deleted and no longer
available:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1225
Class /MSG/CL_VRP_LIB_BO_CLAIM_MOV:
CHECK_CLAIMHD_ALLOC_CLAIM: No replacement
CREATE_NEW_CL_DECISION: The method has been integrated into the
method COPY_OCLAIM_ASS of the class
/MSG/CL_VRP_LIB_BO_CLAIMASS.
In release SAP S/4HANA 2022, the following methods are renamed:
Class /MSG/CL_VRP_LIB_BO_CLAIM_DATA:
SET_OCLAIMHD_FROM_MCLAIMHD is renamed to
ASSIGN_MCLAIMHD_TO_OCLAIMHD
CHK_FIELD_CHANGE is renamed to RESET_CLAIM_HEADER_FIELDS
Class /MSG/CL_VRP_LIB_BO_CLAIM_ASS:
CREAT_OCLAIM_ASS is renamed to CREATE_OCLAIM_ASS
In Release SAP S/4HANA 2022, the following method parameters of the class
/MSG/CL_VRP_LIB_BO_CLAIM_DATA are adjusted:
Method ASSIGN_MCLAIMHD_TO_OCLAIMHD (formerly:
SET_OCLAIMHD_FROM_MCLAIMHD):
IMPORTING parameters (deleted):
IR_OINSPER
IR_MINSPER
IF_CHANGE
IF_NULLVAL
IT_NULLVAL
IF_NEW_CLAIMHD
EXPORTING parameters (deleted):
EF_CLAIM_DATE_IDENT
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1226
EO_MCLAIMHD
EF_UPDATED_CLAIM_HD
IMPORTING parameters (replaced):
IR_OPOL replaced by IO_OPOL
IR_OCLAIM replaced by IO_OCLAIM
IR_MCLAIM replaced by IO_MCLAIM
IR_PARENT_MESSAGE replaced by IO_PARENT_MESSAGE
CHANGING parameters (replaced):
CS_ALLOC (structure) is deleted. The following structure fields are
replaced by parameters:
CS_ALLOC-MR_OLIFE replaced by IMPORTING parameter
IO_OLIFE
CS_ALLOC-MF_NEW_CLAIM_HD replaced by
EXPORTING parameter EF_NEW_CLAIM_HD
CS_ALLOC-MR_OCLAIMHD replaced by EXPORTING
parameter EO_OCLAIMHD
IMPORTING parameters (new):
IT_OCLAIMHD (table with all operational claim headers of the
current life)
IO_MCLAIMHD (claim header of movement)
Method RESET_CLAIM_HEADER_FIELDS (previously:
CHK_FIELD_CHANGE):
IMPORTING parameters (deleted):
IR_OPOL
IR_OINSPER
IR_MINSPER
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1227
IR_OCLAIM
IR_MCLAIM
EXPORTING parameters (deleted):
EF_ASS_EXISTS
EF_FOLLOWING_CLAIM_MOV
ER_OCLAIMDEC
ER_OCLAIMASS
IMPORTING parameter (replaced):
IR_PARENT_MESSAGE replaced by IO_PARENT_MESSAGE
EXPORTING parameter (changed):
EF_CHANGE changed to RETURNING parameter
RF_CHANGE_ALLOWED
Method PROCESS_NEW_CLAIM
IMPORTING parameters (deleted):
IF_NO_ASSESSMENT
IT_CHECK
IMPORTING parameters (replaced):
IR_INSPER replaced by IO_OINSPER
IR_POLCOMP replaced by IO_OPOLCOMP
IR_MPOLCOMP replaced by IO_MPOLCOMP
IR_POL replaced by IO_OPOL
IR_CLAIMHD replaced by IO_OCLAIMHD
IR_MCLAIM replaced by IO_MCLAIM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1228
IR_PARENT_MESSAGE replaced by IO_PARENT_MESSAGE
Method CALC_CLAIMSHR_AMOUNTS
IMPORTING parameter (replaced)
IR_POL replaced by IO_OPOL
CHANGING parameter (replaced)
CO_CLAIM is replaced by IMPORTING parameter IO_OCLAIM.
Method CALC_CLAIM_FROM_CLAIMSHR
IMPORTING parameter (replaced)
IR_POL replaced by IO_OPOL
EXPORTING parameter (deleted)
EF_CLAIM_CALCULATED
CHANGING parameter (replaced)
CS_CLAIM_CH is replaced by IMPORTING parameter IO_OCLAIM
Method SET_CL_PROC_STATUS_IN_PROC
EXPORTING parameter (deleted)
EF_CLAIM_PROCESSED
CHANGING parameter (replaced)
CS_CLAIM is replaced by IMPORTING parameter IO_OCLAIM
Method DET_AMOUNT_ADMITTED
IMPORTING parameter (replaced)
IR_POL replaced by IO_OPOL
IR_PARENT_MESSAGE replaced by IO_PARENT_MESSAGE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1229
CHANGING parameter (deleted)
CF_CLAIM_PROCESSED
CHANGING parameter (replaced)
CS_CLAIM is replaced by IMPORTING parameter IO_OCLAIM
Method DET_CLAIM_AMOUNTS
CHANGING parameter (replaced)
CS_CLAIM is replaced by IMPORTING parameter IO_OCLAIM.
In Release SAP S/4HANA 2022, the following method parameters of the class
/MSG/CL_VRP_LIB_BO_CLAIM_ASS are adjusted:
Method CREATE_OCLAIM_ASS (previously: CREAT_OCLAIM_ASS)
IMPORTING parameter (replaced)
IR_OCLAIM replaced by IO_OCLAIM
IR_OPOL replaced by IO_OPOL
IMPORTING parameters (deleted)
IR_OCLAIMDEC
IR_OCLAIMHD
IF_CLAIMDEC_EXISTS
EXPORTING parameter (replaced)
EO_OCLAIMASS is replaced by RETURNING parameter
RO_OCLAIMASS.
Method REASS_OCLAIM_ASS
IMPORTING parameters (replaced)
IR_OCLAIM replaced by IO_OCLAIM
IR_OPOL replaced by IO_OPOL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1230
IT_OCLAIMDEC replaced by IO_OCLAIMDEC
IR_OCLAIMHD replaced by IO_OCLAIMHD
IMPORTING parameters (deleted)
IF_CLAIMDEC_EXISTS
Information related to the business process
The impact on business processes depends on how you use the deleted objects.
Required action(s)
Check whether you use the deleted objects specified in the object list and in this SAP
Note. If so, you must replace the deleted objects views.
To do this, replace the objects as described in the SAP Note text. If there is no
replacement, you will have to implement a replacement yourself if necessary.
Other Terms
Loss
53.14S4TWL - FS-RI – Replacement of old OA Accounting Reports
Application Components:FS-RI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3227549
S4TWL - FS-RI – replacement of old OA
accounting reports
Symptom
You perform an upgrade to SAP S/4HANA 2022.
Reason and Prerequisites
This SAP Note is relevant if you upgrade from a previous SAP S/4HANA version.
It is not relevant if you do not use any of the obsolete objects.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1231
Solution
Description
This version prepares various CDS views, the analytical queries based on them, and
the Fiori launchpad tiles of these queries for deletion.
The SAP Fiori launchpad tiles with the following titles are marked as obsolete and
removed from the groups:
Accounting Triangle Single Risk Non-Life
Accounting Triangle Treaty
Single Risk Statistics
Single Risk Statistics Ceded View Non-Life
Gross/Ceded/Net View Single Risk Non-Life
Gross/Ceded/Net View Treaty
Non-Finalized Accounts
Policy Statistics Non-Life
Loss Event Report
True Up
Comparison of Financial Periods
Treaty Statistics
A more recent version of the tiles was created and added to the groups.
Information related to the business process
The impact on business processes depends on the use of the obsolete objects.
Required and recommended action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1232
Check whether you used the obsolete objects. If this is the case, you must
replace them with the newly created objects.
53.15S4TWL - FS-RI - Interface adaption of the navigation tree
Application Components:XX-PART-MSG-LRM, FS-RI-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3225429
Transition to SAP S/4HANA - FS-RI -
interface adjustment in navigation tree
Symptom
You are performing a system conversion to SAP S/4HANA 2022.
Reason and Prerequisites
This SAP Note is relevant if your source release for the system conversion is an ERP
release or an SAP S/4HANA release up to and including SAP S/4 HANA 2021.
It is not relevant if your source release is SAP S/4HANA Finance.
Solution
Description
Methods were adjusted in Release SAP S/4HANA 2022:
Class /MSG/CL_VRB_DT_MGR
The following methods have been renamed:
create_tree_mpol_new becomes create_tree_mpol
create_tree_node_new becomes create_tree_node
create_tree_oapp_new becomes create_tree_oapp
create_tree_olife_new becomes create_tree_olife
make_tree_by_ref_new becomes make_tree_by_ref
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1233
start_op_new becomes start_op
mpol_new becomes mpol
oappl_new becomes oappl
olife_new becomes olife
opol_new becomes opol
Class /MSG/CL_VRB_RDF_CONTAINER
The FILL method has been deleted.
The method FILL_NEW has been renamed FILL.
Information related to the business process
The impact on business processes depends on how you use the deleted/renamed objects.
Required and recommended action(s)
Check whether you use the deleted/renamed objects specified in the object list and in this
SAP Note. If so, you must replace the deleted/renamed objects.
To do this, replace the objects as described in the SAP Note text. If there is no
replacement, you will have to implement a replacement yourself if necessary.
Other Terms
Navigation tree
53.16S4TWL - FS-RI – Deprecation of RAM APIs with SAP S/4HANA 2022
Application Components:FS-RI-RAM, XX-PART-MSG-RAM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3260792
S4TWL - FS-RI - Announcement of
deletion of obsolete RAM APIs
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1234
You want to perform a system conversion from EHP7 FOR SAP ERP 6.0 - 06 (10/2014)
or higher, or a release upgrade from SAP S/4HANA 1709, SAP S/4HANA 1809, SAP
S/4HANA 1909, SAP S/4HANA 2020, or SAP S/4HANA 2021 to SAP S/4HANA 2022
or higher.
Reason and Prerequisites
This SAP Note is relevant if your current release is EHP7 FOR SAP ERP 6.0 - 06
(10/2014) or higher, SAP S/4HANA 1709, SAP S/4HANA 1809, SAP S/4HANA
1909, SAP S/4HANA 2020, or SAP S/4HANA 2021.
It is not relevant if you do not use any of the obsolete objects.
Solution
Description
The following function modules are deprecated with SAP S/4HANA 2022.
/MRA/A2A_IR_P_CONFIRM
/MRA/A2X_IR_P_CHK_COVERAGE
/MRA/A2X_IR_P_CONFIRM
/MRA/A2X_IR_P_ALLOC_PRECESSION
/MRA/A2X_RR_P_CHK_COVERAGE
/MRA/A2X_RR_P_CONFIRM
/MRA/A2X_RR_M_PRECESSION_V2
/MRA/A2X_RR_F_BY_ELEMENTS_V2
Information related to the business process
If your target release is SAP S/4HANA 2022, using the obsolete function modules has no
effect for the time being. However, we recommend that you start using the replacing
function modules as soon as possible.
Required and recommended action(s)
Check whether you used the obsolete objects. If this is the case, you must replace them
with the newly created objects.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1235
/MRA/A2A_IR_P_CONFIRM is replaced by /MRA/A2A_IR_P_CONFIRM_V2
/MRA/A2X_IR_P_CHK_COVERAGE is replaced
by /MRA/A2X_IR_P_CHK_COVERAGE_V2
/MRA/A2X_IR_P_CONFIRM is replaced by /MRA/A2X_IR_P_CONFIRM_V2
/MRA/A2X_IR_P_ALLOC_PRECESSION is replaced by
/MRA/A2X_IR_P_ALLOC_PRECES_V2
/MRA/A2X_RR_P_CHK_COVERAGE is replaced
by /MRA/A2X_RR_P_CHK_COVERAGE_V2
/MRA/A2X_RR_P_CONFIRM is replaced by /MRA/A2X_RR_P_CONFIRM_V2
/MRA/A2X_RR_M_PRECESSION_V2 is replaced by
/MRA/A2X_RR_M_PRECESSION_V3
/MRA/A2X_RR_F_BY_ELEMENTS_V2 is replaced by
/MRA/A2X_RR_F_BY_ELEMENTS_V3
Other Terms
Risk Aggregation Management (RAM)
/MRA/A2A_IR_P_CONFIRM
/MRA/A2X_IR_P_CHK_COVERAGE
/MRA/A2X_IR_P_CONFIRM
/MRA/A2X_IR_P_ALLOC_PRECESSION
/MRA/A2X_RR_P_CHK_COVERAGE
/MRA/A2X_RR_P_CONFIRM
/MRA/A2X_RR_M_PRECESSION_V2
/MRA/A2X_RR_F_BY_ELEMENTS_V2
53.17S4TWL - FS-RI - Correction of misleading method names
Application Components:FS-RI-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3310949
Transition to SAP S/4HANA - FS-RI:
correction of misleading method names
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1236
Symptom
You are performing a system conversion to SAP S/4HANA 2023.
Reason and Prerequisites
This SAP Note is relevant if your source release for the system conversion is an ERP
release or an SAP S/4HANA release up to and including SAP S/4 HANA 2022.
It is not relevant if your source release is SAP S/4HANA Finance.
Solution
Description
The following methods were adjusted in Release SAP S/4HANA 2023:
Class /MSG/CL_VF_DP_RULESET_POLICY
allowed_movement_status wird forbidden_movement_status
The following parameters were adjusted in Release SAP S/4HANA 2023:
Class /MSG/CL_VF_DP_UNUSED_OBJECTS
Method restrictions
et_allowed_status wird et_allowed_pc_status
et_mov_status wird et_forbidden_mov_status
Information related to the business process
The impact on business processes depends on how you use the renamed objects.
Required and recommended action(s)
Check whether you are using the renamed objects specified in the object list and in this
SAP Note. If so, you must replace the renamed objects.
To do this, replace the objects as described in the SAP Note text.
Other Terms
Anonymization
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1237
53.18S4TWL - FS-RI - Deprecation of RAM APIs with SAP S/4HANA 2023
Application Components:XX-PART-MSG-RAM, FS-RI-RAM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3385743
S4TWL - FS-RI - Announcement of
deletion of obsolete RAM APIs
Symptom
You want to perform a system conversion from EHP7 FOR SAP ERP 6.0 - 06 (10/2014)
or higher, or a release upgrade from SAP S/4HANA 1709, SAP S/4HANA 1809, SAP
S/4HANA 1909, SAP S/4HANA 2020, SAP S/4HANA 2021, or SAP S/4HANA 2022 to
SAP S/4HANA 2023 or higher.
Reason and Prerequisites
This SAP Note is relevant if your current release is EHP7 FOR SAP ERP 6.0 - 06
(10/2014) or higher, SAP S/4HANA 1709, SAP S/4HANA 1809, SAP S/4HANA
1909, SAP S/4HANA 2020, SAP S/4HANA 2021, or SAP S/4HANA 2022.
It is not relevant to you if you do not use any of the obsolete objects.
Solution
Description
The following function modules are deprecated with SAP S/4HANA 2023.
/MRA/A2X_IR_P_ALLOC_PRECES_V2
/MRA/A2X_IR_P_AL_PRECES_REF
/MRA/A2X_RR_M_PRECESSION_V3
Information related to the business process
If your target release is SAP S/4HANA 2023, using the obsolete function modules has no
effect for the time being. However, we recommend that you start using the replacement
function modules as soon as possible.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1238
Required and recommended action(s)
Check whether you used the obsolete objects. If this is the case, you must replace them
with the newly created objects.
/MRA/A2X_IR_P_ALLOC_PRECES_V2 is replaced
by /MRA/A2X_IR_P_ALLOC_PRECESGRP
/MRA/A2X_IR_P_AL_PRECES_REF is replaced
by /MRA/A2X_IR_P_ALLOC_PRECESGRP
/MRA/A2X_RR_M_PRECESSION_V3 is replaced
by /MRA/A2X_RR_M_PRECESSION_V4
Other Terms
Risk Aggregation Management (RAM)
/MRA/A2X_IR_P_ALLOC_PRECES_V2
/MRA/A2X_IR_P_AL_PRECES_REF
/MRA/A2X_RR_M_PRECESSION_V3
53.19S4TWL - FS-RI – Changing “Remote-Enabled Module” to “Normal
Function Module”
Application Components:FS-RI-LRM, FS-RI-ES, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3400287
Übergang nach SAP S/4HANA - FS-RI -
Ändern eines Bausteins von "Remote
fähiger Baustein" auf "Normaler
Funktionsbaustein"
Symptom
Sie führen eine Systemkonvertierung nach SAP S/4HANA 2022 FPS02 oder höher
durch.
Ursache und Voraussetzungen
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1239
Dieser SAP-Hinweis ist für Sie relevant, wenn Ihr Ausgangsrelease für die
Systemkonvertierung ein ERP-Release oder ein SAP S/4HANA-Release bis
einschließlich SAP S/4HANA 2022 FPS01 ist.
Er ist nicht relevant, wenn Ihr Ausgangsrelease SAP S/4HANA Finance ist.
Lösung
Beschreibung
Im Release SAP S/4HANA 2022 FPS02 wurde der Ablauftyp von folgendem
Funktionsmodul im Extension Service angepasst:
Funktionsgruppe /MSG/2_EXTSRVC_TOOLS
Funktionsmodul /MSG/2_EXTSRVC_TOOLS
Ablauftyp "Remote fähiger Baustein" wurde auf "Normaler
Funktionsbaustein" geändert
Sollten Sie den Baustein per Remoteaufruf verwenden, muss dieser ersetzt werden.
Geschäftsprozessbezogene Informationen
Die Auswirkungen auf die Geschäftsprozesse hängen von der Verwendung der
geänderten Objekte ab.
Erforderliche und empfohlene Aktion(en)
Überprüfen Sie, ob die geänderten Objekte, die in der Stückliste und in diesem Hinweis
angegeben sind, verwendet werden. Falls ja, müssen Sie die geänderten Objekte ersetzen.
Hierzu ersetzen Sie die Objekte wie im Hinweistext beschrieben.
Weitere Begriffe
RFC
ES
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1240
53.20S4TWL - FS-RI - Renaming of a field in PMQ
Application Components:FS-RI-LRM, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3399310
Übergang nach SAP S/4HANA - FS-RI -
Umbenennung eines Feldes im PMQ
Symptom
Sie führen eine Systemkonvertierung nach SAP S/4HANA 2022 FPS02 oder höher
durch.
Ursache und Voraussetzungen
Dieser SAP-Hinweis ist für Sie relevant, wenn Ihr Ausgangsrelease für die
Systemkonvertierung ein ERP-Release oder ein SAP S/4HANA-Release bis
einschließlich SAP S/4 HANA 2022 FPS01 ist.
Er ist nicht relevant, wenn Ihr Ausgangsrelease SAP S/4HANA Finance ist.
Lösung
Beschreibung
Im Release SAP S/4HANA 2022 FPS02 wurden folgende View-Einträge angepasst, da
eine glechnamige Funktion eing4eführt wurde wodurch es zu Problemen kommt:
View /MSG/4P_TABLEFLD
Zeile mit Eintrag für Tabellenname /MSG/VDOESC und Feldname
ESC_ROUND: Merkmal "Round" umbenannt in "Rounding_Factor"
Geschäftsprozessbezogene Informationen
Die Auswirkungen auf die Geschäftsprozesse hängen von der Verwendung der
umbenannten Objekte ab.
Erforderliche und empfohlene Aktion(en)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1241
Überprüfen Sie, ob die umbenannten Objekte, die in der Stückliste und in diesem
Hinweis angegeben sind, verwendet werden. Falls ja, müssen Sie die umbenannten
Objekte ersetzen.
Hierzu ersetzen Sie die Objekte wie im Hinweistext beschrieben.
Weitere Begriffe
PM, PMQ
53.21S4TWL - FS-RI - Deletion of obsolete Claim Methods
Application Components:FS-RI-LRM, XX-PART-MSG-LRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3105510
Transition to SAP S/4HANA - FS-RI -
deletion of obsolete claim methods
Symptom
You are performing a system conversion to SAP S/4HANA 2021.
Reason and Prerequisites
This SAP Note is relevant if your source release for the system conversion is an ERP
release or an SAP S/4HANA release up to and including SAP S/4 HANA 2020.
It is not relevant if your source release is SAP S/4HANA Finance.
Solution
Description
In the Release SAP S/4HANA 2021, the following methods are deleted and no longer
available:
Class /MSG/CL_VRP_LIB_BO_CLAIM_MOV:
calc_claim_amounts
calc_claimshr_amounts
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1242
check_payment_request
chk_fields_claim
chk_fields_claimshr
Class /MSG/CL_VRP_LIB_BO_CLAIM_DATA:
chk_fields_claim
check_claim_amounts
check_claimshare_amounts
chk_fields_claim_amounts
chk_fields_claim_amounts_ca
Class /MSG/CL_VRP_LIB_CLAIM_SHARE:
set_claimshare_data
Class /MSG/CL_VRC_SC_CA_DECTAB_ALV:
set_claim_decisions
Information related to the business process
The impact on business processes depends on how you use the deleted objects.
Required action(s)
Check whether you use the deleted objects specified in the object list and in this SAP
Note. If so, you must replace the deleted objects views.
No replacement is provided for the deleted objects.
Other Terms
Loss
Distribution of claim amounts
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1243
53.22S4TWL - Insurance localization for Russia - deprecation
Application Components:FS-CM-LC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2978033
S4TWL - RU insurance localization -
deprecation of package /GSINS/RU
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this Note. The following SAP S/4HANA Simplification Item is applicable in this case.
Reason and Prerequisites
Insurance Localization FS-CM for Russia installed.
Solution
Description
Package /GSINS/RU and it contents becomes obsolete because of no customer usage.
Objects stored in the package and corresponding subpackages are removed including
their references from other objects.
Business Process related information
Insurance localization for Russia stored in the package /GSINS/RU and it's subpackages
is not being used and has been deprecated in S/4HANA OP2021 and became obsolete in
all the supported lower versions.
Regarding S/4HANA OP2021 release, for transition period of 2 years the package and it's
subpackages has been moved to SW component 'S4DEPREC' if the restoration of the
functionality is needed.
Note content:
1) Existing references in objects ('Ref. Object Name') pointing to the objects in the
package /GSINS/RU and it's subpackages were removed:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1244
Object Name
Package
Applicati
on Area
Software
Compone
nt
Inf
o
Ref.
Obje
ct
Type
Ref. Object Name
/GSINS/CL_CHECK
_EHP
/GSINS/R
EU
FS-CM-
LC
INSURAN
CE
use
d
by
ENH
O
/GSINS/CL_FSCM_LOC_T
R_605
2) Following programs contained in subpackages of main package /GSINS/RU
were deactivated, cannot be executed:
Program
Transaction
Description
/CEEIS/RU_FSCD_RI_DEBTS
/CEEIS/RU_F10_23
FS-CD: Form 10,
Appendix 1,
Rep.: 2.3, 3.3
Reinsurance
operations
/CEEIS/RU_F10_33
/CEEIS/RU_FSCD_RI_PAYM
/CEEIS/RU_F10_21
FS-CD: Form 10,
Appendix 1,
Rep.: 2.1, 3.1 -
Reinsurance
operations
/CEEIS/RU_F10_31
/CEEIS/RU_FSCD_RI_RISPA
/CEEIS/RU_F10_22
FS-CD: Form 10,
Appendix 1,
Rep.: 2.2, 3.2 -
Reinsurance
operations.
/CEEIS/RU_F10_32
/GSINS/CLAIM_REP_PRINT
/GSINS/CLAIMREP
Claim Report
(Russia)
/GSINS/DTINF_ADJ_8755CE1E62E67
N/A
/GSINS/MTPL_ARCHIVE_DELETE
N/A
Archiving of
MTPL: Delete
(Russia)
/GSINS/MTPL_ARCHIVE_WRITE
N/A
Archiving of
MTPL: Write
(Russia)
/GSINS/MTPL_COMPOSE_SEGMENT3
/GSINS/MTPL_SEGMENT3
Segment Three
(Russia)
/GSINS/OLR_ARCHIVE_DELETE
N/A
Archiving of
Open Loss
Reserves: Delete
(Russia)
/GSINS/OLR_ARCHIVE_WRITE
N/A
Archiving of
Open Loss
Reserves: Write
(Russia)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1245
/GSINS/OLR_CREATE_PTERM
/GSINS/PTERM_CREATE
Create Insurance
Premiums
(Russia)
/GSINS/OLR_DISPLAY_PTERM
/GSINS/PTERM_DISPLAY
Display
Insurance
Premiums
(Russia)
/GSINS/OLR_RESERVE_CALC
/GSINS/RESERVE_CALC
Reserve
Calculation of
Claimed but
Unsettled Losses
(Russia)
/GSINS/REU_RETRACT
/GSINS/REU_RTR
Reserves of
Russia posting
/GSINS/RUAC_AAAI_INSTALL
/GSINS/RUAC_AAAI_INS
Additional
Account
Assignment
Installation
(Russia)
/GSINS/UPR_ARCHIVE_DELETE
N/A
Archiving of UPR
(Unearned
Premium
Reserve): Delete
/GSINS/UPR_ARCHIVE_WRITE
N/A
Archiving of UPR
(Unearned
Premium
Reserve): Write
/GSINS/UPR_DISP
/GSINS/UPR_DISP
Unearned
Premium
Reserve
Calculation
Results (Russia)
3) Following transactions were set as obsolete in SU22 transaction, so these cannot be
executed:
Transaction
Description
/CEEIS/RU_F1
F1.: Balance
/CEEIS/RU_F10_1
F10.p1.: Reinsurance operations
/CEEIS/RU_F10_21
F10.p2.1.: Reinsurer's Premiums
/CEEIS/RU_F10_22
F10.p2.2.: Reinsurer's Payments
/CEEIS/RU_F10_23
F10.p2.3.: Reinsurer's Liabilities
/CEEIS/RU_F10_31
F10.p3.1.: Cedent's Premiums
/CEEIS/RU_F10_32
F10.p3.2.: Cedent's Payments
/CEEIS/RU_F10_33
F10.p3.3.: Cedent's Liabilities
/CEEIS/RU_F11
F11.: Info about operational segment
/CEEIS/RU_F2
F2.: Profits and Losses
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1246
/CEEIS/RU_F2_SP
F2.: Profits and Losses; Appendix
/CEEIS/RU_F3_1
F3.p1.: Capital changes
/CEEIS/RU_F3_2
F3.p2.: Reserves
/CEEIS/RU_F3_3
F3.: Reference
/CEEIS/RU_F3_NA
F3.: Net assets value calculation
/CEEIS/RU_F5_3
F5.p3.: Financial investments
/CEEIS/RU_F5_4
F5.p4.: Payables and receivables
/CEEIS/RU_F5_5
F5.p5.: Expences
/CEEIS/RU_F6_1
F6.p1.: Solvency margin of insurer
/CEEIS/RU_F6_2
F6.p2.: Solvency margin of insurer
/CEEIS/RU_F7_1
F7.p1.: Insuran. reserves investment
/CEEIS/RU_F8_1
F8.p1.: Insurance reserves
/CEEIS/RU_F8_2
F8.p2.: Insurance reserves
/CEEIS/RU_F8_2_131
F8.p2.: Insurance reserves; A.g.13.1
/CEEIS/RU_F8_2_131A
F8.p2.: Insur.reserves A.g.13.1.Apdx
/CEEIS/RU_F8_2A
F8.p2.: Insurance reserves Append.
/CEEIS/RU_F9_1
F9.p1.: PMR
/CEEIS/RU_F9_2
F9.p2.: PMR
/GSINS/08000983
/GSINS/08000985
/GSINS/08000986
/GSINS/57000001
/GSINS/57000003
/GSINS/57000005
/GSINS/57000006
/GSINS/57000007
/GSINS/57000008
/GSINS/57000009
/GSINS/57000010
/GSINS/57000011
/GSINS/57000012
/GSINS/57000013
/GSINS/57000014
/GSINS/57000015
/GSINS/CLAIMREP
Print claim report
/GSINS/MTPL_SEGMENT3
Composing of segment 3
/GSINS/OLR
Define Res. Period for OLR
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1247
/GSINS/PTERM_CREATE
Create Insurance Premium
/GSINS/PTERM_DISPLAY
Display Insurance Premium
/GSINS/RESERVE_CALC
Reserve Calculation of Losses
/GSINS/REU_ACCGFI
Selection rules of FI tables content
/GSINS/REU_ETL
Insurance ETL customizing
/GSINS/REU_RST
Retraction customizing
/GSINS/REU_RTR
Reserve to FI retraction
/GSINS/RUAC_AAAI_INS
Additional Account Assignment Instal
/GSINS/RUAC_AC_GR
Maintain Customer Accounting Groups
/GSINS/UPR_CALC
Calculations for Company Codes
/GSINS/UPR_CHARG
Charges - Percentage
/GSINS/UPR_DISP
Display Calculated Results
/GSINS/UPR_FCALC
Calculations Methods
/GSINS/UPR_HKONT
Allowed General Ledger Accounts
/GSINS/UPR_UFUN
Function Module for User Exits
Required and Recommended Action(s)
In general, SAP recommends that you install a solution by applying a Support Package.
You can find more information about the Note Assistant in SAP Service Marketplace,
under service.sap.com/note-assistant.
However, if you need to install a solution earlier, use the Note Assistant to implement
and follow these steps:
IMPORTANT:
To complete the installation procedure for S4TWL - RU insurance localization -
deprecation of package /GSINS/RU you have to implement the automatic correction
instructions from this Note 2978033.
Remember, that you cannot use your own coding/functionality anymore which is based
on the removed coding/functionality, explained in this Note 2978033.
Other Terms
Russia, Insurance, /GSINS/RU, S4DEPREC, deprecation, obsolete
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1248
53.23S4TWL - Insurance localization for Turkey
Application Components:FS-CM-LC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3164537
S4TWL - TR insurance localization -
deprecation of package /GSINS/TR
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this Note.
The following SAP S/4HANA Simplification Item SI8: GSFIN_Insurance_TR is
applicable in this case.
Reason and Prerequisites
Prerequisite: Insurance Localization FS-CM for Turkey installed.
Reason for deprecation:
TRAMER functionality could be used to export automotive insurance related
information in a specific format as XML in order to submit it to authorities in
Turkey.
the functionality is not usable anymore without customer modification, as the export
format defined by the Turkish government has changed since initial delivery of
the functionality, but it was never adapted to the new format.
hence today customers already use other means to export this data from the system in
the required format (eg. export to external text file and perform mapping to a
suitable XML format with XSLT or via 3
rd
party, own code…).
Solution
Description
Package /GSINS/TR and it contents becomes obsolete because of no customer usage.
Objects stored in the package and corresponding subpackages are removed including
their references from other objects.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1249
TRAMER functionality has already been put on the blocklist and hence will not be usable
anymore without intervention in S/4HANA OP2022 release.
Business Process related information
Insurance localization for Turkey stored in the package /GSINS/TR and it's subpackages
is not being used and has been deprecated in S/4HANA OP2022 and became obsolete in
all the supported lower versions.
Regarding S/4HANA OP2022 release, for transition period of 2 years the package and it's
subpackages has been moved to SW component 'S4DEPREC' if the restoration of the
functionality is needed.
Note content:
1) Existing references in objects ('Ref. Object Name') pointing to the objects in the
package /GSINS/TR and it's subpackages were removed:
Object Name
Package
Applicati
on Area
Software
Compone
nt
Inf
o
Ref.
Obje
ct
Type
Ref. Object
Name
/GSINS/TR_CL_SWITCH_C
HECK
/GSINS/TR_R
EU
FS-CM-
LC
INSURAN
CE
use
d
by
REP
S
LICL_MINI_BP
F04
2) Following transactions were set as obsolete in SU22 transaction, so these cannot be
executed:
Transaction
Description
/GSINS/77000006
Define Transformation Definitions
/GSINS/77000007
Assign Internal Claim Types to TRAMER
Transformation
/GSINS/77000008
obsolete
/GSINS/77000009
BAdI: XML Structure Modification for
Transformation KASKO
/GSINS/77000010
BAdI: XML Structure Modification for
Transformation TRAFIK
/GSINS/TR_TRAMER
XML File Generation TRAMER Reporting
Required and Recommended Action(s)
In general, SAP recommends that you install a solution by applying a Support Package.
You can find more information about the Note Assistant in SAP Service Marketplace,
under service.sap.com/note-assistant.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1250
However, if you need to install a solution earlier, use the Note Assistant to implement
and follow these steps:
IMPORTANT:
To complete the installation procedure for S4TWL - TR insurance localization -
deprecation of package /GSINS/TR you have to implement the automatic correction
instructions from this Note 3164537.
Remember, that you cannot use your own coding/functionality anymore which is based
on the removed coding/functionality, explained in this Note 3164537.
Other Terms
Turkey, Insurance, /GSINS/TR, S4DEPREC, deprecation, obsolete
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1251
54.Industry Media
54.1 S4TWL - SAP Media availability in SAP S/4HANA
Application Components:IS-M
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2506999
S4TWL - Industry Solution SAP Media
and SAP S/4HANA
Symptom
You are planning a system conversion to SAP S/4HANA, on Premise Edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
The industry solution SAP Media is not available in SAP S/4HANA, on-premise edition.
None of the media-specific SAP-GUI transactions is released and must not be used in
SAP S/4HANA.
Solution
Customers using the Media Product Master in ERP and no additional functions of the
industry solution SAP Media can use comparable functions in SAP S/4HANA core. The
respective functions are available with SAP S/4HANA, on Premise Edition 1709. See
SAP Note 2499057.
How to determine relevancy
Your start release for the system conversion is an ERP release and has at least one
business function of the industry business function set Media active.
Customers using additional media-specific functions have the following options:
- run SAP Media on a SAP Business Suite on HANA release (if you want to use SAP
HANA as a database for the SAP Business Suite and / or you want to benefit from the
improved functionality of SAP S/4HANA FINANCE Add-on).
- run SAP S/4HANA without SAP Media as separate installation.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1252
Other Terms
SAP Media, Media Product Master
54.2 S4TWL - Media Product Master
Application Components:CA-MDG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2499057
S4TWL - Media Product Master and
SAP S/4HANA
Symptom
You are planning a system conversion to SAP S/4HANA, on Premise Edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
The industry solution SAP Media is not available in SAP S/4HANA, on premise edition.
Solution
Customers using the Media Product Master in ERP and no additional functions of the
industry solution SAP Media can use comparable functions in SAP S/4HANA core. The
respective functions are available with SAP S/4HANA, on Premise Edition 1709.
Business Process related information
Maintain logical hierarchies of media products, such as multiple editions under a
parent title or multiple episodes under a parent series. The number of hierarchy
levels can be defined as needed.
Media-specific and custom fields which were stored in an industry-specific append of
table MARA in ERP can be defined using the field extensibility tool of SAP
FIORI.
The standard FIORI apps of the Product Master can be used to maintain the Media
Product Masters themselves and relationships between Media Product Masters.
The industry-specific SAP GUI transactions are no longer available.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1253
The assignment of business partners to Media Product Masters is not supported in
SAP S/4HANA.
Required and recommended actions
For required actions follow the instructions given in the conversion documentation
attached to SAP Note 2499057.
How to determine relevancy
The business function TITLE LIFECYCLE MANAGEMENT of the industry business
function set Media is active and you have created media product master records.
Other Terms
SAP Media, IS Media, Media Product Master, System Conversion, Industry Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1254
55.Industry Oil
55.1 S4TWL- ACM - Simplification for Contract Approval
Application Components:LO-AGR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2468737
Business Impact Note for S4TWL -
Changes in ACM (Agricultural Contract
Management) Functionality
Symptom
You are doing a system conversion of ACM (Agricultural Contract Management)
from SAP ERP EHP6 or higher to SAP S/4 HANA on-Premise edition. The
following SAP S/4HANA business impact note is applicable in this case.
Reason and Prerequisites
For ACM, Contract Approval and certain other functionality in other modules like
Orchestration Framework, Application Menu and settlement won’t work seamlessly
when accessed from SAP GUI or SAP Fiori launchpad. Functionalities like
Prepayment and External Interfacing are obsolete and no longer available in
ACM on S/4HANA.
Several other functionalities available in the ACM (SAP ERP EHP6 or higher)
ADDON are on the roadmap for the future releases of ACM on S/4HANA.
Solution
In SAP S/4HANA for ACM some applications are not available anymore or changed.
1. Contract approval tab deprecated-
The contract “Approval” tab in the trading contract has now been removed.
The status of contracts is now being managed from GTM Status Management as below:
Select Status from available ‘Application Status’ under Status Tab
Click on ‘Set Status’ button to apply the selected status
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1255
2. Configuration for GTM contract status-
The complete GTM contract status management has to be set up as below:
SAP Customizing Implementation Guide -> Logistics – General -> Global Trade
Management -> Trading Contract -> Define Application Status and Status Groups
a. Create new entries for Status Group.
Status Group
Description
N
ACM Contract Status Group
b. Define Status for Status Group – Select a status from the “Status Groups” list and
maintain the application status.
App. Status
Status Name
Workflow Event
Event Trigger
Default Status Type
O
Ready for Archiving
On Saving
No Default Status
T
Approved
On Saving
No Default Status
U
Draft
On Saving
No Default Status
c. Assign Status group to Contract Type
SAP Customizing Implementation Guide -> Logistics – General -> Global Trade
Management -> Trading Contract -> Define Trading Contract Types
Double click on contract type and assign status group maintained above.
3. Configuration for mapping contract status to call-off and position relevance- SAP
Customizing Implementation Guide -> Logistics – General -> Global Trade Management
-> Agricultural Contract Management -> Basic Settings -> Maintain Contract Status
Categories
App Status
Status Category
Position Relevant
Snap. Relevant
App. Status Name
T
Call-Off/Application Relevant
X
Approved
4. During system conversion, contracts status management relevant changes, for the
contracts which were created in ECC, will be handled automatically when the ACM
XPRA: /ACCGO/XPRA_CAKHDR is executed.
Contracts with the approval indicator set would be converted as follows:
The field ‘BTBSTA’ of WBHK would be changed to ‘T’.
Required and Recommended Action(s): Adjust customer specific coding accordingly.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1256
Run the steps mentioned in SAP notes 2481713.
If you are converting from ACM ECC (with IS-OIL OFF) to ACM on S/4 HANA OP
1709 FP00 (software component, IS-OIL) please run the steps mentioned in note
2481873.
Other Terms
IS-OIL, ACM, Agricultural Contract Management, upgrade, S/4HANA OnPrem, system
conversion
55.2 S4TWL- ACM: Simplification for Pre-payment and External
Interfacing
Application Components:LO-AGR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2468819
Business Impact Note for S4TWL- ACM:
Simplification for Pre-payment and
External Interfacing
Symptom
You are doing a system conversion of ACM (Agricultural Contract Management)
from SAP ERP EHP6 or higher (ACCGO 100, ACCGO 300) to SAP S/4 HANA
on-Premise edition 1709 FP00
Reason and Prerequisites
Certain ACM functionalities in ACM (SAP ERP EHP6 or higher - ACCGO 100,
ACCGO 300) ADDON won't work seemlessly in S/4HANA 1709 FP00 when accessed
fromSAP GUI or SAP Fiori launchpad.
Solution
Recommended Action: Run the steps mentioned in business impact note 2468737 -
Business Impact Note for S4TWL - Changes in ACM (Agricultural Contract
Management) Functionality
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1257
IS-OIL, ACM, Agricultural Contract Management, upgrade, S/4HANA OnPrem 1709
FP00, system conversion
55.3 S4TWL - ACM: Simplification of Cross Topics
Application Components:LO-AGR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2468833
Business Impact Note for S4TWL -
ACM: Simplification of Cross Topics
Symptom
You are doing a system conversion of ACM (Agricultural Contract
Management) from SAP ERP EHP6 or higher (ACCGO 100, ACCGO 300) to
SAP S/4 HANA on-Premise edition 1709 FP00.
Reason and Prerequisites
Certain ACM functionalities in ACM (SAP ERP EHP6 or higher - ACCGO 100,
ACCGO 300) ADDON won't work seamlessly in S/4HANA 1709 FP00 when accessed
from SAP GUI or SAP Fiori launchpad.
Solution
Recomended Action: Run the steps mentioned in business note 2468737 - Business
Impact Note for S4TWL - Changes in ACM (Agricultural Contract Management)
Functionality.
Other Terms
IS-OIL, ACM, Agricultural Contract Management, upgrade, S/4HANA OnPrem 1709
FP00, system conversion
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1258
55.4 S4TWL - ACM: Simplification of Application Document Batch Split
Process
Application Components:LO-AGR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3017200
S4TWL - ACM: Simplification of
Application Document Batch Split
Process
Symptom
You are doing a system conversion of ACM (Agricultural Contract Management) from
SAP ECC(ACCGO 400) to SAP S/4HANA on-premise edition 2020 FPS01 or a higher
release.
Reason and Prerequisites
Application document process changed with respect to batch managed material
Going forward from the S4HANA release 2020 FPS01 the Application document will not
be split on the basis of the batches mentioned on the Load Data Capture(LDC) if Feature
switch (MERGE_APP)( Logistics - General under Global Trade Management ->
Agricultural Contract Management -> Basic Settings -> Activate Feature Switches.)
is checked.
Solution
Recommended action:Its recommended to check all the active application documents
which have been split due to more than one batch on the LDC and complete those
transactions before performing the converison to S4HANA 2020 FPS01 or higher release.
If already converted to Higher release Activate the feature switch Feature switch
(MERGE_APP)( Logistics - General under Global Trade Management -
> Agricultural Contract Management -> Basic Settings -> Activate Feature
Switches.) then use the transaction code /ACCGO/ACM_BSPL_CORR to correct the
Application document by performing the Correction of the Same LDC Document and
form the New sets of the logistics document.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1259
IS-OIL, ACM, Agricultural Contract Management, upgrade, S/4HANA OnPrem 2020
FPS01, system conversion
55.5 S4TWL - ACM Temporary Lots for Draft Contracts
Application Components:LO-AGR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3086524
S4TWL - ACM Temporary Lots for Draft
Contracts
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
A system upgrade/conversion is about to be done and the source system is one of the
following releases: -
ACM 4.0
ACM on SAP S/4HANA 1709 - All releases
ACM on SAP S/4HANA 1809 - FPS00
ACM on SAP S/4HANA 1809 - FPS01
ACM on SAP S/4HANA 1809 - FPS02
ACM on SAP S/4HANA 1909 - FPS00
ACM on SAP S/4HANA 1909 - FPS01
ACM on SAP S/4HANA 1909 - FPS02
ACM on SAP S/4HANA 2020 - FPS00
The target system is 'ACM on SAP S/4HANA 2020 FPS01' or a higher release.
Post-conversion/upgrade, dumps occurs because of the existence of multiple active BAdI
implementations of the BAdI definition
BADI_CPE_FE_RED_DATE_ROUTINE for the same filter value '9999999'. This prevents execution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1260
of various ACM transactions
and prevents successful execution of the SDM /ACCGO/CL_SDM_ACM_V_SDMNPEL.
Important Note: -
The manual instruction in this note must only be implemented after all the productive
activities in the system have been
halted in preparation for the conversion/upgrade.
The transport-request in which the implementation of this note is captured must be
released to all follow-on systems to
prevent occurence of this issue in those systems.
Reason and Prerequisites
This step is needed to prevent the occurrence of dumps because of the existence of
multiple BAdI implementations of the BAdI definition
BADI_CPE_FE_REF_DATE_ROUTINE for the same filter value '9999999'.
Solution
Required and Recommended Action(s)
Run the steps mentioned in SAP Note - 3094714- S4TC ACM Pre-Checks for Data
Migration of /ACCGO/T_NPELOTS table in the source system
The manual instruction in this note must only be implemented after all the productive
activities in the system have been
halted in preparation for the conversion/upgrade.
The transport-request in which the implementation of this note is captured must be
released to all follow-on systems to
prevent occurence of this issue in those systems.
Please implement the manual correction instructions attached to this note.
Other Terms
Pre-upgrade/conversion step for upgrade/conversion to ACM on S/4HANA 2021 FPS01
or higher releases
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1261
55.6 S4TWL - Handling Oil & Gas obsolete t-codes Oil
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328674
S4TWL: OIL Transaction codes will not
be available.
Symptom
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.
Reason and Prerequisites
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.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1262
Obsolete Transaction code
Older Transaction Code
Successor Tcode
O300
IS-Oil Administration info system
SE43
O3C1
Create Oil Conversion Defaults
O3DEFAULTS
O3C2
Change Oil Conversion Defaults
O3DEFAULTS
O4KC
Revaluation active check report 2/2
No Replacement available
O4KE
Excise Duty Valuation record 2/3
No Replacement available
O4KG
Excise Duty Stock values 2/3
No Replacement available
O4KH
Excise Duty Stock values 3/3
No Replacement available
O4KI
Excise Duty Valuation record 3/3
No Replacement available
O4NC
Create Nomination
O4NCN/O4NM
O4NS
Display Nomination
O4NSN/O4NM
O4NV
Change Nomination
O4NM
O4T0
IS-OIL TSW (Trader's & Scheduler's W
No Replacement available
O4TC
Generate Stock Projection
O4TCN
O4TCB
Generate Stock Projection for batch
O4TCN
O4TDL
OIL-TSW Delete Location
O402
O4TE
OIL-TSW: Enter movement ticket
O4TEN
O4TE_CORRECT
OIL-TSW: Correct ticket actualization
O4TENCORR
O4TE_REVERSE
OIL-TSW: Reverse ticket actualization
O4TENREV
O4TF
OIL-TSW: Change ticket
O4TFN
O4TG
OIL-TSW: Display Ticket
O4TGN
O4TH
OIL-TSW: Delete movement ticket
O4THN
O4TO
Work list
O4TO_LIST
O4TW
OIL-TSW Create Location
O401
O4TX
OIL-TSW Change Location
O402
O4TY
OIL-TSW Display Location
O403
O547
Reconciliation OIA07
No Replacement available
O548
Reconcile Movb. Netting balance
No Replacement available
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Other Terms
S/4HANA, SFIN and IS-OIL & GAS
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1263
55.7 S4TWL - Optimization in Oil & Gas - TD module for STO and sales
order with POD b
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328639
S4TWL - Optimization in Oil Gas - TD
module for STO and sales order with
POD business scenario
Symptom
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 doesn’t 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.
Reason and Prerequisites
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.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1264
case of STO) followed by 101 movement for the same outbound delivery at the time of
load confirmation
Software Components
IS-OIL
Languages
English
How to Determine Relevancy
This item is relevant for all IS-Oil customer
55.8 S4TWL - Data Model in Oil & Gas Inventory management
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328419
S4TWL-Data Model in Oil & Gas
Inventory management
Symptom
You are an Oil and Gas customer and doing a system conversion to SAP S/4HANA on-
premise edition 1610. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1265
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.
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
DDL Source of CDS View
for redirect
View to read the
content of the
database table
(w/o redirect to
compatibility
view)
View to
read the
master
data
attributes
only
MBEW
Material
Valuation
MBV_MBEW_EX
T
OIH_OILEMBEW7_MBEW
_EXT_DDL
CWM_MBEW_EXT_DDL
MBV_MBEW_ML
_ONLY
OIH_OILEMBEW7_MBEW
_ML_DDL
CWM_MBEW_ML_DDL
MBV_MBEW_BA
SIS
OIH_OILEMBEW7_MBEW
_BASIS_DDL
CWM_MBEW_BASIS_DDL
MBV_MBEW_CA
SE
OIH_OILEMBEW7_MBEW
_CASE_DDL
CWM_MBEW_CASE_DDL
MBV_MBEW_MO
TH_SEG
OIH_OILEMBEW7_MBEW
_MOTH_DDL
CWM_MBEW_MOTH_SE
G_DDL
MBV_MBEW
OIH_OILEMBEW7_MBEW
_DDL
CWM_MBEW_DDL
EBEW
MBV_EBEW_EX
T
OIH_OILEMBEW7_EBEW
_EXT_DDL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1266
Sales Order
Stock
Valuation
MBV_EBEW_ML
_ONLY
OIH_OILEMBEW7_EBEW
_ML_DDL
MBV_EBEW_BA
SIS
OIH_OILEMBEW7_EBEW
_BASIS_DDL
MBV_EBEW_CA
SE
OIH_OILEMBEW7_EBEW
_CASE_DDL
MBV_EBEW
OIH_OILEMBEW7_EBEW
_DDL
QBEW
Project Stock
Valuation
MBV_QBEW_EX
T
OIH_OILEMBEW7_QBEW
_EXT_DDL
MBV_QBEW_ML
_ONLY
OIH_OILEMBEW7_QBEW
_ML_DDL
MBV_QBEW_BA
SIS
OIH_OILEMBEW7_QBEW
_BASIS_DDL
MBV_QBEW_CA
SE
OIH_OILEMBEW7_QBEW
_CASE_DDL
MBV_QBEW
OIH_OILEMBEW7_QBEW
_DDL
OBEW
Valuated
Stock with
Subcontracto
r
MBV_OBEW_EX
T
OIH_OILEMBEW7_OBEW
_EXT_DDL
MBV_OBEW_ML
_ONLY
OIH_OILEMBEW7_OBEW
_ML_DDL
MBV_OBEW_BA
SIS
OIH_OILEMBEW7_OBEW
_BASIS_DDL
MBV_OBEW_CA
SE
OIH_OILEMBEW7_OBEW
_CASE_DDL
MBV_OBEW
OIH_OILEMBEW7_OBEW
_DDL
MARC
Plant Data
for Material
NSDM_DDL_MA
RC
CWM_MARC_COSTING
OI0_COMMON_2_OILMA
RC_DDL
MKPF
Header:
Material
Document
NSDM_DDL_MK
PF
OI0_COMMON_2_OILMK
PF_DDL
MSEG
Document
Segment:
Material
NSDM_DDL_MS
EG
CWM_MSEG_DDL
OI0_COMMON_2_OILMS
EG_DDL
OIO_OIOMSEG_DDL
MA07V
Material
Master: DB
View for
Inventory
Management
NSDM_E_MA07V
OI0_COMMON_OILVAP_
MA07V_DDL
VAPM
A
Sales Index:
Order Items
by Material
V_VAPMA
OIF_OILVAPMA_DDL
MARC
O1
Appendix for
Additional
Quantities at
Plant Level
OIB_DDL_MARCO1
V_OIB_MG_MA
RCO1
V_MARCO
1_MD
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1267
MARD
O1
Appendix for
Storage
Location
Additional
Quantities
OIB_DDL_MARDO1
V_OIB_MG_MA
RDO1
V_MARDO
1_MD
MCHB
O1
Appendix for
Additional
Quantities at
Batch Level
OIB_DDL_MCHBO1
V_OIB_MG_MC
HBO1
V_MCHBO
1_MD
MKOL
O1
Special
stocks from
vendor
additional
quantity
appendix
OIB_DDL_MKOLO1
V_OIB_MG_MK
OLO1
V_MKOLO
1_MD
MSLB
O1
Appendix for
Special
Stocks with
Vendors:
Add.
Quantities
OIB_DDL_MSLBO1
V_OIB_MG_MS
LBO1
V_MSLBO
1_MD
MSKA
O1
Special
Stocks
Appendix:
Additional
Quantities
OIB_DDL_MSKAO1
V_OIB_MG_MS
KAO1
V_MSKAO
1_MD
MSKU
O1
Appendix for
Special
Stocks with
Customers:
Add.
Quantities
OIB_DDL_MSKUO1
V_OIB_MG_MS
KUO1
V_MSKUO
1_MD
MSPR
O1
Project Stock
additional
quantities
OIB_DDL_MSPRO1
V_OIB_MG_MS
PRO1
V_MSPRO
1_MD
MARC
HO1
MARCH:
Additional
quantities
appendix
OIB_DDL_MARCHO1
V_OIB_MG_MA
RCHO1
MARD
HO1
MARDH:
Aditional
quantities
appendix
OIB_DDL_MARDHO1
V_OIB_MG_MA
RDHO1
MCHB
HO1
Appendix for
Additional
Quantities at
Batch Level
OIB_DDL_MCHBHO1
V_OIB_MG_MC
HBHO1
MKOL
HO1
MKOLH:
Additional
quantities
appendix
OIB_DDL_MKOLHO1
V_OIB_MG_MK
OLHO1
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1268
MSLB
HO1
MSLB:
Additional
quantities
appendix
OIB_DDL_MSLBHO1
V_OIB_MG_MS
LBHO1
MSKA
HO1
MSKAH:
Additional
quantities
appendix
OIB_DDL_MSKAHO1
V_OIB_MG_MS
KAHO1
MSKU
HO1
MSKUH:
Additional
quantities
appendix
OIB_DDL_MSKUHO1
V_OIB_MG_MS
KUHO1
MSPR
HO1
MSPRH: Ad
ditional
quantities
appendix
OIB_DDL_MSPRHO1
V_OIB_MG_MS
PRHO1
MSEG
O1
Quantity
Conversion
Parameters
for Material
Documents
OIB_DDL_MSEGO1
V_OIB_MG_MS
EGO1
MSEG
O2
Material
Document
Quantities in
Additional
Units of
Measure
OIB_DDL_MSEGO2
V_OIB_MG_MS
EGO2
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1269
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 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1270
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1271
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 deleted
from the BAdI ARC_MM_MATBEL_WRITE as the BAdI call is inappropriate.
The material documents already present in the customer’s 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
Other Terms
MATDOCOIL, S/4HANA, on-premise,
conversion, MATDOCOILEXTRACT, MATDOCOIL_INDEX, MSEGO1, MSEGO2, R
OIBSCAN_MISSING_O1O2
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1272
55.9 S4TWL - Improved update logic for excise duty related movements in
MBEW
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2534551
S4TWL IS-OIL Excise Duty Fields
update on MBEW table 1709
Symptom
WARNING:
This is an IS-OIL specific SAP Note.
If you DO NOT have IS-OIL installed on your system, this SAP Note does not apply
to you.
If you apply this SAP Note and you do not have IS-OIL installed, you may cause
serious damage to your system
You are doing a system conversion to SAP S/4HANA, on-premise edition 1709. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Improved MBEW update logic for IS-OIL in SAP S/4HANA on-premise edition 1709
Activated shared lock concept for IS-OIL
No MBEW update required for non-excise duty related movements
Update of MBEW is only required for “taxed” excise duty related movements
IS-OIL master and taxed transactional data update to MBEW table
Proxy object(MBV_MBEW) on MBEW table, Untaxable material data getting from
ACDOCA_M_EXTRACT (Transaction data) Table.
For SAP S/4HANA cloud edition or new installs of the SAP S/4HANA on-premise
edition, the Late Lock (TCURM-MBEQU = 2) and the Non-Exclusive Locking
Mode (TCURM-MB_LOCK_MODE = 3) are activated by default.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1273
Business Process related information
Material movement locking is applicable for taxable material and it will always set
exclusive lock on coding level. Initial posting and after goods movement posting
in both cases taxable material set exclusive lock and update on MBEW Table
Required and Recommended Action(s)
In case of an upgrade from ERP to SAP S/4HANA 1709 or migration from SAP
S/4HANA 1610 to SAP S/4HANA 1709, the configuration is mandatory.
On upgrade or migration the default material lock is set to late lock and configuration
of the non-exclusive locking mode must be active (Table TCURM-MBEQU = 2
and TCURM-MB_LOCK_MODE = 3)
(SAP Customizing->Materials management-> General settings for material management
-> Set material lock for goods movements)
How to Determine Relevancy
This item is relevant for all IS-OIL customers
Other Terms
TCURM (Customizing: MM Configuration)
55.10S4TWL - UoM Group Extension Improvements
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
2396065
S4HANA IS-OIL : UoM Group
Enhancement Update authorization
Issue/OIB05 update failed
Release Restriction
2328459
S4TWL - Unit of Measure (UoM) Group
enhancement
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1274
Business Impact
2534454
S4TWL IS-OIL UoM Group
Enhancement 1709
Symptom
WARNING:
This is an IS-OIL specific SAP Note.
If you DO NOT have IS-OIL installed on your system, this SAP Note does
not apply to you.
If you apply this SAP Note and you do not have IS-OIL installed, you may cause
serious damage to your system
You are doing a system conversion to SAP S/4HANA, on-premise edition 1709. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
UoM group is the major object in HPM module of IS-OIL. UoM attached to material
decides the additional UoMs for that material. Hence it plays a major role in stock
calculation, document posting and display. In ECC system it is not possible to do any
modification like adition of new UoM, delete or change the existing UoM entries in UoM
group which is already created.
This restriction on UoM group changes, will hamper customer in some typical business
scenarios. So in S/4HANA simplification some relaxation is provided in the feature. Now
customer can add a new UoM into UoM group but not to change/delete the existing
UoMs of the UoM group.
Whenever a new UoM added into UoM group, system adjusts the stock with respect to
new UoMs in all the materials which were assigned to that UoM group.
Solution
A report “R_OIB_01_UOM_ADD_INSERT_SUM” is developed to add the new UoM
into the UoM group and adjust the stock for all the materials belonging to UoM group for
the new UoM by inserting summary records.
The report needs to be executed in development, quality and production systems in a
sequence to keep sync between the systems in the landscape.
The report (R_OIB_01_UOM_GRP_EHN_DISPLAY) is developed that gives the output
of summary records created for all the materials assigned to UoM Group which was
enhanced by adding new UoM. And it shows the physical parameters considered for
calculating the summary records, created by, time stamps, and posting date.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1275
Table OIB_UOM_GRP_HIST is updated with change history, Unit of Measure Group,
Version UoM added, Last Changed by and Timestamp and so on.
Other Terms
UoM Group, IS-OIL, Additional UoM
55.11S4TWL - Extended IS-OIL Customizing
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2534360
S4TWL IS-OIL Template with
technically required BC Set values
Symptom
WARNING:
This is an IS-OIL specific SAP Note.
If you DO NOT have IS-OIL installed on your system, this SAP Note does not apply
to you.
If you apply this SAP Note and you do not have IS-OIL installed, you may cause
serious damage to your system
You are doing a system conversion to SAP S/4HANA, on-premise edition 1709. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
You have installed/upgraded to IS-Oil S/4HANA 1709
Solution
Industry Solution - Oil and Gas (IS-OIL) has created an improved customizing template
which comprises of new Switch Business Configuration Sets. The new customizing
values are delivered as part of S/4HANA 1709 and will only be applicable for the IS-OIL
S/4HANA On-Premise customers. These BC Sets do not contain any ecatts or enterprise
configurations. The intent here is to deliver reference customizing entries to help
consultants configure the system as per their business needs.
Other Terms
BC Sets, Customizing Template
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1276
55.12S4TWL - IS-OIL - Commodity Management Integration
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2534268
S4TWL IS_OIL & Commodity Pricing
Engine Integration 1709
Symptom
WARNING:
This is an IS-OIL specific SAP Note.
If you DO NOT have IS-OIL installed on your system, this SAP Note does not apply
to you.
If you apply this SAP Note and you do not have IS-OIL installed, you may cause
serious damage to your system
You are doing a system conversion to SAP S/4HANA, on-premise edition 1709. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
During the integration of Commodity Pricing Engine in an S/4 IS-OIL System, few
changes were made in order to ensure the smooth functioning of the same, specifically
removing the conflicts with Formula and Average Pricing.
Solution
OI0_CPE package created to capture changes related to the integration of
Commodity Pricing Engine. OI0_CPE is assigned to the switch OI0_SERVICE
and has the super package as IS-OIL-DS.
Maintain Formula button for the condition type with calculation type(KRECH) =Q
has been removed and made only for Formula and Average Condition Type in
both SD and MM side for the transactions vk11,vk12,vk13,mek1,mek2 and mek3.
Two new BC Sets were created for IS-OIL in the Commodity Pricing Engine
configuration Tables
OI_DS_S4DEV_CPEV_CALCRULE(calculation rule configuration)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1277
OI_DS_S4DEV_CPEV_SURCHARGE(surcharge rule configuration).
For more details on the Core CPE Simplification refer to Simplification Note: 2226096
Other Terms
IS-OIL, Pricing, CPE, IS-OIL CPE Integration, Commodity Pricing, F&A, Formula and
Average Pricing.
55.13S4TWL - IS-OIL Data Archiving For Exchanges
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2534442
S4TWL Data Archiving for Exchanges
(Data Archiving Object OIA_EXG)
Symptom
WARNING:
This is an IS-OIL specific SAP Note.
If you DO NOT have IS-OIL installed on your system, this SAP Note does
not apply to you.
If you apply this SAP Note and you do not have IS-OIL installed, you may cause
serious damage to your system
You are doing a system conversion to SAP S/4HANA, on-premise edition 1709. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
In SAP S/4HANA, on-premise edition 1709, IS-OIL can support archiving of Exchange
Agreements.
Solution
Exchange agreements can be archived using the Data Archiving Object OIA_EXG.
All the exchange agreements that has the status of ‘To be archived’ can be archived using
this object.
Note: Exchanges Data Archiving Object OIZ_EXG is responsible only for Exchanges
related tables. If you want to make full use of the object you should perform archiving for
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1278
the MM and SD objects first to archive the underlying documents in an exchange
agreement like Sales contracts, Purchase contracts, etc.
Other Terms
Data archiving, OIA_EXG, IS-OIL, Exchanges, OIA, historical data
55.14S4TWL – iTSW available only for ACM customers
Application Components:IS-OIL-DS-TSW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2572363
S4TWL- iTSW available only for ACM
customers
Symptom
WARNING:
This is an IS-OIL specific SAP Note.
If you DO NOT have IS-OIL installed on your system, this SAP Note does
not apply to you.
If you apply this SAP Note and you do not have IS-OIL installed, you may cause
serious damage to your system
You are an iTSW customer and doing a system conversion to SAP S/4 HANA on-
premise edition 1709 FPS01. You face an error "LOG_TSW_ECC is not released for S/4
HANA 1709" during execution of pre-checks or SUM.
Reason and Prerequisites
You face an error during conversion to SAP S/4HANA on-premise edition 1709.
Solution
In general iTSW is not supported in S/4 HANA, the only exception is mentioned below
in this note:
The note is for ACM customers only, who intend to do a conversion from an ECC
system to S/4 HANA 1709 FPS01.
iTSW is not supported in S/4 HANA for new (or greenfield) installations – even
when the target release is an S/4 HANA 1709 FPS01 release.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1279
For conversion, we do not support any S/4 HANA target release higher than S/4
HANA 1709 FPS01 (S/4 HANA 1809, 1909 etc.).
Other Terms
LOG_TSW_ECC; LOG_TSW_ECC_1; iTSW; ACM
55.15S4TWL - Service Station Retailing
Application Components:IS-OIL-DS-SSR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3009925
S4TWL - Service Station Retailing
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
Service Station Retailing is part of the SAP S/4HANA compatibility scope, which comes
with limited usage rights. For more details on the compatibility scope and it’s expiry date
and links to further information please refer to SAP note 2269324. In the compatibility
matrix attached to SAP note 2269324, Service Station Retailing for O&G can be found
under the ID 110.
This means that you need to migrate from Service Station Retailing to its designated
alternative functionality – SAP S/4HANA Supply Chain for secondary distribution
(S4SCSD) component Retail Fuel Network Operations (RFNO), before expiry of the
compatibility pack license. This note shall provide an overview on how you can migrate
to the alternative functionality.
Business Process related information
SAP S/4HANA Supply Chain for secondary distribution is an SAP Oil & Gas add-on that
uses functions from IS-Oil Downstream.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1280
S4SCSD is available as of SAP S/4HANA 1610. You find information about functional
scope of SAP S/4HANA Supply Chain for secondary distribution and its component
Retail Fuel Network Operations at help.sap.com.
Please note that Retail Fuel Network Operations component requires an extra license.
Required and Recommended Action(s)
As Service Station Retailing for O&G can be used until the expiry date of the
compatibility pack license, it’s up to each customer to decide, when (with which of the
coming SAP S/4HANA releases) they want to migrate to the designated alternative
functionality.
Please note that no direct conversion from Service Station Retailing to Retail Fuel
Network Operations is possible and new installation is required. Therefore, please plan
accordingly for the migration efforts in your project.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, Service Station
Retailing, Oil&Gas, ID 110
55.16S4TWL – Shipment Cost Processing
Application Components:LE-TRA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3051698
S4TWL - Shipment Cost Processing
Symptom
You are an IS-OIL customer and doing a system conversion from SAP ERP to SAP
S/4HANA or an upgrade from a lower to a higher SAP S/4HANA release and are using
the functionality described in this note. The following SAP S/4HANA Simplification
Item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1281
LE-TRA Shipment Costing Functionality is part of the SAP S/4HANA compatibility
scope, which comes with limited usage rights. For more details on the compatibility
scope and it’s expiry date and links to further information please refer to SAP note
2269324. Due to dependency on LE-TRA functionality, LE-TRA specific expiry date is
also valid for this functionality. In the compatibility matrix attached to SAP note
2269324, LE-TRA Shipment Costing for Oil & Gas can be found under the ID 127. This
means that you need to migrate from LE-TRA Shipment Costing to its designated
alternative functionality, which is the base variant of SAP S/4HANA Supply Chain for
Transportation Management, that is already available, before expiry of the compatibility
pack license.
Business Process related information
LE-TRA Shipment Costing functionality, which is part of S/4HANA compatibility scope,
includes shipment costing for IS-Oil TD shipment. This calculation is done based on TD
shipment information as well as LE-TRA shipment costing configuration and pricing
condition details. That is part of the LE-TRA solution, which is part of compatibility
scope
Required and Recommended Action(s)
As LE-TRA shipment costing functionality can be used until the expiry date of the
compatibility pack license, it’s up to each customer to decide, when (with which of the
coming SAP S/4HANA releases) they want to migrate to the designated alternative
functionality.
The planned alternative functionality for the shipment cost document of IS-Oil TD
shipment will be the Freight Settlement Document from SAP S/4HANA Supply Chain
for Transportation Management.
To be able to run the above-mentioned alternative functionality for freight costing of IS-
Oil TD shipment, the corresponding development is planned to do the integration
between IS-Oil TD shipment and Transportation Management. Please refer to
IFR/roadmap explorer for details.
Please refer to SAP note 2270199 for Transportation Management as alternative solution
for LE-TRA.
Currently both solutions (LE-TRA and Base Variant of SAP S/4HANA Supply Chain for
Transportation Management) are independent from each other and can be used next to
each other in the same SAP S/4HANA database instance. They are not integrated with
each other. As of expiry date of the compatibility item (LE-TRA shipment costing) any
enhancements or modifications done, will not be available anymore.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1282
SAP S/4HANA TM is already available and can be used as a basic Transportation
Management variant, which comes with the CORE S/4HANA License and covers the
main features of LE-TRA shipment costing. Advanced Transportation Management has
additional features compared to the main features of LE-TRA shipment costing, but
requires additional license.
As well for LE-TRA the main features have already been replaced with the base variant
of SAP S/4HANA Supply Chain for Transportation Management.
For convenience here is the link to the corresponding simplification item of LE-TRA
shipment costing for O&G:
https://launchpad.support.sap.com/#/sic/itemSet('00109B1318B61EDCB0B59EDA85C8
E124','false')
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, TD shipment,
Oil&Gas, ID 127, LE-TRA shipment costing
55.17S4TWL - Optimization in Oil&Gas - Inter company sales - Cross border
excise duty
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2347421
S4TWL - Optimization in Oil & Gas -
Inter company sales- Cross border
excise duty
Symptom
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 doesn’t apply to you. This note does not apply to you
if TDP-‘Cross-Company/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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1283
Reason and Prerequisites
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
With the new SAP S/4HANA MM-IM
optimization, single item process as well as array processing is possible.With the single p
rocessing the items will be processed item by item & throws error (deficit of stock).
Solution
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 o
f inter company Sales (cross border excise duty) reversal scenarios.
Software components
IS-OIL
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1284
55.18S4TWL – Freight Costs
Application Components:IS-OIL-DS-TSW
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3050713
S4TWL - TSW Freight Costs
Symptom
You are an IS-OIL customer and doing a system conversion from SAP ERP to SAP
S/4HANA or an upgrade from a lower to a higher SAP S/4HANA release and are using
the functionality described in this note. The following SAP S/4HANA Simplification
Item is applicable in this case.
Solution
Description
TSW Freight Costs Functionality is part of the SAP S/4HANA compatibility scope,
which comes with limited usage rights. For more details on the compatibility scope and
it’s expiry date and links to further information please refer to SAP note 2269324.
Due to dependency on LE-TRA functionality, LE-TRA specific expiry date is also valid
for this functionality.
In the compatibility matrix attached to SAP note 2269324, TSW Freight Costs for Oil &
Gas can be found under the ID 126.
This means that you need to migrate from Laytime & Demurrage functionality in TSW
Nomination to its designated alternative functionality – ‘Laytime & Demurrage’ Fiori
App, before expiry of the compatibility pack license. This note shall provide an overview
on how you can migrate to the alternative functionality.
Business Process related information
TSW Freight Costs functionality, which is part of S/4HANA compatibility scope,
includes Laytime and Demurrage calculation in TSW Nomination. This calculation is
done based on details maintained in freight contract, such as laytime terms, start and end
events for laytime, as well as demurrage rates. Demurrage calculaton is done based on
Shipment Cost Pricing that is part of the LE-TRA solution, which is also part of
compatibility scope.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1285
As of SAP S/4HANA 1809 the alternative functionality for Laytime and Demurrage
calculation is available – Fiori Apps F3389 ‘Schedule Hydrocarbon Trip’ and F3390
‘Laytime and Demurrage’. With these apps you can calculate laytime, capture related
demurrage costs of a trip and trigger associated follow-up activities. Demurrage
calculation is done based on SD and MM pricing.
You can find more information about functional scope of Laytime & Demurrage
Calculation functionality at help.sap.com.
Please also refer to note 3027954 for information regarding functionality and current
limitations.
Required and Recommended Action(s)
As TSW Freight Costs functionality can be used until the expiry date of the
compatibility pack license, it’s up to each customer to decide, when (with which of the
coming SAP S/4HANA releases) they want to migrate to the designated alternative
functionality.
Currently both solutions are independent from each other and can be used next to each
other in the same SAP S/4HANA database instance. They are not integrated with each
other and data for calculated laytime or demurrage is not exchanged.
The new Fiori apps for laytime and demurrage calculation utilize some of the
functionality used also during calculation in TSW Nomination. However, both apps
represent a new solution, including new processes and capabilities.
As of expiry date of the compatibility item (Laytime and Demurrage functionality in
TSW Nomination) any enhancements or modifications done, will not be available
anymore.
Other Terms
SAP S/4HANA, Compatibility Scope, System Conversion, Upgrade, TSW Freight Cost,
Oil&Gas, ID 126, Laytime & Demurrage
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1286
55.19S4TWL - Remote Logistics Management
Application Components:IS-OIL-OL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3046934
S4TWL - Remote Logistics
Management
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this note. The following SAP S/4HANA Simplification Item is applicable in this case.
Solution
Description
SAP Remote Logistics Management (RLM) is part of the SAP S/4HANA compatibility
scope, which comes with limited usage rights. For more details on the compatibility
scope and it’s expiry date and links to further information please refer to SAP note
2269324. In the compatibility matrix attached to SAP note 2269324, Remote Logistics
Management can be found under the ID 103.
This means that you cannot use Remote Logistics Management (RLM) after the expiry of
the compatibility pack license. There is an alternative functionality called "Field
Logistics" in SAP S/4HANA. This note shall provide information on what to do to move
to the alternative functionality.
Business Process related information
SAP S/4HANA Field Logistics is part of the SAP Oil & Gas Upstream Cloud scope.
Field Logistics is available as of SAP S/4HANA CE1908. You can find information
about the functional scope of Field Logistics at help.sap.com. Field Logistics scenarios
are available with the Best Practice Scope items 40G, 4AH and 5OM.
Please note that Field Logistics, as part of the Oil&Gas Upstream component, requires an
extra license.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1287
As Remote Logistics Management (RLM) can be used until the expiry date of the
compatibility pack license, it’s up to each customer to decide when (based on which of
the upcoming SAP S/4HANA releases) they want to implement the designated alternative
functionality.
Please note that no direct conversion from Remote Logistics Management (RLM) to
Field Logistics is possible and a new installation is required. Therefore, please plan
accordingly for the implementation efforts in your project.
Other Terms
SAP S/4HANA, Compatibility Scope, Compatibility Package, System Conversion,
Upgrade, Remote Logistics Management, Oil&Gas
55.20S4TWL - IS-OIL Proper sign operation for ACDOCA
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2350150
IS-OIL Proper sign operation for
ACDOCA
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition 1610. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
In SAP S/4HANA proper sign operation is adapted for ACDOCA.
Solution
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:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1288
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.
Software Component
IS-OIL
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Other Terms
sign,ACDOCA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1289
55.21S4TWL - Unit of Measure (UoM) Group enahncement
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328459
S4TWL - Unit of Measure (UoM) Group
enhancement
Symptom
UoM group ‘xxx’ assigned to a material; not possible to change or delete
Reason and Prerequisites
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.
Solution
A report “R_OIB_01_UOM_ADD_INSERT_SUM” has been developed, which adds the
new UoM into 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1290
level) with respect to new UoMs for all the materials which were assigned to that UoM
group.
Report “R_OIB_01_UOM_ADD_INSERT_SUM” 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 enhanced and the UoM that has to be added to the
UoM Group. By 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 for ‘Test Mode’.
Role ‘SAP_ISOIL_UOM_GR’ Authorization object OIB_UOM with activity 48 for
Simulation and 10 for Post (or Update) needs to be assigned to the user for executing this
report.
For a particular material/plant/storage location/batch system will check
current/net stock in base UoM and convert it to the newly added UoM based
on QCI parameters and its values.
If O3DEFAULTS is not maintained for the material/plant/storage location,
program will check for last material document posted in which QCI parameter
values are filled in manually and those parameters and their values will be
considered for QCI conversion to calculate the stock in new UoM.
If a material document exists for a material with a conversion group and the assigned
conversion group is changed to a new conversion group for the same material resulting
in a change of the QCI parameters and its values, then the program will check if
conversion group is changed. If yes, it will consider the new conversion group, find the
corresponding reading group, get the QCI parameters assigned to the reading group and
consider the QCI parameter values for conversion and create the summary record.
Use cases handled:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1291
If a material is marked for deletion, program still creates summary record but
‘Material flag for deletion’ column is marked ‘x’ (as just FYI)
Negative stocks are also handled with QCI conversion to new UoM
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
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)
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
There are some cases where material documents are created with a UoM (For Ex:
BBL) which is not part of UoM group. In such cases, program ensures that the
new UoM’s quantity in 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
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
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
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1292
This item is relevant for all IS-Oil customer
55.22S4TWL - eNetting Deprecation
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328548
S4TWL-eNetting functionality in
exchanges module is not available in
S/4 HANA
Symptom
As preparation for a system conversion to SAP S/4HANA 1610 exchange reconciliation
through eNetting.
Reason and Prerequisites
eNetting functionality in exchanges module is not available in SAP S/4HANA 1610.
Solution
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.
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:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1293
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
Other Terms
IS-OIL-DS-EXG, IS-OIL-NET, Exchanges, eNetting
55.23S4TWL - Dynamic Scheduling deprecation
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328538
S4TWL-Dynamic scheduling
functionality in TSW module is not
available in SAP S/4HANA 1610
Symptom
As preparation for a system upgradation to SAP S/4HANA 1610.
Reason and Prerequisites
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 real-time (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.
Solution
Description:
Dynamic scheduling application is an integration of Stock Projection Worksheet (SPW)
and Three-way pegging (3WP) functionality. Dynamic Scheduling integrates these two
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1294
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
Other Terms
IS-OIL-DS-TSW, TSW, Dynamic scheduling, Stock Projection Worksheet
(SPW), Three-way pegging (3WP)
55.24S4TWL - Financial Based netting deprecation
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328017
S4TWL-Financial based Netting
functionality in exchanges
Symptom
Customer may face errors while executing transaction O3A4(Create netting
document) and O54X(Create Selection) that refers to financial based netting.
Reason and Prerequisites
Movement based netting has more advantages over Financial Based Netting functionality
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1295
Solution
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
Other Terms
IS-OIL-DS, EXG, Exchanges, Financial Based Netting, Netting, Netting Selection
Criteria, Netting Document, O54X, O3A4.
55.25S4TWL - Oil & Gas inconsistency reports deprecation
Application Components:IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328561
Inconsistency Reports in HPM
Symptom
Report deprecated due to new data model.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1296
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
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1297
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:
ROIB_MATDOCOIL_CONSI_CHECK (Please check note 2599569 - Data
Inconsistency Between Oil and Core Tables)
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
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
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1298
Aggregate table, History table, Stock, Inconsistency, MARDO1
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1299
56.Industry Oil – OGSD
56.1 S4TWL - OGSD - Classic Data Collation
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2477777
S4TWL - OGSD - Classic Data Collation
Symptom
You are converting a system with installed Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Classic Data Collation" - that is the Data Collation
using SAP-GUI.
Solution
Description:
The old or "Classic Data Collation" incorporates the processes for the retrospective entry
of all activities resulting from the purchase and procurement of petroleum products and
the delivery of these products to customers. This means, it processes sales data "after the
fact" and calls all needed functions or transactions from SD and MM for the actual
process. It is used mainly for mass processing of sales data coming a) via interfaces
(ALE) and b) to some smaller extent by entering data online, meaning that either you or
an automatic process started by ALE enters the actual values from the purchasing and
supply areas and from the sale and delivery of the procured and delivered materials.
Business related information:
Data collation (old and new alike) integrates and automates frequently used processes
mainly in Materials Management (MM) and Sales and Distribution (SD).
It therefore represents a direct connection of MM and SD processes, such as procuring
materials, creating and changing sales contracts, sales orders, and deliveries.
For further information about the old or "Classic Data Collation" see:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1300
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/16c7aa533dae0077e10000000a4450e5.html
For further information about the Floorplan-Manager(FPM)-WebDynpro based New
Data Collation see here:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/8e0cbd535862aa23e10000000a441470.html
This page contains a comparison between both versions allowing for a better assessment
of the usability and scope of both.
Required and recommended action(s):
If you want to continue using Data Collation, you need to switch to the New Data
Collation, which is based on FPM and WebDynpro technology. In this case you
have to check, if you have created some own functionality inside or for use by the
now called "Classic Data Collation". If such own functionalities exists, you need
to manually migrate your functionalities into the New Data Collation or adapt
them in order to make use of them in the future too.
You need to consider this as a project, as there are no migration tools which may
assist you in transfering code of form-routines into class-methods or similar. All
adaptations need to be executed manually.
You do not need to migrate OGSD-own funtionalities of the Classic Data Collation,
these have been migrated into the succcessor application "New Data Collation".
You need to organize knowledge transfer to all users working with Classic Data
Collation" as their pattern of work will change when working with the "New Data
Collation". Users will have to use new applications for creating, changing,
displaying and processing a new Data Collation document.
An introduction to the new Data Collation can be found in a course available on
openSAP:
https://open.sap.com/courses/ogsd1
Week 2 Units 1 - 4 deal with the new Data Dollation.
Other Terms
Simplification Items, System Conversion to SAP S/4HANA, Transactions
/ICO/MO_R1, /ICO/MO_R2, /ICO/MO_R3, /ICO/MO_R9
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1301
56.2 S4TWL - OGSD - Classic OGSD Interfaces
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2489544
S4TWL - OGSD - Classic Interfaces
Symptom
You are converting a system with installed Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Classic Interfaces" to process (mostly inbound)
IDocs using VOFM-style customer enhancements via form routines.
Solution
Description:
The old or "Classic Interfaces" incorporates the processes for the import and processing
of (mostly) inbound IDocs in order to trigger further activities resulting from the
purchase and procurement of petroleum products and the delivery of these products to
customers by making use only of the Classic Data Collation (see SAP-note 2477777).
This means, it processes IDocs coming via ALE, transforms IDoc data or creates IDocs
from flat files. The interfaces are used for checking purposes and also for adding data to
incoming data.
Business related information:
The Classic Interfaces allow for importing data in the form of flat files or IDocs received
by ALE and pass on these data to the Classic Data Colation (see SAP-Note 2477777)
which then integrates and automates frequently used processes mainly in Materials
Management (MM) and Sales and Distribution (SD).
It therefore represents a needed first step to allow for the direct connection of MM and
SD processes, such as procuring materials, creating and changing sales contracts, sales
orders, and deliveries.
For further information about the old or "Classic Data Collation" see:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1302
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/16c7aa533dae0077e10000000a4450e5.html
For further information about the NEW Interfaces see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/75320f54366b2e18e10000000a174cb4.html
There is no information about the Classic Interfaces online anymore, but the listed steps
are quite similar to the New Interfaces, except that wher "methods" are stated, the Classic
Interfaces are using form routines at special events during the process.
Required and recommended action(s):
If you want to continue using the Interfaces, you need to switch to the New
Interfaces, which is using a method framework instead of form routines and has
many more new features . In this case you have to check, if you have created
some own functionality inside or for use by the now called "Classic Interfaces". If
such own functionalities exists, you need to manually migrate your functionalities
into the New Interfaces or adapt them in order to make use of them in the future
too.
You need to consider this as a project, as there are no migration tools which may
assist you in transfering code of form-routines into class-methods. All adaptations
need to be executed manually.
You do not need to migrate OGSD-own funtionalities of the Classic Interfaces, these
have been migrated into the succcessor application "New Interfaces".
You need to organize knowledge transfer to all users working with Classic Interfaces
as their pattern of work will change when working with the "New Interfaces".
Users will have to use new applications for creating, changing, displaying and
processing interface data.
An introduction to the New Interfaces can be found in a course available on
openSAP:
https://open.sap.com/courses/ogsd1
Week 3 Units 4 - 5 deal with the New Interfaces.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1303
Simplification Items, System Conversion to SAP S/4HANA, Transactions /ICO/MO_IF,
/ICO/MO_IA, /ICO/MO_IB, /ICO/MO_I9, ICO/MO_IH, ICO/MO_IM, ICO/MO_FD,
ICO/MO_FU
56.3 S4TWL - OGSD - Sales Logistics Cockpit
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2489567
S4TWL - OGSD - Sales Logistics
Cockpit
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application Sales Logistics Cockpit.
Solution
Description:
The Sales Logistics Cockpit is an application that gives access to customer data including
the OGSD customer history and the OGSD notes.
Business related information:
Sales Logistics Cockpit integrates and automates frequently used processes mainly in
Materials Management (MM) and Sales and Distribution (SD) and is built in a CRM-like
way. It also incorporates functionalities from the "Telesales" thus reducing the need for
users to deal with a more extensive screen like the ones in VA01, VA02, VA03 or
similar.
It therefore represents a direct connection of MM and SD processes, such as procuring
materials, creating and changing sales contracts, sales orders, and deliveries.
The Sales Logistics Cockpit is discontinued in SAP S/4HANA, so all its program and
DDIC-objects are lost after a migration to SAP S/4HANA.
Data: As it holds no own data (except for some own customizing data determining
screens and some functionalities of the Sales Logistics Cockpit) none are lost.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1304
For further information about the Sales Logistics Cockpit see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/1f320f54366b2e18e10000000a174cb4.html
For further information about the Telesales see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/82320f54366b2e18e10000000a174cb4.html
For further information about the FMB-WebDynpro based New Data Collation see here:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/8e0cbd535862aa23e10000000a441470.html
Required and recommended action(s):
If you want to continue using some of the Sales Logistics Cockpit functionalities, you
can check if a switch to S4SCSD Telesales might provide some of the
functionalities you need. You may also check if the new S4SCSD Data Collation
(based on FPM and Web Dynpro technology) can help you realize similar
functionalities.
You need to consider this as a project, as there are no migration tools which may
assist you in transferring code of form-routines into class-methods or similar. All
adaptations need to be executed manually.
You need to organize knowledge transfer to all users working with Sales Logistics
Cockpit as their pattern of work will change when working with the "New Data
Collation" or Telesales. Users will have to use new applications for creating,
changing, displaying and processing new documents.
An introduction to the new Data Collation can be found in a course available on
openSAP:
https://open.sap.com/courses/ogsd1
Week 2 Units 1 - 4 deal with the new Data Collation.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA,
Transactions /ICO/MO_3C, /ICO/MO_3C_FRM, /ICO/MO_VLC_FRM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1305
56.4 S4TWL - OGSD - Liquid Petrol Gas
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2489643
S4TWL - OGSD - Liquid Petroleum Gas
Symptom
You are converting a system with installed Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Liquid Petroleum Gas", a Step-Loop-Application
for processing Gas and Bottles using SAP-GUI.
Solution
Description:
The application Liquid Petroleum Gas incorporates the processes for the administration
and processing of gas and bottles as a retrospective entry of all activities resulting from
the purchase and procurement of LPG products and the delivery of these products to
customers. This means, it processes sales and lending data "after the fact" and calls all
needed functions or transactions from SD and MM for the actual process.
Business related information:
The application Liquid Petroleum Gas integrates and automates frequently used processes
mainly in Materials Management (MM) and Sales and Distribution (SD) by passing data
to the Classic Data Collation (see SAP note 2477777) by either making use of the Classic
Interfaces (which will be lost after a migration also, see SAP-note 2489544) or the New
Interfaces.
It therefore represents an extension to Classic Data Collation which established the direct
connection of MM and SD processes, such as procuring LPG materials, creating and
changing sales contracts, sales orders, and deliveries of the said materials. LPG is
discontinued in SAP S/4HANA, so all its objects and data are lost after a migration
to SAP S/4HANA.
For further information about Liquid Petrol Gas see here:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1306
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/13320f54366b2e18e10000000a174cb4.html
For further information about the old or "Classic Data Collation", to which all data is
passed from LPG, see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/16c7aa533dae0077e10000000a4450e5.html
For further information about the FMB-WebDynpro based New Data Collation see here:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/8e0cbd535862aa23e10000000a441470.html
This page contains a comparison between both versions allowing for a better assessment
of the usability and scope of both.
Required and recommended action(s):
If you want to continue functionalities currently provided by "Liquid Petroleum Gas",
you need to check if, how and where you can re-create your own LPG-
functionality inside the framework provided by the "new Data Collation", which
is based on FPM and Web Dynpro technology. If own functionalities exists in
LPG and you have determined that the New Data Collation can be used for your
business processes, you need to manually migrate your functionalities into the
new Data Collation in order to make use of them in the future too, and
configure the New Data Collation accordingly.
In this case you need to consider this migration to the new Data Collation as a project,
as there are no migration tools which may assist you in transferring code of form-
routines or includes etc. into class-methods or similar used by the new Data
Collation. All adaptations need to be performed manually.
And in this case you also need to organize knowledge transfer to all users currently
working with Liquid Petrol Gas as their pattern of work will change when
working with the "new Data Collation". Users will have to use new applications
for creating, changing, displaying and processing a new Data Collation
document.
An introduction to "New Data Collation" can be found in a course available on
openSAP:
https://open.sap.com/courses/ogsd1
Week 2 Units 1 - 4 deal with the new Data Collation.
Other Terms
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1307
Simplification Item, System Conversion to SAP S/4HANA, LPG, Transactions
/ICO/MO_L1, /ICO/MO_L2, /ICO/MO_L3, /ICO/MO_L9
56.5 S4TWL - OGSD - Infosheet
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2491123
S4TWL - OGSD Infosheet
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Infosheet"
Solution
Description:
"Infosheet" is an OGSD application that allows you to define screens within the
"Telesales" transaction, if you are using transaction VA01, VA02 or similar transactions
for IS-OIL-DS-OGSD. These screen could be defined as to the discretion of any
customer, they could either show or change data withing this scope of IS-OIL-DS-OGSD.
Other business or order types processed by VA01 etc. were not affected by Infosheets nor
are they affected once a migration to SAP S/4HANA has taken place.
Business related information:
The business advantages of Infosheet include the creation of additional all-purpose
popup-dynpros for VA01-processes etc. without requesting modifications of
SAPMV45A. The screens needed to be created by the traditional means of SAP-GUI, but
the inclusion into VA01-screens is done by filling customizing tables.
OGSD application "Infosheet" is discontinued in SAP S/4HANA, so all its program and
DDIC-objects are lost after a migration to SAP S/4HANA.
For further information about the Telesales see:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1308
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/82320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
There is no such function in S4SCSD. If you want to continue to use functionalities in
SAP S/4HANA that are provided at present by using "Infosheet" in OGSD for the
Business Suite, you need make use of SAP-provided customer extensions inside
SAPMV45A / transaction VA01. These may require modifications of standard
SAP code or objects.
You need to consider this as a project, as there are no migration tools which may
assist you in transfering code, data or other objects. All adaptations need to be
executed manually.
You need to organize knowledge transfer to all users working with "Infosheet" as
their pattern of work will change when working with customer extensions instead.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Transactions
/ICO/MO_IS_CHECK, /ICO/MO_FM_IS, /ICO/MO_FILL_LOUA
56.6 S4TWL - OGSD - Best Buy
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2490540
S4TWL - OGSD - Best Buy
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application Sales Logistics Cockpit with application "Best Buy"
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1309
Description:
"Best Buy" is an application integrated into the Sales Logistics Cockpit and designed to
support sales processes by taking into account purchase prices and delivery costs to
determine the lowest possible gross purchasing prices.
Business related information:
You can use this application "Best Buy" to support your sales processes by directly
determining the best combination of the lowest purchase prices and the lowest delivery
costs. The system does this by determining the lowest purchase prices from your material
stocks and purchasing contracts.
Prerequisites: You have made the required settings in Customizing for the Sales Logistics
Cockpit by choosing Best Buy (for details see link below).
"Best Buy" is, like Sales Logistics Cockpit, discontinued in SAP S/4HANA, so all its
data are lost after a migration to SAP S/4HANA.
For further information about "Best Buy" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/65330f54366b2e18e10000000a174cb4.html
For further information about the Sales Logistics Cockpit see note 2489567 - S4TWL -
OGSD - Sales Logistics Cockpit and
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/1f320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
If you want to continue using Best Buy and Sales Logistics Cockpit functionalities,
you need to evaluate if other SAP components provide similar functionality.
You need to consider this as a project, as there are no migration tools which may
assist you in transfering code or functions. You need to organize knowledge
transfer to all users working with Best Buy and Sales Logistics Cockpit as their
pattern of work will change when working with the "New Data Collation" or
Telesales. Users will have to use new applications for creating, changing,
displaying and processing new documents.
An introduction to the new Data Collation can be found in a course available on
openSAP:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1310
https://open.sap.com/courses/ogsd1
Week 2 Units 1 - 4 deal with the new Data Collation.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Sales Logistics Cockpit
56.7 S4TWL - OGSD - Formroutines Telesales
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2491727
S4TWL - OGSD - Formroutines
Telesales
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD Formroutines for Telesales
Solution
Description:
Formroutines in Telesales are used to collect data from various sections of the SD-
process and prepare them for display.
Business related information:
OGSD Formroutines for Telesales allow for customer-own procedures to be integrated
into Telesales.
By using Formroutines you may use, read and display data from:
a) the "Customer History", that is a list of orders and offers relating to a customer,
b) Dialogue Settings, these are settings for the screens and subscreens on the OGSD-
screen inside sales transaction VA01, VA02 etc. meaning: how and where shall data be
displayed?,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1311
c) Reference Pricing,
d) Terminal Access Identification Number.
The Formroutines for Telesales are discontinued in SAP S/4HANA, so all coding is lost
after a migration to SAP S/4HANA.
For further information about "Customer History" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/de310f54366b2e18e10000000a174cb4.html
For further information about "Reference Pricing" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/fed89af9394b46999928ff6a6530a166.html
For further information about the replacement of Formroutines in Telesales into BAdI-
implementations see:
2458477 - Elemente zur Ersetzung des Formroutinenwerks im OGSD Telesales
For further information about the Telesales see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/82320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
If you want to continue using Telesales functionalities currently provided by
Formroutines, you need to switch to the Telesales BAdIs functionality.
You need to consider this as a project, as there are no migration tools which may
assist you in transfering code of form-routines into BAdI-implementations. All
adaptations need to be executed manually. They consist of creating BAdI-
implementations and doing some customizing (this is laid out in SAP Note
2458477, see below).
You need to organize knowledge transfer to all users working with Telesales
functionalities currently provided by Formroutines as their pattern of work, when
it comes to add own functionalities to the Telesales will change.
If you want to migrate the Formroutines you need to check and implement SAP note
2458477 - Elemente zur Ersetzung des Formroutinenwerks im OGSD
Telesales and, as a prerequisite, 2461340 - DDIC-Elemente: Vorausetzung für
Hinweis 2458477 .
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1312
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Transaction VA01
56.8 S4TWL - OGSD - Intercompany Processes
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2491134
S4TWL - OGSD - Intercompany
Processes (IC)
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Intercompany Processes" (IC)
Solution
Description:
"Intercompany Processes" is an OGSD application that allows you to create an overview of
the document and quantity flow that constitutes the purchasing and sales side.
Business related information:
The business advantages of "Intercompany Processes" are to get quick overviews about
the flow of materials, documents etc. It is based on the cross-application accumulation of
quantities on the sales and purchasing side. This enables you to see, for example, whether
the plants have sufficient material. include more efficient use of .
OGSD application "Intercompany Processes" is discontinued in SAP S/4HANA, so all its
program and DDIC-objects are lost after a migration to SAP S/4HANA. No own data are
lost, as IC makes use of data from SD and MM, which are not affected by the loss of IC.
For further information about "Intercompany Processes" see the topic for "Internal Stock
Monitoring"
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1313
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/ad330f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
There is no such function in S4SCSD. If you want to continue using a functionality in
SAP S/4HANA that is provided at present by "Intercompany Processes" in OGSD
for the Business Suite, you need to switch to other SAP- or third-party-software.
You need to consider this as a project. All possible adaptations need to be executed
manually.
In case of switching to a new software you need to organize knowledge transfer to all
users working with "Intercompany Processes" as their pattern of work will change
when working with new software. Users will have to use new applications for
creating, changing, displaying and processing new documents.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Internal Stock Monitoring,
Transactions /ICO/MO_IC, /ICO/MO_ICRB, /ICO/MO_ICRP, /ICO/MO_ICRR,
/ICO/MO_ICRS, /ICO/MO_ICLSLN, /ICO/MO_ICLOE
56.9 S4TWL - OGSD - Classic Method Framework
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2491700
S4TWL - OGSD - Classic Method
Framework
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Classic Method Framework"
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1314
Description:
The old or "Classic Method Framework" incorporates means of creating customer
enhancements for other OGSD applications like the new Interfaces (in OGSD 6.1 and
7.0), the New Data Collation (from OGSD 7.0 only) and Retail Fuels Network Operation
(RFNO, from OGSD 7.0 only) at predefined special events during the processing of data
within these applications.
Business related information:
Nearly all existing business functions of the abovementioned applications are either
executed or at least supported by methods or classes administered by the Method
Framework. Whether you check, post or refuse interface date, enhance, save and post
documents from the New Data Collation or RFNO: you have to do this using methods or
classes administered by the Method Framework. A malfunction there means a
malfunction in one or even all of these applications.
For further information about the old or "Classic Method Framework" as well as the New
Method Framework and the migration process see SAP note 2383036 - Umbau des
Methodenrahmenwerks in eine BAdI-ähnliche Form especially section "Solution" and
inside this section from Chapter A). There are other SAP notes about the Method
Framework, but these deal mainly with corrections of the Classic Method Framework.
Apart from SAP-notes there is no information about the Classic or New Method
Framework online at present as it is no application standing for its own. As described
above it is a part of the foundation of the abovementioned applications, which themselves
constitute the core of OGSD and S4SCSD.
Required and recommended action(s):
If you want to continue using any of the abovementioned applications you need to
switch to the New Method Framework. This migration is, while automated in
most places, still relevant to be understood well. SAP note 2383036 explains the
changes that will take place, how they will take place and what you have to do. It
is important, that you execute all mentioned steps in sequence and completely, as
the process cannot be repeated.
You need to consider this as a project as there are migration tools which do assist you
in transfering code of n static methods of one class for each event into each one
method in n classes for each event. All adaptations are executed automatically,
once you have inserted a number of a transport request, namespaces you use and
names of packets where newly created classes shall be assigned to.
Apart from the number of a workbench transport request there are already defaults
for target names and packets, so this number of a transport request is the one thing
you definitely need to provide to be able to start the migration process.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1315
As the functionalities of the method framework have barely changed you need to
organize only a small knowledge transfer to all users currently working with the
Classic Method Framework as their pattern of work will not change when
working with the "New Method Framework" - except for the copying process of
methods, that is a bit different in the New Method Framework. All other
functions are working the same way as before users when it comes to handling
during the regular work.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Transactions
/ICO/MO_EVTMETH_OI, /ICO/MO_OOIF_EVTMETH,
/ICO/MO_OO_CACHE,/ICO/OO_CPCLASS_COPY
56.10S4TWL - OGSD - Old Notes
Application Components:IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2491245
S4TWL - OGSD - Old Notes
Symptom
You are converting a system with installed Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application "Notes" in the old version (from OGSD 4.72 or 6.0)
Solution
Description:
The "Notes" in the old as in the new version are designed to allow a user of OGSD to
create notes about his customers and to have notes created automatically, if a predefined
event does occur.
Business related information:
You can use this function to create notes about a customer or have the system create
notes automatically. The system can create up to three different notes. You can use notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1316
as reminders and set them for resubmission (RS), or have them printed on the delivery
note or invoice. You can archive the notes.
There is no information about the old version of Notes online anymore, but the
functionalities are quite similar to the new version of the notes.
For further information about the current version of the OGSD application
"Notes" ("New Notes") see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/6480a9533ad72009e10000000a441470.html
For further information about OGSD Telephone Sales (Or Telesales), of which the Notes
are part, see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/82320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
If you want to continue using Notes, you need to switch to the new Notes (which are
actually available since OGSD Release 6.1 in 2009).
There is a migration tool that assists you in transfering notes from the old into new
tables. All adaptations are executed automatically once you start
either using the customizing activity inside the IMG of Oil & Gas Secondary
Distribution - Sales - Notes - Migrate Notes
or directly transaction /ICO/MO_NO_MIGRATE.
But before you start the migration of old notes read and implement SAP
Note 1476702, if it has not been implemented in your system. The correction
coming with this note is part of OGSD since 6.1 SP 3, if you are on a higher
stack, you may start migrating any time.
You need to organize some knowledge transfer to all users working with the "Old
Notes" as their pattern of work will change a bit when working with the "New
Notes". Users will have to use new Notes in future for creating, changing,
displaying and processing notes.
Other Terms
Simplification Items, System Conversion to SAP S/4HANA, Packet /ICO/MO_NT,
Transactions /ICO/MO_NL1, /ICO/MO_NL2, /ICO/MO_NO1, /ICO/MO_NO2,
/ICO/MO_NOA, /ICO/MO_NOA1, /ICO/MO_NOA3, /ICO/MO_NT01,
/ICO/MO_NT02
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1317
57.Industry Oil – OTAS
57.1 S4TWL - OTAS - Integrated Dispatch Managment
Application Components:LO-BSLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2490435
S4TWL - OTAS - Integrated Dispatch
Management (IDM)
Symptom
You want to convert a system with Add-on OTAS to SAP S/4HANA.
Reason and Prerequisites
You are using the OTAS application Integrated Dispatch Management (IDM).
Solution
Description:
The OTAS application Integrated Dispatch Management (IDM) provides various
functions with which you can plan and monitor your outbound delivery tours.
Business related information:
Application IDM provides the following functions:
A) Trip Planning (TP) which includes: Road Map, Gantt Chart, Grids, Vehicle
components, Resources (for futher Information see the links below)
B) Combination groups: This function is used when a trip or group is being checked to
determine whether defined indicators are compatible with trip requirements.
You define the indicators used to check the compatibility of products and loading units as
well as of transport units and customers in the BSLM menu under Integrated Dispatch
Management (IDM) - Master Data- Combination Groups - Define Combination Groups.
This makes it possible to check whether a loading unit is allowed to contain a specific
product or whether a transport unit has specific technical tooling.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1318
IDM is discontinued in SAP S/4HANA, so all its program and DDIC-objects as well
as all data are lost after a migration to SAP S/4HANA.
But depending on the release of S4SCSD you are using or planning to use, you may or
may not have a functional alternative.
If you are planning to use S4SCSD Release 1.0 you must know: you will not have
any functionality from IDM, as it was deleted upon conversion, nor does any
successor application with such functionality exist in S4SCSD 1.0.
If you are planning to use S4SCSD Release 2.0, you will be able to make use of a
successor application offering this functionality. It is called S4IDM and works
with SAPUI5 and ABAP on HANA. As this application makes use of different
namespaces and is realised with different tools, you cannot migrate anything from
IDM (from the Business Suite) to S4IDM in S4SCSD 2.0 running on S/4HANA.
For further information about IDM see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/c0959f5222297704e10000000a445394.html
For further information about IDM function "Trip Planning" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/19b99f5222297704e10000000a445394.html
For further information about IDM function "Combination Groups" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/e7a91953a699ff07e10000000a423f68.html
Required and recommended action(s):
1. IDM is discontinued in SAP S/4HANA, so all its program and DDIC objects as well as
all data are lost after a migration to SAP S/4HANA.
2. If you want to continue using functionalities provided for the Business Suite by IDM
also in SAP S/4HANA, you need to consider switching either to S4SCSD 2.0, where a
successor-application exists, or to other SAP modules / applications.
3. In case of a switching to another module, tool, functionality or application (like
S4IDM in S4SCSD 2.0) you need to organize knowledge transfer to all users working
with IDM as their pattern of work will change considerably after such a switch.
Users will have to use new or different applications for creating, changing, displaying,
processing, planning and monitoring your outbound delivery tours.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1319
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Transactions /IDM/TR_IP,
/IDM/RC, /IDM/MS_GEO_LOCATE, /IDM/SRD, /IDM/TR_EVTMETH10
57.2 S4TWL - OTAS - Integrated Petroleum Report
Application Components:LO-BSLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2490467
S4TWL - OTAS - Integrated Petroleum
Report (IPR)
Symptom
You want to convert a system with Add-on OTAS to SAP S/4HANA.
Reason and Prerequisites
You are using the OTAS application Integrated Petroleum Report (IMB)
Solution
Description:
The OTAS application Integrated Petroleum Report (IPR) is used to compile data for
transfer to the Federal Export Bureau (BAFA).
Business related information:
The OTAS application Integrated Petroleum Report (IPR) is used to compile the data for
transfer to the Federal Export Bureau (BAFA).
IPR is discontinued in SAP S/4HANA, so all its program and DDIC objects are lost after
a migration to SAP S/4HANA.
For further information about IPR see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/1f43d35225d10026e10000000a4450e5.html
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1320
Required and recommended action(s):
1. IPR is discontinued in SAP S/4HANA, so all its program and DDIC objects are lost
after a migration to SAP S/4HANA.
2. If you want to continue using functionalities provided for the Business Suite by IPR
also in SAP S/4HANA, you need to consider switching to other SAP modules /
applications.
3. In case of a switching to another module, tool or functionality you need to organize
knowledge transfer to all users working with IPR as their pattern of work may change
considerably after such a switch.
Users will have to use new or different applications creating such a report.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Transaction /OTAS/IMB
57.3 S4TWL - OTAS - Sales Activities
Application Components:LO-BSLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2490447
S4TWL - OTAS - Sales Activities
Symptom
You want to convert a system with Add-on OTAS to SAP S/4HANA.
Reason and Prerequisites
You are using the OTAS application Sales Activities (or Sales Action) in combination
with OGSD.
Solution
Description:
You can use this OTAS application Sales Activities (or Sales Action) to map the
commission transaction.
Business related information:
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1321
The action partner (commission recipient) provides services to a group of ship-to parties
(delivery locations) in a specific region. The company issues a quotation to its action
partners. You need to create a quotation, the action document, concerning the delivery of
various products with various delivery dates and prices. The action partner forwards this
quotation, with any necessary changes, to the ship-to party. When a quotation results in
an order, a commission settlement will be made for the action partner based on the orders
that are delivered to its ship-to parties.
OTAS application Sales Activities is discontinued in SAP S/4HANA, so all its program
and DDIC objects as well as all data are lost after a migration to SAP S/4HANA.
For further information about "Sales Activities" (= "Sales Action") see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/en-
US/6809d552b2340126e10000000a4450e5.html
Required and recommended action(s):
OTAS application "Sales Activities" is discontinued in SAP S/4HANA, so all its
program and DDIC objects as well as all data are lost after a migration to SAP
S/4HANA.
If you want to continue using functionalities provided by OTAS application "Sales
Activities" also in SAP S/4HANA, you need to consider switching to other SAP
modules / applications.
In case of a switching to another module, tool or functionality you need to organize
knowledge transfer to all users working with OTAS-Application "Sales
Activities" as their pattern of work will change considerably after such a switch.
Users will have to use new or different applications for creating, changing, displaying,
processing, planning and monitoring your commission transactions.
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, OTAS Application Sales
Action, Transactions /OTAS/SA_ACTION, /OTAS/SA_EVALUATION
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1322
58.Industry Public Sector
58.1 S4TWL - Functionality German Local Authorities
Application Components:PSM-FM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270467
S4TWL - Functionality German Local
Authorities
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
Required and Recommended Action(s)
Make sure that the field value KOM_ACTIVE is empty before starting the system
conversion to SAP S/4HANA . You can do this via customizing (IMG) - Public Sector
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1323
Management - Funds Management Government - Basic Settings - Activate Global
Functions for German Government - Field "Authorities Germany"
See SAP note 2868358 in case of error message FI_E207.
Related SAP Notes
Custom Code related information
SAP Note: 2226072
58.2 S4TWL - Authorization in Funds Management
Application Components:PSM-FM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2339149
S4TWL - Authorization in Funds
Management
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1324
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 that’s not supported anymore.
Required and Recommended Action(s)
In the ECC source system which you are planning to convert to SAP S/4HANA,
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1325
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.
58.3 S4TWL - Public Sector localization for Hungary Deprecation
Application Components:FI-LOC-PS-HU
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3347307
S4TWL - Public Sector localization for
Hungary Deprecation
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA or an upgrade from
a lower to a higher SAP S/4HANA release and are using the functionality described in
this Note.
The following SAP S/4HANA Simplification Item SI12 Public Sector_FI-LOC-PS-
HU is applicable in this case.
Solution
Description
Packages GLO_REP_EAPS_HU, GLO_REP_EAPS_SFWS_01 and it contents becomes
obsolete because of no customer usage. Objects stored in the package and corresponding
subpackages are removed including their references from other objects.
Business Process related information
Public Sector Localization for Hungary stored in packages
GLO_REP_EAPS_HU, GLO_REP_EAPS_SFWS_01 and it's subpackages is not being
used and has been deprecated in S/4HANA OP2023 and became obsolete in all the
supported lower versions.
Regarding S/4HANA OP2021 release, for transition period of 2 years the package and it's
subpackages has been moved to SW component 'S4DEPREC' if the restoration of the
functionality is needed.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1326
Note content:
1) Existing references in objects ('Ref. Object Name') pointing to the objects in the
package /GSINS/RU and it's subpackages were removed:
Object Name
Package
Applicati
on Area
Software
Compone
nt
Inf
o
Ref.
Obje
ct
Type
Ref. Object Name
/GSINS/CL_CHECK
_EHP
/GSINS/R
EU
FS-CM-
LC
INSURAN
CE
use
d
by
ENH
O
/GSINS/CL_FSCM_LOC_T
R_605
Required and Recommended Action(s)
In general, SAP recommends that you install a solution by applying a Support Package.
You can find more information about the Note Assistant in SAP Service Marketplace,
under service.sap.com/note-assistant.
IMPORTANT:
To complete the installation procedure for S4TWL - Public Sector localization for
Hungary Deprecation you have to implement the automatic correction instructions from
this Note 2978033.
Remember, that you cannot use your own coding/functionality anymore which is based
on the removed coding/functionality, explained in this Note 3347307.
Other Terms
Public Sector, Hungary, S4DEPREC, deprecation,
obsolete, GLO_REP_EAPS_HU, GLO_REP_EAPS_SFWS_01
58.4 S4TWL - Former Budgeting System (FBS) in Funds Management
Application Components:PSM-FM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270413
S4TWL - Former Budgeting System
(FBS) in Funds Management
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1327
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Using transaction SE16N, read table FM01 to get the list of all FM areas in the client.
Using transaction SE16N, read BCS configuration table FMBCSA for each FM area
defined in table FM01.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1328
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)
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1329
58.5 S4TWL - Functionality for FACTS I and FACTS II (Federal Agencies
Centralized Tri
Application Components:PSM-FG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270415
S4TWL - Functionality for FACTS I and
FACTS II (Federal Agencies Centralized
Trial Balance System)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
RFACTS2_BL
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1330
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1331
58.6 S4TWL - Expenditure Certification
Application Components:PSM-EC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270418
S4TWL - Expenditure Certification
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
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
on-premise edition 1511
FMECDERIVE
FMECDERIVER
FMEUFDD
FMEUFFINTYP
FMEUFINTERV
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1332
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)
In order to proceed with the system conversion, the business function PSM_EXP_CERT
needs to be switched off in case it is active (use transaction SFW5 to switch them off).
Furthermore, the derivation strategy for deriving Operations must be deleted in all system
clients. If you cannot manually delete the strategy in all clients, use the deletion program
of SAP note 3258666.
Related SAP Notes
Custom Code related
information
SAP note 226049
58.7 S4TWL - Specific fields on Business Partner
Application Components:PSM-FG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270420
S4TWL - Specific fields on Business
Partner
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1333
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1334
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
58.8 S4TWL - Fund Accounting based on Special Ledger
Application Components:PSM-FA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270444
S4TWL - Fund Accounting based on
Special Ledger
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1335
In SAP S/4HANA, the Universal Journal (ACDOCA) is the heart of Accounting and
includes all master data entities required to support Fund Accounting and provides the
data model needed to generate financial as well as management information compliant
with Public Sector accounting regulations. 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.
Fund Accounting using Special Ledger tables is still possible, but not the recommended
solution going forward as it results in data redundancies as well as requires reconciliation
efforts between the data tables.
A major benefit of the use of the Universal Journal is to avoid data redundancies and
eliminate reconciliation efforts by using a single location for General Ledger,
Controlling, Asset Accounting as well as Fund Accounting. Offering a unified view of
transactional data (with account assignment dimensions from different applications) in
one location, allows for multi-dimensional reporting with flexible drill-down and
provides a single source of truth for financial as well as management reporting.
For more information about the features and benefits of Universal Journal in general and
more specific for Fund Accounting there, refer to the Innovation Discovery item ‘General
ledger and reporting (unified journal) for SAP S/4HANA’ and 'Fund accounting in SAP
Accounting powered by SAP HANA'.
Description
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 available).
Note that 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 note for General Ledger for further
details.
Business Process related information
The available successor functionality offers the same processes and features.
How to determine relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1336
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
58.9 S4TWL - Data Structure changes in BCS
Application Components:PSM-FM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270445
S4TWL - Data Structure changes in
BCS
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 exist, no migration is needed for migrating
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1337
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 year-dependent, 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
58.10S4TWL - Funds Management Dimensions as part of the Universal
Journal
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1338
Application Components:PSM-FA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270449
S4TWL - Funds Management
Dimensions as part of the Universal
Journal
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1339
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
58.11S4TWL - Functionality for BCS Multi-level Budget Structure
Application Components:PSM-FM
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1340
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270464
S4TWL - Functionality for BCS Multi-
level Budget Structure
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 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.
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
on-premise edition 1511
FMHIE_CHANGE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1341
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 SFW5 (do NOT use SFW2, which will only show you the business
function definition, not the current activation in the system) 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)
In order to proceed with the system conversion, the business functions mentioned above
need to be switched off in case they are active (use transaction SFW5 to switch them off).
Please note that with SAP S/4HANA 1909 some of the functionality included in this
business functions is available again but business function activation is no longer needed.
For more information about the available functionality in S/4HANA, refer to the 'What's
New' documentation for 'Multi-Level Budget Structures in Funds Management
Budgeting'.
Related SAP Notes
Custom Code related information
SAP Note: 2226122
58.12S4TWL - Functionality Average Daily Balance-based Distribution
Application Components:PSM-FA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270466
S4TWL - Functionality Average Daily
Balance-based Distribution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1342
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The Average Daily Balance-based Distribution (ADB) 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1343
Select each ADB rule (table FMADB_HEADER), and look for records in the
following folders:
Pool account assignments (tables FMADB_POOL)
Bank Accounts (FMADB_GLACCOUNT)
Incoming Interest Posting (table FMADB_INT_DOC) without blanks in
document type and account fields
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)
In order to distribute remaining amounts based on prior to using S/4HANA, run report
RFFMS_ADB_INTERESTS_POST. After migration to S/4HANA, undistributed
amounts need to managed as described above.
Related SAP Notes
Custom Code related information
SAP Note: 2226071
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1344
59.Industry Retail & Fashion
59.1 S4TWL - Retail Power Lists
Application Components:LO-SRS-IM, LO-SRS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371193
S4TWL - Retail Power Lists
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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, on-premise edition , refer to ID 104 in the xls.
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.
59.2 S4TWL - Retail Closed BW Scenarios
Application Components:BW-BCT, BW-BCT-ISR, BW-BCT-ISR-AA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371195
S4TWL - Retail Closed Loop BW
Scenarios
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1345
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 , refer to ID 104 in
the xls.
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
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.
59.3 S4TWL - Retail Markdown Plan
Application Components:LO-MD, LO-MD-PR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371590
S4TWL - Retail Markdown Plan
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1346
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 , refer to ID 104 in
the xls.
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 WMF1, WMF2, WMF3, WMF4, WMF5, WMF6,
WMF7,WMF_ARCHR, WMF_SARA, WMR1, WMR2, WMR3, WMR4 are used.
This also can be checked via transaction SE16N. Enter table WMFH, or WMFP and
check whether there are any entries.
59.4 S4TWL - Retail Bonus Buy
Application Components:SD-BF-FG, SD-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371559
S4TWL - Retail Bonus Buy (transaction
VBK*)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1347
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 , refer to ID 104 in the xls.
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.
How to Determine Relevancy
This Simplification Item is relevant if bonus buy funcationality via IDocs 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.
59.5 S4TWL - Retail Sales Forecasting
Application Components:IS-R-PUR-AHD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371616
S4TWL - Retail Sales Forecasting
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1348
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 , refer to ID 104 in
the xls.
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 MAHD1, MAHD2, MAHD3, MAHD4, MDRD1,
MDRD2, MDRD3, MDRD4, WFCS01, WFCS02, WFCS03, WFCS04, MPR1, MPR2
are used.
This also can be checked via transaction SE16N. Enter table MAHD, WFCS_WRFT and
check whether there are any entries.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1349
59.6 S4TWL - Retail Order Optimizing: Load Build, Investment Buy
Application Components:IS-R-PUR-LB, IS-R-PUR, IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371602
S4TWL - Retail Order Optimizing: Load
Build, Investment Buy
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 , refer to ID 104 in the xls.
Business Process related information
There is SAP Forecstaing & Replenishment as an existing solution alternative.
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 WLB1, WLB2, WLB3, WLB4, WLB5, WLB6, WLB7,
WLB13, WLBA, WLBB, WLBC are used.
This also can be checked via transaction SE16N. Enter table WVFB, WBO* and check
whether there are any entries.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1350
59.7 S4TWL - Retail Rapid Replenishment
Application Components:IS-R-PUR-RP, IS-R-PUR, IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371539
S4TWL - Retail Rapid Replenishment
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 ,
refer to ID 104 in the xls.
Business Process related information
There is SAP Forecstaing & Replenishment as an existing solution alternative.
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, WWP1, WWP2, WWP3, WWP4, WVM1,
WVM3, WVM4, WVM5, WVM6, WVM7 are used.
59.8 S4TWL - Automatic Document Adjustment
Application Components:IS-R-PUR-ADA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1351
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267742
S4TWL - Automatic Document
Adjustment
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In SAP S/4HANA, the following differences to the process of automatic document
adjustment apply:
The direct entry function is activated per default for all document categories to
simplify the creation of worklist entries.
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
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 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
2. Rebuilding business data volume (tables WIND and S111)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1352
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.
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
Description
Report for rebuilding S111 and WIND entries
01
Purchase Order
RMEBEIN3
02
Scheduling Agreement
RMEBEIN3
10
Sales Price Calculation
RWVKP012
11
Sales Price Calculation Index
RWVKP012
20
Customer billing document
RMEBEIL3
30
Vendor billing document
RMEBEIL3
31
Expense document
RMEBEIL3
32
Vendor settlement document
RMEBEIV3
35
Remuneration list
RMEBEIL3
40
Vendor settlement request
RMEBEIZ3
50
Assortment List
RMEBEIN3
55
POS-Outbound
RMEBEIN3
60
Customer settlement
RMEBEIK3
If you want to process multiple applications in one step (subsequent settlement and
automatic document adjustment), you can also use report RMCENEUA.
Related SAP Notes
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1353
Conversion Pre-Checks
SAP Notes: 2192984, 2215169
59.9 S4TWL - Retail Additionals
Application Components:LO-ADM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371631
S4TWL - Retail Additionals
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 , refer to ID 104 in the
xls.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1354
How to Determine Relevancy
This Simplification Item is relevant if additionals are used.
This is the case if transactions WTAD, WTAD_ADDI_AL, WTAD_APPL_LOG,
WTAD_ARCHR, WTAD_FMCU_CHANGE, WTAD_FMCU_DISP,
WTAD_IDOC_AL, WTAD_SARA, WTAD_SUP_FM_CHANGE,
WTAD_SUP_FM_DISP, WTAD_VKHM_DISPLAY, WTAD_VKHM_MAINTAIN,
WRF_WTAD_CA, WRF_WTAD_CA1, WRF_WTAD_CA2,
WRF_WTAD_CA3, WTR1, WTR2, WRF_WTR3, or
reports ADDI_ANALYSIS_OF_CHANGES, ADDI_APPL_LOG,
ADDI_ARCHIVE_READ, ADDI_ASSIGN_FM_TO_CUSTOMERS,
ADDI_ASSIGN_FM_TO_SUPPLIERS, ADDI_IDOC_REQUEST,
ADDI_MATNR_MASS_ASSIGN, ADDI_MONITOR, ADDI_ORDERS_CREATE,
ADDI_PR_IDOC_REQUEST, ADDI_STWB_REQUEST,
RWRF_ADDI_ANALYSIS_OF_CHANGES, RWRF_ADDI_IDOC_GENERATE are
used.
This also can be checked via transaction SE16N. Enter table WTADDI and check
whether there are any entries.
59.10S4TWL - Article Discontinuation
Application Components:IS-R, IS-R-BD-ART, IS-R-BD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368683
S4TWL - Article Discontinuation via
transactions WSE*
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1355
In SAP S/4HANA article discontinuation via transactions WSE1, WSE2, WSE3, WSE4,
WSE5 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, WSE5
are used.
Other Terms
WSE1, WSE2, WSE3, WSE4, WSE5, WRF_DIS_SEL, and
WRF_DIS_MON, SYSTEM_ABAP_ACCESS_DENIED
59.11S4TWL - GDS simplified Inbound Price Catalog Interface
Application Components:IS-R-BD-PCT-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2340264
S4TWL - Global Data Synchronization
(GDS)
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using GDS
funcionality. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Solution
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 transactions PRICAT* (PRICAT, PRICATCUS1, PRICATCUS2, PRICATCUS3,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1356
PRICATCUS6, PRICATCUS7, PRICATLOG, PRICATLOGOUT) are 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.
59.12S4TWL - Business Partner in Site Master
Application Components:LO-RFM-MD, IS-R-BD-SIT, LO-MD-PL, LO-RFM, LO-RFM-MD-SIT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2339008
S4TWL - Business Partner for Sites
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using sites in your
source system. The following SAP S/4HANA Transition Worklist item is applicable in
this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1357
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
This Simplification Item is relevant if retail sites are used.
Relevance of this note can be checked via transaction SE16N. Enter table T001W and
check whether there are entries with field VLFKZ (Plant Category) not equal blank.
For functionality not availble anymore, please check whether transactions
WRFCATEGORYSHOP, WRFCLOSESHOPS, WRFDELIVERYSITESHOPS,
WRFREGIONSHOPS, WRFSHOPCAT, WRFSHOPDEP, WRF_ARC_DEPSHOP,
WRF_TCHAIN_MIGR, WSHOPMIGR are used.
59.13S4TWL - Logistical Variant
Application Components:IS-R, IS-R-BD-ART, IS-R-BD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368655
S4TWL - Logistical Variants
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1358
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
prior to SAP S/4HANA 1809. Starting with SAP S/4HANA 1809 FPS01 there is the so
called Logisical Product which offeres functionality that addreesses a similar business
requirement, for functional scope see referenced note.
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.
59.14S4TWL - Article Hierarchy
Application Components:IS-R-BD-CDT, IS-R, IS-R-BD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368680
S4TWL - Article Hierarchy via
transactions MATGRP*
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1359
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 hierarchy maintenance via transactions MATGRP* is not
available anymore.
Article hierarchies should be maintained via transactions WMATGRP* which are richer
in functionality than transactions MATGRP*.
It is possible to migrate MATGRP Article Hierarchies to WMATGRP Article Hierarchies
before doing the SAP S/4HANA system conversion, see referenced note 2536676.
Required and Recommended Action(s)
Switch to article hierarchies via transactions WMATGRP*.
In case you reuse ABAP objects of packetCL_MD in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if article hierarchy of this type is used.
This is the case if transactions MATGRP01, MATGRP02, MATGRP03, MATGRP04,
MATGRP05, MATGRP06, MATGRP07 are used.
This also can be checked via transaction SE16N. Enter table MATGRP_HIER and check
whether there are any entries.
59.15S4TWL - Market Basket Calculation
Application Components:LO-MD, LO-MD-RPC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368716
S4TWL - Market Basket Calculation
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1360
Solution
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)
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.
In case you reuse ABAP objects of Market Basket Calculation in your custom code,
please see attached note.
How to Determine Relevancy
This Simplification Item is relevant if market basket calculation is used.
This is the case if transactions WKK1, WKK2, WWK3, WKK4 are used.
This also can be checked via transaction SE16N. Enter table WWKK, or WWKP and
check whether there are any entries.
59.16S4TWL - Merchandise and Assortment Planning (ERP based)
Application Components:LO-MAP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368741
S4TWL - Merchandise and Assortment
Planning (ERP based)
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1361
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
In case you reuse ABAP objects of packets CM_MAP or WIS_PLAN in your custom
code, please see attached note.
How to Determine Relevancy
This Simplification Item is relevant if Merchandise and Assortment Planning/category
management is used.
This is the case if transactions WSUP, WXP*
(WXP0, WXP01, WXP02, WXP03, WXP04, WXP05, WXP06, WXP07, WXP08,
WXP09, WXP1, WXP10, WXP11, WXP12, WXP13, WXP14, WXP15, WXP16,
WXP17, WXP18, WXP19, WXP2, WXP20, WXP21, WXP22, WXP23, WXP24,
WXP25, WXP26, WXP27, WXP28, WXP29, WXP3, WXP30, WXP31, WXP32,
WXP33, WXP34, WXP35, WXP36, WXP37, WXP38, WXP39, WXP4, WXP40,
WXP41, WXP42, WXP43, WXP44, WXP45, WXP46, WXP47, WXP48, WXP48_OLD,
WXP49, WXP5, WXP51, WXP52, WXP53, WXP54, WXP55, WXP56, WXP57,
WXP58, WXP6, WXP60, WXP61, WXP62, WXP63, WXP64, WXP65, WXP66,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1362
WXP67, WXP68, WXP69, WXP7, WXP70, WXP74, WXP75, WXP8, WXPA, WXPB,
WXPC, WXPD, WXPE, WXPF, WXPG, WXPH, WXPI, WXPJ, WXPN1, WXPN2,
WXP_IMG),
or CMMAP*
(CMMAP01, CMMAP02, CMMAP03, CMMAP04, CMMAP05) 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.
59.17S4TWL - Retail Method of Accounting
Application Components:IS-R-LG-RMA, IS-R, IS-R-LG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368736
S4TWL - Retail Method of Accounting
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1363
In case you reuse ABAP objects of packets WRMA_* your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if Retail Method of Accounting is used.
This is the case if transactions WRMA_1, WRMA_C1, WRMA_CHECK,
WRMA_DATA_DISPLAY, WRMA_DIAG_R3, WRMA_M1, WRMA_M2,
WRMA_NO_DOC, WRMA_VALUES, WRMA_WRART are used.
This also can be checked via transaction SE16N. Enter table WRMA_CLIENT and check
whether there are any entries, and whether there are entries in table WRMA_PROFILE.
59.18S4TWL - Fresh Item Procurement
Application Components:MM-PUR, MM-PUR-FIP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368747
S4TWL - Fresh Item Procurement
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1364
In case you reuse ABAP objects of packets FIP_* in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if fresh item procurement is used.
This is the case if transactions FIP_*
(FIP_MD, FIP_SD, FIP_TD, FIP_CALL_MM03, FIP_CALL_MM43,
FIP_CALL_RP_WL_DELE, FIP_CALL_RP_WL_DISP, FIP_CALL_WF30,
FIP_CALL_WSUBST_CTAB, FIP_CALL_WSUBST_WL,
FIP_RP_WORKLIST_DELE, FIP_RP_WORKLIST_DISP)
are used.
59.19S4TWL - Retail Ledger / Profit Center Analytics
Application Components:FI-RL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368803
S4TWL - Retail Ledger / Profit Center
Analytics
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1365
Strategic planning solutions are SAP Merchandise Planning for Retail, and
SAP Assortment Planning for Retail.
In case you reuse ABAP objects of packet WRTL in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if profit center analytics is used.
This is the case if transactions RETAIL_* (RETAIL_ACTIVATE, RETAIL_BLOCK,
RETAIL_GB01, RETAIL_GCU1, RETAIL_GCU3, RETAIL_GCU6, RETAIL_GVTR,
RETAIL_ITEMS, RETAIL_SUBPOST, RETAIL_TOTALS, RETAIL_VERSIONS,
RTDE) are used.
This also can be checked via transaction SE16N. Enter table PCRRETAILA and check
whether there are any entries.
59.20S4TWL - Goods Receipt Capacity Check
Application Components:MM-PUR-OPT, MM-PUR, MM-PUR-OPT-GRC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368785
S4TWL - Goods Receipt Capacity
Check
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1366
Required and Recommended Action(s)
There is no equivalent functionality to goods receipt capacity check available in SAP
S/4HANA.
In case you reuse ABAP objects of packet WGRC in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if goods receipt capacity check is used.
This is the case if transactions WGRC1, WGRC2, WGRC3, WGRC4, WGRC5, WGRC6
are used.
This also can be checked via transaction SE16N. Enter table WGRC_ACT,
WGRC_ACT_PO and check whether there are any entries.
59.21S4TWL - Online Store
Application Components:LO-MD-PC, LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368835
S4TWL - Online Store (IAC)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1367
SAP Hybris Commerce is the strategic solution for omnichannel commerce.
In case you reuse ABAP objects of packet WWMB in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if online store is used.
This is the case if transactions WW10, WW20, WW30, WW31 are used.
59.22S4TWL - Generic Article Harmonization
Application Components:LO-RFM, LO-RFM-MD-ART, LO-RFM-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2339010
S4TWL - Generic Article Harmonization
Symptom
You want to convert your SAP ERP for Retail/Fashion system to an SAP S/4HANA
system and you want to use existing generic articles in SAP S/4HANA. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
The way of storing characteristic valuations of variants of a generic article and a
configurable material were different.
Solution
Description
With S/4HANA, generic article harmonization with configurable materials
becomes available. With that a generic article is assigned to a configuration class and the
variant-creating characteristics for that generic article are taken from that configuration
class. The valuation of the variant-creating characteristics of the variants is stored within
the configuration storage (IBase). For this reason, the existing generic articles, the
variant-creating characteristics and the variants need to be migrated during the upgrade.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1368
As the variant-creating characteristics are no longer linked to a merchandise category or
characteristics profile, but to configuration classes, a re-classification of the merchandise
category/characteristics profile of a generic article is no longer restricted by the
assignment of variant-creating characteristics to merchandise categories/characteristics
profiles.
As a consequence of the data model change the following functionality is not available
anymore:
Assigning a single article to a generic article via report MMASSIGNMAT, see also
attached note 2772474
Transforming a variant of a generic article to a single article via
report MMUNHINGEVAR
Characteristic value change of a variant of a generic article via
report MMCHANGEVAR
Convert Material Master data to Article Master data via report RMMMMPOI
(transaction WRST); starting with SAP S/4HANA 1909
report RFM_CONV_MATERIAL_TO_ARTICLE is available which has similar
functionality, see note 2843173.
Required and Recommended Action(s)
The complete data migration process is divided into three phases: manual started pre-
migration activities, automated migration processes during downtime, and manual started
post-migration activities.
The 1st phase includes the required manual execution of Pre-Migration reports in the
SAP ERP for Retail system in all clients. Please implement the SAP Note 2331707 to get
the pre-migration reports.
The 2nd phase includes the automatic execution of another migration report which will
be executed by the SUM tool during the downtime.
The 3rd and the last phase includes the recommended manual execution of a Post-
Migration report in the converted SAP S/4HANA system in all clients. Please refer to
SAP Note 2350650 for more details.
How to Determine Relevancy
This Simplification Item is relevant if generic articles and variants are used.
This can be checked via transaction SE16N. Enter table MARA and check whether there
are entries with field ATTYP (Material Category) 01 (generic article) or 02 (variant).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1369
Other Terms
SAP S4HANA
59.23S4TWL - Retail Labeling
Application Components:LO-ADM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368870
S4TWL - Retail Labeling
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
In case you reuse ABAP objects of packet WETI in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if labeling is used.
This is the case if transactions WEBU, WENA, WESO are used.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1370
59.24S4TWL - Seasonal Procurement
Application Components:IS-R, IS-R-PUR-POF, IS-R-PUR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368913
S4TWL - Seasonal Procurement
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
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.
In case you reuse ABAP objects of packets WRF_AT_GENERATE,
WRF_PRC_BASIC_APPL, WRF_PRC_BASIC_DDIC, WRF_PRC_CON_APPL,
WRF_PRC_CON_DDIC, WRF_PRC_EM_AI, WRF_PRC_MAIN,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1371
WRF_PRC_OTB_APPL, WRF_PRC_OTB_DDIC, WRF_PRC_POHF_APPL,
WRF_PRC_POHF_APPL_SFWS_SC, WRF_PRC_POHF_DDIC,
WRF_PRC_POHF_DDIC_SFWS_UI_VS, WRF_SEAS in your custom code, please see
attached note
How to Determine Relevancy
This Simplification Item is relevant if seasonal procurement is used.
This is the case if transactions, WRFAPC01, WRFAPC02, WRFAPC03, WRFAPC11,
WRFAPC12, WRFAPC14, WRFAPC15, WRFAPC16, WRFAPC17, WRFAPC22,
WRFAPC23, WRFAPC24, WRFAPC25, WRFAPC26, WRFAPC27, WRFAPC30,
WRFAPC35, WRFAPC36, WRFAPC37, WRFAPC40, WA10, WCOC, WCOCS,
WOTB1, WOTB2, WOTB3, WOTB4, WOTB6, WPCTRA, WPCTRD, WPCTRQ,
WPOHF1, WPOHF2C, WPOHF2D, WPOHF2DS, WPOHF2X, WPOHF2XS,
WPOHF3C, WPOHF3D, WPOHF3DS, WPOHF3X, WPOHF3XS, WPOHF4C,
WPOHF4D, WPOHF4DS, WPOHF4X, WPOHF4XS, WPOHF7, WPOHF8,
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.
59.25S4TWL - Replenishment
Application Components:IS-R-PUR-RP, IS-R-PUR, IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370106
S4TWL - Retail Replenishment
Symptom
You are doing a system conversion to SAP S/4HANA Retail for merchandise
management or SAP S/4HANA for fashion and vertical business. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1372
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
A) In SAP S/4HANA, some retail specific replenishment functionality (main transaction
WRP1) and multi-step replenishment (transactions WRFE, WRSO, WRSR, ...) are not
available anymore.
B) Generic Materials Requirements Planning (MRP) functionality is available (main
transaction MD01). For details see referenced note.
MRP Live (transaction MD01N) is available. Certain retail specfics available in SAP
ERP in transactions MD01 are not available in MRP Live (neither in SAP ERP nor SAP
S/4HANA):
- Determination of internal supply source (e.g. distribution center as supply source for
store)
- Considering the specifics of structured articles (such as display, sales sets, prepack)
- Promotion check
Required and Recommended Action(s)
A) Rapid Replenishment (transaction WRP1R) covers a similar scope, but is superior
from a performance perspective.
B) Use "classic" MRP (transaction MD01)
How to Determine Relevancy
This Simplification Item is relevant if replenishment is used in SAP Merchandising for
Retail or SAP Fashion Management Solution.
This is the case if transactions WR30, WR31, WR94, WR95, WRP1, WRFE, WRSO,
WRSR, are used.
59.26S4TWL - Retail Information System
Application Components:IS-R-IS, IS-R-IS-RIS, IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370131
S4TWL - Retail Information System
(RIS) and Category Management
Workflow
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1373
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 and Category Management Workflow are not
available anymore.
Required and Recommended Action(s)
RIS (Retail Information System) technology is not available anymore.
To cover reporting requirements usage of SAP BW or SAP BW/4HANA is
recommended.
There is content for Retail for SAP BW, which however does not cover an identical scope
as RIS.
There is no retail specific content for SAP BW/4HANA. Thus, content need to be created
or adjusted part of the implementation project.
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. Till then,
content need to be created part of the implementation project.
In case you reuse ABAP objects of packets WRB or WRBA in your custom code, please
see attached note.
Information structure S160 is used for perishables procurement. In SAP
S/4HANA, perishables procurement is not available from release SAP S/4HANA 1610
till 1909. Starting with SAP S/4HANA 2020 perishables procurement is available again.
Thus, information structure S160 can be used from SAP S/4HANA 2020. It is planned to
substitute functionality of information structure S160 by CDS technology in a future
release.
Coding for retail specific enhancements is controlled via settings in table TMCW. Please
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1374
deactivate all settings, or delete the entry in table TMCW. Active settings can lead to
reduction in performance or even errors. You can maintain entries in table TMCW
through transaction SM30 view V_TMCW.
How to Determine Relevancy
This Simplification Item is relevant if RIS is used.
This 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.
Custom specific RIS structures can be detected via transaction SE16N for table TMC4
with TMC4-MCAPP = 40 and TMC4-KBTCH is not initial (i.e. = 1, 2, 3, D).
RIS structure S160 may be active as it is used for Perishable Procurement, see
note 2368739.
If you have RIS structures with activated updating, and want to convert from ECC to
S/4HANA, please deactivate updating prior to the conversion via transaction MCH6.
Relevant transaction are CMPRO, MC1!, MC1$, MC1§, MCG2, MCG3, MCGC,
MCGD, MCGE, MCGF, MCGG, MCGH, MCGJ, MCGK, MCGL, MCH+, MCH0,
MCH1, MCH2, MCH3, MCH4, MCH7, MCH8, MCH9, MCH:, MCHA, MCHB,
MCHC, MCHD, MCHG, MCHP, MCHS, MCHV, MCHY, MCHZ, MCH_, MCM%,
MCMX, MCMY, MCMZ, MCWIS, MCWRP, T108, T109, T110, T111, T112, T113,
T114, T115, TR02, WCM1, WCM2, WCM3, WCM4, WCMA, WCMB, WCMC,
WCMCP, WCMD, WCME, WDKR.
In case you reuse ABAP objects of packets CM_WF, MCW, WVKP_RRM, WWGR in
your custom code, please see attached note.
This Simplification Item is relevant if Category Management Workflow is used.
This also can be checked via transaction SE16N. Enter table WCMP and check whether
there are any entries.
Other Terms
RIS, Retail Information System, LIS, Logistics Information System, BW/4HANA, Retail
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1375
59.27S4TWL - SAP Retail Store
Application Components:LO-SRS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370133
S4TWL - SAP Retail Store
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
SAP Retail Store and SAP In-Store Merchandise and Inventory Management Mobile
(Java) enhanced and optimized tools available for executing store-oriented processes by
providing store associates with specially developed store management functions. It
offered a web-based user interface that was tailored specifically to the requirements of
stores.
Business Process related information
In SAP S/4HANA, SAP Retail Store and SAP In-Store MIM Mobile (Java) are 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 (Web Dynpro ABAP).
Because of the Business Partner harmonization the WebDynpro WDA_WSSD_CUST
cannot be used in releases prior to SAP S/4HANA 2022, only displaying an existing
customer is possible. The respective
BAPIs BAPI_CUSTOMER_CREATEFROMDATA1
and BAPI_CUSTOMER_CHANGEFROMDATA1 are not available as well. The
WebDynpro app has been adjusted for SAP S/4HANA 2022 and can be used gain.
As an alternative, customer master data can be maintained through the Fiori app Manage
Customer Master Data (F0850A). If you need to adjust the app to your specific needs,
consulting note 2655797 describes how this can be achieved.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1376
It is planned to deprecate the WebDynpro app for sales order maintenance
(LO_OIF_MAIN_APP, LO_OIF_SDOC_APPL) with SAP S/4HANA 2023. You need to
switch to suitable Fiori apps for sales order maintenance by then.
How to Determine Relevancy
This Simplification Item is relevant if SAP Retail Store or SAP In-Store MIM Mobile
(Java) is used.
This is the case if transactions
RFAF
RME2N
SRS_GM_SH
SW_WW10
WCSO
WCSO_ENTRY
WCSOC
WCSOD
WCSOS
WCU2
WOSCR_CBL
WOSCR_EXI
WOSCR_SLOGIN
WOSZ_MAT_SHOW
WOSZ_PRINTER
WSAK
WSAM_ENTRY
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1377
WSAM_SHMAE
WSAM_SHMAE
WSAO_CYCLE
WSAO_LKPLC
WSAU
WSGM
WSHT
WSII_ENTRY
WSPO_ENTRY
WSSW
WSTA
WSTA_R_DLV_DISP
WSTA_R_PDC_DATA
WSTA_R_PDC_STRUCT
WSTE_R_PDC_CUSTOMIZ
WSTE_R_PDC_DOCUMENT
WSTE_R_PDC_GR
WSTE
WSTE_NEW
WSTED
WSTI
WSTI_DOC
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1378
WSTI_MON
WSTI_R_PDC_PI
WSTL
WSTP
WSTSA
WSTU
WSTV
WSTV_R_PDC_CUST
WSTV_R_PDC_DATA
WSTV_R_PDC_MATDATA
WSVD_ENTRY
WSVD_SAPGUI
WSVD_VNDR_WLIST
WTAD_SRS
WTAD_STWB
WebDynpro WDA_WSSD_CUST /sap/bc/webdynpro/sap/WDA_WSSD_CUST
WebDynrpro LO_OIF_MAIN_APP /sap/bc/webdynpro/sap/LO_OIF_MAIN_APP
WebDynrpro LO_OIF_SDOC_APPL /sap/bc/webdynpro/sap/LO_OIF_SDOC_AP
PL
are used. This is not a complete list.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1379
59.28S4TWL - Retail iViews
Application Components:MM-PUR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370183
S4TWL - Retail Buying iViews
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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. Transactions
WRBDL, WRBDL2 are not available anymore.
Required and Recommended Action(s)
In SAP S/4HANA there are alternatives to display the information.
For stock information there is transaction RWBE or the Fiori apps for inventory
management.
For open purchase orders there are transaction ME2L, ME2M, ME2N or the purchase
order Fiori app.
In case you reuse ABAP objects of packet WRB or WRBA in your custome code, please
see attached note.
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,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1380
WRB_RFC_VENDOR_GET_CONTACTDATA are called, or transactions WRBDL,
WRBDL2, or report RWRBADSL is executed
59.29S4TWL - Prepack Allocation Planning
Application Components:IS-R-BD, IS-R, IS-R-BD-ART
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370151
S4TWL - Prepack Allocation Planning
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
In case you reuse ABAP objects of packet WSTRN in your custom code, please see
attached note.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1381
This also can be checked via transaction SE16N. Enter table WSTN_PP_HEADER and
check whether there are any entries.
59.30S4TWL - Assortment List
Application Components:IS-R-IFC, IS-R, IS-R-IFC-AL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370146
S4TWL - Assortment List
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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
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
WDBI_HPR, WDBM_HPR, WDBU_HPR.
WDBI_HPR_ALV, WDBM_HPR_ALV, WDBU_HPR_ALV 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1382
59.31S4TWL - In-store food production integration
Application Components:LO-MD-FPD, LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370148
S4TWL - In-store food production
integration
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
In case you reuse ABAP objects of packets WSFP_* in your custom code, please see
attached note.
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1383
PhysicalInventoryCountERPRequest_Out
PhysicalInventoryCountERPCreateRequest_In
PhysicalInventoryCountERPConfirmation_In
GoodsMovementERPCreateRequest_In
GoodsMovementERPNotification_Out
are used.
59.32S4TWL - PRICAT Outbound
Application Components:IS-R-BD, IS-R-BD-PCT, IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370164
S4TWL - PRICAT Outbound
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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 and price
information.
The alternatives include e.g.:
Article data combined with prices
WES SOAP Service ReplicateMerchandiseDemandManagement
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1384
DRF SOAP Service ProductMerchandiseViewReplication (available with
SAP S/4HANA 1909)
Assortment List IDoc
Article data
DRF SOAP Service ProductMDMBulkReplicate (available with SAP
S/4HANA 2020)
ARTMAS IDoc
Prices
DRF SOAP Service SalesPricingConditionRecord (available with SAP
S/4HANA 1909)
COND_A IDoc
In case you reuse ABAP objects of packet VPRI in your custom code, please see attached
note.
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, WPRI6,
WPRI7, PRICREAT are used.
This also can be checked via transaction SE16N. Enter table PRICAT_K001 and check
whether there are any entries with field PRICAT_K001-PRIOUTSTATE not equal blank.
59.33S4TWL - Retail Business Function Harmonization
Application Components:LO-RFM-SWT, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2339317
S4TWL - Retail Business Function
Harmonization
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1385
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
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)
For details see referenced note 2304479 and 2303155.
In case you have activated one of the following Business Functions, but don't use the
functionality, please, create an incident, and we will release the respective pilot note for
you:
- ISR_RETAIL_INDIA_LOC
- ISR_RET_PERISH_PROCUREMENT
- ISR_RETAIL_MAP_IF
- ISR_RETAIL_MAP_IF2
- ISR_RETAIL_INSTORE_FPD
- ISR_RETAIL_RMA
- ISR_RETAIL_RMA_2
- ISR_RETAIL_RMA_3
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.
59.34S4TWL - Retail Obsolete Transactions
Application Components:IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370655
S4TWL - Retail Obsolete Transactions
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1386
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
With the installation of the SAP S/4HANA, certain transactions will not be available
anymore.
Business Process related information
Transactions which are not available anymore in SAP S/4HANA are listed below.
Required and Recommended Action(s)
Obsolete Transaction
Description of Transaction
Alternative Transaction
CLWA
Create Material Group (MMS)
was already obsolete in SAP
ERP
CLWB
Change Material Group (MMS)
was already obsolete in SAP
ERP
CLWC
Display Material Group (MMS)
was already obsolete in SAP
ERP
CLWD
Delete Material Group (MMS)
was already obsolete in SAP
ERP
CLWJ
Change Generic Article (MMS)
was already obsolete in SAP
ERP
CLWK
Display Generic article (MMS)
was already obsolete in SAP
ERP
CLWL
Delete Generic Article (MMS)
was already obsolete in SAP
ERP
FSH_MD04_DEBUG
FM : Stock Requirement List :
Debug
was already obsolete in SAP
ERP
FSH_SDM_AGG
FM : Stock Demand Mapping
Aggregator
was already obsolete in SAP
ERP
RDMBBYCOPY
Copy Bonus Buy
RDMBBYCOP2
RDMBBYDELE
Delete Bonus Buy
RDMBBYDEL2
WTRA1
Maintain Runtime Customizing
Table
not relevant anymore
WTRA2
Runtime Measurement: Delete
Logs
not relevant anymore
WTRA3
Runtime Measurement: Display
Logs
not relevant anymore
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1387
WA05
Alloc Tbl FDG: Generate POs
was already obsolete in SAP
ERP
WA06
Alloc Tbl FDG: Generate
Deliveries
was already obsolete in SAP
ERP
WA07
Alloc Tbl FDG: Generate Wrhse
Orders
was already obsolete in SAP
ERP
WA12
Create Reminders/Accept Plnd
Qties
was never released
WA15A
Mess.Deter., Alloc Tbl:
Creat.Cond.R
WA/A
WA15B
Mess.Deter.,Alloc Tbl: Chng
Cond.Rec
WA/B
WA15C
Mess.Deter.Alloc Tbl: Displ
Cond.Rec
WA/C
WA40
Adjust Alloc Tbl After Entering GR
was already obsolete in SAP
ERP
WA50
Generate Allocation Rule
obsolete because of deprecated
RIS
WA53
Create Selection Variants
obsolete because of deprecated
RIS
WA54
Generate Alloc Rule / Test RIS-L
obsolete because of deprecated
RIS
WA60
Create Selection Variant for PO
obsolete because of deprecated
RIS
WC11
Batch Changes, Assortments
batch transaction of WSM4
WC21
Batch Reorg Data in LIS
batch transaction of of
deprecated RIS
WC25
Batch Assortment List/Shelf-Edge
Lab
batch transaction of obsolete
WDBU
WC26
Batch Forecast
batch transaction of MP38
WC27
Batch Requirements Planning per
Plnt
batch transaction of MD01
WC33
Assortment List: Initial. & FullVers
batch transaction of obsolete
WDBI
WC41
Batch worklist for doc. index
batch transaction of MEI4
WCMP_MASS
Mass Complaints Processing
not relevant anymore
WCMP_PROCESSING
Complaints Processing
not relevant anymore
WCMP_RESULT
Results Log Mass Complaints
Proc.
not relevant anymore
WER_RULE_PROC_TES
T
Test program for processing rules
test transaction
WB07
Change plant/customer
assignment
not relevant anymore
WB08
Change plant/vendor assignment
not relevant anymore
WB30
Mass maintenance MG to plant
WB30N
WB35
Layout overview
obsolete because of deprecated
RIS
WBTE
Export plant data (file transfer)
not relevant anymore
WBTI
Import plants (file transfer)
not relevant anymore
WBTIMEX
Site Master Transport
not relevant anymore
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1388
WBTIMEX_CUST
Customize Site Master Transport
not relevant anymore
WDH1
Maintain plant hierarchy (SD)
not relevant anymore
WDH2
Display customer hierarchy (SD)
not relevant anymore
WOG3
Plant groups
was already obsolete in SAP
ERP
WF10A
Collective PO Without Tabstrips
WF10
WF50A
Adjust Distribution
WF50
WF80_DEL
Display Delivery Generation Logs
WF80
WF90_DEL
Delete Delivery Generation Logs
WF90
WLB3
Autom. opt. PO-based load
building
WLB13
WGDS_CONFIRM
Send confirmation
not relevant anymore
WGDS_CONFIRM_MANA
GER
Confirmation manager
not relevant anymore
ARTE
Replace Articles in Layout
Modules
not relevant anymore
WLAM
Layout Maintenance
WLWBN
WLMM
Layout Module Maintenance
WLWBN
WLMV
Maintenance of Layout Module
Version
WLWBN
WLWB
Layout Workbench
WLWBN
WPER_ALV
POS Interface Monitor
WPER
WPLG
Space Management
WPLGN
WRFMATCHARVAL
Char. Value Change to Variants
not relevant anymore
WRF_WSOA1
Create Assortments
WSOA1
WRF_WSOA2
Change Assortments
WSOA2
WRF_WSOA3
Display Assortments
WSOA3
WRF_WSOA4
Delete Assortment
WSOA4
W_PRICAT_ASSIGN_001
Assignment ILN Vendor Pur.
Group
not relevant anymore
W_PRICAT_ASSIGN_003
Assignment SAP Mat. Gr. -
Purch.Gr.
not relevant anymore
W_PRICAT_SEL_CREAT
E
Maintain Price Catalog
not relevant anymore
WRF_PRICAT_LOG1
Log for Price Catalog
not relevant anymore
WSFP_LOG_ALL_IN
Ind Processing, All Logs
WESLOG
WSFP_LOG_ALL_OUT
All Logs
WESLOG
WSFP_LOG_CHG_OUT
Change Messages Log
WESLOG
WSFP_LOG_INIT_OUT
Initial Data Transfer
WESLOG
WSFP_LOG_INTERNAL
For Internal Use Only
WESLOG
WSFP_LOG_MAN_OUT
Manual Selection
WESLOG
WSFP_TRANSFER
Master Data Transfer
WESOUT
WLAN
Listing Conditions for Layout
Module
not relevant anymore
WSK3
Assortment copy, batch input
not relevant anymore
WSL3
Material listed in plant before?
WSL11
WSL4
Analyze material in module
not relevant anymore
WSL5
Modules in plant
not relevant anymore
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1389
WSL6
Assortment structure, Plants
not relevant anymore
WSL7
Vendor material list
not relevant anymore
WSLA
Assortment Users per Assortment
not relevant anymore
WSLB
Assortment per Assortment User
not relevant anymore
WSLG
Compare promotion POs - sales
orders
was already obsolete in SAP
ERP
WSM4
Relist after ch. plant/ mat. grp mas
was already obsolete in SAP
ERP
WSM6
Delete Individual Listing, Material
WSE6
WSM7
Delete Individual Listing, Material
WSE6
WSM8
Setup assrt.owner assortment as
WRF6
WSM3
WSOA5
Assign assortment to customer
WSOA2
WSOE
Assign material groups
was already obsolete in SAP
ERP
WSP6
Delete ind. listing, mat. - plant
WSE6
WSOSDISPLAY
Display Possible Sources of
Supply
not relevant anymore
MGW0
Create Components for Set
Material
was already obsolete in SAP
ERP
MGW1
Display Components for Set
Material
was already obsolete in SAP
ERP
MGW2
Create Components for Display
Matl
was already obsolete in SAP
ERP
MGW3
Display Components for Display
Matl
was already obsolete in SAP
ERP
MGW4
Create Components for Prepack
Matl
was already obsolete in SAP
ERP
MGW5
Display Components for Prepack
Matl
was already obsolete in SAP
ERP
MGW6
Create Components for Full
Product
was already obsolete in SAP
ERP
MGW7
Display Components for Full
Product
was already obsolete in SAP
ERP
MGW8
Change Components for Set
Material
was already obsolete in SAP
ERP
MGW9
Change Components for Display
Matl
was already obsolete in SAP
ERP
MGWA
Change Components for Prepack
was already obsolete in SAP
ERP
MGWB
Change Components for Full
Product
was already obsolete in SAP
ERP
DUMMY_MASS_VENDO
R
Load programs global data
not relevant anymore
MASS_VENDOR
Vendor Mass Maintenance
not relevant anymore
WMATGRP06
Copy Article Hierarchy
WMATGRP06N
WMATGRP08
Simulation of Article hierarchy
copy
WMATGRP08N
WDKR
Create customer from vendor
not relevant anymore
WAHD1
Load Alternative Historical Data
MAHD1
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1390
WAHD2
Change Alternative Historical Data
MAHD2
WAHD3
Display Alternative Historical Data
MAHD3
WAHD4
Delete Alternative Historical Data
MAHD4
WDRD1
Determine Delivery Relationship
MDRD1
WDRD2
Change Delivery Relationship
MDRD2
WDRD3
Display Delivery Relationship
MDRD3
WDRD4
Delete Delivery Relationship
MDRD4
How to Determine Relevancy
This Simplification Item is relevant if any of the above listed transactions is used.
59.35S4TWL - Value and Quota Scales
Application Components:IS-R, IS-R-BD, IS-R-BD-MC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2340247
S4TWL - Value and Quota Scales
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1391
Required and Recommended Action(s)
Switch to strategic functionality of distribution curves.
In case you reuse ABAP objects of packet WMOD in your custom code, please see
attached note.
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, WVAL are used.
This also can be checked via transaction SE16N. Enter table WMQK, or WMWK and
check whether there are any entries.
59.36S4TWL - AIN
Application Components:XX-CSC, XX-CSC-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370138
S4TWL - AIN (India Margin Protection)
(Localization for India)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1392
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.
In case you reuse ABAP objects of packet J1IRET inn your custom code, please see
attached note.
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.
59.37S4TWL - SAP Smart Business for Retail Promotion Execution
Application Components:LO-MD-PR, LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2377767
S4TWL - SAP Smart Business for Retail
Promotion Execution
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
Description
SAP Smart Business for Retail Promotion Execution offers insight-to-action capabilities
based on real-time overviews to mitigate exceptions for promotion execution.
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1393
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)
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.
59.38S4TWL - Retail Factsheets
Application Components:LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2377780
S4TWL - Retail Factsheets
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
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)
Starting with SAP S/4HANA 1709 Object Pages for product, site and allocation table are
available. Starting with SAP S/4HANA 1709 FPS01 Object Page for promotion is
available. The development of further Object Pages are under evaluation for future
releases.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1394
59.39S4TWL - Retail Short Text Replacement
Application Components:LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2377816
S4TWL - Retail Short Text Replacement
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
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.
In the meantime, there is a workaround available. Please refer to note 2712569 for further
information.
How to Determine Relevancy
This Simplification Item is relevant if retail short text replacement is used.
Call transaction MM41. If it reads "Create Article" the replacement is used, if it reads
"Create Material" it is not used.
59.40S4TWL - Subsequent Settlement - Vendor Rebate Arrangements
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1395
Application Components:MM-PUR-VM-SET
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267415
S4TWL - Subsequent Settlement -
Vendor Rebate Arrangements
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Business Value
Condition Contract Management is superior to Subsequent Settlement. It offers the
following advantages:
Central, standardized solution for the administration of supplier and customer
conditions
Transparency which documents are relevant and related to each other
Detailed overview of settlements
Flexible settlement calendar
Support of various data sources to allow modelling of flexible scenarios (including,
but not limited to sales-related rebates, scanback rebates, customer funds,
purchase-related-rebates)
Fully integrated with the Order-to-Cash and the Procure-to-Pay Processes
Designed for high performance
Architected to benefit from SAP HANA
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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1396
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, on-premise
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
SAP Notes: 2194923, 2215220
Related SAP Notes
SAP Note: 73214
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1397
59.41S4TWL - Segmentation (from 1809 onwards)
Application Components:LO-RFM, LO-RFM-SGT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2652842
S4TWL - Segmentation (from 1809)
Symptom
You are doing a system conversion to SAP S/4HANA 1809 or higher, and you are
using segmentation related busines applications. The following SAP S/4HANA
Transition Worklist item is applicable in this case
Solution
Description
In SAP S/4HANA segmentation is available, but has some diiferences compared to SAP
ERP which need to be considered.
Business Process related information
The differences in segmentaion between SAP ERP and SAP S/4HANA are the following:
In SAP S/4HANA segmentation strategies 1:n and n:m are available for MRP and
supply asignment.
In SAP S/4HANA segmentation strategies 1:n and n:m are not available for advanced
ATP. Advanced ATP supports Pool Segment only.
Segmentation is considered only in the advanced ATP (aATP). The classic ATP is not
supported anymore.
Stock protection in SAP ERP is implemented via segmentation. In SAP S/4HANA
stock protection can be achieved via product allocation (PAL).
In SAP S/4HANA, the default segmentation can be maitained via a specific
transaction (SGT_DEFAULT).
In SAP S/4HANA transactions to configure segmentation structures and strategies
(SGTS, SGTC) are now available in the application (vs. customiting in SAP
ERP).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1398
In SAP S/4HANA MRP related article/material master data on segment level are not
available anymore.
In SAP S/4HANA segmentation maintenance in the article/material master has been
simplified compared to SAP ERP (e.g. automatic fixing of the segmentation
strategy during article and listing maintenance).
In SAP S/4HANA the transaction LS24 doesn’t support the “Refresh” button
anymore
PRC planning level (SGT_PRPL) and Consecutive Number for Segmentation of
Equal Status (SGT_CNES) fields are not supported anymore
Safety stock is supported only at Default stock segment level (vs stock segment level
in SAP ERP)
Segmentation is considered only in MRP live (MD01N). The classic MRP is not
supported.
In SAP S/4HANA segmentation is not supported in the following applications:
Quality Management (QM)
Production Planning - Detailed Scheduling (PP-DS)
Process Order
Project stock
Demand-Driven MRP (DDMRP)
Predictive MRP (pMRP)
Segmentation structure and strategy are not considered in EWM
Spare Parts Planning (SPP)
In SAP S/4HANA, the following fields are not available:
Discrete Batch Number (SGT_CHINT)
Stock Protection Indicator (SGT_STK_PRT)
Consumption Priority (SGT_PRCM)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1399
ATP/MRP Status for Material and Segment (SGT_MRP_ATP_STATUS)
Date from which the plant-specific material status is valid (SGT_MMSTD)
In SAP S/4HANA, the following transactions are not available:
SGT_CONVERT_MATERIAL
SGT_MAINTAIN_VALT
SGT_MASS_EXTD_MAT
Required and Recommended Action
Part of the conversion from SAP ERP to SAP S/4HANA, article need to be resasigned
from "old" to "new" segmentation, please see referenced note.
Implemented business processes need to be adjusted according to the changes listed
above.
How to Determine Relevancy
This Simplification Item is relevant if segmentation is used.
This can be checked via transaction SE16N. Enter table SGT_COVS_T and check
whether there are entries.
There is also a pre-check class CLS4SIC_SGT_MASTER_DATA, please see attached
note.
Other Terms
Segmentation, Fashion, Retail.
59.42S4TWL - Allocation Run Master Data
Application Components:LO-RFM-MD-ART, LO-RFM-MD, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2465556
S4TWL - Master Data for Order
Allocation Run (ARun) in Fashion
Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1400
Symptom
You are doing a system conversion from SAP Fashion Management to SAP S/4HANA,
and you are using Order Allocation Run functionality. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
There are some differences in master data for Order Allocation Run in SAP
S/4HANA fashion for vertical business compared to SAP Fashion Management.
Business Process related information
In SAP Fashion Management it was possible to maitain both the distribution profile and
the Allocation Run relevance via integrated article maintenance (transaction MM41,
MM42).
In SAP S/4HANA either the distribution profile, or Allocation Run/Supply Assignment
relevancy can be mainatiend, as both functionality exclude each other.
Required and Recommended Action(s)
During the conversion, the adjustments are executed automatically. The relevant XCLA
class is CL_XCLA_MARC.
The class clears the MARC-FPRFM entries, for those MARC entries where there is a
non-initial MARC-FSH_MG_ARUN_REQ.
How to Determine Relevancy
This Simplification Item is relevant if Order Allocation Run functionality is used.
This can be checked via transaction SE16N. Enter table MARC and check whether there
are entries where MARC-FPRFM and MARC-FSH_MG_ARUN_REQ both are not
initial.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1401
59.43S4TWL - Fashion Contract Disablement
Application Components:LO-RFM, LO-RFM-SD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2468952
S4TWL - Fashion Contract
(Requirement Relevant Contracts) in
SAP Fashion Management
Symptom
You are doing a system conversion to an SAP S/4HANA release prior to 1709 FPS02,
and you are using Fashion Contracts (requirement relevant contracts) in SAP Fashion
Management. The following SAP S/4HANA Transition Worklist item is applicable in
this case.
Solution
Description
Fashion contracts are not available prior to SAP S/4HANA 1709 FPS02.
Business Process related information
In SAP Fashion Management it is possible to characterise contracts as fashion contracts.
In the processes of requirements planning (MRP), ATP, and Order Allocation Run those
fashion contracts are treated accordingly. In SAP S/4HANA fashion contracts are
available only starting with release S/4HANA 1709 FPS02.
Required and Recommended Action(s)
If you are using contracts and contract release orders in SAP Fashion Management
solution, and wamt to convert to S/4HANA to a release befor 1709 FPS02 you need to
perform the below mentioned actions:
You must close the existing open contract release orders referencing fashion contracts
(e.g. transaction VA02).
You must close the existing open fashion contract documents (e.g. transaction VA42)
so that additional requirements existing for these documents would not
be considered in SAP S/4HANA system.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1402
In SAP S/4HANA prior to 1709 FPS02 you need to use standard sales orders only to
realize order to cash (O2C) lifecycle.
How to Determine Relevancy
This Simplification Item is relevant if Fashion Contract functionality is used.
This can be checked via transaction SE16N. Enter table VBAK and check whether there
are entries where VBTYP = 'G' and FSH_CQ_CHECK = 'X'.
Other Terms
SAP Fashion Management, Fashion Contract, Requirement Relevant Contract
59.44S4TWL - Allocation Run
Application Components:LO-RFM-ARN, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2467506
S4TWL - Order Allocation Run (ARun)
in Fashion Management
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using Order
Allocation Run (ARun) in SAP Fashion Management. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
There are differences between Order Allocation Run in SAP Fashion Management and
Order Allocation Run in SAP S/4HANA (which is now part of Supply Assignment).
Business Process related information
Salient features of Supply Assignment (ARun) in SAP S/4HANA are as follows:
Supply Assignment is now an SAP S/4HANA core solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1403
Supply Assignment and Back Order Processing (BOP) are merged into one common
solution based on Advanced ATP
FIORI based executions of actual and simulated assignments
FIORI based result monitor and explanation tool for the assignments
Supply Assignments of requirements for sales orders and stock transport orders
Supply Assignment is not mandatory and can be switched on/off at article/site level
Assignment of batches is optional and can be decided on article/site level
Release procedure is decoupled from Supply Assignment execution run and can run
independent
Simplified Release Rule Determination procedure
Insight to action – Supply Assignment workbench to check exceptions and acting on
them
Order Allocation Run features not available in SAP S/4HANA (that were available in
SAP Fashion Management):
Order Allocation Run customizing settings
Contract call off assignments and reference handling
Customer BADIs throughout Order Allocation Run process
Order Allocation Run workbench / Order Allocation Run workbench batch report
Release and grouping strategy and determination table generation
Assignment and reference handling between Multiple-Ship-to-Order (MSO) main
orders and exploded orders
Consistency check report for Order Allocation Run results (because of simplified data
model)
Assignments of Order Allocation Run to Make-to-Order, Purchase-to-Order, and
subcontracting components
Order Allocation Run related transactions are not available in SAP S/4HANA
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1404
Data model simplification:
The design of Order Allocation Run in SAP S/4HANA is different compared to SAP
Fashion Management. In SAP S/4HANA the Order Allocation Run does not store
allocations in the tables FSH_BDBS and FSH_PREVIEW anymore, and those
tables are not refered to by the Order Allocation Run.
The allocations in FSH_BDBS and FSH_PREVIEW in SAP Fashion Management
will not be migrated to the new table in SAP S/4HANA.
As a consequence, the Order Allocation Run has to be set up and executed again after
system conversion.
Due to changed design in SAP S/4 HANA, the fields FSH_RALLOC_QTY and
FSH_SALLOC_QTY in standard tables would not be updated anymore by Supply
Assignment.
In SAP S/4HANA, the following transactions are not available:
ARUN
ARUNNO
ARUNP
ARUNWB
ARUNWB_BATCH
ARUN_BATCH
ARUN_CUST_TEMP_GRP
ARUN_PROI
ARUN_VARIANT
Note - In order to use the Supply Assignment in SAP S/4HANA, the business functions
SUPPLY_ASSIGNMENT_01 has to be activated. For retail fashion management specific
functionalities of Supply Assignment, business function
SUPPLY_ASSIGNMENT_RETAIL_01 has to be activated.
Required and Recommended Action(s)
Adjust the respective business processes accordingly.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1405
How to Determine Relevancy
This Simplification Item is relevant if Order Allocation Run functionality is used.
This can be checked via transaction SE16N. Enter table FSH_BDBS and check whether
there are entries, or whether there are entries in table FSH_PREVIEW.
Other Terms
Order Allocation Run, ARun, Fashion Management, Retail, Supply Assignment
59.45S4TWL - Segment Field Length Extension
Application Components:LO-RFM, LO-RFM-CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2522971
S4TWL - Segment Field Length
Extension
Symptom
You are doing a sytem conversion from SAP ERP 6.0 EHP7/EHP8 to SAP S/4HANA
1709 and you are using segmentation functionality. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The data model of segments has changed in SAP S/4HANA 1709. The field length has
been increased from 16 to 40 characters.
Business Process related information
This data model change does not have any business impact.
Required and Recommended Action(s)
During the conversion, adjustments are made automatically.
How to Determine Relevancy
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1406
This Simplification Item is relevant if segmentation functionality is used.
This can be checked via transaction SE16N. Enter table MARA and check whether there
are entries with MARA-SGT_REL non initial.
59.46S4TWL - Fashion Functionality
Application Components:LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2516743
S4TWL - Fashion Functionality
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using fashion related
busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case
Solution
Description
Certain fashion functionalities have changed or are not available anymore in SAP
S/4HANA for fashion for vertical business, when compared to SAP Fashion
Management.
Business Process related information
For changed functionlity, please see referenced notes for:
Segmentation
Segment Field Length Extension
Fashion Season Conversion
Allocation Run Master Data
Allocation Run
Season in Inventory Management
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1407
The following functionality has changed:
Display Stock/Requirements Situation: Transaction FSH_MD04 is not available in
SAP S/4HANA anymore. There is a new transaction MD04P providing relevant
functionality.
Mass Data Change for Sales Documents and Stock Transport Orders: Transactions
FSH_MASS_SD/FSH_MASS_SDN are not available anymore. Functionality is
provided via repricing functionality in SD and MM (e.g. VA05, MEI1), and
Advanced ATP transactions.
Split and Change Purchase Orders: Transaction FSH_SPLITPO is not available
anymore. Functionality is provided via transaction FSH_PWB (Purchase Order
Mass Maintenance Workbench).
Process for Subcontracting will not be supported by Supply Assignment (Allocation
Run, ARun).
Stock Protection is not considered in ATP overview display in sales order processing
(it is considered in calculation and thus correct).
Multi Ship-to Order (MSO)
Fiori apps for Buy Planner
Plan Procurement for Buy-Planner (PLAN_PROCURE),
Purchase Requisition Processing for Buy-Planner (PR_PROCESS)
are not available anymore.
Purchase Order generation rules.
Snapshot functionality in procurement and sales is not available anymore.
The following transactions are obsolete:
FSH_ARUNITA Insight to Action
FSH_CFMH Hierarchy Transfer for a Gen. Art.
FSH_CIF_BATCH_CL Default Class for Batches at Plant
FSH_CIF_BTCHCHR Batch Characteristics
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1408
FSH_COD Fashion Cut Off Date
FSH_COD_GR_UPD Update Del. Date for Cut Off dates
FSH_DROP_REQ Drop Open Requirements
FSH_ITAE Insight to Action -Config exceptions
FSH_ITAH Insight to action - drilldown configuration
FSH_MASS_SD Mass change transaction
FSH_MD04 Generic Materials Stock/Requirements List
FSH_PROD Create product number for GTS transfer
FSH_SPLITPO Split Purchase Order
FSH_CO09 Generic Article CO09
The following transactions are obsolete prior to SAP S/4HANA 1709 FPS02, and are
available starting w/ SAP S/4HANA 1709 FPS02 (see also note 2627238):
FSH_QDP Quantity Distribution Profile
FSH_PCW Production Control Workbench
In addition, the number range of object FSH_MPLND (was in SAP Fashion
Management) has been substituted by number range object FSH_MPLO. The
number range intervals of object FSH_MPLO need to be maintained accordingly
(transaction SPRO -> Logistics - General -> Fashion Management -> Production
Planning and Control -> Define Number Range for Master Planned Order; or
directly via transaction SNRO, enter FSH_MPLO for the object name).
The following transactions are obsolete prior to SAP S/4HANA 1809, and are available
starting w/ SAP S/4HANA 1809:
FSH_PFM Maintain PFM Rules
FSH_PSM Maintain PSM Rules
Integraion scenarios with SAP Customer Activity Repository 3.0
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1409
Please note, that currently integration scenarios with SAP Customer Activity
Repository 3.0 (CARAB 2.0) and consuming applications are not supported. SAP
plans to provide a note to enbale such an integration scenario.
Required and Recommended Action
Implemented business processes need to be adjusted according to the changes listed
above.
Please see also referenced Release Information Note.
How to Determine Relevancy
This Simplification Item is relevant if fashion processes are used. This is the case if at
least one of the following transaction is used: FSH_ARUNITA, FSH_CFMH,
FSH_CIF_BATCH_CL, FSH_CIF_BTCHCHR, FSH_CO09, FSH_COD,
FSH_COD_GR_UPD, FSH_DROP_REQ, FSH_ITAE, FSH_ITAH, FSH_MASS_SD,
FSH_MD04, FSH_PCW, FSH_PFM, FSH_PROD, FSH_PSM, FSH_QDP,
FSH_SPLITPO.
Other Terms
Fashion, Retail.
59.47S4TWL - Season Active in Inventory Management
Application Components:LO-RFM, LO-RFM-MD, LO-RFM-MD-ART
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2535093
S4TWL - Season Active in Inventory
Management
Symptom
You are doing a system conversion from SAP ERP (SAP Fashion Management or SAP
Merchandising) to SAP S/4HANA, and you are using season based inventory
management. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1410
Description
In SAP S/4HANA functionality to assign a season to inventory stock is not available
anymore.
Business Process related information
Visibility to which season a specific stock is assigned to is not available anymore.
Required and Recommended Action(s)
During conversion from SAP Fashion Management to SAP S/4HANA the respective flag
in the article master (level article-site) is cleared. Stock information as such is unchanged,
just the assignment to a season is cleared.
You need to adjust your business processes accordingly.
How to Determine Relevancy
This Simplification Item is relevant if season functionality is used in inventory
management.
SAP Fashion Management: This can be checked via transaction SE16N. Enter
table MARC and check whether there are entries with FSH_SEAIM set to ‘X’
59.48S4TWL - Segmentation (Upgrade SAP S/4HANA 1709 to 1809)
Application Components:LO-RFM-SGT, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2629241
S4TWL - Segmentation (Upgrade SAP
S/4HANA 1709 to 1809)
Symptom
You are doing a system upgrade from SAP S/4HANA 1709 to SAP S/4HANA 1809, and
you are using segmentation related busines functionality. The following SAP S/4HANA
Transition Worklist item is applicable in this case
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1411
The data model of segmentation has changed from SAP S/4HANA 1709 to SAP
S/4HANA 1809.
Business Process related information
This data model change does not have any business impact.
Required and Recommended Action(s)
In SAP S/4HANA 1809, ATP pool segment is enabled which is stored in table
SGT_CATP.
During the upgrade from 1709 to 1809 a migration report needs to be executed, which
looks at 'ARUN/MRP/ATP: Requirement/Stock Allocation' node and populates the pool
segment in table SGT_CATP. This is achieved via execution of XPRA
report R_SGT_ATP_MIGRATION_XPRA.
In case the installation was originally converted from a SAP Fashion Management (SAP
ERP 6.0 EHP7/EHP8) to SAP S/4HANA 1709 data contained in table SGT_CATP needs
to be deleted via a pre-migration report R_SGT_POOL_SEGMENT_DELETE as ATP
pool segment is not available in S/4HANA 1709.
How to Determine Relevancy
This Simplification Item is relevant if segmentation is used.
This can be checked via transaction SFW2 to check whether Business
Function LOG_SEGMENTATION is activated.
Other Terms
Segmentation, ATP pool segment , Fashion, Retail, SGT_CATP
59.49S4TWL - Conversion of Season Master Data to SAP S/4HANA 1809
Application Components:LO-RFM-CA, LO-RFM-CA-SE, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2640859
S4TWL - Conversion of Season Master
Data to S/4HANA 1809
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1412
You are using season master data and you are doing
- a system conversion from SAP ERP (SAP Fashion Management, or SAP
Merchandising) to SAP S/4HANA 1809 (S4CORE 103)
- or an upgrade from S/4HANA 1610 (S4CORE 101), or S/4HANA 1709 (S4CORE 102)
to SAP S/4HANA 1809 (S4CORE 103)
In this case, the following SAP S/4HANA Transition Worklist item is applicable in this
case.
Reason and Prerequisites
The season master data model is simplified in the SAP S/4HANA 1809 which requires
the existing season master data in respective tables to be converted accordingly.
Solution
Description
In SAP Fashion Management or S/4HANA 1610 or S/4HANA 1709,
seasons/collections/themes are stored in multiple tables such as
FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES, FSH_SEASONS_T,
FSH_COLLECTIONS_T, FSH_THEMES_T.
In SAP ERP (Retail), the seasons were defined as customizing entries.
These tables are not used anymore. Simplified season master data tables
RFM_SEASONS, RFM_SEASONS_T will replace them in SAP S/4HANA 1809
(S4CORE 103) onwards.
Business process related information
As part of conversion/upgrade of the system to SAP S/4HANA 1809 (S4CORE 103), the
following tables are filled automatically:
SAP Fashion Management, S/4HANA 1610 (S4CORE 101), or S/4HANA 1709
(S4CORE 102)
FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES ->
RFM_SEASONS
FSH_SEASONS_T, FSH_COLLECTIONS_T, FSH_THEMES_T ->
RFM_SEASONS_T
SAP ERP (Retail)
First Step
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1413
TWSAI -> FSH_SEASONS
T6WST -> FSH_SEASONS_T
TWSAI -> FSH_COLLECTIONS
T6WSAT -> FSH_COLLECTIONS_T
Second Step
FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES ->
RFM_SEASONS
FSH_SEASONS_T, FSH_COLLECTIONS_T, FSH_THEMES_T ->
RFM_SEASONS_T
Required and Recommended Action(s)
During the conversion/upgrade, the following reports are executed automatically:
SAP Fashion Management, S/4HANA 1610 (S4CORE 101), or S/4HANA 1709
(S4CORE 102)
R_FSH_TO_RFM_SEASONS_MD_XPRA
SAP ERP (Retail)
First Step
R_FSH_S4_SEASONS_MD_MIG
Second Step
R_FSH_TO_RFM_SEASONS_MD_XPRA
How to Determine Relevancy
This Simplification Item is relevant if retail/fashion season is used.
SAP ERP Merchandising (SAP ERP Retail): This can be checked via transaction SE16N.
Enter table MARA and check whether there are entries with field MARA-SAISO
(Season) not initial.
SAP Fashion Management (SAP ERP Fashion): This can be checked via transaction
SE16N. Enter table FSH_SEASONS_MAT and check whether there are entries.
SAP S/4HANA 1610 and 1709: This can be checked via transaction SE16N. Enter
table FSH_SEASONS_MAT and check whether there are entries.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1414
Other Terms
SAP ERP (Retail), SAP Fashion Management, S/4HANA 1610, S4CORE 101,
S/4HANA 1709, S4CORE 102, Seasons, R_FSH_TO_RFM_SEASONS_MD_XPRA,
FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES, FSH_SEASONS_T,
FSH_COLLECTIONS_T, FSH_THEMES_T, RFM_SEASONS, RFM_SEASONS_T
59.50S4TWL - Supply Assignment Preview (upgrade to SAP S/4HANA 1809)
Application Components:LO-RFM-ARN, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2637163
S4TWL - Supply Assignment Preview
(upgrade from S/4HANA 1709 to
S/4HANA 1809)
Symptom
You are doing a system upgrade from SAP S/4HANA 1709 to SAP S/4HANA 1809, and
you are using Supply Assignment Preview functionality. The following SAP S/4HANA
Transition Worklist item is applicable in this case
Solution
Description
The data model of Supply Assignment Preview has changed from SAP S/4HANA 1709
to SAP S/4HANA 1809.
Business Process related information
This data model change does not have any business impact.
In S/4HANA 1709 the preview mode could be executed in back order processing, the
variant having checking rule as $PRE.
In S/4HANA 1809 the preview mode can be executed in back order processing, when in
the variant the new parameter "Assignment Preview" is set to active.
Required and Recommended Action(s)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1415
There is no migration report for Supply Assignment Preview. Before the upgrade the old
preview entries can be deleted (via transaction ARUNITA "Insight to Action", Execution
Mode: Background, Selection Mode: Preview, Action: Unassign). After upgrade the back
order processing needs to be executed again.
How to Determine Relevancy
This Simplification Item is relevant if Supply Assignment Preview functionality is used.
This can be checked via transaction SE16N. This simplification item is relevant if there
are entries
- in table ARUN_BDBS and with ARUN_MODE = 2
or
- in table ATP_BOP_VARIANT with ABOPCHECKINGRULE='$PRE' AND (
ABOPEXECUTIONMETHOD = "FULL" OR ABOPEXECUTIONMETHOD =
"ARUN" )
59.51S4TWL - Vendor Characteristic Values
Application Components:LO-MD-BP-VM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2885547
S4TWL - Vendor Characteristic Values
Symptom
You are doing a system conversion to SAP S/4HANA Retail for merchandise
management or SAP S/4HANA for fashion and vertical business. The following SAP
S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Via classification system it is possible to assigen characteristic values to articles.
Vendor Characteristic Values are used to maintain the descriptions of a characteristic
value a supplier uses, in case this description deviates from the description you are using.
E.g. you use "red" for a characteristic value whereas the supplier uses "fire engine red".
In ECC it was possible to maintain the vendor characteristic values either in vendor
maintenance (transactions MK0x, XK0x) or in purchasing view of the article
maintenance (tramsacations MM4x). Because of the Business Partner harmonization in
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1416
S/4HANA, it is not possible anymore to maintain the values via supplier maintenance. It
is still possible to maitain the values via article maintenance.
In addition it is possible to achieve a simliar via Characteristic Value Conversion.
Business Process related information
Business processes are not affected besides the maintenance as such.
Required and Recommended Action(s)
Use maintenance capabilities of article maintenance or switch to
Characteristic Value Conversion.
This does not affect your custom code.
How to Determine Relevancy
This Simplification Item is potentially relevant if Vendor Characteristic Values are used.
This can be checked via transaction SE16N. Enter table WYT2 and check whether there
are any entries.
59.52S4TWL - Lean SAF Interface
Application Components:IS-R-PUR-FC, IS-R-PUR, IS-R, MM-CBP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3035561
S4TWL - Lean SAF Interface
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using some Retail
related busines applications. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
Description
This interface covers the integration between ECC and a stand alone SAF forecasting
solution (from former company Simulation, Analysis and Forecasting AG).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1417
Business Process related information
In SAP S/4HANA this integration scenario is not available anymore.
This should not be confused with the integration with SAP Forecasting and
Replenishment, which of course is still available and supported.
Software package: WSAFS.
Transactions: WSAF001, WSAF002, WSAF003, WSAF004, WSAFR01, WSAFR02.
Required and Recommended Action(s)
In case you used integration with in the past available stand alone SAF forecastiong
solution, you can switch to SAP Forecasting and Replenishment or SAP UDF (Unified
Demand Forecasting).
In case you reuse ABAP objects of packet WSAFS in your custom code, please see
attached note.
How to Determine Relevancy
This Simplification Item is relevant if the lean SAF interface is used.
This is the case if any of the following transactions is
WSAF001, WSAF002, WSAF003, WSAF004, WSAFR01, WSAFR02.
59.53S4TWL - BAdI for Article Reference Handling
Application Components:LO-RFM-MD, LO-RFM-MD-ART, LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3043856
S4TWL - BAdI for Article Reference
Handling
Symptom
You are doing a system conversion or an upgrade to SAP S/4HANA 2021, and you are
using some Retail related busines applications. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
Solution
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1418
Description
With release SAP S/4HANA 2021 the technical type of BADI_ARTICLE_REF_RT has
changed from a "classic BAdI" to kernel BAdI.
Business Process related information
This change of the BAdI type does not have any business impact.
Required and Recommended Action(s)
Which steps need to be described here.
In case this link does not work, go to the home page http://help.sap.com and enter search
term "Migrating BAdIs".
How to Determine Relevancy
This Simplification Item is relevant if BADI_ARTICLE_REF_RT is used.
This is the case if there is a relevant entry in view V_EXT_ACT. You can test this via
transaction SE16 for
EXIT_NAME = BADI_ARTICLE_REF_RT AND IMP_NAME starts with Z*
or
EXIT_NAME = BADI_ARTICLE_REF_RT and IMP_NAME starts with Y*.
Other Terms
BADI_ARTICLE_REF_RT
59.54S4TWL - Retail Store Fiori App
Application Components:LO-SRS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2342914
S4TWL - Retail Store Fiori App
Symptom
You are doing a system conversion to SAP S/4HANA, and you are using the Fiori app
for transfer stock. The following SAP S/4HANA Transition Worklist item is applicable
in this case.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1419
Solution
Description
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.
59.55S4TWL - SAP AFS Integration
Application Components:CA-DMS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371161
S4TWL - SAP AFS Integration
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1420
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 , refer to ID 104 in the xls
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.
59.56S4TWL - POS Outbound via Idoc WP_PLU
Application Components:SD-POS-OUT, SD-POS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371149
S4TWL - POS Outbound via IDoc
WP_PLU
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
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).
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1421
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, on-premise edition , refer to ID 104 in the xls
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.
59.57S4TWL - Valuation in Retail
Application Components:MM-IM-GF, MM-IM, MM-IM-GF-SAV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2365503
S4TWL - Retail Revaluation
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Reason and Prerequisites
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.
Solution
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,
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1422
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 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.
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.
59.58S4TWL - Retail Demand Management Integration
Application Components:LO-MD-RDM, LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371157
S4TWL - Retail Demand Management
Integration
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1423
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 , refer to ID 104 in the xls.
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1424
60.Industry Telecommunications
60.1 S4TWL - Lock and unlock services using IST_TDATA
Application Components:IS-T-CA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270468
S4TWL - Lock and unlock services
using IST_TDATA
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In the table IST-TDATA telecommunication services data is stored that is used by
Receivables Management - Contract (RM-CA) to create requests for locking or unlocking
services. In case the provider order in Accounting Receivables Management – (RM-CA)
is used, this table is not needed any more. All necessary data can be retrieved from the
provider contract.
Business Process related information
If you are already using database table IST_TDATA for managing telecommunication
services and the provider contract as well, you can continue storing telecommunication
service data in database table IST_TDATA. In case you decide to stop using table
IST_TDATA RM-CA, items that are already posted (still overdue and reason for locking
the telecommunication service) are still processed based on the functionality that is 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 new entries in the database table IST_TDATA.
To discontinue using the 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1425
Required and Recommended Action(s)
No changes in business processes, it might (if you decided for) only have an influence on
the technical level in the sense of "how necessary information are being retrieved from
the system".
To check if table IST_TDATA is used, call the transaction SE16 to check for entries in
the table IST_TDATA.
60.2 S4TWL - PORTAL ROLES FOR NETWORK LIFECYCLE
MANAGEMENT (NLM)
Application Components:IS-T-NM-PCT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273101
S4TWL - Portal Roles for Network
Lifecycle Management (NLM)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
(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)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1426
Business Process related information
No influence on business processes as the functionality itself is still available. This
note is only related to the possibility of implementing the portal roles.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1427
61.Industry Utilities
61.1 S4TWL - CVI Integration for SAP ISU
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2344100
S4TWL - CVI Integration for SAP ISU
Symptom
You are doing a system conversion from SAP ERP to SAP S/4HANA. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
In SAP S/4HANA, on-premise edition, the central business partner approach(CVI) 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).
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.
Please note that CVI functionality described in this note is released for SAP S/4HANA
only and SAP does not plan to make it available on SAP IS-U(ECC).
Business Process related information
No influence on business processes expected.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1428
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 which are provided by the SAP Note 2354282 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 Notes 2202282 and 2456502 are 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 two
reports mentioned above are not run, the system master check S4TC will fail.
Please run the two reports listed above in SAP ERP. Please note that CVI (direction
‘Business Partner-to-Customer/Vendor’) must not be activated in the source ECC system
prior to the S/4HANA conversion. It must be activated in the target SAP S/4HANA
system only after the successful conversion.
The early activation of the CVI(Direction ‘Customer/Vendor-to-Business Partner’) in the
source ECC system before the S/4HANA conversion, is not recommended. If customers
still want to do the early activation for the CVI(Direction ‘Customer/Vendor-to-Business
Partner’) in the source ECC for synchronizing the customers, they might need to
implement the BADI CVI_CUSTOM_MAPPER to avoid merge of first name and last
name. Please see the SAP Note 1830886 for the details.
For more information about CVI-related authorization objects, please check SAP security
guide for SAP S/4HANA release of interest.
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 (attachedwith this note)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1429
Other Terms
CVI, ISU
61.2 S4TWL - Multichannel Foundation for Utilities
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2329190
S4TWL - SAP Multichannel Foundation
for Utilities
Symptom
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.
Solution
Description
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 delivered 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
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1430
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 also apply if you use the mobile apps SAP Self-Service for Utilities for
Android or SAP Self-Service for Utilities for iOS. The code of the mobile apps 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.
Other Terms
SAP MCF, Multichannel for Utilities, SSU, SAP Self-Service for Utilities
61.3 S4TWL - SAP Waste and Recycling: Activation
Application Components:IS-U-WA, SV-SMG-ICO-IWR, CRM-WA, XX-PART-PLG-WAS, XX-
EOD-IS-U-WA, BW-BCT-WA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2437332
SAP S/4HANA, SAP Waste and
Recycling: Activation SAP Note
Symptom
You want to use SAP S/4HANA, on-premise Edition 1610 FPS02 or higher. This SAP
Note provides information about the restrictions of this release with regard to the SAP
Waste and Recycling functions.
Reason and Prerequisites
SAP Waste and Recycling and all enhancements (for example, BW including all
dataSources) are released as of SAP S/4HANA, on-premise 1610 FPS02 or higher. To be
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1431
able to use SAP Waste and Recycling, the business functions ISU_WASTE_1,
ISU_WASTE_RCI_2, ISU_WASTE_C&I_2, ISU_WASTE_2, ISU_WASTE_3,
ISU_WASTE_4 must be activated. All code branches that would pass through the "Off"
switch settings, are no longer available. In this context, also refer to the additional
documentation for the relevant business functions.
If you want to switch from an earlier release to SAP S/4HANA and have not yet activated
all of the aforementioned business functions, a possible conversion strategy could be to
perform the technical upgrade to SAP S/4HANA on-premise first, then to activate the
aforementioned business functions, and then to carry out the functional test.
Please note for the conversion to S/4HANA on-premise that the integration in EH&S:
Waste Management is no longer supported.
The existing integration of SAP CRM for SAP Waste and Recycling and its
corresponding UIs are delivered neither in SAP S/4HANA, on-premise edition nor in
SAP S/4HANA for Customer Management. A comparable integration between SAP
S/4HANA for Customer Management and SAP S/4HANA (SAP Waste and Recycling) is
provided and licensed via the solution extension SAP S/4HANA for Waste and Recycling
by PROLOGA.
Solution
SAP Waste and Recycling is released for SAP S/4HANA, On-Premise-Edition 1610
FPS02 and higher.
The following transactions are no longer supported for SAP S/4HANA On-Premise-
Edition 1610 FPS02 and are on the black list:
EWAEL01
Delivery Locks
EWAEL02
Visual Control
EWAEL03
Reserve Sample
EWAGG
Guarantor Contract
EWAGGABR
Allocate Bill.Data to Guarantor Cat.
EWAORDALL
Create Waste Disposal Order
EWASPGCONF
Configuration: Service Product Generator
EWAWA02
Weighing Transaction
EWAWA04
Offline Weighing
See the corresponding simplification element and the list of simplifications in SAP
S/4HANA.
Other Terms
SAP Waste and Recycling, waste management, IS-U-WA, CRM-WA, BW-BCT-WA,
W&R, IS-WASTE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1432
61.4 S4TWL - IDE Outgoing Payment Processing
Application Components:IS-U-IDE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2574483
S4TWL - IDE outgoing payment
processing
Symptom
You are performing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
You as a utilities company in a deregulated market are using functionality of SAP
Intercompany Data Exchange (IDE).
Solution
Description
Reports RETHP01 and RECTHP02 (program for generating the FI vendor posting) used
in deregulated business scenarios in the Utilities industry are not supported in SAP
S/4HANA Utilities. Instead please use transaction ETHPM (Aggregated Posting of
outgoing payments).
Usage of these reports is indicated by entries in table EPAYTHP (checked via transaction
SE16).
Business Process related information
Transaction ETHPM requires activation of Service Provider Agreements. Change your
configuration and implementation of SAP IDE to the usage of service provider
agreements.
Other Terms
RECTHP02, EPAYTHP, RECTHP01
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1433
61.5 S4TWL - SAP Waste and Recycling: Service orders in EWACONTS
Application Components:IS-U-WA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3245321
S4TWL - SAP Waste and Recycling:
Service orders in EWACONTS
Symptom
You want to use SAP S/4HANA 2021 FPS02 or higher. This SAP Note provides
information about the restrictions of this release with regard to the SAP Waste and
Recycling functions.
Reason and Prerequisites
Update to SAP S/4HANA, 2021 FPS02 or higher
Solution
Description
As of SAP S/4HANA, 2021 FPS02, it is no longer possible to create an additional service
order in EWACONTS when creating a waste disposal order.
Business process information
There is currently no alternative way to create service orders in the SAP Waste and
Recycling core.
In the future, the partner enhancement "Industry Solutions by PROLOGA: Planning and
Dispatching" will provide the creation of service orders as a central component. For more
information, see the SAP Road Map Explorer.
Required and recommended actions
Knowledge transfer to key users and end users
Relevancy
This change is relevant for you if you use the table EWADEVSERV in the SAP Waste
and Recycling environment.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1434
See the corresponding simplification element and the list of simplifications in SAP
S/4HANA.
Other Terms
SAP Waste and Recycling, waste disposal industry, IS-U-WA, W&R
61.6 S4TWL - Late Payment Change
Application Components:IS-U-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2681020
S4TWL - IS-U Late Payment Charge
Symptom
You are using SAP for Utilities (IS-U).
(1) If you are currently using SAP ERP 6.0 and planning a conversion to SAP S/4HANA,
(2) or if you are currently using SAP S/4HANA 1511, 1610, 1709, 1809 FPS0 and
planning an upgrade to a higher release,
the following SAP S/4HANA Transition Worklist item is applicable if you are using the
functionality of Late Payment Charge, and there are data records stored in database table
EKLPCI.
Reason and Prerequisites
You as a utilities company are using the functionality of Late Payment Charge as part of
IS-U Invoicing on SAP S/4HANA.
Solution
Description
SAP plans to deprecate and delete database table EKLPCI. From SAP S/4HANA 1809
FPS1 on, the database table EKLPCI and function module ISU_DB_EKLPCI_CHCRD
are not available anymore. Information related to Late Payment Charge is stored in
database table EKLPCINV. IF table EKLPCI does not contain any data records, this note
is not relevant for you.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1435
Required and recommended actions
You should check content in table EKLPCI. It is expected that EKLPCI is either empty or
contains very old, outdated data records that are not needed anymore. Therefore, SAP
does not provide a migration tool for these data.
You should check your custom code. All accesses to database table EKLPCI have to be
removed or substituted accordingly.
Business Process related information
Database table EKLPCINV has substituted EKLPCI. The standard SAP coding does not
write to table EKLPCI.
Other Terms
EKLPCI, EKLPCINV
61.7 S4TWL - IS-Utilities Settlement Control
Application Components:IS-U-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2694441
S4TWL - IS-U - Utilities clearing control
Symptom
You execute a system conversion for SAP S/4HANA, On-Premise Edition. The
following SAP-S/4HANA conversion work list entry applies in this case.
Solution
Description
The IS-U clearing control was used to clear open items. The FI-CA clearing control
replaced it with the R/3 Release 4.61 (conversion using XPRA:
ISU_XPRA_SETTLEMENT_CONTROL).
Business-process-specific information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1436
No effects on business processes expected. You only have to expect effects on customer
source code, for example, by using one of the data elements affected by this note.
Example 1: You use the data element E_FWERT: Use the data element FWERT_KK
instead.
Example 2: You use the data element E_VERART: Use the data element VERART_KK
instead.
Required and recommended action (s)
To check whether you are still using the IS-U clearing control, call transaction SE16 and
check whether the table°TE515 contains entries.
61.8 S4TWL - Maintenance of non-billable Point of Delivery services
Application Components:IS-U-IDE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2843756
S4TWL - Maintenance of non-billable
Point of Delivery services
Symptom
You are doing a system conversion or an upgrade to SAP S/4HANA 1909 or higher. You
are using functionality of SAP IDE (Intercompany Data Exchange) for deregulated
utilities markets. The following SAP S/4HANA Transition Worklist item is applicable in
this case.
Solution
Description
The concept of non-billable services on level of points of delivery (PoD) is
comprehensively
described: https://help.sap.com/viewer/905da66b76d1449fbe6ac26484842994/1909.000/
en-US/8b5fce53118d4308e10000000a174cb4.html
The maintenaince (creation and change) of non-billable services is supported via the
supply scenario and supply scenario
generator: https://help.sap.com/viewer/905da66b76d1449fbe6ac26484842994/1909.000/e
n-US/ff60ce53118d4308e10000000a174cb4.html
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1437
Non-billable services on PoD level are maintained automatically in the background in the
context of start and end of supply and change of supplier processes. Display is available
on PoD level (transaction EEDM11 "Display point of delivery",
Following these concepts of SAP IDE, transactions for maintaining individual non-
billable services are not required. Following transactions are therefore deprecated in SAP
S/4HANA:
Transaction EPODSRVC1 ("Create PoD service")
Transaction EPODSRVC2 ("Change PoD service")
Transaction EPODSRVC3 ("Display PoD service")
These transactions have been delivered before the concept of the supply scenario has
been provided. Successor of these transactions is the functionality of supply scenario
generator.
This note is only relevant for you if you are using non-billable services in your actual
system, i.e. there are entries in table ESERVICE.
Business Process related information
Use the functionality of supply scenario should be applied.
Transactions not available in SAP
S/4HANA 1909 and higher
EPODSRVC1, EPODSRVC2, EPODSRVC3
61.9 S4TWL - Deprecation of transaction EA22_TOOL
Application Components:IS-U-BI, IS-U-DM-MR, IS-U-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3014556
S4TWL - Deprecation of transaction
EA22_TOOL
Symptom
You are doing a system conversion or an upgrade to SAP S/4HANA 2020 or higher. You
are using functionality of Utilities Meter Reading, Utilities Billing and Utilities
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1438
Invoicing. The following SAP S/4HANA Transition Worklist item is applicable in this
case.
Solution
Description
SAP S/4HANA Utilities provides a rich set of transactions and processes for Utilities
Meter Reading, Utilities Billing and Utilities Invoicing exposed in the SAP Menu for the
Utilities industry.
Beside this functionality, earlier releases of SAP Business suite and SAP S/4HANA
provide the transaction EA22_TOOL ("Billingtool") that exposes a set of functionality in
the functional utilities areas mentioned above. Due to these overlapping functionalities,
transaction EA22_TOOL is not needed and therefore deprecated in SAP S/4HANA.
Business Process related information
For the overview of all meter reading / billing / print documents and orders, you can use
the screen "Billing periods" in transaction ES32 "Display Installation".
61.10S4TWL - Refund Claim for Germany
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3326146
S4TWL - IS-U refund claim (energy
price caps in Germany)
Symptom
This note is relevant for you under folowing conditions:
(1) You are using SAP for Utilities (IS-U).
(2) As a German Utility in the market role supplier, you are using the SAP standard
solution for the German laws for energy price caps according to note 3279875.
Reason and Prerequisites
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1439
The solution for energy price caps in Germany according to the German laws EWPBG
and StromPBG is available for SAP S/4HANA 2022 and higher releases.
The length of the fields EPB_REFWERT and EPB_BETRGEW in the database table
EPB_REFUND_POS has been changed after the initial delivery. This modification has
been delivered with note 3322223. If this note has not been applied to your system, there
would be negative impacts during system upgrades that should be avoided.
Solution
Description
You should prepare your system for the planned upgrade as described below. After
upgrade, there are no more specific actions required in this context.
Required and recommended actions
If you want to upgrade your system (upgrade to higher support package or enhancement
package within SAP ERP 6.0 or upgrade to any SAP S/4HANA release greater or equal
2022), you should consider the following:
(1) Make sure that the solution for energy price caps is supported by the target release
you want to upgrade to. Information are provided in note 3279875.
(2) Make sure that note 3322223 is implemented or, precisely expressed, data
element EPB_REFWERT has a length of 12. If not, please implement note 3322223
before performing any upgrade.
Business Process related information
The increased length of data elements EPB_REFWERT and EPB_BETRGEW became
necessary to process values larger than initially considered.
Other Terms
EWPBG & StromPBG
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1440
61.11S4TWL - Monitoring Profile Value Import
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270502
S4TWL - Monitoring Profile Value Import
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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).
For using the new transaction EDM1N, activation of ISU_EDM_1 is required.
Business Process related information
No change in business process
Transaction not available in SAP
S/4HANA on-premise edition 1511
EDM1
61.12S4TWL - Prepayment solution for the utilities industry
Application Components:IS-U-BI
Related Notes:
Note Type
Note Number
Note Description
Business Impact
3375865
S4TWL - Prepayment solution for the
utilities industry
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1441
Symptom
You are doing a system conversion or an upgrade to SAP S/4HANA 2023 or higher. You
are using prepayment functionality within IS-U Billing. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
Prepayment and prepayment meters are applied in different countries and utilities
markets since a long time. SAP delivered a first solution based on SAP ERP and several
years later a second solution called SAP Prepayment for Utilities. The first prepayment
solution will be now deprecated, and IS-U customers are asked to implement and use
SAP Prepayment for Utilities instead of the old solution.
This deprecation is relevant for you if you have entries in database table EPPMHEADER.
Business Process related information
Following programs and transactions are not supported anymore:
EPREPAY (Amount Mgmt of Prepayment Meter)
EPREPAY_RELEASE (Release locked PPM entries)
EPREPAYFREE (Release locked PPM entries)
ISU_PPM_JOB_NR (Number Range Maintenance: PPM_JOB_NR)
EPPM (Number Range Maintenance: PPM_JOB_NR)
S_XB3_95000002 (IMG Activity: _ISUCSPPM_000002)
ESARA09 (IS-U Archiving: Prepayment Documents)
ESARJ09 (ArchInfStructure: Prepayment Active)
61.13S4TWL - Utilities Customer Electronic Services (UCES)
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270504
S4TWL - Successor for Utilities
Customer Electronic Services (UCES)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1442
Symptom
You are performing a system conversion to SAP S/4HANA, on-premise edition. The
following SAP S/4HANA Transition Worklist item is applicable in this case.
Reason and Prerequisites
This note is only relevant if you are using the SAP Netweaver JAVA component Utility
Customer E-Service (UCES).
Solution
Functionality Utilities Customer Electronic Services (UCES) is not available in SAP
S/4HANA 1511 and higher releases. Functional equivalent named SAP Multichannel
Foundation for Utilities and Public Sector (SAP MCF) is available with SAP S/4HAHA
1610 and higher releases.
Following UCES related transaction codes are not available anymore:
EWEBIAC_1_PAY
ISS Pay Bills
EWEBIAC_A_PAY
ISS Direct Debit Mandate
EWEBIAC_A_PAY_CIC
ISS Direct Debit Mandate as ESS
EWEBIAC_ACCT_INFO
ISS Accounts Information
EWEBIAC_CALLBACK
ISS Initiate Callback
EWEBIAC_CH_MD
ISS Change Bill Address
EWEBIAC_CH_MD_CIC
ISS Change Bill Address ESS
EWEBIAC_CONS_HIS_CIC
ISS Consumption Overview in CIC
EWEBIAC_CONSUMP_HIST
ISS Consumption Overview
EWEBIAC_CONTINUE
Dummy Entry for Service Usage
EWEBIAC_CPUSER
Customer Portal - User
EWEBIAC_ENROLL_CIC
ISS Initial Data Creation as ESS
EWEBIAC_ENROLLMEN
ISS Initial Data Creation
EWEBIAC_ENROLLMENT
ISS Initial Data Creation
EWEBIAC_HTMLBILL
ISS Bill
EWEBIAC_INFO
ISS Accounts Information
EWEBIAC_INFO_CIC
ISS Account Information ESS
EWEBIAC_LOGIN
ISS Internet Account
EWEBIAC_METER_CIC
ISS Meter Reading Entry from CIC
EWEBIAC_METER_READ
ISS Meter Reading Entry
EWEBIAC_MOVE_IN
ISS Move-In
EWEBIAC_MOVEOUT
ISS Move-Out
EWEBIAC_PASSWD
ISS Change Internet Password
EWEBIAC_PASSWD_NEW
ISS Password Forgotten
EWEBIAC_PREM_SEL_CIC
ISS Premise Selection
EWEBIAC_PREMISE_SEL
ISS Premise Selection
EWEBIAC_SHOW_PROFIL
ISS Display Profile Values
EWEBIAC_TEMPLATE
ISS Template
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1443
SAP Multichannel Foundation for Utilities and Public Sector 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. More information is avaliable
in the Innovation Discovery, innovation "SAP Multichannel Foundation for Utilities and
Public Sector software and SAP S/4HANA: self-services for end customers", link:
https://go.support.sap.com/innovationdiscovery/#/innovation/6CAE8B26E4CB1EE5BEC
CBB48AF5EF298
Other Terms
UCES, S/4HANA, MCF
61.14S4TWL - IS-U Stock, Transaction and Master Data Statistics (UIS, BW)
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270505
S4TWL - IS-U Stock, Transaction and
Master Data Statistics (UIS, BW)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
IS-U Stock and Transaction Statistics based on Logistics Information System (LIS) is not
available within SAP S/4HANA, on-premise edition 1511. Successor functionality: CDS
view based virtual data model for Utilities (see documentation
https://help.sap.com/viewer/6b356c79dea443c4bbeeaf0865e04207/1709%20000/en-
US/dde1c356a3386a15e10000000a441470.html and
https://go.support.sap.com/innovationdiscovery/#/innovation/6CAE8B27FCC31EE6A08
0E3EEE0531B00) and SAP BW/4HANA content for Utilities (see documentation
https://help.sap.com/viewer/06e872f914a44d77b6c692b0273ca400/1.0.1/en-
US/a3e19257660b6c10e10000000a441470.html). Please check the documentation for the
availability of the successors.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1444
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.
Following transactions are not available in SAP S/4HANA:
EI35
Set up stock statistics
EP01
Customizing: Transaction Statistics
EP02
Customizing: Stock Statistics
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.
Following BW Data Sources are not available anymore:
Stock and Transaction statistics (in brackets please find alternatives):
0UC_ISU_12 (0UCCONTRACT_ATTR_2)
0UC_ISU_13 (0UCINSTALLAH_ATTR_2)
0UC_ISU_14 (0UC_ISU_32)
0UC_ISU_15 (0UC_DEVINST_ATTR)
0UC_ISU_16 (0UC_SALES_STATS_02 or 0UC_SALES_STATS_03)
0UC_ISU_17 (0UC_SALES_STATS_02 or 0UC_SALES_STATS_03)
0UC_ISU_18 (0UC_DEVICE_ATTR and 0UC_DEVICER_ATTR)
0UC_ISU_19 (0UC_DEVICE_ATTR)
0UC_ISU_20 (0UC_DEVICE_ATTR)
0UC_ISU_22 (0BPARTNER_ATTR)
0UC_ISU_23 (0UC_ACCNTBP_ATTR_2)
0UC_ISU_24 (0UCCONTRACT_ATTR_2 and 0UCCONTRACTH_ATTR_2)
0UC_ISU_25 (0UCINSTALLAH_ATTR_2 or 0UCINSTALLA_ATTR_2)
0UC_ISU_26 (0UC_CONNOBJ_ATTR_2)
0UC_ISU_27 (0UCPREMISE_ATTR_2)
0UC_ISU_28 (0UC_DEVLOC_ATTR)
0UC_ISU_30 (0UC_DEVICE_ATTR and 0UC_DEVICER_ATTR)
0UC_ISU_31 (0UC_INSTFACTS)
Master Data and attributes (in brackets please find alternatives):
0UC_ACCNTBP_ATTR (0UC_ACCNTBP_ATTR_2)
0UC_CONNOBJ_ATTR (0UC_CONNOBJ_ATTR_2)
0UC_INDSECT_TEXT
0UC_TRANSPORT_TEST
0UCCONTRACT_ATTR (0UCCONTRACT_ATTR_2)
0UCCONTRACTH_ATTR (0UCCONTRACTH_ATTR_2)
0UCINSTALLA_ATTR (0UCINSTALLA_ATTR_2)
0UCINSTALLAH_ATTR (0UCINSTALLAH_ATTR_2)
0UCPREMISE_ATTR (0UCPREMISE_ATTR_2)
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1445
Other (in brackets please find alternatives):
0UC_ISU_CONSUMPT_02 (Sales Statistics shall be applied)
0UC_ISU_CONSUMPTION (Sales Statistics shall be applied)
0UC_SALES_SIMU_02 (0UC_SALES_SIMU_01, 0UC_SALES_SIMU_03)
0UC_SALES_STATS_01 (0UC_SALES_STATS_02, 0UC_SALES_STATS_03)
Regarding BW extractors and data sources in other line of businesses and industry areas,
please also refer to SAP note 2500202 of simplification item S4TWL - BW Extractors in SAP
S/4HANA.
Other Terms
Utilities Information System, UIS
61.15S4TWL - IS-U Sales Processing
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270507
S4TWL - IS-U Sales Processing
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1446
61.16S4TWL - Marketing - IS-U Loyalty Program
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270509
S4TWL - Marketing - IS-U Loyalty
Program
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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. Following transactions are not available in SAP S/4HANA:
EBW_DQ_CS
Marketing: Consumpt. -> Delta Queue
ECBWPP
Prepare Extrapolation Indexes
Usage of Loyalty Management is indicated by entries in table ELACC.
61.17S4TWL - Front Office (EC20) and CIC0 Configuration
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270510
S4TWL - Front Office (EC20) and CIC0
Configuration
Symptom
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1447
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
IS-U Front Office (transaction code EC20) is not available within SAP S/4HANA, on-
premise edition 1511.
The CIC Customizing Menu (area menu ISUCC) was removed with SAP S/4HANA, on-
premise edition 1511 FPS 04/1610 FPS 02/1709 FPS 00. Please note that transaction
CIC0 is not available within SAP S/4HANA, see note 2267412.
61.18S4TWL - GIS Business Connector
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270511
S4TWL - GIS Business Connector
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1448
61.19S4TWL - Enterprise Services for SAP for Utilities (IS-U)
Application Components:IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270513
S4TWL - Enterprise Services for SAP
for Utilities (IS-U)
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The following Enterprise Services for SAP for Utilities (IS-U) are not available in SAP
S/4HANA, on-premise 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.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1449
Please check referenced notes 1541831 - UtilitiesConnectionProcessing enterprise services in EHP5 -
and 1527380 - Deprecated ES, EHP6 for ERP, UtilitiesTimeSeriesProcessing - for detailled
information.
61.20S4TWL - Central and Eastern European localization for Utility & Telco
Application Components:XX-CSC-HU-IS-U, XX-CSC-GR-FICA, XX-CSC-RU-IS-U, XX-CSC-SI-
IS-U, XX-CSC-TR-IS-U, XX-CSC-GR-IS-U, XX-CSC-SI-FICA, XX-CSC-HU-FICA, XX-CSC-SK-
FICA, XX-CSC-PL-IS-U, XX-CSC-UA-FICA, XX-CSC-BG-IS-U, XX-CSC-PL-FICA, XX-CSC-RU-
FICA, XX-CSC-RO-FICA, XX-CSC-CZ-FICA, XX-CSC-BG-FICA, XX-CSC-UA-IS-U, XX-CSC-SK-
IS-U, XX-CSC-RO-IS-U, XX-CSC-CZ-IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2338097
S4TWL - Utility & Telco related
Business Functions
Symptom
You are doing a system conversion to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
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
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':
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1450
Business Function /SAPCE/ISU_LOC_CEE
Switch /SAPCE/ISU_LOC_CEE_SFWS_02
Switch Package /SAPCE/IU_LOC_CEE_SFWS_02
Switch /SAPCE/FICA_LOC_CEE_SFWS_02
Switch Package SAPCE/FK_LOC_CEE_SFWS_02
Business Function ISU_UTIL_WASTE
Switch /SAPCE/ISU_LOC_CEE_SFWS_01
Switch Package /SAPCE/IU_LOC_CEE_SFWS_01
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
Switch /SAPCE/FICA_LOC_CEE_SFWS_02
Switch Package /SAPCE/FK_LOC_CEE_SFWS_02
Business Function /SAPCE/TEL_LOC_CEE_HIDDEN
Switch /SAPCE/ISU_LOC_CEE_SFWS_01
Switch Package /SAPCE/IU_LOC_CEE_SFWS_01
Business Function RM_CA
Switch /SAPCE/FICA_LOC_CEE_SFWS_01
Switch Package /SAPCE/FK_LOC_CEE_SFWS_01
Business Process related information
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1451
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.
Other Terms
S4TWL, S4TC, CEEISUT, Pre-Check Class, SAP IS-UT CEE
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1452
62.SAP Ariba
62.1 S4TWL - Ariba Cloud Integration
Application Components:BNS-ARI-TRF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2400737
Ariba Cloud Integration Solutions for
SAP: Supported SAP Product Versions
Symptom
You are planning to use SAP and Ariba Solutions integrated with Integration
Adapters provided by the SAP Ariba Cloud Integration program, or you are
already live with it and are considering an upgrade of one of the solutions. To
plan your project, you need to know the supported versions and constraints with
respect to upgrades.
During upgrade or conversion check, an error is issued in check class
CLS4SIC_ARIBA_CI_CHECK (RC = 7): Go to Solution -> Information for
upgrade and conversion
Reason and Prerequisites
You are using or you are planning to use the Ariba Cloud Integration Solution (CI), that
you can download from Ariba Connect. Or you are planning to use the Ariba Cloud
Integration Gateway (CIG) Add-On for SAP ERP or S/4HANA.
This note is not relevant for integration solutions provided by the 'Ariba Integration Suite'
(Add-On) that you can download from the SAP Service Marketplace.
Solution
The following SAP Product versions are supported with Ariba Cloud Integration:
CI-Version
CI-6
CI-7
CI-8
CI-9
CI-9
SP1
CI-9
SP2 #
CIG*
SAP Product Version
SAP ERP 6.0*
X
X
X
X
EHP1 FOR SAP ERP 6.0*
X
X
X
X
EHP2 FOR SAP ERP 6.0*
X
X
X
X
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1453
EHP3 FOR SAP ERP 6.0*
X
X
X
X
EHP4 FOR SAP ERP 6.0*
X
X
X
X
X
X
EHP5 FOR SAP ERP 6.0*
X
X
X
X
X
X
X
EHP6 FOR SAP ERP 6.0*
X
X
X
X
X
X
X
EHP7 FOR SAP ERP 6.0*
X
X
X
X
X
X
X
EHP8 FOR SAP ERP 6.0
X
X
X
X
SAP SFINANCIALS 1503
X
X
X
X
X
SAP S/4HANA FINANCE 1605
X
X
X
SAP S/4HANA 1511 OnPremise
X
X
X
X
SAP S/4HANA 1610 OnPremise
X
X
X
SAP S/4HANA 1709 OnPremise
X SP2
HF8
X
SAP S/4HANA 1809 OnPremise
X
SAP S/4HANA 1909 OnPremise
X
SAP S/4HANA 2020 OnPremise
X
SAP S/4HANA 2021 OnPremise
X
SAP S/4HANA 2022 OnPremise
X
* Note that some integration scenarios require a minimum EHP Version. Refer to the
documentation of your CI Version X on the required EHP Versions for scenarios in your
implemenation scope.
You must not use an Ariba Cloud Integration Version with a non-supported SAP Product
Version.
IMPORTANT: Consider the follwing information if you are planning to upgrade your
SAP Product.
If you haven't done this already, you should consider upgrading to the Ariba Cloud
Integration Gateway (CIG). This will avoid the potential conflicts described below. CIG
is the unique integration solution going forward and no further development for other
solutions will be made, and product maintenance will be ending after a certain period.
Information for upgrade and conversion
You can only upgrade to a SAP Product Version that is supported by the Ariba Cloud Integration
program. Some integration scenarios will be broken if you upgrade to a non-supported SAP
Product Version. Support is not granted by SAP Ariba for any inquiries related to such
incidents.
SAP Ariba delivered the Cloud Integration programs (CI-9) through SAP transport files within an
exclusive namespace registered with SAP. The solution is supported by SAP Ariba as per the
Ariba Support policy (see section below 'Supported Versions for CI'). However, due to the
nature of transport objects, the programs are considered as customer objects during upgrade
with Software Update Manager (SUM). During the upgrade, you have to ensure that Ariba
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1454
Objects including table contents are retained. Due to their origin from transport files, Ariba
Objects can get deleted during an upgrade. To avoid this, make sure that note 2402191 is
applied in your system, if you want to continue using this solution.
During upgrades and conversions, a detailed check is executed by Software Update Manager
(SUM). In case that CI objects can be found in the system, that have been imported through
transport files (for example CI-9), the check returns error code RC = 7. In this case, you have
to confirm that you have either migrated to CIG already or that you have run the report
attached to note 2402191. You can confirm this by adding an exemption to the check result.
This procedure is described in detail here: https://blogs.sap.com/2018/03/26/sap-s4hana-
simplification-item-check-how-to-do-it-right./
After you have migrated to CIG, you do not longer need to run run the report attached to note
2402191 prior to upgrades. CI objects, that have been imported through transport files (for
example CI-9) will be deleted during the next upgrade.
# Supported Versions for CI:
With SAP’s standard integration platform released with SAP Ariba Cloud Integration
Gateway (CIG) to integrate SAP Ariba solutions with SAP ERP systems, previous
integration tools such as Cloud Integration (CI) and Business Suite Add-On are no
longer available for new installations and no further enhancements will be made. At this
time, only CI-9 version is the only supported version for break fixes while previous CI
versions are deprecated and no longer supported.
* CIG Support Pack - Support Policy:
To adhere with the standard SAP support model, SAP Ariba will only support the current (version N)
and the version preceding the current version (version N-1) for the SAP Ariba Cloud Integration
Gateway. CIG has 3 components ARBCI1, ARBCI2 & ARBCIGR and each of these components
could be at different SP level. Current version is determined from the component with highest Support
Pack level.
For example, with the support package SP 0008 release, ARBCI1 is SP008 while
ARBCI2 is SP006 and ARBCIGR is SP0001 and SAP Ariba supports the following
versions:
· Current released version (version n) – for example, ARBCI1: SP 0008
· Preceding released version (version n-1)– for example, ARBCI1: SP 0007
SAP Ariba recommends that customers must always upgrade to the latest SP release that
is available at GA (General Availability) / RTC (Released To customer). The new
releases always include additional enhancements and new features and customers can
benefits from these functionalities.
Simplification List for SAP S/4HANA 2023 – Initial Shipment & Feature Pack Stack 1 and
SAP S/4HANA Cloud Private Edition 2023 – Initial Shipment & Feature Pack Stack 1
Page | 1455
Other Terms
Cloud Integration CI-9 CI-8 CI-7 CI-6 Upgrade CIG SI01 Ariba Cloud Integ
