What’s new in INFLOR Forest?

The newest INFLOR Forest updates available in this release.

Correctives

[IS-13885] – ERROR REPROGRAMING OPERATIONS ON DEMAND

Reported Problem
When an excel file is imported, the routine is not finding the columns

Adopted Solution
The way columns are returned to the routine has been adjusted

[IS-16218] – MIS Oracle Database Health Check Report

Reported Problem
Evaluate and provide performance enhancements/fixes for the MIS queries.

Adopted Solution
The improvements have been made.

[IS-17894] – Inclusion of error message

Reported Problem
Inclusion of error message when trying to insert the same harvest programmed in the same file.

Adopted Solution
Inclusion of the message and change of the trigger and processing routine.

[IS-18191] – Adjust Manual Exhaust and Manual Adjustment screen to accept import or manually insert fields whose Microcadastro of the month is in history

Reported Problem
The Manual Adjustment and Manual Exhaust screens do not accept entering manually or importing via spreadsheet and validating lines whose microcadaster of the selected month is in history.

Adopted Solution
It will be possible to include / import in the Manual Adjustment and Manual Exhaust screen lines whose microcadastro are in history.

[IS-18223] – Change in Available Balance amount

Reported Problem
The system was displaying a value of available volume greater than what was being pointed out, even so the system displayed the message that the user had already exceeded the value of the available balance.

Adopted Solution
We changed the query so that the system calculates the production value of the harvest programmed according to its operation.

[IS-18419] – Error when approving Delivery Note

Reported Problem
When approving a delivery note, sometimes an internal error occurred in Oracle due to the repeated use of the document number to create the follow-up.

Adopted Solution
The DN approval functionality will force the change of the document number if it already exists a follow up for that document.

[IS-18476] – Transport Plan does not take the price from the price list

Reported Problem
User informed when clicking to calculate the plan the message of success is displayed, but the value of the plan is 0.

Adopted Solution
Adjust the plan calculation routine.

[IS-18584] – Adjust exhaustion interface logs

Reported Problem
The exhaustion interface logs were incorrect.

Adopted Solution
The exhaustion interface logs have been adjusted.

[IS-18606] – Duplicate record in the material interface

Reported Problem
It is possible to call the same ERP interface twice.

Adopted Solution
The EAI was changed to not allow two processes to be opened for the same interface, whether automatic or manual.

[IS-18650] – Material reversal

Reported Problem
Material reversal was not carried out by INFLOR.

Adopted Solution
Adjustment was made in the integration of material write-off to seek the amount used from the mirror table and not from the input table anymore.

[IS-18789] – Transport Payment Process Settings

Reported Problem
User informed that trips with volume 0 (zero) did not enter the payment process.

Adopted Solution
Consider trips with volume 0 (zero) in the payment process.

[IS-19073] – Nota Fiscal does not appear on the packing list screen

Reported Problem
Sometimes the system is not associating the invoice with the packing slip, even when it is processed without errors. This does not happen with all invoices.

Adopted Solution
Treatments have been added at some points in the invoice issue where the problem is likely.

[IS-19083] – Contract approve very slow

Reported Problem
When approving an operational contract, it takes a long time to finalize the operation, taking about 5 minutes, as usually several contracts are selected the waiting time can reach up to 2 hours.

Adopted Solution
It was verified that in the trigger that was triggered when approving a contract, there was an unnecessary loop, which increased the operation time. This loop was removed from the trigger, improving performance.

[IS-19320] – Pesagem

Reported Problem
Finalized trips are still available to be closed.

Adopted Solution
Trips are becoming available because the document is still in a “Outstanding” situation.
Adjust the situation of the travel document and adjust the routine that descends the documents to Scale.

[IS-19323] – Adjustments for MM22 and MM22A interface

Reported Problem
User informs that, when there is a change in the cycle and rotation of the field, this information is not being considered in the interfaces MM22 and MM22A.

Adopted Solution
Consider cycle and rotation of the field as a criterion to determine whether transmission will occur by routine MM22 or MM22A.

[IS-19333] – It should not be considered the items marked as withheld in the direct cost calculation

Reported Problem
The direct costs of services / operations can be considered in several months in Biological Assets if they are marked as withheld. However, they should be considered only in the month in which the operation actually took place.

Adopted Solution
Payment items marked “”Previously withheld”” are not considered in the direct cost calculation. Thus, only in the month that the operation took place will they added to the Biological Assets.

[IS-19369] – Vehicle release completed without end of travel date

Reported Problem
There are scenarios where a trip was finished on the weighing module, but the synchronization with MIS erased the end date of this trip, because in MIS the trip was still outdated.

Adopted Solution
In other tickets, adjustments were made to shield travel dates. One more of these shields was added on synchronization of vehicle release.

[IS-19471] – Sub-Compartment without Regime with notes

Reported Problem
The user was able to make notes without regime, so the system hid some notes in the Appointment Report.

Adopted Solution
A validation was created so that the system does not allow the user to enter an operation with the Sub-Compartment without regime.

[IS-19519] – Master data integration – Contract period

Reported Problem
The contract download interface was not marking the SAP flag for contracts when downloading them.

Adopted Solution
The problem has been fixed, and the SAP flag for contracts is being flagged by downloading them from SAP.

[IS-19539] – Reversal of spreadsheet does not change weight / volume of packing list

Reported Problem
When reversing a customer weight / volume import referring to a packing list, the system is not returning the packing list to its original weight / volume.

Adopted Solution
When reversing a weight / volume import, the packing list will return to its original state.

[IS-19573] – Duplication of items in the payment process

Reported Problem
The follow-ups consolidation in the payment process calculation is not considering the informed contract.

Adopted Solution
Change in the payment process routine to consider the contract when calculating the process.

[IS-19721] – INFLOR – SAP integration error

Reported Problem
When interrupting the equipment and labor hours interface, pending processing records were inserted into the table and did not process again.

Adopted Solution
The interface routine was changed to delete the pending records for each new execution of the integration and insert them again to be processed.

[IS-19839] – Contract with payment source as “”reported volume””

Reported Problem
The adjustment follow-ups are being considered in payment with “”payable volume”” despite the contract indicating that the payment origin is through the “”reported volume””.

Adopted Solution
The system has been adjusted so that if an adjustment follow-up appears in payment, its volume is disregarded when the contract’s payment source is “”reported volume””.
The adjustment line will appear in payment, but with zero in “”payable volume””.

Incidents

[IS-17899] – Audit Notification

Reported Problem
User informs that they are not receiving notification emails about generating audits.

Adopted Solution
Job creation to daily notify users configured to receive audit log.

[IS-19131] – Display value in the “”Item Message Id”” of Cubes MM14, MM15 and MM17

Reported Problem
The value in the Cd Message Interface field was being displayed as Null.

Adopted Solution
The field was changed to find the value of the existing table.

[IS-19178] – Wrong calculation of the adjusted volume

Reported Problem
The system was considering notes in History when calculating the adjusted volume.

Adopted Solution
We changed the cube code.”

[IS-19395] – Query limiting records

Reported Problem
The system is limiting the records that were displayed in the cube.

Adopted Solution
Removing the limiter that was inserted incorrectly.

[IS-19624] – Error when trying to perform road payment process integration

Reported Problem
Value too large for column DLORT on table ESP_OUT_PAGAMENTO.

Adopted Solution
The field was changed to allow receiving values ​​of up to 35 characters.

Requested Services

[IS-13481] – New Proforma report

Reported Problem
The report did not exist.

Adopted Solution
Create a new report, similar to the other datawarehouse screens, with data from approved follow-ups, with some complementary information.

[IS-13644] – Include information on cube 347

Reported Problem
The cube don’t shows only active SC’s and don’t shows the HDOM and UNIDADE_OPERACIONAL column.

Adopted Solution
The active SC’s filter was removed and three new columns were added (HDOM, UNIDADE_OPERACIONAL e EST_REG).

[IS-16851] – Include two columns of a datacube for another two datacubes

Reported Problem
The datacubes Complete View of Silviculture Follow-ups and Complete View of Silviculture Budget need more information, in order to attend to the needs of the users.

Adopted Solution
The fields number of reference days and percent of execution of operations were added in the data cubes.

[IS-17740] – Field adjustment of the “”Visão de custo unificado orçado x realizado”” cube

Reported Problem
When changing the display of the predicted unit cost field from line to data, the field appears with zero values.

Adopted Solution
The calculation of the field has been adjusted to be displayed as a number.

[IS-18378] – Stands of managemente unit

Reported Problem
Projected stands should not appear on any screen in the forest register (the only exception is the stand edition screen, but only for stands projected from operational plans).
Thus, the following changes are necessary:
On the stand edition screen (Forest Register / Location / Operational / Stand Edition), show only current and projected stands from operational plans.
On the other screens, show only current stands.

Adopted Solution
The changes mentioned above have been implemented.

[IS-18733] – Add two new LU3 in view VW_CUBO_POSS_PLANT_AREA_DIST

Reported Problem
We added 2 new LU3 in LU2 “”Possible Plantable Area””, need to show in the view VW_CUBO_POSS_PLANT_AREA_DIST, please add two line code in the view and publish thru INFLOR product version control:
SUM(DECODE(ID_CARACTERISTICA_USO_SOLO, 220, VLR_AREA , NULL)) AS SELF_HARVESTED_SITE,
SUM(DECODE(ID_CARACTERISTICA_USO_SOLO, 221, VLR_AREA , NULL)) AS STUMPAGE_HARVESTED_LAND.

Adopted Solution
Added changes to versioning control.

[IS-18743] – Parameter for calculating the Project Year column

Reported Problem
User informed that the rule for Mato Grosso do Sul region should be changed.

Adopted Solution
Adjustment of a specific rule of the TTG client for the region of Mato Grosso do Sul.

[IS-19082] – Display registered Quality Bulletins for Sub-compartments that are in history

Reported Problem
No records of quality bulletins are displayed for Sub-compartments that are in history.

Adopted Solution
The base table was altered to present plots in history.

[IS-19121] – Addition of a field in the cube – view VW_CUBO_CONTROLE_INSUMOS

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

Adopted Solution
The field have been included in the view.

[IS-19346] – Insertion of month and year columns for cube 376

Reported Problem
Cube without columns of Month and Year of operation date.

Adopted Solution
Cube query change.

[IS-19347] – Display of “”Real Date”” field as a parameter in the cube

Reported Problem
When defining the Actual Date field as a parameter, it does not consider the calendar for choosing the period.

Adopted Solution
The field has been changed to type Date.

[IS-19424] – Inclusion of the species column in cube 468

Reported Problem
Cube 468 does not have the Specie column.

Adopted Solution
Changes in queries to display the column.