Problem with Req Due Date Defaulting to PO Logic for AutoSourced POs
Here's our dilemma...
We went live with PeopleSoft 9.1 in Oct 2011 and are using eProcurement requisitions. We find it problematic that autosourced POs inherit the Req Line Due Date for the following reasons:
1. The requisitioners are not Supply Chain personnel and do not have knowledge regarding contracted lead times for specific items.
2. Therefore, the Due Date entered on the req by the requisitioner is frequently inconsistent with the actual contract delivery terms, and negatively skews supplier performance data.
3. Instructing requisitioners to leave the Req Due Date fields blank for AutoSource items would allow for PeopleSoft to accuratly calculate the PO Line Schedule Due Date based on Lead Days, but it is impractical to do so because the requisitioner does not know which items are AutoSource candidates. Having then always leave the req Due Date blank severs the communication mechanism for requisitioners to let buyers know when the material is desired for the balance of req items (non AutoSource req items).