Expense Lines business rules can fail due to missing AssetCommonTCORollUpUtils script includeDescription6 Business Rules from the Asset Management Common [sn_itam_common] app depend on a script include AssetCommonTCORollUpUtils that will only be present if the Physical Assets [sn_phy_assets] app is also installed, and installed first. Populate expense category on exp line, on fm_expense_line, /sys_script.do?sys_id=62808d0b77ddb11087d92531df5a990dSet Asset value from task or CI, on fm_expense_line, /sys_script_9df50f4fa149f910f877903029e845cbCreate expense line for task m2m asset, on fm_expense_line, /sys_script.do?sys_id=db66d74b77e1311087d92531df5a995aRoll up expense line on parent change, on alm_asset, /sys_script.do?sys_id=6f64087e77d5b11087d92531df5a99c1Create Asset to ExpLine m2m on Insert, on sn_ent_asset, /sys_script.do?sys_id=acf7c32c7702f11087d92531df5a9933Expense roll up for Asset TCO, on fm_expense_line, /sys_script.do?sys_id=7f424b8337c1311087d9e83174924bea Symptoms include: When creating or updating a expense line, it fails and display a red popup with the following error:'Condition: AssetCommonTCORollUpUtils.populateExpenseCategoryCondition(current)' in business rule 'Populate expense category on exp line' on fm_expense_line: EXPXXXXXXX evaluated to null;Steps to Reproduce On a Xanadu and onwards instance, with Asset Management Common v10.0.0 or later installed:Create expense line on Xanadu instanceTry to update it Expected behaviour:Expense line is created or updated Given that the fix of PRB1724467 in Asset Management Common v10.0.0 set the script include to only be present if the Physical Assets [com.sn_phy_assets] plugin is also installed first, these 6 business rule should possibly also only be there if the Physical Assets is installed.Or perhaps the script include is supposed to always be there? Actual behaviour:The action is being errored out with: 'Condition: AssetCommonTCORollUpUtils.populateExpenseCategoryCondition(current)' in business rule 'Populate expense category on exp line' on fm_expense_line: EXPXXXXXXX evaluated to null; WorkaroundThis problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.Related Problem: PRB1810082