Scribd
Upload
411 views3 pages

SHD0

The document discusses using transaction and screen variants (SHD0) in ECC6 to make fields mandatory. It provides steps to create a transaction variant for transaction code FD32 that sets the Risk Category field to required. This is done by creating a screen variant for the FD32 Status screen in SHD0, setting Risk Category to required, and assigning this screen variant to a new transaction variant which is then set as the standard variant for FD32. This makes Risk Category a mandatory field whenever FD32 is run.

Uploaded by

Gaurav Harimitter
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
411 views3 pages

SHD0

The document discusses using transaction and screen variants (SHD0) in ECC6 to make fields mandatory. It provides steps to create a transaction variant for transaction code FD32 that sets the Risk Category field to required. This is done by creating a screen variant for the FD32 Status screen in SHD0, setting Risk Category to required, and assigning this screen variant to a new transaction variant which is then set as the standard variant for FD32. This makes Risk Category a mandatory field whenever FD32 is run.

Uploaded by

Gaurav Harimitter
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

SHD0 - Transaction and Screen Variants

In 4.5B, I like to use field exits to validate the


user entries for some fields in transaction or master data. But in ECC6,
field exits is not available for development anymore. So, I use SHD0
(Transaction and Screen Variants) to hide fields, menu functions,
screens, to supply individual fields with default values, to change the
ready for input status of one or more fields, or to make some fields
mandatory or required.
In my case, I want to set Risk Category field (KNKK-CTLPC) in the Status
screen as mandatory field in Customer Credit Management, t-code FD32.

What I did is creating a transaction variant for FD32 using transaction

SHD0, setting the Risk Category field to required in the process. Set this
variant as the 'standard variant' so that it is used whenever FD32 is run.
1. Creating New Transaction and Screen Variant for FD32.

2. Skip the initial screen by unticking the 'Copy Setting' and click the OK
button.

3. In the Status screen, set Risk Category as 'Required', tick 'Copy


Setting', put the 'Name of screen variant' and 'Screen variant short text',
click 'Exit and Save' button.

4. Continue the process.

5. Create a new Transaction variant and assign the new Screen variant
into it.

6. Assign the new Transaction variant to the Standard variant.

7. Save and check the result. The Risk Category field is become
mandatory.

You might also like