| Additional information fields - Warehousing |  |
| The table below provides an overview of the tables in Warehousing to which you can link additional information fields. The table also contains the corresponding sessions which display the additional information fields. You can also edit the additional information fields using the sessions in the table below:
Table | Session | Description
--- | --- | ---
whinh200 | whinh2100m000 | Warehousing Orders
whinh250 | whinh2550m000 | Warehousing Orders History
whinh220 | whinh2120m000 | Outbound Order Lines
whinh270 | whinh2570m000 | Outbound Order Lines History
whinh430 | whinh4130m000 | Shipments
whinh450 | whinh4550s000 | Shipment History
whinh431 | whinh4131m000 | Shipment Lines
whinh451 | whinh4551s000 | Shipment Line History
whwmd530 | whwmd5130m000 | Handling Units
whwmd531 | Whwmd5531m000 | Handling Unit Version History
Additional information can be transferred from one table to another table. The following flows of additional information are supported in Warehousing: Header Flow: Warehousing Orders (whinh2100m000)-> Shipments (whinh4130m000)-> Handling Units (whwmd5130m000) The additional information on the warehouse order header can be retrieved from the initiating object, for example, a sales schedule header, or specified manually. The additional information is passed from the warehouse order header to the shipment header. Additional information is not overwritten during the transfer process. This rule applies at the level of individual fields. For example, in two warehouse orders, the first has additional field 1 populated and the second has additional field 2 populated. Both warehouse orders result in the same shipment. The shipment header will have additional field 1 populated from the first warehouse order and additional field 2 populated from the second warehouse order. The below table provides some possible scenarios, Warehouse Order 1 is the first order being 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
When handling units are in use, and handling units are created automatically for the shipment header during confirmation of the pick. The additional information can be passed from the shipment header to the generated handling unit. Line Flow: Outbound Order Line (whinh220) -> Shipment Line (whinh431) -> Handling Unit (whwmd530) 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. The additional information is then passed from the outbound order line to the shipment line. When handling units in stock are used in the outbound and shipment process, manually specified additional information can already be present at these handling units. The additional information of the shipment line will be 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 at individual additional information field level. The table below 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
Related topics Additional information fields |