Share
ReportHello:
Has anyone been successful in facilitating the processing of lot number expiration dates through GP SmartConnect? Let me tell you what I mean by “facilitate”.
A GP 2010 client uses SmartConnect to, among other things, import sales orders. They do not import lot numbers or their corresponding expiration dates from the sales order source files, because GP assigns lot numbers to line items on sales orders.
But, after importing, the expiration date is showing as “00/00/0000” instead of the correct expiration date that is set up for the lot in GP. (No error appears in SmartConnect.)
Now, if the client pulls up one of the imported sales orders and removes and adds back the lot number to that sales order manually, the correct expiration date appears.
So, it is not an issue with how GP processes lot numbers and expiration dates. And, really, it is not a problem with how SmartConnect imports. Again, the client’s source files do not contain lot numbers or expiration dates. And, truthfully, it makes no sense from a business or “logic” standpoint for the source files to contain that data, since GP has the capability of assigning lot numbers and expiration dates.
What makes this more interesting is that the client, separately, uses an EDI tool called eBridge that also imports sales orders. This tool, in fact, is also having the same issue where the expiration dates are showing as “00/00/0000”.
Does anyone have any thoughts on how to get the correct expiration dates to appear after importing through SmartConnect? Since both import tools are having this issue, could it be some sort of bug?
John
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
