6 Maintenance

This chapter deals with data retention.

Data Retention

OCDS serves as a common, centralized, repository of the merchandising and pricing data required by Omnichannel applications. At any point, a downstream Omnichannel application should be able to ask OCDS for all data changes since a point in time. In addition, OCDS clients should be able to depend on OCDS to provide a complete snapshot of all Merchandising and Pricing data, if needed.

As Merchandising and Pricing data are added in the upstream source systems, records are added to OCDS's transactional table through BDI and/or RIB communication. When data has been deleted from the source system, OCDS continues to retain records with the state of the data marked as deleted so the "delete" event can be conveyed to OCDS clients.

Purging Deleted Data

OCDS has a built-in mechanism to purge deleted data, at an interval, after the data has been flagged "deleted" for a certain number of days. The OCDS purge mechanism is enabled by default, and can be configured to a retailer's business needs from the OCDS Job Admin UI.

Figure 6-1 OCDS Batch Job - System Options

Use the OCDS Job Admin System Options to view and edit the OCDS Purge property values.

Table 6-1 System Options

System Option Name	Description
OCDS_PURGE_ENABLED	Indicates if deleted data should be purged.
OCDS_PURGE_RETAIN_DELETED_DAYS	The number of days to retail deleted data. The number of days should be enough to be certain all Omnichannel applications have learned about any "deletes".
OCDS_PURGE_FREQUENCY_DAYS	The frequency, described in days, with which deletes are to be purged.