Kontakt

Ansicht
Dokumentation

SAPF059 - FI: Vendor Master Record Archiving: Retrieval Program

SAPF059 - FI: Vendor Master Record Archiving: Retrieval Program

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Overview

Program SAPF059 reloads archived vendor master data including general data, all FI data, and all MM data that are contained in the archive file for one object. You can limit the amount of data for reloading by entering selections. The computer on which you start importing the data must have access to the archive file.

To determine the archive name (for example, for a batch operation), you can use SAP's archive management via transaction SARA.

Selection

You can limit the amount of vendor data for reloading by specifying the account number. If the account number in the archive is the same as your selection, the program reloads the vendor data into the SAP System and deletes it from the archive. The reloaded data has no special indicator and is in its original form.

If the account is not imported because of your selection or technical problems, the system opens a new archive file containing all documents that are not reloaded (remaining data file). The other archives are no longer valid.

Furthermore you can select the usual options, test run (only display data, 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 code level.

  • FI: The master record to be reloaded refers to other master records which do not exist (for example, via fiscal address or alternative payee). This check can, however, be switched off (by means of the "FI link validation off" field) if you know that the referenced master data is also reloaded later.

It is, however, possible to reload master data even if the general record belonging to it still exists (condition: the record must be the same as the one stored in the archive). Therefore, it is possible that only the company code data is deleted during archiving while the general data is merely copied to the archive.

Requirements

Before working with this program, you must make sure that the appropriate achive files are available on the local disk so that the program 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 application level as well as specifying the reason why data could not be reloaded. Then, the program lists all records reloaded, separating them again according 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 the archive.
  • General data exists and is different: Unlike the account in the previous example, this account is not reloaded because the general data already in 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 off using 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 file creation), program SAPF058D deletes the G/L accounts which have been stored 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 of the information in the 2.0 archive, neither an automatic code page conversion (for example, EBCDIC -> ASCII) nor a number format conversion can be carried out. The same applies to structure changes carried out in the vendor tables in an SAP 2.0 Release.






ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5647 Date: 20240531 Time: 215247     sap01-206 ( 94 ms )