SAP ABAP IMG Activity SIMG_CFMENUOLSDVOKO (Archiving Control For Conditions)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ SD-MD (Application Component) Master Data
     ⤷ VIO (Package) Introductory Guide to R/3 Organization and Environment
IMG Activity
ID SIMG_CFMENUOLSDVOKO Archiving Control For Conditions  
Transaction Code S_ALR_87005812   IMG Activity: SIMG_CFMENUOLSDVOKO 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLSDVOKO   Control archiving for conditions 
Customizing Activity SIMG_CFMENUOLSDVOKO   Archiving Control For Conditions 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLSDVOKO    

Description

Conditions: Archiving conditions (create archive)

You archive condition records with the 'ARCHIV DEVELOPMENT KIT' (ADK).

Three programs have been designed for archiving. They can be called up using transaction 'SARA'.

You can, however, call up the 3 programs individually and independently, but then the database deletion program is not automatically started by the archive creation program.

The following programs were created for archiving:

  1. RV13001:

    Creating archiving objects in an archive

  2. RV130002:

    Physical deletion of the database entries for the archiving objects created by RV130001.

    Program documentation

  3. RV130003:

    Option to reload archiving objects into the database created by RV130001 and physically deleted by RV130002.

    Program documentation

Rv130002 should always run after RV130001; this is ensured by transaction 'SARA'.

RV130003 is only to be used in exceptional conditions when archived conditions really must be reloaded.

Affected database tables

The following database tables are grouped together to form an archiving object and archived together:

  • Axxx: condition table
  • KONH: condition header
    • linked with the condition table via KNUMH.
  • KONP: condition items
    • possibly several linked to KONH via KNUMH.
  • KONM: conditions (quantity scale)
    • none or several linked to KONP via KNUMH.
  • KONW: conditions (value scale)
    • none or several linked to KONP via KNUMH.

Restrictions

Agreements, sales deals..: that is, archiving is also carried out for all conditions linked to KONA. If one of the following fields of KONP is not initial, the condition is still archived: KNUMA-PI (promotion), KNUMA_AG (sales deal), KNUMA_SQ (sales quote) and AKTNR (retail promotion)

There may then be references in KONA to conditions which have been archived, or which no longer exist.

Hinweis

If you use subsequent settlements, the residence time set here is classed as logical and "links" with the residence time for the document type maintained here.

Possible Selections

On the initial screen in archiving, you can make the following settings:

  • Usage:

    A = pricing is possible

  • Application:
  • Condition type:

    Possible to restrict to individual condition types

  • Condition table:

    If an entry is made, precisely this condition table is archived for the chosen usage, application and condition type. Only the number is entered.

    • Enter 005, for example, to archive A005 for usage A

The following options are possible:

  • Include deletion indicator (independent of the date):

    The conditions for which the deletion indicator is set are added, regardless of the validity date, to the conditions selected via the normal date selection.

  • Exclude deletion indicator (independent of the date):

    Only the conditions, for which the deletion indicator is set, are taken into account independently of the date.

  • Test run only (without deletion):

    If the program is started using the archiving transaction (SARA), the parameter is transferred to the corresponding deletion program. If the parameter is set, the database is not physically deleted.

  • Create archive file with test:

    This parameter controls whether an archive file is created during the test run or not.

    Backup archives can be created this way without the data being physically deleted.

    The parameter must be set in the production run.

  • With detailed log:

    If the parameter is set, a detailed log is created where all data records to be archived are listed.

  • Maximum conditions (header):

    There can be condition headers (KONH) in the system for which there are no longer any entries in the condition tables (Axxx) (due to overlapping of the dates). Here you can set whether and how many condition headers are to be checked for this. The setting only influences the run time of the program.

  • Document check only up to a maximum:

    If the document check is activated for applications (Customizing), the maximum number of documents to be checked (KONV) can be entered here. If this maximum number is exceeded, the system does not archive the applications with activated document check!

    This parameter not only influences the run time but also the storage requirement of the program. 100,000 documents correspond to approx. 1 MB of additional storage. If the parameter is set too high, the roll area may be too small, and the program terminates.

    Error message

Requirements

Customizing

  • Table T681H:

    can be maintained using view V_T681H. The following must be entered for VERWENDUNG (usage) and APPLIKATION (application) that are to be archived:

    • retention period in days:
      • The to-date of the conditions table must be less than or equal to the current date - retention period.
    • Document check:
      • If this is activated, only those conditions, for which there are no longer any documents (KONV) in the system, are archived.

      Proceed

  • Archiving object:

    Via the transaction 'SAR2', the archiving object 'SD_COND' must be maintained.

    Proceed

  • Structure of the archiving object:

    Via the transaction 'SAR1', the structure of the archiving object 'SD_COND' must be specified:

    Parent segment Segment

    KONH

    KONH SDKONDARCH

    KONH KONP

    KONP KONW

    KONP KONM

    Proceed

  • Customizing view for the archiving object:

    Using the transaction 'SAR3', the user can set, among other things, the log file, the size of the archive file, the variants of the deletion program, and whether it is to be started automatically.

    Proceed

Output

The following output can be issued:

  • Normal or detailed log:

    can be controlled using the parameter 'with detailed log'.

  • Archive file:

    Via the parameter 'Create archive file for test', you can control whether a physical archive file is created during the test run.

Business Attributes
ASAP Roadmap ID 208   Establish Archiving Management 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUOLSDVOKO 0 HLA0006007 Basic Functions 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_T681H V - View OV36 1000000000 Change Archiving Control 
History
Last changed by/on SAP  19981222 
SAP Release Created in