/
Differing functionality on PO Expiration field in Requisitions

Differing functionality on PO Expiration field in Requisitions

Description of Issue

There is differing functionality between Requisitions and Requisition Entry with the PO Expiration field:

In Requisitions, you can enter a PO Expiration date that is before "today's" date, and you receive no message and can save the Requisition.

In Requisition Entry, you are prevented from entering a PO Expiration before today's date:
PO Expiration date is less than today's date.
And you are stopped.

Context
  • Munis
  • Purchasing 
Cause

This is a Munis defect of differing functionality

Resolution

Please download MUN-410308 from the MIU when available.

Additional Information






Related content

Requisitions program not verifying Contract Expiration or Extended Through dates correctly
Requisitions program not verifying Contract Expiration or Extended Through dates correctly
More like this
Requisition Need By Date Calendar does not advance to the next month
Requisition Need By Date Calendar does not advance to the next month
More like this
Auto Posting Purchase Orders failing if buyer is set to require Commodity Codes on transactions
Auto Posting Purchase Orders failing if buyer is set to require Commodity Codes on transactions
More like this
PO Auto Posting is failing, error returned during manual post
PO Auto Posting is failing, error returned during manual post
More like this
Preventing a Contract from being entered on a transaction after its Expiration Date
Preventing a Contract from being entered on a transaction after its Expiration Date
More like this
Unable to see date fields on User Defined Fields in Requisition Entry
Unable to see date fields on User Defined Fields in Requisition Entry
More like this