Update one list

patch

/fscmRestApi/resources/11.13.18.05/maintenanceAssets/{AssetId}/child/PartsListComponent/{ListComponentId}

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
  • Value that uniquely identifies the asset for each component. You can create only one relationship between each value that attribute ListComponentId specifies and that AssetId specifies.
  • Title: Quantity
    Quality of each part list component for the asset. This attribute is optional when creating a part list component for the asset.
  • Value that uniquely identifies the item that is part of the part list for the asset. Asset Item cannot be part of the part list for the same asset.
  • Value that uniquely identifies the organization that creates or uses the asset. The itemOrganizationId for the asset and for the parts list component use the same value.
  • Value that uniquely identifies the parts list item that the asset references.
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 : maintenanceAssets-PartsListComponent-item-response
Type: object
Show Source
  • Value that uniquely identifies the asset for each component. You can create only one relationship between each value that attribute ListComponentId specifies and that AssetId specifies.
  • Title: Quantity
    Quality of each part list component for the asset. This attribute is optional when creating a part list component for the asset.
  • Value that uniquely identifies the item that is part of the part list for the asset. Asset Item cannot be part of the part list for the same asset.
  • Value that uniquely identifies the organization that creates or uses the asset. The itemOrganizationId for the asset and for the parts list component use the same value.
  • Links
  • Value that uniquely identifies the parts list item that the asset references.
Back to Top

Examples

This example describes how to update one parts list in one maintenance asset.

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/maintenanceAssets/AssetId/child/PartsListComponent/ListComponentId"

For example, the following command updates parts list 300100113400236 in maintenance asset 100100053525029:

curl -X PATCH -u "username:password" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/maintenanceAssets/100100053525029/child/PartsListComponent/300100113400236

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.

{
"ComponentQuantity":10
}

Example Response Body

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

{
  "AssetId" : 100100053525029,
  "ComponentQuantity" : 10,
  "ItemId" : 300100013645875,
  "ItemOrganizationId" : 207,
  "ListComponentId" : 300100113400236
}
Back to Top