You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
DD spec states that different parties should be informed about metering point metadata changes in case of ACTIVE and FUTURE agreements. At the moment there's no difference - also in case of FUTURE agreements DDs are generated as the agreements were ACTIVE.
This concerns REGULAR, BORDER and AGG metering points.
Steps to reproduce
Find or create a border metering point where customer is some other market participant.
add FUTURE border grid to customer
Change MP metadata such as resolution, save
Expected result
DDs are generated:
Only for CUSTOMER
Actual Result
DDs are generated for MP owner PP and customer PP (- these messages should NOT have been generated in case of future agreement
DD was not generated for the customer
Additional information:
Since this issue concerns all types of agreements that can start in the future, all of them are affected by this issue. Need to test also with GS/GRID/SUPPLY and AGG agreements.
The text was updated successfully, but these errors were encountered:
Problem
DD spec states that different parties should be informed about metering point metadata changes in case of ACTIVE and FUTURE agreements. At the moment there's no difference - also in case of FUTURE agreements DDs are generated as the agreements were ACTIVE.
This concerns REGULAR, BORDER and AGG metering points.
Steps to reproduce
Find or create a border metering point where customer is some other market participant.
Expected result
DDs are generated:
Actual Result
DDs are generated for MP owner PP and customer PP (- these messages should NOT have been generated in case of future agreement
DD was not generated for the customer
Additional information:
Since this issue concerns all types of agreements that can start in the future, all of them are affected by this issue. Need to test also with GS/GRID/SUPPLY and AGG agreements.
The text was updated successfully, but these errors were encountered: