1. Web Reports Gen2 Report Creation
  2. Changes in Gen2 Web Reports

Changes in Gen2 Web Reports

Chained Reports: Chained reports are not available in Gen2 reports. Chained reports combine multiple reports into a single page document. As an alternative, you can embed the individual reports in a dashboard and execute the dashboard from the web reports tab, however this cannot be linked to a WMS action button, such as BOL or Packing slip etc.

“Missing” categories: As noted earlier in this document, the category design has been revamped completely to provide a more granular, table level view of the data. As such, categories cannot be compared one to one with Gen1 categories. Almost all the data accessible via Gen1 is accessible in Gen2. A handful of entities have been left out of Gen2 and are planned to be added in future updates.

Company Parameter Changes

The company parm "WR2_FILTER_DATETIME_IN_FACILITY_TZ" allows the DateTime clauses in the web report gen2 to be interpreted based on the your current facility timezone instead of interpreting the DateTime based on the server time. However, the data returned by the report will still display the output based on the server time, by default. As before that can be converted to facility time using the available conversion function.

Another company parameter WR2_EVAL_FORMULAS_IN_DB provides better performance for some functions.

When the company parameter "WR2_EVAL_FORMULAS_IN_DB" default value is set to Yes:
  • If the Company ID is set to 0, then the value is updated to Yes.
  • - If no value is set, the default value for the parameter is updated to Yes.
Note: Some functions used in reports can be evaluated either at the database level or at the Web Reports application level. In all cases, it is faster to evaluate it in the database. The default behavior has been changed to perform this for all customers except for those that have explicitly updated the WR2_EVAL_FORMULAS_IN_DB to no.
Note: There are some innate differences between how Web Reports and databases evaluate formulas. Equivalent formulas may return inconsistent data in some situations. Mathematical equations may have differing levels of precision, which can alter the result. Date functions are known to have some divergent behavior as well.

Improvements for Joins in Reports

The default joins in Gen2 have been improved so that in most common reports, you will not need to edit the joins. New categories have also been added to Web Reports Gen 2 to improve the user experience and eliminate the use of aliases for most common reports. With these new categories, you no longer need to create aliases and complex joins for the most common reports:

  • ib_container as clone of container with filter type = 'I'
    • from_inventory.container_id to be joinable to ib_container
  • iblpn_location as clone of location
    • iblpn_container.location_id to be joinable to ib_location.id
  • pallet_location as clone of location
    • pallet.location_id to be joinable to pallet_location
  • ob_container as clone of container with filter type = 'O'
    • to_inventory.container_id to be joinable to ob_container
  • ob_location as clone of location
    • ob_container.location_id to be joinable to ib_location.id
  • destination_company as clone of company
    • order_hdr.destination_company_id to be joinable to destination_company
  • dest_facility as a clone of facility
    • order_hdr.dest_facility_id to be joinable to dest_facility
  • shipto_facility as a clone of facility
    • order_hdr.shipto_facility_id to be joinable to shipto_facility

Flattened View for Item Hierarchy Definition

To allow easier report creation, Web Reports Gen2 has been updated to include a flattened view for item hierarchy definition, so item hierarchy codes 1 through 5 and group code can be more easily included in reports without the need for aliases and complex joins.