SAP Program BUSOBARCH - BDT: Archiving - Archiving Program

Purpose
To create archive files.

Prerequisites

  • You have set the archiving flag in the business partner dialog.

  • The background process for archiving must be set by following these
  • steps:
    Parameterize the archiving object (here BOR object BUS1006005)using transaction DACONTROL.
    Schedule and carry out the background process for data archiving onthe CRM Server (transaction DACHECK).
    • Make the other necessary system settings in the Implementation Guide
    • (IMG) in Customizing of the system administration under archivingobject-specific Customizing in the data archiving (archiving objectCA_BUPA).
      • In the case of users' own data, settings must also be made
      • in the following transactions:
        Transaction BUS7 for BDT event modules
        Transaction AOBJ. Here you include your own tables in the structuredefinition of the archiving object CA_BUPA.

        Features
        The following phases are run through when business partners arearchived:

        • A check to see if archiving is allowed (BDT event ARCH1). The
        • following checks are carried out:
          The reference business partner may not be archived.
          A business partner may not be archived if there are still activebusiness transactions. The business transactions in question mustfirst be archived before the relevant business partners can bearchived.
          A business partner may not be archived if it is actively used in theorganizational data.
          No relationships (product - business partner) may exist any more,but they may however be archived together with the relevant products
          No partner/product ranges may exist. They have their own achivingprocedure.
          An active Internet user may no longer exist.
          • Write to the archive (BDT events ARCH2 and ARCH3):

          • Write the header data for the business partner (ARCH2).
            All dependent data is also written to the archive (ARCH3).

            Activities
            1. Choose a variant using the F4 button.
            If no variant exists, choose variants and maintain the requiredvariant. If the option start is set automatically in thearchivingobject-specific Customizing for the deletion program and a productionvariant is selected for the archiving program, the deletion programthen also starts with its production variant. This means that thedata in the database is deleted after archiving.
            2. Maintain the start date and the spool parameter.
            The pushbutton archive directory allows you to determine thefree memory space in the current object-specific archive directory.This function is however not suited to HSM systems. The valuesdelivered are therefore relatively unreliable.

            Result
            You have now entered all the data needed for the background job. SelectExecute in order to carry out the job now.
            After all the archive directories of a run have been completely written,the system event SAP_ARCHIVING_WRITE_FINISHED is triggered by the ADK.As a reaction to this event, processes that follow archiving, forexample, the automatic saving of files, can be triggered by externaltools.