C_SOURCE_CDC
The C_SOURCE_CDC
table is used for changed data capture (CDC) parameters for the integrations between
the Retail Insights data warehouse and the Planning application schemas. In general, this table is updated automatically as
batches are run. However, it is important to know when you may need to modify these values.
For most interfaces, the table will initially have no records. The first time an integration batch program runs, it will
take all the data from the source table and move it to the export table. It will then create a C_SOURCE_CDC
record for the target table name, with a value for LAST_MIN_DATE
and LAST_MAX_DATE
matching
the timeframe extracted. On the next run, it will look at LAST_MAX_DATE
as the new minimum extract date and
pulls data greater than that date from the source table. If you are performing history loads for tables, such as Sales Transactions,
you may need to change these dates if you have to re-send data to Planning for past periods.
Specifically for positional data (at this time only Inventory Position), the usage is not quite the same. Positional data
will always send the current end-of-week values to Planning, it does not look at historical weeks as part of the normal batch
process. A separate historical inventory integration program is provided in an ad hoc process, which will allow you to send
a range of weeks where LAST_MIN_DATE
is the start of the history you wish to send, and LAST_MAX_DATE
is the final date of history before normal batches take it forward. It is common to load inventory from end to end in isolation
as it is a data-intensive and time-consuming process to gather, load, and validate inventory positions for multiple years
of history.