In some cases, it is useful to
recycle errors from previous runs so that they are added to the flow and
applied again to the target. This method can be useful for example when
receiving daily sales transactions that reference product IDs that may not
exist. Suppose that a sales record is rejected in the error table because the
referenced product ID does not exist in the product table. This happens during
the first run of the interface. In the meantime the missing product ID is
created by the data administrator. Therefore the rejected record becomes valid
and should be re-applied to the target during the next execution of the
interface.
This mechanism is implement IKMs by
an extra task that inserts all the rejected records of the previous executions
of this interface from the error table into integration table. This operation
is made prior to calling the CKM to check the data quality, and is conditioned
by a KM option usually called RECYCLE_ERRORS.
No comments:
Post a Comment