Feature - Skip Orders With Duplicate PO Numbers in Sales Order Import
Release Date: 5/21/2024
Revised Date: 08/27/2024
Version: 8.5 and Up
Background
Sales Order Import would flag orders with duplicate purchase order numbers in Elliott as a warning, but allow the orders to import and place them on hold. This behavior makes sense for most of the Elliott users because they like to review the duplicate PO and decide if it should be deleted. However, certain trading partners using 830 (Forecast and Release) may send duplicate release orders which have previously already been sent. This creates a scenario of receiving a sales order import batch of 100 orders, of which only a few are new orders. Hence there's a need to skip these orders instead of importing them into Elliott.
Feature
A flag was added to the Customer EDI Profile on screen 2, field 11 when the duplicate PO criteria is set to a value other than N, None. A second flag will appear: Skip Orders With Duplicate PO Numbers? The default is N, but a value of Y will cause the import to skip the orders.
Sales Order Import will skip orders for that customer when a duplicate purchase order number is encountered. The duplicate purchase order check applies only to the order header, including posted orders that have not been purged and moved to order history. This check does not extend to the invoice header.
To use this feature, it is assumed the following flag is turned on in Global Setup -> Cop-Func -> Order Header Screen:
5. Duplication Criteria For PO # in Sales Order ?
The value should be set to 'C,' 'S,' or 'P.' If the value is set to 'N,' the system will not check for duplicate purchase orders.
Programs Modified: ARCUSEDI, ARCUSEXT.FD, CPORDIMP
MAD