Market Transaction Management - US Distribution
Market Transaction Management - US Distribution refers to functionality distributors can use to exchange standardized electronic business transactions in deregulated US distribution markets. The functionality supports the processing of Electronic Data Interchange (EDI) transactions that enable the distributor to communicate operational, customer, billing, enrollment, and service-related information with market participants in a consistent and reliable way.
This functionality (also referred to as "market transaction messaging") provides a common baseline architecture and transaction-processing framework that can be extended to support the specific rules, transaction sets, and validation requirements of individual deregulated distribution markets. The functionality provided is a framework on which specific market implementations can be based. The business objects and algorithms represent a generic "root" and "lowest common denominator" implementation, meaning they serve as the basis upon which a market-specific versions of those objects and algorithms can be created. For example, market-specific versions of the business objects and algorithms used for a PJM implementation of a market invoice (810) transaction would differ from those used for an ERCOT implementation, even though they would be based on the same root objects.
Note:
The US Distribution market transaction messaging functionality is intended for use specifically by distributors working in a deregulated market within the United States.
This documentation assumes readers have a basic understanding the market transaction messaging business process, including understanding Electronic Data Interchange (EDI) transactions, different types of market transactions, and the different types of market participants in a deregulated market.
It is CRITICAL that you have a firm understanding of how your market operates before you begin planning your implementation. This includes, but is not limited to, details concerning the types of market participants involved, the billing relationship between the distributor and other market participants, and the types and formats of the market messages the distributor will send to and/or receive from other market participants.
Objects provided with MTM are prefixed with "U2". The business objects provided are intended to serve as parent business objects for market-specific versions. None of the business objects provided can be instantiated.
Note that the information provided in this is not sufficient for configuring any specific market. Use of this functionality requires implementers and users have an understanding of their own market.