My Oracle Support Banner

Supplier Discrepancy Type Is Not Getting Enforced Via VendorDelivery API Like It Happens Through UI (Doc ID 2868188.1)

Last updated on MAY 11, 2022

Applies to:

Oracle Retail Store Inventory Management - Version 16.0.3 and later
Information in this document applies to any platform.


When setting Supplier Discrepancy Type to 2 (to not allow any discrepancies) and user enters received qty not equal to expected qty, then SIM UI throw error "This Supplier does not allow discrepancy".
But if using webservice confirmVendorDeliveryCarton: vendorDeliveryCarton with received qty not equal to expected qty then it does not throw error but it puts container into 'Submitted' status.
Why API does not enforce 'Supplier discrepancy type' as it does in UI?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.