Kinder

IBM Consulting
SAP S/4HANA Impact Assessment

Tier 1 Report - AA MOTORS
September 2024
By: IBM HIA Delivery Team
Executive Summary Compatibility
Assessment
Assessment Scope Security Assessment
Basis Assessment and Testing Consideration

Findings
Functional Assessment Re-training Consideration

and Findings
Fiori Assessment, CDS and Top 20
Technical Assessment Fiori Recommendations and
and Findings Intelligent Enterprise
Content
BW Assessment Next Steps and Follow

up Actions
16 September 2024 IBM and AA MOTORS Confidential 2
AA MOTORS is investigating ways to rationalise and increase
harmonization of current back-office ERP systems.
There are many options to adopting a HANA roadmap - IBM’s HANA Assessment provides the
opportunity to evaluate functional and technical options and benefits of adopting SAP
S/4HANA.
AA MOTORS specifically wanted IBM to assess the current SAP ECC system and the readiness
to move to SAP S/4HANA. IBM HIA delivery team has completed the SAP S/4HANA 2023
assessment on System SR2, a copy of the Production SAP System with production like data for
AA MOTORS.
Functional Assessment Technical Assessment Key Areas of Impact
• Letter of Credit
42% 39%
• Business Partner (BP)
• Credit Management
• Cash and Liquidity Management
L4 business process Custom developments are • General Ledger

scenario are impacted. impacted
• Fixed Assets Accounting
• Bank Account Management
Executive • Dealer Business Management
Summary
Given the results of this assessment specific functional and technical topics are identified that need deeper
investigation/analysis to define the comprehensive concept for AA MOTORS to S/4HANA 2023 System
Conversion scope

SAP S/4HANA assessment was carried out on SR2, with the assumption
that the SR2 system is aligned with Production in terms
of SAP components and their versions.
The assessment objective was to understand the impact of moving the current SAP ERP
to SAP S/4HANA 2023 on premise version.
Source System Target System

Product Release Product Release
EhP 7 for SAP ERP 6.0 with SPS 4 SAP Application Version SAP S/4HANA 2023 FPS01
SAP Application Version
(SAP_APPL 617 - 4 )
SAP Netweaver 7.4 with SPS 6 SAP NetWeaver / ABAP Version SAP ABAP Platform 2023
SAP NetWeaver / ABAP Version
(SAP_BASIS 740 - 6 )
SAP System Type Unicode
SAP System Type Unicode
SAP HANA Platform Edition 2.0
Database Version SYBASE 16.0.04.04 Database Version SPS 07 (Revision 71) on Linux
(SLES or RHEL only)
Two step Conversion process. Need to split Dual Stack before doing conversion
Plan for Dual Stack Split. Only ABAP Stack can be used to convert ECC 6.0 to S/4HANA conversion
It is recommended that these pre-requisites are completed before start of S/4HANA System Conversion Project with a cooling period of at least 1-2
business cycle.
HDB 2.0 SP 07 Revision 71 is the minimum database version needed for S/4 Hana 2023
Assessment EhP 7 for SAP ERP 6.0 with SPS 4 (SAP_APPL 617 - 4 )
Reference : 3338941- Add. info. on converting to SAP S/4HANA using SUM 3307222- SAP S/4HANA 2023: Release Information
Scope 2.0 SP18 Note
3338951- Database Migration Option (DMO) of SUM 2.0 SP18 3351047- SAP S/4HANA 2023 Feature Package
Stack 00: Additional Release Information
Note : S/4HANA Target system runs on Little Endian Architecture Only

Business
Functions There are only 48 Business Functions activated in the AA MOTORS - SR2
Impact (1/4) and none is expected to hinder the System Conversion process.
BF Name Current Status End State Status Type Short Text
/CUM/MAIN Active No Impact Enterprise Enhancement Compatible Units
/CUM/MAIN_1 Active No Impact Enterprise Business Function Compatible Units Archiving
/DBM/SER_MRSS_USAGE Active No Impact Enterprise Business Function DBM Service MRSS Usage
AUTO_DP_1 Active Migration Possible:Supported Industry Business Function Dealer Portal, VMS, SPP, ES
AUTO_DP_2 Active Migration Possible:Supported Industry Business Function DP, NWBC, VC Intgr.
DIMP_SDUD Active Migration Possible:Supported Industry Business Function Discrete Indus. - Mill Products
EA-HR Active No Impact Enterprise Enhancement Human Capital Management
EA-PLM Active Migration Possible:Supported Enterprise Enhancement PLM Extension
EA-TRV Active No Impact Enterprise Enhancement Travel Management Extension
FIN_FSCM_CCD Active Migration Possible:Supported Enterprise Business Function FSCM Functions
FIN_FSCM_CCD_2 Active Migration Possible:Supported Enterprise Business Function FSCM Functions 2
FIN_FSCM_CCD_3 Active Migration Possible:Supported Enterprise Business Function FSCM Functions 3
FIN_FSCM_CCD_INTEGRATI
Active Migration Possible:Supported Enterprise Business Function FSCM Integration 2
ON

Business
FIN_FSCM_CCD_INTEGRATI
Active Migration Possible:Supported Enterprise Business Function FSCM Integration 3
ON_3
FIN_GL_CI_1 Active Migration Possible:Supported Enterprise Business Function New General Ledger Accounting
FIN_LOC_CI_29 Active Migration Possible:Supported Enterprise Business Function Localization Topics for Qatar
FIN_REP_SIMPL_1 Active No Impact Enterprise Business Function Reporting Financials
FIN_REP_SIMPL_2 Active No Impact Enterprise Business Function Reporting Financials 2
FIN_REP_SIMPL_3 Active No Impact Enterprise Business Function Reporting Financials 3
FIN_TRAVEL_1 Active No Impact Enterprise Business Function Travel Management
FIN_TRAVEL_2 Active No Impact Enterprise Business Function Travel Management 2
FIN_TRAVEL_3 Active No Impact Enterprise Business Function Travel Management 3
FND_IBO_MULTIBE_1 Active No Impact Enterprise Business Function FND, Multi Back-End for Inbox
HCM_ASR_CI_1 Active No Impact Enterprise Business Function HCM, Administrative Services 01

Business
HCM_ESS_CI_1 Active No Impact Enterprise Business Function HCM, ESS for Personal Info.
HCM_ESS_UI5_1 Active No Impact Enterprise Business Function HCM, ESS on SAP UI5
HCM_ESS_WDA_1 Active No Impact Enterprise Business Function Employee Self Services on WDA
HCM_ESS_WDA_2 Active No Impact Enterprise Business Function HCM, ESS on Web Dynpro ABAP 2
HCM_ESS_WDA_3 Active No Impact Enterprise Business Function HCM, ESS on WD ABAP 3
HCM_LOC_CI_21 Active No Impact Enterprise Business Function HCM Topics for India
HCM_LOC_CI_42 Active No Impact Enterprise Business Function HCM, Localization for Qatar
HCM_MSS_UI5_1 Active No Impact Enterprise Business Function HCM, MSS on SAP UI5
HCM_MSS_WDA_1 Active No Impact Enterprise Business Function HCM, MSS on WD ABAP
HCM_MSS_WDA_2 Active No Impact Enterprise Business Function HCM, MSS on WD ABAP 2
HCM_TIM_WDA_1 Active No Impact Enterprise Business Function HCM, Leave Request in ESS & MSS

Business
LOG_EAM_PAM Active No Impact Enterprise Business Function EAM: Pool Asset Management
LOG_MMFI_P2P Active No Impact Enterprise Business Function MM, Integration MM and FI
LOG_MM_MAA_1 Active Migration Possible:Supported Enterprise Business Function MM Multiple Account Assignment
LOG_MM_SIT Active Migration Possible:Supported Enterprise Business Function MM, Stock in Transit & Act.Cstng
LOG_SD_CI_01 Active Migration Possible:Supported Enterprise Business Function Sales & Distribution
MDG_FOUNDATION Active No Impact Enterprise Business Function MDG, Generic Functions
MDG_FOUNDATION_2 Active No Impact Enterprise Business Function MDG, Generic Functions 2
MDG_FOUNDATION_3 Active No Impact Enterprise Business Function MDG, Generic Functions 3
SD_01 Active Migration Possible:Supported Enterprise Business Function Logistics S&D Simplification

There are only 11 add-ons identified in the AA MOTORS - SR2 source
system and they are compatible with conversion to target release of
S/4HANA 2023.
Nevertheless, specific version upgrades or specific SAP Notes needs to be considered
for the S/4HANA for technical system conversion.
Vendor
Addon Release Description (SAP / 3rd OSS Notes Impact / Remarks
party)
CoD ERP
CODERINT 600 Integration SAP AddOn 2293815 Available part S/4 Core. This Add on will be uninstalled during migration
Content
DBM (Dealer Business Management) is SAP's solution for automotive
dealers. SAP DBM ( Dealer business Management ) provides the solution
for automotive sales side and after sale side.
To get this functionality, SAP ECC-DIMP and SAP DBM need to be
installed together.
In S/4HANA, SAP DBM is no longer available.
Available on SAP Store, Vehicle Sales and Service (VSS) by proaxia is the
innovative, adaptable, reliable Dealer Management System based on SAP
S/4HANA. The fully integrated and complete solution for vehicle sales
and service is co-innovated with SAP and is part of SAP’s industry cloud
portfolio for auto.
This is an SAP CERTIFIED add-on that works with SAP S/4HANA Cloud
Dealer Business Public Edition, SAP Analytics Cloud for planning
DBM 800 Not Known
Management Minimum system requirements for VSS 3.0 – Backend System,
S/4HANA 2020
SAP_BASIS 755 SP02
S4CORE 105 SP02
For VSSUI 3.0 standalone frontend server, minimum system
requirements - SAP_BASIS 752 SP08, SAP_GWFND 752 SP09, SAP_ABA
SAP and 3rd 752 SP09, SAP_UI 755 SP03.
There are no special SAP Notes which must be implemented in the
party Add-ons system prior to VSS 3.0 installation. Check the note for installation steps.
VSS utilizes the standard SAP resources and therefore it follows standard
Impact(1/5) SAP procedure for sizing process. As per discussion with SAP, the
delivery of these objects in the Y* namespace has been agreed with SAP.
Contact proaxia - [email protected]

S/4HANA 2023.
Vendor
party)
Proaxia DBM|E® is ideal for extending SAP® Dealer Business Management
(SAP DBM). It adds new functionalities and components to SAP DBM in
response to the specific requirements of regional markets, industry
Dealer Business segments and brands.
Management Proaxia DBM|E® provides all components to adapt the system to
DBME 22_04 Extensions requirements, to accelerate implementation and migration, to share best
(proaxia DBM E practice processes and innovative developments with all proaxia DBM|E®
®) users, and at the same time reduce the costs of further development and
maintenance.
https://www.proaxia-group.com/en/portfolio-item/proaxia-dbme-
extension-for-sap-dbm/
Supported with business function /PLMU/IPPE_INT. iPPE BOM converter
within PLM is not available. Successor is Product Structure Management
2240360, and Product Structure Synchronization. iPPE Time Analysis is not
EA-IPPE 400 SAP iPPE SAP AddOn
2330324 available. Functionality of Integrated Product and Process Engineering
(iPPE) is not supported in an APO transaction in S/4HANA. Check Note
2330324.
SAP and 3rd

party Add-ons
Impact(2/5)

S/4HANA 2023.
Vendor
party)
The automotive industry solution for material versions in SAP ERP Discrete Industries &
Mill Products (ECC-DIMP) is based on the industry solution for the long material number
which is activated using the business function MGV_LAMA.
The implementation of the long material number will be fundamentally changed in SAP
S/4HANA, and considering the limited functionality and value of the solution for material
versions and the very low customer adoption rate, that solution will be not available with
2270398,
Industry SAP S/4HANA.
2349033,
ECC-DIMP 617 DIMP Solution- In order to fix, kindly implement the attached correction instructions in note 2849897 to
2194272,
Standard resolve this issue. Also check and if needed, implement, note 2875232 then implement
2333024,
2886896.
Checks have to be executed before the conversion to SAP S/4HANA, if all preliminary steps
in the source system have been performed. This is as per SAP note 2194272. One should
implement this note. The checks will be executed during the transition process. After
implementing this note - one should implement the few more notes as mentioned in this
note.
SAP Learning Solution for SAP S/4HANA is an Add-On that can be installed on SAP
S/4HANA on-premise releases 1809 to 2023. It corresponds to the Learning Solution
Frontend (LSOFE in Business Suite).
LSOFE is now called S4LSOFE in SAP Learning Solution for SAP S/4HANA. The
core(backend) of Learning Solution is still part of EA-HRGXX which is already available in
SAP S/4HANA (S4CORE) and it enables customers to continue using SAP Learning Solution
and SAP Enterprise Learning Environment in SAP S/4HANA as part of the Compatibility
SAP Learning Industry Pack until 2025. The add-on S4LSOFE is available as of October 30th, 2020. SAP Learning
2966518,
LSOFE 600 Solution Front- Solution- Solution for SAP S/4HANA provides Learning Portal for learners in S/4HANA.
2383837
End Standard SAP S/4HANA does not contain the NetWeaver Application Server for Java (AS Java).
Therefore, the Java components such as the Java based content player, authoring
SAP and 3rd environment and offline player, need to be deployed on a stand-alone-server. For this SAP
NW 7.5 AS Java can be used.
party Add-ons With the release of SAP Human Capital Management for SAP S/4HANA, on-premise edition
(SAP HCM for SAP S/4HANA) in 2023, SAP Learning Solution with LSOFE will be part of the
Impact(3/5) product offering. The support of SAP Learning Solution continues after 2025 in SAP HCM
for SAP S/4HANA.

S/4HANA 2023.
Vendor
party)
SAP E-Recruiting is part of the SAP S/4HANA compatibility scope, which
comes with limited usage rights. SAP E-Recruiting with component
ERECRUIT was technically available in SAP S/4HANA releases 1511,
1610 and 1709. SAP S/4HANA releases 1809 and higher, ERECRUIT is
not available anymore. A new add-on product called SAP E-Recruiting for
SAP S/4HANA has been released on 15.03.2023 for releases 1809 and
higher. This add-on product is also available for a standalone installation
based on ABAP FND 1809 FOR HANA, S/4HANA Foundation release
1909 or higher. Customers can continue to use SAP E-Recruiting in SAP
S/4HANA in the Compatibility Mode until 2025. Please refer to SAP Note
3029126 – SAP E-Recruiting for SAP S/4HANA: Release Information Note
(RIN).
SAP SuccessFactors Recruiting Management is the go-to solution for
Industry 2608611, recruiting. For customers - not willing or able to move to SF, can use SAP
ERECRUIT 600 E-Recruiting Solution- 2383888, E-Recruiting for SAP S/4HANA. SAP E-Recruiting in Compatibility Mode
Standard 3029126 and HCM for SAP S/4HANA is not available in the RISE with SAP S/4HANA
Cloud, private edition. If one is planning to move to RISE with SAP
S/4HANA Cloud, private edition one needs to replace SAP E-Recruiting
with SuccessFactors Recruiting Management.
The add-on product version SAP E-Recruiting for SAP S/4HANA needs to
be part of the target stack for the system conversion to SAP S/4HANA
1809 or higher release. This should get added to the target stack by the
maintenance planner, if the source stack contains E-Recruiting instance
SAP and 3rd and target stack meets the minimum Support Package Stack (SPS)
criteria.
party Add-ons There are no application-related actions required to move from SAP E-
Impact(4/5) Recruiting 6.0 to SAP E-Recruiting for SAP S/4HANA 1.0. SAP E-
Recruiting for SAP S/4HANA 1.0 is functionally equivalent to EHP7/EHP8
of SAP E-Recruiting 6.0.

S/4HANA 2023.
Vendor
party)
Industry SAP Fiori - GBAPP002 600 (SAP Fiori oData component for Approve Purchase
2131368,
GBAPP002 600 GBAPP002 Solution- Orders 1.0) Installation for Fiori. Existing Fiori UX app to be undeployed and
2011192
Standard post-upgrade should be re-deployed. MM Fiori APP will not work in S/4 Hana
SAP Multiresource Scheduling enables one to find suitable resources for
demands and assign them to the demands. Demands are units of work from
the areas of Plant Maintenance, or Project System, for which a resource is to
be planned.
As per PAM, existing SAP MRSS 8 needs to be upgraded to ‘SAP Multiresource
Scheduling 1.0, option for SAP S/4HANA’.
First upgrade planning should be done using maintenance planner as
Multi Resource 2332631, specified in note 2914011, then,
MRSS 800 Service SAP AddOn 2332632, Manual pre-conversion steps needs to be executed. Ensure that any custom
Scheduling 2914011 implementations or enhancements related to MRS or any such developments
that make use of MRS objects are disabled/deactivated manually.
SAP Multiresource Scheduling for SAP S/4HANA does not support the material
master enhancement for requirements profiles. If AA Motors has been using
this functionality, they must copy the values for fields in the /MRSS/*
namespace from table MARC to a custom table. They must do so before your
conversion to SAP Multiresource Scheduling for SAP S/4HANA, otherwise data
might be lost.
SAP Supported Conversion to S/4HANA. Manual pre-conversion steps needs to be
Multiresource 2332631, executed. Ensure that any custom implementations or enhancements related
SAP and 3rd MRSS_NW 800
Scheduling for
SAP AddOn
2914011 to MRS or any such developments that make use of MRS objects are
SAP NetWeaver disabled/deactivated manually.
party Add-ons 2451380, SAP_APPL 618 has adopted this SRA component and retrofitted to S4CORE.
Purchase Order Industry
Impact(5/5) SRA020 600 Status (In Solution-
2465146, Needs to be uninstalled.
2034588, This add-on product versions needs to be uninstalled using transaction SAINT
Process, Appro AddOn
2131360 - when the stack xml is consumed by the software update manager.

Functional
Assessment- SAP S/4HANA 2023 will impact 76 business processes with new,
Detailed Findings changed or obsolete features. Approximately 42%
(1/2) of the L4 Business Processes in AA MOTORS - SR2 Source system are expected to be impacted.
Business Processes Not Impacted Impacted Total

Billing 8 3 11
60
Enterprise Asset Management 4 2 6
Financial Accounting 36 15 51 50
Financial Supply Chain

1 0 1 40
Management
Foreign Trade / Customs 0 1 1 30
Inventory and Warehouse
9 3 12 20
Management
Management Accounting 17 11 28 10 Impacted
Master Data 0 3 3 Non Impacted
0
Product Lifecycle Management 3 5 8
Financial Supply Chain…
Inventory and Warehouse…
Product Lifecycle Management
Project System
Master Data
Sales
Treasury
Billing
Enterprise Asset Management
Financial Accounting
Quality Management
Foreign Trade / Customs
Purchasing
Management Accounting
Production Planning
Shipping and Transportation

Production Planning 0 3 3
Project System 0 5 5
Purchasing 4 11 15
Quality Management 0 1 1
Sales 13 7 20
Shipping and Transportation 8 5 13
Treasury 0 1 1
Total 103 76 179
Functional
Assessment- SAP S/4HANA 2023 will impact 76 business processes that belongs to
Detailed Findings around 15 of the scenarios with new, changed or obsolete features.
(2/2) Approximately 42% of the L4 Business Processes in AA MOTORS - SR2 Source system are
expected to be impacted.
Scope for
Business Processes Major Minor Obsolete Total
Improvement 16
14
Billing 0 0 0 3 3
12
Enterprise Asset Management 0 0 0 2 2 10
8
Financial Accounting 0 11 2 2 15
6
Obsolete
Foreign Trade / Customs 1 0 0 0 1 4
2 Scope for Improvement
Inventory and Warehouse
0 1 0 2 3 0 Minor Impact
Management
Enterprise Asset…
Inventory and…
Product Lifecycle…
Foreign Trade /…
Shipping and…
Management…
Project System
Treasury
Master Data
Sales
Billing
Financial Accounting
Purchasing
Quality Management
Production Planning
Major Impact
Management Accounting 0 5 1 5 11
Master Data 3 0 0 0 3
Product Lifecycle Management 0 4 1 0 5
Production Planning 0 2 0 1 3
Project System 0 0 0 5 5
Purchasing 0 1 1 9 11 Major Impact: Major change in functionality. Both end
user and configurations are impacted.
Quality Management 0 0 0 1 1 Minor Impact: Most of as is transactions are available.
Some new functionalities or fields are provided.
Sales 1 2 0 4 7
Scope for Improvement: Existing functionalities
Shipping and Transportation 0 2 0 3 5 will work as it is, however, there is scope for improvement.
Treasury 1 0 0 0 1 Obsolete: The function is not required in S/4Hana.
Either this is included in other function or automated with
Total 6 28 5 37 76 another process.
Note: The business process impact has been analysed by comparing the configured
processes in the AA MOTORS - SR2 system with the IBM reference process model for SAP
S/4HANA 2023
Functional Assessment Key Findings SAP S/4HANA 2023 Key wheel display the key processes on the
basis of impact for conversion.
5 General Ledger
1 Letter of Credit
The new Universal Journal merges Financial
Letter of credit processing is provided by integration of Accounting (FI) and Controlling (CO) providing a
S/4HANA Sales with Trade Finance single source of truth for external + internal
reporting and ensuring reconciliation by design
2 Business Partner (BP)

6 Fixed Assets Accounting
Business Partners are mandatory with SAP S/4HANA
for Customer/vendor master data maintenance and New Asset Accounting is mandatory for S/4HANA.
Asset Accounting functionality is enhanced and
Customer Vendor Integration (CVI) needs to be
completed prior to S/4HANA conversion SAP named as New Asset Accounting - integrated with
new GL accounting
3 Credit Management 7 Bank Account Management

Credit Management (FI-AR-CR) is not available as part of
The old transactions of house bank accounts are
S/4HANA. The functional equivalent in S/4HANA is SAP
not available (coming with Cash Management and
Credit Management (FIN-FSCM-CR)
Liquidity Planner) in S/4HANA. Instead, one must
manage house bank accounts in the new bank
account master data, using either the Basic Cash
4 Cash and Liquidity Management Management capability or full
The Classic Cash and Liquidity Management (Cash
and Liquidity Planner) is not available in S/4HANA. All
8 Dealer Business Management
SAP Business Suite Customer using Classic Cash and
Liquidity Management needs to activate new SAP DBM (Dealer Business Management) is SAP's
S/4HANA Finance for cash management after solution for automotive dealers. SAP DBM ( Dealer
converting to S/4HANA business Management ) provides the solution for
automotive sales side and after sale side.
Show Major Minor Scope for

Stopper Impact Impact Improvement
Functional Assessment Key Findings
1 Bank Account Management

With the use of SAP S/4HANA, the old transactions of maintaining house bank accounts are not available (coming with Cash Management and Liquidity Planner). Instead,
one must manage house bank accounts in the new bank account master data, using either the Basic Cash Management capability or the full scope of Bank Account
Description Management (with SAP S/4HANA Finance for Cash Management). All apps must be accessed from Fiori Launchpad. One can reduce use of G/L accounts as bank accounts
by simplifying bank relationship-management processes.
House Bank account is in use.
AA MOTORS Source System Transactions F110, FEBAN, FI02, FI01, FI12, FI03, FBZP are used.
- See SAP note 2165520 for differences between BAM Lite and BAM.BAM Lite is a basic version of Bank Account Management which is part of basic cash management
capability - provided for customers not having license for SAP S/4HANA Finance for Cash Management.- Before go live with SAP S/4HANA, one needs to migrate house bank
accounts if there are any.
Action / Impact -Deprecated App: Manage Banks The Manage Banks app has been deprecated from the SAP Fiori launchpad as of SAP S/4HANA 2023. The Manage Banks - Basic tile, a
variant of the Manage Banks app, is also deprecated. Manage Banks and Manage Banks
- Basic will be deleted from the SAP Fiori launchpad in SAP S/4HANA 2025. SAP recommends to switch to the successor apps Manage Banks - Master Data (F6437) and
Manage Banks - Cash Management (F1574A) as soon as possible.-Check Note – 2913590 for error messages.
1. Flexible and enhanced control of Bank data by changing it to master data.
2. Fiori Apps available for House banks creation, Bank Accounts creation, Make Bank transfer etc.
Benefits 3. Flexible Fiori-based workflows for bank account activation
4. Simplification of Chart of Accounts by reusing bank reconciliation GL accounts and clearing GL accounts for house bank connectivity
5. Manage bank account group and hierarchies, bank account maintenance process, analyze bank fee data.

2 Billing Output Determination

In SAP S/4HANA, a new output management approach has been implemented and is set as the default for newly created billing documents. The target architecture is based
on Adobe Document Server and Adobe Forms.
Description By design, the new output management includes cloud qualities such as extensibility enablement, multi tenancy enablement and modification free configuration. So,
complete configuration differs from the NAST configuration. The configuration is based on BRF+ which is accessible for Customers.NAST will be supported according to
mainstream maintenance frames for SAP S/4HANA release. However, investment in the Output management area will only be made within the new framework.
Billing/Invoice List Output functionality is in use.
AA MOTORS Source System Transactions VV33, VV32 are used.
As there are valid requirements and use cases for both frameworks with release S/4HANA, there is a new customizing activity "Manage Application Object Type Activation"
where the active framework can be maintained. One can find the Customizing under output control in SPRO, Choose 'Application Inactive' if one wants to switch back to
NAST.
As per SAP Note 2248229, when one starts newly with the SAP S/4HANA system, there are ZIP files in this note, one can pick up matching S4CORE version to begin with
BRFplus output management setup. Flexible output determination is possible using BRFplus, it can be based on app-specific fields that are extendable. It can be sent to
many different channels, there is no limit when designing determination rules.
After a system conversion to SAP S/4HANA, if SAP S/4HANA output control is activated, Old documents that are migrated from an SAP ERP system, can still be processed
with their existing output solution (e.g. NAST). New documents created directly in SAP S/4HANA system will use the new SAP S/4HANA output control. In general, the
Action / Impact documents stay with the output solution which was active at the time of their creation.
Output management is activated by object. It means if for example, the object Purchase order is activated then ALL the new purchase orders will work with the new
framework regardless of the document type.
In contrast to the output management based on NAST the new output management supports only the Channels PRINT, EMAIL, XML (for Ariba Network Integration) and
IDOC (for on premise). Other channels are not supported by default.
SAP S/4HANA output control introduces an enhanced check for output devices defined within the spool administration, which are used for printing of output request items.
SAP S/4HANA output management supports SAPscript and Smart Forms for applications that used NAST before. Other applications need to explicitly support existing form
technologies available in SAP S/4HANA Output Management. ADS is required for this scenario. In any case, adjustments to the print programs must be made when using
existing form technologies. SAP recommends using Adobe Document Services when starting newly with SAP S/4HANA output control.
The new output management for SAP S/4HANA only supports the "pure" output channels, while the NAST-based output can also be used for several kinds of post-
processing. Output management for SAP S/4HANA cannot be used if any one of the NAST transmission mediums is required:
8 Special function,
9 Events (SAP Business Workflow),
A Distribution (ALE),
Benefits T Tasks (SAP Business Workflow).SAP S/4HANA Output Controlincludes cloud qualities such as extensibility enablement, multi- tenancy enablement, and modification-free
configuration.The configuration is technically based on BRFPlus, which is accessible in the cloud.The architecture of SAP S/4HANA output management is based on Adobe
Document Services and SAP Cloud Platform Forms by Adobe. Hence it has all the existing advantages of Adobe print over Smart Forms or Sap Scripts.
Standard sample forms (Commercial Invoices, Invoice for Professional Services, Credit Memo etc.) for various countries are available which can be easily adapted by the
customers for their own form and layout.

3 Business Partner (BP)

Customers and Suppliers (Vendors) will be created as Business partner through transaction code BP and Customer and Vendor master data will be available in tables such
Description as KNA1/KNB1, LFA1 etc. and at transactions level as it is now.
Customer Master / Vendor Master are in use.
AA MOTORS Source System Transactions XD02, XD01, XD03, XD04, VD03, XK03, FK03, XK02, XD07, FD03 are used.
- Convert the customer/vendors to BP using CVI. - Transactions such as XK01, XK02, XK03 are obsolete, and replaced by transaction BP.
- Maintain the required customization only for customers to determine the tax
Action / Impact - Do not configure the time dependency for the BP data.
- The Business Partner Approach is not mandatory for the SAP Simple Finance, on_x0002_premise edition 1503 and 1605.
-The business partner is the new and leading object in SAP S/4HANA, combining vendor and customer data in one central object and thus simplifying the data structure and
master data management.-Centralized and common approach for data maintenance.
-In classical transactions, one customer can only be associated to one account group. But in Business Partner, multiple roles can be associated to the same Business
Benefits Partner.
- Business Partner allows maintenance of multiple addresses with corresponding address usages.
- Maintenance of Time Dependency at different sub-entities roles, address, relationship, bank data etc.
- Maximal data sharing and reuse of data which lead to an easier data consolidation

4 Cash and Liquidity Management

The Classic Cash and Liquidity Management (Cash and Liquidity Planner) is not available in S/4HANA. Cash management in SAP S/4H has been split into ‘The Basic cash
Description management’ and ‘SAP S/4HANA Finance for cash management’ (Depending on the license).
Cash Management is active.

AA MOTORS Source System Transactions FF67 is used.
- Depending on the license, one can check whether to use a basic scope of Cash and Liquidity Management or full scope of SAP S/4HANA Finance for Cash management.
- For customers who want to move from the classic Cash and Liquidity Management to SAP S/4HANA Finance for cash management, they have to
a) Convert their system to SAP S/4HANA or set up a new SAP S/4HANA system.
b) Activate and then implement SAP S/4HANA Finance for cash management. In order to do that, one needs to switch on the business function FIN_FSCM_CLM to gain the full range
of functions for this solution. This BF is integrated with Bank Communication Management (FIN-FSCM-BNK), Treasury and Risk Management (FIN-FSCM-TRM), Consumer and
Mortgage Loans (FS-CLM), SD, MM, FI-CA, SAP Liquidity Planner.
- A number of FF* and FLQ* transactions are obsolete.Basic Cash Management capability can integrate with data sources – MM, SD, FI-CA, FS-CLM (Consumer and Mortgage Loans).
The link from classical Cash Management to the Treasury and Risk Management analyzers (transactions RMCM and KLMAP) has been disabled in S/4HANA.
Instead, SAP S/4HANA Bank Account Management is integrated with the Market Risk Analyzer and the Credit Risk Analyzer of the Treasury and Risk Management by a new type of
Action / Impact financial object for bank account balances.
SAP S/4HANA Finance for cash management – advanced capability can integrate with above data sources – and also FIN-FSCM-BNK (Bank Communication Management), RE-FX
(Flexible Real Estate Management), SAP Liquidity Planner.The functions provided by Cash Operations for China have been replaced by the solution Cash and Liquidity Management
under component FIN-FSCM-CLM. The functions provided by EPIC embedded Cash Budgeting have been replaced by Cash Budgeting in SAP S/4HANA Finance for cash
management, version for China - SAP Note 3087756.
Flow Builder Plus is a module to generate cash flow items from Accounting (FI) and MM source applications. From OP2021 FPS1, Flow Builder Plus is an option to generate cash
flow items for FI and MM source applications. From OP2022, once upgrade is finished, Flow Builder Plus is mandatory if one still need to populate cash flow items from cash and
liquidity management. Cash flow analysis by liquidity item could be more accurate, for example, even if the actual outgoing payment is netted from Account Payable and Account
Receivable, the liquidity item derivation can reveal as if it was not netted and retrieve the separated liquidity items for Account Payable and Account Receivable on corresponding
split amounts.
1. End-to-End process of monitoring bank statement imports, checking cash positions and transferring fund to handle surplus and deficit.
2. Better visibility of Cash Position and Cash Flow - De-coupling cash position from GL accounting as one can create direct cash position based on bank statement. Flow Builder 2.0
allows to improve cash flow analysis using precise derivation tool following classical liquidity planner. Fiori application to manage bank account balance, manually upload balance,
Power of Attorney to ensure complete SoD and signature moving to treasury and cash management. The cash operations functionality of the new cash management in SAP
S/4HANA provides with real-time cash position reporting capabilities. As soon as bank statements are imported, one can immediately check on cash position, without any
dependence on accounting. The cash position is updated whether one posted the bank statement or not.
3. Medium term Liquidity Forecasting and rolling plans of long-term liquidity. There are powerful tools for cash position analysis, with navigation from high-level to detail-level
Benefits analysis, drilling down to the line-item report and even further down to the original business transactions.
4. Enhancement of Cash concentration, bank transfer, and cash trade request apps - increase in efficiency of cash operations. The SAP Fiori apps for cash management in SAP
S/4HANA provide seamless integration from insight to action, that is, from the analytical view to the transactional level.
5. Centralized bank account management, with which business users can manage bank accounts as master data with more business attributes.6. Using flow builder plus, gain real-
time insight into global cash and liquidity management. Capture cashflows from across the enterprise in a central view. Obtain up-to-date cash position and cash flow forecasts in
real-time. Develop a long-term liquidity forecast using embedded planning tools.
Flow Builder Plus, put ‘a better performance and ensure a zero Out-Of-Memory issue’.

5 CO-OM Planning
CO-OM planning, P&L planning, and profit center planning are now covered by SAP BPC for S/4HANA Finance (formerly known as Integrated Business Planning) -SAP Note
Description 2081400.
If customer calculates planned costs for production orders, no business process changes are required, but information in the new planning table is only visible in Fiori apps.
CO-OM Planning scenarios are active.
AA MOTORS Source System Cost Center, Internal Order, Profit center Planning are activated
Transactions KA01, KSB5, KS03, KA03, KL03, KS13, KS02, KABP, KSB1, KSBL, KCH1, KCH2, KCH3, KO01, KO03, KO04, KO05 are used.
'Classical Profit Center Accounting (PCA) is part of the SAP S/4HANA compatibility scope. Alternative functionality "Profit Center Accounting on Universal Journal" in SAP
S/4HANA.
SAC is the recommended financial planning solution for SAP S/4HANA Cloud and On Premise. Only for customers requiring an On-Premise planning solution, BPC Optimized
for SAP S/4HANA still is recommended.
Integrated Financial Planning for SAP S/4HANA with SAP Analytics Cloud consists of three pillars:
• The planning tool "SAP Analytics Cloud" that provides
o generic data input and data import capabilities
o a planning engine powered by SAP HANA
o a full-blown modeling environment for planning models, input layouts
Action / Impact • A dedicated connector for SAP S/4HANA Cloud and On Premise
o that includes the suitable OData services within S/4HANA
o that can read all relevant data from S/4HANA and write the plan results back to S/4HANA
• Pre-delivered Financial planning content package ‘Integrated Financial Planning for SAP S/4HANA’ that covers all financial planning areas
o Expense and activity planning, Product cost planning, Sales and profitability planning, P&L-, Balance Sheet- and Cash Flow planning
- In case, customers cannot transition to SAP BPC optimized for SAP S/4HANA and would need to continue with classic CO-OM planning functions, one can do so, but these
transactions are not included in SAP Easy Access menu. Also, these will not update ACDOCA table. Legacy reports will work, but Fiori apps will not display these data.
- Planning data that existed prior to migration will not be a part of universal journal which means it will only be available for viewing purpose and cannot be used for reports
in combination with new fields.
- SAC removes the separation between reporting and planning, meaning that separate planning environments are no longer necessary. The actual data can be integrated
Benefits into different planning versions.
- Flexible drill-down on drivers of profitability, including customer, product, geography, and channel

6 Cost Element Accounting

Cost Element creation process is through G/L accounts. Secondary Cost Element with S/4HANA becomes a G/L account. Default Cost center assignment maintained in Cost
Description element master is migrated to T code OKB9.Cost element attribute mix does not exist any longer.
Cost element accounting is active.
AA MOTORS Source System Transactions KA01, KA02, KA03, KP06, GRR2, S_ALR_87013611, KS03, KS02.
Cost Elements provide information concerning the value flow and value consumption within the organization. A cost element corresponds to a cost-relevant item in the chart
of accounts.
Primary cost elements reflect operating expenses such as payroll (personnel cost), selling expenses (material cost), or administration costs.
Secondary cost elements represent costs resulting from value flows within the organization, such as internal activity cost allocations, overhead allocations, and settlement
transactions.
In the past, postings on secondary cost elements in CO effecting GL reporting entities (e.g., profit center, functional area) created real time integration postings on primary
Action / Impact G/L accounts! For the real time integration, a mapping of secondary cost elements to primary accounts was necessary.
With S/4HANA postings on G/L accounts with account type ‘secondary cost elements’ appear directly on the same account in GL reporting.
No mapping between different accounts is needed!
The P&L versions have to be updated accordingly, that means one needs to include the secondary cost elements for reporting purposes.
To maintain primary and secondary cost elements one needs authorization for both GL Accounts and Cost elements.
Design for Chart of Accounts must include all P/L accounts and secondary cost elements that represent value flows within the company.
Existing GL Accounts and cost elements are migrated into new data model automatically by a separate step within migration process.
1. Seamless master data management
Benefits 2. Secondary Cost Elements can be depicted in Trial Balance and FSV3. Cost elements move into GL account logic that means - No time dependency for cost elements any
longer! Also, no default account assignments for cost elements in master data maintenance.3. SAP BPC available for integrated planning.

7 Credit Management
Description Credit Management (FI-AR-CR) is not available as part of SAP S/4HANA. The functional equivalent in SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR).
FI-AR-CR Credit Management is NOT active. Though transaction FD11 is used.
AA MOTORS Source System FIN-FSCM-CR SAP Credit Management Active. Transaction UKM_TRANSFER_ITEMS and Program UKM_CASE, UKM_COMMTS_DELETE, UKM_ITEM_DISPLAY,
UKM_MY_DCDS, UKM_RVKRED77 are used.
SAP Notes 2217124 and 2227014 can be referred to.
1.A number of transaction in existing credit management process will be obsolete and few will be replaced by new transaction.
2. If the customer is using only FI-AR-CR OR both FI-AR-CR+FIN-FSCM-CR - then, they need to migrate FI-AR-CR to FIN-FSCM-CR completely. This migration comprises -
Config, master data, credit exposure and credit decision data. There are few pre-requisite, that should be checked and completed. Also, implementation of BADI
'UKM_R3_ACTIVATE' and 'UKM_FILL' should be reviewed.
3. A number of Fiori apps are available. One important in current release is –
Action / Impact Manage Credit Accounts app - a 360° view on all credit accounts, combining operational with reporting data, it gathers all details related to a business partner in addition to
score, limit and payment trends.
Manage Credit Management Rules app - credit manager can define rules for different use cases, like ‘Approval hierarchies for credit limit requests and DCD’, ‘Define
rounding rules for the calculation of credit limits – and risk adjustments based on risk class.
If Advanced Credit Management functionalities are to be used, then transaction UKM_CHECK_MD can be used to check master data for inconsistencies, inconsistent
customizing, as these inconsistencies can cause errors when starting the Fiori application Manage Documented Credit Decisions (F5587).
- Higher degree of automation: automatic calculation of credit scores, risk classes and credit limits, documented credit decisions.
- Less redundant data (reading FI-data via HANA view)
Benefits - Integration with external credit rating agencies for credit rating of the customers
- Credit events help the credit analyst to focus on exceptions during his daily business.

8 Delivery Insights enabled by IoT

Delivery insight empowered with Internet of Things - Using real time insights provided by SAP IoT the company can now plan production more reliably and increase
Description efficiency in subsequent processes. In case a critical situation occurs such as potential material damage, or delay of the delivery the responsible person is immediately
notified in the S/4HANA Fiori Launchpad. This ensures quick reaction within his or her natural working environment.
Outbound Delivery is active.
AA MOTORS Source System Transactions VL10B, VL01N, VL02N, VL10X, VL03N, VL06O, VL32N, VL10, VL06I, VL06F are used.
In S/4HANA, Delivery Management is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles.
In Delivery Management, all delivery procedure decisions can be made at the start of the process by:
Taking into account general business agreements with your customer
Recording special material requests
Defining shipping conditions in the sales order
The result is an efficient and largely automatic shipping process in which manual changes are only necessary under certain circumstances.
The Delivery Management component is integrated under the Logistics Execution component. Delivery Management is a subsequent activity of Sales.
Action / Impact Related Processes for Outbound Deliveries
• Creating and Processing Outbound Deliveries
• Picking
• Packing
• Goods Issue
• Printing and Communication in Delivery Management
• Special Functions in Shipping
Benefits Continuous monitoring of transportation conditions in real time with the integrated IoT capabilities in SAP S/4HANA.

9 Enterprise Asset Management

SAP S/4HANA Enterprise Asset Management (includes SAP PM) improves maintenance execution by utilizing real-time data so a plant foreman can quickly troubleshoot
issues. It also helps keep tabs on important safety information such as incident rate which can help reduce downtime by scheduling planned maintenance and inspections.
Description It also, provides ways to ensure that those components are running the way they should. Managing the status with SAP Fiori apps means maintenance team can have
relevant information at their fingertips via a mobile device. If something goes wrong, they’ll be alerted right away and can dispatch help to wherever the issue occurred.
AA MOTORS Source System Transactions /MRSS/PLBOGEN, /MRSS/PLBOORGM, IK12, IK17, IK13, IE03, IK01, /MRSS/PLBOORG, IE02, /MRSS/UTILREP are used.
- SAP S/4HANA Asset Management’s preventive maintenance functionality provides users with the tools needed to schedule and perform preventive maintenance activities.
SAP Fiori Maintenance Planning Overview apps allow maintenance planners the ability to check unprocessed maintenance requests, POs, and other relevant metrics.
Another helpful SAP Fiori app is the Maintenance Scheduling Board app.
With these, one can
-- Analyze outstanding notifications that have not yet been processed and that have not yet been assigned to a maintenance order
-- Analyze maintenance orders that are still in planning and have not yet been released for processing
-- Display non-stock materials that have been ordered but may not be available on the requirement date
-- Analyze released maintenance orders whose end date is in the past and have still not been finally confirmed
- Use transactions IW37n, IW49n, IP30H instead of IW37, IW47, IP30. IP30H is enabling Real Time Maintenance Plan Scheduling – resulting in Accelerated Mass
Action / Impact Transaction, instant analysis on top of transactions, real time analysis of machine sensor information, planning can be done several times in a day, faster response time for
more accurate maintenance scheduling.
- Enhancements and modifications of the LIS will not work. - Customers can check whether to use SAP Predictive Maintenance and Service that combines sensor data with
business information to help improve service profitability, reduce maintenance costs and increase asset availability.
- EAM is integrated with IoT, Big Data, AI/ML, Mobile solutions
IoT – to provide sensor-enabled condition monitoring for real-time insights.
Big Data to enable real-time analysis of data streaming from assets that are getting smarter and can communicate status and performance data.
AI and ML – to bring unprecedented insights and automation of knowledge work across the enterprise.
Mobile Solutions – to provide workers in the field with easy access to necessary information they would otherwise need to access in the office.
More Predictive and Preventive maintenance in S/4HANA – less of Reactive Maintenance.
- Once LIS table update is switched off, there will be improved performance of many transactions, less memory requirement.
- SAP Predictive Maintenance continuously improve processes and predict outcomes, collaborate across networks and offer differentiated service, while generating new
revenue streams and developing new ways to compete and disrupt industry.
Benefits - SAP Fiori brings a whole host of applications that make asset management tasks easier.
- Increased reliability to identify failure modes of an equipment, and also identify main causes observed by technicians and plan preventive or inspections activities to avoid
future unplanned breakdown

10 Fixed Assets Accounting

Asset Accounting is based on the universal journal entry. This means there is no longer any redundant data store. Asset Accounting functionality is enhanced and named as New
Asset Accounting - integrated with new GL accounting. Integrated Asset acquisition is changed, Periodic APC Posting is obsolete, all changes to asset balances are posted to the
Description general ledger in real time or immediately. Legacy data transfer changed, Significant speed-up of asset depreciation run.
Asset Accounting is based on the universal journal entry. General Ledger Accounting and Asset Accounting are therefore reconciled per se; this means that reconciliation postings
are not necessary as part of closing operations.
Classic Asset Accounting is active.
AA MOTORS Source System Transactions AS01, AS03, AIBU, AS02, AFBP, AFAB, ABZON, ABAON, F-92, S_ALR_87012936 are used.
- In new Asset Accounting one can map parallel valuations with the ledger approach or accounts approach. A mixture of the two is not supported.
- Execute Pre-check programs to analyze Asset Accounting readiness for conversion
- Additional customizing
- Data Migration- New Asset Accounting is mandatory in S/4HANA. It will be activated as part of System Conversion.- The Asset Accounting tables - ANEA, ANEK, ANEP, ANLC, ANLP
are no longer updated in S/4HANA, but selection from these tables are directed to corresponding compatibility views. They make the information from the new data store available
in the format of original tables. Actual data of ANEK, ANEP, ANEA, ANLP, ANLC is now stored in table ACDOCA. ANEK data is stored in BKPF.
Action / Impact - The functionality group assets in Asset Accounting is part of the SAP S/4HANA compatibility scope, which comes with limited usage rights. SAP does not plan to provide an
alternative for group assets in Asset Accounting.
- Classic Asset Accounting is mostly transformed automatically into the New Asset Accounting by executing mandatory migration steps related to Asset Accounting.
- One can post the depreciation amounts periodically, directly in General Ledger Accounting. One can create an asset history sheet in S/4HANA to represent the development of the
fixed asset from the opening balance through to the closing balance.
- Check during migration to Asset Accounting (new) if an error message tells that alternative fiscal year variants (FYVs) are assigned in the general ledger accounting ledgers then
check SAP note 2220152.
- Integrated Asset Acquisition. One “Technical clearing account” is to be defined for integrated asset acquisition. A business transaction created using integration is split by the
system into the operational part and the valuating part. A posting is made in each case against a technical clearing account. For the asset acquisition using integration one will
require a new technical clearing account for integrated asset acquisition; however, for the asset retirement using integration the existing clearing accounts asset retirement with
revenue and asset retirement clearing are used. The operational part is posted across accounting principles, the valuating part is posted accounting-principle-specifically.
- Periodic APC Posting is obsolete. Because all APC changes in Asset Accounting are posted to the general ledger in real time.
- Significant speed-up of asset depreciation run. New program for posting depreciation (depreciation run) – one can compare an asset depreciation over two depreciation areas.
- Fiori-based dashboards available for reporting
Benefits - No more hard coupling of depreciation area 01 (delta areas). The system now posts both the actual values of the leading valuation and the values of parallel valuation in real time
in separate documents. This means the posting of delta values has been replaced; as a result, the delta depreciation areas are no longer required and are no longer supported.
-Always separate documents per accounting principle (FI-AA)
- Posting for group-assets are redundancy free.
- Parallel Valuation for each asset related transaction is done in real-time. For each asset-related transaction (acquisition, capitalization of assets under construction (AUC),
retirement, post-capitalization and so on), the asset values for all posting depreciation areas are updated in Realtime.
- Reconciliation postings are no longer necessary with closing operations as General Ledger Accounting and Asset Accounting are reconciled permanently anyway due to the
universal journal entry.

11 General Ledger
The new universal journal entry replaces the Financial Accounting (FI) document and the Controlling (CO) document with a universal document. Finance reconciliation is no
Description longer required providing a single source of truth.General Ledger in S/4HANA is based in the Universal Journal, the line items are stored in the new database table ACDOCA,
optimized for SAP HANA.
New GL accounting is active. Document Split Active.
AA MOTORS Source System Transactions FBL5N, FBL3N, FBL1N, FAGLB03, FB1S, FAGLL03, FSE3, FS00, FBL3, GLPLUP are used.
No immediate action required. The data will be migrated from the old data structures to the new data structures as part of the system conversion. The new general ledger is
introduced mainly as a result of the need to support multiple valuation methods.- Before Migration, FINS_MIG_PRECHECK transaction should be executed to clean up all
inconsistencies prior to migration.
- Configuration steps in FIN Migration workbench in SPRO should be followed - 'preparation and migration of customizing for the general ledger' in its sequence in the UI.
Also, the last step, 'Execute Consistency Check of General Ledger Settings' should be performed and solve errors if any.
- Use of new reports should be checked.
- The usage of special purpose ledger is partly included in the SAP S/4HANA compatibility scope, which comes with limited usage rights. Special ledgers and respective
Action / Impact tables and reports which have been defined for applications that are part of the compatibility scope will not be supported beyond expiry date – End of 2025.
With SAP S/4HANA, it is possible to create different Ledgers for different accounting principles. That is, one ledger for Local GAAP, one for US GAAP, one for IFRS, one
ledger with different fiscal year other than the one being used in the company code etc. In SAP terminology, these are called Leading Ledger and Non-leading Ledgers. The
ledger for Local GAAP is called Leading Ledger and all others are non-leading ledgers.
- Document splitting is a function of new General Ledger Accounting. It is comparable with document splitting for special purpose ledgers (FI-SL).- In SAP S/4HANA the
contents of the cost of sales ledger and all special ledgers created in table GLFUNCT are included in the Universal Journal (table ACDOCA).
Check SAP Note 2431747 to know more about - Incompatible Changes in S/4HANA compared to classic ERP releases.
1. Reconciliation between FI and CO is not required due to Universal Journal
2. New fields available in the 'control' tab to create GL accounts as cost elements3. Universal Journal significantly changes the way transactional data is stored for financial
Benefits reporting. it offers huge benefits in terms of ability to harmonize internal and external reporting requirement by having both read from same document store whether the
account is the unifying element.

12 Intelligent Product Proposal

Users can use this feature to receive product and quantity proposals as an input help to select products and quantities quickly when creating sales orders in the Create Sales
Orders – VA01 app. This feature provides product and quantity recommendations based on historical data, while considering product listings and exclusions for the product
Description proposals.
In addition, the intelligent product proposal allows customers to predict whether the quantity of products ordered will increase or decrease.
Sales Order is active.
AA MOTORS Source System Transactions VA02, XK15, VA01, VA03, VA05, V/LD, VA05N are used.
This feature is based on the dynamic product proposal framework, one must carry out all the settings in Customizing for Sales and Distribution under Basic Functions ->
Action / Impact Dynamic Product Proposal.The intelligent product proposal is dependent on the customer and sales document type as well as the sales area (sales organization, distribution
channel, division), and is displayed in the sales document as soon as the user has entered a customer.
- Improved sales force efficiency by using product and quantity proposals for faster sales order creation.
Benefits - Faster sales order creation helps to increase potential profitability.

13 Inventory Management
Description There is changes in Inventory Management Data Model as well as in Transactions. Fiori Apps are introduced in this area as well.
Transactions MMBE, MIGO, MB52, MB22, MB51, MB1B, MB25, MB5T, MB5B, MB90 are used. Physical Inventory transactions MI01, MI03, MI11, MI22, MI31, MIGO are
AA MOTORS Source System used.
The SAP ERP inventory management data model consists of the two document tables MKPF for document header information and MSEG for document item data.
With S/4HANA this data model has been changed significantly. The new de-normalized table MATDOC has been introduced which contains the former header and item data
of a material document as well as a lot of further attributes. Material document data will be stored in MATDOC only and not anymore in MKPF and MSEG. Additionally, the
aggregated actual stock quantities will not be persisted anymore in the hybrid or replaced aggregation tables. Instead, actual stock quantity data will be calculated on-the-
fly from the new material document table MATDOC for which some of those additional special fields are used.
SAP ERP tables in this area do still exist in S/4HANA as DDIC definition as well as database object and the hybrid tables will still be used to store the material master data
attributes. For compatibility reasons there are Core Data Service (CDS) Views assigned as proxy objects to all those tables ensuring that each read access to one of the
mentioned tables below still returns the data as before in SAP ERP 6.0.
The following transactions for entering and displaying goods movements (material documents) - called ‘MB transactions’ - below, have been replaced by the single-screen
generalized transaction MIGO or the BAPI's BAPI_GOODSMVT_CREATE and BAPI_GOODSMVT_CANCEL:
• MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST, MBSU and MBBM
These transaction codes shall not be used in customer coding because with this release a new enhanced and improved lock concept has been introduced for transaction
MIGO and the BAPI BAPI_GOODSMVT_CREATE but the above listed obsolete transactions still using the old lock concept (see note 2319579). Hence in case of parallel
posting done via one of the obsolete transactions and transaction MIGO or BAPI BAPI_GOODSMVT_CREATE one may be able to create stock inconsistencies just because
the postings are not protected by the same lock object.
Action / Impact The transaction codes will be deprecated in the near future.
One should use transaction MIGO or MMBE in dialog.
For reporting, the inventory management data is extracted from SAP ERP or SAP S/4HANA On-Premise to the Business Warehouse and made available there for further
evaluation of different stock values, quantities and movements. Possible analyzing scenarios are monitoring of current stock levels, analyzing inventory age and material
range of coverage, and detecting stock obsolescence. One can run analysis for different types of stocks, such as total or valuated stock, special stocks and consignment
stock.
Physical inventory / inventory count and adjustment helps to perform the periodic adjustments to stock on hand after a physical count.
Two physical inventory procedures:
• Sample-based physical inventory – here, the sample to be inventoried is determined on a mathematical-statistical basis. A physical inventory count and an inventory
adjustment posting are performed for the items in the sample. Based on the inventory adjustment posting, an extrapolation provides an estimated value for the entire stock.
If the extrapolation is successful, it is assumed that the book inventory is correct. Sample-based physical inventory is not available for EWM-managed storage locations.
• Cycle Counting - The materials to be inventoried are counted at regular intervals during a fiscal year. One can use the cycle counting approach, for example, to ensure that
stocks of fast-moving items are checked more frequently than slow-moving items.
• Transparent view on the stocks currently available

Benefits • Efficient processing of inventory adjustments

14 Letter of Credit
Description Letter of credit processing is provided by integration of SAP S/4HANA Sales with Trade Finance.
AA MOTORS Source System Letter of Credit is in use (Configurationwise).
SAP notes reference - 2267740, 2205202,

2223144 (Custom Code)
- The payment guarantee-related Letter of Credit has been removed from the SD side
-To guarantee sales order payment with Trade Finance, FTR_* transactions are available to process letter of credit, standby letter or credit and bank guarantee.- Would need
Action / Impact to check whether third party Foreign Trade systems are in use for Foreign Trade processes. Because of the replaced foreign trade functionality in SAP S/4HANA, it is
possible that the third-party foreign trade system will need to be adjusted by the respective third-party solution/service provider
-To migrate financial documents in Foreign Trade to Trade Finance, one should carry out steps in Finance Migration Workbench - post conversion.
Steps - Preparation and Migration of Financial Documents to Trade Finance.
Letter of Credit capabilities are now documented in the area of Treasury Management
1. A complete solution for letter of credit processing through integration of Sales and Trade Finance of Treasury and Financial Risk Management in SAP S/4HANA.
2. This supports common functionalities of Bank Guarantee, Letter of Credit and Stand by Letter of Credit.
3. The system is able to capture the clear information classification with all details. The drawing and release facility can be automatically triggered based on the changes of
the trade finance deal.
Benefits 4. Credit risk analyzer can be activated based on the product types with customizable limit rules and limit types. The utilization and release of limit can be triggered
automatically from the deals themselves.
5. One can configure approval processes for status changes and posting releases. In addition to functions for creating and changing Bank Guarantees/LC, the system also
supports functions for rollover, contract settlement, and contract termination. Cash collateral and Bank Guarantee fees are also covered.

15 Manage Customer Returns

To improve the return process, the SAP Fiori app now offers capabilities to replace ordered products with products from different plants. Additionally, there are new
Description analytics and a new approval process for returns.One can now create approval workflows for customer returns with the approvals inbox app.
Customer Returns is active.
AA MOTORS Source System Transactions VA02, VA01, VA03 are used.
Action / Impact No Action required
- Compensate customers with replacement products that are different from the returned products. In addition, one can choose a supplying plant from which the
replacement products are to be delivered. The supplying plant can be different from the receiving plant for the returned goods.
- Create and process customer returns for bills of materials (BOM) - withdifferent BOM Variant.- View approval status of customer returns. One can withdraw the approval
Benefits request for the returns that are pending approval
- Delete customer returns.- Enhancement to the existing synchronous OData API to create, read, update, or delete return orders with new functionality to create a return
order with reference to a preceding document.

16 New advanced ATP

As an integral part of the order fulfilment process, SAP S/4HANA advanced Available-To-Promise provides accurate and reliable order promise dates considering the
relevant supplies across the network and critical supply chain constraints, in real-time - integrating S/4HANA PPDS, TM and IBP Solution.In S/4HANA it is possible to
aggregate data in real time, so the aggregate-table for sales order requirements VBBS is not necessary anymore. Database table VBBS contained pre-aggregated sales
Description requirements. The requested (OMENG) and confirmed (VMENG) quantities were aggregated on a daily basis. With the new HANA ATP, customers do not need pre-
aggregation anymore, and therefore this table is obsolete. Instead of the VBBS customers must use the VBBE, where each ATP-relevant requirement is explicitly stored. The
old ERP-ATP check code is also redirected to use VBBE.
Sales Order Aggregate is in use.
AA MOTORS Source System Transactions CO06, CO09 are used.
Before S/4HANA 1709, There were two optional checks to be carried out before the upgrade to verify if the VBBS is used:
1. Start transaction "SE16" and display the entries in table "VBBS". If there are any entries, the XPRA has to run. If there are no entries, the second step has to be executed.
2. Start transaction "OVZ2" and check the entries for the fields "SUMAU" and "SUMLF". If there is any entry other than "A: Single records", the XPRA needs to be executed.
If the customers are still using table VBBS, please read the related note 2209696 how to convert the data after upgrade.
If the custom code calling table VBBS, create a db view on table VBBE, and use that view instead of the table VBBS (SAP Note: 2209696).From S/4HANA 1709 and newer
versions, all the above actions are automated and executed in SUM phase using identifying name ATP_XPRA_SUITE_TO_S4_V2. So, manual actions are not needed.Two of
Action / Impact the most-awaited functionalities in order promising in S/4HANA 2022 – Supply Creation-Based Confirmation (SBC) and Business Process Scheduling (BPS).
Supply creation-Based Confirmation (SBC) enables Make-To-Order / Assemble-To-Order business, to provide order confirmation date to customers by ability to produce the
product considering the availability of critical components and raw materials, and the bottle-neck resource capacity - integrating with SAP S/4HANA PPDS to plan and
confirm orders in real time.
Advanced Business Process Scheduling (aBPS) that has:
• Fiori app “Configure Activity Attributes” for a more granular definition of durations and working times of logistical activities for customer-specific use cases
• 2 pre-delivered BPS schemas, which provide more sophisticated scheduling capabilities.
Improvement of system performance along with –Supply creation-Based Confirmation (SBC)enabling ‘Production Planning-Based’ Availability and Product Check with
Supply Creation, Support of both ‘Sales’ and ‘Capacity’ Product Allocation for the finished product, Display of Result of the Supply Demand-Based Capability Check in
Review Availability Check Results App.Business Process Schedulinglays the foundation for further integration of ATP process with SAP S/4HANA Transportation
Management in future releases.Backorder Processing (BOP)provides mass ATP check capabilities by filtering and sorting requirements and confirming orders considering
business priorities and profitability goals. In 2022 Release, new confirmation strategy – IMPROVE – to existing 5 strategies of WIN, GAIN, REDISTRIBUTE, FILL and LOSE,
Benefits that helps BOP to run smoothly in certain exceptional scenarios.Alternative-Based Confirmation (ABC)allows to confirm sales orders based on the availability of substitute
products or plants/storage locations if supplies for the originally requested product or plant are insufficient to fulfill the demand.Product Allocations (PAL)helps companies
to avoid critical situations in demand and procurement by allocating materials in short supply to, for example, specific regions and customers for a specific time period. In
2022, additional features such as enhanced Review Product Allocation Check Result Details screen.Supply Protection (SuP)ensures minimum guarantee to certain orders by
protecting quantities of a material in a specific plant against other competing demands. In the 2022, new features - Restriction by own protection, Consistency checks,
Change/move of planning horizon.

17 Output in Purchasing
In SAP S/4HANA, a new output management approach has been implemented, the target architecture is based on Adobe Document Server and Adobe Forms.
By design, the new output management includes cloud qualities such as extensibility enablement, multi tenancy enablement and modification free configuration. So,
Description complete configuration differs from the NAST configuration. The configuration is based on BRF+ which is accessible for Customers.NAST will be supported according to
mainstream maintenance frames for SAP S/4HANA release. However, investment in the Output management area will only be made within the new framework.
Message Output for Purchase Order.
AA MOTORS Source System Transactions ME21N, ME23N, ME9F are used.
Output management based on NAST is still supported for new documents in purchase order. Purchase orders which are migrated from legacy systems and for which NAST
based output has been determined, can be processed with the new and with NAST technology. The user can decide whether he wants to use for all new purchase orders the
new output management or NAST.
After a system conversion to SAP S/4HANA, if SAP S/4HANA output control is activated, Old documents that are migrated from an SAP ERP system, can still be processed
with their existing output solution (e.g. NAST). New documents created directly in SAP S/4HANA system will use the new SAP S/4HANA output control. In general, the
documents stay with the output solution which was active at the time of their creation.
Output management is activated by object. It means if for example, the object Purchase order is activated then ALL the new purchase orders will work with the new
framework regardless of the document type.
In contrast to the output management based on NAST the new output management supports only the Channels PRINT, EMAIL, XML (for Ariba Network Integration) and
Action / Impact IDOC (for on premise). Other channels are not supported by default.
In the SAP S/4HANA 2021 release, the output solution SAP S/4HANA output control introduces an enhanced check for output devices defined within the spool
administration, which are used for printing of output request items.
Flexible output determination is possible using BRFplus, it can be based on app-specific fields that are extendable. It can be sent to many different channels, there is no
limit when designing determination rules.
As per SAP Note 2248229, when one starts newly with the SAP S/4HANA system, there are ZIP files in this note, one can pick up matching S4CORE version to begin with
BRFplus output management setup.
SAP S/4HANA output management supports SAPscript and Smart Forms for applications that used NAST before. Other applications need to explicitly support existing form
technologies available in SAP S/4HANA Output Management. ADS is required for this scenario. In any case, adjustments to the print programs must be made when using
existing form technologies. SAP recommends using Adobe Document Services when starting newly with SAP S/4HANA output control.
The architecture of SAP S/4HANA output management is based on Adobe Document Services and SAP Cloud Platform Forms by Adobe. Hence, it has all the existing
advantages of Adobe print over Smart Forms or Sap Scripts.
The new output management for SAP S/4HANA only supports the specific output channels, while the NAST-based output can also be used for several kinds of post-
Benefits processing. Output management for SAP S/4HANA cannot be used if any one of the NAST transmission mediums is required: ‘8’ Special function, ‘9’ Events (SAP Business
Workflow), ‘A’ Distribution (ALE), ‘T’ Tasks (SAP Business Workflow).
It is fully integrated with SAP Fiori Apps. Ex - PO Output Automation Rate Fiori App. With this app, one can see an overview of the number of purchase order outputs by
output channel.

18 Period-End Closing
Simplifications and Innovations are introduced in the Period End Closing process which reduces the steps and overall time for PEC. Soft-closing is easily achievable due to capabilities like no
reconciliations needed, real-time profitability, continuous ICR, embedded BPC etc.Group Reporting software is packed with more enhancements.Auto-reversal feature of journal entries
Description available at the time of posting original entries. Machine learning integration to automatically handle GR/IR reconciliation exceptions and related KPIs for early detection. For closing
operations at period-end closing in S/4HANA, one can use the programs available for analyzing, valuating, and reclassifying the journal entries.
Relevant PEC steps are currently used in the system.

AA MOTORS Source System Transactions AS01, AS03, AS02, AFAB, OB52, FAGLGVTR are used.
To prepare for the conversion,

• A certified financial statement for the previous fiscal year is a prerequisite.
• Regarding Asset Accounting (FI-AA), one is not allowed to reopen the previous fiscal year.
• All balances in all applications and ledgers should be carried forward to the current fiscal year using the transactions: • FAGLGVTR for the new General Ledger • F.16 for the classic General
Ledger • AJRW for Asset Accounting • F.07 for Accounts Receivable and Accounts Payable
• Some days before the technical downtime, carry out the usual period-end closing activities for the previous fiscal period. Carry out the depreciation run and Run the periodic asset postings
report without errors.
• Reconcile GL with classic Asset Accounting (using TCode ABST2) or new Asset Accounting (using TCode ABSTL). Correct all differences found during the reconciliation.
• Execute the asset history sheet.
• Before technical downtime, Execute all scheduled jobs, Do not schedule any new jobs, Make sure that all held documents have either been posted or deleted, Perform closing for periodic
asset postings, Calculate the plan values for depreciation, reset the valuations for all periods in the current fiscal year, lock all periods in Financial Accounting and controlling.
• Make sure all checks provided by report RASFIN_MIGR_PRECHECK have been integrated into the program /SDF/RC_START_CHECK, which is started by SUM automatically.
- SAP S/4HANA FCc (embedded in S4core) was developed to take advantage of S/4HANA capabilities and efficiencies and is delivered as part of the core S/4HANA application. Use rights
Action / Impact for SAP S/4HANA FCc does require separate licensing. SAP S/4HANA FCc is considered a matured product by SAP and will no longer develop new capabilities.
- SAP Advanced Financial Closing (AFC) is delivered as a cloud service powered by SAP BTP. Cloud based closing hub can be connected with SAP S/4HANA. AFC kicks off closing jobs in the
background and receive status update which can trigger successor tasks. Managers and chief accountants can use built in embedded analytics and controls to see real time status of all
closing activities from different dimensions and drill down into levels of detail. AFC is a cloud-based application that can automate many of the commonly performed closing activities.
- Period-end closing tasks for deriving market segment information have been eliminated, resulting in (a) no more settlement of sales order items and (b) no cost center allocations to
profitability.
- The bottlenecks for intercompany reconciliation are removed because it can be run anytime with immediate results.
- The SAP Financial Closing cockpit integrates with SAP Fiori and facilitates users running/ scheduling tasks from the apps.
- Check SAP Note 2873915 for what needs to be taken into account for SAP AFC for system conversion or new implementation.
- SAP offers Automation with iRPA for Financial Close Summary and Automation with Automatic Rules / Workflow for Corporate Close
- Add-on extending Entity Close:
SAP Account Substantiation and Automation by BlackLine (Additional License)– for best practice automation for the balance sheet substantiation processes
Add-on extending Corporate Close: SAP Intercompany Governance by BlackLine (Additional License) – for governance especially related to the origination phase for non-trade intercompany
processes in a heterogeneous landscape
Reduced number of steps (various recons, periodic postings, carry forward), faster processing (ICR, settlements, depreciation, WIP, variance, reports), enhanced functionalities (OB52,
foreign currency valuation, soft close).More than 35 new predefined SAP HANA Live views have been added in SAP S/4HANA Finance. These views can help generate finance reports from
multiple reporting tools, such as SAP BO, SAP Lumira, SAP Fiori, which facilitate the month-end closing process.Process automation via fixed rules or machine learning, ex- automation in
Benefits GR/IR account maintenance, reprocessing of bank statement items.
Group reporting software brings 4 new apps to provide smart intercompany matching and reconciliation
SAP AFC provides full transparency and insight needed to resolve error and bottlenecks. It informs accountants and managers via emails notification and status updates and embedded
workflow.Real-time and correct asset acquisition values are provided without the wait for the periodic posting run during the closing process.

19 Physical Inventory
Physical Inventory – comes with S/4Core. There is ‘Situation Handling’ capability in Physical Inventory.Situation Handling provides contextual information proactively and
Description offers resolution proposals to optimize the critical steps of the physical inventory process.
AA MOTORS Source System Physical Inventory transactions MI01, MI03, MI11, MI22, MI31, MIGO are used.
Physical Inventory – comes with S/4Core

Mobile Counting App for Physical Inventory
• Run physical inventory process end-to-end in one system
• Enter counting results via mobile device in the moment of counting
• Leverage device camera or external scanner for scanning the material to be counted
There is ‘Situation Handling’ capability in Physical Inventory.Situation Handling provides contextual information proactively and offers resolution proposals to optimize the
critical steps of the physical inventory process.
Action / Impact Fiori Apps are available - Create Physical Inventory Documents - For this app, one can select either materials with or without movement and create physical inventory
documents for materials for which no material documents exist. Also, usability has been improved.
The Schedule Physical Inventory Document Creation app has been renamed to ‘Job Scheduling and Mass Processing – Physical Inventory’ app. One can now schedule a
background job that processes the mass creation of physical inventory documents in combination with a new print option using the same background job, if desired. Also,
can use a new selection criterion with the introduction of the Valuation Type field including a valuation help.
Manage Physical Inventory Documents app, helps to delete physical inventory documents completely or mark several physical inventory items as deleted. Also, filter
options in the item table for physical inventory document items are available now, to narrow down the existing item list according to available criteria.
Benefits Simplification

20 Preliminary Billing Document

With this feature, one can now use several new apps to create, change, and output preliminary billing documents for customers. A preliminary billing document is an
optional intermediary document between the billed reference document (for example, asales order ordebit memo requestor delivery) and the final billing document (usually
Description an invoice). It is created solely for negotiation purposes and is structurally identical with a standard billing document. Onecan show preliminary billing documents to
customers to align on exact details (such as prices, payment terms, and the billing date).
Billing Document is active.
AA MOTORS Source System Transactions VF03, VF01, VF02, VF04, VF05, VF05N, VF11, VFX3, VF07 are used.
The corresponding business function SD_BIL_PRELIMBILLINGDOC must be activated to enable this functionality.
One can create a preliminary billing document solely to facilitate negotiations with customers. It is therefore relevant for output, but not for posting to financial accounting.
It can be changed as often as necessary following discussions with customers, allowing for repeated negotiations about exact details (such as prices, payment terms, and
Action / Impact the billing date).
In SD Simplification, Customer and document pricing procedure extensions allow for more flexible pricing procedure determination, redundant fields are removed from
condition header table, it reduces the memory footprint of condition records.
1. Increased customersatisfaction with the form and content of a future billing document before one actually create and post the final billing document requesting
Benefits payment.2. This is safe in the knowledge that both parties are fully aligned regarding the upcoming settlement.

21 Processing Purchase Requisition and Purchase Order

CPPR (Collective Processing of Purchase Requisitions) and SPPR (Single Processing Of Purchase Requisitions) are no longer available in S/4HANA. Following the SAP Fiori
Description user experience and simplification approach, the portal content and web Dynpro applications for CPPR (Collective Processing of Purchase Requisition) and SPPR (Single
Processing Of Purchase Requisitions ) are no longer available in S/4HANA.
CPPR / SPPR are in use.
AA MOTORS Source System Transactions ME51N, ME53N, ME52N, ME5A, ME57 are used.
This is relevant as WebDynpro applications (tool integrated with ABAP workbench) for Purchasing Requisition was for data transfer from ECC to SRM.
Some of the Fiori Apps are deprecated as of release SAP S/4HANA 2023.
This means, these apps are still available and supported but no new features or enhancements can be expected. We plan to make these obsolete in favor of the designated
successor functionality as of release SAP S/4HANA 2025:
Action / Impact 1. Create Purchase Requisition (F1643) - Fiori app - plan to use Successor App - F1639A.
2. My Purchase Requisitions (F1639) - Fiori app
3. Manage Catalog Item Recommendations (F3293) - Fiori app
4. Schedule Export of Catalog Item Images for Machine Learning (F4641) - Fiori app
5. Schedule Transfer of Purchase Requisitions for Intelligent Approval (F4155) - Fiori app
These applications are enhanced with better UI interface provided with SAP Fiori UI5 technology that provides greater benefits both in terms of user experience and
Benefits seamless integration with improved system performance.

22 Profit Center Accounting

In SAP S/4HANA, Profit Center Accounting is mapped in the universal journal by default. Classical Profit Center Accounting (PCA) is part of the SAP S/4HANA compatibility
Description scope.
Profit Center Accounting is in use.
AA MOTORS Source System Transactions/Programs KCH2, KE53, KCH3, KCH1, KE52, KEMDM are used.
- In SAP S/4HANA, Profit Center Accounting is mapped in the universal journal by default. Classical Profit Center Accounting (PCA) is part of the SAP S/4HANA compatibility
scope. Alternative functionality "Profit Center Accounting on Universal Journal" in SAP S/4HANA.
During the data migration from an SAP ERP system to SAP S/4HANA, the profit center information from the tables of classic general ledger accounting (BSEG) or, if it was
active, General Ledger Accounting (new) (tables FAGLFLEXA/FAGLFLEXT delivered in the standard system) is transferred to the new table ACDOCA of the universal journal.
First, only actual postings for classical Profit Center Accounting, using GLPCA and GLPCT, will be adopted to S/4HANA product standards and can thus be used after Dec 31,
2025. This allows customers to create their balance sheet, complete their fiscal year, and perform a final year end closing. However, this functionality is set to “deprecated”
Action / Impact and will receive no further developments or updates. Customers need to transition to Profit Center Accounting on Universal Journal at the latest with the next fiscal year
change after Dec 31st 2025.
Second, Profit Center Planning based on table GLPCP stays in compatibility scope and must not be used beyond they expiry date of the compatibility package usage rights,
i.e. Dec 31st 2025.
Now one can reorganize profit centers for project networks, network activities and network elements. In addition, valuated leasing contracts with flexible real estate
management, are also considered in the organizational change.
Benefits Simplification

23 Profitability Accounting
SAP S/4HANA allows two different profitability solutions.
1. Margin Analysis - Profitability Analysis within the Universal Journal addressing the need of internal and external accounting, supporting real-time derivation of reporting
dimensions and embedded analytics. SAP continues to conduct new developments in this area only. It is perfectly integrated into the overall concept of the Universal Journal and is
therefore fully in line with SAP’s Financial Accounting development strategy. Margin Analysis is active if there is an activation flag for 'account-based' in the IMG procedure
Description mentioned above.
2. Costing-Based CO-PA - Groups revenues and costs according to value fields and applies costing-based valuation approaches. Data is recorded in a dedicated persistency apart
from external accounting. Before the conversion to SAP S/4HANA on-premise, SAP recommends that clients verify whether Margin Analysis can already cover all requirements and
costing-based CO-PA can remain de-activated.
Cost Based COPA is active.
AA MOTORS Source System Transactions KEDR is used.
One can continue to run both approaches in parallel, by making the appropriate settings per controlling area. The essential difference is that costing-based CO-PA is a key figure-
based model, rather than an account-based model. Margin Analysis covers record types F (billing documents), B (direct FI postings), C (settlement) and D (assessment) in costing-
based CO-PA. A different approach is taken for record type A (incoming sales orders) where predictive accounting documents are created to represent the sales order prior to
delivery and invoicing in a make-to-stock environment. Predictive accounting does not yet support record type I (order-related projects) in a make-to-order environment.
There is no direct migration from costing-based CO-PA to Margin Analysis.
Customers should analyze existing reporting requirements to understand how market segment reporting is handled today. Also include transfer of profitability information to other
Action / Impact systems, including data warehouses and consolidation. During conversion, the system will create columns in the universal journal for all characteristics in the operating concern.
If costing-based CO-PA is currently used, analyze what workarounds are being used to reconcile the profit and loss statement with costing-based CO-PA to determine whether
these will be required in the future. Check whether the functions available with Margin Analysis can already satisfy reporting requirements or whether one will continue to need
costing-based CO-PA for an interim period. If combined Profitability Analysis is currently used, check whether the functions available with Margin Analysis can already satisfy one’s
requirements.
Existing reporting transactions, such as KE30 and KE24, will continue to work, but also investigate possible usage of the Fiori apps to display information by market segment,
including additional currencies and data from the extension ledgers.
The universal journal (ACDOCA) is the heart of Accounting and includes all Margin Analysis characteristics in order to allow multi-dimensional reporting by market segment. The
universal journal includes columns for the standard characteristics and all additional characteristics included in an organization’s operating concern (up to sixty characteristics,
including the fixed characteristics). If an operating concern is configured for Margin Analysis, columns will be created for each of the characteristics during migration.
The benefit of this approach is that all revenue and cost of goods sold postings are automatically assigned to the relevant characteristics at the time of posting and that allocations
and settlements are made to the characteristics at period close.
Benefits It is also possible to configure some expense postings such that the characteristics are derived automatically, so that material expenses assigned to a WBS element (account
assignment) are automatically assigned to the characteristics entered as settlement receivers for the WBS element. This automatic derivation of the characteristics can reduce the
number of settlements and allocations to be performed at period close and provide real-time visibility into spending during the period.
There are also no reconciliation issues between the general ledger and Margin Analysis. However, revenue is recognized at the time of invoicing and cost of goods sold when the
delivery is made. If there is a time gap between delivery and invoicing, costs may be visible in Margin Analysis for which no revenue has yet been posted (matching principle). From
SAP S/4HANA 2021 one can use event-based revenue recognition to recognize revenue with the outbound delivery or to delay the COGS posting until the contract is completed.

24 Project Builder
- It´s the target to have one maintenance transaction in future. The target transaction is CJ20N Project Builder.
-The currently parallel (partly redundant) transactions for date planning, simulation functions and scheduling will still be available.- A number of Fiori apps are introduced in
Description Project Systems area which are functional equivalents of Project Definition, WBS Element, Network, Activities, Milestone and Material Component Overview processes.
Overview apps have good usability since users have direct access to required data after clicking on the tile for any app. User can go into detailed view as well.
Project Builder is in use.
AA MOTORS Source System Transactions CJ20N, CJ7E, CJI3N, CN43N, CJ8G, CJ13, CJI3, CJ8V are used.
- The target for links and references in strategic reports and transactions is going to single maintenance transaction CJ20N (Project Builder).
- Transactions related to Work Breakdown, Project Definition, WBS Element, Structure Planning, network, Simulation Function - are not the target architecture.
- One can review the 23 improvements which have happened over a period of time in SAP Project Systems area and the complete list of improvements is listed in the
composite SAP Note 2367898.
- In Project Systems and Materials Management integration area, user can monitor materials planned for various projects and its network activities and associated WBS
Action / Impact elements, purchase orders and purchase requisitions created for a project or work breakdown structure (WBS) element in a display currency. Results can be further filtered
for a particular WBS element, supplier, plant, purchasing organization etc.- As of SAP S/4HANA 2021 FPS02, one can provide short and long texts for PS objects in several
languages using multilanguage support and can use standard text keys to create texts that can be used across multiple projects. A lot of Fiori apps are available to view
multilanguage short text in PS WBS elements, Network Activity, Network, Project Definition and milestone.Graphics and Simulation functions in Project System are part of
the SAP S/4HANA compatibility scope. SAP GUI-based project planning board and network graphic will continue to be available. Alternate functionality - Fiori Apps are
available.
1. Overview apps have good usability since users have direct access to required data after clicking on the tile for any app.
2. Different View is available in these Fiori apps – by phase, function and object.
3. Better integration with MRP and Procurement processes.
Benefits 4. Users can track all activities and components end-to-end.
5. Redundant transactions will be removed
6. Lesser system memory usage improving overall performance.7. Multilanguage Support for Short Text in PS Objects.

25 Quality Notification
- The quality notification (in general and result recording) will be replaced. Currently no functional equivalent for Quality notifications in QM within SAP S/4HANA. The old
Description functionality will stay available until the new functionality is released.Some new feature has been added in Quality Notification, With this feature one can transfer defects of
nonconformance management to quality notifications. Further processing is done in the quality notification. The defect is no longer editable and can only be displayed.
Quality Notification functionality is in use.
AA MOTORS Source System Transactions IQS1, IQS2, IQS3 are used.
Quality Notification is used for recording and processing different types of problems (for example, problems resulting from poor-quality goods or services), to analyze the
recorded defects and monitor the correction of these problems. In particular, the notifications can help process internal or external problems such as: Customer complaints,
Complaints against vendors, Company-internal problems, Other user-specific problems.
Quality Notification is integrated with Plant Maintenance (PM) component and service notifications in the Customer Service (CS), also integrated with SD, DMS(Document
Action / Impact Management System), Classification System.
The following transactions are replaced by corresponding Fiori apps – type SAP GUI or Webdynpro.
QM0* - (Create/Change/Display Quality Notifications), QM1* - (Create/Change/Display Quality Notifications Task, Item, Activities).
Knowledge transfer to key resources should be planned.
The quality notifications helps to:
Describe a problem and identify the affected reference objects (for example, material, vendor, manufacturer)
Record the names of all persons (partners) who are involved with the problem
Record individual defect items that relate to the problem and analyze their causes
Benefits Assign a defect item (batches, serial numbers, inspection lots, production orders, process orders, or delivery items)
Specify the corrective actions to be taken
Monitor the execution of corrective actions through a status management function
Print, fax, e-mail, archive, or export various types of reports (shop papers) that relate to the problem

26 Release Approval for Purchasing Document

Description The “My Inbox” Fiori App allows users to manage all their workflow tasks from a single inbox. No need to remember multiple t-codes for approvals of PR, PO.
Release purchase requisition / Release purchase order are in use.

AA MOTORS Source System Transactions ME28, ME55, ME29N, ME54N are used.
Action / Impact No Action required
Benefits Simplified approach, removal of multiple transaction codes leading inconsistency.

27 RFQ
RFQ is a form of invitation that is sent to the suppliers to submit a quotation indicating their pricing and terms & conditions. It contains details about goods or services,
quantity, date of delivery, date of bid etc.
In response to the RFQ, suppliers provide quotations, buyer can compare these quotations and award the order to the competitive and suitable quotation.
Description With the new concept in S/4HANA, system allows to send RFQ via Fiori App to external sourcing platforms without a Supplier included and to receive from them multiple
Supplier Quotes which fits to different Sourcing Integration Scenarios.
On the sourcing platform, the registered suppliers can submit their quotations which are later available to the purchaser.
RFQ is in use.
AA MOTORS Source System Transactions ME41, ME43, ME42 are used.
- Customer must edit the user roles. As soon as the new Fiori Apps will be available also the standard roles delivered with SAP S/4HANA contain this new authorization
object. Relevant business roles – SAP_BR_PURCHASER (Purchaser) and SAP_BR_BUYER (Strategic Buyer) are to be maintained, which contain relevant authorization
object.
- Before using the new Fiori App, customers need to close open RFQ created with the old transactions and set them to status "Completed".
- REQOTE (IDoc for RFQ) and QUOTES (IDoc for Quote) is not considered target architecture; it is planned to replace them with cXML messages. Also, it is planned to
introduce SOAP-based messages to further replace cXML messages for RFQ and supplier quotation.
- ME4* transactions for RFQ and Quotation are planned to be replaced with Fiori Apps.
- Fiori Apps that are available are -
Manage RFQs (F2049) – User can copy an existing RFQ, publish the RFQ and send it to suppliers, display the History of the RFQ to keep track of the document changes,
display process flow.
Action / Impact Monitor RFQ Items (F2425),
Request for Quotation Types (F4149),
Manage Supplier Quotations (F1991) - User can use this app to display all supplier quotations which has been received for different RFQ’s. User can view the details
information for each quotation,
Compare Supplier Quotations (F2324) – User can display all received quotations for this RFQ and check whether all invited suppliers have already sent their quotations or
not, then check best-priced items, compare supplier quotations, and award the best quotation.The 2023 release has added many features for complex RFQ processes –
known as Product Sourcing. Among them, one can now request data about the carbon footprint of items from suppliers. One can decide for each item in sourcing project
whether one would like to collect carbon footprint data for that item, and suppliers can then provide this information in their supplier quotations.
Also, analytics apps to monitor RFQs and compare supplier quotations. For full online RFQ process support use simple offline RFQ apps to seamlessly integrate with
Sourcing in Ariba.
- System can send RFQ via Fiori App to external sourcing platforms without a Supplier included
- Capable to receive the RFQ from multiple suppliers.
Benefits - Portability of the system.
- Manage Central RFQs: This feature enables one to display, create and manage central RFQs in the SAP S/4HANA system that acts as a hub system. One can create central
RFQs from purchase requisitions that are created in the hub system.

28 Run MRP
New MRP Live transaction -MD01N (Optimized for SAP HANA), and associated consistency and performance check reports, simplified storing of planning file entries, several new
Description Fiori APPs and reports are available. Multiple changes in MRP views in Material Master, simplified sourcing.
MRP Functionality is In use.

AA MOTORS Source System Transactions MD04, MD01, MD07 are used. Programs RMMRP000, RMPROG01, SAPMM61R, SAPMM61X are used.
- Instead of SAP ECC static MRP list, SAP S/4HANA offers the new MRP Live and the SAP Fiori applications of the MRP Cockpit, which means faster MRP and a new user interface to
evaluate the MRP results. In transaction MD01N, the MRP List will no longer be generated during the planning run. Check with MRP Fiori Apps if they can be used as a successor to
MRP Lists if it was used earlier. MRP Live does not write MRP Lists.
- Classic MRP (BADI and MRP list) is still available in SAP S/4HANA in compatibility scope. New MRP Live logic was pushed down into the SAP HANA layer, meaning it is almost
entirely executed with SAP HANA stored procedures. Any custom logic written in ABAP-based BAdIs will have to be translated into the new AMDP BAdIs provided by SAP in MRP
Live. Before starting with MRP Live, check if the BADI implementation of classic MRP is required to be re-implemented as AMDP BADI.
- Check note 1914010 for MRP Live Restrictions.
- MRP live does not perform forecast based planning in HANA but sends the affected materials into the classic ABAP planning procedure.
- MTO Planning (transaction MD50) and Individual Project Planning (MD51) are not optimized for HANA.
- For Storage location level planning and subcontracting planning, MRP areas need to be configured mandatorily. S/4HANA MRP only plans on plant and MRP area level. Planning on
storage location level is not available in SAP S/4HANA. Conversion Pre-Checks raise an error if storage location MRP is used in the source ERP system. Run report
Action / Impact MRP_AREA_STORAGE_LOC_MIGRATION (delivered with note 2216528) if the pre-checks detect that storage location MRP is used. Missing storage location MRP Areas will have to
be created manually.
- MRP Live is related to creation indicators, means it reads material receipts and requirements, calculates shortages which allow one to choose whether it should create planned
orders, purchase requisitions, or delivery schedules for materials procured externally – all in one database procedure.
- Check note 1914010 for MRP Live Restrictions.
- When PP/DS is used in SAP S/4HANA system, one can combine PP/DS and the MRP planning run in a single job, reducing the effort of synchronizing different jobs for materials
planning.
- MD01N does not offer the creation of planned orders (rather than rather than purchase requisitions) for external procurement. One can use PPH_MRP_SOURCING_BADI to
achieve a similar functionality like still offered by MRP classic.
- MRP Live is not designed to be integrated with a Manufacturing Execution System (MES). Corresponding materials can be set using transaction MD_MRP_FORCE_CLASSIC in such
a way that they are automatically redirected to classic MRP in MRP Live.
- Improved performance and execute the planning run in much shorter cycle. One can use MRP Live for planning large sets of materials and taking advantage of the performance
improvement but keep using classic MRP for single-item planning
- Sudden changes in the customer requirements/stock situation are not covered in ECC planning process which result in the delay while responding to the requirements and
impacting the revenue. Planning selective multiple materials/or selective plants needed manual efforts which was time consuming and could lead to mistakes as well. With
S/4HANA, the improved MRP Performance allows to run MRP multiple times in a day which helps in accommodating the new customer requirements, and stock changes are covered
quickly in MRP Live.
Benefits - More up-to-date supply and demand information on which to base decisions.
- Identify and faster reaction to demand changes reduces the risk of stock-outs and means that one can reduce safety stocks.
- Match demand and supply more efficiently than was previously possible - faster reaction to demand changes reduces the risk of stock-outs and means that one can reduce safety
stocks.
- Fiori Analytics for better MRP analysis. New Fiori Apps - 'My Area of Responsibility' - to manage 'Planned-Production-Process Orders', monitor 'material Coverage' and
'Requirements', Hand Over Purchase Requisitions. Also, Fiori Apps associated with MRP in Variable display of availability, Demand and Supply, Color Coded for easy identification of
shortages.
29 Sales Contract Management

Sales contracts represent long-term agreements with customers about goods or services. They define when specific goods are to be sold or specific services are to be
provided, and under which conditions. Sales contracts are valid for a certain time period. When the validity ends, they can be renewed.
Sales scheduling agreements represent long-term agreements with customers about goods only. They outline the expected target quantity of goods that is to be delivered
Description over a defined period.
Multiple improvements in the area of Sales Contract Management like Sales Contract Fulfillment Alert, Displaying Legal Transactions in Sales Contracts, Displaying Product
Compliance Statuses in Sales Contracts.This is achieved by using situation template - which is now available for the sales contract Fiori object page.
Sales Contract is active.
With the SAP S/4HANA 2020, one can use situation template which inform users about -
Sales Contract Fulfillment Alert – Fiori ID F2026 – It informs about sales contracts that are being fulfilled at a faster or slower rate, Sales contracts which will expire within
30 days, but no follow-on contracts have been created. When a situation occurs, the users can get an in-app message in the relevant sales contracts. Users can also quickly
identify the top 10 contracts by target value. Further drilldown capability based on real-time data is available. Managers no longer need to wait for contracts to expire or
periods to close in order to analyze the sales contracts.
Display Legal Transactions in Sales Contracts - With the Sales Contract object page, if authorized, one can see related legal transactions and navigate to the Legal
Transaction object page.
Action / Impact Display Product Compliance Statuses in Sales Contracts - sales contracts now include information on product marketability, dangerous goods, and safety data sheets.
Output of Sales Contracts - The pre-delivered form templates for sales contract now include information about product compliance. The form template SD_SLS_CONTRACT
has been enhanced with dangerous goods data if they are included in sales processes.
Using ‘Manage Sales Contract’ Fiori App, one can search for sales contracts according to filter criteria and display them in a list. One can also navigate from the same page to
the Create Contract (VA41) screen. One can now retrieve sales contracts that are blocked for negative credit check and can perform check, read, and release operations.
Also, one can update and delete sales contracts in the SAP Fiori frontend.
Also, using ‘List Incomplete Sales Contract’ app, one can easily check which documents and data are incomplete. Users can then drill into a particular contract to access the
incomplete details.
1. Better visibility and tracking.
Benefits 2.Better sales force efficiency through ready access to Sales Contract Fulfillment and legal content related to a sales contract.

30 Sales Quotation
Sales inquiries are requests from customers for information about the purchasing conditions (such as price and availability) for certain goods or services. Sales quotations, in
turn, are the responses to sales inquiries and represent legally binding offers to customers for the supply of goods or the provision of services under specific conditions.
Customers can respond to a sales quotation with a purchase order, which in turn triggers a sales order.
Description Situation template is now available for the sales quotation object page to inform specific users about their sales quotations that are about to reach the validity end date but
still have a low conversion rate.This situation template is now available for the sales quotation Fiori object page. When a situation occurs, the users can get an in-app
message in the relevant sales quotations.
Sales Quotation is active.
The Sales Rep do not need to monitor valid-to dates of sales quotations in the Manage Sales Quotations app and check quotation conversion rates in analytical apps such as
Quotation Conversion Rates -Valid/Not Completed.
Action / Impact They can now quickly identify expiring sales quotations with a low conversion rate and view details about such quotations - asthe users can get an in-app message in the
relevant sales quotations or notification on Fiori launchpad.
1. Users can immediately learn about expiring quotations with low conversion rates which enables them to focus on quotations of this kind and proactively follow up with
Benefits customers that have not placed orders yet.2. Increased win rate through improved transparency of the status of sales quotations and the ability to take immediate actions if
required.

31 Service Contract Management

Customer Service (CS) provides Service Management functionality for planning, executing and billing service orders. CS is used for Field Service, In-House Repair as well as
Service Projects. It works in conjunction with Plant Maintenance (PM) functionality and provides integration to Resource Related Billing as well as Service Contracts.
Description Customer Service (CS) will be replaced by S/4HANA Service. S/4HANA Service will be the new state-of-the-art Service Management backend as part of SAP S/4HANA.
Using ‘Display Document Flow’, one can see service contracts and service contract billing document requests. The Service Contract and Billing Document Request document
types are available.
Service Contract is active.
AA MOTORS Source System Transactions ME33K, ME32K, ME35K, ME31K are used.
When adding a repair quotation item or a repair order item, it is enabled to assign the applicable contract item or choose an applicable contract when having multiple
choices available.
This contract item is:
• Displayed under Item Details of the repair order or the repair quotation
• Considered in pricing
Action / Impact • Copied to the repair order or the repair confirmation which is created as a follow-up
A new condition type DSC3 (discount for service contract) is enabled to define price agreements at the header level of service contracts. It can be used to apply additional
discounts to the service transaction items (such as service order items) when service contract items are assigned to service transaction items after service contract
determination.
Service contract management enables ad-hoc billing plan which provides complete flexibility on when and how much to bill customers. Enablement of ad hoc billing is a
structured method of service contract billing that enables one to define billing values and billing dates manually.
Service Management introduces the enterprise organization model for customers to have a new option to manage enterprise organizations apart from the existing one and
Benefits legacy organization model.

32 Shipping and Transportation

The Logistics Execution Transportation (LE-TRA) is not the target architecture within SAP S/4HANA and is available within the SAP S/4HANA - compatibility pack – till
2030.The alternative functionality is the basic variant of Transportation Management within SAP S/4HANA, which is already available.Currently, that means until the
Description expiration of the usage rights of the Compatibility Packs, both technical applications (LE-TRA and Transportation Management) are independent from each other and can be
used next to each other in the same SAP S/4HANA database instance.
However they are not integrated with each other and there is no data exchange.
LE-TRA is being used.
AA MOTORS Source System Transactions VT01N, VT02N, VL10B, VL01N, VL02N, VL10X, VL31N, VL33N, VL03N, VL06O are used.
Logistics Execution Transportation (LE-TRA) is not the target architecture anymore within SAP S/4HANA.
The alternative functionality is the basic variant of Transportation Management within SAP S/4HANA, which is already available. The main functions of LE-TRA have already
been replaced with those selected functions of SAP S/4HANA Supply Chain for Transportation Management.
Currently, that means until the expiration of the usage rights of the Compatibility Packs, both technical applications (LE-TRA and Transportation Management) are
independent from each other and can be used next to each other in the same SAP S/4HANA database instance.
However they are not integrated with each other and there is no data exchange.
Action / Impact The Route object of application component LE-TRA and the corresponding objects, which are needed for the definition and determination of this route, have been moved
from the Compatibility Scope into the Perpetual Scope of SAP S/4HANA.The customers can use those objects after 2030 in SAP S/4HANA. That allows the customer to use
these objects for existing functionality in other applications e.g. scheduling in sales order / stock transport order / delivery, etc.
All other objects from LE-TRA which are used for the Transportation functionality will remain in the Compatibility Scope. And cannot be used after 2030.
This would primarily be the shipment document + shipment cost document and all corresponding objects / customizing (e.g., transportation connection point, route stage
definition) / master data / interfaces.
A number of Fiori Apps are available in TM - Forwarding Order/Agreement, Freight Orders and Settlement, Delivery Integration, Change Management.
- The integration of the whole process has been largely enhanced providing integration between the activities in the warehouse; including pick, pack and shipping execution.
- Reduce transportation spend: Automate processes for inbound and outbound shipment
- Improve supply chain FTE productivity: Provide transaction access and real-time information- Improve inventory accuracy with real-time reports on inventory positions
and flows with preconfigured analytical views.
Benefits - Enhance on-time delivery performance by integrating pick, pack, and ship processes.
- The new integration of embedded EWM in SAP S/4HANA and embedded TM in SAP S/4HANA no longer relies on two objects (Transportation Unit in EWM and Freight Order
in TM) that need to be continuously synchronized. With the Freight Order as leading and only object, the new integration offers higher throughput, but also allows new
scenarios like inbound and outbound on one truck.- Multiple locations can be created for every relevant address of a business partner.

34 Simplified Sourcing
A reduced set of possible sources of supplyis suggested in S/4HANA simplification -
1. Production Version (mainly in-house production source)
2. Delivery Schedules (external procurement)
3. Purchasing Contracts (external procurement)
4. Purchasing Info Records. (external procurement)
Quota arrangements can be used to prioritize sources of supply in case several sources of supply are valid simultaneously.
If a purchase requisition is created manually in SAP S/4HANA and the system determines several valid equivalent sources of supply, one must select the appropriate source manually from a list. If
the system is to make this selection on its own, one can additionally use the source list.
The source list is a register of sources of supply for a material in a certain plant. Each source list record contains a validity period, a source of supply, and parameters that control the source of supply
Description during this period. One of these parameters is used to define a source as your preferred source of supply.
A reduced set of possible sources of supplyis suggested in S/4HANA simplification -
1. Production Version (mainly in-house production source)
2. Delivery Schedules (external procurement)
3. Purchasing Contracts (external procurement)
4. Purchasing Info Records. (external procurement)
Quota arrangements can be used to prioritize sources of supply in case several sources of supply are valid simultaneously.
If a purchase requisition is created manually in SAP S/4HANA and the system determines several valid equivalent sources of supply, one must select the appropriate source manually from a list. If
the system is to make this selection on its own, one can additionally use the source list.
The source list is a register of sources of supply for a material in a certain plant. Each source list record contains a validity period, a source of supply, and parameters that control the source of supply
during this period. One of these parameters is used to define a source as your preferred source of supply.
AA MOTORS Source System Purchasing Info Records and Source Lists are in use.
Transactions ME01, ME03, ME12, ME11, ME13, ME15 are used.
-MRP selects Purchasing Info Records as valid sources if the new indicator "relevant for automatic sourcing" is set.
-If BOM or routing are to be considered by MRP, one should create a production version. Check if Production versions exist for those BOM or routings. Use report CS_BOM_PRODVER_MIGRATION02
to analyze.
-S/4HANA sourcing finds contracts and delivery schedule without source lists. So, no action if source lists refer to contract / delivery schedule. But, if, they refer to a supplier, activate automatic
sourcing indicator in corresponding purchasing info record.
- Source lists are not needed. Source list may be used to block a source of supply, MRP-enable it only for a limited period of time or prioritize available sources of supply.
Action / Impact - PO and PR creation and update always consider and update quota arrangements. It is not required to switch usage of quota arrangements on in the material master.
- MRP considers always more detailed planning parameters of the supply source. It is not required to switch it on in the customizing.
- With the Manage Preferred Supplier Lists app for Product Sourcing, one can create and manage lists of suppliers that company advices him to use during the sourcing process. This includes
standard supplier lists that are available for all users, as well as user-specified supplier lists created for own use, such as by material group or purchasing category. The time-consuming manually
search for suppliers is eliminated and one can find the best suppliers by using your own supplier list.
With Product Carbon Footprint app, one can track the carbon footprint of the products being requested in purchase requisitions. These metrics are vital to achieve organization’s sustainability goals
and are calculated in SAP Product Footprint Management on SAP Business Technology Platform.
A number of Fiori Apps are available.
Simplification in master data maintenance:
- Neither customizing nor source list records needed for sourcing, source lists can be used to temporarily block a source of supply or MRP-enable it only for a limited period of time.
- Reduced complexity: Reduced set of possible sources of supply with a clear and symmetric definition.
Benefits - Simplified sourcing logic. Quota arrangements are used if they exist.
- MRP considers always more detailed planning parameters of the supply source. It is not required to switch it on in the customizing.
- Earlier, MRP used to select purchasing info records if a source list entry exists that referenced the supplier in the info record. Now, purchasing info records are a source of supply in their own right.
MRP selects purchasing info records if the “relevant for automatic sourcing” indicator is set in the purchasing info record in S/4HANA. So, the process is simplified.
34 Variant Configuration
Variant configuration helps the customer or salesperson to put together specifications for the product and ensure that the product can be produced from these
specifications. It is intended for the manufacturing of complex products with many variants. During the order processing, one change the existing product designs.
For each variant, one use one configurable material that covers all possible variants. One super bill of material (BOM) and a super routing contain all the components and
Description operations that one needs to produce all variants.
In SAP S/4HANA processes are simplified by switching off obsolete and redundant functionality related to variant configuration. It is not possible anymore to maintain the
"Classification as selection condition" in the bill of material. Furthermore, the usage of actions has been disabled.
With S/4HANA embedded analytics, it is possible to define own analytics using the CDS views for new advanced variant configuration and classification.
Variant Configuration is in use.
AA MOTORS Source System Transactions CU43, CU41 are used.
If one uses actions in VC models, no action needs to be taken for existing models. For new models, however, SAP recommends using the concept involving procedures and
constraints. SAP also recommends remodeling existing models to be prepared for future innovations.
S/4HANA On-Premise can have both LO-VC Configurator+Engine OR New Advanced Variant Configurator with UI and a new Engine.
• Easy conversion from the classic world: LO-VC (within S4core), Migration tool for LO-VC models, single- and multi-level, into the new Advanced Variant Configuration
• Immediate re-use of existing models after system conversion
• LO-VC improvements: new Fiori UIs, Embedded Analytics for Classification & Configuration
• Integration of LO-VC into Order Engineering Workbench -> intuitive user interface
Selection condition to select BOM items or routing operations still uses the LO-VC processing mode. BOM items and routing operations are part of the low-level
Action / Impact configuration. The new Advanced processing mode is used in the Product Variant Configurator for high-level configuration.
One of the new AVC features is the new overview page, only available in Fiori. As a product modeler, one can view and change all objects that are relevant for you.
In LO-VC, one has to list all values for which a certain condition is possible. In AVC one can now exclude the value for which the condition is not possible.
In AVC ALL characteristics are considered ‘restrictable’. One can now restrict multiple value characteristics by using them in constraints.
Also, integration of advanced variant configuration with SAP Commerce Cloud is now enabled.
For custom code related information : SAP Notes: 2210904 , 2214906
As per SAP Note 3190519, in the future, it shall be possible to safely reuse planned order / production order configuration models in bundles (configuration models with
sales order (SET) configuration profiles) in advanced variant configuration (AVC).
• The modelling will be simpler.
• The error rate is reduced, and the consistency of models will increase.
Benefits • Follow-up processes such as Material Requirements Planning (MRP) Live can be accelerated.• With new advanced variant configuration(AVC) and embedded analytics,
highly individualized products can be brought to the market fast and with efficiency.

35 Warehouse Management
The Warehouse Management (LE-WM) is in compatibility scope. The (already available) alternative functionality is Extended Warehouse Management (SAP EWM)and since S/4HANA 1909
Description Stock Room Management.
Warehouse management is in use.

AA MOTORS Source System Transactions LT01, LX02, LL01, LT03, LS01N, LB02, LT12, LT05, LU04, LT06 are used.
SAP LE-WM is available with compatibility scope – Inventory Management, Inbound and Outbound processing (of material), Mobile Execution, Physical Inventory, Reporting, Internal
Warehouse Movement.
SAP offer two options for deploying an embedded EWM solution, with varying functionality depending on the individual business requirements. Basic Embedded EWM option is included in
the cost of S/4HANA licensing, helping to keep deployment and running costs down. This option includes functionality for stock transparency and control, including inventory, process, and
layout management. The Advanced Embedded EWM option includes enhanced functionality, but also incurs an additional license fee. This option includes more detailed functionality that
helps to further enhance optimization of warehouse operations, including wave, yard, and labor management. The functionality Wave Management / collective Processing, Yard
Management, VAS of Warehouse Management (LE-WM) are still available within the SAP S/4HANA architecture stack as part of the compatibility packages.
PM Integration - the material components that are requested are staged from an EWM-managed storage location via an outbound delivery order. This contains a reference to the
maintenance order (PM order) and to the reservation document. The staging area can be determined based on the recipient location that is entered in the PM order.
APIs (ABAP-OO interfaces) are available in EWM, in inbound, outbound, order and labor management, production integration areas.
There is no integration of EWM with International Trade in SAP S/4HANA.
Action / Impact SAP Stock Room Management provides similar capabilities as that of LE-WM for small warehouse operations and warehouse operations with low complexity. One can use Stock Room
Management as a part of a flexible transition to SAP S/4HANA.
SAP S/4HANA 2022 release, during customer-defined packing and picking, only those HUs are picked that were created with a reference to a specific sales scheduling agreement and
according to a specific packing instruction (PI) or packaging specification (PS).
QM Enhancements - customers with QM requirements can now directly post synchronous goods receipts into embedded EWM (only) for goods procured externally or goods from in-house
production. Inspection lot summary, skip lots and cancellations are supported as well.
Also, possible to skip quality inspections if the goods don’t need to be inspected because of the current quality level. When skipping inspections, the system still creates inspection
documents but posts the goods from quality stock to unrestricted-use stock without performing an inspection.
New integration between SAP EWM and SAP TM, ‘Order Based Planning’ - starting the warehouse execution based on a transportation plan.
SAP Warehouse Robotics Integration - SAP Warehouse Robotics is a product that is built on the SAP Business Technology Platform. One can use it to automate warehouse operations using
robots. It has an agnostic architecture, which offers maximum flexibility and freedom of choice when onboarding new robots.
Availability of SAP Analytics Cloud (SAC) business content for EWM
- New analytics capabilities come with CDS views and an improved navigation, allowing one to resolve bottlenecks.
- One can optimize the management of product quantities in different stock categories and also.
process of receiving and sending products and putting them in the warehouse.
- Supports Material Flow System which includes - Automatic identification of HUs that are being scanned on the automatic storage retrieval facility and where scanner information is being
sent to Extended Warehouse Management (EWM) via a telegram.
Benefits - Support JIT Supply, Yard Management, Labor Management, VAS, Kitting, Cross Docking – check whether additional license is needed.
- An embedded EWM solution drastically simplifies the IT landscape and reduces the TCO. As all warehousing and transactional data is held within the S/4HANA database, the need for data
replication is significantly reduced. Master data does not need to be duplicated. It means storage costs are much lower and network loads are reduced, freeing up valuable resources.
- SAP Extended Warehouse Management provides capabilities for the integration with SAP Warehouse Robotics. 1) Allow SAP Warehouse Robotics to read warehouse orders and tasks, 2)
Set warehouse order status to “In Process” when a robot starts processing the warehouse order, 3) Confirm warehouse tasks and orders when a robot finish processing the warehouse
orders.

36 Class/Classification/Characteristics
Description Classification is a master data – i.e., a group of similar objects described by means of characteristics that they have in common.
For migration scenario, before Classification data, Characteristic objects should be maintained or migrated.
Characteristics is property for describing and distinguishing between objects such as length, color or weight.
AA MOTORS Source System Transactions CL24N, CL20N, CL02, CLMM, CT04 are used.
Action / Impact With SAP S/4HANA, transactions of the Classification are renovated so that transactions may have changed functionality or may be completely removed within SAP Product
Lifecycle Management (SAP PLM).
1. User Defined Data Type (031) for characteristics has been removed.
2. Rename Characteristic functionality has been disabled.
3. Parameter Effectivity has been hidden.
4. Due to security reasons batch import has been limited and batch import is possible only from presentation server.
In PP module, SAP S/4HANA processes are simplified by switching off obsolete and redundant functionality related to variant configuration. It is not possible anymore to
maintain the ‘Classification as selection condition’ in the bill of material. The usage of actions has been disabled.
Thereby, customers can benefit from the following:

✓ The modelling will be simpler.
✓ The error rate is reduced, and the consistency of models will increase.
✓ Follow-up processes such as Material Requirements Planning (MRP) Live can be accelerated.
Benefits Simplification..

37 Construction Equipment Management

Description In S/4HANA, the Engineering, Construction, & Operations component meets the wide-ranging demands of the Construction Industries. Primary application -
Equipment and Tools Management (ETM).
Equipment and Tools Management (ETM) deals with issues that secure an optimal process flow in enterprise areas of (construction) companies or equipment rental
companies, and so on, in aspects such as planning, processing, settlement and evaluation of resources (materials and equipment).
ETM integrates with Sales and Distribution (SD), Plant Maintenance (PM), Financial Accounting (FI) and Controlling (CO), Asset Accounting (AA) and Project System (PS).
AA MOTORS Source System Transactions/Programs J3GK03, J_3GWKAT are used.
Action / Impact An ETM catalog is a structured, hierarchical list of different types of machinery (for example, equipment, machines, and vehicles) and is based on the SAP standard
Classification System. Every ETM catalog is assigned to a Class within a Class Type . This means that all the numbers in the catalog are also assigned to this class or class
type. The characteristics used in characteristic value assignment are assigned to the class.
An ETM bill of material (BOM) is a list of parts (for example, machines, equipment, interchangeable items and attachments) that, together with a description and quantity,
forms the ETM Equipment . The parts are referred to as items. Each item has a value. The cumulated values of the items form the equipment valuation (value assignment for
the equipment).
ETM equipment encompasses objects such as vehicles, equipment, machinery, scaffolding, shuttering and tools that have to be sent and managed. These objects can
belong to all branches of industry.
ETM inventory is used in the area of equipment rental. It is based upon recipient-oriented key-date inventory, similar to that used in the Materials Management (MM)
module. However, materials are not included in inventory, only equipment (equipment items and multipart equipment). Materials can be included in inventory by using the
standard S/4HANA System.
One can use ETM planning to help enter requirements (for example, equipment needed by a usage site) that will then be processed by a stock and requirements planning
controller. The controller uses the characteristics ( classes ) of the equipment that is needed to process the requirements and find the equipment that most exactly fulfils
the requirements and is available for use at the required time.
Process Flow
❖ Requesting party (for example, construction site supervisor) reports a requirement
❖ This requirement is entered in the system in the form of a requisition note with appropriate characteristics
❖ The stock and requirements planning controller uses the requirements overview to process the requirements for recipients that are assigned to him (for planning area).
❖ A shipping document is used to send the required and confirmed equipment, material or package to the appropriate usage site.
As per SAP Note 2326777, customers who used ETM functionality in their earlier ERP releases will have to plan ETM recipient data migration to business partner, as
ETM functionality is available from SAP S/4HANA release with the possibility of creating ETM master data recipient as a business partner.
ETM is part of the SAP S/4HANA compatibility scope. As per note 2301533, Certain tables in the ETM package are not required anymore. Therefore, these tables are
removed. There is no change in functionality. Need to check whether existing data needs to be migrated or not.
Benefits One can do the following –

Equipment planning and Inventory management, Maintain relationships between owners and administrators of equipment, Shipping and settlement packages, Time-based
or performance-based settlement, Shipping and performance-based equipment (PBE) documents, Evaluations and reporting functions (settlement lists, statements of
usage, stock lists for construction sites and so on).
38 Invoice Verification (MM-IV)

Description Authorization Concept for Supplier Invoice is new in S/4HANA.
The previous concept was based on checking header data against the item authorization object for all items. The system checked for all items if a user was allowed
to complete certain activities in the plants.
With the new concept, the behaviour of the system is more comprehensive. The new concept introduces a header authorization object that enables the system to
perform the following authorization checks:
Check header data against the header authorization object (M_RECH_BUK). This authorization object checks the common activities a user performs for the header company
code.
Check item data against the item authorization object (M_RECH_WRK). This authorization object checks the common activities a user performs for the plant for the
respective item.
AA MOTORS Source System Transactions MIR4, MIR7, MIR5, MIRO, MRRL, MR8M, MIR6 are used.
Action / Impact User roles should be revisited.. Users working with supplier invoices, additionally need the authorizations based on M_RECH_BUK.
The standard roles delivered with SAP S/4HANA contain this new authorization object. If the customer roles are derived from these standard roles, one must do the
following:
✓ Edit the values of the organizational levels for the new authorization object M_RECH_BUK.
✓ Regenerate the profiles related to the roles using PFCG.
✓ If one has created a role by himself, he must manually insert the authorization object M_RECH_BUK into the role. One can do this preliminary work once SAP S/4HANA
is available.
Also,
• Upload of supplier invoice attachments can be implemented fully automated without user interaction.
• Fiori apps to help manage supplier invoices and payment blocks.
• Upload scanned invoice copies for manual invoice processing (optional integration with OCR via OpenText – additional license, additional configuration).
• Native integration with Business Network
Benefits The new authority concept for supplier invoice enables a simplified handling especially for invoice items w/o PO reference.

39 Logistics Information System (LIS)

Description LIS processing during any document processing means that document data will be prepared (transformed) into LIS structures and those data will be finally written into so
called LIS information structures. Customers can enrich those data structures as well as define their own information structures. LIS processing means that the document
processing time gets enlarged, increases significantly the memory footprint due to the LIS information structures and forces (at least for MM-IM) a serialized processing in
case of V1 mode. Data in those LIS information structures will be used for special reporting by customers.
A forced serialization of MM-IM document processing due to active LIS and a customizing of late lock strategy to enable parallel processing for MM-IM does not make sense
at all. Furthermore, several LIS key figures like # of times a zero stock would be reached by a posting, cannot be determined reliable in parallel processes. Hence, active LIS
and late lock mode is defined now as an inconsistent system state starting with S/4HANA 1610 OP.
AA MOTORS Source System Transactions MC-Q, MC+2, LBWE, LBWQ are used.
Action / Impact If an On-Premise system is configured for early lock strategy, then LIS and the INVCON message type can be used. In this case the processing will be internally switched
into the legacy mode. That means that none of the above-described optimizations will be executed. This is necessary just because the optimized coding does not fill the
internal XMabc tables with stock data in the key figure model anymore (just because in many cases stock data are not calculated at all) and the data in those internal tables
are required for LIS processing and the INVCON message type.
Future production analytics will be based on HANA, CDS views aggregating transactional data dynamically, and powerful analytical UIs for multi-dimensional reporting. With
this it will be possible to replace the current LIS. One will be able to use classic LIS and the future production analytics in parallel for some time as long as one does not
switch off the update of the LIS tables (Functionality available in SAP S/4HANA on-premise edition delivery but not considered as future technology).
Real modification of SAP coding by customers in the area of function group MBWL or the MIGO main program SAPMM07M and its includes using stock aggregate data from
the internal tables XMabc must be refactored. Implemented BAdI methods are not affected by this.
Benefits Once future production analytics supports all analytics requirements, one can switch off the update of the LIS tables. Once one has switched off updating LIS tables, they
will notice the following improvements:
• Improved performance of many transactions (fewer tables to update, fewer locking conflicts)
• Less memory required

40 IS-Auto - Maintain Parts Interchangeability

Description The Parts interchangeability functionality was earlier part of the ECC-DIMP is now available as part of SAP S/4HANA.
AA MOTORS Source System Transactions/Programs PIC01, PIC03 are used.
Action / Impact The functionality is decoupled from MPN (Manufacturer Part Number) and works without an MPN material. Additionally, the ECC-DIMP fields of vendor master are available
as part of business partner fields in SAP S/4HANA. The Purchasing view of business partner role ‘FLVN01 Vendor’ is enhanced with the Interchangeability tab.
Benefits Simplification….

41 Material Forecast
Description Material forecast planning is based on material consumption in which the historical consumption data is used to extrapolate the future consumption patterns, which are
directly used as requirement figures in the next planning run.
AA MOTORS Source System Transactions/Programs MP38, MP30 are used.
Action / Impact Migration to SAP S/4HANA is supported.
Only values that correspond to the current validity period of the product are taken into account. Values that are not in the validity period will be ignored.
Check ‘Material – Forecast Planning’ Object (using Staging Table).
Benefits

42 Project System Reporting

Selected Project Reporting and analytic functions are part of the SAP S/4HANA compatibility scope, which comes with limited usage rights.
Description
Transactions
CJI3 Project Actual Cost Line Items

AA MOTORS Source System CJI3N Projects Line Items Actual Costs New
CN43N Overview: WBS Elements
S_ALR_87013531 Costs/Revenues/Expenditures/Receipts
are used.
Hierarchy Report and Line-Item Report Reporting can be used as part of the SAP S/4HANA compatibility scope. An extension with SAP S/4HANA capabilities is under
investigation, to make hierarchy and line-item reports available as perpetual scope. Enhancements are communicated via SAP product roadmap.
Action / Impact Project System analytical apps from Smart Business for Project Execution are not available with SAP S/4HANA, this includes in SAP Fiori Apps.
Structure reports like – CN40, CN41, CN41N, CN42N, CN43, CN46, CN46N, CN47N – are available in SAP S/4HANA, they are extended by Key User Extensibility.
Benefits Selected Project Reporting and analytic functions are part of the SAP S/4HANA compatibility scope, which comes with limited usage rights.

43 Records and Case Management

Description Records and Case Management provides a record and document management system for the public sector.
One can use Records and Case Management to register, manage and process records and documents quickly and easily.
AA MOTORS Source System Transactions/Programs RMPS_SET_SUBSTITUTE is used.
Action / Impact SAP S/4HANA’s dispute management capability uses SAP’s case management and record management functionalities to provide a folder structure for the electronic records
created in the course of resolving customer disputes. Customer disputes are created in the SAP S/4HANA system as dispute cases, which consist of three elements. First,
the header contains data fields and attributes; second, a folder structure known as linked objects contains various folders such as business partner, disputed objects, etc.;
and finally, notes make up the final element of a dispute case. The folder structure of linked objects in a dispute case is derived from case management.
SAP S/4HANA dispute management is seamlessly integrated with accounts receivable. SAP S/4HANA enables one to create dispute cases from several accounts receivable
transactions. The header fields and linked objects of an existing dispute case also be updated through various accounts receivable processes.
When the collections department contacts a customer for overdue receivables, the outcome of that contact depends on the reason behind the nonpayment of invoices. A
customer may have missed the chance to pay on time and now promises to pay the invoice within a certain timeframe. Another possibility is that the customer is not happy
with the product or service and may raise a dispute case for the invoice. Without a system to streamline collections management processes, the recording and reporting of
customer contacts and their outcomes may not be consistent.
With S4CRM, the Investigative Case Management (ICM) is built in SAP S/4HANA to support full spectrum of investigation processes for any law enforcement authorities,
intelligence organizations or similar institutions to assist with their investigations. The ICM solution is founded on SAP Business Suite CRM. The solution reused standard
business objects like products, business partner, activity management, Case management etc. It is used by many customers around the world.
In the interest of modernizing the product for future sustainable roadmaps and to enable value added innovations, ICM has been moved to SAP S/4HANA, SAP’s intelligent
ERP. With this, ICM customers could take advantage of everything the SAP’s new digital core has to offer.
Investigative Case Management enables to manage investigation processes from start to finish and enables to set up and run functions and processes for cases, activities,
incidents, persons and organizations, objects, locations, documents, including all their relationships.
Further discussion can be planned whether S4CRM and Investigative Case Management (ICM) can be deployed to get specific functionalities.
Benefits ✓
✓
All authorized employees have central access to all required information.
Paper records and electronic records area are managed in the same system.
✓ Scanned documents can be stored.
✓ Storage costs of paper records are reduced.
✓ The transport time of files is reduced or eliminated completely.
✓ Storage costs for records are reduced.
✓ Fast administration and quick access to information for citizens.
✓ It is possible to view and submit records to external authorities without any time-consuming record transports.
✓ Records can be disposed of electronically.

44 SAP Business Partner for Financial Services

Description SAP Business Partner for Financial Services (SAP GP-FS) is the SAP application for saving and managing all customer details. One can process the business partner using
the business partner user interface, as well as through defined interfaces. This enables to integrate customer-specific data without having to make modifications and makes
the data release-insensitive.
The solution is developed by SAP as standard software for international companies.
AA MOTORS Source System Transactions BPCD is used.
Action / Impact SAP Business Partner for Financial Services is closely linked to other components. This ensures continuous processing.
Special tools are used by SAP Business Partner for Financial Services to manage the business partner dataset properly. You can use them to manage the following
business transactions:
Change documents
Document management
Authorizations
External data transfers
Benefits

45 SAP MRSS
SAP Multiresource Scheduling enables to find suitable resources (employees, materials, and tools ) for demands and assign them to the demands. Demands are units of
work from the areas of Plant Maintenance, or Project System, for which a resource is to be planned.
MRS runs fully integrated in the ERP system.

• PS Integration
Description • HR Integration
• PM Integration
• DBM Integration
SAP Multiresource Scheduling, option for SAP S/4HANA supports the short-term and long-term planning of projects, installations, and service activities. Existing SAP MRSS
8 needs to be upgraded to ‘SAP Multiresource Scheduling 1.0, option for SAP S/4HANA. Refer to SAP notes - 2332631, 2332632, 2914011.
AA MOTORS Source System Transactions /MRSS/PLBOGEN, /MRSS/PLBOORGM, /MRSS/PLBOORG, /MRSS/UTILREP are used.
Integration Feature in S/4HANA
Integration with SAP S/4HANA HR

One can use this feature to set up the use of HR persons in SAP Multiresource Scheduling and can transfer HR persons and all relevant data from SAP S/4HANA HR to SAP
Multiresource Scheduling, where one can assign them as resources to demands.
Integration with SAP S/4HANA EAM
One can use this integration scenario to plan resources for orders from Plant Maintenance (PM) and Customer Service (CS) and for networks from Project System (PS). One
can also perform capacity planning (such as capacity leveling) for these types of demand in SAP Multiresource Scheduling.
Integration with SAP Portfolio and Project Management for SAP S/4HANA
Action / Impact One can use this integration scenario to plan resources for project roles from SAP Portfolio and Project Management for SAP S/4HANA.
Web-based planning board
As an alternative to the Scheduler Workplace (SAP GUI), you can use the Web-based planning board for resource and demand planning.
Resource planning for orders and notifications from Plant Maintenance (PM) and Customer Service (CS)
One can use this feature to allocate suitable resources to order operations and notifications from Plant Maintenance and Customer Service.
The process starts in SAP S/4HANA with a requester creating a notification or order that is relevant for resource planning. The system then transfers all relevant data to SAP
Multiresource Scheduling and automatically creates a demand for each order operation or notification. Using the Scheduler Workplace (SAP GUI) or Web-based planning
board, you can then search for suitable resources based on resource availability and qualifications. When you assign a resource to a demand, the relevant data is transferred
back to the SAP S/4HANA system.
Benefits

46 Sales Activities
Description Sales Support: Computer-Aided Selling (SD-CAS) is not available in SAP S/4HANA, because it is not the target architecture. It is suggested to use SAP CRM on-premise
(side-by-side with SAP S/4HANA) or SAP Cloud for Customer.
AA MOTORS Source System Transactions VC/2 is used.
Action / Impact Sales Support is no longer available in SAP S/4HANA. The creation of new business documents or editing of migrated business documents is not possible.
Transaction VC/2 (Customer Master Data Sheet) is obsolete. Use Fiori App "Customer 360 Object Page" instead.
If f sales support functionality is requested, its suggested that customers start evaluating a side-by-side CRM on-premise scenario, or that they use Cloud for Customer.
Benefits Simplification.

47 Service Procurement
Description Lean service is newly introduced process in SAP S/4HANA to simplify service procurement. Here, service entry sheet is not the same as service entry sheet created via
ML81N.
Lean services use ‘Manage Service Entry Sheet’ app for confirmation of services (planned and unplanned). This can be mapped for approval process via flexible workflow.
AA MOTORS Source System Transactions ML81N, AC03, ML84, AC01, MSRV6 are used.
Action / Impact Material type ‘SERV’ for services is introduced for Product Master in S/4HANA for simplification purposes. When one uses material type SERV, some fields and departments
that are irrelevant in S/4HANA are hidden from the screen. This gives all transactions relevant for material master, a leaner and simplified look.
Configurations required for SERV can be seen in SAP Note 2224251.
DIEN material still works the same way as in ECC.
Difference is service material with SERV allows service entry sheet in app ‘manage service entry sheet’ and service material with DIEN allows goods receipt in MIGO / app
‘post goods receipt’.
When purchase requisition is created with product type ‘service’ OR catalog for service with ‘reference to service’ marked as yes – then ‘manage service entry sheet’ app
can be used.
Flow to procure services using Material type DIEN –

Create PR Convert to PO GR IR
Flow to procure services using Material type SERV –

Create PR Convert to PO Service Entry Sheet IR
Benefits Simplified approach .

48 Vehicle Management System

Description SAP S/4HANA Vehicle Management System (VMS) is a central solution for managing vehicles, processing transactions and capturing information in a database along the
vehicle lifecycle. It is completely integrated with the SAP S/4HANA standard components MM (Materials Management), SD (Sales and Distribution), CS (Customer Service)
and FI/CO (Financial Accounting and Controlling) and supports business processes that vehicle importers require when dealing with OEMs and dealers in new and used
vehicle sales.
AA MOTORS Source System Transactions VELO, VELORU, VELOE, OVELO20, OVELO21, VELOS are used.
Action / Impact SAP Digital Vehicle Hub represents the central vehicle repository along the automotive value chain, based on SAP Cloud Platform (SCP), and manages all types of vehicle-
related data. Vehicle-related data is usually generated and stored in the backend system, SAP provides the capability to integrate SAP Digital Vehicle Hub and SAP S/4HANA
VMS via SAP Cloud Platform Integration.
Vehicle Management System is integrated with Web-based user interface of the dealer portal, which is based on the SAP Business Client for HTML, the SAP Business Client
as a desktop-based integration platform, or on the SAP Enterprise Portal.
The Dealer Portal based on Discrete Industries Web Interface (DIWI) and Business Server Pages is not available with SAP S/4HANA.
The Web Dynpro based Dealer Portal is recommended as successor application. The user interface changes by the Dealer Portal switch, but the business processes are not
affected.
In case the conversion to SAP S/4HANA starts from SAP ERP 6.04 (Enhancement Package 4) or higher, the migration to the Web Dynpro based Dealer Portal could be
done before the system conversion.
Otherwise, the migration to the Web Dynpro based Dealer Portal needs to be done after the system conversion to SAP S/4HANA.
Enhancements to the BSP based Dealer Portal have to be reimplemented for the Web Dynpro Dealer Portal, if applicable.
Benefits

49 Warranty Claim
Warranty Claim Processing is a cross-application component that is completely integrated into the SAP solution, from master data management
Description (MM, SD, CS, PM) and pricing (SD) through checking master warranties and creating measurement documents (CS, PM) to posting FI documents
(FI/CO) and evaluation of the warranty data (SAP BW).
AA MOTORS Source System Transactions WTY, WTYSE, WTYRCL are used.
Warranty Claim Processing offers the following functions :

generating worklists, manual processing of warranty claims. finding warranty claims according to selection criteria, creating recalls and
authorizations, posting incoming parts that have to be returned, creating credit memo lists, mass processing, online reporting.
Action / Impact
Fiori Apps are available – one example - The Manage Supplier Claims application allow users to create a reimbursement request to a supplier for a
complaint or repair of a product. It contains detailed information of the complaint/repair, such as specific prices for the replaced material and labor
tasks, dates, and other related data.
Benefits Simplification.

50 Dealer Business Management

DBM (Dealer Business Management) is SAP's solution for automotive dealers. SAP DBM ( Dealer business Management ) provides the solution for automotive sales side and after sale side.
Description Incentive and Commission Management is integrated with all relevant applications to support all major business processes: DBM (Dealer Business Management) is SAP's solution for
automotive dealers. DBM-ICM technical packages deliver pre-configuration for DBM in Incentive and Commission Management.
Transactions /DBM/BOC08 (Create Output: DBM Order), /DBM/BOC10 (Display Output: DBM Order), /DBM/CASHDESK (Cash Desk), /DBM/CDESK_ROLE_COND (Determination of DBM Cash
Desk Role), /DBM/LBROP (Labor Value Maintenance), /DBM/ORDER01 (Create Order), /DBM/ORDER02 (Change Order), /DBM/PACKAGE_LIST1 (Package online reporting), /DBM/VM
AA MOTORS Source System (Vehicle Master), /DBM/VMODEL (Maintain Vehicle Model Master), /DBM/VM_LEAN (Vehicle - Fast Entry), /DBM/VM_OPT (Edit Model and Vehicle Options), /DBM/VSEARCH (Vehicle Search),
/DBM/WTY1 (Warranty Proposal/Determination), /DBME/MMA_VCHLI (Define Check List Items) are used.
SAP DBM is an SAP add on solution for the industry specialized requirement. Simply it’s an SAP industry vertical solution. This solution is basically used in the Automotive companies. SAP IS
auto is the full version solution for the Automotive companies who’s involved in full life cycle of the automotive manufacturing to Sales And after sales.
But SAP DBM ( Dealer business Management ) provides the solution for automotive sales side and after sale side. This is basically used by the automotive dealer companies world-wide. SAP
DBM covers the following areas and gives a full fledge solution on the requirements of the business:
1. Vehicle sales – mainly in the SD platform
2. Vehicle spare parts sales – mainly in the MM platform
3. Vehicle after sales services – mainly in the CS platform
Action / Impact proaxia engaged with SAP to migrate the Dealer Business Management solution to SAP S/4HANA and bring their innovative products on to SAP S/4HANA along with innovations and
integrations to Digital vehicle Hub and proaxia’s Digital Sales Workplace.
proaxia’s Vehicle Sales and Service has been associated with SAP under the ‘Co-Innovated with SAP’ program which offers support in:
• Development of applications, assessment against SAP product standards and certification of the solution.
• Opportunity to leverage SAP’s Industry Cloud and powerful cloud integration to foster innovation, collaboration for enterprises and business networks.
• Adoption of digital retailing options, such as contactless car buying and online dealerships.
• Dealers can use e-commerce technology, digital sales workplace and CX data to support omnichannel vehicle sales and other services, such as accepting trade-ins and arranging test
drives and deliveries.
• Complete connectivity provided between proaxia VSS Digital Sales Workplace and VSS Core solution with SAP S/4HANA backend applications as well as SAP CX.
1. Enables current and future business/retail models, technologies and requirements with Open architecture to support ongoing industry innovation and business models.
2. Handles the increased operational complexity and increases process transparency, retail efficiency and effectiveness, which can be used to increase customer satisfaction, leading to
loyalty and sufficient profitability.
Benefits 3. All sales processes are workflow-driven, self-documenting and omni-channel aware, allowing a fully flexible and the most advanced live and digital interaction between the salesperson
and the customer.
4. The end-to-end process is measured, reports and KPIs are generated real-time, current performance can be analyzed and focused measures taken to reach labor and parts revenue
objectives.

Functional Assessment – Relevant SAP Notes (1 / 3)
Following SAP Notes can be referred to for different SAP modules/business processes – to understand Simplification impact.
Module Sub Module SAP Note Title

Billing Billing document 2267375 S4TWL - Sales Activities
Billing Billing document 2267376 S4TWL - Billing Document Output Management
Billing Billing document 2791338 FAQ: SAP S/4HANA output management
Enterprise Asset Management Calibration Management 2270078 S4TWL - Scheduling of Maintenance Plan
Enterprise Asset Management Calibration Management 2270110 S4TWL - WebDynpro Application for Maintenance Planner (<= EhP4)
Enterprise Asset Management Preventive Maintenance 2270078 S4TWL - Scheduling of Maintenance Plan
Enterprise Asset Management Preventive Maintenance 2270110 S4TWL - WebDynpro Application for Maintenance Planner (<= EhP4)
Financial Accounting Bank Account Management 2270318 S4TWL - SEM Banking
Financial Accounting Bank Account Management 2832124 How to generate a vendor role FLVN00 during synchronization employee to BP
Financial Accounting Bank Account Management 2870766 S4TWL - CASH MANAGEMENT - Bank Accounts
Financial Accounting Fixed Assets Accounting 2270387 S4TWL - DATA STRUCTURE CHANGES IN ASSET ACCOUNTING
Financial Accounting Fixed Assets Accounting 2270388 S4TWL - ASSET ACCOUNTING
Financial Accounting General Ledger 2270339 S4TWL - GENERAL LEDGER
Financial Accounting Period-End Closing 2306348 GR/IR account clearing
Financial Accounting Period-End Closing 2332517 How to correctly create a revaluation depreciation area in asset
Financial Accounting Period-End Closing 2779519 GR/IR Inventories - Balance Summary: Report Entries not Cleared by GR/IR Clearing
Financial Accounting Period-End Closing 2834429 F-90 Error F5201 "Posting period xxx 2019 is not open"
Financial Accounting Period-End Closing 2915307 Year-end closing in Asset Accounting
Financial Accounting Period-End Closing 2943035 Migration of historical balances to SAP S/4HANA and SAP S/4HANA Cloud
Financial Accounting Period-End Closing 3012370 Open and Close Posting Periods for CO Transactions
Financial Accounting Period-End Closing 3026835 Program for year-end closing Asset Accounting: Error from incorrect fiscal year
Foreign Trade / Customs Payment Guarantee 2267310 S4TWL - Foreign Trade
Inventory and Warehouse Management Inbound Processing and Receipt Confirmation without Warehouse Management 2542099 S4TWL - Document Flow Consistency for Goods Receipt to Inbound Delivery
Inventory and Warehouse Management Interchangeable Parts 2957422 Management of interchangeability of part
Inventory and Warehouse Management Interchangeable Parts 3145820 MD04: Selection rule doesn't work for Interchangeable materials when MPN-MRP set view is on.
Management Accounting Cost Center Accounting 2270411 S4TWL - GENERAL COST OBJECTS AND COST OBJECT HIERARCHIES
Management Accounting Cost Element Accounting 2270419 S4TWL - COST ELEMENTS
Management Accounting Cost Element Accounting 2349297 S4TWL - Reporting/Analytics in Controlling
Management Accounting Internal Order 352984 S4TWL - VA01: Planned revenue from sales order for internal order
Management Accounting Profit Center Accounting 2270407 S4TWL - PROFIT AND LOSS PLANNING AND PROFIT CENTER PLANNING


Management Accounting Profit Center Accounting 2425255 Profit Center Accounting in the universal journal in SAP S/4HANA, on-premise edition
Management Accounting Profit Center Accounting 2993220 S4TWL - EC-PCA - Classical profit center accounting
Management Accounting Profitability Accounting 2221237 FAQ in CO-PA (Part III. of note 553626)
Management Accounting Profitability Accounting 2349278 S4TWL - Profitability Analysis
Master Data Customer Master 2265093 S4TWL - Business Partner Approach
Master Data Customer Master 2379157 S4TWL - Business Partner BUT000/Header Level Time Dependency
Master Data Maintain Vendor Master 2265093 S4TWL - Business Partner Approach
Master Data Maintain Vendor Master 2379157 S4TWL - Business Partner BUT000/Header Level Time Dependency
Master Data Maintain contact person 2265093 S4TWL - Business Partner Approach
Master Data Maintain contact person 2379157 S4TWL - Business Partner BUT000/Header Level Time Dependency
Product Lifecycle Management BOM Explosion 2267880 S4TWL - BOM, Routing, Production Version
Product Lifecycle Management Manage Object Dependency 2665488 Header information in the object dependencies editor
Product Lifecycle Management Manage Order BOM 1962059 FAQ: Order BOM's
Product Lifecycle Management Manage Sales BOM 2716494 ARM Returns for Manual Bill of Materials (BOMs)
Product Lifecycle Management Manage Sales BOM 2796264 Sales order BOM cannot be exposed when running MRP
Product Lifecycle Management variant-configuration-modeling 2267873 S4TWL - Variant Configuration
Production Planning Discrete Manufacturing 3164190 General Restrictions and Implementation Recommendations for PPDS for SAP S/4HANA 2022
Production Planning Process Manufacturing 2889468 S4TWL - Warehouse Control Interface
Production Planning Production Planning 2268069 S4TWL - Simplified Sourcing
Production Planning Production Planning 2268085 S4TWL - MRP in HANA
Project System External Services Planning 2270263 S4TWL - Project Planning Board, Gantt-Chart, Hierarchy and Network Graphics
Project System Pre-Conceptualization / Conceptualization 2267189 S4TWL - Workforce Planning
Project System Pre-Conceptualization / Conceptualization 2352369 S4TWL - Handling Large Projects Business Functions
Project System Pre-commissioning & Commissioning 2267182 S4TWL - Selected project financial planning and control functions
Project System Project Completion 2270261 S4TWL - Navigation to Project Builder instead of special maintenance functions
Project System Project Planning 2267188 S4TWL - Simplification of Date Planning Transactions
Purchasing Compare supplier quotations 2619403 Manage Workflows for Supplier Quotation configuration
Purchasing Find new source of supply 2332710 S4TWL - RFQ Simplified Transaction
Purchasing Inter-Company and Intra-Company Stock Transfer 3216468 Procurement - Inventory Management - Standard behaviors guide and How-to scenarios
Purchasing Monitor the output of messages 2267444 S4TWL - Output Management Adoption in Purchase Order


Purchasing Monitor the output of messages 2470711 S4TWL - OUTPUT MANAGEMENT
Purchasing Monitor the output of messages 2608890 Standard S/4HANA Output Control settings for Purchasing (output forms and processing programs)
Purchasing Monitor the output of messages 2791338 FAQ: SAP S/4HANA output management
Purchasing Process purchasing info records 2267449 S4TWL - Classic MM-PUR GUI Transactions replacement
Purchasing Process source list 2267449 S4TWL - Classic MM-PUR GUI Transactions replacement
Purchasing Purchase external services 3095750 Performance issue with External Service Purchase Order
Purchasing Release Purchase Requisition 3035081 Release Procedure copied from Purchase Order to Purchase Requisition
Purchasing Release purchasing documents 2565597 Release strategy not appearing in purchase order/ contract/ schedule agreement
Quality Management Quality Notification 2338215 S4TWL - Redundant Transactions in QM
Quality Management Quality Notification 3215767 Integration of SAP Quality Issue Resolution in the Quality Notification
Sales Contract 2267350 S4TWL - Advanced Order Processing and Billing for Contractors to the public sect
Sales Credit Management 2270544 S4TWL - Credit Management
Sales Credit Management 2898525 Credit status of sales documents after migration to S/4HANA
Sales Domestic Sales Order 2267306 S4TWL - SD Simplified Data Models
Sales Maintain contact person for customer 2265093 S4TWL - Business Partner Approach
Sales Maintain contact person for customer 2713963 FAQ: CVI - Customer Vendor Integration for system conversion to SAP S/4HANA
Sales Maintain contact person for customer 2800183 Maintain Title, Name and Search Term Fields in Contact Person Standard Business Address
Sales Quotation 2900300 No order types in 'Manage Sales Contracts' App (F1851) or 'Manage Sales Quotations' App (F1852)
Sales Returns Order 2992464 Document Flow for Return Deliveries
Sales Service Contract 2984247 Situation Handling for Service Contract Header Object Pages in S/4HANA
Shipping and Transportation Outbound Delivery 2267348 S4TWL - Simplification in SD Analytics
Shipping and Transportation Shipment Cost Document 3051698 S4TWL – Shipment Cost Processing
Shipping and Transportation Shipment Document 2221849 Customizing and process flow of SD scheduling
Shipping and Transportation Shipment Document 2470711 S4TWL - OUTPUT MANAGEMENT
Shipping and Transportation Shipment Document 2791338 FAQ: SAP S/4HANA output management
Shipping and Transportation Shipment Document 3232331 SAP S/4HANA 2022 Supply Chain for Transportation Management - Release information
Treasury Cash and Liquidity Management 2270400 S4TWL - CASH MANAGEMENT - GENERAL
Treasury Cash and Liquidity Management 2781585 S4TWL - CASH MANAGEMENT - Memo Record

Of the custom code will be 4594 Total Custom Code Developments
39% impacted due to the

S/4HANA Simplification 1770 Total Custom Code Impact
items and the HANA DB.
428 HANA DB Code Impact
1506 S/4HANA 2023 Data Model Code Impact
2784 SPAU (ABAP Objects)*
116 SPDD (Data Dictionary)*
HANA DB Code impact 9%
SAP S/4HANA 2023 Code impact 33%
Technical *SPDD and SPAU numbers are indicative

*This includes program, function group and class. Tables, data elements, etc. aren’t covered in the above items since very few are impacted
Assessment
Summary-S/4HANA *Custom Code Impact Numbers are indicative. This may differ from actual impact - based on the technical ATC analysis - in S/4HANA System

Remediation Remediation
Remediation Remediation
Remediation Approach - Approach -
Check Description Type - Type -
Type Automatic (Using Manual (Using
Mandatory Optional
IHC Tool) IHC Tool)
Mandatory ADBC Interface 75 0 0 75
Mandatory DB Hints 56 0 56 0
DB Operations in Pool/Cluster
Mandatory 2 0 0 2
Tables
Mandatory Native SQL 7 0 0 7
Optional Problematic SELECT * Statement 0 3390 1695 1695
SELECT statement with DELETE
Optional 0 1094 1094 0
statement
SELECT/OPEN CURSOR without
Mandatory 868 0 694 174
ORDER BY
Mandatory Scan a Program 8 0 0 8
Statements with Subsequent
Optional 0 4 4 0
CHECK
Unsecure use of FOR ALL
Mandatory 584 0 467 117
ENTRIES
GRAND TOTAL 1600 4488 4010 2078
HANA DB Code
Analysis(1/1)
Automatic: Remediation will be done automatically by the tool. Manual intervention is not required
Semi-Automatic: Tool will propose the correction required. Code change to be done manually.
Manual: Code change needs to be done manually
NB: These are instances of changes across 428 unique programs which are affected by HANA DB Code Impact
ABAP Custom Code is impacted due to SAP S/4HANA Simplification changes. For AA MOTORS, custom
objects are checked against S/4HANA 2023 Simplification database and the result is summarized as
seen below.The result is shown for different customer packages – so that AA MOTORS can get an idea of
simplification impact in specific area of these customer packages.
Simplification Item Category specifies whether findings are related to functionality which is not available
anymore or they have been changed in an incompatible way.For each of these simplification items, there
is an SAP Note – which helps to analyze the finding. The details for which is provided in the appendix.
Impact due to Change in SAP Impact due to functionality not
Package Description Grand Total
Data Model supported/recommended
/DBME/CD8 - Common Functionalities for DBM
6 6 12
8.0
/DBME/CEE - DBM|E Common - ECC
1 3 4
dependent
/DBME/CMA - Common Functionalities
5 2 7
independent of DBM
/DBME/MD8 - MSA Functionalities for DBM 8.0 89 74 163
/DBME/MMA - MSA Main Functionalities

1 12 13
independent of DBM
/HCR/BC0_BASIC - Basic elements (contants,
14 32 46
description methods etc.)
/HCR/BC1_UTILS - Common development
0 2 2
utilities
/HCR/MDM1_CORE - Core MDM Functionality 6 60 66

Simplification
/HCR/MDM3_COMMON - Common MDM
Code Analysis- functions
0 3 3
S/4HANA 2023 /HCR/SD3_COMMON - SD Output processing,

2 15 17
common definitions
(1/12)
Grand Total 124 209 333

/HCR/VMS1_CORE - Core VMS Functionality 0 1 1
/HCR/VMS10_ACTION_ENGINE - VMS Action

2 0 2
Engine
/HCR/VMS21_VELO_EXTENSIONS - Velo
0 1 1
extensions
/HCR/VMS3_COMMON - Common VMS
8 44 52
functions
Z_DEV - Developmnets and enhancements
6 0 6
C4C
Z001 - Customer development class 8 27 35
ZAR_TRANSLATION - Arabic Translation

0 21 21
Package
ZBC3_COMMON - Common 0 17 17
Simplification
Code Analysis- ZBW - BW Package 48 257 305
S/4HANA 2023 ZCA0_BASIC - Basic @ Cross Application 0 6 6
(2/12) Grand Total 72 374 446

ZCA1_CORE - Core @ Cross Application 19 9 28
ZCA2_ENHANCEMENTS - Enhancements @
7 26 33
Cross Application
ZCA3_COMMON - Common @ Cross
93 314 407
Application
ZCA5_REPORTING - Reporting @ Cross
12 17 29
Application
ZCA8_MIGRATION - Migration @ Cross
10 11 21
Application
ZCRM_DEV - Package for CRM developments in
68 162 230
ECC
ZDBME_M - DBM|E MSA Vehicle IObject
0 3 3
Enhancements
ZFI1_CORE - Core @ Finance and Controlling 7 14 21

Simplification
ZFI2_ENHANCEMENTS - Enhancements @
Code Analysis- Finance and Controlling
230 525 755
S/4HANA 2023 ZFI3_COMMON - Common @ Finance and

25 11 36
Controlling
(3/12)

ZFI5_REPORTING - Reporting @ Finance and
135 382 517
Controlling
ZFI6_PRINTOUTS - Printouts @ Finance and
51 18 69
Controlling
ZFI7_INTERFACES - Interfaces @ Finance and
8 0 8
Controlling
ZFIORI_DEV - Fiori Development 0 294 294
ZFIORI1_CORE - Core @ FIORI 6 4 10
ZFIORI2_ENHANCEMENTS - Enhancements @
0 95 95
FIORI
ZHCM2_ENHANCEMENTS - Enhancements @
15 54 69
Human Capital Management
ZHCM3_COMMON - Common @ Human Capital
0 1 1
Simplification Management
ZHCM5_REPORTING - Reporting @ Human
Code Analysis- Capital Management
14 62 76
S/4HANA 2023 ZHCM8_MIGRATION - Migration @ Human

0 4 4
Capital Management
(4/12)

ZMDM1_CORE - Core @ Master Data 4 25 29
ZMDM2_ENHANCEMENTS - Enhancements @
15 16 31
Master Data
ZPPR1_CORE - Core @ Parts Procurement 6 28 34
ZPPR2_ENHANCEMENTS - Enhancements @
280 1491 1771
Parts Procurement
ZPPR3_COMMON - Common @ Parts
25 174 199
Procurement
ZPPR5_MATERIAL_OVERVIEW - Material
13 131 144
overview
ZPPR5_REPORTING - Reporting @ Parts
148 962 1110
Procurement
ZPPR6_PRINTOUTS - Printouts @ Parts
18 132 150
Simplification Procurement
ZPPR73_OEM_INTERFACES - PPR7 - OEM
Code Analysis- Interfaces
0 47 47
S/4HANA 2023 ZPPR74_LANDING_COSTS - PPR7 - Landing

0 77 77
Costs
(5/12)

ZPPR8_MIGRATION - Migration @ Parts
1 2 3
Procurement
ZPSA1_CORE - Core @ Parts Sales 3 124 127
ZPSA2_ENHANCEMENTS - Enhancements @
17 240 257
Parts Sales
ZPSA3_COMMON - Common @ Parts Sales 0 3 3
ZPSA5_REPORTING - Reporting @ Parts Sales 45 319 364
ZPSA6_PRINTOUTS - Printouts @ Parts Sales 14 83 97
ZPSA7_INTERFACES - Interfaces @ Parts

1 9 10
Sales
ZRAC1_CORE - Core @ Rent a Car 35 266 301

Simplification ZRAC11_ACTION_IMPL - VMS (RaC) Action
35 237 272
Code Analysis- implementation
S/4HANA 2023 ZRAC12_QMC - RaC Quotations Management

Cockpit
25 247 272
(6/12) Grand Total 176 1530 1706

ZRAC2_ENHANCEMENTS - Enhancements @
51 559 610
Rent a Car
ZRAC3_COMMON - Common @ Rent a Car 9 29 38
ZRAC5_REPORTING - Reporting @ Rent a Car 37 128 165
ZRAC8_MIGRATION - Migration @ Rent a Car 3 13 16
ZRAC9_ADMIN_TOOLS - Admin Tools @ Rent a

1 0 1
Car
ZSD2_ENHANCMENTS -
7 42 49
ZSD2_ENHANCMENTS
ZSD3_COMMON - ZSD3_COMMON 1 3 4
ZSD5_REPORTING - ZSD5_REPORTING 9 64 73
Simplification
Code Analysis- ZSD6_PRINTOUTS - ZSD6_PRINTOUTS 137 857 994
S/4HANA 2023 ZSEEZ_PAD - Package for Seez_PAD & SAP

Integration
8 12 20
(7/12) Grand Total 263 1707 1970

ZSRV1_CORE - Core @ DBM Service 1 1 2
ZSRV2_ENHANCEMENTS - Enhancements @
144 472 616
DBM Service
ZSRV21_IOBJECT - DBM: iObject
0 1 1
enhancement
ZSRV22_TOOLS - DBM Order Task Tools 3 0 3
ZSRV3_COMMON - Common @ DBM Service 5 5 10
ZSRV5_REPORTING - Reporting @ DBM

92 256 348
Service
ZSRV6_PRINTOUTS - Printouts @ DBM Service 5 37 42
ZSRV7_INTERFACES - Interfaces @ DBM

0 1 1
Service
Simplification ZSRV8_MIGRATION - Migration @ DBM
4 8 12
Code Analysis- Service
S/4HANA 2023 ZSRV9_ADMIN_TOOLS - Admin Tools @ DBM

Service
0 3 3
(8/12) Grand Total 254 784 1038

ZTMC - TMC 2 2 4
ZTMC_DMS - TMC DMS Package 2 0 2
ZVMS1_CORE - Core @ Vehicle Sales,

86 1167 1253
Procurement and Used Cars
ZVMS11_ACTION_IMPL - VMS: actions
149 823 972
implementation
ZVMS12_ASN - VMS: Shipping list 12 15 27
ZVMS13_CQM - VMS: Confirmed quotation

9 28 37
management
ZVMS2_ENHANCEMENTS - Enhancements @
323 1425 1748
Vehicle Sales, Procurement and Used Cars
ZVMS3_COMMON - Common @ Vehicle Sales,
9 55 64
Procurement and Used Cars
Simplification ZVMS5_REPORTING - Reporting @ Vehicle
137 830 967
Code Analysis- Sales, Procurement and Used Cars
S/4HANA 2023 ZVMS6_PRINTOUTS - Printouts @ Vehicle

Sales, Procurement and Used Cars
24 146 170
(9/12) Grand Total 753 4491 5244

ZVMS72_INT_FRAMEWORK - VMS7 - Interface
4 4 8
Framework
ZVMS8_MIGRATION - Migration @ Vehicle
8 12 20
Sales, Procurement and Used Cars
ZWMS2_ENHANCEMENTS - Enhancements @
7 7 14
Warehouse Management
ZWMS5_REPORTING - Reporting @
15 70 85
Warehouse Management
ZWMS6_PRINTOUTS - Printouts @ Warehouse
8 57 65
Management
ZWTY1_CORE - Core @ Warranty 3 141 144
ZWTY2_ENHANCEMENTS - Enhancements @
5 32 37
Warranty
ZWTY3_COMMON - Common @ Warranty 3 49 52

Simplification
Code Analysis- ZWTY5_REPORTING - Reporting @ Warranty 10 55 65
S/4HANA 2023 ZWTY7_INTERFACES - Interfaces @ Warranty 2 3 5
(10/12) Grand Total 65 430 495

ZWTY8_MIGRATION - Migration @ Warranty 1 6 7
ZWTY9_ADMIN_TOOLS - Admin Tools @

0 10 10
Warranty
Grand Total 1 16 17
Simplification
Code Analysis-
S/4HANA 2023
(11/12)

S/4HANA Code Impact- Change Type View # Changes
Impact due to functionality not supported/recommended 14630
Impact due to Change in SAP Data Model 2917
Total 17547
Simplification
Code Analysis-
S/4HANA 2023
(12/12)

ABAP Custom Code is impacted due to SAP S/4HANA Simplification changes. For 'AA MOTORS',
custom objects are checked against S/4HANA '2023' Simplification database and the result is
summarized module-wise as seen below. The result is shown for different modules- so that 'AA
MOTORS' can get an idea of simplification impact module wise.
Module Name Module Description Count
AC Accounting - General 77
AP Application Platform 6
BC Basis Components 220
CA Cross-Application Components 93
CO Controlling 13
CS Customer Service 1
DI Discrete Industries 2
EC Enterprise Controlling 6
EHS Environment, Health and Safety 8
FI Financial Accounting 34
FS Financial Services 20
ICM Incentive and Commission Management (ICM) 36
IS IS 457
LE Logistics Execution 639
LO Logistics - General 4962
Simplification MM Materials Management 2511
Impact - SAP PA Personnel Management 207
Module wise (1 / 2) PM Plant Maintenance 30
PP Production Planning and Control 70
PS Project System 20

ABAP Custom Code is impacted due to SAP S/4HANA Simplification changes. For 'AA MOTORS',
custom objects are checked against S/4HANA '2023' Simplification database and the result is
summarized module-wise as seen below. The result is shown for different modules- so that 'AA
MOTORS' can get an idea of simplification impact module wise.
Module Name Module Description Count

PT Personnel Time Management 11
QM Quality Management 2
SCM Supply Chain Management 1
SD Sales and Distribution 8098
Technical Technical 3
WEC Web Channel 20
Grand Total 17547
Simplification
Impact - SAP
Module wise (2 / 2)

IDoc Details Number of IDoc's
Inbound Custom IDoc 0
Inbound Standard IDoc 9
Outbound Custom IDoc 0
Outbound Standard IDoc 13
Total 22
IDoc Details
Note: Please note that these IDoc counts are present in the client system and needs to be tested after upgrade.

This is the list of Total Custom Programs Used. 407 number of Custom Programs are Used. These
numbers are derived from 3 months (JUNE 2024 TO AUGUST 2024) of Usage Statistics from
Production Server and should be considered as base of analysis.
Package Name Count of Programs Used
/DBME/MMA 3
/HCR/MDM1_CORE 1
Z001 4
ZAR_TRANSLATION 2
ZBC_SECU 2
ZCA0_BASIC 2
ZCA1_CORE 2
ZCA2_ENHANCEMENTS 5
ZCA5_REPORTING 4
ZCRM_DEV 9
ZFI2_ENHANCEMENTS 37
ZFI3_COMMON 4
ZFI5_REPORTING 30
ZFI6_PRINTOUTS 10
ZFI7_INTERFACES 1
ZFIORI2_ENHANCEMENTS 1
ZHCM2_ENHANCEMENTS 21
ZHCM3_COMMON 3
Total Custom ZHCM5_REPORTING 37
Programs Used ZHCM7_INTERFACES 2
(1 / 3) ZHCM8_MIGRATION 1
ZPPR2_ENHANCEMENTS 23
ZPPR5_MATERIAL_OVERVIEW 1
ZPPR5_REPORTING 38
ZPPR6_PRINTOUTS 1
ZPPR73_OEM_INTERFACES 6
ZPPR74_LANDING_COSTS 6
ZPPR7_INTERFACES 2
ZPSA2_ENHANCEMENTS 4
ZPSA5_REPORTING 5
ZRAC12_QMC 1
ZRAC1_CORE 1
ZRAC2_ENHANCEMENTS 6
ZRAC5_REPORTING 6
ZSD5_REPORTING 3
ZSRV2_ENHANCEMENTS 17
ZSRV5_REPORTING 31
ZSRV6_PRINTOUTS 2
ZSRV7_INTERFACES 1
ZSRV8_MIGRATION 2
ZTMC 2
ZVMS11_ACTION_IMPL 1
ZVMS12_ASN 1
ZVMS13_CQM 2
ZVMS1_CORE 3
ZVMS2_ENHANCEMENTS 35
Total Custom ZVMS5_REPORTING 13
Programs Used ZVMS6_PRINTOUTS 2
(2 / 3) ZVMS7_INTERFACES 1
ZWMS5_REPORTING 5
ZWTY5_REPORTING 3
ZWTY7_INTERFACES 1
ZWTY9_ADMIN_TOOLS 1
Grand Total 407
Total Custom
Programs Used
(3 / 3)

In SAP ECC system, unused code increases the code base in scope of any
SAP S/4HANA conversion project, and therefore also increases the complexity, risk, maintenance effort,
testing effort and cost in all phases of these projects. Removing unused code upcoming S/4HANA
conversions will allow one to focus on strategic custom code, which needs to be analysed and maintained.
This is the list of Total Custom Programs Unused. 536 number of Custom Programs are Unused. These
numbers are derived from 3 months (JUNE 2024 TO AUGUST 2024) of Usage Statistics from Production
Server and should be considered as base of analysis.
Package Name Count of Programs Unused

/DBME/CCC 1
/DBME/CLC 4
/DBME/CMA 5
/DBME/MD8 2
/DBME/MMA 9
/HCR/BC0_BASIC 1
/HCR/BC11_SH 2
/HCR/MDM1_CORE 1
/HCR/ORM_EXAMPLE 1
/HCR/SD1_PRINTOUTS 4
/HCR/SD3_COMMON 2
/HCR/STMS 1
/HCR/VMS21_VELO_EXTENSIONS 1
Total Custom Z001 4
Programs ZAR_TRANSLATION 5
Unused (1 / 4) ZAUDIT 2
ZBC9_ADMIN_TOOLS 5
ZBC_SECU 7

ZBW 6
ZCA2_ENHANCEMENTS 1
ZCA3_COMMON 4
ZCA5_REPORTING 6
ZCA8_MIGRATION 3
ZCAX_SAMPLES 1
ZCRM_DEV 8
ZDDX 21
ZFI1_CORE 2
ZFI2_ENHANCEMENTS 37
ZFI3_COMMON 5
ZFI5_REPORTING 30
ZFI6_PRINTOUTS 6
ZFI7_INTERFACES 1
ZFI8_MIGRATION 3
ZFIORI_DEV 1
ZHCM1_CORE 2
ZHCM2_ENHANCEMENTS 22
ZHCM5_REPORTING 22
ZHCM8_MIGRATION 1
ZJKIT 2
ZMDM2_ENHANCEMENTS 1
Total Custom ZPPR1_CORE 3
Programs ZPPR2_ENHANCEMENTS 17
Unused (2 / 4) ZPPR3_COMMON 1
ZPPR5_REPORTING 18
ZPPR6_PRINTOUTS 7
ZPPR73_OEM_INTERFACES 1
ZPPR74_LANDING_COSTS 3
ZPPR8_MIGRATION 1
ZPPR9_ADMIN_TOOLS 1
ZPSA2_ENHANCEMENTS 6
ZPSA3_COMMON 1
ZPSA5_REPORTING 4
ZPSA6_PRINTOUTS 3
ZPSA7_INTERFACES 1
ZRAC2_ENHANCEMENTS 8
ZRAC5_REPORTING 9
ZRAC8_MIGRATION 6
ZRAC9_ADMIN_TOOLS 2
ZRFCQPERF 1
ZSD6_PRINTOUTS 37
ZSRV1_CORE 1
ZSRV23_HR_MRS 1
ZSRV2_ENHANCEMENTS 15
ZSRV5_REPORTING 15
ZSRV6_PRINTOUTS 11
ZSRV8_MIGRATION 11
ZSRV9_ADMIN_TOOLS 1
ZTMC 1
Total Custom ZVMS12_ASN 2
Programs ZVMS1_CORE 4
ZVMS2_ENHANCEMENTS 36
Unused (3 / 4) ZVMS3_COMMON 4
ZVMS5_REPORTING 18
ZVMS6_PRINTOUTS 6

ZVMS7_INTERFACES 3
ZVMS8_MIGRATION 15
ZVMS9_ADMIN_TOOLS 1
ZWMS2_ENHANCEMENTS 1
ZWMS6_PRINTOUTS 2
ZWTY5_REPORTING 7
ZWTY7_INTERFACES 1
ZWTY8_MIGRATION 3
ZWTY9_ADMIN_TOOLS 5
Grand Total 536
Total Custom
Programs
Unused (4 / 4)

There are 872 SAP delivered programs copied and modified in the system. This gives
an idea which are the places where SAP's code is copied and then modified.
Recommendations Clone Analysis

600
Very similar SAP codes should be reviewed to
decide if the current version of standard SAP
provides the missing functionality 500
Check the program for

syntactical correctness. 400
Version compares the standard program

300
before upgrade and after upgrade and take a
call if those changes are important for the Clone Analysis
custom program as well.
200
Since there is a major change in code version,
test all these programs.
100
The original objects (Standard SAP Program)
continue receiving code corrections and
additional functionality with system updates, 0
Identical Very Similar Similar Partly
while clones don't. Also, clones are not
Source Source Source Similar
Custom detected during system conversion. This is Code Code Code Source
why, they represent a risk to system stability. Code
Development: Try to use the standard ones.
Clone Analysis Number of
550 271 49 2
objects

Important Points
All custom code that you keep will have to be adopted to the code line of SAP S/4HANA.
Prepare a backup copy of deleted objects and a tested restore procedure before giving a green light
to custom code deletion. If one retains a (downsized) production SAP ECC for legal or auditing
reasons, it can at the same time serve as a backup repository for the obsolete custom code. If there
is a plan to use a data retention solution and to sunset the production system, please consult the
software vendor on the available options.
ABAP development tools in Eclipse enable the automated adaptation of custom code with only a few clicks
through quick fixes. With the quick fixes delivered by SAP as part of ABAP development tools, one can expect
an automation rate of around 60%. Explore it in detail.
Avoid taking orphaned developments (developments without proper documentation and/or owner) into SAP
S/4HANA system. The system conversion is the right time to reassess and decide on the options for such
developments.
The ABAP test cockpit (ATC) offers performance checks to reveal poorly performing ABAP code. Invest in
performance testing and address the revealed performance issues. Schedule a volume and performance test
and allocate time for performance optimization. Using production-like hardware for both database server and
application servers is essential; experience shows that many post-go-live issues could have been avoided
through more diligent performance testing.
Custom
Development:
Best Practices

Append Structure
The following SAP tables have custom append structures and will require adjustments due to
S/4HANA Data Model Changes. There is an impact followed by action when these tables will be
migrated to S/4HANA. Since these tables have replacement objects (CDS Views) in S/4HANA,
extension CDS views can be created to enrich the standard CDS views with the custom fields in
append structure. This will be an action for ABAP team and inclusion of custom field should be
confirmed by functional team.
This is as per SAP Note 2242679 - Redirect inconsistency - Proxy Substitution.

Table Name Append Structure Name
MARC ZEMARC9
Since this table has replacement objects (CDS Views) in S/4HANA, extension CDS views must be created to
enrich the standard CDS views with the custom fields in append structure. This is as per SAP Note 2242679 -
Redirect inconsistency - Proxy Substitution.
Create an EXTEND VIEW

Standard Table For APPENDs on structures of tables for the above-described cases use ABAP Development Tools (ADT) Core
Data Services (CDS) and create a new DDL source (ABAP Core Data Services - Data Definition) with name
Append Structure <Name of the append>_DDL. Enter a description like 'Extension view for Append <Name of the append>'.
Select the template 'Extend View' and adopt the proposed coding EXTEND VIEW <proxy view name for table>
with <Name of the append>_E

Package Wise Count of Objects which has Database Operations on
tables being replaced by Compatibility Views in S/4HANA
SAP S/4HANA is integrated with the underlying SAP HANA platform. With Simplification
changes, some data dictionary tables are removed, changed, or consolidated and are
replaced by Compatibility views – in order to leverage the full power of the columnar in-
memory concepts of SAP HANA. In order to continue with customer’s existing modification
in custom code, SAP has introduced compatibility views to keep custom interfaces,
transactions, and other code running. If a compatibility view is in place for an obsolete table,
requests to access that table are redirected to newly introduced table(s) by the help and
logic provided in the compatibility view. However, compatibility view is not a simple 1:1
reference to another table. Some logic is required to redirect the request towards an old ERP
interface to the new S/4HANA data model. This logic is implemented as ABAP Core Data
Services, and SAP S/4HANA compatibility views are CDS views. These compatibility views
provide a kind of workaround, but it is not best practice, nor can the same functionality or
performance guaranteed if one will rely on them. So,instead of adjusting the new SAP data
model in S/4HANA to old and obsolete processes, interfaces or APIs, a redesign to
leverage the new data model directly is recommended. In this analysis, the custom
code/objects which contain database operations (INSERT/UPDATE/MODIFY/DELETE) on
tables being replaced by Compatibility Views in S/4HANA, are found and shown.
Package Wise Count of report which has database Operations
Objects with ZFI2_ENHANCEMENTS 3
Database ZFI5_REPORTING 11
Operations ZVMS2_ENHANCEMENTS 1
Grand Total 15

SAP provides a limited use right to SAP S/4HANA On Premise customers to run certain classic SAP ECC
solutions on their SAP S/4HANA installation (as Compatibility Pack). Condition is that these customers
have licensed the applicable solutions as set forth in their License Agreements. This use right expires on
Dec 31, 2025 (for CS, PP-PI, LE-TRA, it extends till end 2030) and is available to installed-base as well
as net-new customers.
Customers must adapt custom code, change customization, train users, migrate data - when they are
planning to migrate from Compatibility Scope to alternative solution in S/4HANA. SAP will not support
related development objects, after expiration of usage rights - if custom code refers to Compatibility
Scope functionality.
SAP recommends that customers check their Compatibility Scope usage in advance to start their
transition and plan accordingly. This can reduce change management efforts for the adoption of a new
data model.
All system conversions done after 2025 are required to include the migration to the designated
alternative functionalities of Compatibility Scope directly in the conversion project.
This assessment checks the AA MOTORS usage data (ST03N) and assess component and sub-
component wise, in case they are designed to be part of SAP’s compatibility pack.
Transaction /. SAP S/4HANA Application
Component Subcomponent Comment SAP Note
Program Compatibility Pack Component
/ MRSS /
POT_CREATE_CAPA
_POTS / / MRSS /
CP-SAP Multiresource
POT_CREATE_CAPA complete solution CA-MRS
Scheduling
_POTS / / MRSS /
POT_CREATE_CAPA
_POTS /
Provide a superior base for decision making in
realtime through integrated revenue and cost
Compatibility Pack KCH1 / KCH2 /
EC-PCA - Classical
accounting.
KCH3 / KE52 / KE53 CP-SAP ERP
Assessment (1/4) / KEMDM /
SAPMKEC1N
EC-PCA profit center
accounting
Foundation Starter
EC-PCA Assign costs, revenues into P&L and balance sheet in
realtime to provide the basis for legal as well as
2993220
internal segment reporting. Record costs and

revenues with highest accuracy and by market
segment.
Electronic Records -
CP-SAP ERP Replacement of legacy functionality Electronic
AUT10 Electronic Records Basic Production LO-ELR 2268131
Foundation Starter Records by successor functionality.
Execution

Transaction / SAP S/4HANA Application
CJI3 / CJI3N /
Current project reporting and analytic functions with
CJ43N / RKPEP003 / CP-SAP ERP PS-IS-REP-ACC,
Project Reporting PS-Project Reporting PS are still available with SAP S/4HANA but not 2267286
RPSISPE000 / Foundation Starter PS-IS-REP-LOG
considered as strategic any longer.
S_ALR_87013531
Usage of SAP
Usage of SAP standard ledgers will expire as
standard ledgers will
outlined in the relevant compatibility scope items. 2474069,
GGB0 / GRR2 / FI-SL / special expire as outlined in CP-SAP ERP FI-SL-VSR,
Usage of customer-defined ledgers will be 3015013,
GRR3 ledger the relevant Foundation Starter FI-SL-IS
supported with limitations. Future technical usage of 3006586
compatibility scope
these ledgers is under discussion.
items.
Compatibility Pack
Assessment (2/4)

Transportation (LE- CP-SAP ERP The Logistics Execution Transportation (LE-TRA) is is

VT02N / VT01N Logistics Execution LE-TRA 2270199
TRA) Foundation Starter not strategic anymore within SAP S/4HANA.
PE01 / PE02 / PE04

/ PU01 / PY-XX, PY-XX-TL,
PC00_M99_PPM / PY-XX-OC, PY-
SAP Payroll SAP Payroll CP-SAP Payroll
PCP0 / MP004500 / CA, PY-LOC-XF, SAP Payroll Processing
Processing Processing Processing
H99CWTR0 / PY-US-FP-TP,
H99_DISPLAY_PAY PY-XX-DT
RESULT
Selected project PS-Selected project

Project System specific financial planning and
financial planning financial planning CP-SAP ERP
CJ8V PS-COS control functions including the Easy Cost Planning 2267182
and control and control Foundation Starter
(ECP) are not strategic within SAP S/4HANA.
functions functions, incl. ECP
The classical MRP lists are not strategic within SAP
CP-SAP ERP
SAPMM61R Classical MRP lists Classical MRP lists PP-MRP-BD S/4HANA but still available. SAP S/4HANA features 2268085
Foundation Starter
MRP live, an MRP run optimized for SAP HANA.
Compatibility Pack
Assessment (3/4)

LL01 / LB13 /
LB12 / LB11 /
Warehouse
LB10 / LB03 / CP-SAP ERP The Warehouse Management (LE-WM) is is not
Logistics Execution Management (LE- LE-WM 2270211
LB02 / RLLL0000 / Foundation Starter strategic anymore within SAP S/4HANA.
WM)
RLLL0100 /
RLLL01SE
Current progress tracking and project monitoring

function with PS are still available with SAP
PS-Progress S/4HANA but not considered as strategic any
COMPXPD / DEXP / Progress Tracking & CP-SAP ERP
Tracking & PS-PRG-TRC 2267190
EXPD Monitoring Dates Foundation Starter
Monitoring Dates longer. It is recommended not to continue to enable
progress tracking for PS objects and project
monitoring function.
Analytics based on Logistics Information System

SD Analytics based SD Analytics based
(LO-LIS) is not strategic anymore within SAP
RMCV0500 / on Logistics on Logistics CP-SAP ERP
SD-IS S/4HANA. The SAP S/4HANA Analytics approach is 2267348
RMCV0300 Information System Information System Foundation Starter
based on ODATA and Open CDS (Core Data Services)
(LO-LIS) (LO-LIS)
directly on top of the original database.
Compatibility Pack
Assessment (4/4)

Customers using BW with ECC as upstream application and considering
moving to SAP S/4HANA (on premise) - should seek information whether
BW extractors (i.e., data sources) coming from SAP ERP would still work,
and to be able to evaluate the potential impact on the BW environment when moving to SAP
S/4HANA.
When planning a conversion from SAP ERP / Suite to SAP S/4HANA, customers need to know which
of their BW extractors in use will still be supported in S/4HANA and what migration options are
available for discontinued BW extractors (CDS-views based extractors). S/4HANA brings new
design as defined in simplification list for a specific version, as a result, some of earlier data sources
are impacted (some becoming obsolete, some can work with restriction etc). The following slides
show the category and definition of this impact.
The next page graph shows AA MOTORS data sources and their impact as per SAP guidelines.
BW Extractor
Assessment (1/5)

BW Extractor Impact Category and Classification – as defined in
SAP Note 2500202.
45
40
35
30
25
DS not working - no alternative exists
20 DS working - no restrictions
DS working - with restrictions
15 DS not relevant
DS working - restrictions
10
DS not working - alternative exists
5 DS obsolete
BW Extractor
Assessment (2/5)

BW Extractor Impact Category and Classification - as defined in
SAP Note 2500202.
Classification Categories Description
DS working - no
Whitelisted DataSource is available in SAP S/4HANA and works without any restrictions compared to ERP.
restrictions.
DS working -
regeneration of
DataSource is working, but because of S/4HANA data model changes, it is recommended to check
Whitelisted extractor and check of
the upward dataflow.
BW content based on
this DS is needed.
DS working - DataSource is available with S/4 but works with noteworthy restrictions; e.g. not all fields are
Not Whitelisted
restrictions available.
DS not working -
Not Whitelisted DataSource is not working with S/4 but an alternative exists, such as a new extractor, CDS view.
alternative exists.
DS not working -
Not Whitelisted DataSource is not working with S/4 but equivalent available on roadmap for future release.
alternative planned.
Deprecated DS obsolete DataSource is obsolete - legacy extractors.
DS not working - no
Deprecated DataSource is not working with S/4 but no alternative exists.
alternative exists.
Generated Data DS working - no Because of the nature of the extractors, being generated in the system, we cannot whitelist those
Source restrictions. in general. Experience so far showed that they should be working without restrictions.
Not Relevant for BW
DS not relevant. Datasource is available in ROOSOURCE, however, not to be used for extraction by BW.
Extraction
BW Extractor
Assessment (3/5)

SAP Note details for different Line of Business and Industries
In case issues arise with extractors listed earlier, or missing extractors,

please do raise an incident on the application component of the respective extractor.
Item Area - Line of Business Note number for details

Asset Management 2299213 - Restrictions for BW-Extractors in S/4HANA in the Enterprise Asset Management domain (EAM)
Business Process Management 2796696 - Restrictions for BW extractors relevant for S/4HANA as part of SAP S/4HANA, on-premise edition 1709 and above
Customer Services 2533548 - Restrictions for BW-Extractors in S/4HANA in the CS (Customer Service) area
Enterprise Portfolio and Project
2496759 - Restrictions for BW extractors relevant for S/4HANA in the area of Enterprise Portfolio and Project Management
Management
Financials 2270133 - Restrictions for BW extractors relevant for S/4HANA Finance as part of SAP S/4HANA, on-premise edition 1511
Flexible Real Estate 2270550 - S4TWL - Real Estate Classic
2559556 - Restrictions for BW extractors in Financial Localizations relevant for S/4HANA Finance as part of SAP S/4HANA,
Globalization Services Finance
on-premise edition 1511
Incident Management and Risk
2267784 - S4TWL - Simplification in Incident Management and Risk Assessment
Assessment
Master Data 2498786 - Data Sources supported by Central Master Data in S/4HANA
Master Data 2576363 - Data Sources supported by Master Data Governance in S/4HANA
2504508 - Restrictions for BW Extractors relevant for S/4 HANA Procurement as part of SAP S/4HANA, on premise edition
Procurement
1709 and above
Produce 2499728 - Restrictions for BW extractors relevant for S/4HANA in the area of Production Planning and Detailed Scheduling
Produce 2499716 - Restrictions for BW extractors relevant for S/4HANA in the area of Production Planning and Control
Produce 2499589 - Restrictions for BW extractors relevant for S/4HANA in the area of Quality Management
Produce 2499310 - Restrictions for BW extractors relevant for S/4HANA in the area of Inventory Management
Sales and Distribution 2498211 - Restrictions for BW extractors relevant for S/4HANA Sales as part of SAP S/4HANA, on-premise edition 1709
Supply Chain - Extended Warehouse
2552797 List of BI Data Sources used in EWM
Management
BW Extractor Supply Chain - Extended Warehouse
2382662 List of BI Data Sources from SCM Basis used in EWM Context
Assessment (4/5) Management
Supply Chain - Transportation
All Data Sources working and whitelisted, no separate note exists
Management
Master data governance for Finance All Data Sources working and whitelisted, no separate note exists

SAP Note details for different Line of Business and Industries
In case issues arise with extractors listed earlier, or missing extractors,

please do raise an incident on the application component of the respective extractor.
Item Area - Industry Note number for details

Defense and Security 2544193 - Restrictions for BW extractors relevant for S/4HANA in the area of Defense & Security
Defense and Security 2273294 - S4TWL - BI content, Datasources and Extractors for DFPS
Financial Services 2543469 - "SAP for Banking": SAP extractors in connection with "SAP S/4HANA on-premise edition
Financial Services 2546102 - "SAP for Insurance": SAP extractors in connection with "SAP S/4HANA on-premise edition“
IS Utilities 2270505 - S4TWL - IS-U Stock, Transaction and Master Data Statistics (UIS, BW)
Public Sector Collection and
All Data Sources working and whitelisted, no separate note exists
Disbursement (PSCD)
Public Sector Management (PSM) 2556359 - Restrictions for BW extractors relevant for S/4HANA in the area of Public Sector Management
IS Retail 2543543 - Restrictions for BW extractors relevant for S/4HANA in the area of Retail
BW Extractor
Assessment (5/5)

Security Assessment – Authorization and Role Impact
Total Medium
Impact on Authorization High Complexity Low Complexity
Count Complexity
Total Unique Auth Roles in system 1698 27 54 1617
Unique authorization Roles impacted 1654 23 38 1593
Custom authorization object mapped to roles
Custom transactions mapped to roles 659
Definition of Complexity No of Objects
High 100 & Above
Medium 50 to 99
Low 1 to 49
Analysis:
Out of 1,698 authorization roles, 1,654 ( 97.41 % ) are impacted.
Assumption:
Authorization role impact assessment is based on comparing standard authorization
check defined in S/4HANA and Source system
Impacted roles are determined by comparing authority check of transactions defined
in S/4HANA and Source system
Roles with custom transaction and custom authorization objects are included in the
Security assessment report
Assessment Derived / Child authorization roles, SAP standard roles/profiles are excluded
Impact due to custom object and transaction is reported under
“…removal of authorization object…..” and “….replacement of transaction….” respectively
Unique Authorization Roles are role-count for roles whose modification for addition and removal
of authorization object check is summed and categorized as per complexity.

Testing
Considerations (1/2) SAP S/4HANA 2023 will impact all or some of the 628 Standard SAP Programs
and 469 Custom programs - which are being executed in production system,
so these should be part of testing phases/test scripts.
Standard vs Custom Program Testing Impact

120
Number of Impacted programs
100
80
60
40
20
0
Construc
MSA
tion Dealer Inventor Logistics Personn Transpor Vehicle Warehou
Asset Batch C4C Cross Financial Financial Human Function Materials Materials Plant Reportin Variant Warranty
Equipme Controlli Custome Business y Informat Master el Time Project Technica tation Manage se
Accounti Manage Integrati CRM Applicati EHS Accounti accounti resource alities Manage manage PPC Maintena g @ Rent Sales Configur Processi
nt ng r branch Manage Manage ion Data Manage Systems l Manage ment Manage
ng ment on on ng ng s for DBM ment ment nce a Car ation ng
Manage ment ment System ment ment System ment
8.0
ment
Standard Testing Impact 24 2 2 0 2 44 27 0 26 1 80 0 59 35 6 0 14 105 0 8 12 13 12 0 83 0 24 2 5 38 4
Custom Testing Impact 0 0 0 6 0 0 11 2 59 0 107 4 74 0 0 3 0 2 1 89 0 0 0 10 77 10 0 0 4 5 5
Standard Testing Impact Custom Testing Impact

Test Focus Analysis
(1/3) SAP S/4HANA 2023 will impact transactions as some of them will be redesigned
from simplification point of view – screen change, design
change, getting obsolete/replaced by new/modified transactions or Fiori Apps.
The S/4HANA System testing should be planned sufficiently well. Generally, following tests can be planned keeping in mind S/4HANA new
simplification changes.
1. The NEW FUNCTIONALITIES that are coming with Simplification Changes should be tested using functional testing, integration testing.
2. Existing configuration should be tested using Regression Testing.
The table below shows the business processes/functional areas which should be in focus for testing, as Simplification changes have
impacted these business processes and its associated transactions, where there are screen changes, design changes, transactions getting
obsolete/replaced by new/modified transactions or Fiori Apps.
Business Process/ Module Name HIGH Focus MEDIUM Focus LOW Focus Legend
FI-Asset Accounting 2
LOW Focus
FI-Asset Accounting-Settlement 1
LOW and
FI-GL-Information System 3 MEDIUM Focus
FI-General Ledger Accounting 1 1 MEDIUM Focus
FI-Localization 3
Financial Accounting 4
IS-A-Vehicle Management System 1
LE-Shipping 6

Test Focus Analysis
LE-Warehouse Management 10
LO-Business Partners 1
LO-Electronic Data Records 1
LO-Material Master 3 2
LO-Warranty Claim Processing 1
MM-External Services 1
LOW Focus
MM-Inventory Controlling 9
LOW and
MEDIUM Focus
MM-Inventory Management 7 9
MEDIUM Focus
MM-Invoice Verification 2
MM-Purchasing 19

Test Focus Analysis
PP-MRP 1
PP-Material Forecast 2
PP-Production Orders 1
PS-Progress Tracking 2
SD-Basic Functions 4
SD-Billing 1 2
LOW Focus
SD-Conditions 1
LOW and
SD-Material Maintenance 1 MEDIUM Focus
SD-Output Determination 1 MEDIUM Focus
SD-Sales 1 2
Grand Total 0 14 92

Transaction Code - Status
14
12
Count of T-Code
10
8
6
4
2
0
Available in Available in Available in Available in Obsolete Obsolete, Obsolete,
S/4HANA, but S/4HANA, but S/4HANA, but S/4HANA, but replaced by replaced by
Obsolete as replaced by replaced by replaced by Fiori Apps new
per SAP Note Fiori Apps Modernized new Transaction
Transaction Transaction
Status of Transactions
Standard Transaction Obsolescence impact :
14 T-codes in Finance area out of those being used currently are either obsolete or replaced with new
T-codes in S/4HANA
33 T-codes in Logistics area out of those being used currently are either obsolete or replaced with new
T-codes in S/4HANA
Re-training Additional training will be required if Fiori adoption is also included in the initial scope of the S/4HANA conversion.
Considerations
(1/2)
Note : These Obsolescence impact is based on ST03N data, as received from AA MOTORS production system

Re-training Considerations Table
Available in Available in
Available in Available in Obsolete, Obsolete,
S/4HANA, but S/4HANA,
S/4HANA, but S/4HANA, but replaced replaced by
Component replaced by but replaced Obsolete
Obsolete as replaced by by Fiori new
Modernized by new
per SAP Note Fiori Apps Apps Transaction
Transaction Transaction
Financial Accounting-Asset
3
Accounting
Financial Accounting-Cash
Management-Bank Account 4
Management
Financial Accounting-
Controlling-Profit Center 1
Planning
Financial Accounting-Cost
2 1
Elements
Financial Accounting-G/L
2 1
planning
IS-Aerospace and Defense-
1
MPN
Logistics-BP 9
Logistics-Materials
2
Management-Purchase
Logistics-Materials
8
Management-RFQ
Logistics-Project Systems 1
Logistics-Project Systems-
1
Control Functions
Re-training Logistics-Project Systems-
Progress Tracking
2 1
Considerations Material Management-
6
(2/2) Inventory Management
Project Systems-Project
1
Builder
Sales and Distribution-
1
Sales Activities
S/4HANA and Intelligent Enterprise (1/15)
Intelligent Technologies as an Integral Part of SAP S/4HANA. These technologies are able to allow businesses to dig deep into their
existing pools of data for analysis and business insight. Through the use of algorithms and automation, companies can complement
their existing manual business processes with automated and digital options.
Interaction with the system via voice or text (chat) is solved via the SAP
Conversational AI (CAI) component. The SAP CAI service runs on the SAP Business
Technology Platform and can be integrated into various systems, e.g., S/4HANA.
The execution of actions is handled by bots that can be developed using the SAP
intelligent RPA (iRPA) component. SAP iRPA is also based on the SAP Business
Technology Platform and can be integrated into both SAP and non-SAP systems.
The scope of delivery includes a variety of preconfigured scenarios (best practices)
for SAP S/4HANA. Software bots are very well suited for completing repetitive tasks,
e.g., when they open a customer order from the email attachment and pre-enter
a corresponding sales order in the system.
Fast reaction: The SAP S/4HANA Situation Handling notification center responds to
specific exceptional situations and informs predefined recipient groups.
One can use the component as part of SAP S/4HANA, i.e., no additional installation
is required for this. Situation Handling contains extensive setting options and
comes with preconfigured scenarios for various departments. Example: if a vendor
is unable to deliver all quantities in a PO, one can get notification and proposal for
other vendor who can fulfil rest of the quantities.
For business process optimization and predictive analytics, one can use the built-in
machine learning component. Here, too, SAP delivers preconfigured scenarios
for purchasing, finance, logistics and sales, among others, some of which are
included in the S/4HANA license. At this point, a distinction is made between two
implementation options. One part of the best practices is integrated into
The interconnection of business processes with things (e.g., with goods) and with people the core of S/4HANA. The other part is provided ‘side-by-side’ (on the SAP BTP)
is based on Internet of Things (IoT) technology. Most recently, subject to licensing and can be used across systems. Machine Learning can be
SAP S/4HANA has been delivering best-practice scenarios for goods tracking. used in a variety of ways, e.g., for the classification of unstructured data, as a decision
These enable internal sales staff to react in good time to problems during internal transport support tool with intelligent suggestions, or for making forecasts, such as a
or transport to the customer and, if necessary, trigger replacement deliveries. delivery date delay forecast.

iRPA
Using SAP Intelligent Robotic
Process Automation (RPA) 2.0, one
can automate the pre-configured
business processes. To enable the
automation within SAP S/4HANA
Cloud, SAP S/4HANA or SAP
S/4HANA Cloud, private edition, one
can browse for the Cloud Studio
template bots in Intelligent RPA
store to get the package.
SAP S/4HANA template bots for SAP

Intelligent Robotic Process
Automation, which are applicable for
AA MOTORS based on the business
process and usage data are seen in
next slide.

These are SAP S/4HANA template bots for SAP Intelligent Robotic Process Automation 2.0, and these are suggested based on
AA MOTORS Production Usage Data
BOT NAME Attended Unattended Transaction/Program Transaction Description

Automatic Creation of Sales Orders from Excel (4G5) ** Y Y VA01 Create Sales Order
Automatic Creation of Sales Orders from Excel (4G5) ** Y Y VA02 Change Sales Order
Automatic Creation of Sales Orders from Excel (4G5) ** Y Y VA03 Display Sales Order
Automatic Creation of Sales Orders from Excel (4G5) ** Y Y VA05 List of Sales Orders
Automatic Creation of Sales Orders from Excel (4G5) ** Y Y VA05N List of Sales Orders
Mass Upload of Bank Statement Files (4X2) Y FEBAN Bank statement postprocessing
Mass Upload of Bank Statement Files (4X2) Y FF_6 Display Electronic Bank Statement
Mass Upload of Bank Statement Files (4X2) Y SAPMF40K Manual Bank Statement: Central Module Pool
FAGL_ACCOUNT_BAL
Automated Upload of General Ledger Entries (48I) Y G/L Account Balance Display
ANCE
FAGL_ACCOUNT_ITE
Automated Upload of General Ledger Entries (48I) Y G/L Account Line Item Display
MS_GL
Automated Upload of General Ledger Entries (48I) Y FS00 G/L acct master record maintenance
Automated Upload of General Ledger Entries (48I) Y MF01ASBU G/L Account Changes (Company Code)
Automated Upload of General Ledger Entries (48I) Y RFITEMGL G/L Account Line Item Display
SAPGL_ACCOUNT_MA
Automated Upload of General Ledger Entries (48I) Y G/L Account Master Record: Start of Transactions
STER_START
Mass Creation of Purchase Orders(6VW) Y Y ME21N Create Purchase Order
** Most Popular Automation Packages

Unattended - BOTs run in the background. One can see the results later and determine something needs to be rolled back or not. It is a no-brainer.
Attended – One can see moving them actively from screen to screen. One can interrupt if he wants to enter some input


Mass Creation of Purchase Orders(6VW) Y Y ME22 Change Purchase Order
Mass Creation of Purchase Orders(6VW) Y Y ME22N Change Purchase Order
Mass Creation of Purchase Orders(6VW) Y Y ME23N Display Purchase Order
Mass Update of G/L Journal Entry Details Without Impacting
Y Y FB50 G/L Acct Pstg: Single Screen Trans.
Financial Postings(6RT)
Y Y FB03 Display Document
Y Y FB02 Change Document
Y Y F-51 Post with Clearing
Y Y F-02 Enter G/L Account Posting
Create Purchase Requisitions from Excel (48M) ** Y Y ME57 Assign and Process Requisitions
Create Purchase Requisitions from Excel (48M) ** Y Y ME5A Purchase Requisitions: List Display
Create Purchase Requisitions from Excel (48M) ** Y Y RM06BA00 List Display of Purchase Requisitions
Create Purchase Requisitions from Excel (48M) ** Y Y RM06BF00 Collective Release of Purchase Requisitions
Create Purchase Requisitions from Excel (48M) ** Y Y RM06BZ00 Assign Purchase Requisitions
Outbound Delivery - Post Goods Issue for Non-Warehouse
Y Y VL01N Create Outbound Dlv. with Order Ref.
Management (4HV)
Y Y VL02N Change Outbound Delivery
Management (4HV)
** Most Popular Automation Packages



Y Y VL06O Outbound Delivery Monitor
Management (4HV)
Outbound Delivery - Post Goods Issue for Non-Warehouse WS_MONITOR_OUTB
Y Y List of Outbound Deliveries
Management (4HV) _DEL_FREE
Post Goods Movement (4FP) Y Y MIGO Goods Movement
Creation of Inbound Delivery (4QK) Y Y VL06I Inbound Delivery Monitor
Creation of Inbound Delivery (4QK) Y Y VL06IF Selection inbound deliveries
Creation of Inbound Delivery (4QK) Y Y VL31N Create Inbound Delivery
Creation of Inbound Delivery (4QK) Y Y VL32N Change Inbound Delivery
Creation of Inbound Delivery (4QK) Y Y VL33N Display Inbound Delivery
WS_MONITOR_INB_D
Creation of Inbound Delivery (4QK) Y Y Inbound Deliveries for Putaway
EL_PICK

Definition
Automation
• to jump from point A to B in a process and linking
data with ML makes process intelligent.
Situation Handling
• getting the notification about current
state and point to the right direction about
how to react and resolve.
Machine learning is used in Predicting the future outcomes by utilizing the past data and help the business users in decision
making. It provides Real-time, predictive insights so users can make faster and better decisions and adjustments. While RPA is
used for automating the repetitive tasks, here the focus is to identify recurring tasks and automate them using RPA bots. It
accelerates the digital transformation of business processes by automatically replicating tedious actions that have no added
value. On the other hand, like ML, Situation Handling also help in decision making but it is based on Decision flow charts, that are
created by the users to take decisions for different kind of situations. Here future outcomes are not predicted to make decisions.

What is ISLM?
Intelligent Scenario Lifecycle Management (ISLM) is a standardized framework that enables end-to-end lifecycle management
operations and consumption of Machine Learning scenarios in SAP S/4HANA. One can consider ISLM as a self-service tool that
allows to handle various operation requirements of machine learning scenarios. One can train an intelligent scenario and use the
trained model to get an accurate inference result.
It is delivered with SAP S/4HANA. It is available since SAP S/4HANA 2020 FPS0 for on-premise and with SAP S/4HANA cloud 2011.
It is part of S/4HANA License.
It is shipped with SAP S/4HANA as part of SAP BASIS layer. The ISLM framework is integrated into the ABAP layer (SAP Basis) so that
the intelligent scenarios from above layers in SAP S/4HANA stack can utilize the framework completely
ISLM Provides:
- Standardized framework to connect machine learning artefact to consuming business application and manage the lifecycle of
these scenarios
- Support for both SAP S/4HANA on-premise and SAP S/4HANA cloud
- Option to create own intelligent scenarios and manage the model training, deployment, and activation process.
- The purpose of PAi aka ISLM is to provide a common interface for the consumption of the ML models independent of the
underlying predictive engine to provide predictions and results. This modeling and administrative tool is hugely helpful in managing
the complete lifecycle of the model creation, model training, model adoption and model application into the SAP S/4HANA business
processes.

ISLM Provides:
- Harmonized cockpit to manage scenarios based on:
• SAP HANA ML (APL (Automated Predicted Library) and PAL (Predictive Analysis Library)) embedded in the SAP. SAP S/4HANA runs
in the same stack as its machine learning provider SAP HANA machine learning with the analytics libraries SAP HANA Automated
Predictive Library (APL) or SAP HANA Predictive Analysis Library (PAL). APL exposes the data mining capabilities of an Automated
Analytics engine for developing predictive modelling processes for business analysts. PAL offers advanced analytics algorithms for
data scientists. This can be used to solve use cases of forecasting, trending, and so on.
• Side-by-side machine learning scenarios where the machine learning artefact is running in the cloud like SAP BTP. For example,
SAP Data Intelligence, SAP AI Core, and SAP Business Technology Platform (SAP BTP) based service, such as Intelligent
Intercompany Reconciliation, Document Information Extraction, Data Attribute Recommendation, and Business Entity Recognition.
Remote machine learning services can be used for high-end use cases, such as image recognition, sentimental analysis, deep
learning for natural language processing that is based on neural networks.

ISLM offers two SAP Fiori Apps to:

• Display the details of the intelligent scenarios.
• Create intelligent scenario for specific business need.
• Train the scenario to generate a trained machine learning model or artifact for the business consumption.
• Deploy the trained machine learning models for inference consumption. (This functionality applies to Side-by-Side scenarios only.)
• Activaten the trained machine learning model for which one wants to get the inference results in the productive environment.
• Inference Results - Get the access points for inference calls to get the predictions based on the trained models. One can get the
predictions that are created from the trained models. Also, batch inference requests can be triggered from consuming Business
Applications.
Scenarios delivered via ISLM
The purpose of ISLM (Predictive Analytics Integrator – Pai 2.0) is to provide a common interface for the consumption of the ML
models independent of the underlying predictive engine to provide predictions and results.
The simplified ISLM interface provides the feature of training the ML model (underlying algorithm) with the data that’s already
available in the customer system and publishing the ML model for productive use within SAP Fiori applications.
The models get better with more data accumulated over time. The data is available to the model for training by mapping the CDS
views and other data structures.
N. B. While PAi was focused on embedding HANA’s APL library directly without coding, the HANA PAL algorithms could be embedded using generic
coding methodology into SAP S4HANA. Now with ISLM technology, one can embed HANA PAL and HANA APL without any coding into the SAP
S/4HANA business applications.
Since the ISLM framework is part of the ABAP platform, the system landscape design is similar to the ABAP platform deployments.
Usage of HANA as a database is a must for the embedded use cases since it is dependent on the HANA libraries.
The machine learning scenarios can be developed in the following ways – talking in terms of the architecture drivers:
• Embedded scenario can be developed in the SAP Analytics Cloud with HANA APL as an extension to SAP S/4HANA.
• Embedded scenario can be developed in HANA Embedded Machine Learning Interface (leveraging HANA PAL) and imported into ISLM in SAP
S/4HANA.
• Embedded scenario can be developed directly in ISLM using capabilities of SAP HANA libraries.
• Side-by-side scenario can be developed via SAP DI on SAP BTP and register to delegate the ABAP class in ISLM.
• Side-by-side scenario can be developed via SAP AI business services using ISLM (in beta) on SAP BTP.
Any of the machine learning scenarios developed irrespective of the type will be operated in ISLM.
The ISLM framework is delivered with 2 Fiori applications namely, the Intelligent Scenarios and the Intelligent Scenario Management.
An intelligent scenario is an ABAP representation of machine learning business-specific use case. Example : Predict cost for a project, forecast
when a buyer is likely to negotiate a new procurement contract.
These apps will be accessible via the Fiori Launchpad based om ‘Intelligent Scenarios’ business catalog.
Intelligent Scenarios:
This is a typical registration and a creation app for the developers to register the intelligent scenarios in the ISLM framework with the basic details
and an ABAP class representing the intelligent scenario. This app will be accessible to the customers to create a custom development of intelligent
scenario. Additionally, for the embedded approach, the framework generates a class internally during this registration process. In the side-by-side
use case (machine learning logic class), the developers need to create their own class. Eventually ISLM will offer an ABAP development tool in
native integration with SAP GUI to create intelligent scenarios.
Intelligent Scenario Management:
Using this app, the business administrators (domain experts) can perform the operations like prerequisite check, training, deployment, activation
and monitoring of the intelligent scenario for a specific business domain. This app is built with more focus on non-ML expert expectations to operate
intelligent scenarios.
There is one more app - 'Monitor Planned Task Jobs'- one can schedule training for intelligent scenarios. Also, monitor the scheduled runs
that are created via ISLM in the Monitor Planned Task Jobs tile. Also, one can trigger batch inference requests by consuming Business Applications.
Prerequisite Checks
Prerequisite checks enable one to check whether the SAP delivered intelligent scenario meets the readiness
requirement to train and consume ML scenarios. These prerequisite checks can be for checking whether sufficient data
quality and quantity is available for training ML algorithms, and also to ensure business specific processes are configured
correctly. Before one starts the ML operations, one can execute the checks for intelligent scenario in SAP S/4HANA
system using ‘Intelligent Scenario Management’ app. Once executed, the prerequisite check result includes the overall
run status, number of successful and failed check, and message associated with each check. Depending on the check
result, one can continue training and consuming ML scenarios.

Implementing ML functionality in S/4HANA using Scope ID - 1 / 2

The best practices package provides a step-by-step guide on the different aspects of machine learning with SAP S/4HANA, explains
the different approaches of doing machine learning with SAP S/4HANA and finally provides access to all the different use cases along
with the scope items corresponding to them. Through SAP's journey into the Intelligent enterprise, there has been a lot of emphasis
and efforts put into developing predictive intelligence into the LoBs such as finance and procurement with use cases embedding
machine learning and predictive analytics. Most of the machine learning and predictive analytics functionality built with SAP
S/4HANA is assigned a scope item.The following details show the Scope ID applicable for (AA MOTORS) – based on business process
/ usage data
Line Of Business Business Area Count of Scope Item ID Relevant Fiori ID

Finance Accounting and Financial Close 92 F0717, F0718, F2547, F1616 and more
Finance Advanced Accounting and Financial Close 1
Finance Cost Management and Profitability Analysis 37 F2918, F3779, F1711, F2680 and more
Finance Financial Operations 49 F1564, F0770, F1927, F1520 and more
Finance Treasury Management 44 F3001, F3002, F3185, F1366 and more
Manufacturing Manufacturing Operations 9 F2035, F2101, F2335, F2336 and more
Manufacturing Manufacturing Options 11 F0859, F3095, F1062, F2101 and more
Manufacturing Production Planning 15 F2336, F2335, F1240, F3445 and more
F2872, F0859, F1060A, F1339 and
R&D/Engineering Product Engineering 7
more
Sales Order and Contract Management 204 F3681, F2228, F1519, F1519 and more
Service Service Master Data & Agreement Management 2

Implementing ML functionality in S/4HANA using Scope ID - 2 / 2

The best practices package provides a step-by-step guide on the different aspects of machine learning with SAP S/4HANA, explains
the different approaches of doing machine learning with SAP S/4HANA and finally provides access to all the different use cases along
with the scope items corresponding to them. Through SAP's journey into the Intelligent enterprise, there has been a lot of emphasis
and efforts put into developing predictive intelligence into the LoBs such as finance and procurement with use cases embedding
machine learning and predictive analytics. Most of the machine learning and predictive analytics functionality built with SAP
S/4HANA is assigned a scope item.The following details show the Scope ID applicable for (AA MOTORS) – based on business process
/ usage data
Line Of Business Business Area Count of Scope Item ID Relevant Fiori ID

Solutions for Specific Industries Automotive 1
Sourcing and Procurement Central Procurement 24 F1639, F3314, F3316, F3268 and more
Sourcing and Procurement Invoice Management 107 F1306, F1639, F1995, F1306 and more
Sourcing and Procurement Operational Procurement 135 F2424, F2594, F2705, F1061 and more
F3290, F2947, F1600A, F1859 and
Sourcing and Procurement Sourcing and Contract Management 27
more
Sourcing and Procurement Supplier Management 14 F2551, F2194, F2019, F1649 and more
Supply Chain Advanced Warehousing 1 F1873
F2872, F3264, F0842A, F0842A and
Supply Chain Inventory 88
more
F1873, F0247A, F0251, F2336 and
Supply Chain Warehousing 19
more
Grand Total 887

Implementing ML functionality in S/4HANA using Scope ID

1. Scope item and flow - Check high-level overview and important information, in each of these Scope ID. That information can then
be used to predict full consumption of factors such as a historical data, other available influencing parameters, and so on.
2. Roles – Check the scope items and determine the roles should be assigned to be able to work with the predictive model/KPI.
3. Business Data - A few required scope items may need to be run to enable corresponding data to be available. The key step here is
the identification of any required scope items to be implemented and hence the data created accordingly.
4. Model training - Train or re-train the model and activation of the required model version is to be done.
5. Access the app - Finally logon to the Fiori Launch Pad as the “Role” and access the app suggested in the Scope Item and follow the
steps as specified in the scope item to run the scenario and see the predicted consumption results.

ISLM Framework
Business user or the end
ABAP developer
user can leverage this
builds the UI code
functionality for performing
that embeds into
the needed business actions
the SAP S/4HANA
business app
leveraging the
Fiori technology Business administrator or
the analytics specialist can
enable the machine learning
Intelligent scenario owner scenario by training,
registers the scenario and deploying and activating the
publishes into the SAP scenario
S/4HANA
Data Science Developer

builds the machine learning
scenario with the various
data science tools
depending on the approach
chosen. This is for example
– to forecast when a buyer is
likely to negotiate a new
procurement contract

S/4HANA and Intelligent Enterprise - JOULE(1/2)
Joule
Joule is not just another AI tool; it's a transformative natural-language, generative AI copilot from SAP that promises to revolutionize the way
businesses run. an automatic co-pilot and digital assistant. This human-to-machine interface can be used in many ways, including conversational,
navigational, and information gathering use cases. It's based on SAP proprietary data, process flows, and applications. It can help users gather new
data about functionalities they want to onboard with or guide them to execute tasks like master data extensions or new sales orders.
AI Copilot is a tool that uses artificial intelligence to understand what one needs and provides suggestions or support, making work easier and more
efficient. Technically, AI Copilot is a conversational interface that uses large language models (LLMs) to support users in various tasks and decision-
making processes.
Joule will be embedded into SAP applications from HR to finance, supply chain, procurement, and customer experience, as well as into SAP
Business Technology Platform. It will be pretrained with SAP business data and business processes.
Users may simply ask a question or frame a problem in plain language and receive intelligent answers drawn from the wealth of business data
across the SAP portfolio and third-party sources, retaining context. It often finds use in interfaces where hands-free or verbal communication is
beneficial.
Joule provides an Out-of-the-box integration with SAP backend systems. It is compliant with AI ethics, GDPR, and privacy controls while
maintaining SOC-II compliance. Joule gets automatically updated whenever the capabilities are added or changed.
Imagine, for example, a manufacturer asking Joule for help understanding sales performance better. Joule can identify underperforming regions,
link to other data sets that reveal a supply chain issue, and automatically connect to the supply chain system to offer potential fixes for the
manufacturer’s review. Or in HR it may help write unbiased job descriptions and generate relevant interview questions.
Joule and SAP Conversational AI
SAP Conversational AI was a platform for custom chatbot creation, and customers had to build their own content. SAP Conversational AI is already
sunset. Starting January 2023, SAP Conversational AI, has been set to maintenance mode. There is no direct successor of SAP Conversational AI.
Joule is not a replacement or successor for SAP Conversational AI. Joule is directly embedded into SAP applications, providing value right out of the
box.

S/4HANA and Intelligent Enterprise - JOULE(2/2)
Starting from the 2H 2023 release, Joule is available in SAP

SuccessFactors .
Users of SAP SuccessFactors now can perform HR tasks in SAP's

new generative AI assistant Joule. For example, employees will
be able to get answers to questions and complete HR-related
tasks, such as approving or rejecting time-off requests; changing
names, locations or personal pronouns; and more.
More functionalities will be available in early 2024, such as

clocking in and out, viewing pay statements and writing unbiased
job descriptions.
Joule is integrated with SAP Start as well. It will be available with

SAP S/4HANA Cloud, public edition early 2024. Afterwards it will
be available in SAP Customer Experience and SAP Ariba solutions
along with SAP BTP as well.
Joule facilitates conversational interactions, enabling seamless communication between humans and computers. It supports three primary conversational
patterns:
1. Navigational: Helping users find the functionality they need within SAP systems.
2. Transactional: Assisting users in efficiently completing tasks.

3. Informational: Retrieving relevant information from existing documents.
Joule facilitates conversational interactions, enabling seamless communication between humans and computers. It supports three primary conversational
patterns:
IBM and AA MOTORS Confidential 130
Fiori is the next generation UX interface from SAP which modernizes and
simplifies the user experience
Based on Production transactional data, we determined that approximately, 955 Fiori applications can
be used to manage business process executions.
Out of these High recommended apps, around 294 applications have a direct match to the t-codes used
by end-users are shown in the table.
Fiori Application
500
450
400
350
300
250
200
150
100
50
0
Fact sheet Analytical Transactional
High
28 43 223
Medium 5 142 448
Low 5 17 44
Based on the current usage data (ST03N) and total processing time of transactions/programs in AA MOTORS
production system, the above chart displays all FIORI apps by their category that can be used for S/4HANA target
system post system upgrade.
Fiori Applications
These SAP Fiori apps are relevant as they can be used for transactions from the application area that the SAP Fiori
(1/2) app belongs to. The level of the rating HIGH/MEDIUM/LOW depends on the proximity of the transaction to the application
area.

Summary of most applicable (High) Fiori Applications
Business Process Analytical Factsheet Transactional Grand Total

Application Development and
0 0 3 3
Integration
Asset Management 2 3 4 9
Database and Data Management 0 0 5 5
Finance 12 3 50 65
Human resources 0 0 6 6
Manufacturing 0 0 15 15
Procurement 1 0 7 8
R&D and Product Management 2 3 3 8
Retail 0 0 12 12
Sales 4 7 36 47
Service 0 2 9 11
Sourcing and Procurement 11 5 44 60
Supply Chain 11 5 27 43
Technical 0 0 2 2
Total 43 28 223 294
Fiori Applications
(2/2)

The top 20 relevant Fiori applications for implementation based on usage of transaction.
Fiori ID Leading Line of Business Application Name Application Type Transaction
MB52, MMBE, MB1B, MB5T,
F1595 Sourcing and Procurement Stock - Multiple Materials Analytical MB58, MB53, MIGO, MBBS,
MB5B
F2769 Supply Chain Overview Inventory Management Analytical MB52, MMBE, MIGO, MB51
Database and Data
XD03, VD03, BP, XD01,
F3163 Management, Application Manage Business Partner Master Data Transactional
XD02, FD03
Development and Integration
XD03, VD03, BP, XD01,
F0850A Supply Chain Manage Customer Master Data Transactional
XD02, FD03
F2347 Supply Chain Overdue Materials - Goods Receipt Blocked Stock Analytical MMBE, MIGO
ME23N, ME22N, ME22,
F0842A Sourcing and Procurement Manage Purchase Orders (Version 2) Transactional
ME21N, ME9F
ME23N, ME22N, MD04,
F1700 Manufacturing Create Optimal Orders for Shipment Transactional
ME21N
F3292 Sourcing and Procurement Manage Purchase Orders Centrally Transactional ME23N, ME21N
F3486 Sourcing and Procurement Create Purchase Order Centrally Transactional ME23N, ME21N
F6635 Sourcing and Procurement Manage Workflows for Central Supplier Confirmation Transactional ME23N, ME21N
F1076 Supply Chain Stock - Single Material Analytical MB52, MMBE, MB5B
VA02, VA22, VA41, VA21,
F2459 Sales Schedule Sales Document Output Transactional
VA01, VA42
F0586 Retail Adjust Stock Transactional MB03, MMBE
F0431 Retail Look Up Retail Products Transactional MMBE
VA02, VA01, FB70, VA05,
F1988 Sales Manage Debit Memo Requests Transactional
VA03
F3893 Sales Manage Sales Orders - Version 2 Transactional VA02, VA01, VA05, VA03
Top 20 Fiori F2305 Service, Sales Manage Sales Orders without Charge Transactional VA02, VA01, VA05, VA03
Applications ID F1873 Service, Sales Manage Sales Orders Transactional VA02, VA01, VA05, VA03
F1708 Service Manage Customer Returns Transactional VA02, VA01, VA03
Manage Sales Documents with Customer-Expected VA02, VA22, VA42, VA43,
F2713 Sales Transactional
Pric VA23, VA03

SAP S/4HANA Embedded Analytics – CDS View (1/2)
SAP S/4HANA Embedded Analytics brings the two operational and analytical world together by providing users a convenient means to
run their operational analytics in real-time in their source SAP S/4HANA system.
For example, it is possible now to check purchasing request along with supplier KPI and then assign a supplier.
Also, it is possible for other SAP Analytics Products to access SAP S/4HANA Embedded Analytics data, and also it brings standard and
custom SAP Fiori app for real-time analytics.
It is based on Virtual Data Model
(VDM, with HANA DB tables
lying beneath), predefined View,
and is implemented as ABAP
Core Data Services (CDS) Views.
CDS View can be used to design
KPI, create multidimensional
report. Also, CDS view can be
consumed by transient
analytical queries, which can be
integrated with other SAP
Analytics Products – such as
SAP Lumira, SAC (SAP Analytics
Cloud).
Although SAP provides
considerable content out-of-
the-box, one can easily extend
underlying ‘CDS views’ to meet
client’s custom
reporting/analytics needs.

SAP S/4HANA Embedded Analytics – CDS View (2/2)
The VDM (virtual data model) forms the basis for data access in SAP S/4HANA in, for example, analytical applications and APIs. The
VDM of SAP S/4HANA Cloud and SAP S/4HANA is represented by CDS views.
The following table shows a list of CDS view which are specific for AA MOTORS’s business processes. Based on usage data ST03N and
application area/component, count of matching CDS views are shown here – which are of type – New, Changes, Deprecated, Deleted
as of SAP S/4HANA 2023 release. Based on requirement, the project team can use these CDS views for many different scenarios like -
✓ Creating Fiori Apps.
✓ Analyzing data.
✓ Create own custom CDS views – reusing released CDS views.
✓ Transfer data from an SAP source system, such as SAP S/4HANA, to the target system SAP BW/4HANA.
✓ Define a data structure and can't be used for other purposes, such as retrieving data.
Line of Business Changed Deleted Deprecated New Grand Total
Asset Management 2 16 18
Cross Applications 27 32 1 60
Finance 36 6 42
Manufacturing 11 11
Sales 2 5 22 29
Service 19 19
Sourcing and Procurement 1 1
Supply Chain 12 4 42 58
Grand Total 16 27 78 117 238
Package Wise No of Enhancements present within T-Codes of that package
In System Conversion or Upgrade scenario, it is better to get to know the enhancements done around critical
transactions.
For this, the list of transaction codes which has enhancements using the package of the respective transaction
codes in AA MOTORS system was found.
This will help to manage/handle any custom field that probably was added in any transaction/SAP screen.
In ECC, for adding a field in a screen, firstly it has to be added in the source table using append structure with the
transaction SE11, and secondary, they also have to be added in the Dynpro screen with the transaction SE51, and
finally, the ABAP logics have to be added to send/receive the values of the added fields between screen and the
tables using User/Customer Exit (Transaction SMOD/CMOD) or BADI (Transaction SE18/19).
Key User Extensibility tools are the tools to create or enhance the objects without custom coding, and Custom
Fields and Logic (CFL) is one of the main tools in Key User Extensibility Tools. Custom Field is a menu in this tool.
In S/4HANA context, S/4HANA Extensibility means creation and enhancement of the apps and objects (note: it
does not mean only enhancement). It consists of In-App Extensibility and Side-by-Side Extensibility. In-App
Extensibility means creation of the object IN S/4HANA, and Side-by-Side Extensibility means development or
enhancement OUTSIDE OF S/4HANA, mainly with SAP Cloud Platform. In-App Extensibility consists of Key User
Extensibility and Classic Extensibility. Classic Extensibility means traditional custom development like custom
program and Function Module. In S/4HANA, the way to create custom object with tools are provided in addition to
classical ways, which is called Key User Extensibility tools. In S/4HANA Cloud (SaaS), Classic Extensibility is not
available and Key User Extensibility is the only way for In-App Extensibility.
Package Name Count of Implementation

MB 15
ME 56
Enhancements Grand Total 71
Around
Transaction Code

S/4HANA Extensibility Options
The clean core is an

extension methodology
concept with the basic goal
i.e. Extensions should not
break an upgrade and
upgrades should not break
an extension.
Follow the rules:
1. Fit-to-Standard: Leverage
SAP standard processes when
possible.
2. Apply a zero-modification
policy from the project’s first
day.
3. Leverage the full potential

of new extension options (In-
App, Developer, or Side-by-
Side ) which fit one’s needs
best. Use allow-listed and
released APIs.
4. Eliminate enhancements
that are redundant to standard
code and functionality, as well
as “clones” of standard code.
Enhancements
Around
Transaction Code

Next Steps and
Follow up Actions

Appendix
Appendix -
For Reference

Based on features used in the AA MOTORS SAP system, below are some
sample business processes that will change with the move to SAP 2023.
Custom Objects
SAP Note Title SAP Note Number
Instances Impacted
FAQ: END OF SUPPORT OF ME21, ME51, BAPI_PO_CREATE AND ARCHIVING
1803189 7
REPORTS ETC.
MB transactions: Limited maintenance/decommissioning 1804812 2
S4TC EA-GLTRADE - DB Field Changes within Global Trade Management 2198031 6
S4TC EA-GLTRADE - Checks for Condition Contract DB Key Field Changes 2198035 12
S/4 HANA: Data Model Changes in SD 2198647 64
Material Inventory Managment: change of data model in S/4HANA 2206980 1
Sales support not available 2214585 8
SAP S/4 HANA Simplification Item: Occupational Health (EHS-HEA) 2217205 4
SAP S/4 HANA SIMPLIFICATION ITEM: INDUSTRIAL HYGIENE AND SAFETY

2217206 4
(EHS-IHS) AND SAP ENVIRONMENTAL COMPLIANCE (EC) INTERFACES
S/4 HANA: Data Model Changes in Pricing and Condition Technique 2220005 31
Simplification
Code Analysis-
S/4HANA 2023
(1/7)

Based on features used in the AA MOTORS SAP system, below are
some sample business processes that will change with the move to SAP 2023.
Custom Objects
Instances Impacted
S/4 HANA - Foreign Trade in SD/MM 2223144 55
S/4HANA: SD - Advanced Order Processing and Billing for Contractors to the

2223800 87
public sector
Deprecation / Restricted Availability of IS-Beverage functionalities in S/4HANA 2224144 1102
SAP S/4HANA Simplification Item: PLM-cFolders-Integration 2224778 14
S/4HANA: SD - SAP INTERNET SALES, SAP E-COMMERCE, SAP WEB CHANNEL

2225107 20
AND SAP WEB CHANNEL EXPERIENCE MANAGEMENT
S/4 HANA SD-Revenue Recognition 2225170 8
SAP S/4 HANA Simplification Item: Public Sector specific fields in Business
2226131 781
Partner
S/4 HANA: Deprecation of SD Rebate Processing 2226380 1
S/4 HANA: CREDIT MANAGEMENT CHANGES IN FI 2227014 1
SAP S/4HANA Simplification Item: Logistics_PP-MRP - Subcontracting 2227532 1
Simplification
Code Analysis-
S/4HANA 2023
(2/7)

Custom Objects
Instances Impacted
SAP S/4HANA Simplification: DIMP Automotive - Regular route shipments 2227568 133
SAP S/4HANA Simplification Item: Logistics_PP-MRP - Storage Location MRP 2227579 136
SAP S/4HANA - Simplification Item SI9: SD_ODP - Operational Data

2228056 19
Provisioning
SAP S/4HANA Simplification: DIMP Automotive - Supplier Workplace 2228218 210
SAP S/4HANA Simplification: DIMP Automotive -

2228241 353
Long Material Number
SAP S/4HANA Simplification: DIMP Automotive - Material versions 2228242 1
SAP S/4HANA Simplification: DIMP Automotive - Dealer portal (DIWI and BSP-
2228244 1
based)
S4TWL - Business Partner Approach 2265093 17
S4TWL - MRP fields in Material/Article Master 2267246 344
S4TWL - MRP Live on SAP HANA - MD01N 2268085 61
Simplification
Code Analysis-
S/4HANA 2023
(3/7)

Custom Objects
Instances Impacted
S4TWL - TRANSPORTATION (LE-TRA) 2270199 31
SAP S/4 HANA custom code adaption - removal of orphaned objects 2296016 4047
S4TWL - Custom Fields 2320132 14
S4TWL - Value and Quota Scales 2340247 3
The Home Building Solution(HBS): System Conversion from software

2343388 1868
component ECC-DIMP to SAP S/4HANA
S4TWL- Retail Season Conversion (SAP ERP to SAP S/4HANA 1610) 2365665 371
S4TWL - Retail Method of Accounting 2368736 24
S4TWL - Fresh Item Procurement 2368747 27
S4TWL - Seasonal Procurement 2368913 588
S4TWL - Retail Information System (RIS) and Category Management Workflow 2370131 2
Simplification
Code Analysis-
S/4HANA 2023
(4/7)

Custom Objects
Instances Impacted
S4TWL - Retail Rapid Replenishment 2371539 1
S4TWL - Retail Bonus Buy (transaction VBK*) 2371559 4
S4TWL - Retail Order Optimizing: Load Build, Investment Buy 2371602 2
S4TWL - Retail Sales Forecasting 2371616 3
S4TWL - Retail Additionals 2371631 7
Material classification: Change in data model in SAP S/4HANA 1610 2378796 1
SAP S/4HANA Simplification: AECMA SPEC2000M Military Solution 2382203 1419
SAP S/4HANA Simplification : Software License Management 2383423 2197
SAP S/4HANA Simplification : Distributor Reseller Management 2383997 611
S4TWL - Flexible Material Prices (FMP) in SAP S/4HANA 2414624 34
Simplification
Code Analysis-
S/4HANA 2023
(5/7)

Custom Objects
Instances Impacted
MATERIAL NUMBER FIELD LENGTH EXTENSION: CODE ADAPTIONS FOR
2438006 168
COMPATIBLY ENHANCED LOCAL FUNCTION MODULES
Material Number Field Length Extension: Code Adaptions for usages of RFC
2438110 108
enabled function modules
Material Number Field Length Extension: Code Adaptions for usages of released
2438131 176
RFCs and BAPIs
S4TWL - Actual labor and costing 2445654 8
S/4HANA: DATA MODEL CHANGES IN IS-M 2469385 337
S4TWL - Segment Field Length Extension 2522971 1
Amount Field Length Extension: Code Adaptations for Usages of Adjusted

2628704 53
Interfaces
Amount Field Length Extension: Code Adaptations for Usages of RFC Enabled
2628706 9
Function Modules
SAP S/4HANA: SAP PATIENT MANAGEMENT (IS-H): RESTRICTION NOTE 2689873 29
S/4HANA 1809+ CONVERSION/UPGRADE GUIDELINES FOR ADVANCED

2716224 10
TRACK & TRACE
Simplification
Code Analysis-
S/4HANA 2023
(6/7)

Custom Objects
Instances Impacted
S4TWL - SD BILLING DOCUMENT DRAFT 2768887 1
PACKAGES DRSCENARIOS, POR4, PORX AND PORX_COMPATIBILITY ARE

2862992 7
MISSING
SIMPLIFICATION ITEM S4TWL - BUSINESS USER INTEGRATION OF BUSINESS
2900607 8
PARTNERS WITH USER NAME AND PERSONNEL NUMBER
S4TWL - Remote Logistics Management 3046934 824
S4TWL - Shipment Cost Processing 3051698 6
Central Note: SAP S/4HANA - Multiple Address Handling in SD Documents

3067314 1017
Using SAP
S4TWL - JIT Inbound 3159740 30
SAP S/4HANA Simplification Item SI_PP14: Logistics_PP-MRP - Forecast

3211383 4
Based Plann
S4TWL – HR Employee Interaction Center 3224334 2
S4TWL – Parts of Time Management 3224341 11
Simplification
Code Analysis-
S/4HANA 2023
(7/7)

Your opinion matters a lot…
FeedBack - We would really value feedback on your experience of the

HIA and the quality of the output, a short(<2 minute) questionnaire is
available online.
https://survey.vovici.com/se/05A1DD043DC08C49

Kinder

Uploaded by

Copyright:

Available Formats

Kinder

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Kinder

Uploaded by

Copyright:

Available Formats

IBM Consulting

SAP S/4HANA Impact Assessment

Assessment Scope Security Assessment

Basis Assessment and Testing Consideration

Functional Assessment Re-training Consideration

BW Assessment Next Steps and Follow

Functional Assessment Technical Assessment Key Areas of Impact

• Cash and Liquidity Management

L4 business process Custom developments are • General Ledger

• Bank Account Management

Executive • Dealer Business Management

16 September 2024 IBM and AA MOTORS Confidential 3

Source System Target System

Note : S/4HANA Target system runs on Little Endian Architecture Only

BF Name Current Status End State Status Type Short Text

/CUM/MAIN Active No Impact Enterprise Enhancement Compatible Units

/CUM/MAIN_1 Active No Impact Enterprise Business Function Compatible Units Archiving

EA-HR Active No Impact Enterprise Enhancement Human Capital Management

EA-PLM Active Migration Possible:Supported Enterprise Enhancement PLM Extension

EA-TRV Active No Impact Enterprise Enhancement Travel Management Extension

FIN_FSCM_CCD Active Migration Possible:Supported Enterprise Business Function FSCM Functions

FIN_FSCM_CCD_2 Active Migration Possible:Supported Enterprise Business Function FSCM Functions 2

FIN_FSCM_CCD_3 Active Migration Possible:Supported Enterprise Business Function FSCM Functions 3

16 September 2024 IBM and AA MOTORS Confidential 5

BF Name Current Status End State Status Type Short Text

FIN_REP_SIMPL_1 Active No Impact Enterprise Business Function Reporting Financials

FIN_REP_SIMPL_2 Active No Impact Enterprise Business Function Reporting Financials 2

FIN_REP_SIMPL_3 Active No Impact Enterprise Business Function Reporting Financials 3

FIN_TRAVEL_1 Active No Impact Enterprise Business Function Travel Management

FIN_TRAVEL_2 Active No Impact Enterprise Business Function Travel Management 2

FIN_TRAVEL_3 Active No Impact Enterprise Business Function Travel Management 3

HCM_ASR_CI_1 Active No Impact Enterprise Business Function HCM, Administrative Services 01

HCM_ASR_CI_2 Active No Impact Enterprise Business Function HCM, Administrative Services 02

HCM_ASR_CI_3 Active No Impact Enterprise Business Function HCM, Administrative Services 03

16 September 2024 IBM and AA MOTORS Confidential 6

BF Name Current Status End State Status Type Short Text

HCM_ASR_CI_4 Active No Impact Enterprise Business Function HCM, Administrative Services 04

HCM_ASR_CI_5 Active No Impact Enterprise Business Function HCM, Administrative Services 05

HCM_ESS_WDA_3 Active No Impact Enterprise Business Function HCM, ESS on WD ABAP 3

HCM_MSS_WDA_1 Active No Impact Enterprise Business Function HCM, MSS on WD ABAP

HCM_MSS_WDA_2 Active No Impact Enterprise Business Function HCM, MSS on WD ABAP 2

16 September 2024 IBM and AA MOTORS Confidential 7

BF Name Current Status End State Status Type Short Text

LOG_MMFI_P2P Active No Impact Enterprise Business Function MM, Integration MM and FI

MDG_FOUNDATION Active No Impact Enterprise Business Function MDG, Generic Functions

MDG_FOUNDATION_2 Active No Impact Enterprise Business Function MDG, Generic Functions 2

MDG_FOUNDATION_3 Active No Impact Enterprise Business Function MDG, Generic Functions 3

16 September 2024 IBM and AA MOTORS Confidential 8

16 September 2024 IBM and AA MOTORS Confidential 9

SAP and 3rd

16 September 2024 IBM and AA MOTORS Confidential 10

16 September 2024 IBM and AA MOTORS Confidential 11

16 September 2024 IBM and AA MOTORS Confidential 12

16 September 2024 IBM and AA MOTORS Confidential 13

Business Processes Not Impacted Impacted Total

Financial Supply Chain

Financial Supply Chain…

Inventory and Warehouse…

Product Lifecycle Management