Kontakt

Ansicht
Dokumentation

Archiving of EBP Documents ( RELNEBP_35_ARCHIVING )

Archiving of EBP Documents ( RELNEBP_35_ARCHIVING )

CL_GUI_FRONTEND_SERVICES - Frontend Services   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Archiving of EBP Documents

Use

As of SAP Markets Enterprise Buyer Release 3.5, functions for archiving of the following documents are available via SAP archive administration (transaction SARA):

  • Shopping cart (SC)
  • Purchase order (PO)
  • Confirmation (CF)
  • Invoice (INV)

The relevant archiving objects BBP_SC, BBP_PO, BBP_CF, and BBP_INV have been created and can be changed using transaction AOBJ (Defining Archiving Objects).

The complete archiving process consists of four subprocesses:

  1. Check program (Description in transaction SARA: Initial run)
Selected documents are checked to establish whether they can be archived. (Document selection per document type and document number interval.) Documents that meet the check requirements are assigned status archivable. For performance reasons, the change date of documents that cannot be archived is set in such a way that these documents cannot be checked again within the next 30 days.
Check criteria that a document has to meet in order for it to receive the status archivable include the retention period in the system (residence time), document status, follow-on documents, and various indicators.
The check program contains a test run and a detail log used for evaluations.
  1. Write program (Write)
The data to be archived is written sequentially to a newly created archive file. (Document selection per document type and document number interval.)
The write program has a test run and detail log.
  1. Conversion program (Delete)
The archive files are read. If archiving is possible, the status of the corresponding EBP documents is set from "archivable" to "archived".
No physical deletion occurs at this point!
The conversion program also has a test run.
  1. Deletion program (Postprocessing)
Documents with "archived" status are deleted from the EBP databases.
Test run and detail log are also available.

Restrictions

  • It is not possible to restore the archive files to the file system.
  • Also, a program to read the archived files has not yet been implemented.
  • In EBP Release 3.5, it is still not possible to archive other EBP document types, such as bid invitations or bids.
EBP archiving for 3.5 primarily serves to facilitate the cleanup of the database and to restrict accumulation of data.

WARNING:
If there are documents to archive both in the EBP system and in the backend system, you must archive the EBP documents first because otherwise data inconsistencies could arise when you read back the archive data files.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

The residence time of the documents to be archived in the system is one of the check criteria for starting EBP document archiving.

You make the settings for this in the IMG activity:

SAP Markets Enterprise Buyer → Cross-Application Basic Settings → Define Residence Times for EBP Documents

Further Information

  • SAP Library:
    Cross-Application Components -> Archiving of Application Data
    (general information on the topic Archiving in SAP Systems)
  • SAP Library:
    SAP Markets Enterprise Buyer → Tasks for System Administrators → Document Archiving
    (specific information on EBP Archiving)






Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 5380 Date: 20240520 Time: 201745     sap01-206 ( 70 ms )