My Oracle Support Banner

ReSA - "getStoreDays" service not fetching any Records (Doc ID 2988155.1)

Last updated on NOVEMBER 20, 2023

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 23.1 and later
Information in this document applies to any platform.


On : 23.1 version, Merch - Integration

ReSA getStoreDays works in 2 different modes.
For one store or for a store list, which is defined in ReSA.
Store list in ReSA is related to employee and the defined traits (sa_user_loc_traits).
Customer tries to use this functionality and it works fine with a user.
He now needs the same functionality for OAuth2 authorization.
In Oauth2, where he does not have a user, but a client_id (IDCS_OAUTH_2_APPID) and a token.
We tried to add this client_id as employee in ReSA, but it is not allowed.
API for one store works as expected, as no trait and user in ReSA is required.

The ReST getStoreDays service with OAuth2 authorization is not fetching any records.

The issue can be reproduced at will with the following steps:
1. Try to add a OAuth2 Client ID to add to employee in Resa.

The issue has the following business impact:
Due to this issue, the ReST getStoreDays service is not fetching any records.




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

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