‎2005 Sep 29 5:37 AM
I need two table controls in one screen...
Can I put two table control in one screen without using subscreen? Is there any danger in doing this?
Or is it better to put the second table in a subscreen?
‎2005 Sep 29 5:42 AM
Hi,
You can go ahead using those in a single screen.
The advantage of using a subscreen for another Table
control will make you easier to hide the entire
functionality.
i.e say you are using a sub screen for the 2nd Table
control.If you don't call that Subscreen the code
written for the entire subscreen will not get triggered
thereby providing a transparency fo one over the
other.
Please reward points if this explanation useful.
Thanks,
Siva
‎2005 Sep 29 5:42 AM
Hi,
You can go ahead using those in a single screen.
The advantage of using a subscreen for another Table
control will make you easier to hide the entire
functionality.
i.e say you are using a sub screen for the 2nd Table
control.If you don't call that Subscreen the code
written for the entire subscreen will not get triggered
thereby providing a transparency fo one over the
other.
Please reward points if this explanation useful.
Thanks,
Siva
‎2005 Sep 29 5:53 AM
Hi SSG,
Why dont you go for TAB Strips.
You can define 2 Tab strips so that 1 table control in one and the other in 2and Tab strip.
CHEERS
‎2005 Sep 29 6:07 AM
Hi,
I agree with deepak, if you occupied more than one table control in one screen it will be climpsy ( if your requirement is like that then go ahead for ex they want to see all the two table control data at a same time )
Instead of the define one tabstrip with two tabs and each tab has separate subscreen then you place the table control in that screen.
cheers,
sasi
‎2005 Sep 29 6:59 AM
yes you should go for tabstrip.
it will be very useful, if you have to add one more table, customer demands always increase, so be prepared for that and create it in tabstrip.
regards
‎2005 Sep 29 7:06 AM
I agree with sasi,
But instead of two subscreens we can go for only one and and assign the same for both tabs. so, again we have to create two screens (as subscreens ) for table controls and assign it to the tabstrip.
reward points if it helps u and close the thread if ur problem is solved
CHEERS
‎2005 Sep 29 10:27 PM
Thanks for all the replies.. the user needs to see the data simultaneously(based on the row selected in first table control).. so tabstrip is not an option..
Both table controls should always be visible .. In such a scenario, do you think a separate subscreen area is useful ?
‎2005 Sep 30 12:09 AM
no problem at all...use as many table control as u need on single screen..i have been into module pools development for long now and it is completly safe.
Regards
Arpit
‎2005 Sep 30 5:52 PM
Arpit, thanks..
i have another question regarding chain endchain.. is it okay to define a same field in two different chain-request?
‎2005 Sep 30 5:53 PM
Hello SSG,
Yes you can define the same fields in different chain-requests.
‎2005 Sep 30 5:55 PM
Hi
Yes you can, there isn't a particular problem...
You can do it if you want to use a screen field in several control.
Generally you can repeat the same screen field in all controls you need.
Max
Message was edited by: max bianchi
‎2005 Oct 02 5:38 PM
I am trying to populate decimal field on the table control.. I have defined it with reference to unit field.. For some units, 6 decimal places is allowed and when I choose that unit, than my screen converts '1' to 0.000100 and gives invalid input message..
But when the unit is for 2 places (say like USD), it display this perfectly
‎2005 Oct 02 6:07 PM
Hi SSG,
USD is currency and not unit.
You have to use a field of type CURR ( like ekpo-netpr ) and reference to a field of type CUKY ( Like EKKO-WAERS )
on the screen to display your value correctly.
Cheers
‎2005 Oct 02 6:31 PM
i meant currency field, sorry for the confusion..
for Certain currency fields , the display is 6 decimal places.. But my screen spits it out, with message 088 (class 00).
‎2005 Oct 02 7:34 PM
I have already given the answer. Use a field CURR with a reference field CUKY . If you use a type P field with 2 decimals you will get that error. Your screen field has to refer to a Dictionary/ Porgram field which has type CURR and there should be another field of type CUKY .
( For example see PO create / change screen ME21/ME22 and see how they define net price and currency field in item overview )
Cheers.
( Dont forget to reward if answers were helpful )
‎2005 Oct 02 9:07 PM
In my case, it may not always be currency (i am using kbetr for condition record value) - depending on the record type it could also be percentage field.. So I cannot use CURR field all the time..
‎2005 Oct 03 3:29 AM
Ok So KBETR is a currency field . Goto SE51 -> Element list . Goto references tab. Here you will see a CUKY field. You will have to define this field as a Currency field on screen or else chanage this field to the fieldname which you have defined as currency field on screen( you will have to remove the Dict Ref Check box to do this ).
After this for the KBETR field in display attributes click on the right justified checkbox. Then try your transaction again.
If you dont put a currency value the input should have no more than 2 decimal places ( suits for percentage ) otherwise it will take the formatting of respective currency. Suppose USD has 2 decimals in currency setting and you try input 1.234 , it will again throw an error . So you have to input with correct decimal places . Try with different currency and the error message will change.
Cheers.
‎2005 Oct 03 2:11 PM
Sanjay, thanx for your patience.. This is what I have been doing from the start, let me know where I am going wrong..
I defined the KBETR field using KONWA field (also available on the screen) as reference and KBETR is right justified.. I am getting the kbetr and konwa values from condition tables .. When I populate it on the table control (through PBO), if konwa supports four decimal places, the value gets displayed perfectly on the table control (for example 1.0000) the first time.. But when I press enter or page down, it gives an error I had referred to earlier... When KONWA has currency like USD which supports two decimal places, it works perfectly...When I change the currency to one that supports multiple decimal places, value '1.00' gets converted to '1.0000' but the error message is also thrown...