General postings using reservations

Note

This section shows the setup for General Postings that uses reservations to selection items for posting and this includes posting against services orders, process orders, production orders and network orders. Transactions PB2_GEN_POSTING_RESV and PB2_GEN_POST_RES_IMB are the standard delivered app transactions.

From release 5.7 onwards the original app transactions of planned goods issue to service order PB2_GEN_POSTING_SO and PB2_GEN_POST_SO_IMB are essentially replaced by the above two transactions respectively and will no longer be maintained.

List action groups

To setup the allowed action groups see:

List action groups

Note

If only one action group is created then the screen will be automatically skipped.

List movement types

To setup the allowed movement types see:

List movement types

Note

Only movement types in SAP that are marked as relevant for reservations (T156-RSTYP not blank) that have entries in the SAP table RESB can be processed with these settings.

Classes /TCTM/WM_APP_513_GI_RESV and /TCTM/WM_APP_513_GI_RESV_TO are generally assigned to the movement types.

Reservation / order selection input

Configuration element
Available structures

INPUT_****

Primary: /TCTM/RPKF; /TCTM/RESB; CAUFV Secondary: None

INPUT_****_ACTIONS

BACK - back to previous screen.

CLEAR_INPUT -clear all input fields.

CONTINUE – proceed to next screen.

Reservation / order list

Configuration element
Available structures

LIST_****

Primary: /TCTM/RKPF; CAUFV Secondary: None

LIST_****_ACTIONS

BACK - back to previous screen.

LIST_****_HEADER

Primary: /TCTM/RKPF; CAUFV Secondary: None

LIST_****_HEADER_EX

n/a

LIST_****_SORT

Primary: /TCTM/RKPF Secondary: None

Document item list

Configuration element
Available structures

LIST_****_ITEM

Primary: /TCTM/RESB Secondary: /TCTM/RKPF, CAUFV, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN

LIST_****_ITEM_ACTIONS

BACK - back to previous screen. VIEW_BASKET - view basket.

LIST_****_ITEM_HEADER

Primary: /TCTM/RESB Secondary: /TCTM/RKPF, CAUFV, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN

LIST_****_ITEM_HEADER_EX

n/a

LIST_****_ITEM_SORT

Primary: /TCTM/RESB Secondary: None

Material input

This is not required and can be left blank.

Item input

Configuration element
Available structures

INPUT_****_ITEM

Primary: /TCTM/RESB Secondary: /TCTM/RKPF, CAUFV, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN

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, 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.

Post input

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’.

SUPPRESS_SUCCESS

Allows success messages to be suppressed. If toggle = ON, success messages are suppressed. If toggle = OFF, success messages are not suppressed.

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.

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_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.

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?