Support for Data Extract API

We’re introducing a new entity-level parameter: create_mod_ts_query_mode (values: AND or OR, default: OR). This parameter controls the logical operator to be applied to the create_ts and mod_ts filters, during extraction.

This improves accuracy and efficiency of incremental data extracts by allowing customers to enforce both “modified since” and “created since initial extract” criteria in a single query, reducing unnecessary data pull, and preventing back-dated records from being reintroduced.

PARAMETER BEHAVIOR

Parameter Behavior
create_mod_ts_query_mode = AND
  • when both create_ts and mod_ts filters are provided for an entity, both conditions are enforced (AND logic).
  • This supports scenarios where you want only records modified since X and created after the initial extract date.
create_mod_ts_query_mode = OR
  • (default, current behavior) - When create_ts and/or mod_ts are provided, the filters are combined using OR logic, broadening the result set to records that meet either condition.

IMPORTANT NOTE:  The status_id filter remains optional, and when provided it is always applied with AND logic, regardless of create_mod_ts_query_mode.

ENHANCED OAuth SUPPORT FOR DATA EXTRACT API

We’ve introduced new enhancements to the WMS Data Extract API to improve security, integration flexibility, and data reliability for downstream systems.

The Data Extract API now supports the OAuth 2.0 client credentials grant type, enabling secure, system-to-system integrations without requiring user-based authentication. External systems (such as FDI and other integrated solutions) can now authenticate using client ID and client secret.

Service User Configuration

A new “Service User” flag has been introduced to simplify API-based access control:

When enabled:

  • The user is authenticated via OAuth client credentials.
  • Access is restricted to APIs only (no UI or RF access).
  • Ideal for integration and automation use cases.

When disabled:

  • The user continues to authenticate via standard credentials or SSO (existing behavior).

IMPROVED CSV EXPORT HANDLING

To ensure compatibility with downstream systems consuming CSV data:

  • Automatic escaping of double quotes (") is now supported.
  • Double quotes within text fields are escaped using a backslash (\"), ensuring proper CSV parsing and data integrity.

Steps to enable and configure

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.