Understanding Basic Settings for Asset Accounting with Universal Parallel Accounting (UPA)

Defining Asset Accounting Specific Company Code Settings

Objective

After completing this lesson, you will be able to ​Define​ the closed and the current fiscal year for a company code – asset accounting specific

Company Code Status - Asset Accounting Specific

Business Scenario

Kevin now has the task of preparing company codes for Asset Accounting. Before he or his colleagues can create or post assets, he must check the initial settings for the company code in Asset Accounting.

Company Code Status – Asset Accounting Specific

To use a company code in Asset Accounting, the Bike Company must first define the correct status. The status determines which actions are allowed in a company code's Asset Accounting.

The flowchart illustrates three company code status options in asset accounting: For Testing allows data deletion, Productive prevents deletion, and Deactivated blocks postings and analyses.

These three status options are available:

  1. For Testing:

    Purpose: To perform the initial setup and testing of a new company code.

    Effect: This status allows the deletion of master and transaction data in Asset Accounting.

    Kevin sets the company code to For Testing mode, then completes the configuration and carries out initial test asset creations and postings.

  2. Productive:

    Purpose: For the ongoing, productive operation of the company code.

    Effect: Once the status is Productive, the system prevents any deletion of master and transaction data in Asset Accounting. This ensures data integrity.

    In coordination with project stakeholders, Kevin changes the status to Productive at the company code's Go-Live. At this point, the team has completed the configuration, successfully concluded the tests, and performed the legacy data transfer. From this point on, all transactions are productive.

  3. Deactivated:

    Purpose: To decommission a company code that is no longer required for Asset Accounting.

    Effect: This status blocks all further postings in Asset Accounting. Additionally, reports will no longer include this company code.

    Note

    This status change is irreversible.

Additional Function: Company Code Lock

A lock immediately prevents all postings and changes to asset master data in this company code.

Purpose: To temporarily block all user activity (postings and master data changes) during administrative tasks, such as data migration. This ensures data consistency while work is in progress.

Open and Closed Fiscal Year - Asset Accounting Specific

Before you can make the first posting in Asset Accounting, the system must know which fiscal year is open. This is controlled by the Highest Fiscal Year settings in combination with the closed fiscal year.

You can define the first highest fiscal year in two ways. The appropriate method depends on whether you are performing a legacy data transfer.

The flowchart illustrates how the highest fiscal year in asset accounting is determined automatically or manually.

Method 1: Automatic Determination (with legacy data transfer)

If you transfer assets from a legacy system, set a date for the legacy data transfer.

Action: Define a segment for the legacy data transfer and specify the transfer date.

  • Legacy data transfer date = end of previous fiscal year:

    Effect: The system automatically sets the year of the transfer date as the first highest fiscal year and as the last closed fiscal year.

  • Legacy data transfer date = during the current fiscal year:

    Effect: The system automatically sets the transfer date's year as the first highest (open) fiscal year and the previous year as the last closed fiscal year.

Example: Bike Company’s fiscal year aligns with the calendar year (currently 2026) across all ledgers. Kevin plans the legacy data transfer for December 31, 2025, and creates a segment for that date.

The system identifies 2025 as the highest fiscal year and sets it as the last closed fiscal year. For a successful data transfer and ongoing postings in the current fiscal year, a balance carryforward is still required.

Method 2: Manual Determination (without legacy data transfer)

If a company code belongs to a newly founded company with no legacy data, set the highest fiscal year manually.

Prerequisite: Ensure there are no assets in the company code.

Action: In the company code’s ledger settings, manually enter the "Highest Fiscal Year".

Effect: The system sets the previous year as the closed fiscal year for all depreciation areas.

Example: A company code belongs to a new company founded on January 1, 2026, with no legacy data. Kevin sets the "Highest Fiscal Year" to 2026 in each ledger. The system then sets 2025 as the closed fiscal year. You can then post the first asset transactions in 2026.

Ongoing Operations

During ongoing operations, the system automatically determines the highest (open) fiscal year in Asset Accounting: It is the fiscal year for which you successfully performed the balance carryforward.

You can reopen a closed fiscal year in Asset Accounting for one or more depreciation areas in a ledger to make corrections.

Note

You cannot reopen a fiscal year once it is closed in accounting and certified by an external auditor.

Summary

  • Set the company code status to For Testing during initial setup to allow deletion of master and transaction data.
  • Switch the company code status to Productive to protect data integrity and enable ongoing operations.
  • Use the Deactivated status to decommission a company code permanently; note that this action is irreversible.
  • Define the first highest fiscal year either automatically via segment creation for legacy data transfer or manually for newly founded companies.