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 MARCH 30, 2023

Applies to:

Goal

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?
 

Solution

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