Goods receipt for production / process orders configuration

Note

The app transaction PB2_GEN_POSTING_PP has been created as a combination of the goods issue to order movements (supported in the standard reservation processing app transaction PB2_GEN_POSTING_RESV), and the goods receipt for production / process orders so that the app transaction can be easily given to a production team that is required to process both the component issues as well as the finished goods receipt from production.

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

For the goods issue movement types use classes /TCTM/WM_APP_513_GI_RESV or /TCTM/WM_APP_513_GI_RESV_TO.

For the goods receipt movement types use classes /TCTM/WM_APP_513_GRPROD_IM or /TCTM/WM_APP_513_GRPROD_IM_TO.

Order selection input

Note

For the goods issue movements see the configuration in the General Postings using reservations.

The below sections are for the goods receipt setup.

Configuration element	Available structures
INPUT_GRIM	ORDER_NUMBER or AUFNR - order number MATERIAL or MATNR or PLNBEZ - SAP material number PROD_PLANT or WERKS - Production plant CATEGORY or AUTYP - order category ORDER_TYPE or AUART - order type ORDER_PRIO or APRIO - order priority MRP_CNTRL or DISPO - MRP controller SALES_ORDER or KDAUF - Sales order number SALES_ORDER_ITM or KDPOS - Sales order item number WBS_ELEMENT or PSPEL - WBS element SEQ_NO or SEQNR - sequence number PROD_SCHED or FEVOR - Production supervisor/scheduler PLAN_PLANT or PLWRK - Planning plant
INPUT_GRIM*_ACTIONS	BACK - back to previous screen. CLEAR_INPUT -clear all input fields. CONTINUE – proceed to next screen.

Document list

Configuration element	Available structures
LIST_GRIM	Primary: /TCTM/BAPI_ORDER_HEADER1 Secondary: None
LIST_GRIM_ACTIONS	BACK - back to previous screen.
LIST_GRIM_HEADER	Primary: /TCTM/BAPI_ORDER_HEADER1 Secondary: None
LIST_GRIM_HEADER_EX	n/a
LIST_GRIM_SORT	Primary: /TCTM/BAPI_ORDER_HEADER1

Document item list

Note

This is not required for goods receipt process because there is only ever one material being received per order.

Item input

Configuration element	Available structures / fields
INPUT_GRIM_ITEM	Primary: /TCTM/BAPI_ORDER_ITEM Secondary: /TCTM/BAPI_ORDER_HEADER1, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN
INPUT_GRIM_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.

Batch detail input

Note

This is a pop-up screen to add the production and expiration dates if required by the system.

Configuration element	Available structures / fields
INPUT_GRIM_BATCH_DETAIL	PROD_DATE - production date EXPIRYDATE - expiration date
INPUT_GRIM_BATCH_ACTIONS	CONTINUE - proceed. CANCEL - return back to previous input screen.

Basket list

Configuration element	Available structures
LIST_GRIM_BASKET	Primary: /TCTM/BAPI2017_GM_ITEM_CREATE Secondary: /TCTM/BAPI_ORDER_HEADER1, /TCTM/BAPI_ORDER_ITEM, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN
LIST_GRIM_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_GRIM_BASKET_HEADER	Primary: /TCTM/BAPI2017_GM_ITEM_CREATE Secondary: /TCTM/BAPI_ORDER_HEADER1, /TCTM/BAPI_ORDER_ITEM, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN
LIST_GRIM_BASKET_HEADER_EX	n/a
LIST_GRIM_BASKET_SORT	Primary: /TCTM/BAPI2017_GM_ITEM_CREATE
SUMMARISE_GRIM_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 / fields
INPUT_GRIM_BASKET	Primary: /TCTM/BAPI_ORDER_ITEM Secondary: /TCTM/BAPI_ORDER_HEADER1, /TCTM/MAKT, /TCTM/MARA, /TCTM/MARC, /TCTM/MARD, /TCTM/MLGN
INPUT_GRIM_BASKET_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.

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	Description
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’.
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_GRIM	Defines transactions that can be called from this app automatically.
SUPPRESS_SUCCESS_GRIM	Allows success messages to be suppressed. If toggle = ON, success messages are suppressed. If toggle = OFF, success messages are not suppressed.
LOCK_LEVEL_GRIM*	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.
GRIM_MTYPE_FILTER	n/a
ORDER_CAT_LIST	This can be used in the Goods Receipt for Production or Process orders selection. Initial list is setup with: 10 – Production Orders 40 – Process Orders.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.