TBG1-BRSCrossIndustryCatalogue2009 (1)

8/6/2019 TBG1-BRSCrossIndustryCatalogue2009 (1)

1/75

UN/CEFACTSimple, Transparent and Effective Processes

For Global Commerce

BUSINESS REQUIREMENTS SPECIFICATION

(BRS)

Business Domain: Cross Industry Supply Chain

Business Process: Catalogue Process

Document Identification: CEFACT/Forum/2006/TBG1

Title: Catalogue

UN/CEFACT International Trade and Business Processes Group: TBG1

Document location : http://www.uncefactforum.org/TBG/TBG1/tbg1.htm

Version: 1.00 review #2

Release: R.09B

Date of TBG approval: Date


2/75

Business Requirements Specification 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(one sentence summary)

Business requirement specification for product catalogue and completebusiness process.

Contributors

Name Organization

Log of Changes

Issue No. Date of Change Changed By Summary of Change

Date 2008-11-10, Issue #2 UN/CEFACT Page 2 of 75


3/75


TABLE OF CONTENTS

Preamble.....................................................................................5

References..................................................................................5

Objective ....................................................................................51.1. Scope ...................................................................................................................................................6

1.2. Context Categories .................................................................................................................. ............7

1.3. Business Domain View ........................................................................................................................8

1.3.1. Catalogue Process within the BUY-SHIP-PAY Model.................................................................8

1.3.2. Catalogue Domain Use Case diagram ....................................................................................... .8

Business Requirements View .......................................................91.4. Business Process Elaboration ..............................................................................................................9

1.4.1. Provide Article/Product/Item/Partner Information via a Catalogue ...............................................9

1.4.1.1. Business Process Use Case Description ..........................................................................9

1.5. Business Entity Life Cycle ..................................................................................................................13

Business Transactions-Use Case Diagrams..................................141.5.1. Request Subscription .......................................................................................................... ......14

1.5.2. Request Catalogue ....................................................................................................................14

1.5.3. Provide Catalogue .....................................................................................................................14

1.5.4. Request Catalogue Update .......................................................................................................15

1.5.5. Provide Catalogue Update ..................................................................................................... ...15

Business Collaborations processes .............................................151.5.6. Provide Catalogue By Subscription Business Collaboration ..................................................... .15

1.5.7. Provide Catalogue By Request Business Collaboration ............................................................18

Business Transactions................................................................191.5.8. Request Catalogue Subscription business transaction ..............................................................20

1.5.9. Request Catalogue business transaction ..................................................................................22

1.5.10. Provide Catalogue business transaction ........................................................................... ......24

1.5.11. Request Catalogue Update business transaction ....................................................................26

1.5.12. Provide Catalogue Update business transaction .....................................................................28

Catalogue Information Model......................................................29

Business Documents..................................................................301.6. Subscription Request (Business Document) ......................................................................................31

1.7. Catalogue Request (Business Document) .............................................................................. ...........34



4/75


1.8. Application Response (Business Document) .....................................................................................37

1.8.1. Response to received catalogue line (Application Response) ...................................................38

1.9. Catalogue (Business Document) ........................................................................................................38

1.9.1.1. Catalogue Item (Catalogue) ............................................................................................40

1.9.1.2. Tax Information (Catalogue Item) ...................................................................................42

1.9.1.3. Tax Exemption (Tax Information) ....................................................................................431.9.1.4. Trade Agreement (Catalogue Item) ................................................................................43

1.9.1.5. Price information (Trade agreement) ..............................................................................46

1.9.1.6. Price List Reference (Price information) ................................................................ .........48

1.9.1.7. Price Comparison (Price Information) ............................................................................48

1.9.1.8. Trade Delivery (Catalogue Item) .....................................................................................50

1.9.1.9. Product (Catalogue Item) ...............................................................................................50

1.9.1.10. Product Identification (Product) ....................................................................................55

1.9.1.11. Marketing (Trade Agreement) .......................................................................................55

1.9.1.12. Campaign (Marketing) ................................................................................................. .57

1.9.1.13. Warranty information (Trade Agreement) .....................................................................57

1.9.1.14. Dimensions (Product) ...................................................................................................57

1.9.1.15. Handling Instructions (Trade Delivery) ..........................................................................58

1.9.1.16. Hazardous Information (Product) ..................................................................................59

1.9.1.17. Hierarchy Information (Product) ..................................................................................61

1.9.1.18. Next lower product level information (Hierarchy Information) .......................................61

1.9.1.19. Additional Product Relation (Catalogue Item) .............................................................. .61

1.9.1.20. Marketing Feature (Marketing) ......................................................................................62

1.9.1.21. Marks and Labels (Package Information) .....................................................................62

1.9.1.22. Logistic Unit Information (Product) ................................................................................67

1.9.1.23. Package Information (Product) .....................................................................................67

1.9.1.24. Packaging Information (Package information) .............................................................681.9.1.25. Packaging Material (Packaging information) .................................................................69

1.9.1.26. Product Material (Product) ............................................................................................69

1.9.1.27. Product Unit (Product) ............................................................................................... ...70

1.9.1.28. Product Class (Product) ................................................................................................70

1.9.1.29. Property (Packaging Material, Product, Product Material and Product Class) ............. .71

1.9.1.30. Product Specification Information Reference (Product) ................................................73

1.9.1.31. Trade Item Delivery Lead Time (Trade Agreement) ................................................ .....73

1.9.1.32. Signature (All documents) .............................................................................................74

Business Rules...........................................................................74

Use case examples.....................................................................74

Definition of Terms....................................................................75



5/75


PreambleThe current practice of exchanging business documents by means of telecommunications usuallydefined 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 thetrading cycle.

Started as an initiative by CEN/ISSS Workshop eBES, the European Expert Group 1 (EEG1) SupplyChain & e-Procurement developed the Cross Industry Catalogue in 2005/2006. The Cross IndustryCatalogue has been compiled by a working group with contributions from BME (German AssociationMaterials Management, Purchasing and Logistics), BLI at the University of Duisburg-Essen,Fernuniversitt Hagen, PIDX, OASIS/UBL, CRITT Informatique, SupplyChange, Healthlogistics,Eurofer, CEN/ISSS WS E-Catalogue. Paradigma Unternehmensberatung Gmbh, EPDC, ISO TC184SC4 and VWR, GS1, the Danish government and Swedish Local authorities and regions.

The document describe globally consistent catalogue information exchange processes for worldwidesupply chains and e-Procurement of commodities, using the UN/CEFACT Modelling Methodology(UMM) approach and Unified Modelling Language to describe the business processes and businessdocuments involved.

The structure of this document is based on the structure of the UN/CEFACT Business RequirementsSpecification (BRS) document reference CEFACT/ICG/005.

ReferencesUN/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 Specificat ion 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

ObjectiveThe objective of this specification is to describe the business processes, the business documents andthe information entities for the exchange of catalogue information, including price information, used byindustries for the supply chain.

The business process is the detailed description of the way trading partners intend to play theirrespective roles, establish business relations and share responsibilities to interact efficiently with thesupport 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 andmessages). The sequence in which these transactions are used, represent particular scenarios andare presented as activity diagrams in this document.

The information exchanged in the business documents/messages are presented in lists of businessentities and their attributes.



6/75


1.1. Scope

This section describes the extent and limits of the business processes within the supply chain beingdescribed in this document. Each industry may specify, based on the BRS of the cross industrycatalogue 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 tofurther specify their products in the existing structure. If further elaboration is needed an industryspecific 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 Customersand give basic information needed for ordering those goods or services. A catalogue will containinformation on the products being offered and may contain price information, terms of trade and othercommercial 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 tostructure the information in electronic catalogues, so they can be sent to customers and potentialcustomers, in whole or part, and be the basis for the ordering of the goods or services defined in thosecatalogues. Customers may ask for catalogue data ad hoc, or they may subscribe to the catalogueprocess and receive all or parts of the catalogue data.



7/75


8/75


1.3. Business Domain View

1.3.1. Catalogue Process within the BUY-SHIP-PAY ModelThe Catalogue Business Process is part of the supply chain process. A catalogue may be

thought of as equivalent to a quotation or as part of a contract reflecting product informationand agreed terms of business. It is positioned within the BUY-SHIP-PAY model as part of the

Establish Business Agreement use case.uc Catalogue

:ldentifyPotentialTrading

Partner

:EstablishBusiness

Agreement:Order

:Ship :Pay

ProcessArea

Catalogue

+ Catalogue

+ Catalogue

+ Catalogue

(from EstablishBusinessAgreement)

Figure 1. Positioning of the Catalogue process within the BUY-SHIP-PAY model.

1.3.2. Catalogue Domain Use Case diagram

The Business partner types involved in the catalogue process includes the Customer, Supplier orIntermediary. They play the roles of Catalogue Provider and Catalogue Receiver.



9/75


uc Catalogue

ProvideCatalogue

SubscibeToCatalogue

RequestCatalogue

CatalogueProvider CatalogueReceiver

Provide

CatalogueUpdate

Request

CatalogueUpdate

participates

participates

participates

participatesparticipates



participates

Figure 2. Catalogue-Business Domain Use Case Diagram

The use cases shown in figure 2 are elaborated in section 4, below.

Business Requirements View

1.4. Business Process ElaborationThis section elaborates the business use cases that make up the catalogue process.

1.4.1. Provide Article/Product/Item/Partner Information via a Catalogue

1.4.1.1. Business Process Use Case Description

Businessprocess name

Provide Article/Product/Item/Partner Information via a Catalogue

Identifier BUY-SHIP-PAY/ Procurement&Sales/ EstablishBusinessAgreement/

Catalogue/ Catalogue Subscription

BusinessPartner Types

Catalogue Provider, Catalogue Receiver



10/75


Pre-conditions(PrC)

PrC1 - Catalogue Receiver has a need for a catalogue.

PrC2 - Parties may have an established business agreement.

PrC3 - The Catalogue Receiver and Catalogue Provider may have established aCatalogue Subscription including agreement concerning the updating of the catalogue

OrPrC4 - the Catalogue Provider provides the catalogue to the Catalogue Receiveraccording to the Request for Catalogue provided by the Catalogue Receiver.

Or

PrC5 - the Catalogue Provider provides the catalogue to the Catalogue Receiver by usingboth Catalogue Subscription and Request for Catalogue.

Description The Catalogue Receiver sends a request for a catalogue subscription to the CatalogueProvider.

The process results in an accepted catalogue subscription request or in the rejection ofthe catalogue subscription request.

The Catalogue Receiver requests a catalogue from a Catalogue Provider usingCatalogue Request or the Catalogue Provider issues a Catalogue to the CatalogueReceiver according to the agreed terms in the Catalogue Subscription.

The Catalogue Provider may reject the request for a catalogue or provide a catalogueaccording to the request.

If the Catalogue Request is rejected by the Catalogue Provider the Catalogue Receivermay request a Catalogue again by using Catalogue Request.

The Catalogue Provider may provide a catalogue according to agreed terms in theCatalogue Subscription.

On receipt of the catalogue the Catalogue Receiver notifies the Catalogue Provider of theacceptance or rejection of the catalogue.

If a Catalogue provided according to a catalogue subscription is rejected by theCatalogue Receiver the Catalogue Provider can provide an altered catalogue afterconsidering the cause for rejection and according to the agreed terms in the CatalogueSubscription.

The Catalogue Provider provides the Catalogue update according to the agreed terms in

the Catalogue Subscription or the Catalogue Provider provides the Catalogue updateaccording to the requirements in the Catalogue Request.

The Catalogue Update may be a full catalogue containing all items including changed andunchanged item information. This replacement catalogue replaces all the prior catalogueinformation.

The catalogue update may contain only information about changed item information. Thischanged information replaces only the catalogue information for the identified catalogueitem in previous accepted catalogue.

The Catalogue Receiver notifies the Catalogue Provider of the acceptance or therejection of the catalogue update received.

The Catalogue Receiver may request a Catalogue update again by using CatalogueRequest.

If a Catalogue Update provided according to a catalogue subscription is rejected by the

Catalogue Receiver the Catalogue Provider can provide an altered catalogue update afterconsidering the cause for rejection and according to the agreed terms in the CatalogueSubscription.

After acceptance of the catalogue, the Catalogue Receiver can use the data provided forfurther business processes.When a Catalogue Update is rejected the Catalogue Receiver must consider items mayhave been expired, replaced or price changed even though the Catalogue Update hasbeen rejected by the Catalogue Receiver.



11/75


Post-conditions(PoC)

PoC1 - Catalogue Subscription Request is rejected:After the rejection of the catalogue subscription request the same situation exists asdefined under the pre-condition PrC1.

PoC2 - Catalogue request is rejected:After the rejection of the request for catalogue the same situation exists as defined under

the pre-condition PrC1.PoC3 Provided Catalogue is rejected and the Catalogue Provider is notified regardingthe reasonAfter the rejection of the catalogue the same situation exists as defined under the pre-condition PrC1.

PoC4 Provided Catalogue Update is accepted.Provided Catalogue Update is accepted by the Catalogue Receiver

PoC5 Provided Catalogue Update is rejected.Catalogue Update is Rejected by the Catalogue Receiver

After the rejection of the Catalogue Update the same situation exists as defined under thepre-condition PrC3, or PrC4 or PrC5.

After rejection of a received catalogue update, the Catalogue Receiver may request aCatalogue again by using Catalogue Request or after considering the cause for rejection

and according to the agreed terms in the Catalogue Subscription the Catalogue Providerprovide an altered catalogue update.

Scenario The catalogue processes are used to offer goods or services by the Supplier to potentialCustomers and give basic information needed for ordering those goods or services. Acatalogue will contain information on the products being offered and may contain priceinformation, 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 toupdates

Exchange of multi Supplier catalogues or parts of multi Suppliers catalogues inrelation to updates

Customer specific items and prices, including contract prices

Table 4-1 Business Process Use Case Description



12/75


13/75


1.5. Business Entity Life Cycle

The Business Entity Life Cycle shows the states that the Catalogue Entity may reach as the Cataloguebusiness process is executed. Each change of state results from the exchange of information betweenthe business partners using the appropriate business transactions. The Catalogue Process requiresfour re-useable business transactions to achieve this. See section 5 and 7 for the transaction details.

stm Catalogue

BusinessEntitySta...

CatalogueAccepted

Initial


CatalogueProvided

Final

BusinessEntityState

CatalogueSubscriptionRequested

BusinessEntityState

CatalogueSubscriptionAcceptedBusinessEntitySta...

CatalogueRequested

BusinessEntityState

CatalogRequestRejected

Start here if

Catalogue

is" provided

by request"

BusinessEntityState

CatalogSubscriptionRejected


CatalogueRejected

BusinessEntityState

CatalogueRequestAccepted

BusinessEntityState

CatalogueUpdateRequested

BusinessEntityState

CatalogueUpdateRequestRejected

BusinessEntityState

CatalogueUpdateProvided

BusinessEntityState

CatalogueUpdateAccepted

BusinessEntityState

CatalogueUpdateRejected

Figure 4 Business Entity States for Catalogue Process



14/75


Business Transactions-Use Case DiagramsThe five business transactions that realize the catalogue process are RequestSubscription,RequestCatalogue, ProvideCatalogue, RequestCatalogueUpdate and ProvideCatalogueUpdate.These transactions are detailed in the sections below.

1.5.1. Request Subscription

uc RequestSubscription

SubscriptionRequester SubscriptionResponder

BusinessTransactionUseCase

RequestSubscrptionparticipates participates

1.5.2. Request Catalogue

uc RequestCatalogue


Request Catalogue

CatalogueRequesterCatalogueResponder


1.5.3. Provide Catalogue

uc ProvideCatalog...


Provide Catalogue

ReceiverProvider



Figure 5 RequestSubscription Use Case diagram

Figure 6 RequestCatalogue Use Case diagram

Figure 7 ProvideCatalogue Use Case diagram


15/75


1.5.4. Request Catalogue Update

uc RequestCatalogueUpdate


Request

CatalogueUpdate

CatalogueUpdateRequester CatalogueUpdateRequestResponder


1.5.5. Provide Catalogue Update

uc ProvideCatalogueUpd...


Provide

CatalogueUpdate

UpdateReceiv erUpdateProvider

participates participates

Business Collaborations processesThe two business collaborations in the Catalogue process are implemented using five businesstransactions illustrated above. The authorized roles of the sender and receiver of the business

transactions in the collaborations are related to the Catalogue Provider and Catalogue Receiver. Theorder in which the transactions occur is shown in the corresponding Activity diagram.

1.5.6. Provide Catalogue By Subscription Business Collaboration

This collaboration uses two of the transactions-RequestSubscription and NotifyResponse.

The Subscription Requester and the ResponseReceiver roles in the transactions are taken by theCatalogue Receiver. The SubscriptionResponder and ResponseProvider roles are taken by theCatalogue Provider.Sub


Figure 8 RequestCatalogueUpdate Use Case diagram

Figure 9 ProvideCatalogueUpdate Use Case diagram


16/75


uc ProvideCatalogueBySubscripti...

CatalogueReceiv er

(from Catalogu e)

CatalogueProvider

(from Catalogu e)

Catalogue

(from ProvideCatalogue)


Provide Catalogue

Provider


Receiver


(from RequestSubscripti on)


RequestSubscrption

SubscriptionRequester

(from RequestSubscriptio n)

SubscriptionResponder

(from RequestSubscriptio n)

(from RequestCatalogue)


Request Catalogue

CatalogueRequester

(from RequestCatalog ue)

CatalogueResponder


(from ProvideCatalogueUpdate)


Provide

CatalogueUpdate

UpdateProvider


UpdateReceiv er


(from RequestCatalogueUpdate)


Request

CatalogueUpdate

CatalogueUpdateRequester


CatalogueUpdateRequestResponder


inc lude

mapsToinclude

mapsTo

mapsTo

mapsTo

mapsTo


include

participates

participates

mapsTo

participates

participates

mapsTo

mapsTo

mapsTo

mapsTo

include

include


participates


participates

Figure 11. SubscribeToCatalogue BusinessCollaboration

The order in which the different transactions take place is shown in figure 12 below, the activity diagramof SubscribeToCatalogue business collaboration



17/75


act Prov ideCatalogBySubscripti...

BusinessTransactionActiv ity

RequestCatalogue

ActivityInitial

ActivityFinal

BusinessTransaction...

RequestCatalogueUpdate


RequestSubscription

BusinessTransactio...

Prov ideCatalogue

BusinessTransactio...Prov ideCatalogueUpdate

Figure 12 ProvideCatalogueBySubscription Business Collaboration activity diagram

Thus the ProvideCatalogueBySubscription BusinessCollaboration uses five transactions.

The RequestSubscription transaction may be followed by the RequestCatalogue transaction beforethe ProvideCatalogue transaction.



18/75


The ProvideCatalogue transaction may or may not be followed by a RequestCatalogueUpdate beforea ProvideCatalogueUpdate transaction follows.

1.5.7. Provide Catalogue By Request Business Collaboration

This collaboration uses two of the transactions-RequestCatalogue, ProvideCatalogue.

The Catalogue Requester and the Catalogue Receiver roles in the transactions are taken by theCatalog Receiver. The Catalogue Responder and Catalogue Provider roles are taken by theCatalogue Provider. Application Response message must be used in both the CatalogueRequest andthe ProvideCatalogue.

uc ProvideCatalogueByRequ...

CatalogueProvider

(from Catalogue)

CatalogueReceiver

(from Catalogue)



Provide Catalogue

Receiver


Provider


(from ProvideCatalogueBySubscription)

Catalogue



Request Catalogue

CatalogueRequester


CatalogueResponder




mapsTo

include

include


mapsTo

mapsTo

mapsTo

Figure 13 ProvideCatalogueByRequest BusinessCollaboration

The order in which the transactions take place is shown in Figure 14 below, the activity diagram ofProvideCatalogueByRequest business collaboration.



19/75


act Prov ideCatalogueByRequ...


Prov ideCatalogue

ActivityInitial

ActivityFinal

BusinessTransaction...RequestCatalog

Figure 14. Activity diagram ofProvideCatalogueByRequest Business Collaboration

The ProvideCatalogueByRequest Collaboration uses the transactions in the order shown in Figure 14.

Business TransactionsThe transactions used in the Catalogue Process are described in the worksheets below and thetransaction pattern illustrated in the activity diagrams. These show the authorized roles of the senderand responder together with the activities that take place and the name of the information envelopethat carries the information (message) exchanged.



20/75


1.5.8. Request Catalogue Subscription business transaction

BusinessTransaction name

RequestSubscription

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 anapplication response.

TransactionPattern

SubscriptionResponse

Requesters side

Requesting Role SubscriptionRequester

RequestingBusiness ActivityName

RequestSubscription

BusinessInformation

Envelope

SubscriptionRequest

Responders Side

Responding Role SubscriptionResponder

RespondingBusiness ActivityName

ReceiveSubscriptionRequest

BusinessInformationEnvelope

ApplicationResponse

Table 5-1 Business Transaction Worksheet for RequestSubscription



21/75


act RequestSubscription

SubscriptionResponder

BusinessTransactionSwimlane

SubscriptionRequester


RequestingBusinessActivity

RequestSubscription

RespondingBusinessActiv ity

Receiv eSubcriptionRequest

RequestingInformationEnvelop...

:SubscriptionRequest

Initial

State

FinalStateName.Success

FinalStateName.Failure

RespondingInformationEn...

:ApplicationResponse

[Failure]

[Success]

Figure 17 Activity diagram for RequestSubscriptionTransaction



22/75


1.5.9. Request Catalogue business transaction

Business Transactionname

RequestCatalogue

Description The Catalogue Receiver requests a catalogue from a Catalogue Responder. TheCatalogue Provider receives the request and must respond using an applicationresponse.

Transaction Pattern Request Response

Requesters Side

Requesting Role CatalogueRequester

Requesting BusinessActivity Name

RequestCatalogue

Business InformationEnvelope

CatalogueRequest

Responders Side

Responding Role CatalogueResponder

Responding BusinessActivity Name

ReceiveCatalogueRequest


ApplicationResponse

Table 5-2 Business Transaction worksheet-RequestCatalogue



23/75


act RequestCatalogue

:CatalogueResponder


CatalogueRequester



RequestCatalogue

RespondingBusinessActivity

ReceiveCatalogueRequest

Initial

State



RequestingInformationEnvelo...

CatalogueRequest

RespondingInformationEnvelope


[Success]

[Failure]

Figure 18. Activity diagram for RequestCatalogue transaction



24/75


1.5.10. Provide Catalogue business transaction


Provide Catalogue

Description The Provider provides Catalogue to a Receiver. The Receiver receives the Catalogue.

Transaction Pattern CatalogueReceiptResponse

Requesters side

Requesting Role Provider


IssueCatalogue


Catalogue

Responders Side

Responding Role Receiver


ReceiveCatalogue


ApplicationResponse

Table 5-3 Business Transaction worksheet-ProvideCatalogue



25/75


act ProvideCatalog

Receiver


Provider



IssueCatalogue

RespondingBusinessActivityReceiveCatalogue

RequestingInformationEnvelope

:Catalogue



RespondingInformationEnve...


Initial

State

[Success]

[Failure]

Figure19. ProvideCatalogue BusinessTransaction



26/75


1.5.11. Request Catalogue Update business transaction

Business Transactionname


Description The Catalogue Requester requests catalogue from a Catalogue Responder. Thedata may be an original catalogue or an update of a whole catalogue or updatesfor a part of a catalogue.

Transaction Pattern CatalogueUpdateRequestResponse

Requesters Side

Requesting Role CatalogueUpdateRequester

Requesting BusinessActivity Name



CatalogueUpdateRequest

Responders Side

Responding Role CatalogueUpdateRequestResponder

Responding BusinessActivity Name

ReceiveCatalogueUpdateRequest


ApplicationResponse

Table 5-2 Business Transaction worksheet-RequestCatalogueUpdate



27/75


act RequestCatalogueUpdate

:CatalogueUpdateRequestResponder


CatalogueUpdateRequester


RequestingBusinessActiv ity


RespondingBusinessActiv ity

Receiv eCatalogueUpdateRequest

Initial

State



RequestingInformationEnvelo...

:CatalogueUpdateRequest

RespondingInformationEnvelope


[Success]

[Failure]

Figure 18. Activity diagram for RequestCatalogueUpdate transaction



28/75


1.5.12. Provide Catalogue Update business transaction


Provide Catalogue Update

Description The Provider provides Catalogue Update to a Receiver. The Receiver receives theCatalogue Update.

Transaction Pattern CatalogueReceiptResponse

Requesters side

Requesting Role Update Provider


IssueCatalogueUpdate


Catalogue

Responders Side

Responding Role Update Receiver


ReceiveCatalogueUpdate


ApplicationResponse

Table 5-3 Business Transaction worksheet-ProvideCatalogue



29/75


30/75


req Catalogue Entity Model

Product

Trade

Agreement

Catalogue Item

Catalogue

Marketing

Marketing

Feature

Handling

Instructions

Hazardous

Information

Price Information

Trade Deli very

Warranty

Information

Price

Comparison

Hierarchy

Information

Dimensions

Price List

Reference

Campaign

Trade Item Delivery

Lead Time

Package

Information

Marks and

Labels

Packaging

Information

Packaging

Material

Product Unit

Tax Information

Tax Exemption

Reason

Signature

Logistic unit

information

Product

Identification

Property

Product Material

Next Lower Product

Level Information

Additional

Product Relation

Product Specification

Information Reference

Product Cla ss

0..*

0..*

0..1

0..*0..1

0..1

0..*

0..1

0..*

0..*

1

0..1

0..1

1..*

0..*

1

0..1

0..1

1..*

0..1 0..1

0..*

0..1

0..*

0..*

0..*

0..*

0..*

0..1

0..1

0..*

0..*

0..*

0..*

0..*

Figure 20. Catalogue Entity Model

Business DocumentsThe information exchanged in the information envelopes described in the four business transactionsrepresent the Subscription Request, Catalogue Request, Application Response and Catalogue. Thedetailed content for these are described below.

General remarks:

When texts have a cardinality of ..* this is meant to support communication of the same text inmultiple languages.



31/75


1.6. Subscription Request (Business Document)

UID Crd Short Name2 Business Requirement Rationale / Example / MappingNotes

SRQSRQ0001

1..1 DocumentInformation

Generic document.

SRQ0002

1..1 SubscriptionRequest Identifier

The identifier of the subscriptionrequest message

SRQ0003

1 SubscriptionRequest Issue datetime

The date/time when theCatalogue subscription requestmessage is issued.

SRQ0004

0..* SubscriptionRequestDescription text

To provide an general overalldescription for the SubscriptionRequest for catalogue

Use case: Can be used for thesubscribtion requester of a catalogueto describe content of subscribedcatalogue.

This description is not an alternative ofusing Product groups or Productclassification.

UBL e.g. Computer accessories forlaptops.

SRQ0005

1..1 CatalogueSubscriptionRequester

The requester of the cataloguesubscription

The requester of a cataloguesubscription and the receiver ofcatalogue

SRQ0006

1..1 CatalogueSubscriptionReceiver

The receiver of the cataloguesubscription request

The receiver of a cataloguesubscription request and the providerof a catalogue

SRQ0007

0..1 Procurement Party The party at the customer sideresponsible for negotiating thecontract and the contents of thecatalogue.

UBL

SRQ0008

0..n Supplier party Supplier (s) whose catalogue(s) is requested to besubscribed to

SRQ0009

0..n Contract Reference Reference to the Contract(s)the catalogue subscriptionrequest is subject of.

SRQ0010

0..n DocumentReference

Reference to other document(s) applicable for the catalogue

subscription

UBL

SRQ0011

0..n Signature To facilitate digital signing of thesubscription request

UBL

SRQ0012

0..1 SubscriptionCatalogue UpdateFrequency

Subscription request onfrequency of Catalogueupdates.

UN/CEFACT Code list to bereferenced

2 The short name of the business entity may be changed in the process of developing the Requirement Specification

Mapping (RSM),



32/75


UID Crd Short Name Business Requirement Rationale / Example / MappingNotes

SRQ0013

0..1 RequestedSubscription period

The requested period for thecatalogue subscription.

SRQ0014

0..n SubscriptionRequest Catalogue

Update Code

The code specifying thesubscription request on content

for update catalogues

Gives the Catalogue Providerinformation on how the Catalogue

Receiver (subscription requester)wants update catalogue (s) to bearranged.

Code list:

Full request a subscription of fullcatalogue including all updates

Partial request a subscription ofcatalogue update including only allupdated/changed catalogue items

Partial Price - subscription requestedof catalogue update including onlyprice changed catalogue items

Partial Item subscription requested

of catalogue update including onlycatalogue items with changed itemspecification

If more than one code is used in asubscription the Catalogue Receivermust use Catalogue Request torequest a specific update catalogueaccording to any of the specifiedupdate codes.

SRQ0015

0..n SubscriptionRequestedCatalogueLanguage Code

Subscription Request oflanguage(s) of Catalogueinformation

Code list: ISO 639

SRQ0016

0..n SubscriptionRequestedCatalogue CurrencyCode

Subscription Request ofCurrency or currencies of theprices, allowances and chargesin Catalogue

Code list: ISO 4217

SRQ0017

0..1 SubscriptionRequestedCatalogue ValidityPeriod

Subscription request on validityperiod for Catalogue for whichthe catalogue must be valid andready for use.

Result in only one issue of acatalogue if used.

SRQ0018

0..n SubscriptionRequested ProductClassificationScheme Code

Subscription request on productclassification scheme(s)(including version etc)requiredfor classifying the products in

the subscribed Catalogue

Code list (examples):

- UNSPSC

- GPC

- CPV

SRQ0019

0..n SubscriptionRequested ProductClassification Code

Requested Product group(s) tobe included in the Catalogue byusing Product ClassificationScheme(s)

Includes a code list of availableProduct Classification schemes



33/75



SRQ0020

0..n SubscriptionRequested PriceType Code

Price type(s) to include in theCatalogue

A code list containing differentprice types (examples)

- Contract price (net price) Priceaccording to contract, includingallowances and charges,excluding taxes

- Contract price (gross price)Price according to contract,excluding allowances andcharges and taxes

- Current (todays) price,contractual (net price) Priceaccording to contract, including

allowances and charges,excluding taxes. This price canvary from day to day during thecontract period. Price at time oftransaction according toagreement: E.g fresh food,flowers, spot price

- Discounted current (todays)price (net price), Price accordingto the suppliers price list orcatalogue including allowancesand charges, excluding taxes.This price can vary from day today during the period of time.Price at time of transactionaccording to agreement: E.g freshfood, flowers, spot price

- Catalogue price, discounted (netprice) Price according to thesupplier's price list or catalogue,including allowances andcharges, excluding taxes.

- Catalogue price, discounted(gross price) Price according tothe supplier's price list orcatalogue, excluding allowances,charges and taxes.



34/75



SRQ0021

0..n Requested TradingTerms

It must be possible to staterequested trading terms andconditions that apply to all tradeitems. Trading terms must be

possible to be given in textand/or as a reference to wherethe trading terms can be found(URL to national or industryspecific terms). Also the tradingterms can apply to specificapplicable regions/country.

UBL

SRQ0022

0..n SubscriptionRequested TargetMarket(s)

A geographical area, basedupon geographical boundariessanctioned by the UnitedNations, for items which shouldbe included in the subscribedcatalogue.

Code list: ISO 3166

SRQ

0023

0..n Subscription

Requested DeliveryRegion(s), text

A medium-scale area of land for

deliveries of items which shouldbe included in the subscribedcatalogue.

Only items which are delivered to the

requested region are to be included inthe subscribed catalogue

SRQ0024

0..n SubscriptionRequested DeliveryLocation(s)

A geographical location fordeliveries of items which shouldbe included in the subscribedcatalogue.

Only items which are delivered to thespecified location (s) are to beincluded in the catalogue.

1.7. Catalogue Request (Business Document)


CRQ

CRQ0001

1 Catalogue RequestIdentifier

The identifier of the CatalogueRequest

CRQ0002

0..n Signature To facilitate digital signing of thecatalogue request

CRQ0003

0..* Catalogue RequestDescription text

A general overall description forthe Catalogue Request in cleartext

Use case: Can be used for therequester to describe the requestedcontent of the catalogue.

This description is not an alternativeof using Product groups or Productclassification.

UBL e.g. Computer accessories for

laptops.

CRQ0004

1..1 Catalogue Receiver Receiver of the CatalogueInformation

CRQ0005

1..1 Catalogue Provider Provider of the catalogue



35/75



CRQ0006


UBL

CRQ0007

0..n Supplier party Supplier (s) whose catalogue (s)is to be provided.

CRQ0008

0..n Contract Reference Reference to the Contract(s) therequested Catalogue is subjectof.

CRQ0009

0..n DocumentReference

Reference to other document (s)applicable for the requestedcatalogue

UBL

CRQ0010

0..1 RequestedCatalogueReference

Reference to the Catalogue tobe updated

UBL

CRQ

0011

0..1 Requested

Catalogue UpdateCode

The code specifying the

requested content of the updatecatalogue

All updates are in comparison with

the most previous catalogue or incomparison to the referencedcatalogue to be updated.

Code list:

Full a full catalogue including allupdates must be provided

Partial only all the updated/changedCatalogue Items must be provided

Partial Price - only price changedcatalogue items must be provided

Partial Item only catalogue itemswith item specification changes must

be provided

CRQ0012

0..n RequestedCatalogueLanguage(s) Code

Requested Language(s) for therequested Catalogue

Code list:ISO 639

CRQ0013

0..1 RequestedCatalogue CurrencyCode

Requested Currency of theprices, allowances and chargesin the requested Catalogue

Code list: ISO 4217

CRQ0014

0..n Requested ProductClassificationScheme Code

The product classificationscheme(s) required forclassifying the products in therequested Catalogue

Code list

UNSPSC

CPV

GS1 GPC

CRQ0015 0..1 RequestedCatalogue ValidityPeriod

The period for which therequested Catalogue must bevalid and ready for use.

CRQ0016

0..n Requested ProductGroup(s)

Requested Product group(s) tobe included in the Catalogue byusing a Product ClassificationScheme



36/75



CRQ0017

0..n RequestedCatalogue itemidentification

Identification of the requestedCatalogue items to be includedin the Catalogue Information

CRQ

0018

0..n Requested Price

type code

Requested Price type(s) to

include in the CatalogueA code list containing differentprice types (examples)

- Contract price (net price) Priceaccording to contract, includingallowances and charges, excludingtaxes

- Contract price (gross price) Priceaccording to contract, excludingallowances and charges and taxes

- Current (todays) price, contractual(net price) Price according tocontract, including allowances andcharges, excluding taxes. This pricecan vary from day to day during the

contract period. Price at time oftransaction according to agreement:E.g fresh food, flowers, spot price

- Discounted current (todays) price(net price), Price according to thesuppliers price list or catalogueincluding allowances and charges,excluding taxes. This price can varyfrom day to day during the period oftime. Price at time of transactionaccording to agreement: E.g freshfood, flowers, spot price- Catalogue price, discounted (netprice) Price according to thesupplier's price list or catalogue,

including allowances and charges,excluding taxes.

- Catalogue price, discounted (grossprice) Price according to thesupplier's price list or catalogue,excluding allowances,charges andtaxes.

CRQ0019

0..1 Requested TradingTerms

It must be possible to staterequested trading terms andconditions that apply to all tradeitems. Trading terms must bepossible to be given in textand/or as a reference to wherethe trading terms can be found(URL to national or industryspecific terms). Also the tradingterms can apply to specificapplicable regions/country.

UBL



37/75



CRQ0020

0..n Requested TargetMarket

A requested geographical area,based upon geographicalboundaries sanctioned by theUnited Nations, for items which

should be included in therequested catalogue..

Code list: ISO 3166 (country codes)

CRQ0021

0..* Requested DeliveryRegion, text

A requested medium-scale areaof land for deliveries of items tobe included in the requestedCatalogue in clear text.

Only items which are delivered to therequested region are to be included inthe catalogue.

CRQ0022

0..n Requested DeliveryLocation

A requested geographicallocation for deliveries of items tobe included in the requestedCatalogue.

Only items which are delivered to thespecified location are to be includedin the catalogue.

1.8. Application Response (Business Document)


ARP

ARP0001


Generic document.

ARP0002

1..1 ApplicationResponse Identifier

The identifier of the ApplicationResponse

ARP0003

0..n Signature To facilitate digital signing of theapplication response

UBL

ARP0004

1..1 ApplicationResponse Code

The code for identifying theapplication response.

Code list:A the received document is rejected

B the received document isaccepted

ARP0005

1..1 ApplicationResponse Issuedate time

The date/time when theApplication Response is issued.

ARP0006

0..n Coded Reason forrejection

Coded reason for rejection. Applicable to use only when codevalue A in Application ResponseCode is used (rejections).

Code list to be provided

The use of the business term must beagreed by the business parties.

Agreement must be made if the

rejection applies at both businesslevel and technical level.

ARP0007

0..* Textual Reason forrejection

Reason for rejection in cleartext.

Applicable to use only when codevalue A, is used (rejections) andcoded reason for rejection not used.

The use of the business term must beagreed by the business parties.



38/75



ARP0008

1..1 RespondedBusiness DocumentReference

Reference to the respondedbusiness document

ARP

0009

1..1 Response Provider The party providing the

Application Response

ARP0010

1..1 Response Receiver The party receiving theApplication Response

ARP0011

0..n Response toreceived catalogueline

A response to a line in thereceived Catalogue

UBL

1.8.1. Response to received catalogue line (Application Response)


ARL

ARL0760

1..1 Line Reference Identifies the line in thereferenced document

NES UBL

ARL0761

1..1 Line ResponseCode

The code for identifying the lineresponse.

Code list::

Accepted

Rejected

NES UBL

ARL 0..1 Reason for rejectionof catalogue line,code

Coded Reason for rejection ofthe catalogue line

Code list?

ARL

0763

0..* Reason for rejection

of line, text

Reason for rejection of the line

in clear text.

NES UBL

1.9. Catalogue (Business Document)


CAT

CAT0001


Generic document.

CAT0002

1..1 Catalogue Identifier The identifier of the cataloguecollection assigned by theCatalogue Provider

CAT0003

0..1 Catalogue RequestReference

The reference to the request ofthe catalogue.

CAT0004

0..1 CatalogueSubscriptionReference

The reference to the cataloguesubscription.

CAT0005

0..* Description To provide an general overalldescription for the Catalogue

UBL e.g. Computer accessories forlaptops.



39/75



CAT0006

0..n Signature To facilitate digital signing of thecatalogue

UBL

CAT0007

0..1 Validity period The period in which thecatalogue or catalogue

collection is valid

Validity period at this header level canbe overridden at a lower level of the

catalogue (catalogue item level orproduct level)

CAT0008

1..1 Catalogue statuscode

Code giving the status of thecatalogue

Code list:

Original Initial catalogue

Replace - Catalogue replacing aprevious catalogue

Change - Catalogue containingchanged items compared to previous

catalogue

CAT0009

0..1 Catalogueupdate/replace,Reference

Reference to the updated orreplaced Catalogue

CAT0010

0..1 Price ListReference

A reference to the price list forthis catalogue

Reference to a price list at this headerlevel can be overridden at line level.A business rule must be made whenusing this business term concurrentlywith the price list reference at thelevel of Trade agreement.

CAT0011

0..1 Contract Reference A reference to business contractwhich the catalogue is basedupon.

UBLReference to contract at this headerlevel can be overridden at line level.

Must be possible to state the contractreference on header level in caseswhere it can not be stated on linelevel or where it must be mandatedthat only one contract can bereferenced for all lines. Must bepossible to give contract reference foreach supplier.

CAT0012

1..1 Catalogue Provider The Provider of the CatalogueInformation.

CAT0013

1..1 Catalogue Receiver The Receiver of the CatalogueInformation

CAT0014


UBL

CAT0015

0..1 Supplier Party Party who owns the item andconsigns or makes themavailable in trade



40/75



CAT0016

0..1 Delivery DatePeriod

The date period in whichcatalogue items may bedelivered

CAT

0017

0..1 Payment

Instructions

The payment instructions

applicable to the catalogue

CAT0018

0..1 Payment Terms The payment term applicable tothe catalogue

CAT0019

0..n Target market A geographical area based upongeographical boundariessanctioned by the UnitedNations, in which the trade itemsmentioned in the catalogue areavailable.

Target market at this header level canbe overridden at line level.

Code list: ISO-3166

CAT0020

0..* Delivery Region,text

A medium-scale area of land towhich the items mentioned inthe catalogue can be delivered.

Delivery region at this header levelcan be overridden at line level.

CAT0021

0..n Delivery Location A geographical location to whichthe items mentioned in thecatalogue can be delivered.

Delivery location at this header levelcan be overridden at line level

Catalogue detail level

CAT0022

0..1 Line Count Numeric The number of lines in thecatalogue

UBL has Items in Lines, the linescontaining the extrinsic iteminformation such as pricing.

CAT0023

1..n Catalogue Item The information of a catalogueitem.

1.9.1.1. Catalogue Item (Catalogue)


CAI

CAI0100

1..1 Catalogue ItemIdentification

The identification of thecatalogue item according to acataloguing system

A continuous number or a logical ID?Or an unambiguous global uniqueidentity?

UBL Catalogue Item Identification inItem

CAI0101

1..1 Catalogue itemaction code

The code specifying the actionvalid for the catalogue item

UBL Action Code in Catalogue Line

GS1

Code list:

- New (added) catalogue item- Updated catalogue item

- Replaced catalogue item

- Deleted catalogue item

CAI0125

0..1 Trade ItemGrouping Code

A code assigned by the supplieror manufacturer to logicallygroup trade items independentlyfrom classification systems.

GS1



41/75



CAI0126

0..1 Trade ItemGrouping Name

The corresponding name inclear text for the grouping codeof a trade item.

GS1

CAI

0102

0..1 Catalogue item

availability Code

Code indicating availability of

the Catalogue Item

UBL

Code list:new, available new and availablecatalogue item

new, not available new not availablecatalogue item, announcement only

deletion, announcement announcement for a future deletion ofa catalogue item

CAI0103

0..1 Catalogue ItemInformationProvider Party

The party who provides thecatalogue item information.

UBL

GS1

CAI

0104

0..1 Trade Item

Shipping Period

Indicates the date period the

catalogue item can be shipped.

GS1

CAI0105

0..1 Catalogue iteminformation Validityperiod

The period during which theinformation provided for thecatalogue item is valid.

UBL

GS1

CAI0106

0..1 Catalogue iteminformation Changelatest date time

The date time on which thecatalogue item data was lastchanged

GS1

CAI0107

0..n Multimediapresentation

Multimedia presentation of theitem (e.g. picture or drawing)

UBL

CAI0108

0..1 AdditionalInformation

Provides more details of theitem (e.g., the URL of arelevant web page).

UBL

CAI0109

0..* AdditionalInformation Note,text

Additional information in cleartext about the item not alreadygiven as structured informationTo be used as non-structuredinformation

UBL

Not GS1

CAI0110

0..* Keyword, text A text string or synonyms to beused for searching for thecatalogue item.

UBL

CAI0111

0..n Replacing

Catalogue item

References to catalogue itemsthat can replace or substitutethe catalogue Item

UBL

Not GS1

CAI0112

0..n Accessory Product Relation to accessories orattachments to the catalogueItem e.g. headphones to amobile phone

UBL

Not GS1

CAI0113

0..n Required Product Relation to a required product tothe Catalogue Item e.g. asubscription to a mobile phone

UBL

CAI0114

0..n ComplementaryProduct

Relation to products thatcompliments the Catalogue Iteme.g. coal for a barbecue

UBL



42/75



CAI0115

0..n Component Product Relation to components or partsto the product e.g. an inkcartridge for a printer

UBL

CAI

0116

0..n Additional Product

relation

Relationship to other products

other than replacing product,accessory product, requiredrelated product, complementaryproduct and componentproduct..

UBL

Not to be mistaken for hierarchyinformation.

CAI0118

0..1 Catalogue ItemReorderableIndicator

The indicator indicating that thecatalogue item may bereordered.

GS1

Indicators:

True, False

CAI0119

0..n Tracking SystemIdentifier

Identifies a system by which theproduct is being tracked

e.g UK National joint implant register

Code list of tracking systems to bedeveloped

CAI

0120

0..n Target market A geographical area based upon

geographical boundariessanctioned by the UnitedNations, in which the catalogueitems are available.

CAI0121

0..n Tax Information Information about all applicabletaxes for the catalogue item

If needed Tax information recurs pereach tax type (Tax Type Code).

CAI0122

0..1 Trade Agreement Information on tradeagreements

CAI0123

0..1 Trade Delivery Information on trade deliveries.

CAI0124

1..1 Product Information on the product(trade item).

1.9.1.2. Tax Information (Catalogue Item)


TXI

TXI0200

1..1 Tax Type Code The code indicating the type of tax

Examples of Tax Types:

- Alcohol tax

- Value added tax (VAT)

- Environmental tax

- Goods and services tax

- Coffee tax

Code list UN/CEFACT 5153

TXI0201

0..1 Tax TypeDescription

Description of tax type code. GS1



43/75


44/75



TAG0222

0..n Trading Terms It must be possible to statetrading terms and conditionsthat apply to all trade items.Trading terms must be possible

to be give in text and/or as areference to where the tradingterms can be found (URL tonational or industry specificterms). Also the trading termscan apply to specific applicableregions/country.

UBL

TAG0223

0..1 Contract Reference The reference to a Contract. Provides for multi supplier catalogue.

TAG0224

0..1 ContractSubdivision text

A text giving a subdivision of acontract or tender.

UBL

Examples "Installation", "Phase One",Support and Maintenance"

TAG0225

0..1 Price ContractReference

The reference to a contractspecifying the price conditions.

TAG0226

0..1 Customer SupportCentre - Party

The customer support centre forthe catalogue item.

GS1

TAG0227

0..1 Restrictedinformationindicator

The indicator to qualify thatcatalogue item information isrestricted to specific useaccording to agreement.

Indicators:

True, False

TAG0228

0..1 Product OrderingPeriod

The period of date the catalogueitem (product) can be ordered.

GS1

TAG0229

0..1 Product Exclusivityend date time

The date and time at which acatalogue item (product)no

longer is exclusive to the tradingpartner

GS1 special exclusivityagreements between brand owner

and a buyer (retailer)

TAG0230

0..1 Availability ToConsumer StartDate and Time

The first date/time the buyer isallowed to resell the catalogueitem (product).

GS1

TAG0231

0..1 Product FirstDelivery Date

The earliest date at which thesupplier can deliver thecatalogue item (product) to thetrading partner.

GS1

TAG0232

0..1 Minimum productlifespan from timeof arrival, Days

A number of days from thearrival date, guaranteed by themanufacturer, before theexpiration date of the product.

GS1

TAG0235

0..1 Orderable indicator The indicator identifying that thecatalogue item may be ordered

UBL

GS1

Indicators:

True, False

TAG0236

0..1 Made to OrderIndicator

Indicates that the item will onlybe produced when themanufacturer receives an order

Not GS1

Indicators:

True, False



45/75


46/75



TAG0247

0..* WarrantyInformation text

Warranty information text aboutthe catalogue item.

UBL

(GS1- used in GS1 XML extensionfor Hard Lines)

TAG0248 0..n Price information Price(s) information applied tothe product within tradeagreement

TAG0249

0..1 Delivery terms The entity contains the deliveryterms and if relevant the locationrelated to the delivery terms.

TAG0250

0..1 Marketing Marketing information about thecatalogue item

1.9.1.5. Price information (Trade agreement)


PRI

PRI0270

0..1 Price ListReference

A reference to the price list usedfor the pricing of the catalogueitem.

UBL

A business rule must be made whenusing this business term concurrentlywith the price list reference at thecatalogue header level.

PRI0271

0..1 Catalogue ItemPrice amount

The price amount for thecatalogue item

UBL



47/75



PRI0272

0..1 Price Amount TypeCode

The code for the Price Type ofthe price amount

UBL

Examples of Price types to include in codelist for Price type code :

- Suggested Retail Price

By the manufacturer suggested retail priceto consumer. Normally used to establish aproposed value for the trade item. May ormay not appear on the package.

- Contract price (net price) Price accordingto contract, including allowances andcharges, excluding taxes

- Contract price (gross price) Priceaccording to contract, excludingallowances and charges and taxes

- Current (todays) price, contractual (netprice) Price according to contract,including allowances and charges,excluding taxes. This price can vary fromday to day during the contract period.Price at time of transaction according to

agreement: E.g fresh food, flowers, spotprice products

- Discounted current (todays) price (netprice), Price according to the suppliersprice list or catalogue includingallowances and charges, excluding taxes.This price can vary from day to day duringthe period of time. Price at time oftransaction according to agreement: E.gfresh food, flowers, spot price products- Catalogue price, discounted (net price)Price according to the supplier's price listor catalogue, including allowances andcharges, excluding taxes.- Catalogue price, discounted (gross

price) Price according to the supplier's

price list or catalogue, excludingallowances, charges and taxes.

- Additional Price Another price typedifferent from coded price types

PRI0273

0..1 Additional PriceAmount Type Code

The code for an additional priceamount type for the item apartfrom qualified price types.

UBL

PRI0274

0..1 Price BasisQuantity

The quantity of the Item to whichthe applicable valid price applies

PRI0275

0..n Allowance Charge An association to charges anddiscounts for the Catalogue Item

UBL

PRI0276 0..* Price ChangeReason Text The reason for the pricechange expressed as text

UBL

PRI0278

0..n Validity Period forPrice

The period(s) for which theprice is valid

UBL

PRI0279

0..1 Bracket PriceQuantity Range

The quantity range (minimum,maximum) of the item for whichthe price is valid

Not GS1



48/75



PRI0280

0..n Price ValidityLocation

A delivery location(s) for whichthe price is valid.

UBL

PRI

0281

0..1 Price Comparison Information about details

for price comparison of theproduct

UBL

GS1

1.9.1.6. Price List Reference (Price information)


PLR

PLR0283

0..1 Price List Identifier The identifier for the Price List UBL

PLR0284

0..1 Validity Period The period(s) for which theprice list is valid

UBL

PLR0285

0..1 Immediate PreviousPrice ListReference

A reference to a immediateprevious Price List

UBL

1.9.1.7. Price Comparison (Price Information)


PRC

PRC0290

1..1 Comparison PriceAmount

The price for the comparisonquantity of the trade item in

respect to the price comparisontype (code)

UBL

PRC0291

1..1 Price ComparisonQuantity

The quantity used for pricecomparison with other items.

UBL

GS1



49/75



PRC0292

1..1 Price ComparisonType Code

Code indicating how pricecomparison is made. How tocalculate the comparative price.

GS1

Code list: GS1PriceComparisonContentTypeDRAINED_WEIGHT - The weight of

a product when all liquids used in thepackaging of the product have beenremoved.INCLUDING_ADDITIVES - Specifiedusing MLT or FZ as unitOfMeas-ure(price per litre/pint drink includingaddi-tives other than water). Foodservice.MILLILITRES_EXCLUDING_DEPOSIT - Specified using MLT asunitOfMeasure (price per litre, notincluding the package deposit charge)PER_CUBIC_METRE - The PriceComparison Content specified maybe used to calculate the price per

cubic metre.PER_DOSE - Specified using PCE asunit of measure.PER_KILOGRAM - Specified usingGRM as unitOfMeasure (price perkilogram).PER_LITRE - Specified using MLT asunitOfMeasure (price per litre).PER_LOAD - Specified using PCE asunit of measure (price per load - usedfor washing up powder).PER_METRE - Specified using MMTas unitOfMeasurePER_PIECE - Specified using PCEas unitOfMeasure (price per piece)PER_PINT - Specified using FZ asunitOfMeasure (price per pint)PER_POUND - Specified using OZas unitOfMeasure (price per pound)PER_SQUARE_METRE - The PriceComparison Content specified maybe used to calculate the price persquare metre.PER_WASH - Specified using PCEas unitOfMeasure (price per wash used for washing detergent).PER_YARD - Specified using IN asunitOfMeasure (price per yard)READY_TO_DRINK - Specified using

MLT or FZ as unitOfMeasure (priceper litre/pint diluted drink).READY_TO_EAT - Specified usingGRM or OZ as unitOfMeas-ure (priceper kilogram/pound prepared food).



50/75


1.9.1.8. Trade Delivery (Catalogue Item)


TDY

TDY

0300

0..1 Handling

Instructions

The specific instructions for

storage, transport or handling ofthe product.

TDY0301

0..1 Carrier Party The party which providestransport services.

TDY0302

0..n Production BatchIdentification

An identification of theproduction batch of the product.

TDY0303

01

ImportClassification CodeList Type Code

A code indicating the importclassification code list used forthe trade item.

GS1

Imports and exports of trade itemsrequire classification codes todetermine appropriate duties andtariffs.

Code list:

- CUSTOMS_TARIFF_NUMBER-HARMONIZED_COMMODITY_DESCRIPTION_AND_CODING_SYSTEM-HARMONIZED_TARIFF_SCHEDULE_OF_THE_US- INTRASTAT-INTRASTAT_COMBINED_NOMENCLATURE- NETHERLANDS

-TARIF_INTEGRE_DE_LA_COMMUNAUTE

TDY0304

0..1 ImportClassification Value

The used value from theaccording import classificationcode list for the trade item

GS1

1.9.1.9. Product (Catalogue Item)


PRO

PRO0312

1..1 ProductIdentification

The identification(s) for theproduct

UBL

GS1

(including Product. Identification,Global Identification, Seller AssignedIdentification, Buyer AssignedIdentification, Manufacturer AssignedIdentification, Industry AssignedIdentification)



51/75



PRO0318

0..n Official regulationscompliance code

A code that indicates that aproduct is in compliance withspecific applicable officialregulations

GS1

Code list: different code lists fordifferent kind of products

PRO0319

0..1 Consumer unitindicator

Indicator identifying the productas a consumer unit.

GS1

Indicators:

True, False

PRO0320

0..1 Despatch unitindicator

The indicator identifying that theproduct may serve as a dispatch(shipping) unit

GS1

Indicators:

True, False

PRO0321

0..1 Product LaunchCancellation date

The cancellation date of thelaunch of a product that wasnever and will never bemanufactured, but may havebeen presented to buyers.

GS1

PRO0322

0..1 Manufacturer Party The party who makes theproduct (not to imply a partywho simply provides packagingof the product)

UBL

PRO0323

0..1 Product rightsowner party

The party who owns the rights ofthe product

PRO0362

0..1 Minimum productlifespan from timeof production, Days

A number of days from theproduction date, guaranteed bythe manufacturer, before theexpiration date of the product

GS1

PRO0363

0..1 Opened ProductLifespan, Days

The number of days remainingfrom the time of break openingof the packaging of the product

until not good for consuming

GS1

(for retail - information about when

product to be removed from the shelf)

PRO0324

0..1 ProductDiscontinued date

The date on which the product isno longer produced.

GS1

PRO0325

0..1 Product Changelatest date time

The date time on which theproduct data was last changed

GS1

PRO0326

0..* Product Name Text The name of the product whichdistinguish it from other productsand if necessary to be used intrade messages such as orderand invoice.

UBL

PRO0327

0..* Product FunctionalDescription Text

A description of the use of theproduct.

GS1

PRO0328

0..* Product DescriptionShort Text

A short description of theproduct which can be used onshelf edge and on receipts.

GS1

PRO0329

0..1 Model Name The model name UBL



52/75



PRO0330

0..* Additional ProductDescription Text

An additional description of theproduct.

UBL

GS1

PRO0331

0..* Variant descriptionText

A description used to identify thevariant of the product. Variantsare the distinguishingcharacteristics that differentiateitems with the same brand andsize including such things as theparticular flavour, fragrance,taste.

GS1

PRO0332

0..1 Product BrandName

The brand name of the product UBL

GS1

PRO0333

0..1 Sub Brand Name Second level of brand name forthe product.

GS1 E.g. trademark. It is theprimary differentiating factor that a

brand owner wants to communicateto the consumer or buyer. E.g.Yummy-Cola Classic. In this exampleYummy-Cola is the brand name andClassic is the subBrand.

PRO0334

0..* Descriptive FormText

A description of the physicalform or shape of the product.Used, for example, inpharmaceutical industry toindicate the formulation of thetrade item. Defines the form thetrade item takes and is distinctfrom the form of the packaging.

Examples: paste, gel, powder

GS1

PRO0335

0..1 Product Quantity The quantity of the productcontained in the product (tradeitem) (incl measurement unitcode according to UN/ECErecommendation 20 /UN/CEFACT code list 6411)

GS1

UBL

PRO0336

0..1 Quantity Of ProductContained In InnerPack

Indicates the number of non-coded physical groupings (innerpacks) of next lower level tradeitems within the current level.

GS1

PRO

0337

0..1 Product Drained

Weight

The weight of the product of the

trade item when drained of itsliquid.

GS1

PRO0338

0..1 Trade Item VariableMeasure Indicator

Indicator identifying the tradeitem as a variable measuretrade item. The content of thetrade item vary about eitherweight, length or volume (orother)

GS1 - Boolean true/false



53/75



PRO0339

0..1 Country of originCode

The code for the country inwhich (where) the product hasbeen produced or manufactured

UBL

GS1

Code list: ISO 3166

PRO0340

0..1 Subdivision Countryof Origin code

A code for subdivision of countyrof origin (state, province orregion) in which the product hasbeen produced or manufactured

UBL

PRO0341

0..1 Country of assembly

The country where the productis assembled.

Code list: ISO 3166

PRO0342

0..1 Product ColourCode

A code for describing the colourof the product.

A code list is required to identify thecolour of the product. No ISOstandards exist. Each industry needsto determine which code agency it willuse (e.g NCS-natural color system)

Colour can also be specified by usingProperty

PRO0343

0..* Product ColourDescription

A clear text describing thecolour of the product.

Not to be used if code for colour isused

One occurrence for each language

Colour can also be specified by usingProperty

PRO0344

0..1 Product PrepackType Code

A code specifying if the contentof the product is pre-packed orcontains loose products.

E.g. a trade item containing plasticbags with apples is of the type "pre-packed". A trade item containingloose applesis of the type "loose".

GS1 code list

Code list:PRE-PACKED

LOOSEPRO0345

0..1 Customer Configurable Code

A code indicating that thecustomer may configure theitem

Code list: yes/no/not used

PRO0346

0..1 Recyclable typecode

A code specifying the recyclablesign marked on the product.

Code list for available recycleablesigns to be developed.

PRO0347

0..1 Product markedwith Serial numberIndicator

Indicate if a serial number ismarked on the product.

Not GS1

True/false

PRO0348

0..1 Security tag typeCode

A code indicating the type ofsecurity tag on the product

GS1

Code list:

Acousto-Magnetic

Electro-Magnetic

Ink or dye

Microwave

Radio Frequency.


8/6/2019 TBG1-BRSCrossI

Date post:	08-Apr-2018
Category:	Documents
Upload:	gracious-tasha
View:	219 times
Download:	0 times