Use cases arise where data augmentation tables are leveraged for custom ETL or views in FAW-ADW. In such scenarios, the data augmentation attributes are not directly published to the semantic layer.

However, depending on the source PVO, these tables can accumulate records quickly (i.e. PVO for XLA_AE_LINES) in production scenarios, which can impact usage in custom logic/ETL.

Ideally, we have the following flexibility in FAW’s data augmentation definitions:

• Ability to purge records or set a retention limit on data aug tables; specifically for those not used for semantic extensions
• Ability to filter inbound records when defining a data augmentation. Similar capabilities are available in BICC extract definitions and should be made available in the FAW UI
  • For example, we may only require AE_LINES for a given application_id but all records are ingested into FAW-ADW.