Template:M summ EUA Annex (c): Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) Created page with "The mechanism allows a single {{euaprov|Confirmation}} with {{euaprov|Multiple Delivery Dates}} to operate as a series of discrete {{euaprov|Transactions}}, each with its own separate {{euaprov|Delivery Date}}. As to the precise consequence, or intended consequence they were driving at: perhaps seeing as {{euaprov|Disruption}}s tend to be {{euaprov|Delivery Date}}-dependent, should there be a {{euaprov|Suspension Event}} or some such thing on ''one'' {{euaprov|Deliver..." |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
The mechanism allows a single {{euaprov|Confirmation}} with {{euaprov|Multiple Delivery Dates}} to operate as a series of discrete {{euaprov|Transactions}}, each with its own separate {{euaprov|Delivery Date}}. | [[Multiple Delivery Dates - Emissions Annex Provision|The]] mechanism allows a single {{euaprov|Confirmation}} with {{euaprov|Multiple Delivery Dates}} to operate as a series of discrete {{euaprov|Transactions}}, each with its own separate {{euaprov|Delivery Date}}. | ||
As to the precise consequence, or intended consequence they were driving at: perhaps seeing as {{euaprov|Disruption}}s tend to be {{euaprov|Delivery Date}}-dependent, should there be a {{euaprov|Suspension Event}} or some such thing on ''one'' {{euaprov|Delivery Date}}, that is unresolved and, God forbid, graduates into a {{euaprov|Continuing Suspension Event}} or a “{{euaprov|then I woke up and it was all a dream}}” Event, it only cancels scheduled deliveries and payments on that part of the multi-{{euaprov|Delivery Date}} {{euaprov|Transaction}} that is actually affected, so each of the other micro-Transactions can carry on unaffected. | As to the precise consequence, or intended consequence they were driving at: perhaps seeing as {{euaprov|Disruption}}s tend to be {{euaprov|Delivery Date}}-dependent, should there be a {{euaprov|Suspension Event}} or some such thing on ''one'' {{euaprov|Delivery Date}}, that is unresolved and, God forbid, graduates into a {{euaprov|Continuing Suspension Event}} or a “{{euaprov|then I woke up and it was all a dream}}” Event, it only cancels scheduled deliveries and payments on that part of the multi-{{euaprov|Delivery Date}} {{euaprov|Transaction}} that is actually affected, so each of the other micro-Transactions can carry on unaffected. | ||
Latest revision as of 15:24, 6 November 2023
The mechanism allows a single Confirmation with Multiple Delivery Dates to operate as a series of discrete Transactions, each with its own separate Delivery Date.
As to the precise consequence, or intended consequence they were driving at: perhaps seeing as Disruptions tend to be Delivery Date-dependent, should there be a Suspension Event or some such thing on one Delivery Date, that is unresolved and, God forbid, graduates into a Continuing Suspension Event or a “then I woke up and it was all a dream” Event, it only cancels scheduled deliveries and payments on that part of the multi-Delivery Date Transaction that is actually affected, so each of the other micro-Transactions can carry on unaffected.