Jumps to general postings

Note

This setup is for the use of general postings as a transaction that you jump to from Stock Enquiry. The initial selection of the specific stock record and the appropriate process/movement type is made in Stock Enquiry and you are taken straight to the item details screen for further processing with all relevant data pre-populated.

This is applicable to the following standard supplied app transactions: PB2_GEN_POSTING_JMP and PB2_GEN_POST_IMB_JMP.

List action groups

To setup the allowed action groups see:

List action groups

Note

This must still be setup for "jump" transactions with at least one group.

List movement types

To setup the allowed movement types see:

List movement types

Note

This must still be setup and controls what actions are visible within the Stock Enquiry app.

Classes /TCTM/WM_APP_513_MIGO and /TCTM/WM_APP_513_MIGO_TO are generally assigned to the movement types.

Material input

This is not required and can be left blank.

Item input

Note

The material relevant fields and movement type will be pre-populated with the material details from Stock Enquiry.

Configuration element	Available structures
INPUT_****_ITEM	Primary: /TCTM/BAPI2017_GM_ITEM_SHOW, BAPI2017_GM_HEAD_01 Secondary: LQUA, LAGP, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, /TCTM/MB52, BAPI2017_GM_CODE
INPUT_****_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.

Note

For IM Multi-bin versions of the app, the field VLPLA will be used to represent the source bin from which the stock will be issued and the field class /TCTM/WM_APP_608_FIELDS_VLPLA should be assigned which will create a pulldown list of suitable bins with stock.

Basket list

Configuration element	Available structures
LIST_****_BASKET	Primary: /TCTM/BAPI2017_GM_ITEM_CREATE Secondary: /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN
LIST_****_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_****_BASKET_HEADER	Primary: /TCTM/BAPI2017_GM_ITEM_CREATE Secondary: /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN
LIST_****_BASKET_HEADER_EX	n/a
LIST_****_BASKET_SORT	Primary: /TCTM/BAPI2017_GM_ITEM_CREATE
SUMMARISE_****_BASKET	Configuration option to allow different ways of updating the basket, where the item has previously been processed and the item details are the same: If set to blank, you will receive an error message if item is already in the basket. You need to remove the existing item before the new one can be added. If set to A, then the quantity in the basket for the matching item will be increased by the quantity entered. If set to B, then a new basket entry will be created, resulting in multiple basket entries for the item.

Basket input

Configuration element	Available structures
INPUT_****_BASKET	Primary: /TCTM/BAPI2017_GM_ITEM_SHOW, BAPI2017_GM_HEAD_01 Secondary: LQUA, LAGP, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN, /TCTM/MB52, BAPI2017_GM_CODE
INPUT_****_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

Note

If you want to be able to skip this screen you must remove all the fields from the AMD configuration element. The app will post the document automatically using the system date.

Configuration element	Available structures
INPUT_****_POST	Primary: BAPI2017_GM_HEAD_01 Secondary: None
INPUT_****_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	Available structures
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.
SPEC_STOCK_LIST	Allows a list to be maintained for choosing special stock.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.