---
title: "Business impact scope and filter criteria"
slug: "business-impact-scope-and-filter-criteria"
description: "Learn how the ECM+ Impact Agent analyzes transaction types in D365 F&SCM to evaluate business impacts on sales, purchases, and inventory."
tags: ["ECM Impact Agent", "Concept", "ECM plus"]
updated: 2026-08-18T08:34:03Z
published: 2026-08-18T08:34:03Z
canonical: "docs.staedean.com/business-impact-scope-and-filter-criteria"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Business impact scope and filter criteria

When the ECM+ Impact Agent analyzes a change, it evaluates the affected item across several transaction types in D365 F&SCM. Each transaction type has a filter that decides which records count as impacted. Understanding this scope helps you interpret the counts and metrics that the agent reports.

The agent evaluates the following transaction types for the affected item:

- **Sales orders** – Sales lines with the status **Open order**.
- **Purchase orders** – Purchase lines with the status **Open order**.
- **Production orders** – Production orders with the status **Created**, **Estimated**, **Scheduled**, **Released**, or **Started**.
- **Inventory** – On-hand inventory that is not closed and has an available physical quantity greater than zero.
- **Purchase requisitions** – Purchase requisition lines with the status **Draft**.
- **Quotations** – Sales quotation lines with the status **Created**.
- **Inventory journals** – Unposted inventory journal lines of the journal types enabled in your ECM+ configuration.

For each transaction type, the agent retrieves aggregate data such as order counts, customer or supplier counts, quantities, total order value, delivery timing (for example, days to nearest delivery), and the company (legal entity) involved.

> [!NOTE]
> Note
> 
> - D365 F&SCM refers to suppliers as *vendors*. This guide uses **supplier** and **vendor** interchangeably; where the agent surfaces a D365 F&SCM field directly (for example, in a rule condition), it uses the underlying field name **Vendor**.
> - Because the agent only counts open and in-progress transactions, a change that affects only completed or closed documents returns no downstream business impact.