To generate orders (TPOP)

With the Generate Orders (TPOP) (whinh2201m000) session, you can only generate time-phased order point (TPOP) orders if:

• You want to replenish at warehouse level.
• The supply system for the item and warehouse combination is Time-Phased Order Point. You can specify the supply system in the Supply System field of the Item Data by Warehouse (whwmd2110s000) session.
• The items are of type Purchased or Manufactured. You can specify the item type in the Item Type field of the Items - Defaults (tcibd0102m000) session.
• The items are non- floor stock items. An item is a non-floor stock item if the Floor Stock check box on the Item - Warehousing (whwmd4100s000) session is cleared.

In the Item Data by Warehouse (whwmd2110s000) session you must specify whether supply must take place from a warehouse. To specify that supply must take place from a warehouse, select the Supply from Warehouse check box. If this check box is cleared, supply will take place from:

• A business partner if the item type is Purchased. You can specify the business partner in the Buy-from Business Partner field of the Item Data by Warehouse (whwmd2110s000) session.
• A work center if the item type is Manufactured. LN retrieves the work center from Manufacturing.

If supply takes place from:

• A business partner, LN retrieves the Supply Time from the Items - Purchase Business Partner (tdipu0110m000) session.
• A work center, LN retrieves the Order Lead Time from the Items - Production (tiipd0101m000) session.

• A warehouse, LN retrieves and adds up the following lead times:

  • Inbound Lead Time from the Item Data by Warehouse (whwmd2110s000) session.
  • Outbound Lead Time from the Item Data by Warehouse (whwmd2110s000) session.
  • 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 on the COM Parameters (tccom0000s000) session.

You can specify:

• The seasonal patterns in the Seasonal Patterns (tcmcs0116m000) session.
• The seasonal factors in the Seasonal Pattern Factors (tcmcs0117m000) session.

In the Item Data by Warehouse (whwmd2110s000) 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.

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:

  • Item Data by Warehouse (whwmd2110s000), Replenishment tab.
  • Items - Purchase Business Partner (tdipu0110m000), Ordering tab.

LN only takes into account:

• The supplier safety time if supply takes place from a business partner.
• The outbound lead time and the item safety time if the requirement is caused by a planned inventory transaction.

LN retrieves:

• The outbound lead time from the Item Data by Warehouse (whwmd2110s000) session.
• The inbound lead time from the Item Data by Warehouse (whwmd2110s000) session.
• The item safety time from Safety Lead Time field of the Item Data by Warehouse (whwmd2110s000) session.
• The supplier safety time from the Safety Time field of the Items - Purchase Business Partner (tdipu0110m000) session.

When LN determines the requirement date, the planned receipt date, and the planned delivery date, it takes into account the actual calendar. Therefore, LN first searches for a calendar in the following order:

1. The warehouse's calendar.
2. If the warehouse's calendar is not specified, the company's calendar.

If the Use Item Ordering Data check box in the Item Data by Warehouse (whwmd2110s000) session is selected, LN retrieves the following data from the Items - Ordering (tcibd2100m000) session instead of from the Item Data by Warehouse (whwmd2110s000) session:

• Seasonal Pattern for Safety Stock
• Reorder Point
• Safety Stock

• Current date/time: Wednesday, January 3/1:30:00.
• Inventory on hand on current date (in pieces): 18.
• Order horizon factor: 3.
• 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.
• Seasonal pattern for safety stock has period type: Week.
• Number of periods: 4.

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.

Planned inventory transactions:

• January 11/18:00:00 planned issue of 9.
• January 23/11:30:00 planned issue of 8.

If you replenish items for each warehouse, based on the data just provided, the results are as follows:

• On Monday, January 8/0:00:00, the safety stock exceeds the projected on hand with two items. Therefore, LN generates a warehousing order to replenish two items. Because Monday, January 8/0:00:00, is not available according to the actual calendar, LN sets Friday, January 5/17:00:00, as the requirement date. To determine the planned receipt date, LN subtracts four hours inbound lead time from the requirement date. As a result, the planned receipt date is Friday, January 5/13:00:00. Because a warehousing order is generated, LN also determines the planned delivery date by subtracting two days transport time from the planned receipt date. As a result, the planned delivery date is Thursday, January 4/8:00:00.
• On Thursday, January 11/18:00:00, the projected on hand decreases and falls below the safety stock with nine items caused by a planned inventory transaction. As a result, LN generates a warehousing order to replenish nine items. Because Thursday, January 11/18:00:00, is not available according to the actual calendar, LN sets Thursday, January 11/17:00:00, as the requirement date. To determine the planned receipt date, LN subtracts four hours outbound lead time, four hours inbound lead time, and one day item safety time from the requirement date. As a result, the planned receipt date is Thursday, January 11/8:00:00. Because a warehousing order is generated, LN also determines the planned delivery date by subtracting two days transport time from the planned receipt date. As a result, the planned delivery date is Tuesday, January 9/8:00:00.
• On Monday, January 15/0:00:00, the safety stock exceeds the projected on hand with five items. Therefore, LN generates a warehousing order to replenish five items. Because Monday, January 15/0:00:00, is not available according to the actual calendar, LN sets Friday, January 12/17:00:00, as the requirement date. To determine the planned receipt date, LN subtracts four hours inbound lead time from the requirement date. As a result, the planned receipt date is Friday, January 12/13:00:00. Because a warehousing order is generated, LN also determines the planned delivery date by subtracting two days transport time from the planned receipt date. As a result, the planned delivery date is Thursday, January 11/8:00:00.
• On Monday, January 22/0:00:00, the safety stock decreases to 15 items while the projected on hand is 25 items. As a result, no replenishment is needed and LN does not generate a warehousing order.
• On Tuesday, January 23/11:30:00, the projected on hand decreases with eight items. Because the projected on hand does not fall below the safety stock, LN does not generate a warehousing order.