The purpose of using Bricks in Veeva CRM is to report on sales data for individual accounts. Since individual accounts can't be reported on, the Bricks are formed to report the sales data.
Brick-based alignments are directly aligned by the brick code (Brick_vod__c) field under the address object, while the address is linked to an account and to a territory. Brick-based alignments work like the Zip-to-Terr functionality and even use the Territory Utilities to assign the territories based on the brick code.
The Brick-to-Terr object contains records that match the brick code to the territory. There are only two fields that need to be populated in each of the Brick-to-Terr entries. The first is the name field which contains the name of the brick code. The second field is the Territory_vod__c field. This field contains the territories (delimited by semicolons) that are assigned when the Mass Assign Territories utility is run from the Territory Utilities tab.
Brick and Territory names in mass assignments are case and accent insensitive. For example, Territóry1 is the same as territory1.
Add the Brick_vod__c field to the address object, as the territory utilities will match the brick code in the Brick_vod__c field to the name field in the Brick-to-Terr to correctly align a territory to the account associated with the address.
When the Territory Utilities run, Test Territory Assignment or Mass Assign Territories, the Territory_vod or the Test_Territory_vod fields on the account object are populated based on the Brick-to-Terr. Additionally, the Territory Utilities respect the Include in Territory Alignments functionality that exists on the address object.
When viewing territories, a brick level analysis displays – you will need to utilize the custom object Brick_Hierarchy_vod. For more information on how to use brick based analysis, see Fixed Reports.