Add production output details

post

/productionMonitoring/clientapi/v2/productionPlans/{plan-id}/output

This operation adds production output details to the production plan. This method supports the request header with name 'X-ORACLE-IOT-ORG', which allows targeting requests to different organizations. The value of this request header should contain the organization identifier.

Request

Supported Media Types
Path Parameters
  • The identifier created by the Oracle IoT Cloud Service for the production plan.
Header Parameters
  • This method supports the request header with name 'X-ORACLE-IOT-ORG', which allows targeting requests to different organizations. The value of this request header should contain the organization identifier.
Body ()
Root Schema : ProductionPlanOutput_create
Type: object
Show Source
Back to Top

Response

Supported Media Types

200 Response

Successfully processed.
Body ()
Root Schema : ProductionPlanOutput_receive
Type: object
Show Source

400 Response

Bad Request. The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

401 Response

Unauthorized. The request requires user authentication.

403 Response

Forbidden. The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.

404 Response

Not Found. The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
Back to Top

Examples

curl -X POST 
   -u <username>:<password>
   -H 'Accept: application/json'
   -H 'Content-Type: application/json'
   https://iotserver/productionMonitoring/clientapi/v2/productionPlans/{plan-id}/output

Example of Request Body

The following example shows the content of the request body in JSON format:


{
"actualQuantity":0.0,
"endTime":1469184297746,
"expectedQuantity":0.0,
"externalId":"61d76382623a-2ddb",
"factory":"The identifier of the factory the production plan is created for.",
"idealCycleTime":0.0,
"machine":"The identifier of the machine the production plan is created for.",
"operator":"The identifier of the operator the production plan is created for.",
"product":"The identifier of the product the production plan is created for.",
"productionLine":"The identifier of the production line the production plan is created for.",
"rejectDetails":"Reject details",
"rejectQuantity":0.0,
"rejectReason":"Description for the reject reason.",
"routingTask":"The identifier of the routing task the production plan is created for.",
"scrapDetails":"Scrap details",
"scrapQuantity":0.0,
"scrapReason":"Description for the scrap reason.",
"startTime":1469184297746,
"workOrder":"The identifier of the work order the production plan is created for.",
"workOrderNumber":"The work order number for the production plan. It is unique within a factory."
}

Example of Response Body

The following example shows the content of the response body in JSON format:


{
"actualQuantity":0.0,
"endTime":1469184297746,
"endTimeAsString":"2016-07-22T10:44:57.746Z",
"expectedQuantity":0.0,
"externalId":"1edc2f6f4775-3e76",
"factory":"The identifier of the factory the production plan is created for.",
"id":"63994e986e96-d8a",
"idealCycleTime":0.0,
"machine":"The identifier of the machine the production plan is created for.",
"operator":"The identifier of the operator the production plan is created for.",
"product":"The identifier of the product the production plan is created for.",
"productionLine":"The identifier of the production line the production plan is created for.",
"rejectDetails":"Reject details",
"rejectQuantity":0.0,
"rejectReason":"Description for the reject reason.",
"routingTask":"The identifier of the routing task the production plan is created for.",
"scrapDetails":"Scrap details",
"scrapQuantity":0.0,
"scrapReason":"Description for the scrap reason.",
"startTime":1469184297746,
"startTimeAsString":"2016-07-22T10:44:57.746Z",
"type":"FACTORY",
"workOrder":"The identifier of the work order the production plan is created for.",
"workOrderNumber":"The work order number for the production plan. It is unique within a factory."
}



Complete cURL Example

The following example shows a complete cURL command that you can use to perform the described operation:

curl -X POST 
   -u <username>:<password>
   -H 'Accept: application/json'
   -H 'Content-Type: application/json'
   -d '{"actualQuantity":0.0,"endTime":1469184297746,"expectedQuantity":0.0,"externalId":"61d76382623a-2ddb","factory":"The identifier of the factory the production plan is created for.","idealCycleTime":0.0,"machine":"The identifier of the machine the production plan is created for.","operator":"The identifier of the operator the production plan is created for.","product":"The identifier of the product the production plan is created for.","productionLine":"The identifier of the production line the production plan is created for.","rejectDetails":"Reject details","rejectQuantity":0.0,"rejectReason":"Description for the reject reason.","routingTask":"The identifier of the routing task the production plan is created for.","scrapDetails":"Scrap details","scrapQuantity":0.0,"scrapReason":"Description for the scrap reason.","startTime":1469184297746,"workOrder":"The identifier of the work order the production plan is created for.","workOrderNumber":"The work order number for the production plan. It is unique within a factory."}'
   https://iotserver/productionMonitoring/clientapi/v2/productionPlans/1d9f43d92e1-aff/output



Note that in the request, https://iotserver will be replaced by the name and port of your assigned IoT Cloud Service instance. The format of the Cloud Service instance is https://myinstance-myidentitydomain.iot.us.oraclecloud.com and the default port is 443.
Back to Top