Primary Key In ASAP XML Request Causing SARM Error " Example Order [XXXXXX] already exists and is in a state that cannot be amended"
(Doc ID 2062841.1)
Last updated on SEPTEMBER 03, 2018
Applies to:Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.
On : 7.0.2 version,
Primary Key in ASAP XML Request
In this case there are multiple Northbound systems connecting to ASAP for provisioning for various types of services.
The Customer has a situation where 2 or more upstream systems send the same value in the field PRIMARYKEY of the ASAP XML request.This causes an error thrown in the SARM process as shown below.
Example Order [XXXXXX] already exists and is in a state that cannot be amended
Is there a possibility that ASAP can validate the request based on the apiClientId+ primarykey?
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