Skip to main content
Skip table of contents

06.22.10-00

R2

Improvements

  1. Equipment Task View

  2. Batch Returning Non-Serial items to a different Site

  3. Ability to set Shipping and Returning Site other than Order Site

  4. Introduced new CID to display Net amount, Discount Amount and Gross Amount from Order Labor Line in Order prints. (R2-19742).

Refer the CID Master document for more details.

  1. Introduced new CID 27004 to Purchase Order print. The CID is one of the UDFs (#9) for PO print.  (R2-19743).

  2. Ensuring compatibility of function based custom reports with Oracle 19c. (R2-19426)
    If you have already been running your R2 instance with Oracle 19C....
    Following two configuration level changes are required to be made, so that R2 Custom reports run as per their usual behavior .

    1. IT Team @UBS will apply Database server level changes.

    2. CC Team @UBS will run a script on your R2 schema to recompile the function-based report objects.
      If you have recently upgraded (from 12C to 19C) or freshly installed a 19C R2 instance
      No further changes are needed to your R2 Instance or your Database Server installation.
      The R2 Custom reports will continue to run as they are expected to behave.

  3. Purging the database (R2-19656)

    What is Data Purging?

    Data purging is the process of permanently removing obsolete data from a specific storage location when it is no longer required. The purging process allows an administrator to permanently remove data from its primary storage location, yet still retrieve and restore the data from the archive copy should there ever be a need.

    Why perform Data Purging?

    Strategies for data purging are often based on specific industry and legal requirements. When carried out automatically through business rules, purging policies can help an organization run more efficiently and reduce the total cost of data storage both on-premises and in the cloud.  Common criteria for data purges include the advanced age of the data or the type of data in question.

    How does the script work in R2?

    Based on your business requirements and legal compliances, the purge script will select Order records, validated as per Order's Status, Date, and Type. The Purge Script can be run manually or scheduled to be run periodically.

    As per the current implementation, any record with the Order status matching either of the following will be purged.

    1. Hold

    2. Back Order

    3. Sold

    4. Reserved

    5. Returned

    6. Missing

    7. Sub Rent

    8. Transfer

    9. Purchase

    10. Not Available

    11. Repair

    12. Lost

    13. Deleted

    However for the following Order status, the purge script will Delink the Purchase or Transfer Order and purge the specific line as well.

    1. Sub Rent Assigned (S-Assigned)

    2. Purchase Assigned (P-Assigned)

    3. S-Filled

    4. S-Out

    5. S-Returned

    6. T-Reserved

    7. Drop Ship

Bug Fixes

  • SR-10528 — Item edit > Comments> Add- System does not accept the special characters to add a comment.

  • SR-10986 —The field 'Model' length was limited to 15 characters which is now extended to 25 characters.

  • SR-10018 —EUV is taking more than a minute to show the data results in 06.22.06-00.

  • SR-11098 —Searching item by item keywords in multiple sites is not working as expected.

  • SR-10385 — Attempt to apply security policies on Configuration Tab failed.

  • SR-11080 — System' utilization continues to remain at unusually high levels.

Labor

Improvements

Retain last saved settings in Graphical Scheduler, Crew => Crew Schedule, My Bookings=> Crew Schedule (R2-15017 and R2-19572)

You no longer need to set the zoom level, layout, etc. each and every time you open Orders in GS and Crew for your convenience.

Now, system retains the last saved for the following options.

  • Sort in Ascending or Descending

  • Group by Ascending or Descending

  • Zoom In/Out or 'To fit'

  • Change the Layout

  • Vertical Zoom

Bug Fixes

  1. SR-8934 — All the e-mail replies from the Crews are not reaching the Planner, few are missing.

  2. SR-10682 — New Schema creation fails if user data has any special characters

  3. SR-10842 — Unable to search the Orders based on the 'Sales Person Full name'.

  4. SR-10412 — System performance is slow when generating the reports.

Mobile Apps

Enhancements

  1. Prep, Dispatch, Receive operations — Shelf and Bin column is added in the grid.

  2. Option to view future 'Reserved Orders' when receiving the items.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.