Ansicht
Dokumentation

FINS_CFIN_CO_INIT_LOAD_PREP - Preparation for Initial Load of CO Secondary Posting

ABAP Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Purpose

In this Customizing activity, you can complete the preparation required before the initial load of management accounting (CO) postings takes place. This preparation aims to fulfill prerequisites of CO initial load, as well as improve the overall loading performance.

You can use this activity for the following:

• Preparing postings that are relevant for profitability analysis (CO-PA)

• Converting CO-PA line items and characteristics into the key-value pair structure in the CFIN_COPA table

• Storing references of the original documents for the reposting documents using the RKU3 business transaction

• Modifying the CFIN_CO_ADD table, moving elements from the COKEY table into the CFIN_CO_ADD table

• Storing additional attributes to generate the CO key subnumber for the CO key subnumber (HRKFT) field in COEP table

Integration

Prerequisites

Before you start, check the following:

• Ensure the following remote function call (RFC) settings are in place:

• The RFC connections between source and target system are established and functional.

• If the trusted system network is not in place, make sure your user has the S_RFC authorization object assigned and it includes the FIN_CFIN_CO functional group.

• If the trusted system network is in place, make sure your user has the S_RFCACL authorization object assigned.

Note: To assign the correct authorization objects to your user, contact your system administrator.

• The initial load of cost objects is complete.

• You have not performed the initial load of the CO postings.

Features

Selection

Standard Variants

Output

Activities

1. Verify the list of source systems in which you want to perform the initial load preparation.
2. Enter the number of background jobs that run in parallel during initial load preparation. If you do not specify any number, the system will run a fixed number of jobs (10 jobs is the default) in the background.
3. Click the Execute Run button to start the preparation.
4. Monitor the status of each job and perform the following activities as appropriate:

• Refresh

Refresh the status monitor to show the most up-to-date information.

• Restart

Restart a job.

Note: To be restarted, the job must have the status A (Aborted).

• Delta Run

Start the delta run for all entries in each logical system.

Note: To start the delta run for the selected entries, the overall status of the logical system needs to have the status F (Finished and Delta Run Required).

1. Schedule the delta run for the same logical system.

If you added some new company codes for existing logical systems or you added new logical systems for initial load preparation, make sure all logical systems scheduled for the current initial load preparation have finished the delta run successfully before you schedule another run.

1. Where jobs have the status A (Aborted), log on to the source system and check for the following:

• Main job has stopped or encountered errors.

You can find out main job number from the CFIN_MIG_LOG_CO table based on the fields, Company Code (BUKRS) and Run Mode (RUN_MODE).

• Sub jobs encountered errors.

You can find a list of aborted jobs and their numbers from the CFIN_JOB_LOG_CO table based on the fields, CO Area (KOKRS), Group (R_GROUP), and Status (JOB_STATUS).

Once you have the details about the aborted jobs, including the job numbers, use the Overview of job selection (SM37) transaction to perform the necessary fixes in the source system, then go back to central system and restart the job.

Example

rdisp/max_wprun_time - Maximum work process run time   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 5850 Date: 20240520 Time: 073341     sap01-206 ( 65 ms )