Sales APIs
Removes sales order from sales delivery project. Sales order will not be deleted.
HTTP method | DELETE |
URI | https://api.rambase.net/sales/delivery-projects/{salesDeliveryProjectId}/sales-orders/{salesOrderId} |
Supported formats | Xml, Html, Json (ex. $format=json) |
- URI parameter {salesDeliveryProjectId} |
Sales delivery project identifier
Integer, minimum 100000 |
- URI parameter {salesOrderId} |
Sales order identifier
Integer, minimum 100000 |
Successful HTTP status code | 202 |
API resource identifier | 2305, version 1 |
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.
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. |
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. Fields colored in grey is expandable 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 100027 HTTP 400 | Missing mandatory parameter {0} |
Error 100854 HTTP 400 | Cannot change production start after operation is started |
Error 101538 HTTP 400 | Date-field can not be blank |
Error 103797 HTTP 400 | Mandatory field department has no value, please select |
Error 104486 HTTP 400 | Unit production is only allowed for measurment units (UNI) of type QTY |
Error 100316 HTTP 400 | Quantity cannot exceed {0} on UNIT productions |
Error 104522 HTTP 400 | Location in goods reception must be equal to location in arriving waybill |
Error 101466 HTTP 400 | Cannot change the location short code because of the object's status |
Error 103023 HTTP 400 | You cannot changes location as purchase order is not prepared for direct/back to back shipment. |
Error 103024 HTTP 400 | You cannot change location in a purchase order which is set up for direct/back to back shipment. |
Error 103025 HTTP 400 | You cannot change location in a purchase order that is assigned to a sales order which is direct shipment/back to back sales order. |
Error 101556 HTTP 400 | You can not change currency when order items have been added |
Error 101562 HTTP 400 | This currency is not supported by the supplier |
Error 101689 HTTP 400 | You cannot change this purchase order to type 'REQUISITION' as it contains standard products (type not equal to X or V). |
Error 101690 HTTP 400 | You cannot change this purchase order to type 'REQUISITION' as it has assignments. |
Error 101470 HTTP 400 | Cannot change currency on an object that contains items |
Error 101464 HTTP 400 | Currency field can not be blank. |
Error 101469 HTTP 400 | The object is not open for edit. To change currency, the object must be in status 1. |
Error 100992 HTTP 400 | This customer does not buy in this currency |
Error 101541 HTTP 400 | Cannot change volume price agreement when the object has items |
Error 101588 HTTP 400 | Effective date must have a date that is earlier or equal to expiration date |
Error 101589 HTTP 400 | The expiration date must be later or equal to effective date |
Error 102521 HTTP 400 | The content of the CASE-field on one of this Orders items exists on another Order outside the project. |
Error 106111 HTTP 400 | Delivery project PRO/{1} have finance project PRJ/{0}. COA item {2} is already linked to finance project PRJ/{3}. |
Error 100276 HTTP 400 | Invalid email format |
Error 106993 HTTP 400 | It is not allowed to add fee to the internal sales order for material for project order. |
Error 106994 HTTP 400 | It is not allowed to add freight to a sales order for material for project order. |