Canceling Approved Trip Errors

Owned by Knowledge Assistant
Jul 31, 2024
2 min read
Description of Issue

Attempted cancel of approved status Trip receives error
There was an error in processing your transactions through Enterprise ERP at this time. Please contact your system administrator as well as Transportation for any scheduling issues.

Viewing the Activity Log the following error or errors display for the problem Trip ID:
Munis Error - The request failed with HTTP status 400: Proxy error.
Munis Error - Error processing journal header. Journal was created but couldn't be posted. It can be posted manually in MUNIS

Context

  • Versatrans Trip Tracker (VTTT)

  • Integration

Cause

True cause not yet identified.

Resolution

Perform the following review before contacting support.

  1. Confirm if Enterprise ERP has been correctly updated with posted encumbrance GEL journals then ensure no unneeded journals remain in proof.

    1. Browse to Enterprise ERP > Financials > General Ledger Menu > Journal Entry/History > Journal Inquiry/Print

    2. Search

    3. Enter VTTT into Reference 1 field and Trip ID# into Reference 4 field.

    4. Accept

    5. Use the Browse option or use navigation arrows at bottom of the screen to review posted journals for the trip

      • A single GEL debit amount journal reflects an Approved Status Trip

      • Two GEL journals one with debit and one with credit reflects a Cancelled Trip

  2. Review proof journals to ensure no extra journals are impacting budget. Depending on how many times cancel was attempted.

    1. Browse to Enterprise ERP > Financials > General Ledger Menu > Journal Entry/History >Encumbrance Journal Entry/Proof

    2. Browse

    3. Identify if there are any Proof GEL journals for Short Description/Reference 4 for the Trip ID in question

  3. Contact Versatran Trip Tracker Support for additional review and discussion of how to bring both VTTT and EERP into sync and ensure trip is cancelled.

Additional Information

Possible issue during process: Approving a trip, scheduling a driver, then removing driver moving trip back into approval status. 

  • HTTP status 400 is a bad request error code indicating the server will not process a request due to error. 

    • This may be resulting in a GEL credit journal posted for liquidation in EERP but failure to update status on VTTT Trip.  

    • Additional cancel attempts could result in additional error, which looks to be false

      • Munis Error - Error processing journal header. Journal was created but couldn't be posted. It can be posted manually in MUNIS

      • This maybe false error and system is not creating another journal, work with support to confirm.