What's New | PUBLIC Document Version: 1.0 – 2021-05-26 What's New in SAP S/4HANA 2020 FPS02 © 2021 SAP SE or an SAP affiliate company. All rights reserved. THE BEST RUN
What's New | PUBLICDocument Version: 1.0 – 2021-05-26
What's New in SAP S/4HANA 2020 FPS02
© 2
021 S
AP S
E or
an
SAP affi
liate
com
pany
. All r
ight
s re
serv
ed.
THE BEST RUN
Content
1 What's New. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Asset Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62.1 Maintenance Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Environment, Health, and Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Finance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Financial Planning and Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2 Accounting and Financial Close. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3 Treasury Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4 Financial Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.5 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4 Manufacturing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.1 Production Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.2 Just-In-Time Supply to Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.3 Quality Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464.4 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5 R&D/Engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.1 Enterprise Portfolio and Project Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.2 Integrated Product Development for Process Industries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6 Enhanced Workflow and Object Support in Change Record. . . . . . . . . . . . . . . . . . . . . . . . . . . .53
7 Sales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.1 Order and Contract Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.2 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8 Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588.1 Service Operations & Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
9 Sourcing and Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .609.1 APIs for Integration with Sourcing and Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.2 Sourcing and Contract Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629.3 Operational Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649.4 Central Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669.5 Procurement Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679.6 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Content
10 Supply Chain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.1 Warehouse Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6910.2 Delivery and Transportation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.3 Simplified Planning Cycle in Forecasting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8810.4 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11 Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9011.1 Business Network Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9011.2 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
12 Cross Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9412.1 Legal Hold Management for Mass Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9412.2 Master Data Governance, Central Governance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9512.3 Situation Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9512.4 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9612.5 Data Quality Management, version for SAP Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9712.6 Behavioral Insights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13 Country/Region Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9913.1 Australia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9913.2 Belgium. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10113.3 Brazil. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10413.4 Chile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11013.5 Colombia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11113.6 Denmark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11213.7 Germany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11313.8 Greece. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11413.9 Hungary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11513.10 India. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11713.11 Mexico. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12013.12 Netherlands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12213.13 New Zealand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12413.14 Poland. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12613.15 Portugal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12713.16 Qatar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12813.17 Singapore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12813.18 Slovakia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13113.19 Spain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13313.20 Sweden. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13713.21 Taiwan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13713.22 Turkey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14013.23 United Kingdom. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
What's New in SAP S/4HANA 2020 FPS02Content PUBLIC 3
14 Industries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14414.1 Consumer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14414.2 Energy & Natural Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15214.3 Financial Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
4 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Content
1 What's New
What's New in SAP S/4HANA provides you with delta information on all new, changed or deleted features of this product. The What's New Viewer provides the same information in an interactive format.
What's New in SAP S/4HANA 2020 FPS02What's New PUBLIC 5
2 Asset Management
2.1 Maintenance Operations
2.1.1 Simplified Management of EAM Functions 17
This business function provides you with enhanced features for processing maintenance orders on the SAP Web UI for Plant Maintenance.
Technical Details
Type New
Functional Localization Not applicable
Scope Item BH1 (Corrective Maintenance), BJ2 (Preventive Maintenance)
Application Component PM (Plant Maintenance)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
For more information about the functions that are included in this business function (LOG_EAM_SIMPLICITY_17), see the related product feature release note Maintenance Orders: Cancelation of System Status "Do not Execute" [page 7].
Related Information
Simplified Management of EAM Functions 17
6 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Asset Management
2.1.1.1 Maintenance Orders: Cancelation of System Status "Do not Execute"
With this feature, you can cancel the status Do Not Execute of a maintenance order from either directly within the order or from the order notification list.
Technical Details
Type New
Functional Localization Not applicable
Scope Item BH1 (Corrective Maintenance), BJ2 (Preventive Maintenance)
Application Component PM (Plant Maintenance)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can now cancel the status Do Not Execute of a maintenance order. You can do so using the change order function or from the order notification list. After setting the status Do Not Execute for a maintenance order, the order is closed, permits are no longer approved, and the corresponding reservation or purchase requisitions are getting a deletion flag. If you now cancel this status, the maintenance order can be changed again, permits can be approved again, and the deletion flag for the same reservation and purchase requisitions is canceled, so that they can also be changed again.
2.1.2 Enterprise Asset Management Part 16
This business function enables you to use several enhancements for maintenance orders and maintenance notifications in Plant Maintenance.
Technical Details
Type New
What's New in SAP S/4HANA 2020 FPS02Asset Management PUBLIC 7
Functional Localization Not applicable
Scope Item BH1 (Corrective Maintenance), BJ2 (Preventive Maintenance)
Application Component PM (Plant Maintenance)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
For more information about the functions that are included in this business function (LOG_EAM_CI_16), see the following product feature release notes:
● Functional Location and Equipment: Additional Display Options for Classification Data [page 8]● List Displays: Standard Export to Spreadsheet Functionality [page 9]● Maintenance Order: Cancelation of System Status "Do not Execute" [page 10]
Related Information
Enterprise Asset Management Part 16
2.1.2.1 Functional Location and Equipment: Additional Display Options for Classification Data
With this feature, you can display more classification information for technical objects in Plant Maintenance.
Technical Details
Type New
Functional Localization Not applicable
Scope Item BH1 (Corrective Maintenance), BJ2 (Preventive Maintenance)
Application Component PM (Plant Maintenance)
8 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Asset Management
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can display up to 200 characteristics in single-level list displays for equipment and functional locations. The option to toggle the display of the characteristics is included in the toolbar. With the display of the characteristics, class assignment indicators are displayed as well which show if a class is assigned to the technical object.
You can navigate directly from the functional location and equipment detail screens to the change documents of the assigned class.
Effects on Customizing
You can use the new sequence number 96 to display 20 characteristics for technical objects in a full screen display in Customizing for Plant Maintenance and Customer Service under Master Data in Plant Maintenance and Customer Service Technical Objects General Data Set View Profiles for Technical Objects .
Related Information
Display of Characteristics and Class Assignment in Enhanced List Editing
2.1.2.2 List Displays: Standard Export to Spreadsheet Functionality
With this feature, you can use the standard export to spreadsheet functionality in maintenance order, notification, functional location, and equipment lists.
Technical Details
Type New
Functional Localization Not applicable
What's New in SAP S/4HANA 2020 FPS02Asset Management PUBLIC 9
Scope Item BH1 (Corrective Maintenance), BJ2 (Preventive Maintenance)
Application Component PM (Plant Maintenance)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can now use the standard single-step export to spreadsheet functionality in single-level lists for functional location and equipment lists as well as for order and notification lists.
NoteYou can choose to revert to the classic export to spreadsheet functionality by using the user parameter EAMCC4_ALV_EXCEL.
Related Information
Working with Lists
2.1.2.3 Maintenance Order: Cancelation of System Status "Do not Execute"
With this feature, you can cancel the status Do Not Execute of a maintenance order directly from within the order and in the corresponding list transactions such as IW32, IW37N, and IW38.
Technical Details
Type New
Functional Localization Not applicable
Scope Item BH1 (Corrective Maintenance), BJ2 (Preventive Maintenance)
Application Component PM (Plant Maintenance)
10 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Asset Management
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can now cancel the status Do Not Execute of a maintenance order in transactions IW32, IW37N, and IW38. After setting the status Do Not Execute for a maintenance order, the order is closed, permits are no longer approved, and the corresponding reservation or purchase requisitions are getting a deletion flag. If you now cancel this status, the maintenance order can be changed again, permits can be approved again, and the deletion flag for the same reservation and purchase requisitions is canceled, so that they can also be changed again.
Related Information
Issuing and Canceling the System Status "Not Executed”
2.2 Environment, Health, and Safety
2.2.1 Environment Management
2.2.1.1 Deprecation of an Environment Management App
The Manage Compliance Requirement Web Dynpro app was deprecated in SAP S/4HANA 2020.
Technical Details
Type Deprecated
Functional Localization Not applicable
Scope Item Not applicable
Application Component EHS-SUS-EM (Environment Management)
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Asset Management PUBLIC 11
Additional Details
You can use the following successor app:
Deprecated App Successor App
Manage Compliance Requirement Web Dynpro Manage Compliance Requirements - Regulations, Permits, Policies (F5038)
Effects on Existing Data
The Manage Compliance Requirement Web Dynpro app is no longer supported and will be deleted from the SAP Fiori launchpad as of 2022. The app may no longer be available by default on the SAP Fiori launchpad. In this case, you can find it in the app finder until it is deleted. We recommend that you switch to the successor app as soon as possible.
Related Information
Manage Compliance Requirements - Regulations, Permits, Policies
2.3 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
12 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Asset Management
3 Finance
3.1 Financial Planning and Analysis
3.1.1 Enhancements for Product Cost Planning
To get you started with financial planning in SAP Analytics Cloud, SAP is delivering the Integrated Financial Planning for SAP S/4HANA Cloud business content.
Product Cost Planning is now extended by the following new stories:
● Product Cost Analytics provides you with KPIs and interactive overview charts of product costs, lot sizes, and lot amounts.
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 13
● Product Cost Reports gives you insight into product costs by plant, product, material, and cost center.
14 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 4RC
Application Component CO-FIO-SAC-PL (SAP Analytics Cloud Planning Content)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Performing Product Cost AnalyticsPerforming Product Cost Reporting
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 15
3.2 Accounting and Financial Close
3.2.1 General Ledger Accounting
3.2.1.1 Deprecated Elements in CDS Views for General Ledger Accounting
With SAP S/4HANA 2020 one or more elements were deprecated in the listed CDS views. SAP may make the deprecated elements unusable usually not earlier that one year after the deprecation. For more information, see the documentation of the individual CDS view.
Technical Details
Type Deprecated
Functional Localization Not applicable
Scope Item J58 (Accounting and Financial Close)
Application Component FI-GL (General Ledger Accounting)
Available As Of SAP S/4HANA 2020
Additional Details
● Accounting Document Item: Operational View (I_OperationalAcctgDocItem)● Accounting Document Item: Operational View (Additional Ledger) (I_AddlLedgerOplAcctgDocItem)● Fiscal Year Period for Ledger (I_FiscalYearPeriodForLedger)● G/L Account Balance (I_GLAcctBalance)● G/L Account Balance Cube (I_GLAcctBalanceCube)● G/L Account Balance Comparison Cube (I_GLAcctBalanceComprnCube)● G/L Account Balance with Flow Measure (C_GLAccountFlow)● G/L Account Line Item Cube (I_GLAccountLineItemCube)● G/L Account Line Item (I_GLAccountLineItem)● Journal Entry (I_JournalEntry)● Journal Entry: Operational View (I_JournalEntryOperationalView)● Journal Entry Item (I_JournalEntryItem)● Journal Entry Item Browser (I_JournalEntryItemBrowser)● Journal Entry Item Cube (I_JournalEntryItemCube)
16 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
● Journal Entry Item Cube - Plan/Actual (I_ActualPlanJrnlEntryItemCube)● Trial Balance (C_Trialbalanceq0001)● Trial Balance Comparison (C_Trialbalanceq0002)● Trial Balance for API (C_TrialBalance)
Effects on Existing Data
We recommend that you switch to the successor elements as soon as possible. The successor elements of deprecated elements are listed in the documentation of the individual CDS view. As key user, you will see tasks in key user extensibility apps for prominent occurrences where the deprecation of CDS view elements makes it necessary to rework your content.
Related Information
Deprecated and Decommissioned CDS ViewsAnalyticsCDS Views for Accounting and Financial Close
3.2.1.2 Accounting Enhancements for Banking
You can use the following features:
● Error Correction and Suspense Accounting○ ECS Automation Dashboard
● Multi Currency Accounting○ Parking of excel upload○ Restatement of open items and fixed assets
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-GL-CU-MCA (Multi Currency Accounting)
AC-INT-ECS (Error Correction and Suspense Accounting)
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 17
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● For the feature ECS Automation Dashboard, the following transactions were added to the SAP Easy Access menu:
○ Accounting Bank Applications Enhancements for Accounting Error Correction and Suspense Acconting Manual Post-Processing Edit ECS Items Dashboard
● For the parking of the excel upload, the transaction Park MCA Excel Upload was added to the SAP Easy Access menu under AccountingBank ApplicationsEnhancements for AccountingMulti Currency AccountingDocument Entry
● For the restatement of open items and fixed assets, the following transactions were added to the SAP Easy Access menu under Accounting Bank Applications Enhancements for Accounting Multi Currency Accounting Periodic Processing Subledger Processing:
○ Restatement Restate Open Items
○ Fixed Assets Restate Fixed Assets
Effects on Customizing
For the feature ECS Automation Dashboard, carry out the following Customizing activities:
● SAP Banking Enhancements for Accounting Error Correction and Suspense Accounting General Settings General Settings for Owner Groups:○ Define ECS Owner Group○ Configure ECS Owner Group○ BAdI: ECS Automation for Owner Group Assignment
● SAP Banking Enhancements for Accounting Multi Currency Accounting Tools BAdI: MCA Excel Check
For the restatement of open items and fixed assets, carry out the following Customizing activities under SAP Banking Enhancements for Accounting Multi Currency Accounting Account Determination:
● Maintain Target Accounts for Open Items Restatement● Maintain Subledgger Adjustment Accounts● Maintain Target Accounts for Fixed Asset Restatement
Related Information
AP/AR Processing Concepts
18 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Fixed Assets MCA Processing ConceptsECS Automation Dashboard
3.2.2 Central Finance
3.2.2.1 Central Management of Open Items in General Ledger
With this feature, when a document is posted or reset in the source system, the relevant open items posted to the G/L accounts are technically cleared automatically in the source system. The corresponding open items replicated to the Central Finance system are still open and you can only manage them in the Central Finance system.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF-INF for source systems and FI-CF-APR for the Central Finance system (Central Finance - Central G/L Management)
Available As Of SAP S/4HANA 2020 FPS2
Effects on Customizing
Two new IMG activities are available in the source system in Customizing of Central Finance (transaction: CFINIMG) under Central Finance: Source System Settings Settings for Central Management of Open Items in General Ledger .
● Activate Central Clearing of G/L Open Items● Define G/L Accounts for Technical Clearing
Related Information
Central Management of Open Items in General Ledger
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 19
3.2.2.2 Outgoing Checks in Central Payment
After Central Payment activation, all outgoing check relevant processes are moved to the Central Finance system. And historical outgoing checks created before Central Payment activation need to be migrated from the source system to the Central Finance system, to ensure the continuity of follow-on outgoing check processes in the Central Finance system.
Technical Details
Type New
New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF-INF for source systems and FI-CF-APR for the Central Finance system (Central Finance - Central Payment)
Available As Of SAP S/4HANA 2020 FPS2
Effects on Customizing
Four IMG activities are available in the Central Finance system in Customizing of Central Finance (transaction: CFINIMG) under Central Finance: Target System Settings Central Payment Handling of Historical Outgoing Checks .
● Define Migration Scope for Historical Outgoing Checks● Migrate Historical Outgoing Checks from Source System to Central Finance● Migration Status Monitor● Delete Migrated Historical Outgoing Checks
Related Information
Outgoing Checks
20 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
3.2.2.3 Replicate Activity Types Manually
With this function, you can manually replicate the master data of activity types from source systems to the Central Finance system. If no key mapping exists for a new activity type, a mapping relationship will be created automatically between the source activity type and the target activity type.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF-CCA (Central Finance - Replication of Cost Center Accounting)
Available As Of SAP S/4HANA 2020 FPS2
Additional Details
To access this program, run transaction CFIN_ACTY_TP_REPL directly in the Central Finance system or go to SAP Easy Access under SAP Menu Accounting Central Finance Manual Transfer Tools Replicate Activity Types Manually .
Effects on Customizing
A new BAdI is available in the Central Finance system in Customizing of Central Finance (transaction: CFINIMG) under Central Finance: Target System Settings BAdIs: Central Finance BAdI: Enhance Processing of Activity Type Replication .
Related Information
Replicate Activity Types Manually
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 21
3.2.2.4 Replicate Material Cost Estimates Manually
With this function, you can manually replicate specific material cost estimates from source systems to the Central Finance system.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF-PCP (Central Finance - Replication of Product Cost Planning )
Available As Of SAP S/4HANA 2020 FPS2
Additional Details
To access this program, run transaction FINS_CFIN_MCE_REPL directly in the Central Finance system or go to SAP Easy Access under SAP Menu Accounting Central Finance Manual Transfer Tools Replicate Material Cost Estimates Manually .
Related Information
Replicate Material Cost Estimates Manually
3.2.2.5 Navigate from Target FI Document to Source EC-PCA Document
When you are displaying an FI document using transaction FB03 in the Central Finance system on SAP GUI, if the FI document is replicated from an EC- PCA document, you can use this function to navigate to its source PCA document.
22 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF-PCA (Central Finance - Replication of EC-PCA Internal Postings)
Available As Of SAP S/4HANA 2020 FPS2
Related Information
Navigate from Target FI Document to Source PCA Document
3.2.2.6 Cross-System Navigation with Smart Link in Fiori Apps (for Cloud Source System)
With the smart link feature, you can navigate from any Fiori app running on your SAP S/4HANA Cloud source system which shows the journal entry number to the Manage Journal Entries app running on the Central Finance system.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1W4 in SAP S/4HANA Cloud
Application Component FI-CF-INF for source systems (Central Finance - Cross-System Navigation)
Available As Of SAP S/4HANA 2020 FPS2 (Central Finance system)
SAP S/4HANA Cloud 2105 (Source System)
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 23
Related Information
Cross-System Navigation
3.2.2.7 Enable Replication of Purchase Orders with Account Assignment Object of Sales Order
With this feature, you can perform accruals calculation in the Central Finance system with sales orders as account assignment on the basis of purchase orders replicated by Accounting View of Logistics Information.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF-AVL (Central Finance - Accounting View of Logistics Information)
Available As Of SAP S/4HANA 2020 FPS2
Additional Details
To use this feature, you need to first implement BAdI BADI_FINS_CFIN_ACCTA in the Central Finance system. With this BAdI, the account assignment for the replicated purchase orders can be changed from source sales order to internal order in the Central Finance system.
You can access this BAdI in the Central Finance system in Customizing of Central Finance (transaction: CFINIMG) under Central Finance: Target System Settings BAdIs: Central Finance.
Related Information
Central Accruals Management
24 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
3.2.2.8 Advanced Compliance Reporting: Additional Country-/Region-Specific Reports
For statutory reporting, you can now additionally use the country-/region-specific reports from Advanced Compliance Reporting in the Central Finance scenario which are listed below in the table in the Additional Details section. For a complete list of statutory reports supported in a country/region in the Central Finance scenario, see here.
Technical Details
Type New
Functional Localization Localized for the countries/regions listed
Scope Item Not applicable
Application Component FI-CF (Central Finance)
Available As Of SAP S/4HANA 2020 FPS2
Additional Details
Country/Region-Specific Statutory Reports in Central Finance
Country/Region Name of Statutory Report
Chile Chile Financial Statement (Balance sheet)
Chile Chile General Ledger
Chile Chile Journal Ledger
Chile Chile Electronic Accounting Books (Partial)
Czech Republic Czech Republic Cash Flow Statement
Czech Republic Czech Republic EC Sales List
Czech Republic Czech Republic Financial Statements
Czech Republic Czech Republic VAT Return
Czech Republic Czech Republic VAT Control Statement (VAT Ledger)
Germany Germany EC Sales List
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 25
Country/Region Name of Statutory Report
Germany Germany Advance VAT Return
Israel Israel VAT Return
Kazakhstan Kazakhstan VAT Return
Malaysia Malaysia Cash Flow Statement
Malaysia Withholdings from royalty and interest paid to non-residents
Malaysia VWithholdings from contract payments made to non-residents
New Zealand New Zealand GST Return (GST101A)
Peru Peru General Ledger
Peru Peru Journal Ledger
Philippines Philippines Expanded Withholding Tax Reporting
Philippines Philippines Final Withholding Tax Reporting - 0619F
Philippines Philippines Expanded Withholding Tax Quarterly Reporting
Philippines Philippines Final Withholding Tax Reporting - 1601FQ
Slovakia Slovakia Cash Flow Statement
Slovakia Slovakia EC Sales
Slovakia Slovakia Financial Statement
Slovakia Slovakia VAT Control Statement
Slovakia Slovakia VAT Declaration
Slovakia Slovakia Withholding Tax Reporting - OZN431
Spain Spain Form 347 - Annual Statement of Transactions
Spain Spain Form 347 - Incoming Cash Transactions
Spain Spain Withholding Modelo-111
Spain Spain Withholding Modelo-216
Spain Spain Withholding Modelo-296
Ukraine Ukraine Financial Statement (Balance sheet, P&L)
26 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Related Information
Advanced Compliance Reporting: Country-/Region-Specific Reports in Central Finance
3.2.2.9 AIF Enhancements: Activate Processing of Replicated FI/CO Data by Source Company Code
With this feature, you can activate and deactivate the processing of replicated FI/CO data in AIF based on source company codes.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component FI-CF (Central Finance)
Available As Of SAP S/4HANA 2020 FPS2
Additional Details
In the IMG activity Assign AIF Runtime Configuration Group to Replication Object you define the AIF (Application Interface Framework) runtime configuration groups that you want to use for processing data replicated to the Central Finance system.
The IMG activity now has two sub-activities in which you can control the processing of the data:
● Under Assign Runtime Configuration to Replication Object, you can specify separate runtime configuration groups for the replication objects available in Central Finance.
● New: Under Assign Runtime Configuration for FI/CO Based on Source Company Code you make settings that are relevant for the replication of FI/CO postings only. You make these settings either for specific source systems or for combinations of source systems and source company codes.
Effects on Existing Data
If you make a setting under Assign Runtime Configuration for FI/CO Based on Source Company Code for a type of posting for which there is also a setting in the activity Assign Runtime Configuration to Replication
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 27
Object the setting you make here overrides the setting in the Assign Runtime Configuration to Replication Object.
If there are no settings for a particular source system (or combination of source system and company code) in this sub-activity, the system defaults to the setting you have defined in Assign Runtime Configuration to Replication Object.
3.2.3 Advanced Compliance Reporting
3.2.3.1 Advanced Compliance Reporting
With this release, the Run Advanced Compliance app and the Define Advanced Compliance app were enhanced.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 1J2 (Advance Compliance Reporting)
Application Component Run Compliance Reports app: FI-LOC-SRF-RUN
Define Compliance Reports app: FI-LOC-SRF-DEF
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Following feature is included in Advanced Compliance Reports:
● Enhancements to Run Level SubmissionRun level submissions are further enhanced so that you can now track the generation and submission status of the run as a whole or at every individual file level, regardless of the type of submission done. The submission status as a whole or at the individual file level is now dependent on the level of response you receive from the government authorities.
● Nested Loop Optimization Report Nested Loop optimization facilitates report generation by improving performance to a significant extent. While enabling nested loop optimization, additional checks have been introduced, which may give errors for existing report definitions. Hence, a new field called Strict Mode has been introduced for these additional checks. While for the new reports this field is already enabled, for the existing reports, this field is always set as false. Strict mode can be enabled by using the Nested Loop Optimization Migration Report.
28 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
3.3 Treasury Management
3.3.1 Cash and Liquidity Management
3.3.1.1 Enhancement for Cash Pool Transfer Report
In addition to actual bank transfers that have been confirmed by bank statements, you can now also view bank transfers for which payments have been made but not yet confirmed by banks (cash in transit) in the Cash Pool Transfer Report app.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 2U8 (Intercompany Process for Cash Concentration)
Application Component FIN-FSCM-CLM-COP (Cash Operations)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Cash Pool Transfer Report
3.3.1.2 Payment Collection in Cash Concentration and Bank Transfers
Payment collection is now supported in the Manage Cash Concentration app, the Make Bank Transfers app, and the Make Bank Transfers - Create with Templates app.
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 29
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 2U8 (Intercompany Process for Cash Concentration)
Application Component FIN-FSCM-CLM-COP (Cash Operations)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Unlike regular payment transactions, payment collections are initiated by a creditor via a bank (the creditor bank) by sending a payment collection message to the debtor's bank. Money is then collected from the debtor bank as instructed by the creditor bank.
In payment collection cases, the following fields may have different meanings compared against regular payment transactions:
● Paying bank account / paying house bank account / paying company code: The bank account / house bank account / company code from which a payment transaction is initiated. In a regular payment transaction, it is the bank account that pays out. However, in a payment collection, it is the bank account that collects money.
● Receiving bank account / receiving house bank account / receiving company code: The bank account / house bank account / company code to which a payment transaction is carried out. In a regular payment transaction, it is the bank account that receives money. However, in a payment collection, it is the bank account that pays out.
You can tell from the payment method whether it is a regular payment or a payment collection:
● When an outgoing payment method is used, this indicates that the transfer is a regular payment transaction.
● When an incoming payment method is used, this indicates that the transfer is a payment collection.
Effects on Customizing
To make payment collections, make sure that you have defined proper incoming payment methods for the bank accounts involved in the bank transfers.
30 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
3.3.2 Treasury and Risk Management
3.3.2.1 Hedge Management and Accounting
3.3.2.1.1 Hedge Management and Accounting for Cross-Currency Hedging
With this feature, you can use Hedge Accounting in a hedging area with cross-currency hedging enabled (Hedging Area: Main Data - Risk-Free Currency set to Currency Defined by the Source). In addition, the Hedge Management Cockpit offers termination and dedesignation requests for hedging areas allowing cross-currency hedges.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1X1 (Foreign Currency Risk Management), 2RW (Side-by-Side Extensibility for SAP S/4HANA Cloud), 2UF (Hedge Accounting for FX Swap - Group Ledger IFRS), 3X1 (Hedge Accounting for FX Forward - Local GAAP), 3X2 (Hedge Accounting for FX Option - Local GAAP)
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● To activate cross-currency hedging, you must create a new hedging area using the Display Hedging Area app. Here go to Main Data Risk-Free Currency and choose the option Currency Defined by the Source. This enables the extraction of cross-currency exposures from Exposure Management 2.0.
NoteYou cannot activate cross-currency hedging in a hedging area that already exists.
Cross-currency hedging only works with FX hedge requests. Further, it supports the instruments FX Spot, FX Forward, and FX NDF.
● When you take a snapshot using the Take Snapshot app, exposure items based on your cross-currency exposures are created.
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 31
○ The Take Snapshot app now has two date fields:○ The Extraction Date is the key date in your local time zone. You can only back-date it for the first
snapshot; after that, it must always the current date.○ The Snapshot Date is the key date in the system time zone and it is the business-relevant date. It is
filled automatically. This field only appears if you acticate the option Day Reference. This option is helpful for back-dated initialization of the hedge management process.
● The created exposure items are shown in the Hedge Management Cockpit app. The table shows the target currency, risk currency and company code currency.○ The Target Currency is the currency used to hedge the exposure.○ The Risk Currency is the currency of the exposure.○ The Company Code Currency is local currency of the company code.
● You can activate Hedge Accounting by selecting the Hedging Area indicator under Main DataIntegration .○ On the Hedge Accounting I tab, the tables Designation Activation and Designation Splitting have been
enhanced to capture the combination of risk currency and target currency.Automated designation is executed based on the currency combination maintained here.
○ The hedging relationships of cross-currency hedges follow the same processes and calculation methods as hedging relationships of non-cross-currency hedges.The NPV and the hedge accounting key figures of the FX transactions (hedging instruments) and the hypothetical derivatives are calculated in the local currency of your company code.
○ The Hedging Relationship tab of the Manage Hedging Relationships app has been enhanced by the new field Target Currency. The target currency is the currency in which the exposure amounts in risk currency are transferred/hedged by the hedging instrument.
● The Hedge Management Cockpit now supports the calculation and the display of all key figures for the analysis items of hedging areas allowing cross-currency hedges. For more information, see also Key Figures in the Hedge Management Cockpit
● You can create dedesignation requests and termination requests for cross-currency FX transactions in the Hedge Management Cockpit.
Related Information
Hedge Management of Net Open Exposures (FX Risk)Hedging Area: Main DataHedging Area: Hedge Accounting IManage Hedging Relationships: Hedging Relationship Detail
3.3.2.1.2 Hedging with Local Currency as Risk Currency
With this feature, you can set a company code's local currency as the risk currency for a hedging area. This setting works for hedging areas with cross-currency hedging enabled.
32 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1X1 (Foreign Currency Risk Management), 2RW (Side-by-Side Extensibility for SAP S/4HANA Cloud), 2UF (Hedge Accounting for FX Swap - Group Ledger IFRS), 3X1 (Hedge Accounting for FX Forward - Local GAAP), 3X2 (Hedge Accounting for FX Option - Local GAAP)
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
To set the local currency as the risk currency:
1. Open your hedging area in the Define Hedging Area app.2. On the Currencies tab, define your hedging-relevant currencies (risk currencies). This way, exposures with
the local currency as the risk currency are extracted during the snapshot process and displayed in the Hedge Management Cockpit so that you can create hedge requests for these exposures.
3. Go to Hedge Accounting I Designation Activation . Here you can set a company code's local currency as the risk currency for this hedging area and choose a (risk-free) target currency.
Related Information
Hedge Management of Net Open Exposures (FX Risk)Hedging Area: Currencies
3.3.2.1.3 Automated Hedge Request Creation for Cross-Currency Hedging
With this feature, you can create automated hedge requests in the Hedge Management Cockpit for exposure items that belong to hedging areas with cross-currency hedging enabled.
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 33
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1X1 (Foreign Currency Risk Management)
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
In the Hedge Management Cockpit, you can now choose the action Automated Request Creation to create automatic hedge requests for cross-currency exposures. The instrument categories supported are FX forwards and NDFs. This feature now also works for hedging areas with the option Currency Defined by the Source (cross-currency hedging) enabled.
If cross-currency hedging is enabled, you must define the risk currency / target currency pairs for hedge requests in the Hedge Request Settings section on the FX Hedge Request tab in the Define Hedging Area app.
Related Information
Hedge Management of Net Open Exposures (FX Risk)Hedging Area: Main DataTriggering the Creation of Automated FX Hedge Requests
3.3.2.1.4 Value Date Shift of Hypothetical Derivative due to Date Shifts by New Bank Holidays
You can shift the dates (such as the value date, fixing date, and expiry date) of a financial transaction that is already used as a hedging instrument in a hedging relationship to a later or previous working day. The change made to the date in the financial transaction causes a change in the dates of the affected hedging relationships. The value date of the hypothetical derivative (HD) is adjusted if the end of term of the HD (value date for forwards and non-deliverable forwards, exercise date for options) is before the new dedesignation date. In this case, the hypothetical derivative would no longer be processed at dedesignation, which would lead to significant ineffectiveness. Therefore, in this case, the term end date of the HD is shifted to the new dedesignation date (the fixing date or value date of the underlying may also be shifted in parallel). If this is not the case, the value date remains unchanged, that is, it remains as it was determined based on the exposure representation.
34 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1X1 (Foreign Currency Risk Management), 2RW (Side-by-Side Extensibility for SAP S/4HANA Cloud), 2UF (Hedge Accounting for FX Swap - Group Ledger IFRS), 3X1 (Hedge Accounting for FX Forward - Local GAAP), 3X2 (Hedge Accounting for FX Option - Local GAAP)
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Change of Hedging Instrument
3.3.2.2 Balance Sheet FX Risk Overview - Based on Snapshots
This app provides an overview of hedge management of balance sheet FX risk based on snapshot data by displaying the total net open amount in the different transaction currencies and the contributing key figure types Net Exposure of Snapshot, Hedged Amount, and Open B/S Hedge Request of Snapshot.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1X1 (Foreign Currency Risk Management)
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 35
Related Information
Hedge Management of Balance Sheet FX RiskBalance Sheet FX Risk Overview - Based on Snapshots
3.3.2.3 CDS Views in Treasury and Risk Management
With this feature, some new CDS views are available in Treasury and Risk Management. Using released CDS views as a basis, you can create your own query views. Released CDS query views can be used by any tool that supports CDS views, such as the SAP Analysis for Microsoft Office, Design Studio, SAP Lumira, or SAP Analytics Cloud.
Technical Details
Type Changed
Functional Localization Not applicable
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● Fin. Trans.: Histl/Fcstd Fee Amt - Query (C_FinTransFcstHistlFeeQry)● Fin Trans Histl Fcst Fee - Cube (I_FinTransHistlFcstFeeCube)● Financial Transaction Amount - Query (C_FinTransAmtQry)● Fin. Trans. Amt on Single Date - Query (C_FinTransSingleDayAmtQry)
Related Information
CDS Views for Treasury and Risk Management
36 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
3.3.3 Payments and Bank Communications
3.3.3.1 Two-Factor Authentication
With this release, you can use two-factor authentication with IAS in the BNK_APP transaction.
Technical Details
Type New
Functional Localization Not applicable
Scope Item J78 (Advanced Cash Operations)
Application Component FIN-FSCM-BNK (Direct Bank Communication)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can activate the two-factor authentication for the processing of payment batches with the Customizing activity Specify Optional User Authentication. You find it under Financial Supply Chain Management Bank Communication Management Basic Settings .
3.3.3.2 Advanced Payment Management
3.3.3.2.1 Regulatory Reporting and Structured Remittance Information in Payment Apps
This feature enables you to maintain or display the information about regulatory reporting and structured remittance. The following Fiori apps available to payment specialists have been extended with the additional information as follows:
● Create Payments app allows you to enter these details during the manual creation of a payment● Manage Payments app displays the information coming either from other (SAP or non-SAP) systems or
from a manual creation
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 37
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4MT (Advanced Payment Management)
Application Component FIN-FSCM-PF (Payment Factory)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Create PaymentsManage Payments
3.3.3.2.2 Automatic Validation and Adjustment of Due Dates with Reference to Cut-Off Times
This feature enables you to validate and adjust due dates automatically for both inbound and outbound payments by considering cut-off times.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4MT (Advanced Payment Management)
Application Component FIN-FSCM-PF (Payment Factory)
Available As Of SAP S/4HANA 2020 FPS02
38 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Additional Details
The automatic validation and adjustment of payment due dates work as follows:
● For inbound process, the validation takes place during inbound processing of a payment within the Payment Factory and it also considers the internal cut-off time agreed with the sending subsidiary. A payment with a due date in the past can be handled with one of the following options:○ Payment will be updated to the next possible date by considering a defined calendar○ Exception handling will be triggered that leads to a rejection or manual repair
● For outbound process, the validation checks if a payment can be executed in time considering bank's cut-off time and lead time. In case the due date cannot be met, the payment can be handled with one of the following options:○ Search will be done to find another payment agreement which allows to meet the due date considering
cut-off times○ Due date will be adjusted to the next possible date by which the payment due date is reachable○ Exception handling will be triggered that leads to a rejection or manual repair
Whenever a due date is adjusted, respective Cash Management entries will be updated.
Related Information
Manage PaymentsClearing AgreementCross Item ChecksRecipient Item Checks
3.3.3.2.3 Enhancement for Country/Region-Specific Payment Formats
The country/region-specific payment formats have been extended with standardized mappings and sorting of transactions according to definitions in the payment format trees. In addition, you can now configure custom mappings from Advanced Payment Management structures to outbound mapping structures to simplify outbound format creation using the same format tree for all payment sources.
Technical Details
Type Changed
Functional Localization Not applicable
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 39
Scope Item 4MT (Advanced Payment Management)
Application Component FIN-FSCM-PF (Payment Factory)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
File HandlerOutput ManagerDMEE
3.3.3.2.4 Enhancement for Compliance with File Handling between Subsidiary and Central Payment Factory
With this enhancement, payment files placed by a subsidiary onto a defined file directory can be encrypted. This ensures that sensitive payment data cannot be accessed by unauthorized parties. During upload, files are decrypted and imported into the central Payment Factory. On application level, sensitive data can be masked to prevent access to detailed payment data such as beneficiary details of salary payments accessed by payment specialists without authorization.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 4MT (Advanced Payment Management)
Application Component FIN-FSCM-PF (Payment Factory)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Directory Import
40 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
3.3.3.2.5 Intra-Day Cash Reconciliation within Payment Factory
Cash Management records created out of a Payment Factory represent the expected bank processing options regarding dates, amounts and granularity of postings. Depending on the Batch Booking indicator of a payment, Cash Management entries will be created either on single transaction level or on batch level. This can be based on the information coming from the subsidiary or can be defined based on the settings for the payment agreement determined for a payment. This feature enables you to perform intra-day cash reconciliation for these payments by matching the incoming intra-day account statements against the corresponding memo records.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4MT (Advanced Payment Management)
Application Component FIN-FSCM-PF (Payment Factory)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Clearing Agreement
3.4 Financial Operations
3.4.1 Extended Data Medium Exchange Engine
This feature enables you to use enhanced functions in the Extended Data Medium Exchange (DME) Engine.
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 41
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item J60 (Accounts Payable), J59 (Accounts Receivable), BFB (Basic Cash Operations), 1X3 (Interest Rate Derivatives Management), 1X1 (Foreign Currency Risk Management), 1WV (Debt and Investment Management), 4MT (Advanced Payment Management), J78 (Advanced Cash Operations)
Application Component CA-GTF-CSC-DME (Data Medium Exchange Engine)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The Extended Data Medium Exchange (DME) Engine has been enhanced with the following features:
● For the DMEE Tree: Properties node, on the Format Attributes tab, the Field Type field label has been changed to Field Value Positioning.
● On the Attributes tab for nodes, the new conversion rule LHEBR is available for selection from the Conversion Function field, which allows you to reverse the order of characters and words for Hebrew text and align the text to the right.
Related Information
Extended Data Medium Exchange Engine
3.4.2 Receivables Management
3.4.2.1 Bank Statement Processing
3.4.2.1.1 Deprecated Apps in Bank Statement Processing
The Upload Bank Statements (FF_5) and Upload Bank Statements - Using Format Selection (FF.5) apps, which are accessible on the SAP Fiori launchpad via the App Finder, have been deprecated. The apps will be deleted with SAP S/4HANA 2021. We recommend that your users switch to using the Manage Incoming Payment Files app as soon as possible.
42 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Finance
Technical Details
Type Deprecated
Functional Localization Not applicable
Scope Item J59 (Accounts Receivable)
Application Component FI-FIO-AR (Fiori UI for Accounts Receivable)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Existing Data
The Manage Incoming Payment Files app is the successor of the Upload Bank Statements (FF_5) and Upload Bank Statements - Using Format Selection (FF.5) apps. The Upload Bank Statements (FF_5) and Upload Bank Statements - Using Format Selection (FF.5) apps are no longer supported and will be deleted from the SAP Fiori launchpad as of SAP S/4HANA 2021. The app may no longer be available by default on the SAP Fiori launchpad. In this case, you can find it in the app finder until it is deleted. We recommend that you switch to the successor app as soon as possible.
Related Information
Manage Incoming Payment Files
3.5 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
What's New in SAP S/4HANA 2020 FPS02Finance PUBLIC 43
4 Manufacturing
4.1 Production Planning
4.1.1 Shortage with Reference to Safety Time
With this feature you can use new Customizing settings in the material shortage profile.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item J44 (Material Requirements Planning)
Application Component PP-MRP (Material Requirements Planning)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Two new threshold types are available in the material shortage profile. These threshold types determine the colors used in the Stock Availability column of the Monitor Material Coverage - Net Segments and Monitor Material Coverage - Net and Individual Segments apps. The column displays a chart that shows the stock availability of a selected material within the horizon you select.
A new calculation of the colors of the Stock Availability chart is only done for days that have a supply or demand. Otherwise the color stays like on the day before.
Effects on Existing Data
One of the following settings must be made in the material master:
● Safety time (complete days)● Material shortage profile (which has the relevant threshold type, see below) (days with decimals)
44 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Manufacturing
Effects on Customizing
Two new threshold types are available in the material shortage profile. You find this Customizing under Production Material Requirements Planning Apps for Material Requirements Planning General SettingsDefine Material Shortage Profiles :
● Avail.Qty Below Zero with Days Coverage● Avail.Qty Below Safety Stock with Days Coverage
The chart displays the colors as follows, depending on the material shortage profile:
● Avail.Qty Below Zero with Days Coverage○ Stock < 0: red○ 0 <= stock < dynamic safety stock: yellow○ Dynamic safety stock <= stock: green
● Avail.Qty Below Safety Stock with Days Coverage○ Stock < dynamic safety stock: red○ Stock >= dynamic safety stock: green
Related Information
Monitor Material Coverage - Net and Individual SegmentsMonitor Material Coverage - Net Segments
4.2 Just-In-Time Supply to Customer
With this release, the following new feature has been included:
● Manage JIT Packing GroupsYou can view the packing groups created for sequenced JIT calls and also monitor their progress and status as further processing takes place.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 2EM (Just-In-Time Supply to Customer)
Application Component LE-JIT-S2C
What's New in SAP S/4HANA 2020 FPS02Manufacturing PUBLIC 45
Available As Of SAP S/4HANA 2020 FPS02
Related Links
For more information, refer to the product documentation at https://help.sap.com under SAP S/4HANAManufacturing Production Operations Just-In-Time (JIT) Supply to Customer .
4.3 Quality Management
4.3.1 APIs for Reading Inspection Methods and Master Inspection Characteristics
The following OData services are now available to read quality-related master data:
● Master Inspection Characteristic – Read (API_MASTERINSPCHARACTERISTIC_SRV)● Inspection Method – Read (API_INSPECTIONMETHOD_SRV)
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1E1 (Quality Management in Discrete Manufacturing), 1FM (Quality Management in Procurement), 1MP (Quality Management in Sales), 1MR (Quality Management in Stock Handling)
Application Component QM-PT-BD (Basic Data)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Master Inspection Characteristic - ReadInspection Method - Read
46 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Manufacturing
4.3.2 API for Inspection Planning
With this OData API, you can create, read, update, and delete an inspection plan and its objects.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 1E1 (Quality Management in Discrete Manufacturing), 1FM (Quality Management in Procurement), 1MP (Quality Management in Sales), 1MR (Quality Management in Stock Handling)
Application Component QM-PT-IP (Inspection Planning)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Inspection Plan
4.3.3 Change Record Integration
With this feature you can track changes in inspection plans using the change record function in Change Management (PLM-CR).
See also SAP Notes 3033633 and 3033685 .
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
What's New in SAP S/4HANA 2020 FPS02Manufacturing PUBLIC 47
Application Component QM-PT-IP (Inspection Planning)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Configuration
The relevant configuration settings for inspection plans are explained in Customizing for Quality Management under Environment Central Functions Change Record Integration.
Related Information
Changes to Inspection Plans
4.4 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
48 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Manufacturing
5 R&D/Engineering
5.1 Enterprise Portfolio and Project Management
5.1.1 SAP Portfolio and Project Management
5.1.1.1 Attribute Synchronization
The INM_EX_PPM_CPM_ATTR_SYNC enhancement spot lets you synchronize attributes between an item and a commercial project. Implement INM_EX_PPM_CPM_ATTR_SYNC_BADI to modify the synchronization parameters. Use this BAdI to:
● Override mappings maintained in the customizing activity SAP Portfolio and Project ManagementPortfolio Management Global Customizing Portfolio-Independent Settings Map Item Type to Project or PS or Commercial Project Field Mapping for Attribute Synchronization
● Override source object values
The source object is either a portfolio item or a commercial project. The modified source object values synchronize with target object values based on the mapping for attribute synchronization. You also have the option to edit the object values as per the business scenario.
Note● Ensure the data types are compatible for synchronization of source and target fields before updating
the attributes in the BAdI.● If no active BAdI implementation is available, the source object values synchronize with the target
object based on the mappings maintained in SAP Portfolio and Project Management Portfolio Management Global Customizing Portfolio-Independent Settings Map Item Type to Project or PS or Commercial Project Field Mapping for Attribute Synchronization .
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component PPM (Porfolio and Project Management)
What's New in SAP S/4HANA 2020 FPS02R&D/Engineering PUBLIC 49
Available As Of SAP S/4HANA 2020 FPS02
Effects on Existing Data
Consider that you have enabled the integration of portfolio items and commercial projects with the necessary customization. The attribute synchronization for any changes made in the existing items and the commercial projects happens after the BAdI implementation is activated.
Effects on Customizing
You can find the complete technical details about the standard settings from the documentation of the BAdI in the SPRO setting: SAP Portfolio and Project Management Portfolio Management Business Add-Ins and Customer Includes BAdI: Attribute Synchronization during CPM Integration .
Related Information
Integration with Commercial Project Management
5.1.1.2 Risk Score Calculation
Use PPM_EX_RISK_SCORE_CALC_BADI from portfolio and project management to calculate risk values and display it as a custom field on the user interface. Build a custom logic to determine custom risk score(s) based on the risk(s) associated to portfolio item or projects.
The BAdI is
● Not active in the standard system. If no active BAdI implementation is available, then the risk score is not calculated for the portfolio item.
● Designed for multiple uses● Filter dependent. You can set the filters based on OBJECT_TYPE for portfolio items (RIH) or project (DPO)
.
50 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
R&D/Engineering
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component PPM (Porfolio and Project Management)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Existing Data
After enabling the integration of risk management with the necessary customization, you can view the Risk Management option on the Item Overview screen and Project screen. The score calculation for any changes made in the existing risks happens after the BAdI implementation is activated.
Refresh item overview or project screen to view risk score values mapped to the custom fields from portfolio items or projects.
Effects on Customizing
You can find the complete technical details about the standard settings (filters, single or multiple uses) from the documentation of the BAdI in the SPRO setting: SAP Portfolio and Project Management Common Functions Risk Management BAdI: Risk Score Calculation .
You can also refer the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
In the standard system, the item types having an associated risk profile ID can be used for risk management integration.
Related Information
Integration with Risk Management
What's New in SAP S/4HANA 2020 FPS02R&D/Engineering PUBLIC 51
5.2 Integrated Product Development for Process Industries
5.2.1 OData API: Product Specification Composition Configuration
The Product Specification Composition Configuration API has been enhanced to read the description of composition types. The description reads the Value Assignment Type (VAT) description for a composition type. The description of VAT's can be retrieved via the API in multiple languages.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 1QA (Specification Management for Recipes)
Application Component PLM-WUI-RCP-SPE (Specification Management)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Customizing
The following Customizing entry supports the enhanced service interface: Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Specification ManagementSpecification Additional Information for Value Assignment Specific Settings for Recipe DevelopmentDefine Settings for Specification APIs .
There is no standard content for this Customizing, therefore you have to fill in the values. Consult the documentation of the Customizing entry for more information.
Related Information
Product Specification Composition Configuration - Read
52 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
R&D/Engineering
6 Enhanced Workflow and Object Support in Change Record
With this feature, Change Record now covers new business objects and offers enhanced workflow handling.
Additional Details
Change Record is available for the following objects:
● Master recipe● Inspection plan● Production routing
For production routing, Change Record now supports processing status as well.
You can also adjust the expected completion date of a change record without having to make the same settings in the change master. The Valid From date of the change number is updated automatically, if synchronization is set in Customizing for the change record type.
An agent overview for process route tasks is available, as well as an enhanced list of supported change objects in the Change Record API.
Effects on Customizing
To make the relevant settings, see the Customizing activities under Logistics - General Product Lifecycle Management (PLM) Change Record.
Related Information
Change Management (PLM-CR)
What's New in SAP S/4HANA 2020 FPS02Enhanced Workflow and Object Support in Change Record PUBLIC 53
7 Sales
7.1 Order and Contract Management
7.1.1 Price Management
7.1.1.1 Manage Prices - Sales
This app now offers you another option for data export. This option allows you to export not only field IDs but also field descriptions to spreadsheets. The descriptions can facilitate your understanding of the exported fields. Please be noted that this export option could take more time due to the increased data volume. Also, exporting descriptions of custom fields is not possible.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item BD9
Application Component SD-MD-CM (Conditions)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Manage Prices - Sales
7.1.2 Sales Order Management and Processing
7.1.2.1 Mass Change of Sales Documents
You can now make changes to multiple documents of a sales document category at a time. The updates are scheduled in the form of one or more jobs which run in the background.
54 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sales
You can make changes to sales documents of the following categories:
● Sales orders● Sales contracts● Sales scheduling agreements● Customer returns● Credit memo requests● Debit memo request
Technical Details
Type New
Functional Localization Not applicable
Scope Item BKK (Sales Order Fulfillment Monitoring)
Application Component SD-SLS-MCC (Mass Change of Sales Documents)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● This app has a template for situation handling that informs users who triggered the jobs about the job completion status.
● This app also supports extensibility.● You can display job details, reschedule failed jobs, and mark failed jobs as completed in the Monitor Mass
Changes of Sales Documents app.
Effects on System Administration
● The new app Mass Change of Sales Documents is part of the new business catalog Sales - Mass Change of Sales Documents (SAP_SD_BC_MCC_SLSDOC), which has been added to the internal sales representative (SAP_BR_INTERNAL_SALES_REP) business role.
● You can delete staging records in the Mass Change of Sales Documents app by using the Deletion of Staging and Job Table Entries for Completed Jobs report (SD_MCC_SDOC_REQUEST_DELETION). You can find the report using transaction SE38.
What's New in SAP S/4HANA 2020 FPS02Sales PUBLIC 55
Effects on Customizing
You can define settings for parallel processing for the Mass Change of Sales Documents app in Customizing under Sales and Distribution Sales Sales Documents Define Parallel Processing for Mass Change of Sales Documents .
Related Information
Mass Change of Sales DocumentsApp Extensibility: Mass Change of Sales Documents (Key User)Situation Template: Mass Change of Sales Docs: Jobs CompleteMonitor Mass Changes of Sales Documents
7.1.2.2 Set Up Email Notifications for Approval Workflows
When workflows are set up correctly, both approval requesters and approvers receive notifications and tasks in the My Inbox app. They can now also be notified through automated emails in approval workflows for sales orders in their internal system.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item BD9 (Sell from Stock)
Application Component SD-SLS (Sales)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Set Up Email Notifications for Approval Workflows
56 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sales
7.1.3 Claims, Returns, and Refund Management
7.1.3.1 Approval Workflows for Credit Memo Requests
The creation and management of approval workflows for credit memo requests using the obsolete method in the Manage Sales Document Workflows app is planned to be deprecated with SAP S/4HANA 2021. We recommend to switch to the new method that works the same way as for other sales document categories.
Technical Details
Type Deprecated
Functional Localization Not applicable
Scope Item BKL (Invoice Correction Process with Credit Memo), 1EZ (Credit Memo Processing)
Application Component SD-SLS (Sales)
Available As Of SAP S/4HANA 2020 FPS02
Effects on System Administration
Please make sure to check whether you're using the deprecated method for approvals of credit memo requests. If that is the case, please recreate the active workflows using the new method, deactivate the old ones, and activate the new ones within the next release.
Related Information
Manage Sales Document Workflows
7.2 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
What's New in SAP S/4HANA 2020 FPS02Sales PUBLIC 57
8 Service
8.1 Service Operations & Processes
8.1.1 Service Order Management
8.1.1.1 Counters and Readings for Service Confirmations
When you edit a service confirmation, you can display all counters assigned to the reference objects (equipment and functional location) in the service confirmation. You can view the details of counters and readings, for example, counter, counter unit, last reading, last reading date, last reading time, and measurement document. You can also use one click action to navigate to the Create Measurement Document app and create a new reading for a piece of equipment or a functional location.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 3D2 (Service Order Management and Monitoring)
Application Component CRM-S4-SRV (Service Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Counters and readings are hidden by default.
Related Information
Service Confirmations
58 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Service
8.1.1.2 OData API: Service Confirmation (A2X)
New fields have been added to the OData Service Confirmation (A2X)
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 3D2 Service Order Management and Monitoring
Application Component CRM-S4-SRV (Service Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The following fields have been added:
● Transaction valuation type (SrvcTransactionValuationType)● Transaction charge type (ServiceTransactionChargeType)
This API is available on the SAP API Business Hub (https://api.sap.com ).
Related Information
Service Confirmation (A2X)
What's New in SAP S/4HANA 2020 FPS02Service PUBLIC 59
9 Sourcing and Procurement
9.1 APIs for Integration with Sourcing and Procurement
9.1.1 SOAP API: Request for Quotation - Receive Confirmation (Inbound)
This service enables you to receive confirmations after a request for quotation created in your SAP S/4HANA system was transferred to an external sourcing system. Confirmations sent by the external sourcing system can include success confirmations or error messages.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4BL (Sourcing with SAP Ariba Sourcing, OBL (PSM: Sourcing with SAP Ariba Sourcing)
Application Component MM-PUR-RFQ (RFQ/Quotation)
Available As Of SAP S/4HANA 2020 FPS02
This API is available on the SAP API Business Hub (https://api.sap.com ).
Related Information
Request for Quotation - Receive Confirmation (Inbound)
9.1.2 SOAP API: Supplier Quotation - Send Confirmation (Outbound)
This service enables you to send confirmations from your SAP S/4HANA system after a supplier quotation created in an external sourcing system was received.
60 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sourcing and Procurement
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4BL (Sourcing with SAP Ariba Sourcing, OBL (PSM: Sourcing with SAP Ariba Sourcing)
Application Component MM-PUR-RFQ (RFQ/Quotation)
Available As Of SAP S/4HANA 2020 FPS02
This API is available on the SAP API Business Hub (https://api.sap.com ).
Related Information
Supplier Quotation - Send Confirmation (Outbound)
9.1.3 Purchase Info Record Events
Two purchase info record events Created and Changed are now available to inform remote systems about created and changed purchase info records.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 2XT
Application Component MM-PUR-PO (Purchasing Info Record Events)
Available As Of SAP S/4HANA Cloud 2105
Additional Details
● Created: This event is raised when a purchase info record instance has been created.
What's New in SAP S/4HANA 2020 FPS02Sourcing and Procurement PUBLIC 61
● Changed: This event is raised when a purchase info record instance has changed, for example when there is a change in the status of the purchase info record.
This event is available on the SAP API Business Hub (https://api.sap.com )
Related Information
Purchase Info Record Events
9.2 Sourcing and Contract Management
9.2.1 Automation of Source-to-Pay with Ariba Network (42K)
This scope item now supports the following features:
● Purchase order confirmations for enhanced limit items● Service entry sheet revisions● Transfer of additional fields in purchase orders
Technical Details
Type New
Functional Localization Not applicable
Scope Item 42K (Automation of Source-to-Pay with Ariba Network)
Application Component BNS-INT-ARI (Ariba Integration with SAP S/4HANA)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Purchase Order Confirmations for Enhanced Limit ItemsPurchase order confirmations are now supported as follow-on documents for material items, lean service items, and enhanced limit items. This means you can create mixed purchase orders with different item types, for example, material items and enhanced limit items, and transfer them to Ariba Network. Suppliers can then send purchase order confirmations to SAP S/4HANA and create ship notices and service entry sheets as required.
62 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sourcing and Procurement
Service Entry Sheet RevisionsIf you detect inconsistencies or errors during the review of a service entry sheet, you can now create a revision of this service entry sheet and transfer it to Ariba Network. The relevant supplier can then create a new service entry sheet and send it back to SAP S/4HANA, where the original service entry sheet is replaced.
Transfer of Additional Fields in Purchase OrdersThe following purchase order fields are now transferred to Ariba Network on header level:
● Your ReferenceYou can use this free-text field to specify the internal reference ID of the supplier.
● Our ReferenceYou can use this free-text field to specify your own internal reference ID.
The following purchase order fields are now transferred to Ariba Network on item level:
● Estimated PriceYou can use this field to indicate that the specified price is an estimated price. This can be useful for materials or services with varying prices. For estimated prices, a greater price tolerance is tolerated during invoice verification.
● Print PriceYou can use this field to indicate that the specified price is a print price and should not be visible to the supplier. This can be useful for materials or services with varying prices or with prices that are still unknown when the purchase order is created. The print price is masked when purchase orders are sent to Ariba Network.
NoteThe Estimated Price and Print Price fields are only available in the Create Purchase Order (Advanced) app.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
What's New in SAP S/4HANA 2020 FPS02Sourcing and Procurement PUBLIC 63
Related Information
Automation of Source-to-Pay with Ariba Network (42K)
9.3 Operational Procurement
9.3.1 Self-Service Requisitioning
9.3.1.1 Define Settings for Creation of Reservation
With this configuration, you can now do the following:
● Select the option Check Unrestricted Stock Only if you want the stock availability to be determined based on only the stock that is available for unrestricted use. In this case, the checking rule is bypassed.
● In the connected system, enable the creation of automatic reservations corresponding to Central Requisitioning.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 18J (Requisitioning), O8J (Requisitioning), 1XI (Central Requisitioning)
Application Component MM-FIO-PUR-REQ-SSP (Self-Service Procurement)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can access the configuration and the related documentation in the SPRO node Define Settings for Creation of Reservation under Materials Management Purchasing Purchase Requisition Reservation .
64 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sourcing and Procurement
9.3.2 Purchase Order Processing
9.3.2.1 Manage Purchase Orders
With this app, you can create purchase orders, change the document type of the newly created purchase order and use any customer-defined purchase order type (Z*) that has been copied with all dependent entries from standard purchase order type NB.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item J62 (Asset Accounting), 3UK (Inbound Storage Tank Management - Process Manufacturing), BMY (Subcontracting), 1W8 (Legal Control), J82 (Automated Purchase-to-Pay with SAP Ariba Commerce Automation), 2TW (Complementary Procurement Functions), BNX (Consumable Purchasing), 2TX (Direct Procurement with Inbound Delivery), 22K (Contingent Workforce Procurement via SAP Fieldglass), 2NV (Guided Buying Capability with SAP Ariba Buying), J45 (Procurement of Direct Materials), 2XU (Procurement of Materials with Variant Configuration), 22Z (Procurement of Services), 2R7 (Purchasing Rebate Processing), 18J (Requisitioning), 2LG (Supplier Consignment), 1FM (Quality Management in Procurement)
Application Component MM-PUR (Purchasing), MM-FIO-PUR-PO (Fiori UI for Purchase Orders )
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Manage Purchase Orders
What's New in SAP S/4HANA 2020 FPS02Sourcing and Procurement PUBLIC 65
9.4 Central Procurement
9.4.1 Integration Scenario for the Automation of Central Procurement Quotes with Ariba Network (5JT)
The scope item Automation of Central Procurement Quotes with Ariba Network (5JT) enables you to create central requests for quotation (central RFQs) in SAP S/4HANA for central procurement by pooling purchase requisitions from connected SAP S/4HANA Cloud , SAP S/4HANA, or SAP ERP systems. The central RFQs are send to SAP Ariba Discovery, where suppliers can create quotations. The supplier quotations are then send from SAP Ariba Discovery to the SAP S/4HANA central procurement system. After awarding the best supplier quotations in central procurement, you can create purchase orders in the connected systems.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 5JT (Automation of Central Procurement Quotes with Ariba Network)
Application Component BNS-INT-ARI (Ariba Integration with SAP S/4HANA)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Automation of Central Procurement Quotes with Ariba Network (5JT)
9.4.2 Central Purchase Contracts
9.4.2.1 Support for Third-Party Connected Systems
With this feature, you can now distribute and exchange information of central purchase contracts in an SAP S/4 HANA Central Procurement (hub) system with outline agreements in any third-party connected system. To do this, you can use the Business Add-In (BAdI) MM_PUR_HUB_NON_SAP_CONECVTY (BAdI: Exchange of Data Between Hub Systems and Third-Party Systems).
66 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sourcing and Procurement
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 2ME (Central Purchase Contracts)
Application Component MM-PUR-HUB-CTR (Central Purchase Contracts)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Use the method PROCESS_CENTRAL_CONTRACTS (Process Central Contract Operations) to perform operations specific to central purchase contracts in the third-party connected system.
You can access the BAdI and the related documentation in the SPRO node BAdI: Exchange of Data Between Hub Systems and Third-Party Systems under Materials Management Purchasing Central Procurement - Settings in Hub System .
Related Information
Manage Central Purchase Contracts
9.5 Procurement Analytics
9.5.1 Supplier Evaluation by Quality (Deprecated)
This app is deprecated and will be removed from the SAP Fiori launchpad with SAP S/4HANA 2021. We recommend that you switch toSupplier Evaluation By Quality Notifications as soon as possible.
Technical Details
Type Deprecated
What's New in SAP S/4HANA 2020 FPS02Sourcing and Procurement PUBLIC 67
Functional Localization Not Applicable
Scope Item 1JI (Real-Time Reporting and Monitoring for Procurement)
Application Component MM-FIO-PUR-ANA (Purchasing Analytics)
Available As Of SAP S/4HANA 2020
Related Information
Supplier Evaluation By Quality Notifications
9.6 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
68 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Sourcing and Procurement
10 Supply Chain
10.1 Warehouse Management
10.1.1 Immediate Batch Replication for Decentralized EWM
This feature enables you to have batches replicated to your Extended Warehouse Management (EWM) system immediately. If you are using decentralized EWM based on SAP S/4HANA, master data, including batches, that were created or changed in the enterprise management system (such as SAP S/4HANA or SAP ERP) must be replicated to EWM. Before SAP S/4HANA 2020 FPS02, this replication was done with a scheduled report and therefore with a time delay. With FPS02, the newly created or changed batches are replicated directly to EWM without a delay.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component LO-SPM-X (Cross-Application Topics)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Customizing
For more information, and in order to activate immediate batch replication, go to the Customizing activity Integration with Other SAP Components Extended Warehouse Management Basic Settings for EWM
Linkage Settings for Decentralized EWM Define Enhanced Settings for Transfer to Decentralized EWM . There you can select your receiving logical system and enter whether or not you want to use immediate batch replication using IDoc transfer.
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 69
10.1.2 Improved Compliance Checks from SAP Global Trade Services
With this feature, compliance checks in SAP Global Trade Services (GTS) for the Extended Warehouse Management (EWM) outbound delivery are performed more frequently:
● As delivery dates can influence the result of a compliance check, EWM calls GTS for a new check each time when the out-of-yard date has been changed.
● The compliance of a delivery in GTS can change even if the outbound delivery has not been changed in EWM (e.g. a business partner is blocked). Therefore GTS can send a push-message to the EWM outbound delivery if something has changed in GTS regarding compliance.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component SCM-EWM-IF-GTS-CC (Interface GTS)
Available As Of SAP S/4HANA 2020 FPS02
10.2 Delivery and Transportation
10.2.1 Delivery Management
10.2.1.1 API for Inbound Delivery (A2X)
This service enables you to read, create, update, and delete outbound deliveries in an API call. It is based on the OData protocol, and can be consumed in Fiori apps and on other user interfaces.
Technical Details
Type Changed
Functional Localization Not applicable
70 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
Scope Item 2TX (Direct Procurement with Inbound Delivery)
Application Component LE-SHP-API (Interfaces for Delivery Documents API)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
This API is available on the SAP API Business Hub .
Related Information
Inbound Delivery (A2X)
10.2.1.2 API for Outbound Delivery (A2X)
This service enables you to read, create, update, and delete outbound deliveries in an API call. It is based on the OData protocol, and can be consumed in Fiori apps and on other user interfaces.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item BD9 (Sell from Stock), BDA (Free of Charge Delivery), 4OO (Electronic Movement Control System)
Application Component LE-SHP-API (Interfaces for Delivery Documents API)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
This API is available on the SAP API Business Hub .
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 71
Related Information
Outbound Delivery (A2X)
10.2.1.3 API for Customer Returns Delivery (A2X)
This service enables you to read, create, update, and delete customer returns deliveries in an API call. It is based on the OData protocol, and can be consumed in Fiori apps and on other user interfaces.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item BDD (Customer Returns), BKP (Accelerated Customer Returns)
Application Component LE-SHP-API (Interfaces for Delivery Documents API)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
This API is available on the SAP API Business Hub .
Related Information
Customer Returns Delivery (A2X)
10.2.2 Transportation Management
10.2.2.1 Enhancements for Advanced Shipping and Receiving
With this feature, the functions for the Advanced Shipping and Receiving process in Transportation Management (TM) have been enhanced.
72 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-INT (Integration)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Advanced Shipping and Receiving is an integrated, end-to-end process that allows users to send, receive, and transport products.
The following functions are now available in Advanced Shipping and Receiving:
● Creating of Packages Across Freight Units [page 73]● Late Changes to Capacity Documents [page 74]● Enhancements for Creating or Updating Consignment or Freight Orders on Inbound Messages [page 76]● Enhancements for Handling of Errors in Business Documents [page 78]● Automatic Consignment Building [page 79]
Related Information
Advanced Shipping and ReceivingEnd-to-End Process (E2E) for Advanced Shipping and Receiving
10.2.2.1.1 Creating of Packages Across Freight Units
With this feature you can merge freight units for packages that contain items across several freight units in the Advanced Shipping and Receiving inbound process.
Technical Details
Type New
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 73
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-INT (Integration)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can assign product items from different freight units to the same package, for example, by packing them on a single pallet. In consignment orders this can be done manually on the UI or by inbound messages. For freight orders this can be done manually on the UI or by combined inbound messages (transport-based freight order). If possible, the system performs a freight unit merge for these packages that contain items across several freight units. Merging means, that all items of a freight unit are moved to another freight unit. The empty freight unit is then cancelled. In all other cases only single items are moved to another freight unit.
Effects on Customizing
You have activated the synchronization of predecessor documents. For more information, see Synchronization of Predecessor Documents.
Related Information
Creation of Packages Across Freight Unit ItemsAdvanced Shipping and Receiving
10.2.2.1.2 Late Changes to Capacity Documents
With this feature, you can make changes to a capacity document even after the execution at the stop in the capacity document has started or been completed. For example, you can add one or more requirement documents to the warehouse unloading stop in the road freight order, even after the truck has departed from that stop. You can also unassign a requirement document from a capacity document after the execution at the stop has started but before goods movement is posted.
74 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-FRM (Freight Order Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
If you add a requirement document after the truck has loaded or unloaded the goods at the warehouse loading stop or warehouse unloading stop, has checked out, or has departed, then the statuses of the items added later do not match the statuses of the stop and of the other items in the road freight order. You can update the statuses of the items in the new requirement document by using the Document Errors tab page in the road freight order. Document errors are created and you can resolve them to correct the mismatch between statuses.
Effects on Existing Data
Document errors are created and the Document Error tab page is enabled, even if you haven't made the corresponding settings, that is, you haven't selected the Enable Saving of Documents with Errors value in the Handling of Incorrect Inbound Messages field in the Customizing for the freight order type. To correct these errors, you can use the actions available next to the description of the error. After you have corrected the error, the Document Errors tab page is disabled.
Related Information
Late Changes to Capacity Documents
10.2.2.2 Package Building in Integration Based on EWM TU
This feature enables you to use package building based on capacity documents in the integration of Transportation Management (TM) and Extended Warehouse Management (EWM) based on the EWM transportation unit (TU). This type of package building takes place late in the process when capacity documents exist already.
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 75
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-INT (Integration)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Package Building in Integration Based on EWM TUsIntegration Based on EWM Transportation Units
10.2.2.3 Enhancements for Creating or Updating Consignment or Freight Orders on Inbound Messages
With this feature, the functions for creating or updating consignment orders or freight orders on inbound messages have been enhanced. Your business partner can send you a consignment order as an advanced shipping notification (ASN) or a freight order using EDI communication. Based on this message, the system automatically creates a consignment order or freight order.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-FRM-CON (Consignment Order)
TM-FRM-FRO (Freight Order)
Available As Of SAP S/4HANA 2020 FPS02
76 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
Additional Details
The following functions are now available:
● You can now update freight orders by using EDI messages.● The functionality to update consignment orders by using EDI messages has been enhanced.● You have the following options to create or update freight orders or consignment orders:
○ Separate Inbound Messages (Consignment-Based Freight Order)Information for freight orders and consignment orders can be sent in separate inbound messages. The freight order contains references to the related consignment orders.This function is already available as of S/4HANA FPS01.
○ Combined Inbound Messages (Transport-Based Freight Order)You can now also send combined inbound messages.Information for freight orders and consignment orders and their item structure can be combined and sent it a single inbound message. With combined inbound messages you can create freight orders and consignment orders.A combined inbound message contains both freight order header data and information about the full item structure (such as, information about the active vehicle resource, shipment items, and references to the requirement documents). With this information the system creates consignment orders with assigned freight units and a freight order with references to the consignment orders.
● An additional option in Customizing is available to handle updates by inbound messages after manual changes.
● The handling of errors in business documents has been enhanced. For more information, see the What's New document for Enhancements for Handling of Errors in Business Documents [page 78].
Effects on Customizing
Updates by Inbound Messages After Manual Changes
When customizing a freight order or consignment order type, you can specify whether further updates of a business document by inbound messages are allowed after you have already made manual changes in that document.
For more information, see Customizing for Transportation Management under Freight Order Management Freight Order Define Freight Order Types or Freight Order Management Consignment Order Define Consignment Order Types .
Related Information
Correction of Errors in Business DocumentsExample Checks to Find Errors in Business DocumentsCreation or Update of Consignment or Freight Orders on Inbound MessagesCreation and Editing of a Consignment Order
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 77
10.2.2.4 Enhancements for Handling of Errors in Business Documents
With this feature, the functions of handling errors in business documents in Transportation Management (TM) have been enhanced.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-FRM (Freight Order Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The following functions are now available:
Automatic Correction of Reference Errors – Automatic RetryAn automatic retry is now available to correct reference errors in business documents.
If you correct and resolve errors, for example, on the Document Errors tab page of a consignment order or in the product item itself, the system retries to resolve reference errors in the related freight order. It checks if reference errors to an unknown consignment order can be resolved. If the consignment order is now available in the system, the missing reference is automatically added in the freight order.
For more information, see Correction of Errors in Business Documents.
New Checks to Find Errors in Business DocumentsNew checks are available to find errors in business documents. The system runs various checks when freight orders or consignment orders are created or changed, for example:
● Check for overdelivery of quantityIn the inbound process the system checks for an overdelivery of quantity when the system creates or updates a consignment order or freight order on the basis of an inbound message or when you manually change quantities in a consignment order or freight order.For purchasing documents (such as purchasing orders or scheduling agreements) you can define a quantity tolerance for a product item, a percentage by which the quantity can be exceeded. You can also specify that there is no limit on overdelivery quantities (Unlimited).You maintain these settings in the purchase order or scheduling agreement on the Delivery tab page.
78 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
If the overdelivery tolerance is exceeded when you update the quantity of the item in the item hierarchy in the document, the system displays an error message. You can correct the product quantity in the item hierarchy. In the Advanced Shipping and Receiving inbound process, the predecessor document is also updated if you have enabled the setting for Enable Synchronization of Predecessor Documents in the Customizing.
● Vendor CheckWhen an inbound message (ASN) arrives to update a consignment order, the system checks the sent vendor.
● Check for Package-Related Errors in Nested PackagesWhen an inbound message (ASN) arrives and a consignment order is created or updated, the system checks for package-related errors.For more information, see Example Checks to Find Errors in Business Documents.
Effects on Customizing
Overdelivery Tolerance
In the Advanced Shipping and Receiving inbound process, you need to enable the setting for Enable Synchronization of Predecessor Documents in the Customizing for freight order type and consignment order type to be able to update the item quantity in the document. For more information, see Customizing for Transportation Management under Freight Order Management Freight Order Define Freight Order Typesor Freight Order Management Consignment Order Define Consignment Order Types .
10.2.2.5 Automatic Consignment Building
With this feature you can let the system automatically build consignment orders for freight orders. You may need these, for example, for follow-up processes such as customs declaration. Based on grouping rules that you have specified in a profile as well as default rules, freight units of a freight order are combined into consignment orders.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-FRM (Freight Order Management)
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 79
Additional Details
You can start the automatic consignment building from the user interface of the freight order document. There, you can choose whether the system first creates the consignment orders only locally in the freight order without reference to consignment order documents or if it directly creates consignment order documents. If the consignment orders are created only locally in the freight order, you can still make changes in the freight order that are applied later in the consignment order documents. Once the consignment documents have been created, they are no longer updated by changes to the freight order.
Consignment Building ProfileIn this profile you can predefine criteria for the automatic consignment building for freight units of a freight order. You can, for example, predefine whether the consignment orders are built only locally in the freight order or directly as consignment order documents. Furthermore, you can choose from predefined grouping rules or from rules that you have defined in Customizing (see below). The system combines the freight units into consignment orders according to these grouping rules and the general default rules for building consignment orders, for example, same source and target location.
Moreover, you can, for example, specify incompatibility settings and the consignment order type in the profile.
Effects on Existing Data
You can now choose the options to build consignment orders locally or create consignment order documents from the Follow-Up menu of the freight order user interface.
To create or edit a consignment building profile, you open one of the new Create Consignment Building Profile or Edit Consignment Building Profile apps from the launchpad. The consignment building profiles are also integrated in the Profiles and Settings - Worklist app on the launchpad.
Effects on Customizing
You can create your own grouping rules for automatic consignment building in Customizing. For more information, see Customizing for Transportation Management under Freight Order ManagementConsignment Order Define Grouping Rules for Automatic Consignment Building .
If you want to use a consignment building profile in your freight order, you must enter its name in the new Consignment Building Profile field in Customizing of the freight order type. For more information, see Customizing for Transportation Management under Freight Order Management Freight Order Define Freight Order Types .
Related Information
Automatic Consignment Building
80 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
10.2.2.6 Enhancements for Freight Order Management
With this feature, the functions of Freight Order Management in Transportation Management (TM) have been enhanced.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-FRM (Freight Order Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Creation of Consignment Orders from a Freight OrderYou can now create consignment orders on the Items tab page of a freight order document using the new Create Consignment Orders pushbutton. The system uses the default consignment order type that you have defined in Customizing for the freight order type or the consignment order types that you have defined in the consignment building profile or the planning profile that you have specified in the freight order type (in this sequence). If you haven't specified a consignment order type, the system uses the predefined default consignment order type. For more information, see Customizing for Transportation Management under
Freight Order Management Freight Order Define Freight Order Types .
Automatic Consignment BuildingYou can now let the system build consignment orders for the freight units of a freight order automatically. For more information, see the What's New document for Automatic Consignment Building [page 79].
Addition of Freight Units to Consignment Orders with Deviating Goods SuppliersIf you add freight units that have the same goods supplier to a consignment order, this goods supplier is added by the system to the consignment order. If the freight units have different goods suppliers, you can manually enter your requested goods supplier for this consignment order as a business partner. The goods suppliers and the corresponding source locations of the freight units are automatically adjusted. The predecessor documents, such as purchase orders, remain unchanged.
Display Package InformationIn the road freight order, consignment order, freight unit, and transportation unit documents, you can display which profile, engine (package builder, packing instruction, or packaging specification), and rule (packaging specification or packing instruction) was used to create packages.
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 81
If you make changes to the package item or to the cargo items contained within it that result in the load plan status of the package item being automatically set to Not Planned or Invalidated, the information in these fields is deleted. For more information, see the What's New document for Enhancements for Package Building [page 84].
Overdelivery Tolerance
In the road freight order and the consignment order documents, the system displays an error message on the Document Errors tab page if the overdelivery tolerance is exceeded when creating or updating the business document on the basis of an inbound message. The overdelivery tolerance percentage is defined in the purchasing document. There are several ways in which you can correct these errors, for example, you can update the quantity of the item to an amount within the overdelivery tolerance limit in the business document on the Document Errors tab page.
If the overdelivery tolerance is exceeded when you update the quantity of the item in the item hierarchy in the document, the system displays an error message. You can correct the product quantity in the item hierarchy.
For more information, see the What's New document for Enhancements for Handling of Errors in Business Documents [page 78].
Effects on Existing Data
Display Package Information
For displaying information about how the packages were created during package building, the Package Building Profile, Package Building Engine, and Package Building Rule fields have been added to the item details tab page for packages. The fields are visible in the road freight order, consignment order, all transportation units, and freight unit documents.
Changed Drop-down Menus
The Stages tab page in the capacity document has been enhanced with the Execution Status (Source) and Execution Status (Destination) drop-down menus. The Execution Status (Source) drop-down menu contains all the handling execution statuses that you can set for a stage at the source location while the Execution Status (Destination) drop-down menu contains all the handling execution statuses that you can set for a stage at the destination location.
Effects on Customizing
Packaging Material Check
You can now define in Customizing for the item type that the system checks for items of the business document whether you have entered a valid packaging material or auxiliary packaging material. For more information, see Customizing for Transportation Management under Freight Order Management Define Item Types for Freight Order Management .
82 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
10.2.2.7 Enhancements for Transportation Cockpit and Manual Planning
With this feature you can hide stages on the geographical map and you can configure a different spot visualization for planned and unplanned requirement documents. Further, you can set the warehouse door status in the road freight order hierarchy.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-PLN (Planning)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
On the geographical map, the following new functions are available:
● You can hide the first or last stage of a freight order or both stages. To do so, a new field has been added in the Customizing activity for defining layouts for the geographical map (see "Effects on Customizing"). By using the context menu on the geographical map, you can overrule the setting you made in Customizing.
● You can configure a different spot visualization, that is, different colors and shapes, for planned and unplanned requirement documents (that is, freight units, transportation units, and consignment orders).For example, the spots for the source and destination location can be displayed as follows:○ Green: for any planned freight unit stage○ Yellow: for any unplanned freight unit stage○ White with a green border: for planned freight unit stages that have the same source location or
destination location○ White with a yellow border: for unplanned freight unit stages that have the same source location or
destination location○ White: for a planned freight unit stage and an unplanned freight unit stage that have the same source
location or destination location
The following general function is available:
You can set the warehouse door status for a road freight order in the transportation cockpit to Arrived at Door or Departed from Door or reverse these status changes. To see the Warehouse Door Status field in the road freight order hierarchy, you need to implement the enhancement described in SAP Note 3006051.
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 83
Effects on Customizing
To define hiding of first or last stages on the geographical map or configure the spot visualization, in Customizing for Transportation Management choose Basic Functions Geographical Map Define Layouts for Geographical Map .
Related Information
Interactive Planning on the Map
10.2.2.8 Enhancements for Package Building
With this feature you can use 3D visualization in the test report for package building. Further, this report as well as the load plan hierarchy provide information on how the packaging hierarchy has been built automatically by package building. And in your freight unit building rule, you can indicate that a separate freight unit, freight order, or package unit is to be created for unpackaged items.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-PLN (Planning), TM-PLN-PB (Package Building), SCM-BAS-PAK-PB (Package Building)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● In the test report for package building, you can display a 3D visualization of your packages. You can either show all packages or only selected packages. Different coloring options are available.
● You can see in the load plan hierarchy, which package building profile, package building engine (package builder, packaging specification, or packing instruction) and package building rule (that is, the packaging specification or packing instruction) was used to create packages. The package building rule and the package building engine are also available on the result screen of the test report for package building. For
84 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
more information, see the What's New document for Enhancements for Freight Order Management [page 81].
● In your freight unit building rule, you can indicate that a separate freight unit, freight order, or package unit is to be created for unpackaged items, that means, one common business document is created for all unpackaged items that contains no other items. The system considers this new setting when it creates a complete package hierarchy (see "Effects on Existing Data"). Note that if you use the package builder as your package building engine, you must select the Only Full Packages in PB Result checkbox in your package building profile. In this case, the system builds full packages for a product and the remaining quantities of this product stay unpackaged. For more information, see Freight Unit Building Rule.
Effects on Existing Data
● You can add the following new fields to your load plan hierarchy (under Settings Columns ):○ Package Building Profile○ Package Building Profile (Description)○ Package Building Engine○ Package Building Engine (Description)○ Package Building Rule○ Package Building Rule (Description)
● The following fields have been added to the test report for package building:○ Package Building Rule○ Package Building Engine
● The new checkbox Create Separate Doc. for Unpackage Items has been added to the freight unit building rule under Advanced Settings Package Building .
Related Information
Test Report for Package BuildingLoad Plan
10.2.2.9 Improved Usability for Changing Transit Durations in Gateway Schedules
With this feature you can change the transit duration of a gateway schedule even after departure rules or voyages have been created.
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 85
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-MD-TN-SCH (Schedule)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
For a sailing schedule with a source container freight station (CFS) and a destination CFS, for example, you can change the pick-up transit duration (that is, the duration from the source CFS to the first port of loading) and the delivery transit duration (that is, the duration from the last port of discharge to the destination CFS). The system considers these transit durations for a new departure rule or a new voyage in the corresponding schedule. Changing the transit durations doesn't have an impact on existing departure rules and voyages.
Further, you can change the transit duration from the last port of discharge to the destination gateway after you created a voyage. The arrival time is derived from the transit duration. If you then copy time changes from the underlying carrier schedule's voyage into the gateway schedule voyage, the manually changed transit duration is preserved and used to re-calculate the arrival time.
This feature is also available in SAP S/4HANA 1909 SP04.
Related Information
Schedule
10.2.2.10 Improved Load Plan Status Handling
This feature enables you to use an improved load plan status handling.
Technical Details
Type Changed
86 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-PLN-LP (Load Planning)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● The load plan status handling is available for scenarios involving consignment orders. This offers transparency on the load plan status and the load plan item status of consignment orders from a packaging perspective.In the consignment order the following statuses are displayed:○ Load plan status (capacity) for top-level package items and lower-level package items○ Load plan item status (cargo) for product items and lower-level package items
Since the consignment order does not represent a capacity (such as a vehicle or a container), the load plan item status (cargo) of top-level items is not relevant.
You can set the load plan status manually using user interface actions or it can be set automatically by package building.
● The load plan item status handling considers auxiliary packaging materials consistently.You can set the load plan item status (cargo) for auxiliary packaging materials manually (for example, in a freight order). Or it is set automatically by package building (for lower-level package items only) or load planning.Note that the load plan status (capacity) is not relevant for auxiliary packaging materials because nothing else can be packaged into an auxiliary packaging material.
Related Information
Load PlanUse of Auxiliary Packaging Materials
10.2.2.11 Scheduling of Background Jobs
With this feature you can schedule several background jobs in a row and define the sequence in which they are to be processed.
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 87
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component TM-BF (Basic Functions)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can include background jobs in the run or exclude them from the run. Further, you can specify whether the system is to continue or cancel the run after one of the background jobs fails. This new program offers improved usability and flexibility for background jobs.
This feature is also available in SAP S/4HANA 1909 SP04, 1809 SP06, and 1709 SP08.
Effects on Existing Data
To schedule background jobs, on the SAP Easy Access menu, choose Logistics Transportation Management Administration Background Processing Schedule Background Jobs .
Related Information
Scheduling of Background Jobs
10.3 Simplified Planning Cycle in Forecasting
The new feature simplifies the planning cycle in the forecasting application within eSPP.
Previously, there was an extra service to determine error margins of statistical and disaggregated forecast results and to save it to respective key figures. Now, this is included in the services for the statistical forecast calculation and forecast disaggregation. The extra service is obsolete, and you can remove it from the process.
88 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Supply Chain
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component SCM-APO-SPP-SFC (Forecasting)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Customizing
For existing PSM planning profiles, you should remove items with the Calculation of the Standard Deviation and MAD service (SPP_FCS_SERVICE_MSE).
10.4 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
What's New in SAP S/4HANA 2020 FPS02Supply Chain PUBLIC 89
11 Integration
11.1 Business Network Integration
11.1.1 Integration with SAP Ariba Applications
11.1.1.1 Sourcing with SAP Ariba Sourcing (4BL)
The scope item now supports the enablement of custom fields for usage in SOAP APIs. You can enable usage for all custom fields that are available for external sourcing requests. If the usage in SOAP APIs is enabled for a custom field, this field is made available for transfer to external sourcing systems.
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4BL (Sourcing with SAP Ariba Sourcing)
Application Component BNS-INT-ARI (Ariba Integration with SAP S/4HANA)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Sourcing with SAP Ariba Sourcing (4BL)
11.1.1.2 Central Procurement with SAP Ariba Sourcing (4QN)
This scope item now supports the following features:
● Confirmations for central requests for quotation and central supplier quotations● Custom fields in SOAP APIs
90 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Integration
Technical Details
Type New
Functional Localization Not applicable
Scope Item 4QN (Central Procurement with Ariba Sourcing)
Application Component BNS-INT-ARI (Ariba Integration with SAP S/4HANA)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Confirmations for Central Requests for Quotation and Central Supplier Quotations
Confirmation messages can be exchanged between SAP S/4HANA and SAP Ariba Sourcing as follows:
● When a central request for quotation is transferred to SAP Ariba Sourcing and a corresponding sourcing request is generated, a success or error message is received in SAP S/4HANA.
● When a central supplier quotation is created in SAP S/4HANA based on bids that have been awarded in SAP Ariba Sourcing, a success or error message is sent to SAP Ariba Sourcing.
Custom Fields in SOAP APIs
You can now enable custom fields in external sourcing requests for usage in SOAP APIs. If the usage in SOAP APIs is enabled for a custom field, this field is made available for transfer to external sourcing systems.
Related Information
Central Procurement with Ariba Sourcing (4QN)
11.1.1.3 Contract Management with SAP Ariba Contracts (4AZ)
With the scope item Contract Management with SAP Ariba Contracts (4AZ), you can now integrate custom fields in SAP Ariba Contracts to SAP S/4HANA using the custom-mapping functionality of SAP Ariba Cloud Integration Gateway.
What's New in SAP S/4HANA 2020 FPS02Integration PUBLIC 91
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item 4AZ (Contract Management with SAP Ariba Contracts)
Application Component BNS-INT-ARI (Ariba Integration with SAP S/4HANA)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Integration of Custom Fields in SAP Ariba Contracts and SAP S/4HANA
This feature enables buyers on SAP Ariba Contracts to integrate custom fields in the contract workspace to SAP S/4HANA using the custom-mapping functionality. You can create custom fields of specific custom types in SAP Ariba Contracts and SAP S/4HANA. Using the custom-mapping functionality of SAP Ariba Cloud Integration Gateway, you can map the custom fields created in SAP Ariba Contracts with the corresponding custom fields created in SAP S/4HANA.
Related Information
Contract Management with SAP Ariba Contracts (4AZ)
11.1.1.4 Contract for Central Procurement with SAP Ariba Contracts (4B0)
With the scope item Contract for Central Procurement with SAP Ariba Contracts (4B0), you can now integrate custom fields in SAP Ariba Contracts to SAP S/4HANA using the custom-mapping functionality of SAP Ariba Cloud Integration Gateway.
Technical Details
Type Changed
92 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Integration
Functional Localization Not applicable
Scope Item 4B0 (Contract for Central Procurement with SAP Ariba Contracts)
Application Component BNS-INT-ARI (Ariba Integration with SAP S/4HANA)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Integration of Custom Fields in SAP Ariba Contracts and SAP S/4HANA
This feature enables buyers on SAP Ariba Contracts to integrate custom fields in the contract workspace to SAP S/4HANA using the custom-mapping functionality. You can create custom fields of specific custom types in SAP Ariba Contracts and SAP S/4HANA. Using the custom-mapping functionality of SAP Ariba Cloud Integration Gateway, you can map the custom fields created in SAP Ariba Contracts with the corresponding custom fields created in SAP S/4HANA.
Related Information
Contract for Central Procurement with SAP Ariba Contracts (4B0)
11.2 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
What's New in SAP S/4HANA 2020 FPS02Integration PUBLIC 93
12 Cross Components
12.1 Legal Hold Management for Mass Data
With this feature you can set legal hold on mass data.
You have the following options for excecuting E-Discovery in batch mode for handling mass data:
● Server Group: Enter the dedicated application server, if any, on which the E-Discovery should be executed in batch mode.
● Max Processes: Enter the maximum number of work processes that can be created in this application server, if applicable.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component BC-ILM-LCM (Legal Case Management for ILM)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● When you execute the E-Discovery program in background mode, you can see the Status of Background E-Discovery Run under Legal Case Attributes.You can check the logs for the scheduled E-Discovery run. To do so, navigate to Other FunctionsDisplay E-Discovery History . Select the Job Name for the relevant E-Discovery report.
● For BOR objects: ARC_LHM_PROPAGATE_LEGAL_HOLD - You can select the legal case, which are to be propagated to the store, from the value help.
● Legal case closure: If the number of objects in a legal case is very large and the legal case needs to be set to status Case Closed, then you can schedule the legal case closure in background mode.
● If the number of records in a legal case are greater than 200, the system displays the Maximum No. of Data Records button. You can select this option to display 200, 500, or 1000 records at one time. You can select Fetch Next 5000 Records to display the next set of 5000 records in addition to the existing records currently displayed on the screen.
94 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Cross Components
Related Information
Setting Legal Holds
12.2 Master Data Governance, Central Governance
12.2.1 Display of Archived Change Documents
In the Web Dynpro application Display Change Requests, you can find and display archived change requests. With this feature, you can choose the Change Documents button to display the related change documents of the selected archived change request.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component CA-MDG-AF (Application Framework)
Available As Of SAP S/4HANA 2020 FPS02
More Information
For more information, see SAP Note 2995802 and improvement request ID 253984 .
12.3 Situation Handling
12.3.1 New Use Cases for Situation Handling
With this feature you can use Situation Handling for additional use cases from these areas in SAP S/4HANA:
● Sales● Service
What's New in SAP S/4HANA 2020 FPS02Cross Components PUBLIC 95
● Public Sector
Get a detailed overview of all new use cases under Additional Details [page 96].
Technical Details
Type New
Functional Localization Not applicable
Scope Item 31N (Situation Handling)
Application Component CA-SIT (Situation Handling)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
New Situation Templates in SAP S/4HANA
Area or TopicSituation Template
Situation Template ID App Name SAP Fiori ID Scope Item
Sales Mass Change of Sales Docs: Jobs Complete
SD_SLSDOC_MASS_CHG_REQ_COMPLETED
Mass Change of Sales Documents
F5210 n/a
Service Service Maint. Plan Mass Schedule Issue
SRVC_MPLAN_MASS_SCHEDULING_ISSUE
Mass Schedule Maintenance Plans - Service
F4929 n/a
Public Sector Person Added in ICM Case
PSM_ICM_NEW_PERSON_IN_CASE
Manage Cases Web GUI app ID: TICM-CSSRH
n/a
Related Information
Use Cases for Situation Handling
12.4 Country/Region Specifics
For country/region-specific changes, please see Country/Region Specifics [page 99].
96 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Cross Components
12.5 Data Quality Management, version for SAP Solutions
SAP Data Quality Management, version for SAP Solutions functionality is now available within SAP S/4HANA for Customer Management. This update also includes changes to tax jurisdiction processing.
Technical Details
Type Changed
Functional Localization Localized for Germany
Scope Item 2UZ
Application Component EIM-DQM-SAP (SAP Data Quality Management, version for SAP Solutions)
Available As Of SAP S/4HANA 2020 FPS02
12.6 Behavioral Insights
With SAP S/4HANA for behavioral insights (abbreviated to: Behavioral Insights), you are provided with a platform to analyze the behavior of customers and generate risk scores and insights across multiple scenarios. These insights will allow you to make more informed decisions and to take pre-emptive or proactive actions.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component IS-PS-BEI
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Cross Components PUBLIC 97
Effects on Customizing
You can customize customer extraction rules, prediction scenarios, and events using the customizing activities under Cross-Application Components > Behavioral Insights.
Additional details
With this release, the following features are available:
● Scenarios Powered by Intelligent Scenario Lifecycle Management:Behavioral Insights uses Intelligent Scenario Lifecycle Management to model and train scenarios. You can train an intelligent scenario and use the trained model to get an accurate inference result.The following default scenarios are delivered in Behavioral Insights:○ Receivership○ Late Payment○ Late Filing
The scenarios include capabilities to automatically source data from SAP Public Sector applications (Tax and Revenue and PSCD) and then feed it into a machine learning-enabled predictive model in order to predict risks for the above scenarios.
● Generate Output for Intelligent Scenarios:Once the prediction scenarios are trained, you can run the prediction report that is delivered by Behavioral Insights to generate the risk scores and influencing factors using machine learning techniques.
● Integration of Behavioral Insights with SAP Analytics Cloud:The risk scores from the prediction report can be accessed using SAP Analytics Cloud. You can use SAP Analytics Cloud to create models from data sources, build stories based on those models, and perform live analysis using the CDS views delivered by Behavioral Insights.
98 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Cross Components
13 Country/Region Specifics
13.1 Australia
13.1.1 Cross-Application Functions
13.1.1.1 Electronic Documents
You can send electronic invoices and credit notes to your customers via the Peppol network using SAP Document Compliance for Australia. You can also receive electronic invoices and credit notes from your suppliers via the Peppol network.
Technical Details
Type New
Functional Localization Localized for Australia
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-AU (Document Compliance Australia)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You use the following transactions to process electronic documents:
Transaction Function
eDocument Cockpit (EDOC_COCKPIT) You can convert invoices into XML format and submit them to the end receivers.
eDocument: Processing in Background (EDOC_BACKGROUND) You can schedule jobs to run actions on electronic documents in the background.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 99
Transaction Function
Read Access Logging Manager (SRALMANAGER) You can log and monitor read access to sensitive personal data in electronic documents.
In addition, you need to maintain the Australian Business Numbers (ABN) of your companies and customers in the system. Companies are identified in the Peppol network by their ABNs, which are also their GST Registration Numbers.
Effects on System Administration
You can archive eDocuments using the archiving object EDOCUMENT.
Effects on Customizing
You need to carry out the following Customizing activities:
Customizing Activity Path in Transaction SPRO
Activate Source Type Documents for Company Code
Define Interface Type for eDocument
Assign eDocument Type to Accounting Document Type
Assign eDocument Type to Billing Document Type
Define Process Communication Through SAP Document Compliance Cloud Service
Cross-Application Components General Application
Functions eDocument General Settings
Assign Party ID Types to Business Partner
Assign Party ID Types to Companies
Define Bank Accounts for Company Code
Cross-Application Components General Application
Functions eDocument Country/Region-Specific Settings
Australia Settings for Peppol
In addition, you need to configure some value mappings and fix values, which are required for XML mapping.
Related Information
Electronic Documents
100 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
13.2 Belgium
13.2.1 Cross-Application Functions
13.2.1.1 Electronic Documents
13.2.1.1.1 eDocuments: PEPPOL for Convergent Invoicing
The central end-to-end business process supported by the eDocuments: PEPPOL for Convergent Invoicing (Belgium) solution involves the creation of invoices (normal invoices as well as correction invoices/credit notes) in Convergent Invoicing and outgoing-only electronic transmission of these documents to specified business partners within the standardized PEPPOL framework.
The following scenarios are supported, where both sender and receiver uses PEPPOL eDocument protocols:
● Domestic outgoing invoices, correction invoices and credit notes: Both sending and receiving entities located only within Belgium.
● Cross-border outgoing invoices, correction invoices and credit notes: Sending entity located in Belgium, receiving entity located in a different EU country.
Technical Details
Type New
Functional Localization Localized for Belgium
Scope Item 2BG (Convergent Invoicing)
Application Component XX-CSC-BE-FICA (Contract Accounting)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
NoteYou must be running an SAP S4HANA On-Premise system with the following minimum current status: S4CORE 104 SP 1 and have implemented the eDocuments for Belgium solution and the SAP Convergent Invoicing Solution.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 101
RestrictionSince Convergent Invoicing generates only out-going invoices, only the sending part of the communication is part of this current solution.
Effects on Customizing
The Customizing activity Assign eDocument Type to Convergent Invoice Document Type has been added under Cross-Application Components General Application Functions eDocument General Settings .
Related Information
eDocument for Belgium
13.2.2 Finance
13.2.2.1 Declaration for VAT Units
With this feature, you can use the Run Compliance Reports app to generate the Declaration for VAT Units (déclaration unité TVA or aangifte BTW-eenheid), a statistical declaration that is required by the National Bank of Belgium. VAT units that submit a collective VAT return must submit this additional declaration. It contains the VAT amounts and base amounts for the VAT reported separately for each company in the VAT unit, aggregated by the respective VAT registration numbers.
Technical Details
Type New
Functional Localization Localized for Belgium
Scope Item 1J2 (Advance Compliance Reporting)
Application Component FI-LOC-FI-BE (Financials Belgium)
Available As Of SAP S/4HANA 2020 FPS02
102 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Effects on Configuration
For more information, see Configuration for Declaration for VAT Units.
Related Information
Declaration for VAT Units
13.2.2.2 Contract Accounting Data in ACR Reports
With this feature, contract accounting (FI-CA) data can be included in the VAT Return report for Belgium using the Run Compliance Reports app. This means that if FI-CA is enabled in your system, the report retrieves data also from FI-CA and include that in the output.
Technical Details
Type New
Functional Localization Localized for Belgium
Scope Item Not applicable
Application Component FI-LOC-CA (Contract Accounting)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
For VAT Returns, the new Reconciliation Key and Reference Document Type columns are available in the analytical view for the generated runs, where you can check details regarding FI-CA documents. You can also check the FI-CA document data by choosing the Jump To… Itemization for G/L Documents option in the context menu of the Reconciliation Key and Document Number columns.
Related Information
VAT Return
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 103
13.2.2.3 Annual Sales Listing
With this feature, you can generate a list of items with the following information per item:
● Belgium tax number of the business partner● Total sales amount (without VAT) in euros● Total VAT amount in euros
In addition, you can now easily display the analytical view via the Analyze Data icon.
Technical Details
Type Changed
Functional Localization Localized for Belgium
Scope Item 1J2 (Advance Compliance Reporting)
Application Component FI-LOC-FI-BE (Financials Belgium)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Configuration
For more information, see Configuration for Annual Sales Listing.
13.3 Brazil
13.3.1 Cross-Application Functions
13.3.1.1 Electronic Documents
13.3.1.1.1 Consignment
This feature enables the consignment processes for Brazil, which represent the following situation: you receive the goods first, and then the goods are invoiced and paid later.
104 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Technical Details
Type New
Functional Localization Localized for Brazil
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-BR (Document Compliance Brazil)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Existing Data
The eDocument Cockpit (EDOC_COCKPIT) transaction displays the following processes:
● Brazil Csgmt Goods Receipt● Brazil Csgmt Invoice Rec.
Related Information
Consignment Goods ReceiptConsignment Invoice Receipt
13.3.1.1.2 Future Delivery
This feature enables the future delivery processes for Brazil, which represent the following situation: goods are invoiced and paid first, and then you receive the goods later.
Technical Details
Type New
Functional Localization Localized for Brazil
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-BR (Document Compliance Brazil)
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 105
Available As Of SAP S/4HANA 2020 FPS02
Effects on Existing Data
The eDocument Cockpit (EDOC_COCKPIT) transaction displays the following processes:
● Brazil Fut. Del. Goods Receipt● Brazil Fut. Del. Invoice Rec.
Related Information
Future Delivery Goods ReceiptFuture Delivery Invoice Receipt
13.3.1.1.3 Returnable Package
This feature enables the returnable package scenario in business processes for Brazil. In this scenario, you can include returnable packages (for example, pallets or barrels) in your inventory at no value until they are returned to the vendor.
Technical Details
Type New
Functional Localization Localized for Brazil
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-BR (Document Compliance Brazil)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The returnable package scenario is available on the following processes:
● Brazil Basic Process
106 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
● Brazil Csgmt Goods Receipt● Brazil Fut. Del. Goods Receipt● Brazil Normal Purchase● Brazil Subcontracting
Effects on Customizing
To configure this feature, make the following settings in Customizing: Cross-Application ComponentsGeneral Application Functions eDocument Country/Region-Specific Settings Brazil NF-e SpecificsDefine Item Type to CFOP Code .
Related Information
Basic Process for InboundConsignment Goods ReceiptFuture Delivery Goods ReceiptNormal PurchaseSubcontracting
13.3.2 Finance
13.3.2.1 Layout Change to Version 7 for ECF
Based on Ato Declaratório Executivo Cofis 86/2020, layout 7 of the ECF report is now supported.
Technical Details
Type Changed
Functional Localization Localized for Brazil
Scope Item 1J2
Application Component FI-LOC-FI-BR
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 107
Additional Details
Many changes have been done to the registers to adapt it to the new layout.
13.3.2.2 Layout Change to Version 9 for ECD
Based on Ato Declaratório Executivo Cofis 79/2020, layout 9 of the ECD report is now supported.
Technical Details
Type Changed
Functional Localization Localized for Brazil
Scope Item 1J2
Application Component FI-LOC-FI-BR
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Many changes have been done to the registers to adapt it to the new layout.
13.3.2.3 Layout Change to Version 1.5.1 for EFD-Reinf
Based on Ato Declaratório Executivo Cofis n° 84/2020, layout 1.5.1 of the EFD-Reinf report is now supported.
Technical Details
Type Changed
Functional Localization Localized for Brazil
Scope Item IJ2
108 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Application Component FI-LOC-FI-BR
Available As Of SAP S/4HANA 2020 FPS02
Related Information
EFD-Reinf Report
13.3.2.4 CTR Tech Info
This feature allows you to check where shadow tables and ERP tables are consumed.
Technical Details
Type New
Functional Localization Localized for Brazil
Scope Item 1J2
Application Component FI-LOC-FI-BR
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You use this report to check where shadow tables and ERP tables are consumed in the Advanced Compliance Report Brazil Option (EFD ICMS IPI, EFD Contribuições, ECD and ECF), either directly, indirectly, or both. The report shows the information by register, by CTR/PRV and by table fields. You can access it using the CTR Tech Info – Brasil tile.
13.3.2.5 Trace Log
This feature allows you to display information about the execution of Advanced Compliance Report Brazil Option.This feature allows you to display information about the execution of Advanced Compliance Report Brazil Option.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 109
Technical Details
Type New
Functional Localization Localized for Brazil
Scope Item 1J2
Application Component FI-LOC-FI-BR
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You use this report to display information about the execution of Advanced Compliance Report Brazil Option (EFD ICMS IPI, EFD Contribuições, ECD and ECF). You can access it using the Trace Log – Brasil tile.
13.4 Chile
13.4.1 Cross-Application Functions
13.4.1.1 Electronic Documents
13.4.1.1.1 Submission of Electronic Boletas
This feature enables you to use the electronic document solution for submitting electronic boletas and boleta summaries to the tax authorities in accordance with the new legal requirements in Chile.
Technical Details
Type Changed
Functional Localization Localized for Chile
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-CL (Document Compliance Chile)
110 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The following changes have been made:
● The eDocument Cockpit has been updated as follows:○ In the Chile eBoleta process, you can now use the Submit action to submit electronic boletas directly to
the tax authorities for approval. Once you click Submit, the selected eDocument for the boleta is automatically sent to the tax authorities in the background.
○ In the Chile eBoleta process, you can use the new Status action to get status updates from the tax authorities regarding approval.
○ The Chile Monthly Summary Boleta process has become obsolete. You can only use this process to display eDocuments for monthly summary boletas created earlier.
● You can no longer create monthly summary boletas using the eDocument Chile: Summary Report (EDOC_CL_SUMMARY_REPORT).
Related Information
eDocument for Chile
13.5 Colombia
13.5.1 Cross-Application Functions
13.5.1.1 Electronic Documents
13.5.1.1.1 Read Access Logging for Electronic Documents
With this feature you can use the Electronic Document channel in the Read Access Logging (RAL) Manager (SRALMANAGER transaction) to log and monitor read access to sensitive personal data for eDocument applications.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 111
Technical Details
Type New
Functional Localization Localized for Colombia
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-CO (Document Compliance Colombia)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Configuring Read Access Logging in Electronic Documents for Colombia
13.6 Denmark
13.6.1 Cross-Application Functions
13.6.1.1 Electronic Documents
13.6.1.1.1 Settlement Management Integration for eDocument
This feature enables you to create electronic documents in the eDocument Cockpit (EDOC_COCKPIT) transaction for the source document type Settlement Management Document (STLMT_INV) for the following Settlement Management Document categories:
● Settlement Document● Customer Settlement● Expense Settlement
Technical Details
Type New
112 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Functional Localization Localized for Denmark
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-DK (Document Compliance Denmark)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Existing Data
The new eDocument source type is available in the eDocument Cockpit (EDOC_COCKPIT), which allows you to create electronic documents for Settlement Management documents.
Effects on Customizing
The following Customizing activity is required to enable the new function: in Customizing for Cross-Application Components, under General Application Functions eDocument Assign eDocument Type to Settlement Document Type (EDOTMFKV) .
Related Information
Customizing
13.7 Germany
13.7.1 Cross-Application Functions
13.7.1.1 Electronic Documents
13.7.1.1.1 Maintaining Document Type for Business Partner (Germany eInvoice (E-Mail) Process)
If you use the Germany eInvoice (E-Mail) process to create invoices, by default the system creates the invoices using the ZUGFeRD XRechnung profile. As of this release, you can, define that for some business partners you want to exchange other profiles, such as the ZUGFeRD Comfort profile.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 113
Technical Details
Type Changed
Functional Localization Localized for Germany
Scope Item BD9 (BD9), BDD (BDD), J14 (J14), J59 (J59), BKL (BKL), 1EZ(1EZ), 2EQ(2EQ)
Application Component CA-GTF-CSC-EDO-DE (Document Compliance Germany)
Available As Of SAP S/4HANA 2020 002
Additional Details
You can define for each business partner, for each type of document which profile you want to use. You do this setting in the SAP Easy Menu under Cross-Application Components eDocument Germany Maintain Document Type for Business Partner or by calling the S_ER9_52002708 transaction.
Related Information
Germany eInvoice (E-Mail)Maintaining Document Type for Business Partner
13.8 Greece
13.8.1 Cross-Application Functions
13.8.1.1 Creating eDocument for Category C
You can now create eDocument for Category C with payroll, depreciation, and financial postings to be compliant with the Greece tax requirements.
114 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Technical Details
Type New
Functional Localization Localized for Greece
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-GR (Document Compliance Greece)
Available As Of SAP S/4HANA 2020 FPS02
Effects on Customizing
For more information about the required configuration settings, see Customizing for Document Compliance for Greece.
Related Information
Creating eDocument for Category C
13.9 Hungary
13.9.1 Cross-Application Functions
13.9.1.1 Electronic Documents
13.9.1.1.1 eInvoices for EU & Non-EU customers and stock transfers within EU
As of this release the Hungary Invoice Registration process for Hungary also supports the creation of electronic documents for the following type of invoices:
● invoices for customers within the European Union (EU)● invoices for customers in non-EU countries● invoices for stock transfers within the EU.
For more information refer to Hungary Invoice Registration.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 115
Technical Details
Type New
Functional Localization Localized for Hungary
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-HU (Document Compliance Hungary)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Hungary Invoice Registration
13.9.2 Finance
13.9.2.1 EC Sales List
You can use the Run Compliance Reports app to generate the EC Sales List.
Technical Details
Type Changed
Functional Localization Localized for Hungary
Scope Item 1J2
Application Component FI-LOC-ECS (Financials EC Sales List)
FI-LOC-FI-HU (Financials Hungary)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Consignment stock function is now available when reporting the EC Sales List.
116 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Related Information
EC Sales List
13.10 India
13.10.1 Finance
13.10.1.1 Treasury and Risk Management (TRM)
With this feature, you can use enhancements to the standard Treasury and Risk Management functions to enable the calculation of Goods and Services Tax (GST) for services, generating the relevant flows and posting them to Finance in accordance with the legal and business requirements in India.
Technical Details
Type New
Functional Localization Localized for India
Scope Item 1S4 (Automatic Market Rates Management), 1MN (SAP Fiori Analytical Apps for Treasury and Risk Management), 1WV (Debt and Investment Management), 1X1 (Foreign Currency Risk Management), 1X3 (Interest Rate Derivatives Management), 1XN (Market Rates Management - Manually via Upload), 1YI (Intercompany Process for Debt and Investment Mgmt), 2F2 (Intercompany Foreign Exchange Management), 2NZ (Bank Guarantee Management), 2UN (Money Market Mutual Fund Management), 3WY (Bond Management), 49D (Letter of Credit Management)
Application Component FI-LOC-TRM (Treasury and Risk Management)
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 117
Effects on Customizing
The following new Customizing activities are available for configuring GST calculation and posting for India in Customizing for Financial Supply Chain Management (FSCM), under Treasury and Risk ManagementTransaction Manager Country-Specific Functions India :
● Define Rules for Tax Flow Calculation● Assign Flow Calculation Procedure to Transaction Flows● Map Tax Cash Flow to Tax-Relevant Cash Flow● Assign SAC Code to Update Type● Define Union Territories for GST Calculation
In addition, you can use a default Business Add-In (BAdI) implementation for the Flow Calculation BAdI (IDCFMFLOWCALC), which enables the calculation of transaction-relevant taxes and the generation of the corresponding tax flows in the cash flow of the transaction. If required, you can make adjustments by creating your own implementation for this BAdI. To access this BAdI, in Customizing for Financial Supply Chain Management (FSCM), choose Treasury and Risk Management Transaction Manager Country-Specific Functions India Business Add-Ins (BAdIs) Business Add-Ins (BAdIs) .
For withholding tax, the existing Customizing activity Determine Flows for Extended Withholding Tax has been renamed to Specify Flow Attributes for Extended Withholding Tax in Customizing for Financial Supply Chain Management (FSCM), under Treasury and Risk Management Transaction Manager Country-Specific Functions India .
Related Information
Treasury and Risk Management - India (TRM)
13.10.2 Sourcing and Procurement (Materials Management)
13.10.2.1 Tax Collected at Source
Indian Income Tax Act has the provisions for tax collection at source. In these provisions, certain persons are required to collect a specified percentage of tax from their buyers on exceptional transactions. Most of these transactions are trading or business in nature.
Tax Collected at Source (TCS) is the tax payable by a seller which he collects from the buyer at the time of sale. Section 206C of the Income-tax act governs the goods on which the seller must collect tax from the purchasers. The current TCS scope has been widened to include sale of all the goods over 50 Lakhs threshold limit.
Business requirement is to capture TCS charged by the seller on the purchase side while booking the incoming invoices.
118 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Technical Details
Type New
Functional Localization Localized for India
Scope Item J45
Application Component FI-LOC-LO-IN (Logistics India)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Tax Collected at Source
13.10.3 Sales and Distribution
13.10.3.1 Tax Collected at Source Journal Voucher
The total sale accumulation amount for the Seller PAN and customer combination can fall below the TCS threshold amount due to the TCS invoices or debit notes cancellation(s). In such case, it is required to post Journal Voucher for the adjustment.
Technical Details
Type New
Functional Localization Localized for India
Scope Item J45
Application Component FI-LOC-LO-IN (Logistics India)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Journal Voucher
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 119
13.11 Mexico
13.11.1 Cross-Application Functions
13.11.1.1 Electronic Documents
13.11.1.1.1 Settlement Management Integration for eDocument
This feature enables you to create and send electronic settlement documents for condition contracts to the tax authorities in Mexico.
Technical Details
Type New
Functional Localization Localized for Mexico
Scope Item 1B6 (Sales Rebate Processing)
Application Component CA-GTF-CSC-EDO-MX (Document Compliance Mexico)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Once you post a settlement document for a condition contract, the system creates and displays an eDocument in the Mexico eInvoice process in the eDocument Cockpit. You can create and send an electronic settlement document in XML format to the tax authorities by submitting the eDocument.
Effects on Customizing
Besides the general settings, you need to make the following settings specifically for settlement documents for condition contracts:
● Activate Source Type Documents for Company CodeAssign the source document type Settlement Management Document (STLMT_INV) to your company code.
120 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
● Assign eDocument Type to Settlement Document TypeAssign the eDocument type Mexico eInvoice (MX_INVOICE) to your settlement document types that are used for condition contracts.
Find the settings in Customizing for Cross-Application Components under General Application FunctionseDocument General Settings .
In addition, you need to configure the following value mappings:
● SM_COND_TYPES (Specify Condition Types for Settlement Documents)● SM_DOC_TYPE (Specify SAT Document Types for Settlement Document)
Related Information
Customizing for eDocument - MexicoMexico eInvoice Process
13.11.1.1.2 Read Access Logging for Electronic Documents
With this feature you can use the Electronic Document channel in the Read Access Logging (RAL) Manager (SRALMANAGER transaction) to log and monitor read access to sensitive personal data for eDocument applications.
Technical Details
Type New
Functional Localization Localized for Mexico, Spain, Turkey
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO (Document Compliance Framework)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Read Access Logging
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 121
13.12 Netherlands
13.12.1 Cross-Application Functions
13.12.1.1 Electronic Documents
13.12.1.1.1 eDocuments: PEPPOL for Convergent Invoicing
The central end-to-end business process supported by the eDocuments: PEPPOL for Convergent Invoicing (Netherlands) solution involves the creation of invoices (normal invoices as well as correction invoices/credit notes) in Convergent Invoicing and outgoing-only electronic transmission of these documents to specified business partners within the standardized PEPPOL framework.
The following scenarios are supported, where both sender and receiver uses PEPPOL eDocument protocols:
● Domestic outgoing invoices, correction invoices and credit notes: Both sending and receiving entities located only within the Netherlands.
● Cross-border outgoing invoices, correction invoices and credit notes: Sending entity located in the Netherlands, receiving entity located in a different EU country.
Technical Details
Type New
Functional Localization Localized for the Netherlands
Scope Item 2BG (Convergent Invoicing)
Application Component XX-CSC-NL-FICA (Contract Accounting)
Available As Of ExampleSAP S/4HANA 2020 FPS02
Additional Details
NoteYou must be running an SAP S4HANA On-Premise system with the following minimum current status: S4CORE 104 SP 1 and have implemented the eDocuments for Belgium solution and the SAP Convergent Invoicing Solution.
122 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
RestrictionSince Convergent Invoicing generates only out-going invoices, only the sending part of the communication is part of this current solution.
Effects on Customizing
The Customizing activity Assign eDocument Type to Convergent Invoice Document Type has been added under Cross-Application Components General Application Functions eDocument General Settings .
Related Information
eDocument for the Netherlands
13.12.2 Insurance
13.12.2.1 Daily Payroll for Insurance Claims
As an enhancement to the available Insurance localization for the Netherlands, you can process pension payments in a more flexible way, on a daily basis.
Technical Details
Type Changed
Functional Localization Localized for the Netherlands
Scope Item Not applicable
Application Component FS-CM-LC (Financial Services Localization)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
With the already available solution, you manage to process a payment in FS-CD and execute a payroll run for the payment subject to the gross to net calculation once for each personnel number for a given payroll period.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 123
With the enhancement, the new daily payroll function, the process steps are the same, but the following enhancements are available:
● When you execute the payroll run, the gross amount goes through the gross to net calculation and the results are stored in new transparent tables.You can execute the payroll run as many times within a month as necessary. The data of each payroll run is stored in sequential order, without overwriting the data of any previous runs. The results of each payroll run are stored in the new tables and also the difference is stored in case a beneficiary receives 2 payments in one month.
● The Display Payroll Results (PAY_NL_PENS_RESULT) transaction displays the results that are stored in the new transparent tables in HCM.
● All the results that have already been posted to FS-CD are marked in the above listed transparent tables; the next time you post open items in FS-CD, the system calls and posts the amount that has not yet been posted to FS-CD.
Effects on Customizing
To be able to apply the daily payroll function, you need to activate the function for the payroll area you want to use during the process in Customizing for SAP Insurance under Claims Management Country SpecificsNetherlands Gross/Net Calculation Settings for Posting from HCM to FS-CD .
Related Information
Processing Daily Posting and Payroll
13.13 New Zealand
13.13.1 Cross-Application Functions
13.13.1.1 Electronic Documents
You can send electronic invoices and credit notes to your customers via the Peppol network using SAP Document Compliance for New Zealand. You can also receive electronic invoices and credit notes from your suppliers via the Peppol network.
124 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Technical Details
Type New
Functional Localization Localized for New Zealand
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-NZ (Document Compliance New Zealand)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You use the following transactions to process electronic documents:
Transaction Function
eDocument Cockpit (EDOC_COCKPIT) You can convert invoices into XML format and submit them to the end receivers.
eDocument: Processing in Background (EDOC_BACKGROUND) You can schedule jobs to run actions on electronic documents in the background.
Read Access Logging Manager (SRALMANAGER) You can log and monitor read access to sensitive personal data in electronic documents.
In addition, you need to maintain the New Zealand Business Numbers (NZBN) of your companies and customers in the system. Companies are identified in the Peppol network by their NZBNs, which are also their Global Location Numbers (GLN).
If you play the customer role, your GLN is required in receiving supplier invoices from your suppliers.
Effects on System Administration
You can archive eDocuments using the archiving object EDOCUMENT.
Effects on Customizing
You need to carry out the following Customizing activities:
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 125
Customizing Activity Path in Transaction SPRO
Activate Source Type Documents for Company Code
Define Interface Type for eDocument
Assign eDocument Type to Accounting Document Type
Assign eDocument Type to Billing Document Type
Define Process Communication Through SAP Document Compliance Cloud Service
Cross-Application Components General Application
Functions eDocument General Settings
Assign Party ID Types to Business Partner
Assign Party ID Types to Companies
Define Bank Accounts for Company Code
Cross-Application Components General Application
Functions eDocument Country/Region-Specific Settings
Australia Settings for Peppol
In addition, you need to configure some value mappings and fix values, which are required for XML mapping.
Related Information
Electronic Documents
13.14 Poland
13.14.1 Finance
13.14.1.1 Excessive Delays Report
You can run the Excessive Delays report using the Run Compliance Reports app to display the total amounts of the customer, supplier or business partner documents with excessive delay for a determined period.
Technical Details
Type Changed
Functional Localization Localized for Poland
Scope Item 1J2
126 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Application Component FI-LOC-FI-PL (Financials Poland)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Excessive Delays
13.15 Portugal
13.15.1 Finance
13.15.1.1 Invoice Print-Out with QR Code
You can print an invoice with QR code to meet legal requirements based on Portaria 195/2020 in Portugal.
Technical Details
Type New
Functional Localization Localized for Portugal
Scope Item Not applicable
Application Component FI-LOC-FI-PT (Financials Portugal)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Invoice Print-Out with QR Code
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 127
13.16 Qatar
13.16.1 Finance
13.16.1.1 Payment Medium Formats Will Be Obsolete
There are three payment medium formats available for Qatar that will become obsolete as of the SAP S/4HANA 2021 release and will be replaced by new payment medium formats. The following formats will be obsolete:
● QA_BT_NATIONAL_BANK● QA_BT_DOHA_BANK● QA_BT_AHLI_BANK
Technical Details
Type Deprecated
Functional Localization Localized for Qatar
Scope Item Not applicable
Application Component FI-LOC-FI-QA (Financials Qatar)
Available As Of SAP S/4HANA 2020 FPS02
13.17 Singapore
13.17.1 Cross-Application Functions
13.17.1.1 Electronic Documents
13.17.1.1.1 Factoring Companies or Remit-to Vendors as Payees
With this feature, for transactions where the payees are factoring companies or remit-to vendors, you can fill in data about the factoring companies or remit-to vendors properly in invoice XML files.
128 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Technical Details
Type New
Functional Localization Localized for Singapore
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-SG (Document Compliance Singapore)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Instead of receiving payments from customers directly, you might use factoring services where factoring companies receive customer payments on your behalf. Or you want your customers to remit payments to a bank account registered under your another Unique Entity Number (remit-to vendor). The system can fill in invoice XML files for such transactions properly, as follows:
● Show corresponding invoice type codes● Show factoring companies or remit-to vendors as payees
NoteIn a business-to-government invoice, the system shows the vendor ID of the factoring company or remit-to vendor registered at Vendors@Gov as the payee ID. You must maintain the vendor ID in the External BP Number field of the vendor master data.
In a business-to-business invoice, the system shows the Unique Entity Number of factoring company or remit-to vendor as the payee ID.
Effects on Customizing
You need to carry out the following Customizing activities:
1. Define a new partner function that refers to factoring companies or remit-to vendors.For invoices created in Sales, use the following Customizing activities to define new partner functions:○ Set Up Partner Determination for Sales Document Header○ Set Up Partner Determination for Billing Header
For invoices created in Finance, you need to implement your own logic using the method SET_OUTPUT_DATA of the Business Add-In (BAdI) Enhancements for eDocument (EDOC_ADAPTOR).
2. Define the usage of the new partner function by assigning a payee type to it.A new value mapping SG_PAYEE_PART_FUNC is available for defining the usage of partner functions. In this value mapping, you assign one of the following payee types to the partner function:○ Factoring Company
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 129
○ Remit-to Vendor
Related Information
Settings for Factoring Companies and Remit-to VendorsConfiguring Value MappingsMaintaining Vendor IDs for Factoring Companies and Remit-to VendorsProcessing Customer Invoices
13.17.1.1.2 Prescribed Goods Invoices
With this feature, for electronic customer invoices that you issue for sales of prescribed goods where customer accounting applies, the system can fill in the invoice XML files properly.
Technical Details
Type New
Functional Localization Localized for Singapore
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-SG (Document Compliance Singapore)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Customer Accounting for Prescribed Goods
130 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
13.18 Slovakia
13.18.1 Finance
13.18.1.1 VAT Return
As of January 1, 2021, the law requires that you use a new XML form structure when submitting VAT returns to the tax authorities. When debts cannot be recovered, you can apply for bad debt relief to recover VAT that is charged but unpaid by your customers. This feature enables you to generate VAT returns with the new structure and to report correction documents created for bad debt relief.
Technical Details
Type New
Functional Localization Localized for Slovakia
Scope Item 1J2 (Advance Compliance Reporting)
Application Component FI-LOC-FI-SK (Financials Slovak Republic)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can now use the Run Compliance Reports app to generate the VAT return with the new form structure that complies with legal requirements.
To report data for bad debt relief, you must create correction documents for bad debt relief with reference to the original documents.
Effects on Customizing
To report data for bad debt relief, you must make Customizing settings for the D (VAT Return) tax box structure type in Customizing for Financial Accounting, under General Ledger Accounting Periodic ProcessingReport Sales/Purchases Tax Returns , using one of the following options:
● Create new tax codes for bad debt relief and assign them to the relevant tax groups and tax boxes in the Define Tax Box Structure Customizing activity.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 131
● Create new document types for bad debt relief, separately for customer correction documents and supplier correction documents (for example, DD and KD) and assign them to the relevant tax groups and tax boxes in the Define Tax Box Structure Customizing activity.
Related Information
VAT Return
13.18.1.2 VAT Control Statement
As of January 1, 2021, the law requires that you use a new XML form structure when submitting VAT control statements to the tax authorities. When debts cannot be recovered, you can apply for bad debt relief to recover VAT that is charged but unpaid by your customers. This feature enables you to generate VAT control statements with the new structure and to report correction documents created for bad debt relief.
Technical Details
Type New
Functional Localization Localized for Slovakia
Scope Item 1J2 (Advance Compliance Reporting)
Application Component FI-LOC-FI-SK (Financials Slovak Republic)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can now use the Run Compliance Reports app to generate the VAT control statement with the new form structure that complies with legal requirements.
To report data for bad debt relief, you must create correction documents for bad debt relief with reference to the original documents.
Effects on Customizing
To report data for bad debt relief, you must make the Customizing settings for the C1-BDR and C2-BDR tax groups in the K (VAT Control Statement) tax box structure type in Customizing for Financial Accounting, under
132 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
General Ledger Accounting Periodic Processing Report Sales/Purchases Tax Returns Define Tax Box Structure .
Related Information
VAT Control Statement
13.19 Spain
13.19.1 Cross-Application Functions
13.19.1.1 Electronic Documents
13.19.1.1.1 Read Access Logging for Electronic Documents
With this feature you can use the Electronic Document channel in the Read Access Logging (RAL) Manager (SRALMANAGER transaction) to log and monitor read access to sensitive personal data for eDocument applications.
Technical Details
Type New
Functional Localization Localized for Mexico, Spain, Turkey
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO (Document Compliance Framework)
Available As Of SAP S/4HANA 2020 FPS02
Related Information
Read Access Logging
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 133
13.19.1.1.2 Settlement Management Integration for Electronic Invoicing of Public Entities
This feature enables you to create and send electronic settlement documents to the public entities in Spain.
Technical Details
Type New
Functional Localization Localized for Spain
Scope Item 1B6 (Sales Rebate Processing)
Application Component CA-GTF-CSC-EDO-ES (Document Compliance Spain)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can create electronic settlement documents for the following document types:
● Invoices and credit memos with reference to Condition Contract Management (CCM)● Invoices and credit memos without reference to CCM● Manual settlement documents with reference to contracts
Once you post a settlement document for these document types, the system creates and displays an eDocument for that either in the Spain eInvoice (Webservice) process (if the public entity provides a web service) or in the Spain eInvoice (Download) process (if the public entity does not provide a web service) in the eDocument Cockpit. You can create and send an electronic settlement document in XML format to the public entities by submitting the eDocument either through the web service or by downloading it and sending it to the public entities manually.
Effects on Customizing
Besides the general settings, you need to make the following settings specifically for settlement documents for condition contracts:
● Activate Source Type Documents for Company CodeA new source document type Settlement Management Document (STLMT_INV) is available. Assign this source document type to your company code.
● Assign eDocument Type to Settlement Document TypeAssign the eDocument type Spain eInvoice (ES_INV) to your settlement document types.
134 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Find the settings in Customizing for Cross-Application Components under General Application FunctionseDocument General Settings .
Related Information
Electronic Invoicing of Public Entities
13.19.2 Finance
13.19.2.1 EC Sales List
You can use the Run Compliance Reports app to generate the EC Sales List.
Technical Details
Type Changed
Functional Localization Localized for Spain
Scope Item 1J2
Application Component FI-LOC-ECS (Financials EC Sales List)
FI-LOC-FI-ES (Financials Spain)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Consignment stock function is now available when reporting the EC Sales List.
Related Information
EC Sales List
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 135
13.19.3 Maintaining Document Type for Business Partner (Germany eInvoice (E-Mail) Process)
If you use the Germany eInvoice (E-Mail) process to create invoices, by default the system creates the invoices using the ZUGFeRD XRechnung profile. As of this release, you can, define that for some business partners you want to exchange other profiles, such as the ZUGFeRD Comfort profile.
Technical Details
Type Changed
Functional Localization Localized for Germany
Scope Item BD9 (BD9), BDD (BDD), J14 (J14), J59 (J59), BKL (BKL), 1EZ(1EZ), 2EQ(2EQ)
Application Component CA-GTF-CSC-EDO-DE (Document Compliance Germany)
Available As Of SAP S/4HANA 2020 002
Additional Details
You can define for each business partner, for each type of document which profile you want to use. You do this setting in the SAP Easy Menu under Cross-Application Components eDocument Germany Maintain Document Type for Business Partner or by calling the S_ER9_52002708 transaction.
Related Information
Germany eInvoice (E-Mail)Maintaining Document Type for Business Partner
136 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
13.20 Sweden
13.20.1 Finance
13.20.1.1 Payment Medium Formats Will Be Obsolete
There are four payment medium formats available in Contract Accounting (FI-CA) for Sweden that will become obsolete as of the SAP S/4HANA 2020 FPS03 and SAP S/4HANA 2021 release and will be replaced by new payment medium formats. The following formats will be obsolete:
● AG● BG● PG● UG
Technical Details
Type Deprecated
Functional Localization Localized for Sweden
Scope Item Not applicable
Application Component FI-LOC-CA-PAY (FI-CA Payments Localization)
Available As Of SAP S/4HANA 2020 FPS02
13.21 Taiwan
13.21.1 Cross-Application Functions
13.21.1.1 Electronic Documents
13.21.1.1.1 Settlement Management Integration for eDocument
This feature enables you to create electronic settlement documents for the condition contracts that meet both the following requirements:
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 137
● They are issued to B2B customers.● They belong to the Sales Rebate type.
Technical Details
Type New
Functional Localization Localized for Taiwan
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-TW (Document Compliance Taiwan)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Once you post a settlement document for a condition contract that meets the requirements described above, the system creates and displays an eDocument in the Taiwan eInvoice process in the eDocument Cockpit. You can create an electronic settlement document in XML format by submitting the eDocument.
NoteElectronic settlement documents are supported in the Taiwan eInvoice process only.
Effects on Customizing
Besides the general settings, you need to make the following settings specifically for settlement documents:
● Activate Source Type Documents for Company CodeAssign the source document type Settlement Management Document (STLMT_INV) to your company code.
● Assign eDocument Type to Settlement Document TypeAssign the eDocument type B2B Allowance (TW_B2BALNC) to your settlement document types that are used for condition contracts.
Find the settings in Customizing for Cross-Application Components under General Application FunctionseDocument General Settings .
138 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Related Information
Customizing for eDocument
13.21.1.1.2 Generation of Number Range Files Based on Calendar Periods
With this feature, you can generate number range files (E0401 and E0402 files) based on calendar periods using the report Creation of Outbound Files for General Files (transaction EDOC_TW_GEN_FILE).
Technical Details
Type New
Functional Localization Localized for Taiwan
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-TW (Document Compliance Taiwan)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
A new Calendar Period option is available on the selection screen of the report Creation of Outbound Files for General Files. You can now generate E0401 and E0402 files based on calendar periods using this option.
For more information about how to use this report, choose More Program Documentation on the selection screen of the report.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 139
13.22 Turkey
13.22.1 Cross-Application Functions
13.22.1.1 Electronic Documents
13.22.1.1.1 Maintenance of Mersis Numbers and Ticaret Sicil Numbers
The way in which you maintain the Ticaret Sicil Numbers and Mersis Numbers has changed. Now you maintain the two numbers in additional parameters of company codes. The previous way of maintaining the two numbers through the value mapping INV_NOTE_TEXT is obsolete now.
Technical Details
Type Changed
Functional Localization Localized for Turkey
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-TR (Document Compliance Turkey)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
You can maintain the Ticaret Sicil Number and Mersis Number through the following new additional parameters of company codes:
● MERSIS: Maintain the Mersis Number as the value of this parameter.● SICIL: Maintain the Ticaret Sicil Number as the value of this parameter.
As a result, the two numbers show in both invoice and delivery note XML files.
The value mapping INV_NOTE_TEXT is obsolete now.
Related Information
Customizing for Full Solution - eInvoicing
140 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Customizing for Full Solution - Delivery Notes
13.22.1.1.2 New Fields for the Processes of Turkey in the eDocument Cockpit
Some new fields have been made available in the eDocument Cockpit to improve usability. Some amounts that you could get from XML files only in the past are now available directly in the eDocument Cockpit. These amounts include Tax-Exclusive Amount, Tax-Inclusive Amount, and Tax Amount. In addition, some other new fields about business partners have been added.
Technical Details
Type New
Functional Localization Localized for Turkey
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO-TR (Document Compliance Turkey)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The following new fields are available:
Processes New Fields
Turkey Basic eInvoice
Turkey Commercial eInvoice
Turkey Consumer eInvoice
● Business PartnerIn a customer invoice scenario, the business partner is a customer. In a returns invoice scenario, the business partner is a supplier.
● Alias● VKN/TCKN● Tax-Exclusive Amount, Tax-Inclusive Amount, Tax
AmountOnly after you submit an eDocument or preview an XML file, does the system fill these amount fields.
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 141
Processes New Fields
Turkey Incoming Basic eInvoice
Turkey Incoming Commercial eInvoice
● Supplier● Alias● VKN/TCKN● Tax-Exclusive Amount, Tax-Inclusive Amount, Tax
Amount
Turkey Export Registration ● Ship-to Party● Alias● VKN/TCKN● Tax-Exclusive Amount, Tax-Inclusive Amount, Tax
AmountOnly after you submit an eDocument or preview an XML file, does the system fill these amount fields.
Turkey Delivery Note
Turkey Delivery Note Unregistered User
● Ship-to Party● Alias● VKN/TCKN
Turkey Incoming Delivery Note ● Supplier● Alias● VKN/TCKN
13.22.1.1.3 Read Access Logging for Electronic Documents
With this feature you can use the Electronic Document channel in the Read Access Logging (RAL) Manager (SRALMANAGER transaction) to log and monitor read access to sensitive personal data for eDocument applications.
Technical Details
Type New
Functional Localization Localized for Mexico, Spain, Turkey
Scope Item Not applicable
Application Component CA-GTF-CSC-EDO (Document Compliance Framework)
Available As Of SAP S/4HANA 2020 FPS02
142 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Country/Region Specifics
Related Information
Read Access Logging
13.23 United Kingdom
13.23.1 Finance
13.23.1.1 Payment Medium Formats Will Be Obsolete
There are two payment medium formats available in Contract Accounting (FI-CA) for the United Kingdom that will become obsolete as of the SAP S/4HANA 2021 release and will be replaced by a new payment medium format. The following formats that are used for domestic payments will be obsolete:
● GB_BACSBOX● GB_BACWAY
Technical Details
Type Deprecated
Functional Localization Localized for the United Kingdom
Scope Item Not applicable
Application Component FI-LOC-CA-PAY (FI-CA Payments Localization)
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Country/Region Specifics PUBLIC 143
14 Industries
14.1 Consumer
14.1.1 Consumer Products
14.1.1.1 Last Mile Distribution for Direct Distribution
14.1.1.1.1 Mapping of Pricing Conditions to Manual Condition Types
This feature enables you to define how new and changed pricing conditions recorded in mobile billing documents are mapped to the condition types used in the pricing calculation.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component LE-LMD (Last Mile Distribution)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
If a mobile scenario is implemented, during route execution, delivery drivers can record new and changed price amounts for goods delivered on customer visits. Amounts can be recorded at document header level and at item level. Therefore, pricing conditions can be mapped at header and item level and also by sales area. Pricing conditions can also be mapped by route type. The route type determines the route processing scenario, for example, the delivery driver scenario.
When additional or changed prices are uploaded from a mobile device to the back-end system by using the Route Data - Download and Upload (LMD_ROUTE_2020), the pricing conditions can be mapped to condition types based on settings defined in Customizing. Condition types represent price elements, for example, prices, surcharges, discounts, taxes or freight. Condition types are also defined in Customizing and are stored in
144 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
condition records. Pricing procedures define which condition types are taken into account during the pricing calculation and in which sequence.
Condition types also let you differentiate between different output types in output determination, for example, order confirmation or delivery note, and between different strategy types in batch determination.
Effects on Data Transfer
At upload, the pricing conditions recorded on a mobile device in mobile billing documents (invoice or credit memo) are transferred to sales documents even if the values recorded are zero. Zero amounts are uploaded, for example, so that the value of a discount is set to zero during the pricing calculation.
NoteIn an upload request that contains additional or changed prices, the corresponding documents and document items must have the property value "DocumentCategory" : "MIV".
Effects on Customizing
● You define condition types in Customizing for Sales and Distribution under Basic Functions PricingPricing Control Define Condition Types .
NoteAn access sequence must not be defined for the condition types of sales documents to which pricing conditions recorded on a mobile device are to be transferred.
● You define pricing procedures in Customizing for Sales and Distribution under Basic Functions PricingPricing Control Define and Assign Pricing Procedures .
NoteTo ensure that the conditions uploaded from mobile devices are included in price determination, in the procedure control data, the Condition determined manually indicator must be set
● You map pricing conditions to condition types in Customizing for Logistics Executions under Last Mile Distribution Route Settlement Final Settlement Map Pricing Conditions (Mobile Scenario) .
NoteIf you leave any header condition type or item condition type fields blank, when data is uploaded from a mobile device, the amounts for the condition types are not updated in sales documents in the back-end system.
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 145
Related Information
OData API: Route Data - Download and Upload [page 147]
14.1.1.1.2 OData API: Mobile Execution Configuration - Read
This feature enables the download of configuration settings that control and provide information that is used in the creation of documents on mobile devices by drivers during route execution.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component LE-LMD (Last Mile Distribution)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
When drivers deliver ordered goods to customers, they sometimes need to create documents such as deliveries on a mobile device, for example, when an unplanned product is delivered. It is now possible to download configuration settings via the OData service Mobile Execution Configuration - Read that support the creation of such documents. The settings are made on the back-end system and are used to:
● Control the sales order type and delivery type of mobile documents by means of so-called “mobile transactions”If a customer uses SAP S/4HANA Sales for sales order creation, at upload, mobile documents can be mapped to sales order types and delivery types that are defined in the back end.
NoteIn OData format, a mobile transaction is represented by a three-character code and is specified by the MobileDocumentType property.
● Define the numbering format used for mobile billing documentsEach mobile billing document created on a mobile device has a unique mobile document number. After upload, this number is referenced by the corresponding document that is created in the back end, for example, an outbound delivery or an invoice.
146 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Effects on Data Transfer
In a download request, the entities Mobile Document Types and Mobile Number Ranges contain the property values that are relevant for the creation of documents of a mobile device.
NoteFor information about the entities and property values that an upload request must contain for the upload of documents, see Upload Requests for Specific Use Cases under Deliveries and Creation of Mobile Billing Documents.
Effects on System Administration
● You define mobile transactions and assign sales order types and delivery types to mobile transactions in Customizing for Logistics Execution under Last Mile Distribution Mobile Adapter Mobile Device Settings Mobile Transactions .
● You define the numbering format of mobile documents in Customizing for Logistics Execution under Last Mile Distribution Mobile Adapter Mobile Device Settings Mobile Document Numbering .
For more information about these Customizing settings, see Creation of Additional Documents on Mobile Devices [page 149].
Related Information
OData API: Route Data - Download and Upload [page 147]
14.1.1.1.3 OData API: Route Data - Download and Upload
This feature enables the upload of different information from mobiles devices that is captured by drivers during route execution. In addition to the use cases supported with the previous release, it supports the creation of billing documents (invoices and credit memos) on mobile devices, also with new and changed pricing conditions, and the upload of attachments of different media types and for various use cases.
Technical Details
Type Changed
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 147
Functional Localization Not applicable
Scope Item Not applicable
Application Component LE-LMD (Last Mile Distribution)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
If a mobile scenario is implemented, during route execution, delivery drivers might need to create additional documents on mobile devices to record returns and unplanned deliveries or they might need to create related billing documents. Furthermore, delivery drivers sometimes need to attach further information, for example, an image showing damaged goods, to other business objects such as a document, a collected payment, or a check-out/check-in stop. It is now possible to upload additional documents and attachments from a mobile device to the back-end system via the OData service Route Data - Download and Upload.
Effects on Data Transfer
In an upload request, the entities Attachments and Content contain the property values that are relevant for the upload of attachments.
NoteFor information about the entities and property values that an upload request must contain for the upload of attachments, see Upload Requests for Specific Use Cases under Attachments.
In an upload request, the entities Documents and Document Items contain the property values that represent pricing conditions recorded on a mobile device at header level and item level.
NoteFor information about the entities and property values that an upload request must contain for the upload of pricing conditions, see Upload Requests for Specific Use Cases under Creation of Mobile Billing Documents.
Effects on System Administration
For information about the Customizing settings for attachment types in the back end, see Upload of Attachments from Mobile Devices [page 150].
For information about the Customizing settings required to map pricing conditions recorded on a mobile device to the condition types defined in the back end, see Mapping of Pricing Conditions to Manual Condition Types [page 144].
148 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Related Information
OData API: Mobile Execution Configuration - Read [page 146]
14.1.1.1.4 Creation of Additional Documents on Mobile Devices
This feature enables the creation of additional documents on mobile devices during route execution.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component LE-LMD (Last Mile Distribution)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
If a mobile scenario is implemented, during route execution, delivery drivers can create additional documents on mobile devices to record returns and unplanned deliveries, or to create new documents, for example, delivery-based billing documents. These mobile transactions are then uploaded to the back-end system by using the Route Data - Download and Upload (LMD_ROUTE_2020) service. Mobile transactions are dependent on sales areas and need to be mapped to a sales order type and, optionally, to a delivery type in the back-end system.
Unique mobile document numbers created on a mobile device can optionally be used as an external reference number to quickly find and access relevant documents upon customer requests. Employees in the back office can thus find business documents more quickly and therefore process customer inquiries related to, for example, sales orders or billing documents, in a more time-efficient manner.
Effects on Data Transfer
The configuration settings for mobile transactions and mobile document numbers are downloaded to mobile devices with the OData service Mobile Execution Configuration - Read. For more information about the OData service, see OData API: Mobile Execution Configuration - Read [page 146].
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 149
Effects on Customizing
● You define mobile transactions in Customizing for Logistics Execution under Last Mile DistributionMobile Adapter Mobile Device Settings Mobile Transactions Define Mobile Transactions .
● You assign sales order types to mobile transactions in Customizing for Logistics Execution under Last Mile Distribution Mobile Adapter Mobile Device Settings Mobile Transactions Assign Sales Order Types to Mobile Transactions .
● You define mobile document numbers in Customizing for Logistics Execution under Last Mile Distribution Mobile Adapter Mobile Device Settings Mobile Document Numbering Define Mobile Document Number Types for Document Numbers .
● You define prefixes for mobile document numbers in Customizing for Logistics Execution under Last Mile Distribution Mobile Adapter Mobile Device Settings Mobile Document Numbering Define Mobile Document Number Prefixes .
Related Information
OData API: Route Data - Download and Upload [page 147]
14.1.1.1.5 Upload of Attachments from Mobile Devices
This feature enables the upload of attachments from mobile devices to the back-end system after route execution.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component LE-LMD (Last Mile Distribution)
Available As Of SAP S/4HANA 2020 FPS02
150 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Additional Details
If a mobile scenario is implemented, during route execution, delivery drivers can use their mobile devices to create attachments, such as signatures, generated billing documents, or pictures of damaged goods. The delivery drivers then select the appropriate attachment type directly on their mobile devices. A delivery driver can, for example, select the attachment type Delivery to add a customer signature to a delivery document.
After route execution, when the attachments are uploaded to the back-end system by using the Route Data - Download and Upload (LMD_ROUTE_2020) service, the selected mobile attachment type is used to assign the attachments to the correct route business object. An attachment with, for example, attachment type Delivery is then assigned to the related delivery document.
Effects on Data Transfer
The configuration settings for mobile attachment types must be downloaded to mobile devices with the OData service Mobile Execution Configuration - Read. For more information about the OData service, see OData API: Mobile Execution Configuration - Read [page 146].
Effects on Customizing
You define additional mobile attachment types in Customizing for Logistics Execution under Last Mile Distribution Mobile Adapter Mobile Attachments Define Mobile Attachment Types .
NoteThe attachment types Billing Document, Check-In, Collection, Check-Out, and Delivery are pre-delivered.
Related Information
OData API: Route Data - Download and Upload [page 147]
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 151
14.2 Energy & Natural Resources
14.2.1 Utilities
14.2.1.1 Contract Billing
14.2.1.1.1 OData API: Extension for Multichannel Foundation for Utilities
With this feature you can create any set of utility-specific master data objects, including technical master data in SAP S/4HANA Utilities, and use enhancements for meter reading results.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component IS-U-BI-PI (Utilities Product Integration Layer)
Available As Of SAP S/4HANA 2020 FPS02
This API is available on the SAP API Business Hub
Related Information
Extension for Multichannel Foundation for Utilities
14.2.1.1.2 OData API: Utilities Price Key
This feature enables you to specify a price origin with a utilities price key. You can use the price origin for fixed pricing. The following operations, which were made available with earlier shipments, have been enhanced to support price origins:
● Create● Read
152 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
● Update (This operation is not supported if the price origin is specified.)
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component IS-U-BI-PI (Utilities Product Integration Layer)
Available As Of SAP S/4HANA 2020 FPS02
This API is available on the SAP API Business Hub .
Related Information
Utilities Price
14.2.1.2 SAP Waste & Recycling
14.2.1.2.1 Minimum Net Weight Check for Multirange Scales
You can use this function to define a minimum net weight according to the gross weight for multirange scales.
There are special requirements for multirange scales. A multirange scale has at least two weighing intervals. If the load increases beyond one of the defined weighing intervals, the minimum net weights change automatically.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component IS-U-WA (Waste Management)
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 153
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Use the enhanced configuration settings for hardware profile groups and maintain the weighing intervals for the gross weight. Depending on the gross weight value, the minimum load of the net weight differs.
The minimum net weight is checked based on the previously determined gross weight. If the minimum net weight is not reached, the assigned weighing information is displayed on the scale in the net weight field.
Effects on Customizing
Maintain all configuration settings for hardware profile groups under Waste Management Waste Disposal Facility Weighing Connection Define Hardware Profile Groups .
Related Information
Load Management for Scales and VehiclesMeasurement Steps for Manual WeighingAllocate Hardware Profile Group and Cash Journal
14.2.1.2.2 Measuring Steps of Manual Weighing Entries
You can use this function to define measuring steps for manual weighing entries on weighbridges.
Some weighbridges have a strictly defined measuring interval. Based on the calibration of the scales they are only able to measure in certain steps. These measuring steps are based on the weight range of the measured gross weight and tara weight. This is required in order to avoid wrong manually entries according to the weighbridge calibration in the weighing transaction.
Technical Details
Type New
Functional Localization Not applicable
154 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Scope Item Not applicable
Application Component IS-U-WA (Waste Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Use the enhanced configuration settings for hardware profile groups and maintain measuring steps for weighing intervals for gross weight and tara weight.
In case of manual weighing in the weighing transaction with the specification of this hardware profile group, a check is carried out to determine whether the weights entered have been entered in the defined measuring steps.
If the manually entered weights do not match the defined measuring steps, the user is informed by a message. The weight must then be corrected manually by the user. Otherwise the weighing process cannot be completed.
Effects on Customizing
Maintain all configuration settings for hardware profile groups under Waste Management Waste Disposal Facility Weighing Connection Define Hardware Profile Groups .
Related Information
Measurement Steps for Manual WeighingLoad Management for Scales and VehiclesAllocate Hardware Profile Group and Cash Journal
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 155
14.3 Financial Services
14.3.1 Insurance
14.3.1.1 Policy Management
14.3.1.1.1 Optimized Web Service Call for Creating an External Renewal Quote
The call of the Web service for creating a renewal quote in SAP Product, Quotation and Underwriting Management has been optimized. Firstly, the Web service is now called only once for each policy, even if the policy contains several contracts (previously, the Web service was called for each contract within the policy). In addition, the handling of errors that can occur when the Web service is called has been refined.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-PM (Policy Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
As of Policy Management in SAP S/4HANA 2020 FPS01, the time model function CTRREN is available to trigger the creation of a renewal quote in SAP Product, Quotation and Underwriting Management via a Web service. This time model function is executed in the renewal run (update type RNW).
The new features when calling the Web service are described in more detail below.
Web Service Is Called Only Once for Each PolicyIf a policy has several contracts, the time model function CTRREN was previously executed for each contract and, as a result, SAP Product, Quotation and Underwriting Management was called multiple times.
However, since a renewal quote is created in SAP Product, Quotation and Underwriting Management at policy level, the renewal quote needs to be created only once for each policy. As a result, the Web service has to be called only once for each policy.
156 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
NoteThe created quote can still include renewals for all contracts of the original policy. For this reason, policy processing is required to execute the time model function CTRREN in the renewal run (update type RNW).
Optimized Error HandlingThe handling of errors that can occur when the Web service is called has been refined. A differentiation is now made between connection errors and functional errors during the creation of the quote.
● Connection errors:If there are connection errors, the update run ends with an error and the time model function CTRREN or the associated date remain scheduled, but are not yet executed.
● Functional errors:The update run is not ended if there are errors that occur during the creation of the renewal quote in SAP Product, Quotation and Underwriting Management and that are returned by the Web service. These error messages are logged during the run and can be monitored and analyzed by an administrator. The time model function CTRREN or the associated date are executed after the successful end of the run and are no longer scheduled.
This differentiation prevents deadlock situations in which the time model function CTRREN blocks further updates because it is still scheduled for execution even though the renewal quote was created successfully in SAP Product, Quotation and Underwriting Management.
14.3.1.1.2 Further Processing of Renewal Quotes Without Customer Response
You can now call the external quotation system SAP Product, Quotation and Underwriting Management from Policy Management to trigger the further processing of renewal quotes to which the customer has not responded after a specific acceptance period. This means that you can close those quotes that are no longer required in the external quotation system.
The new transaction /PM0/ABP_RNW_ACT_NOR (program /PM0/ABP_RNWLOFFER_ACT_NORSPNS) is available for this purpose. You should schedule this transaction as a regular background job. The background job calls the external quotation system, determines which quotes are overdue, and executes the default action for the respective quote. The external quotation system returns the current processing status of the quotes to Policy Management at time intervals defined by the user.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 157
Application Component FS-PM (Policy Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Starting the Transaction
To call the new transaction /PM0/ABP_RNW_ACT_NOR, choose Insurance Policy Management In-Force Business Management Periodic Processing Standard Response If No Customer Response to Renewal Quote in the area menu.
As soon as you execute the transaction, Policy Management calls the interface to the external quotation system via the Business Add-In (BAdI) /PM0/ABT_QU_RNWACT_REMOTE_BADI.
Calling the External Quotation System via a Web Service and Starting the Background Job in the External Quotation SystemFirst, a Web service of the external quotation system is called via the BAdI method TRIGGER_RNWL_DEFAULT_ACTION. This Web service starts a background job in the external quotation system that determines the renewal quotes to which the customer has not responded after a specific acceptance period. The system executes the default action for these renewal quotes that is defined according to the rules in the external quotation system for the quote.
Regular Calling of the External Quotation System via an OData Service and Returning the Processing Status to Policy ManagementAn OData service of the external quotation system is called regularly via the BAdI method GET_RNWL_RUN_STATUS. This OData service calls the external quotation system at the time intervals that you have specified on the program’s initial screen in the Time Interval Between Calls field and returns detailed information about the current processing status of the quotes to Policy Management. This information is saved in a log in Policy Management.
Content and Use of the Application LogA system administrator can display the application log and thus track the current processing status. The system administrator can analyze any errors that occur.
In detail, the application log contains the following information:
● General information about the background run, such as:○ Process ID○ Number of renewal quotes included in the run○ Processing status
● Detailed information about each renewal quote, such as:○ ID of the submission or quote○ Action that was executed for the quote○ Previous policy number○ New policy number (if created)
158 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Effects on System Administration
Scheduling the TransactionSchedule the execution of the transaction /PM0/ABP_RNW_ACT_NOR as a regular background job.
Configuring the Web ServiceFor more information about configuring the Web service, see the documentation Renewal (Quote Created in External System) under Configuration Configuration of the Web Service for Calling SAP Product, Quotation and Underwriting Management below under "Related Links".
Configuring the OData ServiceFor more information about configuring the OData service, see the documentation Renewal (Quote Created in External System) under Configuration Configuration of the OData Service for Calling SAP Product, Quotation and Underwriting Management below under "Related Links".
Effects on Customizing
You find the new BAdI /PM0/ABT_QU_RNWACT_REMOTE_BADI in Customizing for Policy Management under In-Force Business Management Basis Business Processes Business Add-Ins (BAdIs) BAdI: Standard
Response in Quotation System (No Response to Renewal Quote) .
Related Information
Renewal (Quote Created in External System)
14.3.1.1.3 Search for and Navigation to Previous Policy Following Renewal
If a new policy is created as the result of a renewal, the previous policy is now displayed on the user interface (up until now, the previous policy was only saved in the database). In addition, there are now some search and navigation options for the previous policy.
Technical Details
Type New
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 159
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-PM (Policy Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Navigation to Previous Policy
The previous policy for the new policy created as the result of a renewal is now displayed on the Policy Data tab page. From here, you can navigate to the inquiry for the previous policy.
Search Options
● The policy number of the previous policy is now available as a search criterion in the Policy Search General search help in the following business processes:○ Inquiry○ Change○ Reset○ Reversal○ Central Access
● The policy number of the previous policy is now contained as a search field in the input structures of the following remote-enabled search function modules:○ /PM0/ABT_SVC_POL_FIND - to search for policies○ /PM0/ABT_SVC_APPL_FIND - to search for applications
14.3.1.2 Claims Management
14.3.1.2.1 Refreshed design for Insurance Claim Open Letter
The old logo of the claim opened letter has been replaced with a new colored logo and the fonts have been adjusted to improve the layout of the letter.
Technical Details
Type New
160 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-CM (Claims Management)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The technical name of the form for the claim opened letter is ICL_OPEN_PDF.
14.3.1.3 msg.PMQ
14.3.1.3.1 Configurable Display Names for Product Modules
This feature enables you to use configurable display names for product modules.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
These display names are used in all editors, views, dialogs, assistants and other interface texts instead of the technical name (exception: file system based views such as SVN and Git). Thus, technically relevant information is now displayed in the display name instead of the technical name.
Supported:
● Name and/or label of the current product module,
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 161
● Name and/or label of the owner product module (based on the incoming relationship),● Name and/or label of a target product module (based on the outgoing relationships)● Value of a product attribute● Content of a uniqueness rule● Name and/or label of the product module type
Display names can follow an individually defined display name pattern. A display name pattern can be stored on the product module type or inherited from its basic types.
In this context the following functionalities have been integrated into PMQ.Designer:
● Configuration of display names in the workspace settingsThe Show Display Names functionality can be activated/deactivated in the Preferences/PMQ/Display menu under the Display Names group. By default, this option is disabled. You can also specify whether objects that are part of the display name are represented by their (technical) name and/or label.
● Maintenance of display name patternsTo store specific display name patterns for product modules of a type, the property view of product module types has been revised. Using the new selection "Display name of product modules", a specific display name pattern can be defined in a freely editable text field Pattern or with the help of the table below.
● POTATO export of display namesThe POTATO export of the output profiles COMPLETE, REPORT and DEFAULT now considers the Display Name column in the worksheet of the respective product module.
14.3.1.3.2 Uniqueness Rules
In this release, the scope of functions for uniqueness rules is now extended by various contents
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
162 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Additional Details
The scope of functions for uniqueness rules is now extended by the following contents:
● Team comparisonIn the Merge Editor for product module types, uniqueness rules of different versions can now also be compared and merged. The rule content of the respective rule is displayed under the content tab.
● Product module type comparison editorThe product module type comparison editor has been enhanced to display and edit the properties of rules (label, content, rule type, sort key and tags). In the properties view of a rule, it is possible to edit additional information about it.
● Reference viewIn the reference view, the context menu can now also be used to apply filters to specific references caused by rules. The Used in Rule menu item is provided for forward referencing; the Used by Rule menu item is provided for backward referencing. Inherited information (inherited uniqueness rules and their uniqueness criteria) is also considered when determining forward references.
● SearchIn the PMQ Basic search you can filter rule objects by the contexts of product module and product module type. This allows a specific search for dependency or uniqueness rules.
14.3.1.3.3 Dependency Rules
With this feature, the functional scope for handling dependency rules is extended by miscellaneous contents
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The functional scope for handling dependency rules is extended by the following contents:
● Team comparison
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 163
In the Merge Editor, dependency rules of different revisions of product modules can now also be compared and merged. The rule content of the respective rule is displayed under the tab Content (dependency criteria, assigned product module).
● Reference ViewThe reference view has been supplemented by two context menu entries Is used by Rule and Uses in Rule and thus aligned with the existing functionalities of the reference view.
14.3.1.3.4 Improvements for the comparison editor
The functional scope of the comparison editor for product module types and product modules is extended
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
The functional scope is extended as follows:
● Display and editing of relation attributes in the comparison editorThe comparison editors for product module types and product modules have been extended to display and
edit the properties of relation product attributes / and relation contract attributes / (Label, Data Type, Dimension, Visibility, Value/Default Value, Restriction, Tags, Sort Key). The property Optional is only available for product module types. The relation attributes are each grouped with regard to their parent relation.
● Editing relationship targetsIn the comparison editors for product module types and product modules, relationship targets can be edited directly within the table view using a drop-down list, or by using copy and paste. When copying, the qualified name of the relationship target is transferred to the clipboard.
● Deleting and resetting propertiesIt is now possible to delete cell contents or to restore a default value, since not every property can be
completely deleted. The action Delete / Reset to Default is available for this in the context menu. If several cells are selected, the action can only be conducted if the contents of all selected cells can be deleted or reset.
164 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
14.3.1.3.5 Improvement of Column Filters in Tables
With this feature you can filter by display texts and use wildcard expressions as well.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
An assistant for configuring column filters for internal tables is now available. You can filter by display texts and use wildcard expressions as well. You can filter entries via a search input field or by selecting items from a checkbox list containing all available cell entries of the column. The option Add Current Selection to Filter can be used to extend a created column filter. It is also possible to delete the filter of the selected column using the assistant.
14.3.1.3.6 Improvements for M10
With this feature you can use the two new built-in functions GetMessageCountand GetMessageAt have been added for M10.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 165
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
Two new built-in functions GetMessageCount and GetMessageAt have been added for M10. The GetMessageCount function outputs the number of messages in the specified mailbox while the GetMessageAt function retrieves the message with the specified index.
14.3.1.3.7 New column "Original value" for debug views
With this feature you can now use a new column that shows the value of a variable before the calculation.
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
A new, optionally showable column named Original Value has been added to the debug views PMQ Variables, PMQ Instance Details, PMQ Instance Monitoring and PMQ Product Module Instances. It shows the value of a variable before the calculation. The column is filled for instance properties Name/Status and for contract attributes.
14.3.1.3.8 Selection Filter for Table Types
With this feature you can now use the new selection filter parameter tabletypename. This allows filtering for tables that implement the defined table type. Also in POTATO the field name structure type has been replaced by table type.
166 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Technical Details
Type New
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
Additional Details
● POTATO now provides the new selection filter parameter tabletypename.This allows filtering for tables that implement the defined table type.
● Renaming of Structure Types to Table TypesIn POTATO the field name structure type has been replaced by table type. Within the PMQ.Designer, the designation structure types is still used.
14.3.1.3.9 Error Corrections and Usability Improvements
With this feature, smaller issues has been fixed and the usability has been improved.
Technical Details
Type Changed
Functional Localization Not applicable
Scope Item Not applicable
Application Component FS-MPM (msg.PMQ)
Available As Of SAP S/4HANA 2020 FPS02
What's New in SAP S/4HANA 2020 FPS02Industries PUBLIC 167
Additional Details
● PMQ.Designer○ Duplicate GUIDs of elements were not detected as errors in some data constellations. This has been
fixed.○ The Workspace Product Language Selection Control did not update when product languages were
changed via user preferences. This has been fixed.○ The GetLanguage() function determined a different language than the one set in the test case in case
of redundant language objects. This has now been fixed.○ When copying and pasting numbers from Excel into PMQ.Designer, it occurred that only the displayed
(OR formatted) value was pasted instead of the actual (OR saved) value from Exceld. This has been fixed.
○ The Copy as new generation and Copy as new adaptation level actions copied the properties of the compact component (product module) to the root product module of the new adaptation level. This behavior has been fixed.
○ If configurable product module symbols were used, it could happen that these were not displayed and that some functions were missing. The problem only occurred in connection with read-only object libraries. In the case of libraries, their version was saved in the icon path. Increasing the library version therefore resulted in incorrect paths. The library version is now no longer part of the icon paths. For this reason, existing paths must be manually adapted to the new format.
○ When executing the M10 functions round/roundDown/roundup for decimal values, a warning was issued if the second parameter (number of decimal places) was not also of data type Decimal. This has been fixed.
○ Compilation errors were generated for package, formula and function names starting with a number. This has been fixed.
○ For validation messages, double-clicking opens the appropriate editor and selects the corresponding element. This behavior did not work for validation messages which were created using a customer-specific builder. This has been fixed.
● M10○ The built-in functions ToLower and ToUpper for coverting characters of a string now support an
extended character set. In the Java Runtime Environment (JRE) all Unicode characters are supported. In the C runtime environment (CRT) the characters from the Unicode Plane 0 (BMP) are converted. The following special conversions are not supported in C-Runtime:○ Turkish and Azerbaijani I-conversions (with and without dot)○ Lithuanian I and J conversions (with all decorations)○ alternative small Greek sigma at the end of the word.
● POTATO● ○ During POTATO export and subsequent import of an internal table with a restriction to a PMQ object,
the PMQ object restriction was deleted. This triggered an error message in PMQ.Designer that the restriction of the respective column does not match the restriction of the structure type field. This has been fixed.
○ During POTATO import, tag lists with multiple entries were imported incorrectly. This has been fixed.○ In POTATO projects additional statistic entries were created in the .info files. This has been deactivated.
Now no statistic data is written to the .info files.
168 PUBLICWhat's New in SAP S/4HANA 2020 FPS02
Industries
Important Disclaimers and Legal Information
HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.
Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
What's New in SAP S/4HANA 2020 FPS02Important Disclaimers and Legal Information PUBLIC 169
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.
THE BEST RUN