Professional Documents
Culture Documents
Title: Catalogue
Document Summary
Document Item Current Value
Document Title Business Requirements Specification for Catalogue
Date Last Modified Date09
Current Document Issue Issue #2 of draft version
Status Draft for second review
Document Description Business requirement specification for product catalogue and complete
(one sentence summary) business process.
Contributors
Name Organization
Log of Changes
Issue No. Date of Change Changed By Summary of Change
TABLE OF CONTENTS
1. Preamble............................................................................................................................ 5
2. References.......................................................................................................................... 5
3. Objective............................................................................................................................ 5
3.1. Scope 6
3.2. Context Categories 7
3.3. Business Domain View 8
3.3.1.Catalogue Process within the BUY-SHIP-PAY Model 8
3.3.2.Catalogue Domain Use Case diagram 8
7. Business Transactions.....................................................................................................19
7.1.1.Request Catalogue Subscription business transaction 20
7.1.2.Request Catalogue business transaction22
7.1.3.Provide Catalogue business transaction 24
7.1.4.Request Catalogue Update business transaction 26
7.1.5.Provide Catalogue Update business transaction 28
9. Business Documents........................................................................................................30
9.1. Subscription Request (Business Document) 31
9.2. Catalogue Request (Business Document) 36
9.3. Application Response (Business Document) 41
1. Preamble
The current practice of exchanging business documents by means of telecommunications – usually
defined as e-Business – presents a major opportunity to improve the competitiveness of companies,
especially for Small and Medium Enterprises (SME).
The catalogue is an important document exchanged between trading partners, it marks the start of the
trading cycle.
Started as an initiative by CEN/ISSS Workshop eBES, the European Expert Group 1 (EEG1) – Supply
Chain & e-Procurement – developed the Cross Industry Catalogue in 2005/2006. The Cross Industry
Catalogue has been compiled by a working group with contributions from BME (German Association
Materials Management, Purchasing and Logistics), BLI at the University of Duisburg-Essen,
Fernuniversität Hagen, PIDX, OASIS/UBL, CRITT Informatique, SupplyChange, Healthlogistics,
Eurofer, CEN/ISSS WS E-Catalogue. Paradigma Unternehmensberatung Gmbh, EPDC, ISO TC184
SC4 and VWR, GS1, the Danish government and Swedish Local authorities and regions.
The document describe globally consistent catalogue information exchange processes for worldwide
supply chains and e-Procurement of commodities, using the UN/CEFACT Modelling Methodology
(UMM) approach and Unified Modelling Language to describe the business processes and business
documents involved.
The structure of this document is based on the structure of the UN/CEFACT Business Requirements
Specification (BRS) document reference CEFACT/ICG/005.
2. References
UN/CEFACT Modelling Methodology (CEFACT/TMG/N090R10, November 2001)
UN/CEFACT –ebXML Core Components Technical Specification version 2.01 – ISO 15000-5
UN/CEFACT Business Requirements Specification version 1.5 (CEFACT/ICG/005)
Unified Modelling Language (UML version 1.4)
Actors, Roles, Partners & Parties UN/CEFACT TBG14 BPA/N061 - 10 th Aug 2006
3. Objective
The objective of this specification is to describe the business processes, the business documents and
the information entities for the exchange of catalogue information, including price information, used by
industries for the supply chain.
The business process is the detailed description of the way trading partners intend to play their
respective roles, establish business relations and share responsibilities to interact efficiently with the
support of their respective information systems.
The collaborative business processes involved in the catalogue process are made up by five business
transactions.
Each business transaction is realised by an exchange of business information (documents and
messages). The sequence in which these transactions are used, represent particular scenarios and
are presented as activity diagrams in this document.
The information exchanged in the business documents/messages are presented in lists of business
entities and their attributes.
3.1. Scope
This section describes the extent and limits of the business processes within the supply chain being
described in this document. Each industry may specify, based on the BRS of the cross industry
catalogue processes, its industry specific use of the catalogue message and the business processes.
It also allows for industry specific functionality on details to describe a specific product.
Name/Value pairs in the catalogue documents allows the Catalogue Provider to add attributes to
further specify their products in the existing structure. If further elaboration is needed an industry
specific ontology can be made. Industry specific ontology is outside the scope of this BRS.
The catalogue processes are used to offer goods or services by the Supplier to potential Customers
and give basic information needed for ordering those goods or services. A catalogue will contain
information on the products being offered and may contain price information, terms of trade and other
commercial information.
The processes cover:
Exchange of multi language catalogues
Exchange of catalogue being a full catalogue or part of a catalogue in relation to updates
Exchange of multi Supplier catalogues or parts of multi Suppliers catalogues in relation to
updates
Customer specific catalogue items and prices, including contract prices
This document describes the processes involved in the exchange of catalogue data and how to
structure the information in electronic catalogues, so they can be sent to customers and potential
customers, in whole or part, and be the basis for the ordering of the goods or services defined in those
catalogues. Customers may ask for catalogue data ad hoc, or they may subscribe to the catalogue
process and receive all or parts of the catalogue data.
1
See Actors, Roles, Partners & Parties UN/CEFACT TBG14 BPA/N061 - 10th Aug 2006
«ProcessArea»
Catal ogue
+ Catalogue
+ Catalogue
+ Catalogue
(from EstablishBusinessAgreement)
uc Catalogue
SubscibeToCatalogue
«participates» RequestCatalogue
«participates»
«participates» «participates»
«participates» «participates»
«participates» «participates»
Request
CatalogueUpdate
Prov ide
CatalogueUpdate
act Catalogue
ActivityInitial [subscribe]
[provide [request]
catalogue without
request] «BusinessProcessActi... «SharedBusiness...
«BusinessProcessA...
Receiv e&AssessRequest :Catalogue
RequestCatalogue
[CatalogueRequested]
[if subscription
exists]
[reject]
«SharedBusines... «BusinessProcessActi...
«BusinessProcessActivity»
:Catalogue NotifyRej ection
Receiv eRej ectionNotification
[CatalogueRejected]
[accept]
[if update
[if subscription
required]
and update
available] «SharedBusinessEntitySt... «BusinessProcessActiv...
«BusinessProcessActivity»
:Catalogue RequestCatalogueUpdate
CheckCatalogueUpdateRequest
[CatalogueUpdateRequested]
[accept]
«BusinessProcessA... «SharedBusinessEntity...
Receiv eAcceptance :Catalogue «BusinessProcessActivity»
[CatalogueUpdateAccepted] AcceptCatalogueUpdate
End
by request"
is" provided
4.2. Business Entity Life Cycle Catalogue
Start here if
The Business Entity Life Cycle shows the states that the Catalogue Entity may reach as the Catalogue
business process is executed. Each change of state results from the exchange of information between
the business partners using the appropriate business transactions. The Catalogue Process requires
four re-useable business transactions to achieve this. See section 5 and 7 for the transaction details.
stm Catalogue
Initial
«BusinessEntityState»
CatalogueSubscriptionRequested
«BusinessEntityState»
CatalogSubscriptionRej ected
«BusinessEntityState» «BusinessEntitySta...
CatalogueSubscriptionAccepted CatalogueRequested
«BusinessEntityState»
CatalogueRequestAccepted
«BusinessEntitySta...
CatalogueProv ided
«BusinessEntitySta...
CatalogueRej ected
«BusinessEntityState»
CatalogRequestRej ected
«BusinessEntitySta...
CatalogueAccepted
«BusinessEntityState»
CatalogueUpdateRequested
«BusinessEntityState»
CatalogueUpdateProv ided
«BusinessEntityState»
CatalogueUpdateAccepted
«BusinessEntityState»
CatalogueUpdateRequestRej ected
«BusinessEntityState»
CatalogueUpdateRej ected
Final
«BusinessTransactionUseCase»
«participates» RequestSubscrption «participates»
SubscriptionRequester SubscriptionResponder
«BusinessTransactionUseCase»
«participates» Request Catalogue «participates»
CatalogueRequester
CatalogueResponder
«BusinessTransactionUseCase»
«participates» Prov ide Catalogue «participates»
«BusinessTransactionUseCase»
Request
«participates» «participates»
CatalogueUpdate
CatalogueUpdateRequester CatalogueUpdateRequestResponder
«BusinessTransactionUseCase»
Prov ide
«participates» CatalogueUpdate «participates»
uc Prov ideCatalogueBySubscripti...
Catalogue
«participates» «participates»
«BusinessTransactionUseCase»
«participates» RequestSubscrption «participates»
«mapsTo»
SubscriptionResponder
(from RequestSubscription)
SubscriptionRequester
(from RequestSubscription)
(from RequestSubscription) include
«mapsTo»
«BusinessTransactionUseCase»
«participates» Request Catalogue «participates»
CatalogueResponder
CatalogueRequester (from RequestCatalogue)
(from RequestCatalogue)
«mapsTo»
(from RequestCatalogue)
«mapsTo»
«mapsTo»
include
«mapsTo»
«BusinessTransactionUseCase»
«participates» Prov ide Catalogue «participates»
«BusinessTransactionUseCase»
Request
«participates» CatalogueUpdate «participates»
CatalogueUpdateRequester CatalogueUpdateRequestResponder
(from RequestCatalogueUpdate)
(from RequestCatalogueUpdate) (from RequestCatalogueUpdate)
include «mapsTo»
«BusinessTransactionUseCase»
«participates» Prov ide
CatalogueUpdate «participates»
ActivityInitial
«BusinessTransaction...
RequestSubscription
«BusinessTransactionActiv ity»
RequestCatalogue
«BusinessTransactio...
Prov ideCatalogue
«BusinessTransaction...
RequestCatalogueUpdate
«BusinessTransactio...
Prov ideCatalogueUpdate
ActivityFinal
Catalogue
«participates» «participates»
«BusinessTransactionUseCase»
«participates» Request Catalogue «participates»
«mapsTo»
CatalogueRequester CatalogueResponder
(from RequestCatalogue) (from RequestCatalogue)
(from RequestCatalogue)
include
«mapsTo»
«BusinessTransactionUseCase»
«participates» Prov ide Catalogue «participates»
The order in which the transactions take place is shown in Figure 14 below, the activity diagram of
ProvideCatalogueByRequest business collaboration.
ActivityInitial
«BusinessTransaction...
RequestCatalog
«BusinessTransaction...
Prov ideCatalogue
ActivityFinal
The ProvideCatalogueByRequest Collaboration uses the transactions in the order shown in Figure 14.
7. Business Transactions
The transactions used in the Catalogue Process are described in the worksheets below and the
transaction pattern illustrated in the activity diagrams. These show the authorized roles of the sender
and responder together with the activities that take place and the name of the information envelope
that carries the information (message) exchanged.
Business RequestSubscription
Transaction name
Description The Catalogue Receiver sends a request for a catalogue subscription to the Catalogue
Provider. The Catalogue Provider receives the request and must respond using an
application response.
Transaction SubscriptionResponse
Pattern
Requester’s side
Requesting Role SubscriptionRequester
Requesting RequestSubscription
Business Activity
Name
Business SubscriptionRequest
Information
Envelope
Responder’s Side
Responding Role SubscriptionResponder
Responding ReceiveSubscriptionRequest
Business Activity
Name
Business ApplicationResponse
Information
Envelope
act RequestSubscription
«BusinessTransactionSw imlane» «BusinessTransactionSw imlane»
SubscriptionRequester SubscriptionResponder
Initial
State
«RequestingBusinessActiv ity»
«RespondingInformationEn...
RequestSubscription
:ApplicationResponse
[Success]
[Failure]
FinalStateName.Success
FinalStateName.Failure
«RequestingInformationEnvelop...
«RespondingBusinessActiv ity»
:SubscriptionRequest Receiv eSubcriptionRequest
act RequestCatalogue
«BusinessTransactionSw imlane» «BusinessTransactionSw imlane»
CatalogueRequester :CatalogueResponder
Initial
State
[Success]
[Failure]
FinalStateName.Success
FinalStateName.Failure
«RespondingBusinessActiv ity»
«RequestingInformationEnvelo...
Receiv eCatalogueRequest
CatalogueRequest
Initial
State
[Failure]
[Success]
FinalStateName.Failure
FinalStateName.Success
«RequestingInformationEnvelope»
«RespondingBusinessActiv ity»
:Catalogue Receiv eCatalogue
act RequestCatalogueUpdate
«BusinessTransactionSw imlane» «BusinessTransactionSw imlane»
CatalogueUpdateRequester :CatalogueUpdateRequestResponder
Initial
State
«RequestingBusinessActiv ity»
«RespondingInformationEnvelope»
RequestCatalogueUpdate
:ApplicationResponse
[Success]
[Failure]
FinalStateName.Success
FinalStateName.Failure
Initial
State
[Failure]
[Success]
FinalStateName.Failure
FinalStateName.Success
0..1
Hazardous Logistic unit Product Specification
Information information Information Reference
0..*
Dimensions 0..1 0..1
Tax Exemption Product Unit
Reason 0..*
0..1
0..1
Product Class
1..*
Packaging
0..1 Material
Marketing
0..1 Campaign
0..*
Price
Comparison
9. Business Documents
The information exchanged in the information envelopes described in the four business transactions
represent the Subscription Request, Catalogue Request, Application Response and Catalogue. The
detailed content for these are described below.
General remarks:
When texts have a cardinality of ..* this is meant to support communication of the same text in
multiple languages.
SRQ 1..1 Catalogue The requester of the catalogue The requester of a catalogue
0005 Subscription subscription subscription and the receiver of
Requester catalogue
SRQ 1..1 Catalogue The receiver of the catalogue The receiver of a catalogue
0006 Subscription subscription request subscription request and the provider
Receiver of a catalogue
SRQ 0..1 Procurement Party The party at the customer side UBL
0007 responsible for negotiating the
contract and the contents of the
catalogue.
SRQ 0..n Supplier party Supplier (s) whose catalogue
0008 (s) is requested to be
subscribed to
SRQ 0..n Contract Reference Reference to the Contract(s)
0009 the catalogue subscription
request is subject of.
SRQ 0..n Document Reference to other document UBL
0010 Reference (s) applicable for the catalogue
subscription
SRQ 0..n Signature To facilitate digital signing of the UBL
0011 subscription request
SRQ 0..1 Subscription Subscription request on UN/CEFACT Code list to be
0012 Catalogue Update frequency of Catalogue referenced
Frequency updates.
2
The short name of the business entity may be changed in the process of developing the Requirement Specification
Mapping (RSM),
Code list:
Full – a full catalogue including all
updates must be provided
Partial – only all the updated/changed
Catalogue Items must be provided
Partial Price - only price changed
catalogue items must be provided
Partial Item – only catalogue items
with item specification changes must
be provided
CRQ 0..n Requested Requested Language(s) for the Code list:
0012 Catalogue requested Catalogue ISO 639
Language(s) Code
CRQ 0..1 Requested Requested Currency of the Code list: ISO 4217
0013 Catalogue Currency prices, allowances and charges
Code in the requested Catalogue
CRQ 0..n Requested Product The product classification Code list
0014 Classification scheme(s) required for UNSPSC
Scheme Code classifying the products in the
requested Catalogue CPV
GS1 GPC
CRQ 0..1 Requested The period for which the
0015 Catalogue Validity requested Catalogue must be
Period valid and ready for use.
CRQ 0..n Requested Product Requested Product group(s) to
0016 Group(s) be included in the Catalogue by
using a Product Classification
Scheme
CAT 1..1 Catalogue status Code giving the status of the Code list:
0008 code catalogue Original – Initial catalogue
Replace - Catalogue replacing a
previous catalogue
Change - Catalogue containing
changed items compared to previous
catalogue
CAT 0..1 Catalogue Reference to the updated or
0009 update/replace, replaced Catalogue
Reference
CAT 0..1 Price List A reference to the price list for Reference to a price list at this header
0010 Reference this catalogue level can be overridden at line level.
A business rule must be made when
using this business term concurrently
with the price list reference at the
level of Trade agreement.
CAT 0..1 Contract Reference A reference to business contract UBL
0011 which the catalogue is based Reference to contract at this header
upon. level can be overridden at line level.
Must be possible to state the contract
reference on header level in cases
where it can not be stated on line
level or where it must be mandated
that only one contract can be
referenced for all lines. Must be
possible to give contract reference for
each supplier.
CAT 1..1 Catalogue Provider The Provider of the Catalogue
0012 Information.
CAT 1..1 Catalogue Receiver The Receiver of the Catalogue
0013 Information
CAT 0..1 Procurement Party The party at the customer side UBL
0014 responsible for negotiating the
contract and the contents of the
catalogue.
CAT 0..1 Supplier Party Party who owns the item and
0015 consigns or makes them
available in trade
TAG 0..1 Contract Reference The reference to a Contract. Provides for multi supplier catalogue.
0223
TAG 0..1 Contract A text giving a subdivision of a UBL
0224 Subdivision text contract or tender. Examples "Installation", "Phase One",
Support and Maintenance"
TAG 0..1 Price Contract The reference to a contract
0225 Reference specifying the price conditions.
TAG 0..1 Customer Support The customer support centre for GS1
0226 Centre - Party the catalogue item.
TAG 0..1 Restricted The indicator to qualify that Indicators:
0227 information catalogue item information is True, False
indicator restricted to specific use
according to agreement.
TAG 0..1 Product Ordering The period of date the catalogue GS1
0228 Period item (product) can be ordered.
TAG 0..1 Product Exclusivity The date and time at which a GS1 – special exclusivity
0229 end date time catalogue item (product)no agreements between brand owner
longer is exclusive to the trading and a buyer (retailer)
partner
TAG 0..1 Availability To The first date/time the buyer is GS1
0230 Consumer Start allowed to resell the catalogue
Date and Time item (product).
TAG 0..1 Product First The earliest date at which the GS1
0231 Delivery Date supplier can deliver the
catalogue item (product) to the
trading partner.
TAG 0..1 Minimum product A number of days from the GS1
0232 lifespan from time arrival date, guaranteed by the
of arrival, Days manufacturer, before the
expiration date of the product.
TAG 0..1 Orderable indicator The indicator identifying that the UBL
0235 catalogue item may be ordered GS1
Indicators:
True, False
TAG 0..1 Made to Order Indicates that the item will only Not GS1
0236 Indicator be produced when the Indicators:
manufacturer receives an order
True, False
PRI 0..* Price Change The reason for the price UBL
0276 Reason Text change expressed as text
PRI 0..n Validity Period for The period(s) for which the UBL
0278 Price price is valid
PRI 0..1 Bracket Price The quantity range (minimum, Not GS1
0279 Quantity Range maximum) of the item for which
the price is valid
PLR 0..1 Validity Period The period(s) for which the UBL
0284 price list is valid
PRO 0..1 Sub Brand Name Second level of brand name for GS1 – E.g. trademark. It is the
0333 the product. primary differentiating factor that a
brand owner wants to communicate
to the consumer or buyer. E.g.
Yummy-Cola Classic. In this example
“Yummy-Cola” is the brand name and
“Classic” is the subBrand.
PRO 0..* Descriptive Form A description of the physical GS1
0334 Text form or shape of the product.
Used, for example, in
pharmaceutical industry to
indicate the formulation of the
trade item. Defines the form the
trade item takes and is distinct
from the form of the packaging.
Examples: paste, gel, powder
PRO 0..1 Product Quantity The quantity of the product GS1
0335 contained in the product (trade UBL
item) (incl measurement unit
code according to UN/ECE
recommendation 20 /
UN/CEFACT code list 6411)
9.4.1.12.Campaign (Marketing)
UID Crd Short Name Business Requirement Rationale / Example / Mapping
Notes
CAM
CAM 0..1 Product Marketing The name of a marketing GS1
0420 Campaign Name campaign of a product.
CAM 0..1 Product marketing The period for the marketing GS1
0421 campaign period campaign of a product.
9.4.1.14.Dimensions (Product)
UID Crd Short Name Business Requirement Rationale / Example / Mapping
Notes
DIM
DIM 0..1 Product Material The measured area weight of GS1
0440 Area Weight the material. (expressed in ounces per square yard
or grams per square meter)
DIM 0..1 Product Gross The gross weight of the product GS1
0441 weight (includes all packaging materials (At pallet level the item Gross Weight
of the product) includes the weight of the pallet itself)
DIM 0..1 Product Height The height of the product. The GS1
0442 vertical dimension from the
lowest extremity to the highest
extremity, including packaging.
(At a pallet level the item Height
will include the height of the
pallet itself.)
DIM 0..1 Product depth The depth of the product. GS1
0443 Measured from front to back of Measurements are relative to how the
the product. customer normally views the trade
item. May be needed to be
associated with a valid UoM.
MAL 0..* Offer Text marked A text about an offer marked on GS1
0578 on package, text the package.
MAL 0..n Package Marks The code (s) marked on GS1
0579 containment Code package stating whether or not - code list
the product contains or is free
from a specific substance. FREE_FROM_EGG Marks if the
product is free from egg.
FREE_FROM_FISH The item is
physically marked as being free from
fish, as approved by the appropriate
authority of the target market.
FREE_FROM_GLUTEN Marks if the
product is free from gluten.
FREE_FROM_LACTOSE Indicates if
the amount of lactose is reduced.
FREE_FROM_LATEX The item is
physically marked being free from
Latex (rubber) as approved by the
appropriate authority of the target
market.
FREE_FROM_LEGUME_PROTEIN
The item is physically marked as
being free from legume protein, as
approved by the appropriate authority
of the target market.
FREE_FROM_MILK The item is
physically marked as being free from
milk and any of its derivates, as
PRU 0..1 Product Instance The serial number of the product UBL
0654 Serial Number instance.
Price Price
Quantit Quantity
y Range
Range
Price Validity 0..n 7300000000000 7300000000000 7300000000000