My Oracle Support Banner

Unable to hard-code the party number in the request payload (Doc ID 2613597.1)

Last updated on DECEMBER 22, 2020

Applies to:

Oracle Fusion B2B Service Cloud Service - Version 11.13.19.07.0 and later
Information in this document applies to any platform.

Symptoms

Customer is using Upsert-mode as true , in REST API integration to Oracle engagement cloud.
It is working fine, when provided a Party Number that already exists in OEC. which mean, it updates the record if there is record found with Party Number tag value.

However, in case when there is no matching record identified with party Number provided, it fails with an error

Below are the header and payload details.

Headers:
Content-Type:application/vnd.oracle.adf.resourceitem+json
Upsert-Mode:true

Payload:

{
  "FirstName": "Test Contact 1207",
  "LastName": "Test Contact 1207",
  "PersonDEO_FlexID_c":"1-23HYS21",
  "EmailAddress":"test12065@gmail.com",
  "PartyNumber": "688"
}


ERROR
-----------------------
Error:
Attribute set for PartyNumber in entity PersonDEO failed

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


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