Kanban Plans
kanbanPlans Based on 26C
Create, change, delete and look up Kanban Plans, with planned pull sequences. Actions include recalculate and update production.
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE2 actions
- Record key
KanbanPlanId- Required on create
InputTypeKanbanPlanCodeOrganizationId- At a glance
- 10 fields0 finders1 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/kanbanPlans?fields=InputDesignator,InputType,KanbanPlanCode,KanbanPlanDescription,KanbanPlanId&limit=25&onlyData=true
{
"items": [
{
"InputDesignator": "<string, max 10>",
"InputType": "<string, max 30>",
"KanbanPlanCode": "<string, max 10>",
"KanbanPlanDescription": "<string, max 240>",
"KanbanPlanId": 0
}
],
"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 10
| Attribute | Type | Use |
|---|---|---|
InputDesignator | text · max 10 | Optional on createUpdatableSearchable |
InputType | text · max 30 | Required on createSearchable |
KanbanPlanCode | text · max 10 | Required on createSearchable |
KanbanPlanDescription | text · max 240 | Optional on createUpdatableSearchable |
KanbanPlanId | number | Optional on createSearchable |
OrganizationCode | text · max 18 | Optional on createSearchable |
OrganizationId | number | Required on createSearchable |
PlanCutoffDate | date | Read-onlySearchable |
PlanDisableDate | date | Optional on createUpdatableSearchable |
PlanStartDate | date | Read-onlySearchable |
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 1
Child resources sit under one record: /fscmRestApi/resources/11.13.18.05/kanbanPlans/{KanbanPlanId}/child/<name>. Add them to a GET with expand.
PlannedPullSequencesGET · PATCH Planned Kanban Pull Sequences · 18 fieldsAverageDailyDemandCalculatedCardsCalculatedDifferenceCalculatedSizeInventoryItemIdItemNumberKanbanCalculationMethodKanbanPlanIdKanbanSizeLocatorLocatorIdNumberOfCardsPullSequenceIdReplenishmentLeadTimeSafetyStockDaysSubinventoryCodeSubinventoryNameMLSTemporaryCards
Actions 2
POST …/action/recalculate·safetyStockkanbanSizekanbanCardssaveFlagleadTimepullSequenceIdavgDailyDemandPOST …/action/updateProduction·pullSequenceId
Actions use Content-Type: application/vnd.oracle.adf.action+json. A path with a {key} runs on one record.
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/kanbanPlansand 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.
- This resource can change data. Put a human approval step before any create, update, delete or action call.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:InputDesignator, notinputdesignator. - 2 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
- 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. - Text fields have maximum lengths (shown in the field table). Longer values are rejected.