module pool + screens

[Former Member]

i have a main scrreen and 5 tabs and the tabs are called dynamically via subscreens .

i have some fields which are common in some of the tabs .

The problem is when i am retrieving the data in one field using F4 help of one tab the data is getting populated into the othe tabs which have the same fields from the same table which should be restricted .

pl do reply and suitable replies would be rewarded .

[Former Member]

Hi,

If those are standard SAP table fields then it might be problem with the 'Parameter ID' of the DB table field. So when you move from one tab to another just clear the 'Parameter ID'.

Lets take -

---

for Material .... MAT is the parameter ID ...

Regards,

• Dj

reward, if its helpful

[Former Member]

I guess you are using same dictionary field on all 5 tabs.

If it's the same dictionary field then all 5 of them will have the same value because in effect it's only one variable/field.

If you need different values for them then you will have to use different variables.

Define 5 different variables and give them the same type(of that dictionary field).

Then all 5 will have different values.

[Former Member]

no the problem is i have to use the same dictionary fields in all the 5 tabs ( client requirement ).

pl come up with another idea

[Former Member]

If you share a field across the tabs then the value will automatically get updated by SAP as there is just one memory value being display... so you are best off controlling it yourself by having unique field names per tab e.g. if the tab subscreens are 2001, 2002, 2003 etc, then in the top include you can define a global structure per tab and these can contain the same field names, and other tab specifiec ones e.g.

begin of gs_2001,  "screen buffer for tab 2001
  belnr        like bkpf-belnr,
  kunnr        like kna1-belnr,
  date1        like sy-datum,
end of gs_2001,

begin of gs_2002,  "screen buffer for tab 2002
  belnr        like bkpf-belnr,
  kunnr        like kna1-belnr,
  date2        like sy-datum,
end of gs_2002,

then in your user command for the main screen you can control what gets copied between the data fields displayed - a single "move-corresponding gs_2001 to gs_2002" would ensure the values are synchronised as far as the user is concerned. This way, a search help on 2001 won't affect 2002 etc until you pass through the user command and determine that you want to keep the new value.