[Accessibility conventions are described at the bottom of the page]
*** This is a free preview excerpt of a commercial publication. ***

2. Parties, document types and profiles
[> 3.][< 1.4.2][^^^]
2.0 Participants and document flows
[> 3.][< 2.][^^][^^^]
Typically two or more trading partners agree to engage in a business transaction
[[1] - the initial UBL 2 scope is in two areas
[[2] - procurement of goods or services
 [2] - transport of goods
]]
A given business transaction may involve a number of participants (parties)
[[1] - individual, a group, or a body having a role in a business function
 [1] - a single party may play a number of different roles in a given business transaction
 [1] - all of the roles in the UBL scenarios are representative and need not actually be realized as real people or parties
]
Contexts defined for 21 roles involved in 31 document types being exchanged
[[1] - most document exchanges involve two parties
 [1] - some document exchanges involve multiple parties
 [1] - some roles are not involved in sending and receiving documents
]
Documentary scenario use case diagram outlines the roles of the many participants:
[[1] - the following image is a compressed version of the image found in the specification
[[2] - under "UBL 2.0 Context of Use" ([4.]); view it directly to see the detail
]]
[Figure 2.1: Use case diagram of all participants
The image is copied verbatim from the image in section [4.] of the specification.
23 stick figures with various labels of their roles in the process are connected with lines to 20 ovals labeled with business processes such as "sourcing", "fulfillment", "billing", etc.
The diagram overviews the prose and content found in section [4.] of the specification.
]
A given business transaction may involve a number of document exchanges
[[1] - exchanges are choreographed in a UBL scenario as only an example exchange of documents for documentary purposes to illustrate their use
 [1] - UBL does not require trading partners to engage in any particular exchange of documents
 [1] - communities and users of UBL can create their own scenarios using documents of the various document types
 [1] - communicating and negotiating the requirements for document exchanges are not part of UBL
[[2] - e.g. could be implemented by ebCPP/A partner agreements
]]
Communities of users are creating "profiles" of choreography of documents for different scenarios
[[1] - a scenario describes the objective of the interchange of documents
 [1] - the profile fulfills the scenario by describing a particular choreography of a subset of documents
 [1] - the same document can be used differently in different profiles
 [1] - the community could also customize a UBL document in different ways for each of the profiles they define
[[2] - different constructs have applicability in different scenarios
][1] - a hierarchy of profile identity:
[[2] - UBLVersionID - version of UBL
[[3] - e.g. "2.0", "2.1", etc.
][2] - CustomizationID - customization of a particular UBL version
[[3] - e.g. community
][2] - ProfileID - profile within a particular customization
[[3] - e.g. business process
][2] - each specific document type is customized for the profile
[[3] - there may be different document type customizations for different profiles within the same customization
]]]
Benefits can be realized by implementing only a single document
[[1] - e.g. Denmark realized millions of euros in savings implementing (and legislating) only Invoice and no other document types
[[2] - the Danish government already moving to support (and legislate) other document types
]]
Each document exchange is documented in the specification with sample workflows using activity diagrams:
[[1] - the vertical "columns" of activity diagrams are colloquially referred to as "swim lanes"
 [1] - document types are depicted in square-cornered boxes with underscored labels
 [1] - actions are depicted in round-cornered boxes
 [1] - the start of the process is the solid-filled circle
 [1] - the end of the process is the hollow-filled circle
]
Example workflow activity diagram for quotations excerpted from UBL documentation:
[[1] - excerpted from the specification section [4.3.2.]
]
[Figure 2.2: Sample workflow
The activity diagram shows the start of flow under "Originator or Buyer Party" swim lane, performing the "Send request for quotation" activity. This transfers the "Request for Quotation" document to the "Receive request for quotation" in the "Seller Party" swim lane. The flow continues in that lane to the "Send quotation" activity which transfers the "Quotation" document back to the "Receive quotation" activity in the "Originator or Buyer Party" lane, at which point the flow ends.
]
Find all diagrams in the UBL main documentation file under section [4.]

*** This is a free preview excerpt of a commercial publication. ***

This is an accessible version of Crane's commercial training material. The content has been specifically designed to assist screen reader software in viewing the entire textual content. Figures are replaced with text narratives.

Navigation hints are in square brackets:
[Tx.x] and [Fx.x] are textual representations of the applicability icons;
[digit] indicates list depth for nested lists;
[link [URL]] indicates the URL of a hyperlink if different than link;
[EXAMPLE] indicates an example listing of code;
[FIGURE] indicates the presence of a figure replaced by its description;
[>] jumps forward;
[<] jumps backward;
[^] jumps to start of the section;
[^^] jumps to the start of the chapter;
[^^^] jumps to the table of contents.
Suggestions for improvement are welcome: [info@CraneSoftwrights.com]
Book sales: [http://www.CraneSoftwrights.com/links/trn-acc.htm]
Information: [http://www.CraneSoftwrights.com/links/info-acc.htm]
This content is protected by copyright and, as there are no means to protect this accessible version from plagiarism, please do not make any commercial edition available to others.

+//ISBN 1-894049::CSL::Presentation::UBL//DOCUMENT Practical Universal Business Language Deployment 2009-02-12 13:50UTC//EN
Practical Universal Business Language Deployment
Third Edition - 2009-02-12
ISBN 978-1-894049-23-8
Copyright © Crane Softwrights Ltd.