We are on GP 10.0. We are using a home built system and integrating it into GP as Purchase Orders in some cases. We are using eConnect for this and I had a question about some of the dates that are causing failures.
I will just say that these PO's are for non-inventory items (services) and we don't care about the dates that the distribution model might use for planning sales and backorders. But apparently we are bound by their logic. All our PO's have one line item so I may use header and line terminology without specifying. These dates though, all pertain to the line level.
The main culprit here is the Released By Date. We don't map this node. It is a date time value in the database and has the standard 01/01/1900 value when you don't use it.
1. Create a new PO - Po Status of 1 Release By Date = 01/01/1900 / Required Date 12/7/2010
2. Partially Receive the PO - PO Status of 2. Release By Date = 01/01/1900 / Required Date 12/7/2010
3. Update the PO (even with no change), we are using the update if exists flag (maybe someone put a note in the other system, still calls eConnect on the save event)
Release By Date = 12/08/2010 / Required Date 12/7/2010 (you could not manually type this in the PO, is goes against the business logic)
The release by date is being set even though not mapped in eConnect as GetDate().
Try to update again - eConnect error "The Required Date cannot be before the released by date."
Go into the PO, delete the released by date, essentially setting it to 01/01/1900.
Update the PO, it worked, but it sets the released by date back to GetDate().
Even if I map the Released By Date Node (would just assume 01/01/1900 hard coded), it gets totally overwritten by GetDate() in the eConnect Proc. It never comes through as the value that I put there. But it does get past the eConnect Logic check in the proc when I map it, because I'll bet it does a check on these 2 dates before it forces it to be GetDate(). Meaning that I map the node, and I don't get errors, but it still inserts the date in a way that the window would not let you type it.
The worst part is that I don't even care about these dates at all and they are driving me nuts.
We are talking about thousands of Purchase Orders here that are getting errors on update and it won't allow a save in our other system because of the error. But the error is being caused by eConnect. I have to use macros now several times a week to clear this date so people can update the PO's
Has anyone seen this before. What do I do when eConnect is the culprit?
