How to make a field as display in a change mode

[Former Member]

hi gurus

is there any option to reduce the accessblity of a particular field has to be set as deactive mode.

Eg

In tcode XD02

I have to deactive any one of the field in this.

please explain is there any chance to do ?

regards

Maithrayan

[Former Member]

hi,

go to OBD2,enter ur account group for ur customer.

then there will be three types of data

whatever u want , double click on that

then u will find the field names

there wl be 4 options

supress

req

optional

display

choose ur requirement

now u will get the desires in the XD02

cheers

[Former Member]

hi,

At the customer level , these changes are maintained at the account group.

while customizing the accounting group , we have field status varients . in this exactly you can set the fields as your type.

thanks

Kuntla

[Former Member]

Hi,

If its the customer master that you need to do it then use account groups functionality for this. If the field is not appearing in your account group then try using some BADI for this.

If it is for some transational data like sales order screen that you want to acheve this, then use transaction and screen variants in tcode SHD0.

Regards,

Saurabh Diwakar

[Former Member]

Transaction variants simplify transaction flow by:

Inserting default values in fields

Hiding and changing the ready for input status of fields

Hiding and changing the attributes of table control columns

Hiding individual menu functions

Hiding entire screens

Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.

Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.

A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.

Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.

Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).

You can only create transaction variants for dialog transactions and reporting transactions.

Only "normal" screens, dialog boxes, and subscreens can be included in the variant.

Screen variants are automatically created anytime you create a transaction variant.

To create a transaction variant, proceed as follows:

Choose Tools ® AcceleratedSAP ® Personalization to call the transaction variant maintenance transaction, or use transaction code SHD0.

Enter the name of the transaction and the transaction variant on the initial screen.

The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto ® Client-specific transaction variants to branch the client-specific transaction variant maintenance transaction.

Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.

Choose Create to create a variant.

The system calls the application transaction that you want to create a variant for.

Enter the values you want to use in the input fields. Each time an action is completed (choosing for example), a dialog box appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed ( see Requirements).

Choose the options you want. The following options checkboxes can be selected: Adopt field values

Saves the field values you have inserted on the current screen

Resetting this field (deselecting it) allows you to delete all values saved for this screen in your transaction variant.

Do not display screen

Hides screen

This is only possible if settings are copied to your variant (Adopt field values).

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

You may or may not be able to select each of these checkboxes for every field depending on the field's type (see Requirements).

Enter a screen variant name and corresponding short text if necessary.

Screen variants are created automatically for each screen where values have been saved (copied). Enter screen variant names in the Name of screen variant: field. These names must be unique. If the system is able to find a unique name for a screen variant, it is automatically inserted into this field. (The convention reads as follows: .)

The following pushbuttons are available from this dialog box:

Cancel

Displays current application transaction screen again. Here you can make changes to your settings.

Deactivate menu functions

Deactivates menu functions in an additional dialog box.

GuiXT

Allows user to edit a GuiXT script for the current screen ( GuiXT).

Exit and Save

Exits and saves application transaction.

Choose the function Continue to proceed to the next screen in your application transaction. Repeat steps 3-5 for all further screens in the transaction.

When you have reached the last screen of the transaction and inserted the values you want to insert, choose Exit and Save. The system exits the application transaction and saves your entries. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).

You can also branch to this list using the Change values function during the function selection process.

Enter a short text for your transaction variant.

Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.

Choose Save. The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.

Deleting Preassigned Values

You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.

If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.

Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.

Also refer to document;

http://help.sap.com/saphelp_nw04s/helpdata/en/67/232037ebf1cc09e10000009b38f889/content.htm