> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-im-wm-strm/app-master-data/screen-configuration/action-configuration.md). # Action configuration {% embed url="" %} ACTION configuration options will be setup in configuration with the data type ‘H - Screen Action Config’. This ensures that that the following screen is available in app master data to allow the action setup:

The Action Code must be already programmed in the code for the particular app/screen, but app master data allows the customising of the position, icons and/or text that will be displayed on the screen.

Option	Usage	Comments
Option	Usage	Comments
Action Code	This is the code that has been programmed for the app to perform a specific function.	The available action codes will be documented in the specific app configuration guide. It is not possible to create a new action, without an enhancement, but actions can be removed so that they are not visible to the users. Action codes must always be entered in capitals and must not have any spaces.
Default	Toggle to activate a particular action as the default for the screen when ENTER is pressed.	If an action is marked as ‘default’, when ENTER is pressed by the user this action will process. Note: Only one action code should be marked as default.
T-Code to Call	Transaction that is to be ‘jumped’ to by this action	This is the transaction that the action will jump to.
Action Description	Text that is displayed on the screen.	This is the text that will be displayed on the screen for the action. Using the F4 lookup one can see the list and select either DDIC entries or text override entries defined in WM_CFG, by selecting the appropriate tab in the search popup and then selecting the DDIC item or text ID as appropriate. Using F1 will display the text description behind the DDIC or Text ID in the field.
Button	Toggle.	If action button is ticked, the action appears as a standalone item on the screen in the position determined by the ‘Button Position’. If the toggle is off, the action is automatically added to a kebab menu in the position determined by the ‘Button Position’.
Button Position	Controls where on the screen the action is displayed.	The options for action placement include the combinations of header versus footer and left, right and middle. These are designated with the first character of the code as ‘H’ for header and ‘F’ for footer, and the second character of the code as ‘L’ for left, ‘M’ for middle and ‘R’ for right: · HL – header left. This is usually the default position for the BACK action. · HM – header middle. · HR – header right. · FL – footer left. · FM – footer middle. This is usually where kebab menus are placed. · FR – footer right. This is usually where the default action is placed.
Icon	Add the directory and icon reference. The SAP icon directory is typically sap-icon://	If an SAP icon is added here, it will be displayed for the action, together with any ‘Action Description’, if it has been maintained. The icon precedes the action description. Note: the typical SAP icons available can be viewed on the following UI5 website Icon Explorer (ondemand.com).
Tooltip	Tooltip text	Text entered here will display as tooltip text when using the apps on desktop. The tooltip text does not display on Android devices.
Class	Class	If actions are dependent on certain conditions or other criteria, a class may be assigned to the action. Alternatively, the text displayed can be changed for a particular action based on certain criteria.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.theconfigteam.com/prebilt-for-im-wm-strm/app-master-data/screen-configuration/action-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.