Configuration
Last updated
Was this helpful?
Last updated
Was this helpful?
This section applies to all the PB2 Picking and Packing transaction unless stated for WM only.
SELECT_OPTS
Primary: None Secondary: None
SELECT_OPTS_ACTIONS
Primary: None Secondary: None
LIST_OBD
Primary: /TCTM/LIKP_S Secondary: /TCTM/ADRC_S, /TCTM/KNA1_S, /TCTM/LIKP_S, /TCTM/VBUK_S
LIST_OBD_ACTIONS
Primary: None Secondary: None
LIST_OBD_HEADER
Primary: None Secondary: None
LIST_OBD_HEADER_EX
Primary: None Secondary: None
LIST_OBD_SORT
Primary: None Secondary: None
LIST_PICKTYPE
Primary: None Secondary: None
LIST_PICKTYPE_ACTIONS
Primary: None Secondary: None
LIST_PICKTYPE_SORT
Primary: None Secondary: None
INPUT_OBD_HEADER
Primary: None Secondary: /TCTM/ADRC_S, /TCTM/KNA1_S, /TCTM/LIKP_S, /TCTM/VBUK_S
INPUT_OBD_HEADER_ACTIONS
Primary: None Secondary: None
LIST_OBD_ITEM_WM
Primary: /TCTM/LIPS_S Secondary: /TCTM/LIKP_S, /TCTM/LIPS_S, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, T001L, /TCTM/VBUK_S, /TCTM/VBUP_S
LIST_OBD_ITEM_ACTIONS_WM
Primary: None Secondary: None
LIST_OBD_ITEM_HEADER_WM
Primary: None Secondary: /TCTM/ADRC_S, /TCTM/ADRC_S, /TCTM/KNA1_S, /TCTM/KNA1_S
LIST_OBD_ITEM_HEADER_EX_WM
Primary: None Secondary: None
LIST_OBD_ITEM_SORT_WM
Primary: None Secondary: None
LIST_OBD_ITEM_IM
Primary: /TCTM/LIPS_S Secondary: /TCTM/LIKP_S, /TCTM/VBUP_S, /TCTM/VBUK_S, T001L, /TCTM/MLGN, /TCTM/LIPS_S, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD
LIST_OBD_ITEM_ACTIONS_IM
Primary: None Secondary: None
LIST_OBD_ITEM_HEADER_IM
Primary: None Secondary: /TCTM/ADRC_S, /TCTM/ADRC_S, /TCTM/KNA1_S, /TCTM/KNA1_S
LIST_OBD_ITEM_HEADER_EX_IM
Primary: None Secondary: None
LIST_OBD_ITEM_SORT_IM
Primary: None Secondary: None
INPUT_PICK
Primary: /TCTM/LIPS_S Secondary: /TCTM/LIKP_S, /TCTM/LIPS_S, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, T001L, /TCTM/ADRC_S, /TCTM/ADRC_S, /TCTM/KNA1_S, /TCTM/KNA1_S
INPUT_PICK_ACTIONS
Primary: None Secondary: None
FE_APP
Frontend class to use in running the transaction. Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.
MATERIAL_SEARCH_SEQ
Defines the search sequence for materials and the relevant conversion exits. Valid Values: M – Material D – Description E – EAN code (the EAN code for any unit of measure in the material master) B – Storage Bin (Plant/Data Stor 1 view of material master)
DOCUMENT_TYPE
Defines the document types compatible with this app. Standard document types are: LF - Outbound Delivery, document category J NL - Replenishment Delivery, document category J LO - Outbound w/o Ref, document category J UB - Stock Transport Order, document category F OR - Sales Order, document category C LP - Scheduling Agreement, document category 8 0001 - Road Shipment, document category 8 0002 - Collect Shipment, document category 8 0003 - Collective Shipment, document category 8 If the document is to be included on a shipment, and the shipment needs to have a ‘Planned’ status prior to picking of the delivery, ‘Planned Shipment Required’ should be set to toggle = ON. If shipments are not used, then ‘Planned Shipment Required’ should be set to toggle = OFF.
SHORT_PICK_LIST
Allows IM picks to be short picked. Valid Values: A - Do not update Delivery Quantity with Pick Quantity. This will result in the delivery line status changing to ‘B’ (partially picked). B - Update Delivery Quantity with Pick Quantity. This will result in the delivery quantity being updated with the total pick quantity and the status changing to ‘C’ (fully picked). DRP blank should be toggle = ON when maintained on the INPUT_PICK AMD, as a blank value is required when the full delivery quantity is being picked.
SERIAL_OVERRIDE
Serialisation Overrides
CALL_TRANSACTION
Defines transactions that can be called from this app automatically.
SUPPRESS_SUCCESS
Allows success messages to be suppressed. If toggle = ON, success messages are suppressed. If toggle = OFF, success messages are not suppressed.
LOCK_LEVEL
Configure app to lock delivery data during processing at either the header level or item level. Valid values: ‘HEADER’ will lock the delivery when selecting directly from the selection screen, or from the ‘List OBD’ screen. ‘ITEM’ will lock the delivery item when selecting an item from the delivery list, this will enable multiple users to pick the same delivery simultaneously.
MAX_OBD
Maximum number of documents to find in search results. Blank value results in no restriction on the number of records found during search.
SYS_GUIDE_OBD
If set to blank, the user selects an outbound delivery from the Delivery List. If it has multiple open item lines, the Delivery Item List is shown; if it has one IM-relevant item, the pick screen appears; if WM-relevant, it jumps to the stock movements app. After picking, even if items remain, the user is returned to the Delivery List to choose the next (or same) delivery. If set to A, the list is generated the same as for blank, but the top delivery is auto-selected based on the LIST_OBD_SORT order. Navigation follows the same logic as above. If set to B, the same list is generated, but all deliveries are auto-selected and passed on. If multiple deliveries or lines are found, the Delivery Item List is shown; if only one item, it goes to the pick screen. Sort order doesn't apply in this mode. If set to C, the user selects a delivery from the Delivery List as with blank. However, if it has multiple items, the app cycles through them until fully picked, then returns to the list.
SYS_GUIDE_PICKTYPE
Determines the flow logic of the app. If set to blank, the LIST_PICKTYPE screen will be displayed for the user to decide whether to process IM picks before or after WM picks after each pick. If set to A, the LIST_PICKTYPE screen will be suppressed. The sort of the list, and therefore the way to control whether IM picking is carried out before WM, is determined by the sort order defined in LIST_PICKTYPE_SORT. If set to C, the user selects the pick type in the same way as if it had been set to blank. However, if the pick type selected has more than one item to be picked, the item list will be displayed until that pick type has been fully picked, before continuing with the remaining pick type. Note: B is not a valid entry for Pick Type list screen.
SYS_GUIDE_OBD_ITEM_WM
If set to blank, the user selects an item from the Delivery Item List. The pick pack app then jumps to the stock movements transaction (as configured in CALL_TRANSACTION). For setup details, refer to the Stock Movements Configuration Guide. After picking, even if items remain, the user returns to the Delivery List to select the next (or same) delivery. If set to A, the same item list is generated, but the top item (based on SYS_GUIDE_OBD_ITEM_WM sort order) is auto-selected and passed to the stock movements transaction. If set to B, all items are auto-selected and passed on. The list screen is skipped, and sort order is ignored. If set to C, the user selects an item as with blank. If multiple items exist, the list remains until all are picked, then returns to the Delivery List.
SYS_GUIDE_OBD_ITEM_IM
System guided outbound delivery item. Valid values are: If toggle = ON, the same list of outbound delivery items is generated, as if the value was toggle = OFF, but the user will not be presented with the list screen. Instead, the top outbound delivery item from the list will be automatically selected and passed to the next screen; the ‘Input Pick’ screen. The sort of the list, and therefore the way to control which outbound delivery item is selected for the user, is determined by the sort order defined in LIST_OBD_SORT. If toggle = OFF, the LIST_OBD_ITEM_IM screen is displayed, and the user selects a delivery item from the list.
PLANT_FILTER
Enables filtering of plants assigned to the warehouse, allowing you to include or exclude specific values in the list view.
SLOC_FILTER
This is a possible filter element that can be used, as required, to allow filtering of the storage locations (if these need to be restricted to a subset of locations that are allocated to the PreBilt warehouse). It has been created as an example and can be used or changed as required. It must be used in conjunction with a suitable field class assigned to the field.
STAGE_FILTER
Allows filtering based on staging location.
DOOR_FILTER
Allows filtering based on warehouse door.
APP_TEXTS
Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO
Information about the transaction.
