Update one plan schedule

patch

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

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=
  • 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=
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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
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-patch-request
Type: object
Show Source
Nested Schema : planOptions-PlanSchedule-PlanScheduleMeasureLevel-item-patch-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 : 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