For which purposes can transaction variants be used? (Select two)

Transaction variants serve various functions in the context of SAP, particularly in customizing the user experience for specific transactions. One of the main uses of transaction variants is to modify the appearance and behavior of screens based on the user's needs.

Hiding fields in a sales order is a common application of transaction variants. This allows for a streamlined interface, ensuring that users are only presented with fields that are relevant to their tasks, which can enhance efficiency and user friendliness. By customizing which fields are displayed (or not displayed), organizations can enforce data entry standards and minimize confusion for users who might otherwise be overwhelmed by unnecessary options.

Additionally, transaction variants can also be utilized for defining default values for data fields. This capability enables organizations to set specific values that will automatically populate certain fields when a transaction is initiated, thereby reducing the amount of manual data entry required and ensuring consistency across transactions.

The other options, while related to the organization of data and user interface, do not align as closely with the primary functionalities of transaction variants in SAP. For example, defining values in a selection screen pertains more to report generation rather than transactional customization. Adding external fields to sales documents is a more complex process that often involves enhancements or modifications beyond what transaction variants can accomplish.