Get all plan schedules

get

/fscmRestApi/resources/11.13.18.05/planOptions/{PlanId}/child/PlanSchedule

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
  • Used as a predefined finder to search the collection.

    Format ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables

    • PrimaryKey Finds the plan schedule according to the value that identifies the plan schedule.
      Finder Variables
      • TransactionId; integer; Value that uniquely identifies the plan schedule.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AverageArrivalTimeMeasureId; integer; Holds the measure identifier of the average interarrival time in the forecast accuracy measures for the plan schedule.
    • ConsumeComFcstIndicator; integer; Number of days during which planned orders from the feeding production schedule are considered by the supply plan.
    • CreatedBy; string; Name of the user who created the plan.
    • CreationDate; string; Date when the plan was originally created.
    • DemandPlanOutput; integer; Demand plan output measure ID to copy to the supply plan input measure.
    • DemandVariabilityType; number; Type of demand variability to use when calculating the safety stock for the forecasted demand. Valid values are Mean Absolute Deviation, Mean Absolute Percentage Error, and Intermittent.
    • DesignatorType; number; Short code for the type of demand schedule.
    • DesignatorTypeText; string; Name for type of demand schedule.
    • EndItemDemMeasureId; integer; Forecast measure for demand for end items.
    • FirmHorizonDays; number; Number of days during which planned orders from the feeding production schedule are considered by the supply plan.
    • IncludePO; number; Indicates whether purchase orders are used. The possible values are 1 for Yes and 2 for No.
    • IncludePlnOrd; number; Indicates whether planned orders are used. The possible values are 1 for Yes and 2 for No.
    • IncludePsResultsIndicator; integer; Enables the supply plan to include the output of the production scheduling in its next plan run.
    • IncludeTargetDemands; number; Value that indicates whether the target demand is used. Possible values are 1-Yes and 2-No.
    • IndepDemMeasureId; integer; Selected measure that contains the independent demand.
    • InputScheduleId; integer; Identifier of the demand plan schedule to be consumed in a supply plan.
    • InputType; number; Short code for the type of demand schedule.
    • IntermittentDemMeasureId; integer; Demand measure that indicates whether the demand has an irregular demand pattern.
    • InterplantDemandIndicator; number; Indicates whether the interplant demand is used. The possible values are 1 for Yes and 2 for No.
    • LastUpdateDate; string; Date when the user most recently updated the plan.
    • LastUpdateLogin; string; Last time the user logged into the system.
    • LastUpdatedBy; string; User who performed the most recent update on the plan.
    • MadOrMapeMeasureId; integer; ID of the MAD or MAPE forecast error measure.
    • MadOrMapeMeasureType; integer; Specifies whether the forecast error type is MAD or MAPE. This is applicable for demand that's not intermittent.
    • MapeValue; integer; Value of the mean absolute percentage error for the item-organization combination.
    • ObjectVersionNumber; integer; Plan version number.
    • OptionDemandMeasureId; integer; ID of the option demand measure of the forecast.
    • OrganizationId; integer; Organization name. Set to 23453 for schedules to indicate that their forecast error type isn't organization-specific.
    • PlanId; integer; Value that uniquely identifies the plan.
    • PlanningPercentMeasureId; integer; ID of the planning percentage measure for the forecast.
    • PolicyParameters; number; Header for a column with the value used to specify whether to use the policy parameters of the specified plan.
    • Probability; integer; Indicates the probability value of the schedule.
    • ReplDemandSchedules; integer; Indicates whether to use a specific schedule as a demand schedule.
    • ScenarioSet; integer; Identifies the scenario set to be used in calculations.
    • ShipTo; integer; Forecast consumption level for the demand schedule. Values vary depending on the published level of the demand schedule.
    • SupplyPlanInput; integer; Identifier of the demand schedule measure to use in supply planning.
    • TransactionId; integer; Value that uniquely identifies the demand plan schedule.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 : planOptions-PlanSchedule
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : planOptions-PlanSchedule-item-response
Type: object
Show Source
Nested Schema : Forecast Constrained Planning Attributes
Type: array
Title: Forecast Constrained Planning Attributes
The attributes for a demand schedule attached to a plan. User can enable or disable these attributes for forecast consumption by the demand schedules attached to the plan. These attributes, such as Backward Days and Forward Days, determine the range of days from the forecast demand date that the forecast can be consumed in that range by sales orders.
Show Source
Nested Schema : Plan Schedule Measure Levels
Type: array
Title: Plan Schedule Measure Levels
The plan schedule measure levels specified for a demand schedule in the plan options. In supply planning, dimensions such as time can have multiple measure levels. Users can specify measure levels for these dimensions: Time, Demand Class, Customer, Organization, and Product. For example the level for Time could be Day, the level for Customer could be Customer Site, and the level for Product could be Item. On the other hand, the level for organization is fixed as Organization and the level for demand class is only Demand Class.
Show Source
Nested Schema : planOptions-PlanSchedule-FcstConstPlanningAttr-item-response
Type: object
Show Source
Nested Schema : planOptions-PlanSchedule-PlanScheduleMeasureLevel-item-response
Type: object
Show Source
Back to Top