Significance of Pre-Built Flag

While defining a Rule, you can make use of Pre Built Flag to fasten the Rule execution process by making use of pre-compiled technical metadata details. The purpose of Pre Built Flag is to enhance the Rule execution process bypassing the need to search for the required technical metadata within multiple database tables.

Table 10-15 Conditions and its Process flow

Condition	Process flow
Creating Rule:	Rule definition with Pre-Built Flag set to “Y” > Build the Rule query.
	Rule definition with Pre-Built Flag set to “N” > Do not build the Rule query during Rule Save.
Executing Rule:	Pre-Built Flag set to “Y” > Retrieve the rule query from the appropriate table and execute.
	Pre-Built Flag set to “N” > Build the Rule query by referencing the related metadata tables and then execute.

For example, consider a scenario where Rule 1 (RWA calculation), using a Dataset DS1 is to be executed. If the Pre-Built Flag condition is set to “N”, then the metadata details of From Clause and Filter Clause of DS1 are searched through the database to form the query. Whereas, when the Pre-Built Flag condition is set to “Y”, then the From Clause and Filter Clause details are retrieved from the appropriate table to form the query and thereby triggered for execution.

Like Dataset, pre-compiled rules also exist for other Business Metadata objects such as Measures, Business Processors, Hierarchies, and so on.

Note the following:

When you are sure that the Rule definition is not modified in a specific environment (production), you can set the flag for all Rule definitions as “Y”. This would in turn help in performance improvement during Rule execution. However, if the Rule is migrated to a different environment and if there is a change in the query, change the status back to “N” and also may need to resave the Rule, since there could be a change in metadata.