Planning Segment Groups
planningSegmentGroups Based on 26C
Look up Planning Segment Groups, with execute parts segmentation and segmentation results. Read-only.
- Operations
- GET (list)GET (one)
- Record key
SegmentGroupId- Required on create
- no create on this resource
- At a glance
- 14 fields0 finders2 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/planningSegmentGroups?fields=CatalogId,CatalogName,CreationDate,Description,GroupName&limit=25&onlyData=true
{
"items": [
{
"CatalogId": 0,
"CatalogName": "<string>",
"CreationDate": "2026-01-31T09:00:00+00:00",
"Description": "<string, max 240>",
"GroupName": "<string, max 120>"
}
],
"count": 25,
"hasMore": true,
"limit": 25,
"offset": 0
}Shapes and placeholders, not real data. Replace https://<your-pod> and the login with your own: this site never sees them. Based on Oracle's 26C REST specification.
Fields 14
| Attribute | Type | Use |
|---|---|---|
CatalogId | number | Searchable |
CatalogName | text | Searchable |
CreationDate | date-time | Read-onlySearchable |
Description | text · max 240 | Searchable |
GroupName | text · max 120 | Searchable |
LastRunDate | date-time | Searchable |
LastUpdateDate | date-time | Read-onlySearchable |
LastUpdatedBy | text · max 64 | Read-onlySearchable |
SegmentGroupId | number | Searchable |
SimulationSetId | number | Searchable |
SimulationSetName | text | Searchable |
SourceSystemId | number | Searchable |
SourceSystemName | text | Searchable |
StatusCode | number | Searchable |
Names, types, labels and flags from Oracle's REST specification (26C). Flexfield and custom attributes vary by pod: check /describe for yours.
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Children 2
Child resources sit under one record: /fscmRestApi/resources/11.13.18.05/planningSegmentGroups/{SegmentGroupId}/child/<name>. Add them to a GET with expand.
ExecutePartsSegmentationGET · POST Execute Parts Segmentation · 6 fieldsExecutionIdJobIdRetainOverridesSaveLastResultSegmentGroupIdStatusCodeSegmentationResultsGET Segmentation Results · 8 fieldsCustomerIdDemandClassIdItemIdLocationIdOverrideSegmentIdPreviousSegmentIdSegmentGroupIdSegmentId
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/planningSegmentGroupsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Narrow with
q=on searchable fields and a smalllimit; for a count usetotalResults=true&limit=1. - Call once and pass the result on to later steps rather than calling the same endpoint again.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:CatalogId, notcatalogid. - Send dates as
YYYY-MM-DD; date-time fields take ISO 8601 with a time zone. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.