Implementing WebSphere Business Integration Express for Item Synchronization

Chapter 1. UCCnet 17

Mandatory element, containing GLN and name of brand owner.

򐂰 dataPool

򐂰 catalogueItemClassification

Mandatory element, for example a UDEX classification.

򐂰 itemDescription

brandName, descriptionShort, additionalItemDescription.

򐂰 isTradeItemInformationPrivate

Controls whether an item is visible to the public or to subscribers only

򐂰 productType

Case, display, pallet, etc.

򐂰 eanuccType and eanuccCode

Case code number (UN), UPC-12, EAN.UCC-13...).

򐂰 unitIndicator

isTradeItemAConsumerUnit

isTradeItemAnOrderableUnit

򐂰 effectiveDate

򐂰 Measurements

quantityOfNextLowerLevelTradeItem

netContent (and unitOfMeasure)

height, width, depth (and unitOfMeasure)

netWeight, grossWeight (and unitOfMeasure)

volume (and unitofMeasure)

1.8 End-to-End flow

Finally for our UCCnet overview, we see the end-to-end flow for the

item-synchronization process from the UCCnet perspective.

For this flow, we assume that both supplier and retailer are using schema

processing, as shown in Figure 1-4 on page 18.

18 Implementing WebSphere BI Express for Item Synchronization

Figure 1-4 RCIR: Item registration

1. The supplier sends a correctly-formatted RCIR message to UCCnet that

includes the key values of GTIN/GLN/TM.

2. The message is received and validated by UCCnet through its validation

engine. Then, the valid item data is added to the registry.

3. A RCIR Response message is sent to the supplier with the outcome of the

RCIR from Step One. See Figure 1-5 on page 19.

RCIR

GTIN/GLN/TM

35 attrs

Data validation

Data provider

Supplier

UCCnet

GLOBALregistry

registration response

1

3

2

Chapter 1. UCCnet 19

Figure 1-5 Catalogue Item Notification

1. After the item has been added to the GLOBALregistry, one or more Catalogue

Item Notification (CIN) messages are sent to UCCnet. Each of these

messages contains the GLN of the subscribing retailer and the item details

such as GTIN and UDEX category.

2. At UCCnet the router will verify that the item exists with the GLOBALregistry.

3. The retailers whose GLN is in the CIN from the supplier will be forwarded a

CIN from UCCnet.

4. A CIN Response message will be sent from UCCnet to notify that the CIN has

been sent to the recipients. See Figure 1-5.

Important: Only GTINs that have been successfully added to the

GLOBALregistry and RCIR are eligible for Catalogue Item processing.

CIN

GTIN/GLN/TM

151 attrs

list of GLNs

UCCnet

Router

Data provider

Supplier

UCCnet

GLOBALregistry

notification response

Recipient

Worklists

recipients need to subscribe to

GTIN, Category or GLN/Category

CIN

verify

existance

1

3

2

4

1-n

20 Implementing WebSphere BI Express for Item Synchronization

Figure 1-6 Catalogue Item confirmation

1. When a recipient organization (the retailer) has taken action with the item

data that was sent in the CIN, it will send a Catalogue Item Confirmation (CIC)

to UCCnet to indicate the status of the processing of that item.

Statuses may be any of the following:

򐂰 Review

The addition of the item is currently being reviewed by the retailer.

򐂰 Accepted

The item has been accepted by the retailer but has not yet been

synchronized.

򐂰 Synchronised

The item has been accepted by the retailer and will be synchronized in their

systems.

򐂰 Rejected

The item is rejected and no further information is required.

CIC

Status:

Accept, Synchronise

Reject, Review

UCCnet

Router

Data provider

Supplier

UCCnet

GLOBALregistry

CIC

Status

Data Recipient

Retailer

2

1

3

4