5.3.1.3.6 From Transaction Summary to Transaction Summary

Transaction Summary-to-Transaction Summary is an infrequent use case.

• Multiply Liability Transaction Summary volumes by a fixed unit cost and post the result to Liability Transaction Summary costs.
• Another reason that Transaction Summary-to-Transaction Summary is an infrequent use case is that customers often have unit cost data for their activities that allow them to multiply their Volumes times Unit Costs to populate the both the Volume & Cost columns within their ETL that is used to initially load Transaction Summary tables.
• Because Transaction Summary Tables commonly store activity volumes, you are more likely to build this kind of rule using Static Table Driver Rules that contain unit costs for many activities. To complete your Volume * Unit Cost process, one Static Driver Table Allocation Rule could take the place of dozens or hundreds of Static Driver Allocation Rules.