What’s new on INFLOR Forest?

The newest INFLOR Forest updates available in this release.

Correctives

[IS-18973] – Reversal of payment process with follow-up retained in previous process

Reported Scenario
When reversing a payment process calculation, it was not allowing to complete the transaction, if the process contained items retained from previous processes, if they have already been considered in the costs calculation.

Adopted Solution
The payment process reversal routine has been changed to allow deleting items, even if they have already been considered in the costs calculation, in the case of follow-ups retained in previous processes.

[IS-18936] – Inclusion of the processing date in the movements performed by Manual Exhaustion

Reported Scenario
User informed that despite performing the exhaustion, when consulting the record, the processing date field was empty.

Adopted Solution
Adjustment was made to include the processing date.

[IS-18818] – When there are more than 50 Packing Lists with problens in the Simplified Harvest, the system cannot process the other Packing Lists that have no problens

Reported Scenario
When there are more than 50 Packing Lists with problems in the Simplified Harvest, the system cannot process the other Packing Lists that have no problems.

Adopted Solution
An adjustment was applied to the routine for processing Packing Lists so that it first processes the Packing List which do not have any Simplified Harvest problem and only then try to process the Packing List which has already had problems before.

[IS-18762] – Error in changing contract date and price table

Reported Scenario
User reports an error in changing contract’s or price list’s date.

Adopted Solution
Correction in validation mechanism when changing contract’s or price list’s date.

[IS-18692] – Correction in view used in calculating direct cost needed.

Reported Scenario
Error in view used in calculating direct cost.

Adopted Solution
Correction in view used in calculating direct cost.

[IS-18672] – Inclusion of time in the Bulletin History Record Date field

Reported Scenario
Currently, only the date is displayed in the Record Date field.

Adopted Solution
The type of date to be displayed on the screen was included in the field, to also show hour and minute.

[IS-18627] – Stumpage sales finished operation duplicated piles

Reported Scenario
The user identified duplicate piles for the stumpage sales operation when inserting finished operation date.

Adopted Solution
The plan calculation was adjusted to not incorrectly create extra scheduled operations for stumpage sales (which led to duplicate piles in automatic follow-up).

[IS-18594] – Currently the SGF tables that are used in the dimensions do not indicate the date of the last change of the records.

Reported Scenario
Users report slowness in incremental Analytics loads.

Adopted Solution
Adjustment was made to include the processing date.

[IS-18441] – Behavior of the EXA Manual screen

Reported Scenario
Identify flaws in the behavior of the manual exhaust screen, according to the procedure adopted for each client. In initial internal conversations, there was a possible problem in the way the screen processes manual exhaust, if there is more than one record for a given field. In this case, there is no initial processing of the first entry and subsequent processing of the second entry, considering the remaining balance of the first processing.

Adopted Solution
In manual exhaustion, it is intended that the processing does not update the balance for each line, but that base balances remain and that all percentages or amounts apply to this same base.

[IS-18254] – Inappropriate behavior on the screen of the operations programming module in roads module.

Reported Scenario
User informs that in the screen of entering programmed operation without road when performing the operation programming, the fields remain filled.

Adopted Solution
Adjustment on the behavior of the screen to clear the fields after successful creation of the programmed operation.

[IS-18109] – Recalculation of the payment process and application of deductions

Reported Scenario
When recalculating a payment process already calculated, without reversing the calculation previously, the deduction amounts applied to the process are lost.

Adopted Solution
The payment process calculation routine has been changed so that, if the process has already been calculated, apply the deduction amounts to the process again.

[IS-18099] – Harvesting follow-up – HUB

Reported Scenario
Follow-ups that arrived at MIS with canceled scheduled operation due to SC replanning do not display an intuitive message to the user during information processing.

Adopted Solution
The validation was adjusted so that the system identifies these cases and correctly informs the user.

[IS-18020] – Excessive slowness in consulting forestry bulletins

Reported Scenario
User informs that the system presented zero values for materials and seedlings in a series of bulletins even with the values coming correctly from SAP.

Adopted Solution
Adjustment made to the mechanism to store value from SAP. An audit was also created to monitor changes in these values during the process.

[IS-18003] – Transportation Follow-ups (field origin) generated with product stack origin as history.

Reported Scenario
When canceling a bucket report at harvest, if it is the only bucket report, the system changes the bucket pile to history, however it does not check if there are Delivery Notes that are still “not approved”, Sales List in “circulation” or “used” and whether there are vehicle release documents for that stack.

Adopted Solution
Now the system validates if there are vehicle release documents, Delivery Notes or Sales list, before cancelling the bucket report.

[IS-17940] – Problem on Transportation App synchronizatoin

Reported Scenario
When a SC has no Transportation Order (with forest origin) or Sales Plan planned, the SC is not download to the Transportation App through synchronization. The tablet app only shows piles in which the SC exists on the tablet database. The SC information is required even if the Delivery Note is Intermediate Depot Origin, to get the SC type (881 or 885) and show the piles properly.

Adopted Solution
For Delivery Notes with Forest or Transferring Point origin, the SC type will still be recovered by the SCs synchronized. But, for Intermediate Depot origin Delivery Notes, the SC type will be synchronized along with the depot piles, so it will not be necessary to download the full SC information just to get the SC type. MIS-5.8.4.7

[IS-17907] – Excessive slowness in consulting forestry bulletins

Reported Scenario
User informs that the screen for consulting forestry bulletins is taking an excessive time for loading.

Adopted Solution
A performance improvement was made on the complete bulletin query screen to filter data by temporary table.

[IS-17837] – SC without management unit synchronizing with tablet app

Reported Scenario
When a SC that was already available for transportation is disconnected from the management unit, the tablet synchronization tries to download the SC information and presents an error.

Adopted Solution
The application will only synchronize SCs that have an associated management unit.

[IS-17802] – Allow the edit/remove of document batches

Reported Scenario
Currently, it is not possible to edit or delete the document batches in the SGF Sales module.

Adopted Solution
Some validations have been added that only allow editing of document batches, being possible to change the record to “history”.

[IS-17600] – Problem to generate the “Silviculture Payment” report

Reported Scenario
Situation indicated in the generation of the Silviculture Payment report. A calculated payment process, with two operations with equal values, generated only one line in the Silviculture Payment report, when the values of both follow-ups should be added together.

Adopted Solution
A correction was made in the Silviculture payment report so that, when two equal operations are pointed out with the same quantity, display the two operations in the report.

[IS-17563] – Automatic generation of collectors / cost groups failed

Reported Scenario
PEPs were not being generated automatically due to the lack of genetic material information in the stands.

Adopted Solution
The functionality of generating projected stand was adjusted, to oblige the filling of the genetic material information at the moment of the projection (for the regrowth stands, the genetic material of the parent stand is assumed).

[IS-17197] – General adjustments to the functionality of transferring operations between plans.

Reported Scenario
User informed that there were some general problems in the functionality of transferring operations between plans.

Adopted Solution
Adjustments were performed to the functionality of transferring operations between plans to correct the points reported.

Incidents

[IS-18664] – Change in the payment process routine

Reported Scenario
Change in the payment process routine, so that the system does not create retained payments that were already in another payment process already paid.

Adopted Solution
Adjustment in the search.

[IS-18984] – Adjustment of Packaging Stock (BOXES).

Reported Scenario
User reports that, when correcting the mechanism for calculating boxes released by material, pending returns were generated.

Adopted Solution
Performed corrective data requested by the user to match the number of boxes released and returned to work orders of May/20 and back.

Requested Services

[IS-18987] – Error when making manual adjustment of PEP.

Reported Scenario
User reports error when performing manual balance adjustment for SC’s that are in history.

Adopted Solution
Adjusted the search for land use in the routine that validates the balance adjustment, to consider SC’s in history.

[IS-18060] – Inclusion of the Working Scheme column in the cube.

Reported Scenario
The system was returning two lines in the cube due to different handling.

Adopted Solution
We added the management column in the cube for the user to be able to filter the data.

[IS-18054] – Addition of the EST_REG = ‘A’ filter in the VW_CUBO_SGX_SD4 view

Reported Scenario
By now the SD4 – Wood Sales cube returns both active and historical data.

Adopted Solution
Inserting the est_reg = ‘A’ filter into the VW_CUBO_SGX_SD4 cube.

[IS-17701] – Adding fields in the ‘Relat. Gestão – Acompanhamento Rendimento Material Realizado’

Reported Scenario
New fields were requested to include to the year and month of the operation performed.

Adopted Solution
The fields have been included in the view.

[IS-17699] – Addition of a field in the cube – view VW_CUBO_OPER_ORC_PROG_REAL

Reported Scenario
A new field was requested to include the unit of measurement code information.

Adopted Solution
The field have been included in the view.

[IS-17625] – New “Created By” field in the wood sales cube and invoice screen

Reported Scenario
It is only possible to determine which user created the invoice when it has a packing list.

Adopted Solution
The “Created By” field will be included in the invoice screen and in the wood sale cube, and this field will be filled in for all types of invoice.
Invoices prior to this implementation will only have filled in the creator user if they are invoices that have an packing list associated.

[IS-17587] – [105625] Transportation’s SGF

Reported Scenario
Currently, the fields “Age” and “Extractive” do not exist on the Stack situation report.

Adopted Solution
The new fields were added to the Stack Situation report.

[IS-17497] – [105329] Yard movement screen 4724

Reported Scenario
Currently, it is not mandatory to fill in the “Operator” field when inserting a yard movement.

Adopted Solution
A parameter was created to define the mandatory nature of the field, and a validation to not allow the insertion of yard movement without an operator, when this parameter is equal to “S”.

[IS-16806] – Creation of data cube: Budget View / GL Account

Reported Scenario
There is a demand to generate a cube with all the budgeted resources per field, and that also shows the accounting account associated with each resource.

Adopted Solution
Implemented a view to feed the requested data cube.