White Paper
Document Version: 1.08 – 2018-09-19
Simplification List for SAP S/4HANA 1809
Initial Shipment Stack
PUBLIC
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Table of Content
1
2
Introduction ................................................................................................................................. 21
1.1
Purpose of the Document .......................................................................................................... 22
1.2
General Topics for the Simplification List .................................................................................. 22
1.3
System Conversion Sequence..................................................................................................... 24
1.4
The Simplification List 1809 Initial Shipment Stack – this document .......................................... 25
Cross Topics ................................................................................................................................ 28
2.1
ABAPTWL - No support for non simplified system flavour ......................................................... 28
2.2
ABAPTWL - Cleanup of orphaned objects ................................................................................. 28
2.3
ABAPTWL - SSCR license key procedure is no longer supported ............................................... 29
2.4
S4TWL - Removal of Business Application Accelerator .............................................................. 31
2.5
ABAPTWL - VM Container not supported ................................................................................. 32
2.6
ABAPTWL - AS Java not available ............................................................................................ 33
2.7
ABAPTWL - Dual Stack not supported ...................................................................................... 33
2.8
ABAPTWL - Instances without ICM not supported..................................................................... 34
2.9
ABAPTWL - End of Support for Pool Tables.............................................................................. 35
2.10
S4TWL - FIORI APPLICATIONS FOR SUITE ON HANA ON-PREMISE .............................. 38
2.11
S4TWL - SAP S/4HANA AND SAP BUSINESS WAREHOUSE CONTENT ............................. 40
2.12
S4TWL - Social Intelligence.................................................................................................. 41
2.13
S4TWL - Custom Fields ........................................................................................................ 42
2.14
S4TWL - Side Panel functionality in SAP S/4HANA (on-premise) .......................................... 43
2.15
S4TWL - Changed Interfaces ................................................................................................ 47
2.16
S4TWL - Changes in Process Observer ................................................................................. 49
2.17
S4TWL - BI Extractors in SAP S/4HANA .............................................................................. 51
2.18
S4TWL - MRS Enhancements for Material Master ................................................................ 55
2.19
S4TWL - CDS Views with DCL0 ........................................................................................... 56
2.20
S4TWL - Business User Management.................................................................................... 57
2.21
S4TWL - Generic Check for SAP S/4HANA Conversion and Upgrade ................................... 63
2.22
S4TWL - OUTPUT MANAGEMENT ..................................................................................... 65
2.23
S4TWL - SAP HANA LIVE REPORTING .............................................................................. 67
2.24
S4TWL - ENTERPRISE SEARCH ......................................................................................... 68
Page | 2
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
3
4
2.25
S4TWL - Duplicate request entries in Output Management.................................................... 69
2.26
S4TWL - Ariba Network Integration...................................................................................... 71
2.27
S4TWL - INTERNET PRICING AND CONFIGURATOR (SAP IPC) ..................................... 73
2.28
S4TWL - JOB SCHEDULING............................................................................................... 75
2.29
S4TWL - LEGACY SYSTEM MIGRATION WORKBENCH .................................................... 77
Master Data ................................................................................................................................. 81
3.1
S4TWL - MDM 3.0 integration .................................................................................................. 81
3.2
S4TWL - SRM Product Master .................................................................................................. 82
3.3
S4TWL - Logistics Batch Management ...................................................................................... 84
3.4
S4TWL - Product catalog .......................................................................................................... 85
3.5
S4TWL - Object Identifier Type Code ........................................................................................ 86
3.6
S4TWL: Business partner data exchange between SAP CRM and S/4HANA ............................... 87
3.7
S4TWL - HANA-based Analytics for Master Data Governance................................................... 90
3.8
S4TWL - Business Partner BUT000/Header Level Time Dependency ......................................... 91
3.9
S4TWL - BADI ADDRESS_SEARCH (Duplicate Check) is Not Supported in SAP S/4HANA....... 93
3.10
S4TWL - Business Partner Hierarchy Not Available.............................................................. 95
3.11
S4TWL - MDG in Lama ........................................................................................................ 96
3.12
S4TWL - MDG_MDC in Lama.............................................................................................. 97
3.13
S4TWL - Batch Input for Customer Master/Supplier Master .................................................. 98
3.14
S4TWL - API RFC_CVI_EI_INBOUND_MAIN is obsolete.................................................... 99
3.15
S4TWL - Business Partner Approach .................................................................................. 100
3.16
S4TWL - Reduction of Redundant Business Partner Data Storage in the 'BUTADRSEARC .. 105
3.17
S4TWL - Simplified Product Master Tables Related to OMSR Transaction .......................... 107
3.18
S4TWL - Material Number Field Length Extension ............................................................. 108
3.19
S4TWL - Simplification of copy/reference handling ............................................................. 116
3.20
S4TWL - Foreign Trade fields in Material Master ............................................................... 118
3.21
S4TWL - MRP fields in Material Master ............................................................................. 119
3.22
S4TWL - Material Type SERV............................................................................................. 121
Commercial Project Management ............................................................................................ 126
4.1
S4TWL - CPM - Rate Card...................................................................................................... 126
4.2
S4TWL - Interface of SAP CPM with SAP Cloud for Customer ................................................ 126
4.3
S4TWL - Fiori Apps of SAP Commercial Project Management ................................................ 127
4.4
S4TWL - Launchpads of Gantt Chart and Commercial Project Inception ................................. 128
4.5
S4TWL - Workbooks in Project Cost and Revenue Planning .................................................... 129
Page | 3
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
5
6
7
Commodity Management .......................................................................................................... 131
5.1
S4TWL - CM: Simplified Market Data .................................................................................... 131
5.2
S4TWL - CM: Simplified CPE Activation ................................................................................ 132
5.3
S4TWL - CM: CPE Simplified Formula Assembly & Formula Evaluation ................................ 133
5.4
S4TWL - CM: CPE Simplification of Routines & Rules ........................................................... 133
5.5
S4TWL - CM: CPE Simplified Data Model ............................................................................. 134
5.6
S4TWL - Simplified Commodity Curves ................................................................................... 135
5.7
S4TWL - Simplified DCS Access .............................................................................................. 136
5.8
S4TWL - Simplification in Position Reporting for Financial Transactions ................................ 136
5.9
S4TWL - Simplified Data Flow of logistics data for Risk Reporting Database .......................... 138
5.10
S4TWL - Position Reporting on versioned pricing data ....................................................... 139
5.11
S4TWL - Hedge Management for logistics transactions ....................................................... 140
5.12
S4TWL - Position Reports delivered by Agricultural Contract Management ........................ 141
5.13
S4TWL - Risk Determination and Pricing for MM Contracts not supported yet .................... 142
5.14
S4TWL - Unification of supported technologies in analytical data provisioning ................... 143
5.15
S4TWL - Risk Determination on a schedule line level .......................................................... 145
5.16
S4TWL - Simplification of DCS based Market Data Handling for Fin Transactions ............. 146
5.17
S4TWL - Deprecation of Non DCS based Market Data for Financial Transactions .............. 147
5.18
S4TWL - Deprecation of functions using Non DCS based Market Data................................ 148
5.19
S4TWL - Simplified Data Model/Master Data ..................................................................... 149
5.20
S4TWL – Contract Processing Monitor & Logistical Options w/ GTM not supported .......... 151
5.21
S4TWL - Mark-to-Market & Profit-and-Loss Reporting for logistics transactions ................ 151
5.22
S4TWL - Mark-to-Market & Profit-and-Loss Reporting for Derivatives............................... 153
5.23
S4TWL - Mark to Market Accounting Changes.................................................................... 154
5.24
S4TWL – Integration of Pricing and Payment Events in GTM with Commodity Mngmt. ....... 155
5.25
S4TWL – Functionalities on roadmap for CM-GTM Integration .......................................... 156
Customer Service....................................................................................................................... 157
6.1
S4TWL - PH_Sample iView ..................................................................................................... 157
6.2
S4TWL - Customer Interaction Center (CIC) ........................................................................... 158
Enterprise Controlling .............................................................................................................. 160
7.1
8
Usage of long Material Number in EC-CS ............................................................................... 160
Financials – General .................................................................................................................. 161
8.1
S4TWL - DATA MODEL CHANGES IN FIN ........................................................................... 161
8.2
S4TWL - REPLACED TRANSACTION CODES AND PROGRAMS IN FIN .............................. 168
Page | 4
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
9
10
Financials - Accounts Payable/Accounts Receivable ................................................................ 172
9.1
S4TWL - SAP Working Capital Analytics/DSO and DPO ......................................................... 172
9.2
S4TWL - Integration with FSCM Biller Direct (FI-AR) ............................................................ 173
9.3
S4TWL - Integration with FSCM Biller Direct (FI-AP) ............................................................ 174
Financials - Asset Accounting ................................................................................................... 175
10.1
S4TWL - DATA STRUCTURE CHANGES IN ASSET ACCOUNTING ................................. 175
10.2
S4TWL - ASSET ACCOUNTING......................................................................................... 177
10.3
S4TWL - ASSET ACCOUNTING......................................................................................... 194
10.4
S4TWL - INTEGRATION TO LEASE ACCOUNTING ENGINE (LAE) ................................ 211
10.5
S4TWL - JOINT VENTURE ACCOUNTING (JVA) ............................................................. 212
10.6
S4TWL - SELECTED BUSINESS FUNCTIONS IN FINANCIAL ACCOUNTING (FI-GL AND
FI-AA) 213
11
Financials - Cash Management ................................................................................................. 217
11.1
12
13
S4TWL - CASH MANAGEMENT - GENERAL .................................................................... 217
Financials – Controlling ............................................................................................................ 229
12.1
S4TWL - Reference and Simulation Costing ........................................................................ 229
12.2
S4TWL - Summarization Hierarchies in Controlling ........................................................... 230
12.3
S4TWL - Technical Changes in Material Ledger with Actual Costing .................................. 232
12.4
S4TWL - TECHNICAL CHANGES IN CONTROLLING ...................................................... 239
12.5
S4TWL - PROFIT AND LOSS PLANNING AND PROFIT CENTER PLANNING ................. 241
12.6
S4TWL - ACTIVITY-BASED COSTING .............................................................................. 245
12.7
S4TWL - GENERAL COST OBJECTS AND COST OBJECT HIERARCHIES ...................... 247
12.8
S4TWL - TRANSFER PRICES/ PARALLEL DELTA VERSIONS .......................................... 250
12.9
S4TWL - COST ELEMENTS ............................................................................................... 253
12.10
S4TWL - Reporting/Analytics in Controlling ....................................................................... 256
12.11
S4TWL - Profitability Analysis............................................................................................ 260
Financials - General Ledger ...................................................................................................... 263
13.1
S4TWL - GENERAL LEDGER ............................................................................................ 263
13.2
S4TWL - SAP HANA ODP ON HANA CALC VIEW-BASED REPORTING .......................... 265
13.3
S4TWL - Closing Cockpit with S/4 HANA OP ..................................................................... 266
13.4
S4TWL - Currencies in Universal Journal........................................................................... 267
13.5
S4TWL - Manual Accruals (Accrual Engine)....................................................................... 272
13.6
S4TWL - Amount Field Length Extension ............................................................................ 275
Page | 5
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
14
15
16
17
Financials - International Trade ............................................................................................... 284
14.1
S4TWL - Material classification with commodity codes ....................................................... 284
14.2
S4TWL - Personal Data in Provider of Information............................................................. 285
14.3
S4TWL - Determination of default values in Intrastat reporting ........................................... 286
Financials - Treasury and Risk Management ........................................................................... 290
15.1
S4TWL - Drilldown Reporting in Treasury and Risk Management ....................................... 290
15.2
S4TWL - Master Agreements .............................................................................................. 291
15.3
S4TWL - Offers .................................................................................................................. 292
15.4
S4TWL - Simulation in Transaction Management ................................................................ 293
15.5
S4TWL - Quantity Ledger Always Active for Money Market Transactions ........................... 293
15.6
S4TWL - Several Kinds of Financial Objects Disabled ........................................................ 295
15.7
S4TWL - Allocation of FX Transactions to Financial Documents and Cash Management .... 297
15.8
S4TWL - Correspondence Functionality.............................................................................. 298
15.9
S4TWL - Interest Rate and Yield Curve Functionality.......................................................... 299
15.10
S4TWL - Accrual/Deferral of Expenses and Revenues ......................................................... 301
15.11
S4TWL - Credit Risk Analyzer Link to Cash Management ................................................... 303
15.12
S4TWL - Exposure Management 1.0 ................................................................................... 304
15.13
S4TWL - Drawable Bonds .................................................................................................. 306
Financials – Miscellaneous ........................................................................................................ 308
16.1
S4TWL - Credit Management.............................................................................................. 308
16.2
S4TWL - Technical Changes in Material Ledger ................................................................. 312
16.3
S4TWL - Real Estate Classic............................................................................................... 314
16.4
S4TWL - SAP Data Aging for SAP S/4HANA Finance ......................................................... 315
16.5
S4TWL - Conversion to S/4HANA Material Ledger and Actual Costing ............................... 317
16.6
S4TWL - Differentiation Category Dependent FS Datasets Not Available in S/4HANA ........ 322
16.7
S4TWL - Product Design Cost Estimate .............................................................................. 324
Human Resources ...................................................................................................................... 328
17.1
S4TWL - General HCM Approach within SAP S/4HANA ..................................................... 328
17.2
S4TWL - Conversion of Employees to Business Partners ..................................................... 330
17.3
S4TWL - SAP Learning Solution ......................................................................................... 331
17.4
S4TWL - SAP E-Recruiting ................................................................................................. 332
17.5
S4TWL - Java-Based ESS and MSS ..................................................................................... 334
17.6
S4TWL - SAP Travel Management ...................................................................................... 335
Page | 6
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
18
19
Logistics – General .................................................................................................................... 336
18.1
S4TWL - Advanced Track & Trace...................................................................................... 336
18.2
S4TWL - Season Field Length Extension ............................................................................. 337
Logistics – AB ............................................................................................................................ 339
19.1
20
Logistics – ATP.......................................................................................................................... 355
20.1
21
S4TWL - Agency Business................................................................................................... 339
S4TWL - New advanced ATP in SAP S/4HANA – Table VBBS ............................................. 355
Logistics - Environment, Health & Safety (EHS) ..................................................................... 357
21.1
S4TWL - Deprecation of EHS Data Series and Amounts ...................................................... 357
21.2
S4TWL - Deprecation of 'Inspect Safety Control' Fiori app ................................................. 358
21.3
S4TWL - Deprecation of 'Retrieve Safety Information' Fiori app ......................................... 359
21.4
S4TWL - Simplification of Authorizations in Incident Management ...................................... 360
21.5
S4TWL - Removal of EHS Home Screens ............................................................................ 362
21.6
S4TWL - Specification Workbench Adjustments................................................................... 363
21.7
S4TWL - Simplification of Incident Management workflows ................................................ 364
21.8
S4TWL - Changed data model for Occupational Exposure Limits ........................................ 366
21.9
S4TWL - Removal of task und document tab pages on incidents........................................... 368
21.10
S4TWL - Changed process for risk identification................................................................. 370
21.11
S4TWL - Industrial Hygiene and EC interfaces ................................................................... 371
21.12
S4TWL - Renovation of EHS authorization concept ............................................................. 373
21.13
S4TWL - Changed data model for Job Steps ........................................................................ 376
21.14
S4TWL - Adjustments needed due to changed data model for Compliance Requirement ....... 378
21.15
S4TWL - Deprecation of action templates in control master ................................................ 380
21.16
S4TWL - Simplification of Risk Assessment Lifecycle........................................................... 381
21.17
S4TWL - Renovation of task management ........................................................................... 382
21.18
S4TWL - Deprecation of Mapping Workbench in Foundation of EHS .................................. 384
21.19
S4TWL - Occupational Health ............................................................................................ 385
21.20
S4TWL - Waste Management .............................................................................................. 387
21.21
S4TWL - Simplification in Incident Management and Risk Assessment ................................ 388
21.22
S4TWL - Removal of EHS workflows for requesting controls, impacts, agents ..................... 390
21.23
S4TWL - Responsible person for Planned Maintenance at EHS locations ............................ 392
21.24
S4TWL - Remote Integration Scenarios with EHS Health and Safety Management............... 393
21.25
S4TWL - Conversion relevant changes in EHS .................................................................... 394
Page | 7
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
22
Logistics – GT ............................................................................................................................ 396
22.1
23
Logistics - Management of Change ........................................................................................... 399
23.1
24
25
S4TWL - Global Trade Management ................................................................................... 396
S4TWL - Simplifications in Management of Change ............................................................ 399
Logistics - MM-IM .................................................................................................................... 403
24.1
S4TWL - FMP in S4HANA.................................................................................................. 403
24.2
S4TWL - Blocked customer or supplier in Inventory Management ....................................... 404
24.3
S4TWL - Document Flow Consistency for Goods Receipt to Inbound Delivery .................... 407
24.4
S4TWL - DATA MODEL IN INVENTORY MANAGEMENT (MM-IM)................................. 411
24.5
S4TWL - AVAILABILITY OF TRANSACTIONS IN MM-IM ................................................. 421
24.6
S4TWL - Material Ledger Obligatory for Material Valuation .............................................. 423
24.7
S4TWL - Material Valuation - Statistical moving average price........................................... 426
24.8
S4TWL - Performance optimizations within Material Document Processing - lock beh ........ 428
24.9
S4TWL - Material Valuation Data Model Simplification in S/4HANA 1610 and Higher ....... 435
24.10
S4TWL - Goods movements without exclusive locking by material valuation........................ 436
24.11
S4TWL - CWM in SAP S/4HANA ........................................................................................ 438
Logistics – PLM ......................................................................................................................... 445
25.1
S4TWL - Engineering Desktop (EDesk)............................................................................... 445
25.2
S4TWL - DMS - STEP Support ........................................................................................... 446
25.3
S4TWL - DMS Documents@WEB ....................................................................................... 447
25.4
S4TWL - Variant Configuration .......................................................................................... 448
25.5
S4TWL - Classification ....................................................................................................... 449
25.6
S4TWL - IPPE-BOM Converter .......................................................................................... 454
25.7
S4TWL - BOM, Routing, Production Version ...................................................................... 455
25.8
S4TWL - SAP PLM Recipe Development ............................................................................. 456
25.9
S4TWL - Engineering Change Management ECR/ECO ....................................................... 458
25.10
S4TWL - Enterprise Search in SAP Product Lifecycle Management (SAP PLM) .................. 459
25.11
S4TWL - Engineering Change Management Change Sequence Graph ................................. 461
25.12
S4TWL - Engineering Workbench ....................................................................................... 462
25.13
S4TWL - Collaborative Engineering ................................................................................... 463
25.14
S4TWL - iPPE Time Analysis.............................................................................................. 464
25.15
S4TWL - Integration to SAP Portfolio and Project Management ......................................... 465
25.16
S4TWL - Routing Component Assignment ........................................................................... 466
25.17
S4TWL - Release Management Framework ......................................................................... 467
Page | 8
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
26
27
25.18
S4TWL - Engineering Record ............................................................................................. 468
25.19
S4TWL - PLM Labeling Usage ........................................................................................... 469
25.20
S4TWL - Engineering Record with LAMA ........................................................................... 470
25.21
S4TWL - Assemblies ........................................................................................................... 471
25.22
S4TWL - New Access Control Management......................................................................... 472
25.23
S4TWL - Product Designer Workbench ............................................................................... 473
25.24
S4TWL - Access Control Management (ACM) ..................................................................... 474
25.25
S4TWL - cFolders............................................................................................................... 476
25.26
S4TWL - cDesk ................................................................................................................... 477
25.27
S4TWL - Recipe Management ............................................................................................. 478
25.28
S4TWL - Engineering Client Viewer (ECL) ......................................................................... 480
25.29
S4TWL - Easy Document Management (Easy DMS) ............................................................ 481
Logistics – PM ........................................................................................................................... 483
26.1
S4TWL - Object List Number Field Length Extension .......................................................... 483
26.2
S4TWL - LIS in EAM .......................................................................................................... 484
26.3
S4TWL - Download Data in MS Access out of List .............................................................. 486
26.4
S4TWL - Scheduling of Maintenance Plan .......................................................................... 487
26.5
S4TWL - Mobile Asset Management (MAM) ....................................................................... 488
26.6
S4TWL - Batch Input for Enterprise Asset Management (EAM) ........................................... 488
26.7
S4TWL - Change Order and Operations IW37,IW49 ........................................................... 490
26.8
S4TWL - WebDynpro Application for Maintenance Planner (<= EhP4) .............................. 491
26.9
S4TWL - Enterprise Search in EAM .................................................................................... 492
26.10
S4TWL - SAP Graphics in EAM Transactions ..................................................................... 493
Logistics – PP............................................................................................................................. 495
27.1
S4TWL - ERP Line-Balancing and Sequencing ................................................................... 495
27.2
S4TWL - MRP in HANA ..................................................................................................... 496
27.3
S4TWL - Planning File ....................................................................................................... 501
27.4
S4TWL - Total Dependent Requirements ............................................................................. 504
27.5
S4TWL - Forecast Based Planning ..................................................................................... 505
27.6
S4TWL - Demand Forecasting ............................................................................................ 506
27.7
S4TWL - Release status for different RFC function modules revoked ................................... 507
27.8
S4TWL - Computer Aided Processing Planning (CAP) ........................................................ 508
27.9
S4TWL - ABAP-List-Based PI-Sheets .................................................................................. 510
27.10
S4TWL - ANSI/ISA S95 Interface ........................................................................................ 511
Page | 9
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
28
27.11
S4TWL - PP-MRP - Subcontracting .................................................................................... 512
27.12
S4TWL - Digital Signature.................................................................................................. 514
27.13
S4TWL - Electronic Records ............................................................................................... 515
27.14
S4TWL - Downtimes Functionality...................................................................................... 516
27.15
S4TWL - MiniApps PP-PI ................................................................................................... 517
27.16
S4TWL - Process Data Evaluation (PP-PI-PEV) ................................................................. 518
27.17
S4TWL - Campaign Weighing and Dispensing .................................................................... 518
27.18
S4TWL - Production Campaign (ERP) ................................................................................ 519
27.19
S4TWL - Electronic Batch Record....................................................................................... 520
27.20
S4TWL - Process Messages ................................................................................................ 521
27.21
S4TWL - Control Recipes/Instructions ................................................................................ 521
27.22
S4TWL - Storage Location MRP ......................................................................................... 522
27.23
S4TWL - Process Operator Cockpits ................................................................................... 524
27.24
S4TWL - Material Identification/Reconciliation .................................................................. 525
27.25
S4TWL - Flow Manufacturing............................................................................................. 526
27.26
S4TWL - Process Flow Scheduling (PP-PI)......................................................................... 526
27.27
S4TWL - Rate and Rough-Cut Planning .............................................................................. 527
27.28
S4TWL - Planning Horizon ................................................................................................. 529
27.29
S4TWL - Batch History ....................................................................................................... 530
27.30
S4TWL - Selected Business Functions in PP area ................................................................ 531
27.31
S4TWL - External Interfaces in PP ..................................................................................... 533
27.32
S4TWL - Graphical Planning Table .................................................................................... 536
27.33
S4TWL - Logistic Information System in PP ........................................................................ 537
27.34
S4TWL - Sales and Operation Planning .............................................................................. 539
27.35
S4TWL - Simplified Sourcing .............................................................................................. 540
27.36
S4TWL - Browser-based Process Instruction-Sheets/Electronic Work Instructions............... 546
27.37
S4TWL - Internet Kanban ................................................................................................... 547
Logistics – PP/DS ....................................................................................................................... 550
28.1
29
S4TWL - Performance optimizations for publication of planning orders .............................. 550
Logistics – PS ............................................................................................................................. 553
29.1
S4TWL - Simplification of Date Planning Transactions ....................................................... 553
29.2
S4TWL - Workforce Planning ............................................................................................. 554
29.3
S4TWL - Progress Tracking & Monitoring Dates ................................................................ 555
29.4
S4TWL - Project Claim Factsheet ....................................................................................... 556
Page | 10
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
30
31
29.5
S4TWL - Project Reporting ................................................................................................. 557
29.6
S4TWL - Selected Project System Interfaces ........................................................................ 562
29.7
S4TWL - Construction Progress Report and Valuation ........................................................ 563
29.8
S4TWL - Project System ITS Services.................................................................................. 564
29.9
S4TWL - Selected PS Business Function Capabilities .......................................................... 565
29.10
S4TWL - Selected Logistics Capabilities ............................................................................. 567
29.11
S4TWL - Simplification of maintenance transactions ........................................................... 568
29.12
S4TWL - Selected Project System BAPIs ............................................................................. 569
29.13
S4TWL - Handling Large Projects Business Functions ........................................................ 570
29.14
S4TWL - Navigation to Project Builder instead of special maintenance functions ................ 572
29.15
S4TWL - Production Resources and Tools functions for projects ......................................... 573
29.16
S4TWL - Project Planning Board, Gantt-Chart, Hierarchy and Network Graphics .............. 574
29.17
S4TWL - Current simulation functions in project system...................................................... 575
29.18
S4TWL - Specific PS archiving transactions ........................................................................ 576
29.19
S4TWL - Project texts (PS texts) ......................................................................................... 577
29.20
S4TWL - Claim Management .............................................................................................. 578
29.21
S4TWL - Selected project financial planning and control functions ..................................... 579
Logistics – PSS ........................................................................................................................... 582
30.1
S4TWL - PS&S SARA Reports ............................................................................................ 582
30.2
S4TWL - Substance Volume Tracking Selection Criteria based on tables VBUK and VB ...... 582
30.3
S4TWL - Simplification in Product Compliance for Discrete Industry .................................. 585
30.4
S4TWL - QM Interface ....................................................................................................... 587
30.5
S4TWL - PS&S Enterprise Search Model ............................................................................ 588
30.6
S4TWL - Hazardous Substance Management ...................................................................... 588
30.7
S4TWL - Add-On: SAP Product and REACH Compliance (SPRC)....................................... 589
30.8
S4TWL - Add-On: EHS Web-Interface ................................................................................ 591
30.9
S4TWL - Add-On: Genifix (Labelling solution) ................................................................... 592
30.10
S4TWL - BW Extractors for Dangerous Goods Management and Specification Managemen 592
Logistics – QM ........................................................................................................................... 594
31.1
S4TWL - Quality Management Information System (QMIS) ................................................. 594
31.2
S4TWL - Quality Inspection Engine (QIE) .......................................................................... 595
31.3
S4TWL - Redundant Transactions in QM ............................................................................ 595
31.4
S4TWL - Removed Navigation to Transactions for Evaluations in QM................................. 597
31.5
S4TWL - Authorization Objects in QM ................................................................................ 598
Page | 11
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
32
33
31.6
S4TWL - Results Recording ................................................................................................ 600
31.7
S4TWL - ITS services in QM ............................................................................................... 601
31.8
S4TWL - QM WEB Workplace (MiniApps) based on ITS Services ....................................... 603
Logistics – TRA ......................................................................................................................... 606
32.1
S4TWL - Transportation (LE-TRA) ..................................................................................... 606
32.2
S4TWL - Transportation (LE-TRA) External Planning IDOCS ............................................ 607
Logistics – WM .......................................................................................................................... 608
33.1
34
S4TWL - Warehouse Management (WM) ............................................................................ 608
Portfolio and Project Management (PPM) ............................................................................... 609
34.1
S4TWL - Web Dynpro Applications for Resource Maintenance in SAP Portfolio and Pr ...... 609
34.2
S4TWL - Workforce Deployment (WFD) integration in SAP Portfolio and Project Mana ..... 610
34.3
S4TWL - Integration to SAP cFolders in SAP Portfolio and Project Management for .......... 611
34.4
S4TWL - KM Documents in SAP Portfolio and Project Management for SAP S/4HANA ...... 612
34.5
S4TWL - SRM Integration in SAP Portfolio and Project Management for SAP S/4HANA ..... 613
34.6
S4TWL - cFolders not available anymore in SAP Portfolio and Project Management f ........ 614
34.7
S4TWL - Global Settings in SAP Portfolio and Project Management for SAP S/4HANA....... 615
34.8
S4TWL - Fiori apps of UI FOR SAP PORTF PROJ MGMT 6.0 in SAP Portfolio and Projec 623
34.9
S4TWL - Portfolio Structure Graphic in SAP Portfolio and Project Management for ........... 624
34.10
S4TWL - SAP Smart Forms in SAP Portfolio and Project Management for SAP S/4HANA ... 625
34.11
S4TWL - Resource Management Web Dynpro Views in SAP Portfolio and Project Manage . 626
34.12
S4TWL - WebDAV and EasyDMS Integration in SAP Portfolio and Project Management f .. 627
34.13
S4TWL - SAP Portal Integration in SAP Portfolio and Project Management for SAP S ........ 628
34.14
S4TWL - cRoom Integration in SAP Portfolio and Project Management for SAP S/4HAN .... 628
34.15
S4TWL - xPD Integration in SAP Portfolio and Project Management for SAP S/4HANA ..... 629
34.16
S4TWL - Xcelsius Integration in SAP Portfolio and Project Management for SAP S/4 ......... 630
34.17
S4TWL - SAP BusinessObjects Explorer Integration in SAP EPPM ..................................... 631
34.18
S4TWL - Project simulation in SAP Portfolio and Project Management for SAP S/4H ......... 632
34.19
S4TWL - Simplification of data model in SAP Portfolio and Project Management for .......... 633
34.20
S4TWL - Deletion of obsolete packages in EPPM ............................................................... 634
34.21
S4TWL - Business Partner in SAP Portfolio and Project Management for SAP S/4HANA .... 634
34.22
S4TWL - Simplified ACLs (Access Control Lists) concept in SAP Portfolio and Proj ............ 636
34.23
S4TWL - Handling of actual date in scheduling (EPPM) ..................................................... 638
34.24
S4TWL - SAP Web Dynpro usage in SAP Port. and Proj. Management for SAP S/4HANA ... 639
34.25
S4TWL - Changes compared to older releases than SAP Port. and Proj. Mngt. 6.1 .............. 640
Page | 12
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
35
36
34.26
S4TWL - S4TWL - Not strategic functionalities within SAP S/4HANA .................................. 642
34.27
S4TWL - Control Plans in SAP Portfolio and Project Management for SAP S/4HANA......... 643
34.28
S4TWL - HTTP-Based Document Management in SAP Portfolio and Project Management f 644
34.29
S4TWL - Object Links to SAP Environmental Compliance in SAP Portfolio and Projec ....... 646
34.30
S4TWL - Microsoft Project Import/Export in SAP Portfolio and Project Management ......... 646
Procurement .............................................................................................................................. 648
35.1
S4TWL - MM-PUR WebDynpro Applications...................................................................... 648
35.2
S4TWL - Classic MM-PUR GUI Transactions replacement ................................................. 649
35.3
S4TWL - Dedicated SAP Supplier Lifecycle Management (SAP SLC) business processes ..... 651
35.4
S4TWL - Supplier Distribution via MDG-S ......................................................................... 653
35.5
S4TWL - Authority Concept for Supplier Invoice ................................................................. 654
35.6
S4TWL - Foreign Trade within SAP S/4HANA Procurement ............................................... 655
35.7
S4TWL - RFQ Simplified Transaction ................................................................................. 666
35.8
S4TWL - Webdynpro Applications for Purchase Requisition Transfer from ERP to SRM ..... 667
35.9
S4TWL - Co-Deployment of SAP SRM ................................................................................ 668
35.10
S4TWL - Supplier Invoice New Archiving ........................................................................... 669
35.11
S4TWL - Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC) ...................... 670
35.12
S4TWL - Vendor evaluation based on LIS ........................................................................... 671
35.13
S4TWL - ERP Shopping Cart .............................................................................................. 672
35.14
S4TWL - Internet Application Components (IAC) ................................................................ 675
35.15
S4TWL - MDM Catalog...................................................................................................... 676
35.16
S4TWL - Pricing Data Model Simplification ....................................................................... 677
35.17
S4TWL - Output Management Adoption in Purchase Order................................................. 677
Sales & Distribution .................................................................................................................. 680
36.1
S4TWL - Business Role Internal Sales Representative ......................................................... 680
36.2
S4TWL - Webshops by Internet Sales or Web Channel Experience Management .................. 681
36.3
S4TWL - Sales Activities ..................................................................................................... 683
36.4
S4TWL - Billing Document Output Management ................................................................. 686
36.5
S4TWL - SD Rebate Processing replaced by Settlement Management .................................. 688
36.6
S4TWL -Miscellaneous minor functionalities in SD Area..................................................... 690
36.7
S4TWL - SD Complaint Handling ....................................................................................... 691
36.8
S4TWL - SD Simplified Data Models .................................................................................. 692
36.9
S4TWL - VBFA - Indirect Docflow Relationships ................................................................ 694
36.10
S4TWL - Data Model Changes in SD Pricing ...................................................................... 697
Page | 13
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
37
38
39
36.11
S4TWL - Foreign Trade ...................................................................................................... 701
36.12
S4TWL - Credit Management.............................................................................................. 712
36.13
S4TWL - ERP SD Revenue Recognition .............................................................................. 717
36.14
S4TWL - Optimization of SD Rebate Processing for TPM Customers .................................. 718
36.15
S4TWL - Simplification in SD Analytics .............................................................................. 720
36.16
S4TWL - Advanced Order Processing and Billing for Contractors to the public sect ............ 722
36.17
S4TWL - Operational Data Provisioning ............................................................................ 723
Transportation Manangement .................................................................................................. 725
37.1
S4TWL - Simplified customizing of Transportation Manangement (TM) integration............. 725
37.2
S4TWL - Forwarding Settlement Document Transfer in TM ................................................ 727
Globalization Financials ............................................................................................................ 732
38.1
S4TWL - Globalization – Financials ................................................................................... 732
38.2
S4TWL - Annexing Solution for Israel ................................................................................. 732
38.3
S4TWL - Funds Management Portugal ............................................................................... 734
Globalization Logistics .............................................................................................................. 736
39.1
40
41
42
43
S4TWL - Globalization – Logistics...................................................................................... 736
Industry – Cross ........................................................................................................................ 738
40.1
S4TWL - BRIM - Billing of Event Detail Records (EDR) ..................................................... 738
40.2
S4TWL - BRIM - Common Object Layer (COL) .................................................................. 738
40.3
S4TWL - BRIM - Integration with FSCM Biller Direct (FI-CA) ........................................... 740
40.4
S4TWL - BRIM - Solution Sales and Billing ........................................................................ 740
40.5
S4TWL - BRIM – Immediate Master Data Replication to SAP Convergent Charging ........... 742
Industry Banking....................................................................................................................... 746
41.1
S4TWL - SEM Banking ....................................................................................................... 746
41.2
S4TWL - CML-specific functions with regard to collaterals and collateral objects ............... 748
Industry Beverage ..................................................................................................................... 751
42.1
S4TWL - IS-Beverage (Excise Duty).................................................................................... 751
42.2
S4TWL - IS-Beverage (Sales Returns) ................................................................................. 751
42.3
S4TWL - IS-Beverage (Empties Management) ..................................................................... 752
42.4
S4TWL - IS-Beverage (Pendulum List) ................................................................................ 753
Defense&Security ...................................................................................................................... 755
43.1
S4TWL - DFPS eSOA services ............................................................................................ 755
Page | 14
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
44
45
46
43.2
S4TWL - BI content, Datasources and extractors for DFPS ................................................. 756
43.3
S4TWL - Integration of DFPS with Investigative Case Management (ICM) ......................... 757
43.4
S4TWL - Integration of DFPS with Environmental Compliance ........................................... 759
Industry DIMP - Aerospace & Defense..................................................................................... 761
44.1
S4TWL - Collective Processing Pegging ............................................................................. 761
44.2
S4TWL - Actual labor and costing ...................................................................................... 762
44.3
S4TWL - Cost Distribution Processing ................................................................................ 763
44.4
S4TWL - Manufacturer Part Number .................................................................................. 763
44.5
S4TWL - Flight Scheduling ................................................................................................. 769
44.6
S4TWL - Enhancements Actual Labour Costing / Time Recording ....................................... 770
44.7
S4TWL - Enhancements Subcontracting Special Stock Types Not Available ......................... 771
44.8
S4TWL - AECMA SPEC 2000M Military Version................................................................ 772
44.9
S4TWL - Obsolete transactions and Enhancements in GPD................................................. 772
Industry DIMP – Automotive ................................................................................................... 776
45.1
S4TWL - Vehicle search using SAP TREX as external search engine ................................... 776
45.2
S4TWL - Handling Unit Management - Obsolete Transactions ............................................ 777
45.3
S4TWL - Tracking Inbound................................................................................................. 781
45.4
S4TWL - Supplier Workplace .............................................................................................. 783
45.5
S4TWL - External Service Providers ................................................................................... 785
45.6
S4TWL - Cross-System Transit between Two Plants ............................................................ 787
45.7
S4TWL - Long Material Number ......................................................................................... 789
45.8
S4TWL - Material Version .................................................................................................. 791
45.9
S4TWL - Planning Regular Route Shipments....................................................................... 794
45.10
S4TWL - BSP based Dealer Portal...................................................................................... 796
45.11
S4TWL - Web Dynpro based Dealer Portal ......................................................................... 798
Industry DIMP - EC&O ............................................................................................................ 800
46.1
S4TWL - Obsolete BAPIS of Bill of Services (BOS) ............................................................. 800
46.2
S4TWL - BOS Cost Transfer to PS removed ........................................................................ 801
46.3
S4TWL - Business Partner Tax Classification BUT_FRG0011 is deactivatedS4TWL - ZDEP
ETM CATS package ......................................................................................................................... 802
46.4
S4TWL - ETM General ....................................................................................................... 804
46.5
S4TWL - ETM Tables obsolete ............................................................................................ 805
46.6
S4TWL - REAL ESTATE SALES (HOMEBUILDING) ......................................................... 806
46.7
S4TWL Business Package for Subcontracting (EC&O) ....................................................... 807
Page | 15
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
47
48
Industry DIMP - High Tech ...................................................................................................... 809
47.1
S4TWL - Manufacturing Execution Systems ........................................................................ 809
47.2
S4TWL - RosettaNet ........................................................................................................... 810
47.3
S4TWL - Software License Management ............................................................................. 810
47.4
S4TWL - Contract Management Enhancements ................................................................... 811
47.5
S4TWL - Billing Process Enhancements .............................................................................. 812
47.6
S4TWL - Software Maintenance Processing ........................................................................ 813
47.7
S4TWL - User Exits in DRM ............................................................................................... 814
47.8
S4TWL - Condition Technique in DRM: Rule Configuration ............................................... 815
47.9
S4TWL - Manufacturer/Supplier Processes ......................................................................... 816
47.10
S4TWL - Distributor/Reseller Processes ............................................................................. 818
Industry DIMP - High Tec ........................................................................................................ 820
48.1
49
50
51
S4TWL - Installed Base Management.................................................................................. 820
Industry Media .......................................................................................................................... 821
49.1
S4TWL - SAP Media availability in SAP S/4HANA.............................................................. 821
49.2
S4TWL - Media Product Master ......................................................................................... 822
Industry DIMP – Mill ................................................................................................................ 824
50.1
S4TWL - Non ferrous metal processing ............................................................................... 824
50.2
S4TWL - Sales Order Versions............................................................................................ 826
50.3
S4TWL - Stock Overview and Object Search by Characteristics .......................................... 826
50.4
S4TWL - Mill specific enhancements to scheduling PRTs .................................................... 828
50.5
S4TWL - Process batch....................................................................................................... 830
50.6
S4TWL - Fast entry of characteristic values in trading contract .......................................... 831
50.7
S4TWL - Selection by characteristics in mass processing of orders ...................................... 832
50.8
S4TWL - Fast entry of characteristic values in sales document ............................................ 833
Industry Oil ............................................................................................................................... 835
51.1
S4TWL- ACM - Simplification for Contract Approval .......................................................... 835
51.2
S4TWL- ACM: Simplification for Pre-payment and External Interfacing ............................. 836
51.3
S4TWL - ACM: Simplification of Cross Topics .................................................................... 836
51.4
S4TWL - Handling Oil & Gas obsolete t-codes Oil .............................................................. 837
51.5
S4TWL - Optimization in Oil & Gas - TD module for STO and sales order with POD b ....... 839
51.6
S4TWL - Extended IS-OIL Data Aging for SD/MM Objects ................................................. 841
51.7
S4TWL - Data Model in Oil & Gas Inventory management ................................................. 843
Page | 16
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
52
53
54
51.8
S4TWL - Data Aging for IS-OIL Objects ............................................................................. 850
51.9
S4TWL - Improved update logic for excise duty related movements in MBEW ..................... 854
51.10
S4TWL - UoM Group Extension Improvements ................................................................... 856
51.11
S4TWL - Extended IS-OIL Customizing............................................................................... 857
51.12
S4TWL - IS-OIL - Commodity Management Integration ...................................................... 858
51.13
S4TWL - IS-OIL Data Archiving For Exchanges ................................................................. 859
51.14
S4TWL – iTSW available only for ACM customers .............................................................. 860
51.15
S4TWL - Optimization in Oil&Gas - Inter company sales - Cross border excise duty ........... 861
51.16
S4TWL - IS-OIL Proper sign operation for ACDOCA ......................................................... 862
51.17
S4TWL - Unit of Measure (UoM) Group enahncement ........................................................ 864
51.18
S4TWL - eNetting Deprecation ........................................................................................... 867
51.19
S4TWL - Dynamic Scheduling deprecation ......................................................................... 868
51.20
S4TWL - Financial Based netting deprecation..................................................................... 869
51.21
S4TWL - Oil & Gas inconsistency reports deprecation ........................................................ 870
Industry Oil – OGSD................................................................................................................. 874
52.1
S4TWL - OGSD - Classic Data Collation ............................................................................ 874
52.2
S4TWL - OGSD - Classic OGSD Interfaces ........................................................................ 875
52.3
S4TWL - OGSD - Sales Logistics Cockpit ........................................................................... 877
52.4
S4TWL - OGSD - Liquid Petrol Gas ................................................................................... 879
52.5
S4TWL - OGSD - Infosheet ................................................................................................. 881
52.6
S4TWL - OGSD - Collective Orders.................................................................................... 883
52.7
S4TWL - OGSD - Best Buy ................................................................................................. 884
52.8
S4TWL - OGSD - Formroutines Telesales ........................................................................... 885
52.9
S4TWL - OGSD - Intercompany Processes.......................................................................... 887
52.10
S4TWL - OGSD - Classic Method Framework .................................................................... 889
52.11
S4TWL - OGSD - Old Notes ............................................................................................... 890
Industry Oil – OTAS ................................................................................................................. 893
53.1
S4TWL - OTAS - Integrated Dispatch Managment .............................................................. 893
53.2
S4TWL - OTAS - Integrated Petroleum Report .................................................................... 894
53.3
S4TWL - OTAS - Sales Activities......................................................................................... 896
Industry Public Sector ............................................................................................................... 898
54.1
S4TWL - Functionality German Local Authorities ............................................................... 898
54.2
S4TWL - Authorization in Funds Management .................................................................... 899
54.3
S4TWL - Former Budgeting System (FBS) in Funds Management ....................................... 900
Page | 17
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55
54.4
S4TWL - Functionality for FACTS I and FACTS II (Federal Agencies Centralized Tri ......... 902
54.5
S4TWL - Expenditure Certification ..................................................................................... 904
54.6
S4TWL - Specific fields on Business Partner ....................................................................... 906
54.7
S4TWL - Fund Accounting based on Special Ledger ........................................................... 908
54.8
S4TWL - Data Structure changes in BCS ............................................................................ 910
54.9
S4TWL - Funds Management Dimensions as part of the Universal Journal ......................... 911
54.10
S4TWL - Functionality for BCS Multi-level Budget Structure .............................................. 913
54.11
S4TWL - Functionality Average Daily Balance-based Distribution...................................... 915
Industry Retail & Fashion ......................................................................................................... 918
55.1
S4TWL - Retail Power Lists ................................................................................................ 918
55.2
S4TWL - Retail Closed BW Scenarios ................................................................................. 918
55.3
S4TWL - Retail Markdown Plan ......................................................................................... 919
55.4
S4TWL - Retail Bonus Buy.................................................................................................. 920
55.5
S4TWL - Retail Sales Forecasting ....................................................................................... 921
55.6
S4TWL - Retail Order Optimizing: Load Build, Investment Buy ........................................... 922
55.7
S4TWL - Retail Rapid Replenishment.................................................................................. 923
55.8
S4TWL - Automatic Document Adjustment .......................................................................... 924
55.9
S4TWL - Retail Additionals................................................................................................. 926
55.10
S4TWL - Article Discontinuation ........................................................................................ 927
55.11
S4TWL - GDS simplified Inbound Price Catalog Interface .................................................. 928
55.12
S4TWL - Business Partner in Site Master ............................................................................ 929
55.13
S4TWL - Logistical Variant ................................................................................................ 930
55.14
S4TWL - Article Hierarchy ................................................................................................. 931
55.15
S4TWL - Market Basket Calculation ................................................................................... 932
55.16
S4TWL - Merchandise and Assortment Planning (ERP based)............................................. 933
55.17
S4TWL - Retail Method of Accounting ................................................................................ 934
55.18
S4TWL - Perishables Procurement ..................................................................................... 935
55.19
S4TWL - Fresh Item Procurement ....................................................................................... 936
55.20
S4TWL - Retail Ledger / Profit Center Analytics ................................................................. 937
55.21
S4TWL - Goods Receipt Capacity Check ............................................................................. 938
55.22
S4TWL - Online Store ......................................................................................................... 939
55.23
S4TWL - Generic Article Harmonization............................................................................. 940
55.24
S4TWL - Retail Labeling..................................................................................................... 941
55.25
S4TWL - Seasonal Procurement.......................................................................................... 942
Page | 18
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
56
55.26
S4TWL - Replenishment...................................................................................................... 943
55.27
S4TWL - Retail Information System .................................................................................... 945
55.28
S4TWL - SAP Retail Store................................................................................................... 946
55.29
S4TWL - Retail iViews ........................................................................................................ 947
55.30
S4TWL - Prepack Allocation Planning ................................................................................ 948
55.31
S4TWL - Assortment List .................................................................................................... 948
55.32
S4TWL - In-store food production integration ..................................................................... 949
55.33
S4TWL - PRICAT Outbound ............................................................................................... 950
55.34
S4TWL - Retail Business Function Harmonization .............................................................. 951
55.35
S4TWL - Retail Obsolete Transactions ................................................................................ 952
55.36
S4TWL - Value and Quota Scales ....................................................................................... 958
55.37
S4TWL - AIN ...................................................................................................................... 959
55.38
S4TWL - SAP Smart Business for Retail Promotion Execution ............................................. 960
55.39
S4TWL - Retail Factsheets .................................................................................................. 960
55.40
S4TWL - Retail Short Text Replacement .............................................................................. 961
55.41
S4TWL - Subsequent Settlement - Vendor Rebate Arrangements .......................................... 962
55.42
S4TWL - Segmentation (from 1809 onwards) ...................................................................... 964
55.43
S4TWL - Allocation Run Master Data ................................................................................. 965
55.44
S4TWL - Fashion Contract Disablement ............................................................................. 967
55.45
S4TWL - Allocation Run ..................................................................................................... 968
55.46
S4TWL - Segment Field Length Extension ........................................................................... 970
55.47
S4TWL - Fashion Functionality .......................................................................................... 971
55.48
S4TWL - Season Active in Inventory Management ............................................................... 974
55.49
S4TWL - Fashion changes in 1709 FPS02........................................................................... 974
55.50
S4TWL - Retail Revenue Management Integration .............................................................. 976
55.51
S4TWL - Segmentation (Upgrade SAP S/4HANA 1709 to 1809) .......................................... 977
55.52
S4TWL - Conversion of Season Master Data to SAP S/4HANA 1809 ................................... 978
55.53
S4TWL - Supply Assignment Preview (upgrade to SAP S/4HANA 1809) .............................. 981
55.54
S4TWL - Retail Store Fiori App .......................................................................................... 982
55.55
S4TWL - SAP AFS Integration ............................................................................................ 983
55.56
S4TWL - POS Outbound via Idoc WP_PLU ........................................................................ 984
55.57
S4TWL - Valuation in Retail ............................................................................................... 984
55.58
S4TWL - Retail Demand Management Integration .............................................................. 986
Industry Telecommunications ................................................................................................... 987
Page | 19
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
57
58
56.1
S4TWL - Lock and unlock services using IST_TDATA ......................................................... 987
56.2
S4TWL - PORTAL ROLES FOR NETWORK LIFECYCLE MANAGEMENT (NLM)............. 988
Industry Utilities........................................................................................................................ 989
57.1
S4TWL - CVI Integration for SAP ISU ................................................................................ 989
57.2
S4TWL - Multichannel Foundation for Utilities................................................................... 991
57.3
S4TWL - SAP Waste and Recycling: Activation ................................................................... 992
57.4
S4TWL - IDE Outgoing Payment Processing ...................................................................... 994
57.5
S4TWL - IS-Utilities Settlement Control .............................................................................. 995
57.6
S4TWL - Monitoring Profile Value Import .......................................................................... 995
57.7
S4TWL - Utilities Customer Electronic Services (UCES) ..................................................... 996
57.8
S4TWL - IS-U Stock, Transaction and Master Data Statistics (UIS, BW) ............................. 998
57.9
S4TWL - IS-U Sales Processing ........................................................................................ 1000
57.10
S4TWL - Marketing - IS-U Loyalty Program ..................................................................... 1000
57.11
S4TWL - Front Office (EC20) ........................................................................................... 1001
57.12
S4TWL - GIS Business Connector ..................................................................................... 1001
57.13
S4TWL - Enterprise Services for SAP for Utilities (IS-U) .................................................. 1002
57.14
S4TWL - Central and Eastern European localization for Utility & Telco ........................... 1003
SAP Ariba ................................................................................................................................ 1006
58.1
S4TWL - Ariba Cloud Integration ..................................................................................... 1006
Page | 20
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 21
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
timing of change management as a customer decision. Change management may
therefore take place during the initial conversion or be postponed to a later
point in time.
When compared to the number of SAP Business Suite products that appear in this list, the
total list of simplifications for SAP S/4HANA may appear rather long. However, SAP
does not foresee that any one customer system will be affected by all of them, because
the simplifications cover all capabilities of the system, including industry solutions. This
list should be treated as a complete inventory that needs to be mapped against a
productive environment to determine the impact of converting.
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.
Note: The Simplification List for SAP S/4HANA is edition/release dependent. In
this collection we focus on SAP S/4HANA release 1809 initial shipment stack.
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.
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.
Page | 22
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 23
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 1809 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 system1
•
Any active Business Functions in your system2
•
Industry Solutions3
If there is no valid conversion path for any of the items listed above (for example, an addon is not released for the conversion yet), the Maintenance Planner prevents the
conversion. After the check, the Maintenance Planner generates the download files (addons, 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.
1
For a list of supported add-ons, see SAP Note 2214409
SAP Notes 2240359 for the Always-Off Business Functions and 2240360 for the Always-On Business
Functions
3
See SAP Note 2214213 for supported industry solutions
2
Page | 24
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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). 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 1809 Initial Shipment Stack – this document
This document provides the 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 1809 SP0.
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 the this
software release.
Examples:
Simplification Item
Business Impact Note
Business Partner Approach
2265093
Material Number Field Length Extension
2267140
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-ToGuides. For example, the Simplification Item related to the Business Partner Approach
contains a PDF describing the detailed Business Partner Conversion Activities. Please be
Page | 25
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 new, webbased UI for searching and displaying Simplification Items starting with
SAP S/4HANA Release 1709
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.
Page | 26
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Page | 27
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2 Cross Topics
2.1 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
The parameter is obsolete and shall no longer be set. The new behavior equals parameter
value SIMPLE.
Other Terms
Simplification
2.2 ABAPTWL - Cleanup of orphaned objects
Application Components:
BC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2672757
Simplification of SAP_BASIS
Page | 28
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Symptom
With SAP_BASIS 7.53 (1809) SAP has withdrawn some technical features, which are
not available for S/4HANA on-premise and may be seen as incompatible from an ERP /
ECC perspective.
Reason and Prerequisites
New license.
Solution
Adapt custom code.
Other Terms
Migration ERP to S/4HANA
2.3 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 any of the SAP S/4HANA on premise system variants, starting with
S/4HANA 1511. The SSCR license key procedure is not implemented in S/4HANA.
Depending on your task and question you may proceed as outlined in the solution section
of this SAP Note.
Page | 29
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Q1 – Is it possible to activate SSCR license key?
The SSCR license key functionality is activated and deactivated by the product. The
decision is taken at installation time in profile parameter “system/usage_flavour”. If
customer changes this parameter, severe system inconsistencies occur.
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”.
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.
Other Terms
SAP S/4HANA, SSCR key, Developer key, Access key, object key, modification
Page | 30
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.4 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.
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
Page | 31
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.5 ABAPTWL - VM Container not supported
Application Components:
BC-VMC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2560708
Kernel for S/4 HANA does not support
VMC
Symptom
Starting with SAP Kernel version 7.73 the Virtual Machine Container (VMC)
funtionality is no longer included.
Reason and Prerequisites
S/4 HANA does not support Virtual Machine Container (VMC) functionality.
Kernel 7.73 and following are not compatible with earlier versions of the SAP kernel and
Kernel 7.73 and following must not be used with the classical SAP Suite releases.
Solution
Use VMC on classical SAP Business Suite systems.
Other Terms
VMC
Page | 32
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.6 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
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.7 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 SAP Kernel version 7.73 the Dual Stack System setup is no longer
supported.
Page | 33
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Reason and Prerequisites
S/4 HANA never supported and will never support a dual stack system setup.
Kernel 7.73 and following are not compatible with earlier versions of the SAP kernel and
Kernel 7.73 and following can not be used with the classical SAP Suite releases.
Solution
For the classical SAP Suite with Dual Stack System Setup a SAP Kernel with a version <
773 has to be used.
Other Terms
Dual Stack, AS Java
2.8 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 S/4 HANA 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
Page | 34
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.9 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.
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)
Page | 35
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. 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.
2. 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.
3. 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/ClusterPage | 36
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. Repository tables object list:
DD06L, DD06T, DD16S, DD06V, DD06VV, DD16V
2. 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.
3. 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.
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:
1. 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.
2. 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.
3. 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.
4. 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.
Page | 37
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.10 S4TWL - FIORI APPLICATIONS FOR SUITE ON HANA ONPREMISE
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.
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.
Page | 38
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 39
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.11 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
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
Page | 40
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
2.12 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
Page | 41
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.13 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:
•
•
•
•
•
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
Page | 42
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
2.14 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.
Page | 43
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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)
Maintenance / Service Order Reporting
BSSP_LPD_PM_OM_OPA
(Links)
BSSP_LPD_CO_PC
Product Cost Reporting (Links)
BSSP_LPD_FI_GL_PRCTR
Profit Center Reporting (Links)
BSSP_FI_AA_POSTED_DEPREC
BSSP_CO_OM_CC_ACT_PLAN_AGGR
BSSP_FI_AR_TOTALS
BSSP_FI_AR_DUE_ANALYSIS
BSSP_FI_AR_DUE_FORECAST
BSSP_FI_AR_OVERDUE
BSSP_CO_OM_IO_ACT_PLAN_AGGR
BSSP_CO_PC_MAT_ACT_PLAN_AGGR
BSSP_GR_IR_GOODS_RECEIPT
Asset Accounting: Posted Depreciation
(Reports (Display as Form / List))
Cost Center: Cumulative Actual/Planned
Costs (Reports (Display as Form / List))
Cost Center Balance: Totals (Reports
(Display as Form / List))
Customer Due Date Analysis (Reports
(Display as Form / List))
Customer Due Date Forecast (Reports
(Display as Form / List))
Customer Overdue Analysis (Reports
(Display as Form / List))
Internal Order: Cumulative
Actual/Planned Costs (Reports (Display
as Form / List))
Material: Aggregated Actual / Planned
Costs (Reports (Display as Form / List))
Purchase Order History: Goods Receipt
(Reports (Display as Form / List))
Page | 44
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
BSSP_GR_IR_INVOICE_RECEIPT
BSSP_GR_IR_OPEN_ITEM
BSSP_FI_AP_TOTALS
BSSP_FI_AP_DUE_ANALYSIS
BSSP_FI_AP_DUE_FORECAST
BSSP_FI_AP_OVERDUE
Purchase Order History: Invoice
Receipt(Reports (Display as Form / List))
Purchase Order: Open Items (Reports
(Display as Form / List))
Vendor Balance Totals (Reports (Display
as Form / List))
Vendor Due Date Analysis (Reports
(Display as Form / List))
Vendor Due Date Forecast (Reports
(Display as Form / List))
Vendor Overdue Analysis (Reports
(Display as Form / List))
Asset Accounting: Posted Depreciation
(Reports (Display as Chart))
Cost Center: Breakdown Actual/Planned
BSSP_CO_OM_CC_PERIOD_BD_C
Costs by Period (Reports (Display as
Chart))
Cost Center: Cumulative Actual/Planned
BSSP_CO_OM_CC_ACT_PLAN_AGGR_C
Costs (Reports (Display as Chart))
Customer Balance: Period Drilldown
BSSP_FI_AR_PERIOD_C
(Reports (Display as Chart))
Customer Balance: Totals (Reports
BSSP_FI_AR_TOTALS_C
(Display as Chart))
Customer Due Date Analysis (Reports
BSSP_FI_AR_DUE_ANALYSIS_C
(Display as Chart))
Customer Due Date Forecast (Reports
BSSP_FI_AR_DUE_FORECAST_C
(Display as Chart))
Customer Overdue Analysis (Reports
BSSP_FI_AR_OVERDUE_C
(Display as Chart))
G/L Account Balance (Reports (Display
BSSP_FI_GL_ACC_BALANCE_C
as Chart))
Internal Order: Actual/Planned Costs by
BSSP_CO_OM_IO_PERIOD_BD_C
Period (Reports (Display as Chart))
Internal Order: Cumulative
BSSP_CO_OM_IO_ACT_PLAN_AGGR_C Actual/Planned Costs (Reports (Display
as Chart))
Material: Aggregated Actual / Planned
BSSP_CO_PC_MAT_ACT_PLAN_AGGR_C
Costs (Reports (Display as Chart))
Material: Breakdown Actual/Planned
Costs by Period (Reports (Display as
BSSP_CO_PC_MAT_PERIOD_BD_C
Chart))
BSSP_FI_AA_POSTED_DEPREC_C
Page | 45
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
BSSP_FI_AP_PERIOD_C
BSSP_FI_AP_TOTALS_C
BSSP_FI_AP_DUE_ANALYSIS_C
BSSP_FI_AP_DUE_FORECAST_C
BSSP_FI_AP_OVERDUE_C
Vendor Balance: Period Drilldown
(Reports (Display as Chart))
Vendor Balance Totals (Reports (Display
as Chart))
Vendor Due Date Analysis (Reports
(Display as Chart))
Vendor Due Date Forecast (Reports
(Display as Chart))
Vendor Overdue Analysis (Reports
(Display as Chart))
Asset Accounting: Posted Depreciation
(Reports (Display as HTML5 Chart))
Cost Center: Breakdown Actual/Planned
BSSP_CO_OM_CC_PERIOD_BD_C2
Costs by Period (Reports (Display as
HTML5 Chart))
Cost Center: Cumulative Actual/Planned
BSSP_CO_OM_CC_ACT_PLAN_AGGR_C2 Costs (Reports (Display as HTML5
Chart))
Customer Balance: Period Drilldown
BSSP_FI_AR_PERIOD_C2
(Reports (Display as HTML5 Chart))
Customer Balance: Totals (Reports
BSSP_FI_AR_TOTALS_C2
(Display as HTML5 Chart))
Customer Due Date Analysis (Reports
BSSP_FI_AR_DUE_ANALYSIS_C2
(Display as HTML5 Chart))
Customer Due Date Forecast (Reports
BSSP_FI_AR_DUE_FORECAST_C2
(Display as HTML5 Chart))
Customer Overdue Analysis (Reports
BSSP_FI_AR_OVERDUE_C2
(Display as HTML5 Chart))
G/L Account Balance (Reports (Display
BSSP_FI_GL_ACC_BALANCE_C2
as HTML5 Chart))
Internal Order: Actual/Planned Costs by
Period (Reports (Display as HTML5
BSSP_CO_OM_IO_PERIOD_BD_C2
Chart))
Internal Order: Cumulative
BSSP_CO_OM_IO_ACT_PLAN_AGGR_C2 Actual/Planned Costs (Reports (Display
as HTML5 Chart))
Material: Aggregated Actual / Planned
BSSP_CO_PC_MAT_ACT_PLANAGGR_C2 Costs (Reports (Display as HTML5
Chart))
Material: Breakdown Actual/Planned
Costs by Period (Reports (Display as
BSSP_CO_PC_MAT_PERIOD_BD_C2
HTML5 Chart))
BSSP_FI_AA_POSTED_DEPREC_C2
Page | 46
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
BSSP_FI_AP_PERIOD_C2
BSSP_FI_AP_TOTALS_C2
BSSP_FI_AP_DUE_ANALYSIS_C2
BSSP_FI_AP_DUE_FORECAST_C2
BSSP_FI_AP_OVERDUE_C2
Vendor Balance: Period Drilldown
(Reports (Display as HTML5 Chart))
Vendor Balance Totals (Reports (Display
as HTML5 Chart))
Vendor Due Date Analysis (Reports
(Display as HTML5 Chart))
Vendor Due Date Forecast (Reports
(Display as HTML5 Chart))
Vendor Overdue Analysis (Reports
(Display as HTML5 Chart))
Other Terms
CHIPs, Side Panel for Business Suite, S/4HANA (on-premise), Conversion
2.15 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
any remote SAP application and hence used internally for cross application
communication.
Page | 47
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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 1809 | ABLMUCON1809
S/4HANA OP 1809 | 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
Page | 48
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
of the blacklist. For example, on an S/4HANA OP 1809 instance, provide the package
name is ABLMUCON1809 & the names of blacklisted remote enabled Function
Modules would appear in the result .
S/4HANA 1610 OP: Please check the attached PDF document for the names of the
blacklisted RFC Enabled Function Modules.
For S/4HANA 1709 & higher releases: view the contents of the blacklist directly on the
S/4HANA instance by following the instructions mentioned in the section "View the
contents of RFC Blacklist" given above.
Solution
In case any RFC enabled Function Module's external access needs to be un-blocked,
please follow the instructions mentioned in the note #2408693.
Other Terms
RFC UCON, RFC Unified Connectivity, Signature Incompatibility
2.16 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.
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
Page | 49
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
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
Page | 50
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
- 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.17 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 as of SAP
S/4HANA 1709 (on premise) however 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
extractors and share new versions of the list via this note. Hence it is recommended to
review this note for updates.
Page | 51
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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!
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)
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
2498786 - Data Sources supported by Central Master Data
in S/4HANA
Master Data
2576363 - Data Sources supported by Master Data
Governance in S/4HANA
Page | 52
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
2552797 List of BI Data Sources used in EWM
Supply Chain – Extended
2382662 List of BI Data Sources from SCM Basis used in
Warehouse Management
EWM Context
Supply Chain –
Transportation
Management
Item Area - Industry
All Data Sources working and whitelisted, no separate note
exists
Note number for
details
DIMP Automotive
2544193 - Restrictions for BW extractors relevant for
S/4HANA in the area of Defense & Security
Defense and 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
Page | 53
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2270505 - S4TWL - IS-U Stock, Transaction and Master
Data Statistics (UIS, BW)
IS Utilities
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
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
Deprecated
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
DS obsolete
DataSource is obsolete - legacy
extractors
Page | 54
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
DS not working - no alternative
exists
DataSource is not working with S/4
but no alternative exists
Generated
DS working - no restrictions
Data Source
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 DS not relevant
for BW
extraction
Datasource is available in
ROOSOURCE, however, not to be
used for extraction by BW.
Other Terms
BW, Extractors, Datasources, SAP S/4HANA
2.18 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
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.
Page | 55
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Follow the steps describe in the manual activity.
Other Terms
Master Check, S/4 System Conversion, Material Master, MRS.
2.19 S4TWL - CDS Views with DCL0
Application Components:
XX-SER-REL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
12
Individual solution without a specific SAP
Note
Long Text
Solution
Dear customer,
We have provided an individual solution to the problem you reported. Due to the
customer-specific nature of the problem and our solution to it, no SAP Note is available
on SAP Service Marketplace to address your inquiry. Therefore, we have completed your
incident and would request that you confirm it.
Sincerely,
Your SAP Product Support
Page | 56
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.20 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
What has changed in Business User Management in SAP S/4HANA and what is the
business value?
SAP S/4HANA is introducing a new identity model for business users. 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.
Following the Principle-of-One in SAP S/4HANA, the business partner is the natural
person who contains and persists the user data for the person, work center, and
communication-related information.
SAP S/4HANA Business User Management enables and supports the entire lifecycle
maintenance of business users with integration to the employee lifecycle in the sense of
organizational changes, leaving, or retirement. A user in SAP S/4HANA is now related
(1:1) to a corresponding business partner (person) from whom essential data is
referenced. This reduces redundant maintenance and prevents the disadvantage you have
with outdated information.
What is the difference between business user and SU01 user?
The business user is also a SU01 user in the system, but also has a 1:1 relation to the
corresponding business partner. The business user concept is used in many new
applications in SAP S/4HANA. SU01 users created without business partners will lead to
limitations because the business user is a prerequisite for many business applications and
Fiori apps.
This business partner contains the personal information. The decoupling of user
authentication and personal information has the advantage that it integrates the entire
lifecycle of that person without redundant maintenance of the user data. Users can still be
managed using transaction SU01 or an Identity Provider System replicated to all systems.
Page | 57
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Information about persons, work centers, and communication is derived from the related
business partner (1:1 relation). In contrast to the Business Suite, this data is no longer
redundantly managed within the User Management Transaction SU01, and so on.
Many applications in the Business Suite use the business partner to define certain roles
for controlling processes and tasks. They also define special business partner attributes to
manage essential data for their business processes. If system access is required, the
business partner needs to be associated with a user. It then becomes a business user. In
the Business Suite, you can use transaction BP (Business Partner Maintenance) to assign
users to business partners. In SAP S/4HANA this is no longer possible, so you avoid an
inconsistent data model for business users.
What is the business impact of that change and what are the benefits?
With Business Partner Integration, the following changes to business user data in SAP
S/4HANA are integrated and can no longer be edited in SU01:
1. Person: The personal data for the business user in SU01 is derived from the
corresponding business partner, integrated with data that comes from the related
employee from the HR system (SAP SuccessFactors or SAP HCM). This data is
mapped from the HR system to the business partner.
2. Work Center: The work center data for the business user in SU01 is derived
from the workplace address of the corresponding business partner. This address
information is integrated with the related employee (for the Function and
Department fields.) This data is replicated from the HR system to the business
partner.
3. Communication: The communication data for the business user in SU01 is
derived from the workplace address of the corresponding business partner. This
communication information is integrated with the related employee information
(for the Phone and E-Mail Address fields). This data is replicated from the HR
system to the business partner.
4. Company: The organization data for ORGANIZATION_NAME and
LOCATION for the business user in SU01 is derived from the company
address of the corresponding business partner. In case of conversion from SAP
ERP to SAP S/4HANA, this data is copied from the formerly assigned company
address of the user via the periodically scheduled sync report
/SHCM/RH_SYNC_BUPA_FROM_EMPL.
The benefit of automated integration is to get rid of the manual process that has the risk
of causing inconsistencies in the system. Therefore, 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'
Page | 58
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
Internet User (BUS000EMPL-INTERNETUSER), for example, shown for role
category BUP005 'Internet User'
The following role categories cannot be assigned to business partners in transaction BP:
•
•
•
Employee (BUP003)
Freelancer (BBP010) → Contingent worker
Service Provider (BBP005) → Contingent worker with additional supplier
relation (staffed from external supplier)
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 (independent from
whether HR 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
Field group 54: Person: Last Name
Field group 61: Address: Address Usage (HCM01, XXDEFAULT); 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.
Relationships of relationship category BUR025 “Service Provider” also cannot be maintained for roles
of role category BBP005 "Service Provider".
Creating Business Users in SAP S/4HANA On-Premise
1. Create a user in SAP S/4HANA using
o Transaction SU01 or
o APIs such as BAPI_USER_CREATE1 or IDENTITY_MODIFY or
o Other channels that use the Identity API (CL_IDENTITY_FACTORY).
2. Create the corresponding business partner for the user. For more information, see
"Creating business partners (persons) related to business users".
3. Assign the created users (from step 1) to business partners (from step 2). Step 2
and step 3 can be performed as single transaction using the UI or the API.
HR Integration is Active: Creating Business Partners (Persons) Related to Business
Users
Page | 59
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Prerequisite: The HR integration switch in SAP S/4HANA is activated with the system
table T77S0 with the configuration switches HRALX/HRAC and HRALX/PBPON. The
HR system is the origin of business users (see HCM simplification SAP Note 2340095).
If there is an active HR integration, the employees and contingent workers are replicated
to SAP S/4HANA (from SAP SuccessFactors Employee Central or SAP HCM onpremise) and the person information is integrated into the corresponding business partner
in SAP S/4HANA.
The synchronization of employee and employment information between HR and SAP
S/4HANA is managed with the periodically scheduled sync report
/SHCM/RH_SYNC_BUPA_FROM_EMPL. This report synchronizes employee and
employment data into the business partner and user management persistency
and provides a consistent data model.
Depending on the purpose of the person, the business partner is created in a role of one of
the following role categories:
•
•
•
Employee (BUP003)
Freelancer (BBP010)
Service Provider (BBP005)
In addition, the supplier information is also created for payment-related processes. These
roles cannot be assigned to existing business partners in transaction BP.
HR Integration is Inactive: Creating Business Partners (Persons) Related to
Business Users
Prerequisite: The HR integration switch in SAP S/4HANA is de-activated via the system
table T77S0 with the configuration switches HRALX/HRAC and HRALX/PBPON.
1. Business users and persons can be created in SAP S/4HANA (as of release 1709
FPS01) using the Fiori app 'Maintain Employees'. With this app you can create
and update business partners and their assignments to users to create and manage
business users. The app provides a mass maintenance via CSV upload.
2. For mass maintenance, you can also use the report
RFS4BPU_EMPLOYEE_UPLOAD with CSV upload for a mass import (SAP
S/4HANA1610) - see SAP Note 2567604.
If HR integration is inactive in SAP S/4HANA, the user data can still be managed with
transaction SU01.
Page | 60
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Updating Business Partners (Persons) Related to Business Users
Integration and administration services enable you to update the business user through
multiple channels.
SAP S/4HANA 1709 FPS1 provides a configuration view that defines the maintenance
source of the workplace address attributes. SAP delivers a default proposal for both
variants, HR Integration active/inactive. See SAP Note 2548303 for details.
This configuration ensures that updates to the workplace address are restricted to one
dedicated update channel. The configured maintenance source of the workplace address
is not applicable in SAP S/4HANA Cloud.
The configuration only applies to updating business users, not to creating them. The
configured update channel determines whether updating the workplace address is
possible using a dedicated channel.
There are three maintenance sources that can be configured as the source for maintaining
the workplace address on various attributes or nodes:
•
•
•
Human Resources (HR)
Business Partner Management (BP)
User Management (US)
The configuration view TBZ_V_EEWA_SRC has the following constraints:
•
•
•
•
If Central User Management (CUA) is active, the configuration of the CUA is
applied and has a higher priority than view TBZ_V_EEWA_SRC.
If Human Resources (HR) is NOT active, HR is not applicable as maintenance
source.
If only the business partner and workplace address of the business user exist and
there's no user, the configuration view is ignored (otherwise it is not possible to
maintain the created workplace data).
Company address part of the workplace address is not part of configuration view
TBZ_V_EEWA_SRC because it is completely under control of User
Management. Company address parts are supported as of S/4HANA 1709 FP02
only. Please check SAP Note 2571544 for more details.
Restrictions:
•
•
Business partners that exist in an ERP system with linkage from BP-CP-US are
not automatically converted to business users.
Business partners that are neither employee nor contingent workforce cannot be
handled as business users. They can only be created as direct users without
corresponding business partners (e.g. in SU01)
Page | 61
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
In transaction BP (Business Partner Maintenance) there is no capability to assign
users to business partners in SAP S/4HANA. This feature has been removed.
How to Determine Relevancy
Simplification item S4TWL - Business User Management is relevant for all SAP
S/4HANA conversion customers.
Reason and Prerequisites
New data model for Business User Management in SAP S/4HANA.
Solution
It is recommended converting all SU01 users (not the technical users) into business
users after SAP S/4HANA conversion. This is possible with S/4HANA 1709 FP02 or
higher.
Creating Business Users in S/4HANA On-Premise
1. Create a user in SAP S/4HANA using
•
•
•
Transaction SU01 or
Using APIs such as BAPI_USER_CREATE1 or IDENTITY_MODIFY or
Other channels that use the Identity API (CL_IDENTITY_FACTORY).
2. Create the corresponding business partner for the user. See "Creating Business
Partners (Persons) Related to Business Users" for more information.
3. Assign the created users (from step 1) to business partners (from step 2). Step 2 and
step 3 can be performed as single transactions via the UI or the API.
For Active HR Integration:
•
•
Manage the integration between employee (and employee-like persons) and the
business user with the periodically scheduled sync report
/SHCM/RH_SYNC_BUPA_FROM_EMPL. You need to ensure that the
employee records contain the corresponding user assignments (infotype 0105 in
HR master data).
In SAP S/4HANA you can use the HCM transactions (PA30 and PA40) for
managing employee master data as part of the Compatibility Package (see SAP
Note 2269324). After the UserID is written to the infotype 0105 of the employee
records, you can assign the corresponding user. The sync report will then ensure
that the business user will be completed.
Page | 62
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
In SAP SuccessFactors with Employee Central you can manage the employee
master data that is integrated with SAP S/4HANA in the cloud with prepackaged
components. The sync report ensures that the business user is completed.
For Inactive HR Integration:
1. Create persons in SAP S/4HANA (with release 1709 FPS01) via the Fiori app
'Maintain Employees' to create and update business partners and their assignments
to users to get real business users.
2. For mass maintenance, you can use the CSV-Upload functionality in Fiori app
'Maintain Employees' (with SAP S/4HANA 1709 FP1 or higher). For SAP
S/4HANA 1610 FP6 we provide for mass import the report
RFS4BPU_EMPLOYEE_UPLOAD. See SAP Note 2567604 for details.
Other Terms
SU01
Business User
/SHCM/RH_SYNC_BUPA_FROM_EMPL
TBZ_V_EEWA_SRC
RFS4BPU_EMPLOYEE_UPLOAD
2.21 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 or SAP S/4HANA Finance to SAP
S/4HANA
Page | 63
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
or a release upgrade SAP S/4HANA to a higher SAP S/4HANA release
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 affect all customers - irrespective of the specific SAP S/4HANA target release.
•
As of now this Simplification Item contains the following generic checks:
o Check for orphaned client dependent data ( as of SAP S/4HANA 1809
)
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 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. Because tools for
checking data consistency and for data migration will only work on
existing clients.
The Simplification Item Checks associated with this Simplification Items
as of SAP S/4HANA 1809 will do a heuristic check, whether there is
any orphaned, client dependent data in your system and raise a
corresponding warning. In this case please cleaup/delete the orphaned
client dependent data.
•
In addition this Simplification Item serves as an anchor for assigning custom code
check related content, which is not related to any specific functional or technical
area (e.g. deletion of unused orphaned objects).
Other Terms
SAP S/4HANA, Generic Checks, Simplification Item
Page | 64
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.22 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
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.
Page | 65
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. Define the active output management framework for the individual business
applications.
1. Open the customizing activity 'Manage Application Object Type Activation'
under SAP Reference IMG -> Cross-Application Components -> Output Control.
2. 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.
3. 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.
4. 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.
2. 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.
3. 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.
Page | 66
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.
You might not be able to use SAP S/4HANA output management if:
•
You are using SAP IS-OIL.
Other Terms
OM, Output Management, Output Control
2.23 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
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
Page | 67
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.24 S4TWL - ENTERPRISE SEARCH
Application Components:
BC-EIM-ESH
Related Notes:
Note Type
Note Number
Note Description
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.
Page | 68
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
2.25 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
Page | 69
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 70
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2.26 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.
For a broader functional intrgration solution you can use the SAP Ariba Cloud Intgration
Gateway, you will find more information via help.sap.com:
SAP Ariba Cloud Integration Gateway
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
Processing of scheduling agreement releases
Consignment process
Page | 71
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
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, ...)
The following cXML message types are not available:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ReceiptRequest
CopyRequest.InvoiceDetailRequest
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 and on-premise edition
1709 listed below.
The following processes are not supported:
•
•
•
•
•
•
•
•
•
Processing of FI - CC invoices (transfered from SAP S/4HANA to Ariba
Network)
Processing of scheduling agreement releases
Consignment process
Subcontracting process
Processing of forecast data
Multi-tier purchase order processing
Purchase order return items processing
Integration processes for suppliers
Quality Management Process (e.g. Quality Notificiaton, Quality Inspection, ...)
The following cXML message types are not available:
Page | 72
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
ProductActivityMessage
ComponentConsumptionRequest
ProductReplenishmentMessage
QualityNotificationRequest
QualityInspectionRequest
QualityInspectionResultRequest
QualityInspectionDecisionRequest
ApprovalRequest.ConfirmationRequest
OrderStatusRequest
Required and Recommended Action
•
•
•
•
•
Implement the master conversion pre-check SAP Note "2182725 - S4TC Delivery
of the SAP S/4HANA System Conversion Checks" and follow the instructions in
this note.
For Ariba Network Integration, also implement the pre-check SAP Note
"2237932 - S4TC Ariba BS Add-On Master Check for SAP S/4HANA System
Conversion Checks". This note is also listed within the master note.
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.
o Before the
conversion: S4H_CONV_INTEGRATION_ARIBA_NETWORK_PREP
C.PDF
o After the conversion:
S4H_CONV_INTEGRATION_ARIBA_NETWORK_POSTC.PDF
2.27 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)
Page | 73
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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:
Page | 74
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
- If table IBIB shows any entries in field KBID, configurations created with IPC have
been stored. This is an indicator at least for usage in the past.
- Table TCUUISCEN contains mandatory information for the configuration UI. If this
table contains records, at least the installation has been set up. It is quite likely that IPC is
actively used.
- Table CUCFGSW contains the "IPC Switch". If this table contains records, master data
has been set up to use IPC instead of VC. This is not only an indicator for IPC usage,
moreover entries must be reverted prior to conversion to S/4HANA.
Related SAP Notes
Custom Code related information
SAP Note: 2238670
2.28 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
Page | 75
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Scheduling (and monitoring) "Standard Jobs" (e.g. SAP_REORG_SPOOL,
SAP_REORG_ABAPDUMPS, SAP_REORG_JOBS etc.) was a manual action in SAP
ERP. Choosing Standard Jobs in transaction SM36 displayed a table of standard job
templates which the customer could choose to schedule.
In SAP S/4HANA, this manual action has been replaced by an automatic mechanism, the
Technical Job Repository. SAP S/4HANA Technical Job Repository takes care of
scheduling (and de-scheduling) necessary standard jobs (as defined and delivered by
SAP) automatically, without any user intervention.
Nevertheless, in case of conflicts, it is possible to do customizations to job definitions, for
example modify the execution period (or start time) of a job or disable automatic job
scheduling of a job entirely 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.
Page | 76
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.29 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
Page | 77
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Symptom
The LSMW (Legacy System Migration Workbench) tool (transaction code LSMW) is
still available within SAP S/4HANA on-premise but not considered as the migration tool.
LSMW might propose incorrect migration interfaces that cannot be used in SAP
S/4HANA anymore.
This SAP Note is valid only for customers implementing SAP S/4HANA 1511 (on
premise) or higher (for example, SAP S/4HANA 1610).
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 migrations. It uses standard interfaces
like BAPIs, IDocs, Direct Input and Batch Input programs and recordings. Due to this
nature, the use of LSMW is restricted for migrations to SAP S/4HANA.
For restrictions on certain Batch Input or Direct Input programs that are used by LSMW,
please get in touch with the application components directly.
Solution
The Legacy System Migration Workbench (LSMW) should only be considered as a
migration tool for SAP S/4HANA for objects that do not have interfaces or content
available after carefully testing for each and every object. The use of LSMW for data
load to SAP S/4HANA is not recommended and at the customer's own risk.
When using LSMW, you have to carefully test the process 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 Rapid Data Migration with SAP Data Services
Instead, SAP S/4HANA data migration content called SAP Rapid Data Migration
based on SAP Data Services software is offered to migrate data into SAP S/4HANA (on
premise). You can find more information under the link below:
http://service.sap.com/public/rds-dm2s4op
Page | 78
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
This content has been specifically built for the new SAP S/4HANA target system, its
interfaces and data structures. The content is free of charge and can be downloaded under
the link above. There are two ways to leverage the content:
1. Base: Data Integrator
SAP S/4HANA customers have access to a basic Data Integrator license key that
comes with the underlying SAP HANA license (HANA REAB or HANA
Enterprise). This key code applied to SAP Data Services provides full ETL
functionalities (Extract, Transform, Load). Thus, it replaces a mapping and load
tool like LSMW with the Rapid Data Migration content. With this basic data load
functionality of SAP Data Services and together with the Rapid Data Migration
content, legacy data can be loaded into SAP S/4HANA (on premise) including
data validation but without further Data Quality (de-duplication, data cleansing)
and reporting capabilities. For this use case with the aforementioned functionality,
SAP Data Services is free of charge and there is no additional cost.
2. Full: Data Services
Using the full SAP Data Services license (separately licensed and not part of SAP
S/4HANA) unleashes all Data Quality features like data cleansing and deduplication for mitigating risk during the data migration process of a new SAP
S/4HANA implementation.
Option 2: SAP S/4HANA Migration Cockpit and Migration Object Modeler
In addition, there is the SAP S/4HANA Migration Cockpit which is part of SAP
S/4HANA and SAP S/4HANA Cloud and included in these licenses. For on premise, it
helps you to transfer your master and transactional data from SAP systems and non-SAP
systems to SAP S/4HANA 1610 and 1709.
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.
There are two options for transferring data to SAP S/4HANA:
1. Transfer Data Using Files
For each migration object, the cockpit provides Microsoft Excel XML files that contain
the necessary fields for the SAP S/4HANA target structure. You download the file for the
migration object, fill it with the source data, upload it to the cockpit and then migrate the
data to the SAP S/4HANA target system.
2. Transfer Data Using Staging Tables
Page | 79
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
As of Release SAP S/4HANA 1709, FPS01, the migration cockpit contains the data
transfer option using staging tables. This solution allows you to handle large data
volumes more easily. You can fill the staging tables either manually or by using your
preferred tools (SAP or third- party tools). The migration cockpit reads the data from the
staging tables and migrates them into the SAP S/4HANA target system.
Direct data extraction from SAP source systems is planned for future Releases.
In addition, the cockpit allows you to integrate your custom data objects into the
migration using the inherent Migration Object Modeler. 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, 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.
You can use the cockpit by calling transaction LTMC which gives you direct access to it.
The role required for the usage of the cockpit is called SAP_CA_DMC_MC_USER. To
access the migration object modeler you use transaction LTMOM. A prerequisite for
using the modeler is that you have created a migration project in the migration cockpit
and that the role SAP_CA_DMC_MC_DEVELOPER is assigned to the respective user.
For a list of available migration objects that are supported with SAP S/4HANA and
further information about the migration cockpit, see the SAP Help Portal under
https://help.sap.com/viewer/29193bf0ebdd4583930b2176cb993268/1709%20000/en-US.
Additional information is also available in the following blog:
https://blogs.sap.com/2017/07/05/starter-blog-for-sap-s4hana-migration-cockpit/
The migration cockpit can be an alternative for smaller and medium-sized projects and
could also be used in addition to the Rapid Data Migration content. For more
information, please click the link below:
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/BH5)
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
Other Terms
LSMW, Rapid Data Migration, RDS, Best Practices, SAP S/4HANA 1511, SAP
S/4HANA 1610, SAP S/4HANA Migration Cockpit, SAP Data Services
Page | 80
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 edition 1511.
Business Process related information
MDM3.0 was discontinued, all known customer implementations have migrated to
Netweaver MDM or Master Data Governance. All known customer implementations
have already replaced the MDM specific IDoc processing according to SAP note
1529387 "Tables MDMFDBEVENT, MDMFDBID, MDMFDBPR growing
significantly"
Required and Recommended Action(s)
None
Related SAP Notes
General SAP Note related to Simplification SAP Note: 1529387
Item
Page | 81
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
COMC_PR_ALTID
COMC_PR_ALTID_BSP
COMC_PR_OBJ_FAM
COMC_PR_OBJ_FAM1
COMC_PR_RFCDEST
COMC_PRODUCT_IDX
COMC_SERVICEID_ALL
Page | 82
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
COMCMATERIALID
COMCPRAUTHGROUP
COMCPRD_BSP_ID
COMCPRFORMAT
COMCPRLOGSYS
COMCPRMSG
COMCPRTYPENRO
COMCSERVICEID
COMM_DEL_PRWB_USER
COMM_EXTRSET
COMM_HIERARCHY
COMM_IOBJ_RECATEG
COMM_MSG01
COMM_PRAPPLCAT
COMM_PRDARC
COMM_PROD_RECATEG
COMMPR_PCUI
COMMPR01
COMMPR02
CRM_PRODUCT_LOG
CRM_PRODUCT_STA
CRMCFSPRODID
Required and Recommended Action(s)
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.
Page | 83
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 84
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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 webchannel 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.
Transaction not available WCU1 Maintain customer
in SAP S/4HANA.
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
Page | 85
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Required and Recommended Action(s)
Switch to strategic solution.
How to Determine Relevancy
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
Page | 86
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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: 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, onpremise 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:
o SAP enhancement package 6 for SAP ERP 6.0
o SAP enhancement package 7 (SP11) for SAP ERP 6.0
o SAP enhancement package 8 (SP01) for SAP ERP 6.0
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.
Page | 87
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 88
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
3. Miscellaneous required actions
Page | 89
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.7 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
SAP HANA-based Analytics for SAP Master Data Governance is not available within
SAP S/4HANA, on-premise edition 1511 and higher.
Page | 90
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.8 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.
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 .***
Page | 91
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
For customers who have enabled time dependency in releases prior to 1610/11:
You need to deactivate time dependency. It is a one-time process.
1. Run the report BUPTDTRANSMIT which will make BUT000 data up to date.
Page | 92
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2. Run the report Z_NTD_BUT000_NEW attached with this Note. To run this:
1. Call up SE38.
2. Enter Z_NTD_BUT00_NEW and choose Create.
3. Choose type as Executable Program.
4. Paste the code content from the attachment.
5. Save, activate, and then execute the report.
3. 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
3.9 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
Page | 93
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 94
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
3.10 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
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
BUHI_ASSIGN_BP_TO_NODE
BAPIs not available in SAP S/4HANA onpremise edition
BUHI_CLEAR_BUFFER
BUHI_DELETE_BP_FROM_NODE
IMG activity node not available in SAP
S/4HANA on-premise edition
Business Partner Group Hierarchy
Page | 95
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.11 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.
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.
Page | 96
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Implement the technical prerequisites for the S/4 transformation checks via this note.
Other Terms
S4TC
MDG_APPL
MDGM
3.12 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
Page | 97
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
3.13 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. This
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 cease to work as classical customer and supplier transactions have
been made obselete.
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)
Page | 98
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
3.14 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.
Page | 99
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Other Terms
Business Partner, RFC CVI_EI_INBOUND_MAIN, Customer Master, Supplier Master
3.15 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, on-premise edition 1511, 1610, or
1709. 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.
Page | 100
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
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.
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, and 1709. 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, onpremise 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)
Transaction not available
in SAP S/4HANA onpremise edition
FD01, FD02, FD03, FD06, FD0
FK01, FK02, FK03, FK06
MAP1, MAP2, MAP3
MK01, MK02, MK03, MK06, MK12, MK18, MK19,
V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21,
Page | 101
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
V+22, V+23
VAP1, VAP2, VAP3
VD01, VD02, VD03, VD06
XD01, XD02, XD03, XD06, XD07
XK01, XK02, XK03, XK06, XK07
Points to Note in SAP S/4HANA:
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
Page | 102
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Partner customizing entries. For this reason, the customer/vendor data has to be
cleaned up before it can be converted into the S/4 Business Partner.
Prepare: Pre-Checks and clean-up customer/vendor data in the ERP System
•
•
•
•
•
Implement SAP S/4HANA Conversion Pre-Checks according to the SAP
S/4HANA Conversion guide chapter Pre-Checks.
Activate Business Function CA_BP_SOA.
In case that the Business Function CA_BP_SOA not yet in the system exist, you
have to create a new Business Function in the customer namespace with the
switches VENDOR_SFWS_SC1 and VENDOR_SFWS_SC2. The new customer
specific Business Function must be of type Enterprise Business Function (G) - see
also Mandatory checks for customer, vendor and contact.
Check CVI customizing and trigger necessary changes e.g. missing BP Role
Category, Define Number Assignments according to the S/4 Conversion guide
chapter Introduce Business Partner Approach (Customer Vendor Integration).
Check and maintain BP customizing e.g. missing tax types.
Check and clean-up customer/vendor data e.g. missing @-sign in the e-mail
address.
Synchronization
•
•
•
Synchronization (Data load) is done via Synchronization Cockpit according to the
attached BP_Conversion Document.pdf > Chapter 4. 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.
Run Business Partner Pre-Check PRECHECK_UPGRADATION_REPORT to
verify the results according to the note 2211312.
Conversion Process
•
Conversion Process must be triggered according to the BP_Conversion
Document.pdf attached to this SAP Note.
Note: If the runtime error "Inconsistency in the dictionary for structure
"ZT005_GEN" occurs during the SUM execution, execute the process again.
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
Page | 103
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
successful S/4 conversion process you have to activate the post processing for
direction Business Partner a Customer /Vendor.
Related SAP Notes & Additional Information
Conversion PreChecks
Other SAP Notes
SAP Help
SAP Notes: 2211312, 2210486, 2216176
SAP Note: 1623677, 954816
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-PartnerApproach_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:
1. 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.
2. 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:
1. DEBMAS: If you want to integrate customer (without BP) data between
two systems, this IDOC can be used.
Page | 104
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2. CREMAS: If you want to integrate supplier (without BP) data between
two systems, this IDOC can be used.
b. SOA Services
1. 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.16 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
Page | 105
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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
Page | 106
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
This simplification list item is releavent if TB300-ADDRSRCH_ACTIVE = ‘X’ which
means the indexing is activated.
Other Terms
'BUTADRSEARCH', 'TB300'
3.17 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
Required and Recommended Action(s)
Customizing the field selection for data screens in SAP namespace is not recommended
anymore.
Page | 107
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
To customize the field selection settings, kindly follow the below process.
1.
2.
3.
4.
5.
6.
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.
o To assign it to a material type, go to transaction OMS2.
Open the required material type, update the Field reference. Click on Save.
o
To assign it to a plant, go to transaction OMSA.
Add an entry by clicking New entries. Click on Save.
3.18 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
Page | 108
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 109
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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,
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.
Page | 110
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
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
Page | 111
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
already existing field keeps its original length and a new field has been added at the end
of the structure (or as new parameter) that allows transmitting material numbers with 40
characters.
Besides this, it must be ensured that no material number (or other extended field) can be
maintained in the system with a content length greater than the old length of the field. To
enforce this and to make the field length extension as far as possible non-disruptive for
the SAP S/4HANA customers, the extended material number functionality must be
switched on explicitly. Only after this decision it is possible to allow more than 18
characters for the material number.
The changes described have been done for BAPIs, IDocs, and released remote-enabled
function modules. This has additionally been implemented where necessary for remote
function calls issued by the SAP S/4HANA system and for unreleased remote-enabled
function modules that are used to communicate with other SAP Business Suite products
like SAP SCM or SAP CRM.
A complete list of relevant function modules, IDocs, and structures that have been
extended in this way can be found in the piece lists in the simplification database.
For released WebServices, 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, onpremise edition 1511, the B2B and A2A communication via BAPIs, IDOCs,
Web-Services, released RFCs (inbound), and remotely called RFCs (outbound)
still work without further changes.
The shorter versions of the extended fields
o are still part of the interfaces.
o are still filled when sending data.
o are still understood when retrieving data.
o If the extended field is used as part of a communicated concatenated field,
this concatenated field is still sent in the original field in the old short
format and is interpreted in the inbound case in the old short format.
Page | 112
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The system prevents that data is created that cannot be sent via the old
interface, that is the usage of the extended fields is restricted to the old
length.
o Communication partners can still rely on the old known behaviour of the
interfaces.
o The long version of the extended field in the interfaces is filled and
interpreted, too. This means that the communication partners can already
adapt their interfaces for using the long field although only short material
numbers are allowed.
For example, the 18 character material number is also communicated via
the 40 character field. This is also true if the extended field is used as part
of a communicated concatenated field: the new extended field will contain
and expect the new long format.
o
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:
o It cannot longer be guaranteed that the old short fields can be filled or
accepted: if the material number or other extended fields are used with
more than the original length, the shorter version of an extended field
cannot longer be filled in the interface and is therefore left empty.
o This is also true for concatenated keys containing extended fields. If the
value that is part of the concatenate is longer than the original field length,
the concatenate can only be sent and evaluated in the new format.
o Before 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.
o Communication partner have to adjust to the new fields and data formats.
Be aware: All SAP Business Suite systems are communication partners!
Internal Calls of External Interfaces
Page | 113
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
As described in the previous chapters, different strategies have been chosen for internal
and for released external APIs.
If a released external API is called internally, that is locally within one system, it is
always ensured that the call can be done with new extended field length, no compatibility
is required. Therefore – and to be safe when extended material number functionality is
activated – all internal calls of external interfaces must only use the newly added
extended fields.
This is also true if structures are used internally that are also used in released external
interfaces and that therefore have been changed in the way described. Then only the new
extended field shall be used in all internal coding, too.
System Settings to Activate the Extended Material Number Functionality
The default setting, both after the move to SAP S/4HANA and for new installations, is
that the extended material number functionality is NOT activated. To use a material
number with 40 characters, the customer needs to activate this functionality. The
following settings are required for that:
1. Activation of the Extended Material Number Functionality
The activation is realized as client-dependent customizing table.
IMG à Cross-Application Components à General Application Functions à Field
length Extension à Activate extended fields
Alternative: Transaction FLETS (For the table maintenance the authorization
group FLE [authorization object S_TABU_DIS] is required).
2. Changing the Material Number Format
Transaction OMSL allows a customer-specific settings regarding the material
number field length. Here the settings need to be adapted to allow a field length of
more than 18 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
Page | 114
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
component of the Add-On DIMP (Discrete Industries & Mill Products). See SAP Note
1597790.
Although the industry solution DIMP is part of SAP S/4HANA, the already existing
DIMP LAMA-functionality for a long material number (LAMA) will not be part of SAP
S/4HANA. In S/4HANA the material number is natively extended to 40 characters.
Special conversion steps are needed to migrate the existing DIMP LAMA solution to the
new S/4HANA extended material number.
For further information on the conversion of the DIMP 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:
o 2214213 for SAP S/4HANA, on-premise edition 1511
o 2333141 for SAP S/4HANA 1610
Collection of restriction related to MFLE: 2233100
•
o
o
o
o
ALE generation for BAPIs: SAP Note 2232497
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
Page | 115
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
o
o
o
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.19 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
S/4HANA system Release 101 or higher contains an additional Customizing table
T130F_C. This allows alternative maintenance of the copy control to the SAP delivery.
The settings in T130F_C are then taken into account during the maintenance of material
master and article master data.
Therefore, all entries from the table T130F that are relevant for the copy control must be
copied to the new table T130F_C, and their field contents must be identical.
If the 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 101. In this case, it is advisable to migrate the entries from T130F to the table
Page | 116
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 100, the system only issues a warning during
the migration phase because the new table does not exist in this release. In this case,
proceed with the migration process.
If you use an SAP ERP for Retail system that requires at least the S/4HANA target
release version 101, 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 101.
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
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.
Page | 117
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Migration report
SAP Note: 2206932
SAP Note: 2323185, 2324325
Other Terms
SAP_APPL_LO_MD_MM_T130F_CHECK S4 T130F field control
3.20 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.
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
Page | 118
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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 SAP Note 2204534
Item
Information about the report
SAP Note 2458666
ZUPDATE_MARC_FOREIGN_TRADE
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 postconversion phase before release of SAP S/4HANA to users.
Note: The skippable error RC7 is only available if your note 2641097 has been
implemented.
3.21 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
Page | 119
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 S/4HANA simplification is done on the following tabs in transaction
MM01/02/03.
1. Lot Size data in MRP1 Tab:
o Unit of Measure Group (MARC-MEGRU)
2. Procurement in MRP2: MRP considers quota arrangements always, henceforth it
is not required to switch it on in the material master.
o Quota arr. usage. (MARC-USEQU)
3. BOM explosion /dependent Requirement tab in MRP4
o Selection Method (MARC-ALTSL)
4. Repetitive manufacturing /assembly /deployment strategy tab of MRP4
o Action control (MARC-MDACH)
o fair share rule (MARC-DPLFS)
o push distribution (MARC-DPLPU)
o Deployment horizon. (MARC-DPLHO)
5. Storage Location in MRP4
o SLoc MRP indicator (MARD-DISKZ)
o spec.proc.type SLoc (MARD-LSOBS)
o Reoder Point (MARD-LMINB)
o Replenishment qty. (MARD-LBSTF)
6. Also the backend database fields for these "omitted functionality" remains
existing in the system.
The SAP S/4HANA simplification is done on the following tabs/views in transaction
MM41/42/43.
1. 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"
o
Quota arr. usage. (MARC-USEQU)
2. Screen "Repetitive manufacturing/assembly" in views "MRP/Forecast Data: DC",
"Logistics: DC 2" and "MRP/Forecast Data: Store"
o
Action control (MARC-MDACH)
Page | 120
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
3. Screen "BOM explosion/dependent requirements" in views "MRP/Forecast Data:
DC", "Logistics: DC 2" and "MRP/Forecast Data: Store"
o
Selection Method (MARC-ALTSL)
4. Screen "Storage location MRP" in views "MRP/Forecast Data: DC", "Logistics:
DC 2" and "MRP/Forecast Data: Store"
o
o
o
o
SLoc MRP indicator (MARD-DISKZ)
spec.proc.type SLoc (MARD-LSOBS)
Reoder Point (MARD-LMINB)
Replenishment qty. (MARD-LBSTF)
5. Also the backend database fields for these "omitted functionality" remains
existing in the system.
For more information see simplification item in Production Planning “Storage Location
MRP”.
Related SAP Notes
General information about this
Simplification Item
MARCMDACH
SAP Note 2224371
Other Terms
MRP, Simplification
3.22 S4TWL - Material Type SERV
Application Components:
LO-MD-MM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267247
S4TWL - Material Type SERV
Page | 121
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
2. The selected fields are hidden only from the material type "Service Materials",
however, they are supported for other material types.
o
o
o
o
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
Page | 122
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Sales General/Plant
•
•
•
•
•
•
Replacement part
Availability check
Material freight grp
Shipping Data - Trans. Grp, LoadingGrp, Setup time, Proc. time, Base qty
Packaging material data - Matl Grp Pack.Matls, Maximum level, Packaging mat.
Type, Stack ability factor, Allowed pkg weight, Excess wt tolerance, Allowed pkg
volume, Excess volume tol., Ref. mat. for pckg, Closed
General plant parameter - Neg. stocks, SerialNoProfile, DistProf, SerializLevel,
IUID-Relevant, External Allocation of UII, IUID Type
Purchasing
•
•
Material freight grp
Other data - GR Processing time, Post to insp. stock, Critical Part, Source list,
Quota arr. usage, JIT delivery sched.
Accounting 1
•
•
•
•
•
•
•
•
•
VC: Sales order stk
Price control nur Wert S
Moving price
Total Stock
Proj. stk val. Class
Total Value
Valuated Un
Accounting Previous Year (Button)
o MovAvgPrice PP
o Total stock
o Total value PP
Std cost estimate (Button)
Accounting 2
Sales: Sales Org 1
•
•
•
•
•
•
X-distr. Chain status
Valid from
Dchain-spec status
Valid from
Min. dely qty
Delivery Unit
Sales: Sales Org 2
Page | 123
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
Matl statistics grp
Product attributes - Product attribute 1/2/3/4/5/6/7/8/9/10
As of S/4HANA 1605 CE and 1511 FPS2, additionally, the following fields are not
supported for Service Materials (SERV) type:
Basic data 1
•
•
•
•
•
X-plant matl status
Lab/Office
Prod. Hierarchy
Valid from
Packaging material data (entire section)
Sales General/Plant
•
Qual.f.FreeGoodsDis.
Purchasing
•
Qual.f.FreeGoodsDis.
Accounting 1
•
ML act indicator
Sales: sales org. 2
•
Product Hierarchy
Required and Recommended Action(s)
Configurations required for SERV that are part of SET:
1. Material type SERV(Table T134, delivery class: G)
1. This attribute of SERV is provided by SET content
2. Screen sequence control(SPRO transaction: OMT3E
1. Table T133K “Influencing Factors: Screen Sequence No.“ / Delivery
Class: G
2. Tables T133S and T133T are also part of SET content
Related SAP Notes
Page | 124
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
General information about this
Simplification Item
SAP Note 2224251
Page | 125
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
Note Type
Note Number
Note Description
Business Impact
2318733
S4TWL – Interface of SAP Commercial
Project Management with SAP Cloud for
Customer
Page | 126
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Solution
Description
Page | 127
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note that the following Smart Business analytical and transactional apps are not
immediately available with SAP Commercial Project Management for SAP S/4HANA.
•
•
•
•
•
•
F0709
F0710
F0779
F0784
F0786
F0787
My Commercial Projects
Action Items in Commercial Projects
Status Management in Commercial Projects
Overview of Commercial Projects
Costs and Revenues of Commercial Projects
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
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.
Page | 128
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 129
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
/CPD/PFP_A01_IRQ0002_PL_WB01
/CPD/PFP_A01_IRQ0003_PL_WB01
/CPD/PFP_A01_IRQ0004_PL_WB01
/CPD/PFP_A01_IRQ0008_PL_WB01
/CPD/PFP_A01_IRQ0009_PL_WB01
/CPD/PFP_A02_BOQ_PL_WB01
/CPD/PFP_A02_IRQ0001_PL_WB01
/CPD/PFP_A02_IRQ0002_PICM_WB01
/CPD/PFP_A02_IRQ0003_PL_WB01
/CPD/PFP_M_A1_EAC_IRQ0001_WB01
/CPD/PFP_M_A1_ETC_IRQ0002_WB01
/CPD/PFP_M_A1_ETC_IRQ0004_WB01
/CPD/PFP_M_A1_POC_IRQ0003_WB01
/CPD/PFP_M_A1_POC_IRQ0008_WB01
/CPD/PFP_M_A2_IRQ0001_PL_WB01
/CPD/PFP_M_A2_IRQ0002_PL_WB01
/CPD/PFP_M_A2_IRQ0003_PL_WB01
/CPD/PFP_M_A2_IRQ0004_PL_WB01
/CPD/PFP_M_A4_ETC_IRQ0001_WB01
/CPD/PFP_M_A4_ETC_IRQ0002_WB01
/CPD/PFP_M_A4_ETC_IRQ0003_WB01
/CPD/PFP_M_A4_ETC_IRQ0004_WB01
/CPD/PFP_M_A4_ETC_IRQ0005_WB01
/CPD/PFP_M_A6_IRQ0001_PL_WB01
/CPD/PFP_R01_Q0001_VC_WB01
Daily Planning (with Selection Options)
Daily Planning
Weekly Planning (with Selection Options)
Weekly Planning
MRS Weekly Planning (with Selection Options)
MRS Daily Planning (With Selection Options)
BOQ Monthly Planning (with Selection Options)
Monthly Planning
PICM Monthly Planning
MRS Monthly Planning
EAC Forecast
ETC Forecast
ETC Forecast (With Selection Option)
POC Forecast
POC Forecast with Quantity and Cost (with selection
option)
Periodic Planning
Periodic Planning (with Selection Options)
MRS Periodic Planning
MRS Periodic Planning (with Selection Options)
ETC Forecast for Fiscal Period
ETC Forecast for Fiscal Period (with Selection
Options)
ETC Forecast for Fiscal Period (with Qty and Cost)
MRS ETC Forecast for Fiscal Period (with Selection
Options)
MRS ETC Forecast for Fiscal Period
Periodic Cash Flow Planning (with Selection Opt
Version Comparison
Required and Recommended Actions
Inform key users and end users.
Other Terms
SAP Commercial Project Management, CA-CPD-FP, S/4HANA, Workbooks, Project
Cost and Revenue Planning
Page | 130
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
5 Commodity Management
5.1 S4TWL - CM: Simplified Market Data
Application Components:
SD-BF-CPE, MM-PUR-GF-CPE, LO-CMM-BF
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)
1. 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.
Page | 131
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2. 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, MM-PUR-GF-CPE, SD-BF-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
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)
Page | 132
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
LO-CMM-BF, MM-PUR-GF-CPE, SD-BF-CPE
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)
1. In the assigned document 'Cookbook Formula Assembly based on BRFplus', the
process how to transfer Formula Assembly to BRF+ is described.
2. 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
Page | 133
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
5.5 S4TWL - CM: CPE Simplified Data Model
Application Components:
MM-PUR-GF-CPE, LO-CMM-BF, SD-BF-CPE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2461007
S4TWL - CM: CPE Simplified Data Model
Page | 134
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 135
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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'.
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
Page | 136
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 137
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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
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.
Page | 138
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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-BF, LO-CMM-ANL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2547347
S4TWL - CM: Commodity Position
Reporting on Versioned Pricing 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 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.
Page | 139
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Other Terms
ODP, BEx Query, CDS views
5.11 S4TWL - Hedge Management for logistics transactions
Application Components:
LO-CMM-ANL, LO-CMM-BF, FIN-FSCM-TRM-CRM
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
Page | 140
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Hedge Accounting for Exposures, HACC
5.12 S4TWL - Position Reports delivered by Agricultural Contract
Management
Application Components:
LO-CMM-ANL, LO-CMM-BF
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
Page | 141
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
- 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:
Page | 142
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note Type
Note Number
Note Description
Business Impact
2560298
S4TWL - Commodity Pricing in MM
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).
Existing MM Contracts have to be converted to use time independent conditions.
Risk Distribution Plan (RDP) for time independent conditions.
Scheduling Agreements are not supported starting with S/4HANA 1709.
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, LO-CMM-BF, FIN-FSCM-TRM-CRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2555990
S4TWL - CM: Unification of Technologies
for Analytical Data Provision
Page | 143
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
- Operational Data Providers (ODP) 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
Page | 144
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 145
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
5.16 S4TWL - Simplification of DCS based Market Data Handling for Fin
Transactions
Application Components:
LO-CMM-BF, FIN-FSCM-TRM-CRM
Related Notes:
Note Type
Note Number
Note Description
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.
Page | 146
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
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
Page | 147
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Financial transaction pricing data uses DCS-based market data only.
Business Process-Related Information
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:
FIN-FSCM-TRM-CRM, LO-CMM-BF
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
Page | 148
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
•
•
•
•
•
•
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
Page | 149
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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
Page | 150
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 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.
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-ANL, LO-CMM-BF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2591598
S4TWL - CM: Mark-to-Market & Profitand-Loss for logistics transactions
Symptom
Page | 151
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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-toMarket 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 Profitand-Loss for Logistics Transactions', the following steps need to be performed:
•
•
•
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.
Page | 152
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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-andLoss 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
of the MRA functionality 'Determination of Single Records' and stored in the Result Data
Base.
In S4 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.
S4 1709 FPS02 the analytical reporting keyfigures are provided in one single technology
that provides a reporting CDS stack in order to allow Mark-to-Market and Profit-andLoss snapshot reporting across commodities.
Page | 153
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Functional Restrictions
In S4 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)
As described in the attached 'Function in Details - 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 S4 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 S4 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 S4 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 S4 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
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 Markto-Market Accounting for transition from
Business Suite to S/4 HANA
Symptom
Page | 154
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
S4TC Pre-Transition Checks for Mark-to-Market Accounting returns following error
message:
" Action Required: WBRP entries available for conversion. Migration cannot proceed wit
hout 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
Implement this note and run the implemented report in execute mode using the check
box.
Other Terms
S/4 HANA migration, Pre-Checks, LO-CMM, Conversion Report, Markt-to-Market
Accounting
5.24 S4TWL – Integration of Pricing and Payment Events in GTM with
Commodity Mngmt.
Application Components:
LO-GT-CMM, LO-CMM-BF
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
Page | 155
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 – Functionalities on roadmap for CM-GTM Integration
Application Components:
LO-CMM-BF, LO-GT-CMM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2671010
S4TWL – Functionalities on roadmap for
CM-GTM Integration
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.
Risk Integration and Analytics, Free Characteristics, Contract Revaluation and Periodend valuation are not supported in S/4HANA, on premise edition 1809 FPS0. Although
these functionalities are on the roadmap and are planned for future relases.
Page | 156
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
6 Customer Service
6.1 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
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
Page | 157
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code related information
As this is an iView, customers were not
able to develop custom code
6.2 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. CRM on Premise, Cloud 4 Service and
SAP Hybris provide state of the art successors for interaction center help desk use cases.
Business Process related information
Business processes that require a help desk / call center integration cannot be executed in
the customer interaction center any more. Instead they have to be integrated into the
interaction center / help desk applications offered by CRM on Premise, Cloud 4 Service
or SAP Hybris.
Transaction not available in SAP S/4HANA on-premise edition 1511 CIC0
Required and Recommended Action(s)
Business processes that require a help desk / call center integration should be integrated
into the interaction center / help desk applications offered by CRM on Premise, Cloud 4
Service or SAP Hybris.
Related SAP Notes
Page | 158
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code related information
See SAP Note 2229726
Page | 159
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
7 Enterprise Controlling
7.1 Usage of long Material Number in EC-CS
Application Components:
EC-CS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2209784
S4TC SAP_APPL - checks for EC-CS
Symptom
Pre-transition checks for the application EC-CS SAP Consolidation must be
carried out before an upgrade to S/4.
If you have included a field of the type MATNR (material number) as a customerdefined subassignment in the EC-CS data model, the EC-CS data model must
be adjusted before the upgrade.
Reason and Prerequisites
In 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.
Solution
The correction instructions in this SAP Note implement a check to determine whether a
field of the type MATNR is used in the EC-CS data model.
If the check determines that such a field is used in the EC-CS data model as a
customer-defined subassignment, the EC-CS data model must be changed. The
field MATNR must be removed from the data model.
This occurs in the IMG activity under Enterprise Controlling - Consolidation - Add
Characteristics. Note that when you change the data model, the EC-CS Consolidation
transaction data must be converted and information may also be lost during this process,
especially if a field is removed from the data model.
Other Terms
S4TC
Page | 160
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
8 Financials – General
8.1 S4TWL - DATA MODEL CHANGES IN FIN
Application Components:
FI, CO
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
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
Page | 161
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
removed from SAP standard, or has to be removed from custom code – refer to SAP note
1976487.
Compatibility View
(identically-named
view in DDIC)
BSAD
BSAD
BSAK
BSAK
BSAS
BSAS
BSID
BSID
BSIK
BSIK
BSIS
BSIS
FAGLBSAS FAGLBSAS
FAGLBSIS FAGLBSIS
GLT0
GLT0
KNC1
KNC1
KNC3
KNC3
LFC1
LFC1
LFC3
LFC3
COSP
COSP
COSS
COSS
FAGLFLEXT FAGLFLEXT
Original
Table
DDL Source (for the
identically-named DDIC
View)
BSAD_DDL
BSAK_DDL
BSAS_DDL
BSID_DDL
BSIK_DDL
BSIS_DDL
FAGLBSAS_DDL
FAGLBSIS_DDL
GLT0_DDL
KNC1_DDL
KNC3_DDL
LFC1_DDL
LFC3_DDL
V_COSP_DDL
V_COSS_DDL
V_FAGLFLEXT_DDL
Backup Table (for
original table content)
BSAD_BCK
BSAK_BCK
BSAS_BCK
BSID_BCK
BSIK_BCK
BSIS_BCK
FAGLBSAS_BCK
FAGLBSIS_BCK
GLT0_BCK
KNC1_BCK
KNC3_BCK
LFC1_BCK
LFC3_BCK
COSP_BAK
COSS_BAK
FAGLFLEXT_BCK
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
View to read the
identically-named DDIC content of the
view)
database table (w/o
Page | 162
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
ANEA
ANEK
ANEP
ANLC
ANLP
FAAV_ANEA
FAAV_ANEK
FAAV_ANEP
FAAV_ANLC
FAAV_ANLP
FAA_ANEA
FAA_ANEK
FAA_ANEP
FAA_ANLC
FAA_ANLP
BSIM
CKMI1
COEP
V_BSIM
V_CKMI1
V_COEP
BSIM_DDL
V_CKMI1_DDL
V_COEP
FAGLFLEXA FGLV_FAGLFLEXA
FGL_FAGLFLEXA
MLCD
MLCR
MLHD
MLIT
MLPP
T012K
T012T
FMGLFLEX
A
V_MLCD
V_MLCR
V_MLHD
V_MLIT
V_MLPP
V_T012K_BAM
V_T012T_BAM
V_MLCD_DDL
V_MLCR_DDL
V_MLHD_DDL
V_MLIT_DDL
V_MLPP_DDL
V_T012K_BAM_DDL
V_T012T_DDL
FGLV_FMGLFLEXA
FGL_FMGLFLEXA
FMGLFLEXT FGLV_FMGLFLEXT
FGL_FMGLFLEXT
PSGLFLEXA FGLV_PSGLFLEXA
PSGLFLEXT FGLV_PSGLFLEXT
FGL_PSGLFLEXA
FGL_PSGLFLEXT
JVGLFLEXA FGLV_JVGLFLEXA
FGL_JVGLFLEXA
JVGLFLEXT FGLV_JVGLFLEXT
FGL_JVGLFLEXT
redirect to
compatibility view)
FAAV_ANEA_ORI
FAAV_ANEK_ORI
FAAV_ANEP_ORI
FAAV_ANLC_ORI
FAAV_ANLP_ORI
V_BSIM_ORI
V_CKMI1_ORI
V_COEP_ORI
V_FAGLFLEXA_OR
I
V_MLCD_ORI
V_MLCR_ORI
V_MLHD_ORI
V_MLIT_ORI
V_MLPP_ORI
V_T012K_MIG
V_T012T_MIG
V_ FMGLFLEXA
_ORI
V_ FMGLFLEXT
_ORI
V_ JVGLFLEXA
_ORI
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
*
>
>
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.
Page | 163
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Original
Obsolete
As of
DDIC
database
release
database view table used
BKPF_BSAD BSAD
sFIN 1.0
BKPF_BSAD
BSAD
_AEDAT
sFIN 1.0
BKPF_BSAK BSAK
sFIN 1.0
BKPF_BSAK
BSAK
_AEDAT
sFIN 1.0
BKPF_BSID
BSID
sFIN 1.0
BKPF_BSID_
BSID
AEDAT
sFIN 1.0
BKPF_BSIK
BSIK
sFIN 1.0
BKPF_BSIK_
BSIK
AEDAT
sFIN 1.0
GLT0_AEDA
GLT0
T
sFIN 1.0
KNC1_AEDA
KNC1
T
sFIN 1.0
KNC3_AEDA
KNC3
T
sFIN 1.0
LFC1_AEDA
LFC1
T
sFIN 1.0
LFC3_AEDA
LFC3
T
sFIN 1.0
TXW_J_WIT
BSAK
H
sFIN 1.0
Replaced by
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Compatibility
View
DDL Source (for the
compatibility view)
BKPF_BSAD
BKPF_BSAD_DDL
BKPF_BSAD_ BKPF_BSAD_AEDAT
AEDAT
_DDL
BKPF_BSAK
BKPF_BSAK_DDL
BKPF_BSAK_ BKPF_BSAK_AED_D
AEDAT
DL
BKPF_BSID
BKPF_BSID_DDL
BKPF_BSID_A BKPF_BSID_AEDAT_
EDAT
DDL
BKPF_BSIK
BKPF_BSIK_DDL
BKPF_BSIK_A BKPF_BSIK_AEDAT_
EDAT
DDL
GLT0_AEDAT GLT0_AEDAT_DDL
KNC1_AEDAT KNC1_AEDAT_DDL
KNC3_AEDAT KNC3_AEDAT_DDL
LFC1_AEDAT LFC1_AEDAT_DDL
LFC3_AEDAT LFC3_AEDAT_DDL
Identicallynamed DDL TXW_J_WITH TXW_J_WITH_DDL
view
Page | 164
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
V_COSP_A
V_COSS_A
COSP
COSS
sFIN 1.0
sFIN 1.0
VB_DEBI
BSID
sFIN 1.0
VF_BSID
BSID
sFIN 1.0
VFC_DEBI
KNC1
sFIN 1.0
VFC_KRED
LFC1
sFIN 1.0
ENT2006
ENT2163
ENT2164
ENT2165
ENT2166
GLT0
KNC1
LFC1
KNC3
LFC3
sFIN 1.0
sFIN 1.0
sFIN 1.0
sFIN 1.0
sFIN 1.0
Code
Code
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Identicallynamed DDL
view
Code
Code
Code
Code
Code
BSAS
sFIN 1.0
Code
BSIS
sFIN 1.0
Code
BSID
sFIN 1.0
Code
BSIK
sFIN 1.0
Code
BSID
sFIN 1.0
Code
BSIK
sFIN 1.0
Code
BSAK
sFIN 1.0
Code
BSIK
sFIN 1.0
Code
/GRC/V_BAN
T012
K_ACCT
SAP
Simple
Finance,
onpremise
edition
1503
Compatibilit
V_GRC_BANK V_GRC_BANK_ACCT
y view
_ACCT
_DDL
(redirect)
EPIC_V_BRS
_BSAS
EPIC_V_BRS
_BSIS
EPIC_V_BSI
D
EPIC_V_BSI
K
EPIC_V_CUS
TOMER
EPIC_V_VEN
DOR
FMKK_BKPF
_BSAK
FMKK_BKPF
_BSIK
VB_DEBI
VB_DEBI_DDL
VF_BSID
VF_BSID_DDL
VFC_DEBI
VFC_DEBI_DDL
VFC_KRED
VFC_KRED_DDL
Page | 165
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
ANEKPV
ANEP
COPC_V_T01
T012K
2_SKB1
COPC_V_T03
T012K
5D
COVP
COEP
FAP_V_CMP
T012
_HBACC
MLREADST MLHD
MLREPORT MLIT
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
Compatibilit
FAAV_ANEKP
y view
FAA_ANEKPV
V
(redirect)
Compatibilit
V_COPC_T012 V_COPC_V_T012_SK
y view
_SKB1
B1_DDL
(redirect)
Compatibilit
V_COPC_T035 V_COPC_V_T035D_D
y view
D
DL
(redirect)
Compatibilit
y view
V_COVP
(redirect)
V_COVP_DDL
Compatibilit
V_FAP_CMP_ V_FAP_V_CMP_HBA
y view
HBACC
CC_DDL
(redirect)
Compatibilit
V_MLREADST V_MLREADST_DDL
y view
(redirect)
Compatibilit
V_MLREPORT V_MLREPORT_DDL
y view
(redirect)
Page | 166
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
MLXXV
MLHD
V_ANEPK
ANEP
V_ANLAB
ANEP
V_ANLSUM_
ANLA
1
V_ANLSUM_
ANEP
2
V_ANLSUM_
ANLA
5
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
SAP
Simple
Finance,
onpremise
edition
1503
Compatibilit
V_MLXXV
y view
(redirect)
V_MLXXV_DDL
Compatibilit
FAAV_V_ANE
y view
FAA_V_ANEPK
PK
(redirect)
Compatibilit
FAAV_V_ANL
FAA_V_ANLAB
y view
AB
(redirect)
Compatibilit
FAAV_V_ANL
y view
FAA_V_ANLSUM_1
SUM_1
(redirect)
Compatibilit
FAAV_V_ANL
FAA_V_ANLSUM_2
y view
SUM_2
(redirect)
Compatibilit
FAAV_V_ANL
y view
FAA_V_ANLSUM_5
SUM_5
(redirect)
Page | 167
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
There are mandatory configuration steps in General Ledger, Asset Accounting, AccountBased CO-PA, and Cash Management (if used).
IMG -> Migration from SAP ERP to SAP Accounting powered by SAP HANA
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.
8.2 S4TWL - REPLACED TRANSACTION CODES AND PROGRAMS IN
FIN
Application Components:
FI, CO, FIN-FSCM, AC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270335
S4TWL - Replaced Transaction Codes and
Programs 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.
Reason and Prerequisites
Task: Check if the customer uses any of the transactions or programs listed below, in the
column "Old Functionality".
Procedure: Use transaction ST03N to list transaction codes and programs used in the
system in the past.
Rating:
If at least one transaction or program listed below has been used -> YELLOW
If none of the transactions or programs listed below has been used -> GREEN
Solution
Page | 168
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
With the installation of the SAP Simple Finance on-premise edition, certain transaction
codes and programs in the application areas of AC, CO, FI, AA and FIN - compared to
EhP7 for SAP ERP 6.0 - have been replaced with newer transactions, programs, or
WebDynpro applications. The transactions, programs, and WebDynpro applications and
its replacements that are affected are listed in the table below.
Refer to SAP Note 1946054 for more details.
Old
Functionality
FS01
Type New Functionality
Type
Text
TA
FS00
TA
Create G/L Accounts
FS02
FS03
TA
TA
KP06
TA
FS00
FS00
FCOM_IP_CC_COSTELEM
01
TA
TA
WEBDY
N
Change G/L Accounts
Display G/L Accounts
Change Cost and Activity
Inputs
KP07
TA
TA
KP66
TA
KP67
TA
CJ40
TA
CJ41
TA
CJ42
TA
CJ43
TA
CJR2
TA
CJR3
TA
CJR4
TA
CJR5
TA
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
Display Cost and Activity
Inputs
KP65
FCOM_IP_CC_COSTELEM
01
FCOM_IP_CC_COSTELEM
01
FCOM_IP_CC_COSTELEM
01
FCOM_IP_CC_COSTELEM
01
FCOM_IP_PROJ_OVERAL
L01
FCOM_IP_PROJ_OVERAL
L01
FCOM_IP_PROJ_OVERAL
L01
FCOM_IP_PROJ_OVERAL
L01
FCOM_IP_PROJ_COSTELE
M01
FCOM_IP_PROJ_COSTELE
M01
FCOM_IP_PROJ_COSTELE
M01
FCOM_IP_PROJ_COSTELE
M01
CJR6
TA
Create Cost Planning Layout
Change Cost Planning Layout
Display Cost Planning Layout
Change Project Plan
Display Project Plan
Change Project Revenues
Display Project Revenues
PS: Change plan CElem/Activ.
input
PS: Display plan CElem/Activ.
input
PS: Change plan primary cost
element
PS: Display plan primary cost
elem.
FCOM_IP_PROJ_COSTELE WEBDY PS: Change activity input
M01
N
planning
Page | 169
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
TA
TA
TA
TA
TA
TA
FCOM_IP_ORD_COSTELE
M01
FCOM_IP_ORD_COSTELE
M01
FCOM_IP_ORD_COSTELE
M01
FCOM_IP_ORD_COSTELE
M01
CK11N
CK13N
CK40N
CK40N
CK40N
CK40N
WEBDY
N
WEBDY
N
WEBDY
N
WEBDY
N
TA
TA
TA
TA
TA
TA
CK62
TA
CK40N
TA
CK64
TA
CK40N
TA
CK66
CK68
CK74
TA
TA
TA
CK40N
CK40N
CK74N
TA
TA
TA
KB11
TA
KB11N
TA
KB21
KB31
KB33
KB34
KB51
KE21
KE23
TA
TA
TA
TA
TA
TA
TA
KB21N
KB31N
KB33N
KB34N
KB51N
KE21N
KE24
TA
TA
TA
TA
TA
TA
TA
KKE1
KKE2
KKE3
TA
TA
TA
CKUC
CKUC
CKUC
TA
TA
TA
KKEC
TA
CKUC
TA
KKED
TA
CKUC
TA
KKB4
TA
CKUC
TA
KKBF
TA
KKR0
TA
KPF6
TA
KPF7
TA
KO14
TA
KPG7
TA
CK11
CK13
CK41
CK42
CK43
CK60
Change CElem/Activity Input
Planning
Display CElem./Acty Input
Planning
Copy Planing for Internal
Orders
Display Cost Planning Layout
Create Product Cost Estimate
Display Product Cost Estimate
Create Costing Run
Change Costing Run
Display Costing Run
Preselection for Material/Plant
Find Structure: BOM
Explosion
Run: Cost Estimate of Objects
Mark Run for Release
Release Costing Run
Create Additive Costs
Enter Reposting of Primary
Costs
Enter Activity Allocation
Enter Statistical Key Figures
Display Statistical Key Figures
Reverse Statistical Key Figures
Enter Activity Posting
Create CO-PA line item
Display CO-PA line item
Add Base Planning Object
Change Base Planning Object
Display Base Planning Object
Compare Base Object - Unit
Cost Est
BOM for Base Planning
Objects
Itemization for Base Planning
Obj.
Order Selection (Classification)
Page | 170
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
KKPHIE
TA
KKP2
TA
KKP4
TA
KKP6
TA
KKPX
TA
KKPY
Ta
CKMDUVMAT/CKMDUV
ACT (Distribution)
CKMDUVMAT/CKMDUV
ACT (Distribution)
CKMDUVMAT/CKMDUV
ACT (Distribution)
CKMDUVMAT/CKMDUV
ACT (Distribution)
CKMDUVMAT/CKMDUV
ACT (Distribution)
CKMDUVMAT/CKMDUV
ACT (Distribution)
TA
Cost Object Hierarchy
TA
Change Hierarchy Master
Record
TA
Display Cost Object Hierarchy
TA
Cost Object: Analysis
TA
TA
F.24
PRO
RFDEPL00
G
TA FINT
F.2A
TA
FINT
TA
F.2B
TA
FINT
TA
F.2C
TA
FINT
TA
F.4A
TA
FINTAP
TA
F.4B
TA
FINTIAP
TA
F.4C
TA
FINTAP
TA
FA39
TA
obsolete
F.47
TA
FINTAP
RFFOD__L
PRO
PMW
G
RFFOD__S
PRO
PMW
G
RFFOUS_T
PRO
PMW
G
RFDOPO10
RFFOM200
RFFOM202
PRO
PMW
G
PRO
PMW
G
Actual Cost Distribution: Cost
Obj.
Actual Cost Distribution: Cost
Obj.
PROG
TA
TA
A/R: Interest for Days Overdue
A/R Overdue Int.: Post
(Without OI)
A/R Overdue Int.: Post (with
OI)
Calc.cust.int.on arr.: w/o
postings
Calc.vend.int.on arr.: Post (w/o
OI)
Calc.vend.int.on arr.: Post(with
OI)
Calc.vend.int.on arr.: w/o
postings
Vendors: calc.of interest on
arrears
Payment Medium Germany Pmts in Ger.For.Tr.Regs (Z1
Form)/Foreign DME
International Payment Medium
- Check (without check
management)
Payment Medium USA Transfers/Bank Direct Debits
in ACH Format
International Payment Medium
- SWIFT Format MT200
International Payment Medium
- SWIFT Format MT202
Page | 171
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RFFOM210
RAGITT01
FAGL_FC_VA
L
S_PL0_860000
30
S_PCO_360002
18
S_PCO_360002
19
S_ALR_87012
326
PRO
PMW
G
PRO
S_ALR_87011990
G
TA
TA
TA
TA
TA
S_E38_980000
TA
88
S_E38_980000
TA
89
S_AC0_520008
TA
87
S_AC0_520008
TA
88
S_ALR_87100
TA
992
FAGL_FCV
International Payment Medium
- SWIFT Format MT210
TRAN
Asset History Sheet
TRAN
Foreign Currency Valuation
FIS_FPM_GRID_GLACC_B WEBDY
G/L Account Balances
AL
N
WEBDY
FCOM_FIS_AR_OVP
Receivables Segment
N
WEBDY
FCOM_FIS_AP_OVP
Payables Segment
N
FCOM_FIS_GLACCOUNT_ WEBDY
Chart of Accounts
OVP
N
Profit Center - Plan/Actual
(Fiori-ID: F0926;
Profit Center Group:
FIORI
Query: /ERP/SFIN_M01_Q270
Plan/Actual/Dif
1)
Profit Center Group:
Plan/Plan/Actual
Receivables: Profit Center
Payables: Profit Center
Account Assignment Manual
FIORI
Profit-Center - Plan/Actual
current year (Fiori-ID: F0932;
Query:
/ERP/SFIN_M01_Q
2702)
WEBDY
Receivables Profit Center
N
WEBDY
Payables Profit center
N
no replacement
9 Financials - Accounts Payable/Accounts
Receivable
9.1 S4TWL - SAP Working Capital Analytics/DSO and DPO
Application Components:
FI-AP, FI-AR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270383
S4TWL - SAP Working Capital
Analytics/DSO and DPO
Page | 172
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Working Capital Analytics, an innovative means of analyzing DSO and DPO
was provided to every Business Suite, SoH, or Simple Finance Customer (part of the
HANA License). This functionality is not available within SAP S/4HANA. Alternative
reports for DSO and DPO analysis are available, covering the most important aspects of
DSO and DPO analysis.
Business Process related information
DSO and DPO Analysis have to move to the new reports.
Required and Recommended Action(s)
DSO and DPO Analysis have to move to the new reports.
9.2 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
Page | 173
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
account status, and making payments online as a self-service. The functionality is not
considered as the target architecture. The Customer can still continue to use the
functionality to make the system conversion to SAP S/4HANA, on-premise edition 1511
less disruptive (Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is not available
yet.).
Business Process related information
The functionality integration of SAP Accounts Receivable (FI-AR) with FSCM Biller
Direct is not the target architecture, but still available and can be used within SAP
S/4HANA, on-premise edition 1511.
Required and Recommended Action(s)
None
9.3 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 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 Payable (FI-AP) with FSCM Biller Direct it is
possible to offer to end-vendors the convenience of uploading invoices, monitor the
corresponding account movements online as a self-service. The functionality is not
considered as the target architecture. The Customer can still continue to use the
functionality to make the system conversion to SAP S/4HANA, on-premise edition 1511
less disruptive (Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is not available
yet.).
Page | 174
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
The functionality integration of SAP Accounts Payable (FI-AP) with FSCM Biller Direct
is not the target architecture, but still available and can be used within SAP S/4HANA,
on-premise edition 1511.
Required and Recommended Action(s)
None
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:
Page | 175
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
o 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:
o 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.
o Planned values from tables ANLP and ANLC are saved in table
FAAT_PLAN_VALUES in new Asset Accounting.
o
•
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).
Table
ANEA
ANEP
ANEK
ANLC
ANLP
Compatibility Views
DDL Source
DDIC View
FAA_ANEA
FAAV_ANEA
FAA_ANEP
FAAV_ANEP
FAA_ANEK
FAAV_ANEK
FAA_ANLC
FAAV_ANLC
FAA_ANLP
FAAV_ANLP
Access to Original Table
DDL Source
DDIC View
FAA_ANEA_ORI FAAV_ANEA_ORI
FAA_ANEP_ORI FAAV_ANEP_ORI
FAA_ANEK_ORI FAAV_ANEK_ORI
FAA_ANLC_ORI FAAV_ANLC_ORI
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.
DDIC View
V_ANEPK
ANEKPV
V_ANLSUM_2
V_ANLAB
V_ANLSUM_1
Compatibility View
DDL Source
FAA_V_ANEPK
FAA_ANEKPV
FAA_V_ANLSUM_2
FAA_V_ANLAB
FAA_V_ANLSUM_1
DDIC View
FAAV_V_ANEPK
FAAV_ANEKPV
FAAV_V_ANLSUM_2
FAAV_V_ANLAB
FAAV_V_ANLSUM_1
Page | 176
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
V_ANLSUM_5
FAA_V_ANLSUM_5
FAAV_V_ANLSUM_5
Other Terms
SAP S/4HANA; Asset Accounting; ACDOCA; compatibility view
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
Page | 177
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.
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:
Page | 178
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
It is no longer necessary (or possible) to restrict the transaction types to individual
depreciation areas.
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 Change in Holdings in Real-time in All Valuations
In SAP S/4HANA, all changes in holdings are posted in real-time or simultaneously to
the general ledger. Periodical APC postings are therefore superfluous and are no longer
supported. This also applies for the processing of reserves for special depreciation.
This affects the Customizing settings for the depreciation area as follows: All options
previously used to post APC to the general ledger periodically are now inapplicable.
Instead the following indicator must be set for the affected depreciation area:
Depreciation Area
Reserve for special depreciation area
Indicator
4 - Area Posts APC Immediately,
Depreciation Periodically
Area for parallel valuation with the accounts 4 - Area Posts APC Immediately,
approach
Depreciation Periodically
Area for parallel valuation with the ledger 1 - Area Posts in Real Time
approach
Recommendation:
In classic Asset Accounting you may have one depreciation area in a foreign currency
Page | 179
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
that posts periodically to the general ledger (in other words, in Customizing for the
depreciation area, you have selected the option Area posts holdings and depreciation
periodically).
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 Area does not post for postings to the general
ledger. As a consequence, this foreign currency area of Asset Accounting is then
managed as a statistical area.
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:
•
•
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:
Page | 180
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 accountingprinciple-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.
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).
Page | 181
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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-principlespecific 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 is therefore a required entry field.
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.
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,
Page | 182
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. 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.
2. 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:
o The planned depreciation is determined with master record changes and
with postings on the asset and updated in the database accordingly.
o The depreciation run adopts the planned asset values and posts them.
o 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.
o If you specify a server group, the system behaves as it has until now.
Page | 183
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
o Errors occurred
o Documents posted successfully
o No documents to post
o
•
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:
o In a test run, the depreciation run can be started in dialog with a limit to a
maximum of 1000 assets.
o The update run can only be started in the background.
o In an update run, the company code must be capable of being posted to, in
other words, the posting periods must be open.
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 FIORI app Asset Transactions (as of SAP S/4HANA 1709).
Here you can use the transaction variant All Transactions and a filter for posted
depreciation (transaction type 500); and display the documents for the depreciation
posted.
The smoothing method is no longer necessary and is therefore no longer supported.
Page | 184
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
10.2.20Insurance Values
Until now there were two ways to map insurable values in the system:
1. Defining specific information for insuring the complex fixed asset in the asset
master record
2. 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.
10.2.21Leasing 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.22BAPIs
Changed BAPIs
In the BAPIs that already existed in classic Asset Accounting, the fields Accounting
Principle/Ledger Group and Depreciation Area have been added.
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:
Page | 185
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Object:
Short Description
Asset Acquisition
Business Object:
Object Name
AssetAcquisition
Function Modules
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
AssetReversalDoc BAPI_ASSET_REVERSAL_CHECK,
Reversal
BAPI_ASSET_REVERSAL_POST
New BAPIs
There are the following new BAPIs:
Business-Object:
Short Description
Assets: Down
payment
Assets: Investment
Support
Business Object: Function Modules
Object Name
AssetDownPayment BAPI_ASSET_DOWNPAYMENT_CHECK,
BAPI_ASSET_DOWNPAYMENT_POST
AssetInvestSupport BAPI_ASSET_INV_SUPPORT_CHECK,
Assets: Revaluation
AssetRevaluation
Assets: Subsequent
Costs and Revenues
AssetSubCostRev
BAPI_ASSET_INV_SUPPORT_POST
BAPI_ASSET_REVALUATION_CHECK,
BAPI_ASSET_REVALUATION_POST
BAPI_ASSET_SUB_COST_REV_CHECK,
Assets: Transfer
Postings
AssetTransfer
BAPI_ASSET_SUB_COST_REV_POST
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
10.2.23Fiscal Year Change/Balance Carryforward
The balance carryforward of Asset Accounting is integrated with the balance
carryforward of Financial Accounting with the universal journal entry:
Page | 186
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
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.24Reports 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.25Legacy 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:
1. You create asset master records for the legacy data transfer using transaction
AS91.
2. You post the transfer values using transaction ABLDT; In doing so, a universal
journal entry is posted for the fixed asset.
3. 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.
4. You use transaction ABLDT_OI to post the open items for an asset under
construction with line item processing.
Page | 187
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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 masscompatible transfer methods are no longer supported:
•
•
•
Program RAALTD01
Program RAALTD11
Program RAALTD11_UNICODE
Page | 188
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.26Archiving
The reload program for archiving RAARCH03 is no longer supported.
Archived documents of Asset Accounting can only be written but not reloaded.
10.2.27Constraints
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
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.
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.
Page | 189
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
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.28Existing Data and Conversion/Migration
10.2.29Existing 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
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.
Page | 190
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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.
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
Conversion Guide for SAP S/4HANA
Explanation
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 Specification for the Migration in Asset
Accounting
Accounting: Recommended Time for the
Migration, Prerequisites, Migration of
Customizing with Many Examples, Among
Others.
10.2.30User 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
Page | 191
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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).
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
ABUB
AW01_AFAR
ABF1 and ABF1L
AJRW
OASV
AB02
ASKB and ASKBN
ABMW
ABCO
Programs
The following programs are no longer available:
Page | 192
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
RAALTD01, RAALTD11, RAALTD11_UNICODE
RAPERB2000, RAPOST2000
RAABST01, RAABST02, FAA_GL_RECON
RAJAWE00
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,
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
Other Terms
Page | 193
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
10.3 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.3.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
Page | 194
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.
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.3.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.3.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:
Page | 195
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
It is no longer necessary (or possible) to restrict the transaction types to individual
depreciation areas.
The user exit APCF_DIFFERENT_AMOUNTS_GET is no longer supported.
10.3.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.3.5 Updating Journal Entries
The journal entries are updated in Financial Accounting at asset level. The entry also
contains the asset number.
10.3.6 Change in Holdings in Real-time in All Valuations
In SAP S/4HANA, all changes in holdings are posted in real-time or simultaneously to
the general ledger. Periodical APC postings are therefore superfluous and are no longer
supported. This also applies for the processing of reserves for special depreciation.
This affects the Customizing settings for the depreciation area as follows: All options
previously used to post APC to the general ledger periodically are now inapplicable.
Instead the following indicator must be set for the affected depreciation area:
Depreciation Area
Reserve for special depreciation area
Indicator
4 - Area Posts APC Immediately,
Depreciation Periodically
Area for parallel valuation with the accounts 4 - Area Posts APC Immediately,
approach
Depreciation Periodically
Area for parallel valuation with the ledger 1 - Area Posts in Real Time
approach
Recommendation:
In classic Asset Accounting you may have one depreciation area in a foreign currency
Page | 196
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
that posts periodically to the general ledger (in other words, in Customizing for the
depreciation area, you have selected the option Area posts holdings and depreciation
periodically).
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 Area does not post for postings to the general
ledger. As a consequence, this foreign currency area of Asset Accounting is then
managed as a statistical area.
10.3.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.3.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.3.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:
•
•
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:
Page | 197
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.3.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.3.11Document Display
A business transaction is split (1) into an operational part that creates an accountingprinciple-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.
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).
Page | 198
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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-principlespecific documents.
10.3.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.3.13Changed and deleted functions in detail
10.3.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.3.15Revaluation
A revaluation is always posted accounting principle-specific.
The Accounting Principle field in transaction ABAWL is therefore a required entry field.
10.3.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.
You can copy the code from the user exit 1:1 when doing so, since the enhancement
interface has not been changed.
10.3.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,
Page | 199
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.3.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.3.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:
1. 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.
2. 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:
o The planned depreciation is determined with master record changes and
with postings on the asset and updated in the database accordingly.
o The depreciation run adopts the planned asset values and posts them.
o 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.
o If you specify a server group, the system behaves as it has until now.
Page | 200
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
o Errors occurred
o Documents posted successfully
o No documents to post
o
•
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:
o In a test run, the depreciation run can be started in dialog with a limit to a
maximum of 1000 assets.
o The update run can only be started in the background.
o In an update run, the company code must be capable of being posted to, in
other words, the posting periods must be open.
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 FIORI app Asset Transactions (as of SAP S/4HANA 1709).
Here you can use the transaction variant All Transactions and a filter for posted
depreciation (transaction type 500); and display the documents for the depreciation
posted.
The smoothing method is no longer necessary and is therefore no longer supported.
Page | 201
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
10.3.20Insurance Values
Until now there were two ways to map insurable values in the system:
1. Defining specific information for insuring the complex fixed asset in the asset
master record
2. 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.
10.3.21Leasing 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.3.22BAPIs
Changed BAPIs
In the BAPIs that already existed in classic Asset Accounting, the fields Accounting
Principle/Ledger Group and Depreciation Area have been added.
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:
Page | 202
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Object:
Short Description
Asset Acquisition
Business Object:
Object Name
AssetAcquisition
Function Modules
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
AssetReversalDoc BAPI_ASSET_REVERSAL_CHECK,
Reversal
BAPI_ASSET_REVERSAL_POST
New BAPIs
There are the following new BAPIs:
Business-Object:
Short Description
Assets: Down
payment
Assets: Investment
Support
Business Object: Function Modules
Object Name
AssetDownPayment BAPI_ASSET_DOWNPAYMENT_CHECK,
BAPI_ASSET_DOWNPAYMENT_POST
AssetInvestSupport BAPI_ASSET_INV_SUPPORT_CHECK,
Assets: Revaluation
AssetRevaluation
Assets: Subsequent
Costs and Revenues
AssetSubCostRev
BAPI_ASSET_INV_SUPPORT_POST
BAPI_ASSET_REVALUATION_CHECK,
BAPI_ASSET_REVALUATION_POST
BAPI_ASSET_SUB_COST_REV_CHECK,
Assets: Transfer
Postings
AssetTransfer
BAPI_ASSET_SUB_COST_REV_POST
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
10.3.23Fiscal Year Change/Balance Carryforward
The balance carryforward of Asset Accounting is integrated with the balance
carryforward of Financial Accounting with the universal journal entry:
Page | 203
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
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.3.24Reports 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.3.25Legacy 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:
1. You create asset master records for the legacy data transfer using transaction
AS91.
2. You post the transfer values using transaction ABLDT; In doing so, a universal
journal entry is posted for the fixed asset.
3. 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.
4. You use transaction ABLDT_OI to post the open items for an asset under
construction with line item processing.
Page | 204
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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 masscompatible transfer methods are no longer supported:
•
•
•
Program RAALTD01
Program RAALTD11
Program RAALTD11_UNICODE
Page | 205
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.3.26Archiving
The reload program for archiving RAARCH03 is no longer supported.
Archived documents of Asset Accounting can only be written but not reloaded.
10.3.27Constraints
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
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.
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.
Page | 206
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
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.3.28Existing Data and Conversion/Migration
10.3.29Existing 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
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.
Page | 207
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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.
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
Conversion Guide for SAP S/4HANA
Explanation
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 Specification for the Migration in Asset
Accounting
Accounting: Recommended Time for the
Migration, Prerequisites, Migration of
Customizing with Many Examples, Among
Others.
10.3.30User 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
Page | 208
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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).
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
ABUB
AW01_AFAR
ABF1 and ABF1L
AJRW
OASV
AB02
ASKB and ASKBN
ABMW
ABCO
Programs
The following programs are no longer available:
Page | 209
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
RAALTD01, RAALTD11, RAALTD11_UNICODE
RAPERB2000, RAPOST2000
RAABST01, RAABST02, FAA_GL_RECON
RAJAWE00
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,
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
Other Terms
Page | 210
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
10.4 S4TWL - INTEGRATION TO LEASE ACCOUNTING ENGINE
(LAE)
Application Components:
FI-LA, CRM-LAM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270391
Release Restriction
2211665
Release Restriction
2328754
S4TWL - Integration to Lease Accounting
Engine (LAE)
Release information for "SAP for Banking"
in connection with "SAP S/4HANA, onpremise edition 1511"
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
Page | 211
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
10.5 S4TWL - JOINT VENTURE ACCOUNTING (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
GJT3 - Asset retirement
GJT4 - Asset sale
GJT5 - WIP to WIP
GJT6 - WIP to Asset
Page | 212
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.6 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.6.1 Business Functions of Asset Accounting
The following business functions exist for Asset Accounting:
Description Technical Name
FI-AA,
FIN_AA_CI_1
Asset
Accounting
FI-AA,
Parallel
Valuation
FIN_AA_PARALLEL_VAL
Release
Status in
SAP
S/4HANA
On
Premise
SAP
Customer
enhancement switchable
package 6 for
SAP ERP 6.0
SAP
Customer
enhancement switchable
package 7 for
Usability
in SAP
S/4HANA
Obsolete
Obsolete
Page | 213
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
SAP ERP 6.0,
SP02
FI-AA,
FIN_AA_SEGMENT_REPORTING SAP
Always on See below
Segment
S/4HANA
reporting for
1610, FPS01
fixed assets
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".
10.6.2 Business Functions of General Ledger Accounting
For Asset Accounting, the following business functions from General Ledger Accounting
are relevant:
Description
Technical Name
Release
FI-GL (New), FIN_GL_REORG_1
SAP
Profit Ctr
enhancement
Reorganization
package 5 for
and Segment
SAP ERP 6.0
Reports
FI-GL (New), FIN_GL_REORG_SEG SAP SAP
Segment
enhancement
Reorganization
package 6 for
SAP ERP 6.0
Status in SAP
S/4HANA On
Premise
Customer
switchable
Usability in
SAP
S/4HANA
Not supported
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
Page | 214
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
business functions in SAP S/4HANA.
If you want to subsequently activate segment reporting for fixed assets in SAP
S/4HANA, then you need to activate the business function FI-AA for this,
segment reporting for 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.6.3 Other Business Functions
Description
Technical Name Release
Status in SAP
S/4HANA On
Premise
FIN_CO_COGM AP enhancement Customer
package 5 ff. for switchable
SAP ERP 6.0
CO, Parallel
Valuation of
Costs of Goods
Manufactured
Materials
LOG_MM_CI_3 SAP
Management enhancement
Enhancements in
package 5 for
Procurement
SAP ERP 6.0
Customer
switchable
Usability in
SAP S/4HANA
Supported (see
details below)
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
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,
Page | 215
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 216
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
11 Financials - Cash Management
11.1 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 doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item 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.
Business Value
The new SAP S/4HANA Finance for cash managementSAP 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
transfering fund to handle surplus and deficit.
2. Medium-term liquidity forecast and rolling plans of long-term liqudiity.
3. Centralized bank account management, with which business users can manage bank
accounts as master data with more business attributes.
Comparison of Functional Scope
Page | 217
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The following table summarizes the differences between the classic Cash and
Liquidity Management (Cash Management and Liquidity Planner) and SAP Cash
Management.
SAP Cash
Classic Cash and
Management,
Liquidity
delivered with SAP
Management
S/4HANA 1511
•
•
•
•
Banks /
Bank
Accounts
•
SAP S/4HANA
Finance for cash
SAP S/4HANA
management,
Finance for cash
delivered
management,
with SAP
S/4HANA 1610 delivered with SAP
(Delta to 1511) S/4HANA 1709
(Delta to 1610)
With this release, the
Centralized bank
following features
account
have changed for the
management is
app "Manage Bank
supported.
Accounts":
The following
transaction codes are
replaced by the new
Fiori app Manage
Banks, which can be
accessed from the Fiori Bank
Launchpad.
accounts can be
replicated via
• Create Bank: iDoc to other
FI01
Create
systems on
• Change Bank: Simple Finance
Bank: FI01
FI02
Change
1503, S/4HANA
• Display Bank: Finance 1605+,
Bank: FI02
FI03
Display
S/4HANA OP
Bank: FI03
1610+, SAP ERP
House
6.0 EhP6+.
Bank Account
Bank /
Management (BAM)
House
Bank
• Bank hierarchy
Account:
based on bank
FI12
business
Business
partners
Partner
• Free-style bank
(Role
account groups
TR0703):
allow ad-hoc
BP
watch for
several bank
accounts.
• Fuzzy search
for bank
accounts
• Attachments
• The transaction
FI12 House
Bank / House
Bank Account
•
You can now
choose to
implement a
dual control
process for
bank account
management.
Revisions are
then saved
whenever you
or any other
users create,
modify, copy,
reopen, or
close a bank
account. You
can use the
revisions to:
o Ask
anoth
er
autho
rized
user
to
activ
ate
your
revisi
on to
gener
Page | 218
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
is not available.
Instead, you
use the
following apps
via the Fiori
Launchpad to
manage house
banks and
house bank
accounts:
o Define
house
banks:
Use
the Fior
i app
Manag
e Banks
o Define
house
bank
account
s: You
can do
so in
the
Fiori
app M
anage
Bank
Accoun
ts by
editing
the
bank
account
master
data,
on the
Connec
tivity
Path
tab.
o House
bank
and
house
bank
account
o
o
ate a
new
activ
e
bank
accou
nt
versi
on
Com
pare
revisi
ons
to
identi
fy
differ
ences
betw
een
differ
ent
bank
accou
nt
versi
ons○
View
bank
accou
nt
histor
y to
track
accou
nt
chan
ges
This process ensures
the 4-eye principle
but is easier to
implement than the
business workflow
approach.
•
Settings for
bank
statements
Page | 219
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
s
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):
A basic version of Bank
Account Management
is provided for
customers without the
license of SAP Cash
Management. It
provices:
•
•
•
Attributes
include account
holder, internal
contact
persons, and
house bank
account related
settings on
bank accounts.
No workflowbased bank
account
processes.
The transaction
FI12 House
Bank / House
•
•
have been
added to bank
account
master data.
A new field
for financial
object
numbers has
been added
and allows
for
integration
with Treasury
and Risk
Management.
The system
automatically
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
workflow template,
Page | 220
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Bank Account
is not available.
Instead, you
use the
following apps
via the Fiori
Launchpad to
manage house
banks and
house bank
accounts:
o Define
house
banks:
Use
the Fior
i app
Manag
e Banks
o Define
house
bank
account
s: You
can do
so in
the
Fiori
app M
anage
Bank
Accoun
ts by
editing
the
bank
account
master
data,
on the
Connec
tivity
Path
tab.
o House
bank
and
house
bank
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
preconditions
for starting
the workflow
Create new
workflows by
copying
existing ones
You can
define
workflow
processes for
bank account
management
according to
your own
business
requirements
by defining
preconditions
, step
sequence, and
recipients.
Activate and
deactivate
workflows
Page | 221
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
Cash Position:
FF7A
Liquidity
Forecast: FF7B
Data Integration:
•
Cash
Position /
Liquidity
Forecast
•
•
•
•
•
•
•
Bank
statement
accounting
documents
Payment
accounting
documents
AR/AP
accounting
documents
Memo
records
Purchase
orders
Sales
orders
TRM
CML
Cash Position:
•
•
account
s
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.
•
Liquidity
Forecast:
Define an
order for
activated
workflows
The system
evaluates the
order and the
preconditions
of each
activated
workflow to
determine
which
workflow to
trigger for
different bank
accounts and
scenarios.
Delete an
existing
workflow that
is deactivated
Cash Position and
Liquidity Forecast:
Use app Cash
Position to
You can now use With the app "Cash
check highFlow Analyzer", you
the following
level KPIs.
Fiori apps in your can obtain an
• Use app Cash
Fiori launchpad: overview of the
Position Details
aggregate amounts
to display
and line item details
• Liquidity
detailed
of short-term cash
Forecast
positions on
position, medium• Liquidity
bank accounts.
and long-term
Forecast
liquidity forecast, and
Detail
Liquidity Forecast:
actual cash flows.
You can analyze cash
Data
flows over days,
Use SAP
Integration:
weeks, months,
BusinessObjects
Analysis, edition for
quarters, or years.
• MM
Microsoft Office (AO)
You can get an end(Material of-period report with
or transaction code
s
RSRT to open the BW
shifts to working
Manage days. You can also
queries for liquidity
ment)
display an Bank
forecast.
• SD
Account Group
(Sales
Hierarchy view and
Data Integration:
and
Liquidity Item
Page | 222
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
FI-CA
Real-Estate
Public
Sector
•
•
•
•
•
•
•
•
•
•
Memo
Record
Payment
(F110,
F111)
•
•
•
Create
memo
records:
FF63
FF63 and FF65 are
Display
supported with cash
memo
management accounts.
records
List: FF65
F110
F111
Plan part:
Liquidity
Planner
•
Bank
statements
Bank statement
Accounting
documents
Payment
accounting
documents
AR/AP
accounting
documents
Memo records
TRM
CML
FI-CA
Not integrated:
Industryspecific data
sources, sales
orders,
purchase
orders, fund,
grant, payment
orders,
payment
requests
BPC or
BW-IP set
up in a
Distributi Hierarchy view. This
on)
is a successor app for
"Cash Position
Details", as well as
combining the key
features from
"Liquidity Forecast
Details" and "Cash
Flow Detail
Analysis".
Data Integration:
•
Promise-topay
You can now use
the following
Fiori apps in your
Fiori launchpad:
•
•
Actual
Cash
Flow
Cash
Flow Detailed
Analysis
F110 and F111 are
supported as before.
Plan part:
•
Actual part:
Embedded
You can now use
Liquidity Plan
the following
with BPC/PAK
Fiori Theme apps
(Planning
Page | 223
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
separate
system.
ETL for
master data
and
transactiona
l data is
necessary.
Actual part:
•
Actual
Cash Flow
Report:FL
QREP
•
•
•
Configuration:
•
Account
assignment
through
Query and
Query
Sequence
Application
in your Fiori
Kit) and SAP launchpad:
BusinessObject
s Analysis,
• Actual
edition for
Cash
Microsoft
Flow
Office UI.
• Cash
No ETL is
Flow needed.
Detailed
Automated
Analysis
liquidity
forecast is
integrated.
The
functionality of
hedge
planning/report
and currency
conversion
among different
planning units
are not
supported.
Actual part:
•
•
Old transaction
is not available.
You can use
SAP
BusinessObject
s Analysis,
edition for
Microsoft
Office (AO) or
transaction
code RSRT to
show the
integrated
actual cash
flow
information.
Configuration:
•
Account
assignment
through Query
Page | 224
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
and Query
Sequence
•
•
Cash
Concentrat
ion
•
Create:
FF73
Access
with
Variant:
FF74
Print
Confirmati
ons: 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.
Retrieve remote
Liquidity Planner actual
Load remote Cash
data and cash summary
Distributed Position and
data of classic cash into
Liquidity Forecast
Cash
the One Exposure of
data through IDOC.
S/4 HANA Cash
Management.
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/8
FF69
Page | 225
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
FF70
FF71
FF72
FF7A
FF7B
FF:1
FFTL
FFZK
FLQAB
FLQAC
FLQAD
FLQAF
FLQAL
FLQAM
FLQAM_TP
FLQC10
FLQC12
FLQC13
FLQC13F
FLQC1A
FLQC2
FLQC20
Page | 226
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Required and Recommended Actions
•
•
•
With the use of SAP S/4HANA, 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 Bank Account Management Lite
or the full version of Bank Account Management (with SAP Cash Management).
As a result, before you go live with SAP S/4HANA, you must migrate house bank
accounts if there are any.
All the apps must be accessed from the Fiori Launchpad.
Customers who were using the full SAP Cash Management and are 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".
How to Determine Relevancy
You can identify via this description if the Simplification Item might be relevant.
Task 1: Check result of report FINS_PRE_CHECK_SFIN_1503 for the use of classic
Cash Management.
Procedure:
Check if one the following messages are shown:
•
•
If there are no company codes with active cash management found, it
means classic Cash Management is not used;
If the indicator for cash management is active for the following company
codes, you then need to check the following manually:
1. Run transaction SE16
2. Check the table entries in one of the following tables: FDM1, FDM2,
FDMV, FDS1, FDS2, FDSB, FDSB2, FDSBDIST, FDSP, FDSR, FDSR2,
FDSRDIST, FDT1, FDW1, FDD1, FDES, FDESDIST, FDFIEP, FDI1,
FDLF, FDLF2, FDRE.
3. If you find no entries, it means classic Cash Management is not used; If
you find any entries, it means classic Cash Management is used.
Rating: Yellow, if classic Cash Management is used; Otherwise, it's green.
Task 2: Check manually for the use of Liquidity Planner.
Page | 227
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Procedure:
1. Run transaction SE16
2. Check the table entries in one of the following tables: FLQSUM and
FLQSUM_FC.
3. If you find no entries, it means Liquidity Planner is not used; If you find any
entries, it means Liquidity Planner is used.
Rating: Yellow, if Liquidity Planner is used; Otherwise, it's green.
If classic Cash Management and Liquidity Planner are used (e.g. for cash position
reporting), you need to re-implement the new SAP S/4HANA Finance for cash
management.
Page | 228
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 229
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Reason and Prerequisites
Page | 230
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
You are currently using summarization hierarchies, order hierarchies, or project
hierarchies and want to understand the impact of moving to SAP S/4HANA.
Summarization hierarchies allow you to aggregate data on orders or projects using the
characteristics in the order header. 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 entires for the hierarchy structure exist in View
V_KKR0_OR_NEW.
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)
Page | 231
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Check your existing roles to determine which include transaction KKBC_HOE and
KKRC and replace by KKBC_HOE_H.
Other Terms
Order Hierarchy, Project Hierarchy
12.3 S4TWL - Technical Changes in Material Ledger with Actual Costing
Application Components:
CO-PC-ACT, FIN-MIG-ML
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)
Page | 232
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
When this checkbox is marked, this means that Material Ledger Actual Costing is active
in this plant.
Technically this can be verified via database table T001W, field MGVUPD. 'X' means
that Material Ledger Actual Costing is active in this plant.
In addition, the table T001W shows the link between the plant and the valuation area.
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.
Page | 233
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
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.
It is not allowed to change Material Ledger costing runs, nor to run steps of
Material Ledger costing runs during the process of system conversion.
It is not allowed to activate or deactivate Material Ledger Actual Costing during
the process of system conversion for one or more plants.
Details:
Simplified Data Model
•
Tables MLDOC and MLDOCCCS
o The new Material Ledger Document tables MLDOC and MLDOCCCS
replace most former periodic tables (MLHD, MLIT, MLPP, MLPPF,
MLCR, MLCRF,
MLKEPH, CKMLPP, CKMLCR, MLCD, CKMLMV003, CKMLMV004,
CKMLPPWIP, CKMLKEPH). For more information refer to note
2352383.
o Some of the former periodic tables are still required for the following
purposes:
▪ The Material Ledger Closing Document is stored in the former ML
document tables (ML*)
▪ Standard Price. Periodic Unit Price and Price Control are still
managed in table CKLMLCR
▪ Cost Component Split for Prices is still managed in tables
CKMLPRKEKO and CKMLPRKEPH
o The design of tables MLDOC/ MLDOCCCS allows storing both line item
and aggregated data.
o Periodic transactions (goods movements, activity confirmation, etc.)
update tables MLDOC/ MLDOCCCS with line item data using the
INSERT ONLY principle.
Page | 234
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Material Ledger Period Close creates (run-dependent) settlement records
in tables MLDOC/ MLDOCCCS to store the results from Actual Costing.
These records are stored under the costing run key (field ‘Run Reference’)
so that they are ‘visible’ only by the corresponding costing run. In this
way different runs (e.g. a periodic run and an AVR) can store their results
independently from each other.
o Important design changes
▪ Single- and multilevel differences are no longer distinguished. In
table MLDOC all price/exchange rate differences are stored in
fields PRD/KDM. In table MLDOCCCS the CCS for
price/exchange rate differences are stored under the CCS types E/F
(field MLCCT).
▪ The CCS is stored in a table format using the cost component (field
ELEMENT) as additional key. This allows increasing the number
of cost components without modification.
▪ The CCS for preliminary valuation is always stored
o
•
Tables MLDOC_EXTRACT and MLDOCCCS_EXTRACT
o The table MLDOC_EXTRACT holds information about quantity and
valuation changes. Transaction based updates, like goods movements or
invoice receipts, usually update tables MLDOC and MLDOC_EXTRACT
in parallel. But table MLDOC_EXTRACT can be compressed. After
compression, the table will contain only one entry per cost estimate
number, period and currency type valuation view. Table
MLDOC_EXTRACT allows fast and efficient calculation of total quantity
and total value, by cumulating all records for specific cost estimate
number(s). The same is true for table MLDOCCCS_EXTRACT which has
been designed for holding cost component information. During period
shift (transaction MMPV) the tables MLDOC_EXTRACT and
MLDOCCCS_EXTRACT will be compressed automatically for periods
older than previous period. Manual compression via program
FCML4H_RMLDOC_EXTRACT_COMPRESS or via function module
FCML4H_MLDOC_EXTRACT_COMPRESS is possible and
recommended in case of very high number of material movements.
•
Table MLRUNLIST
o Table MLRUNLIST replaces the former table CKMLMV011 (Object List
for Costing Run), but has some additional functions:
▪ Materials and activities selected for a costing run are stored under
the corresponding run id.
▪ It manages the period status of materials and activities
Page | 235
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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,
Page | 236
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
ML Actual Costing Cockpit (Transaction CKMLCPAVR):
•
•
•
•
•
•
•
•
In the transactions CKMLCP and CKMLCPAVR, there is an additional parameter
“Application”. This means that the application can be chosen so that it is possible
to process Alternative Valuation Runs via the transaction CKMLCP and Actual
Costing Runs via the transaction CKMLCPAVR.
In the toolbar of the transactions CKMLCP and CKMLCPAVR, there is a new
button next to the “Display <-> Change”-Button to switch the application from
“Costing Run” to “Run Reference” and back.
When the application is switched to “Run Reference”, a run reference can be
created, changed or displayed. A run reference is a reference that contains all
settings of an Alternative Valuation Run. It can be used when creating an
Alternative Valuation Run but it is only mandatory for creating Alternative
Valuation Runs for Parallel COGM. It can also be created for a single period run,
for year-to-date run or for a rolling run.
There are 2 options for creating an AVR:
o Create a “Classic AVR” which is the same like before.
o Create an AVR with run reference which means the settings are taken
from the run reference and 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:
o Selection (program FCML4H_SELECTION)
o Preparation (program FCML4H_PREPROCESSOR)
o Settlement (program FCML4H_SETTLEMENT)
o Post Closing (program FCML4H_POST_CLOSING)
It is no longer possible to use delta posting runs.
Additionally to the status of the materials, the status of the activity types is
displayed in the section “Processing”. The button “Activity Types” for displaying
the activity types value flow has been removed.
The section “Costing Results” has been removed. It will be replaced by the report
FCML4H_RUN_DISPLAY_MATERIALS that displays a material list with
status. It will called via the button “Results” in the section “Processing”.
Page | 237
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
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):
o The new AVR do no longer copy the data into a separate key area. (Only
the settlement records are stored under the AVR ‘Run Reference’, see
above). In particular,
the cumulation of several period is done ‘On-the-fly’.
o The former step Cumulate Data is no longer needed
o The complex rescale logic, which adjusts all materials data to a common
preliminary AVR price, is no longer needed.
o All AVR can now handle WIP
o Post Closing:
▪ Post Closing uses a ‘push logic’ (in accordance to the new
Settlement). This means that the price differences rolled from an
input to the output are now posted
in the closing document of the input (material/activity)
▪ For activity types (and business processes) a new posting has been
introduced. See the documentation in transaction OBYC for the
new transaction key PRL:
Price differences for activity types or business processes. During
settlement in the material ledger, these price differences are posted
from cost centers
(Transaction/Account Modification GBB/AUI) to the material
ledger (transaction PRL) and then further allocated to the
receivers (finished products/WIP).
Page | 238
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Restrictions
•
•
•
•
•
AVR Delta Posting Logic is not available
External Ending Inventory Valuation and Cumulated Inventory Valuation are
currently not available
The BAdI CKMLAVR_SIM is currently not available
Material Ledger Costing Runs and Alternative Valuation Runs, which have been
created before the system conversion cannot be changed nor reversed any more
after the conversion to SAP S/4HANA
Material Ledger Valuated Quantity Structure (Transaction CKMLQS) is 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
12.4 S4TWL - TECHNICAL CHANGES IN CONTROLLING
Application Components:
CO-PA, CO-PC, 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
Page | 239
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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, socalled 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
Page | 240
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.5 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.
Page | 241
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Reason and Prerequisites
This Simplification Item is relevant if:
•
•
•
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
Solution
Business Value
The universal journal is the unifying element for Accounting. 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 With the new approach
it is possible to move many planning tasks back into SAP S/4HANA, reducing
complexity and total cost of ownership. Where additional flexibility is required (for
example to build a model to calculate headcount costs), it is possible to extend the
planning model using SAP BPC tools to get the best of both planning approaches. 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). Plan/actual
reporting is provided by comparing the entries in the two tables. Integration to SAP
Analytics Cloud is also via the new table.
Description
CO-OM planning, P&L planning, and profit center planning are now covered by SAP
BPC for S/4HANA Finance (formerly known as Integrated Business Planning) (SAP
Note 2081400). If you do not want to use SAP BPC for S/4HANA but classic FI-GL and
CO-OM planning functions instead, you 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.
•
•
•
FI-GL Planning - SAP Note 2253067 describes how to reactivate
Profit Center Planning (classic) - SAP Note 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
Page | 242
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
Order Planning by Cost Element - no longer in menu but can be used in SAP S/4
HANA
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 required to activate SAP BPC for S/4HANA Finance and adapt the
delivered queries to customer needs. Customers preferring to delay such a project can
reactivate the classic planning transactions using the SAP Notes described above.
Note that it is also possible to run the two solutions in parallel. SAP Note 2061419
describes how to retract data from SAP BPC for S/4HANA Finance into the totals tables
so that this data can be used as a basis for cost center allocations and activity price
calculation and order/project budget setting and settlements and to extract the data back
to SAP BPC for S/4HANA Finance so that it is available for reporting when the planning
cycle is complete.
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).
Business Process related information
If SAP BPC for S/4HANA Finance is desired or required, then SAP BPC for S/4HANA
Finance has to be set up (SAP Note 2081400). Implications:
•
•
•
•
•
•
Customer roles (menus and authorizations) may need to be adapted.
Decision needed as to whether plan/actual reporting will be based on totals tables
or take place using SAP S/4HANA Finance reports
Decision needed as to whether planning data is needed for follow-on processes in
S/4HANA Finance (e.g. target cost calculation for cost centers, project budgeting
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 frontends 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
Page | 243
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
knowledge base article for further details.
https://launchpad.support.sap.com/#/notes/2162222
Transactions which GP12N, GP12NA, FAGLP03 (plan data entry in FI) plus plan
have been removed
assessment cycles (FAGLGA4* transactions) and plan
from the menu in SAP distribution cycles (FAGLGA2* transactions)
S/4HANA on-premise
edition 1511
CJ40/CJ42 (overall planning on projects) KP06/KP07 (cost
centre planning), CJR2/CJR3 (project planning) and
KPF6/KPF7 (order planning)
7KE1-6 and 7KEP (profit center planning), IKE0 (transfer COOM plan to profit center plan)
Required and Recommended Action(s)
•
•
•
•
Decision needed concerning scope of existing planning processes, requirements
for plan/actual reporting and ability to use delivered business content for SAP
BPC for S/4HANA Finance.
Activate SAP BPC for S/4HANA Finance and compare against project needs.
No changes to existing tables, but table ACDOCP offered in addition from 1610.
Instead new business content for SAP BPC for S/4HANA Finance must be
activated as described in SAP Note 2081400.
Follow steps in Installation Guide provided with SAP Note 1972819. Explore
SAP BPC functions to extend scope (e.g. use of business process flows)
Related SAP Notes
Conversion Pre-Checks
Related SAP Notes
Please check scope of existing planning activities and
determine whether they can be covered using the business
content currently available for SAP BPC for S/4HANA
Finance. If you are currently using activity price calculation to
set activity rates or Investment Planning, you can still use
Integrated Business Planning for Finance but will need to
retract the results to tables COSP_BAK, COSS_BAK to
perform the follow-on processes. If you are using costingbased CO-PA the table structure will remain unchanged and
there will be no loss of functionality.
SAP Note: 2081400, 1972819
Page | 244
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
ACDOCP
12.6 S4TWL - 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.
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".
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
Page | 245
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 246
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
For this reason transaction CPV5 has been replaced by KSV5
(distribution), transaction CPP5 by KSU5 (assessment),
transaction CPC5 by KSC5 (indirect activity allocation). 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 have
been disabled. Please contact SAP support for further details.
Required and Recommended Action(s)
Activate Operational Activity Based Costing. Check existing roles and adjust assigned
transactions if necessary.
Related SAP Notes
Conversion Pre-Checks Check controlling area settings in customizing to determine the
type of Activity Based Costing which is active. Check version
settings in Customizing to determine whether there are CO
versions other than version 0 that contain actual data.
Other Terms
Activity Based Costing (CO-OM-ABC)
12.7 S4TWL - GENERAL COST OBJECTS AND COST OBJECT
HIERARCHIES
Page | 247
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 248
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
KKC1, KKC2, KKC3 - Create, change and display general cost
available in SAP
object
S/4HANA onpremise edition 1511 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
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
Page | 249
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 CKMATDUV.and
CKACTDUV instead)
KKPY -.Actual Cost Distribution: Cost Objects (consider using
distribution of usage variances instead)
KKAO, KKAV - WIP Calculation for cost object hierarchies
KKP5, KKPT - Variance calculation for cost object hierarchies
BAPI_COSTOBJECT_GETDETAIL and
BAPI_COSTOBJECT_GETLIST
Required and Recommended Action(s)
Do not activate Cost Objects in controlling area. Do not build a data model that requires
use of general cost objects or cost object hierarchies.
Investigate alternative solutions outlined above if you are using cost objects or cost object
hierarchies as you move to SAP S/4HANA.
Adjust roles and authorizations to remove deprecated transactions.
12.8 S4TWL - TRANSFER PRICES/ PARALLEL DELTA VERSIONS
Application Components:
CO-PA
Page | 250
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 251
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 252
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.9 S4TWL - COST ELEMENTS
Application Components:
CO-PA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270419
S4TWL - Account/Cost Element
Page | 253
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 254
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
Controlling-area-specific area - Contains data that may vary from one controlling
area to another, such as the cost element category. Only needed for accounts of
the type Primary Costs or Revenue and Secondary Costs.
Default account assignments for cost elememts can be set in transaction OKB9 rather
than in the cost element master. 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 changes
(updated under secondary cost elements). Please adjust financial statement versions
accordingly.
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
Page | 255
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
activity allocations, settlement, and so on). Intercompany postings originating in
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.10 S4TWL - Reporting/Analytics in Controlling
Application Components:
CO-OM-IS, CO-PA-IS, CO-PC-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349297
S4TWL - Reporting/Analytics in
Controlling
Symptom
Page | 256
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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, and in some
cases the embedded BW content within SAP S/4HANA to enable these reports. There are
Fiori apps for reporting on cost centers, internal orders, projects, and sales order items.
The account structure for these reports can be based on the financial statement version or
on the cost element groups. For cost centers, internal orders, and projects you can
distinguish between real and statistical postings in reporting. A new field has been
Page | 257
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
introduced to the universal journal that represents the old CO object number and works
using a 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 and you will need to activate the
appropriate planning applications and BW content. 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.
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.
There are Fiori apps for reporting on market segments based on the account-based
approach. Plan/actual reporting here is also based on SAP BPC and you will need to
activate the appropriate planning applications and BW content. SAP S/4HANA includes
new functions allowing you to derive the market segments at the time of postings to cost
Page | 258
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
show the costs and revenues by G/L account and account assignment. If you select the
Page | 259
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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), CO01CO03 (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.
12.11 S4TWL - 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 any type of 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
Business Value
The universal journal (ACDOCA) is the heart of Accounting and includes all Profitability
Analysis (CO-PA) characteristics in order to allow multi-dimensional reporting by
Page | 260
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
market segment. The universal journal includes columns for the standard CO-PA
characteristics and all additional characteristics included in an organization’s operating
concern (up to fifty characteristics). If you have already configured an operating concern,
columns will be created for each of the CO-PA characteristics during migration.
The benefit of this approach is that all revenue and cost of goods sold postings are
automatically assigned to the relevant CO-PA characteristics at the time of posting and
that allocations and settlements are made to the CO-PA characteristics at period close. It
is also possible to configure some expense postings such that the CO-PA characteristics
are derived automatically, so that material expenses assigned to a WBS element (account
asssignment) are automatically assigned to the CO-PA characteristics definied as
settlement receivers for the WBS element. This automatic derivation of the CO-PA
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.
There are also no reconciliation issues between the general ledger and Profitability
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 Profitability Analysis for which no revenue has yet
been posted (matching principle). An approach to delay the cost of goods sold posting
until the invoice is available is planned.
If you have worked with account-based CO-PA in SAP ERP, you no longer need to
reduce the number of characteristics available in account-based CO-PA compared to
costing-based CO-PA, but can include all available characteristics in the universal
journal. It is not possible to use more than 50 characteristics in one operating concern.
Business Process related information
If you currently work with costing-based CO-PA, you can continue to run both
approaches in parallel, by making the appropriate settings per controlling area. The
essential difference is that costing-based CO-PA is a key figure based model, rather than
an account-based model. Account-based CO-PA covers record types F (billing
documents, B (direct FI postings), C (settlement) and D (assessment) in costing-based
CO-PA.
There is no direct migration from costing-based CO-PA to account-based CO-PA. Please
bear in mind the following general principles as you consider a conversion:
•
Revenues and sales deductions are included in CO-PA whenever the price
conditions are mapped to an account. Statistical price conditions are included
from SAP S/4HANA 1809 (or 1808 cloud edition).
•
Cost of goods sold (COGS) postings are captured at the time of the goods issue
from the warehouse. New functions are available to split the COGS posting to
Page | 261
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
multiple accounts in accordance with the relative weight of the assigned cost
components. Functions to support the matching principle between revenues and
COGS are planned.
•
Production order variances can be split to multiple accounts to separate scrap,
price variances, quantity variances, and so on.
•
Assessment cycles and settlement will update under secondary cost elements.
Depending on how many value fields you used before, you may need to define
additional cost elements and adjust your cycles/settlement profiles to give you the
required detail.
•
You may be able to replace some assessment cycles and settlements by having the
system derive the CO-PA characteristics at the time of posting instead of moving
them from the cost center, order or project at period close.
•
Top-down distribution works in account-based CO-PA, but you must include the
account/cost element in the selection criteria.
•
New fields are included in the universal journal for the invoice quantities. BADIs
can be used to convert e.g. the quantity from the invoice to a base unit of measure
and from there to a reporting unit. Note that only three additional quantity fields
are supported, though convertible quantities (e.g. grams to kilograms) can be
handled in the same field.
All transactions available, but some
Transaction not available in SAP S/4HANA
transactions (e.g. KE27) only
on-premise edition 1511
support costing-based CO-PA.
Required and Recommended Action(s)
Analyze existing reporting requirements to understand how market segment reporting is
handled today. Also include transfer of profitability information to other systems,
including data warehouses.
If costing-based CO-PA is currently used, analyze what workarounds are being used to
reconcile the profit and loss statement with costing-based CO-PA to determine whether
these will be required in the future.
Other Terms
Account-based CO-PA
Page | 262
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
13 Financials - General Ledger
13.1 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.
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
Page | 263
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
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 nonproductively 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
Page | 264
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Carry Forward has slightly changed. Please make yourself familiar with the new handling
of them in NewGL before the Migration.
13.2 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
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
Page | 265
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
13.3 S4TWL - Closing Cockpit with S/4 HANA OP
Application Components:
FI-GL-GL-G
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
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. See SAP note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, onpremise edition. Thus transaction codes CLOCO, CLOCOC and CLOCOS are
supported but are part of compatibility scope in S/4HANA OP. 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
Page | 266
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
If any of the Business Functions listed above are active, consider to use the AddOn Financials Closing Cockpit 2.0 instead.
Other Terms
SYSTEM_ABAP_ACCESS_DENIED
13.4 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.
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.
Page | 267
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 S/4H
Finance 1605)
ACDOCA
Fieldname
Description
WSL
Amount in Transaction
Currency (Document
Currency)
Original currency of the transaction, not
contained in balances, as it might happen
that different currencies cannot be
aggregated; corresponds to BSEG-WRBTR.
TSL
Amount 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 BSEGPSWBT.
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
Page | 268
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Object currency of CO, only if it is really the
of CO
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.
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 (or S/4H Finance 1605) we achieved the following
coverage:
HSL KSL OSL VSL BSL CSL DSL ESL FSL GSL
Example configuration
Page | 269
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Universal Journal
(ACDOCA)
10
30
40
BSEG and Fixed Asset
Accountning
10
30
40
Material Ledger
10
30
40
Controlling
10
30
Realtime Currency
Conversion
X
X
Balance zero per Journal
Entry
X
Open Item Management
(FI-AP, FI-AR, FI-GL)
Foreign Currency
Valuation
50
60
Z1
Z2
Z3
Z4
Z5
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
1
1
1
1
1
1
1
GL and CO Allocations
(Assessment and
Distribution)
X
X
X
X
X
X
X
X
X
X
Fixed Asset Accounting
X
X
X
1
1
1
1
1
1
1
Material Ledger
X
X
X
1
1
1
1
1
1
1
CO Settlement
X
X
1
1
1
1
1
1
1
1
CO Reposting
X
X
1
1
1
1
1
1
1
1
Supported Processes
(for example config.)
Regrouping
This means that all journal entry items are converted in the accounting interface for all
configured currencies, regardless of the source where the business transaction originates
from. In the accounting interface the journal entry is converted according to the
conversion settings in tx FINSC_LEDGER (exchange rate type, ....), and balance zero per
journal entry is guaranteed.
Some processes require more that a mere document wise currency conversion with the
current rate. These processes require that the amounts are converted with rates of
the historical data being processed. This is not yet supported for all processes. We
achieved this for open item management in FI-AP, 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.
Page | 270
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Overview on supported reporting for currency fields
With S/4H 1610 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.
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.
Page | 271
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.
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.
13.5 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
Page | 272
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
•
•
•
•
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):
1. 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
Page | 273
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
2. 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.
3. After the customizing transport was imported in the productive system, you need
to execute the mass data project in the productive system also.
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 presentation.
Other Terms
ACE, ACAC.
Page | 274
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
13.6 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
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
o Decoupling
o Code Adaptation
o Storage of an Amount on the Database
o Internal Interfaces
o Write To List
o Strict Type Checks
o External Interfaces
System Settings to Activate the Provided Amount Field Length Extension in
Customizing
Functions that may use the Provided Amount Field Length Extension
Page | 275
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Change Log
Date
Description
Link to download ZIP file containing preliminary simplification database. Refer
note 2659194
22nd
June
2018
Please be aware this ZIP file is not yet the final version, so please disregard
findings that are reported relating to other simplification topics than Amount
Field Length Extension (AFLE). Furthermore this information is not intended
for distribution so please treat it as confidential, especially don’t forward the
contents.
Introduction
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
Page | 276
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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:
1. 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.
2. 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.
3. 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
Page | 277
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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,
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
Page | 278
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 279
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 nonSAP) 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.
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
Page | 280
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 281
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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)
Page | 282
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 283
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
14 Financials - International Trade
14.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 commodiy codes in transaction MM01 / MM02.
This functionality (material classification with commodity codes) is redesigned in SAP
S/4HANA 1610. Following redesign apply:
1. Management of commodity codes
-
Old in ECC and S/4HANA 1511: not time-dependent, valid for a country
New in S/4HANA 1610 onwards: time-dependent, valid for a country or multiple
countries, new app, new data model
2. Classification of materials with commodity codes
Old in ECC and S/4HANA 1511: not time-dependent, valid for material and plant,
done in material master apps (e.g. MM01, MM02)
New in S/4HANA 1610 onwards: time-dependent, valid for material and a country
or multiple countries, new FIORI apps, new data model
Reason and Prerequisites
Upgrade or conversion to SAP S/4HANA 1610 or later release
Solution
Page | 284
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Before conversion you can run the pre-check report to check if there is inconsistent
data. Inconsistent data is not taken over in new data model. If there is inconsistent data,
you can check and correct it (Details in note 2332472) before conversion is triggered.
During upgrade to S/4HANA 1610, a XPRA - /SAPSLL/XPRA_1610_MARC_STAWN
- migrates classification data to new data model.
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)
•
Knowledge transfer to key and end users
Other Terms
Material classification with commodity codes, International Trade, STAWN.
14.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
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
Page | 285
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.)
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.
14.3 S4TWL - Determination of default values in Intrastat reporting
Application Components:
SD-FT-GOV, SLL-ITR-ISR
Related Notes:
Page | 286
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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:
1. 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.
2. 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. 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.
3. 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:
Page | 287
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. 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).
2. Allow the definition of defaults values for receipts and returns to supplier in
intercompany sales that is valid for all country combinations and without
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:
Page | 288
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
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:
1. 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)
2. 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)
3. 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)
4. 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, 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
Page | 289
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
15 Financials - Treasury and Risk Management
15.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
Page | 290
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
FTI_TR_PL_CF
Treasury: Revenue and Cash Flow Reporting
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
15.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
Page | 291
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
15.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
Page | 292
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
S4TC, S/4 Transition
15.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
15.5 S4TWL - Quantity Ledger Always Active for Money Market
Transactions
Application Components:
FIN-FSCM-TRM
Related Notes:
Page | 293
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 294
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 precheck 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
15.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
o Namespace of Financial Object: T2*
o Master Data Maintenance Transaction: JBWPORD
Page | 295
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
o
[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
o Namespace of Financial Object: B1*
o Master Data Maintenance Transactions: JBB0, JBB1. JBB2
o [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)
o Namespace of Financial Object: BV*
o Master Data Maintenance Transactions: JBVT*
•
Positions of Fictitious/Simulated Transactions
o Namespace of Financial Object: R3*
o Master Data Maintenance Transaction: RTBST
•
Facilities in SAP Banking
o Namespace of Financial Object: F2*
o Master Data Maintenance Transactions: KLFZ01, KLFZ02. KLFZ03
o [IMORTANT] This is to be distinguished from the facility instrument in
SAP Treasury and Risk Management (product category 560) which is
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
o Namespace of Financial Object: PL*
o 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.
Page | 296
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
15.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
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 S4WTL - 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.
Page | 297
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
S4TC, S/4 Transition
15.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
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)
Page | 298
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 are using old correspondence functionality and upgrade to SAP S/4HANA from an
older release in which the Correspondence Framework is technically not available, you
first need to upgrade to a release in which the Correspondence Framework is available
and activate the Correspondence Framework including necessary customizing creation
(which is an own project and needs time), before upgrading to SAP S/4HANA.
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
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 stop the error message by activating business function FIN_TRM_CORR_FW.
Other Terms
S4TC S/4 Transition
15.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
Page | 299
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 300
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
If you upgrade to S/4HANA from a release in which the yield curve framework is
technically available, SAP recommends that you activate the yield curve framework
before upgrading to S/4HANA.
If you upgrade to S4/HANA directly from an older release, in which the yield curve
framework is not yet available, you have to perform the migration to the yield curve
framework in S4/HANA before you can continue using yield-curve related functionality,
such as the calculation of NPVs with transaction TPM60.
Refer to note 1873119 and its related notes for more information on the yield curve
framework.
The pre-upgrade-check for S4/H transition issues a warning with check ID SI5_YCF if at
least one client exists in the system in which the yield curve framework is not active, or if
the system is on a release level in which the yield curve framework is not yet technically
available. (Clients 000 and 066 are exempt from the check.)
How to Determine Relevancy
Use transaction SFW_BROWSER to check the activation status of object
FIN_TRM_YCF .
If the business function is not activated, the classical interest rate and yield curve
functionality is active.
If the business function is activated, use transaction SPRO to check the status of the
following customizng activity:
Financial Supply Chain Management -> Treasury and Risk Management -> Basic
Functions -> Market Data Management -> Settings for Ref. Interest Rates and Yield
Curves -> Activate Yield Curve Framework
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.
15.10 S4TWL - Accrual/Deferral of Expenses and Revenues
Application Components:
FIN-FSCM-TRM
Related Notes:
Note Type
Note Number
Note Description
Page | 301
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Required and Recommended Action(s)
If you are upgrading from SAP Enhancement Packages >= 3 for SAP ERP 6.0 (EAFINSERV 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 (EAFINSERV 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.
Page | 302
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 you now 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
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 precheck raises a skippable message with check id SI3_ACCR (message ‘Conversion
required. See SAP note 2270462.’). 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
15.11 S4TWL - 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
Page | 303
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
15.12 S4TWL - Exposure Management 1.0
Application Components:
FIN-FSCM-TRM
Page | 304
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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,
Page | 305
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
15.13 S4TWL - 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.
Page | 306
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
S4TC, S/4 Transition
Page | 307
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
16 Financials – Miscellaneous
16.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:
A. You are only using FI-AR-CR Credit Management in your source release
B. You are only using SAP Credit Management (FIN-FSCM-CR) in your source
release
C. You are using both Credit Management solutions (FI-AR-CR & FIN-FSCM-CR)
in your source release
D. 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
Page | 308
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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”.
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)
Page | 309
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information:
A & C: You need to migrate FI-AR-CR to FIN-FSCM-CR. The migration from onesystem 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. To use
transaction UKM_MY_DCDS, the credit specialist might
need additional authorizations. As a workaround, the
transactions VKM1 and VKM4 are still available.
Transactions not available F.28 - Customers: Reset Credit Limit
in SAP S/4HANA
F.31 - Credit Management - Overview
F.32 - Credit Management - Missing Data
F.33 - Credit Management - Brief Overview
F.34 - Credit Management - Mass Change
FCV1 - Create A/R Summary
FCV2 - Delete A/R Summary
FCV3 - Early Warning List
FD24 - Credit Limit Changes
FD32 - Change Customer Credit Management (but FD33
still available for Migration checks)
FDK43 - Credit Management - Master Data List
S_ALR_87012215 - Display Changes to Credit Management
S_ALR_87012218 - Credit Master Sheet
VKM2 - Released SD Documents
VKM3 - Sales Documents
VKM5 - Deliveries
Reports not available in
RFARI020 - FI-ARI: Extract from credit master data
SAP S/4HANA
RFARI030 - FI-ARI: Import credit master data
RFDFILZE - Credit Management: Branch/Head Office
Reconciliation Program
Page | 310
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 311
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
You have completed the migration for Accounting.
If you are running on your own code, you have eliminated the usage of SAP
objects in your own code. For details on how to adapt user-defined customer code
that relies on the changed objects, see the following SAP Notes:
o 2227014 (Financials)
o 2227014 (SD)
2. Perform the recommended actions in the Task List PDF attached to this Note (only
available in English). This list is only valid for the conversion of one-system landscapes.
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)
Custom code-related information
(Financials)
SAP Note: 2217124
SAP Note: 2227014
16.2 S4TWL - Technical Changes in Material Ledger
Application Components:
CO-PC-ACT
Related Notes:
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.
Page | 312
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
o CKMLPP “Material Ledger Period Totals Records Quantity”
o CKMLCR “Material Ledger: Period Totals Records Values”
o Access function: CKMS_PERIOD_READ_WITH_ITAB
Material Ledger Document and associated views
o MLHD
o MLIT
o MLPP
o MLPPF
o MLCR
o MLCRF
o MLCRP
o MLMST
o Access functions: CKML_F_DOCUMENT_READ_MLHD,
CKML_F_DOCUMENT_READ_MLXX
o Further tables (with no access function): MLKEPH, MLPRKEKO,
MLPRKEPH
o Obsolete database views: MLXXV, MLREPORT, MLREADST
Index for Accounting Documents for Material
o CKMI1
o Obsolete, no further access possible
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
Page | 313
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
leading ledger in Financials.
There is no default Material Ledger Type “0000” anymore.
Customizing in Financial applications allows you to assign more than three
currency and valuation types as being relevant in your company code. As the
Material Ledger still supports only three currency and valuation types, it is no
longer allowed to use an ML Type that references currency settings defined in FI
or CO (flags “Currency Types from FI” and “Currency Types from CO”). Instead
you have to explicitly define the currency and valuation types that are relevant for
the Material Ledger.
Steps to be executed:
1. Use transaction OMX2 to define the currency and valuation types that are
relevant for the Material Ledger.
2. Then use transaction OMX3 to assign this ML Type to your valuation area.
•
•
See also note https://i7p.wdf.sap.corp/sap/support/notes/2291076
Material Price Analysis (transaction CKM3 / CKM3N)
The transaction CKM3/CKM3N was refactored and now provides a simplified
and improved view of materials in plants with active Actual Costing. It replaces
the former CKM3 view Price Determination Structure.
The former CKM3 Price History view is still available via transaction CKM3PH
for all materials (independent of price determination control and active Actual
Costing).
All other views formerly offered by CKM3/CKM3N are no longer available.
For details about new Actual Costing simplification, please check the
corresponding upgrade information SAP Note.
Other Terms
ML, Document, CKMB, CKM3, Period Totals, LBKUM, SALK3
16.3 S4TWL - Real Estate Classic
Application Components:
RE-BD, RE-BP, RE-RT, RE-IT, RE-TP, RE-CP, RE-CO, RE-PR, RE-
IS, FS-CML
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.
Page | 314
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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 onpremise 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
16.4 S4TWL - SAP Data Aging for SAP S/4HANA Finance
Application Components:
FI-GL-GL
Related Notes:
Page | 315
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note Type
Note Number
Note Description
Business Impact
2170722
Overview: SAP Data Aging for SAP Simple
Finance
Symptom
You want to use SAP Data Aging for SAP Simple Finance. Beforehand, various matters
must be noted. They are described in SAP Notes. This SAP Note provides an overview
and specifies specific SAP Notes that give further details.
Reason and Prerequisites
This SAP Note is relevant if you carry out a migration from ECC 6.0 (EHP 7+) or
already use SAP S/4HANA Finance, on-premise edition and want to restrict the data
volume in the FI document area. In this case, you can use SAP Data Aging.
Solution
You must note the following things or implement the corresponding corrections:
•
•
•
•
•
•
Adjustment of the customer programs during an access to aggregates and application
indexes for Financial Accounting (SAP Note 2076652). The following adjustments are
required for all SAP Simple Finance releases. SAP standard programs are adjusted with the
delivery of SAP Simple Finance 1.0.
Adjustment of customer programs during access to the general ledger view in conjunction
with the entry view (SAP Note 2143420). The described adjustments are required only if
you have already moved FI documents to the historic part of the database for SAP Simple
Finance 1.0 and if you use SAP Simple Finance 1503 or above. Adjustments to SAP
standard programs were delivered with SAP Note 2164573.
Adjustment of customer programs during access to CO/ML/AA data from the database in
conjunction with archived data (SAP Note 2170778 for CO, SAP Note 2190816 for ML, SAP
Note 2190818 for AA). This is required as of SAP Simple Finance 1503. Adjustments to SAP
standard programs were not required.
Adjustment of customer programs during access to old CO/ML data. In addition to the
archive, data in the historic area of the database is accessed. Consulting note 2190841 and
SAP Note 2175897 are available for SAP standard programs.
Adjustment of aging object FI_DOCUMENT for journal entry. SAP Note 2178388 is a
prerequisite for the use of the aging run as of SAP Simple Finance 1503.
Adjustment of existing archiving. With SAP Simple Finance 1503, some tables are no
longer archived or are only written to the archive as copies. This is due to the fact that this
information is now persisted in the journal entry. A further consequence of this and of the
migration to the new persistence is restricted reload options for archiving objects that
offer these.
Page | 316
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
For some adjustments, corrections were necessary after the delivery of the release. These are
listed in case they are suitable for use as templates for your own corrections. Note that pure
corrections are not collected here.
The FAQ note 2190848 for SAP Data Aging in SAP Simple Finance is also available.
Other Terms
SAP Simple Finance, SAP Data Aging
16.5 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
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)
Page | 317
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
o
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.)
o
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.)
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 process of migrating the material ledger consists of the following activities in the
Start and Monitor Migration activity:
o
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
Page | 318
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
previous year are converted into material ledger currencies using the standard exchange
rate type. 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:
Table Name
Description
Replacement for
Purpose
Remark for
Migration
MLDOC
Material
Ledger
Document
MLHD, MLIT,
MLPP, MLPPF,
MLCR, MLCRF,
CKMLPP,
CKMLCR, MLCD,
CKMLMV003,
CKMLMV004,
CKMLPPWIP etc.
Optimized data
structure for ML
actual costing. Will
be filled during
transactional update
of ML data and
during ML
settlement.
During step M10,
data in MLDOC is
created from the
last period of the
previous year to the
current period for all
valuation areas
where actual
costing is activated.
MLDOCCCS
Material
Ledger
Document
Cost
Component
Split
MLKEPH,
CKMLKEPH,
(CKMLPRKEKO)
Optimized data
structure for cost
component split in
ML actual costing
During step M10,
cost component
split data are
created based on
MLDOC entries.
MLDOC_EXT Extract of
RACT
Material
Ledger
Document
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_MLDOC_
EXTRACT_COMP
RESS.
During migration,
one entry is created
for each
combination of cost
estimate number,
currency type,
period, category,
and process
category.
MLDOCCCS
_EXTRACT
-
Similar to
MLDOC_EXTRACT
but with information
per cost component.
Tables
Extract of
Material
Ledger
Document
Cost
Page | 319
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Component
Split
MLRUNLIST
Object List
for Costing
Run
MLDOC_EXTRACT
and
MLDOCCCS_EXTR
ACT will be used
especially to
calculate
information about
beginning inventory
in specific period, by
cumulating
quantities and
values from all
previous periods.
CKMLMV011,
status in CKMLPP
Information about
status of materials
and activity types in
ML costing runs
During migration,
table MLRUNLIST
is filled based on
costing runs created
in the start release.
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
Page | 320
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
transaction GBB, make sure to create an account assignment entry for General
Modification AUI and Valuation Class <blank> also.
▪
Transactions PRV and KDV:
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.
o
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.
o
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.
o
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:
o
Inventory valuation tables: MBEWH, EBEWH, QBEWH, OBEWH
o
Material ledger inventory tables (only relevant if material ledger was
active before SAP S/4HANA migration): CKMLPP, CKMLCR
Page | 321
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
o
Purchase order history tables: EKBE, EKBEH, EKBZ, EKBZH
o
Production order history tables: MLAUFCR, MLAUFCRH
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.
Other Terms
Migration On-Premise
16.6 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
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:
Page | 322
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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
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
Page | 323
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. Call up transaction SM30, enter view V_BPCONSTANTS and click Change.
2. Select constant 'FSDT' and enter constant value '1'.
3. 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
16.7 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
Page | 324
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 325
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
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
Page | 326
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 327
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
17 Human Resources
17.1 S4TWL - General HCM Approach within SAP S/4HANA
Application Components:
PA-BC, PY-XX
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, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
SAP SuccessFactors, the next generation HCM suite in the public Cloud, is the goforward HCM solution for both editions of SAP S/4HANA, cloud and on premise.
Productized integration exists today so customers can easily connect these solutions.
Customers choosing SAP S/4HANA as their next-generation business suite deserve a
next-generation HCM suite and this is the focus of SAP SuccessFactors. SAP
SuccessFactors connect easily with SAP S/4HANA with productized integration based on
HCI content.
Productized Integrations among SAP SuccessFactors with SAP S/4HANA on-premise
based on HCI content are available as of SAP S/4HANA, on-premise edition 1511. As of
August 2017, these productized integrations are utilizing a new configuration framework
for value mapping and value conversion, the so-called Business Integration Builder
(BIB). This configuration framework offers simplification how EC to ERP field mapping
can be handled for standard and custom infotypes instead of necessity to use custom
BAdI implementations. BIB is available with the integration add-on PA_SE_IN SP18.
Customers already using the integration between SAP S/4HANA and SAP
SuccessFactors based on BAdI implementations may continue to use it (until
SPxx???). These S/4HANA customers will not be able to apply latest PA_SE_IN SPs and
utilize features provided. Future enhancements will only be provided for BIB-based
integration.
Page | 328
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
Net new SAP S/4HANA customers (for all releases starting from 1511 OP
editions) as of October 2017 are recommended to only use BIB-based integration
between SAP S/4HANA and SAP SuccessFactors Employee Central
Customers already productively using the integration between SAP S/4HANA
and SAP SuccessFactors Employee Central prior to PA_SE_IN SP 18 (based on
BAdIs) may continue to use it but should plan implementation of integration
based on BIB
Customers performing system conversions from SAP ERP to SAP S/4HANA and
being already productive with SAP SuccessFactors Employee Central Integration
prior to PA_SE_IN SP 18 (based on BAdIs) should plan implementation of
Integration based on BIB. Implementation of BIB can either be done while still on
SAP ERP and before the system conversion to SAP S/4HANA or after the system
conversion to SAP S/4HANA
SAP S/4HANA customers may also using SAP ERP HCM on-premise and might not be
willing/able to move to SuccessFactors in the near term and like to continue to use SAP
ERP HCM. SAP HCM can be run in either a separate instance or single instance with
SAP S/4HANA. The integration among both on-premise instances (SAP HCM with SAP
S/4HANA on-premise) will be available via ALE in case SAP HCM is running on
separate instance. In case SAP HCM is running inside of SAP S/4HANA on-premise
then the integration is automatically given as part of so-called Compatibility Mode.
Business Process related information
When using S/4HANA and SAP HCM in one system (Compatibility Mode), then only
the Software components SAP-HR and EA-HR are still available in SAP S/4HANA.
The go-to architecture in the HCM area is SAP SuccessFactors, in particular SAP
SuccessFactors Employee Central for Core HR, SAP SuccessFactors Learning for
Learning, and SAP SuccessFactors Recruiting Management for Recruiting.
Limited application simplifications for traditional SAP HCM functionalities are planned
(continuous improvements for SAPGui-based functionality, HR Renewal, Fiori Apps),
available for both SAP HCM standalone and SAP HCM and SAP S/4HANA in one
system.
Required and Recommended Action(s)
The go-to architecture in the HCM area is SAP SuccessFactors. Accordingly it is
recommended to move the human resources-related functionalities to SAP
SuccessFactors.
Page | 329
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
As of October 2017, it's recommended for all customers using SAP SuccessFactors
Employee Central to SAP S/4HANA integration to be implemented based on BIB.
17.2 S4TWL - Conversion of Employees to Business Partners
Application Components:
PA-BC, PY-XX
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
SuccessFactors, the next generation HCM suite in the public Cloud, is the go-forward
HCM solution for both editions of SAP S/4HANA, cloud and on premise. Productized
integration exists today so customers can easily connect these solutions. Customers
choosing SAP S/4HANA as their next-generation business suite deserve a nextgeneration HCM suite and this is the focus of SuccessFactors. SuccessFactors connect
easily with SAP S/4HANA with productized integration based on HCI content
Productized Integrations among SuccessFactors with SAP S/4HANA on-premise based
on HCI content are available with SAP S/4HANA, on-premise edition 1511, and
onwards.
SAP S/4HANA customers may also using SAP ERP HCM on-premise and might not be
willing/able to move to SuccessFactors in the near term and like to continue to use SAP
ERP HCM. SAP HCM can be run in either a separate instance or single instance with
SAP S/4HANA. The integration among both on-premise instances (SAP HCM with SAP
S/4HANA on-premise) will be available via ALE in case SAP HCM is running on
separate instance. In case SAP HCM is running inside of SAP S/4HANA on-premise
then the integration is automatically given as part of so-called Compatibility Mode.
Business Process related information
Page | 330
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The new data model in S/4HANA is based on Business Partners (BP). A BP must be
assigned to each employee.
Required and Recommended Action(s)
After transformation to S/4HANA, the migration report
/SHCM/RH_SYNC_BUPA_FROM_EMPL must be executed before productive use of
the system. Due to customizing dependencies, the report cannot be executed in technical
downtime. That same report needs to be scheduled 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 is synchronized to the Business Partner automatically. The
synchronization is able to handle employees with single employments and single vendor
assignment only.
17.3 S4TWL - SAP Learning Solution
Application Components:
PE-LSO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2383837
S4TWL - SAP Learning Solution not
available in Compatibility Mode
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
SuccessFactors, the next generation HCM suite in the public Cloud, is the go-forward
HCM solution for both editions of SAP S/4HANA, cloud and on premise. Productized
integration exists today so customers can easily connect these solutions. Customers
choosing SAP S/4HANA as their next-generation business suite deserve a nextgeneration HCM suite and this is the focus of SuccessFactors. SuccessFactors connect
easily with SAP S/4HANA with productized integration based on HCI content
Productized Integrations among SuccessFactors with SAP S/4HANA on-premise based
on HCI content will be available with SAP S/4HANA, on-premise edition 1511.
Page | 331
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
SAP S/4HANA customers may also using SAP ERP HCM on-premise and might not be
willing/able to move to SuccessFactors in the near term and like to continue to use SAP
ERP HCM. SAP HCM can be run in either a separate instance or single instance with
SAP S/4HANA. The integration among both on-premise instances (SAP HCM with SAP
S/4HANA on-premise) will be available via ALE in case SAP HCM is running on
separate instance. In case SAP HCM is running inside of SAP S/4HANA on-premise
then the integration is automatically given as part of so-called Compatibility Mode.
Business Process related information
When using S/4HANA and SAP HCM in one system (Compatibility Mode), then only
the Software components SAP-HR and EA-HR are still available in SAP S/4HANA. SAP
Learning Solution can not be used in Compatibility Mode, only as a separate installation.
The go-to architecture in the HCM area is SuccessFactors, in particular SAP
SuccessFactors Employee Central for Core HR, SAP SuccessFactors Learning for
Learning, and SAP SuccessFactors Recruiting Management for Recruiting.
It´s not planned to provide application simplifications based on the traditional SAP HCM
functionalities. As example: It is not planned to offer Fiori-based user interfaces for these
traditional functionalities. SAPGui based functionality stay unchanged for those
customers unable to make the move to SuccessFactors in the near term.
Required and Recommended Action(s)
Customers running S/4HANA on premise, SAP HCM and SAP Learning Solution in one
system are required to do one of the following:
- Replace SAP Learning Solution with SuccessFactors Learning
- Carve out SAP HCM together with SAP Learning Solution and run it separate from
S/4HANA
- Carve out SAP Learning Solution and run it separated from S/4HANA and SAP HCM
(stand-alone SAP Learning Solution requires SAP HCM modules PA, OM, TM, so this
data needs to be duplicated and available in both SAP Learning Solution and SAP HCM)
17.4 S4TWL - SAP E-Recruiting
Application Components:
PA-ER
Related Notes:
Note Type
Note Number
Note Description
Page | 332
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Impact
2383888
S4TWL - SAP E-Recruiting not available in
Compatibility Mode
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
SuccessFactors, the next generation HCM suite in the public Cloud, is the go-forward
HCM solution for both editions of SAP S/4HANA, cloud and on premise. Productized
integration exists today so customers can easily connect these solutions. Customers
choosing SAP S/4HANA as their next-generation business suite deserve a nextgeneration HCM suite and this is the focus of SuccessFactors. SuccessFactors connect
easily with SAP S/4HANA with productized integration based on HCI content
Productized Integrations among SuccessFactors with SAP S/4HANA on-premise based
on HCI content will be available with SAP S/4HANA, on-premise edition 1511.
SAP S/4HANA customers may also using SAP ERP HCM on-premise and might not be
willing/able to move to SuccessFactors in the near term and like to continue to use SAP
ERP HCM. SAP HCM can be run in either a separate instance or single instance with
SAP S/4HANA. The integration among both on-premise instances (SAP HCM with SAP
S/4HANA on-premise) will be available via ALE in case SAP HCM is running on
separate instance. In case SAP HCM is running inside of SAP S/4HANA on-premise
then the integration is automatically given as part of so-called Compatibility Mode.
Business Process related information
When using S/4HANA and SAP HCM in one system (Compatibility Mode), then only
the Software components SAP-HR and EA-HR are still available in SAP S/4HANA. SAP
E-Recruiting can not be used in Compatibility Mode, only as a separate installation.
The go-to architecture in the HCM area is SuccessFactors, in particular SAP
SuccessFactors Employee Central for Core HR, SAP SuccessFactors Learning for
Learning, and SAP SuccessFactors Recruiting Management for Recruiting.
It´s not planned to provide application simplifications based on the traditional SAP HCM
functionalities. As example: It is not planned to offer Fiori-based user interfaces for these
traditional functionalities. SAPGui based functionality stay unchanged for those
customers unable to make the move to SuccessFactors in the near term.
Page | 333
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
Customers running S/4HANA on premise, SAP HCM and SAP E-Recruiting in one
system are required to do one of the following:
- Carve out SAP E-Recruiting and run it separated from S/4HANA and SAP HCM
- Carve out SAP HCM together with SAP E-Recruiting and run it separate from
S/4HANA
- Replace SAP E-Recruiting with SuccessFactors Recruiting Management
17.5 S4TWL - Java-Based ESS and MSS
Application Components:
PA-ESS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2383879
S4TWL - Java-based ESS and MSS not
available in Compatibility Mode
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
SuccessFactors, the next generation HCM suite in the public Cloud, is the go-forward
HCM solution for both editions of SAP S/4HANA, cloud and on premise. Productized
integration exists today so customers can easily connect these solutions. Customers
choosing SAP S/4HANA as their next-generation business suite deserve a nextgeneration HCM suite and this is the focus of SuccessFactors. SuccessFactors connect
easily with SAP S/4HANA with productized integration based on HCI content
Productized Integrations among SuccessFactors with SAP S/4HANA on-premise based
on HCI content will be available with SAP S/4HANA, on-premise edition 1511.
SAP S/4HANA customers may also using SAP ERP HCM on-premise and might not be
willing/able to move to SuccessFactors in the near term and like to continue to use SAP
ERP HCM. SAP HCM can be run in either a separate instance or single instance with
Page | 334
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
SAP S/4HANA. The integration among both on-premise instances (SAP HCM with SAP
S/4HANA on-premise) will be available via ALE in case SAP HCM is running on
separate instance. In case SAP HCM is running inside of SAP S/4HANA on-premise
then the integration is automatically given as part of so-called Compatibility Mode.
Business Process related information
When using S/4HANA and SAP HCM in one system (Compatibility Mode), then only
the Software components SAP-HR and EA-HR are still available in SAP S/4HANA.
Java-based ESS and MSS can not be used in Compatibility Mode, only the WebDynpro
ABAP-based ESS and MSS can be used.
The go-to architecture in the HCM area is SuccessFactors, in particular SAP
SuccessFactors Employee Central for Core HR, SAP SuccessFactors Learning for
Learning, and SAP SuccessFactors Recruiting Management for Recruiting.
It´s not planned to provide application simplifications based on the traditional SAP HCM
functionalities. As example: It is not planned to offer Fiori-based user interfaces for these
traditional functionalities. SAPGui based functionality stay unchanged for those
customers unable to make the move to SuccessFactors in the near term.
Required and Recommended Action(s)
Customers running S/4HANA on premise, SAP HCM and Java-based ESS and MSS in
one system are required to do the following:
- Replace Java-based ESS and MSS with WebDynpro ABAP-based ESS and MSS
17.6 S4TWL - SAP Travel Management
Application Components:
FI-TV
Related Notes:
Note Type
Note Number
Note Description
Page | 335
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
18 Logistics – General
18.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 currently not
released for S/4 HANA 1809 SP00. It is planned to be available for S/4 HANA 1809 OP
at a later service pack level.
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.
Other Terms
ECC, S4HANA, Pre-Check, Simplification
Page | 336
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
18.2 S4TWL - Season Field Length Extension
Application Components:
LO-RFM, LO-RFM-CA
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
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 or
SAP Master Data Governance Retail and Fashion Management extension by Utopia 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 (CrossApplication Components -> General Application Functions -> Activate Extended Fields).
Page | 337
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
For further information regarding integration in a solution landscape, and how to adjust
customer specific coding, please see attached not.
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
Page | 338
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
19 Logistics – AB
19.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
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
Page | 339
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Obsolete
Report
Report Title
RWLF1001 Billing docs
(header data)
Successor Tcode
RWLF1002
WLI2
RWLF1003
RWLF1004
RWLF1005
RWLF1006
RWLF1007
RWLF1008
Obsolete Successor Successor Report
Tcode
Report
Title
WLFB
RWLF1051 List Output
Settlement
Management
Documents
Billing
WLFC
RWLF1051 List Output
documents (with
Settlement
item data)
Management
Documents
Settlement
WLFD
RWLF1051 List Output
Document Lists
Settlement
(Header
Management
Information)
Documents
Settlement
WLFE
RWLF1051 List Output
Document Lists
Settlement
(With Item Data)
Management
Documents
Settlement
WLFG
RWLF1051 List Output
Requests
Settlement
(Header
Management
Information)
Documents
Settlement
WLFH
RWLF1051 List Output
Requests (With
Settlement
Item Data)
Management
Documents
Settlement
WLFO
RWLF1051 List Output
Request Lists
Settlement
(Header Data)
Management
Documents
Settlement
WLFP
RWLF1051 List Output
Request List
Settlement
(Item Data)
Management
Documents
WLI2
WLI2
WLI2
WLI2
WLI2
WLI2
WLI2
Page | 340
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF1009 Customer
WLFQ
Settlement Lists
(Header Data)
RWLF1010 Customer
WLFR
Settlement Lists
(With Item Data)
RWLF1011 Display Relevant WLRA
Payment
Documents for
Settlement Doc
List Creation
RWLF1012 Display Relevant WLRB
Billing
Documents for
Creation of
Settlem. Doc
Lists
RWLF1013 Display Relevant WBLRB
Customer
Settlement Lists
for Settl Doc
List Creation
RWLF1014 Customer
S_AL0_9
Settlement
6000193
(Header
Information)
RWLF1015 Customer
S_AL0_9
Settlement (With 6000194
Item Data)
RWLF1051 List Output
WLI2
Settlement
Management
Documents
RWLF1051 List Output
WLI2
Settlement
Management
Documents
RWLF_SE Worklist based
WLFSLRL
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
RWLF_SE Worklist based
WLFSLRL
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
RWLF_SE Worklist based
WLFSLRL
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
RWLF1051 List Output
Settlement
Management
Documents
RWLF1051 List Output
Settlement
Management
Documents
RWLF1016 Expenses
S_AL0_9 RWLF1051 List Output
Settlement
6000195
Settlement
(Header
Management
Information)
Documents
RWLF1017 Expenses
S_AL0_9 RWLF1051 List Output
Settlement (With 6000196
Settlement
Item Data)
Management
Documents
RWLF1018 Display
S_AL0_9 RWLF_SE Worklist based
Customer
6000198 TTLEMEN Creation of
Settlements for
T_LIST_RL Settlement Document
Settlement
List (Dialog)
Document List
Creation
WLI2
WLI2
WLI2
WLI2
WLFSLRL
Page | 341
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF1019 Relevant
Expenses
Settlements for
Settlement
Document List
Creation
RWLF1050 List Output
Single
Documents
S_AL0_9 RWLF_SE Worklist based
WLFSLRL
6000334 TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
WLI1
RWLF1052 List Output List WLI3
Documents
RWLF1CH Display Change
D
Document for
Settlement
Management
Documents
RWLF1KO Conditions for
1
Settlement
Requests
(Vendor)
RWLF1KO Conditions for
2
Settlement
Request Lists
RWLF1KO Conditions for
3
Settlement
Document Lists
RWLF1KO Conditions for
4
Settlement
Requests
(Customer)
RWLF1KO Conditions for
5
Customer
Settlement List
Documents
RWLF2001 Mass Release of WLFF
Settlement
Documents to
Accounting
RWLF2002 Mass
WLFI
Cancellation of
Settlement
Requests
RWLF1051 List Output
Settlement
Management
Documents
RWLF1051 List Output
Settlement
Management
Documents
RWLF_CH Display Change
ANGE_DO Documents
CUMENTS
WLI2
RWLF1051 List Output
Settlement
Management
Documents
RWLF1051 List Output
Settlement
Management
Documents
RWLF1051 List Output
Settlement
Management
Documents
RWLF1051 List Output
Settlement
Management
Documents
RWLF1051 List Output
Settlement
Management
Documents
RWLF2056 Mass Release of
Settlement
Management
Documents
RWLF2055 Mass Cancellation of
Settlement
Management
Documents
WLI2
WLI2
WLF_CHANGE_D
OCUMENTS
WLI2
WLI2
WLI2
WLI2
WAB_RELEASE
WAB_CANCEL
Page | 342
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF2003 Mass
Cancellation of
Billing
Documents
RWLF2004 Mass release of
billing
documents to
accounting
RWLF2005 Mass Release of
Remuneration
Lists to
Accounting
RWLF2006 Generate
Settlement
Document Lists
from Vendor
Billing
Documents
RWLF2007 Generate
Remuneration
Lists from
Payment
Documents
RWLF2008 Mass Release of
Settlement
Request Lists to
Accounting
RWLF2009 Mass release of
posting lists to
Accounting
WLFJ
RWLF2055 Mass Cancellation of
Settlement
Management
Documents
RWLF2056 Mass Release of
Settlement
Management
Documents
RWLF2056 Mass Release of
Settlement
Management
Documents
RWLF9039 Create Settlement
Document Lists
WAB_CANCEL
WLFN
RWLF9039 Create Settlement
Document Lists
WLF_RRLE_CRE
ATE
WRL4
RWLF2056 Mass Release of
Settlement
Management
Documents
RWLF2056 Mass Release of
Settlement
Management
Documents
RWLF2052 Generate Customer
Settlement Lists from
Settlement
Documents
RWLF9039 Create Settlement
Document Lists
WAB_RELEASE
WLFK
WLFL
WLFM
WBL4
RWLF2010 Create posting WBLR
lists from
preceding
documents
RWLF2011 Create
WLFV
Settlement
Document Lists
from Customer
Settlement Lists
RWLF2012 Complete
WLFW
Settlement
Request Lists
RWLF2013 Mass Release of WLFLK
Customer
Remuneration
WAB_RELEASE
WAB_RELEASE
WLF_RRLE_CRE
ATE
WAB_RELEASE
WBLRN
WLF_RRLE_CRE
ATE
RWLF2057 Mass Completion of WAB_CLOSE
Settlement
Management
Documents
RWLF2056 Mass Release of
WAB_RELEASE
Settlement
Management
Documents
Page | 343
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF2014
RWLF2016
RWLF2018
RWLF2019
RWLF2020
RWLF2021
RWLF2022
RWLF2023
RWLF2024
RWLF2025
RWLF2026
Lists to Financial
Accounting
Create Customer S_AL0_9
Settlements for 6000192
Settlement
Requests
Create
S_AL0_9
Remuneration 6000197
Lists from
Customer
Settlements
Mass Release of S_AL0_9
Customer
6000212
Settlements for
Financial
Accounting
Mass
S_AL0_9
Cancellation of 6000307
Settlement
Request Lists
Mass
S_AL0_9
Cancellation of 6000308
Customer
Settlements
Mass
S_AL0_9
Cancellation of 6000306
Remuneration
Lists
Mass
S_AL0_9
Cancellation of 6000309
Customer
Settlement Lists
Mass Price
S_AL0_9
Determination 6000324
for Settlement
Request Lists
Mass Price
S_AL0_9
Determination 6000325
for Payment
Documents
Create
S_AL0_9
Remuneration 6000333
Lists from
Expense
Settlements
Mass Release of S_AL0_9
Expense
6000335
Settlements for
RWLF2051 Generate Customer
Settlements from
Settlement
Documents
RWLF9039 Create Settlement
Document Lists
WLF1K
RWLF2056 Mass Release of
Settlement
Management
Documents
WAB_RELEASE
RWLF2055 Mass Cancellation of
Settlement
Management
Documents
RWLF2055 Mass Cancellation of
Settlement
Management
Documents
RWLF2055 Mass Cancellation of
Settlement
Management
Documents
RWLF2055 Mass Cancellation of
Settlement
Management
Documents
RWLF2054 Mass Pricing for
Settlement
Management
Documents
RWLF2054 Mass Pricing for
Settlement
Management
Documents
RWLF9039 Create Settlement
Document Lists
WAB_CANCEL
RWLF2056 Mass Release of
Settlement
WAB_RELEASE
WLF_RRLE_CRE
ATE
WAB_CANCEL
WAB_CANCEL
WAB_CANCEL
WAB_PRICING
WAB_PRICING
WLF_RRLE_CRE
ATE
Page | 344
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Financial
Accounting
RWLF2027 Mass
Cancellation of
Expense
Settlement
RWLF2028 Complete
Settlement
Requests
RWLF2029 Complete
Vendor Billing
Documents
S_AL0_9 RWLF2055
6000336
S_AC0_5 RWLF2057
2000143
S_AC0_5 RWLF2057
2000169
Management
Documents
Mass Cancellation of
Settlement
Management
Documents
Mass Completion of
Settlement
Management
Documents
Mass Completion of
Settlement
Management
Documents
Generate Vendor
Settlement Lists from
Settlement
Documents
RWLF2030 Create
WRLV
RWLF2053
Settlement
Request Lists
from Preceding
Documents
RWLF2031 Complete
S_AC0_5 RWLF2057 Mass Completion of
Expenses
2000170
Settlement
Settlements
Management
Documents
RWLF2032 Reopen
S_AC0_5 RWLF2058 Mass Reopening of
Settlement
2000172
Settlement
Requests
Management
Documents
RWLF2033 Reopen Vendor S_AC0_5 RWLF2058 Mass Reopening of
Billing
2000174
Settlement
Documents
Management
Documents
RWLF2034 Reopen
S_AC0_5 RWLF2058 Mass Reopening of
Expenses
2000175
Settlement
Settlements
Management
Documents
RWLF2059 Generate Posting WBLRO RWLF2052 Generate Customer
Lists from
Settlement Lists from
Settlement
Settlement
Requests
Documents
RWLF2059 Dispatcher:
WBLRO_ RWLF2052 Dispatcher: Create
D
Create Posting DISP
D
Customer Settlement
Lists
Lists
RWLF2060 Generate
WLF1KO RWLF2051 Generate Customer
Customer
Settlements from
Settlements from
Settlement
Settlement
Documents
Requests
WAB_CANCEL
WAB_CLOSE
WAB_CLOSE
WRLVN
WAB_CLOSE
WAB_REOPEN
WAB_REOPEN
WAB_REOPEN
WBLRN
WBLRN_DISP
WLF1K
Page | 345
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF2061 Create
WRLVO RWLF2053
Settlement Lists
from Settlement
Requests
RWLF4001 Delete Archived WACLFR WLF_DEL
Vendor Billing
Documents from
the Database
RWLF4002 Delete Archived WACBLR WBU_DEL
Customer
Settlement Lists
from Database
RWLF4003 Delete Archived WACLRR WRECH_D
Settlement
EL
Document Lists
from Database
RWLF4004 Delete Archived WACZRR WZR_DEL
Settlement
Documents from
Database
RWLF4005 Delete Archived WACRLR WREG_DE
Vendor
L
Settlement Lists
from Database
RWLF4006 Delete Archived WACCIR WCI_DEL
Customer
Settlements from
Database
RWLF4007 Delete Archived WACSIR WSI_DEL
Expense
Settlements from
Database
RWLF7001 Display
WFL1
RWLF1051
Document Flow
of Vendor
Billing
Documents
RWLF7002 Display
WFL2
RWLF1051
Document Flow
for Customer
Settlement Lists
RWLF7003 Display
WFL3
RWLF1051
Document Flow
for Settlement
Document Lists
RWLF7004 Display
WFL4
RWLF1051
Document Flow
Generate Vendor
WRLVN
Settlement Lists from
Settlement
Documents
Archiving Vendor
Billing Docs and
Vendor Settlements:
Delete Program
Archiving Customer
Settlement Lists:
Delete Program
Archiving Settlement
Document Lists:
Delete Program
Archiving Settlement
Documents: Delete
Program
Archiving Vendor
Settlement Lists:
Delete Program
Archiving Customer
Settlements: Delete
Program
Archiving Expense
Settlements: Delete
Program
List Output
Settlement
Management
Documents
WLI2
List Output
Settlement
Management
Documents
List Output
Settlement
Management
Documents
List Output
Settlement
WLI2
WLI2
WLI2
Page | 346
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF7005
RWLF9002
RWLF9003
RWLF9004
RWLF9005
RWLF9006
RWLF9007
RWLF9008
RWLF9009
RWLF9010
for Settlement
Document
Display
Document Flow
for Vendor
Settlement Lists
Generate
Extended
Remuneration
Lists From
Payment
Documents
Create Extended
Remuneration
Lists From
Posting Lists
Settlement
Documents for
Application
Status
Vendor
Settlement Lists
for Application
Status
Generate
Remuneration
Lists from
Vendor Billing
Documents
Generate
Remuneration
Lists From
Customer
Settlements
Generate
Remuneration
Lists From
Expense
Settlements
Relevant
Payment
Documents For
Extended
Remuneration
List Creation
Relevant
Customer
Settlements For
Management
Documents
WFL5
RWLF1051 List Output
Settlement
Management
Documents
S_ALN_0 RWLF9039 Create Settlement
1000170
Document Lists
WLI2
WLF_RRLE_CRE
ATE
S_ALN_0 RWLF9039 Create Settlement
1000171
Document Lists
WLF_RRLE_CRE
ATE
WAPZR
RWLF1051 List Output
Settlement
Management
Documents
WAPRL RWLF1051 List Output
Settlement
Management
Documents
S_ALN_0 RWLF9039 Create Settlement
1000172
Document Lists
WLI2
S_ALN_0 RWLF9039 Create Settlement
1000173
Document Lists
WLF_RRLE_CRE
ATE
S_ALN_0 RWLF9039 Create Settlement
1000174
Document Lists
WLF_RRLE_CRE
ATE
WLI2
WLF_RRLE_CRE
ATE
S_ALN_0 RWLF_SE Worklist based
WLFSLRL
1000175 TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
S_ALN_0 RWLF_SE Worklist based
1000176 TTLEMEN Creation of
T_LIST_RL
WLFSLRL
Page | 347
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF9011
RWLF9012
RWLF9013
RWLF9014
RWLF9015
RWLF9016
RWLF9017
RWLF9018
Extended
Remuneration
List Creation
Relevant Posting S_ALN_0
Lists For
1000177
Extended
Remuneration
List Creation
Relevant
S_ALN_0
Expense
1000178
Settlements for
Extended
Remuneration
List Creation
Relevant Vendor S_ALN_0
Billing
1000179
Documents,
Extended
Remuneration
List Creation
Simulate
S_ALN_0
Generation of
1000371
Remuneration
Lists From
Payment
Documents
Simulate
S_ALN_0
Generation of
1000372
Remuneration
Lists From
Posting Lists
Simulate
S_ALN_0
Generation of
1000373
Remuneration
Lists From
Customer
Settlements
Generate
S_ALN_0
Simulation of
1000375
Remuneration
Lists From
Expense
Settlements
Simulate
S_ALN_0
Generation of
1000376
Remuneration
List From
Settlement Document
List (Dialog)
RWLF_SE Worklist based
WLFSLRL
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
RWLF_SE Worklist based
WLFSLRL
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
RWLF_SE Worklist based
WLFSLRL
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
RWLF9042 Simulate Settlement WLF_RRLE_SIM
Document Lists
RWLF9042 Simulate Settlement WLF_RRLE_SIM
Document Lists
RWLF9042 Simulate Settlement WLF_RRLE_SIM
Document Lists
RWLF9042 Simulate Settlement WLF_RRLE_SIM
Document Lists
RWLF9042 Simulate Settlement WLF_RRLE_SIM
Document Lists
Page | 348
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF9019
RWLF9020
RWLF9021
RWLF9022
RWLF9023
RWLF9024
RWLF9028
RWLF9029
Vendor Billing
Documents
Create Extended
Remuneration
Lists from
Remuneration
Lists
Relevant
Remuneration
Lists for
Extended
Remuneration
List Creation
Create
Simulation of
Remuneration
Lists from
Remuneration
Lists
Generate
Extended
Remuneration
Lists from
Preceding
Documents
Relevant
Preceding
Documents for
Extended
Remuneration
List Creation
Create
Simulation of
Remuneration
Lists from
Preceding
Documents
Generate
Extended
Remuneration
Lists from FI
Documents
Generate
Simulation
Remuneration
Lists from FI
Documents
S_AEN_1 RWLF9039 Create Settlement
0000032
Document Lists
WLF_RRLE_CRE
ATE
S_AEN_1 RWLF_SE Worklist based
WLFSLRL
0000033 TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
S_AEN_1 RWLF9042 Simulate Settlement WLF_RRLE_SIM
0000034
Document Lists
S_AEN_1 RWLF9039 Create Settlement
0000060
Document Lists
WLF_RRLE_CRE
ATE
S_AEN_1 RWLF_SE Worklist based
WLFSLRL
0000065 TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
S_AEN_1 RWLF9042 Simulate Settlement WLF_RRLE_SIM
0000066
Document Lists
S_E37_17 RWLF9039 Create Settlement
000019
Document Lists
WLF_RRLE_CRE
ATE
S_E37_17 RWLF9042 Simulate Settlement WLF_RRLE_SIM
000020
Document Lists
Page | 349
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF9030 Generate
Remuneration
Lists from
Vendor
Settlements
RWLF9031 Generate
Simulation of
Remuneration
Lists from
Vendor
Settlements
RWLF9032 Relevant Vendor
Settlements for
Extended
Remuneration
List Creation
RWLF9033 Generate
Extended
Remuneration
Lists from SD
Billing
Documents
RWLF9034 Generate
Simulation of
Remuneration
Lists from SD
Billing
Documents
RWLF9037 Relevant SD
Billing
Documents for
Extended
Remuneration
List Creation
RWLF9038 Relevant FI
Documents for
Extended
Remuneration
List Creation
RWLF9080 Posting List
Creation
Dispatcher
RWLF9081 Customer
Settlement
Creation
Dispatcher
S_PRN_5 RWLF9039 Create Settlement
3000718
Document Lists
WLF_RRLE_CRE
ATE
S_PRN_5 RWLF9042 Simulate Settlement WLF_RRLE_SIM
3000719
Document Lists
S_PRN_5 RWLF_SE Worklist based
WLFSLRL
3000720 TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
S_E4R_35 RWLF9039 Create Settlement
000021
Document Lists
WLF_RRLE_CRE
ATE
S_E4R_35 RWLF9042 Simulate Settlement WLF_RRLE_SIM
000022
Document Lists
S_E4R_35 RWLF_SE Worklist based
WLFSLRL
000025
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
S_E4R_35 RWLF_SE Worklist based
WLFSLRL
000024
TTLEMEN Creation of
T_LIST_RL Settlement Document
List (Dialog)
S_AEN_1 RWLF2052 Dispatcher: Create
WBLRN_DISP
0000037 D
Customer Settlement
Lists
S_AEN_1 RWLF2051 Dispatcher: Create
WLF1K_DISP
0000038 D
Customer Settlements
Page | 350
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF9082 Mass Release
Dispatcher
RWLF9083 Settlement
Request List
Creation
Dispatcher
RWLF9084 Extended
Remuneration
List Creation
Dispatcher
RWLF9085 Dispatcher
Message Output
RWLF9086
RWLFFLO
W
RWLFIDO
C
RWLFM30
RWLFM31
RWLFM32
RWLFM60
RWLFM40
S_AEN_1 RWLF2056 Dispatcher: Mass
WAB_RELEASE_
0000075 D
Release of Settlement DISP
Management Doc.
S_AEN_1 RWLF2053 Dispatcher: Create
WRLVN_DISP
0000074 D
Vendor Settlement
Lists
S_AEN_1 RWLF9039 Dispatcher: Create
WLF_RRLE_CRE
0000083 D
Settlement Document ATE_DISP
Lists
S_E37_17 RWLFWR1 Dispatcher: Message
000021
4D
Output for Settlement
Mgmt Documents
Dispatcher Mass
RWLF2055 Dispatcher: Mass
Reversal
D
Cancellation of
Settlement
Management Docs
Display
WLFU
RWLF1051 List Output
Document Flow
Settlement
Information for
Management
Settlement
Documents
Management
Documents
Extended IDoc WLFEIR RWLFIDO IDoc Processing
Reporting
C_NEW
Automatic
WLFM30 RWLFM99 Automatic Document
Document
Adjustment of
Adjustment of
Settlement
Vendor Billing
Management
Documents
Documents
Automatic
WLFM31 RWLFM99 Automatic Document
Document
Adjustment of
Adjustment of
Settlement
Expenses
Management
Documents
Documents
Automatic
WLFM32 RWLFM99 Automatic Document
Document
Adjustment of
Adjustment of
Settlement
Vendor
Management
Settlements
Documents
Automatic
WLFM60 RWLFM99 Automatic Document
Document
Adjustment of
Adjustment of
Settlement
Customer
Management
Settlements
Documents
Automatic
WLFM40 RWLFM99 Automatic Document
Document
Adjustment of
WLN14D
WAB_CANCEL_D
ISP
WLI2
WLF_IDOC
WLFM99
WLFM99
WLFM99
WLFM99
WLFM99
Page | 351
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Adjustment of
Payment
Documents
RWLFWR0 Messages from
1
Vendor Billing
Documents
WLN1
RWLFWR0 Messages from WLN2
2
Customer
Settlement Lists
RWLFWR0 Messages from WLN3
3
Remuneration
Lists for Vendor
Billing
Documents
RWLFWR0 Messages from WLN4
4
settlement
requests
RWLFWR0 Messages from
5
Settlement
Request Lists
WLN5
RWLFWR0 Messages from
6
Remuneration
Lists for
Settlement
Requests
RWLFWR1 Messags from
0
Customer
Settlements
WLN6
RWLFWR1 Messages from
1
Expenses
Settlements
WLN11
RWLFWR1 Messages from
2
Remuneration
Lists for
Customer
Settlements
RWLFWR1 Messages from
3
Remuneration
Lists for
Expenses
Settlements
WLN12
WLN10
WLN13
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
RWLFWR1 Issue Messages from WLN14
4
Settlement
Management
Documents
Page | 352
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLWRCI Archive
WACCIA WCI_WRI
NV
Customer
Settlements
RWLWRIL Archive
WACLA WRECH_
S
Settlement
WRI
Document List
RWLWRIN Archive Vendor WACLFA WLF_WRI
V
Billing
Documents
Archiving Customer
Settlements: Write
Program
Archiving Settlement
Document Lists:
Write Program
Archiving Vendor
Billing Docs and
Vendor Settlements:
Write Program
RWLWRP Archive
WACBA WBU_WRI Archiving Customer
LS
Customer
Settlement Lists:
Settlement Lists
Write Program
RWLWRSI Activate
WACSIA WSI_WRI Archiving Expense
NV
Expense
Settlements: Write
Settlements
Program
RWLWRS Archive
WACRLA WREG_W Archiving Vendor
LS
Settlement
RI
Settlement Lists:
Request List
Write Program
RWLWRS Archive
WACZRA WZR_WRI Archiving Settlement
MR
Settlement
Documents: Write
Documents
Program
RWLF3001 Read Vendor
WLFT
RWLFLIST Document Monitor WLI5
Billing
Documents from
the Archive
(Display Items)
RWLF3002 Read Customer WLA8
RWLFLIST Document Monitor WLI5
Settlement Lists
from the Archive
(Display Items)
RWLF3003 Read Settlement WLA5
RWLFLIST Document Monitor WLI5
Document Lists
from the Archive
(Display Items)
RWLF3004 Read Settlement WLA6
RWLFLIST Document Monitor WLI5
Documents from
the Archive
(Display Items)
RWLF3005 Read Vendor
WLA7
RWLFLIST Document Monitor WLI5
Settlement Lists
from the Archive
(With Items)
RWLF3006 Read Customer WLACII RWLFLIST Document Monitor WLI5
Settlements
(with Item Data)
from the Archive
Page | 353
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWLF3007 Read Expense WLASII
Settlements
(with Item Data)
from the Archive
RWLF906 List Output of WRLI
0
Inbound IDoc
for Settlement
Request List
RWLF906 List Output of WZRI
1
Inbound IDocs
for Payment
Documents
RWLFLIST Document Monitor
WLI5
RWLFIDO IDoc Monitor
C_NEW
WLF_IDOC
RWLFIDO Idoc Monitor
C_NEW
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
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.
Page | 354
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
20 Logistics – ATP
20.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.
Required and Recommended Action(s)
Page | 355
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
There are two optional checks to be carried out before the upgrade to verify if the VBBS
is used:
1. Start transaction "SE16" and display the entries in table "VBBS". If there are any
entries, the XPRA has to run. If there are no entries, the second step has to be
executed.
2. Start transaction "OVZ2" and check the entries for the fields "SUMAU" and
"SUMLF". If there is any entry other than "A: Single records", the XPRA needs
to be executed.
If you are still using table VBBS, please read the related note 2209696 how to convert
your data after upgrade.
If you have custom code calling table VBBS, create a db view on table VBBE, and use
that view instead of the table VBBS.
Related SAP Notes
Custom code-related information
SAP Note: 2209696
Page | 356
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
21 Logistics - Environment, Health & Safety
(EHS)
21.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.
Required and Recommended Action(s)
Page | 357
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.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.
Required and Recommended Action(s)
Inform your business users.
Page | 358
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.3 S4TWL - Deprecation of 'Retrieve Safety Information' Fiori app
Application Components:
EHS-MGM-RAS, EHS-SUS-HS
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.
Required and Recommended Action(s)
Inform your business users.
How to Determine Relevancy
Page | 359
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
This Simplification Item is relevant if you have the 'Retrieve Safety Information' Fiori
application in use.
Other Terms
Environment, Health and Safety
21.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)
EHHSS_INC3 (EHSM: Incident Group)
EHHSS_INC5 (EHSM: Incident by Location)
The following authorization objects have been newly introduced:
•
EHHSS_INC6 (EHS: Incident)
o This replaces EHHSS_INC1 and EHHSS_INC5
Page | 360
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
EHHSS_INC7 (EHS: Incident Group)
o This replaces EHHSS_INC3
Most authorization criteria which previously were covered by EHHSS_INC5 are now
covered by EHHSS_INC6. But some of the criteria from EHHSS_INC5 (like for example
'Location Authorization Group') no longer exist; the mitigation of this missing
authorization aspect is planned to be done in a successor release of S/4HANA 1610.
The standard implementations of the following BAdIs together with their implementing
standard classes were removed (the BAdIs themselves still exist; customer
implementations are not touched):
•
•
BADI_EHHSS_INC_EXT_AUTH_CHECK (extended authorization check based
on EHHSS_INC3)
BADI_EHHSS_INC_EXT_LOC_CHECK (extended authorization check based
on EHHSS_INC5)
These BAdIs (see also SAP Implementation Guide (IMG)): Environment, Health and Safety
Incident Management Business Add-Ins Business Add-Ins for Authorization BAdI:
Extended Authorization Checks) are the place where the authorization checks for the now
obsolete authorization objects EHHSS_INC3 and EHHSS_INC5 took place. As the
standard implementations do no longer exist, EHHSS_INC3 and EHHSS_INC5 are now
ignored by the standard.
Business Process related information
Incident Management will not work before you have adjusted your business roles in a
way that they also contain the newly introduced authorization objects.
Required and Recommended Action(s)
Review your authorization concept and your EHS roles. Replace the obsolete
authorization objects accordingly with the new authorization objects EHHSS_INC6 and
EHHSS_INC7.
In case you want to perform additional authorization checks based on the now
obsolete authorization objects EHHSS_INC3 and EHHSS_INC5, do a customer
implementation of the above mentioned BAdIs. In this case make sure that your users
still own the appropriate authorizations. SAP recommends to consider this option
thoroughly and only use it if the new authorization objects are not sufficient and you
cannot wait for the planned extensions of the authorization concept.
In case you have previously already done a custom implementation of the above BAdIs
please keep in mind the following:
Page | 361
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
If you have written your own class or have copied the SAP class as basis for your
own implementation, please be aware that these BAdIs are still active and
working. You need to de-activate them if you want to de-activate the processing
of EHHSS_INC3 and EHHSS_INC5.
If you have derived your custom implementation class from the standard
implementation class of the BAdI, please be aware that this derived class will be
deleted during the upgrade!
How to Determine Relevancy
This Simplification Item is relevant if you have EHS Incident Management in use. This is
usually the case if table EHHSSD_INC_ROOT hat 20 or more entries.
Other Terms
Environment, Health, and Safety; EHS Management
21.5 S4TWL - Removal of EHS Home Screens
Application Components:
EHS-MGM-RAS, EHS-MGM-INC, EHS-SUS-HS, EHS-SUS-IM
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
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)
Page | 362
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
Hazardous Material Manager / Hazardous Substance Manager
(SAP_EHSM_HSS_HAZSUBMGR)
Sampling Technician (SAP_EHSM_HSS_SMPLTECH)
Incident Manager (SAP_EHSM_HSS_INCIDENT_MANAGER)
These home pages are no longer available in SAP S/4HANA.
Business Process related information
The users of the mentioned roles should use the following alternative approaches to
access the former home page functionality:
•
•
To access the overview charts from the former home pages, use the
corresponding SAP Fiori launchpad tiles.
o Example: To get the same information as from the "Risks" chart on the
former Industrial Hygienist home page, use the "Risk overview" tile from
the SAP Fiori launchpad.
To access the applications and activities which were accessible via links on the
former home pages, use the corresponding SAP Fiori launchpad tiles.
o Example: To start the "Search/edit risks" application as known from the
former Industrial Hygienist home page, use the "Manage Risks" tile from
the SAP Fiori lauchpad.
Required and Recommended Action(s)
Inform the end users about the changed user interface (UI) and how Fiori and the
SAP Fiori launchpad replace the former UI concepts.
How to Determine Relevancy
This Simplification Item is relevant if you use Risk Assessment or Incident
Management. This is usually the case if either table EHHSSD_INC_ROOT or table
EHHSSD_RAS_ROOT has 20 or more entries.
Other Terms
Environment, Health, and Safety; EHS Management
21.6 S4TWL - Specification Workbench Adjustments
Application Components:
EHS-BD-SPE
Related Notes:
Note Type
Note Number
Note Description
Page | 363
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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
21.7 S4TWL - Simplification of Incident Management workflows
Application Components:
EHS-MGM-INC, EHS-SUS-IM
Related Notes:
Page | 364
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 365
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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
21.8 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
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
Page | 366
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
OELs are no longer maintained via the application Manage Regulatory
Lists - OELs. This application has been deprecated.
o Instead, OELs are maintained as Compliance Requirements using the new
application Manage Compliance - Regulations, Policies.
OEL - Configuration
o 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.
o
•
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).
Check the OEL data migration (after the actual upgrade):
1. Start the new application Manage Compliance - Regulations, Policies.
2. 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").
3. If you are satisfied with the results, remove the text "Migrated" from the
Compliance Requirement names.
Page | 367
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.9 S4TWL - 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
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.
Page | 368
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 369
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
21.10 S4TWL - 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 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 EHS Risk Assessment process roughly speaking consists of these three steps:
1. Identify risks
2. Plan the assessment of the risks (by grouping them into Risk Assessment projects)
3. 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 exist 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 just 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 two new applications.
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 some limited amount of time.
Page | 370
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
- 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 do 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.
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
21.11 S4TWL - Industrial Hygiene and EC interfaces
Application Components:
EHS-IHS, XAP-EM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267781
S4TWL - Industrial Hygiene and EC
interfaces
Symptom
Page | 371
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Customers can use SAP Environmental Compliance (SAP EC) to support emissions and
compliance-relevant processes. In addition, Environmental Compliance provides
interfaces to exchange data with other applications.
In SAP S/4HANA on-premise edition 1511, the following interfaces are not available:
1. Environmental Compliance - Specification Database:
o Environmental Compliance will not be able to read specification data or
units of measurement from Environment, Health, and Safety as part of
SAP S/4HANA
2. Environmental Compliance - Incident:
o Environmental Compliance will not be able to read incident or location
data from Environment, Health, and Safety as part of SAP S/4HANA
3. EAM - Environmental Compliance:
o Enterprise Asset Management (EAM), as part of SAP S/4HANA, will not
be able to display Environmental Compliance data
A successor solution for SAP Environmental Compliance is planned for Environment,
Health, and Safety in a future SAP S/4HANA delivery.
Business Process related information
Industrial Hygiene and Safety (EHS-IHS) is replaced by the new incident management
solution and health and safety management solution of Environment, Health, and
Safety as part of SAP S/4HANA.
Business processes are described in the documentation for Environment, Health, and
Safety as part of SAP S/4HANA.
Page | 372
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Transaction not
available in SAP
S/4HANA onpremise edition
1511
CBIH02,CBIH03,CBIH12,CBIH13,CBIH14,CBIH42,CBIH43,CBIH
50,CBIH51,CBIH52,CBIH72,
CBIH73,CBIH82,CBIH83,CBIH88,CBIH89,CBIHB0,CBIHB1,CBI
HB2,CBIHB3,CBIHB4,CBIHB5,CBIHB6,CBIHM2,CBIHM3,CBIH
MR01,CBIHMR02,
CBIHMR03,CBIHMR04,CBIHMR05,CBIHMR06,CBIHMR07,CBI
HMR08,CBIHMR09,CBIHT0,CBIHT1,CBIHT2,CBIHT3,CBIHT4,C
BIHT5,CBIHT6,CBIHT7
Related SAP Notes
Custom Code related information
SAP Note: 2217206
21.12 S4TWL - Renovation of EHS authorization concept
Application Components:
EHS-MGM-RAS, EHS-MGM-INC, EHS-MGM-ENV, EHS-MGMFND, EHS-SUS-HS, EHS-SUS-IM, EHS-SUS-EM, EHS-SUS-FND
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
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
Page | 373
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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...
THEN...
...user has authorization to ...user can access incidents ...user can access incidents
access incidents at ...
without assigned location at location 'XYZ'
location 'XYZ'
yes(!)
yes
location ' '
yes
no
New behaviour:
IF...
THEN...
...user has authorization to ...user can access incidents ...user can access incidents
access incidents at ...
without assigned location 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)
1. 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.
Page | 374
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2. 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.
3. Else you need to adjust your authorization concept for the authorization objects
listed below.
o 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
EHS
Foundation
Environment
Management
Health and
Safety
Management
Incident
Management
Authorization object
Name
Relevant authorization object fields
technically
Name
technically
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
Scenario
Location
Authorization Group
Business Area
Company Code
EHENV_SCEN
Cost Center
Country
Plant ID
Region
LOCAUTHGRP
LOCBUSAREA
LOCCOMP
LOCCOST
LOCCOUNTRY
LOCPLANT
LOCREGION
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
Incident Report
EHHSS_INC2
Organizational Unit
ID
Plant ID
ORGUNIT_ID
PLANT_ID
Page | 375
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.13 S4TWL - 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
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
Page | 376
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
o 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".
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".
Page | 377
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
o 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
Environment, Health, and Safety; EHS Management; EHS; Risk Assessment; Health &
Safety Management; Health and Safety Management
21.14 S4TWL - 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
Page | 378
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
1. Log on to your backend system.
2. Start transaction SPRO.
3. In the Customizing for Environment, Health & Safety, open the activity
under: Environment Management -> Compliance Requirement -> Specify
Regulatory List Types.
4. 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.
5. 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
Page | 379
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Environment, Health, and Safety; EHS; EHS Management; Environment Management;
EM
21.15 S4TWL - 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
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.
Page | 380
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.16 S4TWL - 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
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.
Page | 381
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Other Terms
Environment, Health, and Safety; EHS; EHS Management; Health and
Safety Management
21.17 S4TWL - Renovation of task management
Application Components:
EHS-SUS-HS, EHS-SUS-EM, EHS-SUS-IM
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
Page | 382
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Renovation
Solution
Description
This note is intended to give a deeper insight into the renovation of the EHS task
management. This is particulaly interesting for customers who have enhanced the EHS
Task Management (for example with custom coding or additional workflows).
Note: Resulting functional changes are described in the referenced notes.
Environment, Health and Safety contains task management functionality which is used by
its components Health and Safety Management, Incident Management and Environment
Management. The EHS Task Management was completely reworked (new data model,
new coding) and moved to Fiori (new user interface). The following processes are
affected by this change:
•
•
•
Incident Management
o Standard incident actions
o Standard investigation step actions
o Plant maintenance notifications
o MoC (= Management of Change) change requests
o Incident lifecycle workflow
o Notify HR (absence) administrator workflow
o HR absence maintained workflow
o Report generation workflow (removed)
o Report shipment workflow (removed)
o Report approval workflow (removed)
Health and Safety Management
o Standard risk assessment actions
o Control actions
o Plant maintenance notifications
o MoC (= Management of Change) change requests
Environment Management
o Standard compliance scenario actions
Business Process related information
The business process as such is not affected by this change as task management
functionality is still available and automatic migration to the new data model takes place.
Required and Recommended Action(s)
Page | 383
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
1. Before upgrading make sure to complete all open processes listed in the paragraph
'Description'.
o If you miss to do so, these processes will be cancelled/stopped by the
system upgrade.
▪ In this case you need to manually run the report
R_EHFND_WFF_RESTART_PROCESSES after the upgrade in
order to correctly re-schedule the previously stopped processes.
▪ For more details see the report documentation of the mentioned
report.
2. Check if you have implemented any additional functionality (like additional or
modified workflows) on top of the old task management.
o If this is the case you need to adjust your workflows.
How to Determine Relevancy
This Transition Worklist item is relevant for you if you have the EHS task management
in use. This is the case if at least one of the following tables contains any entries:
•
•
•
•
•
•
•
EHHSSD_IAC_ROOT
EHHSSD_RAC_ROOT
EHENVD_SAC_ROOT
EHHSSD_PIL_ROOT
EHHSSD_PIH_ROOT
EHHSSD_PIR_ROOT
EHHSSD_PIA_ROOT
Other Terms
Environment, Health, and Safety; EHS; Health and Safety Management; Incident
Management; Environment Management
21.18 S4TWL - Deprecation of Mapping Workbench in Foundation of EHS
Application Components:
EHS-MGM, EHS-SUS-FND, EHS-MGM-FND-FRM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2408533
S4TWL - Deprecation of Mapping
Workbench in Foundation of EHS
Symptom
Page | 384
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
21.19 S4TWL - Occupational Health
Page | 385
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 on-premise edition 1511, this solution is no longer available
and there is no successor solution.
Business Process related information
Occupational Health (EHS-HEA) is not available in SAP S/4HANA and the related
business processes are no longer supported.
Transaction not EHSAMBTAET,EHSASSIGN,EHSASSLTA,EHSASSPERS,
available in SAP
S/4HANA on- EHSBC02,EHSBP11,EHSBP12,EHSBP13,EHSBP31,EHSBP32,EHS
premise edition BP33,EHSBP41,EHSBP42,EHSBP43,EHSBP51,EHSBP52,EHSBP53,
1511
EHSCALPROX,EHSCBER,EHSCDCT, EHSCMAS,EHSDATIMP,E
HSDIAGSL,EHSEVAL00,EHSEXIST0,
EHSH_C_NR_EXA_C,EHSH_C_NR_NEWPE,EHSH_C_NR_RECN,
EHSH_C_NR_VAC_I,EHSH_D_CALPHYS,EHSH_D_PCP,
EHSMQUEST,EHSMQUEST01,EHSPERSHC1,EHSPP01,EHSPRAN
Z,EHSPRLOE,EHSQCATOH,EHSQEVAL01,EHSQUESTOH,
EHSSCAN,EHSSERV,EHSSERV01,EHSSERV11,EHSSERV30,EHS
SER50,EHSSTRU00,EHSSUGGP,EHSTERM01,
Page | 386
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
EHSVA02,EHSVU01,EHSVU01_SELSCREEN,EHSVU11,EHSVU2
1,EHSVU31
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2217205
21.20 S4TWL - 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.
Transaction not WAA01,WAA02,WAA03,WAA04,WAA10,WAA11,WAA12,WAA1
available in SAP 3,WAA19,WAA20,WAA21,WAA22,WAA23,WAA24,WAA25,WAA
S/4HANA on- 26, WAAP,
Page | 387
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
premise edition WACB01,WACM01,WACM02,WACM03,WACM04,WACM10,WA
1511
CM30,WACO02,WACO02OLD,WACO03OLD,WACO04OLD,
WACS1,WACS2,WACS3,WACS4,WACS6,WADC,WADI,WAE01,
WAE02,WAE03,WAE10,WAEA,WAGE, WAM01,
WAM02,WAM03,WAM04,WAM05,WAMC,WAMI,WAMR,WANP,
WAREP001,
WASM100,
WASM101,WASM102,WASM109,WASS100,WASS101,WASS102,
WASS103,WASS104,WASS105,WASS106,WASS107,WASS108,W
ASS110,
WASS111,WASS112,WASS113,WASS114,WASS115,WASS116,W
ASS117,WASS118,WASS119,WASS120,WASS121,WASS122,WAS
S123,WASS124,
WATR,WATREE
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related information
SAP Note: 2217202
21.21 S4TWL - Simplification in Incident Management and Risk Assessment
Application Components:
EHS-MGM-RAS, EHS-MGM-INC
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
Page | 388
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 onpremise edition 1511, the some functions are not available.
Incident Management
The following incident management functions are not available in SAP S/4HANA:
•
•
•
•
•
•
•
•
•
•
BI extraction and queries for incident reporting
GRC integration of incidents
MM integration for released material as part of incidents
Novareto integration for incidents
eSOA services for incidents
Enterprise search for incidents
Direct creation of HR absences from incidents
Creation of quality notifications from incidents
Creation of service notifications from incidents
Service orders for financial tracking
Risk Assessment
The following risk assessment functions are not available in SAP S/4HANA:
•
•
•
•
•
•
BI extraction and queries for chemicals
Amounts/data series
Creation of customer notifications from risk assessments
Creation of quality notifications from risk assessments
IH work area integration with locations
Application "Identification of risks effected by OEL changes"
o 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.
Page | 389
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Actions
Recommended actions for Incident Management:
•
•
•
•
Close all open quality notifications for incidents.
Set the end date of recurring quality notifications for incidents to a date that is
earlier than the conversion to the target system.
Close all open customer service notifications for incidents.
Set the end date of recurring customer service notifications for incidents to a date
that is earlier than the conversion to the target system.
Recommended actions for Risk Assessment:
•
•
•
•
Close all open quality notifications for risk assessments.
Set the end date of recurring quality notifications for risk assessments to a date
that is earlier than the conversion to the target system.
Close all open customer service notifications for risk assessments.
Set the end date of recurring customer service notifications for risk assessments to
a date that is earlier than the conversion to the target system.
Related SAP Notes
Conversion Pre-Checks
Custom Code related information
Additional related SAP Notes
SAP Note: 2194782
SAP Note: 2217208
SAP Note: 2065178
21.22 S4TWL - 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.
Page | 390
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
The following functions no longer exist in Health and Safety Management (formerly
known as Risk Assessment)
•
•
•
•
Requesting controls ...
o ... while editing controls in a Risk Assessment
o ... while indentifying risks using the guided activity for Risk Identification
Requesting impacts ...
o ... while editing impacts in the Edit Impact popup window
o ... while indentifying risks using the guided activity for Risk Identification
Requesting agents ...
o ... while indentifying risks using the guided activity for Risk Identification
Requesting hazards ...
o ... 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)
EHHSS_RAS_IDENTIF_CHM_DLG_LST (for Hazards)
EHHSS_RAS_IDENTIF_AIRBOR_DLG_LST (for Hazards)
Business Process related information
Page | 391
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.23 S4TWL - Responsible person for Planned Maintenance at EHS
locations
Application Components:
EHS-MGM, EHS-SUS-FND, EHS-SUS-HS, EHS-SUS-IM, EHS-SUS-
EM
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
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
Page | 392
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
21.24 S4TWL - Remote Integration Scenarios with EHS Health and Safety
Management
Application Components:
EHS-MGM, EHS-SUS-FND
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
Renewal
Solution
Page | 393
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
The following remote integration scenarios for EHS under S/4HANA are no longer
supported:
•
•
•
•
•
•
•
Integration of EHS with an external Enterprise Asset Management (EAM, PM)
system
Integration of EHS with an externalWork Clearance Management (WCM)
system
Integration of EHS with an externalMaterial Management / Inventory
Management (MM/IM) system
Integration of EHS with an external substance or specification database
Integration of EHS with an externalFinancials (FIN/Accounting) system
Integration of EHS with an external Human Resources, Human Capital
Management(HR, HCM) system
Integration of EHS with an external business partner (BuPa) administration
Business partner process-related information
It is only possible in S/4HANA with the S/4HANA own functions and modules to
integrate the above areas. Other integrations are not supported.
Required and recommended action(s)
Contact your SAP Account Manager, if you currently connect EHS with an external
system of the type described above, and discuss possible alternatives.
Determination of relevance
This simplification item is relevant if you want to connect EHS with one or several
external systems of the types mentioned above.
Other Terms
EHS risk assessment
21.25 S4TWL - Conversion relevant changes in EHS
Application Components:
EHS-MGM, EHS-SUS-FND, EHS-SUS-HS, EHS-SUS-IM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2336396
S4TWL - Conversion-relevant changes in
EHS
Page | 394
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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; conversion to SAP S/4HANA 1610; conversion to SAP
S/4HANA 1709
Page | 395
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
22 Logistics – GT
22.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/4 HANA
anymore becasue these transactions are replaced already in SAP ERP EHP7.
Transaction Codes and Reports not available in SAP S/4HANA
See also note 2204137
Obsolete Report
Obsolete Report Obsolete TCode Successor
Title
Report
Successo Successo
r Report r TCode
Title
Page | 396
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
RWB2B001
Trading Contract: WB24
General
Document
Overview
RWB2B001
Trading Contract: WB25_COMP
General
Document
Overview
RWB2BRE Trading WBRR
L
Contract:
Follow
on
documen
t
prosessin
g
RWB2BMA Mass
WB24N
S
Processin
g
(Release
and
Status
update)
WB2B_CREATE_TC_US Create User For WB2B_NETUS
ER
TC At Web
ER
RWB2DI001
Generate
WB2DI1
Differential
Invoices
RWB2DI002
Over of Billing
WB2DI2
Documents releva
nt for Creating
Differential Invs
RWB2DI003
Process Billing
WB2DI3
Documents
regarding
Differential
Invoices
RWB2DI004
Process Billing
WB2DI4
Documents
regarding
Differential Invoic
es
RWB2B006
Trading Contract: WB31
Financial
Documents
Obsolete TCode Successor TCode
POFO1
POFO31
POFO2
POFO32
POFO3
POFO33
Required and Recommended Action(s)
Page | 397
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 398
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
23 Logistics - Management of Change
23.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
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).
Page | 399
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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)
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:
Page | 400
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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.
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:
o Only contain business users as Business Partner.
o Do not contain Positions from the Business Partner Hierarchy.
Page | 401
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 402
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
24 Logistics - MM-IM
24.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 ISCWM, 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
a call of FMP transactions and reports will cause a dump (Blacklisted objects)
Page | 403
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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
24.2 S4TWL - Blocked customer or supplier in Inventory Management
Application Components:
MM-IM-GF, MM-IM-PI, MM-IM-RS, BNS-INT-ARI-IM
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.
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).
Page | 404
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
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.
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:
1. Select application ME (Inventory Management) and enter “Condition records
(F8)”
2. Select Output Type ARIB (Ariba Rcpt Request)
3. Select key combination ("Supplier/CoCode" or "Supplier")
4. In the selection screen for the condition records enter the supplier for that you
want to create or display conditions and press execute (F8).
Page | 405
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
5. Enter the conditions (supplier, respectively company code; the other attributes can
be ignored).
6. 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:
1. 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.
2. 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.
3. 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.
4. 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.
5. 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).
Page | 406
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
6. 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).
7. 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.
8. 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.
24.3 S4TWL - Document Flow Consistency for Goods Receipt to Inbound
Delivery
Application Components:
MM-IM-GR, LE-SHP-DL-LA, IS-A-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
Page | 407
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 408
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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 317 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.
Page | 409
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 410
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. Apply for an exemption for this check item
2. 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
24.4 S4TWL - DATA MODEL IN INVENTORY MANAGEMENT (MMIM)
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
Page | 411
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
You have customer enhancements, modifications or own functionalities in the area of
inventory management (component MM-IM) which were built for SAP ERP 6.0.
You are using functionalities which behave different in SAP S/4HANA Supply Chain
(MM - Inventory Management) compared to Suite on HANA.
The SAP ERP 6.0 stock inventory management data model consists of the two document
tables MKPF for document header information and MSEG for document item data.
Additionally there were aggregated actual stock quantity data stored in several tables.
Some of these tables do also store material master data attributes like the tables MARC,
MARD and MCHB. Such tables with material master data attributes as well as actual
stock quantities will be named as hybrid tables in the following. In contrast there are also
tables like MSSA containing only aggregated actual stock quantities for sales order stock.
Such tables will be called in the following as replaced aggregation tables.
With S/4HANA this data model has been changed significantly. The new de-normalized table
MATDOC has been introduced which contains the former header and item data of a material
document as well as a lot of further attributes. Material document data will be stored in
MATDOC only and not anymore in MKPF and MSEG. Additionally the aggregated actual
stock quantities will not be persisted anymore in the hybrid or replaced aggregation tables.
Instead, actual stock quantity data will be calculated on-the-fly from the new material
document table MATDOC for which some of those additional special fields are used. Hence,
with the new MM-IM data model the system will work on database level in an INSERT only
mode without DB locks. Nevertheless, for stock decreasing processes there will be still
ABAP locks to ensure stock consistency. A further advantage of the new MM-IM data model
is the capability of simple and fast reporting because the most information is all in one place:
MATDOC.
All below mentioned tables of the SAP ERP 6.0 product do still exist in S/4HANA as DDIC
definition as well as database object and the hybrid tables will still be used to store the
material master data attributes. For compatibility reasons there are Core Data Service (CDS)
Views assigned as proxy objects to all those tables ensuring that each read access to one of
the mentioned tables below still returns the data as before in SAP ERP 6.0. The CDS Views
do the on-the-fly aggregation of actual stock quantities from the new MM-IM data model and
join the master data attributes from the material master data table. Hence all customer
coding reading data from those tables will work as before because each read access to one
of the tables will get redirected in the database interface layer of NetWeaver to the assigned
CDS view. Write accesses to those tables have to be adjusted.
The affected tables are:
Page | 412
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Table
Table
descriptio
n
DDL Source of CDS
View for redirect
View to read the
content of the
database table (w/o
redirect to
compatibility view)
MKPF
Material
document
header
NSDM_DDL_MKPF
NSDM_MIG_MKPF
Material
document
item
NSDM_DDL_MSEG
MARC
Plant Data
for Material
NSDM_DDL_MARC
NSDM_MIG_MARC
V_MARC_M
D
MARD
Storage
Location
Data for
Material
NSDM_DDL_MARD
NSDM_MIG_MARD
V_MARD_M
D
MCHB
Batch
stocks
NSDM_DDL_MCHB
NSDM_MIG_MCHB
V_MCHB_M
D
MKOL
Special
Stocks
from
Vendor
NSDM_DDL_MKOL
NSDM_MIG_MKOL
V_MKOL_M
D
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_M
D
MSSA
Total
Customer
Orders on
Hand
NSDM_DDL_MSSA
NSDM_MIG_MSSA
MSEG
View to read
the master
data
attributes
only
-
NSDM_MIG_MSEG
-
-
Page | 413
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
MSPR
Project
Stock
NSDM_DDL_MSPR
NSDM_MIG_MSPR
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_MSKA
NSDM_MIG_MSKU
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
Stock in
Transit for
Project
NSDM_DDL_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
MSTQ
V_MSPR_M
D
V_MSKU_M
D
-
-
NSDM_MIG_MSTQ
-
Page | 414
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Vendor Total
NSDM_DDL_MSIS
NSDM_MIG_MSIS
MSIS_MD
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
MARC
H
History
NSDM_DDL_MARC
H
NSDM_MIG_MARC
H
-
Page | 415
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
MARD
H
History
NSDM_DDL_MARD
H
NSDM_MIG_MARD
H
-
MCHB
H
History
NSDM_DDL_MCHB
H
NSDM_MIG_MCHB
H
-
MKOLH
History
NSDM_DDL_MKOL
H
NSDM_MIG_MKOL
H
-
MSLBH
History
NSDM_DDL_MSLBH
NSDM_MIG_MSLBH
-
MSKAH
History
NSDM_DDL_MSKA
H
NSDM_MIG_MSKA
H
-
MSSAH
History
NSDM_DDL_MSSA
H
NSDM_MIG_MSSA
H
-
MSPR
H
History
NSDM_DDL_MSPR
H
NSDM_MIG_MSPR
H
-
MSSQ
H
History
NSDM_DDL_MSSQ
H
NSDM_MIG_MSSQ
H
-
MSKU
H
History
NSDM_DDL_MSKA
H
NSDM_MIG_MSKA
H
-
MSTBH
History
NSDM_DDL_MSTB
H
NSDM_MIG_MSTB
H
-
MSTEH
History
NSDM_DDL_MSTE
H
NSDM_MIG_MSTE
H
-
MSTQ
H
History
NSDM_DDL_MSTQ
H
NSDM_MIG_MSTQ
H
-
MCSD
H
History
NSDM_DDL_MCSD
H
NSDM_MIG_MCSD
H
-
MCSS
H
History
NSDM_DDL_MCSS
H
NSDM_MIG_MCSS
H
-
MSCD
H
History
NSDM_DDL_MSCD
H
NSDM_MIG_MSCD
H
-
Page | 416
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
MSFDH
History
NSDM_DDL_MSFD
H
NSDM_MIG_MSFD
H
-
MSIDH
History
NSDM_DDL_MSIDH
NSDM_MIG_MSIDH
-
MSRD
H
History
NSDM_DDL_MSRD
H
NSDM_MIG_MSRD
H
-
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
Page | 417
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 418
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Page | 419
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
the hybrid tables are still possible. Write operations on table MATDOC and your moved
customer append fields are done by class CL_NSDM_STOCK.
Page | 420
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
24.5 S4TWL - AVAILABILITY OF TRANSACTIONS IN MM-IM
Application Components:
MM-IM-GF
Related Notes:
Note Type
Note Number
Note Description
Page | 421
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Replace customer coding using the transaction codes MB01, MB02 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 transaction MB03 by make use of function module
MIGO_DIALOG
Page | 422
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Replace customer coding using the transaction MBST by make 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
24.6 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:
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1511:
transaction: SPRO --> Migration from SAP ERP Accounting powered by
SAP HANA --> Preparations and Migration of Customizing -->
Preparations and Migration of Customizing for Material Ledger -->
Migrate Material Ledger Customizing
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1610 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
Page | 423
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
Data migration:
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1511:
transaction: SPRO --> Migration from SAP ERP Accounting powered by
SAP HANA --> Migration --> Material Ledger Migration
o from SAP ERP or SAP Simple Finance to SAP S/4HANA 1610 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.
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
Page | 424
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
EBEW Sales Order Stock MBV_EBEW
Valuation
EBEWH History of Sales MBV_EBEWH
Order Stock
Valuation
MBEW Material
MBV_MBEW
Valuation
MBEWH History of
MBV_MBEWH
Material
Valuation
OBEW Valuated Stock MBV_OBEW
with
Subcontractor
(Japan)
OBEWH History of
MBV_OBEWH
Valuated Stock
with
Subcontractor
(Japan)
QBEW Project Stock
MBV_QBEW
Valuation
QBEWH History of Project MBV_QBEWH
Stock Valuation
View to read the content
of the original database
table (w/o redirect to
proxy view)
MBVEBEWOLD
View to read
master data
attributes only
MBVEBEWHOLD
V_EBEWH_MD
MBVMBEWOLD
V_MBEW_MD
MBVMBEWHOLD
V_MBEWH_MD
MBVOBEWOLD
V_OBEW_MD
MBVOBEWHOLD
V_OBEWH_MD
MBVQBEWOLD
V_QBEW_MD
MBVQBEWHOLD
V_QBEWH_MD
V_EBEW_MD
Page | 425
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 onpremise edition 1511
MMPI: Initialize period for material master records (Not
available with activated Material Ledger)
Required and Recommended Action(s)
Perform Conversion Pre-Checks on start release to identify start situation
Related SAP Notes
Conversion Pre-Checks
Custom Code related information
SAP Note: 2194618
SAP Note: 2129306
SAP Notes: 1804812
24.7 S4TWL - Material Valuation - Statistical moving average price
Application Components:
MM-IM-GF-VAL, MM-IM-GF-LOCK
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
Page | 426
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
One major innovation of SAP S/4HANA in the area of MM-IM is the significant increase
of transactional data throughput for high-volume transactions, especially goods
movements. To enable this from a technical point of view, it is necessary for the
application logic to avoid exclusive locking on the application layer.
For goods movements this can be achieved (with a few exceptions) for materials with
price control "Standard", where the relationship between unit costs for material inventory
(standard price) on the one hand, and inventory quantity and inventory value on the other
hand, is kept constant during goods movements. To calculate a consistent moving
average valuation, the system is still forced to use exclusive locks. Therefore it is not
possible to achieve the same increase in transactional data throughput for materials with
price control "Moving Average" as for materials with price control “Standard”.
In SAP ERP, for materials with price control "Standard" the system also calculates a
moving average valuation in parallel, the so-called "statistical" moving average price.
Obviously this statistical valuation requires exclusive locking as well. As previously
mentioned, exclusive locking limits the transactional data throughput, and therefore needs
to be avoided in SAP S/4HANA. In consequence, this parallel statistical moving average
valuation is not available in SAP S/4HANA, on-premise edition 1511.
Deactivation of the statistical moving average is not mandatory in SAP S/4HANA, but is
nevertheless recommended in order to achieve a significant increase of transactional data
throughput for goods movements. It is important to note that the deactivation is not
reversible.
As a result, end users creating material master data in SAP S/4HANA have to select one
of the following material valuation methods for a material:
•
•
Price control "Standard", which offers a fixed price inventory valuation and no
parallel "statistical" moving average valuation. Only dedicated business
transactions can change unit costs (e.g. MR21). But a significantly increased
transactional data throughput for goods movements can be achieved.
Price control "Moving Average", with which unit costs of material inventory can
be changed by any business transaction, but transactional data throughput is still
limited by exclusive locking.
In addition, the following database table fields are affected by the deactivation of the
statistical moving average:
•
In table MBEW, EBEW, OBEW, QBEW the fields SALKV and VERPR are not
updated anymore for materials with price control “Standard”. The same applies to
the history tables MBEWH, EBEWH, OBEWH and QBEWH.
Page | 427
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
In table CKMLCR the fields PVPRS and SALKV are not updated anymore for
materials with price control “Standard”.
In table MLCR the fields SALKV, SALKV_OLD and PVPRS_OLD are not
updated anymore for materials with price control “Standard”.
If Actual Costing is used, the above mentioned fields will still be updated with the
periodic unit price during the Actual Costing Closing Steps.
As a consequence of not updating the above-mentioned fields, the statistical moving
average price and the value based on the statistical moving average price are no longer
available on the user interface. This concerns the following transaction codes: MM01,
MM02, MM03, CKM3 and MR21.
Business Process related information
As its name implies, the statistical moving average price is purely statistical and does not
have any impact on actual financials-relevant valuation.
Without the statistical moving average price, an alternative way of valuation needs to be
used in few scenarios. This concerns, for instance, Balance Sheet Valuation and Product
Cost Planning, where selection/valuation variants must be checked and adapted.
Required and Recommended Action(s)
If within custom code the fields mentioned above under “Description” are evaluated for
materials with price control “Standard”, then this usage should be removed. One possible
reaction to this change could be to use instead of the V-Price (VERPR) either the S-Price
(STPRS) or the V-Price (VERPR) depending on the configured price control for the
respective material.
To identify such locations, it is required to make use of the where-used functionality of
transaction code SE11 and to consider other techniques like transaction
code CODE_SCANNER to find locations which SE11 cannot handle – such as dynamic
programming or native SQL statements.
Finally, the report SAPRCKM_NO_EXCLUSIVELY_LOCKING can be used to
deactivate the statistical moving average price. This can be done for converted systems
running the S/4HANA on-premise edition. In the S/4HANA cloud edition or new installs
of the SAP S/4HANA on-premise edition, the statistical moving average price is disabled
by default.
24.8 S4TWL - Performance optimizations within Material Document
Processing - lock beh
Application Components:
MM-IM, MM-IM-GF
Page | 428
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
require changes of the process behavior. Both will have effects on follow-on processes or
side processes.
2. Opportunities
2.1 Locks to protect stock
With the introduction of the new MM-IM data model in S/4HANA OP1511 there are no
UPDATE processes on the actual stock quantity fields in the material master and stock
aggregate tables anymore. Instead of the UPDATEs only INSERTs into the new material
document table will be done. Hence from a data base perspective there are no locks
anymore on DB level. That enables - from a DB perspective - parallel execution of
material document processing. Anyway, from a business perspective there are still logical
locks required because
1. Consistency with material master data (i.e. prevent parallel change of master data
attributes). This can be ensured already with a shared logical lock because with
such a lock a change of material master is protected.
2. Defined sequence of material documents (e.g. for moving average price).
3. Consistency with stock quantity (check availability if negative stock is not
allowed).
The consistency with master data and with stock quantity (1 + 3) is necessary in any case.
The defined sequence of material documents (2) is ensured only in the case that exclusive
lock is chosen in the customizing. Regarding the lock of materials to enable a consistent
quantity check (lock reason 3) there are currently two different kinds of lock strategies:
early exclusive quantity lock and late exclusive quantity lock.
2.2 Early lock strategy
Page | 429
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
In the early exclusive lock strategy, all material master data and quantities are read in an
array fetch before the item processing (except for special stocks) and exclusive locks are
set during the entire processing of the material document. As this implies that valid
quantities are read from the buffer, this option has the best performance regarding process
runtime, but on the other hand it has a worst performance regarding process throughput in
scenarios with many equal material items in parallel processes.
2.3 Late lock strategy
In the late exclusive lock strategy, the material master data and quantities are read also in
an array fetch before the item processing but no exclusive locks are set. An exclusive
lock will be set only for a short period of time during the item processing for each
specific item. This exclusive lock will be converted into a shared lock after checks for
stock underrun.
As the new MM-IM data model changes the old key figure model to an account model
this enables a more finer granular locking for the late quantity lock case starting with
S/4HANA OP1610 and CE1608. For the key figure model the locks have been set on
material and plant level in S/4HANA OP1511. With the account model the locks can be
set on material, plant, storage location, stock 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.
Page | 430
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
3. Overcome drawbacks
With the introduction of the new MM-IM data model for S/4HANA OP1511 the material
stock quantity data are not stored anymore as pre aggregated data in the old hybrid
(containing material master and material actual stock quantity data) or aggregate
(containing only material actual stock quantity data) tables. Instead the material stock
quantity data will be calculated on-the-fly from the material document table. For
applications this is transparent because the calculation of stock data as well as the
determination of the material master data will be done via CDS-compatibility views
which are assigned as proxy objects to those tables with hybrid or aggregate character
and each fetch to the tables get redirected in the DBI layer to the assigned proxy view.
According to the on-the-fly calculation, read accesses to those hybrid and aggregate
tables are much slower than in Suite on HANA where the aggregated quantity changes
have been stored in these tables as actual stock quantity data.
During material document processing, material data is read from the database in general
in an array fetch at the beginning of the processing. A second access to the database to
read material data will be done in case of the late exclusive lock during the item
processing. In both cases – due to the compatibility view – the material master as well as
the material stock quantity data will be read whereas in the prefetch only the master data
is required and during the late exclusive lock phase only the material stock quantity data
is required.
To turn the drawback of on-the-fly calculation into an advantage the following will be
introdcued with S/4HANA OP1610 and CE1608:
•
•
during the prefetch phase only the material master data will be read into internal
buffers by using the pure material master data views to retrieve the data from DB
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.
Page | 431
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Hence for S/4HANA OP1610 and CE1608, the adaptation done for the late lock
strategy allows parallel execution of material document processes whereas the stock
quantity read from DB and stock underrun check reduces the processing time of a single
material document process. Overall it increases the performance of material document
processing in S/4HANA OP1610 and CE1608 compared to S/4HANA OP1511 and Suite
on HANA.
4. Permission of negative stocks
It is possible to allow on plant level negative stocks. Also on storage location level
negative stocks can be permitted. And for the material itself a negative stock can be
enabled. All this was possible to configure already in S/4HANA OP1511 and also in
Suite on HANA. If on all 3 level the permission on negative stock has been granted then
in S/4HANA OP1610 and CE1608
1. no locks at all will be set in the late lock strategy case.
2. no stock determination from the data base will be done and no stock underrun
check will be executed (in both lock strategies).
Hence for such a configuration and setting of material master data the runtime and the
throughput may increase further.
5. Business process related information
5.1 Modifications in the coding of Material Document Processing
As already described in the Overcome Drawback section, stock quantity data will be read
and calculated only for stock decreasing processes where negative stocks are prohibited.
And this will be done, if necessary, in the new account model. Hence, the actual stock
quantity fields in the internal tables XMabc tables used and routed internally are always
zero and cannot be used for any subsequent calculation incorporated in the material
document processing. There is no option to populate these actual stock quantity fields in
the internal tables XMabc tables anymore! Thus, customer coding modifications using
stock quantity data from those XMabc internal tables must be 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
Page | 432
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
the LIS information structures and forces (at least for MM-IM) a serialized processing in
case of V1 mode. Data in those LIS information structures will be used for special
reporting by customers.
A forced serialization of MM-IM document processing due to active LIS and a
customizing of late lock strategy to enable parallel processing for MM-IM does not make
sense at all. Furthermore several LIS key figures like # of times a zero stock would be
reached by a posting, cannot be determined reliable in parallel processes. Hence, active
LIS and late lock mode is defined now as an inconsistent system state starting with
S/4HANA OP1610 and CE1608!
Furthermode, because several fields in internal structures (exactly those stock quanitity
fields of the former key figure model like field LABST in the internal structure
XMARD) are not populated with data anymore with the active optimization, absolut
stock quanities can not be send via the INVCON0x IDOC (message type INVCON).
If an On-Premise system is configured for early lock strategy then LIS and the INVCON
message type can be used. In this case the processing will be internally switched into the
legacy mode. That means that none of the above described optimizations will be
executed. This is necessary just because the optimized coding does not fill the internal
XMabc tables with stock data in the key figure model anymore (just because in many
cases stock data are not calculated at all) and the data in those internal
tables are required for LIS processing and the INVCON message type.
MM-IM development plans to provide step by step Virtual Data Model (VDM) views as
successor for LIS. The first VDM's released with S/4HANA OP1610 and CE1608 will be
for stock quantity reporting.
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.
Page | 433
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 434
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
24.9 S4TWL - 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
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
Page | 435
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
24.10 S4TWL - 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.
Page | 436
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
The second method involves individual locking of material master and valuation
data. Reduced exclusive locking times are used to minimize the collision
probability between parallel postings. To achieve this, intended stock changes are
communicated early in the process via the central enqueue server. All similar
postings need to read these numbers from the enqueue server and take them into
account along with the data read from the database. The drawback of this method
is increased effort resulting in a longer total runtime for each document. This
method is called “Late block” in Customizing.
With SAP S/4HANA 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
Page | 437
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
values. You can find more information about the Adjustment of Inventory Value
transaction in the SAP Help Portal.
Required and Recommended Action(s)
See SAP Note 2267835 for more information about the deactivation of statistical moving
average price, which is the prerequisite to increase transactional data throughput as
described above.
24.11 S4TWL - CWM in SAP S/4HANA
Application Components:
IS-CWM, MM-IM-GF-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.
Page | 438
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Description
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 you are using the ‘new architecture’ and
no further action is needed.
2. Category of Parallel Unit of Measure
In ECC 6.0 IS-CWM 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.
Page | 439
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.
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.
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
BUS1001006
BUS1001006
BUS2015
BUS2015
BUS2015
BOR method
SAVEDATA
SAVEREPLICA
CONFIRMDECENTRA
L
DELIVERYCHANGE
SAVEREPLICA
CWM enhanced Standard BAPI
BAPI_MATERIAL_SAVEDATA
BAPI_MATERIAL_SAVEREPLICA
BAPI_INB_DELIVERY_CONFIRM_DEC
BAPI_INB_DELIVERY_CHANGE
BAPI_INB_DELIVERY_SAVEREPLICA
Page | 440
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
BUS2017
LIKP
LIKP
CREATEFROMDATA
CONFIRMDECENTRA
L
DELIVERYCHANGE
LIKP
LIKP
SAVEREPLICA
SPLITDECENTRAL
BAPI_GOODSMVT_CREATE
BAPI_OUTB_DELIVERY_CONFIRM_DE
C
BAPI_OUTB_DELIVERY_CHANGE
BAPI_OUTB_DELIVERY_SAVEREPLIC
A
BAPI_OUTB_DELIVERY_SPLIT_DEC
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
/CWM/BUS06
/CWM/BUS15
/CWM/BUS17
/CWM/BUS28
/CWM/BUS42
/CWM/BUS70
/CWM/LIKP
Description
Standard material
Inbound delivery
Goods Movement
Material inventory
REM Backflush
Handling unit
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
/CWM/BUS06
/CWM/BUS06
/CWM/BUS15
/CWM/BUS15
/CWM/BUS15
/CWM/BUS17
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
Obsolete
Object Type
/CWM/BUS06
/CWM/BUS06
Method
SAVEDATA
SAVEREPLICA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
CREATEFROMDATA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
SPLITDECENTRAL
Message Type
/CWM/MATMAS_BAPI
/CWM/MATMAS_MASS_BAPI
/CWM/SHP_IBDLV_CONFIRM_DEC
/CWM/SHP_IBDLV_CHANGE
/CWM/SHP_IBDLV_SAVE_REPLICA
/CWM/MBGMCR
/CWM/SHP_OBDLV_CONFIRM_DEC
/CWM/SHP_OBDLV_CHANGE
/CWM/SHP_OBDLV_SAVE_REPLICA
/CWM/SHP_OBDLV_SPLIT_DECENTRAL
Method
SAVEDATA
SAVEREPLICA
IDOC Type
/CWM/MATMAS_BAPI01
/CWM/MATMAS_MASS_BAPI01
Page | 441
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
/CWM/BUS15
/CWM/BUS15
/CWM/BUS15
/CWM/BUS17
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
Obsolete
Object Type
/CWM/BUS06
/CWM/BUS06
/CWM/BUS15
/CWM/BUS15
/CWM/BUS15
/CWM/BUS17
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
Obsolete
Object Type
/CWM/BUS06
/CWM/BUS06
/CWM/BUS15
/CWM/BUS15
/CWM/BUS15
/CWM/BUS17
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
Obsolete
Object Type
/CWM/BUS06
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
CREATEFROMDATA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
SPLITDECENTRAL
/CWM/SHP_IBDLV_CONFIRM_DEC01
/CWM/SHP_IBDLV_CHANGE01
/CWM/SHP_IBDLV_SAVE_REPLICA01
/CWM/MBGMCR01
/CWM/SHP_OBDLV_CONFIRM_DEC01
/CWM/SHP_OBDLV_CHANGE01
/CWM/SHP_OBDLV_SAVE_REPLICA01
/CWM/SHP_OBDLV_SPLIT_DECENTR01
Method
SAVEDATA
SAVEREPLICA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
CREATEFROMDATA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
SPLITDECENTRAL
Function module for outbound ALE
/CWM/ALE_MATERIAL_SAVEDATA
/CWM/ALE_MATERIAL_SAVEREPLICA
/CWM/ALE_INB_DELVRY_CONFIRMDEC
/CWM/ALE_INB_DELVRY_CHANGE
/CWM/ALE_INB_DELVRY_SAVEREPL
/CWM/ALE_GOODSMVT_CREATE
/CWM/ALE_OUT_DELVRY_CONFIRMDEC
/CWM/ALE_OUT_DELVRY_CHANGE
/CWM/ALE_OUT_DELVRY_SAVEREPL
/CWM/ALE_OUT_DELVRY_SPLIT_DEC
Method
SAVEDATA
SAVEREPLICA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
CREATEFROMDATA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
SPLITDECENTRAL
Function module for inbound ALE
/CWM/IDOC_INPUT_MATMAS_BAPI
/CWM/IDOC_INPUT_MATMAS_MASS_BA
/CWM/IDOC_INPUT_SHP_IBDLV_CONF
/CWM/IDOC_INPUT_SHP_IBDLV_CHAN
/CWM/IDOC_INPUT_SHP_IBDLV_SAVE
/CWM/IDOC_INPUT_MBGMCR
/CWM/IDOC_INPUT_SHP_OBDLV_CONF
/CWM/IDOC_INPUT_SHP_OBDLV_CHAN
/CWM/IDOC_INPUT_SHP_OBDLV_SAVE
/CWM/IDOC_INPUT_SHP_OBDLV_SPLT
Method
SAVEDATA
IS-CWM Segment
/CWM/E1BP_MBEW
/CWM/E1BP_MBEWX
/CWM/E1BP_MATRETURN2
/CWM/E1BP_MARM
/CWM/E1BP_MARMX
/CWM/E1BPE1MBEW
/CWM/E1BPE1MBEWX
/CWM/E1MATMAS_MASS_BAPI
/CWM/E1BPE1MARM
/CWM/E1BPE1MARMX
/CWM/BUS06 SAVEREPLICA
/CWM/BUS15 CONFIRMDECENTRAL
Page | 442
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
/CWM/BUS15
/CWM/BUS15
/CWM/BUS17
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
/CWM/LIKP
DELIVERYCHANGE
SAVEREPLICA
CREATEFROMDATA
CONFIRMDECENTRAL
DELIVERYCHANGE
SAVEREPLICA
SPLITDECENTRAL
/CWM/E1SHP_IBDLV_CHANGE
/CWM/E1SHP_IBDLV_SAVE_REPLI
/CWM/E1SHP_OBDLV_CONFIRM_DE
/CWM/E1SHP_OBDLV_CHANGE
/CWM/E1SHP_OBDLV_SAVE_REPLI
/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
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.
Page | 443
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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.
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
Page | 444
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
25 Logistics – PLM
25.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 EDESK_CUS, EDESK_IPPE
in SAP S/4HANA onpremise edition 1511
Required and Recommended Action(s)
Page | 445
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
25.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- STEP10, STEP20
premise edition 1511
Required and Recommended Action(s)
Page | 446
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
25.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, onpremise 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 onpremise edition 1511
CVW*
Required and Recommended Action(s)
Page | 447
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
25.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:
•
Object dependencies of type actions have been documented as obsolete. Creation
of object dependencies of type actions isn't possible anymore (e.g. transaction
Page | 448
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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 CU51E -> Included in CU51
in SAP S/4HANA onCU52 -> Included in CU51
premise edition 1511
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
25.5 S4TWL - Classification
Application Components:
CA-CL
Page | 449
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Description
With SAP S/4HANA, on-premise edition 1511 transactions of the Classification are
renovated so that transactions may have changed functionality or may be completely
removed within SAP Product Lifecycle Management (SAP PLM).
•
•
•
•
User Defined Data Type (031) for characteristics has been removed.
Rename Characteristic functionality has been disabled.
Parameter Effectivity has been hidden.
Due to security reasons batch import has been limited and batch import is possible
only from presentation server.
Business Process related information
Parameter Effectivity has been hidden for classification in the SAP S/4HANA, onpremise edition 1511 shipment. As an alternative solution, Variant Configuration shall be
used with object based dependencies.
Transaction not available in CL20
SAP S/4HANA on-premise
edition 1511
CL22
Assign Object to Classes
Allocate Class to Classes
CL24
Assign Objects to One Class
CL6E
Copy DIN Standard
CL6F
Copy DIN Characteristic Data
CL6G
Create Material w. DIN Char. Data
CL6R
Direct Input for Classes
Page | 450
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
CLB1
Batch Input for Classification
CLB2
Direct Input for Classification
CLB3
Display Classification File
GENC
Generate Source Code
O005
C CL Characteristic Default Settings
O021
Class Data Transfer
O023
Display Class Maintenance Data File
O024
Transfer Class Data: Direct Input
S_ABA_72000139
S_ABA_72000140
S_ALR_87003718
IMG Activity:
SIMG_CFMENUO000O1CL
S_ALR_87003725
IMG Activity:
SIMG_CFMENUO000O008
S_ALR_87003732
IMG Activity:
SIMG_CFMENUO000O016
S_ALR_87003741
IMG Activity:
SIMG_CFMENUO000O002
S_ALR_87003752
IMG Activity:
SIMG_CFMENUO000SMOD
S_ALR_87003765
IMG Activity:
SIMG_CFMENUO000MERK
S_ALR_87003777
IMG Activity:
SIMG_CFMENUO000KLAS
S_ALR_87003789
IMG Activity:
SIMG_CFMENUO0002239
S_ALR_87003802
IMG Activity:
SIMG_CFMENUO000O12A
Page | 451
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
S_ALR_87003812
IMG Activity:
SIMG_CFMENUO000O003
S_ALR_87003831
IMG Activity:
SIMG_CFMENUO000O005
S_ALR_87003842
IMG Activity:
SIMG_CFMENUO000O004
S_ALR_87003852
IMG Activity:
SIMG_CFMENUO000O017
S_ALR_87003863
IMG Activity:
SIMG_CFMENUO000O006
S_ALR_87009587
S_AX6_42000002
IMG Activity: BWCLBW_CTBW
S_S6B_86000002
IMG Activity: CTWUL_LOCDEP
S_S6B_86000003
IMG Activity: CTWUL_LOCDEP
S_S6B_86000004
S_S6B_86000005
S_S6B_86000006
CLNA
Namespace f. Classes/Characteristics
CT01
Create Characteristic
CT02
Change Characteristic
CT03
Display Characteristic
CT05
Create Characteristic
CT06
Display Characteristic
CT11
Use CT12 instead
CT21
Batch Input for Characteristics
CT22
Maint. Seq. File for Characteristics
Page | 452
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
CT23
Display Chars for Change Number
CT24
Display Change Numbers Used
CT25
Where-Used List of Chars in Deps
CTCP
Copy C tables for characteristics
S_ABA_72000141
CL2A
Classification Status
CL6B
Object List
CL6D
Classes Without Superior Class
CL6M
Delete Class (with Assignments)
CL6O
Plus-Minus Object Display
CL2B
Class Types
CL6A
Class List
CL6Q
Where-Used List for Classes
CL6T
Copy Text for Classes
CLCP
Copy Classification C Tables
S_ALR_87009588
.
S_ALR_87011758
.
CL21
Display Object in Classes
CL23
Display Class for Classes
CL25
Display Objects in Class
CL26
Mass Release of Assignments
CL30
Find Objects in Classes
Required and Recommended Action(s)
Page | 453
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
No special actions required.
Related SAP Notes
Custom Code related information
SAP note:2213569
25.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 onpremise edition 1511
PPECS
Required and Recommended Action(s)
Page | 454
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
25.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
Page | 455
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
validity, lotsize interval, and a status, which blocks using the source of supply in
MRP, but not in manual sourcing.
Solution
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,
25.8 S4TWL - SAP PLM Recipe Development
Application Components:
PLM-WUI-RCP-SPE, PLM-WUI-RCP-LBL, PLM-WUI-RCP-RCP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267893
S4TWL - SAP PLM Recipe Development
Page | 456
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
•
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
Page | 457
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
25.9 S4TWL - Engineering Change Management ECR/ECO
Application Components:
PLM-WUI-OBJ-ECN, LO-ECH, CA-GTF-ECM
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 Record / Engineering Change Order functionality is no more
available with SAP S/4HANA.
Solution
Description
With SAP S/4HANA the current the Engineering Change Record / Engineering Change
Order functionality within SAP Product Lifecycle Management (SAP PLM) is not
available anymore. It is recommended for new customers to use Engineering Record
instead for tracking, approving and facilitating (change management) purposes.
Business Process related information
Managing (tracking, approving and facilitating) changes will still be possible. The
Engineering Record (only available on Web UI) shall be used for this.
The change number will serve to identify the explicit changes and the Engineering
Record is to be used to manage the whole process. The approval process, the objects to be
changed will all be part of the Engineering Record, while the change number will solely
be used to facilitate the changes after approval has been given.
Transaction not available CC31 - Create Change Request
in SAP S/4HANA onCC32 - Change Change Request
premise edition 1511
CC33 - Display Change Request
CC62 - Conversion of change packages
OS72 - ECH: Workflow for ECR/ECO
OS73 - ECH: Workflow for Object Mgmt Record
Page | 458
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
Existing and running Change Requests and Change Orders should be finished before
system upgrade is facilitated as working with these type of object will not be possible in
S/4HANA. Additional settings will be required in the system for the Customer to use the
Engineering Record. Set up Engineering Record (ER Types, status network, BRF+) and
Process Route (Activities, services, process route templates, BRF+) for tracking,
approving and facilitating business object related changes.
How to Determine Relevancy
•
•
The Engineering Change Request / Engineering Change Order functionality is
used if entries exist in DB Table AENR where the CCART field is fileld (check
with SE16)
Use ST03N (on the production system, if possible) to check transaction profile of
the complete last month, whether the following transactions have been used:
CC31, CC32, CC33, CC62, OS72, OS73
Other Terms
Change Number, Change Master, Change Management, Engineering Change Request,
Engineergin Change Order, ECR, ECO
25.10 S4TWL - 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.
Page | 459
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 onpremise 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
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
With the SAP S/4HANA op-premise 1709 release the following searches are still not
available:
•
•
Recipe search with formula item quantity
Search for any object with IDs without leading zeroes
Required and Recommended Action(s)
Customizing and Custom Code related
information
SAP Note: 2217234
How to Determine Relevancy
Page | 460
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
1. Navigate to the PLM Search customizing: Product Lifecycle Management
(PLM) -> PLM Web User Interface -> PLM Web Applications -> PLM Search ->
Define Settings for PLM Search
2. Check if any of the following columns contains entries referring to a custom
search model or a class that resides in the customer namespace:
1. Object Type of Service
2. Result Class Name
3. Key Conv. Class Name
4. Configuration ID
Other Terms
PLM, Enterprise Search
25.11 S4TWL - 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.
Page | 461
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Transaction not available CCSEQ_CSGUPD - Update Change Sequence Graph
in SAP S/4HANA onCCSEQ_CUST - Activate Change Sequence Graph
premise edition 1511
CCSEQ_CYCLE - Display Cycles
Required and Recommended Action(s)
None
How to Determine Relevancy
•
Change Sequence Graph is used if entries exist in DB Tables ENODE or EDGE
(check with SE16)
Other Terms
Change Sequence Graph, Engineering Change Management
25.12 S4TWL - 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
Page | 462
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Transaction not available CEWB (affected but not removed)
in SAP S/4HANA onpremise edition 1511
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
25.13 S4TWL - Collaborative Engineering
Application Components:
LO-CEP, LO-CEP-CTL
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
Page | 463
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
With SAP S/4HANA, on-premise edition 1511 the Collaborative Engineering is not
available. SAP recommends to evaluate SAP Mobile Documents as a substitute for
selected collaboration scenarios.
Business Process related information
The Collaborative Engineering Functionality is not available and current alternative
solutions like e.g. Mobile Documents should be evaluated as alternatives.
Transaction not available in SAP S/4HANA on-premise
edition 1511
CE01
CE02
CE03
CEP_R3_MON
Required and Recommended Action(s)
Evaluate Mobile Document as alternative for collaboration.
Related SAP Notes
Custom Code related information
SAP Note: 2226803
25.14 S4TWL - 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
Page | 464
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
In SAP S/4HANA, the integration of time analysis tools into the iPPE Workbench is not
available. This integration was previously available via the customizing transaction
OPPE07. This transaction will be removed.
Business Process related information
Transaction not available in SAP S/4HANA on-premise edition OPPE07
1511
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
25.15 S4TWL - Integration to SAP Portfolio and Project Management
Application Components:
PPM-PFM, PPM-FIO, PPM-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268020
S4TWL - Integration to SAP Portfolio and
Project 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
1.1.1.1.1
Description
SAP Portfolio and Project Management is integrated with ERP in various ways. SAP
plans to simplify and improve this integration in the way to ease configuration and
leverage HANA capabilities (Functionality available in SAP S/4HANA on-premise
Page | 465
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
edition 1511 delivery but not considered as future technology. Functional equivalent is
not available yet).
The integration topics are:
•
•
•
•
•
Integration of Portfolio Management with ERP Project System, ERP Plant
Maintenance, ERP Financials etc.
Object Links between SAP Portfolio and Project Management objects and ERP
objects (various)
Integration of Project Management with ERP Financials via the Generic Cost
Collector/Accounting Object Manager
Integration of Project Management with PLM Document Management
CATS Integration for time recording
For the time being, customers can continue using the integration as it is offered today.
Screen enhancements were done (not necessary complete) in:
•
•
•
•
Internal Order displaying data from project in PPM
Value help for internal orders to search for orders created by PPM
Project System projects displaying data from project in PPM
CATS displaying project and task from PPM
Configuration in customizing tree (see attachments)
Controlling cockpit for "Collaboration Projects" (see attachments)
(Only the first transaction "Cockpit for Controlling Integration (cProjects)" is affected,
the others are standard CO transactions.)
1.1.1.1.2
Business Process related information
No influence on business processes expected
1.1.1.1.3
Required and Recommended Action(s)
None
25.16 S4TWL - Routing Component Assignment
Application Components:
PLM-WUI-APP-RTG
Related Notes:
Note Type
Note Number
Note Description
Page | 466
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
25.17 S4TWL - Release Management Framework
Application Components:
PLM-PPM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268042
S4TWL - Release Management Framework
Symptom
Page | 467
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
25.18 S4TWL - Engineering Record
Application Components:
PLM-WUI-OBJ-ECR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268043
S4TWL - Engineering Record
Symptom
Page | 468
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 PLM Web UI Engineering Record (ER) is part of the compatibility package. The
first version 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 ER within SAP S/4HANA as long as the Compatibility
pack is supported.
Business Process related information
More information about Change Record can be found here [Link]
The following are the key available capabilities in the alternative solution Change record:
•
•
•
•
•
•
•
•
SAP Fiori UX to deliver a personalized, responsive, and simple user experience
Workflow driven change management process along with ad-hoc stakeholder
communication with Copilot
Single source of truth (centralized change data, e.g. scopes, processes, and
responsible persons)
Pre-defined process templates as well as auto-determined responsible persons
Unified My Inbox for task owners to monitor and handle their tasks
Engineering Cockpit, giving insight on business process with visualized data
Extensibility on customer attributes
Searching capabilities, e.g. searching on-going changes on a certain material
Comparing to the current capabilities of ER, there are the following major features which
are currently missing in CR:
•
•
•
Advanced Workflow Capabilities, e.g. different activities working in parallel,
digital signature, ad-hoc task and very flexible process jumping
Change Objects in Process Industry, e.g. Recipe and Specification
Allowing customers to enable new change objects
25.19 S4TWL - PLM Labeling Usage
Application Components:
PLM-WUI-RCP, PLM-WUI-RCP-LBL
Related Notes:
Page | 469
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note Type
Note Number
Note Description
Business Impact
2387911
SAP PLM Recipe Development Labeling
Usage hiding
Symptom
SAP PLM Recipe Development Labeling Usage hiding
Reason and Prerequisites
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
25.20 S4TWL - 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
Page | 470
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
25.21 S4TWL - 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
Page | 471
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
Customers moving from SAP Business Suite to SAP S/4HANA, on-premise edition 1511
can use the report /PLMI/ER_ASM_DELECTION to remove Product Assembly related
entries from the Engineering Record and Object Navigator customizing.
25.22 S4TWL - 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
Transition Worklist item is applicable in this case.
Reason and Prerequisites
Access Control Management has limitation in S/4HANA
Solution
Description
The PLM specific Access Control Management is available in the SAP S/4HANA
shipment but it has some limitations.
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
for the owning contexts, recipes, specification and document info records.
Also the Access Control List is not supported in SAP S/4HANA.
Required and Recommended Action(s)
Page | 472
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Check if Access Control Management is in use see below "How to Determine
Relevancy" chapter. If you are using Access Control Management 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
How to Determine Relevancy
This Simplification Item is relevant if ACM objects are linked to unsupported Business
Objects, thus entries exist in DB Table /PLMB/AUTH_OBSID (check with transaction
SE16)
Other Terms
PLM, ACM, Simplification, Access Control Management
25.23 S4TWL - 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
Page | 473
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Following objects are not available in SAP S/4HANA via transaction PDN
•
•
•
iPPE-objects not type of CMP-application of the product structure
o Colour nodes (type COL)
o Generic nodes (type GEN)
o Focus nodes (type FOC)
o Concept nodes (type CON)
Non-configurable part of the product structure, e.g. variant assembly
Alternatives of the product structure
Following functionalities are not available
•
•
Priority definition for nodes
Variant differentiation
The automotive scenarios provided via transaction PPE are not affected. PPE is still
available.
Transaction not available
in SAP S/4HANA onpremise 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
25.24 S4TWL - Access Control Management (ACM)
Application Components:
PLM-WUI-APP-ACC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267842
S4TWL - Access Control Management
(ACM)
Symptom
Page | 474
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Access Control Management not supported in S/4HANA
Solution
Description
The PLM specific Access Control Management is not available in the SAP S/4HANA
shipment. Access Control related UI fields are not available from the PLM objects' Web
screens. Authorization restriction is not in place so these fields would not be considered
and system won't restrict authorizations.
Also please check the related SAP Note: 2212593
Business Process related information
The unavailability of ACM in SAP S/4HANA means that instance specific control for
data access is not in place. Normal authorization object can be used via standard
transactions, like PFCG.
Required and Recommended Action(s)
Check if Access Control Management is in use see below "How to Determine
Relevancy" chapter. If you are using Access Control Management 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
How to Determine Relevancy
This Simplification Item is relevant if:
•
•
ACM objects are linked to Business Objects, thus entries exist in DB Table
/PLMB/AUTH_OBSID (check with SE16)
ACM is used if entries exist in DB Table HRP7600 where Otype=CC, as these
entries contain ACM type objects (check with SE16)
Other Terms
Page | 475
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
PLM, ACM, Simplification, Access Control Management
25.25 S4TWL - 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
With SAP S/4HANA, on-premise edition 1511 the current cFolder interfaces is not
available. SAP recommends to evaluate SAP Document Center or SAP Intelligent
Product Design 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 CFI01 – Importing Documents
in SAP S/4HANA onCFE01 – Exporting Documents
premise edition 1511
CFI02 – Importing Documents, Materials and Bills of
Material
CFE02 – Exporting Documents, Materials and Bills of
Material
CFI03 – Importing Documents, Materials, Bills of Material
and iPPE Objects
CFE03 – Exporting Documents, Materials, Bills of Material
and iPPE Objects
CFC01 – Customizing for cFolders backend integration
Page | 476
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Document Center or SAP Intelligent Product Design.
Related SAP Notes
Custom Code related information
SAP Note: 2224778
25.26 S4TWL - 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.
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.
Page | 477
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 onpremise 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.
25.27 S4TWL - 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
Page | 478
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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).
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 RMWB
Start Workbench
in SAP S/4HANA onBD_GEN_GRCP
General Recipe Distribution
premise edition 1511
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 ORCP*, RCP*, RMS*, RMX*
not available in SAP
S/4HANA on-premise
edition 1511
Required and Recommended Action(s)
Projects need to migrate their processes from PLM Recipe Management functional
capabilities to PLM Recipe Development functional capabilities.
Page | 479
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
o /PLMI/RCP_MIGRATION
Recipe
Migration
o /PLMI/RMSL_MIGRATION
Migration
of Label Sets
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
25.28 S4TWL - 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
Page | 480
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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 No influence expected since no open interfaces are available and
information
the usage is stopped before launching itself. BAPI
'EASYDMS_ECL_OPEN_DOCUMENT' will issue an error if it
is called remotely in custom code.
25.29 S4TWL - 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)
Page | 481
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Easy DMS Functionality within SAP
Product Lifecycle Management (SAP PLM) will no longer be available. As an
alternative, customers using Easy DMS may consider SAP Document Center for DMS.
Business Process related information
Business processes can be achieved by using SAP Document Center for DMS.
Transaction not available EASYDMS_CUS
in SAP S/4HANA onpremise edition 1511
Required and Recommended Action(s)
Switch to SAP Document Center for DMS which is powerful and simple.
Related SAP Notes
Custom Code related
information
Custom plugin developed (in VC++) for Easy DMS
solution has no influence as the application usage is stopped
at log-in level.
Other Terms
Easy DMS
Page | 482
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
26 Logistics – PM
26.1 S4TWL - Object List Number Field Length Extension
Application Components:
LO-MD-SN, PM-WOC-MO, LE-SHP, MM-IM, MM-PUR, PP-SFC-
EXE, QM-IM, SD-SLS, LO-HU
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 customerdefined 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.
Required and recommended action(s)
Page | 483
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
26.2 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
26.2.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.
26.2.2 Solution
Description
Remark: For the general approach regarding analytics within SAP S/4HANA see the
following analytics simplification item in cross topics area.
Page | 484
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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 multidimensional 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:
Page | 485
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
S061 Location and planning
S062 Object class and manufacturer
S063 Damage analysis 30
S064 Damage analysis
S065 Object statistics
S070 Breakdown statistics
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.
26.3 S4TWL - Download Data in MS Access out of List
Application Components:
PM, PM-EQM-LE, PM-WOC-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)
Page | 486
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Custom Code Related information:
In Case you use this functionality plan to populate your MS Access DB in a different
way.
26.4 S4TWL - Scheduling of Maintenance Plan
Application Components:
PM, PM-PRM
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)
Page | 487
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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).
26.5 S4TWL - Mobile Asset Management (MAM)
Application Components:
PM, PM-WOC-MB
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 the target architecture
within SAP S/4HANA, on-premise edition 1511. The available functional equivalent is
SAP Work Manager ( Functionality available in SAP S/4HANA on-premise edition 1511
delivery but not considered as future technology. Functional equivalent is available. ).
We plan to discontinue the Objects mentioned in the piecelist and delete these objects in
a future release of S/4
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 piecelist in any of your
Custom Applications , reports etc and replace these.
26.6 S4TWL - Batch Input for Enterprise Asset Management (EAM)
Application Components:
PM
Page | 488
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related Notes:
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
o BAPI_EQUI_CREATE
o BAPI_EQUI_CHANGE
o BAPI_EQUI_GET_DETAIL
Functional Location
o BAPI_FUNCLOC_CREATE
o BAPI_FUNCLOC_CHANGE
o BAPI_FUNCLOC_GET_DETAIL
Notification
o BAPI_ALM_NOTIF_CREATE
o BAPI_ALM_NOTIF_DATA_ADD
o BAPI_ALM_NOTIF_DATA_MODIFY
Page | 489
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
o BAPI_ALM_NOTIF_GET_DETAIL
Maintenance Order
o 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-customfields-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.
26.7 S4TWL - Change Order and Operations IW37,IW49
Application Components:
PM, PM-WOC-MO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270108
S4TWL - Change Order and Operations
transaction IW37, IW49
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
Within PM we plan to discontinue IW37, IW49 in a future release.
Currently there is no functional equivalent for enterprise asset management (EAM)
within SAP S/4HANA, on-premise edition 1511 (Functionality available in SAP
Page | 490
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
S/4HANA on-premise edition 1511 delivery but not considered as future technology.
Functional equivalent is not fully available yet.). It´s recommend to use transaction
IW37n, IW49n instead.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
In case you use the transaction IW37, IW49, please use IW37n or IW49n instead.
26.8 S4TWL - 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
You are doing a system conversion to SAP S/4HANA, on-premise edition. You are
using PM Functionaliyt fo Maintenance Planer, Worker or Supervisor deliuvered (<=
EhP4). The following SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Old WD Application covering Maintenance Worker, 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.).
We plan to discontinue this functionality in one of the next release.
Please use the new Maintenance Planner and Maintenance Worker Role which is
available in S4.
Business Process related information
Page | 491
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
No influence on business processes expected.
Required and Recommended Action(s)
Activate the Business Function to get full functionality of Maintenance Planner and
Maintenance Worker Role
•
•
•
•
LOG_EAM_SIMPLICITY_3
LOG_EAM_SIMPLICITY_4
LOG_EAM_SIMPLICITY_5
LOG_EAM_SIMPLICITY_6
26.9 S4TWL - 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
Page | 492
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
1. You have to activate the Enterprise search models
Please check our How To Guide in SCN. https://blogs.sap.com/2016/07/01/eamenterprise-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.
2. 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
Enterprise search in the Input Help you find a ppt with the configuration steps.
https://zinnovationdiscoverysupportportal.dispatcher.hana.ondemand.com/#/innovation/6CAE8B27FCC31ED
5A995CA1EED5A222A
3. In case you have mainteained special setting for Value help in Customizing under
Plant Maintenance -> Maintenance Roles -> Maintenance Worker -> Configure
Search help Assignment
o 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
26.10 S4TWL - 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
Page | 493
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Please use the tabular display options.
Page | 494
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
27 Logistics – PP
27.1 S4TWL - ERP Line-Balancing and Sequencing
Application Components:
PP-FLW, PP-FLW-LDS, PP-FLW-SEQ
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268084
S4TWL - ERP Line-Balancing and
Sequencing
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
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.
The classic sequence planning transactions LAS1, LAS2, LAS3, LAS4, LAS5 are still
available (Functionality available in SAP S/4HANA on-premise edition but not
considered as future technology. The function is part of the S/4HANA compatibility
pack. Functional equivalent is available).
Page | 495
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
Please refer to PPDS Model mix planning in help.SAP.com to get an idea of PPDS
sequence planning.
Required and Recommended Action(s)
The classic sequence planning transactions are still available. No immediate action is
required but we recommend making yourself familiar with PPDS model mix planning.
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.
27.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
Page | 496
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Production planners have to make sure material is available when needed. MRP assists
production planners with this task. The MRP run determines expected material shortages
and creates planned orders, purchase requisitions, or delivery schedule lines to cover the
expected material shortages. A shortage exists for a material if the material is subject to
demand-driven planning and if the total quantity of material requirements (sales orders,
stock transfer requirements, production requirements, and forecast requirements) up to a
certain point in time exceeds the total quantity of material receipts (inventory, production
orders, purchase orders, delivery schedule lines, firmed planned orders, and firmed
purchase requisitions).
SAP S/4HANA features MRP Live (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:
•
•
•
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 as an interim solution(Functionality available in SAP
S/4HANA on-premise edition 1511 delivery but not considered as future technology.),
which at the moment has to be used for creating MRP lists.
Business Process related information
MRP live differs from classic MRP in the following aspects:
•
MRP live does not write MRP lists.
•
Multi-level, make-to-order planning (transaction MD50) is not optimized for
HANA.
Individual project planning (transaction MD51) is not optimized for HANA.
The creation indicator for purchase requisitions is not available in MRP Live.
MRP Live always creates purchase requisitions if the material is procured
externally.
•
•
Page | 497
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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.
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 allows you
to change the MRP element type of a material receipt to be created by MRP. Implement
Page | 498
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
this BAdi if you want MRP live to create planned orders rather than purchase requisitions
for externally procured materials.
Required and Recommended Action(s)
Classic MRP is still available in the SAP S/4HANA compatibility pack. You can start
using MRP live rather than the classic MRP at any time. Therefore, there is no need to
become active on the start release. Before you start using MRP live, check the following:
•
•
Re-implement BAdI implementations and extensions of the classic MRP as
AMDP BAdIs.
Make yourself familiar with the MRP apps and check whether they can be used as
a successor to MRP lists if you used MRP lists in the past.
Related SAP Notes
Conversi No
on PreChecks
BADi Many calculations in MRP Live are implemented in SQLScript/CDS
related views/AMDPs running on the database server as opposed to classic ABAP code, which
informat is performed on the application server. Enhancements or BAdI implementations of the
ion
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 if classic MRP does not use the HANA optimization - otherwise BAdI
MD_ADD_ELEMENTS has to be used instead of BAdI
MD_CHANGE_MRP_DATA for material B.
A new set of AMDP BAdIs will be available for MRP Live from SAP S/4HANA onpremise edition 1603. BAdI implementations of the classic MRP have to be translated
into AMDP BAdI implementations if still required. This affects the following BAdIs:
Purpose
Classic BAdI or
extension
AMDP BAdI
Subcontract MD_SUBCONT_LOGI PPH_MRP_RUN_BADI =>
ing logic C
MDPS_ADJUST
Comment
See
simplification
item
2.1.11.1PPMRP Subcontractin
g
Page | 499
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Reading
material
receipts
MD_CHANGE_MRP_ PPH_MRP_RUN_BADI =>
and
DATA
MDPS_ADJUST
requiremen
ts
Scheduling
of stock
MD_STOCK_TRANSF PPH_MRP_RUN_BADI =>
transfer
ER
MDPS_ADJUST
requiremen
ts
Userdefined
MD_ADD_ELEMENT PPH_MRP_RUN_BADI =>
MRP
S
MDPS_ADJUST
elements in
MRP
Planned
independen
t
PPH_MRP_RUN_BADI =>
requiremen MD_PIR_FLEX_CONS
MDPS_ADJUST
t
consumptio
n
PPH_MRP_LOTSIZING_BADI
Change
MD_MRP_PARAMET => LOT_SIZE_CALC
planning
PPH_MRP_NETTING_BADI =>
ERS
parameters
NET_REQ_CALC
Change
MRP list
MRP lists are
not available
by MRP Live
MD_MRP_LIST
Change
purchase MD_PURREQ_CHAN
requisitions GE,
created by MD_PURREQ_POST
MRP
Change
MD_PLDORD_CHAN
planned
GE,
orders
created by MD_PLDORD_POST
MRP
PPH_MRP_RUN_BADI =>
PURREQ_BEFORE_UPDATE_A
DJUST
PPH_MRP_RUN_BADI =>
PLANORD_BEFORE_UPDATE_
ADJUST
Source of
supply
determinati
on in MRP
MD_MODIFY_SOUR
CE,
PPH_MRP_SOURCING_BADI
MD_MODIFY_PROD => SOS_DET_ADJUST
VERS
Package
size for
MD_MRP_RUN_PAR MRP_DISPATCHER_BADI =>
ALLEL
DISPATCH_CREATE_TASK
See
simplification
item
2.1.11.7Simpl
ified Sourcing
Page | 500
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
parallel
processing
Material
PPH_MRP_NETTING_BADI =>
selection
Extension M61X0001 AT_PLANNING_FILE_ENTRIE
for MRP
S_READ
run
Table
MRP live is still writing most of the classic ERP tables. Most importantly planned
related orders, purchase orders, and delivery schedule lines are still written into the same
informat tables. The classic MRP was writing data into the following tables, which are no longer
ion
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
Materials MRP
was not able to
plan
MDKP with
Table PPH_DBVM with MSGID
selection
populated
group 8
populated
Various material
master attributes
controlling MRP
functions such as
lotsizing
MDKP
End of MRP
planning time
fence
MDKP field Add MARC-FXHOR to
FIXTR
PPH_DBVM-DSTMP
MRP list
MDTB
call function
module MD_MDPSX_READ_API
MRP planning file
DBVM,
MDVM
Table PPH_DBVM
MRP runtime
statistics
MONI
Table PPHMRPLOGITEM
Comment
Table MARC
See
note 2268088
Other Terms
MRP live, MD01n
27.3 S4TWL - Planning File
Application Components:
PP-MRP, PP-MP-LTP
Related Notes:
Page | 501
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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,
or if master data like the BOM or the product master was changed. The planning file
stores the materials that have to be planned by the next MRP.
Description
The new planning file does not have columns for low level code and record type. This
information does not have to be copied from the material master into the planning file
when updating the planning file. The MRP planning run reads the low level code of all
materials requiring planning from the material master.
Reason
In SAP S/4HANA the planning file was optimized for simplified update logic,
consistency and for update performance.
Business Process related information
In the classic Business Suite, reports RMMDVM10 and RMMDVM20 made a first setup
of planning file entries and checked planning file consistency for operative planning. In
SAP S/4HANA, run report PPH_SETUP_MRPRECORDS instead. For long-term
planning, the reports RMMDVL10 and RMMDVL20 are replaced by the report
PPH_SETUP_MRPRECORDS_SIMU.
SAP S/4HANA, on-premise edition 1511 no longer supports net change planning in the
planning horizon (processing key NETPL). MRP always determines material shortages
for all known material requirements. MRP can no longer cover only the material
Page | 502
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 onpremise edition
1511
Reports (not
available in SAP
S/4HANA)
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).
RMDBVM00, RMDBVM10 (for conversion MDVM/MDVL into
DBVM/DBVL and back),
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).
Related SAP Notes
Conversion Pre-Checks
Custom Code related
The original planning files MDVM/MDVL and DBVM/DBVL
information
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
Page | 503
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
27.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.
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.
Page | 504
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
27.5 S4TWL - Forecast Based Planning
Application Components:
MM-CBP-CBP, PP-MRP
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
Page | 505
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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
Required and Recommended Action(s)
No mandatory action
27.6 S4TWL - Demand Forecasting
Application Components:
PP-MP-MFC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268100
S4TWL - Demand Forecasting
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
Demand forecasting estimates future material demand based on historic material
consumption data. The material demand forecast can be copied into planned independent
requirements or it can be used to compute safety stocks and reorder points.
Classic demand forecasting copies the consumption history into an ABAP application
server, performs the forecasting algorithm in ABAP and writes the result back into the
database. Copying data between database server and ABAP application server takes time.
Page | 506
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
HANA has a built in library of forecasting algorithms, which could be utilized for
forecasting material demand. A future demand forecasting solution will probably perform
the forecasting algorithm in HANA utilizing HANA's forecasting library.
Transactions MP30, MP31, MP32, MP33, MP38, and MP39 are still available in SAP
S/4HANA on-premise edition 1511(Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional
equivalent is not available yet). Currently there is no functional equivalent available
within SAP S/4HANA, on-premise edition 1511.
Business Process related information
Business processes will not change if the forecasting algorithm is changed.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related Custom code or BAdi-implementations in material demand
information
forecasting will not be called when demand forecasting is
performed in HANA.
27.7 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
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
Page | 507
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
BAUTL, MATNR, EMATNR,
COCF_SN_CREATE_EAM RIQS5
RM_MATNR
BAUTL, MATNR, EMATNR,
COCF_SN_CREATE_PP
RIQS5
RM_MATNR
MATNR, EMATNR,
COCF_SN_GET_LIST_EAMCOCF_S_SN_LIST_FLAT
RM_MATNR
MATNR, EMATNR,
COCF_SN_GET_LIST_PP COCF_S_SN_LIST_FLAT
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
27.8 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)
Page | 508
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Standard value calculation with CAPP can be used to adjust standard values determined
using any of the above procedures depending on some context 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
CAPP has been used to multiply standard values for duration with a season factor
Description
In SAP S/4HANA CAPP is available, but defined as "not strategic any more". Functional
equivalent is not available. It is part of the compatibility package. See SAP note 2269324
– “Compatibility Scope Matrix for SAP S/4HANA, on-premise edition” .
Required and Recommended Action
You can continue to use CAPP after migrating to SAP S/4HANA.
Page | 509
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Future Direction
In a future release SAP intends to equip routing operations with operation activities (subnodes to routing operations) 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.
Other Terms
CE11. CE12, CE13, CE21, CE22, CE23, CE31, CE32, CE33, CE41
27.9 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). Currently only very few customers (less than 5 known) still
use ABAP list-based PI sheets. The code needed for list-based PI sheets is still available
in SAP S/4HANA on-premise edition 1511 but will be not available in a future release.
Use browser-based PI sheets for the time being.
Page | 510
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
Customers that used ABAP list-based PI sheets temporarily have to switch to browserbased PI sheets: The corresponding control recipe destinations of type 1 (ABAP-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 that include the
usage of ABAP-list based PI sheets. No effects on business processes are expected.
Transactions CO55, CO60, CO60XT, CO64, and CO67 are still available but will be
replaced in a future release when a successor for browser-based PI sheets is available.
The possibility to select ABAP list-based PI sheets is still available in SAP S/4HANA,
on-premise edition 1511 but will be not available in a future release.
Required and Recommended Action(s)
Start exchanging control recipe destinations of type 1 (ABAP list-based PI sheets) with
master recipes (process orders). Create and send test control recipes for the exchanged
control recipe destinations. Check the browser-based PI sheets that are generated from
the test control recipes.
Recommended:
•
•
Use XStep-based process instructions instead of characteristic-based process
instructions
Replace generation scopes and filters that are defined in customizing (of the
control recipe destination) with XStep-based generation scopes and valuation
symbols
27.10 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
Symptom
Page | 511
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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).
27.11 S4TWL - 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:
•
Provide the sophisticated planning functionality for subcontracting components
using subcontracting MRP area without the necessaty to maintain appropriate
material master data
Page | 512
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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-tostock 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.0logic)
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/supplierspecific 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
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)
Page | 513
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
27.12 S4TWL - Digital Signature
Application Components:
CA-DSG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268120
S4TWL - Digital Signature
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
Digital signature legacy functionality is based on function modules of package CJ in
SAP_APPL. The code needed for the legacy functionality is still available in SAP
S/4HANA, on-premise edition 1610 (Functionality available in SAP S/4HANA onpremise edition 1610 delivery but not considered as future technology. Functional
equivalent is available).
Since SAP_ABA 6.20 the successor functionality (class-based signature tool, package
DS) is available. Implementations of digital signature functionality using class-based
signature tool is easier to establish. Use the class-based signature tool instead of the
legacy functionality.
Business Process related information
Page | 514
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
No influence on business processes expected. Transaction DSAL is still available in SAP
S/4HANA, on-premise edition 1610 but will be replaced by a successor functionality in a
future release.
Required and Recommended Action(s)
Check before the upgrade that all open signature processes are completed. This is
generally relevant for all signature processes, independent of the signature functionality
used (legacy or class-based signature tool).
Related SAP Notes
SAP Note
SAP Note: 700495
27.13 S4TWL - Electronic Records
Application Components:
LO-ELR
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268131
S4TWL - Electronic Records
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
Electronic records (LO-ELR) provide tools for evaluation of the logs that can be written
for changes in database table content. These logs are stored in database table
DBTABLOG. It is also possible to display change documents and logs of long text
changes. Electronic records are part of the SAP functionality that supports legal
compliance in the regulated environment (production of active ingredients and
pharmaceuticals).
Page | 515
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Since SAP_BASIS 7.03, the successor functionality (NetWeaver-based audit trail) is
available in SAP_BASIS (package S_AUT). In addition to the functionality of the
electronic records, the NetWeaver-based audit trail provides the following functions:
•
•
•
Access to archived change documents and database table records
Compliance with the Information Lifecycle management (ILM) standard of SAP
Improved functionality to define custom selections on database table logs and
change documents
The NetWeaver-based audit trail provides a migration report to transfer the customizing
settings of the electronic records.
The functionality of electronic records is still available in SAP S/4HANA, on-premise
edition 1610 (Functionality available in SAP S/4HANA on-premise edition but not
considered as future technology. Functional equivalent is available).
Business Process related information
No changes to business processes. Transactions AUT01 - AUT05, AUT10 are still
available in SAP S/4HANA, on-premise edition 1610 as an interim solution.
Required and Recommended Action(s)
If necessary, transfer the customizing settings using SAP report
AUT_MIGRATE_ENHAT_DB_DATA in old release before migrating to SAP
S/4HANA, on-premise edition 1610.
27.14 S4TWL - 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.
Page | 516
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
27.15 S4TWL - MiniApps PP-PI
Application Components:
PP-PI-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271204
S4TWL - MiniApps PP-PI
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
Page | 517
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
None
27.16 S4TWL - 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 (PP-PIPMA)
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, on-premise edition 1610 (Functionality
available in SAP S/4HANA on-premise edition but not considered as future technology.
Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
None
27.17 S4TWL - Campaign Weighing and Dispensing
Application Components:
PP-PI-PMA-CWD
Related Notes:
Page | 518
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 was not used productively. The
corresponding xMII content is not available anymore. The functionality is still available
in SAP S/4HANA, on-premise edition 1511(Functionality available in SAP S/4HANA
on-premise edition 1511 delivery but not considered as future technology. Functional
equivalent is available)
Business Process related information
No changes to business processes. The weighing solution of the SAP PP-PI consulting
organization does support the required functionality. Transaction CMATRANGE is still
visible in SAP S/4HANA, on-premise edition 1511.
Required and Recommended Action(s)
None
27.18 S4TWL - 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 to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Page | 519
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Description
The functionality of production campaign is still available in SAP S/4HANA, on-premise
edition 1611 (Functionality available in SAP S/4HANA on-premise edition 1611 delivery
but not considered as future technology. SAP S/4HANA has PP/DS built in and PP/DS
supports campaign planning. Future campaign planning solutions will be built on PP/DS.
Business Process related information
Transactions CPCN, PCA1-PCA3, and PCCO are still available.
27.19 S4TWL - 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, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The functionality of electronic batch record (EBR) is required by customers who work in
a regulated environment (production of active ingredients, pharmaceuticals, and so on).
The content of the EBR is stored in optical archives (using SAP ArchiveLink
technology). EBR Content is revisited during external audits. The content has to be
available for 10 years on average.
The functionality is still available and working in SAP S/4HANA, on-premise edition
1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is not available yet).
Business Process related information
Page | 520
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
No influence on business processes expected.
Required and Recommended Action(s)
Before upgrading to SAP S/4HANA, on-premise edition 1511, it is recommended that
you complete all open approval procedures for electronic batch records.
27.20 S4TWL - 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 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 process messages is still available in SAP S/4HANA, on-premise
edition 1511(Functionality available in SAP S/4HANA on-premise edition 1511 delivery
but not considered as future technology. Functional equivalent is not available yet).
Business Process related information
No influence on business processes expected.
27.21 S4TWL - Control Recipes/Instructions
Application Components:
PP-PI-PMA-RCP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270233
S4TWL - Control Recipes/Instructions
Page | 521
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 control recipes and control instructions is still available in SAP
S/4HANA, on-premise edition 1511(Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional
equivalent is not available yet).
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
Not required.
27.22 S4TWL - 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:
Page | 522
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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-areaspecific MRP type 'ND' (no MRP) can be used instead of materials with a storage
location excluded from MRP. Materials with MRP-area-specific MRP type 'VB' (reorder
point planning) can be used instead of materials with separately planned storage
locations. The storage location functionality is a subset of the MRP areas capabilities.
Description of Simplification
The S/4HANA MRP only plans on plant and MRP area level. Planning on storage
location level is not available in SAP S/4HANA, on-premise edition 1511.
Reason
The reason for this change are:
•
•
•
The MRP logic is simplified. There is only one solution for planning on storage
location level
The MRP area logic is more advanced than the logic for planning on storage
location level. All MRP types and lot-sizing procedures are possible on MRP area
level
The system creates planning file entries on plant and MRP area level. If planning
is required on MRP area level, then the system only plans the affected MRP area.
The system does not create planning file entries on storage location level and it
did not do so in SAP ERP. The SAP ERP MRP had to plan all separately planned
storage locations and the plant level every time inventory or an expected receipt
was changed in a single separately planned storage location. Planning on MRP
area level is more efficient
Business Process related information
Page | 523
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Custom Code related information
SAP Note: 2216528
SAP Note: 2227579
See SAP Note 2466264 for S/4 conversion with storage location MRP for a Retail
system.
27.23 S4TWL - Process Operator Cockpits
Application Components:
PP-PI-PMA-OPC
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, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
The functionality of process operator cockpits (POC) is still available in SAP S/4HANA,
on-premise edition 1511(Functionality available in SAP S/4HANA on-premise edition
Page | 524
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
1511 delivery but not considered as future technology. Functional equivalent is not
available yet).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Not required.
27.24 S4TWL - 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 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 material identification/reconciliation is still available in SAP
S/4HANA, on-premise edition 1511(Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional
equivalent is not available yet).
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
Not required
Page | 525
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
27.25 S4TWL - 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 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 flow manufacturing including line design and sequence planning is
still available in SAP S/4HANA, on-premise edition (Functionality available in SAP
S/4HANA on-premise edition but not considered as future technology. Functional
equivalent is available). 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.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
SAP recommends to use model mix planning and sequencing in PPDS.
Related SAP Notes
Custom Code related ERP coding enhancements will not be supported after replacement
information
with PPDS.
27.26 S4TWL - Process Flow Scheduling (PP-PI)
Page | 526
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Application Components:
PP-PI-PMA
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2273079
S4TWL - Process Flow Scheduling (PP-PI)
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.
27.27 S4TWL - 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
Page | 527
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
Reduced complexity in capacity planning and in reporting on capacities utilization
and capacity load
Better performance of scheduling
Description
SAP ERP production versions allowed you to reference routings, rate routings, and
rough-cut planning profiles in parallel. MRP then created capacity requirements for
detailed planning, 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 jobshop 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
Page | 528
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 jobshop 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 "Ratebased planning".
Related SAP Notes
Conversion Pre-Checks
Pre-Check class CLS4H_PP_MRP
27.28 S4TWL - Planning Horizon
Application Components:
PP-MP-MPS, PP-MP-LTP, 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.
Page | 529
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Customers can build their own planning application using the
information
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.
27.29 S4TWL - 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.
Page | 530
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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, as part of the S/4HANA compatibility pack.
27.30 S4TWL - 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
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
Page | 531
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 customerswitchable and obsolete:
•
•
•
•
•
LOG_PP_INTELI_01 (Power list for process manufacturing)
LOG_PP_PRSP (Portal for production supervisor)
EA-SCM
LOG_PP_BATCH_HISTORY
LOG_PP_CFB (Food and Beverage Solution)
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, onpremise 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”
Customer having one or all of these business functions switched “ON” in Business Suite
start release can execute the system conversion. Nevertheless the functionality related to
these business functions is not available within SAP S/4 HANA, on-premise edition 1511
– FPS1.
Customers having none of these business functions switched “ON” in Business Suite start
release cannot activate these business functions after the system conversion to SAP S/4
HANA, on-premise edition 1511 – FPS1.
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".
Page | 532
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Enterprise extension EA-SCM offered various functions like
•
•
•
•
Direct Store Delivery DSD
Cross Docking
Vehicle Space Optimization
Logistical Value Added Services
Successor functions for cross docking and vehicle space optimization are available in
transportation management SCM-TM.
Originally enterprise extension EA-SCM also swtiched 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.
The functions switched by business function LOG_PP_BATCH_HISTORY will be
replaced by global batch traceability in a future release.
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 were reports CFB_PV_MRP_PREP_MIXCAL and
CFB_PV_MRP_RELEASE_LOCK allow 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.
27.31 S4TWL - External Interfaces in PP
Application Components:
PP-MES, LO-SCI
Related Notes:
Page | 533
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
LPOXLPO Lean planning and operations LPO was an algorithm for levelling
Interface
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
This interface used an outdated interface technology (flat file)
Interface
KK5
This interface used an outdated interface technology (flat file)
Interface
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
project teams looking for ways to connect an external system and it facilitates the further
development of the POI interface.
Business Process related information
Page | 534
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Use the POI interface or the MES interface to connect SAP S/4HANA to an MES system
or a planning system. For details, see the MES integration documentation and the POI
documentation
Transaction not available in SAP
S/4HANA on-premise edition 1511
RFC-enabled function modules are not
available in SAP S/4HANA
CBP1, CBP2, CBP3, CBP4, CBP5, CBP6, CBP7,
CBPV, CBCACT, CBCAT, CBCBRG, CBCF,
CBCMLGMRP, CBCMLGSOP, CBCMLS,
CBCMOD, CBCMSV, CBCMTG, CBCONFMRP,
CBCONFSOP, CBCPAR, CBCS, CBCSTEP,
CBPRO, PFSE, PX01, PX02, PX03, PX04, PX05
LPO_BOM_GETDETAIL,
LPO_DEMANDS_GETLIST,
LPO_ITEM_GETDETAIL, LPO_MATDATA_FIND,
LPO_MATDATA_GETDETAIL,
LPO_PLANT_GETLIST,
LPO_PRODCOMPLETE_GETLIST,
LPO_PRODCONF_CREATE,
LPO_PRODSHIPMENT_GETLIST,
LPO_ROUTE_GEDETAIL,
LPO_SCHEDULEPLAN_UPDATE,
LPO_STOCK_GETLIST,
LPO_WORKCENTER_FIND,
LPO_WORKCENTER_GETDETAIL,
CBP_MRP_DEMORDERLIST_GET_RFC,
CBP_MRP_DEMORDER_GET_RFC,
CBP_MRP_MANORDERLIST_GET_RFC,
CBP_MRP_MANORDER_GET_RFC,
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.
Page | 535
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
Custom Code related information
SAP Note: 2226966
27.32 S4TWL - 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.
Solution
Description
The graphical planning table (also known as graphical planning board or Gantt chart) can
be used for capacity load levelling and sequence planning. The graphical planning table is
still available in SAP S/4HANA, but not considered as the target architecture. Currently
there is no functional equivalent available within SAP S/4HANA, on-premise edition
151(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is not available yet).
Business Process related information
The future graphical planning table implementation will support the basic features like
changing operation start times or resources by drag and drop. The influence on business
processes should therefore be minimal. It will however not be possible to translate
customizing and personalization of the classic graphical planning table into a UI
configuration of a future graphical planning table.
Required and Recommended Action(s)
Invest reasonably in the classic planning board
Page | 536
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
27.33 S4TWL - 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.
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 multidimensional 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
Page | 537
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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/9d794cbd48c648bc8a176e422772de7e/1708%20500/enUS/d12d2a589aa80a02e10000000a44147b.html
Package PPH_ANALYTICS contains CDS views, which you can use to implement your
own analytical queries.
Custome Code related information
Page | 538
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 will be replaced by CDS views providing more or less the same information
but with different column names and structures.
27.34 S4TWL - Sales and Operation Planning
Application Components:
PP-SOP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2268064
S4TWL - Sales and Operation 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
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 &
Page | 539
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
27.35 S4TWL - 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
Page | 540
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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
receipt. After lot sizing, the planned material receipts with the requirement date and
quantity are known. Subsequently sourcing determines whether the required quantity is
manufactured or purchased and from which supplier the material is purchased.
Description of Simplification
The Basic idea of this simplification is a reduced set possible sources of supply. SAP
S/4HANA supports the following types of sources of supply:
•
•
•
•
Production versions
Delivery schedules
Purchasing contracts
Purchasing info records
Sources of supply have a common set of attributes like a temporal validity interval and a
quantitative validity interval.
Sourcing selects valid sources of supply with the following conditions:
•
•
The source of supply is a production version
o and the procurement type of the material is either 'E' (in-house production)
or 'X' (Both procurement types)
o and the production version is neither "Locked for any usage" nor "Locked
for automatic sourcing"
o and the planned material receipt's quantity is inside the quantity range of
the production version
o and the planned material receipt's delivery date is in the validity period of
the production version
The source of supply is a purchasing info record
o and the procurement type is 'F' (external procurement)
o and the purchasing info record is flagged for "Relevant for automatic
sourcing"
o and the planned material receipt's quantity is inside the quantity range of
the purchasing info record
o and the planned material receipt's delivery date is in the validity period of
the purchasing info record
Page | 541
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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
Material master attribute
"Selection Method" MARCALTSL determines if MRP
finds a BOM via the BOM's
validity period, the BOM's
quantity range, or via
production version
SAP S/4HANA Logic
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-toproject bills of material, but
production versions are required to
select routings also if make-toorder or make-to-project BOMs are
used.
The order type attribute
Production versions are the only
"Routing selection" T399X- source of supply for in-house
ARBPA determines how a production. A production version
routing is determined during references a routing. This routing is
production order creation.
used to create production orders
The attribute can be defined
in customizing transaction
OPL8.
The production version has a MRP only selects production
locking indicator with values versions that are neither 'Locked for
'Locked' and 'Not locked'.
any usage' nor "Locked for
MRP only selects production automatic sourcing."
versions that are not locked.
Reason
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
Simplification of the sourcing
logic
The new status "Locked for
automatic sourcing"
corresponds to the "Relevant
for automatic sourcing"
indicator on the purchasing
info record (Symmetry); you
can use one production
Page | 542
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Phantom assemblies are
exploded with the
method defined in the
phantom assembly's material
master attribute MARCALTSL.
version (maybe with an
artificial routing) as the
default for new planned
orders and manually dispatch
these planned orders to proper
lines/work centers
Simplified sourcing logic and
the possibility to synchronize
BOM explosion on several
BOM levels.
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.
Subcontracting purchase
Production versions are the only
Simplified sourcing logic and
requisitions are exploded
source of supply for subcontracting. the possibility to define a
with the method defined in If you use subcontracting purchasing supplier-specific production
the material master attribute info records to define the supplier, version. Different suppliers
MARC-ALTSL
you should define the production
may need different
version in the purchasing info
subcontracting components
record. In all other cases, the system from the client while
selects the material's production
procuring the other parts from
versions, also for subcontracting
elsewhere
MRP only selects purchasing Purchasing info records are a source Simplification of the sourcing
info records if a source list of supply in their own right. MRP logic: It is not required to
entry exists that references selects purchasing info records if the create a source list entry on
the supplier referenced in the "relevant for automatic sourcing"
top of the purchasing info
info record
indicator is set in the purchasing info record
record
MRP uses source lists to
Source lists are not considered in the Optionally, source lists can be
determine vendors,
S/4HANA on-premise edition 1511 used to temporarily block a
contracts, or delivery
until SP01.
source of supply or MRPschedules
enable it only for a limited
In later releases source lists can be period of time.
used to provide additional
information for sources of supply.
For example, the source list may be
used to block a source of supply or
MRP-enable it only for a limited
period of time.
Page | 543
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Alternatively quota arrangements
can be used as a workaround.
MRP only considers quota MRP considers quota arrangements In the early days of MRP,
arrangements if the material always. It is not required to switch it reading and considering quota
master attribute "Quota
on in the material master
arrangements was expensive.
arrangement usage" MARCMARC-USEQU was a
USEQU is set and the quota
performance measure, with
arrangement usage
which you could switch off
configuration includes MRP
quota arrangements in MRP
to improve performance.
MRP in HANA does not
suffer much from considering
quota arrangements.
Purchase order creation only Purchase order creation and update Simplified sourcing logic.
considers quota
as well as purchase requisition
Quota arrangements are used
arrangements if the material creation and update always consider if they exist.
master attribute "Quota
and update quota arrangements. It is
arrangement usage" MARC- not required to switch usage of quota
USEQU is set and the quota arrangements on in the material
arrangement usage
master
configuration includes
purchase orders
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 inhouse 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
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
Page | 544
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 545
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code SAP Note: 2226333
related
information 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
27.36 S4TWL - 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, on-premise edition. 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 on-premise edition (Functionality available in SAP
S/4HANA on-premise edition but not considered as future technology. Functional
equivalent is not available yet). There is no functional equivalent as alternative available
within SAP S/4HANA, on-premise edition.
Browser-based Process Instruction Sheets (PI-Sheets) and electronic work instructions
(EWI) are based on a framework that allows the creation of worker UIs optimized for the
needs of individual workers. The content of the PI sheets/EWI is rendered as plain
HTML and displayed in the SAP HTML Viewer of ABAP dynpros. It requires
SAPWinGUI as UI technology and does not work with SAPWebGUI. Because
SAPWinGUI is used, the browser-based PI sheets and EWIs are dependent on MS
Internet Explorer (technical prerequisite for HTML viewer).
Page | 546
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Content of browser-based PI sheets and EWIs is defined using process instruction
characteristics (XStep-based process instructions or characteristic-based process
instructions [only PI sheets]). Based on the process instruction content, the control
recipes/control instructions are created. If the control recipes/instructions belong to the
control recipe destination of type 4, the corresponding browser-based PI sheet/EWI is
created when the control recipe/instruction is sent.
The rendered HTML content of browser-based PI sheets and EWIs uses XSL and CSS.
SAP standard XSL and CSS can easily be exchanged by custom style sheets. This allows
easy custom adoption of the UI at the customer.
Browser-based PI sheets are used in the regulated environment (pharma production, and
so on) to control and track the production execution. They can be archived to optical
archives as part of the electronic batch record (EBR) to ensure compliant manufacturing
(comply with US CFR21 part 11 and so on).
Starting with SAP R/3 4.6 C, formerly used ABAP-list based process instruction sheets
have been replaced by browser-based PI sheets (see SAP Note 397504 - Support for
ABAP list-based PI sheet). Related functionality is still part of SAP ECC and S/4 ->
separate simplification item.
Business Process related information
A future production operator UI will be built using state-of-the-art UI technology. It will
not be possible to translate the UI configuration of browser-based PI sheets/EWIs into a
UI configuration of a future worker UI. It has to be checked if the XSteps (the building
blocks for browser-based PI sheets/EWIs) can be used as the basis for generating modern
worker UIs.
Required and Recommended Action(s)
You can still use PI-sheets using SAP-GUI for Windows.
Invest reasonably in electronic work instructions and browser-based PI sheets.
Related SAP Notes
Custom Code related
information
Enhancements and modifications of the browser-based
PI sheets/EWIs will not work for future worker UIs.
27.37 S4TWL - Internet Kanban
Page | 547
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 548
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code related information
SAP Note: 2228178
Page | 549
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
28 Logistics – PP/DS
28.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 system conversion 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: Conversion from S/4HANA for Production Planning and Detailed Scheduling
(PP/DS) to SAP S/4HANA 1809.
Prerequisite: Target release is SAP S/4HANA 1809.
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
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.
Page | 550
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Other Terms
Page | 551
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
PP/DS
PPDS
S/4HANA 1809
Order Publishing
Page | 552
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
29 Logistics – PS
29.1 S4TWL - Simplification of Date Planning Transactions
Application Components:
PS-DAT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267188
S4TWL - Simplification of Date Planning
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
There are currently multiple (partially redundant) transaction available to plan dates in
projects. It´s the target to have to simplify the related transaction in future. Accordingly
the recommendation is to use the Project Builder transaction CJ20N for this business
requirements even if other transactions are still available with SAP S/4HANA
1511(Functionality available in SAP S/4HANA 1511 delivery but not considered as
future technology. Functional equivalent is available.).
For cross network scheduling still transactions CN24 and CN24N are available with SAP
S/4HANA 1511, however, these transactions are planned to be replaced by other,
simplified cross project / network scheduling functions in future and hence are not the
target architecture as well.
Overall hence the following date planning / scheduling transactions are categorized not as
the target architecture:
•
•
•
•
•
•
•
•
CN24N Overall Network Scheduling
CN24 Overall Network Scheduling
CJ21 Change Basic Dates
CJ22 Display Basic Dates
CJ23 Change Forecast Dates
CJ24 Display Forecast Dates
CJ25 Change Actual Dates
CJ26 Display Actual Dates
Page | 553
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
CJ29 Update WBS (Forecast)
Business Process related information
The currently parallel (partly redundant) transactions for date planning and scheduling
are still available with SAP S/4HANA 1511 but they are not the target architecture.
Customer invest (for example related custom code or new end user knowledge transfer)
need to consider this.
Required and Recommended Action(s)
End user knowledge transfer required to switch from multiple date planning transactions
to single maintenance transaction CJ20N.
29.2 S4TWL - Workforce Planning
Application Components:
PS-CRP-WFP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267189
S4TWL - Workforce 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
There are currently several workforce planning functions such as usage of PS teams and
transactions CMP2/CMP3/CMP9 available. These traditional transactions are still
supported with SAP S/4HANA 1511 in project system but they are not considered as the
target architecture (Functionality available in SAP S/4HANA 1511 delivery but not
considered as future technology. Functional equivalent is not available yet.). It´s the
target to have simplified and improved ways of workforce planning available in future.
The following transactions are hence categorized not to be the target architecture:
Page | 554
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
CMP2 Workforce Planning: Project View
CMP3 Workforce Planning: Work Center View
CMP9 Workforce Planning - Reporting
Business Process related information
Still the existing workforce planning functions can be used. However, these functions and
related transactions are not the target architecture any longer and might be replaced in
future by other solutions which might not provide exactly the same functional scope of
currently existing functions.
Required and Recommended Action(s)
None
29.3 S4TWL - Progress Tracking & Monitoring Dates
Application Components:
PS-PRG-TRC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267190
S4TWL - Progress Tracking & Monitoring
Dates
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
Current progress tracking and project monitoring function in Project System are still
available with SAP S/4HANA 1511 but not considered as the target architecture
(Functionality available in SAP S/4HANA 1511 delivery but not considered as future
technology. Functional equivalent is not available yet.). It is recommended not to
continue to enable progress tracking for PS objects and project monitoring function. It is
the intention in future to offer a simplified solution for this business requirements.
The following transactions are hence categorized not to be the target architecture:
Page | 555
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
NTWXPD Progress Tracking: Networks
WBSXPD Progress Tracking: WBS
NWTM Monitoring Network Dates
ACOMPXPD Progress Tracking Evaluations
AXPD Progress Tracking Evaluations
COMPXPD Progress Tracking for Components
DEXP Expediting
EXPD Expediting
Business Process related information
Still the existing progress tracking and monitoring dates functions can be used. However,
these functions and related transactions are not the target architecture and might be
replaced in future by other solutions which might not provide exactly the same functional
scope of currently existing functions.
Required and Recommended Action(s)
None
29.4 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
since the claim functionality is categorized not as the target architecture (see note
2267169).
Page | 556
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
No influence on business processes expected
Required and Recommended Action(s)
•
•
It is recommended using Project Issue and Change Management functionality and
not PS claim Management for appropriate business requirement.
Knowledge Transfer to key- and end-user
29.5 S4TWL - Project Reporting
Application Components:
PS-IS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267286
S4TWL - Project Reporting
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
Current project reporting and analytic functions in Project System (PS) are still available
with SAP S/4HANA 1511 but not considered as the target architecture (Functionality
available in SAP S/4HANA 1511 delivery but not considered as future technology.
Functional equivalent is not available yet.). It is intended to offer a simplified and even
more flexible solution leveraging SAP HANA capabilities in an optimized way for this
business requirements in future. Please note that for example in Financials partly already
simplified reports exist, which could be used as replacements for certain PS reports.
Please double check also the SAP Fiori apps for Project System available in the
latest SAP S/4HANA releases for replacement options for some transactions listed below.
The following transactions are hence categorized not to be the target architecture:
•
•
•
CN40 Project Overview
CN41 Structure Overview
CN42 Overview: Project Definitions
Page | 557
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CN43 Overview: WBS Elements
CN44 Overview: Planned Orders
CN45 Overview: Orders
CN46 Overview: Networks
CN47 Overview: Activities/Elements
CN48 Overview: Confirmations
CN49 Overview: Relationships
CN50 Overview: Capacity Requirements
CN51 Overview: PRTs
CN52 Overview: Components
CN53 Overview: Milestones
CN60 Change Documents for Projects/Netw.
CN70 Overview: Batch variants
CN71 Create versions
CNB1 Purchase requisitions for project
CNB2 Purchase orders for project
CNMT Milestone Trend Analysis
CNS40 Project Overview
CNS41 Structure Overview
CNS42 Overview: Project Definitions
CNS43 Overview: WBS Elements
CNS44 Overview: Planned Orders
CNS45 Overview: Orders
CNS46 Overview: Networks
CNS47 Overview: Activities/Elements
CNS48 Overview: Confirmations
CNS49 Overview: Relationships
CNS50 Overview: Capacity Requirements
CNS51 Overview: PRTs
CNS52 Overview: Components
CNS53 Overview: Milestones
CNS54 Overview: Sales Document
CNS55 Overview: Sales and Dist. Doc. Items
CNS60 Change Documents for Projects/Netw.
CNS71 Create versions
CNS83 PS: Archiving project - Info System
CNSE5 Progress Analysis
CJH1 Reconstruct Project Inheritance
CJH2 Project Inheritance Log
CJSA Data Transfer to SAP-EIS
CJSB Select Key Figure and Characteristic
CN41N Project structure overview
CNPAR Partner Overview
CJ74 Project Actual Cost Line Items
CJ76 Project Commitment Line Items
Page | 558
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CJ7M Project Plan Cost Line Items
CJ80 Availability Control - Overview
CJ81 Update Report List
CJBBS1 Planning Board Report Assignment
CJBBS2 Structure Overview Report Asst
CJE0 Run Hierarchy Report
CJE1 Create Hierarchy Report
CJE2 Change Hierarchy Report
CJE3 Display Hierarchy Report
CJE4 Create Project Report Layout
CJE5 Change Project Report Layout
CJE6 Display Project Report Layout
CJEA Call Hierarchy Report
CJEB Background Processing, Hier.Reports
CJEC Maintain Project Crcy Trans.Type
CJEK Copy Interfaces/Reports
CJEM Project Reports: Test Monitor
CJEN Reconstruct: Summarized Proj.Data
CJEO Transport Reports
CJEP Transport Forms
CJEQ Import Reports from Client
CJET Translation Tool - Drilldown
CJEV Maintain Global Variable
CJEX Reorganize Drilldown Reports
CJEY Reorganize Report Data
CJEZ Reorganize Forms
CJI1 Project Budget Line Items
CJI2 Budget Line Items: Document Chain
CJI3 Project Actual Cost Line Items
CJI3N Projects Line Items Actual Costs New
CJI4 Project Plan Cost Line Items
CJI4N Projects Line Items Plnd Costs New
CJI5 Project Commitment Line Items
CJI8 Project Budget Line Items
CJI9 Project Struct.Pld Costs Line Items
CJIA Project Actual and Commt Paymt LIs
CJIB Project Plan Payment Line Items
CJIF Projects: Profitability Analysis LI
CJT2 Project Actual Payment Line Items
CJVC Value Category Checking Program
OPI1 Maintain Value Categories
OPI2 Value Categories for Cost Elements
OPI3 Update Control: File RPSCO
OPI4 Commitment Item Value Categories
OPI5 Value Categories for Stag.Key Figs
Page | 559
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
OPI8 Display Value Category
S_ALR_87013503 SObj: Actual/Plan/Variance
S_ALR_87013504 SObj: Actual/Plan/Commitment
S_ALR_87013505 SObj: Current/Cumulated/Total
S_ALR_87013511 Order Profit
S_ALR_87013512 SObj: Actual/Plan/Variance
S_ALR_87013513 SObj: Current/Cumulated/Total
S_ALR_87013531 Costs/Revenues/Expenditures/Receipts
S_ALR_87013532 Plan/Actual/Variance
S_ALR_87013533 Plan/Actual/Cmmt/Rem.Plan/Assigned
S_ALR_87013534 Plan 1/Plan 2/Actual/Commitments
S_ALR_87013535 Actual in COArea/Object/Trans. Curr.
S_ALR_87013536 Plan/Actual/Down Payment as Expense
S_ALR_87013537 Commitment Detail
S_ALR_87013538 Project Version Comparison:Act./Plan
S_ALR_87013539 Project Version Comparison: Plan
S_ALR_87013540 Forecast
S_ALR_87013541 Project Interest: Plan/Actual
S_ALR_87013542 Actual/Comm/Total/Plan in COAr crcy
S_ALR_87013543 Act/plan/variance abs. / % var.
S_ALR_87013544 Actual/Plan Comparison: Periods
S_ALR_87013545 Period Comparison - Actual
S_ALR_87013546 Commitments: Period comparison
S_ALR_87013547 Period Comparison - Plan
S_ALR_87013548 Stat. key figures/periods
S_ALR_87013549 Act/plan compare with partner
S_ALR_87013550 Debit in object/CO area currency
S_ALR_87013551 Plan: Debits in obj./CO area crcy
S_ALR_87013552 Debit/credit actual
S_ALR_87013553 Debit/credit plan
S_ALR_87013554 Comparison of 2 plan versions
S_ALR_87013555 Project results
S_ALR_87013556 Funds Overview
S_ALR_87013557 Budget/Actual/Variance
S_ALR_87013558 Budget/Actual/Commitmt/Rem.Plan/Assg
S_ALR_87013559 Budget/Distributed/Plan/Distributed
S_ALR_87013560 Budget updates
S_ALR_87013561 Availability Control
S_ALR_87013562 Annual Overview
S_ALR_87013563 Structure
S_ALR_87013564 Plan/Actual/Variance
S_ALR_87013565 Planned Contribution Margin
S_ALR_87013566 Actual Contribution Margin
S_ALR_87013567 Quotation/Order/Plan/Actual
S_ALR_87013568 Project Results
Page | 560
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
S_ALR_87013569 Incoming Orders/Balance
S_ALR_87013570 Act/plan/variance abs. / % var.
S_ALR_87013571 Actual/Plan Comparison: Periods
S_ALR_87013572 Project results
S_ALR_87013573 Overview
S_ALR_87013574 Expenditures
S_ALR_87013575 Revenues
S_ALR_87013577 Costs/Revenues/Expenditures/Receipts
S_ALR_87015124 Progress Analysis
S_ALR_87015125 Progress Analysis: Detail
S_ALR_87100185 Actual Costs Per Month, Current FY
S_ALR_87100186 Plan Costs per Month, Current FY
S_ALR_87100187 Commitment per Month, Current FY
S_ALR_87100188 Cumulated Actual Costs
S_ALR_87100189 Actual/Planned Time Series
S_ALR_87100190 Actual/Plan/Var Project + Respons
S_ALR_87100191 Receipts/Expenditures in Fiscal Year
CN42N Overview: Project Definitions
CN43N Overview: WBS Elements
CN44N Overview: Planned Orders
CN45N Overview: Orders
CN46N Overview: Networks
CN47N Overview: Activities/Elements
CN48N Overview: Confirmations
CN49N Overview: Relationships
CN50N Overview: Capacity Requirements
CN51N Overview: PRTs
CN52N Overview: Components
CN53N Overview: Milestones
CN54N Overview: Sales Document
CN55N Overview: Sales and Dist. Doc. Items
CNVL Variable Overviews
OPU8 Overview Var.: Header Line Info Sys.
OPU9 Overview Variant: Item Line
CNE5 Progress Analysis
CJCD Change documents: WBS
CODC Change Documents for Network
Please note that PS analytical apps from Smart Business for Project Execution will not be
available with SAP S/4HANA 1511. The following SAP Fiori apps are not available
with SAP S/4HANA 1511:
•
•
•
F0293
F0294
F0297
WBS Element Cost Variance
WBS Element Costs at Risk
Due Project Milestones
Page | 561
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
F0298
F0299
F0300
F0301
F0302
F0303
F0304
F0305
F0306
F0630
F0632
F0633
F0635
F0696
F0697
F0698
F0699
Overdue Project Milestones
Overdue Project PO Items
Due Project PO Items
Due Network Activities
Overdue Network Activities
Due WBS Elements
Overdue WBS Elements
Project Missing Parts
Project Open Reservations
WBS-Element Revenue Variance
WBS-Element Exceeding Work
WBS-Element Pending Work
Project Report
WBS Element Percentage of Completion
WBS Element Earned Value
Project Earned Value
Project Percentage of Completion
Please double check the SAP Fiori apps for Project System available in the latest SAP
S/4HANA releases for replacement options for some of the uses cases formerly adressed
by Smart Business for Project Execution.
Business Process related information
No influence on business processes expected.
Required and Recommended Action(s)
None
29.6 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.
Page | 562
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Required and Recommended Action(s)
Knowledge Transfer to key- and end user.
29.7 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
Page | 563
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Report
Create Construction Progress
/SAPPCE/PNV03
Report
Display Construction Progress
/SAPPCE/PNV04
report
Display construction progress
/SAPPCE/PNV05
Create and Change CPR
/SAPPCE/PNV07
Plan
Create and Change Remaining
Required and Recommended Action(s)
Knowledge Transfer to key- and end-user. A customer specific solution or a switch to
SAP standard functions should be considered.
29.8 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
Page | 564
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
CNW4
SR10
WWW: Confirmation
Project Documents
Claims
Business Process related information
Selected ITS services for document search, confirmations and creation of claims are not
available as of SAP S/4HANA 1511.
Required and Recommended Action(s)
Knowledge Transfer to key- and end user.
29.9 S4TWL - Selected PS Business Function Capabilities
Application Components:
PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267333
S4TWL - Selected PS Business Function
Capabilities
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
Page | 565
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
Selected PS business functions and related transactions are not the target architecture
anymore in SAP S/4HANA 1511.
With SAP S/4 HANA 1511 - FPS1 the following business functions are switchable but
obsolete:
•
•
OPS_PS_CI_3
LOG_XPD_EXT_1
The following PS business functions are customer-switchable in SAP S/4 HANA 1511 –
FPS1. The related functions are intended to be replaced in future by improved functions
and hence are not the target architecture (Functionality available in SAP S/4HANA 1511
delivery but not considered as future technology. Functional equivalent is not available
yet.).
•
•
OPS_PS_CI_1
OPS_PS_CI_2
The following transactions are hence categorized not to be the target architecture:
•
•
•
CN08CI Config. of Commercial Proj Inception
CNACLD PS ACL Deletion Program transaction
CNSKFDEF SKF defaults for project elements
Basic Information related to Business Functions
If a business function was switched “ON” in the Business Suite start release system, but
defined as “always_off” in the SAP S/4HANA, on-premise edition target release, then a
system conversion is not possible with this release. See SAP Note 2240359 - SAP
S/4HANA, on-premise edition 1511: Always-Off Business Functions. If a business
function is defined as "customer_switchable" in the target release (SAP S/4HANA, onpremise 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.
Page | 566
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The Business Functions OPS_PS_CI_1 and OPS_PS_CI_2 are available and selectable
with SAP S/4HANA 1511, but the related functionalities are not considered as target
architecture.
Alternative standard functions should be considered.
Required and Recommended Action(s)
None
29.10 S4TWL - Selected Logistics Capabilities
Application Components:
PS-MAT-PRO
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267384
S4TWL - Selected Logistics Capabilities
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 PS logistics functions are not the target architecture in SAP S/4HANA
(Functionality available in SAP S/4HANA 1511 delivery but not considered as future
technology. Functional equivalent is not available yet.). However, the functions are still
available in SAP S/4HANA 1511.
The following transactions are categorized not as the target architecture and are planned
to be replaced by new functions in future:
o
o
o
CNMM Project-Oriented Procurement
CNC4 Consistency checks for WBS
CNC5 Consistency checks sales order/proj.
In addition it is also intended to provide alternative solutions for using the non-valuated
project stock and the Open Catalog Interface (OCI).
Page | 567
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
No influence on business processes expected – functionality still available
Required and Recommended Action(s)
None
29.11 S4TWL - Simplification of maintenance transactions
Application Components:
PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270246
S4TWL - Simplification of maintenance
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
There are currently multiple, partially redundant transactions to maintain projects in
project system. It´s the target to have one single maintenance transaction in future. The
target transaction is transaction CJ20N Project Builder. The following maintenance
transactions are hence categorized not as target architecture (Functionality available in
SAP S/4HANA 1511 delivery but not considered as future technology. Functional
equivalent is available):
•
•
•
•
•
•
•
•
•
•
CJ01 Create Work Breakdown Structure
CJ02 Change Work Breakdown Structure
CJ03 Display Work Breakdown Structure
CJ06 Create Project Definition
CJ07 Change Project Definition
CJ08 Display Project Definition
CJ11 Create WBS Element
CJ12 Change WBS Element
CJ13 Display WBS Element
CJ14 Display WBS Element (From DMS)
Page | 568
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CJ20 Structure planning
CJ2A Display structure planning
CJ2D Structure planning
OPUM Maintain Subprojects
CN19 Display Activity (From DMS)
CN20 Dsply network/act.bsc data init.scrn
CN21 Create Network
CN22 Change Network
CN23 Display Network
CJ27 Project planning board
CJ2B Change project planning board
CJ2C Display project planning board
CN26 Display Mat.Comp/Init: Ntwk,Acty,Itm
CN26N Display Mat. Components (From DMS)
Business Process related information
Transaction CJ20N Project Builder is the strategic functionality related to project
maintenance. The currently parallel (partly redundant) transactions are still available with
SAP S/4HANA 1511 but they are not the target architecture. However, navigation e.g.
from strategic reports or other strategic transactions to the list of maintenance
transactions not the target architecture will be exchanged by navigation to the Project
Builder transaction CJ20N. Customer invest (for example related custom code or new
end user knowledge transfer) need to consider this.
Required and Recommended Action(s)
It´s recommended to use single maintenance transaction CJ20N (Project Builder) instead
of using multiple project related transactions.
End user knowledge transfer required to switch from multiple transactions to single
maintenance transaction CJ20N.
29.12 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
Page | 569
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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).
29.13 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
Page | 570
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Project System business functions for Handling Large Projects and related transactions
are not the target architecture anymore in SAP S/4HANA.
With SAP S/4 HANA 1511 - FPS1 hence the following business functions are switchable
(to enable technical conversion) but obsolete:
•
•
OPS_PS_HLP_1
OPS_PS_HLP_2
The following transactions and related IMG activities are categorized not to be the target
architecture and cannot be used any longer with SAP S/4HANA:
•
•
•
•
PSHLP10 Project Worklist
PSHLP20 Project Editor
PSHLP30 Draft Workbench
PSHLP90 Administrator Workbench
Basic Information related to Business Functions
If a business function was switched “ON” in the Business Suite start release system, but
defined as “always_off” in the SAP S/4HANA, on-premise edition target release, then a
system conversion is not possible with this release. See SAP Note 2240359 - SAP
S/4HANA, on-premise edition 1511: Always-Off Business Functions. If a business
function is defined as "customer_switchable" in the target release (SAP S/4HANA, onpremise 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
Page | 571
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
29.14 S4TWL - 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 to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
There are currently multiple, partially redundant transactions to maintain projects. It´s the
target to have one single maintenance transaction in future. The target transaction is
transaction CJ20N Project Builder. See as well SAP note 2270246. With SAP S/4HANA
1511 the target for links and references in reports, still classified as relevant for the target
architecture, is going to the single maintenance transaction CJ20N (Project Builder). For
reports classified as not strategic anymore the navigation has not been adopted.
Business Process related information
Transaction CJ20N Project Builder is the strategic functionality related to project
maintenance. The currently parallel (partly redundant) transactions are still available with
SAP S/4HANA 1511 but they are not the target architecture. Customer invest (for
example related custom code or new end user knowledge transfer) need to consider this.
With SAP S/4HANA 1511 the target for links and references in strategic reports and
transactions is going to single maintenance transaction CJ20N (Project Builder) and not
longer to other project related transactions. A customer can re-enable on project specific
basis the link and reference to the old (multiple) transactions, which are still available.
Required and Recommended Action(s)
Page | 572
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
It´s recommended to use single maintenance transaction CJ20N (Project Builder) instead
of using multiple project related transactions and accordingly the links and references
from related transactions should have CJ20N (Project Builder).
End user knowledge transfer required to switch from multiple transactions to single
maintenance transaction CJ20N.
Custom Code related information
In case of custom code for special maintenance functions only, customer should consider
to enable the custom code for the Project Builder transactions
29.15 S4TWL - 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 to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Solution
Description
The current handling of Production Resources and Tools (PRT) is not the target
architecture (Functionality available in SAP S/4HANA 1511 delivery but not considered
as future technology. Functional equivalent is not available yet) in SAP S/4HANA 1511
since the Project Builder transaction does not support PRTs. Currently no functional
equivalent for Production Resources and Tools (PRT) for projects in SAP S/4HANA
1511 exist. PRTs will not be available in the Project Builder transaction CJ20N.
Business Process related information
No functional equivalent for Production Resources and Tools (PRT) exist in SAP
S/4HANA 1511. Still old special maintenance functions can be used for PRT handling.
Page | 573
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
However, please note that special maintenance functions are not the target architecture
and the Project Builder transaction does not support PRTs (Functionality available in
SAP S/4HANA 1511 delivery but not considered as future technology. Functional
equivalent is not available yet).
Required and Recommended Action(s)
Knowledge Transfer to key- and end user, usage of alternatives to PRTs need to be
considered
29.16 S4TWL - Project Planning Board, Gantt-Chart, Hierarchy and
Network Graphics
Application Components:
PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270263
S4TWL - Project Planning Board, GanttChart, Hierarchy and Network Graphics
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
Please be informed that graphics in Project System including Gantt charts, network
graphics and hierarchy graphics might be replaced in future by new graphic user interface
patterns. The existing graphical views hence are categorized not as the target architecture
(Functionality available in SAP S/4HANA 1511 delivery but not considered as future
technology. Functional equivalent is not available yet). Because of this also the following
transactions are categorized not as the target architecture:
•
•
•
CJ27 Project planning board
CJ2B Change project planning board
CJ2C Display project planning board
Business Process related information
Page | 574
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Still the existing graphics and corresponding transactions can be used. However, the
graphics might be replaced in future by new and improved graphic user interface patterns
which might not provide exactly the same functional scope of currently existing
functions.
Required and Recommended Action(s)
Knowledge Transfer to key- and end user
29.17 S4TWL - Current simulation functions in project system
Application Components:
PS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270264
S4TWL - Current simulation functions in
project 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
With SAP S/4HANA 1511 the current simulation functions in project system are still
available but not considered as the target architecture (Functionality available in SAP
S/4HANA 1511 delivery but not considered as future technology. Functional equivalent
is not available yet).
The following transactions are hence categorized not as the target architecture:
•
•
•
•
•
•
•
CJV1 Create project version (simulation)
CJV2 Change project version (simulation)
CJV3 Display Project Version (Simulation)
CJV4 Transfer project
CJV5 Delete simulation version
CJV6 Maintenance: Version administration
CJV7 Display transfer log
Page | 575
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
Still the existing simulation functions can be used. However, the existing simulation
functions and related transactions are not the target architecture and might be replaced in
future by other, improved simulation capabilities which might not provide exactly the
same functional scope of currently existing functions.
29.18 S4TWL - 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 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 system specific archiving transactions are still
available, but they are not considered as the target architecture any longer (Functionality
available in SAP S/4HANA 1511 delivery but not considered as future technology.
Functional equivalent is available). It is recommended to use the central archiving
transaction SARA instead.
The following transactions are categorized not as the target architecture:
•
•
•
•
•
•
CN80
CN81
CN82
CN83
CN84
CN85
Archiving project structures
PS: Archiving project - preliminary
PS: Archiving project structures
PS: Archiving project - Info System
PS: Archiving project - admin.
PS: Delete operative structures
Page | 576
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
CN99
Archiving Standard Networks
KBEA
Trsfr Price Docs: Set Del.Indicator
KBEB Trsfr Price Docs: Generate Archive
KBEC Trsfr Price Docs: Manage Archive
Business Process related information
Still the existing project specific archiving transactions can be used. However, these
transactions are not the target architecture. Going forward it is recommended to use the
central archiving transaction SARA instead.
Required and Recommended Action(s)
•
•
It is recommended to use central archiving transaction SARA instead of project
system specific transactions.
Knowledge Transfer to key- and end-user
29.19 S4TWL - 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 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 1511 in Project System the Project texts (PS texts) are not
considered as the target architecture (Functionality available in SAP S/4HANA onPage | 577
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
premise edition 1511 delivery but not considered as future technology. Functional
equivalent is not available yet). It is planned to replace the PS texts with alternative
functionality.
The following transactions are hence categorized not as the target architecture as well:
•
•
CN04
CN05
Edit PS Text Catalog
Display PS Text Catalog
Business Process related information
Still the Project texts can be used. However, this function is not the target architecture.
Going forward it is recommended to use alternative ways of document handling for
projects.
29.20 S4TWL - Claim Management
Application Components:
PS-CLM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267169
S4TWL - Claim 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
With SAP S/4HANA 1511 the Project System Claim Management is still available but
not considered as the target architecture (Functionality available in SAP S/4HANA onpremise edition 1511 delivery but not considered as future technology. Functional
equivalent is available). It is recommended to use alternative solutions such as Project
Issue and Change Management for this business requirement.
Page | 578
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The following transactions are hence categorized not as the target architecture:
•
•
•
•
•
CLM1
CLM10
CLM11
CLM2
CLM3
Create Claim
Claim Overview
Claim Hierarchy
Change Claim
Display Claim
Please note that hence also the factsheet/object page Project Claim will not be available
with SAP S/4HANA 1511 (see note 2267283).
Business Process related information
Still the existing claim management functionality can be used. However, the related
functions and transactions are not the target architecture.
Going forward it is recommended to use alternative solutions such as Project Issue and
Change Management for this business requirement. This might require also process
changes as claim management and Project Issue and Change Management partially
provide different capabilities.
Required and Recommended Action(s)
It is recommended to use Project Issue and Change Management functionality and not PS
claim management for appropriate business requirement.
Knowledge Transfer to key- and end-user, evaluation of Project Issue and Change
Management as alternative to PS claim management.
29.21 S4TWL - Selected project financial planning and control functions
Application Components:
PS-COS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267182
S4TWL - Selected project financial planning
and control functions
Symptom
Page | 579
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 project financial planning and control functions including the
Easy Cost Planning (ECP) tool are still available but not considered as the target
architecture (Functionality available in SAP S/4HANA 1511 delivery but not considered
as future technology. Functional equivalent is not available yet.) any longer since it is
planned to provide improved project costing and project financial planning tools
addressing customer needs.
The following transactions are hence categorized not as the target architecture:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CJFA Analysis of Data Trans. into PS Cash
CJFN CBM Payment Converter
CJ48 Change Payment Planning: Init.Screen
CJ49 Display Payment Planning: Init.Screen
FM48 Change Financial Budget: Initial Scn
FM49 Display Financial Budget: Init.Scrn
CJ8V Period Close for Project Selection
CJC1 Maintenance Dialog for Stat.by Per.
CJC2 Maintain Planned Status Changes
CJSG Generate WBS Element Group
CJZ1 Act. Int Calc.: Projects Coll. Proc.
CJZ2 Actual Int.Calc.: Project Indiv.Prc.
CJZ3 Plan Int.Calc.: Project Indiv.Prc.
CJZ5 Plan Int.Calc.: Project Coll.Prc.
CJZ6 Actual Int.Calc.: Indiv.CO Order Prc
CJZ7 Planned Int.Calc: Indiv.CO Ord.Proc.
CJZ8 Actual Int.Calc.: Coll.CO Order Prc.
CJZ9 Plan Int.Calc.: Coll.CO Order Prc.
CNFOWB Forecast Workbench
CJ9D Copy Plan Versions
CJ9ECP Project System: Easy Cost Planning
CJ9K Network Costing
CJ9L Forecast Costs: Individual Projects
CJ9M Forecast Costs: Coll.Project Proc.
CJ9Q Integrated Planning for Ntwks(Coll.)
CJ9QS Integrated Planning for Ntwks (Ind.)
CNPAWB Progress Analysis Workbench
DP101 Reset Billing Plan Date
DP80 SM: Resource-Related Quotation
Page | 580
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
DP81 PS: Sales Pricing
DP82 PS: Sales Pricing Project
DP98 Resource for Billing Request
DP99A Doc.Flow Reporting - Res.-Rel. Bill.
DP99B Doc.Flow for Res.-Rel. Bill. - SD
DP99C Doc.Flow for Res.-Rel. Bill.-Service
DP60 Change Accounting Indicator in LI
DP70 Conversion of Individual Orders
RKPSANALYSE RKPSANALYSE
CJF1 Create Transfer Price Agreement
CJF2 Change Transfer Price Agreement
CJF3 Display Transfer Price Agreement
CJF4 Transfer Price Agreement List
CJG1 Enter Transfer Price Allocation
CJG3 Display Transfer Price Allocation
CJG4 Enter Trsfr Price Allocation: List
CJG5 Cancel Transfer Price Allocation
CJL2 Collective Agreement
CNPRG Network Progress
Business Process related information
No influence on business processes expected.
Page | 581
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
30 Logistics – PSS
30.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 a future release.
Business Process related information
Transaction CBIHSR01 is not available in SAP S/4HANA.
30.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
Page | 582
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
PUR
PURCHASE_REQUISITION
Tables
EBAN
PUR
EKKO,
EKPO,
EKET,
MKPF,
EKET-EINDT: Delivery date of
item
MSEG
VBAK,
VBAP,
VBEP,
VBPA,
VBEP-EDATU: Schedule line
date
SO
SO
PURCHASE
SALES
DELIVERY
IMP
PURCHASE_REQUISITION
IMP
PURCHASE
VBUP
LIKP,
LIPS,
VBPA,
VBUP,
MKPF,
MSEG
EBAN
EKKO,
EKPO,
Date for Planned Quantities
EBAN-LFDAT: Delivery date of
item
LIKP-WADAT: Planned date of
goods movement
EBAN-LFDAT: Delivery date of
item
EKET-EINDT: Delivery date of
item
Page | 583
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
EKET,
MKPF,
EXP
EXP
PRO
SALES
DELIVERY
PRODUCTION
PRO
REPET_MANUFACTURING
CON
PRODUCTION
CON
REPET_MANUFACTURING
MSEG
VBAK,
VBAP,
VBEP,
VBPA,
VBUP
LIKP,
LIPS,
VBPA,
VBUP,
MKPF,
MSEG
AUFK,
AFKO,
AFPO,
RESB,
MKPF,
MSEG
PLAF,
RESB,
MKPF,
MSEG
AUFK,
AFKO,
AFPO,
RESB,
MKPF,
MSEG
PLAF,
RESB,
MKPF,
MSEG
VBEP-EDATU: Schedule line
date
LIKP-WADAT: Planned date of
goods movement
AFKO-GSTRS: Scheduled start
PLAF- PSTTR: Basic start date
AFKO-GSTRS: Scheduled start
PLAF- PSTTR: Basic start date
As a result of the SAP S/4HANA data model change in Sales & Distribution, tables
VBUK and VBUP are no longer supported in this Customizing activity. Selection criteria
which relate to the status of a sales document need to be defined based on the
corresponding header and item tables (VBAK, VBAP, LIKP and LIPS). For further
details of the data model change see Simplification Item in Sales & Distribution area.
Page | 584
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
30.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
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
Page | 585
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
In SAP S/4HANA on-premise edition the compliance reporting in BI is not available. For
parts of the BI reporting, the compliance explorer and the exemption explorer is a
functional equivalent.
If you are using SAP Product Stewardship Network to collaborate with your suppliers, the
contact person information are not updated automatically any more in SAP S/4HANA
on-premise edition.
The following compliance requirement check conflict workflow templates are not
available in SAP S/4HANA, on-premise edition. They have been replaced with a new
application that allows exploring the compliance requirement check conflicts based on
native master data using CDS views.
Workflow Template / Process Control
Object
00600054 - EHPRC_CHK_BA
00600049 - EHPRC_CHK_CH
00600056 - EHPRC_CHK_IM
00600069 - EHPRC_CHK_JG
00600053 - EHPRC_CHK_SV
00600068 - EHPRC_CHK_RO
Class Name / Event
CL_EHPRC_PCO_COMP_REQ_BASE
CL_EHPRC_PCO_COMP_REQ_CHROHS
CL_EHPRC_PCO_CMP_REQ_IMDS
CL_EHPRC_PCO_CMP_REQ_JIG
CL_EHPRC_PCO_COMP_REQ_SVHC
CL_EHPRC_PCO_COMP_REQ_EUROHS
The following compliance assessment workflow templates are not available in SAP
S/4HANA, 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 Class Name / Event
Control
Type of Assessment Process
Object
CL_EHPRC_PCO_BASMAT_A
Basic Material Assessment
SSMNT
CL_EHPRC_PCO_COMP_ASS
00600071 - EHPRC_COASMT
Component Assessment
MNT
CL_EHPRC_PCO_PROD_ASS
00600062 - EHPRC_PRASMT
Product Assessment
MNT
00600070 - EHPRC_BMASMT
Page | 586
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
30.4 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
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.
Page | 587
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
How to Determine Relevancy
None
30.5 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
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).
30.6 S4TWL - Hazardous Substance Management
Application Components:
EHS-HSM
Related Notes:
Page | 588
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note Type
Note Number
Note Description
Business Impact
2267422
S4TWL - Hazardous Substance
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
The existing functionality SAP Hazardous Substance Management (EHS-HSM) can be
used within SAP S/4HANA, however the use of component SAP Risk Assessment (EHSMGM-RAS) is recommended instead (Functionality available in SAP S/4HANA delivery
but not considered as future technology. Functional equivalent is available.).
Business Process related information
Some adjustments in the SAP Easy Access menu have been made:
•
•
The menu item Hazardous Substance Management has been removed from the
Product Safety and Stewardship SAP Easy Access Menu.
The two menu items Hazardous Substance Master and Filling from Specification
Management are now located under: Logistics Product Safety and Stewardship Product Safety - Tools - Hazardous Substance Master.
SAP Risk Assessment provides a disjunctive functionality without any dependency on
Hazardous Substance Management.
30.7 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
Page | 589
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Product Compliance Management of SAP Environment, Health and Safety Management
Extension EHSM provides compliance functionality for the needs of the discrete industry.
If you use the discrete industry solution of SPRC or Compliance for Products (CfP), you
are able to migrate to Product Compliance Management.
For the process industry solution of SPRC, no successor exists.
The focus of SPRC version 2.0 was to support process and discrete industry
manufacturers to become REACH compliant by using functionalities, such as campaign
management for supply chain communication, bulk material assessment and registration
and endpoint management.
With the deadline for the last REACH registration period in 2018, the focus of customers
will switch towards functionality which supports them to remain REACH compliant. The
provision of new cloud-enabled solution capabilities, which take these new requirements
into account, is planned within SAP S/4HANA.
Business Process related information
No influence on business processes expected
The tools of SPRC version 2.0 will only be relevant for process industry manufacturers
until the deadline of the last REACH registration period in 2018. The focus of customers
will then switch to functionality which supports them to remain REACH compliant.
All transaction codes which were delivered with the SPRC add-on are not available
within SAP S/4HANA.
Page | 590
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
You need to uninstall the add-on before you do a system conversion to SAP S/4HANA.
Follow SAP Note 2298456 to perform the uninstallation.
If you use the discrete industry solution of SPRC or CFP, you are able to migrate to
Product Compliance Management of SAP Environment, Health and Safety Management
(EHSM), which provides functionalities for discrete industries. For details refer to
http://help.sap.com/ehs-comp or SAP Note 1489703.
30.8 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.
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.
Page | 591
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
30.9 S4TWL - 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).
30.10 S4TWL - BW Extractors for Dangerous Goods Management and
Specification Managemen
Application Components:
EHS-SAF
Related Notes:
Note Type
Note Number
Note Description
Page | 592
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 593
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
31 Logistics – QM
31.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 on-premise edition 1511 delivery but not considered as future technology.
Functional equivalent is not available yet.) anymore within SAP S/4HANA and will be
replaced by corresponding new applications in the future. This applies to evaluations for
quality notifications as well as inspection lots and related data.
Business Process related information
No influence on business processes expected. Customers should just consider this when
they think about investments into their QMIS functionality. The old functionality will
stay available until the new functionality is released.
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
Page | 594
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
31.2 S4TWL - Quality Inspection Engine (QIE)
Application Components:
CA-QIE
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270197
S4TWL - Quality Inspection Engine (QIE)
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 Inspection Engine (QIE) which is part of EWM is not the target architecture
(Functionality available in SAP S/4HANA on-premise edition 1511 delivery but not
considered as future technology. Functional equivalent is not available yet.) within SAP
S/4HANA and will be replaced by corresponding new functions in the future.
Business Process related information
No influence on business processes yet. Customers should consider this when they use
QIE for other purposes. The old functionality will stay available until the new
functionality is released.
Other Terms
Inspection Document
31.3 S4TWL - Redundant Transactions in QM
Application Components:
QM-PT-BD, QM-IM-SM, QM-PT-RP-PRC, QM-PT-BD-SPL, QM-
CA-MD, QM
Related Notes:
Page | 595
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 in the SAP Fiori launchpad for SAP S/4HANA 1610.
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 transaction(s) will not be provided in SAP S/4HANA 1610.
Transaction Text
QE51
Results recording worklist
QS45
Display catalog
Component
QM-PT-BD
Alternative
QE51N
QS42
The following transactions are replaced by corresponding Fiori apps and are therefore not
available in the SAP Fiori launchpad for SAP S/4HANA 1610:
Transaction Text
QDV3
QI03
QPR3
QS34
Component
Alternative
Fiori app
Display sampling procedure QM-PT-BD-SPL Sampling Procedure
Fiori app
Quality Info Records Display q-info record QM-PT-RP-PRC Procurement
procurement
Fiori app
Display sample
QM-IM-SM
Sample
Display inspection method
Fiori app
version
Inspection Method
QM-PT-BD
Page | 596
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The following transactions can be covered by alternate transactions and are therefore not
available in the SAP Fiori launchpad for SAP S/4HANA 1610:
Transaction Text
Create certificate profile
assignment
QC11
Change certificate profile
QC12
assignment
Display certificate profile
QC13
assignment
Create certificate profile
assignment with copy model
QC14
Component
Alternative
QC15
QM-CA-MD
QC16
QM-CA-MD
QC17
QM-CA-MD
QC18
QM-CA-MD
Required and Recommended Action(s)
Alternate transactions can directly be used. Fiori apps are already integrated in the QM
Fiori launchpad roles.
31.4 S4TWL - Removed Navigation to Transactions for Evaluations in QM
Application Components:
QM-QN, QM-IM, QM-QC-IS, QM
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.
Solution
Description
Page | 597
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
QGA1
QM50
QGP1
QST05
Text
Display quality score time line
Time Line Display of Quality
Notifications
Results history for task list
characteristic
Graphical Scheduling
Overview
Component
QM-QC-IS
QM-QN
QM-QC-IS
QM-IM
Required and Recommended Action(s)
For the time being, open the transaction in SAP GUI for Windows.
31.5 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
Renewal
Page | 598
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
will be replaced by new authorization objects with an activity in the medium term in SAP
S/4HANA - starting with the current Release 1709.
In the release after the next, the old authorization objects will be deleted. However, until
then, they retain their validity. This means that the new authorization objects will be
checked in addition to the old authorization objects. The new objects are also assigned to
the authorization profile SAP_NEW.
For this reason, if you have maintained the old authorization objects previously, you do
not have to additionally maintain the new authorization objects for existing functions
immediately; you only have to do this for new functions. However, we do recommend
that you switch your authorizations to the new authorization objects as soon as possible.
The following table shows which new authorization object replaces which old
authorization objects.
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_QPTB, 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
Page | 599
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Q_INSPPNT
Q_TCODE
Authorization to edit inspection
points
Business-process-related information
No consequences are expected for business processes. Consequences are expected only
for system administration.
Required and recommended action(s)
1. Assign the authorization profile SAP_NEW to your roles.
2. Implement the new authorization objects in your roles and maintain the
authorizations for the new authorization objects. Note that for the time being the
old objects will still be checked in parallel.
3. Then remove the authorization profile SAP_NEW again so that the newly
maintained authorizations take effect.
31.6 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.
Page | 600
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 QEH1
edition 1511
Required and Recommended Action(s)
Knowledge transfer to key and end users
Other Terms
Worklist
31.7 S4TWL - ITS services in QM
Application Components:
QM-QN, QM-IM-RR, QM-QC
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
Page | 601
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Transaction
Code
QC40
Corresponding
ITS Service
QC40
QC40A
QC40A
QC42
QC42
QEW01
QEW01
QEW01V
QEW01V
QMW1
QMW1
QISR
QISR
Description
Internet Certificate for
Delivery
Internet Certificate for
Delivery
Batch certificate on
Package
QC
Application
Component
QM-CA-MD
QC
QM-CA-MD
Certificates
Basic Data for
QC
QM-CA-MD
Certificates
Basic Data for
WWW
Results Recording on QEWW
Web
Variant Maint.:
QEWW
Recording on Web
Create quality
QQM
notification (WWW)
Internal Service
QNWEB
QM-IM
QM-IM
QM-QN
QM
Area
Basic Data for
Certificates
Quality
Inspection
Quality
Inspection
Quality
Notifications
Quality
Notifications
Request
Page | 602
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
QISRW
QISRW
Internal Service
QNWEB
QM
Quality
Notifications
Request on the
Web
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
31.8 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
Page | 603
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
IQS8WP
available in SAP
S/4HANA on-premise IQS9WP
edition 1511
QA32WP
IQS8 - Call from Workplace/MiniApp
IQS9 - Call from Workplace/MiniApp
QA32 - Call from Workplace/MiniApp
QE09WP
Call QE09 from Workplace
QPQA32
QM MiniApp Selection Variant
QPQGC1
QM MiniApp Selection Variant
QPQM10
QM MiniApp Selection Variant
QPQM13
QM MiniApp Selection Variant
QM10WP
QM10 - Call from Workplace/MiniApp
QM13WP
QM13 - Call from Workplace/MiniApp
QPIQS8 QM
MiniApp Selection Variant
QPIQS9 QM
MiniApp Selection Variant
WAO_QA32WP QA32 -Call from Workplace/MiniApp
WAO_QM10WP QM10 - Call from Workplace/MiniApp
WAO_QM13WP QM13 - Call from Workplace/MiniApp
WAO_QPQA32 QM
iView Selection Variant Insp.Lot
WAO_QPQM10 QM
iView Selection Variant Notificat
WAO_QPQM13 QM
iView Selection Variant Task
Page | 604
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
Knowledge transfer to key and end users
Other Terms
IAC
Page | 605
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
32 Logistics – TRA
32.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.
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 Shipping solution within SAP S/4HANA, which
is already available.
The main functions of LE-TRA have already been replaced with selected functions of
SAP S/4HANA Supply Chain for Transportation Management.
Currently, that is until the end of life of the Compatibility Packs, both technical
applications (LE-TRA and Basic Shipping) are independent from each other and can be
Page | 606
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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: Definition - Logistics Execution - Transportation
- the readyness check lists table entries
32.2 S4TWL - Transportation (LE-TRA) External Planning IDOCS
Application Components:
LE-TRA
Related Notes:
Note Type
Note Number
Note Description
Page | 607
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
33 Logistics – WM
33.1 S4TWL - Warehouse Management (WM)
Application Components:
LE-WM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270211
S4TWL - Warehouse Management (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
The Warehouse Management (LE-WM) is not the target architecture anymore within
SAP S/4HANA, on-premise edition (Functionality available in SAP S/4HANA onpremise 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 influence on business processes expected related to the Warehouse Management. The
functionality related to Warehouse Management (LE-WM) and the other components
described above is still available within the SAP S/4HANA architecture stack. All related
functionalities can be used in an unchanged manner.
Required and Recommended Action(s)
The Warehouse Management (LE-WM) and the other components described above is not
the target architecture within SAP S/4HANA, on-premise edition. The (already available)
alternative functionality is Extended Warehouse Management (SAP EWM) and a
customer could start introducing EWM upfront to the SAP S/4HANA installation.
Page | 608
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
34 Portfolio and Project Management (PPM)
34.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
This transition worklist item is relevant for you, if you are using the WebDynpro
applications 'Create resource' or 'Edit resource'. SAP Note 2321885 provides a preconversion check for this feature.
Page | 609
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
Conversion pre-checks SAP Note 2321885
34.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
Page | 610
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
WFM Core
34.3 S4TWL - Integration to SAP cFolders in SAP Portfolio and Project
Management for
Application Components:
PPM-PFM, PPM-PRO
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 SAP Document Center as a substitute for selected
collaboration scenarios.
How to Determine Relevancy
Page | 611
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
This Transition Worklist item is relevant if cFolders and SAP Portfolio and Project
Management is used.
34.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 2321885 provides a pre-conversion check for this feature.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
In order to prevent the loss of the linkage between documents stored in KM and SAP
Portfolio and Project Management for SAP S/4HANA during the system conversion, it is
required to switch from the KM based document management to a KPRO based solution.
For this, migrate your KM documents to KPRO documents using the report
/RPM/MIGRATE_KM_DOCS. 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
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.
Page | 612
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
34.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 2321885 provides a pre-conversion check for this feature.
Business Process related information
It is not possible anymore to order external materials and resources directly from Project
Management through SRM.
Required and Recommended Action(s)
Page | 613
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
34.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
With SAP Portfolio and Project Management for SAP S/4HANA, the cFolders
component is not available anymore. SAP recommends to evaluate SAP Document
Center as a substitute for selected collaboration scenarios.
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process related information
Page | 614
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
All the features of cFolders application and all the integration between cFolders and other
applications, e.g. SAP PLM, SAP SRM etc., are not available anymore.
Required and Recommended Action(s)
Because cFolders is not available anymore with SAP Portfolio and Project Management
for SAP S/4HANA, customers need to archive existing cFolders data before the system
conversion by following the steps below:
1. This step is mandatory to continue the conversion. Go to the collaboration
overview page, select the collaborations you would like to archive, and click
'Archive' button in the toolbar above the list. Then the system will set a deletion
indicator and remove the collaboration from the collaboration overview.
2. This step is not mandatory for the conversion, but it's highly recommended to
keep the integrity of your data. Use SAP Data Archiving and archive object
'CFX_ARCH' to archive the collaboration data.
For the collaboration with partners, customers could consider to use other products like
SAP Document Center.
How to Determine Relevancy
This Simplification Item is relevant if:
•
cFolders is used if entries exist in Table CFX_COL, and column
TO_BE_ARCHIVED is not set to 'X' (check with SE16)
34.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.
Page | 615
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
2
Master
5
Switches
Integration with Other
Components (see SAP
Note 1391444)
2
Master
7
Switches
Integration with PS
and FI/CO (see SAP
Note 1427365)
2
Master
8
Switches
Enhanced Capital and
Resource Mgmt
X
Switch (see SAP Note
1457426)
2
Master
13
Switches
2
Master
14
Switches
Flag is Obsolete (SAP
Note 1759150)
Flag is Obsolete Change Documents for
Financial and Capacity
Planning
Availability in S/4HANA
PPM
Switch will be removed.
Feature will be activated by
default. In most cases, using
the features require further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch is obsolete and will be
deleted.
Switch is obsolete and will be
deleted.
2
Master
15
Switches
Milestone Filter for
Tasks ('X'=On, '
'=Off)
2
Master
16
Switches
Accumulate the
Number of Objects in
X
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.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Page | 616
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2
Master
17
Switches
2
Master
18
Switches
Flag is obsolete (SAP
Note 1780409)
Flag is Obsolete Automatic Refresh of
Project Dashboards
('X'=On, ' '=Off)
Switch is obsolete and will be
deleted.
Switch is obsolete and will be
deleted.
Master
21
Switches
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
22
Switches
Activate Operative
Object Links ( '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 21
Settings
DEPRECATED:
Display Additional
Information on Gantt
Chart (' ': No, 'X': Yes)
Switch is obsolete and will be
deleted.
Flag is obsolete (SAP
Note 1756616)
Switch is obsolete and will be
deleted.
Flag is obsolete (SAP
Note 1769591)
Switch is obsolete and will be
deleted.
2
6
6
User
Interface 23
Settings
User
Interface 24
Settings
6
User
Interface 26
Settings
Display Additional
Information on MultiProject Monitor (' ':
No, 'X': Yes)
6
User
Interface 28
Settings
Adjustment of
Structure Tree Area by
Splitter ('X'=Enabled, '
'=Disabled)
6
User
Interface 29
Settings
Delete Button in
Project Dashboard
('X'=Yes, ' '=No)
6
User
Interface 30
Settings
Data Aggregation in
Projects ('X'=Enabled,
' '=Disabled)
X
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Page | 617
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
6
User
Interface 31
Settings
Fullscreen Mode for
Graphical View
('X'=Enabled, '
'=Disabled)
6
User
Interface 32
Settings
Move-Up/Move-Down
Buttons in Project
('X'=Yes, ' '=No)
6
User
Interface 33
Settings
Summary of Project
Data in Multi-Project
Monitor ('X'=Yes, '
'=No)
6
User
Interface 34
Settings
Concurrent Status
Changes for Multiple
Tasks ('X'=Enabled, '
'=Disabled)
6
User
Interface 35
Settings
Display Mirrored Task
Relationships in MP
Monitor ('X'=Enabled,
' '=Disabled)
6
User
Interface 36
Settings
Assignment of
Multiple Roles to
Tasks at a Time
(‘X’=Enabled, ‘
‘=Disabled)
6
User
Interface 37
Settings
Allow Constraint
Icons without Add.
Info. in Graphical
View ('X'=On, ' '=Off)
6
User
Interface 38
Settings
Enhance Display of
Details Window in
Graphical View
('X'=On, ' '=Off)
6
User
Interface 40
Settings
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.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Page | 618
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
6
User
Interface 41
Settings
One-Click Completion
of Subordinate Project
Elements (' '=No,
'X'=Yes)
6
User
Interface 42
Settings
Improved Alignment
of Project Evaluation
Display (' '=No,
'X'=Yes)
7
General
Default
Values
17
SAP Notes Language
Independent
7
General
Default
Values
22
Document Alignment('
X
': KM, 'X': KPRO)
7
General
Default
Values
23
Default number of
columns initially
displayed in Financial
and Capacity Planning
7
General
Default
Values
7
General
Default
Values
General
Default
Values
27
28
X
Check-in/Check-out of
Documents (' ':
Normal, 'X': HTTPBased)
HTTP Destination for
SAP BusinessObjects
Explorer
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch is obsolete and will be
deleted.
Switch will be Removed.
Feature will no longer be
available.
Switch will be Removed.
Feature will no longer be
available.
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
X
Reporting Cockpit ('X'
=Yes, ' ' = No )
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
7
Page | 619
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
7
General
Default
Values
7
General
Default
Values
9
11
11
11
11
11
11
11
40
Flag is obsolete
46
Override
Authorizations for
Documents in Item
Versions ('X'=Yes, '
'=No)
9
Use Project Calendar
for Linked Item
('X'=Yes, ' '=No)
1
Updating Staffing
According To Tasks
('X'=Enabled,
' '=Disabled)
2
Confirmed Role
Efforts in Staffing
Overview of Projects
('X'=Yes, ' '=No)
3
Export of CrossProject
Resource/Staffing
Data ('X'=Enabled, '
'=Disabled)
4
Consider User Group
Authorization in
Resource Management
(Yes = 'X', No = ' ')
5
Personalized Layout
for Resource
Management Screens
('X'=Yes, ' '=No)
6
SAP Notes in CrossProject Staffing
Overview ('X'=Yes, '
'=No)
Staffing
and
7
Resource
Updating Multiple
Roles According to
Tasks ('X'=Enabled, '
'=Disabled)
Portfolio
Item
Project
Integratio
n
Staffing
and
Resource
Managem
ent
Staffing
and
Resource
Managem
ent
Staffing
and
Resource
Managem
ent
Staffing
and
Resource
Managem
ent
Staffing
and
Resource
Managem
ent
Staffing
and
Resource
Managem
ent
Switch is obsolete and will be
deleted.
Switch will be removed.
Feature will be activated
available by default. In most
cases, using the feature
requires further configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
Page | 620
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
11
11
12
Managem
ent
Staffing
and
Resource
Managem
ent
Staffing
and
Resource
Managem
ent
Schedulin
g and
Project
Structurin
g
Schedulin
g and
Project
Structurin
g
Schedulin
g and
Project
Structurin
g
Schedulin
g and
Project
Structurin
g
Schedulin
g and
Project
Structurin
g
8
12
1
Project Number as
Search Criterion in
Role Search ('X'=Yes, '
'=No)
Retain Node
Expansion After
Saving in Overview
Screens ('X'=Yes, '
'=No)
Automatic Scheduling
of All Project
Elements
('X'=Enabled, '
'=Disabled)
3
Creation/Deletion of
Multiple Relationships
('X'=Enabled, '
'=Disabled)
4
Optimization of Task
and Milestone
Relationships
('X'=Enabled, '
'=Disabled)
5
Changing Scheduling
Type in Project
('X'=Enabled, '
'=Disabled)
6
Preserve Relationships
When Canceling Tasks
('X'=Enabled, '
'=Disabled)
13
Additiona
1
l Features
Sending E-Mails from
Project Elements ('X' =
Enabled, ' ' =
Disabled)
13
Additiona
2
l Features
Export/Import of
Templates
('X'=Enabled, '
'=Disabled)
12
12
12
12
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Page | 621
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
13
Additiona
4
l Features
Comparison with
Actual Dates in
Graphical View
('X'=Enabled, '
'=Disabled)
13
Additiona
5
l Features
Export of MultiProject Monitor Data
('X'=Enabled, '
'=Disabled)
13
Additiona
6
l Features
Export of Resource
Planning Data
('X‘=Enabled, '
'=Disabled)
13
Additiona
7
l Features
Export of Graphical
View ('X' =Enabled, ' ' X
=Disabled)
13
Additiona
8
l Features
Export of Evaluation
Data ('X‘=Enabled, '
'=Disabled)
X
Additiona
9
l Features
Project-Specific
Display of Earliest or
Latest Dates
('X'=Enabled, '
'=Disabled)
X
13
X
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
Switch will be removed.
Feature will be activated by
default. In most cases, using
the feature requires further
configuration.
SAP Note 2321885 provides a pre-conversion check for some of these features.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
Review the settings in your system before the conversion. If you have overwritten the
default values, SAP recommends to delete the entries that have been deleted by SAP.
How to Determine Relevancy
Page | 622
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 CheckSAP Note 2353984
In/Check-out
34.8 S4TWL - Fiori apps of UI FOR SAP PORTF PROJ MGMT 6.0 in SAP
Portfolio and Projec
Application Components:
PPM-PRO, PPM-PFM, 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
Page | 623
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The functionality is also provided by corresponding Web Dynpro applications, therefore
no major impact is expected.
Required and Recommended Action(s)
If you are using the apps for the Program Manager role, check the Web Dynpro
applications.
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.
34.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.
Page | 624
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
The table view for the portfolio structure is still available. No further actions expected.
How to determine Relevancy
This SAP S/4HANA Transition Worklist item is relevant if you are using portfolio
management.
34.10 S4TWL - 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.
Page | 625
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
How to Determine Relevancy
To determine if this Simplification Item is relevant please check if you use SAP Smart
Forms for printing Project Management information.
Other Terms
Smart Forms
34.11 S4TWL - 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.
Page | 626
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
DPR_RES_MAIN, VI_ROL_LIST_R, VI_ROL_LIST_S
34.12 S4TWL - 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.
Page | 627
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
34.13 S4TWL - 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.
34.14 S4TWL - cRoom Integration in SAP Portfolio and Project
Management for SAP S/4HAN
Application Components:
PPM-PRO
Related Notes:
Page | 628
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
34.15 S4TWL - 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
Page | 629
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
34.16 S4TWL - 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.
Page | 630
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
34.17 S4TWL - SAP BusinessObjects Explorer Integration in SAP EPPM
Application Components:
PPM-PRO
Related Notes:
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.
Page | 631
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
34.18 S4TWL - 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
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)
Page | 632
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
No further actions expected.
34.19 S4TWL - Simplification of data model in SAP Portfolio and Project
Management for
Application Components:
PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2361690
S4TWL - Simplification of data model 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
With SAP Portfolio and Project Management for SAP S/4HANA, the current data model
is considered as not strategic in SAP Portfolio and Project Management for SAP
S/4HANA, because there is a known need to change or replace the current data model by
a simplified one. The current data model can still be used with SAP Portfolio and Project
Management 1.0 for SAP S/4HANA to enable an end-to-end business process, but could
be changed, removed or replaced according to the roadmap for SAP Portfolio and Project
Management for SAP S/4HANA.
Business Process related information
Changes or replacements of the current data model should primarily influence how a
business process is supported by the solution, but do not necessarily lead to a change of
the business process itself.
Required and Recommended Action(s)
The current data model is still used in SAP Portfolio and Project Management 1.0 for
SAP S/4HANA to enable an end-to-end business process, but will be subject of
Page | 633
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
renovation and simplification according to the roadmap for SAP Portfolio and Project
Management for SAP S/4HANA.
34.20 S4TWL - 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
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
34.21 S4TWL - Business Partner in SAP Portfolio and Project Management
for SAP S/4HANA
Page | 634
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Application Components:
PPM-PRO, PPM-PFM
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
In SAP Portfolio and Project Management for SAP S/4HANA user assignments of
business partners of type 'Resource' are no longer available. User Assignments using
transaction BP are no longer possible, therefore you cannot create a business partner of
type 'Employee' with user assignment using transaction BP.
Required and Recommended Action(s)
SAP recommends to evaluate other options to use business partners of type 'Employee'
for which user assignments are still possible according to Human Resources processes,
for example:
1. Use transaction PA40 (action Hiring) to create a minimum set of HR master data
2. Use transaction PA30 to maintain the user information in infotype 0105/0001
3. Run report /SHCM/RH_SYNC_BUPA_FROM_EMPL (S/4 HANA BUPA
Synchronization)
A business partner of type 'Employee' is then created which has an user assignment. For
this business partner also the type 'Resource' can be maintained, e.g. to define a cost rate.
How to Determine Relevancy
This Simplification Item is relevant if business partners of type 'Employee' and type
'Resource' with user assignments have been used in SAP Portfolio and Project
Management.
Other Terms
Page | 635
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Partner Approach, Resources
34.22 S4TWL - 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.
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.
Page | 636
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 2321885 provides a pre-conversion check for this feature.
Business Process related information
Since the new and simplified ACLs (Access Control Lists) concept is now used,
depending on the maintained authorizations the results of authorization determination
could now differ from results of the non simplified authorization concept in the SAP
Portfolio and Project Management solution. You can now check and adapt the
authorizations maintained in your projects according to the information given by the precheck.
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
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
Page | 637
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
34.23 S4TWL - 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
The default scheduling logic has changed since actual dates are no longer taken into
account by default.
Required and Recommended Action(s)
Page | 638
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
34.24 S4TWL - SAP Web Dynpro usage in SAP Port. and Proj. Management
for SAP S/4HANA
Application Components:
PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349580
S4TWL - SAP Web Dynpro usage in SAP
Port. and Proj. 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.
Page | 639
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Description
With SAP Portfolio and Project Management for SAP S/4HANA, it is planned to revise
various features in order to simplify the solution. This includes the renovation of the user
interface, whereas SAP Fiori is the preferred technology. That means that the SAP Web
Dynpro based user interfaces of SAP Portfolio and Project Management for SAP
S/4HANA are considered as not strategic anymore, means no major improvements are
currently planned based on this technology for the solution. This applies to the portfolio
management and project management part of SAP Portfolio and Project Management for
SAP S/4HANA and comprises for example:
•
•
•
SAP Web Dynpro based dashboards (e.g. project dashboard) and table views (e.g.
table view for the project structure)
SAP Web Dynpro based detail screens (e.g. detail view for the project structure
or for the portfolio item)
SAP Web Dynpro based functionalities, e.g. project favorites for the project
dashboard.
As the renovation with SAP Fiori is planned based on a step-wise approach according to
the roadmap of SAP Portfolio and Project Management for SAP S/4HANA and will take
some time, the SAP Web Dynpro based user interface can still be used to enable end-toend business processes.
Business Process related information
The renovation of the user interface of SAP Portfolio and Project Management for SAP
S/4HANA with SAP Fiori is planned to happen along business roles, to provide a more
simple solution for e.g. the project manager.
Required and Recommended Action(s)
No immediate action required, but with each additionally released SAP Fiori based app
you should check if you could apply it for your business process.
How to Determine Relevancy
This item is relevant for every customer of SAP Portfolio and Project Management for
SAP S/4HANA.
34.25 S4TWL - Changes compared to older releases than SAP Port. and
Proj. Mngt. 6.1
Page | 640
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Application Components:
PPM-PRO, PPM-PFM
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
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.
Page | 641
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
34.26 S4TWL - S4TWL - Not strategic functionalities within SAP S/4HANA
Application Components:
PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2349713
S4TWL - Not strategic functionalities within
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
With SAP Portfolio and Project Management for SAP S/4HANA, many features are
changed in order to improve and simplify the solution. To streamline the solution, some
features are removed. SAP plans to continue to improve, simplify and streamline SAP
Portfolio and Project Management for SAP S/4HANA in future. The list below
summarizes features which SAP considers as not strategic in SAP Portfolio and Project
Management for SAP S/4HANA, because there is a known need to change or replace
them in future. These features can still be used with SAP Portfolio and Project
Management 1.0 for SAP S/4HANA to enable an end-to-end business process, but could
be changed, removed or replaced by another feature in future according to the roadmap of
SAP Portfolio and Project Management for SAP S/4HANA.
•
•
•
•
•
•
Document management: There is a known need to adjust this feature with the
planned SAP Fiori Attachment Service.
Phase approvals: There is a known need for a more generic approval feature,
means a feature which also enables an approval process of e.g. milestones.
Decision flow management: With SAP Portfolio and Project Management for
SAP S/4HANA, it is planned to simplify the object and data model. Based on
that, there is a known need to adjust the decision flow management accordingly.
Field control: There is a known need to streamline the different field control
features of the solution.
SAP Smart Forms for E-Mail: There is a known need to replace SAP Smart
Forms.
Business Context Viewer: There is a known need to streamline different
analytical features.
Page | 642
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
Extractors for SAP Business Warehouse: There is a known need to streamline
different analytical features.
RFC enabled function modules of the project management as well as of the
portfolio management part: Both have never been released for usage by customer.
Integration to the PLM object navigator: There is a known need for a renovation
of this feature with SAP Fiori. According to that, the integration needs to be
adjusted.
Search within documents with SAP TREX: There is a known need to streamline
different search capabilities.
Integration with SAP Identity Management: There is a known need to streamline
different capabilities.
Business Process related information
Changes or replacements of the mentioned features should primarily influence how a
business process is supported by the solution, but do not necessarily lead to a change of
the business process itself.
Required and Recommended Action(s)
No immediate action required, but customers should be aware that one or more of the
mentioned features could be changed, removed or replaced by another feature in future.
How to Determine Relevancy
This item is relevant for every customer of SAP Portfolio and Project Management for
SAP S/4HANA.
34.27 S4TWL - 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
Page | 643
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
SAP Note 2321885 provides a pre-conversion check for this feature.
Business Process-Related Information
In case that control plans are used, the corresponding business processes have to be
adapted.
Required and Recommended Action(s)
The control plan data cannot be migrated to SAP Portfolio and Project Management for
SAP S/4HANA, therefore it is required to clean up the data before the system conversion
in order to prevent any data loss. Archive the corresponding projects or delete not needed
control plan data before you continue the system conversion.
The control plan UI field customizing (customer own) cannot be migrated to SAP
Portfolio and Project Management for SAP S/4HANA, therefore needs to be deleted.
Further details are described in the consulting note 2363785.
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
34.28 S4TWL - HTTP-Based Document Management in SAP Portfolio and
Project Management f
Application Components:
PPM-PRO, PPM-PFM
Related Notes:
Note Type
Note Number
Note Description
Page | 644
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Related SAP Notes
Conversion pre-checks SAP Note 2321885
Page | 645
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
34.29 S4TWL - Object Links to SAP Environmental Compliance in SAP
Portfolio and Projec
Application Components:
PPM-PRO, PPM-PFM
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.
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
34.30 S4TWL - Microsoft Project Import/Export in SAP Portfolio and
Project Management
Application Components:
PPM-PRO, PPM-PFM
Page | 646
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
SAP Note 2321885 provides a pre-conversion check for this feature.
Page | 647
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
35 Procurement
35.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
Collective
Processing of
MMPUR_CPPR_MAIN_APPL
Purchase
Requisition
Purchase
MMPUR_SPPR_MAIN_APPL
Requisition
Processing
Account
MMPUR_ACCOUNT_ASSIGN_COMP
assignments
MMPUR_ADDRESS_COMP
Display Address
MMPUR_BWLAUNCHER_APP
BW Starter
SAP S/4HANA Replacement
SAP GUI report
BBP_EXTREQ_TRANSFER,
Fiori Application
SAP GUI transaction ME51N,
Fiori Application
Smart Business? BW Integration?
Page | 648
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
MMPUR_CFOLDERS_EP_EVENT
MMPUR_CFOLDERS_URL_APP
MMPUR_DISPLSCHEDLINE_APP
MMPUR_DOCTRK_APP
MMPUR_DOC_TRACE
MMPUR_FINDSUPPLIER_COMP
MMPUR_FORECAST_APP
MMPUR_MAVERICK_APP
MMPUR_PRICECOND_APP
MMPUR_RELEASEDOC_APP
MMPUR_REL_STRAT_APP
MMPUR_SRCOFSUPPLY_APP
MMPUR_UI_PR_APP
MMPUR_VNDCONF_APP
MMPUR_VNDCTCDTA_APP
MMPUR_VNDPARTNER_APP
Document Storage
Document Storage
Display of
Delivery Schedule
Lines for Item
Document Tracing
Graphical
document tracing
Find Supplier
Expected Contract
Smart Business?
Release Orders
Maverick Buying
Smart Business?
Analysis
Pricing Conditions
Contract Release
Order
Release Strategy
Display Sources of
Supply
Purchase
Requisition
Processing
Process Different
Vendor
Confirmations
Display of Vendor
Contact Data
Including Contact
Persons
Display of Partner
Roles of a Vendor
Related SAP Notes
Custom Code related information
SAP Note: 2228261
35.2 S4TWL - Classic MM-PUR GUI Transactions replacement
Application Components:
MM-PUR-GF
Related Notes:
Note Type
Note Number
Note Description
Page | 649
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 will no
longer be available. The replacements that are available since SAP R/3 Enterprise 4.70
shall be used.
Business Process related information
No influence on business processes expected
Transaction not available in SAP ME21
S/4HANA on-premise edition
1511
ME22
ME23
ME24
ME25
ME26
ME27
ME28
ME51
ME52
Page | 650
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
ME53
ME54
ME59
MR01
MR1M
BAPI_PO_CREATE
BAPI_REQUISITION_CREATE
BAPI_PO_GETDETAIL
BAPIs not available SAP
S/4HANA on-premise edition
1511
Required and Recommended Action(s)
See SAP notes:
•
•
1803189: FAQ: End of Support of ME21, ME51, and BAPI_PO_CREATE etc.
144081: Replacing MR01 / Functions of MR1M (Release 4.6)
Related SAP Notes
Custom Code related
information
SAP Notes:
•
•
1803189: FAQ: End of Support of ME21, ME51,
and BAPI_PO_CREATE etc.
144081: Replacing MR01 / Functions of MR1M
(Release 4.6)
35.3 S4TWL - Dedicated SAP Supplier Lifecycle Management (SAP SLC)
business processes
Application Components:
SLC-SUP
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271188
S4TWL - Dedicated SAP Supplier Lifecycle
Management (SAP SLC) business processes
Page | 651
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 652
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
Conversion Pre-Checks
Pre-check required to guide customers who have installed SAP
SLC and SAP ERP on one server. See Simplification Item CoDeployment of SAP Supplier Lifecycle Management (SAP
SLC) for details.
35.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
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.
Page | 653
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
Custom Code
If customers have enhanced interfaces for point-to-point supplier
related information distribution from SAP SLC to SAP ERP using the SLC integration
component in SAP ERP, communication with MDG-S must
be enhanced accordingly.
35.5 S4TWL - Authority Concept for Supplier Invoice
Application Components:
MM-IV
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2271189
S4TWL - Authority 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.
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
Page | 654
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
35.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
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
Page | 655
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 VX99
SAP S/4HANA on-premise
edition 1511
EN99
FT/Customs: General overview
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
Page | 656
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
VECZ
INTRASTAT: XML File - Belgium
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
Page | 657
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Create
Page | 658
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
VE05
EXTRASTAT: Data selection for export
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
Page | 659
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
VX10
Countries of Destination for License
VX05
Customers for License
VX06
Export Control Classes for License
Page | 660
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
VE56
Check Export Control for Consistency
VI84
Doc.Payments: Check Customer Master
VX14N Maintain Financial Document
VX11N Create Financial Document
VX12N Change Financial Document
VX13N Display Financial Document
VI73N Foreign Trade: Maintain Long-Term Vendor Declaration
VI74N FT: Display Vendor Declaration
VI78
Foreign Trade: Countries
VI54
Customs Approval Numbers
VI55
Approval Number per Plant
VED1
Print Parameters for Export Documents
OVE1
Commodity Code / Import Code Number
VPAR
Archiving Preference Logs
VFAI
Archiving – INTRASTAT
VFAE
Archiving – EXTRASTAT
FTUS
Foreign Trade: Maintain User Data
ENCO Printing / Communication
ENGK
Legal Control
ENLO
Documentary payments
ENPR
Preference Processing
ENGR
Periodic Declarations
ENSV
Foreign Trade Data Maintenance
Page | 661
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Credit
Foreign Trade: Customer Master Consistency - Letter of
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
Page | 662
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
FTGR
Import Gds Receipt Analysis
FTEX
Export Bill. Documents Journal
FTEX
Exp.bill.doc.analysis
VE30
Expiring Licenses
VE29
Sales Orders for a License
VXA2
Financial Documents: List
VXA1
Financial Documents: SD Documents
VI74N Display Vendor Declaration
CAAT
Foreign Trade: Call up FT Atrium
VIUL
Foreign Trade: Data Upload
VIBA
Send IDoc Output-AES-Initial Procg
VIBC
Send IDoc Output-AES-Error in Procg
VIBB
Send IDoc Output-AES-Repeat Procg
VIB7
Send IDoc Output - Initial Procg
VIB9
Send IDoc Output - Error in Procg
VIB8
Send IDoc Output - Repeat Procg
VIB4
Print Transaction: Initial Procg
VIB6
Print Transaction: Error in Procg
VIB5
Print Transaction: Repeat Procg
VIB3
Foreign Trade Output Status
VEII
SAPMSED8: Call IMPINV01
VEIE
SAPMSED8: Call EXPINV02
VX00
Preference Handling
Page | 663
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
EU - Import Code Number
VA94
Merge:
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
Page | 664
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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)
Existing
Required and Recommended Action(s)
Analysis of all currently used foreign trade processes.
Related SAP Notes
Page | 665
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code related information
SAP Note: 2223144
35.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 to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
The previous concept was based on Request for Quote with a mandatory Supplier Field.
In addition it was only possible to enter one Supplier Quote per Request for Quote. This
does not fit to different Sourcing Integration Scenarios (Example Ariba Sourcing, Ariba
Spot Quote…).
With the new concept, the behaviour of the system allows to send RFQ via Fiori
App to external sourcing platforms without a Supplier included and to receive
from them multiple Supplier Quotes.
Following IDOCS and Transactions related to Request for Quote are not considered as
the target architecture (Functionality available in current SAP S/4HANA delivery but not
considered as future technology. Functional equivalent is not available).
It is planned to replace them with cXML messages:
REQOTE (Basic Idoc type = ORDERS05) is the IDOC for RFQ
QUOTES (Basic Idoc type = ORDERS05) is the Idoc for Quote
The following transactions are not strategic anymore and it is planned to replace
them with corresponding Fiori Apps:
ME41
ME42
ME43
Create
Change
Display
Create Request For Quotation
Change Request For Quotation
Display Request For Quotation
Page | 666
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
ME44
ME45
ME47
ME48
ME49
ME4B
ME4C
ME4L
ME4M
ME4N
ME4S
Maintain Supplement
Release
Maintain
Display
Price Comparison List
RFQs by Requirement
Tracking Number
RFQs by Material Group
RFQs by Vendor
RFQs by Material
RFQs by RFQ Number
RFQs per Collective Number
Maintain RFQ Supplement
Release RFQ
Create Quotation
Display Quotation
Price Comparison List
RFQs by Requirement Tracking Number
RFQs by Material Group
RFQs by Supplier
RFQs by Material
RFQs by RFQ Number
RFQs by Collective Number
Business Process related information
Before using the new Fiori App you need to close your open RFQ created with
the old transactions.
Required and Recommended Action(s)
You must edit the user roles . As soon as the new Fiori Apps will be available also
the standard roles delivered with SAP S/4HANA contain this new authorization
object.
35.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
Page | 667
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
35.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
Page | 668
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
35.10 S4TWL - Supplier Invoice New Archiving
Page | 669
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Application Components:
MM-IV, MM-IV-GF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2578291
Simplification Item: Supplier Invoice
Archiving
Symptom
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.
35.11 S4TWL - 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
Page | 670
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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 SAP Note:
Implementation 2186288
Description 2187627
35.12 S4TWL - Vendor evaluation based on LIS
Application Components:
MM-PUR-GF-LIS
Related Notes:
Note Type
Note Number
Note Description
Page | 671
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Impact
2267414
S4TWL - Vendor evaluation based on LIS
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 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
35.13 S4TWL - ERP Shopping Cart
Page | 672
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 673
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
/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
Page | 674
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
35.14 S4TWL - 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 MEW0
S/4HANA on-premise edition
1511
MEW1
Procurement Transaction
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
Page | 675
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code related information
SAP Note: 2228250
35.15 S4TWL - 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
Page | 676
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
35.16 S4TWL - 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
Conversion pre-checks
Custom code-related
information
Carefully follow the instructions in SAP Notes 2188695,
2189301, and 2220005.
SAP Note: Pre-checks delivered with Note 2188735.
SAP Note: 2220005
35.17 S4TWL - Output Management Adoption in Purchase Order
Page | 677
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 678
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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/4HANABased 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.
Page | 679
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
36 Sales & Distribution
36.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. As a first step, these roles offer a basic set of transactions that are
typically needed for the day-to-day work of a sales representative. During the next
releases, these roles will be further enhanced with custom-made apps based on FIORI.
For more information about this new concept, see SAP Note 2223838.
Business Process related information
Page | 680
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Transaction not available in SAP VPW1
S/4HANA
VPWL
Change View "Tasks"
Change View "Maintain Portal Targets"
Required and Recommended Action(s)
Adaption to the new FIORI role concept
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer has activated one of the
following Business Functions:
LOG_SD_SIMP_02
LOG_SD_CI_01
SD_01
36.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 CRMISA), SAP E-Commerce (component CRM-ISE), SAP Web Channel (component CRMMD-PCT) or SAP Web Channel Experience Management (component WEC) are not
available in SAP S/4HANA. From a technical point of view, these components require
TREX and IPC. Both components, however, are not available in SAP S/4HANA. From a
strategic point of view, the required web shop functionality based on the SAP S/4HANA
backend is provided by SAP hybris e-commerce in SAP S/4HANA 1610 OP.
Page | 681
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 ecommerce solution instead (available with S/4HANA 1610 OP).
Transaction not available in Transactions
SAP S/4HANA
• 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
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)
Page | 682
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
None
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using a web shop or an ecommerce solution based on one of the components mentioned above.
36.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
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
Page | 683
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
OVCC
Assign View to User
OVCD
Definition of Reporting View
OVCE
Control Update of Perform.Measures
OVCF
Control Reporting - Info Blocks
OVCI
C SD Set Workflow Action box
OVL5
Maintain Transit Time
SDCAS_MCQ
Call MC/Q From Address Selection
V+01
Create Sales Call
V+02
Create Telephone Call
V+03
Create Sales Letter
V+11
Create Direct Mailing
V+21
Create Sales Prospect
V+22
Create Competitor
V+23
Create Business Partner
VC_2
Customer Fact Sheet PDF Version
VC/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
Page | 684
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
VC/F
Sales Activity Description 06
VC/G
Sales Activity Description 07
VC/H
Sales Activity Description 08
VC/I
Sales Activity Description 09
VC/J
Sales Activity Description 10
VC01
Create Sales Activity
VC010102
Only Follow-up Activities
VC010103
Do not Delete Mail. Camp.+Addresses
VC010104
Internet mailing
VC01N
Edit Sales Activity
VC01N_DRAG_KONTAKT Edit Sales Activity
VC01N_DRAG_MAILING Edit Sales Activity
VC01N_M
Edit Mailing
VC02
Change Sales Activity
VC05
Sales support monitor
VC06
Parallel Processing for Address List
VC10
Report Tree - Select Addresses
VC10_BMENU
Area Menu for VC10
VC15
Crossmatching
VCR1
Competitive products
VCU3
Display Incompletion Log
VIM6
Customer Exits: Data Selection
VN05
No.Assignment for Address List(SSup)
Page | 685
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
VN06
Create No.Interval-Sales Activities
VOC1
Customizing for List of Addresses
VUC2
Maintain Incompletion Log
VV51
Create Output for Sales Activity
VV52
Change Output: Sales Activity
VV53
Display Output: Sales Activity
VVCB
Maintain Activity Authorization
Required and Recommended Action(s)
If sales support functionality is requested, we recommend that customers start evaluating
a side-by-side CRM on-premise scenario, or that they use Cloud for Customer.
Related SAP Notes
Custom code-related information
SAP Note: 2214585
36.4 S4TWL - Billing Document Output Management
Application Components:
SD-BIL
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267376
S4TWL - Billing Document Output
Management
Symptom
In SAP S/4HANA, a new output management approach has been implemented and is set
as the default for newly created billing documents.
Reason and Prerequisites
This note is relevant for you when your start release for the system conversion is an ERP
release. It is also relevant if your start release is SAP S/4HANA and you require
"special" output channels.
Page | 686
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 switch back to NAST-based output management.
Solution
As there are valid requirements and use cases for both frameworks with release SAP
S/4HANA OP 1610, there is a new customizing activity "Manage Application Object
Type Activation" where the active 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 Inactive" if you want to switch back to NAST.
For older releases, please refer to the included correction instruction on how to switch
back to NAST-based output management for all billing documents.
The output management framework is determined with the creation of the billing
document. If, following this, the framework is changed, the billing document will be
processed using the origin framework. This also applies for migrated billing documents.
For the SAP S/4HANA output control, configuration is different than for NAST-based
output management and must to be created in the Output Parameter Determination
(BRF+).
For technical and implementation details, please refer to simplification item “Output
Management” (SAP Note 2228611).
Business Process related information
SAP S/4HANA output control includes cloud qualities such as extensibility enablement,
multi- tenancy enablement, and modification-free configuration. Therefore, the entire
Page | 687
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
configuration differs from the configuration that is used when output management is
based on NAST. The configuration is technically based on BRFplus, which is accessible
in the cloud. The architecture of SAP S/4HANA output control is based on Adobe
Document Services and SAP Cloud Platform Forms by Adobe. For the form
determination rules (along with other output parameters), BRFplus functionality is used
(in combination with message determination).
The following forms are delivered by SAP and can be adapted:
- SDBIL_CI_STANDARD_... used for standard customer invoices
- SDBIL_CI_PROF_SRV_... used for professional service invoices
- SDBIL_CM_STANDARD_... used for credit memos
- SDBIL_IL_STANDARD_... used for invoice lists
Because the forms may differ from country to country, there is a separate form for each
country. For example, SDBIL_CI_STANDARD_DE is for Germany.
Other Terms
Billing Document Output Management, SAP S/4HANA output control
36.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
Page | 688
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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 VBO1
S/4HANA
VB(D
Create Rebate Agreement
Extend Rebate Agreements
Required and Recommended Action(s)
See the attached documents for more detailed information.
How to Determine Relevancy
Use SE16 to check table KONA: If table KONA contains records with ABTYP = ‘A’
then SD Rebate Processing is used.
Related SAP Notes
Custom code-related information
SAP Note: 2226380
Page | 689
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
36.6 S4TWL -Miscellaneous minor functionalities in SD Area
Application Components:
SD-SLS-GF, SD-BIL, SD-MD-CM
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.
Page | 690
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
36.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
Required and Recommended Action(s)
Page | 691
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
None
Related SAP Notes
Custom code-related information
SAP Note 2239184
36.8 S4TWL - SD Simplified Data Models
Application Components:
SD-BF, SD-BF-MIG
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
o elimination of index tables
o elimination of status tables
o simplified document flow
o 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
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,
Page | 692
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
LIKP and LIPS for deliveries, VBRK for billing documents.
This leads to increased performance, e.g.:
o 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.
o 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:
o Data element VBTYP (Char1) has been replaced by data element
VBTYPL (Char4);
o Field VBTYP_EXT (Char4) has been eliminated
Elimination of redundancies – Document index tables VAKPA, VAPMA,
VLKPA, VLPMA, VRKPA, VRPMA
Elimination of redundancies
o Rebate index table VBOX: See simplification item "SD Rebate Processing
replaced by Settlement Management", SAP Note 2267377.
o LIS tables S066, S067: See simplification item "Credit Management",
SAP Note 2270544.
The changes are described in more detail in the guidelines attached to the related SAP
Note 2198647.
Business Process-Related Information
No effects on business processes are expected.
Required and Recommended Action(s)
1. Adapt customer code according to the custom code check results, see SAP Note
2198647 for a detailed description.
2. If you have added one or more append structures to database tables VBUK or
VBUP (document status header and item table) in the source release to store
additional data for documents that are persistent in tables VBAK/VBAP,
LIKP/LIPS, or VBRK, and these fields are to be used in SAP S/4HANA, you
must ensure that the appended fields are added to the respective document tables.
An append field to the document header status table VBUK must be added to one or
several of the document header tables VBAK, LIKP, or VBRK. This decision depends on
which of the document types the respective field is relevant for. An append field to
document item status table VBUP must be added to one or more of the document item
tables VBAP or LIPS. Again, the choice depends on which of the document types the
respective field is relevant for.
Page | 693
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Each append field must have the same name and the same data type as it does in the
source table, and each one has to be appended to the table-specific status include
structure (DDIC structures VBAK_STATUS, LIKP_STATUS, VBRK_STATUS,
VBAP_STATUS or LIPS_STATUS). Only then will the field be considered by the
automatic data conversion from VBUK to VBAK/LIKP/VBRK and from VBUP to
VBAP/LIPS, as well as by read function modules that can be used to replace direct
SELECTs to the deprecated status tables VBUK/VBUP.
Do not choose a different field name or data type. Do not append the field directly to the
document table. It is possible to have several append structures for one status include
structure.
When do you have to add the append fields to the status include structures in order to
have the data transferred automatically during the SAP S/4HANA system conversion?
In the development system, you have to add the fields during phase ACT_UPG, when
you are prompted for SPDD. In all other systems, you may use modification adjustment
transports or customer transport integration during the upgrade-like conversion.
The append fields must be contained in one of the custom transport requests from the
development system.
The conversion pre-check class CLS4H_CHECKS_SD_DATA_MODEL delivered via
SAP Note 2224436 provides a check for such append fields and issues a warning if such
append fields are recognized in the source release. The warning refers to the necessary
action to add the append fields to the status include structures.
How to Determine Relevancy
This Transition Worklist Item is relevant if the custom code check shows results that
refer to note 2198647.
Related SAP Notes
Conversion pre-checks SAP Note 2224436
Custom code-related
Customer code has to be adapted according to the cookbooks in
information
SAP Note 2198647.
36.9 S4TWL - VBFA - Indirect Docflow Relationships
Application Components:
SD-BF-MIG
Related Notes:
Note Type
Note Number
Note Description
Page | 694
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 695
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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.
Page | 696
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
36.10 S4TWL - 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
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.
o Customer and document pricing procedure extensions allow for more
flexible pricing procedure determination.
o The number of possible customer condition tables for pricing has
been roughly doubled.
o The number of possible accesses in an access sequence has been enhanced
from 99 to 999.
o The key of condition tables ('A-Tables') can now be 255 characters long
(previously 100).
The removal of redundant fields from condition header table:
o reduces the memory footprint of condition records
o 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
Page | 697
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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:
o DDIC changes:
▪ The concatenated variable key field VAKEY of a condition
table has been removed from all condition header tables, including
KONH (pricing), NACH (output determination), KOND3
(campaign determination), KONDN (free goods determination),
KONHM (portfolio determination), J_3GPRLHD (CEM price list
determination), and WIND (document index). The concatenated
variable data field VADAT has also been removed. This was done
to avoid data migration of these tables as a result of the material
number extension.
▪ For internal processing, long data elements VAKEY_LONG and
VADAT_KO_LONG with length CHAR255 have been
introduced.
▪ The content of the new long VAKEY and VADAT can be
determined at runtime using methods of the service class
CL_COND_VAKEY_SRV.
Data element QUDIW (special value source in access sequence) has been
extended from CHAR20 to CHAR50. Data element SKONDTAB (CHAR128, for
archiving SD conditions) has been replaced by SDKONTAB_LONG
(CHAR512). Data element KOND_DATA (used for general condition
determination) has been extended from CHAR255 to CHAR512.
o
Interface changes:
▪ Batch input of price condition records (program RV14BTCI):
▪ For compatibility reasons, the field VAKEY_LONG
(CHAR255) has been added to the batch input structures. If
this field is filled or used by external programs, the content
of this field is used instead of the content of the still
existing field VAKEY.
▪ IDOC COND_A for price condition records:
▪ For compatibility reasons, the fields MATNR_LONG
(CHAR40), UPMAT_LONG (CHAR40), BOMAT_LONG
(CHAR40), and VAKEY_255 and VADAT_255 have been
added to the COND_A IDOC segments. If these fields for
the extended material number or long
VAKEY/VADAT are to be filled in addition to the still
existing short fields, the content of the long fields has
priority.
Page | 698
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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, Pricing formula and requirement
GRLNR, KOFRS
number
NUMC3
NUMC7
DZAEHK, DZAEHK_IND, Condition counter in pricing
DZAEKO, BBP_ZAEHK
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
Field is obsolete. Possible field content will be
merged with content of KOLNR and moved to
PRCD_ELEMENTS
KOLNR3
Access Sequence Access Number
STUFE
Level (in multi-level Field is obsolete and will not be transferred to
BOM explosions)
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.
Page | 699
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
•
•
•
•
•
Carefully follow the instructions in SAP Notes 2188695, 2189301, and 2220005.
If you have added one or more append structures to database table KONV in the
source release to store additional data, and these fields are to be used in SAP
S/4HANA, you must ensure that the appended fields are also added to the new
structure PRCS_ELEMENTS_DATA, which is included in all necessary tables
and structures, such as database tables PRCD_ELEMENTS and
PRCD_ELEM_DRAFT, for example.
Each append field must have the same name and the same data type as it does in
the source table.
When do you have to add the append fields to the structure
PRCS_ELEMENTS_DATA?
o In the development system, you have to add the fields
to PRCS_ELEMENTS_DATA during phase ACT_UPG, when you are
prompted for SPDD.
This is necessary to ensure that the automatic data migration transfers the
field content from KONV to PRCD_ELEMENTS during the upgrade-like
conversion.
o In all other systems, you may use modification adjustment transports or
customer transport integration during the upgrade-like conversion for the
appends to structure PRCS_ELEMENTS_DATA.
The append fields must be contained in one of the custom transport
requests from the development system.
The conversion pre-check delivered via SAP Note 2188735 provides a check for
such append fields and issues a warning if these append fields are recognized in
the source release. The warning refers to the necessary action to add the append
fields to the new database tables. An overview over the pre-checks is provided in
SAP Note. 2313318.
In the development system, you have to make all necessary adjustments in your
code to deal with the changed data model. See SAP Note 2220005 for
more information. You need to do this before going productive again.
SAP provides an automated migration to migrate data from the old database table
KONV to the new database table PRCD_ELEMENTS. However, the document
currency field WAERK of table PRCD_ELEMENTS needs to be filled with the
currency of the related document header. To reduce downtime, it was decided to
move this step to the post-processing phase. Within the automatic migration, the
currency is filled with the technical currency '2', allowing the system to correctly
convert PRCD_ELEMENT to KONV format and vice versa. However, to fill the
currency consistently in accordance with the related document, SAP recommends
that you run the post-processing report PRC_MIG_POST_PROCESSING as soon
as possible. After a recommended test, this report is supposed to run on the
productive data. However, note that running the report is not mandatory before
going productive again. Its execution can be postponed to a later point in time.
Page | 700
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
General information
Carefully follow the instructions in SAP Notes 2188695,
2189301, 2313318, and 2220005
SAP Note: Pre-checks delivered with Note 2188735
SAP Note: 2220005
Conversion pre-checks
Custom code-related
information
36.11 S4TWL - 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.
Solution
Business Value
With the new Intrastat Solution in SAP S/4HANA you will have:
1)
Optimized maintenance of the commodity code
•
•
•
•
Not limited to the plant level anymore
Time dependent
One numbering schema for multiple countries
Mass classification possible
2)
All User interfaces are build based on Fiori design principles
3)
The selection reports for Intrastat are simplified
4) Synchronization for the commodity codes between "SAP Global Trade Services"
(SAP GTS) and "SAP S/4HANA for international trade" without any manual interactions
Page | 701
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
5) A complete solution for letters of credit processing through integration of Sales and
Trade Finance of Treasury and Financial Risk Management in SAP S/4HANA.
Description
There are currently two software services for international trade transactions: Foreign
Trade and SAP Global Trade Services (SAP GTS).
Foreign Trade is part of the standard Sales and Distribution (SD) scope.
SAP GTS is an external service that can be installed on an additional instance.
As of SAP S/4HANA, the Foreign Trade functionality will be not available because SAP
GTS is the successor for this business requirement. With SAP S/4HANA 1709, letter of
credit processing is provided by integration of SAP S/4HANA Sales with Trade Finance.
For Intrastat, customers can leverage functions within SAP S/4HANA.
For Legal Control and Preference Management, you can use functions based on SAP
GTS. SAP GTS can be natively integrated with SAP S/4HANA.
Compare the Roadmap for SAP S/4HANA under
http://www.sap.com/solution/roadmaps.cross-topics.html, section "LoB: Sales; LoB:
Service"
Additional functions for Import and Export Management are available with SAP GTS.
Business Process-Related Information
The customer needs to check whether third-party foreign trade systems are in use for
foreign trade processes. Because of the replaced foreign trade functionality in SAP
S/4HANA, it is possible that the third-party foreign trade system will need to be adjusted
by the respective third-party solution/service provider. However, SAP GTS can be
connected to SAP S/4HANA to run the respective foreign trade processes.
Transaction not available in VX99
SAP S/4HANA
EN99
FT/Customs: General overview
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
Page | 702
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
VECZ
INTRASTAT: XML File - Belgium
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
Page | 703
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Create
Page | 704
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
VE05
EXTRASTAT: Data selection for export
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
Page | 705
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
VX10
Countries of Destination for License
VX05
Customers for License
Page | 706
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
ENPA
Foreign Trade: Periodic Declarations
ENPR
Preference Processing
Page | 707
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Credit
Foreign Trade: Customer Master Consistency - Letter of
VIE4
Periodic Declarations: Log of Incomplete Items
VE24X Foreign Trade: Information Commodity Code
VI24X
Foreign Trade: Information Import Code Number
FTIM
Journal: Purchase Orders
Page | 708
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 709
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
VEIE
SAPMSED8: Call EXPINV02
VX00
Preference Handling
LEAN
Request long-term VendDecl. (vendor)
LEMA
Dun long-term vendor decl. (vendor)
VE67
Aggregate Vendor Declarations
LEER
Create long-term VenDecl. (customer)
VE55
Preference Determination: Individual
VE54
Preference Determination: Collective
VEB5
Calculate Assemblies Individually
VEB6
Calculate Assemblies Collectively
VEPR
Customs log
VE91
Display Preference Values
VE90
Change preference values
VE83
Check Report: Preference Data
VE66
Preference Procedure
VE65
Preference Reg./Percentage Rates
VE64
Commodity Code/Customs Areas
VE94
Load Commodity Code for EU Countries
VEM4
Merge: EU - Commodity Code
VI94
Load Import Code Nos - EU Countries VIM4
EU - Import Code Number
VA94
Merge:
Load Commodity Codes for Japan
VAM4 Merge: Japan - Commodity Code
VP94
Load Import Code No. for Japan
Page | 710
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
VPM4 Merge: Japan - Import Code Number
VEU4
Load Commodity Code-Other Countries
VEI4
Merge: Remaining Commodity Codes
VIU4
Load Import Code No.-Other Countries
VII4
Merge: Rest - Import Code Number
VE24
Comm. Code Number Information (old)
VI24
Code Number Information – Import
VI20
Display Customs Quota
VI21
Display Pharmaceutical Products
VI22
Display Customs Exemption
VI23
Display Preferential Customs Duties
VI19
Display Third-country Customs Duties
VI18
Display Anti-dumping
VXA3 Financial Documents: Blocked Docs VXA2
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)
Existing
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)
Page | 711
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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 financial documents in Foreign Trade to Trade Finance, you carry out
the migration steps available as Customizing activities (transaction SPRO, SAP
Reference IMG) under:
o Conversion of Accounting to SAP S/4HANA-->Preparations and
Migration of Customizing-->Preparations for Migration of Financial
Documents to Trade Finance
o 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
o Conversion of Accounting to SAP S/4HANA-->Activities after Migration->Manual Activities for Trade Finance
Related SAP Notes
Conversion pre-checks
Custom code-related information
SAP Note: 2205202
SAP Note: 2223144
36.12 S4TWL - Credit Management
Application Components:
FI-AR-CR, SD-BF-CM
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:
Page | 712
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
A. You are only using FI-AR-CR Credit Management in your source release
B. You are only using SAP Credit Management (FIN-FSCM-CR) in your source
release
C. You are using both Credit Management solutions (FI-AR-CR & FIN-FSCM-CR)
in your source release
D. 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”.
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)
Page | 713
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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 onesystem 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. To use
transaction UKM_MY_DCDS, the credit specialist might
Page | 714
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
need additional authorizations. As a workaround, the
transactions VKM1 and VKM4 are still available.
Transactions not available F.28 - Customers: Reset Credit Limit
in SAP S/4HANA
F.31 - Credit Management - Overview
F.32 - Credit Management - Missing Data
F.33 - Credit Management - Brief Overview
F.34 - Credit Management - Mass Change
FCV1 - Create A/R Summary
FCV2 - Delete A/R Summary
FCV3 - Early Warning List
FD24 - Credit Limit Changes
FD32 - Change Customer Credit Management (but FD33
still available for Migration checks)
FDK43 - Credit Management - Master Data List
S_ALR_87012215 - Display Changes to Credit Management
S_ALR_87012218 - Credit Master Sheet
VKM2 - Released SD Documents
VKM3 - Sales Documents
VKM5 - Deliveries
Reports not available in
RFARI020 - FI-ARI: Extract from credit master data
SAP S/4HANA
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
Page | 715
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
o 2227014 (Financials)
o 2227014 (SD)
2. Perform the recommended actions in the Task List PDF attached to this Note (only
available in English). This list is only valid for the conversion of one-system landscapes.
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)
Custom code-related information
(Financials)
SAP Note: 2217124
SAP Note: 2227014
Page | 716
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
36.13 S4TWL - 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.
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 VF42 "Update Sales Documents"
in SAP S/4HANA
VF43 "Revenue Recognition: Posting Doc"
VF44 "Revenue Recognition: Work List"
VF45 "Revenue Recognition: Revenue Report"
Page | 717
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
VF46 "Revenue Recognition: Cancellation"
VF47 "Revenue Recognition: Consistency Check"
VF48 "Revenue Recognition: Compare Report"
Required and Recommended Action(s)
Prior to the Conversion to SAP S/4HANA, you need to migrate all sales order and
contracts processed by SD Revenue Recognition to SAP Revenue Accounting and
Reporting that are
•
•
•
not fully delivered and invoiced
have deferred revenue still to be realized
and for which you expect follow-on activities like increase quantity, create credit
memo or cancel invoice
Please note that release 1.3 of SAP Revenue Accounting and Reporting does not include
the full functional capabilities of SD Revenue Recognition. Examples of unavailable
functionalities in SAP S/4HANA include:
•
•
Revenue Recognition Type D (billing-based): Invoice cap is not available.
Call Off Orders: While SD Contracts are supported call of orders are not
available.
If you are using SD Revenue Recognition, you need to evaluate whether a migration
to SAP Revenue Accounting and Reporting is possible for your business before you
decide to convert to SAP S/4HANA.
You can find more details about the migration to SAP Revenue Accounting and
Reporting can in the migration chapter of the online help (RevAcc Help) and in the
administrator guide for the product SAP SD Integration with SAP Revenue Accounting
and Reporting: Admin Guide Integration SD
Related SAP Notes
Conversion pre-checks
Custom code-related information
SAP Note: 2227824
SAP Note: 2225170
36.14 S4TWL - Optimization of SD Rebate Processing for TPM Customers
Application Components:
SD-BIL-RB
Related Notes:
Note Type
Note Number
Note Description
Page | 718
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
severely reduced database footprint.
Additional information can be found in note 2200691 and the documentation/notes for
business function LOG_SD_REBATE_INDEX.
Description
Customers who will integrate their existing CRM TPM scenario with SAP S/4HANA
need to use SD Rebate Processing, even though a successor is already being provided by
Settlement Management (cp. simplification item SD Rebate Processing replaced by
Settlement Management).
For these customers, the existing SD Rebate functionality has been optimized with regard
to the database footprint. For this purpose, from a technical viewpoint, the rebate index
table VBOX is not available.
Business Process-Related information
Please note that TPM customers are also unable to neither create new rebate agreements
in SAP S/4HANA nor extend existing ones (cp. simplification item SD Rebate
Processing replaced by Settlement Management). However, for the TPM process this is
not necessary at all, since for this business process, rebate agreements are created by
CRM TPM.
Transaction not available in SAP VBO1
SAP S/4HANA
VB(D
Create Rebate Agreement
Extend Rebate Agreements
Required and Recommended Action(s)
•
•
If the customer is using the extended SD rebate processing, a rebuild of the S469
content is required after the upgrade.
The customer has to maintain new customizing settings.
Page | 719
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
How to Determine Relevancy
This Transition Worklist Item is only relevant if the customer is using Trade Promotion
Management in his CRM system which is connected with the ERP system.
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 use Trade Promotion Management in
CRM.
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
36.15 S4TWL - Simplification in SD Analytics
Application Components:
SD-IS, SD-HBA-VDM, SD-HBA-SOF
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2267348
S4TWL - Simplification in SD Analytics
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item applies in this scenario.
Solution
Description
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.
Page | 720
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
CDS Basic Views Represent the Core Entities in SD
The SD-specific business objects Sales Order, Customer Invoice, Outbound Delivery,
and many others on top of database tables VBAK, LIKP, and VBRK are represented by
CDS views that encompass access of the analytics CDS queries to the database in a
uniform manner. This is achieved by offering semantic field names and associations
to connected business objects, such as Customer, Material, and so on.
All analytics content will be built on top of these core entities.
Incoming Sales Orders and Sales Volume Based on CDS Views
The initially delivered analytics content consists of two CDS queries: Incoming Sales
Orders and Sales Volume. These two exemplify the capability of SAP S/4HANA to
report directly on the database, without any prebuilt aggregates, but with the possibility to
make use of all dimensions for grouping, aggregation, and filtering on the fly.
New Persistent Fields in the Database
To make effective use of SAP S/4HANA's capabilities for SD Analytics, there are new
persistent fields in the database (which, in the past, were only calculated on the fly):
•
•
Sales Order Open Delivery Quantity and Amount (on schedule line level - VBEP)
Sales Order Requested Quantity in Base Unit (on item level - VBAP)
Further Usage of BW and LIS/SIS[1]
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.
Customers are allowed to make extended use of the LIS/SIS[2] tool, as long as the CDSbased approach in SD is not yet available in a comparable standard. LIS is part of the
compatibility package "ERP Package". See note
https://launchpad.support.sap.com/#/notes/2269324 for details of the Compatibility
Packages.
Business Process-Related Information
No impact on business processes is expected.
Transaction not
available in SAP
S/4HANA
VA06
Sales Order Monitor
Instead of transaction VA06
SAP recommends the Fiori App
'Sales Order Fulfillment Issues'
Required and Recommended Action(s)
None
Page | 721
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer is using transaction VA06.
Customers using LIS/SIS and customers extracting data from SAP ERP to their own BWHub can continue with these processes in SAP S/4HANA considering the additional
information in the referenced notes.
Related SAP Notes
Custom code-related information
SAP Note: 2227750
[1] Functionality available in the SAP S/4HANA delivery, but not considered as future
technology. Functional equivalent is available.
[2] Note: If you use a material number longer than 18 characters - see restriction note
“Extended Material Number in LIS: SAP Note 2232362”.
36.16 S4TWL - 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
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
Page | 722
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 VACB
Advanced Order Processing and Billing
S/4HANA
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
36.17 S4TWL - 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
Page | 723
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Operational Data Provisioning in SD (see SAP Help: Link) is not available in SAP
S/4HANA.
Simplification in SD Analytics follows the overall analytics strategy in SAP S/4HANA
(see Simplification Item SD Analytics): The SAP S/4HANA Analytics approach is based
on ODATA and Open CDS (also known as ABAP-managed Core Data Services (CDS)),
which sit directly on top of the original database. Corresponding analytics content will be
provided in SAP S/4HANA. This content will grow over time.
Successor: HANA Analytics
CDS Basic Views Representing the Core Entities in SD
The SD-specific business objects Sales Order, Customer Invoice, Outbound Delivery,
and many others on top of database tables VBAK, LIKP, and VBRK are represented by
CDS views that encompass access of the analytics CDS queries to the database in an
uniform manner by offering semantic field names and associations to connected business
objects as Customer, Material, and so on.
All analytics content will be built on top of these core entities.
Business Process-Related Information
No impact on business processes is expected.
Required and Recommended Action(s)
If operational or analytical reporting is requested, it is recommended that the customer
starts evaluating the use of HANA Analytics.
How to Determine Relevancy
This Transition Worklist Item is relevant if the customer has used Operational Data
Provisioning in SD.
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
Page | 724
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
37 Transportation Manangement
37.1 S4TWL - Simplified customizing of Transportation Manangement (TM)
integration
Application Components:
TM-FRS, TM-FRS-IP, TM-FRS-IV
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.
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
Page | 725
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
If you have any of the above combinations of data in the source table, Review these
entries to adjust the right settings either by
Page | 726
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
37.2 S4TWL - Forwarding Settlement Document Transfer in TM
Application Components:
TM-FWS-BIL, TM-FWS
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
Symptom
Page | 727
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 forwarding settlement process integration with Sales and
Distribution(SD) with SAP TM in a side-by-side mode.
As a part of integration, there are mappings maintained for TM sales organization to the
SD sales organization in addition to the mapping of forwarding settlement document
(FWSD) type to sales document type, pricing procedure, billing type in the view
TCM_V_SLS_MAP.
The system conversion is planned to S/4HANA 1809 or system upgrade is planned from
S/4HANA 1511 or S/4HANA 1610 or S/4HANA 1709 to S/4HANA 1809.
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 also. Also this has
impact to the side-by-side integration with S/4HANA 1809 onwards.
The mapping requirement for the posting of the forwarding settlement document in
S/4HANA 1809 is now changed. From S/4HANA 1809 release onwards, the usage of
the view TCM_V_SLS_MAP and the underlying customizing table TCM_C_SLS_MAP
have been discontinued.
For posting the intracompany settlement document in S/4HANA 1809, the usage of the
view TCM_V_TCD_MAP , TCM_V_TCDPURMAP and the underlying customizing
tables TCM_C_TCD_MAP and TCM_C_TCD_PURMAP respectively have been
discontinued.
Description :
In a side by side scenario, with S/4HANA 1809, there are the following changes required.
1. The mapping of sales organization unit from TM org data to the SD Sales
organization is no longer required in S/4HANA. SAP TM sends this mapping
information with the message type: CustomerFreightInvoiceRequestSUITERequest used
in the A2A service interface: CustomerFreightInvoiceRequestSUITERequest_In_V1 on
S/4HANA.
Page | 728
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2. The other information for posting of the forwarding settlement document such as Sales
document type, billing type , billing item type and pricing procedure are now
maintained in the maintanence view /SCMTMS/V_CFSD_T based on the
/SCMTMS/C_CFIR_T table . You now maintain the sales document type, billing type
, billing item type and pricing procedure at the forwarding settlement document type
level.
System conversion or upgrade shall take care of copying the entries from the source table
TCM_C_SLS_MAP to the target table which is /SCMTMS/C_CFIR_T table and the
/SCMTMS/C_COMMON table. For the copy to happen successfully, there should not be
conflicting entries for the same FWSD type or entries with blank FWSD types in the
source table i.e. in table TCM_C_SLS_MAP.
Also system conversion or upgrade shall take care of copying the entries from the source
table 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 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) :
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 and
/SCMTMS/C_COMMON table 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 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
Page | 729
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 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.
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 and
TCM_C_TCDPURMAP table to the TCM_C_SLSASSGN and 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 sales organization/purchase organization are 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 a appropriate logical system
2. Maintain the TM sales organization/purchase organization
3. Maintain the controlling area, internal order and cost center for all entries
NOTE: Before conversion please also check if there are FWSDs 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 FWSDs for posting.
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 and
/SCMTMS/C_COMMON table via an XPRA which will be executed during the upgrade
/ system conversion process, it is required that the source table doesn't contain :
Page | 730
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 731
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
38 Globalization Financials
38.1 S4TWL - Globalization – Financials
Application Components:
XX-CSC-XX, FI-LOC
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 countryspecific 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.
38.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.
Here new Business Functions and switches have been provided to make Area Menus,
IMG nodes etc. switchable.
Page | 732
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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,
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).
Page | 733
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
38.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 S/4HANA
On-Premise 1709
Symptom
The SAP LOCPTFM Add-on (software component LOCPTFM) has been integrated into
S/4HANA On-Premise Edition, as of release S/4HANA 1709 OP.
However, the Portuguese Public Sector Funds Management features are available as of
release S/4HANA On-Premise Edition 1709 FPS01 with one restriction (See Solution).
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 Localization for Portuguese
Public Sector solution implemented in system via transports solution or via LOCPTFM
add-on.
It is not relevant for release S/4HANA OP 1709, FPS 00.
Solution
The functionality for Portuguese Public Sector Funds Management will be available in
Feature Pack 1 for S/4HANA 1709 On-Premise, with the following restriction:
•
As a Customer who used the integration between Logistics documents and Funds
Management with LOCPTFM and are planning to move to S/4HANA OnPremise, please be aware that in S/4HANA, the Funds Management integration
with Materials Management has been enhanced to accomodate country-version
Portugal requirements. However, a document chain initiated with the LOCPTFM
Add-on cannot migrate to 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 S/4HANA.As a Customer who used the
integration between Logistics documents and Funds Management with
Page | 734
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
LOCPTFM and are planning to move to S/4HANA On-Premise, please be aware
that in 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 precommitment document) the new functionality can be used but not for an
unfinished document chain.
For detailed information on the system installation / conversion of the Portuguese Public
Sector Funds Management, available in Feature Pack 1 for S/4HANA 1709 On-Premise,
please see SAP Note 2595915, Customer Installation/Conversion Procedures for
Portuguese LOCPTFM in S/4HANA On-Premise.
Other Terms
Globalization, Localization, Add-on, PT, Portugal, PTFM, Funds Management, Public
Sector, LOCPTFM, PSM-FM
Page | 735
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
39 Globalization Logistics
39.1 S4TWL - Globalization – Logistics
Application Components:
FI-LOC-LO, FI-LOC, XX-CSC-BR, XX-CSC-BR-REP
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:
•
•
SAP Tax Declaration Framework for Fiscal and Accounting Legal Reporting.
TAXBRA tax procedure for the tax calculation.
Page | 736
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note: SAP Tax Declaration Framework is part of the Compatible Add-ons and requires
an additional license.
Related SAP Notes
General
Custom Code related
information
SAP Note: 2244803 - Fiscal and Accounting Legal
Reporting for SAP S/4HANA, on premise edition 1511
SAP Note: 2195701
Page | 737
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
40 Industry – Cross
40.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.
40.2 S4TWL - BRIM - Common Object Layer (COL)
Application Components:
FI-CA
Page | 738
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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).
Page | 739
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
40.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. The
functionality is not considered as the target architecture, but customers can still continue
to use it to make the upgrade to S/4 less disruptive (Functionality is available in SAP
S/4HANA on-premise edition delivery but not considered as future technology.
Functional equivalent is not available).
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.
40.4 S4TWL - BRIM - Solution Sales and Billing
Application Components:
FI-CAX, SD-BIL-IV-CB
Related Notes:
Page | 740
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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".
Page | 741
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
40.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
Page | 742
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
PSCD_COLLECTIONS_MANAGEMENT_4G
TEL_INV_2G
Afterwards, the joint master data replication needs to be activated in the IMG
customizing under Contract Accounts Receivable and Payable -> Integration ->
Convergent Charging -> Activate Joint Replication of All Master Data. For further
activities, please refer to the documentation of this IMG activity.
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
Page | 743
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
available from SAP ERP 6.0 EHP7 SPS14 and SAP ERP 6.0 EHP8 SPS06 onwards.
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.
Page | 744
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Page | 745
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
41 Industry Banking
41.1 S4TWL - SEM Banking
Application Components:
IS-B-SA, IS-B-RA, IS-B-DP, IS-B-PA
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
2144579
Release Restriction
2328754
Release Restriction
2211665
Release Restriction
2484134
Release Restriction
2059467
Business Impact
2270318
Release Information for SAP for Banking
together with SAP Simple Finance, OnPremise Edition 1503 & 1605
Release information for "SAP for Banking"
in connection with "SAP S/4HANA 1610"
("SAP S/4HANA, on-premise edition
1610")
Release information for "SAP for Banking"
in connection with "SAP S/4HANA, onpremise edition 1511"
Release information for "SAP for Banking"
in connection with "SAP S/4HANA 1709"
("SAP S/4HANA, on-premise edition
1709")
Release Information for SAP for Banking
together with SAP Simple Finance add-on
1.0 for SAP Business Suite powered by SAP
HANA
S4TWL - SEM Banking
Release Restriction
2661159
Release Information für "SAP for Banking"
im Zusammenhang mit "SAP S/4HANA
1809" ("SAP S/4HANA, on-premise edition
1809")
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 SEM Banking functionality is not included in SAP S/4HANA.
Page | 746
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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).
How to Determine Relevancy
There is an active risk management area and / or there is an active Banking operating
concern in the system
Page | 747
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
Custom Code related information
For more details see SAP Note 2211665
Other Terms
SEM Banking
41.2 S4TWL - CML-specific functions with regard to collaterals and
collateral objects
Application Components:
FS-CML
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
2059467
Release Restriction
2144579
Release Restriction
2328754
Business Impact
2369934
Release Restriction
2661159
Release Restriction
2484134
Release Restriction
2211665
Release Information for SAP for Banking
together with SAP Simple Finance add-on
1.0 for SAP Business Suite powered by SAP
HANA
Release Information for SAP for Banking
together with SAP Simple Finance, OnPremise Edition 1503 & 1605
Release information for "SAP for Banking"
in connection with "SAP S/4HANA 1610"
("SAP S/4HANA, on-premise edition
1610")
S4TWL - CML-specific functions with
regard to collaterals and collateral objects
Release Information für "SAP for Banking"
im Zusammenhang mit "SAP S/4HANA
1809" ("SAP S/4HANA, on-premise edition
1809")
Release information for "SAP for Banking"
in connection with "SAP S/4HANA 1709"
("SAP S/4HANA, on-premise edition
1709")
Release information for "SAP for Banking"
in connection with "SAP S/4HANA, onpremise edition 1511"
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Page | 748
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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".)
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 CMLspecific 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
Page | 749
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
CML collaterals and collateral objects
Page | 750
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
42 Industry Beverage
42.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 ISBeverage 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-codeadaptation-process/
Other Terms
IS-Beverage; S/4HANA; Excise Duty; Deprication
42.2 S4TWL - IS-Beverage (Sales Returns)
Application Components:
SD-SLS-PLL, MM-IM-ED, SD-SLS-RE-SR, SD-BF-EC, SD-BF-AC
Related Notes:
Page | 751
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 ISBeverage 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-codeadaptation-process/
Other Terms
IS-Beverage; S/4HANA; Sales Returns; Deprication
42.3 S4TWL - IS-Beverage (Empties Management)
Application Components:
SD-BIL-EM, MM-PUR-EM
Related Notes:
Note Type
Note Number
Note Description
Page | 752
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Impact
2531901
Restricted Availability of Empties
Management as part of the IS-Beverage
Solution
Symptom
Empties Management is available with S/4HANA On Premise 1610 FPS2 in
compatibility mode.
It is a non strategic function and for the time beeing it has not been defined if and when
there will be an equivalent available.
Reason and Prerequisites
With the transition from ERP to S/4HANA old Beverage functionalities
will be available in restricted usage.
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-codeadaptation-process/
Other Terms
IS-Beverage; S/4HANA; LE-DSD; LE-TRA; Direct Store Delivery
42.4 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
Page | 753
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The IS-Beverage functionality Pendulum List is unavailable in S4HANA. In 2004 the ISBeverage 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-codeadaptation-process/
Other Terms
IS-Beverage; S/4HANA; Pendulum List; Deprication
Page | 754
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
43 Defense&Security
43.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)
Implement Business Scenarios and Business Processes based on the functionality
available within SAP S/4HANA.
Page | 755
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
43.2 S4TWL - BI content, Datasources and extractors for DFPS
Application Components:
BW-BCT-DFS-MM, BW-BCT-DFS-PM, BW-BCT-DFS-OF
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
Solution
Description
Page | 756
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 CDSViews 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
43.3 S4TWL - Integration of DFPS with Investigative Case Management
(ICM)
Application Components:
IS-DFS-ICM
Related Notes:
Page | 757
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 758
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
43.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)
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
Page | 759
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 760
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
44 Industry DIMP - Aerospace & Defense
44.1 S4TWL - Collective Processing Pegging
Application Components:
IS-ADEC, IS-ADEC-GPD
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
Page | 761
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
44.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.
ADAA
Transactions not available with SAP S/4HANA
AD02PRCE - Program t
Programs/Reports not available with SAP S/4HANA
AD02ACTV - Activity
AD02_HIERARCHY_D
Required and Recommended Action(s)
No influence on business processes expected.
Eliminate the indicated usages from your customer objects.
Page | 762
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
44.3 S4TWL - Cost Distribution Processing
Application Components:
IS-ADEC-GPD, IS-ADEC
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
44.4 S4TWL - Manufacturer Part Number
Application Components:
IS-ADEC-MPN
Page | 763
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
•
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'.
Page | 764
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
'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.
Page | 765
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
'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.
Page | 766
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 SAPdelivered 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
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.
Page | 767
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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
•
Deprecated objects
Object
Type
Object Name
FUNC
It is no longer relevant as there is
no conversion done for the MPN
MPN01_CHECK_MPN_CONVERSION
Material. MPN Material is stored
directly in MARA-MATNR.
DTEL
MPN_OUTLEN
Use the data element
'OUTPUTLEN' instead
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.
MSAG
Remarks
Page | 768
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
PROG
Not relevant. Remove the usage of
this include from your code
FMPN30LCCD
MPNUPGRADE01
MPNUPGRADE02
PROG
MPNUPGRADETOP
RMPNAFTERUPGRADE
RIXPRA_ISAD30
PROG
RIXPRA_ISAD30_3
This is a reconciliation report after
upgrade in EHP releases. Not
required. There are separate
conversion programs available for
conversion to S/4HANA1610
release.
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:
2334012
2334008
SAP Notes
2270836
2360860
Other Terms
SAP S/4HANA System Conversion, MPN, Manufacturer Part Number,
S4_TRANSFORMATION
44.5 S4TWL - Flight Scheduling
Application Components:
IS-ADEC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270837
S4TWL - Flight Scheduling
Symptom
Page | 769
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
44.6 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
Page | 770
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
44.7 S4TWL - Enhancements Subcontracting Special Stock Types Not
Available
Application Components:
IS-ADEC, IS-ADEC-SUB
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.
Page | 771
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
44.8 S4TWL - AECMA SPEC 2000M Military Version
Application Components:
IS-ADEC, IS-ADEC-SPC
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
44.9 S4TWL - Obsolete transactions and Enhancements in GPD
Application Components:
IS-ADEC-GPD
Page | 772
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 773
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
The below described objects related to GPD are no longer available in SAP S4HANA.
CANCDIS01 - Collective Processing Distribution
PEG12 - Filling of Pegging Worklist
Transactions not available in SAP S/4HANA
PEG13 - Pegging: Unassigned Replenishments
PEG15 - Transfer Pegging Program
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
Business Add-Ins not available in
BADI_GPD_11 - Pegging: Fixing rule - Building real
SAP S/4HANA
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
Page | 774
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
GDP_MM_EKKO_WRITE - MM_EKKO: Write GPDspecific 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_0
ES_BADI_GPD_PEGGING
2
BADI_GPD_PEG_SURPLUS
BADI_GPD_0
ES_BADI_GPD_PEGGING
3
BADI_GPD_PEG_SCRAP
BADI_GPD_0
ES_BADI_GPD_PEGGING
4
BADI_GPD_PEG_LOST
BADI_GPD_0
ES_BADI_GPD_PEGGING
5
BADI_GPD_PEG_ADJ_BEFORE_COMP
L
BADI_GPD_0
ES_BADI_GPD_PEGGING
6
BADI_GPD_PEG_BREAKPOINT
BADI_GPD_0 ES_BADI_GPD_DISTRIBUTIO
BADI_GPD_DIS_ADJUST_COST_CASH
7
N
BADI_GPD_0 ES_BADI_GPD_DISTRIBUTIO BADI_GPD_DIS_BEFORE_DB_UPDAT
9
N
E
BADI_GPD_1
ES_BADI_GPD_PEGGING
1
BADI_GPD_PEG_FIXING_RULE
BADI_GPD_1
ES_BADI_GPD_PEGGING
2
BADI_GPD_PEG_SURPLUS
BADI_GPD_1
ES_BADI_GPD_PEGGING
4
BADI_GPD_PEG_SCRAP
BADI_GPD_1
ES_BADI_GPD_PEGGING
5
BADI_GPD_PEG_LOST
BADI_GPD_1
ES_BADI_GPD_PEGGING
7
BADI_GPD_PEG_ADJ_BEFORE_COMP
L
BADI_GPD_1
ES_BADI_GPD_PEGGING
8
BADI_GPD_1
ES_BADI_GPD_PEGGING
9
BADI_GPD_PEG_TECO_LOGIC
BADI_GPD_PEG_CUST_DATA
BADI_GPD_PEG_MAT_GRP_SEGM
Page | 775
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
45 Industry DIMP – Automotive
45.1 S4TWL - Vehicle search using SAP TREX as external search engine
Application Components:
IS-A, IS-A-VMS, IS-A-VMS-SR
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 (ECCDIMP) to SAP S/4HANA.
Solution
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECCDIMP) 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
The vehicle search in VMS using either SAP TREX as external search engine or Live
Cache technology is not supported with SAP S/4HANA.
Page | 776
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
45.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
Symptom
Page | 777
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
with respect whether the handling units should be created as planned or directly as
physical existent:
Page | 778
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
o
o
o
o
o
o
o
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
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
Page | 779
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
sales and shipping, and/or with respect whether the handling units should be created
as planned or directly as physical existent:
o
o
o
o
o
o
o
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
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
Page | 780
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Other Terms
COWBPACK, HUP1, Automatic packing, Automotive, ECC-DIMP, S/4HANA
45.3 S4TWL - Tracking Inbound
Application Components:
IS-A-TRI
Related Notes:
Note Type
Note Number
Note Description
Page | 781
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 (ECCDIMP) to SAP S/4HANA.
Solution
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECCDIMP) for tracking of inbound deliveries and shipments is not available with SAP
S/4HANA.
To calculate and track the exact time of arrival, the recipient of goods could use the
tracking of inbound deliveries and shipments. Event information could be received via
EDI message with type TRXSTA and processed with reference to an inbound delivery or
inbound shipment. The event location had to be defined as node of a route assigned to the
delivery or shipment document. The event time is used then to calculate the expected
time of arrival based on the duration information stored with the route for scheduling.
The automotive industry solution for tracking of inbound deliveries and shipments has a
low customer adoption rate. With SAP Transportation Management, a much more
comprehensive and scalable solution exists.
Business Process related information
The industry-specific solution for tracking of inbound deliveries and shipments is not
available with SAP S/4HANA.
How to Determine Relevancy
The Simplification Item is relevant, if:
Page | 782
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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
45.4 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 (ECCDIMP) to SAP S/4HANA.
Solution
Page | 783
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
The Supplier Workplace (SWP) is an early collaboration solution in SAP ERP Discrete
Industries & Mill Products (ECC-DIMP), enabling suppliers to access supplier-related
data directly from the SAP ERP system of a company in addition or as an alternative to
EDI communication. With SWP, the company could allow their suppliers to display
purchasing documents and price information, view and confirm scheduling agreement
releases, create, change or display inbound deliveries, view goods receipt and settlement
information, and returnable packaging account information.
The Supplier Workplace has a low customer adoption rate, is not strategic and the
technology used is no longer the target architecture, therefore it will be not available with
SAP S/4HANA.
With SAP Ariba and Ariba Networks or SAP Supply Network Collaboration (SNC),
there are successors available.
Business Process related information
Implementing a successor solution for supplier collaboration will result in a change in the
IT system landscape and integration as well as in the business applications used for
supplier collaboration.
Not all scenarios covered by SWP are supported by the successor products.
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
Page | 784
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
Supplier Workplace users have been assigned to vendors (check for entries in
table ISAUTOSICVENDTAB with transaction SE16)
Required and Recommended Action(s)
Evaluate SAP Ariba / Ariba Networks or SAP Supply Network Collaboration as
successor or alternative solution.
Remove all Supplier Workplace users assigned to vendors from table
ISAUTOSICVENDTAB.
Related SAP Notes
Pre Check
Custom Code Check
SAP Note 2326822
SAP Note 2228218
Other Terms
Automotive, ECC-DIMP, S/4HANA, Supplier Workplace, SWP
45.5 S4TWL - 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 (ECCDIMP) to SAP S/4HANA.
Page | 785
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECCDIMP) for managing supplier stock at External Service Providers (ESP) is not available
in SAP S/4HANA.
The solution had been addressed to companies purchasing direct material from vendors
who put the products to stock at an ESP for replenishment to the customer. The stock at
the ESP is still owned by the vendor until the supply to the customer who requests a just
in time replenishment directly from the ESP to the production.
An EDI message with type STOACT allowed the transmission of the current vendor
stock for each product in inventory at the ESP; the inbound processing compared that
stock information with the current vendor consignment stock at a defined storage location
assigned to the ESP and posted the differences. It was recommended to exclude the ESP
storage location from MRP to not consider the vendor's stock into account when planning
and creating delivery schedules. For evaluation reasons, the vendor consignment stock at
ESP storage locations could be included when defining selection rules for the
stock/requirements list.
Business Process related information
The automotive solution for managing supplier stock at external service providers (ESP)
had a very low adoption rate and is not available in SAP S/4HANA.
Managing vendor consignment stock in general is available in SAP S/4HANA and stock
at storage locations could be separated in MRP by defining specific storage location MRP
areas.
Transactions not available in SAP S/4HANA OESP, ESPLOG, ESPLOGD
How to Determine Relevancy
The Simplification Item is relevant, if:
•
•
Plant and storage location parameters for ESP processing have been maintained
(check for entries in tables ESPPL and ESPST with transaction SE16), and
EDI messages of message type STOACT have been processed (check for entries
with MESTYP = 'STOACT' in table EDIDC with transaction SE16)
Page | 786
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
45.6 S4TWL - 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 (ECCDIMP) to SAP S/4HANA.
Solution
Page | 787
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
The automotive industry solution for cross-system transit between two plants addressed
the need to manage stock in transit between different plants of a company operating in
different SAP ERP systems. The goods issue posting at the supplying plant resulted in a
goods movement posting to the stock in transit of the receiving plant using a remote
function call in the target system. The goods in transit are then managed and valuated
automatically by the receiving plant. A goods receipt in the receiving plant then resulted
in a transfer posting from the stock in transit to a storage location stock. The automotive
industry solution focused especially on the usage of scheduling agreements for
procurement between the plants.
That solution had a very low adoption rate and is not available in SAP S/4HANA.
Business Process related information
The automotive industry solution for managing stock in transit for goods transferred
between two plants of a company operating in different systems is not available in SAP
S/4HANA.
Transactions not available in S/4HANA XLOC, XLOR, XLOS
How to Determine Relevancy
The Simplification Item is relevant, if:
•
•
•
Purchasing documents exist with document types maintained for crosssystem 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.
Page | 788
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Custom Code Check
SAP Note 2349033
SAP Note 2228220
Other Terms
Automotive, ECC-DIMP, S/4HANA, XLO, stock in transit
45.7 S4TWL - 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 (ECCDIMP) to SAP S/4HANA.
Prerequisite: Target release is SAP S/4HANA 1610 or subsequent.
Solution
Description
Page | 789
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
In SAP ERP, the automotive industry solution for the long material number did not
extend the material number used as key and reference field in database tables. Instead it
provided an additional extended representation of the material number up to 40 characters
and a conversion from the 18 characters internal representation to the external
representation and vice versa. The external representation has been entered and displayed
on user interfaces and has been added to technical interfaces like BAPIs and IDOCs. The
solution is activated with business function MGV_LAMA. It had restrictions and with its
necessary conversions between an internal and external representation, it is suboptimal
from a performance perspective.
In SAP S/4HANA, the material number is natively extended to 40 characters, therefore
the automotive industry solution for the long material number is obsolete and will not be
supported.
For more information on the material number field length extension in SAP S/4HANA,
see SAP Note 2267140.
A conversion to SAP S/4HANA 1511 is not supported; In SAP S/4HANA 1511, the
business function MGV_LAMA is set to "Always off".
Business Process related information
The industry solution for long material numbers has been replaced by a natively extended
material number, clearly beneficial with regards to simplification, performance and
integration.
The industry solution for long material numbers and its replacement by an extended
material number requires a database conversion replacing the internal representation of
the material number by the external representation. Not in all cases it will be an identical
exchange and not in all cases an exchange might be supported.
Interfaces like BAPIs, IDocs or Webservices had been extended by the industry solution
for long material numbers, and they had been extended additionally for the natively
extended material number. The interfaces might not provide the material numbers in
exactly the same way before and after the conversion. A compatability mode is provided
to support the interface extensions of the industry solution for long material numbers.
For more details on conversion to S/4HANA with respect to long material numbers, refer
to SAP Note 2360860.
How to Determine Relevancy
The Simplification Item is relevant, if:
Page | 790
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
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.
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
45.8 S4TWL - Material Version
Application Components:
IS-A-LMN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270398
S4TWL - Material Version
Page | 791
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 (ECCDIMP) 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
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.
Page | 792
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Except for the master data maintenance, the only application specifically handling
material versions is the BOM explosion from iPPE (Integrated Product and Process
Engineering). An iPPE could be maintained just using header materials as components,
so new material versions do not require the maintenance of iPPE objects. During BOM
explosion, a valid material version with active logistics switch is dynamically determined
and the header material replaced by its version if found. The validity for material versions
is determined via ECM (Engineering Change Management) which is obligatory for
material versions to be used. All other applications do not distinguish between header
material and material versions.
A conversion to SAP S/4HANA 1511 is not supported; In SAP S/4HANA 1511, the
business function MGV_LAMA is set to "Always off".
Business Process related information
The automotive industry solution for material versions is not available with SAP
S/4HANA.
Material versions as material master referring to a header material with version ID and
version type could not be maintained. Instead, material versions could be maintained as
other materials with a material number combining the header material number and the
version ID. Version type specific material master maintenance, logistics switch and
material version determination during iPPE explosion according to the validity defined in
ECM is not supported.
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)
Page | 793
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
A conversion of material versions is not supported by the standard conversion tools for
long material numbers. Create an incident on application component IS-A-LMN with
short text "S4HANA conversion for material versions required" to get support in
converting material versions to normal material numbers in SAP S/4HANA.
Related SAP Notes
Pre-Check
Custom Code Check
SAP Note 2326776
SAP Note 2228242
Other Terms
Automotive, ECC-DIMP, S/4HANA, Material version, LMN, LAMA
45.9 S4TWL - 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 (ECCDIMP) 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.
Page | 794
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Regular routes like milk-run tours lead to recurrent shipments. Route schedules could be
defined as basis for generating these recurrent inbound shipments. Inbound deliveries
created based on shipping notifications from suppliers could be directly linked as items to
the generated inbound shipments. The inbound shipments could then be used for goods
receipt processing collectively for all inbound deliveries shipped together.
Planning regular route shipments has a low customer adoption and is not available in
SAP S/4HANA.
With SAP Transportation Management, a new solution for planning, executing and
settling shipments is available.
Business Process related information
In SAP S/4HANA, the automotive industry solution for maintaining schedules for regular
routes and planning and creating inbound shipments based on route schedules is not
available.
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.
Page | 795
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related SAP Notes
Custom Code Check
SAP Note 2227568
Other Terms
Automotive, ECC-DIMP, S/4HANA, Transportation, Regular Routes
45.10 S4TWL - 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
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 (ECCDIMP) to SAP S/4HANA.
Solution
Description
The automotive industry solution in SAP ERP Discrete Industries & Mill Products (ECCDIMP) 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.
Page | 796
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
•
•
•
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
Page | 797
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
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.
Related SAP Notes
Custom Code Check
SAP Note 2228244
Other Terms
Automotive, ECC-DIMP, S4HANA, DP, DIWI
45.11 S4TWL - 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 (ECCDIMP) to SAP S/4HANA.
Solution
Page | 798
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
Page | 799
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
46 Industry DIMP - EC&O
46.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 (ECCDIMP) 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
Page | 800
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
46.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-Strategicfunction.
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.
The transactions BOSPS01 - Online Processing, BOSPS02 - Batch Processing
and BOSPS_REV1 - BOS/Project Plan/Actual Revenue are not available
Page | 801
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
46.3 S4TWL - Business Partner Tax Classification BUT_FRG0011 is
deactivatedS4TWL - 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
/SAPCEM/BGL91 have no equivalent objects or reports available till SAP S/4HANA
1610 FPS1.
Page | 802
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Test script is replaced by the Function
ERP release
Module in S/4HANA 1610 FPS1
J_3GBU1022 /SAPCEM/AS01
BAPI_FIXEDASSET_CREATE
Report Name
J_3GBU1022 /SAPCEM/AS02
J_3GRAWFOB01
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
Page | 803
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
46.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 (ECCDIMP) 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.
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 NonStrategic-function
Required and Recommended Action(s)
Please consider to convert the ETM recipient related customer master records to business
partner records. Refer to the SAP Note 2265093. Ensure that you perform the following
pre-requisite steps during conversion of ECC DIMP ETM recipient to Business partner :
1. Perform additional Customizing for ETM recipient:
Page | 804
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
46.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
Page | 805
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 (ECCDIMP) 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
46.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
Page | 806
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
46.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 (ECCDIMP) to SAP S/4HANA
Solution
Description
Page | 807
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
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
Page | 808
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
47 Industry DIMP - High Tech
47.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
/SAPHT/MESCL30 - Batch Characteristic Search
/SAPHT/MESZMLG - Batch Genealogy
Transactions not available
in SAP S/4HANA
/SAPHT/MESZPRM - Formula parameter dynamic
generation
/SAPHT/SPCZQ02 - QM: SPC Review Control Chart
Page | 809
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
47.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
/SAPHT/RN_DUNS - RosettaNet Building Block: DUNS
implementation
/SAPHT/RN_GTIN1 - RosettaNet Building Block: GTIN
Business Add-Ins not
implementation
available in SAP S/4HANA /SAPHT/RN_USER_DUNS - RosettaNet Building Block:
DUNS implementation - User exit
/SAPHT/RN_USER_GTIN - RosettaNet Building
Block: GTIN implementation - User exit
47.3 S4TWL - Software License Management
Application Components:
IS-HT-SW-LIC
Page | 810
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 VBSY – Billing Plan Synchronization
in SAP S/4HANA
47.4 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
Page | 811
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
47.5 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
Page | 812
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
47.6 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).
Page | 813
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 OK32 - SMP Order Due List
in SAP S/4HANA
OK30 - Software Maintenance Process
OK36 - SMP Log
47.7 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.
Page | 814
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
“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.
47.8 S4TWL - Condition Technique in DRM: Rule Configuration
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.
Page | 815
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
“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.
47.9 S4TWL - 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.
Page | 816
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
“Manufacturer/Supplier Processes” provided the core capabilities for High Tech
Manufacturers.
Within SAP Business Suite, DRM had been superseded by the SAP CRM Channel
Management for High Tech solution.
DRM and thus “Manufacturer/Supplier Processes” have not been brought into SAP
S/4HANA, nor has SAP Channel Management for High Tech been brought into SAP
S/4HANA.
Thus, there is no specific, targeted successor solution in SAP S/4HANA for these
capabilities.
Business Process related information
Transactions not DRMPPMS_C - Price Protection (Create Due List)
available in SAP
S/4HANA
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
Page | 817
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
47.10 S4TWL - 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
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.
Page | 818
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
Transactions not /SAPHT/DRMPPDR_C - Price Protection (Create Due List)
available in SAP
S/4HANA
/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
/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
Page | 819
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
48 Industry DIMP - High Tec
48.1 S4TWL - Installed Base Management
Application Components:
IS-HT-SW-IB
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270849
S4TWL - Installed Base 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
Installed Base Management was part of the IS-SW industry solution.
It used the SAP Installed Base (IBASE) database to manage software licenses, with
capabilities including: business data inheritance, license bump processing, IBASE record
splits.
IS-SW and thus Installed Base Management capabilities have not been brought in to SAP
S/4HANA.
There is no specific, targeted successor solution in SAP S/4HANA for these capabilities.
Business Process related information
Transaction not available PASW - Partner Inheritance Switch
in SAP S/4HANA
Page | 820
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
49 Industry Media
49.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.
Page | 821
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
SAP Media, Media Product Master
49.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.
The assignment of business partners to Media Product Masters is not supported in
SAP S/4HANA.
Page | 822
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Page | 823
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
50 Industry DIMP – Mill
50.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 to SAP S/4HANA, on-premise edition. The following
SAP S/4HANA Transition Worklist item is applicable in this case.
Solution
Description
Non Ferrous Metal Processing functionality enables to consider fluctuating metal prices
in area of Sales and Purchasing pricing. In SAP ERP, the functionality is part of Industry
Solution Mill Products. In parallel in SAP ERP the new Solution SAP Commodity
Management is available.
SAP Commodity Management is for SAP the strategic solution with new innovations.
Since SAP S/4HANA, on-premise edition 1511, the NFM functionality is available, but
defined as "not strategic any more". See SAP note 2269324 - Compatibility Scope Matrix
for SAP S/4HANA, on-premise edition. The NFM solution is defined as Compatibility
Pack, end of usage rights 31.12.2025. In SAP S/4HANA 1709, the SAP Commodity
Management sales/purchasing is available and can replace the Non Ferrous Metals
(NFM) functionality.
Business Process related information
In SAP S/4HANA, on-premise edition 1511, Customer and Vendor master transactions
are combined into new Business Partner transaction "BP". The Non Ferrous Metals
(NFM) field “Exchange key” is not shown in transaction "BP"; the user cannot add or
change the data.Technically in the DDIC tables LFM1 [ Vendor master record
purchasing organization data ] and KNVV [ Customer Master Sales Data ], field
/NFM/BOESL which represents NFM “Exchange Key“ is still available. Sales and
purchase orders get the default NFM “Exchange key” value from the these tables [ LFM1
Page | 824
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
and KNVV ] and the user can change it. If no default value exists, then the user needs
manually to add the missing NFM “Exchange Key“ in the sales and purchase orders.
Required and Recommended Action
No special actions for Non Ferrous Metal customers during transition from SAP ERP to
SAP S/4HANA, on-premise edition 1511 or higher.
Explain your end user, that in some cases the “Exchange key” value within the NFM
screen of Sales/ Purchase Order must be added manually.
Customers who need the edit/ change feature for the default NFM field “Exchange key”
in transaction “BP” have to do a project development.
How to Determine Relevancy
The simplification item is possibly relevant if in SAP ERP the Business Function
DIMP_SDUD (Discrete Indus. - Mill Products) is active in your system. You can check
its status via transaction SFW_BROWSER (Switch Framework Browser) under object
DIMP. Furthermore, the ‘NF Metal Activated’ indicator is set at Customizing step IMG ->
Logistics - General -> NF Metal Processing -> NF Cross-Application Components ->
Maintain Basic Settings for NF Metal Processing.
The simplification item is relevant if there are entries in table /NFM/TORDERPOS. You
can use transaction SE16 to verify.
Migration
SAP does not offer data migration tools. The majority transition work is in area
customizing.
License situation
There is a special license rule for SAP ERP customers using Non Ferrous Management
functionality in their productive system. Please contact your Account Manager to
consider the situation in your SAP ERP-> SAP S/4HANA contract conversion.
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
Mill Products
Page | 825
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
50.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
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
50.3 S4TWL - Stock Overview and Object Search by Characteristics
Page | 826
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
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
Page | 827
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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.
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
50.4 S4TWL - Mill specific enhancements to scheduling PRTs
Application Components:
IS-MP-PP
Related Notes:
Page | 828
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
•
•
/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
Page | 829
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Custom Code related information
SAP Note: 2226674
50.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
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
Page | 830
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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).
50.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
Page | 831
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Display’ and ‘Define Characteristics Display for Overview Screen’ under IMG “Logistics –
General->Global Trade Management->Trading contract->Fast Entry of Characteristics”.
50.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
Page | 832
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
The simplification item is relevant if you are using the mill specific transaction
/SAPMP/PP_COHV.
50.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
Page | 833
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
Page | 834
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
51 Industry Oil
51.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 (ACCGO 100, ACCGO 300) to SAP S/4 HANA
on-Premise edition 1709 FP00. 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 fromSAP 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 - ACCGO 100, ACCGO 300) 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. This might be
relevant for customer specific coding.
Required and Recommended Action(s): Adjust customer specific coding accordingly.
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
Page | 835
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
IS-OIL, ACM, Agricultural Contract Management, upgrade, S/4HANA OnPrem 1709
FP00, system conversion
51.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
IS-OIL, ACM, Agricultural Contract Management, upgrade, S/4HANA OnPrem 1709
FP00, system conversion
51.3 S4TWL - ACM: Simplification of Cross Topics
Application Components:
LO-AGR
Related Notes:
Page | 836
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
51.4 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.
Page | 837
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
Obsolete Transaction Older Transaction Code
code
O300
IS-Oil Administration info
system
O3C1
Create Oil Conversion Defaults
O3C2
Change Oil Conversion Defaults
O4KC
Revaluation active check report
2/2
O4KE
Excise Duty Valuation
record 2/3
O4KG
Excise Duty Stock values 2/3
O4KH
Excise Duty Stock values 3/3
O4KI
Excise Duty Valuation
record 3/3
O4NC
Create Nomination
Successor Tcode
SE43
O3DEFAULTS
O3DEFAULTS
No Replacement available
No Replacement available
No Replacement available
No Replacement available
No Replacement available
O4NCN/O4NM
Page | 838
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
O4NS
O4NV
O4T0
O4TC
O4TCB
O4TDL
O4TE
O4TE_CORRECT
O4TE_REVERSE
O4TF
O4TG
O4TH
O4TO
O4TW
O4TX
O4TY
O547
O548
Display Nomination
O4NSN/O4NM
Change Nomination
O4NM
IS-OIL TSW (Trader's &
No Replacement available
Scheduler's W
Generate Stock Projection
O4TCN
Generate Stock Projection for
O4TCN
batch
OIL-TSW Delete Location
O402N
OIL-TSW: Enter movement
O4TE
ticket
OIL-TSW: Correct ticket
O4TENCORR
actualization
OIL-TSW: Reverse ticket
O4TENREV
actualization
OIL-TSW: Change ticket
O4TFN
OIL-TSW: Display Ticket
O4TGN
OIL-TSW: Delete movement
O4THN
ticket
Work list
O4TO_LIST
OIL-TSW Create Location
O401
OIL-TSW Change Location
O402
OIL-TSW Display Location
O403
Reconciliation OIA07
No Replacement available
Reconcile Movb. Netting balance No Replacement available
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Other Terms
S/4HANA, SFIN and IS-OIL & GAS
51.5 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
Page | 839
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
case of STO) followed by 101 movement for the same outbound delivery at the time of
load confirmation
Software Components
IS-OIL
Page | 840
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Languages
English
How to Determine Relevancy
This item is relevant for all IS-Oil customer
51.6 S4TWL - Extended IS-OIL Data Aging for SD/MM Objects
Application Components:
IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2534445
S4TWL IS-OIL Data Aging extensions of
SD & MM objects 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
The data volume in the tables of IS-OIL dependent tables is high and growing fast. You
would like to have some portion of the data available in the database (i.e. you cannot
delete or archive it), but at the same time you don't want all the data occupying the
working memory.
To cover these requirements, you would like to use the data aging functionality.
There are several oil tables that are part of the MM and SD data aging objects namely,
MM_MATDOC, MM_EKKO, SD_VBAK, SD_VBRK and LE_LIKP.
Page | 841
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Data Aging extensions of IS-OIL for following MM and SD data aging objects namely,
MM_MATDOC, MM_EKKO, SD_VBAK, SD_VBRK and LE_LIKP are available with
S/4HANA On Premise release 1709.
Data aging related details can be found in SAP Note 2315141 (Collective Note for Data
Aging Framework).
Solution
In addition to the configurations of following data aging objects; MM_MATDOC,
MM_EKKO, SD_VBAK, SD_VBRK and LE_LIKP (you can find the details in the note
2315141), to use IS-OIL data aging extensions you should do the followings;
To use MM_MATDOC extensions:
1. Create partitions for historical area in MATDOCOIL table. This is done via
partitioning object MM_MATDOCOIL
To use MM_EKKO extensions:
1. Create partitions for historical area in oil tables like OIA06, OIA06H and OIAFE.
This is done through partitioning object MM_EKKO_IS_OIL
2. Create partitions for historical area in oil tables like OIAF7, OIAF8, OIAF9, and
OIANF. This is done through partitioning object OIA_COMMON
3. Create partitions for historical area in oil tables like OICQ7, OICQ8, and OICQ9.
This is done through partitioning object OICQ_COMMON
4. Create partitions for historical area in oil tables like OIJ_EL_CP_LAYT,
OIJ_EL_CP_LOC, OIJ_EL_DOC_EV, OIJ_EL_DOC_I_REF,
OIJ_EL_DOC_MOT, OIJ_EL_DOC_M_MOT, OIJ_EL_LAYT_EV,
OIJ_EL_LAYT_INF and OIJ_EL_CP_PROD. This is done through partitioning
object OIJ_EL_COMMON
To use SD_VBAK extensions:
1. Create partitions for historical area in oil tables like OIA05, OIA05H,
OICINT_MASTER, OIK01, OIK01D and OIKLIDR. This is done through
partitioning object SD_VBAK_IS_OIL
2. Create partitions for historical area in oil tables like OIAF7, OIAF8, OIAF9, and
OIANF. This is done through partitioning object OIA_COMMON
3. Create partitions for historical area in oil tables like OICQ7, OICQ8, and OICQ9.
This is done through partitioning object OICQ_COMMON
4. Create partitions for historical area in oil tables like OIJ_EL_CP_LAYT,
OIJ_EL_CP_LOC, OIJ_EL_DOC_EV, OIJ_EL_DOC_I_REF,
OIJ_EL_DOC_MOT, OIJ_EL_DOC_M_MOT, OIJ_EL_LAYT_EV,
Page | 842
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
OIJ_EL_LAYT_INF and OIJ_EL_CP_PROD. This is done through partitioning
object OIJ_EL_COMMON
To use SD_VBRK extensions:
1. Create partitions for historical area in oil tables like OIC_KONV and
OIC_OIANF. This is done through partitioning object SD_VBAK_IS_OIL
2. Create partitions for historical area in oil tables like OIAF7, OIAF8, OIAF9, and
OIANF. This is done through partitioning object OIA_COMMON
3. Create partitions for historical area in oil tables like OICQ7, OICQ8, and OICQ9.
This is done through partitioning object OICQ_COMMON
To use LE_LIKP extensions:
1. Create partitions for historical area in oil tables like LIPSO1, LIPSO2, OIA11,
TVPODO1 and TVPODO2. This is done through partitioning object
SD_LIKP_IS_OIL
Create partitions for historical area in oil tables like OIAF7, OIAF8, OIAF9, and OIANF.
This is done through partitioning object OIA_COMMON
Other Terms
Data Aging, MM_MATDOC, MM_EKKO, SD_VBAK, SD_VBRK, LE_LIKP, Data
Aging Extensions, IS-OIL, IS-OIL-DS, IS-OIL Data Aging Extensions, current area,
historical area, current data, historical data
51.7 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 onpremise edition 1610. The following SAP S/4HANA Transition Worklist item is
applicable in this case.
Solution
Page | 843
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
The SAP ERP 6.0 stock inventory management data model consists of the two document
tables MKPF for document header information and MSEG for document item data. In
addition Oil & Gas has MSEGO1 for quantity conversion parameters for material
documents and MSEGO2 Material Document Quantities in Additional Units of Measure.
Additionally there were aggregated actual stock quantity data stored in several tables.
Some of these tables do also store material master data attributes like the tables
MARCO1, MARDO1, MCHBO1, MKOLO1, MSLBO1, MSKAO1, MSKUO1 &
MSPRO1. Such tables with material master data attributes as well as actual stock
quantities will be named as hybrid tables in the following. There were also tables like
MARCHO1, MARDHO1, MCHABO1, MKOLHO1, MSLBHO1, MSKAHO1,
MSKUHO1 & MSPRHO1 which holds periodical history data.
With SAP S/4HANA 1610, this data model has changed significantly. The new denormalized 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
MBEW
Table
Description
Core CDS View
DDL Source of CDS
View for redirect
Material
Valuation
OIH_OILEMBEW7_M
BEW_EXT_DDL
MBV_MBEW_EXT
CWM_MBEW_EXT_
DDL
OIH_OILEMBEW7_M
MBV_MBEW_ML_ BEW_ML_DDL
ONLY
CWM_MBEW_ML_D
DL
OIH_OILEMBEW7_M
MBV_MBEW_BASI BEW_BASIS_DDL
S
CWM_MBEW_BASIS
_DDL
OIH_OILEMBEW7_M
MBV_MBEW_CASE
BEW_CASE_DDL
View to read the
content of the
View to read the
database table
master data
(w/o redirect to
attributes only
compatibility
view)
Page | 844
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
CWM_MBEW_CASE_
DDL
OIH_OILEMBEW7_M
MBV_MBEW_MOT BEW_MOTH_DDL
H_SEG
CWM_MBEW_MOTH
_SEG_DDL
OIH_OILEMBEW7_M
BEW_DDL
MBV_MBEW
CWM_MBEW_DDL
OIH_OILEMBEW7_E
MBV_EBEW_EXT
BEW_EXT_DDL
MBV_EBEW_ML_O OIH_OILEMBEW7_E
NLY
BEW_ML_DDL
OIH_OILEMBEW7_E
MBV_EBEW_BASIS
BEW_BASIS_DDL
OIH_OILEMBEW7_E
MBV_EBEW_CASE
BEW_CASE_DDL
OIH_OILEMBEW7_E
MBV_EBEW
BEW_DDL
OIH_OILEMBEW7_Q
MBV_QBEW_EXT
BEW_EXT_DDL
MBV_QBEW_ML_O OIH_OILEMBEW7_Q
NLY
BEW_ML_DDL
OIH_OILEMBEW7_Q
MBV_QBEW_BASIS
BEW_BASIS_DDL
OIH_OILEMBEW7_Q
MBV_QBEW_CASE
BEW_CASE_DDL
OIH_OILEMBEW7_Q
MBV_QBEW
BEW_DDL
OIH_OILEMBEW7_O
MBV_OBEW_EXT
BEW_EXT_DDL
MBV_OBEW_ML_O OIH_OILEMBEW7_O
NLY
BEW_ML_DDL
OIH_OILEMBEW7_O
MBV_OBEW_BASIS
BEW_BASIS_DDL
OIH_OILEMBEW7_O
MBV_OBEW_CASE
BEW_CASE_DDL
OIH_OILEMBEW7_O
MBV_OBEW
BEW_DDL
CWM_MARC_COSTI
NG
NSDM_DDL_MARC
OI0_COMMON_2_OI
LMARC_DDL
EBEW
Sales Order
Stock
Valuation
QBEW
Project Stock
Valuation
OBEW
Valuated
Stock with
Subcontracto
r
MARC
Plant Data
for Material
MKPF
Header:
Material
Document
NSDM_DDL_MKPF
MSEG
Document
Segment:
Material
CWM_MSEG_DDL
OI0_COMMON_2_OI
NSDM_DDL_MSEG LMSEG_DDL
OIO_OIOMSEG_DDL
OI0_COMMON_2_OI
LMKPF_DDL
Page | 845
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Material
Master: DB
MA07V View for
NSDM_E_MA07V
Inventory
Management
Sales Index:
VAPMA Order Items V_VAPMA
by Material
Appendix for
MARCO Additional
Quantities at
1
Plant Level
Appendix for
Storage
MARDO
Location
1
Additional
Quantities
Appendix for
MCHBO Additional
Quantities at
1
Batch Level
Special
stocks from
MKOLO vendor
additional
1
quantity
appendix
Appendix for
Special
Stocks with
MSLBO1
Vendors:
Add.
Quantities
Special
Stocks
MSKAO
Appendix:
1
Additional
Quantities
Appendix for
Special
MSKUO Stocks with
Customers:
1
Add.
Quantities
Project Stock
MSPRO1 additional
quantities
MARCH:
MARCH Additional
quantities
O1
appendix
MARDH MARDH:
O1
Aditional
OI0_COMMON_OILV
AP_MA07V_DDL
OIF_OILVAPMA_DD
L
OIB_DDL_MARCO1
V_OIB_MG_M
V_MARCO1_MD
ARCO1
OIB_DDL_MARDO1
V_OIB_MG_M
V_MARDO1_MD
ARDO1
OIB_DDL_MCHBO1
V_OIB_MG_M
V_MCHBO1_MD
CHBO1
OIB_DDL_MKOLO1
V_OIB_MG_M
V_MKOLO1_MD
KOLO1
OIB_DDL_MSLBO1
V_OIB_MG_M
V_MSLBO1_MD
SLBO1
OIB_DDL_MSKAO1
V_OIB_MG_M
V_MSKAO1_MD
SKAO1
OIB_DDL_MSKUO1
V_OIB_MG_M
V_MSKUO1_MD
SKUO1
OIB_DDL_MSPRO1
V_OIB_MG_M
V_MSPRO1_MD
SPRO1
OIB_DDL_MARCHO1
V_OIB_MG_M
ARCHO1
OIB_DDL_MARDHO1
V_OIB_MG_M
ARDHO1
Page | 846
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
quantities
appendix
Appendix for
MCHBH Additional
Quantities at
O1
Batch Level
MKOLH:
MKOLH Additional
quantities
O1
appendix
MSLB:
MSLBH Additional
quantities
O1
appendix
MSKAH:
MSKAH Additional
quantities
O1
appendix
MSKUH:
MSKUH Additional
quantities
O1
appendix
MSPRH: Ad
MSPRH ditional
quantities
O1
appendix
Quantity
Conversion
MSEGO1 Parameters
for Material
Documents
Material
Document
Quantities in
MSEGO2
Additional
Units of
Measure
OIB_DDL_MCHBHO1
V_OIB_MG_M
CHBHO1
OIB_DDL_MKOLHO1
V_OIB_MG_M
KOLHO1
OIB_DDL_MSLBHO1
V_OIB_MG_M
SLBHO1
OIB_DDL_MSKAHO1
V_OIB_MG_M
SKAHO1
OIB_DDL_MSKUHO1
V_OIB_MG_M
SKUHO1
OIB_DDL_MSPRHO1
V_OIB_MG_M
SPRHO1
OIB_DDL_MSEGO1
V_OIB_MG_M
SEGO1
OIB_DDL_MSEGO2
V_OIB_MG_M
SEGO2
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
Page | 847
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Material Stock condensate table MATDOCOILEXTRACT
MATDOCOILEXTRACT is the condensed table of MATDOCOIL which contains
technical key fields to optimize memory consumption, stock identifier fields, period
fields and additional quantity fields.
Records will be inserted in this condensate table MATDOCOILEXTRACT at the same
time as records are inserted in the material document table MATDOCOIL.
The Pre-compacting functionality
•
•
•
•
Running at the period end closing
Can be scheduled as periodic job
Creates a condensate from all records having the same values in its stock
identifying fields
Inserts this condensate as new record and deletes all records contributing to this
condensate. Hence the actual stock needs to be calculated only from this
condensate and all document records created since the last Pre-Compacting run.
Thus, the overall number of records in the condensate table is much less than in
the material document table as well as the number of records to be aggregated onthe-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.
Page | 848
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Flexible framework for UoM extension after 60 UoM
According to SAP S4 HANA redesign in HPM, the system supports up to 60 unique
UoMs. Once the UoM count exceeds 60, the user will not be able to post material
documents with new UoM. To overcome this problem a flexible framework is provided
to customers.
As per the framework when the UoM count reached to warning limit (total UoM fileds –
5 UoM fields i.e. 60-5 = 55), an information message will be popped up in MIGO process
stating UoM count has reached XX number, to retain smooth operation implement SAP
note 2293641.
Data Archiving in S/4HANA for HPM (MATDOCOIL)
With SAP S/4HANA the database design for material documents was changed from the
old tables MKPF and MSEG to the new table MATDOC and in IS-OIL from MSEGO1
and MSEGO2 to MATDOCOIL. For the tables MKPF, MSEG, MSEGO1 and MSEGO2
an archiving function is in place through the archiving object MM_MATBEL. The
existing implementation of the archiving object MM_MATBEL shall be changed in a
way that it works with the new table while existing settings for this archiving object are
still valid and data which has already been archived in the customer environment is still
accessible.
When material documents are moved from the DB into archive files it must be ensured
that the calculation of the current stock level, as well as of historical stock levels is still
working accurately. As the stock level is calculated on the basis of all stock movements
for a particular stock identifier, this means that the archiving of material documents goes
together with the creation of representatives for the archived entities.
It must be ensured that the aging and deletion of archived material documents does not
happen in parallel. For this purpose a new lock object EMATDOC_AGING with client
(MANDT) as lock parameter is introduced. When starting data aging for aging object
MM_MATDOC in the aging runtime an exclusive lock shall be raised, while the delete
program for material documents shall raise a shared lock for the same client.
A new program NSDM_MM_MATBEL_POST_PROCESSING (package
MBND_ARCHIVING) is provided to consolidate the archive representatives (i.e. records
of type ARC_DELTA) that were created by report RM07MADES.Consolidation means
that the key figures of all representatives having the same aggregation key are aggregated
into a single new representative and inserted into the table MATDOC and
MATDOCOIL, while the representatives forming this new representative are deleted
from the table MATDOC and MATDOCOIL.
It must be ensured that the aging and consolidation of archive representatives does not
happen in parallel. For this purpose, the same lock object is used that is already applied to
protect the aging and deletion of material documents (i.e. lock object
EMATDOC_AGING). But as compared to the delete program, where a shared lock is
Page | 849
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
used to enable the parallel execution of the delete process, the post processing program
shall raise an exclusive lock. By using an exclusive lock it is ensured that the post
processing program is called only once at a time (i.e. it must not run parallel).
Old BAdI implementation for Oil and Gas (OI0_MM_MATBEL_WRITE) is 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
51.8 S4TWL - Data Aging for IS-OIL Objects
Application Components:
IS-OIL-DS
Related Notes:
Page | 850
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Note Type
Note Number
Note Description
Business Impact
2476582
S4WTL IS-OIL Data Aging 1709
Release Restriction
2315141
Collective note for Data Aging Framework
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
The data volume in the tables of IS-OIL Nominations, Ticketing and Exchnages are high
and growing fast. You would like to have some portion of the data available in the
database (i.e. you cannot delete or archive it), but at the same time you don't want all the
data occupying the working memory.
To cover these requirements, you would like to use the data aging functionality.
Solution
Data Aging for Nominations, Ticketing and Exchanges are available with S/4HANA onpremise edition 1709.
Further details can be found in SAP Note 2315141 (Collective Note for Data Aging
Framework).
To use data aging for nominations you must do the following:
1. Create partitions for historical area in nominations table. This is done through
partitioning object OIJ_NOMIN.
2. Activate data aging object OIJ_NOMIN.
3. Configure residence times for nominations in current area. Relevant for the
residence time determination is the change date of an exchange agreement.
Page | 851
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
With SAP S/4HANA on-premise edition 1709 the residence time configuration for nominations can
be found in SAP Customizing (transaction SPRO: Industry Solution Oil & Gas (Downstream)->TSW
(Trader’s and Scheduler’s Workbench)->Data Aging->Nominations). Residence times can be defined
per transport system.
If no residence time is maintained (or if no residence time configuration is available) the
system assumes a default residence time of two years. For further details see the
documentation of the Customizing activity.
By running report OIJ_NOMI_DAAG_ANALYSIS you can execute an analysis run to
check how many nominations would be affected by the given residence time
configuration.
Schedule a data aging job for data aging group OIJ_NOMIN.
When an exchange agreement is selected for aging, either all items or none of the items
are moved to the historical area. There is no partial aging of an exchange agreement.
The access to aged nominations is still possible, for example , through the display
functions for nominations (such as the Nomination - Display Fiori App or transaction
O4NSN).
In custom code, when selecting exchanges from table OIJNOMH, class
CL_OIJ_DAAG_COLD_ACCESS can be used to decide whether access to historical
area shall be activated beforehand. For an ABAP session method SET_COLD sets the
temperature to cold.
Enhancement spot ES_DAAG_OIJ_NOMI is provided for customer-specific veto checks
when performing data aging for exchanges (with SAP S/4HANA on-premise edition
1709 see SAP customizing, transaction SPRO: Industry Solution Oil & Gas
(Downstream)->TSW (Trader’s and Scheduler’s Workbench)->Data Aging>Nominations->BAdI: Aging of Nominations).
To use data aging for Ticketing you must do the following:
1. Create partitions for historical area in Ticketing table. This is done through
partitioning object OIJ_TICKET.
2. Activate data aging object OIJ_TICKET.
3. Configure residence times for Ticketing in current area. Relevant for the residence
time determination is the change date of an exchange agreement.
With S/4HANA On Premise release 1709 the residence time configuration for
Ticketing can be found in SAP Customizing (transaction SPRO: Industry Solution
Oil & Gas (Downstream)->TSW (Trader’s and Scheduler’s Workbench)->Data
Aging->Ticketing). Residence times can be defined per transport system.
If no residence time is maintained (or if no residence time configuration is available) the
Page | 852
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
system assumes a default residence time of two years. For further details see the
documentation of the IMG activity.
By running report OIJ_TICKT_DAAG_ANALYSIS you can execute an analysis run to
check how many Ticketing would be affected by the given residence time configuration.
1. Schedule a data aging job for data aging group OIJ_TICKET.
When an exchange agreement is selected for aging, either all items or none of the
items are moved to the historical area. There is no partial aging of an exchange
agreement.
The access to aged Ticketing is still possible, for example, through the display
functions for Ticketing (such as the Ticketing - Display Fiori App or transaction
O4TGN).
In custom code, when selecting exchanges from table OIJ_EL_TICKET_H, class
CL_OIJ_DAAG_COLD_ACCESS can be used to decide whether access to historical
area shall be activated beforehand. For an ABAP session method SET_COLD sets the
temperature to cold.
Enhancement spot ES_DAAG_OIJ_TICKET is provided for customer-specific veto
checks when performing data aging for exchanges (with SAP S/4HANA on-premise
edition 1709 see SAP customizing, transaction SPRO: Industry Solution Oil & Gas
(Downstream)->TSW (Trader’s and Scheduler’s Workbench)->Data Aging->Ticketing>BAdI: Aging of Ticketing).
To use data aging for exchanges you must do the following:
1. Create partitions for historical area in exchanges table. This is done through
partitioning object OIA_EXG.
2. Activate data aging object OIA_EXG.
3. Configure residence times for exchanges in current area. Relevant for the
residence time determination is the change date of an exchange agreement.
With S/4HANA On Premise release 1709 the residence time configuration for
exchanges can be found in SAP customizing (transaction SPRO: Industry
Solution Oil & Gas (Downstream)->EXG (Exchanges)->Data Aging>Exchanges). Residence times can be defined per exchange partner.
If no residence time is maintained (or if no residence time configuration is available) the
system assumes a default residence time of two years. For further details see the
documentation of the IMG activity.
By running report OIA_EXG_DAAG_ANALYSIS you can execute an analysis run to
check how many exchanges would be affected by the given residence time configuration.
Page | 853
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Schedule a data aging job for data aging group OIA_EXG.
When an exchange agreement is selected for aging, either all items or none of the items
are moved to the historical area. There is no partial aging of an exchange agreement.
The access to aged exchanges is still possible, for example, through the display functions
for exchanges (such as the Display Exchange Agreement Contract Assignments Fiori
App or transaction O3A3).
In custom code, when selecting exchanges from table OIA01, class
CL_OIA_EXG_DAAG_COLD_ACCESS can be used to decide whether access to
historical area shall be activated beforehand. For an ABAP session method SET_COLD
sets the temperature to cold.
Enhancement spot ES_DAAG_OIA_EXG is provided for customer-specific veto checks
when performing data aging for exchanges (with SAP S/4HANA on-premise edition
1709 see SAP Customizing, transaction SPRO: Industry Solution Oil & Gas
(Downstream)->EXG (Exchanges)->Data Aging->Exchanges->BAdI: Aging of
Exchanges).
Note:
Exchanges object is responsible only for exchanges related tables. If you want to make
full use of the object you must perform aging for the MM and SD objects first to age the
underlying documents in an exchange agreement like Sales contracts, Purchase contracts,
and son on.
Other Terms
Data Aging, OIJ_NOMIN, IS-OIL, IS-OIL-DS, Nominations, OIJ, current area, historical
area, current data, historical data
51.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
Page | 854
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 onpremise edition, the Late Lock (TCURM-MBEQU = 2) and the Non-Exclusive
Locking Mode (TCURM-MB_LOCK_MODE = 3) are activated by default.
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 TCURMMBEQU = 2 and TCURM-MB_LOCK_MODE = 3)
Page | 855
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
(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)
51.10 S4TWL - UoM Group Extension Improvements
Application Components:
IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Release Restriction
2396065
Release Restriction
2328459
S4HANA IS-OIL : UoM Group
Enhancement Update authorization
Issue/OIB05 update failed
Unit of Measure (UoM) Group enhancement
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
Page | 856
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
51.11 S4TWL - 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
Page | 857
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
51.12 S4TWL - 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.
Page | 858
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
1.
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.
2. 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.
3. Two new BC Sets were created for IS-OIL in the Commodity Pricing Engine
configuration Tables
•
•
OI_DS_S4DEV_CPEV_CALCRULE(calculation rule configuration)
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.
51.13 S4TWL - 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
Page | 859
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
51.14 S4TWL – 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.
Page | 860
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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/4HANA on-premise
edition 1709. You face an error "LOG_TSW_ECC is not released for S/4HANA 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
iTSW is only released for ACM(Agriculture Contract Management) Customers and is not
supposed to be used in S/4 HANA 1709 for any other customer segment.
Other Terms
LOG_TSW_ECC; LOG_TSW_ECC_1; iTSW; ACM
51.15 S4TWL - 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.
Page | 861
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
51.16 S4TWL - IS-OIL Proper sign operation for ACDOCA
Application Components:
IS-OIL-DS
Page | 862
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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, onpremise edition 1610.
Nevertheless there might be constellations where a customer needs to be aware about. For
example:
•
Any FI Posting happened in the system Excise duty values come with sign
operation, Condition credit indicator ‘H’ with negative values posting can see
in ACDOCA
Overview
With SAP S/4HANA, on-premise edition 1610, posting proper sign operation adapted in
ACDOCA.
Posting any FI document with Credit Indicator ‘H’, negative sign values applied to
posting document and Debit indicator ‘S’ there is no sign-operation applied.
Posting proper sign to ACDOCA we implemented BADI
‘BADI_OIL_ACDOCA_POST_SIGN’ and with Implementing Class
‘CL_OIL_ACDOCA_POST_SIGN’.
Coding part done in above class using interface method
IF_BADI_FINS_ACDOC_POST_EV_INT~SUBST_ACDOCA_EXTENSION_FIELDS
.
Page | 863
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
51.17 S4TWL - Unit of Measure (UoM) Group enahncement
Application Components:
IS-OIL-DS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2328459
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.
Page | 864
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Page | 865
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
1. If a material is marked for deletion, program still creates summary record but
‘Material flag for deletion’ column is marked ‘x’ (as just FYI)
2. Negative stocks are also handled with QCI conversion to new UoM
3. If material in context has few material postings (GR & GI) and nett stock in base
UoM is 0, as the base UoM stock is zero, no summary record is created
4. Stock in Base UoM is negligible quantity (Ex: 0,001 KG) and newly added UoM
is biggest UoM (Ex: MBL), as conversion of 0,001 KG to MBL will lead to ~0
value, summary record with 0 quantity will be added and stock in MBL will be
shown as 0 in MMBE for newly added UoM (i.e. MBL)
5. If there are more than 1 O3DEFAULTS maintained for same
material/plant/storage location, most relevant record (active and valid on current
date) will be considered for QCI conversion to new UoM
6. There are some cases where material documents are created with a UoM (For Ex:
BBL) which is 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
1. Case1: If BBL was part of only few material documents, assuming net quantity in
BBL from existing material documents is 1 BBL, Summary record will be created
for BBL as 1 so that in MMBE after summary record is created, stock for BBL
will be shown as 2
2. Case2: If BBL was part of only few material documents, assuming net quantity in
BBL from existing material documents is 0 BBL, Summary record will be created
for BBL as 0 so that in MMBE after summary record is created, stock for BBL
will be shown as 2
3. Case3: If BBL was part of only few material documents, assuming net quantity in
BBL from existing material documents is -1 BBL, Summary record will be
Page | 866
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
created for BBL as 3 so that in MMBE after summary record is created, stock for
BBL will be shown as 2
Business Process related information.
New functionality available in SAP S4HANA 1610
How to Determine Relevancy
This item is relevant for all IS-Oil customer
51.18 S4TWL - 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 upgradation 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.
Page | 867
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
eNetting functionality was available till 4.6C version of ERP which is not available in
SAP S/4HANA 1610.
Required and Recommended Action:
There is no equivalent functionality of eNetting available in SAP S/4HANA 1610.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Other Terms
IS-OIL-DS-EXG, IS-OIL-NET, Exchanges, eNetting
51.19 S4TWL - 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.
Page | 868
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Solution
Description:
Dynamic scheduling application is an integration of Stock Projection Worksheet (SPW)
and Three-way pegging (3WP) functionality. Dynamic Scheduling integrates these two
applications so that when a user makes a data-change in one application, they can see the
effect of it in the other application in real-time (without requiring a data-save). This
allows the user to create simulations in 3-way pegging, see its effect on the inventory in
the Stock Projection, modify the simulations, undo/redo changes, and make changes to
already published nomination. Once satisfied, the user can save these changes to the
database. As SAP has come up with similar applications recently, it creates confusion to
customers with similar solutions and hence Dynamic Scheduling has been removed in
SAP S/4HANA 1610.
Business Process related information: Dynamic scheduling is an integration of SPW
and 3WP functionality which has been removed from SAP S/4HANA 1610.
Required and Recommended Action: There is no equivalent functionality of dynamic
scheduling available in SAP S/4HANA 1610, but advanced functionalities like Inventory
Planning Workbench (IPW) and Nomination Planning Workbench (NPW) are available.
How to Determine Relevancy
This item is relevant for all IS-Oil customer
Other Terms
IS-OIL-DS-TSW, TSW, Dynamic scheduling, Stock Projection Worksheet
(SPW), Three-way pegging (3WP)
51.20 S4TWL - 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
Page | 869
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
51.21 S4TWL - 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
Page | 870
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Report deprecated due to new data model.
Solution
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
MKPF
MSEG
MSEGO1
MSEGO2
Core Aggregate
tables (MARC...)
Data Storage as per
New Data Model
MATDOC
MATDOC
MATDOCOIL
MATDOCOIL
Aggregate Table +
MATDOC
Oil Aggregate tables
(MARCO1...)
Aggregate Table +
MATDOCOIL
Details
No data is stored in MKPF
No data is stored in MSEG
No data is stored in MSEGO1
No data is stored in MSEGO2
Master data is stored in
Aggregate table, the transactional
data is calculated on the fly from
MATDOC using redirect CDS view
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)
Page | 871
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
ROIBSCAN_SEL_MSEGO2 (Oil Aggregate table Inconsistency check)
ROIBSCAN_SEL_MSEGO2_H (Oil History table Inconsistency check)
Since the new data model eliminates data storage in the Aggregate/History tables
there is no longer the requirement to correct inconsistencies between the Core and
Oil counterpart tables. The 4 reports mentioned above are deprecated with SAP
S4HANA 1610.
Required and Recommended Actions
The reports for inconsistency check in the Oil Aggregate/History tables are no
longer available.
To check for inconsistency between MATDOC and MATDOCOIL the following
report can be executed:
o
ROIBSCAN_MISSING_O1O2
Data Storage as
per Old Data Model
MKPF
MSEG
MSEGO1
MSEGO2
Core Aggregate
tables (MARC...)
Data Storage as per
New Data Model
MATDOC
MATDOC
MATDOCOIL
MATDOCOIL
Aggregate Table +
MATDOC
Oil Aggregate tables
(MARCO1...)
Aggregate Table +
MATDOCOIL
Core History Tables
(MARCH...)
Aggregate Table +
MATDOCOIL
Oil History Tables
(MARCHO1…)
Aggregate Table +
MATDOCOIL
Details
No data is stored in MKPF
No data is stored in MSEG
No data is stored in MSEGO1
No data is stored in MSEGO2
Master data is stored in Aggregate
table, the transactional data is
calculated on the fly from MATDOC
Master data is stored in Aggregate
table, the transactional data is
calculated on the fly from
MATDOCOIL
Master data is stored in Aggregate
table, the transactional data is
calculated on the fly from MATDOC
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
Page | 872
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
Aggregate table, History table, Stock, Inconsistency, MARDO1
Page | 873
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
52 Industry Oil – OGSD
52.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:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/16c7aa533dae0077e10000000a4450e5.html
Page | 874
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
For further information about the FMB-WebDynpro based New Data Colllation see here:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/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):
1. 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.
2. 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.
3. 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".
4. 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.
5. 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
52.2 S4TWL - OGSD - Classic OGSD Interfaces
Application Components:
IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Page | 875
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/16c7aa533dae0077e10000000a4450e5.html
For further information about the NEW Interfaces see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/75320f54366b2e18e10000000a174cb4.html
Page | 876
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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):
1. 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.
2. 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.
3. You do not need to migrate OGSD-own funtionalities of the Classic Interfaces,
these have been migrated into the succcessor application "New Interfaces".
4. 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.
5. 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 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
52.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
Page | 877
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
For further information about the Sales Logistics Cockpit see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/1f320f54366b2e18e10000000a174cb4.html
For further information about the Telesales see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/82320f54366b2e18e10000000a174cb4.html
For further information about the FMB-WebDynpro based New Data Colllation see here:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/8e0cbd535862aa23e10000000a441470.html
Page | 878
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and recommended action(s):
1. If you want to continue using Sales Logistics Cockpit functionalities, you can
either switch to the Telesales functionality or you need to switch to the New Data
Collation, which is based on FPM and WebDynpro technology.
2. 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.
3. 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.
4. 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
52.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:
Page | 879
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/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/enUS/16c7aa533dae0077e10000000a4450e5.html
For further information about the FMB-WebDynpro based New Data Collation see here:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/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):
1. If you want to continue functionalities currently provided by "Liquid Petroleum
Gas", you need to switch to the New Data Collation, which is based on FPM and
WebDynpro technology, and configure it accordingly. This means you have to
rebuild your functionalities there. In this case you have to check how and where
you can recreate your own LPG-functionality inside the framework provided by
Page | 880
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
the "New Data Collation". If such own functionalities exists, you need to
manually migrate your functionalities into the New Data Collation in order to
make use of them in the future too.
2. You need to consider this as a project, as there are no migration tools which may
assist you in transfering code of form-routines or includes etc. into class-methods
or similar used by the New Data Collation. All adaptations need to be executed
manually.
3. You 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.
4. 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 Item, System Conversion to SAP S/4HANA, LPG, Transactions
/ICO/MO_L1, /ICO/MO_L2, /ICO/MO_L3, /ICO/MO_L9
52.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:
Page | 881
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
"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:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/82320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
1. 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.
2. 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.
3. 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
Page | 882
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
52.6 S4TWL - OGSD - Collective Orders
Application Components:
IS-OIL-DS-OGSD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2490624
S4TWL - OGSD - Collective Orders
Symptom
You want to convert a system with Add-on OGSD to SAP S/4HANA.
Reason and Prerequisites
You are using the OGSD application Collective Orders
Solution
Description:
Collective Orders is an OGSD application that involves customers ordering materials for
themselves and for other customers in the surrounding area, for example, to obtain better
conditions from the supplier.
Business related information:
The business advantages of collective orders include more efficient use of means of
transport and more options for pricing, due to lower shipment costs and the fostering of
relationships between the customer and the company. The ordering parties for a
collective order are clearly mapped in a customer hierarchy.
OGSD application "Collective Orders" 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 Collective Orders see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/4f330f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
1. 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 Collective Orders in
Page | 883
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
OGSD for the Business Suite, you need to switch to other SAP- or third-partysoftware.
2. You need to consider this as a project. All possible adaptations need to be
executed manually.
3. In case of switching to a new software you need to organize knowledge transfer to
all users working with Collective Orders 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, Transactions
/ICO/MO_CO01, /ICO/MO_CO, /ICO/MO_H1,/ICO/MO_H3
52.7 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
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
Page | 884
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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/enUS/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/enUS/1f320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
1. If you want to continue using Best Buy and Sales Logistics Cockpit
functionalities, you need to evaluate if other SAP components provide similar
functionality.
2. 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.
3. 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, Sales Logistics Cockpit
52.8 S4TWL - OGSD - Formroutines Telesales
Application Components:
IS-OIL-DS-OGSD
Related Notes:
Page | 885
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 SDprocess 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 OGSDscreen inside sales transaction VA01, VA02 etc. meaning: how and where shall data be
displayed?,
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/enUS/de310f54366b2e18e10000000a174cb4.html
For further information about "Reference Pricing" see:
Page | 886
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/fed89af9394b46999928ff6a6530a166.html
For further information about the replacement of Formroutines in Telesales into BAdIimplementations 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/enUS/82320f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
1. If you want to continue using Telesales functionalities currently provided by
Formroutines, you need to switch to the Telesales BAdIs functionality.
2. 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 BAdIimplementations and doing some customizing (this is laid out in SAP Note
2458477, see below).
3. 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.
4. 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 .
Other Terms
Simplification Item, System Conversion to SAP S/4HANA, Transaction VA01
52.9 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)
Page | 887
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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"
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/ad330f54366b2e18e10000000a174cb4.html
Required and recommended action(s):
1. 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.
2. You need to consider this as a project. All possible adaptations need to be
executed manually.
3. 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.
Page | 888
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
52.10 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
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.
Page | 889
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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):
1. 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.
2. 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.
3. 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
52.11 S4TWL - OGSD - Old Notes
Page | 890
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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/enUS/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/enUS/82320f54366b2e18e10000000a174cb4.html
Page | 891
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and recommended action(s):
1. 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).
2. 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.
3. 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
Page | 892
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
53 Industry Oil – OTAS
53.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.
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.
Page | 893
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
For further information about IDM see
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/c0959f5222297704e10000000a445394.html
For further information about IDM function "Trip Planning" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/19b99f5222297704e10000000a445394.html
For further information about IDM function "Combination Groups" see:
https://help.sap.com/viewer/ac2edcbb31de46e48bb3986017667d9a/7.0.6/enUS/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 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 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.
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
53.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)
Page | 894
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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/enUS/1f43d35225d10026e10000000a4450e5.html
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
Page | 895
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
53.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:
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/enUS/6809d552b2340126e10000000a4450e5.html
Required and recommended action(s):
Page | 896
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
1. 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.
2. 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.
3. 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
Page | 897
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
54 Industry Public Sector
54.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.
Related SAP Notes
Custom Code related information
SAP Note: 2226072
Page | 898
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
54.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
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
Page | 899
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
54.3 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
Page | 900
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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, the process budget maintenance was reflected by two tools, the
older Former Budgeting System or FBS (co-development with the Project System budget
capabilities) and the more recent Budget Control System (BCS). While a migration from
FBS to BCS is available since release ECC 5.0 already, a large number of customers was
quite satisfied with FBS and never saw a business need to execute the migration. SAP did
never announce the end of life for FBS in the Business Suite.
For SAP S/4HANA, the decision was taken to only support BCS as a tool, also because
the architecture of BCS is much more suitable to the simplification approach.
Business Process related information
Customers need to reconsider their needs in budget maintenance and how these are best
reflected in BCS. Different objects and configuration (compared to FBS) is available to
support budget maintenance. The BCS tool is already available since ECC 5.0, thus
impact analysis, PoCs, migration tests and migration can take place before the system
conversion to SAP S/4HANA.
Once on SAP S/4HANA, the FBS data is still available but operational transactions are
blocked. As the typical timeframe of an approved budget is one year, the time remaining
after system conversion to SAP S/4HANA might not be sufficient to consider and
execute a smooth Conversion. It is therefore recommended from a business perspective to
perform the FBS -> BCS migration before the system conversion to SAP S/4HANA.
How to determine relevancy
1. Using transaction SE16N, read table FM01 to get the list of all FM areas in the
client.
2. Using transaction SE16N, read BCS configuration table FMBCSA for each FM
area defined in table FM01.
o
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.
Page | 901
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Case 2: FBS to BCS migration is planned for future years. Maintained
fiscal year is later than current fiscal year. Check if migration from FBS
was already completed by selecting from the BCS budget header table
FMBH using transaction code SE16N.
▪ If an FMBH entry was found, then migration to BCS was already
completed. No action is required.
▪ If no FMBH entry was found, migration to BCS was not completed
and FBS might still be in use. Proceed as described above in
Business Process related information to migrate FBS to BCS
o 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.
o
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 PreChecks
Custom Code related The FBS tool is only technically disabled, not removed. Customer
information
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
54.4 S4TWL - Functionality for FACTS I and FACTS II (Federal Agencies
Centralized Tri
Application Components:
PSM-FG
Page | 902
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
RFACTS2_UPLMAF
RFACTS2_MAF
Page | 903
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
54.5 S4TWL - Expenditure Certification
Application Components:
PSM-EC
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270418
S4TWL - Expenditure Certification
Page | 904
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
FMEUFLEVELS
FMEUFLP1
FMEUFLP2
FMEUFPROC
Page | 905
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
FMEUFRCODE
FMEUFTAXHAN
How to determine relevancy
Go to transaction SFW2 and check if the Business Function PSM_EXP_CERT is active
or not. If the activation status of the Business Function is not ON then they have to do
nothing.
If the Activation status of the Business Function is ON: Go to transaction SE16N, check
if there are any entries in the table FMEUFRUN. If there are any entries in the table
FMEUFRUN, then please refer to the note 2270418. If no entries are found, no action is
needed.
Required and Recommended Action(s)
None
Related SAP Notes
Custom Code related
information
SAP note 226049
54.6 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
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
Page | 906
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
FD03
XD01
XD02
XD03
How to determine relevancy
Page | 907
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 Customer code to create or change customer or vendor master
information
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
54.7 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
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 provide the
data model needed to generate financial as well 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.
Page | 908
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 yet
available).
It is also planned to offer a Special Ledger migration option after the migration to S/4
HANA. Refer to the Innovation Discovery item 'Migration of special ledgers with
document splitting to the universal ledger' planned for a future version of S/4HANA.
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
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
Page | 909
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
54.8 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
customers. A compatibility view is attached as proxy object to the totals table
(CDS view V_FMBDT).
Page | 910
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
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 reinitialization 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 No technical object has been deleted or changed, thus no syntax
information
error will occur, However, data content is changed and needs to be
considered
For more details see SAP note 2226129
54.9 S4TWL - Funds Management Dimensions as part of the Universal
Journal
Application Components:
PSM-FA
Related Notes:
Page | 911
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Page | 912
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 All related objects do still exist,
information
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
54.10 S4TWL - Functionality for BCS Multi-level Budget Structure
Application Components:
PSM-FM
Related Notes:
Note Type
Note Number
Note Description
Page | 913
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 was this decided to
discontinue the functionality without commitment that any kind of successor would be
offered with a future release
It is therefore no longer considered the target architecture in SAP S/4HANA. Activation
of BF in SAP S/4HANA is not supported for new customers, customers with BF
activated in Business Suite and migrating to SAP S/4HANA should contact SAP Product
Management to discuss strategy going forward.
Business Process related information
A customer needs to decide if hierarchy-based budget processes are relevant to him and
how to reflect them with the remaining functionality. No standard suggestion can be
given.
The existing Business Processes cannot be executed in a hierarchical environment any
longer.
Page | 914
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Transaction not available in SAP
S/4HANA on-premise edition 1511
FMHIE_CHANGE
FMHIE_CHKINCONDATA
FMHIE_CHKINCONDISTR
FMHIE_COPY FMHIE_DELETE
FMHIE_DISPLAY
FMHIE_EXPORT FMHIE_GENERATION
FMHIE_HIEID FMHIE_IMPORT
How to determine relevancy
Go to transaction 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)
None.
Related SAP Notes
Custom Code related information
SAP Note: 2226122
54.11 S4TWL - 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
Symptom
Page | 915
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
•
Select each ADB rule (table FMADB_HEADER), and look for records in the
following folders:
o Pool account assignments (tables FMADB_POOL)
Page | 916
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Bank Accounts (FMADB_GLACCOUNT)
Incoming Interest Posting (table FMADB_INT_DOC) without blanks in
document type and account fields
o Transfer Parameters (table FMADB_DOC) without blanks in document
type, posting keys and target account fields
If all these customizing records are found for at least one ADB rule (header),
please proceed as described above.
o
o
•
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
Page | 917
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55 Industry Retail & Fashion
55.1 S4TWL - Retail Power Lists
Application Components:
LO-SRS, LO-SRS-IM
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 .
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.
55.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
Page | 918
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 .
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.
55.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
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Page | 919
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 .
Business Process related information
Move to available functionality of markdown profile integrating in the price planning
workbench.
Furthermore, SAP evaluates whether to develop a price and markdown
optimization solution as a consuming application on SAP Customer Activity Repository.
Required and Recommended Action
No special actions for retail markdown plan is needed when converting from SAP ERP to
SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if markdown planning is used.
This is the case if transactions WMF*, WMR* are used.
This also can be checked via transaction SE16N. Enter table WMFH, or WMFP and
check whether there are any entries.
55.4 S4TWL - Retail Bonus Buy
Application Components:
SD-BF, SD-BF-FG
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371559
S4TWL - Retail Bonus Buy (transaction
VBK*)
Symptom
You are doing a system conversion to SAP S/4HANA. The following SAP S/4HANA
Transition Worklist item is applicable in this case.
Page | 920
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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, onpremise edition .
Business Process related information
Move to available bonus buy functionality via transactions RDMBB*.
Required and Recommended Action
No special actions for bonus buy is needed when converting from SAP ERP to SAP
S/4HANA.
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.
55.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
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
Page | 921
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
In SAP S/4HANA Retail for merchandise management, retail sales forecasting is
available, but defined as "not strategic any more". See SAP note 2269324 Compatibility Scope Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
The following areas are affected:
•
•
•
Sales forcasting for stores
Import of external forecast data
Forecast with AHD (Alternative Historical Data)
UDF (Unified Demand Forecast) is strategic for forecasting in retail, which is part
of SAP Customer Activity Repository.
Required and Recommended Action
No special actions for retail sales forecasting is needed when converting from SAP ERP
to SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if retail sale forecasting is used.
This is the case if transactions MAHD*, MDRD*, WFCS*, MPR2 are used.
This also can be checked via transaction SE16N. Enter table MAHD, WFCS_WRFT and
check whether there are any entries.
55.6 S4TWL - Retail Order Optimizing: Load Build, Investment Buy
Application Components:
IS-R, IS-R-PUR, IS-R-PUR-LB
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
Page | 922
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Description
In SAP S/4HANA Retail for merchandise management, functionality to support order
optimizing via load build, and investment buy is available, but defined as "not strategic
any more". See SAP note 2269324 - Compatibility Scope Matrix for SAP S/4HANA,
on-premise edition .
Business Process related information
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 WLB* are used.
This also can be checked via transaction SE16N. Enter table WVFB, WBO* and check
whether there are any entries.
55.7 S4TWL - Retail Rapid Replenishment
Application Components:
IS-R, IS-R-PUR, IS-R-PUR-RP
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
Page | 923
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
In SAP S/4HANA Retail for merchandise management, rapid repelnishment and
planning workbench is available, but defined as "not strategic any more". See SAP
note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, on-premise edition .
Business Process related information
There is SAP Forecstaing & Replenishment as an existing solution alternative.
Required and Recommended Action
No special actions for rapid repelnishment is needed when converting from SAP ERP to
SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if rapid replenishment, or planning workbench is
used.
This is the case if transactions WRP1R, WWP* are used.
55.8 S4TWL - Automatic Document Adjustment
Application Components:
IS-R-PUR-ADA
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:
1. The direct entry function is activated per default for all document categories to
simplify the creation of worklist entries.
Page | 924
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
2. The field length of the Material Number data element (MATNR) is 40 characters.
As a consequence, the field length of data element 'VAKEY' is enhanced and the
database tables WIND and S111 have also been adjusted.
Business Process related information
1. In SAP S/4HANA, the indicator for direct entry is set now automatically during
the update process of conditions. This means that:
•
•
When a user saves a condition change - including the creation of a new condition
- an entry is made in the worklist (table WIND) for all document categories with
valid Customizing settings.
For worklist creation, the transaction MEI4 can no longer be used.
For more information, please see SAP Note 519685 (Conversion of the procedure for
Worklist creation).
Note also that change pointers do not have to be updated for message type CONDBI
if direct entries are activated. With the conversion to the 'direct entry' procedure, you can
deactivate the update of change pointers if you do not use it for other purposes
2. Rebuilding business data volume (tables WIND and S111)
•
•
SAP recommends that you process all open worklist entries completely before
conversion to SAP S/4HANA. In this case, no activities for automatic document
adjustment are required after the system conversion process
If the worklist cannot be completed in the SAP ERP system, you can proceed with
the procedure described in section 'Required and Recommended Actions on Start
Release.
Transaction not available in SAP MEI4 - Create Worklist
S/4HANA on-premise edition
1511
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)
Page | 925
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
Rebuild the table entries for S111 and WIND for the used document categories by
using the appropriate setup reports (see below). Make sure that the filter selection
for rebuilding the S111 entries is meaningful by selecting the appropriate
organizational criteria ( time, org data, docnr, ...) [Rebuild is in SAP S/4HANA]
Doc.
category
01
02
10
11
20
30
31
32
35
40
50
55
60
Report for rebuilding S111 and WIND
entries
RMEBEIN3
RMEBEIN3
RWVKP012
Description
Purchase Order
Scheduling Agreement
Sales Price Calculation
Sales Price Calculation
RWVKP012
Index
Customer billing document RMEBEIL3
Vendor billing document RMEBEIL3
Expense document
RMEBEIL3
Vendor settlement
RMEBEIV3
document
Remuneration list
RMEBEIL3
Vendor settlement request RMEBEIZ3
Assortment List
RMEBEIN3
POS-Outbound
RMEBEIN3
Customer settlement
RMEBEIK3
If you want to process multiple applications in one step (subsequent settlement and
automatic document adjustment), you can also use report RMCENEUA.
Related SAP Notes
Conversion Pre-Checks
SAP Notes: 2192984, 2215169
55.9 S4TWL - Retail Additionals
Application Components:
LO-ADM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2371631
S4TWL - Retail Additionals
Symptom
Page | 926
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 .
Business Process related information
For the use cases of additionals the alternatives are:
•
•
•
There is an existing Fiori app to print labels.
There is existing functionality of value added services for activities or products
which are applied to ordered products that enhance their value, worth,
functionality, or usefulness. It is planned to enhance functionality of value added
services in future releases.
To support processes of floor ready merchandise: development of a future
solution closely integrated with SAP EWM is under evalution.
Required and Recommended Action
No special actions for additionals functionality is needed when converting from SAP
ERP to SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if additionals are used.
This is the case if transactions WTAD*, WRF_WTAD*, WTR1, WTR2, WRF_WTR3
are used.
This also can be checked via transaction SE16N. Enter table WTADDI and check
whether there are any entries.
55.10 S4TWL - Article Discontinuation
Application Components:
IS-R, IS-R-BD, IS-R-BD-ART
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368683
S4TWL - Article Discontinuation via
transactions WSE*
Page | 927
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
In SAP S/4HANA article discontinuation via transactions WSE1, WSE2, WSE3, WSE4,
WSE5, WSE8 is not available anymore.
Article discontinuation should be carried out via transaction WRF_DIS_SEL, and
WRF_DIS_MON which are richer in functionality than WSE*.
Required and Recommended Action(s)
Switch to article discontinuation via transactions WRF_DIS_SEL, and WRF_DIS_MON.
How to Determine Relevancy
This Simplification Item is relevant if transactions WSE1, WSE2, WSE3, WSE4, WSE8
are used.
Other Terms
WSE1, WSE2, WSE3, WSE4, WSE5, WSE8, WRF_DIS_SEL, and
WRF_DIS_MON, SYSTEM_ABAP_ACCESS_DENIED
55.11 S4TWL - 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)
Page | 928
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 transaction PRICAT is not supported anymore. Transactions W_SYNC or
W_PRICAT_MAINTAIN need to be used.
Business Process related information
It is required that the latest Open Catalog Interface is used.
Required and Recommended Action(s)
Execute process as described in referenced note 2326511.
How to Determine Relevancy
This Simplification Item is relevant if GDS is used.
This is the case if transactions PRICAT, W_SYNC, W_PRICAT_MAINTAIN are used.
55.12 S4TWL - Business Partner in Site Master
Application Components:
LO-RFM, LO-RFM-MD, LO-RFM-MD-SIT, LO-MD-PL, IS-R-BD-
SIT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2339008
S4TWL - Business Partner for Sites
Symptom
Page | 929
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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.
Furthermore, check whether transactions WRFCATEGORYSHOP, WRFCLOSESHOPS,
WRFDELIVERYSITESHOPS, WRFREGIONSHOPS, WRFSHOPCAT,
WRFSHOPDEP, WRF_ARC_DEPSHOP, WRF_TCHAIN_MIGR, WSHOPMIGR are
used.
55.13 S4TWL - Logistical Variant
Application Components:
IS-R, IS-R-BD, IS-R-BD-ART
Related Notes:
Page | 930
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
For articles with several units of measures it was possible via logistical variants to a)
manage the stocks of an article separately for different units of measure and b) plan
requirements according to the unit of measure
Business Process related information
In SAP S/4HANA logistical variants are not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to logistical variants available in SAP S/4HANA. It
is under evaluation whether there will be functionality in a future release to address the
business requirement.
How to Determine Relevancy
This Simplification Item is relevant if logistical variants are used. This can be checked
via transaction SE16N. Enter table MARA and check whether there are entries with field
BFLME (Logistical Variant) not equal blank.
55.14 S4TWL - Article Hierarchy
Application Components:
IS-R, IS-R-BD, IS-R-BD-CDT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368680
S4TWL - Article Hierarchy via transactions
MATGRP*
Page | 931
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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*.
How to Determine Relevancy
This Simplification Item is relevant if article hierarchy of this type is used.
This is the case if transactions MATGRP01 - MATGRP07 are used.
This also can be checked via transaction SE16N. Enter table MATGRP_HIER and check
whether there are any entries.
55.15 S4TWL - Market Basket Calculation
Application Components:
LO-MD, LO-MD-RPC
Related Notes:
Note Type
Note Number
Note Description
Page | 932
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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.
How to Determine Relevancy
This Simplification Item is relevant if market basket calculation is used.
This is the case if transactions WKK1 - WKK4 are used.
This also can be checked via transaction SE16N. Enter table WWKK, or WWKP and
check whether there are any entries.
55.16 S4TWL - 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)
Page | 933
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
Merchandise and assortment planning/category management offered planning
functionalities, analysis and reporting options, for seasonal and non seasonal retailers,
Business Process related information
In SAP S/4HANA, merchandise and assortment planning/category management is not
available anymore (software packages CM_MAP, WIS_PLAN, transaction CMMAP*,
WXP*), as it is based on key figures from RIS (Retail Information System), which is not
available anymore.
Please note that this is not the BW based solution SAP Merchadise and Assortment
Planning (SAP MAP).
Strategic solutions are SAP Merchandise Planning for Retail, and SAP Assortment
Planning for Retail, based on SAP Customer Activity Repository.
Required and Recommended Action(s)
Switch to strategic solutions SAP Merchandise Planning for Retail, and SAP Assortment
Planning for Retail.
How to Determine Relevancy
This Simplification Item is relevant if Merchandise and Assortment Planning/category
management is used.
This is the case if transactions WXP*, or CMMAP*are used.
This also can be checked via transaction SE16N. Enter tables S202 S203 S204 S206
S207 S208 S209 S210 S211 S212 S214 S216 S217 S218 S219 and check whether there
are any entries.
55.17 S4TWL - Retail Method of Accounting
Application Components:
IS-R, IS-R-LG, IS-R-LG-RMA
Related Notes:
Page | 934
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
How to Determine Relevancy
This Simplification Item is relevant if Retail Method of Accounting is used.
This is the case if transactions WRMA* are used.
This also can be checked via transaction SE16N. Enter table WRMA_CLIENT and check
whether there are any entries, and whether there are entries in table WRMA_PROFILE.
55.18 S4TWL - Perishables Procurement
Application Components:
IS-R, IS-R-PUR, IS-R-PUR-PER
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2368739
S4TWL - Perishables Procurement
Page | 935
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
A perishables buyer needs to have all the relevant data available in order to make a
qualified decision about the perishables assortements, quantities, prices, source of supply,
delivery dates and the distribution. To address this need, the central Perishables
Procurement Work Center was developed. This work center supported the buyer with
tools and consolidated informations that are required to manage purchasing\distribution
decisions for perishables across the company.
Business Process related information
In SAP S/4HANA, perishables procurement is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to perishables procurement available in SAP
S/4HANA. It is under evaluation whether there will be functionality in a future release.
How to Determine Relevancy
This Simplification Item is relevant if perishables procurement is used.
This is the case if transactions WDFR, WDFR2, WDFR3 are used.
This also can be checked via transaction SE16N. Enter table WDFR_DISP and check
whether there are any entries.
55.19 S4TWL - 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
Page | 936
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
How to Determine Relevancy
This Simplification Item is relevant if fresh item procurement is used.
This is the case if transactions FIP_MD, FIP_SD, FIP_TD are used.
55.20 S4TWL - 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
Page | 937
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
The planning application "Profit Center Analytics in Retail: Store Planning" allowed
planning the finances for stores in the retail sector. A store was portrayed as a profit
center and a cost center. It was possible to perform both revenue planning and cost
planning for the stores.
Business Process related information
In SAP S/4HANA, Retail Ledger / Profit Center Analytics is not available anymore.
Required and Recommended Action(s)
Strategic planning solutions are SAP Merchandise Planning for Retail, and
SAP Assortment Planning for Retail
How to Determine Relevancy
This Simplification Item is relevant if profit center analytics is used.
This is the case if transactions RETAIL_* are used.
This also can be checked via transaction SE16N. Enter table PCRRETAILA and check
whether there are any entries.
55.21 S4TWL - Goods Receipt Capacity Check
Application Components:
MM-PUR, MM-PUR-OPT, 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.
Page | 938
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Process related information
In SAP S/4HANA, goods receipt capacity check is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to goods receipt capacity check available in SAP
S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if goods receipt capacity check is used.
This is the case if transactions WGRC* are used.
This also can be checked via transaction SE16N. Enter table WGRC_ACT* and check
whether there are any entries.
55.22 S4TWL - Online Store
Application Components:
LO-MD, LO-MD-PC
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)
Page | 939
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
SAP Hybris Commerce is the strategic solution for omnichannel commerce.
How to Determine Relevancy
This Simplification Item is relevant if online store is used.
This is the case if transactions WW10, WW20, WW30 are used.
55.23 S4TWL - Generic Article Harmonization
Application Components:
LO-RFM, LO-RFM-MD, LO-RFM-MD-ART
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
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
Page | 940
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
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
Required and Recommended Action(s)
The complete data migration process is divided into three phases: manual started premigration 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 PostMigration 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).
Other Terms
SAP S4HANA
55.24 S4TWL - Retail Labeling
Application Components:
LO-ADM
Related Notes:
Page | 941
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
How to Determine Relevancy
This Simplification Item is relevant if labeling is used.
This is the case if transactions WEBU, WENA, WESA are used.
55.25 S4TWL - Seasonal Procurement
Application Components:
IS-R, IS-R-PUR, IS-R-PUR-POF
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.
Page | 942
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
How to Determine Relevancy
This Simplification Item is relevant if seasonal procurement is used.
This is the case if transactions WRFAPC*, WA10, WCOC*, WOTB*, WPCTR*,
WPOHF*, WRFROCAT, WOOS are used.
This also can be checked via transaction SE16N. Enter table WRF_APC_PLH and check
whether there are any entries.
This also can be checked via transaction SE16N. Enter table EKKO and check whether
there are entries with field POHF_TYPE (Seasonal Purchase Order Processing) is not
equal blank.
55.26 S4TWL - Replenishment
Application Components:
IS-R, IS-R-PUR, IS-R-PUR-RP
Related Notes:
Note Type
Note Number
Note Description
Page | 943
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Business Impact
2370106
S4TWL - Retail 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
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.
This is the case if transactions WR30, WR31, WR94, WR95, WRP1, WRFE, WRSO,
WRSR, MD01N are used.
Page | 944
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.27 S4TWL - Retail Information System
Application Components:
IS-R-IS, IS-R, IS-R-IS-RIS
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370131
S4TWL - Retail Information System (RIS)
and Category Management Workflow
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
operational reporting requirements CDS (Core Data Services) technology should be used.
It is planned to offer retail specific content in a future release.
How to Determine Relevancy
This Simplification Item is relevant if RIS is used.
This also can be checked via transaction SE16N. Enter table S077 S078 S079 S080 S081
S082 S083 S084 S085 S086 S087 S105 S106 S107 S108 S110 S117 S119 S120 S121
S122 S123 S124 S160 S200 S202 S203 S204 S205 S206 S207 S208 S209 S210 S211
S212 S214 S216 S217 S218 S219 S270 S271 S272 S273 S274 S275 S276 S277 S278
S279 and check whether there are any entries.
Page | 945
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
55.28 S4TWL - 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).
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 WCSO WCSOD WCU2 WSAK WSAM_ENTRY WSAU
Page | 946
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
WSGM WSHT WSSW WSTA WSTE WSTE_NEW WSTED WSTI WSTL WSTP
WSTSA WSTU WSTV WSTV_R_PDC_MATDATA WOSCR_CBL WSRS_HI_MENU
are used. This is not a complete list.
55.29 S4TWL - 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.
Required and Recommended Action(s)
In SAP S/4HANA there are alternatives to display the information.
How to Determine Relevancy
This Simplification Item is relevant if iViews for retail buying are used.
This is can be observed if functions modules
WRB_RFC_GET_OPEN_PO_OVERVIEW, WRB_RFC_GET_VENDOR_OPEN_PO,
WRB_RFC_GET_OOS_OVERVIEW, WRB_RFC_VENDOR_GET_OUTOFSTOCKS,
WRB_RFC_VENDOR_GET_CONTACTDATA are called.
Page | 947
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.30 S4TWL - Prepack Allocation Planning
Application Components:
IS-R, IS-R-BD, 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.
How to Determine Relevancy
This Simplification Item is relevant if prepack allocation planning is used.
This is the case if transactions WSTN11, WSTN13, WSTN14, WSTN15 are used.
This also can be checked via transaction SE16N. Enter table WSTN_PP_HEADER and
check whether there are any entries.
55.31 S4TWL - Assortment List
Application Components:
IS-R, IS-R-IFC, IS-R-IFC-AL
Related Notes:
Page | 948
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
WDB*HPR* is still available in SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if assortment list is used.
This is the case if transactions WBBA, WDBI, WDBI_ALV, WDBM, WDBM_ALV,
WDBU, WDBU_ALV are used.
55.32 S4TWL - In-store food production integration
Application Components:
LO-MD, LO-MD-FPD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370148
S4TWL - In-store food production
integration
Page | 949
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
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
PhysicalInventoryCountERPRequest_Out
PhysicalInventoryCountERPCreateRequest_In
PhysicalInventoryCountERPConfirmation_In
GoodsMovementERPCreateRequest_In
GoodsMovementERPNotification_Out
are used.
55.33 S4TWL - PRICAT Outbound
Application Components:
IS-R, IS-R-BD, IS-R-BD-PCT
Related Notes:
Note Type
Note Number
Note Description
Page | 950
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 information.
How to Determine Relevancy
This Simplification Item is relevant if PRICAT outbound is used.
This is the case if transactions VPRE, VPRICAT, WEB_PRICAT, WPRI are used.
This also can be checked via transaction SE16N. Enter table PRICAT_K001 and check
whether there are any entries.
55.34 S4TWL - Retail Business Function Harmonization
Application Components:
LO-RFM, LO-RFM-SWT
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2339317
S4TWL - Retail Business Function
Harmonization
Symptom
Page | 951
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
55.35 S4TWL - Retail Obsolete Transactions
Application Components:
IS-R
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2370655
S4TWL - Retail Obsolete Transactions
Page | 952
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
CLWA
CLWB
CLWC
CLWD
CLWJ
CLWK
CLWL
WTRA1
WTRA2
WTRA3
WA05
WA06
Description of
Transaction
Create Material Group
(MMS)
Change Material Group
(MMS)
Display Material Group
(MMS)
Delete Material Group
(MMS)
Change Generic Article
(MMS)
Display Generic article
(MMS)
Delete Generic Article
(MMS)
Maintain Runtime
Customizing Table
Runtime Measurement:
Delete Logs
Runtime Measurement:
Display Logs
Alloc Tbl FDG: Generate
POs
Alloc Tbl FDG: Generate
Deliveries
Alternative Transaction
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
not relevant anymore
not relevant anymore
not relevant anymore
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
Page | 953
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
WA07
WA12
WA15A
WA15B
WA15C
WA40
WA50
WA53
WA54
WA60
WC11
WC21
WC25
WC26
WC27
WC33
WC41
WER_RULE_PROC_TEST
WB07
WB08
WB30
Alloc Tbl FDG: Generate was already obsolete in
Wrhse Orders
SAP ERP
Create Reminders/Accept was never released
Plnd Qties
Mess.Deter., Alloc Tbl:
WA/A
Creat.Cond.R
Mess.Deter.,Alloc Tbl:
WA/B
Chng Cond.Rec
Mess.Deter.Alloc Tbl:
WA/C
Displ Cond.Rec
Adjust Alloc Tbl After
was already obsolete in
Entering GR
SAP ERP
Generate Allocation Rule obsolete because of
deprecated RIS
Create Selection Variants obsolete because of
deprecated RIS
Generate Alloc Rule / Test obsolete because of
RIS-L
deprecated RIS
Create Selection Variant obsolete because of
for PO
deprecated RIS
Batch Changes,
batch transaction of "real"
Assortments
transaction
Batch Reorg Data in LIS batch transaction of "real"
transaction
Batch Assortment
batch transaction of "real"
List/Shelf-Edge Lab
transaction
Batch Forecast
batch transaction of "real"
transaction
Batch Requirements
batch transaction of "real"
Planning per Plnt
transaction
Batch worklist for doc.
batch transaction of "real"
index
transaction
Assortment List: Initial. & batch transaction of "real"
FullVers
transaction
Test program for
test transaction
processing rules
Change plant/customer
not relevant anymore
assignment
Change plant/vendor
not relevant anymore
assignment
Mass maintenance MG to WB30N
plant
Page | 954
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
WB35
Layout overview
WBTE
Export plant data (file
transfer)
Import plants (file transfer)
Site Master Transport
Customize Site Master
Transport
Maintain plant hierarchy
(SD)
Display customer
hierarchy (SD)
Plant groups
WBTI
WBTIMEX
WBTIMEX_CUST
WDH1
WDH2
WOG3
WF10A
Collective PO Without
Tabstrips
WF50A
Adjust Distribution
WF80_DEL
Display Delivery
Generation Logs
WF90_DEL
Delete Delivery
Generation Logs
WLB3
Autom. opt. PO-based load
building
WGDS_CONFIRM
Send confirmation
WGDS_CONFIRM_MANAGE Confirmation manager
R
ARTE
Replace Articles in Layout
Modules
WLAM
Layout Maintenance
WLMM
Layout Module
Maintenance
WLMV
Maintenance of Layout
Module Version
WLWB
Layout Workbench
WPLG
Space Management
WRFMATCHARVAL
Char. Value Change to
Variants
WRF_WSOA1
Create Assortments
WRF_WSOA2
Change Assortments
WRF_WSOA3
Display Assortments
WRF_WSOA4
Delete Assortment
obsolete because of
deprecated RIS
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
was already obsolete in
SAP ERP
WF10
WF50
WF80
WF90
WLB13
not relevant anymore
not relevant anymore
not relevant anymore
WLWBN
WLWBN
WLWBN
WLWBN
WPLGN
not relevant anymore
WSOA1
WSOA2
WSOA3
WSOA4
Page | 955
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
W_PRICAT_ASSIGN_001
W_PRICAT_ASSIGN_003
W_PRICAT_SEL_CREATE
WRF_PRICAT_LOG1
WSFP_LOG_ALL_IN
WSFP_LOG_ALL_OUT
WSFP_LOG_CHG_OUT
WSFP_LOG_INIT_OUT
WSFP_LOG_INTERNAL
WSFP_LOG_MAN_OUT
WSFP_TRANSFER
WLAN
WSK3
WSL3
WSL4
WSL5
WSL6
WSL7
WSLA
WSLB
WSLG
WSM4
WSM6
WSM7
WSM8
WSOA5
Assignment ILN Vendor
Pur. Group
Assignment SAP Mat. Gr.
- Purch.Gr.
Maintain Price Catalog
Log for Price Catalog
Ind Processing, All Logs
All Logs
Change Messages Log
Initial Data Transfer
For Internal Use Only
Manual Selection
Master Data Transfer
Listing Conditions for
Layout Module
Assortment copy, batch
input
Material listed in plant
before?
Analyze material in
module
Modules in plant
Assortment structure,
Plants
Vendor material list
Assortment Users per
Assortment
Assortment per
Assortment User
Compare promotion POs sales orders
Relist after ch. plant/ mat.
grp mas
Delete Individual Listing,
Material
Delete Individual Listing,
Material
Setup assrt.owner
assortment as WRF6
Assign assortment to
customer
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
WESLOG
WESLOG
WESLOG
WESLOG
WESLOG
WESLOG
WESOUT
not relevant anymore
not relevant anymore
WSL11
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
not relevant anymore
was already obsolete in
SAP ERP
was already obsolete in
SAP ERP
WSE6
WSE6
WSM3
WSOA2
Page | 956
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
WSOE
Assign material groups
WSP6
Delete ind. listing, mat. plant
Display Possible Sources not relevant anymore
of Supply
Create Components for Set was already obsolete in
Material
SAP ERP
Display Components for was already obsolete in
Set Material
SAP ERP
Create Components for
was already obsolete in
Display Matl
SAP ERP
Display Components for was already obsolete in
Display Matl
SAP ERP
Create Components for
was already obsolete in
Prepack Matl
SAP ERP
Display Components for was already obsolete in
Prepack Matl
SAP ERP
Create Components for
was already obsolete in
Full Product
SAP ERP
Display Components for was already obsolete in
Full Product
SAP ERP
Change Components for
was already obsolete in
Set Material
SAP ERP
Change Components for
was already obsolete in
Display Matl
SAP ERP
Change Components for
was already obsolete in
Prepack
SAP ERP
Change Components for
was already obsolete in
Full Product
SAP ERP
Load programs global data not relevant anymore
Vendor Mass Maintenance not relevant anymore
Copy Article Hierarchy
WMATGRP06N
Simulation of Article
WMATGRP08N
hierarchy copy
Create customer from
not relevant anymore
vendor
WSOSDISPLAY
MGW0
MGW1
MGW2
MGW3
MGW4
MGW5
MGW6
MGW7
MGW 8
MGW9
MGWA
MGWB
DUMMY_MASS_VENDOR
MASS_VENDOR
WMATGRP06
WMATGRP08
WDKR
was already obsolete in
SAP ERP
WSE6
How to Determine Relevancy
This Simplification Item is relevant if any of the above listed transactions is used.
Page | 957
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.36 S4TWL - 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.
Required and Recommended Action(s)
Switch to strategic functionality of distribution curves.
How to Determine Relevancy
This Simplification Item is relevant if value and quota scales are is used.
This is the case if transactions WC01 WQ01 WQ02 WQ03 WQ04 WQ05 WQ11 WQ12
WQ13 WQ14 WQ15 WQ21 are used.
This also can be checked via transaction SE16N. Enter table WMQK, or WMWK and
check whether there are any entries.
Page | 958
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.37 S4TWL - 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
Business Process related information
In SAP S/4HANA, AIN (India Margin Protection) is not available anymore.
Required and Recommended Action(s)
There is no equivalent functionality to AIN available in SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if AIN is used.
This is the case if transactions J1IR01 J1IR02 J1IR03 J1IR10 J1IR20 J1IRAIN01
J1IRAIN02 J1IRAIN03 J1IRAIN10 J1IRAIN20 are used.
This also can be checked via transaction SE16N. Enter table J_1IRAINHDR and check
whether there are any entries.
Page | 959
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.38 S4TWL - SAP Smart Business for Retail Promotion Execution
Application Components:
LO-MD, LO-MD-PR
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
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.
55.39 S4TWL - Retail Factsheets
Application Components:
LO-MD
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2377780
S4TWL - Retail Factsheets
Page | 960
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
55.40 S4TWL - 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
Page | 961
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 via a pilot note. Please, open an incident
in component LO-RFM-MD-ART if you are interested in that workaround, so we can
assign the note to you.
How to Determine Relevancy
This Simplification Item is relevant if retail short text replacement is used.
Call transaction MM01. If it reads "Create Article" the replacement is used, if it reads
"Create Material" it is not used.
55.41 S4TWL - Subsequent Settlement - Vendor Rebate Arrangements
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:
Page | 962
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
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
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 MEB1; MEB7; MEBV, MEBH
S/4HANA on-premise edition
1511
Required and Recommended Action(s)
Page | 963
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
In SAP S/4HANA there are no direct activities required for continuing the business
process for subsequent settlement, with the only exception that the agreements have to be
closed after the end of the validity period.
If a recompilation of the business volume data is required, the table S111 has to be rebuilt
with the report RMEBEIN3 as described in note 73214
Related SAP Notes
Conversion Pre-Checks
Related SAP Notes
SAP Notes: 2194923, 2215220
SAP Note: 73214
55.42 S4TWL - 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.
Page | 964
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
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).
In SAP S/4HANA MRP related article master data on segment level are not
available anymore.
In SAP S/4HANA segmentation maintenance in the article 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 following fields are not available:
o Discrete Batch Number (SGT_CHINT)
o Stock Protection Indicator (SGT_STK_PRT)
o Consumption Priority (SGT_PRCM)
o ATP/MRP Status for Material and Segment
(SGT_MRP_ATP_STATUS)
o Date from which the plant-specific material status is valid
(SGT_MMSTD)
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.
55.43 S4TWL - Allocation Run Master Data
Application Components:
LO-RFM-MD, LO-RFM-MD-ART, LO-RFM
Page | 965
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2465556
S4TWL - Master Data for Order Allocation
Run (ARun) in Fashion Management
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.
Page | 966
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.44 S4TWL - 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.
In SAP S/4HANA prior to 1709 FPS02 you need to use standard sales orders only to
realize order to cash (O2C) lifecycle.
Page | 967
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
55.45 S4TWL - Allocation Run
Application Components:
LO-RFM, LO-RFM-ARN
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
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
Page | 968
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
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
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.
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)
Page | 969
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Adjust the respective business processes accordingly.
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
55.46 S4TWL - 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
Page | 970
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
55.47 S4TWL - 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
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.
Page | 971
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
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
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_PFM Miantain PFM Rules
FSH_PROD Create product number for GTS transfer
FSH_PSM Miantain PSM Rules
FSH_SPLITPO Split Purchase Order
FSH_PG_CTCT Maintain Condition Tables
FSH_PG_CTFC Maintain Field Catalog
FSH_PG_CT_ACC_SEQ Maintenance of Access Sequences
FSH_PG_CT_COND_TYPE Maintain Condition Types in POG
FSH_PG_CT_DET_PROC Determination procedure maintenance
FSH_PG_CT_MGROUP Maintenance Group
FSH_POGD Delivery Date Determination
FSH_POGG Group Type Determination
FSH_POGO Order Type Determination
Page | 972
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
FSH_POGT PO Generation Tool
FSH_POGTWB Purchase Order Workbench
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).
Required and Recommended Action
Implemented business processes need to be adjusted according to the changes listed
above.
In case of Purchase Order Generation Tool process information was stored in table
FSH_POG. This table is not available in SAP S/4HANA anymore. If these data
are needed for future reference, a back-up of the table entries need to be taken .
For clean-up report, please see refernced not 2590824.
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.
Usage of Purchase Order Generation Tool can be checked via transaction SE16N. Enter
table FSH_POG and check whether there are entries.
Other Terms
Fashion, Retail.
Page | 973
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.48 S4TWL - Season Active in Inventory Management
Application Components:
LO-RFM, LO-RFM-MD-ART, LO-RFM-MD
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
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’
55.49 S4TWL - Fashion changes in 1709 FPS02
Page | 974
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Application Components:
LO-RFM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2627238
S4TWL - Fashion changes in 1709 FPS02
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 in SAP S/4HANA for fashion for vertical
business, when compared to SAP Fashion Management.
Business Process related information
The following transactions are obsolete prior to SAP S/4HANA 1709 FPS02, and are
available starting w/ SAP S/4HANA 1709 FPS02:
•
•
•
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 transaction is obsolete in SAP S/4HANA
•
•
FSH_POGT PO Generation Tool
FSH_CO09 Generic Article CO09
Required and Recommended Action
Implemented business processes need to be adjusted according to the changes listed
above.
Page | 975
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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_QDP, FSH_PCW, FSH_POGT.
Other Terms
Fashion, Retail.
55.50 S4TWL - Retail Revenue Management Integration
Application Components:
LO-MD, LO-MD-RDM
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2630840
S4TWL - Retail Revnue 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
SAP Retail Revnue Management is not available anymore. Thus, the respective
integration scenario is not needed anymore, and as a consequence not available in SAP
S/4HANA Retail for merchandise management.
Business Process related information
In case an integration scenario with business object Promotion/Retail Event is needed the
available enterprise services can be used.
Required and Recommended Action
Switch to intergration with available enterprise services for business object
Promotion/Retail Event.
How to Determine Relevancy
Page | 976
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
This Simplification Item is relevant if retail revenue management integration is used.
This is the case if transactions WPMLOGINT, WPMLOG, WPMLOG1, WPMLOG2,
WPMLOG3 , WPMOA, WPMOAC are used.
55.51 S4TWL - Segmentation (Upgrade SAP S/4HANA 1709 to 1809)
Application Components:
LO-RFM, LO-RFM-SGT
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
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. The following Strategies 1:1, 1:N, N:1 are supported using ATP pool
Segment.
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
Page | 977
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
to be deleted via a pre-migration report R_SGT_POOL_SEGMENT_DELETE as ATP
pool segment is not available in S/4HANA 1709.
Note: N:1 is achieved in pool segment by mapping the requirement segments to common
pool segment and stock segment is mapped to common pool segment. Customer can
default and determine requirement segment and stock segment using SGT_DEFAULT
transaction.
For example: In S/4 1709 , customer has maintained below ATP mapping in SGT_CMRP
as mentioned below
RET ---> COMMONSTOCKSEG
ECOMM ---> COMMONSTOCKSEG
WHO ----> COMMONSTOCKSEG
In 1809 after ATP pool migration , the data will be as mentioned below
RET ---> POOL1
WHO ---> POOL1
ECOMM ---> POOL1
COMMONSTOCKSEG ---> POOL1
Customer can maintain RET , WHO, ECOMM as default requirement segment values on
demand side in the SGT_DEFAULT and COMMONSTOCKSEG as default Stock
segments on Supply side.This is one of the example to achieve N:1 using Pool Segment.
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
55.52 S4TWL - Conversion of Season Master Data to SAP S/4HANA 1809
Application Components:
LO-RFM-CA, LO-RFM, LO-RFM-CA-SE
Page | 978
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2640859
S4TWL - Conversion of Season Master
Data to S/4HANA 1809
Symptom
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)
Page | 979
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES ->
RFM_SEASONS
o FSH_SEASONS_T, FSH_COLLECTIONS_T, FSH_THEMES_T ->
RFM_SEASONS_T
SAP ERP (Retail)
o First Step
▪ TWSAI -> FSH_SEASONS
▪ T6WST -> FSH_SEASONS_T
▪ TWSAI -> FSH_COLLECTIONS
▪ T6WSAT -> FSH_COLLECTIONS_T
o Second Step
▪ FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES ->
RFM_SEASONS
▪ FSH_SEASONS_T, FSH_COLLECTIONS_T, FSH_THEMES_T
-> RFM_SEASONS_T
o
•
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)
o R_FSH_TO_RFM_SEASONS_MD_XPRA
SAP ERP (Retail)
o First Step
▪ R_FSH_S4_SEASONS_MD_MIG
o 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.
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,
Page | 980
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
FSH_SEASONS, FSH_COLLECTIONS, FSH_THEMES, FSH_SEASONS_T,
FSH_COLLECTIONS_T, FSH_THEMES_T, RFM_SEASONS, RFM_SEASONS_T
55.53 S4TWL - 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)
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.
Page | 981
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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" )
55.54 S4TWL - 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.
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
Page | 982
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
55.55 S4TWL - 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.
In SAP S/4HANA the functionality to integrate with SAP AFS is available, but defined
as "not strategic any more". See SAP note 2269324 - Compatibility Scope Matrix for
SAP S/4HANA, on-premise edition
Business Process related information
Move to verticalized fashion processes once available.
Required and Recommended Action
No special actions for the SAP AFS integration scenario is needed when converting from
SAP ERP to SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if Apparel and Footwear integration is used.
This is the case if transaction WAFS is used.
Page | 983
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
55.56 S4TWL - POS Outbound via Idoc WP_PLU
Application Components:
SD-POS, SD-POS-OUT
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).
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
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.
55.57 S4TWL - Valuation in Retail
Application Components:
MM-IM, MM-IM-GF, MM-IM-GF-SAV
Related Notes:
Page | 984
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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,
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 MBEWVKSAL 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
Page | 985
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
field WWGPA (Material group material) not equal blank. If this is the case, that is a good
indicator that value-only articles are used.
55.58 S4TWL - Retail Demand Management Integration
Application Components:
LO-MD, LO-MD-RDM
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
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, onpremise edition .
Business Process related information
Move to other available communcation methods.
Required and Recommended Action
No special actions for Retail Demand Management integration is needed when
converting from SAP ERP to SAP S/4HANA.
How to Determine Relevancy
This Simplification Item is relevant if retail demand management integration is used.
This is the case if transactions RDMCHG RDMINI RDMMAN RDMREO RDMSEL
RDM_S* are used.
Page | 986
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
56 Industry Telecommunications
56.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 RMCA -> Define Basic Settings for Managing Service Data
Page | 987
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
56.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)
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.
Page | 988
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
57 Industry Utilities
57.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.
Page | 989
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Required and Recommended Action(s)
In addition to following the required steps as suggested in the 'Required and
Recommended Action(s)' section of SAP Note 2265093, execute the following two
reports for data conversion:
Report Name
Purpose
REU_CVI_CUST_LINK
Establishes a link between the business partner
and the customer as required by the standard
Customer Vendor Integration (CVI) solution
REU_CVI_EKUN_TO_BUT0ID
Converts the ISU-specific identification fields from
the table EKUN to the table BUT0ID in the system
SAP 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.
However, CVI(Direction ‘Customer/Vendor-to-Business Partner’) can be activated in the
source ECC system before the S/4HANA conversion.
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)
Page | 990
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Other Terms
CVI, ISU
57.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 selfservice 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
Page | 991
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
57.3 S4TWL - SAP Waste and Recycling: Activation
Application Components:
CRM-WA, IS-U-WA, SV-SMG-ICO-IWR, BW-BCT-WA, XXPART-PLG-WAS, XX-EOD-IS-U-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) are released as of
SAP S/4HANA, on-premise Edition 1610 FPS02 or higher. To be able to use SAP Waste
and Recycling, the business functions ISU_WASTE_1, ISU_WASTE_RCI_2,
Page | 992
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 migration strategy could be to
perform the technical upgrade to SAP S/4HANA first, then to activate the
aforementioned business functions, and then to carry out the functional test.
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-PremiseEdition 1610 FPS02 and are on the black list:
EWAEL01
EWAEL02
EWAEL03
EWAGG
EWAGGABR
EWAORDALL
EWASPGCONF
EWAWA02
EWAWA04
Delivery Locks
Visual Control
Reserve Sample
Guarantor Contract
Allocate Bill.Data to Guarantor Cat.
Create Waste Disposal Order
Configuration: Service Product Generator
Weighing Transaction
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
Page | 993
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
57.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
Page | 994
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
57.5 S4TWL - IS-Utilities Settlement Control
Application Components:
IS-U-IN
Related Notes:
Note Type
Note Number
Note Description
Business Impact
12
Individual solution without a specific SAP
Note
Long Text
Solution
Dear customer,
We have provided an individual solution to the problem you reported. Due to the
customer-specific nature of the problem and our solution to it, no SAP Note is available
on SAP Service Marketplace to address your inquiry. Therefore, we have completed your
incident and would request that you confirm it.
Sincerely,
Your SAP Product Support
57.6 S4TWL - 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
Page | 995
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 EDM1
S/4HANA on-premise edition
1511
57.7 S4TWL - 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)
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.
Page | 996
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Following UCES related transaction codes are not available anymore:
EWEBIAC_1_PAY
EWEBIAC_A_PAY
EWEBIAC_A_PAY_CIC
EWEBIAC_ACCT_INFO
EWEBIAC_CALLBACK
EWEBIAC_CH_MD
EWEBIAC_CH_MD_CIC
EWEBIAC_CONS_HIS_CIC
EWEBIAC_CONSUMP_HIST
EWEBIAC_CONTINUE
EWEBIAC_CPUSER
EWEBIAC_ENROLL_CIC
EWEBIAC_ENROLLMEN
EWEBIAC_ENROLLMENT
EWEBIAC_HTMLBILL
EWEBIAC_INFO
EWEBIAC_INFO_CIC
EWEBIAC_LOGIN
EWEBIAC_METER_CIC
EWEBIAC_METER_READ
EWEBIAC_MOVE_IN
EWEBIAC_MOVEOUT
EWEBIAC_PASSWD
EWEBIAC_PASSWD_NEW
EWEBIAC_PREM_SEL_CIC
EWEBIAC_PREMISE_SEL
EWEBIAC_SHOW_PROFIL
EWEBIAC_TEMPLATE
ISS Pay Bills
ISS Direct Debit Mandate
ISS Direct Debit Mandate as ESS
ISS Accounts Information
ISS Initiate Callback
ISS Change Bill Address
ISS Change Bill Address ESS
ISS Consumption Overview in CIC
ISS Consumption Overview
Dummy Entry for Service Usage
Customer Portal - User
ISS Initial Data Creation as ESS
ISS Initial Data Creation
ISS Initial Data Creation
ISS Bill
ISS Accounts Information
ISS Account Information ESS
ISS Internet Account
ISS Meter Reading Entry from CIC
ISS Meter Reading Entry
ISS Move-In
ISS Move-Out
ISS Change Internet Password
ISS Password Forgotten
ISS Premise Selection
ISS Premise Selection
ISS Display Profile Values
ISS Template
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
Page | 997
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
57.8 S4TWL - 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/enUS/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/enUS/a3e19257660b6c10e10000000a441470.html). Please check the documentation for the
availability of the successors.
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
EP01
EP02
Set up stock statistics
Customizing: Transaction Statistics
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.
Page | 998
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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)
Other:
0UC_ISU_CONSUMPT_02
0UC_ISU_CONSUMPTION
0UC_EDM_01
0UC_EDM_02
0UC_SALES_SIMU_02
0UC_SALES_STATS_01
Other Terms
Utilities Information System, UIS
Page | 999
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
57.9 S4TWL - 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.
57.10 S4TWL - 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
Page | 1000
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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
ECBWPP
Marketing: Consumpt. -> Delta Queue
Prepare Extrapolation Indexes
Usage of Loyalty Management is indicated by entries in table ELACC.
57.11 S4TWL - Front Office (EC20)
Application Components:
IS-U
Related Notes:
Note Type
Note Number
Note Description
Business Impact
2270510
S4TWL - Front Office (EC20) and CIC0
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
Description
IS-U Front Office (transaction code EC20) is not available within SAP S/4HANA, onpremise edition 1511.
The CIC Customizing Menu (area menu ISUCC) was removed with SAP S/4HANA, onpremise 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.
57.12 S4TWL - GIS Business Connector
Application Components:
IS-U
Related Notes:
Page | 1001
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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.
57.13 S4TWL - 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
Page | 1002
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
•
•
•
•
•
•
•
•
TEST_UtilitiesConnectionStatusChangeRequestRequest_In
UtilitiesConnectionStatusChangeRequestConfirmation_In
UtilitiesConnectionStatusChangeRequestCancelRequest_Out
UtilitiesConnectionStatusChangeRequestRequest_Out
UtilitiesTimeSeriesBundleItemCreateConfirmation_In
UtilitiesTimeSeriesBundleItemCreateRequest_In
UtilitiesTimeSeriesBundleItemCreateConfirmation_Out
UtilitiesTimeSeriesBundleItemCreateRequest_Out
There is no precise check on the usage of obsolete Enterprise Services. Looking for service messages
of these obsolete enterprise services in the monitoring transactions SXMB_MONI (using Monitor for
Processed XML Messages) and SRT_MONI indicates the usage.
Please check referenced notes 1541831 - UtilitiesConnectionProcessing enterprise services in EHP5 and 1527380 - Deprecated ES, EHP6 for ERP, UtilitiesTimeSeriesProcessing - for detailled
information.
57.14 S4TWL - Central and Eastern European localization for Utility &
Telco
Application Components:
XX-CSC-CZ-IS-U, XX-CSC-BG-IS-U, XX-CSC-GR-IS-U, XX-CSCHU-IS-U, XX-CSC-PL-IS-U, XX-CSC-RO-IS-U, XX-CSC-SI-IS-U, XX-CSC-RU-IS-U, XX-CSC-SK-ISU, XX-CSC-TR-IS-U, XX-CSC-UA-IS-U, XX-CSC-BG-FICA, XX-CSC-CZ-FICA, XX-CSC-GR-FICA,
XX-CSC-PL-FICA, XX-CSC-RO-FICA, XX-CSC-RU-FICA, XX-CSC-SI-FICA, XX-CSC-SK-FICA,
XX-CSC-UA-FICA, XX-CSC-HU-FICA
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
Page | 1003
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
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 AddOn 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':
•
•
Business Function /SAPCE/ISU_LOC_CEE
o Switch /SAPCE/ISU_LOC_CEE_SFWS_02
▪ Switch Package /SAPCE/IU_LOC_CEE_SFWS_02
o Switch /SAPCE/FICA_LOC_CEE_SFWS_02
▪ Switch Package SAPCE/FK_LOC_CEE_SFWS_02
Business Function ISU_UTIL_WASTE
o Switch /SAPCE/ISU_LOC_CEE_SFWS_01
▪ Switch Package /SAPCE/IU_LOC_CEE_SFWS_01
o Switch /SAPCE/FICA_LOC_CEE_SFWS_01
▪ Switch Package /SAPCE/FK_LOC_CEE_SFWS_01
Business Function Set 'TELCO':
•
•
•
•
Business Function /SAPCE/TEL_LOC_CEE
o Switch /SAPCE/FICA_LOC_CEE_SFWS_02
▪ Switch Package /SAPCE/FK_LOC_CEE_SFWS_02
Business Function /SAPCE/TEL_LOC_CEE_HIDDEN
o Switch /SAPCE/ISU_LOC_CEE_SFWS_01
▪ Switch Package /SAPCE/IU_LOC_CEE_SFWS_01
Business Function RM_CA
o
Switch /SAPCE/FICA_LOC_CEE_SFWS_01
▪ Switch Package /SAPCE/FK_LOC_CEE_SFWS_01
Business Process related information
No influence on business processes and custom code.
Required and Recommended Action(s)
Page | 1004
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
Execute related pre-check (see the SAP Note 2314696) on SAP Business Suite startrelease.
Other Terms
S4TWL, S4TC, CEEISUT, Pre-Check Class, SAP IS-UT CEE
Page | 1005
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
58 SAP Ariba
58.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.
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. 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
SAP Product Version
SAP ERP 6.0*
EHP1 FOR SAP ERP 6.0*
EHP2 FOR SAP ERP 6.0*
EHP3 FOR SAP ERP 6.0*
EHP4 FOR SAP ERP 6.0*
EHP5 FOR SAP ERP 6.0*
EHP6 FOR SAP ERP 6.0*
EHP7 FOR SAP ERP 6.0*
EHP8 FOR SAP ERP 6.0
SAP SFINANCIALS 1503
CI-6
CI-7
CI-8
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
CI-9
CI-9
SP1
CI-9
SP2
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Page | 1006
Simplification List for SAP S/4HANA 1809 Initial Shipment Stack
SAP S/4HANA FINANCE 1605
SAP S/4HANA 1511 OnPremise
SAP S/4HANA 1610
SAP S/4HANA 1709
X
X
X
X
X
X
X
X
X
X SP2
HF8
* Note that some integration scenarios require a minimum EHP Version. Refer to the
documentation of your CI Version Xon 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.
1. 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.
2. SAP Ariba delivers the Cloud Integration programs through SAP transport files
within an exclusive namespace registered with SAP. The solution is fully
supported by SAP Ariba as per the Ariba Support policy. However, due to the
nature of transport objects, the programs are considered as customer objects
during upgrade with Software Update Manager. During the upgrade, you have to
ensure that Ariba Objects including table contents are retained. Due to a software
error, Ariba Objects can get deleted during an upgrade. To avoid this, make sure
that note 2402191 is applied in your system.
3. If you want to migrate to S/4HANA or upgrade your S/4HANA system to a
higher product version, the prechecks delivered through notes 2403186 and
2406491 should be downloaded and installed.
Other Terms
Cloud Integration CI-9 CI-8 CI-7 CI-6 Upgrade
Page | 1007