What’s new in INFLOR Forest?

The newest INFLOR Forest updates available in this release.

Correctives

[IS-18098] – PO Interface Error – Send Registration Sheet (Payment) – Forestry

Reported Scenario
When executing the registration sheet submission interface in SAP, data with errors are registered sheets and also cases in which the sheet number is being saved wrong.

Adopted Solution
It is necessary to sort records by purchase order before they being sent.

[IS-19103] – Purchase Order: MuleSoft error: One or more errors occurred

Reported Scenario
User informs that in the purchase order interface the errors are being presented in a non-explanatory way.

Adopted Solution
Correction in receiving the response from MuleSoft to consider message coming from SAP correctly.

[IS-19586] – In the Weighing Module the Weighing Screen for Simplified Transport is not working correctly for Third Party Yard Origins

Reported Scenario
Simplified Transport is not working properly for Third Party Yard Origins.

Adopted Solution
Adjust fields when the origin is Third Party Yard.

[IS-19629] – It is not possible to filter the Batteries on the Distance Screen for the section Pátio de Terceiros x Centro de Consumo

Reported Scenario
It is not possible to filter the Batteries on the Distance Screen for the section Pátio de Terceiros x Centro de Consumo.

Adopted Solution
The Batteries filter on the Distance Screen for the Third Party Patio x Consumer Center section is working correctly.

[IS-19999] – The Travel Receiving Screen of the Weighing Module is allowing the user to enter an “”Issue Date”” invalid in the Travel register

Reported Scenario
the Weighing Module allowed the user to enter invalid dates on the Travel Receiving screen.

Adopted Solution
Validation has been implemented to prevent the user from entering invalid dates in the Travel Receiving screen of the Weighing Module.

[IS-20035] – 1. VW_CUBO_COL_BOLETIM_CTO view change

Reported Scenario
The system was duplicating a value with the VLR_VOLUME_AJUSTADO_PERIODO field, and incorrectly calculating the VLR_VOLUME_APONTADO_ACUM and VLR_VOLUME_AJUSTADO_ACUM fields.

Adopted Solution
Changing the VLR_VOLUME_APONTADO_ACUM and VLR_VOLUME_AJUSTADO_ACUM fields.
Removal of the VLR_VOLUME_AJ_PERIODO_ACUM subselect as it was duplicating the information.

[IS-20109] – Manual creation of price list registration in contract with ERP origin

Reported Scenario
User informs that it is possible to manually add price tables for contracts that originate through ERP.

Adopted Solution
A control was implemented in the display of the mechanism of manually adding the price table considering the origin of the contract.

[IS-20169] – Error in issuing chipping report

Reported Scenario
The complete chipping report is showing an error, regardless of the filter that is performed.

Adopted Solution
The report query has been adjusted and the data will be displayed correctly.

Incidents

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

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

Adopted Solution
We changed the cube code.

Requested Service

[IS-19423] – Extra fields – Data Cube

Reported Scenario
Need to translate of extra fields according to 4305 window of SGF.

Adopted Solution
Translatation of extra fields in vw_cubo_cfg_uso_solo.

[IS-20126] – Display currency type data for reports from previous years

Reported Scenario
Currency records are not displayed for reports that are in history.

Adopted Solution
The base view that fills the cube has been changed to display reports in history.

[IS-2083] – Improvement – GAP 376

Reported Scenario
In every division of the land use, all attributes of the parent land use must be taken to the son land use.

Adopted Solution
Routine creation to include information automatically.

Project

2020-092 – Deployment of Exhaust Module

Created parameter that allows configuring if the assessment variable configured for the group of direct costs should be checked during the allocation of direct costs

Reported Scenario
By default, the product allocates direct cost follow-ups to the stand in which it was created, regardless of whether the value / cost collector of the follow-up is or is not consistent with the biological asset information. For example, if an Implementation operation is posted to a Maintenance subcompartment, the appropriation of costs occurs in the same way.

Adopted Solution
To meet the scenario in which the same cost collector is used to post operations from different cost groups, it was necessary to create a check in the calculation of direct costs. This verification ensures that the subcompartment indicated falls within the apportionment variable associated with the cost group and makes an allocation only if this criterion is met.

View used for allocation of costs now contains the information of Gender and Age in Years

Reported Scenario
Due to a demand from the NGB implementation project, it was necessary to make Gender and Age information available in the main view of the apportionments: VW_EXA_VARRAT_TODOS_TOLHOES.

Adopted Solution
The mentioned view has been updated and now contains the Gender and Age information available for use in the apportionments of costs in the Biological Asset module.

Cubo used for create informes of BioAsset now contains the information of Gender and Age, in years

Reported Scenario
Due to a demand from the NGB implementation project, it was necessary to make Gender and Age information available in the BioAsset movements cube.

Adopted Solution
The mentioned view has been updated, and now contains the Gender and Age information available for use, in the reports in the Biological Asset module.