|
BASIC PARTY SYNCHRONISATION v. 2.1 |
|
|
|
|
|
Problem
Statement |
|
|
Substantial
effort has been made to develop a Global Data Synchronisation process because
master data sharing between partners is both complex and fundamental to all supply
chain processes. Integrity and timeliness of master data is critical to the
flow of goods, services and information throughout the chain. Sharing data
effectively and efficiently relies on access to common data definitions, data
accuracy and agreement on the processes used to exchange data. This process is
termed Master Data Synchronisation.
The salient points for
synchronisation are:
- synchronisation is a process
- it is auditable
- the process must utilize EAN·UCC
industry standards
- the data exchanged must be
compliant with these standards
- the recipient must
acknowledge the integration of the data
- continuous updates must be
applied
Party
information is a part of Master Data. Trading Partner’s involved with the Global Data Synchronisation Network
(GDSN) require data regarding party (GLN) information to determine the unique
identification, the role definition, the business process capability and the
message capability required to function in the network defined to achieve
Master Data Synchronisation.Due to the complexities of full Party
Synchronisation, there is a requirement to create an initial Basic Party
Synchronisation process. The process requirements for basic party
synchronisation within the Global Data Synchronisation Network should include:
- Load and Update Party Data within the Global
Registry
- Manage Party Data in the Global Registry
- Distribute Party Data
The data requirements for synchronisation of
Party information within the Global Data Synchronisation Network should
include:
- GLN as mandatory choice for Party Identification
- At least one role of Party as mandatory, allowing additional roles
- At least one business process identification (party role) and one
Message Identification used to define the capability of the party
|
|
|
Objective |
|
|
To
supply the detail design of the (specific) business transaction needed to meet
the requirements specified in the BRAD for Align_Basic Party Sync. To populate
the GS1 Global Registry and report to data pools and their registered trading
partners up to date data source party information.
|
|
|
Audience |
|
|
The audience of this standard is any
participant in the global supply chain.
This includes retailers, manufacturers, service providers and other
third parties.
|
|
|
Business
Context |
|
|
Industry: All
Geopolitical: All
Product: All
Process: Align_Basic Party Synchronisation
System
Capabilities: EAN.UCC
Official
Constraints: None |
|
|
Business
Transaction View |
|
|
Use Case Overview |
|
|
|
|
|
Use Case Description for
Register Party |
|
|
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Register Party
|
|
Use
Case Description
|
Prior to registration, the party data must pass validations at the
data pool and a uniqueness check at the Registry. The Global Registry ensures that valid,
unique party data is available within the Global Data Synchronisation Network
and that all valid GDSN parties must be registered in the Global Registry.
This Use Case describes the registration process that is performed by the
Global Registry.
|
|
Actors (Goal)
|
Data Pool (Source Data Pool or Recipient Data Pool)
Global Registry (GR)
|
|
Performance Goals
|
Data Pool: To have validated, registered Party data.
Global Registry: To ensure
valid, unique Party data is registered.
|
|
Preconditions
|
The data pool is a certified. The data pool has a profile that resides in the registry.
|
|
Post conditions
|
The party data has been registered and retained by the Global
Registry.
|
|
Scenario
|
Begins when. the Global
Registry receives validated Party Data from a data pool.
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
GR
|
ensures that the data
pool is certified
|
|
2
|
GR
|
verifies
the uniqueness of the GLN.
|
|
3
|
GR
|
stores
the party data
|
Ends when... The Global
Registry sends a registration response to the data pool.
|
|
Alternative Scenario
|
ad 1.
Data Pool not certified:
1.1. The GR sends an error
message to the data pool
1.2. Ends when, the data
pool receives the error message.
ad 2 The party already exists in the GR:
2.1 GR sends an
error message to the data pool.
2.2 The data pool
receives the error message.
2.3 Ends when,
the data pool receives the error message.
|
|
Related Requirements
|
N/A
|
|
Related Rules
|
|
1
|
The secondaryGovernmentArea (e.g. State, Province, Department) must
be populated in the Party Name and Address if the country associated with
the address has a secondaryGovernmentArea.
|
|
2
|
The data pool
submitting the Basic Party Registration message populates the isPartyActive
flag in the GR through the Basic Party Registration message.
|
|
|
|
|
|
|
|
Business Transaction Sequence
Diagram for
Register Party
|
|
|
 |
|
|
Business Transaction Use Case
Diagram for Change Registered Party
|
|
|
|
|
|
Use Case Definition Change Registered Party
|
|
|
|
Use Case ID
|
UC-2
|
|
Use Case Name
|
Change Registered Party
|
|
Use
Case Description
|
In the event that party data changes in a data pool, the changes must
be reflected in the Global Registry.
|
|
Actors (Goal)
|
Data Pool (Source
Data Pool or Recipient Data Pool)
Global Registry (GR)
|
|
Performance Goals
|
Data Pool: To have
validated, registered Party data.
Global Registry: To ensure valid, unique Party data
is registered.
|
|
Preconditions
|
The data pool is certified.
The data pool has a profile that resides in the registry. The data pool has received a “Change
Registered Party” message from their trading partner. The data pool has validated party data
received and has sent that Party data to the Global Registry. The Party data has been previously
registered.
|
|
Post conditions
|
The party data changes have been applied and retained in the Global
Registry.
|
|
Scenario
|
Begins when. the Global
Registry receives a validated Change Registered Party message from a data
pool.
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
GR
|
ensures
that the data pool is certified.
|
|
2
|
GR
|
validates
the party data from the data pool.
|
|
3
|
GR
|
ensures that the party data already exists in the Global Registry and
that the transmittingParty (GLN) of the Basic Party Registration Change
equals the partyDataPool GLN on the party record in the Global Registry.
|
|
4
|
GR
|
updates
the party data.
|
Ends when... The Global
Registry sends a registration response to the data pool.
|
|
Alternative Scenario
|
ad 1.
Data Pool not certified:
1.1. The GR sends an error message to the data
pool.
Ends when, the data pool receives the error message
ad 2. The
Party data does not exist in the GR:
GR sends an error
message to the data pool
Ends when, the data pool receives the error message
|
|
Related Requirements
|
N/A
|
|
Related Rules
|
|
1
|
The
transmittingParty (GLN) of the Basic Party Registration Change equals the
partyDataPool GLN on the party record in the Global Registry.
|
|
2
|
The
informationProviderOfParty GLN cannot be changed through a Change
Registered Party message.
|
|
|
|
|
|
|
|
Sequence Diagram Change Registered Party |
|
|
 |
|
|
Structured Business Scenario for Distribute Party Data from GR to
Data Pool
|
|
|
|
|
|
Use Case Definition for Distribute Party Data from GR to Data Pool |
|
|
 |
|
|
|
Use Case ID
|
UC-4
|
|
Use Case Name
|
Distribute Party Information
|
|
Use
Case Description
|
This use case describes the process of sending party information from
the Global Registry to the data pool (DP)
|
|
Actors (Goal)
|
Data Pool (Source Data Pool or Recipient Data Pool)
Global Registry (GR)
|
|
Performance Goals
|
Data Pool: To receive updated and validated party data from the
Global Registry.
Global Registry: To send
updated, validated and registered party data.
|
|
Preconditions
|
|
|
Post conditions
|
Data Pool has received Party Data.
|
|
Scenario
|
Begins when.the GR sends party data to DP via AS2.
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
DP
|
receives
the party data.
|
Ends when...the data pool filters the Party Data to validate Party Data.
|
|
Alternative Scenario
|
|
|
Related Requirements
|
N/A
|
|
Related Rules
|
N/A
|
|
|
|
|
|
|
|
|
|
TOP |
|
|
|
|
|
Code lists |
|
|
Glossary of Terms |
|
|
Test Data |
|