My Oracle Support Banner

Status Key Values Are Not Fetched In The SiebelMessage In EAI Siebel Adapter Upsert Method Output when StatusObject is missing or false. (Doc ID 2373580.1)

Last updated on MARCH 14, 2018

Applies to:

Siebel CRM - Version 16.11 [IP2016] and later
Information in this document applies to any platform.

Symptoms

On : 16.11 [IP2016] version, Siebel EAI

ACTUAL BEHAVIOR
---------------
A workflow calls EAI Siebel Adapter , method Upsert and the integration object is configured to return the Id and operation fields as status key fields.
This workflow is published as a web service and called from SOAPUI.
Even though the actual operation was "Insert" , the status key returns "Upsert".
And the bogus Id passed as input is returned in the status key instead of the system generated id for the newly created record.

EXPECTED BEHAVIOR
-----------------------
the actual operation performed (Insert) and the new row id should be returned

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. just call the web service from soapui passing in operation as upsert and a row id as part of the user key.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot obtain the accurate operation and id in the development environment.

Changes

 

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
Changes
Cause
Solution
 Example with StatusObject
References


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