VLMOVE configuration

Note

This setup is for the use of general postings to be used to perform the postings that the SAP transaction VLMOVE performs.

This is applicable to the standard supplied app transaction PB2_GEN_POST_VLMOVE.

List action groups

To setup the allowed action groups see:

List action groups

Note

As standard we have created two action groups: "Goods Issue" and "Transfer Postings".

List movement types

To setup the allowed movement types see:

List movement types

Note

The movement types used in this VLMOVE app transaction are the SAP process codes.

Classes /TCTM/WM_APP_513_VLMOVE and /TCTM/WM_APP_513_VLMOVE_TO are generally assigned to the process codes.

Handling unit input

Configuration element	Available structures
INPUT_VLMOVE_HU	Primary: /TCTM/VEKPVB Secondary: None
INPUT_VLMOVE_HU_ACTIONS	BACK - back to previous screen. CLEAR_INPUT -clear all input fields. CONTINUE – proceed to next screen.

Item input

Configuration element	Available structures
INPUT_VLMOVE_ITEM	Primary: /TCTM/VEKOVB Secondary: /TCTM/VEKPVB, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, LQUA
INPUT_VLMOVE_ITEM_ACTIONS	BACK - back to previous screen. CLEAR_INPUT - clear all input fields. SAVE – proceed to post this item. ADD_TO_BASKET - add item to basket. VIEW_BASKET - view basket.

Basket list

Configuration element	Available structures
LIST_VLMOVE_BASKET	Primary: /TCTM/HUM_DATA_MOVE_TO Secondary: /TCTM/VEPOVB, /TCTM/VEKPVB, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, LQUA
LIST_VLMOVE_BASKET_ACTIONS	EXIT - returns to selection. EMPTY_BASKET - clear the basket. SAVE - process the basket for posting. ADD_NEW_ITEM - return to lists for next item. DELETE - remove the basket item from basket.
LIST_VLMOVE_BASKET_HEADER	Primary: /TCTM/HUM_DATA_MOVE_TO Secondary: /TCTM/VEPOVB, /TCTM/VEKPVB, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, LQUA
LIST_VLMOVE_BASKET_HEADER_EX	n/a
LIST_VLMOVE_BASKET_SORT	Primary: /TCTM/HUM_DATA_MOVE_TO

Basket input

Configuration element	Available structures
INPUT_VLMOVE_BASKET	Primary: /TCTM/VEKOVB Secondary: /TCTM/VEKPVB, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, LQUA
INPUT_VLMOVE_BASKET_ACTIONS	BACK - back to previous screen. CLEAR_INPUT - clear all input fields. SAVE – proceed to post. ADD_TO_BASKET – update basket. DELETE – remove item from basket.

Posting

Configuration element	Available structures
INPUT_VLMOVE_POST	Primary: /TCTM/HUM_DATA_MOVE_TO Secondary: /TCTM/VEPOVB, /TCTM/VEKPVB
INPUT_VLMOVE_POST_ACTIONS	BACK - back to previous screen. CLEAR_INPUT -clear all input fields. SAVE – proceed to post. VIEW_BASKET - view basket.

General configuration elements

Configuration element	Descriptions
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.
ACTION_LIST	Allows a static list to be maintained for choosing an action group. If the user needs to choose from a list of action groups, the allowed values can be set here. The value and description of the action groups are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP. More information on how a fixed list key configuration option can be set and how it works can be found in the Functional Design Document.
ACTION_TYPE_LIST	Allows a static list of movement types to be maintained for a given action group. If users need to choose from predefined movement types, the allowed values can be set here. Values and descriptions appear as configured, but unlike filters, no validation occurs until the data is submitted to SAP. For setup details, see the Functional Design Document. The standard class /TCTM/WM_APP_513_MIGO posts the material document. When called from app 512 – Stock Enquiry, /TCTM/WM_APP_513_MIGO_TO also creates a 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)
ACTION_TYPE_VERIFY_BESTQ_S	Validation of stock type ‘Blocked’.
ACTION_TYPE_VERIFY_BESTQ_Q	Validation of stock type ‘Quality’.
ACTION_TYPE_VERIFY_BESTQ_U	Validation of stock type ‘Unrestricted’.
ACTION_TYPE_VERIFY_BESTQ_R	Validation of stock type ‘Returns’.
SERIAL_OVERRIDE	Serialisation Overrides
SH_PARAMS_1	Search Help Parameter Map.
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.
CALL_TRANSACTION_VLMOVE	Defines transactions that can be called from this app automatically.
SUPPRESS_SUCCESS_VLMOVE	Allows success messages to be suppressed. If toggle = ON, success messages are suppressed. If toggle = OFF, success messages are not suppressed.
UOM_FILTER	Enables filtering of unit of measure, allowing the user to include or exclude specific values in the list view.
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.
CC_FILTER	This is a possible filter element that can be used, as required, to allow filtering of the cost centers (if these need to be restricted to a subset of cost centers instead of displaying a list of all cost centers assigned to a PreBilt warehouse). It must be used in conjunction with a suitable field class assigned to the field.
GL_FILTER	This is a possible filter element that can be used, as required, to allow filtering of the General Ledger accounts (if these need to be restricted to a subset of general ledgers that are allocated to the PreBilt warehouse). It must be used in conjunction with a suitable field class assigned to the field.
PLANTS_LIST	List of plants.
SLOCS_LIST	List of storage locations.
CC_LIST	Allows a static list to be maintained for choosing a cost center. If the user needs to choose from a list of cost centers, the allowed values can be set here. The value and description of the cost centers are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP.
GL_LIST	Allows a static list to be maintained for choosing a general ledger account. If the user needs to choose from a list of general ledgers, the allowed values can be set here. The value and description of the general ledgers 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.