API

Sales APIs

POST sales/order-requests

Creates a new sales order request

HTTP method POST
URI https://api.rambase.net/sales/order-requests
Supported formats Xml, Html, Json (ex. $format=json)
Custom fields Custom fields supported
Successful HTTP status code 201
API resource identifier 1909, version 7

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
<SalesOrderRequest>
2
     <CustomersReference
CustomersReference

Customers reference. Typically a person.

This field is optional.

>
{String}</CustomersReference>
3
     <CustomersReferenceNumber
CustomersReferenceNumber

Customers reference number. E.g. the internal sales order id the customer use in their own system.

This field is optional.

>
{String}</CustomersReferenceNumber>
4
     <VolumePriceAgreement
VolumePriceAgreement

Special price agreement related to the quantity beeing ordered.

Applicable domain values can be found here

This field is optional.

>
{String}</VolumePriceAgreement>
5
     <ExchangeRateFluctuationAgreement
ExchangeRateFluctuationAgreement

When a sales order is issued, RamBase stores the current exchange rate and the currency the product normally is purchased in. The exchange rate might have changed when the invoice is issued. The exchange rate fluctuation agreement specifies how to handle these differences. The agreement has the format AAA/BBB, where AAA is a percentage of the total invoice, and BBB is the exchange rate fluctuation percentage. E.g. 100/3.0 means that if the rate of exchange on the date a sales order is forwarded to an invoice has changed more than +/- 3% from the rate of exchange, 100% of the invoice amount will be adjusted.

Applicable domain values can be found here

This field is optional.

>
{String}</ExchangeRateFluctuationAgreement>
6
     <Currency
Currency

Three character code following the ISO 4217 standard

Applicable domain values can be found here

Input must match the following regular expression pattern: ^[A-Z]{3}$

This field is optional.

>
{String}</Currency>
7
     <Note
Note

Additional information regarding the object (free text). This note might be visible to customers/suppliers.

This field is optional.

>
{String}</Note>
8
     <Location
Location

This field is optional.

>
9
          <LocationId
LocationId

Location identifier

Minimum value: 10000

This field is optional.

>
{Integer}</LocationId>
10
     </Location>
11
     <Customer>
12
          <CustomerId
CustomerId

Required/mandatory field

Customer identifier

Minimum value: 10000

>
{Integer}</CustomerId>
13
     </Customer>
14
     <ShippingAddress
ShippingAddress

This field is optional.

>
15
          <AddressId
AddressId

Address identifier

Minimum value: 1

This field is optional.

>
{Integer}</AddressId>
16
     </ShippingAddress>
17
     <Shipment
Shipment

This field is optional.

>
18
          <DeliveryTerms
DeliveryTerms

Delivery terms when shipping the goods. The delivery terms is based on the Incoterms rules from ICC (International Chamber of Commerce). The delivery terms is by default retrieved from the customer.

Applicable domain values can be found here

This field is optional.

>
{String}</DeliveryTerms>
19
          <DeliveryTermPlace
DeliveryTermPlace

Named place related to delivery terms (Incoterms)

This field is optional.

>
{String}</DeliveryTermPlace>
20
          <ShippingService
ShippingService

This field is optional.

>
21
               <ShippingServiceId
ShippingServiceId

Shipping service identifier

Minimum value: 100000

This field is optional.

>
{Integer}</ShippingServiceId>
22
          </ShippingService>
23
     </Shipment>
24
     <Payment
Payment

This field is optional.

>
25
          <PaymentTerms
PaymentTerms

Terms of payment. Defaut value is retrieved from the customer. The due date of the sales order and sales invoice is calculated based on this field.

Applicable domain values can be found here

This field is optional.

>
{String}</PaymentTerms>
26
          <PaymentMethod
PaymentMethod

Method of payment. Default value is retrieved from the customer.

Applicable domain values can be found here

This field is optional.

>
{String}</PaymentMethod>
27
     </Payment>
28
     <VATDetails
VATDetails

This field is optional.

>
29
          <VATHandling
VATHandling

Specifies how value added tax (VAT) should be calculated. Either always include VAT, always exclude VAT or use standard/default VAT rules.

Applicable domain values can be found here

This field is optional.

>
{String}</VATHandling>
30
     </VATDetails>
31
</SalesOrderRequest>
1
{
2
     "salesOrderRequest": {
3
          "customersReference
CustomersReference

Customers reference. Typically a person.

This field is optional.

":
"{String}",
4
          "customersReferenceNumber
CustomersReferenceNumber

Customers reference number. E.g. the internal sales order id the customer use in their own system.

This field is optional.

":
"{String}",
5
          "volumePriceAgreement
VolumePriceAgreement

Special price agreement related to the quantity beeing ordered.

Applicable domain values can be found here

This field is optional.

":
"{String}",
6
          "exchangeRateFluctuationAgreement
ExchangeRateFluctuationAgreement

When a sales order is issued, RamBase stores the current exchange rate and the currency the product normally is purchased in. The exchange rate might have changed when the invoice is issued. The exchange rate fluctuation agreement specifies how to handle these differences. The agreement has the format AAA/BBB, where AAA is a percentage of the total invoice, and BBB is the exchange rate fluctuation percentage. E.g. 100/3.0 means that if the rate of exchange on the date a sales order is forwarded to an invoice has changed more than +/- 3% from the rate of exchange, 100% of the invoice amount will be adjusted.

Applicable domain values can be found here

This field is optional.

":
"{String}",
7
          "currency
Currency

Three character code following the ISO 4217 standard

Applicable domain values can be found here

Input must match the following regular expression pattern: ^[A-Z]{3}$

This field is optional.

":
"{String}",
8
          "note
Note

Additional information regarding the object (free text). This note might be visible to customers/suppliers.

This field is optional.

":
"{String}",
9
          "location
Location

This field is optional.

":
{
10
               "locationId
LocationId

Location identifier

Minimum value: 10000

This field is optional.

":
"{Integer}"
11
          },
12
          "customer": {
13
               "customerId
CustomerId

Required/mandatory field

Customer identifier

Minimum value: 10000

":
"{Integer}"
14
          },
15
          "shippingAddress
ShippingAddress

This field is optional.

":
{
16
               "addressId
AddressId

Address identifier

Minimum value: 1

This field is optional.

":
"{Integer}"
17
          },
18
          "shipment
Shipment

This field is optional.

":
{
19
               "deliveryTerms
DeliveryTerms

Delivery terms when shipping the goods. The delivery terms is based on the Incoterms rules from ICC (International Chamber of Commerce). The delivery terms is by default retrieved from the customer.

Applicable domain values can be found here

This field is optional.

":
"{String}",
20
               "deliveryTermPlace
DeliveryTermPlace

Named place related to delivery terms (Incoterms)

This field is optional.

":
"{String}",
21
               "shippingService
ShippingService

This field is optional.

":
{
22
                    "shippingServiceId
ShippingServiceId

Shipping service identifier

Minimum value: 100000

This field is optional.

":
"{Integer}"
23
               }
24
          },
25
          "payment
Payment

This field is optional.

":
{
26
               "paymentTerms
PaymentTerms

Terms of payment. Defaut value is retrieved from the customer. The due date of the sales order and sales invoice is calculated based on this field.

Applicable domain values can be found here

This field is optional.

":
"{String}",
27
               "paymentMethod
PaymentMethod

Method of payment. Default value is retrieved from the customer.

Applicable domain values can be found here

This field is optional.

":
"{String}"
28
          },
29
          "vATDetails
VATDetails

This field is optional.

":
{
30
               "vATHandling
VATHandling

Specifies how value added tax (VAT) should be calculated. Either always include VAT, always exclude VAT or use standard/default VAT rules.

Applicable domain values can be found here

This field is optional.

":
"{String}"
31
          }
32
     }
33
}

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.
$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]
$showCustomFields Boolean, optional Set to "true" to include custom fields. Default value is false.

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
<SalesOrderRequest>
2
     <SalesOrderRequestId
SalesOrderRequestId

Sales order request identifier

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

Status of sales order request

Possible domain values can be found here

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

Date and time of creation

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

Date of registration

>
{Date}</RegistrationDate>
6
     <SellersReferenceNumber
SellersReferenceNumber

Sellers reference number.

>
{String}</SellersReferenceNumber>
7
     <CustomersReference
CustomersReference

Customers reference. Typically a person.

>
{String}</CustomersReference>
8
     <CustomersReferenceNumber
CustomersReferenceNumber

Customers reference number. E.g. the internal sales order id the customer use in their own system.

>
{String}</CustomersReferenceNumber>
9
     <VolumePriceAgreement
VolumePriceAgreement

Special price agreement related to the quantity beeing ordered.

Possible domain values can be found here

>
{String}</VolumePriceAgreement>
10
     <ExchangeRateFluctuationAgreement
ExchangeRateFluctuationAgreement

When a sales order is issued, RamBase stores the current exchange rate and the currency the product normally is purchased in. The exchange rate might have changed when the invoice is issued. The exchange rate fluctuation agreement specifies how to handle these differences. The agreement has the format AAA/BBB, where AAA is a percentage of the total invoice, and BBB is the exchange rate fluctuation percentage. E.g. 100/3.0 means that if the rate of exchange on the date a sales order is forwarded to an invoice has changed more than +/- 3% from the rate of exchange, 100% of the invoice amount will be adjusted.

Possible domain values can be found here

>
{String}</ExchangeRateFluctuationAgreement>
11
     <NetWeight
NetWeight

The net weight of object (excluding packing meterial) in kilograms

>
{Decimal}</NetWeight>
12
     <GrossMargin
GrossMargin

Gross margin of sale, calculated as an average of gross margin of all items at the time items are created and when the document is registered. Will not be recalculated if gross margin in items change afterwards

>
{Decimal}</GrossMargin>
13
     <Currency
Currency

Three character code following the ISO 4217 standard

Possible domain values can be found here

>
{String}</Currency>
14
     <HasAttachmentsToForward
HasAttachmentsToForward

Has attachements that will be included when forwarded to other transaction documents.

>
{Boolean}</HasAttachmentsToForward>
15
     <Note
Note

Additional information regarding the object (free text). This note might be visible to customers/suppliers.

>
{String}</Note>
16
     <ShippingAddressAttention
ShippingAddressAttention

Attention of the shipping address. When changing shipping address, the ShippingAddressAttention will be overridden by the attention of the new shipping address.

>
{String}</ShippingAddressAttention>
17
     <ShippingAddressPhone
ShippingAddressPhone

Phone number of the shipping address. When changing shipping address, the ShippingAddressPhone will be overridden by the phone number of the new shipping address.

>
{String}</ShippingAddressPhone>
18
     <ShippingAddressEmail
ShippingAddressEmail

Email address of the shipping address. When changing shipping address, the ShippingAddressEmail will be overridden by the email of the new shipping address.

>
{String}</ShippingAddressEmail>
19
     <InvoiceAddressAttention
InvoiceAddressAttention

Attention of the invoice address. When changing invoice address, the InvoiceAddressAttention will be overridden by the attention of the new invoice address.

>
{String}</InvoiceAddressAttention>
20
     <Location>
21
          <ShortName
ShortName

Unique abbreviation/short name of the location

>
{String}</ShortName>
22
     </Location>
23
     <Assignee
Assignee

The user who has been assigned to work with this object.

>
24
          <UserId
UserId

User identifier

>
{Integer}</UserId>
25
          <Name
Name

Name of the user

>
{String}</Name>
26
          <FirstName
FirstName

First name of the user

>
{String}</FirstName>
27
          <UserLink
UserLink

User reference

>
{String}</UserLink>
28
     </Assignee>
29
     <Customer>
30
          <CustomerId
CustomerId

Customer identifier

>
{Integer}</CustomerId>
31
          <Name
Name

Name of customer (name of company or surname/familyname/lastname of a person)

>
{String}</Name>
32
          <Firstname
Firstname

Secondary name of a company or firstname of a person

>
{String}</Firstname>
33
          <Sales>
34
               <SalesDistrict
SalesDistrict

A geographic district for which an individual salesperson or sales team holds responsibility

Possible domain values can be found here

>
{String}</SalesDistrict>
35
               <MarketSegment
MarketSegment

Market segment of the customer

Possible domain values can be found here

>
36
                    <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
37
                    <LastName
LastName

Last name of employee

>
{String}</LastName>
38
                    <FirstName
FirstName

First name of employee

>
{String}</FirstName>
39
                    <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
40
                    <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
41
                    <LastName
LastName

Last name of employee

>
{String}</LastName>
42
                    <FirstName
FirstName

First name of employee

>
{String}</FirstName>
43
                    <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
44
               </MarketSegment>
45
          </Sales>
46
          <CustomerLegalEntity>
47
               <CustomerLegalEntityId
CustomerLegalEntityId

Customer legal entity identifier

>
{Integer}</CustomerLegalEntityId>
48
               <CustomerLegalEntityLink
CustomerLegalEntityLink

Reference to customer legal entity

>
{String}</CustomerLegalEntityLink>
49
          </CustomerLegalEntity>
50
          <CustomerLink
CustomerLink

Customer reference

>
{String}</CustomerLink>
51
     </Customer>
52
     <ShippingAddress>
53
          <AddressId
AddressId

Address identifier

>
{Integer}</AddressId>
54
          <Name
Name

Name of receiver (Name of company or last name of a person). Note that default invoice address must have the same name as the customer.

>
{String}</Name>
55
          <Firstname
Firstname

Firstname if the receiver is a person. Note that default invoice address must have the same firstname as the customer.

>
{String}</Firstname>
56
          <AddressLine1
AddressLine1

First address line

>
{String}</AddressLine1>
57
          <AddressLine2
AddressLine2

Second address line

>
{String}</AddressLine2>
58
          <PostalCode
PostalCode

Postalcode/Postcode/ZIP

>
{String}</PostalCode>
59
          <City
City

City/town/village

>
{String}</City>
60
          <Region
Region

Region/province/state

>
{String}</Region>
61
          <CountryCode
CountryCode

Two-character code (ISO 3166) identifying the country.

>
{String}</CountryCode>
62
          <Country
Country

English name of country.

>
{String}</Country>
63
          <ExternalReference
ExternalReference

External address identifier. Normally defined by the customer.

>
{String}</ExternalReference>
64
     </ShippingAddress>
65
     <InvoiceAddress>
66
          <Name
Name

Name of receiver (Name of company or last name of a person). Note that default invoice address must have the same name as the customer.

>
{String}</Name>
67
          <Firstname
Firstname

Firstname if the receiver is a person. Note that default invoice address must have the same firstname as the customer.

>
{String}</Firstname>
68
          <AddressLine1
AddressLine1

First address line

>
{String}</AddressLine1>
69
          <AddressLine2
AddressLine2

Second address line

>
{String}</AddressLine2>
70
          <PostalCode
PostalCode

Postalcode/Postcode/ZIP

>
{String}</PostalCode>
71
          <City
City

City/town/village

>
{String}</City>
72
          <Region
Region

Region/province/state

>
{String}</Region>
73
          <CountryCode
CountryCode

Two-character code (ISO 3166) identifying the country.

>
{String}</CountryCode>
74
          <Country
Country

English name of country.

>
{String}</Country>
75
     </InvoiceAddress>
76
     <Totals>
77
          <Currency
Currency

Three character code following the ISO 4217 standard

>
{String}</Currency>
78
          <FreightAmount
FreightAmount

Freight amount in transaction document's currency

>
{Decimal}</FreightAmount>
79
          <FeeAmount
FeeAmount

Fee amount in transaction document's currency

>
{Decimal}</FeeAmount>
80
          <SubTotalAmount
SubTotalAmount

Total amount of the object in object currency, excluding VAT.

>
{Decimal}</SubTotalAmount>
81
          <VATAmount
VATAmount

Total value added tax in object currency.

>
{Decimal}</VATAmount>
82
          <TotalAmount
TotalAmount

The total amount in object currency, including VAT

>
{Decimal}</TotalAmount>
83
          <Currency
Currency

Currency used in conversion. Default is company accounting currency. Three character code following the ISO 4217 standard.

>
{String}</Currency>
84
          <ExchangeRate
ExchangeRate

The exchange rate used in convertion

>
{Decimal}</ExchangeRate>
85
          <FreightAmount
FreightAmount

Freight amount in company currency.

>
{Decimal}</FreightAmount>
86
          <FeeAmount
FeeAmount

Fee amount in company currency

>
{Decimal}</FeeAmount>
87
          <SubTotalAmount
SubTotalAmount

Total amount of the object in company currency, excluding VAT.

>
{Decimal}</SubTotalAmount>
88
          <VATAmount
VATAmount

Value added tax amount in company currency.

>
{Decimal}</VATAmount>
89
          <TotalAmount
TotalAmount

The total amount in company currency, including VAT.

>
{Decimal}</TotalAmount>
90
     </Totals>
91
     <Shipment>
92
          <DeliveryTerms
DeliveryTerms

Delivery terms when shipping the goods. The delivery terms is based on the Incoterms rules from ICC (International Chamber of Commerce). The delivery terms is by default retrieved from the customer.

Possible domain values can be found here

>
{String}</DeliveryTerms>
93
          <DeliveryTermPlace
DeliveryTermPlace

Named place related to delivery terms (Incoterms)

>
{String}</DeliveryTermPlace>
94
          <OnlyShipEntireSalesOrder
OnlyShipEntireSalesOrder

True if all items of a sales order should be shipped together. The items of a sales order should never be split into several shipments. If sales order is forwarded to shipping advice by bulk handling, this will be controlled by RamBase. Manually forward requires that the users controls this themselves.

>
{Boolean}</OnlyShipEntireSalesOrder>
95
          <OnlyShipEntireSalesOrderItems
OnlyShipEntireSalesOrderItems

True if the total quantity of a sales order item always should be shipped together. The quantity should never be split into several shipments. If sales order is forwarded to shipping advice by bulk handling, this will be controlled by RamBase. Manually forward requires that the users controls this themselves.

>
{Boolean}</OnlyShipEntireSalesOrderItems>
96
          <AvoidMultipleShipmentsOnSameDate
AvoidMultipleShipmentsOnSameDate

True if all items of a sales order with the same sheduled delivery date should be shipped together. If sales order is forwarded to shipping advice by bulk handling, this will be controlled by RamBase. Manually forward requires that the users controls this themselves.

>
{Boolean}</AvoidMultipleShipmentsOnSameDate>
97
          <ShipBasedOnConfirmedDeliveryDate
ShipBasedOnConfirmedDeliveryDate

If true, will sheduled shipping date on each item be calculated based on confirmed date rather than requested date.

>
{Boolean}</ShipBasedOnConfirmedDeliveryDate>
98
          <FreightForEachShipment
FreightForEachShipment

If unchecked there will only be calculated freight on one shipping advice if the particular sales order has serveral shipments.

>
{Boolean}</FreightForEachShipment>
99
          <ShippingDay
ShippingDay

Specifies when the goods should be shipped. This is used to calculate the scheduled shipping date for each item.

Possible domain values can be found here

>
{String}</ShippingDay>
100
          <ConsolidateShippingAdvices
ConsolidateShippingAdvices

If true, sales orders will be consolidated when creating shipping advices via the "Prepare for picking" process the . If false, each sales order will result in seperate shipping advice. The field to use when consolidating is specified in the ShippingAdviceConsolidationField.

>
{Boolean}</ConsolidateShippingAdvices>
101
          <ShippingAdviceConsolidationField
ShippingAdviceConsolidationField

Field to use when consolidating sales order items into shipping advices in the "Prepare for picking" process.

Possible domain values can be found here

>
{String}</ShippingAdviceConsolidationField>
102
          <ShippingAdviceItemSortBy
ShippingAdviceItemSortBy

Items in consolidated shipping advices will be sorted by this fields when they are created in the 'Prepare for picking' process

Possible domain values can be found here

>
{String}</ShippingAdviceItemSortBy>
103
          <SpecialHandling
SpecialHandling

Special handling to use for this shipment.

>
104
               <SpecialHandlingId
SpecialHandlingId

Special handling identifier

>
{Integer}</SpecialHandlingId>
105
               <SpecialHandlingLink
SpecialHandlingLink

Special handling code reference

>
{String}</SpecialHandlingLink>
106
          </SpecialHandling>
107
          <ShippingService>
108
               <ShippingServiceId
ShippingServiceId

Shipping service identifier

>
{Integer}</ShippingServiceId>
109
               <Name
Name

Name of shipping service

>
{String}</Name>
110
               <Carrier>
111
                    <CarrierId
CarrierId

Carrier identifier

>
{Integer}</CarrierId>
112
                    <CarrierLink
CarrierLink

Carrier reference

>
{String}</CarrierLink>
113
               </Carrier>
114
               <ShippingServiceLink
ShippingServiceLink

Shipping service reference

>
{String}</ShippingServiceLink>
115
          </ShippingService>
116
     </Shipment>
117
     <Invoicing>
118
          <SalesInvoiceConsolidation
SalesInvoiceConsolidation

Specifies whether or how often shipping advices that origins from this sales order will be consolidated when creating sales invoices.

Possible domain values can be found here

>
{String}</SalesInvoiceConsolidation>
119
          <SalesInvoiceConsolidationField
SalesInvoiceConsolidationField

Field name to group by when consolidating shipping advice items into sales invoices.

Possible domain values can be found here

>
{String}</SalesInvoiceConsolidationField>
120
          <SalesInvoiceItemSortBy
SalesInvoiceItemSortBy

Field name to sort by when creating sales invoice items.

Possible domain values can be found here

>
{String}</SalesInvoiceItemSortBy>
121
     </Invoicing>
122
     <Payment>
123
          <PaymentTerms
PaymentTerms

Terms of payment. Defaut value is retrieved from the customer. The due date of the sales order and sales invoice is calculated based on this field.

Possible domain values can be found here

>
{String}</PaymentTerms>
124
          <PaymentMethod
PaymentMethod

Method of payment. Default value is retrieved from the customer.

Possible domain values can be found here

>
{String}</PaymentMethod>
125
     </Payment>
126
     <VATDetails>
127
          <VATType
VATType

Type of value added tax

>
{String}</VATType>
128
          <VATHandling
VATHandling

Specifies how value added tax (VAT) should be calculated. Either always include VAT, always exclude VAT or use standard/default VAT rules.

Possible domain values can be found here

>
{String}</VATHandling>
129
          <DefaultVATPercent
DefaultVATPercent

Value added tax percent.

>
{Decimal}</DefaultVATPercent>
130
          <NotificationId
NotificationId

Notification identifier

>
{Integer}</NotificationId>
131
          <Status
Status

Status of the notification

Possible domain values can be found here

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

Date and time of creation

>
{Datetime}</CreatedAt>
133
          <Message
Message

The message from the notification definition, expanded with parameters.

>
{String}</Message>
134
          <TranslatedMessage
TranslatedMessage

The translated message from the notification definition, expanded with parameters.

>
{String}</TranslatedMessage>
135
          <NotificationType>
136
               <NotificationTypeId
NotificationTypeId

Notification type identifier

>
{String}</NotificationTypeId>
137
               <Category
Category

Category of notification type (warning, information etc)

Possible domain values can be found here

>
{String}</Category>
138
               <NotificationTypeLink
NotificationTypeLink

Notification type reference

>
{String}</NotificationTypeLink>
139
          </NotificationType>
140
          <NotificationLink
NotificationLink

Notification reference

>
{String}</NotificationLink>
141
     </VATDetails>
142
</SalesOrderRequest>
1
{
2
     "salesOrderRequest": {
3
          "salesOrderRequestId
SalesOrderRequestId

Sales order request identifier

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

Status of sales order request

Possible domain values can be found here

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

Date and time of creation

":
"{Datetime}",
6
          "registrationDate
RegistrationDate

Date of registration

":
"{Date}",
7
          "sellersReferenceNumber
SellersReferenceNumber

Sellers reference number.

":
"{String}",
8
          "customersReference
CustomersReference

Customers reference. Typically a person.

":
"{String}",
9
          "customersReferenceNumber
CustomersReferenceNumber

Customers reference number. E.g. the internal sales order id the customer use in their own system.

":
"{String}",
10
          "volumePriceAgreement
VolumePriceAgreement

Special price agreement related to the quantity beeing ordered.

Possible domain values can be found here

":
"{String}",
11
          "exchangeRateFluctuationAgreement
ExchangeRateFluctuationAgreement

When a sales order is issued, RamBase stores the current exchange rate and the currency the product normally is purchased in. The exchange rate might have changed when the invoice is issued. The exchange rate fluctuation agreement specifies how to handle these differences. The agreement has the format AAA/BBB, where AAA is a percentage of the total invoice, and BBB is the exchange rate fluctuation percentage. E.g. 100/3.0 means that if the rate of exchange on the date a sales order is forwarded to an invoice has changed more than +/- 3% from the rate of exchange, 100% of the invoice amount will be adjusted.

Possible domain values can be found here

":
"{String}",
12
          "netWeight
NetWeight

The net weight of object (excluding packing meterial) in kilograms

":
"{Decimal}",
13
          "grossMargin
GrossMargin

Gross margin of sale, calculated as an average of gross margin of all items at the time items are created and when the document is registered. Will not be recalculated if gross margin in items change afterwards

":
"{Decimal}",
14
          "currency
Currency

Three character code following the ISO 4217 standard

Possible domain values can be found here

":
"{String}",
15
          "hasAttachmentsToForward
HasAttachmentsToForward

Has attachements that will be included when forwarded to other transaction documents.

":
"{Boolean}",
16
          "note
Note

Additional information regarding the object (free text). This note might be visible to customers/suppliers.

":
"{String}",
17
          "shippingAddressAttention
ShippingAddressAttention

Attention of the shipping address. When changing shipping address, the ShippingAddressAttention will be overridden by the attention of the new shipping address.

":
"{String}",
18
          "shippingAddressPhone
ShippingAddressPhone

Phone number of the shipping address. When changing shipping address, the ShippingAddressPhone will be overridden by the phone number of the new shipping address.

":
"{String}",
19
          "shippingAddressEmail
ShippingAddressEmail

Email address of the shipping address. When changing shipping address, the ShippingAddressEmail will be overridden by the email of the new shipping address.

":
"{String}",
20
          "invoiceAddressAttention
InvoiceAddressAttention

Attention of the invoice address. When changing invoice address, the InvoiceAddressAttention will be overridden by the attention of the new invoice address.

":
"{String}",
21
          "location": {
22
               "shortName
ShortName

Unique abbreviation/short name of the location

":
"{String}"
23
          },
24
          "assignee
Assignee

The user who has been assigned to work with this object.

":
{
25
               "userId
UserId

User identifier

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

Name of the user

":
"{String}",
27
               "firstName
FirstName

First name of the user

":
"{String}",
28
               "userLink
UserLink

User reference

":
"{String}"
29
          },
30
          "customer": {
31
               "customerId
CustomerId

Customer identifier

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

Name of customer (name of company or surname/familyname/lastname of a person)

":
"{String}",
33
               "firstname
Firstname

Secondary name of a company or firstname of a person

":
"{String}",
34
               "sales": {
35
                    "salesDistrict
SalesDistrict

A geographic district for which an individual salesperson or sales team holds responsibility

Possible domain values can be found here

":
"{String}",
36
                    "marketSegment
MarketSegment

Market segment of the customer

Possible domain values can be found here

":
{
37
                         "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
38
                         "lastName
LastName

Last name of employee

":
"{String}",
39
                         "firstName
FirstName

First name of employee

":
"{String}",
40
                         "employeeLink
EmployeeLink

Employee reference

":
"{String}",
41
                         "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
42
                         "lastName
LastName

Last name of employee

":
"{String}",
43
                         "firstName
FirstName

First name of employee

":
"{String}",
44
                         "employeeLink
EmployeeLink

Employee reference

":
"{String}"
45
                    }
46
               },
47
               "customerLegalEntity": {
48
                    "customerLegalEntityId
CustomerLegalEntityId

Customer legal entity identifier

":
"{Integer}",
49
                    "customerLegalEntityLink
CustomerLegalEntityLink

Reference to customer legal entity

":
"{String}"
50
               },
51
               "customerLink
CustomerLink

Customer reference

":
"{String}"
52
          },
53
          "shippingAddress": {
54
               "addressId
AddressId

Address identifier

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

Name of receiver (Name of company or last name of a person). Note that default invoice address must have the same name as the customer.

":
"{String}",
56
               "firstname
Firstname

Firstname if the receiver is a person. Note that default invoice address must have the same firstname as the customer.

":
"{String}",
57
               "addressLine1
AddressLine1

First address line

":
"{String}",
58
               "addressLine2
AddressLine2

Second address line

":
"{String}",
59
               "postalCode
PostalCode

Postalcode/Postcode/ZIP

":
"{String}",
60
               "city
City

City/town/village

":
"{String}",
61
               "region
Region

Region/province/state

":
"{String}",
62
               "countryCode
CountryCode

Two-character code (ISO 3166) identifying the country.

":
"{String}",
63
               "country
Country

English name of country.

":
"{String}",
64
               "externalReference
ExternalReference

External address identifier. Normally defined by the customer.

":
"{String}"
65
          },
66
          "invoiceAddress": {
67
               "name
Name

Name of receiver (Name of company or last name of a person). Note that default invoice address must have the same name as the customer.

":
"{String}",
68
               "firstname
Firstname

Firstname if the receiver is a person. Note that default invoice address must have the same firstname as the customer.

":
"{String}",
69
               "addressLine1
AddressLine1

First address line

":
"{String}",
70
               "addressLine2
AddressLine2

Second address line

":
"{String}",
71
               "postalCode
PostalCode

Postalcode/Postcode/ZIP

":
"{String}",
72
               "city
City

City/town/village

":
"{String}",
73
               "region
Region

Region/province/state

":
"{String}",
74
               "countryCode
CountryCode

Two-character code (ISO 3166) identifying the country.

":
"{String}",
75
               "country
Country

English name of country.

":
"{String}"
76
          },
77
          "totals": {
78
               "currency
Currency

Three character code following the ISO 4217 standard

":
"{String}",
79
               "freightAmount
FreightAmount

Freight amount in transaction document's currency

":
"{Decimal}",
80
               "feeAmount
FeeAmount

Fee amount in transaction document's currency

":
"{Decimal}",
81
               "subTotalAmount
SubTotalAmount

Total amount of the object in object currency, excluding VAT.

":
"{Decimal}",
82
               "vATAmount
VATAmount

Total value added tax in object currency.

":
"{Decimal}",
83
               "totalAmount
TotalAmount

The total amount in object currency, including VAT

":
"{Decimal}",
84
               "currency
Currency

Currency used in conversion. Default is company accounting currency. Three character code following the ISO 4217 standard.

":
"{String}",
85
               "exchangeRate
ExchangeRate

The exchange rate used in convertion

":
"{Decimal}",
86
               "freightAmount
FreightAmount

Freight amount in company currency.

":
"{Decimal}",
87
               "feeAmount
FeeAmount

Fee amount in company currency

":
"{Decimal}",
88
               "subTotalAmount
SubTotalAmount

Total amount of the object in company currency, excluding VAT.

":
"{Decimal}",
89
               "vATAmount
VATAmount

Value added tax amount in company currency.

":
"{Decimal}",
90
               "totalAmount
TotalAmount

The total amount in company currency, including VAT.

":
"{Decimal}"
91
          },
92
          "shipment": {
93
               "deliveryTerms
DeliveryTerms

Delivery terms when shipping the goods. The delivery terms is based on the Incoterms rules from ICC (International Chamber of Commerce). The delivery terms is by default retrieved from the customer.

Possible domain values can be found here

":
"{String}",
94
               "deliveryTermPlace
DeliveryTermPlace

Named place related to delivery terms (Incoterms)

":
"{String}",
95
               "onlyShipEntireSalesOrder
OnlyShipEntireSalesOrder

True if all items of a sales order should be shipped together. The items of a sales order should never be split into several shipments. If sales order is forwarded to shipping advice by bulk handling, this will be controlled by RamBase. Manually forward requires that the users controls this themselves.

":
"{Boolean}",
96
               "onlyShipEntireSalesOrderItems
OnlyShipEntireSalesOrderItems

True if the total quantity of a sales order item always should be shipped together. The quantity should never be split into several shipments. If sales order is forwarded to shipping advice by bulk handling, this will be controlled by RamBase. Manually forward requires that the users controls this themselves.

":
"{Boolean}",
97
               "avoidMultipleShipmentsOnSameDate
AvoidMultipleShipmentsOnSameDate

True if all items of a sales order with the same sheduled delivery date should be shipped together. If sales order is forwarded to shipping advice by bulk handling, this will be controlled by RamBase. Manually forward requires that the users controls this themselves.

":
"{Boolean}",
98
               "shipBasedOnConfirmedDeliveryDate
ShipBasedOnConfirmedDeliveryDate

If true, will sheduled shipping date on each item be calculated based on confirmed date rather than requested date.

":
"{Boolean}",
99
               "freightForEachShipment
FreightForEachShipment

If unchecked there will only be calculated freight on one shipping advice if the particular sales order has serveral shipments.

":
"{Boolean}",
100
               "shippingDay
ShippingDay

Specifies when the goods should be shipped. This is used to calculate the scheduled shipping date for each item.

Possible domain values can be found here

":
"{String}",
101
               "consolidateShippingAdvices
ConsolidateShippingAdvices

If true, sales orders will be consolidated when creating shipping advices via the "Prepare for picking" process the . If false, each sales order will result in seperate shipping advice. The field to use when consolidating is specified in the ShippingAdviceConsolidationField.

":
"{Boolean}",
102
               "shippingAdviceConsolidationField
ShippingAdviceConsolidationField

Field to use when consolidating sales order items into shipping advices in the "Prepare for picking" process.

Possible domain values can be found here

":
"{String}",
103
               "shippingAdviceItemSortBy
ShippingAdviceItemSortBy

Items in consolidated shipping advices will be sorted by this fields when they are created in the 'Prepare for picking' process

Possible domain values can be found here

":
"{String}",
104
               "specialHandling
SpecialHandling

Special handling to use for this shipment.

":
{
105
                    "specialHandlingId
SpecialHandlingId

Special handling identifier

":
"{Integer}",
106
                    "specialHandlingLink
SpecialHandlingLink

Special handling code reference

":
"{String}"
107
               },
108
               "shippingService": {
109
                    "shippingServiceId
ShippingServiceId

Shipping service identifier

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

Name of shipping service

":
"{String}",
111
                    "carrier": {
112
                         "carrierId
CarrierId

Carrier identifier

":
"{Integer}",
113
                         "carrierLink
CarrierLink

Carrier reference

":
"{String}"
114
                    },
115
                    "shippingServiceLink
ShippingServiceLink

Shipping service reference

":
"{String}"
116
               }
117
          },
118
          "invoicing": {
119
               "salesInvoiceConsolidation
SalesInvoiceConsolidation

Specifies whether or how often shipping advices that origins from this sales order will be consolidated when creating sales invoices.

Possible domain values can be found here

":
"{String}",
120
               "salesInvoiceConsolidationField
SalesInvoiceConsolidationField

Field name to group by when consolidating shipping advice items into sales invoices.

Possible domain values can be found here

":
"{String}",
121
               "salesInvoiceItemSortBy
SalesInvoiceItemSortBy

Field name to sort by when creating sales invoice items.

Possible domain values can be found here

":
"{String}"
122
          },
123
          "payment": {
124
               "paymentTerms
PaymentTerms

Terms of payment. Defaut value is retrieved from the customer. The due date of the sales order and sales invoice is calculated based on this field.

Possible domain values can be found here

":
"{String}",
125
               "paymentMethod
PaymentMethod

Method of payment. Default value is retrieved from the customer.

Possible domain values can be found here

":
"{String}"
126
          },
127
          "vATDetails": {
128
               "vATType
VATType

Type of value added tax

":
"{String}",
129
               "vATHandling
VATHandling

Specifies how value added tax (VAT) should be calculated. Either always include VAT, always exclude VAT or use standard/default VAT rules.

Possible domain values can be found here

":
"{String}",
130
               "defaultVATPercent
DefaultVATPercent

Value added tax percent.

":
"{Decimal}",
131
               "notificationId
NotificationId

Notification identifier

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

Status of the notification

Possible domain values can be found here

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

Date and time of creation

":
"{Datetime}",
134
               "message
Message

The message from the notification definition, expanded with parameters.

":
"{String}",
135
               "translatedMessage
TranslatedMessage

The translated message from the notification definition, expanded with parameters.

":
"{String}",
136
               "notificationType": {
137
                    "notificationTypeId
NotificationTypeId

Notification type identifier

":
"{String}",
138
                    "category
Category

Category of notification type (warning, information etc)

Possible domain values can be found here

":
"{String}",
139
                    "notificationTypeLink
NotificationTypeLink

Notification type reference

":
"{String}"
140
               },
141
               "notificationLink
NotificationLink

Notification reference

":
"{String}"
142
          }
143
     }
144
}

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 102447 HTTP 400 Missing both assignment id and item id parameters.
Error 102012 HTTP 400 Transcation Object ID is required
Error 100563 HTTP 400 Currency {0} is not supported by the system
Error 101488 HTTP 400 Illegal general ledger account : {0}
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}