Title
Analyze print document header data for archiving

Purpose
This report carries out the first step in archiving print documentheader data: Analyzing print document header data with a view topossibly archiving it.
The archiving object related to the archiving of print document headerdata is ISU_PRDOCH. It encompasses the following print document data:

• Print document header data


• Outsorting data for a print document


• Link data for contract accounting documents


• Discount line item data for a print document


• Data for conversion steps per billing line item

Using the AOBJ transaction you will find the definition of theISU_PRDOCH archiving object and the related Customizing.
Using the SARA transaction you will find archiving administration andthe related Customizing.
Using the SARI transaction you will find the technical view of anarchive.
Using the standard IS-U transaction SISU, you will find the accountingview of an archived print document.

Integration


• REPDAR_ARCH_HEAD

Second step: Archiving the print document header data selected in thefirst step.

• REPDAR_DEL_HEAD

Third step: Deleting the print document header data from the database onthe basis of the previously created archive.

• REPDAR_REL_HEAD

Use this report to reload data that has been archived and alreadydeleted. Note that you cannot reload individual budget billing plans.You have to reload the entire archiving run. This procedure should notnormally be used and should be limited to extreme problem cases (forexample, incorrect retention period in Customizing).

• REPDAR_READ_ARCHIVE_HEAD

This report allows you to read a print document header data archive andto display parts of the data in a list before the deletion program hasbeen executed. It displays the data in a technical view.

Features
The analysis report selects the print documents:


• That lie within the specified number range for documents, contract
accounts or portions

• That have archiving status 3 (print document line items deleted) in the
document header data

• That are not simulation documents (these are only deleted)


• Whose retention period has expired.

The retention period is configured in
Customizing. Here you can assign differentretention periods (in days) to the reversal print document header data,reversed print document headers and the rest of the print documentheaders respectively.
You have the option of defining customer-specific checks for whether aprint document header can be archived or not in a subsequent analysisprocess. This allows you to make further restrictions. For moreinformation, see the documentation on the ETOAR001 enhancementand on the EXIT_REPDAR_ANALYSE_HEAD_001 function module.
RESET N1
If you don't start the report in test mode, then the archive status ofall the selected print documents that remain after the analysis processis set to 4 (print document header can be archived).

Starting the program
When you start the report you can make various settings on the initialscreen:


• Document number: limits the set of data to be analyzed to certain
bill print-document numbers

• Contract account: limits the set of data to be analyzed to
certain contract accounts

• Portion: limits the set of data to be analyzed to certain
portions

• Log type: general statistical data or detail log containing every
analyzed data record (can become confusing with large amounts of data).

• Run time restriction: If you activate the run time restriction,
the analysis report terminates when the end date and end time isreached. This means that you can let the analysis report run as a jobduring short time frames.

• Test run: If you start the report as a test run, no changes are
made to the database (updating the archiving indicator in the printdocument header).

• Automatic archiving start: Setting this indicator triggers the
SAP_ISU_ARC_PRDOC_ANA_HEAD_END after the completion of the analysis run.If you have previously scheduled an archiving run with the sameselection parameters, saved under the same variant name, and the startcondition "After Event", then this archiving run is startedautomatically after the completion of the analysis run.