Overview
Program SAPF059 reloads archived vendor master data including generaldata, all FI data, and all MM data that are contained in the archivefile for one object. You can limit the amount of data for reloading byentering selections. The computer on which you start importing the datamust have access to the archive file.
To determine the archive name (for example, for a batch operation), youcan use SAP's archive management via transaction SARA.

Selection
You can limit the amount of vendor data for reloading by specifying theaccount number. If the account number in the archive is the same as yourselection, the program reloads the vendor data into the SAP System anddeletes it from the archive. The reloaded data has no special indicatorand is in its original form.
If the account is not imported because of your selection or technicalproblems, the system opens a new archive file containing all documentsthat are not reloaded (remaining data file). The other archives are nolonger valid.
Furthermore you can select the usual options, test run (only displaydata, no reload) and detail log (log at object level).

What can be reloaded
Vendor data can be fully reloaded if the following criteria are met:
General: The account is within your selection (see above) and
FI: All company codes in the account company code data are created and
FI: Master data stored in the archive no longer exists at company codelevel.
FI: The master record to be reloaded refers to other master recordswhich do not exist (for example, via fiscal address or alternativepayee). This check can, however, be switched off (by means of the "FIlink validation off" field) if you know that the referenced master datais also reloaded later.
It is, however, possible to reload master data even if the generalrecord belonging to it still exists (condition: the record must be thesame as the one stored in the archive). Therefore, it is possible thatonly the company code data is deleted during archiving while the generaldata is merely copied to the archive.

Precondition
Before working with this program, you must make sure that theappropriate achive files are available on the local disk so that theprogram can access them.

Output
The output lists in the detail log correspond to those from archiving:First, the program outputs the vendor data that cannot be reloaded,separating it according to general data and data at the applicationlevel as well as specifying the reason why data could not be reloaded.Then, the program lists all records reloaded, separating them againaccording to general data and data in the application area.
The following error messages and warnings can be displayed in the log:

• Account not selected: Account is not reloaded because you did not select
it.

• General data already exists: Account is fully reloaded because the
general data already in the system is the same as the data stored in thearchive.

• General data exists and is different: Unlike the account in the previous
example, this account is not reloaded because the general data alreadyin the system is different from the data stored in the archive.

• Referenced to xyz: This vendor refers to another vendor who does not
currently exist in the database. This validation can be switched offusing the "FI link validation off" switch.

• Other error found: This error type appears when a program error occurs.
The object is not reloaded but placed in the remaining data file.

• The following messages refer to an error in another area. For more
information you must check the detail log in the respective area.
Error adding general data to the database
Error adding FI data to the database
Error adding MM data to the database
because of the general data (see data)
because of the FI data (see data)
because of the MM data (see data)
General information on the program run is displayed in the overview log.

Note

Related programs
Where as program SAPF058 carries out archiving (selection and filecreation), program SAPF058D deletes the G/L accounts which have beenstored in the archive file.

Independent of Release
Basically all archives from prior Releases can be reloaded or read.
Yet for archives from Release 2.0, you must take note that, because ofthe information in the 2.0 archive, neither an automatic code pageconversion (for example, EBCDIC -> ASCII) nor a number format conversioncan be carried out. The same applies to structure changes carried out inthe vendor tables in an SAP 2.0 Release.