When rate table data is published via the application's APIs, the system creates, updates or removes stored CER Rule Objects as appropriate. The exact data written is configured via the CER Rule Object Propagators. See "Understanding Rule Object Propagators and Converters" in the Inside Cúram Eligibility and Entitlement Using Cúram Express Rules guide for further details.
In contrast, there may be situations where the rate data on a production system is created, modified or removed outside of application's APIs, in particular, the initial bulk population of business data via the use of SQL scripts to insert large volumes of data. Under these circumstances, no CER Rule Objects will be stored and the system will not yet be in a usable state.
The application includes a batch program to create CER Rule Objects for rate data which was inserted into a system outside of the application's APIs. You must run this program so that any functionality that relies on CER use of this data will operate correctly.
If you choose to populate your production data in a series of migrations, then you must run the batch program each time you create new production data. The batch program will only take action for newly-populated data and will automatically ignore existing data which has been processed by a previous run of the batch program.