Refer to documentation Implementation
The screen is made up of a first part identifying the workload analysis and a table allowing the definition of the selection criteria of the entities to be analyzed.
The result of the workload analysis will be presented in a form of a table.
Presentation
Identification of the workload analysis
An analysis is identified by a unique sequential number attributed by the system and by description.
The calculation of the workload can only be launched one time for a given analysis, the loads of an analysis can not be actualized..
There exist two types of workload analysis :
· the « short-lived » analysis which one doesn’t desire to keep the trace and whose indicator « to be conserved » is not ticked
· the « permanent » analysis which one desire to reuse and whose indicator « to be conserved » is ticked.
Distinct purge codes were defined for these two types of analysis, so as to temporarily conserve the « short-lived » analysis.
A workload analysis may make reference or not to an analysis template pre defined on the analysis models table. If it is the case :
· The type of entities considered in the analysis are imposed by the template
· The available selection criteria are imposed by the template
· The operands and the value of the selection for each of the criteria are modifiable for each analysis.
If the analysis does not refer to a template then the selection criteria of the entities to be considered in the analysis should be directly keyed in during the creation of the analysis.
The zone « depositor » allows to limit the analysis of entities of a particular depositor and can be imposed by the analysis template.
Selection criteria of workload analysis
Each line of the table corresponds to a selection criteria or to a logical operator « OR »
Two lines of consecutive criteria related to the same table are linked by the logical operator « AND ». The explicit addition of the operator « OR » between these two lines allows to modify this rule by default..
Two lines of consecutive criteria related to two distinct tables are linked by the logical operator « OR ».
Example :
Table | Field | Operand | Value | Formula |
Expected input header
Input Movements | Status Date of appointment
Status | Greater than or equal
Indifferent | 3 4 |
Date$ |
The analysis template represented by the above-mentioned table considers :
· The expected inputs in status greater than or equal « 3 » andof the carrier CALBER
· The expected inputs to be received today whatever their status or their carrier
· The DO in status greater or equal to « 4 »
· The DO launched today
· The input movements
· The transfer movements
The selections concern the following tables : Delivery Orders, Expected Input headers, Direct Input headers, Input movements, Output movements, Preparation Orders, Dock management, Receipt header, storing list, Transfer movements and Waves.
Anyway, the selections on the status of the entities are implicitly carried out, in such a way that only the active entities are considered, because we are only interested on the workload left to be processed.
Close
Fields
The following fields are present on this tab :
Block number 1
| Numerical sequence automatically assigned by the system upon creation of the analysis. This number is an information specific to the site, all depositors included. This information features a unique access key to an analysis. |
|   |
| Specifies whether or not the analysis must be kept. |
| Groupof selection criteria of entity records. |
| Depositorcode if the analysis is single depositor. |
Calculation
| No help linked to this field. |
|   |
|   |
|   |
Grid Criteria
| Iftwo consecutive lines have the same table then the selected records are thosethat will meet the combination of the two criteria. Toselect therecords that will satisfy tothe one or to the other of the criteria one should a line whose field has the value of « Or ». Iftwo consecutive lines have different tables then the criteria are evaluatedindependently one from the other. |
| No help linked to this field. |
|
| No help linked to this field. |
| Formula expressed in Adonix 4GL and assessable in a Where clause of an SQL query. |
Close
Action icon
Batch calculation
Possibility to launch the calculation of the workload from the batch job « LAHBAT ».
It allows :
· the calculation of the workload of an analysis not yet calculated
· the creation of a new analysis and the calculation of the corresponding loads by duplication of an analysis already calculated.
·the creation of a new analysis and the calculation of the corresponding loads based on an analysis template.
The batch job is associated to the following parameters :
· the analysis number.
If the analysis was not calculated, the batch job will calculate the load analysis, if not a new analysis is created by duplicating the characteristics of the reference analysis and the calculation is launched from this new analysis
The indicator « to be conserved » is forced to « yes » for this new analysis and the description can be changed.
·The template.
It allows the creation of a new analysis and the calculation of the workload, based on the selection criteria of the template.
For this new analysis, the indicator « to be conserved » is forced to « yes » for this new analysis and the description can be keyed in.
· The description
It is used in case of a creation of a new analysis.
Of the 2 parameters « Analysis n°» and « Template », one and only one can be keyed in.
Purge of the workload analysis
The purge code « LOADANY » allows the purge of the calculated analysis that are known « not to be conserved » according to the calculation date and all the « pseudo analysis » (cannot be displayed) generated during the demand of printouts.
The purge code « LOADANYHIS » allows the purge of the calculated analysis that are known « to be conserved » according to the calculation date.
Function / template linkages
It is possible to define several workload analysis functions, each one being dedicated to a particular template.
For example, « Analysis of EI portfolio » on the « Input » menu or « Analysis of DO portfolio » on that of the « Output ».
For that, the function should specify a value corresponding to the template for the parameter « GTAH ».
Users rights
It is possible, through the management of the users profiles, to specifically limit the users rights of use of the « GESLAH » function, through the following specific option codes :
· « 1 » (all templates) : forbids the user to change the template associated to the current function through the option Display / transaction
· « 2 » (all depositors) : imposes the access and the creation of analysis limited to the entities of the current depositor.
· « 3 » (template compulsory) : imposes to the user to use the analysis functions dedicated to a template.
By default, the following reports are associated with this function :
LOADANY : Load analysis
This can be changed using a different setup.
In addition to the generic error messages, the following messages can appear during the entry :
Analysis workload template: XX ,Unknown record
The template keyed in should exist on the table of analysis template
Error zone « Depositor » : XX, Unknown record
The depositor keyed in should exist on the table of depositors for the current site
Error zone « Table » : compulsory zone
If key in of selection criteria, the entity should be keyed in
Error zone « Table » : value not correct
The value keyed in should exist on the list of entities allowed.
Error zone « field » : unknown field
The value keyed in should exist on the list of the fields of the entity keyed in
Error zone « Formula » No criteria is defined
No value keyed in for the field of the entity neither on the zone « formula »
Error zone « Analysis N°1 » : compulsory value
On the display screen of the workload analysis , it is compulsory to key in a number for the analysis N°1
Error zone « Analysis N°1 », XXX : unknown record
On the display screen of the workload analysis, the number for the analysis N°1 should exist on the table of the load analysis of the current site.
Error zone « Analysis N°1 », XXX : the loads were not calculated
On the display screen of the workload analysis, key in of number of an analysis whose calculation was not yet launched.
Error zone « Analysis comparison N°2 », XXX : unknown record
On the display screen of the workload analysis, the number for the analysis N°2 should exist on the table of workload analysis for the current site.
Error zone « Analysis comparison N°2 », XXX : the loads were not calculated
On the display screen of the workload analysis, key in of number of an analysis whose calculation was not yet launched.
Error zone « Page », XXX : Unknown field
The entity keyed in does not exist on the table of entities for a detailed workload analysis (zooms)
Error zones « Value » : compulsory zone
If an entity was keyed in on the zone « Page », it is compulsory to key in the depositor of the entity processed if the analysis is not mono depositor and the number of the entity processed.
Error zone « Line » : compulsory zone
It is compulsory to key in an entity type on the zone « Line »
Error zone « Line », XXX : Unknown field
The entity keyed in does not exist on the table of entities for a detailed workload analysis (zooms)
Error zone « Line » : Impossible to make a table of workload with this setting
The entity keyed should be coherent with the entity keyed in on the zone « Page ».
Example of incoherent setting
« EI » the entity keyed in on the zone « Station » to know the workload of EI in particular and « preparation area » the entity keyed in on the zone « line » to know the load of the preparation area of the EI => this setting is incoherent because the EI are never associated to a preparation area.
Error zone « Column », XXX : Unknown field
The entity keyed in does not exist on the table of entities for a detailed workload analysis (zooms)
Error zone « Column » : Impossible to make a table of workload with this setting
The entity keyed in should be coherent with the entity keyed in on the zones « Page » and « Line ».
Example of an incoherent setting
« EI » the entity keyed in on the zone « Line » to display the workload of an EI and « DO » the entity keyed in on the zone « column » to know the workload of the EI by => this setting is incoherent because the EI are never associated to the DO.
Error zone « Station » : compulsory zone
If theworkload station is not defined as value « Page », « Line » or « Column », then it should be specified on the zone « Station » because the elements of workloads are always related to a station.
Error zone « Station », XX : Unknown record
The workload station keyed in should exist on the table of the workload station of the current site.
Error zone « Station » : Impossible to make a table of workload with this setting
The workload station keyed in should be coherent with the entities keyed in on the zones « Page », « Line » and « Column ».
Error zone « Unit » : compulsory zone
If the field « Column » is reserved to a particular entity type (and therefore cannot serve in the display of the different units of the stations considered), then the unit should be specified on the zone « Unit » because the elements of the workload are always related to a unit.
Error zone « Unit », XX : Unknown record
The unit keyed in should exist on the tables of units.
Error zone « Unit » : Impossible to make a table of workload with this setting
The unit keyed in should belong to at least one of the workload station of the analysis.