# Create an engineering change

> Open a change number to make BOM and routing revisions valid from a future date — directly or through an approved change request.

URL: https://erpdocs.corexlogic.com/en/uretim/islemler/muhendislik-degisikligi-olusturma

- **Type:** Task
- **Module:** Manufacturing
- **Menu path:** Üretim › Ana Veriler › Mühendislik Değişiklikleri › Değişiklik Numarası Oluştur (Production › Master Data › Engineering Changes › Create Change Number)
- **Screen route:** `/erp/manufacturing/engineering-changes/new`
- **Required permission:** `erp-manufacturing-engineering-changes.create`
- **Prerequisites:**
  - The day from which the change will be valid is known.
  - If an approved request is mandatory in the installation, the number is not opened directly but through the approval of a change request (the second path below).

A change number makes changes in several BOMs and routings valid **from the same day**: the revisions are released in
advance and become effective together when the number's date arrives.

## Steps

1. In the **Üretim › Ana Veriler › Mühendislik Değişiklikleri** (Production › Master Data › Engineering Changes) list, click **Değişiklik Numarası Oluştur** (Create Change Number).
   <!-- action: navigate · target: "/erp/manufacturing/engineering-changes/new" · expect: "The Değişiklik Numarası Oluştur (Create Change Number) form" -->

   ![Engineering Changes list](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/muhendislik-listesi.png)
   1. New change number
   2. Valid-from date of the number
   3. Revisions released with it
   4. Active or Locked

2. Enter the **Başlık** (Title) and **Değişiklik nedeni** (Reason for change) (both are required).
   <!-- action: fill · target: "Başlık" · value: "Demo — tezgâh ayak borusu boyu" -->
3. Select the **Geçerlilik başlangıcı** (Valid from). Revisions released with this number become valid from this day; until then, the previous revision remains effective.
   <!-- action: fill · target: "Geçerlilik başlangıcı" · value: "02.11.2026" -->

   ![Create Change Number](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/muhendislik-olustur.png)
   1. Title
   2. Reason — required
   3. Valid from — revisions take effect that day
   4. Save — number assigned on save

4. Click **Değişiklik Numarasını Kaydet** (Save Change Number).
   <!-- action: click · target: "Değişiklik Numarasını Kaydet" · expect: "The detail of change MDN-2026-000001; Durum (Status) Etkin (Active)" -->
5. When releasing the revision, select this number in the **Değişiklik numarası** (Change number) field of the release window.
   <!-- action: select · target: "Değişiklik numarası" · value: "MDN-2026-000001 · Demo — tezgâh ayak borusu boyu" -->

**Result:** The number is saved in **Etkin** (Active) status (e.g. **MDN-2026-000001**). The **Nesne Listesi — Ürün Ağacı Revizyonları** (Object List — BOM Revisions) in its detail shows the revisions released with this number; when it will no longer be used, click **Kilitle** (Lock).

## With an approved change request (second path)

If the reason for and impact of the change must go through approval, the request opens the number:

1. In the **Üretim › Ana Veriler › Değişiklik Talepleri** (Production › Master Data › Change Requests) list, click
   **Değişiklik Talebi Aç** (Open Change Request).
2. Enter the **Başlık** (Title), **Neden** (Reason), **Etki notu** (Impact note) and **Önerilen geçerlilik** (Proposed
   validity).
3. In the **Etkilenen Nesneler** (Affected Objects) section, select the object type (**Ürün ağacı** (BOM), **Rota**
   (Routing), **Ürün** (Item)), add at least one record with **Nesne ekle** (Add object), and click **Taslağı Kaydet**
   (Save Draft). The request becomes **Taslak** (Draft) with the number `DTL-yyyy-nnnnnn`.
4. On the request detail, click **Gönder** (Submit). If an approval template is defined, the request becomes **Onay
   Bekliyor** (Awaiting Approval) and the approver chooses **Onayla** (Approve) or **Reddet** (Reject); if not, the
   request becomes **Onaylandı** (Approved) immediately.
5. The `MDN-` number that was opened appears in the **Değişiklik numarası** (Change number) field of the approved
   request; its validity is the proposed validity day. Release the revision with this number.

![Draft change request](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/muhendislik-talep-detay.png)
1. Submit — for approval or approved directly
2. Edit — draft only
3. Cancel
4. Change number is opened on approval

In the demo environment, DTL-2026-000001 was submitted and, because there is no approval template, it was approved
directly and opened MDN-2026-000002; DTL-2026-000002 remains as a draft.

## What you need to know

- The date of a number that has taken effect and is in use cannot be changed; a new number is opened. Shifting the
  date also shifts the revisions released with the number, and it cannot be moved into the past.
- A **Kilitli** (Locked) number cannot be selected for a new release; releases made with this number remain valid.
  **Kilidi Kaldır** (Unlock) makes the number selectable again.
- You cannot approve a request you opened yourself; a rejection reason is mandatory, and a rejected request returns to
  draft.

## Related

- [Engineering changes screen](https://erpdocs.corexlogic.com/en/uretim/ekranlar/muhendislik-degisiklikleri)
- [Release a BOM revision](https://erpdocs.corexlogic.com/en/uretim/islemler/urun-agacini-yayinlama)