1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Product Lifecycle Management
  4. itemStructures
  5. Component
  6. ReferenceDesignator

Create

post

/fscmRestApi/resources/11.13.18.05/itemStructures/{BillSequenceId}/child/Component/{ComponentSequenceId}/child/ReferenceDesignator

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=
  • 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=
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
Nested Schema : ReferenceDesignatorDFF
Type: array
Descriptive Flexfield extensions for structure reference designators.
Show Source
Nested Schema : schema
Type: object
Show Source
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 : itemStructures-Component-ReferenceDesignator-item-response
Type: object
Show Source
Nested Schema : ReferenceDesignatorDFF
Type: array
Descriptive Flexfield extensions for structure reference designators.
Show Source
Nested Schema : itemStructures-Component-ReferenceDesignator-ReferenceDesignatorDFF-item-response
Type: object
Show Source
Links
ReferenceDesignatorDFF
Parameters:
  • BillSequenceId: $request.path.BillSequenceId
  • ComponentSequenceId: $request.path.ComponentSequenceId
  • ReferenceDesignatorSequenceId: $request.path.ReferenceDesignatorSequenceId
Back to Top

Examples

This example describes how to create one reference designator.

Example cURL Command

Use the following cURL command to submit a request on the REST resource.

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/itemStructures/BillSequenceId/child/Component/ComponentSequenceId/child/ReferenceDesignator"

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 creates. 

{           
"ReferenceDesignator": "RD001",
"Description": "Add from Rest"
}

Example Response Body

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

{
    "ACDType": 1,
    "ChangeLineId": -1,
    "ChangeNotice": null,
    "ReferenceDesignator": "RD001",
    "CreationDateTime": "2018-06-28T05:56:33.001+00:00",
    "LastUpdateDateTime": "2018-06-28T05:56:33.199+00:00",
    "Description": "Add from Rest",
    "ReferenceDesignatorSequenceId": 300100159659336,
    "ACDTypeValue": null,
...
}
Back to Top