Get one kanban plan

get

/fscmRestApi/resources/11.13.18.05/kanbanPlans/{KanbanPlanId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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