REST APIs (GET)
Oracle Fusion Cloud Supply Chain Planning provides several REST resources for integrating with external systems.
A typical use of REST APIs is in a coexistence scenario where a third-party execution system is integrated to work with Oracle Supply Chain Planning.
Applicable to All REST Resources
Best Practices
Use these guidelines to help improve performance.
- When possible, provide identifiers such as item ID, organization ID, and supplier ID rather than the names of entities.
- Limit the GET operations to 3000 records at a time (5000 is a maximum).
- Avoid using filters that are derived and must be evaluated rows by row. For example, customer site, bucket type, and release status.
- Avoid OR conditions with LIKE clauses.
- Avoid querying master records that use only child query criteria.
Constraints
Large queries might be aborted after 5 minutes.
Applicable to Multiple REST Resources
These resources are:
- Supply Plans / Planning Demands
- Demand and Supply Plans / Planning Demands
- Replenishment Plans / Planning Demands
- Simulation Set / Planning Demands
- Supply Plans / Planning Supplies
- Demand and Supply Plans / Planning Supplies
- Replenishment Plans / Planning Supplies
- Simulation Set / Planning Supplies
Key Features
- Create or update demands.
- Create or update supplies.
Best Practices
Using item, organization, or order type when querying planning demands or planning supplies will run the query faster.