Skip to main content
Skip table of contents

DT445 Exit

DI000609 EXIT

ID of the exit. It is composed of the license number and an incrementing counter. This ensures that an exit created by the customer does not accidentally receive the same number as an exit supplied by PLANTA as part of an update to the standard system. This way, individual exits are not affected by updates.

Details

DI000671 Exit name

Name of the exit

DI000937 Class

The value for the exit class can be combined in binary form from the following values.

Values

  • 1: Data item exit
  • 2: Data table exit (formerly traditional exit)
    • For exit class 2, the Option data field must necessarily be filled.
  • 4: Value range exits: These are only used within the program and are never customized.
  • 8: Print exit (must not be combined in binary form with other exit classes). The values for exit option are ignored. The exit must be entered in a data item of class 0. Print exits do not work for data items with class <> 0, nor do they take effect for data items in print areas. The print exit is opened per record and has no impact (as far as the value is concerned) on the current UIDO. Only values of objects that are not in the current UIDO are changed. Print exits are opened per printed record.
    • Technology: The p_exit_call_obj function is used.
  • 16: Exit is called directly after the field content has been sent, even before the standard has performed any check operations. In the exit, for example, higher-level data records can be created if they do not yet exist.
  • 32: Exit calls an ORACLE stored function. The exit text is the source text of the call. The call is effected for each record upon saving. The ID for such an exit must be class 14.
  • 64: Exit calls an ORACLE stored function. The exit text is the source text of the call. The call is effected for each record actually found in the search. The ID for such an exit must be class 0.

DI000938 Option

Values

  • For Class = 1:
    • 0: Fetch exit: is used to fetch DI values from other data tables into virtual DIs. The DT, Source DI, and Fetch DI parameters must be filled.
    • 2: Date grid exit. determines the grid position for the date DI shown in a fetch DI, and enters the resulting value in the DI which is assigned to the exit. The Option, Fetch DI, and Grid parameters must be filled.
  • For Class = 2:
    • 1: before the creation of a record
    • 2: after the creation of a record
    • 4: before the modification of a record
    • 8: after the modification of a record
    • 16: before the deletion of a record
    • 32: after the deletion of a record
    • 64: before the deletion of a record (before the database check)
    • 128: check when inserting a record - must be assigned to a 1:1 ID if the exit refers to part of it.
    • 256: check when modifying a record after it has been validated, i.e. the exit is called whenever a field is changed.

DI001614 DT

For Class = 1 and Option = 0

  • The entry here is the number of the data table from which the DI value (e.g. name) is to be fetched.

Caution

  • Filling the DT field in the Exits module is no longer required since the specification of the Fetch DI already implies the data table.

DI001615 Source DI

For Class = 1 and Option = 0

  • Here, the number (ID) of the source DI (DI which corresponds to the primary key of the fetch DT) of the data table in which the DI value (e.g. name) is to be fetched is entered.

Note

  • If the Source DI consists of a compound DI (e.g. Task), the first DI from the 1:1 ident is used (e.g. Task in the Load DT, project DI 001515 from Load).

DI001616 Fetch DI

For Class = 1 and Option = 0

  • Here you can enter the DI number of the fetch DI from which the DI value (name) is to be fetched.

For Class = 1 and Option = 2

  • Date grid exit. Here, the DI from which the date is fetched is entered and then gridded.

DI002351 Grid

For Exit class

1 and Option

2

  • 2: day
  • 3: week
  • 4: month
  • 5: quarter
  • 6: year:

DI000099 Source reference

Specifies the source reference (number) if the exit has its own source. An exit can be programmed as follows:

  • fixed (for a specific use case) with source reference
  • variable (for a less specific use case) without source reference

Example

  • Hard-coded exit
    • Exit 00000004 changes the period records after a resource has been created or changed. The source reference specifies which program code the exit executes.
  • Variably programmed exit
    • Exit 00000028 copies the basic unit from the resource stem to the TAR record. Fetching a value from another table via an ID is frequently desired. Hence, there is an exit which fetches the value based on the
    • exit parameters. The exit can (with other exit parameters) also transfer the project text to the DT operation. No source reference is specified for variable exits; the exit parameters determine which function is executed.

DI002927 Parameter

Currently without function.

DI010675 UF DI

Specifies to how many DIs the exit is assigned

DI000665 Created by

When a record is created, the ID (code) of the logged-on user is automatically entered in this field. The creating user is also the owner of a record.

DI000610 Created on

Upon creation of a record, the time of creation is automatically entered here.

DI000663 Changed on

When a record is modified, the modification date is automatically entered here.

DI000666 Changed by

When a record is modified, the ID (code) of the logged-on user is automatically entered in this field.

DI027353 Source text

DI027733 Source DI

Name of the Source DI

DI027734 Fetch DI

Name of the Fetch DI

DI027736 Fetch DT

Data table of the Fetch DI

DI027735 Source DT

Name of the Source DI

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.