I took a quick look at the schema and there can be only one expiration date per item/warehouse/lot combination.

In Sage 500, there are a couple of mechanisms that could be used here: A security event and/or a message. 

Messages can be suppressed, while a security event cannot.  Messages by themselves cannot stop an action, while a security event can. Both mechanisms must be in the source code.

I did not do a deep dive into this as it would require a ticket for me to do that.  I did not test it out in the UI.  However, I do see a couple of messages that MAY be currently in play here by the verbiage of the message, which might possibly be suppressible. 

1.  "{0} Lot {1} expired on {2}. ".  This is known within the code as MessageNo = 166180.
2.  "The expiration date entered "{0}" does not match previous receipts of this lot which expire on {1}. Do you wish to replace the previous lot expiration date with the new date?". This is known within the code as MessageNo = 166267.

The {x} values are just variables and you can probably guess what they are given the context of the message.   The MessageNo values may assist in unsuppresing a message previously suppressed.

At first glance, I would say that the second message MAY already be coded.   If this message is suppressed, then it will not show.  Even if not suppressed, it would likely allow a user to answer a yes and change the expiration date for the entire lot.  To prevent someone from doing that or require an approval to do that, a security event would need to be added in addition to the message.   The security event would need to be added in source code, and would be considered an  enhancement  if it is not already coded.   Please keep in mind that adding a security event may also require it be placed in more than one location, and ideally would  be placed in any location that allows a user to update the expiration date for a lot.

Adding this as an enhancement via Sage, if approved, would likely only show up in a future version of Sage 500.  A customization could likely be made by one of our fine qualified partners to accomplish the same thing for your particular version.  A partner could probably do this faster than waiting for a new Sage release (assuming it was approved as an enhancement).  If you have qualified programming staff on-site you could make the changes yourself but that would require that you have purchased our SDK in the past (the SDK contains source code for the vast majority of our applications).

Our support team may be able to help you unsuppress a message that has been suppressed in the past (I do not believe there is an existing application to do this), but they cannot add a security event.  They could also likely help you with removing the suppressibility of a given message.

With any luck, hopefully this helps explain things a little better and lets you know some additional options without getting too complicated.

I took a quick look at the schema and there can be only one expiration date per item/warehouse/lot combination.

In Sage 500, there are a couple of mechanisms that could be used here: A security event and/or a message. 

Messages can be suppressed, while a security event cannot.  Messages by themselves cannot stop an action, while a security event can. Both mechanisms must be in the source code.

I did not do a deep dive into this as it would require a ticket for me to do that.  I did not test it out in the UI.  However, I do see a couple of messages that MAY be currently in play here by the verbiage of the message, which might possibly be suppressible. 

1.  "{0} Lot {1} expired on {2}. ".  This is known within the code as MessageNo = 166180.
2.  "The expiration date entered "{0}" does not match previous receipts of this lot which expire on {1}. Do you wish to replace the previous lot expiration date with the new date?". This is known within the code as MessageNo = 166267.

The {x} values are just variables and you can probably guess what they are given the context of the message.   The MessageNo values may assist in unsuppresing a message previously suppressed.

At first glance, I would say that the second message MAY already be coded.   If this message is suppressed, then it will not show.  Even if not suppressed, it would likely allow a user to answer a yes and change the expiration date for the entire lot.  To prevent someone from doing that or require an approval to do that, a security event would need to be added in addition to the message.   The security event would need to be added in source code, and would be considered an  enhancement  if it is not already coded.   Please keep in mind that adding a security event may also require it be placed in more than one location, and ideally would  be placed in any location that allows a user to update the expiration date for a lot.

Adding this as an enhancement via Sage, if approved, would likely only show up in a future version of Sage 500.  A customization could likely be made by one of our fine qualified partners to accomplish the same thing for your particular version.  A partner could probably do this faster than waiting for a new Sage release (assuming it was approved as an enhancement).  If you have qualified programming staff on-site you could make the changes yourself but that would require that you have purchased our SDK in the past (the SDK contains source code for the vast majority of our applications).

Our support team may be able to help you unsuppress a message that has been suppressed in the past (I do not believe there is an existing application to do this), but they cannot add a security event.  They could also likely help you with removing the suppressibility of a given message.

With any luck, hopefully this helps explain things a little better and lets you know some additional options without getting too complicated.