Transfer order confirmation
Confirm transactions
This section applies to transactions PB2_STK_MVTS_CONF_QU, PB2_STK_MVTS_CNF_JMP, PB2_STK_MVTS_CONF_2S, PB2_STK_MVTS_CONF_SU, PB2_STK_MVTS_CONF_HU and PB2_STK_MVTS_PICK_HU.
Selection options
SELECT_OPTS
Generic fields:
TO_NUMBER or TANUM - Transfer order number
TO_ITEM or TAPOS - Transfer order item number
MATERIAL or MATNR - SAP material number
BATCH or CHARG - SAP batch number
PLANT or WERKS - Plants
STORE_LOC or LGORT - Storage locations
ST_TYPE_S or VLTYP - Source storage type
ST_TYPE_D or NLTYP - Destination storage type
ST_BIN_S or VLPLA - Source storage bin
ST_BIN_D or NLPLA - Destination storage bin
ST_STATUS or BESTQ - Stock status
SP_STOCK or SOBKZ – Special stock type
SP_STOCK_NUM or SONUM – Special stock number
SU_S or VLENR - Source storage unit number
SU_D or NLENR - Destination storage unit number
SU or LENUM - Storage unit number
DELIVERY or VBELN - SAP delivery number
DELIVERY_ITEM or POSNR - SAP delivery item number
QUEUE - WM queue
BETYP - Requirement type
BENUM - Requirement number
MBLNR - Material document number
MJAHR - Material document year
TBNUM - WM Transfer requirement number
AUFNR or PROD_ORDER or PROCESS_ORDER - Order numbers
SHIPMENT or TKNUM - Transportation shipment number
SELECT_OPTS_ACTIONS
BACK - back to previous screen.
CLEAR_INPUT - clear all input fields.
VAR_CHOOSE – select from saved variants.
VAR_SAVE – save the selection entries as a variant.
SELECT – proceed to next screen.
TO list
LIST_TO
Primary: /TCTM/LTAK (LTAK) Secondary: None
LIST_TO_ACTIONS
BACK - back to previous screen.
LIST_TO_HEADER
Primary: /TCTM/LTAK (LTAK) Secondary: None
LIST_TO_HEADER_EX
n/a
LIST_TO_SORT
Primary: /TCTM/LTAK
TO item list
LIST_TO_ITEM
Primary: /TCTM/LTAP (LTAP) Secondary: /TCTM/LTAK (LTAK), /TCTM/MAKT (MAKT), /TCTM/MARA (MARA), /TCTM/MARC (MARC), /TCTM/MARD (MARD)
LIST_TO_ITEM_ACTIONS
BACK - back to previous screen.
LIST_TO_ITEM_HEADER
Primary: /TCTM/LTAP (LTAP) Secondary: /TCTM/LTAK (LTAK), /TCTM/MAKT (MAKT), /TCTM/MARA (MARA), /TCTM/MARC (MARC), /TCTM/MARD (MARD)
LIST_TO_ITEM_HEADER_EX
n/a
LIST_TO_ITEM_SORT
Primary: /TCTM/LTAP
Source detail input
INPUT_SOURCE_DETAIL
Primary: /TCTM/LTAP (LTAP) Secondary: /TCTM/LTAK (LTAK), /TCTM/MAKT (MAKT), /TCTM/MARA (MARA), /TCTM/MARC (MARC), /TCTM/MARD (MARD), LAGP (LAGP), T313A (T313A), T313B (T313B) Verification fields: MATNR_VERIF - material verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. CHARG_VERIF* - batch verification class /TCTM/WM_APP_510_FIELDS controlled by table T313B.
VLENR_VERIF - source SU verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. VLTYP_VERIF - source storage type verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. VLPLA_VERIF - source storage bin verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. VSOLA_VERIF - source target quantity in alternate unit with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. VSOLM_VERIF - source target quantity in stockkeeping unit with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. ZERO_QTY* - confirm zero quantity with class /TCTM/WM_APP_510_FIELDS controlled by table T313B and linked to the quantity verification. ZERO_QTY_IN* - allow confirmation of zero quantity - to be used if verification profiles are not used/setup. *Available as of release 5.8.0
INPUT_SOURCE_ACTIONS
BACK - back to previous screen.
CLEAR_INPUT - clear all input fields.
CONTINUE – proceed to next screen. CREATE_PICK_HU - create Pick HU (if required).
Note
As of release 5.8.0, the following new zero quantity logic is available.
ZERO_QTY is linked to the verification profile for "quantity" verification and will be displayed if the "quantity" verification is active. The field is required to confirm a zero quantity rather than entering "0" in VSOLA_VERIF or VSOLM_VERIF fields and if so then the material and batch verification fields will be ignored.
ZERO_QTY_IN is an alternative zero quantity field that can be setup in AMD to allow confirming with a zero quantity even if the quantity verification is not active in the verification profile. It is mutually exclusive to the field ZERO_QTY and will only display if that is not.
CHARG_VERIF can be used with the standard field class /TCTM/WM_APP_510_FIELDS for batch verifications if the client has used the hidden field T313B-VSBAT to activate batch verification. Alternatively use the field class /TCTM/WM_APP_FIELD_VERIFY to use PreBilt's standard verification logic.
Create pick HU
Note
This is used in the app transaction PB2_STK_MVTS_PICK_HU and is called by the action "CREATE_PICK_HU".
INPUT_PICK_HU_CREATE
Field: VHILM_IN - Packaging material number
INPUT_PICK_HU_CREATE_ACTIONS
AMD not required - standard popup actions.
OK - create pick HU. CANCEL - go back to previous screen.
Zero stock input
INPUT_ZERO_STOCK
Primary: /TCTM/LTAP (LTAP) Secondary: /TCTM/LTAK (LTAK), /TCTM/MAKT (MAKT), /TCTM/MARA (MARA), /TCTM/MARC (MARC), /TCTM/MARD (MARD), LAGP (LAGP), T313A (T313A), T313B (T313B)
INPUT_ZERO_STOCK_ACTIONS
BACK - back to previous screen. CONTINUE - confirm details.
Destination detail input
INPUT_DEST_DETAIL
Primary: /TCTM/LTAP (LTAP) Secondary: /TCTM/LTAK (LTAK), /TCTM/MAKT (MAKT), /TCTM/MARA (MARA), /TCTM/MARC (MARC), /TCTM/MARD (MARD), LAGP (LAGP), T313A (T313A), T313B (T313B) Verification fields: MATNR_VERIF - material verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. CHARG_VERIF* - batch verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B.
NLENR_VERIF - destination SU verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. NLTYP_VERIF - destination storage type verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. NLPLA_VERIF - destination storage bin verification with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. NSOLA_VERIF - destination target quantity in alternate unit with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. NSOLM_VERIF - destination target quantity in stockkeeping unit with class /TCTM/WM_APP_510_FIELDS controlled by table T313B. ZERO_QTY* - confirm zero quantity with class /TCTM/WM_APP_510_FIELDS controlled by table T313B and linked to the quantity verification. ZERO_QTY_IN* - allow confirmation of zero quantity - to be used if verification profiles are not used/setup. *Available as of release 5.8.0
INPUT_DEST_ACTIONS
BACK - back to previous screen.
CLEAR_INPUT - clear all input fields.
CONTINUE – proceed to next screen.
Note
As of release 5.8.0, the following new zero quantity logic is available.
ZERO_QTY is linked to the verification profile for "quantity" verification and will be displayed if the "quantity" verification is active. The field is required to confirm a zero quantity rather than entering "0" in NSOLA_VERIF or NSOLM_VERIF fields and if so then the material and batch verification fields will be ignored.
ZERO_QTY_IN is an alternative zero quantity field that can be setup in AMD to allow confirming with a zero quantity even if the quantity verification is not active in the verification profile. It is mutually exclusive to the field ZERO_QTY and will only display if that is not.
CHARG_VERIF can be used with the standard field class /TCTM/WM_APP_510_FIELDS for batch verifications if the client has used the hidden field T313B-VDBAT to activate batch verification. Alternatively use the field class /TCTM/WM_APP_FIELD_VERIFY to use PreBilt's standard verification logic.
General configuration elements
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.
ALLOW_CONFIRM_TO
Allows transfer order confirmation. If toggle = ON, the app will allow confirmation of transfer orders that are already created, or created via the app. If toggle = OFF, if searching for transfer orders to confirm, the app will not be able to determine a processing mode. If creating a new transfer order, the app will not allow direct confirmation of that transfer order.
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)
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.
UOM_CONVERSION
You can identify and setup the quantity and the UOM fields that should be converted to the alternative UOM.
UOM_SEQ
You can create an app transaction specific sequence of UOM types that is different from the global default.
ALLOW_SINGLE_LIST
Allows the app to return to a list screen when the penultimate item on that list screen is processed so that the user can then select the last items from the list rather than the last items being automatically selected. It applies to both header or item lists.
SYS_GUIDE_TO
If set to blank, the user selects a transfer order from the TO List. The next screen is either the TO Item List (if multiple open items) or the confirmation screen (if only one). After confirming an item, the user returns to the TO List, even if more items remain. If set to A, the same list is generated, but the top transfer order (based on LIST_TO_SORT) is auto-selected and passed to the next screen. The list screen is skipped. If set to B, all transfer orders are auto-selected and passed to the next screen. The list screen is skipped, and sort order does not apply. If set to C, the user selects a transfer order like with blank. If it has multiple items, the app cycles through all items until the transfer order is fully confirmed, then returns to the list.
SYS_GUIDE_TO_ITEM
Determines the flow logic of the app. If toggle = ON, the same list of transfer order items is generated as if the value was toggle = OFF, but the user will not be presented with the list screen. Instead, the top transfer order item from the list will be automatically selected and passed to the next screen. The sort of the list, and therefore the way to control which transfer order item is selected for the user, is determined by the sort order defined in LIST_TO_ITEM_SORT. If toggle = OFF, the LIST_TO_ITEM screen is displayed, and the user selects a transfer order item to count from the item 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.
STYPE_FILTER
Enables filtering of storage types, allowing the user to include or exclude specific values in the list view.
QUEUE_FILTER
Enables filtering of queues assigned to the warehouse, allowing the user to include or exclude specific values in the list view.
ST_BIN_FILTER
Enables filtering of storage bins, allowing the user to include or exclude specific values in the list view.
STYPE_LIST
Storage type list, if required.
PACKMAT_LIST
Allows a static list to be maintained for choosing a packaging material. Used in the Pick HU app transaction PB2_STK_MVTS_PICK_HU. If the user is required to choose from a list of packaging materials, the allowed values can be set here. The value and description of the packaging materials are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP.
APP_TEXTS
Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO
Information about the transaction.
Last updated
Was this helpful?