| eventIdentifier | BusinessEventIdentifier | Individual parties should only use a single event identifier to identify a retraction.
Platforms providing services on behalf of both parties in a transaction may provide
event identifiers for both parties; in this case it is up to the recipient (the trade
repository) to validate that the event IDs refer to the same event.
| Business event identifier. | | 0-∞,
ncf | This is not used in messages to the repository. |
| report | Field must be replaced by one of next elments:
transfersAndExecution,
markToMarketValuation,
creditSupportAnnex,
depositReport,
| | | | 1-1 | |
| agreementDate | xsd:date | The date on which the change was agreed. | Change agreed date | | 0-1,
mre,
mfr | |
| executionDateTime | ExecutionDateTime | The date and time at which the negotiated change to the terms of the original contract
was agreed, such as via telephone or electronic trading system (i.e., agreement date/time).
| Time when change negotiation was confirmed | | 0-1,
ncf | This is not used in messages to the repository. |
| effectiveDate | xsd:date | The date on which the change become effective. | Amendment effective date | | 0-1,
mfr | |
| correctRegisteredInfo | xsd:boolean | | Correction of previously registered information | | 0-1,
mfr | |