Update one name

patch

/fscmRestApi/resources/11.13.18.05/assetLogicalHierarchies/{HierarchyId}

Request

Path Parameters
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: Code
    Maximum Length: 30
    Abbreviation that uniquely identifies the asset hierarchy name.
  • Title: Description
    Maximum Length: 240
    Description of the hierarchy.
  • Contains one of the following values: true or false. If true, then the hierarchy name is disabled. If false, then the hierarchy name is enabled. The default value is false.
  • Value that uniquely identifies the hierarchy name. The application generates this value when it creates the hierarchy. This attribute is read-only.
  • Title: Name
    Maximum Length: 120
    Name of the hierarchy.
  • Value that identifies the route asset associated with the hierarchy.
  • Value that identifies the route asset number associated with the hierarchy.
  • Maximum Length: 30
    Code that uniquely identifies the route completion. Valid values are Automatic or Manual, as defined in the lookup ORA_MNT_MX_PROGRAM_WO_CREATE. If set to Automatic, route assets don't need to be marked as complete or skipped during work order reporting. If set to Manual, route assets must be marked as either complete or skipped during work order reporting.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then it indicates a route asset hierarchy. The default value is false.
  • Maximum Length: 1
    Contains one of the following values: true or false. If set to true, then assets can optionally be marked as skipped during work order reporting. If set to false, then all assets must be marked as complete during work order reporting. The default value is false.
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 : assetLogicalHierarchies-item-response
Type: object
Show Source
  • Title: Disabled
    Read Only: true
    Date and time when the hierarchy name becomes inactive.
  • Title: Code
    Maximum Length: 30
    Abbreviation that uniquely identifies the asset hierarchy name.
  • Title: Description
    Maximum Length: 240
    Description of the hierarchy.
  • Contains one of the following values: true or false. If true, then the hierarchy name is disabled. If false, then the hierarchy name is enabled. The default value is false.
  • Value that uniquely identifies the hierarchy name. The application generates this value when it creates the hierarchy. This attribute is read-only.
  • Title: Name
    Maximum Length: 120
    Name of the hierarchy.
  • Links
  • Read Only: true
    Maximum Length: 240
    Description of the route asset number associated with the hierarchy.
  • Value that identifies the route asset associated with the hierarchy.
  • Value that identifies the route asset number associated with the hierarchy.
  • Maximum Length: 30
    Code that uniquely identifies the route completion. Valid values are Automatic or Manual, as defined in the lookup ORA_MNT_MX_PROGRAM_WO_CREATE. If set to Automatic, route assets don't need to be marked as complete or skipped during work order reporting. If set to Manual, route assets must be marked as either complete or skipped during work order reporting.
  • Title: Meaning
    Read Only: true
    Maximum Length: 80
    Meaning of the route completion code.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then it indicates a route asset hierarchy. The default value is false.
  • Maximum Length: 1
    Contains one of the following values: true or false. If set to true, then assets can optionally be marked as skipped during work order reporting. If set to false, then all assets must be marked as complete during work order reporting. The default value is false.
Back to Top

Examples

This example describes how to update one logical hierarchy name.

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/assetLogicalHierarchies/123456789101112"

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.

{
	"HierarchyName": "Hierarchy_Name_Updated",
	"HierarchyCode": "Hierarchy_Code_Updated",
	"HierarchyDescription": "Hierarchy_Description_Updated",
	"HierarchyDisableFlag": "true"
}

Example Response Body

The following example includes the contents of the response body in JSON format:

{
	"HierarchyName": "Hierarchy_Name_Updated",
	"HierarchyCode": "Hierarchy_Code_Updated",
	"HierarchyDescription": "Hierarchy_Description_Updated",
	"HierarchyId": 123456789101112,
	"ActiveEndDate": systemdate,
	"HierarchyDisableFlag": "true"
}
Back to Top