Page Comparison

...

<referenceTransaction>
     <header>
          <batchKey>PRIMARY_ASSET_ID^PRIMARY_ASSET_ID_TYPE^UNDERLYING_TYPE</batchKey>
          <processingOptions>batchUnderlyingReinsertMode</processingOptions>
          <objectType>UnderlyingSMF</objectType>
     </header>
     <underlyingSMF>
          …
          <beginDate>2018-07-10</beginDate>
          <endDate>2018-07-12</endDate>
     </underlyingSMF>
     <underlyingSMF>
          …
          <beginDate>2019-07-11</beginDate>
          <endDate>2019-07-13</endDate>
     </underlyingSMF>
<referenceTransaction>

Underlying SMF records inside each referenceTransaction should be sorted by the timeline, first going with the earliest begindate/enddate, last - with the latest begindate/enddate. Date logic will remain the same as in usual underlying upload and will not allow time periods overlapping.

Since we have several ways to resolve security, batch Batch key can be set in various ways based on the final design. Suggested structures for batch key:

...

as XREF_ID^XREF_TYPE^UNDERLYING_TYPE

...

 , where XREF_ID and XREF_TYPE are identifiers that should be used for resolution

Batch key identifiers will be used to define records for DELETE during batchUnderlyingReinsertMode.

Batch Mode Load Process

...

batchUnderlyingReinsertMode

...

.