Product APIs
Create a new traceable material element for product unit.
| HTTP method | POST |
| URI | https://api.rambase.net/product/units/{productUnitId}/traceable-materials |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {productUnitId} |
Product unit identifier
Integer, minimum 100000 |
| Successful HTTP status code | 200 |
| API resource identifier | 3465, version 6 |
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.
ProductId
Required/mandatory field
Product identifier
Minimum value: 10000
>{Integer}</ProductId>ProductUnit
This field is optional.
>ProductUnitId
Product unit identifier
Minimum value: 100000
This field is optional.
>{Integer}</ProductUnitId>ProductId
Required/mandatory field
Product identifier
Minimum value: 10000
": "{Integer}"ProductUnit
This field is optional.
": {ProductUnitId
Product unit identifier
Minimum value: 100000
This field is optional.
": "{Integer}"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 100089 HTTP 404 | Product not found |
| Error 101139 HTTP 400 | COSTCUR is missing |
| Error 100563 HTTP 400 | Currency {0} is not supported by the system |
| Error 101044 HTTP 400 | Purchase Quote Item expired on {0} |
| Error 101050 HTTP 400 | Purchase Quote Item quantity needs to be increased |
| Error 101045 HTTP 400 | The purchase quote item needs to be activated |
| Error 101401 HTTP 400 | The Ship and debit purchase quote must be in the same database as the stock assignment |
| Error 101047 HTTP 400 | The purchase quote item has too low available quantity |
| Error 101400 HTTP 400 | Supplier credit claim has been created from shipping advice |
| Error 102483 HTTP 400 | Finance project is required for general ledger account {0} |
| Error 102484 HTTP 400 | Asset is required for general ledger account {0} |
| Error 102485 HTTP 400 | Dimension {0} ({1}) is required for general ledger account {2} |
| Error 101313 HTTP 400 | Department number is not valid: {0} |
| Error 101320 HTTP 400 | The project number is not valid: {0} |
| Error 101500 HTTP 400 | Project {0} could not be used : Check project FromPeriod and ToPeriod. |
| Error 101501 HTTP 400 | Asset is not allowed on general ledger account {0} |
| Error 101326 HTTP 400 | The asset number is not valid : {0} |
| Error 102486 HTTP 400 | Invalid value for dimension {0} |