API

Procurement APIs

GET procurement/requirements/{purchaseRequirementId}

Purchase requirement details for provided identifier

HTTP method GET
URI https://api.rambase.net/procurement/requirements/{purchaseRequirementId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {purchaseRequirementId} Purchase requirement identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 3365, version 8

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
1

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.

$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$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
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$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.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select 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.

Format:
1
<PurchaseRequirement>
2
     <PurchaseRequirementId
PurchaseRequirementId

Purchase requirement identifier

>
{Integer}</PurchaseRequirementId>
3
     <Status
Status

Status of purchase requirement

Possible domain values can be found here

>
{Integer}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
5
     <RequestedDeliveryDate
RequestedDeliveryDate

The delivery date as requested by the customer.

>
{Date}</RequestedDeliveryDate>
6
     <DemandForecastedQuantity
DemandForecastedQuantity

The total quantity from the demand forecast. This might include sales forecasts, sales backlog, minimum reorder point quantity, quantity expanded from BOM etc.

>
{Decimal}</DemandForecastedQuantity>
7
     <AvailableQuantity
AvailableQuantity

Total quantity available to be subtracted from the gross quantity. This is the sum of all goods receptions, purchase orders and purchase order responses ready to be consumed at requested delivery date.

>
{Decimal}</AvailableQuantity>
8
     <GrossQuantity
GrossQuantity

Gross quantity is initially the same as the sales forecasted quantity but might have changed during the production requirement planning. The gross quantity is the final required quantity for given product at requested delivery date.

>
{Decimal}</GrossQuantity>
9
     <SubtractedQuantity
SubtractedQuantity

Quantity of stock, purchase orders and purchase order responses subtracted from the gross quantity

>
{Decimal}</SubtractedQuantity>
10
     <NetQuantity
NetQuantity

Net purchase requirement. This is the quantity needed to be ordered for this product at this requested delivery date. The net quantity is calculated by subtracting stock, purchase orders and purchase order responses from the gross quantity.

>
{Decimal}</NetQuantity>
11
     <Product>
12
          <ProductId
ProductId

Product identifier

>
{Integer}</ProductId>
13
          <Name
Name

Name of the product

>
{String}</Name>
14
          <Type
Type

Type of product

Possible domain values can be found here

>
{String}</Type>
15
          <Description
Description

Description of the product

>
{String}</Description>
16
          <ProductLink
ProductLink

Product reference

>
{String}</ProductLink>
17
     </Product>
18
     <SOPProcess>
19
          <SOPProcessId
SOPProcessId

S&OP (sales and operation planning) process identifier

>
{Integer}</SOPProcessId>
20
          <SOPProcessLink
SOPProcessLink

S&OP (salse and operation planning) process reference

>
{String}</SOPProcessLink>
21
     </SOPProcess>
22
</PurchaseRequirement>
1
{
2
     "purchaseRequirement": {
3
          "purchaseRequirementId
PurchaseRequirementId

Purchase requirement identifier

":
"{Integer}",
4
          "status
Status

Status of purchase requirement

Possible domain values can be found here

":
"{Integer}",
5
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
6
          "requestedDeliveryDate
RequestedDeliveryDate

The delivery date as requested by the customer.

":
"{Date}",
7
          "demandForecastedQuantity
DemandForecastedQuantity

The total quantity from the demand forecast. This might include sales forecasts, sales backlog, minimum reorder point quantity, quantity expanded from BOM etc.

":
"{Decimal}",
8
          "availableQuantity
AvailableQuantity

Total quantity available to be subtracted from the gross quantity. This is the sum of all goods receptions, purchase orders and purchase order responses ready to be consumed at requested delivery date.

":
"{Decimal}",
9
          "grossQuantity
GrossQuantity

Gross quantity is initially the same as the sales forecasted quantity but might have changed during the production requirement planning. The gross quantity is the final required quantity for given product at requested delivery date.

":
"{Decimal}",
10
          "subtractedQuantity
SubtractedQuantity

Quantity of stock, purchase orders and purchase order responses subtracted from the gross quantity

":
"{Decimal}",
11
          "netQuantity
NetQuantity

Net purchase requirement. This is the quantity needed to be ordered for this product at this requested delivery date. The net quantity is calculated by subtracting stock, purchase orders and purchase order responses from the gross quantity.

":
"{Decimal}",
12
          "product": {
13
               "productId
ProductId

Product identifier

":
"{Integer}",
14
               "name
Name

Name of the product

":
"{String}",
15
               "type
Type

Type of product

Possible domain values can be found here

":
"{String}",
16
               "description
Description

Description of the product

":
"{String}",
17
               "productLink
ProductLink

Product reference

":
"{String}"
18
          },
19
          "sOPProcess": {
20
               "sOPProcessId
SOPProcessId

S&OP (sales and operation planning) process identifier

":
"{Integer}",
21
               "sOPProcessLink
SOPProcessLink

S&OP (salse and operation planning) process reference

":
"{String}"
22
          }
23
     }
24
}

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