Do you have any question about this t-code?
Transaction Code: FOXI
Description: Display tenant
Release: S/4HANA and ECC 6
Program: SAPMF69P
Screen: 999
Authorization Object:
Development Package: FVVI
Package Description: R/3 appl.dev. for Financial Assets Management: Real estate
Parent Package: APPL
Module/Component: RE
Description: Real Estate Management
settings Overview: The SAP transaction code FOXI is used to display tenant settings in the SAP system. It is a part of the SAP S/4HANA Cloud system and is used to manage and configure tenant settings. Functionality: The FOXI transaction code allows users to view and manage tenant settings in the SAP system. This includes settings such as user roles, authorization objects, and other tenant-specific settings. It also allows users to view and edit existing tenant settings, as well as create new ones. Step-by-step How to Use: 1. Enter the transaction code FOXI in the command field of the SAP system. 2. The tenant settings will be displayed in a list format. 3. Select the setting you wish to view or edit by clicking on it. 4. The details of the setting will be displayed on the right side of the screen. 5. To edit an existing setting, click on the “Edit” button at the bottom of the screen. 6. To create a new setting, click on the “Create” button at the bottom of the screen. 7. Enter all necessary information for the new setting and click “Save” when finished. 8. To delete an existing setting, click on the “Delete” button at the bottom of the screen. 9. Confirm that you wish to delete the setting by clicking “Yes” when prompted. 10. Click “Back” to return to the list of tenant settings or “Exit” to exit out of FOXI transaction code. Other Recommendations: It is recommended that users familiarize themselves with all available tenant settings before making any changes or creating new ones in order to ensure that they are making changes that are appropriate for their system environment and business needs. Additionally, it is important to ensure that all changes are properly tested before being implemented in a production environment in order to avoid any potential issues or disruptions in service.