Simplification List FI MM SD PP QM 09282
Simplification List FI MM SD PP QM 09282
/ LoB Simplification No
Area
KONV =>
Conditions (Transaction Data) FIELDS not
available in S/4 HANA: KONH-VAKEY => The concatenated variable key field of
condition header tables.
KONH-VADAT => The concatenated variable DATA field of condition header tables.
Logic :- WebDynpro is not available, but can be done with GUI & FIORI.(If FIORI
App is available).
Transactions : - TSTC
ME21/ME22/ME23/ME24/ME25/ME26/ME27/
ME28/ME51/ME52/ME53/ME54/ME59/MR01/MR1M.
Select above table and find out the availability in the ECC system.If found then
check whether any data is available in it or not.(Y/N).
Select above table and find out the availability in the ECC system.If found then
check whether any data is available in it or not.(Y/N).
for example where is 2.1.4.16 Commodity Management Procurement?
Where is 2.1.4.1 co-deployment of SRM, etc
Simplification Value Simplification Action
Current functions are unchanged. recommend that you use the SAP HANA
reporting capabilities for vendor
evaluation based on CDS views and
smart business technology SAP Note:
2228247
the Subsequent Settlement (MM-PUR-VM- there are no direct activities required for
SET) application is replaced by the new continuing the business process for
Contract Settlement (LO-GT-CHB) subsequent settlement, with the only
application exception that the agreements have to
be closed after the end of the validity
period. If a recompilation of the business
volume data is required, the table S111
has to be rebuilt with the report
RMEBEIN3 as described in note 73214
SAP Notes:
2194923, 2215220
Please refer SD pricing. Same simplification Carefully follow the instructions in SAP
for MM. Notes 2188695, 2189301, and 2220005
SAP Note: Pre-checks delivered with
Note 2188735. SAP Note:
2220005
In purchase order it is recommended to use Output Management for Purchase Order
Adobe Forms but due to compatibility the has to be configured. In cases where
form technologies known from Business there is not customer specific
Suite (like SmartForms, SapScript) are configuration for the new output
supported as well. This is also true for the management for purchase orders, it will
print reports.With SAP S/4HANA a new not be possible to print purchase orders
Output Management approach is in place. or to send purchase orders via e-mail or
The complete configuration differs from the XML.
configuration that is used when output
management is based on NAST.
Classic MM transactions and BAPIs for the The replacements that are available
business objects Purchase Order, Purchase since SAP R/3 Enterprise 4.70 shall are
Requisition, and Supplier Invoice have been used. SAP Note:
replaced by the corresponding transactions 1803189: FAQ: End of Support of ME21,
and BAPIs made available with SAP R/3 ME51, and BAPI_PO_CREATE etc.
Enterprise 4.70. With SAP S/4HANA, on- 144081: Replacing MR01 / Functions of
premise, these classic MM transactions MR1M (Release 4.6)
and BAPIs will no longer be available
The foreign trade solution will be not SAP GTS can be connected to S/4HANA
available because SAP Global Trade Services to run the respective foreign trade
is the successor for the business processes. Analysis of all currently used
requirement. foreign trade processes. SAP Note:
2223144
the indicator for direct entry is set now Delete the content for automatic
automatically during the update process of document adjustment of table S111
conditions ( Report RMEBEIN6 (transaction MEI6))
and Delete the content of table WIND
( Report RMEBEIN5 (transaction MEI5)
Rebuild the table entries for S111 and
WIND for the used document categories
by using the appropriate setup reports
(see below). Make sure that the filter
selection for rebuilding the S111 entries
is meaningful by selecting the
appropriate organizational criteria ( time,
org data, docnr, ...) SAP Notes:
2192984, 2215169
The new de-normalized table MATDOC has tables of the SAP ERP 6.0 world do still
been introduced which contains the former exist in S/4HANA as DDIC definition as
header and item data of a material well as data base object and the hybrid
document as well as a lot of further tables will still be used to store the
attributes. Material document data will be material master data attributes. For
stored in MATDOC only and not anymore in compatibility reasons there are Core
MKPF and MSEG Data Service (CDS) Views assigned as
proxy objects to all those tables ensuring
that each read access to one of the
mentioned tables below still returns the
data as before in SAP ERP 6.0. The CDS
Views do the on- the-fly aggregation of
actual stock quantities from the new
MM-IM data model and join the master
data attributes from the material master
data table. Hence all customer coding
will work as before because each read
access to one of the tables will get
redirected in the database interface layer
of NetWeaver to the assigned CDS view.
SAP note 2194618
In classic SAP Business Suite the system Without the statistical moving average
calculates for materials with price control price in few scenarios an alternative way
"Standard", also a moving average valuation of valuation needs to be used. This
in parallel, the so called "statistical" moving concerns for instance
average price. Obviously this statistical Balance Sheet Valuation: Selection
valuation requires also exclusive locking. As variants must be checked and adapted.
said, exclusive locking is limiting the Product Cost Planning: Valuation variants
transactional data throughput, and must be checked and adapted.
therefore shall be avoided in SAP S/4HANA.
In consequence, this parallel statistical
moving average valuation is not available in
SAP S/4HANA 1511.
Purpose Remark
Logic
The deactivation of the To check in ECC system whether "Material Valuation - Statistica
statistical moving average is functionality is available or not.If available, check for the data a
not mandatory in SAP whether Client is using that functionality or not.
S/4HANA, but recommended Search the table, MBEW,EBEW,OBEW,QBEW,CKMLCR,MLCR.
to achieve a significant Select above table and find out the availability in the ECC syste
increase of transactional data whether any data is available in it or not.(Y/N).
throughput for goods
movements. It is important to
note that the deactivation is
not reversible.
Hans comments Available in Platform KPIT HANA Toolkit
Nov 9th 2016 1-2-3? corresponding
description for ABAP
Query
Logic
Where is the ? ?
query for this?
How do we
check if
Webdynpro is
used in the MM
area?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
? ? ?
table changes dmo sap
Transaction not available in SAP only the most recent and most Deprecated versions have been
S/4HANA: SDO1, comprehensive version is disabled.
VA05N, VA15N.VA25N, VA45N available.
SPRO> GTS: Component LO-GT. N/A Custom code adoption on the new
DB-Design
Transaction not available in S/4
HANA
WB24,WB25_COMP,WB2B_NETUSE
R,POFO1,POFO2,POFO3
SD Classification 2.1.1.15
functionality of
Customer Not available
master In traditional ERP systems, you could classify
customers using transactions for customer
master data maintenance (using the menu Extras
-> Classification).
SD Customer CRM on Premise, Cloud 4 Service and SAP Hybris 2.1.3.1.
Interaction provide successors for interaction center help
Centre(CIC) desk use.
SAP Note 2229726
FIELDS not available in S/4 HANA: New table VBTYPL Change of existing
VBAK-VBTYP => SD document category field replaces VBTYP functionality.No influence on
(Char1). No change in business process.Tables are business processes expected
obsolete.Abap query is required to search the above
tables and whether the data exists in the tables or not.
Currency of document header will fill the table SAP recommends that you run
PRCD_ELEMENTS the post-processing report
PRC_MIG_POST_PROCESSING as
soon as possible.
TRANSACTIONS:
VA05 &
VA05N => Open Sales Orders
VF04/VF06 => Display all sales order pending for
invoice
VF45 => shows deferred revenues, unbilled receivables,
billed and realized amounts on the level of a sales
document item.
TRANSACTIONS not available in S/4HANA:
VF42 => Update Sales
Documents
VF43 => Revenue Recognition: Posting Doc
VF44 => Revenue Recognition: Work list
VF45 => Revenue Recognition: Revenue Report
VF46 => Revenue Recognition: Cancellation
VF47 => Revenue Recognition: Consistency Check
VF48 => Revenue Recognition: Compare Report
Logic :- No change in business process. Abap
query is required to search the above tables and whether
the data exists in the tables or not. Transaction code
which are obsolete, can be checked through T-Code
ST03N.
Table: EIKP: EIKO SAP GTS SAP recommends to use SAP
GTS functionality, instead of
foreign trade.The below
mentioned fields for Letter of
Credit/ Legal control/ Export
control/ Preference
management in Foreign Trade is
supported by GTS and not
through Material Master: CAP
product list no.
CAP prod. Group
Preference status
Vendor decl. status
Exemption Certificate
Exemption Cert. No.
Iss.date of ex.cert.
Military goods
Transaction not available in SAP S/4HANA: SAP CRM on- If sales support functionality is
OV/8 Test Data - Transfer Data - Cond.: OV/9 Display Test premise or SAP requested by customer, it is
Data: OV1Z Define Product Allocation Procedure: OV2Z Cloud for recommended that customers
Define Product Allocation Object: OV3Z Determine Prod. Customer start evaluating a side-by-side
Allocation Hierarchy: OV5Z Maintain Consumption CRM on-premise scenario or use
Periods: OV7Z Create Characteristics for Rem.Alloc: OV8Z Cloud.
Check Settings: OV9Z Suitable Statistical Structures: OVBR
Assignment to Item Category: OVBS Rule Table for
Determining Dates: OVCB Structure of Reporting View
(rest tables mentioned in table list)
SAP Note: 2214585
Path.> SD> Basic Functions > Integration with Contract Contract Accounts Customers that used the
A/R and A/P > Specify Posting to Contract A/R and A/P Receivable and integration between FI-CA and
For Customer Groups Payable(FI-CA) SD in a distributed scenario, and
Integration >Sales and are planning to move to
Distribution >Define Logical Systems for Distributed SD S/4HANA, have to use the FI-CA
Systems within S/4HANA.
Transaction not available in SAP S/4HANA: Hybris Hybris is the strategic solution to
WCU1 Maintain support web-channel processes.
customer: WCUM Maintain customer: WW10 IAC product
catalog: WW20 IAC Online Store: WW30 SD part for IAC
MM-SD
Transaction not available in SAP S/4HANA: Hybris e- Hybris is the strategic solution to
WPC1 Prepare product commerce support web-channel processes.
catalog Idocs: WPC2 Prepare item Idocs: WPC3 Prepare
catalog change Idocs: WPC4 Prepare item change IDocs:
WPC5 Convert product catalog: WWCD Product catalog:
Display change docs.: WWM1 Create product catalog:
WWM2 Change product catalog: WWM3 Display product
catalog: WWM4 Copy product catalog: WWM5 Delete
product catalog
They are planned to be available in a future release of SAP master data They are planned to be available
S/4HANA, on-premise edition. (customer and in a future release of SAP
supplier) must be S/4HANA, on-premise, edition. If
created only by you want to perform a master
using business transfer of data pertaining to
partner as the customer or supplier, SAP
leading object recommends that you do so
after contacting the S/4HANA
Master Data team for Business
Partner (DL STE_MD_BP
<DL_5555B04B7BCF84913B0000
[email protected]>).
Instead of the VBBS we use the VBBE where each ATP- In VBBE where the new HANA ATP we do not
relevant requirement is explicitly stored. each ATP-relevant need, pre-aggregation anymore
SAP Note: 2209696 requirement is and therefore this table is
explicitly stored. obsolete.
SPRO>Logistics Execution> DSD> Basic function> Activate N/A The Direct Store Delivery
DSD:Basic Function> Activate DSD : The Direct Store functionality is on the roadmap
Delivery (LE-DSD) is related to Business Function EA-CP. for SAP S/4HANA
Note: It
is planned to change the state of Business Function EA-CP
so that a system conversion is
possible for customers having business function EA-CP
switched on.
Transactions not available in S/4 HANA:
WB24,WB25_COMP,WB2B_NETUSER,POFO1,POFO2,POFO
3
SAP Notes: 2198031, 2204137, 2198035
Remark Hans Available in Level of Effort Level of Recommended
Comment Platform 1-2-3? during Migration: OCM initiative before
L-M-H impact: L- Migration Start
M-H Y/N?
Considered in L L N
Rule1,4
Considered in M M Y
Rule1,4,
Considered in Rule H H Y
2
Platform 1 H H Y
Rule2 H H Y
Rule2 M H Y
Pre- Platform 1,2 M M Y
requisite--
Credit
managemen
t need to be
activated
Platform 1,2 M H N
Added in platform M M N
1, to be added in
platform 2
Added in platform M M N
1, to be added in
platform 2
Will be adding in L L N
rule 1-4
Wiil be
in Platform 1
Added in platform L L Y
1, to be added in
platform 2
Will be adding in L L N
rule 1-4
Added in platform L L N
1, to be added in
platform 2
Added in platform M M N
1, to be added in
platform 2
Added in platform M M N
1, to be added in
platform 2
Added in platform H H Y
1, to be added in
platform 2
Added in platform M M Y
1, to be added in
platform 2
Added in platform M M N
1, to be added in
platform 2
Will be in platform M M N
1
Will be considered M M Y
in platform 1
Will be considered H H Y
in platform 1
Will be considered M M Y
in Platform-1
Will be considered M M Y
in Platform-1
Will be available in M M N
platform1
Will be available in M M N
platform1
Will be available in M M Y
paltform1
Will be available in L L N
platform1
M M N
Will be considered M M N
in Platform 1
Will be considered M M Y
in Platform 1
Will be considered M M N
in Platform 1
Will be considered M M Y
in Platform 1
KPIT HANA Toolkit corresponding description STATUS
for ABAP Query
Platform 1 Only
N/A
N/A
N/A
N/A
Field Condition Class (KOAID) of Table KONV COMPLETED
should have the value ->
A,B,C,D,E,F,G,H,Q,W.
Then Sub-Module, Pricing is ACTIVE in the
system.
N/A
N/A
Fetch KKBER (Credit control area) from table COMPLETED
T001 (Company Code). Find data by using
KKBER (Credit control area) as Input Value
for table KNKK (Customer master credit
management: Control area data). If value
exist then Sub-Module "Credit
Management" is active or else It is Inactive.
N/A
N/A
N/A
N/A
How many Pricing condition tables is being used for
SD?_PRICING
N/A
N/A
Do you use "Simple Credit Limit" check for sales
document table: VBAK?_Credit management
N/A
N/A
N/A
N/A
In table Conditions: Structures:T681: pass application "V"- SD in
field 'KAPPL" and count the number of record in Table "KOTABNR"
N/A
N/A
Fetch Value of field KLIMP (Check credit limit) and CMGRA (Credit
group sales order) from table TVAK (Sales Document Types). If
value exists it means "Simple Credit Limit" is used.
Tresury & Risk Management 2.1.25.2 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.3 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.4 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.5 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.6 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.7 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.8 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.9 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.10 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.11 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.12 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.13 Financial - Tresury & Risk Manageme
Tresury & Risk Management 2.1.25.14 Financial - Tresury & Risk Manageme
Miscellaneous 2.1.26.1 Financial -Miscellaneous
General Ledger
SAP Invoice and Goods Receipt Reconciliation
Asset Accounting
Integration to Lease accounting engine (LAE)
Cost Elements
Fiduciary Deposits
Drawable Bonds
Master Agreements
Offers
Data Archiving
T-code-FS01/KP06/KP65/CJ40/KPF6/CJ40/CJR2/CK11/CK42/KB11/KKP4/F.24. Y
Logic:-No change in business process.Above T-Codes which are functioning in
ECC but not in S/4 HANA can be checked through T-Code ST03N.
NA Y
Pending Y
Pending Y
Table-ANEP/ANEK/ANEA/ANLP/ANLC Y
Logic:-No change in business process. Abap query is required to search the
tables and to check whether the data exists and is updated on a regular basis in
current fiscal year.
S/4 HANA implies migration to New Asset Accounting. If you want to use new Y
Asset Accounting, you are not allowed to use Integration to JVA (Joint Venture
Accounting).
T-code-FI01/FI02/FI03/FI12/FF7A/ Y
Logic:-No change in business process.Above T-Codes which are functioning in
ECC can be checked through T-Code ST03N. Check tables
REGUH/REGUP/PAYR/T012K/BNKA for data to determine use of classical cash
managment in the system. Yes or No.
COEP/COBK-Pending. Y
Pending Y
Table-CBPR Y
Logic:-No change in business process. Abap query is required to search the table
and whether the data exists in the tables or not
T-code-KA01/KKPHIE/KKR0)/KKP2/KKP4/KKP6/KKPX/KKPY/ Y
Logic:-No change in business process.Above T-Codes which are functioning in
ECC can be checked through T-Code ST03N
Y Ledgers ->Parallel Accounting-> Defi
Financial Accounting (New) under Financial Accounting Basic Settings (New)->
T-code-KA01/KA02/KA03/KA06 Y
Logic:-No change in business process.Above T-Codes which are functioning in
ECC can be checked through T-Code ST03N
Transaction KE30-Roobal-AT51/AT51T-Pending. Y
SAP Customizing Implementation Guide -> Financial Supply Chain Management - Y
> Treasury and Risk Management->Money market->Correspondence or
SAPmenu->FSCM->Treasury and risk Management->Transaction Manager-
>Information system->Transaction->Correspondence.-Pending.
SAP Menu -> Accounting -> Financial Supply Chain Management -> Treasury and Y
Risk Management->Transaction Manager->derivative->information system-
>Postion->Display Quantity ladger position.- Pending.
SAP Menu -> Accounting -> Financial Supply Chain Management -> Treasury and R Y
Y
TRANSACTIONS not
available in S/4HANA:
FD32 => Maintenance of the credit account master data VKM1 => Release of
credit blocked sales orders.
Logic :- No change in business process.Abap query is required to search the
above tables and whether the data exists in the tables or not. Above T-Codes
which are functioning in ECC but not in S/4 HANA can be checked through T-
Code ST03N.
Table-MLHD ,MLIT,MLPP. Y
Logic:-No change in business process. Abap query is required to search the table
and whether the data exists in the tables or not.
Table-VIOB03,VIMI01,VIOB03,VIMI01,VIBDBU,VIBDRO. Y
Logic:-No change in business process. Abap query is required to search the table
and whether the data exists in the tables or not
T-code-AOBJ/SARA Y
Logic:-No change in business process.Above T-Codes which are functioning in
ECC can be checked through T-Code ST03N
Pending Y
Simplification Value Simplification Action
Write access (INSERT, UPDATE, DELETE,
Change in existing functionality. With the installation of MODIFY) was removed from SAP standard, or
SAP S4 HANA Finance, on premise edition totals and has to be removed from custom code – refer
application index tables were removed and replaced by to SAP note 1976487 related to Custom code.
identically-named DDL SQL views, called compatibility Also there are mandatory configuration steps
views. These views are generated from DDL sources. in General Ledger, Asset accounting, account
SAP S/4HANA on premise edition 1511, additional based CO-PA and Cash management (if used)
tables were (partially) replaced by Universal Journal
(ACDOCA).
Change of existing functionality New General Ledger Mandatory application configuration steps
(G/L in SAP Accounting powered by SAP HANA) is related to General Ledger. Check and
mandatory in SAP S/4HANA.Classic General Ledger is complete configuration for G/L, currencies,
mostly transformed automatically into a basic and integration of CO postings
implementation of New General Ledger (G/L in SAP
Accounting powered by SAP HANA).
With SAP Invoice and Goods Receipt Reconciliation Customers traditionally use Microsoft Excel
(part of the HANA License), every Business Suite, sheets and other reporting means to monitor
SoH, or Simple Finance Customer could organize the and
processing of GR/R differences. This Functionality is not organize the GR/IR account. With SAP
available for SAP S/4HANA, on premise edition 1511. S/4HANA, they have to revert to these
The transactions and apps. To process GR/IR differences methods. Monitoring of GR/IR Account needs
such as MR11 remain available, only the monitoring to be organized by the customer
and organization Capabilities added by SAP Invoice and
Goods Receipt Reconciliation are no longer available.
SAP HANA Live provides reporting capabilities for If HANA Live views are used, time and
Business Suite and Suite on HANA customers. A resources should be planned for migration to
Strategic decision was taken to switch the technology CDS Views or for
from Calculation Views to CDS Views with SAP Implementation of the additional RDS
S/4HANA. Reporting scenarios built with the SAP HANA package (if that is available). If the customer
Live content in Business Suite, Suite on HANA, or copied calc views delivered by SAP or created
Simple Finance installations have to be rebuilt manually userdefined calc views on top of SAP
with CDS Views in SAP S/4HANA delivered views, they need to be redone with
CDS Views.
With the integration of SAP Accounts Receivable (FI-AR) None
with FSCM Biller Direct it is possible to offer to end-
customers the convenience of receiving invoices,
viewing account status, and making Payments online as
a self-service. The functionality is not considered as the
target architecture. The Customer can still continue to
use the functionality to make the system conversion to
SAP S/4HANA, on premise edition 1511 less disruptive.
The functionality integration of SAP Accounts
Receivable (FI-AR) with FSCM Biller Direct is not the
target architecture, but still available and can be used
within SAP S/4HANA, on premise edition1511
Functionality not available in SAP S/4 HANA ( No Need to check the conversion pre checks
Functional Equivalent avaialble) If you want to use new related business function
Asset Accounting, you are not allowed to use the
business function JVA. Integration with New General
Ledger Accounting (JVA_GL_INTEGRATION) is also not
compatible with new Asset Accounting.
Change of existing Functionality. Classic Cash Classic Cash Management is replaced by the
Management is replaced by the new SAP Cash new SAP Cash Management powered by SAP
Management. A SAP Business Suite customer using HANA. A
classical Cash Management needs to activate the new SAP Business Suite customer using classical
SAP Cash Management. Once customers have installed Cash Management needs to activate the new
SAP S/4HANA, on premise edition 1511 (or SAP Simple SAP Cash
Finance), SAP Cash Management powered by SAP Management. Required action: migrate
HANA is the only compatible cash management existing house bank account into BAM
product to be used. Classic cash management accounts. This is mandatory, no matter
(including Liquidity Planner) is not officially supported. customer use BAM Lite (in SAP Accounting
powered by SAP HANA) or BAM (in SAP Cash
Management). For additional Information see
the following sources: Trouble Shooting
Consulting Note for migration:
http://service.sap.com/sap/support/notes/21
75053
Changes of existing Functionality.
·Choose
Application Help: CO-PA characteristics for
appropriate
http://help.sap.com/sfin200.
profitability reporting. Set up required master
data in order to derive correct profit centers,
·functional
Configuration Guide
areas, and Data
segments, Setup
and Guide:
so on.Build
http://service.sap.com/erp-inst -> SAP
allocations structures, settlement profilesERPand
Add-
costing sheets to ensure that all required
Ons
value-> flows
SAP Simple Finance,modelled.Planning
are properly on-premise
edition -> SAP Simple Finance,
of migration process when moving on-premise
from older
edition
release of SAP ERP Financials
1503 -> Data Setup Guide for SAP Cash
Management powered by SAP HANA.
Decision needed concerning scope of existing
CO-OM planning, P&L planning, and profit center planning processes and ability to use
planning are now covered by Integrated Business delivered
Planning (SAP Note 2081400). CO-OM planning: If you business content for Integrated Business
do not want to use "Integrated Business Planning for Planning for Finance. Activate Integrated
Finance” but classic CO-OM planning functions instead, Business Planning for Finance and compare
you may apply the modifications as indicated in SAP against project needs. No
Note 1946054.With these modifications, the changes to existing tables. Instead new
deactivation of the old CO-OM planning transactions business content for Integrated Business
can be removed. However, please be aware that the Planningfor Finance must be activated as
former planned integration to P&L planning is not described in SAP Note 2081400. Follow
available in SAP S/4HANA, on premise edition steps in Installation Guide provided with SAP
1511.Customer project required to activate Integrated Note 1972819. Explore SAP BPC functions to
Business Planning for Finance and adapt the delivered extend scope (e.g. use of business process
queries to customer needs. Customers preferring to flows)
delay such a project can reactivate the classic planning
transactions using the SAP Note described above.
Activity-Based Costing (CO-OM-ABC) using delta Activate Operational Activity Based Costing.
versions is not available in SAP S/4HANA. Delta
versions in general are not available in SAP S/4HANA,
on-premise edition 1511, so the option to use Parallel
Activity Based Costing (setting in the controlling area) is
no longer available. Activity-Based Costing using
version 0 (Integrated Activity Based Costing in the
controlling area settings) is stillsupported.
General Cost Objects and Cost Object Hierarchies are Do not activate Cost Objects in controlling
not available within SAP S/4HANA, on-premise edition area. Do not build a data model that requires
1511 use of
general cost objects or cost object
hierarchies.
Parallel Delta Versions for Actuals in Controlling. With If currency and valuation profiles exist for
the merge of FI and CO into the Universal Journal a new group valuation, profit center valuation or
approach to parallel valuations will be implemented. parallel cost of
Therefore, the existing solutions based on parallel delta goods manufactured and delta versions have
versions for actuals inControlling have to be adapted. been set up that contain such data you will
The functionality of "Transfer prices" valuating the not be able
transfer of a goodor service according to legal-, group-, to migrate.Group valuation, profit center
or profit center valuation is not yet supported. valuation and parallel cost of goods
Thefunctionality of "Multiple Valuation of Cost of manufactured not currentlysupported. In a
Goods Manufactured" providing parallel valuations in new system, configuration activities are
CO according to multiple accounting principles is not blocked. In an existing system, migration
yet supported. See SAP note 2127080 isblocked.Missing function for intercompany
processes and reporting according to
multiple accountingprinciples.
Cost elements become part of the chart of accounts, Design for chart of accounts must include
maintenance in account master data (transaction FS00) profit and loss accounts and secondary cost
instead of separate cost element master data elements that represent value flows within
(transactions KA01, KA02, KA03, and the company.Also ensure that master data is
KA06). Account master record includes new field for set up to derive functional areas, profit
cost element category. Field status groups can centers, and so on
remain unchanged but default account assignments correctly.Adapt to the new cost element
must be set via transaction OKB9 rather than in approach
the cost element master.Implications: Customer roles
(menus and authorizations) need to be adjusted.To
maintain primaryand secondary cost elements you will
need authorization for both G/L accounts and cost
elements.Period close locks will have to ensure that
postings are allowed to the appropriate accounts and
tothe appropriate CO business transactions (transaction
OKP1).
The old yield curve functionality has been replaced by The customers have to implement the yield
the more flexible Yield Curve Framework. The curve framework before they go to the SAP
Yield Curve Framework provides a powerful yield curve S/4HANA On
framework that enables you to do the Premise 1511 Edition.
following:
The old functions for the accrual/deferral of expenses The customers have to implement the new
and revenues have been replaced by a central central accrual/deferral of expenses and
function for the accrual/deferral of expenses and Revenues
revenues for all kinds of financial transactions. functionality before they go to SAP S/4HANA
On Premise 1511 Edition.
Commodity Risk Management is switched off Execute the Conversion Pre-Checks. The
technically in SAP S/4HANA, on-premise edition 1511. A “central pre-transformation check” checks
successor is planned for a future release of SAP the deactivated
S/4HANA on-premise edition 1511. CM Business Functions. Check if the
Commodity Business Functions are active – if
yes, the system conversion with active
Commodity Management Business Functions
to SAP S/4HANA on-premise
edition 1511 is not possible. The following
Commodity Management Business Functions
have been
deactivated in SAP S/4HANA, on-premise
edition 1511:
Usage of Material Ledger for parallel currencies and paraChanges of existing functionality
The SAP Simple Finance, on-premise edition 1503 does Functionality not available in SAP S/4HANA
not support Real Estate Classic (RE Classic). (functional equivalent available)
The business requirements can be covered by using
Real Estate Flexible (RE-FX) functionality. For
more details, see SAP Note 1944871. As RE-FX is the
more up-to-date solution and has a much
broader functional scope (see SAP Note 517673), only
RE-FX is included as the RE component in the
SAP S/4HANA on-premise edition.
You have installed SAP Simple Finance and want to use Data aging needs to be configured, and in all
SAP Data Aging for the FI document. To do so, places where you previously accessed the
you must adjust customer-specific programs or archive, you
modifications. For the FI document in SAP Simple must now access the cold area of the
Finance, archiving was replaced by data aging, pushing database and potentially the archive as well.
out data to the cold store area of the If you use
database. Access to files archived before the system standard SAP function modules for this, no
conversion is still supported. adjustment is required (otherwise, see SAP
note
2076652).
SAP Smart Business for SAP Simple Finance includes There should be replacement Smart Business
many KPI reports on various aspects in FI, CO, Apps for all existing Smart Business Apps with
AP, and AR. A strategic decision was taken to switch the equivalent capabilities.
technology from Calculation Views to CDS
Views with SAP S/4HANA. This requires a technical
adaptation at the customer's site: Existing
personalization needs to be redone, personalized tiles
have to be deleted and recreated, and userdefined
KPIs have to be redone on CDS technology.
Impact H-M-L Application Component Business Impact notes
H FI-CF 2270333 & 1976487
H FI-GL 2270339
M FI-GL 2270359
M FI-GL 2270360
M FIN-FSCM-BD-AR 2270384
M FIN-FSCM-BD 2270386
H FI-AA 2270387
H FI-AA 2270388
M FI-AA 2270391
M FI-AA 2270392
M CO-OM-ABC 2270408
M CO-PC-OBJ 2270411
L CO-PA 2270414
H CO-PA 2270419
L CO-FIO 2270442
L FIN-FSCM-TRM-TM 2270450
M FIN-FSCM-TRM 2270461
M FIN-FSCM-TRM 2270462
M FIN-FSCM-TRM 2270469
L FIN-FSCM-TRM 2270470
M FIN-FSCM-TRM 2270514
L FIN-FSCM-TRM 2270518
L FIN-FSCM-TRM 2270521
L FIN-FSCM-TRM 2270522
L FIN-FSCM-TRM 2270523
L FIN-FSCM-TRM 2270526
L FIN-FSCM-TRM 2270527
L FIN-FSCM-TRM 2270529
L FIN-FSCM-TRM 2270530
H FI-AR-CR 2270544
FIN-FSCM-CR
H CO-PC-ACT 2270546
M RE-FX 2270550
M FI-GL-GL 2270561
M FIN-FSCM-CLM 2270562
FI-AP-IS
FI-AR-IS
Module sub-module/ Simplification Item Reference IMG node or transactional data Activated in
/ LoB Simplification No present/queiry customer
Area system: Y/N
PP Master Data Simplified Sourcing 2.1.12.7 Production --> Master Data -->
Create Production Version ( T- Code
= C223)
ABAP query can be created to check
entries in table MKAL.
PP Downtimes 2.1.12.22 -
Functionality
PP MiniApps PP-PI 2.1.12.23 -
The default way of planning parts Create MRP areas for every M
to be provided to subcontractors subcontractor + Run regenerative
is based on MRP areas. A MRP after the upgrade
subcontracting MRP area should
be created for every
subcontractor. It is not required to
create an MRP-area-specific
material master record for every
part to be provided to the
subcontractor, but of course it is
possible if you want to overrule
the default planning parameters.
- - L
Usage of the ANSI /ISA S95 Use the POI interface or the MES M
interface is not recommended in interface to connect SAP S/4HANA
S/4HANA. to an MES system or a planning
system.
This functionality available + SAP Create Master data in SAP APO & M
Advanced Planning and setup flow manufacturing in SAP
Optimization (SAP APO) acts as APO.+ Check custom code
successor.
Where is
the ABAP
query for
this to
check on
active
use? To
state 'no
impact' is
incorrect.