Warehousing Orders (whinh2100m000)Use this session to view and maintain warehousing orders by order origin. Note Use the Maps section to view the location of the Ship-from Address and the Ship-to Address. You must select only one record at a time. For warehousing orders originating from other packages, you can only modify the data created in Warehousing. If the Warehousing Order History 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:
Note LN allows you to add cost items for the warehouse orders that have the origin Project (Manual) and Project Contract. The origin Project Contract is used for the orders that originate from the project contracts. For warehousing orders created in Warehousing, 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:
To adjust the warehousing procedure for individual warehousing orders, select Activities by Warehousing Order (whinh2104m000) from the appropriate 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 appropriate 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. Note Effectivity units of items that are not lot-controlled are not recorded in warehouse inventory.
Warehouse Order Order The origin of the order. The origin refers to the package
that initiated the warehousing order. The Transfer origin refers to Warehousing. When you use Budget Control, warehousing orders of the following origin are allowed:
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 Header Status The status of the warehouse order header.
Transaction Type A classification that is used to indicate the type of inventory
movement. The following inventory transaction types are available:
When you use Budget Control, any change in the Planned Delivery Date of all related inbound order lines is updated in the Budget Account Distribution (tcbgc1100m000) session for warehousing orders of transaction type Receipt Transactions and orders that have the following Order Origin:
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. When you use Budget Control, for manual warehousing orders, you must select the following parameter check boxes in the Warehousing Order Types (whinh0110m000) session:
Related Order/Company If the warehousing order concerns a goods transfer between
different companies, and the ship-from company and the ship-to company are not
the same, this field indicates the linked warehousing order of the other
company. Shipping 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. 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:
Order Information Order Date The date on which the warehousing order is generated or
registered. Office The department that handles warehousing orders. 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. Ship-From Ship-from 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:
Ship-from Code A code used, together with the ship-from type, to identify the
exact source of a warehousing order. Description The description or name of the code. Ship-from Address The address from where the goods are shipped. This is the
address of the entity indicated in the Ship-from Code field. 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:
Note You can only specify a location of type Pick or Bulk. Ship-from Item The item that will be transferred to another item. Revision The revision number of the order. 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:
LN does not take into account the transport time if the warehousing order originates from a production order. If LN determines the planned receipt date and the lead times are expressed in hours, 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, 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. Planned Delivery Date The date for which delivery of a shipment is planned. Default value If LN determines the planned delivery date and the lead times are expressed in hours, 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, 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. So, 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. 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:
LN does not take into account the transport time if the warehousing order originates from a production order. If LN determines the planned receipt date and the lead times are expressed in hours, 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, 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. Ship-To Ship-to 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:
Note For warehouse orders that have the origin Project (Manual), cost items are allowed only when the Ship-to is set to Business Partner. Ship-to Code A code used, together with the ship-to type, to identify where
goods are shipped to. Description The description or name of the code. Ship-to Address 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. 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:
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. Ship-to Item The code of the item to which the original item is transferred. Revision The revision number of the item. Item Transfer Assign Item Surcharge Specifies the way an item surcharge must be applied in case of item transfers. Freight Carrier 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 Binding If this check box is selected, The carrier selected in the Carrier 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 Warehousing. 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:
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. Motive of Transport motive of transport The value in this field is taken from the originating order of
the current warehousing order, or defaulted from the Default Order Types by Origin (whinh0120m000) session. This field is available if the
ship-from code listed on the order header is a warehouse for which the use of
delivery notes is enabled. Delivery Code delivery code The value in this field is taken from the originating order of the
current warehousing order, or defaulted from the Default Order Types by Origin (whinh0120m000) session. This field is available if the
ship-from code listed on the order header is a warehouse for which the use of
delivery notes is enabled. Kit Order for Kit If this check box is selected, the current warehousing order is a kit order. Main Item The main item of the sales order. When the sales order is
released to Warehousing, the value is retrieved from the Sales Order Main Items (tdsls4561m000) session. Description The description of the main item. Kit Item Quantity in Storage Unit The quantity of the subkit item, expressed in the storage unit. The value in this field is taken from the sales order line that
initiated the current warehousing order set. Note that the quantity of the components is listed on the related
outbound order lines. Miscellaneous Constraints Shipping Constraint The constraint/rules related to the shipment and delivery
of goods. For more information, refer to Shipping Constraints. Note
Tolerances 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 Quantity field in
the Inbound Order Lines (whinh2110m000) session indicates which action LN carries out if the
tolerance is not met. LN retrieves the Minimum Quantity Tolerance from the Item - Purchase Business Partner (tdipu0110m000) session or from the Item - Purchase (tdipu0101m000) session if you release a purchase order or if a purchase schedule is released to Warehousing. Note If the shipping constraint is Ship Set Complete or Ship Order Complete, the Minimum Quantity Tolerance is 0 percent. Example receipt Minimum Quantity Tolerance: 10% Ordered quantity: 200 If the received quantity is less than 180 items, and the value of the Quantity field in the Inbound Order Lines (whinh2110m000) session is:
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 Quantity field in
the Inbound Order Lines (whinh2110m000) session indicates which action LN carries out if the
tolerance is not met. LN retrieves the Maximum Quantity Tolerance from the Item - Purchase Business Partner (tdipu0110m000) session or from the Item - 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 Quantity field in the Inbound Order Lines (whinh2110m000) session is:
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 LN carries out if the tolerance is not met. LN retrieves the Maximum Quantity Tolerance from the Item - Sales Business Partner (tdisa0510m000) session or from the Item - Sales (tdisa0501m000) session, if you release a sales order or a sales schedule to Warehousing. If the value of the Tolerance Type field in the Item - Sales Business Partner (tdisa0510m000) session or in the Item - Sales (tdisa0501m000) session is:
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:
Min. 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. Miscellaneous Subcontracting Indicates if or how the warehousing order is involved in subcontracting. Allowed values The available values in this field pertain to the roles involved in subcontracting. Available values for the: To define these roles for a company, in the Concepts (Logistics) tab of the Implemented Software Components (tccom0500m000) session, select the Subcontracting with Material Flow (manufacturer) check box or the Subcontracting with Material Flow (subcontractor) check box. Note that if a company has both roles selected, the actual role depends on the role assumed when creating (or initiating the creation of) the warehousing order: is the warehousing order created by a subcontractor manufacturing a product or performing a service for the manufacturer, or by a manufacturer subcontracting services or products to the subcontractor? Contract Date The contract date for warehousing orders derived from orders linked to a
contract. Language The language in which the company communicates and in which the
work instructions are printed. Reference Any informative description field used to refer to, for example:
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. Landed Cost Classification Attribute that allows users to link a logistic transaction to a
specific landed costs set, overruling the landed costs settings
of that transaction. If required, users can specify a landed costs
classification and use this classification on the transaction. Note This optional field is only available if these conditions are met:
Options Options 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 current check box is enabled if the order origin is SFC Production (Manual). Rush Order If this check box is selected, the order is a rush order. 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. Blocked If this check box is selected, the order is blocked. Return Rejected Goods If this check box is selected, the order is used to
return rejected items to the business partner. Return Disposition Goods If this check box is selected, the order is used to
return disposition items to the business partner. Consignment If this check box is selected, this order concerns consignment inventory. Default value LN retrieves the default value, if specified, from the Consigned check box of the Item - Purchase Business Partner (tdipu0110m000) session. Invoicing If this check box is selected, an internal invoicing
relation is present for the departments involved in receiving the goods listed on the
current warehousing order. If the goods are company owned, LN creates an invoice if the receipt is confirmed. Text Header Text If this check box is selected, a text is created for
the header of the warehousing order. Click the text button to create a header
or footer text for the order. Footer Text If this check box is selected, a text is created for
the footer of the warehousing order. Click the text button to create a header
or footer text for the order. Additional Information Additional Information User-defined fields that can be linked to LN tables. The contents of additional fields can be transferred between LN tables. Additional information fields are meaningless to LN as no functional logic is linked to the contents of these fields.
Inbound Order Lines Starts the Warehousing Orders (whinh2100m000) details session. Inbound Order Lines Starts the Inbound Order Lines (whinh2110m000) session. Outbound Order Lines Starts the Outbound Order Lines (whinh2120m000) session. Calculate Planned Receipt Date Calculates the planned receipt date based on the planned
delivery date using the following formula:
Note: When LN calculates the planned receipt date and the lead times are expressed in hours, 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, 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, LN sets the planned delivery date to the current date. Calculate Planned Delivery Date Calculates the planned delivery date based on the planned
receipt date using the following formula:
Note: When LN calculates the planned delivery date and the lead times are expressed in hours, 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, 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
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. If the header status is Planned, Modified or when the order lines are set to Planned status, you can activate the order from the
warehouse order header. 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. You can deactivate the order at header level
only when the header status is Open or Modified and when at least one of the lines is set to Open status. If you deactivate, the order line status changes from Open to Planned. Process Use this command to process the selected order lines or the
order lines of the selected orders. You must use this command to start
processing warehousing orders whose first activity is set to automatic
processing and that are manually created or originating from Project. In addition, if normally the first activity for a particular warehousing order type is performed manually, but you change this to automatic for a particular order or order line, you must click the Process button to start processing the order or order line. Activate Start the Activate Warehousing Orders (whinh2203m000) session. Remove Closed Warehousing Orders Start the Remove Closed Warehousing Orders (whinh2250m000) session. Serials Start the Serial Tracking - Overview (whltc5515m000) session. Landed Cost Lines Start the Landed Cost Lines (tclct2100m000) session. Landed Costs by Warehousing Order Start the Landed Cost Lines by Warehouse Order (tclct2100m500) session to view all landed costs that
are linked to the warehouse order. Recalculate Landed Costs Start the Recalculate Landed Costs (tclct2800s000) session. The availability of this command depends on the Recalculate Landed Costs setting in the Landed Costs Parameters (tclct0100m000) session. Print Warehousing Orders Starts the Print Warehousing Orders (whinh2400m000) session. By default, LN starts this session
to print the report.
| |||||||||||||||||||||||||||||