Supressing Fields In A Sales Order

Solution 1:

If u want to suppress any fields in the screen U have to do in the SE51.

In VA03

1.... goto SYSTEM -> STATUS u will see the program name as SAPMV45A
2....double click on the program name.. then u can see the program name.. In this screen click the DISPLAY
OBJECT LIST (ctrlshiftf5) .. Then all objects of that program u can see...In those click the SCREEN
then u will see the all the screen numbers of the VA03 transaction.
3...here u can adjustments to that corresponding fields..

Solution 2:

Transaction Variants and Screen Variants

Transaction variants can simplify transaction runs as they allow you to:

Pre-assign values to fields

Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity
and simplicity.

Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the
individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned
to a specific transaction, can, however, also contain values for screens in other transactions if this is required by
transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is
called.

There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may
be assigned to a client-specific transaction variant.

A namespace exists for cross-client transaction variants and screen variants and both are automatically attached
to the Transport Organizer. Client-specific transaction variants must be transported manually.

In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are,
however, certain Restrictions that apply to certain transactions, depending on their internal structure.

No transaction variants are possible with transactions already containing preset parameters (parameter
transactions and variant transactions).
Solution 3:

Make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete
Procedures => select the fields > from the tables and the system will check for them (OVA2/VUA2)

To make a filed entry enabled or grey (non-entry allowed):

User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION

This user exit can be used to modify the attributes of the screen fields.

To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together
during a modification in ABAP.

If a field has no field name, it cannot be allocated to a group. The usage of the field groups (modification
group 1-4) is as follows:

Modification group 1: Automatic modification with transaction MFAW

Modification group 2: It contains 'LOO' for step loop fields

Modification group 3: For modifications which depend on check tables or on other fixed information

Modification group 4: is not used

The FORM routine is called up for every field of a screen. If you require changes to be made, you must
make them in this user exit. This FORM routine is called up by the module FELDAUSWAHL.

With Compliments by: Taner Yuksel

Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this
we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.

Below is the sample code

IF SCREEN-NAME = 'VBKD-ABSSC'.

AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.

IF sy-subrc = 0.
SCREEN-INPUT = 1.
else.
SCREEN-INPUT = 0.
ENDIF.
endif.

You place the authority check object in authorization profile in the role of the users, who should have
access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to
be accessed via this userexit.