This function is used to define the hierarchical organization of the folder. The entities can be viewed as control centers designed to structure the budget forecast and monitoring according to the entity type:

  • Entity controlling and monitoring a budget,
  • Entity consuming the budget,
  • Entity approving the budget allocated or the revisions carried out.

An entity is compulsorily assigned to an "Assignment entity" allowing the entry of the entity code at the immediate superior level. The number of levels is not limited, but the application has a search function for the entity supervisor code in the setup of WORKFLOW circuits which is limited to 9 entity levels. Therefore, it is not possible to search for the code of the supervisor of these entities beyond Level 9 in the framework of the signature controls.

The creation of entities is combined with the automatic creation of the corresponding analytical dimensions on a dimension type "Entity" (see Paragraph "Prerequisites"). Upon creation of an entity, the code and dimension type description created are the entity's.

  • Inquiring on the corresponding dimensions is carried out by "right click" on the selected Entity/dimension type.
  • Inquiring on dimension groups is carried out by a zoom on the dimension group.

The creation of analytical dimensions makes it possible to manage budget and analytical pyramids (Menu bar/Function/Pyramid generation), from any entity belonging to a hierarchy linked to a level 1 entity.

  • Inquiring on pyramid "Zoom pyramid" makes it possible to inquire on the graphical representation of said pyramid. By default, all the levels are displayed, starting from entity level 1.

The entity has an optional field "Company" used to assign the entity to a company. See "Company" field.

Deleting entities
  • It is prohibited to delete an entity if it is used by an envelope or a budget line (Company code grayed).
  • Deleting an entity also deletes the corresponding dimension.
  • It is prohibited to delete an analytical dimension in a dimension type Entity; You must delete the entity to delete the dimension.
Modifying entities
  • It is possible to add a Company code for an entity created without a Company code if this entity is not used by an envelope or budget line. In this case, adding a Company code triggers the deletion of all analytical dimensions created under this entity, and the creation of a dimension in the dimension type corresponding to the one of the entered company.
  • It is possible to delete a Company code for an entity if this entity is not used by an envelope or budget line (Company code not grayed). In this case, deleting the Company code triggers the deletion of the dimension created in the dimension type corresponding to the entered company and proposes to create dimensions on the available dimension types Entities.
Modifying pyramids
  • It is prohibited to modify pyramids on a dimension type "Entity" via the pyramid or the dimension groups.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

Presentation

Identification of employee

Close

 

Fields

The following fields are present on this tab :

Identifier

  • Identifier (field REFNUM)

 

 

 

Identity

  • Title (field CIVA)

 

  • Last name (field NAM)

 

  • First name (field SRN)

 

 

Management

  • Payroll mgmt (field FLGPAY)

 

  • Multi-contracts (field FLGMULCTR)

 

  • Casual worker (field FLGINT)

 

Close

 

Entry screen

Fields

The following fields are present on this tab :

Block number 1

Entity code (15 alphanumerical characters). The maximum length for this code must be the same as the maximum length of the corresponding section code. In case of modification, these two parameters must be modified.

  • field DESTRA

Description/title that can be translated related to the entity.

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.

SEEINFOThe 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.

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

Management

Entity supervisor code, to enter or search in the users table. If you wish to set up a signatures circuit, it is this code that will be recovered if you search for the approving entity or the responsible entity. Cf. Signature circuit.

  • Budget entity (field ENTFLG)

This box should be checked to indicate that the entity has the autorization to create budget envelopes, budgets and budget lines, depending on the autorized access codes.

  • Approval entity (field ENTAPP)

Entity autorized to approve a budget, whichever approval level. If the approval entity is not entered by the user, this zone will display automatically the code of the entity that is being created or modified. Only existing entities from the entities table can be entered.

Assignment entity with the next greater level to enter or search in the list of existing entities. As the creation of an entity automatically generates the creation of a corresponding analytical section, this zone has a tunnel that makes it possible to access to the analytical section.

  • Level (field LEV)

Entity level in the entity hierarchy. Each entity owns an attachment entity of a higher level, except for level-1 entities. This information makes it possible to generate automatically the pyramid of entities/dimensions.

Accessibility

  • Active (field ENAFLG)

This box is used to specify whether the current record must be activated or not:

  • If this box is checked, the current record can be used in other records (documents, parameters, etc.) or during mass processing,
  • if it is not checked, the current record is considered to be inactive and it cannot be selected.
  • Company (field CPY)

Code of the entity assignment company. Optional field that used to specify entities common to several companies. If the company code is entered, the creation of an entity generates the automatic creation of the corresponding analytical section on the entity dimension specified in the assignment reference of the company with the type "Entity". The selection only displays the companies which main ledger is "flagged" "Operational budgets".

If there is no entry in this zone, a dialogue box displaying all the dimensions with the type "entity", is used to select the dimension on which this section must be created.

An entity of basic level that includes a company code can be attached only to an assignment entity that includes the same company code or that has a blank company code. As soon as an entity level is attached to an entity with a blank company code, the upper levels of this entity can only be entities with a blank company code.

  • Validity start date (field VLYSTR)

Optional field, makes it possible to enter a start date relating to the entity validity.

  • Validity end date (field VLYEND)

Optional field, makes it possible to enter an end date relating to the entity validity.

This access code makes it possible to prohibit access to the current record for some users.

If the field is populated, only users that have this access code with read access rights (and write access rights respectively) can view (or with write access rights, modify) the record.

Grid 'entity'/dimension dimension types

This column displays the list of analytical dimensions with the type "Entity".

If the entity has a company code, only the corresponding dimension is displayed. This cannot be modified and the corresponding checking cannot be cancelled.

If the entity does not have a company code, all the dimensions with the type "Entity" are displayed, the user has to select the dimensions on which they wish to create an analytical dimension. It is possible to generate the creation of another section a posteriori by checking one of the displyed dimensions. If you cancel the checking of a dimension, it will generate the cancellation of the corresponding section. This cancellation will not be possible if no envelope has been created for this entity in this dimension.

  • Selection (field COCHE)

This column can be reached if the entity does not have a company code and makes it possible to select the "Entity" analytical dimensions on which an analytical section has to be created.

Close

 

Action icon

Dimensions

A "right click" on the line of a selected dimension type makes it possible to access the inquiry of the analytical dimension on the determined dimension type.

The modification of this dimension is forbidden directly within the operating budgets:

  • Function "Copy of an analytical dimension type" has been inhibited from the dimension.
  • It is the same for the function GESCCE, when the dimension comes from an entity or a budget envelope (Operational budgets).
  • Function "Dimension inquiry" presenting the allocations carried out on the dimension remains accessible

 

Close

 

Tab Contract

Presentation

Entry and inquiry of information concerning a new employee in the company and the characteristics and conditions of his/her future contract (contract type, position, income, schedule, etc.) 
SEEINFO If the "Multi-contracts" box is ticked in the header, several contracts can be created for one employee.

 

Fields

The following fields are present on this tab :

Grid Dates

  • Date (field CTRDAT)

 

Contract

  • Receipt date (field WCTRDAT)

 

  • Arrival time (field WETRTIM)

 

  • Career follow-up (field WSUICAR)

 

 

  • field WCLCDOC

 

  • field WCLCLIB

 

  • Extracted DUE (field WFLGDUE)

 

 

 

  • Duration (field WNBRPER)

 

  • Unit (field WPERCON)

 

  • Contract end (field WENDCON)

 

  • Trial period end (field WENDTRY)

 

 

  • Marital status (field WSITFAMA)

 

  • Dependent adult(s) (field WADT)

 

  • Dependent child(ren) (field WCHD)

 

  • Child disability (field WCHDDIS)

 

  • Number of holders (field WNBRHLD)

 

  • Spouse disability (field WJNTDIS)

 

  • Pension (field WCOIPLN)

 

Job

  • Job type (field WTYPJOB)

 

  • Student (field WSCHJOB)

 

  • PT rate (field WRATMIDWRK)

 

 

 

 

 

  • Payslip title (field WJOB)

 

 

  • Basic salary (field WMTH)

 

 

Classification

  • Coefficient (field WCOE)

 

  • Index (field WIND)

 

  • Rank (field WGRA)

 

Exemption

 

  • Period (field WEXOSTR1)

 

  • field WEXOEND1

 

 

  • Period (field WEXOSTR2)

 

  • field WEXOEND2

 

 

  • Period (field WEXOSTR3)

 

  • field WEXOEND3

 

 

  • Period (field WEXOSTR4)

 

  • field WEXOEND4

 

 

Tab Contract

Presentation

If there must be an automatic generation of arrival documents for this new employee, then tick the type(s) of the given documents.

../FCT/GESTXC_CLAUSPE.GIF The icon button [Particular Clauses] is used to establish, by document type, the particular clauses linked to the employee.
../FCT/VIEWING.GIF The icon button [View] is used to view the arrival document, when it already exists.

Close

 

Fields

The following fields are present on this tab :

Contract

  • Date (field WCTRDATA)

 

 

Multi-employer

  • Multi-employer (field WSEVEMP)

 

  • Period start (field WSTRDATSEV)

 

  • Period end (field WENDDATSEV)

 

Time

  • Weekly hours (field WHRSWEK)

 

  • Monthly hours (field WHRSMTH)

 

  • Annualized no. days (field WNBRDAYCTR)

 

Multiple jobs

  • Multiple jobs (field WSEVCTR)

 

Contribution funds

 

 

Yearly declaration

 

 

 

Documents to generate

Block number 8

  • Add (field WADD)

 

Close

 

Tab Casual worker in entertainment industry

Fields

The following fields are present on this tab :

Contract

  • Date (field WCTRDATA)

 

 

Multi-employer

  • Multi-employer (field WSEVEMP)

 

  • Period start (field WSTRDATSEV)

 

  • Period end (field WENDDATSEV)

 

Time

  • Weekly hours (field WHRSWEK)

 

  • Monthly hours (field WHRSMTH)

 

  • Annualized no. days (field WNBRDAYCTR)

 

Multiple jobs

  • Multiple jobs (field WSEVCTR)

 

Contribution funds

 

 

Yearly declaration

 

 

 

Documents to generate

Block number 8

  • Add (field WADD)

 

Close

 

Action icon

Payroll

 

Close

 

Reports

By default, the following reports are associated with this function :

 LISSEC : List of dimensions

This can be changed using a different setup.

Specific buttons

This button is used to confirm the final hiring of the employee, and creates a new tab in theEmployee record and in the Contract record.

This button is used to view the potentially generated arrival documents.

Menu Bar

Function / Generate pyramid

This function is used to generate the entity/dimension types pyramid. This generation can be carried out from any entity of the hierarchy. The pyramid generated will include all the dimension groups and dimensions attached to the level 1 entity, on the dimension type determined by said entity.

A report indicates if the generation was carried out correctly, the number of groups, levels and entities/dimensions created.

Zooms / Dimension

Zooms / Dimension Group

If the pyramid has been generated, this zoom is used to access the analytical dimension group inquiry.

The modification of dimension groups is forbidden directly within the operating budgets:

  • Functions "Pyramid duplication" and 'Automatic generation" have been inhibited from the inquiry of dimension groups.
  • It is the same for the function GESCYRY, when the dimension comes from an entity or a budget envelope (Operational budgets).

Zooms / Pyramid

If the pyramid has been generated, this function gives access to the inquiry on the pyramid of the analytical dimension types generated upon creating entities. By default, all the dimension groups and dimensions are displayed from the level 1 entity. In order to inquire a partial pyramid, the "Start group" code must be modified. The graphical representation starts from the selected group and unfolds its sub-levels.

 The modification of the pyramids is forbidden directly within the operating budgets:

  • Functions "Pyramid duplication" and 'Automatic generation" have been inhibited from the pyramid inquiry.
  • It is the same for the function GESCYM, when the dimension comes from an entity or a budget envelope (Operational budgets).

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Only companies/sites with their main analytical ledger set to Operating budgets are authorized.

The Company code entered is attached to a ledger not flagged "Operating budgets". Modify the Company code or check the general structure setup if the said Company code is correct.

Incorrect entity

The entity code entered does not exist in the entity list. Modify this code or select a code from the entity list.

The entity cannot be linked to a different company entity

The assignment entity code entered does not have the same Company code as the entity. The modification of an assignment entity can only be performed on entities sharing the same company code, or with a blank company code. Modify the assignment entity code.

This message also appears upon duplicating an entity which is not attached to a company, to create an entity attached to a company, when the assignment entity is modified. In this case, it is necessary to enter the company's code prior to modifying the assignment entity's code.

A child entity has a company whose value is blank. As a consequence, the company of this entity can only be blank

The Company code of the attached entity is blank. The company code of the assigned entity must also be blank.

Company incompatible with the attached entity/entities

Modify the Company code of the entity. This entity is an assignment entity having attached entities whose Company code is different from the entered code. The code of this entity must be the same as the one of the assigned or blank entities. The company code of this entity can be set to blank, but provided that the assignment entity of this particular entity has a blank company code. If this is not the case, the Company code must be the same as the one of its assigned entities.

Attached entities contain different companies, the company code of this entity must be blank

This message is displayed upon entering the company code of an assignment entity with a blank code and attached entities with different or blank company codes.

An entity cannot be linked to itself

The assignment entity code entered is the same as the entity code. Modify the assignment entity code or select an assignment entity in the list.

The entity cannot be attached to one of its child entities

You are attaching an entity to one of its attached entities. This is incoherent, please modify your entry.

The entity cannot be linked to a different company entity

You are modifying the assignment entity of the said entity, but this assignment entity has a Company code different form that of the entity being modified. The entity can only be attached to an entity having the same Company code, or to an entity having a blank Company code field.

Tables used

SEEREFERTTO Refer to documentation Implementation