| To generate order advice (SIC) |  |
| In the Generate Order Advice (SIC) (whina3200m000) session, you can generate order advice to replenish purchased and manufactured items. However, you can only do so if: For the item/warehouse combination, the supply system is set to None. You can specify the supply system in the Supply System field of the Warehouse - Item (whwmd2110s000) session. The items are Purchased or Manufactured type. You can specify the item type in the Item Type field of the Item - General (tcibd0101s000) session. The items are non- floor stock items. An item is a non-floor stock item if the Floor Stock check box in the Item - Warehousing (whwmd4100s000) session is cleared. Order horizon Before ERP LN generates order advice, ERP LN determines the order horizon for which the replenishment must take place. The order horizon is determined as follows:
    order horizon = current date + (total lead time * order horizon factor) + order horizon constant
ERP LN determines the total lead time based on the item type, without taking the calendars into account. If the item type is Purchased, ERP LN retrieves and adds up the following lead times: Internal Processing Time from the Items - Purchase Business Partner (tdipu0110m000) session. Safety Time from the Items - Purchase Business Partner (tdipu0110m000) session. Supply Time from the Items - Purchase Business Partner (tdipu0110m000) session. If the item type is Manufactured, ERP LN retrieves the Order Lead Time from the Items - Production (tiipd0101m000) session. Note In the Generate Order Advice (SIC) (whina3200m000) session, you can overrule any of the order horizon data that is defined under SIC Order Horizon in the Inventory Analysis Parameters (whina0100m000) session. Reorder point and safety stock The reorder point does not need to be a fixed amount; it can fluctuate over time. The fluctuations of the reorder point depend on the fluctuations of the seasonal pattern with its seasonal factors of the forecast/demand. You can let the safety stock fluctuate based on a seasonal pattern with its seasonal factors. For more information, refer to Seasonal pattern for safety stock and demand. You can specify: The seasonal patterns in the Seasonal Patterns (tcmcs0116m000) session. The seasonal factors in the Seasonal Pattern Factors (tcmcs0117m000) session. Note You can specify a seasonal pattern for at most one year. All seasonal patterns start at January 1, after which they are repeated during the year according to the number of periods. In the Warehouse - Item (whwmd2510m000) or the Item - Ordering (tcibd2100s000) session, you can specify: The base reorder point in the Reorder Point field. The base safety stock in the Safety Stock field. The seasonal pattern for safety stock in the Seasonal Pattern for Safety Stock field. To generate orders With the Generate Order Advice (SIC) (whina3200m000) session, ERP LN generates an order advice for each requirement within the order horizon. A requirement may occur if the projected on hand drops below the reorder point, which can be caused by: A decrease of the projected on hand. An increase of the reorder point. The ordered quantity depends on: The safety stock. (If seasonal patterns apply, the safety stock defined at the end of the order horizon is taken into account.) The projected on hand. The replenishment settings defined in the following sessions: Warehouse - Item (whwmd2110s000) Items - Purchase Business Partner (tdipu0110m000) The kind of order advice that is generated for the item depends on the item type:
Item type | ERP LN generates...
Purchased | A purchase-order advice, which you can view and maintain in the Purchase Order Advice (whina3110m000) session.
Manufactured | A production-order advice, which you can view and maintain in the Production Order Advice (whina3100m000) session.
Note Planned inventory transactions that are excluded from planning, that is, for which the Exclude from Planning have quantity 1, are not taken into account for SIC runs. To determine the requirement date The requirement date is the date on which the projected on hand drops below the reorder point. To determine the actual requirement date, ERP LN takes into account the actual calendar. If the requirement date is not available according to the actual calendar, ERP LN looks backwards for the first available date/time before the requirement date. ERP LN sets the first available date/time as the actual requirement date. To determine the planned receipt date ERP LN determines the planned receipt date by planning forwards from the requirement date and taking into account the actual calendar. ERP LN determines the planned receipt date as follows:
    planned receipt date = planned requirement date + outbound lead time + inbound lead time + item safety time + supplier safety time
ERP LN only takes into account: The supplier safety time if the item type is Purchased. The outbound lead time and the item safety time if the requirement is caused by a planned inventory transaction. ERP LN retrieves: The outbound lead time from the Warehouse - Item (whwmd2110s000) session for the default warehouse that is linked to the item in the Item - General (tcibd0101s000) session. The inbound lead time from the Warehouse - Item (whwmd2110s000) session for the default warehouse that is linked to the item in the Item - General (tcibd0101s000) session. The item safety time from Safety Time field of the Item - Ordering (tcibd2100s000) session. The supplier safety time from the Safety Time field of the Items - Purchase Business Partner (tdipu0110m000) session. To determine the planned delivery date ERP LN determines the planned delivery date based on the planned receipt date with the following formula, taking into account the actual calendar:
    planned delivery date = planned receipt date - transport time
ERP LN determines the transport time between the ship-from's address and the ship-to's address, based on a relevant distance table (if available) in the Distance Table by City (tccom4137s000) session or in the Distance Table by ZIP Code/Postal Code (tccom4138s000) session. From which of these two sessions the transport time is retrieved depends on the value of the Usage Distance Tables field in the COM Parameters (tccom0000s000) session. To take into account the actual calendar When ERP LN determines the requirement date, the planned receipt date, and the planned delivery date, it takes into account the actual calendar. Therefore, ERP LN first searches for a calendar in the following order: The warehouse's calendar. If the warehouse's calendar is not specified, the company's calendar. ERP LN bases the actual calendar on the found calendar code and the availability type. ERP LN determines the requirement date, the planned receipt date, and the planned delivery date based on the actual calendar. Before the calendar's start date and after the calendar's end date, the standard calendar applies. When ERP LN determines the requirement date, the planned receipt date, and the planned delivery date, and if the lead times are expressed in hours, ERP LN takes into account all the time that is available on a day according to the actual calendar. However, if the lead times are expressed in days, ERP LN considers a day a whole day if the actual calendar indicates that time is available on that day. Note You can view the actual calendar in the Calendar Working Hours (tcccp0120m000) session. You can define the availability type on the Storage Inspection tab of the Master Data Parameters (whwmd0100s000) session. Example To generate order advice for an item with item type Purchased. Current date/time: Wednesday, January 3/1:30:00 pm Inventory on hand on current date (in pieces): 18 SIC order horizon factor: 3 SIC order horizon constant (in days): 15 Inbound lead time (in hours): 4 Outbound lead time (in hours): 4 Transport time (in days): 2 Item safety time (in days): 2 Supplier safety time (in days): 2 Base safety stock (in pieces): 10 Base reorder point (in pieces): 15 Seasonal pattern for safety stock and demand has period type: Week. Number of periods: 53 First allowed order date: January 3/10:00:00 am Order interval: 7 days Order quantity is economic order quantity, with EOQ = 24 The warehouse's actual calendar is available from Monday through Friday each week and has an 8:00:00 start time and a 17:00:00 end time. ERP LN determines the order horizon as follows: Order horizon = current date + [(inbound lead time + outbound lead time + transport time) * order horizon factor] + order horizon constant. Order horizon = January 3/1:30:00 + [(4 hours + 4 hours + 2 days) * 3] + 15 days. Order horizon = January 3/1:30:00 + [56 hours x 3] + 360 hours. Order horizon = January 3/1:30:00 + 528 hours = January 25/1:30:00. The seasonal pattern for safety stock and reorder point is as follows, with the resulting safety stock and reorder point (only the first four weeks are listed):
Period | Start date period | Seasonal pattern factor Safety stock | Safety stock | Seasonal pattern factor Demand | Reorder point
--- | --- | --- | --- | --- | ---
Period 1 | January 1/0:00:00 | 1.00 | 10 | 1 | 15
Period 2 | January 8/0:00:00 | 1.50 | 15 | 2 | 30
Period 3 | January 15/0:00:00 | 2.00 | 20 | 2 | 30
Period 4 | January 22/0:00:00 | 1.00 | 10 | 1 | 15
Planned inventory transactions: January 11/18:00:00 planned issue of 9. January 23/11:30:00 planned issue of 8. No planned receipts. The projected on hand before planning the replenishment is as follows:
Date | Projected on hand
--- | ---
January 3 | 18
January 11 | 9
January 23 | 1
Each day, the Generate Order Advice (SIC) (whina3200m000) session is run. This means for today (Current date/time: Wednesday, January 3/1:30:00 pm) the following information is valid: Reorder point: 15 Projected on hand within order horizon = 18 – 9 – 8 = 1 piece. This is below ROP, so an order advice will be created. The order quantity will be: Safety Stock + Quantity Allocated – Quantity On Order – Quantity On Hand = 10 (Safety Stock is taken at the end of the order horizon, which is week 4) + 17 – 0 – 18 = 9. Because EOQ = 24, this quantity will be ordered and stored on the order advice. The order date is the current date when creating the purchase/production order advice, which means for this example January 3/1:32:45 (some minutes after the Generate Order Advice (SIC) (whina3200m000) session was started). The delivery date will be: Order Date + Inbound Lead Time (4 hours) + Transport Time (only for Purchase) (2 days) = Friday January 5/5:32:45 pm. Because this is outside the calendar, delivery date will be Monday January 8/8:32:45 am (08.00 + 32:45 minutes/seconds of Friday). Safety times are not calculated with forward planning used by SIC. When the order advice is confirmed and transferred to purchase (or production), the first allowed order date will be increased with the order interval of 7 days to January 10/10:00:00 am. This means that when Generate Order Advice (SIC) (whina3200m000) is run tomorrow (January 4), this item will be skipped, because the first allowed order date is still in the future. The projected on hand after planning the replenishment is as follows:
Date | Projected on hand
--- | ---
Wednesday January 3 | 18
Monday January 8/8:32:45 | 42
Thursday January 11/18:00:00 | 33
Tuesday January 23/11:30:00 | 25
Related topics To generate orders (TPOP) Overview of calendar functionality |