Warehouse Data Collection Process

General Information

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

Handling Units:

• When setting up the configuration, you should decide if the HANDLING_UNIT_ID, SSCC or ALT_HANDLING_UNIT_LABEL_ID should be used to identify the handling unit. Data items that are not used for identifying the handling unit are placed after the identifying data item in the configuration using the Input Order field and the Use Automatic Value field is set to Fixed. If you want to hide data items that are not used for identifying the handling unit, set the Hide Line field to Always.
• Note that the ALT_HANDLING_UNIT_LABEL_ID and PARENT_ALT_HANDLING_UNIT_LABEL_ID data items can only identify a handling unit if unique strings are used.

GS1 barcodes:

• The GS1 barcode data items are disabled by default. To enable the GS1 functionality the GS1_BARCODE data item must be put before the data item(s) it should identify and Use Fixed Value should be set to Never. In order to display the scanned GS1 value in the information table of the scanning client, Hide Line must be set to Never. The GS1 Application Identifier is used to decide what data is used from the GS1 barcode. For further information, refer the About Warehouse Data Collection Configuration and the Configure Data Collection document.
• If the Barcode Validation is enabled, GS1 Application Identifiers of connected data items will be validated in all configurations, both when a barcode is entered and when the value is empty.

GTIN:

• The GTIN data item is disabled by default. To enable the GTIN functionality, Use Fixed Value should be set to Never. In order to display the scanned GTIN value in the information table of the scanning client, Hide Line must be set to Never.
• If a GTIN14 barcode is entered, it can automatically identify the Input UoM.
• When you use a GTIN value to automatically identify a part number, the PART_NO data item should have Use Automatic Value set to Fixed.

INPUT UOM and INPUT QTY:

• The INPUT UOM and INPUT QTY data items are disabled by default. If a GTIN14 barcode is entered it can be used to automatically identify the Input UoM.

Camera Support can be enabled in the following processes:

• Count Handling Unit per Count Report
• Count Part per Count Report
• Deliver Customer Order
• Process Shipment
• Receive Dispatch Advice
• Receive Handling Unit on Dispatch Advice
• Receive Part on Dispatch Advice
• Register Arrivals

Attach Part to Handling Unit

The ATTACH_PART_TO_HANDLING_UNIT process ID identifies the Attach Part to Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Handling Unit/Structure/Unattached Inventory Parts In Stock tab. With the Warehouse Data Collection process, the Attach Part to Handling Unit activity can be performed.

The data items in the Attach Part to Handling Unit process will behave according to the following:

• When the Use Automatic Value field is set to Fixed SERIAL_NO, LOT_BATCH_NO or CONFIGURATION_ID data item, it will be given the value * automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not serial, lot batch or configuration enabled.
• 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, it 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, it 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 Attach Part to Handling Unit process has process specific details that can be enabled:

• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.

The Attach Part to Handling Unit 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Attach Receipt to Handling Unit

The ATTACH_RECEIPT_TO_HANDL_UNIT process ID identifies the Attach Receipt to Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Receipt/Details page. With the Warehouse Data Collection process, the Attach Receipt to Handling Unit activity can be performed.

• When the Use Automatic Value field is set to Fixed on the SOURCE_REF_TYPE data item will be given the value automatically, if the SOURCE_REF1 data item is placed before.
• When the Use Automatic Value field is set to Fixed on the SENDER data item will be given the value automatically, if the SOURCE_REF1 data item is placed before.
• When the Use Automatic Value field is set to Fixed SERIAL_NO, LOT_BATCH_NO or CONFIGURATION_ID data item, it will be given the value * automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not serial, lot batch or configuration enabled.
• 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, it 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, it 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 Attach Receipt to Handling Unit process has process specific details that can be enabled:

• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Change Parent Handling Unit

The CHG_PARENT_HANDLING_UNIT process ID identifies the Change Parent Handling Unit process in the Warehouse Data Collection page. The standard pages for this are the Handling Unit/General, Handling Unit/Structure, Handling Units In Stock, and Shipment/Handling Unit Structure/Handling Units tab. With the Warehouse Data Collection process, the Change Parent Handling Unit ID activity can be performed.

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

• The SHIPMENT_ID can be set to null. If Null is entered the change parent activity can be performed on a empty handling unit or a handling unit in inventory. If a shipment ID is entered the change parent activity can be performed on a handling unit from that shipment.
• When setting up the configuration you decide if the PARENT_HANDLING_UNIT_ID, PARENT_SSCC or PARENT_ALT_HANDLING_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 are placed after the identifying data item in the configuration using the Input Order field. The Use Automatic Value field is set to Fixed for those data items. If you also want 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 used as filters: SHIPMENT_ID and PARENT_CONSOL_SHIPMENT_ID.

The Change Parent Handling Unit process has process specific details that can be enabled:

• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• If the IFS/Shipment component is not installed the following data items will not be available:
  SHIPMENT_ID, PARENT_CONSOL_SHIPMENT_ID

Count Handling Unit

The COUNT_HANDLING_UNIT process ID identifies the Count Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Count Handling Units page. With the Warehouse Data Collection process, the Count without Differences, and Count as Does Not Exist activities can be performed.

In addition there is a third option that will allow you to jump to the COUNT_PART process if counting on part level needs to be performed, for example when a Handling Unit is found to be broken. The COUNT_PART process needs to be configured as a subsequent process in order for this feature to work.

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

• When the HANDLING_UNIT_EXISTS data item is set to No the content of the handling unit is counted with quantity 0 (zero). If you want to count the parts attached to the Handling Unit, you need to start the Count Inventory Part process instead.
• The ACTION data item indicates which action will be taken. The options are:
  • Exists, the handling unit is counted.
  • Does Not Exist, the content of the handling unit is counted with quantity 0 (zero).
• Count Part. Upon execution, the COUNT_PART process will automatically start and part level counting can be performed.

The Count Handling Unit process has process specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Count Handling Unit per Count Report

The COUNT_HANDL_UNIT_COUNT_REPORT process ID identifies the Count Handling Unit per Count Report process in the Warehouse Data Collection page. The standard page for this is the Count per Count Report page. With the Warehouse Data Collection process, the Count without Differences and Count as Does Not Exist activities can be performed. In addition to this you can also chose on which level to perform the counting.

In the Count Handling Unit per Count Report configuration the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Handling Unit page.

Prerequisite: Add MediaLibrary^ to the Service List for LU HandlingUnit in the Object Connections page.

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

• When the Use Automatic Value field is set to Fixed on the LOCATION_NO and HANDLING_UNIT_ID data items, they will be given values automatically if the AGGREGATED_LINE_ID is placed before and a value is entered.
• The ACTION data item indicates which action will be taken. The options are:
  • Exist, the handling unit is counted.
  • Does Not Exist, the content of the handling unit is counted with quantity 0 (zero).
  • Count Sub Level, the current handling unit will be ignored and counting will continue with the next handling unit in this structure.
  • Count Parts, the current handling unit and its underlying structure will be ignored and the counting will continue with the content of this structure.

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

• If the DISPLAY_ALT_HANDLING_UNIT_ID, DISPLAY_HANDLING_UNIT_ID, and/or DISPLAY_SSCC process detail are enabled the values will be displayed in the description field in the List of Values for Aggregated Line ID
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The default configuration is set up to use the Start Count Report process to start the Count Handling Unit per Count Report process.

Count Inventory Part

The COUNT_PART process ID identifies the Count Inventory Part process in the Warehouse Data Collection page. The standard page for this is the Count per Inventory Part page. 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 (zero) 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Count Inventory Part process does not support the following:

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

Count Part per Count Report

The COUNT_PART_COUNT_REPORT process ID identifies the Count Part per Count Report process in the Warehouse Data Collection page. The standard page for this is the Count per Count Report page. 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.

In the Count Part per Count Report configuration the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Count Results page.

Prerequisite: Add MediaLibrary^ to the Service List for LU CountingResult in the Object Connections page.

The data items in the Count Part 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 CONFIRM data item is an enumeration with the values Yes and No. If Yes is entered, the Confirmed field in the Count per Count Report page is set to Yes. If No is entered, the field is set to No.
• 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 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 (zero) as the barcode ID to be able to continue the counting, if for instance the Barcode ID is missing.

The Count Part 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Count Part per Count Report process does not support the following:

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

Note that:

• The default configuration is set up to use the Start Count Report process to start the Count Part per Count Report process.

Create Handling Unit

The CREATE_HANDLING_UNIT process ID identifies the Create Handling Unit process in the Warehouse Data Collection page. The standard pages for this are the Handling Unit, Handling Unit/Structure and Shipment/Handling Unit Structure tabs. With the Warehouse Data Collection process, the Create Handling Unit and Add Handling Units activities can be performed. Using this process it is also possible to create SSCC, Alt Handling Unit Label ID, and to print the Handling Unit Label and the Shipment Handling Unit Label.

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

• The SHIPMENT_ID data item can be set to null. If Null is entered, an empty handling unit is created, otherwise it is added to the entered shipment.
• 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. Otherwise 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, PARENT_SSCC and PARENT_ALT_HANDLING_UNIT_LABEL_ID data items, the value will be set to Null automatically if a SHIPMENT_ID without any existing handling units connected to it has been entered before or if SHIPMENT_ID is Null.
• When the Use Automatic Value field is set to Fixed on the PRINT_HANDLING_UNIT_LABEL and/or PRINT_SHIPMENT_LABEL data item and the handling unit basic data for a handling unit type ID has Print Handling Unit Label and/or Print Shipment Handling Unit Label enabled, the value will be set to Yes automatically. If Print Handling Unit Label and Print Shipment Handling Unit Label is not enabled, the value will be set to No automatically.
• When the Use Automatic Value field is set to Fixed on the NO_OF_HANDLING_UNIT_LABELS and/or NO_SHIPMENT_LABELS data item, it will be given an automatic value according to the handling unit basic data in the Handling Unit Type page.
• The following data items are only used to filter out a SHIPMENT_ID: RECEIVER_ID, SHIPMENT_TYPE, SHIP_VIA_CODE, FORWARD_AGENT_ID, PARENT_CONSOL_SHIPMENT_ID and SHIP_ADDR_NO.

The Create Handling Unit process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Create Handling Unit process does not support the following:

• Creating more than one level at a 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.

Note that:

• The values for PRINT_HANDLING_UNIT_LABEL, PRINT_SHIPMENT_LABEL, NO_OF_HANDLING_UNIT_LABELS and NO_SHIPMENT_LABELS are not saved on the handling unit. The values are only used when executing the process.
• If the IFS/Shipment component is not installed the following data items will not be available:
  FORWARD_AGENT_ID, PARENT_CONSOL_SHIPMENT_ID, SHIPMENT_ID, SHIPMENT_TYPE, SHIP_VIA_CODE, PRINT_SHIPMENT_LABEL, NO_OF_SHIPMENT_LABELS, RECEIVER_ID, RECEIVER_ADDR_ID

Delete Handling Unit

The DELETE_HANDLING_UNIT process ID identifies the Delete Handling Unit process in the Warehouse Data Collection page. The standard pages for this are the Handling Unit/Structure and Shipment/Handling Unit Structure tabs. With the Warehouse Data Collection process, the Delete Handling Unit activity can be performed.

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

• The SHIPMENT_ID can be set to null. If Null is entered an empty handling unit can be deleted, otherwise a handling unit from the entered shipment can be deleted.
• When the Use Automatic Value field is set to Fixed on the DELETE_CONNECTED_HANDLING_UNITS data item, the value will be set to No automatically if the actual handling unit does not have any connected handling units.
• If Yes is entered for the DELETE_CONNECTED_HANDLING_UNITS data item all connected handling units will be deleted and if any shipment lines are attached those will be unattached.
• The following data items are only used as filters: SHIPMENT_ID and PARENT_CONSOL_SHIPMENT_ID.

The Delete Handling Unit process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• If the IFS/Shipment component is not installed the following data items will not be available:
  SHIPMENT_ID, PARENT_CONSOL_SHIPMENT_ID

Deliver Customer Order

The DELIVER_CUSTOMER_ORDER process ID identifies the Deliver Customer Order process in the Warehouse Data Collection page. The standard page for this is the Deliver Customer Orders and Quick Order Flow Handling pages. With the Warehouse Data Collection process, the Deliver Order activity can be performed. The available customer order lines to be delivered are filtered on the selected site.

In the Deliver Customer Order configuration, the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Customer Order page.

Prerequisite: Add MediaLibrary^ to the Service List for LU CustomerOrder in the Object Connections page.

The data items in the Deliver Customer Order process will behave according to the following:

• If ORDER_NO is the first data item then the other items can have the Use Automatic Value field set to Fixed and will then be fetched automatically.
• All data items other than ORDER_NO are used for filtering.

The Deliver Customer Order process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• You are recommended to use an order type with online processing.
• It is possible to deliver a partially picked Customer Order using this process.

Delivery Confirmation of Customer Order

The DELIVERY_CONFIRMATION process ID identifies the Delivery Confirmation of Customer Order process in the Warehouse Data Collection page. The standard page for this is the Delivery Confirmation of Customer Orders page. 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.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Find Inventory

The FIND_INVENTORY process ID identifies the Find Inventory process in the Warehouse Data Collection page. This process does not correspond to a specific activity, it can be compared to doing a search by selecting the Search command, in the Inventory Part in Stock page. Note: This process have a limited search possibility and it is only possible to get information about a few attributes.

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

• All data items in this process can be set to Null, i.e. it is possible to complete this process without entering any data. If a value is entered it will be used to filter the search result in this process.

The Find Inventory process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• Which search information that should be displayed is decided by connecting feedback items to a data item. What the given feedback item will display, depends on which data is entered in the process, entering only a part number might result in several records and entering both part number and location number will result in maximum one record.
• All quantities will be summarized per part and location, i.e. if a serial tracked part with 100 serials is stored on a location, only one record will be displayed with an on-hand quantity of 100 pcs.

Issue Inventory Part

The ISSUE_INVENTORY_PART process ID identifies the Issue Inventory Part process in the Warehouse Data Collection page. The standard page for this is the Issue Inventory Part page. With the Warehouse Data Collection process, the Register Issue of Single Parts activity can be performed.

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

• When the Use Automatic Value is set to Default on the LOCATION_NO data item and the PART_NO is before, the default location for the PART_NO will be fetched.
• When the Use Fixed Value is set to When Applicable for the code part data items the user will only be prompted for an entry when that code part is set up for pre-posting with issue from inventory (M110).
• When the Use Fixed Value is set to When Applicable and the Fixed Value is set to 1, the QTY_TO_ISSUE data item will be set to 1 if the PART_NO is before and the part is serial tracked.
• When the Use Fixed Value is set to When Applicable and the Fixed Value is set to *, the SERIAL_NO, LOT_BATCH_NO and CONFIGURATION_ID data items will be set to * if the PART_NO data item is placed before and the part is not a serial, lot batch, or configuration enabled part.

The Issue 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• For the code part data items the descriptions displayed in the client will be the Internal Name defined in the Define Code String page. If you change the description of the data item from the default descriptions in the process, e.g. CODE_A_ default description is Code A, this will only apply in the Data Collection Configuration page. It is possible to configure feedback items for the code part values and they will behave in the same way, these descriptions will be fetched from the Code Part Values page.

Issue of Material Requisition Line

The ISSUE_MATERIAL_REQUIS_LINE process ID identifies the Issue Material Requisition Line process in the Warehouse Data Collection page. The standard page for this is the Material Requisition page. 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN 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.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Kanban Replenishment Request

The KANBAN_REPLENISHMENT_REQUEST process ID identifies the Kanban Replenishment Request process in the Warehouse Data Collection page. 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 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.

The Kanban Replenishment Request process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Manual Issue Shop Order Handling Unit

The MANUAL_ISSUE_SHOP_ORDER_HU process ID identifies the Manual Issue Shop Order Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Manual Issue Shop Order page Handling Units tab. With the Warehouse Data Collection process, the Issue Components Manually activity can be performed to issue components which are in handling units. 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.

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

• When the Use Automatic Value field is set to Fixed on the RELEASE_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 SEQUENCE_NO data item will be given the value automatically, if only one unique value exists
• The PART_NO data item will not be asked if the ORDER_NO, RELEASE_NO and SEQUENCE_NO data items are placed before PART_NO data item.
• When the Use Automatic Value field is set to Fixed on the LINE_ITEM_NO and/or COMPONENT_PART_NO data items, they will be given the value automatically, if only one unique value exists.
• When the Use Automatic Value field is set to Fixed on the COMPONENT_PART_NO data item it will be given the value automatically, if it is placed after the LINE_ITEM_NO data item.

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

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The handling units that are allowed to issue must be reserved handling units and/or having less than the remaining quantity to issue.

Manual Issue Shop Order Part

The MANUAL_ISSUE_SHOP_ORDER_PART process ID identifies the Manual Issue Shop Order Part process in the Warehouse Data Collection page. The standard page for this is the Manual Issue Shop Order page. 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 the shop order key. If the PART_NO data item is placed after the shop order key, it will be set automatically by the process.
• 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).
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Manual Issue Work Order

The MANUAL_ISSUE_WORK_ORDER process ID identifies the Manual Issue Work Order process in the Warehouse Data Collection page. The standard page for this is Manual Issue Work Order page. 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 Work Done). 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 none 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

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

• Pick lists

Modify Handling Unit

MODIFY_HANDLING_UNIT process ID identifies the Modify Handling Unit process in the Warehouse Data Collection page. The standard pages for this are the Handling Unit/General, Handling Unit/Structure/Handling Units, and Shipment/Handling Unit Structure/Handling Units tabs. 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 alternative handling unit label ID and to print the handling unit label, handling unit content label and the shipment handling unit label.

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

• The SHIPMENT_ID data item can be set to null. If Null is entered a handling unit in inventory or a empty handling unit can be modified. Otherwise a handling unit from the entered shipment can be modified.
• 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 the NO_OF_HANDLING_UNIT_LABELS data item, it will be given a automatic value according to the Handling Unit ID value in the Handling Unit/Structure/Handling Units or the Shipment/Handling Unit Structure/Handling Units tab.
• When the Use Automatic Value field is set to Fixed on the NO_OF_CONTENT_LABELS data item, it will be given a automatic value according to the Handling Unit ID value in the Handling Unit/Structure tab.
• When the Use Automatic Value field is set to Fixed on the NO_OF_SHIPMENT_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: PARENT_CONSOL_SHIPMENT_ID.

The Modify Handling Unit process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The values for PRINT_HANDLING_UNIT_LABEL, PRINT_CONTENT_LABEL, PRINT_SHIPMENT_LABEL, NO_OF_HANDLING_UNIT_LABELS, NO_OF_CONTENT_LABELS and NO_SHIPMENT_LABELS are saved on the handling unit.
• If the IFS/Shipment component is not installed the following data items will not be available:
  SHIPMENT_ID, PRINT_SHIPMENT_LABEL, NO_OF_SHIPMENT_LABELS, PARENT_CONSOL_SHIPMENT_ID

Move Handling Unit

MOVE_HANDLING_UNIT process ID identifies the Move Handling Unit process in the Warehouse Data Collection page. The standard pages for this are the Handling Units In Stock, Handling Unit/Structure, and Handling Unit/Structure/Handling Units tabs. With the Warehouse Data Collection process the Move Handling Unit activity can be performed, this includes moving to and between quality assurance, arrival, and picking locations as well as moving into Stock. To use the move reserved stock functionality it must be enabled via the Move Reserved Stock setting on the Site/Warehouse Management/General tab.

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

• The LOCATION_NO can be set to Fixed if the handling unit is identified by HANDLING_UNIT_ID or SSCC because then you can receive the information about where the handling unit is located.
• 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 Move Handling Unit process has process specific details that can be enabled:

• 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 entries.
• If the PERFORM_PUTAWAY process detail is enabled, the process will perform put-away on the handling unit identified in the scanning process. Note that put-away can only be performed on handling units in receipt.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• If ALT_HANDLING_UNIT_LABEL_ID data item is not unique and HANDLING_UNIT_ID/SSCC is set to Fixed or default user will not get the data and have to choose from list of values or scan the data.

Move Handling Units Between Shipment Inventories

MOVE_HU_BETWEEN_SHIP_INV process ID identifies the Move Handling Units Between Shipment Inventories process in the Warehouse Data Collection page. The standard page for this is Handling Units In Shipment Inventory page, Move command. With the Warehouse Data Collection process the Move Handling Unit in Shipment inventory activity can be performed.

The data items in the Move Handling Units Between Shipment Inventories process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the FROM_LOCATION_NO data item, the value will be given automatically if the handling unit has already been identified.

The Move Handling Units Between Shipment Inventories process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• If the ALT_HANDLING_UNIT_LABEL_ID data item is not unique and HANDLING_UNIT_ID/SSCC is set to Fixed or Default, no default value can be given automatically for these data items.
  

Move Inventory Part

The MOVE_PART process ID identifies the Move Inventory Part process in the Warehouse Data Collection page. The standard page for this is the Move Inventory Part page. With the Warehouse Data Collection process, the Move to Another Site/Stock Location and Move to Transit activities can be performed. To use the move reserved stock functionality it must be enabled via the Move Reserved Stock setting on the Site/Warehouse Management/General tab. 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 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN 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 entries.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Move Inventory Part process does not support the following:

• 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 field in the Move Inventory Part page.

Move Part in Receipt

The MOVE_PART_IN_RECEIPT process ID identifies the Move Part in Receipt process in the Warehouse Data Collection page. The standard pages for this are the Move Into Stock and Move Into QA pages. 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 available receipt lines.

The data items in the Move Part in Receipt 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 SENDER data item could be used as a filter for the available receipts, if placed before the order reference. If the SENDER data item is placed after the order reference, it will be set automatically by the process.

The Move Part in Receipt 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN 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.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Move Part in Receipt process does not support the following:

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

Move Parts Between Shipment Inventories

The MOVE_PART_BETWEEN_SHIP_INV process ID identifies the Move Parts Between Shipment Inventories process in the Warehouse Data Collection page. The standard page for this is the Inventory Parts in Shipment Inventory page. With the Warehouse Data Collection process, the Move Parts activity can be performed.

The data items in the Move Parts Between Shipment 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 source 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 automatically, if no project connection exists.
• When the Use Automatic Value field is set to Fixed on the WAIV_DEV_REJ_NO data item, it 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, it 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: RECEIVER_ID.

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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

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 page. The standard page for this is the Shipment/Shipment Handling Unit Structure/Unattached Shipment Lines tab. With the Warehouse Data Collection process the Attach Parts to handling Unit 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.

The data items in the Pack into Handling Unit on Shipment 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 following data items are only used as filters: SHIPMENT_ID and PARENT_CONSOL_SHIPMENT_ID.

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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

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

• 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 page. The standard page for this is the My Warehouse Task page.

Only a warehouse task in status Started can be parked and each warehouse worker can only have one started task at a time.

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.

Pick Handling Units Shipment Order and Project Deliverables

The PICK_HU process ID identifies the Pick Handling Units Shipment Order and Project Deliverables process in Warehouse Data Collection page. The standard page for this is Report Picking of Pick List Lines page. With the Warehouse Data Collection process, the Pick and Unreserve Pick List Lines activities can be performed. In addition to this you can also chose on which level to perform the picking. With this process it is also possible to pick and pack a handling unit into other handling unit connected to the shipment.

The data items in the Pick Handling Units Shipment Order and Project Deliverables process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the RES_HANDLING_UNIT_ID and LOCATION_NO data items, they will be given values automatically if the AGGREGATED_LINE_ID is placed before and a value is entered.
• The ACTION data item indicates which actions will be taken. The options are:
  • Pick, the handling unit is picked.
  • Unreserve Pick List Lines, the content of the handling unit is unreserved.
  • Pick Sub Level, the current handling unit will be ignored and Report Picking of Handling Units will continue with the next handling unit in the structure.
  • Pick Parts, the current handling unit and its underlying structure will be ignored and Report Picking of Parts will be performed for the content of the structure instead.

The Pick Handling Units Shipment Order and Project Deliverables process has specific details that can be enabled:

• If DISPLAY_ALT_HANDLING_UNIT ID, DISPLAY_HANDLING_UNIT_ID and/or DISPLAY_SSCC process details are enabled the values will be displayed in the description field in the List of Values for Aggregated Line ID together with LOCATION_NO.
• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Pick Handling Units Shipment Order and Project Deliverables process does not support following:

• The pick by choice functionality.
• Packing into handling unit connected to the shipment when a planned packing already exists in the shipment.

Note that:

• If a consolidated pick list is created and one reserved handling unit consist of reservations from different shipments the user is not allowed to add the reserved handling unit to a shipment handling unit, because a shipment handling unit can only be connected to one shipment.
• The default configuration is set up to use the Start Pick process to start the Pick Handling Units Shipment Order and Project Deliverables process.

Pick Parts Shipment Order and Project Deliverables

The PICK_PART process ID identifies the Pick Parts Shipment Order and Project Deliverables process in the Warehouse Data Collection page. The standard page for this is the Report Picking of Pick List Lines page. With the Warehouse Data Collection process, the Report Picking and Quantity Deviation activities can be performed. The process also handles partial picking if that is enabled. The available pick lists are filtered on the selected site. With this process it is also possible to pack pick list lines into handling units connected to the shipment.

The data items in the Pick Parts Shipment Order and Project Deliverables 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.
• 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, it 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, it 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 Pick Parts Shipment Order and Project Deliverables 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Pick Parts Shipment Order and Project Deliverables process does not support the following:

• The activity Report Picking from Another Location.
• The pick by choice functionality.
• Packing into handling unit connected to the shipment when a planned packing already existst in the shipment.

Note that:

• The default configuration is set up to use the Start Pick process to start the Pick Parts Shipment Order and Project Deliverables process.

Process Handling Unit on Transport Task

The PROCESS_TRANSPORT_TASK_HU process ID identifies the Process Handling Unit on Transport Task process in Warehouse Data Collection page. The standard page for this is the Transport Task page. With this Warehouse Data Collection process it is possible to perform Pick, Unpick, and Execute. In addition to this you can also choose on which level to perform the action. Using this process, it is possible to change the value of the To Location No if required.

The data items in Process Handling Unit on Transport Task will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the FROM_CONTRACT, FROM_LOCATION_NO, and HANDLING_UNIT_ID data items, they will be given automatically if the AGGREGATED_LINE_ID is placed before and a value is entered.
• The ACTION data item indicates which actions will be taken. The options are:
  • Pick, the handling unit is picked and the status is changed to Picked.
  • Unpick, the handling unit is unpicked and the status is changed to Created.
  • Execute, the movement of the handling unit is executed and the status is changed to Executed.
  • Process Sub Level, the current handling unit will be ignored and Process Handling Unit on Transport Task will continue with the next handling unit in the structure.
  • Process Parts, the current handling unit and its underlying structure will be ignored and Process Part on Transport Task will be performed for the content of the structure instead.
• 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 handling unit will be in transit.

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

• If DISPLAY_ALT_HANDLING_UNIT ID, DISPLAY_HANDLING_UNIT_ID and/or DISPLAY_SSCC process details are enabled the values will be displayed in the description field in the List of Values for Aggregated Line ID together with LOCATION_NO.
•  If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The default configuration is set up to use the Start Transport Task process to start the Process Handling Unit on Transport Task process.

Process Part on Transport Task

The PROCESS_TRANSPORT_TASK_PART process ID identifies the Process Part on Transport Task process in the Warehouse Data Collection page. The standard page for this is the Transport Task page. 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 Part on 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 ACTION data item indicates which actions will be taken. The options are:
  • Pick, the part is picked and the status is changed to Picked.
  • Unpick, the part is unpicked and the status is changed to Created.
  • Execute, the movement of the part is executed and the status is changed to Executed.
• 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 Part on 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Process Part on Transport Task process does not support the following:

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

Note that:

• The default configuration is set up to use the Start Transport Task process to start the Process Part on Transport Task process.

Process Shipment

The PROCESS_SHIPMENT process ID identifies the Process Shipment process in the Warehouse Data Collection page. The standard pages for this are the Shipment and Shipments pages. With the Warehouse Data Collection process, the Reserve Shipment Lines, Create Pick List, Print Pick List, Report Picking, Complete Shipment, Deliver Shipment, and Close Shipment activities can be performed. It is also possible to back-up to the Preliminary status from Completed status in order to enable making changes to the shipment and handling unit structure. The available shipments are filtered on the selected site, and only shipments in status Preliminary and Completed are available for processing.

In the Process Shipment process, the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Shipment page.

Prerequisite: Add MediaLibrary^ to the Service List for LU Shipment in the Object Connections page.

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

• SHIPMENT_ID is the identification of the shipment regardless of the shipment category, Consolidated or Normal.
• All data items other than SHIPMENT_ID and ACTION are used for filtering. Any filter item that is after SHIPMENT_ID can have the Use Automatic Value field set to Fixed and will then be fetched automatically.
• If FROM_DATE is before SHIPMENT_ID and no unique value is found the default value will be today's date.
• If the DELNOTE_NO data item is before SHIPMENT_ID the list of values will have limited filtering. For instance ACTION cannot be user to filter out delivery notes available to process. This is due to performance considerations.

The Process Shipment process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• You are recommended to use an order type with online processing.
• If the shipments included in a consolidated shipment have different values for the same data item, that data item will get value NULL for the consolidated shipment.
• If approval is required before delivery you will receive an error message if you try to deliver before approval. Approval is performed in the regular client.

Reassign Handling Unit on Shipment

REASSIGN_HANDLING_UNIT_SHIP process ID identifies the Reassign Handling Unit on Shipment process in the Warehouse Data Collection page. The standard page for this is the Shipment/Shipment Handling Unit Structure/Handling Units tab. With the Warehouse Data Collection process, the Reassign Handling Unit activity can be performed.

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

• 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.

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

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Receive Dispatch Advice

The RECEIVE_DISPATCH_ADVICE process ID identifies the Receive Dispatch Advice process in the Warehouse Data Collection page. The standard page for this is the Incoming Dispatch Advice page header. With the Warehouse Data Collection process the Receive activity on header can be performed. The available dispatch advices are filtered on the selected site.

In the Receive Dispatch Advice configuration, the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Incoming Dispatch Advice page.

Prerequisite: Add MediaLibrary^ to the Service List for LU ExtDispatchAdvice in the Object Connections page.

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

• The SENDER data item could be used as a filter for the available dispatch advices, if placed before the DELNOTE_NO data item. If the SENDER data item is placed after the DELNOTE_NO data item, it will be set automatically by the process.
• The RECEIVE_TO_DEFAULT_LOCATION data item will automatically be set to No if the LOCATION_NO data item is placed before.
• The USE_SOURCE_LINE_REVISION data item values represent the default Part Revision to be used for Incoming Dispatch lines if the received revision is different from the one expected from the demand source line.

The Receive Dispatch Advice process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Receive Handling Unit on Dispatch Advice

The RECEIVE_HU_DISPATCH_ADVICE process ID identifies the Receive Handling Unit on Dispatch Advice process in the Warehouse Data Collection page. The standard pages for this is the Incoming Dispatch Advice/Handling Unit structure navigator or Handling Units in Incoming Dispatch Advice page. With the Warehouse Data Collection process the Receive Handling unit from Incoming Dispatch Advice page can be performed.

In the Receive Handling Unit on Dispatch Advice configuration, the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Handling Units in Incoming Dispatch Advice page.

Prerequisite: Add MediaLibrary^ to the Service List for LU ExtDispatchAdviceHu in the Object Connections page.

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

• The SENDER data item could be used as a filter for the connected delivery notes per sender, if placed before the DELNOTE_NO.
• The SENDER_HANDLING_UNIT_ID data item values will represent the Top parent handling units connected to a Incoming Dispatch Advice.

The Receive Handling Unit on Dispatch Advice process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Receive Part on Dispatch Advice

The RECEIVE_PART_DISPATCH_ADVICE process ID identifies the Receive Part on Dispatch Advice process in the Warehouse Data Collection page. The standard page for this is the Incoming Dispatch Advice/Part Lines tab. With the Warehouse Data Collection process the Receive and Receive with Serials/Lots activities can be performed. The available dispatch advice lines are filtered on the selected site.

In the Receive Part on Dispatch Advice configuration, the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Receipts page.

Prerequisite: Add MediaLibrary^ to the Service List for LU ReceiptInfo in the Object Connections page.

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

• The SENDER data item could be used as a filter for the available receipts, if placed before the source reference. If the SENDER data item is placed after the source reference, it will be set automatically by the process.
• The SENDER_HANDLING_UNIT_ID data item could be used as a filter for the available receipts, if placed before the source reference. If the SENDER_HANDLING_UNIT_ID data item is placed after the source 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 source reference. If the GTIN_NO data item is placed after the source reference, it will be set automatically by the process.
• Of the data items SOURCE_QTY_ARRIVED and INV_QTY_ARRIVED, the data item with the lowest Input Order has to be entered and the other will be calculated and set automatically.
• The SERIAL_NO_PREFIX, SERIAL_NO_SUFFIX, and SERIAL_NO_PADDING data items will automatically be blank if the part is not serial traced.

The Receive Part on Dispatch Advice 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Receive Handling Unit from Transit

The RECEIVE_HU_FROM_TRANSIT process ID identifies the Receive Handling Unit from Transit process in the Warehouse Data Collection page. The standard pages for this are the Handling Unit/Structure and Handling Unit In Stock tabs. With the Warehouse Data Collection process, the Receive Handling Unit from Transit activity can be performed.

The data items in the Receive Handling Unit from Transit process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the LOCATION_NO data item, it will be given a value automatically if the data items identifying the handling unit is placed before LOCATION_NO.

The Receive Handling Unit from Transit process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

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 page. The standard page for this is the Receive from Transit page. 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Receive Shop Order

The RECEIVE_SHOP_ORDER process ID identifies the Receive Shop Order process in the Warehouse Data Collection page. The standard page for this is the Receive Shop Order page. 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 MANUFACTURED_DATE data item, it will be given the value automatically. If manufactured date is not used it will be given the value Null
• When the Use Automatic Value field is set to Fixed on the EXPIRATION_DATE data item, it will be given the value automatically or a calculated value is used if manufactured date is used. If expiration date is not used it will be given the value Null.
• When the Use Automatic Value field is set to Fixed on the QUANTITY data item and a handling unit created on the shop order is entered prior, it will be given the Qty to Attach value defined for the handling unit automatically. Otherwise the remaining quantity on the shop order will be given automatically.
• 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Receive Shop Order Handling Unit

The RECEIVE_SHOP_ORD_HANDL_UNIT process ID identifies the Receive Shop Order Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Shop Order page Handling Unit Structure tab. 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 Handling Unit 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 MANUFACTURED_DATE data item, it will be given the value automatically. If manufactured date is not used it will be given the value Null
• When the Use Automatic Value field is set to Fixed on the EXPIRATION_DATE data item, it will be given the value automatically or a calculated value is used if manufactured date is used. If expiration date is not used it will be given the value Null.
• 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 Handling Unit process has process specific details that can be enabled:

• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

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 page. The standard page for this is the Shop Order page. 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, it will be given the value Null automatically.
• When the Use Automatic Value field is set to Fixed on the AVAILABLITY_CONTROL_ID data item, it will be given the value Null automatically.
• 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

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

• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process

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

• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Register Arrivals

The REGISTER_ARRIVALS process ID identifies the Register Arrivals process in the Warehouse Data Collection page. The standard page for this is the Register Arrivals page. With the Warehouse Data Collection process, the Change Arrival Data, Report Arrival, and Report Arrival with Serials activities can be performed. The available source lines to be received are filtered on the selected site.

Also the user can pack the registering goods if default Packing Instruction (PACKING_INSTRUCTION_ID) is defined for the registering PO line or enter a Handling Unit Type (HANDLING_UNIT_TYPE_ID) during the process. Packing Rule (PACKING_RULE) will only be used when a Handling Unit Type is entered. Possible values for Packing Rule are listed below.

Single Handling Unit: A single handling unit of the type selected will be created. This can be used e.g. when items are packed onto a pallet in the arrival area.
By Part Capacity:     A number of handling units will be created based on the capacity for the given part for the handling unit type selected. This can be used e.g. when items arrive pre-packed in a certain type of container where packing instructions are not used.

In the Register Arrivals configuration, the camera can be enabled. When the camera is enabled, the option to take a photo and save it to the media library is available in the Windows client, Android client and the iOS client. The photos are saved as attachments in the Receipts page.

Prerequisite: Add MediaLibrary^ to the Service List for LU ReceiptInfo in the Object Connections page.

The data items in the Register Arrivals process will behave according to the following:

• For RECEIPT_REFERENCE data item Null is allowed.
• For the QC_CODE 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 SENDER data item will be given the value automatically, if the SOURCE_REF1 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_DB 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 SOURCE_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 Register Arrivals 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. Note: For serial tracked parts with automatic serial rule, and for order based lot tracked parts, serial- and lot batch numbers will be automatically set even if this process detail is disabled.
• 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Report Picking of Handling Units

The REPORT_PICKING_HU process ID identifies the Report Picking of Handling Units process in Warehouse Data Collection page. The standard page for this is Report Picking of Pick List Lines page. With the Warehouse Data Collection process, the Pick, Pick by Choice, and Unreserve Pick List Lines activities can be performed. To use the pick by choice functionality it must be enabled via the Pick by Choice setting on the Site/Warehouse Management/General tab. In addition to this you can also chose on which level to perform the picking. With this process it is also possible to pack handling units into other handling units connected to the shipment.

The data items in the Report Picking of Handling Units process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the RES_HANDLING_UNIT_ID and LOCATION_NO data items, they will be given values automatically if the AGGREGATED_LINE_ID is placed before and a value is entered.
• The ACTION data item indicates which actions will be taken. The options are:
  • Pick, the handling unit is picked.
  • Unreserve Pick List Lines, the content of the handling unit is unreserved.
  • Pick Sub Level, the current handling unit will be ignored and Report Picking of Handling Units will continue with the next handling unit in the structure.
  • Pick Parts, the current handling unit and its underlying structure will be ignored and Report Picking of Parts will be performed for the content of the structure instead.

The Report Picking of Handling Units process has specific details that can be enabled:

• If DISPLAY_ALT_HANDLING_UNIT ID, DISPLAY_HANDLING_UNIT_ID and/or DISPLAY_SSCC process details are enabled the values will be displayed in the description field in the List of Values for Aggregated Line ID together with LOCATION_NO.
• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Report Picking of Handling Units process does not support following:

• Packing into handling unit connected to the shipment when a planned packing already exists in the shipment.
• Project Deliverables.

Note that:

• If a consolidated pick list is created and one reserved handling unit consist of reservations from different shipments the user is not allowed to add the reserved handling unit to a shipment handling unit, because a shipment handling unit can only be connected to one shipment.
• The default configuration is set up to use the Start Picking process to start the Report Picking of Handling Units process.

Report Picking of Parts

The REPORT_PICKING_PART process ID identifies the Report Picking of Parts process in the Warehouse Data Collection page. The standard page for this is the Report Picking of Pick List Lines page. With the Warehouse Data Collection process, the Report Picking, Pick by Choice, and Quantity Deviation activities can be performed. To use the pick by choice functionality it must be enabled via the Pick by Choice setting on the Site/Warehouse Management/General tab. The process also handles partial picking if that is enabled on the order type or shipment type. The available pick list numbers are filtered on the selected site. With this process it is also possible to pack pick list lines into handling units connected to the shipment.

 The data items in the Report Picking of Parts 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.
• 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, it 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, it 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 Parts 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the MAX_WEIGHT_VOLUME_ERROR process detail is enabled, the system will check that the Max Weight Capacity and/or Max Volume Capacity, registered in the Handling Unit Types page, is not exceeded. If that is the case, there will be an error message and the process cannot be completed.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.
• If the PICK_BY_CHOICE_DETAILS process detail is enabled, the scanning performance when pick by choice and data item details are used will be enhanced.

The Report Picking of Parts process does not support the following:

• The activity Report Picking from Another Location
• Packing into handling unit connected to the shipment when a planned packing already existst in the shipment.
• Report Picking of parts that are serial-traced at receipt and issue (but not serial-traced in inventory), when Pick by Choice setting is enabled.
• Report Picking of pegged orders using Pick by Choice.
• Project Deliverables.

Note that:

• The default configuration is set up to use the Start Picking process to start the Report Picking of Parts process.

Report Picking of Shipment Handling Units

REPORT_PICK_SHIPMENT_HU process ID identifies the Report Picking of Shipment Handling Units process in the Warehouse Data Collection page. The standard page for this is Report Picking of Pick List Lines/Shipment Handling Units tab. With the Warehouse Data Collection process, the Pick Shipment Handling Units activity can be performed. See the Report Picking, Shipment Handling Units Activity description for more information.

The data items in the Report Picking of Shipment Handling Units process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the SHIPMENT_ID and PICK_LIST_NO data items, they will be given values automatically, if the SHP_HANDLING_UNIT_ID data item is placed before and a value is entered.
• The following data items are only used as filters: SHIPMENT_ID and PICK_LIST_NO.

The Report Picking of Shipment Handling Units process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Report Picking of Shipment Handling Units process does not support following:

• Pick reporting a shipment handling unit that contains a serial part that is serial-traced at receipt and issue
• Pick reporting a shipment handling unit that contains a catch unit of measure (Catch UoM) enabled inventory part.

Report Picking of Handling Unit Shop Order Pick List

The REPORT_PICK_HU_SO_PICK_LIST process ID identifies the Report Picking of Handling Unit Shop Order Pick List process in Warehouse Data Collection page. The standard page for this is Report Picking of Shop Order Pick List page. With the Warehouse Data Collection process, the Issue, and Pick by Choice activities can be performed. The available pick list numbers are filtered on the selected site. To use the pick by choice functionality it must be enabled via the Pick by Choice setting on the Site/Warehouse Management/General tab. In addition to this you can also chose on which level to perform the picking.

The data items in the Report Picking of Handling Unit Shop Order Pick List process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the RES_HANDLING_UNIT_ID and LOCATION_NO data items, they will be given values automatically if the AGGREGATED_LINE_ID is placed before and a value is entered.
• The ACTION data item indicates which actions will be taken. The options are:
  • Pick, the handling unit is picked.
  • Unreserve Pick List Lines, the content of the handling unit is unreserved.
  • Pick Sub Level, the current handling unit will be ignored and the process Report Picking of Handling Units Shop Order Pick List will continue with the next handling unit in the structure.
  • Pick Parts, the current handling unit and its underlying structure will be ignored and the process Report Picking of Part Shop Order Pick List will be performed for the content of the structure instead.

The Report Picking of Handling Unit Shop Order Pick List process has specific details that can be enabled:

• If DISPLAY_ALT_HANDLING_UNIT ID, DISPLAY_HANDLING_UNIT_ID and/or DISPLAY_SSCC process details are enabled the values will be displayed in the description field in the List of Values for Aggregated Line ID together with LOCATION_NO.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The default configuration is set up to use the Start Shop Order Picking process to start the Report Picking of Handling Unit Shop Order Pick List process.

Report Picking of Part Shop Order Pick List

The REPORT_PICK_PART_SO_PICK_LIST process ID identifies the Report Picking of Part Shop Order Pick List process in the Warehouse Data Collection page. The standard page for this is the Report Picking of Shop Order Pick List page. With the Warehouse Data Collection process, the Issue, Pick by Choice, Un-reserve, and Create Count Report activities can be performed. To use the pick by choice functionality it must be enabled via the Pick by Choice setting on the Site/Warehouse Management/General tab. The available pick list numbers are filtered on the selected site.

The data items in the Report Picking of Part Shop Order Pick List 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 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 Report Picking of Part 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.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Report Picking of Part Shop Order 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.

Note that:

• The default configuration is set up to use the Start Shop Order Picking process to start the Report Picking of Part Shop Order Pick List process.

Return Handling Units from Shipment Inventory

The RETURN_HU_FROM_SHIP_INV process ID identifies the Return Handling Units From Shipment Inventory process in the Warehouse Data Collection page. The standard page for this is the Handling Units In Shipment Inventory, Return command. With the Warehouse Data Collection process the Return Handling Unit in Shipment inventory activity can be performed.

The data items in the Move Handling Units Between Shipment Inventories process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the FROM_LOCATION_NO data item, the value will be given automatically if the handling unit has already been identified.

The Return Handling Units From Shipment Inventory process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• If the ALT_HANDLING_UNIT_LABEL_ID data item is not unique and HANDLING_UNIT_ID/SSCC is set to Fixed or Default, no default value can be given automatically for these data items.
  

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 page. The standard page for this is the Inventory Parts in Shipment Inventory page. 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 source 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, it 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, it 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: RECEIVER_ID.

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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Scrap Handling Unit

The SCRAP_HANDLING_UNIT process ID identifies the Scrap Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Handling Units In Stock page, accessible through the context menu, using menu item Scrap. With the Warehouse Data Collection process, the Scrap Handling Unit activity can be performed. The available handling units are filtered based on the selected site and location.

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

• When the Use Automatic Value field is set to Fixed on the LOCATION_NO data item, it will be given a value automatically if the data items identifying the handling unit is placed before LOCATION_NO.

The Scrap Handling Unit process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Scrap Handling Units in Shipment Inventory

The SCRAP_HU_IN_SHIP_INV process ID identifies the Scrap Handling Units in Shipment Inventory process in the Warehouse Data Collection page. The standard page for this is the Handling Units In Shipment Inventory, Scrap command. With the Warehouse Data Collection process the Scrap Handling Unit in Shipment Inventory activity can be performed.

The data items in the Move Handling Units Between Shipment Inventories process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the FROM_LOCATION_NO data item, the value will be given automatically if the handling unit has already been identified.

The Scrap Handling Units in Shipment Inventory process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• If the ALT_HANDLING_UNIT_LABEL_ID data item is not unique and HANDLING_UNIT_ID/SSCC is set to Fixed or Default, no default value can be given automatically for these data items.
  

Scrap Inventory Part

The SCRAP_INVENTORY_PART process ID identifies the Scrap Inventory Part process in the Warehouse Data Collection page. The standard page is the Scrap Inventory Part page.
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 the 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 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 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, it 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Scrap Parts in Shipment Inventory

The SCRAP_PARTS_IN_SHIP_INV process ID identifies the Scrap Parts in Shipment Inventory process in the Warehouse Data Collection page. The standard page is the Inventory Parts in Shipment Inventory page. With the Warehouse Data Collection process, the Scrap Parts activity can be performed.

The data items in the Scrap Parts in 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 source 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, it 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, it 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: RECEIVER_ID.

The Scrap 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Start Count Report

The START_COUNT_REPORT process ID identifies the Start Count Report process in the Warehouse Data Collection page. The standard page for this is the Count per Count Report page. The Start Count Report process continues using the Count Handling Unit per Count Report process or Count Part per Count Report process.

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

• When the Use Automatic Value field is set to Fixed on the COUNT_REPORT_LEVEL data item, and the report only includes parts or only includes Handling Units, the level will be chosen automatically.
• When the List of Values field is set to Auto Pick on the COUNT_REPORT_LEVEL data item, the process will continue with the next item on the count report.
• To determine which process to start, conditions for the subsequent processes has to be defined. Depending on a specific control data item value, in this case Count Report Level, different subsequent processes can be started. On the Data Collection Configuration/General tab, the Subsequent Control Data Item ID should be set to COUNT_REPORT_LEVEL. On the Data Collection Configuration/Subsequent Process Details tab in the field Control Item Value the value Part is entered to start the COUNT_PART_COUNT_REPORT process, and the value Handling Unit to start the COUNT_HANDL_UNIT_COUNT_REPORT process.
• Optionally you can also set subsequent data items, for each control item, in the lower part of the table on the Data Collection Configuration/Subsequent Process Details tab.

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

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Start Pick Shipment Order and Project Deliverables

The START_PICK process ID identifies the Start Pick Shipment Order and Project Deliverables in the Warehouse Data Collection page. The standard page for this is the Report Picking of Pick List Lines page. The Start Pick Shipment Order and Project Deliverables process continues using the Pick Parts Shipment Order and Project Deliverables process or Pick Handling Units Shipment Order and Project Deliverables process.

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

• When the List of Values is set to Auto Pick on the PICK_LIST_NO_LEVEL data item the process will continue with the next item on the Pick List.
• When the Use Automatic Value is set to Fixed on the PICK_LIST_NO_LEVEL data item and the pick list only includes parts or only includes handling units the level will be chosen automatically.
• To determine which process to start, conditions for the subsequent processes have to be defined. Depending on a specific control data item value, in this case Pick List No Level, different subsequent processes can be started. On the Data Collection Configuration/General tab, the Subsequent Control Data Item ID should be set to PICK_LIST_NO_LEVEL. On the Data Collection Configuration/Subsequent Process Details tab in the field Control Item Value the value Part is entered to start the PICK_PART process and the value Handling Unit to start the PICK_HU process.
• Optionally you can also set subsequent data items, for each control item, in the lower part of the table on the Data Collection Configuration/Subsequent Process Details tab.

The Start Picking Process process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Start Picking

The START_PICKING process ID identifies the Start Picking Process in the Warehouse Data Collection page. The standard page for this is the Report Picking of Pick List Lines page. The Start Picking process continues using the Report Picking of Parts process or Report Picking of Handling Units process.

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

• When the List of Values is set to Auto Pick on the PICK_LIST_NO_LEVEL data item the process will continue with the next item on the Pick List.
• When the Use Automatic Value is set to Fixed on the PICK_LIST_NO_LEVEL data item and the pick list only includes parts or only includes handling units the level will be chosen automatically.
• To determine which process to start, conditions for the subsequent processes has to be defined. Depending on a specific control data item value, in this case Pick List No Level, different subsequent processes can be started. On the Data Collection Configuration/General tab, the Subsequent Control Data Item ID should be set to PICK_LIST_NO_LEVEL. On the Data Collection Configuration/Subsequent Process Details tab in the field Control Item Value the value Part is entered to start the REPORT_PICKING_PART process and the value Handling Unit to start the REPORT_PICKING_HU process.
• Optionally you can also set subsequent data items, for each control item, in the lower part of the table on the Data Collection Configuration/Subsequent Process Details tab.

The Start Picking Process process has specific details that can be enabled:

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The Start Picking process can be started using the Start Warehouse Task process.

Start Shop Order Picking

The START_SHOP_ORDER_PICKING process ID identifies the Start Shop Order Picking Process in the Warehouse Data Collection page. The standard page for this is theReport Picking of Shop Order Pick List page. The Start Shop Order Picking process continues using the Report Picking of Part Shop Order Pick List process or Report Picking of Handling Unit Shop Order Pick List process.

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

• When the List of Values is set to Auto Pick on the PICK_LIST_NO_LEVEL data item the process will continue with the next item on the Pick List.
• When the Use Automatic Value is set to Fixed on the PICK_LIST_NO_LEVEL data item and the pick list only includes parts or only includes handling units the level will be chosen automatically.
• To determine which process to start, conditions for the subsequent processes has to be defined. Depending on a specific control data item value, in this case Pick List No Level, different subsequent processes can be started. On the Data Collection Configuration/General tab, the Subsequent Control Data Item ID should be set to PICK_LIST_NO_LEVEL. On the Data Collection Configuration/Subsequent Process Details tab in the field Control Item Value, the value Part is entered to start the REPORT_PICK_PART_SO_PICK_LIST process and the value Handling Unit to start the REPORT_PICK_HU_SO_PICK_LIST process.
• Optionally you can also set subsequent data items, for each control item, in the lower part of the table on the Data Collection Configuration/Subsequent Process Details tab.

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

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The Start Shop Order Picking process can be started using the Start Warehouse Task process.

Start Transport Task

The START_TRANSPORT_TASK process ID identifies the Start Transport Task Process in the Warehouse Data Collection page. The standard page for this is theTransport Task page. The Start Transport Task process continues using the Process Part on Transport Task process or Process Handling Unit on Transport Task process.

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

• When the List of Values is set to Auto Pick on the TRANSPORT_TASK_LEVEL data item the process will continue with the next item on the Transport Task.
• When the Use Automatic Value is set to Fixed on the TRANSPORT_TASK_LEVEL data item and the transport task only includes parts or only includes handling units the level will be chosen automatically.
• To determine which process to start, conditions for the subsequent processes has to be defined. Depending on a specific control data item value, in this case Transport Task Level, different subsequent processes can be started. On the Data Collection Configuration/General tab, the Subsequent Control Data Item ID should be set to TRANSPORT_TASK_LEVEL. On the Data Collection Configuration/Subsequent Process Details tab in the field Control Item Value the value Part is entered to start the PROCESS_TRANSPORT_TASK_PART process and the value Handling Unit to start the PROCESS_TRANSPORT_TASK_HU process.
• Optionally you can also set subsequent data items, for each control item, in the lower part of the table on the Data Collection Configuration/Subsequent Process Details tab.

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

• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Note that:

• The Start Transport Task process can be started using the Start Warehouse Task process.

Start Warehouse Task

The START_WAREHOUSE_TASK process ID identifies the Start Warehouse Task process in the Warehouse Data Collection page. The standard page for this is the My Warehouse Task page. 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 WORKER_ID data item should be the first item in the configuration.

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 page. 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 page.
• STATUS 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 Parts.
• 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. The task type is used as the Subsequent Control Data Item ID to control which subsequent process that should be started.
• To determine which process to start, conditions for the subsequent processes has to be defined. Depending on a specific control data item value, in this case Count Report Level, different subsequent processes can be started.
• Several different task types can be handled with Warehouse Task. To determine which process to start, conditions for the subsequent processes has to be defined. Depending on a specific control data item value, in this case Task Type, different subsequent processes can be started. If a warehouse task of task type Customer Order Pick List is started a configuration of the START_PICKING, REPORT_PICKING_HU, or REPORT_PICKING_PART is opened. For task type Transport Task process START_TRANSPORT_TASK, PROCESS_TRANSPORT_TASK_HU, or PROCESS_TRANSPORT_TASK_PART is opened, and for task type Shop Order Pick List process START_SHOP_ORDER_PICKING, REPORT_PICK_HU_SO_PICK_LIST and REPORT_PICK_PART_SO_PICK_LIST 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.

Unattach Part from Handling Unit

The UNATTACH_PART_FROM_HANDL_UNIT process ID identifies the Unattach Part from Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Handling Unit/Structure and Handling Unit/Structure/Handling Units tabs. With the Warehouse Data Collection process, the Unattach Part from Handling Unit activity can be performed.

The data items in the Unattach Part from Handling Unit process will behave according to the following:

• When the Use Automatic Value field is set to Fixed SERIAL_NO, LOT_BATCH_NO or CONFIGURATION_ID data item, it will be given the value * automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not serial, lot batch, or configuration 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 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 Unattach Part from Handling Unit 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 GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Unattach Receipt from Handling Unit

The UNATTACH_RECEIPT_FROM_HU process ID identifies the Unattach Receipt from Handling Unit process in the Warehouse Data Collection page. The standard page for this is the Receipt page. With the Warehouse Data Collection process, the Unattach Receipt from Handling Unit activity can be performed.

The data items in the Unattach Part from Handling Unit process will behave according to the following:

• When the Use Automatic Value field is set to Fixed on the SOURCE_REF_TYPE data item will be given the value automatically, if the SOURCE_REF1 data item is placed before
• When the Use Automatic Value field is set to Fixed on the SENDER data item will be given the value automatically, if the SOURCE_REF1 data item is placed before
• When the Use Automatic Value field is set to Fixed SERIAL_NO, LOT_BATCH_NO or CONFIGURATION_ID data item, it will be given the value * automatically, if the PART_NO data item is placed before and the value entered for PART_NO is not serial, lot batch, or configuration 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 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 Unattach Receipt from Handling Unit 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 GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Unissue Work Order

The UNISSUE_WORK_ORDER process ID identifies the process Unissue Work Order in the Warehouse Data Collection page. The standard page for this is the Unissue Maintenance Material Requisition page. 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 (up to Work Done).

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, it 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, it 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 BARCODE_ID_IS_MANDATORY process detail is enabled, the entry of a valid barcode will be required to complete the process.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the ALLOW_MULTI_SITE process detail is enabled, the process will allow unissue from all user allowed sites.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The process Unissue Work Order does not support the following:

• Set default return location.

Unpack from Handling Unit on Shipment

The UNPACK_PART_FROM_HU_SHIP process ID identifies the process Unpack from Handling Unit on Shipment in the Warehouse Data Collection page. With the Warehouse Data Collection process it is possible to unpack parts from a Handling Unit connected to a shipment pick list which is already picked. This process will unpack parts by removing the shipment attached reservation and also remove the attached quantity from the handling unit at the same time. It is possible to re-pack again with the Pack into Handling Unit on Shipment process.

• 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.

The Unpack from Handling Unit in 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.
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process.
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

The Unpack from Handling Unit in Shipment process does not support the following:

• Partial unpack, i.e. Unpack, the quantity that is reserved but not unattaching the shipment quantity.
• Non-inventory parts

Unplanned Issue Work Order

The UNPLANNED_ISSUE_WORK_ORDER process ID identifies the process Unplanned Issue Work Order in the Warehouse Data Collection page. 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 Work Done). A new material order is always created 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, it 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, it 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, it 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
• If the GTIN_IS_MANDATORY process detail is enabled, the entry of a valid GTIN will be required to complete the process
• If the GS1_BARCODE_IS_MANDATORY process detail is enabled, an entry will be required for the GS1 barcode to complete the process.

Pages

Data Collection Configuration
Data Collection Configurations
Data Collection General Basic Data
Data Collection Menu
Data Collection Process
Data Collection Processes
Data Collection Session
Data Collection Sessions
Data Collection User Group
Warehouse Data Collection

Activity Diagrams

Handle Data Collection Configuration