8/16/2024

Asset Accounting
Generated on: 2024-08-16 11:02:31 GMT+0000

SAP S/4HANA Cloud | 2408 Latest

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_CLOUD/3e5fcf2c768746049b5627bd5a42f720?locale=en-

US&state=PRODUCTION&version=2408.500

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 8/16/2024

Asset Accounting

Use
You use Asset Accounting to manage and monitor tangible xed assets. It provides detailed information about the transactions
relating to tangible xed assets.

Implementation Considerations
To be able to use Asset Accounting, you have to also use General Ledger Accounting.

You can use Asset Accounting without further con guration, or use the asset accounting-speci c con guration options available
in the con guration environment SAP Central Business Con guration (CBC) or in the Con gure Your Solution app.

Asset Accounting is intended for international use in many countries, irrespective of the nature of the industry. To map country-
speci c valuation rules in the system, SAP delivers prede ned country-speci c content. In addition, you have country-speci c
con guration options in the SAP Central Business Con guration (CBC) con guration environment or in the Con gure Your
Solutionapp.

Integration
The Asset Accounting postings are recorded in the universal journal. This contains postings from various application
components, in particular from General Ledger Accounting and Controlling.

Asset Accounting is also closely integrated with other application components: On the one hand, data from other application
components is transferred directly to Asset Accounting. On the other hand, Asset Accounting also transfers data to other
application components. For example, when an asset is purchased or produced in-house, you can directly post the invoice/goods
receipt or the material withdrawal from the warehouse in the application component Sourcing and Procurement to assets in
the Asset Accounting component. At the same time, you can pass on recorded depreciation directly to General Ledger
Accounting and Controlling. Maintenance activities that require capitalization can be settled to the respective assets from the
Asset Management application component (including Plant Maintenance).

Key Features
Asset Accounting comprises the following functions:

Master data (asset maintenance)

Functions for valuation

Transactions, such as asset acquisitions and retirements

Depreciation

Closing operations

Reporting

Legacy data transfer

Archiving

This is custom documentation. For more information, please visit the SAP Help Portal 2
 8/16/2024
The functions cover the entire life of the asset from the purchase order or initial acquisition (which can be managed as an asset
under construction) all the way to the asset retirement. The system calculates, to a large extent automatically, the values for
depreciation and other purposes between these two points in time, and places this information at your disposal in varied form in
reporting. There is a report for depreciation forecasting and simulation of the development of asset values.

Asset Accounting supports parallel accounting using parallel value management in different currencies and valuations. The
system posts parallel values with the actual values in real time; separate documents are posted for each valuation (that is, each
accounting principle).

 Note
The following functions are covered by other application components: Asset Management (including plant maintenance)
offers functional locations and equipment for the technical management of assets. Treasury and Risk Management (TRM)
offers functions for managing nancial assets.

Master Data

Use
You can use the asset master record to create, edit, and display the master data of Asset Accounting.

To manage single or few asset master records, you can use the Manage Fixed Assets and Manage Legacy Assets apps. For
more information about these apps, see the sections below.

APIs are available for mass management of asset master records. For more information, see APIs for Asset Accounting.

Manage Fixed Assets

App ID:F3425

With this app, you can display worklists for asset master data, manage asset master records, and display asset values in various
valuations.

Features
You can use this app to do the following:

Display the worklist of the asset master records

Manage xed asset master data

Display asset values for each valuation

Display the worklist of the asset master records

You can display a worklist of xed assets and get an overview of the status of all assets in the list. You can lter this list
according to certain criteria, such as company code or asset class. You can also re ne the list so that, for example, only xed
assets that are incomplete, capitalized, or deactivated are displayed.

From the worklist, you can also create new assets or asset subnumbers. You can also branch to the management of xed asset
master data, to the display of the asset values, or to posting apps.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 8/16/2024

Manage xed asset master data

You can create new xed assets in the management of xed asset master data. You can also create an asset subnumber for a
main asset number. You can change an existing xed asset or block an existing asset against acquisition postings. Finally, you
can delete a xed asset if no postings on the xed asset exist.

To make it easier for you to manage and evaluate xed asset master data, the xed asset data is structured according to its use
and function in the system. The asset master record consists of the following areas:

Header data: company code, asset class, account determination, lifecycle status, and so on.

General data description, base unit of measure, and so on.

Physical inventory data

Time-dependent data: for example, assignment to cost center

Information on the origin of the asset

Ledgers in which the asset is managed

For each ledger and depreciation area: Details for the valuation (depreciation key, useful life, and so on)

File attachments

Change documents for tracking changes to the xed asset

The following functions are available when you create an asset:

You can create a new xed asset from scratch, or you can use an existing xed asset as a template.

You can create a single asset, or you can create several similar assets at the same time (this is possible for main asset
numbers as well as for asset subnumbers). You can use this function, for example, if the assets that you need to create
only differ in their description.

Display asset values for each valuation

In this part of the app, you can nd all the data for valuating the xed asset. A graphical representation of the xed asset's life
cycle gives you a quick overview of the valuation. Key gures, such as acquisition and production cost (APC), accumulated
depreciation and netbook value help you to understand the xed asset valuation in detail and to determine why unexpected
value changes have occurred, for example, when special depreciation for a xed asset has been posted by accident.

The following functions are available:

Display header data for an asset, including the asset number, asset class, short description, ledger, and depreciation
area

Get an overview of the selected depreciation area and its parameters, and deep dive into details for the depreciation
area

View key gures by area and see reports for depreciation with different value corrections, such as ordinary or special
depreciation

View related journal entries and transactions

View the life cycle chart and see how the values for your xed asset evolve

Compare values in parallel for a range of scal years and depreciation areas

Display Depreciation Calculation

This is custom documentation. For more information, please visit the SAP Help Portal 4
 8/16/2024
In many cases it is not immediately clear how individual depreciation values were calculated, due to complex
depreciation terms and asset transactions. The system, therefore, enables you to clearly see the origin of asset values
by identifying the various levels of the calculations and depreciation terms involved. You can display more detailed
information on the calculated depreciation values step-by-step for each scal year, real depreciation area, and currency
type.

The system displays the asset balance at the start of the scal year, as well as the depreciation planned on the balance.
In addition, all changes to APC values in the current year, with the corresponding adjustments to planned annual
depreciation, are displayed.

If you are using the app Maintain Number of Units for UoP Depreciation, note the following: In the Manage Fixed Assets app,
you can assign the xed asset to a usage object. As a result, the xed asset - together with other assets assigned to the usage
object - is depreciated using the same factor for a given period. (This factor results, for example, from the number of units of
the usage object.) As soon as you have assigned a depreciation key for the units-of-production depreciation in the xed asset
valuation part of the app Manage Fixed Assets, under General Parameters in the time-dependent depreciation terms, the
system displays the eld for the usage object as a required entry eld. Once you have speci ed the usage object and saved the
assignment, the system displays information about the number of units. For more information about the app for units-of-
production depreciation, see Maintain Number of Units for UoP Depreciation.

How-to Video (English only)

 Note
Captions are available for multiple languages. Use the CC (Closed Captions) button in the video player to see which
languages are supported.

You can also use the Search within video eld to search for speci c text in the English or German captions.

Supported Devices
Desktop

Tablet

This is custom documentation. For more information, please visit the SAP Help Portal 5
 8/16/2024

App Extensibility: Manage Fixed Assets

As a key user, you can extend the Manage Fixed Assets app according to your business needs.

Features
You can enhance the standard elds that exist in the asset master record with custom elds.

You can add custom elds to the tab General Data/Physical Inventory Data.

 Example
In the asset master record, you want to add the eld Warranty End Date to the General Data/Physical Inventory
Data tab.

You can also add custom elds to the Time-Dependent Data tab.

 Example
In the asset master record, you want to add the Organizational Unit eld to the Time-Dependent Data tab.

You add a custom eld to the UI by using the appropriate business context in the Custom Fields app:

UI Element Business Context

Manage Fixed Assets app → Details for the Asset Master Record Fixed Asset Master Data (FAA_ASSET_MASTER_DATA)
→ General Data/Inventory Data tab page

Manage Fixed Assets app → Details for the Asset Master Record Fixed Asset Master Time-Dependent Data
→ Time-Dependent Data tab (FAA_ASSET_MASTER_TD_DATA)

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes (Object Pages).

Procedure: Create custom eld for the xed asset master record
1. Call the app Custom Fields.

2. To create a new eld, on the Custom Fields tab page, choose the „+“ (Create) pushbutton.

3. In the New Field dialog box, specify the following eld attributes:

a. Business Context Fixed Asset Master Data or Fixed Asset Master Time-Dependent Data

b. Labels

c. Type (for example, number or amount)

Choose Create.

4. In the list of elds, you lter according to the Fixed Asset Master Data business context or the Fixed Asset Master Time-
Dependent Data business context.

5. In order to get from the list of elds to the detail view for your new eld, choose the pushbutton „>“ in the line of your
new eld.

6. In the detail view for your new eld, navigate to the tab UIs and Reports.

a. Activate the use in the proposed UIs and reports.

This is custom documentation. For more information, please visit the SAP Help Portal 6
 8/16/2024
b. Choose Save.

c. Choose Release.

Business users can then display elds that you have enabled in the Custom Fields app.

How-to Video (English only)

This video shows you how to extend the master data for your xed assets by creating custom elds and implementing them in
your business applications and Asset Accounting reports.

 Note
The following multimedia content displays screens and user interfaces in English only.

Captions/subtitles are available for a range of languages. Click on the CC button at the bottom of the video player to see
which languages are supported.

You can also use the Search within video eld to search for a speci c text in the English or German captions.

Open this video in a new window

Related Information
Key User Extensibility
Custom Fields

Manage Legacy Assets

App ID:F7280

You can use this app to create master data for legacy assets manually in the SAP system. You can also manage the master data
of existing xed assets (display, change, block against changes, and delete) and display the values of the xed assets.

This is custom documentation. For more information, please visit the SAP Help Portal 7
 8/16/2024
You can use this app if you want to transfer only a little legacy data to the SAP system. However, if you want to transfer large
amounts of legacy assets, we recommend an automatic legacy data transfer using SAP S/4HANA Migration Cockpit. You should
also use this app to transfer some legacy data manually as a test before the automatic legacy data transfer takes place using
the SAP S/4HANA Migration Cockpit.

You can use this app exclusively to create the master data for legacy xed assets manually in the SAP system for a legacy data
transfer. To continue managing transferred legacy assets (for example, to change or delete them), you can either use this app
or the Manage Fixed Assets app.

To manually transfer accumulated asset values (APC, depreciation), use the app Post Transfer Values for Legacy Asset.

Prerequisites
Before you can create legacy assets with this app, you must create a legacy data transfer segment and specify the parameters
for the legacy data transfer.

For more information, see Preparations: Create Legacy Data Transfer Segment with Parameters.

Features
You can use this app to do the following:

Create legacy assets manually in the SAP system

Manage existing legacy assets: display, change, block against changes, and delete

Display Values for Legacy Asset

Supported Devices
Desktop

See Also
For more information about legacy data transfer in Asset Accounting (and for automatic legacy data transfer using SAP
S/4HANA Migration Cockpit), see Legacy Data Transfer.

App Extensibility: Manage Legacy Assets

As a key user, you can extend the Manage Legacy Assets app according to your business needs.

Features
The enhancement of this app is similar to the enhancement of the Manage Fixed Assets app.

For more information, see App Extensibility: Manage Fixed Assets.

Time-Dependent Master Data

Use
This is custom documentation. For more information, please visit the SAP Help Portal 8
 8/16/2024
In the life cycle of a xed asset, the assignment of the xed asset to organizational units (account assignment objects or other
organizational units) can change.

 Example
An asset is rst assigned to cost center CC1. At a later point in time, it is assigned to cost center CC2.

You use the time-dependent data in the asset master record.

The system can display the correct assignment for a given time and

This allows the system to historically store the different assignments and to evaluate them for posting and reporting
purposes.

Features
You can assign account assignment objects, such as cost center, WBS element, and pro t center time-dependently in the asset
master record.

Create and Change Assignment

To create an assignment to an account assignment object, create a new time interval. The time interval has a valid-from date
and a valid-to date. This way, the system saves the assignments without gaps and to the day.

For time-dependent data, the account assignment objects relevant to the balance sheet differ from the account assignment
objects and organizational units that are not relevant to the balance sheet.

Account Assignment Objects Relevant to the Balance Sheet

Some account assignment objects are marked as relevant for balance sheet in the con guration (for example, pro t center and
segment). If you create a new time interval and change the account assignment object, the system automatically triggers a
transfer from the old to the new account assignment object for such account assignment objects relevant to the balance sheet.

 Example
The asset is assigned to pro t center PC1 up to the date of March 10. As of 11.03.YYYY, pro t center PC2 is assigned. You
create a corresponding new time interval.

Time Interval Valid-from Date Valid-to Date Pro t Center

1 01.01.1900 10.03.YYYY PC1

2 11.03.YYYY 31.12.9999 PC2

On 11.03.YYYY, the system automatically transfers to the new pro t center.

The transfer can also be triggered by an indirect derivation of balance sheet-relevant account assignment objects, for example,
through a change of cost center in a new time interval, which leads to a change of the pro t center.

 Note
The following applies to account assignment objects relevant to the balance sheet: As long as no documents have been
posted to a newly created asset, you can change the existing time interval and enter other account assignment objects
there by overwriting.

This is custom documentation. For more information, please visit the SAP Help Portal 9
 8/16/2024
However, once documents have been posted to the xed asset, this is no longer possible. To assign another account
assignment object, you need to create a new time interval, as described above.

Non-Balance Sheet-Relevant Account Assignment Objects and Organizational Units

For non-balance sheet-relevant account assignment objects and other organizational units, the following applies: You can
change the assignment to a xed asset by overwriting the assignment in the existing time interval. This means that you do not
need to create a new time interval.

Delete Last Time Interval

If you want to undo the change to an assignment, you can delete the last time interval. A distinction must be made between the
following cases:

a) The object is either not relevant to the balance sheet, or the account assignment object is relevant to the balance sheet,
but the system has not made any transfers.

This case includes the following subordinate cases:

The account assignment object or other organizational object is not relevant to the balance sheet.

Although the account assignment object is relevant to the balance sheet, the system has not made any transfers for the
time interval you want to delete.

For example, if the cost center has changed, but the pro t center has not changed, you can delete the last time interval.

In both subordinate cases, you can delete the last time interval without further action.

b) The account assignment object is relevant to the balance sheet and the system has already performed a transfer.

If the system has already triggered an account assignment change with the corresponding transfer due to the last time interval
and you now delete the last time interval, the system automatically posts a reversal. This reversal can only be triggered in the
time-dependent master data by deleting the corresponding time interval.

The following prerequisites need to be met for the reverse posting: It can only be executed if the system check determines that
the balance for the new account assignment object is zero after the reverse posting.

In both cases (that is, a) and b), you must note the following: If you want to delete several time intervals, you must delete them
gradually. It is not possible to delete several time intervals at the same time.

Document Display for Transfer and Reversal Document

You can display the documents for transfers due to account assignment changes and for corresponding reversal postings as
follows:

If you add a new time interval that triggers a transfer and then save the xed asset, the system displays a link to the
transfer document for the newly added time interval in the time-dependent master data.

If you delete a time interval and the transfer is reversed, the system does not display the link in the time-dependent
master data.

However, you can display both documents (the transfer document and the reversal document) in the Value Display of
the Manage Fixed Assets app under Journal Entries.

Change Master Record for Account Assignment Object Assigned to Fixed Assets

This is custom documentation. For more information, please visit the SAP Help Portal 10
 8/16/2024
You cannot change a master record for an account assignment object that is assigned to xed assets, such as the master
record for a cost center. The system issues a corresponding error message.

 Example
A cost center is assigned to an asset in the asset master record.

In this case, the system does not allow you to exchange the pro t center in the master record for the cost center.

 Recommendation
Before you make the change to the desired master record for the account assignment object, you must rst remove the
assignment of the cost center to the assets affected.

In the event of a change in cost center, remove only the cost center. However, you leave the pro t center assignment to the
xed asset. After changing the cost center, you assign it again to the assets, and an automatic transfer posting is triggered.

Manage Substitution and Validation Rules - For Asset Master

Data
App ID: F6968

As a con guration expert, you can use this app to create rules that are used to validate or substitute asset master data at
runtime.

Features
You can use this app to do the following:

In validation rules, you can specify how the system should check values that the user enters for the asset master record.

In substitution rules, you can specify the preconditions under which the system is to ll or overwrite (replace) certain
elds from the asset master record.

You can create the validation and substitution rules for standard elds from the asset master record as well as for customer
elds.

Where do the validation and substitution rules apply?

The validation and substitution rules affect the manual creation and change of asset master records. This means the following:
The validation and substitution rules have an effect when you create or change asset master records in one of the following
ways:

Using the Manage Fixed Assets app (see also Manage Fixed Assets)

Using the Manage Legacy Assets app (see also Manage Legacy Assets)

With the master data APIs (for example, with the API Fixed Asset - Create Main Asset (Asynchronous)
(FAA_FIXED_ASSET_CREATE_MAIN_WEBI)

During the automatic legacy data transfer of master data using the SAP S/4HANA migration cockpit (with the migration
object Fixed Asset - Master Data (SIF_FIXED_ASST_M))

 Restriction

This is custom documentation. For more information, please visit the SAP Help Portal 11
 8/16/2024
In the following case, the system does not apply a substitution rule, but does not explain this: You have de ned a rule for
pro t center substitution, whereby you want to use a speci c value on the tab page for time-dependent data. If the
preconditions are now met and you create an asset dynamically using an SAP GUI app (for example, with the app Post
Acquisition (Non-Integrated) – With Automatic Offsetting Entry (ABZO)), the system derives the pro t center correctly
using the pro t center derivation of Cost Center Accounting and not using the substitution rule. However, the system does
not issue a warning message explaining this.

How do I use validation and substitution in detail?

Using the app, you create all rules in the business context Asset Accounting - Master Data. Validation and substitution are
available as rule types.

Business Context: Asset Accounting - Master Data

Rule Type:
Validation

Substitution

In a validation rule, you can specify that the system issues a warning or error message if a certain precondition is met.

 Example
You want the system to issue an error message if the Location eld (required entry eld) is not lled in the master record of
an asset from the building asset class.

Using a substitution rule, you can derive asset master data automatically or even have it replaced by other values. To do this,
you can de ne preconditions and the substitution itself, that is, the reaction of the system.

You can use asset-speci c elds and associated elds in the preconditions. Associated elds are elds that are indirectly
available via other elds; for example, the Country eld is indirectly available via the Company Code eld.

Only asset-speci c elds are available for substitution, since you can only use the app to ll or replace elds of the asset
master record.

You use the substitution type to de ne possible system reactions: For example, the system can reset (delete) a value, replace it
with a constant, or with a value that is determined using a function.

Substitution Type:
Clear Value:

Substitute with Constant

Substitute with Field /Function

Table Lookup

 Example

As a customer eld, you use the Warranty Expiration Date eld and want to ll it automatically when you create an
asset master record. You have an asset class in which the assets all have a guarantee duration of two years.

You then proceed as follows:

In addition to the customer eld Warranty Expiration Date, you create an additional customer eld: Purchase
Date.

This is custom documentation. For more information, please visit the SAP Help Portal 12
 8/16/2024
You create a substitution rule that lls the warranty expiration date when the asset is capitalized. In this rule,
you specify that the warranty expiration date is to be calculated using the purchase date and the two-year
warranty duration (constant).

You want the depreciation key to be selected automatically depending on the country and thus override the default
value from the asset class.

The Overwrite indicator has the following effect:

If you set the indicator and a value already exists in the master record, this is replaced.

If you do not set the indicator, only initial elds are lled with the substitution value. Existing values, on the other hand,
are not overwritten.

A validation or substitution rule can have the following status:

Status:
New

Active

Deactivated

The system considers the active validation and substitution rules at runtime.

Which master data elds can I check or in uence, and how?

The asset master record elds that you can check by a validation rule or in uence by a substitution rule are grouped into so-
called events:

Event:
Time-independent data

Time-dependent data:

Time-independent valuation

Time-dependent valuation

Depending on which event you choose, you have different elds for your validation or substitution rule.

Time-Independent Data

You can use the event Time-Independent Data to maintain rules for the following elds, for example:

Field Description

AssetSerialNumber Serial Number

BaseUnit Base Unit of Measure

FixedAssetDescription Name of Asset

Inventory Inventory Number

Time-Dependent Data

This is custom documentation. For more information, please visit the SAP Help Portal 13
 8/16/2024
You can use the event Time-Dependent Data to maintain rules for the following elds, for example:

Field Description

CostCenter Cost Center

WBSElementInternalID WBS Element

Time-Independent Valuation

You can use the event Time-Independent Valuation to maintain rules for the following eld, for example:

Field Description

NegativeAmountIsAllowed Indicator: Negative values allowed

Time-Dependent Valuation

You can use the event Time-Dependent Valuation to maintain rules for the following elds, for example:

Field Description

DepreciationKey Depreciation Key

PlannedUsefulLifeInPeriods Planned Useful Life in Periods

PlannedUsefulLifeInYears Planned Useful Life in Years

Log
The system logs the execution of the validation and substitution rules in the app Logs for Substitution/Validation (App ID
F4886) provided that you have activated the logging for the affected period.

You activate the logging in the app Set Substitution/Validation Logs (App ID 4945).

Authorization Concept

Access to the app Manage Substitution and Validation Rules - For Asset Master Data

To be able to access the app Manage Substitution and Validation Rules - For Asset Master Data on the SAP Fiori launchpad as
con guration expert for Asset Accounting, you require a business role containing the business catalog Asset Accounting -
Con guration for Master Data (SAP_CA_BC_AA_MDAT_CONFIG_PC). The business catalog role Con guration Expert -
Business Process Con guration (SAP_BR_BPC_EXPERT) which is provided by SAP as a template contains the business catalog
SAP_CA_BC_AA_MDAT_CONFIG_PC.

 Note
In addition to the app Manage Substitution and Validation Rules - For Asset Master Data, the business catalog
SAP_CA_BC_AA_MDAT_CONFIG_PC also contains the above-mentioned log apps:

Substitution/Validation Logs (App ID F4886)

Set Substitution/Validation Logs (App ID 4945)

Access to the asset master data elds in the value help

This is custom documentation. For more information, please visit the SAP Help Portal 14
 8/16/2024
If a user should de ne the substitution and validation of asset master data, the business catalog
SAP_FIN_BC_AA_MDAT_REG_PC should be assigned to their business role in addition to business catalog
SAP_CA_BC_AA_MDAT_CONFIG_PC. The reason for this is that if only SAP_CA_BC_AA_MDAT_CONFIG_PC is assigned to the
business role, but not SAP_FIN_BC_AA_MDAT_REG_PC, then the user gets no value help for the asset master data elds in the
app Manage Substitution and Validation Rules - For Asset Master Data (due to missing authorizations).

Access to Rule Detail from Runtime Applications

If master data changes are made in the runtime applications where the de ned rules are applied, business users may want to
view the rule details, for example, when an error or warning message shows up because their entered values don't comply with
a validation rule. To navigate from the messages to the rule display page, the users must have a business role that contains the
business catalog Asset Accounting - Master Data for Ordinary Assets (SAP_FIN_BC_AA_MDAT_REG_PC).

More Information about Authorizations

For more general information on authorizations, see Identity and Access Management.

Supported Devices
Desktop

Tablet

Maintain Number of Units for UoP Depreciation

App ID:F4907

You use this app when you apply units-of-production depreciation. In the app, you enter the total number of units and the actual
number of units per period for a so-called usage object.

You can assign one or more xed assets to a usage object. All assigned assets are then depreciated over a given period with the
same factor.

Example: The usage object is an oil eld. All assets used in the oil eld should be depreciated equally in accordance with output,
depending on the expected total production amount (= total number of units) and the actual amount of oil extracted in a period
(= actual number of units per period). Therefore, the assets used in the oil eld are assigned to the usage object “oil eld”.

Prerequisites
The depreciation keys are prede ned in the system. The following depreciation keys are used for units-of-production
depreciation:

A depreciation key with which the acquisition value is depreciated over the total number of units (UOPT).

The system then calculates the depreciation based on the number of units per period entered for the usage object and
the acquisition cost of the asset.

A depreciation key with which the net book value is depreciated over the remaining number of units (UOPR).

The system then calculates the depreciation based on the remaining number of units of the usage object and the net
book value of the asset.

For more information about calculating units-of-production depreciation, see Units-of-Production Depreciation.

This is custom documentation. For more information, please visit the SAP Help Portal 15
 8/16/2024

 Note
If, during the transfer of legacy data, you have the system recalculate accumulated past depreciation and use units-of-
production depreciation, you must then enter the number of units for the period beginning with the acquisition date of the
oldest asset, up to the time of the legacy data transfer.

Features
You can use this app to do the following:

Display the worklist of usage objects

Create a usage object

Display and change the lifecycle status

Maintain the total number of units and the number of units per period for a usage object

Display change documents

Display the worklist of usage objects

You can display a worklist of usage objects to get an overview of the status of all usage objects in the list. You can lter this list
according to certain criteria, such as company code or lifecycle status. You can also re ne the list so that, for example, only
usage objects that are active or deactivated are displayed.

From the worklist, you can also create new usage objects. You can also navigate to the management of usage objects.

Create usage object

You create a usage object in a speci c company code.

Once you have created the usage object, it has the lifecycle status Created.

Display and change lifecycle status

A usage object can have the following lifecycle statuses:

Created

Active

Deactivated

Archivable, Archived and Deletable, Archived and Deleted

When you create a usage object, it rst has the status Created. A usage object can only be deleted when it has the status
Created.

A usage object can only be assigned to assets when it has the status Active. Once a usage object is active, it cannot be deleted.

When a usage object has the status Deactivated, you can only change the description and the status. You can set the status
back to Active.

A usage object can be set to Archivable by the archiving program as soon as all assigned assets are archived.

Maintain the total number of units and the number of units per period for a usage object

This is custom documentation. For more information, please visit the SAP Help Portal 16
 8/16/2024
For user-de ned time intervals, you can enter the following number of units for a usage object:

The expected total number of units (total production amount) for the usage object.

The total number of units is valid for the duration of the time interval, that is, it is used for the calculation of depreciation
for this duration.

If the planned total number of units changes, create a new time interval. This changed total number of units then
becomes valid at the start of the new time interval for the calculation of depreciation.

You can create a time interval for the total number of units for all depreciation areas (depreciation area ʻ*’) or for a
speci c depreciation area.

Number of units per period (production amount in period).

You also create time intervals for the number of units per period. You can de ne these as you want and they are based
on calendar date. Each time interval for the number of units per period must be completely covered by a time interval for
the total number of units.

For the calculation of depreciation, the system uses the scal year variant valid for the valuation to determine the
number of units per period for the depreciation period.

The remaining number of units (remaining production amount) is calculated by the system. The remaining number of units for a
speci c date is the difference between the total number of units (valid on that date) and the cumulated number of units per
period from previous time intervals (up to that date). The remaining number of units must not become negative in all
depreciation areas at the same time.

Assign assets to a usage object

The assets that are to be assigned to a usage object and the usage object itself must be in the same company code. Only active
usage objects can be assigned to assets.

You assign the assets to the usage object outside the app Maintain Number of Units for UoP Depreciation. You have the
following options for this assignment:

Manual assignment in the Manage Fixed Assets app:

We recommend manual assignment if you want to assign only one or a few assets.

As soon as you have assigned a depreciation key for the units-of-production depreciation in the xed asset valuation part
of the app under General Parameters in the time-dependent depreciation terms, the system displays the eld for the
usage object as a required entry eld. Once you have speci ed the usage object and saved the assignment, the system
displays information about the number of units.

Automatic Assignment via API Fixed Asset - Change (Asynchronous) (FAA_FIXED_ASSET_CHANGE_WEBI)

We recommend that you make assignments using the API if you want to assign a large number of assets.

For more information about the API, see Fixed Asset - Change (Asynchronous).

Once you have assigned one or more assets to a usage object, these assets are displayed in the app Maintain Number of Units
for UoP Depreciation in the area Assigned Fixed Assets. From here, you can navigate to the relevant asset master record and
vice versa.

Display change documents

All changes to the usage object are documented in change documents. You can view the change documents in the Change
Documents area.

This is custom documentation. For more information, please visit the SAP Help Portal 17
 8/16/2024

Supported Devices
Desktop

Tablet

Additional Information
For more information about calculating units-of-production depreciation, see Units-of-Production Depreciation.

For more information about master data maintenance, see Manage Fixed Assets.

There is an API for managing usage objects. For information about this, please see Fixed Asset: Usage Object for UoP
Depreciation.

As part of a legacy data transfer with the SAP S/4HANA Migration Cockpit, you can transfer usage objects from a legacy
system. For information about the corresponding migration object, see Fixed asset - Usage object.

Transactions

Transactions in Asset Accounting

The business transactions during the life of an asset are represented in the system by transactions.

 Example
The transactions include acquisitions, retirements, transfers, and post-capitalizations.

The system generates journal entries for Asset Accounting transactions.

Apps for Transactions

The following apps are available for Asset Accounting transactions:

Transaction Explanation App More Information

Asset Acquisition - Integrated You post the acquisition of an Manage Supplier Invoices Manage Supplier Invoices
with Accounts Payable - Without asset through a purchase. In (F0859)
Purchase Order Reference doing so, in Asset Accounting,
you post without reference to a
purchase order, but integrated
with Accounts Payable
Accounting, that is, against the
supplier.

Asset Acquisition - Not You post the acquisition of an Post Asset Acquisition - And
Post Asset Acquisition -
Integrated with Accounts asset through a purchase. In Quantity Adjustment (F6488).
And Quantity
Payable - Without Purchase doing so, in Asset Accounting,
Adjustment
Order Reference you post without reference to a
purchase order and without Example: Acquisition,
integration with Accounts Non-Integrated Posting
Payable Accounting; instead,
you post against a clearing
account.

This is custom documentation. For more information, please visit the SAP Help Portal 18
 8/16/2024

Transaction Explanation App More Information

Post-Capitalization Post-capitalizations are Post Asset Acquisition - And Post Asset Acquisition - And
subsequent corrections to the Quantity Adjustment (F6488). Quantity Adjustment
acquisition cost of a xed
asset. An example of when you
need this type of correction is if
you neglected to add costs
linked with the acquisition or
assembly of an asset to its
acquisition cost in a scal year
that is now closed.

Credit Memo You can post received credit Post Asset Acquisition - And Post Asset Acquisition - And
memos, both for invoices from a Quantity Adjustment (F6488). Quantity Adjustment
previous year and for invoices
from the same year as the
credit memo.

Quantity Adjustment You can make adjustment Post Asset Acquisition - And
Post Asset Acquisition -
postings for quantities. This is Quantity Adjustment (F6488).
And Quantity
only possible if quantity
Adjustment
postings to the xed asset
already exist. With the Quantity Adjustments
adjustment posting, the system
only adjusts the quantity up or
down, but it does not change
the value.

Transfer - Intracompany With this type of transfer, you Post Transfer - Within
transfer a sending asset or Company Code (ABUMN)
asset component within a
company code to a target asset.
This may be necessary, for
example, because the asset
was created in the wrong asset
class.

Transfer - intercompany, within With this type of transfer, you Post Transfer - Across
the same country transfer a sending asset or Company Codes Within the
asset component to a target Same Country (ABT1N)
asset that is assigned to a
different company code. The
company code of the target
asset is within the same country
or region.

Asset Retirement - Integrated An asset is sold and revenue is Post Retirement (Integrated Post Retirement (Integrated AR)
with Accounts Receivable generated. You post the asset AR) – With Customer (F-92) – With Customer
retirement integrated with
Accounts Receivable
Accounting, that is, against the
customer.

Asset retirement with revenue An asset is sold and revenue is Post Asset Retirement (F7107) Post Asset Retirement
(not integrated with Accounts generated. You do not post the
Receivables) retirement integrated with the
customer invoice; you post it
against a clearing account
instead.

This is custom documentation. For more information, please visit the SAP Help Portal 19
 8/16/2024

Transaction Explanation App More Information

Asset retirement without An asset is retired from the Post Asset Retirement (F7107) Post Asset Retirement
revenue (for example, with xed assets without revenue
scrapping) (for example, by scrapping). You
post an asset retirement by
scrapping. The system then
creates the posting Loss made
on asset retirement without
revenue in the amount of the
net book value being retired
instead of the revenue and
gain/loss posting.

Manual Depreciation The following depreciation Post Depreciation Manually – Depreciation

types are available in the Unplanned and Planned
system: (ABAA)

The depreciation types

calculated
automatically: Ordinary
depreciation and
special depreciation.

The depreciation type to

be scheduled manually:
unplanned depreciation

The automatic calculation of

depreciation is controlled by
depreciation keys in the
system.

This is custom documentation. For more information, please visit the SAP Help Portal 20
 8/16/2024

Transaction Explanation App More Information

Manual Write-Up A writeup is a subsequent Post Writeup (ABZU)

change to the valuation of a
xed asset. It always refers to
the value adjustment
(depreciation). Post-
capitalization, on the other
hand, refers to the acquisition
cost.

A writeup usually has the

following cause: The
depreciation calculated in the
past was too high. You must now
correct this depreciation using a
writeup in the current scal
year. Excessive depreciation
can have the following reasons:

The use of incorrect

depreciation terms
(incorrect expected
useful life, incorrect
depreciation key)

Unplanned depreciation
which is no longer valid
in the current situation

Subsequent reduction of
the acquisition or
production costs of an
asset (for example, by
means of a subsequent
credit memo); this
means that depreciation
should be lower

You can post writeups to

ordinary depreciation, special
depreciation, unplanned
depreciation, and manual
depreciation.

Manual Revaluation Revaluation enables you to Post Asset Revaluation Post Asset Revaluation
revaluate an asset with (F7775)
replacement values (so different
to the acquisition cost). For Note: The app replaces the
example, you can perform a following deprecated app: Post
revaluation to offset the Asset Revaluation (ABAWL)
in ation-related cash
devaluation or to apply market
value principles for Asset
Accounting.

Manual Revaluation Deprecated

Post Asset Revaluation

(ABAWL)

This is custom documentation. For more information, please visit the SAP Help Portal 21
 8/16/2024

Transaction Explanation App More Information

Reversal With a reversal, you reverse Reverse Journal Entries Reversal

(undo) postings. The system (ABMW)
makes an inverse posting for
this. If the underlying
transaction was triggered in
Asset Accounting, reverse the
posting using the app Reverse
Journal Entries (ABMW). You can
access the app in the document
display of the Manage Fixed
Assets app (F3425).

Manual Legacy Data Transfer: If you only need to transfer a Post Transfer Values – For
Legacy Data Transfer
Value Transfer small amount of legacy data to Legacy Asset (ABLDT)
the SAP system, or if you want Manual Legacy Data
to carry out the legacy data Transfer
transfer as a test, then perform
the transfer manually. First, you
transfer the asset master
records using the Manage
Legacy Assets app (F7280);
then you transfer the asset
values using this app (Post
Transfer Values - For Legacy
Asset (ABLDT).

Manual Legacy Data Transfer: To ensure that the line-item- Transfer Open Items of AuC –
Legacy Data Transfer
Transfer of open items for an managed assets under For Legacy Asset (ABLDT_OI)
asset under construction construction can be settled, you Transferring Assets
cannot enter values as under Construction
cumulated values using the app
Post Transfer Values – For Manual Legacy Data
Legacy Asset (ABLDT). Instead Transfer
you have to enter the values
individually using the app
Transfer Open Items of AuC –
For Legacy Asset (ABLDT_OI).

Miscellaneous Transactions in The app is intended for other Post Miscellaneous

 Caution
Asset Accounting Asset Accounting transactions Transactions) (ABSOL)
that cannot be performed using Use this app only for
the apps mentioned above. In postings within Asset
particular, you use this app if Accounting.
you perform a legacy data
transfer manually during the
scal year.

Basic Concepts for Transactions

Use
Transaction types and line item types classify the transactions and control the postings.

In addition to the posting date and the document date from General Ledger Accounting, there are several other date
speci cations in Asset Accounting.

This is custom documentation. For more information, please visit the SAP Help Portal 22
 8/16/2024

Transaction Types

Use
Within Asset Accounting, the transaction type classi es the business transaction (for example: acquisition, retirement,
transfer). It also controls various system actions when posting business transactions; it therefore determines how the
transaction is processed in the system.

For all asset postings, the system automatically proposes a suitable transaction type, or you enter it manually.

 Example
For a retirement with revenue, enter transaction type 210.

The transaction type is the basis for the system assigning a business transaction to a column of the asset history sheet.

Available Transaction Types

SAP provides transaction types for Asset Accounting. They are xed in the system and cannot be changed by the user.

Assignment to Transaction Type Group

Each transaction type is assigned to a transaction type group. The transaction type group performs various control functions for
posting and for calculating depreciation. The transaction type groups are also prede ned by the system. (However, they are not
visible on the user interfaces.)

Examples for transaction type groups are year-end carryforward, acquisition, retirement, transfer prior-year acquisitions being
retired and manual ordinary depreciation.

The business transactions are subdivided on the basis of the transaction type group into:

Transactions that in uence the acquisition and production costs of xed assets

This includes acquisitions, retirements, transfers, and post-capitalizations.

Manual depreciation

Write-Ups

Revaluation

In uence of the Transaction Type Group on the Posting

The transaction type group controls the posting. It determines:

Which value elds are to be updated in the year segments

Whether the transaction refers to the past (for example write-ups) or to the current scal year

Whether the total of the transactions of a group is positive or negative (with reference to a scal year)

Whether the acquisition date of the xed asset is to be set with the rst transaction of a transaction type group

Whether proportional accumulated depreciation can be entered for a transaction (for example during post-
capitalization), or is to be determined by the system (for example with asset retirements).

This is custom documentation. For more information, please visit the SAP Help Portal 23
 8/16/2024

In uence of the Transaction Type on the Posting

The transaction type also in uences the posting. The individual transaction types determine the following:

Property Determination:

Account assignment
Capitalize asset

Deactivate asset

Debit/credit indicator

Document type

Retirement/transfer
Retirement with revenue

Gain/Loss from retirement of xed assets

Transaction type for offsetting entry

Acquisition in same scal year

Other features
Transaction in the past

Propose consolidation transaction type

Cannot be used manually

Some of these speci cations are dependent on the assigned transaction type group, and are mutually exclusive.

Line Item Types

Use
The subledger-speci c line item type is called 'line item type’ in its short form; the technical name is SLALITTYPE. The line item
type classi es the amount posted for a line item. There are speci c line item types for each subledger, including Asset
Accounting.

 Example
Line item type 07040 is relevant for Asset Accounting and speci es the amount posted as the acquisition cost (APC) with
reference to the current scal year.

Within Asset Accounting, the line item type is an important value. The system generates and posts a separate line item for each
value type, such as APC or Accumulated Ordinary Depreciation. The line item type allows the speci c differentiation at line
item level and is therefore used in several apps for document simulation and document display.

Using line item types in detail

With both the legacy data transfer and when processing line items in the document simulation, you enter the amounts for each
currency type on the basis of the line item type.

It is forbidden to have the xed asset as an auxiliary account assignment on a line item. Only line item types of Asset Accounting
allow the speci cation of a xed asset. This affects on the one hand the balance line items, characterized by line item types in

This is custom documentation. For more information, please visit the SAP Help Portal 24
 8/16/2024
the interval 07000 to 07899, as well as the offsetting item (in expense), characterized by the line item types 79xxx.

The line item type and the transaction type category(MOVCAT) enable differentiated analytical reporting for Asset Accounting.

What connection is there between transaction types and line item types?
The transaction type controls the posting process. Or, more precisely: The app selected de nes the posting process and with it
the possible transaction type or the possible transaction types.

 Example
Transaction type 100 is allowed for a posting with the app Post Acquisition (Non-Integrated) With Automatic Offsetting
Entry; transaction type 105 would also be possible. The exact document structure is de ned based on the posting process.
This can be in uenced by other characteristics such as the country/region or the accounting principle.

In the case of a posting with the app Post Acquisition (Non-Integrated) With Automatic Offsetting Entry, a line item schema
is de ned that expects an APC line item and a clearing line as offsetting item. The system would normally nd line item itype
07040 (APC - Current-Year Acquis.), however, according to a different transaction type, line item type 07000 (APC Prior-
Year Acquis.) could also be found.

Available line item types

SAP provides all line item types, also those for Asset Accounting. They are xed in the system and cannot be changed by the
user.

The keys for the line item types of Asset Accounting start with the number '07'. See also the examples above.

Dates in Asset Accounting

Use
In addition to the usual dates entered in General Ledger Accounting (posting date, document date), there are more dates to
consider in Asset Accounting. Either you enter these additional asset accounting dates yourself when posting transactions, or
the system determines them.

Details on Specifying Dates

Asset Value Date

The asset value date is the value date of an asset transaction from an Asset Accounting point of view. Each transaction on a
capitalized asset triggers the automatic calculation of depreciation on the posting amount. The asset value date, adjusted by
the period control of the depreciation key, is the key factor in determining the depreciation start date.

Default Values for Asset Value Date

Since the asset value date has a direct in uence on the amount of depreciation, the system creates a default value for this date
when it can. The overview that follows shows the default values for the most important asset transactions:

Asset Transaction Default Value for Asset Value Date

This is custom documentation. For more information, please visit the SAP Help Portal 25
 8/16/2024

Asset Transaction Default Value for Asset Value Date

Initial acquisition
Capitalization date, if this is de ned.

If the capitalization date is not de ned, the system

proceeds as follows:

It proposes the smaller date from the posting date

and document date, if these dates are in the same
scal year.

If they are not in the same scal year, the system

proposes the posting date.

Subsequent acquisition in the same year Asset value date of initial acquisition

Subsequent acquisition in later years As with acquisition

Down payment Capitalization date from the asset master record (if in same scal
year, otherwise posting date)

Credit memo at time of invoice receipt Value date of the invoice receipt (if in same scal year, otherwise
posting date)

Manual value adjustments First day of scal year

Retirement/transfer No default value, but manual required entry

Settlement of an asset under construction (AuC) Posting date

The logic for rst acquisition is explained again here: If the capitalization date is not set in the asset master record after the
initial acquisition, or if this date is not in the current scal year, the system determines the default value for the asset value
date as follows:

If the document date and the posting date are both in the same (current) scal year, the system uses the smaller of
these two dates as the default asset value date.

If the document date is in a past scal year, the system uses the posting date as the default asset value date.

Automatically Set Asset Value Date

In the following posting transactions, you cannot enter an asset value date directly. The system therefore uses the default asset
value date automatically. The system determines this based on the following logic:

Transaction Default Value for Asset Value Date

Goods receipt (valuated) Posting date

Invoice receipt with reference to purchase order (valuated) Posting date of goods receipt (if in same scal year, otherwise
posting date)

Invoice receipt without reference to purchase order (valuated) Posting date

Invoice receipt (difference posting) Posting date of goods receipt

Stock withdrawal Posting date

Capitalization Date

The capitalization date is the date on which the asset is initially used and in operation.

This is custom documentation. For more information, please visit the SAP Help Portal 26
 8/16/2024
You can enter the capitalization date manually when you create an asset master record. The system uses this date as the
default asset value date when you make the rst acquisition posting. If you create an asset master record without capitalization
date, the system automatically enters the asset value date of the rst acquisition posting in this eld. The system inserts the
asset value date of the rst acquisition posting in the empty eld Capitalized on for the capitalization date in the asset master
record, when a “capitalizing” transaction type is used.

Depreciation Start Date

The system determines the start period for depreciation calculation from the asset value date and the period control speci ed
in the depreciation key of the transaction category. (See also Period Control Method.) The depreciation start date is the rst
day of the start period. The system determines the book value of an asset at the point of retirement In a similar fashion.

Date Asset Is Ready for Operation

Along with the date speci cations already mentioned, you can also enter the date the asset is ready for operation in the asset
master record (in the additional parameters for valuation). This date is for informational purposes only, and has no in uence on
the calculation of depreciation. If you do not enter it manually, the system automatically enters the capitalization date.

External Asset Acquisitions

Use
An external asset acquisition is a business transaction in which a xed asset is acquired from a business partner. (In contrast to
this, an acquisition from in-house production is not linked to a purchase.)

The acquisition of an externally-procured asset can take place in different ways and with the participation of different
application components:

In Asset Accounting with integration with Accounts Payable, but without reference to a purchase order

In Asset Accounting without purchase order reference and without integration with Accounts Payable; the posting is
then made against a clearing account

In Materials Management at goods receipt or invoice receipt

Integrated and Non-Integrated Acquisition Posting

Integrated Asset Acquisition Posting

If you are using Accounts Payable, it is recommended that you take advantage of this integration and post the asset acquisition
(without reference to a purchase order) with vendor. By entering the asset acquisition and the corresponding vendor payable in
the app Create Supplier Invoice – Advanced, you reduce the effort required for data entry and the risk of discrepancies.

For cash discount handling, note the following: For an asset acquisition posting integrated with Accounts Payable, you can
specify, by your choice of document type, if the invoice should be posted gross (without cash discount being deducted) or net
(with deduction of cash discount). If you use a document type for net posting, the system automatically determines the cash
discount to be deducted on the basis of the payment terms. The system capitalizes the invoice amount, less tax and cash
discount, on the xed asset.

 Recommendation
The MIRO app will be replaced by the successor app Manage Supplier Invoices (F0859).

This is custom documentation. For more information, please visit the SAP Help Portal 27
 8/16/2024
We recommend that you switch to the successor app F0859 as soon as possible. For information about the successor app
F0859, see Manage Supplier Invoices.

Non-Integrated Asset Acquisition Posting

Alternatively, you can perform an asset acquisition in the following two steps:

The invoice receipt is entered in Accounts Payable; the offsetting account is a clearing account.

You enter the asset acquisition in Asset Accounting using the app Post Asset Acquisition - And Quantity Adjustment
(F6488). The asset acquisition can be entered before or after the invoice receipt.

For cash discount handling, note the following: The entry is made with the net amount to be capitalized (acquisition and
production costs without cash discount); the system does not deduct the cash discount. In this case, the cash discount is
executed on the vendor side only.

You use the same clearing account as for the invoice receipt as the offsetting account for the acquisition posting.

After these two documents (invoice receipt and asset acquisition) have been entered, the clearing account balances to zero.

 Note
The clearing account must not have open item management.

Acquisition with Value Adjustments

If you want to acquire assets that not only have acquisition costs, but also have value adjustments already, you can also post the
acquisitions gross. To do this, use a transaction type that allows a gross acquisition. You can then enter the acquisition costs
and the corresponding value adjustments when posting the acquisition using the Post Miscellaneous Transactions app.

Post Acquisition Integrated Using the 'Create Supplier Invoice -

Advanced' (MIRO) App

Use
You can use the app Create Supplier Invoice - Advanced (MIRO) to post asset acquisitions. The posting is integrated with
Accounts Payable, but without reference to a purchase order.

 Note
The MIRO app posts integrated with Accounts Payable.

However, the Post Asset Acquisition app (F6488) does not post integrated but against a clearing account. The payable for
the asset purchase must be entered separately in Accounts Payable and posted against the clearing account.

 Recommendation
The MIRO app will be replaced by the successor app Manage Supplier Invoices (F0859).

We recommend that you switch to the successor app F0859 as soon as possible. For information about the successor app
F0859, see Manage Supplier Invoices.

This is custom documentation. For more information, please visit the SAP Help Portal 28
 8/16/2024

Prerequisite: Con guration

To activate the integration with Asset Accounting for the MIRO app, you must set the corresponding indicator in the following
con guration activity:

Activate Direct Posting to G/L & Material Accounts & Assets (ID in the con guration environment Con gure Your Solution:
106330)

Features
The MIRO app enables you to make postings for the following transactions:

Invoice for an asset acquisition

The posting is made without reference to a purchase order. However, it is made against a supplier account (payables
account), that is, integrated with Accounts Payable.

For more information, see External Asset Acquisitions.

Credit Memo

Subsequent Debit

Subsequent Credit

For an integrated posted asset acquisition, the following elds and functions from the app are relevant:

Fields and Functions for the Asset Acquisition Details

Company Code You de ne for which company code you want to enter the business
transaction.

Transaction For your business transaction, choose one of the following

transactions:

Invoice (for an asset acquisition)

Credit Memo

Subsequent Debit

Subsequent Credit

Header tab You enter the following data:

→ Basic Data Invoice and posting date, reference, amount, and related document
currency (that is, transaction currency) as well as data for tax.

Header tab In the Invoicing Party eld, you specify the vendor (supplier) who
issued the invoice.
→ Details

Details tab, below As purchase order reference, you select the option Suppliers.

→ PO Reference You then enter the speci c supplier (vendor).

Details tab, below You select the display variant Account Assignment – Asset,
Order.
→ PO Reference

→ Display Variant

This is custom documentation. For more information, please visit the SAP Help Portal 29
 8/16/2024

Fields and Functions for the Asset Acquisition Details

Details tab, below On the Asset tab, make the following entries:

→ Asset tab Asset Number and Subnumber

Debit/Credit Indicator:

This is preset on the basis of the selected transaction.

APC (Net Amount)

You can enter the quantity and base unit of measure,

provided this is de ned in the asset master record of the
asset.

Check the tax code, and correct it if necessary.

If the invoice contains several asset purchases, you can

enter additional items for additional asset numbers.

If the invoice contains costs that are not to be capitalized,

you can enter these costs in the corresponding G/L
accounts. (To do so, use the G/L Accounttab.)

Simulation/Posting If necessary, you simulate the document before you post it.

Updating Quantities You can post on a quantity basis, provided this is speci ed in the
asset master record of the asset.

Post Transaction for Existing Asset You can only post business transactions for assets that already
exist. (It is not possible to create a new asset ad hoc.)

Additional Information
See also the application help (product assistance) for Asset Accounting under Sourcing and Procurement under Create
Supplier Invoice - Advanced.

Post Asset Acquisition - And Quantity Adjustment

App ID: F6488

You can use this app to post asset acquisitions (without reference to a purchase order and without integration with Accounts
Payable) as well as post-capitalizations, credit memos, and quantity adjustments.

Features
You can use the app Post Asset Acquisition - And Quantity Adjustment to make postings for the following transactions:

Asset acquisition (without reference to a purchase order and without integration with Accounts Payable Accounting)

The posting is made without purchase order reference and without integration with Accounts Payable; the posting is
made against a clearing account instead.

Post-Capitalization

Post-capitalizations are subsequent corrections to the acquisition cost of a xed asset. An example of when you need
this type of correction is if you neglected to add costs linked with the acquisition or assembly of an asset to its

This is custom documentation. For more information, please visit the SAP Help Portal 30
 8/16/2024
acquisition cost in a scal year that is now closed. In the case of a post-capitalization, the system recalculates
depreciation from closed scal years on the basis of the capitalization date de ned in the asset master record.

Credit Memo

You can post received credit memos, both for invoices from a previous year and for invoices from the same year as the
credit memo.

Quantity Adjustment

You can make adjustment postings for quantities. You make such an adjustment posting if you only want to adjust the
quantity up or down without making a value change. However, this is only possible if quantity postings to the xed asset
already exist.

The following table explains more details about the features:

Function Details

Selection of Ledgers For the posting, you can either select one ledger or all ledgers or
several individual ledgers. To select all ledgers, you have the
following options: You select either all ledgers individually or you do
not specify a ledger (that is, you leave the ledger eld empty). The
same applies to the Depreciation Area eld.(1)

Authorization Check The system checks the authorization for all explicitly selected
ledgers or for the ledgers selected indirectly (via depreciation
areas).

Business Transaction Type Depending on which transaction you want to post, choose the
appropriate business transaction type:

Acquisition (Net),

Post-Capitalization,

Credit Memo or

Quantity Adjustment

The use of the business transaction type facilitates the year-end

closing and the display of transactions in the asset history sheet.

Currency You enter the amounts in the transaction currency. The transaction
currency can differ from the functional currency.

Quantities You can post on a quantity basis, provided the base unit of quantity
is speci ed in the asset master record of the asset.

Offsetting entry The system determines the account for the offsetting entry (usually
a reconciliation account) automatically and posts to it. However,
you can specify an alternative offsetting account.

Simulation You can simulate the posting and the corresponding journal entry
before you then execute the posting.

Post Transaction for Existing Asset You can only post an acquisition, a post-capitalization, a credit
memo, and a quantity adjustment for an existing asset. (It is not
possible to create a new asset ad hoc.)

Change posting amounts (only for post-capitalization) Before you post a post-capitalization, you can change the amounts
proposed by the system in the line item table.

(1) Further details on the selection of ledgers and depreciation areas:

This is custom documentation. For more information, please visit the SAP Help Portal 31
 8/16/2024
If you select or remove a ledger from the selection in the Posting Information screen area, the system determines the
corresponding depreciation areas and displays them. (The system proceeds accordingly if you select depreciation areas.) Due
to technical restrictions, the user interface does not always update (synchronize) the display of the ledgers determined or
depreciation areas determined. In such a case, we recommend that you reload the page.

 Note

It is not possible to change the account assignment in the header and in the line item. This is only possible in the
deprecated apps for asset acquisition (for example, in the app Post Acquisition (Non-Integrated) - With Automatic
Offsetting Entry (ABZO)).

You cannot make a posting for multiple assets. To do so, use the corresponding API (see Fixed Asset – Post Asset
Acquisition).

Navigation to App
To navigate to the app Post Asset Acquisition - And Quantity Adjustment, you have the following options:

Tile on Launchpad

Navigation menu in the launchpad: On the launchpad, you can choose Home All My Apps <Business Catalog> Post
Asset Acquisition - And Quantity Adjustment .

App Manage Fixed Assets - Worklist: You can select an asset from the worklist and then choose Post Post Acquisition
Post Acquisition (Non-Integrated) .

For a post-capitalization, credit memo, or quantity adjustment, you can proceed in the same way.

Supported Devices
Desktop

Tablet

Example: Acquisition, Non-Integrated Posting

Initial Data
The company creates nancial statements based on two parallel accounting principles:

IFRS accounting principle and

LGAAP accounting principle (local accounting principle)

There is a corresponding ledger for each accounting principle.

The enterprise posts asset acquisitions non-integrated with Accounts Payable.

The enterprise purchases a new asset. The invoice total is 10,200. Of this, 10,000 are apportioned to the acquisition cost and
200 to the incidental acquisition cost (here: freight costs).

According to IFRS, the acquisition costs in the amount of 10,000 and the freight costs in the amount of 200 are both to
be capitalized.

This is custom documentation. For more information, please visit the SAP Help Portal 32
 8/16/2024
According to the local accounting principle, only the acquisition costs in the amount of 10,000 are to be capitalized. The
freight costs are to be posted as expense.

The accounts payable assistant rst posts the complete invoice amount. Then the asset accountant capitalizes the amount
according to accounting principle IFRS and then according to the local accounting principle LGAAP.

Note: The example is shown in simpli ed form: It is posted without tax (0%). Line items for statistical depreciation areas are
not handled.

Document Entry and Generated Journal Entries

In step 1, the accounts payable accountant rst enters the total invoice amount.

In step 2 and 3, the asset accountant capitalizes the asset and posts the freight costs.

Step 1: Entry of Invoice Amount (Accounts Payable)

Step 1 - Document Entry:

The accounts payable accountant rst enters the invoice amount in the Create Incoming Invoice app:

Transaction: Invoice

Supplier: 10300081 (Payables Domestic)

Reference: ASSET ACQUISITION

Amount: 10,200

G/L account: 16014100 (Clearing Account Asset Acquisition)

Document Overview:

Document Type: KR (Supplier Company Code: 1010 Fiscal Year: JJJJ

Invoice) Normal
Document

Document Number: ... Posting Date: MM/TT/JJJJ Period: MM

Document Date: MM/TT/JJJJ Tax Reporting Date: MM/TT/JJJJ

Calculate Tax: √

Reference: ASSET
ACQUISITION

Document Currency: ...

Itm Account Account Short Text NoP Amount

1 10,300,081 Payables Domestic V0 10,200-

2 16,014,100 Clearing Account Asset V0 10,200

Acquisition

Step 1 - Generated Journal Entry

The system posts the asset acquisition cross-ledger to the asset clearing account:

This is custom documentation. For more information, please visit the SAP Help Portal 33
 8/16/2024
The following shows the journal entry generated for ledger IFRS. The system posts the same journal entry for ledger LGAAP.

No. Ledger Debit/Credit Account (No.) Account (Name) Amount

1 IFRS Debit 16,014,100 Clearing Account 10,200

Asset Acquisition

IFRS Credit 10,300,081 Payables Domestic 10,200

Steps 2 and 3: Capitalization of Fixed Asset and Posting of Freight Costs (Asset Accounting)

As an asset accountant, you activate the asset using the app Post Asset Acquisition - And Quantity Adjustment (F6488). In the
ledgers, you need to activate the asset with different amounts. There are two possible variants for how you can enter the
postings. In the second variant, the general ledger accountant is also involved.

Variant A:

Step 2: As an asset accountant, you enter and post (capitalize) the total amount of 10,200 (that is, including freight
costs) in both ledgers (IFRS and LGAAP).

Step 3: You correct the posting in ledger LGAAP by 200 and transfer this amount to freight expense.

Variant B:

Step 2: As an asset accountant, you enter and post (capitalize) an amount of 10,200 for ledger IFRS only, that is,
including freight costs.

Step 3: You enter and post an amount of 10,000 for ledger LGAAP, that is, without freight costs.

Step 4: The general ledger accountant enters a general journal entry using the corresponding app in General Ledger
Accounting: He/she posts the freight costs by posting the Clearing Account Asset Acquisition in debit and the freight
costs in credit.

Variant A is shown below.

Step 2 - Document Entry: Capitalization

You post an acquisition across ledgers using the business transaction type Acquisition (Net).

Debit/Credit Account Type Account (No.) Account (Name) Amount

Debit Assets 16,004,000 Vehicles (Acquisition 10,200

Cost)

Credit General Ledger 16,014,100 Asset Acquisition 10,200

Clearing Account

Step 2 - Generated journal entry: Capitalization

The system generates the following journal entry:

No. Ledger Debit/Credit Account (No.) Account (Name) Amount

2a IFRS Debit 16,004,000 Vehicles 10,200

(Acquisition Cost)

IFRS Credit 16,014,100 Clearing Account 10,200

Asset Acquisition

This is custom documentation. For more information, please visit the SAP Help Portal 34
 8/16/2024

No. Ledger Debit/Credit Account (No.) Account (Name) Amount

2b LGAAP Debit 16,004,000 Vehicles 10,200

(Acquisition Cost)

LGAAP Credit 16,014,100 Clearing Account 10,200

Asset Acquisition

Step 3 - Document Entry: Transfers

With the Post Asset Acquisition - And Quantity Adjustment app, you post a credit memo that is only relevant for the ledger
LGAAP. To do this, select the transaction Other Posting Transaction Post Acquisition Post Credit Memo . The Business
Transaction Type eld is then pre lled with the value Credit Memo. You enter the freight account as the offsetting account. You
select the local ledger as the valuation.

Ledger Debit/Credit Account Type Account (No.) Account (Name) Amount

LGAAP Debit General Ledger 65,400,000 Freight 200

LGAAP Credit Assets 16,004,000 Vehicles 200

(Acquisition Cost)

Step 3 - Generated journal entry: Transfers

The system generates the following journal entry:

No. Ledger Debit/Credit Account (No.) Account (Name) Amount

3 LGAAP Debit 65,400,000 Freight 200

LGAAP Credit 16,004,000 Vehicles 200

(Acquisition Cost)

Posting Records and T Accounts

Posting Records

No. Debit Credit Amount Comment

1) Clearing Account -> Payables Domestic 10,200 Cross-Ledger

Asset Acquisition

2) Vehicles -> Clearing Account 10,200 Capitalization of

(Acquisition Cost) Asset Acquisition xed asset; cross-
ledger

3) Freight -> Vehicles 200 Only for Ledger

(Acquisition Cost) LGAAP

T Accounts

This is custom documentation. For more information, please visit the SAP Help Portal 35
 8/16/2024

Retirement

Use
An asset retirement is the removal of an asset (or part of an asset) from the asset portfolio. The transaction is posted as an
asset retirement.

You can distinguish between the following retirement types:

An asset is sold, resulting in revenue being earned. The sale is posted with a customer.

An asset is sold, resulting in revenue being earned. The sale is posted against a clearing account.

An asset has to be scrapped, with no revenue earned.

A xed asset is sold to an affiliated company.

Post Retirement (Integrated AR) – With Customer

App ID:F-92

Use
An asset was sold and revenue was generated. You want to post the asset retirement integrated with Accounts Receivable
Accounting, that is, against a customer.

Procedure
Preparations

1. Specify the customer, against whose account you want to post the retirement revenue, as well as the affected revenue
account.

This is custom documentation. For more information, please visit the SAP Help Portal 36
 8/16/2024
2. Specify the affected asset, the amount of APC that is being retired, and the amount of revenue that was earned.

Note: The system determines and posts the proportional value adjustments on the APC retirement amount
automatically.

3. Check if you are retiring prior-year acquisitions (acquisitions from previous scal years) or current-year acquisitions
(acquisitions in the current scal year). To do this, display the asset values of the asset.

Post Asset Retirement

Post the asset retirement using the app Post Retirement (Integrated AR) – With Customer (F-92). When you do this, you rst
post the revenue (customer invoice to revenue account).

1. Enter the header data on the screen Asset Retirement from Sale with Customer.

This includes Document Date, Document Type DR, Company Code, Posting Date, Currency, Posting Key , and Customer
Account.

Con rm your entries.

2. On the screen Enter Customer Invoice: Add Customer Item, enter the following data:

Amount

Calculate Tax, Tax Code (speci cation for output tax calculation)

Posting Key

Revenue Account for Asset Retirement

Con rm your entries.

3. On the screen Enter Customer Invoice: Add G/L Account Item, enter the following data:

Amount. You can enter "*" in this eld. The system then uses the total of all line items created up to this point as
the posting amount, with reversed debit/credit indicators.

Tax Code

Asset Retirement

Con rm your entries.

4. Enter the asset data on the screen Enter Asset Retirement:

Asset, Asset Subnumber

Transaction Type, for example, for the retirement of prior-year acquisitions (210) or for the retirement of
current-year acquisitions (260).

Asset Value Date

You can post either a complete retirement or a partial retirement:

For a complete retirement: Set the indicator for a complete retirement.

For a partial retirement: Enter the APC amount being retired or a percentage of the APC, or, if quantities
are managed on the asset, the retired quantity.

Based on the percentage or quantity, the system determines the proportional amount, that is, the amount
by which the acquisition cost (APC) is reduced.

If necessary, simulate the document.

This is custom documentation. For more information, please visit the SAP Help Portal 37
 8/16/2024
Post the document.

Example
See Example: Integrated Retirement Posting (with Parallel Valuation).

Example: Integrated Retirement Posting (with Parallel Valuation)

Initial Data
The company creates nancial statements based on two parallel accounting principles:

IFRS accounting principle and

LGAAP accounting principle (local accounting principle)

The enterprise posts asset retirements integrated with Accounts Receivable.

The enterprise sells an asset for a price of 8,500.

According to IFRS, the net book value of the asset is 8,000.

According to the local accounting principle, the net book value of the asset is 9,000.

According to IFRS, there is a loss on the asset retirement; whereas, according to the local accounting principle, there is a gain
from the asset retirement.

The accounts receivable assistant posts the receivable.

Document Entry and Generated Documents

The accounts receivable accountant posts the receivable amount using the app Post Retirement (Integrated AR) - With
Customer (F-92) for all ledgers (that is, without restriction to one ledger):

Document entry:

Debit/Credit Posting key Account type Account (No.) Account (Name) Amount

Debit 01 Customer 12100000 Receivables 8500

Domestic

Credit 50 Asset 70020000 Gain from Asset 8500

Retirement

The system generates a document with the following line items that are posted with different ledger information:

(5) For each ledger: Receivables domestic to revenue from asset retirement

(6) Asset retirement with ledger IFRS: Clearing account for asset retirement to machinery and equipment and to loss from
asset retirement

(7) Asset retirement with ledger LGAAP: Clearing account for asset retirement and gain from asset retirement to machinery
and equipment

This is custom documentation. For more information, please visit the SAP Help Portal 38
 8/16/2024
Generated document with line items:

Remark: For reasons of simpli cation, it is not necessary to display the necessary adjustment of the depreciation values still to
be posted.

No. Ledger Debit/Credit Posting key Account (No.) Account (Name) Amount

5 IFRS and LGAAP Debit 01 12100000 Receivables 8,500

Domestic

Credit 50 70020000 Gain from Asset 8,500

Retirement

6 IFRS Debit 40 70030000 Asset 8,500

Retirement
Clearing Account

Credit 75 16002000 Machinery and 8,000

Equipment

Credit 40 71010000 Loss from Asset 500

Retirement

7 LGAAP Debit 40 70030000 Asset 8,500

Retirement
Clearing Account

Debit 40 71010100 Gain from Fixed 500

Asset
Retirement

Credit 75 16002000 Machinery and 9,000

Equipment

Account Display
The gure below shows the corresponding T accounts.

The system generated documents 2 to 4 during the postings for acquisition and value adjustment.

This is custom documentation. For more information, please visit the SAP Help Portal 39
 8/16/2024

Figure: Integrated Retirement Posting

Post Asset Retirement

App ID: F7107

You can use this app to post asset retirements with revenue as well as asset retirements without revenue. In the case of a
retirement with revenue, you do not post the retirement integrated with the customer invoice, but against a clearing account.
An example of a retirement without revenue is scrapping.

Features
You can use the Post Asset Retirement app to make postings for the following transactions:

Asset retirement with revenue (without integration to Accounts Receivables)

The revenue can be determined as follows:

By manual user input

By automatic determination from the net book value in a speci c depreciation area

The system automatically generates a gain/loss posting to the G/L account that is de ned for it by default or that you
have de ned for it. (In the con guration activity Assign G/L Accounts, you can assign the relevant G/L account to the

This is custom documentation. For more information, please visit the SAP Help Portal 40
 8/16/2024
symbolic accounts KTMEHR (for gain) and KTMIND (for loss).)

Asset retirement without revenue

You post an asset retirement without revenue, for example in the case of scrapping.

The system automatically generates a loss posting on the G/L account that is de ned for it by default or that you have
de ned for it. (In the con guration activity Assign G/L Accounts, you can assign the corresponding G/L account to the
symbolic account KTREST (Pro t and Loss Account for Losses from Asset Retirement Without Revenue, for example, by
Scrapping).)

You can use the following functions:

Function Details

Selection of Ledgers For the posting, you can either select one ledger or all ledgers or
individual ledgers. To select all ledgers, you have the following
options: You select either all ledgers individually or you do not
specify a ledger (you leave the ledger eld empty). The same
applies to the Depreciation Area eld.

Authorization Check The system checks the authorization for all explicitly selected
ledgers or for the ledgers selected indirectly (via depreciation
areas).

Business Transaction Type The types of postings are represented by business transaction
types: The use of the business transaction type facilitates the year-
end closing and the display of transactions in the asset history
sheet.

The following business transaction types are available for asset

retirements:

Retirement with revenue

Retirement Without Revenue

Revenue Determination Either enter the revenue manually. Or you can have the revenue
calculated automatically; in this case, you must specify a
depreciation area whose net book value is then used as revenue.

Currency Type of Revenue You only need to specify the currency type if you specify the
revenue manually. (You can only select currency types that are
managed in the selected depreciation areas.) You enter the
amounts in the transaction currency. The transaction currency can
differ from the functional currency.

Retirement Type The following are the supported types of retirements:

Complete retirement

Partial retirement by amount

Partial retirement by percentage

Acquisition year Both retirements of assets that were acquired in the current year
and retirements of assets that were acquired in previous years are
supported.

This is custom documentation. For more information, please visit the SAP Help Portal 41
 8/16/2024

Function Details

Quantity An explicit quantity speci cation is only possible for a partial

retirement (for a partial retirement by amount or by percentage).
The quantity is deducted during the partial retirement (in addition
to the amount). The quantity does not determine the retirement
percentage.

 Note
It is not possible to change the account assignment in the header and in the line item. This is only possible in the deprecated
apps for asset retirement (ABAON, ABAVN).

Navigation to App
To navigate to the app, you have the following options:

Tile on Launchpad: You can start the app by clicking the Post Asset Retirement tile on the launchpad.

Home ʻmenu’: On the launchpad, you can choose Home All My Apps <Business Catalog> Post Asset Retirement .

'Manage Fixed Assets' app, worklist: You can select an asset from the worklist and then choose Post Post Retirement
Post Retirement with Revenue or Post Retirement Without Revenue.

Supported Devices
Desktop

Tablet

Asset Retirement at Net Book Value (Without Gain/Loss

Posting)

Use
In Asset Accounting, a distinction is made between the following retirement variants for asset retirements: Retirement with
revenue and retirement without revenue (scrapping):

Retirement Without Revenue (Scrapping):

The total of all value types (for example: acquisition costs as well as cumulated ordinary depreciation) is
compared with the loss from scrapping. This value corresponds exactly to the net book value of the retirement.

The posting is made to the G/L account that is assigned to the symbolic account KTREST(G/L Account for Net
Book Value When Scrapped).

Retirement with Revenue

The total of all value elements is compared with the revenue amount.

The posting is made to the G/L account that is assigned to the symbolic account KTERLW (Clearing Account for
Revenue from Asset Sale).

The resulting difference is posted explicitly as gain or loss.

This is custom documentation. For more information, please visit the SAP Help Portal 42
 8/16/2024
The retirement variant of the retirement without revenue is mandatory for some countries, such as France. This means that:
Even if revenue is generated when an asset is sold, the retirement in Asset Accounting is only made at the net book value;
therefore, no revenue and no explicit gain/loss is posted.

The retirement variant without revenue is set by default for the local accounting principles of those countries in the system.

Prerequisites
The retirement variant of the retirement without revenue (Post Net Book Value for Retirement -POST_NBV_RETIREMENT) is
activated for each accounting principle and automatically taken into account by the system for a retirement posting.

 Note
The activation is pre-delivered per accounting principle in the standard cloud content. The setting cannot be changed.

Features

Posting at net book value

As the retirement variant without revenue is set by default for the affected countries, the posting of the asset retirement
occurs automatically in accordance with the corresponding posting speci cations at net book value.

 Note
Up until release SAP S/4HANA 2308, the account KTERWL was used for scrapping instead of account KTREST in the French
accounting principle.

This system behavior has now been changed: The standard retirement from scrapping is posted in accordance with French
law (see also the example below). A different posting variant is used that hides the revenue types and posts the net book
value against account KTERLW only when a retirement with revenue occurs.

This change applies not only to the French accounting principle, but also to the accounting principles in Kazakhstan, Russia,
and Ukraine.

 Recommendation
We recommend that you check and, if necessary, adjust the account determination in the affected country versions.

Parallel accounting principles

If you have parallel accounting principles, note the following: The retirement documents may differ for each ledger. As explained
in the ʻPrerequisites’ section, this depends on the retirement variant set for the accounting principle.

 Example
The accounting principle of the group, IFRS, is assigned to ledger 0L. The local accounting principle for France is assigned to
ledger 2L.

If you now have an asset retirement with a sales revenue that is above the net book value, you have a retirement with
revenue in ledger 0L, while in ledger 2L you have a retirement without revenue at net book value.

Example

This is custom documentation. For more information, please visit the SAP Help Portal 43
 8/16/2024
The following example shows a standard retirement due to scrapping:

Retirement APC Ordinary Write-Down Loss from

(SAP depreciation Expense Scrapping
Standard)

21100000 12600010 (VAT) 16001000 0017001000 64007000 64001000

(Payables) (KTANSW) (KTNAFB) (KTNAFG) (KTREST)

Purchased 1200 200 1000

for 1200
euros, useful
life 3 years

Depreciation 306 306

from
January to
November
(306 euros)

Complete 1000 306 694

scrapping
on 1st
December

Manual Revaluation
Revaluation enables you to revaluate an asset with replacement values (so different to the acquisition cost). For example, you
can perform a revaluation to offset the in ation-related cash devaluation or to apply market value principles for Asset
Accounting.

To manually post a one-time revaluation for a single asset, you can use the Post Asset Revaluation app (F7775). See Post Asset
Revaluation.

To post a one-time revaluation for one or more assets, you can use the API Fixed Asset – Post Asset Revaluation
(API_FIXEDASSETREVALUATION_G4BA). See Fixed Asset – Post Asset Revaluation.

Post Asset Revaluation

App ID:F7775

With this app, you can manually post a one-time revaluation for a single asset.

 Note
The API Fixed Asset – Post Asset Revaluation (API_FIXEDASSETREVALUATION_G4BA) enables you to post asset
revaluation for multiple assets in one request.

For more information about the API, see Fixed Asset – Post Asset Revaluation.

Features
You can post revaluation for an asset that was acquired either in the current scal year (current-year acquisitions) or in a
previous scal year (prior-year acquisitions).

This is custom documentation. For more information, please visit the SAP Help Portal 44
 8/16/2024
If you want to post a revaluation, specify the revaluation amount by which the original acquisition costs (APC) are to be
increased and the corresponding cumulative value for revaluation of ordinary depreciation.

The system then posts (for the selected ledgers and depreciation areas) the increase in APC and, on the other hand, the
increased ordinary depreciation.

As a result, this leads to a net book value that corresponds to the fair value.

 Example
An asset was acquired on 01/01/YYYY. The average useful life is 4 years. The depreciation is straight-line.

Up to now, the xed asset has the following values:

APC: 100,000

Planned Depreciation for YYYY: -25,000

Net book value at year-end: 75,000

Due to in ation, a revaluation is required at the end of the year: The book value of the asset is to be revaluated by 20%.

On the selection screen of the app, you specify the following values:

A revaluation of the APC of 20,000 and

A corresponding revaluation of ordinary depreciation of 5,000

After the posting, the following values result (according to the value display of the Manage Fixed Assets app):

Value Start of FY Change Posted Value Due Value Year End

Asset Balance 0 100,000 100,000 0 100,000

Transaction

Revaluation 0 20,000 20,000 0 20,000

Total APC 0 120,000 120,000 0 120,000

Ordinary 0 -28,750 0 -28,750 -28,750

depreciation

Revaluation of 0 -5,000 -5,000 0 -5,000

ordinary
depreciation

Net Book Value 0 86,250 115,000 -28,750 86,250

The following functions are available for revaluations:

Feature Details

This is custom documentation. For more information, please visit the SAP Help Portal 45
 8/16/2024

Feature Details

Business Transaction Type The types of postings are represented by business transaction
types: The use of the business transaction type facilitates the year-
end closing and the display of transactions in the asset history
sheet.

The following business transaction types are available for manual

revaluation:

Revaluation (RA60)

Selection of Ledgers You can post the revaluation either for one ledger, for all ledgers, or
for individual ledgers. To select all ledgers, you have the following
options: You select either all ledgers individually or you do not
specify a ledger (you leave the ledger eld empty). The same
applies to the Depreciation Area eld.

Authorization Check The system checks the authorization for all explicitly selected
ledgers or for the ledgers selected indirectly (via depreciation
areas).

Acquisition year The asset can be acquired in the current scal year (current-year
acquisitions) or in a previous year (prior-year acquisitions).

If you choose Prior Year as the acquisition year, you can specify the
revaluation of ordinary depreciation separately: for the previous
years and for the current scal year.

Debit/Credit Indicator The debit/credit indicator controls whether the revaluation is a

revaluation or a reduction of the revaluation.

Symbolic Account The system uses the following symbolic accounts to determine the
general ledger account to be posted to:

KTAUFW - Reconciliation account: Revaluation

KTAUNB - Value Adjustment Account: Revaluation of

Ordinary Depreciation

Currency Type You specify the revaluation amounts in the functional currency. The
functional currency is usually the same as the company code
currency.

In the Asset Line Items table as well as in the simulation, the

amounts are also displayed for the other currencies that are
de ned for the respective ledger (for example: Group Currency).

Revaluation Amount for APC You specify the amount by which you want to revaluate the
acquisition costs (APC).

Revaluation Amount for Ordinary Depreciation You specify the cumulative revaluation of ordinary depreciation.

For a xed asset that was acquired in the previous year, you can
distribute the revaluation of ordinary depreciation to the previous
years on the one hand and the current year on the other.

This is custom documentation. For more information, please visit the SAP Help Portal 46
 8/16/2024

Feature Details

Line Item Types (SLALITTYPEs) For revaluations for assets acquired in the current scal year
(current-year acquisitions), you can enter revaluation amounts for
the following SLALITTYPEs:

07143 - Revaluation of APC

07144 - Revaluation of Current Year Depreciation

For revaluations for assets acquired in previous years (prior-year

acquisitions), you can enter revaluation amounts for the following
SLALITTYPEs:

07123 - Revaluation of APC

07104 - Revaluation of the depreciation of the previous

year

07124 - Revaluation of depreciation of PY in current

year

(The SLALITTYPEs are displayed in the Asset Line Items table and
in the simulation.)

Asset Line Items Table Once you have made the necessary entries and before you simulate
the posting, choose the Display and Change Line Items
pushbutton. This enables you to display the asset line items and, if
necessary, change them in company code currency.

By choosing the Adjust Converted Values button, you can adjust

or even delete the amounts converted by the system.

Simulating the Posting We recommend that you simulate the posting before actually
making it.

Worklist You can display the list of posted revaluations and the drafts in the
worklist (view Post Asset Revaluation: Worklist).

Supported Devices
Desktop

Tablet

Postings with Quantities

Use
When you post asset acquisitions and retirements, you can specify a quantity in addition to the currency amount. For such a
posting with a quantity (short: quantity posting), the system updates the quantity change together with the value change. The
quantities are therefore also listed in the corresponding document.

You can also post quantity adjustments without a corresponding value change. For more information, see Quantity Adjustments.

Prerequisites
The following prerequisite must be ful lled in order for you to be able to post with quantities:

This is custom documentation. For more information, please visit the SAP Help Portal 47
 8/16/2024
You have de ned a base unit of quantity in the asset master record of the xed asset. There can only be one base unit of
quantity for each xed asset.

Features

Quantity Posting with Value Change

You can use the following apps to post asset acquisitions and retirements with quantities:

Postings without integration to the vendor or customer invoice:

You post acquisitions with quantities using the app Post Asset Acquisition - And Quantity Adjustment F6488).

You post retirements with quantities using the Post Asset Retirement app (F7107).

Postings with integration to the vendor or customer invoice:

When you use the apps for integrated acquisition or retirement, you can also post quantities at the same time.

However, the following sections only deal with non-integrated acquisition or retirement postings.

When you post with quantities, you post a corresponding value change at the same time. Quantity postings will be updated in
the leading (that is, relevant for the balance sheet) depreciation area of each ledger. Quantity update is not supported in the
other depreciation areas for a ledger.

 Example
You post an asset acquisition in company code 1010 across ledgers, that is, for all ledgers that are intended for the asset.

The system updates the quantity in depreciation areas 01 and 32. No quantity update takes place in depreciation area 15.

If you only want to post a business transaction in one ledger, restrict the posting to the relevant ledger on the selection screen
of the relevant app. The quantity is then only updated in the relevant ledger (or more precisely: in the leading depreciation area
of the ledger).

For a posting with a quantity, the system writes a document to the journal in General Ledger Accounting; this document also
contains the corresponding quantity information.

It is not possible to manage negative quantities on an asset.

Special Features for Partial Retirement

If you want to post a partial retirement with a quantity using the Post Asset Retirement app (F7107), you have the following
options:

Choice of business transaction type:

Retirement with revenue

Retirement without revenue

Selection of retirement type:

Partial retirement by amount

Partial retirement by percentage

Depending on the retirement type, you must specify the following data:

This is custom documentation. For more information, please visit the SAP Help Portal 48
 8/16/2024

Field Partial retirement by amount Partial retirement by percentage

Retirement Amount/Retirement For a partial retirement by amount, you For a partial retirement by percentage, you
Percentage must always enter a retirement amount. must always enter a retirement
percentage.

Quantity The quantity is deducted during the partial retirement (in addition to the amount).

The quantity does not determine the retirement percentage.

 Note
You can restrict the partial retirement to one speci c ledger. If you then enter
the quantity in the Quantity eld, the system calculates and posts the quantity
and value accordingly for the relevant ledger.

However, if you want to post the partial retirement for all ledgers at the same
time, this is only possible if the quantity balances in all ledgers are the same
before the partial retirement. Otherwise, the system cannot determine the
retiring quantity for each individual ledger.

Acquisition year Both retirements of assets that were acquired in the current year and retirements of assets
that were acquired in previous years are supported.

Display of Quantities in the ʻManage Fixed Assets’ App

In the master data area of the Manage Fixed Assets app, you can see the quantity balance for each ledger on the Ledger tab.

In the value display of the Manage Fixed Assets app, you can display the quantities for each document in the document display.

Quantity Adjustments

Use
If you post with quantities, the system updates the value and quantity changes at the same time for the Asset Accounting
transactions.

However, if you make quantity adjustments, you post the quantity (in the amount of the adjustment value) without a value
change.

Prerequisites
For quantity adjustments, the same prerequisite must be ful lled as for postings with quantities: You have de ned a base unit of
quantity in the asset master record of the xed asset. There can only be one base unit of quantity for each xed asset.

The following also applies: An adjustment posting is only possible if the asset has already been capitalized, that is, if postings
already exist for the asset or if it is an asset from the legacy data transfer.

Features
Adjustment Postings for Quantities (Without Value Change)

You can make adjustment postings for quantities using the app Post Asset Acquisition - And Quantity Adjustment F6488). The
system only adjusts the quantity up or down, but it does not change the value.

This is custom documentation. For more information, please visit the SAP Help Portal 49
 8/16/2024

 Example
You have posted an acquisition and then notice that you have made a mistake when specifying the quantity. You now want to
adjust the quantity.

Instead of reversing the complete business transaction (here: acquisition) and posting it again with the adjusted quantity,
you can use the app Post Asset Acquisition - And Quantity Adjustment to adjust the quantity.

You can make ledger-speci c adjustment postings for quantities.

The system also writes a document to the journal in General Ledger Accounting for an adjustment posting.

Activities
Adjust Quantities Without Value Change

To post a quantity adjustment on an asset, proceed as follows in the app Post Asset Acquisition - And Quantity Adjustment:

1. Under General Information, you specify the basic data and specify the dates.

Choose the option Quantity Adjustment as the business transaction type.

2. Make the following entries under Posting Data:

If you want to restrict the quantity adjustment to one or more ledgers, enter that ledger or ledgers.

Specify the Debit/Credit Code:

Increase Quantity (Debit) or

Reduce Quantity (Credit)

Specify the quantity with which the adjustment is to be made.

3. Save your entries.

Reversal

What happens during a reversal?

With a reversal, you reverse (undo) postings. If you reverse an existing journal entry, the system makes an inverse posting for
this journal entry. The original document is reversed by another document that posts to the same combination of
characteristics, but with a reversed +/- sign. The original document remains in the system. After the reversal , there is no net
effect.

Where is the document reversed?

You reverse most of the asset transactions in Asset Accounting. However, certain asset transactions have to be reversed in the
application component that triggered the transaction.

a) Original document in another application component, reversal also

If the transaction was triggered in application components other than Asset Accounting, reverse the posting there. This applies,
for example, to the reversal of the following transactions:

This is custom documentation. For more information, please visit the SAP Help Portal 50
 8/16/2024
Goods/invoice receipt: Receipt with Purchase Order Reference

Settlement of an asset under construction with integration for investment measures; the costs for the asset under
construction were previously collected on a WBS element (see also the section below)

If the document to be reversed was posted in a different application component, only the entire transaction, that is, the
operational document and all related valuating documents, can be reversed.

It is not possible to reverse only part of the business transaction, for example, only the valuating documents or only one of the
valuating (ledger-speci c) documents. This would cause only a part of the transaction to be reversed, which would not be
correct from a business point of view.

If you really only want to reverse a valuating (ledger-speci c) part of the transaction, you can make a manual inverse posting
using the xed asset posting apps and restrict it to the corresponding ledger.

b) Integrated posted document: Reversals in Asset Accounting

You post some transactions in another application component, but you can still reverse them in Asset Accounting. An example
of this:

Original Transaction Application Components of Original Original transaction posted with this app
Transaction

Retirement with Customer Accounts Receivable Accounting and Asset Post Retirement (Integrated AR) – With
Accounting Customer

c) Non-integrated posted document from Asset Accounting: Reversals in Asset Accounting

If you have posted a transaction in Asset Accounting, reverse it there as well. Examples of this are:

Original Transaction Application Component of Original Original transaction posted with this app
Transaction

Acquisition, not integrated Asset Accounting Post Asset Acquisition - And Quantity
Adjustment,

Transaction: Acquisition

Post-Capitalization Asset Accounting Post Asset Acquisition - And Quantity

Adjustment,

Transaction: Post-Capitalization

Retirement, not integrated Asset Accounting Post Asset Retirement

What do you need to consider for a reversal in Asset Accounting?

For a reversal in Asset Accounting, note the following:

App for reversal postings

You reverse a document in the value display of the Manage Fixed Assets app. This also applies to the reversal of settlements for
independent assets under construction.

For information about how to proceed for reversals, see Reverse Journal Entries.

Independent assets under construction

This is custom documentation. For more information, please visit the SAP Help Portal 51
 8/16/2024
If you want to reverse the settlement of an independent asset under construction (AuC), you have to select the settlement
document on the independent AuC, that is, the sending asset, in the value display of the Manage Fixed Assets app. It is not
possible to execute the reversal from the value display of the Manage Fixed Assets app if you have selected the settled
completed asset, that is, the receiving asset.

Assets under construction with integration for investment measures

If you have settled an asset under construction with integration for investment measures and for this asset you rst collected
the costs on a WBS element, then note the following:

You cannot reverse the settlement from the Manage Fixed Assets app. Instead, you must use the app Schedule Project
Controlling Jobs with job template Actual Settlement: Projects (SAP). For more information on this app, see the application
help (product assistance) for R&D / Engineering under Schedule Project Accounting Jobs.

Adjustment of depreciation postings

If you have reversed a business transaction, you do not need to reverse the posting run for the depreciation (depreciation
posting run), it is also not possible. The reason for this is: If you reverse a business transaction and this has the effect that the
depreciation needs to be adjusted accordingly, the system makes this adjustment automatically with the next depreciation run.

Quantity postings

You can either reverse quantity postings without value changes or you can correct them by performing a quantity posting in a
separate app.

For more information about quantity postings in general and quantity adjustments without value changes, see Postings with
Quantities.

Multiple transactions

If there are several transactions and a xed asset account is involved, then the following applies: Be careful when you have an
asset with several transactions, and you want to reverse a transaction that is chronologically immediately after a negative
transaction. In this case, you may have to reverse the negative transaction as well, since the net book value of the asset could
become temporarily negative through the reversal.

 Example
You post an acquisition. You then post a credit memo (negative transaction). If you then reverse the acquisition posting, you
must then also reverse the credit memo.

If you only reversed the acquisition, the credit memo would remain, and a negative net book value would occur. Therefore,
the system issues an error message in such a case.

Legacy data transfer

If you have posted incorrect transfer values during the legacy data transfer, you must reverse the posted transfer document
and post it again. If follow-on transactions have already been posted on the asset, you rst have to reverse all the transactions
in reverse chronological order.

You can read how to do this in the documentation for legacy data transfers under Manual Legacy Data Transfer in the section
“Change Transfer Values Subsequently”.

Reverse Journal Entries

This is custom documentation. For more information, please visit the SAP Help Portal 52
 8/16/2024
You can reverse a journal entry or a settlement for an asset under construction (AuC) directly in the asset value display in the
Manage Fixed Assets app.

The following procedures describe how to reverse non-integrated postings, integrated postings, and settlements for
independent AuCs.

Reverse Non-Integrated Posting

You want to reverse a journal entry that has not been posted integrated. For example, you want to reverse a journal entry that
you originally posted using the app Post Acquisition (Non-Integrated) - With Automatic Offsetting Entry. To do this, proceed as
follows:

1. Call up the Manage Fixed Assets app.

2. From the worklist of assets, select the asset for which you want to reverse a journal entry.

Call the asset valuation for this asset.

3. On the Asset Valuation screen, on the Asset Value Display tab, choose the Journal Entries pushbutton.

Select a scal year.

4. Select the journal entry to be reversed by clicking the link for the journal entry number.

5. In the dialog box with the link list, select the entry for reversing the journal entry (Reverse Journal Entry).

The system copies the parameters for the journal entry to the following dialog box.

6. In the dialog box for the details of the reversal, proceed as follows:

a. Check the posting date and change it if necessary.

b. State the reason for the reversal

c. Con rm your entries.

7. You can display the reversal document in the document overview Reverse Document.

8. To post the reversal document, choose Post.

Reverse Integrated Posting

You want to reverse a journal entry that has been posted integrated. For example, you want to reverse a journal entry that you
originally posted using the app Post Retirement (Integrated AR) - With Customer. To do this, proceed as follows:

1. Call up the Manage Fixed Assets app.

2. From the worklist of assets, select the asset for which you want to reverse a journal entry.

Call the asset valuation for this asset.

3. On the Asset Valuation screen, on the Asset Value Display tab, choose the Journal Entries pushbutton.

Select a scal year.

4. Select the journal entry to be reversed by clicking the link for the journal entry number.

5. In the dialog box with the link list, select the entry for reversing the journal entry (Reverse Journal Entry).

The system copies the parameters for the journal entry to the next screen.

6. On the screen Reverse Document: Header Data, proceed as follows:

This is custom documentation. For more information, please visit the SAP Help Portal 53
 8/16/2024
a. Check the posting date and change it if necessary.

b. State the reason for the reversal

7. To display the reversal document, choose the Display Before Reversal pushbutton.

8. To post the reversal document, go back to the previous screen Reverse Document: Header Data and choose Post.

The reverse document is posted.

Reverse Settlement for Independent Asset Under Construction

You want to reverse a settlement that was previously posted from an independent asset under construction (AuC) to a
completed asset (or several completed assets). The original document was posted using the app Execute Settlement - For AuC.
For a reversal, proceed as follows:

1. Call up the Manage Fixed Assets app.

2. From the asset worklist, select the asset under construction for which you want to reverse a document.

 Note
It is not possible to reverse the settlement from the completed (receiving) asset.

Call the asset valuation for the AuC.

3. On the Asset Valuation screen, on the Asset Value Display tab, choose the Journal Entries pushbutton.

Select a scal year.

4. Select the journal entry to be reversed by clicking the link for the journal entry number.

5. In the dialog box with the link list, select the entry for reversing the journal entry (Reverse Journal Entry).

The system copies the parameters for the journal entry to the next screen.

6. On the screen Reverse Document: Header Data, proceed as follows:

a. Check the posting date and change it if necessary.

b. If you want to display the reversal document for the settlement in advance, you must set the Test Run indicator.

Then choose Simulate.

7. To reverse the settlement, deselect the Test Run indicator and choose the Execute pushbutton.

The reverse document is posted.

Manage Substitution and Validation Rules - For Asset Postings

App ID: F7699

As a con guration expert, you can use this app to create rules that are used to validate asset postings or substitute elds of the
document header at runtime.

Key Features
With this app, you can use validation and substitution rules in the following ways:

This is custom documentation. For more information, please visit the SAP Help Portal 54
 8/16/2024
In validation rules, you can specify how the system should check values that the user has entered for an asset posting.

You can specify that the system issues a warning or error message if a certain precondition is met.

Example: You want the system to issue an error message if a settlement is to be made to an asset with a speci c asset
class.

In substitution rules, you can specify the preconditions under which the system is to ll or overwrite (replace) certain
elds in the document header.

You can therefore de ne preconditions and the substitution itself, that is, the reaction of the system.

Validation and substitution rules affect both manual postings and automatic postings (for example, automatic postings using
APIs or the SAP S/4HANA migration cockpit for legacy data transfer).

Business Context, Rule Types, and Events

Using the app, you create all rules in the business context Asset Accounting - Posting. Validation Rules and Substitution Rules
are available as rule types.

Those elds that you can check by a validation rule or in uence by a substitution rule are grouped into so-called events:

Business Context: Asset Accounting - Posting

Rule Type:
Substitution Rule

Validation Rule

Event:
Assets: Posting Header (Document Header)

Assets: Posting Item (Line Item)

Where and when do the validation and substitution rules apply?

Validation and substitution differ in terms of the supported postings and events as well as the point in time at which the rule
takes effect. The table below explains these differences.

Validation Substitution

Supported Postings You can apply the validation to any posting Substitution rules only have an effect if
to assets, that is, to asset acquisition Asset Accounting is the sender application.
postings (integrated and non-integrated This is the case, for example, with the app
posted acquisitions, legacy data transfer), Post Asset Acquisition – And Quantity
retirement postings, post-capitalizations, Change (F6488).
and so on.

This is custom documentation. For more information, please visit the SAP Help Portal 55
 8/16/2024

Validation Substitution

Supported Events (Document Header, You can de ne the validation for elds of On the other hand, you can only de ne the
Line Items) the document header as well as at line item substitution for selected elds of the
level. document header:

Asset Value Date

(AssetValueDate)

Mapping
(AssignmentReference)

Document Type
(AccountinDocumentType)

Document Header Text

(HeaderText)

Text (ItemText)

Time at which the rule takes effect Validation rules apply to the posted Substitution rules take effect before the
document. This means that the posted document is posted. This means that the
document, to which the precondition prima nota is changed (and not the
applies, is checked. document that has already been posted).

How do I use substitution in detail?

You use the substitution type to de ne possible system reactions: For example, the system can reset (delete) a value, replace it
with a constant, or with a value that is determined using a function.

Substitution Type:
Clear Value:

Substitute with constant

Replace eld/function with

Table Lookup

 Example
You want the document header text of a speci c asset class to be replaced during a post-capitalization.

The Overwrite indicator has the following effect:

If you set the indicator and a value already exists in the document header, this is replaced.

If you do not set the indicator, only initial elds are lled with the substitution value. Existing values, on the other hand,
are not overwritten.

Which rules have an effect on live operations?

A validation or substitution rule can have the following status:

Status:
New

Active

Deactivated

This is custom documentation. For more information, please visit the SAP Help Portal 56
 8/16/2024

Only the active validation and substitution rules are considered by the system at runtime.

Log
The system logs the execution of the validation and substitution rules in the app Logs for Substitution/Validation (App ID
F4886) provided that you have activated the logging for the affected period.

You activate the logging in the app Set Substitution/Validation Logs (App ID F4945).

Authorization Concept
Access to the app Manage Substitution and Validation Rules - For Asset Postings

To be able to access the app Manage Substitution and Validation Rules - For Asset Postings on the SAP Fiori launchpad as
con guration expert for Asset Accounting, you require a business role containing the business catalog Asset Accounting -
Con guration for Postings and Journal Entries (SAP_CA_BC_AA_JE_CONFIG_PC). The business catalog role Con guration
Expert - Business Process Con guration (SAP_BR_BPC_EXPERT) which is provided by SAP as a template contains the
business catalog SAP_CA_BC_AA_JE_CONFIG_PC.

 Note
In addition to the app Manage Substitution and Validation Rules - For Asset Postings, the business catalog
SAP_CA_BC_AA_JE_CONFIG_PC also contains the above-mentioned log apps:

Substitution/Validation Logs (App ID F4886)

Set Substitution/Validation Logs (App ID F4945)

More Information about Authorizations

For more general information on authorizations, see Identity and Access Management.

Supported Devices
Desktop

Tablet

Alternative Fiscal Year Variant and Its Effects on Transactions

Use
You can assign an alternative scal year variant to your local ledger at company code level. As a result, in the ledgers you have
scal years that are not completely identical but rather only partially overlap.

This affects the transactions in Asset Accounting.

Integration

This is custom documentation. For more information, please visit the SAP Help Portal 57
 8/16/2024
The alternative scal year variant is assigned for Finance. It therefore not only affects Asset Accounting transactions, but also
processes of General Ledger Accounting, of Actual Costing/Material Ledger, of Overhead Cost Controlling, and of Product Cost
Planning, as well as integrated processes.

Prerequisites
To be able to use an alternative scal year variant, you must make the settings in the following con guration activity:

Assign Fiscal Year Variants to Ledgers and Company Codes

This con guration activity is mandatory.

Note the prerequisites in Asset Accounting:

You are not allowed to already have asset master data in a company code for which you want to create an alternative
scal year variant.

We recommend that you rst de ne the alternative scal year variant and then de ne the company code settings for
Asset Accounting.

Note also the special features if you calculate depreciation on the basis of half periods (in the standard system, this is the case
for the accounting principle USAP).

For more information on the con guration activity, read the corresponding Con guration Help in the system.

Effects on Asset Accounting Transactions

Initial Example

In ledger 0L (for accounting principle IFRS), you use scal year variant K4, that is, the scal year corresponds to the calendar
year.

In ledger 2L (for your local accounting principle), you use scal year variant V6. The scal year therefore starts on 1st of July and
ends on 30th of June.

The current calendar year is 2022.

Ledgers with Shifted Fiscal Years

Causes for Effects on Transactions

The alternative scal year variant affects Asset Accounting transactions. This may have the following causes:

You want to make a posting for both ledgers, but in one ledger, the relevant scal year is already closed in Asset
Accounting but is still open in the other ledger.

Depending on the ledger, the business transaction falls in different scal years. In the example above, this would be a
business transaction in March 2022.

This is custom documentation. For more information, please visit the SAP Help Portal 58
 8/16/2024

Acquisition

Initial Situation

The following scal years are open in General Ledger Accounting and Asset Accounting:

Ledger FY 2020 FY 2021 FY 2022

(Highlighted in grey) (Highlighted in yellow) (Highlighted in green)

0L Closed Closed Open

2L Closed Closed Open

The current calendar year is 2022. The current calendar month is August 2022.

Acquisition and Post-Capitalization

You want to capitalize a new xed asset; the acquisition should be entered and posted with the date 01/01/2022 (asset value
date).

Entry and Posting

In ledger 0L this can be treated as a normal acquisition; in ledger 2L the posting would refer to scal year 2021 (period
07/2021). However, that scal year is already closed for ledger 2L. You must therefore enter and post the business transaction
as a post-capitalization for ledger 2L in the next open scal year.

You must therefore enter the different transactions for each ledger (that is, ledger-speci c).

You use the Manage Fixed Assets app to create the xed asset and in doing so you set the indicator for the post-capitalization.
You must enter the capitalization date when creating the xed asset.

You use the app Post Acquisition (Non-Integrated) - With Automatic Offsetting Entry to enter the acquisition for ledger 0L. You
restrict the business transaction to ledger 0L.

You use the Post Post-Capitalization app to enter the business transaction for ledger 2L. You restrict the business transaction
to ledger 2L, enter a posting date in the open scal year 2022 (for example, 08/01/2022), and choose a date in the scal year
2021 that is already closed (for example, 01/01/2022, that is, period 07/2021) as the asset value date.

Capitalization

Although the capitalization date of an asset is always the same calendar date in both ledgers, the capitalization date can be in
different periods and scal years for each ledger.

Partial retirement, intracompany transfer, transfer

Partial retirement: Initial Situation

The following scal years are open in General Ledger Accounting and Asset Accounting:

This is custom documentation. For more information, please visit the SAP Help Portal 59
 8/16/2024

Ledger FY 2020 FY 2021 FY 2022

(Highlighted in grey) (Highlighted in yellow) (Highlighted in green)

0L Closed Closed Open

2L Closed Closed Open

The current calendar year is 2022.

Acquisition with Subsequent Partial Retirement

An asset acquisition was posted in all ledgers with the posting date 01/01/2022 (January 2022). In ledger 0L this date is in
scal year 2022, by contrast, in ledger 2L it is in scal year 2021. (The acquisition is marked in the gure with the number 1.)

A partial retirement takes place in August 2022. (This is marked in the gure with the number 2.) In ledger 0L, the partial
retirement refers to current-year acquisitions because the acquisition occurred in the current scal year 2022. However, in
ledger 2L it refers to prior-year acquisitions because the acquisition took place in scal year 2021.

Partial retirement: Entry and Posting

Due to the different references, you cannot enter the business transaction across ledgers. You must enter the business
transaction in two steps instead, and for each ledger separately. As such, the business transaction must be entered in ledger 0L
with a reference different to that in ledger 2L. The system uses the reference to determine a different transaction type for
each ledger.

In the rst step you use the app Post Retirement (Non-Integrated) - Without Customer to enter your partial retirement and
restrict the business transaction to ledger 0L. On the tab Partial Retirement, for the Reference, choose the option Curr.-Year
Acquisition. Post the document.

In the second step, you post the partial retirement for ledger 2L using the same app. Enter your partial retirement and restrict
the business transaction to ledger 2L. On the Partial Retirement tab, for the Reference, choose the option Prior-Year Acquis..
Post the document.

In the example, the ledger-speci c entry is necessary regardless of whether you post an amount-based partial retirement, a
percentage partial retirement, or a quantity-based partial retirement.

Note: If you post a complete retirement, you can post it across ledgers. This is because it is not necessary to differentiate
between current-year acquisitions and prior-year acquisitions.

Summary

No. Transaction Posting Date Ledger Posting Period/ Explanation of

Entry
Fiscal Year of
Ledger

1) Acquisition 01/01/2022 0L 01/2022

2L 07/2021

This is custom documentation. For more information, please visit the SAP Help Portal 60
 8/16/2024

No. Transaction Posting Date Ledger Posting Period/ Explanation of

Entry
Fiscal Year of
Ledger

2) Partial Retirement 08/01/2022 0L 08/2022 App Post

for Ledger 0L Retirement (Non-
Integrated) –
Without Customer

Only for Ledger 0L

Reference: Curr.-
Year Acquisition

3) Partial Retirement 08/01/2022 2L 02/2022 App Post

for Ledger 2L Retirement (Non-
Integrated) –
Without Customer

Only for Ledger 2L

Reference: Prior-
Year Acquis.

Partial Intracompany Transfer and Partial Transfer

Even in the case of an intracompany transfer or partial transfer, the transaction may refer to a current-year acquisition in one
ledger and to a prior-year acquisition in the other ledger. In this case, you also need to enter the transaction for a speci c
ledger.

In the case of a partial transfer, you can enter the business transaction ledger-speci c using the Post Transfer – Within
Company Code app.

In the case of a partial transfer, it is not possible to make a ledger-speci c entry and posting with the Post Transfer – Across
Company Codes Within the Same Country app. Instead, you have to post a partial retirement and an acquisition for each
ledger.

Credit Memo

Initial Situation

The following scal years are open in General Ledger Accounting and Asset Accounting:

Ledger FY 2020 FY 2021 FY 2022

(Highlighted in grey) (Highlighted in yellow) (Highlighted in green)

0L Closed Closed Open

2L Closed Closed Open

The current calendar year is 2022.

This is custom documentation. For more information, please visit the SAP Help Portal 61
 8/16/2024

Acquisition with Subsequent Credit Memo

An asset acquisition was posted in all ledgers with the posting date 01/01/2022 (January 2022). In ledger 0L, the posting takes
place in scal year 2022, by contrast in ledger 2L it takes place in scal year 2021. (The acquisition is marked with the number 1
in the gure.)

You get a credit memo in August 2022. (The credit memo is marked in the gure with the number 2.) In ledger 0L, the credit
memo is to be treated as a credit memo in the invoice year, and in ledger 2L it’s treated as a credit memo in the following year.
The business transaction must be entered in ledger 0L with a different reference and as such they are posted with different
transaction types.

Entry and Posting

Due to the different references, you cannot enter the business transaction across ledgers. You must enter the business
transaction in two steps instead, and for each ledger separately.

In the rst step you use the app Post Credit Memo – In Year of Invoice and restrict the business transaction to ledger 0L. Make
sure that transaction type 105 (Credit Memo in Invoice Year) is used. Post the document.

In the second step, you use the app Post Credit Memo – After Year of Invoice and restrict the business transaction to ledger 2L.
Make sure that transaction type 160 (Credit Memo in Following Year) is used. Post the document.

Summary

No. Transaction Posting Date Ledger Posting Period/ Explanation of

Entry
Fiscal Year of
Ledger

1) Acquisition 01/01/2022 0L 01/2022

2L 07/2021

2) Credit Memo for 08/01/2022 0L 08/2022 App Post Credit

Ledger 0L Memo - In Year of
Invoice

Only for Ledger 0L

With transaction
type 105 (Credit
Memo in Invoice
Year)

This is custom documentation. For more information, please visit the SAP Help Portal 62
 8/16/2024

No. Transaction Posting Date Ledger Posting Period/ Explanation of

Entry
Fiscal Year of
Ledger

3) Credit Memo for 08/01/2022 2L 02/2022 App Post Credit

Ledger 2L Memo - After Year
of Invoice

Only for Ledger 2L

With transaction
type 160 (Credit
Memo in Following
Year)

Reversal

Initial Situation

The following scal years are open in General Ledger Accounting and Asset Accounting:

Ledger FY 2020 FY 2021 FY 2022

(Highlighted in grey) (Highlighted in yellow) (Highlighted in green)

0L Closed Closed Open

2L Closed Closed Open

The current calendar year is 2022.

Acquisition with Subsequent Reversal

An asset acquisition was posted in all ledgers with the posting date 01/01/2022 (January 2022). In ledger 0L this is in scal
year 2022, by contrast, in ledger 2L it is in scal year 2021. (The acquisition is marked in the gure with the number 1.)

Entry and Posting

If you want to reverse a document, the ledger-speci c scal years of the original document must be open. As scal year 2021 is
already closed for ledger 2L, it is not possible to reverse this document. The document can only be reversed when scal year
2022 is open for ledger 0L and scal year 2021 is reopened for ledger 2L.

Depreciation

You have to perform both the depreciation calculation and the posting of depreciation for each ledger.

When posting the depreciation, the system determines the posting date for each ledger based on the parameters Period and
Fiscal Year. If you use several ledgers, that have different scal year variants assigned, this results in a different posting date for
each ledger.

This is custom documentation. For more information, please visit the SAP Help Portal 63
 8/16/2024
Example: You want to execute the depreciation run for the end of June 2022 (in the gure marked with the number 1).

Depreciation Posting Run

Due to changes to assets in ledger 0L, you want to perform a depreciation run at the end of June 2022. For the depreciation run
in ledger 0L, you must specify period 06 and scal year 2022 as parameters. The system uses this to determine the posting
date 06/30/2022.

(For ledger 2L, scal year 2021 is already closed anyway, and no depreciation run can be performed anymore.)

Legacy Data Transfer

The alternative scal year variant also affects the legacy data transfer:

If the legacy data transfer date in one ledger corresponds to the end of the scal year and not in the other, you have to perform
a legacy data transfer at the end of the scal year for one ledger and a legacy data transfer during the year for the other ledger.

Example: You want to perform the legacy data transfer on 06/30/2022 (indicated with the number 1 in the gure).

Legacy Data Transfer

In ledger 0L, you perform a legacy data transfer during the scal year. 06/30/2022 corresponds to period 06/2022.

In ledger 2L, on the other hand, you perform a transfer at the end of the year, that is, in period 12/2021.

For a manual legacy data transfer, proceed as follows:

In the app Make Company Code Settings – Asset Accounting-Speci c, you create a legacy data transfer segment for the
company code with the legacy data transfer date 06/30/2022. Afterwards, you create your legacy data using the Manage
Legacy Assets app.

For ledger 0L, you post the cumulated transfer values at the end of the scal year, that is, on 12/31/2021 (period 12/2021) using
the app Post Transfer Values – For Legacy Asset. You use the Post Miscellaneous Transactions app to post the transactions
that took place in scal year 2022 before the transfer date.

For ledger 2L, you post the cumulated transfer values at the end of the scal year, that is, on 06/30/2022 (period 12/2021)
using the app Post Transfer Values – For Legacy Asset.

Alternatively, you can also perform the legacy data transfer automatically using the SAP S/4HANA Migration Cockpit.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 8/16/2024
Note the following for the legacy data transfer using the SAP S/4HANA migration cockpit: In the XML template for the master
data, you nd the Ledger worksheet. This is used to enter ledger-speci c capitalization dates for an asset.

For more information about the ledger data transfer in Asset Accounting, see Time of Transfer.

Functions Not Supported

The following Asset Accounting function is not supported in a company code in which you use an alternative scal year variant:

You cannot use independent assets under construction. This means that: You can neither create assets under construction nor
settle them to completed assets.

The other unsupported features can be found in the following SAP Note: 3169537 .

Depreciation

Purpose
Impairment of a xed asset caused by use or that which is required by tax depreciation law is mapped using depreciation.
Depreciation reduces the book value of a xed asset.

The following depreciation types are available in the system:

Depreciation types calculated automatically:

Ordinary depreciation

Special depreciation

Depreciation types calculated automatically can also be scheduled manually:

Depreciation types that are normally scheduled manually:

Unplanned depreciation

The automatic calculation of depreciation is controlled by depreciation keys in the system.

 Note
Interest calculation (for example, in the same way as depreciation calculation using a depreciation key) is not supported.

Additional Information
The following sections depict how depreciation is calculated automatically.

You can read how to calculate and post the depreciation values using jobs under Recalculate Depreciation, as well as
Depreciation Posting Run.

Depreciation Types

Use

This is custom documentation. For more information, please visit the SAP Help Portal 65
 8/16/2024
It is de ned for each depreciation area which depreciation types are allowed in this depreciation area. Depreciation types that
are not explicitly permitted this way are rejected by the system with a corresponding error message.

Key Features
The following depreciation types are supported:

Ordinary depreciation

The term ʻordinary depreciation’ refers to the planned depreciation with normal usage of a xed asset. It re ects the planned
distribution of the acquisition cost of a xed asset over the duration of the asset usage.

Special depreciation

Special depreciation is tax-based depreciation that goes beyond the scope of ordinary depreciation. In general, for special
depreciation a percentage depreciation is allowed, possibly scaled within a tax concession period without taking into account
the actual depreciation of the complex xed asset.

Unplanned Depreciation

Ordinary depreciation re ects the depreciation caused by the normal usage of the complex xed asset. Unusual in uences, such
as damage that causes a permanent impairment of the complex xed asset, are entered using unplanned depreciation.

Valuation Methods

Use
The following variables are relevant for the depreciation calculation:

The planned useful life for the xed asset

The planned useful life is de ned in the asset master record.

The valuation method

Features
The valuation methods are prede ned in the system. They are based on the following variables:

Depreciation key

The depreciation key contains all control variables for calculating the planned annual depreciation.

The calculation methods are the most important part of the depreciation key for calculating the different,
automatically calculated depreciation types (ordinary depreciation, special depreciation).

The base method of a calculation method contains the depreciation calculation method in particular.

Further parameters:

The system can factor in a cutoff value (scrap value).

Depreciation Key
This is custom documentation. For more information, please visit the SAP Help Portal 66
 8/16/2024

General Use
The system uses the setting variables from the depreciation key to determine the depreciation amounts for ordinary
depreciation and special depreciation (also for the depreciation types to be calculated automatically).

Available Depreciation Keys

The depreciation keys available in the system are prede ned. SAP provides a set of depreciation keys for each chart of
depreciation (in other words, for each country and/or accounting principle). This ensures that the special valuation rules of a
country or an accounting principle are adhered to with one uni ed manner of depreciation.

 Note
You cannot create any new depreciation keys and you can also not change any existing depreciation keys.

Use in the Asset Class and in the Asset Master Record

Depreciation keys and useful life are assigned in the set of depreciation terms in the asset class (valuation part of the asset
class); this means that the xed assets of an asset class have the same depreciation key and the same useful life.

The depreciation key from the asset class serves as a default value for the asset master record.

 Note
The set of depreciation terms in the asset class (with depreciation key and useful life) cannot be adjusted to suit a
customer’s individual needs.

However, you do have the option of assigning a depreciation key that differs to the default one in the asset master record for
each depreciation area, if necessary.

Structure
The depreciation type is de ned in the depreciation key.

Calculation methods are assigned to each depreciation key for the actual determination of depreciation amounts.

The duration of depreciation can be split into different depreciation phases in the depreciation key. When you enter a
changeover method for one of these phases, the system changes over to the next phase as soon as the event speci ed in the
changeover method has occurred. The system then uses the depreciation calculation that is speci ed in the calculation method
for this phase.

Changeover methods are also assigned to the depreciation key.

The following overview shows the different elements of the depreciation key:

Depreciation key:

Depreciation type (ordinary depreciation or special depreciation)

Depreciation phase

This is custom documentation. For more information, please visit the SAP Help Portal 67
 8/16/2024

Depreciation key:

Calculation method:

Base method

Declining-balance method

Multi-Level method

Period control method

Classi cation of ordinary depreciation (straight line, declining balance, as above)

Changeover method; changeover percentage rate

Effects of multiple-shift operation

In uence of scrap value on the base value

Effect of shutdown periods

Maximum amount method

Additional settings. Examples:

Suspend ordinary depreciation with special depreciation; period control according to scal year; day-exact calculation; do not reduce in
shortened scal year

Additional Information
Background information about the structure of the depreciation key

Information on the calculation methods and parameters de ned in the depreciation keys can be found in the following sections.

App „Depreciation Key: Display Details”

In order to display more detailed information about a given depreciation key in a chart of depreciation, if you have the
corresponding authorization, you can display the app Depreciation Key: Display Details. The app provides you with a detailed
overview of all in uencing factors (calculation methods, depreciation phases, and so on) for the depreciation key.

The app Depreciation Key: You can call up Display Details in the following ways:

Directly from the SAP Fiori launchpad or the App Finder or

Using the Manage Fixed Assets app for a speci c asset:

In the Asset Valuation view. To do this, choose the General Parameters tab page.

The Depreciation Key eld displays the smart link for the speci c depreciation key. Click the smartlink and choose
the link from the popover that navigates you to the Depreciation Key: Display Details.

In the master data view on the Valuation tab page

Calculation Methods

Use

This is custom documentation. For more information, please visit the SAP Help Portal 68
 8/16/2024
The system uses calculation methods for calculating depreciation. The calculation methods are assigned to the depreciation
keys.

The calculation methods are de ned independently of each other. Because of this they can be used in several depreciation keys.

Features
Calculation Methods in the Narrower Sense

In the narrower sense the following methods belong to the calculation methods:

Method Parameters

Base Method
Depreciation type (ordinary depreciation, special
depreciation)

Depreciation calculation method (for example, stated

percentage)

Treatment of end of depreciation

Declining-Balance Method Declining-balance multiplication factor, maximum and minimum

percentage rate

Multi-Level Method Validity date or period, levels, base value, calculation of percentage
or remaining useful life, reduction of base value

Period Control Method Period control for acquisition, subsequent acquisition, retirement,
intracompany transfer

The individual calculation methods, with the exception of the base method, are dependent on the chart of depreciation. This
means you can represent your country-speci c depreciation requirements by means of calculation methods that are chart-of-
depreciation-speci c.

Calculation Methods in the Broader Sense

The following settings belong to the calculation methods in the broader sense:

Setting Explanation

Classi cation of ordinary depreciation: Classes: Straight line, declining balance, or other depreciation

Changeover method; changeover percentage rate To changeover to an alternative calculation method to achieve a net
book value of zero at the end of the planned useful life

Multiple-shift Effects of multiple-shift operation

Scrap value In uence of scrap value on the base value

Shutdown Effect of shutdown periods

Additional Information
You can nd further information on calculation methods in the following sections.

Base Method: Depreciation Calculation Methods

This is custom documentation. For more information, please visit the SAP Help Portal 69
 8/16/2024

Use
The depreciation calculation method is the most important control parameter of the base method. The depreciation calculation
method makes it possible to carry out the numerous different types of depreciation calculation in the system.

Key Features
There are the following depreciation calculation methods, amongst others:

Percentage from Useful Life / Percentage from Remaining Useful Life

There are two variants of this depreciation calculation method:

The system determines a depreciation percentage rate from the total useful life; the rate remains the same for each
year.

The system calculates a new percentage rate for each year based on the remaining useful life. The depreciation
percentage rate rises constantly until it reaches 100% in the last year of the useful life.

Total Percentage Rate in the Tax Concession Period

You use this method to write a certain percentage rate from the depreciation base within a tax concession period. In order to
calculate the current periodic depreciation, the system rst determines the accumulated depreciation up to the period under
consideration. The period depreciation is the difference between the already existing depreciation and the total depreciation
allowed. With subsequent acquisitions, the system automatically catches up depreciation from previous years in a lump sum.

Stated Percentage Rate

In contrast to a total percentage rate, here the percentage rate for each scal year is speci ed. The system uses this
percentage rate for calculating depreciation for each period. For example, you can depreciate 3.5% in each of the rst 12 years,
then 2% a year for 20 years and 1% per year for the remaining 18 years. The total of the percentage rates over the useful life is
always 100%, so that complete depreciation is reached by the end of the useful life.

Percentage Rate from Remaining Useful Life Starting from Changeover Year

This method is used as a changeover method in the next phase in the depreciation key following depreciation within the tax
concession period of an investment support measure. The net book value of the asset will be depreciated over the total useful
life when the tax concession period ends. That is, the actual duration of depreciation encompasses the tax concession period
plus the total useful life that is entered.

Mean Value from Several Areas

When de ning depreciation areas, you can establish dependencies between them by specifying a mathematical formula. This
method allows you to calculate depreciation in one area based on the depreciation in another area using this mathematical
formula. Using this method you can, for example, calculate the mean value of straight-line depreciation and declining-balance
depreciation.

Sum-of-the-Years-Digits Method

An arithmetic sequence is set up based on the total useful life. The depreciation percentage rate is proportional to the
remaining useful life.

Depreciation from real estate leasing

When using this method, the depreciation is determined by the contract values for the lease and not by Asset Accounting.

This is custom documentation. For more information, please visit the SAP Help Portal 70
 8/16/2024

Calculation Method Key for Depreciation Calculation

The calculation method is assigned to the base method of the depreciation key. The method used in a particular calculation can
be seen under Calculation Parameters in the Depreciation Calculation section of the Manage Fixed Assets app. The following
values are possible:

Calculation Method Key for Depreciation Calculation

Calculation Method Description

A Sum-of-the-years-digits method of depreciation

B Depreciation from real estate leasing

C Declining multi-phase depreciation CZ

D Percentage from the useful life

G Total percentage in concessionary period

H Stated percentage, half-year depreciation for Japan

J Declining balance (logarithmic) over total life for Japan

K Declining balance (logarithmic) over remaining life for Korea

L Depreciation according to the present valuation portion of leasing

installment

M Mean value from several areas

N No automatic calculation

P Stated percentage

R Percentage from the remaining useful life*

S Number of units/total number of units

T Number of units/remaining units

U Percentage from remaining life calculated from depreciation conversion date

V Immediate depreciation

X Customer-speci c method 1

Y Customer-speci c method 2

Z Customer-speci c method 3

1 Country/region-speci c method

2 Country/region-speci c method

3 Country/region-speci c method

4 Country/region-speci c method

5 Country/region-speci c method

6 Country/region-speci c method

7 Country/region-speci c method

8 Country/region-speci c method

This is custom documentation. For more information, please visit the SAP Help Portal 71
 8/16/2024

Calculation Method Description

9 Country/region-speci c method

*'R' is set when the method de ned in the depreciation key is 'D, but the multi-level method of the same phase is set to
'Remaining Useful Life'.

Base Method: Treatment of End of Depreciation

Use
In general, the depreciation of a complex xed asset ends when the book value reaches zero or you reach the end of the asset’s
planned useful life. If these differ due to the depreciation method used with the result that, for example, the useful life has
expired but the book value still hasn’t reached zero, it is possible to keep on depreciating past the planned end of useful life. You
can do this by de ning the corresponding setting for ʻtreatment of end of depreciation’ in the base method.

Key Features
The treatment of end of depreciation is de ned in the chart-of-depreciation-independent base method. The following
possibilities exist, amongst others:

Calculation After End of Planned Useful Life

The system continues to calculate the depreciation also after the end of the planned useful life.

Curb

When depreciating past the end of the planned useful life, the depreciation percentage can be derived from the effective useful
life as well as the planned useful life. This results in a declining-balance calculation of depreciation (curbed) instead of straight
line.

 Example
A xed asset with an original planned useful life of 10 years is depreciated in the 11th year with 1/11 = 9,09 %, in the 12th year
with 8,33 % and in the nth year with 100/n %.

 Note
Note that the system determines the depreciation percentage rate after the end of the planned duration period-speci c and
not year-speci c for depreciation below zero with curb.

Depreciation Below Zero

It is possible to depreciate under a book value of zero provided that the depreciation area permits a negative net book value.
Depreciation under a book value of zero may be desired for cost-accounting purposes, for example.

When you use a corresponding changeover method, it is possible to depreciate using a different depreciation key after the end
of the planned useful life. See the section Changeover Method also for this.

Shorten Useful Life to End of Fiscal Year

The end of depreciation of a complex xed asset is normally also during the scal year (so mid-year) due to the year the
depreciation start date is in. Treatment of end of depreciation can be de ned in such a way that the speci ed useful life is
This is custom documentation. For more information, please visit the SAP Help Portal 72
 8/16/2024
reduced so that the depreciation end always coincides with the end of a scal year.

Declining-Balance Method

Structure
For the declining balance depreciation of complex xed assets there are several methods. The declining-balance method is
determined by the following factors:

Declining-balance multiplication factor

The multiplication factor is used in determining the depreciation percentage rate for declining-balance depreciation. The
system multiplies the depreciation percentage rate resulting from the total useful life with straight-line depreciation by
this factor.

Maximum percentage rate

This determines the upper limit for the depreciation percentage rate.

If a higher depreciation percentage rate is produced from the useful life, multiplication factor or number of units to be
depreciated, then the system uses the maximum percentage rate speci ed here.

Minimum percentage rate

This forms the lower limit for the depreciation percentage rate.

If a lower percentage rate is produced from the useful life, multiplication factor, or number of units to be depreciated,
then the system uses the minimum percentage rate speci ed here.

The following declining-balance methods exist, amongst others:

Declining-balance method of depreciation

Declining multi-phase depreciation

Sum-of-the-years-digits method of depreciation

Examples
More explanations and examples can be found in the following sections:

Declining-Balance Method of Depreciation

Declining Multi-Phase Depreciation

Sum-of-the-Years-Digits Method of Depreciation (Digital)

Period Control Method

Use
On order to determine the depreciation start/end date for asset transactions, in the period control method there can only be
one period control to be used for the following transaction categories:

Acquisitions

This is custom documentation. For more information, please visit the SAP Help Portal 73
 8/16/2024
Subsequent acquisitions/post-capitalization

Transfer Postings

Retirements

This lets, for example, the depreciation start to be set for all acquisitions of a year to the beginning of the year and, for
retirements to the rst or last day of a period. Using the asset value date of a transaction (acquisition or retirement), the
system determines the start date or end date of depreciation calculation using the period control.

Key Features
Standard Period Control

The most important standard period controls are the following:

Period Control Explanation

Pro rata at the start of the period The depreciation start/end date is always set to the beginning of
the period in which the asset value date for the
acquisition/retirement lies.

Pro rata at the start of the period, up to the middle of the period The depreciation start/end date is set to the beginning of the
period for transactions in the rst half of the period. For
transactions in the second half, it is set to the beginning of the next
period.

Pro rata in the middle of the period This rule is the same as the rst rule, however it is intended for the
calculation of depreciation based on half-periods.

First year convention of a half-year (See example.)

Beginning of year / middle of year / end of year For transactions on the rst day of a scal year, complete
depreciation for the year is calculated; for transactions in the rst
half, depreciation is calculated for a half year; for transactions in
the second half, no depreciation is calculated.

At the beginning of the year

In the middle of the period

At the end of the period (beginning in the subsequent year)

In the middle of the quarter (Compare the period control pro rata at the middle of the period.)

At the rst quarter

At the following quarter/following month

At the following half-year Transactions up to the middle of the scal year have a depreciation
start date in the middle of the year. Transactions after the middle
of the scal year have a depreciation start date in the following
year.

 Example
First year convention:

To June 30th Depreciation start date/end in period 0

From June 30th until December 31st Depreciation start date/end in period 6

This is custom documentation. For more information, please visit the SAP Help Portal 74
 8/16/2024
The system interprets period 0 as the start of the scal year (January 1st), not period 1. Period 6 represents July 1st.

Half-Periods

The number of posting periods in Asset Accounting generally corresponds to the number of posting periods in Financial
Accounting. However, it is possible to double the number of depreciation periods if the basic number of posting periods
corresponds to the number of calendar months (12). It may be de ned in the company code that the system works with half
periods. The depreciation calculation can then start and end in the middle of a period (so-called mid-quarter convention (USA)).

Variable Period Control

It may be speci ed in the de nition of the individual depreciation keys that the keys do not use the period controls of the
corresponding period control methods, but use company code-speci c and scal year-speci c period controls instead.

This may be necessary, for example, when depreciating according to US law, if you only apply the mid-quarter convention to
acquisitions in speci c company codes or scal years.

Multi-Level Method

Use
Base methods with depreciation calculation methods that depreciate using a whole percentage rate or using a period
percentage rate (depreciation methods stated percentage rate and whole percentage rate in a tax concession period) can be
split over levels. Each level represents a validity period for a given percentage rate. This percentage rate is then replaced with a
subsequent level once the validity period has come to an end.

Features
Validity period of the individual levels

The validity periods of the individual levels of a multi-level method key are de ned by entering the duration in years and months.
The de ned validity periods can begin at the following call-up points:

From the capitalization date

From the start date of ordinary and/or special depreciation or

From the original acquisition date of the asset under construction

From the changeover year

As the de ned periods of a key always have a joint start date, they overlap respectively from the joint start date up to the end of
the previous level. The validity periods of the individual levels are therefore represented in cumulative form.

For non-calendar scal years you can de ne that the system refers the periods and annual input in the level de nitions to the
scal year and not the calendar year. Note the special features of shortened scal years.

Depreciation percentage rates

The entry of the depreciation percentage rate depends on the depreciation method used:

For the depreciation method Whole percentage rate in tax concession period, you must also specify the depreciation
percentage rates in cumulative form (see example below).

This is custom documentation. For more information, please visit the SAP Help Portal 75
 8/16/2024
For the depreciation method Stated percentage rate, you must specify the depreciation percentage rates non-
cumulative.

 Example
There are ve levels; each level should last one year. The depreciation method used is Whole percentage rate in tax
concession period. The depreciation percentage rates in the individual years are 60, 10, 10, 10, and 10%.

Validity period Percentage rate

1 year 60

2 years 70

3 years 80

4 years 90

5 years 100

In addition you can limit the levels to certain acquisition years so that you can accommodate legal requirements that apply
for a limited time period.

Base Value for Depreciation

Use
The base value for depreciation is closely linked to the selection of the depreciation calculation method . Since it is not logical to
use every depreciation method with every base value, the base value is often already determined by the depreciation method.
The following base values are de ned in the system:

Acquisition value

Acquisition value less unplanned depreciation

Half of acquisition value

Replacement value

Half of replacement value

Current net book value without special depreciation

Average net book value

Average net book value without special depreciation

Current net book value

Accumulated ordinary depreciation

Accumulated special depreciation

Sum of accumulated ordinary and special depreciation

Limited base value (see below)

 Caution

This is custom documentation. For more information, please visit the SAP Help Portal 76
 8/16/2024
Since revaluation takes place with reference to a speci c point in time and not according to a period of time, the system
does not calculate a mean value for the annual revaluation portion of the asset value when calculating the average net book
value.

Key Features
Reducing Percentage Rate

You can reduce the base value for the calculation of depreciation by entering a reduction percentage rate. Entering 50.0000,
for example, results in reducing the base value by one half. The reducing percentage rate is de ned in the multilevel de nition of
the multilevel method.

Limited Base Value

Limited acquisition value means that the system uses a speci ed maximum amount as the base value for depreciation.

If the acquisition value of the asset is under this maximum amount, the system uses the actual acquisition value as the
basis for depreciation.

If the acquisition value exceeds this maximum amount, depreciation is based on the maximum amount speci ed.

You can set a maximum base value per depreciation area and asset class in a given company code. In addition, you can set a
time limit on it by entering a "valid to" date. This time limitation relates to the capitalization date of the asset, and therefore
can only be set once for each asset. It is, therefore, not possible to assign different maximum base values to an asset in the
individual years during its useful life.

 Note
You can use the BAdI FAA_DC_UPA_CUSTOMER and its interface method SET_MAX_BASE_VALUE to de ne your own
maximum base values.

Note that the BAdI is only available in a 3-system landscape.

For more information about the BAdI and its interface methods, see the BAdI documentation.

Depreciation per Asset Value Date

The system lets you choose to depreciate acquisitions in the original acquisition year either starting from the depreciation start
date or from the asset value date of the acquisition. If you choose the depreciation start date, the system carries out uniform
depreciation for all acquisitions to an asset. If you choose the asset value date, the system depreciates each acquisition to the
asset starting from the asset value date of the individual acquisition posting.

Base Value Key for Depreciation Calculation

The base value used in a calculation can be seen under Calculation Parameters in the Depreciation Calculation section of the
Manage Fixed Assets app. The following values are possible:

Base Value Key for Depreciation Calculation

Base Value Description

01 Acquisition value

02 Half of acquisition value

This is custom documentation. For more information, please visit the SAP Help Portal 77
 8/16/2024

Base Value Description

03 Replacement value

04 Half of replacement value

05 Limited replacement value

06 Replacement value reduced by reserves

10 Acquisition value reduced by unplanned depreciation

11 Acquisition value reduced by special depreciation

12 Acquisition value reduced by unplanned depreciation (without write-

up)

13 Acquisition value reduced by cumulated unplanned depreciation

14 Acquisition value reduced by reserves

20 Net book value without special depreciation and current depreciation

21 Net book value without special depreciation

22 Mean net book value without special depreciation

23 Net book value without current depreciation

24 Net book value

25 Mean net book value

26 Remaining net book value without revaluation

27 Net book value with proportional value adjustments

28 Reduced base value (asset-speci c reduction)

29 External base value from real estate leasing

30 Accumulated ordinary depreciation

31 Cumulative special depreciation

32 Accumulated ordinary and special depreciation

40 Acquisitions

51 Ordinary depreciation on the transaction

G1-G9 Country/region-speci c base values

Changeover Method

Use
To depreciate the net book value to zero by the end of the xed asset’s useful life, for some depreciation methods it is necessary
to switch to an alternative calculation method. An example for this is the declining-balance method of depreciation, which
mathematically never achieves a book value of zero.

Therefore, calculation methods are de ned in the depreciation keys which specify when the system is to use a different
calculation method (for example, Changeover as soon as the net book value percentage rate is reached). The changeover

This is custom documentation. For more information, please visit the SAP Help Portal 78
 8/16/2024
method also speci es the conditions under which the changeover takes place. A net book value percentage rate is also de ned
for different changeover methods.

The duration of depreciation can be split into different depreciation phases in the depreciation key. When you enter a
changeover method for one of these phases, the system changes over to the next phase as soon as the event speci ed in the
changeover method has occurred. The system then uses the depreciation calculation that is speci ed in the calculation method
for this phase.

Changeover Methods in Detail

The following changeover methods exist, amongst others:

Changeover as soon as the depreciation amount of the changeover method is higher

Here, the result of the depreciation calculation in one phase of the depreciation key is compared with the result in the following
phase. The system performs the changeover as soon as depreciation in the following phase is higher than in the previous phase.

Changeover as soon as the net book value percentage is reached

With this changeover method, the changeover takes place as soon as the net book value falls below a speci ed percentage of
the acquisition value.

Changeover as soon as the net book value percentage rate is less or same as x%

With this changeover method, changeover takes place as soon as the net book value is equal to the speci ed percentage rate of
the acquisition value or lower.

Changeover as soon as the net book value is less than straight-line rate

A straight-line depreciation rate is calculated from the the useful life which is then compared to the net book value. If the net
book value falls below this straight-line rate, changeover to another method takes place.

Changeover after the end of planned useful life

When the planned useful life has expired, changeover to another method can also take place. Sum-of-the-years-digits methods
in particular are de ned only during the useful life. If a post-capitalization is posted after expiration of the planned nish, a
different method must be used.

With the changeover at the end of the planned useful life, the conversion to a speci ed changeover method occurs period-
speci c. With other changeover methods, the changeover takes place according to scal years. The changeover criteria are
checked in relation to depreciation for the entire year, and the depreciation for the entire scal year is either calculated with the
original key or with the new changeover key.

Changeover in next year as soon as straight-line depreciation is higher (Poland)

This is functionally the same as changeover when depreciation amount of changeover method higher, except that the
changeover is not performed until the following year.

Time of the Changeover

For the functions for year-end carryforward, recalculate values, and posting of transactions, the system decides if a phase
change needs to be carried out. For this check, the system uses by default the annual values.

However, one exception is the changeover after end of useful life: This is carried out on a period basis. If the end of the planned
useful life does not fall at the end of a scal year, the system decides which method applies for each activity (year-end
This is custom documentation. For more information, please visit the SAP Help Portal 79
 8/16/2024
carryforward or transaction), based on the asset value date. However, it does not calculate using two methods for one activity
(period before the end of the planned useful life and the period after the end of planned useful life). When deciding which
method is valid, it is only relevant whether the asset value date of the relevant transaction is before or after the end of planned
useful life. This means that a changeover after the end of the planned duration for a year-end carryforward takes place only at
the end of the scal year that follows the end of the useful life. In case of a transaction, the system decides on an individual
basis whether the value date lies before or after the end of the useful life.

 Note
A changeover to a different percentage rate or base value in the multilevel method is not considered a changeover method
in the above sense. The changeover to another level takes place at the exact period for each transaction.

 Note
You can use the BAdI FAA_DC_UPA_CUSTOMER and its interface method SET_CHANGEOVER_YEAR to de ne the changeover
year and, if necessary, the changeover period.

Note that the BAdI is only available in a 3-system landscape.

For more information about the BAdI and its interface methods, see the BAdI documentation.

Example
Example: Changeover after the end of planned useful life

Example: Changeover after the end of planned useful life

In the example, the following conditions apply for an asset:

Start date of depreciation: 7/1/2009

Useful life: 5 years

End of useful life: 6/30/2014

Acquisition cost: 100

Depreciation Method: Straight-line, percentage rate based on useful life, base value 100% of acquisition cost

Changeover after the end of useful life: linear; Percentage rate based on useful life, base value 50% of acquisition cost

This results in the following course of depreciation:

2009: 10 (100/60*6)

2010: 20 (100/60*12)

2011: 20 (100/60*12)

2012: 20 (100/60*12)

2013: 20 (100/60*12)

2014: 18 (100/66*12) or 2010: 10 (100/60*6)

This is custom documentation. For more information, please visit the SAP Help Portal 80
 8/16/2024
2015: 10 (50 /60*12)

The changeover therefore does not take place in the year 2014 is, but the useful life is internally increased by 6 months and
continues with the old method of calculation as it was de ned that, after the end of the useful life, depreciation should continue
below zero. If you do not want this, you must change the base method so that the calculation is only performed up to the end of
the useful life and not below zero.

A transaction with an asset value date up to 6.30.2014 is calculated with the calculation methods of the old phase. A transaction
with an asset value date after 7.01.2014 is calculated based on the changeover method with calculation methods of the next
phase.

Maximum Amount Method

Use
The maximum amount method is used to de ne up to which amount the system should depreciate up to a certain calendar
date. This makes it possible to map legal requirements that, for example, only allow depreciation up to a certain amount for
certain xed assets. The system then depreciates only until the amount is reached within the de ned period.

In contrast to the maximum base value, with the maximum amount method you do not assume a limited, zero base value
possibly below the actual acquisition value. In fact, the system calculates the depreciation independent of an acquisition value.
As soon as the de ned maximum amount is reached, no more depreciation is calculated.

The maximum amount can be valid for the annual or the accumulated depreciation.

 Note
You can use BAdI FAA_DC_UPA_CUSTOMER and its interface method SET_MAX_DEPRECIATION_AMOUNT to de ne your
own maximum amounts that are valid for annual depreciation or accumulated depreciation.

Note that the BAdI is only available in a 3-system landscape.

For more information about the BAdI and its interface methods, see the BAdI documentation.

Cutoff Value Key or Explicit Scrap Value

Use
For certain types of valuation, it makes sense, or is legally required, that you end depreciation when a certain value is reached.
The system offers the following options:

You specify an absolute scrap value explicitly in the asset master record, or

a percentage cutoff value (scrap value) is de ned by a cutoff value key.

Key Features

Cutoff Value Key

The following is de ned in the cutoff value key:

This is custom documentation. For more information, please visit the SAP Help Portal 81
 8/16/2024
the percentage of the depreciation base that should be used as the cut-off value percentage

whether the cut-off value percentage should be deducted at the start or the end of the calculation of depreciation

at what point in time the system should start calculating the validity period for the de ned cutoff value percentage rate

There can be different cutoff value percentage rates depending on the cutoff value key. You can de ne the cut-off
percentages/levels per acquisition year, and the validity period can be of any length.

 Example

Start of the validity period: Capitalization Date

Period of validity: 5 years

Percentage rate: 5%

A cutoff percentage rate of 5% is valid for assets that, calculated from their capitalization date, are no older than 5 years
old.

Explicitly De ned Scrap Value

The scrap value is not depreciated.

When maintaining the depreciation area-speci c asset master data, you can specify an absolute scrap value, and/or a
percentage rate, in the detail screen of each depreciation area. If you enter both, the system uses the percentage by default.

 Recommendation
We recommend that you always enter a percentage rate.

If you de ned a cutoff value key, the system ignores the cutoff value percentage of the key and treats the amount entered in the
asset master record as the scrap value. Depending on the cutoff value key, the amount is either subtracted from the
depreciation base before the depreciation calculation start date, or depreciation ends when the value is reached.

Memo Value

The system re ects the memo value by reducing the planned annual depreciation of the acquisition year by the amount of the
memo value.

 Recommendation
It is not normally necessary to manage memo values, since Asset Accounting always considers gross values (that is,
acquisition values and value adjustments), and not just the remaining book value. This fact ensures that fully depreciated
assets with a book value of zero are also shown in all legally required reports.

Extensibility

 Note
You can use the BAdI FAA_DC_UPA_CUSTOMER and its interface method SET_MIN_NETBOOK_VALUE to de ne the
minimum net book value in percent of the APC or as an explicit amount. You can also de ne whether a minimum net book
value should be deducted from a base value at depreciation start or whether the depreciation should be continued after the
net book value of zero was reached.

Note that the BAdI is only available in a 3-system landscape.

This is custom documentation. For more information, please visit the SAP Help Portal 82
 8/16/2024
For more information about the BAdI and its interface methods, see the BAdI documentation.

Further Settings in the Depreciation Key

Use
The depreciation key can contain further settings that are relevant for calculating depreciation.

Key Features
Suspend ordinary depreciation with special depreciation

With special depreciation, the system suspends ordinary depreciation, in other words, ordinary depreciation is set to zero.

Period control by scal year

In certain depreciation keys it can be de ned that the period controls apply differently from the period control methods for
selected company codes and scal years.

This may be necessary, for example, when depreciating according to US law, if you only apply the mid-quarter convention to
acquisitions in speci c company codes or scal years.

Depreciation by day

If this is the case, the system executes the depreciation calculation exact to the day. With this, the period control rules of the
depreciation key are suspended for the whole duration of the useful life of the xed asset.

 Note
Note that the 29th of February in a leap year is only taken into account when there was a transaction in this year on the
affected xed asset. If no transaction takes place in a leap year, then the annual depreciation of this leap year is just as high
as in a normal year.

This special handling is in line with a legal requirement in France.

Depreciation calculation in shortened scal years

In this case, depreciation is not shortened in shortened scal years, even if area-speci c de nitions exist at company code level.

Acquisitions only in the capitalization year

Here the system only allows further acquisitions in the year of the depreciation start. This can be technically necessary, for
example, if sum-of-the-years-digits depreciation was used. In addition, this function can be used for organizational purposes.

Number of digits when rounding

This setting de nes how many digits are used in rounding for the depreciation calculation of the percentage.

 Note
You can use the BAdI FAA_DC_UPA_CUSTOMER and its interface method SET_ROUNDING to de ne rounding settings.

Note that the BAdI is only available in a 3-system landscape.

This is custom documentation. For more information, please visit the SAP Help Portal 83
 8/16/2024
For more information about the BAdI and its interface methods, see the BAdI documentation.

Depreciation class

The depreciation class serves as a classi cation of ordinary depreciation (aforementioned straight line, declining balance).

Multiple-shift operation

This de nes whether the system calculates increased depreciation amounts due to increased impairment of a xed asset
through multiple-shift operation.

In uence of scrap value on the base value

This de nes how the scrap value should affect the base value (for example, reduction of base value).

You should make this setting only if you use a depreciation key that uses different calculation methods in different phases, and
the scrap value is treated differently in different phases. Normally the scrap value is treated the same in the depreciation key
over the entire useful life

Calculate shutdown

By specifying shutdown periods when maintaining the asset master record, you ensure that depreciation is suspended during
the shutdown periods.

Depreciation Methods
The depreciation keys, with their calculation methods and parameters, let you represent the most varied depreciation methods
in the system. The following sections describe the most important depreciation methods and their representation in the
system, and give examples.

Additional Information
In order to display more detailed information about a given depreciation key in a chart of depreciation, if you have the
corresponding authorization, you can display the app Depreciation Key: Show Details. The app provides you with a detailed
overview of all in uencing factors (calculation methods, depreciation phases, and so on) for the depreciation key.

Straight-Line Depreciation over Total Useful Life

Use

The asset is depreciated uniformly over the speci ed total useful life. Post-capitalization and subsequent acquisitions
necessitate an increase in depreciation, by the amount that would have been necessary to fully depreciate the subsequent
acquisition over the original useful life of the asset. This results in an increase in the length of time necessary to depreciate the
asset, that is, the time period from the beginning of depreciation until the book value of zero is reached.

Calculation:

Depreciation = APC / expected useful life

 Example
APC: 1,000

This is custom documentation. For more information, please visit the SAP Help Portal 84
 8/16/2024
Useful life: 10

Depreciation = 1000 / 10 = 100

A depreciation key, which determines a percentage rate from expected useful life and uses the acquisition value or replacement
value as the base value for depreciation, characterizes this depreciation method. Furthermore, certain depreciation keys (in
their base method) allow depreciation below book value zero after the planned life has expired.

In this case, the rate of depreciation can decrease after the planned life because you can then use the already expired useful life
instead of the planned expected useful life to calculate depreciation. In the 11th year of use, you would not use 10% for the
calculation as in the preceding 10 years, instead you would use 1/11 = 9.0909%.

Straight-Line from the Book Value over Remaining Useful Life

Use

The book value of the xed asset is distributed in uniform amounts over the remaining life. However, unlike straight-line
depreciation over the total useful life, this method ensures that post-capitalization and subsequent acquisitions do not lead to
an extension of expected useful life. Post-capitalization or subsequent acquisitions after the expiration of the speci ed expected
useful life do, however, cause problems in this depreciation method. In such cases, the changeover key in the depreciation key
used has to provide for another method after the expiration of the expected useful life.

Calculation:

Depreciation = net book value / remaining life

 Example

APC: 1000

Useful life: 10

Net book value: 500

Remaining useful life: 5

Depreciation = 500 / 5 = 100

You can represent this depreciation method in the system, for example, with a depreciation key that calculates a depreciation
percentage rate from the remaining life, due to the depreciation calculation method Percentage from the useful life being set in
its base method, and the Rem. life indicator being set in the multi-level method. Furthermore, the base value indicator "24" in
the multi-level method ensures that the net book value is the basis for depreciation. The net book value and the remaining life
are related proportionally, which results in straight-line depreciation. In the event of acquisitions after the expiration of the
expected useful life, the depreciation key switches to a new phase after the planned end of useful life. The new phase is set up
for straight-line/remaining life/pro rata/to zero/to end of life. As a result, these subsequent acquisitions are also depreciated
completely.

Declining-Balance Method of Depreciation

Use

This is custom documentation. For more information, please visit the SAP Help Portal 85
 8/16/2024
For the declining-balance method, the asset is depreciated by a progressively falling rate. A constant percentage rate is
calculated from the expected useful life and a given multiplication factor, which is multiplied with the falling net book value of
the asset. For mathematical reasons, the net book value can never reach zero using this method. Therefore, the SAP system
changes the method to straight-line or complete depreciation under certain conditions:

Declining-balance method of depreciation < straight-line depreciation

Net book value < x percent of acquisition value

Net book value < xed amount

Net book value < straight-line depreciation

The changeover method is speci ed in the internal calculation key.

For more information, see Changeover Method.

Calculation
Depreciation = net book value * percentage rate from useful life and factor

 Example
APC: 1000

Useful Life:10

Net Book Value: 700

Multiplication factor: 3

Depreciation = 700 * (100% / 10 * 3) = 210

Declining Multi-Phase Depreciation

Use

By specifying the rate of depreciation and the validity period, you can determine a course of depreciation that changes in levels
over time (usually decreasing). The validity period can be based, among other things, either on the capitalization date or on the
depreciation start date. The change between the levels of depreciation does not have to take place at the start or end of a scal
year. You can also change to another rate of depreciation during the scal year.

Calculation :

Depreciation = Acquisition value * percentage rate of the level

 Example

APC: 1000

useful life: 50

Percentage rate year 1-8: 5.00%

This is custom documentation. For more information, please visit the SAP Help Portal 86
 8/16/2024
Percentage rate year 9-14: 2,50%

Percentage rate year 15-50: 1.25%

Depreciation level 1 = 1000 * 5.00% = 50

Depreciation level 2 = 1000 * 2.50% = 25

Depreciation level 3 = 1000 * 1.25% = 12.5

When you de ne the depreciation levels in the system, you have to enter the period of validity for the individual depreciation
levels as cumulative values (see Multi-Level Depreciation ).

Sum-of-the-Years-Digits Method of Depreciation (Digital)

Use
The total of the remaining life is mapped in each individual year over the entire useful life. The depreciation percentage rate of a
scal year is then derived from the respective remaining life, divided by this total. The result of this method leads to
depreciation amounts that are reduced by the same amount in each period.

As the remaining useful life is no longer de ned after the end of the planned useful life, you can no longer depreciate using this
method once the planned useful life has expired. However, it is possible to change over to another method once the expected
useful life has expired. For more information, see Changeover Method.

Acquisitions after the depreciation start year or post-capitalization would cause a positive net book value at the end of the
planned useful life. For this reason, such transactions are not allowed with the sum-of-the-years-digits method of depreciation.
Subsequent acquisitions must be created here as sub-numbers for the asset. In addition, it is a requirement of digital
depreciation that the acquisition year and depreciation start year are identical.

Calculation
Depreciation = APC * remaining useful life (current period) / total of remaining useful life (over all periods)

 Example
APC: 1000

Useful life: 4

Total remaining useful life: 10 (= 4 + 3 +2 +1)

Depreciation 1st year = 1000 * 4 / 10 = 400

Depreciation 2nd year = 1000 * 3 / 10 = 300

Depreciation 3rd year = 1000 * 2 / 10 = 200

Depreciation 4th year = 1000 * 1 / 10 = 100

This is custom documentation. For more information, please visit the SAP Help Portal 87
 8/16/2024

Mean Value Method

Use

You can manage the mean value of two depreciation methods in a derived depreciation area that links the values of the two
depreciation areas. In order to do so, you have to identify the derived depreciation area as a mean value area. Instead of using
the arithmetic mean, you can also link the areas proportionally.

Linking formula for the mean value:

Depreciation = (depreciation in area 1) / 2 + (depreciation in area 2) / 2

 Example

Depreciation in area 1: 300

Depreciation in area 2: 100

Formula: (depreciation in area 1) / 2 + (depreciation in area 2) / 2

Depreciation = 300 / 2 + 100 / 2 = 200

Depreciation for Multiple-Shift Operation and Shutdown

Use
For assets that produce in multiple shifts, increased depreciation should be calculated often. However, no depreciation should
be calculated for assets that have shutdown periods. For this purpose, in the Manage Fixed Assets app, the following
parameters are provided in the time-dependent depreciation terms of a xed asset:

Shift Factor

Portion of Variable Depreciation

Shutdown Indicator

Features

Multiple-shift operation

You can calculate increased depreciation due to multiple-shift operation for all types of depreciation methods except for units-
of-production method of depreciation (units-of-production depreciation is 100% variable anyway). You can take into account the
increased wear and tear on xed assets in the Manage Fixed Assets app as follows: In Fixed Asset Valuation, on the General
Parameters tab, you specify the following parameters for a time interval:

Portion of Variable Depreciation

Shift factor

The total depreciation amount is then calculated as follows:

Depreciation amount = xed depreciation + (variable depreciation * shift factor)

This is custom documentation. For more information, please visit the SAP Help Portal 88
 8/16/2024

 Example
The following example shows the depreciation amounts for a xed asset with 1,000 annual depreciation and a variable
portion of 60%:

shift factor 0: 400 + (0 * 60 * 1000/100) = 400 (only xed portion)

shift factor 1: 400 + (1 * 60 * 1000/100) = 1,000

shift factor 2: 400 + (2 * 60 * 1000/100) = 1,600

shift factor 3: 400 + (3 * 60 * 1000/100) = 2,200

Expired Useful Life

In the de nition of the depreciation key, you can specify the following for multiple-shift operation:

Whether depreciation and the expired useful life should be increased

Whether only depreciation should be increased and not the expired useful life

Whether no increase of depreciation or expired useful life should occur

By using these options, you can ensure, for example, that depreciation is increased during the declining-balance phase, but that
the straight-line phase after the changeover continues until the end of the planned useful life.

Multiple-Shift Operation for Fixed Assets with Declining-Balance Method of Depreciation

For assets using declining-balance depreciation, the system increases depreciation amounts during the declining-balance phase
of depreciation, based on the multiple-shift factor and the variable portion of depreciation. However, depreciation is only
increased up to the maximum percentage rate that is speci ed in the depreciation key.

Shutdown

If an asset is shut down for a given period of time, you can suspend the depreciation as follows:

De ne a corresponding time interval for the xed asset in Fixed Asset Valuation on the tab General Parameters.

Set the shutdown indicator for this interval.

Use a depreciation key that allows shutdown in the affected depreciation areas.

During this period of shutdown, the system will not calculate any depreciation. The useful life of the asset increases by this
length of time. If you unset the shutdown indicator, the system automatically restarts depreciation.

Units-of-Production Depreciation

Use
Depreciation that is based on the production amount or the number of units produced is useful for certain types of assets. This
depreciation method is 100% variable and therefore allows you to re ect uctuations in operating levels or in the output
quantity. This is done by linking the amount of the period depreciation directly to the output quantity (number of units).

Features
This is custom documentation. For more information, please visit the SAP Help Portal 89
 8/16/2024

Depreciation Method, Depreciation Key, and Calculation

The calculation of period depreciation is dependent on the calculation method used in the base method of the relevant
depreciation key. There are the following calculation methods with the corresponding depreciation keys:

Depreciation of acquisition value over the total output (total number of units)

Depreciation key: UOPT

The base value here is the acquisition value or the replacement value.

Calculation:

Depreciation = Acquisition value / Total number of units * Number of units per period

 Example
APC: 10,000

Total number of units: 10,000 PCS

Number of units per period: 100 PCS

Depreciation = 10000 / 10000 * 100 = 100

Depreciation of net book value over the remaining output (remaining number of units)

Depreciation key: UOPR

The base value here is the net book value with proportional value adjustments.

Calculation:

Depreciation = Net book value / Remaining number of units * Number of units per period

As with other depreciation methods, the actual posting of the units-of-production depreciation is carried out by the periodic
depreciation posting run.

Maintain Number of Units

You maintain the total number of units and the number of units per period in the app Maintain Number of Units for UoP
Depreciation. You can change the total number of units and the number of units per period by creating a new time interval. The
system then calculates the units-of-production depreciation based on the new number of units from the beginning of the new
time interval.

For more information about maintaining the number of units, see Maintain Number of Units for UoP Depreciation.

Example: Depreciation Keys for the USA

Use
The following describes some depreciation keys that are available with the chart of depreciation for the USA.

Depreciation Keys (Examples)

Example: Straight-line depreciation with depreciation key LINS

This is custom documentation. For more information, please visit the SAP Help Portal 90
 8/16/2024

Depreciation key LINS

Name Straight line over remaining life pro rata to zero

Depreciation type Ordinary depreciation

Depreciation phase 1 - From depreciation start

Base method 0011 - Normal: Percentage duration

Declining-balance method 001 - 0,00x / 0,0000% / 0,0000%

Period control method 003 - 01/06/02/02

Multi-level method 001 - 0,0000%

Depreciation class Straight-line depreciation

Changeover method Changeover after the end of planned useful life

Changeover percentage 0.0

Multiple-shift Increasing depreciation and the expired useful life

Scrap value Allowance controlled by cutoff value keys

Shutdown No

Example: Valuation according to MACRS

The following depreciation keys are delivered for valuation according to MACRS (Modi ed Accelerated Cost Recovery System):

M200: 3, 5, 7, 10 years of useful life

M150: 15, 20 years of useful life

MSTL: 27.5 and 31.5 years of useful life

Example: Depreciation Keys for Germany (Ordinary

Depreciation)

General Regulations for Depreciation

Certain general requirements for depreciation stipulated in the German commercial code and German tax law are re ected in
the depreciation keys that SAP provides.

End of depreciation

Depreciation always ends when the net book value reaches zero, or when it reaches the memo value speci ed globally per
depreciation area and company code, or when it reaches the scrap value speci ed in the asset.

Acquisitions during the year of capitalization

All acquisitions in the rst year always refer to the depreciation start date that was set automatically by the rst acquisition
according to the period control that was entered or that was set manually by the user.

Acquisitions in subsequent scal years

This is custom documentation. For more information, please visit the SAP Help Portal 91
 8/16/2024
Additional acquisitions to existing assets are allowed in subsequent scal years. The system always sets the asset value date to
the rst day of the scal year, so that a full year’s depreciation is calculated in the year in which the acquisition was posted.

Transfers and retirements

The system calculates transfers and retirements using pro rata temporis. Using pro rata temporis, transactions during the rst
half of a period start depreciation on the rst day of the period, and transactions in the second half of the period start
depreciation at the end of the period.

Shutdowns

Shutdowns are not recognized by the standard depreciation keys.

Depreciation Keys (Examples)

The special settings for Germany are shown here using the examples of depreciation keys and processes that are common in
Germany.

LINR: straight-line depreciation

The depreciation key calculates depreciation as follows:

Depreciation = net book value / remaining life

In the year of acquisition, the rst year convention of a half year is used, whereby the depreciation start date for acquisitions in
the rst half of the scal year is set to the rst day of the scal year, so that a full year's depreciation is calculated for the asset.
For acquisitions during the second half of the scal year, the depreciation start date is set to the middle of the scal year, so
that half of the annual depreciation is calculated.

The system ensures that when the planned useful life is expired, the net book value reaches one of the following: either book
value zero or the speci ed scrap value or memo value. Depreciation ends at that point. Acquisitions that are posted to the
asset after that time are written off completely in the year they are acquired, so that the net book value of the asset remains
the same.

Overview of settings:

Depreciation key LINR LINR

For depreciation phase 1 For depreciation phase 2

Description Str.-line frm rem.life to book value zero Str.-line frm rem.life to book value zero

Depreciation type Ordinary depreciation Ordinary depreciation

Depreciation phase From depreciation start Changeover during planned life

Base method 0011 - Normal: Percentage duration 0017 - Normal: Immediate deprec. (after
end of useful life)

Declining-balance method 001 - 0,00x / 0,0000% / 0,0000% 001 - 0,00x / 0,0000% / 0,0000%

Period control method 002 - 04/06/02/02 003 - 01/06/02/02

Multi-level method 001 - 0,0000% 013 - 0,0000%

Depreciation class Straight-line depreciation Straight-line depreciation

This is custom documentation. For more information, please visit the SAP Help Portal 92
 8/16/2024

Depreciation key LINR LINR

For depreciation phase 1 For depreciation phase 2

Changeover method Changeover after the end of planned useful --

life

Changeover percentage 0.0 0.0

Multiple-shift Increasing depreciation and the expired Increase in depreciation, no increase of

useful life expired useful life

Scrap value Allowance controlled by cutoff value keys Allowance controlled by cutoff value keys

Shutdown No No

DGxy: Declining Balance with x,y-times the Straight-Line Rate

Depreciation keys DG20, DG25 and DG30 calculate depreciation from the net book value at x,y-times the straight-line
percentage rate, with a maximum of 10 * x,y %. You enter the declining balance multiplication factor in the declining-balance
methods used. The depreciation key DG30 is to be used with the 3-times straight-line percentage rate, but with a maximum of
30% for the new xed assets. This depreciation key uses this formula:

Depreciation = net book value * 3 / total useful life

As soon as straight-line depreciation over the remaining useful life is greater than the declining-balance depreciation, the
system changes over to straight-line depreciation. This ensures that when the planned useful life is expired, the net book value
reaches one of the following: zero, or the speci ed scrap value or memo value. Depreciation ends at that point. Acquisitions that
are posted to the asset after that time are written off completely in the year they are acquired, so that the net book value of
the asset remains the same.

Buildings (B), straight-line depreciation (SL) (BSL20/BST25): Buildings, straight-line depreciation

For the depreciation of buildings, you use these depreciation keys that depreciate either 2% of APC over a useful life of 50 years
or 2.5% over 40 years. These percentages are speci ed in the corresponding multilevel method (14 or 15).

In the year of capitalization, pro rata temporis is used, so that depreciation is calculated starting from the period of the rst
acquisition. Because of rounding, there can sometimes still be a book value when the useful life has expired. When there are
subsequent acquisitions to a building, this results in a mandatory extension of the time period for depreciation. If a book value
exists, depreciation is still calculated with the same percentage rate after the useful life has expired.

GDxx (buildingxx): Declining-balance depreciation for buildings

Depreciation keys GD35, GD50, GD70 and GD10 are provided for declining-balance depreciation of buildings according to the
different percentage rates permitted by tax laws for particular types of buildings and time periods. These percentages are
speci ed in the corresponding multilevel methods of the depreciation keys (11, 12, 13, 10).

In the capitalization year a full year's depreciation is always calculated. The percentage rates are speci ed so that exactly 100%
is always depreciated at the end of the planned useful life. Because of rounding, there can sometimes still be a book value when
the useful life has expired. When there are subsequent acquisitions, this results in a mandatory extension of the time period for
depreciation. If a book value exists, depreciation is still calculated with the same percentage rate after the useful life has
expired.

Low-value asset: Complete depreciation in acquisition year

This depreciation key is speci cally set up to provide for the complete depreciation of low value assets in the year in which they
were acquired. The depreciation calculation method entered in the base method of the depreciation key is Immediate
depreciation. Together with the recommended useful life of 1 period for low value assets, this causes the asset to be fully

This is custom documentation. For more information, please visit the SAP Help Portal 93
 8/16/2024
depreciated immediately in the period in which it is acquired. You cannot post subsequent acquisitions in later scal years to
assets with this depreciation key. In this way, you can always immediately identify low value assets according to their year of
acquisition. Retirements in the acquisition year are always calculated with the complete depreciation.

Periodic Activities

Schedule Asset Accounting Jobs

App ID: F1914

You use the Schedule Asset Accounting Jobs app to perform periodic activities in Asset Accounting.

Job Templates
The following job templates are available:

Recalculate Depreciation

Depreciation Posting Run

Year-End Closing Asset Accounting (Cross-Company Code and Ledger)

Supported Device Types

Desktop

Tablet

More Information
For more information about Job Scheduling apps, see Application Jobs.

Recalculate Depreciation
The determination of depreciation of a xed asset and the posting of depreciation expense takes place at different times in the
system:

1. Determination of depreciation

The depreciation is either determined automatically by the system (usually), or you determine the depreciation using
this job Recalculate Depreciation.

You use this job to determine the planned depreciation (planned depreciation values).

2. Depreciation posting

You post depreciation using the Depreciation Posting Run job.

With the actual depreciation posting, the system copies the planned depreciation values that were determined and
posts them to the G/L accounts.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 94
 8/16/2024
The function for recalculating depreciation is also available in the Manage Fixed Assets app, in case you wish to recalculate
depreciation for just one xed asset only.

Use
In most cases, the system recalculates depreciation automatically. You only need to manually start the Recalculate
Depreciation job to get depreciation recalculated in exceptional cases. Exceptional cases include:

You want to recalculate depreciation for control purposes.

You need to recalculate depreciation for correction purposes.

Corresponding examples can be found below.

Automatic Recalculation of Depreciation by the System

The system recalculates the planned depreciation values automatically in the following cases:

There was a change to the master record (for example, the useful life was changed or a different depreciation key has
been assigned)

For asset processing postings (for example, xed asset acquisition or credit memo received)

As part of the balance carryforward at scal year change

The changed planned depreciation values determined in such cases are updated in the database.

Manual Running of the Job “Recalculate Depreciation”

As already mentioned, you should only have to schedule and run the job Recalculate Depreciation in exceptional cases. Here
are some examples of when it might be necessary:

You want to make sure at some point during the year that the depreciation calculated is correct; your intention is to
correct errors in the context of year-end closing in time or avoid them from the start.

You have performed the legacy data transfer but did not calculate depreciation for performance reasons. To do so, you
set the indicator Suppress Depreciation Calculation in the legacy data transfer segment in the app Make Company
Code Settings - Asset Accounting Speci c. (See also the corresponding eld help.)

The de nition of a depreciation key used was changed (example: SAP had to change a depreciation key for legal
reasons.)

The system issues a message saying that the depreciation should be recalculated.

This can occur, for example, when you close the scal year in Asset Accounting using the app Make Company Code
Settings - Asset Accounting-Speci c.

Prerequisites
To be able to run the job Recalculate Depreciation, the following prerequisite must be ful lled:

The scal year for which you want to have the depreciation calculated must be open.

This is because it is only possible to recalculate depreciation for a company code, ledger and/or a depreciation area when the
corresponding scal year is open in Asset Accounting. You can see the open scal years in the app Make Company Code
Settings - Asset Accounting-Speci c in the Ledger Settings.

This is custom documentation. For more information, please visit the SAP Help Portal 95
 8/16/2024

Procedure
To schedule and run the depreciation calculation, proceed as follows:

1. In the app Schedule Asset Accounting Jobs, choose Create.

2. In the Template Selection step, choose the job template Recalculate Depreciation.

3. In the Scheduling Options step, you de ne when the job should be run:

Either you set the indicator Start Immediately.

Or you de ne a speci c point in time (with date and time).

This is by default for a single run. To run the job regularly, you can de ne a Recurrence Pattern; in doing so, please
consider the associated effect on performance.

4. In the Parameters step, you de ne the following parameters:

Under Selections:

One or more company codes

One or more ledgers or alternatively one or more depreciation areas

The scal year from which the depreciation should be recalculated (see also the “Prerequisites” section)

If you do not specify a scal year, the open scal years are processed; this option makes sense provided
that the scal years of all depreciation areas are open. If you enter a scal year and only the scal years of
individual depreciation areas from the ledger are open, you must limit your selection to those depreciation
areas.

If necessary, one or more asset numbers and/or subnumbers (only if you want to limit the depreciation
calculation to individual main asset numbers or subnumbers)

Under Test Run, you de ne whether you want to run the job as a test run or as an update run. The system only
writes planned depreciation values to the database in an update run.

Under Log, you specify whether you want an output log and whether it should be detailed:

The Totals Log lists the depreciation as a summary only. The individual xed assets are not listed.

In the Detailed Log, the individual xed assets are listed.

5. To schedule and run the job, choose Schedule.

In the list of the application jobs, you can monitor the status of the jobs and go directly to the log.

Note: Alternative Fiscal Year Variant

If you have assigned an alternative scal year variant to your local ledger at company code level, your scal years in the ledgers
are not congruent. This affects the calculation of depreciation and the posting of depreciation; you therefore have to perform
these for each ledger.

For more information, see Alternative Fiscal Year Variant and Its Effects on Transactions.

Additional Information
More information can be found here:

This is custom documentation. For more information, please visit the SAP Help Portal 96
 8/16/2024
About the job Depreciation Posting Run: Depreciation Posting Run

About depreciation in general, as well as depreciation methods and depreciation keys: Depreciation

Depreciation Posting Run

The determination of depreciation of a xed asset and the posting of depreciation expense takes place at different times in the
system:

1. Determination of depreciation

The depreciation is either determined automatically by the system (usually), or you determine the depreciation using
the job Recalculate Depreciation.

You use the job to determine the planned depreciation (planned depreciation values).

2. Depreciation posting

You post depreciation using this Depreciation Posting Run job.

With the actual depreciation posting, the system copies the planned depreciation values that were determined and
posts them to the G/L accounts.

Distinction: Automatic and manual posting of depreciation

To post depreciation calculated automatically (ordinary depreciation and special depreciation), use this job: Depreciation
Posting Run. Unplanned depreciation on the other hand is posted manually using the app Post Depreciation Manually -
Unplanned and Planned.

Both the depreciation posting run and a manual posting using the app Post Depreciation Manually - Unplanned and Planned
lead to a direct posting on the corresponding depreciation accounts in General Ledger Accounting.

Features
The depreciation posting run (in short: depreciation run) adopts the planned depreciation values and posts them to General
Ledger Accounting; the journal entry updates the values at xed asset level. The journal entry is created for several xed assets
together. If there is an error in one of the xed assets, the journal entry cannot be posted. In this case, the log lists all xed
assets with an error in the simulated journal entry.

Errors in individual xed assets do not necessarily have to be xed before period-end closing; the period-end closing can still be
carried out. However, you must have corrected all xed assets by the end of the year at the latest so that it is possible to post
depreciation completely.

Posting in Prior Periods

You can also run the depreciation posting run again for periods that are before the last period posted.

 Example
In the current scal year YYYY, the last depreciation posting run you performed was for period 005. You must repeat the
depreciation posting run for period 003.

If two scal years are open (for example, YYYY-1 and YYYY), then the depreciation can be posted in both scal years before
the period most recently posted, that is, before period 005.

This is custom documentation. For more information, please visit the SAP Help Portal 97
 8/16/2024
Note also the following: The depreciation posting in prior periods affects the income statement-related values for the posted
and planned depreciation and the net book values for the balance sheet; the system displays these changed values in the value
display of the app Manage Fixed Assets.

Posted Depreciation in Reporting

After the depreciation posting run, the values are displayed in reporting as posted values (and no longer as planned values), for
example in the Depreciation Lists app and in the Manage Fixed Assets app.

 Tip
In the value display of the app Manage Fixed Assets, you can display the eld Fiscal Period of Depreciation under Journal
Entries. This enables you to see for which period the depreciation amount was posted.

Prerequisites
To be able to run the depreciation posting run successfully, the following prerequisites must be ful lled:

The corresponding posting periods of the scal year are open in General Ledger Accounting.

The corresponding scal year is open in Asset Accounting.

You can check this in the app Make Company Code Settings - Asset Accounting-Speci c.

If you performed a legacy data transfer and for performance reasons set the indicator Suppress Depreciation
Calculation, you must rst recalculate depreciation before posting it. To do so, run the job Recalculate Depreciation.

Procedure
To schedule and run the depreciation posting run, proceed as follows:

1. In the app Schedule Asset Accounting Jobs, choose Create.

2. In the Template Selection step, choose the job template Depreciation Posting Run.

3. In the Scheduling Options step, you de ne when the job should be run.

Either you set the indicator Start Immediately.

Or you de ne a speci c point in time (with date and time).

This is by default for a single run. To run the job regularly, you can de ne a recurrence pattern; in doing so, please
consider the associated effect on performance.

4. In the Parameters step, you de ne the following parameters:

Under Selections:

One or more company codes

Fiscal year and posting period.

The system posts depreciation for the depreciation values currently available within the scal year
entered up to the posting period entered.

You can limit the posting to one or more ledgers.

Under Test Run Parameters, you de ne whether you want to run the job as a test run or as an update run. The
system only writes the values to the G/L accounts in an update run.

This is custom documentation. For more information, please visit the SAP Help Portal 98
 8/16/2024
Asset numbers and subnumbers.

You can only limit the posting to certain xed assets in a test run; this is not possible in an update run.

Under Options you specify whether you want an output log and whether it should be detailed:

The Totals Log lists the depreciation as a summary only. The individual xed assets are not listed.

In the Detailed Log, the individual xed assets are listed.

5. To schedule and run the job, choose Schedule.

In the list of the application jobs, you can monitor the status of the jobs and go directly to the log.

Note: Alternative Fiscal Year Variant

If you have assigned an alternative scal year variant to your local ledger at company code level, your scal years in the ledgers
are not congruent. This affects the calculation of depreciation and the posting of depreciation; you therefore have to perform
these for each ledger.

For more information, see Alternative Fiscal Year Variant and Its Effects on Transactions.

Additional Information
More information can be found here:

About the job Recalculate Depreciation: Recalculate Depreciation

About depreciation in general, as well as depreciation methods and depreciation keys: Depreciation

Year-End Closing Asset Accounting (Cross-Company Code and

Ledger)
With this job, you can close a scal year for one or more company codes or ledgers in Asset Accounting.

Use
You can use this job to close a scal year from an accounting perspective for one or more company codes or ledgers.
Subsequently, neither postings nor value changes (for example, through recalculating depreciation) are possible in Asset
Accounting for the closed scal year.

The scal year to be closed is always the scal year which follows the scal year closed most recently. The current scal year
should not be closed unless you want to deactivate the company code.

You must rst close a scal year in Asset Accounting so that you can then close it in General Ledger Accounting. (See also the
product assistance for General Ledger Accounting under Opening and Closing Posting Periods.)

 Note
Depending on whether you want to close the scal year for several company codes or ledgers or only for individual
depreciation areas, you can use different apps:

To close a scal year for one or more company codes or ledgers, you use the job template Year-End Closing Asset
Accounting (Cross-Company Code and Ledger) from the Schedule Asset Accounting Jobs app. For more
information, see this document.
This is custom documentation. For more information, please visit the SAP Help Portal 99
 8/16/2024
To close a scal year for a depreciation area of a company code, use the app Make Company Code Settings - Asset
Accounting-Speci c (F7312). For more information, see Year-End Closing for Individual Depreciation Areas.

Prerequisites
To be able to perform the year-end closing, the following prerequisites must be ful lled:

No errors occurred in any of the xed assets with the depreciation calculation.

The planned depreciation was posted fully in General Ledger Accounting.

This prerequisite does not apply to assets under construction as it would not make sense in this case. Therefore the
system does not perform any checks for assets under construction.

All incomplete assets have been completed.

The incomplete assets can be seen in the worklist of the Manage Fixed Assets app.

Features
The job determines the depreciation areas that are possible for the scal year to be closed (for one or more company codes
and/or ledgers). The scal year is closed as soon as the prerequisite checks are successful.

Procedure
To schedule and run the closing of a scal year, proceed as follows:

1. In the app Schedule Asset Accounting Jobs, choose Create.

2. In the Template Selection step, choose the job template Year-End Closing Asset Accounting (Cross-Company Code and
Ledger).

3. In the Scheduling Options step, you de ne when the job should be run:

Either you set the indicator Start Immediately.

Or you de ne a speci c point in time (with date and time).

This is by default for a single run. (It is possible to de ne a recurrence pattern but we do not recommend it for this job.)

4. In the Parameters step, you de ne the following parameters:

Company Code:

The closing of a scal year can occur for one or more company codes simultaneously.

You can limit the selection to one or more company codes. To select all company codes, enter a star (asterisk).

Ledger:

The closing of a scal year can take place simultaneously for one or more ledgers. You can therefore limit the
selection to one or more ledgers.

If the ledgers have a different periodicity (due to an alternative scal year variant, for example), then you must
run the job for each ledger individually.

Fiscal Year to Be Closed:

Here you enter the scal year to be closed.

This is custom documentation. For more information, please visit the SAP Help Portal 100
 8/16/2024
Test Run or Update Run:

If you perform an update run, the program must run in the background.

5. To schedule and run the job, choose Schedule.

In the list of the application jobs, you can monitor the status of the jobs and go directly to the log.

Year-End Closing for Individual Depreciation Areas

To perform year-end closing for individual depreciation areas, use the app Make Company Code Settings - Asset Accounting-
Speci c (F7312). In addition, you can reset the year-end closing for depreciation areas in the app.

You must rst close a scal year in Asset Accounting so that you can then close it in General Ledger Accounting. (See also the
product assistance for General Ledger Accounting under Opening and Closing Posting Periods.)

 Note
Depending on whether you want to close the scal year for individual depreciation areas or for several company codes or
ledgers, you can use different apps:

To close a scal year for one depreciation area of a company code, use the app Make Company Code Settings - Asset
Accounting-Speci c (F7312). Read more in this document.

To close a scal year for one or more company codes or ledgers, use the job template Year-End Closing Asset
Accounting (Cross-Company Code and Ledger) from the Schedule Asset Accounting Jobs app. For more
information, see Year-End Closing Asset Accounting (Cross-Company Code and Ledger).

Execute Year-End Closing

Use

You can close a scal year for a depreciation area. Afterwards, postings are no longer possible within Asset Accounting for the
closed scal year.

The scal year that is closed is always the year following the last closed scal year. The current scal year should not be closed
unless you want to deactivate the company code.

Prerequisites

The system found no errors during the calculation of depreciation (such as, incorrectly de ned depreciation keys).

Planned depreciation was not posted completely to the general ledger

All assets acquired in the scal year have already been capitalized.

This prerequisite does not apply to assets under construction as this would not make any sense. The system therefore
does not make any corresponding check for assets under construction.

All incomplete assets (master records) have been completed.

Procedure

To perform year-end closing at the level of depreciation areas, select one or more depreciation areas and close it or them. (If
you choose all depreciation areas, it is the same as performing a year-end closing at ledger level).

This is custom documentation. For more information, please visit the SAP Help Portal 101
 8/16/2024
It makes sense to do a year-end closing at depreciation area level when you expect that you will have to reopen some
depreciation areas and close them again later (for tax reasons, for example).

Proceed as follows:

1. Select the required ledger in the ledger settings.

2. Choose the depreciation areas you require and then close them using the corresponding pushbutton.

 Note
On ledger level, you can jump to the Balance Carryforward Status app. To do this, select the required ledger in the ledger
settings and choose the Balance Carryforward Status pushbutton. The system then displays the balance carryforward
status for the highest open scal year (that is, the latest scal year opened by a scal year change). From the Balance
Carryforward Status app, you can jump to the balance carryforward log.

Undo Year-End Closing

Use

If you have closed a scal year by mistake and still have to make adjustments, you can reopen the scal year last closed for one
or more depreciation areas of a company code.

Note:

 Note
A scal year that is already closed from an accounting point of view and has been certi ed by an external auditor is not
allowed to be reopened. Check with your external auditor if this is still possible.

Procedure

To reopen the last closed scal year for individual or all depreciation areas of a company code, perform the following steps:

1. Choose the ledger for which you want to reopen the scal year from the detail screen of the company code.

2. In the detail screen of the ledger, choose the depreciation areas and open the previous year for them using the
corresponding pushbutton.

Follow-on activities:

1. Make your adjustments in the previous year. (The corresponding posting periods must be open in General Ledger
Accounting for this.)

2. Execute all necessary year-end closing operations.

3. Make sure that the previous year is closed again in both Asset Accounting and General Ledger Accounting.

To close the scal year in Asset Accounting, proceed as described above.

Fiscal Year Change in Asset Accounting: FAQ

This section answers important questions about the scal year change in Asset Accounting.

This is custom documentation. For more information, please visit the SAP Help Portal 102
 8/16/2024

At the end of the current scal year YYYY, I would like to prepare for posting to the
new scal year YYYY+1. What must I do so that my colleagues can continue
working freely in the new scal year?
The system executes a balance carryforward automatically at the end of the scal year. This occurs a few days before the end of
the current scal year YYYY You do not need to perform any manual activities for the balance carryforward.

The successful execution of the balance carryforward is a prerequisite so that you can make xed asset postings in the new
scal year (YYYY+1).

If there are any difficulties, you can also trigger the balance carryforward manually. To do this, you must schedule the
corresponding job. Then use the Schedule General Ledger Jobs app with the Balance Carryforward job template.

To nd out whether the balance carryforward has already been performed, you can check the status of the balance carryforward
either directly in the Balance Carryforward Status app or indirectly using the Make Company Code Settings - Asset
Accounting-Speci c app.

App See Also

Schedule General Ledger Jobs, job template Balance Balance Carryforward

Carryforward

Balance Carryforward Status Balance Carryforward Status

What do I need to do so that I can post to the new scal year?

The system performs the balance carryforward automatically. Therefore, you usually do not need to worry about this. (See
previous question.)

However, you need to ensure that the posting periods are maintained for the new scal year (YYYY+1). You do this using the
app Manage Posting Periods. This app, for which the general ledger accountant is usually responsible, can be used to open
posting periods.

App See Also

Manage Posting Periods Opening and Closing Posting Periods

How many scal years can be open at the same time?

In Asset Accounting, only two scal years are allowed to be open at the same time. To be able to open the new scal year
(YYYY+1), you must rst close the scal year YYYY-1.

Fiscal year YYYY-1 Fiscal year YYYY Fiscal year YYYY+1

Open Open --

→ Must rst be → Can only be opened

closed when YYYY-1

closed.

To open scal years, use the app Make Company Code Settings - Asset Accounting-Speci c.

App See Also

This is custom documentation. For more information, please visit the SAP Help Portal 103
 8/16/2024

App See Also

Make Company Code Settings - Asset Accounting-Speci c Choose Con guration Help within the app.

See also the question "How can I perform year-end closing for multiple company codes?" below.

I get an error message saying that the scal year is already closed. How do I nd
out which scal years are already closed?
You can nd out which scal years have already been closed in the app Make Company Code Settings – Asset Accounting-
Speci c. You then choose the required company code and ledger.

In the ledger settings, you can also see which scal year was opened by the scal year change or the balance carryforward.

App See Also

Make Company Code Settings - Asset Accounting-Speci c Choose Con guration Help within the app.

How is the current scal year and the scal year last closed determined for the rst
time in a newly created company code?
The system derives the current scal year and the scal year last closed from the legacy data transfer date in the legacy data
transfer segment. You need to create a legacy data transfer segment in the app Make Company Code Settings - Asset
Accounting-Speci c.

If you do not perform a legacy data transfer in the new company code (for example, because it is for a startup company), you do
not need to create a legacy data transfer segment; instead, you can specify the highest open scal year (Highest F. Year)
directly in the ledger settings.

App See Also

Make Company Code Settings - Asset Accounting-Speci c Choose Con guration Help within the app.

I want to make my rst postings in Asset Accounting in a new company code for
the current scal year YYYY. However, the system issues an error message that I
should rst execute a balance carryforward to the current scal year. - Why and
when do I need to perform the balance carryforward even though I have not yet
made any postings in previous years?
Before you can make the rst postings in Asset Accounting for the current scal year YYYY, the following prerequisites must be
ful lled:

1. The highest scal year is de ned:

In the app Make Company Code Settings - Asset Accounting-Speci c, you de ne the current scal year by specifying
the highest scal year. You have the following options for doing this:

If you want to perform a legacy data transfer, proceed as follows:

Create a legacy data transfer segment on the Legacy Data Transfer tab page. Enter a legacy data transfer date
for the legacy data transfer segment. The system automatically derives the current scal year and the scal year
last closed from the legacy data transfer date.

Alternatively, you can de ne the highest open scal year (Highest F. Year) directly in the ledger settings.

This is custom documentation. For more information, please visit the SAP Help Portal 104
 8/16/2024
2. The balance carryforward was executed:

You have to execute a balance carryforward to the current scal year (YYYY). This applies regardless of whether you
have carried out a legacy data transfer or whether you do not perform a legacy data transfer, for example, due to a
start-up.

The balance carryforward is necessary so that the system can update the values based on the balances and your
postings from the legacy data transfer. Without the balance carryforward, incorrect values would occur due to values
missing from the previous year.

The balance carryforward is carried out automatically on a regular basis in the last period of the year. If desired, you can
perform the balance carryforward immediately, using the Balance Carryforward job template from the Schedule
General Ledger Jobs app.

App See Also

Make Company Code Settings - Asset Accounting-Speci c Choose Con guration Help within the app.

Schedule General Ledger Jobs, job template Balance Balance Carryforward

Carryforward

I want to create an asset master record in a new company code. If I enter the
company code and asset class for this, then the system issues an error message
(for example, AY159) saying that no information exists yet for the scal year last
closed in the company code. - What do I need to do?
Check whether you have de ned the closed scal year and the current scal year.

You select the relevant company code and ledger in the app Make Company Code Settings - Asset Accounting-Speci c. In the
settings for ledgers and depreciation areas, the system displays the scal year last closed. In the ledger settings, you can also
nd information about the last scal year that was opened by the scal year change (this is the scal year for which the balance
carryforward was executed either automatically or manually with the job template Balance Carryforward).

To enable the system to derive the scal year last closed, you have to create a legacy data transfer segment or specify the
highest scal year. See also the answer to the previous question.

The balance carryforward has already been executed. Do I need to re-execute it

after I post to the previous scal year (YYYY-1)?
No, you do not need to perform the balance carryforward again in this case. The system has already executed the balance
carryforward automatically at the end of the scal year (YYYY-1) and at the start of the scal year (YYYY). This means that the
system automatically transfers all subsequent postings for scal year YYYY-1 to the current scal year YYYY.

If I try to close the scal year YYYY-1 in Asset Accounting, I receive an error
message (for example, FAA_CMP078). Why can't I close the scal year?
You cannot close scal year YYYY-1 for a ledger or a depreciation area in an Asset Accounting company code until you have
ful lled the necessary requirements. This includes the following steps:

1. You have successfully calculated depreciation for all xed assets for the entire scal year YYYY-1.

Use the app Schedule Asset Accounting Jobs with the job template Recalculate Depreciation.

2. You have successfully posted depreciation for all xed assets for the entire scal year YYYY-1.

You can use the app Schedule Asset Accounting Jobs with the job template Depreciation Posting Run.

This is custom documentation. For more information, please visit the SAP Help Portal 105
 8/16/2024
3. If you have carried out a legacy data transfer in the scal year to be closed YYYY-1, you have done the following:

a. You have nished the legacy data transfer for scal year YYYY-1 and reconciled the results with the legacy
system.

b. In the app Make Company Code Settings - Asset Accounting-Speci c, on the Legacy Data Transfer tab, you
have set the status of the legacy data transfer segments that have a legacy data transfer date in scal year
YYYY-1 to Completed.

c. For legacy data transfer during the year, the following also applies:

Depending on the structure of your legacy data transfer, you may need to calculate and post depreciation for
scal year YYYY-1.

App See Also

Schedule Asset Accounting Jobs, job template Recalculate Recalculate Depreciation

Depreciation

Schedule Asset Accounting Jobs, job template Depreciation Depreciation Posting Run
Posting Run

Make Company Code Settings - Asset Accounting-Speci c Choose Con guration Help within the app.

Legacy Data Transfer (Different Apps) Legacy Data Transfer

I'm trying to close scal year YYYY-1 in Asset Accounting. When you do this, the
system issues an error message (for example, AU268), which states that the
depreciation has not been posted completely in YYYY-1 for all assets. Even the
recalculation of the depreciation and the posting of the depreciation does not solve
the problem. How should I proceed?
You must rst determine the assets with errors, then remove the cause of the error, and nally calculate and post the
depreciation.

1. To nd out which assets are causing problems, you must use the Manage Fixed Assets app (F3425). Proceed as follows:

a. In the app, adjust the lter bar: Add eld Error in Depreciation.

b. For the depreciation error lter, choose the following values:

Error in depreciation calculation of current year and

Error in depreciation calculation of previous year(s)

c. Create the worklist using the lter values mentioned.

2. First check the assets individually. Correct existing errors, for example, in the asset master data.

3. Recalculate depreciation – either for individual assets or for all assets:

To recalculate the depreciation for a speci c asset, select the asset in the Manage Fixed Assets app, call the
master data view, and choose Recalculate.

To recalculate the depreciation for all assets for the entire scal year YYYY-1 (or to restrict it to one depreciation
area with incorrect assets), use the app Schedule Asset Accounting Jobs with the job template Recalculate
Depreciation.

4. To schedule a depreciation posting run, proceed as follows:

This is custom documentation. For more information, please visit the SAP Help Portal 106
 8/16/2024
To post depreciation for xed assets for the entire scal year YYYY-1, use the app Schedule Asset Accounting Jobs with
the job template Depreciation Posting Run.

App See Also

Manage Fixed Assets Manage Fixed Assets

Schedule Asset Accounting Jobs, job template Recalculate Recalculate Depreciation

Depreciation

Schedule Asset Accounting Jobs, job template Depreciation Depreciation Posting Run
Posting Run

How can I execute the year-end closing for multiple company codes?
With the app Make Company Code Settings - Asset Accounting-Speci c, you can only perform year-end closing for each
company code and ledger.

However, the app Schedule Asset Accounting Jobs provides you with the job template Year-End Closing Asset Accounting
(Cross-Company Code and Ledger). This job template allows you to close the scal year for multiple company codes and/or
ledgers in one step.

App See Also

Schedule Asset Accounting Jobs, job template Year-End Closing Year-End Closing Asset Accounting (Cross-Company Code and
Asset Accounting (Cross-Company Code and Ledger) Ledger)

Reporting
Create an asset history sheet to represent the development of the xed asset from the opening balance through to the closing
balance. From an Asset Accounting point of view, the asset history sheet is the most important supplement to the balance
sheet.

More tools for the reporting and analysis of asset portfolios, asset transactions, and depreciation are also available.

Asset Accounting Overview

App-ID: F3096

With this app you can easily access key information and KPIs within the Asset Accounting area, and gain insight into current
trends. The app provides a central source of information for the asset accountant, and offers a range of lters and built-in
navigation to related apps.

Key Features

 Recommendation
Although a wide range of cards is available, not all are enabled by default, and we anticipate that you will enable only the
cards that are most useful for you. Please be aware that if you enable a large number of cards, there will be an inevitable
drop in the app's performance.

'Asset Balances' Cards

This is custom documentation. For more information, please visit the SAP Help Portal 107
 8/16/2024

Card Name Description

Asset Balances Shows total planned asset net book values as of the end of the
scal year and period you speci ed in the lters.

Asset Balances - Chart View The KPI shows total planned asset net book values as of the end of
the scal year and period selected in the lters.

Asset Depreciation Values Shows asset depreciation values for the scal year and period you
speci ed in the lters.

This card shows value to be posted. The values shown are the
same as in the Depreciation to Be Posted card

Assets Under Construction Shows assets under construction in the scal year and period you
speci ed in the lters.

Depreciation to Be Posted Shows value to be posted by depreciation type for the scal year
and period you speci ed in the lters.

Origin of Assets Shows asset origin displayed either by country or by supplier. Data
is for the scal year and period you speci ed in the lters

These cards relate to the Asset Balances app. For these cards, data is displayed based on the Fiscal Year and the Fiscal Period
(Balances) you select in the app.

'Asset Transactions' Cards

Card Name Description

Asset Acquisitions Shows the total value of acquisitions within the selected period.

Asset Transactions Shows acquisitions and retirements displayed by Asset Class,

Account Determination and similar.

Asset Retirements Shows the total value of retirements within the selected period.

Asset Transactions by Type Shows the proportion of acquisitions and retirements in the
selected period.

Assets Under Construction - Aging Shows the age in days of assets under construction.

 Recommendation
This card is not enabled by default. The card requires
signi cant system resources, so please be aware that enabling
this card is likely to have an impact on performance.

These cards relate to the Asset Transactions app. For these cards, data is displayed based on the Fiscal Year and the Fiscal
Period (Transactions) you select. The Fiscal Period (Transactions) lter is not displayed by default, but can be found under
Adapt Filters Fixed Asset Filters . The exception is Assets Under Construction - Aging, which always shows data 'as of today'.

Other Cards

Card Name Description

Manage Fixed Assets Shows current number of assets by status.

Open Purchase Orders with Account Assignment *A* - Chart Shows Open Purchase Orders by value.
View

This is custom documentation. For more information, please visit the SAP Help Portal 108
 8/16/2024

Card Name Description

Open Purchase Orders with Account Assignment *A* Shows relevant items by either Value Still to Be Invoiced or Value
Still to Be Delivered.

 Recommendation
Use the Purchasing Filters (under Adapt Filters) to re ne the
data presented in the two Open Purchase Orders cards.
Limiting the search parameters in this way can improve
performance. You can save frequently-used search criteria
under My Views to make this process more efficient.

These cards show data 'as of today', and are not affected by the scal year or period lters.

Users of the Asset Accounting Overview app have the authorization to navigate to the Purchase Order Items by Account
Assignement app from the Open Purchase Orders cards. The Purchase Order Items by Account Assignment app will be display-
only for users of the Asset Accounting Overview app, and it will not appear on their launchpad.

Supported Device Types

Desktop

Tablet

App Extensibility
Please note that the Asset Accounting Overview app is not extensible.

Asset Balances
App ID: F1617

With this app, you can display balances of xed assets according to various criteria, such as company code, depreciation area,
segment, or pro t center. The report enables you to understand the netbook value of xed assets derived from acquisition and
production costs (APC) and depreciation. SAP provides pre-con gured key gure groups that you can use for your reporting.
These key gure groups bundle key gure codes, such as acquisition and production cost, cumulative depreciation and netbook
value at reporting date.

Key Features
Use the SAP standard key gure groups:

For planned values (default view): ABS_DEF

For posted values (current book values): ABS_POSTED

For total depreciation: DEPR_TOTAL

For Write-ups: DEPR_WRUP

Display the following values for each asset:

The cumulative acquisition value at reporting date

This is custom documentation. For more information, please visit the SAP Help Portal 109
 8/16/2024
The accumulated depreciation for each depreciation type in posted and not yet posted amounts for the current
scal year

The planned booked value at the end of the reporting period

Specify the search criteria using lters

Display the query results in a grid format

Export the query results to Microsoft Excel

Modify the query results grid by moving available characteristics to and from the grid axes

Supported Device Types

Desktop

Tablet

Additional Information

How-to Video: Web Dynpro Apps - Working with Reports (English Only)

This how-to video shows one of the analytical apps that were developed as Web Dynpro apps.

Open this video in a new window

 Note
Captions are available for multiple languages. Use the CC (Closed Captions) button in the video player to see which
languages are supported.

You can also use the Search within video eld to search for speci c text in the English or German captions.

Further Information

This is custom documentation. For more information, please visit the SAP Help Portal 110
 8/16/2024
For general informationen about multidimensional data grid apps, see Multidimensional Data Grid Apps.

App Extensibility: Asset Balances

You can extend the Asset Balances app according to your business needs.

Features
Key users can extend this app in the Custom Fields app using the business context Fixed Asset Master Data.

You can add elds to the following UI elements using UI adaption at runtime:

UI Element Business Context

Smart form Fixed Asset Master Data (FAA_ASSET_MASTER_DATA)

For more information about how to adapt an SAP Fiori UI at runtime, see Adapting SAP Fiori UIs at Runtime - Key User
Adaptation.

Related Information
Custom Fields

Asset Transactions
App ID: F1614

With this app, you can check and evaluate daily or monthly operations in Asset Accounting by listing asset transactions posted
to the general ledger. The SAP standard key gure groups enable you to select asset transactions by group, such as
acquisitions, retirements, transfers, or posted depreciations. The report then displays all transactions of the selected key gure
groups and their respective key gures. For example, retirements are listed with retirement revenues or costs, gains, losses,
acquisition and production costs (APC), and book value.

What are the differences between the Asset Transactions and Asset History Sheet
apps?
The Asset Transactions app shows a list of real postings in a table that offers various grouping options. It is used to check asset
acquisitions and retirements – information that is useful in your daily business. In contrast, the Asset History Sheet app
displays not only asset transactions but also planned values. It's a legal report that is generated periodically. In addition, the
Asset History Sheet is a grid-based app and can show various dimensions.

Supported Device Types

Desktop

Tablet

Additional Information

How-to Video (English Only): Working with Reports (Analytical List Page)

This is custom documentation. For more information, please visit the SAP Help Portal 111
 8/16/2024
This how-to video shows one of the analytical apps that were developed as Analytical List Page apps.

Open this video in a new window

 Note
Captions are available for multiple languages. Use the CC (Closed Captions) button in the video player to see which
languages are supported.

You can also use the Search within video eld to search for speci c text in the English or German captions.

Further Information

For general informationen about multidimensional data grid apps, see Multidimensional Data Grid Apps.

App Extensibility: Asset Transactions

You can extend the Asset Transactions app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the business context Fixed Asset Master Data.

You can add elds to the following UI elements using UI adaption at runtime:

UI Element Business Context

Smart form Fixed Asset Master Data (FAA_ASSET_MASTER_DATA)

Additional Information

This is custom documentation. For more information, please visit the SAP Help Portal 112
 8/16/2024
For more information about how to adapt an SAP Fiori UI at runtime, see Adapting SAP Fiori UIs at Runtime - Key User
Adaptation.

For more information about the Custom Fields app, see Custom Fields.

Depreciation Lists
App ID: F1616

This app serves as a supplement to the pro t and loss statement. The key gures enable you to analyze the depreciation of
xed assets. You can report depreciation values as a total, or by depreciation type such as ordinary depreciation, special
depreciation, unplanned depreciation, and transferred reserves (deferred gain). In addition, the status of depreciation and
asset attributes, such as the depreciation key and the useful life, help you to analyze the reported gures.

Key Features
The Key Date eld determines the date for which time-dependent data is selected.

The default value for the Key Date is the current date. If you don´t enter any value for the Key Date, the system automatically
chooses today´s date.

If you need to select time-dependent data for previous scal years, months, or years, you must enter the relevant date in the
Key Date eld.

Example:

The current date is March 30, YYYY. You need to analyze the depreciation up to the end of January YYYY, when your cost center
was different from your current cost center. In this case you enter 31.01.YYYY in the Key Date eld to get the results for the
relevant cost center.

Supported Device Types

Desktop

Tablet

Additional Information
For general informationen about multidimensional data grid apps, see Multidimensional Data Grid Apps.

App Extensibility: Depreciation Lists

You can extend the Depreciation Lists app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the business context Fixed Asset Master Data.

You can add elds to the following UI elements using UI adaption at runtime:

This is custom documentation. For more information, please visit the SAP Help Portal 113
 8/16/2024

UI Element Business Context

Smart form Fixed Asset Master Data (FAA_ASSET_MASTER_DATA)

Additional Information
For more information about how to adapt an SAP Fiori UI at runtime, see Adapting SAP Fiori UIs at Runtime - Key User
Adaptation.

For more information about the Custom Fields app, see Custom Fields.

Asset History Sheet

App ID: F1615

Use this app to display the asset history sheet, which shows value changes to the xed asset balances in a scal year for a
depreciation area. The asset history sheet enables you to document and explain the balances on xed assets for every
accounting principle, any local regulation, and for management purposes. SAP provides precon gured key gure groups that
you can use for your reporting. These key gure groups bundle key gure codes, such as acquisitions, retirements, transfers,
and depreciation. Certain key gure groups can be used to display key gures in a hierarchy.

Key Features
Use the following SAP standard key gure groups:

Key Figures Without Hierarchy Key Figures with Hierarchy

For Posted Values AHS AHS_HRY

For Planned Values AHS_PLAN AHS_HRY_PL

Specify the search criteria using lters

Display the query results in a grid format

Export the query results to Microsoft Excel

Modify the query results grid by moving available characteristics to and from the grid axes

You can exclude deactivated assets from your asset history sheet by using the Deactivation on lter option. If you use this lter,
deactivated assets are only displayed if they are deactivated within the selected scal year. Deactivated assets, which were
deactivated before the selected scal year, aren´t displayed.

The Deactivation on lter isn´t available in the standard variant of this app. To make this lter available, proceed as follows:

In the lter section, select Adapt Filters.

In the Adapt Filters popup, under Assets select the Deactivation on option.

Select OK in the popup.

 Example

This is custom documentation. For more information, please visit the SAP Help Portal 114
 8/16/2024
If your scal year begins on January 1, YYYY and you don´t want assets to be displayed, which were deactivated before this
date, then you must de ne the following conditions in the Deactivation on lter:

1. Condition with operator selection empty.

This condition makes sure that all assets, which aren´t deactivated yet, are displayed.

2. Condition with operator selection greater than or equal to and value January 1, YYYY..

This condition makes sure that all assets, which are to be deactivated during the selected scal year (January 1,
YYYY), are displayed.

See animated GIF below (English Only).

What are the differences between the Asset Transactions and Asset History Sheet
apps?
The Asset Transactions app shows a list of real postings in a table that offers various grouping options. It is used to check asset
acquisitions and retirements – information that is useful in your daily business. In contrast, the Asset History Sheet app
displays not only asset transactions but also planned values. It's a legal report that is generated periodically. In addition, the
Asset History Sheet is a grid-based app and can show various dimensions.

Supported Device Types

Desktop

Tablet

Additional Information
How to Work with Web Dynpro Reports (English Only)

This is custom documentation. For more information, please visit the SAP Help Portal 115
 8/16/2024

Open this video in a new window

 Note
Captions are available for multiple languages. Use the CC (Closed Captions) button in the video player to see which
languages are supported.

You can also use the Search within video eld to search for speci c text in the English or German captions.

Further Information

For information about the Asset Transactions app, see Asset Transactions.

For general informationen about multidimensional data grid apps, see Multidimensional Data Grid Apps.

App Extensibility: Asset History Sheet

You can extend the Asset History Sheet app according to your business needs.

Features
Key users can extend the app in the Custom Fields app using the business context Fixed Asset Master Data.

You can add elds to the following UI elements using UI adaption at runtime:

UI Element Business Context

Smart form Fixed Asset Master Data (FAA_ASSET_MASTER_DATA)

Additional Information
For more information about how to adapt an SAP Fiori UI at runtime, see Adapting SAP Fiori UIs at Runtime - Key User
Adaptation.

This is custom documentation. For more information, please visit the SAP Help Portal 116
 8/16/2024
For more information about the Custom Fields app, see Custom Fields.

Evaluation of Asset Values from Future Fiscal Years (Planning

Horizon)

Use
In reports such as the Asset History Sheet, Asset Balances, or Depreciation Lists, the evaluation of planned values from future
scal years is not supported by default. However, with the corresponding settings, you can enable this evaluation:

So, if you want to see planned values for scal years after the current scal year in your reports, you can specify a planning
horizon in years for each company code and ledger. The planning horizon de nes the number of years for which the planned
values are updated after the current scal year and are thereby available in reporting. The planned values are calculated for
each scal year and period, and are saved so that reporting can be period-based. You de ne the planning horizon at ledger level;
it is therefore valid for all depreciation areas of the ledger.

 Note
The planning horizon only affects reporting.

In the Manage Fixed Assets app however, you can also calculate and display all future asset values of an individual xed
asset, irrespective of the de ned planning horizon.

Prerequisite
You need to make the following settings:

1. De ne Planning Horizon (App 'Make Company Code Settings - Asset Accounting-Speci c')

You de ne the planning horizon in the app Make Company Code Settings – Asset Accounting-Speci c.

You de ne the planning horizon at ledger level; it is therefore valid for all depreciation areas of the ledger.

 Note
The way you de ne the planning horizon can signi cantly affect performance as well as the required memory space. This is
because planned values for future scal years are calculated and saved when you de ne the planning horizon. The amount of
data processed affects the runtime of the individual business transactions (for example, in the asset master record and
when posting transactions) as well as the amount of memory space required. Therefore, you should only de ne the planning
horizon (by entering a value larger than zero) for those ledgers for which you actually require the corresponding reporting.
You should also specify the smallest number of years possible for the planning horizon.

To de ne the planning horizon, follow these steps:

1. On the detail page of the required company code, select the ledger for which you want to de ne the planning horizon.

2. Choose the Edit pushbutton

3. Under Ledger Settings, make the following entries:

If you would like to have future scal years in reporting, enter the number of years you want for the planning
horizon; a value between one and ve is recommended.

This is custom documentation. For more information, please visit the SAP Help Portal 117
 8/16/2024
If you had de ned a planned value calculation but would like to deactivate this, then enter 0 years as the planning
horizon.

4. Choose Save.

2. Making Settings in the Reporting App

You may have to make relevant preparations in the respective reporting app: If necessary, display the planned values.

 Example

The planned values (key gure group AHS_PLAN) are available in the Asset History Sheet app, so you do not need to
show them separately. The planned and posted depreciation is displayed automatically.

In the Depreciation Lists app, you cannot select a key gure group. Instead, there is a column for the planned amount
in the column set for all depreciation types (ordinary depreciation, special depreciation, and so on). To display the
planned depreciation, display the column for each depreciation type.

Activities
Evaluate Planned Values

Evaluate the planned values in one of the reporting apps (for example, in the Asset History Sheet, in Asset Balances, or in
Depreciation Lists).

Recalculate Depreciation After Changes to Planning Horizon

If you either rst de ned the planning horizon or changed it, then you must recalculate depreciation for the affected ledger in
the company code. This recalculates the planned values for the newly con gured planning horizon and the planned values will
then be available in reporting.

 Caution
If you change the planning horizon without recalculating depreciation, this can cause incomplete planned values in reporting.

Recalculate Depreciation After a Balance Carryforward

When you perform a balance carryforward, afterwards you must recalculate depreciation for all company codes and ledgers for
which you have de ned a planning horizon. The recalculation of depreciation generates the planned records (after the balance
carryforward) for the year that was added at the end of the planning horizon.

 Example
You have de ned a planning horizon of three years. You perform the balance carryforward for the following year YYYY+1.

If you the recalculate the depreciation, the system generates the additional planned values for the year YYYY+1+3.

Value Display in Asset Reports Depending on the To Period

The purpose of the reports Asset Balances, Asset History Sheet, and Asset Transactions is different. As a result, the apps also
differ in the representation of the values.

For example, the apps differ in terms of value representation when looking at the To Period.

This is custom documentation. For more information, please visit the SAP Help Portal 118
 8/16/2024
The following example shows how the apps display a transfer during the year. In addition, the special case of display
authorization restricted to certain periods is taken into account.

Example

Starting scenario:

FixedAsset1 was acquired in the previous year ( scal year YYYY-1). The acquisition costs were 60,000.

FixedAsset2 was acquired in the current scal year ( scal year YYYY). The acquisition costs were 30,000.

In the current scal year ( scal year YYYY), a transfer of 30,000 is made to FixedAsset1 in period 007. Therefore, FixedAsset1 is
the receiving asset.

Posting Date Transaction Amount

01.01.YYYY-1 Acquisition for FixedAsset1 60,000

01.01.YYYY Acquisition for FixedAsset2 30,000

01.07.YYYY Transfer from FixedAsset2 to FixedAsset1 30,000

If a transfer is made to a xed asset acquired in the previous year in the new scal year, the values are displayed in the Transfers
column in the Asset History Sheet. The different display is explained below.

Display in Asset Balances

If you expand the Asset Balances by period, the system displays the transfers (posted with transaction type 320) within a scal
year in the period in which the posting document was created.

Selection: To Period 012/YYYY

... Fixed Asset To Period APC at Reporting Date, ...

Planned

Balance Amount

Fixed Asset1 # [Balance Carryforward 60,000

Value]

001

002

003

004

005

006

007 30,000

008

009

010

011

This is custom documentation. For more information, please visit the SAP Help Portal 119
 8/16/2024

... Fixed Asset To Period APC at Reporting Date, ...

Planned

Balance Amount

012

Overall Result 90,000

Selection: To Period 003/YYYY

... Fixed Asset To Period APC at Reporting Date, ...

Planned

Balance Amount

FixedAsset1 # [Balance Carryforward 60,000

Value]

001

002

003

Result 60,000

FixedAsset2 001 30,000

002

003

Result 30,000

Overall Result 90,000

Excursus: Effect of the To Period with restricted display authorization

If, for example, an auditor is only authorized to see the values up to and including period 003, the values are then displayed in
Asset Balances as follows:

For selection up to period 003:

Since the transfer was not posted until period 007, this is not yet taken into account on the FixedAsset1 being acquired,
but rather only the original APC value from the previous year. Instead, the APC value is displayed on the sending
FixedAsset2.

For selection up to period 007:

The original acquisition costs are displayed. Contrary to the display above, no value is displayed in period 007, since the
auditor is only allowed to see the authorizations for values up to period 003. Even though the To Period is 007, the xed
asset transfer is not taken into account in this case.

Display in Asset History Sheet

In Asset History Sheet (as well as in Asset Transactions), the values are displayed totaled in period 001. As a result, different
values are displayed depending on which periods were selected.

Selection: Period 001 to 012/YYYY

This is custom documentation. For more information, please visit the SAP Help Portal 120
 8/16/2024

... Fixed Asset To Period APC FY Start Acquisition, APC at Reporting

Current Year Date
Balance Amount
Balance Amount Balance Amount

FixedAsset1 # [Balance 60,000 60,000

Carryforward Value]

007 30,000 30,000

Result 60,000 30,000 90,000

FixedAsset2 001 30,000 30,000

007 -30,000 -30,000

Result 0 0 0

Overall Result 60,000 30,000 90,000

Selection: Period 001 to 003/YYYY

... Fixed Asset To Period APC FY Start Acquisition, APC at Reporting

Current Year Date
Balance Amount
Balance Amount Balance Amount

FixedAsset1 # [Balance 60,000 60,000

Carryforward Value]

Result 60,000 0 60,000

FixedAsset2 001 30,000 30,000

Result 0 30,000 30,000

Overall Result 60,000 30,000 90,000

Display in Asset Transactions

Selection: Period 001 to 012/YYYY

Asset Transaction Type Document Number/Text Period APC FY Start ...

Balance Amount

100 #1/Acquisition 001 30,000

FixedAsset2

320 #2/Transfer 007 -30,000

FixedAsset2 Being
Retired

330 #2/Transfer FixedAsset1 007 30,000

Being Acquired

Overall Result 30,000

Selection: Period 001 to 003/YYYY

Asset Transaction Type Document Number/Text Period APC FY Start ...

Balance Amount

This is custom documentation. For more information, please visit the SAP Help Portal 121
 8/16/2024

Asset Transaction Type Document Number/Text Period APC FY Start ...

Balance Amount

100 #1/Acquisition 001 30,000

FixedAsset2

Overall Result 30,000

Preparations for Production Operation and Con guration

Options
Before you can use Asset Accounting productively, you have to set up the company code.

You can use the legacy data transfer to transfer xed asset data from a feeder system to the SAP system.

If you want to make your own settings for Asset Accounting beyond the standard cloud con guration, you can use the existing
con guration steps (SSCUIs).

Prede ned Con guration

Scope Items for Asset Accounting

Overview of Scope Items

The following scope items are available for Asset Accounting:

Scope Item, ID Scope Item, Name More Information

J62 Asset Accounting See the SAP Signavio Process Navigator at

J62 .

1GB Asset Accounting - Group Ledger IFRS See the SAP Signavio Process Navigator at
1GB .

33F Asset Accounting - Group Ledger US GAAP See the SAP Signavio Process Navigator at
33F .

BFH Asset Under Construction See the SAP Signavio Process Navigator at
BFH .

1GF Asset Under Construction - Group Ledger See the SAP Signavio Process Navigator at
IFRS 1GF .

33G Asset Under Construction - Group Ledger See the SAP Signavio Process Navigator at
US GAAP 33G .

1IH Intercompany Asset Transfer Within the See the SAP Signavio Process Navigator at
Same Country 1IH .

5HG Asset Accounting – Additional Depreciation See the SAP Signavio Process Navigator at
Area 5HG .

See also the section below in this

document.

This is custom documentation. For more information, please visit the SAP Help Portal 122
 8/16/2024

Scope Item, ID Scope Item, Name More Information

5KF Asset Under Construction – Additional See the SAP Signavio Process Navigator at
Depreciation Area 5KF .

See also the section below in this

document.

6VB Asset Accounting – Additional Depreciation See the SAP Signavio Process Navigator at
Keys for Local GAAPs 6VB .

See also the section below in this

document.

5HG and 5KF in detail

Use

Some local or industry-speci c rules (for example, for utility companies) may contain speci c rules for depreciation and
reporting. To meet these needs, you can activate the above-mentioned scope items 5HG und 5KF.

When you activate these scope items, an additional depreciation area is added. This depreciation area is for Asset Accounting
purposes only. It contains postings that are only relevant for Asset Accounting (known as statistical postings).

The two scope items provide pre-con gured content, such as a speci c valuation view and speci c depreciation terms for asset
classes at accounting principle and valuation view level.

The use of the scope items optional.

Prerequisites

You can implement the additional depreciation area using the scope items 5HG and 5KF, provided that the following
prerequisites are met:

You use the SAP Central Business Con guration (CBC) as your con guration environment.

You start the system setup in an empty system and choose the scope items 5HG and 5KF already during the initial scope
de nition.

Precon gured content

Along with the scope items 5HG and 5KF, the following pre-con gured content is available:

Object Technical Name Further Details

Valuation View 0<country code>_0DE_0016 SAP delivers the assignment of the

valuation view to the corresponding
(for example 0DE_0016, 0US_0016)
accounting principle. For example,
0DE_0016 is assigned to accounting
principle DEAP.

Depreciation Area 16 The system automatically creates

depreciation area 16 in all local legders
where the accounting principle is assigned.

Asset Class Default -- Taken over from source valuation view

0<country code>_0001.

This is custom documentation. For more information, please visit the SAP Help Portal 123
 8/16/2024

Implementation

Capitalization

You activate the scope items during initial scoping in an empty system.

Please note that it is not possible to set up a new depreciation area subsequently (that is, if master data and transaction data
already exists).

If you want to activate scope item 5KF, you must also activate 5HG, since scope item 5HG is a prerequisite for 5KF.

Recommendation

If you want to use the additional depreciation area, we recommend that you activate both scope items (not just one of them).

This is because the functionality can only be introduced during initial scoping and subsequent implementation of the
functionality (after initial scoping) is not possible.

Moreover, scope item 5HG is the prerequisite for 5KF anyway.

Con guration

For the additional depreciation area, you create the asset classes and select the depreciation keys to suit your requirements.

Legacy Data Transfer

You can perform a legacy data transfer for the additional depreciation area. You proceed in the same way as for other
depreciation areas for this.

6VB in detail
Use

Scope item 6VB contains precon gured depreciation keys for local accounting principles; these depreciation keys are made
available from the main scope item of Asset Accounting J62 in addition to the depreciation keys required by law.

The 6VB scope item contains only depreciation keys for local accounting principles and country versions: The scope item is
localized for the following countries: Belgium; Brazil; Canada; China; France; India; Japan; South Korea; Mexico; Netherlands;
Switzerland; Thailand; USA

You can use these depreciation keys either on asset level or replace the asset class standard values per valuation view.

 Recommendation
Before you use these depreciation keys, you must check whether you are allowed to use them in your country and industry.

The use of the scope items is optional.

Prerequisites

As a con guration environment, use SAP Central Business Con guration (CBC) or the Con gure Your Solution app.

Make Company Code Settings - Asset Accounting-Speci c

This is custom documentation. For more information, please visit the SAP Help Portal 124
 8/16/2024
App ID: F7312

You can use this app to set up new company codes for Asset Accounting before you use them productively. You can also make
the settings for the legacy data transfer and for the evaluation of future scal years. You can also perform year-end closing.

Features
In detail, you can use this app to do the following:

De ne Company Code Status and Set Company Code Block

De ne Current Fiscal Year (for a New Company Code)

Prepare Legacy Data Transfer: Create and Change Legacy Data Transfer Segments with Parameters

Perform Year-End Closing for Individual Depreciation Areas

Reset Year-End Closing for Individual Depreciation Areas

De ne Planning Horizon for Evaluating Future Fiscal Years

Authorizations
The following authorizations are relevant for the app:

Authorization to display and change company codes in Asset Accounting

For the closing and opening of scal years: Authorization for periodic processing in Asset Accounting

Supported Devices
Desktop

Tablet

Additional Information
For more information about the individual functions of the app, see the following documents:

Year-End Closing for Individual Depreciation Areas

Evaluation of Asset Values from Future Fiscal Years (Planning Horizon)

Set Up Company Code

Preparations: Create Legacy Data Transfer Segment with Parameters

Set Up Company Code

If you are setting up a new company code for Asset Accounting, you need to consider the following points.

General Prerequisites
The following general prerequisites must be ful lled for your company code:

This is custom documentation. For more information, please visit the SAP Help Portal 125
 8/16/2024
Your company code already exists.

You have made the posting-relevant settings for the company code.

For the con guration environment Con gure Your Solution, you do this under Finance General Ledger Company
Codes .

De ne Company Code Status and Set Company Code Block

To set up or block the company code for Asset Accounting, use the app Make Company Code Settings - Asset Accounting-
Speci c (F7312).

De ne Company Code Status

Possible company code statuses are For Testing, Productive, and Deactivated.

The table below details how to use the company code status:

Company Code Status Use and Prerequisites Effect

Test Operation To set up a new company code, select the With this status, it is possible to delete
status Test Operation. accounting data in the Q system; this also
applies to master data and transaction data
in Asset Accounting. To delete, use the
Reset Transaction Data job template from
the app Schedule Accounting Data
Corrections.

See also the application help (product

assistance) for General Ledger Accounting
under Reset Transaction Data.

Productive As soon as you want to use the company With the status Productive, it is no longer
code productively in Asset Accounting, set possible to delete master data and
its status to Productive. transaction data.

Deactivated You deactivate a company code, for With the status Deactivated, It is not
example, so that a company code that is no possible to post any postings at all in Asset
longer used productively is no longer taken Accounting.
into account in reporting.
 Caution
You can only deactivate a company code if
the following prerequisites are met: Once a company code has the
status Deactivated, you can no
There are no active assets in the
longer make settings for that
company code.
company code (in the app Make
The planned depreciation for this Company Code Settings -
company code was completely Asset Accounting-Speci c
posted to the general ledger. (F7312)).

Changing the status to

Deactivated is irreversible.

Procedure

1. In the app Make Company Code Settings - Asset Accounting-Speci c, you navigate to the detail view for the company
code.

2. Choose the Change Status button and then choose the new status for the company code.

This is custom documentation. For more information, please visit the SAP Help Portal 126
 8/16/2024

Set Company Code Block

When a company code is blocked in Asset Accounting, it is no longer possible to make postings on xed asset accounts or
changes to the asset master records in the company code.

Procedure

1. In the app Make Company Code Settings - Asset Accounting-Speci c, you navigate to the detail view for the company
code.

2. Choose the Block button.

De ne Closed and Current Fiscal Year

Before you can make the rst postings in Asset Accounting for the current scal year, you need to de ne the closed and the
current scal year in the app Make Company Code Settings - Asset Accounting-Speci c. You have the following options for
doing this:

Automatic determination during legacy data transfer:

If you want to perform a legacy data transfer, proceed as follows:

Create a legacy data transfer segment on the Legacy Data Transfer tab page. Enter a legacy data transfer date for the
legacy data transfer segment.

The system then automatically derives the current scal year and the scal year last closed from the legacy data
transfer date.

Manual Determination:

If you do not carry out a legacy data transfer (for example, because your company is new), then specify the highest open
scal year (Highest Fiscal Year) manually in the ledger settings.

You can only set the highest open scal year manually if there are no assets in the corresponding company code.

See Also
To choose the correct ledger combination, see the application help (product assistance) for General Ledger Accounting at
Ledger Scenarios: Choosing the Right Combination for Your Business Needs.

Perform Legacy Data Transfer with Subsequent Balance

Carryforward
If you want to transfer asset master data and asset values from a legacy system to the SAP system, you can use the methods
provided by SAP: You can either transfer the legacy data automatically using the SAP S/4HANA Migration Cockpit (using an
XML template) or manually.

If you have executed a legacy data transfer at the end of the previous year, a balance carryforward to the current scal year
must also take place. The system performs the balance carryforward automatically on a regular basis. If you want to execute it
immediately, use the Balance Carryforward job template to do this manually in General Ledger Accounting (see Balance
Carryforward).

Additional Information

You can nd additional information on the legacy data transfer in the following places:

This is custom documentation. For more information, please visit the SAP Help Portal 127
 8/16/2024
In the system documentation:

In the con guration help for the app Make Company Code Settings - Asset Accounting-Speci c, you can refer to the
Legacy Data Transfer section to see which settings you need to make.

In the product assistance (application documentation):

Background information with lots of examples can be found under Legacy Data Transfer.

Information about what to do if you have transferred incorrect legacy data can be found under Reset Incorrectly
Transferred Legacy Data

Using Con guration Options

 Note
New customers starting with SAP S/4HANA Cloud 2011 or higher are automatically connected to the SAP Central Business
Con guration.

For customers with existing SAP S/4HANA Cloud systems, a step-by-step migration is planned from the current
con guration environment with the app Con gure Your Solution to the SAP Central Business Con guration. For more
information, see Con guration Environment of SAP S/4HANA Cloud.

The following sections explain in more detail about the con guration environment SAP Central Business Con guration.

Con guring Asset Accounting

You can use the standard Cloud con guration provided for Asset Accounting without making your own settings.

However, if you want to do so, you can also de ne your own settings for Asset Accounting using the con guration activities. All
con guration activities are optional.

The following con guration activities are available:

Con guration Activity (ID) What you can do Scope Item

De ne Account Determination (102626) You can de ne the key and the name of your All Asset Accounting scope items
own account determination in Asset
Accounting. The account determination links
an asset master record with the G/L
accounts being posted to.

Assign G/L Accounts (102622) For Asset Accounting transactions, you can All Asset Accounting scope items
specify which accounts in General Ledger
Accounting should be posted to (asset
balance accounts, clearing accounts, or
offsetting accounts, etc.).

De ne Asset Class (102606) You can de ne your own asset classes for All Asset Accounting scope items
Asset Accounting.

Make Valuation View-Dependent Settings De ne the depreciation terms that should All Asset Accounting scope items
for Asset Class (102609) be used in the asset class at the level of the
accounting principle and the valuation view.

Specify Amounts (102610) You can specify your own maximum All Asset Accounting scope items
amounts for low-value assets (LVA).

This is custom documentation. For more information, please visit the SAP Help Portal 128
 8/16/2024

Con guration Activity (ID) What you can do Scope Item

De ne Depreciation Areas in Company For existing depreciation areas, you can All Asset Accounting scope items
Code (105494) de ne the following settings:

You can change the name of the

depreciation area.

You can adjust the rounding

settings.

 Note
In the Con gure Your Solution app, you
cannot change settings, you can only
display existing settings.

Additional Information

For more information, see the documentation of the respective con guration activity.

Display Depreciation Key

The depreciation keys available in the system are prede ned. You cannot create any new depreciation keys and you can also not
change any existing depreciation keys.

To display detailed information for a speci c depreciation key of a chart of depreciation, you can use the app Depreciation Key:
Display Details (FAA_DEPRKEY_SHOW). The app provides you with a detailed overview of all in uencing factors (calculation
methods, depreciation phases, and so on) for the depreciation key.

Additional Information

For more information, see Depreciation Key

Legacy Data Transfer

Use
A legacy data transfer is the transfer of existing data from a previous system or from a xed asset card le maintained outside
the accounting system. The transfer of legacy data is generally the rst action after you con gure the Asset Accounting
component and classify your assets.

Legacy data transfer includes the transfer of the following data:

Asset master records

Asset values

Cumulated values from the previous year

For a legacy data transfer during the scal year: if necessary, the transfer of depreciation for the scal year of the
transfer

For legacy data transfer during the scal year: the transfer of transactions from the start of the scal year up to
the time of the transfer

This is custom documentation. For more information, please visit the SAP Help Portal 129
 8/16/2024
If required, you can also transfer usage objects; these are required for the units-of-production depreciation. You can only
transfer usage objects automatically, that is, using the SAP S/4HANA migration cockpit.

Features
The following methods of the legacy data transfer are available for Asset Accounting:

Transfer Method Use Constraints

Manual Legacy Data Transfer Small data volumes (individual assets,

pretest for automatic transfer,
postprocessing)

Automatic Transfer Medium and large amounts of data

No assets under construction that
With the SAP-S/4HANA Migration Cockpit are linked to investment measures
(by using an XML template)
No investment support

No external number assignment

With the transfer of the asset values and with the transfer of transactions, balances are updated on the general ledger
accounts in General Ledger Accounting.

 Recommendation
An incorrect legacy data transfer cannot simply be reset.

You should therefore plan enough time for the legacy data transfer in advance and prepare for it properly. Before you
transfer the legacy data to the production system, you should have run a complete and correct test, reconciled with the
legacy system, in the test system.

Preparations: Create Legacy Data Transfer Segment with

Parameters
You must rst prepare the legacy data transfer:

You must ensure that the prerequisites listed below are met.

You make the settings for the legacy data transfer by creating a legacy data transfer segment that contains the
parameters for the legacy data transfer.

 Note
You must create a legacy data transfer segment in any case, regardless of the time of the transfer (at the end of the
year or during the year) and also independent of the transfer method (manually or automatically using the SAP
S/4HANA migration cockpit).

Then you can perform the legacy data transfer.

Check Prerequisites
Before you create a legacy data transfer segment, the following prerequisites must be met:

This is custom documentation. For more information, please visit the SAP Help Portal 130
 8/16/2024
Asset Accounting is con gured consistently and completely.

When you create a legacy data transfer segment, the system checks the scal years that are open in Asset Accounting.
The prerequisites are as follows:

For a transfer at the end of the scal year, the scal year after the transfer must be the rst open scal year.

Example: The transfer is to take place on 12/31/YYYY. Then the scal year YYYY must be closed and YYYY+1
must be open.

In the case of a legacy data transfer during the year, the scal year in which the transfer takes place must be
open; previous scal years are closed.

Example: The transfer is to take place on 03/31/YYYY. Then scal year YYYY-1 must be closed and YYYY must be
open.

Existing Settings

The following setting exists in the system:

An offsetting account for the legacy data transfer is de ned. The account is assigned in a nancial statement item with
other transfer accounts (for example, for transferring G/L account balance and open items of customers/vendors/G/L
accounts). The total of all accounts for the legacy data transfer balances in accordance with the complete legacy data
transfer and the reconciliation of the legacy system and SAP system to zero.

Important for New Customers

Before you start with the legacy data transfer and start using Asset Accounting, note the following for a new company code:

The system determines the current scal year and the last closed scal year based on the transfer date of the rst
legacy data transfer segment. The transfer date of Asset Accounting is therefore the validity start date for a company
code.

The transfer date of Asset Accounting is not allowed to be before the transfer date of General Ledger Accounting.

You de ne the transfer date of General Ledger Accounting in the app De ne Settings for Legacy Data Transfer in the
Migration Date eld.

Create Legacy Data Transfer Segment with Parameters

To create a legacy data transfer segment with the corresponding parameters, use the app Make Company Code Settings -
Asset Accounting-Speci c (F7312). Create a legacy data transfer segment on the Legacy Data Transfer Settings tab page.

Parameters

Some parameters are prede ned by the system, others must be de ned by you:

The system assigns a sequential number for the legacy data transfer segment.

You de ne the transfer date: This is the calendar date on which the assets are transferred to the SAP System.

The legacy data transfer can take place at scal year end or during the year.

Transfer at the end of the scal year: In this case, the transfer date is identical with the scal year end. All
transactions starting in the new scal year are then carried out only in Asset Accounting. The transfer occurs with
the cumulative values at the end of the scal year.

Transfer during the scal year: The transfer date can also be during the scal year. In this case, the asset values
are transferred at the end of the previous scal year. Apart from the cumulative values at the end of the scal
This is custom documentation. For more information, please visit the SAP Help Portal 131
 8/16/2024
year, you must also transfer the transactions that have occurred since the start of the scal year. The
depreciation posted in the year of the transfer can either be transferred from the legacy system or calculated in
the SAP system and then posted with the depreciation run.

Note the following dependencies:

The system automatically derives the last closed scal year from the transfer date as already mentioned above.

Example 1: Transfer date = 12.31.YYYY

=> last closed scal year = YYYY

Example 2: Transfer date = 03.31.YYYY

=> Last closed scal year = YYYY-1

As also mentioned above, the transfer date of Asset Accounting must either coincide with the transfer date of
General Ledger Accounting or be later.

Transfer status:

The legacy data transfer segment then rst has the status In Preparation.

At any given time there can only ever be one segment for which a legacy data transfer is being performed or for
which the segment has the status In Preparation.

With this status, the system allows the settings for the legacy data transfer to be incomplete (for example, the
document type for legacy data transfer postings may still be missing).

If the status is Ongoing, only legacy data transfer postings are allowed; other types of postings (for example,
acquisition and retirement postings) are not allowed.

If the status is Ongoing (Other Postings Allowed), both legacy data transfer postings and other postings are
allowed. This status is useful if you are carrying out further legacy data transfers in a company code that is
already productive.

As soon as the legacy data transfer has been performed successfully (so posted and reconciled), you should set
the status of the segment to Completed. This means that no further master data for legacy xed assets can be
created and no further transfer values can be posted for the affected legacy data transfer segment using the
legacy data transfer for the company code.

This document type is used to post the posting documents in the context of legacy data transfer.

If you have to transfer lots of xed assets (mass data), for performance reasons you can suppress the calculation of
planned values for the depreciation during the legacy data transfer. To do so, you set the Suppress Depreciation
Calculation indicator. You must then subsequently perform the recalculation of depreciation in the app for Asset
Accounting jobs (see Recalculate Depreciation).

Procedure: Create New Legacy Data Transfer Segment

To create a new legacy data transfer segment, proceed as follows in the app Make Company Code Settings - Asset Accounting-
Speci c (spezi sch (F7312):

1. From the initial screen of the app, choose the company code for which you want to create the legacy data transfer
segment.

2. In the detail screen for the company code, choose the Editpushbutton.

3. On the Legacy Data Transfer Settings tab, choose the pushbutton Create.

4. Specify the required parameters or check the default values:

This is custom documentation. For more information, please visit the SAP Help Portal 132
 8/16/2024
a. Enter a transfer date.

b. Check the transfer status.

c. Check the proposed document type.

d. If necessary, set the indicator for suppressing depreciation calculation.

e. Enter a comment, if necessary.

5. Choose Save.

 Note
As long as there are no legacy assets for a new legacy data transfer segment in the system, you can delete the segment
again.

Additional Legacy Data Transfers After the First Legacy Data Transfer

If you want to perform another legacy data transfer for a company code at a later transfer date, then create a new (another)
legacy data transfer segment for this company code. This may be necessary, for example, if your company takes over another
company.

Reopening a Completed Legacy Data Transfer Segment

You can reopen a legacy data transfer segment that has been closed, in order to make adjustment postings or additional
postings, for example.

 Example
Several legacy data transfers were carried out and completed during the scal year. The system determines that the legacy
data transfer is incomplete and also contains a posting with incorrect values whilst performing year-end closing activities (or
an external auditor does).

You can also reopen a segment from a previous scal year, that is, from a scal year before the current scal year. To do this,
you may have to reopen a scal year that has already been closed. The usual conditions for reopening closed scal years then
apply, and the system performs the usual consistency checks for the posting in the reopened scal year.

 Note

It is possible to have more than two scal years open at the same time.

However, only one legacy data transfer segment can be open at a given time. This means that to be able to reopen a
segment, all other segments must be closed.

Outlook: Time Schedule for the Legacy Data Transfer

A journal entry is made with the transfer of asset values and with the transfer of transactions (the latter is necessary during a
legacy data transfer during the year). The system posts the postings for the legacy data transfer with the prede ned document
type. It uses the offsetting account for the legacy data transfer as the offsetting account.

Proceed as follows for the legacy data transfer:

1. Set the legacy data transfer status for the legacy data transfer segment to Ongoing or to Ongoing (Other Postings
Allowed).

This is custom documentation. For more information, please visit the SAP Help Portal 133
 8/16/2024
2. Perform the legacy data transfer manually or automatically using the SAP S/4HANA migration cockpit.

3. Check the result and reconcile it with the legacy system.

4. After a successful legacy data transfer, set the legacy data transfer status for the legacy data transfer segment to
Completed.

For details on the legacy data transfer process, see the following sections.

Transferring Assets under Construction

Use
As you can manage assets under construction (AuC) with line item management, they require special treatment during the
legacy data transfer.

Features
An automatic transfer with the SAP S/4HANA Migration Cockpit is only possible for independent assets under construction. For
assets under construction with integration in investment measures (that is, for assets under construction for which the Assets
under construction for capital investment measures indicator is set in the asset class), on the other hand, no transfer is
possible.

In any case, you can transfer assets under construction by using the manual legacy data transfer. To do this, you use the
Transfer Open Items from AuC – For Legacy Asset app.

Assets under construction with line item management manage acquisitions over the course of a number of scal years as line
items, without cumulating them. This is also possible in the SAP System. For these assets under construction, the open items
not yet settled that were acquired before the date of the legacy data transfer must be transferred as transactions.

For assets under construction with line item management, you can therefore not transfer any accumulated acquisition costs
(APC) and also not transfer any accumulated depreciation. The data transfer must occur when transferring the transactions
instead.

The line items must be transferred with the special transaction type for prior-year acquisitions (900 - Takeover open items APC
(AuC)). This applies for both a legacy data transfer during the year and a legacy data transfer at the end of the scal year.

 Note
If you have the special case of proportional depreciation on the AuC, then enter this as proportional depreciation from the
previous years using the transaction.

Asset value date

You cannot transfer the historical asset value date for these transactions. For a transfer at the end of the scal year (e.g.
31.12.YYYY-1), the system always uses the rst day of the current scal year that follows the year of the legacy data transfer as
the asset value date (e.g. 01.01.YYYY). For a legacy data transfer during the year (e.g. 28.02.YYYY), the system uses the rst
day of the scal year in which the transfer takes place (01.01.YYYY).

Constraints

The following restrictions apply to the legacy data transfer for AuC:

This is custom documentation. For more information, please visit the SAP Help Portal 134
 8/16/2024
The legacy data transfer for AuC connected to investment measures is not supported. You can only use the transfer for
an independent AuC. For the nal settlement the values transferred on the independent AuC must be transferred
separately with the AuC settlement to the receiver of the nal settlement.

In the case of a transfer within the scal year, it is not possible to transfer settlement documents of those line items that
have already been settled in the scal year of the transfer. For more information, see Transfer During the Fiscal Year.

Examples
You can nd examples of assets under construction in the following places:

Example 4: Transfer at End of Fiscal Year for AuC with Line Item Management

Example 5: Transfer During the Year for an AuC with Line Item Management

Time of Transfer
The transfer date is the cut-off date for the transfer of legacy data. The transfer will only include data up to this point in time.
There are two possibilities:

Transfer at the end of the scal year:

Here the transfer date is the end of the last closed scal year.

With a transfer at the end of the scal year (YYYY-1), only the following scal year (YYYY) is allowed to be open.

Transfer during the scal year:

Here the transfer date can be in the scal year that directly follows the last closed scal year.

 Example
The following data exists for a transfer during the year:

Posting date = transfer date (02/28//YYYY)

Asset value date = 01/01/YYYY with transfer during the year (cumulated values)

With a transfer during the year in year YYYY, only the scal year of the transfer (YYYY) is allowed to be open.

You create a legacy data transfer segment for a speci c company code. You enter the legacy data transfer date in such a
segment.

 Note
The system adopts the transfer date in the master record of the legacy asset as the value date. As soon as you have created
the rst legacy xed asset, you can no longer change the transfer date in the segment.

Note that the transfer date is generally not the same as the date when the data was actually entered. Normally, you create
legacy data after the transfer date. This could be necessary, for example, if you have to perform a closing in your legacy system
between the transfer date and the date of the actual transfer. The consequences of the this difference will be explained later in
more detail.

You can also transfer legacy assets to the SAP System before the transfer date. However, you then have to make sure that the
transactions that you post in your legacy system up until the transfer date are also later posted (reposted) in the SAP Asset
Accounting component.

This is custom documentation. For more information, please visit the SAP Help Portal 135
 8/16/2024

Transfer at End of Fiscal Year

Use
With a transfer at the end of the scal year, the transfer date is the date at the end of the last closed scal year. (In the example
below, the transfer date should be de ned as 31.12.YYYY-1.)

In the case of a legacy data transfer at the end of the scal year, you do not need to include any depreciation or transactions
posted during the year in the transfer of legacy data. Transfer only master data and the asset values (this means the APC and
the accumulated depreciation) with the status at the end of the last closed scal year. (In the gure below, this is the data of
period A.)

Prerequisites
For a transfer at the end of the scal year (YYYY-1), the scal year with the transfer date is closed (YYYY-1), the scal year after
the transfer date (YYYY) is open.

Process
The following applies: Transfer date = scal year end YYYY-1

Step App Example

(For manual transfer) (see below)

1. Enter master data with the status on the Manage Legacy Assets Entry for period A
date of transfer

2. Enter asset values for each master Post Transfer Values – For Legacy Asset Entry for period A
record with the status of the transfer date

3. Reserve for special depreciation (if any): Entry for period A

Enter balances of the corresponding G/L
accounts with the status on the transfer
date in the general ledger

4. Reconcile legacy data transfer at end of

the scal year with the legacy system Asset History Sheet

Manage Fixed Assets

Asset Balances

5. Asset-relevant business transactions that To repost these business transactions: Repost for period C
occur after the transfer date have to be
reposted subsequently after the complete Apps for posting acquisitions, retirements,
legacy data transfer and reconciliation. and so on.

This is custom documentation. For more information, please visit the SAP Help Portal 136
 8/16/2024

Time sequence of legacy data transfer at end of fiscal year

Example
Prerequisites

You have created a legacy data transfer segment with the following parameters:

Transfer date = last closed scal year (31.12.YYYY-1)

Document type for the legacy data transfer

You have chosen in execution or in process (Other Postings Allowed) as the status of the legacy data transfer segment.

An offsetting account for the legacy data transfer (asset balance sheet account) is de ned in the system.

Assuming:

There are two ratings:

Valuation 1: local accounting principle as the leading valuation

Valuation 2: IFRS as the parallel valuation

The asset with an acquisition cost of 60,000 was capitalized on 01.01.YYYY-2.

The xed asset was as such depreciated over two years in the legacy system.

Based on valuation 1, the asset should be depreciated over ve years; based on the valuation 2 it should be depreciated
over three years.

Legacy Data Transfer

You transfer your legacy data manually.

The following documents with date 31.12.YYYY-1 are created:

1a) xed asset balance sheet account and xed asset accumulated depreciation account to offsetting account for legacy
data transfer

with valuation 1

1b) xed asset balance sheet account and xed asset accumulated depreciation account to offsetting account for legacy
data transfer

with valuation 2

This is custom documentation. For more information, please visit the SAP Help Portal 137
 8/16/2024

Transfer During the Fiscal Year

With a transfer during the year, the transfer date is in the scal year that directly follows the last closed scal year. In this case,
all business transactions up to the date of the transfer are carried out in the legacy system.

Time sequence for a transfer during the year

You transfer the following data from the legacy system:

Data App Explanation

(For manual transfer)

Master data Manage Legacy Assets

Asset values (for example, APC and Post Transfer Values – For Legacy Asset In the graphic: Period A
accumulated depreciation)

As at the end of the last closed scal year

If applicable, depreciation that was posted Post Transfer Values – For Legacy Asset See the following section.
in the legacy system in the current scal
year before the transfer date.

Transactions that were posted in the current See the section further down.
scal year before the transfer date in the
legacy system

Posted Depreciation
You have the following options:

You transfer the posted depreciation from the legacy system.

Alternatively, you can perform the legacy data transfer without the posted depreciation of the current scal year, then
after the legacy data transfer, you get the depreciation in the SAP system by using the depreciation run.

Transfer posted depreciation from the legacy system

Include the depreciation posted in the legacy system since the end of the last closed scal year up to the date of transfer (time
period B).

In the case of a manual legacy data transfer, you use the app Post Transfer Values – For Legacy Asset.

This is custom documentation. For more information, please visit the SAP Help Portal 138
 8/16/2024

 Note
When transferring posted depreciation from the current scal year, you must also enter the following information for the
depreciation period: For each asset, you specify the depreciation period last posted in the legacy system (for a manual
legacy data transfer in the eld Depreciation Period). The system requires this information to determine the rst period for
the depreciation that should be posted in the system.

Calculate and post posted depreciation in the SAP system (after the legacy data transfer)

If you do not want to transfer any depreciation posted from your legacy system, you have an alternative. After the legacy data
transfer, you can "catch up" the posting of depreciation by carrying out a depreciation posting run. This posting run will "catch
up" all depreciation in the current scal year up to the date of the transfer. In this case the system posts all depreciation that
Asset Accounting determines for this time period. That depreciation is posted with an offsetting entry to the transfer account
for the legacy data transfer. The posting to the expense account (P&L account) must take place as part of the balance transfer
for the G/L accounts.

If, therefore, you do not want to transfer posted depreciation, you do not need to specify a value for the transfer of asset values
in the eld for the period up to which depreciation was posted in the legacy system; or you can enter the value 000.

Start of depreciation postings

For xed assets from a legacy data transfer during the year, the depreciation is rst posted in the period that follows the legacy
data transfer.

 Example
Example 1:

The date of the legacy data transfer is 30.09. For the legacy data transfer, you enter the depreciation already posted in the
legacy system up to and including period 6. The SAP system then calculates the values for periods 7 to 12.

The system does not post depreciation at rst for this xed asset in the periods up to and including period 9. The system rst
posts the values for the periods 7, 8, 9, and 10 with the posting run for period 10 (of the rst period that follows the legacy
data transfer), not before.

Example 2:

The date of the legacy data transfer is 01.09. For the legacy data transfer, you enter the depreciation already posted in the
legacy system up to and including period 6. The SAP system then calculates values for periods 7 to 12.

The system does not post depreciation at rst for this xed asset in the periods up to and including period 8. The system rst
posts the values for the periods 7, 8 und 9 with the posting run for period 9, not before.

Example 3:

For a legacy data transfer between the 02.09. and the 29.09., the system behaves in the same way as for a transfer on
30.09.: It posts depreciation from period 10 onwards.

Transactions
Transactions before the transfer date in the year of the transfer

When transferring legacy data during the scal year, you also have to include the transactions from the end of the last closed
scal year up to the date of transfer (time period B).

This is custom documentation. For more information, please visit the SAP Help Portal 139
 8/16/2024
For a manual transfer, you enter the transactions with the app relevant for the transaction. (For an example of an acquisition
before the transfer date in the year of the transfer, see Example 3: Transfer During the Year with More Transactions in Year of
Transfer.)

When these transactions are entered, the G/L accounts are also updated in the general ledger.

Proportional depreciation does not apply to the mid-year transactions. These are handled as follows:

For a manual legacy data transfer, the following applies:

The proportional values for depreciation are calculated automatically with the transfer of a transaction during the year.

For an automatic transfer of legacy data, the following applies:

The proportional values for depreciation are not calculated automatically, they must be explicitly posted.

Business transactions after the transfer date

Any asset transactions in your legacy system that have a value date after the transfer date, but before the date of the physical
transfer of data (time period C), have to be reposted in Asset Accounting after the data transfer and reconciliation between the
legacy system and SAP system.

For legacy assets (in the example, for assets that were acquired before 28.02.YYYY-1), the following applies: You must repost
the asset-relevant business transactions in Asset Accounting that occur in period C after the data transfer and reconciliation of
data.

Line items of an asset under construction (AuC)

In the case of a transfer during the year, you can also transfer line items of an asset under construction that were posted in the
scal year of the transfer before the transfer date. However, the following restriction applies.

Constraint: No transfer of line items settled in transfer year

If you want to perform a mid-year legacy data transfer of independent assets under construction and have already settled a line
item to the completed asset in the year of the transfer before the transfer date, note the following restriction that applies to
both the automatic legacy data transfer and the manual legacy data transfer:

It is not possible to transfer this settlement document (with retirement posting for the AuC and acquisition posting on the
completed asset) as part of the legacy data transfer. This means that the mid-year acquisition posting on the completed asset
cannot be transferred.

Instead, you must transfer the original line item (that was settled in the year of the legacy data transfer) to the independent
AuC; you either transfer it manually using the app Transfer Open Items of AuC – For Legacy Asset or automatically using the
SAP S/4HANA Migration Cockpit (see also the Automatic Transfer section on Transferring AuC with Line Item Management).

After you have performed the legacy data transfer, you settle the line item accordingly.

Examples: Time of Transfer

Starting Situation for All Examples

A scal year variant is de ned in the company code that corresponds to the calendar year and uses 12 periods.

There are the following ratings:

This is custom documentation. For more information, please visit the SAP Help Portal 140
 8/16/2024
Valuation 1: local accounting principle as the leading valuation

Valuation 2: IFRS as the parallel valuation

To be able to post transfer documents, you must have created a legacy data transfer segment to which a transfer date and a
document type for the legacy data transfer are assigned.

An offsetting account for the legacy data transfer (asset balance sheet account) is de ned in the system. This account
“Offsetting Account for Legacy Data Transfer” is assigned in a nancial statement item together with other accounts for the
legacy data transfer (for example, for transferring G/L account balance and open items of customers/vendors/G/L accounts).

The total of all accounts for the legacy data transfer balances in accordance with the complete legacy data transfer and the
reconciliation of the legacy system and SAP system to zero.

Example 1: Transfer at End of Fiscal Year

You want to perform a legacy data transfer at the end of a closed scal year, so on 12.31.YYYY-1. You de ne this date as the
transfer date in the legacy data transfer segment (in Current Settings using the app Make Company Code Settings - Asset-
Accounting-Speci c, tab Legacy Data Transfer).

You have an asset with an acquisition cost of 60,000 which was capitalized on 01.01.YYYY-2. The xed asset was as such
depreciated over two years (straight line) in the legacy system. According to valuation 1, the xed asset should be depreciated
over 5 years; according to valuation 2, it should be depreciated over 3 years.

Valuation 1:

Year Start value Value adjustment Ending level

1 60,000 12,000 48,000

2 48,000 12,000 36,000

3 36,000 12,000 24,000

4 24,000 12,000 12,000

5 12,000 12,000 0

Valuation 2:

Year Start value Value adjustment Ending level

1 60,000 20,000 40,000

2 40,000 20,000 20,000

3 20,000 20,000 0

Proceed as follows:

1. You create a master record for the legacy asset with all details.

(App: Manage Legacy Assets

You de ne 01.01.YYYY-2 as the capitalization date.

This is custom documentation. For more information, please visit the SAP Help Portal 141
 8/16/2024
2. You enter the following transfer values for this legacy asset: the cumulated acquisition and production costs and the
cumulated ordinary depreciation at the end of the scal year, that is, at the end of the scal year of the second year
(12.31.YYYY-1).

(App: Post Transfer Values – For Legacy Asset)

The system generates the following accounting principle-speci c (or ledger-speci c) documents with posting date and asset
value date 12.31.YYYY-1:

Document Accounting Principle Debit/Credit Account Amount

1) Valuation 1 Debit Fixed asset balance 60,000

sheet account(1)

1) Valuation 1 Cr Asset value adjustment 24,000

account(2)

1) Valuation 1 Cr Offsetting account for 36,000

legacy data transfer

2) Valuation 2 Debit Fixed asset balance 60,000

sheet account(1)

2) Valuation 2 Cr Asset value adjustment 40,000

(2)
account

2) Valuation 2 Cr Offsetting account for 20,000

legacy data transfer

Explanation:

(1) The accumulated APC is posted with transaction type 970.

(2) The accumulated ordinary depreciation is posted with transaction type 970.

Example 2: Transfer During the Fiscal Year

You want to perform a legacy data transfer during the year at the end of February on 02.28.YYYY. You de ne this transfer date
in the legacy data transfer segment (in Current Settings using the Make Company Code Settings - Asset-Accounting-Speci c
app, tab page Legacy Data Transfer). The preceding scal year YYYY-1 is closed.

You have already posted the depreciation for periods 01 and 02 in the legacy system. The posted depreciation of periods 01 and
02 should be posted as accumulated ordinary depreciation. In the SAP system the depreciation should rst be posted from
period 03.

You have an asset with an acquisition cost of 60,000 which was capitalized on 01.01.YYYY-2. The xed asset was as such
straight line depreciated in the legacy system over 2 years and 2 months, and the depreciation was posted. According to
valuation 1, the xed asset should be depreciated over 5 years; according to valuation 2, it should be depreciated over 3 years.

Valuation 1:

Year Start value Value adjustment Ending level

1 60,000 12,000 48,000

2 48,000 12,000 36,000

This is custom documentation. For more information, please visit the SAP Help Portal 142
 8/16/2024

Year Start value Value adjustment Ending level

3 36,000 12,000 24,000

4 24,000 12,000 12,000

5 12,000 12,000 0

Valuation 2:

Year Start value Value adjustment Ending level

1 60,000 20,000 40,000

2 40,000 20,000 20,000

3 20,000 20,000 0

Proceed as follows:

1. You create a master record for the legacy asset with all details.

(App: Manage Legacy Assets

You de ne 01.01.YYYY-2 as the capitalization date.

2. You enter the following transfer values for this legacy asset:

the accumulated acquisition cost

the accumulated ordinary depreciation at the end of the scal year, so at the end of the second year (12.31.YYYY-
1) and

the posted ordinary depreciation of the year, so the depreciation posted during the year in the legacy system for
periods 01 and 02. YYYY

(App: Post Transfer Values – For Legacy Asset)

When entering the ordinary depreciation, specify period 02 as the last depreciation period posted in the legacy
system ( eld Depreciation Period ) because depreciation was posted up to and including this period in the legacy
system.

The system generates the following accounting principle-speci c (or ledger-speci c) documents with the posting date
02.28.YYYY and the asset value date 02.28.YYYY:

Document Accounting Principle Debit/Credit Account Amount

1 Valuation 1 Debit Fixed asset balance 60,000

sheet account(1)

1 Valuation 1 Cr Asset value adjustment 24,000

account(2)

1 Valuation 1 Cr Offsetting account for 36,000

legacy data transfer

1 Valuation 1 Debit Offsetting account for 2,000

(3)
legacy data transfer

1 Valuation 1 Cr Asset value adjustment 2,000

account

This is custom documentation. For more information, please visit the SAP Help Portal 143
 8/16/2024

Document Accounting Principle Debit/Credit Account Amount

2 Valuation 2 Debit Fixed asset balance 60,000

sheet account(1)

2 Valuation 2 Cr Asset value adjustment 40,000

account(2)

2 Valuation 2 Cr Offsetting account for 20,000

legacy data transfer

2 Valuation 2 Debit Offsetting account for 3,333

legacy data transfer(3)

2 Valuation 2 Cr Asset value adjustment 3,333

account

Explanation:

(1) The accumulated APC is posted with transaction type 970.

(2) The accumulated ordinary depreciation is posted with transaction type 970.

(3) As part of the legacy data transfer of General Ledger Accounting, you have to transfer the depreciation expense for the
current scal year that has already been posted in the source system for the expense account (P&L account for Depreciation of
Tangible Assets).

Alternative: Calculate the depreciation in the current year of the transfer in the SAP
system
Alternatively, you can calculate and post the depreciation in the current year before the transfer date - so for periods 01 and 02
- in the SAP system. In this case, you are not allowed to enter any posted ordinary depreciation of the year. Additionally, when
you enter the transfer document, you do not specify the last depreciation period posted in your legacy system ( eld
Depreciation Period).

Example 3: Transfer During the Year with More Transactions in

Year of Transfer
This example is based on the same prerequisites and the same data as example 2. In addition, an acquisition of 15,000 was
posted on the xed asset in the legacy system on 01.01.YYYY.

Enter the business transaction as transfer document: The acquisition cost is posted on the acquisition date, so on 01.01.YYYY.
As this business transaction is a transfer document that was also already posted in the legacy system, the system does not
calculate and post any depreciation.

The system generates the following nancial reporting-speci c (or ledger-speci c) documents with posting date 01.01.YYYY and
asset value date 01.01.YYYY:

Document Accounting Principle Debit/Credit Account Amount

1) Valuation 1 Debit Fixed asset balance 15,000

sheet account(1)

1) Valuation 1 Cr Offsetting account for 15,000

legacy data transfer

This is custom documentation. For more information, please visit the SAP Help Portal 144
 8/16/2024

Document Accounting Principle Debit/Credit Account Amount

2) Valuation 2 Debit Fixed asset balance 15,000

sheet account(1)

2) Valuation 2 Cr Offsetting account for 15,000

legacy data transfer

Explanation:

(1) The acquisition cost is posted with transaction type 100.

 Note
As part of the legacy data transfer of General Ledger Accounting, you have to transfer the depreciation expense for the
current scal year that has already been posted in the source system for the expense account (P&L account Depreciation of
Tangible Assets), including the depreciation expense for the asset acquisition during the year.

Variant for example 3: Legacy data transfer during the year with rst acquisition of
the legacy asset in year of transfer
This variant of example 3 is also based on the same prerequisites and the same data as example 2. The depreciation was
already posted up to the transfer date in the legacy system. On 31.01.YYYY an acquisition was also posted on a newly created
xed asset in the legacy system.

When making the entry manually, make sure you have the following sequence order.

1. You create a master record for the legacy asset with all details and de ne 31.01.YYYY as the capitalization date.

(App: Manage Legacy Assets

2. You enter the acquisition as a transfer document.

The acquisition cost is posted on the acquisition date, so on 31.01.YYYY. As this business transaction is a transfer
document that was also already posted in the legacy system, the system does not calculate and post any depreciation.

3. Only now can you enter the transfer value for the posted ordinary depreciation of the year, so the depreciation posted
during the year in the legacy system for period 02.YYYY You also specify period 02 as the last depreciation period posted
in the legacy system ( eld Depreciation Period) because depreciation was posted up to this period in the legacy system.

(App: Post Transfer Values – For Legacy Asset)

 Note
As part of the legacy data transfer of General Ledger Accounting, you have to transfer the depreciation expense for the
current scal year that has already been posted in the source system for the expense account (P&L account for
Depreciation of Tangible Assets).

Example 4: Transfer at End of Fiscal Year for AUC with Line Item
Management
You want to perform a legacy data transfer at the end of a closed scal year, so on 12.31.YYYY-1. You de ne this date as the
transfer date in the legacy data transfer segment (in Current Settings using the Make Company Code Settings - Asset-
Accounting-Speci c app, tab page Legacy Data Transfer).

This is custom documentation. For more information, please visit the SAP Help Portal 145
 8/16/2024
You have an asset under construction for which you manage line items. You must transfer the line items of the previous years,
so in the year of transfer YYYY-1 and before. A line item with the amount of 20,000 was posted in year YYYY-1 on the asset
under construction.

Proceed as follows:

1. You create a master record for the legacy asset that belongs to the asset class Asset under Construction with Line Item
Management. You enter all details.

(App: Manage Legacy Assets

2. You enter the line items for this legacy asset.

(App: Transfer Open Items of AuC – For Legacy Asset)

You must enter the line items with transaction type 900.

The system generates the following accounting principle-speci c (or ledger-speci c) documents with the posting date and asset
value date 01.01.YYYY:

Document Accounting Principle Debit/Credit Account Amount

1) Valuation 1 Debit Fixed asset balance 20,000

sheet account AuC(1)

1) Valuation 1 Cr Offsetting account for 20,000

legacy data transfer

2) Valuation 2 Debit Fixed asset balance 20,000

sheet account(1)

2) Valuation 2 Cr Offsetting account for 20,000

legacy data transfer

Explanation:

(1) The acquisition cost is posted with transaction type 900.

Additional Information
For more information, see Transfer of Assets under Construction.

Example 5: Transfer During the Year for an AUC with Line Item
Management
You want to perform a legacy data transfer during the year at the end of February on 02.28.YYYY. You de ne this date as the
transfer date in the legacy data transfer segment (in Current Settings using the Make Company Code Settings - Asset-
Accounting-Speci c app, tab page Legacy Data Transfer). The preceding scal year YYYY-1 is closed.

You have an asset under construction for which you manage line items, that is open items. In Asset Accounting you transfer the
line Items that were posted in the previous years (so in the year YYYY-1 and before then). You also need to transfer the line
items that were posted in the current scal year before the transfer date 02/28/YYYY; on 02/11/YYYY, a line item of 20,000
was posted to the asset under construction.

Proceed as follows:

This is custom documentation. For more information, please visit the SAP Help Portal 146
 8/16/2024
1. You create a master record for the legacy asset that belongs to the asset class Asset under Construction with Line Item
Management. You enter all details.

(App: Manage Legacy Assets

2. You enter the line items for this legacy asset.

(App: Transfer Open Items of AuC – For Legacy Asset)

You must enter the line items with transaction type 900.

The system generates the following accounting principle-speci c (or ledger-speci c) journal entries with the posting date
02/28/YYYY (transfer date):

Journal Entry Accounting Principle Debit/Credit Account Amount

1) Valuation 1 Debit Fixed asset balance 20,000

sheet account AUC(1)

1) Valuation 1 Cr Offsetting account for 20,000

legacy data transfer

2) Valuation 2 Debit Fixed asset balance 20,000

sheet account(1)

2) Valuation 2 Cr Offsetting account for 20,000

legacy data transfer

Explanation:

(1) The acquisition cost is posted with transaction type 900.

Additional Information
For more information, see Transfer of Assets under Construction.

Transfer Methods
The manual legacy data transfer has some similarities with the automatic legacy data transfer using the SAP S/4HANA
migration cockpit, but also some differences.

Common Functions
Both transfer methods use the following functions:

Depreciation period (for mid-year legacy data transfer and transfer of depreciation posted in the legacy system)

If you are performing a legacy data transfer during the year, have already posted depreciation in the legacy system in the year
of the transfer and you want to transfer this depreciation with the legacy data transfer, you must specify the last depreciation
period posted (in the legacy system). The system requires this information to determine the rst period for the depreciation to
be posted in the SAP system.

Transfer of values in parallel currencies

You can decide whether you want to transfer your historical parallel currency values or if you want the system to automatically
translate the values instead.

This is custom documentation. For more information, please visit the SAP Help Portal 147
 8/16/2024
In the standard system, the system translates the values you transferred; this applies to both the manual transfer and the
automatic transfer of values. If you do not want automatic currency translation and want to transfer historical values instead,
you can control this using a corresponding indicator.

The following overview shows the interaction between the indicator for the currency translation and the transfer of parallel
currency values (that is, values in group currency) for the manual transfer on the one hand and the automatic transfer (using
the SAP S/4HANA migration cockpit) on the other hand:

Automatic Currency Translation of Values Transfer of historical parallel currency

values, that is, no automatic currency
(Standard System Behavior)
translation of values

Manual Transfer
The indicator for automatic currency You deselect the indicator for
translation is set (default setting). automatic currency translation.

You do not specify any historical You specify your historical parallel
parallel currency values. currency values explicitly.

This means that in addition to the

values in company code currency,
you also specify the values in group
currency.

Automatic transfer (with the SAP S/4HANA

The indicator for suppressing You set the indicator for
migration cockpit)
automatic currency translation is suppressing automatic currency
not set (default setting). translation.

You do not specify any historical You specify your historical parallel
parallel currency values. currency values explicitly.

This means that in addition to the

values in company code currency,
you also specify the values in group
currency.

 Note

In the posting apps of Asset Accounting, values are posted automatically to the general ledger in the group currency,
for example, when posting depreciation.

Therefore, make sure that you use the legacy data transfer to also make the group currency values available in the
SAP system: either by automatic translation or by transferring historical values.

Only in justi ed exceptional cases should you transfer historical group currency values of zero, for example, if the
values already existed as such in the legacy system. This is because if you transfer group currency values of zero (for
example, by not setting the translation indicator for the manual transfer and yet also do not specify historical values),
this would usually lead to errors when calculating and posting depreciation.

After the legacy data transfer, you reconcile the data transferred to the SAP system against the data in the legacy
system. Make sure that you perform the reconciliation not only in the local currency, but also in all parallel currencies.

Speci c Functions
The following sections explain the special features of the manual data transfer and of the automatic transfer using the SAP
S/4HANA migration cockpit.

This is custom documentation. For more information, please visit the SAP Help Portal 148
 8/16/2024

Manual Legacy Data Transfer

Use
If you have only a handful of legacy data to be transferred to the SAP system, transfer your legacy data manually using the apps
in Asset Accounting.

Steps with the Manual Transfer of Legacy Data

The manual legacy data transfer includes, as already described in the previous sections - the following steps:

1. For the legacy data transfer segment previously created, set the legacy data transfer status to In Execution or to In
Execution (Other Postings Allowed).

2. Create the asset master records for the legacy data transfer.

(App: Manage Legacy Assets)

3. Post the transfer values.

(App: Post Transfer Values – For Legacy Asset)

A journal entry is posted for the xed asset and the general ledger accounts are updated. For each asset a transfer
document is created that posts the transfer values, for example, on the APC and accumulated depreciation account and
against the offsetting account for the legacy data transfer.

4. With a data transfer during the year, you also transfer asset-related business transactions that occurred before the
transfer date in the current scal year. To do this, you use an app that is suitable for the transaction.

If a posting date in the current scal year is entered that is before the transfer date, the system recognizes this business
transaction as a transfer document; no depreciation is calculated, the document is posted against the offsetting account
for the legacy data transfer.

5. For assets under construction that are line item-managed, transfer the open items.

(App: Transfer Open Items of AuC – For Legacy Asset)

Master Data
To create the asset master records for the legacy data transfer, use the Manage Legacy Assets app.

You create master data for legacy assets exactly the same way as you create regular asset master data. However, take into
account the following special features of legacy assets:

The capitalization date is always a required entry. Using the capitalization date, the system determines the depreciation
start date and the expired useful life, based on the period control in the depreciation key. Check the expired useful life
that the system calculated.

The planned useful life is a required entry when a depreciation key for automatic depreciation calculation has been
entered.

You can also account for increased wear and tear on an asset in the past as the result of multiple shift use. You do this by
manually correcting the expired useful life that was automatically calculated by the system.

Time-dependent data (such as the assignment to a cost center) can only be transferred with the values current on the
transfer date. To must create new time intervals with modi ed data using the app Manage Fixed Assets.

This is custom documentation. For more information, please visit the SAP Help Portal 149
 8/16/2024
In addition to creating master records for legacy assets, the Manage Legacy Assets app provides you with the following
functions:

You can display the master data.

You can modify the master data.

You can create subnumbers for the asset master record.

Post Asset Values (Transfer Values)

Cumulated values and depreciation from the transfer year

To transfer the cumulated values and depreciation from the transfer year for a legacy asset, use the app Post Transfer Values –
For Legacy Asset. Note the following speci c features:

Depreciation areas:

You must specify the asset values for all active depreciation areas.

Transfer of parallel currency values:

If you want to transfer values in additional currencies, note the following:

Automatic Currency Translation of Transfer of historical parallel currency

Values values, that is, no automatic currency
translation of values
(Standard System Behavior)

Manual Transfer
The indicator for automatic You deselect the indicator for
currency translation is set automatic currency translation.
(default setting).
You specify your historical
You do not specify any historical parallel currency values
parallel currency values. explicitly.

See also the section on transferring values in parallel currencies under Transfer Methods.

Posted depreciation (for a transfer during the year)

If you transfer legacy data during the scal year, you can enter the depreciation that was already posted in the legacy
system in the current scal year.

Specify the last depreciation period posted (in the legacy system) ( eld Depreciation Period) when entering the
depreciation posted in the transfer year. The system requires this information to determine the rst period for the
depreciation that should be posted in the SAP system.

Posted revaluations:

The values you enter are also checked against the positive/negative sign rules of the depreciation area
(positive/negative net book value, positive/negative ordinary depreciation, and so on).

Transactions in the year of the transfer (for a transfer during the scal year)

You must transfer the transactions from the current scal year up to the date of the transfer for legacy data transfer during the
scal year. To do this, use an app that is suitable for the transaction.

Make the following entries when transferring transactions:

This is custom documentation. For more information, please visit the SAP Help Portal 150
 8/16/2024
Asset value date

Note that the asset value date has to be in the current scal year, and it must lie before the transfer date.

Transaction type

Posting Amount

Assets under Construction with Line Item Management

To ensure that the line-item-managed assets under construction (AuC) can be settled, you cannot enter values as accumulated
values using the app Post Transfer Values – For Legacy Asset.

Instead you have to enter the values individually using the app Transfer Open Items of AuC – For Legacy Asset. For the transfer,
you have to use the speci c transaction types (900 -Takeover open items APC (AuC)).

If you have the special case of proportional depreciation on the AuC, then enter this as proportional depreciation from the
previous years using the transaction.

Change Transfer Values Subsequently

If wrong transfer values were posted, you must reverse the journal entry and then enter the transfer values again.

You can only change transfer values by reversing the posted transfer document and making a new posting. To be able to reverse
a transfer document, subsequent transactions are not allowed to exist on the xed asset.

If follow-on transactions were already posted on the xed asset, we recommend you proceed as follows:

1. Reverse all transactions in reverse chronological order.

2. Reverse the transfer transaction.

3. Post the new transfer values.

4. Enter the follow-on transactions again individually.

However, you can delete legacy data that you have transferred to the quality management system (Q system) for test
purposes. For more about this, see Reset Incorrectly Transferred Legacy Data.

Automatic Transfer

Use
If you have to transfer a lot of legacy data to the SAP system, perform the transfer automatically using the SAP S/4HANA
migration cockpit.

Key Features
In the SAP S/4HANA migration cockpit, you use the migration objects Fixed Asset - Master Data and Fixed Asset - Postings and
the relevant XML template.

As with the manual data transfer, you can also use the SAP S/4HANA migration cockpit to transfer the following data: the asset
master records, the asset values or the cumulated values from the previous year, and, in the case of a legacy data transfer
during the scal year, the transactions from the start of the scal year up to the date of the transfer.

This is custom documentation. For more information, please visit the SAP Help Portal 151
 8/16/2024
Constraints:

You cannot use the SAP S/4HANA migration cockpit to transfer the following data:

Assets under construction that are linked to investment measures

Investment support

External number assignment is not supported.

The following sections go into the details of the automatic transfer.

Uploading legacy asset subnumbers

It is possible to upload asset subnumbers using the SAP S/4HANA migration cockpit. It must take place within the same
migration project as the main numbers, but with a separate le.

For more information, see the documentation for the migration object, under Fixed asset - Master data.

Transferring mid-year transactions

You can either transfer transactions during the scal year as part of the legacy data transfer, or you can post them manually
afterwards. The features of transactions during the year mentioned in section Manual Legacy Data Transfer also apply to
automatic legacy data transfers.

Parallel currency values

As with the manual legacy data transfer, you can also decide for the automatic legacy data transfer whether you want to
transfer your historical parallel currency values or whether you want to translate the values automatically instead.

During the automatic transfer using the SAP S/4HANA migration cockpit, the system translates the values you transferred by
default. (The indicator for suppressing automatic currency translation is then not set.) With the automatic translation, the
exchange rate is calculated as follows:

For cumulated year-start values: with the exchange rate on the capitalization date of the asset

For transactions during the year: with the exchange rate on the date of the legacy data transfer

For open items on a line item-managed asset under construction (transaction type 900): with the exchange rate on the
date of the legacy data transfer (as for a mid-year transaction)

However, if you want to transfer historical parallel currency values, then set the indicator for suppressing the automatic
currency translation and specify the parallel currency values for the legacy data transfer. The system responds to this by not
translating anything.

Automatic Currency Translation of Values Transfer of historical parallel currency

values, that is, no automatic currency
(Standard System Behavior)
translation of values

Automatic transfer (with the SAP S/4HANA

The indicator for suppressing You set the indicator for
migration cockpit)
automatic currency translation is suppressing automatic currency
not set (default setting). translation.

You do not specify any historical You specify your historical parallel
parallel currency values. currency values explicitly.

This is custom documentation. For more information, please visit the SAP Help Portal 152
 8/16/2024

Assets under construction (AuC) with line item management

To ensure that the line item-managed assets under construction can be settled, you are not allowed to enter the transfer values
as cumulated values in the XML template, you must provide the line items instead (in the XML template on the Transaction
Items) tab. You must use the speci c transaction type 900 for the transfer.

If you have the special case of proportional depreciation on the AuC, then enter this as proportional depreciation from the
previous years using the transaction.

See Also
For more information, see:

The general documentation on the migration cockpit under Migrate Your Data - Migration Cockpit

The test script for scope item BH5 under https://rapid.sap.com/bp/#/scopeitems/BH5

The documentation for the migration objects:

Fixed asset - Master data

Fixed asset - Postings

The introductory text in the respective XML template

The eld help for the elds in the respective XML template

Transfer Legacy Assets with the SAP S/4HANA Migration

Cockpit

Overview: Overall Process

To transfer legacy data with the SAP S/4HANA Migration Cockpit, proceed as follows.

(I) You carry out a pre-test for the legacy data transfer.

(II) You transfer the asset master data by using the migration object Assets - Master Data.

You must migrate the master data before you migrate the postings.

(III) You transfer the asset values by using the migration object Assets - Postings.

(IV) Reconcile the data in the SAP system with your legacy system.

(I) Pre-Test
We recommend that you rst carry out a pre-test and copy some assets in to the SAP system manually when doing so.

For more information, see the documentation for migration object Fixed asset - Master data in the “Pre-Test” section.

(II)/(III) Procedure for Each Migration Object

1. To call the SAP S/4HANA Migration Cockpit, call the app Migrate Your Data - Migration Cockpit.

2. Create a migration project.

This is custom documentation. For more information, please visit the SAP Help Portal 153
 8/16/2024
Select the migration object (Assets - Master Data or Assets - Postings).

The system generates a corresponding template (XML le), which you later ll with your legacy data.

3. Download the XML template by choosing the action Download Template.

4. Read the introductory text in the XML template.

Also refer to the documentation for the migration object, which you can nd for example in the migration object details
under Documentation.

5. Remove the write protection for all worksheets in the XML template, and save the le locally.

6. Fill the XML template with the legacy data from your legacy system.

Make sure that the eld formats do not change.

Use the function Insert Values.

If you want to transfer legacy data during the year, including depreciation posted in the current year, then enter the
depreciation period posted last (in the legacy system) in the worksheet Posted Values for each asset.

7. Upload the le by choosing the Upload File action.

If there are no errors in the uploaded data, it is automatically written to the staging tables.

8. Choose Mapping Tasks to start mapping.

To enable the system to convert the data in the same way as mapping (that is, to the assignments), maintain, con rm
and save the mapping.

9. Simulate the import of legacy data to the SAP system by choosing Simulation.

The system validates the data and issues an error list if applicable.

10. If errors are displayed, correct them:

Do missing mapping. (See the corresponding step above).

Correct the data in the XML template. (See the corresponding step above).

Delete the affected instances from the staging area, delete the XML template, and upload the corrected version.

11. Simulate the import of the legacy data to the SAP system again.

12. Execute the import: Start transferring the data to the SAP system by clicking on the Migrate Action.

In doing so, the system loads all the data that exists in the staging tables into the SAP system.

13. If errors occur during the import, the system displays a corresponding list.

You can then use the Create Correction File function to create and download a delta le with the incorrect data records
that were not transferred.

(IV) Reconciliation with the Legacy System

After the legacy data transfer, you reconcile the data transferred to the SAP system against the data in the legacy system. For
more information, see Transfer at End of Fiscal Year in the respective process step, for example.

Reset Incorrectly Transferred Legacy Data

This is custom documentation. For more information, please visit the SAP Help Portal 154
 8/16/2024

Use
If you have transferred legacy data incorrectly, under certain circumstances, you can reset it .

The following different cases are possible:

You only want to manually correct individual values.

You can read how to do this under Manual Legacy Data Transfer in section "Change Transfer Values Subsequently".

You want to completely delete transferred legacy data in the quality management system (Q system).

For more information, see the section below.

Reset All Fixed Asset Data in the Q System

If you have transferred legacy data with errors to the Q system, either manually or using the SAP S/4HANA migration cockpit,
you can completely delete this incorrect data.

To do so, use the Reset Transaction Data job template from the app Schedule Accounting Data Corrections.

You use this job template to delete master data and transaction data from Asset Accounting, along with other accounting data.

 Note
You can only use the job template in the quality management system (Q system), and not in the production system (P
system).

Additional Information

For more information, see the application help (product assistance) for General Ledger Accounting under Reset Transaction
Data.

Legacy Data Transfer in Asset Accounting: FAQ

How do I start a migration project for the legacy data transfer in Asset Accounting?
Proceed as follows:

1. You check the prerequisites.

In the app Make Company Code Settings - Asset Accounting-Speci c (F7312), the company code status is not
deactivated. And the company code must not be blocked. Asset Accounting is con gured consistently and completely.

For information about the open and closed scal years, see the answer to the question "Which date should I choose as
the transfer date?” below.

2. You use the app Make Company Code Settings - Asset Accounting-Speci c (F7312) to create a legacy data transfer
segment and specify the transfer date in it.

If a highest scal year has not yet been maintained for the company code, the highest scal year is determined
automatically when the legacy data transfer segment is created.

You may be prompted to perform a balance carryforward.

This is custom documentation. For more information, please visit the SAP Help Portal 155
 8/16/2024
Set the legacy data transfer status for the legacy data transfer segment to Ongoing or to Ongoing (Other Postings
Allowed).

3. You perform the legacy data transfer as a test in the Q system.

Background information: You can reverse the legacy data transfer by reversing the transfer postings. However, if you
have already used the SAP S/4HANA migration cockpit to transfer a large amount of data, manual reversal can be very
tedious.

In the Q system (and only there), you can not only reverse the asset master data and postings, but alternatively you can
also reset (that is, delete) the asset master data and postings.

Recommendation: To test what the postings look like in the system after the transfer, you should proceed as follows:

a. In the Q system, you rst perform a test of a manual legacy data transfer for some assets using the following
apps:

For transferring master data: Manage Legacy Assets (F7280)

To transfer the postings: Post Transfer Values – For Legacy Asset (ABLDT) and,

if necessary, for the transfer of mid-year transactions: Post Miscellaneous Transactions) (ABSOL)

b. Then (also in the Q system) test the legacy data transfer for all assets using the SAP S/4HANA migration
cockpit.

4. If the test legacy data transfer has been carried out as expected, start the transfer in the production system. You can
transfer the asset data automatically using the SAP S/4HANA migration cockpit; you do this separately according to
master data and postings with the respective XML template, but in the same project.

Topic Further Information

Preparation of Legacy Data Transfer Preparations: Create Legacy Data Transfer Segment with
Parameters

Manual and Automatic Legacy Data Transfer Transfer Methods

Reset Legacy Data in the Q System Reset Incorrectly Transferred Legacy Data

Which date should I choose as the transfer date?

A legacy data transfer can take place at different times, either at the end of a scal year or during the year:

Transfer at the end of the scal year: The transfer date can be the end of the last closed scal year. You transfer the
cumulative values as they are at the end of the scal year.

Transfer during the scal year: The transfer date can be a date in the scal year directly following the last closed scal
year.

 Example
Your scal year is the same as the calendar year; you use scal year variant K4.

The current scal year YYYY is open, the scal year YYYY-1 is closed. You could choose 31.12.YYYY-1 as the transfer date or –
for a legacy data transfer during the year – for example, 28.02.YYYY.

Time of Transfer Transfer Date Last Closed Fiscal Year Open Fiscal Year

At the end of the scal year 31.12.YYYY-1 JJJJ-1 YYYY

This is custom documentation. For more information, please visit the SAP Help Portal 156
 8/16/2024

Time of Transfer Transfer Date Last Closed Fiscal Year Open Fiscal Year

During the scal year 28.02.YYYY JJJJ-1 YYYY

To be able to migrate the data, you need to create a legacy data transfer segment in the app Make Company Code Settings -
Asset Accounting-Speci c (F7312). The system derives the current scal year and the scal year last closed from the legacy
data transfer segment.

Topic Further Information

Create Legacy Data Transfer Segment with Transfer Date Preparations: Create Legacy Data Transfer Segment with
Parameters

Time of Transfer Time of Transfer

I want to perform a legacy data transfer using the SAP S/4HANA migration
cockpit. – How can I check in advance whether the settings for the legacy data
transfer are correct, the legacy assets are transferred, and the transfer documents
are posted?
Recommendation: Before you transfer legacy data for Asset Accounting in a corresponding project using the SAP S/4HANA
migration cockpit, you should carry out a manual legacy data transfer in the Q system as a test. Manually create legacy asset
master data for some assets and try to post the cumulative values of the transactions to these legacy assets (and, in the case
of a mid-year transfer, also transactions from the transfer year).

If problems occur, you should correct them before you transfer the complete asset data as a test using the SAP S/4HANA
migration cockpit.

In the Q system, you can also reset the data in the company code if required.

Topic Further Information

Preparation of Legacy Data Transfer, Including Test See the answer to the question “How do I start a migration project
for legacy data transfer in Asset Accounting?“ higher up.

Manual Legacy Data Transfer Manual Legacy Data Transfer

Reset Company Code Data in the Q System Reset Incorrectly Transferred Legacy Data

I want to perform a legacy data transfer using the SAP S/4HANA migration
cockpit. – How can I improve performance?
If you have to transfer lots of xed assets (mass data), to improve performance you can suppress the calculation of planned
values for the depreciation. To do so, you set the indicator Suppress Depreciation Calculation in the legacy data transfer
segment in the app Make Company Code Settings - Asset Accounting Speci c.

Immediately after the legacy data transfer has been completed, you must recalculate the depreciation using the job template
Recalculate Depreciation in the Schedule Asset Accounting Jobs app.

Which worksheets do I need to ll in the XML template for the asset postings?
In the SAP S/4HANA migration cockpit, there is an XML template for asset master data and one for asset postings.

This is custom documentation. For more information, please visit the SAP Help Portal 157
 8/16/2024
In the XML template for asset postings, there are several worksheets. Depending on whether you perform a transfer at the end
of the year or during the year, the following worksheets are relevant for you:

Posting Key Cumulative Posted Values Transaction Headers Transaction Transaction

Values Items Proportional
Values

For a transfer at Mandatory Mandatory -- Mandatory only in the -- --

the end of the following cases:
year:
When
transferring
quantity data
(speci cation
of the
opening
quantity)

When you
transfer open
items for an
asset under
construction

For transfers Mandatory Mandatory As Required As Required As Required As Required

during the
scal year:

Topic Further Information

Process for the Automatic Legacy Data Transfer with the SAP Transfer Legacy Assets with the SAP S/4HANA Migration Cockpit
S/4HANA Migration Cockpit

Migration object Fixed asset - Postings Fixed asset - Postings

How do I transfer historical values in parallel currencies (that is, currencies that
exist in the ledger in addition to the company code currency)?
If, in addition to the company code currencies, you have one or more other currencies in the ledger (for example, the group
currency), you can either specify your historical parallel currency values from the legacy system explicitly during the legacy data
transfer or have the SAP system determine the parallel currency values automatically.

To be able to transfer historical parallel currency values, the following prerequisites must be met:

Transfer of Historical Parallel Currency Values from the Legacy

System

For manual transfer:

You deselect the indicator for automatic currency
translation.

You specify your historical parallel currency values

explicitly.

This is custom documentation. For more information, please visit the SAP Help Portal 158
 8/16/2024

Transfer of Historical Parallel Currency Values from the Legacy

System

For automatic transfer (with the SAP S/4HANA migration cockpit):

In the XML template for postings, set the indicator for
suppressing automatic currency translation on the Posting
Key worksheet.

You specify your historical parallel currency values

explicitly.

Topic Further Information

Transfer of values in parallel currencies Transfer Methods

Exchange rates and their maintenance Product Assistance for General Ledger Accounting under Exchange
Rates

I want the system to determine the values in a parallel currency (for example, the
group currency). – Which exchange rate is used to translate the values?
For the SAP system to determine the parallel currency values automatically, the following prerequisites must be met:

Automatic Determination of Parallel Currency Values by the SAP

system

For manual transfer:

The indicator for automatic currency translation is set
(default setting).

You do not specify any historical parallel currency values.

For automatic transfer (with the SAP S/4HANA migration cockpit):

In the XML template for journal entries, on the Posting Key
worksheet, make sure that the indicator for suppressing
automatic currency translation is not set (default setting).

You do not specify any historical parallel currency values.

You must also have maintained the required exchange rates.

Depending on the value type, the system uses the exchange rate at a speci c time:

- For cumulated values at the start of the year: With the exchange rate on the capitalization date of the xed asset.

For transactions during the year: With the exchange rate on the date of the legacy data transfer.

- For open items on a line item-managed xed asset under construction (transaction type 900): With the exchange rate
on the date of the legacy data transfer (as with a transaction during the year).

Topic Further Information

Transfer of values in parallel currencies Transfer Methods

Exchange rates and their maintenance Product Assistance for General Ledger Accounting under Exchange
Rates

This is custom documentation. For more information, please visit the SAP Help Portal 159
 8/16/2024

During the reconciliation of my transfer values with the legacy system, I noticed
that values with the amount 0 were transferred in the parallel currency. – How can I
correct the values in the parallel currency?
Parallel currency values with amount 0 can be caused by the following: During the transfer, you speci ed that you do not want
the values in the parallel currency to be translated automatically, but that you want to enter the historical values. However, you
did not enter any values. In such a case, a value of zero is posted as the transfer value.

This can lead to errors during the calculation and posting of depreciation in the future.

Proceed as follows: Reverse the transfer document and post it again – this time with correct parallel currency values.

Topic Further Information

Transfer of values in parallel currencies Transfer Methods

What do I have to consider if I want to transfer quantity data?

If you also want to transfer quantities for your cumulated values during the legacy data transfer, note the following:

Automatic transfer with the SAP-S/4HANA migration cockpit:

1. In the XML template for master data, you must specify the base unit of measure.

2. The following applies to the XML template for journal entries: Postings with quantities are possible in all ledgers.
When you make a quantity posting, it is posted to all ledgers by default. In each ledger, quantity postings are
updated in the balance sheet-relevant depreciation area. In the same way as for posting currency amounts, you
can post different quantities for each ledger:

Accordingly, the quantity for each ledger must be speci ed in the XML template in the Transaction Headers
sheet.

Manual Transfer:

1. You transfer the master data using the Manage Legacy Assets app. You specify the base unit of measure.

2. You transfer the postings (cumulated values) using the Post Transfer Values app.

3. You then transfer the quantities separately using the app Post Asset Acquisition – And Quantity Adjustment. In
the app, choose Other Posting Transaction Post Acquisition Post Quantity Adjustment . Journal entry date,
posting date, and asset value date are the same as the transfer date. The asset value date is only the transfer
date + 1 day for a transfer during the year.

Topic Further Information

Transfer using the SAP S/4HANA migration cockpit, migration Fixed asset - Postings
object Fixed asset - Postings

What do I need to consider for low-value assets?

SAP delivers maximum amounts for low-value assets (LVA) for most countries. You can use these LVA maximum amounts as
they are, or you can specify your own LVA maximum amounts in the Specify Amounts con guration activity.

The following amount types are available for each accounting principle:

A highest amount for low-value assets for acquisition postings

This is custom documentation. For more information, please visit the SAP Help Portal 160
 8/16/2024
A highest amount for low-value assets for purchase orders

In con guration activity Make Valuation View-Dependent Settings for Asset Class, you can con gure that the system should
perform a maximum amount check for the asset class of low-value assets.

There is a class for low-value assets among the standard asset classes.

Depending on whether you use individual or collective management, note the following:

Individual check (for individual management): When an acquisition posting is transferred in the legacy data transfer, the
total acquisition cost of the asset is compared with the LVA maximum amount.

Quantity check (for collective management): During the posting/transfer of the acquisition during the legacy data
transfer, the total acquisition cost of the asset, divided by the total quantity, is checked against the LVA maximum
amount.

The total quantity consists of the opening balance of the quantity (on the Transaction Headers worksheet, the
Assignment Number eld must be lled with the character string STARTQUANTITY ) and the total of the quantities of
any acquisition/retirement postings.

Topic Further Information

Transfer using the SAP S/4HANA migration cockpit, migration Fixed asset - Postings
object Fixed asset - Postings

What do I need to consider when creating, correcting, and deleting a legacy data
transfer segment?
You need to be aware of the following:

The transfer date for Asset Accounting must not be before the migration date (transfer date) for General Ledger
Accounting (FI-GL).

A new legacy data transfer segment can only be created if no open segment exists in the company code. This means
that: All earlier segments must have the status Completed.

The transfer date of a new legacy data transfer segment must always be after the transfer data of the segments that
have already been completed.

The transfer can only take place if the legacy data transfer segment has the status Ongoing or Ongoing (Other Postings
Allowed).

If you need to make corrections or make additional postings, you can reopen a legacy data transfer segment that has
already been closed. If you need to reopen a scal year that has already been closed for this, the usual conditions for
reopening closed scal years then apply, and the system performs the usual consistency checks for the posting in the
reopened scal year.

An existing legacy data transfer segment can only be deleted if no legacy assets exist in the company code and the
segment has the highest sequence number.

If you want to open a subsequent scal year, you must have performed year-end closing activities and completed the
legacy data transfer segment.

The scal years before the transfer must be closed.

A transfer date for a legacy data transfer during the year must be in an open scal year.

In the case of a legacy data transfer at the end of the scal year, the scal year following the transfer date must be open.

This is custom documentation. For more information, please visit the SAP Help Portal 161
 8/16/2024
If you entered an incorrect transfer date by mistake, you can proceed as follows:

As long as there are no legacy assets for a new legacy data transfer segment in the system and the legacy data
transfer segment has the status In Preparation, you can still delete the legacy data transfer segment.

Alternatively, if the same prerequisites exist, you can change the transfer date; you may have to open the
corresponding scal year rst.

If you want to change the legacy data transfer segment in the production system, but legacy assets have already
been transferred, you must rst reverse the transferred postings and execute scrapping. Then set the status of
the legacy data transfer segment to Completed.

Only then can you create a new legacy data transfer segment. The restriction applies that the new transfer date
must be after the old transfer date.

Topic Further Information

Preparation for the Legacy Data Transfer, Legacy Data Transfer Preparations: Create Legacy Data Transfer Segment with
Segment, Transfer Date Parameters

I have forgotten postings for a legacy data transfer that has already been
completed. – How can I add these subsequently?
Proceed as follows:

1. If another legacy data transfer segment is open, you must close it.

2. If necessary, reopen scal years that have already been closed.

3. Reopen the completed segment.

4. Make the missing postings.

5. Close the scal years opened under no. 2.

 Example
You have the following initial situation:

Open scal years: YYYY and YYYY+1

Existing legacy data transfer segments:

Segment 3: Transfer date 31.5.YYYY; not yet completed

Segment 2: Transfer date 31.12.YYYY-1; Status: Completed

Segment 1: Transfer date 31.3.YYYY-2; Status: Completed

You want to transfer additional legacy data for segment 1 on 31/03/YYYY-2.

Proceed as follows:

1. You close segment 3.

2. You reopen the scal years YYYY-1 and YYYY-2.

3. You reopen segment 1.

4. You transfer the missing postings.

This is custom documentation. For more information, please visit the SAP Help Portal 162
 8/16/2024
5. You perform the year-end closing activities for YYYY-2 and YYYY-1 and close the scal years YYYY-2 and YYYY-1.

Topic Further Information

Reopening a Completed Legacy Data Transfer Segment Preparations: Create Legacy Data Transfer Segment with
Parameters

I want to perform a legacy data transfer during the year. – How do I transfer my
depreciation from the current scal year?
You have the following options:

You either transfer the posted depreciation of the current scal year from the legacy system.

Alternatively, you can perform the legacy data transfer without the posted depreciation of the current scal year, then
after the legacy data transfer, you get the depreciation in the SAP system by using the depreciation run.

For more detailed information, see the following documentation:

Topic Further Information

Transfer During the Fiscal Year, Transfer of Depreciation in Transfer Transfer During the Fiscal Year
Year

For my non-leading ledger in the company code, I use an alternative scal year
variant. – What do I need to consider for the legacy data transfer?
If the transfer date in one ledger corresponds to the end of the scal year and not in the other, you have to perform a legacy
data transfer at the end of the scal year for one ledger and a legacy data transfer during the year for the other ledger.

 Example
A company works with an alternative scal year variant:

Legder 0L with scal year variant K4

Ledger 2L with scal year variant V3 (in other words, scal year from 1.4. to 31.3.)

From an organizational point of view, the following transfer dates are possible for your company:

Possible Transfer Date Ledger 0L with K4 Ledger 2L with V3

a) 31.12.YYYY Transfer at End of Fiscal Year Transfer During the Fiscal Year

b) 31.3.YYYY Transfer During the Fiscal Year Transfer at End of Fiscal Year

c) 1.5.YYYY Transfer During the Fiscal Year Transfer During the Fiscal Year

In the Current Fiscal Year YYYY In the Current Fiscal Year YYYY

d) 1.2.YYYY Transfer During the Fiscal Year Transfer During the Fiscal Year

In the Current Fiscal Year YYYY In the Previous Year YYYY-1

Explanation:

This is custom documentation. For more information, please visit the SAP Help Portal 163
 8/16/2024
a) + b) In the ledger with a transfer at the end of the scal year, only the cumulated values are transferred; for the ledger
with a transfer during the year, you must also transfer the transactions posted in YYYY up to the transfer date.

d) You must also take into account the different scal years during the transfer.

Topic Further Information

Legacy Data Transfer During the Year Transfer During the Fiscal Year

Alternative scal year variant for transactions in Asset Accounting, Alternative Fiscal Year Variant and Its Effects on Transactions
also for the legacy data transfer

What do I need to consider when transferring independent assets under

construction?
You can use the SAP S/4HANA migration cockpit to transfer independent assets under construction.

A manual transfer using the app Transfer Open Items of AuC – For Legacy Asset is also possible.

Topic Further Information

Legacy data transfer for assets under construction, also for Transferring Assets under Construction
independent assets under construction

The reconciliation of the productive SAP system with the legacy system has shown
that xed assets or values were transferred incorrectly. – What should I do in such
a case?
In the production system, it is not possible to simply delete documents or master data. Instead, you have to reverse postings
and transfer them again.

First check whether only individual assets are incorrect or whether a large number or all assets are incorrect:

Incorrect values were transferred for individual legacy assets:

Reverse the incorrect transfer documents from the legacy data transfer and post the legacy data transfer documents
again.

For individual legacy assets, the asset master data was created incorrectly:

Reverse the transfer documents and block the individual asset master data so that acquisitions can no longer be posted
to them.

Then recreate the asset master data as legacy assets and post the correct transfer documents again.

For a large number or all legacy assets, incorrect values have been transferred, or the master data for the legacy assets
was created incorrectly:

Again, proceed as described in the previous two points.

You can reverse a journal entry in the Manage Fixed Assets app directly in the value display for an asset.

You can repost the document manually using the app Post Transfer Values – For Legacy Asset.

Topic Further Information

This is custom documentation. For more information, please visit the SAP Help Portal 164
 8/16/2024

Topic Further Information

Reverse Journal Entries Reverse Journal Entries

Manual Transfer of Fixed Asset Master Data and Fixed Asset Manual Legacy Data Transfer
Postings

Reset Fixed Asset Data in the Q System Reset Incorrectly Transferred Legacy Data

I have reversed transfer documents for an incorrect legacy asset. This xed asset
should no longer be used. – How can I prevent someone from posting to the asset?
Proceed as follows:

1. Lock the asset against acquisition postings.

2. Set a deactivation date manually for this legacy asset. You set the deactivation date for each ledger individually in the
Manage Legacy Assets app. When the deactivation date is reached, the xed asset can be archived.

3. Archive the xed asset.

Topic Further Information

Block Acquisition Postings on an Asset Manage Fixed Assets

Archive Fixed Assets Archiving Assets using FAA_ASSET

In the account determination for the asset classes, an incorrect G/L account was
assigned by mistake. – Can I assign a different G/L account in the corresponding
con guration activity “Assign G/L Accounts” (ID 102622)?
As long as you have not yet posted any documents to the xed assets using account determination or all postings have been
reversed, you can assign a different G/L account. This applies to the P system as well as to the Q system.

Please note the following exceptions:

Depreciation postings cannot be reversed. This means that: As soon as a depreciation account has been posted to, it is
not possible to change the account determination.

For resetting postings from other application components, for example, Purchasing, the following applies: An inverse
posting is posted, but no true reversal. Therefore, you cannot change the relevant account determination.

If you must use a different G/L account, you have the following options:

Option 1: As long as you have not yet made any postings for an asset that is assigned using account determination
(neither in the Q system nor in the P system), you can still change the assignment to the G/L account.

Option 2: If the postings are only in your Q system and there are no corresponding postings on the G/L account in the P
system yet, you can reset the transaction data from your company code and then change the assignment to the G/L
account.

Option 3: If you have not yet posted any depreciation or transactions from other application components, you can
reverse all documents on your xed assets that were originally posted to the G/L account.

Option 4: If you have postings (including depreciation postings and/or postings from other application components) in
the Q and P system, create a new asset class to which an account determination with the correct G/L account is
assigned. Then transfer post all xed assets that have already been created to the new assets with the new asset class.
This is custom documentation. For more information, please visit the SAP Help Portal 165
 8/16/2024

Topic Further Information

For option 2: Reset Company Code with Asset Data in the Q System Reset Incorrectly Transferred Legacy Data

For option 3: Change Transfer Values Subsequently by Reversal and Manual Legacy Data Transfer
New Posting

Assign G/L Accounts Documentation for the con guration activity Assign G/L Accounts
(ID102622)

What is the meaning of the individual statuses of the legacy data transfer segment
and which status changes are possible?
For information about the statuses of a legacy data transfer segment (In Preparation, Ongoing, Ongoing (Other Postings
Allowed), Completed), see the documentation below. It also tells you how to set the status.

The following status changes are allowed: In Preparation -> Ongoing or Ongoing (Other Postings Allowed) -> Completed. If the
status changes are not permitted, the system issues an error message (for example: FAA_CMP043).

Topic Further Information

Legacy data transfer statuses and their meaning Preparations: Create Legacy Data Transfer Segment with
Parameters

CDS Views for Asset Accounting

The following table shows the released CDS views available in Asset Accounting. Using released CDS views as a basis, you can
create your own query views. Released CDS query views can be used by any tool that supports CDS views, such as the Analysis
for Microsoft Office, Design Studio, SAP Lumira, or SAP Analytics Cloud.

For more information on CDS views, see also the following documents:

CDS Views

Stability Contracts for CDS Views

View Browser

Custom CDS Views

Custom Fields App and Custom Logic App

Custom Analytical Queries

Overview of CDS Views for Asset Accounting

Data Group Name Technical Name Data Category Corresponding

DataSource
(Extractor)

Master Data Master Fixed Asset I_MasterFixedAsset Dimension

Master Data Fixed Asset I_FixedAsset Dimension IFIXASSET

Master Data Fixed Asset (Time- I_FixedAssetAssgmt Dimension

Dependent Data)

This is custom documentation. For more information, please visit the SAP Help Portal 166
 8/16/2024

Data Group Name Technical Name Data Category Corresponding

DataSource
(Extractor)

Master Data Fixed Asset (Ledger- I_FixedAssetForLedger Dimension

Dependent Data)

Master Data Fixed Asset (Country- I_FixedAssetCountryData Dimension

Dependent Data)

Master Data Fixed Asset Valuation I_AssetValuationForLedger Dimension

(Ledger-Dependent
Data)

Master Data Fixed Asset Valuation I_AssetValuationScrapAmount Dimension

Scrap Values

Master Data Fixed Asset Usage I_FixedAssetUsageObject Dimension

Object

Master Data Total Units of Fixed I_FixedAssetUsageObjectTotal

Asset Usage Object

Master Data Period Units of Fixed I_FixedAssetUsageObjectPeriod

Asset Usage Object

Con guration Data Fixed Asset Group I_FixedAssetGroup Dimension

Con guration Data Depreciation Key I_DepreciationKey Dimension

Con guration Data Depreciation Area I_DepreciationAreaForLedger Dimension

Con guration Data Chart of Depreciation I_ChartOfDepreciation Dimension

Con guration Data Asset Transaction I_AssetTransactionType Dimension

Type

Con guration Data Asset Account I_AssetAcctDetermination Dimension

Determination

Transaction Data Asset Accounting Key I_AssetSortedKeyFigureSetSpec Dimension

Figure Group
Speci cation (With
Sorting Sequence)

Transaction Data Asset Accounting Key I_AssetKeyFigureSet Dimension

Figure Group

Transaction Data Asset Accounting Key I_AssetKeyFigure Dimension

Figure

Con guration Data Asset Class I_AssetClass Dimension

Con guration Data Investment Support I_InvestmentSupportMeasure Dimension

Measure

Con guration Data Company Code (Asset I_CompanyCodeAsset Dimension

Accounting)

Con guration Data CDS Views for Asset I_FixedAssetNatlClfn Dimension

Accounting

Con guration Data Tax Depreciation I_TaxDepreciationGroup Dimension

Group

Transaction Data Asset Balances C_AssetBalance Cube

This is custom documentation. For more information, please visit the SAP Help Portal 167
 8/16/2024

Data Group Name Technical Name Data Category Corresponding

DataSource
(Extractor)

Transaction Data Asset Balances C_FIXEDASSETBALANCE

(Deprecated)

Transaction Data Asset Balances Cube I_AssetBalanceCube Cube

Transaction Data Asset Balances Cube I_FIXEDASSETVALUECUBE Cube

(Deprecated)

Transaction Data Asset History Sheet C_AssetHistorySheet Cube

Transaction Data Asset History Sheet C_FIXEDASSETHISTORYSHEET

(Deprecated)

Transaction Data Asset History Sheet I_AssetHistorySheetCube Cube

Cube

Transaction Data Asset History Sheet I_FIXEDASSETAHSVALUECUBE

Cube (Deprecated)

Transaction Data Depreciation Area I_UserSetttingsForDeprArea Dimension

User Default Value

Transaction Data Selected Currency I_SelectedCurrencyBranch Dimension

Branch

Transaction Data Selected Currency I_LdgrCoCodeSelectedCrcyBranch Dimension

Branch for Ledger and
Company Code

Data Management in Asset Accounting

Archiving Assets using FAA_ASSET

You can use the FAA_ASSET archiving object to archive xed assets.

Checks
The following mandatory and optional checks are carried out for xed assets before they can be archived:

The xed asset must have the status Archivable (mandatory).

A xed asset can be archived if the asset is deactivated and no longer ful ls its business purpose.

The residence time for the xed asset must have expired (mandatory).

Prerequisites
The following prerequisites must be ful lled before a xed asset can be archived:

The following business objects must be archived if these business objects are referenced from xed assets:

Internal order (archiving object CO_ORDER)

This is custom documentation. For more information, please visit the SAP Help Portal 168
 8/16/2024
Operative data of the project system (archiving object PS_PROJECT)

The xed asset has the status Archivable (see section "Checks" above).

The residence time for the xed asset has expired.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FAA_ASSET ILM object as part of SAP Information Lifecycle Management.

The following elds for FAA_ASSET are de ned in the ILM policy and are visible when processing the ILM Policies app:

Available Time Bases

End of Fiscal Year (END_OF_FISCAL_YEAR)

End of Year (END_OF_YEAR)

Available Condition Fields

Standard Field Country from Company Code BS_COUNTRY_OF_BUKRS

Company Code (COMP_CODE)

Asset Class (ASSET_CLASS)

Available Policy Categories

Residence Rules RST

Retention Rules RTP

For more information, see Information Lifecycle Management.

De ning Preprocessing Variants

Preprocessing program for FAA_ASSET selects all deactivated xed assets and checks for these whether the retention rules
are ful lled. If this is the case, the preprocessing program sets the status of the xed asset to Archivable.

You can de ne variants for this program using the following parameters:

Company code

Fixed asset (test run only)

To scal year (test run only)

De ning Write Variants

When you schedule the archiving run, you need to enter an existing variant or create a new one. You can do so in the Manage
Archiving Variants app.

The variant contains the parameters for the xed assets that you want to archive.

You can select the xed assets to be archived using the following parameters:

Company code

Fixed asset (test run only)

This is custom documentation. For more information, please visit the SAP Help Portal 169
 8/16/2024
To scal year (test run only)

Dependencies of FAA_ASSET
The following archiving objects must be archived before or after FAA_ASSET:

Archiving Object Description Predecessors/Successors

CO_ORDER Orders with transaction data Predecessor

PS_PROJECT Project system: Operational structures Predecessor

FI_DOCUMENT Journal entries Successor

This is custom documentation. For more information, please visit the SAP Help Portal 170