Production APIs
See AOP
| HTTP method | POST |
| URI | https://api.rambase.net/system/api/api-operations/100296 |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| Successful HTTP status code | 200 |
| API resource identifier | 2437, version 3 |
The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.
Parameters
This field is optional.
>ReleaseForProduction
If true, the orders should be released for production (batch parameter, not dictionary field).
This field is optional.
>{Boolean}</ReleaseForProduction>NewScheduledStartDate
Specifies a new scheduled start date on the production work order beeing splitted.
This field is optional.
>{Date}</NewScheduledStartDate>ProductionWorkOrders
This field is optional.
>ProductionWorkOrder
This field is optional.
>ScheduledStartDate
Scheduled/planned date of production start
This field is optional.
>{Date}</ScheduledStartDate>Quantity
The quantity that will be (or has been) produced
This field is optional.
>{Decimal}</Quantity>Parameters
This field is optional.
": {ReleaseForProduction
If true, the orders should be released for production (batch parameter, not dictionary field).
This field is optional.
": "{Boolean}",NewScheduledStartDate
Specifies a new scheduled start date on the production work order beeing splitted.
This field is optional.
": "{Date}",ProductionWorkOrders
This field is optional.
": [ScheduledStartDate
Scheduled/planned date of production start
This field is optional.
": "{Date}",Quantity
The quantity that will be (or has been) produced
This field is optional.
": "{Decimal}"The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.
| $access_token String, optional | After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time. |
| $db String, optional | Set the database/company for the request |
| $useMinimumVersion Integer, optional | Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information. |
| $lang String, optional | Specifies the language used in the response, following the 3-letter ISO-639-1 [lll] |
Read more about filters and sorting on how to use filter parameters and named filters.
Read more about filters and sorting on how to use sortable parameters
Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
List of available operations/actions for this resource.
See the operations documentation for more information about API operations.
Possible error codes the response might return:
| Error 101015 HTTP 404 | Permission not found |
| Error 101746 HTTP 404 | Product structure not found. Id: {0} |
| Error 105377 HTTP 400 | Picking not initialized for Material: {0} on Operation: {1}. |
| Error 101812 HTTP 400 | Not all parts have been picked |
| Error 106981 HTTP 400 | Validation failed. Not all parts are assigned to stock for {0} |
| Error 100858 HTTP 400 | No LCM found |
| Error 100859 HTTP 400 | Mismatch between net quantity on the production work order and sum of quantity on LCM |