DT445 Exit

DI000609 EXIT

Ident number of the exit. The ident number is automatically generated from the license number and a sequential counter. This ensures that an exit created by the customer does not accidentally have the same number as an exit shipped by PLANTA as part of an update of the standard system. Customer-specific exits therefore remain unaffected by updates.

Details

• General Information on the Customizing of Exits

DI000671 Exit name

Name of the exit

DI000937 Class

The value for the exit class can be compiled as a binary combination of the following values:

Values

• 1: Data item exit
  • Fetch exit (Option = 0) or date grid exit (Option = 2)
• 2: Data table exit (formerly classical 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 used in binary combinations with other exit classes). The values for the exit option are ignored. The exit must be recorded 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 called for each data record which is printed, and has no effect on the (value of the) current UIDO. The only values changed are those of objects which are not in the current UIDO. A print exit is called for each data record which is printed.
  • Technique: The _p_exit_call_obj function is used.
• 16: The exit is called immediately after the field contents have been sent off, even before the standard system has executed any check operations. The exit can, for example, create higher-level (parent) data records if they do not yet exist.
• 32: The exit calls an ORACLE stored function. The exit text is the source text for the call. The exit is called for each data record while saving. The DI for an exit of this type must have class 14.
• 64: The exit calls an ORACLE stored function. The exit text is the source text for the call. The exit is called for each data record which is actually found when performing a search. The DI for an exit of this type must have 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

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 DT Load, the 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 is entered from which the date is fetched and subsequently located on the grid.

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 application case) with source reference
• variable (for a less specific application case) without source reference

Example

• Hard coded exit
  • Exit 00000004 changes the period data records after a resource has been created or changed. The source reference specifies which program code the exit executes.
• Variably coded exit
  • Exit 00000028 copies the basic unit from the resource stem to the TAR record. Fetching a value from another table using a key is often required. Therefore, there is an exit that fetches the value on the basis of the
    • Option
    • DT
    • Source DI
    • Fetch DI
  • exit parameters. The exit can (alongside other exit parameters) also transfer the project text to the DT Task, for example. No source reference is specified for variable exits; the exit parameters define which function is executed.

DI002927 Parameter

Currently without function

DI010675 UF DI

Specifies the number of DIs the exit is assigned to

DI000665 Created by

When you create a record, 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

When you create a record, the creation date is automatically entered in this field.

DI000663 Changed on

When you modify a record, the modifying date is automatically entered in this field.

DI000666 Changed by

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

DI027353 Source text

DI027733 Source date item

Name of the Source DI

DI027734 Fetch data item

Name of the Fetch DI

DI027736 Fetch DT

Data table of the Fetch DI

DI027735 Source DT

Data table of the Source DI