Kontakt

Ansicht
Dokumentation

RV130005 - Agreement Archiving: Write program for object SD_AGREEM

RV130005 - Agreement Archiving: Write program for object SD_AGREEM

ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Description

Conditions: Archiving agreements (create archive)

Archiving condition records is carried out using the 'ARCHIVE DEVELOPMENT KIT' (ADK).
Archiving is carried out via transaction 'SARA'!
Calling the 3 programs can be carried out individually and independently, in which case the DB deletion program is not, however, started automatically by the archive creation program.

  1. Use the F4 Help to choose a variant with which the program should be started.
    If no variant exists, create a variant with the pushbutton Maintain. (Notes on the procedure can be found in the F1-help for the field variant.)
  2. With the pushbutton Start time, determine when the job should run.
  3. Use the pushbutton Spool Parameter to define how the archiving log should be managed. If the deletion program is started automatically by the archiving program, these spool parameters also apply to the log for the deletion program.
    (For further details on the topic Spool Management, refer to "Introduction to the SAP System" in the SAP Library under the section "Print".)
  4. Under Customizing -> Technical Settings, you can if necessary make further settings such as the size of an archive file, the logical file name, content repository for storing the archive files, and automatic start of the delete program.
  5. Customizing -> Client-(in)dependent file/path names takes you to the maintenance of logical file names/paths (transaction FILE (client-independent), SF01 (client dependent).
  6. Select Generate job to create the job with the set values.
    Under Environment -> Job overview, a list of all jobs available for the current archiving program in job management is displayed.
    (For further information on the topic Background Jobs, refer to the SAP Library in the area SAP NetWeaver, System Administration, section "Scheduling Background Jobs".)

The following programs have been created for archiving:

  1. RV13005:
Creation of archiving objects (agreements) in an archive
  1. RV13006:
Physical deletion of the database entries for the archive objects created by RV130005
Program documentation
  1. RV13007:
Option for reload to the database for archiving objects created by RV130005 and physically deleted by RV130006.
Program documentation

Rv130006 should always be run after RV130005; this is guaranteed by transaction 'SARA'.

RV130007 should only be used in exceptional circumstances, when it is absolutely necessary to reload archived agreements.

DB tables involved

The following DB tables are combined in an archiving object and archived together:

  • KONA: Agreements

Corresponding conditions

  • Axxx bzw. KOTExxx: Condition tables

  • KONH: Condition header

  • KONP: Condition item

  • KONM/KONW: Quantities or value scales

Item and scale are archived via archiving class CONDS

Indices

  • KONAIND: Index

  • WAKHIND: Index retail promotions

  • EKBO: Index subsequent settlement

  • EBOX: Index settlement documents for subsequent settlement

Restrictions

Normal archiving of conditions (SD_COND) can lead to conditions for agreements are already written to the condition archive. When the agreements are reloaded, these conditions are no longer found.

Normal; Furthermore data records can remain in the index table KONAIND, for which the volume rebate stipulations in sales, as well as the corresponding condition records have already been archived.

By selecting the checkbox for index cleanup in the window "Agreements in Sales' you archive these data records as well.

This should occur after you run a regular archiving session with those variants (select the checkbox for index cleanup, in addition), since the index cleanup requires many resources, in some cases, and therefore the regular archiving session could last too long.

Requirements

Rebate agreements in sales and arrangements in purchasing can only be

archived if settlement has been completed.

Output

The archiving log can also include a list of agreements to be processed.






CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5521 Date: 20240601 Time: 162300     sap01-206 ( 71 ms )