Additional information fields in Warehousing

The use of additional information fields is supported in various database tables in Warehousing.

The table lists the database tables in Warehousing to which you can link additional information fields. The table also contains the corresponding sessions which display the additional information fields:

Table Session
whinh200 Warehousing Orders (whinh2100m000)
whinh250 Warehousing Orders History (whinh2550m000)
  Outbound
whinh220 Outbound Order Lines (whinh2120m000)
whinh270 Outbound Order Lines History (whinh2570m000)
whinh430 Shipments (whinh4130m000)
whinh450 Shipment History (whinh4550s000)
whinh431 Shipment Lines (whinh4131m000)
whinh451 Shipment Line History (whinh4551s000)
  Inbound
whinh210 Inbound Order Lines (whinh2110m000)
whinh260 Inbound Order Lines History (whinh2560m000)
whinh312 Warehouse Receipt Lines (whinh3512m100)
  Receipt Lines (whinh3112s000)
whinh362 Receipt Lines History (whinh3562m000)
  Handling units
whwmd530 Handling Units (whwmd5130m000)
whwmd531 Handling Unit Version History (whwmd5531m000)

In the details session of the corresponding sessions and in the Extended Additional Information (tcstl2110m000) session, you can specify or modify the information in the additional information fields.

Additional information definition levels

The additional information fields can be defined for these additional information definition levels:

Transferring additional information

The information in the additional fields can be transferred to additional information fields in other sessions. For example, if you specified a value in additional information field ConsumptionPoint in the Warehousing Orders (whinh2100m000) session, this value is transferred to the additional information field ConsumptionPoint in the Shipments (whinh4130m000) session.

These additional information flows are supported in Warehousing:

  • Header flow outbound

    Originating Sales Control or Project object, or manual entry --> Warehousing Orders (whinh2100m000)-> Shipments (whinh4130m000)-> Handling Units (whwmd5130m000)
  • Line flow outbound

    Originating Sales Control or Project object, or manual entry --> Outbound Order Lines (whinh2120m000)-> Shipment Lines (whinh4131m000)-> Handling Units (whwmd5130m000)
  • Header flow inbound

    Originating Project or Purchase Control object, or manual entry -> Warehousing Orders (whinh2100m000)
  • Line flow inbound

    Originating Project or Purchase Control object, or manual entry Inbound Order Lines (whinh2110m000)-> Warehouse Receipt Lines (whinh3512m100) or Receipt Lines (whinh3112s000)-> Handling Units (whwmd5130m000)
Note: 

The information can only be transferred if all tables involved contain identical additional field formats and field names. For example, to enable the value of additional information field ConsumptionPoint of the string format to be transferred through the header flow, the whinh200, whinh430 and whwmd530 tables must contain a string field named ConsumptionPoint.

Header flow outbound: Originating Sales Control or Project object, or manual entry Warehousing Orders (whinh2100m000)-> Shipments (whinh4130m000)-> Handling Units (whwmd5130m000)

The additional information on the warehouse order header can be retrieved from the originating object, for example, a sales schedule header, or specified manually. The additional information is transferred from the warehouse order header to the shipment header.

Additional information is not overwritten during the transfer process. This rule applies to the individual field level. For example, two warehouse orders are available. For the first warehousing order, a value is specified in additional field 1. For the second, a value is specified in additional field 2. Both warehouse orders result in the same shipment. The shipment header displays the value of additional field 1 from the first warehouse order and the value of additional field 2 from the second warehouse order.

The following table lists a few scenarios. Warehouse Order 1 is the first order that is linked to the shipment:

Warehouse Order 1 Warehouse Order 2 Shipment
Content Field 1 Content Field 2 Content Field 1 Content Field 2 Content Field 1 Content Field 2
Sample_x Sample_y Sample_z   Sample_x Sample_y
    Sample_q Sample_r Sample_q Sample_r
Sample_s   Sample_q Sample_r Sample_s Sample_r

If handling units are used, and are created automatically for the shipment header during the confirmation of the picking list, the additional information can be transferred from the shipment header to the generated handling unit.

Line flow outbound: Originating Sales Control or Project object, or manual entry -> Outbound Order Lines (whinh2120m000)-> Shipment Lines (whinh4131m000)-> Handling Units (whwmd5130m000)

The additional information on the outbound order line can be retrieved from the initiating object, for example, a sales schedule line, or specified manually for the manual warehouse order types. This additional information is transferred from the outbound order line to the shipment line.

When handling units from stock are used in the outbound and shipment processes, additional information that is manually specified can already be present for these handling units. The additional information of the shipment line is merged with the additional information of the handling unit.

Existing additional information of the handling unit is not overwritten by additional information from the shipment line. This rule applies to the individual field level. The table outlines some scenarios:

Shipment Line Handling Unit before merge Handling Unit after merge
Content Field 1 Content Field 2 Content Field 1 Content Field 2 Content Field 1 Content Field 2
Sample_x Sample_y     Sample_x Sample_y
Sample_x Sample_y Sample_q   Sample_q Sample_y
Sample_x Sample_y Sample_q Sample_r Sample_q Sample_r

Header flow inbound: Originating Project or Purchase Control object, or manual entry -> Warehousing Orders (whinh2100m000)

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. The additional information field contents are not transferred from the warehouse order header to the inbound order lines, receipt lines or handling units.

Line flow inbound: Originating Project or Purchase Control object, or manual entry -> Inbound Order Lines (whinh2110m000)-> Receipt Lines (whinh3112s000)-> Handling Units (whwmd5130m000)

The additional information of the inbound order lines is retrieved from the originating purchase order line or purchase schedule, or entered manually. The additional information is then transferred from the inbound order line to the receipt line. This is done when the order line is linked to the receipt.

If handling units are used, the additional information can be transferred from the receipt line to the linked or generated handling units in the Handling Units (whwmd5130m000) session.

Handling units can be linked to an inbound order line before the inbound order line is linked to the receipt line. These handling units can contain additional information. If the handling units are linked to receipt lines that also contain additional information, the additional information of the inbound order-line handling unit is merged with the additional information of the receipt line. The additional information of the handling unit is not overwritten with the additional information of the receipt line.

Print Labels (whwmd5430m100)

If additional information fields are present for the handling unit, outbound order line, or shipment line for which labels are printed, the descriptions of the additional information fields are also printed.

Integration with Quality

For inbound order inspections created in Quality that are linked to warehousing inspections, the additional information fields are retrieved from the related Warehousing inbound order line.

For outbound order inspections in Quality, the additional information fields are retrieved from the outbound order line.

Additional information fields are not available for Warehousing inspections.