Update one backlog planning option

patch

/fscmRestApi/resources/11.13.18.05/backlogPlanningOptions/{ConfigurationId}

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=
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
  • Title: Planning Horizon in Days
    Value that specifies the number of days over which demand is considered by backlog plan.
  • Title: Display constraints for configure-to-order items, shipment sets, and arrival sets
    Value that indicates whether the constraints for configure-to-order and sets order will be calculated by the backlog plan.
  • Title: Past-Due Supply and Demand Considered in Days
    Value that determines which past due supplies and demands are considered in the backlog plan.
  • Value that uniquely identifies the assignment set.
  • Title: Assignment Set Name
    Maximum Length: 255
    Name of the assignment set used.
  • Value that uniquely identifies the demand priority rule.
  • Title: Demand Priority Rule
    Maximum Length: 255
    Name of the default priority rule that's used in planning demands in backlog management.
  • Title: Default Demand Fulfillment Lead Time in Days
    Value that specifies the default lead time that's used to determine the fulfillment lead time date on demands.
  • Title: Horizon Start Date
    Date that signifies the start of the planning horizon and is typically defaulted to the system date.
  • Maximum Length: 255
    Text of the error message, if any, encountered when creating or updating the backlog planning options.
  • Title: Supply Plans
    Maximum Length: 4000
    Values of the supply plan unique identifiers or the plan ID that are used as supply schedules in backlog management.
  • Maximum Length: 255
    Names of the supply plans that are used as supply schedules in backlog management.
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 : backlogPlanningOptions-item-response
Type: object
Show Source
Back to Top

Examples

This example describes how to update one backlog planning option.

Example cURL Command

Use the following cURL command to submit a request on the REST resource.

curl -X PATCH -u "username:password" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -d 'request payload'  "https://servername/fscmRestApi/resources/version/backlogPlanningOptions/ConfigurationId"
For example:
curl -X PATCH -u "username:password" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -d 'request payload'  "https://servername/fscmRestApi/resources/version/backlogPlanningOptions/-1"

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.

{
"BucketsPerHorizon": 360
}

Example Response Body

The following example includes the contents of the response body in JSON format:
{
    "BucketsPerHorizon": 360,
    "CalculateConstraint": 1,
    "CategorySetId": 10154,
    "ConfigurationId": -1,
    "CreatedBy": "BLM_ALL",
    "CreationDate": "2019-03-27T09:14:04+00:00",
    "DaysPastdue": 10,
    "DefaultAssignmentSetId": 100000012037099,
    "DefaultPriorityRuleId": 300100178581705,
    "DemFulfilLeadTime": 10,
    "HorizonStart": null,
    "LastBaselineHorizonStart": null,
    "SupplyPlan": "300100550649238",
    "SupplyPlanName": "BLM_RT-SP-INT",
    "DefaultAssignmentSetName": "BLM_ASET_DEFAULT",
    "DefaultPriorityRuleName": "Default_reqdate_revenue",
    "CategorySetName": "GOP_Catalog",
    "Message": null,
    "links": [
        {
            "rel": "self",
            "href": "https://servername/fscmRestApi/resources/version/backlogPlanningOptions/-1",
            "name": "backlogPlanningOptions",
            "kind": "item"
        },
        {
            "rel": "canonical",
            "href": "https://servername/fscmRestApi/resources/version/backlogPlanningOptions/-1",
            "name": "backlogPlanningOptions",
            "kind": "item"
        }
    ]
}
Back to Top