Get one resource

get

/fscmRestApi/resources/11.13.18.05/workCenters/{WorkCenterId}/child/WorkCenterResource/{WorkCenterResourceUniqID}

Request

Path Parameters
  • Value that uniquely identifies the work center. It is a primary key that the application generates when it creates a work center.
  • This is the hash key of the attributes which make up the composite key--- ResourceId and WorkCenterId ---for the Work Center Resources resource and used to uniquely identify an instance of Work Center Resources. The client should not generate the hash key value. Instead, the client should query on the Work Center Resources collection resource with a filter on the primary key values in order to navigate to a specific instance of Work Center Resources.

    For example: WorkCenterResource?q=ResourceId=<value1>;WorkCenterId=<value2>
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 : workCenters-WorkCenterResource-item-response
Type: object
Show Source
  • Title: Available 24 Hours
    Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the work center resource is available 24 hours each day. If false, then the work center resource is not available 24 hours each day. A work center resource that is not available 24 hours each day is available only during the shifts that you assign to this work center resource. A work center resource is available in shifts only if this attribute is set to false. The default value is true.
  • Title: Check Capable to Promise
    Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then Oracle Global Order Promising Cloud considers the capacity of this work center resource during order promising. If false, then Global Order Promising does not consider this capacity. If this attribute is set to false, then the capable-to-promise (CTP) check does not consider the capacity of this work center resource. The default value is false.
  • Title: Efficiency
    Default Value: 100
    Percent of time that the work center resource requires to finish the task.
  • Read Only: true
    Date when the resource becomes inactive.
  • Links
  • Title: Code
    Read Only: true
    Maximum Length: 30
    Abbreviation that identifies the work center resource.
  • Title: Description
    Read Only: true
    Maximum Length: 240
    Description of the work center resource.
  • Value that uniquely identifies the work center resource. It is a primary key that the application generates when it creates a work center resource.
  • Title: Name
    Maximum Length: 80
    Name of the work center resource.
  • Title: Default Units Available
    Number of work center resources assigned to this work center.
  • Read Only: true
    Maximum Length: 30
    Indicates the type of the resource, equipment, or labor.
  • Title: Type
    Read Only: true
    Maximum Length: 30
    Indicates the type of the resource, equipment, or labor.
  • Title: Utilization
    Default Value: 100
    Percent of time that is available to perform the task.
  • Value that uniquely identifies the work center production calendars record. This is an application generated unique ID.
  • Read Only: true
    Value that uniquely identifies the work center that this work center resource references.
  • Shifts for Work Center Resources
    Title: Shifts for Work Center Resources
    The Shifts for Work Center Resources manages the shifts for each work center resource. The application automatically creates each shift when you assign a production resource to a work center.
Nested Schema : Shifts for Work Center Resources
Type: array
Title: Shifts for Work Center Resources
The Shifts for Work Center Resources manages the shifts for each work center resource. The application automatically creates each shift when you assign a production resource to a work center.
Show Source
Nested Schema : workCenters-WorkCenterResource-WorkCenterResourceShift-item-response
Type: object
Show Source
Back to Top

Examples

This example describes how to get one resource.

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/workCenters/WorkCenterId/child/WorkCenterResource/WorkCenterResourceUniqID"

For example, the following command gets one resource:

curl -u username:password "https://servername/fscmRestApi/resources/version/workCenters/WorkCenterId/child/WorkCenterResource?q=ResourceId=300100073217879;WorkCenterId=300100073218337"

Example Response Body

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

{
      "ResourceId" : 300100073217879,
      "ResourceName" : "CST_Resource",
      "ResourceDescription" : "Resource Created to Test Cost Planning Tests",
      "WorkCenterId" : 300100073218337,
      "ResourceQuantity" : 100,
      "Available24HoursFlag" : true,
      "CheckCtpFlag" : true,
      "UtilizationPercentage" : 90,
      "EfficiencyPercentage" : 80,
      "links" : [ {
        ...
        }]
}
Back to Top