Create kanban plan
post
/fscmRestApi/resources/11.13.18.05/kanbanPlans
Request
Header Parameters
-
Metadata-Context: string
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version: string
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
-
Upsert-Mode: string
Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
InputDesignator: string
Title:
External ForecastMaximum Length:10Represents the external forecast designator or demand plan designator. -
InputType(required): string
Title:
Demand TypeMaximum Length:30Represents the type of demand provided to the plan such as external forecast or actual production. -
KanbanPlanCode(required): string
Title:
Plan NameMaximum Length:10Represents the Kanban designator, which serves as a reference label to distinguish individual Kanban plans. -
KanbanPlanDescription: string
Title:
Plan DescriptionMaximum Length:240The description of plan used in the Kanban planning process. -
KanbanPlanId: integer
(int64)
The unique identifier of a Kanban plan. Its value is an application generated unique identifier.
-
OrganizationCode: string
Maximum Length:
18Code of the inventory organization to which this pull sequence belongs. -
OrganizationId(required): integer
(int64)
The organization identifier represents the manufacturing plant to which this Kanban plan belongs.
-
PlanDisableDate: string
(date)
Title:
Inactive OnThe plan disable date used in the Kanban planning process. -
PlannedPullSequences: array
Planned Kanban Pull Sequences
Title:
Planned Kanban Pull SequencesA Kanban pull sequence that belongs to a Kanban plan, identified by the Kanban plan ID.
Nested Schema : Planned Kanban Pull Sequences
Type:
arrayTitle:
Planned Kanban Pull SequencesA Kanban pull sequence that belongs to a Kanban plan, identified by the Kanban plan ID.
Show Source
Nested Schema : kanbanPlans-PlannedPullSequences-item-post-request
Type:
Show Source
object-
AverageDailyDemand: number
Title:
Average Daily DemandAverage daily demand for the Kanban item, in the pull sequence unit of measure -
CalculatedCards: integer
Title:
Calculated Number of CardsNumber of Kanban cards calculated by planning when the calculation method is to calculate cards -
CalculatedSize: number
Title:
Calculated Card SizeKanban size calculated by planning when the calculation method is to calculate size, in the pull sequence unit of measure -
ReplenishmentLeadTime: number
Title:
Lead TimeTime required to source the item. -
SafetyStockDays: number
Title:
Safety StockSafety stock days for the pull sequence
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Root Schema : kanbanPlans-item-response
Type:
Show Source
object-
InputDesignator: string
Title:
External ForecastMaximum Length:10Represents the external forecast designator or demand plan designator. -
InputType: string
Title:
Demand TypeMaximum Length:30Represents the type of demand provided to the plan such as external forecast or actual production. -
KanbanPlanCode: string
Title:
Plan NameMaximum Length:10Represents the Kanban designator, which serves as a reference label to distinguish individual Kanban plans. -
KanbanPlanDescription: string
Title:
Plan DescriptionMaximum Length:240The description of plan used in the Kanban planning process. -
KanbanPlanId: integer
(int64)
The unique identifier of a Kanban plan. Its value is an application generated unique identifier.
-
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
OrganizationCode: string
Maximum Length:
18Code of the inventory organization to which this pull sequence belongs. -
OrganizationId: integer
(int64)
The organization identifier represents the manufacturing plant to which this Kanban plan belongs.
-
PlanCutoffDate: string
(date)
Title:
Demand Cutoff DateRead Only:trueThe plan cutoff date used in the Kanban planning process. -
PlanDisableDate: string
(date)
Title:
Inactive OnThe plan disable date used in the Kanban planning process. -
PlannedPullSequences: array
Planned Kanban Pull Sequences
Title:
Planned Kanban Pull SequencesA Kanban pull sequence that belongs to a Kanban plan, identified by the Kanban plan ID. -
PlanStartDate: string
(date)
Title:
Demand Start DateRead Only:trueThe demand start date used in the Kanban planning process.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : Planned Kanban Pull Sequences
Type:
arrayTitle:
Planned Kanban Pull SequencesA Kanban pull sequence that belongs to a Kanban plan, identified by the Kanban plan ID.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Nested Schema : kanbanPlans-PlannedPullSequences-item-response
Type:
Show Source
object-
AverageDailyDemand: number
Title:
Average Daily DemandAverage daily demand for the Kanban item, in the pull sequence unit of measure -
CalculatedCards: integer
Title:
Calculated Number of CardsNumber of Kanban cards calculated by planning when the calculation method is to calculate cards -
CalculatedDifference: integer
Title:
Calculated DifferenceRead Only:trueDifference between the current value and the planning-recommended value, either the number of Kanban cards or the Kanban size, based on the calculation method -
CalculatedSize: number
Title:
Calculated Card SizeKanban size calculated by planning when the calculation method is to calculate size, in the pull sequence unit of measure -
InventoryItemId: integer
(int64)
Title:
ItemRead Only:trueThe unique identifier of the item defined in the pull sequence. -
ItemNumber: string
Title:
ItemRead Only:trueMaximum Length:300Item number in the pull sequence. -
KanbanCalculationMethod: string
Title:
CalculationRead Only:trueMaximum Length:30Default Value:DO_NOT_CALCULATEIndicates whether planning calculates the number of Kanban cards or the Kanban size for upcoming periods based on demand. -
KanbanPlanId: integer
(int64)
Read Only:
trueDefault Value:-1The application generated unique identifier of a Kanban plan. -
KanbanSize: integer
Title:
Current Card SizeRead Only:trueSize of the Kanban bin. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
Locator: string
Read Only:
trueMaximum Length:255Name of the destination locator of the item in the pull sequence. -
LocatorId: integer
(int64)
Title:
Destination LocatorRead Only:trueIdentifier of the destination locator of the item in the pull sequence. -
NumberOfCards: integer
Title:
Current Number of CardsRead Only:trueNumber of Kanban cards in the pull sequence. -
PullSequenceId: integer
(int64)
Read Only:
trueUnique identifier of the Kanban pull sequence. Its value is an application-generated unique ID. -
ReplenishmentLeadTime: number
Title:
Lead TimeTime required to source the item. -
SafetyStockDays: number
Title:
Safety StockSafety stock days for the pull sequence -
SubinventoryCode: string
Title:
Destination SubinventoryRead Only:trueMaximum Length:10Name of the destination subinventory of the item in the pull sequence. -
SubinventoryNameMLS: string
Read Only:
trueMaximum Length:255Name of the destination subinventory (MLS) for the item in the kanban card. -
TemporaryCards: integer
Title:
Temporary CardsRead Only:truePlanned Kanban Pull Sequences
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Links
- PlannedPullSequences
-
Parameters:
- KanbanPlanId:
$request.path.KanbanPlanId
A Kanban pull sequence that belongs to a Kanban plan, identified by the Kanban plan ID. - KanbanPlanId:
Examples
This example describes how to create one Kanban plan.
Example cURL Command
Use the following cURL command to submit a request on the REST resource.
curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/kanbanPlans"
Example Request Body
The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it updates.
{
"KanbanPlanCode": "KP_C3_102",
"KanbanPlanDescription": "KP_C3_101 - Description",
"InputDesignator": "AV_RING_1b",
"InputType": "EXTERNAL_FORECAST",
"OrganizationId": 207,
"PlanDisableDate": "2026-12-16"
}
Example Response Body
The following example includes the contents of the response body in JSON format: