Warehouse Data Collection Process

General Information

All the processes available in the Warehouse Data Collection window can be configured. By configuring the processes, different behavior can be achieved depending on the specific process features. Each of the available processes is described below. For general configuration options, see the Warehouse Data Collection Configuration About description.  

Add Handling Unit to Shipment

The ADD_HANDLING_UNIT process ID identifies the Add Handling Unit to Shipment process in the Warehouse Data Collection window. The standard window for this is the Shipment/Handling Unit Structure tab. With the Warehouse Data Collection A process, the Add Handling Units activity can be performed. Using this process it is also possible to create SSCC, Alt Transport Label ID and to print the Handling Unit Label.

The data items in the Add Handling Unit to Shipment process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CREATE_SSCC data item, the value will be set to No automatically if a SSCC has previously been entered. If the handling unit basic data for a handling unit type ID has Generate SSCC enabled, the value will be set to Yes automatically and if Generate SSCC is not enabled, the value will be set to No automatically.
• When the Use Automatic Value field is set to Fixed on the SSCC data item, the value will be set to Null automatically if Generate SSCC has previously been entered with the value Yes. If the number of units has previously been entered with a value greater than 1, the value will be set to Null automatically.
• When the Use Automatic Value field is set to Fixed on the PARENT_HANDLING_UNIT_ID data item, the value will be set to Null automatically if a SHIPMENT_ID without any existing handling units connected to it has been entered before.
• When the Use Automatic Value field is set to Fixed on the NO_OF_HANDLING_UNIT_LABELS data item, it will be given an automatic value according to the handling unit basic data in the Handling Unit Type window.
• The following data items are only used to filter out a SHIPMENT_ID: DELIVER_TO_CUSTOMER_NO, SHIPMENT_TYPE, SHIP_VIA_CODE, FORWARD_AGENT_ID, PARENT_CONSOL_SHIPMENT_ID and SHIP_ADDR_NO.

The Add Handling Unit to Shipment process does not support the following:

• Creating more than one level at the time in the handling unit structure, even when using loops, since the parent handling unit has to be created before a child unit can be connected to it. By running the process multiple times, a multilevel handling unit structure can be created.

Change Parent Handling Unit in Shipment

The CHG_PARENT_HANDLING_UNIT_SHIP process ID identifies the Change Parent Handling Unit in Shipment process in the Warehouse Data Collection window. The standard window for this is the Shipment/Handling Unit Structure/Handling Units tab. With the Warehouse Data Collection process, the Change Parent Handling Unit ID activity can be performed. Using this process it is possible to identify the handling unit and the new parent handling unit via handling unit ID, SSCC or the alternate transport label ID. 

The data items in the Change Parent Handling Unit in Shipment process will behave according to the following:

• When setting up the configuration one decides if the HANDLING_UNIT_ID, SSCC or ALT_TRANSPORT_LABEL_ID should be used to identify the handling unit. Data items that are not used for identifying the handling unit is placed after the identifying data item in the configuration using the Input Order field, the Use Automatic Value field is set to Fixed. If one also wants to hide data items that are not used for identifying the handling unit, Hide Line field is set to Always.
• When setting up the configuration one decides if the PARENT_HANDLING_UNIT_ID, PARENT_SSCC or PARENT_ALT_TRANSPORT_LABEL_ID should be used to identify the new parent handling unit. Data items that are not used for identifying the new parent handling unit is placed after the identifying data item in the configuration using the Input Order field, the Use Automatic Value field is set to Fixed. If one also wants to hide data items that are not used for identifying the new parent handling unit, Hide Line field is set to Always.   
• The following data items are only used as filters: SHIPMENT_ID and PARENT_CONSOL_SHIPMENT_ID.

Note that:

• The ALT_TRANSPORT_LABEL_ID and PARENT_ALT_TRANSPORT_LABEL_ID data item only can identify a handling unit if unique strings are used.

Count Inventory Part

The COUNT_PART process ID identifies the Count Inventory Part process in the Warehouse Data Collection window. The standard window for is the Count per Inventory Part window. With the Warehouse Data Collection process, the Report Counting activity can be performed.

The data items in the Count Inventory Part process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit-enabled.
• When the Use Automatic Value field is set to Fixed on the SERIAL_NO data item, it will be given the value "*" automatically, if the data item PART_NO is placed before and the value entered for PART_NO is not serial-traced in inventory.
• When the Use Automatic Value field is set to Fixed on the LOT_BATCH_NO data item, it will be given the value "*" automatically, if the data item PART_NO is placed before and the value entered for PART_NO is not lot/batch traced.
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value "0" automatically, if no project exists.
• When the Use Automatic Value field is set to Fixed  on the ENG_CHG_LEVEL data item will be given the value “1” automatically, if the data item PART_NO is placed before and the value entered for PART_NO only have one Rev No/EC.

The Count Inventory Part process has specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Count Inventory Part process does not support the following:

• Pallets
• Identifying serial numbers of part numbers that are serial-traced at receipt (but not serial-traced in inventory).
• The process will not give all values automatically when the Use Automatic Value is set to Fixed.

Count per Count Report

The COUNT_PER_COUNT_REPORT process ID identifies the Count per Count Report process in the Warehouse Data Collection window. The standard window is the Count per Count Report window. With the warehouse data collection process, the Report Using Counting Report activity can be performed. If a counted quantity has been entered as a sequence number on the count report, the sequence number is considered as counted and the record will no longer be visible in the Warehouse Data Collection process.

The data items in the Count per Count Report process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit-enabled.
• The user has to enter the QTY_COUNT1 data item. This value will not be given automatically if the Use Automatic Value field is set to Fixed .
• The CONFIRM data item is an enumeration with the values Yes and No. If Yes is entered, the Confirmed check box in the Count per Count Report window is selected. If No is selected, the check box is left cleared.
• When the INV_LIST_NO and SEQ data items are entered, one unique line on the count report is identified and all the data items can be given automatically (Except QTY_COUNT1 and CATCH_QTY_COUNTED).
• When the BARCODE_ID data item is used and INV_LIST_NO and SEQ have been identified it is possible to enter “0” to set the quantity to 0. This can be used when the Barcode ID is missing.

The Count per Count Report process has specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

Count per Count Report process does not support the following:

• Pallets
• Identifying serial numbers of part numbers that are serial-traced at receipt (but not serial-traced in inventory).

Delivery Confirmation of Customer Order

The DELIVERY_CONFIRMATION process ID identifies the Delivery Confirmation of Customer Order process in the Warehouse Data Collection window. The standard window is the Delivery Confirmation of Customer Orders window. With the Warehouse Data Collection process, the Delivery Confirmation activity can be performed. When the session is started, the selected site is used as a filter for the customer order deliveries. For more explanation, see the Warehouse Data Collection About description.

The data items in the Delivery Confirmation of Customer Order process will behave according to the following:

• When the user reaches the signature data item in the process the signature pane will open and the delivery confirmation can be signed.

The Delivery Confirmation of Customer Oder process has process specific details that can be enabled:

• Connect signature (media) to Customer Order Object in Media Library.
• Connect signature (media) to Customer Order Delivery Note Object in Media Library.

Issue of Material Requisition Line

The ISSUE_MATERIAL_REQUIS_LINE process ID identifies the Issue Material Requisition Line process in the Warehouse Data Collection window. The standard window is the Material Requisition window. With the Warehouse Data Collection process, an internal issue of material can be performed. When the session is started, the selected site is used as a filter for the material requisition line.

• The data item SERIAL_NO will not be asked for if the data item PART_NO is placed before and the data entered is not serial-traced in inventory.
• The data item LOT_BATCH_NO will not be asked for if the data item PART_NO is placed before and the data entered is not lot-batch-traced.
• The data item CATCH_QUANTITY will not be asked for if the data item PART_NO is placed before and the data entered is not catch-unit-enabled.

The Issue of Material Requisition Line process has specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.
• If the ISSUE_UNRESERVED_MATERIAL process detail is enabled, the process will allow performing issue of material requisition lines with status Released.

Issue of Material Requisition Line process does not support the following:

• Pallets

Kanban Replenishment Request

The KANBAN_REPLENISHMENT_REQUEST process ID identifies the process Kanban Replenishment Request in the Warehouse Data Collection window. With this process, the user can perform a replenishment request for an inventory part. The system will create the respective replenishment order in the background. (i.e., shop order requisition, shop order, purchase requisition, purchase order, or production line schedule for the part with a quantity equal to the value of Qty per Kanban field). The same validations apply for Kanban Replenishment Request function in Warehouse Data Collection as when executing the same in the IEE client.

The data items in Kanban Replenishment Request process will behave according to the following:

• The BARCODE_ID data item could be scanned or manually entered by the user.
• The PART_NO is unique for the identified barcode ID if the barcode ID is identified at the start of the process.
• The SUPPLY_TO_LOCATION_NO unique for the identified barcode ID if the barcode ID is identified at the start of the process.

Manual Issue Shop Order

The MANUAL_ISSUE_SHOP_ORDER process ID identifies the Manual Issue Shop Order process in the Warehouse Data Collection window. The standard window is the Manual Issue Shop Order window. With the Warehouse Data Collection process, the Issue Components Manually activity can be performed. The available shop orders that components can be issued for, are filtered on the selected site and status on the shop order. The status should be Released or Started. In the process, barcode ID can be used to identify the COMPONENT_PART_NO data item.

The data items in the Manual Issue Shop Order process will behave according to the following:

• The PART_NO data item could be used as a filter for the available shop orders, if placed before. If the PART_NO data item is placed after the shop order key, it will be set automatically by the process.

The data items in the Manual Issue Shop Order process will behave according to the following:

• When the Use Automatic Value  field is set to Fixed  on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch unit enabled.
• The SERIAL_NO data item will not be asked for, if the PART_NO data item is placed before, and the data entered is not serial-traced in inventory.
• The LOT_BATCH_NO data item will not be asked for, if the PART_NO data item is placed before and the data entered is not lot/batch traced.
• The ENG_CHG_LEVEL data item will not be asked for, if the PART_NO data item is placed before, and the data entered is not lot/batch traced.

The Manual Issue Shop Order process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.
• If the DISPLAY_LOCATION_DESCRIPTION process detail is enabled, the location description will be included in the Description field of the List of Values for locations.
• If the DISPLAY_QTY_AVAILABLE process detail is enabled, the quantity available for the component part on this location will be included in the Description field of the List of Values for locations.
• If the DISPLAY_QTY_AVAILABLE_HEADER process detail is enabled, the header AVAIL: will be included in the Description field of the List of Values for locations (right before quantity available).
• If the DISPLAY_QTY_RESERVED process detail is enabled, the quantity reserved for the component part on this location will be included in the Description field of the List of Values for locations.
• If the DISPLAY_QTY_RESERVED_HEADER process detail is enabled, the header RES: will be included in the Description field of the List of Values for locations (right before quantity reserved).

The Manual Issue Shop Order process does not support the following:

• Pallets.

Manual Issue Work Order

The MANUAL_ISSUE_WORK_ORDER process ID identifies the Manual Issue Work Order process in the Warehouse Data Collection window. The standard dialogue for this is Manual Issue Work Order. With the Warehouse Data Collection process the activity Issue Material can be performed. The available work orders where material lines are planned are filtered on the selected site and the status on the work order, the status should be Released or higher (up to WorkDone). The user can also filter available work orders by giving a date range where material required date is defined. When the user is given the range, it will give a list of work orders in which material lines with the required date lie within the given range.

The data items in Manual Issue Work Order process will behave according to the following:

• The FROM_DATE and TO_DATE data items can be used as a filters, if placed before the WO_NO data item.
• When the Use Automatic Value field is set to Fixed on the FROM_DATE data item, it will be given the system date automatically, if placed before the WO_NO data item. 
• When the Use Automatic Value field is set to Fixed on the FROM_DATE and TO_DATE data items they will be given the values automatically, if they are placed after the MAINT_MATERIAL_ORDER_NO data item.
• When the Use Automatic Value field is set to Fixed on the SPARE_CONTRACT data item, it will be given the session site automatically, given that the ALLOW_MULTI_SITE process detail is disabled.
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision number.
• When the Use Automatic Value field is set to Fixed on the INT_DESTINATION_ID data item will be given the value Null automatically, if non is defined.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.

The Manual Issue Work Order process has specific details that can be enabled:

• If the ALLOW_MULTI_SITE process detail is enabled, the process will allow issue from all user-allowed sites.
• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Manual Issue Work Order process does not support the following:

• Pick lists

Modify Handling Unit in Shipment

MODIFY_HANDLING_UNIT_SHIPMENT process ID identifies the Modify Handling Unit in Shipment process in the Warehouse Data Collection window. The standard window for this is the Shipment/Handling Unit Structure/Handling Units tab. With the Warehouse Data Collection process it is possible to change width, height, depth, weight and volume. It is also possible to create SSCC, the alternate transport label ID and to print the handling unit label. Using this process it is possible to identify the handling unit via handling unit ID, SSCC or the alternate transport label ID. 

The data items in the Modify Handling Unit in Shipment process will behave according to the following:

• When setting up the configuration one decides if the HANDLING_UNIT_ID, SSCC or ALT_TRANSPORT_LABEL_ID should be used to identify the handling unit. Data items that are not used to identify the handling unit is placed after the identifying data item in the configuration using the Input Order field, the Use Automatic Value field is set to Fixed. If one also wants to hide data items that are not used for identifying the handling unit, Hide Line field is set to Always.
• When the Use Automatic Value field is set to Fixed on the CREATE_NEW_SSCC data item, the value will be set to No automatically if a NEW_SSCC has previously been entered. If the Handling Unit ID in the Shipment/Handling Unit Structure/Handling Units tab has Generate SSCC enabled, the value will be set to Yes automatically and if Generate SSCC is not enabled, the value will be set to No automatically.
• When the Use Automatic Value field is set to Fixed on the NEW_SSCC data item, the value will be set to Null automatically if Generate SSCC has previously been entered with the value Yes.
• When the Use Automatic Value field is set to Fixed on on the NO_OF_HANDLING_UNIT_LABELS data item, it will be given a automatic value according to the Handling Unit ID value in the Shipment/Handling Unit Structure/Handling Units tab. 
• The following data items are only used as filters: SHIPMENT_ID and PARENT_CONSOL_SHIPMENT_ID.

Note that:

• The ALT_TRANSPORT_LABEL_ID data item only can identify a handling unit if unique strings are used.

Move into Stock

The MOVE_INTO_STOCK process ID identifies the Move Into Stock and Move Into QA processes in the Warehouse Data Collection window. The standard windows are the Move Into Stock/Move Into QA windows. With the Warehouse Data Collection process, the Move Into Stock, Move Into QA and Perform Put-away activities can be performed. When the session is started, the selected site is used as a filter for the purchase order receipt lines.

The data items in the Move Into Stock process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch unit enabled.
• The VENDOR_NO data item could be used as a filter for the available receipts, if placed before the order reference. If the VENDOR_NO data item is placed after the order reference, it will be set automatically by the process.

The Move Into Stock process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.
• If the PERFORM_PUTAWAY process detail is enabled, the process will perform put-away on the identified receipt in the scanning process.

Move Into Stock process does not support the following:

• Pallets
• Identifying serial numbers of part numbers that are serial-traced at receipt (but not serial-traced in inventory).

Move Inventory Part

The MOVE_PART process ID identifies the Move Inventory Part process in the Warehouse Data Collection window. The standard window is the Move Inventory Part window. With the Warehouse Data Collection process, the Move to Another Site/Stock Location and Move to Transit activities can be performed. When the session is started, the selected site is considered as the from site.

The data items in the Move Inventory Part process will behave according to the following:

When the Use Automatic Value check box is selected on data items in the Move Inventory Part process, the data item will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit-enabled.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, no quantity is reserved and the user is moving all quantity then the CATCH_QUANTITY will be given automatically, if the PART_NO data item is placed before and the value entered for PART_NO is catch-unit-enabled.
• The DESTINATION data item is an enumeration with the values Move to Inventory and Move to Transit. If Move to Inventory is selected, the move will be performed when the process is executed. If Move to Transit is selected, the part will be in transit.
• The ACTIVITY_SEQ data item will be given automatically, if only one project exists.

The Move Inventory Part process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.
• If the USE_FROM_SITE_AS_DEFAULT_VALUE process detail is enabled, the from site is given as a default value to the TO_SITE data item. This setting can be used if most of the moves are done within the site but it should be possible to change the value before it is entered.
• If the USE_FROM_SITE_AS_FIXED_VALUE process detail is enabled, the from site is automatically committed to the TO_SITE data item. This setting can be used if all of the moves are done within sites. This setting reduces the number of data entry.

The Move Inventory Part process does not support the following:

• The process will not give all values automatically when the Use Automatic Value field is set to Fixed.
• Identifying serial numbers of part numbers that are serial-traced at receipt (but not serial-traced in inventory).
• It is not possible to set the Default Location check box in the Move Inventory Part  window.

Move Parts Between Ship Inventories

The MOVE_PART_BETWEEN_SHIP_INV process ID identifies the Move Parts Between Ship Inventories process in the Warehouse Data Collection window. The standard window is the Handle Orders in Shipment Inventory window. With the Warehouse Data Collection process, the Move Parts activity can be performed.

The data items in the Move Parts between Ship Inventories process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the PICK_LIST_NO data item, it will be given the value automatically, if the order key is placed before. 
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision number.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• The following data items are only used as filters: CUSTOMER_NO.

The Move Part Between Ship Inventories process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

Move Parts Between Ship Inventories process does not support the following:

• Pallets

Pack into Handling Unit on Shipment

PACK_INTO_HANDLING_UNIT_SHIP process ID identifies the Pack into Handling Unit on Shipment process in the Warehouse Data Collection window. The standard window for this is the Shipment/Handling Unit Structure/Unattached Shipment Reservations tab. With the Warehouse Data Collection process, the Attach Reservations activity can be performed. In Warehouse Data Collection it is only possible to attach, i.e., pack, the quantity of a shipment line that is picked. Using this process it is possible to identify the handling unit via the handling unit ID, SSCC or the alternate transport Label ID. 

The data items in the Pack into Handling Unit on Shipment process will behave according to the following:

• When setting up the configuration one decides if the HANDLING_UNIT_ID, SSCC or ALT_TRANSPORT_LABEL_ID should be used to identify the handling unit. Data items that are not used for identifying the handling unit is placed after the identifying data item in the configuration using the Input Order field, the Use Automatic Value field is set to Fixed. If one also wants to hide data items that are not used for identifying the handling unit, Hide Line field is set to Always.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• The following data items are only used as filters: SHIPMENT_ID and PARENT_CONSOL_SHIPMENT_ID.

Note that:

• The ALT_TRANSPORT_LABEL_ID data item can only identify a handling unit if unique strings are used.

The Pack into Handling Unit on Shipment process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Pack into Handling Unit on Shipment process does not support the following:

• Pallets
• Attach, i.e. pack, the quantity that is reserved but not picked.
• Non-inventory parts.

Park Warehouse Task

The PARK_WAREHOUSE_TASK process ID identifies the Park Warehouse Task process in the Warehouse Data Collection window. In IEE client Park is handled from My Warehouse Task window and the same validations apply for this process as when performing it there.

Only a warehouse task in status Started can be parked and each warehouse worker can only have one started task at a time so the input for this process is given.

The data items in the Park Warehouse Task process will behave according to the following:

• The TASK_ID data item is the Warehouse Task ID that is the unique identifier of the task.

• The
PARK_REASON is optional to register but if it is a value in Park Reason field will be set.

Process Transport Task

The PROCESS_TRANSPORT_TASK process ID identifies the Process Transport Task process in the Warehouse Data Collection window. The standard window is the Transport Task window. With this Warehouse Data Collection process it is possible to Pick, Unpick and Execute a transport task line. Using this process it is possible to change the value of the To Location No if required. 

The data items in Process Transport Task process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit-enabled.
• The DESTINATION data item is an enumeration with the values Move to Inventory and Move to Transit. If Move to Inventory is selected, the move will be performed when the process is executed. If Move to Transit is selected, the part will be in transit.

The Process Transport Task process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Process Transport Task process does not support the following:

• Pallets
• Move of parts that are serial-traced at receipt and issue between two sites.

Purchase Order Arrival

The PURCH_ARRIVAL process ID identifies the Purchase Order Arrival process in the Warehouse Data Collection window. The standard window is the Register Purchase Order Arrivals window. With the Warehouse Data Collection process, the Change Arrival Data, Report Arrival and Report Arrival with Serials activities can be performed. The available purchase order lines to be received are filtered on the selected site. In the Purchase Order Arrival configuration the camera can be enabled. When the camera is enabled the option to take a photo and save it to the media library of the purchase order receipt is available for the Windows Mobile and the Android client.

The data items in the Purchase Order Arrival process will behave according to the following:

• For RECEIPT_REFERENCE data item Null is allowed.
• For the QC_ANALYST data item Null is allowed.
• For the EXPIRATION_DATE data item Null is allowed.
• When the Use Automatic Value field is set to Fixed on the VENDOR_NO data item will be given the value automatically, if the ORDER_NO data item is placed before. 
• When the Use Automatic Value field is set to Fixed on the ARRIVAL_DATE data item, the system date and time will be set automatically.
• When the Use Automatic Value field is set to Fixed on the RECEIVER data item, the current user will be set automatically.
• When the Use Automatic Value field is set to Fixed on the PART_OWNERSHIP data item and the purchase order line is a rental line in an internal order flow within the same company, the ownership will be set automatically based on the rental parts in transit if a unique ownership can be found for the purchase order line. In all other cases the ownership will be fetched from the purchase order line.
• When the Use Automatic Value field is set to Fixed on the OWNER data item and the purchase order line is a rental line in an internal order flow within the same company, the owner will be set automatically based on the rental parts in transit if a unique owner can be found for the purchase order line. In all other cases the owner will be fetched from the purchase order line.
• When the Use Automatic Value field is set to Fixed on the SERIAL_NO_PREFIX, SERIAL_NO_SUFFIX, SERIAL_NO_SEQ_FROM, SERIAL_NO_SEQ_TO and SERIAL_NO_PADDING data items and the part is not serial-tracked they get the value Null automatically.
• When the Use Automatic Value field is set to Fixed on the SERIAL_NO_PREFIX, SERIAL_NO_SUFFIX, SERIAL_NO_SEQ_FROM, SERIAL_NO_SEQ_TO and SERIAL_NO_PADDING data items and the SERIAL_NO data item is placed before, they get the value Null automatically.
• When the Use Automatic Value field is set to Fixed on the SERIAL_NO data item and the SERIAL_NO_PREFIX, SERIAL_NO_SUFFIX, SERIAL_NO_SEQ_FROM, SERIAL_NO_SEQ_TO and SERIAL_NO_PADDING data items are placed before, then the SERIAL_NO data item get the value * automatically.
• For PURCH_QTY_ARRIVED and INV_QTY_ARRIVED, the data item with the lowest input order number has to be entered and the other will be calculated and set automatically.

The Purchase Order Arrival process has process specific details that can be enabled:

• If the RECEIVE_SERIALS_TO_ARRIVAL process detail is enabled, then the data items for serial will not be given automatically even though the Use Automatic Value field is set to Fixed and the receipt is done to an arrival location. This will result in the possibility to identify the serials.

The Purchase Order Arrival process does not support the following:

• Pallets

Reassign Handling Unit on Shipment

REASSIGN_HANDLING_UNIT_SHIP process ID identifies the Reassign Handling Unit on Shipment process in the Warehouse Data Collection window. The standard window for this is the Shipment/Handling Units tab. With the Warehouse Data Collection process, the Reassign Handling Unit activity can be performed. Using this process it is possible to identify the handling unit via the handling unit ID, SSCC or the alternate transport label ID. 

The data items in the Reassign Handling Unit on Shipment process will behave according to the following:

• When setting up the configuration one decides if the HANDLING_UNIT_ID, SSCC or ALT_TRANSPORT_LABEL_ID should be used for identifying the handling unit. Data items that are not used for identifying the handling unit is placed after the identifying data item in the configuration using the Input Order field, the Use Automatic Value field is set to Fixed. If one also wants to hide data items that are not used for identifying the handling unit, Hide Line field is set to Always.
• When the Use Automatic Value field is set to Fixed on the TO_NEW_SHIPMENT_ID data item, it will be set to No automatically if the TO_SHIPMENT_ID data item is placed before the TO_NEW_SHIPMENT_ID.
• When the Use Automatic Value field is set to Fixed on the TO_SHIPMENT_ID data item, it will be set to Null automatically if the TO_NEW_SHIPMENT_ID data item is placed before the TO_SHIPMENT_ID.
• When the Use Automatic Value field is set to Fixed on the RELEASE_RESERVATIONS data item, it will set to No automatically. 
• The PARENT_CONSOL_SHIPMENT_ID data item is used as a filter.

Note that:

• The ALT_TRANSPORT_LABEL_ID data item can only identify a handling unit if unique strings are used.

Receive Inventory Part from Transit

The RECEIVE_INV_PART_FROM_TRANSIT process ID identifies the Receive Inventory Part from Transit process in the Warehouse Data Collection window. The standard window is the Receive from Transit window. With the Warehouse Data Collection process, the Receive Inventory Part from Transit activity can be performed. When the session is started, the selected site is used as a filter for the part lines.

The data items in the Receive Inventory Part from Transit process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value "0" automatically, if no project exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value “1” automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one Rev No/EC.

The Receive Inventory Part from Transit process has process specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Receive Inventory Part from Transit process does not support the following:

• Pallets

Receive Order via Dispatch Advice

The RECEIVE_DISPATCH_ADVICE process ID identifies the Receive Order via Dispatch Advice process in the Warehouse Data Collection window. The standard window is the Incoming Dispatch Advice Lines window. With the Warehouse Data Collection process, the Report Arrival and Report Arrival with Serials activities can be performed. The available dispatch advice lines are filtered on the selected site.

The data items in the Receive Order via Dispatch Advice process will behave according to the following:

• The VENDOR_NO data item could be used as a filter for the available receipts, if placed before the order reference. If the VENDOR_NO data item is placed after the order reference, it will be set automatically by the process.
• The HANDLING_UNIT_ID data item could be used as a filter for the available receipts, if placed before the order reference. If the HANDLING_UNIT_ID data item is placed after the order reference, it will be set automatically by the process.
• The PACKGE_UNIT_ID data item could be used as a filter for the available receipts, if placed before the order reference. If the PACKGE_UNIT_ID data item is placed after the order reference, it will be set automatically by the process.
• The GTIN_NO data item could be used as a filter for the available receipts, if placed before the order reference. If the GTIN_NO data item is placed after the order reference, it will be set automatically by the process.
• Of the data items PURCH_QTY_ARRIVED and INV_QTY_ARRIVED, the data item with the lowest input order number has to be entered and the other will be calculated and set automatically.
• The SERIAL_NO_PREFIX, SERIAL_NO_SUFFIX, SERIAL_NO_SEQ_FROM, SERIAL_NO_SEQ_TO and SERIAL_NO_PADDING data items will automatically be blank if the part is not serial traced.

The Receive Order via Dispatch Advice process does not support the following:

• Pallets

Receive Shop Order

The RECEIVE_SHOP_ORDER process ID identifies the Receive Shop Order process in the Warehouse Data Collection window. The standard window is the Receive Shop Order window. With the Warehouse Data Collection process, the Receive, Close, Backflush, Simplified Material Check and Auto Report Operations activities can be performed. The available shop orders are filtered by the selected site and status on the shop order. The status should be Released, Reserved or Started.

The data items in the Receive Shop Order process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value from an existing stock record automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision number.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• When the Use Automatic Value field is set to Fixed on the ORIGIN_PACK_SIZE data item, it will be given the value Null automatically if PRINT_INVENTORY_PART_BARCODE is placed before and equal to No.
• The BARCODE_ID data item could be scanned or manually entered by the user.
• The PART_NO is unique for the identified barcode ID if the barcode ID is identified at the start of the process.
• When the Use Automatic Value field is set to Fixed on the CLOSE_SHOP_ORDER data item and total quantity received is equal to the lot size of the shop order, it will be given the value Yes automatically.

The Receive Shop Order process has process specific details that can be enabled:

• If the ALLOW_OVERREC_LINES process detail is enabled, the process will allow over receiving on the identified shop order.
• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Receive Shop Order process does not support the following:

• Pallets

Receive Shop Order By-Product

The RECEIVE_SHOP_ORDER_BY_PRODUCT process ID identifies the Receive Shop Order By-Product process in the Warehouse Data Collection window. The standard window is the Shop Order window. With the Warehouse Data Collection process, the Receive By-Product activity can be performed. 

The data items in the Receive Shop Order By-Product process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the EXPIRATION_DATE data item will be given the value Null automatically.
• When the Use Automatic Value field is set to Fixed on the OPERATION_NO data item will be given the value Null or the Operation No value automatically, if the data item BY_PRODUCT_PART_NO is placed before and the value entered for BY_PRODUCT_PART_NO has non or only one unique operation no connected to it.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value * automatically, if * is the only unique value.
• When the Use Automatic Value field is set to Fixed on the AVAILABLITY_CONTROL_ID data item will be given the value Null automatically.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item BY_PRODUCT_PART_NO is placed before and the value entered for BY_PRODUCT_PART_NO has only one revision no.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the BY_PRODUCT_PART_NO data item is placed before and the value entered for BY_PRODUCT_PART_NO is not catch-unit enabled.

Report Picking of Customer Order Lines

The PICK_CUSTOMER_ORDER process ID identifies the Report Picking of Customer Order Lines process in the Warehouse Data Collection window. The standard window is the Report Picking of Customer Order Lines window. With the Warehouse Data Collection process, the Report Picking and Report Picking, Quantity Deviation activities can be performed. The available pick list number is filtered on the selected site. With this process it is also possible to pack pick list lines into handling units if they are connected to a shipment and one or several handling units exists. It is possible to identify the handling unit via the handling unit ID, SSCC or the alternate transport label ID. 

The data items in the Report Picking of Customer Order Lines process will behave according to the following:

• The UNIQUE_LINE_ID data item uniquely identifies one pick list line. The UNIQUE_LINE_ID data item can preferably be used for guided picking. See the Warehouse Data Collection Configuration About description for more information.
• The ALT_TRANSPORT_LABEL_ID data item can only identify a handling unit if unique strings are used.
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• When the Use Automatic Value field is set to Fixed on the RELEASE_RESERVATION data item and no partial picking to shipment inventory is to be performed, it will be set to No automatically.

The Report Picking of Customer Order Lines process has specific details that can be enabled:

• If the ALLOW_OVERPICK_LINES process detail is enabled, the process will allow over picking on the identified pick list.
• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Report Picking of Customer Order Lines process does not support the following:    

• Pallets
• The activity Report Picking from Another Location

Return Parts from Shipment Inventory

The RETURN_PARTS_FROM_SHIP_INV process ID identifies the Return Parts from Shipment Inventory process in the Warehouse Data Collection window. The standard window is the Handle Orders in Shipment Inventory window. With the Warehouse Data Collection process, the Return Parts activity can be performed.

The data items in the Return Parts from Shipment Inventory process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the PICK_LIST_NO data item, it will be given the value automatically, if the order key is placed before. 
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision number.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• The following data item is only used as a filter: CUSTOMER_NO.

The Return Parts from Shipment Inventory process has specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

Return Parts from Shipment Inventory process does not support the following:

• Pallets

Scrap Inventory Part

The SCRAP_INVENTORY_PART process ID identifies the Scrap Inventory Part process in the Warehouse Data Collection window. The standard window is Scrap Inventory Part window.
With the Warehouse Data Collection process, the Scrap Inventory Part activity can be performed. The available part lines are filtered based on the selected site and location.

The data items in Scrap Inventory Part process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit-enabled.
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value "0" automatically, if no project exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value “1” automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one Rev No/EC.

The Scrap Inventory Part process has specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Scrap Inventory Part from Transit process does not support the following:

• Pallets

Shop Order Pick List

The SO_PICK_LIST process ID identifies the Issue Components using Pick List process in the Warehouse Data Collection window. The standard window is the Issue Material Using Pick List window. With the Warehouse Data Collection process, the Issue, Un-reserve and Create Count Report activities can be performed. The available pick list number is filtered on the selected site.

The data items will behave according to the following:

• The UNIQUE_LINE_ID data item uniquely identifies one pick list line. The UNIQUE_LINE_ID data item can preferably be used for guided picking. See the Warehouse Data Collection Configuration About description for more information.
• The QUANTITY data item is used to enter the quantity to pick and issue the shop order. If a partial issue is made and warehousing is not used, the remaining quantity will remain reserved on the pick list. If warehousing is used, a partial issue will leave nothing remaining reserved on the pick list line.
• When the Use Automatic Value is set to Fixed on the CATCH_QUANTITY data item, it will be given a null value automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit-enabled.
• If the COUNT_REPORT data item is set to Yes, a count report will be created for the selected part number and location.
• If the UNRESERVE data item is set to Yes, the quantity reserved for the pick list line will be unreserved. New reservations and pick lists will have to be made to complete the picking.

The Shop Order Pick List process has specific details that can be enabled:

• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The Issue Components using Pick List process does not support the following:

• Identifying serial numbers of part numbers that are serial-traced at receipt (but not serial-traced in inventory).

Start Warehouse Task

The START_WAREHOUSE_TASK process ID identifies the Start Warehouse Task process in the Warehouse Data Collection window. The standard window is the My Warehouse Task window. With the Warehouse Data Collection process, warehouse tasks can be started for the warehouse worker that corresponds to the logged on, or chosen, user. The same validations apply for the Start Warehouse Task function in WADACO as when starting tasks in the IEE client.

The data items in the Start Warehouse Task process will behave according to the following:

• The WORKER_ID corresponds to a record in the Person window. If the person is connected to a user ID that will be validated against the logged on user as long as no other action is registered in the Data Collection Configuration
window.
• ROWSTATE corresponds to the warehouse task status. Only statuses Released and Parked can be used. A separate configuration to restart parked warehouse tasks can be created by using this data item. Tasks in status Started can be picked up either through the Continue Session function or by the subsequent process where the task is handled, e.g., Report Picking of Customer Order.
• The TASK_ID data item is the Warehouse Task ID that is the unique identifier of the task.
• The LOCATION_GROUP identifies which location group the warehouse task belongs to.
• The TASK_TYPE identifies the task type. Possible values are Transport Task, Customer Order Pick List or Shop Order Pick List. It is the task type that should be used as the Subsequent Control Data Item ID that controls which subsequent process that should be started.
• If several different task types are handled with Warehouse Task it is possible to configure conditioned subsequent processes. It means that depending on a specific value, in this case Task Type, different subsequent processes can be opened. E.g., if a warehouse task of task type Customer Order Pick List is started a configuration of the PICK_CUST_ORDER is opened, and for a task type Transport Task process PROCESS_TRANSPORT_TASK is opened. This is set up in Data Collection Configuration/ Subsequent Process Detail. In Data Collection Configuration/ General the data item for the condition is registered in field Subsequent Control Data Item.

The Start Warehouse Task process has process specific details that can be enabled. It controls how the List of Values for data item TASK_ID is sorted. If the flag SORT_ON_OPERATIONAL_PRIORITY is not selected the priority order is:

• Assigned to worker
• Assigned to worker group
• Operational priority
• Default Priority
• Latest Start Date

If the flag SORT_ON_OPERATIONAL_PRIORITY is selected the priority order is:

• Default Priority or Operational Priority if entered for the warehouse task.
• Assigned to worker
• Assigned to worker group
• Latest Start Date

The Start Warehouse Task process does not support the following:

• Pallets

Unissue Work Order

The UNISSUE_WORK_ORDER process ID identifies the process Unissue Work Order in the Warehouse Data Collection  window. The standard window is Unissue Maintenance Material Requisition window. With the Warehouse Data Collection process the Unissue Material activity can be performed. The available Work Orders where materials are issued are filtered on the selected site and the status on the work order should be Released or higher (upto WorkDone). 

The data items in Unissue Work Order process will behave according to the below bullets:

• When the Use Automatic Value field is set to Fixed on the SPARE_CONTRACT data item, it will be given the current site automatically, given that the ALLOW_MULTI_SITE process detail is disabled.
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision number.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.
• When the Use Automatic Value field is set to Fixed on the TRANSACTION_ID data item, it will be given the value automatically, if the MAINT_MATERIAL_ORDER_NO and LINE_ITEM_NO is placed before and only one transaction exists.

The Unissue Work Order process has specific details that can be enabled:

• If the ALLOW_MULTI_SITE process detail is enabled, the process will allow un-issue from all user allowed sites.
• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.

The process Unissue Work Order does not support the following:

• Set default return location.

Unplanned Issue Work Order

The UNPLANNED_ISSUE_WORK_ORDER process ID identifies the process Unplanned Issue Work Order in the Warehouse Data Collection window. The available work orders where materials are issued are filtered on the selected site and the status on the work order should be Released or higher (up to WorkDone). System always creates a new material order for each occurrence of issuing with system date as the date required on requisition line and as the due date on the material requisition order.

The data items in Unplanned Issue Work Order process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the SPARE_CONTRACT data item, it will be given the current site automatically, given that the ALLOW_MULTI_SITE process detail is disabled.
• When the Use Automatic Value field is set to Fixed on the OPERATION_NO data item will be given the value Null automatically, if the work order is not connected to any operation. 
• When the Use Automatic Value field is set to Fixed on the ACTIVITY_SEQ data item, it will be given the value 0 (zero) automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the ENG_CHG_LEVEL data item will be given the value 1 automatically, if the data item PART_NO is placed before and the value entered for PART_NO has only one revision number.
• When the Use Automatic Value field is set to Fixed on the CATCH_QUANTITY data item, it will be given the value Null automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not catch-unit enabled.

The Unplanned Issue Work Order process has specific details that can be enabled:

• If the ALLOW_MULTI_SITE process detail is enabled, the process will allow issue from all user-allowed sites.
• If the BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.