Transaction codes
Last updated
Was this helpful?
Last updated
Was this helpful?
Initial transactions for each PreBilt app will be provided in the initial installation using preconfigured BC Sets.
Note
Standard PreBilt transactions should be copied to create new app transactions . This both preserves the integrity of the out-of-the-box apps which can be used for reference, and then allows for the customising of the apps with new AMD settings. Additional copying to new app transactions can then also be performed for specific and different uses of an app. For example, with the WM Stock Movements app (service class: /TCTM/WM_APP_510), you may wish to create different app transactions, that reference the same service class, so that you can configure each to perform or select data differently while still using the core functionality of the app.
Enter edit mode in transaction /TCTM/WM_CFG by clicking the 'Display -> Change' button, and then 'New Entries'. Select 'Transaction Codes' from the Dialog Structure on the left of the screen.
It is recommended to copy an existing transaction by selecting a reference transaction and clicking the 'Copy As...' button.
When prompted, rename the transaction and amend the other details, if required. Copying a transaction allows dependent entries such as configuration fields and string list fields to be copied, which is recommended. Click 'copy all' on the pop-up.
Configuration fields control the screens and the functions available within each transaction.
If a transaction was created using a provided BC Set or by copying another transaction with its dependent entries, configuration fields will already be maintained.
Each entry contains the following information:
Sequence Number
Automatically calculated based on the next entry added to the list. Used to control the order in which the columns are displayed in /TCTM/WM_CFG_D (maximum 3 characters).
Field The name of the configuration option. It must be a single string without spaces, with a maximum length of 30 characters.
Device Type Relevant when implementing multiple device types requiring different screen configurations or app behaviors. A configuration option can be repeated for different device types. Refer to the document “PreBilt Apps - Defining a Menu Configuration Guide” for more details.
Field Text Description of the field, with a maximum length of 40 characters.
Data Type Specifies the data type for the field. There are 8 available data types that can be configured.
Length Defines the maximum number of characters allowed for entries when the data type is set to String. For all other data types, this value should be set to 0.
Warehouse Relevant Indicates whether the configuration option can be customized with different app master data settings for each warehouse. This setting should be active for applicable options.
Frontend Relevant Not currently used for PreBilt in IM/WM modules. Leave this field blank for all configuration elements.
There are 12 data types that allow configuration fields to complete particular functions.
Toggle Used when an option can be turned on or off.
String Used when a single value needs to be maintained for the app to reference.
String List Used when multiple values need to be maintained for the app to reference.
Detail Screen Config Selected when adding an option for screen configuration of a selection screen, input screen, or list header.
List Screen Config Selected when adding an option for screen configuration of a list body screen.
Fixed Key List Config Used when a fixed list of options needs to be maintained, and the field will not have a database-selected list of options (e.g., Plants, Storage Types).
Selection Range Filter Used when the field will default to reading a list of options from a database but requires further filtering. For example, exclude storage types starting with "9" from the selection.
Screen Action Config Selected when adding an option for controlling actions on a screen.
Search Help Parameter Map Fixes the format for the Search Help fields that can be set up in the AMD.
Serial Profile Overrides Fixes the format for the Serial Override fields that can be set up in the AMD.
UoM Value Conversion Fixes the format of the fields for setting up alternative UoM and Quantity display in the AMD.
UoM Conversion Sequence Fixes the format of the fields for setting up UoM Sequence in the AMD.
This option is only relevant if a data type of ‘String List’ is selected in the configuration fields section. A string list entry consists of multiple columns for each entry maintained:
Sequence Number Automatically calculated based on the next entry added to the list.
Field
Internal key for the entry. Must be a single string without spaces (e.g., SRC_LIST) with a maximum length of 30 characters.
Field Text
Description displayed as the column header when maintaining entries in /TCTM/WM_CFG_D. Maximum length: 40 characters.
Sequence Number (Display)
Controls the order in which columns are displayed in /TCTM/WM_CFG_D. Maximum length: 3 characters.
Data Type Selected from a drop-down list. Options:
A: Toggle (on/off).
B: String entry for entering a value.
Int Length
Specifies the maximum number of characters that can be inputted in the field when maintaining a value in /TCTM/WM_CFG_D.
Out Length
Defines the display length of the field when maintaining a value in /TCTM/WM_CFG_D.
Lowercase
Determines whether lowercase descriptions can be entered in /TCTM/WM_CFG_D. If not checked, entries are converted to uppercase when pressing "Enter."
Text Conversion
Identifies fields within the text list that are relevant for text conversion with a text ID. Supports language translation preparation and is used by the transaction /TCTM/WM_TEXTID_RPT for inclusion in selections and reporting.
Bespoke text elements can be used for labels or hints when standard data dictionary labels are unavailable or need customization.
Text elements can be created at the app transaction level in /TCTM/WM_CFG with any customer-defined name (up to 8 characters).
Standard text overrides are provided in the _GLOBAL_DEFAULTS transaction (loaded during the initial BC set setup) and referenced by all app transactions unless customized text overrides are created for local terms.
Some examples of how the text elements can be created are below:
When a text element is to be referenced in the app master data, it should be preceded with ‘TEXT-‘ so that the app knows to check for text elements. Example entries to be used in app master data, based on the above, would be:
TEXT-NO_DELIV
TEXT-SCAN
TEXT-ZEROPICK
Transaction /TCTM/WM_TEXTID_RPT (program /TCTM/WM_TEXTID_REPORT) can be run to identify all the elements in transactions’ AMD that are relevant for text IDs and show either the text ID that is already assigned or the free text that has not yet been converted to a text ID.
Upload program /TCTM/WM_TEXTID_UPLOAD can be run to upload text IDs into the configuration table 'Text Overrides' for any particular app transaction. The layout of the Excel upload file should be as follows and CSV, XLS and XLSX formats are supported.
Language
Tcode
TEXTID
Text
EN
_GLOBAL_DEFAULTS
TEST
Testing
DE
_GLOBAL_DEFAULTS
TEST
Testen
FR
_GLOBAL_DEFAULTS
TEST
Test
The above file would create entries for the text ID TEST is English, German and French for app transaction “_GLOABL_DEFAULTS”. The text would then be referenced in the AMD of anywhere that needs it as “TEXT-TEST”.
