DATASECURITIES REST API USES DIFFERENT SECURITYCONTEXTVALUE FOR POST AND GET (Doc ID 2777833.1)

Last updated on JULY 09, 2022

Applies to:

Symptoms

 When sending a POST request to the
/fscmRestApi/resources/11.13.18.05/dataSecurities REST API endpoint to create
a new data assignment, the SecurityContextValue item must be populated with a
security context name.

When sending a GET request to the same endpoint, the
SecurityContextValue item for that record is the security context
description, not the security context name.

This mismatch makes it difficult to validate newly created data assignments or to confirm existing data
assignments, since there is no way to match security context names with
security context descriptions.

Example:
1. New fixed asset book is created, with NAME="TEST US CORP" and
DESCRIPTION="TEST US Corporate Book"

2. Create a new data assignment via REST API:
Endpoint: /fscmRestApi/resources/11.13.18.05/dataSecurities
HTTP request: POST
Request payload:

...
}

In the  GET response is "TEST US CORP" is not  listed as a value, so the user can't programmatically validate the successful Post.

Cause

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