Show TOC

Archiving Long Text Logs (BC-SRV-ASF-AT)Locate this document in the navigation structure

Definition

Archiving of logged long texts with the archiving object S_AUT_LTXT.

Note

The archiving object LO_CHVW has been revised within the framework of a project to standardize and optimize data archiving. You can use the standardized archiving object by activating the business function Data Archiving: Standardization of Archiving Objects (DA_ARCHOBJ_STANDARD_1). For more information see Data Archiving: Standardization of Archiving Objects or refer to the business function documentation in the Switch Framework (transaction SFW5).

Use

A complete archiving cycle has the following 3 main steps:

  • Executing the preprocessing program:

    The data to be archived is prepared for the write program.

  • Generating the archive files:

    With the help of the write program, the long texts to be archived are sequentially written to newly generated archive files. Note that archiving is client-dependent.

  • Executing the deletion program:

    Once the long texts to be archived have been completely written to the archive files, the deletion program removes them from the database. For security reasons, the system first reads the archived data, and does not start the deletion run until this read operation has been completed successfully.

Recommendation

SAP recommends that you perform the Delete Long Text Logs function (program S_AUT_DEL) prior to the start of archiving. As a result, you ensure that irrelevant data records are not archived.

You should reload archived data into the database only in exceptional circumstances. For example, it may be necessary to reload data if you discovered immediately after archiving that too much or the wrong data was archived. This data should be reloaded as soon as possible after archiving has been carried out.

Caution

After a release upgrade or code page switch, a reload of archived long texts may lead to a loss of data, and therefore must not be carried out.

The reload program cannot be started if data of a non-archived preprocessing program exists. If necessary, discard this data using the program S_AUT_ARCH_UNDO.

When you reload archived data, note that active info structures for the reloaded archive files must be manually deconstructed (transaction Start of the navigation path SARI Next navigation step Status End of the navigation path).

The archiving programs use the Codepage information to format the data. A different data conversion may be required depending on the current code page at the time of long text logging.

Caution

If you changed the code page of the systems (for example as a result of an upgrade from SAP R/3 4.6C to SAP ERP including a switchover to a two-byte Unicode code page), you have to record in the system the time at which this code page switch took place. Specifying the wrong code page may result in loss of data.

You record the change in the code page in Customizing under Start of the navigation path SAP NetWeaver Next navigation step Application Server Next navigation step System Administration Next navigation step Evaluation of Table Changes Next navigation step Document Code Page Migrations End of the navigation path.

Structure

The archiving object S_AUT_LTXT archives the following tables:

  • AUT_D_STXH_ARCH

  • AUT_D_STXL_ARCH

The following programs are available for the archiving object:

Function

Program:

Preprocessing

S_AUT_ARCH_PRE

Write

S_AUT_ARCH_WRI

Delete

S_AUT_ARCH_DEL

Reload (to be run in exceptional cases only)

S_AUT_ARCH_REL