API

Logistics APIs

POST logistics/stock-takings/{stockTakingId}/goods-reception-counts/{goodsReceptionCountId}/stock-location-counts

Adds a stock location count to the goods reception count

HTTP method POST
URI https://api.rambase.net/logistics/stock-takings/{stockTakingId}/goods-reception-counts/{goodsReceptionCountId}/stock-location-counts
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {stockTakingId} Stock taking identifier
Integer, minimum 100000
- URI parameter {goodsReceptionCountId} Goods reception count identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 2201, 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.

Format:
1
<StockLocationCount
StockLocationCount

This field is optional.

>
2
     <CountedStockQuantity
CountedStockQuantity

The counted/actual quantity found when counting the goods reception item for the stock location

This field is optional.

>{Decimal}</CountedStockQuantity>
3
     <StockLocation
StockLocation

This field is optional.

>
4
          <StockLocationId
StockLocationId

Stock location identifier

This field is optional.

>{Integer}</StockLocationId>
5
     </StockLocation>
6
</StockLocationCount>
1
{
2
     "stockLocationCount
StockLocationCount

This field is optional.

": {
3
          "countedStockQuantity
CountedStockQuantity

The counted/actual quantity found when counting the goods reception item for the stock location

This field is optional.

": "{Decimal}",
4
          "stockLocation
StockLocation

This field is optional.

": {
5
               "stockLocationId
StockLocationId

Stock location identifier

This field is optional.

": "{Integer}"
6
          }
7
     }
8
}

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.

Format:
1
1

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 103470 HTTP 404 Owner document of the cost not found
Error 103472 HTTP 400 Owner document has already cost set
Error 100563 HTTP 400 Currency {0} is not supported by the system
Error 101069 HTTP 404 Stock assignment link - document not found
Error 105186 HTTP 400 Postings are not allowed on control accounts.
Error 101490 HTTP 400 Illegal Account {0}: This account has been blocked for {1}-documents
Error 101491 HTTP 400 Illegal Account {0}: Check the account's FromPeriod and ToPeriod
Error 101517 HTTP 400 Illegal Account {0}: This account require ICTDB.
Error 102482 HTTP 400 Department is required for general ledger account {0}
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}