What’s New in INFLOR Forest? (.NET – 27th/May 2019)

Home/2019, Blog, INFLOR Forest, WEB/What’s New in INFLOR Forest? (.NET – 27th/May 2019)

What’s New in INFLOR Forest? (.NET – 27th/May 2019)

What’s new in INFLOR Forest?

See the INFLOR Forest’s updates in this new release.

Service request

[IS-9565] – Forestry Register: Configuring parameter for column “Project Year”

Request
It was missing a characteristic for calculate the column “Project Year”

Adopted Solution
Including a new characteristic for calculate the column “Project Year”

Incident

[IS-10773] – Administrative Register: Translation error and data string of the input stock

Scenario Reported
Error in translations and date conversion is in error.

Adopted Solution
The translations were implemented and the date conversion was corrected.

[IS-10920] – Transportation: Wood Entry

Scenario Reported
The wood entry report, when allowed access by suppliers, was not filtering the data correctly from the logged supplier.

Adopted Solution
The wood entry report has been adjusted to correctly display only the data from the logged supplier when it has access.

[IS-11223] – Silviculture: Fetch the Unit Price of a Material updated from ERP

Scenario Reported
It was identified a case that the system did not fetch the latest unit price of a material reported when calculating the Silviculture Payment Process which caused an impact on the calculation of direct costs of the bio-asset. Currently, the system searches for latest unit price with the reference date less or equal to the Silviculture operation date performed. However, there are clients that the rule is based on latest unit price available within the same month and year of the date when the Silviculture operation was performed.

Adopted Solution
Therefore, the system must be flexible in order to provide more than one way of fetching unit prices for materials downloaded from ERP.
It was created a new numeric parameter “TIPO_CRITERIO_BUSCA_PRECO_MATERIAL_ERP” that informs which way the system fetches unit price of material from the price table:

  1. It fetches the latest unit price available with Reference Date Less or Equal to the date of the Silviculture operation performed.
  2.  It fetches the latest unit price available within the same month and year of the date when the Silviculture operation was performed.

Corrective

[IS-5299] – Transportation: Wood Yard

Scenario Reported
The display of the piles and weighted values of the characteristics of the yard’s stored products was showing low performance when many pile transfer records were made inside the yard.

Adopted Solution
New calculation mechanisms were implemented to improve overall system performance by performing calculations of the characteristics of the products being handled.

[IS-8603] –  Transport: Error in MIS x MES service log record

Scenario Reported
The MIS x MES service has a feature that saves logs on the server to the “.txt” file. When there is concurrent processing, there was a concurrency error occurring between processing for file use.

Adopted Solution
All MIS x MES service logs will be saved to the server in the Windows event log, with the “MISxMES” identifier. This will make it easier to search the logs and will not present a concurrency error, regardless of the amount of concurrent processing.

[IS-9759] – Error in closing transportation and loading

Scenario Reported
Payment process 5038 is not seeking all notes made within the accrual period, returning only 1 record as payment process item.

Adopted Solution
Adjusting the query that updates the routine notes that generates the payment process items, so as to return contracts that have the field FLAG_CONTRATO_AUTOMATICO null.

[IS-10547] – Asset: Error when reversing “Processing Pending Balances” report 4323

Scenario Reported
The report 4323 (Custos e Imobilizado / Lançamentos / Tratamento de Saldos Pendentes). Can not mark more than one item

Adopted Solution
A fix was made to allow the button to process more than one record.

[IS-10576] – Climatology: Action of correction of data – 4th level

Scenario Reported
The interpolation calculation routine with neighboring stations was taking into account measurements of only one station.

Adopted Solution
The routine now only takes into account the measurements in the two stations.

[IS-10579] – Climatology: Cube of visualization of daily data

Scenario Reported
The interpolation calculation routine with neighboring stations was taking into account measurements of only one station.

Adopted Solution
The routine now only takes into account the measurements in the two stations.

[IS-10695] – Transportation: Wood Yard – Pile Detail

Scenario Reported
In the scenario of use of delivery note and primary pile in the yard, the revert full pile feature was erasing the characteristic of wood-type of the primary pile.

Adopted Solution
The revert full pile feature has been changed so as not to erase the wood type characteristic of the primary pile in the scenario of using the delivery note and primary pile in the yard.

[IS-10728] – Silviculture: In the reports of the PPF appear more than two houses after comma

Scenario Reported
The values of Dose/ha and Quantity columns in the reports have two decimal places.

Adopted Solution
The values of Dose/ha and Quantity columns in the reports have four decimal places.

[IS-10807] – Harvest: Allow register follow-up without duration, but with volume

Scenario Reported
It’s not possible to register a Harvest Follow-up with duration, but without volume. This case is important for products assortment that requires a follow-up with duration, but without volume and another follow-ups with volume, but without duration (for different products).

Adopted Solution
We’ve created a configuration in “MIS / Harvest / Configuration / Work Teams / Work Teams” that allows one work team to avoid some rules in harvest follow-up registration.

[IS-10866] – Failed to calculate payment process

Scenario Reported
Failed price lines passed to history after running master data.

Adopted Solution
The interface procedure has been adjusted, and now prices that do not fall from SAP for update / inactivation will no longer be impacted.

[IS-11232] – Transportation: When saving “Supply Type” the system is always obliged to fill in the field “Sample Type”

Scenario Reported
When attempting to save a record on the “Supply Type” screen, the system is required to fill in the “Sample Type” field even when the “Volume Calculated by” field is different from “Sampling”.

Adopted Solution
After this call is implemented, the system will only allow and require the field “Sample Type” when the “Volume Calculated by” field is filled in with the “Sampling” option.

[IS-11362] – Transportation: Wood Entry Report

Scenario Reported
The report is displaying the current RPV value instead of displaying the RPV value on the date of the Follow-up transportation.

Adopted Solution
Display the RPV value on the creation date of the Follow-up transportation.

Other Requests

[IS-10772] – SGF: View segregated by UG

Scenario Reported
It was identified that even after the improvement of adding the UG field on the TTG input screen, by rotating the 254 cube, it did not filter by Management Unit even though it marked the flag to filter on the cube view screen.

Adopted Solution
There was a cube limitation per UG because it did not consider all information relevant to the search process. Therefore, the information was added to the query, allowing the correct operation during the consultation process.

Leave A Comment