9/14/2022

Data Archiving (CA-ARC)

Generated on: 2022-09-14 10:15:56 GMT+0000

SAP S/4HANA | 1909 (Sep 2019)

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/0cc7ab3f01db4133a5d830dfd566abb6?locale=en-

US&state=PRODUCTION&version=1909.000

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 9/14/2022

Data Archiving in Financial Accounting (FI)

The following table shows the business objects in Financial Accounting and the corresponding archiving objects:

Objects in Financial Accounting Archiving Object

Asset data AM_ASSET

Bank data storage FI_ELBANK

Bank master data FI_BANKS

Budget hierarchy documents (Funds Management) FM_BUDHIE

CO posting documents (Funds Management) FM_DOC_CO

Customer master data FI_ACCRECV

Line items (consolidation) FI_LC_ITEM

FI accounting document (Funds Management) FM_DOC_FI

Cash journal documents FI_TCJ_DOC

Supplier/Vendor master data FI_ACCPAYB

Earmarked funds documents (Funds Management) FM_FUNRES

Commitment and funds transfer documents (Funds Management) FM_DOC_OI

G/L account master data FI_ACCOUNT

Check data FI_SCHECK

Totals records (Consolidation) FI_LC_SUM

Totals records and line items (consolidation) (Reload, delete, and FLC_OBJECT
read only)

Totals records and line items (Special Purpose Ledger) FI_SL_DATA

Payment requests FI_PAYRQ

Archiving Financial Accounting Data (FI)

De nition
In Financial Accounting you can archive the following business objects:

Description Archiving object

Bank master data FI_BANKS

Customer master data FI_ACCRECV

Customer transaction gures FI_TF_DEB

Electronic bank data FI_ELBANK

Journal Entries/Financial Accouting Documents FI_DOCUMNT

Supplier/Vendor master data FI_ACCPAYB

This is custom documentation. For more information, please visit the SAP Help Portal 2
 9/14/2022

Supplier/Vendor transaction gures FI_TF_CRE

G/L account master data FI_ACCOUNT

G/L account transaction gures (new) FI_TF_GLF

Checks FI_SCHECK

Payment requests FI_PAYRQ

Payment release list items FI_FPRL

Use
You can access the archiving functions via Archive Administration (transaction SARA) or from within the menu under G/L
Account, Customers, Vendors or Banks, by choosing Periodic Processing Archiving <name of archiving object> .

When you access the archiving functions from the main menu under G/L Account, Customers, Vendors or Banks, the
corresponding archiving object is automatically called. In Archive Administration you must enter the archiving object manually.

To nd out how to archive the different data objects, see the descriptions of the different archiving objects with the title
Archiving <object type>.

See also: The Archiving Object.

 Note
To reduce memory consumption, you can use Data Aging for certain business objects. For more information, see Data Aging
for Financial Accounting Documents.

Dependencies in Financial Accounting (FI)

During archiving you must consider dependencies between archiving objects. This means that you will need to know if a
predecessor exists for some of these objects. Predecessors must be archived rst.

You can display this information by viewing the network graphic that shows the sequence in which objects must be archived.

To display the network graphic:

1. Choose Tools Administration Administration Archiving.

2. To display the graphic for all archiving objects, make no entry in the eld for the name of the archiving object.

If you want to see the graphic for a speci c object that must be archived in advance, enter the name of the archiving
object.

3. Choose Goto Network graphic.

To display the graphic for a speci c object from the General Ledger menu, choose Periodic processing Archiving <Archiving
object (Document for example)> Archive. Then choose Goto Network graphic .

If only a single object is displayed within the network graphic, then there are no dependencies for that object.

If you want to archive bank master data, the network graphic shows you which objects to archive and in which sequence they
must be archived. Bank master data cannot be archived before you have archived all Accounts Payable and Accounts Receivable

This is custom documentation. For more information, please visit the SAP Help Portal 3
 9/14/2022
accounts for which this bank master data is used. Customer and vendor accounts cannot be archived if their documents and
transaction gures still exist in the system.

You must adhere to the following sequence:

1. Archive objects of subledgers, such as cost accounting and asset accounting, rst

2. Archive journal entries and transaction gures

3. Archive customer and vendor master data

4. Archive bank master data

Archiving Authorizations (FI)

The S_ARCHIVE authorization object controls the execution of the different archiving programs (write, delete, and read).

For more information, see User Authorization Checks.

To archive data, you require the following authorizations:

S_ADMIN_FCD for printing and using the spool

S_BTCH_JOB for archiving and deleting data, and for the read program in background processing

You can create authorizations in Customizing under Financial Accounting Global Settings by choosing Maintain Authorizations.

Available Archiving Programs (FI)

The following table lists the write and delete programs available in Financial Accounting.

List of available programs

Archiving Object Write Program Delete Program

FI_DOCUMNT FI_DOCUMNT_WRI FI_DOCUMNT_DEL

FI_TF_CRE FI_TF_CRE_WRI FI_TF_CRE_DEL

FI_TF_DEB FI_TF_DEB_WRI FI_TF_DEB_DEL

FI_TF_GLF FI_TF_GLF_WRI FI_TF_GLF_DEL

FI_SCHECK RFCHKA00 RFCHKA10

FI_PAYRQ FI_PAYRQ_WRI FI_PAYRQ_DEL

FI_ELBANK SAPF066 SAPF066D

FI_ACCOUNT SAPF053 SAPF053D

FI_ACCRECV SAPF056 SAPF056D

FI_ACCPAYB SAPF058 SAPF058D

FI_BANKS FI_BANKS_WRI FI_BANKS_DEL

 Note
This is custom documentation. For more information, please visit the SAP Help Portal 4
 9/14/2022
For the archiving objects FI_DOCUMNT and FI_TF_GLF there is a compression run and an analyzing run that you have to use
in addition to the write programs. To use the compression run and the analyzing run in the SAP Easy Access menu choose
Accounting Financial Accounting General Ledger Periodic Processing Archiving Archiving Journal Entries Analyze Data
and Compress Data.

You can also use data aging for reducing memory consumption. To use data aging, in the SAP Easy Access menu
chooseAccounting Financial Accounting General Ledger Periodic Processing Data Aging Journal Entries . For more
information see Data Aging for Financial Accounting Documents.

Archiving Deferred Taxes Using FI_DEFTAX

You can use archiving object FI_DEFTAX to archive deferred taxes. For more information about deferred taxes, see Deferred
Taxes.

Tables

FI_DEFTAX archives data from several tables. To check which tables these are, call up transaction SARA, enter the archiving
object, and choose Database Tables. You can display the relevant tables in the lower part of the screen.

Archiving Classes

FI_DEFTAX may trigger further archiving classes to write additional data, for example change documents, into the archive. To
check which classes these are, call up transaction AOBJ, select your archiving object and choose Archiving Classes Used.

Programs

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

Prerequisites
The following prerequisites must be ful lled before deferred taxes can be archived:

The invoices have been cleared

The taxes have been reported completely

The following checks have been carried out:

The posting dates of all payments and of all down payment clearings are smaller than the To Date.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FI_DEFTAX ILM object as part of SAP Information Lifecycle Management. In
transaction IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here
you can also see the available time references and which condition elds exist, and decide which of them shall be used in which
order to de ne your rule structure.

The following condition elds are available:

BS_COUNTRY_OF_BUKRS – Country Code from Company Code

BUKRS – Company Code

The following time references are available:

END_OF_MONTH - End of Month

This is custom documentation. For more information, please visit the SAP Help Portal 5
 9/14/2022
END_OF_QUARTER - End of Quarter

END_OF_YEAR - End of Year

For more information, see SAP Information Lifecycle Management.

De ning Write Variants

When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

A write variant contains the parameters for the deferred taxes that you want to archive.

SAP delivers the following parameters:

Company Code

An organizational unit within nancial accounting

Document Number

The key that the system uses to access the accounting document

Fiscal Year

The period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The scal year can
be the same as the calendar year, but does not have to be.

To Date

The date up to which objects are archived. An object is only archived if the posting dates of all payments and all down
payment clearing is before the archiving date.

Displaying Deferred Taxes Archived with FI_DEFTAX

To display archived deferred taxes using the Archive Information System, you need an archive information structure that was
created based on the SAP_FI_DEFTAX01 eld catalog provided by SAP.

An infostructure is only usable if it has been activated and built.

Archiving Financial Accounting Documents (FI-GL, FI-AR, FI-AP)

De nition
You can archive nancial accounting documents (FI documents, journal entries) using the archiving object FI_DOCUMNT.

To manage memory consumption, you can also use data aging for nancial accounting documents. For more information, see
Data Aging for Financial Accounting Documents.

You can access nancial accounting documents that have already been archived. For more information, see Displaying Archived
Accounting Documents (FI).

Use

This is custom documentation. For more information, please visit the SAP Help Portal 6
 9/14/2022
When you archive documents, the system writes the archivable documents, including change documents, SAPscript texts, and
ArchiveLink linkage data, to one or more archive les.

A number of conditions must be met to ensure that only documents no longer needed in the online system are archived. The
write program checks the document header and line items to determine whether a document can be archived. For more
information see Checks (FI-GL, FI-AR, FI-AP).

Structure
Tables

Archiving object FI_DOCUMNT is used to archive data from different tables. For more information about how to display the table
names, see Tables and Archiving Objects.

The system copies the structure of line item tables of the general ledger, e.g. FAGLFlEXA, that existed before S/4HANA into the
archive because they are necessary for displaying archived journal entries. This information is calculated using table ACDOCA;
no information will be deleted. In addition, table ACDOCA is archived, but not deleted, because this table is also used for
calculating balances (transaction gures). G/L transaction gures are archived using archiving object FI_TF_GLF. The entries in
the table are changed, so that they are no longer used for line item and journal entry reports. The enries of the table are
deleted when the data is compressed.

For AP/AR transaction gures, that are primarily based on tables BKPF and BSEG, either table LFCX_DIF or KNCX_DIF is
adjusted to that the balance of the archived journal entries is stored. So the transaction gures in AP/AR are the result of the
sum of the journal entries in the database and these tables. You use the archiving objects FI_TF_DEB and FI_TF_CRE to archive
those tables.

Extended Archive Management

In addition to the management data generated by ADK, archiving object FI_DOCUMNT writes additional management data to
tables T001_ARCH and ADMI_FI_DOC.

Programs

The following programs are delivered for FI_DOCUMNT.

Program Function

FI_DOCUMNT_WRI Write

FI_DOCUMNT_DEL Delete

FI_DOCUMNT_PST Postprocessing

SAPF048S Correction: Building of secondary indexes

SAPF048X Correction: Repair of extended archive management

The delete program contains the standard variants SAP&PROD (production mode) and SAP&TEST (test mode). During the
write and delete sessions, regular progress messages appear in the job log (background processing) and in the status line
(dialog).

Integration

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 7
 9/14/2022
You can use archiving object FI_DOCUMNT in Information Lifecycle Management. You must have activated the corresponding
business functions to do this. The system then also shows the ILM Actions group box. You can use these actions to carry out
archiving, for example, where the retention periods stored in the Information Retention Manager can be evaluated.
Additionally, you can create snapshots (copies) of data or destroy data that matches the requirements. For more
information, see ILM Enhancements for Data Archiving, ILM Actions in the Write Program.

Secondary Indexes in Financial Accounting

A number of programs in nancial accounting do not use journal entries / nancial accounting documents (tables BKPF and
BSEG) directly. Instead they use a secondary index, that is implemented as a view on BKPF and BSEG. BSIP, in contrast, is a data
base table. See also Displaying Archived Accounting Documents (FI).

Since a lot of programs use this data, there is the possibility to keep this data for a longer period of time in the system even
when the journal entry has already been archived. If you set the run time of the secondary index greater than the account type
life, the system writes, when archiving the journal entries, a redundant copy to the data base (table BSIS_ BCK, BSAS_ BCK,
BSAD_BCK, BSAS_BCK). For more information, see Secondary Index Life in Financial Accounting (FI).

When the secondary index run time has expired, you can later on remove these entries from the data base using the
Postprocessing Program (FI).

You can use the secondary index build program to reconstruct the secondary indexes from the archived document data and
store them again in the database, if necessary (except for BSIM entries).

 Note

If you archive data because of reasons of data protection and privacy, note that secondary indexes may contain
personal data. For this reason, secondary indexes are not allowed to have a greater run time.

In S/4HANA almost all accounts are managed based on line items. So secondary indexes might have a bigger data
volume than in other SAP products.

If you use data aging and you want to keep secondary indexes longer in the system, maintain the partitioning object
FI_INDEX in order to create historical partitions for BSIS_BCK, BSAS_BCK, BSAD_BCK and BSAK_BCK. Then the
secondary indexes that are created during archiving are directly written to the historical partition. For more
information see Data Aging for Financial Accounting Documents

Archiving Double-Entry Invoicing Data

The double-entry invoicing data (table BSIP) is deleted by the archiving object FI_DOCUMNT. So that you can store this data in
the database longer than the nancial accounting document itself, it is removed from the database together with the vendor
secondary indexes (table BSAK) by the postprocessing program and not by the delete program.

The double-entry invoice veri cation can take place as long as the vendor secondary index BSIP still exists in the database, even
if the corresponding document was already archived.

In Customizing for account type lives (to archive nancial accounting documents) you should set the secondary indexes for
vendors so that the data for the double-entry invoice veri cation remains in the system for the required period of time. For
more information about archiving account type lives, see Archiving Account Type Lives in Customizing for Financial Accounting
under Financial Accounting Global Settings Document Archiving Accounting Documents.

Cross-Company Code Posting Processes (Table BVOR)

The archived documents of a cross-company code posting process are treated in the following manner:

This is custom documentation. For more information, please visit the SAP Help Portal 8
 9/14/2022
1. For every document the write program copies not only the data record of the cross-company code posting process to the
archive, but all data records of the same cross-company code posting process ( eld BVOR-BVORG) to which the
document to be archived belongs. This ensures that the information about the cross-company code posting process is
completely available for a direct access to the archive.

2. For every archived document the delete program sets the BVOR-XARCH indicator. Then for every archived document of a
cross-company code posting process it tries to delete all data records of the complete corresponding cross-company
code posting process. However, a cross-company code posting process can only be deleted from the database, when all
documents of a cross-company code posting process have been archived (technically this means that in the database
the BVOR-XARCH indicator must be set for all BVOR entries with the same BVOR-BVORG).

More Information
Displaying Archived Accounting Documents (FI).

Archiving Bank Communication Management Using

BNKCOM_ARC
You can use archiving object BNKCOM_ARC to archive bank communication management.

Tables

BNKCOM_ARC archives data from several tables. To check which tables these are, call up transaction SARA, enter the archiving
object, and choose Database Tables. You can display the relevant tables in the lower part of the screen.

Archiving Classes

BNKCOM_ARC may trigger further archiving classes to write additional data, for example change documents, into the archive. To
check which classes these are, call up transaction AOBJ, select your archiving object and choose Archiving Classes Used.

Programs

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

Prerequisites
The following prerequisites must be ful lled before a bank communication management batch can be archived:

The date of the le generation ( eld LAUFD_F in the table BNK_STR_BATCH_HEADER) of the selected batches must be
within a posting period that is closed for postings in nancial accounting.

ILM-Related Information for the Archiving Object

You can use this archiving object with the BNKCOM_ARC ILM object as part of SAP Information Lifecycle Management. In
transaction IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here
you can also see the available time references and which condition elds exist, and decide which of them shall be used in which
order to de ne your rule structure.

The following condition elds are available:

BS_COUNTRY_OF_BUKRS (Standard Field Country from Company Code)

BUKRS (Paying Company Code)

This is custom documentation. For more information, please visit the SAP Help Portal 9
 9/14/2022
CRDATE (Created On)

The following time references are available:

CREATION_DATE (Created On)

De ning Write Variants

When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

A write variant contains the parameters for the bank communication management that you want to archive.

SAP delivers the following parameters:

Processing Options

Detail Log

Log Output

Archiving Session Note

De ning Preprocessing Variants

The preprocessing program for BNKCOM_ARC sets the archive_status eld to value 02 (Document set for Archive) of
bnk_batch_header (Batch Header) so that bank communication management can be archived.

You can de ne variants for this program using the following parameters:

Processing Options

Detail Log

Log Output

De ning Read Program Variants

A read program RBNK_ARC_READ sequentially reads from a given archive and displays the data. You can de ne the following
selection criteria for this program:

Batch Number

Rule ID

Batch Amount

Batch Currency

No. of Payments

Create Date

Dependencies of BNKCOM_ARC
For information on the archiving session order, see the Network Graphic for your archiving object in transaction SARA under
Goto → Network Graphic.

Authorizations for BNKCOM_ARC

This is custom documentation. For more information, please visit the SAP Help Portal 10
 9/14/2022
You need the following authorization objects:

Activity Required Authorization Object

READ (read and display batch or batch item) F_STAT_MON

01 (write, delete, and read) S_ARCHIVE

Displaying Bank Communication Management Archived with BNKCOM_ARC

Single document display: A read program that RBNK_ARC_READ sequentially reads from a given archive and displays the data.

Secondary Index in Financial Accounting (FI)

Formerly it was possible to keep a secondary index in the database when archiving nancial accounting documents. As there
may be documents archived already, the secondary indexes corresponding to archived documents are kept in the system. They
are stored in a database table with the original name followed by _BCK). It is possible to delete a secondary index after a
certain period of time (speci ed by the secondary index life time) and it is possible to build up secondary indexes from archived
documents.

Secondary Index Life in Financial Accounting

You can de ne secondary index lives. When this time period has been completed, you can delete the secondary indexes from the
database using a Postprocessing Program (FI).

Secondary indexes contain information on G/L, customer and vendor accounts that is used when displaying line items. They
also contain information used for double invoice veri cation.

The secondary index life determines whether and for how long an index for a document (based on the posting date and
secondary index removal program key date) should remain in the system following archiving of the document.

You de ne secondary index lives in Customizing for Financial Accounting Global Settings in the process step De ne Account
Type Lives.

Among other things, this allows you to display the line items for archived documents. For more information, see Line Item
Display.

If you have accidentally deleted a secondary index or need to reconstruct one for any reason, see Secondary Index Build
Program (FI).

Postprocessing Program (FI)

Use
The postprocessing program is used to delete the secondary indexes of nancial accounting from the database, according to
the secondary index life you entered in Customizing.

You can start the postprocessing program and enter the necessary selection criteria, from within Archive Administration by
choosing Postprocessing.

This is custom documentation. For more information, please visit the SAP Help Portal 11
 9/14/2022

Features
The post processing program deletes all secondary indexes whose lives have expired by the key date. The index life runs from
the clearing date (or the posting date in the case of accounts not managed on an open item basis). The documents belonging to
the secondary index must already have been archived.

The program deletes the secondary indexes from tables BSIS_BCK, BSAS_BCK, BSAD_BCK, BSAK_BCK, BSIP, FAGLBSIS_BCK,
and FAGLBSAS_BCK.

 Note
The postprocessing program takes clearing transactions into account, meaning that if you select both cleared and open
items for display, the displayed balance can be incorrect. In accounting terms no error has occurred, since the balance is
equivalent to the total of open items. You should therefore display balances using the account balance function and not line
item display.

More Information
Secondary Index Build Program (FI)

Secondary Index Build Program (FI)

Context
You can use program SAPF048S to build secondary indexes. However, this program is a correction program and should only be
used under the following circumstances:

You accidentally deleted the secondary indexes

You have never built the indexes

You want to (re)build the indexes for other reasons

When indexes are built from archives that had not been converted the secondary indexes are translated. They then have
the same condition as if they had been part of the local currency changeover.

Displaying Archived Accounting Documents (FI)

Use
You can display individual accounting documents from the archive. You can display a document using, for example, the Archive
Information System, the document display function or from the display line items function via the General Ledger, Account
Receivable or Accounts Payable menu.

 Note
Documents can only be displayed if an appropriate archive index exists for them.

You can index your FI_DOCUMNT archives using the Archive Information System. The old archive index in table ARIX_BKPF
is no longer updated. However, if you have indexed old archives with this index, it will continue to be evaluated in table
ARIX_BKPF.

This is custom documentation. For more information, please visit the SAP Help Portal 12
 9/14/2022

Features
Archive Information System

To display archived accounting documents using the Archive Information System or transaction FB03, you require an archive
information structure that has been created based on one of the following standard SAP eld catalogs:

SAP_FI_DOC_001 (FI document by header)

SAP_FI_DOC_002 (FI document by account)

To display archived accounting documents in the General Ledger view (transaction FB03L), you require an information structure
that is based on the following standard eld catalog:

SAP_FI_DOC_003 (FI document G/L view)

The information structure must be active and con gured correctly before it can be used.

For more information about how to use information structures, see Using the Archive Information System.

To display archived accounting documents using the Archive Information System or transaction FB03, you require an archive
information structure that has been created based on one of the following standard SAP eld catalogs:

SAP_FI_DOC_001 (FI document by header)

SAP_FI_DOC_002 (FI document by account)

To display archived accounting documents in the General Ledger view (transaction FB03L), you require an information structure
that is based on the following standard eld catalog:

SAP_FI_DOC_003 (FI document G/L view)

The information structure must be active and con gured correctly before it can be used.

For more information about how to use information structures, see Using the Archive Information System.

Line Item List

You can display the line items of an account only if the corresponding secondary indexes are still available in the system.

If you want the documents that have already been archived to continue to be available in the line item display of an account, you
must adjust the secondary index life accordingly in the account life Customizing for document archiving. For more information,
see Secondary Index Life in Financial Accounting (FI).

Having the line item report linked with the archive allows you to view all lines items available in the database and in the archive,
even if the corresponding documents have been archived and the corresponding FI secondary indexes have been deleted. The
archive can be accessed either via the Archive Information System or through a manual selection of the archives. For more
information, see SAP Note 596865 .

More Information
Document Relationship Browser (DRB) in Accounting

Line Item Display

Document Display

This is custom documentation. For more information, please visit the SAP Help Portal 13
 9/14/2022

Programs for Evaluating Documents (FI)

Evaluation programs allow different types of evaluation for selected archives, using additional selection criteria where
necessary. Some of these programs also take the type of database into consideration.

Archived data can also be evaluated by standard evaluation programs like RFBELJ00 (for creating the compact journal) and
RFEPOJ00 (for creating the line item journal).

Program name Meaning

FAGL_ACCOUNT_ITEMS_GL G/L account line item report

RFITEMAP Vendor line item report

RFITEMAR Customer line item report

RFITEMGL G/L account line item report

RFBELJ00 Compact journal

RFEPOJ00 Line item journal

RFKKET00 Extract for accumulated open item balance audit trail

RFKLET00 Extract for the accumulated historical balance audit trail

 Note
For the changeover of archives that have not been translated the documents are translated according to the local currency
changeover. The documents then have the same condition as if they had been part of the local currency changeover.

Archiving FI Transaction Figures (FI-GL, FI-AR, FI-AP)

De nition
Transaction gures are archived and deleted using the following archiving objects.

Archiving Object Type of Transaction Figure

FI_TF_CRE Vendors

FI_TF_DEB Customers

FI_TF_GLF G/L accounts (new)*

*including SAPscript texts of G/L accounts

 Caution
In other products, customer, vendor and G/L account transaction gures were archived and deleted using archiving object
FI_MONTHLY and FI_TF_GLC. The writing and deletion of data using this archiving object is not supported. You must use
the above-named archiving objects.

However, it is still possible to access data that was archived using FI_MONTHLY or FI_TF_GLC. For more information, see
Display of Archived Transaction Figures (FI-GL, FI-AR, FI-AP).

This is custom documentation. For more information, please visit the SAP Help Portal 14
 9/14/2022

 Note
You can use archiving objects FI_TF_CRE, FI_TF_DEB and FI_TF_GLF in Information Lifecycle Management. You must
have activated the corresponding business functions to do this. The system then also shows the ILM Actions group box. You
can use these actions to carry out archiving, for example, where the retention periods stored in the Information Retention
Manager can be evaluated. Additionally, you can create snapshots (copies) of data or destroy data that matches the
requirements. For more information, see ILM Enhancements for Data Archiving, ILM Actions in the Write Program.

Use
Transaction gures can be archived regardless of whether documents exist for that scal year or company code. This means
that it is not necessary to have archived accounting documents with FI_DOCUMNT in order to archive transaction gures.

It is, however, necessary to have archived transaction gures before you can archive the corresponding master data. For
example, vendor master data can only be removed from the system when there are no more vendor transaction gures in the
system. This also applies to the other transaction gures.

Transaction gures that originated in the current or previous scal year cannot be archived. Neither can data from scal years
with open periods or data from all following scal years.

Structure
Tables

The archiving objects for transaction gures are used to archive and delete data from different tables.

For more information about how to display the table names, see Tables and Archiving Objects.

 Note
G/L transaction gures are calculated using entries in table ACDOCA, every time the data in ACDOCA is accessed. Those
entries can be line items of an nancial accounting document, balance carryforward entries or entries resulting from
archiving nancial accounting documents. Since line items of not yet archived accounting documents must not be deleted,
the system enters a sum with inverse +/- sign into the data base. From the operational point of view this is the same as
deleting them. A reduction in data volume only takes places after compressing the data. For more information see Data
Compression.

Transaction Figures in AP/AR are calculated from line items in table BSEG and tables KNCX_DIF and LFCX_DIF. During
archiving, the sums in tables KNCX_DIF and LFCX_DIF are adjusted so that the balances of those tables and the accounting
documents amount to zero.

Programs

The following programs are delivered for the archiving objects for transaction gures.

Archiving Object Program Function

FI_TF_CRE FI_TF_CRE_WRI Write

FI_TF_CRE_DEL Delete

FI_TF_DEB FI_TF_DEB_WRI Write

FI_TF_DEB_DEL Delete

This is custom documentation. For more information, please visit the SAP Help Portal 15
 9/14/2022

Archiving Object Program Function

FI_TF_GLF FI_TF_GLF_WRI Write

FI_TF_GLF_DEL Delete

The write program supports the ADK interruption concept, meaning that you can interrupt the write phase and continue it at a
later point in time. For more information, see Interrupting and Continuing Archiving Sessions.

The delete program contains the standard variants SAP&PROD (production mode) and SAP&TEST (test mode). During the
write and delete sessions, regular progress messages appear in the job log (background processing) and in the status line
(dialog). For more information, see Logs.

More Information
Variant Settings for Writing (FI-GL, FI-AR, FI-AP)

Display of Archived Transaction Figures (FI-GL, FI-AR, FI-AP)

Display of Archived Transaction Figures (FI-GL, FI-AR, FI-AP)

To be able to display archived transaction gures using the Archive Information System need an infostructure that was created
based on one of the following standard eld catalogs provided by SAP:

Archiving Objects Standard Field Catalog Transaction Figure Type

FI_MONTHLY SAP_FI_MONTH_01 General ledger

SAP_FI_MONTH_02 Customer master

SAP_FI_MONTH_03 Vendor master

SAP_FI_MONTH_04 Customer Special Ledger G/L Transaction

SAP_FI_MONTH_05 Vendor Special Ledger G/L Transaction

FI_TF_CRE SAP_FI_TF_CRE_1 Vendor

SAP_FI_TF_CRE_2 Vendor Special Ledger G/L Transaction

FI_TF_DEB SAP_FI_TF_DEB_1 Customer

SAP_FI_TF_DEB_2 Customer Special Ledger G/L Transaction

FI_TF_GLC SAP_FI_TF_GLC_1 General ledger

FI_TF_GLF SAP_FI_TF_GLF_1 General ledger (new)

An infostructure can only be used if it is active and has been built. For more information see Using the Archive Information
System.

Archiving G/L Account Master Data (FI-GL)

De nition
Archiving object FI_ACCOUNT is used to archive and delete G/L account master data.
This is custom documentation. For more information, please visit the SAP Help Portal 16
 9/14/2022

Use
Master data for G/L accounts is stored in two different areas:

General area

A company code-speci c area

During archiving, you can decide from which of these areas you want to archive data. To archive master data, you must set the
deletion ag in the master record. You can set this ag for both the general and speci c areas. It has the following effect:

If you enter the deletion ag in the general area, the system can archive this area only or, if all other requirements have
been ful lled, the entire master record. It follows that to archive the entire master record, you do not need to set the
deletion ag in the company code-speci c area.

If you enter the deletion ag in the company code-speci c area, the system can archive this area of the master record
only, if the other requirements have been ful lled. This enables you, for example, to archive and delete only the company
code data for G/L accounts.

The following requirements must be met before you can archive data in the general area of the master record:

If you have implemented the Sales, Purchasing, or Materials Management application components, then the general
master data of your business partners will be used by these applications, as well as by Financial Accounting (FI).
Accordingly, the general area of master data can only be archived if this does not cause any con icts in the other
application components.

You can archive only those G/L accounts that are not primary cost elements.

All company code-speci c data must be capable of being archived. Company code-speci c data can only be archived if
the account contains no transaction gures or open items.

In addition to the deletion ag, a series of other prerequisites must be met so that you can archive G/L account customer
master data. For more information about the checks performed by the system during archiving, see Checks (FI-GL).

Structure
Tables

Archiving object FI_ACCOUNT is used to archive data from different tables. To nd out how to display the table names, see
Tables and Archiving Objects.

Function/Report Assignment

Functionality Report

Write FI_ACCOUNT_WRI

Delete FI_ACCOUNT_DEL

Integration
Displaying Archived G/L Account Master Data

To display individual objects for the archiving object FI_ACCOUNT using the Archive Information System, you require an
information structure that has been created based on the standard SAP eld catalog SAP_FI_ACC_01. The information
structure must be active and con gured correctly.

This is custom documentation. For more information, please visit the SAP Help Portal 17
 9/14/2022
For more information about information structures, see Using the Archive Information System.

 Note
You can also use the archiving object FI_ACCOUNT in the context of Information Lifecycle Management. You must have
activated the relevant business functions to do this. The system then also shows the ILM Actions frame. You can use these
actions to carry out archiving, for example, where the retention periods stored in the Information Retention Manager can be
evaluated. Additionally, you can create snapshots (copies) of data or destroy data that matches the requirements. For more
information, see the ILM Actions in the Write Program section of ILM Enhancements in Data Archiving.

Checks (FI-GL)
In order for the system to only archive data that is no longer needed in current business processes, this data must meet certain
conditions. To make sure the data to be archived meets these conditions, the write program performs several checks.

Master data is only eligible for archiving if you have set the deletion ag in the master record in each area.

When you archive Chart of Accounts data for G/L account master data, the system automatically checks whether the following
conditions have been met:

The deletion ag is set.

Dependent data of the following types no longer exists in the system:

Company code-speci c data

Dependent cost elements

When you archive Company Code data for G/L account master data, the system automatically checks whether the following
conditions have been met:

The deletion ag is set.

Dependent data of the following types no longer exists in the system:

Transaction gures

Open items

Cleared items

Variant Settings for Writing (FI-GL)

Use
When you schedule the write program you must either enter an already existing variant or create a new one. The variant
contains the selection criteria for the G/L account master data you want to archive.

Features
In the Data To Be Archived dropdown list box you can choose the areas from which you want to archive master data. You can
choose from the following areas:

Chart of Accounts Data

This is custom documentation. For more information, please visit the SAP Help Portal 18
 9/14/2022
The system archives only the master data for a speci c chart of accounts.

Company Code Data

The system archives only the master data for a speci c company code.

In the G/L Account Master Data frame you can choose the following selection
criteria:
Chart of Accounts

The system archives only the master data that falls within the range of chart of accounts you enter.

Company Code

The system archives only master data that falls within the range of company codes you enter.

This selection option is only offered if you have chosen Company Code Data for archiving.

G/L Account

The system archives only master data that falls within the range of G/L accounts you enter.

Additional Settings

The settings you make under Processing Options, for Log Settings, and Archiving Session Note are standard settings that are
also valid for other archiving objects. They are therefore described in the general archiving documentation under Variant
Maintenance for Archiving Jobs .

Archiving Customer Master Data (FI-AR, SD)

De nition
Archiving object FI_ACCRECV is used to archive and delete customer master data in the Financial Accounting (FI) and Sales
and Distribution (SD) components.

Use
Customer master data is stored and archived in three different areas, as follows:

General data

FI data (for a speci c company code)

SD data (for a speci c sales organization)

When you archive general data that depends on data in the other two areas, archive in sequence of FI data, SD data, general
data.

This is custom documentation. For more information, please visit the SAP Help Portal 19
 9/14/2022
The term customer master data is used in both the FI and SD components.

Calling the Archiving Function

You can archive customer master data on the SAP Easy Access screen under Tools → Administration → Administration → Data
Archiving.

Structure
Tables

Archiving object FI_ACCRECV is used to archive data from different tables. For more information about how to display the table
names for individual archiving objects, see Tables and Archiving Objects.

Reports

The following table shows the available reports:

Function Report

Write FI_ACCRECV_WRI

Delete FI_ACCRECV_DEL

Archiving Classes

FI_ACCRECV may trigger further archiving classes to write additional data, for example change documents, into the archive. To
check which classes these are, call up transaction AOBJ, select your archiving object and choose Archiving Classes Used.

Programs

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

Integration
Displaying Archived Customer Master Data

To display individual documents for archiving object FI_ACCRECV using the Archive Information System, you require an
information structure that has been created based on one of the following standard SAP eld catalogs:

SAP_FI_ACCRECV1 (general customer master data)

SAP_FI_ACCRECV2 (customer master data FI)

SAP_FI_ACCRECV3 (customer master data SD)

 Note
Please see 1037272 for information about the following eld catalogs:

SAP_FI_ACCREC_1

SAP_FI_ACCREC_2

Each information structure must be active and con gured correctly.

This is custom documentation. For more information, please visit the SAP Help Portal 20
 9/14/2022
For more information about information structures, see Using the Archive Information System.

Prerequisites
The following prerequisites must be ful lled before customer master data can be archived:

You must set the archiving ag in the master record. You can set this ag for a complete vendor or for individual
company codes or purchasing organizations.

1. Call up transaction BP and select a business partner by double-clicking on it.

2. On the Status tab, select Archiving Flag.

For more information, see:

Archiving and Deleting a Customer Master Record

Application Customizing (FI-AR, SD)

A series of checks must be passed, for example, all dependent data must be archived and deleted from the database. For
more information, see Checks (FI-AR, SD).

If Business Function ERP_CVP_DP_ILM_1 is active, the residence period must be over and the End of Purpose check must
have blocked the vendor.

If Business Function ERP_CVP_DP_ILM_1 is not active, the residence period must be over.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FI_ACCRECV ILM object as part of SAP Information Lifecycle Management. You must
have activated the corresponding business functions to do so. The system then also shows the ILM Actions group box. You can
use these actions to carry out archiving, for example, where the retention periods stored in the Information Retention Manager
can be evaluated.

In transaction IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here
you can also see the available time references and which condition elds exist, and decide which of them shall be used in which
order to de ne your rule structure.

The following condition elds are available:

APPL_NAME - Application Name

APPL_RULE_VARIANT - Application Rule Variant

BUKRS - Company Code

KTOKD - Account Group

VKORG - Sales Organization

WERKS - Plant

The following time references are available:

END_OF_FISCAL_YEAR - End of Fiscal Year

END_OF_YEAR - End of Year

START_RET_DATE- Start of Retention Period

This is custom documentation. For more information, please visit the SAP Help Portal 21
 9/14/2022
For more information, see SAP Information Lifecycle Management.

Legal Holds

It is possible to set a legal hold on this archiving object. For more information, see Setting Legal Holds.

De ning Write Variants

A write variant contains the parameters for the customer master data that you want to archive.

When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

Dependencies of FI_ACCRECV
For information on the archiving session order, see the Network Graphic for your archiving object in transaction SARA under
Goto → Network Graphic.

Enhancements for FI_ACCRECV

The FI_ACCRECV archiving object offers the following Business Add-Ins (BAdIs):

BAdI Description Used to

FI_ACCRECV_CHECK Archiving of Customer Master Implement additional checks for general

Data (General Part): Additional data
Checks

FI_ACCRECV_CHECK_FI Archiving of Customer Master Implement additional checks for FI data

Data (FI Part): Additional
Checks

FI_ACCRECV_CHECK_MM Archiving of Customer Master Implement additional checks for MM data

Data (MM Part): Additional
Checks

FI_ACCRECV_WRITE Archiving of Customer Master Data (General Enable archiving from additional tables for
Part): Archive Additional Tables general data

FI_ACCRECV_WRITE_FI Archiving of Customer Master Data (FI Enable archiving from additional tables for
Part): Archive Additional Tables FI data

FI_ACCRECV_WRITE_MM Archiving of Customer Master Data (MM Enable archiving from additional tables for
Part): Archive Additional Tables MM data

Related Information
Archive Information System

Checks (FI-AR , SD)

In order for the system to only archive data that is no longer needed in current business processes, this data must meet certain
conditions. To make sure that the data to be archived meets these conditions, the write program performs several checks.

Master data is only eligible for archiving if you have set the deletion ag in the master record in each area.

This is custom documentation. For more information, please visit the SAP Help Portal 22
 9/14/2022
When you archive general data for customer master records, the system automatically checks whether the following conditions
have been met:

The deletion ag is set.

The vendor (that is, the supplier) is not locked for deletion.

Dependent data of the following types no longer exists in the system:

Business partner of the customer

Plants of the customer

Customer / vendor links

Company code-speci c data (Financial Accounting (FI) data)

Sales data (Sales and Distribution (SD) data)

Additional checks may be implemented in your system using BAdI FI_ACCRECV_CHECK.

When you archive FI data for customer master records, the system automatically checks whether the following conditions have
been met:

The deletion ag is set.

The vendor is not locked for deletion.

Dependent data of the following types no longer exists in the system:

Transaction gures

Special general ledger transaction gures

Open items

Cleared items

Store items

Customer / vendor links

Parked documents

Additional checks may be implemented in your system using BAdI FI_ACCRECV_CHECK_FI.

When you archive SD data for customer master records, the system automatically checks whether the following conditions have
been met:

The deletion ag is set.

Dependent data of the following types no longer exists in the system:

Customer hierarchies

Partner functions

Additional checks may be implemented in your system using BAdI FI_ACCRECV_CHECK_SD.

Related Information
Customer Hierarchies

This is custom documentation. For more information, please visit the SAP Help Portal 23
 9/14/2022
Partner Functions

Application Customizing (FI-AR, SD)

Use
You can set the deletion indicator for a customer in application Customizing.

Activities
You have the following options for accessing application Customizing:

To access archive management on the SAP Easy Access screen, choose Tools Administration Administration Data
Archiving . Enter as object name FI_ACCRECV. Choose Customizing and then Application-Speci c Customizing.

To access archive management on the SAP Easy Access screen under Sales and Distribution, choose Logistics Sales
and Distribution Master Data Business Partner Customer Archiving . Then choose Customizing and then Application-
Speci c Customizing.

To access archive management on the SAP Easy Access screen under Financial Accounting, choose
Accounting Financial Accounting Accounts Receivable Periodic Processing Archiving Customers . Then choose
Customizing and then Application-Speci c Customizing.

Related Information
Archiving Customer Master Data (FI-AR, SD)

Variant Settings for Writing (FI-AR, SD)

Use
When you schedule the write program, you must either enter an already existing variant or create a new one. The variant
contains the selection criteria for the customer master data you want to archive.

Features
In the Data To Be Archived dropdown list box, you can choose the areas from which you want to archive master data. You can
choose from the following areas:

General Data

The system archives only general data (not chart of account-speci c).

FI Data

The system archives only company code-speci c master data.

SD Data

The system archives only sales organization-speci c master data.

Document Selection Criteria

This is custom documentation. For more information, please visit the SAP Help Portal 24
 9/14/2022
In the Customer Master Data, you can choose the following selection criteria:

Vendor

The system archives only the master data of accounts that fall within the range covered by the selection criteria you
enter.

Company Code

The system archives only the master data of company codes that fall within the range covered by the selection criteria
you enter.

This selection option is only offered if you are archiving FI data.

Purchasing Organization

The system archives only the master data of accounts that fall within the range covered by the selection criteria you
enter.

This selection option is only offered if you are archiving MM data.

Additional Selections and Options

In the Selections frame you can make the following setting:

Minimum Number of Days in the System

This function is identical for customers and vendors. For a detailed description of this option, see Variant Settings for
Writing (FI-AP) in the section on vendors.

In the Options frame, you can make the following settings:

FI Link Validation Off

This function is identical for customers and vendors. For a detailed description of this option, see Variant Settings for
Writing (FI-AP) in the section on vendors.

SD Document Validation Off

If this ag is set, the system does not check in SD whether sales documents still exist for the master record that is to be
archived. This check generates long runtimes and may not always be necessary. You can therefore switch off this check
and herewith reduce the runtime of the write program. In the standard system, this check is always switched on.

This option is only relevant if you are archiving SD data.

Take Deletion Flag Into Account

This function is identical for customers and vendors. For a detailed description of this option see Variant Settings for
Writing (FI-AP) in the section on vendors.

Additional Settings

The settings you make under Processing Options, for Log Settings, and Archiving Session Note are standard settings that are
also valid for other archiving objects. They are therefore described in the general archiving documentation under Variant
Maintenance for Archiving Jobs.

Related Information
Creating Archive Files

This is custom documentation. For more information, please visit the SAP Help Portal 25
 9/14/2022

ILM-related Information for FI_ACCRECV

Use
To create and use policies and rules for the archiving object FI_ACCRECV in Retention Management of ILM, an ILM object is
available. FI_ACCRECV is the ILM object associated with the archiving object FI_ACCRECV.

For more information, see Archiving Customer Master Data (FI-AR, SD)

Prerequisites
You have activated the business function Activating SAP ILM (ILM).

For more information, see Activating SAP ILM

Features
Condition Fields and Time References

To de ne retention rules using ILM policies (transaction IRMPOL), you can use the following condition elds and time
references (start time for determining the retention duration) for the ILM object.

Condition Fields

Condition Fields Description

APPL_NAME Application Name

APPL_RULE_VARIANT Application Rule Variant

KTOKD Customer Account Group

BUKRS Company Code

VKORG Sales Organization

BS_COUNTRY_OF_BUKRS Country of Company Code

WERKS Plant Table for National (Centrally Agreed) Contracts

Time Reference

Start Retention Time Description

START_RET_DATE Start Date of Retention

END_OF_FISCAL_YEAR End of Fiscal Year

END_OF_YEAR End of Year

Object Category and Policy Category

You de ne policies for FI_ACCRECV in the BOR object category (data BUS1007) with the Retention Rules policy category RST
and RTP.

Archiving Supplier/Vendor Master Data (FI-AP)

This is custom documentation. For more information, please visit the SAP Help Portal 26
 9/14/2022

De nition
Archiving object FI_ACCPAYB is used to archive and delete supplier/vendor master data.

Use
Supplier/Vendor master data is stored and archived in three different areas:

General data

FI data (for a speci c company code)

MM data (purchasing organization-speci c)

Structure
Tables

Archiving object FI_ACCPAYB is used to archive data from different tables. For more information about how to display the table
names for individual archiving objects, see Tables and Archiving Objects.

Reports

The following table shows the available reports:

Function Report

Write FI_ACCPAYB_WRI

Delete FI_ACCPAYB_DEL

Archiving Classes

To check which classes these are, call up transaction AOBJ, select your archiving object and choose Archiving Classes Used.

Programs

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

Integration
Displaying Archived Supplier/Vendor Master Data

To display individual documents for archiving object FI_ACCPAYB using the Archive Information System, you require an
information structure that has been created based on one of the following standard SAP eld catalogs:

SAP_FI_ACCPAYB1 (general supplier/vendor master data)

SAP_FI_ACCPAYB2 (supplier/vendor master data FI)

SAP_FI_ACCPAYB3 (supplier/vendor master data MM)

 Note
Please see sap note 1037272 for information about the following eld catalogs:

SAP_FI_ACCPAY_1 (supplier/vendor master data FI)

This is custom documentation. For more information, please visit the SAP Help Portal 27
 9/14/2022
SAP_FI_ACCPAY_2 (supplier/vendor master data SD)

Each information structure must be active and con gured correctly. For more information about information structures, see
Using the Archive Information System.

Prerequisites
The following prerequisites must be ful lled before supplier/vendor master data can be archived:

You must set the achiving ag in the master record. You can set this ag for a complete supplier/vendor or for individual
company codes or purchasing organizations.

1. Call up transaction BP and select a business partner by double-clicking on it.

2. On the Status tab, select Archiving Flag.

For more information, see Archiving and Deleting Supplier/Vendor Master Records.

A series of checks must be passed, for example, all dependent data must be archived and deleted from the database. For
more information, see Checks (FI-AP).

If business function ERP_CVP_DP_ILM_1 is active, the residence period must be over and the End of Purpose check
must have blocked the supplier/vendor.

If business function ERP_CVP_DP_ILM_1 is not active, the residence period must be over.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FI_ACCPAYB ILM object as part of SAP Information Lifecycle Management. You must
have activated the corresponding business functions to do this. The system then also shows the ILM Actions group box. You can
use these actions to carry out archiving, for example, where the retention periods stored in the Information Retention Manager
can be evaluated.

In transaction IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here
you can also see the available time references and which condition elds exist, and decide which of them shall be used in which
order to de ne your rule structure.

The following condition elds are available:

APPL_NAME - Application Name

APPL_RULE_VARIANT - Application Rule Variant

BUKRS - Company Code

KTOKK - Account Group

The following time references are available:

LAST_CHANGE_DATE - Last Changed On

START_RET_DATE- Start of Retention Period

For more information, see SAP Information Lifecycle Management.

Legal Holds

This is custom documentation. For more information, please visit the SAP Help Portal 28
 9/14/2022
It is possible to set a legal hold on this archiving object. For more information, see Setting Legal Holds.

De ning Write Variants

A write variant contains the parameters for the supplier/vendor master data that you want to archive.

When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

Dependencies of FI_ACCPAYB
For information on the archiving session order, see the Network Graphic for your archiving object in transaction SARA under
Goto → Network Graphic.

Enhancements for FI_ACCPAYB

The FI_ACCPAYB archiving object offers the following Business Add-Ins (BAdIs):

BAdI Description Used to

FI_ACCPAYB_CHECK Supplier Master Data Archiving: Implement additional checks for general
Additional Check of General data
Part

FI_ACCPAYB_CHECK_FI Supplier Master Data Archiving: Implement additional checks for FI data
Additional Check of FI Part

FI_ACCPAYB_CHECK_MM Supplier Master Data Archiving: Implement additional checks for MM data
Additional Check of MM Part

FI_ACCPAYB_WRITE Vendor Master Data Archiving: Enable archiving from additional tables for
Archive Additional Tables of general data
General Part

FI_ACCPAYB_WRITE_FI Vendor Master Data Archiving: Enable archiving from additional tables for
Archive Additional Tables of FI FI data
Part

FI_ACCPAYB_WRITE_MM Vendor Master Data Archiving: Enable archiving from additional tables for
Archive Additional Tables of MM MM data
Part

Variant Settings for Writing (FI-AP)

Use
When you schedule the write program, you must either enter an already existing variant or create a new one. The variant
contains the selection criteria for the supplier/vendor master data you want to archive.

Features
In the Data To Be Archived dropdown list box, you can choose the areas from which you want to archive master data. You can
choose from the following areas:

General Data
This is custom documentation. For more information, please visit the SAP Help Portal 29
 9/14/2022
The system archives only general data (not chart of account-speci c).

FI Data

The system archives only company code-speci c master data.

MM Data

The system archives only purchasing organization-speci c master data.

Document Selection Criteria

In the Account Payable Master Data frame, you can choose the following selection criteria:

Vendor

The system archives only the master data of accounts that fall within the range covered by the selection criteria you
enter.

Company Code

The system archives only the master data of company codes that fall within the range covered by the selection criteria
you enter.

This selection option is only offered if you are archiving FI data.

Purchasing Organization

The system archives only the master data of accounts that fall within the range covered by the selection criteria you
enter.

This selection option is only offered if you are archiving MM data.

Additional Selections and Options

In the Selections frame, you can make the following setting:

Minimum Number of Days in the System

You can use this parameter to determine the minimum amount of time that data must remain in the system before it
can be archived. At the time of archiving, the system then selects only the data that has been in the system at least the
amount of time entered under Minimum Number of Days in System.

By entering a value in this parameter, you can, for example, protect newly created data from being archived. When
checking against this parameter, the system uses the creation date of the master data records.

If you do not enter any value here, the system selects the data for archiving without taking any time restrictions into
account. This is especially signi cant if you have deactivated the Take Deletion Flag Into Account indicator. In this case,
you may unintentionally archive newly created data.

In the Options frame, you can make the following settings:

FI Link Validation Off

In nancial accounting, you have the option to link customers and suppliers/vendors. You create the link by lling in
speci c elds, such as the scal address, the dunning recipient, or the alternative payment recipient. With this setting
you can, for example, remove Customer A, to which a link exits from Customer B, from the database. The link from B
remains, even though A is archived.

In the standard, the FI link validation is always activated, meaning that all those customers or supplier/vendors for which
links exist, cannot be archived. If you want to archive these customers or suppliers/vendors anyway, you must either

This is custom documentation. For more information, please visit the SAP Help Portal 30
 9/14/2022
eliminate the link or switch the link validation off, using this setting.

This option is only relevant if you are archiving general data or FI data.

Take Deletion Flag Into Account

In the standard, this option is always set so that the deletion ag is always taken into account. This means that only data
for which the appropriate deletion ag has been set, can be archived.

If you deselect this option you can archive master data for which the deletion ag has not been set. The system runs
additional checks to determine whether or not the data is archivable. Only if these additional checks allow archiving the
deletion ag is set by the write program (if necessary) and the data is written to archive les. Note that through this
option you may run the risk of archiving newly created data. To prevent this situation, you can enter a value for Minimum
Number of Days in System, and in this way protect recently created data. Make sure you always check whether your
processes allow you to archive data without setting a deletion ag.

Additional Settings

The settings you make under Processing Options, for Log Settings, and Archiving Session Note are standard settings that are
also valid for other archiving objects. They are therefore described in the general archiving documentation under Variant
Maintenance for Archiving Jobs.

Checks (FI-AP)
Use

In order for the system to only archive data that is no longer needed in current business processes, this data must meet certain
conditions. To make sure the data to be archived meets these conditions, the write program performs several checks.

Master data is only eligible for archiving if you have set the deletion ag in the master record in each area.

When you archive general data for supplie/vendor master records, the system automatically checks whether the following
conditions have been met:

The deletion ag is set.

The supplier/vendor is not locked for deletion.

Dependent data of the following types no longer exists in the system:

Business partner of the supplier/vendor

Supplier/Vendor plants

Customer/Vendor links

Company code-speci c data (FI data)

Purchasing data (MM data)

Supplier/Vendor partner roles

Additional checks may be implemented in your system via the BAdI FI_ACCPAYB_CHECK.

When you archive FI data for supplier/vendor master records, the system automatically checks whether the following conditions
have been met:

The deletion ag is set.

This is custom documentation. For more information, please visit the SAP Help Portal 31
 9/14/2022
The supplier/vendor is not locked for deletion.

Dependent data of the following types no longer exists in the system:

Transaction gures

Special general ledger transaction gures

Open items

Cleared items

Store items

Customer/Vendor links

Parked documents

Additional checks may be implemented in your system via the BAdI FI_ACCPAYB_CHECK_FI.

When you archive MM data for supplier/vendor master records, the system automatically checks whether the following
conditions have been met:

The deletion ag is set.

Dependent data of the following types no longer exists in the system:

Purchasing documents

Purchasing info records

Supplier/Vendor partner roles

Additional checks may be implemented in your system via the BAdI FI_ACCPAYB_CHECK_MM.

Archiving FI Bank Master Data (FI-GL, FI-AR, FI-AP, FI-BL)

De nition
Bank master data is archived and deleted using archiving object FI_BANKS.

Use
Bank master data is only archived if it is no longer used within the nancial accounting component and in other components. In
the detail log of the write program, you can double-click a bank master record to display a table and the table key of an example
data record that still references the bank master record and therefore prevents this bank master record from being archived.
For more information about the logs generated during archiving, see Logs .

Structure
Tables

Archiving object FI_BANKS is used to archive data from different tables. For more information about how to display the table
names, see Tables and Archiving Objects .

Programs

This is custom documentation. For more information, please visit the SAP Help Portal 32
 9/14/2022
The following programs are delivered for FI_BANKS.

Program Function

FI_BANKS_WRI Write

FI_BANKS_DEL Delete

Integration

 Note
You can use archiving object FI_BANKS in Information Lifecycle Management . You must have activated the corresponding
business functions to do this. The system then also shows the ILM Actions group box. You can use these actions to carry out
archiving, for example, where the retention periods stored in the Information Retention Manager can be evaluated.
Additionally, you can create snapshots (copies) of data or destroy data that matches the requirements. For more
information, see ILM Enhancements for Data Archiving , ILM Actions in the Write Program .

Displaying Archived Bank Master Data

To display archived bank master data using the Archive Information System , you require an information structure that has been
created based on the following standard SAP eld catalog:

SAP_FI_BANKS_01 (bank master data)

The information structure must be active and con gured correctly before it can be used.

For more information about information structures, see Using the Archive Information System .

Variant Settings for Writing (FI-GL, FI-AR, FI-AP, FI-BL)

Use
When you schedule the write program, you must enter either an already existing variant or create a new one. The variant
contains the selection criteria for the electronic bank data you want to archive.

Features
Document Selection Criteria

Under Bank Master Data you enter the following data:

Bank Country

The system archives only those banks from the country or countries you specify here. If you do not enter a country, the
system archives bank master data for every country.

Bank Key

The key under which the bank data is stored in each country. Normally this key is the bank number; in some countries this
can also be the bank account number.

Further Restrictions

This is custom documentation. For more information, please visit the SAP Help Portal 33
 9/14/2022
Under Restrictions you can further restrict the selection of documents to be archived:

Only with Deletion Indicator

You can set a deletion indicator in the bank’s master record. At the time of archiving banks, you then have the option of
deleting all the banks that are no longer referenced, or of deleting only those for which the deletion indicator was
previously set. For the latter you must activate the deletion indicator.

Minimum Number of Days in the System

All banks that have been in the system for at least the number of days indicated here will be considered to be archivable.
The reference for the archivability of the bank master records is the their entry date.

Additional Settings

The settings you make under Processing Options, Logs and Archiving Session Note are settings that are offered by other
archiving objects. These are described in the general archiving documentation under Maintaining Variants for Archiving Jobs .

See also:

Creating Archive Files

Archiving FI Check Data (FI-AR, FI-AP, FI-BL)

De nition
Checks are archived, deleted, and reloaded using archiving object FI_SCHECK.

 Note
This archiving object was revised in the course of a project to standardize and optimize data archiving. You can use the
standardized archiving object by activating the business function Data Archiving:Use Standardizing Archiving Objects
(technical name DA_ARCHOBJ_STANDARD_1). For more information, see the business function documentation in the Switch
Framework (transaction SFW5) under Data Archiving:Standardizing Archiving Objects .

You can also use the archiving object in the context of Information Lifecycle Management. You must have set up the relevant
business functions to do this. The system then also shows the ILM Actions frame. You can use these actions to carry out
archiving, for example, where the retention periods stored in the Information Retention Manager can be evaluated.
Additionally, you can create snapshots (copies) of data or destroy data that matches the requirements. For more
information, see the LM Actions in the Write Program section of ILM Enhancements in Data Archiving.

Use
Only checks that have been either cashed or voided can be archived; in other words, the cashing or voiding must have taken
place a certain number of days in the past in order to carry out archiving. You enter the number of days in thesystem in variant
maintenance for the archiving session

Structure
Tables

The archiving object FI_SCHECK is used to archive data from different tables. To nd out how to display the table names, see
Tables and Archiving Objects.
This is custom documentation. For more information, please visit the SAP Help Portal 34
 9/14/2022
Function/report assignment

Functionality Report

Write RFCHKA00

Delete RFCHKA10

Reloading Data from the Archive RFCHKA20

Displaying Individual Objects Using SAP AS

To display individual objects for the archiving object MM_SCHECK using the Archive Information System, you require an
information structure that has been created based on the standard eld catalog SAP_FI_SCHECK_1. The info structure must be
active and lled.

For more information about information structures, see Using the Archive Information System.

Creating Archive Files - Check Data (FI)

Procedure

1. Choose General Ledger , Accounts Receivable , Accounts Payable or Banks Periodic processing Archiving Checks
then Archive .

The Archive Administration: Create Archive Files screen appears.

2. Enter a variant name and choose Maintain .

3. De ne the variant by specifying the following selection criteria:

Paying company code

House bank

Account ID

Check number

Payroll checks indicator

If you set this indicator, the system selects Human Resources checks only. If it is not set, the system selects
checks from Financial Accounting only.

4. Having entered the selection criteria above, you can now maintain the following program parameters where necessary:

Number of days in the system

Note that only cashed or voided checks can be archived. Here you can specify a minimum number of days a check
must have been in the system before if can be archived.

Key date

The system uses this date to determine if a check can be archived. Unless you specify otherwise, today’s date will
be adopted.

Test run

If you start the archiving program in test mode, archiving is only simulated. The system neither writes data to
archive les nor deletes data from the database.

This is custom documentation. For more information, please visit the SAP Help Portal 35
 9/14/2022
Detail log

The detail log records information on each archived object. For more information, see Logs .

5. Enter an archive description.

Archiving run memo

A short text added to help identify the archiving session within archive administration.

6. Choose Back .

The system asks you whether you want to save your values. To save your data choose Yes .

The ABAP: Save variant attributes screen appears, and you enter a description of your variant in the Description eld.

7. Save the variant by choosing Save . To return to the Archive Administration : Create Archive Files screen choose Back .

8. Maintain the Start date and the Spool parameters for the archiving session.

9. Once you have maintained the above selection criteria, start date, and spool parameters, you can execute the archiving
session by choosing Execute .

To display the status of the jobs you created, chooseGoto Job overview.

For more information see Variant Maintenance for Archiving Jobs .

Reloading Archive Files - Check Data (FI)

Prerequisites
Before reloading check data, you must ensure that the appropriate archive les are on the local drive so that the program can
access them.

In check lot management, you can view information on the archiving of a check lot. To display this information, proceed as
follows: From the Implementation Guide (IMG) for Financial Accounting choose Accounts Receivable and Accounts
Payable Business Transactions Outgoing Payments AutomaticOutgoing Payments Payment Media Check Management.

Individual check lots are indicated as Partially Archived or Archived as appropriate. A check lot is indicated as Archived if the
system has written all the checks to the archive le and deleted them from the database. A check lot is indicated as Partially
Archived if some checks remain in the system after the deletion program is run.

The system assigns the indicator to the check lot when checks have been deleted for the rst time after an archiving session,
and it updates the indicator with each additional deletion or reload.

Procedure
1. Choose General Ledger , Accounts Receivable , Accounts Payable or Banks Periodic
processing Archiving ChecksthenGoto Reload.

The Archive Administration: Create Archive Files screen appears.

2. Enter a variant name and choose Maintain .

The selection screen for maintaining variants appears.

3. The number of documents to be reloaded is determined using the following selection criteria:

This is custom documentation. For more information, please visit the SAP Help Portal 36
 9/14/2022
Paying company code

The system only reloads check data posted by the company codes you specify.

House bank

The system only reloads check data for checks paid by the house bank you specify.

Account ID

The system only reloads check data for checks paid from the accounts you specify.

Check number

The system only reloads the check data within the number range you specify.

Payroll checks

If you set this indicator, the system selects Human Resources checks only. If it is not set, the system selects
checks from Financial Accounting only.

4. Enter the appropriate selection criteria and, if necessary, activate the following elds:

Test Run

If you start the reload program in test mode, the system only simulates the reload run. The system does not
change data in the database or in the archive.

Detail Log

The detail log records information on each reloaded object. For more information, see Logs .

5. Choose Back .

The system asks you whether you want to save your values. To save your data choose Yes .

The ABAP: Save Attributes of Variant screen appears, and you enter a description of your variant in the Description eld.

6. Save the variant by choosing Save . To return to the Archive Administration : Reload Archive Files screen choose Back .

7. Make the following settings:

Select the archive from which data is to be reloaded

Enter the start date for the reload run

Enter the spool parameters for the reload run

8. Once you have entered your selection criteria and have set the archive selection, start date, and spool parameters,
choose Execute .

To display the status of the jobs you created, c hoose Goto Job Overview.

For more information see Variant Maintenance for Archiving Jobs .

Archiving Payment Requests

De nition
Payment requests are archived and deleted using the FI_PAYRQ archiving object.

This is custom documentation. For more information, please visit the SAP Help Portal 37
 9/14/2022

Use
You can only archive cleared payment requests. These can be either cancelled payment requests or payment requests for which
a payment was made. The clearing must have taken place a certain number of days beforehand in order for a payment request
to be archivable. You enter the Minimum number of days since clearing when maintaining the variants for the write session.

Structure
Tables

You can archive data from tables PAYRQ, PAYRQP and PAYRQT. Using the archiving object FI_PAYRQ. To nd out how to display
the table names, see Tables and Archiving Objects .

Programs

Archiving object FI_PAYRQ comes with the following programs:

Function Report

FI_PAYRQ_WRI Writing

FI_PAYRQ_DEL Deleting

Integration
Displaying Archived Payment Requests

To display archived payment requests using the Archive Information System , you need an archive information structure that
was created based on the following standard eld catalog:

SAP_FI_PAYRQ_1 (payment requests)

An infostructure is only usable if it has been activated and built.

For more information about archive information structures, see Using the Archive Information System .

Variant Settings for Writing

Use
When you schedule the write program you must either enter an existing variant or create a new one. The variant contains the
selection criteria for the payment request you want to archive.

Features
Document Selection Criteria

Under Payment Requests you can enter the following selection criteria:

Company Code

The system archives only those payment requests that were posted under the company code you enter.

This is custom documentation. For more information, please visit the SAP Help Portal 38
 9/14/2022
Key Number

The system archives only those payment requests that fall within the interval you enter.

Further Restrictions

Under Selections you can further restrict the selection of the documents to be archived:

Customer items

The system archives payment requests for customers.

Vendor items

The system archives payment requests for vendors.

G/L account items

The system archives payment requests for G/L accounts.

Minimum Number of Days Since Clearing

The system archives only payment requests that have been in the system longer than the number of days indicated.

The settings you make under Processing Options, Logs and Archiving Session Note
are settings that are offered by other archiving objects. These are described in the
general archiving documentation underMaintaining Variants for Archiving Jobs.
See also:

Creating Archive Files

Archiving Electronic Bank Data (FI-BL)

De nition
Electronic bank data is archived and deleted using archiving object FI_ELBANK.

Use
You can archive only electronic bank data that has been completely posted. Electronic bank data is completely posted when
update 1 and 2 have been executed, meaning that elds VB1OK and VB2OK in table FEBKO have the value "X".

Structure
Tables

Archiving object FI_ELBANK is used to archive data from different tables. For more information about how to display the table
names, see Tables and Archiving Objects .

This is custom documentation. For more information, please visit the SAP Help Portal 39
 9/14/2022
Programs

The following programs are delivered for FI_ELBANK.

Program Function

FI_ELBANK_WRI Write

FI_ELBANK_DEL Delete

Integration

 Note
You can use archiving object FI_ELBANK in Information Lifecycle Management . You must have activated the corresponding
business functions to do this. The system then also shows the ILM Actions group box. You can use these actions to carry out
archiving, for example, where the retention periods stored in the Information Retention Manager can be evaluated.
Additionally, you can create snapshots (copies) of data or destroy data that matches the requirements. For more
information, see ILM Enhancements for Data Archiving , ILM Actions in the Write Program .

Displaying Archived Electronic Bank Data

To display archived electronic bank data using the Archive Information System , you require an information structure that has
been created based on the standard SAP eld catalog SAP_FI_ELBANK_1. To use the Document Relationship Browser (DRB) ,
you require an information structure that has been created based on the standard SAP eld catalog SAP_FI_ELBANK_2.

The information structure must be active and con gured correctly before it can be used.

For more information about information structures, see Using the Archive Information System .

Variant Settings for Writing (FI-BL)

Use
When you schedule the write program, you must enter either an already existing variant or create a new one. The variant
contains the selection criteria for the electronic bank data you want to archive.

Prerequisites
You can only archive electronic bank data that has been completely posted.

Features
Document Selection Criteria

Under Electronic Bank Details you can enter the following data:

ID

The system only archives electronic bank data that falls within the interval you enter.

Further Restrictions

This is custom documentation. For more information, please visit the SAP Help Portal 40
 9/14/2022
Under Selections you can further restrict the selection of electronic bank data to be archived by using the following criteria:

Company Code

The system only archives electronic bank data that was posted within the company code you enter.

Application

The system only archives electronic bank data from the applications you enter.

To Statement Date

The system archives only electronic bank data that falls within the date interval you enter.

Additional Settings

The settings you make under Processing Options, Logs and Archiving Session Note are settings that are offered by other
archiving objects. These are described in the general archiving documentation under Maintaining Variants for Archiving Jobs .

See also:

Creating Archive Files

Archiving Cash Journal Documents (FI-BL)

De nition
You can archive and delete cash journal documents using the FI_TCJ_DOC archiving object.

Use
You can only archive completely posted, deleted, and reversed cash journal documents. However, as soon as your selection
includes a cash journal document that does not ful ll this criteria, all other documents that belong to this cash journal and the
same company code cannot be archived either. Furthermore, if at least one check of a check lot is selected for archiving and is
archivable, then all documents within this check lot must fall inside the selected range of documents. If not, then all the
documents of the cash journal to which the check belongs, are not archivable for that particular company code. The system
checks this during the archiving session.

Structure
Tables

You can archive data from different tables using the archiving object FI_TCJ_DOC. For information on how to display the table
names for this archiving object, see Tables and Archiving Objects .

Programs

The following programs are offered with FI_TCJ_DOC:

Program Function

Writing FI_TCJ_DOC_WRI

Deleting FI_TCJ_DOC_DEL

This is custom documentation. For more information, please visit the SAP Help Portal 41
 9/14/2022

Integration
Displaying archived cash journal documents

To display archived cash journal documents using the Archive Information System , you need an archive information structure
that was created based on the following eld catalog provided by SAP:

SAP_FI_TCJDOC_1

An infostructure is only usable if it has been activated and built.

For more information about archive information structures, see Using the Archive Information System .

Variant Settings for Writing (FI-BL)

Use
When you schedule the write program, you have to enter an existing variant or create a new one. The variant contains the
selection criteria for the cash journal documents you want to archive.

Features
Document Selection Criteria

Under Cash Journal Documents you can enter the following selection criteria:

Company Code

The system archives only those cash journal documents that were posted under the company codes you enter.

Cash Journal Number

The system archives only the cash journal documents that lie within the interval you enter.

Further Restrictions

Under Selections you can further restrict the selection of documents to be archived, using the following selection criteria:

To Posting Date

The system archives only those documents that were entered by bookkeeping or accounting by the date you enter.

Minimum Number of Days in the System

The system archives only the cash journal documents that have been in the system for at least the Minimum Number of
Days in the System you enter. The check is carried out for the eld TCJ_DOCUMENTS-POSTING_DATE.

Additional Settings

The settings you make under Processing Options , Logs and Archiving Session Note are settings that are offered by other
archiving objects. These are described in the general archiving documentation under Maintaining Variants for Archiving Jobs .

See also:

Creating Archive Files

This is custom documentation. For more information, please visit the SAP Help Portal 42
 9/14/2022

Archiving Reorganization Plans

Use
Data archiving is used to free up space on your production system by removing data that you no longer require for daily
business but that needs to be retrievable for tracking purposes.

The following archiving object is provided for the reorganization:

Reorganization Plan (FAGL_REORG).

When you archive a reorganization plan, all related objects (such as assignment tables and object lists) are archived.

Integration
To archive reorganization plans, the system uses the standard archiving tools.

For general information about data archiving, see Data Archiving (CA-ARC).

Prerequisites
For you to be able to archive a reorganization plan, the following criteria must be met:

The reorganization plan has been closed.

The residence time needs to prevent reorganization plans from being archived prematurely. The residence time is the
amount of time that needs to have elapsed before a reorganization plan can be archived. The residence time is
calculated on the basis of the reorganization date. The residence time is expressed in days.

In the Customizing settings for the Reorganization, you have de ned the residence times for reorganization plans in the
activity Basic Settings Archiving: De ne Residence Times .

The residence time for the reorganization plan has elapsed.

Features
Archiving

You perform archiving in transaction SARA (in the SAP Easy Access menu under Tools Archiving Archive Data ). You need to
perform the following two steps:

1. Archive Data (Write Program)

In this activity, the system uses write programs to write to the archive data that can be archived.

In the selection screen for the write program, you specify selection criteria (such as the reorganization plan type and the
reorganization date). From the selected quantity, the write program only considers reorganization plans that meet the
prerequisites described above.

The write program creates an archive le in accordance with the archive administration settings that you have made. In
the standard system, the write program does not delete the data from the database. This means that, after the write
program has been executed, the data remains in the archive and in the database until the deletion program has been
run on the basis of this archive le.

2. Delete Data from the Database

This is custom documentation. For more information, please visit the SAP Help Portal 43
 9/14/2022
The deletion program reads the archived data from the selected archive le. The system only deletes data from the
database when that data has been read successfully from the archive le.

Deleted reorganization plans are subsequently no longer displayed in the input helps. Moreover, the system prevents
any objects with an identical key from being created again.

Reloading Archived Data to the Database

At a later point in time, you may nd that you need to view data from the archive (for example, for auditing purposes). For such
cases, you can use a program to reload data.

Displaying Archived Reorganization Plans

You also have the option of displaying archive data simply as follows:

You can display archived table entries in the Archive Explorer in the Archive Information System (transaction SARI). The
prerequisite for this is that you have created at least one corresponding archive information structure.

Activities
To archive reorganization plans, perform the required steps in transaction SARA:

1. Use the write program to archive reorganization plans.

2. Delete from the database the data relating to those reorganization plans.

Additional Information
To remove reorganization plans that have been created by mistake in the system and that are not required, you simply delete
them without archiving them. Reorganization plans that need to be deleted must not contain any data. You delete
reorganization plans by selecting them in the reorganization plan overview and choosing the Delete pushbutton.

Archiving Payment Release List Items Using FI_FPRL

You can use archiving object FI_FPRL to archive and delete payment release list items together with their dependent logs and
warnings.

Tables

FI_FPRL archives data from several tables. To check which tables these are, call up transaction SARA, enter the archiving
object, and choose Database Tables. You can display the relevant tables in the lower part of the screen.

Please note the following characteristics:

Entries from table FPRL_ITEM are archived and deleted.

Entries from table FPRL_LOG that have a corresponding entry in table FPRL_ITEM are archived and deleted. Entries
that exist in table FPRL_LOG only, however, are deleted directly without being archived rst.

Entries from table FPRL_WARNINGS are never archived, but deleted directly.

Programs

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

This is custom documentation. For more information, please visit the SAP Help Portal 44
 9/14/2022

Prerequisites
The following prerequisites must be ful lled before a payment release list item can be archived:

The payment release list item must be in status Refused, Paid or Exception.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FI_FPRL ILM object as part of SAP Information Lifecycle Management. In transaction
IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here you can also
see the available time references and which condition elds exist, and decide which of them shall be used in which order to
de ne your rule structure.

The following condition elds are available:

Status (Item Status ID)

The following time references are available:

LAST_CHANGE_DATE (Last Changed On)

For more information, see SAP Information Lifecycle Management.

De ning Write Variants

When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

A write variant contains the parameters for the payment release list items that you want to archive.

SAP delivers the following parameters:

Company Code

Specify the company code under which the payment release list items were posted.

Status

Specify the status of the payment release list items to be archived (possible status values: refused, paid, exception)

Minimum Number of Days

The system only archives payment release list items with the above listed status that have not been changed in the
system for more than the number of days indicated.

Dependencies of FI_FPRL
For information on the archiving session order, see the Network Graphic for your archiving object in transaction SARA under
Goto → Network Graphic.

Enhancements for FI_FPRL

The FI_FPRL archiving object offers the following Business Add-Ins (BAdIs):

BAdI / User Exit Description Used to

This is custom documentation. For more information, please visit the SAP Help Portal 45
 9/14/2022

BAdI / User Exit Description Used to

FI_FPRL_CHECK Archiving of FI_FPRL: Additional Checks You can use this BAdI to carry out additional
checks for the archiving of payment relese
list items.

FI_FPRL_WRITE Archiving of FI_FPRL: Additional Tables You can use this BAdI to archive additional
table entries for payment release list items.

Displaying Payment Release List Items Archived with FI_FPRL

To display archived payment release items using the Archive Information System you need an archive information structure that
was created based on the following standard eld catalog:

SAP_FI_FPRL_001 (Payment Release List Items)

Archiving Temporary FI Data Using FI_TEMP

You can use archiving object FI_TEMP to archive temporary FI data.

Tables

FI_TEMP archives data from the ACDOCTEMP table. To check which tables these are, call up transaction SARA, enter the
archiving object, and choose Database Tables. You can display the relevant tables in the lower part of the screen.

Programs

Write Program: FINS_ARCH_TEMP_WRI

Delete Program: FINS_ARCH_TEMP_DEL

Reload Program: FINS_ARCH_TEMP_REL

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

Prerequisites
There are no prerequisites. You can restrict archiving using the selection criteria.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FI_TEMP ILM object as part of SAP Information Lifecycle Management. In transaction
IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here you can also
see the available time references and which condition elds exist, and decide which of them shall be used in which order to
de ne your rule structure.

The following condition elds are available:

Company Code

Country from the Company Code

Application that creates the temporary FI data, such as test results of a balance carryforward run.

This is custom documentation. For more information, please visit the SAP Help Portal 46
 9/14/2022
The following time references are available:

End of Year

For more information, see SAP Information Lifecycle Management.

Performing Application-Speci c Con guration

There is no application-speci c con guration.

De ning Write Variants

When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

A write variant contains the parameters for the temporary FI data that you want to archive.

SAP delivers the following parameters:

Application

The application that created the data, such as a balance carryforward.

ID

The ID of the data, such as the balance carryforward ID.

The following elds can be used to restrict archiving based on business relevant entities.

Ledger

Company Code

Fiscal Year

Posting Period

Dependencies of FI_TEMP
There are no dependencies.

Displaying Temporary FI Data Archived with FI_TEMP

You can display archived data with transaction SARI based on the eld catalog SAP_FI_TEMP and the archiving infostructure
SAP_FI_TEMP01.

Archiving Deferred Summarization Using FI_DEFSUM

You can use archiving object FI_DEFSUM to archive deferred Summarization.

Tables

FI_DEFSUM archives data from the ACDOCD table. To check which tables these are, call up transaction SARA, enter the
archiving object, and choose Database Tables. You can display the relevant tables in the lower part of the screen.

This is custom documentation. For more information, please visit the SAP Help Portal 47
 9/14/2022
Programs

Write Program: FINS_ARCH_DEFSUM_WRI

Delete Program: FINS_ARCH_DEFSUM_DEL

Reload Program: FINS_ARCH_DEFSUM_REL

To nd out which programs this archiving object offers, call up transaction AOBJ and double-click on your AO.

Prerequisites
The following prerequisites must be ful lled before a deferred summarization run can be archived:

The data has existed for a length of time that is equal to or greater than the residence time that was assigned to it. As a
reference, the current period of material management, for each company code, is used.

ILM-Related Information for the Archiving Object

You can use this archiving object with the FI_DESUM ILM object as part of SAP Information Lifecycle Management. In
transaction IRMPOL, you can create policies for residence or retention rules, depending on the available policy category. Here
you can also see the available time references and which condition elds exist, and decide which of them shall be used in which
order to de ne your rule structure.

The following condition elds are available:

Company Code

Country from Company Code

Plant

The following time references are available:

Posting Date with Offset

End of Year

End of Fiscal Year

For more information, see SAP Information Lifecycle Management.

Legal Holds
It is possible to set a legal hold on this archiving object. For more information, see Setting Legal Holds.

Performing Application-Speci c Con guration

Before you can use the FI_DEFSUM archiving object, you must rst check in the settings under Financial Accounting Global
Settings Document Summarization Activate Deferred Summarization Deferred Summarization . The rst residence period
de nes when the data is moved into the ACDOCD table by deferred summarization. The second residence period de nes when
these entries can be archived.

De ning Write Variants

This is custom documentation. For more information, please visit the SAP Help Portal 48
 9/14/2022
When you schedule the archiving run, you must enter an existing variant or create a new one. You can do so in transaction
SARA.

A write variant contains the parameters for the deferred summarization that you want to archive.

SAP delivers the following parameters:

Ledger

Company Code

Key Date

The key date sets the reference day for the residence time. By default the current day is used.

Dependencies of FI_DEFSUM
There are no explicit dependencies for archiving object FI_DEFSUM. This includes archiving object FI_DOCUMNT, which can be
archived independently.

 Note
Deferred summarization can be run only after:

A document has been posted and it has existed for a length of time equal to or greater than the residence time that
was assigned to it

The data has been moved to ACDOCD.

Displaying Deferred Summarization Archived with FI_DEFSUM

Archived data cannot be displayed in business transactions. However, it is possible to display archived data in transaction SARI
based on the eld catalog SAP_FI_DEFSUM and archiving infostructure SAP_FI_DEFSUM01.

Archiving Asset Data (FI-AA)

De nition
The archiving object AM_ASSET is used for archiving asset data in Asset Accounting (FI-AA). This object contains all master
data, transactions, and values that are associated with an asset in the database. However, it does not contain any control
tables (Customizing).

 Note
You can use archiving object AM_ASSET in the context of Information Lifecycle Management (ILM). You must have activated
the relevant business functions to do this. The system then also shows the ILM Actions frame. You can use these actions to
carry out archiving, for example, where the retention periods stored in the Information Retention Manager can be evaluated.
Additionally, you can create snapshots (copies) of data or destroy data that ful lls the requirements for this.

For more information, see the ILM Actions in the Write Program section of ILM Enhancements in Data Archiving.

Structure
This is custom documentation. For more information, please visit the SAP Help Portal 49
 9/14/2022
Archiving object Fixed Asset has the following table structure:

ANLA Technical information on the main asset number

ANLH Asset Master Data

ANLT Language-dependent texts

ANLV Insurance entries

ANLW Base insurable value

ANLZ Time-Dependent Data

ANLB Depreciation area speci cations

ANLC Annual values

ANLP Depreciation posting values

ANEK Transaction header

ANEP Transactions

ANEA Proportional values

ANEV Information on down payments

ANLI Assignment CO-Object/AuC for investment measures

ANLE Proof of origin

COBRA Settlement rule header (for AuC)

CORB Settlement rules (for AuC)

Asset long texts and change documents also belong to the archiving object xed asset.

Subobjects
Attachments are archived as a whole, i.e. with all the master data (table ANLH), transactions (ANEP), annual values (ANLC),
proportional values (ANEA), depreciation posting values (ANLP), and so on.

It is not possible to archive line items separately.

Dependent Objects
Archiving object AM_ASSET is always archived together with object AM_STEUER. This object contains control tables that are
made available for the further development of asset archiving that may occur later on. The technical settings for archiving
object AM_STEUER (such as the logical le path) must therefore be maintained in asset archiving.

Assets under construction for investment measures can only be deleted when the corresponding Controlling (CO) object
(internal order, WBS element) is deleted.

 Note
Note the sequence in which the archiving sessions must be carried out. To obtain an overview choose Goto Network
graphic .

This is custom documentation. For more information, please visit the SAP Help Portal 50
 9/14/2022

Changes Brought About by the Introduction of the Universal Journal Entry

The universal journal entry was introduced with release SAP Simple Finance 1503 or SAP S/4HANA, On-Premise-Edition 1511. As
a result, the following changes apply when archiving assets:

The system generally archives in the old table structures. This enables compatible reporting if you use logical database
ADA for reporting purposes. This means that reporting can take place on the same data structures.

It is no longer possible to archive subobjects separately: xed assets now have to be archived completely.

You can use delete program (RAARCH02) to delete data from tables Statistical Line Items in Asset Accounting
(FAAT_DOC_IT), Planned Depreciation and Revaluations (FAAT_PLAN_VALUES), Year-Dependent Attributes for
Depreciation (FAAT_YDDA).

The Data Retention Period (FI-AA)

 Note
The data retention period is the only archiving test criterion.

Standard Retention Period

Complete asset

The earliest that a complete asset can be got rid of is when it is deactivated and as such its depreciation areas no longercontain
any values. By default, the minimum retention period is one year, starting from the end of the deactivation year.

Customer-Speci c Retention Periods

In Customizing for Asset Accounting under Master Data, you can also de ne an individual retention period for complete xed
assets, in addition to the standard retention period mentioned above. The actual minimum retention period is the sum of this
individual retention period and the standard retention period of one year.

 Example

Deactivation of the asset: 1.3.YYYY

Standard retention period: 1 year

Customer-speci c retention period: 1 year

The asset can be reorganized in the scal year YYYY+3 at the earliest. The number 3 is determined as follows:

Year following the deactivation year + standard retention period + customer-de ned retention period

 Note
An individual analysis of individual assets that are to remain in the system for longer than the de ned minimum retention
time is not possible (exception: Assets with history management).

Retention Period for Capital Investment Measures

This is custom documentation. For more information, please visit the SAP Help Portal 51
 9/14/2022
Assets under construction for investment measures can only be deleted when the corresponding Controlling (CO) object
(internal order, WBS element) is deleted.

Test Criteria (FI-AA)

The Data Retention Period (FI-AA) is the only test criterion.

Authorizations (FI-AA)

Use
To archive data in Asset Accounting, you need the following authorizations:

Authorization Objects
The following authorization objects are relevant:

Authorization object S_ARCHIVE

Activity 01 (create archive les, reloading, deleting, and reading)

Application area: FI

For archiving objects AM_ASSET, AM_STEUER:

Authorization object A_PERI_BUK with the following values:

Activity 37 (archiving)

Activity 38 (reload)

Additional Information

For general information about authorizations for archiving, see Authorization Check.

Archive, Delete, and Reload Asset Data (FI-AA)

In principle, archiving in Asset Accounting is divided into two steps:

1. Archiving objects with related table entries into an archive le and marking the records to be deleted (Create Archive).

2. Comparison of the generated archive le with the speci ed data records and deletion of the marked data records from
the database (Edit Archive).

However, note that after generating an archive, the deletion program can be triggered automatically. In this case archiving and
reorganization are completed in one step. The relevant control ag is a customizing parameter for the archiving run.

Further transactions enable the reloading (Reload Archive) and viewing of log information about the executed archiving
sessions (Manage Archive).

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 52
 9/14/2022
If there is an error in the archiving run, the system ends the archiving transaction without archiving any assets. This ensures
that no data is lost. You can correct the error and restart the archiving run.

Additional Information
For more information, see Archiving Procedure: Overview .

Archiving Totals Records and Line Items (FI-SL)

De nition
Archiving object FI_SL_DATA for archiving totals records and line items in the application component Special Purpose Ledger
(FI-SL)

Use
When you choose Accounting Financial Accounting Special Purpose Ledger Periodic Processing Archiving , “FI_SL_DATA” is
displayed automatically as the default value, hence you do not need to set this value. If you access Archive Administration from
elsewhere in the system, you need to enter the name of the archiving object.

You can use archiving object FI_SL_DATA to archive or delete line items and totals records according to your own speci c
requirements. For example, if you database contains a large number of journal entries, you can archive these records regularly.
If your system has enough storage space, you need only archive the journal entries once per scal year.

The archiving object also enables you to evaluate archived data. Reloading archived data is also possible, although this should
only be done in exceptional cases.

After you have performed a local currency changeover in your system it is no longer possible to reload data archived before this
changeover.

 Note
Because the scal year is part of the totals record key, you cannot archive totals records during the current scal year. If, for
example, you were to archive a totals record in May and then make new system postings in June, a new totals record would
be created. This would lead to inconsistencies with the totals record that has already been archived.

Structure
Tables

The archiving object FI_SL_DATA is used to archive data from different tables. In transaction “DB15”, you can nd out which
tables are affected. See Tables and Archiving Objects.

Programs

The write program supports the ADK interruption function, which allows you to interrupt the write phase and restart it at a later
point in time. For more information about this function, see Interrupting and Continuing Archiving Sessions.

For general information about data archiving, see Introduction to Data Archiving (CA-ARC) .

This is custom documentation. For more information, please visit the SAP Help Portal 53
 9/14/2022

Technical Data (FI-SL)

Storage Requirements

To estimate the amount of memory needed to archive summary and line item records, use the following guidelines:

1 Summary Record 1 Line Item 1 Plan Line Item

Estimated amount of memory 800 300 800

required in database in bytes

The data is compressed during archiving. The compression factor depends on the data record length and content. A data record
containing lots of empty elds is compressed to a smaller size than a record that is completely lled.

500 Plan Line Items 5000 Plan Line Items

Before archiving 0.4 MB 4 MB

After archiving 0.91 MB 1.10 MB

Thereof: 0.89 MB 0.89 MB

Storage requirement for header data 0.02 MB 0.21 MB

information

Storage requirement for remaining data

The 0.91MB of memory space required in the database after archiving 500 plan line items is made up of 0.89MB for the header
data and 0.02MB for the remaining data after compression. The storage requirement for the header data information after
archiving 5000 plan line items is the same as for the archiving of 500 plan line items.

The storage requirement for header data information per le depends on the number of FI-SL tables and their record lengths.
Regard the data in the example as a guideline for the possible scale of the data.

Life

The time needed to run the archiving program depends on the number of records you want to archive and the system load and
performance.

On average, the write program processes 1-2 million records per hour. On average, the deletion program processes 1 million
records per hour. The values are guidelines. For precise information about runtimes and storage requirements for the archive
le, see the test mode for the write or deletion programs.

Application Customizing (FI-SL)

Use
In addition to maintaining the Customizing settings for the FI_SL_DATA archiving object, you can also perform the following
archiving activities in Customizing for the Special Purpose Ledger as required:

Select existing Report Writer/Report Painter reports and customer programs to be read from the archive or the
database.

This is custom documentation. For more information, please visit the SAP Help Portal 54
 9/14/2022
Generate reports to read archived data and/or database data for FI-SL ledgers

Regenerate coding for the archiving programs

 Note
Data archived before a local currency changeover is displayed in the original currency. A translation is not carried out
in the background.

Features
De ne Report Groups and Programs for Archive Reporting

If you want to output Report Writer/Report Painter reports to evaluate archived data and/or databases, you have to assign the
corresponding report groups to the archiving object FI_SL_DATA. You can specify any of the report groups that you have created
in reporting. The report groups 0M11 and 0M12 are delivered with the standard system and contain reference reports for table
GLFUNCT. You can then call up these report groups from the archive administration.

 Note
You do not have to specify the archive report programs that you generated in Customizing (see next section). The system
automatically includes these programs so that you can execute them in archive reporting.

 Note
You can also assign your own programs that read archived data to the archiving object FI_SL_DATA. You can then call up
these programs from the archive administration (transaction SARA).

Generating Sequential Read Programs

SAP provides ABAP read programs for some of the standard tables delivered with the Special Purpose Ledger application
component (for example, GLT1, GLS1, GLP1, GLFUNCT, GLFUNCA, GLFUNCP). These programs enable you to output totals
reports and actual and plan line item reports that evaluate archived data and/or database data.

If you have modi ed the standard tables or want to use standard tables for which there are no generated programs, you can
generate the read programs.

If you have installed and activated your own database tables in the Special Purpose Ledger, you can also generate read
programs for evaluating archived and/or database data. You can then call up these programs from the archive administration.

 Note
For read programs generated in this way, only sequential archive access is possible. The archive les are read completely.
You cannot access the archive via the Archive Information System (AS).

Regenerating Coding for Archiving Programs

Before you create an archive and execute the archiving program, you can regenerate the code for the archiving programs in
Customizing for the Special Purpose Ledger .

 Note
You only need to regenerate the coding before you start to archive if syntax errors have occurred in the archiving programs.
Coding is generated automatically when you rst install the Special Purpose Ledger application component (table group
installation). It is also advisable to regenerate coding if you have changed your system setup.

This is custom documentation. For more information, please visit the SAP Help Portal 55
 9/14/2022
You must not regenerate coding when other programs for the archiving object FI_SL_DATA are running.

Activities
You can call up the above functions in Customizing for Special Purpose Ledger by choosing one of the following:

Periodic Processing Archiving Generate Coding for Archiving

Periodic Processing Archiving Generate Archive Reports

Periodic Processing Archiving De ne Report Groups and Read Programs

Archiving Authorizations (FI-SL)

To archive data in Special Purpose Ledger, you must have authorizations for:

Archiving in general

For more information, see User Authorization Checks .

Authorization object G_ADMI_CUS with activity 03 (archiving)

Authorization object S_ARCHIVE with the following values:

Activity: 01 (creating, reloading, deleting, and reading archive les)

Application area: GL

Archiving object: FI_SL_DATA

Authorization object S_TCODE

Variant Settings for Writing Data (FI-SL)

Use
When you schedule a write program, you have to enter an existing variant or create a new one. The variant contains the
selection criteria for the Special Purpose Ledger totals or line item records that you want to archive.

Features
When you create the archiving variant, you de ne whether you want to archive line item records only or totals records. The
default archiving type is line items . You can change this default setting in the eld Data to be archived .

In the eld Grouping of line items you can determine how the system organizes the line items during archiving:

According to account

If you choose this option the line items are sorted according to account assignment features (account, scal year, ledger,
company code, company) and written to the archive.

According to document number

This is custom documentation. For more information, please visit the SAP Help Portal 56
 9/14/2022
If you choose this option the system archives the line items according to document number as speci ed in the selection
criteria. The records are sorted based on table, ledger and document number.

For the selection criteria you can enter single values and intervals. The system archives only data that meets the selection
criteria you entered in the variant.

You can use the following groups of input elds:

Object Parameters

Restrictions

Processing Options

The input elds contained in these groups depends on the type of archiving that you have selected.

Object Parameters

The object parameters for the totals records and line items that you want to archive are the ledger, company code, company,
account, and FI-SL document number.

You only need to enter document selection criteria if you want to archive line items. You cannot enter document selection
criteria for archiving totals records.

Restrictions

In this group, enter the scal year, period, record type, and version to be archived. The P eriod eld only appears when you
archive line items.

 Note
The period eld is only used for archiving actual line items. You cannot enter periods if you are archiving plan line items (that
is, when you use record type 1 (plan records) or 3 (plan allocation records)). If you do so, the system displays an error
message.

When you archive actual and plan line items, the period restrictions are only taken into account for actual line items. The
plan line items are archived for the complete year.

Other Settings

For more information, see Variant Maintenance for Archiving Jobs in the general archiving documentation.

De ning Variants for Reloading (EC-PCA)

Use
Using the Reload function, you can retrieve archived data from archive les and load the data back into your online system.
Note that this function is to be used exceptionally as a last resort.

 Note
You can reload an archive le as often as required. However, you should be careful when reloading because the system does
not generate a log telling you whether archive les have already been reloaded previously. For this reason, after reloading,
your system could contain incorrect or duplicated data.

This is custom documentation. For more information, please visit the SAP Help Portal 57
 9/14/2022
Data that was archived before a local currency changeover cannot be reloaded.

To reload an archive le, you must enter an existing variant or create a new one. The variant contains the selection criteria for
the summary records and line items of the special purpose ledgers that you want to reload.

Activities
When creating the variant for reloading archived data, you must make entries for the selection criteria, additional settings, and
data records.

Settings for Reloading

Specify whether you want to reload line items or totals records.

Object Parameters

The object parameters for the totals records or line items to be reloaded are as follows: ledger, company code, company,
account, and FI-SL document number.

You can enter document selection criteria only when you reload line items. When you reload totals records, you cannot enter
any document selection criteria.

Constraints

In this group, enter the following for the reload: scal year, period, record type, and version. The Period eld is only available
when you are reloading line items.

You can enter either individual values or value intervals as selection criteria.

The system only reloads data records that meet the selection criteria that you have entered in the variant.

Specify as many selection criteria as possible to reduce the processing time of the reload program. You must always specify a
ledger name and a scal year.

Processing Options

If you want to start the reload program in test mode, choose Test Run.

In this case, no data is reloaded into your system. The system only reads the selected archive les according to the selection
criteria that you have entered.

Archive Selection

Select the archive les that you want to reload.

Displaying Archived FI-SL Totals Records and Line Items (FI-SL)

Accounts that were archived before a local currency changeover are displayed in the original currency. No translation is
performed in the background.

Features

Evaluating Line Items

This is custom documentation. For more information, please visit the SAP Help Portal 58
 9/14/2022
1. The FI-SL standard read transactions GD23, GD33, and GD20 read from the database and the archive. You can call up
the transactions from the FI-SL application menu or from archive management.

The archive can be accessed either via the Archive Information System (AS) or by manual le selection. For more
information, choose the "i" pushbutton in the dialog box for the data source (Extras -> Data Source).

2. The programs that are called up with transaction SARA ("Read" pushbutton), "Actual Line Items for Table..." and "Plan
Line Items for Table...", can read data from the archive and the database. It is not possible to access the archive using AS.
You have to select the les to be read manually. The programs read the les sequentially and in full. This can make the
evaluation process quite time-consuming. Where possible, run the reports as a background job.

Each of the read programs reads data from one table only. For information on the table from which data from existing
programs can be read, or on the tables for which you can create additional read programs, see Archive Management,
under Customizing -> Application-Speci c Customizing -> Generated FI-SL Archive/DB Reports (transaction GAR9). To
create new read programs, switch to the change mode, enter a program name for the required table, and save your
changes.. The required program is generated, and you can call it up in transaction SARA by choosing “Read”.

In the standard system, an actual line item report, a plan line item report, and a totals record report are delivered for
tables GLS1, GLP1, GLT1 and GLFUNCA, GLFUNCP, and GLFUNCT.

In Customizing transaction GAR8, you can assign to archiving object FI_SL_DATA the report writer/report painter report
groups (for FI-SL tables) that are relevant for archiving.

3. To obtain a technical view of archived data, like the one provided in the data browser (transaction SE16) for table records
that have not yet been archived, call up the AS Archive Explorer . Call up transaction SARI, choose "Archive Explorer", and
enter the relevant info structure.

A precondition for this kind of archive access is that the relevant info structures have been activated and lled:

If you want to access via the account: info structure SAP_FI_SL_001

To access using the document number/reference document number: info structure SAP_FI_SL_002

You can only access via the account (document number/reference document number) if "Archiving by Account"
("Archiving by Document") has been selected for archiving.

4. The Document Relationship Browser (SAP DRB) displays FI-SL documents archived with archiving object FI_SL_DATA if
an active info structure exists for eld catalog SAP_FI_SL_002 (such as info structure SAP_FI_SL_002).If you call up the
SAP DRB other than from an FI-SL transaction, the info structure must contain eld REFDOCNR for the reference
document number. If you call up the SAP DRB this way often, we recommend that you create a secondary index via the
reference document REFDOCNR (see SAP Note 164704).

Evaluating Totals Records (with Link to Line Items)

1. The FI-SL standard read transaction GD13 reads from the database and the archive. The archive can be accessed either
via AS or by manual le selection. For more information, choose the "i" pushbutton in the dialog box for the data source (
Extras -> Data Source ).

2. Report writer summary reports can be read from the archive or the database provided that they have been assigned to
archiving object FI_SL_DATA. You make this assignment in Archive Administration, under Component-Speci c
Customizing -> RW/RP Reports for FI-SL Archives (transaction GAR8).

It is not possible to analyze totals records from archived and non-archived scal years. (We advise you not to archive
totals records until you are sure that you no longer need them for year comparisons and the like. For example, you keep
totals records from the last two scal years in the system.)

It is not possible to access totals records automatically via AS with these reports. You have to manually select the les to
be read (by choosing the “Data Source” pushbutton on the selection screen). The les are read sequentially and in full.

This is custom documentation. For more information, please visit the SAP Help Portal 59
 9/14/2022
This can result in the analysis taking quite a long time. Where possible, run the reports as a background job. However,
this makes it impossible to call up the line items.

If you have entered a line item report as the receiver report (via the report/report interface) when de ning the report
writer summary report, you have the following options:

a. You have entered transaction GD20 as the receiver report.(In this case, the entry in the report/report interface
must contain the values "RT" for the report type and "RGGD2300" for the report.)

All line items belonging to the totals record are displayed if you have assigned to transaction GD20 a
variant for which both "Database" and "Archive" have been selected under "Data Source..." and for which
"Use Info System" has been activated.The archiving object with which the data has been archived is
irrelevant if corresponding AS info structures have been created.(How the "Archiving Object" eld is lled
is insigni cant.)

All line items belonging to the totals record are also displayed if you have not assigned a variant, but
automatic archive access has been activated for this report in table ASACCESS01. For more information,
choose the "i" pushbutton in the dialog box for the data source ( Extras -> Data Source ).

In all other cases, no archived line items are read. Instead, only those that are still in the database are
read.

b. For the other line item reports (such as the reports mentioned in point 2 under "Analyzing Line Items" above), the
line items belonging to the totals record are only displayed if they have not yet been archived.

3. See point 3 under "Analyzing Line Items" above.An info structure for eld catalog SAP_FI_SL_001 must be active and
lled with data.

4. The summary report that is called up with transaction SARA (by choosing the "Read" pushbutton), "Totals Records from
...", can read data from the archive and the database. The report has exactly the same properties as the report
described in point 2 under "Analyzing Line Items" above. It is possible to call up the line items from the summary report,
but not if the summary report has been run as a background job.

The read programs and report groups that are displayed are those that you generated or de ned in Customizing for Special
Purpose Ledger. For more information on this topic, see Application Customizing (FI-SL) .

Activities

Connection to the Archive Information System (AS)

To display individual objects for the archiving object FI-SL-DATA using the Archive Information System or to access individual
objects using the AS (from transactions GD13, GD20, GD23, or GD33), y ou require an info structure that has been created on
the basis of the standard eld catalogs SAP_FI_SL_001 or SAP_FI_SL_002 delivered by SAP. The info structure must be active
and lled.

 Recommendation
Use the info structures SAP_FI_SL_001 or SAP_FI_SL_002, which are delivered in the standard system.

To access archived FI-SL documents using the Document Relationship Browser , an info structure for eld catalog
SAP_FI_SL_002 must exist and be active. If you call up the SAP DRB other than from an FI-SL transaction, the info structure
must contain eld REFDOCNR for the reference document number. If you often call up the SAP DRB in this way, we recommend
that you create a secondary index via the reference document REFDOCNR (see SAP Note 164704).

For more information on info structures, see Using the Archive Information System .

This is custom documentation. For more information, please visit the SAP Help Portal 60
 9/14/2022

Archiving Funds Management Data (FI-FM)

De nition

In Funds Management, you can archive and reload:

Description Archiving Object

Earmarked funds FM_FUNRES

Budget postings FM_BUDHIE

FI postings FM_DOC_FI

CO postings FM_DOC_CO

Commitment and funds transfers FM_DOC_OI

See also:

Introduction

Earmarked Fund Archiving (FI-FM)

De nition
Archiving object FM_FUNRES for archiving the following document categories:

Funds block

Funds reservation

Funds precommitments

Funds commitment

Funds transfer

Forecast of revenues

Structure
If you use the archiving object FM_FUNRES, data from various tables is archived. You can display these table names by choosing
DB Tables.

The following functions are available for FM_FUNRES:

Action Report

Preprocessing RFMRESDF

During preprocessing, the program checks whether a document can

be archived. If it can, the archiving indicator in the document is set.
The posted document can no longer be changed.

For more information, see the program documentation.

Archiving RFMRESWR
This is custom documentation. For more information, please visit the SAP Help Portal 61
 9/14/2022
During archiving, the relevant data is written to newly created
archive les on the disk. However, the data is not removed from the
database. Only documents in which the archiving indicator is set
are deleted (see “Preprocessing”).

Delete RFMRESDL

The deletion program is always based on the archive les already

generated. In Customizing for archiving objects, you can stipulate
that the archive elds are always copied automatically to an
archive system after successful processing, using the Content
Management Service.

The standard setting for the archiving object FM_FUNRES is for the
system to trigger the deletion transaction automatically after
archiving.

However, you can opt to have the deletion program run only in test
mode. Do this in Customizing for archiving object FM_FUNRES.

Reloading Data from the Archive RFMRESRL

In reloading, the program returns the funds precommitments that

have been archived to the system. You can only use the reload
program if an archiving run has taken place rst. The archiving run
must have been complete.

We advise that you take great care when using this program. It is
particularly dangerous to reload documents if the Customizing
settings have changed in the meantime.

Manage You can use management to display object-speci c management

information in a list and to evaluate this.

For information on the range of functions of archiving run

management, see: Accessing Archiving Management

Archiving Periods and Criteria (FI-FM)

A number of prerequisites must be satis ed before documents no longer required can be archived. The preprocessing program
does not set the indicator in the relevant document headers until all the conditions are met. Only the preprocessing program
can set the archiving indicator. You cannot make any further changes to the document once the archiving indicator is set. The
archiving indicator cannot be removed.

Prerequisites for Setting of the Archiving Indicator

You must be authorized to archive the document. For more information, see Earmarked Fund Authorizations (FI-FM)

The document must have been completed for a given period of time (retention period) with no changes made in the
interim. The term "changes" in this context includes reduction postings.

 Note

Information on the document, particularly on when it was last changed and whether the archiving indicator has been set, is in
the document header. For detailed document header information, choose Goto Document header detail in the document
display.

There must be no dependent documents. For more information, see Earmarked Fund Dependencies (FI-FM)

This is custom documentation. For more information, please visit the SAP Help Portal 62
 9/14/2022

Application Customizing (FI-FM)

Use
As well as basic customizing for archiving, you must stipulate the retention period which the preprocessing program evaluates
in the archivability check.

 Note

The retention period should be at least three months.

Features
The retention period is the timespan (in calendar months) which must have elapsed between the last change to a document
and the preprocessing program or, more precisely, the setting of the archiving indicator.

Activities
Go to the Funds Management IMG and maintain the retention period using the step De ne document types .

Earmarked Fund Dependencies (FI-FM)

Earmarked funds documents which reference each other, such as where a funds commitment references a funds reservation,
must be archived in the same archiving run.

Other documents, such as invoices or purchase orders, which reference the earmarked funds to be archived, must be archived
and deleted before you archive the earmarked funds themselves.

Earmarked Fund Authorizations (FI-FM)

To archive earmarked fund documents, you must have both the general archiving authorization and authorization for the
F_FUNDSRES authorization object, with activity 24 (archiving).

Archiving Budget Postings (FI-FM)

De nition
Budget hierarchy documents from Funds Management (FM) are archived using the archiving object FM_BUDHIE .

Structure
You can archive data from different tables using the archiving object FM_BUDHIE . From the archiving function you can display
the tables affected by pressing the pushbutton DB tables .

The following functions are available for archiving object FM_BUDHIE:

Function Description Report

This is custom documentation. For more information, please visit the SAP Help Portal 63
 9/14/2022

Archiving This program archives budget documents RFFMAR41

for closed scal years, generating an
archive le. You can set the program up so
that the database entries are deleted
immediately after archiving.

Deleting This program deletes the database entries RFFMAR44

of budget documents that have been
archived.

Reloading This program reloads the archived budget RFFMAR45

documents to the database.

You should only reload database entries in

exceptional cases. For more information,
see the program documentation.

See also:

Archiving Funds Management (FI-FM)

Program documentation RFFMAR41

Archiving FI Postings (FI-FM)

De nition
Archiving object FM_DOC_FI for archiving Funds Management (FM) FI postings. These postings include:

FI line items

FI actuals line items

FM postings

Structure
When archiving Funds Management FI postings, data is archived from a number of different tables. If you are archiving the
FM_DOC_FI archiving object, you can display the relevant tables by clicking on the DB tables button.

When working with archiving object FM_DOC_FI , the following functions are available : You can display the programs that these
functions provide using transaction code AOBJ.

Function Description Program

Archive The archiving program archives Funds RFFMAR01

Management FI postings and generates an
archive le from the data. You can set up
the program in such a way that database
entries are deleted immediately after
archiving

Delete The deletion program deletes the database RFFMAR04

entries for Funds Management FI postings
that have been archived.

Evaluate The evaluation program evaluates the RFFMAR02

This is custom documentation. For more information, please visit the SAP Help Portal 64
 9/14/2022
archived data sequentially. This program is
intended for test cases and small volumes
of data.

For more comprehensive evaluations, you

can use the Archive Information System

Reload The reload program reloads archived Funds RFFMAR05

Management FI postings into the database.

You should only reload database entries in

exceptional cases. For more information,
see the program documentation.

Integration
Funds Management FI postings are copies of Financial Accounting documents. You can only archive FI postings in Funds
Management if you have already archived the corresponding documents in Financial Accounting using archiving object
FI_DOCUMNT .

See also:

Archiving Funds Management (FI-FM)

Program documentation for archiving functions. You can nd this documentation using transaction SARA:

1. Enter an archiving object. Choose Write .

2. Enter a variant. Choose Maintain .

3. Choose ( p rogram documentation ).

Archiving CO Postings (FI-FM)

De nition
CO postings from Funds Management (FM) are archived using the archiving object FM_DOC_CO . These are:

CO line items

CO actual line items

FM postings

Structure
You can archive data from different tables using the archiving object FM_DOC_CO . From the archiving function you can display
the tables affected by pressing the pushbutton DB tables .

The following functions are available for archiving object FM_DOC_CO:

Function Description Report

Archiving The archiving program archives the CO RFFMAR21

postings from FM, generating an archive
le. You can set the program up so that the

This is custom documentation. For more information, please visit the SAP Help Portal 65
 9/14/2022
database entries are deleted immediately
after archiving.

Deleting The delete program deletes the database RFFMAR24

entries of the CO postings from FM that
have been archived.

Evaluating The evaluation program carries out a RFFMAR22

sequential evaluation of the archived CO
postings. This program is designed for test
cases or a small amount of data.

Use the archive information system (SAP

AS) for more comprehensive evaluations.

Reloading The reloading program reloads archived CO RFFMAR25

postings for FM to the database.

You should only reload database entries in

exceptional cases. For more information,
see the program documentation.

Integration
The CO postings in Funds Management are copies of the nancial accounting documents. You can not archive CO postings in FM
until the corresponding external CO documents have been archived using the archiving object CO_ITEM .

See also:

Archiving Funds Management (FI-FM)

Program documentation RFFMAR21

Archiving Commitment and Funds Transfers (FI-FM)

De nition
Commitment and funds transfers from Funds Management (FM) are archived using the archiving object FM_DOC_OI . These
are:

Commitment line items

Commitment actual line items

FM postings

Structure
You can archive data from different tables using the archiving object FM_DOC_OI . From the archiving function you can display
the tables affected by pressing the pushbutton DB tables .

The following functions are available for archiving object FM_DOC_OI:

Function Description Report

Archiving The archiving program archives the RFFMAR11

This is custom documentation. For more information, please visit the SAP Help Portal 66
 9/14/2022
commitment and funds transfers from FM,
generating an archive le. You can set the
program up so that the database entries are
deleted immediately after archiving.

Deleting The delete program deletes the database RFFMAR14

entries of the commitment and funds
transfers from FM that have been archived.

Evaluating The evaluation program carries out a RFFMAR12

sequential evaluation of the archived
commitment and funds transfers. This
program is designed for test cases or a
small amount of data.

Use the archive information system for

more comprehensive evaluations.

Reloading The reloading program reloads archived RFFMAR15

commitment and funds transfers for FM to
the database.

You should only reload database entries in

exceptional cases. For more information,
see the program documentation.

Integration
The commitment and funds transfers in Funds Management are copies of the nancial accounting documents. You can not
archive CO postings in FM until the corresponding external MM documents have been archived using the archiving object
FI_DOCUMNT .

See also:

Archiving Funds Management (FI-FM)

Program documentation RFFMAR11

This is custom documentation. For more information, please visit the SAP Help Portal 67