Entry Transactions

• Transaction (field DIA)

A transaction is used to define the entry framework for a journal. It is possible to choose the account structure to be applied, and to define a default value and a specific control for each field. The transaction is identified by an alphanumerical code of one to five characters that will be used on journal entry to select the transaction.

The STD code transaction is used to view all the journals, irrespective of the transaction of origin.
Similarly, the STDLC code transaction enables the display and/or modification of batches, irrespective of the transaction of origin.

• Description (field DESTRA)

Full title of the current record.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Short description (field SHOTRA)

The short description replaces the standard description when display or print constraints require it.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Batch entry (field FLGLOT)

If this check box is selected, the current entry transaction is only used for a batch entry and the Counterpart fields do not display on the Lines tab.
 A batch entry transaction is necessarily of type 'Column'.

• Active (field ENAFLG)

This box is used to specify if the tax determination rule must be activated or not:

• if this box is checked, the tax determination rule is used in other records (documents, setup, etc.) or during mass processing,
• if it is not checked, the tax determination rule is considered to be inactive and it cannot be selected.

• Legislation (field LEG)

Non-compulsory field containing the legislation code (miscellaneous table 909).

The entered value is used upon creation and validation of the folder and upon addition of data during legislation copy.

The data concerning the requested legislations and the common data (legislation code empty) on folder creation.

Only the records concerning the folder legislations are retrieved on folder validation.

The Legislation field is also used as a filter and checked upon movement selection and entry (entry of invoices, payments, journals etc.).

If the field is empty, the current record can be used whatever the legislation of the company concerned by the movement.

• Group (field GFY)

An entry transaction can be used on a company or a dedicated group. Enter the code of the group or the company to limit the use of the entry transaction.

• Access code (field ACS)

This access code makes it possible to prohibit access to the transaction for certain users. If the field is assigned, only those users who have this access code in their profile will be in a position to enter or view these entries using this transaction. A user will be able to use a transaction if they have been granted the execution rights for said transaction (see the Access codes documentation).

• Validity start date (field VLYSTR)

These dates define the period during which the entry transaction can be used. If the start date is not entered, the transaction can be used from the very first day of the first financial year. If the end date is not given, the transaction can be used from the start date without limit of time.

• Validity end date (field VLYEND)

• View left list (field FLGBRO)

If checked, this box will authorize on journal entry the display of all the journals entered with the current transaction in the left list.

• No. currency rates (field NBRRAT)

Number of currencies that can be taken into account by the transaction (limited to five).

• No. of fixed columns (field NBRCOL)

The first N columns specified in this field remain visible on the screen when scrolling.

• BP search (field BPRFLG)

This field makes it possible to define the search order of the collective account.
For instance, when a Business Partner is both a customer and a supplier, the field specifies for which type of BP the collective account to be allocated should be looked for.

The search order is defined as follows:
1 = customer
2 = supplier
3 = carrier
4 = factor
5 = sales rep.
6 = miscellaneous BP.

For instance: 612 means that the search will be conducted in priority on the collective account associated with the accounting code of type "miscellaneous BP", then to the accounting code of type "customer" and finally to the accounting code of type "supplier".

• Entry type (field TYPENT)

The entry of a journal can be performed according to three types:

• In column mode: each ledger type (set up in the transaction) is a column. On journal entry, foe each line, all the manual ledgers are visible.
• In line mode: on journal entry, the first line corresponds to the first ledger specified in the list of ledgers for the current transaction. An entry can be created on any line but it has to meet the constraints of the social ledgers. It is entered as a whole for a type of ledger and it is then propagated to the others by validating using the Create button. Upon journal entry, the identifiers link the account concerned with the propagation. On line entry, dimension types can be entered on the line of the social ledger and then passed down to the IAS and analytical ledgers by validating by means of the Create button. The default values of the IAS and analytical ledgers are submitted upon entry of the line of the social ledger.
• In tab mode: the 'tab' configuration is only available on inquiry. A tab corresponds to a ledger type. The whole accounting entry is available on all ledger types, either automatic or manual.

• Single page (field FLGPAG)

If the current entry transaction fields are not numerous, journal entry will be performed on a single page.

• field NBRGDA

• Account core model (field GCM)

Specify the account core models for which account structures can be applied to the current entry transaction.
 An account structure is necessarily linked to a chart of accounts, and, as a consequence, to a model.

• Account structure (field DIAACC)

If needed, specify an entry model that can be used only within the account core model selected beforehand.
If no chart of accounts has been specified, the current transaction will be used irrespective of the entered accounts.

• Ledger type (field LEDTYP)

Use this field to define the ledger type concerned by the journal balance. In this function, only Manual ledgers can be accessed.

You can read the balance on the selected ledger and balance the account for that ledger type.The propagation then initializes the accounts for the non automatic and non prohibited ledger types. This initialization process is based on the entry type setup and account setup.

The propagated amount is the one calculated on the main general ledger in transaction currency. This amount is then converted into the currency of the propagated ledgers.

When generating the journal balance, the propagation depends on the selected entry type.

If the two entry types are not consistent, the balance process must be launched on each non-propagated manual ledger where the account needs to be balanced.

Examples

Selected ledger type = Social, Generation type = Actual

In this case, when generating the balance, the propagation is global.

Selected ledger type = Legal; Generation type = Actual

Here, the propagation is incomplete. The IAS ledger is not propagated.If you want to balance the account on the IAS ledger, relaunch the balance process for this ledger type using an entry type that only authorizes IAS ledgers.

For an automatic ledger type, the amounts in transaction currency are not calculated from the balance.

They are the same as the currency amounts calculated for the original manual ledger. The ledger amounts for the automatic ledger are calculated by converting its currency amounts according to the journal entry rates.

• Balanced entry (field FLGEQL)

In a ledger, excluding the Social ledger, the entry can be unmatched. If this box is checked, the program will force the user to perform a matched entry.

• field NBRFLD

• Block (field MSK)

Non-modifiable dentifier of a block of fields in the "Header" tab of the journal entry.

• Description (field FLDDES)

Field identifier.

• Entry mode (field DAC)

Field with a scroll-down list, to authorize, or not, the entry of a field, according to three modes:

• entered: the field is loaded with a default and modifiable value,
• displayed: the field is loaded with a default and non-modifiable value,
• hidden (suggested depending on the case): the field is hidden.

• Default value (field DEFVAL)

Each field, editable or not, can benefit from a default value. The default value can be indicated:

• in the form of an Adonix expression, for instance, to indicate the due date, "date$" makes it possible to assign the day's actual date as the default value for the due date.
• in the form of a constant wetween brackets, for instance, "EUR" is used to assign the EUR character string as the default value for the currency field.

If the default value is not entered, the program will assign a default value based on the context.

Some instances of default values: DES field

• string$(nolign>1,DES(max(0,nolign-2)))
  To propose the title of the previous posting line.
• string$(nolign>1,DES(0))
  To propose the title of the first posting line.

• Control (field CTL)

This field refers to a Control table, if any, that is used te perform validity controls on each field, that is to say:

• a list of possible values,
• a list of prohibited values.
• ranges,
• reference to a table (refer to the Control tables documentation).

• field NBRFLD

• Description (field FLDDES)

Field identifier.

• Entry mode (field DAC)

Field with a scroll-down list, to authorize, or not, the entry of a field, according to three modes:

• entered (single choice for the BP, Accounts, Debit and Credit lines): the field is loaded with a default and modifiable value,
• displayed: the field is loaded with a default and non-modifiable value,
• hidden: the field is hidden.

• Form mode (field CRD)

This field authorizes or not the display of the screen in record mode:

• No: the display is only available in grid mode,
• Yes: the display is available in grid and record mode.

• Default value (field DEFVAL)

Each field, editable or not, can benefit from a default value. The default value can be indicated:

• in the form of an Adonix expression, for instance, to indicate the due date, "date$" makes it possible to assign the day's actual date as the default value for the due date.
• in the form of a constant wetween brackets, for instance, "EUR" is used to assign the EUR character string as the default value for the currency field.

If the default value is not entered, the program will assign a default value based on the context.

Some instances of default values: DES field

• string$(nolign>1,DES(max(0,nolign-2)))
  To propose the title of the previous posting line.
• string$(nolign>1,DES(0))
  To propose the title of the first posting line.

• Control (field CTL)

This field refers to a Control table, if any, that is used te perform validity controls on each field, that is to say:

• a list of possible values,
• a list of prohibited values.
• ranges,
• reference to a table (refer to the Control tables documentation).

• Default dimensions (field CDE)

If it is entered, this field specifies the default dimension to be taken account if no default value has been defined at account level or at the level of each dimension type of the transaction.

• field NBRFLD

• Dimension type code (field DIE)

Select any dimension type code in the database. The dimension type code will load the journal entry with the default values chosen in the other fields of the grid.

• Entry mode (field DAC)

Field with a scroll-down list, to authorize, or not, the entry of a field, according to three modes:

• entered: the field is loaded with a default and modifiable value,
• displayed: the field is loaded with a default and non-modifiable value.

• Default value (field DEFVAL)

Each field, editable or not, can benefit from a default value. The default value can be indicated:

• in the form of an Adonix expression, for instance, to indicate the due date, "date$" makes it possible to assign the day's actual date as the default value for the due date.
• in the form of a constant wetween brackets, for instance, "EUR" is used to assign the EUR character string as the default value for the currency field.

If the default value is not entered, the program will assign a default value based on the context.

Some instances of default values: DES field

• string$(nolign>1,DES(max(0,nolign-2)))
  To propose the title of the previous posting line.
• string$(nolign>1,DES(0))
  To propose the title of the first posting line.

• Control (field CTL)

This field refers to a Control table, if any, that is used te perform validity controls on each field, that is to say:

• a list of possible values,
• a list of prohibited values.
• ranges,
• reference to a table (refer to the Control tables documentation).