Mobile demand planning dashboard shows blank charts after data refresh in ofc-23d

SCM Oracle Fusion Cloud SCM
, , , , , , , ,
1

Our demand planning team uses the mobile dashboard for reviewing forecasts on the go, but we’re encountering a frustrating issue after upgrading to 23D. Whenever we refresh the demand data, all the charts go blank and show no data, even though the underlying tables clearly have forecast information.

The desktop version works perfectly fine, so this appears to be mobile-specific. I suspect it might be related to API version compatibility or how the mobile app is handling the JSON response. Here’s the error I’m capturing in the browser console when accessing via mobile:


GET /fscmRestApi/resources/demandPlanning/forecasts
Status: 200 OK
Response: {"items":[], "count":0}

The response shows empty items even though we have active forecasts. User permissions seem fine since desktop access works. Has anyone dealt with mobile dashboard rendering issues after the 23D update?

2

Another thing to check - the mobile dashboard might be using cached metadata about the chart structure that’s now outdated after the 23D upgrade. Try clearing the mobile app cache or reinstalling the app. Also verify that the chart component library in your mobile framework is compatible with the new data format. We had to update our charting library from version 3.x to 4.x to handle the new JSON structure.

3

The empty response despite a 200 OK status is telling. This usually means the query executed successfully but returned no results due to filtering or permissions. Since desktop works, I’d focus on the mobile-specific security context. Mobile apps often use a different authentication flow (OAuth vs session-based), and the user context might not be carrying over the necessary data security attributes. Check your VPD policies for demand planning data.

4

Check the API version being called by your mobile app. In 23D, Oracle moved some demand planning endpoints to a newer API version (11.13.18.05 to 11.13.19.02). Your mobile app configuration might still be pointing to the old version. Also, verify that your mobile app’s OAuth token has the correct scope for accessing demand planning data - the scopes changed in 23D.

5

We experienced something similar. The issue was that the mobile dashboard was applying default filters that excluded all our data. Check the filter parameters being sent in the API request - there might be date range filters or organization filters that are too restrictive. Try accessing the API endpoint directly with Postman to see what parameters are being passed and what the actual response looks like.

6

I can provide a complete solution addressing all three key areas:

API Version Compatibility: The 23D upgrade introduced breaking changes to the demand planning mobile APIs. Your mobile app is likely calling the deprecated API version. Update your mobile app configuration:


Mobile App Config > API Endpoints
Base URL: /fscmRestApi/resources/11.13.19.02/
Deprecated: /fscmRestApi/resources/11.13.18.05/

The new API version uses a different response structure. Verify your mobile app is requesting the correct version by checking the request headers for the REST-Framework-Version parameter.

User Data Access Permissions: Even though desktop access works, mobile API calls use a different security context. Verify these permissions:

  1. Ensure mobile users have both ‘Demand Planner’ and ‘Demand Planning Mobile User’ roles
  2. Check the data security policies - mobile API calls don’t inherit the same session-based securities
  3. Verify the OAuth scope includes ‘urn:opc:resource:consumer::all’ for full data access

You can test permissions by making a direct REST call with the mobile user’s credentials:


curl -X GET "https://your-instance/fscmRestApi/resources/11.13.19.02/demandPlanning/forecasts" \
-H "Authorization: Bearer {mobile_token}" \
-H "REST-Framework-Version: 7"

If this returns empty results while the desktop session returns data, it’s definitely a permission scope issue.

JSON Payload Structure: The 23D update changed how forecast data is structured in the mobile API response. The old format used flat arrays; the new format uses nested objects with metadata. Update your mobile app’s data parser to handle the new structure:

Old format (23C):

{"items": [{"forecastId": "F001", "quantity": 100}]}

New format (23D):

{"data": {"forecasts": [{"id": "F001", "metrics": {"quantity": 100}}]}}

Your mobile app’s chart rendering code needs to be updated to parse the new nested structure. If you’re using a custom mobile app, update the data transformation layer. If you’re using Oracle’s standard mobile framework, ensure you’ve applied the latest mobile app patch (Patch 35892441 for 23D mobile dashboard compatibility).

Additionally, check your mobile app’s API response caching. The app might be caching the old empty response. Clear the cache by:

  1. Uninstalling and reinstalling the mobile app
  2. Or programmatically clearing cache: Settings > Application > Clear Data

After applying these fixes, your mobile dashboard should display charts correctly. The key is ensuring API version alignment, proper OAuth scopes, and updated JSON parsing logic to handle the 23D payload structure.