Planned independent requirements
A planned independent requirement (forecast) feeds MRP with demand that is expected but has no orders yet: "6 filing cabinets will be sold in December". The period's approved sales orders consume the forecast; MRP counts only the remainder as demand. This way the same demand is not planned twice, once from the forecast and once from the order.
Screen/erp/demand/independent-requirementserp-demand-independent-requirements.view (görme)erp-demand-independent-requirements.edit (Tahmin Gir, düzenleme, silme)The Malzeme İhtiyaçları (Material Requirements) view and the availability check on the sales order do not count the forecast. The forecast appears in the timeline of the MRP run as a Tahmin (Forecast) element, as a requirement on the first day of the period.
List
- 1Enter Forecast
- 2Approved orders in the period consume the forecast
- 3Remainder enters MRP as demand
- 4Show finished periods too
| Column | Meaning |
|---|---|
| Malzeme (Material) | The item for which the forecast was entered. |
| Dönem Türü (Period Type) | Gün · Hafta · Ay (Day · Week · Month). |
| Dönem (Period) | The period range. A finished period shows the Geçmiş (Past) badge: "Dönem bitti — MRP'ye girmez, iz olarak kalır" (The period has ended — it does not go into MRP and remains as a record). |
| Tahmin (Forecast) | The quantity entered (in the item's base unit). |
| Siparişle Tüketilen (Consumed by Orders) | Approved sales orders whose requested delivery date falls in the period (including shipped ones), limited to the forecast. |
| Kalan (MRP) (Remaining, MRP) | Forecast − consumed; goes into MRP as demand. If fully consumed, Karşılandı (Covered). |
| Not (Note) | Period note. |
Filters: Ara (Search; item code or name) and Geçmiş dönemleri göster (Show past periods). When opened via the Tahmin (Forecast) link in the MRP timeline, the list narrows to a single item and the Tek kart (Single item) badge is shown.
From the row's İşlemler (Actions) menu you can edit the item's forecast or delete a period. Delete confirmation: "Tahmin dönemi silinsin mi? … dönemi silinir; MRP bu dönemin kalanını artık talep saymaz." (Delete the forecast period? Period … is deleted; MRP no longer counts the remainder of this period as demand.)
Enter / Edit Forecast window
- 1Item — planned stock item
- 2Period type — Day, Week, Month
- 3Period quantity (base unit)
- 4Add next N periods
- 5Propose from history — statistical proposal
- 6Save — replaces unfinished periods
The window opens all unfinished periods of the item in a single table, and saving replaces them completely (MD62 planning table). Saving with an empty table deletes the item's future forecast.
| Field | Rule |
|---|---|
| Kart (Item) | A planned stock item. An item that is not planned cannot be selected; the reason is shown (e.g. "Planlama stratejisi "planlama yok" — tahmin MRP'ye girmez; kartın planlama verisini düzenleyin." — Planning strategy is "no planning" — the forecast does not go into MRP; edit the item's planning data.). |
| Dönem türü (Period type) | Gün · Hafta · Ay (Day · Week · Month; default Month). A week is aligned to Monday, a month to the first of the month; all future periods of an item are of a single type. |
| Dönem başı (Period start) | Date; a past date cannot be selected. The Dönem (Period) column shows the aligned range. |
| Miktar (Quantity) | Greater than zero, within the decimal limit of the unit. |
| Not (Note) | Optional. |
| Sonraki [N] … ekle (Add next [N] …) | Adds the next N periods (at most 60 rows). |
Validation messages (N = row): "N. dönem: dönem başı zorunludur." (Period N: the period start is required.), "N. dönem bitmiş — geçmiş döneme tahmin girilmez." (Period N has ended — a forecast cannot be entered for a past period.), "N. dönem tekrar ediyor." (Period N is repeated.), "N. dönem: miktar sıfırdan büyük olmalıdır." (Period N: the quantity must be greater than zero.), and additionally on the server "gg.aa.yyyy dönemi geçmiş bir tahminle çakışıyor." (Period dd.mm.yyyy overlaps with a past forecast.) and "'KOD' planlanmıyor (planlama stratejisi "planlama yok") — tahmin MRP'ye girmez." ('KOD' is not planned (planning strategy "no planning") — the forecast does not go into MRP.)
Propose from History
The Geçmişten Öner (Propose from History) section at the bottom of the window calculates a statistical proposal from the item's consumption history (it does not write anything):
| Field | Values |
|---|---|
| Model | Otomatik (Automatic) · Hareketli ortalama (Moving average) · Üstel düzeltme (Exponential smoothing) · Trend · Mevsimsel (Seasonal) |
| Geçmiş dönem (History periods) | Day 1–365 (default 56) · Week 1–156 (52) · Month 1–36 (24) |
| Önerilecek dönem (Periods to propose) | Day 1–90 (14) · Week 1–52 (12) · Month 1–24 (6) |
| Alfa (Alpha) | Between 0 and 1, both excluded (hidden for moving average) |
Öner (Propose) shows the historical consumption chart, the selected model, the MAD and the period proposals. The proposal is not saved: Öneriyi Forma Aktar (Transfer Proposal to Form) replaces the period rows (asks for confirmation if rows exist), and you then save with Kaydet (Save). If there is no consumption in the history, the screen shows "Seçilen geçmişte tüketim yok — öneri üretilmedi." (No consumption in the selected history — no proposal was produced.)
Step by step: Enter a planned independent requirement.