Ansicht
Dokumentation

RFKKINV_ARCH_BILLDOC_ARCHIVE - Archive Billing Documents

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

This report carries out the first step in archiving billing documents. It covers:

1. The analysis of billing documents with respect to possible archiving
2. Writing the billing documents to an archive file, based on the analysis performed in the first step
3. Possible deletion of additional data for the archived billing documents, if you set this up in Customizing

The archiving object includes the following data of the billing documents:

• DFKKINVBILL_H

• DFKKINVBILL_T

• DFKKINVBILL_I

• FKKINVBILL_A

• DFKKINVBILL_PY
  
  

The archiving object that belongs to the archiving of billing documents is FKKINVBILL.

Using the transaction AOBJ, you can access the definition of the archiving object and the related Customizing.

Using the transaction SARA, you can access the archive administration and the related Customizing.

Using the transaction SARI, you can access the technical view of archived billing documents.

In variant maintenance for the write program the following actions from SAP NetWeaver Information Lifecycle Management are available:

• Archiving

With this action, you can archive the data of closed business objects. The system performs archivability checks to check if the data can be archived. In this respect, this function corresponds to the function of standard data archiving that you are used to. By means of the ILM enhancements, the system evaluates the rules maintained in the Information Retention Manager (IRM) for each object instance during the write phase, and thereby determines the retention period and the storage location for the object. This information is persisted on the database as part of the management data and is later interpreted when the data is stored.

• Snapshot

Snapshots represent archiving runs that extract data from the database, but do not delete this data from the database. Except for considering the restrictions in the selection variant, the system does not perform any additional checks. Using this option, therefore, you can also write data from current, not yet completed business transactions to the archive. To exclude the possibility of losing data, runs of this type are not offered for deletion. With snapshots therefore, you always create redundant copies of data from the database. This function is especially useful for system decommissioning in conjunction with the ILM component Retention Warehouse.

• Destruction of Data

The destruction of data from the database takes place using an archiving write run followed by a deletion run. During this process, temporary archive files are created that are then deleted again after the deletion phase is completed. The system automatically deletes these files along with the file-related management data. The technical classification of a run as a destruction run is made using the parameter DESTROY. If an archiving object is not registered in IRM, the parameter DESTROY is completely ignored, and a normal archiving run takes place.

Reports

Archiving of billing documents consists of the following reports:

• Delete Additional Items of Billing Documents (RFKKINV_DFKKINVBILLA_DELETE)

You use this report to control the deletion of additional data. If you have specified in Customizing that the additional data of a billing document should be deleted before archiving, then the report deletes this data.

Using the BAdI FKKINV_BILLDOC_ARCHIVE, you can define additional checks for the deletion of additional data of billing documents.

• Archive Billing Documents (RFKKINV_ARCH_BILLDOC_ARCHIVE)

Using this report you archive billing documents. The system analyzes all specified billing documents with respect to possible archiving.

Using the BAdI FKKINV_BILLDOC_ARCHIVE, you can define additional checks for the archiving of billing documents.

See the Prerequisites section.

• Delete Archived Billing Documents (RFKKINV_ARCH_BILLDOC_DELETE)

You use this report to delete the billing documents written to the archive file from the corresponding database tables.

• Display Archived Billing Documents (RFKKINV_ARCH_BILLDOC_READ)

You use this report to display the archived billing documents.

Note

You should not archive billing documents before the invoicing document was created. Otherwise this can reduce performance during invoicing.

You have to enter the standard residence time for the archiving of billing documents in Customizing before you can carry out archiving.

In addition, you have to maintain the control for the additional data of billing documents for each document type. You make this setting in the Customizing activity Define Additional Settings for Archiving of Billing Documents. You can also define the residence time there at the level of the document type.

The archiving report selects the following billing documents:

• Billing documents with a document number that falls within the selection entered

• Billing documents whose residence time has expired

You define the residence time in Customizing.

At event 2751, you can you can define additional checks on the archivability of billing documents in a subsequent analysis process.

At event 2750, you can archive your own tables, if table DFKKINVBILL_A is only a reference table.

If you defined in Customizing that additional data is deleted during archiving, you can delete your own tables in event 2753.

For more information, see the documentation of the given event module.

Checks for archivability:

A billing document can only be archived when the following prerequisites are met:

• The to-date and the creation date are before the defined residence time (residence time check).

• The document is not simulated.

• There is no invoicing trigger.
  
  

You can limit the dataset to be analyzed by the document type, billing document number, contract account, and business partner.

If you start the report as a test run, no changes are made to the database.

In an update run, changes are made to the database. The detailed log displays comprehensive data for each analyzed data record. However, in the case of large data volumes this can become unwieldy.

In the Comment for Archive Run field, you can enter your own comment for the archive run.

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 7857 Date: 20240520 Time: 124400     sap01-206 ( 127 ms )