# Enter planned independent requirements (forecast)

> Enter a sales forecast period by period for a planned card; the period's approved orders consume the forecast, and MRP plans the remainder.

URL: https://erpdocs.corexlogic.com/en/uretim/islemler/planli-bagimsiz-ihtiyac-girme

- **Type:** Task
- **Module:** Manufacturing
- **Menu path:** Üretim › Üretim Planlama › Planlı Bağımsız İhtiyaçlar › Tahmin Gir (Production › Production Planning › Planned Independent Requirements › Enter Forecast)
- **Screen route:** `/erp/demand/independent-requirements`
- **Required permission:** `erp-demand-independent-requirements.edit`
- **Prerequisites:**
  - The card's **Planlama stratejisi** (Planning strategy) is not *Planlama Yok* (No Planning) and the card is stock-managed.

A forecast brings demand for which no order has arrived yet into planning. As approved sales orders arrive in the
period, the forecast is consumed; MRP counts only the **Kalan (MRP)** (Remaining, MRP) quantity as a requirement.

## Steps

1. Open the **Üretim › Üretim Planlama › Planlı Bağımsız İhtiyaçlar** (Production › Production Planning › Planned Independent Requirements) screen and click **Tahmin Gir** (Enter Forecast).
   <!-- action: click · target: "Tahmin Gir" · expect: "The Tahmin Gir (Enter Forecast) window" -->

   ![Planned Independent Requirements — forecast, consumption, remainder](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/ihtiyac-tahmin-listesi.png)
   1. Enter Forecast
   2. Approved orders in the period consume the forecast
   3. Remainder enters MRP as demand
   4. Show finished periods too

2. Click the **Kart** (Card) field, type the card's code in the search and select it from the list. If the card has unfinished periods, they are loaded into the table.
   <!-- action: choose · target: "Kart" · value: "MAM-0005" · expect: "The window title is "Tahmin Gir — MAM-0005" (Enter Forecast — MAM-0005)" -->
3. Select the **Dönem türü** (Period type) (Gün (Day) · Hafta (Week) · Ay (Month)).
   <!-- action: select · target: "Dönem türü" · value: "Ay" -->
4. Enter the number of periods to add in the **Sonraki** (Next) box and click **ay ekle** (add months) (**hafta ekle** (add weeks) for weeks, **gün ekle** (add days) for days). Remove a period you do not want with the trash can at the end of the row.
   <!-- action: click · target: "ay ekle" · value: "3" -->
5. Fill in the **Miktar** (Quantity) field of each period; enter a **Not** (Note) if necessary.
   <!-- action: fill · target: "1. dönem miktarı" · value: "6" -->

   ![Enter Forecast dialog — monthly periods](https://erpdocs.corexlogic.com/en/en/img/screens/uretim/ihtiyac-tahmin-gir.png)
   1. Item — planned stock item
   2. Period type — Day, Week, Month
   3. Period quantity (base unit)
   4. Add next N periods
   5. Propose from history — statistical proposal
   6. Save — replaces unfinished periods

6. If you wish, open **Geçmişten Öner** (Propose from History), select a model, and fill the rows with the proposal using **Öner** (Propose) and **Öneriyi Forma Aktar** (Transfer Proposal to Form).
   <!-- action: open · target: "Geçmişten Öner" -->
7. Click **Kaydet** (Save).
   <!-- action: click · target: "Kaydet" · expect: ""MAM-0005 tahmini kaydedildi." (MAM-0005 forecast saved.) and the period rows in the list: Tahmin (Forecast), Siparişle Tüketilen (Consumed by Orders), Kalan (MRP) (Remaining, MRP)" -->

**Result:** The card's unfinished periods are replaced by the list you entered. MRP plans the remainder of each period as a requirement on the first day of the period. Next step: [run MRP](https://erpdocs.corexlogic.com/en/uretim/islemler/mrp-kosusu-yapma).

## What you need to know

- **Saving is a full replacement:** the window carries all unfinished periods of the card; a period you remove from
  the table is deleted. Saving with an empty table deletes the future forecast.
- A forecast cannot be entered for a past period; finished periods remain as a trace and are not included in MRP. The
  current period can be entered; MRP moves its requirement to today and writes the **Gecikmiş ihtiyaç** (Overdue
  requirement) exception.
- A card's future periods are of a single type; when you change the period type, the rows are aligned to the new type.
- Consumption: **approved** sales order items (including those shipped) whose requested delivery date falls in the
  period, limited to the forecast. A draft order does not consume.
- Example (demo): 6 pcs were entered for December 2026 and 4 pcs for January 2027 for MAM-0005. Because on hand is 6,
  minimum 2 and maximum 8, MRP generated a proposal of 8 pcs for the 01.12.2026 requirement (PLO-2026-000001).

## Related

- [Planned independent requirements screen](https://erpdocs.corexlogic.com/en/uretim/ekranlar/planli-bagimsiz-ihtiyaclar)
- [MRP run](https://erpdocs.corexlogic.com/en/uretim/ekranlar/mrp-kosusu)
- [Make-to-stock process](https://erpdocs.corexlogic.com/en/surecler/stoga-uretim)