Create associations between installed base and fixed assets

post

/fscmRestApi/resources/11.13.18.05/installedBaseAssets/{AssetId}/child/fixedAssetAssociations

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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Date and time when the association between installed base and fixed asset becomes inactive.
  • Date and time when the association between installed base and fixed asset becomes active.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the association is made inactive automatically. If false, then the association is not inactivated automatically. This attribute value is set conditionally during the updation of the asset.
  • Value that uniquely identifies the fixed asset.
  • Title: Fixed Asset Number
    Maximum Length: 255
    Number that uniquely identifies the fixed asset.
  • Maximum Length: 30
    Contains a value when the autoTerminationFlag is set to yes. The value indicates the message code and the message text is displayed in the UI conditionally.
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 : installedBaseAssets-fixedAssetAssociations-item-response
Type: object
Show Source
Back to Top