This function is used to define the archiving and purging procedures for a table and possibly any associated detail tables, as well as all the tables linked to it in the dictionary and whose cancellation code is set to deletion. Taking for example the archiving formula SOH for the customer order table SORDER, the tables SORDERP, SORDERQ etc are also archived.

These archive formulas are used during the archiving / purging function.

It is a supervisor process, which starting from the archiving formulas and the parameterization, will carryout this archiving and purging. It is however possible to add customization in a process whose name will be identified in a purging formula.

Remarque importante

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

The entry of the purging formulas is carried out in a tab.

Block number 1

Code (field COD)

This code identifies a purging formula.

Description (field ZDES)

Characteristics

Short description (field ZDESSHO)
Activity code (field CODACT)

An activity code is used to:

  • Make an element optional in the dictionary if the value associated with the activity code is null
  • Identify the specific/custom elements if they are marked with a code starting with X, Y, or Z
  • Size a maximum number of lines when the activity code marks elements from a grid

If the activity code is disabled:

  • The marked element will not be useable
  • The associated code will not be generated nor activated
Module (field MODULE)

Select a module for the setup.

Use this field to specify if the screen has to be created in the folder database. This is the case when the module linked to the screen is active on the folder.

Processes

Active (field ENAFLG)

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used by recalling their code:

  • On other records such as documents and settings
  • On mass processes

The authorizations for a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature workflow.
Standard processing (field CTLTRT)

Optional processes can include miscellaneous sub-programs that will be called during the execution of the archiving . See the characteristics of these sub-programs. The vertical developments must start with X; the specific/custom developments must start with either Y or Z. The update of the specific/custom process does not require protection by activity code.  
Specific processing (field SPETRT)

Grid Tables

Table (field TBL)

Tables to be archived and purged.

Linked table (field LNKTBL)

It is possible to assign a principal table as well as these detail tables. As a consequence, for a detail table, the principal table with which it is associated will be specified in this field. For a detail table, no other parameter will be entered. A table can be considered as a detail table if its primary key is made up of the primary key of the principal table + an identifier. It is possible to enter up to 20 detail tables per principal table.

Company (field CPYFLD)

These fields (Company, Site and Date) are used to identify the fields in the principal table containing respectively the company, the site, the date. These are the standard criteria to filter the records in the principal table to be archived.

Site (field FCYFLD)
Date (field DATFLD)
Formula for creating data to be purged (field FRM)

This field is used to define the additional filters for a formula to archive the records. The purge function uses this formula when the archiving is not activated by the parameterization.

Specific Buttons

Copy

This button is used to copy an archiving formula to another folder Warning, the associated processes are not copied.

Important remark

It is important to note that the standard processes are passed on when the archiving or purging condition is not sufficient, and these standard processes must not be changed. Their poorly considered modification can provoke archiving and purging that could place the database stability in danger. It is recommended, if it is necessary to modify the archiving / purging rules, to complete the archiving formula by defining for example more restrictive criteria and to write if necessary the deletion of additional data created in the specific/custom tables in the specific/custom process. (see the methodology).

 

Copie

Documentation / Paragraphs

This menu item allows access to the documentation management on the first paragraph of the documentation (if there is one) associated with the current record.

Documentation / Links

This menu item allows access to link management. It is used to define the links between the current record and other records (for example, the links between functions and parameters). These links are specific to the documentation and are used to load the generation of documentation structures.

Documentation / Generation

This menu item launches a documentation generation. You can also launch it from the Generation button at the bottom of the screen.

You can launch three types of generation one by one or simultaneously

  • The generation of the documentation structure from the dictionary (ADOCUMENT, ADOCBLB, and ADOCCLB tables)
  • The generation of the documentation from the previous tables
  • The generation of the field documentation

The range suggested by default takes into account the current record, but you can modify it at launch time.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Table not defined

The table entered in the "Linked table" field must have been entered as a table to be processed in the "table" field.

XXXXXX : Too many lines in this table

An attempt has been made to enter more than 20 detail tables for a principal table.

XXXXXX : Field does not exist in table YYYYYYY

Table YYYYYYY has been linked to a principal table. At least one primary key field for the principal table must exist in the detail table YYYYYYY.

XXXXXX : Incorrect data type

Table YYYYYYY has been linked to a principal table. The XXXXX field of the primary key for the principal table exists in the detail table but it is of a different data type.

Field does not exist in the XXXXXX table

The field identification fields (company, site, date) must reference a field that exists in the principal table.

Data type incorrect

The Company Zone field must reference a zone of the type CPY or FCY.
The field Site Zone must reference a zone of the type CPY or FCY.
The field Date Zone must reference a zone of the type date.

 

Tables used

SEEREFERTTO Refer to documentation Implementation