Universal Parallel Accounting: Scope Information: Symptom

3191636_E_20231214 14/12/23, 8:31 PM
SAP Note
3191636 - Universal Parallel Accounting: Scope Information

Component: FI-GL (General Ledger Accounting), Version: 40, Released On: 14.11.2023
Symptom
You are interested in the business function Universal Parallel Accounting (FINS_PARALLEL_ACCOUNTING_BF)
which is available as of release SAP S/4HANA 2022. You want to know which features are included in its scope and which are
not.
Disclaimer
This SAP Note outlines our general product direction and should not be relied upon in making a purchase decision. This SAP
Note is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of
business outlined in this SAP Note or to develop or release any functionality mentioned in this SAP Note. This SAP Note and
SAP’s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason
without notice. This SAP Note is provided without a warranty of any kind, either expressed or implied, including but not
limited to, the implied warranties of merchantability, fitness for a particular purpose, or noninfringement. SAP assumes no
responsibility for errors or omissions in this SAP Note, except if such damages were caused by SAP intentionally or by gross
negligence.
Safe Harbor Statement
This SAP Note is intended to outline future product direction and is not a commitment by SAP to deliver any given code or
functionality. Any statements contained in this SAP Note that are not historical facts are forward-looking statements. SAP
undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are
subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The timing or
release of any product described in this SAP Note remains at the sole discretion of SAP. This SAP Note is for informational
purposes and may not be incorporated into a contract. Readers are cautioned not to place undue reliance on these forward-
looking statements, and they should not be relied upon in making purchasing decisions.
Note
This is not a roadmap. For roadmap information, see the SAP Roadmap Explorer.
Other Terms
FINS_PARALLEL_ACCOUNTING_BF
Reason and Prerequisites
Solution
General Information
Characteristics of the Universal Parallel Accounting business function:
Shipment: As of release SAP S/4HANA (on premise) 2022
Availability: For pilot customers selected by SAP only
Level of activation: Business function is activated on system level (and not on client or organizational-unit level, for
example, company-code level).
Migration from previous solutions to Universal Parallel Accounting:
Release SAP S/4HANA (on premise) 2022: Not possible. Activate the Universal Parallel Accounting business
function with a new implementation in a system in which no data has been posted yet.
As of release SAP S/4HANA (on premise) 2023: Possible if relevant prerequisites are fulfilled. For more
information, see SAP Note 3327778.
https://userapps.support.sap.com/sap/support/sfm/notes/print/0003191636?language=E&token=51B19E0829302AEA23CC8756C191E0D5 Page 1 of 29
3191636_E_20231214 14/12/23, 8:31 PM
Affected application components:

FI-GL (General Ledger Accounting)
FI-AA (Asset Accounting)
CO-OM (Overhead Cost Controlling)
CO-PA (Profitability Analysis)
CO-PC-OBJ (Cost Object Controlling)
CO-PC-OBJ-EBR (Event-Based Revenue Recognition)
CO-PC-PCP (Product Cost Planning)
CO-PC-ACT (Actual Costing)
CO-PC-ML (Material Subledger)
IM (Investment Management)
MM-IM-VP (Inventory Balance Sheet Valuation)
Compatibility Scope for SAP S/4HANA
For information about simplification items in SAP S/4HANA, see SAP Note 2269324.
Localization:
Universal Parallel Accounting is supported for the following countries: USA, Germany, France, Japan, and
Romania.
Migration to Universal Parallel Accounting is supported for the following countries: USA, Germany.
Required business functions and how to apply for them:
Depending on your scenario, you need one or two business functions. Both business functions are only available for
authorized users. To request authorization for the business functions, you must proceed as described below:
Sce Scenario 1: New system implementation Scenario 2: Systems with existing data
nari s
o
Scen Release 2022 Release 2023

ario
supp
orte
d as
of:
Scen The following prerequisites must be met: If postings exist in your system, the business function can only be activated i
ario n connection with a migration project and only if the prerequisites for the m
No postings exist in any company code in
desc igration are met. For more information, see Universal Parallel Accounting
your system.
ripti Migration.
Asset Accounting: No asset master data a
on:
nd no asset postings must exist in your sy
stem.
Materials Management: No material mas
ter data and no material prices must exist
in your system.
Req FINS_PARALLEL_ACCOUNTING_BF ( FINS_UPA_MIGRATION (Universal Parallel Accounting Migration);

uire Universal Parallel Accounting) for the prechecks
d bu FINS_PARALLEL_ACCOUNTING_BF (Universal Parallel Accounting
sines )
s fun
ction
s:
Proc 1. Read the information contained in this sc 1. Read the information contained in this scope information note and in the
edur ope information note and in the following documentation for the following business functions carefully:
e: business function documentation carefull
Universal Parallel Accounting Migration | SAP Help Portal
y:
Universal Parallel Accounting | SAP Help Portal
Universal Parallel Accounting | SAP Help
Portal
2. Contact SAP and request authorization fo
2. Run prechecks to analyze whether the migration is possible.
3191636_E_20231214 14/12/23, 8:31 PM
r the business function activation. To do t

his, create a case for component FI-GL-G
3. Contact SAP and request authorization for the business function activatio
L and enter “[Activation of Universal Par
n. To do this, create a case for component FI-GL-GL and enter " [Migration
allel Accounting]” as the subject.
to Universal Parallel Accounting]" as the subject.
3. Once SAP has approved the activation, i
mplement the correction instruction in S 4. Once SAP has approved the activation, implement the correction instructi
AP Note 3207221 (only accessible for aut on in SAP Note 3325920.
horized customers).
5. Activate the business function using the Switch Framework Customizing
4. Activate the business function using the S
(SFW5) transaction. Be aware that the activation cannot be reversed.
witch Framework Customizing (SFW5) t
ransaction. Be aware that the activation c 6. You must also activate the FINS_PARALLEL_ACCOUNTING_BF (Unive
annot be reversed. rsal Parallel Accounting) business function. However, you do not need separ
ate permission from SAP for this because this is included in the permission f
or the FINS_UPA_MIGRATION (Universal Parallel Accounting Migration)
business function.
Scope information (including main restrictions)

Recommendation on how to use the scope information:
1. First, check the features that are in scope.
2. Then check the features that are not in scope or have restrictions.
Please note that this list is not exhaustive.
Tip: If you are interested in information specific to a particular release, for example, regarding the changes for the current
release, you can use the search function (Ctrl + F) and look for key words, such as "relase 2022" or "As of release 2023".
General Finance Features
Featu I N Additional Details

re n ot
S in
c S
o c
p o
e p
e/
W
it
h
R
es
tr
ic
ti
o
n
s
End-to X With universal parallel accounting, financial reporting is possible on an end-to-end basis and provides full audit tra
-end p ils through consistent information across all ledgers.
aralleli
sm acr
oss led
gers a
nd app
licatio
ns
Count X
3191636_E_20231214 14/12/23, 8:31 PM
ry-spe To enable the definition of country-specific rules, at least one local accounting principle must be defined per countr
cific lo y and assigned to the company codes created for each country.
cal acc For example, in Asset Accounting, you specify the corresponding valuation views for each accounting principle.
ountin
g princ
iple
Generi X If you operate in more than one country, you cannot use a generic local accounting principle; instead, you must use
c local different country-specific local accounting principles for these countries.
accou
nting
princi
ple
Multip X Up to 10 currencies are supported across accounting processes in the FI-GL, FI-AA, CO, and CO-PC-ML application
le curr components.
encies
Restriction: Currency type 20 (controlling area currency) is not supported.
Altern X Enhanced procedure of adding an alternative fiscal year variant.

ative F
Restrictions:
iscal Y
ear Va Some functions still have restrictions which are outlined here:
riant General:
Only one common fiscal year variant is allowed in the leading ledger.
If group valuation is used: The FYV that is assigned to the group valuation ledger must be the same as t
he FYV that is assigned to the leading ledger.
Alternative FYVs can only be assigned to the non-leading, parallel ledger on company code level.
Alternative FYVs can only be assigned to new company codes, where no data has been posted yet.
The posting period start dates and posting period end dates of the alternative fiscal year variants must n
ot differ from the posting period start and end dates of the common fiscal year variant assigned to the le
ading ledger. The posting periods of all related fiscal year variants must be of equal length. This means t
hat, for example, if the posting period of the common fiscal year variant equals the calendar month and
the fiscal year has 12 posting periods, then the alternative fiscal year variant must also follow this patter
n. Currently, industry-specific fiscal year variants, such as the 4-4-5 variant, are not supported as altern
ative FYVs.
Asset Accounting:
You cannot use independent assets under construction. This means that: You can neither create asset
s under construction nor settle them to completed assets.
As an alternative, we recommend that you settle investment projects.
Production Accounting:
Period-end production cost posting is not supported with the alternative fiscal year variant. Use event
-based production cost posting instead, which fully supports the universal parallel accounting capability
.
Inventory Accounting:
Product Cost Planning:
Release Material Cost Estimates (CK24): For the Organizational Measure (Marking Allowance) yo
u can only mark material cost estimates for one company code at once.
Dependencies
If you use different fiscal year variants, run your period-end closing activities using the combination of ledger
and company code that corresponds to the relevant alternative fiscal year variant. If you run the activities for
one or more periods (such as for actual cost rate calculation or settlement), you should keep the following in
mind:
- You have to start your period-end closing activities individually per ledger.
- Depending on the respective job, you also have to start your period-end closing activities individually per
ledger and company code.
If you run period-end activities for a specific key date (for example, foreign currency valuations), you can run
the respective job for all ledgers even if you use different FYVs.
3191636_E_20231214 14/12/23, 8:31 PM
Shorte X Not in scope.

ned fis
cal yea
r
Legal X
valuati
on
Group X Restrictions:
valuati
General considerations:
on
Only the approach of separate valuation views in separate ledgers is supported; the approach using several val
uation views within one ledger is not supported.
A subsequent implementation of Group Valuation is currently not supported.
All company codes have to be assigned to the Group Valuation ledger.
Logistics Integration:
Classic intercompany processes are not supported in combination with Group Valuation. Please use the Adva
nced Intercompany business processes instead.
The elimination of intercompany margins is supported for Advanced Intercompany Sales and Stock Transfer
processes. For other intercompany processes, the elimination posting logic is not available yet. For more infor
mation, see Advanced Intercompany Sales and Advanced Intercompany Stock Transfer.
General Ledger Accounting:
Posting currency adjustments: Postings in a ledger group containing several ledgers including 4G or postings
in a ledger group left blank are not yet supported. In this case, post currency adjustments either in legal ledge
rs only or in the group valuation ledger only.
The following valuation runs are not supported:
- Regroup Payables/Receivables
- Perform Further Valuations
- Perform Foreign Currency Valuation; please use the Advanced Foreign Currency Valuation run instead.
Transaction currency amounts cannot be reported according to group valuation. The transaction currency am
ounts displayed are based on legal valuation. Note that this can also have implications for the balance carryfor
ward.
Inventory Balance Sheet Valuation cannot run for the group valuation ledger (ledger not available in filter). Si
nce inventory balance sheet valuation runs on company code level only, this behavior is intended.
Revenue and Cost Accounting:
Event-Based Revenue Recognition: In general, the posting logic of Event-Based Revenue Recognition is the s
ame as for any other non-leading ledger.
However, as soon as Advanced Intercompany Sales and Advanced Intercompany Stock Transfer and Group
Valuation are used in combination, there is a specific posting logic for revenue recognition in the group valua
tion ledger, specifically for the integration of Event-Based Revenue Recognition with Sell from Stock and the
respective revenue recognition keys SFS, SFSCCM and SFSN. In these scenarios, to make sure that the postin
g logic in the context of intercompany elimination postings is correct, the elimination postings created in the
group valuation ledger during billing do not trigger Event-Based Revenue Recognition postings, neither in re
al-time processing nor during month-end close.
Please note that it is not possible to maintain different revenue recognition rules for the group valuation ledge
r compared to the legal valuation ledger that is assigned to the group accounting principle since the configura
tion for “Document Types” and “Recognition Keys – Company Code and Accounting Principle Settings” depe
nds on the accounting principle.
Profit See A Release 2022: Not in scope.

Center dditio
As of release 2023: In scope with restrictions.
Valuat nal D
ion etails Restrictions:
3191636_E_20231214 14/12/23, 8:31 PM
colum General considerations:

n.
Only the approach of separate valuation views in separate ledgers is supported; the approach using several val
uation views within one ledger is not supported.
A subsequent implementation of Profit Center Valuation is currently not supported.
All company codes have to be assigned to the Profit Center Valuation ledger.
Logistics Integration:
Classic intercompany processes are not supported in combination with Profit Center Valuation. Please use the
Advanced Intercompany business processes instead.
The elimination of intercompany margins is supported for Advanced Intercompany Sales and Stock Transfer
processes. For other intercompany processes, the elimination posting logic is not available yet. For more infor
mation, see Advanced Intercompany Sales and Advanced Intercompany Stock Transfer.
General Ledger Accounting:
Posting currency adjustments: Postings in a ledger group containing several ledgers including 5P or postings i
n a ledger group left blank are not yet supported. In this case, post currency adjustments either in legal ledger
s only or in the Profit Center Valuation ledger only.
The following valuation runs are not supported:
- Regroup Payables/Receivables
- Perform Further Valuations
- Perform Foreign Currency Valuation; please use the Advanced Foreign Currency Valuation run instead.
Transaction currency amounts cannot be reported according to Profit Center Valuation. The transaction curre
ncy amounts displayed are based on legal valuation. Note that this can also have implications for the balance
carryforward.
Inventory Balance Sheet Valuation cannot run for the Profit Center Valuation ledger (ledger not available in fi
lter) since inventory balance sheet valuation runs on company code level only. This behavior is intended.
Production Accounting:
Order plan costs: Order plan costs are not calculated for the Profit Center valuation view in make-to-stock sce
nario. Please refer to plan costs in the leading ledger instead.
Production across company scenario, where the production plant and planning plant are assigned to different
companies. This scenario is not supported yet after the activation of Universal Parallel Accounting (UPA). If t
he plants involved in the “production in alternative plant” process belong to different company codes, then th
e issue of raw materials or delivery of finished goods in the alternative plant will trigger goods movements tha
t are not correct from the intercompany perspective and manual adjustment postings will be required to ensu
re a compliant process. SAP reserves the right to switch this warning to an error with the delivery of a standar
d process for intercompany subcontracting. It is strongly recommended to choose a production and planning
plant that are assigned to the same company code.
Revenue and Cost Accounting:
EBRR must not be used in the Profit Center Valuation ledger. Integration between Profit Center Valuation and EBR
R is not supported with release OP2023.
Subse X Not in scope.

quent
imple
menta
tion of
a furth
er acco
unting
princi
ple
Subse X Not in scope.

quent
3191636_E_20231214 14/12/23, 8:31 PM
imple
menta
tion of
additi
onal c
urrenc
ies
(Local X If you are planning a currency changeover, note the following: You need to complete your currency changeover proj
) Curr ect before you activate the Universal Parallel Accounting business function.
ency C
hange
over
Multip X The CO, Parallel Valuation of Cost of Goods Manufactured (FIN_CO_COGM) business function is not compatible
le Valu with the Universal Parallel Accounting (FINS_PARALLEL_ACCOUNTING_BF) business function. To benefit from
ation o parallel valuation in CO, you can use the Universal Parallel Accounting business function instead.
f Cost
of Goo
ds Ma
nufact
ured
Report X In general, only the new analytical apps have been enabled for Universal Parallel Accounting, allowing them to deal
ing with several ledgers and up to ten currencies. This means that the Report Painter/Writer-based reports in Controlli
ng, for example, have not been enabled to show several ledgers and currencies. Please use the analytical apps and vi
ews provided instead. For further details, please refer to the detailed information per area below.
Profit X Organizational changes of profit center is not available with the full scope. You cannot use the Organizational Chan
Center ge tool for the reorganization of profit centers in fixed assets, in cost centers, in internal orders and WBS elements/
Reorg projects related to a fixed asset. As a consequence, the transfer of inventory and open items related to these objects
anizati is also not supported.
on
Centra X Release 2022: If universal parallel accounting is activated in your source system, all values of ledgers of type “lega
l Fina l valuation” are transferred to Central Finance. Please check note 3305495 for details for the required configuration
nce .
Activating universal parallel accounting in your Central Finance system is not part of a standard scenario and the p
otential results of doing so must be considered carefully by the project team.
As of release 2023: If universal parallel accounting is activated in your source system, all values of ledgers of typ
e “legal valuation” are transferred to Central Finance. Please check SAP Note 3305495 for details for the required c
onfiguration.
Activating universal parallel accounting in your Central Finance system is not part of the standard scenario and the
potential results of doing so must be considered carefully by the project team.
Some features are already available, such as the mapping from the old cost rates to ACCOSTRATE, but most CFIN-
specific features are not yet available for CFIN based on UPA:
Central Asset Accounting is not working with IAA.

Revaluation in CFIN is not supported.
Indus
try So
lutio
ns
Retail X
(LO-R
FM-M
3191636_E_20231214 14/12/23, 8:31 PM
D-AR
T)
Joint X JVA supports the selection of the Joint Venture expense source ledger for the JV partner reporting. The ledge
Ventur r choice only affects the ledger from which cutback (partner cost allocation and all other JVA month-end proc
e Acco esses) will take the billable expenses for the JV partner reporting. The postings which are created by the JVA
unting processes will nevertheless be made to all ledgers. In other words, JVA is not fully enabled for parallel ledgers
(JVA) in the sense that there are completely different JVA process results in the different ledgers.
In general, the venture-related costs are recorded in the different ledgers by the original finance processes (fo
r example, time writing or universal allocation). However, only one ledger value can be invoiced by JVA to the
JV partners according to the rules of the Joint Operating Agreement. For example, the hourly rate 100€ for J
V Operator’s internal engineer service is recorded in the leading ledger 0L; while the same engineer service wi
th 150€ per hour for venture-related services is recorded in the parallel ledger 2L and invoiced to the JV partn
ers by JVA into all ledgers.
Produ X FI postings created by PRA are replicated to all the ledgers. You can restrict this replication to specific ledger group
ction a s using the BAdI “/PRA/ACCUNT_DOCUMENT_POST_SIMU”.
nd Re
Note: PRA does not have any process that reads the FI-posted entries, but there is a report to show the FI documen
venue
ts created for a PRA document.
Accou
nting (
PRA)
Autom X The Advanced Planning and Optimization (APO) scenario Repetitive Manufacturing which is based on Integrated P
otive ( roduct and Process Engineering (iPPE) is not supported with UPA.
IS-A)
SAP P X Data replication to SAP Product Lifecycle Costing is not supported. With UPA, the activity rates will no longer be in
roduct table COST but in table ACCOSTRATE and the raw material prices will no longer be in table MBEW but in table F
Lifecy MLT_PRICE.
cle Cos
ting
SAP D X SAP Dairy Management is a partner application that is not integrated with universal parallel accounting.
airy M Cost estimates without quantity structure and mixed costing are not supported.
anage
ment
applic
ation b
y msg.
FI-GL (General Ledger Accounting)
Feature In Not i Additional Details

Sc n Sco
o pe/
p With
e Restr
iction
s
Parallel ledgers X For the implementation of universal parallel accounting, several parallel ledgers
can be used for different accounting principles. It is not possible to use specific
accounts for each accounting principle.
For more information on the migration of the accounts approach (also known a
s the accounts solution) to the ledger approach, see SAP Note 3042755.
3191636_E_20231214 14/12/23, 8:31 PM
Valuations per ledger X The approach of separate valuation views in separate ledgers is used.
Restriction: The approach using several valuation views within one ledger is not
supported.
Full integration of ledgers X All standard G/L ledgers are fully integrated with the FI-AA, CO, and CO-PC-M
L application components. No non-representative or reference ledgers are used.
Extensibility options (for example, u n/ n/a There are no differences compared to the solution with the Universal Parallel A
sing master data enhancement, BAd a ccounting (FINS_PARALLEL_ACCOUNTING_BF) business function inactive.
Is, APIs, CDS views)
FI-AA (Asset Accounting)
Feature In Scope Not in Scop Additional Details

e/
With Restri
ctions
Master data
Asset master data: Worklist X Only available in the 'Manage Fixed Assets' app (F34
25).
Asset master record: Create, edit, and manag X New master data concept. Functions only available i
e the master data of Asset Accounting n the 'Manage Fixed Assets' app (F3425).
Scrap values X Available in all currencies.
Insurance values X Obsolete in asset master record. You may define a sp

ecific deprecation area instead. Since no index series
are available, you need to make manual adjustment p
ostings.
Group assets X Obsolete in SAP S/4HANA.
Business area X Obsolete. Instead, you can use profit centers.
Integration with equipment master data X Not in scope.
Value display for single assets X Only available in the 'Manage Fixed Assets' app (F34
25).
Units-of-production depreciation X The new SAP Fiori app 'Maintain Number of Units fo
r UoP Depreciation‘ (F4907) replaces the previous fe
ature for units-of-production depreciation.
Evaluation groups X Obsolete. Is replaced by extensibility concept (see bel

ow).
Extensibility: Custom fields for asset master X You can enhance the asset master data with custom f
data ields using the standard extensibility tools as follows:
You cannot enhance the general data and the i

nventory data.
You can enhance the time-dependent data.
3191636_E_20231214 14/12/23, 8:31 PM
Customer-specific substitution and validatio X Not in scope.

n rules for asset master data
APIs for asset master data X New SOAP APIs for creating and changing asset mas
ter data are available (for both ordinary assets and le
gacy assets). These APIs replace the previous BAPIs.
Asset class Customizing: Chart-of-depreciati X Obsolete.

on-dependent specification of account deter
mination (table ANKP)
Asset transactions
Post Acquisition (Integrated AP) – Without X

Purchase Order (F-90)
Post Acquisition (Non-Integrated) - With Au X

tomatic Offsetting Entry (ABZON)
Post Credit Memo - In Year of Invoice (ABG X

L)
Post Credit Memo - After Year of Invoice (A X

BGF)
Post Post-Capitalization (ABNAN) X
Post Transfer - Within Company Code (ABU X

MN)
Post Transfer - Across Company Codes (ABT X Limited depreciation area mapping capabilities.
1N)
Post Retirement (Integrated AR) – With Cus X You cannot post an asset retirement for several asset
tomer (F-92) subnumbers by entering an asterisk for the subnumb
ers.
Post Retirement (Non-Integrated) – Withou X

t Customer (ABAON)
Post Retirement – By Scrapping (ABAVN) X
Post Depreciation Manually – Unplanned an X Manual depreciation is directly posted to the corresp
d Planned (ABAA) onding account in the general ledger.
Post Writeup (ABZU) X Writeups are directly posted to the corresponding ac

count in the general ledger.
Post Asset Revaluation (ABAWL) X An asset revaluation is directly posted to the corresp
onding account in the general ledger.
Revaluations are supported in all depreciation areas
except for pure revaluation depreciation areas (see in
flation management).
Impairment with AR29N, RAAUFW02 X Not in scope. Instead, you can make manual revaluat
ion postings using ABAWL.
3191636_E_20231214 14/12/23, 8:31 PM
Journal entries in universal journal X
Post Quantity - Adjustment (ABQAL) X Postings with quantities are possible in all ledgers. Y
ou can also make ledger-specific adjustment postings
for quantities.
Interest calculation and posting X Not in scope.
Vendor down payment to asset: Posting and X Obsolete. Instead, you can use CO objects such as W
capitalization of down payment to asset BS elements and then execute an AuC settlement if n
ecessary.
Functional currency X Used as the primary working currency of an or

ganization
Can be the company code currency, the group c
urrency, or a currency that differs from these c
urrencies
Available for value display of single assets, asse
t postings, and reporting
Default for asset postings: The currency is pres
et either to the functional currency (provided t
hat it has been defined) or to the local company
code currency. If a functional currency is not u
niquely defined for all ledgers within a compan
y code, the system presets the company code cu
rrency as the default.
Support of G/L currencies X Not only three currencies are supported but all G/L c
urrencies.
BAdI 'Customer-Specific Change of Line Ite X Due to the changed posting document structure, you
ms in Asset Document' (FAA_DOCLINES_C must replace implementations of the previous metho
USTOMER) d CHANGE_DOCUMENT with a new implementatio
n of CHANGE_DOCUMENT_UPA. For the relevant
correction instructions, see SAP Note 3243881.
BAPIs for asset postings X The previous BAPIs for asset postings (for example,
BAPI_ASSET_ACQUISITION_POST, BAPI_ASSET
_TRANSFER_POST, BAPI_ASSET_VALUE_ADJU
ST_POST) are obsolete.
Account assignment Customizing: Assignme X The previous Customizing in transaction ACSET is o

nt of account assignment types for APC and bsolete. However, the new Asset Accounting Customi
depreciation to account assignment objects zing provides a more consistent and flexible approac
h: The account assignment types are portrayed using
the asset transaction type.
Assets under construction (AuC)
Assets under construction based on WBS ele X Assets under construction based on WBS elements ar
ments e in scope. For internal orders, see the section for IM
(Investment Management) below.
Summary settlements are supported.
Down payments are supported.
3191636_E_20231214 14/12/23, 8:31 PM
Independent assets under construction (incl. X Obsolete. You can use WBS elements instead.
creation of settlement rules)
Reporting
Asset History Sheet (F1615) X Some fields are obsolete but still visible. Examples:
Evaluation group fields are obsolete; use extens

ibility tools instead. See also the entries “Evalu
ation groups” and “Extensibility: Custom fields
for asset master data” above.
Group assets are obsolete.
Asset Balances (F1617) X The same applies to the Asset History Sheet (F1615).
Asset Transactions (F1614) X
Depreciation Lists (F1616) X
Asset Accounting Overview (F3096) X
Asset reports with ALV X Obsolete. Asset reports with ALV (for example: RAGI
TT_ALV01, RABEST_ALV01) are obsolete. They are
replaced by the SAP Fiori apps listed above.
Logical database ADA X Obsolete. The logical database ADA and the reports b
ased on it are obsolete. Use SAP Fiori analytical apps
instead or create your own.
Depreciation forecast (reporting for future fi X Depreciation forecast is in scope. Reporting for futur
scal years) e fiscal years is limited to a planning horizon of a ma
ximum of 5 years.
The new feature replaces the previous depreciation si
mulation (RASIMU_ALV01).
Integrated cost planning X Integrated cost planning (for example, with RAKOPL
02) is not in scope.
BW extraction X Not in scope.
Legacy Data Transfer
Manual legacy data transfer (for master data X

and postings)
Automatic legacy data transfer (for master d X

ata and postings) using the SAP S/4HANA
migration cockpit
Parallel accounting and valuation
Single valuation ledger X Asset Accounting now supports the assignment of an

accounting principle to several representative ledger
s. Furthermore, it is no longer mandatory that the lo
cal currency must be managed with currency type 10.
3191636_E_20231214 14/12/23, 8:31 PM
Group valuation ledger X Asset-specific postings to this ledger type are support
ed.
Alternative fiscal year variant X See also section 'General Finance Features' above.
Inflation accounting X Not in scope.
Depreciation area posting depreciation only X Obsolete. Depreciation area with posting option 3 ('A
rea Posts Depreciation Only') is no longer supported.
Foreign currency areas X Obsolete. No longer required due to new concept for
parallel accounting and currencies.
Other
Predefined standard delivery Customizing fo X The previous standard Customizing is not adjusted t
r Asset Accounting in SAP S/4HANA on pre o Universal Parallel Accounting. Check which parts o
mise f the previous standard Customizing you still want to
use (for example, individual depreciation keys).
Workflow: Incomplete assets X Obsolete. Use worklist in ‘Manage Fixed Assets’ app i
nstead.
Workflows for other use cases, for example, f X Not in scope. For mass changes, use SOAP APIs for a
or asset mass changes, impairment. sset master data instead.
View authorization (ANSICHT) X Obsolete.
Subsequent introduction of a new depreciati X Not in scope.

on area
Reorganisation/organizational change X To reflect organizational changes, you need to chang

e individual asset master records manually.
Transferred reserves X Not in scope.
Net worth tax X Obsolete.
Integration with purchase orders X You cannot create an asset within a purchase or
der. Instead, you create the asset in a separate s
tep.
In purchase orders, the account assignment to
an asset is only allowed in fiscal years that were
opened by the balance carryforward.
In both cases, we recommend that you create a WBS

element.
Investment support X Not in scope.
Mid-month convention X To fulfill the requirements of the mid-month convent

ion, there is a period control with 24 real calculation
periods.
3191636_E_20231214 14/12/23, 8:31 PM
Integration with Flexible Real Estate Manag X Not in scope. Exception: Leasing (Contract and Leas
ement (RE-FX) e Management) is in scope.
Integration with Joint Venture Accounting ( X Asset Accounting does not support the JVA recovery
JVA) indicator (field RECID):
The recovery indicator cannot be used in any of

the Asset Accounting posting apps.
The recovery indicator is not displayed in any A
sset Accounting report.
There is no posting amount control by the reco
very indicator.
Integration with Public Sector X Not in scope.
Integration with Group Reporting X Integration has changed. See the detailed informatio
n.
Extensibility options (for example, using ma n/a n/a See the detailed entries above (for example, “Extensi
ster data enhancement, BAdIs, APIs, CDS vi bility: Custom fields for asset master data”, “APIs for
ews) asset master data”).
CO-OM (Overhead Cost Controlling)

e/
With Restri
ctions
Master data
Business processes X Activity-based costing (ABC) isn't supported.
Activity types X Features such as indirect activity allocation, predistri

bution of fixed costs, and the differentiation of alloca
tion default values for the combination of cost center
/activity type aren't supported.
Planning
Planning X As of release 2023:

Classic planning transactions for cost centers, project
s and internal orders aren't supported any longer.
Use SAP Analytics Cloud (SAC) for your planningacti

vities instead.
Classic budgeting transactions and classic availabilit

y control are supported for internal orders and proje
cts.
Classic commitments for cost centers, projects and in
ternal orders are supported.
Plan data is stored in table ACDOCP.
Use new planning apps, such as:
3191636_E_20231214 14/12/23, 8:31 PM
Import Financial Plan Data (F1711)

Fiori reporting app:
Commitments by Cost Center - Classic Commit

ment Management (F4998)
Actual Postings
Direct activity allocation X Cost Rates (table COST will be replaced with ACCOS
TRATE).
Service cost rates are also stored in table ACCOSTRA
TE. The SD condition technique isn't used any longer
.
Use new apps, such as:
Manage Direct Activity Allocation (F3697)
Cost rate maintenance X Ledger-specific cost rates can be maintained.
You can use the following apps:

Manage Cost Rates - Plan (F3162)
Manage Cost Rates - Service (F3161) (only avail
able if business function Intercompany Process
Enhancements 1 (FINS_CO_ICO_PROC_ENH
_101) is active)
Manage Cost Rates - Actual (F3422)
Display Cost Rates (F5150)
Indirect activity allocation X Not in scope.
Group valuation X Note that the intercompany margin isn't posted in in

tercompany activity allocations.
Period-end closing
Actual price calculation (KSII) X Actual price calculation only comes with a reduced sc
ope.
Use new apps, e.g.
Schedule Overhead Accounting Jobs (F3767)
Plan price calculation (KSPI) X Plan price calculation isn't supported any longer. Use
SAP Analytics Cloud (SAC) for your planning activiti
es instead. For more information, see the Financial P
lanning section.
Universal allocation X Only universal allocation can be used. Classic allocati

on and distribution aren't supported any longer (tran
sactions KSV* and KSU* are blocked).
Use new universal allocation apps, such as:
Manage Allocations (F3338)

Run Allocations (F3548)
Overhead calculation X Use new overhead calculation apps, such as:

Run Overhead Calculation (F4857)
Postprocess Event-Based Postings - Overhead
3191636_E_20231214 14/12/23, 8:31 PM
Calculation (F5763)
Schedule Overhead Accounting Jobs (F3767)
Distribution (KSV*) X Not in scope.
Use universal allocation instead.
Assessment (KSU*) X Not in scope.

Settlement X Only settlements to CO object, profitability segment,

asset, and G/L account are supported.
Classic settlement to material (WIP, variances, actual
costs) isn't supported with UPA, please use the event
-based production cost posting solution in CO-PC-O
BJ-ORD instead.
Classic settlement to results analysis data isn't suppo
rted with UPA. Please use event-based revenue recog
nition solution in CO-PC-OBJ-EBR instead.
Ledger-specific settlement rules are available and set

tlement can be carried out per ledger.
Use new settlement apps, such as:
Run Actual Settlement (F4568)

Display Settlement Documents (F4597)
CO repostings X Use 'Reassign Cost and Revenues (F2009)' app for re

postings. Note that the app isn't ledger-enabled.
Activity allocation reposting and line item reposting
are not in scope.
Reporting New analytical apps meet the reporting demands of

Universal Parallel Accounting. You can report by led
ger and additional currencies in the following reports
.
Multidimensional reports X Cost Centers – Plan/Actual (Fiori ID: W0081,

CDS view: C_COSTCENTERPLANACTQ2001)
Functional Areas – Plan/Actual (Fiori ID: F158
4, CDS view: C_FUNCTIONALAREAPLANACT
Q2801)
Internal Orders – Plan/Actuals (Fiori ID: F094
8, CDS view: C_INTERNALORDERPLANACT
Q2101)
P&L - Plan/Actual (Fiori ID: F1710; CDS view:
C_PROFITANDLOSSPLANACTQ2903)
Projects - Plan/Actuals (Fiori ID: W0080; CDS
view: C_PROJECTPLANACTQ2201)
Financial Plan Data (Fiori ID: W0163; CDS vie
w: C_GENERICPLANQ3001)
Cost Centers – Actuals (Fiori ID: F0963, CDS v
iew: C_COSTCENTERQ2001)
Functional Areas – Actuals (Fiori ID: F1583; C
DS view: C_FUNCTIONALAREASQ2801)
P&L – Actuals (Fiori ID: 0958; CDS view: C_P
ROFITANDLOSSQ2901)
Projects – Actuals (Fiori ID: F0961; CDS view:
3191636_E_20231214 14/12/23, 8:31 PM
C_PROJECTQ2201)
Line Item Reporting X Display Line Items – Cost Accounting (F4023)
Extensibility
Extensibility options (for example, using ma X Enhancements for classic GUI or Web Dynpro transa
ster data enhancement, BAdIs, APIs, CDS vi ctions are not supported any longer. Fiori apps can o
ews) nly be enhanced using key user extensibility.
The following APIs are supported:

COSTCENTREREPLICATIONBULKRQ
CO_COST_CENTRE_REPLICATION_OUT
COSTCENTREGROUPHIERARCHYREPLRQ
CO_COST_CENTRE_GROUP_HIERAR
ALLOCATIONPOSTINGCREATEREQUEST
API_COSTCENTER_SRV_0001
API_COSTCENTERACTIVITYTYPE_SRV_00
01
API_STATISTICALKEYFIGURE_SRV_0001
The following CDS views are supported with restricti
ons. See section ‘Master Data’ for further details.
I_CostCenter
I_CostCenterText
I_CostCenterStdVH
I_CostCenterCategory
I_CostCtrActytypeCostCtrCat
I_CostCenterActivityTypeCatT
I_CostCenterActivityType
I_CostCenterActivityTypeText
I_STATISTICALKEYFIGURE
I_StatisticalKeyFigureText
I_StatisticalKeyFigureCat
I_StatisticalKeyFigureCatText
I_InternalOrder
IM (Investment Management)

e/
With restric
tions
Master data
Projects as investment measures X
Internal orders as investment measures X With restrictions, such as no Fiori apps available.
Appropriation requests and investment prog X Reporting on planning/budgeting for investment pro
rams grams is not supported.
Line item settlement X Line item settlement is not supported for parallel led
gers.
3191636_E_20231214 14/12/23, 8:31 PM
This means that investment profiles for which line it

em settlement and the settlement of parallel ledgers
are set cannot be used with UPA.
Plant maintenance orders as investment me X Not in scope.

asures
Investment measures with line-item settlem X As of release 2023:

ent
Open investment measures with line-item settlement
need to be manually closed. Existing settlement profi
les need to be changed to “No line-item settlement”.
Capitalization keys X Capitalization keys aren't supported any longer. Use l

edger-specific settlement rules instead. For more inf
ormation, see the Overhead Cost Controlling section
above.
Planning
Planning X Classic planning transactions aren't supported for In

vestment Management.
CO-PA (Profitability Analysis)

e/
With Restri
ctions
Margin Analysis X
Universal allocation X
Settlement to profitability segment X
Top-down distribution (universal allocation) X
COGS split X COGS split is supported also for ledger-specific cost e

stimates.
Cost center assessment X The transfer of cost center costs using transactions, s
uch as KEU1/KEU2/KEU5, is not supported.
Use Universal Allocation instead.
Indirect activity allocation X Indirect activity allocation using transactions, such a

s KEG1/KEG2/KEG5, is not supported.
Top-down distribution X Top-down distribution using transactions, such as K

E28/KE28A, is not supported.
Planning X Classic planning transactions, such as transaction KE

PM, aren't supported any longer. Use SAP Analytics
Cloud (SAC) for your planning activities instead. Pla
n data is stored in table ACDOCP.
3191636_E_20231214 14/12/23, 8:31 PM
Costing-Based Profitability Analysis X Not in scope.

Use margin analysis instead.
Combined Profitability Analysis X Not in scope.
Use margin analysis instead.
Extensibility options (for example, using ma n/a n/a There are no differences compared to the solution wi
ster data enhancement, BAdIs, APIs, CDS vi th the Universal Parallel Accounting (FINS_PARALL
ews) EL_ACCOUNTING_BF) business function inactive.
CO-PC-PCP (Product Cost Planning)
Feature In Not in Additional Details

Sc Scope
o /
pe With
Restri
ctions
Cost estimates Also available in Fiori app Manage Costing Runs - Estimated Costs (F1865).
Cost estimates can be created per ledger.
Material cost estimates are still calculated and stored in the controlling area c
urrency and object currency. When releasing the cost estimate, they are transl
ated into additional currencies.
Make to stock material cost estimate X
Make to order material cost estimate X
Preliminary cost estimate X Can only be created for the leading ledger.
Cost estimate with quantity structure X
Cost estimate without quantity struct X Not in scope.

ure
Additive costs X
Price marking and release X Price marking and release can be done using one costing variant per company
code, ledger, and period.
Production lot cost estimate X
Easy cost planning X Not in scope.
Mixed costing X Not in scope.
Analysis
Costing run analysis X Available transactions/apps:

Results of Costing Run (S_ALR_87099930)
Price vs Cost Estimate (S_ALR_87099931)
3191636_E_20231214 14/12/23, 8:31 PM
Variances Between Costing Runs (S_ALR_87099932)
Reporting
Detailed reports for material X Not in scope:
Costed Multilevel BOM

Cost Components
Partner Cost Component Split
Cost Elements
Detailed reports for sales-order cost e X Not in scope.

stimate and order BOM cost estimate
Reports for product cost by sales orde X Not in scope:

r
Sales Order Hierarchy Display
Display Sales Order Item to be Costed
Sales Order Selection
Analyze Sales Order
Extensibility
Extensibility options (for example, usi X Supported APIs:

ng master data enhancement, BAdIs,
API_MATERIAL_VALUATION_SRV (Material Price - Update)
APIs, CDS views)
Supported CDS views:
I_CostingOverheadGroup (Costing Overhead Group)

I_CostingType (Costing Type)
I_CostingValuationVariant (Costing Valuation Variant)
I_CostingVariant (Costing Variant)
I_CostingVersion (Costing Version)
I_CurrentMatlValnPriceDEX (Current Material Valuation Price for Extr
action)
I_InventoryPriceByKeyDate (Inventory Price by Key Date)
I_MaterialCostEstCostingRunDEX (Material Cost Estimate Costing Ru
n)
I_MaterialValuationDEX (Material Valuation for Extraction)
I_ProductCostEstimate (Product Cost Estimate)
I_ProductCostEstimateDEX (Product Cost Estimate (Data Extraction))
I_ProductCostEstimateErrorLog (Product Cost Estimate Error Log)
I_ProductCostEstimateItem (Product Cost Estimate Item)
I_ProductCostEstimateItemDEX (Product Cost Estimate Item (Data Ex
traction)
BAPIs for Product Cost Controlling X The following BAPIs are not supported:
BAPI_MATVAL_DEBIT_CREDIT
BAPI_MATVAL_PRICE_CHANGE
BAPI_SALESORDSTCK_DEBIT_CREDIT
BAPI_SALESORDSTCK_PRICE_CHANGE
BAPI_PROJECTSTOCK_DEBIT_CREDIT
BAPI_PROJECTSTOCK_PRICE_CHANGE
CO-PC-ACT (Actual Costing)
Feature Additional Details
3191636_E_20231214 14/12/23, 8:31 PM
I Not
n in S
S cop
c e/
o Wit
p h Re
e stric
tion
s
Actual costing run X Available ledger run types:

Single period run
Year-to-date run
Material Value Flow Monitor X

(ML4HVFM)
Cost components for price X
Display actual cost componen X

t splits
Material price analysis X
Activity Consumption Analysi X

s
Edit procurement alternative X

s and consumption alternativ
es
Distribution of usage varianc X Available transactions/apps:

es
Distribution of Activity Differences (CKMDUVACT)
Distribution of Inventory Differences (CKMDUVMAT)
Enter Actual Activity Quantities (CKMDUVREC)
Display Inventory and Activity Differences (CKMDUVSHOW)
Detailed Reports X Not in scope:
Material Prices and Inventory Values Over Several Periods

Transaction History for Material
Valuated Multilevel Quantity Structure
Display of WIP for Actual Costs
WIP Quantity Document
Business function Multiple V X You cannot activate the business functions for universal parallel accounting (FINS_PAR
aluation of Cost of Goods Ma ALLEL_ACCOUNTING_BF) and parallel valuation of costs of goods manufactured (FIN
nufactured (FIN_CO_COGM _CO_COGM) concurrently in your system. You must decide which feature you want to us
) e.
Extensibility options (for exa X See section CO-PC-PCP.

mple, using master data enha
ncement, BAdIs, APIs, CDS vi
ews)
3191636_E_20231214 14/12/23, 8:31 PM
CO-PC-ML (Material Subledger)
Feature In Sc Not in Sco Additional Details

ope pe/
With Restr
ictions
Manage Material Valuations (F2680) X
Price maintenance X Available transactions/apps:
Debit/Credit Inventory Values (MR22

)
Enter Future Prices (CKMPRPN)
Release Planned Prices (CKME)
Change Material Prices (MR21)
Manual Change of Actual Cost Compo
nent Splits (CKMCCC)
Upload Material Inventory Prices (F4
006)
Manage Material Valuations (F2680)
Statistical moving average price X
Valuated special stock X Supported special stock types:
Valuated project stock

Valuated sales order stock
Valuated transport stock
Valuated subcontracting stock
Price change document X
Split valuation X
Extensibility options (for example, using master data enhance X See section CO-PC-PCP.
ment, BAdIs, APIs, CDS views)
MM-IM-VP (Inventory Balance Sheet Valuation)

Sc Scope/
op With R
e estricti
ons
Inventory Balance Sheet Valuations (F334 X

3)
Determination of lowest value X Supported valuation procedures:
Lowest value determination based on market prices (in release

2022 enabled for the leading ledger only); as of release 2023 e
nabled for all ledgers
Lowest value determination by range of coverage (enabled for

all ledgers)
Lowest value determination by movement rate (enabled for all
ledgers)
Not in scope:
3191636_E_20231214 14/12/23, 8:31 PM
Loss-free valuation
FIFO valuation X Inventory price can only be processed for the leading ledger.
LIFO valuation X Not in scope.
Adjustment of inventory balance sheet acc X Available transactions/apps:

ounts
Adjust Inventory Balance Sheet Accounts - Delta Posting (MRND)
Adjust Inventory Balance Sheet Accounts - Price Change (MRNP)
Replacement cost valuation (inflation) X Not in scope.
Extensibility options (for example, using X See section CO-PC-PCP.

master data enhancement, BAdIs, APIs, C
DS views)
CO-PC-OBJ (Cost Object Controlling/Production Accounting)
Feature In S Not in Sc Additional Details

cop ope/
e With Rest
rictions
Production Costs Posting Solution
Event-based production cost posting X Find supported scenarios and limitations of this solution in SAP Note 3315659.
Classic period-based production cost p X Classic period-based order cannot be created.

osting
Classic period-based period-end activites like WIP calculation (KKAX/KKAO),
KKS5) and settlement (KO88/CO88/CO8A/CO8B) cannot be used.
Production Scenario
Product cost by order X Normal products with both S price and V price are supported
Co-product used in joint production scenario is supported (distribution ru
Settlement to a non-MAT receiver (cost center, WBS element and manufa
Product cost by period See Additional Det Release 2022:

ails column. Not in scope. Neither product cost collector used in repetitive manufacturing n
with periodic settlement are supported.
As of release 2023:
Product cost collectors used in repetitive manufacturing are supported
Production orders and process orders with periodic settlement are not su
Product cost by sales order (valuated s X Production orders and process orders are supported. The order receiver should
ales order stock) order is the cost carrier. Account assignment is 'EO' (Profitability).
Product cost collectors are not supported.
Product cost by sales order (non-valuat X

ed sales order stock)
Engineering-to-order (valuated project X

stock)
Engineering-to-order (non-valuated pr X
3191636_E_20231214 14/12/23, 8:31 PM
oject stock)
Cost Object
Production order X
Process order X
Product cost collector (repetitive manu See Additional Det Release 2022: Not in scope.
facturing) ails column.
As of release 2023: Product cost collectors are supported in cost object contr
he following production scenarios:
Product cost collectors with settlement receivers that have a mixed usage
ceivers
Manufacturing orders assigned to product cost collectors
Make-to-order (MTO) production with valuated sales order stock
Engineer-to-order (ETO) production with valuated project stock

Product material with valuation split
Production across companies (with warning message)
CO production order X
Extensibility
Published API X Below query view supports parallel ledger valuation
I_MfgOrderActlPlanTgtLdgrCost
C_MfgOrdActlPlnTgtLdgrCost
I_MfgOrderEvtBsdWIPVariance
C_MfgOrderEvtBsdWIPVarcQry
BADIs, User exits X Existing BADIs or user exits for classic period-based order production cost pos
ledger valuation, for example BADI CO_ML_WIP.
Reporting
Analyze Costs by Work Center/Operati X Only production orders, and process orders, and product cost collectors runnin
on (F3331) posting solution are have parallel accounting capability.
Find a detailed introduction of F3331 and its restrictions in SAP Note 3316297
Display Line Items - Production Accou X New app as of release 2023: Only production orders, process orders, and produ
nting (F7288) t-based production cost posting solution have parallel accounting capability.
Production Accounting Overview - Eve X App name in relase 2022: Event-Based Production Accounting Overview
nt-Based (F6248)
App name as of release 2023: Production Accounting Overview - Event Based.
Posting Rules - Event-Based (F5228) X App name in release 2022: Event-Based Posting Rules
App name as of release 2023: Display Posting Rules - Event Based
Production Costs - Event-Based (F405 X App name in release 2022: Event-Based Production Costs
9)
App name as of release 2023: Analyze Production Costs - Event-Based
Order Cost Details - Event-Based (F42 X App name in release 2022: Event-Based Order Cost Details
54)
App name as of release 2023: Analyze Production Costs - Event-Based
3191636_E_20231214 14/12/23, 8:31 PM
Product Cost Collector Details - Event- New app as of release 2023

Based (F6965)
Order Exception Monitor - Event-Base X App name in release 2022: Event-Based Solution Monitor
d (F5133)
App name as of release 2023: Order Exception Monitor - Event-Based
Manage Event-Based Posting Errors - X

Product Costing (F5132)
Postprocess Event-Based Postings - Pr X

oduct Costing (F3669)
Postprocess Event-Based Postings - Ov X

erhead Calculation (F5763)
Schedule Product Costing Jobs (F3683 X Available job templates:

)
Postprocess Event-Based Posting - Product Costing
Postprocess Event-Based Posting - Overhead Calculation
Event-Based Posting – WIP Quantity Posting for Actual Costing Revaluat
Production Cost Analysis (F1780) X
Analyze Summarization Hierarchy (KK X

BC_HOE_H)
Select Orders (S_ALR_87013127) X
Analyze Order (KKBC_ORD) X
Analyze Product Cost Collectors (KKB X

C_PKO)
CO-PC-OBJ-EBR (Event-Based Revenue Recognition)

Sc Scope/
op With R
e estricti
ons
Integration scenarios: X
- Sell from stock (Event-Based

Revenue Recognition for Sales
Orders)
- Project system (Event-Based R

evenue Recognition for Projects
)
Revenue recognition methods X For integration with the project system, you can use the following revenue recogni
tion methods with universal parallel accounting:
Recognize revenue on cost-based POC (method 3)

Recognize costs on revenue-based POC (method 7)
Recognize revenue time-based (method 10)
Recognize all costs and revenues (method 2)
Completed contract: recognition at final billing/technical completion (meth
od 9)
3191636_E_20231214 14/12/23, 8:31 PM
For the integration with sell from stock, you can use the following revenue recogni
tion methods with universal parallel accounting:
Recognize costs on revenue-based POC (method 7)

Recognize revenue on delivery-related invoice simulation (method 14)
Completed contract: recognition at final billing/technical completion (meth
od 9)
Recognize all costs and revenues (method 2)
For these methods, universal parallel accounting for Event-Based Revenue Recog
nition is supported during real-time processing and period-end closing.
The cost-based and revenue-based POC methods (method 3 & 7) have specifics th
at need to be kept in mind.
To learn more about which methods have been adapted for Universal Parallel Acc
ounting, see Specifics of Revenue Recognition Methods with Parallel Accounting.
Revenue recognition method: ti X Parallel accounting for the revenue recognition method "Recognize revenue on ti
me & expense-based invoice sim me & expense-based invoice simulation (method 4)" is only supported during peri
ulation od-end closing.
Imminent loss X
Plan data import from ECC clas X When you have activated universal parallel accounting, you have to import plan d
sic planning ata from ACDOCP. For more information, please see the Financial Planning sectio
n.
Results Analysis X Results Analysis is not supported with universal parallel accounting. Use Event-B
ased Revenue Recognition instead.
To learn more about Event-Based Revenue Recognition in general and which features are supported for SAP S/4HANA 2022,
see the Release Information Note 3220122.
CO-FIO-OM (Financial Planning)
Feature In Not i Additional Details

S n Sco
co pe/
p With
e Restr
iction
s
SAP Analytics Cloud x Integration with tables ACDOCP, FINSSKF (statistical key figures), and ACCOSTRATE (pri
ces)
Transfer programs x The following transfer program is not supported:
Transfer CO plan data from SAP ERP (CO-tables) to SAP S/4HANA (ACDOCP) (R_FINS_
PLAN_TRANS_CO_ERP_2_S4H)
Classic planning transact x

ions
SAP Business Planning x Restrictions: For example, the tables FINSSKF and ACCOSTRATE are not used here, only t
& Consolidation (BPC) f able ACDOCP or, alternatively, an info provider. The planning functions for the transfer to t
or SAP S/4HANA he classic planning tables are also not available.
In general, SAP’s strategy is to use SAP Analytics Cloud for financial planning.
3191636_E_20231214 14/12/23, 8:31 PM
The financial planning functions within SAP Analytics Cloud and for the integration between SAP Analytics Cloud and SAP
S/4HANA also work in the context of universal parallel accounting. In addition to planning table ACDOCP, tables FINSSKF
(statistical key figures) and ACCOSTRATE (prices), which are important for universal parallel accounting, also have read and
write access.
Note that the classic planning transactions, for example in overhead accounting and margin analysis, are no longer available
in connection with universal parallel accounting. The transfer programs that enable a transfer between classic planning tables
and the new tables mentioned above are also not available.
You can continue to use SAP Business Planning & Consolidation (BPC) for SAP S/4HANA even if universal parallel
accounting is used. However, there are restrictions for this. For example, the above-mentioned tables FINSSKF and
ACCOSTRATE are not used here, only table ACDOCP or, alternatively, an info provider. The planning functions for the
transfer to the classic planning tables are also not available.
RE-FX (Flexible Real Estate Management)
Leasing is available in combination with universal parallel accounting, specifically Intelligent Asset Accounting (see
section FI-AA (Asset Accounting)). Flexible Real Estate Management as well as Intelligent Real Estate can also be active
in combination with universal parallel accounting. However, please consider that real estate account assignment objects, such
as business entity, are not supported in Overhead Accounting processes such as settlement or allocation if universal parallel
accounting is active.
MM-SRV (Services Management)
Feature I Not in Sco Additional Details

n pe/With R
S estrictions
c
o
p
e
External x Item categories D – Service (replaced by “ “ – Standard) and B – Limit (replaced by E – Enhanced Li
Service Pr mit) are not available. Instead, a new field called Product Type Group has been introduced for the lin
ocuremen e item in the contract, purchase requisition and purchase order.
t
Service requisitions or service orders that use the standard item category are mapped at the line-item
level, differentiating as services using Product Type Group – 2.
The successor of Classic External Service Management (MM-SRV*) is SAP S/4HANA Service Procur
ement called Lean Service / Enhanced Limits.
The transition of External Service Management to Service Procurement is described in SAP Note 313
2075.
Settlement process in Transportation Management is not integrated with Lean Service Procurement
(see SAP Note 2660326).
Country/Region-Specific Features
Applica Feature C I Not i Additional Details

tion Co o n n Sc
mpone u S ope/
nt n c With
tr o Rest
y/ p ricti
R e ons
e
gi
o
n
Release 2022: Not in scope.
3191636_E_20231214 14/12/23, 8:31 PM
FI-LOC- Pro-Rata adjustments using the program RFID_PTVPRADPRC00 (Pro F See Additi As of release 2023: Both p
RAT (VA -Rata adjustments due to PR calculation) or the program RFID_PTVPR R, onal Detai ro-rata reports are available f
T Pro Ra ADPRV00 (Pro-Rata adjustments due to PR variation) R ls column. or the indicated countries.
ta) O
For more information about the Universal Parallel Accounting business function, see Universal Parallel
Accounting.
Attributes
Key Value
Other Components CO-OM (Overhead Cost Controlling)
Other Components CO-PC-ML (Material Subledger)
Other Components CO-PC-OBJ-ORD (Product Cost by Order)
Other Components IM (Investment Management)
Other Components FI-AA (Asset Accounting)
Other Components CO-PA (Profitability Analysis)
Other Components CO-PC-OBJ-EBR (Event-Based Revenue Recognition)
Other Components FI-GL-OC (Organizational Changes in Accounting for PC and Segment)
Other Components MM-SRV (Services Management)
Other Components CO-PC-OBJ (Cost Object Controlling)
Other Components CO-PC-PCP (Product Cost Planning)
Other Components RE-FX (Flexible Real Estate Management)
Other Components MM-IM-VP (Balance Sheet Valuation Procedures)
Other Components CO-PC-ACT (Actual Costing)
Software Components
Software Component From To And subsequent
S4CORE 107 107
This document refers to

SAP Component Title
Note/KBA
3207925 CO-PC-OBJ SAP S/4HANA 2022: Business Catalogs and Tiles for Production Accounting with/without Universal
Parallel Accounting
3206444 CO-PA Business Catalogs and Tiles for Sales Accounting with/without Universal Parallel Accounting
3205432 CO-PC Business Catalogs and Tiles for Inventory Accounting with/without Universal Parallel Accounting
3198793 CO-OM Business Catalogs and Tiles for Overhead Accounting with/without Universal Parallel Accounting
3191517 FI-AA Business Catalogs and Tiles for Asset Accounting with/without Universal Parallel Accounting
3191636_E_20231214 14/12/23, 8:31 PM
This document is referenced by

SAP Component Title
Note/KBA
3327778 Migration to Universal Parallel Accounting (SAP S/4HANA 2023): Scope Information
3302551 FI-LOC-RAT VAT Pro-Rata: Adaptation for Asset Accounting within Universal Parallel Accounting
3353050 XX-PART- Usage of SAP S/4HANA Public Cloud integration for SAP Account Substantiation and Automation by
BKL BlackLine with Universal Parallel Accounting
3346736 XX-PART- Usage of SAP S/4HANA integration for SAP Account Substantiation and Automation by BlackLine & SAP
BKL Intercompany Governance by BlackLine with Universal Parallel Accounting
3232317 FI-LOC-AA- Restrictions and limitations of FI-AA functionality RU, UA, KZ: Universal Parallel Accounting - SAP
RU S/4HANA 2022
3207464 CO-PC-OBJ SAP S/4HANA 2022: Universal Parallel Accounting for Event-Based Production Accounting
3207925 CO-PC-OBJ SAP S/4HANA 2022: Business Catalogs and Tiles for Production Accounting with/without Universal
Parallel Accounting
3212130 FI-LOC-FI- Revaluation of Fixed Assets for Romania: Not Supported in Universal Parallel Accounting - SAP S/4HANA
RO 2022

Universal Parallel Accounting: Scope Information: Symptom

Uploaded by

Document Information

Original Description:

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

Universal Parallel Accounting: Scope Information: Symptom

Uploaded by

Copyright:

Available Formats

3191636_E_20231214 14/12/23, 8:31 PM

3191636 - Universal Parallel Accounting: Scope Information

Reason and Prerequisites

Affected application components:

Scen Release 2022 Release 2023

Req FINS_PARALLEL_ACCOUNTING_BF ( FINS_UPA_MIGRATION (Universal Parallel Accounting Migration);

r the business function activation. To do t

Scope information (including main restrictions)

Featu I N Additional Details

Altern X Enhanced procedure of adding an alternative fiscal year variant.

Shorte X Not in scope.

Profit See A Release 2022: Not in scope.

colum General considerations:

Revenue and Cost Accounting:

Subse X Not in scope.

Subse X Not in scope.

Central Asset Accounting is not working with IAA.

FI-GL (General Ledger Accounting)

Feature In Not i Additional Details

FI-AA (Asset Accounting)

Feature In Scope Not in Scop Additional Details

Scrap values X Available in all currencies.

Insurance values X Obsolete in asset master record. You may define a sp

Group assets X Obsolete in SAP S/4HANA.

Business area X Obsolete. Instead, you can use profit centers.

Integration with equipment master data X Not in scope.

Evaluation groups X Obsolete. Is replaced by extensibility concept (see bel

You cannot enhance the general data and the i

Customer-specific substitution and validatio X Not in scope.

Asset class Customizing: Chart-of-depreciati X Obsolete.

Post Acquisition (Integrated AP) – Without X

Post Acquisition (Non-Integrated) - With Au X

Post Credit Memo - In Year of Invoice (ABG X

Post Credit Memo - After Year of Invoice (A X

Post Post-Capitalization (ABNAN) X

Post Transfer - Within Company Code (ABU X

Post Retirement (Non-Integrated) – Withou X

Post Retirement – By Scrapping (ABAVN) X

Post Writeup (ABZU) X Writeups are directly posted to the corresponding ac

Journal entries in universal journal X

Interest calculation and posting X Not in scope.

Functional currency X Used as the primary working currency of an or

Account assignment Customizing: Assignme X The previous Customizing in transaction ACSET is o

Assets under construction (AuC)

Summary settlements are supported.

Down payments are supported.

Evaluation group fields are obsolete; use extens

Asset Transactions (F1614) X

Depreciation Lists (F1616) X

Asset Accounting Overview (F3096) X

BW extraction X Not in scope.

Legacy Data Transfer

Manual legacy data transfer (for master data X

Automatic legacy data transfer (for master d X

Parallel accounting and valuation

Single valuation ledger X Asset Accounting now supports the assignment of an

Inflation accounting X Not in scope.

View authorization (ANSICHT) X Obsolete.

Subsequent introduction of a new depreciati X Not in scope.

Reorganisation/organizational change X To reflect organizational changes, you need to chang

Transferred reserves X Not in scope.

Net worth tax X Obsolete.