# Release a BOM revision

> Release a draft BOM revision — valid from today or from the date of a change number; a released revision does not change.

URL: https://erpdocs.corexlogic.com/en/uretim/islemler/urun-agacini-yayinlama

- **Type:** Task
- **Module:** Manufacturing
- **Menu path:** Üretim › Ana Veriler › Ürün Ağaçları › ağaç detayı › Yayınla (Production › Master Data › Bills of Materials › BOM detail › Release)
- **Screen route:** `/erp/manufacturing/boms/{id}`
- **Required permission:** `erp-manufacturing-boms.edit`
- **Prerequisites:**
  - The BOM has a revision in **Taslak** (Draft) status.
  - If it is to be valid from a future date, an **Etkin** (Active) change number has been opened ([Create an engineering change](https://erpdocs.corexlogic.com/en/uretim/islemler/muhendislik-degisikligi-olusturma)).
  - If it is the BOM of a configurable item, the revision has been tested with **Yapılandırarak Dene** (Configure and Test) ([Configure and test](https://erpdocs.corexlogic.com/en/uretim/islemler/yapilandirarak-deneme)).

Releasing makes a draft revision final. A released revision is a historical production definition: it cannot be
changed, cannot be deleted and does not return to draft.

## Steps

1. Open the BOM detail. Click **Yayınla (Rev. N)** (Release, Rev. N) in the header (the same command is also in the **İşlemler** (Actions) menu of the revision row and in the **Yayınla** (Release) button on the revision detail).
   <!-- action: click · target: "Yayınla (Rev. 1)" · expect: "The Revizyon yayınlansın mı? (Release the revision?) window" -->

   ![BOM detail — revisions and validity](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/agac-detay.png)
   1. Release the draft
   2. Copy engineering BOM to production
   3. Revision effective today
   4. Usage, alternative name, lot size
   5. Revision valid-from date

2. If you leave the **Değişiklik numarası** (Change number) field empty, the revision is valid from today. If it is to be valid from a future day, select an active change number from the list.
   <!-- action: select · target: "Değişiklik numarası" · value: "Değişiklik numarası yok — bugünden geçerli" · expect: "With a future-dated number: Bu tarihe kadar mevcut revizyon etkin kalır (The current revision remains effective until this date)" -->
3. Click **Revizyonu Yayınla** (Release Revision).
   <!-- action: click · target: "Revizyonu Yayınla" -->

   ![Release revision dialog](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/agac-yayinla.png)
   1. Change number — empty means valid from today
   2. Open orders keep their revision
   3. Release Revision

4. In the revisions table, check that the status is **Yayınlandı** (Released) and that **Yayın Tarihi** (Release Date) and **Geçerlilik** (Validity) are filled in; if it is valid today, the **Etkin** (Active) badge appears on the row.
   <!-- action: verify · target: "Yayınlandı" · expect: "Summary: Yayında Revizyon 1 · Bugün etkin Revizyon 1 (Released: Revision 1 · Effective today: Revision 1)" -->

**Result:** The revision becomes **Yayınlandı** (Released) and can never be changed again; from the validity day onwards, planning (MRP, planned orders) and new production orders use it. For a change, [open a new revision](https://erpdocs.corexlogic.com/en/uretim/islemler/urun-agaci-revizyonu-acma).

## What you need to know

- **Existing production orders are not affected**: each order selects its own revision, and the material requirements
  of a released order remain frozen. To use the new revision, the order is reopened.
- The **effective revision** is the highest-numbered revision whose validity has started on that day. A revision
  released with a change number stays pending until the number's date; until then, the previous revision is effective.
  MRP explodes a planned order with the BOM valid on its start day.
- Validity progresses in revision order. If the date of the selected number is earlier than that of the previous
  revision, the release is rejected: "Revizyon N gg.aa.yyyy tarihinden geçerli olamaz — önceki revizyon M gg.aa.yyyy
  tarihinden geçerli; geçerlilik revizyon sırasıyla ilerler." (Revision N cannot be valid from dd.mm.yyyy — the
  previous revision M is valid from dd.mm.yyyy; validity progresses in revision order.)
- A locked number cannot be selected: "MDN-… kilitli — yeni yayında kullanılamaz." (MDN-… is locked — it cannot be used
  in a new release.)
- On release, the BOM graph is checked; if a sub-BOM uses this card indirectly: "Bu revizyon yayınlanırsa ürün ağacı
  grafında döngü oluşur — bir malzeme zinciri dolaylı olarak bu çıktı kartına geri dönüyor." (If this revision is
  released, a cycle is created in the BOM graph — a material chain leads back indirectly to this output card.)
- If the window shows a 409 conflict message (someone else changed it at the same time, the card became inactive…),
  refresh the page with **Ürün ağacını yeniden yükle** (Reload BOM) and try again.
- If an approved request is mandatory in Üretim Ayarları (Production Settings), the revision can be released only with
  the number of an approved change request ([Engineering changes](https://erpdocs.corexlogic.com/en/uretim/ekranlar/muhendislik-degisiklikleri)).
- A routing revision is released the same way (**Rota revizyonu yayınlansın mı?** (Release the routing revision?)).

## Related

- [Bills of materials screen](https://erpdocs.corexlogic.com/en/uretim/ekranlar/urun-agaclari)
- [Engineering changes](https://erpdocs.corexlogic.com/en/uretim/ekranlar/muhendislik-degisiklikleri)
- [Production orders](https://erpdocs.corexlogic.com/en/uretim/ekranlar/uretim-emirleri)