Change reason codes

Change Reason Codes govern the population of data in a Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS.. All Change Requests require a Change Reason Code A code that identifies a type of Change Request. It defines rules such as what NMI information can be updated and which roles will receive a Change Request Notification each time the Change Request Status is updated.:

You can find a list of Change Reason Codes in the MSATS Web Portal > Administration > Codes Maintenance > Change Reason Codes

• Identifying the type of Transaction See Relevant Rules or Procedures (for example, Change of Retailer See Relevant Rules or Procedures, Creation of a NMI See Relevant Rules or Procedures, and so on)
• Defining the reason for the Transaction.

For specific requirements for each Change Reason Code, see CATS Procedure Principles and Obligations.

For any Change Reason Code, some elements are defined globally. For example, they apply in all Jurisdictions. While others are defined separately for each Jurisdiction participating jurisdiction (defined in the NER).

Change Reason Codes are separated into groups of events and contain rules specifying:

• Which participant(s) must provide the data and when.

• Which data must exist in the NMI Master Record The NMI master record with an end date set to the year 9999. before the Change Request The way information is returned from an API. In a request, the client provides a resource URL with the proper authorization to an API server. The API returns a response with the information requested. can complete.

Change reason code parameters

Each Change Reason Code has the following parameters:

1. The participants permitted to initiate a Change Request.

2. The data items in the Change Request.

3. The data that must already be present in MSATS before the Change Request can complete.

4. Whether another participant must supply the exact date of the change. For example, is the MDP required to supply the date of the Actual Meter Reading to Complete the Change Request.

5. The date range window.

6. The Roles notified of a Change Request each stage they are notified.

7. The Objection Logging Period.

8. The Objection Clearing Period.

9. The participants who can Object to Change Request and the basis for Objection.

Change reason code rules

The Change Reason Codes control the following information:

Controls	Rule
The role / role status that can initiate the CR	CR Initiation
Whether it is retrospective	Jurisdictional
The number of days into the past or future when the change can be made	Jurisdictional
The number of days allowed for objections	Jurisdictional
The number of days after when an objected to CR is cancelled	Jurisdictional
The valid Objection codes (by NMI classification / Role and Role Status)	Objection
The mandatory and optional data provided by the Initiating participant	Field Validation
The mandatory and optional data provided by another party (e.g. LNSP or MDP) before the change can complete	Field Validation
Which parties are notified during each stage of the CR lifecycle	Notification

 

Address information

For certain Change Reason Codes, participants must provide mandatory or optional items associated with address information.