Ansicht
Dokumentation

FINS_CFIN_ACTY_TP_REPL - Transfer Activity Types from Source System to Central Finance

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Purpose

If you need activity type data in the Central Finance system, for example, using activity type as one mapping entity for activity rate replication, you can use this program to manually transfer specific activity types from a source system to the Central Finance system, instead of creating such information from a scratch in the Central Finance system.

Additionally, this program will automatically create a mapping relationship for activity types which have not been maintained in key mapping before.

Prerequisites

You have activated Central Finance.

In the Central Finance system, you have authorization for authorization object F_CFIN_TRG(application: 16, activity: 19) for executing activity type replication and K_CSLA(controlling area, activity: 01, 02) for creating and changing activity types master.

In the source system, the RFC user has authorization for authorization object F_CFIN_SRC (purpose: 14, activity: 33) for reading activity type data from source system, and have authorization for authorization object F_CFIN_SRC (purpose: 07, activity: 03) for displaying value help data from source system.

Features

Harmonization of Activity Type Master Data

You can use this program to create or update activity type master data in the Central Finance system, to ensure consistent activity type information in source and Central Finance systems.

Mapping for Activity Type

In the Central Finance system, the values of relevant controlling area and cost element have run through business mapping. While for the activity type, its value in the Central Finance system is determined following different rules.

• If mapping relationship exists for a source activity type in key mapping, the target activity type derives from the key mapping configuration.

• If 1:N mapping relationship exists for a source activity type in key mapping, the activity type cannot be transferred to the Central Finance system. And an error message will be returned to AIF.

• If no mapping relationship exists for the activity type, the target activity type can be different depending on the implementation of BADI_FINS_CFIN_ACTY_TP_REPL. With the target activity type, a mapping relationship between source and target activity types will be automatically created and maintained into the key mapping in the subsequent transfer process.

• If the BADI is implemented, the value generated from the BADI will be used as the target activity type.

• If the BADI is not implemented, the source activity type value will be used as the target activity type.

Note: In order to ensure the activity type mapping relationship created here can be used by other related replication scenarios like the replication of FI documents, you are recommended to configure the mapping action as 'Mapping obligatory' or 'Mapping if possible' for activity type entity.

Selection

You can use different criteria to specify the activity types you want to transfer from the source system to the Central Finance system.

Value help supported	Mandatory
Source System	Yes	Yes
Controlling Area	Yes	No
Activity Type	Yes	No
Valid On/After	No	No

Output

On the output screen, only default fields are displayed. You can see more fields by clicking the change layoutbutton.

And you can select activity types of specific periods as per your requirement to do transfer or check the transfer results.

Replicate: The system will only do the transfer for the selected activity types. An information message will be prompted to indicate whether the selected activity types are posted to AIF.

AIF: If any of the selected activity types is posted to AIF, the system will jump to the AIF error handling screen where detailed processing messages are shown. If none of the selected activity types is posted, an information message will be prompted.

Please be noted that activity type name and description maintained in all languages will be transferred to the Central Finance system, although only those in system language are displayed on the output screen.

Special Case Handling

If the validity periods for an activity type are inconsistent in the source system and the Central Finance system, the program can split a source period into different sub-periods based on the corresponding period in the Central Finance system. Correspondingly, you may see different message for each sub-period in AIF.

Example:

Given that the following activity type in your source system has been transferred to the Central Finance system.

Source System	Controlling Area	Activity Type	Valid To	Valid From
SXXCLNT001	S001	ACT01	31.12.2021	01.01.2021
Central Finance System	Controlling Area	Activity Type	Valid To	Valid From
CXXCLNT001	C001	CACT01	31.12.2021	01.01.2021

Then you extended period of ACT01 to fiscal year 2022 in your source system and used this program to do transfer for the activity type.

Source System	Controlling Area	Activity Type	Valid To	Valid From
SXXCLNT001	S001	ACT01	31.12.2022	01.01.2021

In AIF, you can see that the period has been split into two sub-periods, 01.01.2021-31.12.2021 and 01.01.2022-31.12.2022. After both split sub-periods are processed, the period for activity type CACT01 in the Central Finance system will also be extended to 2022 as that in the source system.

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8097 Date: 20240531 Time: 091236     sap01-206 ( 107 ms )