---
title: "Automated review of engineering change orders"
slug: "bc-automated-review-of-engineering-change-orders"
tags: ["Concept"]
updated: 2026-06-25T09:59:00Z
published: 2026-06-25T09:59:00Z
canonical: "docs.staedean.com/bc-automated-review-of-engineering-change-orders"
---

> ## 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.

# Automated review of engineering change orders

The Engineering Change Staging table is a background function: records are processed by batch functions, either directly following the import or as separate batches run by the job queue.

The Engineering Change Request (ECR) is an important driver for the engineering change process. When the change is triggered by an ECR, the source type and number are stored in the ECR, so the origin is known.

When engineering responds with an ECO, the ECR is preferably mentioned as a reference. This means the ECO can be handled as pre-approved, because it is based on the operations request.

When the ECR is not specified, the **Get ECR Lines** action in the ECO allows the user to manually retrieve one or more ECRs being resolved by the ECO. When the ECO is processed with the **Carryout Action**, the linked ECRs are marked as **Processed** and the ECR lifecycle status is set accordingly (**ARCHIVE**).

In this process, the Engineering Change Staging shows a history of the imported records.

> [!NOTE]
> Note
> 
> To support the automated process, a codeunit is provided for use in an Event Generator activity in a Connectivity Studio process: 11014979 N149 Create Eng. Change Order.

## Related

- [Engineering Change Management ](/bc-engineering-change-management.md)