Skip to Content
author's profile photo Former Member
Former Member

User access to the field.

Hi,

Will anybody plz tell me ...........

How to make a field appears in gray mode (Display mode) after

it is updated in change mode. Means user can only see it for his information & can not change it but, same time he allowed for input i.e. other fields on the transaction screen should appear change mode i.e. allow user to input the data.

Ex :- In transaction CO02, ( order quantity field ) Total Quantity field should not be changed. i.e. first of all after maintaining the total quantity for a material , user should not allow to change it.

in this screen, user is allowed to enter Basic dates but, the sheduled & confirmed are in gray format i.e. on display only in change mode(CO02).

Thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 07:24 AM

    Hi,

    Usually the modify screen statement enables us to maintain screen attributes like display change etc.

    Syntax

    MODIFY SCREEN .

    Effect

    This statement can be used in the statement block after LOOP AT SCREEN only and makes sense only during PBO processing. If FROM is not specified, MODIFY SCREEN modifies the attributes of the current screen element with the values from the predefined screen work area. If a wa work area is specified, its contents are used for the modification.

    The wa work area must have the same data type as screen. The name component must contain the name of the current screen element, otherwise the statement is not executed. nweisung nicht ausgeführt. Up to the group1 to group4 and length components, all remaining components of screen and wa must contain either the value 0 or 1. The value 0 deactivates the corresponding field attribute, and 1 activates it.

    If MODIFY SCREEN is executed during PBO processing, the modified attributes for the display of the screen affect the current dynpro after PBO processing. The attributes of the screen element of the dynpro are reset to their static attributes at the start of each PBO processing, so that the execution of MODIFY SCREEN during PAI processing does not effect the display of the following screen.

    The active component

    The active component is used to set the input, output and invisible components at once. At the start of PBO processing, the active component always has the value 1. If active is set to 0 with MODIFY SCREEN, input and output are automatically set to 0 and invisible is set to 1. Other values in input, output and invisible are ignored. Conversely, setting input and output to 0 and invisible to 1 automatically sets active to 0 and a different value in active is ignored.

    Modifications in Table Controls and Step Loops

    During processing of a table control or a step loop, the changes affect the current line of the table control or the current step loop group. Before the processing of a table control, the change to the attributes of a screen element that is part of a line in the table control does not effect the table control, since the values are transferred from the structure created using CONTROLS. Before a step loop is processed, the change to the attributes of a screen elements that is part of a step loop group affects all groups in the step loop.

    Modifications to Tabstrip Controls

    If the active component for a tab title of a tabstrip control is set to 0, the whole tabstrip page is hidden.

    Example

    In the following PBO module, an input field called val is made mandatory and converted to display in the foreground.

    MODULE modify_0100 OUTPUT.

    LOOP AT SCREEN.

    IF screen-name = 'VAL'.

    screen-required = '1'.

    screen-intensified = '1'.

    MODIFY SCREEN.

    ENDIF.

    ENDLOOP.

    ENDMODULE.

    In your scenario, pls check whether any exits are available.

    Regards,

    Renjith Michael.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 09:53 AM

    Hi Ajit,

    I had a similar problem but solved. Refer this.

    In tcode U have to enter Transaction code VL01N

    Transaction variants field just Press F4 to get already buid transaction variant else u have to create the ur screen variant by clicking the button named Create in Below menu option .

    If the variant already exist -> enter

    u will get the data in the lower half of the screen , select the transaction Variant with field for storage location , generally datais distributed in delivry doc at header and item level so for storage location u have to take the one with item level data .

    There u will find the all the fields which are there in Delivery doc at item level with check boxes in front of them please goto storage location field and check the check box saying output field ( This means this field will be display only) Save and try and create the delivery again.

    This will be display only in VL01N.

    kindly reward if found helpful.

    cheers,

    Hema.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.