XML Standards > Message
 
Message Description
 

PURCHASE CONDITIONS v. 2.1
Problem Statement
Purchase Conditions express the official commitment between buyer and seller that certain quantities are to be delivered over a given period and at the stated price. In doing so it sets the contractual conditions for the ordering and delivering of the goods and so details specific terms and conditions that apply for a given period.
 
The Purchase Conditions does not intend to contain the totality of the contractual information, but to provide the relevant data in order to be able to align key conditions in an automated way.
 
The Purchase Conditions message supports multiple scenarios:
  • Fixed quantity and fixed period
  • Fixed quantity and variable period
  • Variable quantity and fixed period

To supply the detail design of the (specific) business transaction needed to meet the requirements of the referenced BRAD(s).
Audience
  • Manufacturers
  • Suppliers
Business Context
Industry: All
Geopolitical: Global
Product: All
Process: Plan
Official Constraints: None
Roles: Buyer, Seller
 System Capabilities: EANCOM, XML

Business Transaction View
Business Transaction PURCHASE CONDITIONS
Business Transaction Use Case Diagram
Use Case Diagram

Figure 1 – Use Case Diagram: Business Transaction
Use Case Description
Use Case ID BTP8
Use Case Name Purchase Conditions
Use Case Description The Purchase Conditions sets the contractual conditions for the ordering and delivering of the goods and so details specific terms and conditions that apply for a given period. While both parties need to agree on Purchase Conditions data, it is understood that only one party, i.e. the buyer or seller, will send the Purchase Conditions message and that the information flow will be in one direction only in order to ensure alignment.
Actors (Goal) Buyer: to align Purchase Conditions with the seller.
Seller: to align Purchase Conditions with the buyer.
Performance Goals  
Preconditions Integration agreement is in place
Item data are aligned
Post conditions Purchase conditions are communicated
Scenario Begins when:
The buyer generates the purchase conditions message
Continues with:
Step # Actor Activity Step
1.      Buyer Sends Purchase Conditions message to the Seller.
2.      Seller Receives Purchase Conditions Message
Ends when: the seller has received the purchase conditions message
Alternative Scenario
Step # Actor Activity Step
1.              Seller Sends Purchase Conditions message to the Buyer.
2.              Buyer Receives Purchase Conditions Message
Business Transaction Rules
N/A

Business Transaction Activity Diagram
Not Available
Business Transaction Activity Diagram
Not Available
Business Document Example
Code Lists
Backward Compatibility Assessment
Stop Gap Report
 
Date of Publication: June 2007
Copyright © GS1 Global Office 2007. All rights reserved