Transportation – Market Wood Purchasing

The purpose of this improvement is to allow the system to receive the timber from the market. Previously the system did not allow a truck without vehicle release to be received at Mill. The possible origins of the trips were External Yard, Forest or Intermediate Depot. Two new scenarios regarding the purchase of market timber will be allowed:

  1. Receipt of truck already loaded, with invoice.
  2. Release of vehicle to search for wood directly at the supplier.

How to use

In the screens MIS / Administrative Register / Business Contacts / All Related Individuals and MIS / Administrative Register / Business Contacts / All Related Companies it will be possible to include Business Contacts in the system. These Business Contacts will be the suppliers of market wood, and will have the “Origin MIS” field marked “yes” automatically.

Image 01

Image 02

In the screens MIS / Transportation / Configuration / Depot / Third party deposit register and MIS / Transportation / Configuration / Depot / Piles – origin/source third party deposit screen, it will be possible to create and configure new yards and piles respectively, which will be used as market wood. In the screen ” Piles – origin/source third party deposit” is made the register of the characteristics, certifications, species and genetic material of the wood.

Image 03

Image 04

In the MIS / Transportation / Control / Fiscal Documents / Lots screen, the series of documents that will be used for these follow ups is made. The “Goal” of the series should be “Wood Purchase” for purchases without vehicle release, and “Conventional Transportation” for purchases with vehicle release. The Local Type should be “Third Parties Yard“. Suppliers of this type of wood are associated with the series in the “Restriction by Transportation Supplier” tab.

Image 05

In the MIS / Transportation / Configuration / Register / Supply Type screen you can enter the supply types for these series.

Image 06

In the weighing module, it will be possible to receive trucks directly on the weighing screen, without vehicle release. For this, it is necessary to inform the number and volume of the invoice that is arriving at the factory.

Image 07

It is also possible to issue a vehicle release for the truck to fetch this wood. Just inform the origin as “Third Parties Yard”.

Image 08

The end trip is normally carried out according to conventional transport.

The reports “Monitoring of Received and Determined Volumes“, “Wood Entry“, “Production by City” and “Wood Credit Report” will display the data referring to the wood post factory follow ups.

Image 09

The Transport / Control / Closing / Wood Purchase / Complementary Note screen will display the factory-installed follow ups that were issued without vehicle release.

Image 10

The Transport / Control / Closing / Wood Buying / Totalizing Note screen will display the factory-installed follow ups that were issued with vehicle release.

Image 11

In these two screens, the “Operational Follow Up” button will display a summary report.

To view the notes separately by city for total or complementary notes, simply go to the “Invoice Grouping” tab.

Transportation – Add column “Certificate” to report “Road Field Inventory”.

Previously, the report “Road Field Inventory” did not present any information on the sub-compartments certifications. Now the “Road Field Inventory” report will have the columns “Certification – CER” and “Certification – FSC“. This will be filled as follows:

  • Certification – CER
    • If the sub-compartments is associated with certification of type “CERFLOR”, the column will present the value “Yes”;
    • If the sub-compartments is associated with “CERFLOR CW” type certification, the column will have the value “CW”;
    • If the sub-compartments is NOT associated with “CERFLOR” and “CERFLOR CW” type certification, the column will present a value of “No”;
  • Certification – FSC
    • If the sub-compartments is associated with certification of type “FSC”, the column will present the value “Yes”;
    • If the sub-compartments is associated with “FSC CW” type certification, the column will have the value “CW”;
    • If the sub-compartments is NOT associated with “FSC” and “FSC CW” type certification, the column will present a value of “No”;

Image 12

Transportation – Chipper Consumption – Complete

The purpose of this improvement was to add the hour in the date filter and replace the precipitation column by extractive. After implementation of this improvement, the report will have a more accurate period with the date and hour filter;

How to use

MIS – Report of Chipper Consumption – Complete.
Path: MIS / Transportation / Control / Report / Chipper Consumption – Complete.

To use this functionality, select the date and hour filter.

Image 13 – Filter By Date and Hour

Transportation – Volume Comparison Received at the Factory

The purpose of this improvement was to add the hour in the date filter. After implementation of this improvement, the report will have a more accurate period with the date and hour filter.

How to use

MIS – Report of Volume Comparison Received as the Factory.
Path: MIS / Transportation / Control / Report / Volume Comparison Received as the Factory.

To use this functionality, select the date and hour filter.

Figure 14 – Filter By Date and Hour

Transportation – Piles of Wood Situation

The purpose of this improvement was to add the reference date filter, Product Type and Product. After implementation of this improvement, the report will be able to filter by a Reference Date, Product Type and Product.

How to use

MIS – Report of Piles of Wood Situation.
Path: MIS / Transportation / Control / Report / Piles of Wood Situation.

To use this functionality, select the reference date filter, product type and product.

Figure 15 – Filter By Reference Date, Product Type and Product

Figure 16 – Report

Harvest – Add SC running ID search field

The search for the land use on the harvest module is complicated. Now it was sdded search for the land use code (flat text) on the screens:

  • Harvest / Operational Planning / Operational Plan / Edit Harvest Sequence / Include SC
  • Harvest / Operational Planning / Operational Plan / Edit Harvest Sequence / Edit SC (Change date or cancel)
  • Harvest / Operational Planning / Operational Plan / Plan Result – Edit Operations / Include Operation
  • Harvest / Operational Planning / Operational Plan / Plan Result – Edit Operations / Release Operation Programmed manually
  • Harvest / Operational Planning / Operational Plan / Plan Result – Edit Operations / Cancelling
  • Harvest / Operational Planning / Operational Plan / Plan Result – Edit Operations / Edit operation date, productivity class or %
  • Harvest / Operational Planning / Operational Plan / Plan Result – Edit Resources / Equipment
  • Harvest / Operational Planning / Operational Plan / Plan Result – Edit Resources / Material
  • Harvest / Control / Follow-Ups / Sales/write off
  • Harvest / Control / Follow-Ups / Pile Measurement
  • Harvest / Control / Reports / Screen (Excel) Reports / Harvest Detailed Follow-up
  • Harvest / Control / Reports / Screen (Excel) Reports / Harvest Downtime View
  • Harvest / Control / Reports / Screen (Excel) Reports / #Paradas Colheita – Insumos
  • Harvest / Control / Reports / Screen (Excel) Reports / Stock (opened and closed days)
  • Harvest / Control / Reports / Screen (Excel) Reports / Stock (closed days)
  • Harvest / Control / Reports / Screen (Excel) Reports / Detailed productivity by Operator

Corrections

Problems

[IS-8662] – Transport: Error in sending data from the interfaces of the Transport Operations Log Sheet

When executing the Registry Sheet interface for the Transport operations, it presented errors. This was due to the fact that in certain groupings, the resulting value was ZERO (due to the volume adjustments that are made in the transport operations). And in this scenario SAP rejected these records. For the improvement, an adjustment was made in the routine of sending the records of the Record Sheet routine to not send the records with ZERO value.

[IS-8639] – Harvest: Inventory report showing negative values

The stock report was displaying negative values. They should not appear for greater assertiveness in calculations. As an improvement, it has been parameterized in the system so that negative values ​​are displayed as required. The default is for non-display.

IS-8599 – Transport: Error closing Operational Calendar in Management Units with Volume Adjustment Transported by IPC

When closing the “Operational Calendar” in a “Management Unit” that is configured to perform adjustment of the volume transported based on the IPC, in some scenarios the system would not allow the closing of the day and would display an error message informing the existence of bulletins with ZERO volume. We identified that the problem quoted above was due to the fact that the “Setting Guide” creation routine was trying to create the tabs without verifying that its volume was different from ZERO. An adjustment was made to the “Setting Guides” routine so that only the Guide is created if it does have an adjusting volume.

[IS-8432] – Harvest: Adjust problem where some plots are not turning cadastre

Some plots were not registering in the system even obeying all the configuration conditions for this transition. Now Inflor Forest allows the possibility of separating the operational calendar from the transport and harvest management units, making their days independent of each other. Thus, when this separation occurred, there was a problem where at the opening of the day in the operational calendar of transportation, the turn of registration made by the harvest was being undone. A change was made so that this situation does not occur.

IS-7643 – Sales: Show Only Active Products on the Weighing Module Selling Romaneio screen

The SGF Weighing Module was displaying historical product on the Selling Romans Output screen. After this item has been deployed, the SGF Weighing Module will display only active products on the Selling Romans Output screen.

Incidents

IS-8667 – Simplified Harvest: Problem in processing companion notes

Error in processing cockipit of pending of the Harvest referring to complementary notes of sale of wood. After improvement, the data from a complementary guide were adjusted.

IS-8656 – Harvest: Problem in the Purchase Order Interface – Gerdau

Before, there was a problem in sending some harvest data through the Gerdau purchase order interface. The problem was caused by a scheduled operation that did not have expected production (SAP does not accept receiving zero values). It has been set so that the interface does not send operations with zero production expected.

IS-8609 – Transport: Scale Module – Synchronization of Truck Receiving Data

Due to an internal problem, one of the synchronization objects was attached to the last problematic publication package, which could lead to errors of synchronization of the truck pick-up data made in the scale module with the SGF.

Note: Occurs only on delivery without using Delivery Note.

Correct corrections were applied to the synchronism object of the scale module that synchronizes the truck pickup data with the SGF. That way, the data will synchronize correctly.

IS-8565 – Administrative Register: Habilitation Contracts x Supplier x Operation

A rule has recently been deployed to prevent the user from manually configuring contracts received from third-party ERP systems. However, this rule had an impact on the configuration of transportation contracts enabled by transport equipment, where their configuration should be allowed if the ERP contract was downloaded third or not. We have adjusted the rules that prevent the realization of contract configurations downloaded from third-party ERP, so that it allows the configuration of the authorization of transportation equipment for the transportation process, regardless of whether or not the contract was downloaded from ERP.

IS-8543 – Harvest: Problem in front view of operation in report 5246

Report 5246 (Harvest / Control / Reporting / Queries / Production of Already Processed Processing) is displaying the operation front information incorrectly for transport operation. A correction was made in obtaining the transport data so that the operating fronts were considered correctly.

IS-8449 – Harvest: Error generating finished operations cube

Finished operations cube shows error when generated. There was a problem in generating a validation on the cube opening that was set.

IS-8437 – Silviculture: Button disabled

In the Silviculture follow-up screen, the button to create Quality follow-up was disabled for the user. The button was enabled.

IS-8304 – SGF-NC Interfaces Execute with Error

Interfaces for Harvesting, Material Handling, and Material Downloading submit errors in all runs. Change generic REST Client data send behavior to work with different data patterns.

IS-7951 – Administration: Environment and wrong sender on interface error

In cases where the interface presented error, the email was triggered from the sender “sgf@storaenso.com” and even though the environment was production the body of the message had written “test environment”. Guide the user about changing the parameters “MIS_EMAIL_PATTERN” and “EMAIL_SENDER_PATTERN” and change the value of the translation key of the text with the environment to the correct value.

IS-7750 – Silviculture: “Operation Closed” in the road contract screen

When closing an operation, the Closed Operation flag is not being flagged. This is because programming has not been performed for this behavior to occur in the system. The system will change the Closed Operation flag when an operation is approved with the Operation Close option checked.

IS-7952 – Administration: Error Exporting to Excel

When you try to export a cube to excel when there are more than 60,000 lines, the system generates an error because it is not prepared for this. The export method has been changed so that it can generate the rows when the file has more than 60,000 rows.