How to Use Event Generation to automate reporting updates to long Notional Schedules

If the Notional Amount Schedule related fields are required to be reported and the endpoint (TR, SDR, RRM) places limits on the length of these fields, meaning that the full length of schedule fields cannot be reported, this functionality limits the initial reporting to the allowed length of schedule and then automates the generation of required MODI messages to update the schedule once the end of the reported schedule is reached.

Once the counts exceed the allowed cardinality of the end point, then the system will report the schedule values for the supported counts and queue a submission to be processed on the effective date of schedules that have not been reported. 

The scheduling continues on the proceeding effective dates until all schedules are reported. For example, if the cardinality is 17 and a reportable trade is submitted with 20 schedules, then the system will report schedules 1-17 on the NEWT and queue a MODI for schedules 18-20 to be reported on the Effective date of the 18th schedule at approximately 1AM of the Jurisdiction's corresponding local time. This MODI message will have the same Ingestion ID as the NEWT. If there are many more Effective dates in a schedule, a MODI will be queued on every 18th Effective date to be reported.

The following conditions must be met for subsequent MODIs to automatically generate based on Notional Amount Schedule fields:
- The Notional Amount Schedule arrays contain more elements than the allowed cardinality of the end point
- The NEWT message is successfully Acknowledged by the end point
- KOR's "notionalScheduleIndicator" rule is configured to be "true"