Inbound

The inbound process is used to receive and store goods in a warehouse. To receive and store goods in a warehouse, you can process the inbound order lines on which the goods are listed, or you can process the handling units used to pack the goods. Both inbound order lines and handling units are processed according to user-defined warehousing procedures. If you use handling units to process goods, the order lines related to the handling units are updated in the background.

• Run number

  A run number is a code assigned to a group of warehousing order lines when they are advised. LN assigns or generates a run number if a user does not manually enter or select a run number while he generates inbound or outbound advice for a group of warehousing order lines.

  For inbound movements, the user can generate storage lists and confirm storage lists by run. For outbound movements, the user can release outbound advice, generate picking lists, and confirm picking lists by run.

• Generate and put away inbound advice

  Inbound advice is a list generated by LN that indicates the location where received goods must be stored, taking into account storage conditions, blockings, and so on. Inbound advice consists of the instructions to move received items into a warehouse. An example of inbound advice line: Take 10 pieces of item A from location Receipt 3 and put them in location Bulk 5.

  Inbound advice is normally generated according to the warehousing procedure defined for the warehousing order lines related to the receipt lines, inspection lines, or handling units for which inbound advice must be created. You can also manually generate inbound advice. For non-location controlled warehouses, LN skips the inbound advice step.

• Overview of receipt and inbound inspection procedures

  The warehousing inbound flow comprises the following default procedures:

  • Receipt
  • Inspection

• Storage list

  A storage list states the warehouse or locations where goods must be stored. A storage list is used by warehouse personnel to place the received items in the correct location in the warehouse. The storage lists are shown for each run number and for each storage mission.

• Return certificates

  Return certificates are generated for receipts based on sales return orders. You can print a preliminary version of a return certificate before printing the final version that is sent to the customer.

• Peg distribution in the inbound and inspection processes

  Receiving project pegged goods into a warehouse results in inventory transactions that are based on the underlying peg distribution of the related receipt line. This results in an update of the pegged inventory levels. The planned quantity of the inbound order line is also updated, which includes the peg data. Planned inventory transactions are also generated for each peg.

• Additional information fields

  You can define additional information fields that can be linked to LN tables. The contents of these additional fields can be transferred between LN tables, which allows users to enter additional information in sales schedules or sales orders. The additional information on the warehouse order header can be retrieved from the originating object, for example, a purchase order or purchase schedule header, or specified manually.

• Lineside labeling

  Various fields of the sold-to business partner can be printed on container labels when the receipt of end items from production is confirmed. The purpose is to reduce mislabeling by attaching container labels during production or receipt rather than at the shipping dock.

  The sold-to business partner fields are retrieved from the demand order, for example, the sales order or sales schedule, for which the production order for the item was initiated.