TMS Issue Tracking - QA and Production

Tracking Report in Legacy View for ezVision is Missing

Need this to apply unmatched status messages to the load. Example inbound loads with no PO Number.

  • Astrophel Evora
  • Apr 1 2020
  • MercuryGate Review
  • Attach files
  • Astrophel Evora commented
    July 22, 2020 21:47

    TMS-I-105 is the same issue but for EDI 210's. Proposed solution is to add EZV prefix to the inbound files to route them down to Commerce Services Transporation enterprise

  • Astrophel Evora commented
    May 06, 2020 18:02

    Update from Mark. The unmatched messages on the Newgistics level can be moved to Transportation but only after all carriers have been moved into ezVision. This way, Parcel Services can still have current access.

  • Astrophel Evora commented
    April 02, 2020 04:32

    After further review, the issue is being reframed as such. The unmatched status messages are on the Newgistics level which is not the level where the users reside. Users are on the Commerce Services Transportation level.

    Can the loader put the unmatched status messages on the Commerce Services Transportation level. Historically, unmatched status messages were put on Parcel Services where the users resided, so this should be possible.

  • Astrophel Evora commented
    April 01, 2020 16:05

    Mark showed us that the report could be configured to True from the users screen at the Newgistics level.

  • Astrophel Evora commented
    April 01, 2020 01:14

    As an example attached the unmatched DAFG status messages for the 3/30 inbound loads that are now in ezVision. We need the team to be able to match these updates to the loads, have the PRO applied, update the QtyPickup and WtPickup, then kick off the re-rate.