1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Manufacturing
  4. Workstations

Create workstations

post

/fscmRestApi/resources/11.13.18.05/workstations

Request

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 : Attachments
Type: array
Title: Attachments
The attachments that are associated with workstations.
Show Source
Nested Schema : Flexfields for Workstations
Type: array
Title: Flexfields for Workstations
Descriptive flexfields are fields used to provide additional information for workstations.
Show Source
Nested Schema : Workstation Equipment Instances
Type: array
Title: Workstation Equipment Instances
Equipment resource instances associated with the workstation.
Show Source
Nested Schema : schema
Type: object
Show Source
Nested Schema : Attachment Previews
Type: array
Title: Attachment Previews
A preview of workstation attachments.
Show Source
Nested Schema : schema
Type: object
Show Source
Nested Schema : schema
Type: object
Show Source
  • Title: Context Segment
    Maximum Length: 80
    Descriptive flexfield context name for workstations.
  • Title: Context Segment
    Descriptive flexfield context display value for workstations.
  • Value that uniquely identifies the workstation. You can use a flexfield with this resource. A flexfield is a flexible data field that your organization can use to modify your implementation without having to write programming code.
Nested Schema : workstations-WorkstationEquipmentInstance-item-post-request
Type: object
Show Source
  • Value that uniquely identifies the equipment instance that is associated with this workstation.
  • Value that uniquely identifies the workstation. It's a primary key that the application generates when it creates a workstation.
  • Value that uniquely identifies the equipment instance associated with workstation. It's a primary key that the application generates when it creates an equipment instance association with a workstation. This attribute is required.
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 : workstations-item-response
Type: object
Show Source
Nested Schema : Attachments
Type: array
Title: Attachments
The attachments that are associated with workstations.
Show Source
Nested Schema : Flexfields for Workstations
Type: array
Title: Flexfields for Workstations
Descriptive flexfields are fields used to provide additional information for workstations.
Show Source
Nested Schema : Workstation Equipment Instances
Type: array
Title: Workstation Equipment Instances
Equipment resource instances associated with the workstation.
Show Source
Nested Schema : workstations-Attachments-item-response
Type: object
Show Source
Nested Schema : Attachment Previews
Type: array
Title: Attachment Previews
A preview of workstation attachments.
Show Source
Nested Schema : workstations-Attachments-AttachmentsPreview-item-response
Type: object
Show Source
Nested Schema : workstations-WorkstationDFF-item-response
Type: object
Show Source
  • Title: Context Segment
    Maximum Length: 80
    Descriptive flexfield context name for workstations.
  • Title: Context Segment
    Descriptive flexfield context display value for workstations.
  • Links
  • Value that uniquely identifies the workstation. You can use a flexfield with this resource. A flexfield is a flexible data field that your organization can use to modify your implementation without having to write programming code.
Nested Schema : workstations-WorkstationEquipmentInstance-item-response
Type: object
Show Source
Links
Attachments
Parameters:
  • WorkstationId: $request.path.WorkstationId
The attachments that are associated with workstations.
WorkstationDFF
Parameters:
  • WorkstationId: $request.path.WorkstationId
Descriptive flexfields are fields used to provide additional information for workstations.
WorkstationEquipmentInstance
Parameters:
  • WorkstationId: $request.path.WorkstationId
Equipment resource instances associated with the workstation.
Back to Top

Examples

This example describes how to create workstations.

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/workstations"

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. 

{
    "OrganizationId": 207,
    "WorkstationCode": "SPRAY_WORKSTATION_A",
    "WorkstationName": "Spray Paint WorkStation A",
    "WorkstationDescription": "Spray Paint WorkStation A",
    "WorkCenterName": "SPRAY_WC"
}

Example Response Body

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

{
    "OrganizationId": 207,
    "OrganizationCode": "M1",
    "OrganizationName": "Seattle Manufacturing",
    "WorkstationId": 300100545640760,
    "WorkStationCode": "SPRAY_WORKSTATION_A",
    "WorkStationName": "Spray Paint WorkStation A",
    "WorkStationDescription": "Spray Paint WorkStation A",
    "WorkCenterId": 300100071642891,
    "WorkCenterCode": "PAINT_WA",
    "WorkCenterName": "SPRAY_WC",
    "WorkCenterDescription": "Paint",
    "links": [
    {
        "rel": "self",
        "href": "https://servername/fscmRestApi/resources/version/workstations/300100545640760"
        ...
    }
    ]
}
Back to Top