|
CATALOGUE ITEM AUTHORISATION v. 2.1 |
|
|
Use of Catalogue Item
Authorisation for Store Openings and New Item Introductions |
|
|
The Catalogue Item
Authorisation Message supports both the store opening and new item introduction
scenarios by allowing the sending of either many trade items to a single business
location or one trade item to a multiple locations. In the message, these two
scenarios are implemented as a choice. In the case of a store opening, it is
recommended to use the “MultipleItemAuthorisation” construct. For the new item
scenario, it is recommended to use the “SingleItemAuthorisation construct (see
class diagram). Note: the structure by design does not support multiple items
to multiple business locations.
|
|
|
Use of Catalogue Item
Authorisation Response for Store Openings and New Item Introductions |
|
|
As a rule, the Catalogue Item Authorisation
Response should resemble the structure of the originating Catalogue Item
Authorisation. For example, if a Catalogue Item Authorisation was sent for one
trade item to multiple business locations, the response should only contain one
trade item. If a Catalogue Item Authorisation was sent for many trade items to a
single business location, the response should only contain one business
location. The Catalogue Item Authorisation Response supports both scenarios
through the AuthorisationResponse class.
|
|
|
Reference between Catalogue
Item Authorisation Response and the Catalogue Item Authorisation
|
|
|
During requirements gathering, it was
decided that Item Authorisations are performed for individual items and there
is no blanket acceptance or rejection of an entire Item Authorisation message.
Because of this decision, there is no reference to the message identification
of the originating Catalogue Item Authorisation in the Catalogue Item
Authorisation Response.
|
|
|
Back
to Message Description |
|
|
Code Lists |
|
|
Test Data |
|
|
|
|
|
|
|
