My Oracle Support Banner

Orders with Old Prefix Causes Integration Error after Order Id Prefix Updated (Doc ID 2858042.1)

Last updated on MAY 30, 2024

Applies to:

Oracle Commerce Cloud Service - Version 21.4.11 and later
Information in this document applies to any platform.

Symptoms

In some scenario order id prefix must be updated to match the order id form in customer's order management service (OMS). However, after the order id prefix is updated, some orders submitted can still have id with old prefix. This breaks the integration with customer's OMS. For instance, currently the order id has no prefix. Now you want order id to have 'O' prefix such as O123456, etc. After this change, the server continues to receive submitted orders without prefix. Since the customer's OMS expects the order id to have leading 'O', the integration fails.

Cause

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
Symptoms
Cause
Solution
 1. Delete all incomplete orders immediately
 2. Delete all incomplete orders after a grace period
 3. Convert the incomplete orders to new orders
References


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