Kontakt

Ansicht
Dokumentation

CACS_FPP_DBC_FRAMEWORK - Framework for Parallel Processing of DB Conversion (See Note 833306)

CACS_FPP_DBC_FRAMEWORK - Framework for Parallel Processing of DB Conversion (See Note 833306)

TXBHW - Original Tax Base Amount in Local Currency   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The framework uses parallel background jobs to convert databases. The processing takes place using "events". An event describes the database conversion of a table in the database. The database conversion must take place for each application and client in each system.

Integration

The database conversion for ERP 6.00 takes place for 18 events. This means that the background jobs run for several hours depending on the quantity of data (in the individual tables). For this reason, you should start the database conversion at a time when the system workload is at a minimum. It makes sense to execute the database conversiondirectly after the upgrade. This should be done first in the development system, then in the consolidation system, and then finally (provided the execution is successful) in the production system.

Prerequisites

Before you execute the data conversion (for each application, client, and system) you must first perform the following preliminary work, which you can do using this report. The report is divided into five steps:

(1),,Generate Customizing

(2),,Generate interval distribution

(3),,Start database conversion (parallel processing)

In the case of complete database conversions, you can execute the following optional process steps:

(4),,Delete interval distribution

(5),,Delete Customizing

Features

Selection

Enter the application to be processed.

If you start the "start database conversion (parallel processing)" step (3), then you enter the number of background jobs for each event under parallel processing.

Caution: If you enter "1" job for each event, then at least 18 background jobs are started!

If jobs are to be cancelled, you can only restart the database conversion (flag). If this should occur again when you repeat the database conversion, you should contact SAP.

Standard Variants

Output

Activities

For (1): No further selection conditions necessary -> Start (1)

For (2): No further selection conditions necessary -> Start (2) (dependent on the data volumes in the background)

For (3): Initial execution: ,,Enter the number of jobs for each event.

,,Restart: ,,Set the "Restart" flag.

Optional:

For (4): If you have checked that the database conversion is correct, and do not want to convert any more data from another application in the same client, then you can delete the interval distribution.

For (5): If you have checked that the database conversion is correct, and do not want to convert any more data from another application in the same client, then you can delete the Customizing.

Controls for Database Conversion:

Checks:

  • Use the "Background Jobs Log" button (or F7) to check the logs
  • Use the "Database Conversion Log" button (or F6) to check the logs
  • Check the events in the CACS_DBC_EVENT table
  • Check the instances (interval distribution) in the CACS_FPP_DBCYEAR in the CACS_FPP_DBCYEAR table

Have all events and intervals been processed?

You should also check:

  • Are all time stamps maintained in all tables (see example)?
  • Is the LED_CURR field in the _DOCOBJ table maintained?
  • Does the reference to a _DOCHD line exist?
  • Has the database conversion been executed correctly?

Example

The changes to the data in the individual tables are listed here:

  • The DATE and TIME fields are replaced by a time stamp TIMESTAMP. This affects the triple:

CLC_DATE,,,,CLC_TIME,,,,CLC_TIMESTAMP

KNW_DATE,,,,KNW_TIME,,,,KNW_TIMESTAMP

CHG_DATE,,,,CHG_TIME,,,,CHG_TIMESTAMP

REV_DATE,,,,REV_TIME,,,,REV_TIMESTAMP

And the tables:

_CAS

_B_VAR_CAS

_DOCHD

  • In addition, an "Update Time Stamp" has been added to the document tables. This logs changes to existing data records. The field is called UPD_TIMESTAMP and exists after generation in the following tables:

_DOCACT

_DOCDT

_DOCFI_H

_DOCFI_P

_DOCHD

_DOCINV

_DOCOBJ

_DOCPAR

_DOCRE

_DOCREL

_DOCSE

_DOCSEDT

_DOCVA

_DOCSHA

CACS_CPD_REF

  • The third change affects the _DOCOBJ table, in which you must maintain the LED_CURR field. This happens from a 1:n relationship between _DOCHD and _DOCOBJ.






rdisp/max_wprun_time - Maximum work process run time   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 5956 Date: 20240531 Time: 145506     sap01-206 ( 87 ms )