Operation: GetItemDetails

The operation GetItemDetails is used to query the details of an article, identified by its article number (SellersItemIdentification).

The request is an element comprising vco:GetItemDetailsRequest, an extension of the type vct:RequestType by the mandatory element cac:SellersItemIdentification and the optional element cbc:Quantity.

Rule: Serialization of GetItemDetailsRequest

In addition to the parameters of RequestType, the following parameters are used:

  • SellersItemIdentification

  • Quantity

  • quantityUnitCode

Serving as the value of the first parameter is the content of the ID element of the element of the same name, serving as the value of the second parameter is the content of the quantity element, and serving as the value of the third parameter is the value of the QuantityUnitCode attribute of the quantity element.

The response is an element vco:GetItemDetailsResponse which extends the type vct:ResponseType with the optional elements vco:Item (of type cac:ItemType), vco:Availability and vco:RequestReplacement.

Rule: GetItemDetails

A Veloconnect-compliant server must implement the GetItemDetails operation, and responds to a GetItemDetailsRequest as follows:

  1. A check is performed as to whether SellersItemIdentification is a valid item identifier. If not, the information is used to generate, if possible, a RequestReplacement element as per Rule: RequestReplacement, and Point 4 is proceeded with. Otherwise, an ItemUnknown element is created from the submitted SellersItemIdentification, and Point 4 is proceeded with.

  2. The identified item's master data are determined from the merchandise management system and stored in an Item element.

  3. The item's availability should be determined from the data present in the merchandise management system, and stored in the Availability element as per Rule: Availability. If the server does not provide this information, it must be specified in the Veloconnect profile.

  4. The determined information is to be returned with ResponseCode 200.

Related pages