Create kanban plan

post

/fscmRestApi/resources/11.13.18.05/kanbanPlans

Request

Header Parameters
  • 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".
  • 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.
  • 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
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Planned Kanban Pull Sequences
Type: array
Title: Planned Kanban Pull Sequences
A 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: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • 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".
  • 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.
Body ()
Root Schema : kanbanPlans-item-response
Type: object
Show Source
Nested Schema : Planned Kanban Pull Sequences
Type: array
Title: Planned Kanban Pull Sequences
A Kanban pull sequence that belongs to a Kanban plan, identified by the Kanban plan ID.
Show Source
Nested Schema : kanbanPlans-PlannedPullSequences-item-response
Type: object
Show Source
  • Title: Average Daily Demand
    Average daily demand for the Kanban item, in the pull sequence unit of measure
  • Title: Calculated Number of Cards
    Number of Kanban cards calculated by planning when the calculation method is to calculate cards
  • Title: Calculated Difference
    Read Only: true
    Difference between the current value and the planning-recommended value, either the number of Kanban cards or the Kanban size, based on the calculation method
  • Title: Calculated Card Size
    Kanban size calculated by planning when the calculation method is to calculate size, in the pull sequence unit of measure
  • Title: Item
    Read Only: true
    The unique identifier of the item defined in the pull sequence.
  • Title: Item
    Read Only: true
    Maximum Length: 300
    Item number in the pull sequence.
  • Title: Calculation
    Read Only: true
    Maximum Length: 30
    Default Value: DO_NOT_CALCULATE
    Indicates whether planning calculates the number of Kanban cards or the Kanban size for upcoming periods based on demand.
  • Read Only: true
    Default Value: -1
    The application generated unique identifier of a Kanban plan.
  • Title: Current Card Size
    Read Only: true
    Size of the Kanban bin.
  • Links
  • Read Only: true
    Maximum Length: 255
    Name of the destination locator of the item in the pull sequence.
  • Title: Destination Locator
    Read Only: true
    Identifier of the destination locator of the item in the pull sequence.
  • Title: Current Number of Cards
    Read Only: true
    Number of Kanban cards in the pull sequence.
  • Read Only: true
    Unique identifier of the Kanban pull sequence. Its value is an application-generated unique ID.
  • Title: Lead Time
    Time required to source the item.
  • Title: Safety Stock
    Safety stock days for the pull sequence
  • Title: Destination Subinventory
    Read Only: true
    Maximum Length: 10
    Name of the destination subinventory of the item in the pull sequence.
  • Read Only: true
    Maximum Length: 255
    Name of the destination subinventory (MLS) for the item in the kanban card.
  • Title: Temporary Cards
    Read Only: true
    Planned Kanban Pull Sequences
Back to Top

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:


                  
Back to Top