| Warehousing Order (whinh2100m100) |  |
| Use this session to view and maintain warehousing orders by order origin. For warehousing orders originating from other packages, you can only modify the data created in Warehouse Management. If the Warehousing Order check box on the Inventory Handling Parameters (whinh0100m000) session is selected and you modify, create, or remove a warehousing order manually, history is generated to register the different versions of the warehousing order. This applies to orders and order lines. You can divide each origin/order combination into multiple sets of order lines. All order lines that belong to one order set will have the same shipping attributes. A manually created warehousing order can have the following order origins: Sales (Manual) Purchase (Manual) Service (Manual) Maint. Sales (Manual) Maint. Work (Manual) SFC Production (Manual) Transfer (Manual) For warehousing orders created in Warehouse Management, the order number is determined by the Number Group field in the Inventory Handling Parameters (whinh0100m000) session. Warehousing orders are processed according to one of the following procedures: The default warehousing procedure that is linked to the warehousing order type of the warehousing order header to which the current order line belongs. The warehousing procedure defined for the current warehousing order. To adjust the warehousing procedure for individual warehousing orders, select Activities by Warehousing Order (whinh2104m000) from the Specific menu. Note that if, for a particular order, you change the first activity of the procedure from manual to automatic, you must use the Process command from the Specific menu to start processing the order. You must also use the Process command for manual orders whose first activity is automatic. For further details on warehousing procedures, see To define warehousing procedures. Note You cannot handle inventory adjustments in this session. Inventory adjustments are supported by the Cycle Counting Orders (whinh5100m000) session because they do not generate a physical transaction. Related topics To handle warehousing orders To define warehousing procedures To define warehousing order types To store finished generic items Multicompany warehouse transfers Overview of kit handling in Warehouse Management
Fields | Description
Order | The origin of the order. The origin refers to the package that initiated the warehousing order. The Transfer origin refers to Warehouse Management.
Order | The code of the warehousing order. If the order is generated by another package, this number will correspond to the original order number.
Order | order set In a kit handling scenario, an order set includes the components of a subkit item. Related topics Overview of kit handling in Warehouse Management
Blocked | If this check box is selected, the order is blocked. Related topics To block and unblock
Inventory Transaction Type | A classification that is used to indicate the type of inventory movement. The following inventory transaction types are available: Issue From warehouse to other entity than warehouse. Receipt From other entity than warehouse to warehouse. Transfer From one warehouse to another. WIP Transfer From one costing work center to another.
Order Date | The date on which the warehousing order is generated or registered.
Order Group | The group of orders to which the warehousing order belongs. You can use order groups to carry out the outbound process for each group of related warehousing orders, to save time.
Carrier/ LSP | An organization that provides transport services. You can link a default carrier to both ship-to and ship-from business partners. In addition, you can print sales and purchase orders on a packing list, sorted by carrier. For ordering and invoicing, you must define a carrier as a business partner.
Carrier/LSP Binding | If this check box is selected, The carrier selected in the Carrier/LSP field is mandatory. If freight orders are created from the warehousing order, the binding carrier is the carrier that must be used to plan the transportation of the freight orders. You can select or clear this check box for warehousing orders created in Warehouse Management. For warehousing orders that originate from sales orders or purchase orders, this check box is read-only. The value of this check box is determined on the originating sales order or purchase order.
Route | The route that is used to ship the goods. When you generate an outbound advice, you can select all warehousing orders for a specific route to create a run.
Freight Service Level | An entity that expresses the duration of transportation, such as: delivery within twelve hours. A freight service level (optional) is used as follows: As a factor that determines the transportation costs of a load. As a factor that determines the freight rate of a freight order.
Revision | The revision number of the order.
Revision | The revision number of the item.
Minimum Quantity Tolerance | If the warehousing order is of the Receipt transaction type, this field shows the greatest negative deviation from the ordered quantity that is tolerated, expressed in a percentage. The Hard Stop on Quantity field in the Inbound Order Lines (whinh2110m000) session indicates which action ERP LN carries out if the tolerance is not met. ERP LN retrieves the Minimum Quantity Tolerance from the Items - Purchase Business Partner (tdipu0110m000) session or from the Items - Purchase (tdipu0101m000) session if you release a purchase order or if a purchase schedule is released to Warehouse Management. Example receipt Minimum Quantity Tolerance: 10% Ordered quantity: 200 If the received quantity is less than 180 items, and the value of the Hard Stop on Quantity field in the Inbound Order Lines (whinh2110m000) session is: No, you can confirm the receipt. Warn, you can confirm the receipt, but you get a warning. Block, you cannot confirm the receipt.
Maximum Quantity Tolerance | If the warehousing order is of the Receipt transaction type, this field shows the greatest positive deviation of the ordered quantity that is tolerated, expressed in a percentage. The Hard Stop on Quantity field in the Inbound Order Lines (whinh2110m000) session indicates which action ERP LN carries out if the tolerance is not met. ERP LN retrieves the Maximum Quantity Tolerance from the Items - Purchase Business Partner (tdipu0110m000) session or from the Items - Purchase (tdipu0101m000) session if you release a purchase order or if a purchase schedule is released to Warehouse Management. Example receipt Maximum Quantity Tolerance: 10% Ordered quantity: 200 If the received quantity is more than 220 items, and the value of the Hard Stop on Quantity field in the Inbound Order Lines (whinh2110m000) session is: No, you can confirm the receipt. Warn, you can confirm the receipt, but you get a warning. Block, you cannot confirm the receipt. If the warehousing order is of the Issue transaction type, this field shows the greatest positive deviation from the ordered quantity that is tolerated to be shipped, expressed in a percentage. The Hard Stop on Quantity field in the Outbound Order Lines (whinh2120m000) session indicates which action ERP LN carries out if the tolerance is not met. ERP LN retrieves the Maximum Quantity Tolerance from the Items - Sales Business Partner (tdisa0510m000) session or from the Items - Sales (tdisa0501m000) session, if you release a sales order or a sales schedule to Warehouse Management. If the value of the Tolerance Type field in the Items - Sales Business Partner (tdisa0510m000) session or in the Items - Sales (tdisa0501m000) session is: Percentage, the value of the Maximum Quantity Tolerance field is equal to this percentage. Quantity, ERP LN determines the Maximum Quantity Tolerance, which is always expressed in a percentage, as follows:
    maximum tolerance (expressed as a quantity) / ordered quantity * 100%
Note If you manually create a warehouse order, you can also manually specify the Maximum Quantity Tolerance. Example issue Maximum Quantity Tolerance: 10% Ordered quantity: 200 If the advised quantity is more than 220 items, and the value of the Hard Stop on Quantity field in the Outbound Order Lines (whinh2120m000) session is: No, you can save the outbound advice. Warn, you can save the outbound advice, but you get a warning. Block, you cannot save the outbound advice.
Minimum Time Tolerance | The number of days that the supplier is allowed to deliver too early. Deliveries before this limit will be signaled or blocked.
Maximum Time Tolerance | The number of days that the supplier is allowed to deliver too late. Deliveries after this limit will be signaled or blocked.
Contract Date | The contract date for warehousing orders derived from orders linked to a contract.
Terms of Delivery | The terms or agreements concerning the delivery of goods.
Point of Title Passage | The point at which the legal ownership changes. At this point, the risk passes from the seller to the buyer.
Language | The language in which the company communicates and in which the work instructions are printed.
Reference |
Information | Enter any information in this field.
Assembly Kit | An order-dependent set of items that must be supplied together to the shop-floor warehouse.
Return Order | If this check box is selected, this order is a return order. The current check box is selected and disabled if one of the following is true: The order origin is Sales (Manual) and the inventory-transaction type is Receipt. The order origin is Purchase (Manual) and the inventory-transaction type is Issue. The current check box is enabled if the order origin is SFC Production (Manual).
Backflush Order | If this check box is selected, this order is a backflushing order. Note If the Suppress Backflushing Orders check box in the Inventory Handling Parameters (whinh0100m000) session is selected, backflushing orders are suppressed. Therefore, you cannot view these orders in the current session, unless they are not blocked and not shipped.
Blanket Order | If this check box is selected, this order is a blanket warehouse order. Related topics Blanket warehousing orders
Consignment | If this check box is selected, this order concerns consignment inventory. Default value ERP LN retrieves the default value, if specified, from the Consigned check box of the Items - Purchase Business Partner (tdipu0110m000) session. Related topics Consignment
Invoicing | If this check box is selected, the order must be invoiced at the moment of shipping, because an invoice relation is already defined.
Return Rejected Goods | If this check box is selected, the order is used to return rejected items to the business partner. Related topics Rejected inventory
Return Disposition Goods | If this check box is selected, the order is used to return disposition items to the business partner. Related topics Inventory disposition
Direct Material Supply Transfer | If this check box is selected, the order was generated by DMS planning. Related topics Direct material supply (DMS)
Ship-From
Ship-from Code | The company from where the goods are shipped. The ship-from company is the logistic company to which the warehouse in the Ship-from Code field belongs. Important! Only take into account this field if the warehousing order concerns a multicompany warehouse transfer. Related topics Multicompany warehouse transfers
Code | The ship-from type is used, together with the ship-from code, to identify the exact source of a warehousing order. The ship-from type can have the following values: Business Partner Warehouse Work Center Project
Code | A code used, together with the ship-from type, to identify the exact source of a warehousing order.
Address | The code of the address from where the goods are shipped. This is the address of the entity indicated in the Ship-from Code field.
Address | The address from which the goods are shipped.
Location | The location where the goods are shipped from. You can specify a location in the current field if both the warehouse and the item are location controlled, and the order origin is one of the following: Sales (Manual) Service (Manual) Maint. Sales (Manual) Maint. Work (Manual) SFC Production (Manual) ASC Production (Manual) Transfer (Manual) Purchase (Manual) Note You can only specify a location of type Pick or Bulk.
Delivery Date | The date for which delivery of a shipment is planned. Default value If ERP LN determines the planned delivery date and 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 as a whole day if the actual calendar indicates that time is available on that day. Example 1: lead times in hours System date/time (= order creation date/time): Wednesday 7:00:00. Outbound lead time: two hours. The actual calendar is available from Monday through Friday each week, and has an 8:00:00 start time and an 18:00:00 end time. According to the actual calendar, a calendar correction must be added: the actual time to which the outbound lead time will be added is Wednesday 8:00:00. Therefore, the default planned delivery date is Wednesday 10:00:00. Example 2: lead times in days System date/time (= order creation date/time): Wednesday 17:45:00. Outbound lead time: one day. The actual calendar is available from Monday through Friday each week, and has an 8:00:00 start time and an 18:00:00 end time. According to the actual calendar, no calendar correction is added. If, according to the actual calendar, some time is available on a day, the day is considered as a whole day. So, Wednesday is considered a whole day because 15 minutes are left. The default planned delivery date is the start time of (in this example) the next day, Thursday 8:00:00. Note Select Calculate to get a planned delivery date that is based on the planned receipt date. You can, for example, use this option if you only know the planned receipt date. Related topics Determination of lead time How ERP LN determines the calendar correction
Ship-To
Ship-to Code | The company to which the goods are shipped. The ship-to company is the logistic company to which the warehouse in the Ship-to Code field belongs. Important! Only take into account this field if the warehousing order concerns a multicompany warehouse transfer. A warehousing order is a multicompany warehouse transfer if: The inventory-transaction type is Transfer. The ship-from type and the ship-to type is Warehouse. The warehouses specified in the Ship-from Code and Ship-to Code fields belong to different logistic companies.
Code | The ship-to type is used, together with the ship-to code, to identify where goods are shipped to. The ship-to type can have the following values: Business Partner Warehouse Work Center Project
Code | A code used, together with the ship-to type, to identify where goods are shipped to.
Address | The code of the address to which the goods must be shipped. Note When you generate outbound advice, you can select all the warehousing orders for the same ship-to address to create a run.
Address | The address to which the goods must be shipped.
Location | The location where the goods are shipped to. You can specify a location in the current field if both the warehouse and the item are location controlled, and the order origin is one of the following: Sales (Manual) Service (Manual) Maint. Sales (Manual) Maint. Work (Manual) SFC Production (Manual) ASC Production (Manual) Transfer (Manual) Purchase (Manual) You can only specify a location of type Pick or Bulk. Note In a Shop Floor warehouse, you can only receive goods in Bulk locations. Therefore, if you ship goods to a Pick location in a Shop Floor warehouse, you cannot receive these goods in this warehouse.
Receipt Date | The date on which the goods are expected to arrive in the destination warehouse. Default value The default planned receipt date is calculated as follows:

                                        planned receipt date = PLD + TT + CC

                                              PLD
                                              Planned delivery date

                                              TT
                                              Transport time

                                              CC
                                              Calendar correction (ship-to)
ERP LN does not take into account the transport time if the warehousing order originates from a production order. If ERP LN determines the planned receipt date and 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 as a whole day if the actual calendar indicates that time is available on that day. Example 1: lead times in hours Planned delivery date: Wednesday 10:00:00 Transport time: eight hours The carrier's actual calendar has a 7:00:00 start time and a 17:00:00 end time. The ship-to's actual calendar has an 8:30:00 start time and an 18:00:00 end time. Both actual calendars are available from Monday through Friday each week. The carrier will carry the goods for seven hours on Wednesday (from 10:00:00 until 17:00:00) and for 1 hour on Thursday (from 7:00:00 till 8:00:00). So, according to the carrier's calendar, the planned receipt date is Thursday 8:00:00. However, if you also take into account the ship-to's actual calendar, the default planned receipt date is Thursday 8:30:00. Example 2: lead times in days Planned delivery date: Wednesday 16:00:00 Transport time: two days The carrier's actual calendar has a 7:00:00 start time and a 17:00:00 end time. The ship-to's actual calendar has an 8:30:00 start time and an 18:00:00 end time. Both actual calendars are available from Monday through Friday each week. If the actual calendar indicates that time is available on a day, the day is considered a whole day. So, Wednesday is considered a whole day according to the carrier's actual calendar because one hour remains. The transport will thus take place on Wednesday and Thursday. The default planned receipt date is Friday 7:00:00 according to the carrier's actual calendar. However, also taking into account the ship-to's actual calendar, the default planned receipt date is Friday 8:30:00. Note Choose Calculate to get a planned receipt date that is based on the planned delivery date. You can, for example, use this option if you only know the planned delivery date. Related topics Determination of transport time How ERP LN determines the calendar correction
Order Information
Office | A group of order numbers or document numbers starting with the same series code. Series identify orders with certain characteristics. For example, all sales orders handled by the large accounts department start with LA (LA0000001, LA0000002, LA0000003, and so on).
Warehousing Order Type | A code that identifies the type of a warehousing order. The default warehousing procedure that you link to a warehousing order type determines how the warehousing orders to which the order type is allocated are processed in the warehouse, although you can modify the default procedure for individual warehousing orders or order lines.
Office | The department that handles warehousing orders.
Item Transfer
From Item | The item that will be transferred to another item.
Into Item | The code of the item to which the original item is transferred.
Commands | Description
Create Return Order | ERP LN creates a regular warehouse transfer order for the items to be transported back to the warehouse specified in the Ship-From group box. The Return Order transports the items from the Ship-To warehouse back to the Ship-From warehouse. Example When the first warehouse transfer is from warehouse A to warehouse B and you create a Return warehouse transfer, ERP LN copies the warehouse transfer (same item, quantity and so on) and the transfer is from B to A.
Calculate Planned Delivery Date | Use this command to calculate the planned delivery date based on the planned receipt date using the following formula:

                                     PRD - CC - TT - CCsf

                                           PRD
                                           Planned receipt date

                                           CC
                                           Calendar correction (ship-to)

                                           TT
                                           Transport time

                                           CCsf
                                           Calendar correction (ship-from)
Note: When ERP LN calculates the planned delivery date and 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. Example 1: lead times in hours. Planned receipt date: Friday 17:30:00. Transport time (in hours): 10. The ship-to business partner's actual calendar has an 8:30:00 start time and a 17:00:00 end time. The carrier's actual calendar has a 7:30:00 start time and an 18:00:00 end time. The ship-from's actual calendar has an 8:00:00 start time and a 17:00:00 end time. These calendars are all available from Monday through Friday each week. According to the ship-to business partner's actual calendar, receipt cannot take place at Friday 17:30:00. Therefore the corrected planned receipt date is Friday 17:00:00. According to the carrier's actual calendar, the carrier will carry the goods 9.5 hours on Friday (from 7:30:00 until 17:00:00) and half an hour on Thursday (from 17:30:00 until 18:00:00). According to the ship-from's actual calendar, the goods cannot be delivered at Thursday 17:30:00. Therefore, the corrected planned delivery date is Thursday 17:00:00. Example 2: lead times in days. Planned receipt date: Friday 9:00:00. Transport time (in days): 2. The ship-to business partner's actual calendar has an 8:30:00 start time and a 17:00:00 end time. The carrier's actual calendar has a 7:30:00 start time and an 18:00:00 end time. The ship-from's actual calendar has an 8:00:00 start time and a 17:00:00 end time. These calendars are all available from Monday through Friday each week. According to the ship-to business partner's actual calendar, receipt can take place at Friday 9:00:00. Therefore, no calendar correction (ship-to) is needed. If the actual calendar indicates that time is available on a day, the day is considered a whole day. Thus, according to the carrier's actual calendar, Friday is considered a whole day, which means Friday and Thursday are transport days. According to the carrier's actual calendar, the planned delivery date is Thursday 7:30:00. However, taking into account the ship-from business partner's actual calendar, the planned delivery date is Wednesday 17:00:00 because Thursday at 7:30:00 the ship-from business partner's actual calendar is not open. Note If the planned receipt date is not specified, ERP LN sets both the planned receipt date and the planned delivery date to the current date. If the calculated planned delivery date is before the current date, ERP LN sets the planned delivery date to the current date. Related topics How ERP LN determines the calendar correction Determination of transport time
... | Start the Addresses (tccom4530m000) to select the ship-from address for the warehousing order.
... | Start the Addresses (tccom4530m000) to select the ship-to address for the warehousing order.
Remove Warehousing Orders | Start the Remove Warehousing Orders (whinh2250m000) session.
Print Warehousing Orders | Start the Print Warehousing Orders (whinh2400m000) session.
Print Warehousing Order Types | Start the Print Warehousing Order Types (whinh0410m000) session.
Generate Outbound Advice | Start the Generate Outbound Advice (whinh4201m000) session.
Process Outbound Advice | Start the Process Outbound Advice (whinh4200m000) session.
Release Outbound Advice | Start the Release Outbound Advice (whinh4202m000) session.
Shipment Lines | Start the Shipment Lines (whinh4131m000) session.
Warehousing Orders History | Start the Warehousing Orders History (whinh2550m000) session.
Lots | Start the Order - Lots (whltc3502m000) session.
Planned Inventory Transactions | Start the Order - Planned Inventory Transactions (whinp1501m000) session.
Inventory Transactions | Start the Item - Warehouse - Inventory Transactions (whinr1510m000) session.
Invy Receipt Transactions Consumption | Start the Inventory Consumptions (whina1514m000) session.
Inventory Commitment | Start the Inventory Commitments (whinp2100m000) session.
Generate Orders (KANBAN) | Start the Generate Orders (KANBAN) (whinh2200m000) session.
Generate Orders (TPOP) | Start the Generate Orders (TPOP) (whinh2201m000) session.
Easy Entry Warehousing Order | Start the Easy Entry Warehousing Order (whinh2202m000) session.
Serials | Start the Serial Tracking - Overview (whltc5515m000) session.
Negative Inventory Consumptions | Start the Negative Inventory Consumptions (whina1520m000) session.
Calculate Planned Receipt Date | Calculates the planned receipt date based on the planned delivery date using the following formula:

                                     planned receipt date = PDD + TT + CC

                                           PDD
                                           Planned delivery date

                                           TT
                                           Transport time

                                           CC
                                           Calendar correction (ship-to)
Note: When ERP LN calculates the planned receipt date and 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. Example 1: lead times in hours. Planned delivery date: Wednesday 10:00:00. Transport time (in hours): 8. The carrier's actual calendar has a 7:00:00 start time and a 17:00:00 end time. The ship-to business partner's actual calendar has an 8:30:00 start time and an 18:00:00 end time. Both actual calendars are available from Monday through Friday each week. The carrier will transport the goods for seven hours on Wednesday (from 10:00:00 until 17:00:00) and for one hour on Thursday (from 7:00:00 until 8:00:00). Thus, according to the carrier's calendar, the planned receipt date is Thursday 8:00:00. However, also, taking into account the ship-to business partner's actual calendar, the planned receipt date is Thursday 8:30:00. Example 2: lead times in days. Planned delivery date: Wednesday 16:00:00. Transport time (in days): 2. The carrier's actual calendar has a 7:00:00 start time and a 17:00:00 end time. The ship-to business partner's actual calendar has an 8:30:00 start time and an 18:00:00 end time. Both actual calendars are available from Monday through Friday each week. If the actual calendar indicates that time is available on a day, the day is considered a whole day. Thus, Wednesday is considered a whole day according to the carrier's actual calendar, because one hour is left. The transport will thus take place on Wednesday and Thursday. The default planned receipt date is Friday 7:00:00 according to the carrier's actual calendar. However, also, taking into account the ship-to business partner's actual calendar, the default planned receipt date is Friday 8:30:00. Note: If the planned delivery date is not specified, ERP LN sets the planned delivery date to the current date. Related topics How ERP LN determines the calendar correction Determination of transport time
Activities by Warehousing Order | Start the Activities by Warehousing Order (whinh2104m000) session.
Activate | Use this command to change the status of the selected order from Planned to Open. For more information, refer to Planned status for Warehousing order lines
Deactivate | Use this command to change the status of the selected order from Open to Planned. For more information, refer to Planned status for Warehousing order lines
Process | Process
Activate Warehousing Orders | Start the Activate Warehousing Orders (whinh2203m000) session.
Related Order | This command is available for multicompany transfers. Use this command to view the transfer order for the related company, which enables you to view information on the items to be transferred in the related company. If you are working in the from-company, click this command to view the related order in the to-company. If you access the order in the to-company, click this command to view the related order in the from-company. The order number of the transfer order for the related company can be different. The reason is that each company can have different number groups and series for transfer orders. If you create a transfer order to transfer items to a warehouse in a different company, ERP LN creates the transfer order for both the from-company and the to-company. The from-company is the issuing company and the to-company is the receiving company.