Creating a Write Variant (PY-XX-DT)
If you run the write program RPAR6W00
of the archiving object HR: Index Files for Posting to Accounting
(PA_PIDX
), you need to enter an exisiting variant or create a new variant. For each archiving session, even for a test run, you need to maintain your own variant for Archiving
. This variant is used to write index files and statuses that belong to the successfully posted posting runs to an archive file.
On the specified start date, the archive file is written to the output device that you entered in the spool parameters. The system then deletes the archived data from the database.
The variant contains the selection criteria for the index files that you want to archive or destroy. For information about the meaning of the parameters that are available on the selection screen of the write program, see the documentation for the write program RPAR6W00
(transaction SE38
).
Prerequisites
You are on the Archive Administration: Create Archive Files
screen.
Procedure
Enter a variant name and choose
Maintain
.If required, state whether you want to use the variant for all selection screens, or only to archive index files, and choose
Continue
.For the run type
Payroll Posting
(PP
), use the run number to select the posting runs for which you want to archive the index files.If you have not performed archiving previously, select all posting runs.
If you have already archived index files, select the posting runs that have occurred since the last archiving session.
For documentation purposes, you can enter a comment or a note to characterize the archiving session, for example, information about the period.
Choose
Attributes
.The
ABAP: Save Attributes of Variant
screen appears.Make the settings of your choice and save the variant.
Recommendation
We recommend that you initially start the archiving session as a test run so that you can resolve any errors before archiving. In this case, no archive file is generated and the table entries are not deleted.
Caution
If you want to use the same variant for the productive archiving session, you need to delete the successful test run from the job overview.