Subprograms

• File (field PRG)

Process code. It must be used in the process dictionary.

• Subprograms (field SUBPRG)

sub-program or function considered as re-usable and as a result to be capitalized on in this dictionary.

• Description (field ZINTIT)

• 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)

Whether the module is active or not has no impact on the execution of the sub-program.

• Type (field TYPASU)

Used to sort the sub-programs and functions in order to facilitate the search, for better reusability.

The sub-programs and functions should be sorted according to their purpose:

• Control
• Entry
• Selection
• Update
• Xsl (processing linked with the screen component)
• Return of a status
• Information search
• Calculation
• Other

• field WA

• Web services (field WEBS)

Used to specify that this sub-program or function can be generated for the web services. In fact, no process is shipped that can be directly used for the web services. However, a services web generationfunction is available for the objects and sub-programs identified as being suitable for generation.

• field PUBNAM

• Function (field FONCTION)

Check box that is used to make the distinction between the functions (called by the instruction Func ) and the sub-programs (called by the instruction Call.)

• Argument type (field TYPFCT)

This field should be assigned for the functions. The latter should be sorted according to the nature of their return argument.

• Char
• Integer
• Decimal
• Date
• etc.

• field TEXTE

Text loading the PRE "presentation" paragraph, in the record help. In the documentation management, the record help is identified by :

• documentation type = ASU
• documentation code = sub-program_process

• No. (field NUMLIG2)

• Code (field PARAM)

Each parameter is identified with a 10 character code (uppercase and numbers). There is no dictionary for these parameters.

• Description (field ZINTITPAR)

• Type (field TYPPAR)

Nature of the parameter :

• Char : Character string
• Integer : Integer number
• Decimal : Decimal number
• Date : date
• Title : Local menu
• Clob : text
• Blob : image

• Class code (field CODCLA)

• Dim. (field DIME)

Dimension of the parameter

• Argument type (field ADRVAL)

It indicates how the parameter is passed.

          by address ( a variable is necessary to pass the parameter. On exiting the sub-program, the value of any modified parameter is returned to the calling process).

          by value ( the parameter is passed by a variable or by a constant. On exiting the sub-program, the value of the parameter even if it is modified is not returned to the calling process).