The current processing logic for building up a flattened dimension combination table was inefficiently handling the creation of the table. The customer has 150+ basis allocation sources/destinations, and the table was being regenerated for each one of those building a large transaction scope. The update statements to set the individual dimension values was also setting dimension values unneccessarily as not all dimensions are used in the basis rule setup.
Modified the logic to maintain the temp table across all of the basis rules, and only do incremental updates as needed, and reduced the dimension values being set based on the dimensions used in the allocation rule setup.
Article ID: 4033003 - Last Review: 2017, ജൂൺ 20 - Revision: 1