Exact semantic of data from /operations/{operationId}/recordedOutputQuantities

Exact semantic of data from /operations/{operationId}/recordedOutputQuantities › Category: Any › Exact semantic of data from /operations/{operationId}/recordedOutputQuantities
0 Vote Up Vote Down
Ekrem asked 6 months ago

The data structure of the output for the endpoint /operations/{​​​​​​​​operationId}​​​​​​​​/recordedOutputQuantities is an array of quantity booking. How are these quantities to be understood to get the final output quantity of the operation once the operation is completed? Should they be summed up to get the final output quantities for Yield, Scrap and Rework?

Thanks.

1 Answers
0 Vote Up Vote Down
Dominik Amann Staff answered 6 months ago

Hi Ekrem,

yes, the quantities must be summarized. For your proposal it is easier to use the interface /operations/{operationId}/quantitySummary. This interface provides a summary of all quantities of the operation (no booking timeline).

New Event

Vivamus sagittis lacus vel augue laoreet rutrum faucibus dolor auctor. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Nulla vitae elit libero, a pharetra augue. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros.