JOURNAL: Before controls and validation of the journal

This entry point is used to insert additional logic during the validation of an automatic journal.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

A log file is normally open (can depend on the context).

Different call cases

The entry point " PIECE " is called just before the recording of the journal.

Available variables and masks

The journal is stored before its validation in the GACCENT0 [HAE0], GACCENT1 [HAE1] and GACCENT2 [HAE2] screens. All the fields in these screens are accessible and can be modified on the condition of respecting the general validation rules for a document, if new fields are added to the accounting document tables these must be added in these screens.

Open tables

The tables that can be used are as follows: 

GAUTACE [GAU]

Automatic journal

COMPANY[CPY]

FACILITY[FCY]

TABCUR[TCU]

In addition the triggering table and the linked tables are on line.

Other tables can be on line according to the call context.

CLEGRP: Document lines grouping

This entry point is used to take control in order to identify the grouping of a document line.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

A log file is normally open (can depend on the context).

Different call cases

Entry point CLEGRP is called just before the initialization of the NOL variable (index of the line about to be posted).

Available variables and masks

The journal is stored before its validation in the GACCENT0 [HAE0], GACCENT1 [HAE1] and GACCENT2 [HAE2] screens. All the fields in these screens are accessible and can be modified on the condition of respecting the general validation rules for a document, if new fields are added to the accounting document tables these must be added in these screens. Local variable CLEGRP contains the grouping fields separated by '/'. This variable can be completed.

Open tables

The tables that can be used are as follows: 

GAUTACE [GAU]

Automatic journals

COMPANY[CPY]

Company

FACILITY[FCY]

Sites

TABCUR[TCU]

Currencies

 GAUTACED [GAD]

Auto. journal line

 GACCOUNT[GAC]

Account for the current line

 BPARTNER[BPR]

BP

In addition the triggering table and the linked tables are on line.

Other tables can be on line according to the call context.

LIGNE: Journal line entry point

This entry point is used to take control each time a document general line is filled.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

A log file is normally open (can depend on the context).

Different call cases

The entry point " LIGNE " is called on the creation of each line in the journal.

Available variables and masks

The journal is stored before its validation in the GACCENT0 [HAE0], GACCENT1 [HAE1] and GACCENT2 [HAE2] screens. All the fields in these screens are accessible and can be modified on the condition of respecting the general validation rules for a document, if new fields are added to the accounting document tables these must be added in these screens. The local variable NOL contains the index for the line that has just been created.

Open tables

The tables that can be used are as follows: 

GAUTACE [GAU]

Automatic journals

COMPANY[CPY]

Company

FACILITY[FCY]

Sites

TABCUR[TCU]

Currencies

 GAUTACED [GAD]

Auto. journal line

 GACCOUNT[GAC]

Account for the current line

 BPARTNER[BPR]

BP

In addition the triggering table and the linked tables are on line.

Other tables can be on line according to the call context.

LIN_ANA: Journal analytical lines entry point

This entry point is used to take control each time a document analytical line is filled.

Context and operating method

Transaction

There is one transaction in progress.

Log file

A log file is normally open (can depend on the context).

Different call cases

The entry point "LIN_ANA" is called on the creation of each analytical line in the journal.

There are 2 possible contexts for the analytical loading:

- Automatic journal is set up with an Analytical table, the entry point will be called for each line read in the analytical table. The analytical lines are stored under the VENTILE2 [VT2] mask and the pointers (start and end) are stored under the GACCENT2 [HAE2] mask via the PTV(NOL) & PTF(NOL) fields.

- Automatic journal is set up without Analytical table, the entry point will be called once. The line will still be stored under the VENTILE2 [VT2] mask. According to the general lines setup, several general lines can be grouped in one single general line, but the analytical lines are not grouped and the pointers (start and end) are stored under the GACCENT2 [HAE2] mask via the PTV(NOL) & PTF(NOL) fields.

The entry point is not called when the general line is linked to a prior analytical distribution (Data defined under the GESDSP function)

Available variables and masks

The journal is stored before its validation in the GACCENT0 [HAE0], GACCENT1 [HAE1], GACCENT2 [HAE2], VENTILE2 [VT2] screens. All the fields in these screens are accessible and can be modified on the condition of respecting the general validation rules for a document, if new fields are added to the accounting document tables these must be added in these screens. The local variable NOL contains the index for the general line that has just been created (access to the HAE2 mask). The local variable VENT contains the index for the analytical line that has just been activated (access to the VT2 mask).

Open tables

The tables that can be used are as follows: 

GAUTACE [GAU]

Automatic journals

COMPANY[CPY]

Company

FACILITY[FCY]

Sites

TABCUR[TCU]

Currencies

 GAUTACED [GAD]

Auto. journal line

 GACCOUNT[GAC]

Account for the current line

 BPARTNER[BPR]

BP

In addition the triggering table and the linked tables are on line.

Other tables can be on line according to the call context.

OPNTAB: Tables opening entry point

This entry point is used to take control after opening the tables.

Context and operating method

Transaction

There is one transaction in progress.

Log file

A log file is normally open (can depend on the context).

Different call cases

The "OPNTAB" entry point is called after opening the tables and declaring the variables, and before reading the automatic journal. It is used to define other tables using the same abbreviations.

Available variables and masks

The masks and variables are not yet initialized

Open tables

The tables that can be used are as follows: 

COMPANY[CPY]

Company