PB2_GEN_POST_IMB_JMP configuration
Last updated
Was this helpful?
Last updated
Was this helpful?
LIST_ACT_GROUPS
Primary: None Secondary: None
LIST_ACT_GROUPS_ACTIONS
Primary: None Secondary: None
LIST_ACT_GROUPS_HEADER
Primary: None Secondary: None
LIST_ACT_GROUPS_HEADER_EX
Primary: None Secondary: None
LIST_ACT_GROUPS_SORT
Primary: None Secondary: None
LIST_MOVE_TYPES
Primary: None Secondary: None
LIST_MOVE_TYPES_ACTIONS
Primary: None Secondary: None
LIST_MOVE_TYPES_HEADER
Primary: None Secondary: None
LIST_MOVE_TYPES_HEADER_EX
Primary: None Secondary: None
LIST_MOVE_TYPES_SORT
Primary: None Secondary: None
INPUT_****_MATERIAL
Primary: None Secondary: None
INPUT_****_MATERIAL_ACTIONS
Primary: None Secondary: None
INPUT_****_ITEM
Primary: None Secondary: None
INPUT_****_ITEM_ACTIONS
Primary: None Secondary: None
LIST_****_BASKET
Primary: None Secondary: None
LIST_****_BASKET_ACTIONS
Primary: None Secondary: None
LIST_****_BASKET_HEADER
Primary: None Secondary: None
LIST_****_BASKET_HEADER_EX
Primary: None Secondary: None
LIST_****_BASKET_SORT
Primary: None Secondary: None
SUMMARISE_****_BASKET
Primary: None Secondary: None
INPUT_****_BASKET
Primary: None Secondary: None
INPUT_****_BASKET_ACTIONS
Primary: None Secondary: None
INPUT_****_POST
Primary: None Secondary: None
INPUT_****_POST_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.
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_****
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.
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.
****_MTYPE_FILTER
These are all possible filter elements that can be used, as required, to allow filtering of the movement types. They have been created as examples and can be used or changed as required. They must be used in conjunction with a suitable field class assigned to the field.
PLANT_LIST
Allows a static list to be maintained for plants. If the user needs to choose from a list of plants, the allowed values can be set here. The value and description of the plants are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP.
SLOC_LIST
Allows a static list to be maintained for choosing a storage location. If the user is required to select from a list of storage locations, the allowed values can be set here. The value and description of the storage locations are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP.
****_MTYPE_LIST
Allows a static list to be maintained for choosing a movement type. These have been created as examples and can be copied or changed as required. If you need to choose from a list of movement types, the allowed values can be set here on the appropriate list. The value and description of the movement types are displayed as set up, and unlike a filter option, no validation will take place until the data is submitted to SAP and so no field class is required.
UNLOADING_LIST
Unloading point list.
APP_TEXTS
Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO
Information about the transaction.
