6 Catalog Extension

With Catalog Extension, you can extend the seeded Catalog data model to support new or client-specific business use cases. You can create new entity definitions or customize the existing entity definitions based on the use case.

Table 6-1 Enabled Data Model Extensions in Catalog

Catalog Object Type	Create	Modify	Extend	Delete
Business Term	Yes	No	No	No
Dimension Entity	Yes	No	No	No
Extend Fact Entities	No	No	Yes	No

All the points mentioned above are applicable to both Seeded and Custom Objects

• New Business Terms added to fact entities can be dimension references, measures, flag or indicators and alphanumeric attributes without dimensional reference.
• Fact logical entities that are allowed for extensions are product processors, account transactions, accounting entries, Accounting Entries Header and Transaction Header.
• Extensions are allowed to logical entities and physical model modification is controlled by the service.
• Required data flow for the extended entities are auto generated by the system.
• Completes basic data quality checks required for extended entities.

You must identify the additional data requirements to implement in the application through system and business use case analysis. Data model gaps need to be captured in Issues and Action governance framework.

Data model extensions must be designed based on the guidelines provided for each area.

Catalog Result layer is designed as a Star Schema for better performance of Analytical and Reporting queries. Hence it is highly recommended that Dimensional Entities must be created for a pre-defined list of values before adding to the Fact Entities. Adding of alphanumeric attributes for Fact Entities must be avoided wherever possible.