Get one attribute sequence

get

/fscmRestApi/resources/11.13.18.05/productionSchedulingOrganizations/{OrganizationId}/child/attributeSequences/{attributeSequencesUniqID}

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=
  • This is the hash key of the attributes which make up the composite key--- OrganizationId, WorkCenterId, ResourceId and AttributeId ---for the Attribute Sequences resource and used to uniquely identify an instance of Attribute Sequences. The client should not generate the hash key value. Instead, the client should query on the Attribute Sequences collection resource with a filter on the primary key values in order to navigate to a specific instance of Attribute Sequences.

    For example: attributeSequences?q=OrganizationId=<value1>;WorkCenterId=<value2>;ResourceId=<value3>;AttributeId=<value4>
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 : productionSchedulingOrganizations-attributeSequences-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 300
    Abbreviation that identifies the attribute that's enabled for scheduling.
  • Read Only: true
    Maximum Length: 2000
    Description of the associated attribute.
  • Value that uniquely identifies the attribute for an organization. It's a primary key of the attribute.
  • Number that indicates the attribute sequence in the ideal sequence.
  • Attribute Value Sequences
    Title: Attribute Value Sequences
    The Attribute Value Sequences resource manages the user-specified sequence in which attribute values are processed in a manufacturing resource.
  • Read Only: true
    Maximum Length: 64
    User who created the resource attribute sequence.
  • Read Only: true
    Date and time when the user created the resource attribute sequence.
  • Maximum Length: 30
    Rule for the resource that defines the user-defined attribute sequence rule across scheduling buckets. Valid values are RestartSequence, ContinueSequence, and ReverseSequence.
  • Read Only: true
    Maximum Length: 40
    Abbreviation that identifies the descriptive flexfield used in Oracle Manufacturing Cloud for scheduling attributes of the organization.
  • Read Only: true
    Maximum Length: 80
    Abbreviation that identifies the flexfield context code used in Oracle Manufacturing Cloud for scheduling attributes of the organization.
  • Contains one of the following values: true or false. If true, then automatically generate attribute value sequences. If false, then don't automatically generate attribute value sequences. The default value is false.
  • Read Only: true
    Date and time when the user most recently updated the resource attribute sequence.
  • Read Only: true
    Maximum Length: 64
    User who most recently updated the resource attribute sequence.
  • Read Only: true
    Maximum Length: 32
    Login that the user used when updating the resource attribute sequence.
  • Links
  • Value that uniquely identifies the inventory organization that's enabled for scheduling. It's a primary key of the inventory organization.
  • Maximum Length: 300
    Abbreviation that identifies the production resource.
  • Value that uniquely identifies the resource that's used in the changeover. It's a primary key of the resource.
  • Maximum Length: 120
    Name of the resource used to define the resource attribute sequence.
  • Read Only: true
    Maximum Length: 30
    Abbreviation that identifies the segment used in Oracle Manufacturing Cloud for scheduling attributes of the organization.
  • Maximum Length: 100
    Abbreviation that identifies the work center.
  • Value that uniquely identifies the work center for the resource that's used in the changeover. It's a primary key of the work center.
  • Maximum Length: 120
    Name of the work center. This attribute is used to define the resource attribute sequence.
Nested Schema : Attribute Value Sequences
Type: array
Title: Attribute Value Sequences
The Attribute Value Sequences resource manages the user-specified sequence in which attribute values are processed in a manufacturing resource.
Show Source
Nested Schema : productionSchedulingOrganizations-attributeSequences-attributeValueSequences-item-response
Type: object
Show Source
Back to Top