{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":32764,"path":"it-service-management/expense-line/r_InstalledWithExpenseLine.md","title":"Components installed with Expense Line","bundle":null,"doc_type":null,"release":"australia","body":"\n# Components installed with Expense Line\n\nSeveral types of components are installed with the Expense Line plugin.\n\n**Parent Topic:**[Expense Line](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/expense-line/c_ExpenseLine.md)\n\n**Related topics**  \n\n\n[View an expense]()\n\n[Expense lines and expense allocations]()\n\n[Domain separation and Expense Line]()\n\n## Tables installed with Expense Line\n\nTables are added with activation of Expense Line.\n\n<table id=\"table_d4l_3zy_nr\"><thead><tr><th>\n\nTable\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nExpense Line \\[fm\\_expense\\_line\\]\n\n</td><td>\n\nStores information about expense lines, including a link to the associated rate card. Contains the status and next scheduled processing date for the expense line.\n\n</td></tr></tbody>\n</table>## Roles installed with Expense Line\n\nRoles are added with activation of Expense Line.\n\n|Role|Contains roles|Description|\n|----|--------------|-----------|\n|Financial admin \\[financial\\_mgmt\\_admin\\]|\\[financial\\_mgmt\\_user\\]|Can create, write, and delete allocation units, fixed assets, depreciation, rate cards, distribution costs, expense lines, and expense allocations.|\n|Financial user \\[financial\\_mgmt\\_user\\]|none|Can read allocation units and expense allocations. Can create, read, and write rate cards and expense lines. Can create, read, write, and delete fixed assets, depreciation, distribution costs.|\n\n## Script includes installed with Expense Line\n\nScript includes are added with activation of Expense Line.\n\n|Script include|Description|\n|--------------|-----------|\n|ExpenseLine|Helps create expense line records.|\n|ExpenseManagementUtils|Provides utilities for financial management modules.|\n|ExpenseManagementUtilsAJAX|Provides AJAX utilities for expense lines.|\n\n## Client scripts installed with Expense Line\n\nClient scripts are added with activation of Expense Line.\n\n|Client script|Table|Description|\n|-------------|-----|-----------|\n|Populate sources if inherited|\\[fm\\_expense\\_line\\]|Copies the source fields of the parent expense line to the current line on the Expense Line record if an expense line is inherited.|\n|Populate source fields from asset|\\[fm\\_expense\\_line\\]|If the source asset changes, updates related source fields on the Expense Line record . For example, if the asset source field changes, the configuration item source field is updated, as well.|\n|Populate source fields from ci|\\[fm\\_expense\\_line\\]|Updates related source fields if the source configuration item changes on the Expense Line record.|\n|Populate source fields from contract|\\[fm\\_expense\\_line\\]|Updates related source fields if the source contract changes on the Expense Line record.|\n|Populate source fields from task|\\[fm\\_expense\\_line\\]|Updates related source fields if the source task changes on the Expense Line record.|\n\n## Business rules installed with Expense Line\n\nBusiness rules are added with activation of Expense Line.\n\n|Business rule|Table|Description|\n|-------------|-----|-----------|\n|Create Expense Line|\\[alm\\_asset\\]|Automatically creates an expense line for a new asset based on asset cost unless the asset is a merged software license.|\n|Set source allocation fields|\\[fm\\_expense\\_line\\]|Sets the related source fields when the source ID changes. For example, when an asset becomes the source ID, the asset source field and configuration item source field are automatically populated.|\n|Update Costs|\\[alm\\_consumable\\]|Updates the cost of a consumable when quantity is reduced.|\n\n## Domain separation and Expense Line\n\nDomain separation is unsupported in Expense Line processing. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.\n\n### Support level: No support\n\n-   The domain field may exist on data tables but there is no business logic to manage the data.\n-   This level is not considered domain-separated.\n\nFor more information on support levels, see [Application support for domain separation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-separated-apps.md).\n\n**Related topics**  \n\n\n[Domain separation for service providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-sep-landing-page.md)\n\n"}}