1. REST API for Oracle Supply Chain Management Cloud
  2. Tasks
  3. Supply Chain Planning
  4. Supply Plans
  5. Planning Supplies
  6. Pegged Demands

Get all pegged demands

get

/fscmRestApi/resources/11.13.18.05/supplyPlans/{PlanId}/child/PlanningSupplies/{TransactionId}/child/PeggedDemands

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=
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 Find the pegged demand according to the value that identifies the pegged demand.
      Finder Variables
      • PeggingId; integer; Value that uniquely identifies the pegged demand.
  • 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:
    • DemandId; integer; Value that identifies the pegged demand.
    • EndDemandId; integer; Value that identifies the end pegged independent demand.
    • EndDemandOrderNumber; string; Number that identifies the order associated with the pegged independent demand.
    • Item; string; Name of the item associated with the supply.
    • OrderNumber; string; Number that identifies the order associated with the demand.
    • OrderQuantity; number; Quantity associated with the demand.
    • OrderTypeText; string; Type of demand such as forecast or sales order. A list of accepted values is defined in the lookup type MSC_ORDER_TYPE.
    • Organization; string; Name of the organization associated with the demand.
    • PeggedQuantity; number; Quantity of the supply that's pegged to this demand.
    • PeggingId; integer; Value that identifies the association of the supply with the pegged demand.
    • PreviousPeggingId; integer; Value that identifies the next level of supply and demand in the supply chain.
    • SuggestedDueDate; string; Date when a demand is expected to be satisfied.
  • 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 : supplyPlans-PlanningSupplies-PeggedDemands
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : supplyPlans-PlanningSupplies-PeggedDemands-item-response
Type: object
Show Source
Back to Top

Examples

This example describes how to get all pegged demands.

Example cURL Command

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

curl -u username:password "https://servername/fscmRestApi/resources/version/supplyPlans/PlanId/child/PlanningSupplies/TransactionId/child/PeggedDemands"

For example:

curl -u username:password "https://servername/fscmRestApi/resources/version/supplyPlans/300100545960039/child/PlanningSupplies/99874539/child/PeggedDemands"

Example Response Body

The following shows an example of the response body in JSON format.

{
    "items": [
        {
            "PeggingId": 157,
            "DemandId": 2991580,
            "Item": "AI-ABP-5000",
            "Organization": "PDSCM1",
            "OrderTypeText": "Forecast",
            "OrderNumber": "AI-AB-FC2",
            "OrderQuantity": -10,
            "SuggestedDueDate": "2030-03-13",
            "PeggedQuantity": 10,
            "PreviousPeggingId": null,
            "EndDemandId": 2991580,
            "EndDemandOrderNumber": "AI-AB-FC2",
            "links": [
                {
                    "rel": "self",
                    "href": "https://servername/fscmRestApi/resources/version/supplyPlans/300100545960039/child/PlanningSupplies/99874539/child/PeggedDemands/157",
                    "name": "PeggedDemands",
                    "kind": "item"
                },
                {
                    "rel": "canonical",
                    "href": "https://servername/fscmRestApi/resources/version/supplyPlans/300100545960039/child/PlanningSupplies/99874539/child/PeggedDemands/157",
                    "name": "PeggedDemands",
                    "kind": "item"
                },
                {
                    "rel": "parent",
                    "href": "https://servername/fscmRestApi/resources/version/supplyPlans/300100545960039/child/PlanningSupplies/99874539",
                    "name": "PlanningSupplies",
                    "kind": "item"
                }
            ]
        }
    ],
    "count": 1,
    "hasMore": false,
    "limit": 25,
    "offset": 0,
    "links": [
        {
            "rel": "self",
            "href": "https://servername/fscmRestApi/resources/version/supplyPlans/300100545960039/child/PlanningSupplies/99874539/child/PeggedDemands",
            "name": "PeggedDemands",
            "kind": "collection"
        }
    ]
}
Back to Top