A large number of Incoming Customer Orders stop every morning during the scheduled EDI file import with 'ORA-20112: CustomerOrder.EXIST2: The Customer Order object already exists' — even though the orders genuinely don't already exist, and manually approving the stopped order from Incoming Customer Order succeeds immediately with no further action needed.

All FAQ questions / Integrations and APIs

Answer

A confirmed working workaround (after escalating to IFS support without a definitive root-cause fix) was enabling 'Allow Lapses in Number Sequences' on the Coordinator Group used for these orders — found at Application Base Setup > General Data > Coordinator Groups, on the relevant Coordinator Group record. After enabling this checkbox, the false 'object already exists' errors on incoming EDI orders stopped recurring, even across later update levels where the underlying issue apparently still exists in some form. This points to the false-positive 'already exists' check being tied to how the Customer Order numbering sequence is validated, which the lapses-allowed setting relaxes.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions