Configuration

Note

This configuration guide refers to PreBilt transactions beginning 'PB2_' and details the standard process without additional features or enhancements. You should copy these transactions with a different prefix to maintain a backup and protect the originals.

The guide displays the standard PreBilt screens and gives details of the structures in which the on screen fields can be found. Fields within these structures can be used to customise and enhance the screen. For instructions on how to use structures to find fields, please see Available data structures. For instructions on how to maintain the configuration elements in AMD, please see General configuration elements.

This covers the user profile maintenance that covers RF queues, default printers and any parameter ID updates for app transactions PB2_USER_MAINT_ALL, PB2_USER_MAINT_PRINT and PB2_USER_MAINT_RF.

User profile updates

All the supplied app transactions behave in the same way and are just different flavours with the same logic and structures.

User defaults

PB2_USER_MAINT_ALL

PB2_USER_MAINT_PRINT

PB2_USER_MAINT_RF

Configuration element	Available structures/fields
INPUT_MAIN	LRF_WKQU-QUEUE - queue assigned to the user USR01-SPLD - printer assigned to user USR05-<parameter ID> - PID from user profile Note To add the input fields for changing a value, use the above field names suffixed with "_IN".
INPUT_MAIN_ACTIONS	BACK - back to previous screen. SAVE – save updates.

Warning

For any parameter IDs that have a "/" (such as, for example, the TCT created ID for device types "/TCTM/WM_DEVICE_TYPE"), you will need to replace the "/" with a "." in the field column (since the frontend code cannot process "/"). Therefore the value to be added into the "Field" column in the AMD should be "USR05-.TCTM.WM_DEVICE_TYPE". In the "Initial Value Source" column in the AMD however you still use the PID as normal, e.g. "PID:/TCTM/WM_DEVICE_TYPE". See picture below for example.

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.
QUEUES_FILTER	Enables filtering of queues assigned to the warehouse, allowing the user to include or exclude specific values in the list view.
PRINTERS_FILTER	Enables filtering of printers assigned to the warehouse, allowing the user to include or exclude specific values in the list view.
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.
APP_TEXTS	Defines standard app text to be used in screen headers, buttons etc.
TRANS_INFO	Information about the transaction.