Ansicht
Dokumentation

RACHECK_ACTIVATION_PARVAL - Check of Prerequisites for Parallel Valuation in FI-AA (New)

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Purpose

You activate new Asset Accounting using the Customizing switch PARALLEL_VAL. This program checks if the prerequisites for the activation are met.

The individual prerequisites are listed in the Implementation Guide of Asset Accounting under Prepare New Asset Accounting.

Integration

Prerequisites

Features

The following transactions are available for running the program:

Check Before Activation (transaction FAA_CHECK_ACTIVATION)

This transaction is contained in the Customizing activity Check Prerequisites for Activating Asset Accounting (New).

You can start the transaction (or the Customizing activity) at the following points in time:

System	Start	Time	Necessity
Customizing System	Manual	Before activation of new Asset Accounting	Mandatory activity
Follow-on systems	Manual	Before Customizing changes are imported	Recommended activity
Follow-on systems	Automatic	When new Customizing settings are being imported	Mandatory activity (automatic)

Before you import the value for the Customizing switch PARALLEL_VAL and the other configuration data from the preceding system, you have to execute this transaction (or the Customizing activity) so that the system can check whether all prerequisites for activating the Customizing switch are met and whether all periodic postings have been completed correctly. This preliminary check ensures that the checks performed during the Customizing import are successful.

Also ensure that absolutely no postings are made between the successful execution of transaction FAA_CHECK_ACTIVATION and the import of Customizing switch PARALLEL_VAL.

Check and Activation (transaction FAA_DO_ACTIVATION)

If the value for the Customizing switch PARALLEL_VAL and the other configuration data are changed directly in the client (Customizing client or test client, for example) and not by means of a transport, you can run this transaction to execute the check and activation directly that would otherwise take place during the transport.

You need the following authorization for this activation:

• S_TABU_DIS = table maintenance (using standard tools, such as transaction SM30) with the values

• ACTVT (activity) = '02' (add, change, or delete table entries)

• DICBERCLS (authorization group) = 'AC'

After successful activation, you can use new Asset Accounting.

You can execute the transaction in the test run. Even if the transaction has been executed successfully, you still need to deactivate the Test Run indicator to activate the function fully so that postings can take place using the new logic.

If the checks are not successful, it is possible to force the activation. However, this option is not available in the production system and should never be used in clients with productive use. Forcing activation despite an unsuccessful check leads to inconsistency between existing data and new Customizing or postings completed after the activation. Therefore, you can only use this option if data consistency within the client is not important (in test clients or practice clients, for example).

Output

The messages are displayed in the application log.

Activities

ABAP Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4529 Date: 20240520 Time: 135556     sap01-206 ( 63 ms )