Introduction

This document will help functional consultant to create screen variant/transaction variant and achieve the business requirement without the support of technical team. This document aims to identify and describe all steps associated with the screen variant & transaction varaints. In addition, This document will help functional consultant who want to explore the possibility by screen variant functionality.

Purpose

Usually we have many such business requirement in every project where business ask us to preform such validation during a business transaction. We can achieve below functionality without the help of technical team. We can use screen variant to achieve the desired result. Screen variants can be used to achieve the below business requirement –

• Adopt field values – Saves the field values you have inserted on the current screen.
• Do not display screen – Hides screen
• With contents – Field contents are saved with it
• Output only – Field is no longer ready for input (display mode only)
• Invisible – Hides field
• Mandatory – Required field

Scope 

Explaining the creation of screen variant and transaction variant with the help of business requirement.

Requirement 

There is a requirement to grey out (Display mode) below mentioned fields during the MIRO transaction and make the Inv. Ref. a mandatory field.

Baseline date – Display Only

Payment terms – Display Only

Due on – Display Only

In. Ref. – Mandatory

Configuration 

Step 1 – find the program and field name. T code MIRO and Keep the cursor on field baseline date and click on F1.

Step2 – T code – OLMRLIST and enter the transaction MIRO

Click on Screen Variant and enter the program name and hit enter.

Select the screen 020.

Click on edit

Select the output only checkbox for

BaselineDt

Pyt Terms

Due On

Select the Required checkbox for

Inv. Ref.

Save the screen variant.

Step 3 – T code – SHD0

Create a transaction variant and assigned the screen variant.

Authorization 

The specific group for which we have created this transaction variant XXXXXXX  will now be authorized by BASIS with proper roles and authorizations. We can assign the group name as below.

Step 4- Check and test the variant.

Please do not forget to activate it.

Result

 Mandatory checkbox will appear in field.

Please share your valuable feedback.

Please follow my blog for FI cutover activities – 

https://blogs.sap.com/2022/10/14/sap-fi-cutover-activity-plan-complete-activities/

Please follow my blog for validation and substitution – 

https://blogs.sap.com/2022/10/30/user-exit-in-validation-substitution-for-functional-consultant/

Please follow the below link for related topic

https://answers.sap.com/tags/648420875567243523242285841826221

and read other posts on the topic –

https://blogs.sap.com/tags/648420875567243523242285841826221/

Please follow my profile for related information. Thanks Everyone 🙂