| Easy Entry Warehousing Order (whinh2202m000) |  |
| Use this session to easily create a warehousing order with a single order line and with one of the following order origins: Sales (Manual) Purchase (Manual) Service (Manual) Maintenance Sales (Manual) Maintenance Work (Manual) SFC Production (Manual) Transfer (Manual) After you create a warehousing order and an outbound order line and/or an inbound order line, information on the created warehousing order is printed on a report and/or an error is printed on a report. Note You cannot create warehousing orders for a project with the current session. In the current session you can only create a warehousing order for an item of one of the following item types: Purchased Manufactured Use the Warehousing Orders (whinh2100m000) session to create warehousing orders with more than one order line.
Fields | Description
Order | The origin of the order. Allowed values Sales (Manual) Purchase (Manual) Service (Manual) Maintenance Sales (Manual) Maintenance Work (Manual) SFC Production (Manual) Transfer (Manual)
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. Allowed values Receipt Issue Transfer The Receipt and Issue inventory-transaction types are only applicable for the following order origins: Sales (Manual) Purchase (Manual) Service (Manual) SFC Production (Manual) The Transfer inventory-transaction type is only applicable for the Transfer (Manual) order origin. Transaction type
Office | The department for handling warehousing orders. The order origins and department types correspond as follows: Sales (Manual) and Sales Office Purchase (Manual) and Purchase Office Service (Manual) and Service Department SFC Production (Manual) and Work Center If the order origin is Transfer (Manual), the current field is disabled.
Rush Order | If this check box is selected, the order is a rush order.
Item | In ERP LN, the raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, sold, and so on. An item can also represent a set of items handled as one (kit), or exist in multiple product variants. You can also define nonphysical items, which are not held in inventory but can be used to post costs or to invoice services to customers. Examples of nonphysical items: Cost items (for example, electricity) Service items Subcontracting services List items (menus/options) You can only enter items of the following item types: Purchased Manufactured
Quantity Ordered in Order Unit | The unit in which the quantity of goods stored is expressed. Example Storage unit: box Inventory unit: liter
Ordered Quantity in Order Unit | The ordered quantity expressed in the storage unit.
Quantity Ordered in Inventory Unit | The unit of measure in which the inventory of an item is recorded, such as piece, kilogram, box of 12, or meter. The inventory unit is also used as the base unit in measure conversions, especially for conversions that concern the order unit and the price unit on a purchase order or a sales order. These conversions always use the inventory unit as the base unit. An inventory unit therefore applies to all item types, also to item types that cannot be kept in stock.
Ordered Quantity in Inventory Unit | The ordered quantity expressed in the inventory unit.
Lot | The specific conditions that can be established for lot items on order lines. These conditions are: Any The goods to be received or shipped are not subject to specific lot conditions. You can use more than one lot. Same You can select any lot for receipt or shipment, but the entire receipt or shipment must have the same lot. Specific You can receive or ship only one, specific lot. Note If the item is not lot controlled, this field is unavailable. Possible values
Lot | A number of items produced and stored together that are identified by a (lot) code. Lots identify goods. Note The current field is not available if: The item is not lot controlled. The item is lot controlled and the Lot field's value is Any or Same.
Serial Number | The serial number of the item for which you want to generate the warehousing order.
Effectivity Unit | The effectivity unit of the item.
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) Maintenance Sales (Manual) Maintenance Work (Manual) SFC Production (Manual) ASC Production (Manual) Transfer (Manual) Purchase (Manual) Note You can only specify a location of type Pick or Bulk.
Planned Delivery Date | The date for which delivery of a shipment is planned. Default value The default planned delivery date is the system date/time. However, if the ship-from type is Warehouse, the default planned delivery date is calculated as follows:
    System date/time + outbound lead time
If the order origin is Transfer or Transfer (Manual), and the transaction type is Transfer, ERP LN retrieves the outbound lead time from the Warehouse - Item (whwmd2110s000) session.
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) Maintenance Sales (Manual) Maintenance Work (Manual) SFC Production (Manual) ASC Production (Manual) Transfer (Manual) Purchase (Manual) Note You can only specify a location of type Pick or Bulk.
Planned 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 delivery date + transport time
Note ERP LN calculates the transport time based on the distance between the ship-from address and the ship-to address.
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 Warehousing. 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 Warehousing. 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 Warehousing. The value of the Tolerance Type field in the Items - Sales Business Partner (tdisa0510m000) session or in the Items - Sales (tdisa0501m000) session is: Maximum tolerance (expressed as a quantity) / Ordered quantity x 100% Note If you manually create a warehouse order, you can also manually specify the Maximum Quantity Tolerance. 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: 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.
Delivery Terms | 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.
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. Default value ERP LN retrieves the order-origin-dependent default warehousing-order type from the Default Order Types by Origin (whinh0120m000) session.
Purchase Order Series | A group of first free number series that you can assign to a specific use. For example, you can assign a number group to: Business partner codes Purchase contracts Sales orders Production orders Service orders Warehousing orders Freight orders Within a number group you can define multiple series. Each series is identified by the series code. The series numbers that ERP LN generates consist of the series code followed by the first free number in the series. Series codes of the same number group have the same length. Default value By default, ERP LN retrieves the number group from the Default Order Types by Origin (whinh0120m000) session.
Series | 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). Default value By default, ERP LN retrieves the series from the Default Order Types by Origin (whinh0120m000) session.
Process Order | If this check box is selected, warehousing orders entered in the current session are processed automatically according to the activities as specified for the warehousing-order type. The automatically processing of the activities takes place as follows: The inbound activities are processed automatically upto and including the confirmation of the receipt in the Warehouse Receipt (whinh3512m000) activity. You must manually carry out all specified inbound activities that follow upon the Warehouse Receipt (whinh3512m000) activity in the warehousing-order type. The outbound activities are all processed automatically. If this check box is cleared, you must manually carry out the activities as specified in the warehousing order type for warehousing orders entered in the current session.
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. Purchase (Manual) and the inventory transaction type is Issue. The order origin is Service (Manual) and the inventory transaction type is Receipt. The order origin is Maintenance Sales (Manual) and the inventory transaction type is Receipt. The order origin is Maintenance Work (Manual) and the inventory transaction type is Receipt. The current check box is enabled if the order origin is SFC Production (Manual).
Rush Order | If this check box is selected, this order is a rush order.
Header Reference | The reference of the warehousing order.
Order Price | The price of one item to be received or issued. Default value The default order price is the fixed transfer price. ERP LN retrieves the fixed transfer price from the Cost Price Calculation module in Manufacturing. You can only specify or modify the order price if the Use Warehouse Order Price check box in the current session is selected. If the Use Warehouse Order Price check box is cleared, no order price is specified in the current field.
Order Price | The currency in which the order price is expressed. Default value The default currency is the local currency of the financial company that is linked to the enterprise unit of the warehouse to which the transfer takes place. ERP LN retrieves the local currency from the Companies (tcemm1170m000) session. The current field is available if the Order Price field is available. If the outbound-order line concerns a transfer between two warehouses and an invoice relation that is based on the commercial price exists between the two warehouses, the current field is unavailable and ERP LN retrieves the currency from the Goods Transfer (tcemm2150m000) session.
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 The ship-from type is determined by the combination of order origin and inventory-transaction type. Possible values
Code | A code used, together with the ship-from type, to identify the exact source of a warehousing order. If the ship-from type is Warehouse, you can only specify a warehouse of the following types in the current field: Normal Shop Floor Service Consignment (Not Owned) Consignment (Owned) If the ship-from type is Business Partner, the ship-from code that you can specify in the current field depends on the order origin and the inventory-transaction type: If the order origin is Sales (Manual), you can only specify a ship-to business partner. If the order origin is Purchase (Manual), you can only specify a ship-from business partner. If the order origin is Service (Manual), you can only specify a ship-to business partner. If the ship-from type is Work Center, you can only specify a department of type Work Center in the current field.
Code | The logistic company to which the ship-from warehouse in the Code field belongs. Note Only take this field into account if the warehousing order concerns a multicompany warehouse transfer. A warehousing order is a multicompany warehouse transfer if: The order origin is Transfer (Manual). The inventory-transaction type is Transfer. The ship-from type and the ship-to type are Warehouse. The warehouses specified in the Ship-from Code and Ship-to Code fields belong to different logistic companies.
Order | Zoom to the Warehousing Orders (whinh2100m000) to select the warehousing order for which you want the inbound order line and/or the outbound order line to be generated.
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 The ship-to type is determined by the combination of order origin and inventory-transaction type. Possible values
Code | A code used, together with the ship-to type, to identify where goods are shipped to. If the ship-to type is Warehouse, you can only specify warehouse of the following types in the current field: Normal Shop Floor Service Consignment (Not Owned) Consignment (Owned) If the ship-to type is Business Partner, the ship-to code that you can specify in the current field depends on the order origin and the inventory-transaction type: If the order origin is Sales (Manual), you can only specify a ship-to business partner. If the order origin is Purchase (Manual), you can only specify a ship-from business partner. If the order origin is Service (Manual), you can only specify a ship-to business partner. If the ship-to type is Work Center, you can only specify a department of type Work Center in the current field.
Code | The logistic company to which the ship-to warehouse in the Code field belongs. Note Only take this field into account if the warehousing order concerns a multicompany warehouse transfer. A warehousing order is a multicompany warehouse transfer if: The order origin is Transfer (Manual). The inventory-transaction type is Transfer. The Code and the Code is Warehouse. The warehouses specified in the Code field and the Code field belong to different logistic companies.
Order Amount | The order amount of the inbound-order line. ERP LN calculates the order amount as follows:
    order amount = order quantity (in inventory unit) * order price.
Line Reference | The reference of the warehousing-order line.
Use Warehouse Order Price | If this check box is selected, ERP LN uses the Order Price, as specified in the current session, for the financial transactions related to the warehousing-order line. Default value If the order origin is Transfer (Manual), the current check box is by default cleared. If the order origin is one of the following and the warehousing order does not concern a return order, the current check box is by default selected: Sales (Manual). Purchase (Manual). Service (Manual). Maintenance Work (Manual). SFC Production (Manual). You can only specify or modify the order price if the current check box is selected. The current check box is only available if the warehousing order does not concern a return order (the Return Order check box in the current session is cleared) and the order origin is: Transfer (Manual), the outbound-order line concerns a transfer between two warehouses, and no invoice relation exists between the two warehouses. Transfer (Manual), the outbound-order line concerns a transfer between two warehouses, and an invoice relation that is based on the commercial price exists between the two warehouses. Purchase (Manual). Service (Manual) and the warehousing order's inventory-transaction type is Receipt. Maintenance Sales (Manual) and the warehousing order's inventory-transaction type is Receipt. Maintenance Work (Manual) and the warehousing order's inventory-transaction type is Receipt. SFC Production (Manual) and the warehousing order's inventory-transaction type is Receipt. Invoice relationship ERP LN only uses the commercial price if an entity-entity releationship is defined between the ship-from entity and the ship-to entity of the warehousing order. You can define such a relationship in the Entity - Entity Relationships (tcemm2110m000) session. To this relationship, you can link an application process of type Goods Transfer. You can specify a goods transfer relationship in the Goods Transfer (tcemm2150m000) session. The goods transfer contains information about: The invoice relation between the two entity types. The price type; Commercial Price or Valuation Price.
Commands | Description
Calculate Delivery Date | Calculates the planned receipts date based on the planned delivery date with the following formula:
    planned delivery date + transport time + 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'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 one hour on Thursday (from 7:00:00 intil 8:00:00). So, according to the carrier's calendar, the planned receipt date is Thursday 8:00:00. But, also taking into account the ship-to'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'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 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. But, also taking into account the ship-to'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
Calculate Receipt Date | Calculates the planned receipts date based on the planned delivery date with the following formula:
    planned delivery date + transport time + 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'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 one hour on Thursday (from 7:00:00 intil 8:00:00). So, according to the carrier's calendar, the planned receipt date is Thursday 8:00:00. But, also taking into account the ship-to'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'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 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. But, also taking into account the ship-to'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